Login
- Released At: 15-02-2025
- Page Views:
- Downloads:
- Table of Contents
- Related Documents
-
|
|
|
H3C CR16000-M System Log Messages Reference |
|
|
|
|
|
|
Copyright © 2024 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_INTERFACE_THRESHOLD_EXCEED
ARP_USER_DUPLICATE_IPADDR_DETECT
ATK_IPV6_EXT_HEADER_ABNORMAL_RAW
CLKM_SOURCE_FREQDEVIATION_ALARM
CLKM_SOURCE_FREQDEVIATION_NORMAL
DEV_BOARD_RUNNING_FAULT_REBOOT
DHCPS_ANTIFLOOD_DISABLE_FAILURE
DHCPS_ANTIFLOOD_ENABLE_FAILURE
DHCPS_WARNING_EXHAUSTIONRECOVER
DHCPS6_ANTIFLOOD_DISABLE_FAILURE
DHCPS6_ANTIFLOOD_ENABLE_FAILURE
DHCPS6_IP_NET_THRESHOLD_EXCEED
DHCPS6_IP_WARNING_EXHAUSTRECOVER
DHCPS6_PD_NET_THRESHOLD_EXCEED
DHCPS6_PD_WARNING_EXHAUSTRECOVER
DHCPS6_POOLGP_EXHAUSTION_RECOV
DHCPS6_POOLGP_THRESHOLD_EXCEED
DIAG_DMA_MEM_CRITICAL_THRESHOLD
KERNEL_MEMFRAGMT_BELOW_THRESHOLD
KERNEL_MEMFRAGMT_EXCEED_THRESHOLD
DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE
DOMAIN_ND_PREF_UPTHR_ALM_REMOVE
DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE
DOMAIN_PD_PREF_UPTHR_ALM_REMOVE
DOMAIN_IPV6_WEB_SERVER_NOT_REACH
DOMAIN_IPV6_WEB_SERVER_URL_SWITCH
DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE
DOMAIN_ND_PREF_UPTHR_ALM_REMOVE
DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE
DOMAIN_PD_PREF_UPTHR_ALM_REMOVE
DOT1X_CLEAR_MAX_USER_THRESHOLD
EDEV_FAILOVER_GROUP_STATE_CHANGE
ETH_VLAN_TERMINATION_NOT_SUPPORT
ETHOAM_CONNECTION_FAIL_TIMEOUT
ETHOAM_CONNECTION_FAIL_UNSATISF
ETHOAM_ENTER_LOOPBACK_CTRLLING
ETHOAM_LOCAL_ERROR_FRAME_PERIOD
ETHOAM_LOCAL_ERROR_FRAME_SECOND
ETHOAM_REMOTE_ERROR_FRAME_PERIOD
ETHOAM_REMOTE_ERROR_FRAME_SECOND
FDB/3/EVPN_MACMOVE_REPORT_SUPPRESS
FDB/3/EVPN_MACMOVE_LOG_SUPPRESS
FLEXE_BANDWIDTH_MISMATCH_RECOVER
FLEXE_BANDWIDTH_REDUCE_RECOVER
FLEXE_CLIENTID_MISMATCH_RECOVER
FLEXE_GROUPMEMBER_FAULT_RECOVER
FLEXE_PHYGROUP_MISMATCH_RECOVER
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
IP6ADDR_CREATEADDRESS_CONFLICT
IPADDR_CREATEADDRESS_CONFILICTADDR
IPADDR_CREATEADDRESS_OVERLAPADDR
IP_ADD_INTERFACE_ANTITCPSYNFLD
IP_DEL_INTERFACE_ANTITCPSYNFLD
IP_INSERT_FAILED_ANTITCPSYNFLD
IP_SETTING_FAILED_ANTITCPSYNFLD
IPFW_FRAGPKTNUM_EXCALARMRESUME
IPOE_IPV4_HTTP_ATTACK_EXCEED_ERROR
IPOE_IPV4_REMAIN_ACL_BELOW_ERROR
IPOE_IPV6_HTTP_ATTACK_EXCEED_ERROR
IPOE_IPV6_REMAIN_ACL_BELOW_ERROR
IPOE_SESSIONS_LOWER_THRESHOLD (non-vBRAS-CPs)
IPOE_SESSIONS_LOWER_THRESHOLD (vBRAS-CPs)
IPOE_SESSIONS_LOWER_RECOVER (non-vBRAS-CPs)
IPOE_SESSIONS_LOWER_RECOVER (vBRAS-CPs)
IPOE_SESSIONS_UPPER_THRESHOLD (non-vBRAS-CPs)
IPOE_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
IPOE_SESSIONS_UPPER_RECOVER (non-vBRAS-CPs)
IPOE_SESSIONS_UPPER_RECOVER (vBRAS-CPs)
ISIS_LSP_TOO_LARGE_TO_PROPAGATE
L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD (UPs)
L2TPV2_LOSS_RATIO_RECOVER_NORMAL (UPs)
L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD (non-vBRAS-CPs)
L2TPV2_LOSS_RATIO_RECOVER_NORMAL (non-vBRAS-CPs)
L2TPV2_SESSIONS_LOWER_THRESHOLD (non-vBRAS-CPs)
L2TPV2_SESSIONS_LOWER_THRESHOLD (vBRAS-CPs)
L2TPV2_SESSIONS_LOWER_RECOVER (non-vBRAS-CPs)
L2TPV2_SESSIONS_LOWER_RECOVER (vBRAS-CPs)
L2TPV2_SESSIONS_UPPER_THRESHOLD (non-vBRAS-CPs)
L2TPV2_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
L2TPV2_SESSIONS_UPPER_RECOVER (non-vBRAS-CPs)
L2TPV2_SESSIONS_UPPER_RECOVER (vBRAS-CPs)
L2TPV2_TUNNEL_ADD_DRIVER_FAILED
LAGG_INACTIVE_DRNI_PRIORITY_WRONG
LAGG_INACTIVE_DRNI_SPEED_WRONG
LAGG_INACTIVE_PARTNER_KEY_WRONG
LAGG_INACTIVE_PARTNER_MAC_WRONG
LAGG_INACTIVE_RESOURCE_INSUFICIE
NAT_EIM_MODE_PORT_USAGE_RECOVER
NAT_PORTBLOCKGRP_MEMORY_WARNING
NAT_SERVICE_CARD_RECOVER_FAILURE
ND_SET_VLAN_REDIRECT_NORESOURCE
NETSLICING_NO_ENOUGH_HARDWARE_RESOURCE
NETSLICING_NOT_SUPPORT_PROTOCOLNUM
NQA_TWAMP_LIGHT_PACKET_INVALID
NQA_TWAMP_LIGHT_SENDER_START_FAILURE
OFC_DATAPATH_CHANNEL_DISCONNECT
OFP_ACTIVE_MAC_LEARN_FORBIDDEN_F
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
PKI_REQUEST_LOCAL_CERT_FAIL_LDAP
PKI_REQUEST_LOCAL_CERT_FAIL_SCEP
PKI_REQUEST_LOCAL_CERT_SUCCESS_LDAP
PKI_REQUEST_LOCAL_CERT_SUCCESS_SCEP
PPP_SESSIONS_LOWER_THRESHOLD (non-vBRAS-CPs)
PPP_SESSIONS_LOWER_THRESHOLD (vBRAS-CPs)
PPP_SESSIONS_LOWER_RECOVER (non-vBRAS-CPs)
PPP_SESSIONS_LOWER_RECOVER (vBRAS-CPs)
PPP_SESSIONS_UPPER_THRESHOLD (non-vBRAS-CPs)
PPP_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
PPP_SESSIONS_UPPER_RECOVER (non-vBRAS-CPs)
PPP_SESSIONS_UPPER_RECOVER (vBRAS-CPs)
PPPOES_LOSS_RATIO_EXCEED_THRESHOLD
PPPOES_LOSS_RATIO_RECOVER_NORMAL
PPPOES_SESSION_ADD_DRIVER_FAILED
PPPOES_SESSIONS_LOWER_THRESHOLD
PPPOES_SESSIONS_RECOVER_NORMAL
PPPOES_SESSIONS_UPPER_THRESHOLD
PTP_TIME_OFFSET_EXCEED_THRESHOLD
QOS_QMPROFILE_MODIFYQUEUE_FAIL
SRPV6_SEGLIST_STATE_DOWN_CLEAR
STRUNK_DROPPACKET_INCONSISTENCY
DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE
DOMAIN_ND_PREF_UPTHR_ALM_REMOVE
DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE
DOMAIN_PD_PREF_UPTHR_ALM_REMOVE
IPOE_IPV4_HTTP_ATTACK_EXCEED_ERROR
IPOE_IPV4_REMAIN_ACL_BELOW_ERROR
IPOE_IPV6_HTTP_ATTACK_EXCEED_ERROR
IPOE_IPV6_REMAIN_ACL_BELOW_ERROR
UCM_APPLY_PPPOEA_FWD_POLICY_FAIL (non-vBRAS-CPs)
UCM_IFBACKUPSTATUS_DRIVER_FAILED (pUPs)
UCM_IPV4_PPPOEA_BOUND_SUCCESS (non-vBRAS-CPs)
UCM_LOSS_RATIO_EXCEED_THRESHOLD
UCM_SESSIONS_LOWER_THRESHOLD (non-vBRAS-CPs)
UCM_SESSIONS_LOWER_THRESHOLD (vBRAS-CPs)
UCM_SESSIONS_LOWER_RECOVER (non-vBRAS-CPs)
UCM_SESSIONS_LOWER_RECOVER (vBRAS-CPs)
UCM_SESSIONS_UPPER_THRESHOLD (non-vBRAS-CPs)
UCM_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
UCM_SESSIONS_UPPER_RECOVER (non-vBRAS-CPs)
UCM_SESSIONS_UPPER_RECOVER (vBRAS-CPs)
UCM_UP_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
UCM_UP_SESSIONS_RECOVER_NORMAL (vBRAS-CPs)
UCM_UPBAK_STATE_CHANGE (vBRAS-CPs)
UCM_USER_RECOVER_NORMAL (non-vBRAS-CPs)
UCM_USER_RECOVER_NORMAL (vBRAS-CPs)
UCM_USER_UPPER_THRESHOLD (non-vBRAS-CPs)
UCM_USER_UPPER_THRESHOLD (vBRAS-CPs)
UCM_USER_ONLINE_FAIL_ALARM (non-vBRAS-CPs)
UCM_USER_ONLINE_FAIL_ALARM (vBRAS-CPs)
Introduction
This document includes the following system messages:
· Messages specific to Release R8385P66 of the device.
· Messages for the Comware 7 software platform version based on which Release R8385P66 was produced. Some platform system messages might not be available on the device.
This document is intended only for managing CR16000-M devices. 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. It is calculated by using the following formula: Priority identifier=facilityx8+severity Where: · Facility is specified by using the info-center loghost command. A log host uses this parameter to identify log sources and filter log messages. · Severity represents the importance of the message. For more information about severity levels, see Table 2. |
|
Prefix |
Message type identifier. This element is contained in the system log messages sent to non-log-host destinations. The element uses the following symbols to indicate message severity: · Percentage sign (%)—Informational and higher levels. · Asterisk (*)—Debug level. |
|
TIMESTAMP |
Date and time when the event occurred. The following are commands for configuring the timestamp format: · Log host—Use the info-center timestamp loghost command. · Non-log host destinations—Use the info-center timestamp command. |
|
Sysname |
Name or IP address of the device that generated the message. |
|
%%vendor |
Manufacturer flag. This element is %%10 for H3C. This element is contained only in messages sent to the log host. |
|
MODULE |
Name of the module that produced the message. |
|
severity |
Severity level of the message. (For more information about severity levels, see Table 2.) |
|
MNEMONIC |
Text string that uniquely identifies the system message. The maximum length is 32 characters. |
|
location |
Optional. This element identifies where the message occurred. This element is contained only in messages sent to the log host. This element presents location information for the message in the following format: -attribute1=x-attribute2=y…-attributeN=z The following are examples of location attributes: · -MDC=XX, which represents the MDC on which the message occurred. · -DevIp=XXX.XXX.XXX.XXX, which represents the source IP of the message. · -Slot=XX, which represents the slot on which the message occurred. · -Chassis=XX-Slot=XX, which represents the chassis and slot on which the message occurred. This element is separated from the message description by using a semicolon (;). |
|
CONTENT |
Text string that contains detailed information about the event or error. For variable fields in this element, this document uses the representations in Table 3. |
System log messages are classified into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 2.
Table 2 System log message severity levels
|
Level |
Severity |
Description |
|
0 |
Emergency |
The system is unusable. For example, the system authorization has expired. |
|
1 |
Alert |
Action must be taken immediately. For example, traffic on an interface exceeds the upper limit. |
|
2 |
Critical |
Critical condition. For example, the device temperature exceeds the upper limit, the power module fails, or the fan tray fails. |
|
3 |
Error |
Error condition. For example, the link state changes or a storage card is unplugged. |
|
4 |
Warning |
Warning condition. For example, an interface is disconnected, or the memory resources are used up. |
|
5 |
Notification |
Normal but significant condition. For example, a terminal logs in to the device, or the device reboots. |
|
6 |
Informational |
Informational message. For example, a command or a ping operation is executed. |
|
7 |
Debug |
Debugging message. |
For variable fields in the message text, this document uses the representations in Table 3. The values are case insensitive, even though the representations are uppercase letters.
Table 3 Variable field representations
|
Representation |
Information type |
|
INT16 |
Signed 16-bit decimal number. |
|
UINT16 |
Unsigned 16-bit decimal number. |
|
INT32 |
Signed 32-bit decimal number. |
|
UINT32 |
Unsigned 32-bit decimal number. |
|
INT64 |
Signed 64-bit decimal number. |
|
UINT64 |
Unsigned 64-bit decimal number. |
|
DOUBLE |
Two dot-separated signed 32-bit decimal numbers. The format is [INTEGER].[INTEGER]. |
|
HEX |
Hexadecimal number. |
|
CHAR |
Single character. |
|
STRING |
Character string. |
|
IPADDR |
IP address. |
|
MAC |
MAC address. |
|
DATE |
Date. |
|
TIME |
Time. |
Managing and obtaining system log messages
You can manage system log messages by using the information center.
By default, the information center is enabled. Log messages can be output to the console, 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/ path if the flash is not partitioned.
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 |
|
ANCP |
Access Node Control Protocol |
|
ARP |
Address Resolution Protocol |
|
ATK |
Attack Detection and Prevention |
|
ATM |
|
|
BFD |
Bidirectional Forwarding Detection |
|
BGP |
Border Gateway Protocol |
|
BIER |
Bit Index Explicit Replication |
|
CFGMAN |
Configuration Management |
|
CLKM |
Clock Monitoring |
|
CONNLMT |
Connection Limit |
|
DEV |
Device Management |
|
DHCPR |
IPv4 DHCP Relay |
|
DHCPS |
DHCP Server |
|
DHCPS6 |
DHCPv6 Server |
|
DHCPSP4 |
DHCP Snooping |
|
DHCPSP6 |
DHCPv6 Snooping |
|
DIAG |
Diagnosis |
|
DLDP |
Device Link Detection Protocol |
|
DOT1X |
802.1X |
|
EDEV |
|
|
EIGRP |
Enhanced Interior Gateway Routing Protocol |
|
ETH |
Ethernet |
|
ETHOAM |
Ethernet Operation, Administration and Maintenance |
|
FIB |
Forwarding Information Base |
|
FILTER |
Filter |
|
gRPC |
Google Remote Procedure Call |
|
HA |
High Availability |
|
HQOS |
Hierarchical QoS |
|
iFIT |
In-situ Flow Information Telemetry |
|
IFMON |
Interface Monitor |
|
IFNET |
Interface Net Management |
|
IGMP |
Internet Group Management Protocol |
|
IKE |
Internet Key Exchange |
|
IP6ADDR |
IPv6 Addressing |
|
IP6FW |
IPv6 Forwarding |
|
IPADDR |
IP Addressing |
|
IPFW |
IP Forwarding |
|
IPOE |
IP over Ethernet |
|
IPSEC |
IP Security |
|
IRDP |
ICMP Router Discovery Protocol |
|
IRF |
Intelligent Resilient Framework |
|
ISIS |
Intermediate System-to-Intermediate System |
|
L2TPV2 |
Layer 2 Tunneling Protocol Version 2 |
|
L2VPN |
Layer 2 VPN |
|
LAGG |
Link Aggregation |
|
LDP |
Label Distribution Protocol |
|
LIPC |
Leopard Inter-process Communication |
|
LLDP |
Link Layer Discovery Protocol |
|
LOAD |
Load Management |
|
LOCAL |
Local |
|
LOGIN |
Login |
|
LPDT |
Loopback Detection |
|
LS |
Local Server |
|
LSM |
Label Switch Management |
|
LSPV |
LSP Verification |
|
MAC |
Media Access Control |
|
MBFD |
MPLS BFD |
|
MFIB |
Multicast Forwarding Information Base |
|
MGROUP |
Mirroring group |
|
MPLS |
Multiprotocol Label Switching |
|
MTLK |
Monitor Link |
|
MTP |
Maintenance Probe |
|
NAT |
Network Address Translation |
|
ND |
Neighbor Discovery |
|
NETCONF |
Network Configuration Protocol |
|
NQA |
Network Quality Analyzer |
|
NTP |
Network Time Protocol |
|
OFP |
OpenFlow Protocol |
|
OPTMOD |
Optical Module |
|
OSPF |
Open Shortest Path First |
|
OSPFV3 |
Open Shortest Path First Version 3 |
|
PBR |
Policy-Based Routing |
|
PFILTER |
Packet Filter |
|
PIM |
Protocol Independent Multicast |
|
PING |
Packet Internet Groper |
|
PKI |
Public Key Infrastructure |
|
PKT2CPU |
Packet to CPU |
|
PKTCPT |
Packet Capture |
|
PORTAL |
Portal |
|
PPP |
Point to Point Protocol |
|
PTP |
Precision Time Protocol |
|
PWDCTL |
Password Control |
|
QOS |
Quality of Service |
|
RADIUS |
Remote Authentication Dial In User Service |
|
RESMON |
Resource Monitor |
|
RIP |
Routing Information Protocol |
|
RIPNG |
Routing Information Protocol Next Generation |
|
RM |
Routing Management |
|
RSVP |
Resource Reservation Protocol |
|
RTM |
Real-Time Event Manager |
|
SAVA |
Source Address Validation Architecture |
|
SCRLSP |
Static CRLSP |
|
SESSION |
Session |
|
SHELL |
Shell |
|
SLSP |
Static LSP |
|
SNMP |
Simple Network Management Protocol |
|
SRPV6 |
SRv6-TE Policy |
|
SRV6 |
SRv6 |
|
SSHC |
Secure Shell Client |
|
STM |
Stack Topology Management |
|
STP |
Spanning Tree Protocol |
|
STRUNK |
Smart Trunk |
|
SYSEVENT |
System Event |
|
SYSLOG |
System Log |
|
TACACS |
Terminal Access Controller Access Control System |
|
TE |
Traffic Engineering |
|
UCM |
User Connection Management |
|
URPF |
Unicast Reverse Path Forwarding |
|
VLAN |
Virtual Local Area Network |
|
VRRP |
Virtual Router Redundancy Protocol |
|
VSRP |
Virtual Service Redundancy Protocol |
|
VXLAN |
Virtual eXtensible LAN |
Using this document
This document categorizes system log messages by software module. The modules are ordered alphabetically. Except for OPENSRC, the system log messages for each module are listed in alphabetic order of their mnemonic names. The OPENSRC messages are unordered because they use the same mnemonic name (SYSLOG). For each OPENSRC message, the section title uses a short description instead of the mnemonic name.
This document explains messages in tables. Table 5 describes information provided in these tables.
Table 5 Message explanation table contents
|
Item |
Content |
Example |
|
Message text |
Presents the message description. |
ACL [UINT32] [STRING] [UINT64] packet(s). |
|
Variable fields |
Briefly describes the variable fields in the order that they appear in the message text. The variable fields are numbered in the "$Number" form to help you identify their location in the message text. |
$1: ACL number. $2: ID and content of an ACL rule. $3: Number of packets that matched the rule. |
|
Severity level |
Provides the severity level of the message. |
6 |
|
Example |
Provides a real message example. The examples do not include the "<PRI>TIMESTAMP Sysname %%vendor" part or the "Prefix TIMESTAMP Sysname" part, because information in this part varies with system settings. |
ACL/6/ACL_STATIS_INFO: ACL 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s). |
|
Explanation |
Explains the message, including the event or error cause. |
Number of packets that matched an ACL rule. This message is sent when the packet counter changes. |
|
Recommended action |
Provides recommended actions. For informational messages, no action is required. |
No action is required. |
AAA messages
This section contains AAA messages.
AAA_ADMIN_LOGIN_FAILED_ACTIVE
|
Message text |
Administrative user login failed too frequently. Failures=[UINT32], statistics period=[UINT32] min. |
|
Variable fields |
$1: Number of login failures of the administrative user. $2: Statistical period for the login failures of the administrative user, in minutes. |
|
Severity level |
4 (Warning) |
|
Example |
AAA/4/AAA_ADMIN_LOGIN_FAILED_ACTIVE: Administrative user login failed too frequently. Failures=[35], statistics period=[10] min. |
|
Impact |
The system might be under login attacks. |
|
Cause |
When the number of failed login attempts by the administrative user reaches the alarm threshold for the first time within a specified statistical period, or increases from below the recovery threshold to the alarm threshold, this log message will be generated. You can use the aaa login-failed alarm-threshold command to set the alarm threshold and statistical period for login failures of the administrative user. |
|
Recommended action |
1. The system might be under login attacks. Contact the administrator. 2. If you have forgotten the username or password, contact the administrator. |
AAA_ADMIN_LOGIN_FAILED_CLEAR
|
Message text |
Number of administrative user login failures dropped below the alarm clearing threshold. Failures=[UINT32], statistics period=[UINT32] min. |
|
Variable fields |
$1: Number of login failures of the administrative user. $2: Statistical period for the login failures of the administrative user, in minutes. |
|
Severity level |
5 (Notification) |
|
Example |
AAA/5/AAA_ADMIN_LOGIN_FAILED_CLEAR: Number of administrative user login failures dropped below the alarm clearing threshold. Failures=[14], statistics period=[10] min. |
|
Impact |
No negative impact on the system. |
|
Cause |
When the number of failed login attempts by the administrative user decreases from a value equal to or greater than the alarm threshold to a value below the recovery threshold within a specified statistical period, this log message will be generated. You can use the aaa login-failed alarm-threshold command to set the recovery threshold and statistical period for login failures of the administrative user. |
|
Recommended action |
No action is required. |
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 (Notification) |
|
Example |
AAA/5/AAA_FAILURE: -AAAType=AUTHORIZATION-AAADomain=domain1-Service=login-UserName=cwf@system; AAA failed. |
|
Impact |
No negative impact on the system. |
|
Cause |
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, collect the device configuration file, log information, and alarm information, and 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 (Informational) |
|
Example |
AAA/6/AAA_LAUNCH: -AAAType=AUTHENTICATION-AAADomain=domain1-Service=login-UserName=cwf@system; AAA launched. |
|
Impact |
No negative impact on the system. |
|
Cause |
The user attempts to come online through AAA authentication. |
|
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 (Informational) |
|
Example |
AAA/6/AAA_SUCCESS: -AAAType=AUTHORIZATION-AAADomain=domain1-Service=login-UserName=cwf@system; AAA succeeded. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device accepted an AAA request. |
|
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 (Warning) |
|
Example |
ACL/4/ACL_ACCELERATE_NO_RES: Failed to accelerate IPv6 ACL 2001. The resources are insufficient. |
|
Impact |
If the ACL contains a large number of rules, the packet match speed will be affected, and the connection establishment time or packet forwarding efficiency will be affected. |
|
Cause |
Hardware resources were insufficient for accelerating an ACL. |
|
Recommended action |
Delete some rules or disable ACL acceleration for other ACLs to release hardware resources. |
ACL_ACCELERATE_NONCONTIGUOUSMASK
|
Message text |
Failed to accelerate IPv4 ACL [UINT32]. ACL acceleration supports only contiguous wildcard masks. |
|
Variable fields |
$1: ACL number. |
|
Severity level |
4 (Warning) |
|
Example |
ACL/4/ACL_ACCELERATE_NONCONTIGUOUSMASK: Failed to accelerate ACL 2001. ACL acceleration supports only contiguous wildcard masks. |
|
Impact |
If the ACL contains a large number of rules, the packet match speed will be affected, and the connection establishment time or packet forwarding efficiency will be affected. |
|
Cause |
ACL acceleration failed because rules containing noncontiguous wildcard masks exist in the ACL. |
|
Recommended action |
Modify or delete the ACL rules containing noncontiguous wildcard masks. |
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 (Warning) |
|
Example |
ACL/4/ACL_ACCELERATE_NOT_SUPPORT: Failed to accelerate IPv6 ACL 2001. The operation is not supported. |
|
Impact |
If the ACL contains a large number of rules, the packet match speed will be affected, and the connection establishment time or packet forwarding efficiency will be affected. |
|
Cause |
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 (Warning) |
|
Example |
ACL/4/ACL_ACCELERATE_NOT_SUPPORTHOPBYHOP: Failed to accelerate IPv6 ACL 3001. ACL acceleration does not support the rules that contain the hop-by-hop keywords. |
|
Impact |
If the ACL contains a large number of rules, the packet match speed will be affected, and the connection establishment time or packet forwarding efficiency will be affected. |
|
Cause |
ACL acceleration failed for the IPv6 ACL because rules containing the hop-by-hop keyword exist in the ACL. |
|
Recommended action |
Delete the ACL rules containing the hop-by-hop keyword. |
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 (Warning) |
|
Example |
ACL/4/ACL_ACCELERATE_NOT_SUPPORTMULTITCPFLAG: Failed to accelerate IPv6 ACL 3001. ACL acceleration does not support specifying multiple TCP flags in one rule. |
|
Impact |
If the ACL contains a large number of rules, the packet match speed will be affected, and the connection establishment time or packet forwarding efficiency will be affected. |
|
Cause |
ACL acceleration failed for the IPv6 ACL because rules containing multiple TCP flags (ACK, FIN, PSH, RST, SYN, and URG) exist in the ACL. |
|
Recommended action |
Retain only one TCP flag in the IPv6 ACL rules or delete the IPv6 ACL rules. |
ACL_ACCELERATE_UNK_ERR
|
Message text |
Failed to accelerate [STRING] ACL [UINT32]. |
|
Variable fields |
$1: ACL type. $2: ACL number. |
|
Severity level |
4 (Warning) |
|
Example |
ACL/4/ACL_ACCELERATE_UNK_ERR: Failed to accelerate IPv6 ACL 2001. |
|
Impact |
If the ACL contains a large number of rules, the packet match speed will be affected, and the connection establishment time or packet forwarding efficiency will be affected. |
|
Cause |
ACL acceleration failed because of an unknown error. |
|
Recommended action |
1. Execute the undo accelerate command and then execute the accelerate command. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
ACL/6/ACL_IPV6_STATIS_INFO: IPv6 ACL 2000 rule 0 permit source 1:1::/64 logging 1000 packet(s). |
|
Impact |
No negative impact on the system. |
|
Cause |
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 [UINT32] due to lack of memory. |
|
Variable fields |
$1: ACL type. $2: ACL number. |
|
Severity level |
3 (Error) |
|
Example |
ACL/3/ACL_NO_MEM: Failed to configure IPv4 ACL 2001 due to lack of memory. |
|
Impact |
The ACL cannot take effect. |
|
Cause |
Configuring the ACL failed because memory is insufficient. |
|
Recommended action |
Use the display memory-threshold command to check the memory usage. · If the memory usage is too high, increase memory. · If the memory usage is abnormal, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
ACL/6/ACL_STATIS_INFO: ACL 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s). |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of packets matching the IPv4 ACL rule changed. |
|
Recommended action |
No action is required. |
ANCP messages
This section contains ANCP messages.
ANCP_INVALID_PACKET
|
Message text |
-NeighborName=[STRING]-State=[STRING]-MessageType=[STRING]; The [STRING] value [STRING] is wrong, and the value [STRING] is expected. |
|
Variable fields |
$1: ANCP neighbor name. $2: Neighbor state. $4: Field. $5: Wrong value of the field. $6: Expected value of the field. |
|
Severity level |
6 (Informational) |
|
Example |
ANCP/6/ANCP_INVALID_PACKET: -NeighborName=Dslam-State=SYNSENT-MessageType=SYNACK; The Sender Instance value 0 is wrong, and the value 1 is expected. |
|
Impact |
The impact on the system depends on the actual situation. |
|
Cause |
The system received an adjacency message that had a field with a wrong value. |
|
Recommended action |
1. Verify that the ANCP configuration is correct. 2. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
API messages
This section contains API messages.
PORT_BW_NOTENOUGH
|
Message text |
Not enough limit resources. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PORT/3/PORT_BW_NOTENOUGH: -MDC=1-Slot=2; Not enough limit resources. |
|
Explanation |
The rate-limiting resources are insufficient for an XGE/GE switchover. |
|
Recommended action |
Make sure the rate-limiting resources are sufficient. |
PORT_INTERNAL_FAULT
|
Message text |
A fault has been detected for the internal link used by the interface side. Please check the hardware! |
|
Severity level |
3 |
|
Example |
PORT/3/PORT_INTERNAL_FAULT: -MDC=1-Slot=2; A fault has been detected for the internal link used by the interface side. Please check the hardware! |
|
Explanation |
The interface used by the internal link is incorrect. |
|
Recommended action |
· Please contact Technical Support. |
ARP
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 (Informational) |
|
Example |
ARP/6/ARP_ACTIVE_ACK_NO_REPLY: No ARP reply from IP 192.168.10.1 was received on interface GigabitEthernet1/0/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
Possible causes include: · ARP active acknowledgement detects an attack. · The interface sends an ARP request to the sender IP of the received ARP packet, without receiving an ARP response. |
|
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 issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 |
4 (Warning) |
|
Example |
ARP/4/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. |
|
Impact |
Some normal ARP response packets might be discarded. |
|
Cause |
Possible causes include: · ARP active acknowledgement detects an attack. · When the interface receives an ARP response without sending an ARP request to the IP address of the sender of the ARP packet |
|
Recommended action |
1. Check for ARP packet attacks in the network by capturing packets to find the source of the attack 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_ALARM_CLEAR
|
Message text |
The number of ARP entries dropped below the threshold. Threshold=[UINT32]; Number of dynamic ARP entries=[UINT32]; Number of static ARP entries=[UINT32]; Other ARP entries=[UINT32]. |
|
Variable fields |
$1: Security threshold for the number of global ARP entries. $2: Number of dynamic ARP entries. $3: Number of static ARP entries. $4: Number of other ARP entries. |
|
Severity level |
5 (Notification) |
|
Example |
ARP/5/ARP_ALARM_CLEAR: The number of ARP entries dropped below the threshold. Threshold=100; Number of dynamic ARP entries=59; Number of static ARP entries=0; Other ARP entries=0. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of global ARP entries (static and dynamic ARP entries) drops below the global security threshold. The global security threshold equals to 60% of the custom device entry specifications. |
|
Recommended action |
No action is required. |
ARP_ATTACK_SUPPRESSION_ADD
|
Message text |
An ARP attack has been detected on interface [STRING], and an ARP attack suppression entry was generated for it. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (warning) |
|
Example |
ARP/4/ARP_ATTACK_SUPPRESSION_ADD: An ARP attack has been detected on interface GigabitEthernet1/0/1, and an ARP attack suppression entry was generated for it. |
|
Impact |
Before the suppression time for the entry expires, the maximum receiving rate for ARP packets is limited on the interface. |
|
Cause |
After you enable ARP attack suppression, an ARP attack occurs on an interface. |
|
Recommended action |
Use the display arp attack-suppression per-interface command to view interface-based ARP attack suppression entries. |
ARP_ATTACK_SUPPRESSION_DEL
|
Message text |
The ARP attack suppression entry for interface [STRING] was deleted. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 (Notification) |
|
Example |
ARP/5/ARP_ATTACK_SUPPRESSION_DEL: The ARP attack suppression entry for interface GigabitEthernet1/0/1 was deleted. |
|
Impact |
No negative impact on the system. |
|
Cause |
When an interface has an ARP attack suppression entry, the number of ARP requests received by the interface within the suppression period drops below a specific value, and the ARP attack suppression entry is deleted. |
|
Recommended action |
No action is required. |
ARP_BINDRULETOHW_FAILED
|
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 (Notification) |
|
Example |
ARP/5/ARP_BINDRULETOHW_FAILED: Failed to download binding rule to hardware on the interface Ethernet1/0/1, SrcIP 1.1.1.132, SrcMAC 0015-E944-A947, VLAN 1, Gateway MAC 00A1-B812-1108. |
|
Impact |
No negative impact on the system. |
|
Cause |
Binding rule delivery failed due to insufficient hardware resources, insufficient memory, or other hardware errors. |
|
Recommended action |
1. Execute the display qos-acl resource command to verify whether there are sufficient hardware ACL resources. ¡ If there are, go to step 2 ¡ If there are not, cancel some ACL configurations or accept the current result. 2. Execute the display memory command to verify whether there are sufficient memory resources. ¡ If there are, go to step 3 ¡ If there are not, cancel some configurations or accept the current result. 3. Hardware error occurred, cancel the last relevant configuration and try again. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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: Name of an interface (including the tunnel interface, Layer 3 interface, or Ethernet service instance). $3: VSI name. $4: Source MAC address of the conflicting peer $5: Source interface name of the conflicting peer (Including Tunnel interface, Layer 3 interface, and Ethernet service instance, etc.) $6: VSI name of the conflicting peer $7: Conflicting IP address |
|
Severity level |
6 (Informational) |
|
Example |
ARP/6/ARP_DUPLICATE_IPADDR_DETECT: Detected an IP address conflict. The device with MAC address 00-00-01 connected to interface Ethernet0/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. |
|
Impact |
There may be IP address configuration conflicts in the network, which may cause route flapping, disruption of user services or traffic, and other faults |
|
Cause |
The interface receives ARP packets with conflicting IP addresses from the sender compared to the IP addresses learned in the ARP table of this device |
|
Recommended action |
1. Identify whether there are devices with the same IP address configured in the network, and adjust the IP address of the conflicting device 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_DYNAMIC
|
Message text |
The maximum number of dynamic ARP entries for the device reached. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
ARP/3/ARP_DYNAMIC: The maximum number of dynamic ARP entries for the device reached. |
|
Impact |
The device cannot learn new ARP entries due to insufficient resources, which might cause service unreachability. |
|
Cause |
The total number of dynamic ARP entries learned on the device reaches the upper limit. |
|
Recommended action |
1. Execute the display arp command to view dynamic ARP entries 2. Execute the arp max-learning-number command to increase the maximum number of dynamic ARP entries that the device can learn 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_DYNAMIC_IF
|
Message text |
The maximum number of dynamic ARP entries for interface [STRING] reached. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
3 (Error) |
|
Example |
ARP/3/ARP_DYNAMIC_IF: The maximum number of dynamic ARP entries for interface GigabitEthernet3/0/1 reached. |
|
Impact |
The device cannot learn new dynamic ARP entries due to insufficient resources, which might cause service unreachability. |
|
Cause |
The total number of dynamic ARP entries learned on the interface reaches the upper limit. |
|
Recommended action |
1. Execute the display arp command to view dynamic ARP entries on the specified interface 2. Based on network planning and business provisioning, Verify whether the dynamic ARP entries learned on the interface are necessary for the user ¡ If the dynamic ARP entries are necessary for the user, go to step 3 ¡ If the dynamic ARP entries are not necessary for the user, and ensure that the service is not affected, execute the undo arp command to delete the specified ARP entry 3. Execute the arp max-learning-num command to increase the maximum number of dynamic ARP entries allowed to be learned on the specified interface 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 |
3 (Error) |
|
Example |
Pattern 1: ARP/3/ARP_DYNAMIC_SLOT: The maximum number of dynamic ARP entries for slot 2 reached. Pattern 2: ARP/3/ARP_DYNAMIC_SLOT: The maximum number of dynamic ARP entries for chassis 1 slot 2 reached. |
|
Impact |
The card cannot learn new dynamic ARP entries due to insufficient resources, which might cause service unreachability. |
|
Cause |
Pattern 1: The number of dynamic ARP entries learned on the specified slot reaches the upper limit. Pattern 2: The number of dynamic ARP entries learned on the specified slot in the chassis reaches the upper limit. |
|
Recommended action |
1. Execute the display arp command to view dynamic ARP entries on the specified board 2. Check whether the learned dynamic ARP entries are necessary according to network planning and business provisioning ¡ If the dynamic ARP entries are necessary, go to step 3 ¡ If the dynamic ARP entries are not necessary, and the service is not affected, execute the command 'undo arp' to delete the specified ARP entry 3. Execute the arp max-learning-number command to increase the maximum number of dynamic ARP entries that can be learned on the specified board 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 belongs to the public network, it will be displayed as the public network $3: Inconsistent entry parameter type. · MAC address: MAC address. · output interface: ARP entry's output interface. · output port: ARP entry's output port. · outermost layer VLAN ID: Layer 1 VLAN tag. · second outermost layer VLAN ID: Layer 2 VLAN tag. · VSI index: VSI index. · link ID: VSI outbound link identifier. |
|
Severity level |
6 (Informational) |
|
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. |
|
Impact |
Possible causes for abnormal business traffic interruption or forwarding to the wrong port. |
|
Cause |
Due to insufficient resources or software runtime errors, there is a discrepancy between hardware forwarding entry information and the information recorded in memory. |
|
Recommended action |
No action is required. ARP will actively refresh the hardware entries. |
ARP_FEATURE_ENABLE_FAILED
|
Message text |
Failed to enable the feature on interface [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
ARP/6/ARP_FEATURE_ENABLE_FAILED: Failed to enable the feature on interface GE1/0/1. |
|
Impact |
The issue affects normal operation of the feature. |
|
Cause |
Failed to issue the arp rate-limit, arp filter binding, or arp filter source command on an interface. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_HOST_IP_CONFLICT
|
Message text |
The host [STRING] connected to interface [STRING] cannot communicate correctly, because it uses the same IP address as the host connected to interface [STRING]. |
|
Variable fields |
$1: IP address. $2: Interface name. $3: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_HOST_IP_CONFLICT: The host 1.1.1.1 connected to interface GigabitEthernet1/0/1 cannot communicate correctly, because it uses the same IP address as the host connected to interface GigabitEthernet1/0/2. |
|
Impact |
The issue might cause user service or traffic interruption. |
|
Cause |
Possible causes include: · Different hosts connected under this device are configured with the same IP address. · Possible ARP attack in the network. |
|
Recommended action |
1. According to the log information, check the configuration of the conflicting hosts under the corresponding interface and adjust the IP address. 2. Check the legitimacy of the host sending the ARP message. If the host is illegitimate, disconnect it from the network. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_IP_CONFLICT
|
Message text |
Received an ARP packet with a duplicate IP address. ConflictInterface=[STRING]; Conflict IP address=[STRING]; ConflictMac=[STRING]; SVlan=[UINT32]; CVlan=[UINT32]. |
|
Variable fields |
$1: Name of the interface that receives the conflicting ARP packet. $2: Sender IP address in the conflicting ARP packet. $3: Sender MAC address in the conflicting ARP packet. $4: Outer VLAN ID in the conflicting ARP packet. $5: Inner VLAN ID in the conflicting ARP packet. |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_IP_CONFLICT: Received an ARP packet with a duplicate IP address. ConflictInterface=GigabitEthernet2/0/1; Conflict IP address=192.168.56.2; ConflictMac=0300-1602-00e0; SVlan=0; CVlan=0. |
|
Impact |
The gateway information of the user might be edited by the attacker, causing an ARP attack and user service interruption. |
|
Cause |
After you use the arp local-conflict record enable command to enable recording conflicts between an endpoint and the local device, the device detects a conflict. Possible reasons include: · The IP address of the local device is also used by another device on the network. · An ARP attack that forges the source IP address exists on the network. |
|
Recommended action |
1. Identify whether another device on the network has the same IP address as that of the local device. ¡ If you can identify the device that has the same IP address, change the IP address of the device. ¡ If you cannot identify the device that has the same IP address, change the IP address of the corresponding interface. Make sure the operation does not affect services. 2. Identify whether an ARP attack exists on the network and identify the attack source through capturing packets. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_IP_CONFLICT_RESOLVED
|
Message text |
IP address conflicts were resolved. ConflictInterface=[STRING]; Conflict IP address=[STRING]; ConflictMac=[STRING]; SVlan=[UINT32]; CVlan=[UINT32]. |
|
Variable fields |
$1: Name of the interface that receives the conflicting ARP packet. $2: Sender IP address in the conflicting ARP packet. $3: Sender MAC address in the conflicting ARP packet. $4: Outer VLAN ID in the conflicting ARP packet. $5: Inner VLAN ID in the conflicting ARP packet. |
|
Severity level |
5 (Notification) |
|
Example |
ARP/5/ARP_IP_CONFLICT_RESOLVED: IP address conflicts were resolved. ConflictInterface=vlan-interface 10; Conflict IP address=192.168.56.100; ConflictMac=0300-1602-00e1; SVlan=0; CVlan=0. |
|
Impact |
No negative impact on the system. |
|
Cause |
After you use the arp local-conflict record enable command to enable recording conflicts between an endpoint and the local device, the interface does not receive any ARP packet in which the sender IP address is the same as the interface IP address within 3 minutes. |
|
Recommended action |
No action is required. |
ARP_INTERFACE_ALARM_CLEAR
|
Message text |
The number of ARP entries dropped below the threshold of interface [STRING]. Threshold=[UINT32]; Number of dynamic ARP entries=[UINT32]. |
|
Variable fields |
$1: Interface name. $2: Dynamic ARP entry security threshold on the interface. $3: Number of dynamic ARP entries on the interface. |
|
Severity level |
5 (Notification) |
|
Example |
ARP/5/ARP_INTERFACE_ALARM_CLEAR: The number of ARP entries dropped below the threshold of interface GigabitEthernet1/0/1. Threshold=100; Number of dynamic ARP entries=59. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of dynamic ARP entries on the interface drops below the security threshold, which is 60% of the dynamic ARP learning limit on the interface set by the arp max-learning-num command. |
|
Recommended action |
No action is required. |
ARP_INTERFACE_THRESHOLD_EXCEED
|
Message text |
The number of ARP entries exceeded the threshold of interface [STRING]. Threshold=[UINT32]; Number of dynamic ARP entries=[UINT32]. |
|
Variable fields |
$1: Interface name. $2: Dynamic alarm threshold for the interface. $3: Number of dynamic ARP entries on the interface. |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_INTERFACE_THRESHOLD_EXCEED: The number of ARP entries exceeded the threshold of interface GigabitEthernet1/0/1. Threshold=100; Number of dynamic ARP entries=81. |
|
Impact |
The interface cannot learn new ARP entries, which might cause service unreachability. |
|
Cause |
The number of dynamic ARP entries exceeded the dynamic alarm threshold for the interface. The dynamic alarm threshold for an interface is 80% of the dynamic ARP learning limit set by the arp max-learning-num command. |
|
Recommended action |
1. Execute the display arp command to check the dynamic ARP entries on the interface. 2. Based on the network planning and service deployment, identify whether the dynamic ARP entries learned by the interface are necessary. ¡ If the dynamic ARP entries are necessary, go to step 3. ¡ If the dynamic ARP entries are not necessary, execute the undo arp command to delete ARP entries. Make sure the operation does not affect services. 3. Execute the arp max-learning-num command to set a larger dynamic ARP learning limit for the interface. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_MAC_CONFLICT
|
Message text |
A MAC address conflict occurred. ConflictInterface=[STRING]; ConflictMac=[STRING]; Source IP address=[STRING]; SVlan=[UINT32]; CVlan=[UINT32]; InputInterface=[STRING]. |
|
Variable fields |
$1: Name of the interface that received the ARP packet with a conflicting MAC address. $2: Sender MAC address in the ARP packet. $3: Sender IP address in the ARP packet. $4: Outer VLAN ID for the ARP packet. $5: Inner VLAN ID for the ARP packet. $6: Name of the physical interface corresponding to the VLAN interface that received the ARP packet. |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_MAC_CONFLICT: A MAC address conflict occurred. ConflictInterface=vlan-interface 10; ConflictMac=0300-1602-00e0; Source IP address=192.168.10.1; SVlan=0; CVlan=0; InputInterface=GigabitEthernet1/0/1. |
|
Impact |
User services might be interrupted. |
|
Cause |
The sender MAC address in the ARP packet conflicted with the MAC address of the local device after you enable recording conflicts between the endpoints and local device by using the arp local-conflict record enable command. Possible reasons are: · An endpoint has the same MAC address as that of the local device on the network. · The network has a loop. |
|
Recommended action |
1. Configure STP to identify whether the network has a loop. 2. Identify whether another device on the network has the same MAC address as that of the local device. ¡ If you can identify the device that has the same MAC address, change the MAC address of the device. ¡ If you cannot identify the device that has the same MAC address, change the MAC address of the corresponding interface. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_MAC_CONFLICT_RESOLVED
|
Message text |
The MAC address conflict was removed. ConflictInterface=[STRING]; ConflictMac=[STRING]; Source IP address=[STRING]; SVlan=[UINT32]; CVlan=[UINT32]; InputInterface=[STRING]. |
|
Variable fields |
$1: Name of the interface that received the ARP packet with a conflicting MAC address. $2: Sender MAC address in the ARP packet. $3: Sender IP address in the ARP packet. $4: Outer VLAN ID for the ARP packet. $5: Inner VLAN ID for the ARP packet. $6: Name of the physical interface corresponding to the VLAN interface that received the ARP packet. |
|
Severity level |
5 (Notification) |
|
Example |
ARP/5/ARP_MAC_CONFLICT_RESOLVED:The MAC address conflict was removed. ConflictInterface=vlan-interface 10; ConflictMac=0300-1602-00e0; Source IP address=192.168.10.1; SVlan=0; CVlan=0; InputInterface=GigabitEthernet1/0/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
No new conflict occurs within 3 minutes after you enable recording conflicts between the endpoints and local device by using the arp local-conflict record enable command and a MAC address conflict occurs. |
|
Recommended action |
No action is required. |
ARP_MAC_IP_CONFLICT
|
Message text |
A MAC and IP address conflicts occurred. ConflictInterface=[STRING]; ConflictMac=[STRING]; Conflict IP address=[STRING]; Received packet's destination MAC address=[STRING]; Received packet's destination IP address=[STRING]; SVlan=[UINT32]; CVlan=[UINT32]; InputInterface=[STRING]. |
|
Variable fields |
$1: Name of the interface that received the ARP packet with conflicting MAC and IP addresses. $2: Sender MAC address in the ARP packet. $3: Sender IP address in the ARP packet. $4: Target MAC address in the ARP packet. $5: Target IP address in the ARP packet. $6: Outer VLAN ID for the ARP packet. $7: Inner VLAN ID for the ARP packet. $8: Name of the physical interface corresponding to the VLAN interface that received the ARP packet. |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_MAC_IP_CONFLICT: A MAC and IP address conflicts occurred. ConflictInterface= vlan-interface 10; ConflictMac=0300-1602-00e0; Conflict IP address=192.168.56.100; Received packet's destination MAC address=0300-1602-00e1; Received packet's destination IP address=192.168.56.2; SVlan=0; CVlan=0; InputInterface= GigabitEthernet2/0/1. |
|
Impact |
User services might be interrupted. |
|
Cause |
The sender MAC and IP addresses in the ARP packet conflicted with the MAC and IP addresses of the local device after you enable recording conflicts between the endpoints and local device by using the arp local-conflict record enable command. Possible reasons are: · The network might have an ARP attack. · The network has a loop. |
|
Recommended action |
1. Configure STP to identify whether the network has a loop. 2. If the network does not have any loop, identify the source through capturing packets, and then edit the IP and MAC addresses of the device that sends the ARP packet. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_MAC_IP_CONFLICT_RESOLVED
|
Message text |
The MAC and IP address conflicts were resolved. ConflictInterface=[STRING], ConflictMac=[STRING]; Conflict IP address=[STRING]; Received packet's destination MAC address=[STRING]; Received packet's destination IP address=[STRING]; SVlan=[UINT32], CVlan=[UINT32]; InputInterface=[STRING]. |
|
Variable fields |
$1: Name of the interface that received the ARP packet with duplicate MAC and IP addresses. $2: Sender MAC address in the ARP packet. $3: Sender IP address in the ARP packet. $4: Target MAC address in the ARP packet. $5: Target IP address in the ARP packet. $6: Outer VLAN ID for the ARP packet. $7: Inner VLAN ID for the ARP packet. $8: Name of the physical interface corresponding to the VLAN interface that received the ARP packet. |
|
Severity level |
5 (Notification) |
|
Example |
ARP/5/ARP_MAC_IP_CONFLICT_RESOLVED: The MAC and IP address conflicts were resolved. ConflictInterface= vlan-interface 10; ConflictMac=0300-1602-00e0; Conflict IP address=192.168.56.100; Received packet's destination MAC address=0300-1602-00e1; Received packet's destination IP address=192.168.56.2; SVlan=0; CVlan=0; InputInterface= GigabitEthernet2/0/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
No new conflict occurs within 3 minutes after you enable recording conflicts between the endpoints and local device by using the arp local-conflict record enable command and a MAC and IP address conflict occurs. |
|
Recommended action |
No action is required. |
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 packet rate limit, $3: Interface name. $4: Interval. |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_RATE_EXCEEDED: The ARP packet rate (100 pps) exceeded the rate limit (80 pps) on interface Ethernet0/1/0 in the last 10 seconds. |
|
Impact |
ARP message rate on the interface exceeds the ARP rate limit and may affect normal ARP learning and response, causing traffic forwarding failure |
|
Cause |
The ARP packet rate of the interface exceeded the rate limit. |
|
Recommended action |
1. Identify whether the ARP messages received on the interface are normal ¡ If all received ARP messages are reasonable, execute the arp rate-limit command to increase the value of ARP message rate limit on the specified interface ¡ If abnormal ARP messages are detected, go to step 2 2. Use packet capture to check for ARP message attacks in the network and find the source of the attack 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_RATELIMIT_NOTSUPPORTED
|
Message text |
Pattern 1: The ARP packet rate limit feature is not supported on interface [STRING] in slot [INT32]. Pattern 2: The ARP packet rate limit feature is not supported on interface [STRING] in chassis [INT32] slot [INT32]. |
|
Variable fields |
Pattern 1: $1: Interface name. $2: Slot number. Pattern 2: $1: Interface name. $2: Chassis number. $3: Slot number. |
|
Severity level |
6 (Informational) |
|
Example |
ARP/6/ARP_RATELIMIT_NOTSUPPORTED: The ARP packet rate limit feature is not supported on interface GE2/0/1 in slot 2. |
|
Impact |
No negative impact on the system. |
|
Cause |
Pattern 1: The interface on the specified slot does not support the ARP packet rate limit feature. Pattern 2: The interface on the specified slot in the specified chassis does not support the ARP packet rate limit feature. |
|
Recommended action |
No action is required. |
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 (Informational) |
|
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. |
|
Impact |
The network might have an ARP attack, affecting the normal operation of the device. |
|
Cause |
Possible causes include: · The IP address configuration of the ARP message sender is incorrect and does not belong to the same network segment as the corresponding interface. · The host sending the ARP message is not legitimate, and there may be ARP attacks in the network. |
|
Recommended action |
1. Check the legitimacy of the IP address of the ARP message sender's host. ¡ If the host is illegal, it needs to be disconnected from the network. ¡ If the host is legal, then, while ensuring that the business is not affected, adjust the IP address of the host and the corresponding interface to be in the same network segment. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 |
4 (Warning) |
|
Example |
ARP/4/ARP_SENDER_MAC_INVALID: Sender MAC 0000-5E14-0E00 was not identical to Ethernet source MAC 0000-5C14-0E00 on interface GigabitEthernet1/0/1. |
|
Impact |
The network might have an ARP attack, affecting normal device operation. |
|
Cause |
The host that sends the ARP packet is not valid, and the network might have an ARP attack. |
|
Recommended action |
1. Check the legitimacy of the MAC address of the ARP message sender's host. If the host is illegal, it needs to be disconnected from the network 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_SLOT_ALARM_CLEAR
|
Message text |
Pattern 1: The number of ARP entries dropped below the threshold of slot [UINT16]. Threshold=[ UINT32]; Number of dynamic ARP entries=[UINT32]; Pattern 2: The number of ARP entries dropped below the threshold of chassis [UINT16] slot [UINT16]. Threshold=[ UINT32]; Number of dynamic ARP entries=[UINT32]; |
|
Variable fields |
Pattern 1: $1: Slot number. $2: Dynamic security threshold for the card. $3: Number of dynamic ARP entries on the card. Pattern 2: $1: Chassis number. $2: Slot number. $3: Security threshold for the card. $4: Number of dynamic ARP entries for the card. |
|
Severity level |
5 (Notification) |
|
Example |
Pattern 1: ARP/5/ARP_SLOT_ALARM_CLEAR: The number of ARP entries dropped below the threshold of slot 1. Threshold=60; Number of dynamic ARP entries=59. Pattern 2: ARP/5/ARP_SLOT_ALARM_CLEAR: The number of ARP entries dropped below the threshold of chassis 1 slot 1. Threshold=60; Number of dynamic ARP entries=59; |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of dynamic ARP entries on the card dropped below the dynamic security threshold for the card. The dynamic security threshold for a card is 60% of the dynamic ARP learning limit set by the arp max-learning-number command. |
|
Recommended action |
No action is required. |
ARP_SLOT_THRESHOLD_EXCEED
|
Message text |
Pattern 1: The number of ARP entries exceeded the threshold of slot [UINT16]. Threshold=[UINT32]; Number of dynamic ARP entries=[UINT32]; Pattern 2: The number of ARP entries exceeded the threshold of chassis [UINT16] slot [UINT16]. Threshold=[UINT32]; Number of dynamic ARP entries=[UINT32]; |
|
Variable fields |
Pattern 1: $1: Slot number. $2: Dynamic alarm threshold for the card. $3: Number of dynamic ARP entries on the card. Pattern 2: $1: Chassis number. $2: Slot number. $3: Alarm threshold for the card. $4: Number of dynamic ARP entries on the card. |
|
Severity level |
4 (Warning) |
|
Example |
Pattern 1: ARP/4/ARP_SLOT_THRESHOLD_EXCEED: The number of ARP entries exceeded the threshold of slot 1. Threshold=80; Number of dynamic ARP entries=81. Pattern 2: ARP/4/ARP_SLOT_THRESHOLD_EXCEED: The number of ARP entries exceeded the threshold of chassis 1 slot 1. Threshold=80; Number of dynamic ARP entries=81; |
|
Impact |
The card cannot learn new ARP entries, which might cause service unreachability. |
|
Cause |
The number of dynamic ARP entries on the card exceeded the dynamic alarm threshold for the card. The dynamic alarm threshold for a card is 80% of the dynamic ARP learning limit set by the arp max-learning-number command. |
|
Recommended action |
1. Execute the display arp command to check the dynamic ARP entries on the card. 2. Based on the network planning and service deployment, identify whether the dynamic ARP entries learned by the card are necessary. ¡ If the dynamic ARP entries are necessary, go to step 3. ¡ If the dynamic ARP entries are not necessary, execute the undo arp command to delete ARP entries. Make sure the operation does not affect services. 3. Execute the arp max-learning-number command to set a larger dynamic ND learning limit for the card. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_SPEEDLIMIT_ALARM
|
Message text |
Packet rate exceeded the rate limit. ThresholdRate =[UINT32]; CurrentRate=[UINT32]; SuppressType=[STRING]; |
|
Variable fields |
$1: Alarm threshold for ARP packets or ARP Miss messages sent per second. $2: The current peak number of ARP packets or ARP Miss messages sent per second. $3: Limit object, including ARP packets or ARP Miss messages. |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_SPEEDLIMIT_ALARM: Packet rate exceeded the rate limit. ThresholdRate =50; CurrentRate =60; SuppressType=ARP. |
|
Impact |
Some normal ARP packets might be dropped, causing traffic forwarding failure. |
|
Cause |
The sending rate of ARP packets or ARP Miss messages exceeded the alarm threshold or the network might have an ARP attack. |
|
Recommended action |
1. Identify whether the network has an ARP attack based on the message. Capture packets to identify the source of IP packets in which the destination IP address is unreachable. Identify whether the source is valid. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_SPEEDLIMIT_ALARM_CLEAR
|
Message text |
Packet rate dropped below the rate limit. ThresholdRate =[UINT32]; CurrentRate=[UINT32]; SuppressType=[STRING]. |
|
Variable fields |
$1: Alarm threshold for ARP packets or ARP Miss messages sent per second. $2: The current peak number of ARP packets or ARP Miss messages sent per second. $3: Limit object, including ARP packets or ARP Miss messages. |
|
Severity level |
5(Notification) |
|
Example |
ARP/5/ARP_SPEEDLIMIT_ALARM_CLEAR: Packet rate dropped below the rate limit. ThresholdRate =50; CurrentRate =60; SuppressType=ARP. |
|
Impact |
No negative impact on the system. |
|
Cause |
The sending rate of ARP packets or ARP Miss messages dropped below the alarm threshold. To avoid frequent alarm notifications or alarm recovery notifications, the device does not output notifications within 1 minute after the alarm recovers. |
|
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 (Informational) |
|
Example |
ARP/6/ARP_SRC_MAC_FOUND_ATTACK: An attack from MAC 0000-5E14-0E00 was detected on interface GigabitEthernet1/0/1. |
|
Impact |
Some normal ARP packets may be discarded, affecting normal business |
|
Cause |
The ARP attack detection function with a fixed source MAC address detects an attack. Within 5 seconds, if ARP packets with the same source MAC address (fixed source MAC address) exceed a certain threshold |
|
Recommended action |
1. Check the legitimacy of the host corresponding to this source MAC address ¡ If the host is legitimate, execute the 'arp source-mac exclude-mac' command to configure the MAC address as a protected MAC address ¡ If the host is illegitimate, the host's network needs to be disconnected or the 'arp source-mac filter' command needs to be executed to configure the detection mode of the ARP attack detection function with a fixed source MAC address as filtering mode 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_SUPPR_ALARM_CLEAR
|
Message text |
The number of ARP suppression entries dropped below the threshold. (Threshold=[ UINT32], Number of Suppression ARP entries=[UINT32]) |
|
Variable fields |
$1: Alarm threshold of ARP flooding suppression table $2: Number of devices ARP flooding suppression table |
|
Severity level |
5 (Notification) |
|
Example |
ARP/5/ARP_SUPPR_ALARM_CLEAR: The number of ARP suppression entries dropped below the threshold. Threshold=100; Number of Suppression ARP entries=59. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of devices ARP flooding suppression table has recovered below the safe threshold. The safe threshold of ARP flooding suppression is equal to 60% of the customized suppression entry specifications. |
|
Recommended action |
No action is required. |
ARP_SUPPR_THRESHOLD_EXCEED
|
Message text |
The number of ARP suppression entries exceeded the threshold. Threshold=[UINT32]; Number of ARP Suppression entries=[UINT32]. |
|
Variable fields |
$1: Alarm threshold for ARP flooding suppression table $2: Current number of ARP flooding suppression tables on the device |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_SUPPR_THRESHOLD_EXCEED: The number of ARP suppression entries exceeded the threshold. Threshold=100; Number of ARP Suppression entries=81. |
|
Impact |
Possible inability to learn new ARP flooding suppression entries due to insufficient resources, leading to out of service interruptions |
|
Cause |
Number of ARP flooding suppression tables on the device exceeds the alarm threshold. Alarm threshold for ARP flooding suppression = Customized suppression table specifications × 80% |
|
Recommended action |
1. Execute the display arp suppression xconnect-group command to view ARP flooding suppression entries 2. Verify whether the ARP flooding suppression entries on the device are necessary according to network planning and business deployment ¡ If ARP flooding suppression entries are necessary for the user, go to step 3 ¡ If ARP flooding suppression entries are not necessary for the user, execute the reset arp suppression xconnect-group command to clear ARP flooding suppression entries 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
ARP/6/ARP_TARGET_IP_INVALID: Target IP 192.168.10.2 was not the IP of the receiving interface Ethernet0/1/0. |
|
Impact |
The network might have an ARP attack, affecting the normal operation of devices |
|
Cause |
The host sending the ARP packet is illegal, and there may be ARP attacks in the network |
|
Recommended action |
1. Verify whether the received ARP packet is a broadcast packet ¡ If it is, no action is required. ¡ If it is not, go to step 2 2. Check the legitimacy of the host that sent the ARP packet, if the host is illegal, the network connection should be terminated 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_THRESHOLD_EXCEED
|
Message text |
The number of ARP entries exceeded the threshold. Threshold=[UINT32]; Number of dynamic ARP entries=[UINT32]; Number of static ARP entries=[UINT32]; Other ARP entries=[UINT32]. |
|
Variable fields |
$1: Alarm threshold for global ARP entries. $2: Number of dynamic ARP entries. $3: Number of static ARP entries. $4: Number of other ARP entries. |
|
Severity level |
4 (Warning) |
|
Example |
ARP/4/ARP_THRESHOLD_EXCEED: The number of ARP entries exceeded the threshold. Threshold=100; Number of dynamic ARP entries=81; Number of static ARP entries=0; Other ARP entries=0. |
|
Impact |
The device cannot learn new ARP entries, which might cause service unreachability. |
|
Cause |
The number of global ARP entries (static ARP entries and dynamic ARP entries) exceeded the global alarm threshold. The global alarm threshold is 80% of the customized ARP entry specification for the product. |
|
Recommended action |
1. Execute the display arp all command to compare the numbers of static and dynamic ARP entries. ¡ If the number of static ARP entries is larger, go to step 2. ¡ If the number of dynamic ARP entries is larger, go to step 3. 2. Based on the network planning and service deployment, identify whether the static ARP entries are necessary. ¡ If the static ARP entries are necessary, go to step 3. ¡ If the static ARP entries are not necessary, execute the undo arp command to delete ARP entries or execute the reset arp static command to clear static ARP entries. Make sure the operation does not affect services. 3. Execute the arp max-learning-number command to set a larger dynamic ARP learning limit for the device. Execute the arp max-learning-num command to set larger dynamic ARP learning limits for interfaces. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_USER_DUPLICATE_IPADDR_DETECT
|
Message text |
Detected a user IP 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 IP address [IPADDR]. |
|
Variable fields |
$1: New user's MAC address. $2: Outer VLAN where the new user resides. $3: Inner VLAN where the new user resides. $4: Name of the interface connecting to the new user. $5: Old user's MAC address. $6: Outer VLAN where the old user resides. $7: Inner VLAN where the old user resides. $8: Name of the interface connecting to the old user. $9: IP address of the endpoint user. |
|
Severity level |
6 (Informational) |
|
Example |
ARP/6/ARP_USER_DUPLICATE_IPADDR_DETECT: Detected a user IP 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 IP address 192.168.1.1. |
|
Impact |
Possible conflicting IP addresses in the network, which may cause user service or traffic disruption and other faults |
|
Cause |
New user's IP address is the same as an old user's IP address |
|
Recommended action |
Check all terminal user IP addresses, adjust conflicting user IP addresses, and resolve IP address conflict issues |
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: Move user's IP address. $2: Move user's MAC address. $3: Interface name before migration. $4: ID of the outer VLAN where the user resides before migration. $5: ID of the inner VLAN where the user resides before migration. $6: Interface name after migration. $7: ID of the outer VLAN where the user resides after migration. $8: ID of the inner VLAN where the user resides after migration. |
|
Severity level |
6 (Informational) |
|
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. |
|
Impact |
User services might be interrupted. When a large number of user migration operations occur, it may reduce device performance. |
|
Cause |
After enabling the ARP record terminal user port migration function, the terminal user undergoes interface migration actions |
|
Recommended action |
1. Use the display arp user-move record command to view the terminal user migration information and check whether the migration is reasonable 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
ARP/6/DUPIFIP: Duplicate address 1.1.1.1 on interface Ethernet1/1/1, sourced from 0015-E944-A947. |
|
Impact |
User services might be interrupted. |
|
Cause |
There are other devices in the network configured with the same IP address as the IP address of this interface |
|
Recommended action |
1. Identify whether another device in the network has the same IP address as the interface, and edit the IP addresses to ensure no address conflict exists. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
ARP/6/DUPIP: IP address 30.1.1.1 conflicted with global or imported IP address, sourced from 0000-0000-0001. |
|
Impact |
User services might be interrupted. |
|
Cause |
There are other devices in the network with the same IP address as the global or imported IP address of this device |
|
Recommended action |
1. Identify whether another device in the network has the same IP address as the device, and edit the IP addresses to ensure no address conflict exists. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
ARP/6/DUPVRRPIP: IP address 1.1.1.1 conflicted with VRRP virtual IP address on interface Ethernet1/1/1, sourced from 0015-E944-A947. |
|
Impact |
User services might be interrupted. |
|
Cause |
There are other devices in the network configured with the same IP address as the VRRP virtual IP address of this device |
|
Recommended action |
1. Identify whether there are other devices in the network configured with the same IP address as the VRRP virtual IP address of this device, and adjust the IP address of the conflicting device 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
L3_COMMON
|
Message text |
Pattern 1: The Board on slot [INT32] doesn't support the ARP safe-guard function. Pattern 2: The Board on chassis [INT32] slot [INT32] doesn't support the ARP safe-guard function. |
|
Variable fields |
Pattern 1: $1: Slot number. Pattern 2: $1: Chassis number. $2: Slot number. |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/L3_COMMON: -MDC=1-Slot=5; The Board on slot 5 doesn't support the ARP safe-guard function. |
|
Impact |
The system cannot address ARP attacks that consume traffic. |
|
Cause |
Pattern 1: The slot did not support the ARP safe-guard feature. Pattern 2: The slot of the chassis did not support the ARP safe-guard feature. |
|
Recommended action |
Use a card that supports the ARP safe-guard feature. |
ATK
This section contains ATK messages.
ATK_ICMP_ADDRMASK_REQ
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_ADDRMASK_REQ: IcmpType(1058)=17; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP address mask request packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_ADDRMASK_REQ_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_ADDRMASK_REQ_RAW: IcmpType(1058)=17; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP address mask requests of the same attributes, this message is sent only when the first request is received. If log aggregation is disabled, this message is sent every time an ICMP address mask request is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_ADDRMASK_RPL
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_ADDRMASK_RPL: IcmpType(1058)=18; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP address mask reply packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_ADDRMASK_RPL_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_ADDRMASK_RPL_RAW: IcmpType(1058)=18; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP address mask replies of the same attributes, this message is sent only when the first reply is received. If log aggregation is disabled, this message is sent every time an ICMP address mask reply is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_ECHO_REQ
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_ECHO_REQ: IcmpType(1058)=8; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP echo request packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_ECHO_REQ_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1004)=[UINT16]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: Destination port. $7: VPN instance name. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_ECHO_REQ_RAW: IcmpType(1058)=8; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; DstPort(1004)=22; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP echo requests of the same attributes, this message is sent only when the first request is received. If log aggregation is disabled, this message is sent every time an ICMP echo request is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_ECHO_RPL
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_ECHO_RPL: IcmpType(1058)=0; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP echo reply packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_ECHO_RPL_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_ECHO_RPL_RAW: IcmpType(1058)=0; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP echo replies of the same attributes, this message is sent only when the first reply is received. If log aggregation is disabled, this message is sent every time an ICMP echo reply is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of ICMP packets with the specified destination address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the ICMP flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_INFO_REQ
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_INFO_REQ: IcmpType(1058)=15; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP information request packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_INFO_REQ_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_INFO_REQ_RAW: IcmpType(1058)=15; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP information requests of the same attributes, this message is sent only when the first request is received. If log aggregation is disabled, this message is sent every time an ICMP information request is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_INFO_RPL
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_INFO_RPL: IcmpType(1058)=16; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP information reply packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_INFO_RPL_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_INFO_RPL_RAW: IcmpType(1058)=16; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP information replies of the same attributes, this message is sent only when the first reply is received. If log aggregation is disabled, this message is sent every time an ICMP information reply is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_LARGE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_LARGE: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of large ICMP packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_LARGE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_LARGE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for large ICMP packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a large ICMP packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_PARAPROBLEM
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_PARAPROBLEM: IcmpType(1058)=12; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP parameter error packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_PARAPROBLEM_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_PARAPROBLEM_RAW: IcmpType(1058)=12; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP parameter error packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMP parameter error packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_PINGOFDEATH
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_PINGOFDEATH: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP packets larger than 65535 bytes with the MF flag set to 0 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_PINGOFDEATH_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_PINGOFDEATH_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for the ping of death attack. The attack uses ICMP packets larger than 65535 bytes with the MF flag set to 0. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_REDIRECT
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_REDIRECT: IcmpType(1058)=5; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP redirect packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_REDIRECT_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_REDIRECT_RAW: IcmpType(1058)=5; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP redirect packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMP redirect packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_SMURF
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_SMURF: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for ICMP echo requests whose destination IP address is one of the following addresses: · A broadcast or network address of A, B, or C class. · An IP address of D or E class. · The broadcast or network address of the network where the receiving interface resides. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_SMURF_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_SMURF_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for the smurf attack. The attack uses ICMP echo requests with the destination IP address being one of the following addresses: · A broadcast or network address of A, B, or C class. · An IP address of D or E class. · The broadcast or network address of the network where the receiving interface resides. If log aggregation is enabled, for requests of the same attributes, this message is sent only when the first request is received. If log aggregation is disabled, this message is sent every time a request is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_SOURCEQUENCH
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_SOURCEQUENCH: IcmpType(1058)=4; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP source quench packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_SOURCEQUENCH_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_SOURCEQUENCH_RAW: IcmpType(1058)=4; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP source quench packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMP source quench packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TIMEEXCEED
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_TIMEEXCEED: IcmpType(1058)=11; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP timeout packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TIMEEXCEED_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_TIMEEXCEED_RAW: IcmpType(1058)=11; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP timeout packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMP timeout packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TRACEROUTE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_TRACEROUTE: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with ICMP type 11 and code 0 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TRACEROUTE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMP_TRACEROUTE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this log is generated when the first packet with ICMP type 11 and code 0 is received. If log aggregation is disabled, this log is generated each time a packet with ICMP type 11 and code 0 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TSTAMP_REQ
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_TSTAMP_REQ: IcmpType(1058)=13; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP timestamp request packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TSTAMP_REQ_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_TSTAMP_REQ_RAW: IcmpType(1058)=13; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP timestamp requests of the same attributes, this message is sent only when the first request is received. If log aggregation is disabled, this message is sent every time an ICMP timestamp request is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TSTAMP_RPL
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_TSTAMP_RPL: IcmpType(1058)=14; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP timestamp reply packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TSTAMP_RPL_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_TSTAMP_RPL_RAW: IcmpType(1058)=14; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP timestamp replies of the same attributes, this message is sent only when the first reply is received. If log aggregation is disabled, this message is sent every time an ICMP timestamp reply is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TYPE
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_TYPE: IcmpType(1058)=38; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of user-defined ICMP packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_TYPE_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_TYPE_RAW: IcmpType(1058)=38; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for user-defined ICMP packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a user-defined ICMP packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_UNREACHABLE
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_UNREACHABLE: IcmpType(1058)=3; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011091319; EndTime_c(1012)=20131011091819; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP destination unreachable packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMP_UNREACHABLE_RAW
|
Message text |
IcmpType(1058)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMP type. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMP_UNREACHABLE_RAW: IcmpType(1058)=3; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP destination unreachable packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMP destination unreachable packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_DEST_UNREACH
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_DEST_UNREACH: Icmpv6Type(1059)=133; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 destination unreachable packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_DEST_UNREACH_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_DEST_UNREACH_RAW: Icmpv6Type(1059)=133; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 destination unreachable packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMPv6 destination unreachable packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_ECHO_REQ
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_ECHO_REQ: Icmpv6Type(1059)=128; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 echo request packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_ECHO_REQ_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_ECHO_REQ_RAW: Icmpv6Type(1059)=128; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 echo requests of the same attributes, this message is sent only when the first request is received. If log aggregation is disabled, this message is sent every time an ICMPv6 echo request is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_ECHO_RPL
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_ECHO_RPL: Icmpv6Type(1059)=129; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 echo reply packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_ECHO_RPL_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_ECHO_RPL_RAW: Icmpv6Type(1059)=129; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 echo replies of the same attributes, this message is sent only when the first reply is received. If log aggregation is disabled, this message is sent every time an ICMPv6 echo reply is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port number. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMPV6_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2002::2; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of ICMPv6 packets with the specified destination address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the ICMPv6 flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_GROUPQUERY
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_GROUPQUERY: Icmpv6Type(1059)=130; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 multicast listener query packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_GROUPQUERY_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_GROUPQUERY_RAW: Icmpv6Type(1059)=130; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 multicast listener query packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMPv6 multicast listener query packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_GROUPREDUCTION
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_GROUPREDUCTION: Icmpv6Type(1059)=132; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 multicast listener done packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_GROUPREDUCTION_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_GROUPREDUCTION_RAW: Icmpv6Type(1059)=132; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 multicast listener done packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMPv6 multicast listener done packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_GROUPREPORT
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_GROUPREPORT: Icmpv6Type(1059)=131; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 multicast listener report packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_GROUPREPORT_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_GROUPREPORT_RAW: Icmpv6Type(1059)=131; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 multicast listener report packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMPv6 multicast listener report packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_LARGE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMPV6_LARGE: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of large ICMPv6 packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_LARGE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMPV6_LARGE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for large ICMPv6 packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a large ICMPv6 packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_PACKETTOOBIG
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_PACKETTOOBIG: Icmpv6Type(1059)=136; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 packets too big exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_PACKETTOOBIG_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_PACKETTOOBIG_RAW: Icmpv6Type(1059)=136; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 packets too big of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMPv6 packet too big is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_PARAPROBLEM
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_PARAPROBLEM: Icmpv6Type(1059)=135; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 parameter error packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_PARAPROBLEM_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_PARAPROBLEM_RAW: Icmpv6Type(1059)=135; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 parameter error packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMPv6 parameter error packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_TIMEEXCEED
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_TIMEEXCEED: Icmpv6Type(1059)=134; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMPv6 timeout packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_TIMEEXCEED_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_TIMEEXCEED_RAW: Icmpv6Type(1059)=134; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMPv6 timeout packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMPv6 timeout packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_TRACEROUTE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMPV6_TRACEROUTE: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of ICMP type-3 packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_TRACEROUTE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_ICMPV6_TRACEROUTE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for ICMP type-3 packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an ICMP type-3 packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_TYPE
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_TYPE: Icmpv6Type(1059)=38; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011100935; EndTime_c(1012)=20131011101435; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of user-defined ICMPv6 packets exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_ICMPV6_TYPE_RAW
|
Message text |
Icmpv6Type(1059)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: ICMPv6 type. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_ICMPV6_TYPE_RAW: Icmpv6Type(1059)=38; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=5600::12; DstIPv6Addr(1037)=1200:0:3400:0:5600:0:7800:0; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for user-defined ICMPv6 packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a user-defined ICMPv6 packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP_OPTION
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. $9: Time when the attack started. $10: Time when the attack ended. $11: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IP_OPTION: IPOptValue(1057)=38; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131011063123; EndTime_c(1012)=20131011063623; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with a user-defined IP option exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP_OPTION_RAW
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IP_OPTION_RAW: IPOptValue(1057)=38; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for packets with a user-defined IP option of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet with a user-defined IP option is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_ACK_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_ACK_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of IPv4 ACK packets with the specified destination address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the ACK flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_DIS_PORTSCAN
|
Message text |
RcvIfName(1023)=[STRING]; Protocol(1001)=[STRING]; TcpFlag(1074)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Protocol name. $3: TCP type. This field is displayed only for TCP packets. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_DIS_PORTSCAN: RcvIfName(1023)=Ethernet0/0/2; Protocol(1001)=TCP; TcpFlag(1074)=[SYN]; DstIPAddr(1007)=6.1.1.5; RcvVPNInstance(1041)=vpn1; Action(1049)=logging,block-source; BeginTime_c(1011)=20131009052955. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when an IPv4 distributed port scan attack is detected. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_DNS_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_DNS_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of DNS query packets destined to specified IP address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the DNS flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_FIN_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_FIN_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of SYN-ACK packets destined to specified IP address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the FIN flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_FRAGMENT
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_FRAGMENT: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=TCP; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of IPv4 packets with an offset smaller than 5 but bigger than 0 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_FRAGMENT_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_FRAGMENT_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=TCP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this log is generated when the first IPv4 packet with an offset smaller than 5 but bigger than 0 is received. If log aggregation is disabled, this log is generated each time an IPv4 packet with an offset smaller than 5 but bigger than 0 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_HTTP_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_HTTP_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of HTTP Get packets destined to specified IP address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the HTTP flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_IMPOSSIBLE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_IMPOSSIBLE: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=TCP; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of IPv4 packets whose source IPv4 address is the same as the destination IPv4 address exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_IMPOSSIBLE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_IMPOSSIBLE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=TCP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for IPv4 packets whose source IPv4 address is the same as the destination IPv4 address of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an IPv4 packet whose source IPv4 address is the same as the destination IPv4 address is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_IPSWEEP
|
Message text |
RcvIfName(1023)=[STRING]; Protocol(1001)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Protocol name $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: VPN instance name. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_IPSWEEP: RcvIfName(1023)=Ethernet0/0/2; Protocol(1001)=TCP; SrcIPAddr(1003)=9.1.1.5; DSLiteTunnelPeer(1040)=--; RcvVPNInstance(1041)=vpn1; Action(1049)=logging,block-source; BeginTime_c(1011)=20131009060657. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when an IPv4 sweep attack is detected. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_PORTSCAN
|
Message text |
RcvIfName(1023)=[STRING]; Protocol(1001)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; RcvVPNInstance(1041)=[STRING]; DstIPAddr(1007)=[IPADDR]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Protocol name $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: VPN instance name. $6: Destination IP address. $7 Action type. $8: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_PORTSCAN: RcvIfName(1023)=Ethernet0/0/2; Protocol(1001)=TCP; SrcIPAddr(1003)=9.1.1.5; DSLiteTunnelPeer(1040)=--; RcvVPNInstance(1041)=vpn1; DstIPAddr(1007)=6.1.1.5; Action(1049)=logging,block-source; BeginTime_c(1011)=20131009052955. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when an IPv4 port scan attack is detected. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_RST_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_RST_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of IPv4 RST packets with the specified destination address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the RST flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_SYN_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_SYN_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of IPv4 SYN packets with the specified destination address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the SYN flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_SYNACK_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_SYNACK_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
The number of IPv4 SYN-ACK packets with the specified destination address within the specified time period exceeds the threshold. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the SYN-ACK flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_ALLFLAGS
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_ALLFLAGS: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of IPv4 TCP packets that have all flags set exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_ALLFLAGS_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_ALLFLAGS_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this log is generated when the first IPv4 TCP packet that has all flags set is received. If log aggregation is disabled, this log is generated each time an IPv4 TCP packet that has all flags set is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_FINONLY
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_FINONLY: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of IPv4 TCP packets that have the FIN flag set exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_FINONLY_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_FINONLY_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this log is generated when the first IPv4 TCP packet that has the FIN flag set is received. If log aggregation is disabled, this log is generated each time an IPv4 TCP packet that has the FIN flag set is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_INVALIDFLAGS
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_INVALIDFLAGS: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 TCP packets that have invalid flag settings. Invalid flag settings include: · The RST and FIN flags are both set. · The RST and SYN flags are both set. · The RST, FIN, and SYN flags are all set. · The PSH, RST, and FIN flags are all set. · The PSH, RST, and SYN flags are all set. · The PSH, RST, SYN, and FIN flags are all set. · The ACK, RST, and FIN flags are all set. · The ACK, RST, and SYN flags are all set. · The ACK, RST, SYN, and FIN flags are all set. · The ACK, PSH, SYN, and FIN flags are all set. · The ACK, PSH, RST, and FIN flags are all set. · The ACK, PSH, RST, and SYN flags are all set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_INVALIDFLAGS_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_INVALIDFLAGS_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv4 TCP packets that have invalid flag settings. Invalid flag settings include: · The RST and FIN flags are both set. · The RST and SYN flags are both set. · The RST, FIN, and SYN flags are all set. · The PSH, RST, and FIN flags are all set. · The PSH, RST, and SYN flags are all set. · The PSH, RST, SYN, and FIN flags are all set. · The ACK, RST, and FIN flags are all set. · The ACK, RST, and SYN flags are all set. · The ACK, RST, SYN, and FIN flags are all set. · The ACK, PSH, SYN, and FIN flags are all set. · The ACK, PSH, RST, and FIN flags are all set. · The ACK, PSH, RST, and SYN flags are all set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_LAND
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_LAND: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 TCP packets whose source IP address is the same as the destination IP address. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_LAND_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_LAND_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for the IPv4 land attack. The attack uses IPv4 TCP packets whose source IP address is the same as the destination IP address. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_NULLFLAG
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_NULLFLAG: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=4. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 TCP packets that have no flag set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_NULLFLAG_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_NULLFLAG_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv4 TCP packets that have no flag set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_SYNFIN
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_SYNFIN: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 TCP packets that have SYN and FIN flags set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_SYNFIN_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_SYNFIN_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv4 TCP packets that have SYN and FIN flags set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_WINNUKE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_WINNUKE: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=5. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 TCP packets with destination port 139, the URG flag set, and a nonzero Urgent Pointer. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TCP_WINNUKE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TCP_WINNUKE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for the IPv4 WinNuke attack. The attack uses IPv4 TCP packets with destination port 139, the URG flag set, and a nonzero Urgent Pointer. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TEARDROP
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TEARDROP: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=TCP; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 overlapping fragments. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TEARDROP_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TEARDROP_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=TCP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for IPv4 overlapping fragments of the same attributes, this message is sent only when the first overlapping fragment is received. If log aggregation is disabled, this message is sent every time an IPv4 overlapping fragment is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TINY_FRAGMENT
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TINY_FRAGMENT: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=TCP; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=6. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 packets with a datagram smaller than 68 bytes and the MF flag set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_TINY_FRAGMENT_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_TINY_FRAGMENT_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=TCP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for the IPv4 tiny fragment attack. The attack uses IPv4 packets with a datagram smaller than 68 bytes and the MF flag set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_UDP_BOMB
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_UDP_BOMB: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 UDP packets in which the length value in the IP header is larger than the IP header length plus the length in the UDP header. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_UDP_BOMB_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_UDP_BOMB_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv4 UDP bomb attack. The attack uses IPv4 UDP packets in which the length value in the IP header is larger than the IP header length plus the length in the UDP header. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_UDP_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPAddr(1007)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IP address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_UDP_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPAddr(1007)=6.1.1.5; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009093351. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv4 UDP packets sent to a destination per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the UDP flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_UDP_FRAGGLE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_UDP_FRAGGLE: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=11. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 UDP packets with source port 7 and destination port 19. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_UDP_FRAGGLE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_UDP_FRAGGLE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv4 UDP fraggle attack. The attack uses IPv4 UDP packets with source port 7 and destination port 19. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_UDP_SNORK
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_UDP_SNORK: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131011074913; EndTime_c(1012)=20131011075413; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv4 UDP packets with source port 7, 19, or 135, and destination port 135. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP4_UDP_SNORK_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP4_UDP_SNORK_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv4 UDP snork attack. The attack uses IPv4 UDP packets with source port 7, 19, or 135, and destination port 135. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_ACK_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_ACK_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2::2; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009100434. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv6 ACK packets sent to a destination per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the ACK flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_DIS_PORTSCAN
|
Message text |
RcvIfName(1023)=[STRING]; Protocol(1001)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Protocol name $3: Destination IPv6 address. $4: VPN instance name. $5: Action type. $6: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_DIS_PORTSCAN: RcvIfName(1023)=Ethernet0/0/2; Protocol(1001)=UDP; DstIPv6Addr(1037)=2::2; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009100928. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when an IPv6 distributed port scan attack is detected. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_DNS_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_DNS_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2::2; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009100434. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv6 DNS queries sent to a destination per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the DNS flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_FIN_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_FIN_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2::2; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009100434. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv6 SYN+ACK packets sent to a destination per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the FIN flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_FRAGMENT
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Protocol type. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_FRAGMENT: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=1::1; RcvVPNInstance(1041)=--; Protocol(1001)=IPv6-ICMP; Action(1049)=logging; BeginTime_c(1011)=20131011103335; EndTime_c(1012)=20131011103835; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 packets with an offset smaller than 5 but bigger than 0. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_FRAGMENT_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Protocol name $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_FRAGMENT_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=1::1; RcvVPNInstance(1041)=--; Protocol(1001)=IPv6-ICMP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for the IPv6 fragment attack. The attack uses IPv6 packets with an offset smaller than 5 but bigger than 0. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_HTTP_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_HTTP_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2::2; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009100434. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv6 HTTP Get packets sent to a destination per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the HTTP flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_IMPOSSIBLE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Protocol type. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_IMPOSSIBLE: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=1::1; RcvVPNInstance(1041)=--; Protocol(1001)=IPv6-ICMP; Action(1049)=logging; BeginTime_c(1011)=20131011103335; EndTime_c(1012)=20131011103835; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 packets whose source IPv6 address is the same as the destination IPv6 address. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_IMPOSSIBLE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Protocol name $6: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_IMPOSSIBLE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=1::1; RcvVPNInstance(1041)=--; Protocol(1001)=IPv6-ICMP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, for IPv6 packets whose source IPv6 address is the same as the destination IPv6 address of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an IPv6 packet whose source IPv6 address is the same as the destination IPv6 address is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_IPSWEEP
|
Message text |
RcvIfName(1023)=[STRING]; Protocol(1001)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Protocol name $3: Source IPv6 address. $4: VPN instance name. $5: Action type. $6: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_IPSWEEP: RcvIfName(1023)=Ethernet0/0/2; Protocol(1001)=UDP; SrcIPv6Addr(1036)=1::5; RcvVPNInstance(1041)=--; Action(1049)=logging,block-source; BeginTime_c(1011)=20131009100639. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when an IPv6 sweep attack is detected. |
|
Recommended action |
Verify that the packet drop action is configured in the attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_PORTSCAN
|
Message text |
RcvIfName(1023)=[STRING]; Protocol(1001)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Protocol name $3: Source IPv6 address. $4: VPN instance name. $5: Destination IPv6 address. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_PORTSCAN: RcvIfName(1023)=Ethernet0/0/2; Protocol(1001)=UDP; SrcIPv6Addr(1036)=1::5; RcvVPNInstance(1041)=--; DstIPv6Addr(1037)=2::2; Action(1049)=logging,block-source; BeginTime_c(1011)=20131009100455. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when an IPv6 port scan attack is detected. |
|
Recommended action |
Verify that the packet drop action is configured in the attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_RST_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_RST_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2::2; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009100434. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv6 RST packets sent to a destination per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the RST flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_SYN_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_SYN_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2::2; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009100434. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv6 SYN packets sent to a destination per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the SYN flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_SYNACK_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_SYNACK_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2::2; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009100434. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv6 SYN-ACK packets sent to a destination per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the SYN flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_ALLFLAGS
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_ALLFLAGS: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 TCP packets that have all flags set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_ALLFLAGS_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_ALLFLAGS_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=2000::1; DstIPv6Addr(1037)=2003::200; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv6 TCP packets that have all flags set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_FINONLY
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_FINONLY: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 TCP packets that have only the FIN flag set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_FINONLY_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_FINONLY_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=2000::1; DstIPv6Addr(1037)=2003::200; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv6 TCP packets that have only the FIN flag set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_INVALIDFLAGS
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_INVALIDFLAGS: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 TCP packets that have invalid flag settings. Invalid flag settings include: · The RST and FIN flags are both set. · The RST and SYN flags are both set. · The RST, FIN, and SYN flags are all set. · The PSH, RST, and FIN flags are all set. · The PSH, RST, and SYN flags are all set. · The PSH, RST, SYN, and FIN flags are all set. · The ACK, RST, and FIN flags are all set. · The ACK, RST, and SYN flags are all set. · The ACK, RST, SYN, and FIN flags are all set. · The ACK, PSH, SYN, and FIN flags are all set. · The ACK, PSH, RST, and FIN flags are all set. · The ACK, PSH, RST, and SYN flags are all set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_INVALIDFLAGS_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_INVALIDFLAGS_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=2000::1; DstIPv6Addr(1037)=2003::200; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv6 TCP packets that have invalid flag settings. Invalid flag settings include: · The RST and FIN flags are both set. · The RST and SYN flags are both set. · The RST, FIN, and SYN flags are all set. · The PSH, RST, and FIN flags are all set. · The PSH, RST, and SYN flags are all set. · The PSH, RST, SYN, and FIN flags are all set. · The ACK, RST, and FIN flags are all set. · The ACK, RST, and SYN flags are all set. · The ACK, RST, SYN, and FIN flags are all set. · The ACK, PSH, SYN, and FIN flags are all set. · The ACK, PSH, RST, and FIN flags are all set. · The ACK, PSH, RST, and SYN flags are all set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_LAND
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_LAND: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 TCP packets whose source IPv6 address is the same as the destination IPv6 address. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_LAND_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_LAND_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=2000::1; DstIPv6Addr(1037)=2003::200; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for the IPv6 land attack. The attack uses IPv6 TCP packets whose source IPv6 address is the same as the destination IPv6 address. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_NULLFLAG
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_NULLFLAG: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 TCP packets that have no flag set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_NULLFLAG_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_NULLFLAG_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=2000::1; DstIPv6Addr(1037)=2003::200; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv6 TCP packets that have no flag set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_SYNFIN
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_SYNFIN: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 TCP packets that have SYN and FIN flags set. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_SYNFIN_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_SYNFIN_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=2000::1; DstIPv6Addr(1037)=2003::200; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv6 TCP packets that have SYN and FIN flags set. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_WINNUKE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_WINNUKE: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when logs are aggregated for IPv6 TCP packets with destination port 139, the URG flag set, and a nonzero Urgent Pointer. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_TCP_WINNUKE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_TCP_WINNUKE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for the IPv6 WinNuke attack. The attack uses IPv6 TCP packets with destination port 139, the URG flag set, and a nonzero Urgent Pointer. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_UDP_FLOOD
|
Message text |
RcvIfName(1023)=[STRING]; DstIPv6Addr(1037)=[IPADDR]; DstPort(1008)=[UINT16]; RcvVPNInstance(1041)=[STRING]; UpperLimit(1048)=[UINT32]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Destination IPv6 address. $3: Destination port. $4: VPN instance name. $5: Upper rate limit. $6: Action type. $7: Time when the attack started. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_UDP_FLOOD: RcvIfName(1023)=Ethernet0/0/2; DstIPv6Addr(1037)=2::2; DstPort(1008)=22; RcvVPNInstance(1041)=--; UpperLimit(1048)=10; Action(1049)=logging; BeginTime_c(1011)=20131009100434. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is sent when the number of IPv6 UDP packets with the specified destination address per second exceeds the rate limit. |
|
Recommended action |
Identify whether the packets are attack packets. If they are not attack packets, adjust the threshold. If they are attack packets, verify that the packet drop action is configured in the UDP flood attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_UDP_FRAGGLE
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_UDP_FRAGGLE: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of IPv6 UDP packets with a source port number of 7 and a destination port number of 19 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_UDP_FRAGGLE_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_UDP_FRAGGLE_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this log is generated when the first IPv6 UDP packet with a source port number of 7 and a destination port number of 19 is received. If log aggregation is disabled, this log is generated each time an IPv6 UDP packet with a source port number of 7 and a destination port number of 19 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_UDP_SNORK
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_UDP_SNORK: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of IPv6 UDP packets with a source port number of 7, 19, or 135 and a destination port number of 135 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IP6_UDP_SNORK_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: VPN instance name. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IP6_UDP_SNORK_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
This message is for IPv6 UDP snork attack. The attack uses IPv6 UDP packets with source port 7, 19, or 135, and destination port 135. If log aggregation is enabled, for packets of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time a packet is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_ABNORMAL
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. $8: Time when the attack started. $9: Time when the attack ended. $10: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IPOPT_ABNORMAL: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131011072002; EndTime_c(1012)=20131011072502; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with more than two IP options exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_ABNORMAL_RAW
|
Message text |
RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IP address. $3: IP address of the peer DS-Lite tunnel interface. $4: Destination IP address. $5: VPN instance name. $6: Protocol type. $7: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IPOPT_ABNORMAL_RAW: RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this message is generated when the first packet with more than two IP options is received. If log aggregation is disabled, this message is generated each time a packet with more than two IP options is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_LOOSESRCROUTE
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)= [UINT32]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. $9: Time when the attack started. $10: Time when the attack ended. $11: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_LOOSESRCROUTE: IPOptValue(1057)=131; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131011063123; EndTime_c(1012)=20131011063623; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with IP option 131 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_LOOSESRCROUTE_RAW
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_LOOSESRCROUTE_RAW: IPOptValue(1057)=131; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this message is generated when the first packet with IP option 131 is received. If log aggregation is disabled, this message is generated each time a packet with IP option 131 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_RECORDROUTE
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. $9: Time when the attack started. $10: Time when the attack ended. $11: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_RECORDROUTE: IPOptValue(1057)=7; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131011063123; EndTime_c(1012)=20131011063623; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with IP option 7 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_RECORDROUTE_RAW
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_RECORDROUTE_RAW: IPOptValue(1057)=7; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this message is generated when the first packet with IP option 7 is received. If log aggregation is disabled, this message is generated each time a packet with IP option 7 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_ROUTEALERT
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. $9: Time when the attack started. $10: Time when the attack ended. $11: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_ROUTEALERT: IPOptValue(1057)=148; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131011063123; EndTime_c(1012)=20131011063623; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with IP option 148 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_ROUTEALERT_RAW
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_ROUTEALERT_RAW: IPOptValue(1057)=148; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this message is generated when the first packet with IP option 148 is received. If log aggregation is disabled, this message is generated each time a packet with IP option 148 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_SECURITY
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. $9: Time when the attack started. $10: Time when the attack ended. $11: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_SECURITY: IPOptValue(1057)=130; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131009091022; EndTime_c(1012)=20131009091522; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with IP option 130 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_SECURITY_RAW
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_SECURITY_RAW: IPOptValue(1057)=130; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this message is generated when the first packet with IP option 130 is received. If log aggregation is disabled, this message is generated each time a packet with IP option 130 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_STREAMID
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. $9: Time when the attack started. $10: Time when the attack ended. $11: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_STREAMID: IPOptValue(1057)=136; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131011063123; EndTime_c(1012)=20131011063623; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with IP option 136 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_STREAMID_RAW
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_STREAMID_RAW: IPOptValue(1057)=136; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this message is generated when the first packet with IP option 136 is received. If log aggregation is disabled, this message is generated each time a packet with IP option 136 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_STRICTSRCROUTE
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. $9: Time when the attack started. $10: Time when the attack ended. $11: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_STRICTSRCROUTE: IPOptValue(1057)=137; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131011063123; EndTime_c(1012)=20131011063623; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with IP option 137 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_STRICTSRCROUTE_RAW
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_STRICTSRCROUTE_RAW: IPOptValue(1057)=137; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this message is generated when the first packet with IP option 137 is received. If log aggregation is disabled, this message is generated each time a packet with IP option 137 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_TIMESTAMP
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. $9: Time when the attack started. $10: Time when the attack ended. $11: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_TIMESTAMP: IPOptValue(1057)=68; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging; BeginTime_c(1011)=20131011063123; EndTime_c(1012)=20131011063623; AtkTimes(1050)=3. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of packets with IP option 68 exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPOPT_TIMESTAMP_RAW
|
Message text |
IPOptValue(1057)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPAddr(1003)=[IPADDR]; DSLiteTunnelPeer(1040)=[STRING]; DstIPAddr(1007)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Protocol(1001)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IP option. $2: Ingress interface name. $3: Source IP address. $4: IP address of the peer DS-Lite tunnel interface. $5: Destination IP address. $6: VPN instance name. $7: Protocol type. $8: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPOPT_TIMESTAMP_RAW: IPOptValue(1057)=68; RcvIfName(1023)=Ethernet0/0/2; SrcIPAddr(1003)=9.1.1.1; DSLiteTunnelPeer(1040)=--; DstIPAddr(1007)=6.1.1.1; RcvVPNInstance(1041)=--; Protocol(1001)=RAWIP; Action(1049)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this message is generated when the first packet with IP option 68 is received. If log aggregation is disabled, this message is generated each time a packet with IP option 68 is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPV6_EXT_HEADER
|
Message text |
IPv6ExtHeader(1060)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]; BeginTime_c(1011)=[STRING]; EndTime_c(1012)=[STRING]; AtkTimes(1050)=[UINT32]. |
|
Variable fields |
$1: IPv6 extension header value. $2: Ingress interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: Name of the VPN instance to which the ingress interface belongs. $6: Action type. $7: Time when the attack started. $8: Time when the attack ended. $9: Number of attacks. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPV6_EXT_HEADER: IPv6ExtHeader(1060)=43; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging; BeginTime_c(1011)=20131009103631; EndTime_c(1012)=20131009104131; AtkTimes(1050)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
Log aggregation is enabled, and the number of IPv6 packets with a user-defined extension header exceeds one. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPV6_EXT_HEADER_ABNORMAL
|
Message text |
RcvIfName(1023)=[STRING];SrcIPv6Addr(1036)=[IPADDR];DstIPv6Addr(1037)=[IPADDR];RcvVPNInstance(1042)=[STRING];Action(1053)=[STRING];BeginTime_c(1011)=[STRING];EndTime_c(1012)=[STRING];AtkTimes(1054)=[UINT32]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. $6: Time when the attack started. $7: Time when the attack ended. $8: Number of attacks. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IPV6_EXT_HEADER_ABNORMAL: RcvIfName(1023)=Ethernet0/0/2;SrcIPv6Addr(1036)=1::1;DstIPv6Addr(1037)=2::11;RcvVPNInstance(1042)=--;Action(1053)=logging;BeginTime_c(1011)=20131009103631;EndTime_c(1012)=20131009104131;AtkTimes(1054)=2. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is enabled, this log is generated when the number of extension headers exceeds the upper limit or more than one IPv6 packet has a non-duplicable extension header. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPV6_EXT_HEADER_ABNORMAL_RAW
|
Message text |
RcvIfName(1023)=[STRING];SrcIPv6Addr(1036)=[IPADDR];DstIPv6Addr(1037)=[IPADDR];RcvVPNInstance(1042)=[STRING];Action(1053)=[STRING]. |
|
Variable fields |
$1: Ingress interface name. $2: Source IPv6 address. $3: Destination IPv6 address. $4: Name of the VPN instance to which the ingress interface belongs. $5: Action type. |
|
Severity level |
3 (Error) |
|
Example |
ATK/3/ATK_IPV6_EXT_HEADER_RAW: RcvIfName(1023)=Ethernet0/0/2;SrcIPv6Addr(1036)=1::1;DstIPv6Addr(1037)=2::11;RcvVPNInstance(1042)=--;Action(1053)=logging. |
|
Impact |
Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
If log aggregation is disabled, the message is sent every time the device receives an abnormal IPv6 packet in which the number of extension headers exceeds the specified upper limit. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATK_IPV6_EXT_HEADER_RAW
|
Message text |
IPv6ExtHeader(1060)=[UINT32]; RcvIfName(1023)=[STRING]; SrcIPv6Addr(1036)=[IPADDR]; DstIPv6Addr(1037)=[IPADDR]; RcvVPNInstance(1041)=[STRING]; Action(1049)=[STRING]. |
|
Variable fields |
$1: IPv6 extension header value. $2: Receiving interface name. $3: Source IPv6 address. $4: Destination IPv6 address. $5: VPN instance name. $6: Action type. |
|
Severity level |
5 (Notification) |
|
Example |
ATK/5/ATK_IPV6_EXT_HEADER_RAW: IPv6ExtHeader(1060)=43; RcvIfName(1023)=Ethernet0/0/2; SrcIPv6Addr(1036)=1::1; DstIPv6Addr(1037)=2::11; RcvVPNInstance(1041)=--; Action(1049)=logging. |
|
Cause |
If log aggregation is enabled, for IPv6 packets with a user-defined extension header and of the same attributes, this message is sent only when the first packet is received. If log aggregation is disabled, this message is sent every time an IPv6 packet with a user-defined extension header is received. |
|
Recommended action |
Verify that the packet drop action is configured in the single-packet attack defense policy. For more information, see the attack detection and prevention configuration guide. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATM
This section contains ATM messages.
ATM_PVCDOWN
|
Message text |
|
|
Variable fields |
|
|
Severity level |
|
|
Example |
ATM/5/ATM_PVCDOWN: Interface ATM2/0/2 PVC 0/100 status is down. |
|
Impact |
The PVC-based ATM feature is unavailable. |
|
Cause |
· The ATM interface to which the PVC belongs went down. · The OAM state of the PVC became down. · The PVC had been manually shut down. |
|
Recommended action |
Use the display atm pvc-info command to display detailed information about the PVC and take relevant actions: 1. If the interface state is down, take the following actions: ¡ Make sure both the local and remote ATM interfaces are up by using the display interface atm command. If the interfaces have been manually shut down, execute the undo shutdown command in interface view to bring them up. ¡ Make sure the two interfaces are correctly connected. 2. If the OAM state is down, take the following actions: ¡ Make sure the VPI/VCI value of the remote PVC is the same as the VPI/VCI value of the local PVC. ¡ Make sure the OAM configuration of the remote PVC is consistent with the OAM configuration of the local PVC. For example, if one end is configured as the OAM CC cell sink, the other end must be configured as the OAM CC cell source. ¡ Make sure the remote PVC is up. If the remote PVC has been manually shut down, execute the undo shutdown command in PVC view to bring it up. ¡ Make sure the two ends are correctly connected. ¡ If the two routers are connected through an ATM network, in addition to the previous check items, you must check the forwarding rule of the ATM network. If the ATM network cannot reach the PVC, the PVC cannot come up. 3. If the PVC state is down, check if the local PVC has been manually shut down. To bring up the PVC, execute the undo shutdown command in PVC view. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
ATM_PVCUP
|
Message text |
|
|
Variable fields |
|
|
Severity level |
|
|
Example |
|
|
Impact |
The PVC-based ATM feature is recovered. |
|
Cause |
The ATM interface to which the PVC belongs became up. The OAM state for the PVC became up. The PVC was shut down by using the undo shutdown command. |
|
Recommended action |
No action is required. |
BFD messages
This section contains BFD messages.
BFDMAD_PORT_CONFLICT
|
Message text |
Interface [STRING] has been configured as a dedicated BFD MAD port. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 (Notification) |
|
Example |
BFD/5/BFDMAD_PORT_CONFLICT: -MDC=1-Chassis=1-Slot=9; Interface XGE1/9/2/2 has been configured as a dedicated BFD MAD port. |
|
Impact |
No negative impact on the system. |
|
Cause |
In an IRF fabric, a card can have only one dedicated BFD MAD port if IRF physical interfaces exist on the card. |
|
Recommended action |
No action is required. |
BFD_NORESOURCE
|
Message text |
No hardware resource for session LD [INT32]. |
|
Variable fields |
$1: BFD local identifier. |
|
Severity level |
5 (Notification) |
|
Example |
BFD/5/BFD_NORESOURCE: -Slot=8; No hardware resource for session LD [1]. |
|
Impact |
New hardware BFD sessions and CFD sessions cannot be created. |
|
Cause |
Hardware BFD resources are insufficient. |
|
Recommended action |
1. Use the display resource-monitor command to view the resource usage of hard_bfd_counter_resource in the corresponding slot. 2. Identify whether the BFD or CFD service quantity exceeds the total amount of resources. 3. Release unnecessary BFD or CFD services. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BFD messages
This section contains BFD messages.
BFD_CHANGE_FSM (Severity 4)
|
Message text |
Sess[STRING], Ver:[UINT32], 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: BFD version. Options are 0 and 1. $3: Session state before changing. Options are INIT, UP, ADMIN-DOWN, DOWN, and FAIL. $4: Session state after changing. Options are UP and DOWN. $5: Diagnostic information: · 0 (No Diagnostic)—The BFD session is in up state. · 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 |
4 (Warning) |
|
Example |
BFD/4/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/4/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/4/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/4/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). |
|
Impact |
· If the session transitions from a non-down state to down, an abnormal session state occurs, which might impact the upper-level service associated with the session. · If the session transitions from a non-up state to up, the session state recovers, and the associated service also recovers. · If the session transitions from Down to Init, or transitions from Down/Init/Up to AdminDown, the associated service is not impacted. · If alarm is turned on, a large number of session state changes might result in a high CPU usage. |
|
Cause |
If the BFD session transitions to Up from another state, possible reasons for this message include: · When the BFD session is created or recovers from a failure, the BFD session transitions from Down to Up state. · When the BFD session is created or recovers from a failure, the BFD session transitions from Init to Up state. · When BFD configuration changes, the BFD session transitions from AdminDown to Up state. If the BFD session transitions from Up to another state, possible reasons for this message include: · The path detected by the BFD session becomes faulty, resulting in a BFD packet exchange failure. · The session-associated interface goes down. · The session-associated BFD session transitions to Down state. · The peer session is shut down or deleted. If the BFD session transitions to AdminDown from another state, possible reason for this message is that the session has been deleted. |
|
Recommended action |
1. If the session state is not Down, no action is required. 2. If the BFD session transitions to Down from another state, proceed to step 3. 3. Use the display interface interface-type interface-number command to identify whether the physical state of the session-associated interface is Up. ¡ If the interface is Up, proceed to step 4. ¡ If the interface is not Up, identify whether the physical link is normal (whether the hardware, such as network cable and transceiver module, is loose or falls off). If such a case exists, connect the physical link correctly again, and then use the display bfd session command to view the session state. If the State field of the session is still not Up, proceed to step 4. 4. Use the display bfd session command at both ends to identify whether the BFD session is removed. ¡ If the BFD session is removed, correctly configure the BFD session at both ends, and then use the display bfd session command to view the session state. If the State field of the session is still not Up, proceed to step 5. ¡ If the BFD session is not removed, proceed to step 5. 5. Use the ping command to identify whether the link detected by the BFD session can correctly forward packets. ¡ If session cannot correctly forward packets, identify whether the link is faulty, and routes are correctly deployed. You can deploy the forwarding path again, and then use the display bfd session command to view the session state. If the State field of the session is still not Up, proceed to step 6. ¡ If session can correctly forward packets, proceed to step 6. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BFD_CHANGE_FSM (Severity 5)
|
Message text |
Sess[STRING], Ver:[UINT32], 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: BFD version. Options are 0 and 1. $3: Session state before changing. Options are INIT, UP, ADMIN-DOWN, and DOWN. $4: Session state after changing. Options are INIT, DOWN, and FAIL. $5: Diagnostic information: · 0 (No Diagnostic)—The BFD session is in up state. · 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 (Notification) |
|
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: DOWN->INIT, 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: DOWN->INIT, 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: DOWN->INIT, 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: DOWN->INIT, Diag: 0 (No Diagnostic). |
|
Impact |
· If the session transitions from a non-down state to down, an abnormal session state occurs, which might impact the upper-level service associated with the session. · If the session transitions from a non-up state to up, the session state recovers, and the associated service also recovers. · If the session transitions from Down to Init, or transitions from Down/Init/Up to AdminDown, the associated service is not impacted. |
|
Cause |
If the BFD session transitions to Up from another state, possible reasons for this message include: · When the BFD session is created or recovers from a failure, the BFD session transitions from Down to Up state. · When the BFD session is created or recovers from a failure, the BFD session transitions from Init to Up state. · When BFD configuration changes, the BFD session transitions from AdminDown to Up state. If the BFD session transitions from Up to another state, possible reasons for this message include: · The path detected by the BFD session becomes faulty, resulting in a BFD packet exchange failure. · The session-associated interface goes down. · The session-associated BFD session transitions to Down state. · The peer session is shut down or deleted. If the BFD session transitions to AdminDown from another state, possible reason for this message is that the session has been deleted. |
|
Recommended action |
1. If the session state is not Down, no action is required. 2. If the BFD session transitions to Down from another state, proceed to step 3. 3. Use the display interface interface-type interface-number command to identify whether the physical state of the session-associated interface is Up. ¡ If session can correctly forward packets, proceed to step 4. ¡ If the interface is not Up, identify whether the physical link is normal (whether the hardware, such as network cable and transceiver module, is loose or falls off). If such a case exists, connect the physical link correctly again, and then use the display bfd session command to view the session state. If the State field of the session is still not Up, proceed to step 4. 4. Use the display bfd session command at both ends to identify whether the BFD session is removed. ¡ If the BFD session is removed, correctly configure the BFD session at both ends, and then use the display bfd session command to view the session state. If the State field of the session is still not Up, proceed to step 5. ¡ If the BFD session is not removed, proceed to step 5. 5. Use the ping command to identify whether the link detected by the BFD session can correctly forward packets. ¡ If session cannot correctly forward packets, identify whether the link is faulty, and routes are correctly deployed. You can deploy the forwarding path again, and then use the display bfd session command to view the session state. If the State field of the session is still not Up, proceed to step 6. ¡ If session can correctly forward packets, proceed to step 6. 6. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
BFD_CHANGE_SESS
|
Message text |
Sess[STRING], Ver:[UNIT32], 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: BFD version. Options are 0 and 1. $3: Session state. Supported value is Deleted. $4: Diagnostic information: · 0 (No Diagnostic)—The BFD session is in up state. · 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 (Notification) |
|
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 (Administratively Down) |
|
Impact |
If a user actively deletes the association between the upper-layer protocol and BFD, resulting in the deletion of the BFD session, the system will not be impacted. Except from the previous situation, the deletion of a BFD session is considered abnormal and might be caused by a fault in the upper-layer protocol. |
|
Cause |
The BFD session is deleted. |
|
Recommended action |
1. Execute the display current-configuration command to identify whether the configuration of collaboration between an upper-layer protocol and BFD exists. ¡ If such a collaboration configuration exists, proceed to step 2. ¡ If the collaboration configuration does not exist, and the diagnostic code in the log message is 7 (Administratively Down), the user has actively removed the configuration. In this case, no action is required. ¡ If the collaboration configuration does not exist, and the diagnostic code in the log message is 0 (No Diagnostic), 1 (Control Detection Time Expired), 2 (Echo Function Failed), or 3 (Neighbor Signaled Session Down), proceed to step 3. 2. Delete the BFD configuration for the upper-layer protocol, and then identify whether the upper-layer protocol is stable. ¡ If upper-layer protocol flapping occurs, first troubleshoot the upper-layer protocol issue. Then associate the upper-layer protocol with BFD again, and identify whether the log message is still generated. If the log message is not generated, the processing is completed. If the log message is still generated, proceed to step 3. ¡ If the upper-layer protocol is stable, associate the upper-layer protocol with BFD again. If the BFD session is still deleted, proceed to step 3. 3. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
BFD_CREATE_SESS
|
Message text |
The BFD session has been created successfully. Sess [STRING], Ver:[STRING], SessActive: [UINT32], SessName: [STRING], VpnName: [STRING], Applications: [STRING] |
|
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: BFD version. Options are 0 and 1. $3: Whether the session state is active: · 0—The session is not activated. · 1—The session is activated. $4: Session name. $5: Name of the VPN associated with the session. $6: Name of the application associated with the session. |
|
Severity level |
5 (Notification) |
|
Example |
BFD/5/BFD_CREATE_SESS: Sess [17.1.1.2/17.1.1.1, LD/RD: 1537/1537, Interface: GE1/0/1, SessType: Ctrl, LinkType: INET], Ver: 1, SessActive: 1, SessName: test, VpnName: test, Applications: BGP/OSPF |
|
Impact |
No negative impact on the system. |
|
Cause |
A BFD session is created. |
|
Recommended action |
No action is required. |
BFD_PKT_AUTH_ERR
|
Message text |
Sess [STRING], Ver:[UNIT32], Sta: [STRING], Diag: [UINT32], P: [ UINT32], F: [ UINT32], C: [UINT32], A: [UINT32], D: [UINT32], M: [UINT32], DetectMult: [UINT32], Length: [UINT32], UDP port: [UINT32], TTL: [UINT32], PktAuthType: [UINT32], SessAuthType: [UINT32], Reason: [STRING] |
|
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: BFD version. Options are 0 and 1. $3: State carried in the BFD packet: · 0—AdminDown. · 1—Down. · 2—Init. · 3—Up. $4: Diagnostic information: · 0 (No Diagnostic)—The BFD session is in up state. · 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. $5: P bit carried in the BFD packet. $6: F bit carried in the BFD packet. $7: C bit carried in the BFD packet. $8: A bit carried in the BFD packet. $9: D bit carried in the BFD packet. $10: M bit carried in the BFD packet. $11: Detection time multiplier carried in the BFD packet. $12: Length carried in the BFD packet. $13: UDP port number carried in the BFD packet. $14: TTL carried in the BFD packet. $15: Authentication type carried in the BFD packet: · 0—No authentication. · 1—Simple authentication. · 2—MD5 authentication. · 3—M-MD5 authentication. · 4—SHA1 authentication. · 5—M-SHA1 authentication. $16: Authentication type of the BFD session: · 0—No authentication. · 1—Simple authentication. · 2—MD5 authentication. · 3—M-MD5 authentication. · 4—SHA1 authentication. · 5—M-SHA1 authentication. · 6—HMAC_MD5 authentication. · 7—HMAC-MMD5 authentication. · 8—HMAC_SHA1 authentication. · 9—HMAC-MSHA1 authentication. $17: Reason why the BFD packet becomes invalid: · Received a simple authentication packet with mismatching authentication type. Discard packet · Received a simple authentication packet with mismatching length. Discard packet · Received a simple authentication packet with mismatching key ID. Discard packet · Received a simple authentication packet with incorrect password. Discard packet · Received an MD5 authentication packet with mismatching authentication type. Discard packet · Received an MD5 authentication packet with mismatching length. Discard packet · Received an MD5 authentication packet with mismatching key ID. Discard packet · Received an MD5 authentication packet with mismatching sequence number. Discard packet · Received an MD5 authentication packet with mismatching digest or calculation failure. Discard packet · Received a SHA1 authentication packet with mismatching hash value or calculation failure. Discard packet · Received a SHA1 authentication packet with mismatching authentication type. Discard packet · Received a SHA1 authentication packet with mismatching length. Discard packet · Received a SHA1 authentication packet with mismatching key ID. Discard packet · Received a SHA1 authentication packet with mismatching sequence number. Discard packet · Received a packet with none authentication mode. Discard packet |
|
Severity level |
5 (Notification) |
|
Example |
BFD/5/BFD_PKT_AUTH_ERR: Sess [17.1.1.2/17.1.1.1, LD/RD: 1537/1537, Interface: GE1/0/1, SessType: Ctrl, LinkType: INET], Ver: 1, Sta: 3, Diag: 0, P: 1, F: 0, C: 1, A: 1, D: 0, M: 0 , DetectMult: 5, Length: 48, UDP Port: 3784, TTL: 255, PktAuthType: 2, SessAuthType: 0, Reason: Received an MD5 authentication packet with mismatching authentication type. Discard packet. |
|
Impact |
The BFD session cannot come up. The BFD session state anomaly will impact the upper-layer service associated with the BFD session. |
|
Cause |
· Authentication is configured on only one end. · The authentication settings are inconsistent on both ends. · The connection to the peer end of the session is incorrect. |
|
Recommended action |
1. Use the display current-configuration command to identify whether the local and peer sessions have consistent authentication settings. ¡ If the authentication settings are consistent, proceed to step 2. ¡ If the authentication settings are inconsistent, configure authentication settings correctly, and then use the display bfd session command to view the session state. If the State field of the session is still not Up, proceed to step 2. 2. Identify whether the connection between the local and peer interfaces is correct. ¡ If the connection is correct, proceed to step 3. ¡ If the connection is incorrect, correctly connect the interfaces, and then use the display bfd session command to view the session state. If the State field of the session is still not Up, proceed to step 3. 3. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
BFD_REACH_PEAK_PERF_ACTIVE
|
Message text |
BFD has reached the peak performance. Avoid creating new sessions or increasing the BFD packet transmission interval. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
BFD/3/BFD_REACH_PEAK_PERF_ACTIVE: BFD has reached the peak performance. Avoid creating new sessions or increasing the BFD packet transmission interval. |
|
Impact |
If this log message is generated for the first time, BFD performance has reached its peak. If you create new BFD sessions or increase the packet transmission rate, BFD might become unstable, and flapping might even occur. If this log message is continuously generated, see the recommended action to reduce BFD performance consumption. |
|
Cause |
BFD performance consumption has reached its peak. |
|
Recommended action |
If this log message is generated for the first time, BFD performance has reached its peak. In this case, no action is required. If this log message is continuously generated, take the following actions: Avoid creating new sessions, or increase the time parameter values for the existing the BFD session: · For control-mode single-hop BFD sessions, use the bfd min-transmit-interval, bfd min-receive-interval, and bfd detect-multiplier commands to set greater BFD detection intervals. · For control-mode multihop BFD sessions, use the bfd multi-hop detect-multiplier, bfd multi-hop min-receive-interval, and bfd multi-hop min-transmit-interval commands to set greater BFD detection intervals. · For echo-mode single-hop BFD sessions, use the bfd min-echo-receive-interval and bfd detect-multiplier commands to set greater BFD detection intervals. · For echo-mode multihop BFD sessions, use the bfd multi-hop min-echo-receive-interval and bfd multi-hop detect-multiplier commands to set greater BFD detection intervals. · For control-mode BFD sessions with a BFD template specified, use the bfd detect-multiplier, bfd min-receive-interval, and bfd min-transmit-interval commands in BFD template view to set greater BFD detection intervals. · For echo-mode BFD sessions with a BFD template specified, use the bfd detect-multiplier and bfd min-echo-receive-interval commands in BFD template view to set greater BFD detection intervals. |
BFD_REACH_PEAK_PERF_CLEAR
|
Message text |
BFD has restored to the normal performance. You can create new sessions, or decrease the BFD packet transmission interval. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
BFD/3/BFD_REACH_PEAK_PERF_CLEAR: BFD has restored to the normal performance. You can create new sessions, or decrease the BFD packet transmission interval. |
|
Impact |
BFD performance consumption restores to normal status, and BFD can operate stably. |
|
Cause |
BFD performance consumption restores to normal status. |
|
Recommended action |
No action is required. |
BFD_REACHED_UPPER_LIMIT
|
Message text |
The total number of BFD sessions [ULONG] reached the upper limit. Please avoid creating a new session. |
|
Variable fields |
$1: Total number of BFD sessions. |
|
Severity level |
3 (Error) |
|
Example |
BFD/3/BFD_REACHED_UPPER_LIMIT: The total number of BFD sessions 100 reached the upper limit. Please avoid creating a new session. |
|
Impact |
· If the number of BFD sessions has reached the upper limit, new sessions cannot be created. · If the device generating the message is powered down or reset, resource allocation might occur, which can affect services. As a best practice, do not power down or reset the device when it generates this message. |
|
Cause |
· New BFD configuration is submitted when the total number of BFD sessions has reached the upper limit. · The number of created dynamic BFD sessions has exceeded the upper limit. |
|
Recommended action |
1. Stop configuring new BFD sessions. 2. Delete redundant or unused BFD sessions with the relevant command. For example, if a redundant OSPF-associated BFD session exists, use the undo ospf bfd enable command to remove the session. For more information about deleting BFD sessions for other services, see the command references for the services. 3. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
BFD_RX_ZERO
|
Message text |
Received a message with a Required Min RX Interval of 0 during BFD session negotiation. Local discriminitor: [UINT32], Remote discriminitor: [UINT32] |
|
Variable fields |
$1: Local discriminator of the BFD session. $2: Remote discriminator of the BFD session. |
|
Severity level |
5 (Notification) |
|
Example |
BFD/5/BFD_RX_ZERO: Received a message with a Required Min RX Interval of 0 during BFD session negotiation. Local discriminitor: 100, Remote discriminitor: 100 |
|
Impact |
No negative impact on the system. |
|
Cause |
Required Min RX Interval represents the minimum interval for receiving BFD control packets supported by the sender. If this value is 0, the sender does not require the peer end to send any periodic BFD control packets. When a device receives a packet with a Required Min RX Interval field of 0, it stops BFD session negotiation with the device that sends the packet. |
|
Recommended action |
No action is required. |
BGP
This section contains BGP messages.
BGP_ASPATH_OVR_LMT
|
Message text |
The AS count in the AS_PATH attribute exceeded the limit. (Peer=[STRING], Source interface=[STRING], limit=[STRING], VPN instance=[STRING], address family=[STRING], operation=[STRING], Instance=[STRING]) |
|
Variable fields |
$1: IP address of the BGP peer. $2: Source interface used for TCP connection. $3: Maximum number of ASs in the AS_PATH attribute. $4: VPN instance name. This field is blank for the public network. $5: Address family to which the BGP route belongs: · IPv4-UNC: IPv4 unicast address family. · IPv4-MLC: IPv4 multicast address family. · IPv4-VPN: VPNv4 address family. · IPv6-UNC: IPv6 unicast address family. · IPv6-VPN: VPNv6 address family. · IPv4-flowspec: IPv4 flowspec address family. · IPv6-flowspec: IPv6 flowspec address family. $6: Action taken by the local device when the AS count in the AS_PATH attribute of an advertised or received BGP route exceeds the limit: · The route will be withdrawn: The local device will send UPDATE messages to withdraw the advertised route. · The route will be retained: The route is a local summary route. The AS count limit does not take effect on that route. · The route will be discarded: The local device will discard the received route. $7: BGP instance name. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_ASPATH_OVR_LMT: The AS count in the AS_PATH attribute exceeded the limit. (Peer=1.1.1.1, Source interface=GE1/0/1, limit=50, VPN instance=vpn1, address family=IPv4-UNC, operation=The route will be withdrawn, Instance=default) |
|
Impact |
Routes exceeding the upper AS count limit will not be added into the BGP routing table. |
|
Cause |
A route received from a BGP peer exceeded the upper AS count limit. |
|
Recommended action |
Determine whether the local device needs the received route: · If no, no action is required. · If yes, contact the network administrator of the BGP peer that sent the route. To resolve this issue, the network administrator can perform one of the following tasks: ¡ Reduce the number of ASs included in advertised routes by configuring a BGP route distribution policy. ¡ Set a larger AS number quantity threshold by using the as-path-limit command. |
BGP_AUTH_FAILED
|
Message text |
BGP session authentication failed. (Peer=[STRING], TcpConnSocket=[STRING], Instance=[STRING]) |
|
Variable fields |
$1: IP address of the BGP peer. $2: Socket number of the TCP connection. $3: BGP instance name. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_AUTH_FAILED: BGP session authentication failed. (Peer=192.99.0.2, TcpConnSocket=10, Instance=default) |
|
Impact |
The BGP session will be terminated. |
|
Cause |
The two ends of a BGP session used different security settings. |
|
Recommended action |
Execute the display current-configuration configuration bgp command on the local and peer devices separately to identify whether they have security settings: · If they have security settings, adjust their security settings to ensure that they use the same security settings. · If they do not have security settings or BGP session authentication still fails after you adjust their security settings, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_BMP_STATE_CHANGED
|
Message text |
· Pattern 1: BGP [STRING]: BMP Server [STRING] state has changed from Not connected to Connected. · Pattern 2: BMP Server [STRING] state has changed from Connected to Not connected for [STRING]. |
|
Variable fields |
$1: BGP instance name. $2: BMP server ID. In pattern 2: $1: BGP instance name. $2: BMP server ID. $3: Reason why the TCP connection to the BGM server went down: · manual reset: The TCP connection to the BGM server was manually reset. · tcp connect error: A TCP connection error occurred. · configuration changed: The settings for BMP server connection were changed on the local device. · bmp server deleted: The BGM server is removed. · ha stop event received: A STOP event was received from the HA module. · bgp instance deleted: The BGP instance was deleted. · maximum limit of sending buffer reached: The number of messages sent from the client to the BMP server exceeded the buffer size limit and thus the TCP connection was terminated. |
|
Severity level |
3 (Error) |
|
Example |
BGP/3/BGP_BMP_STATE_CHANGED: BGP default: BMP Server 2 state has changed from Not connected to Connected. |
|
Impact |
· Pattern 1: No negative impact on the system. · Pattern 2: The TCP connection between the local device and the BMP server will be terminated. |
|
Cause |
The BMP client successfully established a TCP connection to the BMP server or was disconnected from the BMP server. |
|
Recommended action |
If the TCP connection to the BMP server is terminated by incident, perform the following operations: · Identify whether the BMP server fails. · Identify whether the settings for BMP server connection are correct on the client: ¡ IP address and port number of the BMP server. ¡ VPN instance to which the BMP server belongs. ¡ Client-side interface that launches a TCP connection to the BMP server. ¡ IP address of the client-side interface that launches a TCP connection to the BMP server. ¡ Authentication method for the TCP connection between the client device and the BMP server. |
BGP_ERR_PEER_AS
|
Message text |
The AS number carried in the OPEN message from the peer was different from that configured for the peer. (VPN instance=[STRING], peer=[STRING], source interface=[STRING], expected AS=[STRING], received AS=[STRING], Instance=[STRING]) |
|
Variable fields |
$1: VPN instance name. This field is blank for the public network. $2: IP address of the BGP peer. $3: Source interface used for TCP connection. $4: AS number configured for the BGP peer. $5: AS number in the OPEN message received from the BGP peer. $6: BGP instance name. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_ERR_PEER_AS: The AS number carried in the OPEN message from the peer was different from that configured for the peer. (VPN instance=vpn1, peer=192.99.0.2, source interface=G1/0/1, expected AS=100, received AS=100, Instance=default) |
|
Impact |
BGP session establishment will fail. |
|
Cause |
The AS number carried in the OPEN message from a BGP peer was different from that configured for the BGP peer. |
|
Recommended action |
1. Contact the network administrator of the BGP peer to obtain the AS number of the peer. 2. Re-configure the AS number of the BGP peer on the local device. |
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 (Warning) |
|
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. |
|
Impact |
The impact on the system varies by the configuration of the rpki-limit command: · If the alert-only keyword is not specified, the TCP connection between the device and the RPKI server will be terminated. · If the alert-only keyword is specified, this issue has no negative impact on the system. |
|
Cause |
The number of ROAs received from an RPKI server exceeds the upper ROA count limit configured for that RPKI server. |
|
Recommended action |
To resolve this issue: 1. Execute the display bgp rpki server command and view the ROAs(IPv4/IPv6) field in the command output to check whether the number of ROAs received from the RPKI server has reached the upper limit. ¡ If the number of ROAs received from the RPKI server has reached the upper limit, go to step 2. ¡ If the number of ROAs received from the RPKI server has not reached the upper limit, go to step 6. 2. Identify whether the overflowing received ROAs are necessary for current services. ¡ If the overflowing received ROAs are necessary, go to step 5. ¡ If the overflowing received ROAs are not necessary, go to step 3. 3. Contact the administrator of the RPKI server to check whether the ROAs advertised to the device are all necessary. ¡ If the ROAs advertised to the device are all necessary, go to step 5. ¡ If some of the ROAs advertised to the device are not necessary, go to step 4. 4. Notify the administrator of the RPKI server to withdraw unnecessary ROAs. If this issue persists, go to step 6. 5. Use the rpki-limit command on the device to increase the maximum number of ROAs that can be received from the RPKI server. If this issue persists, go to step 6. 6. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
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 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of ROAs received from an RPKI server has dropped below the upper ROA count limit configured for that RPKI server. |
|
Recommended action |
No action is required. |
BGP_EXCEED_ROUTE_LIMIT
|
Message text |
BGP [STRING].[STRING]: The number of routes ([UINT32]) from peer [STRING] ([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 route prefixes received from the BGP peer. $4: IP address of the BGP peer. $5: Address family of the BGP peer. $6: Maximum number of route prefixes that can be received from the peer. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_EXCEED_ROUTE_LIMIT: BGP default.vpn1: The number of routes (101) from peer 1.1.1.1 (IPv4-UNC) exceeds the limit 100. |
|
Impact |
Causing the interruption of the BGP session between the device and the neighbor, or the inability to receive new routes from the neighbor, resulting in a service interruption. |
|
Cause |
The number of routes received from a peer has exceeded the upper limit configured for that peer. |
|
Recommended action |
To resolve this issue: 1. Identify whether the overflowing received routes are necessary for forwarding services. ¡ If the overflowing received routes are necessary, go to step 7. ¡ If the overflowing received routes are not necessary, go to step 2. 2. Execute the display current-configuration configuration bgp command to view the current BGP configurations. Check for configurations that cause the local device to receive too many unnecessary routes. Such configurations include peer prefix-list, peer filter-policy, peer as-path-acl, filter-policy, and peer route-policy. ¡ If the local device has some configurations that affect the route reception policy, go to step 3. ¡ If the local device does not have configurations that affect the route reception policy, go to step 4. 3. Edit those configurations to reduce the number of routes received by the local device, and then go to step 8. 4. Contact the administrator of the peer to identify whether the number of BGP routes sent to the local device is appropriate: ¡ If the number of BGP routes sent to the local device is appropriate, go to step 5. ¡ If the number of BGP routes sent to the local device is not appropriate, go to step 6. 5. Notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local device, and then go to step 8. To reduce the number of BGP routes sent to the local device, the administrator can use the following methods: ¡ Summarize the routes sent to the local device. ¡ Suppress the advertisement of summarized routes. 6. Notify the administrator of the BGP peer to edit the policy of route distribution to the local device, which prevents the local device from receiving unnecessary routes. Then, go to step 8. 7. Use the peer route-limit command to increase the maximum number of BGP routes that can be received from the peer. Then, go to step 8. 8. Identify whether the BGP/6/BGP_EXCEED_ROUTE_LIMIT_CLEAR log message is generated on the device. ¡ If the message is generated, the issue is cleared. ¡ If the message is not generated, go to step 9. 9. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_EXCEED_ROUTE_LIMIT_CLEAR
|
Message text |
BGP [STRING].[STRING]: The number of routes ([UINT32]) from peer [STRING] ([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 route prefixes received from the BGP peer. $4: IP address of the BGP peer. $5: Address family of the BGP peer. $6: Maximum number of route prefixes that can be received from the peer. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_EXCEED_ROUTE_LIMIT_CLEAR: BGP default.vpn1: The number of routes (99) from peer 1.1.1.1 (IPv4-UNC) fell below the limit 100. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of routes received from a peer dropped below the upper limit configured for that peer. |
|
Recommended action |
No action is required. |
BGP_GR_DUPLICT_OPEN_RCV
|
Message text |
Duplicate OPEN message was received from the peer, and this peer was detected GR-capable. (Peer=[STRING], VPN instance=[STRING], Instance=[STRING]) |
|
Variable fields |
$1: IP address of the BGP peer. $2: VPN instance name. This field is blank for the public network. $3: BGP instance name. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_GR_DUPLICT_OPEN_RCV: Duplicate OPEN message was received from the peer, and this peer was detected GR-capable. (Peer=192.99.0.2, VPN instance=vpn1, Instance=default) |
|
Impact |
|
|
Cause |
A BGP peer repeatedly sent an OPEN message to the local device and the peer was detected GR-capable. |
|
Recommended action |
No action is required. |
BGP_GR_NO_R_IN_OPEN
|
Message text |
The BGP session was re-established, because the GR-capable peer received an OPEN message without the R flag set. (VPN instance=[STRING], peer=[STRING], source interface=[STRING], Instance=[STRING]) |
|
Variable fields |
$1: VPN instance name. This field is blank for the public network. $2: IP address of the BGP peer. $3: Source interface used for TCP connection. $4: BGP instance name. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_GR_NO_R_IN_OPEN: The BGP session was re-established, because the GR-capable peer received an OPEN message without the R flag set. (VPN instance=vpn1, peer=192.99.0.2, source interface=G1/0/1, Instance=default) |
|
The peer will exit from the GR process, and the local device and the peer will re-establish a BGP session. |
|
|
Cause |
The BGP session was re-established between the local device and a GR-capable BGP peer, because the peer received an OPEN message without the R flag set. |
|
Recommended action |
No action is required. |
BGP_GR_PEER_START
|
Message text |
The peer is performing GR. (Peer=[STRING], source interface=[STRING], Instance=[STRING]) |
|
Variable fields |
$1: IP address of the BGP peer. $2: Source interface used for TCP connection. $3: BGP instance name. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_GR_PEER_START: The peer is performing GR. (Peer=192.99.0.2, source interface= G1/0/1, Instance=default) |
|
Impact |
|
|
Cause |
The local device found that a BGP peer was performing GR. |
|
Recommended action |
No action is required. |
BGP_GR_RST_TMR_EXPIRE
|
Message text |
The GR timer expired. (Peer=[STRING], source interface=[STRING], VPN instance=[STRING], Instance=[STRING]) |
|
Variable fields |
$1: IP address of the BGP peer. $2: Source interface used for TCP connection. $3: VPN instance name. This field is blank for the public network. $4: BGP instance name. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_GR_RST_TMR_EXPIRE:The GR timer expired. (Peer=192.99.0.2, source interface=GE1/0/1, VPN instance=vpn1, Instance=default) |
|
Impact |
No negative impact on the system. |
|
Cause |
The GR timer specified for the peer on the local device expired. |
|
Recommended action |
No action is required. |
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. $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 (Warning) |
|
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. |
|
Impact |
Frequent BGP route flapping will increase system CPU usage and might cause service disruption. |
|
Cause |
The route learned from a BGP peer flapped due to unreasonable configurations or other issues on devices in the network. |
|
Recommended action |
1. Configure BGP route dampening to minimize the impact of route flapping. 2. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_LABEL_CONFLICT
|
Message text |
BGP egress-engineering incoming label [STRING] conflicts with current configuration. |
|
Variable fields |
$1: SID value. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_LABEL_CONFLICT: BGP egress-engineering incoming label 3000 conflicts with current configuration. |
|
Impact |
|
|
Cause |
The SID value assigned by BGP Egress Peer Engineering (EPE) was already in use by other services. |
|
Recommended action |
Verify that the assigned SID value is not in use by any other service. |
BGP_LABEL_OUTOFRANGE
|
Message text |
BGP egress-engineering incoming label [STRING] is out of range. |
|
Variable fields |
$1: SID value. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_LABEL_OUTOFRANGE: BGP egress-engineering incoming label 1024 is out of range. |
|
Impact |
The SID value cannot be assigned to peers. |
|
Cause |
The SID value assigned by BGP EPE was out of range. |
|
Recommended action |
If a routing policy is used by BGP EPE for SID assignment to peers, verify that the SID value specified in the routing policy is valid. |
BGP_MEM_ALERT
|
Message text |
BGP [STRING] instance received system memory alert [STRING] event. |
|
Variable fields |
$2: Type of the memory alarm, including stop and start. |
|
Severity level |
5 (Notification) |
|
Example |
BGP/5/BGP_MEM_ALERT: BGP default instance received system memory alert start event. |
|
Impact |
The BGP process cannot run normally. |
|
Cause |
BGP received a memory alarm. |
|
Recommended action |
1. Execute the display memory-threshold command to obtain the current memory alarm threshold. 2. Collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_PEER_LICENSE_REACHED
|
Message text |
BGP [STRING]: Number of peers in Established state reached the license limit. |
|
Variable fields |
$1: BGP instance name. |
|
Severity level |
3 (Error) |
|
Example |
BGP/3/BGP_PEER_LICENSE_REACHED: BGP default: Number of peers in Established state reached the license limit. |
|
Impact |
The local device cannot establish more peers in Established state. |
|
Cause |
The number of peers in Established state has reached the upper limit of the license. |
|
Recommended action |
Identify whether the upper limit specified in the installed license meets the service requirements: · If yes, delete unnecessary BGP peers. · If no, purchase and install a license with a higher upper limit on the number of BGP peers. |
BGP_PEER_RT_EX_ACTIVE
|
Message text |
The number of routes received from the BGP peer exceeded the max number of routes that can be received from the peer. (Instance=[STRING], AFI=[STRING], SAFI=[STRING], PeerAddrType=[STRING], PeerAddr=[STRING], MaxRouteNum=[STRING]) |
|
Variable fields |
$1: BGP instance name. $2: Address family identifier. $3: Subsequent address family identifier. $4: IP address type of the BGP peer. $5: IP address of the BGP peer. $6: Maximum number of routes that can be received from the BGP peer. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_PEER_RT_EX_ACTIVE: The number of routes received from the BGP peer exceeded the max number of routes that can be received from the peer. (Instance=default, AFI=1, SAFI=1, PeerAddrType=IPv4-UNC, PeerAddr=1.1.1.1, MaxRouteNum=50) |
|
Impact |
The BGP session between the local device and the peer will be terminated, or the local device cannot receive new routes from the peer. |
|
Cause |
The number of routes received from a BGP peer exceeded the maximum number of routes that can be received from the peer. |
|
Recommended action |
1. Identify whether the overflowing received routes are necessary for forwarding services. ¡ If the overflowing received routes are necessary, go to step 7. ¡ If the overflowing received routes are not necessary, go to step 2. 2. Execute the display current-configuration configuration bgp command to view the current BGP configurations. Check for configurations that cause the local device to receive too many unnecessary routes. Such configurations include peer prefix-list, peer filter-policy, peer as-path-acl, filter-policy, and peer route-policy. ¡ If the local device has some configurations that affect the route reception policy, go to step 3. ¡ If the local device does not have configurations that affect the route reception policy, go to step 4. 3. Edit those configurations to reduce the number of routes received by the local device, and then go to step 8. 4. Contact the administrator of the peer to identify whether the number of BGP routes sent to the local device is appropriate: ¡ If the number of BGP routes sent to the local device is appropriate, go to step 5. ¡ If the number of BGP routes sent to the local device is not appropriate, go to step 6. 5. Notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local device, and then go to step 8. To reduce the number of BGP routes sent to the local device, the administrator can use the following methods: ¡ Summarize the routes sent to the local device. ¡ Suppress the advertisement of summarized routes. 6. Notify the administrator of the BGP peer to edit the policy of route distribution to the local device, which prevents the local device from receiving unnecessary routes. Then, go to step 8. 7. Use the peer route-limit command to increase the maximum number of BGP routes that can be received from the peer. Then, go to step 8. 8. Identify whether the BGP/4/BGP_PEER_RT_EX_CLEAR log message is generated on the device. ¡ If the message is generated, the issue is cleared. ¡ If the message is not generated, go to step 9. 9. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_PEER_RT_EX_CLEAR
|
Message text |
The number of routes received from the BGP peer decreased below the max number of routes that can be received from the peer. (Instance=[STRING], AFI=[STRING], SAFI=[STRING], PeerAddrType=[STRING], PeerAddr=[STRING], MaxRouteNum=[STRING]) |
|
Variable fields |
$1: BGP instance name. $2: Address family identifier. $3: Subsequent address family identifier. $4: IP address type of the BGP peer. $5: IP address of the BGP peer. $6: Maximum number of routes that can be received from the BGP peer. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_PEER_RT_EX_CLEAR: The number of routes received from the BGP peer decreased below the max number of routes that can be received from the peer. (Instance=default, AFI=1, SAFI=1, PeerAddrType=IPv4-UNC, PeerAddr=1.1.1.1, MaxRouteNum=50) |
|
Impact |
|
|
Cause |
The number of routes received from a BGP peer dropped below the maximum number of routes that can be received from the peer. |
|
Recommended action |
BGP_PEER_RT_NUM_THR_EX_ACTIVE
|
Message text |
The number of routes received from the BGP peer exceeded the alarm threshold. (Instance=[STRING], AFI=[STRING], SAFI=[STRING], PeerAddrType=[STRING], PeerAddr=[STRING], MaxRouteNumber=[STRING], alarm threshold=[STRING]) |
|
Variable fields |
$1: BGP instance name. $2: Address family identifier. $3: Subsequent address family identifier. $4: IP address type of the BGP peer. $5: IP address of the BGP peer. $6: Maximum number of routes that can be received from the BGP peer. $7: Alarm threshold specified for the BGP peer on the local device. The local device generates an alarm message when the ratio of received routes to maximum routes that can be received reaches the alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_PEER_RT_NUM_THR_EX_ACTIVE: The number of routes received from the BGP peer exceeded the alarm threshold. (Instance=default, AFI=1, SAFI=1, PeerAddrType=IPv4-UNC, PeerAddr=1.1.1.1, MaxRouteNumber=50, alarm threshold=50) |
|
The impact on the system varies by the alarm threshold configuration of the peer route-limit command: · If the alarm threshold is set to 100% for the peer, the device will be disconnected from the peer or cannot receive new routes from the peer. · If the alarm threshold is set to a value other than 100% for the peer, this issue has no negative impact on the system. This alarm message aims at informing users of the potential impact, that is, the number of routes received from the peer is reaching the upper limit. |
|
|
Cause |
The number of routes received from a BGP peer exceeded the alarm threshold configured for that peer. |
|
Recommended action |
To resolve the issue: 1. Execute the display bgp peer verbose command and view the NLRI statistics and Message statistics fields in the command output to identify whether the number of routes received from the peer has reached the alarm threshold: ¡ If the number of routes received from the peer has reached the alarm threshold, go to step 2. ¡ If the number of routes received from the peer has not reached the alarm threshold, go to step 10. 2. Identify whether the overflowing received routes are necessary for forwarding services. ¡ If the overflowing received routes are necessary, go to step 8. ¡ If the overflowing received routes are not necessary, go to step 3. 3. Execute the display current-configuration configuration bgp command to view the current BGP configurations. Check for configurations that cause the local device to receive too many unnecessary routes. Such configurations include peer prefix-list, peer filter-policy, peer as-path-acl, filter-policy, and peer route-policy. ¡ If the local device has some configurations that affect the route reception policy, go to step 4. ¡ If the local device does not have configurations that affect the route reception policy, go to step 5. 4. Edit those configurations to reduce the number of routes received by the local device, and then go to step 9. 5. Contact the administrator of the peer to identify whether the number of BGP routes sent to the local device is appropriate: ¡ If the number of BGP routes sent to the local device is appropriate, go to step 6. ¡ If the number of BGP routes sent to the local device is not appropriate, go to step 7. 6. Notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local device, and then go to step 9. To reduce the number of BGP routes sent to the local device, the administrator can use the following methods: ¡ Summarize the routes sent to the local device. ¡ Suppress the advertisement of summarized routes. 7. Notify the administrator of the BGP peer to edit the policy of route distribution to the local device, which prevents the local device from receiving unnecessary routes. Then, go to step 9. 8. Use the peer route-limit command to increase the maximum number of BGP routes that can be received from the peer or increase the alarm threshold. Then, go to step 9. 9. Identify whether the BGP/4/BGP_PEER_RT_NUM_THR_EX_CLEAR log message is generated on the device. ¡ If the message is generated, the issue is cleared. ¡ If the message is not generated, go to step 10. 10. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_PEER_RT_NUM_THR_EX_CLEAR
|
Message text |
The number of routes received from the BGP peer decreased below the alarm threshold. (Instance=[STRING], AFI=[STRING], SAFI=[STRING], PeerAddrType=[STRING], PeerAddr=[STRING], MaxRouteNumber=[STRING], alarm threshold=[STRING]) |
|
Variable fields |
$1: BGP instance name. $2: Address family identifier. $3: Subsequent address family identifier. $4: IP address type of the BGP peer. $5: IP address of the BGP peer. $6: Maximum number of routes that can be received from the BGP peer. $7: Alarm threshold specified for the BGP peer on the local device. The local device generates an alarm message when the ratio of received routes to maximum routes that can be received reaches the alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_PEER_RT_NUM_THR_EX_CLEAR: The number of routes received from the BGP peer decreased below the alarm threshold. (Instance=default, AFI=1, SAFI=1, PeerAddrType=IPv4-UNC, PeerAddr=1.1.1.1, MaxRouteNumber=50, alarm threshold=50) |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of routes received from a BGP peer dropped below the alarm threshold configured for that peer. |
|
Recommended action |
BGP_PEER_STATE_CHG
|
Message text |
Peer state changed after BGP received an event. (PrevState=[STRING], CurrState=[STRING], input event=[STRING], peer=[STRING], source interface=[STRING], VPN instance=[STRING], Instance=[STRING]) |
|
Variable fields |
$1: Original state of the peer session: · IDLE: Initial BGP session state. In this state, BGP refuses all connection requests. · CONNECT: In this state, BGP is establishing TCP connection to the peer. · ACTIVE: Intermediate state of BGP session establishment. In this state, BGP is trying to establish TCP connection to the peer. · OPENSENT: In this state, BGP is waiting for an OPEN message from the peer. · OPENCONFIRM: In this state, BGP is waiting for a KEEPALIVE or NOTIFICATION message from the peer. · ESTABLISHED: BGP has successfully established a session to the peer. Only in this state can BGP exchange UPDATE messages with the peer. $2: Current state of the peer session: · IDLE: Initial BGP session state. In this state, BGP refuses all connection requests. · CONNECT: In this state, BGP is establishing TCP connection to the peer. · ACTIVE: Intermediate state of BGP session establishment. In this state, BGP is trying to establish TCP connection to the peer. · OPENSENT: In this state, BGP is waiting for an OPEN message from the peer. · OPENCONFIRM: In this state, BGP is waiting for a KEEPALIVE or NOTIFICATION message from the peer. · ESTABLISHED: BGP has successfully established a session to the peer. Only in this state can BGP exchange UPDATE messages with the peer. $3: Event that caused the peer session state change: · START: BGP started establishing TCP connection to the peer. · STOP: BGP stopped establishing TCP connection to the peer. · IH_TIMER: The IdleHoldTimer expired. · CR_TIMER: The ConnectRetryTimer expired. · OD_TIMER: The DelayOpenTimer expired. · HOLD_TIMER: The HoldTimer expired. · KA_TIMER: The KeepaliveTimer expired. · TCP_SUCCEED: BGP successfully established TCP connection to the peer. · TCP_FAIL: BGP failed to establish TCP connection to the peer. · TCP_INCOMING: BGP received a TCP connection request from the peer. · RECV_OPEN: BGP received an OPEN message from the peer. · RECV_KA: BGP received a KEEPALIVE message from the peer. · RECV_UPDATE: BGP received an UPDATE message from the peer. · RECV_RR: BGP received a Route-Refresh message from the peer. · RECV_NOTIF: BGP received a NOTIFICATION message from the peer. · RECV_NOTIF_VER: BGP received a BGP-version error notification from the peer. · RECV_HEAD_ERR: BGP received an incorrect BGP packet header from the peer. · RECV_OPEN_ERR: BGP received an incorrect OPEN message from the peer. · RECV_UPDATE_ERR: BGP received an incorrect UPDATE message from the peer. · RECV_RR_ERR: BGP received an incorrect Route-Refresh message from the peer. · LINK_UNREACHABLE_DETECTED: The peer was detected unreachable. $4: IP address of the BGP peer. $5: Source interface used for TCP connection. $6: VPN instance name. This field is blank for the public network. $7: BGP instance name. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_PEER_STATE_CHG: Peer state changed after BGP received an event. (PrevState=OPENCONFIRM, CurrState=ESTABLISHED, input event=RECV_KA, peer=192.99.0.2, source interface= GE1/0/1, VPN instance=vpn1, Instance=default) |
|
Impact |
· If the BGP session state is transitioned to Established, this issue has no negative impact on the system. · If the BGP session state is transitioned from Established to another state, the BGP session will be terminated. As a result, the device might not have the associated BGP route to guide traffic forwarding, resulting in service interruption. |
|
Cause |
BGP changed the state of a peer session after receiving a related event. |
|
Recommended action |
If the BGP session state is transitioned to Established, no action is required. If the BGP session state is transitioned from Established to another state, perform the following operations: 1. Execute the display current-configuration configuration bgp command to identify the settings that affect BGP session state. ¡ If a setting that causes BGP session disconnection exists, execute the relevant command to cancel the setting. ¡ If BGP uses a loopback interface as the source interface of TCP connections, execute the peer connect-interface or peer source-address command to specify the loopback interface as the source interface for establishing TCP connections. ¡ To establish an EBGP session to an indirectly connected peer, make sure the peer ebgp-max-hop command is executed on both ends of the session. ¡ If the peer ttl-security command is configured to enable BGP GTSM on the device, the device receives the BGP packets with a TTL value in the range from 255 – the configured hop count + 1 to 255. ¡ If no settings affect BGP session state, go to step 2. 2. Wait for a short period of time to exclude the cause of disconnection by BGP session reset. If the BGP session fails to restore to the Established state within a long period of time, go to step 3. 3. Execute the display current-configuration configuration bgp command to check for the configuration of the peer route-limit command, and the BGP/4/BGP_EXCEED_ROUTE_LIMIT log message printed by the device. ¡ If both the configuration and the log exist, the BGP session is disconnected because excessive BGP routes are received. In this case, verify that the maximum number of routes that can be received configured with the peer route-limit command is appropriate: ¡ If the setting is appropriate, notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local end. ¡ If the setting is inappropriate, increase the maximum number of BGP routes that can be received on the local end. ¡ If the configuration or the log does not exist, or neither of them exists, receiving excessive BGP routes is not the cause for the BGP session disconnection. In this case, go to step 4. 4. Execute the display bgp peer log-info command. From the command output, identify the BGP session disconnection cause based on the error code or subcode printed in the Notification Error/SubError field. · If the error code (Error) is 4, the local end fails to receive any keepalive or update messages from the peer end within the BGP session hold time. This results in BGP session disconnection. If the error code is 5 or 6, the BGP session is disconnected because the TCP connection has an error or the connection is actively terminated. You can perform troubleshooting by using the following methods: ¡ On the local end, ping the source address used for establishing TCP connections on the BGP peer. If the ping operation fails, execute the display ip routing-table command to identify whether a route is available to the BGP peer. If no routes are available to the BGP peer, troubleshoot IGP route, static route, or direct route settings. ¡ Execute the display memory-threshold command to identify whether the device has reached the memory usage threshold. If the memory usage threshold is reached, go to step 5. ¡ Execute the display cpu-usage command to identify whether the CPU usage is too high. If the CPU usage is too high, go to step 5. ¡ Execute the display acl all command to identify whether a rule exists that denies port bgp or 179. If such an ACL exists, delete the ACL. ¡ Execute the display interface command to identify whether the output interface associated with the next hop of the route to the BGP peer is up. If the output interface is down, execute the undo shutdown command to bring up the interface in the view of the interface. If the interface fails to be brought up, or the interface is up but the alarm persists, go to step 5. · If the error code (Error) is 1 or 3, the device has received wrong BGP packets. Go to step 5. 5. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_REACHED_THRESHOLD
|
BGP [STRING].[STRING]: The ratio of the number of routes ([UINT32]) received from peer [STRING] ([STRING]) to the number of allowed routes ([UINT32]) has reached the threshold ([UINT32]%). |
|
|
Variable fields |
$1: BGP instance name. $2: VPN instance name. This field is blank for the public network. $3: Number of routes received from the BGP peer. $4: IP address of the BGP peer. $5: Address family of the BGP peer. $6: Maximum number of routes that can be received from the peer. $7: Alarm threshold specified for the BGP peer on the local device. The local device generates an alarm message when the ratio of received routes to maximum routes that can be received reaches the alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
BGP/4/BGP_REACHED_THRESHOLD: BGP default.vpn1: The ratio of the number of routes (3) received from peer 1.1.1.1 (IPv4-UNC) to the number of allowed routes (2) has reached the threshold (75%). |
|
Impact |
The impact on the system varies by the alarm threshold configuration of the peer route-limit command: · If the alarm threshold is set to 100% for the peer, the device will be disconnected from the peer or cannot receive new routes from the peer. · If the alarm threshold is set to a value other than 100% for the peer, this issue has no negative impact on the system. This alarm message aims at informing users of the potential impact, that is, the number of routes received from the peer is reaching the upper limit. |
|
Cause |
The number of routes received from a BGP peer exceeded the alarm threshold. |
|
Recommended action |
To resolve the issue: 1. Execute the display bgp peer verbose command and view the NLRI statistics and Message statistics fields in the command output to identify whether the number of routes received from the peer has reached the alarm threshold: ¡ If the number of routes received from the peer has reached the alarm threshold, go to step 2. ¡ If the number of routes received from the peer has not reached the alarm threshold, go to step 10. 2. Identify whether the overflowing received routes are necessary for forwarding services. ¡ If the overflowing received routes are necessary, go to step 8. ¡ If the overflowing received routes are not necessary, go to step 3. 3. Execute the display current-configuration configuration bgp command to view the current BGP configurations. Check for configurations that cause the local device to receive too many unnecessary routes. Such configurations include peer prefix-list, peer filter-policy, peer as-path-acl, filter-policy, and peer route-policy. ¡ If the local device has some configurations that affect the route reception policy, go to step 4. ¡ If the local device does not have configurations that affect the route reception policy, go to step 5. 4. Edit those configurations to reduce the number of routes received by the local device, and then go to step 9. 5. Contact the administrator of the peer to identify whether the number of BGP routes sent to the local device is appropriate: ¡ If the number of BGP routes sent to the local device is appropriate, go to step 6. ¡ If the number of BGP routes sent to the local device is not appropriate, go to step 7. 6. Notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local device, and then go to step 9. To reduce the number of BGP routes sent to the local device, the administrator can use the following methods: ¡ Summarize the routes sent to the local device. ¡ Suppress the advertisement of summarized routes. 7. Notify the administrator of the BGP peer to edit the policy of route distribution to the local device, which prevents the local device from receiving unnecessary routes. Then, go to step 9. 8. Use the peer route-limit command to increase the maximum number of BGP routes that can be received from the peer or increase the alarm threshold. Then, go to step 9. 9. Identify whether the BGP_REACHED_THRESHOLD_CLEAR log message is generated on the device. ¡ If the message is generated, the issue is cleared. ¡ If the message is not generated, go to step 10. 10. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_REACHED_THRESHOLD_CLEAR
|
Message text |
BGP [STRING].[STRING]: The ratio of the number of routes ([UINT32]) received from peer [STRING] ([STRING]) to the number of allowed routes ([UINT32]) has fallen below the threshold ([UINT32]%). |
|
Variable fields |
$2: VPN instance name. This field is blank for the public network. $3: Number of routes received from the BGP peer. $4: IP address of the BGP peer. $5: Address family of the BGP peer. $6: Maximum number of routes that can be received from the peer. $7: Alarm threshold specified for the BGP peer on the local device. The local device generates an alarm message when the ratio of received routes to maximum routes that can be received reaches the alarm threshold. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_REACHED_THRESHOLD_CLEAR: BGP default.vpn1: The ratio of the number of routes (3) received from peer 1.1.1.1 (IPv4-UNC) to the number of allowed routes (5) has fallen below the threshold (75%). |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of routes received from a BGP peer dropped below the alarm threshold. |
|
Recommended action |
BGP_ROUTE_LICENSE_REACHED
|
Message text |
BGP [STRING]: Number of [STRING] routes reached the license limit. |
|
Variable fields |
$1: BGP instance name. $2: BGP address family, including: · IPv4-UNC public: Public IPv4 unicast address family. · IPv6-UNC public: Public IPv6 unicast address family. · IPv4 private: Private IPv4 unicast address family, VPNv4 address family, and nested VPN address family · IPv6 private: Private IPv6 unicast address family, VPNv6 address family. |
|
Severity level |
3 (Error) |
|
Example |
BGP/3/BGP_ROUTE_LICENSE_REACHED: BGP default: Number of IPv4-UNC public routes reached the license limit. |
|
Impact |
BGP cannot support more route entries. |
|
Cause |
The number of BGP routes of the specified type reached the upper limit of the license. |
|
Recommended action |
Identify whether the upper limit specified in the installed license meets the service requirements: · If yes, configure route distribution and reception policies to reduce unnecessary BGP routes. · If no, purchase and install a license with a higher upper limit on the number of BGP routes. The methods above cannot restore the routes that have been dropped. You can manually trigger the local device to learn the missing routes. |
BGP_RPKI_STATE_CHANGED
|
Message text |
BGP [STRING].[STRING]: RPKI server [STRING] state has changed from [STRING] to [STRING]. Pattern 2: BGP [STRING].[STRING]: RPKI server [STRING] state has changed from [STRING] to [STRING] for [STRING]. |
|
Variable fields |
Pattern 1: $1: BGP instance name. $2: Name of the VPN instance to which the BGP RPKI server belongs. This field is blank for the public network. $3: IP address of the BGP RPKI server. $4: Old state name. $5: New state name. Pattern 2: $1: BGP instance name. $2: Name of the VPN instance to which the BGP RPKI server belongs. This field is blank for the public network. $3: IP address of the BGP RPKI server. $4: Old state name. $5: New state name. $6: Reason for the state change and the related error code. · configuration changed: The port number used for connection to the RPKI server was changed on the device side, or the RPKI session was reset by using the reset bgp rpki server command. · error report PDU received: The device received an Error Report message from the RPKI server. · response timer expired: The device did not receive a reply from the RPKI server. · error PDU received: The device received an invalid packet. · TCP connect failed: The TCP connection between the device and the RPKI server was terminated. · no port configured: The device was not configured with a BGP RPKI port number. · not enough memory: Insufficient memory. · Cache Reset PDU received: The device received a Cache Reset message from the RPKI server. · maximum number of ROAs reached: The number of ROAs received from the RPKI server has exceeded the upper limit configured for the RPKI server. · HA stop event received: The device was disconnected from the RPKI server due to an HA active/standby switchover. · BGP process stopped: The BGP process was stopped. |
|
Severity level |
3 (Error) |
|
Example |
BGP/3/BGP_RPKI_STATE_CHANGED: BGP default.vpn1: RPKI server 192.99.0.2 state has changed from CONNECT to ESTABLISHED. |
|
Impact |
· If this issue occurs when the RPKI server state changes to Established, this issue does not have negative impact on the system. · If this issue occurs when the RPKI server state changes from Established to another, the local device is disconnected from the RPKI server. If the disconnection remains for a long time, the ROAs that the local device has received from the RPKI server will expire. As a result, the local device cannot use the BGP RPKI feature to identify whether routes are valid based on their origin AS numbers. |
|
Cause |
This message is generated when the state of the connection between the device and an RPKI server changes to Established or changes from Established to another. |
|
Recommended action |
If this message is generated when the state of an RPKI server connection changes from Established to another, view the reason for the state change, and then check the following settings on the device: · Identify whether the port number used for connection with the RPKI server is configured, and whether the RPKI server listens for the configured port number. · Identify whether the RPKI server address is configured correctly. · Identify whether the device and the RPKI server use the same MD5 password. · Identify whether the upper limit of the number of ROAs received from the RPKI server is too small. · Identify whether the device is performing an active/standby switchover. If the above settings are all correct, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BGP_RTID_CHG
|
Message text |
The router ID of the BGP instance is changed. For the new router ID to take effect, manually reset the BGP session. (Router ID=[STRING], instance=[STRING], VPN instance=[STRING]) |
|
Variable fields |
$1: New router ID $2: BGP instance name. $3: VPN instance name. This field is blank for the public network. |
|
Severity level |
6 (Informational) |
|
Example |
BGP/6/BGP_RTID_CHG: The router ID of the BGP instance is changed. For the new router ID to take effect, manually reset the BGP session. (Router ID=2.2.2.2, instance=default, VPN instance=vpn1) |
|
Impact |
The specified BGP instance uses the original router ID until the related BGP sessions are reset. |
|
Cause |
This message is generated when the router ID of a BGP instance is changed. It notifies users to reset BGP sessions, so the new router ID can take effect. |
|
Recommended action |
In user view, execute the reset bgp command to reset BGP sessions of the BGP instance. |
BGP_STATE_CHANGED
|
Message text |
Pattern 1: BGP [STRING].[STRING]: [STRING] state has changed from [STRING] to [STRING]. Pattern 2: BGP [STRING].[STRING]: [STRING] state has changed from [STRING] to [STRING] for [STRING]. |
|
Variable fields |
Pattern 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: Old state name. $5: New state name. Pattern 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: Old state name $5: New state name $6: Reason for the state change and the related error code. |
|
Severity level |
3 (Error) |
|
Example |
BGP/3/BGP_STATE_CHANGED: BGP default.vpn1: 192.99.0.2 state has changed from OPENCONFIRM to ESTABLISHED. |
|
Impact |
Pattern 1: No negative impact on the system. Pattern 2: The BGP session will be terminated. As a result, the device might not have the associated BGP route to guide traffic forwarding, resulting in service interruption. |
|
Cause |
Pattern 1: The session to the specified BGP peer transitioned to Established state. Pattern 2: The session to the specified BGP peer transitioned from Established state to another state. |
|
Recommended action |
Pattern 1: No action is required. Pattern 2: 1. Execute the display current-configuration configuration bgp command to identify the settings that affect BGP session state. ¡ If a setting that causes BGP session disconnection exists, execute the relevant command to cancel the setting. ¡ If BGP uses a loopback interface as the source interface of TCP connections, execute the peer connect-interface or peer source-address command to specify the loopback interface as the source interface for establishing TCP connections. ¡ To establish an EBGP session to an indirectly connected peer, make sure the peer ebgp-max-hop command is executed on both ends of the session. ¡ If the peer ttl-security command is configured to enable BGP GTSM on the device, the device receives the BGP packets with a TTL value in the range from 255 – the configured hop count + 1 to 255. ¡ If no settings affect BGP session state, go to step 2. 2. Wait for a short period of time to exclude the cause of disconnection by BGP session reset. If the BGP session fails to restore to the Established state within a long period of time, go to step 3. 3. Execute the display current-configuration configuration bgp command to check for the configuration of the peer route-limit command, and the BGP/4/BGP_EXCEED_ROUTE_LIMIT log message printed by the device. ¡ If both the configuration and the log exist, the BGP session is disconnected because excessive BGP routes are received. In this case, verify that the maximum number of routes that can be received configured with the peer route-limit command is appropriate: ¡ If the setting is appropriate, notify the administrator of the BGP peer to reduce the number of BGP routes sent to the local end. ¡ If the setting is inappropriate, increase the maximum number of BGP routes that can be received on the local end. ¡ If the configuration or the log does not exist, or neither of them exists, receiving excessive BGP routes is not the cause for the BGP session disconnection. In this case, go to step 4. 4. Execute the display bgp peer log-info command. From the command output, identify the BGP session disconnection cause based on the error code or subcode printed in the Notification Error/SubError field. · If the error code (Error) is 4, the local end fails to receive any keepalive or update messages from the peer end within the BGP session hold time. This results in BGP session disconnection. If the error code is 5 or 6, the BGP session is disconnected because the TCP connection has an error or the connection is actively terminated. You can perform troubleshooting by using the following methods: ¡ On the local end, ping the source address used for establishing TCP connections on the BGP peer. If the ping operation fails, execute the display ip routing-table command to identify whether a route is available to the BGP peer. If no routes are available to the BGP peer, troubleshoot IGP route, static route, or direct route settings. ¡ Execute the display memory-threshold command to identify whether the device has reached the memory usage threshold. If the memory usage threshold is reached, go to step 5. ¡ Execute the display cpu-usage command to identify whether the CPU usage is too high. If the CPU usage is too high, go to step 5. ¡ Execute the display acl all command to identify whether a rule exists that denies port bgp or 179. If such an ACL exists, delete the ACL. ¡ Execute the display interface command to identify whether the output interface associated with the next hop of the route to the BGP peer is up. If the output interface is down, execute the undo shutdown command to bring up the interface in the view of the interface. If the interface fails to be brought up, or the interface is up but the alarm persists, go to step 5. · If the error code (Error) is 1 or 3, the device has received wrong BGP packets. Go to step 5. 5. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support for help. |
BIER messages
This section contains BIER messages.
BIER_BFRID_CONFLICT_ACTIVE
|
Message text |
A BFR ID conflict exists. Address family=[STRING], Sub-domain=[INT32], BFR ID=[INT32], BFR prefixes=[STRING]. |
|
Variable fields |
$1: Address family, which can only be IPv6. $2: BIER sub-domain ID. $3: Conflicting BFR ID. $4: BFR prefixes where the conflict exists. |
|
Severity level |
5 (Notification) |
|
Example |
BIER/5/BIER_BFRID_CONFLICT_ACTIVE: -MDC=1; A BFR ID conflict exists. Address family=IPv6, Sub-domain=1, BFR ID=4, BFR prefixes=B::1,C::1. |
|
Impact |
BIER traffic forwarding fails. |
|
Cause |
This message is generated when BFR IDs of different devices in a sub-domain are the same. |
|
Recommended action |
1. Identify the conflicting BFR edge devices through the BFR prefixes. 2. Modify the BFR ID for one of the two edge devices. |
BIER_BFRID_CONFLICT_CLEAR
|
Message text |
The BFR ID conflict was removed. Address family=[STRING], Sub-domain=[INT32], BFR ID=[INT32], BFR prefix=[STRING]. |
|
Variable fields |
$1: Address family, which can only be IPv6. $2: BIER sub-domain ID. $3: BFR ID. $4: BFR prefixes where the conflict was removed. |
|
Severity level |
5 (Notification) |
|
Example |
BIERRIB/5/BIER_BFRID_CONFLICT_CLEAR: -MDC=1; The BFR ID conflict was removed. Address family=IPv6, Sub-domain=1, BFR ID=4, BFR prefix=B::1. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when a BFR ID conflict is removed. |
|
Recommended action |
1. No action is required. |
BRAS_COM messages
This section contains common BRAS messages.
BRAS_FUNC
|
Message text |
Not enough resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DBRAS/4/BRAS_FUNC: -MDC=1 -Slot=4; Not enough resources. |
|
Impact |
The BRAS service rate-limiting feature does not take effect. |
|
Cause |
The rate-limiting feature does not take effect because the BRAS service rate-limiting profile does not have sufficient resources in either of the following scenarios: · Assign the maximum number of users through the RADIUS server by using standard attribute 62 (Port-Limit) to a user. · Use the users-per-account command to set the maximum number of users allowed to access by using a single account in the ISP domain to which a user belongs. |
|
Recommended action |
1. Log off unnecessary users based on the actual situation. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
BRIPRO messages
This section contains BRIPRO messages.
CFD_CFG_NOTSPT
|
Message text |
Interface [INT32].does not support CFD. Please check your configuration. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
BRIPRO/6/CFD_CFG_NOTSPT: -Slot=3; Interface XGE3/0/1 does not support CFD. Please check your configuration. |
|
Impact |
No impact on the system. |
|
Cause |
The interface does not support CFD. |
|
Recommended action |
Do not configure CFD on the interface. |
LAGG_SHARE_NOT_SPT
|
Message text |
Link aggregation load sharing not supported. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
BRIPRO/6/LAGG_SHARE_NOT_SPT: -MDC=1-Slot=2; Link aggregation load sharing not supported. |
|
Impact |
An aggregation group containing ports on certain card models does not support global load sharing mode configuration. Aggregation groups containing ports on other cards are not affected. |
|
Cause |
An aggregation group does not support the set global load sharing modes if its member ports are on certain cards. |
|
Recommended action |
· Adjust the global load sharing mode for link aggregation based on services. · If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support. |
PVST_NOT_SUPPORT
|
Message text |
PVST is not supported on this board. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
BRIPRO/6/PVST_NOT_SUPPORT: -MDC=1-Slot=5; PVST is not supported on this board. |
|
Impact |
The card does not support PVST. |
|
Cause |
PVST was enabled on a card that does not support this feature. |
|
Recommended action |
· Do not configure PVST on the cards that do not support this feature. · If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support. |
VLAN_TPID_CFGERR
|
Message text |
Operation failed because TPID value [INT32] was configured on [STRING]. Restore TPID value to default on this interface and try again. |
|
Variable fields |
$1: TPID value in the SVLAN tag. $2: Interface name. |
|
Severity level |
2 (Critical) |
|
Example |
BRIPRO/2/VLAN_TPID_CFGERR: -MDC=1-Slot=4; Operation failed because TPID value 2000 was configured on Bridge-Aggregation200. Restore TPID value to default on this interface and try again. |
|
Impact |
The TPID cannot be set for SVLANs on an interface. |
|
Cause |
, only one interface can be configured with a TPID value in the SVLAN tag other than the default TPID value. Restore the TPID value in the SVLAN tag to the default for the interface prompted in the message before you modify the TPID value on the target interface. |
|
Recommended action |
1. To configure the TPID for an SVLAN: ¡ Use the undo qinq ethernet-type service-tag command to restore the default TPID for the SVLAN tag. Then, use the qinq ethernet-type service-tag hex-value command to set the TPID for the SVLAN tag. ¡ Use the undo dot1q ethernet-type command to restore the TPID of the SVLAN tag to 0x8100 for incoming and outgoing packets, Then, use the dot1q ethernet-type command to set the TPID of the SVLAN tag for the incoming and outgoing packets. 2. If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support. |
CFD messages
This section contains CFD messages.
HRD_TIMER_NORES
|
Message text |
No hardware resource for CFD detecting. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
CFD/4/HRD_TIMER_NORES: -MDC=1-Slot=5; No hardware resource for CFD detecting. |
|
Impact |
The CFD feature is not available. |
|
Cause |
The CFD feature is not available because of insufficient hardware timer resources. |
|
Recommended action |
1. Use the display bfd working-mode command to view the resource usage. 2. Cancel the CFD configuration related to unnecessary Layer 2 VPN services, and then reconfigure CFD. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
HRD_MEPNODE_NORES
|
Message text |
No hardware resource for ServiceInstance (INT32) MEP (INT32) RMEP (INT32). |
|
Variable fields |
$1: Service instance ID. $2: Local MEP ID. $3: Remote MEP ID. |
|
Severity level |
4 (Warning) |
|
Example |
CFD/4/HRD_MEPNODE_NORES: -MDC=1-Slot=5; No hardware resource for ServiceInstance(1) MEP(2) RMEP(3). |
|
Impact |
The CFD feature is not available. |
|
Cause |
The CFD feature is not available because of insufficient hardware memory space. |
|
Recommended action |
1. Use the display resource-monitor command to view the resource usage of hard_bfd_counter_resource. 2. Cancel the CFD configuration related to unnecessary Layer 2 VPN services, and then reconfigure CFD. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
COUNTERID_NORES
|
Message text |
No hardware resource for ServiceInstance (INT32) MEP (INT32). |
|
Variable fields |
$1: Service instance ID. $2: Local MEP ID. |
|
Severity level |
4 (Warning) |
|
Example |
CFD/4/COUNTERID_NORES: -MDC=1-Slot=5; No hardware resource for ServiceInstance(1) MEP(2). |
|
Impact |
The CFD feature is not available. |
|
Cause |
The CFD feature is not available because of insufficient hardware counter resources. |
|
Recommended action |
1. Use the display resource-monitor command to view the resource usage of hard_bfd_counter_resource. 2. Cancel the CFD configuration related to unnecessary Layer 2 VPN services, and then reconfigure CFD. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
WATCHDOG_NORES
|
Message text |
No hardware resource for ServiceInstance (INT32) MEP (INT32) RMEP (INT32). |
|
Variable fields |
$1: Service instance ID. $2: Local MEP ID. $3: Remote MEP ID. |
|
Severity level |
4 (Warning) |
|
Example |
CFD/4/WATCHDOG_ADDR_NORES: -MDC=1-Slot=5; No hardware resource for ServiceInstance(1) MEP(2) RMEP(3). |
|
Impact |
The CFD feature is not available. |
|
Cause |
The CFD feature is not available because of insufficient hardware memory resources. |
|
Recommended action |
1. Use the display resource-monitor command to view the resource usage of cfd_watchdog_index. 2. Cancel the CFD configuration related to unnecessary Layer 2 VPN services, and then reconfigure CFD. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CFD messages
This section contains CFD messages.
CFD_CROSS_CCM
|
Message text |
MEP [UINT16] in SI [INT32] received a cross-connect CCM. Its 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 (Informational) |
|
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. |
|
Impact |
Continuity check cannot be performed. |
|
Cause |
The MEPs at the two ends have inconsistent MD and MA settings, levels, or directions. |
|
Recommended action |
Check the configurations of MEPs on both ends. Make sure the MEPs have consistent configurations, including MD, MA, and level. |
CFD_ERROR_CCM
|
Message text |
MEP [UINT16] in SI [INT32] received an error CCM. Its 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 (Informational) |
|
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. |
|
Impact |
Continuity check cannot be performed. |
|
Cause |
· The CCM intervals are in consistent on both ends. · The remote MEP ID is not included in the MEP list of the local end. |
|
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 (Informational) |
|
Example |
CFD/6/CFD_LOST_CCM: MEP 1 in SI 7 failed to receive CCMs from RMEP 2. |
|
Impact |
Continuity check cannot be performed. |
|
Cause |
· The CCM intervals are in consistent on both ends. · A link failure occurs. |
|
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 (Informational) |
|
Example |
CFD/6/CFD_NO_HRD_RESOURCE: -MDC=1; Failed to start CCM on service instance 7 because of insufficient hardware frequency resources. |
|
Impact |
CC cannot be performed. |
|
Cause |
Insufficient hardware frequency resources. |
|
Recommended action |
Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
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 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
CFD performs delay or packet loss measurement with alarm threshold configured. The frame delay or MEP packet loss rate 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 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
CFD performs single-ended synthetic LM with alarm threshold configured. The 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 (Informational) |
|
Example |
CFD/6/ CFD_REACH_UPPERLIMIT: Far-end frame loss ratio reached or exceeded the upper limit 80% on MEP 1 in service instance 3. |
|
Impact |
· The link delay is high. · Link congestion or packet loss occurs. |
|
Cause |
CFD performs frame delay or packet loss measurement with alarm threshold configured. The frame delay or MEP packet loss rate reaches or exceeds the upper limit for three consecutive times. |
|
Recommended action |
Check whether overloaded traffic exists in the network and whether a link issue exists. |
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 (Informational) |
|
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. |
|
Impact |
Link congestion or packet loss occurs. |
|
Cause |
CFD performs single-ended synthetic LM with alarm threshold configured. The single-ended synthetic LM reaches or exceeds the upper limit for three consecutive times. |
|
Recommended action |
Check whether overloaded traffic exists in the network and whether a link issue exists. |
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 (Informational) |
|
Example |
CFD/6/CFD_RECEIVE_CCM: MEP 1 in SI 7 received CCMs from RMEP 2. |
|
Impact |
No negative impact on the system |
|
Cause |
A MEP received CCMs from a remote MEP. |
|
Recommended action |
No action is required. |
CFGMAN messages
This section contains configuration management messages.
CFGMAN_CFGCHANGED
|
Message text |
-EventIndex=[INT32]-CommandSource=[STRING]-ConfigSource=[ISTRING]-ConfigDestination=[STRING]; 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 (Notification) |
|
Example |
CFGMAN/5/CFGMAN_CFGCHANGED: -EventIndex=6-CommandSource=snmp-ConfigSource=startup-ConfigDestination=running; Configuration changed. |
|
Impact |
If this issue occurs when a service module actively accesses DBM, the system might repeatedly generate this message. |
|
Cause |
This message is generated when one of the following conditions exists: · The user performs an operation, such as issuing a command or performing SNMP or NETCONF operations, causing configuration information changes in DBM. · The user performs a configuration file-related operation, for example, deleting, renaming, moving, or saving the configuration file. · The user downloads and overwrites the configuration file through FTP/TFTP. · A service module actively accesses DBM, causing configuration information changes in DBM. |
|
Recommended action |
· If this message is generated because the user performs an operation, no action is required. · If this issue is generated when a service module actively accesses DBM, the service module might run incorrectly. In this situation, contact Technical Support. |
CFGMAN_OPTCOMPLETION
|
Message text |
-OperateType=[STRING]-OperateTime=[INT32]-OperateState=[STRING]-OperateEndTime=[INT32]; Operation completed. |
|
Variable fields |
$1: User line name. If the system failed to obtain the user line name, this field displays two asterisks (**). $2: IP address of the user. If the system failed to obtain the IP address, this field displays two asterisks (**). $3: Username. If the system failed to obtain the username, this field displays two asterisks (**). |
|
Severity level |
5 (Notification) |
|
Example |
CFGMAN/5/CFGMAN_EXIT_FROM_CONFIGURE: Line=con0, IP address=**, user=**; Exit from the system view or a feature view to the user view. |
|
Impact |
No negative impact on the system. |
|
Cause |
The user exited from system view or a feature view to user view. |
|
Recommended action |
No action is required. |
CFG_SAVE_SAVE_FAILURE
|
Message text |
Automatic running configuration saving was not executed because the status of [STRING] is fault. |
|
Variable fields |
$1: Slot number of the failed card. |
|
Severity level |
4 (Warning) |
|
Example |
CFGMAN/4/CFGMAN_SAVE_FAILURE: Automatic running configuration saving was not executed because the status of chassis 1 slot 0 subslot 1 is fault. |
|
Impact |
The configuration cannot be saved on the card. |
|
Cause |
The card failed. |
|
Recommended action |
Execute the display device command to check the card status, resolve the card failure, and the save the configuration again. |
CLK messages
This section contains clock monitoring messages.
CLK_GET_CFG_OK
|
Message text |
Get clock global config succeed. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DSYSM/5/CLK_GET_CFG_OK: -MDC=1; Get clock global config succeed. |
|
Impact |
No negative impact on the system. |
|
Cause |
The following global clock settings were obtained successfully: · Whether the SSM quality level is used in automatic reference selection. · Cock reference selection mode. |
|
Recommended action |
No action is required. |
CLK_TRACE_CHG
|
Message text |
Traced reference change alarm, current traced reference of chassis [INT32] is [INT32]. |
|
Variable fields |
$1: IRF member device ID. $2: Clock source ID. |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_TRACE_CHG: -MDC=1; Traced reference change alarm, current traced reference of chassis 1 is 9. |
|
Impact |
No negative impact on the system. |
|
Cause |
The clock reference traced by the device changed. |
|
Recommended action |
No action is required. |
CLK_TRACE_CHG
|
Message text |
Traced reference change alarm, current traced reference is [INT32]. |
|
Variable fields |
$1: Clock source ID. |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_TRACE_CHG: -MDC=1; Traced reference change alarm, current traced reference is 9. |
|
Impact |
No negative impact on the system. |
|
Cause |
The clock reference traced by the device changed. |
|
Recommended action |
No action is required. |
CLK_TRACE_NOREF
|
Message text |
Traced reference change alarm, no reference traced now. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
DRIVER/3/CLK_TRACE_NOREF: -MDC=1; Traced reference change alarm, no reference traced now. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device did not have a clock reference to trace. |
|
Recommended action |
1. Use the display network-clock status command to display the operating state of the network clock monitoring module. ¡ If the device uses automatic reference selection, ensure link connectivity between the device and clock source. ¡ If the device uses manual reference selection, first use the display network-clock source command to display the states of all clock sources. Then use the network-clock work-mode manual source command to specify a clock reference in normal state as the clock reference. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CLK_REF_RECOVER
|
Message text |
Reference [INT32] is recovered. |
|
Variable fields |
$1: Clock source ID. |
|
Severity level |
3 (Error) |
|
Example |
DRIVER/3/CLK_REF_RECOVER: -MDC=1; References 5 is recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
The clock reference of the device recovered to normal state. Only a clock source in normal state can be selected as the clock reference. To display the states of clock sources, execute the display network-clock source command. |
|
Recommended action |
No action is required. |
CLK_REF_LOST
|
Message text |
Reference [INT32] is lost. |
|
Variable fields |
$1: Clock source ID. |
|
Severity level |
5 |
|
Example |
DRIVER/3/CLK_REF_LOST: -MDC=1; References 5 is lost. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
· The link between the device and the clock source was disconnected. · The line clock input port went down. |
|
Recommended action |
1. Ensure link connectivity between the device and the clock source. 2. Check if the line clock input port on the device is down. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CLK_ALLREF_LOST
|
Message text |
All references are lost. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_ALLREF_LOST: -MDC=1; All references are lost. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
· The links between the device and the clock sources were disconnected. · The line clock input port went down. |
|
Recommended action |
1. Ensure link connectivity between the device and the clock sources. 2. Check if the line clock input port on the device is down. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CLK_PTP_PRICHG
|
Message text |
Priority alarm, current priority of PTP is [INT32]. |
|
Variable fields |
$1: PTP clock priority. |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_PTP_PRICHG: -MDC=1; Priority alarm, current priority of PTP is 8. |
|
Impact |
No negative impact on the system. |
|
Cause |
The PTP clock priority was changed. |
|
Recommended action |
No action is required. |
CLK_REF_PRICHG
|
Message text |
Priority alarm, current priority of reference [INT32] is [INT32]. |
|
Variable fields |
$1: Clock source ID. $2: Clock priority. |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_SSM_CHG: -MDC=1; SSM level alarm, current SSM level of reference 2 1 is SSUB. |
|
Impact |
No negative impact on the system. |
|
Cause |
The priority of a clock source was changed. |
|
Recommended action |
No action is required. |
CLK_SSM_CHG
|
Message text |
SSM level alarm, current SSM level of reference [INT32] is [STRING]. |
|
Variable fields |
$1: Clock source ID. $2: SSM quality level. |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_SSM_CHG: -MDC=1; SSM level alarm, current SSM level of reference 2 is SSUB. |
|
Impact |
No negative impact on the system. |
|
Cause |
The SSM quality level of a clock source was changed. |
|
Recommended action |
No action is required. |
CLK_PTPSSM_CHG
|
Message text |
SSM level alarm, current SSM level of PTP is [STRING]. |
|
Variable fields |
$1: SSM quality level. |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_PTPSSM_CHG: -MDC=1; SSM level alarm, current SSM level of PTP is SSUA. |
|
Impact |
No negative impact on the system. |
|
Cause |
The SSM quality level of the PTP clock was changed. |
|
Recommended action |
No action is required. |
CLK_LOCKED
|
Message text |
Phase lock alarm, current phase lock mode is [STRING]. |
|
Variable fields |
$1: Phase lock state. |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_LOCKED: -MDC=1; Phase lock alarm, current phase lock mode is Locked. DRIVER/5/CLK_LOCKED: -MDC=1; Phase lock alarm, current phase lock mode is Holdover. DRIVER/5/CLK_LOCKED: -MDC=1; Phase lock alarm, current phase lock mode is Freerun. |
|
Impact |
No negative impact on the system. |
|
Cause |
The phase lock state of the clock monitoring module changed. |
|
Recommended action |
No action is required. |
CLK_SSM_OUTLEVEL
|
Message text |
SSM out level alarm, current SSM out level is [STRING]. |
|
Variable fields |
$1: SSM quality level. |
|
Severity level |
5 (Notification) |
|
Example |
DRIVER/5/CLK_SSM_OUTLEVEL: -MDC=1; SSM out level alarm, current SSM out level is SSUB. |
|
Impact |
No negative impact on the system. |
|
Cause |
The SSM quality level of the selected clock reference was changed. |
|
Recommended action |
No action is required. |
DrvDebug
|
Message text |
Failed to receive ToD signals from the GPS device. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; Failed to receive ToD signals from the GPS device. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The FPGA detected anomalies in ToD signals from the GPS device. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
Failed to receive 1PPS signals from the GPS device. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; Failed to receive 1PPS signals from the GPS device. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The FPGA detected anomalies in 1PPS signals from the GPS device. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
On the MPU, the FPGA failed to transmit frequency signals to the clock chip. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; On the MPU, the FPGA failed to transmit frequency signals to the clock chip. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The clock chip detected anomalies in 8 KHz signals from the FPGA. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
The clock chip on the MPU failed to distribute frequency signals to the FPGA. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; The clock chip on the MPU failed to distribute frequency signals to the FPGA. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The FPGA detected anomalies in 8 KHz signals from the clock chip. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
The clock chip on the MPU failed to distribute 1PPS signals to the FPGA. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; The clock chip on the MPU failed to distribute 1PPS signals to the FPGA. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The FPGA detected anomalies in 1PPS signals from the clock chip. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
The MPU failed to distribute ToD signals to the interface module. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The MPU failed to distribute ToD signals to the interface module. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The interface module logic detected anomalies in ToD signals from the MPU. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
The MPU failed to distribute 1PPS signals to the interface module. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The MPU failed to distribute 1PPS signals to the interface module. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The interface module logic detected anomalies in 1PPS signals from the MPU. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
The MPU failed to distribute frequency signals to the interface module. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The MPU failed to distribute frequency signals to the interface module. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The interface module clock chip detected anomalies in frequency signals from the MPU. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
The interface module failed to distribute frequency signals to the interface. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The interface module failed to distribute frequency signals to the interface. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The interface module clock chip detected anomalies in frequency signals from the base card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
The interface failed to transmit frequency signals to the interface module. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The interface failed to transmit frequency signals to the interface module. |
|
Impact |
The user services get stuck and users go offline. |
|
Cause |
The interface module clock chip detected anomalies in frequency signals from the interface. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SFE_CLK_SOURCE
|
Message text |
Npu clock source MPA, p1 = %lu |
|
Variable fields |
%lu: Clock reference change result. · 0: Successful. · Other value than 0: Failed. |
|
Severity level |
6 (Informational) |
|
Example |
BSP/6/ SFE_CLK_SOURCE: -MDC=1-Slot=18; Npu clock source MPA, p1 = 0 |
|
Impact |
No negative impact on the system. |
|
Cause |
The clock reference of the SFE-A switching fabric module changed to the downstream clock port on the MPU in slot 0. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help if the switching fails. |
|
Message text |
Npu clock source MPB, p1 = %lu |
|
Variable fields |
%lu: Clock reference change result. · 0: Successful. · Other value than 0: Failed. |
|
Severity level |
6 (Informational) |
|
Example |
BSP/6/ SFE_CLK_SOURCE: -MDC=1-Slot=19; Npu clock source MPB, p1 = 0 |
|
Impact |
No negative impact on the system |
|
Cause |
The clock reference of the SFE-A switching fabric module changed to the downstream clock port of the MPU in slot 1. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help if the switching fails. |
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 (Warning) |
|
Example |
CLKM/4/CLKM_ESMC_PKT_ALARM: ESMC packets were lost. (PortName=G1/0/1) |
|
Impact |
The running state of SyncE might be affected. |
|
Cause |
In SSM standard mode, an Ethernet port was configured as the clock source and no ESMC message was received within 5 seconds. |
|
Recommended action |
To resolve the issue, execute the display esmc command on both the local and remote devices: 1. View the ESMC status field to identify whether ESMC is enabled. If this feature is not enabled, execute the esmc enable command in interface view to enable this feature on the related interface. 2. View the Interface and Port status fields to identify whether the ESMC interface is in Up state. If the state of the interface is not Up, troubleshoot the interface and restore its state to Up. 3. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
CLKM_SOURCE_FREQDEVIATION_ALARM
|
Message text |
The frequency offset of the clock reference for [STRING] has crossed the threshold. |
|
Variable fields |
$1: Device or chassis ID. |
|
Severity level |
4 (Warning) |
|
Example |
CLKM/4/CLKM_SOURCE_FREQDEVIATION_ALARM: The frequency offset of the clock reference for chassis 1 has crossed the threshold. |
|
Impact |
The running state of SyncE might be affected. |
|
Cause |
The clock frequency deviation crossed the threshold. |
|
Recommended action |
To resolve the issue: 1. Execute the display network-clock freq-deviation-detect command to view information about clock frequency deviation detection. 2. Log in to the clock source, identify whether the clock source provides correct clock signals: ¡ If the clock source provides normal clock signals, execute the network-clock freq-deviation-threshold command in the system view of the local device to adjust the clock frequency deviation threshold. ¡ If the clock source provides abnormal clock signals, execute the network-clock freq-deviation-source elect disable command in the system view of the local device to disable clocks with abnormal frequency deviation status from competing in clock reference election. When the clock source provides normal clock signals, execute the network-clock freq-deviation-source elect recover command in the system view of the local device to restore the frequency deviation status of the clock source to normal. This operation enables the clock source to compete in the clock reference election. Support for the network-clock freq-deviation-source elect disable and network-clock freq-deviation-source elect recover commands varies by device model. 3. If the issue persists, collect configuration data and alarm information, and then contact Technical Support for help. |
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 (Warning) |
|
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. |
|
Impact |
The running state of SyncE might be affected. |
|
Cause |
The clock frequency deviation resumed to normal. |
|
Recommended action |
To resolve the issue, execute the display network-clock source command to view information about the clock sources. · If the State field in the command output displays Normal, no action is required. · If the State field in the command output does not display Normal, execute the display network-clock freq-deviation status command to view the frequency deviation status of clock signals received by the device. If both the Frequency deviation detection and Reference selection by clock source with deviated frequency fields display Enabled, the line clock source is disabled from competing in clock reference election. You must execute the network-clock freq-deviation-source elect recover command in interface view to restore the frequency deviation status of the clock source to normal. This operation enables the clock source to compete in the clock reference election. Support for the network-clock freq-deviation-source elect recover command varies by device model. If the issue persists, collect configuration data and alarm information, and then contact Technical Support for help. |
CLKM_SOURCE_LOST
|
Message text |
|
|
Variable fields |
$1: Device or chassis ID. |
|
Severity level |
4 (Warning) |
|
Example |
CLKM/4/CLKM_SOURCE_LOST: Chassis 1 has lost signals from the clock reference. |
|
Impact |
Clock reference switchover might be triggered. |
|
Cause |
A link failure occurred or the line clock input port went down. |
|
Recommended action |
To resolve the issue: 1. Execute the display network-clock source command to view information about the clock sources, and then use the Reference and State fields in the command output to find the interface associated with the failed line clock source. 2. Execute the display interface command to view the reason why the interface went down, and then troubleshoot the interface accordingly. 3. Log in to the clock source, and then identify whether the clock source can run correctly. If it runs incorrectly, repair it or replace it with a new clock source. |
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 (Warning) |
|
Example |
CLKM/4/CLKM_SOURCE_SSM_DEGRADE: The SSM quality level of the clock reference for chassis 1 has degraded from SSU-A to SEC. The SSM quality level threshold is SSU-A. |
|
Clock reference switchover might be triggered. |
|
|
· Reason 1: The SSM level received on the port decreased. · Reason 2: The SSM level configured on the port decreased. · Reason 3: The SSM level decreased, because a link failure occurred or the port went down. |
|
|
Recommended action |
The actions vary by issue cause as follows: · For reason 1, log in to the clock source, and then identify whether the clock source can run correctly. If it runs incorrectly, repair it or replace it with a new clock source. · For reason 2, no action is required. · For reason 3, take the following actions: 1. Execute the display network-clock source command to view information about the clock sources, and then use the Reference and State fields in the command output to find the interface associated with the failed line clock source. 2. Execute the display interface command to view the reason why the interface went down, and then troubleshoot the interface accordingly. |
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 (Warning) |
|
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. |
|
No negative impact on the system. |
|
|
Cause |
The SSM quality level of the clock reference resumed to the acceptable ranges. |
|
Recommended action |
No action is required. |
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 (Warning) |
|
Example |
CLKM/4/CLKM_SOURCE_SSM_SWITCHOVER: The clock reference of chassis 1 has changed to BITS0. |
|
Impact |
No negative impact on the system. |
|
Cause |
· Reason 1: The network-clock work-mode manual source command was executed to specify a new clock reference. · Reason 2: A better clock source appeared. · Reason 3: A link failure occurred or the port went down. |
|
Recommended action |
The actions vary by issue cause as follows: · For reason 1 or reason 2, no action is required. · For reason 3, take the following actions: 1. Execute the display network-clock source command to view information about the clock sources, and then use the Reference and State fields in the command output to find the interface associated with the failed line clock source. 2. Execute the display interface command to view the reason why the interface went down, and then troubleshoot the interface accordingly. |
CONNLMT messages
This section contains connection limit messages.
CONNLMT_IPV4_OVERLOAD
|
Message text |
RcvIfName(1023)=[STRING];Protocol(1001)=[STRING];SrcIPAddr(1003)=[IPADDR];DstIPAddr(1007)=[IPADDR];ServicePort(1071)=[UINT16];RcvVPNInstance(1042)=[STRING];SndVPNInstance(1043)=[STRING];SndDSLiteTunnelPeer(1041)=[STRING];UpperLimit(1049)=[UINT32];LimitRuleNum(1051)=[UINT16];Event(1048)=[STRING]; |
|
Variable fields |
$1: Global, or interface name. $2: Transport layer protocol type. $3: Source IP address. $4: Destination IP address. $5: Service port number. $6: Source VPN instance name. $7: Destination VPN instance name. $8: Peer tunnel ID. $9: Upper threshold. $10: Rule ID. $11: Event message. |
|
Severity level |
6 (Informational) |
|
Example |
CONNLMT/6/CONNLMT_IPV4_OVERLOAD: RcvIfName(1023)=Global;Protocol(1001)=;SrcIPAddr(1003)=10.10.10.1;DstIPAddr(1007)=;ServicePort(1071)=;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;SndDSLiteTunnelPeer(1041)=;UpperLimit(1049)=1000;LimitRuleNum(1051)=1;Event(1048)=Exceeds upper threshold; |
|
Impact |
New connections matching the rule cannot be established. |
|
Cause |
The number of concurrent connections exceeded the upper threshold. |
|
Recommended action |
No action is required. |
CONNLMT_IPV4_RECOVER
|
Message text |
RcvIfName(1023)=[STRING];Protocol(1001)=[STRING];SrcIPAddr(1003)=[IPADDR];DstIPAddr(1007)=[IPADDR];ServicePort(1071)=[UINT16];RcvVPNInstance(1042)=[STRING];SndVPNInstance(1043)=[STRING];SndDSLiteTunnelPeer(1041)=[STRING];DropPktCount(1052)=[UINT32];LowerLimit(1050)=[UINT32];LimitRuleNum(1051)=[UINT16];Event(1048)=[STRING]; |
|
Variable fields |
$1: Global, or interface name. $2: Transport layer protocol type. $3: Source IP address. $4: Destination IP address. $5: Service port number. $6: Source VPN instance name. $7: Destination VPN instance name. $8: Peer tunnel ID. $9: Number of dropped packets. $10: Lower threshold. $11: Rule ID. $12: Event message. |
|
Severity level |
6 (Informational) |
|
Example |
CONNLMT/6/CONNLMT_IPV4_RECOVER: RcvIfName(1023)=Global;Protocol(1001)=;SrcIPAddr(1003)=10.10.10.1;DstIPAddr(1007)=;ServicePort(1071)=;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;SndDSLiteTunnelPeer(1041)=;DropPktCount(1052)=306004;LowerLimit(1050)=10;LimitRuleNum(1051)=1;Event(1048)=Reduces below lower threshold; |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of concurrent connections dropped to the lower threshold from the upper threshold. |
|
Recommended action |
No action is required. |
CONNLMT_IPV6_OVERLOAD
|
Message text |
RcvIfName(1023)=[STRING];Protocol(1001)=[STRING];SrcIPv6Addr(1036)=[IPADDR];DstIPv6Addr(1037)=[IPADDR];ServicePort(1071)=[UINT16];RcvVPNInstance(1042)=[STRING];SndVPNInstance(1043)=[STRING];SndDSLiteTunnelPeer(1041)=[STRING];UpperLimit(1049)=[UINT32];LimitRuleNum(1051)=[UINT16];Event(1048)=[STRING]; |
|
Variable fields |
$1: Global, or interface name. $2: Transport layer protocol type. $3: Source IPv6 address. $4: Destination IPv6 address. $5: Service port number. $6: Source VPN instance name. $7: Destination VPN instance name. $8: Peer tunnel ID. $9: Upper threshold. $10: Rule ID. $11: Event message. |
|
Severity level |
6 (Informational) |
|
Example |
CONNLMT/6/CONNLMT_IPV6_OVERLOAD: RcvIfName(1023)=Global;Protocol(1001)=;SrcIPv6Addr(1036)=2001::1;DstIPv6Addr(1037)=;ServicePort(1071)=;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;SndDSLiteTunnelPeer(1041)=;UpperLimit(1049)=1000;LimitRuleNum(1051)=1;Event(1048)=Exceeds upper threshold; |
|
Impact |
New connections matching the rule cannot be established. |
|
Cause |
The number of concurrent connections exceeded the upper threshold. |
|
Recommended action |
No action is required. |
CONNLMT_IPV6_RECOVER
|
Message text |
RcvIfName(1023)=[STRING];Protocol(1001)=[STRING];SrcIPv6Addr(1036)=[IPADDR];DstIPv6Addr(1037)=[IPADDR];ServicePort(1071)=[UINT16];RcvVPNInstance(1042)=[STRING];SndVPNInstance(1043)=[STRING];SndDSLiteTunnelPeer(1041)=[STRING];DropPktCount(1052)=[UINT32];LowerLimit(1050)=[UINT32];LimitRuleNum(1051)=[UINT16];Event(1048)=[STRING]; |
|
Variable fields |
$1: Global, or interface name. $2: Transport layer protocol type. $3: Source IPv6 address. $4: Destination IPv6 address. $5: Service port number. $6: Source VPN instance name. $7: Destination VPN instance name. $8: Peer tunnel ID. $9: Number of dropped packets. $10: Lower threshold. $11: Rule ID. $12: Event message. |
|
Severity level |
6 (Informational) |
|
Example |
CONNLMT/6/CONNLMT_IPV6_RECOVER: RcvIfName(1023)=Global;Protocol(1001)=;SrcIPAddr(1003)=2001::1;DstIPAddr(1007)=;ServicePort(1071)=;RcvVPNInstance(1042)=;SndVPNInstance(1043)=;SndDSLiteTunnelPeer(1041)=;DropPktCount(1052)=306004;LowerLimit(1050)=10;LimitRuleNum(1051)=1;Event(1048)=Reduces below lower threshold; |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of concurrent connections dropped to the lower threshold from the upper threshold. |
|
Recommended action |
No action is required. |
DEV messages
This section contains device management messages.
CPLD_STAT_CONFLICT
|
Message text |
The CPLD on the standby MPU in slot [INT32] mistakenly reported a switchover to the active MPU role. The active MPU is in slot [INT32]. |
|
Variable fields |
$1: Slot number of the standby MPU. $2: Slot number of the active MPU. |
|
Severity level |
4 (Warning) |
|
Example |
DEVD/4/CPLD_STAT_CONFLICT: -MDC=1-Slot=0; The CPLD on the standby MPU in slot 0 mistakenly reported a switchover to the active MPU role. The active MPU is in slot 1. |
|
Impact |
The message is reported mistakenly, which does not impact the system. |
|
Cause |
The CPLD on the standby MPU mistakenly reported a switchover to the active MPU role. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DrvDebug
|
Message text |
Over-current occurred to the USB port on the MPU. Please remove and check the USB device. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; Over-current occurred to the USB port on the MPU. Please remove and check the USB device. |
|
Impact |
The connected USB device is not available. |
|
Cause |
The current of a USB port on the MPU is too high. The connected USB device failed. |
|
Recommended action |
1. Replace the USB device. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Temperature of the board is too high! |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DRVPLAT/4/DrvDebug: Temperature of the board is too high! |
|
Impact |
The card might be damaged. |
|
Cause |
The card temperature is too high. Fans failed or the ambient temperature is too high. |
|
Recommended action |
1. Check the ambient temperature. If the ambient temperature is too high, verify that the air conditioner for the room is operating correctly. 2. Verify that the air inlet and outlet for the device are not blocked. 3. Check the fans of the device. If the fans in a fan tray are not operating correctly, replace the fan tray. 4. Verify that all cards are installed correctly and all blank slots are covered by filler panels. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Warning: Chip [INT32] temperature([STRING]) in slot [INT32] is too high, please check it. |
|
Variable fields |
$1: Chip ID. $2: Temperature of the chip. $3: Slot number of the card. |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: Warning:Chip 1 temperature(80) in slot 2 is too high, please check it. |
|
Impact |
The card might fail to operate correctly. |
|
Cause |
The temperature of a chip is too high. |
|
Recommended action |
1. Check the ambient temperature. If the ambient temperature is too high, verify that the air conditioner for the room is operating correctly. 2. Verify that the air outlet for the device is not blocked. 3. Check the fans of the device. If the fans in a fan tray are not operating correctly, replace the fan tray. 4. Verify that all cards are installed correctly and all blank slots are covered by filler panels. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
hotspot [STRING] in slot [INT32] temperature([STRING]) is too high, please check it. |
|
Variable fields |
$1: Hotspot sensor ID. $2: Slot number of the card. $3: Temperature value. |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: hotspot 1 in slot 2 temperature(80) is too high, please check it. |
|
Impact |
The card might fail to operate correctly. |
|
Cause |
A hotspot sensor on a card detected that the temperature was too high. |
|
Recommended action |
1. Check the ambient temperature. If the ambient temperature is too high, verify that the air conditioner for the room is operating correctly. 2. Verify that the air outlet for the device is not blocked. 3. Check the fans of the device. If the fans in a fan tray are not operating correctly, replace the fan tray. 4. Verify that all cards are installed correctly and all blank slots are covered by filler panels. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Warning: cpu temperature([STRING]) in slot [INT32] is too high, please check it. |
|
Variable fields |
$1: Temperature value. $2: Slot number of the card. In IRF mode, this value indicates the global slot number, which is calculated by using the following equation: Global number = (Member ID – 1) * 18 + slot number of the card in the chassis.) |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: Warning: cpu temperature(80) in slot 2 is too high, please check it. |
|
Impact |
The card might fail to operate correctly. |
|
Cause |
The temperature of the CPU on a card is too high. |
|
Recommended action |
1. Check the ambient temperature. If the ambient temperature is too high, verify that the air conditioner for the room is operating correctly. 2. Verify that the air inlet and outlet for the device are not blocked. 3. Check the fans of the device. If the fans in a fan tray are not operating correctly, replace the fan tray. 4. Verify that all cards are installed correctly and all blank slots are covered by filler panels. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Warning: The LPU board on slot [STRING] is not compatible with MPU board. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Warning: The LPU board on slot 4 is not compatible with MPU board. |
|
Impact |
The card might fail to start up. |
|
Cause |
The specified service module has a different device identifier than the MPU. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Warning: Standby board on slot [STRING] is not compatible with MPU board. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Warning: Standby board on slot 1 is not compatible with MPU board. |
|
Impact |
The standby MPU might fail to start up. |
|
Cause |
The specified MPU has different device identification than the active MPU. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Warning: Two power modules have different power specifications. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
Warning: Two power modules have different power specifications. |
|
Impact |
The power modules fail to provide power, which might cause a card to power off randomly. |
|
Cause |
Power modules in the router have different power specifications. |
|
Recommended action |
Use power modules of the same power specifications in the router. |
|
Message text |
Current temperature on slot [STRING] is [STRING] degrees centigrade, which is higher than the shutdown threshold. The board is being shut down. |
|
Variable fields |
$1: Slot number of the card. $2: Temperature. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Current temperature on slot 4 is 101 degrees centigrade, which is higher than the shutdown threshold. The board is being shut down. |
|
Impact |
The card is powered off. |
|
Cause |
The temperature of a card exceeded the shutdown threshold and was going to be shut down. |
|
Recommended action |
1. Verify that all fans are installed firmly. If a fan has been pulled out, install the fan firmly and power on the card after the fan operates correctly. 2. If the issue persists, check the operating status of fans. If one or more fans are not operating correctly, replace the fans. 3. If the issue persists, replace the card or wait for the card to cool down. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
In Mode [STRING], the card in slot [INT32] is not supported. Now rebooting. |
|
Variable fields |
$1: System operating mode of the device. $2: Slot number of the card. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: In Mode sdn-wan, the card in slot 6 is not supported. Now rebooting. |
|
Impact |
The interface module cannot operate correctly in the specified mode. |
|
Cause |
The specified interface module is not supported in the current system operating mode, and is to reboot. |
|
Recommended action |
Determine whether to continue using the specified system operating mode: · To continue using the specified system operating mode, replace the interface module with an interface module that supports the specified system operating mode. · To stop using the specified system operating mode, execute the system-working-mode command to specify a new system operating mode. |
|
Message text |
The card in slot [UINT32] failed to start up. The card is not compatible with the chassis. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; The card in slot 4 failed to start up. The card is not compatible with the chassis. |
|
Impact |
The card cannot start up. |
|
Cause |
The specified card was not compatible with the chassis. |
|
Recommended action |
1. Replace the card with a card that is compatible with the chassis. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help |
|
Message text |
Power supply in power [UINT32] became abnormal. The power supply might be powered off. |
|
Variable fields |
$1: Power supply slot. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1;Power supply in power 1 became abnormal. The power supply might be powered off. |
|
Impact |
The power supply for the system is abnormal. |
|
Cause |
The system detected a power supply failure. The power supply might be powered off. |
|
Recommended action |
· Check the power supply on the device. · Replace the abnormal power supply. |
SFC_CHANGED
|
Message text |
Warning: Short circuit sfc has been changed, it will take effect only after system restart. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DEVD/4/SFC_CHANGED:Warning: Short circuit sfc has been changed, it will take effect only after system restart. |
|
Impact |
Traffic cannot be forwarded correctly. |
|
Cause |
The number of switching fabric modules was reduced, and the chassis is no longer fully configured with switching fabric modules. You must reboot the system for the switching fabric modules to take effect. |
|
Recommended action |
Reboot the system. |
DEV
This section contains device management messages.
AUTOSWITCH_FAULT
|
Message text |
[STRING] automatically switches between active and standby, and a fault occurs during the switching. |
|
Variable fields |
$1: Chassis number. |
|
Severity level |
1 (Alert) |
|
Example |
DEV/1/AUTOSWITCH_FAULT: Chassis 1 automatically switches between active and standby, and a fault occurs during the switching. |
|
Impact |
A primary/backup switchover fails. |
|
Cause |
This message is generated when a fault occurs during the primary/backup switchover process. |
|
Recommended action |
· Manually restart the device to resolve the issue. Before restarting the device, execute the display diagnostic-information command to collect and save diagnostic information for troubleshooting. · After the device restarts, execute the display device command to view the device state. If the state is not Normal, the issue is not resolved. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
AUTOSWITCH_FAULT_REBOOT
|
Message text |
[STRING] automatically switches between active and standby, and a fault occurs during the switching, the device will immediately restart [STRING] to restore the fault. |
|
Variable fields |
$1: Chassis number. $2: Chassis number and slot number or slot number. |
|
Severity level |
1 (Alert) |
|
Example |
DEV/1/AUTOSWITCH_FAULT_REBOOT: Chassis 1 automatically switches between active and standby, and a fault occurs during the switching, the device will immediately restart chassis 1 slot 0 to restore the fault. |
|
Impact |
The card is about to restart and will be temporarily unavailable. |
|
Cause |
The device will automatically switch over from active to standby. If a fault occurs during the switchover process, the device will immediately restart the faulty card to recover from the fault. This message is generated when the faulty card restarts. |
|
Recommended action |
After the faulty card restarts, you can execute the display device command to check the card status. If the state is not Normal, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
2 (Critical) |
|
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.) |
|
Impact |
No negative impact on the system. |
|
Cause |
A critical alarm is 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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
2 (Critical) |
|
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.) |
|
Impact |
Services on the card might be affected. |
|
Cause |
A critical alarm occurs on the card. |
|
Recommended action |
1. Review the alarm information. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BOARD_FATALALARM_CLEAR
|
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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
1 (Alert) |
|
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.) |
|
Impact |
The services on the card might be impacted. |
|
Cause |
This message is generated in one for following conditions: · A slot is not installed with a card of the corresponding type, causing the system operation failure. · The system is no installed with the required type of switching fabric module or service module. For more information, see fault cause description. |
|
Recommended action |
1. Use the display device command to check the operating state of the card. Make sure the card is in normal operation. 2. If the card is running correctly but the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BOARD_INSERTED
|
Message text |
Board was inserted on [STRING], type is unknown. |
|
Variable fields |
$1: Chassis number and slot number or slot number. |
|
Severity level |
5 (Notification) |
|
Example |
DEV/5/BOARD_INSERTED: Board was inserted on slot 1, type is unknown. |
|
Impact |
No negative impact on the system. |
|
Cause |
After a card is inserted, it takes some time to complete the card startup. This message is generated during this period. |
|
Recommended action |
No action is required. |
BOARD_REBOOT
|
Message text |
Board is rebooting on [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. |
|
Severity level |
5 (Notification) |
|
Example |
DEV/5/BOARD_REBOOT: Board is rebooting on slot 1. |
|
Impact |
The card is to stop providing services and restart. |
|
Cause |
A user is restarting the card or the card restarts abnormally. |
|
Recommended action |
1. Identify whether a user is restarting the card. 2. If no user restarts the card, wait for the card to finish the restart, and then execute the display version command to identify the restart reason the Last reboot reason field.. 3. If the card restarts abnormally, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Error) |
|
Example |
DEV/3/BOARD_REMOVED: Board was removed from slot 1, type is LSQ1FV48SA. |
|
Impact |
The card is not available. |
|
Cause |
An LPU or standby MPU is removed from the device and the device exits the IRF fabric. |
|
Recommended action |
1. If the card is removed, no action is required. 2. If no card is removed, perform the following operations: 3. Identify whether the card is installed correctly. If the card is not installed correctly, re-install the card. 4. Identify whether the card is damaged. If the card is damaged, replace the card. 5. Add the device to the IRF fabric again. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BOARD_STATE_FAULT
|
Message text |
Board state changed to Fault on [STRING], type is [STRING]. |
|
Variable fields |
$1: Chassis number and slot number or slot number. $2: Card type. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/BOARD_STATE_FAULT: Board state changed to Fault on slot 1, type is LSQ1FV48SA. |
|
Impact |
The card is not available. |
|
Cause |
A card will be in Fault state when one of the following conditions are met: · The card is in the startup phase (initializing or loading software version), and the card is not available. · The card cannot operate properly. |
|
Recommended action |
Based on the log, the recommended actions are as follows based on the cause in the log message: · If the card is in the startup phase, the loaded software version and the startup time vary by card model. Typically, the startup time does not exceed 10 minutes. · If the card cannot operate correctly, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Notification) |
|
Example |
DEV/5/BOARD_STATE_NORMAL: Board state changed to Normal on slot 1, type is LSQ1FV48SA. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when a new LPU or standby MPU finishes initialization. This does not indicate that configuration recovery is completed. You cannot perform a primary/standby switchover when this message is generated. |
|
Recommended action |
No action is required. |
CFCARD_FAILED
|
Message text |
CF card state changed to Fault in [STRING] [STRING]. |
|
Variable fields |
$1: Device or chassis number + slot number or slot number $2: Slot number where the CF card is located (only supported by products with multiple CF cards) |
|
Severity level |
3 (Error) |
|
Example |
DEV/3/CFCARD_FAILED: CF card state changed to Fault in slot 1 CF card slot 1. |
|
Impact |
The CF card is not available. |
|
Cause |
This message is generated when the CF card is faulty. |
|
Recommended action |
1. Identify whether the CF card is installed correctly. If the CF card is not installed correctly, re-install the CF card. 2. Identify whether the CF card is damaged. If the CF card is damaged, replace the CF card. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CFCARD_INSERTED
|
Message text |
CF card was inserted in [STRING] [STRING]. |
|
Variable fields |
$1: Device or chassis number + slot number or slot number $2: Slot number where the CF card is located (only supported by products with multiple CF cards) |
|
Severity level |
4 (Warning) |
|
Example |
DEV/4/CFCARD_INSERTED: CF card was inserted in slot 1 CF card slot 1. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when the CF card is installed in the specified slot. |
|
Recommended action |
No action is required. |
CFCARD_REMOVED
|
Message text |
CF card was removed from [STRING] [STRING]. |
|
Variable fields |
$1: Device or chassis number + slot number or slot number $2: Slot number where the CF card is located (only supported by products that support multiple CF cards) |
|
Severity level |
3 (Error) |
|
Example |
DEV/3/CFCARD_REMOVED: CF card was removed from slot 1 CF card slot 1. |
|
Impact |
The CF card is not available |
|
Cause |
This message is generated when the CF card is removed from the device. |
|
Recommended action |
1. If the CF card is removed, no action is needed 2. If the CF card is not removed, identify whether the CF card is installed correctly. If the CF card is not installed correctly, re-install the CF card. 3. Identify whether the CF card is damaged. If the CF card is damaged, replace the CF card 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CHASSIS_REBOOT
|
Message text |
Chassis [STRING] is rebooting now. |
|
Variable fields |
$1: Chassis number. |
|
Severity level |
5 (Notification) |
|
Example |
DEV/5/CHASSIS_REBOOT: Chassis 1 is rebooting now. |
|
Impact |
The member device is about stop providing services and restart. |
|
Cause |
A user is restarting the member device, or the member device is restarting due to an anomaly. |
|
Recommended action |
1. Identify whether any user is restarting the member device 2. If no user is restarting the member device, wait for the member device to restart, and then use the display version command to check the Last reboot reason field in the card information for the member device to view the restart reason. 3. If the restart reason is abnormal, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CPU_STATE_NORMAL
|
Message text |
Cpu state changed to Normal on [STRING]. |
|
Variable fields |
$1: Chassis number + slot number + CPU number, or slot number + CPU number. The CPU number is displayed only if multiple CPUs are supported. |
|
Severity level |
5 (Notification) |
|
Example |
DEV/5/CPU_STATE_NORMAL: Cpu state changed to Normal on slot 1 cpu 1. |
|
Impact |
No negative impact on the system. |
|
Cause |
The CPU status changed to normal. |
|
Recommended action |
No action is required. |
DEV_BOARD_RUNNING_FAULT
|
Message text |
[STRING] is detected to be faulty. |
|
Variable fields |
$1: Chassis number and slot number or slot number. |
|
Severity level |
1 (Alert) |
|
Example |
DEV/1/DEV_BOARD_RUNNING_FAULT: Chassis 1 slot 0 is detected to be faulty. |
|
Impact |
Services on the card might be affected. |
|
Cause |
This message is generated when a fault occurs on a card during the device operation. |
|
Recommended action |
· Manually restart the faulty card. Before restarting the card, you can execute the display diagnostic-information command to collect and save diagnostic information for fault location. · After restarting the card, you can execute the display device command to check the card status. If the state is not Normal, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DEV_BOARD_RUNNING_FAULT_REBOOT
|
Message text |
[STRING] is detected to be faulty, the device will immediately restart [STRING] to recover from 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 (Alert) |
|
Example |
DEV/1/DEV_BOARD_RUNNING_FAULT_REBOOT: Chassis 1 slot 0 is detected to be faulty, the device will immediately restart chassis 1 slot 0 to recover from the fault. |
|
Impact |
The card will restart soon and will be temporarily unavailable. |
|
Cause |
When a fault occurs on the card during the device operation, the device will immediately restart the card to recover from the fault. |
|
Recommended action |
After the card automatically restarts, you can execute the display device command to check the device status. If the card status is not Normal, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DEV_CLOCK_CHANGE
|
Message text |
-User=[STRING]-IPAddr=[IPADDR]; System clock changed from [STRING] to [STRING]. |
|
Variable fields |
$1: Username of the current logged-in user $2: IP address of the current logged-in user $3: Old time $4: New time |
|
Severity level |
5 (Notification) |
|
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. |
|
Impact |
The background timing program might fail. |
|
Cause |
This message is generated when the system time changes. Possible reasons include: · The administrator manually changes the system time. · The clock protocol automatically changes the system time. |
|
Recommended action |
1. Check the background timing program configuration. 2. Modify the background timing program that automatically failed. |
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: Duration of the status. |
|
Severity level |
4 (Warning) |
|
Example |
DEV/4/DEV_FAULT_TOOLONG: Card in slot 1 is still in Fault state for 60 minutes. |
|
Impact |
The card is not available. |
|
Cause |
This message is generated if the card remains in Fault state for a long time. |
|
Recommended action |
1. Restart the card. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DEV_REBOOT_UNSTABLE
|
Message text |
A reboot command was executed while the system status was not Stable. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DEV/5/DEV_REBOOT_UNSTABLE: A reboot command was executed while the system status was not Stable. |
|
Impact |
The system is to stop providing services and restart. |
|
Cause |
The reboot command was executed while the system status was not stable. |
|
Recommended action |
Do not execute the reboot command while the system is starting up. It takes some time for the system to enter Stable state. If the system does not enter Stable state after a period, perform the following tasks: 1. Execute the display system stable state command to identify the components that are not in Stable state. 2. Troubleshoot the components that are not in Stable state. |
DEV_SAVE_DIAGFILE
|
Message text |
Diagnostic information saved to file [STRING] successfully. |
|
Variable fields |
$1: Full path of the file for saving diagnostic information. |
|
Severity level |
6 (Informational) |
|
Example |
DEV/6/DEV_SAVE_DIAGFILE: Diagnostic information saved to file flash:/diag_H3C_20210425-103409.tar.gz successfully. |
|
Impact |
No negative impact on the system. |
|
Cause |
Diagnostic information has been saved successfully. |
|
Recommended action |
No action is required. |
DEV_SAVE_DIAGFILE_INTERRUPT
|
Message text |
Diagnostic information saved to file [STRING] interrupted by a new collection directive. |
|
Variable fields |
$1: Full path of the file for saving diagnostic information. |
|
Severity level |
6 (Informational) |
|
Example |
DEV/6/DEV_SAVE_DIAGFILE_INTERRUPT: Diagnostic information saved to file /flash:/diag_H3C_20210425-103910.tar.gz interrupted by a new collection directive. |
|
Impact |
No negative impact on the system. |
|
Cause |
The diagnostic information collection task in progress in the background is interrupted by a new directive for collecting diagnostic information. |
|
Recommended action |
No action is required. |
FAN_ABSENT
|
Message text |
Pattern 1: Fan [INT32] is absent. Pattern 2: Chassis [STRING] fan [INT32] is absent. |
|
Variable fields |
Pattern 1: $1: Fan number Pattern 2: $1: Chassis number. $2: Fan number. |
|
Severity level |
3 (Error) |
|
Example |
DEV/3/FAN_ABSENT: Fan 2 is absent. |
|
Impact |
Heat dissipation in the system might be affected. |
|
Cause |
This message is generated when the fan module is not installed in the specified slot or is removed from the device. |
|
Recommended action |
1. If the fan module is not installed in the specified slot, it might cause poor heat dissipation and lead to an increase in device temperature. As a best practice, install the fan module. 2. If the fan module is removed, no action is required 3. If the fan module is not removed, identify whether the fan module is installed correctly, such as whether the fan module is not inserted tightly and the fan module is damaged. If the fan module is damaged, replace the fan module 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/FAN_ALARM_CLEAR: Fan alarm cleared. (PhysicalIndex=199, PhysicalName=Fan 2, RelativeResource=0, ErrorCode=300020, Reason=Fan tray is not present.) |
|
Impact |
No negative impact on the system. |
|
Cause |
A critical fan 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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/FAN_ALARM_OCCUR: Fan alarm occurred. (PhysicalIndex=199, PhysicalName=Fan 2, RelativeResource=0, ErrorCode=300020, Reason=Fan tray is not present.) |
|
Impact |
Heat dissipation in the system might be affected. |
|
Cause |
This message is generated when a critical fan failure occurs. |
|
Recommended action |
1. Verify that the fan module is installed correctly. If the fan module is not installed correctly, re-install the fan module. 2. If the alarm is not cleared, replace the fan module. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
FAN_DIRECTION_NOT_PREFERRED
|
Message text |
Fan [INT32] airflow direction is not preferred [STRING], please check it. |
|
Variable fields |
$1: Fan number. $2: Chassis number and slot number or slot number. |
|
Severity level |
1 (Alert) |
|
Example |
DEV/1/FAN_DIRECTION_NOT_PREFERRED: Fan 1 airflow direction is not preferred slot 1, please check it. |
|
Impact |
Heat dissipation in the system might be affected. |
|
Cause |
The airflow direction of the fan tray is different from the airflow direction setting. |
|
Recommended action |
1. Choose a fan model with the same airflow direction as the ventilation system in the equipment room. 2. If the fan airflow direction is consistent with the ventilation system in the equipment room, adjust the fan airflow direction configuration. |
FAN_FAILED
|
Message text |
Pattern 1: Fan [INT32] failed. Pattern 2: Chassis [STRING] fan [INT32] failed. |
|
Variable fields |
Pattern 1: $1: Fan number. Pattern 2: $1: Chassis number. $2: Fan number. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/FAN_FAILED: Fan 2 failed. |
|
Impact |
Heat dissipation might be affected. |
|
Cause |
The fan has malfunctioned and stopped working. |
|
Recommended action |
Replace the fan. |
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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
1 (Alert) |
|
Example |
DEV/1/FAN_FATALALARM_CLEAR: Fan fatal alarm cleared. (PhysicalIndex=199, PhysicalName=Fan 2, RelativeResource=0, ErrorCode=300016, Reason=The fan resumed running.) |
|
Impact |
No negative impact on the system. |
|
Cause |
A critical alarm on the fan was cleared. |
|
Recommended action |
No action is required. |
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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
1 (Alert) |
|
Example |
DEV/1/FAN_FATALALARM_OCCUR: Fan fatal alarm occurred. (PhysicalIndex=199, PhysicalName=Fan 2, RelativeResource=0, ErrorCode=300016, Reason=The fan stopped running.) |
|
Impact |
Heat dissipation might be affected. |
|
Cause |
A critical alarm occurs on the fan. |
|
Recommended action |
1. Verify that the fan module is installed correctly. If the fan module is not installed correctly, re-install the fan module. 2. If the alarm is not cleared, replace the fan module. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
FAN_RECOVERED
|
Message text |
Pattern 1: Fan [INT32] recovered. Pattern 2: Chassis [INT32] fan [INT32] recovered. |
|
Variable fields |
Pattern 1: $1: Fan number. Pattern 2: $1: Chassis number. $2: Fan number. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/FAN_RECOVERED: Fan 2 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
Insert the fan, shortly after, the fan will switch to the normal operating state. |
|
Recommended action |
No action is required. |
MAD_DETECT
|
Message text |
Multi-active devices detected, please fix it. |
|
Variable fields |
No |
|
Severity level |
1 (Alert) |
|
Example |
DEV/1/MAD_DETECT: Multi-active devices detected, please fix it. |
|
Impact |
IRF split into two IRF systems, only one of which can continue to work, while the other cannot |
|
Cause |
This message is generated when an IRF fabric is split into two separate IRF fabrics, with only one able to continue operating while the other cannot. |
|
Recommended action |
1. Use display irf to check which member devices are currently in the IRF, to determine which member devices have been split. 2. Use display irf link to check the faulty IRF link. 3. Fix the IRF link in DOWN state. |
MAD_PROC
|
Message text |
[STRING] protocol detected MAD conflict: Local health value=[UINT32], Peer health value=[UINT32]. |
|
Variable fields |
$1: Detected protocol names causing MAD conflicts are ARP, ND, LACP, BFD $2: Health value of local IRF $3: Health value of peer IRF when MAD conflict is detected |
|
Severity level |
6 (Informational) |
|
Example |
DEV/6/MAD_PROC: ARP protocol detected MAD conflict: Local health value=1, Peer health value=0. |
|
Impact |
IRF splits into two IRF systems, only one of which can continue to operate, while the other IRF system cannot. |
|
Cause |
This message is generated when ARP, ND, LACP, or BFD protocols detect IRF MAD conflicts in an IRF networking environment. |
|
Recommended action |
1. Use display irf to identify which member devices are currently in the IRF to determine which member devices have been split. 2. Use display irf link to locate the faulty IRF link. 3. Fix the IRF links in a DOWN state. |
POWER_ABSENT
|
Message text |
Pattern 1: Power [INT32] is absent. Pattern 2: Chassis [INT32] power [INT32] is absent. |
|
Variable fields |
Pattern 1: $1: Power module ID. Pattern 2: $1: Chassis number. $2: Power module ID. |
|
Severity level |
3 (Error) |
|
Example |
DEV/3/POWER_ABSENT: Power 1 is absent. |
|
Impact |
System power supply might be affected. |
|
Cause |
The power module was removed from the device, or the power module was damaged. |
|
Recommended action |
1. If the power module was removed, no action is required. 2. If the power module was not removed, check the power module connection for the device, such as whether the cable is loose or whether the power module is damaged. If the power module is damaged, replace it. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
2 (Critical) |
|
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.) |
|
Impact |
No negative impact on the system. |
|
Cause |
A critical power 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 position. $4: Fault code. $5: Fault cause description. |
|
Severity level |
2 (Critical) |
|
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.) |
|
Impact |
System power supply might be affected. |
|
Cause |
A critical power alarm occurs. |
|
Recommended action |
1. Execute the display power command to view the power module status. If the power module is in Absent state, the power module is not installed. Verify that the power module is installed correctly. 2. If the power module is installed correctly, replace the power module. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
POWER_FAILED
|
Message text |
Pattern 1: Power [INT32] failed. Pattern 2: Chassis [INT32] power [INT32] failed. |
|
Variable fields |
Pattern 1: $1: Power module ID. Pattern 2: $1: Chassis number. $2: Power module ID. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/POWER_FAILED: Power 1 failed. |
|
Impact |
The power supply in the system might be affected. |
|
Cause |
This message is generated when the power module fails or is just inserted. |
|
Recommended action |
1. If the power module fails, replace it. 2. If the power module is just inserted, verify that the power module is installed correctly. |
POWER_MONITOR_ABSENT
|
Message text |
Pattern 1: Power monitor unit [INT32] is absent. Pattern 2: Chassis [INT32] power monitor unit [INT32] is absent. |
|
Variable fields |
Pattern 1: $1: Power monitoring module ID. Pattern 2: $1: Chassis number. $2: Power monitoring module ID. |
|
Severity level |
3 (Error) |
|
Example |
DEV/3/POWER_MONITOR_ABSENT: Power monitor unit 1 is absent. |
|
Impact |
System power supply might be affected. |
|
Cause |
The power monitoring module was removed from the device, or the power monitoring module failed. |
|
Recommended action |
1. If the power monitoring module is removed, no action is required. 2. If the power monitoring module is not removed, check the connection of the power monitoring module, such as whether the cable is loose and whether the power monitoring module is damaged. If the power monitoring module is damaged, replace it. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
POWER_MONITOR_FAILED
|
Message text |
Pattern 1: Power monitor unit [INT32] failed. Pattern 2: Chassis [INT32] power monitor unit [INT32] failed. |
|
Variable fields |
Pattern 1: $1: Power monitoring module ID. Pattern 2: $1: Chassis number. $2: Power monitoring module ID. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/POWER_MONITOR_FAILED: Power monitor unit 1 failed. |
|
Impact |
System power supply might be affected. |
|
Cause |
The power monitoring module is faulty. |
|
Recommended action |
1. Identify whether the power monitoring module is damaged. If the power monitoring module is damaged, replace it. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
POWER_MONITOR_RECOVERED
|
Message text |
Pattern 1: Power monitor unit [INT32] recovered. Pattern 2: Chassis [INT32] power monitor unit [INT32] recovered. |
|
Variable fields |
Pattern 1: $1: Power monitoring module ID. Pattern 2: $1: Chassis number. $2: Power monitoring module ID. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/POWER_MONITOR_RECOVERED: Power monitor unit 1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
After the power monitoring module is inserted, its state changes from Failed or Absent to OK. |
|
Recommended action |
No action is required. |
POWER_RECOVERED
|
Message text |
Pattern 1: Power [INT32] recovered. Pattern 2: Chassis [INT32] power [INT32] recovered. |
|
Variable fields |
Pattern 1: $1: Power module ID. Pattern 2: $1: Chassis number. $2: Power module ID. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/POWER_RECOVERED: Power 1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
After the power module is inserted, its state changes from Failed or Absent to OK |
|
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 position. $4: Fault code. $5: Fault position. For more information, see the fault code and fault cause description table. |
|
Severity level |
4 (Warning) |
|
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.) |
|
Impact |
No negative impact on the system. |
|
Cause |
A power 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 position. $4: Fault code. $5: Fault position. For more information, see the fault code and fault cause description table. |
|
Severity level |
4 (Warning) |
|
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.) |
|
Impact |
System power supply might be affected. |
|
Cause |
A power alarm occurs. |
|
Recommended action |
1. Execute the display power command to view the power module status. If the power module is in Absent state, the power module is not installed. Verify that the power module is installed correctly. 2. If the power module is installed correctly, replace the power module. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
RPS_ABSENT
|
Message text |
Pattern 1: RPS [INT32] is absent. Pattern 2: Chassis [INT32] RPS [INT32] is absent. |
|
Variable fields |
Pattern 1: $1: Redundant power module ID. Pattern 2: $1: Chassis number. $2: Redundant power module ID. |
|
Severity level |
3 (Error) |
|
Example |
DEV/3/RPS_ABSENT: RPS 1 is absent. |
|
Impact |
System power supply might be affected. |
|
Cause |
The redundant power module was removed from the device, or the redundant power module failed. |
|
Recommended action |
1. If the redundant power module is removed, no action is required. 2. If the redundant power module is not removed, check the connection of the redundant power module, such as whether the cable is loose and whether the redundant power module is damaged. If the power module is damaged, replace it. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
RPS_FAILED
|
Message text |
Pattern 1: RPS [INT32] failed. Pattern 2: Chassis [INT32] RPS [INT32] failed. |
|
Variable fields |
Pattern 1: $1: Redundant power module ID. Pattern 2: $1: Chassis number. $2: Redundant power module ID. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/RPS_FAILED: RPS 2 failed. |
|
Impact |
System power supply might be affected. |
|
Cause |
This message is generated when the redundant power module is not powered on or is faulty. |
|
Recommended action |
1. If the redundant power module was removed, no action is required. 2. If the redundant power module is not removed, check the connection of the redundant power module, such as whether the cable is loose and whether the redundant power module is damaged. If the power module is damaged, replace it. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
RPS_NORMAL
|
Message text |
Pattern 1: RPS [INT32] is normal. Pattern 2: Chassis [INT32] RPS [INT32] is normal. |
|
Variable fields |
Pattern 1: $1: Redundant power module ID. Pattern 2: $1: Chassis number. $2: Redundant power module ID. |
|
Severity level |
5 (Notification) |
|
Example |
DEV/5/RPS_NORMAL: RPS 1 is normal. |
|
Impact |
No negative impact on the system. |
|
Cause |
After the redundant power module is inserted, the status is normal |
|
Recommended action |
No action is required. |
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: Number of the subslot where the subcard resides. $3: Subcard type. |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/SUBCARD_FAULT: Subcard state changed to Fault on slot 1 subslot 1, type is MIM-1ATM-OC3SML. |
|
Impact |
The subcard is not available if it is faulty. |
|
Cause |
This message is generated when the subcard is restarted or is faulty. |
|
Recommended action |
1. If the subsequent subcard status can be changed to Normal, no action is needed 2. If the subcard remains in Fault status, replace it. |
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: Number of the subslot where the subcard resides. $3: Subcard type. |
|
Severity level |
4 (Warning) |
|
Example |
DEV/4/SUBCARD_INSERTED: Subcard was inserted in slot 1 subslot 1, type is MIM-1ATM-OC3SML. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when the subcard is inserted into the device. |
|
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: Number of the subslot where the subcard resides. |
|
Severity level |
5 (Notification) |
|
Example |
DEV/5/SUBCARD_REBOOT: Subcard is rebooting on slot 1 subslot 1. |
|
Impact |
The subcard is about to stop providing services and restart. |
|
Cause |
A user is restarting the subcard or the subcard restarts automatically due to an anomaly. |
|
Recommended action |
1. If the subcard can run normally after restart, no action is needed. 2. To further understand the reason for the abnormal restart or if the subcard keeps restarting automatically, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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: Number of the subslot where the subcard resides. $3: Subcard type. |
|
Severity level |
3 (Error) |
|
Example |
DEV/3/SUBCARD_REMOVED: Subcard was removed from slot 1 subslot 1, type is MIM-1ATM-OC3SML. |
|
Impact |
The subcard is not available. |
|
Cause |
This message is generated when a subcard is removed from the device. |
|
Recommended action |
1. If the subcard was removed, no action is required. 2. If the subcard is not removed, identify whether the subcard is installed correctly. If the subcard is not installed correctly, re-install the subcard. 3. Identify whether the subcard is damaged. If the subcard is damaged, replace it. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SYSTEM_REBOOT
|
Message text |
System is rebooting now. |
|
Variable fields |
N/A |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/SYSTEM_REBOOT: System is rebooting now. |
|
Impact |
The system is about to stop providing services and restart. |
|
Cause |
Identify whether any user is restarting the system or whether the system is restarting due to an anomaly. |
|
Recommended action |
1. Identify whether any user is restarting the system. If no user is restarting the system, wait for the system to restart. Then, use the display version command to view the Last reboot reason field to check the reason for the restart. 2. If the reason for the restart is abnormal, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 ID. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor ID. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor ID. |
|
Severity level |
4 (Warning) |
|
Example |
DEV/4/TEMPERATURE_ALARM: Temperature is greater than the high-temperature alarming threshold on slot 1 sensor inflow 1. |
|
Impact |
High temperature will affect the normal operation of the system. |
|
Cause |
The temperature exceeds the critical (Alarm) high temperature alarm threshold, the ambient temperature is too high, or the fan is abnormal. |
|
Recommended action |
1. Identify whether the temperature in the equipment room is in the acceptable range. Make sure the device is properly ventilated. 2. Execute the display fan command to identify whether the fan was removed or failed, and identify whether the fan was running correctly. If the fan is absent or faulty, install or replace the fan. 3. Use the display environment command to check the current temperature and the effective threshold. If the ambient temperature is too high, adjust the ambient temperature. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 position. $4: Fault code. $5: Fault cause description. $6: Threshold type. $7: Threshold value. $8: Current value. |
|
Severity level |
2 (Critical) |
|
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.) |
|
Impact |
No negative impact on the system. |
|
Cause |
A critical temperature alarm is 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 position. $4: Fault code. $5: Fault ,cause description. $6: Threshold type. $7: Threshold value. $8: Current value. |
|
Severity level |
2 (Critical) |
|
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.) |
|
Impact |
A high temperature will affect the normal operation of the system |
|
Cause |
This message is generated when the temperature of the entity exceeds the alarm threshold. |
|
Recommended action |
1. Identify whether the temperature in the equipment room is in the acceptable range and make sure the device is properly ventilated. 2. Execute the display fan command to identify whether the fan was removed or failed, and identify whether the fan was running correctly. If the fan is absent or faulty, install or replace the fan. 3. Use the display environment command to check the current temperature and the effective threshold. If the ambient temperature is too high, adjust the ambient temperature. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 ID. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor ID. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor ID. |
|
Severity level |
4 (Warning) |
|
Example |
DEV/4/TEMPERATURE_LOW: Temperature is less than the low-temperature threshold on slot 1 sensor inflow 1. |
|
Impact |
Low temperature will affect system operation. |
|
Cause |
This message is generated when the temperature drops below the low temperature alarm threshold. |
|
Recommended action |
1. Identify whether the ambient temperature in the equipment room is too low. If the ambient temperature is too low, improve the ambient temperature. 2. Execute the display fan command to identify whether the fan was removed or failed, and identify whether the fan was running correctly. If the fan is absent or faulty, install or replace the fan. 3. Use the display environment command to check the current temperature and the effective threshold. If the ambient temperature is too high, adjust the ambient temperature. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 ID. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor ID. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor ID. |
|
Severity level |
4 (Warning) |
|
Example |
DEV/4/TEMPERATURE_NORMAL: Temperature changed to normal on slot 1 sensor inflow 1. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when the entity's temperature returns to normal from an abnormal state. |
|
Recommended action |
No action is required. |
TEMPERATURE_POWEROFF
|
Message text |
Powering off [STRING]: Temperature exceeded the shutdown threshold. |
|
Variable fields |
$1: Chassis number + slot number, or slot number |
|
Severity level |
2 (Critical) |
|
Example |
DEV/2/TEMPERATURE_POWEROFF: Powering off slot 1: Temperature exceeded the shutdown threshold. |
|
Impact |
The temperature is too high, which might shut down the system any time. |
|
Cause |
The temperature of the entity exceeds the threshold that can shut down the system. |
|
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 absent, install the fan tray. If a fan tray does not operate correctly, replace it. 3. Use the display environment command to view the current temperature and the temperature thresholds. If the ambient temperature is too high, adjust the ambient temperature as needed. 4. Power on the slot manually. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 ID. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor ID. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor ID. |
|
Severity level |
2 (Critical) |
|
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. |
|
Impact |
High temperature will affect system operation. |
|
Cause |
The temperature exceeds the shutdown-level high temperature alarm threshold, the ambient temperature is too high, or the fan is abnormal. |
|
Recommended action |
1. Identify whether the temperature in the equipment room is in the acceptable range and make sure the device is properly ventilated. 2. Execute the display fan command to identify whether the fan was removed or failed, and identify whether the fan was running correctly. If the fan is absent or faulty, install or replace the fan. 3. Use the display environment command to check the current temperature and the effective threshold. If the ambient temperature is too high, adjust the ambient temperature. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 ID. Pattern 2: $1: Slot number. $2: Sensor type. $3: Sensor ID. Pattern 3: $1: Chassis number. $2: Slot number. $3: Sensor type. $4: Sensor ID. |
|
Severity level |
4 (Warning) |
|
Example |
DEV/4/TEMPERATURE_WARNING: Temperature is greater than the high-temperature warning threshold on slot 1 sensor inflow 1. |
|
Impact |
High temperature will affect system operation. |
|
Cause |
The temperature exceeds the high temperature alarm threshold, or the ambient temperature is too high, or the fan is abnormal. |
|
Recommended action |
1. Identify whether the temperature in the equipment room is in the acceptable range and make sure the device is properly ventilated. 2. Execute the display fan command to identify whether the fan was removed or failed, and identify whether the fan was running correctly. If the fan is absent or faulty, install or replace the fan. 3. Please use the display environment command to check the current temperature and the effective threshold. If the ambient temperature is too high, adjust the ambient temperature 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
VCHK_VERSION_INCOMPATIBLE
|
Message text |
Software version of [STRING] is incompatible with MPU. |
|
Variable fields |
$1: Chassis number + slot number or slot number. |
|
Severity level |
1 (Alert) |
|
Example |
DEV/1/VCHK_VERSION_INCOMPATIBLE: Software version of slot 1 is incompatible with MPU. |
|
Impact |
The card is not available. |
|
Cause |
During startup, PEX detects that its boot software package is incompatible with the software package running on the parent device. In this case, PEX generates this message and restarts. |
|
Recommended action |
1. Set a software package compatible with the current version of the parent device as the next startup software package/load software package for PEX. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 position. $4: Fault code. $5: Fault cause description. $6: Threshold type. $7: Threshold value. $8: Current value. |
|
Severity level |
2 (Critical) |
|
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. ) |
|
Impact |
No negative impact on the system. |
|
Cause |
A critical 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 position. $4: Fault code. $5: Fault cause description. $6: Threshold type. $7: Threshold value. $8: Current value. |
|
Severity level |
2 (Critical) |
|
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.) |
|
Impact |
Voltage abnormality may affect the normal operation of the system |
|
Cause |
A critical voltage alarm occurs. |
|
Recommended action |
1. Execute the display voltage command to identify whether the power module meets the power supply requirements. If it does not meet the power supply requirements, replace the power module. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 position. $4: Fault code. $5: Fault cause. $6: Threshold type. $7: Threshold value with unit. $8: Current value with unit. |
|
Severity level |
1 (Alert) |
|
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) |
|
Impact |
No negative impact on the system. |
|
Cause |
A voltage alert 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 position. $4: Fault code. $5: Fault cause. $6: Threshold type. $7: Threshold value with unit. $8: Current value with unit. |
|
Severity level |
1 (Alert) |
|
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) |
|
Impact |
The abnormal voltage might affect the system operation. |
|
Cause |
An alert voltage alarm occurs. |
|
Recommended action |
1. Execute the display voltage command to identify whether the power module meets the power supply requirements. If it does not meet the power supply requirements, replace the power module. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DEVD
This section contains DEVD messages.
CARD_NOT_CMPT
|
Message text |
The board installed in slot [UINT32] cannot start up. The board model is different from the preprovisioned model. |
|
Variable fields |
$1: Slot number of the card. |
|
Severity level |
3 (Error) |
|
Example |
DEVD/3/CARD_NOT_CMPT: -MDC=1; The board installed in slot 8 cannot start up. The board model is different from the preprovisioned model. |
|
Impact |
The card cannot start up. |
|
Cause |
The specified card cannot start up because the model of the card is different from the preprovisioned model. |
|
Recommended action |
1. Replace the card with a card of the preprovisioned model. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
EDEV_CMD_SET_RSA_RESULT
|
Message text |
Check can't pass! |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DEVD/4/EDEV_CMD_SET_RSA_RESULT: Check can't pass! |
|
Impact |
The card reboot might occur. |
|
Cause |
This message is generated when software images do not exist or are invalid. |
|
Recommended action |
Upload valid software images. |
DHCP
This section contains DHCP messages.
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 (Error) |
|
Example |
DHCP/3/DHCP_NOTSUPPORTED: Failed to apply filtering rules for DHCP packets because some rules are not supported. |
|
Impact |
The system cannot process DHCP packets. |
|
Cause |
The system failed to apply filtering rules for DHCP packets because some rules are not supported on the device. |
|
Recommended action |
Disable unnecessary services to release hardware resources, and then re-configure DHCP. |
DHCP_NORESOURCES
|
Message text |
Failed to apply filtering rules for DHCP packets because hardware resources are insufficient. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
DHCP/3/DHCP_NORESOURCES: Failed to apply filtering rules for DHCP packets because hardware resources are insufficient. |
|
Impact |
The system cannot process DHCP packets. |
|
Cause |
The system failed to apply filtering rules for DHCP packets because the hardware resources are insufficient. |
|
Recommended action |
1. Identify whether the device supports DHCP: ¡ If the device does not support DHCP, no action is required. ¡ If the device supports DHCP, enable DHCP again. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DHCPR
This section contains DHCP relay agent messages.
DHCPR_INVALIDPACKET
|
Message text |
Invalid BOOTP packet received: [STRING]. |
|
Variable fields |
$1: Invalid packets. Options are: · Invalid packet type. · Invalid giaddr. · Invalid magic cookie. |
|
Severity level |
3 (Error) |
|
Example |
DHCPR/3/DHCPR_INVALIDPACKET: Invalid BOOTP packet received: Invalid packet type. |
|
Impact |
The system does not process invalid BOOTP request packets. |
|
Cause |
The BOOTP request packets received on the DHCP relay are invalid. |
|
Recommended actions |
Check the source of the BOOTP request packet by using methods such as port mirroring: · If the packet is from an unauthorized user, ignore this request packet. · If the packet is from an authorized user, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
DHCPR_PACKETLARGEHOP
|
Message text |
BOOTP request discarded: Hop limit exceeded. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DHCPR/4/DHCPR_PACKETLARGEHOP: BOOTP request discarded: Hop limit exceeded. |
|
Impact |
The BOOTP client cannot obtain an address. |
|
Cause |
· The link between the BOOTP client and the DHCP relay has exceptions. · The BOOTP request packet is invalid. |
|
Recommended actions |
· For the link exception between the BOOTP client and DHCP relay: 1. Identify whether an exception between the BOOTP client and DHCP relay, for example, a loop. If the link is abnormal, restore the link status. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. · For invalid BOOTP request packet issue, check the source of the BOOTP request packet by using methods such as port mirroring: · · |
DHCPR_SERVERCHANGE
|
Message text |
· Switched to the server of pool [STRING] at [IPADDR] vrf [STRING] because the current server does not respond. · Switched to the server of interface [STRING] at [IPADDR] vrf [STRING] because the current server does not respond. |
|
Variable fields |
$1: DHCP relay address pool name. $2: Next DHCP server IP address. $3: Interface where DHCP relay is enabled. $4: VPN instance index. |
|
Severity level |
3 (Error) |
|
Example |
DHCPR/3/DHCPR_SERVERCHANGE: -MDC=1; · Switched to the server of pool 1 at 2.2.2.2 vrf 0 because the current server does not respond. DHCPR/3/DHCPR_SERVERCHANGE: -MDC=1; · Switched to the server of interface GigabitEthernet1/0/1 at 2.2.2.2 vrf 0 because the current server does not respond. |
|
Impact |
The DHCP relay agent turns to another DHCP server for IP address acquisition. |
|
Cause |
The DHCP relay agent did not receive any responses from the current DHCP server and switched to another DHCP server in the specified VPN or on the public network for IP address acquisition. |
|
Recommended action |
No action is required. |
DHCPR_SERVERNORESPONSE
|
Message text |
No response received from DHCP server ( [IPADDR] in [STRING], pool [STRING] ) because of the reason: [STRING]. |
|
Variable fields |
$1: DHCP server address. $2: VPN instance name. This parameter is displayed as N/A on the public network. $3: Address pool name. $4: Reason why the DHCP server did not respond: · No route to the DHCP server. · DHCP server too busy. · DHCP server pool exhausted. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPR/4/DHCPR_SERVERNORESPONSE: No response received from DHCP server ( 10.1.1.1 in vpn1, pool pool1 ) because of the reason: No route to the DHCP server. |
|
Impact |
The DHCP client cannot obtain an address. |
|
Cause |
· Reason why the DHCP server did not respond: · No route to the DHCP server. · DHCP server too busy. · DHCP server pool exhausted. |
|
Recommended actions |
· If the No route to the DHCP server or DHCP server too busy message is displayed: 1. Check the link status between the DHCP relay and the DHCP server. If the link is abnormal, restore the link. 2. If the issue persists, verify that the DHCP configuration is correct on the DHCP relay and DHCP server. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. · If the DHCP server pool exhausted message is displayed: 4. Re-plan the address pool resources, such as assigning multiple address pools to a group or expanding the existing pool by adding secondary network segments. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
DHCPR_SWITCHMASTER
|
Message text |
Switched to the master DHCP server at [IPADDR] vrf [STRING]. |
|
Variable fields |
$1: IP address of the master DHCP server. $2: VPN instance index. |
|
Severity level |
3 (Error) |
|
Example |
DHCPR/3/DHCPR_SWITCHMASTER: -MDC=1; Switched to the master DHCP server at 2.2.2.2 vrf 0. |
|
Impact |
The DHCP relay agent turns to the master DHCP server for IP address acquisition. |
|
Cause |
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. |
DHCPR6
This section contains DHCPv6 relay agent messages.
DHCPR6_SERVERNORESPONSE
|
Message text |
No response received from DHCP server ( [IPADDR] in [STRING], pool [STRING] ) because of the reason: [STRING]. |
|
Variable fields |
$1: IP address of the DHCPv6 server. $2: VPN instance name. This field displays N/A for the public network. $3: Name of the IPv6 address pool. $4: Reason why the DHCPv6 server did not respond: · No route to the DHCPv6 server—No route to the DHCPv6 server exists. · DHCPv6 server too busy—The DHCPv6 server was too busy. · DHCPv6 server pool exhausted—The DHCPv6 server had no assignable IPv6 addresses. · DHCPv6 server prefix exhausted—The DHCPv6 server had no assignable IPv6 prefixes. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPR6/4/DHCPR6_SERVERNORESPONSE: No response received from DHCP server ( 10::1 in vpn1, pool pool1 ) because of the reason: No route to the DHCPv6 server. |
|
Impact |
The user cannot obtain an IPv6 address to come online. |
|
Cause |
· Reason 1: The DHCPv6 relay agent did not have a route to the DHCPv6 server. · Reason 2: The DHCPv6 server was busy. · Reason 3: The DHCPv6 server does not have assignable addresses in its address pools. · Reason 4: The DHCPv6 server does not have assignable prefixes in its address pools. |
|
Recommended action |
For reason 1 or reason 2, take the following actions: 1. Identify whether the link between the DHCPv6 relay agent and the DHCPv6 server is normal. If the link is abnormal, restore the link to normal. If the issues persists after the link is restored to normal, go to step b. 2. Check for incorrect DHCPv6 settings on the DHCPv6 relay agent and the DHCPv6 server, and then correct them (if any). If the issues persists when all DHCPv6 settings on the DHCPv6 relay agent and the DHCPv6 server are correct, go to step c. 3. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. For reason 3 or reason 4, replan and increase address pool resources. For example, you can increase address pool resources as follows: 4. Use the ipv6 pool-group command to create an IPv6 address pool group, and then add multiple address pools to the address pool group. 5. Use the undo authorization-attribute ipv6-pool command in ISP domain view to remove the current authorization IPv6 address pool attribute. 6. Use the authorization-attribute ipv6-pool-group command in ISP domain view to specify the IPv6 address pool group for users. If the issue persists after you increase address pool resources, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
DHCPS messages
This section contains DHCP server (DHCPS) 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 (Notification) |
|
Example |
DHCPS/5/ALLOCATE_IP: DHCP server received a DHCP client’s request packet on interface GigabitEthernet1/0/2, and allocated an IP address 1.0.0.91(lease 86400 seconds) for the DHCP client(MAC 0000-0000-905a) from p1 pool. |
|
Impact |
No negative impact on the system. |
|
Cause |
The DHCP server assigned an IPv4 address lease to a DHCP client. |
|
Recommended action |
No action is required. |
DHCPS_ALLOC_USERIP_FAILED
|
Message text |
IP allocation failed in domain [STRING] because of the reason: [STRING]. |
|
Variable fields |
$1: Name of the ISP domain. $2: Reason why the DHCP server failed the IP allocation: · UP information mismatch. · No authorized pool or pool-group exists or the interface is not on the network specified for the matching pool. · No free lease in the matching pool or pool-group. · Creating lease failed. · Pool misconfiguration on the relay agent. · Other. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCPS_ALLOC_USERIP_FAILED: IP allocation failed in domain domain1 because of the reason: UP information mismatch. |
|
The DHCP client fails to obtain an IP address, and cannot come online. |
|
|
Cause |
The log message is generated possibly because: · The UP information is not matching. · No authorization address pool or pool group exists or the interface is not on the network segment specified for the matching address pool. · No free lease exists in the matching address pool or pool group. · Lease creation fails. · The address pool settings are incorrect on the DHCP relay agent. |
|
Recommended action |
1. Verify that all necessary address pool settings are correct on the DHCP relay agent and the DHCP server. 2. Replan address pool resources or address pool group resources to ensure sufficient address resources. You can use one of the following methods to increase address resources: ¡ Bind more address pools to the current address pool group. ¡ Add secondary network segments for dynamic address allocation in the current address pools. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS_ANTIFLOOD_DISABLE_FAILURE
|
Message text |
Failed to disable DHCP flood protection function on the interface [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: Reason why DHCP flood protection failed to be disabled: · Not enough resources: Insufficient resources. · Configuration already exists: The configuration already exists. · Not found: The interface does not exist. · Configuration not supported: The configuration is not supported. · Unknown error: Unknown reason. |
|
Severity level |
3 (Error) |
|
Example |
DHCPS/3/DHCPS_ANTIFLOOD_DISABLE_FAILURE: -MDC=1; Failed to disable DHCP flood protection function on the interface GigabitEthernet1/0/1. Reason: Configuration not supported. |
|
Impact |
DHCP flood protection is still enabled on the interface. |
|
Cause |
This message is generated when you disable global DHCP flood protection and this feature fails to be disabled on an interface. |
|
Recommended action |
Execute the display dhcp flood-protection command to view the enabling status of global DHCP flood protection: · If this feature is enabled, disable this feature again. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. · If this feature is disabled, view this message to locate the cause of this issue. ¡ If this issue occurs because the device is busy with services and hardware resources are insufficient, wait a minute or close unnecessary services, and then disable global DHCP flood protection again. ¡ If the issue persists after troubleshooting, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DHCPS_ANTIFLOOD_ENABLE_FAILURE
|
Message text |
Failed to enable DHCP flood protection function on the interface [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: Reason why DHCP flood protection failed to be enabled: · Not enough resources: Insufficient resources. · Configuration already exists: The configuration already exists. · Not found: The interface does not exist. · Configuration not supported:The configuration is not supported. · Unknown error: Unknown reason. |
|
Severity level |
3 (Error) |
|
Example |
DHCPS/3/DHCPS_ANTIFLOOD_ENABLE_FAILURE: -MDC=1; Failed to enable DHCP flood protection function on the interface GigabitEthernet1/0/1. Reason: Configuration not supported. |
|
Impact |
DHCP flood protection is still disabled on the interface. |
|
Cause |
This message is generated when you enable global DHCP flood protection and this feature fails to be enabled on an interface. |
|
Recommended action |
Execute the display dhcp flood-protection command to view the enabling status of global DHCP flood protection: · If this feature is disabled, enable this feature again. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. · If this feature is enabled, view this message to locate the cause of this issue. ¡ If this issue occurs because the device is busy with services and hardware resources are insufficient, wait a minute or close unnecessary services, and then enable global DHCP flood protection again. ¡ If the issue persists after troubleshooting, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
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 (Notification) |
|
Example |
DHCPS/5/DHCPS_CONFLICT_IP: A conflict IP 100.1.1.1 from p1 pool was detected by DHCP server on interface GigabitEthernet1/0/2. |
|
Impact |
The conflicting IPv4 address cannot be assigned. |
|
Cause |
The address pool contains an IPv4 interface address of the DHCP server. |
|
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 (Notification) |
|
Example |
DHCPS/5/DHCPS_EXTEND_IP: DHCP server received a DHCP client’s request packet on interface GigabitEthernet1/0/2, and extended lease from p1 pool for the DHCP client (IP 1.0.0.91, MAC 0000-0000-905a). |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
DHCPS/4/DHCPS_FILE: Failed to save DHCP client information due to lack of storage resources. |
|
The DHCP server failed to save DHCP client information, and the related DHCP client cannot come online. |
|
|
Cause |
A new user attempted to come online when the DHCP server did not have sufficient storage resources. |
|
Recommended action |
Delete unnecessary files to release storage resources. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DHCPS_FLOOD_ATTACK
|
Message text |
A DHCP flood attack exists because the number of DHCP packets that interface [STRING] receives from client (MAC [MAC]) has exceeded the limit within the specified detection period. |
|
Variable fields |
$1: Name of the interface that received DHCP packets. $2: MAC address of the attacker. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS/5/DHCPS_FLOOD_ATTACK: A DHCP flood attack exists because the number of DHCP packets that interface [STRING] receives from client (MAC [MAC]) has exceeded the limit within the specified detection period. |
|
The DHCP flood attack protection feature will drop the attack packets that exceed the upper limit. |
|
|
Cause |
This log message is generated when the following conditions exist: · DHCP flood attack protection is enabled on the interface. · The number of incoming DHCP packets from the same MAC address reaches the upper limit in the detection duration, the DHCP device determines that the client is launching a DHCP flood attack. |
|
Recommended action |
Use the display dhcp flood-protection command to view the operating state of the DHCP flood attack protection feature and information about DHCP flood attack protection entries. |
DHCPS_NET_THRESHOLD_EXCEED
|
Message text |
The subnet usage of address pool [STRING] has reached or exceeded the threshold. |
|
Variable fields |
$1: IP address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS/5/DHCPS_NET_THRESHOLD_EXCEED: The subnet usage of address pool pool1 has reached or exceeded the threshold. |
|
Impact |
If the DHCP server continues to assign subnets from the address pool to clients, the address pool might run out of address resources. As a result, new DHCP users cannot obtain addresses and thus cannot come online. |
|
Cause |
The usage of assignable subnets in an address pool has reached or exceeded the threshold. |
|
Recommended action |
To resolve this issue: 1. Use the display ip pool command in any view to identify whether the subnet usage threshold specified for the current address pool is appropriate: ¡ If the subnet usage threshold is too low, increase the threshold. ¡ If the subnet usage threshold is appropriate, go to step 2. 2. Use the display dhcp server statistics command in any view to view the subnet usage of the current address pool and the number of assignable subnets in the current address pool: ¡ If the assignable subnets are insufficient, increase subnet resources for the address pool. For example, you can add the current address pool and other address pools to an address pool group, or add secondary network segments for dynamic subnet allocation in the current address pool. ¡ If the assignable addresses are sufficient, keep observing the subnet usage of the current address pool. When the address pool has a high subnet usage, increase subnet resources timely to ensure that new DHCP users can obtain addresses. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS_NET_THRESHOLD_REC
|
Message text |
The subnet usage of pool [STRING] has descended to or dropped below 90% of the threshold. |
|
Variable fields |
$1: IP address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS/5/DHCPS_NET_THRESHOLD_REC: The subnet usage of pool pool1 has descended to or dropped below 90% of the threshold. |
|
Impact |
|
|
Cause |
Some subnets in an address pool are reclaimed, and the usage of assignable subnets in that address pool has dropped to or below 90% of the threshold. |
|
Recommended action |
No action is required. |
DHCPS_NET_EXHAUST
|
Message text |
Address pool [STRING] has run out of assignable subnets. |
|
Variable fields |
$1: IP address pool name. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCPS_NET_EXHAUST: Address pool pool1 has run out of assignable subnets. |
|
Impact |
New DHCP users cannot obtain addresses and thus cannot come online. |
|
Cause |
An address pool has run out of subnet resources. |
|
Recommended action |
To resolve this issue: 1. Use one of the following methods to increase subnet resources: ¡ Add the current address pool and other address pools to an address pool group. ¡ Add secondary network segments for dynamic subnet allocation in the current address pool. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS_NET_EXHAUSTREC
|
Message text |
The subnet usage of pool [STRING] has descended to or dropped below 90%. |
|
Variable fields |
$1: IP address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS/5/DHCPS_NET_EXHAUSTREC: The subnet usage of pool pool1 has descended to or dropped below 90%. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some subnets in an address pool are reclaimed, and the usage of assignable subnets in that address pool has dropped to or below 90%. |
|
Recommended action |
No action is required. |
DHCPS_PACKET_ATTACK
|
Message text |
The device might be under a DHCP packet attack. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS/5/DHCPS_PACKET_ATTACK: The device might be under a DHCP packet attack. |
|
Impact |
Memory resources might be insufficient, and the related services cannot run correctly. |
|
Cause |
The device is under a DHCP packet attack and might trigger memory usage alarms. |
|
Recommended action |
Enable a DHCP attack prevention feature, such as DHCP flood attack protection or DHCP packet rate limiting. |
DHCPS_POOLGP_EXHAUSTION
|
Message text |
Pool group [STRING] has run out of IP addresses. |
|
Variable fields |
$1: Name of the IP address pool group. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCPS_POOLGP_EXHAUSTION: Pool group group1 has run out of IP addresses. |
|
Impact |
New DHCP users might fail to obtain addresses and thus cannot come online. |
|
Cause |
An IP address pool group has run out of IP addresses. |
|
Recommended action |
To resolve this issue: 1. Use one of the following methods to increase address resources for the address pool group: ¡ Add new address pools to the address pool group. ¡ Add secondary network segments for address pools in the address pool group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS_POOLGP_EXHAUSTION_RECOV
|
Message text |
IP address usage of pool group [STRING] has dropped to or below 90%. |
|
$1: Name of the IP address pool group. |
|
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCPS_POOLGP_EXHAUSTION_RECOV: IP address usage of pool group group1 has dropped to or below 90%. |
|
No negative impact on the system. |
|
|
Some IP addresses in an address pool group are reclaimed, and the IP address usage of that address pool group has dropped to or below 90%. |
|
|
Recommended action |
DHCPS_POOLGP_THRESHOLD_EXCEED
|
Message text |
IP address usage of pool group [STRING] has exceeded the threshold. |
|
Variable fields |
$1: Name of the IP address pool group. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCPS_POOLGP_THRESHOLD_EXCEED: IP address usage of pool group group1 has exceeded the threshold. |
|
Impact |
If the DHCP server continues to assign IP addresses from the address pool group to clients, the address pool group might run out of addresses. As a result, new DHCP users cannot obtain IP addresses and thus cannot come online. |
|
The IP address usage of an IP address pool group has exceeded the threshold. |
|
|
Recommended action |
To resolve this issue: 1. Use the display ip pool-group command in any view to identify whether the address usage threshold specified in the current address pool group is appropriate. ¡ If the address usage threshold is too low, increase the threshold. ¡ If the address usage threshold is appropriate, proceed to step 2. 2. Use the display dhcp server statistics command in any view to view the address usage of the current address pool group and the number of assignable addresses in the current address pool group. ¡ If the assignable addresses are insufficient, increase address resources for the address pool group. For example, you can add new address pools to the address pool group, or add secondary network segments for address pools in the address pool group. ¡ If the assignable addresses are sufficient, keep observing the address usage of the current address pool group. When the address pool group has a high address usage, increase address resources timely to ensure that new DHCP users can obtain addresses. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS_POOLGP_THRESHOLD_RECOV
|
Message text |
IP address usage of pool group [STRING] has dropped to or below 90% of the threshold. |
|
Variable fields |
$1: Name of the IP address pool group. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCPS_POOLGP_THRESHOLD_RECOV: IP address usage of pool group group1 has dropped to or below 90% of the threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some IP addresses in an address pool group are reclaimed, and the IP address usage of that address pool group has dropped to or below 90% of the threshold. |
|
Recommended action |
No action is required. |
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 (Notification) |
|
Example |
DHCPS/5/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). |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when one of the following conditions exists: · Lease information is deleted through CLI. · The client sends a DHCP-RELEASE message to the DHCP server. · The address lease expires, because the client does not renew the lease. |
|
Recommended action |
No action is required. |
DHCPS_ROUTE_ADD
|
Message text |
UNR route ( Destination [STRING], Nexthop [STRING], Tunnel-destination [STRING] ) added for pool [STRING]. |
|
Variable fields |
$1: Destination network. $2: Next hop of the network route. $3: Destination of the tunnel. If no tunnel is configured, this field displays N/A. $4: Name of the IP address pool. |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS/6/DHCPS_ROUTE_ADD: UNR route ( Destination 10.1.1.1/24, Nexthop 0.0.0.0, Tunnel-destination N/A ) added for pool pool1. |
|
Impact |
Network traffic can reach the network segment at which the client is located. |
|
Cause |
The local device automatically generates a UNR for the IP address pool. For example, the export-route keyword is specified when the network command is configured on the device. |
|
Recommended action |
No action is required. |
DHCPS_ROUTE_DEL
|
Message text |
UNR route ( Destination [STRING], Nexthop [STRING], Tunnel-destination [STRING] ) deleted for pool [STRING]. |
|
Variable fields |
$1: Destination network. $2: Next hop of the network route. $3: Destination of the tunnel. If no tunnel is configured, this field displays N/A. $4: Name of the IP address pool. |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS/6/DHCPS_ROUTE_DEL: UNR route ( Destination 10.1.1.1/24, Nexthop 0.0.0.0, Tunnel-destination N/A ) deleted for pool pool1. |
|
Impact |
Network traffic cannot reach the network segment at which the client is located. |
|
A UNR issued for the IP address pool was deleted as the corresponding network segment was deleted from the IP address pool. |
|
|
Recommended action |
No action is required. |
DHCPS_ROUTE_UPADD
|
Message text |
Issued UNR route ( Destination [STRING], Nexthop [STRING], Tunnel-destination [STRING] ) for pool [STRING] to UP [UINT]. |
|
Variable fields |
$1: Destination network. $2: Next hop of the network route. $3: Destination of the tunnel. If no tunnel is configured, this field displays N/A. $4: Name of the IP address pool. $5: UP ID. |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS/6/DHCPS_ROUTE_UPADD: Issued UNR route ( Destination 10.1.1.1/24, Nexthop 0.0.0.0, Tunnel-destination N/A ) for pool pool1 to UP 1024. |
|
Impact |
Network traffic can reach the UP at which the client is located. |
|
After the CP assigns an IP address to a DHCP client, it issues a UNR for that client to the UP. The UNR can guide downlink traffic to the client. |
|
|
Recommended action |
No action is required. |
DHCPS_ROUTE_UPDEL
|
Message text |
Delete UNR route ( Destination [STRING], Nexthop [STRING], Tunnel-destination [STRING] ) for pool [STRING] issued to UP [UINT]. |
|
Variable fields |
$1: Destination network. $2: Next hop of the network route. $3: Destination of the tunnel. If no tunnel is configured, this field displays N/A. $4: Name of the IP address pool. $5: UP ID. |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS/6/DHCPS_ROUTE_UPDEL: Delete UNR route ( Destination 10.1.1.1/24, Nexthop 0.0.0.0, Tunnel-destination N/A ) for pool pool1 issued to UP 1024. |
|
Impact |
Network traffic cannot reach the UP at which the client is located. |
|
Cause |
The CP deleted a UNR issued to the UP because the corresponding network segment was deleted from the IP address pool. |
|
Recommended action |
No action is required. |
DHCPS_ROUTE_SMOOTHSTART
|
Message text |
Route restore started. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS/6/DHCPS_ROUTE_SMOOTHSTART: Route restore started. |
|
Impact |
|
|
Cause |
After the device or the process restarted, the device started smoothing network routes issued for IP address pools. |
|
Recommended action |
No action is required. |
DHCPS_ROUTE_SMOOTHEND
|
Message text |
Route restore ended. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS/6/DHCPS_ROUTE_SMOOTHEND: Route restore ended. |
|
Impact |
|
|
Cause |
The device finished smoothing network routes issue for IP address pools. |
|
Recommended action |
No action is required. |
DHCPS_ROUTE_UPSMOOTHSTART
|
Message text |
The CP started synchronizing routes to UPs. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS/6/DHCPS_ROUTE_UPSMOOTHSTART: The CP started synchronizing routes to UPs. |
|
Impact |
No negative impact on the system. |
|
Cause |
|
|
Recommended action |
No action is required. |
DHCPS_ROUTE_UPSMOOTHEND
|
Message text |
The CP finished synchronizing routes to UPs. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS/6/DHCPS_ROUTE_UPSMOOTHEND: The CP finished synchronizing routes to UPs. |
|
Impact |
No negative impact on the system. |
|
Cause |
The CP finished synchronizing the network routes issued for IP address pools to UPs. |
|
Recommended action |
No action is required. |
DHCPS_SUPPRESS_INT_RATE
|
Message text |
A DHCP packet attack exists because the number of DHCP packets received on interface [STRING] has exceeded the limit within the specified detection period. |
|
Variable fields |
$1: Name of the interface that received DHCP packets. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS/5/DHCPS_SUPPRESS_INT_RATE: A DHCP packet attack exists because the number of DHCP packets received on interface GE1/0/1 has exceeded the limit within the specified detection period. |
|
Impact |
The DHCP interface attack suppression feature will drop the DHCP packets that exceed the upper limit. |
|
Cause |
This log message is generated when the following conditions exist: · DHCP interface attack suppression is enabled on the interface. · The number of incoming DHCP packets from the same MAC address reaches the upper limit in the detection duration, the DHCP device determines that the client is launching a DHCP packet attack. |
|
Recommended action |
Use the display dhcp interface-rate-suppression command to view the operating state of the DHCP interface attack suppression feature and information about DHCP interface attack suppression entries. |
DHCPS_THRESHOLD_EXCEED
|
Message text |
The IP address utilization of the address pool [STRING] has exceeded the threshold. |
|
Variable fields |
$1: Name of the IP address pool. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCPS_THRESHOLD_EXCEED: The IP address utilization of the address pool 1 has exceeded the threshold. |
|
Impact |
If the DHCP server continues to assign IP addresses from the address pool to clients, the address pool might run out of addresses. As a result, new DHCP users cannot obtain IP addresses and thus cannot come online. |
|
Cause |
The IP address usage of an address pool has exceeded the threshold. |
|
Recommended action |
To resolve this issue: 1. Use the display ip pool command in any view to identify whether the address usage threshold specified in the current address pool is appropriate. ¡ If the address usage threshold is too low, increase the threshold. ¡ If the address usage threshold is appropriate, proceed to step 2. 2. Use the display dhcp server statistics command in any view to view the address usage of the current address pool and the number of assignable addresses in the current address pool. ¡ If the assignable addresses are insufficient, increase address resources for the address pool. For example, you can add the current address pool and other address pools to an address pool group, or add secondary network segments for dynamic address allocation in the current address pool. ¡ If the assignable addresses are sufficient, keep observing the address usage of the current address pool. When the address pool has a high address usage, increase address resources timely to ensure that new DHCP users can obtain addresses. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS_THRESHOLD_RECOVER
|
Message text |
The IP address usage of pool [STRING] has descended to 90% of the threshold. |
|
Variable fields |
$1: Name of the IP address pool. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCP_THRESHOLD_RECOVER: The IP address usage of pool 1 has descended to 90% of the threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
The IP address usage of an address pool has dropped below 90% of the specified threshold. |
|
Recommended action |
No action is required. |
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 (Notification) |
|
Example |
|
|
Impact |
The DHCP server does not process the request from the DHCP client. |
|
Cause |
The DHCP server verified that the DHCP client was not on the user class allowlist. (This log message is not supported by vBRAS-CPs.) |
|
Recommended action |
1. Check the validity of the DHCP client by using the port mirroring feature. ¡ If the DHCP client is unauthorized, ignore the request. ¡ If the DHCP client is authorized, add the user class of the DHCP client to the DHCP user class allowlist. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DHCPS_WARNING_EXHAUSTION
|
Message text |
Address pool [STRING] has run out of IP addresses. |
|
Variable fields |
$1: Name of the IP address pool. |
|
Severity level |
3 (Error) |
|
Example |
DHCPS/3/DHCPS_WARNING_EXHAUSTION: Address pool 1 has run out of IP addresses. |
|
Impact |
New DHCP users cannot obtain IP addresses from the DHCP server. |
|
Cause |
An IP address pool has run out of IP addresses. |
|
Recommended action |
To resolve this issue: 1. Use one of the following methods to increase address resources: ¡ Add the current address pool and other address pools to an address pool group. ¡ Add secondary network segments for dynamic address allocation in the current address pool. |
DHCPS_WARNING_EXHAUSTIONRECOVER
|
Message text |
The IP address usage of pool [STRING] has descended to 90%. |
|
Variable fields |
$1: Name of the IP address pool. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS/4/DHCPS_WARNING_EXHAUSTIONRECOVER: The IP address usage of pool pool1 has descended to 90%. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some IP addresses in an address pool are reclaimed, and the IP address usage of that address pool has dropped to or below 90%. |
|
Recommended action |
No action is required. |
DHCPS6 messages
This section contains DHCPv6 server (DHCPS6) 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 DHCPv6 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 (Notification) |
|
Example |
DHCPS6/5/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 DHCPv6 client(DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) from p1 pool. |
|
Impact |
No negative impact on the system. |
|
Cause |
The DHCPv6 server assigned an IPv6 address 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 DHCPv6 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 (Notification) |
|
Example |
DHCPS6/5/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 DHCPv6 client(DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) from p1 pool. |
|
Impact |
No negative impact on the system. |
|
Cause |
The DHCPv6 server assigned an IPv6 prefix lease to a DHCPv6 client. |
|
Recommended action |
No action is required. |
DHCPS6_ALLOC_USERIP_FAILED
|
Message text |
IPv6 allocation failed in domain [STRING] because of the reason: [STRING]. |
|
Variable fields |
$1: Name of the ISP domain. $2: Reason why the DHCPv6 server failed the IPv6 address allocation: · UP information mismatch. · No authorized pool or pool-group exists or the interface is not on the network specified for the matching pool. · No free lease in the matching pool or pool-group. · Creating lease failed. · Pool misconfiguration on the relay agent. · Other. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/ DHCPS6_ALLOC_USERIP_FAILED: IPv6 allocation failed in domain domain1 because of the reason: UP information mismatch. |
|
The DHCPv6 client fails to obtain an IPv6 address, and cannot come online. |
|
|
Cause |
The log message is generated possibly because: · The UP information is not matching. · No authorization address pool or pool group exists or the interface is not on the IPv6 network segment specified for the matching address pool. · No free lease exists in the matching address pool or pool group. · Lease creation fails. · The address pool settings are incorrect on the DHCPv6 relay agent. |
|
Recommended action |
1. Verify that all necessary address pool settings are correct on the DHCPv6 relay agent and the DHCPv6 server. 2. Replan address pool resources or address pool group resources to ensure sufficient address resources. You can bind more address pools to the current address pool group. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_ALLOC_USERPD_FAILED
|
Message text |
IPv6 prefix allocation failed in domain [STRING] because of the reason: [STRING]. |
|
Variable fields |
$1: Name of the ISP domain. $2: Reason why the DHCPv6 server failed the IPv6 prefix allocation: · UP information mismatch. · No authorized pool or pool-group exists or the interface is not on the network specified for the matching pool. · No free lease in the matching pool or pool-group. · Creating lease failed. · Pool misconfiguration on the relay agent. · Other. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_ALLOC_USERIP_FAILED: IPv6 prefix allocation failed in domain domain1 because of the reason: UP information mismatch. |
|
Impact |
The DHCPv6 client fails to obtain an IPv6 prefix. |
|
Cause |
The log message is generated possibly because: · The UP information is not matching. · No authorization address pool or pool group exists or the interface is not on the IPv6 network segment specified for the matching address pool. · No free lease exists in the matching address pool or pool group. · Lease creation fails. · The address pool settings are incorrect on the DHCPv6 relay agent. |
|
Recommended action |
1. Verify that all necessary address pool settings are correct on the DHCPv6 relay agent and the DHCPv6 server. 2. Replan address pool resources or address pool group resources to ensure sufficient prefix resources. You can bind more address pools to the current address pool group. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_ANTIFLOOD_DISABLE_FAILURE
|
Message text |
Failed to disable DHCPv6 flood protection function on the interface [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: Reason why DHCPv6 flood protection failed to be disabled: · Not enough resources: Insufficient resources. · Configuration already exists: The configuration already exists. · Not found: The interface does not exist. · Configuration not supported: The configuration is not supported. · Unknown error: Unknown reason. |
|
Severity level |
3 (Error) |
|
Example |
DHCPS6/3/DHCPS6_ANTIFLOOD_DISABLE_FAILURE: -MDC=1; Failed to disable DHCPv6 flood protection function on the interface GigabitEthernet1/0/1. Reason: Configuration not supported. |
|
Impact |
DHCPv6 flood protection is still enabled on the interface. |
|
Cause |
This message is generated when you disable global DHCPv6 flood protection and this feature fails to be disabled on an interface. |
|
Recommended action |
Execute the display ipv6 dhcp flood-protection command to view the enabling status of global DHCPv6 flood protection: · If this feature is enabled, disable this feature again. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. · If this feature is disabled, view this message to locate the cause of this issue. ¡ If this issue occurs because the device is busy with services and hardware resources are insufficient, wait a minute or close unnecessary services, and then disable global DHCPv6 flood protection again. ¡ If the issue persists after troubleshooting, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DHCPS6_ANTIFLOOD_ENABLE_FAILURE
|
Message text |
Failed to enable DHCPv6 flood protection function on the interface [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Interface type and number. $2: Reason why DHCPv6 flood protection failed to be enabled: · Not enough resources: Insufficient resources. · Configuration already exists: The configuration already exists. · Not found: The interface does not exist. · Configuration not supported:The configuration is not supported. · Unknown error: Unknown reason. |
|
Severity level |
3 (Error) |
|
Example |
DHCPS6/3/DHCPS6_ANTIFLOOD_ENABLE_FAILURE: -MDC=1; Failed to enable DHCPv6 flood protection function on the interface GigabitEthernet1/0/1. Reason: Configuration not supported. |
|
Impact |
DHCPv6 flood protection is still disabled on the interface. |
|
Cause |
This message is generated when you enable global DHCPv6 flood protection and this feature fails to be enabled on an interface. |
|
Recommended action |
Execute the display ipv6 dhcp flood-protection command to view the enabling status of global DHCPv6 flood protection: · If this feature is disabled, enable this feature again. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. · If this feature is enabled, view this message to locate the cause of this issue. ¡ If this issue occurs because the device is busy with services and hardware resources are insufficient, wait a minute or close unnecessary services, and then enable global DHCPv6 flood protection again. ¡ If the issue persists after troubleshooting, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DHCPS6_CONFLICT_ADDRESS
|
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 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_CONFLICT_ADDRESS: A conflict IPv6 address 33::1 from p1 pool was detected by DHCPv6 server on interface Ethernet0/2. |
|
The conflicting IPv6 address cannot be assigned. |
|
|
Cause |
The address pool contains an IPv6 interface address of the DHCPv6 server. |
|
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 (Notification) |
|
Example |
DHCPS6/5/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). |
|
Impact |
No negative impact on the system. |
|
Cause |
The DHCPv6 server extended 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 (Notification) |
|
Example |
DHCPS6/5/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). |
|
Impact |
No negative impact on the system. |
|
Cause |
The DHCPv6 server extended 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 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_FILE: Failed to save DHCP client information due to lack of storage resources. |
|
The DHCPv6 server failed to save DHCPv6 client information, and the related DHCPv6 client cannot come online. |
|
|
Cause |
A new user attempted to come online when the DHCPv6 server did not have sufficient storage resources. |
|
Recommended action |
Delete unnecessary files to release storage resources. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DHCPS6_FLOOD_ATTACK
|
Message text |
A DHCPv6 flood attack exists because the number of DHCPv6 packets that interface [STRING] receives from client (MAC [MAC]) has exceeded the limit within the specified detection period. |
|
Variable fields |
$1: Name of the interface that received DHCPv6 packets. $2: MAC address of the attacker. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_FLOOD_ATTACK: A DHCPv6 flood attack exists because the number of DHCPv6 packets that interface GE1/0/1 receives from client (MAC 3042-9cc2-0207) has exceeded the limit within the specified detection period. |
|
Impact |
The DHCPv6 flood attack protection feature will drop the attack packets that exceed the upper limit. |
|
Cause |
This log message is generated when the following conditions exist: · DHCPv6 flood attack protection is enabled on the interface. · The number of incoming DHCPv6 packets from the same MAC address reaches the upper limit in the detection duration, the DHCPv6 server determines that the client is launching a DHCPv6 flood attack. |
|
Recommended action |
Use the display ipv6 dhcp flood-protection command to view the operating state of the DHCPv6 flood attack protection feature and information about DHCPv6 flood attack protection entries. |
DHCPS6_IP_NET_EXHAUST
|
Message text |
|
|
Variable fields |
$1: IPv6 address pool name. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_IP_NET_EXHAUSTION: Address pool pool1 has run out of assignable subnets. |
|
Impact |
New DHCPv6 users cannot obtain addresses and thus cannot come online. |
|
Cause |
An IPv6 address pool has run out of subnet resources. |
|
Recommended action |
To resolve this issue: 1. Increase subnet resources. For example, you can add the current address pool and other address pools to an address pool group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_IP_NET_EXHAUSTREC
|
Message text |
The subnet usage of address pool [STRING] has descended to or dropped below 90%. |
|
Variable fields |
$1: IPv6 address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_IP_NET_EXHAUSTREC: The subnet usage of address pool pool1 has descended to or dropped below 90%. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some subnets in an IPv6 address pool are reclaimed, and the usage of assignable subnets in that address pool has dropped to or below 90%. |
|
Recommended action |
No action is required. |
DHCPS6_IP_NET_THRESHOLD_EXCEED
|
Message text |
The subnet usage of address pool [STRING] has reached or exceeded the threshold. |
|
Variable fields |
$1: IPv6 address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_IP_NET_THRESHOLD_EXCEED: The subnet usage of address pool pool1 has reached or exceeded the threshold. |
|
Impact |
If the DHCPv6 server continues to assign subnets from the address pool to clients, the address pool might run out of address resources. As a result, new DHCPv6 users cannot obtain addresses and thus cannot come online. |
|
Cause |
The usage of assignable subnets in an address pool has reached or exceeded the threshold. |
|
Recommended action |
To resolve this issue: 1. Use the display ipv6 dhcp dynamic address command in any view to view the subnets in IPv6 address pools that support dynamic IPv6 subnet allocation. If the utilization of each subnet is high, use the dynamic utilization mark command to increase the low utilization mark. This operation will make the address pool to release idle subnets. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_IP_NET_THRESHOLD_REC
|
Message text |
The subnet usage of pool [STRING] has descended to or dropped below 90% of the threshold. |
|
Variable fields |
$1: IPv6 address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_IP_NET_THRESHOLD_REC: The subnet usage of pool pool1 has descended to or dropped below 90% of the threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some subnets in an IPv6 address pool are reclaimed, and the usage of assignable subnets in that address pool has dropped to or below 90% of the threshold. |
|
Recommended action |
No action is required. |
DHCPS6_IP_THRESHOLD_EXCEED
|
Message text |
The IPv6 address usage of pool [STRING] has reached or exceeded the threshold. |
|
Variable fields |
$1: Name of the IPv6 address pool. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/ DHCPS6_IP_THRESHOLD_EXCEED: The IPv6 address usage of pool pool1 has reached or exceeded the threshold. |
|
Impact |
If the DHCPv6 server continues to assign IPv6 addresses from the address pool to clients, the address pool might run out of addresses. As a result, new DHCPv6 users cannot obtain IPv6 addresses and thus cannot come online. |
|
Cause |
The address usage of an IPv6 address pool has reached or exceeded the threshold. |
|
Recommended action |
To resolve this issue: 1. Use the display ipv6 pool command in any view to identify whether the address usage threshold specified in the current address pool is appropriate. ¡ If the address usage threshold is too low, increase the threshold. ¡ If the address usage threshold is appropriate, proceed to step 2. 2. Use the display ipv6 dhcp server statistics command in any view to view the address usage of the current address pool and the number of assignable addresses in the current address pool. ¡ If the assignable addresses are insufficient, replan and increase address pool resources. For example, you can increase address resources as follows: ¡ i. Use the ipv6 pool-group command to create an IPv6 address pool group, and then add multiple address pools to the address pool group. ¡ ii. Use the undo authorization-attribute ipv6-pool command in ISP domain view to remove the current authorization IPv6 address pool attribute. ¡ iii. Use the authorization-attribute ipv6-pool-group command in ISP domain view to specify the IPv6 address pool group for users. ¡ If the assignable addresses are sufficient, keep observing the address usage of the current address pool. When the address pool has a high address usage, increase address resources timely to ensure that new DHCPv6 users can obtain addresses. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_IP_THRESHOLD_RECOVER
|
Message text |
The IPv6 address usage of pool [STRING] is below 90% of the threshold. |
|
Variable fields |
$1: Name of the IPv6 address pool. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_IP_THRESHOLD_ RECOVER: The IPv6 address usage of pool pool1 is below 90% of the threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
The address usage of an IPv6 address pool has dropped below 90% of the specified threshold. |
|
Recommended action |
No action is required. |
DHCPS6_IP_WARNING_EXHAUSTION
|
Message text |
IPv6 pool [STRING] has run out of addresses. |
|
Variable fields |
$1: Name of the IPv6 address pool. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_IP_WARNING_EXHAUSTION: IPv6 pool pool1 has run out of addresses. |
|
Impact |
New DHCPv6 users cannot obtain IPv6 addresses from the DHCPv6 server. |
|
Cause |
An IPv6 address pool has run out of IPv6 addresses. |
|
Recommended action |
To resolve this issue: 1. Increase address resources. For example, you can add the current address pool and other address pools to an address pool group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_IP_WARNING_EXHAUSTRECOVER
|
Message text |
The IPv6 address usage of pool [STRING] has dropped to or below 90%. |
|
Variable fields |
$1: Name of the IPv6 address pool. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_IP_WARNING_EXHAUSTRECOVER: The IPv6 address usage of pool pool1 has dropped to or below 90%. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some IPv6 addresses in an IPv6 address pool are reclaimed, and the IPv6 address usage of that address pool has dropped to or below 90%. |
|
Recommended action |
No action is required. |
DHCPS6_PACKET_ATTACK
|
Message text |
The device might be under a DHCPv6 packet attack. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_PACKET_ATTACK: The device might be under a DHCPv6 packet attack. |
|
Impact |
Memory resources might be insufficient, and the related services cannot run correctly. |
|
Cause |
The device is under a DHCPv6 packet attack and might trigger memory usage alarms. |
|
Recommended action |
Enable a DHCPv6 attack prevention feature, such as DHCPv6 flood attack protection or DHCPv6 packet rate limiting. |
DHCPS6_PD_NET_EXHAUSTION
|
Message text |
Address pool [STRING] has run out of assignable IPv6 prefix ranges. |
|
Variable fields |
$1: IPv6 address pool name. |
|
Severity level |
4 |
|
Example |
4 (Warning) |
|
Impact |
DHCPS6/4/DHCPS6_PD_NET_EXHAUSTION: Address pool pool1 has run out of assignable IPv6 prefix ranges. |
|
Cause |
An IPv6 address pool has run out of prefix range resources. |
|
Recommended action |
To resolve this issue: 1. Increase prefix range resources. For example, you can add the current address pool and other address pools to an address pool group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_PD_NET_EXHAUSTREC
|
Message text |
The IPv6 prefix range usage of address pool [STRING] has descended to or dropped below 90%. |
|
Variable fields |
$1: IPv6 address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_PD_NET_EXHAUSTREC: The IPv6 prefix range usage of address pool pool1 has descended to or dropped below 90%. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some prefix ranges in an IPv6 address pool are reclaimed, and the usage of assignable prefix ranges in that address pool has dropped to or below 90%. |
|
Recommended action |
No action is required. |
DHCPS6_PD_NET_THRESHOLD_EXCEED
|
Message text |
The prefix range usage of address pool [STRING] has reached or exceeded the threshold. |
|
Variable fields |
$1: IPv6 address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_PD_NET_THRESHOLD_EXCEED: The prefix range usage of address pool pool1 has reached or exceeded the threshold. |
|
Impact |
If the DHCPv6 server continues to assign prefix ranges from the address pool to clients, the address pool might run out of prefix range resources. As a result, new DHCPv6 users cannot obtain prefixes and thus cannot come online. |
|
Cause |
The usage of assignable prefix ranges in an IPv6 address pool has reached or exceeded the threshold. |
|
Recommended action |
To resolve this issue: 1. Use the display ipv6 dhcp dynamic prefix command in any view to view the prefix usage of prefix ranges in the current IPv6 address pool. If the prefix usage of each prefix range is high, use the dynamic utilization mark command to increase the low utilization mark. This operation will make the address pool to release idle prefix ranges. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_PD_NET_THRESHOLD_REC
|
Message text |
The prefix range usage of pool [STRING] has descended to or dropped below 90% of the threshold. |
|
Variable fields |
$1: IPv6 address pool name. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_PD_NET_THRESHOLD_REC: The prefix range usage of pool pool1 has descended to or dropped below 90% of the threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some prefix ranges in an IPv6 address pool are reclaimed, and the usage of assignable prefix ranges in that address pool has dropped to or below 90% of the threshold. |
|
Recommended action |
No action is required. |
DHCPS6_PD_THRESHOLD_EXCEED
|
Message text |
The IPv6 prefix usage of pool [STRING] has reached or exceeded the threshold. |
|
Variable fields |
$1: Name of the IPv6 address pool. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_PD_THRESHOLD_EXCEED: The IPv6 prefix usage of pool pool1 has reached or exceeded the threshold. |
|
Impact |
If the DHCPv6 server continues to assign IPv6 prefixes from the address pool to clients, the address pool might run out of prefixes. As a result, new DHCPv6 users cannot obtain IPv6 prefixes and thus cannot come online. |
|
Cause |
The prefix usage of an IPv6 address pool has reached or exceeded the threshold. |
|
Recommended action |
To resolve this issue: 1. Use the display ipv6 pool command in any view to identify whether the prefix usage threshold specified in the current address pool is appropriate. ¡ If the prefix usage threshold is too low, increase the threshold. ¡ If the prefix usage threshold is appropriate, proceed to step 2. 2. Use the display ipv6 dhcp server statistics command in any view to view the prefix usage of the current address pool and the number of assignable prefixes in the current address pool. ¡ If the assignable prefixes are insufficient, replan and increase address pool resources. For example, you can increase prefix resources as follows: ¡ i. Use the ipv6 pool-group command to create an IPv6 address pool group, and then add multiple address pools to the address pool group. ¡ ii. Use the undo authorization-attribute ipv6-pool command in ISP domain view to remove the current authorization IPv6 address pool attribute. ¡ iii. Use the authorization-attribute ipv6-pool-group command in ISP domain view to specify the IPv6 address pool group for users. ¡ If the assignable prefixes are sufficient, keep observing the prefix usage of the current address pool. When the address pool has a high prefix usage, increase prefix resources timely to ensure that new DHCPv6 users can obtain prefixes. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_PD_THRESHOLD_ RECOVER
|
Message text |
The IPv6 prefix usage of pool [STRING] is below 90% of the threshold. |
|
Variable fields |
$1: Name of the IPv6 address pool. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_PD_THRESHOLD_RECOVER: The IPv6 prefix usage of pool pool1 is below 90% of the threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
The prefix usage of an IPv6 address pool has dropped below 90% of the specified threshold. |
|
Recommended action |
No action is required. |
DHCPS6_PD_WARNING_EXHAUSTION
|
Message text |
Address pool [STRING] has run out of Ipv6 pd. |
|
Variable fields |
$1: Name of the IPv6 address pool. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_PD_WARNING_EXHAUSTION: Address pool pool1 has run out of Ipv6 pd. |
|
Impact |
New DHCPv6 users cannot obtain IPv6 prefixes from the DHCPv6 server. |
|
Cause |
An IPv6 address pool has run out of IPv6 prefixes. |
|
Recommended action |
To resolve this issue: 1. Increase prefix resources. For example, you can add the current address pool and other address pools to an address pool group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_PD_WARNING_EXHAUSTRECOVER
|
Message text |
The Ipv6 pd usage of pool [STRING] has descended to 90%. |
|
Variable fields |
$1: Name of the IPv6 address pool. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS6/5/DHCPS6_PD_WARNING_EXHAUSTRECOVER: The Ipv6 pd usage of pool pool1 has descended to 90%. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some IPv6 prefixes in an IPv6 address pool are reclaimed, and the prefix usage of that address pool has dropped to or below 90%. |
|
Recommended action |
No action is required. |
DHCPS6_POOLGP_IP_EXHAUSTION
|
Message text |
Pool group [STRING] has run out of IPv6 addresses. |
|
Variable fields |
$1: Name of the IPv6 address pool group. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_POOLGP_IP_EXHAUSTION: Pool group group1 has run out of IPv6 addresses. |
|
Impact |
New DHCPv6 users might fail to obtain IPv6 addresses and thus cannot come online. |
|
Cause |
An IPv6 address pool group has run out of IPv6 addresses. |
|
Recommended action |
To resolve this issue: 1. Increase address resources for the address pool group. For example, you can add new address pools to the address pool group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_POOLGP_EXHAUSTION_RECOV
|
Message text |
IPv6 address usage of pool group [STRING] has dropped to or below 90%. |
|
Variable fields |
$1: Name of the IPv6 address pool group. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_POOLGP_EXHAUSTION_RECOV: IPv6 address usage of pool group group1 has dropped to or below 90%. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some IPv6 addresses in an IPv6 address pool group are reclaimed, and the IPv6 address usage of that address pool group has dropped to or below 90%. |
|
Recommended action |
No action is required. |
DHCPS6_POOLGP_THRESHOLD_EXCEED
|
Message text |
IPv6 address usage of pool group [STRING] has exceeded the threshold. |
|
Variable fields |
$1: Name of the IPv6 address pool group. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_POOLGP_THRESHOLD_EXCEED: IPv6 address usage of pool group group1 has exceeded the threshold. |
|
Impact |
If the DHCPv6 server continues to assign IPv6 addresses from the address pool group to clients, the address pool group might run out of addresses. As a result, new DHCPv6 users cannot obtain IPv6 addresses and thus cannot come online. |
|
Cause |
The IPv6 address usage of an IPv6 address pool group has exceeded the threshold. |
|
Recommended action |
To resolve this issue: 1. Use the display ipv6 pool-group command in any view to identify whether the address usage threshold specified in the current address pool group is appropriate. ¡ If the address usage threshold is too low, increase the threshold. ¡ If the address usage threshold is appropriate, proceed to step 2. 2. Use the display ipv6 dhcp server statistics command in any view to view the address usage of the current address pool group and the number of assignable addresses in the current address pool group. ¡ If the assignable addresses are insufficient, increase address resources for the address pool group. For example, you can add new address pools to the address pool group. ¡ If the assignable addresses are sufficient, keep observing the address usage of the current address pool group. When the address pool group has a high address usage, increase address resources timely to ensure that new DHCPv6 users can obtain addresses. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DHCPS6_POOLGP_THRESHOLD_RECOV
|
Message text |
IPv6 address usage of pool group [STRING] has dropped to or below 90% of the threshold. |
|
Variable fields |
$1: Name of the IPv6 address pool group. |
|
Severity level |
4 (Warning) |
|
Example |
DHCPS6/4/DHCPS6_POOLGP_ THRESHOLD_RECOV: IPv6 address usage of pool group group1 has dropped to or below 90% of the threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
Some IPv6 addresses in an IPv6 address pool group are reclaimed, and the IPv6 address usage of that address pool group has dropped to or below 90% of the threshold. |
|
Recommended action |
No action is required. |
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 (Notification) |
|
Example |
DHCPS6/5/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). |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when one of the following conditions exists: · The reset command is used to delete lease information. · The client sends a DHCP-RELEASE message to the DHCPv6 server. · The address lease expires, because the client does not renew the lease. |
|
Recommended action |
If the DHCPv6 client needs to come online, request an address lease again. |
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 (Notification) |
|
Example |
DHCPS6/5/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). |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when one of the following conditions exists: · The reset command is used to delete lease information. · The client sends a DHCP-RELEASE message to the DHCPv6 server. · The prefix lease expires, because the client does not renew the lease. |
|
Recommended action |
If the DHCPv6 client needs to come online, request a prefix lease again. |
DHCPS6_ROUTE_ADD
|
Message text |
UNR route ( Destination [STRING], Nexthop [STRING], Tunnel-destination [STRING] ) added for pool [STRING]. |
|
Variable fields |
$1: Destination network. $2: Next hop of the network route. $3: Destination of the tunnel. If no tunnel is configured, this field displays N/A. $4: Name of the IPv6 address pool. |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS6/6/DHCPS6_ROUTE_ADD: UNR route ( Destination 10::1/64, Nexthop ::, Tunnel-destination N/A ) added for pool pool1. |
|
Impact |
Network traffic can reach the network segment at which the client is located. |
|
Cause |
The local device automatically generates a UNR for the IPv6 address pool. For example, the export-route keyword is specified when the network command is configured on the device. |
|
Recommended action |
No action is required. |
DHCPS6_ROUTE_DEL
|
Message text |
UNR route ( Destination [STRING], Nexthop [STRING], Tunnel-destination [STRING] ) deleted for pool [STRING]. |
|
Variable fields |
$1: Destination network. $2: Next hop of the network route. $3: Destination of the tunnel. If no tunnel is configured, this field displays N/A. $4: Name of the IPv6 address pool. |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS6/6/DHCPS6_ROUTE_DEL: UNR route ( Destination 10::1/64, Nexthop ::, Tunnel-destination N/A ) deleted for pool pool1. |
|
Impact |
Network traffic cannot reach the network segment at which the client is located. |
|
Cause |
A UNR issued for the IPv6 address pool was deleted as the corresponding network segment was deleted from the IPv6 address pool. |
|
Recommended action |
No action is required. |
DHCPS6_ROUTE_UPADD
|
Message text |
Issued UNR route ( Destination [STRING], Nexthop [STRING], Tunnel-destination [STRING] ) for pool [STRING] to UP [UINT]. |
|
Variable fields |
$1: Destination network. $2: Next hop of the network route. $3: Destination of the tunnel. If no tunnel is configured, this field displays N/A. $4: Name of the IPv6 address pool. |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS6/6/DHCPS6_ROUTE_UPADD: Issued UNR route ( Destination 10::1/24, Nexthop ::, Tunnel-destination N/A ) for pool pool1 to UP 1024. |
|
Impact |
Network traffic can reach the UP at which the client is located. |
|
Cause |
After the CP assigns an IPv6 address to a DHCPv6 client, it issues a UNR for that client to the UP. The UNR can guide downlink traffic to the client. |
|
Recommended action |
No action is required. |
DHCPS6_ROUTE_UPDEL
|
Message text |
Delete UNR route ( Destination [STRING], Nexthop [STRING], Tunnel-destination [STRING] ) for pool [STRING] issued to UP [UINT]. |
|
Variable fields |
$1: Destination network. $2: Next hop of the network route. $3: Destination of the tunnel. If no tunnel is configured, this field displays N/A. $4: Name of the IPv6 address pool. $5: UP ID. |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS6/6/DHCPS6_ROUTE_UPDEL: Delete UNR route ( Destination 10::1/24, Nexthop ::, Tunnel-destination N/A ) for pool pool1 issued to UP 1024. |
|
Impact |
Network traffic cannot reach the UP at which the client is located. |
|
Cause |
The CP deleted a UNR issued to the UP because the corresponding network segment was deleted from the IPv6 address pool. |
|
Recommended action |
No action is required. |
DHCPS6_ROUTE_SMOOTHSTART
|
Message text |
Route restore started. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS6/6/DHCPS6_ROUTE_SMOOTHSTART: Route restore started. |
|
Impact |
No negative impact on the system. |
|
Cause |
After the device or the process restarted, the device started smoothing network routes issued for IPv6 address pools. |
|
Recommended action |
No action is required. |
DHCPS6_ROUTE_SMOOTHEND
|
Message text |
Route restore ended. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS6/6/DHCPS6_ROUTE_SMOOTHEND: Route restore ended. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device finished smoothing network routes issue for IPv6 address pools. |
|
Recommended action |
No action is required. |
DHCPS6_ROUTE_UPSMOOTHSTART
|
Message text |
The CP started synchronizing routes to UPs. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS6/6/DHCPS6_ROUTE_UPSMOOTHSTART: The CP started synchronizing routes to UPs. |
|
Impact |
No negative impact on the system. |
|
Cause |
After the CP was re-connected to UPs, the CP started synchronizing the network routes issued for IPv6 address pools to UPs. |
|
Recommended action |
No action is required. |
DHCPS6_ROUTE_UPSMOOTHEND
|
Message text |
The CP finished synchronizing routes to UPs. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
DHCPS6/6/DHCPS6_ROUTE_UPSMOOTHEND: The CP finished synchronizing routes to UPs. |
|
Impact |
No negative impact on the system. |
|
Cause |
The CP finished synchronizing the network routes issued for IPv6 address pools to UPs. |
|
Recommended action |
No action is required. |
DHCPS6_SUPPRESS_INT_RATE
|
Message text |
A DHCPv6 packet attack exists because the number of DHCPv6 packets received on interface [STRING] has exceeded the limit within the specified detection period. |
|
Variable fields |
$1: Name of the interface that received DHCPv6 packets. |
|
Severity level |
5 (Notification) |
|
Example |
DHCPS/5/DHCPS6_SUPPRESS_INT_RATE: A DHCPv6 packet attack exists because the number of DHCPv6 packets received on interface GE1/0/1 has exceeded the limit within the specified detection period. |
|
Impact |
The DHCPv6 interface attack suppression feature will drop the DHCPv6 packets that exceed the upper limit. |
|
Cause |
This log message is generated when the following conditions exist: · DHCPv6 interface attack suppression is enabled on the interface. · The number of incoming DHCPv6 packets from the same MAC address reaches the upper limit in the detection duration, the DHCPv6 device determines that the client is launching a DHCPv6 packet attack. |
|
Recommended action |
Use the display ipv6 dhcp interface-rate-suppression command to view the operating state of the DHCPv6 interface attack suppression feature and information about DHCPv6 interface attack suppression entries. |
DHCPSP4
This section contains DHCP snooping (DHCPSP4) messages.
DHCPSP4_FILE
|
Message text |
Failed to save DHCP client information due to lack of storage resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DHCPSP4/4/DHCPSP4_FILE: Failed to save DHCP client information due to lack of storage resources. |
|
Impact |
The DHCP snooping device failed to save DHCP client information, and the related DHCP client cannot come online. |
|
Cause |
A new user attempted to come online when the DHCP snooping device did not have sufficient storage resources. |
|
Recommended action |
Delete unnecessary files to release storage resources. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DHCPSP6
This section contains DHCPv6 snooping (DHCPSP6) messages.
DHCPSP6_FILE
|
Message text |
Failed to save DHCP client information due to lack of storage resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DHCPSP6/4/DHCPSP6_FILE: Failed to save DHCP client information due to lack of storage resources. |
|
Impact |
The DHCPv6 snooping device failed to save DHCPv6 client information, and the related DHCPv6 client cannot come online. |
|
Cause |
A new user attempted to come online when the DHCPv6 snooping device did not have sufficient storage resources. |
|
Recommended action |
Delete unnecessary files to release storage resources. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
DIAG messages
This section contains DIAG messages. These messages are output only if the system is configured to take an action in response to hardware failures.
FMEA_ERR_REBOOT
|
Message text |
Hardware error detected on slot [UINT32]. Rebooting the card… |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
2 (Critical) |
|
Example |
DIAG/2/FMEA_ERR_REBOOT: Hardware error detected on slot 2. Rebooting the card… |
|
Impact |
A large number of packets were lost. |
|
Cause |
FMEA detected an interface module hardware failure. The system was rebooting the interface module. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
FMEA_ERR
|
Message text |
Hardware error detected on slot [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
4 (Warning) |
|
Example |
DIAG/4/FMEA_ERR: Hardware error detected on slot 2. |
|
Impact |
Error packets might exist. |
|
Cause |
FMEA detected an interface module hardware failure. The system only sent a log message and did not try to resolve the issue. |
|
Recommended action |
1. Identify whether the message is reported repeatedly. 2. If not, no action is required. If yes, go the next step. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
EMMC storage media error or storage insufficiency detected on slot [UINT32]. |
|
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
3 (Error) |
|
Example |
DIAG/3/FMEA_ERR: -MDC=1; EMMC storage media error or storage insufficiency detected on slot 1. |
|
Impact |
The storage media became unavailable, system logs cannot be generated, and no configuration file can be created. |
|
Cause |
EMMC storage media error or storage insufficiency was detected. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
LVDS timeout on slot [UINT32] was detected on slot [UINT32]. |
|
Variable fields |
$1: Slot number of the switching fabric module in the device. $1: Slot number of the interface module in the device. |
|
Severity level |
3 (Error) |
|
Example |
DIAG/3/FMEA_ERR: -Slot=10; LVDS timeout on slot 10 was detected on slot 4. |
|
Impact |
The module was restarted. |
|
Cause |
The CPLD on the interface module was faulty. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Pattern 1: I2C error detected on chassis [UINT32] slot [UINT32]. Pattern 2: I2C error detected on chassis [UINT32] slot [UINT32] subslot [UINT32]. |
|
Variable fields |
Pattern 1: $1: Chassis number of the device. $2: Slot number of the card in the device. Pattern 2: $1: Chassis number of the device. $2: Slot number of the card in the device. $3: Sub slot number of the sub card. |
|
Severity level |
3 (Error) |
|
Example |
DIAG/3/FMEA_ERR: I2C error detected on chassis 0 slot 5. |
|
Impact |
The system might be unable to obtain transceiver module, voltage, or temperature information on the card or sub card. |
|
Cause |
A hardware failure has occurred on the l2C channel. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
I210 error detected on slot [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
3 (Error) |
|
Example |
DIAG/3/FMEA_ERR: I210 error detected on slot 0. |
|
Impact |
The management interface became unavailable. |
|
Cause |
A chip failure has occurred. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 ID. $2: CPU core ID. |
|
Severity level |
3 (Error) |
|
Example |
DIAG/3/CORE_EXCEED_THRESHOLD: Usage of CPU 0 core 2 exceeded the threshold (90%). |
|
Impact |
The device's running speed will slow down, CPU processing capacity will decrease, and available CPU resources will be insufficient. |
|
Cause |
The CPU core usage has exceeded the severe CPU core usage alarm threshold. |
|
Recommended action |
1. Use the display process cpu and monitor thread commands to display CPU usage information for all processes. 2. If the issue persists for more than 10 minutes, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
CORE_MINOR_RECOVERY
|
Message text |
Core usage minor alarm CPU [INT] core [INT] removed. |
|
Variable fields |
$1: CPU ID. $2: CPU core ID. |
|
Severity level |
5 (Notification) |
|
Example |
DIAG/5/CORE_MINOR_RECOVERY: Core usage minor alarm CPU 0 core 1 removed. |
|
Impact |
No negative impact on the system. |
|
Cause |
The CPU core usage has dropped to or below the minor CPU core usage alarm threshold. |
|
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 ID. $2: CPU core ID. |
|
Severity level |
4 (Warning) |
|
Example |
DIAG/4/CORE_MINOR_THRESHOLD: Usage of CPU 0 core 2 exceeded the threshold (80%). |
|
Impact |
No negative impact on the system. However, you must observe whether the CPU core usage continues to rise. |
|
Cause |
The CPU core usage has exceeded the minor CPU core usage alarm threshold. |
|
Recommended action |
1. Use the display process cpu and monitor thread commands to display CPU usage information for all processes. 2. There might be potential errors that affect the services provided. You must evaluate whether to take appropriate actions. |
CORE_RECOVERY
|
Message text |
Core usage alarm CPU [INT] core [INT] removed. |
|
Variable fields |
$1: CPU ID. $2: CPU core ID. |
|
Severity level |
5 (Notification) |
|
Example |
DIAG/5/CORE_RECOVERY: Core usage alarm CPU 0 core 1 removed. |
|
Impact |
No negative impact on the system. |
|
Cause |
The CPU core usage has dropped to or below the severe CPU core usage alarm threshold. |
|
Recommended action |
No action is required. |
CPU_MINOR_RECOVERY
|
Message text |
CPU usage minor alarm removed. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DIAG/5/CPU_MINOR_RECOVERY: CPU usage minor alarm removed. |
|
Impact |
No negative impact on the system. |
|
Cause |
The CPU usage decreased below the recovery threshold. The alarm was removed and the CPU usage status changed to recovered state. |
|
Recommended action |
No action is required. |
CPU_MINOR_THRESHOLD
|
Message text |
CPU usage is in minor alarm state. CPU usage: [UINT]% in last 1 minute. CPU usage thresholds: Minor: [UINT]% Severe: [UINT]% Recovery: [UINT]% Process info: JID PID PRI State FDs HH:MM:SS CPU Name [UINT] [UINT] [UINT] [CHAR] [UINT] [CHAR] [CHAR] [CHAR] Core states: ID Idle User Kernel Interrupt Busy CPU[UINT] [CHAR] [CHAR] [CHAR] [CHAR] [CHAR] |
|
Variable fields |
$1: CPU usage during the last minute. $2: Minor CPU usage alarm threshold. $3: Severe CPU usage alarm threshold. $4: CPU usage recovery threshold. $5: Job ID of the process. $6: PID of the process. $7: Priority of the process. $8: Status of the process. $9: Number of file handles. $10: Running time of the process. $11: CPU usage of the process. $12: Name of the process. $13: Core ID. $14: Idle time. $15: Time used by processes in the user space. $16: Time used by kernel threads. $17: Time used by interrupts. $18: Total time used. |
|
Severity level |
4 (Warning) |
|
Example |
DIAG/4/CPU_MINOR_THRESHOLD: CPU usage is in minor alarm state. CPU usage: 3% in last 1 minute. CPU usage thresholds: Minor: 1% Severe: 2% Recovery: 0% Process info: JID PID PRI State FDs HH:MM:SS CPU Name 108398 108398120 S 36 00:00:0 12.58% snmpd 52 52 102 S 0 00:01:2 2.58% [DRV_FWD] 371 371 120 S 95 00:18:5 0.17% pppd 90 90 120 R 18 00:12:0 0.34% diagd 109 109 119 S 41 00:11:1 0.00% vbrd Core states: ID Idle User Kernel Interrupt Busy CPU0 98.61% 0.24% 0.62% 0.53% 1.39% CPU1 99.88% 0.00% 0.03% 0.09% 0.12% |
|
Impact |
The device's operating speed will become slow, CPU processing capability will decline, and available CPU resources will become insufficient. |
|
Cause |
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 |
1. Check the log information and identify the processes that have high CPU usage. 2. Close the processes that are not in use based on the analysis result. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
CPU_SEVERE_RECOVERY
|
Message text |
CPU usage severe alarm removed. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DIAG/5/CPU_SEVERE_RECOVERY: CPU usage severe alarm removed. |
|
Impact |
No negative impact on the system. |
|
Cause |
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: [UINT]% in last 1 minute. CPU usage thresholds: Minor: [UINT]% Severe: [UINT]% Recovery: [UINT]% Process info: JID PID PRI State FDs HH:MM:SS CPU Name [UINT] [UINT] [UINT] [CHAR] [UINT] [CHAR] [CHAR] [CHAR] Core states: ID Idle User Kernel Interrupt Busy CPU[UINT] [CHAR] [CHAR] [CHAR] [CHAR] [CHAR] |
|
Variable fields |
$1: CPU usage during the last minute. $2: Minor CPU usage alarm threshold. $3: Severe CPU usage alarm threshold. $4: CPU usage recovery threshold. $5: Job ID of the process. $6: PID of the process. $7: Priority of the process. $8: Status of the process. $9: Number of file handles. $10: Running time of the process. $11: CPU usage of the process. $12: Name of the process. $13: Core ID. $14: Idle time. $15: Time used by processes in the user space. $16: Time used by kernel threads. $17: Time used by interrupts. $18: Total time used. |
|
Severity level |
3 (Error) |
|
Example |
DIAG/3/CPU_SEVERE_THRESHOLD: CPU usage is in severe alarm state. CPU usage: 3% in last 1 minute. CPU usage thresholds: Minor: 1% Severe: 2% Recovery: 0% Process info: JID PID PRI State FDs HH:MM:SS CPU Name 108398 108398120 S 36 00:00:0 12.58% snmpd 52 52 102 S 0 00:01:2 2.58% [DRV_FWD] 371 371 120 S 95 00:18:5 0.17% pppd 90 90 120 R 18 00:12:0 0.34% diagd 109 109 119 S 41 00:11:1 0.00% vbrd Core states: ID Idle User Kernel Interrupt Busy CPU0 98.61% 0.24% 0.62% 0.53% 1.39% CPU1 99.88% 0.00% 0.03% 0.09% 0.12% |
|
Impact |
The device's operating speed will become slow, CPU processing capability will decline, and available CPU resources will become insufficient. |
|
Cause |
The CPU usage increased above the severe alarm threshold and entered severe alarm state. The device sends this message periodically until the severe alarm is removed. |
|
Recommended action |
1. Use the display cpu-usage configuration" command to view the alarm thresholds. Use the monitor cpu-usage command to adjust the alarm thresholds as required. 2. If the issue persists for more than 10 minutes, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
DIAG_DMA_MEM_CRITICAL_THRESHOLD
|
Message text |
Free DMA memory [UINT]KB is equal to or less than the critical threshold [UINT]KB. |
|
Variable fields |
N/A |
|
Severity level |
1 (Alert) |
|
Example |
DIAG/1/DIAG_DMA_MEM_CRITICAL_THRESHOLD: Free DMA memory 1600KB is equal to or less than the critical threshold 800KB. |
|
Impact |
No negative impact on the system. However, you must observe whether the free DMA memory continues to decrease. |
|
Cause |
The free DMA memory is less than or equal to the DMA memory alarm threshold. |
|
Recommended action |
Use the display memory-threshold dma command to display DMA memory alarm information. · If the threshold is set incorrectly, use the memory-threshold dma command to edit it. · If the threshold is set correctly, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
DIAG_DMA_MEM_RECOVERY
|
Message text |
Free DMA memory [UINT]KB is greater than the normal threshold [UINT]KB. DMA memory alarm removed. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DIAG/4/DIAG_DMA_MEM_RECOVERY: Free DMA memory 1600KB is greater than the normal threshold 1000KB. DMA memory alarm removed. |
|
Impact |
No negative impact on the system. |
|
Cause |
The idle DMA memory has exceeded the DMA memory alarm restoration threshold. |
|
Recommended action |
No action is required. |
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 (Warning) |
|
Example |
DIAG/4/DIAG_FD_UPLIMIT_REACHED: FD number upper limit already reached: Process name=snmpd, PID=244. |
|
Impact |
The process cannot open new files. |
|
Cause |
The maximum number of file descriptors that a process can use has been reached. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
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 (Warning) |
|
Example |
DIAG/4/DIAG_FD_UPLIMIT_TO_REACH: Number of FDs is about to reach the upper limit. Process name=snmpd, PID=244. |
|
Impact |
No negative impact on the system. Observe whether the number of file descriptors used by the process keeps rising. |
|
Cause |
The maximum number of file descriptors that a process can use was about to be reached. |
|
Recommended action |
No action is required. |
DIAG_PROCESS_DEADLOOP
|
Message text |
The process [STRING] has been running for [UINT64] minutes. |
|
Variable fields |
$1: Name of the process. $2: Duration of the process dead loop. |
|
Severity level |
5 (Notification) |
|
Example |
DIAG/5/DIAG_PROCESS_DEADLOOP: The process edev has been running for 2 minutes. |
|
Impact |
The services running in the process will be affected. |
|
Cause |
A process is in a dead loop state and continues to run. |
|
Recommended action |
1. Use the display process command to check the process running state. If a process remains in R state for a long period of time, it will be forcibly restarted after a certain time. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
DIAG_PROCESS_DEADLOOP_KILL
|
Message text |
The process [STRING] has been running for [UINT64] minutes and is killed forcibly. |
|
Variable fields |
$1: Name of the process. $2: Duration of the process dead loop. |
|
Severity level |
3 (Error) |
|
Example |
DIAG/3/DIAG_PROCESS_DEADLOOP_KILL: The process edev has been running for 10 minutes and is killed forcibly. |
|
Impact |
No negative impact on the system. |
|
Cause |
A process is in a dead loop state and continues to run. This message is generated when the process is forcibly terminated. |
|
Recommended action |
1. Use the display process command to identify whether the process has recovered. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
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 |
4 (Warning) |
|
Example |
DIAG/4/DIAG_STORAGE_BELOW_THRESHOLD: The usage of flash (90%) was below or equal to the threshold of 95%. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 |
4 (Warning) |
|
Example |
DIAG/4/DIAG_STORAGE_EXCEED_THRESHOLD: The usage of flash (96%) exceeded the threshold of 95%. |
|
Impact |
Services that require disk writing will be affected, and the storage medium will not have sufficient space. |
|
Cause |
This message indicates that the storage medium does not have sufficient space, because the disk usage is higher than the threshold. |
|
Recommended action |
1. 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. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
KERNEL_MEMFRAGMT_BELOW_THRESHOLD
|
Message text |
Free kernel memory fragment ratio[UINT]% is less than the threshold[UINT]%. |
|
Variable fields |
$1: Current free kernel memory fragment ratio. $2: Free kernel memory fragment ratio alarm threshold |
|
Severity level |
4 (Warning) |
|
Example |
DIAG/4/KERNEL_MEMFRAGMT_BELOW_THRESHOLD: Free kernel memory fragment ratio 30% is less than the threshold 40%. |
|
Impact |
No negative impact on the system. |
|
Cause |
When a kernel thread is running, it requests memory from the kernel space. This memory is requested and released as a whole. Even if parts of the memory block are used during the thread's execution and are no longer needed, they cannot be released early for use by other kernel threads. This type of idle memory that cannot currently be used is also known as a memory fragment. You can use the monitor kernel memory fragment ratio command to monitor the ratio of memory fragments in the kernel space to the total kernel space memory. This message is generated when the idle ratio of kernel space memory fragments is lower than the alarm threshold. |
|
Recommended action |
No action is required. |
KERNEL_MEMFRAGMT_EXCEED_THRESHOLD
|
Message text |
Free kernel memory fragment ratio [UINT]% is equal to or greater than the threshold [UINT]%. |
|
Variable fields |
$1: Current free kernel memory fragment ratio. $2: Free kernel memory fragment ratio alarm threshold |
|
Severity level |
1 (Alert) |
|
Example |
DIAG/1/KERNEL_MEMFRAGMT_EXCEED_THRESHOLD: Free kernel memory fragment ratio 50% is equal to or greater than the threshold 40%. |
|
Impact |
The device's running speed will slow down, and the available memory resources will be insufficient. |
|
Cause |
When a kernel thread is running, it requests memory from the kernel space. This memory is requested and released as a whole. Even if parts of the memory block are used during the thread's execution and are no longer needed, they cannot be released early for use by other kernel threads. This type of idle memory that cannot currently be used is also known as a memory fragment. You can use the monitor kernel memory fragment ratio command to monitor the ratio of memory fragments in the kernel space to the total kernel space memory. This message is generated when the idle ratio of kernel space memory fragments is greater than or equal to the alarm threshold. |
|
Recommended action |
1. Verify that appropriate alarm thresholds are set. To view the alarm thresholds, use the display kernel memory fragment free command. Then you can use the memory-threshold command to edit the alarm thresholds if required. 2. Use the display system internal kernel memory pool command to display the details of kernel memory usage to further locate the issue. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
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 (Warning) |
|
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 |
|
Impact |
No negative impact on the system. Observe whether the available memory keeps decreasing. |
|
Cause |
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, critical, or early-warning. |
|
Severity level |
1 (Alert) |
|
Example |
DIAG/1/MEM_BELOW_THRESHOLD: Memory usage has dropped below critical threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
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, critical, or early-warning. |
|
Severity level |
1 (Alert) |
|
Example |
DIAG/1/MEM_EXCEED_THRESHOLD: Memory minor threshold has been exceeded. |
|
Impact |
The running speed of the device will become low and the available memory resources will become insufficient. |
|
Cause |
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. |
MEM_USAGE_RECOVERY
|
Message text |
Memory usage recovered to normal state. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DIAG/5/MEM_USAGE_RECOVERY: Memory usage recovered to normal state. |
|
Impact |
No negative impact on the system. |
|
Cause |
The current memory usage of the device has dropped to or below the memory usage threshold. |
|
Recommended action |
No action is required. |
MEM_USAGE_THRESHOLD
|
Message text |
Memory usage is in alarm state. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DIAG/4/MEM_USAGE_THRESHOLD: Memory usage is in alarm state. |
|
Impact |
The device's running speed will slow down, and the available memory resources will be insufficient. |
|
Cause |
The current memory usage of the device has exceeded the memory usage threshold. |
|
Recommended action |
1. 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 edit the alarm thresholds if required. 2. Verify that the device is not under attack by checking the ARP table and routing table. 3. Examine and optimize the network, for example, reduce the number of routes or replace the device with a higher-performance device. |
DLDP messages
This section contains DLDP messages.
DLDP_AUTHENTICATION_FAILED
|
Message text |
The DLDP packet failed the authentication because of unmatched [STRING] field. |
|
Variable fields |
$1: Authentication field. · AUTHENTICATION PASSWORD—Authentication password mismatch. · AUTHENTICATION TYPE—Authentication type mismatch. · INTERVAL—Advertisement interval mismatch. |
|
Severity level |
5 (Notification) |
|
Example |
DLDP/5/DLDP_AUTHENTICATION_FAILED: The DLDP packet failed the authentication because of unmatched INTERVAL field. |
|
Impact |
DLDP cannot operate correctly. |
|
Cause |
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 (Informational) |
|
Example |
DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface Ethernet1/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
The optical fiber is connected correctly. |
|
Recommended action |
No action is required. |
DLDP_LINK_SHUTMODECHG
|
Message text |
DLDP automatically blocked the interface [STRING] because the port shutdown mode was changed to auto mode. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 (Notification) |
|
Example |
DLDP/5/DLDP_LINK_SHUTMODECHG: DLDP automatically blocked the interface Ethernet1/1 because the port shutdown mode was changed to auto mode. |
|
Impact |
The interface cannot forward service traffic. |
|
Cause |
The port shut down mode was changed from manual to auto, and DLDP detects a unidirectional link. |
|
Recommended action |
Check for incorrect cable connection, cable falloff, or other problems. |
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. |
|
Severity level |
3 (Error) |
|
Example |
DLDP/3/DLDP_LINK_UNIDIRECTIONAL: DLDP detected a unidirectional link on interface Ethernet1/1. DLDP automatically blocked the interface. |
|
Impact |
The interface cannot forward service traffic correctly. |
|
Cause |
· One fiber of a fiber pair is not connected or is broken. · Fibers are cross-connected. |
|
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 (Notification) |
|
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. |
|
Impact |
DLDP neighbor relationship cannot be established, and DLDP detection connection cannot be established. |
|
Cause |
No Advertisement packets are received when the neighbor aging timer expires. |
|
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 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
Advertisement packets are received when the neighbor aging timer expires. |
|
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 (Notification) |
|
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. |
|
Impact |
DLDP neighbor relationship cannot be established, and DLDP detection connection cannot be established. |
|
Cause |
A DISABLE or LINKDOWN packet is received. |
|
Recommended action |
No action is required. |
DOMAIN messages
This section contains DOMAIN messages.
DOMAIN_IP_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolLowerValue=[STRING]; IP resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: Low alarm threshold for IP address usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IP_LOWTHR_ALM: -Domain=abc-IPUsage=10%-IPPoolLowerValue=20%; IP resource usage reached or dropped below the lower threshold. |
|
Explanation |
The usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or dropped below the low alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_IP_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolLowerValue=[STRING]; Low IP resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: Low alarm threshold for IP address usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IP_LOWTHR_ALM_REMOVE: -Domain=dom1-IPUsage=50%-IPPoolLowerValue=20%; Low IP resource usage alarm condition cleared. |
|
Explanation |
The usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or exceeded the value calculated by using the formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IP_UPTHR_ALM
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolUpperValue=[STRING]; IP resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: High alarm threshold for IP address usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IP_UPTHR_ALM: -Domain=dom1-IPUsage=90%-IPPoolUpperValue=80%; IP resource usage reached or exceeded the upper threshold. |
|
Explanation |
The usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or exceeded the high alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_IP_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolUpperValue=[STRING]; High IP resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: High alarm threshold for IP address usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IP_UPTHR_ALM_REMOVE: -Domain=dom1-IPUsage=50%-IPPoolUpperValue=80%; High IP resource usage alarm condition cleared. |
|
Explanation |
The usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or dropped below the value calculated by using the formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolLowerValue=[STRING]; IPv6 address resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IPV6_LOWTHR_ALM: -Domain=abc-IPv6Usage=10%-IPv6PoolLowerValue=20%; IPv6 address resource usage reached or dropped below the lower threshold. |
|
Explanation |
The usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the low alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolLowerValue=[STRING]; Low IPv6 address resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IPV6_LOWTHR_ALM_REMOVE: -Domain=dom1-IPv6Usage=50%-IPv6PoolLowerValue=20%; Low IPv6 address resource usage alarm condition cleared. |
|
Explanation |
The usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the value calculated by using the formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_UPTHR_ALM
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolUpperValue=[STRING]; IPv6 address resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolUpperValue=[STRING]; IPv6 address resource usage reached or exceeded the upper threshold. |
|
Explanation |
The usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the high alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolUpperValue=[STRING]; High IPv6 address resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IPV6_UPTHR_ALM_REMOVE: -Domain=dom1-IPv6Usage=50%-IPv6PoolUpperValue=80%; High IPv6 address resource usage alarm condition cleared. |
|
Explanation |
The usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the value calculated by using the formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; ND prefix resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. ND prefixes refer to IPv6 prefixes assigned by ND. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_ND_PREF_LOWTHR_ALM: -Domain=abc-NDPrefixUsage=10%-IPv6PoolLowerValue=20%; ND prefix resource usage reached or dropped below the lower threshold. |
|
Explanation |
The usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or dropped below the low alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; Low ND prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE: -Domain=abc-NDPrefixUsage=50%-IPv6PoolLowerValue=20%; Low ND prefix resource usage alarm condition cleared. |
|
Explanation |
The usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or exceeded the value calculated by using the formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_UPTHR_ALM
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; ND prefix resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_ND_PREF_UPTHR_ALM: -Domain=abc-NDPrefixUsage=90%-IPv6PoolUpperValue=80%; ND prefix resource usage reached or exceeded the upper threshold. |
|
Explanation |
The usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or exceeded the high alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; High ND prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_ND_PREF_UPTHR_ALM_REMOVE: -Domain=abc-NDPrefixUsage=50%-IPv6PoolUpperValue=80%; High ND prefix resource usage alarm condition cleared. |
|
Explanation |
The usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or dropped below the value calculated by using the formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; PD prefix resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. PD prefixes refer to IPv6 prefixes assigned by DHCPv6 PD. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_PD_PREF_LOWTHR_ALM: -Domain=abc-PDPrefixUsage=10%-IPv6PoolLowerValue=20%; PD prefix resource usage reached or dropped below the lower threshold. |
|
Explanation |
The usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the low alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; Low PD prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE: -Domain=abc-PDPrefixUsage=50%-IPv6PoolLowerValue=20%; Low PD prefix resource usage alarm condition cleared. |
|
Explanation |
The usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the value calculated by using the formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_UPTHR_ALM
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; PD prefix resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_PD_PREF_UPTHR_ALM: -Domain=abc-PDPrefixUsage=90%-IPv6PoolUpperValue=80%; PD prefix resource usage reached or exceeded the upper threshold. |
|
Explanation |
The usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the high alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; High PD prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_PD_PREF_UPTHR_ALM_REMOVE: -Domain=abc-PDPrefixUsage=50%-IPv6PoolUpperValue=80%; High PD prefix resource usage alarm condition cleared. |
|
Explanation |
The usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the value calculated by using the formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN messages
This section contains DOMAIN messages.
DOMAIN_IP_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolLowerValue=[STRING]; IP resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: Lower alarm threshold for IP address usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IP_LOWTHR_ALM: -Domain=abc-IPUsage=10%-IPPoolLowerValue=20%; IP resource usage reached or dropped below the lower threshold. |
|
Impact |
More clients might go offline unexpectedly. |
|
Cause |
A low-usage alarm was generated when the usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or dropped below the lower alarm threshold. Possible reasons include: · Users go offline and the IP usage in the domain drops below the lower threshold. · The lower threshold configured by using the ip-usage-warning low-threshold command is too high. |
|
Recommended action |
1. Use the display this command in domain view to view the ip-usage-warning low-threshold configuration, and verify if the current lower threshold for the IP usage is proper. ¡ If the lower threshold is too high, proceed to step 2. ¡ If the lower threshold is proper, proceed to step 3. 2. Use the ip-usage-warning low-threshold command in domain view to adjust the lower threshold for the IP usage. 3. In any view, use the display dhcp pool-usage and display dhcp pool-group-usage commands to view the current IP usage. ¡ If the current IP usage drops below or is approaching the lower threshold, use the display aaa offline-record command to view the user disassociation reason records. If the disassociation reason is User request, no action is required. If the disassociation reason is not User request, contact Technical Support. ¡ If the current IP is not approaching the lower threshold, proceed to step 4. 4. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
DOMAIN_IP_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolLowerValue=[STRING]; Low IP resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: Lower alarm threshold for IP address usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IP_LOWTHR_ALM_REMOVE: -Domain=dom1-IPUsage=50%-IPPoolLowerValue=20%; Low IP resource usage alarm condition cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The low IP resource usage alarm was cleared when the usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or exceeded the value calculated by using the following formula: Lower alarm threshold + (upper alarm threshold – lower alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IP_UPTHR_ALM
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolUpperValue=[STRING]; IP resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: Upper alarm threshold for IP address usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IP_UPTHR_ALM: -Domain=dom1-IPUsage=90%-IPPoolUpperValue=80%; IP resource usage reached or exceeded the upper threshold. |
|
Impact |
The IP addresses in the IP address pool for the domain might be exhausted, causing new users to be unable to come online because they cannot obtain an IP address. |
|
Cause |
A high-usage alarm was generated when the usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or exceeded the upper alarm threshold. |
|
Recommended action |
1. In domain view, use display this to view the ip-usage-warning high-threshold configuration. ¡ If ip-usage-warning high-threshold is configured and the threshold value is in the range of 1 to 100 (excluded), proceed to step 2. ¡ If ip-usage-warning high-threshold is not configured or the threshold value is 100, proceed to step 4. 2. In any view, use display dhcp pool-usage and display dhcp pool-group-usage to view if the current IP address usage has reached the peak. ¡ If yes, proceed to step 3. ¡ If no, no action is required. 3. Expand the range of the local address pool or address pool group , or configure new users to come online in other domains. Wait for 30 minutes and verify if the alarm can be generated again. ¡ If yes, proceed to step 4. ¡ If no, no action is required. 4. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
DOMAIN_IP_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolUpperValue=[STRING]; High IP resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: Upper alarm threshold for IP address usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IP_UPTHR_ALM_REMOVE: -Domain=dom1-IPUsage=50%-IPPoolUpperValue=80%; High IP resource usage alarm condition cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The high IP resource usage alarm was cleared when the usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or dropped below the value calculated by using the following formula: Upper alarm threshold – (upper alarm threshold – lower alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolLowerValue=[STRING]; IPv6 address resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: Lower alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IPV6_LOWTHR_ALM: -Domain=abc-IPv6Usage=10%-IPv6PoolLowerValue=20%; IPv6 address resource usage reached or dropped below the lower threshold. |
|
Impact |
More clients might go offline unexpectedly. |
|
Cause |
When the IPv6 address usage in the authorized IPv6 address pool or IPv6 address pool group for the domain reaches or drops below the lower threshold, a lower limit alarm is generated. Possible reasons include: · Users go offline and the IPv6 usage in the domain drops below the lower threshold. · The lower threshold configured by using the ipv6-usage-warning low-thresholdcommand is too high. |
|
Recommended action |
1. Use the display this command in domain view to view ipv6-usage-warning low-threshold configuration, and verify if the current lower threshold for IPv6 usage is proper. ¡ If the lower threshold is too high, proceed to step 2. ¡ If the lower threshold is proper, proceed to step 3. 2. Use ipv6-usage-warning low-threshold in domain view to adjust the lower threshold for IPv6 usage. 3. In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view if the current IPv6 address usage has reached the peak. ¡ If the current IPv6 usage drops below or is approaching the lower threshold, use the display aaa offline-record command to view the user disassociation reason records. If the disassociation reason is User request, no action is required. If the disassociation reason is not User request, contact Technical Support. ¡ If the current IPv6 is not approaching the lower threshold, proceed to step 4. 4. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
DOMAIN_IPV6_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolLowerValue=[STRING]; Low IPv6 address resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: Lower alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IPV6_LOWTHR_ALM_REMOVE: -Domain=dom1-IPv6Usage=50%-IPv6PoolLowerValue=20%; Low IPv6 address resource usage alarm condition cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The low IPv6 address resource usage alarm was cleared when the usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the value calculated by using the following formula: Lower alarm threshold + (upper alarm threshold – lower alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_UPTHR_ALM
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolUpperValue=[STRING]; IPv6 address resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: Upper alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IPV6_UPTHR_ALM: -Domain=abc-IPv6Usage=90%-IPv6PoolUpperValue=80%; IPv6 address resource usage reached or exceeded the upper threshold. |
|
Impact |
The IPv6 addresses in the address pool for the domain might be exhausted, causing new users to be unable to come online because they cannot obtain an IPv6 address. |
|
Cause |
A high-usage alarm was generated when the usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the upper alarm threshold. |
|
Recommended action |
1. In domain view, use the display this command to view the ipv6-usage-warning high-threshold configuration. ¡ If ipv6-usage-warning high-threshold is configured and the upper threshold value is in the range of 1 (included) to 100 (excluded), proceed to step 2. ¡ If ipv6-usage-warning high-threshold is not configured or the configured upper threshold is 100, proceed to step 4. 2. In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view if the current IPv6 address usage has reached the peak. ¡ If yes, proceed to step 3. ¡ If no, no action is required. 3. Expand the range of the local address pool or address pool group , or configure new users to come online in other domains. Wait for 30 minutes and verify if the alarm can be generated again. ¡ If yes, proceed to step 4. ¡ If no, no action is required. 4. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
DOMAIN_IPV6_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolUpperValue=[STRING]; High IPv6 address resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: Upper alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IPV6_UPTHR_ALM_REMOVE: -Domain=dom1-IPv6Usage=50%-IPv6PoolUpperValue=80%; High IPv6 address resource usage alarm condition cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The high IPv6 address resource usage alarm was cleared when the usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the value calculated by using the following formula: Upper alarm threshold – (upper alarm threshold – lower alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_WEB_SERVER_ACCESS
|
Message text |
Domain=[STRING]-WebActiveServerIPv6URL=[STRING]; This trap is generated when the IPv6 Web server is restored to available. |
|
Variable fields |
$1: ISP domain name. $2: Current active IPv6 Web server URL. |
|
Severity level |
5 (Notification) |
|
Example |
DOMAIN/5/DOMAIN_IPV6_WEB_SERVER_ACCESS: -Domain=dom1-WebActiveServerIPv6URL=test.com; This trap is generated when the IPv6 Web server is restored to available. |
|
Impact |
No negative impact on the system. |
|
Cause |
This notification is generated when the IPv6 URL of the Web server in a domain becomes available. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_WEB_SERVER_NOT_REACH
|
Message text |
-Domain=[STRING]-WebActiveServerIPv6URL=[STRING]; This trap is generated when the IPv6 Web server is unavailable. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 Web server URL that became unavailable. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IPv6_WEB_SERVER_NOT_REACH: -Domain=1-WebActiveServerIPv6URL=test.com; This trap is generated when the IPv6 Web server is unavailable. |
|
Impact |
User web authentication fails. |
|
Cause |
This notification is generated when all IPv6 URLs of the Web server in a domain become unavailable. Possible reasons include: The Web server is faulty or communication between the device and the Web server is faulty. |
|
Recommended action |
1. Examine the operation status of the Web server. 2. If the Web server is down, contact the server administrator and bring up the server. 3. If no recovery log message is generated after the Web server is up, troubleshoot network connection errors between the device and the Web server until the alarm is cleared. |
DOMAIN_IPV6_WEB_SERVER_URL_SWITCH
|
Message text |
-Domain=[STRING]-WebActiveServerIPv6URL=[STRING]; This trap is generated when the valid IPv6 URL of the Web server changes. |
|
Variable fields |
$1: ISP domain name. $2: Current active IPv6 Web server URL. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_IPV6_WEB_SERVER_URL_SWITCH: -Domain=dom1-WebActiveServerIPv6URL= test1.com; This trap is generated when the valid IPv6 URL of the Web server changes. |
|
Impact |
No negative impact on the system. |
|
Cause |
This notification is generated when the IPv6 URL of the Web server in a domain changes for one of the following reasons: · The IPv6 URL of the active Web server changes. · The primary IPv6 Web server URL becomes inaccessible and the secondary IPv6 Web server URL takes over to provide services. · The primary IPv6 Web server URL restores its accessibility and preempts the secondary IPv6 Web server URL to provide services. |
|
Recommended action |
· Verify that the IPv6 Web server URLs in the domain are configured correctly as planned. · Verify that the link between the device and the Web server is operating correctly. |
DOMAIN_ND_PREF_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; ND prefix resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. ND prefixes refer to IPv6 prefixes assigned by ND. $3: Lower alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_ND_PREF_LOWTHR_ALM: -Domain=abc-NDPrefixUsage=10%-IPv6PoolLowerValue=20%; ND prefix resource usage reached or dropped below the lower threshold. |
|
Impact |
If this alarm is triggered due to the lower threshold value set too high, it may cause more users to go offline abnormally. |
|
Cause |
When the ND prefix usage in the authorized ND prefix pool or ND prefix pool group for the domain reaches or drops below the lower threshold, a lower limit alarm is generated. Possible reasons include: · The IPv6 ND prefix usage in the domain drops below the lower threshold. · The lower threshold configured by using the ipv6-usage-warning low-thresholdcommand is too high. |
|
Recommended action |
1. Use the display this command in domain view to view ipv6-usage-warning low-threshold configuration, and verify if the current lower threshold for ND prefix usage is proper. ¡ If the lower threshold is too high, proceed to step 2. ¡ If the lower threshold is proper, proceed to step 3. 2. Use ipv6-usage-warning low-threshold in domain view to adjust the lower threshold for ND prefix usage. 3. In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view the current ND prefix usage. ¡ If the current ND prefix usage drops below or is approaching the lower threshold, use the display aaa offline-record command to view the user disassociation reason records. If the disassociation reason is User request, no action is required. If the disassociation reason is not User request, contact Technical Support. ¡ If the current ND prefix usage is not approaching the lower threshold, proceed to step 4. 4. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; Low ND prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: Lower alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE: -Domain=abc-NDPrefixUsage=50%-IPv6PoolLowerValue=20%; Low ND prefix resource usage alarm condition cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The low ND prefix resource usage alarm was cleared when the usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or exceeded the value calculated by using the following formula: Lower alarm threshold + (upper alarm threshold – lower alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_UPTHR_ALM
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; ND prefix resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: Upper alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_ND_PREF_UPTHR_ALM: -Domain=abc-NDPrefixUsage=90%-IPv6PoolUpperValue=80%; ND prefix resource usage reached or exceeded the upper threshold. |
|
Impact |
The ND prefixes in the IP address pool for the domain might be exhausted, causing new users to be unable to come online because they cannot obtain an ND prefix. |
|
Cause |
A high-usage alarm was generated when the usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or exceeded the upper alarm threshold. |
|
Recommended action |
1. In domain view, use the display this command to view the ipv6-usage-warning high-threshold configuration. ¡ If ipv6-usage-warning high-threshold is configured and the upper threshold value is in the range of 1 (1 included) to 100 (100 excluded), proceed to step 2. ¡ If ipv6-usage-warning high-threshold is not configured or the configured upper threshold is 100, proceed to step 4. 2. In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to verify if the current ND prefix usage has reached the upper threshold. ¡ If yes, proceed to step 3. ¡ If no, no action is required. 3. Expand the range of the local address pool or address pool group , or configure new users to come online in other domains. Wait for 30 minutes and verify if the alarm can be generated again. ¡ If yes, proceed to step 4. ¡ If no, no action is required. 4. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
DOMAIN_ND_PREF_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; High ND prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: Upper alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_ND_PREF_UPTHR_ALM_REMOVE: -Domain=abc-NDPrefixUsage=50%-IPv6PoolUpperValue=80%; High ND prefix resource usage alarm condition cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The high ND prefix resource usage alarm was cleared when the usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or dropped below the value calculated by using the following formula: Upper alarm threshold – (upper alarm threshold – lower alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; PD prefix resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. PD prefixes refer to IPv6 prefixes assigned by DHCPv6 PD. $3: Lower alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_PD_PREF_LOWTHR_ALM: -Domain=abc-PDPrefixUsage=10%-IPv6PoolLowerValue=20%; PD prefix resource usage reached or dropped below the lower threshold. |
|
Impact |
The DHCPv6 PD prefixes in the domain might be exhausted, causing new users to be unable to come online because they cannot obtain a DHCPv6 PD address. |
|
Cause |
A low-usage alarm was generated when the usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the lower alarm threshold. Possible reasons: · Users go offline and the DHCPv6 PD prefix usage in the domain drops below the lower threshold. · The lower threshold configured by using the ipv6-usage-warning low-thresholdcommand is too high. |
|
Recommended action |
1. Use the display this command in domain view to view ipv6-usage-warning low-threshold configuration, and verify if the current lower threshold for IPv6 prefix usage is proper. ¡ If the lower threshold is too high, proceed to step 2. ¡ If the lower threshold is proper, proceed to step 3. 2. Use ipv6-usage-warning low-threshold in domain view to adjust the lower threshold for IPv6 prefix usage. 3. In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to view the current PD prefix usage. ¡ If the current PD prefix usage drops below or is approaching the lower threshold, use the display aaa offline-record command to view the user disassociation reason records. If the disassociation reason is User request, no action is required. If the disassociation reason is not User request, contact Technical Support. ¡ If the current PD prefix usage is not approaching the lower threshold, proceed to step 4. 4. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; Low PD prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: Lower alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE: -Domain=abc-PDPrefixUsage=50%-IPv6PoolLowerValue=20%; Low PD prefix resource usage alarm condition cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The low PD prefix resource usage alarm was cleared when the usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the value calculated by using the following formula: Lower alarm threshold + (upper alarm threshold – lower alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_UPTHR_ALM
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; PD prefix resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: Upper alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_PD_PREF_UPTHR_ALM: -Domain=abc-PDPrefixUsage=90%-IPv6PoolUpperValue=80%; PD prefix resource usage reached or exceeded the upper threshold. |
|
Impact |
The DHCPv6-PD prefixes in the domain may be exhausted, causing new users to be unable to go online because they cannot be assigned an DHCPv6-PD address. |
|
Cause |
A high-usage alarm was generated when the usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the upper alarm threshold. |
|
Recommended action |
1. In domain view, use the display this command to view the ipv6-usage-warning high-threshold configuration. ¡ If ipv6-usage-warning high-threshold is configured and the upper threshold value is in the range of 1 (1 included) to 100 (100 excluded), proceed to step 2. ¡ If ipv6-usage-warning high-threshold is not configured or the configured upper threshold is 100, proceed to step 4. 2. In any view, use the display ipv6 dhcp pool-usage and display ipv6 dhcp pool-group-usage commands to verify if the current PD prefix usage has reached the upper threshold. ¡ If yes, proceed to step 3. ¡ If no, no action is required. 3. Expand the range of the local address pool or address pool group , or configure new users to come online in other domains. Wait for 30 minutes and verify if the alarm can be generated again. ¡ If yes, proceed to step 4. ¡ If no, no action is required. 4. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
DOMAIN_PD_PREF_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; High PD prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: Upper alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_PD_PREF_UPTHR_ALM_REMOVE: -Domain=abc-PDPrefixUsage=50%-IPv6PoolUpperValue=80%; High PD prefix resource usage alarm condition cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The high PD prefix resource usage alarm was cleared when the usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the value calculated by using the following formula: Upper alarm threshold – (upper alarm threshold – lower alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_WEB_SERVER_ACCESS
|
Message text |
-Domain=[STRING]-WebActiveServerURL=[STRING]; This trap is generated when the Web server is restored to available. |
|
Variable fields |
$1: ISP domain name. $2: URL of a Web server. |
|
Severity level |
5 (Notification) |
|
Example |
DOMAIN/5/DOMAIN_WEB_SERVER_ACCESS: -MDC=1; -Domain=dom1-WebActiveServerURL=test.com; This trap is generated when the Web server is restored to available. |
|
Impact |
No negative impact on the system. |
|
Cause |
This notification is generated when a Web server URL in an ISP domain becomes reachable. |
|
Recommended action |
No action is required. |
DOMAIN_WEB_SERVER_NOT_REACH
|
Message text |
-Domain=[STRING]-WebActiveServerURL=[STRING]; This trap is generated when the Web server is unavailable. |
|
Variable fields |
$1: ISP domain name. $2: URL of a Web server. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_WEB_SERVER_NOT_REACH: -Domain=1-WebActiveServerURL=test.com; This trap is generated when the Web server is unavailable. |
|
Impact |
User web authentication fails. |
|
Cause |
This notification is generated when all Web server URLs in an ISP domain become unreachable. Possible reasons include: The Web server is faulty or communication between the device and the Web server is faulty. |
|
Recommended action |
1. Examine the operation status of the Web server. 2. If the Web server is down, contact the server administrator and bring up the server. 3. If no recovery alarm is generated after the Web server is up, troubleshoot network connection errors between the device and the Web server until the alarm is cleared. |
DOMAIN_WEB_SERVER_URL_SWITCH
|
Message text |
-Domain=[STRING]-WebActiveServerURL=[STRING]; This trap is generated when the valid URL of the Web server changes. |
|
Variable fields |
$1: ISP domain name. $2: URL of the Web server in use. |
|
Severity level |
4 (Warning) |
|
Example |
DOMAIN/4/DOMAIN_WEB_SERVER_URL_SWITCH: -Domain=dom1-WebActiveServerURL= test1.com; This trap is generated when the valid URL of the Web server changes. |
|
Impact |
No negative impact on the system. |
|
Cause |
This notification is generated when the URL of the Web server in use is changed to another URL in the following situations: · Configuration changes for the URL of the Web server in use. · The URL of the primary server becomes unreachable. The URL in use is changed to the URL of the secondary Web server. · The URL of the primary server becomes reachable. The URL in use is changed from the URL of the secondary Web server to the URL of the primary Web server. |
|
Recommended action |
1. Verify that the Web server URL settings are configured as expected in the ISP domain. 2. Check the links between the device and the unreachable Web server for connectivity issues and resolve the issues. |
DOT1X messages
This section contains 802.1X messages.
DOT1X_CLEAR_MAX_USER_THRESHOLD
|
Message text |
The max-user high alarm condition cleared when the percentage of online 802.1X users reached or dropped below the max-user clear threshold on interface [STRING]. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
5 (Notification) |
|
Example |
DOT1X/5/DOT1X_CLEAR_MAX_USER_THRESHOLD: The max-user high alarm condition cleared when the percentage of online 802.1X users reached or dropped below the max-user clear threshold on interface GigabitEthernet1/0/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
The percentage of current online 802.1X users to the maximum number of concurrent 802.1X users on the interface dropped to the alarm clear threshold from a value above or equal to the alarm threshold. |
|
Recommended action |
No action is required. |
DOT1X_LOGIN_FAILURE
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-SVLAN=[STRING]-CVLAN=[STRING]-Username=[STRING]; User failed 802.1X authentication. Reason:[STRING]. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: CVLAN ID. $4: SVLAN ID. $5: Username. $6: Authentication failure reason. Values include: ¡ Supplicant logoff. ¡ Port status error. ¡ Reauthentication failure. ¡ Deauthorization by the device. ¡ The port was administratively down. ¡ Account password error. ¡ Online handshake failure. ¡ Session timeout. ¡ Server request. ¡ Real-time accounting failure. ¡ Default error. ¡ Port error. |
|
Severity level |
6 (Informational) |
|
Example |
DOT1X/6/DOT1X_LOGIN_FAILURE:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-SVLAN=444-CVLAN=555-Username=aaa; User failed 802.1X authentication. Reason: Supplicant logoff. |
|
Impact |
The 802.1X user cannot come online. |
|
Cause |
This message is generated when a user fails 802.1X authentication. |
|
Recommended action |
1. Verify that the 802.1X authentication settings are correct. 2. Locate the failure reason and resolve the issue according to the failure reason. If the configuration of the device or authentication server is incorrect, promptly modify the configuration of the device or server. Common configuration errors include inconsistent authentication methods on the device and server, no username has been added on the server, and incorrect username or password. 3. If the issue persists, collect alarm information, log information, and configuration data, and then contact Technical Support for help. |
DOT1X_LOGIN_SUCC
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-SVLAN=[STRING]-CVLAN=[STRING]-Username=[STRING]; User passed 802.1X authentication and came online. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: SVLAN ID. $4: CVLAN ID. $5: Username. |
|
Severity level |
6 (Informational) |
|
Example |
DOT1X/6/DOT1X_LOGIN_SUCC:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-SVLAN=444-CVLAN=555-Username=aaa; User passed 802.1X authentication and came online. |
|
Impact |
An 802.1X user passes authentication and comes online successfully. |
|
Cause |
This message is generated when a user passes 802.1X authentication successfully. |
|
Recommended action |
No action is required. |
DOT1X_LOGOFF
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-SVLAN=[STRING]-CVLAN=[STRING]-Username=[STRING]; 802.1X user was logged off. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: SVLAN ID. $4: CVLAN ID. $5: Username. |
|
Severity level |
6 (Informational) |
|
Example |
DOT1X/6/DOT1X_LOGOFF:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-SVLAN=444-CVLAN=555-Username=aaa; 802.1X user was logged off. |
|
Impact |
The 802.1X user goes offline. |
|
Cause |
This message is generated when an 802.1X user goes offline normally, for example, the user proactively logs off . |
|
Recommended action |
No action is required. |
DOT1X_LOGOFF_ABNORMAL
|
Message text |
-IfName=[STRING]-MACAddr=[STRING]-SVLAN=[STRING]-CVLAN=[STRING]-Username=[STRING]; 802.1X user was logged off abnormally. Reason:[STRING]. |
|
Variable fields |
$1: Interface type and number. $2: MAC address. $3: SVLAN ID. $4: CVLAN ID. $5: Username. $6: Reason for the 802.1X user abnormal logoff. Values include: ¡ Port status error. ¡ Reauthentication failure. ¡ Deauthorization by the device. ¡ The port was administratively down. ¡ Account password error. ¡ Online handshake failure. ¡ Session timeout. ¡ Server request. ¡ Real-time accounting failure. ¡ Default error. ¡ Port error. |
|
Severity level |
6 (Informational) |
|
Example |
DOT1X/6/DOT1X_LOGOFF_ABNORMAL:-IfName=GigabitEthernet1/0/4-MACAddr=0010-8400-22b9-SVLAN=444-CVLAN=555-Username=aaa; 802.1X user was logged off abnormally. Reason: Supplicant logoff. |
|
Impact |
The 802.1X user goes offline. |
|
Cause |
This message is generated when an 802.1X user goes offline abnormally. |
|
Recommended action |
1. Verify that the 802.1X authentication settings are correct. 2. Locate the abnormal logoff reason and resolve the issue according to the reason. If the configuration of the device or authentication server is incorrect, promptly modify the configuration of the device or server. 3. If the issue persists, collect alarm information, log information, and configuration data, and then contact Technical Support for help. |
DOT1X_MAX_USER_THRESHOLD
|
Message text |
The percentage of online 802.1X users exceeded the max-user high alarm threshold on interface [STRING]. |
|
Variable fields |
$1: Interface type and number. |
|
Severity level |
4 (Warning) |
|
Example |
DOT1X/4/DOT1X_MAX_USER_THRESHOLD: The percentage of online 802.1X users exceeded the max-user high alarm threshold on interface GigabitEthernet1/0/1. |
|
Impact |
New 802.1X users cannot come online. |
|
Cause |
The percentage of current online 802.1X users to the maximum allowed number of 802.1X users on the interface reached the specified alarm threshold for the first time, or it increased to the alarm threshold from below or equal to the alarm clear threshold. |
|
Recommended action |
1. Use the display dot1x interface command to view the maximum number of concurrent 802.1X users on the interface. If the maximum number is too small, reconfigure this value 2. Use the display dot1x command to view the alarm threshold for the number of 802.1X users. If the alarm threshold is too low, reconfigure this value. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DSYSM messages
This section contains DSYSM messages.
INNERLINK_EXCEPTION
|
Message text |
An exception has occured on an internal link. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
DSYSM/3/INNERLINK_EXCEPTION: -MDC=1; An exception has occured on an internal link. |
|
Impact |
The device cannot correctly communicate with other devices, which affects the running of user services. |
|
Cause |
Error occurred on the MPU hardware, which resulted in an exception on an internal chip link. |
|
Recommended action |
To remove the hardware failure, contact Technical Support. |
CTRL_CHANNEL_IS_ERR
|
Message text |
The control channel status was abnormal. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
DSYSM/3/CTRL_CHANNEL_IS_ERR: -MDC=1; The control channel status was abnormal. |
|
Impact |
Modules might have hardware failures and might not operate correctly. |
|
Cause |
The control channel remains in abnormal state and the massage is generated every 10 minutes. The reason might be hardware control link errors. |
|
Recommended action |
1. Reboot or replace modules. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CTRL_CHANNEL_TO_OK
|
Message text |
The control channel status changed to normal. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
DSYSM/3/CTRL_CHANNEL_TO_OK: -MDC=1; The control channel status changed to normal. |
|
Impact |
No negative impact on the system. |
|
Cause |
The control channel state changed to normal. |
|
Recommended action |
No action is required. |
CTRL_CHANNEL_TO_ERR
|
Message text |
The control channel status changed to abnormal. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
DSYSM/3/CTRL_CHANNEL_TO_ERR: -MDC=1; The control channel status changed to abnormal. |
|
Impact |
No negative impact on the system. |
|
Cause |
The control channel state changed to abnormal, which might be caused by hardware control link errors. |
|
Recommended action |
1. Reboot or replace modules. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
EDEV messages
This section contains messages for extended-device management.
EDEV_FAILOVER_GROUP_STATE_CHANGE
|
Message text |
Status of stateful failover group [STRING] with ID [UINT32] changed to [STRING]. |
|
Variable fields |
$1: Failover group name. $2: Failover group ID. $3: Failover group state. |
|
Severity level |
5 (Notification) |
|
Example |
|
|
Impact |
No negative impact on the system. |
|
Cause |
The status of a failover group changed. |
|
Recommended action |
No action is required. |
EIGRP messages
This section contains EIGRP messages.
RID_CHANGE
|
Message text |
EIGRP [UINT32]: New elected router ID will take effect after EIGRP address family is reset. |
|
Variable fields |
$1: EIGRP process ID. |
|
Severity level |
5 (Notification) |
|
Example |
EIGRP/5/RID_CHANGE: EIGRP 1: New elected router ID will take effect after EIGRP address family is reset. |
|
Impact |
No negative impact on the system. |
|
Cause |
A change of interface IP address causes the change of router ID for the EIGRP router. You must restart the EIGRP address family to make the new router ID take effect. |
|
Recommended action |
To have the new router ID take effect, make sure restarting the EIGRP address family does not affect current services. Use the reset eigrp process command to have the new router ID take effect. |
PEER_CHANGE
|
Message text |
EIGRP [UINT32]: Neighbor [STRING] ([STRING]) is [STRING]: [STRING]. |
|
Variable fields |
$1: EIGRP process ID. $2: IP address of the neighbor router. $3: Interface that is connected to the neighbor router. $4: Neighbor state, Up or Down. $5: Reason for the EIGRP neighbor state change. For information about the neighbor state change reasons, see Table 1. |
|
Severity level |
5 (Notification) |
|
Example |
EIGRP/5/PEER_CHANGE: EIGRP 2: Neighbor 100.100.10.2 (GigabitEthernet1/0/1) is Up: New neighbor. |
|
Impact |
· If the neighbor state changes from Down to Up, no action is required. · If the neighbor state changes from Up to Down, the neighbor relationship is in initial state or disconnected. If the neighbor relationship is disconnected, service interruption might occur. |
|
Cause |
The EIGRP neighbor state changed. |
|
Recommended action |
Take an action according to the neighbor state change reason. For more information, see Table 1. |
Table 6 Neighbor state change reasons and recommended actions
|
Reason |
Remarks |
Recommended action |
|
New neighbor |
N/A |
No action is required. |
|
Interface down |
N/A |
3. Enter the view of the interface in the log message, and execute the display this command to identify whether the shutdown is configured for the interface. ¡ If the shutdown is configured for the interface, execute the undo shutdown command. ¡ If the shutdown is not configured for the interface, proceed to step 2. 4. Execute the display eigrp interface interface-type interface-number command to view the state of the interface connected to the neighbor. ¡ If the value for the State field is Up, proceed to step 3. ¡ If the value for the State field is Down, identify whether the neighbor interface state is normal. If the neighbor interface state is normal, proceed to step 3. If the neighbor interface state is abnormal, troubleshoot the neighbor interface issue. 5. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
|
Reset operation |
The reset eigrp process or reset eigrp peer command was executed. |
No action is required. |
|
Delete operation |
The process or address family was deleted. |
No action is required. |
|
Hold timer expired |
N/A |
6. Identify whether the IP address of the peer interface can be pinged. ¡ If the ping operation fails, proceed to step 3. ¡ If the ping operation succeeds, proceed to step 2. 7. Execute the display current-configuration configuration eigrp command to identify whether the hold timer configured with the eigrp timer hold command is appropriate. ¡ If it is not appropriate, configure the hold timer again. ¡ If it is appropriate, proceed to step 3. 8. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
|
Maximum retransmission times reached |
N/A |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Inconsistent K values |
N/A |
9. Obtain the EIGRP process ID from the log message, and then enter IPv4 address family view of the EIGRP process. 10. Execute the display this command to identify whether the K values are consistent between the local and neighbor devices. ¡ If they are consistent and the log message is still generated, proceed to step 3. ¡ If they are inconsistent, execute the metric weights command to configure the K value again to make sure the K values are consistent between the local and neighbor devices. Then identify whether the log message is still generated. If the log message is not generated, the processing is completed. If the log message is still generated, proceed to step 3. 11. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
|
Neighbor restart |
N/A |
12. Determine the neighbor device based on the Neighbor value in the log message. Then, repeatedly execute the display eigrp peer command on the local device to identify whether the neighbor relationship between the local and neighboring devices is flapping. ¡ If the neighbor relationship is flapping, the EIGRP process of the neighbor device is repeatedly restarted. Troubleshoot the neighbor device issue. ¡ If the neighbor relationship is in Up state, no action is required. 13. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
|
Stuck in active |
When a route in the EIGRP topology table enters the Active state and does not converge within the convergence wait timer, the EIGRP process enters the Stuck In Active (SIA) state. |
If an SIA issue occurs, a fault exists in the network, and the specific cause cannot be easily identified. As a best practice, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
|
Peer termination |
The neighbor actively terminated the neighbor relationship. |
This log message generated by the local device indicates it has received a Hello message from a neighbor device to reset the neighbor relationship. If this log message is generated multiple times, troubleshoot the neighbor device issue. |
|
Configuration changed |
N/A |
14. Obtain the EIGRP process ID from the log message, and then enter the view of the EIGRP process. 15. Execute the display this command to identify whether the configuration for the EIGRP process is as expected. ¡ If the configuration is as expected, no action is required. ¡ If the configuration is not as expected, edit or delete the corresponding configuration. |
|
Process switchover |
EIGRP process switchover occurred. |
16. In the process switchover is manually performed, no action is required. If this log message is generated without manual intervention, proceed to step 2. 17. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
|
Insufficient memory |
The memory threshold was reached. |
18. Execute the display memory-threshold command to view the value for the Current free-memory state field, which indicates the memory usage status of the system. If the value for the Current free-memory state field is Minor, Severe, or Critical, the remaining free memory is low. To resolve this issue, disable some unnecessary features. 19. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
EKDM messages
This section contains EKDM messages.
EKDM_REBOOT_PREVNT
|
Message text |
Standby MPU in slot [UINT32] rebooted abnormally [UINT32] times and was prevented from rebooting again. |
|
Variable fields |
$1: Slot number of the standby MPU on the device. $2: Number of reboot times. |
|
Severity level |
2 (Critical) |
|
Example |
DEVD/2/EKDM_REBOOT_PREVNT: -MDC=1; Standby MPU in slot 1 rebooted abnormally 4 times and was prevented from rebooting again. |
|
Impact |
The standby MPU cannot operate correctly. |
|
Cause |
The system does not start the standby MPU again after the standby MPU has exceptionally rebooted four times. |
|
Recommended action |
1. Replace the standby MPU. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ETH messages
This section contains Ethernet module messages.
ETH_VLAN_TERMINATION_FAILED
|
Message text |
The vlan-type dot1q configuration on [STRING] failed. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
ETH/4/ETH_VLAN_TERMINATION_FAILED: -MDC=1; The vlan-type dot1q configuration on GigabitEthernet1/0/1.1 failed. |
|
Impact |
No negative impact on the system. |
|
Cause |
The hardware resources might be insufficient. |
|
Recommended action |
If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
ETH_VLAN_TERMINATION_NOT_SUPPORT
|
Message text |
The vlan-type dot1q configuration on [STRING] is not supported. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
ETH/4/ETH_VLAN_TERMINATION_NOT_SUPPORT: -MDC=1; The vlan-type dot1q configuration on GigabitEthernet1/0/1.1 is not supported. |
|
Impact |
N/A |
|
Cause |
The interface does not support the vlan-type dot1q commands. |
|
Recommended action |
Identify whether the card where the interface resides supports VLAN termination. |
ETH_VMAC_INEFFECTIVE
|
Message text |
Interface [STRING] failed to add a virtual MAC: [STRING]. |
|
Variable fields |
$1: Interface name. $2: Reasons for the failure to add a virtual MAC address to the interface. |
|
Severity level |
3 (Error) |
|
Example |
ETH/3/ETH_VMAC_INEFFECTIVE: Interface GigabitEthernet1/0/1 failed to add a virtual MAC: Insufficient hardware resources. |
|
Impact |
Evaluate the impact on the system based on the actual condition. |
|
Cause |
Failed to add a virtual MAC address. |
|
Recommended action |
Identify the failure reason and then take actions based on the reason. For example, if the number of virtual MAC addresses on the interface has reached the upper limit, there might not be enough hardware resources to add new virtual MAC addresses. In this case, delete idle VRRP groups to release some hardware resources. |
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 (Notification) |
|
Example |
ETHOAM/5/ETHOAM_CONNECTION_FAIL_DOWN: The link is down on interface Ethernet1/0/1 because a remote failure occurred on peer interface. |
|
Impact |
The link goes down. |
|
Cause |
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 (Notification) |
|
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. |
|
Impact |
The Ethernet OAM connection cannot be established. |
|
Cause |
· The link goes down. · OAM is not enabled on the peer end. |
|
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 (Error) |
|
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. |
|
Impact |
The Ethernet OAM connection cannot be established. |
|
Cause |
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 (Informational) |
|
Example |
ETHOAM/6/ETHOAM_CONNECTION_SUCCEED: An OAM connection is established on interface Ethernet1/0/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
An Ethernet OAM connection is correctly 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 (Informational) |
|
Example |
ETHOAM/6/ETHOAM_DISABLE: Ethernet OAM is now disabled on interface Ethernet1/0/1. |
|
Impact |
Ethernet OAM is disabled on the interface. |
|
Cause |
Ethernet OAM is disabled on the Ethernet interface. |
|
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 (Notification) |
|
Example |
ETHOAM/5/ ETHOAM_DISCOVERY_EXIT: OAM interface Ethernet1/0/1 quit the OAM connection. |
|
Impact |
The Ethernet OAM connection cannot be established. |
|
Cause |
Ethernet OAM is disabled on the peer end. |
|
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 (Informational) |
|
Example |
ETHOAM/6/ETHOAM_ENABLE: Ethernet OAM is now enabled on interface Ethernet1/0/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
Ethernet OAM is enabled on an Ethernet interface. |
|
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 (Informational) |
|
Example |
ETHOAM/6/ ETHOAM_ENTER_LOOPBACK_CTRLLED: The local OAM entity enters remote loopback as controlled DTE on OAM interface Ethernet1/0/1. |
|
Impact |
Ethernet OAM remote loopback is enabled correctly. |
|
Cause |
Ethernet OAM remote loopback is enabled 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 (Informational) |
|
Example |
ETHOAM/6/ ETHOAM_ENTER_LOOPBACK_CTRLLING: The local OAM entity enters remote loopback as controlling DTE on OAM interface Ethernet1/0/1. |
|
Impact |
Ethernet OAM remote loopback is enabled correctly. |
|
Cause |
Ethernet OAM remote loopback is enabled on the local end. |
|
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 (Warning) |
|
Example |
ETHOAM/4/ETHOAM_LOCAL_DYING_GASP: A local Dying Gasp event occurred on interface Ethernet1/0/1. |
|
Impact |
The link goes down. |
|
Cause |
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 (Informational) |
|
Example |
ETHOAM/6/ETHOAM_LOCAL_ERROR_FRAME: An errored frame event occurred on local interface Ethernet1/0/1. |
|
Impact |
The link quality is poor. |
|
Cause |
The number of errored frames detected based on the specified detection time window crosses the detection threshold. |
|
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 (Informational) |
|
Example |
ETHOAM/6/ETHOAM_LOCAL_ERROR_FRAME_PERIOD: An errored frame period event occurred on local interface Ethernet1/0/1. |
|
Impact |
The link quality is poor. |
|
Cause |
The number of frame errors detected based on the specified frame count window crosses the detection threshold. |
|
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 (Informational) |
|
Example |
ETHOAM/6/ETHOAM_LOCAL_ERROR_FRAME_SECOND: An errored frame seconds event occurred on local interface Ethernet1/0/1. |
|
Impact |
The link quality is poor. |
|
Cause |
The number of errored frame seconds (the second in which an errored frame appears is called an errored frame second) detected based on the specified detection time window crosses the detection threshold. |
|
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 (Warning) |
|
Example |
ETHOAM/4/ETHOAM_LOCAL_LINK_FAULT: A local Link Fault event occurred on interface Ethernet1/0/1. |
|
Impact |
The link goes down |
|
Cause |
The local interface becomes faulty. |
|
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 (Warning) |
|
Example |
ETHOAM/4/ETHOAM_LOOPBACK_EXIT: OAM interface Ethernet1/0/1 quit remote loopback. |
|
Impact |
Remote loopback connection cannot be established. |
|
Cause |
· Remote loopback was disabled on the interface before the remote loopback connection was established. · The established OAM connection was torn down. |
|
Recommended action |
No action is required. |
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 (Warning) |
|
Example |
ETHOAM/4/ETHOAM_LOOPBACK_NO_RESOURCE: OAM interface Ethernet1/0/1 can’t enter remote loopback due to insufficient resources. |
|
Impact |
The remote loopback feature cannot operate correctly. |
|
Cause |
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 (Warning) |
|
Example |
ETHOAM/4/ETHOAM_LOOPBACK_NOT_SUPPORT: OAM interface Ethernet1/0/1 can't enter remote loopback because the operation is not supported. |
|
Impact |
The remote loopback feature cannot operate correctly. |
|
Cause |
The remote loopback feature is not supported on the device. |
|
Recommended action |
No action is required. |
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 (Warning) |
|
Example |
ETHOAM/4/ ETHOAM_NO_ENOUGH_RESOURCE: The configuration failed on OAM interface Ethernet1/0/1 because of insufficient resources. |
|
Impact |
Ethernet OAM cannot be configured on the interface. |
|
Cause |
Insufficient system memory 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 (Notification) |
|
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. |
|
Impact |
The Ethernet OAM connection cannot be established. |
|
Cause |
· The link goes down. · OAM is not enabled on the peer end. |
|
Recommended action |
Check the link status and the OAM status on the peer. |
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 (Informational) |
|
Example |
ETHOAM/6/ ETHOAM_QUIT_LOOPBACK_CTRLLED: The local OAM entity quit remote loopback as controlled DTE on OAM interface Ethernet1/0/1. |
|
Impact |
Remote loopback connection cannot be established. |
|
Cause |
When Loopback Control OAMPDUs receiving is enabled on the local end, OAM loopback is disabled 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 (Informational) |
|
|
Example |
ETHOAM/6/ETHOAM_QUIT_LOOPBACK_CONTROLLING: The local OAM entity quit remote loopback as controlling DTE on OAM interface Ethernet1/0/1. |
|
|
Impact |
Remote loopback connection cannot be established. |
|
|
Cause |
Enable and then disable OAM loopback on the 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 (Warning) |
|
Example |
ETHOAM/4/ETHOAM_REMOTE_CRITICAL: A remote Critical event occurred on interface Ethernet1/0/1. |
|
Impact |
The link goes down. |
|
Cause |
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 (Warning) |
|
Example |
ETHOAM/4/ETHOAM_REMOTE_DYING_GASP: A remote Dying Gasp event occurred on interface Ethernet1/0/1. |
|
Impact |
The link goes down. |
|
Cause |
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 (Informational) |
|
Example |
ETHOAM/6/ETHOAM_REMOTE_ERROR_FRAME: An errored frame event occurred on the peer interface Ethernet1/0/1. |
|
Impact |
The link quality is poor. |
|
Cause |
The number of errored frames detected based on the specified detection time window crosses the detection threshold. |
|
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 (Informational) |
|
Example |
ETHOAM/6/ETHOAM_REMOTE_ERROR_FRAME_PERIOD: An errored frame period event occurred on the peer interface Ethernet1/0/1. |
|
Impact |
The link quality is poor. |
|
Cause |
The number of frame errors detected based on the specified frame count window crosses the detection threshold. |
|
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 (Informational) |
|
|
Example |
ETHOAM/6/ETHOAM_REMOTE_ERROR_FRAME_SECOND: An errored frame seconds event occurred on the peer interface Ethernet1/0/1. |
|
|
Impact |
The link quality is poor. |
|
|
Cause |
The number of errored frame seconds (the second in which an errored frame appears is called an errored frame second) detected based on the specified detection time window crosses the detection threshold. |
|
|
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 (Informational) |
|
|
Example |
ETHOAM/6/ETHOAM_REMOTE_ERROR_SYMBOL: An errored symbol event occurred on the peer interface Ethernet1/0/1. |
|
|
Impact |
The link quality is poor. |
|
|
Cause |
The number of errored symbols detected based on the symbol count detection window crosses the detection threshold. |
|
|
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 (Notification) |
|
Example |
ETHOAM/5/ ETHOAM_REMOTE_EXIT: OAM interface Ethernet1/0/1 quit OAM connection because Ethernet OAM is disabled on the peer interface. |
|
Impact |
Ethernet OAM connection cannot be established. |
|
Cause |
Ethernet OAM is 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 (Notification) |
|
Example |
ETHOAM/5/ ETHOAM_REMOTE_FAILURE_RECOVER: Peer interface Ethernet1/0/1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
The link fault is cleared from the peer interface. |
|
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 (Warning) |
|
Example |
ETHOAM/4/ETHOAM_REMOTE_LINK_FAULT: A remote Link Fault event occurred on interface Ethernet1/0/1. |
|
Impact |
The link goes down. |
|
Cause |
A remote interface failure occurred. |
|
Recommended action |
Reconnect the Rx end of the fiber on the remote interface. |
EVPN messages
This section contains EVPN messages.
FDB/3/EVPN_MACMOVE_REPORT_SUPPRESS
|
Message text |
Reporting of the local MAC address [STRING] in VSI index [UNIT32] is suppressed. |
|
Variable fields |
$1: MAC address $2: VSI index. |
|
Severity level |
6 (Informational) |
|
Example |
FDB/6/EVPN_MACMOVE_REPORT_SUPPRESS: Reporting of the local MAC address 0001-0001-0001 in VSI index 0 is suppressed. |
|
Impact |
Suppression of local EVPN MAC move reports for business traffic might result in the discarding of business packets. |
|
Cause |
The PE detects that the migration times of a MAC address exceeds the report suppression threshold within a detection interval, and suppresses local move reports for the MAC address. |
|
Recommended action |
1. Make sure the user devices attached to the PE use unique MAC addresses. 2. If MAC address migrations are unavoidable, execute the evpn mac-move local-suppression command to set the report suppression threshold to 100 or higher. 3. If this message persists, execute the evpn mac-move local-suppression check-interval 0 command to disable suppression of local EVPN MAC move reports. |
FDB/3/EVPN_MACMOVE_LOG_SUPPRESS
|
Message text |
The remaining EVPN_MACMOVE_REPORT_SUPPRESS logs will not be printed because the number of logs exceeds 100 within 3 minutes. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
FDB/6/EVPN_MACMOVE_REPORT_SUPPRESS: Reporting of the local MAC address 0001-0001-0001 in VSI index 0 is suppressed. FDB/6/EVPN_MACMOVE_REPORT_SUPPRESS: Reporting of the local MAC address 0001-0001-0002 in VSI index 0 is suppressed. ... FDB/6/EVPN_MACMOVE_LOG_SUPPRESS: The remaining EVPN_MACMOVE_REPORT_SUPPRESS logs will not be printed because the number of logs exceeds 100 within 3 minutes. |
|
Impact |
None. |
|
Cause |
A large number of MAC address migrations occur within a short period in the EVPN network, which triggers suppression of local EVPN MAC move reports. |
|
Recommended action |
If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support. |
FDB messages
This section contains FDB messages.
MAC_REACH_LIMIT
|
Message text |
Pattern 1: The number of mac address received in interface [STRING] reaches the upper limit. Pattern 2: The number of mac address received in VLAN [INT32] reaches the upper limit. |
|
Variable fields |
Pattern 1: $1: Interface name. Pattern 2: $1: VLAN ID. |
|
Severity level |
6 (Informational) |
|
Example |
FDB/6/MAC_REACH_LIMIT: -MDC=1-Slot=3; The number of mac address received in interface Ten-GigabitEthernet3/0/5 reaches the upper limit. |
|
Impact |
The number of MAC addresses has exceeded the upper limit for hardware. New MAC addresses cannot be learned. |
|
Cause |
The number of MAC addresses learned by an interface or VLAN has reached the upper limit. |
|
Recommended action |
1. Verify that the number of configured MAC addresses does not exceed the upper limit for hardware. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
FIB messages
This section contains FIB messages.
FIB_BOARDMSG_CONGEST
|
Message text |
· Text 1: The FIB message on the board is congested: SlotID=[UINT32]. · Text 2: The FIB message on the board is congested: Chassis=[UINT32], SlotID=[UINT32]. |
|
Variable fields |
In text 1: $1: Slot number. In text 2: $1: Chassis number. $2: Slot number. |
|
Severity level |
4 |
|
Example |
· Text 1: FIB/4/FIB_BOARDMSG_CONGEST: The FIB message on the board is congested: SlotID=2. · Text 2: FIB/4/FIB_BOARDMSG_CONGEST: The FIB message on the board is congested: Chassis=1, SlotID=2. |
|
Explanation |
Packet forwarding congestion occurred on the current card. |
|
Recommended action |
Check whether a packet attack exists. |
FIB_BOARDMSG_CONGESTRESUME
|
Message text |
· Text 1: The FIB message congestion is resolved: SlotID=[UINT32]. · Text 2: The FIB message congestion is resolved: Chassis=[UINT32], SlotID=[UINT32]. |
|
Variable fields |
In text 1: $1: Slot number. In text 2: $1: Chassis number. $2: Slot number. |
|
Severity level |
5 |
|
Example |
· Text 1: FIB/4/FIB_BOARDMSG_CONGESTRESUME: The FIB message congestion is resolved: SlotID =2. · Text 2: FIB/4/FIB_BOARDMSG_CONGESTRESUME: The FIB message congestion is resolved: Chassis=1, SlotID =2. |
|
Explanation |
Packet forwarding congestion was resolved on the current card. |
|
Recommended action |
No action is required. |
FIB_FILE
|
Message text |
Failed to save the IP forwarding table due to lack of storage resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
FIB/4/FIB_FILE: -MDC=1; Failed to save the IP forwarding table due to lack of storage resources. |
|
Explanation |
Failed to save the IP forwarding table due to lack of storage resources. |
|
Recommended action |
Delete unused files to release storage space. |
FIB_OVERLOAD_FORWARD
|
Message text |
The system is in the overload forwarding state because the FIB module is overloaded: FibOverloadModule=[STRING]. |
|
Variable fields |
$1: FIB entry type: · FIB4—The number of IPv4 FIB entries has reached 80% of the upper limit. · FIB6—The number of IPv6 FIB entries has reached 80% of the upper limit. |
|
Severity level |
4 |
|
Example |
FIB/4/FIB_OVERLOAD_FORWARD: The system is in the overload forwarding state because the FIB module is overloaded: FibOverloadModule=FIB4. |
|
Explanation |
The number of FIB entries has reached 80% of the upper limit on the device. |
|
Recommended action |
Check whether a packet attack exists. |
FIB_OVERLOAD_FORWARDRESUME
|
Message text |
The system changes from the overload forwarding state to the normal state: FibOverloadModule=[STRING]. |
|
Variable fields |
$1: FIB entry type: · FIB4—The number of IPv4 FIB entries has dropped to 50% of the upper limit. · FIB6—The number of IPv6 FIB entries has dropped to 50% of the upper limit. |
|
Severity level |
5 |
|
Example |
FIB/4/FIB_OVERLOAD_FORWARDRESUME: The system changes from the overload forwarding state to the normal state: FibOverloadModule=FIB4. |
|
Explanation |
The number of FIB entries has restored to normal state on the device. |
|
Recommended action |
No action is required. |
FIB messages
This section contains FIB messages.
FIB_BOARDMSG_CONGEST
|
Message text |
Pattern 1: The FIB message on the board is congested: SlotID=[UINT32]. Pattern 2: The FIB message on the board is congested: Chassis=[UINT32], SlotID=[UINT32]. |
|
Variable fields |
Pattern 1: $1: Slot number. Pattern 2: $1: Chassis number. $2: Slot number. |
|
Severity level |
4 (Warning) |
|
Example |
Pattern 1: FIB/4/FIB_BOARDMSG_CONGEST: The FIB message on the board is congested: SlotID=2. Pattern 2: FIB/4/FIB_BOARDMSG_CONGEST: The FIB message on the board is congested: Chassis=1, SlotID=2. |
|
Impact |
The device forwarding service cannot operate correctly. |
|
Cause |
Device hardware issue or refresh of a large number of FIB entries results in FIB message processing congestion. |
|
Recommended action |
1. Use the display ip routing-table all-routes statistics and display ipv6 routing-table all-routes statistics commands to identify whether the device experiences a large number of route changes. If rapid changes exist, proceed to step 2. If no rapid changes exist, proceed to step 3. 2. Identify the source protocol for the route change based on the search result in step 1. Then analyze the protocol change reason. If the reason cannot be located, proceed to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
FIB_BOARDMSG_CONGESTRESUME
|
Message text |
Pattern 1: The FIB message congestion is resolved: SlotID=[UINT32]. Pattern 2: The FIB message congestion is resolved: Chassis=[UINT32], SlotID=[UINT32]. |
||
|
Variable fields |
Pattern 1: $1: Slot number. Pattern 2: $1: Chassis number. $2: Slot number. |
||
|
Severity level |
5 (Notification) |
||
|
Example |
Pattern 1: FIB/5/FIB_BOARDMSG_CONGESTRESUME: The FIB message congestion is resolved: SlotID =2. Pattern 2: FIB/5/FIB_BOARDMSG_CONGESTRESUME: The FIB message congestion is resolved: Chassis=1, SlotID =2. |
||
|
Impact |
No negative impact on the system. |
|
|
|
Cause |
Packet forwarding congestion was resolved on the current card. |
||
|
Recommended action |
No action is required. |
|
|
FIB_FILE
|
Message text |
Failed to save the IP forwarding table due to lack of storage resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
FIB/4/FIB_FILE: -MDC=1; Failed to save the IP forwarding table due to lack of storage resources. |
|
Impact |
The related services might run incorrectly. |
|
Cause |
Failed to save the IP forwarding table due to lack of storage resources. |
|
Recommended action |
Delete unused files to release storage space. |
FIB_OVERLOAD_FORWARD
|
Message text |
The system is in the overload forwarding state because the FIB module is overloaded: FibOverloadModule=[STRING]. |
|
Variable fields |
$1: FIB entry type: · FIB4—The number of IPv4 FIB entries has reached 80% of the upper limit. · FIB6—The number of IPv6 FIB entries has reached 80% of the upper limit. |
|
Severity level |
4 (Warning) |
|
Example |
FIB/4/FIB_OVERLOAD_FORWARD: The system is in the overload forwarding state because the FIB module is overloaded: FibOverloadModule=FIB4. |
|
Impact |
If the number of FIB entries exceeds the threshold, the device cannot issue FIB entries and the related services might run incorrectly. |
|
Cause |
The number of FIB entries has reached 80% of the upper limit on the device. |
|
Recommended action |
1. Use the display ip routing-table all-routes statistics or display ipv6 routing-table all-routes statistics command to view the number of FIB entries issued by each protocol running on the device. 2. Check for unnecessary routes, and withdraw them (if any). |
FIB_OVERLOAD_FORWARDRESUME
|
Message text |
The system changes from the overload forwarding state to the normal state: FibOverloadModule=[STRING]. |
|
Variable fields |
$1: FIB entry type: · FIB4—The number of IPv4 FIB entries has dropped to 50% of the upper limit. · FIB6—The number of IPv6 FIB entries has dropped to 50% of the upper limit. |
|
Severity level |
5 (Notification) |
|
Example |
FIB/5/FIB_OVERLOAD_FORWARDRESUME: The system changes from the overload forwarding state to the normal state: FibOverloadModule=FIB4. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of FIB entries has restored to normal on the device. |
|
Recommended action |
No action is required. |
FILTER messages
This section contains filter messages.
FILTER_EXECUTION_ICMP
|
Message text |
RcvIfName(1023)=[STRING];Direction(1070)=[STRING];AclType(1067)=[STRING];Acl(1068)=[STRING];Protocol(1001)=[STRING];SrcIPAddr(1003)=[IPADDR];DstIPAddr(1007)=[IPADDR];IcmpType(1062)=[STRING]([UINT16]);IcmpCode(1063)=[UINT16];MatchAclCount(1069)=[UINT32];Event(1048)=[STRING]; |
|
Variable fields |
$1: Receiving interface name. $2: Direction. $3: ACL type. $4: ACL number or name. $5: Layer 4 protocol name. $6: Source IP address. $7: Destination IP address. $8: ICMP message type. $9: ICMP message code. $10: Match count. $11: Event information. |
|
Severity level |
6 (Informational) |
|
Example |
FILTER/6/FILTER_EXECUTION_ICMP: RcvIfName(1023)=GigabitEthernet2/0/2;Direction(1070)=inbound;AclType(1067)=ACL;Acl(1068)=3000;Protocol(1001)=ICMP;SrcIPAddr(1003)=100.1.1.1;DstIPAddr(1007)=200.1.1.1;IcmpType(1062)=ECHO(8);IcmpCode(1063)=0;MatchAclCount(1069)=1000;Event(1048)=Permit; |
|
Impact |
No negative impact on the system. |
|
Cause |
ICMP packets matched a packet filter. This message is sent when the first ICMP packet of a flow matches the packet filter, and subsequently it will be sent for the flow at the interval configured by using the acl logging interval command. |
|
Recommended action |
No action is required. |
FILTER_EXECUTION_ICMPV6
|
Message text |
RcvIfName(1023)=[STRING];Direction(1070)=[STRING];AclType(1067)=[STRING];Acl(1068)=[STRING];Protocol(1001)=[STRING];SrcIPv6Addr(1036)=[IPADDR];DstIPv6Addr(1037)=[IPADDR];Icmpv6Type(1064)=[STRING]([UINT16]);Icmpv6Code(1065)=[UINT16];MatchAclCount(1069)=[UINT32];Event(1048)=[STRING]; |
|
Variable fields |
$1: Receiving interface name. $2: Direction. $3: ACL type. $4: ACL number or name. $5: Layer 4 protocol name. $6: Source IPv6 address. $7: Destination IPv6 address. $8: ICMPv6 message type. $9: ICMPv6 message code. $10: Match count. $11: Event information. |
|
Severity level |
6 (Informational) |
|
Example |
FILTER/6/FILTER_EXECUTION_ICMPV6: RcvIfName(1023)=GigabitEthernet2/0/2;Direction(1070)=inbound;AclType(1067)=ACL6;Acl(1068)=3000;Protocol(1001)=IPv6-ICMP;SrcIPv6Addr(1036)=2001::1;DstIPv6Addr(1037)=3001::1;Icmpv6Type(1064)=ECHO_REQUEST(128);Icmpv6Code(1065)=0;MatchAclCount(1069)=1000;Event(1048)=Permit; |
|
Impact |
No negative impact on the system. |
|
Cause |
ICMPv6 packets matched a packet filter. This message is sent when the first ICMPv6 packet of a flow matches the packet filter, and subsequently it will be sent for the flow at the interval configured by using the acl logging interval command. |
|
Recommended action |
No action is required. |
FILTER_IPV4_EXECUTION
|
Message text |
RcvIfName(1023)=[STRING];Direction(1070)=[STRING];AclType(1067)=[STRING];Acl(1068)=[STRING];Protocol(1001)=[STRING];SrcIPAddr(1003)=[IPADDR];SrcPort(1004)=[UINT16];DstIPAddr(1007)=[IPADDR];DstPort(1008)=[UINT16];MatchAclCount(1069)=[UINT32];Event(1048)=[STRING]; |
|
Variable fields |
$1: Receiving interface name. $2: Direction. $3: ACL type. $4: ACL number or name. $5: Layer 4 protocol name. $6: Source IP address. $7: Source port. $8: Destination IP address. $9: Destination port number. $10: Match count. $11: Event information. |
|
Severity level |
6 (Informational) |
|
Example |
FILTER/6/FILTER_IPV4_EXECUTION: RcvIfName(1023)=GigabitEthernet2/0/2;Direction(1070)=inbound;AclType(1067)=ACL;Acl(1068)=3000;Protocol(1001)=TCP;SrcIPAddr(1003)=100.1.1.1;SrcPort(1004)=1025;DstIPAddr(1007)=200.1.1.1;DstPort(1008)=1026;MatchAclCount(1069)=1000;Event(1048)=Permit; |
|
Impact |
No negative impact on the system. |
|
Cause |
Packets other than ICMP packets matched a packet filter. This message is sent when the first packet of a flow matches the packet filter, and subsequently it will be sent for the flow at the interval configured by using the acl logging interval command. |
|
Recommended action |
No action is required. |
FILTER_IPV6_EXECUTION
|
Message text |
RcvIfName(1023)=[STRING];Direction(1070)=[STRING];AclType(1067)=[STRING];Acl(1068)=[STRING];Protocol(1001)=[STRING];SrcIPv6Addr(1036)=[IPADDR];SrcPort(1004)=[UINT16];DstIPv6Addr(1037)=[IPADDR];DstPort(1008)=[UINT16];MatchAclCount(1069)=[UINT32];Event(1048)=[STRING]; |
|
Variable fields |
$1: Receiving interface name. $2: Direction. $3: ACL type. $4: ACL number or name. $5: Layer 4 protocol name. $6: Source IPv6 address. $7: Source port number. $8: Destination IPv6 address. $9: Destination port number. $10: Match count. $11: Event information. |
|
Severity level |
6 (Informational) |
|
Example |
FILTER/6/FILTER_IPV6_EXECUTION: RcvIfName(1023)=GigabitEthernet2/0/2;Direction(1070)=inbound;AclType(1067)=ACL;Acl(1068)=3000;Protocol(1001)=TCP;SrcIPv6Addr(1036)=2001::1;SrcPort(1004)=1025;DstIPv6Addr(1037)=3001::1;DstPort(1008)=1026;MatchAclCount(1069)=1000;Event(1048)=Permit; |
|
Impact |
No negative impact on the system. |
|
Cause |
Packets other than ICMPv6 packets matched a packet filter. This message is sent when the first packet of a flow matches the packet filter, and subsequently it will be sent for the flow at the interval configured by using the acl logging interval command. |
|
Recommended action |
No action is required. |
FTP messages
This section contains File Transfer Protocol messages.
FTP_ACL_DENY
|
Message text |
The FTP Connection [IPADDR]([STRING]) request was denied according to ACL rules. |
|
Variable fields |
$1: IP address of the FTP client. $2: VPN instance to which the IP address of the FTP client belongs. |
|
Severity level |
5 (Notification) |
|
Example |
FTP/5/FTP_ACL_DENY: The FTP Connection 1.2.3.4(vpn1) request was denied according to ACL rules. |
|
Impact |
The system might be attacked. |
|
Cause |
The ACL for controlling FTP access denied the access request of an FTP client. |
|
Recommended action |
Contact Technical Support to verify that the FTP connection matches the related ACL rules. |
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 |
|
|
Impact |
The FTP user cannot access the system correctly. |
|
Cause |
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. To set a greater limit, execute the aaa session-limit command. If the limit is proper, no action is required. |
gRPC messages
This section contains gRPC messages.
GRPC_DIALIN_CLI
|
Message text |
Processed a CLI operation request from user [STRING] at [STRING]: Session ID=[INT32], Result=[STRING], Error code=[STRING], Used time=[STRING]. |
|
Variable fields |
$1: Username of a user. $2: IPv4 or IPv6 address of a gRPC client. $3: gRPC session ID. $4: RPC operation result: ¡ Succeeded. ¡ Failed. $5: Error code. This field displays OK if the operation succeeded. $6: Time used, in seconds. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_DIALIN_CLI: Processed a CLI operation request from user test at ipv4:192.168.100.20:50051: Session ID=1, Result=Succeeded, Error code=OK, Used time=0.02s. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device processed a CLI operation requested by a gRPC client. |
|
Recommended action |
· If the operation succeeded, no action is required. · If the operation failed, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
GRPC_DIALIN_GET
|
Message text |
Processed a GET operation request from user [STRING] at [STRING]: Session ID=[INT32], Path=[STRING]/[STRING], Result=[STRING], Used time=[STRING]. |
|
Variable fields |
$1: Username of a user. $2: IPv4 or IPv6 address of a gRPC client. $3: gRPC session ID. $4: Module name in an Xpath path. $5: Table name in the Xpath path. $6: RPC operation result: ¡ Succeeded. ¡ Failed. $7: Time used, in seconds. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_DIALIN_GET: Processed a GET operation request from user test at ipv6:[11::86]: 50051: Session ID=1, Path=ACL/ACLBase, Result=Succeeded, Used time=0.02s. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device processed a Get operation requested by a gRPC client. |
|
Recommended action |
No action is required. |
GRPC_DIALOUT_CONNECT
|
Message text |
Connection established to a collector: Collector IP=[STRING], Port=[STRING], VPN instance=[STRING], Destination group=[STRING], Subscription=[STRING]. |
|
Variable fields |
$1: IPv4 or IPv6 address of a collector. $2: Listening port of the collector. $3: VPN instance to which the collector belongs. This field displays N/A if the collector belongs to the public network. $4: Destination group to which the collector belongs. $5: Subscription for which the destination group is specified. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_DIALOUT_CONNECT: Connection established to a collector: Collector IP=11::86, Port=50050, VPN instance=N/A, Destination group=D, Subscription=A. |
|
Impact |
No negative impact on the system. |
|
Cause |
In dial-out mode, the device initiated a gRPC connection to the collector. |
|
Recommended action |
No action is required. |
GRPC_DIALOUT_DISCONNECT
|
Message text |
Device disconnected from a collector: Collector IP=[STRING], Port=[STRING], VPN instance=[STRING], Destination group=[STRING], Subscription=[STRING]. |
|
Variable fields |
$1: IPv4 or IPv6 address of a collector. $2: Listening port of the collector. $3: VPN instance to which the collector belongs. This field displays N/A if the collector belongs to the public network. $4: Destination group to which the collector belongs. $5: Subscription for which the destination group is specified. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_DIALOUT_DISCONNECT: Device disconnected from a collector: Collector IP=11::86, Port=50050, VPN instance=N/A, Destination group=D, Subscription=A. |
|
Impact |
No negative impact on the system. |
|
Cause |
The gRPC connection between the device and the collector in dial-out mode was disconnected. |
|
Recommended action |
If the gRPC connection is disconnected abnormally, check the network connection. |
GRPC_DIALOUT_EVENT
|
Message text |
Pushed event-triggered data to a collector: Collector IP=[STRING], Port=[STRING], VPN instance=[STRING], Source interface=[STRING], Sensor path=[STRING]. |
|
Variable fields |
$1: IPv4 or IPv6 address of a collector in a destination group. $2: Listening port of the collector. $3: VPN instance to which the collector belongs. This field displays N/A if the collector belongs to the public network. $4: Source interface for packets sent to the collector. $5: Name of a sensor path. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_DIALOUT_EVENT: Pushed event-triggered data to a collector: Collector IP=192.168.100.20, Port=50050, VPN instance=N/A, Source interface=loopback0, Sensor path=ifmgr/interfaceevent. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device pushed data collected by event-triggered sampling to a collector. |
|
Recommended action |
No action is required. |
GRPC_DIALOUT_SAMPLE
|
Message text |
Pushed periodic data to a collector: Collector IP=[STRING], Port=[STRING], VPN instance=[STRING], Source interface=[STRING], Sensor path=[STRING]. |
|
Variable fields |
$1: IPv4 or IPv6 address of a collector in a destination group. $2: Listening port of the collector. $3: VPN instance to which the collector belongs. This field displays N/A if the collector belongs to the public network. $4: Source interface for packets sent to the collector. $5: Name of a sensor path. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_DIALOUT_SAMPLE: Pushed periodic data to a collector: Collector IP=11::86, Port=50050, VPN instance=N/A, Source interface=loopback0, Sensor path=acl/aclbase. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device pushed data collected by periodic sampling to a gRPC client. |
|
Recommended action |
No action is required. |
GRPC_ENABLE_WITHOUT_TLS
|
Message text |
PKI domain [STRING] isn't associated with a valid local certificate. The gRPC process will start without the PKI domain. |
|
Variable fields |
$1: PKI domain name. |
|
Severity level |
4 (Warning) |
|
Example |
GRPC/4/GRPC_ENABLE_WITHOUT_TLS: PKI domain xxx isn't associated with a valid local certificate. The gRPC process will start without the PKI domain. |
|
Impact |
Security risks exist when gRPC connections are unencrypted. |
|
Cause |
The specified PKI domain was not associated with a valid local certificate, gRPC could not use the PKI domain to establish a secure connection to the collector. The connection between the device and collector would not provide data encryption service. |
|
Recommended action |
· No action is required. The device and collector still establish an unencrypted gRPC connection. · To encrypt gRPC connections, configure a PKI domain and make sure the domain contains complete certificate and key settings. Then, execute the undo grpc enable, grpc pki domain, and grpc enable commands in sequence to have the PKI domain take effect. |
GRPC_GNMI_CAPABILITY
|
Message text |
Processed a gNMI Capabilities operation request from user [STRING] at [STRING]: Session ID=[INT32], Result=[STRING], Used time=[STRING]. |
|
Variable fields |
$1: Username of a user. $2: IPv4 or IPv6 address of a gRPC client. $3: gRPC session ID. $4: RPC operation result: ¡ Succeeded. ¡ Failed. $5: Time used, in seconds. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_GNMI_CAPABILITY: Processed a gNMI Capabilities operation request from user test at ipv4:192.168.100.20:50051: Session ID=1, Result=Succeeded, Used time=1.01s. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device processed a gNMI Capabilities operation requested by a gRPC client. |
|
Recommended action |
No action is required. |
GRPC_GNMI_GET
|
Message text |
Processed a gNMI Get operation request from user [STRING] at [STRING]: Session ID=[INT32], Data type=[STRING], Encoding=[STRING], Prefix=[STRING], Path=[STRING], Result=[STRING], Error code=[STRING], Used time=[STRING]. |
|
Variable fields |
$1: Username of a user. $2: IPv4 or IPv6 address of a gRPC client. $3: gRPC session ID. $4: Data type: ¡ ALL—All types of data. ¡ CONFIG—Read-write data ¡ STATE—Read-only data. $5: Encoding format: ¡ JSON. ¡ BYTES. ¡ PROTO. ¡ ASCII. ¡ JSON_IETF. $6: Prefix for an Xpath path, which represents the name of a module. For example, ifmgr indicates the interface management module. This field might not be displayed if the operation fails. $7: Xpath path, which identifies a node in a data structure. This field might not be displayed if the operation fails. $8: RPC operation result: ¡ Succeeded. ¡ Failed. $9: Error code. This field displays OK if the operation succeeded. $10: Time used, in seconds. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_GNMI_GET: Processed a gNMI Get operation request from user test at ipv4:192.168.100.20: 50051: Session ID=1, Data type=CONFIG, Encoding=JSON, Prefix=ifmgr, Path=interfaceevent, Result=Succeeded, Error code=OK, Used time=1.25s. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device processed a gNMI Get operation requested by a gRPC client. |
|
Recommended action |
· If the operation succeeded, no action is required. · If the operation failed, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
GRPC_GNMI_SET
|
Message text |
Processed a gNMI Set operation request from user [STRING] at [STRING]: Session ID=[INT32], Operation=[STRING], Result=[STRING], Error code=[STRING], Used time=[STRING]. |
|
Variable fields |
$1: Username of a user. $2: IPv4 or IPv6 address of a gRPC client. $3: gRPC session ID. $4: Single operation or operation list. Each operation includes the type of the operation, Xpath expression, and index of a table or row. If the operation fails, this field might not be correctly displayed. Operation types include the following: ¡ delete—Deletes the table or row. ¡ update—Edit the table or row. ¡ replace—Replace the table or row. $5: RPC operation result: ¡ Succeeded. ¡ Failed. $6: Error code. This field displays OK if the operation succeeded. $7: Time used, in seconds. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_GNMI_SET: Processed a gNMI Set operation request from user test at ipv6:[11::86]: 50051: Session ID=1, Operation=delete, VLAN/VLANS(ID=3), Result=Succeeded, Error code=OK, Used time=3.25s. GRPC/6/GRPC_GNMI_SET: Processed a gNMI Set operation request from user test at ipv4:192.168.100.20:50051: Session ID=1, Operation=delete, Ifmgr/interfaces(IfIndex=258) Operation=delete, Ifmgr/interfaces(IfIndex=259), Result=Succeeded, Error code=OK, Used time=3.25s. GRPC/6/GRPC_GNMI_SET: Processed a gNMI Set operation request from user test at ipv4:192.168.100.20:50051: Session ID=1, Operation=update, system/logging/remote-servers/remote-server(host=1.1.1.20)/config/ Operation=update, system/logging/remote-servers/remote-server(host=1.1.1.20)/selectors/selector/, Result=Succeeded, Error code=OK, Used time=3.25s. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device processed a gNMI Set operation requested by a gRPC client. |
|
Recommended action |
· If the operation succeeded, no action is required. · If the operation failed, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
GRPC_GNMI_SUBSCRIBE
|
Message text |
Processed a gNMI Subscribe operation request from user [STRING] at [STRING]: Session ID=[INT32], Mode=[STRING], Encoding=[STRING], Prefix=[STRING], Path=[STRING], Result=[STRING], Error code=[STRING], Used time=[STRING]. |
|
Variable fields |
$1: Username of a user. $2: IPv4 or IPv6 address of a gRPC client. $3: gRPC session ID. $4: Subscription type: ¡ ONCE—The device pushes data only once. ¡ POLL—The device pushes data upon receiving a poll request. ¡ STREAM—The device periodically pushes data at an interval. $5: Encoding format: ¡ JSON. ¡ BYTES. ¡ PROTO. ¡ ASCII. ¡ JSON_IETF. $6: Prefix for an Xpath path, which represents the name of a module. For example, ifmgr indicates the interface management module. This field might not be displayed if the operation fails. $7: Xpath path, which identifies a node in a data structure. This field might not be displayed if the operation fails. $8: RPC operation result: ¡ Succeeded. ¡ Failed. $9: Error code. This field displays OK if the operation succeeded. $10: Time used, in seconds. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_GNMI_SUBSCRIBE: Processed a gNMI Subscribe operation request from user test at ipv4:192.168.100.20:50051: Session ID=1, Mode=POLL, Encoding=JSON, Prefix=ifmgr, Path=interfaceevent, Result=Succeeded, Error code=OK, Used time=1.01s. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device processed a gNMI Subscribe operation requested by a gRPC client. |
|
Recommended action |
· If the operation succeeded, no action is required. · If the operation failed, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
GRPC_LOGIN
|
Message text |
[STRING] logged in from [STRING], session id [INT32]. |
|
Variable fields |
$1: Username. $2: Client address, including the IP version, IP address, and port number. $3: Session ID. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_LOGIN: user logged in from ipv4:192.168.56.99:41996, session id 1. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 address, including IP version, IP address, and port number. $3: Login failure reason. The value might be Number of the gRPC sessions reached the limit. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_LOGIN_FAILED: admin1 from ipv4:192.168.70.10:53254 login failed. |
|
Impact |
If the number of gRPC sessions has reached the upper limit, a new user (gRPC client) cannot log in. |
|
Cause |
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 (Informational) |
|
Example |
GRPC/6/GRPC_LOGOUT: user logged out, Session id 1. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
GRPC/4/GRPC_SERVER_FAILED: Failed to enable gRPC server. |
|
Impact |
The gRPC service is unavailable. |
|
Cause |
The default listening port for the gRPC service is 50051. If this port has already been used by another service, the gRPC service will fail to start. |
|
Recommended action |
1. Use the grpc port command to edit the port number of the gRPC service. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
GRPC_SUBSCRIBE_EVENT_FAILED
|
Message text |
Failed to subscribe event [STRING]. |
|
Variable fields |
$1: Event name. |
|
Severity level |
4 (Warning) |
|
Example |
GRPC/4/GRPC_SUBSCRIBE_EVENT_FAILED: Failed to subscribe event syslog. |
|
Impact |
The system cannot normally push subscribed events. |
|
Cause |
A possible cause might be that the service process corresponding to the subscription information is not started. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
GRPC_RECEIVE_SUBSCRIPTION
|
Message text |
Received a subscription of module [STRING]. |
|
Variable fields |
$1: Module name. |
|
Severity level |
6 (Informational) |
|
Example |
GRPC/6/GRPC_RECEIVE_SUBSCRIPTION: Received a subscription of module syslog. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device received a subscription request for a module. |
|
Recommended action |
No action is required. |
HA messages
This section contains HA messages.
HA_BATCHBACKUP_FINISHED
|
Message text |
Batch backup of standby board in [STRING] has finished. |
|
Variable fields |
$1: Slot location when a slot supports only one CPU. CPU location when a slot supports multiple CPUs. |
|
Severity level |
5 (Notification) |
|
Example |
HA/5/HA_BATCHBACKUP_FINISHED: Batch backup of standby board in slot 1 CPU 0 has finished. |
|
Impact |
No negative impact on the system. |
|
Cause |
Batch backup from the active MPU to the standby MPU has finished. |
|
Recommended action |
No action is required. |
HA_BATCHBACKUP_STARTED
|
Message text |
Batch backup of standby board in [STRING] started. |
|
Variable fields |
$1: Slot location when a slot supports only one CPU. CPU location when a slot supports multiple CPUs. |
|
Severity level |
5 (Notification) |
|
Example |
HA/5/HA_BATCHBACKUP_STARTED: Batch backup of standby board in slot 1 CPU 0 started. |
|
Impact |
No negative impact on the system. |
|
Cause |
Batch backup from the active MPU to the standby MPU has started. |
|
Recommended action |
No action is required. |
HA_STANDBY_NOT_READY
|
Message text |
Standby board in [STRING] is not ready, reboot ... |
|
Variable fields |
$1: Slot location when a slot supports only one CPU. CPU location when a slot supports multiple CPUs. |
|
Severity level |
4 (Warning) |
|
Example |
HA/4/HA_STANDBY_NOT_READY: Standby board in slot 1 CPU 0 is not ready, reboot ... |
|
Impact |
An active/standby MPU switchover cannot be performed. |
|
Cause |
The standby MPU is starting up or has failed. |
|
Recommended action |
· Execute the display device command to identify the state of cards. ¡ If the State field displays Master or Standby, the card is in normal state. If the State field displays Normal, the card is starting up. If the State field displays other values, troubleshoot the card issues or contact Technical Support. · Execute the display system stable state command to identify the system state. If the System state field displays a value other than Stable, do not perform an ISSU or active/standby MPU switchover. |
HA_STANDBY_TO_MASTER
|
Message text |
Standby board in [STRING] changed to master. |
|
Variable fields |
$1: Slot location when a slot supports only one CPU. CPU location when a slot supports multiple CPUs. |
|
Severity level |
5 (Notification) |
|
Example |
HA/4/HA_STANDBY_TO_MASTER: Standby board in slot 1 CPU 0 changed to master. |
|
Impact |
No negative impact on the system. |
|
Cause |
An active and standby MPU switchover occurs. The standby MPU changed to active. |
|
Recommended action |
No action is required. |
HQOS messages
This section contains HQoS messages.
HQOS_DP_SET_FAIL
|
Message text |
Failed to set drop profile [STRING] globally. |
|
Variable fields |
$1: Drop profile name. |
|
Severity level |
4 (Warning) |
|
Example |
HQOS/4/HQOS_DP_SET_FAIL: Failed to set drop profile b globally. |
|
Impact |
The drop profile does not take effect. |
|
Cause |
The system failed to perform one of the following actions: · Apply a drop profile globally. · Modify a drop profile applied globally. |
|
Recommended action |
1. Examine the drop profile, and make sure it is supported and has no conflicted contents. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
HQOS_FP_SET_FAIL
|
Message text |
Failed to set [STRING] in forwarding profile [STRING] globally. |
|
Variable fields |
$1: Policy type: · gts. · bandwidth. · queue. · drop profile. $2: Forwarding profile name. |
|
Severity level |
4 (Warning) |
|
Example |
HQOS/4/HQOS_FP_SET_FAIL: Failed to set gts in forwarding profile b globally. |
|
Impact |
The forwarding profile does not take effect. |
|
Cause |
The system failed to perform one of the following actions: · Apply a forwarding profile globally. · Modify a forwarding profile applied globally. |
|
Recommended action |
1. Examine the forwarding profile, and make sure it is supported and has no conflicted contents. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
HQOS_POLICY_APPLY_FAIL
|
Message text |
Failed to apply some forwarding classes or forwarding groups in scheduler policy [STRING] to the [STRING] direction of interface [STRING]. |
|
Variable fields |
$1: Scheduler policy name. $2: Policy direction: inbound or outbound. $3: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
HQOS/4/HQOS_POLICY_APPLY_FAIL: Failed to apply some forwarding classes or forwarding groups in scheduler policy b to the inbound direction of interface Ethernet3/1/2. |
|
Impact |
The applied scheduler profile does not take effect. |
|
Cause |
The system failed to perform one of the following actions: · Apply a scheduler policy to a specific direction of an interface. · Modify a scheduler policy applied to a specific direction of an interface. |
|
Recommended action |
Use the display qos scheduler-policy diagnosis interface command to identify the nodes that failed to be applied and the failure causes, and modify the running configuration. If a forwarding profile has failed to be issued completely, the following possible causes are displayed: · Insufficient resources—Insufficient hardware resources. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. · Conflicting match rule—Modify rule contents. · Not support—Unsupported configuration exists. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. · GTS Failed—The GTS parameters failed to be issued to a forwarding class or forwarding group. Modify GTS parameters. · WRED Failed—The WRED parameters failed to be issued to a forwarding class or forwarding group. Modify WRED parameters. · Queue Failed—The queuing algorithm failed to be issued to a forwarding class or forwarding group. Modify the queuing algorithm. · Bandwidth Failed—The minimum guaranteed bandwidth failed to be issued to a forwarding class or forwarding group. Modify the minimum guaranteed bandwidth. |
HQOS_POLICY_RECOVER_FAIL
|
Message text |
Failed to recover scheduler policy [STRING] to the [STRING] direction of interface [STRING] due to [STRING]. |
|
Variable fields |
$1: Scheduler policy name. $2: Policy direction: inbound or outbound. $3: Interface name. $4: Failure cause: ¡ conflicting with QoS configuration ¡ conflicting with exclusive bandwidth configuration ¡ conflicting with channel bandwidth configuration ¡ conflicting with network slicing configuration ¡ lack of hardware resources ¡ not support |
|
Severity level |
4 (Warning) |
|
Example |
HQOS/4/HQOS_POLICY_RECOVER_FAIL: Failed to recover scheduler policy b to the outbound direction of interface Ethernet3/1/2 due to conflicting with QoS configuration. |
|
Impact |
The applied scheduler profile does not take effect. |
|
Cause |
The system failed to recover an applied scheduler policy after the card or device rebooted. |
|
Recommended action |
Take an action according to the failure cause: · conflicting with QoS configuration—Delete the QoS configuration. · conflicting with exclusive bandwidth configuration—Delete the exclusive bandwidth configuration. · conflicting with channel bandwidth configuration—Delete the interface channelization configuration. · conflicting with network slicing configuration—Delete the network slicing configuration. · lack of hardware resources—Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. · not support—Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IBC
This section contains IBC messages.
CTRL_PATH_FAULT
|
Message text |
A link fault occurred on a control path. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
IBC/3/CTRL_PATH_FAULT: -MDC=1; A link fault occurred on a control path. |
|
Impact |
The system might get stuck. |
|
Cause |
A link fault occurred on a control path of the device. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help |
IF
This section contains interface management messages.
IF_BDG_FWD_NOTSPT
|
Message text |
Pattern 1: Interfaces of this board don’t support the bridge-forwarding enable command. Pattern 2: Some member ports of [STRING] don't support the bridge-forwarding enable command. |
|
Variable fields |
Pattern 1: N/A Pattern 2: $1: Layer 3 aggregation group name. |
|
Severity level |
3 (Error) |
|
Example |
Pattern 1: LIF/3/IF_BDG_FWD_NOTSPT: -MDC=1-Slot=3; Interfaces of this board don’t support the bridge-forwarding enable command. Pattern 2: LIF/3/IF_BDG_FWD_NOTSPT: -MDC=1-Slot=3; Some member ports of Route-Aggregation1 don't support the bridge-forwarding enable command. |
|
Impact |
Pattern 1: Layer 2 forwarding cannot be enabled for the Layer 3 interfaces on the card. Pattern 2: Layer 2 forwarding cannot be enabled on.the Layer 3 aggregate interfaces, because some member ports of the Layer 3 aggregation group do not support the bridge-forwarding enable command. |
|
Cause |
Pattern 1: Layer 3 Ethernet interfaces on the specified card do not support the bridge-forwarding enable command. Pattern 2: Some member ports of the Layer 3 aggregation group do not support the bridge-forwarding enable command because of the limitation of the cards where the member ports are located. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. Only |
IF_RAGG_NOTSPT
|
Message text |
Pattern 1: Cannot assign [STRING] to [STRING] that was configured with the bridge-forwarding enable command. Pattern 2: The interface can't be assigned to Route-Aggregation that was configured with the bridge-forwarding enable command. |
|
Variable fields |
$1: Interface name. $2: Layer 3 aggregate interface name. |
|
Severity level |
3 (Error) |
|
Example |
Pattern 1: LIF/3/IF_RAGG_NOTSPT: -MDC=1; Cannot assign GigabitEthernet3/1/1 to Route-Aggregation1 that was configured with the bridge-forwarding enable command. Pattern 2: LIF/3/IF_RAGG_NOTSPT: -MDC=1-Slot=3; The interface can't be assigned to Route-Aggregation when the route-aggregation different-mac-address enable command is configured. |
|
Impact |
This interface cannot be assigned to a Layer 3 aggregation group. |
|
Cause |
A Layer 3 interface that does not support the bridge-forwarding enable command cannot be assigned to a Layer 3 aggregation group enabled with Layer 2 forwarding. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INT_QINQ_NORES
|
Message text |
Not enough resources for [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
LIF/6/INT_QINQ_NORES: -MDC=1-Slot=5; Not enough resources for Route-Aggregation1.1. |
|
Impact |
QinQ termination feature became unavailable on the interface. |
|
Cause |
Failed to enable the QinQ termination feature because of insufficient hardware resources. |
|
Recommended action |
1. Use the display current-configuration | include second-dot1q command to display the current QinQ termination configuration. 2. Use the undo vlan-type dot1q vid second-dot1q command to disable QinQ termination to release resources. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MACADDR_CFG_NOTSPT
|
Message text |
This board doesn't support VE-L3VPN interfaces configured with the mac-address command. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/MACADDR_CFG_NOTSPT: -MDC=1-Slot=3; This board doesn't support VE-L3VPN interfaces configured with the mac-address command. |
|
Impact |
VE-L3VPN interfaces configured with the mac-address command cannot be configured on the card. |
|
Cause |
The card does not support VE-L3VPN interfaces configured with the mac-address command. |
|
Recommended action |
1. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MACADDR_NOTSPT_INT
|
Message text |
[STRING] can't be assigned to [STRING] configured with a MAC address. |
|
Variable fields |
$1: Interface name. If the device fails to obtain the interface name, The interface is displayed. $2: Layer 3 aggregate interface name. If the device fails to obtain the interface name, the interface number is not displayed. |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/MACADDR_NOTSPT_INT: -MDC=1-Slot=3; Ten-GigabitEthernet3/0/5 can't be assigned to Route-Aggregation100 configured with a MAC address. LIF/3/MACADDR_NOTSPT_INT: -MDC=1-Slot=3; The interface can't be assigned to Route-Aggregation configured with a MAC address. |
|
Impact |
The Layer 3 Ethernet interface cannot be assigned to a Layer 3 aggregation group configured with a MAC address. |
|
Cause |
Because of the limitation of the card where the Layer 3 Ethernet interface is located, the Layer 3 Ethernet interface cannot be assigned to the Layer 3 aggregation group configured with the mac-address command. |
|
Recommended action |
1. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MACADDR_NOTSPT_RAGG
|
Message text |
[STRING] has been configured with a MAC address and can't be assigned to [STRING]. |
|
Variable fields |
$1: Interface name. If the device fails to obtain the interface name, The interface is displayed. $2: Layer 3 aggregate interface name. If the device fails to obtain the interface name, the interface number is not displayed. |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/MACADDR_NOTSPT_RAGG: -MDC=1-Slot=3; Ten-GigabitEthernet3/0/5 has been configured with a MAC address and can't be assigned to Route-Aggregation100. LIF/3/MACADDR_NOTSPT_RAGG: -MDC=1-Slot=3; The interface has been configured with a MAC address and can't be assigned to Route-Aggregation. |
|
Impact |
The Layer 3 Ethernet interface cannot be assigned to a Layer 3 aggregation group. |
|
Cause |
A Layer 3 Ethernet interface cannot be assigned to an aggregation group if it has been assigned a MAC address by using the mac-address command. |
|
Recommended action |
1. Execute the undo mac-address command to delete the MAC address of the Layer 3 Ethernet interface before you assign it to an aggregation group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
OP_INF_NORES
|
Message text |
Operation failed because of insufficient hardware resources. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/OP_INF_NORES: -MDC=1-Slot=4; Operation failed because of insufficient hardware resources. |
|
Impact |
The interface became unavailable. |
|
Cause |
A created interface (for example, a VLAN interface) is unavailable because of insufficient hardware resources. |
|
Recommended action |
1. Use the undo command to delete the interface. 2. Use the display interface interface-type brief command to displays brief interface information. 3. Delete unnecessary interfaces to release resources and re-create the interface. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
OP_SUBINT_NORES
|
Message text |
Operation failed on [STRING] because of insufficient hardware resources. |
|
Variable fields |
$1: Interface name or VLAN number. |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/OP_SUBINT_NORES: -MDC=1-Slot=4; Operation failed on Route-Aggregation3.2 because of insufficient hardware resources. LIF/3/OP_SUBINT_NORES: -MDC=1-Slot=4; Operation failed on VLAN222 because of insufficient hardware resources. |
|
Impact |
The interface became unavailable. |
|
Cause |
A created interface (for example, a Layer 3 aggregate subinterface) or sub-VLAN is unavailable because of insufficient hardware resources. |
|
Recommended action |
1. Use the undo command to delete the interface or VLAN. 2. Use the display interface interface-type brief command to displays brief interface information. Alternatively, use the display supervlan command to display information about super VLANs and their associated sub-VLANs. 3. Delete unnecessary interfaces or sub-VLANs to release resources and re-create the interface or VLAN. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PORT_MACADDR_NOTSPT
|
Message text |
Some member ports of [STRING] don't support the mac-address command. |
|
Variable fields |
$1: Layer 3 aggregate interface name. If the device fails to obtain the interface name, the interface number is not displayed. |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/PORT_MACADDR_NOTSPT: -MDC=1-Slot=3; Some member ports of Route-Aggregation100 don't support the mac-address command. LIF/3/PORT_MACADDR_NOTSPT: -MDC=1-Slot=3; Some member ports of Route-Aggregation don't support the mac-address command. |
|
Impact |
The mac-address command cannot be executed on the Layer 3 aggregate interface. |
|
Cause |
Because of the limitation of the card where some member ports are located, the member ports on the card do not support the mac-address command. |
|
Recommended action |
1. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
RAGG_MACADDR_NOTSPT
|
Message text |
Member port of Route-Aggregation doesn't support the mac-address command. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/RAGG_MACADDR_NOTSPT: -MDC=1-Slot=3; Member port of Route-Aggregation doesn't support the mac-address command. |
|
Impact |
The mac-address command cannot be configured on a Layer 3 Ethernet interface. |
|
Cause |
The mac-address command cannot be executed on a Layer 3 Ethernet interface that is already assigned to an aggregation group. |
|
Recommended action |
1. Execute the mac-address command on the Layer 3 Ethernet interface after you remove the member ports from the Layer 3 aggregation group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
RAGGSUB_L2VPN_ CONFLICT
|
Message text |
The operation is not supported because configuration conflicts on Route-Aggregation[INT32] |
|
Variable fields |
$1: Aggregate subinterface number. |
|
Severity level |
2 (Critical) |
|
Example |
LIF/2/RAGGSUB_L2VPN_ CONFLICT: -MDC=1-Chassis=1-Slot=3; The operation is not supported because configuration conflicts on Route-Aggregation1.1. |
|
Impact |
The traffic statistics feature cannot be enabled on the Layer 3 aggregate subinterface because of the configuration conflicts on Layer 3 aggregate subinterface. |
|
Cause |
The traffic statistics feature and the L2VPN feature are mutually exclusive on the aggregate subinterface. If you configure both of the features, the traffic statistics feature does not take effect. |
|
Recommended action |
1. Use the undo traffic-statistic enable command to disable the traffic statistics feature for the Layer 3 aggregate subinterface. 2. Disable IPoE L2VPN configuration for the Layer 3 aggregate subinterface. 3. Execute the traffic-statistic enable command for the aggregate subinterface. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
RAGGSUB_NORES
|
Message text |
Operation failed because of insufficient resources on Route-Aggregation [INT32] |
|
Variable fields |
$1: Aggregate subinterface number. |
|
Severity level |
2 (Critical) |
|
Example |
LIF/2/RAGGSUB_NORES: -MDC=1-Slot=2; Operation failed because of insufficient resources on Route-Aggregation1.1. |
|
Impact |
· The traffic statistics feature cannot be enabled on the Layer 3 aggregate subinterface. · The traffic statistics feature failed to take effect on the Layer 3 aggregate subinterface after you execute the traffic-statistic enable command on the Layer 3 aggregate subinterface. |
|
Cause |
· The traffic statistics feature cannot be enabled on the Layer 3 aggregate subinterface. · System resources were not enough to enable the traffic statistics feature. |
|
Recommended action |
1. Use the undo traffic-statistic enable command to disable the traffic statistics feature for the aggregate subinterface. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
iFIT messages
This section contains in-situ Flow Information Telemetry (iFIT) messages.
IFIT_COUNTER_NORES
|
Message text |
Not enough counter resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IFIT/4/IFIT_COUNTER_NORES: Not enough counter resource. |
|
Impact |
The system cannot perform iFIT measurement on target flows that are newly learned. |
|
Cause |
Counter resources were exhausted for the system to measure new target flows by using iFIT. |
|
Recommended action |
1. Execute the display this command in iFIT view to view the iFIT instance information. 2. Execute the undo instance instance-name command to remove the iFIT instances corresponding to unused dynamic flows to release counter resources. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IFIT_FLOW_NORES
|
Message text |
Not enough Flow resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IFIT/4/IFIT_FLOW_NORES: Not enough Flow resource. |
|
Impact |
The system cannot perform iFIT measurement on target flows that are newly learned. |
|
Cause |
The amount of target flows for iFIT measurement exceeded the system upper limit, which causes resource exhaustion. The system cannot measure the newly-learned target flows by using iFIT. |
|
Recommended action |
1. Execute the display this command in iFIT view to view the iFIT instance information. 2. Execute the undo instance instance-name command to remove the iFIT instances corresponding to unused dynamic flows to decrease the number iFIT target flows in the system. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IFIT_MAPPING_NORES
|
Message text |
Not enough iFit Mapping resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IFIT/4/IFIT_MAPPING_NORES: Not enough iFit Mapping resource. |
|
Impact |
The system cannot perform iFIT measurement on target flows that are newly learned. |
|
Cause |
iFIT mapping resources were exhausted for the system to measure the newly-learned target flows by using iFIT. |
|
Recommended action |
1. Execute the display this command in iFIT view to view the iFIT instance information. 2. Execute the undo instance instance-name command to remove the iFIT instances corresponding to unused dynamic flows to release iFIT mapping resources in the system. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IFIT_ACL_NORES
|
Message text |
Not enough ACL resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IFIT/4/IFIT_ACL_NORES: Not enough ACL resource. |
|
Impact |
The system cannot perform iFIT measurement on target flows that are newly learned. |
|
Cause |
ACL resources were exhausted for the system to measure the newly-learned target flows by using iFIT. |
|
Recommended action |
1. Execute the display this command in iFIT view to view the iFIT instance information. 2. Execute the undo instance instance-name command to delete unnecessary iFIT configurations to release ACL resources. 3. Delete other unnecessary service configurations that use ACL to release ACL resources. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
IFIT/5/IFIT_GLOBAL_FAILURE: Failed to issue the ifit enable command to the driver. |
|
Impact |
iFIT cannot operate correctly. |
|
Cause |
· The system resources are insufficient, so the iFIT kernel thread fails to be started. · The hardware resources are insufficient, so the iFIT entries failed to be deployed to the driver. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support. |
IFIT_INST_ACTIVE
|
Message text |
iFIT measurement for instance [STRING] is active. |
|
Variable fields |
$1: Instance name. |
|
Severity level |
6 (Informational) |
|
Example |
IFIT/6/IFIT_INST_ACTIVE: iFIT measurement for instance A is active. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packet delay measurement or packet loss measurement is enabled. |
|
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 (Notification) |
|
Example |
IFIT/5/IFIT_INST_FAILURE: Failed to issue the configuration of flow 4097 to the driver. |
|
Impact |
The iFIT instance cannot operate correctly to perform iFIT measurement. |
|
Cause |
The hardware resources are insufficient. |
|
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 then configure the iFIT instance again. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
IFIT_INST_INACTIVE
|
Message text |
iFIT measurement for instance [STRING] is inactive. Reason: [TEXT]. |
|
Variable fields |
$1: instance name. $2: Reasons: · The bound interfaces are invalid. · The VPN instance does not exist. · VPN [STRING] does not exist. · Xconnect-group [STRING] connection [STRING] does not exist. · VSI [STRING] does not exist. |
|
Severity level |
5 (Notification) |
|
Example |
IFIT/5/IFIT_INST_INACTIVE: iFIT measurement for instance a is inactive. Reason: The bound interfaces are invalid. |
|
Impact |
The iFIT instance cannot operate correctly to perform iFIT measurement. |
|
Cause |
This message is generated due to the following reasons: · The interfaces bound to the target flow are all invalid. For example, these interfaces do not exist. · The VPN instance bound to the target flow does not exist. · The cross-connect bound to the target flow does not exist. · The VSI bound to the target flow does not exist. |
|
Recommended action |
If the bound interfaces are invalid, perform the following steps to resolve the issue: 1. Execute the display ifit flow static command to view information of the interfaces bound to the iFIT instance. 2. Execute the display interface command to verify that the interfaces bound to the iFIT instance are up. If a bound interface is not up, resolve the link issue. If the VPN, VSI, or cross-connect does not exist, perform the following steps to resolve the issue: 3. Execute the display ifit flow static command to view information about the VPN instance, VSI, and cross-connect bound to the iFIT instance. 4. If a VPN instance is bound to the iFIT instance, execute the display ip vpn-instance command to identify whether the VPN instance exists. If the VPN instance does not exist, create the VPN instance. 5. If a VSI is bound to the iFIT instance, execute the display l2vpn vsi command to identify whether the VSI exists. If the VSI does not exist, create the VSI instance. 6. If a cross-connect is bound to the iFIT instance, execute the display l2vpn xconnect-group command to identify whether the cross-connect exists. If the cross-connect does not exist, create the cross-connect instance. |
IFIT_NO_RESOURCE
|
Message text |
Failed to configure the flow [UINT] due to insufficient resources. |
|
Variable fields |
$1: Flow ID. |
|
Severity level |
5 (Notification) |
|
Example |
IFIT/5/IFIT_NO_RESOURCE: Failed to configure the flow 4097 due to insufficient resources. |
|
Impact |
The iFIT flow cannot operate correctly. |
|
Cause |
The hardware resources are insufficient. |
|
Recommended action |
1. Execute the display qos-acl resource command to identify whether the ACL resources are sufficient. If the ACL resources are insufficient, delete unnecessary ACLs, and then execute the command to configure an iFIT flow. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
IFIT_NO_SUPPORT
|
Message text |
iFIT is not supported in this slot. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
IFIT/5/IFIT_NO_SUPPORT: -slot=2; iFIT is not supported in this slot. |
|
Impact |
iFIT cannot operate correctly on the specified slot. |
|
Cause |
The hardware does not support iFIT. |
|
Recommended action |
Make sure iFIT is supported by the hardware. Replace the existing card with a card that supports iFIT, or switch the traffic to be measured by iFIT to a slot that supports iFIT. |
IFMON messages
This section contains interface alarm messages.
CRC_BIT_ERROR_RECOVERY
|
Message text |
The value of CRC error ratio dropped below the lower threshold: Interface name=[STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/CRC_BIT_ERROR_RECOVERY: -Slot=2; The value of CRC error ratio dropped below the lower threshold: Interface name=GigabitEthernet1/0/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
This log message was generated when the number of CRC bit error packets detected within a statistics collection interval dropped below the lower threshold and the alarm was cleared. |
|
Recommended action |
No action is required. |
CRC_BIT_ERROR_THRESHOLD
|
Message text |
The CRC error ratio exceeds the upper threshold: Interface name=[STRING], upper threshold=[UINT32], CRC bit error ratio value=[STRING]. |
|
Variable fields |
$1: Interface name. $2: Upper bit error rate threshold. $3: Number of CRC bit error packets detected within the latest statistics collection interval. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/CRC_BIT_ERROR_THRESHOLD: -MDC=1-Slot=2; The CRC error ratio exceeds the upper threshold: Interface name=Ten-GigabitEthernet1/0/1, upper threshold=1E-3, CRC bit error ratio value=4E-1. |
|
Impact |
If the shutdown keyword is configured when you configure the CRC packet error rate on a physical interface, the system shuts down the interface when the number of received CRC error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of received CRC error packets exceeds the upper threshold on the interface. |
|
Cause |
This log message was generated when the number of CRC bit error packets detected 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. |
CRC_ERROR_RECOVERY
|
Message text |
Number of CRC error packets recovered to normal. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/CRC_ERROR_RECOVERY: Number of CRC error packets recovered to normal. |
|
Impact |
N/A |
|
Cause |
This log message was generated when the number of CRC error packets detected within a statistics collection interval dropped below the lower threshold and the alarm was cleared. |
|
Recommended action |
No action is required. |
CRC_ERROR_THRESHOLD
|
Message text |
Number of CRC error packets exceeded the high threshold: Interface Name=[STRING], High threshold=[UINT32], Number of CRC error packets=[UINT64], Interval=[UINT32]s. |
|
Variable fields |
$1: Interface name. $2: Upper threshold for the alarm or upper bit error rate threshold. $3: Number of CRC error packets within the latest statistics collection interval. $4: Statistics collection and comparison interval for CRC error packets in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/CRC_ERROR_THRESHOLD: Number of CRC error packets exceeded the high threshold: Interface Name=HundredGigE1/0/1, High threshold=100, Number of CRC error packets=200, Interval=10s. |
|
Impact |
If the shutdown keyword is configured when you configure the CRC packet error rate on a physical interface, the system shuts down the interface when the number of received CRC error packets on the interface exceeds the upper threshold. Then, the interface stops forwarding all packets. To recover the interface, execute the undo shutdown command on the interface. If you do not specify this keyword, an upper threshold exceeding alarm is generated and the interface enters the alarm state when the number of received CRC error packets exceeds the upper threshold on the interface. |
|
Cause |
This log message was generated when the number of CRC error packets detected 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 |
1. Identify whether the upper threshold is set properly. 2. Identify whether the link environment quality is good. |
BGTRAFFIC_SEND_BEGIN
|
Message text |
Interface [STRING] began sending background traffic. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
IFMON/6/BGTRAFFIC_SEND_BEGIN: Interface GigabitEthernet1/0/1 began sending background traffic. |
|
Impact |
N/A |
|
Cause |
An interface began sending background traffic when the outgoing traffic of the interface did not reach 100 Mbps. |
|
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 (Informational) |
|
Example |
IFMON/6/BGTRAFFIC_SEND_END: Interface GigabitEthernet1/0/1 stopped sending background traffic. |
|
Impact |
N/A |
|
Cause |
An interface stopped sending background traffic when the outgoing traffic of the interface exceeded 300 Mbps. |
|
Recommended action |
No action is required. |
INPUT_BUFFER_DROP_RECOVERY
|
Message text |
The number of input buffer drop packets dropped below the lower threshold: Interface name=[STRING], upper threshold=[UINT32], lower threshold=[UINT32], number of input buffer drop packets=[UINT64], interval=[UINT32]s. |
|
Variable fields |
$1: Interface name. $2: Upper threshold for the alarm. $3: Lower threshold for the alarm. $4: Number of input packets dropped in the data buffer detected within the latest statistics collection interval. $5: Collection and comparison interval for input packets dropped in the data buffer, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/INPUT_BUFFER_DROP_RECOVERY: The number of input buffer drop packets dropped below the lower threshold: Interface name=GigabitEthernet0/0/2, upper threshold=5000, lower threshold=1000, number of input buffer drop packets=25552, interval=30s. |
|
Impact |
N/A |
|
Cause |
This log message was generated when the number of input packets dropped in the data buffer detected within a statistics collection interval dropped below the lower threshold and the alarm was cleared. |
|
Recommended action |
No action is required. |
INPUT_BUFFER_DROP_THRESHOLD
|
Message text |
The number of input buffer drop packets exceeded the upper threshold: Interface name=[STRING], upper threshold=[UINT32], lower threshold=[UINT32], number of input buffer drop packets=[UINT64], interval=[UINT32]s. |
|
Variable fields |
$1: Interface name. $2: Upper threshold for the alarm. $3: Lower threshold for the alarm. $4: Number of input packets dropped in the data buffer detected within the latest statistics collection interval. $5: Collection and comparison interval for input packets dropped in the data buffer, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/INPUT_BUFFER_DROP_THRESHOLD: The number of input buffer drop packets exceeded the upper threshold: Interface name=GigabitEthernet0/0/2, upper threshold=5000, lower threshold=1000, number of inout buffer drop packets=25552, interval=30s. |
|
Impact |
Service traffic might be dropped. |
|
Cause |
This log message was generated when the number of input packets dropped in the data buffer detected within a statistics collection interval exceeded the upper threshold. Typically, this issue occurs because the threshold is set improperly or too many packets are lost during transmission. |
|
Recommended action |
1. Identify whether the upper threshold is set properly. 2. Identify whether the link environment quality is good. 3. Decrease the packet sending rate of the peer interface. For example, use QoS to rate-limit the traffic. |
INPUT_ERROR_RECOVERY
|
Message text |
The number of input error packets dropped below the lower threshold: Interface name=[STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/INPUT_ERROR_RECOVERY: The number of input error packets dropped below the lower threshold: Interface name=GigabitEthernet1/0/1. |
|
Impact |
N/A |
|
Cause |
This log message was generated when the number of input error packets detected within a statistics collection interval dropped below the lower threshold and the alarm was cleared. |
|
Recommended action |
No action is required. |
INPUT_ERROR_THRESHOLD
|
Message text |
The number of input error packets exceeded the upper threshold: Interface name=[STRING], upper threshold=[UINT32], number of input error packets=[UINT64], interval=[UINT32] s. |
|
Variable fields |
$1: Interface name. $2: Upper threshold for the alarm or upper bit error rate threshold. $3: Number of input error packets detected within the latest statistics collection interval. $4: Collection and comparison interval for input error packets, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/INPUT_ERROR_THRESHOLD: The number of input error packets exceeded the upper threshold: Interface name=HundredGigE1/0/1, upper threshold=100, number of input error packets=200, interval=10 s. |
|
Impact |
Service traffic might be dropped. |
|
Cause |
This log message was generated when the number of input error packets detected 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 |
1. Identify whether the upper threshold is set properly. 2. Identify whether the link environment quality is good. |
OUTPUT_BUFFER_DROP_RECOVERY
|
Message text |
The number of output buffer drop packets dropped below the lower threshold: Interface name=[STRING], upper threshold=[UINT32], lower threshold=[UINT32], number of output buffer drop packets=[UINT64], interval=[UINT32]s. |
|
Variable fields |
$1: Interface name. $2: Upper threshold for the alarm. $3: Lower threshold for the alarm. $4: Number of output packets dropped in the data buffer detected within the latest statistics collection interval. $5: Collection and comparison interval for output packets dropped in the data buffer, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/OUTPUT_BUFFER_DROP_RECOVERY: The number of output buffer drop packets dropped below the lower threshold: Interface name=GigabitEthernet0/0/2, upper threshold=5000, lower threshold=1000, number of output buffer drop packets=25552, interval=30s. |
|
Impact |
N/A |
|
Cause |
This log message was generated when the number of output packets dropped in the data buffer detected within a statistics collection interval dropped below the lower threshold and the alarm was cleared. |
|
Recommended action |
No action is required. |
OUTPUT_BUFFER_DROP_THRESHOLD
|
Message text |
The number of output buffer drop packets exceeded the high threshold: Interface name=[STRING], upper threshold=[UINT32], lower threshold=1000, number of output buffer drop packets=[UINT64], Interval=[UINT32]s. |
|
Variable fields |
$1: Interface name. $2: Upper threshold for the alarm. $3: Lower threshold for the alarm. $4: Number of output packets dropped in the data buffer detected within the latest statistics collection interval. $5: Collection and comparison interval for output packets dropped in the buffer, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/OUTPUT_BUFFER_DROP_THRESHOLD: The number of output buffer drop packets exceeded the high threshold: Interface name=GigabitEthernet0/0/2, upper threshold=5000, lower threshold=1000, number of output buffer drop packets=25552, Interval=30s. |
|
Impact |
Service traffic might be dropped. |
|
Cause |
This log message was generated when the number of output packets dropped in the data buffer detected within a statistics collection interval exceeded the upper threshold. Typically, this issue occurs because the threshold is set improperly or too many packets are lost during transmission. |
|
Recommended action |
1. Identify whether the upper threshold is set properly. 2. Identify whether the link environment quality is good. 3. Decrease the packet sending rate of the peer interface. For example, use QoS to rate-limit the traffic. |
OUTPUT_ERROR_RECOVERY
|
Message text |
The number of output error packets dropped below the lower threshold: Interface name=[STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/OUTPUT_ERROR_RECOVERY: The number of output error packets dropped below the lower threshold: Interface name=GigabitEthernet1/0/1. |
|
Impact |
N/A |
|
Cause |
This log message was generated when the number of output error packets detected within a statistics collection interval dropped below the lower threshold and the alarm was cleared. |
|
Recommended action |
No action is required. |
OUTPUT_ERROR_THRESHOLD
|
Message text |
The number of output error packets exceeded the upper threshold: Interface name=[STRING], upper threshold=[UINT32], number of output error packets=[UINT64], interval=[UINT32] s. |
|
Variable fields |
$1: Interface name. $2: Upper threshold for the alarm or upper bit error rate threshold. $3: Number of output error packets detected within the latest statistics collection interval. $4: Collection and comparison interval for output error packets, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/OUTPUT_ERROR_THRESHOLD: The number of output error packets exceeded the upper threshold: Interface name=HundredGigE1/0/1, upper threshold=100, number of output error packets=200, interval=10 s. |
|
Impact |
Service traffic might be dropped. |
|
Cause |
This log message was generated when the number of output error packets detected 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 |
1. Identify whether the upper threshold set on the interface is too low. If the threshold is too low, execute the port ifmonitor output-error command to modify the threshold. 2. Identify whether the link environment quality is good. 3. Execute the display interface command to identify whether the Tx power of the transceiver module of the interface that fails is within the normal range. Identify whether the negotiation mode, clock mode, and scrambling mode (link protocol, clock, and scramble) are the same on both ends. If they are different, modify the negotiation mode configuration on both ends to make them consistent. |
SLOT_PACKETDROP_RECOVERY
|
Message text |
The number of drop packets dropped below the lower threshold: Slot=[UINT32], upper threshold=[UINT32], lower threshold=[UINT32], number of drop packets=[UINT64], interval=[UINT32]s. |
|
Variable fields |
$1: Card information. $2: Upper threshold for the alarm. $3: Lower threshold for the alarm. $4: Number of output packets dropped on a card detected within the latest statistics collection interval. $5: Collection and comparison interval for packets dropped on a card, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/SLOT_PACKETDROP_RECOVERY: The number of drop packets dropped below the lower threshold: Slot=3, upper threshold=5000, lower threshold=1000, number of drop packets=25552, interval=30s. |
|
Impact |
N/A |
|
Cause |
This log message was generated when the number of packets dropped on a card within a statistics collection interval dropped below the lower threshold and the alarm was cleared. |
|
Recommended action |
No action is required. |
SLOT_PACKETDROP_THRESHOLD
|
Message text |
The number of drop packets exceeded the upper threshold: Slot=[UINT32], upper threshold=[UINT32], lower threshold=[UINT32], number of packet drop packets=[UINT64], interval=[UINT32]s. |
|
Variable fields |
$1: Card information. $2: Upper threshold for the alarm. $3: Lower threshold for the alarm. $4: Number of packets dropped on a card detected within the latest statistics collection interval. $5: Collection and comparison interval for packets dropped on a card, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/SLOT_PACKETDROP_THRESHOLD: The number of drop packets exceeded the upper threshold: Slot=3, upper threshold=5000, lower threshold=1000, number of packet drop packets=25552, interval=30s. |
|
Impact |
The sending bandwidth of normal protocol packets is preempted. As a result, the protocols are interrupted, and data is lost. |
|
Cause |
This log message was generated when the number of packets dropped on a card within a statistics collection interval exceeded the upper threshold. Typically, this issue occurs because the threshold is set improperly or too many packets are lost during transmission. |
|
Recommended action |
1. Use the High threshold field from the display slot-monitor command output to identify whether the configured upper threshold is appropriate. If not, use the slot-monitor packet-drop command to modify the upper threshold. 2. Identify whether the link environment quality is good. |
SLOT_PACKETDROP_THRESHOLD
|
Message text |
Within the last [UINT64] periods,the number of drop packets exceeded the upper threshold: Slot=[UINT32], upper threshold=[UINT32], lower threshold=[UINT32], number of packet drop packets=[UINT64], interval=[UINT32]s. |
|
Variable fields |
$1: Number of statistics collection intervals. $2: Card information. $3: Upper threshold for the alarm. $4: Lower threshold for the alarm. $5: Number of packets dropped on a card detected within the latest statistics collection interval. $6: Collection and comparison interval for packets dropped on a card, in seconds. |
|
Severity level |
4 (Warning) |
|
Example |
IFMON/4/SLOT_PACKETDROP_THRESHOLD: Within the last 10 periods, the number of drop packets exceeded the upper threshold: Slot=3, upper threshold=5000, lower threshold=1000, number of packet drop packets=25552, interval=30s. |
|
Impact |
The sending bandwidth of normal protocol packets is preempted. As a result, the protocols are interrupted, and data is lost. |
|
Cause |
This log message was generated when the number of packets dropped on a card within continuous statistics collection intervals exceeded the upper threshold. Typically, this issue occurs because the threshold is set improperly or too many packets are lost during transmission. |
|
Recommended action |
1. Use the High threshold field from the display slot-monitor command output to identify whether the configured upper threshold is appropriate. If not, use the slot-monitor packet-drop command to modify the upper threshold. 2. Identify whether the link environment quality is good. |
IFNET messages
This section contains interface management messages.
VLAN_MODE_CHG
|
Message text |
Dynamic VLAN [INT32] has changed to a static VLAN. |
|
Variable fields |
$1: VLAN ID. |
|
Severity level |
5 (Notification) |
|
Example |
IFNET/5/VLAN_MODE_CHG: -MDC=1; Dynamic VLAN 20 has changed to a static VLAN. |
|
Impact |
N/A |
|
Cause |
Creating a VLAN interface changes the corresponding dynamic VLAN to a static VLAN. |
|
Recommended action |
No action is required. |
IFNET
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 (Warning) |
|
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. |
|
Impact |
Service traffic might be dropped. |
|
Cause |
FlexE logical interfaces configured with the same client ID on two ends were configured with different available bandwidth. |
|
Recommended action |
Use the client command to modify the available bandwidth of the FlexE logical interface 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 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
IFNET/4/FLEXE_BANDWIDTH_REDUCE: The actual bandwidth 50 Gbps of FlexE logical interface FlexE2/1/129 became less than the configured bandwidth. |
|
Impact |
The bandwidth of a FlexE logical interface decreases. |
|
Cause |
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 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
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. |
|
Impact |
The FlexE physical interface is down. |
|
Cause |
FlexE logical interfaces on two ends were configured with different client IDs. |
|
Recommended action |
Use the client 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 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
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-group interface number. |
|
Severity level |
4 (Warning) |
|
Example |
IFNET/4/FLEXE_GROUP_FAULT: FlexE interface group 1 state changed to fault. |
|
Impact |
A FlexE-group interface fails and cannot forward traffic. |
|
Cause |
All FlexE physical interfaces in an FlexE-group interface went down. As a result, the FlexE-group interface failed. |
|
Recommended action |
Check the physical connection of the FlexE physical interface and identify whether the link fails. |
FLEXE_GROUP_FAULT_RECOVER
|
Message text |
FlexE interface group [INT32] state changed to normal |
|
Variable fields |
$1: FlexE-group interface number. |
|
Severity level |
5 (Notification) |
|
Example |
IFNET/5/FLEXE_GROUP_FAULT_RECOVER: FlexE interface group 1 state changed to normal. |
|
Impact |
No negative impact on the system. |
|
Cause |
FlexE physical interfaces in up state existed in the FlexE interface group, and the FlexE-group interface 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-group interface number. |
|
Severity level |
4 (Warning) |
|
Example |
IFNET/4/FLEXE_GROUPMEMBER_FAULT: FlexE physical interface FlexE-50G2/1/1 in FlexE interface group 1 failed. |
|
Impact |
Service traffic might be dropped. |
|
Cause |
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-group interface number. |
|
Severity level |
5 (Notification) |
|
Example |
IFNET/5/FLEXE_GROUPMEMBER_FAULT_RECOVER: FlexE physical interface FlexE-50G2/1/1 in FlexE interface group 1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
FlexE physical interfaces in the FlexE interface group recover. |
|
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 (Warning) |
|
|
Example |
IFNET/4/FLEXE_PHYFCSSD_ALARM: FCS-SD error occurred on local FlexE physical interface FlexE-50G2/1/1. |
|
|
Impact |
Packets are dropped because of error packets, and service packet forwarding is affected. |
|
|
Cause |
An FCS-SD error occurs on the overhead section layer of 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 (Notification) |
|
|
Example |
IFNET/5/FLEXE_PHYFCSSD_ALARM_RECOVER: FCS-SD error on local FlexE physical interface FlexE-50G2/1/1 was cleared. |
|
|
Impact |
No negative impact on the system. |
|
|
Cause |
An FCS-SD error recovers on the overhead section layer of a FlexE physical interface. |
|
|
Recommended action |
Check the FlexE physical interface, and make sure the FlexE physical interface is connected normally. |
|
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: FlexE-group interface number on the local end. $2: Interface name. $3: Remote FlexE-group interface number. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
A FlexE physical interface cannot come up. |
|
Cause |
The two FlexE physical interfaces connected have inconsistent FlexE-group interfaces. |
|
Recommended action |
Use the bind interface command to modify the FlexE physical interface associated with a FlexE-group interface, and add the two interconnected FlexE physical interfaces to the same FlexE-group interface. |
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: FlexE-group interface number on the local end. $2: Interface name. $3: Remote FlexE-group interface number. |
|
Severity level |
5 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
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. |
|
Impact |
Service switchover or interruption might occur. |
|
Cause |
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 (Notification) |
|
Example |
IFNET/5/FLEXE_PHYLOCAL_FAULT_RECOVER: Local FlexE physical interface FlexE-50G2/1/1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
The local FlexE physical interface recovers. |
|
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 (Warning) |
|
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. |
|
Impact |
A FlexE physical interface cannot come up. |
|
Cause |
Two interconnected FlexE physical interfaces were configured with different PHY numbers. |
|
Recommended action |
Use the bind interface 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 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
IFNET/4/FLEXE_PHYREMOTE_FAULT: The peer interface of local FlexE physical interface FlexE-50G2/1/1 failed. |
|
Impact |
Service switchover or interruption might occur. |
|
Cause |
The peer FlexE physical interface fails |
|
Recommended action |
Identify whether the physical connection of the peer FlexE physical interface is normal or whether the local 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 (Notification) |
|
Example |
IFNET/5/FLEXE_PHYREMOTE_FAULT_RECOVER: The peer interface of local FlexE physical interface FlexE-50G2/1/1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 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 (Warning) |
|
|
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. |
|
|
Impact |
Services on the interfaces are affected. |
|
|
Cause |
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 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 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
The subcards of two interconnected FlexE physical interfaces were configured with the same sub-timeslot granularity. |
|
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 (Error) |
|
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. |
|
Impact |
The impact on the system depends on the actual situation. |
|
Cause |
Some member interfaces do not support the jumboframe enable [ size ] configuration when you modify the aggregate interface. |
|
Recommended action |
Identify the value ranges for the jumbo frame size supported on member ports. Specify a jumbo frame size supported by member ports for the aggregate interface. |
IF_LINKFLAP_DETECTED
|
Message text |
Link flapping was detected on [STRING]. |
|
Variable fields |
$1: Interface name |
|
Severity level |
3 (Error) |
|
Example |
IFNET/3/IF_LINKFLAP_DETECTED: Link flapping was detected on GigabitEthernet1/0/1. |
|
Impact |
Service traffic might be dropped. |
|
Cause |
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_SMOOTH_IF_FAILED
|
Message text |
Failed to smooth interfaces to UP [STRING]. Total failed interfaces: [STRING]. Recently failed to smooth [STRING] interfaces: [STRING]. |
|
Variable fields |
$1: UP ID. $2: Total number of interfaces failing to be smoothed. $3: Number of interfaces failing to be smoothed recently. $4: List of interfaces failing to be smoothed. |
|
Severity level |
5 (Notification) |
|
Example |
IFNET/5/IFMGR_SMOOTH_IF_FAILED: Failed to smooth interfaces to UP 1024. Total failed interfaces: 510. Recently failed to smooth 2 interfaces: GE1/1/0, GE1/2/0. |
|
Impact |
The impact on the system depends on the actual situation. |
|
Cause |
The CP failed to smooth interface information to a UP. |
|
Recommended action |
¡ Verify that the interfaces exist on the UP. 1. Verify that the protocol channel, management channel, and control channel between the CP and UP operate properly. 2. Contact Technical Support. |
INTERFACE_NOTSUPPRESSED
|
Message text |
Interface [STRING] is not suppressed. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
IFNET/6/INTERFACE_NOTSUPPRESSED: Interface GigabitEthernet1/0/1 is not suppressed. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Notification) |
|
Example |
IFNET/5/INTERFACE_SUPPRESSED: Interface GigabitEthernet1/0/1 was suppressed. |
|
Impact |
Service traffic might be dropped. |
|
Cause |
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. Identify whether the cable is frequently plugged and unplugged for the local or peer interface. 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 |
4 (Warning) |
|
Example |
IFNET/4/LINK_UPDOWN: Line protocol state on the interface GigabitEthernet1/0/1 changed to down. |
|
Impact |
If the physical link status of the interface becomes down, it will be unable to forward the traffic. If the physical link status of the interface becomes up, there will be no impact on the system. |
|
Cause |
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 (Warning) |
|
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. |
|
Impact |
PFC packets might be dropped. |
|
Cause |
The rate at which the interface receives or sends PFC packets 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 (Error) |
|
Example |
IFNET/3/PHY_UPDOWN: Physical state on the interface GigabitEthernet1/0/1 changed to down. |
|
Impact |
If the physical status of the interface becomes down, it will be unable to forward the traffic. If the physical status of the interface becomes up, there will be no impact on the system. |
|
Cause |
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: State of link layer protocol, which can be up or down. |
|
Severity level |
5 (Notification) |
|
Example |
IFNET/5/PROTOCOL_UPDOWN: Protocol IPX state on the interface GigabitEthernet1/0/1 changed to up. |
|
Impact |
If the protocol status of the interface becomes down, it will be unable to forward the traffic. If the protocol status of the interface becomes up, there will be no impact on the system. |
|
Cause |
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 (Alert) |
|
Example |
IFNET/1/STORM_CONSTRAIN_BELOW: GigabitEthernet1/0/1 is in controlled status, BC flux falls below its lower threshold 90%. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Alert) |
|
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%. |
|
Impact |
Packets of the specified type might be lost, or the interface might be shut down. |
|
Cause |
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 (Alert) |
|
Example |
IFNET/1/STORM_CONSTRAIN_EXCEED: GigabitEthernet1/0/1 is in controlled status, BC flux exceeds its upper threshold 90%. |
|
Impact |
Packets of the specified type might be lost, or the interface might be shut down. |
|
Cause |
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_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 (Alert) |
|
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%. |
|
Impact |
No negative impact on the system. |
|
Cause |
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. |
VLAN_MODE_CHANGE
|
Message text |
Dynamic VLAN [INT32] has changed to a static VLAN. |
|
Variable fields |
$1: VLAN ID. |
|
Severity level |
5 (Notification) |
|
Example |
IFNET/5/VLAN_MODE_CHANGE: Dynamic VLAN 20 has changed to a static VLAN. |
|
Impact |
No negative impact on the system. |
|
Cause |
Creating a VLAN changes the corresponding dynamic VLAN to a static VLAN. |
|
Recommended action |
No action is required. |
IGMP messages
This section contains IGMP messages.
IGMP_UNICFG_SMOOTH_FAIL
|
Message text |
Failed to smooth configuration with UP (UP-ID:[INTEGER]) from BRAS-VM. |
|
Variable fields |
$1: UP ID |
|
Severity level |
4 (Warning) |
|
Example |
IGMP/4/IGMP_UNICFG_SMOOTH_FAIL: Failed to smooth configuration with UP (UP-ID:1024) from BRAS-VM. |
|
Impact |
IGMP configuration will fail to be deployed. |
|
Cause |
· BRAS-VM and UP-VM connection exception occurred. · The IGMP configuration from the BRAS-VM to the UP-VM conflicts with the IGMP configuration on the UP-VM. |
|
Recommended action |
1. Identify whether the NETCONF channel and CUSP channel between the BRAS-VM and UP-VM are normal. 2. Check the IGMP configuration on the UP-VM and adjust it as needed. |
IKE messages
This section contains IKE messages.
IKE_P1_SA_ESTABLISH_FAIL
|
Message text |
Failed to establish phase 1 SA for the reason of [STRING]. The SA’s source address is [STRING], and its destination address is [STRING]. |
|
Variable fields |
$1: Reason for the failure, including no matching proposal, invalid ID information, unavailable certificate, unsupported DOI, unsupported situation, invalid proposal syntax, invalid SPI, invalid protocol ID, invalid certificate, authentication failure, invalid message header, invalid transform ID, malformed payload, retransmission timeout, and incorrect configuration. $2: Source address. $3: Destination address. |
|
Severity level |
6 (Informational) |
|
Example |
IKE/6/IKE_P1_SA_ESTABLISH_FAIL: Failed to establish phase 1 SA for the reason of no matching proposal. The SA’s source address is 1.1.1.1, and its destination address is 2.2.2.2. |
|
Impact |
The IKE SA cannot be established. |
|
Cause |
· The IKE proposal parameters and IKE authentication algorithms are inconsistent between the two ends. · The preshared keys are inconsistent between the two ends. · The certificate is unavailable or invalid. · The physical link status is poor or the peer network is unreachable. |
|
Recommended action |
· Verify that the two ends use the same IKE proposal parameters and IKE authentication algorithms. · Verify that the two ends use the same preshared key. · Verify that the two ends have obtained certificates and the certificates are effective. · Troubleshoot network issues to make sure the physical link status is good and the peer network is reachable. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IKE_P2_SA_ESTABLISH_FAIL
|
Message text |
Failed to establish phase 2 SA for the reason of [STRING]. The SA’s source address is [STRING], and its destination address is [STRING]. |
|
Variable fields |
$1: Reason for the failure, including invalid key information, invalid ID information, unavailable proposal, unsupported DOI, unsupported situation, invalid proposal syntax, invalid SPI, invalid protocol ID, invalid hash information, invalid message header, malformed payload, retransmission timeout, and incorrect configuration. $2: Source address. $3: Destination address. |
|
Severity level |
6 (Informational) |
|
Example |
IKE/6/IKE_P2_SA_ESTABLISH_FAIL: Failed to establish phase 2 SA for the reason of invalid key information. The SA’s source address is 1.1.1.1, and its destination address is 2.2.2.2. |
|
Impact |
The IPsec SA cannot be established. |
|
Cause |
· The IPsec transform set parameters, IPsec authentication and encryption algorithms, and IPsec encapsulation modes are inconsistent between the two ends. · The IPsec policy settings are inconsistent between the two ends. · The ACLs used by the two ends are not mirror ACLs. · The physical link status is poor or the peer network is unreachable. |
|
Recommended action |
· Verify that the two ends use the same IPsec transform set parameters, IPsec authentication and encryption algorithms, and IPsec encapsulation mode. · Verify that the two ends use the same IPsec policy configuration. · Verify that the ACLs used by the two ends are mirror ACLs. · Troubleshoot network issues to make sure the physical link status is good and the peer network is reachable. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IKE_P2_SA_TERMINATE
|
Message text |
The IKE phase 2 SA was deleted for the reason of [STRING]. The SA’s source address is [STRING], and its destination address is [STRING]. |
|
Variable fields |
$1: Reason why the SA was deleted: SA expiration $2: Source address. $3: Destination address. |
|
Severity level |
6 (Informational) |
|
Example |
IKE/6/IKE_P2_SA_TERMINATE: The IKE phase 2 SA was deleted for the reason of SA expiration. The SA’s source address is 1.1.1.1, and its destination address is 2.2.2.2. |
|
Impact |
When the IKE phase 2 SA is deleted, the IPsec service that the SA carries is interrupted. |
|
Cause |
The IKE phase 2 SA was deleted due to expiration. |
|
Recommended action |
· If an SA was deleted due to reasons listed in this log, it will be renegotiated and established normally. In this case, no action is required. · If an SA was deleted due to other reasons, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
INQA messages
This section contains iNQA messages.
INQA_COUNTER_NORES
|
Message text |
Not enough counter resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
INQA/4/INQA_COUNTER_NORES: Not enough counter resource. |
|
Impact |
The system failed to perform iNQA operations on the newly learned target flows. |
|
Cause |
The system failed to perform iNQA operations on the newly learned target flows because of insufficient counter resources. |
|
Recommended action |
1. Use the display this command in iNQA view to view configured iNQA instances. 2. Use the undo instance instance-id command to delete unnecessary instances, thus releasing counter resources. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INQA_ACL_NORES
|
Message text |
Not enough ACL resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
INQA/4/INQA_ACL_NORES: Not enough ACL resource. |
|
Impact |
The system failed to perform iNQA operations on the newly learned target flows. |
|
Cause |
The system failed to perform iNQA operations on the newly learned target flows because of insufficient ACL resources. |
|
Recommended action |
1. Use the display this command in iNQA view to view configured iNQA instances. 2. Use the undo instance instance-id command to delete unnecessary instances, thus releasing ACL resources. 3. Delete other unnecessary services that occupy ACL resources. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
iNQA messages
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 (Notification) |
|
Example |
INQA/5/INQA_BWD_LOSS_EXCEED: Packet loss rate of the backward flow in instance 1 exceeded the upper limit. |
|
Impact |
The packet loss rate is too high, which might not meet the service requirements. As a result, the service is affected. |
|
Cause |
If you enable packet loss measurement for backward flows, iNQA will measure packet loss rate at the specified intervals. If the packet loss rate exceeds or reaches the threshold for a consecutive of five intervals, the instance has too many lost packets, and the analyzer will generate a threshold-exceeded log. Possible reasons for this log include: · Abnormal traffic results in network congestion. · The link state is unstable. |
|
Recommended action |
1. Identify whether the network contains abnormal traffic when this log is generated. 2. Identify whether the link state is stable in the network when this log is generated. Troubleshoot and eliminate the factors for the unstable link state. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
INQA/6/INQA_BWD_LOSS_RECOV: Packet loss rate of the backward flow in instance 1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
When iNQA measures packet loss rate for backward flows at the specified intervals, if the packet loss rate drops down below the recovery threshold for a consecutive of five intervals, the packet loss rate for the instance has returned to normal range. The analyzer then generates this log. |
|
Recommended action |
No action is required. |
INQA_DEBUG_FAIL
|
Message text |
Setting debugging switch to drive failed. |
|
Severity level |
5 (Notification) |
|
Example |
INQA/5/INQA_DEBUG_FAIL: Setting debugging switch to drive failed. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when the system fails to set iNQA debugging switch to drive. |
|
Recommended action |
1. Execute the display debugging command to view the iNQA debugging switch setting. 2. Execute the debugging inqa command to reconfigure the iNQA debugging switch setting. |
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 (Notification) |
|
Example |
INQA/5/INQA_FLAG_DIFF: Flags of collectors bound with the analyzer instance 1 are inconsistent. |
|
Impact |
No negative impact on the system. |
|
Cause |
Configuration error. |
|
Recommended action |
1. Execute the display inqa analyzer instance command to check the IDs of all collectors bound to the analyzer instance. 2. Log in to each collector, and execute the display inqa collector command to view the value for the Loss-measure flag field. If a configuration error exists, use the flag command to edit the configuration in collector view. |
INQA_FLAG_FAIL
|
Message text |
Setting coloring bit to drive failed. |
|
Severity level |
5 (Notification) |
|
Example |
INQA/5/INQA_FLAG_FAIL: Setting coloring bit to drive failed. |
|
Impact |
No negative impact on the system. |
|
Cause |
Insufficient hardware resources. |
|
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. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Notification) |
|
Example |
INQA/5/INQA_FLOW_DIFF: Flows of collectors bound with the analyzer instance 1 are inconsistent. |
|
Impact |
No negative impact on the system. |
|
Cause |
Configuration error. |
|
Recommended action |
1. Execute the display inqa analyzer instance command to check the IDs of all collectors bound to the analyzer instance. 2. Log in to each collector, and execute the display inqa collector command to view the value for the Flow configuration field. If configuration inconsistency exists, use the flow command to edit the configuration in collector instance view. |
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 (Notification) |
|
Example |
INQA/5/INQA_FWD_LOSS_EXCEED: Packet loss rate of the forward flow in instance 1 exceeded the upper limit. |
|
Impact |
The packet loss rate is too high, which might not meet the service requirements. As a result, the service is affected. |
|
Cause |
If you enable packet loss measurement for forward flows, iNQA will measure packet loss rate at the specified intervals. If the packet loss rate exceeds or reaches the threshold for a consecutive of five intervals, the instance has too many lost packets, and the analyzer will generate a threshold-exceeded log. Possible reasons for this log include: · Abnormal traffic results in network congestion. · The link state is unstable. |
|
Recommended action |
1. Identify whether the network contains abnormal traffic when this log is generated. 2. Identify whether the link state is stable in the network when this log is generated. Troubleshoot and eliminate the factors for the unstable link state. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
INQA/6/INQA_FWD_LOSS_RECOV: Packet loss rate of the forward flow in instance 1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
When iNQA measures packet loss rate for forward flows at the specified intervals, if the packet loss rate drops down below the recovery threshold for a consecutive of five intervals, the packet loss rate for the instance has returned to normal range. The analyzer then generates this log. |
|
Recommended action |
No action is required. |
INQA_INST_FAIL
|
Message text |
Setting instance [UINT] information to drive failed. |
|
Variable fields |
$1: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
INQA/5/INQA_INST_FAIL: Setting instance 1 information to drive failed. |
|
Impact |
No negative impact on the system. |
|
Cause |
Insufficient hardware resources. |
|
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. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Notification) |
|
Example |
INQA/5/INQA_INTVL_DIFF: Intervals of collectors bound with analyzer instance 1 are inconsistent. |
|
Impact |
No negative impact on the system. |
|
Cause |
Configuration error. |
|
Recommended action |
1. Execute the display inqa analyzer instance command to check the IDs of all collectors bound to the analyzer instance. 2. Log in to each collector, and execute the display inqa collector command to view the value for the Interval field. If a configuration error exists, use the interval command to edit the configuration in collector instance view. |
INQA_NO_RESOURCE
|
Message text |
Failed to configure instance [UINT] due to insufficient resources. |
|
Variable fields |
$1: ID of the instance. |
|
Severity level |
5 (Notification) |
|
Example |
INQA/5/INQA_NO_RESOURCE: Failed to configure instance 1 due to insufficient resources. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when iNQA fails to configure an instance due to insufficient ACL resources. |
|
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. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INQA_NO_SUPPORT
|
Message text |
iNQA is not supported in this slot. |
|
Severity level |
5 (Notification) |
|
Example |
INQA/5/INQA_NO_SUPPORT: -Slot=1; iNQA is not supported in this slot. |
|
Impact |
No negative impact on the system. |
|
Cause |
The hardware does not support iNQA. |
|
Recommended action |
iNQA requires hardware support. Install an iNQA-capable module 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 (Notification) |
|
Example |
INQA/5/INQA_SMOOTH_BEGIN_FAIL: Setting smoothing beginning to the kernel failed. |
|
Impact |
No negative impact on the system. |
|
Cause |
Communication failure in software. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INQA_SMOOTH_END_FAIL
|
Message text |
Setting smoothing ending to kernel failed. |
|
Severity level |
5 (Notification) |
|
Example |
INQA/5/INQA_SMOOTH_END_FAIL: Setting smoothing ending to kernel failed. |
|
Impact |
No negative impact on the system. |
|
Cause |
Communication failure in software. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INTRACE messages
This section contains Internet Protocol Control Block (INPCB) messages.
WHITELIST
|
Message text |
-[STRING]; Failed to add ACL rule [STRING]:[UINT16] -> [STRING]:[UINT16] to the whitelist, VRF: [UINT16], error code: 0x[UINT32]. |
|
Variable fields |
$1: Card number. $2: Local address. $3: Local port number. $4: Remote address. $5: Remote port number. $6: VRF (VPN instance) index. $7: Error code: ¡ 0x22010002—The ACL rule already exists. ¡ 0x22010008—The number of rules in the whitelist has reached the upper limit. ¡ 0x40010001—Other errors, for example, the MDC control block does not exist. ¡ 0x4001000B—Insufficient resources. |
|
Severity level |
3 (Error) |
|
Example |
INTRACE/3/WHITELIST: -Chassis=2-Slot=3; Failed to add ACL rule 1.1.1.1:36523 -> 1.1.1.2:179 to the whitelist, VRF: 0, error code: 0x22010002. |
|
Impact |
The TCP allowlist service is faulty. |
|
Cause |
The ACL process is faulty, and a message that failed to add to the allowlist is returned to the TCP module. |
|
Recommended action |
· If the ACL rule already exists, it conflicts with the TCP allowlist rule. In this case, edit the ACL filtering rule. · If the issue persists, collect output information of the display tcp whitelist command, and then contact Technical Support for help. |
|
Message text |
-[STRING]; Failed to delete ACL rule [STRING]:[UINT16] -> [STRING]:[UINT16] from the whitelist, VRF: [UINT16], error code: 0x[UINT32]. |
|
Variable fields |
$1: Card number. $2: Local address. $3: Local port number. $4: Remote address. $5: Remote port number. $6: VRF (VPN instance) index. $7: Error code: ¡ 0x40010001—Other errors, for example, the MDC control block does not exist. ¡ 0x40010008—Incorrect input parameters. ¡ 0x4001000B—Insufficient resources. |
|
Severity level |
3 (Error) |
|
Example |
INTRACE/3/WHITELIST:-Chassis=2-Slot=3; Failed to delete ACL rule 1.1.1.1:36523 -> 1.1.1.2:179 from the whitelist, VRF: 0, error code: 0x40010001. |
|
Impact |
The TCP allowlist service is faulty. |
|
Cause |
The ACL process is faulty, and a message that failed to remove from the allowlist is returned to the TCP module. |
|
Recommended action |
Collect output information of the display tcp verbose and display tcp whitelist commands, and then contact Technical Support for help. |
Introduction
This document includes the following system messages:
· Messages specific to Release xxx of the switch.
· Messages for the Comware 7 software platform version based on which Release xxx was produced. Some platform system messages might not be available on the switch.
This document is intended only for managing XXX 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 7 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 3. |
|
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 only available 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 3.) |
|
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 4. 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 3.
Table 8 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 4. The values are case insensitive, even though the representations are uppercase letters.
Table 9 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 cfa0:/logfile/ path if the CF card is not partitioned. If the CF card is partitioned, the file path is cfa1:/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 5 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 |
|
AFT |
Address Family Translation |
|
ANCP |
Access Node Control Protocol |
|
APMGR |
Access Point Management |
|
ARP |
Address Resolution Protocol |
|
ATK |
ATK Detect and Defense |
|
ATM |
Asynchronous Transfer Mode |
|
BFD |
Bidirectional Forwarding Detection |
|
BGP |
Border Gateway Protocol |
|
BIER |
Bit Index Explicit Replication |
|
BLS |
Blacklist |
|
CFD |
Connectivity Fault Detection |
|
CFGMAN |
Configuration Management |
|
CLKM |
Clock Monitoring |
|
CONNLMT |
Connect Limit |
|
CPDR |
Control Plane Disaster Recovery |
|
CUSP |
Control-/User-plane Separation Protocol |
|
DEV |
Device Management |
|
DHCP |
Dynamic Host Configuration Protocol |
|
DHCPR |
IPv4 DHCP Relay |
|
DHCPR6 |
IPv6 DHCP Relay |
|
DHCPS |
IPv4 DHCP Server |
|
DHCPS6 |
IPv6 DHCP Server |
|
DHCPSP4 |
IPv4 DHCP snooping |
|
DHCPSP6 |
IPv6 DHCP snooping |
|
DIAG |
Diagnosis |
|
DLDP |
Device Link Detection Protocol |
|
DOMAIN |
Domain |
|
DOT1X (Layer 2) |
802.1X |
|
DOT1X (Layer 3) |
802.1X |
|
EDEV |
Extender Device Management |
|
EIGRP |
Enhanced Interior Gateway Routing Protocol |
|
EM |
rEceive & transMit |
|
ERPS |
Ethernet Ring Protection Switching |
|
ETH |
Ethernet |
|
ETHOAM |
Ethernet Operation, Administration and Maintenance |
|
EVB |
Ethernet Virtual Bridging |
|
EVIISIS |
Ethernet Virtual Interconnect Intermediate System-to-Intermediate System |
|
FCLINK |
Fibre Channel Link |
|
FCOE |
Fibre Channel Over Ethernet |
|
FCZONE |
Fibre Channel Zone |
|
FIB |
Forwarding Information Base |
|
FILTER |
Filter |
|
FIPSNG |
FIP Snooping |
|
FTP |
File Transfer Protocol |
|
gRPC |
Google Remote Procedure Call |
|
HA |
High Availability |
|
HQOS |
Hierarchical QoS |
|
HTTPD |
Hypertext Transfer Protocol Daemon |
|
iFIT |
in-situ Flow Information Telemetry |
|
IFMON |
Interface Monitor |
|
IFNET |
Interface Net Management |
|
IGMP |
Internet Group Management Protocol |
|
IKE |
Internet Key Exchange |
|
iNQA |
Intelligent Network Quality Analyzer |
|
INTRACE |
INTRACE |
|
IP6ADDR |
IPv6 address |
|
IP6FW |
IPv6 Forwarding |
|
IPADDR |
IP address |
|
IPFW |
IP Forwarding |
|
IPOE |
IP Over Ethernet |
|
IPSEC |
IP Security |
|
IPSG |
IP Source Guard |
|
IRDP |
ICMP Router Discovery Protocol |
|
IRF |
Intelligent Resilient Framework |
|
ISIS |
Intermediate System-to-Intermediate System |
|
ISSU |
In-Service Software Upgrade |
|
KHTTP |
Kernel Hypertext Transfer Protocol |
|
L2PT |
Layer 2 Protocol Tunneling |
|
L2TPV2 |
Layer 2 Tunneling Protocol Version 2 |
|
L2VPN |
Layer 2 VPN |
|
L3VPN |
Layer 3 VPN |
|
LAGG |
Link Aggregation |
|
LB |
Load Balance |
|
LDP |
Label Distribution Protocol |
|
LIPC |
Leopard Inter-process Communication |
|
LIC |
License |
|
LLDP |
Link Layer Discovery Protocol |
|
LOAD |
Load Management |
|
LOCAL |
Local |
|
LOGIN |
Login |
|
LPDT |
Loopback Detection |
|
LS |
Local Server |
|
LSM |
Label Switch Management |
|
LSPV |
LSP Verification |
|
MAC |
Media Access Control |
|
MACA |
MAC Authentication |
|
MACSEC |
MAC Security |
|
MBFD |
MPLS BFD |
|
MBUF |
Memory Buffer |
|
MDC |
Multitenant Device Context |
|
MFIB |
Multicast Forwarding Information Base |
|
MGROUP |
Mirroring group |
|
MPLS |
Multiprotocol Label Switching |
|
MSC |
Media Stream Control |
|
MSDP |
Multicast Source Discovery Protocol |
|
MTLK |
Monitor Link |
|
MTP |
Maintain Probe |
|
NAT |
Network Address Translate |
|
NCM |
Netconf Client Management |
|
ND |
Neighbor Discovery |
|
NETCONF |
Network Configuration Protocol |
|
NETSLICE |
SRv6 Network Slicing |
|
NQA |
Network Quality Analyzer |
|
NTP |
Network Time Protocol |
|
OAM |
VM internal link OAM |
|
OBJP |
Object Policy |
|
OFP |
OpenFlow Protocol |
|
OPENSRC(DB-VM) |
Open Source(Database virtual machine) |
|
OPENSRC(RSYNC) |
Open Source(Remote Synchronize) |
|
OPTMOD |
Optical Module |
|
OSPF |
Open Shortest Path First |
|
OSPFV3 |
Open Shortest Path First Version 3 |
|
PathMTU |
VM Path MTU |
|
PBB |
Provider Backbone Bridge |
|
PBR |
Policy Based Route |
|
PCE |
Path Computation Element |
|
PEX |
Port Extender |
|
PFILTER |
Packet Filter |
|
PIM |
Protocol Independent Multicast |
|
PING |
Packet Internet Groper |
|
PKG |
Package management |
|
PKI |
Public Key Infrastructure |
|
PKT2CPU |
Packet to CPU |
|
PKTCPT |
Packet Capture |
|
PORTAL |
Portal |
|
PORTSEC |
Port Security |
|
PPP |
Point to Point Protocol |
|
PTP |
Precision Time Protocol |
|
PWDCTL |
Password Control |
|
QOS |
Quality of Service |
|
RADIUS |
Remote Authentication Dial In User Service |
|
RDDC |
Redundancy |
|
RESMON |
RESOURCE MONITER |
|
RIP |
Routing Information Protocol |
|
RIPNG |
Routing Information Protocol Next Generation |
|
RM |
Routing Management |
|
RPR |
Resilient Packet Ring |
|
RMDB |
Remote Database |
|
RRPP |
Rapid Ring Protect Protocol |
|
RSVP |
Resource Reservation Protocol |
|
RTM |
Real-Time Management |
|
SAVA |
Source Address Validation Architecture |
|
SCMD |
Service Control Manager |
|
SCRLSP |
Static CRLSP |
|
SESSION |
Session |
|
SFLOW |
Sampler Flow |
|
SHELL |
Shell |
|
SLSP |
Static LSP |
|
SMLK |
Smart Link |
|
SNMP |
Simple Network Management Protocol |
|
SRP |
SR-MPLS TE Policy |
|
SRPM |
Segment Routing Performance Measurement |
|
SRPV6 |
SRv6 TE Policy |
|
SRV6 |
SRv6 |
|
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 |
|
TE |
Traffic Engineering |
|
TELNETD |
Telnet Daemon |
|
TRILL |
Transparent Interconnect of Lots of Links |
|
UCM |
User Connection Management |
|
UNICFG |
Unified Configuration Management |
|
UPBAK |
User Plane Backup |
|
UPLB |
User Plane Load Balance |
|
UPMGR |
User Plane Management |
|
URPF |
Unicast Reverse Path Forwarding |
|
USER |
User |
|
VLAN |
Virtual Local Area Network |
|
VMMGR |
VM Manager |
|
VMPATHMTU |
Virtual Machine Path MTU |
|
VRRP4 |
IPv4 Virtual Router Redundancy Protocol |
|
VRRP6 |
IPv6 Virtual Router Redundancy Protocol |
|
VSRP |
Virtual Service Redundancy Protocol |
|
VXLAN |
Virtual eXtensible LAN |
|
WEB |
Web |
|
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 6 describes information provided in these tables.
Table 11 Message explanation table contents
|
Item |
Content |
Example |
|
Message text |
Presents the message description. |
ACL [UINT32] [STRING] [UINT64] packet(s). |
|
Variable fields |
Briefly describes the variable fields in the order that they appear in the message text. The variable fields are numbered in the "$Number" form to help you identify their location in the message text. |
$1: ACL number. $2: ID and content of an ACL rule. $3: Number of packets that matched the rule. |
|
Severity level |
Provides the severity level of the message. |
6 |
|
Example |
Provides a real message example. The examples do not include the "<PRI>TIMESTAMP Sysname %%vendor" part or the "Prefix TIMESTAMP Sysname" part, because information in this part varies with system settings. |
ACL/6/ACL_STATIS_INFO: ACL 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s). |
|
Explanation |
Explains the message, including the event or error cause. |
Number of packets that matched an ACL rule. This message is sent when the packet counter changes. |
|
Recommended action |
Provides recommended actions. For informational messages, no action is required. |
No action is required. |
IP ROUTING messages
This section contains IP routing messages.
ROUTE_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
L3/3/ROUTE_NORES: -MDC=1-Slot=4; No enough resource |
|
Impact |
The current operation fails. |
|
Cause |
Failed to perform the operation because of insufficient hardware resources. For example, packet statistics collection cannot be performed because of insufficient statistics-collection resources. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ECMP_NORES
|
Message text |
Not enough ECMP-ID resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/ECMP_NORES: -MDC=1-Slot=5; Not enough ECMP-ID resource. |
|
Impact |
The current cannot learn new IPv4 equal-cost routes. |
|
Cause |
A card failed to learn a new equal-cost route because of insufficient ECMP-ID resources on the card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ROUTE6_ECMP_NORES
|
Message text |
Not enough ECMP-ID resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/ROUTE6_ECMP_NORES: -MDC=1-Slot=5; Not enough ECMP-ID resource. |
|
Impact |
The current cannot learn new IPv6 equal-cost routes. |
|
Cause |
A card failed to learn a new equal-cost route because of insufficient ECMP-ID resources on the card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
VN_NORES
|
Message text |
No enough VN index resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/VN_NORES: -MDC=1-Slot=3; No enough VN index resource. |
|
Impact |
The current cannot learn new non-host routes. |
|
Cause |
A card failed to learn a new non-host route because of insufficient VN index resources on the card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
VN_ECMP_NORES
|
Message text |
Not enough ECMP-ID resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/VN_ECMP_NORES: -MDC=1-Slot=3; Not enough ECMP-ID resource. |
|
Impact |
The current cannot learn new equal-cost routes. |
|
Cause |
A card failed to learn a new equal-cost route because of insufficient ECMP-ID resources on the card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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: SRv6 locator. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
IPv6 address generation failed on the interface, which affects normal service operation. |
|
Cause |
The IPv6 address configured for the interface by using the ipv6 address prefix-number command conflicts with the Locator field configured in SRv6 view. |
|
Recommended action |
Examine the interface IPv6 address configured by using the ipv6 address prefix-number command and the Locator field in SRv6 view, remove the conflicting configuration, and configure a new IPv6 address for the interface. |
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 (Warning) |
|
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. |
|
Impact |
IPv6 interface address generation fails, which causes abnormal service running. |
|
Cause |
The device failed to generate an IPv6 address for an interface by using the prefix specified in the ipv6 address prefix-number command, because the prefixes overlapped on this interface and another interface. |
|
Recommended action |
Check the IPv6 prefixes of the related interfaces, 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_FAIL
|
Message text |
Pattern 1: Failed to create an address. Reason: The IPv6 address [STRING] configured on [STRING] is being used by interface [STRING] on the device. Pattern 2: Failed to create an address. Reason: The subnet of the IPv6 address [STRING] configured on [STRING] overlaps with the subnet of interface [STRING] on the device. |
|
Variable fields |
$1: IPv6 address. $2: Interface name 1. $3: Interface name 2. |
|
Severity level |
3 (Error) |
|
Example |
Pattern 1: IP6ADDR/3/IP6ADDR_CREATEADDRESS_FAIL: Failed to create an address. Reason:The IPv6 address 2::1 configured on GigabitEthernet 1/0/1 is being used by interface GigabitEthernet 1/0/2 on the device. Pattern 2: IP6ADDR/3/IP6ADDR_CREATEADDRESS_FAIL: Failed to create an address. Reason:The subnet of the IPv6 address 3::10 configured on Vlan-interface 10 overlaps with the subnet of interface Vlan-interface 20 on the device. |
|
Impact |
IPv6 interface address generation fails, which causes abnormal service running. |
|
Cause |
· The message in pattern 1 is generated when the IPv6 address configured for an interface is in use by another interface. · The message in pattern 2 is generated when the IPv6 address configured for an interface has a subnet conflict with another interface's IPv6 address. |
|
Recommended action |
Cancel the invalid configuration and reconfigure an IPv6 address for the interface, according to the network plan and service deployment requirements. |
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 (Warning) |
|
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. |
|
Impact |
IPv6 interface address generation fails, which causes abnormal service running. |
|
Cause |
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. |
|
Recommended action |
Cancel the invalid configuration and reconfigure an IPv6 address for the interface. |
IP6FW
This section contains IPv6 forwarding messages.
IP6FW_ABNORMAL_HEADERS
|
Message text |
Received an IPv6 packet with repeated extension headers. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
IP6FW/6/IP6FW_ABNORMAL_HEADERS: Received an IPv6 packet with repeated extension headers. |
|
Impact |
N/A |
|
Cause |
The IPv6 packet has errors. |
|
Recommended action |
Verify the validity of the packet source. |
IP6FW_FAILED_TO_SET_MTU
|
Message text |
The operation is not supported to set driver IPv6 interface MTU: interface is [STRING], MTU is [UINT32]. |
|
Variable fields |
$1: MTU value. $2: Interface name. |
|
Severity level |
5 (Notification) |
|
Example |
IP6FW/5/IP6FW_FAILED_TO_SET_MTU: The operation is not supported to set driver IPv6 interface MTU: interface is GigabitEthernet2/0/2, MTU is 1280. |
|
Impact |
N/A |
|
Cause |
The interface is set with an invalid MTU or configuration deployment failed. |
|
Recommended action |
Modify the interface MTU. |
IP6FW_PMTU_MAXNUMBER
|
Message text |
The number of toobig PMTU entries has reached the limit. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
IP6FW/6/IP6FW_PMTU_MAXNUMBER: The number of toobig PMTU entries has reached the limit. |
|
Impact |
N/A |
|
Cause |
The number of dynamic entries added due to "toobig" packets has reached the system upper limit. No more dynamic entries can be added. |
|
Recommended action |
No action is required. |
IPADDR messages
This section contains IP addressing messages.
IPADDR_CREATEADDRESS_CONFILICTADDR
|
Message text |
The IP address [STRING] configured on [STRING] is used by interface [STRING] on the device. |
|
Parameters |
$1: IP address. $2: Interface name. $3: Interface name. |
|
Severity level |
3 (Error) |
|
Example |
IPADDR/3/IPADDR_CREATEADDRESS_CONFILICTADDR: The IP address 192.168.56.166 configured on GigabitEthernet 1/0/1 is used by interface GigabitEthernet 1/0/2 on the device. |
|
Impact |
Failed to configure an IPv4 address for the interface. |
|
Cause |
When the system deploys the configured IPv4 address to the interface, it detects that the address has been already configured for another interface. |
|
Recommended action |
Configure another address for the interface. |
IPADDR_CREATEADDRESS_OVERLAPADDR
|
Message text |
The subnet of the IP address [STRING] configured on [STRING] overlaps with the subnet of interface [STRING] on the device. |
|
Parameters |
$1: IP address. $2: Interface name. $3: Interface name. |
|
Severity level |
3 (Error) |
|
Example |
IPADDR/3/IPADDR_CREATEADDRESS_OVERLAPADDR: The subnet of the IP address 192.168.56.166 configured on Vlan-interface 10 overlaps with the subnet of interface Vlan-interface 20 on the device. |
|
Impact |
Failed to configure an IPv4 address for the interface. |
|
Cause |
When the system deploys the configured IPv4 address to the interface, it detects that the address conflicts with the network segment configured for another interface. |
|
Recommended action |
Configure an address in another network segment for the interface. |
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 (Warning) |
|
Example |
IPADDR/4/IPADDR_HA_EVENT_ERROR: A process failed HA upgrade because IPADDR failed the smooth upgrade. |
|
Impact |
The primary/secondary switchover service cannot take effect, because the IP address module does not respond to the HA event. |
|
Cause |
A process failed HA upgrade and the message showed the failure reason. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support. |
IPADDR_HA_STOP_EVENT
|
Message text |
The device received an HA stop event. |
|
Variable fields |
None. |
|
Severity level |
4 (Warning) |
|
Example |
IPADDR/4/IPADDR_HA_STOP_EVENT: The device received an HA stop event. |
|
Impact |
The device is downgraded from primary to secondary. |
|
Cause |
The device receives an HA stop event during master/backup switchover of the process. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support. |
IPFW
This section contains IP forwarding messages.
IP_ADD_FLOW_ANTITCPSYNFLD
|
Message text |
Add a flow-based entry: Packet type=[STRING]; SrcIP=[IPADDR]; DstPort=[UINT16]; VPN=[STRING]. |
|
Variable fields |
$1: Packet type. Options include: · MPLS · IP $2: Source IP address of the attack packet. $3: Number of the destination port being attacked. $4: VPN instance name. For the public network, this field displays the public network. If the system fails to obtain the VPN instance name, this field displays N/A. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_ADD_FLOW_ANTITCPSYNFLD: Add a flow-based entry: Packet type=IP; SrcIP=2000::1; DstPort=23; VPN=the public network |
|
Impact |
The device is under TCP SYN Flood attacks, which might result in excessive use of system resources. |
|
Cause |
A data flow to the device has been detected sending excessive SYN packets, which might indicate a flow-based TCP SYN Flood attack. The system then adds a prevention entry for this type of attack based on the flow. |
|
Recommended action |
Verify if the source of the TCP SYN packet is valid based on information in the log message. |
IP_ADD_FLOW_ANTIUDPFLD
|
Message text |
Add a flow-based entry: Packet type=[STRING]; SrcIP=[IPADDR]; DstPort=[UINT16]; VPN=[STRING]. |
|
Variable fields |
$1: Packet type. Options include: · MPLS · IP $2: Source IP address of the attack packet. $3: Number of the destination port being attacked. $4: VPN instance name. For the public network, this field displays the public network. If the system fails to obtain the VPN instance name, this field displays N/A. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_ADD_FLOW_ANTIUDPFLD: Add a flow-based entry: Packet type=IP; SrcIP=2000::1; DstPort=69; VPN=the public network. |
|
Impact |
The device is under UDP Flood attacks, which might result in a heavy system load. |
|
Cause |
A data flow to the device has been detected sending excessive UDP packets, which might indicate a flow-based UDP Flood attack. The system then adds a prevention entry for this type of attack based on the flow. |
|
Recommended action |
Verify if the source of the UDP packet is valid based on information in the log message. |
IP_ADD_INTERFACE_ANTITCPSYNFLD
|
Message text |
Add an interface-based entry: Packets type=[STRING]; Interface=[STRING]. |
|
Variable fields |
$1: Packet type. Options include: · MPLS · IP $2: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_ADD_INTERFACE_ANTITCPSYNFLD: Add an interface-based entry: Packets type=MPLS; Interface=GigabitEthernet1/0/1. |
|
Impact |
The device is under TCP SYN Flood attacks, which might result in excessive use of system resources. |
|
Cause |
It has been detected that a particular interface received an excessive number of SYN packets, which might indicates an interface-based TCP SYN Flood attack. The system then adds a prevention entry for this attack based on the interface. |
|
Recommended action |
Verify if the source of the TCP SYN packet is valid based on information in the log message. |
IP_ADD_INTERFACE_ANTIUDPFLD
|
Message text |
Add an interface-based entry: Packets type=[STRING]; Interface=[STRING]. |
|
Variable fields |
$1: Packet type. Options include: · MPLS · IP $2: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_ADD_INTERFACE_ANTIUDPFLD: Add an interface-based entry: Packets type=MPLS; Interface=GigabitEthernet1/0/1. |
|
Impact |
The device is under UDP Flood attacks, which might result in a heavy system load. |
|
Cause |
It has been detected that a particular interface received an excessive number of UDP packets, which might indicates an interface-based UDP Flood attack. The system then adds a prevention entry for this attack based on the interface. |
|
Recommended action |
Verify if the source of the UDP packet is valid based on information in the log message. |
IP_CLEARDRVSTAT_ANTITCPSYNFLD
|
Message text |
Failed to clear drive's statistics. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_CLEARDRVSTAT_ANTITCPSYNFLD: Failed to clear drive's statistics. |
|
Impact |
No negative impact on the system. |
|
Cause |
Hardware issue. |
|
Recommended action |
No action is required. |
IP_CLEARDRVSTAT_ANTIUDPFLD
|
Message text |
Failed to clear drive's statistics. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_CLEARDRVSTAT_ANTIUDPFLD: Failed to clear drive's statistics. |
|
Impact |
N/A |
|
Cause |
Hardware issue. |
|
Recommended action |
No action is required. |
IP_DEL_FLOW_ANTITCPSYNFLD
|
Message text |
Delete a flow-based entry: Packet type=[STRING]; SrcIP=[IPADDR]; DstPort=[UINT16]; VPN=[STRING]. |
|
Variable fields |
$1: Packet type. Options include: · MPLS · IP $2: Source IP address of the attack packet. $3: Number of the port being attacked. $4: VPN instance name. For the public network, this field displays the public network. If the system fails to obtain the VPN instance name, this field displays N/A. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_DEL_FLOW_ANTITCPSYNFLD: Delete a flow-based entry: Packet type=MPLS; SrcIP=192.168.1.2; DstPort=80; VPN=vpn1. |
|
Impact |
N/A |
|
Cause |
An entry aged out. |
|
Recommended action |
No action is required. |
IP_DEL_FLOW_ANTIUDPFLD
|
Message text |
Delete a flow-based entry: Packet type=[STRING]; SrcIP=[IPADDR]; DstPort=[UINT16]; VPN=[STRING]. |
|
Variable fields |
$1: Packet type. Options include: · MPLS · IP $2: Source IP address of the attack packet. $3: Number of the port being attacked. $4: VPN instance name. For the public network, this field displays the public network. If the system fails to obtain the VPN instance name, this field displays N/A. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_DEL_FLOW_ANTIUDPFLD: Delete a flow-based entry: Packet type=MPLS; SrcIP=192.168.1.2; DstPort=80; VPN=vpn1. |
|
Impact |
N/A |
|
Cause |
An entry aged out. |
|
Recommended action |
No action is required. |
IP_DEL_INTERFACE_ANTITCPSYNFLD
|
Message text |
Delete an interface-based entry: Packets type=[STRING]; Interface=[STRING]. |
|
Variable fields |
$1: Packet type. Options include: · MPLS · IP $2: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_DEL_INTERFACE_ANTITCPSYNFLD: Delete an interface-based entry: Packets type=IP, Interface=GigabitEthernet1/0/1. |
|
Impact |
N/A |
|
Cause |
An entry aged out. |
|
Recommended action |
No action is required. |
IP_DEL_INTERFACE_ANTIUDPFLD
|
Message text |
Delete an interface-based entry: Packets type=[STRING]; Interface=[STRING]. |
|
Variable fields |
$1: Packet type. Options include: · MPLS · IP $2: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IP_DEL_INTERFACE_ANTIUDPFLD: Delete an interface-based entry: Packets type=IP, Interface=GigabitEthernet1/0/1. |
|
Impact |
N/A |
|
Cause |
An entry aged out. |
|
Recommended action |
No action is required. |
IP_INSERT_FAILED_ANTITCPSYNFLD
|
Message text |
Insert into AVL tree failed for flow-based entry: Family=[UINT32]; DstPort=[UINT16]; VPN=[UINT16]. |
|
Variable fields |
$1: Protocol family number. $2: Destination port number. $3: VPN name. |
|
Severity level |
5 (Notification) |
|
Example |
IPFW/5/IP_INSERT_FAILED_ANTITCPSYNFLD: Insert into AVL tree failed for flow-based entry : Family=2; DstPort=80; VPN=2. |
|
Impact |
The TCP SYN Flood attack prevention feature does not take effect, and the system will continue to attempt to insert entries. |
|
Cause |
Entry conflicts occur of the system resource is insufficient. |
|
Recommended action |
No action is required. |
IP_INSERT_FAILED_ANTIUDPFLD
|
Message text |
Insert into AVL tree failed for flow-based entry: Family=[UINT32]; DstPort=[UINT16]; VPN=[UINT16]. |
|
Variable fields |
$1: Protocol family number. $2: Destination port number. $3: VPN name. |
|
Severity level |
5 (Notification) |
|
Example |
IPFW/5/IP_INSERT_FAILED_ANTIUDPFLD: Insert into AVL tree failed for flow-based entry : Family=2; DstPort=80; VPN=2. |
|
Impact |
The UDP Flood attack prevention feature does not take effect, and the system will continue to attempt to insert entries. |
|
Cause |
Entry conflicts occur of the system resource is insufficient. |
|
Recommended action |
No action is required. |
IP_NOTSUPPORT_ANTITCPSYNFLD
|
Message text |
TCP SYN flood attack prevention is not supported. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
IPFW/6/IP_NOTSUPPORT_ANTITCPSYNFLD: TCP SYN flood attack prevention is not supported. |
|
Impact |
N/A |
|
Cause |
The device does not support the TCP SYN Flood attack prevention feature. |
|
Recommended action |
No action is required. |
IP_NOTSUPPORT_ANTIUDPFLD
|
Message text |
UDP flood attack prevention is not supported. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
IPFW/6/IP_NOTSUPPORT_ANTIUDPFLD: UDP flood attack prevention is not supported. |
|
Impact |
N/A |
|
Cause |
The device does not support the UDP Flood attack prevention feature. |
|
Recommended action |
No action is required. |
IP_SETTING_FAILED_ANTITCPSYNFLD
|
Message text |
Setting entry to drive failed. Total failures=[UINT32]. |
|
Variable fields |
$1: Total number of attack entries for TCP SYN Flood prevention that failed to be issued to the driver. |
|
Severity level |
5 (Notification) |
|
Example |
IPFW/5/IP_SETTING_FAILED_ANTITCPSYNFLD: Setting entry to drive failed. Total failures = 12345. |
|
Impact |
The TCP SYN Flood attack prevention feature does not take effect, and the system will continue to issue entries to the driver. |
|
Cause |
Hardware issue. |
|
Recommended action |
No action is required. |
IP_SETTING_FAILED_ANTIUDPFLD
|
Message text |
Setting entry to drive failed. Total failures=[UINT32]. |
|
Variable fields |
$1: Total number of attack entries for UDP Flood prevention that failed to be issued to the driver. |
|
Severity level |
5 (Notification) |
|
Example |
IPFW/5/IP_SETTING_FAILED_ANTIUDPFLD: Setting entry to drive failed. Total failures = 12345. |
|
Impact |
The UDP Flood attack prevention feature does not take effect, and the system will continue to issue entries to the driver. |
|
Cause |
Hardware issue. |
|
Recommended action |
No action is required. |
IPFW_BPA_NORESOURCE
|
Message text |
Not enough resources are available on [STRING] to enable BGP policy accounting for interface [STRING]. |
|
Variable fields |
$1: Chassis ID+slot number or slot number only. $2: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
IPFW/6/IPFW_BPA_NORESOURCE: -MDC=1-Slot=2; Not enough resources are available on slot2 to enable BGP policy accounting for interface Route-Aggregation1. |
|
Impact |
The BGP policy accounting feature does not take effect. |
|
Cause |
The system fails to enable BGP policy accounting when executing the bgp-policy accounting command because of slot resource insufficiency. |
|
Recommended action |
Use the display memory-threshold and display process memory commands to collect memory alarm threshold-related information and contact Technical Support. |
IPFW_FAILED_TO_SET_MTU
|
Message text |
Failed to set MTU [UINT32] on interface [STRING] for IPv4 packets. |
|
Variable fields |
$1: MTU value. $2: Interface name. |
|
Severity level |
5 (Notification) |
|
Example |
IPFW/5/IPFW_FAILED_TO_SET_MTU: Failed to set MTU 9600 on interface GigabitEthernet6/3/8 for IPv4 packets. |
|
Impact |
N/A |
|
Cause |
The interface is configured with an invalid MTU value. |
|
Recommended action |
Modify the interface MTU. |
IPFW_FRAGPKTNUM_EXCALARM
|
Message text |
Received packets over limit alarm was detected: IfIndex=[STRING], PeerAddress=[STRING], InterfaceName=[STRING]. |
|
Variable fields |
$1: Index of the interface that received the IP fragment. $2: Destination IP address of the IP fragment. $3: Name of the interface that received the IP fragment. |
|
Severity level |
4 (Warning) |
|
Example |
IPFW/4/IPFW_FRAGPKTNUM_EXCALARM: Received packets over limit alarm was detected: IfIndex=258, PeerAddress= 192.168.0.115, InterfaceName=GigabitEthernet2/0/1. |
|
Impact |
When the number of fragments reaches the upper limit, service errors might occur. |
|
Cause |
The queue length for the currently received fragments has reached 80% of the maximum queue length. |
|
Recommended action |
Increase the MTU to reduce the number of fragments. |
IPFW_FRAGPKTNUM_EXCALARMRESUME
|
Message text |
Received fragment packets over limit alarm was resumed: IfIndex=[STRING], PeerAddress=[STRING], InterfaceName=[STRING]. |
|
Variable fields |
$1: Index of the interface that received the IP fragment. $2: Destination IP address of the IP fragment. $3: Name of the interface that received the IP fragment. |
|
Severity level |
5 (Notification) |
|
Example |
IPFW/5/IPFW_FRAGPKTNUM_EXCALARMRESUME: Received fragment packets over limit alarm was resumed: IfIndex=258, PeerAddress= 192.168.0.115, InterfaceName=GigabitEthernet2/0/1. |
|
Impact |
N/A |
|
Cause |
The queue length for the currently received fragments has decreased to 60% of the maximum queue length. |
|
Recommended action |
No action is required. |
IPFW_INFO
|
Message text |
The specified IP load sharing mode is not supported on this slot. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
IPFW/6/IPFW_INFO: -MDC=1-Slot=2; The specified IP load sharing mode is not supported on this slot. |
|
Impact |
N/A |
|
Cause |
The user-configured IP load balancing mode is not supported on the slot. |
|
Recommended action |
Identify the load balancing modes supported by the module and use the ip load-sharing mode command to specify a supported mode. |
|
Message text |
Failed to configure IP load sharing mode on this slot. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
IPFW/6/IPFW_INFO: -MDC=1-Slot=2; Failed to configure IP load sharing mode on this slot. |
|
Impact |
N/A |
|
Cause |
The user-configured IP load balancing mode failed to be configured on the slot. |
|
Recommended action |
Use the ip load-sharing mode command to configure the mode again. |
IPoE messages
This section contains IPoE messages.
IPOE_ACCOUNT_NORES
|
Message text |
Insufficient BRAS statistics or BRAS rate-limiting profile resources for IPoE. The statistics or rate-limiting function of the session(UserID = [int32]) does not take effect. |
|
Variable fields |
$1: User ID. |
|
Severity level |
4 (Warning) |
|
Example |
DIPOE/4/IPOE_ACCOUNT_NORES:Insufficient BRAS statistics or BRAS rate-limiting profile resources for IPoE. The statistics or rate-limiting function of the session(UserID = 0x38200002) does not take effect. |
|
Impact |
· Some features (such as session statistics and rate-limiting) do not take effect for a newly added IPoE session. · When a port is added to the aggregate interface of an online IPoE session, some features (such as session statistics and rate-limiting) do not take effect for the IPoE session. |
|
Cause |
· When an IPoE session is added, some features (such as session statistics and rate-limiting) do not take effect for the newly added IPoE session because of insufficient system resources. · When a port is added to the aggregate interface of an online IPoE session, some features (such as session statistics and rate-limiting) do not take effect on access users on the port because of insufficient system resources. |
|
Recommended action |
1. Use the display qos-acl resource command to view the resource usage on the specified card. 2. Use the display qos policy user-defined command to display information about user-defined general QoS policies. 3. Use the display ip policy-based-route command to display PBR policy information. 4. Use the display packet-filter global command to display ACL application information for inbound and outbound packet filtering on all physical interfaces. 5. Delete unnecessary QoS, ACL, and PBR policy configurations. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPOE_NORES
|
Message text |
Insufficient BRAS statistics or BRAS rate-limiting profile resources for IPoE. The statistics or rate-limiting function of the session(UserID = [int32]) does not take effect according to the account number. |
|
Variable fields |
$1: User ID. |
|
Severity level |
4 (Warning) |
|
Example |
DIPOE/4/IPOE_NORES:Insufficient BRAS statistics or BRAS rate-limiting profile resources for IPoE. The statistics or rate-limiting function of the session(UserID = 0x38200002) does not take effect according to the account number. |
|
System impact |
For a newly added IPoE session, the statistics and rate-limiting features do not take effect based on user ID. |
|
Cause |
For a newly added IPoE session, the statistics and rate-limiting features do not take effect based on user ID because the IPoE user statistics or rate-limiting profile resources are insufficient. |
|
Recommended action |
1. Use the display qos-acl resource command to view the resource usage on the specified card. 2. Use the display qos policy user-defined command to display information about user-defined general QoS policies. 3. Use the display ip policy-based-route command to display PBR policy information. 4. Use the display packet-filter global command to display ACL application information for inbound and outbound packet filtering on all physical interfaces. 5. Delete unnecessary QoS, ACL, and PBR policy configurations. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPOE_IPV4_HTTP_ATTACK_EXCEED_ERROR
|
Message text |
The number of anti-HTTP attack IPv4 ACLs exceeded 30 percent of the total number of IPv4 ACLs. The percentage is [STRING]. |
|
Variable fields |
$1: Percentage of the number of anti-HTTP attack IPv4 ACLs to the total number of IPv4 ACL resources of a card. |
|
Severity level |
4 (Warning) |
|
Example |
DIPOE/4/IPOE_IPV4_HTTP_ATTACK_EXCEED_ERROR: -MDC=1-Slot=4; The number of anti-HTTP attack IPv4 ACLs exceeded 30 percent of the total number of IPv4 ACLs. The percentage is 31%. |
|
Impact |
The system is not impacted. |
|
Cause |
The number of anti-HTTP attack IPv4 ACLs exceeds 30% of the total number of IPv4 ACL resources of a card. |
|
Recommended action |
1. Use the display ip subscriber http-defense blocked-destination-ip command to display entries of the destination IP addresses blocked by IPoE HTTP attack defense. 2. Use the display ip subscriber http-defense unblocked-destination-ip command to display entries of the destination IP addresses not blocked by IPoE HTTP attack defense. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPOE_IPV4_REMAIN_ACL_BELOW_ERROR
|
Message text |
The number of remaining IPv4 ACLs dropped below 20 percent of the total number of IPv4 ACLs. The percentage is [STRING]. |
|
Variable fields |
$1: Percentage of the number of remaining IPv4 ACLs to the total number of IPv4 ACL resources on a card. |
|
Severity level |
4 (Warning) |
|
Example |
DIPOE/4/IPOE_IPV4_HTTP_ATTACK_EXCEED_ERROR: -MDC=1-Slot=4; The number of remaining IPv4 ACLs dropped below 20 percent of the total number of IPv4 ACLs. The percentage is 18%. |
|
Impact |
The system is not impacted. |
|
Cause |
The percentage of the number of remaining IPv4 ACL entries is less than 20% of the total number of IPv4 ACL resources on a card. |
|
Recommended action |
1. Use the display qos-acl resource command to view the resource usage on the specified card. 2. Use the display qos policy user-defined command to display information about user-defined general QoS policies. 3. Use the display ip policy-based-route command to display PBR policy information. 4. Use the display packet-filter global command to display ACL application information for inbound and outbound packet filtering on all physical interfaces. 5. Delete unnecessary QoS, ACL, and PBR policy configurations. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPOE_IPV6_HTTP_ATTACK_EXCEED_ERROR
|
Message text |
The number of anti-HTTP attack IPv6 ACLs exceeded 30 percent of the total number of IPv6 ACLs. The percentage is [STRING]. |
|
Variable fields |
$1: Percentage of the number of anti-HTTP attack IPv6 ACLs to the total number of IPv6 ACL resources of a card. |
|
Severity level |
4 (Warning) |
|
Example |
DIPOE/4/IPOE_IPV6_HTTP_ATTACK_EXCEED_ERROR: -MDC=1-Slot=4; The number of anti-HTTP attack IPv6 ACLs exceeded 30 percent of the total number of IPv6 ACLs. The percentage is 31%. |
|
Impact |
The system is not impacted. |
|
Cause |
The number of anti-HTTP attack IPv6 ACLs exceeds 30% of the total number of IPv6 ACL resources of a card. |
|
Recommended action |
1. Use the display ip subscriber http-defense blocked-destination-ip command to display entries of the destination IP addresses blocked by IPoE HTTP attack defense. 2. Use the display ip subscriber http-defense unblocked-destination-ip command to display entries of the destination IP addresses not blocked by IPoE HTTP attack defense. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPOE_IPV6_REMAIN_ACL_BELOW_ERROR
|
Message text |
The number of remaining IPv6 ACLs dropped below 20 percent of the total number of IPv4 ACLs. The percentage is [STRING]. |
|
Variable fields |
$1: Percentage of the number of remaining IPv6 ACLs to the total number of IPv6 ACL resources on a card. |
|
Severity level |
4 (Warning) |
|
Example |
DIPOE/4/IPOE_IPV6_REMAIN_ACL_BELOW_ERROR: -MDC=1-Slot=4; The number of remaining IPv6 ACLs dropped below 20 percent of the total number of IPv4 ACLs. The percentage is 18%. |
|
Impact |
The system is not impacted. |
|
Cause |
The percentage of the number of remaining IPv6 ACL entries is less than 20% of the total number of IPv6 ACL resources on a card. |
|
Recommended action |
1. Use the display qos-acl resource command to view the resource usage on the specified card. 2. Use the display qos policy user-defined command to display information about user-defined general QoS policies. 3. Use the display ip policy-based-route command to display PBR policy information. 4. Use the display packet-filter global command to display ACL application information for inbound and outbound packet filtering on all physical interfaces. 5. Delete unnecessary QoS, ACL, and PBR policy configurations. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPOE_USERVLAN_CONFLICT
|
Message text |
The [STRING] configuration conflicts with user-vlan configuration. To avoid conflicts, do not configure both features on interface [STRING]. |
|
Variable fields |
$1: Configuration name. Options include: · ip subscriber l2vpn-leased: IPoE L2VPN-leased user configuration. · ip subscriber routed enable: Layer 3 IPoE access mode configuration. $2: Subinterface name. |
|
Severity level |
4 (Warning) |
|
Example |
DIPOE/4/IPOE_USERVLAN_CONFLICT: -MDC=1-Slot=4; The ip subscriber routed enable configuration conflicts with user-vlan configuration. To avoid conflicts, do not configure both features on interface Route-Aggregation1.2. |
|
Impact |
It might cause anomalies in the statistics and rate-limiting features (for example, statistics or rate-limiting is not performed). |
|
Cause |
An interface is configured with both the user VLAN termination feature and one of the following features, and the configurations conflict: · IPoE L2VPN-leased users (ip subscriber l2vpn-leased) · Layer 3 IPoE access mode (ip subscriber routed enable). |
|
Recommended action |
1. In interface view, use the display this command to identify whether both user VLAN termination configuration and IPoE L2VPN-leased user configuration (or Layer 3 IPoE access mode configuration) exist. If yes, delete one of them. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPoE messages
This section contains IPoE messages.
IPOE_ENABLE_ERROR
|
Message text |
Failed to [STRING] [STRING] [STRING] for the reason of [STRING] on [STRING]. |
|
Variable fields |
$1: Operation type. Options are: ¡ enable. ¡ disable. $2: Protocol stack type. Options are: ¡ IPv4. ¡ IPv6. $3: Function type. Options are: ¡ IPoE—IPoE or sending unclassified-IP packets to the CPU. ¡ IPoE set web mode—Web or Web MAC authentication. ¡ IPoE http fast reply—HTTP packet fast reply. $4: Failure reason. For more information, see Table 7. $5: Interface name. |
|
Severity level |
3 (Error) |
|
Example |
IPOE/3/IPOE_ENABLE_ERROR: Failed to enable IPv4 IPOE for the reason of not enough resources on Route-Aggregation1023. |
|
Impact |
An interface cannot provide IPoE access services if IPoE fails to be enabled on the interface. |
|
Cause |
Failed to enable or disable IPoE on an interface because resources are insufficient, this operation is not supported, or because of other unknown errors. |
|
Recommended action |
See Table 7. |
|
Reason for failure to be issued to the driver |
Description |
Recommended action |
|
this operation is not supported |
This operation is not supported |
Identify whether the interface supports IPoE. |
|
not enough resources |
Resources are insufficient |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
other unknown errors |
Other unknown errors |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPOE_HTTP_DEFENSE
|
Message text |
An HTTP/HTTPS attack was detected, and the attacked destination IP was [ IPADDR] in VPN [STRING]. |
|
Variable fields |
$1: Target IPv4 or IPv6 address of an HTTP/HTTPS attack. $2: Name of the VPN where an HTTP/HTTPS attack occurred. The value N/A indicates that the attacked occurred on the public network. |
|
Severity level |
5 (Notification) |
|
Example |
IPOE/5/IPOE_HTTP_DEFENSE: An HTTP/HTTPS attack was detected, and the attacked destination IP was 1.1.1.1 in VPN vpn1. |
|
Impact |
The authentication efficiency of users is affected, and the authentication might even fail |
|
Cause |
An attack log message was output when the HTTP/HTTPS attack reached the blocking conditions. |
|
Recommended action |
Examine the destination IP address to identify whether the HTTP/HTTPS attack was caused by a tool software products (for example, Baidu cloud) installed by a user in the network. · If yes, verify that the ip subscriber http-defense destination-ip enable action block command has been executed. · If no, take an action as follows: ¡ To limit the HTTP/HTTPS requests frequently initiated and reduce the resource usage of these massive HTTP/HTTPS packets, use the ip subscriber http-defense destination-ip enable action block command to generate blocking entries when the blocking conditions are met and block HTTP/HTTPS requests sent to the specified destination IP addresses based on the blocking entries. ¡ Blocking HTTP/HTTPS requests will affect users’ access to the specified destination IP addresses. To only detect the HTTP/HTTPS requests frequently initiated to the specified destination IP addresses rather than block them, use the ip subscriber http-defense destination-ip enable action logging command to output attack logs and generate attack defense blocking entries that are used to view blocked users but will not block attack packets when the blocking conditions are met. ¡ To collect attack defense statistics of HTTP/HTTPS packets sent by users to the specified destination IP addresses and to unconditionally push the Web authentication page to users accessing these destination IP addresses, use the ip subscriber http-defense free-destination-ip command to add these destination IP addresses to the allowlist. |
IPOE_SESSIONS_LOWER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
The IPoE session number is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower online IPoE session count alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
IPOE/4/IPOE_SESSIONS_LOWER_THRESHOLD:The IPoE session number is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of IPoE users might go offline abnormally. |
|
Cause |
The configured lower online IPoE session count alarm threshold is too large or a large number of IPoE users go offline abnormally. |
|
Recommended action |
1. Use the display current-configuration command in any view to identify whether the lower online IPoE session count alarm threshold is too large: ¡ If yes, go to step 2. ¡ If no, go to step 3. 2. Use the ip subscriber session-threshold command in system view to modify the lower online IPoE session count alarm threshold. 3. Use the display aaa abnormal-offline-record access-type ipoe command to identify whether a large number of IPoE users go offline abnormally: ¡ If yes, take an action according to the offline reason. ¡ If no, use the display aaa abnormal-offline-record access-type ipoe command to identify the offline reason, and take an action according to the offline reason. 4. If the issue persists, collect the following information and then contact Technical Support for help: ¡ Results of each step. ¡ Alarm information, log messages, and configuration data. |
IPOE_SESSIONS_LOWER_THRESHOLD (vBRAS-CPs)
|
Message text |
The IPoE session number on slot [INT32] is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Lower online IPoE session count alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
IPOE/4/IPOE_SESSIONS_LOWER_THRESHOLD:The IPoE session number on slot 97 is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of IPoE users might go offline abnormally. |
|
Cause |
The configured lower online IPoE session count alarm threshold is too large or a large number of IPoE users go offline abnormally. |
|
Recommended action |
1. Use the display current-configuration command in any view to identify whether the lower online IPoE session count alarm threshold is too large: ¡ If yes, go to step 2. ¡ If no, go to step 3. 2. Use the ip subscriber session-threshold command in system view to modify the lower online IPoE session count alarm threshold. 3. Use the display aaa abnormal-offline-record access-type ipoe command to identify whether a large number of IPoE users go offline abnormally: ¡ If yes, take an action according to the offline reason. ¡ If no, use the display aaa abnormal-offline-record access-type ipoe command to identify the offline reason, and take an action according to the offline reason. 4. If the issue persists, collect the following information and then contact Technical Support for help: ¡ Results of each step. ¡ Alarm information, log messages, and configuration data. |
IPOE_SESSIONS_LOWER_RECOVER (non-vBRAS-CPs)
|
Message text |
The IPoE session number has recovered to normal state from below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower online IPoE session count alarm threshold. |
|
Severity level |
5 (Notification) |
|
Example |
IPOE/5/IPOE_SESSIONS_LOWER_RECOVER:The IPoE session number has recovered to normal state from below the lower warning threshold (LowerThreshold=20). |
|
Impact |
No negative impact on the system. |
|
Cause |
IPoE users come online. |
|
Recommended action |
No action is required. |
IPOE_SESSIONS_LOWER_RECOVER (vBRAS-CPs)
|
Message text |
The IPoE session number on slot [INT32] has recovered to normal state from below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Lower online IPoE session count alarm threshold. |
|
Severity level |
5 (Notification) |
|
Example |
IPOE/5/IPOE_SESSIONS_LOWER_RECOVER:The IPoE session number on slot 97 has recovered to normal state from below the lower warning threshold (LowerThreshold=20). |
|
Impact |
No negative impact on the system. |
|
Cause |
IPoE users come online. |
|
Recommended action |
No action is required. |
IPOE_SESSIONS_UPPER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
The IPoE session number is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper online IPoE session count alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
IPOE/4/IPOE_SESSIONS_UPPER_THRESHOLD:The IPoE session number is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
IPoE users might fail to come online. |
|
Cause |
The configured upper online IPoE session count alarm threshold is too small or a large number of IPoE users come online. |
|
Recommended action |
1. Use the display current-configuration command in any view to identify whether the upper online IPoE session count alarm threshold is too small: ¡ If yes, go to step 2. ¡ If no, go to step 3. 2. Use the ip subscriber session-threshold command in system view to modify the upper online IPoE session count alarm threshold. 3. If the issue persists, collect the following information and then contact Technical Support for help: ¡ Results of each step. ¡ Alarm information, log messages, and configuration data. |
IPOE_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
|
Message text |
The IPoE session number on slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Upper online IPoE session count alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
IPOE/4/IPOE_SESSIONS_UPPER_THRESHOLD:The IPoE session number on slot 97 is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
IPoE users might fail to come online. |
|
Cause |
The configured upper online IPoE session count alarm threshold is too small or a large number of IPoE users come online. |
|
Recommended action |
1. Use the display current-configuration command in any view to identify whether the upper online IPoE session count alarm threshold is too small: ¡ If yes, go to step 2. ¡ If no, go to step 3. 2. Use the ip subscriber session-threshold command in system view to modify the upper online IPoE session count alarm threshold. 3. If the issue persists, collect the following information and then contact Technical Support for help: ¡ Results of each step. ¡ Alarm information, log messages, and configuration data. |
IPOE_SESSIONS_UPPER_RECOVER (non-vBRAS-CPs)
|
Message text |
The IPoE session number has recovered to normal state from above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper online IPoE session count alarm threshold. |
|
Severity level |
5 (Notification) |
|
Example |
IPOE/5/IPOE_SESSIONS_UPPER_RECOVER: The IPoE session number has recovered to normal state from above the upper warning threshold (UpperThreshold=20). |
|
Impact |
No negative impact on the system. |
|
Cause |
Some IPoE users go offline. |
|
Recommended action |
No action is required. |
IPOE_SESSIONS_UPPER_RECOVER (vBRAS-CPs)
|
Message text |
The IPoE session number on slot [INT32] has recovered to normal state from above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Upper online IPoE session count alarm threshold. |
|
Severity level |
5 (Notification) |
|
Example |
IPOE/5/IPOE_SESSIONS_UPPER_RECOVER: The IPoE session number on slot 97 has recovered to normal state from above the upper warning threshold (UpperThreshold =20). |
|
Impact |
No negative impact on the system. |
|
Cause |
Some IPoE users go offline. |
|
Recommended action |
No action is required. |
IPOE_SESSION_CONFLICT
|
Message text |
Forced the user (IPAddr=[STRING], MACAddr=[STRING]) on [STRING] to go offline because the same user came online on [STRING] |
|
Variable fields |
$1: IP address. $2: MAC address. $3: Interface name. $4: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
IPOE/6/IPOE_SESSION_CONFLICT: Forced the user (IPAddr=1.1.1.2, MACAddr=1-2-3) on Route-Aggregation1023 to go offline because the same user came online on Route-Aggregation1024. |
|
Impact |
The old user was forced to go offline. |
|
Cause |
When a user comes online through an interface, the device will force the user with the same IP address and MAC address as the online user to go offline. |
|
Recommended action |
No action is required. |
IPSEC messages
This section contains IPsec messages.
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 (Warning) |
|
Example |
IPSEC/4/IPSEC_FAILED_ADD_FLOW_TABLE: Failed to add flow-table due to no enough resource. |
|
Impact |
The current and subsequent IPsec SAs cannot be established. |
|
Cause |
Not enough hardware resources. |
|
Recommended action |
If the failure is caused by not enough hardware resources, contact Technical Support for help. |
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 of the packet. $2: Destination IP address of the packet. $3: Security Parameter Index (SPI). $4: Reason for dropping the 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 (Informational) |
|
Example |
IPSEC/6/IPSEC_PACKET_DISCARDED: IPsec packet discarded, Src IP:1.1.1.2, Dst IP:1.1.1.4, SPI:1002, SN:0, Cause:AH authentication failed. |
|
Impact |
No negative impact on the system. |
|
Cause |
An IPsec packet is dropped. |
|
Recommended action |
No action is required. |
IPSEC_SA_ESTABLISH
|
Message text |
Established IPsec SA. The SA’s source address is [STRING], destination address is [STRING], protocol is [STRING], and SPI is [UINT32]. |
|
Variable fields |
$1: Source IP address of the IPsec SA. $2: Destination IP address of the IPsec SA. $3: Security protocol used by the IPsec SA. $4: SPI of the IPsec SA. |
|
Severity level |
6 (Informational) |
|
Example |
IPSEC/6/IPSEC_SA_ESTABLISH: Established IPsec SA. The SA’s source address is 1.1.1.1, destination address is 2.2.2.2, protocol is AH, and SPI is 2435. |
|
Impact |
No negative impact on the system. |
|
Cause |
An IPsec SA is established. |
|
Recommended action |
No action is required. |
IPSEC_SA_ESTABLISH_FAIL
|
Message text |
Failed to establish IPsec SA for the reason of [STRING]. The SA’s source address is [STRING], and its destination address is [STRING]. |
|
Variable fields |
$1: Reason for the IPsec SA establishment failure: · Tunnel establishment failure. · Incomplete configuration. · Unavailable transform set. · 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 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. $3: Source IP address. $4: Destination IP address. |
|
Severity level |
6 (Informational) |
|
Example |
IPSEC/6/IPSEC_SA_ESTABLISH_FAIL: Failed to establish IPsec SA for the reason of creating tunnel failure. The SA’s source address is 1.1.1.1, and its destination address is 2.2.2.2. |
|
Impact |
The IPsec SA failed to be established and therefore the IPsec tunnel cannot be established to protect packets. |
|
Cause |
· The IPsec transform set parameters, IPsec authentication and encryption algorithms, and IPsec encapsulation modes are inconsistent between the two ends. · The IPsec policy settings are inconsistent between the two ends. · The ACLs used by the two ends are not mirror ACLs. · The physical link status is poor or the peer network is unreachable. |
|
Recommended action |
· Verify that the two ends use the same IPsec transform set parameters, IPsec authentication and encryption algorithms, and IPsec encapsulation mode. · Verify that the two ends use the same IPsec policy configuration. · Verify that the ACLs used by the two ends are mirror ACLs. · Troubleshoot network issues to make sure the physical link status is good and the peer network is reachable. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPSEC_SA_INITINATION
|
Message text |
Began to establish IPsec SA. The SA’s source address is [STRING], and its destination address is [STRING]. |
|
Variable fields |
$1: Source address of the IPsec SA. $2: Destination address of the IPsec SA. |
|
Severity level |
6 (Informational) |
|
Example |
IPSEC/6/IPSEC_SA_INITINATION: Began to establish IPsec SA. The SA’s source address is 1.1.1.1, and its destination address is 2.2.2.2. |
|
Impact |
No negative impact on the system. |
|
Cause |
An IPsec SA is to be established. |
|
Recommended action |
No action is required. |
IPSEC_SA_TERMINATE
|
Message text |
The IPsec SA was deleted for the reason of [STRING]. The SA’s source address is [STRING], destination address is [STRING], protocol is [STRING], and SPI is [UINT32]. |
|
Variable fields |
$1: Reason for the IPsec SA removal: · SA idle timeout. · The reset command was executed. $2: Source IP address. $3: Destination IP address. $4: Security protocol used. $5: SPI. |
|
Severity level |
6 (Informational) |
|
Example |
IPSEC/6/IPSEC_SA_TERMINATE: The IPsec SA was deleted for the reason of SA idle timeout. The SA’s source address is 1.1.1.1, destination address is 2.2.2.2, protocol is ESP, and SPI is 34563. |
|
Impact |
An IPsec SA was deleted, and the IPsec service that the SA carried was interrupted. |
|
Cause |
An IPsec SA was deleted. |
|
Recommended action |
· If an SA was deleted due to reasons listed in this log, it will be renegotiated and established normally. In this case, no action is required. · If an SA was deleted due to other reasons, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
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 [STRING]) 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 N/A. $4: Interface name. If you do not specify an interface, this field displays N/A. $5: Failure reasons. Available options include: ¡ Feature not supported. ¡ Not enough resources. ¡ Unknown error. |
|
Severity level |
6 (Informational) |
|
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. Not enough resources. |
|
Impact |
The system cannot use the IPSG binding to filter packets. |
|
Cause |
This message is sent in the following conditions: · The IPSG feature is not supported. · Hardware resources are insufficient, · An unknown error occurs. |
|
Recommended action |
· Identify whether the device supports the IPSG feature. If IPSG is not supported, output of this message is normal. No action is required. · Disable unnecessary services to release hardware resources when the failure is caused by insufficient hardware resources. · If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPSG_DELENTRY_ERROR
|
Message text |
Failed to delete an IP source guard binding (IP [STRING], MAC [STRING], and VLAN [STRING]) 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 N/A. $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 (Informational) |
|
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. |
|
Impact |
The system can still use this binding to filter packets. |
|
Cause |
This message is sent in the following conditions: · The IPSG feature is not supported. · An unknown error occurs. |
|
Recommended action |
1. Identify whether the device supports the IPSG feature. If IPSG is not supported, output of this message is normal. No action is required. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
IRDP/6/IRDP_EXCEED_ADVADDR_LIMIT: The number of advertisement addresses on interface GigabitEthernet1/0/1 exceeded the limit 255. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of addresses to be advertised on an interface exceeds the upper limit. |
|
Recommended action |
Remove unused secondary IP addresses on the interface. |
IRF
This section contains IRF messages.
IRF_DISCOVER_FAIL
|
Message text |
The [STRING] channel with link ID [UINT32] detected having failed in the link discovery phase: interface=[STRING], latest local Tx request seq=[UINT32], latest local Rx reply seq=[UINT32]. |
|
Variable fields |
$1: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $2: Link ID. $3: Interface name. $4: Sequence number of the most recently sent detection request packet. $5: Sequence number of the most recently received detection reply packet. |
|
Severity level |
4 (Warning) |
|
Example |
IRF/4/IRF_DISCOVER_FAIL: The control channel with link ID 1 detected having failed in the link discovery phase: interface=GigabitEthernet1/0/1, latest local Tx request seq=100, latest local Rx reply seq=94. |
|
Impact |
|
|
Cause |
In the link discovery phase, the system determined that an IRF link has failed when the detection timer expired because it had not received detection reply packets from the remote end. This issue occurred possibly because: · The remote port was initializing. · IRF connections were incorrect. |
|
Recommended action |
If this issue occurs because the remote port is initializing in the IRF fabric establishment phase, keep observing. If a IRF_DISCOVER_FAIL_PERSIST log message is received later, resolve the issue as described in "IRF_DISCOVER_FAIL_PERSIST.' |
IRF_DISCOVER_FAIL_PERSIST
|
Message text |
[UINT32] consecutive link detection failures occurred on the [STRING] channel with link ID [UINT32] in the link discovery phase: interface=[STRING], latest local Tx request seq=[UINT32], latest local Rx reply seq=[UINT32]. |
|
Variable fields |
$1: Number of consecutive link detection failures. $2: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $3: Link ID. $4: Interface name. $5: Sequence number of the most recently sent detection request packet. $6: Sequence number of the most recently received detection reply packet. |
|
Severity level |
4 (Warning) |
|
Example |
IRF/4/IRF_DISCOVER_FAIL_PERSIST: 3 consecutive link detection failures occurred on the data channel with link ID 1 in the link discovery phase: interface=GigabitEthernet1/2/0, latest local Tx request seq=120, latest local Rx reply seq=94. |
|
Impact |
The device cannot join the IRF fabric. |
|
Cause |
In the link discovery phase, consecutive link detection failures occurred. The IRF link might have failed. |
|
Recommended action |
Log in to the local and remote devices separately, execute the display irf link command to view the status of the IRF physical ports, and then take actions accordingly: · If the port status is Down, the related physical links fail, and you can take the following actions: a. Verify that the physical connections are correct. The local control-channel interface should be connected to the remote control-channel interface. Similarly, the local data-channel interface should be connected to the remote data-channel interface. When the physical connections are correct, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. b. 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 remote member device. Then, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. c. Replace the network cables. After replacing the network cables, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. · If the port status is ADM, the port is shut down. You can execute the undo shutdown command on the port to bring it up. If the issue persists, collect configuration data and alarm information, and then contact Technical Support for help. |
IRF_DISCOVER_SUCCESS
|
Message text |
The [STRING] channel with link ID [UINT32] detected up in the link discovery phase: interface=[STRING], latest local Tx request seq=[UINT32], latest local Rx reply seq=[UINT32]. |
|
Variable fields |
$1: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $2: Link ID. $3: Interface name. $4: Sequence number of the most recent sent detection request packet. $5: Sequence number of the most recent received detection reply packet. |
|
Severity level |
6 (Informational) |
|
Example |
IRF/6/IRF_DISCOVER_SUCCESS: The control channel with link ID 2 detected up in the link discovery phase: interface=GigabitEthernet1/2/0, latest local Tx request seq=120, latest local Rx reply seq=120. |
|
Impact |
No negative impact on the system. |
|
Cause |
In the link discovery phase, the system determined that an IRF link has been up when it received detection reply packets from the remote end. |
|
Recommended action |
No action is required. |
IRF_KEEPALIVE_FAIL
|
Message text |
The [STRING] channel with link ID [UINT32] detected having failed in the link keepalive phase: interface=[STRING], latest local Tx request seq=[UINT32], latest local Rx reply seq=[UINT32]. |
|
Variable fields |
$1: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $2: Link ID. $3: Interface name. $4: Sequence number of the most recently sent detection request packet. $5: Sequence number of the most recently received detection reply packet. |
|
Severity level |
4 (Warning) |
|
Example |
IRF/4/IRF_KEEPALIVE_FAIL: The control channel with link ID 1 detected having failed in the link keepalive phase: interface=GigabitEthernet1/2/0, latest local Tx request seq=100, latest local Rx reply seq=94. |
|
Impact |
The IRF fabric might be split. |
|
Cause |
In the link keepalive phase, the system determined that an IRF link has failed when the detection timer expired because it had not received detection reply packets from the remote end. |
|
Recommended action |
Log in to the local and remote devices separately, execute the display irf link command to view the related IRF physical ports and their status, and then take actions accordingly: · If the port status is Down, the related physical links fail, and you can take the following actions: d. Verify that the physical connections are correct. The local control-channel interface should be connected to the remote control-channel interface. Similarly, the local data-channel interface should be connected to the remote data-channel interface. When the physical connections are correct, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. e. 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 remote member device. Then, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. f. Replace the network cables. After replacing the network cables, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. · If the port status is ADM, the port is shut down. You can execute the undo shutdown command on the port to bring it up. · If the port status is Blocked, the related link is blocked. If an IRF member device is in Blocked state, it will be isolated and cannot join any IRF fabric. To cancel the Blocked state, execute the irf member stack enable command on that IRF member device. · If the port status is --, the IRF port on the device is not bound to any IRF physical ports. You can execute the port group interface command in IRF port view to bind the IRF port with IRF physical ports. If the issue persists, collect configuration data and alarm information, and then contact Technical Support for help. |
IRF_KEEPALIVE_SUCCESS
|
Message text |
The [STRING] channel with link ID [UINT32] detected up in the link keepalive phase: interface=[STRING], latest local Tx request seq=[UINT32], latest local Rx reply seq=[UINT32]. |
|
Variable fields |
$1: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $2: Link ID. $3: Interface name. $4: Sequence number of the most recently sent detection request packet. $5: Sequence number of the most recently received detection reply packet. |
|
Severity level |
6 (Informational) |
|
Example |
IRF/6/IRF_KEEPALIVE_SUCCESS: The control channel with link ID 2 detected up in the link keepalive phase: interface=GigabitEthernet1/2/0, latest local Tx request seq=120, latest local Rx reply seq=120. |
|
Impact |
No negative impact on the system. |
|
Cause |
In the link keepalive phase, the system determined that an IRF link has been up when it received detection reply packets from the remote end. |
|
Recommended action |
No action is required. |
IRF_LINK_BLOCK
|
Message text |
IRF port went blocked. |
|
Variable fields |
N/A |
|
Severity level |
2 (Critical) |
|
Example |
IRF/2/IRF_LINK_BLOCK: IRF port went blocked. |
|
Impact |
The device cannot form an IRF fabric with other devices. |
|
Cause |
This message is generated on a device when it attempts to join an IRF fabric, but its member ID conflicts with the member ID of an existing member device in the IRF fabric. A blocked IRF port cannot forward data packets, but it can send and receive IRF protocol packets. |
|
Recommended action |
To resolve the issue: 1. Log in to the device, and then execute the display irf command to obtain the member ID of the device. If the member ID of the device is the same as that of an existing IRF member device, use the irf member renumber command to assign a unique member ID to the device, and then reboot the device. 2. If the issue persists, collect alarm information and configuration data, and then contact Technical Support for help. |
IRF_LINK_DOWN
|
Message text |
IRF port went down. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
IRF/3/IRF_LINK_DOWN: IRF port went down. |
|
Impact |
The device will leave the IRF fabric. |
|
Cause |
All physical interfaces bound to the IRF port went 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 remote member device to identify whether the remote 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 remote 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. If the member devices are connected in daisy-chain topology, make sure the local control links are connected to the peer control links and the local data links are connected to the peer data links. If the member devices are connected in star topology, make sure the local control links have Layer 2 connectivity to the peer control links and the local data links have Layer 2 connectivity to the peer data links. 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 remote 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 information and configuration data, and then contact Technical Support for help. |
IRF_LINK_SWITCH
|
Message text |
The [STRING] channel switched to link [UINT32]: interface=[STRING], latest local Tx request seq=[UINT32], latest local Rx reply seq=[UINT32]. |
|
Variable fields |
$1: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $2: Link ID. $3: Interface name. $4: Sequence number of the most recently sent detection request packet. $5: Sequence number of the most recently received detection reply packet. |
|
Severity level |
4 (Warning) |
|
Example |
IRF/4/IRF_LINK_SWITCH: The control channel switched to link 2: interface=GigabitEthernet1/2/0, latest local Tx request seq=120, latest local Rx reply seq=120. |
|
Impact |
No negative impact on the system. |
|
Cause |
The original link used by the control channel failed, and the backup link was used. |
|
Recommended action |
No action is required. |
IRF_LINK_UP
|
Message text |
IRF port came up. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
IRF/6/IRF_LINK_UP: IRF port came up. |
|
Impact |
This issue leads to IRF merge. |
|
Cause |
An IRF link recovered from failure. |
|
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 (Warning) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
A member ID conflict was detected. Another device in the same broadcast domain has the same member ID as this device. |
|
Recommended action |
To resolve this issue: 1. Retain the member ID of the device that has joined the IRF fabric. 2. Log in to the other device and use the irf member renumber command to change the member ID of that device to a member ID not used in the IRF fabric. |
IRF_MERGE
|
Message text |
IRF merge occurred. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IRF/4/IRF_MERGE: IRF merge occurred. |
|
Impact |
No negative impact on the system. |
|
Cause |
An IRF link came up. |
|
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 (Warning) |
|
Example |
IRF/4/IRF_MERGE_NEED_REBOOT: IRF merge occurred. This IRF system needs a reboot. |
|
Impact |
The local IRF system cannot provide services during reboot. |
|
Cause |
An IRF link came up, which led to IRF merge. In addition, the local IRF system failed in the master election. |
|
Recommended action |
Reboot the local IRF system. After it reboots, all its member devices join the IRF system that has won the master election as standby devices. |
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 (Notification) |
|
Example |
IRF/5/IRF_MERGE_NOT_NEED_REBOOT: IRF merge occurred. This IRF system does not need to reboot. |
|
Impact |
No negative impact on the system. |
|
Cause |
An IRF link came up, which led to IRF merge. In addition, the local IRF system succeeded in the master election. |
|
Recommended action |
No action is required. |
IRF_RECEIVE_THIRD_PACKET
|
Message text |
The [STRING] channel with link ID [UINT32] received a [STRING] packet from a third device: interface=[STRING], seq=[UINT32]. |
|
Variable fields |
$1: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $2: Link ID. $3: Detection packet type: ¡ Discover_Request. ¡ Discover_Reply. ¡ LinkSelect_Request. ¡ LinkSelect_Reply. ¡ Keepalive_Request. ¡ Keepalive_Reply. $4: Interface name. $5: Sequence number of the packet. |
|
Severity level |
4 (Warning) |
|
Example |
IRF/4/IRF_RECEIVE_THIRD_PACKET: The control channel with link ID 2 received a Discover_Request packet from a third device: interface=GigabitEthernet1/2/0, seq=120. |
|
Impact |
No negative impact on the system. |
|
Cause |
The current device series only supports two-member IRF fabrics. This message is generated when an IRF fabric receives a detection packet from a third device. |
|
Recommended action |
Check the network connection. |
IRF_SELECT_FAIL
|
Message text |
The [STRING] channel with link ID [UINT32] detected having failed in the link selection phase: interface=[STRING], latest local Tx request seq=[UINT32], latest local Rx reply seq=[UINT32]. |
|
Variable fields |
$1: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $2: Link ID. $3: Interface name. $4: Sequence number of the most recently sent detection request packet. $5: Sequence number of the most recently received detection reply packet. |
|
Severity level |
4 (Warning) |
|
Example |
IRF/4/IRF_SELECT_FAIL: The control channel with link ID 1 detected having failed in the link selection phase: interface=GigabitEthernet1/0/1, latest local Tx request seq=100, latest local Rx reply seq=94. |
|
Impact |
The device cannot join the IRF fabric. |
|
Cause |
In the link selection phase, the system determined that an IRF link has failed when the detection timer expired because it had not received detection reply packets from the remote end. This issue occurred possibly because: · The remote port was initializing. · IRF connections were incorrect. |
|
Recommended action |
If this issue occurs because the remote port is initializing in the IRF fabric establishment phase, keep observing. If a IRF_SELECT_FAIL log message is received repeatedly later, log in to the local device, execute the display irf link command to view the status of the IRF physical ports, and then take actions accordingly: · If the port status is Down, the related physical links fail, and you can take the following actions: a. Verify that the physical connections are correct. The local control-channel interface should be connected to the remote control-channel interface. Similarly, the local data-channel interface should be connected to the remote data-channel interface. When the physical connections are correct, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. b. 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 remote member device. Then, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. c. Replace the network cables. After replacing the network cables, execute the display irf link command again. If the port status is Up, the issue has been resolved. If the port status is not Up, continue with the troubleshooting. · If the port status is ADM, the port is shut down. You can execute the undo shutdown command on the port to bring it up. If the issue persists, collect configuration data and alarm information, and then contact Technical Support for help. |
IRF_SELECT_SUCCESS
|
Message text |
The [STRING] channel with link ID [UINT32] detected up and set to the [STRING] state in the link selection phase: interface=[STRING], latest local Tx request seq=[UINT32], latest local Rx reply seq=[UINT32]. |
|
Variable fields |
$1: Channel type: ¡ control&data—Hybrid channel. ¡ control—Control channel. ¡ data—Data channel. $2: Link ID. $3: Link state: ¡ selected—The link is selected to forward traffic. ¡ unselected—The link is a backup of the selected link. $4: Interface name. $5: Sequence number of the most recently sent detection request packet. $6: Sequence number of the most recently received detection reply packet. |
|
Severity level |
6 (Informational) |
|
Example |
IRF/6/IRF_SELECT_SUCCESS: The control channel with link ID 2 detected up and set to the selected state in the link selection phase: interface=GigabitEthernet1/2/0, latest local Tx request seq=120, latest local Rx reply seq=120. |
|
Impact |
No negative impact on the system. |
|
Cause |
On receipt of a detection reply packet from the remote end of an IRF channel, the system determined that the channel has been up and set its link state to Selected or Unselected. |
|
Recommended action |
No action is required. |
ISIS messages
This section contains IS-IS messages.
ISIS_ADJSID_CONFLICT
|
Message text |
IS-IS [UINT16] failed to allocate adjacent SID [UINT32] on interface [STRING], reason: SID conflicted. |
|
Variable fields |
$1: IS-IS process ID. $2: Adjacency SID. $3: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_ADJSID_CONFLICT: IS-IS 1 failed to allocate adjacent SID 15010 on interface Route-Aggregation1, reason: SID conflicted. |
|
Impact |
The system will only select one SID, ignoring any identical SIDs released by other devices. |
|
Cause |
Adjacency SID conflicts occurred. |
|
Recommended action |
Execute the isis adjacency-sid command on the source device to edit the adjacency SID assigned to an IS-IS adjacency. Before executing the isis adjacency-sid command, execute the display mpls label command to display MPLS label usage information. Make sure that all labels in the specified range are idle. |
ISIS_AUTH_FAILURE
|
Message text |
ISIS [UINT16] dropped a [STRING] PDU on interface [STRING] due to authentication setting inconsistency. (isisPDULen=[UINT16], isisPDUFragment=[STRING]) |
|
Variable fields |
$1: IS-IS process ID. $2: IS level. Available values include Level-1, Level-2, and Level-1-2. $3: Interface name. $4: PDU length. $5: First 32 bytes of the PDU header in hexadecimal notation. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_AUTH_FAILURE: ISIS 1 dropped a Level-1 PDU on interface GE1/0/1 due to authentication setting inconsistency. (isisPDULen=179, isisPDUFragment=00 b3 02 e0 00 00 00 00 00 11 00 00 00 00 00 64 f2 2b 03 01 02 01 00 81 02 cc 8e e8 20 00 11 00) |
|
Impact |
· The system will fail to create an IS-IS neighbor if the hello packet authentication fails. · If LSP or SNP authentication fails, the device cannot perform LSDB synchronization, but can still create an IS-IS neighbor . |
|
Cause |
Authentication is configured on an interface or process on the local device. Make sure the peer device and the local device use the same authentication type, but have different authentication algorithms, keys, or key IDs. |
|
Recommended action |
1. Identify the IS-IS process ID of the received packet based on log information, and identify the type of the packet as well as the interface that received the packet. Check the isisPDUFragment field (hexadecimal notation) in log information to find the system ID of the source device that sent the packet and packet type. ¡ If the packet is a hello packet, go to step 2. ¡ If the packet is an LSP or SNP packet, go to step 4. 2. Identify the source device based on the system ID, and then execute the display isis peer command to obtain the interface that sends this packet. 3. In interface view of the source device and local device, execute the isis authentication-mode command to configure the same authentication mode and authentication key. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 4. 4. Execute the display current-configuration configuration isis command on the source device to identify whether the IS-IS process is configured with an area or routing domain authentication mode. ¡ If an area or routing domain authentication mode is configured, go to step 5. ¡ If no area or routing domain authentication mode is configured, go to step 6. 5. In IS-IS view of the source device and local device, execute the area-authentication-mode or domain-authentication-mode command to configure the same authentication mode and authentication key. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 6. 6. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ISIS_AUTH_TYPE_FAILURE
|
Message text |
ISIS [UINT16] dropped a [STRING] PDU on interface [STRING] due to authentication type inconsistency. (isisPDULen=[UINT16], isisPDUFragment=[STRING]) |
|
Variable fields |
$1: IS-IS process ID. $2: Interface name. $3: IS level. Available values include Level-1, Level-2, and Level-1-2. $4: PDU length. $5: First 32 bytes of the PDU header in hexadecimal notation. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_AUTH_FAILURE: ISIS 1 dropped a Level-1 PDU on interface GE1/0/1 due to authentication type inconsistency. (isisPDULen=179, isisPDUFragment=00 b3 02 e0 00 00 00 00 00 11 00 00 00 00 00 64 f2 2b 03 01 02 01 00 81 02 cc 8e e8 20 00 11 00) |
|
Impact |
· The system will fail to create an IS-IS neighbor if the hello packet authentication fails.. · If LSP or SNP authentication fails, the device cannot perform LSDB synchronization, but can still create an IS-IS neighbor. |
|
Cause |
Authentication is configured on an interface or process on the local device. However, the peer device is either not configured with authentication or is configured with a different authentication type from the local device. |
|
Recommended action |
1. Identify the IS-IS process ID of the received packet based on log information, and identify the type of the packet as well as the interface that received the packet. Check the isisPDUFragment field (hexadecimal notation) in log information to find the system ID of the source device that sent the packet and packet type. ¡ If the packet is a hello packet, go to step 2. ¡ If the packet is an LSP or SNP packet, go to step 4. 2. Identify the source device based on the system ID, and then execute the display isis peer command to obtain the interface that sends this packet. Enter the view of the obtained interface and execute the display this command to identify whether the interface is configured an authentication mode and compares the authentication mode with that on the interface of the local device. ¡ If the two authentication modes are different, go to step 3. ¡ If the two authentication modes are the same, go to step 6. 3. In interface view of the source device, execute the isis authentication-mode command to configure the same authentication mode as the local device. Make sure the source device and the local device have the same authentication key. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 4. 4. Execute the display current-configuration configuration isis command on the source device to identify whether the IS-IS process is configured with an area or routing domain authentication mode and compare them with the local device. ¡ If the authentication modes are the same, go to step 6. ¡ If the authentication modes are different, go to step 5. 5. In IS-IS view of the source device, execute the area-authentication-mode or domain-authentication-mode command to configure the same authentication mode as the local device. Make sure the source device and the local device have the same authentication key. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 6. 6. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ISIS_BFRPREFIX_CONFLICT
|
Message text |
IS-IS [UINT16], [STRING] BFR-prefix [STRING] might be assigned to multiple devices: system IDs=[STRING]. |
|
Variable fields |
$1: IS-IS process ID. $2: IS level. Available values include Level-1 and Level-2. $3: BIER forwarding router prefix. $4: System IDs on which the conflict occurs. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_BFRPREFIX_CONFLICT: -MDC=1; IS-IS 1, Level-1 BFR-prefix 3333::3 might be assigned to multiple devices: system IDs=0000.0000.0003, 0000.0000.0004. |
|
Impact |
A BIER forwarding error might occur. |
|
Cause |
The BIER forwarding router prefixes for non-level penetration might conflict. |
|
Recommended action |
1. Identify the conflicting system ID based on the system IDs in log information. 2. Identify the devices based on the system IDs and execute the display current-configuration to check the configuration by the bfr-prefix command on these devices. ¡ If different devices are configured with the same BFR prefix, reconfigure the BFR prefix. Then, identify whether the device still generates this message: If the device does not generate this message, the issue is resolved. If the device still generates this message, go to step 3. ¡ If different devices are configured with different BFR prefixes, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ISIS_ID_LEN_MISMATCH
|
Message text |
ISIS [UINT16] dropped a [STRING] PDU on interface [STRING] due to system ID length inconsistency. (isisPDULen=[UINT16], isisPDUIDLen=[UINT16], isisPDUFragment=[STRING]) |
|
Variable fields |
$1: IS-IS process ID. $2: IS level. Available values include Level-1, Level-2, and Level-1-2. $3: Interface name. $4: PDU length. $5: ID length. $6: First 32 bytes of the PDU header in hexadecimal notation. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_ID_LEN_MISMATCH: ISIS 1 dropped a Level-1 PDU on interface GE1/0/1 due to system ID length inconsistency. (isisPDULen=179, isisPDUIDLen=10, isisPDUFragment=00 b3 02 e0 00 00 00 00 00 11 00 00 00 00 00 64 f2 2b 03 01 02 01 00 81 02 cc 8e e8 20 00 11 00) |
|
Impact |
· Route flapping might occur. · If this message is generated due to device interconnection issues, the device cannot establish the neighbor relationship between another device or cannot learn routes from each other. |
|
Cause |
The system ID length in the header of the received PDU (including all types of IS-IS messages) does not match the system ID length of this device. |
|
Recommended action |
1. Check the isisPDUFragment field (hexadecimal notation) in the device log to find the system ID of the source device that sent the PDU. ¡ If the length of the system ID of the source device is not 0 or 6, go to step 2. ¡ If the length of the system ID of the source device is 0 or 6, go to step 3. 2. Change the system ID length of the source device to 6. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ISIS_LOCAL_SYS_IS_DIS
|
Message text |
ISIS [UINT16] interface [STRING] became the temporary DIS when receiving hello packet with RR bit set. |
|
Variable fields |
$1: IS-IS process ID. $2: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
ISIS/6/ISIS_LOCAL_SYS_IS_DIS: ISIS 1 interface GE1/0/1 became the temporary DIS when receiving hello packet with RR bit set. |
|
Impact |
No negative impact on the system. |
|
Cause |
The broadcast interface became the temporary DIS after receiving a hello packet with the RR bit of Restart TLV set. |
|
Recommended action |
No action is required. |
ISIS_LSDB_OVERLOAD
|
Message text |
The overload state of IS-IS [UINT16] [STRING] LSDB changed to [STRING]. |
|
Variable fields |
$1: IS-IS process ID. $2: IS level. Available values include Level-21, Level-2, and Level-1-2. $3: Overload state. Available values include Normal and Overloaded. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_LSDB_OVERLOAD: The overload state of IS-IS 1 Level-1 LSDB changed to Normal. |
|
Impact |
· If this message is generated due to a change in the LSDB overload bit state, route selection of neighbors is affected. · If this message is generated due to a memory issue, the IS-IS database is untrustable. |
|
Cause |
· The set-overload or undo set-overload command is executed in IS-IS view. · Memory application failed. |
|
Recommended action |
1. Execute the display this command in IS-IS view to identify whether the set-overload command is executed in the process. ¡ If the set-overload command is executed, no action is required. ¡ If the set-overload command is not executed, go to step 2. 2. Execute the display history-command command in IS-IS view to identify whether the undo set-overload command is executed in the process. ¡ If the undo set-overload command is executed, no action is required. ¡ If the undo set-overload command is not executed, go to step 3. 3. Execute the display memory command to view memory usage on the device. ¡ If the device has high memory usage, go to step 4. ¡ If the device does not have high memory usage, go to step 5. 4. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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. The IS type can be Level-1 or Level-2. $3: LSP ID. $4: LSP sequence number. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_LSP_CONFLICT: IS-IS 1, Level-2 LSP, LSPID=0000.0000.2001.00-00, SeqNum=0x000006a0, system ID conflict might exist. |
|
LSP updates occur frequently, which causes route flapping. |
|
|
Cause |
System ID conflict might exist. |
|
Recommended action |
1. Verify that each device in the topology uses a unique system ID. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
ISIS_LSP_TOO_LARGE_TO_PROPAGATE
|
Message text |
ISIS [UINT16] attempted to propagate a [STRING] LSP larger than MTU [UINT16] on interface [STRING]. (isisPDULSPSize=[UINT16], isisPDULSPID=[STRING]) |
|
Variable fields |
$1: IS-IS process ID. $2: IS level. Available values include Level-1, Level-2, and Level-1-2. $3: Interface MTU. $4: Interface name. $5: LSP length. $6: LSP ID. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_LSP_TOO_LARGE_TO_PROPAGATE: ISIS 1 attempted to propagate a Level-1 LSP larger than MTU 1500 on interface GE1/0/1. (isisPDULSPSize=1600, isisPDULSPID=0000.0000.0011.00-00) |
|
Impact |
LSPs are missing. |
|
Cause |
The length of the LSP that IS-IS attempted to propagate was larger than the interface MTU. |
|
Recommended action |
1. Execute the display ip interface interface-type interface-number command to view the value for the Maximum Transmit Unit field. This field displays the MTU of an interface. 2. Execute the display current-configuration configuration isis command in the current IS-IS process to view the configuration of the lsp-length originate command. If the lsp-length originate command is executed, the maximum LSP length equals the default value, 1497 bytes. ¡ If the maximum LSP length is greater than the interface MTU, go to step 3. ¡ If the maximum LSP length is less than the interface MTU, go to step 4. 3. Execute the lsp-length originate command in IS-IS view to change the maximum LSP length to a value less than the interface MTU. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 4. 4. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ISIS_MANUAL_ADDRESS_DROPS
|
Message text |
ISIS [UINT16] discarded some area addresses because the number of area addresses exceeded three. (isisManAreaAddr=[STRING]) |
|
Variable fields |
$1: IS-IS process ID. $2: Discarded area addresses. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_MANUAL_ADDRESS_DROPS: ISIS 1 discarded some area addresses because the number of area addresses exceeded three. (isisManAreaAddr=51) |
|
Impact |
Some Level-2 area addresses in the local IS-IS might be discarded. |
|
Cause |
When IS-IS leaks Level-1 area addresses to the Level-2 area on a Level-1-2 device, the number of Level-2 area addresses might exceed three. In this situation, IS-IS keeps only the lowest three addresses as Level-2 area addresses. As a result, some local Level-2 area addresses might be discarded. |
|
Recommended action |
1. Execute the display isis lsdb level-1 verbose command to view detailed Level-1 LSDB information. View the Area address field in the command output. This field records the total number of Level-1 area addresses. ¡ If the total number of Level-1 area addresses is greater than 3, go to step 2. ¡ If the total number of Level-1 area addresses is less than 3, go to step 4. 2. Execute the display isis lsdb level-1 verbose command to identify whether the Level-1 area addresses are the same as the Level-2 area addresses: ¡ If they are exactly the same, go to step 4. ¡ If some of them are different, go to step 3. 3. Use the undo network-entity command to reduce the number of invalid or unused area addresses. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 4. 4. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 system ID. $4: Interface name. $5: Neighbor state. This field might display DOWN, UP, or INIT. $6: Reason of neighbor state change. 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 |
3 (Error) |
|
Example |
ISIS/3/ISIS_NBR_CHG: IS-IS 1, Level-1 adjacency 0000.0000.0001 (GigabitEthernet1/0/1), state changed to DOWN, Reason: circuit data clean. |
|
Impact |
IS-IS might recalculate routes, which causes route flapping and traffic flapping. |
|
Cause |
This message is generated when one of the following conditions exists: · An IS-IS adjacency goes up or goes down. · An IS-IS configuration error exists. · The system is so busy that an IS-IS neighbor relationship flaps. · The state of an IS-IS neighbor relationship changes due to link failure. |
|
Recommended action |
Take actions based on the reason why the neighbor state changes, especially when the neighbor state changes to DOWN or INIT. If the reason for the neighbor state change is circuit data clean, perform the following operations: 5. Execute the display interface [ interface-type [ interface-number | interface-number.subnumber ] ] command to view the physical state of the related IS-IS interfaces. ¡ If the physical state is Down, troubleshoot the interfaces and recover the physical state to Up. ¡ If the physical state is Up, go to step 2. 6. Execute the ping command to check for link failures (including transport device failures). If no link failures are found, go to step 3. 7. Execute the display current-configuration configuration isis command to check for incorrect IS-IS settings. ¡ If all IS-IS settings are correct, go to step 4. ¡ If incorrect IS-IS settings exist, correct them and then check whether this message is generated again later. If this message is not generated any longer, the troubleshooting is successful. If this message is generated again, go to step 4. 8. Collect alarm information, log messages, and configuration data, and then contact Technical Support. If the reason for the neighbor state change is holdtime expired, perform the following operations: 9. Execute the ping command to check for link failures between the local device and the remote device. ¡ If no link failures are found, go to step 2. ¡ If link failures are found, go to step 4. 10. Execute the display current-configuration configuration isis command on the remote device to check for incorrect IS-IS settings. ¡ If all IS-IS settings are correct, go to step 3. ¡ If incorrect IS-IS settings exist, correct them and then identify whether this message is generated again later. If this message is not generated any longer, the troubleshooting is successful. If this message is generated again, go to step 7. 11. Execute the display cpu-usage command to identify whether the CPU usage is too high. ¡ If the CPU usage is too high, go to step 6. ¡ If the CPU usage is normal, go to step 7. 12. Troubleshoot the links between the local device and the remote device, and then execute the display isis packet hello by-interface interface-type interface-number command to identify whether the local device can receive hello packets from the neighbor. Make sure that the interface-type interface-number argument specifies the interface mentioned in this message. ¡ If the local device cannot receive hello packets from the neighbor, go to step 7. ¡ If the local device can receive hello packets from the neighbor, go to step 5. 13. Change the IS-IS settings, and then identify whether the neighbor state of the remote device restores to Up. ¡ If the neighbor state becomes Up, the troubleshooting is successful. ¡ If the neighbor state does not become Up, go to step 7. 14. Execute the display current-configuration command on the local device to check for and remove unnecessary IS-IS settings, and then identify whether the neighbor state of the remote device restores to Up. ¡ If the neighbor state becomes Up, the troubleshooting is successful. ¡ If the neighbor state does not become Up, go to step 7. 15. Collect alarm information, log messages, and configuration data, and then contact Technical Support. If the reason for the neighbor state change is BFD session down, perform the following operations: 16. Execute the ping command to check for link failures between the local device and the remote device. ¡ If no link failures are found, go to step 3. ¡ If link failures are found, go to step 2. 17. Troubleshoot the links between the local device and the remote device. 18. Collect alarm information, log messages, and configuration data, and then contact Technical Support. If the reason for the neighbor state change is peer reset, perform the following operations: 19. Execute the display isis troubleshooting command to view the reason for the neighbor down event. ¡ If the reason is the reset isis peer command was executed, no action is required. This is because the message is a normal result of executing the reset isis peer command. ¡ If the reason is not the reset isis peer command was executed, go to step 2. 20. Collect alarm information, log messages, and configuration data, and then contact Technical Support. If the reason for the neighbor state change is circuit ID conflicts, identify whether the IS-IS interface settings have been edited multiples times on the neighbor. If the reason for the neighbor state change is P2P peer GR down, identify whether the neighbor supports GR. If the reason for the neighbor state change is 2way-fail, perform the following operations: 21. Execute the display isis packet hello by-interface interface-type interface-number command to identify whether the local device can receive hello packets from the neighbor. Make sure that the interface-type interface-number argument specifies the interface mentioned in this message. ¡ If the local device cannot receive hello packets from the neighbor, go to step 3. ¡ If the local device can receive hello packets from the neighbor, go to step 2. 22. Identify whether the authentication settings are the same on the local device and the neighbor. ¡ If the local device and the neighbor use the same authentication settings, go to step 3. ¡ If the local device and the neighbor use different authentication settings, change their authentication settings to ensure that they use the same authentication settings, and then identify whether this message is generated again later. If this message is not generated any longer, the troubleshooting is successful. If this message is generated again, go to step 3. 23. Collect alarm information, log messages, and configuration data, and then contact Technical Support. |
ISIS_PEER_HOLD_MAX_COST_ENTER
|
Message text |
ISIS [UINT] peers on interface [STRING] enter hold-max-cost state. |
|
Variable fields |
$1: IS-IS process ID. $2: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
ISIS/6/ISIS_PEER_HOLD_MAX_COST_ENTER: ISIS 1 peers on interface GE1/0/1 enter hold-max-cost state. |
|
Impact |
No negative impact on the system. |
|
Cause |
IS-IS advertises the maximum link cost to neighbors within the period of time specified by the isis peer hold-max-cost duration command. |
|
Recommended action |
No action is required. |
ISIS_PEER_HOLD_MAX_COST_EXIT
|
Message text |
ISIS [UINT] peers on interface [STRING] exit hold-max-cost state. |
|
Variable fields |
$1: IS-IS process ID. $2: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
ISIS/6/ISIS_PEER_HOLD_MAX_COST_EXIT: ISIS 1 peers on interface GE1/0/1 exit hold-max-cost state. |
|
Impact |
No negative impact on the system. |
|
Cause |
IS-IS advertises the original link cost to neighbors when the period of time specified by the isis peer hold-max-cost duration command expires. |
|
Recommended action |
No action is required. |
ISIS_PREFIX_SID_OVER_RANGE
|
Message text |
ISIS [UINT16] received prefix SID [UINT32]. The prefix SID is not included in the local SRGB range. (Prefix=[STRING], AdvertiseSource=[STRING], localSRGB=[UINT32]-[UINT32]) |
|
Variable fields |
$1: IS-IS process ID. $2: Prefix SID. $3: Prefix address and mask. $4: Source of prefix SID advertisement. $5: Minimum value in the local SRGB. $6: Maximum value in the local SRGB. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_PREFIX_SID_OVER_RANGE: ISIS 1 received prefix SID 16020. The prefix SID is not included in the local SRGB range. (Prefix=10.1.1.0/24, AdvertiseSource=0000.0000.0002.00, localSRGB=16000-16010) |
|
Impact |
The system fails to generate an incoming label, which causes the failure to forward packets through SRLSPs. |
|
Cause |
The remote prefix SID received by IS-IS is not included in the local SRGB range. |
|
Recommended action |
1. Identify the source system ID based on the AdvertiseSource field in log information. 2. Identify the source device based on the system ID. Then, modify the prefix SID settings of the source device to ensure that the remote prefix SIDs are included in the local SRGB range. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ISIS_PREFIXSID_CONFLICT
|
Message text |
IS-IS failed to allocate prefix SID [UINT32] for IP address [STRING] because of SID conflict. |
|
Variable fields |
$1: Prefix SID. $2: Prefix address and mask. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_PREFIXSID_CONFLICT: IS-IS failed to allocate prefix SID 18020 for IP address 103.0.0.1/32 because of SID conflict. |
|
Impact |
The system will only select one SID, ignoring any identical SIDs released by other devices. |
|
Cause |
Multiple devices in the network are advertising the same prefix SID. |
|
Recommended action |
1. Identify the source device based on the prefix SID, and modify the SID settings on the loopback interface of the source device. Before modifying the prefix SID, execute the display mpls label command to display MPLS label usage information. Make sure that the prefix SID is idle. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ISIS_REJECTED_ADJACENCY
|
Message text |
IS-IS [UINT16] failed to establish [STRING] adjacency with its peer on interface [STRING]. (isisPDULen=[UINT16], isisPDUFragment=[STRING]) |
|
Variable fields |
$1: IS-IS process ID. $2: IS level. Available values include Level-1, Level-2, and Level-1-2. $3: Interface name. $4: PDU length. $5: First 32 bytes of the PDU header in hexadecimal notation. |
|
Severity level |
4 (Warning) |
|
Example |
ISIS/4/ISIS_REJECTED_ADJACENCY: IS-IS 1 failed to establish Level-1 adjacency with its peer on interface GE1/0/1. (isisPDULen=179, isisPDUFragment=00 b3 02 e0 00 00 00 00 00 11 00 00 00 00 00 64 f2 2b 03 01 02 01 00 81 02 cc 8e e8 20 00 11 00) |
|
Impact |
A neighbor cannot be established correctly. |
|
Cause |
· The local system ID or virtual system ID is duplicated with the system ID of the neighbor. · An hello packet fails authentication because the authentication mode or authentication key configured on the interface is different from that of the neighbor. · The IS-IS Level-1 neighbor area addresses are different at both ends of the link. · The local interface receives an hello packet that does not match the local level. · On a broadcast network, the IP address of the local interface that receives a hello packet resides on a different subnet from that of the interface that sends the hello packets. · On a P2P network,when the isis peer-ip-check command is executed on the local interface, the local interface receives a hello packet from an interface on a different subnet. |
|
Recommended action |
1. Identify the interface that receives the packet based on the interface value in log information. 2. Check the isisPDUFragment field (hexadecimal notation) in the device log to find the system ID of the source device that sent the PDU. Then, execute the display this command in interface view and in IS-IS process view at both ends of the link on the source device and local device to identify whether the IS-IS level and interface level are consistent. ¡ If these levels are consistent, go to step 3. ¡ If these levels are inconsistent, go to step 6. 3. Execute the isis circuit-level command in interface view at both ends of the link to configure the same IS-IS level and interface level. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 4. 4. Execute the display ip interface command to identify whether the IP address of the interface on the source device and that on the local device are on the same network segment. ¡ If they are on the same network segment, go to step 7. ¡ If they are not on the same network segment, go to step 5. 5. Execute the ip address command to configure the IP addresses of the interfaces to ensure that the interface IP addresses at both ends of the link are on the same network segment. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 7. 6. Identify whether the Level-1 area addresses at both ends of the link are on the same. ¡ If they are the same, go to step 9. ¡ If they are different, go to step 7. 7. Execute the network-entity command in IS-IS view to reconfigure the IS-IS area address, ensuring that the newly configured Level-1 area address is the same as the area address of the local device. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 8. 8. Execute the display current-configuration command to identify whether the system ID of the source device and the system ID or virtual system ID of the local device are duplicated. ¡ If they are duplicated, go to step 9. ¡ If they are not duplicated, go to step 11. 9. Execute the network-entity command to modify the system ID or virtual system ID of one of the devices to ensure that the system ID or virtual system ID at both ends of the link are not duplicated. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 10. 10. Execute the display this command in interface view at both ends of the link to identify whether the IS-IS authentication modes are consistent. ¡ If they are the same, go to step 12. ¡ If they are different, go to step 11. 11. Execute the isis authentication-mode command to edit the authentication modes and authentication keys in interface view at both ends of the link to ensure that the IS-IS authentication configuration at both ends of the link are the same. Alternatively, execute the isis authentication-mode command in interface view at both ends of the link to cancel authentication configuration. Then, identify whether the device still generates this message: ¡ If the device does not generate this message, the issue is resolved. ¡ If the device still generates this message, go to step 12. 12. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
KHTTP messages
This section contains KHTTP messages.
KHTTP_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. $2: TCP port number. $3: VPN instance index. |
|
Severity level |
3 (Error) |
|
Example |
KHTTP/3/KHTTP_BIND_PORT_ALLOCETED: Failed to bind TCP connection 192.168.30.117/10000 to VPN instance 0 because the port was already allocated. |
|
Impact |
The device cannot use this address and port number to provide the SSL VPN gateway service. |
|
Cause |
This message is generated when the binding of an IP address, TCP port, and VPN instance failed because the TCP port was already allocated. |
|
Recommended action |
Use an available TCP port for the binding. To view the available TCP ports, execute the display tcp-proxy port-info or display ipv6 tcp-proxy port-info command. |
KHTTP_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. $2: TCP port number. $3: VPN instance index. |
|
Severity level |
3 (Error) |
|
Example |
KHTTP/3/KHTTP_BIND_ADDRESS_INUSED: Failed to bind TCP connection 192.168.30.117/10000 to VPN instance 0 because the address was already used. |
|
Impact |
The device cannot use this address and port number to provide the SSL VPN gateway service. |
|
Cause |
This message is generated when the binding of an IP address, TCP port, and VPN instance failed because the IP address was already used and was not allowed to be used by multiple systems. |
|
Recommended action |
Use an available IP address for the binding. To view the available IP addresses, execute the display tcp-proxy command. |
L2MC messages
This section contains Layer 2 multicast messages.
L2MC_CFD_NOTSPT
|
Message text |
Interface [STRING] does not support CFD. Please check your configuration. |
|
Variable fields |
$1: Interface number. |
|
Severity level |
6 (Informational) |
|
Example |
L2MC/6/L2MC_CFD_NOTSPT: -MDC=1-Slot=3; Interface GigabitEthernet3/1/1.1 does not support CFD. Please check your configuration. |
|
Impact |
None. |
|
Cause |
The interface does not support CFD. |
|
Recommended action |
Do not configure CFD on the interface. |
L2TPv2 messages
This section contains L2TPv2 messages.
L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD (UPs)
|
Message text |
Centralized devices: The keepalive packet loss ratio is [UINT32]%, and exceeds [UINT32]%. Distributed devices in standalone mode: Centralized IRF devices: The keepalive packet loss ratio on slot [UINT32] is [UINT32]%, and exceeds [UINT32]%. Distributed devices in IRF mode: The keepalive packet loss ratio on chassis [UINT32] slot [UINT32] is [UINT32]%, and exceeds [UINT32]%. |
|
Variable fields |
$1: Chassis number. (Distributed devices in IRF mode.) $2: Slot number. (Distributed devices in standalone mode.)(Centralized IRF devices.)(Distributed devices in IRF mode.) $3: Packet loss ratio of detection packets. $4: Packet loss ratio alarm threshold for detection packets. |
|
Severity level |
4 (Warning) |
|
Example |
Centralized devices: L2TPv2/4/L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio is 50%, and exceeds 30%. Distributed devices in standalone mode: Centralized IRF devices: L2TPv2/4/L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio on slot 1 is 50%, and exceeds 30%. Distributed devices in IRF mode: L2TPv2/4/L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio on chassis 1 slot 1 is 50%, and exceeds 30%. |
|
Impact |
Users might be forced to go offline due to detection failure caused by an excessively high packet loss ratio. |
|
Cause |
· The maximum threshold is small. · The poor link quality caused by reasons such as device interface cabling faults has resulted in the number of dropped packets for online users exceeding the alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view to filter the configuration by the access-user user-detect packet-loss-ratio-threshold command to identify whether the alarm threshold for the packet loss ratio of access user detection packets is configured properly. ¡ If the threshold is too small, go to step 2. ¡ If the threshold is too great, go to step 3. 2. Execute the access-user user-detect packet-loss-ratio-threshold command in system view to edit the alarm threshold for the packet loss ratio of access user detection packets. 3. Identify whether the device interface cable connections and network configuration are normal ¡ If the device interface cable connections and network configuration are abnormal, troubleshoot the issues. ¡ If the device interface cable connections and network configuration are normal, go to step 4. 4. If the issue persists, collect the following information and contact Technical Support: ¡ The results in the previous results. ¡ Configuration files, log information, and alarm information on the device. |
L2TPV2_LOSS_RATIO_RECOVER_NORMAL (UPs)
|
Message text |
Centralized devices: The keepalive packet loss ratio has recovered to normal state. Distributed devices in standalone mode: Centralized IRF devices: The keepalive packet loss ratio on slot [UINT32] has recovered to normal state. Distributed devices in IRF mode: The keepalive packet loss ratio on chassis [UINT32] slot [UINT32] has recovered to normal state. |
|
Variable fields |
$1: Chassis number. (Distributed devices in IRF mode.) $2: Slot number. (Distributed devices in standalone mode.)(Centralized IRF devices.)(Distributed devices in IRF mode.) |
|
Severity level |
4 (Warning) |
|
Example |
Centralized devices: L2TPv2/4/L2TPV2_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio has recovered to normal state. Distributed devices in standalone mode: Centralized IRF devices: L2TPv2/4/L2TPV2_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio on slot 1 has recovered to normal state. Distributed devices in IRF mode: L2TPv2/4/L2TPV2_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio on chassis 1 slot 1 has recovered to normal state. |
|
Impact |
The network jitter and latency has reduced to a reasonable range, recovering the user service quality to normal. |
|
Cause |
The device interface cabling faults are cleared for the link quality to recover to normal. |
|
Recommended action |
No action is required. |
L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD (non-vBRAS-CPs)
|
Message text |
Centralized devices: The keepalive packet loss ratio on the interface [STRING] is [UINT32]%, and exceeds [UINT32]%. Distributed devices in standalone mode: Centralized IRF devices: The keepalive packet loss ratio on the interface [STRING] on slot [UINT32] is [UINT32]%, and exceeds [UINT32]%. Distributed devices in IRF mode: The keepalive packet loss ratio on the interface [STRING] on chassis [UINT32] slot [UINT32] is [UINT32]%, and exceeds [UINT32]%. |
|
Variable fields |
$1: Interface name. $2: Chassis number. (Distributed devices in IRF mode.) $3: Slot number. (Distributed devices in standalone mode.)(Centralized IRF devices.)(Distributed devices in IRF mode.) $4: Packet loss ratio of detection packets. $5: Packet loss ratio alarm threshold for detection packets. |
|
Severity level |
4 (Warning) |
|
Example |
Centralized devices: L2TPv2/4/L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio on the interface BAS-interface1 is 50%, and exceeds 30%. Distributed devices in standalone mode: Centralized IRF devices: L2TPv2/4/L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio on the interface BAS-interface1 on slot 1 is 50%, and exceeds 30%. Distributed devices in IRF mode: L2TPv2/4/L2TPV2_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio on the interface BAS-interface1 on chassis 1 slot 1 is 50%, and exceeds 30%. |
|
Impact |
Users might be forced to go offline due to detection failure caused by an excessively high packet loss ratio. |
|
Cause |
· The maximum threshold is small. · The poor link quality caused by reasons such as device interface cabling faults has resulted in the number of dropped packets for online users exceeding the alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view to filter the configuration by the access-user user-detect packet-loss-ratio-threshold command to identify whether the alarm threshold for the packet loss ratio of access user detection packets is configured properly. ¡ If the threshold is too small, go to step 2. ¡ If the threshold is too great, go to step 3. 2. Execute the access-user user-detect packet-loss-ratio-threshold command in system view to edit the alarm threshold for the packet loss ratio of access user detection packets. 3. Identify whether the device interface cable connections and network configuration are normal ¡ If the device interface cable connections and network configuration are abnormal, troubleshoot the issues. ¡ If the device interface cable connections and network configuration are normal, go to step 4. 4. If the issue persists, collect the following information and contact Technical Support: ¡ The results in the previous results. ¡ Configuration files, log information, and alarm information on the device. |
L2TPV2_LOSS_RATIO_RECOVER_NORMAL (non-vBRAS-CPs)
|
Message text |
Centralized devices: The keepalive packet loss ratio on the interface [STRING] has recovered to normal state. Distributed devices in standalone mode: Centralized IRF devices: The keepalive packet loss ratio on the interface [STRING] on slot [UINT32] has recovered to normal state. Distributed devices in IRF mode: The keepalive packet loss ratio on the interface [STRING] on chassis [UINT32] slot [UINT32] has recovered to normal state. |
|
Variable fields |
$1: Interface name. $2: Chassis number. (Distributed devices in IRF mode.) $3: Slot number. (Distributed devices in standalone mode.)(Centralized IRF devices.)(Distributed devices in IRF mode.) |
|
Severity level |
4 (Warning) |
|
Example |
Centralized devices: L2TPv2/4/L2TPV2_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio on the interface BAS-interface1 has recovered to normal state. Distributed devices in standalone mode: Centralized IRF devices: L2TPv2/4/L2TPV2_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio on the interface BAS-interface1 on slot 1 has recovered to normal state. Distributed devices in IRF mode: L2TPv2/4/L2TPV2_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio on the interface BAS-interface1 on chassis 1 slot 1 has recovered to normal state. |
|
Impact |
The network jitter and latency has reduced to a reasonable range, recovering the user service quality to normal. |
|
Cause |
The device interface cabling faults are cleared for the link quality to recover to normal. |
|
Recommended action |
No action is required. |
L2TPV2_SESSION_EXCEED_LIMIT
|
Message text |
|
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L2TPV2/4/L2TPV2_SESSION_EXCEED_LIMIT: Number of L2TP sessions exceeded the limit. |
|
Impact |
The system cannot create new L2TP sessions. That is, new L2TP users are not allowed to come online. |
|
Cause |
The number of the established L2TP sessions has reached the upper limit. |
|
Recommended action |
For new L2TP users to come online, wait for old L2TP users to go offline to release L2TP session resources. Alternatively, the administrator can execute the cut access-user command to forcibly log out L2TP users to release L2TP session resources. |
L2TPV2_SESSIONS_LOWER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
The L2TP session number is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower online L2TP session count alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
L2TPV2/4/L2TPV2_SESSIONS_LOWER_THRESHOLD: The L2TP session number is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A larger number of users might go offline due to exceptions. Identify whether a large number of users go offline abnormally. |
|
Cause |
· The specified lower online L2TP session count alarm threshold is too great. · Users go offline and the number of users decreases to the lower online L2TP session count alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view to filter the configuration by the l2tp session-threshold command to identify whether the lower online L2TP session count alarm threshold is configured properly. ¡ If the lower online L2TP session count alarm threshold is too great, go to step 2. ¡ If the lower online L2TP session count alarm threshold is proper, go to step 3. 2. Execute the l2tp session-threshold command in system view to edit the lower online L2TP session count alarm threshold. 3. Execute the display aaa abnormal-offline-record access-type ppp command to identify whether a large number of L2TP users go offline abnormally. ¡ If a large number of L2TP users go offline abnormally, troubleshoot the issues accordingly. ¡ If not a large number of L2TP users go offline abnormally, execute display aaa offline-record access-type ppp command to check the reasons for L2TP user disconnection and take appropriate actions accordingly. 4. If the issue persists, collect the following information and contact Technical Support: ¡ The results in the previous results. ¡ Configuration files, log information, and alarm information on the device. |
L2TPV2_SESSIONS_LOWER_THRESHOLD (vBRAS-CPs)
|
Message text |
The L2TP session number on slot [INT32] is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Lower online L2TP session count alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
L2TPV2/4/L2TPV2_SESSIONS_LOWER_THRESHOLD: The L2TP session number on slot 97 is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A larger number of users might go offline due to exceptions. Identify whether a large number of users go offline abnormally. |
|
Cause |
· The specified lower online L2TP session count alarm threshold is too great. · Users go offline and the number of users decreases to the lower online L2TP session count alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view to filter the configuration by the l2tp session-threshold command to identify whether the lower online L2TP session count alarm threshold is configured properly. ¡ If the lower online L2TP session count alarm threshold is too great, go to step 2. ¡ If the lower online L2TP session count alarm threshold is proper, go to step 3. 2. Execute the l2tp session-threshold command in system view to edit the lower online L2TP session count alarm threshold. 3. Execute the display aaa abnormal-offline-record access-type ppp command to identify whether a large number of L2TP users go offline abnormally. ¡ If a large number of L2TP users go offline abnormally, troubleshoot the issues accordingly. ¡ If not a large number of L2TP users go offline abnormally, execute display aaa offline-record access-type ppp command to check the reasons for L2TP user disconnection and take appropriate actions accordingly. 4. If the issue persists, collect the following information and contact Technical Support: ¡ The results in the previous results. 5. Configuration files, log information, and alarm information on the device. |
L2TPV2_SESSIONS_LOWER_RECOVER (non-vBRAS-CPs)
|
Message text |
The L2TP session number has recovered to normal state from below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower online L2TP session count alarm threshold. |
|
Severity level |
5 (Notification) |
|
Example |
L2TPV2/5/L2TPV2_SESSIONS_LOWER_RECOVER: The L2TP session number has recovered to normal state from below the lower warning threshold (LowerThreshold=20). |
|
Impact |
The number of L2TP users meets the expected access quantity for the device. |
|
Cause |
L2TP users come online and the online L2TP session count recovers from below the lower threshold to the normal range. |
|
Recommended action |
No action is required. |
L2TPV2_SESSIONS_LOWER_RECOVER (vBRAS-CPs)
|
Message text |
The L2TP session number on slot [INT32] has recovered to normal state from below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Lower online L2TP session count alarm threshold. |
|
Severity level |
5 (Notification) |
|
Example |
L2TPV2/5/L2TPV2_SESSIONS_LOWER_RECOVER: The L2TP session number on slot 97 has recovered to normal state from below the lower warning threshold (LowerThreshold=20). |
|
Impact |
The number of L2TP users meets the expected access quantity for the device. |
|
Cause |
L2TP users come online and the online L2TP session count recovers from below the lower threshold to the normal range. |
|
Recommended action |
No action is required. |
L2TPV2_SESSIONS_UPPER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
The L2TP session number is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper online L2TP session count alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
L2TPV2/4/L2TPV2_SESSIONS_UPPER_THRESHOLD: The L2TP session number is above the upper warning threshold (UpperThreshold=80). |
|
Impact |
The L2TP users come online, leading to the L2TP user count exceeding the device's capacity, resulting in subsequent failures for L2TP user login. |
|
Cause |
· The specified upper online L2TP session count alarm threshold is too small. · Users come online and the number of users increases to the upper online L2TP session count alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view to filter the configuration by the l2tp session-threshold command to identify whether the upper online L2TP session count alarm threshold is configured properly. ¡ If the upper online L2TP session count alarm threshold is too small, go to step 2. ¡ If the upper online L2TP session count alarm threshold is proper, go to step 3. 2. Execute the l2tp session-threshold command in system view to edit the upper online L2TP session count alarm threshold. 3. If the issue persists, collect the following information and contact Technical Support: ¡ The results in the previous results. ¡ Configuration files, log information, and alarm information on the device. |
L2TPV2_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
|
Message text |
The L2TP session number on slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Upper online L2TP session count alarm threshold. |
|
Severity level |
4 (Warning) |
|
Example |
L2TPV2/4/L2TPV2_SESSIONS_UPPER_THRESHOLD: The L2TP session number on slot 97 is above the upper warning threshold (UpperThreshold=80). |
|
Impact |
The L2TP users come online, leading to the L2TP user count exceeding the device's capacity, resulting in subsequent failures for L2TP user login. |
|
Cause |
· The specified upper online L2TP session count alarm threshold is too small. · Users come online and the number of users increases to the upper online L2TP session count alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view to filter the configuration by the l2tp session-threshold command to identify whether the upper online L2TP session count alarm threshold is configured properly. ¡ If the upper online L2TP session count alarm threshold is too small, go to step 2. ¡ If the upper online L2TP session count alarm threshold is proper, go to step 3. 2. Execute the l2tp session-threshold command in system view to edit the upper online L2TP session count alarm threshold. 3. If the issue persists, collect the following information and contact Technical Support: ¡ The results in the previous results. ¡ Configuration files, log information, and alarm information on the device. |
L2TPV2_SESSIONS_UPPER_RECOVER (non-vBRAS-CPs)
|
Message text |
The L2TP session number has recovered to normal state from above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper online L2TP session count alarm threshold. |
|
Severity level |
5 (Notification) |
|
Example |
L2TPV2/5/L2TPV2_SESSIONS_UPPER_RECOVER: The L2TP session number has recovered to normal state from above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The L2TP user login count has decreased and did not exceed the device's capacity, allowing for successful subsequent L2TP user logins. |
|
Cause |
Some L2TP users go offline. The online L2TP session count recovers from above the upper threshold to the normal range. |
|
Recommended action |
No action is required. |
L2TPV2_SESSIONS_UPPER_RECOVER (vBRAS-CPs)
|
Message text |
The L2TP session number on slot [INT32] has recovered to normal state from above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Upper online L2TP session count alarm threshold. |
|
Severity level |
5 (Notification) |
|
Example |
L2TPV2/5/L2TPV2_SESSIONS_UPPER_RECOVER: The L2TP session number on slot 97 has recovered to normal state from above the upper warning threshold (UpperThreshold =20). |
|
Impact |
The L2TP user login count has decreased and did not exceed the device's capacity, allowing for successful subsequent L2TP user logins. |
|
Cause |
Some L2TP users go offline. The online L2TP session count recovers from above the upper threshold to the normal range. |
|
Recommended action |
No action is required. |
L2TPV2_TUNNEL_ADD_DRIVER_FAILED
|
Message text |
Failed to add an L2TP tunnel Ipaddr=[STRING], TunnelID=[UINT16]. Cause: Not enough hardware resources. |
|
Variable fields |
$1: Local IP address. $2: Local tunnel ID. |
|
Severity level |
4 (Warning) |
|
Example |
L2TPV2/4/L2TPV2_TUNNEL_ADD_DRIVER_FAILED: Failed to add an L2TP tunnel Ipaddr=1.1.1.1, TunnelID =100. Cause: Not enough hardware resources. |
|
Impact |
The L2TP tunnel failed to be created. |
|
Cause |
Failed to add an L2TP tunnel because of insufficient hardware resources. |
|
Recommended action |
Collect the following information and contact Technical Support: · The results in the previous results. · Configuration files, log information, and alarm information on the device. |
L2TPV2_TUNNEL_EXCEED_LIMIT
|
Message text |
Number of L2TP tunnels exceeded the limit. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L2TPV2/4/L2TPV2_TUNNEL_EXCEED_LIMIT: Number of L2TP tunnels exceeded the limit. |
|
Impact |
The new L2TP tunnel failed to be created. |
|
Cause |
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 Technical Support. |
L2TPV2_TUNNEL_UP_OR_DOWN
|
Message text |
The status of L2TP tunnel changed (LocalTunnelID=[INT32], TunnelRemoteName=[STRING],PeerIPAddress=[IPADDR],TunnelStatus=[STRING],TunnelDownReason=[STRING], RemoteTunnelID=[INT32], SessionCount=[INT32]). |
|
Variable fields |
$1: Local tunnel ID. $2: Remote tunnel name. $3: Remote tunnel IP address. $4: Tunnel state: ¡ Established. ¡ stopping. $5: Tunnel disconnection reason. $6: Remote tunnel ID. $7: L2TP session count. |
|
Severity level |
5 (Notification) |
|
Example |
L2TPV2/5/L2TPV2_TUNNEL_UP_OR_DOWN: The status of L2TP tunnel changed (LocalTunnelID= 1,TunnelRemoteName= lns, PeerIPAddress= 120.1.1.1, TunnelStatus= stopping, TunnelDownReason= lns clear tunnel, RemoteTunnelID= 1, SessionCount= 10). |
|
Impact |
· An L2TP tunnel is established on which new L2TP sessions come online. · An L2TP tunnel is removed on which L2TP sessions go offline. · If an L2TP tunnel is unexpectedly removed, its carried L2TP sessions will go offline abnormally, causing user traffic interruption. |
|
Cause |
· An L2TP session comes online and an L2TP tunnel is established. · An L2TP session goes offline and an L2TP tunnel is removed. · An L2TP tunnel is removed because the keepalive timeout timer expires. · An L2TP tunnel is removed due to protocol packet loss and disorder that causes misalignment. |
|
Recommended action |
1. Execute the display l2tp tunnel command in any view based on log information to identify whether the status of the L2TP tunnel is established. ¡ If the L2TP tunnel is in established state, the L2TP tunnel is set up successfully. No action is required. ¡ If the L2TP tunnel is not in established state, go to step 2. 2. If an L2TP user goes offline on the tunnel, have the user come online again, and then identify whether this message still exists. ¡ If this message still exists, go to step 3. ¡ If this message does not exist, no action is required. 3. Check the reason for the user login failure, troubleshoot the issue according to the L2TP user login failure troubleshooting guide, and identify whether this message still exists. ¡ If this message still exists, go to step 4. ¡ If this message does not exist, no action is required. 4. If the issue persists, collect the following information and contact Technical Support: ¡ The results in the previous results. ¡ Configuration files, log information, and alarm information on the device. |
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 |
4 (Warning) |
|
Example |
L2VPN/4/L2VPN_BGPVC_CONFLICT_LOCAL: Remote site ID 1 (From 1.1.1.1, route distinguisher 1:1) conflicts with local site. |
|
Impact |
The PW cannot be established. |
|
Cause |
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 |
4 (Warning) |
|
Example |
L2VPN/4/L2VPN_BGPVC_CONFLICT_REMOTE: Remote site ID 1 (From 1.1.1.1, route distinguisher 1:1) conflicts with another remote site. |
|
Impact |
The local device can establish a PW with only one of the two remote devices. |
|
Cause |
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 (Warning) |
|
Example |
L2VPN/4/L2VPN_HARD_RESOURCE_NOENOUGH: No enough hardware resource for L2VPN. |
|
Impact |
No new VSI, PW, or AC can be created. |
|
Cause |
Hardware resources for L2VPN were insufficient. |
|
Recommended action |
Identify 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 |
2 (Critical) |
|
Example |
L2VPN/2/L2VPN_HARD_RESOURCE_RESTORE: Hardware resources for L2VPN are restored. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
L2VPN/4/L2VPN_LABEL_DUPLICATE: Incoming label 1024 for a static PW in Xconnect-group aaa is duplicate. |
|
Impact |
The current PW cannot be created. |
|
Cause |
The incoming label of a static PW in this Xconnect-group or VSI was occupied by another configuration, for example, by a static LSP, static BSID, or static CRLSP. |
|
Recommended action |
Execute the display mpls label command to display the state and owner of the MPLS label. If the label is in use, specify a new label for the static PW. To use the label for other purposes, delete the configuration based on the owner information to release the label. |
L2VPN_MACLIMIT_FALL_AC
|
Message text |
The number of MAC address entries on the AC fell below the upper limit. (VSI name=[STRING], link ID=[UINT32], max-mac-entries=[UINT32], current-mac-entries=[UINT32]) |
|
Variable fields |
$1: Name of the VSI associated with the AC. $2: Link ID for the AC. $3: Maximum number of MAC addresses that the AC can learn. A value of unlimited indicates that no limit is set on the number of MAC addresses that the AC can learn. $4: Number of MAC addresses currently learned by the AC. |
|
Severity level |
4 (Warning) |
|
Example |
L2VPN/4/L2VPN_MACLIMIT_FALL_AC: -MDC=1-Slot=5; The number of MAC address entries on the AC fell below the upper limit. (VSI name=aaa, link ID=1, max-mac-entries=100, current-mac-entries=80) |
|
Impact |
No negative impact on services. |
|
Cause |
The number of MAC addresses learned by the AC falls below 90% of the upper limit. |
|
Recommended action |
No action is required. |
L2VPN_MACLIMIT_FALL_PW
|
Message text |
The number of MAC address entries on the PW fell below the upper limit. (VSI name=[STRING], link ID=[UINT32], max-mac-entries=[UINT32], current-mac-entries=[UINT32]) |
|
Variable fields |
$1: Name of the VSI associated with the PW. $2: Link ID for the PW. $3: Maximum number of MAC addresses that the PW can learn. A value of unlimited indicates that no limit is set on the number of MAC addresses that the PW can learn. $4: Number of MAC addresses currently learned by the PW. |
|
Severity level |
4 (Warning) |
|
Example |
L2VPN/4/L2VPN_MACLIMIT_FALL_PW: -MDC=1-Slot=5; The number of MAC address entries on the PW fell below the upper limit. (VSI name=aaa, link ID=100, max-mac-entries=50, current-mac-entries=30) |
|
Impact |
No negative impact on services. |
|
Cause |
The number of MAC addresses learned by the PW falls below 90% of the upper limit. |
|
Recommended action |
No action is required. |
L2VPN_MACLIMIT_FALL_VSI
|
Message text |
The number of MAC address entries on the VSI fell below the upper limit. (VSI name=[STRING], max-mac-entries=[UINT32], current-mac-entries=[UINT32]) |
|
Variable fields |
$1: Name of the VSI. $2: Maximum number of MAC addresses that the VSI can learn. A value of unlimited indicates that no limit is set on the number of MAC addresses that the VSI can learn. $3: Number of MAC addresses currently learned by the VSI. |
|
Severity level |
4 (Warning) |
|
Example |
L2VPN/4/L2VPN_MACLIMIT_FALL_VSI: -MDC=1-Slot=5; The number of MAC address entries on the VSI fell below the upper limit. (VSI name=aaa, max-mac-entries=200, current-mac-entries=150) |
|
Impact |
No negative impact on services. |
|
Cause |
The number of MAC addresses learned within the VSI falls below 90% of the upper limit. |
|
Recommended action |
No action is required. |
L2VPN_MACLIMIT_MAX_AC
|
Message text |
The number of MAC address entries on the AC reached the upper limit. (VSI name=[STRING], link ID=[UINT32], max-mac-entries=[UINT32]) |
|
Variable fields |
$1: Name of the VSI associated with the AC. $2: Link ID for the AC. $3: Maximum number of MAC addresses that the AC can learn. |
|
Severity level |
4 (Warning) |
|
Example |
L2VPN/4/L2VPN_MACLIMIT_MAX_AC: -MDC=1-Slot=5; The number of MAC address entries on the AC reached the upper limit. (VSI name=aaa, link ID=1, max-mac-entries=100) |
|
Impact |
The AC cannot learn new MAC address entries. |
|
Cause |
The number of MAC addresses learned on the AC has reached the maximum allowed. |
|
Recommended action |
Use the mac-limit command to modify the MAC address learning limit or delete unnecessary MAC address entries. |
L2VPN_MACLIMIT_MAX_PW
|
Message text |
The number of MAC address entries on the PW reached the upper limit. (VSI name=[STRING], link ID=[UINT32], max-mac-entries=[UINT32]) |
|
Variable fields |
$1: Name of the VSI associated with the PW. $2: Link ID for the PW. $3: Maximum number of MAC addresses that the PW can learn. |
|
Severity level |
4 (Warning) |
|
Example |
L2VPN/4/L2VPN_MACLIMIT_MAX_PW: -MDC=1-Slot=5; The number of MAC address entries on the PW reached the upper limit. (VSI name=aaa, link ID=100, max-mac-entries=50) |
|
Impact |
The PW cannot learn new MAC address entries. |
|
Cause |
The number of MAC addresses learned on the PW has reached the maximum allowed. |
|
Recommended action |
Use the mac-limit command to modify the MAC address learning limit or delete unnecessary MAC address entries. |
L2VPN_MACLIMIT_MAX_VSI
|
Message text |
The number of MAC address entries on the VSI reached the upper limit. (VSI name=[STRING], max-mac-entries=[UINT32]) |
|
Variable fields |
$1: Name of the VSI. $2: Maximum number of MAC addresses that the VSI can learn. |
|
Severity level |
4 (Warning) |
|
Example |
L2VPN/4/L2VPN_MACLIMIT_MAX_VSI: -MDC=1-Slot=5; The number of MAC address entries on the VSI reached the upper limit. (VSI name=aaa, max-mac-entries=200) |
|
Impact |
The VSI cannot learn new MAC address entries. |
|
Cause |
The number of MAC addresses learned within the VSI has reached the maximum allowed. |
|
Recommended action |
Use the mac-table limit command to change the maximum number of MAC addresses that the VSI can learn or delete unnecessary MAC address entries. |
L3 messages
This section contains Layer 3 messages.
BIER_TNLDIP_NORES
|
Message text |
No enough bier tunnel dip index resource |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/BIER_TNL_DIP_NORES: -MDC=1-Slot=3; No enough bier tunnel dip index resource |
|
Impact |
BIER tunnels cannot be used. |
|
Cause |
BIER tunnel index resources are insufficient. |
|
Recommended action |
1. Check the environment and roll back unused configuration. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
STATIS_NORES
|
Message text |
Operation failed on [string] because of insufficient resources. |
|
Variable fields |
$1: Interface number obtained based on the interface index. |
|
Severity level |
2 (Critical) |
|
Example |
L3/2/STATIS_NORES: -MDC=1-Slot=2; Operation failed on Ten-GigabitEthernet3/0/1.1 because of insufficient resources. |
|
Impact |
The Layer 3 packet statistics collection feature cannot be used. |
|
Cause |
The device failed to enable statistics counting for IPv4 and IPv6 packets on the interface because this interface does not have enough token bucket resources for incoming and outgoing packets. |
|
Recommended action |
1. Release token bucket resources on the interface. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IFINDEX_STATIS_NORES
|
Message text |
Operation failed on [string] because of insufficient resources. |
|
Variable fields |
$1: Interface index. |
|
Severity level |
2 (Critical) |
|
Example |
L3/2/IFINDEX_STATIS_NORES: -MDC=1-Slot=2; Operation failed on 9728 because of insufficient resources. |
|
Impact |
The Layer 3 packet statistics collection feature cannot be used. |
|
Cause |
The device failed to enable statistics counting for IPv4 and IPv6 packets on the interface because this interface does not have enough token bucket resources for incoming and outgoing packets. |
|
Recommended action |
1. Release token bucket resources on the interface. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
STATIS_CONF_CONFLICT
|
Message text |
The operation is not supported because configuration conflict on [string]. |
|
Variable fields |
$1: Interface number obtained based on the interface index. |
|
Severity level |
2 (Critical) |
|
Example |
L3/2/STATIS_CONF_CONFLICT: -MDC=1-Slot=2; The operation is not supported because configuration conflict on Ten-GigabitEthernet3/0/1.1. |
|
Impact |
The Layer 3 packet statistics collection feature cannot be used. |
|
Cause |
The device failed to enable statistics counting for IPv4 and IPv6 packets on an interface because of the configuration conflict. |
|
Recommended action |
1. Delete the following configurations on the interface and enable Layer 3 packet statistics collection: ¡ An L2VPN-leased user is configured on the interface. ¡ The VLAN to which the interface belongs is enabled with packet statistics for Ethernet service instances of the VLAN. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INFINDEX_STATIS_CONFLICT
|
Message text |
The operation is not supported because configuration conflict on [string]. |
|
Variable fields |
$1: Interface index. |
|
Severity level |
2 (Critical) |
|
Example |
L3/2/INFINDEX_STATIS_CONFLICT: -MDC=1-Slot=2; The operation is not supported because configuration conflict on 9728. |
|
Impact |
The Layer 3 packet statistics collection feature cannot be used. |
|
Cause |
The device failed to enable statistics counting for IPv4 and IPv6 packets on an interface because of the configuration conflict. |
|
Recommended action |
1. Delete the following configurations on the interface and enable Layer 3 packet statistics collection: ¡ An L2VPN-leased user is configured on the interface. ¡ The VLAN to which the interface belongs is enabled with packet statistics for Ethernet service instances of the VLAN. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARPINDEX_NORES
|
Message text |
Not enough ARP index resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/23.8 ARPINDEX_NORES: -MDC=1; Not enough ARP index resource. |
|
Impact |
ARP or ND entries cannot be learned. |
|
Cause |
ARP index resources are insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NEXTHOP_NORES
|
Message text |
Not enough NextHop resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/NEXTHOP_NORES: -MDC=1-Slot=3; Not enough NextHop resource. |
|
Impact |
ARP/ND entries and non-equal-cost routes cannot be learned, and traffic forwarding might fail. |
|
Cause |
Next hop resources are insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
V4PREFIX_NORES
|
Message text |
Not enough IPv4 prefix resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/V4PREFIX_NORES: -MDC=1-Slot=3; Not enough IPv4 prefix resource. |
|
Impact |
IPv4 routes cannot be learned. |
|
Cause |
IPv4 prefix resources are insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
V6PREFIX_NORES
|
Message text |
Not enough IPv6 prefix resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/V6PREFIX_NORES: -MDC=1-Slot=3; Not enough IPv6 prefix resource. |
|
Impact |
IPv6 routes cannot be learned. |
|
Cause |
IPv6 prefix resources are insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARP_ATTACK
|
Message text |
Arp Attack!!! |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/ARP_ATTACK: -MDC=1-Slot=3; Arp Attack!!! |
|
Impact |
User services are affected. |
|
Cause |
An ARP attack was detected. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ICMP_ATTACK
|
Message text |
ICMP Attack! |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/ICMP_ATTACK: -MDC=1-Slot=3; ICMP Attack! |
|
Impact |
Determine the impact according to the actual situation. |
|
Cause |
An ICMP attack was detected. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPV4_ACL_EXCEED
|
Message text |
The IPv4 ACL resource usage exceeds 80%. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPV4/4/IPV4_ACL_EXCEED: -MDC=1-Slot=3; The IPv4 ACL resource usage exceeds 80%. |
|
Impact |
DHCP flood attack prevention entries cannot be assigned. |
|
Cause |
The usage of IPv4 ACL resources exceeded 80%. In this case, the device cannot assign DHCP flood attack prevention entries. |
|
Recommended action |
1. Execute the display qos-acl resource command in system view to examine the ACL resource usage for the card, and then delete unused IPv4 ACL rules to release some IPv4 ACL resources. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPV6_ACL_EXCEED
|
Message text |
The IPv6 ACL resource usage exceeds 80%. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPV4/4/IPV6_ACL_EXCEED: -MDC=1-Slot=3; The IPv6 ACL resource usage exceeds 80%. |
|
Impact |
DHCPv6 flood attack prevention entries cannot be assigned. |
|
Cause |
The usage of IPv6 ACL resources exceeded 80%. In this case, the device cannot assign DHCPv6 flood attack prevention entries. |
|
Recommended action |
1. Execute the display qos-acl resource command in system view to examine the ACL resource usage for the card, and then delete unused IPv6 ACL rules to release some IPv6 ACL resources. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
IPV4_ACL_NORES
|
Message text |
Not enough IPv4 ACL resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPV4/4/IPV4_ACL_NORES: -MDC=1-Slot=3; Not enough IPv4 ACL resources. |
|
Impact |
IPv4 ACL rules cannot be configured. |
|
Cause |
· This message is sent when ACL hardware entries fail to be deployed due to insufficient IPv4 ACL resources. GTSM cannot work in this case. · After TCP SYN flood attack prevention is enabled, the system deploys ACL hardware entries when an attack occurs. This message is sent when ACL hardware entries fail to be deployed due to insufficient IPv4 ACL resources. TCP SYN flood attack prevention cannot work in this case. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
IPV6_ACL_NORES
|
Message text |
Not enough IPv6 ACL resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPV4/4/IPV6_ACL_NORES: -MDC=1-Slot=3; Not enough IPv6 ACL resources. |
|
Impact |
IPv6 ACL rules cannot be configured. |
|
Cause |
· This message is sent when ACL hardware entries fail to be deployed due to insufficient IPv6 ACL resources. GTSM cannot work in this case. · After TCP SYN flood attack prevention is enabled, the system deploys ACL hardware entries when an attack occurs. This message is sent when ACL hardware entries fail to be deployed due to insufficient IPv6 ACL resources. TCP SYN flood attack prevention cannot work in this case. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
MTU_NORES
|
Message text |
Insufficient system resources! |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
IPV4/3/MTU_NORES: -MDC=1-Slot=3; Insufficient system resources! |
|
Impact |
Determine the impact according to the actual situation. |
|
Cause |
MTU index resources were insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
P2C_CONF_CONFLICT
|
Message text |
The operation is not supported. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/P2C_CONF_CONFLICT: -MDC=1-Slot=3; The operation is not supported. |
|
Impact |
The ipv6 option source-route enable command fails to be executed. |
|
Cause |
The device does not support the ipv6 option source-route enable command. |
|
Recommended action |
Do not execute the ipv6 option source-route enable command on the device. |
STATIS_NORES
|
Message text |
Failed to enable packet drop statistics collection on interface [UINT32] because of insufficient resources. |
|
Variable fields |
$1: Interface index. |
|
Severity level |
4 (Warning) |
|
Example |
L3/4/STATIS_NORES: -MDC=1-Slot=3; Failed to enable packet drop statistics collection on interface 1153 because of insufficient resources. |
|
Impact |
The packet drop statistics collection function cannot be used. |
|
Cause |
After you enable SAVA, the system notifies the QACL module of assigning TB counter resources. This message is generated when the TB counter resources are insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
L3MC messages
This section contains Layer 3 multicast messages.
BRAS_HW_NORES
|
Message text |
No enough resource! |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
L3MC/3/BRAS_HW_NORES: -MDC=1; Slot=4; No enough resource! |
|
Impact |
ACLs fail to be configured. |
|
Cause |
IGMP attack defense could not take effect on the IPoE user access interface because not enough ACL resources were available on the card. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
IPV4_ACL_NORES
|
Message text |
Not enough ACL resource |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3MC/4/IPV4_ACL_NORES: -MDC=1-Slot=4; Not enough ACL resource |
|
Impact |
ACLs fail to be deployed, and IGMP attack defense fails to take effect. |
|
Cause |
With the interface-based IGMP suppression enabled, the device deploys ACLs when detecting IGMP attacks. This message is sent when the hardware resources are not enough to deploy ACLs. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
IPV4_HW_NORES
|
Message text |
No enough resource! |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
L3MC/3/IPV4_HW_NORES: -MDC=1-Slot=4; No enough resource! |
|
Impact |
The related function fails to take effect. |
|
Cause |
The hardware resources are insufficient. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display hardware internal l3mc slot slot-number global command. · Alarm information, log messages, and configuration data. |
IPV4_IC_IPV6_ACL_NORES
|
Message text |
This board no enough acl resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3MC/4/IPV4_IC_IPV6_ACL_NORES: -MDC=1-Slot=4; This board no enough acl resource. |
|
Impact |
The related function fails to take effect. |
|
Cause |
ACL resources on the card are insufficient. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
IPV6_ACL_NORES
|
Message text |
Not enough IPv6 ACL resources |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
L3MC/4/IPV6_ACL_NORES: -MDC=1-Slot=4; Not enough IPv6 ACL resources |
|
Impact |
ACLs fail to be deployed, and MLD attack defense fails to take effect. |
|
Cause |
With the interface-based MLD suppression enabled, the device deploys ACLs when detecting MLD attacks. This message is sent when the hardware resources are not enough to deploy ACLs. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
IPV6_HW_NORES
|
Message text |
No enough resource! |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
L3MC/3/IPV6_HW_NORES: -MDC=1-Slot=4; No enough resource! |
|
Impact |
The related function fails to take effect. |
|
Cause |
The hardware resources are insufficient. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
L3MC_IPV4_ACL_NORES_INFO
|
Message text |
No enough ACL resource , P1=[UINT32]. |
|
Variable fields |
$1: Interface index. |
|
Severity level |
3 (Error) |
|
Example |
L3MC/3/L3MC-IPV4_ACL_NORES_INFO: -MDC=1-Slot=4; No enough ACL resource, p1=1153. |
|
Impact |
The related function fails to take effect. |
|
Cause |
The hardware resources are insufficient. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
MVPN_MTUNNEL_NORES
|
Message text |
MtunnelCreate No enough resource! |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
L3MC/3/MVPN_MTUNNEL_NORES: -MDC=1; MtunnelCreate No enough resource! |
|
Impact |
Multicast tunnel interfaces fail to be created. |
|
Cause |
The hardware resources used by the multicast VPN have reached the upper limit. |
|
Recommended action |
Collect the following information and then contact Technical Support for help: · Output from the display qos-acl resource slot slot-number command. · Alarm information, log messages, and configuration data. |
SRPM_NORES
|
Message text |
This module does not support SRPM. Please check your configuration. |
|
Variable fields |
N/A |
|
Severity level |
2 (Critical) |
|
Example |
L3MC/2/SRPM_NORES: -MDC=1; This module does not support SRPM. Please check your configuration. |
|
Impact |
Networking performance measurement errors occur. |
|
Cause |
This message is generated when a new member port is added to the Layer 3 aggregate group after you enable SRPM on a Layer 3 aggregate interface or a Layer 3 aggregate subinterface. |
|
Recommended action |
1. Disable SRPM on the Layer 3 aggregate interface or a Layer 3 aggregate subinterface and then add the new member port is added to the Layer 3 aggregate group, or add the new member port to a Layer 3 aggregate group that is not enabled with SRPM 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
L3VPN
This section contains L3VPN messages.
L3VPN_VRF_IFDOWN
|
Message text |
The interface bound to the VPN instance went down (VPN instance name=[STRING], Interface name=[STRING], Interface status=[STRING], VPN instance status=[STRING]). |
|
Variable fields |
$1: VPN instance name. $2: Interface name. $3: Interface status, active or inactive. $4: VPN instance status, up or down. |
|
Severity level |
6 (Informational) |
|
Example |
L3VPN/6/L3VPN_VRF_IFDOWN_ACTIVE: The interface bound to the VPN instance went down (VPN instance name=vpn1, Interface name=GE1/0/1, Interface status=active, VPN instance status=down). |
|
Impact |
The VPN instance does not have an interface to forward IPv4 traffic. |
|
Cause |
· When the VPN instance is bound to only one interface and the interface’s link layer protocol state is up: This message is generated when the interface's link layer protocol state changes from up to down or the interface is unbound from the VPN instance. · When the VPN instance is bound to multiple interfaces: This message is generated when the link layer protocol state of the last bound interface changes from up to down, or the last up interface is unbound from the VPN instance. |
|
Recommended action |
Identify whether the VPN instance is in use. If the VPN instance is not in use, unbinding the VPN instance from interfaces is normal and no action is required. If the VPN instance is in use, execute the display ip vpn-instance instance-name vpn-instance-name command to view the Interfaces field in the output. · If the Interfaces field is not displayed, it indicates that no interface is bound to the VPN instance. In this case, identify the interface for the VPN instance, execute the ip binding vpn-instance command to bind the interface to the VPN instance, and then execute the ip address command to configure an IPv4 address for the interface. · If the value of the Interfaces field is an interface or multiple interfaces, execute the display ip interface command to view interface state. ¡ If the interface physical state (current state) is down, troubleshoot the physical link faults. ¡ If the interface physical state (current state) is Administratively DOWN, execute the undo shutdown command to bring up the interface. ¡ If the interface does not have an IPv4 address, execute the iP address command to assign an IPv4 address to the interface. · If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
L3VPN_VRF_IFDOWN_CLEAR
|
Message text |
The interface bound to the VPN instance went up (VPN instance name=[STRING], Interface name=[STRING], Interface status=[STRING], VPN instance status=[STRING]). |
|
Variable fields |
$1: VPN instance name. $2: Interface name. $3: Interface status, active or inactive. $4: VPN instance status, up or down. |
|
Severity level |
6 (Informational) |
|
Example |
L3VPN/6/L3VPN_VRF_IFDOWN_CLEAR: The interface bound to the VPN instance went up (VPN instance name=vpn1, Interface name=GE1/0/1, Interface status=active, VPN instance status=up). |
|
Impact |
No negative impact on the system. |
|
Cause |
· When the VPN instance is not bound to any interface, this message is generated when an interface (with the link layer protocol state of up) is bound to the VPN instance. · When the VPN instance is bound to only one interface, this message is generated when the link layer protocol state of this interface changes from down to up. · When the VPN instance is bound to multiple interfaces and all the interfaces are in down state (link layer), this message is generated when one of the interfaces changes from down state to up state. |
|
Recommended action |
No action is required. |
L3VPN_VRF_IPV6_IFDOWN
|
Message text |
The IPv6 status of interface bound to a VPN instance went down (VPN instance name=[STRING], Interface name=[STRING]). |
|
Variable fields |
$1: VPN instance name. $2: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
L3VPN/6/L3VPN_VRF_IPV6_IFDOWN_ACTIVE: The IPv6 status of interface bound to a VPN instance went down (VPN instance name=vpn1, Interface name=GE1/0/1). |
|
Impact |
The VPN instance does not have an interface to forward IPv6 traffic. |
|
Cause |
· When the VPN instance is bound to only one interface and the interface’s IPv6 protocol state is up: This message is generated when the interface's IPv6 protocol state changes from up to down or the interface is unbound from the VPN instance. · When the VPN instance is bound to multiple interfaces: This message is generated when the IPv6 protocol state of the last bound interface changes from up to down, or the last up interface is unbound from the VPN instance. |
|
Recommended action |
· Identify whether the VPN instance is in use. If the VPN instance is not in use, unbinding the VPN instance from interfaces is normal and no action is required. If the VPN instance is in use, execute the display ip vpn-instance instance-name vpn-instance-name command to view the Interfaces field in the output. · If the Interfaces field is not displayed, it indicates that no interface is bound to the VPN instance. In this case, identify the interface for the VPN instance, execute the ip binding vpn-instance command to bind the interface to the VPN instance, and then execute the ip address command to configure an IPv4 address for the interface. · If the value of the Interfaces field is an interface or multiple interfaces, execute the display ip interface command to view interface state. ¡ If the interface physical state (current state) is down, troubleshoot the physical link faults. ¡ If the interface physical state (current state) is Administratively DOWN, execute the undo shutdown command to bring up the interface. ¡ If the interface does not have an IPv6 address (display as IPv6 is disabled), execute the ipv6 address command to assign an IPv6 address to the interface. · If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
L3VPN_VRF_IPV6_IFDOWN_CLEAR
|
Message text |
The IPv6 status of interface bound to a VPN instance went up (VPN instance name=[STRING], Interface name=[STRING]). |
|
Variable fields |
$1: VPN instance name. $2: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
L3VPN/6/L3VPN_VRF_IPV6_IFDOWN_CLEAR: The IPv6 status of interface bound to a VPN instance went up (VPN instance name=vpn1, Interface name=GE1/0/1). |
|
Impact |
No negative impact on the system. |
|
Cause |
· When the VPN instance is not bound to any interface, this message is generated when an interface (with the IPv6 protocol state of up) is bound to the VPN instance. · When the VPN instance is bound to only one interface, this message is generated when the IPv6 protocol state of this interface changes from down to up. · When the VPN instance is bound to multiple interfaces and all the interfaces are in down state (IPv6 protocol state), this message is generated when one of the interfaces changes from down state to up state. |
|
Recommended action |
No action is required. |
LAGG messages
This section contains LAGG messages.
LAGG_ACTIVE
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the active state. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_ACTIVE: Member port GE1/0/1 of aggregation group BAGG1 changed to the active state. |
|
Impact |
No negative impact on the system. |
|
Cause |
A member port in an aggregation group changed to the Selected state. |
|
Recommended action |
No action is required. |
LAGG_INACTIVE_AICFG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the port and the aggregate interface had different attribute configurations. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_AICFG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the port and the aggregate interface had different attribute configurations. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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 configuration of the member port to be the same as the attribute configuration of 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: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_BFD: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the BFD session state of the port was down. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the BFD session on the port went down. |
|
Recommended action |
1. Check for a link failure. 2. 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 link aggregation configuration of the port was incorrect. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_CONFIGURATION: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the link aggregation configuration of the port was incorrect. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because some configuration on the member port cannot be issued to the driver. |
|
Recommended action |
No action is required. |
LAGG_INACTIVE_DRNI_KEY_WRONG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the operational key of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_DRNI_KEY_WRONG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the operational key of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the operational key of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Recommended action |
Modify the peer port configuration. |
LAGG_INACTIVE_DRNI_MAC_WRONG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the system MAC address of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_DRNI_MAC_WRONG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the system MAC address of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the MAC address of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Recommended action |
Verify that the peer ports are in the same aggregation group on the peer device. |
LAGG_INACTIVE_DRNI_PRIORITY_WRONG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the system priority of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_DRNI_PRIORITY_WRONG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the system priority of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the system priority of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Recommended action |
Verify that the peer ports are in the same aggregation group on the peer device. |
LAGG_INACTIVE_DRNI_SPEED_WRONG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because its speed was different than the member ports of the peer DR interface. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_DRNI_SPEED_WRONG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because its speed was different than the member ports of the peer DR interface. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the speed of the peer port was different than the other peer ports for the DR group to which this aggregate interface belongs. |
|
Recommended action |
Modify the peer port configuration. |
LAGG_INACTIVE_DUPLEX
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the duplex mode of the port was different from that of the reference port. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_DUPLEX: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the duplex mode of the port was different from that of the reference port. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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 prevented it from being Selected. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_HARDWAREVALUE: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because of the port's hardware restriction prevented it from being Selected. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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_IFCFG_DEFAULT
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because no LACPDU was received by the reference port. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_IFCFG_DEFAULT: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because no LACPDU was received by the reference port. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because no LACPDU was received by the reference port. |
|
Recommended action |
Check whether the peer sends LACPDUs. |
LAGG_INACTIVE_IFCFG_LOOPPORT
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the reference port received its own LACPDUs. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_IFCFG_LOOPPORT: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the reference port received its own LACPDUs. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the reference port received its own LACPDUs. |
|
Recommended action |
Check the peer device for loops. |
LAGG_INACTIVE_IFCFG_NONAGG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the link of the port was not aggregatable. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_IFCFG_NONAGG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the link of the port was not aggregatable. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the link of the port was not aggregatable. |
|
Recommended action |
Editing port settings |
LAGG_INACTIVE_IRFSELECTMODE
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the port does not meet the Selected port requirements of the IRF member device it belongs to. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_IRFSELECTMODE: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the port does not meet the Selected port requirements of the IRF member device it belongs to. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the lacp irf-select command was executed. This command restricts the Selected ports in a dynamic multichassis link aggregation to one IRF member device. |
|
Recommended action |
No action is required. |
LAGG_INACTIVE_KEY_INVALID
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the port's operational key was invalid. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_KEY_INVALID: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the port's operational key was invalid. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the port's operational key was invalid. |
|
Recommended action |
Modify the reference port configuration for the reference port to use a valid operational key. |
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: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
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. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because aggregate interfaces were isolated on the device. |
|
Recommended action |
Remove aggregate interface isolation. |
LAGG_INACTIVE_LINKQUALITY_LOW
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the member port has low link quality. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_LINKQUALITY_LOW: Member port FGE1/0/50 of aggregation group BAGG1 changed to the inactive state, because the member port has low link quality. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group was set to the Unselected state because of low link quality. |
|
Recommended action |
1. Verify that the cable is securely connected and is in a good condition. Replace the cable if its quality has degraded. 2. Check the interface module for hardware failure. |
LAGG_INACTIVE_LOWER_LIMIT
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the number of Selected ports was below the lower limit. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_LOWER_LIMIT: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the number of Selected ports was below the lower limit. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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_NODEREMOVE
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the card that hosts the port was absent. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_NODEREMOVE: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the card that hosts the port was absent. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group was set to the Unselected state because the card that hosts the port was removed. |
|
Recommended action |
Verify that the card is present. |
LAGG_INACTIVE_OPERSTATE
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the peer port did not have the Synchronization flag. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_OPERSTATE: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the peer port did not have the Synchronization flag. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the peer port did not have the Synchronization flag. |
|
Recommended action |
Check whether the peer device sends LACPDUs. |
LAGG_INACTIVE_PARTNER
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the link aggregation configuration of its peer port was incorrect. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_PARTNER: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the link aggregation configuration of its peer port was incorrect. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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_PARTNER_KEY_WRONG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the operational key of the peer port was different from that of the reference port. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_PARTNER_KEY_WRONG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the operational key of the peer port was different from that of the reference port. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because the operational key of the peer port was different from that of the reference port. |
|
Recommended action |
Verify the operational key of the peer port is the same as that of the reference port. |
LAGG_INACTIVE_PARTNER_MAC_WRONG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the system MAC address of the peer port was different from that of the peer port for the reference port. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_PARTNER_MAC_WRONG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the system MAC address of the peer port was different from that of the peer port for the reference port. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state, because the system MAC address of the peer port was different from that of the peer port for the reference port. |
|
Recommended action |
Verify the system MAC address of the peer port is the same as that of the peer port for the reference port. |
LAGG_INACTIVE_PARTNER_NONAGG
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the link of the peer port was not aggregatable. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_PARTNER_NONAGG: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the link of the peer port was not aggregatable. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in aggregation group changed to the Unselected state, because the link of the peer port was not aggregatable. |
|
Recommended action |
Modify the peer port configuration. |
LAGG_INACTIVE_PHYSTATE
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the physical or line protocol state of the port was down. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_PHYSTATE: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the physical or line protocol state of the port was down. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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_PORT_DEFAULT
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the port had not received LACPDUs. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_PORT_DEFAULT: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the port had not received LACPDUs. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state because no LACPDU was received by the member port. |
|
Recommended action |
Check whether the peer sends LACPDUs. |
LAGG_INACTIVE_RDIRHANDLE
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_RDIRHANDLE: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because link-aggregation traffic redirection was triggered on the local port. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state, because link-aggregation traffic redirection was triggered on the aggregate interface. |
|
Recommended action |
Editing port settings |
LAGG_INACTIVE_REDUNDANCY
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the port was in secondary state in a redundancy group. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_ REDUNDANCY: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the port was in secondary state in a redundancy group. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in an aggregation group changed to the Unselected state, because the port was in secondary state in a redundancy group. |
|
Recommended action |
Change the port to primary state in the redundancy group. |
LAGG_INACTIVE_RESOURCE_INSUFICIE
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because hardware resources were not enough. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
3 (Error) |
|
Example |
LAGG/3/LAGG_INACTIVE_RESOURCE_INSUFICIE: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because hardware resources were not enough. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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_SECONDARY
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because it was the secondary member port in the aggregation group in 1+1 backup mode. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_SECONDARY: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because it was the secondary member port in the aggregation group in 1+1 backup mode. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port in a 1+1 backup aggregation group changed to the Unselected state because it was assigned the secondary role. |
|
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 was different from that of the reference portincorrect. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_SPEED: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the speed configuration of the port was different from that of the reference portincorrect. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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_STANDBY
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the port was in Standby state. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_STANDBY: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the port was in Standby state. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port of an aggregation group changed to the Unselected state because the port was in Standby state. |
|
Recommended action |
Check the state of the member port after a time period. If the port is in Unselected state, locate the cause and see the recommended action by executing the display link-aggregation troubleshooting command. |
LAGG_INACTIVE_STRUNK_DOWN
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the role of the aggregate interface is secondary in a smart trunk. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_INACTIVE_STRUNK_DOWN: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the role of the aggregate interface is secondary in a smart trunk. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A member port of an aggregate interface changed to the Unselected state because the aggregate interface's role changed to secondary in a smart trunk. |
|
Recommended action |
No action is required. |
LAGG_INACTIVE_UPPER_LIMIT
|
Message text |
Member port [STRING] of aggregation group [STRING] changed to the inactive state, because the number of Selected ports had reached the upper limit. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
3 (Error) |
|
Example |
LAGG/3/LAGG_INACTIVE_UPPER_LIMIT: Member port GE1/0/1 of aggregation group BAGG1 changed to the inactive state, because the number of Selected ports had reached the upper limit. |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
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. |
LAGG_LACP_MISCONNECT_ACTIVE
|
Message text |
The peer port of aggregation group [STRING] might be incorrectly connected. Local information: System priority=[UINT16], system MAC address=[STRING], local operational key=[UINT16], port priority=[UINT16], index=[UINT16] Received LACPDU information: System priority=[UINT16], system MAC address=[STRING], operational key=[UINT16], port priority=[UINT16], index=[UINT16] |
|
Variable fields |
$1: Link aggregation group type and ID. $2: System priority. $3: System MAC address. $4: Operational key. $5: Port priority. $6: Port index assigned by the link aggregation module. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_LACP_MISCONNECT_ACTIVE: The peer port of aggregation group BAGG1 might be incorrectly connected. Local information: System priority=32768 system MAC address=40c0-0c41-0100, local operational key=1, port priority=32768, index=1 Received LACPDU information: System priority=32768, system MAC address=0000-0000-0000, operational key=0, port priority=32768, index=0 |
|
Impact |
The member port cannot forward the service traffic. |
|
Cause |
A peer port of an aggregation group was incorrectly connected. |
|
Recommended action |
Verify that the link to the peer port is correctly connected and the peer port joins the correct aggregation group. |
LAGG_LACP_MISCONNECT_CLEAR
|
Message text |
The peer port of aggregation group [STRING] was correctly connected. Local information: System priority=[UINT16], system MAC address=[STRING], local operational key=[UINT16], port priority=[UINT16], index=[UINT16] Received LACPDU information: System priority=[UINT16], system MAC address=[STRING], local operational key=[UINT16], port priority=[UINT16], index=[UINT16] |
|
Variable fields |
$1: Link aggregation group type and ID. $2: System priority. $3: System MAC address. $4: Operational key. $5: Port priority. $6: Port index assigned by the link aggregation module. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_LACP_MISCONNECT_CLEAR: The peer port of aggregation group BAGG1 was correctly connected. Local information: System priority=32768 system MAC address=40c0-0c41-0100, local operational key=1, port priority=32768, index=1 Received LACPDU information: System priority=32768 system MAC address=40c0-0c41-0100, local operational key=1, port priority=32768, index=1 |
|
Impact |
No negative impact on services. |
|
Cause |
The incorrect connection issue was resolved on a peer port of an aggregation group. |
|
Recommended action |
No action is required. |
LAGG_LACP_RECEIVE_TIMEOUT
|
Message text |
LACPDU reception timed out on member port [STRING] in aggregation group [STRING]. |
|
Variable fields |
$1: Interface type and interface number. $2: Link aggregation group type and ID. |
|
Severity level |
6 (Informational) |
|
Example |
LAGG/6/LAGG_RECEIVE_TIMEOUT: LACPDU reception timed out on member port GE1/0/1 in aggregation group BAGG1. |
|
Impact |
The impact on the system depends on the actual situation. |
|
Cause |
LACPDU reception timed out on the reference port in an aggregation group. |
|
Recommended action |
Verify that the member ports in the aggregation group are correctly connected. |
LDP messages
This section contains LDP messages.
LDP_SESSION_ABNORM_MSG
|
Message text |
Received incorrect messages ([STRING]) by the session ([STRING], [STRING]). |
|
Variable fields |
$1: Error message type. Options include: · Label Request Message · Label Mapping Message · Label Release Message · Label Withdraw Message · Label Abort Request Message · Initialization Message · Keepalive Message · Notification Message · Address Message · Address Withdraw Message · A hyphen (-) indicates that the message type cannot be identified. $2: LDP ID of the peer. If the system cannot obtain the peer LDP ID, this field displays 0.0.0.0. $3: VPN instance name. If the session belongs to the public network, this field displays public instance. |
|
Severity level |
5 (Notification) |
|
Example |
LDP/5/LDP_SESSION_ABNORM_MSG: Received incorrect messages (Initialization Message) by the session (10.200.0.60:0, public instance). |
|
Impact |
The LDP session might go down. |
|
Cause |
The device received an erroneous packet from the LDP peer. |
|
Recommended action |
Verify that the LDP configuration is correct at both ends of the LDP session. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LDP_SESSION_AUTH_FAIL
|
Message text |
LDP session ([STRING], [STRING]) failed [STRING] authentication. |
|
Variable fields |
$1: IP address and port number used by the peer to establish a TCP connection. $2: VPN instance name. If the session belongs to the public network, this field displays public instance. $3: Security authentication type, MD5 or keychain. |
|
Severity level |
5 (Notification) |
|
Example |
LDP/5/LDP_SESSION_AUTH_FAIL: LDP session (2.2.2.9:61890, public instance) failed MD5 authentication. |
|
Impact |
The LDP session cannot be established. |
|
Cause |
LDP security authentication fails because the security authentication configurations at both ends of the LDP session are inconsistent. |
|
Recommended action |
Modify the LDP session security authentication settings to ensure consistent settings on both ends of the LDP session. |
LDP_SESSION_CHG
|
Message text |
Session ([STRING], [STRING]) is [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, up or down. $4: Reason for the down state error. This field is displayed only when the state is down. $5: Session information. This field is displayed only when the state is down. The following information will be displayed: · LocalTransportAddr—Local transport address. · PeerTransportAddr—Peer transport address. · SessionRole—Role of the local LSR in the session, which can be Active or Passive. · SessionUpTime—Period of time (in DD:HH:MM format) during which the session was in Operational state. · KeepaliveTime—Negotiated keepalive time, in seconds. · KeepaliveSentCount—Number of keepalive messages sent locally. · KeepaliveRcvdCount—Number of keepalive messages received locally. · GracefulRestart—Indicates the LDP GR capability of the peer. ¡ On—LDP GR is enabled on the peer. ¡ Off—LDP GR is disabled on the peer. · SocketID—Socket ID of the session. · WaitSendMsgCount—Number of TCP messages to be sent. · CPUusage—The CPU usage rate when the session was down. · MemoryState—Memory usage threshold level when the session was down. ¡ Normal—Memory usage is normal. ¡ Minor—Memory usage has reached the level 1 threshold. ¡ Severe—Memory usage has reached the level 2 threshold. ¡ Critical—Memory usage has reached the level 3 threshold. |
|
Severity level |
4 (Warning) |
|
Example |
LDP/4/LDP_SESSION_CHG: Session (22.22.22.2:0, public instance) is up. LDP/4/LDP_SESSION_CHG: Session (22.22.22.2:0, VPN instance: vpn1) is down (hello hold timer expired). (LocalTransportAddr=11.1.1.1, PeerTransportAddr=22.2.2.2, SessionRole=Passive, SessionUpTime=0000:00:35, KeepaliveTime=45s, KeepaliveSentCount=143, KeepaliveRcvdCount=148, GracefulRestart=Off, SocketID=35, WaitSendMsgCount=0, CPUUsage=19%, MemoryState=Normal) |
|
Impact |
When the session state changes to up, there is no negative impact on the system. When the session state changes to down, all services based on this LDP session will be interrupted. |
|
Cause |
The session state changed. |
|
Recommended action |
When the session state changed to up, no action is required. When the session state changed to down, check the interface state, link state, and other configurations depending on the reason displayed. Possible reasons and the recommended actions are as follows: · interface not operational—The interface is unavailable. Verify that the interface state is normal and has correctly configured with an IPv4 or IPv6 address. · MPLS disabled on interface—MPLS was disabled on the interface. Use the mpls enable command in interface view to enable LDP on the interface. · LDP disabled on interface—LDP was disabled on the interface. Use the mpls ldp enable command in interface view to enable LDP on the interface. · VPN instance changed on interface—The VPN instance to which the interface belongs was changed. Use the ip binding vpn-instance command in interface view to change the association between the interface and the VPN instance. · LDP instance deleted—The LDP-VPN instance was deleted. Use the vpn-instance command in LDP view to enable the LDP capability for the specified VPN instance. · targeted peer deleted—The targeted peer was deleted manually. Use the target-peer command in LDP view to restore the remote session configuration. · L2VPN disabled targeted peer—L2VPN disabled the targeted peer. To resolve this issue: ¡ In an MPLS L2VPN network, enable MPLS and L2VPN, create a cross-connect, and then execute the peer command in cross-connect view to create a PW for the cross-connect. ¡ In a VPLS network, enable MPLS and L2VPN, create a VSI, and then execute the peer command in VSI view to create a PW for VPLS. · TE tunnel disabled targeted peer—A TE tunnel disabled the targeted peer. To resolve this issue: ¡ Execute the display interface tunnel command to check whether the TE tunnel interface is in up state. If not, verify that MPLS and MPLS TE are enabled on all the devices and interfaces that the MPLS TE tunnel traverses. If the MPLS TE tunnel is signaled by using RSVP, you must verify that RSVP is enabled, link bandwidth and affinity settings are correct, and RSVP verification configuration is correct on all the devices and interfaces that the MPLS TE tunnel traverses. If the MPLS TE tunnel is established statically, verify that the static CRLSP or SRLSP related settings are correct. ¡ Execute the display mpls ldp interface command to check whether the MPLS and LDP capabilities are correctly configured on the interface. If not, execute the mpls enable command and the mpls ldp enable command on the interface. · session protection disabled targeted peer—Execute the session protection command in LDP view to restore the session protection configuration. · OSPF Remote LFA disabled targeted peer—OSPF calculated that the PQ node address of the remote LFA was changed, so it disabled the targeted peer corresponding to the old PQ node address. This is normal when the network topology changes. No action is required. · IS-IS Remote LFA disabled targeted peer—IS-IS calculated that the PQ node address of the remote LFA was changed, so it disabled the targeted peer corresponding to the old PQ node address. This is normal when the network topology changes. No action is required. · process deactivated—The LDP process was downgraded. The LDP session will be restored automatically after the LDP process is upgraded. As a best practice, use the non-stop-routing command in LDP view to enable NSR to reduce the impact of process upgrade and downgrade. · failed to receive the initialization message—Check the link status by executing the ping -a local-address -c count dest-address command. The local and destination addresses are the local and destination device LSR IDs (which can be obtained by using the display mpls ldp parameter command), and the count is 100 or larger. If packet loss occurs on the link, collect alarm information and configuration data, and then contact Technical Support for help. · graceful restart reconnect timer expired—Check the link status by executing the ping -a local-address -c count dest-address command. The local and destination addresses are the local and destination device LSR IDs (which can be obtained by using the display mpls ldp parameter command), and the count is 100 or larger. If packet loss occurs on the link, collect alarm information and configuration data, and then contact Technical Support for help. · failed to recover adjacency by NSR—Execute the display ha service-group ldp command to view the value of the State field in the command output. The value Realtime Backup indicates the complete of data backup. You must wait the state value to become Realtime Backup, and then perform a primary/backup switchover. · failed to upgrade session by NSR—Execute the display ha service-group ldp command to view the value of the State field in the command output. The value Realtime Backup indicates the complete of data backup. You must wait the state value to become Realtime Backup, and then perform a primary/backup switchover. · closed the GR session—Check the link status by executing the ping -a local-address -c count dest-address command. The local and destination addresses are the local and destination device LSR IDs (which can be obtained by using the display mpls ldp parameter command), and the count is 100 or larger. If packet loss occurs on the link, collect alarm information and configuration data, and then contact Technical Support for help. · keepalive hold timer expired—Check the link status by executing the ping -a local-address -c count dest-address command. The local and destination addresses are the local and destination device LSR IDs (which can be obtained by using the display mpls ldp parameter command), and the count is 100 or larger. If packet loss occurs on the link, collect alarm information and configuration data, and then contact Technical Support for help. · hello hold timer expired—Check whether the link is stable. If not, replace the link or clear the link faults to stabilize the link. · session reset—The session was manually reset. The session can be reestablished automatically. No action is required. · TCP connection down—Check the link status by executing the ping -a local-address -c count dest-address command. The local and destination addresses are the local and destination device LSR IDs (which can be obtained by using the display mpls ldp parameter command), and the count is 100 or larger. If packet loss occurs on the link, collect alarm information and configuration data, and then contact Technical Support for help. · received a fatal notification message—View the failure reason carried in the notification message, and then process accordingly. · internal error—Collect alarm information and configuration data, and then contact Technical Support for help. · memory in critical state—The memory has entered level 3 alarm state. Collect alarm information and configuration data, and then contact Technical Support for help. · transport address changed on interface—Execute the mpls ldp transport-address command in interface view to restore the transport address on the interface. · MD5 password changed—Execute the display this command in LDP view to display the md5-authentication configuration. Make sure the MD5 passwords configured on both sides of the session are the same. · Auto targeted peer deleted—The automatically created remote session was deleted. Execute the display this command in LDP view to display the accept target-hello configuration: ¡ If no accept target-hello configuration exists, check whether the configuration has been mistakenly deleted. ¡ If the accept target-hello prefix-list prefix-list-name has been configured, execute the display ip prefix-list name prefix-list-name command to check whether the IP prefix list permits the remote device LSR ID. If not, modify the IP prefix list configuration. ¡ In other cases, collect alarm information and configuration data, and then contact Technical Support for help. · Modify LDP local LSR ID—The modification caused the session to be down. This is a normal event. You can wait the session to come up and no action is required. · LDP process stopped—Execute the display current-configuration configuration ldp command to check whether the LDP configuration exists. If the LDP configuration exists, it indicates that the LDP process was stopped abnormally and you need to collect alarm information and configuration data, and then contact Technical Support for help. If the LDP configuration does not exist, check whether the configuration was mistakenly deleted. The following information indicates that the LDP configuration exists: The following information indicates that the LDP configuration does not exist: |
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 (Notification) |
|
Example |
LDP/5/LDP_SESSION_GR: Session (22.22.22.2:0, VPN instance: vpn1): Start reconnection. |
|
Impact |
When the state of the session graceful restart is Reconnection failed, all services based on the LDP session are interrupted. Other states have no negative impact on the system. |
|
Cause |
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 message. When the graceful restart state Reconnection failed is displayed, check the interface state, link state, TCP connection state, and other related configurations according to the reason for the session graceful restart. For details, see the recommended action in "LDP_SESSION_CHG." No action is required for other graceful restart states. |
LDP_SESSION_INIT_EXCEED
|
Message text |
Session ([STRING], [STRING], [STRING]) negotiation failed after [UINT32] attempts. |
|
Variable fields |
$1: LDP ID of the peer. If the system cannot obtain the peer LDP ID, it displays 0.0.0.0. $2: VPN instance name. If the session belongs to the public network, this field displays public instance. $3: Index of the LDP instance. $4: Number of times the Initialization message is transmitted. |
|
Severity level |
5 (Notification) |
|
Example |
LDP/5/LDP_SESSION_INIT_EXCEED: Session (2.2.2.9, public instance, 2) negotiation failed after 2 attempts. |
|
Impact |
The LDP session cannot be established. |
|
Cause |
When the device transmits the Initialization message to negotiate LDP session parameters with a peer, the LDP session negotiation fails. The device has sent the Initialization message for the maximum number of times but the session negotiation still fails. |
|
Recommended action |
Verify that session parameters are configured correctly. · Check the keepalive hold time configured on the remote device. If the hold time is 0, change it to a non-0 value. · Check the label advertisement mode on the remote device. Comware devices do not support Downstream On Demand (DoD) mode, if the remote device is configured with DoD mode, change it to Downstream Unsolicited (DU) mode. · Check the loop detection settings on the remote device. Enable loop detection on the remote device or set the PV limit to 0 if loop detection is disabled. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Notification) |
|
Example |
LDP/5/LDP_SESSION_SP: Session (22.22.22.2:0, VPN instance: vpn1): Hold up the session. |
|
Impact |
When the state of the session protection is Session recovery failed, if the link hello adjacency cannot be established before the session hold timer expires, all services based on this LDP session will be interrupted. Other session protection states do not have negative impact on the system. |
|
Cause |
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 |
When the state of the session protection is Session recovery failed, check the interface state, link state, and other related configurations according to the reason for the LDP session failure. For details, see the recommended action in "LDP_ADJACENCY_DOWN." No action is required for other session protection states. |
LDP_ADJACENCY_DOWN
|
Message text |
ADJ ([STRING], [STRING], [STRING]) is down [STRING]. ([STRING]) |
|
Variable fields |
$1: LDP ID of the peer. Value 0.0.0.0:0 indicates that the peer LDP ID cannot be obtained. $2: Name of the VPN instance. Value public instance indicates that the session belongs to the public network. $3: Interface name. This field is not available for a targeted hello. $4: Reason for the down state of the adjacency. $: Information about the adjacency: · Type—Adjacency type. ¡ Link—Link Hello adjacency. ¡ Target—Targeted Hello adjacency. · SourceAddr—Source address of the adjacency. · DestinationAddr—Destination address of the adjacency. · TransportAddr—Transport address of the adjacency. · ADJUpTime—Duration of the adjacency in up state. The duration time is in DD:HH:MM format. · HelloHoldTime—Hello holding time, in seconds. · HelloSentCount—Number of Hello message sent locally. · HelloRcvdCount—Number of Hello message received locally. |
|
Severity level |
5 (Notification) |
|
Example |
LDP/5/LDP_ADJACENCY_DOWN: ADJ (10.200.0.60:0, public instance, GE2/0/1) is down (Hello timer expired). (Type=Link, SourceAddr=100.12.1.2, DestinationAddr=224.0.0.2, TransportAddr=22.2.2.2, ADJUpTime=0000:00:02, HelloHoldTime=15s, HelloSentCount=27, HelloRcvdCount=25) |
|
Impact |
The LDP session between the local device and the LDP adjacency might go down. |
|
Cause |
The state of the LDP adjacency changed to down. |
|
Recommended action |
When the LDP adjacency is down, check the interface state, link state, and other configurations depending on the reason displayed. Possible reasons and the recommended actions are as follows: · VPN instance changed on interface—The VPN instance to which the interface belongs was changed. Use the ip binding vpn-instance command in interface view to change the association between the interface and the VPN instance. · LDP disabled on interface—LDP was disabled on the interface. Use the mpls ldp enable command in interface view to enable LDP on the interface. · MPLS disabled on interface—MPLS was disabled on the interface. Use the mpls enable command in interface view to enable LDP on the interface. · interface not operational—The interface is unavailable. Verify that the interface state is normal and has correctly configured with an IPv4 or IPv6 address. · targeted peer deleted—The targeted peer was deleted manually. Use the target-peer command in LDP view to restore the remote session configuration. · L2VPN disabled targeted peer—L2VPN disabled the targeted peer. To resolve this issue: ¡ In an MPLS L2VPN network, enable MPLS and L2VPN, create a cross-connect, and then execute the peer command in cross-connect view to create a PW for the cross-connect. ¡ In a VPLS network, enable MPLS and L2VPN, create a VSI, and then execute the peer command in VSI view to create a PW for VPLS. · TE tunnel disabled targeted peer—A TE tunnel disabled the targeted peer. To resolve this issue: ¡ Execute the display interface tunnel command to check whether the TE tunnel interface is in up state. If not, verify that MPLS and MPLS TE are enabled on all the devices and interfaces that the MPLS TE tunnel traverses. If the MPLS TE tunnel is signaled by using RSVP, you must verify that RSVP is enabled, link bandwidth and affinity settings are correct, and RSVP verification configuration is correct on all the devices and interfaces that the MPLS TE tunnel traverses. If the MPLS TE tunnel is established statically, verify that the static CRLSP or SRLSP related settings are correct. ¡ Execute the display mpls ldp interface command to check whether the MPLS and LDP capabilities are correctly configured on the interface. If not, execute the mpls enable command and the mpls ldp enable command on the interface. · session protection disabled targeted peer—Execute the session protection command in LDP view to restore the session protection configuration. · OSPF Remote LFA disabled targeted peer—OSPF calculated that the PQ node address of the remote LFA was changed, so it disabled the targeted peer corresponding to the old PQ node address. This is normal when the network topology changes. No action is required. · IS-IS Remote LFA disabled targeted peer—IS-IS calculated that the PQ node address of the remote LFA was changed, so it disabled the targeted peer corresponding to the old PQ node address. This is normal when the network topology changes. No action is required. · process deactivated—The LDP process was downgraded. The LDP session will be restored automatically after the LDP process is upgraded. As a best practice, use the non-stop-routing command in LDP view to enable NSR to reduce the impact of process upgrade and downgrade. · LDP instance deleted—The LDP-VPN instance was deleted. Use the vpn-instance command in LDP view to enable the LDP capability for the specified VPN instance. · hello hold timer expired—The hello hold timer expired. Check whether the link is stable. If not, replace the link or clear the link faults to stabilize the link. · no IPv6 transport address—No IPv6 transport address was configured. Use the mpls ldp transport-address command in interface view or LDP peer view to configure an IPv6 transport address. |
LIF messages
This section contains LIF messages.
HW_NORES
|
Message text |
Not enough resources for [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
LIF/6/HW_NORES: -MDC=1-Slot=5; Not enough resources for Route-Aggregation1.1. |
|
Impact |
QinQ termination is unavailable on the interface. |
|
Cause |
Hardware resources were insufficient for enabling QinQ termination on the interface. |
|
Recommended action |
1. View the QinQ termination configurations by using the display current-configuration | include second-dot1q command. 2. Delete the unused configurations by using the undo vlan-type dot1q vid second-dot1q command. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help.. |
IF_RAGG_FAILED
|
Message text |
Failed to assign the interface to the link aggregation group, because the corresponding aggregate interface has subinterfaces with some VLAN termination configuration not supported by the board of this interface. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/IF_RAGG_FAILED: -MDC=1; Failed to assign the interface to the link aggregation group, because the corresponding aggregate interface has subinterfaces with some VLAN termination configuration not supported by the board of this interface. |
|
Impact |
Failed to assign the Ethernet interface to the link aggregation group. |
|
Cause |
Failed to assign the Ethernet interface to the link aggregation group, because the corresponding aggregate interface has subinterfaces with some VLAN termination configuration not supported by the card of this Ethernet interface. |
|
Recommended action |
1. Delete the aggregate subinterface and then assign the Ethernet interface to the link aggregate group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MAC_INCORRECT
|
Message text |
Pattern 1: Incorrect MAC address. The MAC address of [STRING] must range from [UCHAR] [UCHAR]-[UCHAR] [UCHAR]-[UCHAR] [UCHAR] to [UCHAR] [UCHAR]-[UCHAR] [UCHAR]-[UCHAR] [UCHAR]. Pattern 2: Incorrect MAC address. The MAC address of the interface must range from [UCHAR] [UCHAR]-[UCHAR] [UCHAR]-[UCHAR] [UCHAR] to [UCHAR] [UCHAR]-[UCHAR] [UCHAR]-[UCHAR] [UCHAR]. |
|
Variable fields |
Pattern 1: $1: Interface name. $2-$7: Configured start MAC addresses. $8-$13: Configured end MAC addresses. Pattern 2: $1-$6: Configured start MAC addresses. $7-$12: Configured end MAC addresses. |
|
Severity level |
3 (Error) |
|
Example |
Pattern 1: LIF/3/MAC_INCORRECT: -MDC=1-Slot=3; Incorrect MAC address. The MAC address of Ten-GigabitEthernet3/0/1 must range from 0000-1111-2222 to 1111-2222-3333 Pattern 2: LIF/3/MAC_INCORRECT: -MDC=1-Slot=3; Incorrect MAC address. The MAC address of the interface must range from 0000-1111-2222 to 1111-2222-3333 |
|
Impact |
The configured MAC address does not take effect because of it is not in the specified range. |
|
Cause |
The configured MAC address is in the specified range. |
|
Recommended action |
1. Configure the MAC address range from 0000-1111-2222 to 1111-2222-3333. Make sure the configured MAC address is in the specified range. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
OUTLIFID_NORES
|
Message text |
Not enough OutlifID resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
LIF/4/OUTLIFID_NORES: -MDC=1-Slot=3; Not enough OutlifID resource. |
|
Impact |
The card failed to learn new ARP entries, ND entries, or non-host routes. Traffic forwarding failures might occur. |
|
Cause |
The card failed to learn new ARP entries, ND entries, or non-host routes because of insufficient OutlifID resources. Traffic forwarding failures might occur. |
|
Recommended action |
1. Delete redundant configuration on the device. 2. Remove redundant interfaces on the device. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKTCNT_NOTSPT
|
Message text |
This board does not support traffic statistics on the VLAN interface. |
|
Variable fields |
N/A |
|
Severity level |
2 (Critical) |
|
Example |
LIF/2/IF: -MDC=1-Slot=3; This board does not support traffic statistics on the VLAN interface. |
|
Impact |
The board does not support traffic statistics on the VLAN interface. |
|
Cause |
An interface on a board does not support traffic statistics for the VLAN interface of a VLAN to which the interface belongs. |
|
Recommended action |
1. The board does not support traffic statistics on the VLAN interface if the interfaces on the following cards are added to the specified VLAN: , , , . 2. Delete the interface on the card from the VLAN, and then enable the packet statistics function of the VLAN interface. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QINQ_SUBVLAN_CFGERR
|
Message text |
Subinterface [STRING] only supports VLAN termination by the vlan-type dot1q vid [INT32] command. |
|
Variable fields |
$1: Subinterface name. $2: VLAN ID. |
|
Severity level |
5 (Notification) |
|
Example |
LIF/5/QINQ_SUBVLAN_CFGERR: -MDC=1; Subinterface VE-L3VPN1.1 only supports VLAN termination by the vlan-type dot1q vid 1 command. |
|
Impact |
1. QinQ termination is unavailable on the subinterface. 2. The subinterface cannot terminate packets with the Layer 1 VLAN ID as the subinterface number. |
|
Cause |
The specified L3VE subinterface supports only dot1q termination, and can terminate only packets with the Layer 1 VLAN ID as the subinterface number. |
|
Recommended action |
1. When configuring dot1q termination on a subinterface, make sure the Layer 1 VLAN ID to be terminated is the same as the subinterface number. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QINQ_SUBVLAN_NOTSPT
|
Message text |
Subinterface [STRING] not supports QINQ VLAN termination. |
|
Variable fields |
$1: Subinterface name. |
|
Severity level |
5 (Notification) |
|
Example |
LIF/5/QINQ_SUBVLAN_NOTSPT: -MDC=1-Slot=3; Subinterface Ten-GigabitEthernet3/0/1.2048 not supports QINQ VLAN termination. |
|
Impact |
The subinterface does not support the user-vlan dot1q vid second-dot1q command. The subinterface does not support the vlan-type dot1q vid second-dot1q command. |
|
Cause |
The subinterface does not support VLAN QinQ termination. |
|
Recommended action |
1. Configure the interface that supports VLAN QinQ termination. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QINQ_SUBVLAN_STARTERR
|
Message text |
Subinterface [STRING] only supports VLAN termination by commands starting with vlan-type dot1q vid [INT32]. |
|
Variable fields |
$1: Subinterface name. $2: VLAN ID. |
|
Severity level |
5 (Notification) |
|
Example |
LIF/5/QINQ_SUBVLAN_STARTERR: -MDC=1-Slot=3; Subinterface Ten-GigabitEthernet3/0/1.2048 only supports VLAN termination by commands starting with vlan-type dot1q vid 2048. |
|
Impact |
1. If the Layer 1 VLAN ID to be terminated is not the same as the subinterface number, the subinterface does not support dot1q termination. 2. If the Layer 1 VLAN ID to be terminated is not the same as the subinterface number, the subinterface does not support QinQ termination. |
|
Cause |
A subinterface only supports terminating packets with the Layer 1 VLAN ID as the subinterface number. |
|
Recommended action |
1. When configuring dot1q termination or QinQ termination on a subinterface, make sure the Layer 1 VLAN ID to be terminated is the same as the subinterface number. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QINQ_UNTAG_DEFAULT_NOTSPT
|
Message text |
The board in slot [UINT16] doesn't support untagged or default termination. Or The board doesn't support untagged or default termination. |
|
Variable fields |
$1: Slot number. |
|
Severity level |
3 (Error) |
|
Example |
LIF/3/QINQ_UNTAG_DEFAULT_NOTSPT: -MDC=1-Slot=3; The board in slot 3 doesn't support untagged or default termination. |
|
Impact |
The interfaces on the board do not support untagged or default termination. |
|
Cause |
¡ a member port does not support untagged termination or default termination. The system will prompt that the card does not support untagged termination or default termination. |
|
Recommended action |
1. Configure the interface that supports untagged termination or default termination. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QINQ_USERVLAN_CHK
|
Message text |
The user-vlan configuration conflicts with [STRING] configuration. To avoid conflicts, do not configure both features on interface [STRING]. |
|
Variable fields |
$1: Feature configuration: · ip subscriber l2vpn-leased—IPoE L2VPN-leased user configuration. · ip subscriber routed enable—IPoE configuration in Layer 3 access mode. · portal—Portal authentication configuration. $2: Subinterface name. |
|
Severity level |
4 (Warning) |
|
Example |
LIF/4/QINQ_USERVLAN_CHK: -MDC=1-Slot=4; The user-vlan configuration conflicts with portal configuration. To avoid conflicts, do not configure both features on interface Route-Aggregation1.2. |
|
Impact |
User VLAN termination is unavailable on the subinterface. |
|
Cause |
User VLAN termination conflicts with one of the following configurations on the subinterface: · Portal authentication configuration (portal [ ipv6 ] enable). · IPoE L2VPN-leased user configuration (ip subscriber l2vpn-leased). · IPoE configuration in Layer 3 access mode (ip subscriber routed enable). |
|
Recommended action |
1. Execute the display this command in subinterface view to check for conflicting configurations. If conflicting configurations are present on the subinterface, remove the conflicting configurations according to the actual service requirements. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QINQ_USERVLAN_NORES
|
Message text |
Pattern 1: Not enough resources for user-vlan QINQ termination on [STRING]. Pattern 2: Not enough resources for user-vlan QINQ termination on [INT32]. |
|
Variable fields |
$1: Subinterface name. $2: Interface index. |
|
Severity level |
4 (Warning) |
|
Example |
LIF/4/QINQ_USERVLAN_NORES: -MDC=1-Slot=5; Not enough resources for user-vlan QINQ termination on Route-Aggregation1.1. |
|
Impact |
Failed to enable QinQ termination on the subinterface. |
|
Cause |
QinQ termination configured by using the user-vlan dot1q vid second-dot1q command failed to be enabled on a subinterface because of insufficient hardware resources. |
|
Recommended action |
1. When resources are insufficient for configure user VLAN termination on a subinterface, use the display current-configuration | include second-dot1q command to view the current user VLAN QinQ termination configuration. Use the undo user-vlan dot1q vid second-dot1q command to disable user VLAN QinQ termination. 2. Remove configurations that are not used currently to release resources. 3. When resources are insufficient for adding a member interface to an aggregate group, use the display link-aggregation verbose command to view the aggregate group configuration. Use the undo port link-aggregation group command to remove member ports that are not used currently from the aggregation group to release resources. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QINQ_VLAN_NORES
|
Message text |
Not enough resources for QinQ termination. |
|
Variable fields |
N/A |
|
Severity level |
2 (Critical) |
|
Example |
LIF/2/QINQ_VLAN_NORES: -MDC=1-Slot=3; Not enough resources for QinQ termination. |
|
Impact |
Failed to enable QinQ termination. |
|
Cause |
The card does not have enough hardware resources for user VLAN QinQ termination probably due to one of the following reasons: · A large number of IPoE or PPPoE users have come online. · A majority of interfaces on the card are used for user VLAN QinQ termination. |
|
Recommended action |
1. When resources are insufficient for configure user QinQ termination on a subinterface, use the display current-configuration | include second-dot1q command to view the current user QinQ termination configuration. Use the undo user-vlan dot1q vid second-dot1q command to disable QinQ termination. 2. Remove configurations that are not used currently to release resources. 3. When resources are insufficient for adding a member interface to an aggregate group, use the display link-aggregation verbose command to view the aggregate group configuration. Use the undo port link-aggregation group command to remove member ports that are not used currently from the aggregation group to release resources. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SUB_SPT_VID
|
Message text |
Subinterface [STRING] only supports VLAN termination by commands starting with vlan-type dot1q vid [INT32]. |
|
Variable fields |
$1: Subinterface name. $2: VLAN ID. |
|
Severity level |
5 (Notification) |
|
Example |
LIF/5/SUB_SPT_VID: -MDC=1-Slot=1; Subinterface Ten-GigabitEthernet3/0/1.2048 only supports VLAN termination by commands starting with vlan-type dot1q vid 2048. |
|
Impact |
1. If the Layer 1 VLAN ID to be terminated is not the same as the subinterface number, the subinterface does not support dot1q termination. 2. If the Layer 1 VLAN ID to be terminated is not the same as the subinterface number, the subinterface does not support QinQ termination. |
|
Cause |
A subinterface only supports terminating packets with the Layer 1 VLAN ID as the subinterface number. |
|
Recommended action |
1. When configuring dot1q termination or QinQ termination on a subinterface, make sure the Layer 1 VLAN ID to be terminated is the same as the subinterface number. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help |
LIPC messages
This section contains Leopard inter-process communication (LIPC) messages.
LIPC_DOWN
|
Message text |
The quality of the link is poor. 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 (Warning) |
|
Example |
LIPC/4/LIPC_DOWN: The quality of the link is poor. Owner=1, VRF=0, local address/port=0/20415, remote address/port=8/10515. |
|
Impact |
Communication between processes will be affected. |
|
Cause |
Processes will establish an LIPC link during internal communication. LIPC STCP automatically checks the link quality at intervals and outputs this log when the link quality is detected poor. |
|
Recommended action |
The system will try to restore the LIPC link of poor quality automatically. If the restoration fails, the system will terminate the LIPC link automatically and create a new one. |
LIPC_MTCP_CHECK
|
Message text |
Data stays in the receive buffer for an over long time. Owner=[STRING], VRF=[INTEGER], MDC=[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: MDC ID of the LIPC link. $4: Multicast group ID of the LIPC link. $5: Multicast group member ID of the LIPC link. |
|
Severity level |
4 (Warning) |
|
Example |
LIPC/4/LIPC_MTCP_CHECK: Data stays in the receive buffer for an over long time. Owner=fsd, VRF=0, MDC=1, Group=134, MID=10001. |
|
Impact |
Processes might operate incorrectly. |
|
Cause |
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 |
Collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
LIPC_STCP_CHECK
|
Message text |
Data stays in the receive buffer for an over long time. Owner=[STRING], VRF=[INTEGER], MDC=[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: ID of the MDC to which the local node on the LIPC link belongs. $4: LIP address of the local node. $5: Port number of the local node. $6: LIP address of the remote node. $7: Port number of the remote node. |
|
Severity level |
4 (Warning) |
|
Example |
LIPC/4/LIPC_STCP_CHECK: Data stays in the receive buffer for an over long time. Owner=fsd, VRF=0, MDC=1, local address/port=8/10515, remote address/port=0/20415. |
|
Impact |
Processes might operate incorrectly. |
|
Cause |
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 |
Collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
LIPC_SUDP_CHECK
|
Message text |
Data stays in the receive buffer for an over long time. Owner=[STRING], VRF=[INTEGER], MDC=[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: MDC ID of the LIPC link. $4: Port number of the local node. $5: IP address of the local node. $6: LIP address of the remote node. $7: Port number of the remote node. |
|
Severity level |
4 (Warning) |
|
Example |
LIPC/4/LIPC_SUDP_CHECK: Data stays in the receive buffer for an over long time. Owner=snmpd, VRF=0, MDC=1, local address/port=0/10525, remote address/port=32768/0. |
|
Impact |
Processes might operate incorrectly. |
|
Cause |
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 |
Collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
PORT_CHANGE
|
Message text |
STCP: Node where the listening port number [INT] (MDC: [INT] VRF: [INT]) resides changed from LIP [INT] to LIP [INT]. |
|
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 (Notification) |
|
Example |
LIPC/5/PORT_CHANGE: Node where the listening port number 620 (MDC: 1 VRF: 1) resides changed from LIP 1 to LIP 3. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Informational) |
|
Example |
LLDP/6/LLDP_CREATE_NEIGHBOR: Nearest bridge agent neighbor created on port GigabitEthernet1/0/1 (IfIndex 599), neighbor's chassis ID is 3822-d666-ba00, port ID is GigabitEthernet1/0/1. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Informational) |
|
Example |
LLDP/6/LLDP_DELETE_NEIGHBOR: Nearest bridge agent neighbor deleted on port GigabitEthernet1/0/1 (IfIndex 599), neighbor's chassis ID is 3822-d666-ba00, port ID is GigabitEthernet1/0/1. |
|
Impact |
The LLDP neighbor is disconnected. |
|
Cause |
The port received a deletion message when a neighbor was deleted. |
|
Recommended action |
1. View related settings on the neighboring device to identify whether the neighboring device is disabled with LLDP. ¡ If LLDP is disabled on the neighboring device, execute the lldp enable and lldp global enable commands to enable LLDP. ¡ If LLDP is enabled on the neighboring device, go to step 2. 2. Execute the display interface command to identify whether a link failure occurs between the local device and the neighboring device. ¡ If a link failure occurs, troubleshoot the link failure. If the link failure cannot be cleared, go to step 3. ¡ If no link failure occurs, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
LLDP/6/LLDP_LESS_THAN_NEIGHBOR_LIMIT: The number of nearest bridge agent neighbors maintained by port GigabitEthernet1/0/1 (IfIndex 599) is less than 5, and new neighbors can be added. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of the neighbors for a port changes. |
|
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 |
4 (Warning) |
|
Example |
LLDP/4/LLDP_NEIGHBOR_AGE_OUT: Nearest bridge agent neighbor aged out on port GigabitEthernet1/0/1 (IfIndex599), neighbor's chassis ID is 3822-d666-ba00, port ID is GigabitEthernet1/0/1. |
|
Impact |
The LLDP neighbor is disconnected. |
|
Cause |
This message is generated when the port failed to receive LLDPDUs from the neighbor within a certain period of time. |
|
Recommended action |
1. Execute the display interface command to identify whether a link failure occurs between the local device and the neighboring device, which causes LLDP packet loss or congestion. ¡ If a link failure occurs, troubleshoot the link failure. If the link failure cannot be cleared, go to step 2. ¡ If no link failure occurs, go to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LLDP_PVID_INCONSISTENT
|
Message text |
PVID mismatch discovered on [STRING] (PVID [UINT32]), with [STRING] [STRING] (PVID [STRING]). |
|
Variable fields |
|
|
Severity level |
5 (Notification) |
|
Example |
LLDP/5/LLDP_PVID_INCONSISTENT: PVID mismatch discovered on GigabitEthernet1/0/1 (PVID 1), with H3C GigabitEthernet1/0/1 (PVID 500). |
|
Impact |
A PVID mismatch occurs between two ends of the link, which causes the failure of packet forwarding for some protocols. |
|
Cause |
|
|
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 |
3 (Error) |
|
Example |
LLDP/3/LLDP_REACH_NEIGHBOR_LIMIT: The number of nearest bridge agent neighbors maintained by the port GigabitEthernet1/0/1 (IfIndex 599) has reached 5, and no more neighbors can be added. |
|
Impact |
The interface cannot create a new LLDP neighbor entry. |
|
Cause |
This message is generated when the port with its maximum number of neighbors reached received an LLDP packet from a new neighbor. |
|
Recommended action |
To create a new neighbor entry, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LOAD messages
This section contains load management messages.
BOARD_LOADING
|
Message text |
Mode 1: Board in chassis [INT32] slot [INT32] is loading software images. Mode 2: Board in slot [INT32] is loading software images. |
|
Variable fields |
Mode 1: $1: Chassis ID. $2: Slot ID. Mode 2: $1: Slot ID. |
|
Severity level |
4 (Warning) |
|
Example |
Mode 1: LOAD/4/BOARD_LOADING: Board in chassis 1 slot 5 is loading software images. Mode 2: LOAD/4/BOARD_LOADING: Board in slot 5 is loading software images. |
|
Impact |
No negative impact on the system. |
|
Cause |
The card is loading software images during the boot process. |
|
Recommended action |
No action is required. |
LOAD_FAILED
|
Message text |
Mode 1: Board in chassis [INT32] slot [INT32] failed to load software images. Mode 2: Board in slot [INT32] failed to load software images. |
|
Variable fields |
Mode 1: $1: Chassis ID. $2: Slot ID. Mode 2: $1: Slot ID. |
|
Severity level |
3 (Error) |
|
Example |
Mode 1: LOAD/3/LOAD_FAILED: Board in chassis 1 slot 5 failed to load software images. Mode 2: LOAD/3/LOAD_FAILED: Board in slot 5 failed to load software images. |
|
Impact |
The card will fail to start. |
|
Cause |
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 issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
LOAD_FINISHED
|
Message text |
Mode 1: Board in chassis [INT32] slot [INT32] has finished loading software images. Mode 2: oard in slot [INT32] has finished loading software images. |
|
Variable fields |
Mode 1: $1: Chassis ID. $2: Slot ID. Mode 2: $1: Slot ID. |
|
Severity level |
5 (Notification) |
|
Example |
Mode 1: LOAD/5/LOAD_FINISHED: Board in chassis 1 slot 5 has finished loading software images. Mode 2: LOAD/5/LOAD_FINISHED: Board in slot 5 has finished loading software images. |
|
Impact |
No negative impact on the system. |
|
Cause |
The card has finished loading software images. |
|
Recommended action |
No action is required. |
Local messages
This section contains local messages.
LOCAL_CMDDENY
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Permission denied for visiting user [STRING]. |
|
Variable fields |
$1: User line name. This field displays two asterisks (**) if a login user is not assigned a user line. $2: IP address of the login user. This field displays two asterisks (**) if the system does not obtain the IP address of the login user. $3: Name of the login user. This field displays two asterisks (**) if the login user does not have a username. $4: Name of a local user. |
|
Severity level |
5 (Notification) |
|
Example |
LOCAL/5/LOCAL_CMDDENY: -Line=vty0-IPAddr=111.8.10.111-User=opt; Permission denied for visiting user admin. |
|
Impact |
No negative impact on the system. |
|
Cause |
The system rejected to enter the view of a local user because the login user does not have the access permission. |
|
Recommended action |
No action is required. |
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Permission denied for adding user [STRING]. |
|
Variable fields |
$1: User line name. This field displays two asterisks (**) if a login user is not assigned a user line. $2: IP address of the login user. This field displays two asterisks (**) if the system does not obtain the IP address of the login user. $3: Name of the login user. This field displays two asterisks (**) if the login user does not have a username. $4: Name of a local user. |
|
Severity level |
5 (Notification) |
|
Example |
LOCAL/5/LOCAL_CMDDENY: -Line=vty0-IPAddr=111.8.10.111-User=opt; Permission denied for adding user admin. |
|
Impact |
No negative impact on the system. |
|
Cause |
The system rejected to add a local user because the login user does not have the access permission. |
|
Recommended action |
No action is required. |
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Permission denied for deleting user [STRING]. |
|
Variable fields |
$1: User line name. This field displays two asterisks (**) if a login user is not assigned a user line. $2: IP address of the login user. This field displays two asterisks (**) if the system does not obtain the IP address of the login user. $3: Name of the login user. This field displays two asterisks (**) if the login user does not have a username. $4: Name of a local user. |
|
Severity level |
5 (Notification) |
|
Example |
LOCAL/5/LOCAL_CMDDENY: -Line=vty0-IPAddr=111.8.10.111-User=opt; Permission denied for deleting user admin. |
|
Impact |
No negative impact on the system. |
|
Cause |
The system rejected to delete a local user because the login user does not have the access permission. |
|
Recommended action |
No action is required. |
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Permission denied for configuring user [STRING]'s [STRING]. |
|
Variable fields |
$1: User line name. This field displays two asterisks (**) if a login user is not assigned a user line. $2: IP address of the login user. This field displays two asterisks (**) if the system does not obtain the IP address of the login user. $3: Name of the login user. This field displays two asterisks (**) if the login user does not have a username. $4: Name of a local user. $5: User attribute. The following options are available: ¡ state—User state. ¡ service-type—Type of service. ¡ authorization-attribute—Authorization attribute. ¡ bind-attribute—Binding attribute. ¡ group—User group. ¡ access-limit—Maximum number of concurrent logins for a local user. |
|
Severity level |
5 (Notification) |
|
Example |
LOCAL/5/LOCAL_CMDDENY: -Line=vty0-IPAddr=111.8.10.111-User=opt; Permission denied for configuring user admin's access-limit. |
|
Impact |
No negative impact on the system. |
|
Cause |
The system rejected to configure an attribute for a local user because the login user does not have the access permission. |
|
Recommended action |
No action is required. |
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Permission denied for visiting group [STRING]. |
|
Variable fields |
$1: User line name. This field displays two asterisks (**) if a login user is not assigned a user line. $2: IP address of the login user. This field displays two asterisks (**) if the system does not obtain the IP address of the login user. $3: Name of the login user. This field displays two asterisks (**) if the login user does not have a username. $4: Name of a user group. |
|
Severity level |
5 (Notification) |
|
Example |
LOCAL/5/LOCAL_CMDDENY: -Line=vty0-IPAddr=111.8.10.111-User=opt; Permission denied for visiting group system. |
|
Impact |
No negative impact on the system. |
|
Cause |
The system rejected to enter the view of a user group because the login user does not have the access permission. |
|
Recommended action |
No action is required. |
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Permission denied for adding group [STRING]. |
|
Variable fields |
$1: User line name. This field displays two asterisks (**) if a login user is not assigned a user line. $2: IP address of the login user. This field displays two asterisks (**) if the system does not obtain the IP address of the login user. $3: Name of the login user. This field displays two asterisks (**) if the login user does not have a username. $4: Name of a user group. |
|
Severity level |
5 (Notification) |
|
Example |
LOCAL/5/LOCAL_CMDDENY: -Line=vty0-IPAddr=111.8.10.111-User=opt; Permission denied for adding group system. |
|
Impact |
No negative impact on the system. |
|
Cause |
The system rejected to add a user group because the login user does not have the access permission. |
|
Recommended action |
No action is required. |
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Permission denied for deleting group [STRING]. |
|
Variable fields |
$1: User line name. This field displays two asterisks (**) if a login user is not assigned a user line. $2: IP address of the login user. This field displays two asterisks (**) if the system does not obtain the IP address of the login user. $3: Name of the login user. This field displays two asterisks (**) if the login user does not have a username. $4: Name of a user group. |
|
Severity level |
5 (Notification) |
|
Example |
LOCAL/5/LOCAL_CMDDENY: -Line=vty0-IPAddr=111.8.10.111-User=opt; Permission denied for deleting group system. |
|
Impact |
No negative impact on the system. |
|
Cause |
The system rejected to delete a user group because the login user does not have the access permission. |
|
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: User line name or IP address. $3: Failure cause. For more information, see the user online/offline reason description in AAA commands in Security Command Reference. |
|
Severity level |
5 (Notification) |
|
Example |
LOGIN/5/LOGIN_AUTHENTICATION_FAILED: Authentication failed for Usera from console0 because of Invalid username or password. |
|
Impact |
The user failed to log in to the system. |
|
Cause |
Authentication failed upon user login. |
|
Recommended action |
1. Check the connection between the device and server. 2. Verify that the username and password are correct. 3. Verify that the settings on the server are correct, such as service type. 4. Identify whether the number of login users has reached the upper limit. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LOGIN_FAILED
|
Message text |
[STRING] failed to login from [STRING]. |
|
Variable fields |
$1: Username. $2: Line name or IP address. |
|
Severity level |
5 (Notification) |
|
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. |
|
Impact |
A user fails to log in to the system. |
|
Cause |
A login attempt failed. |
|
Recommended action |
1. Verify the connection between the device and the server. 2. Enter the username and password again. 3. Verify that the server settings are correct, such as the server type. 4. Verify that the number of login users has not reached the upper limit. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
A user entered an invalid username or password. |
|
Recommended action |
Verify that the username and password for login are correct. |
LPDT messages
This section contains LPDT messages.
LPDT_LOOPED
|
Message text |
Loopback exists on [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
LPDT/4/LPDT_LOOPED: Loopback exists on Ethernet6/4/2. |
|
Impact |
The device processes the port based on the loop protection action configured for the port. |
|
Cause |
The port has received a loop detection packet from this device. |
|
Recommended action |
1. Identify whether the existing Layer 2 loops in the current network are necessary for network deployment: ¡ If yes, proceed to step 2. ¡ If not, redeploy the network to eliminate Layer 2 loops. 2. Identify whether the network topology meets the requirements after the loop detection feature processes the port: ¡ If yes, no action is required. ¡ If not, modify the loop detection configuration for the device to ensure that the network topology after the loop detection feature processes the port meets the requirements. If the issue persists, proceed to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LPDT_QINQ_LOOPED
|
Message text |
A loop was detected on [STRING] in SVLAN [UINT16] and CVLAN [UINT16]. |
|
Variable fields |
$1: Interface name. $2: Outer VLAN ID. $3: Inner VLAN ID. |
|
Severity level |
4 (Warning) |
|
Example |
LPDT/4/LPDT_QINQ_LOOPED: A loop was detected on Ethernet6/4/1 in SVLAN 1 and CVLAN 1. |
|
Impact |
The device prevents the port from learning the MAC address and blocks the port. |
|
Cause |
The port received a loop detection packet with a higher priority than its own. |
|
Recommended action |
1. Identify whether the existing Layer 2 loops in the current network are necessary for network deployment: ¡ If yes, proceed to step 2. ¡ If not, redeploy the network to eliminate Layer 2 loops. 2. Identify whether the network topology meets the requirements after the loop detection feature processes the port: ¡ If yes, no action is required. ¡ If not, modify the loop detection configuration for the device to ensure that the network topology after the loop detection feature processes the port meets the requirements. If the issue persists, proceed to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LPDT_QINQ_RECOVERED
|
Message text |
A loop was removed on [STRING] in SVLAN [UINT16] and CVLAN [UINT16]. |
|
Variable fields |
$1: Interface name. $2: Outer VLAN ID. $3: Inner VLAN ID. |
|
Severity level |
5 (Notification) |
|
Example |
LPDT/5/LPDT_QINQ_RECOVERED: A loop was removed on Ethernet6/4/1 in SVLAN 1 and CVLAN 1. |
|
Impact |
No negative impact on the system. |
|
Cause |
The port does not receive loop detection packets within three times the loop detection interval. |
|
Recommended action |
No action is required. |
LPDT_RECOVERED
|
Message text |
Loopback on [STRING] recovered. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 (Notification) |
|
Example |
LPDT/5/LPDT_RECOVERED: Loopback on Ethernet6/4/1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
Reason 1: Within all VLANs, a port does not receive loop detection packets within three times the loop detection interval. Reason 2: The port is shut down to eliminate loops. |
|
Recommended action |
No action is required. |
LPDT_VLAN_LOOPED
|
Message text |
Loopback exists on [STRING] in VLAN [UINT16]. |
|
Variable fields |
$1: Interface name. $2: VLAN ID. |
|
Severity level |
4 (Warning) |
|
Example |
LPDT/4/LPDT_VLAN_LOOPED: Loopback exists on Ethernet6/4/1 in VLAN 1. |
|
Impact |
The device processes the port based on the loop protection action configured for the port. |
|
Cause |
The port received a loop detection packet from this device within the specified VLAN. |
|
Recommended action |
1. Identify whether the existing Layer 2 loops in the current network are necessary for network deployment: ¡ If yes, proceed to step 2. ¡ If not, redeploy the network to eliminate Layer 2 loops. 2. Identify whether the network topology meets the requirements after the loop detection feature processes the port: ¡ If yes, no action is required. ¡ If not, modify the loop detection configuration for the device to ensure that the network topology after the loop detection feature processes the port meets the requirements. If the issue persists, proceed to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LPDT_VLAN_RECOVERED
|
Message text |
Loopback on [STRING] in VLAN [UINT16] recovered. |
|
Variable fields |
$1: Interface name. $2: VLAN ID. |
|
Severity level |
5 (Notification) |
|
Example |
LPDT/5/LPDT_RECOVERED: Loopback on Ethernet6/4/1 in VLAN 1 recovered. |
|
Impact |
No negative impact on the system. |
|
Cause |
Reason 1: Within all VLANs, a port does not receive loop detection packets within three times the loop detection interval. Reason 2: The port is shut down to eliminate loops. |
|
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 name, or user line class name. $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 (Informational) |
|
Example |
LOCALSVR/6/LOCALSVR_PROMPTED_CHANGE_PWD: Please change the password of device management user hhh, because the current password is a weak password. |
|
Impact |
No negative impact on the system. |
|
Cause |
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. |
LOCALSVR_SMOOTH_FAILED
|
Message text |
Failed to smooth configuration to UP [INTEGER]: path([STRING]), configuration([STRING]), reason([STRING]). |
|
Variable fields |
$1: UP ID. $2: XPath path with smooth errors $3: Configuration information with smooth errors $4: Failure reason: ¡ Can't delete the user group: It has one or more local users. ¡ Maximum number of user groups already reached. |
|
Severity level |
4 (Warning) |
|
Example |
LOCALSVR/4/LOCALSVR_SMOOTH_FAILED: Failed to smooth configuration to UP 1027: path(/rpc/edit-config[1]/config[1]/top[1]/UserAccounts[1]/UserGroups[1]/Group[1]/Name[1]), configuration(<top xmlns="http://www.h3c.com/netconf/config:1.0"><UserAccounts><UserGroups> <Group><Name>09</Name></Group></UserGroups></UserAccounts></top>), reason(Can't delete the user group: It has one or more local users.). |
|
Impact |
Evaluate the impact on the system based on the actual condition. |
|
Cause |
· A user group that contains users cannot be deleted. · The number of user groups on the UP has reached the maximum allowed. |
|
Recommended action |
1. Adjust the configuration on the UP according to the failure reason. 2. If the issue persists, collect log messages and configuration data, and then contact Technical Support for help. |
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 (Warning) |
|
Example |
LOCALSVR/4/LS_ADD_USER_TO_GROUP: Admin admin added user user1 to group group1. |
|
Impact |
No negative impact on the system. |
|
Cause |
The administrator added a local user into a specific 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 (Notification) |
|
Example |
LS/5/LS_AUTHEN_FAILURE: User cwf@system from 192.168.0.22 failed authentication. "User not found." |
|
Impact |
Users cannot come online. |
|
Cause |
The local server rejected a user's authentication request. Possible reasons include: · The user cannot be found. · Password verification failed. · The user is not online. · The access type does not match. · Binding attributes failed. · The user has been blacklisted. |
|
Recommended action |
Troubleshoot according to the reason displayed in the message. |
LS_AUTHEN_SUCCESS
|
Message text |
User [STRING] from [STRING] was authenticated successfully. |
|
Variable fields |
$1: Username. $2: IP address. |
|
Severity level |
6 (Informational) |
|
Example |
LS/6/LS_AUTHEN_SUCCESS: User cwf@system from 192.168.0.22 was authenticated successfully. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
LS/4/LS_DEL_USER_FROM_GROUP: Admin admin delete user user1 from group group1. |
|
Impact |
No negative impact on the system. |
|
Cause |
The administrator deleted a local user from a specific user group. |
|
Recommended action |
No action is required. |
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 (Warning) |
|
Example |
LS/4/LS_PWD_ADDBLACKLIST: User aaa at 192.168.0.22 was added to the blacklist due to multiple login failures, but could make other attempts. |
|
Impact |
The impact on the system depends on the actual situation. |
|
Cause |
After a user login authentication fails, the system adds the user to the password management blacklist and restricts subsequent login attempts according to the measures configured in the password-control login-attempt command. When a user login fails more times than the specified limit, the system will prohibit that user from logging in. After a period, the system allows the user to attempt to log in again. |
|
Recommended action |
1. If this message appears occasionally, check the user's password. Incorrect password input might cause login prohibition. As a best practice, try to log in again after waiting for some time. If you encounter the same issue when logging into the device again with the correct username and password, collect log messages and configuration data, and then contact Technical Support for help. 2. If this message appears frequently, the system might be under a login attack. Contact Technical Support for help. |
LS_PWD_CHGPWD_FOR_AGEDOUT
|
Message text |
User [STRING] changed the password because it was expired. |
|
Variable fields |
$1: Username. |
|
Severity level |
4 (Warning) |
|
Example |
LS/4/LS_PWD_CHGPWD_FOR_AGEDOUT: User aaa changed the password because it was expired. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
LS/4/LS_PWD_CHGPWD_FOR_AGEOUT: User aaa changed the password because it was about to expire. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
LS/4/LS_PWD_CHGPWD_FOR_COMPOSITION: User aaa changed the password because it had an invalid composition. |
|
Impact |
No negative impact on the system. |
|
Cause |
A user reentered the password due to a mistake in the password 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 (Warning) |
|
Example |
LS/4/LS_PWD_CHGPWD_FOR_FIRSTLOGIN: User aaa changed the password at the first login. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Warning) |
|
Example |
LS/4/LS_PWD_CHGPWD_FOR_LENGTH: User aaa changed the password because it was too short. |
|
Impact |
No negative impact on the system. |
|
Cause |
A user changed the password because the input password 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 (Warning) |
|
Example |
LS/4/LS_PWD_FAILED2WRITEPASS2FILE: Failed to write the password records to file. |
|
Impact |
The local user's password cannot be modified. |
|
Cause |
A user failed to change its own password during login, or an administrator failed to change a local user's password. Possible reasons include: · The local file system of the device is running out of memory space. · An anomaly occurs on the local lauth.dat file. |
|
Recommended action |
1. Execute the dir command in user view to check the remaining capacity information of local storage media (such as flash). If no enough remaining space is available, delete unnecessary files. 2. Execute the dir command in user view to check for the lauth.dat file on local storage media (such as flash). If the file does not exist, has a size of 0, or is very small (likely an anomaly if less than 20B), please contact Technical Support for help. |
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: · password is too short. · password has not minimum different chars. · invalid password composition. · password has repeated chars. · password contains username. · password used already. · Failed to verify password. · password is in update-wait time. · password be part of username. |
|
Severity level |
4 (Warning) |
|
Example |
LS/4/LS_PWD_MODIFY_FAIL: Admin admin from 1.1.1.1 could not modify the password for user user1, because password is too short. |
|
Impact |
No negative impact on the system. |
|
Cause |
Possible causes: · The password is too short. · The number of unique characters is fewer than 4. · Invalid password composition. · The password contains three or more consecutive identical characters. · The password contains the username. · The password is identical to the current or a previous password. · The old password is incorrect. · The password update interval has not been reached. · The password is part of the username. |
|
Recommended action |
Troubleshoot according to the reason displayed in the message. |
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 (Informational) |
|
Example |
LS/6/LS_PWD_MODIFY_SUCCESS: Admin admin from 1.1.1.1 modify the password for user abc successfully. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Notification) |
|
Example |
LS/5/LS_REAUTHEN_FAILURE: User abcd from 1.1.1.1 failed reauthentication. |
|
Impact |
The user failed to change their password because the old password entered was incorrect. |
|
Cause |
When a user changes their own password during login or after successful login from the CLI, the system requires the user to enter the old password first. If verification of the old password fails, the system will output this log message. |
|
Recommended action |
Check the local user's old password. If it is correct, contact Technical Support for help. |
LS_UPDATE_PASSWORD_FAIL
|
Message text |
Failed to update the password for user [STRING]. |
|
Variable fields |
$1: Username. |
|
Severity level |
4 (Warning) |
|
Example |
LS/4/LS_UPDATE_PASSWORD_FAIL: Failed to update the password for user abc. |
|
Impact |
The local user's password cannot be modified. |
|
Cause |
Adding, changing, or deleting a local user password from CLI failed. Possible reasons include: · The password does not meet security requirements, such as being too short or identical to the current or past passwords. · The local file system of the device is running out of memory space. · An anomaly occurs on the local lauth.dat file. |
|
Recommended action |
1. Reset the password according to the system's prompt to meet security requirements. 2. Execute the dir command in user view to check the remaining capacity information of local storage media (such as flash). If no enough remaining space is available, delete unnecessary files. 3. Execute the dir command in user view to check for the lauth.dat file on local storage media (such as flash). If the file does not exist, has a size of 0, or is very small (likely an anomaly if less than 20B), please contact Technical Support for help. |
LS_USER_CANCEL
|
Message text |
User [STRING] from [STRING] cancelled inputting the password. |
|
Variable fields |
$1: Username. $2: IP address. |
|
Severity level |
5 (Notification) |
|
Example |
LS/5/LS_USER_CANCEL: User 1 from 1.1.1.1 cancelled inputting the password. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Notification) |
|
Example |
LS/5/LS_USER_PASSWORD_EXPIRE: User 1's login idle timer timed out. |
|
Impact |
No negative impact on the system. |
|
Cause |
After logging in, the local user was idle for a period that exceeded the idle timeout. |
|
Recommended action |
No action is required. |
LS_USER_ROLE_CHANGE
|
Message text |
Admin [STRING] [STRING] user role [STRING] for [STRING]. |
|
Variable fields |
$1: Administrator name. $2: Administrator operation: added or deleted. $3: User role. $4: Username. |
|
Severity level |
4 (Warning) |
|
Example |
LS/4/LS_USER_ROLE_CHANGE: Admin admin added user role network-admin for abcd. |
|
Impact |
No negative impact on the system. |
|
Cause |
The administrator added a user role for a local user. |
|
Recommended action |
No action is required. |
LSM
This section contains LSM messages.
LSM_SR_LABEL_CONFLICT
|
Message text |
Protocol [STRING] assigned label([STRING]) to prefix([STRING]), which already has label([STRING]) assigned by protocol [STRING]. |
|
Variable fields |
$1: Routing protocol 1. $2: Label value 1. $3: Prefix address and mask. $4: Label value 2. $3: Routing protocol 2. |
|
Severity level |
4 (Warning) |
|
Example |
LSM/4/LSM_SR_LABEL_CONFLICT: Protocol ISIS assigned label(16000) to prefix(5.5.5.5/32), which already has label(17000) assigned by protocol OSPF. |
|
Impact |
No negative impact on the system. |
|
Cause |
On the same SR node, different routing protocols assign different labels to the same prefix address. |
|
Recommended action |
Confirm whether it is necessary to assign different labels for the same prefix under different protocols. If it is not necessary, as a best practice, adjust the configuration. |
LSM_SR_PREFIX_CONFLICT
|
Message text |
The label([STRING]) for prefix([STRING]) has been used by prefix([STRING]). |
|
Variable fields |
$1: Label value. $2: Prefix address 1 and mask. $3: Prefix address 2 and mask. |
|
Severity level |
4 (Warning) |
|
Example |
LSM/4/LSM_SR_PREFIX_CONFLICT: The label(16700) for prefix(8.8.8.8/32) has been used by prefix(5.5.5.5/32). |
|
Impact |
The device will create only one ILM entry for prefixes with label conflicts, which might lead to incorrect forwarding of some traffic. |
|
Cause |
One label is assigned to two different prefix addresses. |
|
Recommended action |
Adjust the SR label configuration to avoid conflicts in label allocation. |
LSPV messages
This section contains LSP verification messages.
LSPV_PING_STATIS_INFO
|
Message text |
Ping statistics for [STRING]: [UINT32] packets transmitted, [UINT32] packets received, [DOUBLE]% packets loss, round-trip min/avg/max = [UINT32]/[UINT32]/[UINT32] ms. |
|
Variable fields |
$1: FEC. $2: Number of echo requests sent. $3: Number of echo replies received. $4: Percentage of the non-replied packets to the total requests. $5: Minimum round-trip delay. $6: Average round-trip delay. $7: Maximum round-trip delay. |
|
Severity level |
6 (Informational) |
|
Example |
LSPV/6/LSPV_PING_STATIS_INFO: Ping statistics for FEC 192.168.1.1/32: 5 packets transmitted, 5 packets received, 0.0% packets loss, round-trip min/avg/max = 1/2/5 ms. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when the ping mpls command is executed. It displays the ping statistics for an LSP tunnel or a PW. |
|
Recommended action |
If no reply is received, it indicates a fault in the LSP tunnel or PW. Check the network status and related configurations of the LSP or PW to resolve connectivity issues. If the fault is with the LSP, proceed with the following processing: 4. Execute the display ip routing-table command to identify whether there is a subnet route destined for the Loopback interface address of the LSP destination node. If the route does not exist, enable the IGP protocol on the Loopback interface and the public network interfaces to ensure the advertisement of the corresponding subnet route. 5. Check if the route has been recursed to the LSP tunnel or if there is an MPLS label present. Execute the display fib command to view the FIB entry for the specified prefix. Check whether the FIB entry has an LSP index number (Token field) or a label value (Label field). If it exists, proceed with the next step. If it does not exist, it means the route is not an FTN entry. Execute the display mpls lsp command to check for an LSP to the destination address of the route. If no such LSP exists, establish one of the specified type: ¡ To establish an LDP LSP, enable MPLS and MPLS LDP on interfaces. ¡ To establish an SRLSP, execute the segment-routing mpls command in IS-IS IPv4 unicast address family view, OSPF view, or BGP IPv4 unicast address family view to enable MPLS-based SR. ¡ To establish an SR-MPLS TE policy, create it correctly in SR TE view. 6. Execute the display cpu-usage command to view CPU usage statistics. ¡ If the CPU usage is too high, disable some unnecessary features to reduce the device's CPU usage. ¡ If the CPU usage is normal, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. If it's a PW fault, execute the ping mpls pw command, and then identify the cause of the issue depending on the received error message. · If you receive the Unknown PW error message, the issue occurs because the PW does not exist. You must modify the configuration to make sure the PW can be created correctly. · If the error message is No suitable control channel for the PW, check for VCCV control channel type misconfiguration. Then, execute the vccv cc command to specify the correct VCCV control channel type in the PW class. · If the error message is Please configure pseudowire control-word for control channel, execute the control-word enable command to enable the control word feature in the PW class. · If the error message is Request time out, identify whether the local PW is up, and then use the tracert mpls pw command to locate the faulty node and clear the fault. If the issue persists, collect the configuration data, log messages, and alarm information, and then contact Technical Support for help. |
MAC messages
This section contains MAC messages.
MAC_CAPACITY_LIMIT
|
Message text |
The number of MAC address entries exceeded the maximum number [UNIT32]. |
|
Variable fields |
$1: Maximum number of MAC address entries on the LPU. |
|
Severity level |
5 (Notification) |
|
Example |
MAC/5/MAC_CAPACITY_LIMIT: -MDC=1-Slot=3; The number of MAC address entries exceeded the maximum number 1048576. |
|
Impact |
· If the mac-address max-mac-count enable-forwarding command has been executed, the device forwards unknown frames received on the interface after the MAC learning limit on the interface is reached. · If the undo mac-address max-mac-count enable-forwarding command has been executed, the device does not forward unknown frames received on the interface after the MAC learning limit on the interface is reached. |
|
The number of MAC address entries on the LPU exceeded the supported maximum number. |
|
|
Recommended action |
· Use the mac-address max-mac-count command to set the MAC learning limit on a per-interface basis. · Use the mac-address max-mac-count enable-forwarding command to enable the device to forward unknown frames received on an interface after the MAC learning limit on the interface is reached. · If the issue persists, collect the configuration file, log messages, and alarm information, and then contact Technical Support. |
MAC messages
This section contains MAC messages.
MAC_NOTIFICATION
|
Message text |
Pattern 1: MAC address [STRING] in VLAN [UNIT32] has moved from port [STRING] to port [STRING] for [UNIT32] times. Pattern 2: MAC address [STRING] in VSI [STRING] has moved from [STRING] service-instance [UNIT32] to [STRING] service-instance [UNIT32] for [UNIT32] times. |
|
Variable fields |
Pattern 1: $1: MAC address table $2: VLAN ID. $3: Interface name. $4: Interface name. $5: Number of MAC address moves. Pattern 2: $1: MAC address. $2: VSI instance name. $3: Interface name. $4: Ethernet service instance ID. $5: Interface name. $4: Ethernet service instance ID. $5: Number of MAC address moves. |
|
Severity level |
4 (Warning) |
|
Example |
Pattern 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. Pattern 2: MAC/4/MAC_NOTIFICATION: MAC address 0010-9400-0002 in VSI vpna has moved from GigabitEthernet1/0/1 service-instance 40 to GigabitEthernet1/0/2 service-instance 30 for 152499 times. |
|
Impact |
If MAC address moves occur frequently, Layer 2 loops might occur in the network to cause a broadcast storm. |
|
Cause |
Reason 1: Layer 2 loops exist in the network. Reason 2: Malicious attacks exist in the network. |
|
Recommended action |
Reason 1: Deploy the correct physical network topology to eliminate loops, or deploy loop avoidance protocols (such as spanning tree, loop protection, RRPP, and ERPS). Reason 2: 7. Use the mac-address mac-learning priority command to configure the MAC address learning priority for an interface, or use the mac-address notification mac-move suppression command to configure MAC address move suppression to avoid the impact of malicious attacks. If MAC address moves still occur frequently, proceed to step 2. 8. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Warning) |
|
Example |
MAC/4/MAC_TABLE_FULL_GLOBAL: The number of MAC address entries reached the maximum number 1024. |
|
Impact |
The device cannot learn new MAC address entries. |
|
Cause |
The number of entries in the global MAC address table reached the maximum number supported by the table. |
|
Recommended action |
1. Execute the display mac-address command to display all current MAC address entries. 2. Execute the undo mac-address command in system view or interface view to delete unnecessary MAC address entries. |
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 (Warning) |
|
Example |
MAC/4/MAC_TABLE_FULL_PORT: The number of MAC address entries reached the maximum number 1024 for interface GigabitEthernet1/0/1. |
|
Impact |
The interface cannot learn new MAC address entries. |
|
Cause |
The number of entries in the MAC address table for an interface reached the maximum number supported by the table. |
|
Recommended action |
Use the display mac-address interface interface-type interface-number command to identify whether the MAC address entries on the interface are the required ones: · If yes, execute the mac-address max-mac-count command on this interface to increase the MAC address learning limit. · If not, execute the undo mac-address command on the interface to delete unnecessary MAC address entries. |
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 (Warning) |
|
Example |
MAC/4/MAC_TABLE_FULL_VLAN: The number of MAC address entries reached the maximum number 1024 in VLAN 2. |
|
Impact |
The VLAN cannot learn new MAC address entries. |
|
Cause |
The number of entries in the MAC address table for a VLAN reached the maximum number supported by the table. |
|
Recommended action |
Use the display mac-address interface vlan vlan-id command to identify whether the MAC address entries for the VLAN are the required ones: · If yes, execute the mac-address max-mac-count command in the view of this VLAN to increase the MAC address learning limit. · If not, execute the undo mac-address command in the view of this VLAN to delete unnecessary MAC address entries. |
MBFD messages
This section contains MPLS BFD messages.
MBFD_TRACEROUTE_FAILURE
|
Message text |
[STRING] is failed. ([STRING].) |
|
Variable fields |
$1: LSP information. · For an IPv4 LDP LSP, the value is LSP (LDP IPv4: ipv4-address/mask-length, nexthop: nexthop-address), where ipv4-address is the FEC destination IPv4 address prefix, mask-length is the mask length of the FEC destination IPv4 address prefix, and nexthop-address is the next hop address of the next hop. · For an MPLS TE tunnel, the value is TE tunnel (RSVP IPv4: tunnel-name), where tunnel-name is the name of the MPLS TE tunnel interface. $2: Reason for the LSP failure. Possible values include: · Malformed echo request received. · One or more of the TLVs was not understood. · Replying router has no mapping for the FEC. · Downstream Mapping Mismatch. · Upstream Interface Index Unknown. · Label switched but no MPLS forwarding. · Mapping for this FEC is not the given label. · No label entry. · Protocol not associated with interface. · Premature termination of ping due to label stack shrinking to a single label. |
|
Severity level |
4 (Warning) |
|
Example |
MBFD/4/MBFD_TRACEROUTE_FAILURE: LSP (LDP IPv4: 22.22.2.2/32, nexthop: 20.20.20.2) is failed. (Replying router has no mapping for the FEC.) MBFD/4/MBFD_TRACEROUTE_FAILURE: TE tunnel (RSVP IPv4: Tunnel1) is failed. (No label entry.) |
|
Impact |
When the failure reason is Malformed echo request received or One or more of the TLVs was not understood, it indicates an issue of the periodic tracert feature, which does not have negative impact on the system or services. When the failure reason is other values, traffic forwarded by this LSP or MPLS TE tunnel will be interrupted. |
|
Cause |
The periodic MPLS tracert feature encountered a problem or the detected LSP or MPLS TE tunnel failed. |
|
Recommended action |
When the failure reason is Malformed echo request received or One or more of the TLVs was not understood, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. When the failure reason is other values, verify that the tunnel related configuration and forwarding entries on the nodes that the LSP or MPLS TE tunnel traverses are correct. If the configuration and entries are correct but the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MBUF messages
This section contains MBUF messages.
MBUF_DATA_BLOCK_CREATE_FAIL
|
Message text |
Failed to create an MBUF data block because of insufficient memory. Failure count: [UINT32]. |
|
Variable fields |
$1: Failure count. |
|
Severity level |
2 (Critical) |
|
Example |
MBUF/2/MBUF_DATA_BLOCK_CREATE_FAIL: Failed to create an MBUF data block because of insufficient memory. Failure count: 128. |
|
Impact |
Running of the service modules will be affected. |
|
Cause |
The message is output when the system fails to create an MBUF data block 1 minute or more after the most recent creation failure. |
|
Recommended action |
1. Execute the display system internal kernel memory pool | include mbuf command in probe view to view the number of the allocated MBUF data blocks. 2. Execute the display memory command in system view to display the total size of the system memory. 3. Determine whether an excessive number of MBFU data blocks are allocated by comparing the size of the allocated MBUF data blocks with that of the system memory. ¡ If it is not an excessive number, use the memory management commands to check for the memory-intensive modules. ¡ If it is an excessive number, go to step 506. 4. Execute the display system internal mbuf socket statistics command in probe view to view the number of the MBUF data blocks buffered in the socket. Determine whether a process has too many MBUF data blocks buffered in the socket buffer. ¡ If it is too many, locate the reason why the MBUF data blocks cannot be released from the socket buffer. ¡ If it is not too many, use other means to locate the reasons for excessive allocation of MBUF data blocks. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
·
MFIB messages
This section contains MFIB messages.
MFIB_CFG_NOT_SUPPORT
|
Message text |
Failed to apply [STRING] configuration because the operation is not supported. |
|
Variable fields |
$1: Attack defense command: igmp attack-defense or mld attack-defense. |
|
Severity level |
4 (Warning) |
|
Example |
MFIB/4/MFIB_CFG_NOT_SUPPORT: Failed to apply igmp attack-defense configuration because the operation is not supported. |
|
Impact |
IGMP or MLD attack defense cannot work. |
|
Cause |
The device does not support the feature. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MFIB_MTI_NO_ENOUGH_RESOURCE
|
Message text |
Failed to create [STRING] because of insufficient resources. |
|
Variable fields |
$1: Multicast tunnel name. |
|
Severity level |
4 (Warning) |
|
Example |
MFIB/4/MFIB_MTI_NO_ENOUGH_RESOURCE: Failed to create MTunnel1 because of insufficient resources. |
|
Impact |
Multicast packets cannot be forwarded. |
|
Cause |
Driver resources are insufficient. |
|
Recommended action |
Use the undo group group-address source source-address command in VXLAN view or the undo default-group command in MVPN IPv4/IPv6 address family view to delete unused multicast tunnels. |
MFIB_OIF_NOT_SUPPORT
|
Message text |
Failed to add oif to entry ([STRING], [STRING]) because some oifs are not supported. |
|
Variable fields |
$1: Multicast source address. $2: Multicast group address. |
|
Severity level |
4 (Warning) |
|
Example |
MFIB/4/MFIB_OIF_NOT_SUPPORT: Failed to add oif to entry (1.1.1.1, 225.0.0.1) because some oifs are not supported. |
|
Impact |
Multicast packets cannot be forwarded. |
|
Cause |
The device does not support add some interfaces to multicast forwarding entry. |
|
Recommended action |
1. If any interface on the card is configured with the following commands, delete the configuration and reconfigure it. ¡ igmp static-group group-address [ source source-address ] { dot1q vid vlan-list | dot1q vid vlan-id second-dot1q vlan-list } ¡ igmp user-vlan-aggregation dot1q vid vlan-id [ second-dot1q vlan-id ] ¡ mld static-group ipv6-group-address [ source ipv6-source-address ] { dot1q vid vlan-list | dot1q vid vlan-id second-dot1q vlan-list } ¡ mld user-vlan-aggregation dot1q vid vlan-id [ second-dot1q vlan-id ] 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MGROUP messages
This section contains mirroring group messages.
MGROUP_APPLY_SAMPLER_FAIL
|
Message text |
Failed to apply the sampler for mirroring group [UINT16], because the sampler resources are insufficient. |
|
Variable fields |
$1: Mirroring group ID. |
|
Severity level |
3 (Error) |
|
Example |
MGROUP/3/MGROUP_APPLY_SAMPLER_FAIL: Failed to apply the sampler for mirroring group 1, because the sampler resources are insufficient. |
|
Impact |
Mirrored packets cannot be sampled. |
|
Cause |
A sampler was not applied to the mirroring group because the sampler resources were insufficient. |
|
Recommended action |
1. Use the display mirroring-group all command to view all samplers referenced by mirroring groups on the device. If some samplers are not needed, you can delete them to release sampler resources. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
MGROUP_RESTORE_CPUCFG_FAIL
|
Message text |
Failed to restore configuration for mirroring CPU of [STRING] in mirroring group [UINT16], because [STRING] |
|
Variable fields |
$1: Slot number. $2: Mirroring group ID. $3: Failure reason. |
|
Severity level |
3 (Error) |
|
Example |
MGROUP/3/MGROUP_RESTORE_CPUCFG_FAIL: Failed to restore configuration for mirroring CPU of chassis 1 slot 2 in mirroring group 1, because the type of the monitor port in the mirroring group is not supported. |
|
Impact |
Mirroring in source CPU mode cannot be used normally. |
|
Cause |
When the CPU of the card in the slot is the source CPU in the mirroring group, configuration changes after the card is removed. When the card is reinstalled into the slot, restoring the source CPU configuration might fail. |
|
Recommended action |
Check for the failure reason. · If the reason is that the system does not support the changed configuration, delete the unsupported configuration, and reconfigure the source CPU in the mirroring group. · If not, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
MGROUP_RESTORE_IFCFG_FAIL
|
Message text |
Failed to restore configuration for interface [STRING] in mirroring group [UINT16], because [STRING]. |
|
Variable fields |
$1: Interface name. $2: Mirroring group ID. $3: Failure reason. |
|
Severity level |
3 (Error) |
|
Example |
MGROUP/3/MGROUP_RESTORE_IFCFG_FAIL: Failed to restore configuration for interface Ethernet3/1/2 in mirroring group 1, because the type of the monitor port in the mirroring group is not supported. |
|
Impact |
Mirroring in source port mode cannot be used normally. |
|
Cause |
When the interface of the card in the slot is the monitor port in the mirroring group, configuration changes after the card is removed. When the card is reinstalled into the slot, restoring the monitor port configuration might fail. |
|
Recommended action |
Check for the failure reason. · If the reason is that the system does not support the changed configuration, delete the unsupported configuration, and reconfigure the source port in the mirroring group. · If not, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
MGROUP_SYNC_CFG_FAIL
|
Message text |
Failed to restore configuration for mirroring group [UINT16] in [STRING], because [STRING]. |
|
Variable fields |
$1: Mirroring group ID. $2: Slot number. $3: Failure reason. |
|
Severity level |
3 (Error) |
|
Example |
MGROUP/3/MGROUP_SYNC_CFG_FAIL: Failed to restore configuration for mirroring group 1 in chassis 1 slot 2, because monitor resources are insufficient. |
|
Impact |
The mirroring feature cannot be used normally. |
|
Cause |
When the complete mirroring group configuration was synchronized on the card in the slot, restoring configuration failed because resources on the card were insufficient. |
|
Recommended action |
1. Delete the mirroring group whose configuration failed to be restored. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
MPLS messages
This section contains MPLS messages.
LABEL_NORES
|
Message text |
No enough resource |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
MPLS/3/LABEL_NORES: -MDC=1-Slot=4; No enough resource |
|
Impact |
The VPN service or tunnel cannot be set up. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the tunnel label resources are insufficient, the system cannot create an MPLS tunnel. |
|
Recommended action |
1. Execute the display resource-monitor command to view the mpls_label resource occupation information. 2. Delete unused MPLS tunnels. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
TNL_TBORPROFILE_NORES
|
Message text |
Hardware resources not enough. The rate limits set by QoS rate limit or MPLS TE traffic policing for [STRING] do not take effect. |
|
Variable fields |
$1: Name of MPLS TE tunnel. |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/TNL_TBORPROFILE_NORES: -MDC=1-Slot=5; Hardware resources not enough. The rate limits set by QoS rate limit or MPLS TE traffic policing for Tunnel256 do not take effect. |
|
Impact |
The rate limit function cannot take effect on the TE tunnels on the card. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the Tbindex or Profile resources are insufficient on a card, rate limit settings cannot take effect on the TE tunnels on the card. |
|
Recommended action |
1. Execute the display resource-monitor command to view the mpls_tecar_profile_x (x represents the chip number) resource occupation information. 2. Delete the rate limit commands for unused MPLS tunnels. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
P2MPTE_TUNNEL_NORES
|
Message text |
Not enough hardware resources for P2MP-TE tunnel. |
|
Variable fields |
N/A |
|
Severity level |
2 (Critical) |
|
Example |
MPLS/2/P2MPTE_TUNNEL_NORES: -MDC=1-Slot=5; Not enough hardware resources for P2MP-TE tunnel. |
|
Impact |
The P2MP TE tunnel cannot be established. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the tunnel resources are insufficient, the system cannot create an MPLS tunnel. |
|
Recommended action |
1. Execute the display resource-monitor command to view the ipmc resource occupation information. 2. Delete the unused P2MP TE tunnels. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
OUTLIF_NORES
|
Message text |
Not enough outlif resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/OUTLIF_NORES: -MDC=1-Slot=5; Not enough outlif resource. |
|
Impact |
The public tunnel cannot forward traffic. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the outlif resources are insufficient on a card, MPLS tunnels on the card cannot forward traffic. |
|
Recommended action |
1. Execute the display resource-monitor command to view the mpls_outlif resource occupation information. 2. Delete the unused MPLS tunnels or L2VPN services. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
REMOTEMAC_NORES
|
Message text |
Not enough remoteMac resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/REMOTEMAC_NORES: -MDC=1-Slot=5; Not enough remoteMac resource. |
|
Impact |
The related FRR function is unavailable. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the remoteMac resources are insufficient, FRR does not take effect. |
|
Recommended action |
1. Execute the display hardware internal indexq all slot command to view the RemoteMac resource occupation information. 2. Delete the unused public tunnels or L2VPN services. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CFDORACSTAT_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
VPLS/3/CFDORACSTAT_NORES: -MDC=1-Slot=2; No enough resource. |
|
Impact |
The VPLS-based CFD function or AC statistics function cannot take effect. |
|
Cause |
Hardware resources were insufficient for enabling CFD or packet statistics on the AC. In this case, packet forwarding is normal but packet statistics is disabled. |
|
Recommended action |
1. Delete the statistics commands for unused ACs. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CFDORACSTAT_CONFLICTS_INTF
|
Message text |
Operation conflicts with the configuration on this interface. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
VPLS/3/CFDORACSTAT_CONFLICTS_INTF: -MDC=1-Slot=5; Operation conflicts with the configuration on this interface. |
|
Impact |
The configuration cannot be deployed to the interface. |
|
Cause |
This message is sent if you enable CFD or packet statistics for an AC (interface) where subinterface statistics is configured. |
|
Recommended action |
1. Delete the statistics command for the subinterface that acts as the AC. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CFDORAC_STAT_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
VLL/3/CFDORAC_STAT_NORES: -MDC=1-Slot=2; No enough resource. |
|
Impact |
The VPWS-based CFD function or AC statistics function cannot take effect. |
|
Cause |
Hardware resources were insufficient for enabling packet statistics on the AC. In this case, packet forwarding is normal but packet statistics is disabled. |
|
Recommended action |
1. Delete the statistics commands for unused ACs. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CFDORAC_CONFLICTS_INTFSTAT
|
Message text |
Operation conflicts with the configuration on this interface. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
VLL/3/CFDORAC_CONFLICTS_INTFSTAT: -MDC=1-Slot=5; Operation conflicts with the configuration on this interface. |
|
Impact |
The configuration cannot be deployed to the interface. |
|
Cause |
This message is sent if you enable CFD or packet statistics for an AC (interface) where subinterface statistics is configured. |
|
Recommended action |
1. Delete the statistics command for the subinterface that acts as the AC. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NDSUPR_DUALFORWARD_NOTSPT
|
Message text |
In standard mode, the card does not support vpws nd suppression or dual-forward. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VLL/4/NDSUPR_DUALFORWARD_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpws nd suppression or dual-forward. |
|
Impact |
ND suppression or dual-forward for VPWS cannot take effect. |
|
Cause |
In standard mode, the card does not support ND suppression or dual-forward for VPWS. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARPSUPR_DUALFORWARD_NOTSPT
|
Message text |
In standard mode, the card does not support vpws arp suppression or dual-forward. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VLL/4/ARPSUPR_DUALFORWARD_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpws arp suppression or dual-forward. |
|
Impact |
ARP suppression or dual-forward for VPWS cannot take effect. |
|
Cause |
In standard mode, the card does not support ARP suppression or dual-forward for VPWS. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DOUBLEBYPASS_NOTSPT
|
Message text |
In standard mode, the card does not support vpws double bypass. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VLL/4/DOUBLEBYPASS_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpws double bypass. |
|
Impact |
Dual bypass PWs for VPWS cannot take effect. |
|
Cause |
In standard mode, the card does not support dual bypass PWs for VPWS. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
EVPN_MULTIHOME_NOTSPT
|
Message text |
In standard mode, the card does not support evpn vpws multihoming. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VLL/4/EVPN_MULTIHOME_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support evpn vpws multihoming. |
|
Impact |
EVPN VPWS dual homing cannot take effect |
|
Cause |
In standard mode, the card does not support EVPN VPWS dual homing. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
AC_REACH_MAXNUM
|
Message text |
The number of ACs or PWs or VXLAN TUNNELs in the VSI has reached the limit. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VPLS/4/AC_REACH_MAXNUM: -MDC=1; The number of ACs or PWs or VXLAN TUNNELs in the VSI has reached the limit. |
|
Impact |
No new AC, PW, or VXLAN tunnel can be created. |
|
Cause |
This message is sent when the number of ACs, PWs, or VXLAN tunnels configured in a VSI exceeds the maximum allowed. |
|
Recommended action |
1. Execute the display l2vpn vsi name verbose command to view the number and state of the ACs, PWs, or VXLAN tunnels in the VSI. 2. Remove the associations between unused ACs and the VSI. 3. Delete unused PWs or VXLAN tunnels. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PW_REACH_MAXNUM
|
Message text |
Pattern 1: The number of ACs or PWs in the VSI has reached the limit. Pattern 2: The number of PWs or VXLAN TUNNELs in the VSI has reached the limit. Pattern 3: The number of ACs or PWs or VXLAN TUNNELs in the VSI has reached the limit. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VPLS/4/PW_REACH_MAXNUM: -MDC=1; The number of ACs or PWs in the VSI has reached the limit. |
|
Impact |
No new AC, PW, or VXLAN tunnel can be created. |
|
Cause |
This message is sent when the number of ACs, PWs, or VXLAN tunnels configured in a VSI exceeds the maximum allowed. |
|
Recommended action |
1. Execute the display l2vpn vsi name verbose command to view the number and state of the ACs, PWs, or VXLAN tunnels in the VSI. 2. Remove the associations between unused ACs and the VSI. 3. Delete unused PWs or VXLAN tunnels. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
EVPNORSRV6_NOTSPT
|
Message text |
In standard mode, the card does not support evpn vpls or srv6. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VPLS/4/EVPNORSRV6_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support evpn vpls or srv6. |
|
Impact |
EVPN VPLS and EVPN VPLS over SRv6 functions cannot take effect. |
|
Cause |
In standard mode, the card does not support EVPN VPLS or EVPN VPLS over SRv6. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ARPSUP_NOTSPT
|
Message text |
In standard mode, the card does not support vpls arp suppression. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VPLS/4/ARPSUP_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpls arp suppression. |
|
Impact |
VPLS ARP suppression cannot take effect. |
|
Cause |
In standard mode, the card does not support VPLS ARP suppression. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ONEHUB_SUPPORT
|
Message text |
The device supports only one HUB. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
VPLS/3/ONEHUB_SUPPORT: -MDC=1-Slot=5; The device supports only one HUB. |
|
Impact |
Excessive hubs cannot be deployed. |
|
Cause |
In a hub-spoke network, each VPLS instance supports only one hub. |
|
Recommended action |
1. Make sure a VPLS instance has only one hub configured. To bind a new hub, delete the existing hub if it is unused. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LEAFSTAT_NORES
|
Message text |
No enough leaf stat index resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VPLS/4/LEAFSTAT_NORES: -MDC=1-Slot=4; No enough leaf stat index resource. |
|
Impact |
The E-tree function cannot take effect. |
|
Cause |
Hardware resources on the card were insufficient for completing an operation. For example, when the leaf statistics counter resources for PWs are insufficient, the leaf statistics feature does not take effect for PWs on the card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PRIVATESID_NORES
|
Message text |
Not enough Private-SID resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/PRIVATESID_NORES: -MDC=1-Slot=4; Not enough Private-SID resources. |
|
Impact |
SRv6 service features cannot take effect. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the private-SID resources on a card are insufficient, the card cannot use the EVPN VPWS/VPLS over SRv6 service or the MPLS/EVPN L3VPN over SRv6 service. |
|
Recommended action |
1. Execute the display hardware internal indexq all slot command to view the Srv6PrvtSid resource occupation information. 2. Delete the unused VPWS over SRv6, VPLS over SRv6, and L3VPN over SRv6 configuration. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DT2_NORES
|
Message text |
Not enough DT2 resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/DT2_NORES: -MDC=1-Slot=4; Not enough DT2 resources. |
|
Impact |
SRv6 service features cannot take effect. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the DT2 resources on a card are insufficient, the card cannot use the EVPN VPWS/VPLS over SRv6 service. |
|
Recommended action |
1. Execute the display hardware internal indexq all slot command to view the Srv6PrvtSid resource occupation information. 2. Delete the unused VPWS over SRv6 or VPLS over SRv6 configuration. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SRV6_POLICYSTAT_NORES
|
Message text |
Not enough resources for SRv6-TE policy statistics. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/SRV6_POLICYSTAT_NORES: -MDC=1-Slot=2; Not enough resources for SRv6-TE policy statistics. |
|
Impact |
The SRv6-TE policy statistics feature cannot take effect. |
|
Cause |
Statistical resources were insufficient for completing an operation. For example, when the SRv6-TE policy statistical resources on a card are insufficient, the card cannot collect SRv6-TE policy statistics but it can use the SRv6 tunnel. |
|
Recommended action |
1. Execute the display hardware internal indexq all slot command to view the Srv6 OutStatIdx resource occupation information. 2. Delete unused SRv6 TE policies. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SRV6_TNLINLIF_NORES
|
Message text |
Not enough tunnel INLIF resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/SRV6_TNLINLIF_NORES: -MDC=1-Slot=2; Not enough tunnel INLIF resources. |
|
Impact |
The SRv6 tunnel feature no longer takes effect. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the tunnel INLIF resources on a card are insufficient, the card cannot create an SRv6 tunnel. |
|
Recommended action |
1. Execute the display hardware internal indexq all slot command to view the Mpls Srv6TnlInlif resource occupation information. 2. Delete unused SRv6 TE policies. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SRV6_SRLIST_NORES
|
Message text |
Not enough IPv6_SR_List resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/SRV6_SRLIST_NORES: -MDC=1-Slot=2; Not enough IPv6_SR_List resources. |
|
Impact |
The SRv6 tunnel feature no longer takes effect. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the IPV6_SR_LIST resources on a card are insufficient, the card cannot create an SRv6 tunnel. |
|
Recommended action |
1. Execute the display hardware internal indexq all slot command to view the Mpls SrListIndex resource occupation information. 2. Delete unused SRv6 TE policies. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SRV6_CBTSSTAT_NORES
|
Message text |
Not enough resources for SRv6-TE Policy service class-based statistics. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/SRV6_CBTSSTAT_NORES: -MDC=1-Slot=2; Not enough resources for SRv6-TE Policy service class-based statistics. |
|
Impact |
CBTS-based traffic statistics for SRv6 tunnels cannot take effect. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the CBTS statistical resources for SRv6-TE policies on a card are insufficient, the card cannot perform CBTS-based traffic statistics for the SRv6 tunnels on the card. |
|
Recommended action |
1. Execute the display hardware internal indexq all slot command to view the Srv6 CbtsStatIdx resource occupation information. 2. Delete unused SRv6 TE policies. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SRV6_TBORPROFILE_NORES
|
Message text |
Hardware resources are not enough. The rate limit set for the SRv6-TE policy does not take effect. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/SRV6_TBORPROFILE_NORES:-MDC=1;Hardware resources are not enough. The rate limit set for the SRv6-TE policy does not take effect. |
|
Impact |
Rate limit settings cannot take effect on SRv6-TE policies. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the Tbindex or Profile resources on a card are insufficient, rate limit settings cannot take effect on the SRv6 policy tunnels. |
|
Recommended action |
1. Delete the rate limit commands configured for unused SRv6-TE policies. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SRV6_NOTSPT
|
Message text |
In standard mode, the card does not support vpws srv6. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VLL/4/SRV6_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpws srv6. |
|
Impact |
The VPWS over SRv6 feature cannot take effect. |
|
Cause |
In standard mode, the card does not support VPWS over SRv6. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CBTSACL_NORES
|
Message text |
Not enough acl resource to add vxlan cbts acl. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VXLAN/4/CBTSACL_NORES: -MDC=1-Slot=5; Not enough acl resource to add vxlan cbts acl. |
|
Impact |
CBTS for VXLAN packets cannot take effect. |
|
Cause |
Hardware resources were insufficient for completing an operation. For example, when the CBTS ACL resources for VXLANs on a card are insufficient, the card cannot perform CBTS for VXLAN packets. |
|
Recommended action |
1. Delete CBTS commands configured for unused VXLAN tunnels. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SERVICECLASS_NOTSPT
|
Message text |
In standard mode, the card does not support vxlan config service class. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VXLAN/4/SERVICECLASS_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vxlan config service class. |
|
Impact |
The system cannot configure service class values for VXLAN packets. |
|
Cause |
In standard mode, the card does not support configuring service class values for VXLAN packets. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
DSCP_NOTSPT
|
Message text |
In standard mode, the card does not support vxlan config dscp. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
VXLAN/4/DSCP_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vxlan config dscp. |
|
Impact |
The DSCP feature for VXLAN tunnels cannot take effect. |
|
Cause |
In standard mode, the card does not support VXLAN tunnel DSCP operations. |
|
Recommended action |
1. Change the system operating mode to SDN-WAN. The mode change requires a system reboot. Supported features in different system operating modes are different. Use caution when you change the system operating mode. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MPLS_PWSTAT_NOTSPT
|
Message text |
MPLS L2VPN does not support PW statistics. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/MPLS_PWSTAT_NOTSPT: -MDC=1; MPLS L2VPN does not support PW statistics. |
|
Impact |
Packet statistics for MPLS L2VPN PWs cannot take effect. |
|
Cause |
The device does not support packet statistics for MPLS L2VPN PWs. |
|
Recommended action |
If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
VP_NORES
|
Message text |
Not enough VP resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/VP_NORES: -MDC=1-Slot=4; Not enough VP resources. |
|
Impact |
VPWS over MPLS, VPLS over MPLS, and EVPN VPWS/VPLS over SRv6 services cannot take effect. |
|
Cause |
Hardware resources on the card were insufficient for completing an operation. For example, when the VP resources on a card are insufficient, the card cannot use the VPWS over MPLS/VPLS over MPLS/EVPN VPWS/VPLS over SRv6 service. |
|
Recommended action |
1. Execute the display hardware internal mpls global-var rsc vp command to view VP resource occupation information. 2. Delete the unused VPWS over MPLS, VPLS over MPLS, and EVPN VPWS/VPLS over SRv6 services configuration. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
FAST_SWITCH_NORES
|
Message text |
Not enough Fast_Switch resources |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
MPLS/4/ FAST_SWITCH_NORES: -MDC=1-Slot=2; Not enough Fast_Switch resources. |
|
Impact |
Service packet loss might occur. |
|
Cause |
Fast switching resources on the card were insufficient for completing an operation. For example, when the fast switching resources on a card are insufficient, the fast switching feature loses effect but the SRv6 tunnel can be used normally. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Warning) |
|
Example |
MPLS/4/MPLS_HARD_RESOURCE_NOENOUGH: No enough hardware resource for MPLS. |
|
Impact |
New LSPs cannot be established. |
|
Cause |
Too many MPLS hardware resources were used, for example, by excessive number of LSPs. |
|
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 (Informational) |
|
Example |
MPLS/6/MPLS_HARD_RESOURCE_RESTORE: Hardware resources for MPLS are restored. |
|
Impact |
No negative impact on the system. |
|
Cause |
Hardware resources for MPLS changed from insufficient to sufficient. |
|
Recommended action |
No action is required. |
MSDP messages
This section contains MSDP messages.
MSDP_PEER_CLOSE
|
Message text |
Stopped a session with peer [STRING]. |
|
Variable fields |
$1: IP address of an MSDP peer. |
|
Severity level |
5 (Notification) |
|
Example |
MSDP/5/MSDP_PEER_CLOSE: Stopped a session with peer 192.168.0.1. |
|
Impact |
SA messages cannot be forwarded between MSDP peers. |
|
Cause |
· The forwarding path between MSDP peers failed. · The local or remote MSDP peer was deleted. · The TCP connection between MSDP peers was disconnected. |
|
Recommended action |
1. Use the display this command on the local device and the remote device to identify whether an MSDP peer has been configured. ¡ If yes, go to step 2. ¡ If no, use the peer command to configure an MSDP peer. 2. Use the display this command on the local device and the remote device to identify whether the authentication configurations for MSDP peers are the same. ¡ If yes, go to step 3. ¡ If no, use the peer password command to configure the same authentication settings for MSDP peers or use the command to cancel the authentication configurations for both MSDP peers. 3. Use the display this command on the local device and the remote device to identify whether the interface used to establish a TCP connection is correct. ¡ If yes, go to step 4. ¡ If no, use the peer command to configure a correct interface. 4. Use the ping command on the local device to test the connectivity with the remote device. ¡ If the ping succeeds, go to step 6. ¡ If the ping fails, go to step 5. 5. Use the display ip routing-table command on the local device and the remote device to identify whether the unicast routes to each other are normal. ¡ If the unicast routes are normal, go to step 6. ¡ If the unicast routes are abnormal, address the route issues. 6. Use the display msdp peer-status command on the local device and the remote device to identify the state of the MSDP peer. ¡ If the State field is Established, go to step 7. ¡ If the State field is Shutdown, execute the undo shutdown command in MSDP view. 7. Identify whether the reset msdp peer command is executed on the remote device. ¡ If yes, wait for the TCP connection to be re-established. ¡ If no, go to step 8. 8. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MSDP_PEER_START
|
Message text |
Started a session with peer [STRING]. |
|
Variable fields |
$1: IP address of an MSDP peer. |
|
Severity level |
5 (Notification) |
|
Example |
MSDP/5/MSDP_PEER_START: Started a session with peer 192.168.0.1. |
|
Impact |
No negative impact on the system. SA messages can be forwarded between MSDP peers. |
|
Cause |
· The forwarding path between the local device and remote device was restored. · The device established an MSDP session with a peer for the first time. |
|
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 (Notification) |
|
Example |
MSDP/5/MSDP_PEER_START: NSR started a session with peer 192.168.0.1. |
|
Impact |
No negative impact on the system. SA messages can be forwarded between MSDP peers. |
|
Cause |
NSR recovered the MSDP session between the device and a peer. |
|
Recommended action |
No action is required. |
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, A) entries allowed to be cached for the MSDP peer. |
|
Severity level |
5 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
The maximum number of (S, A) entries allowed to be cached for the MSDP peer was already reached. |
|
Recommended action |
1. Use the peer sa-cache-maximum command to increase the maximum number of (S, A) entries allowed to be cached for the MSDP peer or reduce the number of (S, A) entries. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
MTLK/6/MTLK_UPLINK_STATUS_CHANGE: The uplink of monitor link group 1 is up. |
|
Impact |
When the monitor link group is in down state, the links in the group cannot forward traffic. |
|
Cause |
When the number of uplink interfaces in up state in a monitor link group is less than the specified threshold, the monitor link group goes down. When the number of uplink interfaces in up state reaches the threshold, the monitor link group comes up. |
|
Recommended action |
Troubleshoot the uplink when it fails. |
MTP messages
This section contains MTP messages.
MTP_PING_INFO
|
Message text |
Ping information, (Base: [STRING]), (Result: [STRING]). |
|
Variable fields |
$1: Basic information about the ping operation, including time, destination IP address, VRF index, protocol module information (module name and instance name), and the number of sent ping packets. The instance name in the protocol module information can be empty. $2: Result of the ping operation, including the number of successfully sent ping packets and ping packet result information. The ping packet result information includes the ping packet length, sequence, and result. |
|
Severity level |
6 (Informational) |
|
Example |
MTP/6/MTP_PING_INFO: Ping information, (Base: Time = 09:39:18, Destination IP = 10.11.1.1, VrfIndex = 0, Protocol Module = BGP (default), Packet Number = 9), (Result: Success = 9, Length 100 ping 1 success, Length 100 ping 2 success, Length 100 ping 3 success, Length 1000 ping 4 success, Length 1000 ping 5 success, Length 1000 ping 6 success, Length 4000 ping 7 success, Length 4000 ping 8 success, Length 4000 ping 9 success). |
|
Impact |
No negative impact on the system. |
|
Cause |
With MTP enabled, the device automatically pinged a neighbor and recorded the ping result when the neighbor's hold timer expired. |
|
Recommended action |
Troubleshoot the issue as follows: · Troubleshoot the link according to the ping result information. · Execute the display protocol troubleshooting command to view the neighbor disconnection reason for the specified routing protocol. · Execute the display logbuffer command to view detailed MTP information. |
MTP_TRACERT_INFO
|
Message text |
Tracert information, (Base: [STRING]), (Result: [STRING]). |
|
Variable fields |
$1: Basic information about the tracert operation, including time, destination IP address, VRF index, maximum number of hops allowed for a probe packet, number of probe packets to send per hop, and protocol module information (module name and instance name). The instance name in the protocol module information can be empty. $2: Result of the tracert operation, including the IP address of each hop, number of the AS that each hop belongs to (optional), and the number of probe successes. If a hop does not respond, no result will be displayed for the hop. |
|
Severity level |
6 (Informational) |
|
Example |
MTP/6/MTP_TRACERT_INFO: Tracert information, (Base: Time = 10:39:18, Destination IP = 10.11.1.1, VrfIndex = 0, MaxHop = 30, Packet Number = 3, Protocol Module = BGP (default)), (Result: TTL 1 Response IP = 10.2.1.1 Success = 3, TTL 2 Response IP = 10.11.1.1 [ AS 100 ] Success = 3). |
|
Impact |
No negative impact on the system. |
|
Cause |
With MTP enabled, the device automatically traced the route to the neighbor and recorded the tracert result when the neighbor's hold timer expired. |
|
Recommended action |
Troubleshoot the issue as follows: · Troubleshoot the link according to the tracert result information. · Execute the display protocol troubleshooting command to view the neighbor disconnection reason for the specified routing protocol. · Execute the display logbuffer command to view detailed MTP information. |
NAT messages
This section contains NAT messages.
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 (Warning) |
|
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. |
|
Impact |
The configuration succeeds but does not take effect. |
|
Cause |
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 |
1. Use the display nat all command to identify whether multiple interfaces reference the same address group or public addresses. ¡ If multiple interfaces reference the same address group or public addresses, specify the same service card for the interfaces. Execute the undo nat service command to cancel the specified traffic processing slots for the interfaces that require configuration changes. Then, execute the nat service command to specify the same traffic processing slot for the interfaces. ¡ If no multiple interfaces reference the same address group or public addresses, go to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_AGENCY_ALG_FAILED
|
Message text |
Failed to enable ALG for the user over Ethernet agency module, because not enough ACL resources are available. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_AGENCY_ALG_FAILED: Failed to enable ALG for the user over Ethernet agency module, because not enough ACL resources are available. |
|
Impact |
The system cannot provide the ALG service for agency users that have successfully come online. |
|
Cause |
The hardware ACL resources are insufficient. |
|
Recommended action |
1. Use the display qos-acl resource command to check the hardware ACL resources. ¡ If the hardware ACL resources are insufficient, cancel unnecessary ACL settings or keep the settings unchanged. ¡ If the hardware ACL resources are sufficient, go to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_BANDWIDTH_EXCEED
|
Message text |
Bandwidth usage of the CGN card reached [UINT32]%. |
|
Variable fields |
$1: Bandwidth usage threshold. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_BANDWIDTH_EXCEED: Bandwidth usage of the CGN card reached 90%. |
|
Impact |
The CGN card bandwidth usage exceeds the threshold. If it continues to increase, services might be damaged. |
|
Cause |
This message is sent when the bandwidth usage of the CGN card exceeds the threshold set by the nat log bandwidth-usage threshold command. |
|
Recommended action |
1. Use the display nat statistics packet command in any view to identify whether the current traffic or history peak traffic of the CGN card exceeds the bandwidth usage threshold. ¡ If the current traffic or history peak traffic of the CGN card approaches the bandwidth usage threshold, go to step 2. ¡ If the current traffic or history peak traffic of the CGN card does not approach the bandwidth usage threshold, go to step 3. 2. Scale out the CGN card, and then identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_BANDWIDTH_RECOVERY
|
Message text |
Bandwidth usage of the CGN card dropped below alarm threshold([UINT32]%). |
|
Variable fields |
$1: Bandwidth usage threshold. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_BANDWIDTH_RECOVERY: Bandwidth usage of the CGN card dropped below alarm threshold(90%). |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when the bandwidth usage of the CGN card drops below 87.5% of the threshold set by the nat log bandwidth-usage threshold command. |
|
Recommended action |
No action is required. |
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)=([UINT16])[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. $12: Event description: ¡ NAT EIM entry created: A NAT EIM entry was created. The value for the event type field is 8. ¡ Aged for timeout: A NAT EIM entry was deleted because it aged out. The value for the event type field is 2. ¡ Aged for reset or config-change: A NAT EIM entry was deleted by configuration. The value for the event type field is 3. |
|
Severity level |
6 (Informational) |
|
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; |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when a NAT EIM entry is created or removed. |
|
Recommended action |
No action is required. |
NAT_EIM_MODE_PORT_USAGE_ALARM
|
Message text |
Ratio of assigned port count to the specified [STRING] is [STRING]%, reaching the port usage threshold. Protocol=[STRING]; OrigSrcIP=[IPADDR]; VPNInstance=[STRING]; NATIP=[IPADDR]; ConnectCount=[UINT16]. |
|
Variable fields |
$1: Usage type for the alarm. ¡ port-limit: Maximum number of ports that can be assigned to a protocol. This value is set by the port-limit command. ¡ block-size: Port block size. $2: Percentage. $3: Protocol type. ¡ UDP: UDP protocol. ¡ TCP: TCP protocol. ¡ ICMP: ICMP protocol. ¡ TOTAL: All protocols. $4: Source IP address. $5: Source VPN instance name. $6: Source IP address after translation. $7: Number of connections. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_EIM_MODE_PORT_USAGE_ALARM: Ratio of assigned port count to the specified port-limit is 40%, reaching the port usage threshold. Protocol=UDP; OrigSrcIP=1.1.1.211; VPNInstance=-; NATIP=198.1.1.16; ConnectCount=40. |
|
Impact |
When the message is initially generated, it has no negative impact on services. However, if the number of sessions reaches the maximum number of ports that can be used by users, session establishment will fail. |
|
Cause |
This message is sent in the following conditions: · The usage of ports assigned to a protocol in a port block or the resource usage in the port block reaches or exceeds the threshold set by the nat log port-block port-usage threshold command. · The Endpoint-Independent Mapping mode is applied. |
|
Recommended action |
1. Use the display nat user-table command to obtain the values for the TCP/UDP/ICMP port current and Port total fields. Identify whether the port usage in port blocks reaches or exceeds the specified alarm threshold. ¡ If the port usage reaches or exceeds the specified alarm threshold, go to step 2. ¡ If the port usage is below the specified alarm threshold, go to step 3. 2. Use the nat log port-block port-usage threshold command to set a larger threshold for port usage in port blocks, and then identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_EIM_MODE_PORT_USAGE_RECOVER
|
Message text |
The ratio of assigned ports to the specified [STRING] is [UINT32]%, recovering from a usage threshold alarm. Protocol=[STRING]; OrigSrcIP=[IPADDR]; VPNInstance=[STRING]; NATIP=[IPADDR]; ConnectCount=[UINT16]. |
|
Variable fields |
$1: Usage type for the alarm. ¡ port-limit: Maximum number of ports that can be assigned to a protocol. This value is set by the port-limit command. ¡ block-size: Port block size. $2: Percentage. $3: Protocol type. ¡ UDP: UDP protocol. ¡ TCP: TCP protocol. ¡ ICMP: ICMP protocol. ¡ TOTAL: All protocols. $4: Source IP address. $5: Source VPN instance name. $6: Source IP address after translation. $7: Number of connections. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_EIM_MODE_PORT_USAGE_RECOVER: The ratio of assigned ports to the specified port-limit is 40%, recovering from a usage threshold alarm. Protocol=UDP; OrigSrcIP=1.1.1.211; VPNInstance=-; NATIP=198.1.1.16; ConnectCount=40. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent in the following conditions: · The usage of ports assigned to a protocol in a port block or the resource usage in the port block drops below 87.5% of 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_EIM_PORT_EXHAUST_ALARM
|
Message text |
Port allocation failed due to [STRING], Protocol=[STRING]; OrigSrcIP=[IPADDR]; VPNInstance=[STRING]; NATIP=[IPADDR]. |
|
Variable fields |
$1: Usage type for the alarm. ¡ port limit setting: Maximum number of ports that can be assigned to a protocol. This value is set by the port-limit command. ¡ port usage threshold violation: Port block size. $2: Protocol type. ¡ UDP: UDP protocol. ¡ TCP: TCP protocol. ¡ ICMP: ICMP protocol. ¡ TOTAL: All protocols. $3: Source IP address. $4: Source VPN instance name. $5: Source IP address after translation. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_EIM_PORT_EXHAUST_ALARM: Port allocation failed due to port limit setting, Protocol=UDP; OrigSrcIP=1.1.1.211; VPNInstance=-; NATIP=198.1.1.16. |
|
Impact |
Session establishment fails. |
|
Cause |
This message is sent in the following conditions: · The public port resources are used up. · The Endpoint-Independent Mapping mode is applied. |
|
Recommended action |
1. Use the display nat user-table command to identify whether the number of user sessions reaches the upper limit of resources that can be assigned by the port blocks. ¡ If the upper limit is reached, increase the pre-allocated port block size or configure extended port blocks, and then identify whether the message is generated again. If the message is no longer generated, the issue has been resolved. If the message is generated again, go to step 2. ¡ If the upper limit is not reached, go to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_EIM_PORT_EXHAUST_RECOVER
|
Message text |
Recovered from port allocation failure due to [STRING], Protocol=[STRING]; OrigSrcIP=[IPADDR]; VPNInstance=[STRING]; NATIP=[IPADDR]. |
|
Variable fields |
$1: Usage type for the alarm. ¡ port limit setting: Maximum number of ports that can be assigned to a protocol. This value is set by the port-limit command. ¡ port usage threshold violation: Port block size. $2: Protocol type. ¡ UDP: UDP protocol. ¡ TCP: TCP protocol. ¡ ICMP: ICMP protocol. ¡ TOTAL: All protocols. $3: Source IP address. $4: Source VPN instance name. $5: Source IP address after translation. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_EIM_PORT_EXHAUST_RECOVER: Recovered from port allocation failure due to port limit setting, Protocol=UDP; OrigSrcIP=1.1.1.211; VPNInstance=-; NATIP=198.1.1.16. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent in the following conditions: · The public port usage drops below 87.5%. · The Endpoint-Independent Mapping mode is applied. |
|
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)=([UINT16])[STRING]; |
|
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: A NAT session was created. The value for the event type field is 8. ¡ Active data flow timeout: The duration of a NAT session exceeded the active data flow time. The value for the event type field is 6. ¡ Normal over: A NAT session ended and was deleted. The value for the event type field is 1. ¡ Aged for timeout: A NAT session was deleted because it aged out. The value for the event type field is 2. ¡ Aged for reset or config-change: A NAT session was deleted by configuration. The value for the event type field is 3. ¡ Other: A NAT session was deleted because of other reasons. For example, it was deleted by another module. The value for the event type field is 254. |
|
Severity level |
6 (Informational) |
|
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)=03232017091640;EndTime_e(1014)=;Event(1048)=(8)Session created; |
|
Impact |
No negative impact on the system. |
|
Cause |
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_INSTANCE_SERVER_INVALID
|
Message text |
The NAT server with Easy IP is invalid because its global settings conflict with that of another NAT server in the same instance. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_INSTANCE_SERVER_INVALID: The NAT server with Easy IP is invalid because its global settings conflict with that of another NAT server in the same instance. |
|
Impact |
The NAT server mapping with Easy IP cannot take effect. |
|
Cause |
This message is sent when the same public network settings have been configured for both the NAT server mapping with Easy IP and another NAT server mapping in the same NAT instance. |
|
Recommended action |
1. Use the display nat instance command to check NAT server mappings in the NAT instance. 2. Use the nat server command to modify the conflicting NAT server mapping. The mapping of the protocol type, public address, and public port number must be unique for an internal server in a NAT instance. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_IP_ADD_FAILURE_ALARM
|
Message text |
Failed to add a subnet to global address pool [PoolName] (start address [address], mask [mask]). Failure cause: [Reasonstring]. |
|
Variable fields |
$1: Address pool name. $2: Start address. $3: Mask. $4: Failure reason: ¡ The subnet overlaps with other address ranges in the global address pool. ¡ The subnet overlaps with addresses in a NAT address group. ¡ The subnet overlaps with addresses in a NAT port block group. ¡ The subnet overlaps with addresses in a NAT server. ¡ The number of addresses in the global address pool has reached the upper limit. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_IP_ADD_FAILURE_ALARM: Failed to add a subnet to global address pool pool1 (start address 192.168.1.1, mask 255.255.0.0). Failure cause: The subnet overlaps with other address ranges in the global address pool. |
|
Impact |
The system cannot assign public IP addresses to users. |
|
Cause |
This message is sent in the following conditions: · The IP addresses in the subnet requested from the CP by the dynamic global address pool on the UP overlap with the IP addresses in other global address pools. · The number of IP addresses in the global address pool on the UP has reached the limit. |
|
Recommended action |
1. Check the value for the Failure cause field in the log message. ¡ If the value is The number of addresses in the global address pool has reached the upper limit, you cannot add new address to the global address pool. Go to step 2. ¡ If the value is not The number of addresses in the global address pool has reached the upper limit, the added address range conflicts with public addresses of an existing NAT configuration. Use the display nat ip-pool, display nat address-group, display nat port-block-group, or display nat server command to identify the conflicting public addresses, and then go to step 3. 2. Reduce the number of addresses in the global address pool, and then identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 4. 3. Delete the conflicting public addresses in the global address pool, NAT address group, NAT port block group, or NAT server mapping configurations, and then identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 4. 4. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_IP_EXHAUST_ALARM
|
Message text |
The IP addresses in NAT IP pool [STRING] ran out. |
|
Variable fields |
$1: Name of the address pool. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_IP_EXHAUST_ALARM: The IP addresses in NAT IP pool1 ran out. |
|
Impact |
The address pool cannot assign public addresses, which affects user services. |
|
Cause |
This message is sent when IP address resources in the address pool are used up. |
|
Recommended action |
1. Use the display nat ip-pool command to identify whether the addresses in the address pool are used up. ¡ If the addresses in the address pool are used up, go to step 2. ¡ If the addresses in the address pool are not used up, go to step 3. 2. Reduce the IP usage of the address pool or add new public addresses to the address pool as required. Then, identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_IP_EXHAUST_ALARM_RECOVER
|
Message text |
IP addresses in NAT IP pool [STRING] became available. |
|
Variable fields |
$1: Name of the address pool. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_IP_EXHAUST_ALARM_RECOVER: IP addresses in NAT IP pool pool1 became available. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when the IP usage in the address pool drops to or below 87.5%. |
|
Recommended action |
No action is required. |
NAT_IP_USAGE_ALARM
|
Message text |
NAT IP pool [STRING], total IP count [UINT16], active IP count [UINT16], exceeding the upper limit. |
|
Variable fields |
$1: Name of the address pool. $2: Total number of addresses in the pool. $3: Number of used addresses in the pool. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_IP_USAGE_ALARM: NAT IP pool 1, total IP count 100, active IP count 100, exceeding the upper limit. |
|
Impact |
When the message is initially generated, the issue has no negative impact on services. However, if new users come online and the maximum number of addresses that can be assigned by the address pool is reached, the address pool will have no available resources, which affects user services. |
|
Cause |
This message is sent when the IP usage in the address pool reaches or exceeds the subnet acquisition threshold set by the ip-usage-threshold command. |
|
Recommended action |
1. Use the display nat ip-pool command to check the IP usage of the global address pool. ¡ If the IP usage of the global address pool reaches or exceeds the threshold, go to step 2. ¡ If the IP usage of the global address pool is below the threshold, go to step 3. 2. Reduce the IP usage of the global address pool or use the ip-usage-threshold command to set a larger subnet acquisition threshold. Then, identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_IP_USAGE_ALARM_RECOVER
|
Message text |
NAT IP pool [STRING], total IP count [UINT16], active IP count [UINT16], recovering from a usage alarm. |
|
Variable fields |
$1: Name of the address pool. $2: Total number of addresses in the pool. $3: Number of used addresses in the pool. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_IP_USAGE_ALARM_RECOVER: NAT IP pool 1, total IP count 100, active IP count 87, recovering from a usage alarm. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when the IP usage in the address pool drops to or below 87.5% of the threshold. |
|
Recommended action |
No action is required. |
NAT_NAT444_SYSLOG
|
Message text |
All port block resources ran out in address group [STRING] id [UINT 16]. |
|
Variable fields |
$1: Address group name. $2: Address group ID. |
|
Severity level |
3 (Error) |
|
Example |
NAT/3/NAT_NAT444_SYSLOG: All port block resources ran out in address group 1 id 1. |
|
Impact |
Subsequent users cannot come online. |
|
Cause |
This message is sent when an address group has no available port blocks. |
|
Recommended action |
1. Use the display nat user-table command to identify whether the number of user sessions reaches the upper limit of ports that can be assigned by the port blocks. ¡ If the upper limit is reached, increase the pre-allocated port block size or configure extended port blocks, and then identify whether the message is generated again. If the message is no longer generated, the issue has been resolved. If the message is generated again, go to step 2. ¡ If the upper limit is not reached, go to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_NAT444_SYSLOG_RECOVER
|
Message text |
The port block resources had been restored in address group [STRING] id [UINT 16]. |
|
Variable fields |
$1: Address group name. $2: Address group ID. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_NAT444_SYSLOG_RECOVER: The port block resources had been restored in address group 1 id 1. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when the port block resource usage in the address group drops below 87.5% of the total number of port blocks. |
|
Recommended action |
No action is required. |
NAT_PAT_ALARM
|
Message text |
Address group [STRING] id [UINT16], usage reaches [UINT16]%. |
|
Variable fields |
$1: Address group name. $2: Address group ID. $3: Port block usage. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_PAT_ALARM: Address group 3 id 3, usage reaches 40%. |
|
Impact |
When the message is initially generated, the issue has no negative impact on services. However, if the number of ports assigned to users reaches the upper limit, new users will fail to apply for public ports, which affects user services. |
|
Cause |
This message is sent when the following conditions are met: · Configure the PAT mode and specify the port-by-port allocation method for an address group (by using the port-single-alloc enable command). · The port block usage reaches or exceeds the threshold set by the nat log port-block usage threshold command. |
|
Recommended action |
1. Use the display nat instance instance-name address-group command to check the resource usage of the NAT address group. ¡ If the resource usage of the NAT address group is below the specified threshold, go to step 4. ¡ If the resource usage of the NAT address group reaches or exceeds the specified threshold, go to step 2. 2. Use the nat log port-block usage threshold command to set a larger threshold. Then, identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 3. 3. Expand the address pool, and then identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 4. 4. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_PAT_RECOVERY
|
Message text |
Address group [STRING] id [UINT16], usage below [UINT16]%. |
|
Variable fields |
$1: Address group name. $2: Address group ID. $3: Port block usage. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_PAT_RECOVERY: Address group 3 id 3, usage below 35%. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when the port block usage in PAT mode drops below 87.5% of the threshold set by the nat log port-block usage threshold command. |
|
Recommended action |
No action is required. |
NAT_PORT_EXHAUST_ALARM
|
Message text |
Port allocation failed due to [STRING], Protocol=[STRING]; OrigSrcIP=[IPADDR]; VPNInstance=[STRING]; NATIP=[IPADDR]. |
|
Variable fields |
$1: Usage type for the alarm. ¡ port limit setting: Maximum number of ports that can be assigned to a protocol. This value is set by the port-limit command. ¡ port usage threshold violation: Port usage in the port block. $2: Protocol type. ¡ UDP: UDP protocol. ¡ TCP: TCP protocol. ¡ ICMP: ICMP protocol. ¡ TOTAL: All protocols. $3: Source IP address. $4: Source VPN instance name. $5: Source IP address after translation. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_PORT_EXHAUST_ALARM: Port allocation failed due to port limit setting, Protocol=UDP; OrigSrcIP=1.1.1.211; VPNInstance=-; NATIP=198.1.1.16. |
|
Impact |
Session establishment fails. |
|
Cause |
This message is sent in the following conditions: · The public port resources are used up. · The Connection-Dependent Mapping mode is applied. |
|
Recommended action |
1. Use the display nat user-table command to identify whether the number of user sessions reaches the upper limit of ports that can be assigned by the port blocks. ¡ If the upper limit is reached, increase the pre-allocated port block size or configure extended port blocks. Then, identify whether the message is generated again. If the message is no longer generated, the issue has been resolved. If the message is generated again, go to step 2. ¡ If the upper limit is not reached, go to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_PORT_EXHAUST_RECOVER
|
Message text |
Recovered from port allocation failure due to [STRING], Protocol=[STRING]; OrigSrcIP=[IPADDR]; VPNInstance=[STRING]; NATIP=[IPADDR]. |
|
Variable fields |
$1: Usage type for the alarm. ¡ port limit setting: Maximum number of ports that can be assigned to a protocol. This value is set by the port-limit command. ¡ port usage threshold violation: Port usage in the port block. $2: Protocol type. ¡ UDP: UDP protocol. ¡ TCP: TCP protocol. ¡ ICMP: ICMP protocol. ¡ TOTAL: All protocols. $3: Source IP address. $4: Source VPN instance name. $5: Source IP address after translation. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_PORT_EXHAUST_RECOVER: Recovered from port allocation failure due to port limit setting, Protocol=UDP; OrigSrcIP=1.1.1.211; VPNInstance=-; NATIP=198.1.1.16. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent in the following conditions: · The public port resource usage drops below 87.5%. · The Connection-Dependent Mapping mode is applied. |
|
Recommended action |
No action is required. |
NAT_PORT_USAGE_ALARM
|
Message text |
Ratio of assigned port count to the specified [STRING] is [STRING]%, reaching the port usage threshold. Protocol=[STRING]; OrigSrcIP=[IPADDR]; VPNInstance=[STRING]; NATIP=[IPADDR]; ConnectCount=[UINT16]. |
|
Variable fields |
$1: Usage type for the alarm. ¡ port-limit: Maximum number of ports that can be assigned to a protocol. This value is set by the port-limit command. ¡ block-size: Port block size. $2: Percentage. $3: Protocol type. ¡ UDP: UDP protocol. ¡ TCP: TCP protocol. ¡ ICMP: ICMP protocol. ¡ TOTAL: All protocols. $4: Source IP address. $5: Source VPN instance name. $6: Source IP address after translation. $7: Number of connections. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_PORT_USAGE_ALARM: Ratio of assigned port count to the specified port-limit is 40%, reaching the port usage threshold. Protocol=UDP; OrigSrcIP=1.1.1.211; VPNInstance=-; NATIP=198.1.1.16; ConnectCount=40. |
|
Impact |
When the message is initially generated, the issue has no negative impact on services. However, if the number of ports allocated to users reaches the upper limit, session establishment will fail. |
|
Cause |
This message is sent in the following conditions: · The usage of ports assigned to a protocol in a port block or the resource usage in the port block reaches or exceeds the threshold set by the nat log port-block port-usage threshold command. · The Connection-Dependent Mapping mode is applied. |
|
Recommended action |
1. Use the display nat user-table command to obtain the values for the TCP/UDP/ICMP port current and Port total fields. Identify whether the port usage in port blocks reaches or exceeds the specified alarm threshold. ¡ If the port usage reaches or exceeds the specified alarm threshold, go to step 2. ¡ If the port usage is below the alarm threshold, go to step 3. 2. Use the nat log port-block port-usage threshold command to set a larger threshold for port usage in port blocks, and then identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_PORT_USAGE_RECOVER
|
Message text |
The ratio of assigned ports to the specified [STRING] is [UINT32]%,recovering from a usage threshold alarm. Protocol=[STRING]; OrigSrcIP=[IPADDR]; VPNInstance=[STRING]; NATIP=[IPADDR]; ConnectCount=[UINT16]. |
|
Variable fields |
$1: Usage type for the alarm. ¡ port-limit: Maximum number of ports that can be assigned to a protocol. This value is set by the port-limit command. ¡ block-size: Port block size. $2: Percentage. $3: Protocol type. ¡ UDP: UDP protocol. ¡ TCP: TCP protocol. ¡ ICMP: ICMP protocol. ¡ TOTAL: All protocols. $4: Source IP address. $5: Source VPN instance name. $6: Source IP address after translation. $7: Number of connections. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_PORT_USAGE_RECOVER: The ratio of assigned ports to the specified port-limit is 40%, recovering from a usage threshold alarm. Protocol=UDP; OrigSrcIP=1.1.1.211; VPNInstance=-; NATIP=198.1.1.16; ConnectCount=40. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent in the following conditions: · The usage of ports assigned to a protocol in a port block or the resource usage in the port block drops below 87.5% of 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. |
NAT_PORTBLOCK_ALARM
|
Message text |
Address group [STRING] id [UINT16]; total port blocks [UINT16]; active port blocks [UINT16]; usage reaches [UINT16]%. |
|
Variable fields |
$1: Address group name. $2: Address group ID. $3: Total number of port blocks. $4: Numbers of port blocks that are allocated. $5: Port block usage. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_PORTBLOCK_ALARM: Address group 3 id 3; total port blocks 16575; active port blocks 6630; usage reaches 40%. |
|
Impact |
When the message is initially generated, the issue has no negative impact on services. However, if the number of ports assigned to users reaches the upper limit, new users will fail to apply for public ports. |
|
Cause |
This message is sent when the port block usage reaches or exceeds the threshold set by the nat log port-block usage threshold command. |
|
Recommended action |
1. Use the display current-configuration command to obtain the threshold for port usage in port blocks set by the nat log port-block usage threshold command. ¡ If the threshold is too small, use the nat log port-block usage threshold command to set a large threshold (not larger than 90%). Then, identify whether the message is generated again. If the message is no longer generated, the issue has been resolved. If the message is generated again, go to step 2. ¡ If the threshold is appropriate, go to step 2. 2. Add port block resources. (Use the port-range command to add port resources or use the address command to add address resources.) Then identify whether the message is generated again. ¡ If the message is no longer generated, the issue has been resolved. ¡ If the message is generated again, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NAT_PORTBLOCK_RECOVERY
|
Message text |
Address group [STRING] id [UINT16]; total port blocks [UINT16]; active port blocks [UINT16]; usage below [UINT16]%. |
|
Variable fields |
$1: Address group name. $2: Address group ID. $3: Total number of port blocks. $4: Number of port blocks that have been allocated. $5: Port block usage. |
|
Severity level |
5 (Notification) |
|
Example |
NAT/5/NAT_PORTBLOCK_RECOVERY: Address group 3 id 3; total port blocks 16575; active port blocks 5800; usage below 35%. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when the port block usage drops below 87.5% of the threshold set by using the nat log port-block usage threshold command. |
|
Recommended action |
No action is required. |
NAT_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 (Warning) |
|
Example |
NAT/4/NAT_PORTBLOCKGRP_MEMORY_WARNING: Insufficient memory caused by excessive public addresses in port block group 1. Please reconfigure the public address space. |
|
Impact |
NAT port block group configuration has failed to be deployed. |
|
Cause |
This message is sent when a public address range in a NAT port block group is too large and causes insufficient memory. |
|
Recommended action |
1. Obtain the NAT port block group ID from the log message, and then use the nat port-block-group command to enter the view of the NAT port block group. 2. Use the undo global-ip-pool command to remove public IP address ranges from the NAT port block group until this message is no longer generated. |
NAT_RESOURCE_MEMORY_WARNING
|
Message text |
Insufficient memory to alloc nat resource pool. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_RESOURCE_MEMORY_WARNING:Insufficient memory to alloc nat resource pool. |
|
Impact |
Failed to request public resources in CDM mode. |
|
Cause |
The device did not have enough memory when the EIM mode was switched to the CDM mode. |
|
Recommended action |
1. Use the display current-configuration command to check the device configuration and delete unnecessary configuration. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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. Values are: ¡ NAT addresses already bound to another service card. ¡ NAT service is not supported on this service card. ¡ the hardware resources are not enough. ¡ unknown error. 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. Values are: ¡ NAT addresses already bound to another service card. ¡ NAT service is not supported on this service card. ¡ the hardware resources are not enough. ¡ unknown error. |
|
Severity level |
4 (Warning) |
|
Example |
NAT/4/NAT_SERVICE_CARD_RECOVER_FAILURE: Failed to recover the configuration of binding the service card on slot 3 to interface GigabitEthernet0/0/2, because NAT service is not supported on this service card. |
|
Impact |
The service card cannot process NAT services. |
|
Cause |
This message is sent in the following conditions: · The NAT addresses have been bound to another service card. · The specified service card does not support the NAT service. · The hardware resources are not enough. |
|
Recommended action |
1. Check the value for the because field in the log message: ¡ If the value is NAT addresses already bound to another service card, use the display nat all command to check NAT configuration. Specify the same service card for interfaces that reference the same public addresses. ¡ If the value is NAT service is not supported on this service card, the hardware resources are not enough, or unknown error, identify the hardware issues of the service card. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND
This section contains ND messages.
ND_ALARM_CLEAR
|
Message text |
The number of ND entries dropped below the threshold. Threshold=[UINT32]; Number of dynamic ND entries=[UINT32]; Number of static ND entries=[UINT32]; Other ND entries = [UINT32]. |
|
Variable fields |
$1: Security threshold for global ND entries. $2: Number of dynamic ND entries. $3: Number of static ND entries. $4: Number of other ND entries. |
|
Severity level |
5 (Notification) |
|
Example |
ND/5/ND_ALARM_CLEAR: The number of ND entries dropped below the threshold. Threshold=100; Number of dynamic ND entries=59; Number of static ND entries=0; Other ND entries = 0. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of global ND entries (static and dynamic ND entries) dropped below the global security threshold. The global security threshold for ND entries is 60% of the customized system entry specification for the product. |
|
Recommended action |
No action is required. |
ND_CONFLICT
|
Message text |
[STRING] is inconsistent. |
|
Variable fields |
$1: Configuration type. Options include the following: · M_FLAG: Configuration flag for managed address · O_FLAG: Configuration flag for other information · CUR_HOP_LIMIT: Hop count limit · REACHABLE TIME: Time to maintain neighbor reachability · NS INTERVAL: Neighbor solicitation message interval · MTU: MTU for the advertised link · PREFIX VALID TIME: Valid lifetime of the prefix · PREFIX PREFERRED TIME: Preferred lifetime of the prefix for stateless address configuration |
|
Severity level |
6 (Informational) |
|
Example |
ND/6/ND_CONFLICT: PREFIX VALID TIME is inconsistent. |
|
Impact |
User service or traffic might be interrupted. |
|
Cause |
The device received a route advertisement message, causing inconsistency with the configuration on the neighboring router |
|
Recommended action |
Check the device configuration and modify it to match the configuration on the neighboring router |
ND_DUPADDR
|
Message text |
Duplicate address: [STRING] on the interface [STRING]. |
|
Variable fields |
$1: The IPv6 address to be assigned. $2: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
ND/6/ND_DUPADDR: Duplicate address: 33::8 on the interface Vlan-interface9. |
|
Impact |
No negative impact on the system. |
|
Cause |
The IPv6 address has been used by other devices in the network |
|
Recommended action |
Based on network planning and provisioning, assign a new IPv6 address to this interface |
ND_HOST_IP_CONFLICT
|
Message text |
The host [STRING] connected to interface [STRING] cannot communicate correctly, because it uses the same IPv6 address as the host connected to interface [STRING]. |
|
Variable fields |
$1: IPv6 address. $2: Interface name. $3: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
ND/4/ND_HOST_IP_CONFLICT: The host 2::2 connected to interface GigabitEthernet1/0/1 cannot communicate correctly, because it uses the same IPv6 address as the host connected to interface GigabitEthernet1/0/1. |
|
Impact |
User service or traffic might be interrupted. |
|
Cause |
Possible causes include: · Different hosts connected under this device are configured with the same IPv6 address · There is a ND attack with forged source IPv6 addresses in the network |
|
Recommended action |
1. Based on the log information, check the configuration of the hosts connected under the corresponding interface, and adjust the IPv6 address of conflicting hosts 2. Check the legitimacy of the host that sent the ND message. If the host is illegal, the network connection of the host needs to be disconnected 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_HOST_ROUTE_CONFLICT
|
Message text |
Interface [STRING] failed to add the host route for [STRING], because a host route to that IPv6 address already exists on another interface. |
|
Variable fields |
$1: Interface name. $2: IPv6 address. |
|
Severity level |
4 (Warning) |
|
Example |
ND/4/ ND_HOST_ROUTE_CONFLICT: Interface GigabitEthernet1/0/1 failed to add the host route for 2::2, because a host route to that IPv6 address already exists on another interface. |
|
Impact |
Traffic might be forwarded incorrectly. |
|
Cause |
The host route to that IPv6 address already exists on another interface. |
|
Recommended action |
1. Check the reason for the ND entry conflict. ¡ If the issue is caused by an IPv6 address conflict, assign an unused IP address to the host. ¡ If the issue is caused by a host migration, execute the undo ipv6 neighbor command to delete the ND entry for the old host. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_INTERFACE_ALARM_CLEAR
|
Message text |
The number of ND entries dropped below the threshold of Interface [STRING]. Threshold=[UINT32]; Number of dynamic ND entries=[UINT32]. |
|
Variable fields |
$1: Interface name. $2: Dynamic security threshold for the interface. $3: Number of dynamic ND entries on the interface. |
|
Severity level |
5 (Notification) |
|
Example |
ND/5/ND_INTERFACE_ALARM_CLEAR: The number of ND entries dropped below the threshold of Interface GigabitEthernet1/0/1. Threshold=100; Number of dynamic ND entries=59. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of dynamic ND entries on the interface dropped below the dynamic security threshold. The dynamic security threshold for an interface is 60% of the dynamic ND learning limit set by the ipv6 neighbors max-learning-num command. |
|
Recommended action |
No action is required. |
ND_INTERFACE_THRESHOLD_EXCEED
|
Message text |
The number of ND entries exceeded the threshold of Interface [STRING]. Threshold=[UINT32]; Number of dynamic ND entries=[UINT32]. |
|
Variable fields |
$1: Interface name. $2: Dynamic alarm threshold for the interface. $3: Number of dynamic ND entries on the interface. |
|
Severity level |
4 (Warning) |
|
Example |
ND/4/ND_INTERFACE_THRESHOLD_EXCEED: The number of ND entries exceeded the threshold of Interface GigabitEthernet1/0/1. Threshold=100; Number of dynamic ND entries=81. |
|
Impact |
The interface cannot learn new dynamic neighbor entries, which might cause service unreachability. |
|
Cause |
The number of dynamic ND entries learned by the interface exceeded the alarm threshold. The alarm threshold is 80% of the dynamic ND learning limit set by the ipv6 neighbors max-learning-num command. |
|
Recommended action |
1. Execute the display ipv6 neighbors command to view the dynamic ND entries on the interface. 2. Based on the network planning and service deployment, identify whether the dynamic ND entries are necessary. ¡ If the dynamic ND entries are necessary, go to step 3. ¡ If the dynamic ND entries are not necessary, execute the undo ipv6 neighbor command to delete ND entries. Make sure the operation does not affect services. 3. Execute the ipv6 neighbors max-learning-num command to set a larger dynamic ND learning limit for the interface. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_IP_CONFLICT
|
Message text |
Host IPv6 address conflicted. Local IPv6 address=[STRING]; LocalMac=[STRING]; LocalInterface=[ STRING]]; LocalSVlan=[UINT32]; LocalCVlan=[UINT32]; Remote IPv6 address=[STRING];RemoteMac=[STRING]; RemoteSVlan=[UINT32]; RemoteCVlan=[UINT32]. |
|
Variable fields |
$1: IPv6 address of the local device. $2: MAC address of the local device. $3: Name of the interface on the local device. $4: Outer VLAN ID for the interface on the local device. $5: Inner VLAN ID for the interface on the local device. $6: IPv6 address of the endpoint. $7: MAC address of the endpoint. $8: Outer VLAN ID for the interface on the endpoint. $9: Inner VLAN ID for the interface on the endpoint. |
|
Severity level |
4 (Warning) |
|
Example |
ND/4/ND_IP_CONFLICT: Host IPv6 address conflicted. Local IPv6 address=0:0::0:1; LocalMac=0300-1602-00e0; LocalInterface= vlan-interface 10; LocalSVlan=0; LocalCVlan=0; Remote IPv6 address=0:0::0:1; RemoteMac=0300-1602-00e1; RemoteSVlan=1; RemoteCVlan=1. |
|
Impact |
If you do not clear the IPv6 address conflict immediately, user services or traffic might be interrupted. |
|
Cause |
The interface on the local device received a packet with the same IP address as the interface IP address after you enable recording conflicts between the endpoints and local device by using the ipv6 nd local-conflict record enable command. Possible reasons are: · Another device on the network is configured with the same IPv6 address as that of the local device. · An ND attack that forges the source IPv6 address exists on the network. |
|
Recommended action |
1. Identify whether another device on the network is configured with the same IPv6 address as that of the local device. ¡ If you can identify the device configured with the same IPv6 address, change the IPv6 address of the device. ¡ If you cannot identify the device configured with the same IPv6 address, change the IPv6 address of the corresponding interface. Make sure the operation does not affect services. 2. Identify whether an ND attack exists on the network and identify the attack source. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_IP_CONFLICT_RESUME
|
Message text |
Host IPv6 address conflict was resolved. Local IPv6 address=[STRING],LocalMac=[STRING], LocalInterface =[ STRING], LocalSVlan=[UINT32], LocalCVlan=[UINT32], Remote IPv6 address=[STRING], RemoteMac=[ STRING], RemoteSVlan=[UINT32], RemoteCVlan=[UINT32] |
|
Variable fields |
$1: IPv6 address of the local device. $2: MAC address of the local device. $3: Name of the interface on the local device. $4: Outer VLAN ID for the interface on the local device. $5: Inner VLAN ID for the interface on the local device. $6: IPv6 address of the endpoint. $7: MAC address of the endpoint. $8: Outer VLAN ID for the interface on the endpoint. $9: Inner VLAN ID for the interface on the endpoint. |
|
Severity level |
5 (Notification) |
|
Example |
ND/5/ND_IP_CONFLICT_RESUME: Host IPv6 address conflict was resolved. Local IPv6 address=0:0::0:1, LocalMac=0300-1602-00e0, LocalInterface = vlan-interface 10, LocalSVlan=0, LocalCVlan=0, Remote IPv6 address=0:0::0:1 RemoteMac=0300-1602-00e1, RemoteSVlan=1, RemoteCVlan=1 |
|
Impact |
No negative impact on the system. |
|
Cause |
No conflict occurs within 3 minutes after you enable recording conflicts between the endpoints and local device by using the ipv6 nd local-conflict record enable command and an IP address conflict occurs. |
|
Recommended action |
No action is required. |
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: Name of the interface receiving ND packets. $2: Source MAC address in ND packets. $3: Link layer source MAC address in ND packets. |
|
Severity level |
6 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
Enable ND protocol packet source MAC address consistency check with 'execute ipv6 nd mac-check enable' command, and enable ND log information with 'execute ipv6 nd check log enable' command. If the MAC address in the received ND protocol packet and the MAC address in the source link layer option address do not match, check the legitimacy of the link layer source MAC address corresponding to the host. If the host is illegal, disconnect it from the network. |
|
Recommended action |
1. Check the legality of the link layer source MAC address corresponding to the host. If the host is illegal, it needs to be disconnected from the network. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_MAXNUMBER
|
Message text |
The number of dynamic neighbor entries for the device has reached the maximum. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
ND/6/ND_MAXNUMBER: The number of dynamic neighbor entries for the device has reached the maximum. |
|
Impact |
The device cannot learn new dynamic neighbor entries, which might cause service unreachability. |
|
Cause |
The number of dynamic neighbor entries learned by the device reached the upper limit. |
|
Recommended action |
1. Execute the display ipv6 neighbors command to obtain IPv6 neighbor information. 2. Based on the network planning and service deployment, identify whether the dynamic ND entries are necessary. ¡ If the dynamic ND entries are necessary, go to step 3. ¡ If the dynamic ND entries are not necessary, execute the undo ipv6 neighbor command to delete ND entries. Make sure the operation does not affect services. 3. Execute the ipv6 neighbors max-learning-number command to set a larger dynamic ND learning limit for the device. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_MAXNUMBER_IF
|
Message text |
The number of dynamic neighbor entries on interface [STRING] has reached the maximum. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
ND/6/ND_MAXNUMBER_IF: The number of dynamic neighbor entries on interface GigabitEthernet3/0/1 has reached the maximum. |
|
Impact |
The interface cannot learn new dynamic neighbor entries, which might cause service unreachability. |
|
Cause |
The number of dynamic neighbor entries learned by the interface reached the upper limit. |
|
Recommended action |
1. Execute the display ipv6 neighbors command to obtain IPv6 neighbor information on the interface. 2. Based on the network planning and service deployment, identify whether the dynamic ND entries learned by the interface are necessary. ¡ If the dynamic ND entries are necessary, go to step 3. ¡ If the dynamic ND entries are not necessary, execute the undo ipv6 neighbor command to delete ND entries. Make sure the operation does not affect services. 3. Execute the ipv6 neighbors max-learning-num command to set a larger dynamic ND learning limit for the interface. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_MAXNUMBER_SLOT
|
Message text |
Pattern 1: The maximum number of dynamic neighbor entries for slot [INT32] reached. Pattern 2: The maximum number of dynamic neighbor entries for chassis [INT32] slot [INT32] reached. |
|
Variable fields |
Pattern 1: $1: Slot number. Pattern 2: $1: Chassis number. $2: Slot number. |
|
Severity level |
3 (Error) |
|
Example |
ND/3/ND_MAXNUMBER_SLOT: The maximum number of dynamic neighbor entries for slot 2 reached. ND/3/ND_MAXNUMBER_SLOT: The maximum number of dynamic neighbor entries for chassis 1 slot 2 reached. |
|
Impact |
The card cannot learn new ND entries, which might cause service unreachability. |
|
Cause |
Pattern 1: The maximum number of dynamic neighbor entries for the specified slot was reached. Pattern 2: The maximum number of dynamic neighbor entries for the specified chassis in the specified slot was reached. |
|
Recommended action |
1. Execute the display ipv6 neighbors command to obtain IPv6 neighbor information on the card. 2. Based on the network planning and service deployment, identify whether the dynamic ND entries learned by the card are necessary. ¡ If the dynamic ND entries are necessary, go to step 3. ¡ If the dynamic ND entries are not necessary, execute the undo ipv6 neighbor command to delete ND entries. Make sure the operation does not affect services. 3. Execute the ipv6 neighbors max-learning-number command to set a larger dynamic ND learning limit for the card. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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: Source IPv6 address of the dropped packet. $2: Port name of the dropped packet. $3: Total number of packets dropped by the port. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
The network might have spoofing attacks with RA messages in the network, affecting normal device operation. |
|
Cause |
RA Guard detected illegal RA messages, indicating possible RA message spoofing attacks in the network. |
|
Recommended action |
1. Check if the device sending the RA message is legitimate, if the device is illegal, disconnect it from the network 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_SET_PORT_TRUST_NORESOURCE
|
Message text |
Not enough resources to complete the operation. |
|
Variable fields |
N/A |
|
Severity level |
2 (Critical) |
|
Example |
ND/2/ND_SET_PORT_TRUST_NORESOURCE: Not enough resources to complete the operation. |
|
Impact |
Insufficient driver resources affecting normal service operations. |
|
Cause |
Insufficient driver resources during port rule deployment. |
|
Recommended action |
1. Release device driver resources and redeploy 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_SET_VLAN_REDIRECT_NORESOURCE
|
Message text |
Not enough resources to complete the operation. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
ND/6/ND_SET_VLAN_REDIRECT_NORESOURCE: Not enough resources to complete the operation. |
|
Impact |
Insufficient driver resources affecting normal service operations. |
|
Cause |
Insufficient driver resources during VLAN rule issuance. |
|
Recommended action |
1. Release device driver resources and reissue 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_SLOT_ALARM_CLEAR
|
Message text |
Pattern 1: The number of ND entries dropped below the threshold of slot. Slot name=[UINT32]; Threshold=[ UINT32]; Number of dynamic ND entries=[UINT32]. Pattern 2: The number of ND entries dropped below the threshold of chassis [UINT16] slot [UINT16]. Threshold=[ UINT32]; Number of dynamic ND entries=[UINT32]. |
|
Variable fields |
Pattern 1: $1: Slot number. $2: Dynamic security threshold for the card. $3: Number of dynamic ND entries on the card. Pattern 2: $1: Chassis number. $2: Slot number. $3: Security threshold for the card. $4: Number of dynamic ND entries on the card. |
|
Severity level |
5 (Notification) |
|
Example |
Pattern 1: ND/5/ND_SLOT_ALARM_CLEAR: The number of ND entries dropped below the threshold of slot. Slot name=1; Threshold=100; Number of dynamic ND entries=59. Pattern 2: ND/5/ND_SLOT_ALARM_CLEAR: The number of ND entries dropped below the threshold of chassis 1 slot 1. Threshold=100; Number of dynamic ND entries=59. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of dynamic ND entries dropped below the dynamic security threshold for the card. The dynamic security threshold for a card is 60% of the dynamic ND learning limit for a card set by the ipv6 neighbors max-learning-number command. |
|
Recommended action |
No action is required. |
ND_SLOT_THRESHOLD_EXCEED
|
Message text |
Pattern 1: The number of ND entries exceeded the threshold of slot. Slot name=[UINT32];, Threshold=[UINT32]; Number of dynamic ND entries=[UINT32]. Pattern 2: The number of ND entries exceeded the threshold of chassis [UINT16] slot [UINT16]. Threshold=[UINT32]; Number of dynamic ND entries=[UINT32]. |
|
Variable fields |
Pattern 1: $1: Slot number. $2: Dynamic alarm threshold for the card. $3: Number of dynamic ND entries on the card. Pattern 2: $1: Chassis number. $2: Slot number. $3: Alarm threshold for the card. $4: Number of dynamic ND entries on the card. |
|
Severity level |
4 |
|
Example |
Pattern 1: ND/4/ND_SLOT_THRESHOLD_EXCEED: The number of ND entries exceeded the threshold of slot. Slot name=1; Threshold=100; Number of dynamic ND entries=80. Pattern 2: ND/4/ND_SLOT_THRESHOLD_EXCEED: The number of ND entries exceeded the threshold of chassis 1 slot 1. Threshold=100; Number of dynamic ND entries=80. |
|
Impact |
The card cannot learn new ND entries, which might cause service unreachability. |
|
Cause |
The number of dynamic ND entries exceeded the dynamic alarm threshold for the card. The alarm threshold for a card is 80% of the maximum number of dynamic ND learning limit for a card set by the ipv6 neighbors max-learning-number command. |
|
Recommended action |
1. Execute the display ipv6 neighbors command to check the dynamic ND entries on the card. 2. Based on the network planning and service deployment, identify whether the dynamic ND entries learned by the card are necessary. ¡ If the dynamic ND entries are necessary, go to step 3. ¡ If the dynamic ND entries are not necessary, execute the undo ipv6 neighbor command to delete ND entries. Make sure the operation does not affect services. 3. Execute the ipv6 neighbors max-learning-number command to set a larger dynamic ND learning limit for the card. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_SPEEDLIMIT_ALARM
|
Message text |
Packet rate exceeded the rate limit. ThresholdRate=[UINT32]; CurrentRate=[UINT32]; SuppressType=[STRING]. |
|
Variable fields |
$1: Alarm threshold for ND packets or ND Miss messages sent per second. $2: Current peak number of ND packets or ND Miss messages sent per second. $3: Limit object, including ND packets or ND Miss messages. |
|
Severity level |
4 (Warning) |
|
Example |
ND/4/ND_SPEEDLIMIT_ALARM: Packet rate exceeded the rate limit. ThresholdRate=50; CurrentRate=60; SuppressType=ND. |
|
Impact |
The device might not send ND requests correctly, which affects ND learning and might cause traffic forwarding failure. |
|
Cause |
The sending rate of ND packets or ND Miss messages exceeded the alarm threshold, or an ND attack exists on the network. |
|
Recommended action |
1. Identify whether an ND attack exists on the network based on the message. Capture packets to identify and analyze the source of IPv6 packets that trigger ND resolution. If the source is unreasonable, limit attack packet sending for the attack source. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_SPEEDLIMIT_ALARM_CLEAR
|
Message text |
Packet rate dropped below the rate limit. ThresholdRate=[UINT32]; CurrentRate=[UINT32]; SuppressType=[STRING]. |
|
Variable fields |
$1: Alarm threshold for ND packets or ND Miss messages sent per second. $2: The current peak number of ND packets or ND Miss messages sent per second. $3: Limit object, including ND packets and ND Miss messages. |
|
Severity level |
5 (Notification) |
|
Example |
ND/5/ND_SPEEDLIMIT_ALARM_CLEAR: Packet rate dropped below the rate limit. ThresholdRate=50; CurrentRate=60; SuppressType=ND. |
|
Impact |
No negative impact on the system. |
|
Cause |
The sending rate of ND packets or ND Miss messages dropped below the alarm threshold. To avoid frequent alarm notifications or alarm recovery notifications, the device does not output notifications within one minute after the alarm recovers. |
|
Recommended action |
No action is required. |
ND_SUPPR_ALARM_CLEAR
|
Message text |
The number of ND suppression entries dropped below the threshold. Threshold=[UINT32], Number of ND suppression entries=[UINT32]) |
|
Variable fields |
$1: Threshold for ND suppression entries. $2: Number of ND suppression entries. |
|
Severity level |
5 (Notification) |
|
Example |
ND/5/ND_SUPPR_ALARM_CLEAR: The number of ND suppression entries dropped below the threshold. Threshold=100; Number of ND Suppression entries=59. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of ND suppression entries dropped below 60% of the threshold. |
|
Recommended action |
No action is required. |
ND_SUPPR_THRESHOLD_EXCEED
|
Message text |
The number of ND suppression entries exceeded the threshold. Threshold=[UINT32]; Number of ND suppression entries=[UINT32]. |
|
Variable fields |
$1: Threshold for ND suppression entries. $2: Number of ND suppression entries. |
|
Severity level |
4 (Warning) |
|
Example |
ND/4/ND_SUPPR_THRESHOLD_EXCEED: The number of ND suppression entries exceeded the threshold. Threshold=100; Number of ND suppression entries=80. |
|
Impact |
The device cannot learn new ND suppression, which might cause the device to flood ND packets. This increases the number of multicast packets in the network, affecting device performance. |
|
Cause |
The number of ND suppression entries exceeds 80% of the threshold. |
|
Recommended action |
1. Execute the display ipv6 nd suppression xconnect-group command to view ND suppression entries. 2. Based on network planning and provisioning, identify whether the ND suppression entries on the device are necessary for the user: ¡ If the ND suppression entries are necessary for the user, go to step 3 ¡ If the ND suppression entries are not necessary for the user, execute the reset ipv6 nd suppression xconnect-group command to clear ND suppression entries. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ND_THRESHOLD_EXCEED
|
Message text |
The number of ND entries exceeded the threshold. Threshold=[UINT32]; Number of dynamic ND entries=[UINT32]; Number of static ND entries=[UINT32]; Other ND entries = [UINT32]. |
|
Variable fields |
$1: Alarm threshold for global ND entries. $2: Number of dynamic ND entries. $3: Number of static ND entries. $4: Number of other ND entries. |
|
Severity level |
4 (Warning) |
|
Example |
ND/4/ND_THRESHOLD_EXCEED: The number of ND entries exceeded the threshold. Threshold=100; Number of dynamic ND entries=81; Number of static ND entries=0; Other ND entries = 0. |
|
Impact |
The device cannot learn new ND entries, which might cause service unreachability. |
|
Cause |
The number of global ND entries (static and dynamic ND entries) exceeded the global alarm threshold. The global alarm threshold is 80% of the customized system entry specification for the product. |
|
Recommended action |
1. Execute the display ipv6 neighbors all command to compare the numbers of static and dynamic ND entries. ¡ If the number of static ND entries is larger, go to step 2. ¡ If the number of dynamic ND entries is larger, go to step 3. 2. Based on the network planning and service deployment, identify whether the static ND entries are necessary. ¡ If the static ND entries are necessary, go to step 4. ¡ If the static ND entries are not necessary, execute the undo ipv6 neighbor command to delete ND entries or execute the reset ipv6 neighbors static command to clear static ND entries. Make sure the operation does not affect services. 3. Execute the ipv6 neighbors max-learning-number command to set a larger dynamic ND learning limit for the device. Execute the ipv6 neighbors max-learning-num command to set larger dynamic ND learning limits for interfaces. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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: New user's MAC address. $2: New user's outer VLAN ID. $3: New user's inner VLAN ID. $4: Name of the interface connecting to the new user. $5: Old user's MAC address. $6: Old user's outer VLAN ID. $7: Old user's inner VLAN ID. $8: Name of the interface connecting to the old user. $9: Endpoint user's IPv6 address. |
|
Severity level |
6 (Informational) |
|
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. |
|
Impact |
The network might have an IPv6 address conflict, which might cause user service or traffic interruption. |
|
Cause |
This message is sent when the device detects an IPv6 address conflict after you execute the ipv6 nd user-ip-conflict record enable command to enable recording user IPv6 address conflicts on the device. |
|
Recommended action |
1. Check all endpoint users' IPv6 addresses and change the conflicting user IPv6 addresses. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
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. |
|
Impact |
The impact is related to the command line contents in the CLI request. |
|
Cause |
A user performs a CLI operation. |
|
Recommended action |
No action is required. |
EDIT-CONFIG
|
Message text |
User ([STRING], [STRING], session ID [UINT]) performed an edit-config operation: message ID=[STRING], operation result=[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: Operation result, Succeeded or Failed. |
|
Severity level |
6 (Informational) |
|
Example |
XMLSOAP/6/EDIT-CONFIG: User (test, 192.168.56.1, session ID 1) performed an edit-config operation: message ID=101, operation result=Succeeded. |
|
Impact |
The impact is related to the entry to be operated in the edit-config request. |
|
Cause |
A user executed the edit-config operation. |
|
Recommended action |
· No action is required if the operation succeeded. · If the operation failed, identify whether the edit-config operation conflicts with the current configuration of the device. Alternatively, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
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 (Informational) |
|
Example |
XMLSOAP/6/EDIT-CONFIG: -MDC=1; User (test, 192.168.200.220, session ID 1), message ID=101, operation=merge DHCP/DHCPServerPoolStatic (PoolIndex=1, Ipv4Address=1.1.1.1), result=Failed. Attributes: CID="aaaaa", HType=1. |
|
Impact |
The impact is related to the entry to be operated in the edit-config request. |
|
Cause |
The device outputs this log message for each row operation for an <action> or <edit-config> operation. |
|
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 |
N/A |
|
Severity level |
7 (Debug) |
|
Example |
NETCONF/7/NETCONF_MSG_DEL: A NETCONF message was dropped. Reason: Packet size exceeded the upper limit. |
|
Impact |
No negative impact on the system. |
|
Cause |
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. Segment the request message and then re-encapsulate the segments before sending them to the device. As a best practice, collect alarm information, log messages, and configuration data, and contact Technical Support. |
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 (Debug) |
|
Example |
XMLSOAP/7/REPLY: -MDC=1; Sent a NETCONF reply to the client: Session ID=1, Content=</env:Body></env:Envelope>. |
|
Impact |
No negative impact on the system. |
|
Cause |
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. |
SOAP_XML_LOGIN
|
Message text |
[STRING] logged in from [STRING], session id [STRING]. |
|
Variable fields |
$1: Username. $2: User IP address. $3: ID of the NETCONF session. |
|
Severity level |
6 (Informational) |
|
Example |
NETCONF/6/SOAP_XML_LOGIN: test logged in from 192.168.56.101, session id 1. |
|
Impact |
A HTTP or HTTPS session resource is consumed. |
|
Cause |
A NETCONF over SOAP client logged in to the device. |
|
Recommended action |
No action is required. |
SOAP_XML_LOGOUT
|
Message text |
[STRING] logged out from [STRING], session id [STRING]. |
|
Variable fields |
$1: Username. $2: User IP address. $3: ID of the NETCONF session. |
|
Severity level |
6 (Informational) |
|
Example |
NETCONF/6/SOAP_XML_LOGOUT: test logged out from 192.168.56.101, session id 1. |
|
Impact |
A HTTP or HTTPS session resource is released. |
|
Cause |
A NETCONF over SOAP client logged out from the device. |
|
Recommended action |
No action is required. |
SSH_XML_LOGIN
|
Message text |
User ([STRING], [STRING], session ID=[STRING]) logged in. |
|
Variable fields |
$1: Username. $2: User IP address. $3: ID of the NETCONF session. |
|
Severity level |
6 (Informational) |
|
Example |
NETCONF/6/SSH_XML_LOGIN: User (test, 192.168.56.101, session ID=1) logged in. |
|
Impact |
An SSH session resource is consumed. |
|
Cause |
A NETCONF over SSH client logged in to the device. |
|
Recommended action |
No action is required. |
SSH_XML_LOGOUT
|
Message text |
User ([STRING], [STRING], session ID=[STRING]) logged out. |
|
Variable fields |
$1: Username. $2: User IP address. $3: ID of the NETCONF session. |
|
Severity level |
6 (Informational) |
|
Example |
NETCONF/6/SSH_XML_LOGOUT: User (test, 192.168.56.101, session ID=1) logged out. |
|
Impact |
An SSH session resource is released. |
|
Explanation |
A NETCONF over SSH client logged out from the device. |
|
Recommended action |
No action is required. |
THREAD
|
Message text |
Maximum number of NETCONF threads already reached. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
XMLCFG/3/THREAD: -MDC=1; Maximum number of NETCONF threads already reached. |
|
Impact |
New NETCONF over SSH sessions are not accepted. New NETCONF SOAP and RESTful requests are not accepted. The Web feature is unavailable. |
|
Cause |
The number of NETCONF threads already reached the upper limit. |
|
Recommended action |
Please try again later. |
NETSLICE
This section contains SRv6 network slicing messages.
NETSLICING_IF_BANDWIDTH_CHG
|
Message text |
The modified bandwidth value [UINT32] (Mbps) of interface [String] is less than the bandwidth value [UINT32] (Mbps) configured for slices. |
|
Variable fields |
$1: Edited bandwidth of the main interface. $2: Name of the main interface. $3: Bandwidth (of the main interface and its subinterfaces) specified for the network slice. |
|
Severity level |
4 (Warning) |
|
Example |
NETSLICE/4/NETSLICING_IF_BANDWIDTH_CHG: The modified bandwidth value10000 (Mbps) of the interface ForthGigE 3/0/32 is less than the bandwidth value 20000 (Mbps) configured for slices. |
|
Impact |
The edited bandwidth of the main interface does not take effect. |
|
Cause |
The edited bandwidth of the main interface is smaller than the bandwidth specified for the network slice. |
|
Recommended action |
Edit the bandwidth of the main interface based on the bandwidth (of the main interface and its subinterfaces) specified for the network slice. Make sure the edited bandwidth of the main interface is greater than the bandwidth specified for the network slice. |
NETSLICING_BANDWIDTH_CONFLICT
|
Message text |
The slice bandwidth configuration conflicts with some existing settings such as HQoS, exclusive bandwidth, CBQ, and MPLS TE bandwidth. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
NETSLICE/4/NETSLICING_BANDWIDTH_CONFLICT: The slice bandwidth configuration conflicts with some existing settings such as HQoS, exclusive bandwidth, CBQ, and MPLS TE bandwidth. |
|
Impact |
The slice bandwidth configuration does not take effect. |
|
Cause |
The bandwidth setting of the network slice conflicts with the HQoS, exclusive bandwidth, CBQ, and MPLS TE bandwidth reservation settings on the interface. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NETSLICING_BANDWIDTH_EXCEED
|
Message text |
The sum of the slice bandwidth and the channelized bandwidth configured for the interface exceeds the limit. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
NETSLICE/4/NETSLICING_ BANDWIDTH_EXCEED: The sum of the slice bandwidth and the channelized bandwidth configured for the interface exceeds the limit. |
|
Impact |
The slice bandwidth and the channelized bandwidth might not take effect. |
|
Cause |
The sum of the network slice bandwidth and channelized bandwidth exceeds the maximum bandwidth of the interface. |
|
Recommended action |
· Edit the slice bandwidth or the channelized bandwidth for the subinterfaces. · Use the bandwidth command to change the interface speed. |
NETSLICING_NO_ENOUGH_HARDWARE_RESOURCE
|
Message text |
Not enough hardware resources to complete the operation. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
NETSLICE/4/NETSLICING_NO_ENOUGH_HARDWARE_RESOURCE: Not enough hardware resources to complete the operation |
|
Impact |
The slice bandwidth does not take effect. |
|
Cause |
The hardware resources are insufficient to support the deployment or adjustment of the network slice bandwidth. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NETSLICING_NOT_SUPPORT_PROTOCOLNUM
|
Message text |
The board on slot [USHORT] does not support protocol number configuration. |
|
Variable fields |
$1: Slot number of the interface card. |
|
Severity level |
4 (Warning) |
|
Example |
NETSLICE/4/NETSLICING_NOT_SUPPORT_PROTOCOLNUM: The board on slot 3 does not support protocol number configuration. |
|
Impact |
The interface card cannot parse or process slice information in the HBH extension header. |
|
Cause |
The interface card does not support protocol number configuration. |
|
Recommended action |
Use an interface card that supports protocol number configuration. |
NP messages
This section contains NP messages.
LINK_FLAP_FREQ
|
Message text |
The link of [STRING] flaps frequently. Please check the hardware link! |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
PORT/4/LINK_FLAP_FREQ: The link of Ten-GigabitEthernet 5/0/1 flaps frequently. Please check the hardware link! |
|
Explanation |
The interface goes down and comes up frequently. |
|
Recommended action |
1. Verify that the physical link is normal. 2. Verify that the peer interface is operating correctly. 3. Reset the card where the peer interface resides. 4. If the issue persists, contact Technical Support. |
NPD
This section contains NPD messages.
ECC_ERROR
|
Message text |
ECC reset-level error occurred on slot [UINT32]. Error not corrected after three fast reset actions. |
|
Variable fields |
$1: Slot number of a card. |
|
Severity level |
2 (Critical) |
|
Example |
NPD/2/ECC_ERROR: -MDC=1-Slot=5; ECC reset-level error occurred on slot 5. Error not corrected after three fast reset actions. |
|
Impact |
A card error occurs, causing a large number of dropped packets and incorrect packets. |
|
Cause |
An ECC error occurred on the card chip and cannot be cleared. |
|
Recommended action |
Replace the card. |
NPS_ECC_ERROR
|
Message text |
ECC reset-level error occurred on slot [UINT32]. |
|
Variable fields |
$1: Slot number of a card. |
|
Severity level |
2 (Critical) |
|
Example |
NPD/2/NPS_ECC_ERROR: -MDC=1-Slot=5; ECC reset-level error occurred on slot 5. |
|
Impact |
A large number of dropped packets might occur on the card. |
|
Cause |
On the specified card, a reset-level error occurred. |
|
Recommended action |
1. Identify whether this message has been continuously reported. ¡ If yes, go to step 3. ¡ If not, go to step 2. 2. Identify whether the following message is generated: ECC reset-level error occurred on chassis [UINT32] slot [UINT32]. Error not corrected after three fast reset actions. ¡ If yes, go to step 3 ¡ If not, no action is required. 3. Replace the card. |
MACTX_FIFO_ERR
|
Message text |
MAC TX FIFO error detected on interface. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
NPD/3/MACTX_FIFO_ERR: MAC TX FIFO error detected on interface. |
|
Impact |
A large number of dropped packets occur on the card. |
|
Cause |
The MAC TX FIFO queue was congested on an interface, which cannot be resolved. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
MAC TX FIFO error detected on slot [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
3 (Error) |
|
Example |
NPD/3/MACTX_FIFO_ERR: -MDC=1-Slot=5; MAC TX FIFO error detected on slot 5. |
|
Impact |
A large number of dropped packets occur on the card. |
|
Cause |
The MAC TX FIFO queue was congested on the card, which cannot be resolved. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NPS_MONT
|
Message text |
TND is blocked, TM OQ is not valid, slot [UINT32], chip [UINT32], side [UINT32], TM OQ [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. $2: NP chip number. $3: NP chip part, 0 represents the left half of the chip, and 1 represents the right half of the chip. $4: Queue number of the TM OQ (queue of the data management module). |
|
Severity level |
3 (Error) |
|
Example |
NPD/3/NPS_MONT: TND is blocked, TM OQ is not valid, slot 3, chip 0, side 1, TM OQ 8. |
|
Impact |
The card cannot operate correctly. |
|
Cause |
An NP chip fault occurs on the card. |
|
Recommended action |
Restart or replace the card. |
|
Message text |
Eth TND is blocked detected on slot [UINT32] chip [UINT32] side [UINT32] IF Engine [UINT32] IF Number [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. $2: NP chip number. $3: NP chip part, 0 represents the left half of the chip, and 1 represents the right half of the chip. $4: Interface engine number. $5: Interface number. |
|
Severity level |
3 (Error) |
|
Example |
NPD/3/NPS_MONT: Eth TND is blocked detected on slot 3 chip 0 side1 IF Engine 1 IF Number 2. |
|
Impact |
The card cannot operate correctly. |
|
Cause |
An NP chip fault occurs on the card. |
|
Recommended action |
Restart or replace the card. |
|
Message text |
ILKN TND is blocked detected on slot [UINT32] chip [UINT32] side [UINT32] IF Engine [UINT32] IF Number [UINT32] Channel Number [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. $2: NP chip number. $3: NP chip part, 0 represents the left half of the chip, and 1 represents the right half of the chip. $4: Interface engine number. $5: Interface number. $6: ILKN channel number. |
|
Severity level |
3 (Error) |
|
Example |
NPD/3/NPS_MONT: ILKN TND is blocked detected on slot 3 chip 0 side1 IF Engine 1 IF Number 2 Channel Number 8. |
|
Impact |
The card cannot operate correctly. |
|
Cause |
An NP chip fault occurs on the card. |
|
Recommended action |
Restart or replace the card. |
NQA messages
SESSION_NOTSPT
|
Message text |
The board on slot [STRING] doesn't support NQA sessions. |
|
Variable fields |
$1: Slot number. |
|
Severity level |
4 (Warning) |
|
Example |
NQA/4/SESSION_NOTSPT: -MDC=1-Slot=3; The board on slot 2 doesn't support NQA sessions. |
|
Impact |
NQA operations cannot start. |
|
Cause |
The card does not support NQA sessions. |
|
Recommended action |
1. Use the display device command in system view to view the hardware type of the card. 2. Contact Technical Support to identify whether the card supports the NQA feature. |
REFLECTOR_NOTSPT
|
Message text |
The board on slot [STRING] doesn't support reflectors on the NQA server. |
|
Variable fields |
$1: Slot number. |
|
Severity level |
4 (Warning) |
|
Example |
NQA/4/REFLECTOR_NOTSPT: -MDC=1-Slot=3; The board on slot 3 doesn't support reflectors on the NQA server. |
|
Impact |
NQA reflector settings cannot be configured. |
|
Cause |
The card does not support NQA reflector settings configured by the nqa reflector command. |
|
Recommended action |
1. Use the display device command in system view to view the hardware type of the card. 2. Contact Technical Support to identify whether the card supports NQA reflector configuration. |
NQA
This section contains NQA messages.
NQA_BATCH_START_FAILURE
|
Message text |
Failed to batch start the [STRING] operation. Reason: [STRING] |
|
Variable fields |
$1: Type of the NQA operation. The value is Y.1564. $3: Failure reason: · Invalid configuration. · Not enough resources. |
|
Severity level |
6 (Informational) |
|
Example |
NQA/6/NQA_BATCH_START_FAILURE: Failed to batch start the Y.1564 operation. Reason: Invalid configuration. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when NQA failed to start the service performance test of the Y.1564 operation in batch due to invalid configuration or insufficient resources. |
|
Recommended action |
1. In Y.1564 operation view, execute the display this command to view the Y.1564 operation configuration. If the parameter settings do not meet the network requirements, edit the configuration and start the operation again. 2. In Y.1564 operation view, to avoid NQA operation startup failure, configure the source and destination addresses as follows: ¡ You must configure the source and destination addresses in the Layer 3 Ethernet and Layer 3 VPN environments. ¡ You must configure both the source and destination addresses or neither of them in other network environments. To configure the source and destination addresses, make sure they are both the IPv4 or IPv6 type. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NQA_LOG_UNREACHABLE
|
Message text |
Server [STRING] unreachable. |
|
Variable fields |
$1: IP address of the NQA server. |
|
Severity level |
6 (Informational) |
|
Example |
NQA/6/NQA_LOG_UNREACHABLE: Server 192.168.30.117 unreachable. |
|
Impact |
No negative impacts on the system. |
|
Cause |
An unreachable NQA server was detected. |
|
Recommended action |
1. Identify whether the IP address of the NQA server is correct based on the IP address in the message. If it is configured incorrectly, execute the destination command in NQA operation view to reconfigure the IP address of the NQA server. 2. Execute the display ip routing-table command to identify whether the device has routes to the NQA server. If the device has no routes to the NQA server, execute the ip route-static command to configure a static route, or configure a dynamic routing protocol to generate a route. 3. Execute the display interface command to view the state of the outbound interface to the NQA server. If the interface is in down state, resolve the interface failure. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
The NQA client attempted to send UDP probe packets with an IPv6 destination address and the data size exceeding 65503 bytes. The oversized probe packets will be dropped by the NQA server. |
|
Recommended action |
Use the data-size command to edit the payload size in bytes for each probe packet in NQA operation type view or NQA template view. |
NQA_REFLECTOR_START_FAILURE
|
Message text |
NQA reflector [UINT32]: Failed to start the NQA reflector. Please check the parameters. |
|
Variable fields |
$1: ID of a reflector. |
|
Severity level |
6 (Informational) |
|
Example |
NQAS/6/NQA_REFLECTOR_START_FAILURE: NQA reflector 1: Failed to start the NQA reflector, Please check the parameters. |
|
Impact |
No negative impact on the system. |
|
Cause |
Driver check failed. Required settings are missing. |
|
Recommended action |
The network configuration requirements for the driver vary by network environment. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NQA_REFRESH_FAILURE
|
Message text |
Failed to refresh the [STRING] operation. Reason: [STRING] |
|
Variable fields |
$1: Type of the NQA operation. The value is RFC2544. $3: Failure reason: · Invalid configuration. · Not enough resources. |
|
Severity level |
6 (Informational) |
|
Example |
NQA/6/NQA_REFRESH_FAILURE: Failed to refresh the RFC2544 operation. Reason: Invalid configuration. |
|
Impact |
No negative impact on the system. |
|
Cause |
For path quality analysis operations (RFC2544), the reasons for continuous operation startup failures include the following: · Reason 1: Parameter configuration error. · Reason 2: Insufficient resources. If the log message is displayed, the device clears results of the started path quality analysis operations and stops all path quality analysis operations. |
|
Recommended action |
1. For reason 1, take the following actions: ¡ Execute the display nqa rfc2544 group brief command to display brief information about path quality analysis operation groups. ¡ Execute the display nqa rfc2544 group name group-name command to display detailed information about the specified path quality analysis operation group. ¡ Enter NQA path quality analysis operation view, and execute the display this command to view the NQA path quality analysis operation group configuration. ¡ Each configuration must meet the device requirements. If the configuration does not meet the device requirements, edit the configuration. For configuration requirements of the NQA path quality analysis operation, see the NQA configuration guide. 2. For reason 2, execute the display current-configuration | include speed command to view the probe packet sending rate configuration for the NQA path quality analysis operation. If you start multiple path quality analysis operations continuously, make sure the maximum packet sending rate does not exceed 255 times the minimum packet sending rate. In the NQA operation view, execute the speed init and speed granularity commands to adjust the packet sending rate. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
NQA_REFRESH_START
|
Message text |
Start to refresh the [STRING] operation and reset the result. |
|
Variable fields |
$1: Type of the NQA operation. The value is RFC2544. |
|
Severity level |
6 (Informational) |
|
Example |
NQA/6/NQA_REFRESH_START: Start to refresh the RFC2544 operation and reset the result. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is sent when a new path quality analysis operation (RFC2544 operation) is started through the start command during an ongoing path quality analysis operation. The system clears the results of the ongoing path quality analysis operation and starts all path quality analysis operations. |
|
Recommended action |
No action is required. |
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 entry. $2: Operation tag of the NQA entry. $3: Port number. |
|
Severity level |
4 (Warning) |
|
Example |
NQA/4/NQA_SCHEDULE_FAILURE: NQA entry (admin-tag): Failed to start the scheduled NQA operation because port 10000 used by the operation is not available. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The port is occupied by other services. |
|
Recommended action |
1. By using the display tcp and display udp commands to view the information in the Local Addr:port field, you can see the IPv4 address and port number currently in use by this end; by using the display ipv6 tcp and display ipv6 udp commands to view the information in the LAddr->port field, you can see the IPv6 address and port number currently in use by this end. 2. Executing the source port command to modify the source port of the NQA test to the currently available port number. |
NQA_SEVER_FAILURE
|
Message text |
Failed to enable the NQA server because listening port [ STRING ] is not available. |
|
Variable fields |
$1: Port number. |
|
Severity level |
4 (Warning) |
|
Example |
NQA/4/NQA_SEVER_FAILURE: Failed to enable the NQA server because listening port 10000 is not available. |
|
Impact |
No negative impacts on the system. |
|
Cause |
Due to the port being occupied by other services, the NQA server function failed to open |
|
Recommended action |
1. By using the display tcp and display udp commands to display the Local Addr:port field in the information, you can view the IPv4 address and port number being used by this end. By using the display ipv6 tcp and display ipv6 udp commands to display the LAddr->port field in the information, you can view the IPv6 address and port number being used by this end 2. Execute the display current-configuration | include nqa command to view the current NQA configuration. When the device is acting as an NQA server, you can configure the nqa server tcp-connect, nqa server udp-echo, and nqa reflector commands. If the port number parameter in these commands is currently in use by the device, replace the port number parameter with an unused port number, and then reconfigure the nqa server tcp-connect, nqa server udp-echo, and nqa reflector commands. |
NQA_START_FAILURE
|
Message text |
NQA entry ([STRING]-[STRING]): [STRING] |
|
Variable fields |
$1: Admin name of the NQA entry. $2: Operation tag of the NQA entry. $3: Failure reason: · Operation failed due to configuration conflicts. · Operation failed because the driver was not ready to perform the operation. · Operation not supported. · Not enough resources to complete the operation. · Operation failed due to an unknown error. |
|
Severity level |
6 (Informational) |
|
Example |
NQA/6/NQA_START_FAILURE: NQA entry (admin-test): Operation failed due to configuration conflicts. |
|
Impact |
No negative impacts on the system. |
|
Cause |
· The operation failed due to configuration conflicts. · The operation failed because the driver was not ready to perform the operation. · The operation is not supported by the driver. · The operation failed due to resource insufficiency. · The operation failed due to an unknown error. |
|
Recommended action |
· If the NQA operation failed due to configuration conflicts, execute the display this command in NQA operation view to view the configuration of the NQA operation. Configure the NQA operation according to the NQA configuration guide and restart the operation. · If the NQA operation failed for other reasons, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
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. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The statistics collection interval for the TWAMP Light test was shorter than the packet sending interval. Results of the test will not be included in statistics. |
|
Recommended action |
1. Execute the stop command in TWAMP Light sender view to stop the test. 2. Execute the start command in TWAMP Light sender view to start the test, and make sure the following conditions are met: ¡ The packet monitoring time is greater than the statistics collection interval. ¡ The statistics collection interval is greater 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: ID of the NQA reaction entry. $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 (Informational) |
|
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. |
|
Impact |
No negative impacts on the system. |
|
Cause |
In a TWAMP Light 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_SENDER_START_FAILURE
|
Message text |
NQA TWAMP Light sender test session [UINT32]: Failed to start the test session. Reason: [TEXT]. |
|
Variable fields |
$1: Test session ID. $2: Failure cause: Test tx-interval is mutually exclusive with the timestamp format of NTP. |
|
Severity level |
6 (Informational) |
|
Example |
NQA/6/NQA_TWAMP_LIGHT_SENDER_START_FAILURE: NQA TWAMP Light sender test session 1:Failed to start the test session.Reason: Test tx-interval is mutually exclusive with the timestamp-format of NTP. |
|
Impact |
No negative impacts on the system. |
|
Cause |
When the timestamp type on the TWAMP-light sender is configured as NTP, and the inter-packet gap configuration of the test packet is set to 10ms or 100ms, a configuration conflict occurs, and the TWAMP_LIGHT test fails to start |
|
Recommended action |
Please use the start command to modify the inter-packet gap on the TWAMP-light sender, or use the timestamp-format command to modify the timestamp format |
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 (Informational) |
|
Example |
NQAS/6/NQA_TWAMP_LIGHT_START_FAILURE: NQA TWAMP Light test session 1: Failed to start the test session, Please check the parameters. |
|
Impact |
No negative impacts on the system. |
|
Cause |
Driver check failed. Required settings are missing. |
|
Recommended action |
The network configuration requirements for the driver vary by network environment. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NTP
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 (Notification) |
|
Example |
NTP/5/NTP_CLOCK_CHANGE: System clock changed from 02:12:58:345 12/28/2012 to 02:29:12:879 12/28/2012, the NTP server's IP address is 192.168.30.116. |
|
Impact |
No negative impacts on the system. |
|
Cause |
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 system Leap Indicator. Options include the following: · 01: Indicates that the last minute of the day has 61 seconds. · 10: Indicates that the last minute of the day has 59 seconds. $2: Current system Leap Indicator. Options include the following: · 01: Indicates that the last minute of the day has 61 seconds. · 10: Indicates that the last minute of the day has 59 seconds. |
|
Severity level |
5 (Notification) |
|
Example |
NTP/5/NTP_LEAP_CHANGE: System Leap Indicator changed from 00 to 01 after clock update. |
|
Impact |
The device will adjust the time by leaping one second during the last minute of the day on which this log is generated. |
|
Cause |
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 (rollover interval) in the day of insertion to be increased or decreased by one. |
|
Recommended action |
Determine if a leap second adjustment is necessary today for printing this log, based on the deviation values of TAI and UTC time published regularly by the International Bureau of Weights and Measures (BIPM): If a leap second adjustment is needed and its value is correct, then no action is required. If a leap second adjustment is not needed, then wait for the next time synchronization. If after the next synchronization, the device's system time matches the international standard time, then no action is required. If after the next synchronization, the device's system time does not match the international standard time, continue to check if the time source has also undergone a leap second adjustment. If the time source has an incorrect leap second adjustment, recalibrate the time of the time source. |
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 (Notification) |
|
Example |
NTP/5/NTP_SOURCE_CHANGE: NTP server's IP address changed from 1.1.1.1 to 1.1.1.2. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The system changed the time source. |
|
Recommended action |
Generally, no action is required. You can also further identify the cause of the clock source switch, for example: · Ping the IP address of the original clock source to see if the original clock source is route reachable. If the route is not reachable, resolve the routing issue first. · Log in to the original clock source and check if the clock on the original clock source is accurate. If it is not accurate, adjust the time on the original clock source. · Log in to the original clock source and check if the NTP configuration on the original clock source is correct. If it is not correct, modify it according to the NTP configuration manual. |
NTP_SOURCE_LOST
|
Message text |
Lost synchronization with NTP server with IP address [STRING]. |
|
Variable fields |
$1: IP address. |
|
Severity level |
4 (Warning) |
|
Example |
NTP/4/NTP_SOURCE_LOST: Lost synchronization with NTP server with IP address 1.1.1.1. |
|
Impact |
The accuracy of the device's clock might be affected. |
|
Cause |
During NTP interactions, if the clock source is unsynchronized or unreachable, and there are no other candidate sources for synchronization, the device generates this log. |
|
Recommended action |
1. Ping the IP address of the original clock source to see if the original clock source is route reachable. If the route is not reachable, resolve the routing issue first. 2. Log in to the original clock source and identify whether the clock on the original clock source is accurate. If it is not accurate, adjust the time on the original clock source. 3. Log in to the original clock source and identify whether the NTP configuration on the original clock source is correct. If it is not correct, modify it according to the NTP configuration manual. 4. Execute the corresponding command to configure a new clock source based on the clock synchronization mode. |
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 (Notification) |
|
Example |
NTP/5/NTP_STRATUM_CHANGE: System stratum changed from 6 to 5 after clock update. |
|
Impact |
Clock synchronization between the device and downstream devices might be affected. |
|
Cause |
Causes for changes in the device's clock stratum might include: · Changes in the hierarchy of the clock source itself, such as when the system initially selects a clock source. · Switching of synchronization clock sources during the synchronization process, with changes in the clock source leading to changes in the clock hierarchy. In actual networks, NTP servers that obtain time synchronization from authoritative clocks (such as atomic clocks) typically have their stratums set to 1 and are used as the primary time servers to synchronize the clocks of other devices in the network. The NTP distance between devices in the network and the primary time server, which is the number of NTP servers in the NTP synchronization chain, determines the stratum of the clock on the device. For example, in a network topology like: Atomic Clock -> Device A -> Device B -> Device C, the clock stratum of Device A would be 1, the clock stratum of Device B would be 2, and the clock stratum of Device C would be 3. |
|
Recommended action |
1. Identify whether the clock source has changed. Execute the display ntp-service status command to check the value of the Reference clock ID field (which represents the clock source address): ¡ If the value of the Reference clock ID field is consistent with the main clock source address in the network plan, proceed to step 2. If the value of the Reference clock ID field is not consistent with the main clock source address in the network plan, this indicates a clock source switch has occurred. The switch in the clock source leads to changes in clock stratums, no action is required. ¡ If the value of Reference clock ID is none, it indicates the loss of the clock source. Replace the clock source or repair the faulty one. 2. Identify whether the change in the clock stratums of this device is caused by the change in the hierarchy of the clock source itself. Log in to the clock source and check its clock stratums. If the clock stratums of the clock source are inconsistent with the network plan, modify the clock stratums of the clock source (if the clock source is an H3C device, execute the display ntp-service sessions command to see the value of the stra field, which represents the clock stratums of the clock source. Under system view, execute the ntp-service refclock-master command to change the clock hierarchy of the clock source). 3. Identify whether the change in the clock stratums of this device is caused by the change in the hierarchy of the clock source itself. Execute the display ntp-service sessions command on the device, where the value of the stra field indicates the clock stratums of the clock source. If the clock stratums of the clock source are inconsistent with the network plan, log in to the clock source and modify its clock stratums (if the clock source is an H3C device, the clock stratums can be modified by executing ntp-service refclock-master command in system view). |
OAM
This section contains OAM messages.
OAM_SLOT_MAC_CONFLICT
|
Message text |
Slot [INT32] (MAC: [STRING]) in forwarding state conflicts with slot [INT32]% (MAC: [STRING]) |
|
Variable fields |
$1: Slot number of the VM where a slot conflict was detected. $2: The first VMC interface MAC of the VM detected with a slot conflict. $3: Slot number of the VM that has a slot conflict with the detected VM. $4: The first VMC interface MAC of the VM that has a slot conflict with the detected VM. |
|
Severity level |
4 (Warning) |
|
Example |
OAM/4/OAM_SLOT_MAC_CONFLICT: Slot 1(MAC: 00:16:EA:AE:3C:40) in forwarding state conflicts with slot 1(MAC: 00:16:EA:AE:3C:41) |
|
Impact |
The VM where a slot number conflict was detected cannot process services correctly. |
|
Cause |
When a VM experiences an anomaly and fails, the system creates a new VM to replace it. If the faulty VM restores, it initiates a check upon restoration. This message is generated if it detects a slot number and interface MAC conflict between the new VM and itself. |
|
Recommended actions |
Shut down one VM to ensure uniqueness of the VM slot number within the same multicast domain while ensuring that services are running correctly. |
OAM_SLOT_CONFLICT
|
Message text |
Slot [INT32] entered silent state because its UUID([STRING]) is different from UUID ([STRING]) in the conflict detection packet. |
|
Variable fields |
$1: Slot number of the VM. $2: VM's UUID. $3: UUID carried in the conflict detection packet. |
|
Severity level |
4 (Warning) |
|
Example |
OAM/4/OAM_SLOT_CONFLICT: Slot 10 entered silent state because its UUID(00000000-0000-0000-0054-AABBCCDDEEFF) is different from UUID(00000000-0000-0000-0054-AABBCCDDEEEE) in the conflict detection packet. |
|
Impact |
The VM enters silent state and can only receive packets. |
|
Cause |
CTRL-VM periodically sends conflict detection packets that carry valid VM UUID information. If a VM receives a conflict detection packet that carries a UUID different than its UUID from the same slot number, the VM enters silent state and can only receive packets. |
|
Recommended actions |
No action is required. |
OAM_SLOT_RECOVER
|
Message text |
Slot [INT32] entered forwarding state because its UUID([STRING]) is the same as the one in the conflict detection packet. |
|
Variable fields |
$1: Slot number of the VM. $2: VM's UUID. |
|
Severity level |
5 (Notification) |
|
Example |
OAM/5/OAM_SLOT_RECOVER: Slot 10 entered forwarding state because its UUID(00000000-0000-0000-0054-AABBCCDDEEFF) is the same as the one in the conflict detection packet. |
|
Impact |
No negative impact on the system. |
|
Cause |
A VM in silent state receives a conflict detection packet that carries a UUID the same as its own from the same slot number. The VM enters forwarding state and starts receiving and transmitting packets. |
|
Recommended actions |
No action is required. |
NOTIFY
|
Message text |
The status of the interface with mac address [STRING] has changed from [STRING] to [STRING] |
|
Variable fields |
$1: MAC address of an interface within a VM. $2: Health of the link within the VM. ¡ Normal: The link is normal. ¡ Minor: The link is abnormal. ¡ Major: The link quality is poor. $3: Health of the link within the VM. ¡ Normal: The link is normal. ¡ Minor: The link is abnormal. ¡ Major: The link quality is poor. |
|
Severity level |
4 (Warning) |
|
Example |
OAM/4/NOTIFY: -Slot=2; The status of the interface with mac address fa16-3ef2-fa79 has changed from Minor to Major |
|
Impact |
Communication within the CM might experience packet loss if the link quality becomes poor. |
|
Cause |
OAM detected that the state of a link within a VM changed. |
|
Recommended actions |
Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OFP messages
This section contains OpenFlow messages.
OFC_DATAPATH_CHANNEL_CONNECT
|
Message text |
OpenFlow Controller datapath [STRING], channel with IP address [STRING] connected |
|
Variable fields |
$1: Datapath ID of the OpenFlow instance. $2: IP address of the OpenFlow switch connected to the controller. |
|
Severity level |
5 (Notification) |
|
Example |
OFC/5/OFC_DATAPATH_CHANNEL_CONNECT: OpenFlow Controller datapath 0x174258ae43182, channel with IP address 169.28.25.123 connected |
|
Impact |
N/A |
|
Cause |
The controller established a new connection. |
|
Recommended action |
No action is required. |
OFC_DATAPATH_CHANNEL_DISCONNECT
|
Message text |
OpenFlow Controller datapath [STRING], channel with IP address [STRING] disconnected.disconnected reason:[STRING]. |
|
Variable fields |
$1: Datapath ID of the OpenFlow instance. $2: IP address of the OpenFlow switch connected to the controller. $3: Disconnection reason. Possible values are: · Connection became abnormal · A SSL connection became abnormal · BFD timed out · Version negotiation failed · Protocol disable · Connection became abnormal when Sending message · Connection recover failed · Received invalid packets or incorrectly processed received packets · Connection became abnormal when receiving message · VPN instance deleted · A SSL connection became abnormal · Heartbeat packets sending failed · Heartbeat packets timed out · Configuration changed · Not enough memory · Connection became abnormal |
|
Severity level |
5 (Notification) |
|
Example |
OFC/5/OFC_DATAPATH_CHANNEL_DISCONNECT: OpenFlow Controller datapath 0x13c3164380100, channel with IP address 30.0.0.1 disconnected.disconnected reason:Connection became abnormal when receiving message. |
|
Impact |
N/A |
|
Cause |
The connection between the controller and the OpenFlow switch was disconnected. See the disconnected reason field for the reason. |
|
Recommended action |
As a best practice, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
OFC_FLOW_ADD
|
Message text |
App [CHAR] added flow entry: [STRING]. |
|
Variable fields |
$1: App ID. $2: Flow entry content. The match field specifies the match fields. The action field specifies the action set. |
|
Severity level |
5 (Notification) |
|
Example |
OFC/5/OFC_FLOW_ADD: App 1 added flow entry: match(context 0x12a56, ipaddr 1.1.1.1, vxlan id 1), action(set svlan 2, set cvlan 3, modify destination mac 0-0-5, output 11). |
|
Impact |
N/A |
|
Cause |
An app on the controller deployed information for adding flow entries to the OpenFlow switch. |
|
Recommended action |
No action is required. |
OFC_FLOW_DEL
|
Message text |
App [CHAR] deleted flow entry: [STRING]. |
|
Variable fields |
$1: App ID. $2: Flow entry content. The match field specifies the match fields. The action field specifies the action set. |
|
Severity level |
5 (Notification) |
|
Example |
OFC/5/OFC_FLOW_DEL: App 1 deleted flow entry: match(context 0x12a56, ipaddr 1.1.1.1, vxlan id 1), action(set svlan 2, set cvlan 3, modify destination mac 0-0-5, output 11). |
|
Impact |
N/A |
|
Cause |
An app on the controller deployed information for deleting flow entries to the OpenFlow switch. |
|
Recommended action |
No action is required. |
OFC_FLOW_MOD
|
Message text |
App [CHAR] modified flow entry: [STRING]. |
|
Variable fields |
$1: App ID. $2: Flow entry content. The match field specifies the match fields. The action field specifies the action set. |
|
Severity level |
5 (Notification) |
|
Example |
OFC/5/OFC_FLOW_MOD: App 1 modified flow entry: match(context 0x12a56, ipaddr 1.1.1.1, vxlan id 1), action(set svlan 2, set cvlan 3, modify destination mac 0-0-5, output 11). |
|
Impact |
N/A |
|
Cause |
An app on the controller deployed information for modifying flow entries to the OpenFlow switch. |
|
Recommended action |
No action is required. |
OFP_ACTIVE
|
Message text |
Activate openflow instance [UINT16] |
|
Variable fields |
$1: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_ACTIVE: Activate openflow instance 1. |
|
Impact |
N/A |
|
Cause |
A command is received 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 (Warning) |
|
Example |
OFP/4/OFP_ACTIVE_FAILED: Failed to activate instance 1. |
|
Impact |
The OpenFlow instance cannot be used. |
|
Cause |
An OpenFlow instance failed to be activated. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
OFP_ACTIVE_MAC_LEARN_FORBIDDEN_F
|
Message text |
Failed to execute the mac-learning forbidden command when activating instance [UINT16] |
|
Variable fields |
$1: Instance ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_ACTIVE_MAC_LEARN_FORBIDDEN_F: Failed to execute the mac-learning forbidden command when activating instance 1. |
|
Impact |
The feature of disabling MAC address learning is not available. |
|
Cause |
The device hardware does not support this feature. At the same time, configurations that fail to be issued will be automatically deleted. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
OFP_CONNECT
|
Message text |
OpenFlow instance [UINT16] connected to controller [STRING]. |
|
Variable fields |
$1: Instance ID. $2: Controller ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_CONNECT: OpenFlow instance 1 connected to controller 63. |
|
Impact |
N/A |
|
Cause |
An OpenFlow instance was connected to a controller. |
|
Recommended action |
No action is required. |
OFP_DISCONNECT
|
Message text |
OpenFlow instance [UINT16] disconnected from controller [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Instance ID. $2: Controller ID. $3: Disconnection reason. Possible values are: · Connection became abnormal · Configuration changed · Heartbeat packets timed out · Version negotiation failed · Hello packets timed out · Receiving message failed · A SSL connection became abnormal · VPN instance deleted · VRF service disabled · Resource request failed · APP down · BFD timed out · Not enough memory · Connection became abnormal |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_DISCONNECT: OpenFlow instance 1 disconnected from controller 63. Reason: A TCP connection became abnormal. |
|
Impact |
N/A |
|
Cause |
An OpenFlow instance was disconnected from a controller. For the disconnection reason, see the Reason field. |
|
Recommended action |
As a best practice, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
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 (Notification) |
|
Example |
OFP/5/OFP_FAIL_OPEN: Openflow instance 1 is in fail secure mode. |
|
Impact |
N/A |
|
Cause |
An activated instance cannot connect to any controller or is disconnected from all controllers. |
|
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: Flow entry cookie. $6: Flow table ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_FLOW_ADD: Openflow instance 1 controller 0: add flow entry 1, xid 0x1, cookie 0x0, table id 0. |
|
Impact |
N/A |
|
Cause |
A flow entry is to be added to a flow table according to a flow table modification message that has passed the packet check. |
|
Recommended action |
No action is required. |
OFP_FLOW_ADD_DUP
|
Message text |
Openflow instance [UINT16] controller [CHAR]: add duplicate flow entry [UINT32], xid 0x[HEX], cookie 0x[HEX], table id [CHAR]. |
|
Variable fields |
$1: Instance ID. $2: Controller ID. $3: Rule ID. $4: XID. $5: Cookie. $6: Flow table ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_FLOW_ADD_DUP: Openflow instance 1 controller 0: add duplicate flow entry 1, xid 0x1, cookie 0x1, table id 0. |
|
Impact |
N/A |
|
Cause |
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]. |
|
Variable fields |
$1: Instance ID. $2: Controller ID. $3: Rule ID. $4: Flow table ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_FLOW_ADD_FAILED: Openflow instance 1 controller 0: failed to add flow entry 1, table id 0. |
|
Impact |
The traffic forwarding function of the flow entry is unavailable. |
|
Cause |
A flow entry failed to be added. |
|
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: Flow entry cookie. $5: Flow table ID. |
|
Severity level |
5 (Notification) |
|
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. |
|
Impact |
N/A |
|
Cause |
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: Flow table ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_FLOW_ADD_TABLE_MISS_FAILED: Openflow instance 1 controller 0: failed to add table miss flow entry, table id 0. |
|
Impact |
This table-miss flow entry is unavailable. |
|
Cause |
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: Flow entry cookie. $5: Flow table ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_FLOW_DEL: Openflow instance 1 controller 0: delete flow entry, xid 0x1, cookie 0x0, table id 0. |
|
Impact |
N/A |
|
Cause |
A list of flow entries were 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: Flow entry cookie. $5: Flow table ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP_FLOW_DEL_TABLE_MISS Openflow instance 1 controller 0: delete table miss flow entry, xid 0x1, cookie 0x0, table id 0. |
|
Impact |
N/A |
|
Cause |
A list of table-misses flow entries were 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: Flow table ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_FLOW_DEL_TABLE_MISS_FAILED: Openflow instance 1 controller 0: failed to delete table miss flow entry, table id 0. |
|
Impact |
The old table-miss flow entry still takes effect. |
|
Cause |
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: Flow entry cookie. $5: Flow table ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_FLOW_MOD: Openflow instance 1 controller 0: modify flow entry, xid 0x1, cookie 0x0, table id 0. |
|
Impact |
N/A |
|
Cause |
A list of flow entries were 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: Flow table ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_FLOW_MOD_FAILED: Openflow instance 1 controller 0: failed to Modify flow entry, table id 0. |
|
Impact |
The old flow entries still take effect. |
|
Cause |
Failed to modify flow entries. |
|
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: Flow entry cookie. $5: Flow table ID. |
|
Severity level |
5 (Notification) |
|
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. |
|
Impact |
N/A |
|
Cause |
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: Flow table ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_FLOW_MOD_TABLE_MISS_FAILED: Openflow instance 1 controller 0: failed to modify table miss flow entry, table id 0. |
|
Impact |
The old table-miss flow entry still takes effect. |
|
Cause |
Failed to modify the table-miss flow entries. |
|
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: Flow table ID. $3: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_FLOW_RMV_GROUP: The flow entry 1 in table 0 of instance 1 was deleted with a group_mod message. |
|
Impact |
N/A |
|
Cause |
A flow entry was deleted. |
|
Recommended action |
No action is required. |
OFP_FLOW_RMV_HARDTIME
|
Message text |
The flow entry [UINT32] in table [CHAR] of instance [UINT16] was deleted because of a hard-time expiration. |
|
Variable fields |
$1: Rule ID. $2: Flow table ID. $3: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_FLOW_RMV_HARDTIME: The flow entry 1 in table 0 of instance 1 was deleted because of a hard-time expiration. |
|
Impact |
N/A |
|
Cause |
A flow entry was deleted because of a hard time expiration. |
|
Recommended action |
No action is required. |
OFP_FLOW_RMV_IDLETIME
|
Message text |
The flow entry [UINT32] in table [CHAR] of instance [UINT16] was deleted because of an idle-time expiration. |
|
Variable fields |
$1: Rule ID. $2: Flow table ID. $3: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_FLOW_RMV_IDLETIME: The flow entry 1 in table 0 of instance 1 was deleted because of an idle-time expiration. |
|
Impact |
N/A |
|
Cause |
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: Flow table ID. $3: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_FLOW_RMV_GROUP: The flow entry 1 in table 0 of instance1 was deleted with a meter_mod message. |
|
Impact |
N/A |
|
Cause |
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: Flow table ID. $3: Flow entry ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_FLOW_UPDATE_FAILED: OpenFlow instance 1 table 0: failed to update or synchronize flow entry 10000. |
|
Impact |
The updated or synchronized flow entry is lost. |
|
Cause |
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 entry ID. $4: XID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/ OFP_GROUP_ADD: Openflow instance 1 controller 0: add group 1, xid 0x1. |
|
Impact |
N/A |
|
Cause |
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 entry ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_GROUP_ADD_FAILED: Openflow Instance 1 controller 0: failed to add group 1. |
|
Impact |
The traffic forwarding function of the flow entry is unavailable. |
|
Cause |
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 entry ID. $4: XID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_GROUP_DEL: Openflow instance 1 controller 0: delete group 1, xid 0x1. |
|
Impact |
N/A |
|
Cause |
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 entry ID. $4: XID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_GROUP_MOD: Openflow instance 1 controller 0: modify group 1, xid 0x1. |
|
Impact |
N/A |
|
Cause |
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 entry ID. |
|
Severity level |
4 (Warning) |
|
Example |
OFP/4/OFP_GROUP_MOD_FAILED: Openflow instance 1 controller 0: failed to modify group 1. |
|
Impact |
The old group entry still takes effect. |
|
Cause |
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 (Notification) |
|
Example |
OFP/5/OFP_METER_ADD: Openflow instance 1 controller 0: add meter 1, xid 0x1. |
|
Impact |
N/A |
|
Cause |
A meter entry is to be added to a meter table, according to a meter table modification message that has passed the packet check. |
|
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 (Warning) |
|
Example |
OFP/4/OFP_METER_ADD_FAILED: Openflow Instance 1 controller 0: failed to add meter 1. |
|
Impact |
N/A |
|
Cause |
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 (Notification) |
|
Example |
OFP/5/OFP_METER_DEL: Openflow instance 1 controller 0: delete meter 1, xid 0x1. |
|
Impact |
N/A |
|
Cause |
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 (Notification) |
|
Example |
OFP/5/OFP_METER_MOD: Openflow Instance 1 controller 0: modify meter 1, xid 0x1. |
|
Impact |
N/A |
|
Cause |
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 (Warning) |
|
Example |
OFP/4/OFP_METER_MOD_FAILED: Openflow instance 1 controller 0: failed to modify meter 1. |
|
Impact |
The old flow entries still take effect. |
|
Cause |
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: Flow table ID. $2: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_MISS_RMV_GROUP: The table-miss flow entry in table 0 of instance 1 was deleted with a group_mod message. |
|
Impact |
N/A |
|
Cause |
The table-miss flow entry was deleted due to a group modification message. |
|
Recommended action |
No action is required. |
OFP_MISS_RMV_HARDTIME
|
Message text |
The table-miss flow entry in table [CHAR] of instance [UINT16] was deleted because of a hard-time expiration. |
|
Variable fields |
$1: Flow table ID. $2: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_MISS_RMV_HARDTIME: The table-miss flow entry in table 0 of instance 1 was deleted because of a hard-time expiration. |
|
Impact |
N/A |
|
Cause |
The table-miss flow entry was deleted because of a hard time expiration. |
|
Recommended action |
No action is required. |
OFP_MISS_RMV_IDLETIME
|
Message text |
The table-miss flow entry in table [CHAR] of instance [UINT16] was deleted because of an idle-time expiration. |
|
Variable fields |
$1: Flow table ID. $2: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_MISS_RMV_IDLETIME: The table-miss flow entry in table 0 of instance 1 was deleted because of an idle-time expiration. |
|
Impact |
N/A |
|
Cause |
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: Flow table ID. $2: Instance ID. |
|
Severity level |
5 (Notification) |
|
Example |
OFP/5/OFP_MISS_RMV_METER: The table-miss flow entry in table 0 of instance 1 was deleted with a meter_mod message. |
|
Impact |
N/A |
|
Cause |
The table-miss flow entry was deleted due to a meter modification message. |
|
Recommended action |
No action is required. |
OPTMOD
This section contains OPTMOD messages.
BIAS_HIGH
|
Message text |
[STRING]: Bias current is high. |
|
Variable fields |
$1: Port name. |
|
Severity level |
2 (Critical) |
|
Example |
OPTMOD/2/BIAS_HIGH: GigabitEthernet1/0/1: Bias current is high. |
|
Impact |
The transceiver module cannot run correctly. |
|
Cause |
When the bias current of the optical transceiver module exceeds the high bias current alarm threshold, this log is generated |
|
Recommended action |
1. Use the 'display transceive diagnosis interface' command to Verify whether the current bias current value has exceeded the high bias current alarm threshold 2. Use the 'display transceive alarm interface' command multiple times to confirm the presence of high bias current alarm 3. If there is indeed a high bias current alarm, it indicates an issue with the optical transceiver module. Please replace the transceiver module. |
BIAS_LOW
|
Message text |
[STRING]: Bias current is low. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/BIAS_LOW: GigabitEthernet1/0/1: Bias current is low. |
|
Impact |
The transceiver module cannot run correctly. |
|
Cause |
When the bias current of the optical transceiver module is lower than the bias current low alarm threshold, this log is generated |
|
Recommended action |
1. Verify if the port status is shutdown. If the status is shutdown, recover the port status to up 2. Use the display transceiver diagnosis interface command to Verify whether the current bias current value has exceeded the bias current low alarm threshold 3. Use the display transceiver alarm interface command to check multiple times if there is indeed a bias current low alarm 4. If it is lower than the bias current low alarm threshold, there may be a fault with the optical transceiver module or the board. Collect the configuration file, log file, and alarms, and then contact Technical Support. |
BIAS_NORMAL
|
Message text |
[STRING]: Bias current is normal. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/BIAS_NORMAL: GigabitEthernet1/0/1: Bias current is normal. |
|
Impact |
No negative impacts on the system. |
|
Cause |
This log is generated when the bias current of the optical transceiver module is restored to normal range. |
|
Recommended action |
No action is required. |
CFG_ERR
|
Message text |
[STRING]: Transceiver type and port configuration mismatched. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/CFG_ERR: GigabitEthernet1/0/1: Transceiver type and port configuration mismatched. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When the optical transceiver module type does not match the port configuration, this log is generated |
|
Recommended action |
1. Verify whether the optical transceiver module can work properly. If it can, no action is required. 2. If the transceiver module cannot run correctly, collect the configuration file, log file, and alarms, and then contact Technical Support. |
CHKSUM_ERR
|
Message text |
[STRING]: Transceiver information checksum error. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/CHKSUM_ERR: GigabitEthernet1/0/1: Transceiver information checksum error. |
|
Impact |
No negative impacts on the system. |
|
Cause |
When the optical transceiver module register information verification fails, this log is generated |
|
Recommended action |
1. Verify whether the optical transceiver module can work normally, if yes, no action is required. 2. If the optical transceiver module cannot work normally, please re-plug the optical transceiver module 3. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical 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: Port name. $2: Optical Transceiver Module Failure Days |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
The transceiver module cannot run correctly. |
|
Cause |
This log is generated when the optical transceiver module does not match the interface card |
|
Recommended action |
Replace the transceiver module. |
FIBER_SFPMODULE_NOWINVALID
|
Message text |
[STRING]: This is not a supported transceiver for this platform. HP does not guarantee the normal operation or maintenance of unsupported transceivers. Please review the platform datasheet on the HP web site or contact your HP sales rep for a list of supported transceivers. |
|
Variable fields |
$1: Port name. |
|
Severity level |
4 (Warning) |
|
Example |
OPTMOD/4/FIBER_SFPMODULE_NOWINVALID: GigabitEthernet1/0/1: This is not a supported transceiver for this platform. HP does not guarantee the normal operation or maintenance of unsupported transceivers. Please review the platform datasheet on the HP web site or contact your HP sales rep for a list of supported transceivers. |
|
Impact |
Unsupportable optical transceiver modules may not work properly on the device |
|
Cause |
When the optical transceiver module is not supported, this log is generated |
|
Recommended action |
Please refer to the platform data on the HP website or contact your HP sales representative for a list of supported optical transceiver modules, Replace the transceiver module. |
IO_ERR
|
Message text |
[STRING]: The transceiver information I/O failed. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/IO_ERR: GigabitEthernet1/0/1: The transceiver information I/O failed. |
|
Impact |
The transceiver module cannot run correctly. |
|
Cause |
When the device fails to read the optical transceiver module register, this log is generated |
|
Recommended action |
1. Verify whether the port is working properly. If the port is not working properly, Verify and resolve the port issue first 2. If the same fault occurs multiple times with other optical modules on the single board, it indicates a component failure on the board. Collect the configuration file, log file, and alarms, and then contact Technical Support. 3. Execute the 'display transceiver diagnosis interface' or 'display transceiver alarm interface' command. If both commands fail, it indicates a fault with the transceiver module. Please replace the transceiver module. |
MOD_ALM_OFF
|
Message text |
[STRING]: [STRING] was removed. |
|
Variable fields |
$1: Port name. $2: Fault type. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/MOD_ALM_OFF: GigabitEthernet1/0/1: Module_not_ready was removed. |
|
Impact |
No negative impacts on the system. |
|
Cause |
This log is generated when the optical transceiver module fault is cleared. |
|
Recommended action |
No action is required. |
MOD_ALM_ON
|
Message text |
[STRING]: [STRING] was detected. |
|
Variable fields |
$1: Port name. $2: Fault type. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/MOD_ALM_ON: GigabitEthernet1/0/1: Module_not_ready was detected. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When a fault is detected in the optical transceiver module, this log is generated |
|
Recommended action |
According to different types of faults, the cause of the fault may be the problem with the optical transceiver module itself, or it may be a port or link problem, collect the configuration file, log file, and alarms, and then contact Technical Support. |
MODULE_IN
|
Message text |
[STRING]: The transceiver is [STRING]. |
|
Variable fields |
$1: Port name. $2: Transceiver module type. |
|
Severity level |
4 (Warning) |
|
Example |
OPTMOD/4/MODULE_IN: GigabitEthernet1/0/1: The transceiver is 1000_BASE_T_AN_SFP. |
|
Impact |
No negative impacts on the system. |
|
Cause |
When an optical transceiver module is inserted into a port, this log is generated. |
|
Recommended action |
No action is required. |
MODULE_OUT
|
Message text |
[STRING]: Transceiver absent. |
|
Variable fields |
$1: Port name. |
|
Severity level |
4 (Warning) |
|
Example |
OPTMOD/4/MODULE_OUT: GigabitEthernet1/0/1: Transceiver absent. |
|
Impact |
The transceiver module is not available. |
|
Cause |
This log is generated when the transceiver module is 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 information. $4: Error code. $5: Error reason. |
|
Severity level |
4 (Warning) |
|
Example |
OPTMOD/4/OPTICAL_WARNING_CLEAR: Transceiver warning alarm cleared. (PhysicalIndex=8833, PhysicalName=GE1/0/1, RelativeResource=1/0/1, ErrorCode=600060, Reason=Transceiver RXCDR_unlock detected. Lane = 1.) |
|
Impact |
No negative impact on the system. |
|
Cause |
The transceiver module alarm is 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 information. $4: Error code. $5: Error reason. |
|
Severity level |
4 (Warning) |
|
Example |
OPTMOD/4/OPTICAL_WARNING_OCCUR: Transceiver warning alarm occurred. (PhysicalIndex=8833, PhysicalName=GE1/0/1, RelativeResource=1/0/1, ErrorCode=600060, Reason=Transceiver RXCDR_unlock detected. Lane = 1.) |
|
Impact |
The transceiver module cannot operate correctly. |
|
Cause |
The transceiver module alarm is generated. |
|
Recommended action |
1. Verify that the transceiver module and fibers are connected correctly. 2. Remove the transceiver module and insert it again. 3. Verify that all interface modules installed on the device are operating correctly. 4. Take corresponding measures based on the FaultID. 5. If the issue persists, collect the device configuration file, log information, and alarm information, and contact 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: Interface Module Model $3: Serial number of the transceiver module. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When counterfeit, pirate, or unauthorized H3C optical transceiver modules are detected on the device, this log is generated. For counterfeit, pirate, or unauthorized H3C optical transceiver modules, data cannot be obtained through the display transceiver diagnosis command. |
|
Recommended action |
Please purchase and use H3C transceiver modules. |
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 (Informational) |
|
Example |
OPTMOD/6/OPTMOD_MODULE_CHECK: An H3C transceiver is detected. Please go to the website www.h3c.com to verify its authenticity. |
|
Impact |
No negative impacts on the system. |
|
Cause |
When no H3C optical transceiver module is detected on the device, this log will be printed. Remind users to visit the H3C official website (www.h3c.com) for bar code anti-counterfeiting verification. |
|
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: Port name. |
|
Severity level |
4 (Warning) |
|
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! |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
This log is generated when a non-H3C transceiver module is detected. |
|
Recommended action |
1. Please purchase and use H3C transceiver modules. 2. If Verify using H3C optical transceiver module, collect the configuration file, log file, and alarms, and then contact Technical Support. |
RX_ALM_OFF
|
Message text |
[STRING]: [STRING] was removed. |
|
Variable fields |
$1: Port name. $2: Rx fault type. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/RX_ALM_OFF: GigabitEthernet1/0/1: RX_not_ready was removed. |
|
Impact |
No negative impacts on the system. |
|
Cause |
This log is generated when the optical transceiver module RX fault is cleared. |
|
Recommended action |
No action is required. |
RX_ALM_ON
|
Message text |
[STRING]: [STRING] was detected. |
|
Variable fields |
$1: Port name. $2: Rx fault type. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/RX_ALM_ON: GigabitEthernet1/0/1: RX_not_ready was detected. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When an optical transceiver module RX fault is detected, this log is generated |
|
Recommended action |
The cause of the failure may be the optical transceiver module itself, or it may be a port or link issue, collect the configuration file, log file, and alarms, and then contact Technical Support. |
RX_POW_HIGH
|
Message text |
[STRING]: RX power is high. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/RX_POW_HIGH: GigabitEthernet1/0/1: RX power is high. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When the RX power of the optical module exceeds the high alarm threshold of the received optical power, this log is generated. |
|
Recommended action |
1. Adjust the link and increase the optical attenuation to ensure that the optical power of the optical module meets the normal working range of received optical power. 2. Use the display transceiver diagnosis interface command to Verify whether the power has exceeded the high alarm threshold of the received optical power. 3. Use the display transceiver alarm interface command to Verify whether there is currently a high alarm for received optical power. 4. If the high alarm threshold of the received optical power is indeed exceeded, it indicates a problem with the optical module. Please replace the transceiver module. |
RX_POW_LOW
|
Message text |
[STRING]: RX power is low. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/RX_POW_LOW: GigabitEthernet1/0/1: RX power is low. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When the optical transceiver module RX power is lower than the receive optical power low alarm threshold, this log is generated |
|
Recommended action |
1. Adjust the link to make the optical transceiver module receive optical power within the normal working range 2. Use the 'display transceive diagnosis interface' command to Verify whether the power has fallen below the receive optical power low alarm threshold 3. Use the 'display transceive alarm interface' command to Verify whether there is indeed a receive optical power low alarm currently 4. If it is indeed below the receive optical power low alarm threshold, it means there is a problem with the optical module. Please replace the transceiver module. |
RX_POW_NORMAL
|
Message text |
[STRING]: RX power is normal. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/RX_POW_NORMAL: GigabitEthernet1/0/1: RX power is normal. |
|
Impact |
No negative impacts on the system. |
|
Cause |
This log is generated when the optical transceiver module RX power is recovered to the normal range |
|
Recommended action |
No action is required. |
TEMP_HIGH
|
Message text |
[STRING]: Temperature is high. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TEMP_HIGH: GigabitEthernet1/0/1: Temperature is high. |
|
Impact |
High temperature will affect the normal operation of the optical transceiver module |
|
Cause |
When the temperature of the optical transceiver module exceeds the high temperature alarm threshold, this log is generated |
|
Recommended action |
1. Please Verify whether the ambient temperature in the computer room is too high. If the ambient temperature is indeed too high, please improve the room temperature and ensure normal ventilation of the equipment environment 2. Verify whether the device fan is working properly. If the fan is not working properly, install or replace the faulty fan 3. If the device fan is normal and the ambient temperature is normal, it means the optical transceiver module is faulty. Please replace the transceiver module. |
TEMP_LOW
|
Message text |
[STRING]: Temperature is low. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TEMP_LOW: GigabitEthernet1/0/1: Temperature is low. |
|
Impact |
Low temperature will affect the normal operation of the optical transceiver module. |
|
Cause |
When the temperature of the optical module is lower than the low temperature alarm threshold, this log is generated. |
|
Recommended action |
1. Please Verify whether the ambient temperature in the equipment room is too low. If the ambient temperature is indeed too low, please improve the room temperature. 2. If the ambient temperature is normal, it indicates a fault in the optical module. Please replace the transceiver module. |
TEMP_NORMAL
|
Message text |
[STRING]: Temperature is normal. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TEMP_NORMAL: GigabitEthernet1/0/1: Temperature is normal. |
|
Impact |
No negative impacts on the system. |
|
Cause |
This log is generated when the optical transceiver module temperature has recovered to the normal range. |
|
Recommended action |
No action is required. |
TX_ALM_OFF
|
Message text |
[STRING]: [STRING] was removed. |
|
Variable fields |
$1: Port name. $2: Tx fault type. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TX_ALM_OFF: GigabitEthernet1/0/1: TX_fault was removed. |
|
Impact |
No negative impacts on the system. |
|
Cause |
When the optical transceiver module TX fault is cleared, this log is generated |
|
Recommended action |
No action is required. |
TX_ALM_ON
|
Message text |
[STRING]: [STRING] was detected. |
|
Variable fields |
$1: Port name. $2: Tx fault type. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TX_ALM_ON: GigabitEthernet1/0/1: TX_fault was detected. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When an optical transceiver module TX fault is detected, this log is generated |
|
Recommended action |
The cause of the fault may be the optical transceiver module itself, or it may be a port or link issue, collect the configuration file, log file, and alarms, and then contact Technical Support. |
TX_POW_HIGH
|
Message text |
[STRING]: TX power is high. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TX_POW_HIGH: GigabitEthernet1/0/1: TX power is high. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When the optical module TX power exceeds the high alarm threshold of the transmitted optical power, this log is generated |
|
Recommended action |
1. Adjust the link, increase the optical attenuation to ensure that the optical power of the optical module meets the normal working range 2. Use the 'display transceiver diagnosis interface' command to Verify whether the power has exceeded the high alarm threshold of the transmitted optical power 3. Use the 'display transceiver alarm interface' command to Verify whether there is currently a high alarm for the transmitted optical power 4. If the high alarm threshold of the transmitted optical power has indeed been exceeded, it indicates a problem with the optical module. Please replace the transceiver module. |
TX_POW_LOW
|
Message text |
[STRING]: TX power is low. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TX_POW_LOW: GigabitEthernet1/0/1: TX power is low. |
|
Impact |
The transceiver module cannot run correctly. |
|
Cause |
When the optical module TX power is lower than the low optical power transmission alarm threshold, this log is generated |
|
Recommended action |
1. Verify the port status to see if it is shutdown. If the status is shutdown, restore the port status to up 2. Use the display transceiver diagnosis interface command to Verify whether the power is indeed lower than the low optical power transmission alarm threshold 3. Use the display transceiver alarm interface command to Verify whether there is currently a low optical power transmission alarm 4. If it is indeed lower than the low optical power transmission alarm threshold, it means there is a problem with the optical module. Please replace the transceiver module. 5. If the problem cannot be resolved, it may be a board problem (such as turning off the light, abnormal high-speed signals, etc.), collect the configuration file, log file, and alarms, and then contact Technical Support. |
TX_POW_NORMAL
|
Message text |
[STRING]: TX power is normal. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TX_POW_NORMAL: GigabitEthernet1/0/1: TX power is normal. |
|
Impact |
No negative impacts on the system. |
|
Cause |
Optical transceiver module TX power recovered to normal range, this log is generated |
|
Recommended action |
No action is required. |
TYPE_ERR
|
Message text |
[STRING]: The transceiver type is not supported by port hardware. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/TYPE_ERR: GigabitEthernet1/0/1: The transceiver type is not supported by port hardware. |
|
Impact |
The transceiver module cannot run correctly. |
|
Cause |
When the port hardware does not support the optical transceiver module type, this log is generated. |
|
Recommended action |
1. Replace the transceiver module. 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
VOLT_HIGH
|
Message text |
[STRING]: Voltage is high. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/VOLT_HIGH: GigabitEthernet1/0/1: Voltage is high. |
|
Impact |
The transceiver module might fail to run correctly. Or the optical transceiver module is damaged. |
|
Cause |
When the voltage of the optical transceiver module exceeds the overvoltage high alarm threshold, this log is generated. |
|
Recommended action |
1. Verify whether the port is working properly. If the port is not working properly, first Verify the port issue and resolve it. 2. Verify if this fault has occurred multiple times on other optical transceiver modules on the board. If so, it indicates a possible component failure on the board, collect the configuration file, log file, and alarms, and then contact Technical Support. 3. Use the display transceiver diagnosis interface command to Verify whether the voltage has exceeded the overvoltage high alarm threshold. 4. Use the display transceiver alarm interface command to Verify whether there is indeed a high voltage alarm currently. 5. If the overvoltage high alarm threshold is indeed exceeded, it means there is a problem with the optical transceiver module. Please replace the transceiver module. |
VOLT_LOW
|
Message text |
[STRING]: Voltage is low. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/VOLT_LOW: GigabitEthernet1/0/1: Voltage is low. |
|
Impact |
The transceiver module might fail to run correctly. |
|
Cause |
When the voltage of the optical transceiver module is lower than the low voltage alarm threshold, this log is generated |
|
Recommended action |
1. Verify whether the port is working properly. If the port is not working properly, Verify the port issue and resolve it first 2. Confirm if other optical transceiver modules on the board have encountered this fault multiple times. If so, it indicates a component failure on the board, collect the configuration file, log file, and alarms, and then contact Technical Support. 3. Use the display transceiver diagnosis interface command to Verify whether the voltage has exceeded the low voltage alarm threshold 4. Use the display transceiver alarm interface command to Verify whether there is currently a low voltage alarm 5. If it is indeed below the low voltage alarm threshold, it indicates a problem with the optical transceiver module. Please replace the transceiver module. |
VOLT_NORMAL
|
Message text |
[STRING]: Voltage is normal. |
|
Variable fields |
$1: Port name. |
|
Severity level |
3 (Error) |
|
Example |
OPTMOD/3/VOLT_NORMAL: GigabitEthernet1/0/1: Voltage is normal! |
|
Impact |
No negative impacts on the system. |
|
Cause |
This log is generated when the optical transceiver module voltage is restored to normal range. |
|
Recommended action |
No action is required. |
MODULATION_INVALID
|
Message text |
The transceiver module in [STRING] does not support modulation mode [STRING] configured on the interface. |
|
Variable fields |
$1: Port name. $2: Modulation mode. Options include: · Diff 15% SD-FEC QPSK Everest Compatible · Non-Diff 15% SD-FEC QPSK Denali Compatible · Non-Diff 15% SD-FEC 8QAM Denali Compatible · Non-Diff 15% SD-FEC 16QAM Denali Compatible |
|
Severity level |
4 (Warning) |
|
Example |
OPTMOD/4/MODULATION_INVALID: The transceiver module in HundredGigE1/0/1 does not support modulation mode Diff 15% SD-FEC QPSK Everest Compatible configured on the interface. |
|
Impact |
Failed to set the modulation mode for the transceiver module installed on the interface. |
|
Cause |
The newly inserted transceiver module does not support the modulation mode configured for the transceiver module installed on the interface. |
|
Recommended action |
Cancel the configuration or reconfigure the modulation mode. |
TX_POW_INVALID
|
Message text |
The transceiver module [STRING] does not support transmission power [STRING] dBm configured on the interface. |
|
Variable fields |
$1: Port name. $2: Output optical power of the transceiver module. |
|
Severity level |
4 (Warning) |
|
Example |
OPTMOD/4/TX_POW_INVALID: The transceiver module in HundredGigE1/0/1 does not support transmission power 0.3dBm configured on the interface. |
|
Impact |
Failed to set the output optical power for the transceiver module installed on the interface. |
|
Cause |
The newly inserted transceiver module does not support the output optical power configured for the transceiver module installed on the interface. |
|
Recommended action |
Cancel the configuration or reconfigure the output optical power. |
ITU_CHANNEL_INVALID
|
Message text |
The transceiver module in [STRING] does not support ITU channel number [UINT32] configured on the interface. |
|
Variable fields |
$1: Port name. $2: ITU channel number of the transceiver module. |
|
Severity level |
4 (Warning) |
|
Example |
OPTMOD/4/ITU_CHANNEL_INVALID: The transceiver module in HundredGigE1/0/1 does not support ITU channel number 3 configured on the interface. |
|
Impact |
Failed to set the ITU channel number for the transceiver module installed on the interface. |
|
Cause |
The newly inserted transceiver module does not support the ITU channel number configured for the transceiver module installed on the interface. |
|
Recommended action |
Cancel the configuration or reconfigure the ITU channel number. |
OSPF messages
This section contains OSPF messages.
OSPF_ADJSID_CONFLICT
|
Message text |
OSPF [UINT16] failed to allocate adjacent SID [UINT32] to interface [STRING] because of SID conflict. |
|
Variable fields |
$1: OSPF process ID. $2: Adjacency SID. $3: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
OSPF/4/OSPF_ADJSID_CONFLICT: OSPF 1 failed to allocate adjacent SID 15010 on interface Route-Aggregation1 because of SID conflict. |
|
Impact |
The system selects only one SID, and ignores the same SID advertised by other devices. |
|
Cause |
The adjacency SID configured on the local device is being used by another device. |
|
Recommended action |
Use the ospf adjacency-sid command on the advertising source to edit the adjacency SID configuration. Before editing the configuration, use the display mpls label command to verify that the adjacency SID is free. |
OSPF_CANNOT_ENTER_HELPER
|
Message text |
OSPF [ProcessId] cannot act as GR helper on interface [STRING] due to [STRING]. (RouterID=[STRING], AreaID=[STRING], NbrIPAddr=[STRING], NbrRtrID=[STRING]) |
|
Variable fields |
$1: OSPF process ID. $2: Interface name. $3: Reason why the OSPF process cannot enter GR helper mode: · HelperDisable—The process is not enabled with the helper capability. · GRConfigMismatch—The GR helper and restarter settings do not match. · NbrNotFull—The neighbor is not in Full state. · RxmtChgLSA—The retransmission list of the restarting neighbor contains changed LSAs. · GRPeriodError—GR period error. · GRReasonError—GR reason error. $4: Router ID of the local process. $5: OSPF area ID. $6: IP address of the neighbor. $7: Router ID of the neighbor. |
|
Severity level |
6 (Informational) |
|
Example |
OSPF/6/OSPF_CANNOT_ENTER_HELPER: OSPF 1 cannot act as GR helper on interface GE1/0/1 due to GRPeriodError. (RouterID=1.1.1.1, AreaID=0.0.0.1, NbrIPAddr=10.1.1.12, NbrRtrID=2.2.2.2) |
|
Impact |
GR might fail, resulting in route forwarding failure. |
|
Cause |
Reason why the OSPF process cannot enter GR helper mode. · The process is not enabled with the helper capability. · The GR helper and restarter settings do not match. · Neighbor is not in the Full state. · The retransmission list of the restarting neighbor contains changed LSAs. · GR period error. · GR reason error. |
|
Recommended action |
If the reason why the OSPF process cannot enter GR helper mode is HelperDisable, take the following actions: 1. Use the graceful-restart helper enable command to enable the GR helper capability. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. If the reason why the OSPF process cannot enter GR helper mode is GRConfigMismatch or GRReasonError, take the following actions: 3. Identify whether the GR-associated settings match on the GR helper and GR restarter. ¡ If they do not match, proceed to step 2. ¡ If they do not match, edit related settings. For example, if the GR restarter uses the IETF standard, the GR helper must also use the IETF standard. Then identify whether the log message is still generated. If the log message is not generated, the processing is completed. If the log message is still generated, proceed to step 2. 4. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. If the reason why the OSPF process cannot enter GR helper mode is NbrNotFull, take the following actions: 5. Use the display ospf peer command to check the neighbor state. If the neighbor cannot enter the Full state, troubleshoot the issue. 6. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. If the reason why the OSPF process cannot enter GR helper mode is RxmtChgLSA, take the following actions: 7. Enter the view of the OSPF process displayed in the log message, and then use the display this command to identify whether the graceful-restart helper strict-lsa-checking command is configured. ¡ If the graceful-restart helper strict-lsa-checking command is configured, use the display ospf retrans-queue command to identify whether the retransmission list contains data that has not been completed. If such data exists, no action is required. If no such data exists, proceed to step 2. ¡ If the graceful-restart helper strict-lsa-checking command is not configured, proceed to step 2. 8. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. If the reason why the OSPF process cannot enter GR helper is GRPeriodError, take the following actions: 9. Enter the view of the OSPF process displayed in the log message, and then use the display this command to identify whether the GR interval configuration is appropriate. ¡ Make sure the OSPF GR interval is greater than the maximum neighbor dead timer among all the OSPF interfaces. Then identify whether the log message is still generated. If the log message is not generated, the processing is completed. If the log message is still generated, proceed to step 2. ¡ If the GR interval is appropriate, proceed to step 2. 10. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
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 |
4 (Warning) |
|
Example |
OSPF/4/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. |
|
Impact |
Router LSA continues to refresh, causing route flapping. |
|
Cause |
Two directly connected devices have the same router ID configured. |
|
Recommended action |
1. Take an action based on the ways to obtain the router ID for the OSPF process: ¡ If the OSPF process uses the global router ID, execute the router id command to edit the router ID. ¡ If the OSPF process uses a manually specified router ID, execute the ospf router-id command to edit the router ID. ¡ If the OSPF process uses an automatically obtained router ID, execute the ip address command to edit the IP address of the corresponding interface. 2. Execute the reset ospf process command to enable the new router ID to take effect. |
OSPF_IF_CONFIG_ERROR
|
Message text |
OSPF [UINT16] dropped a [STRING] packet on interface [STRING] due to incorrect configuration. (RouterID=[STRING], AreaID=[STRING], PacketSrc=[STRING], ConfigErrorType=[STRING]) |
|
Variable fields |
$1: OSPF process ID. $2: Packet type. Options include Hello, DD, LSR, LSU, and LSAck. $3: Interface name. $4: Router ID. $5: OSPF area ID. $6: Source IP address of the packet. $7: Error type: · VersionMismatch—Version number mismatch. · AreaMismatch—Area mismatch. · UnknownNbmaNbr—Unknown NBMA neighbor. · UnknownVirNbr—Unknown virtual link neighbor. · AuthTypeMismatch—Authentication type mismatch. · AuthCheckFail—Authentication failure. · NetworkMaskMismatch—Network mask mismatch. · HelloTimeMismatch—Hello time mismatch. · DeadTimeMismatch—Dead timer mismatch. · OptionMismatch—Option field mismatch. · MtuMismatch—MTU mismatch. · RouterIdConflict—Router ID conflict. OtherReason—Unknown error. |
|
Severity level |
4 (Warning) |
|
Example |
OSPF/4/OSPF_IF_CONFIG_ERROR: OSPF 1 dropped a Hello packet on interface GE1/0/1 due to incorrect configuration. (RouterID=1.1.1.1, AreaID=0.0.0.1, PacketSrc=10.10.1.1, ConfigErrorType= HelloTimeMismatch) |
|
Impact |
The neighbor relationship cannot be established, and routes cannot be learned. |
|
Cause |
The interface parameter settings are inconsistent. |
|
Recommended action |
1. Use the display ospf interface command to identify whether the settings are consistent on both ends. ¡ If the settings are consistent, proceed to step 3. ¡ If the settings are inconsistent, proceed to step 2. 2. If you are allowed to configure consistent settings on both ends, proceed to step 3. If not, proceed to step 4. 3. Configure consistent hello, dead, and poll timers on both ends. Identify whether the log message is still generated. ¡ If the log message is not generated, the processing is completed. ¡ If the log message is still generated, proceed to step 4. 4. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
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 (Informational) |
|
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. |
|
Impact |
The following impacts might exist on the system: · The device CPU or memory usage is too high. · OSPF frequently ages and regenerates LSAs. · Device routes are frequently refreshed, and route calculation errors occur. |
|
Cause |
The interfaces on the two devices in the same OSPF area might be configured with the same primary IP address, and at least one of the devices is DR. |
|
Recommended action |
1. Identify whether OSPF_RTRID_CONFLICT_INTRA is generated on both devices, that is, whether router ID conflict occurs in the same OSPF area. ¡ If a router ID conflict occurs in the same OSPF area, resolve the issue based on the recommended action of the OSPF_RTRID_CONFLICT_INTRA log message. ¡ If no router ID conflict occurs in the same OSPF area, proceed to step 2. 2. Obtain interface information from the log message, and then edit the primary IP address of the interface. Make sure the device interfaces in the same OSPF area use different primary IP addresses. |
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: Reasons for the OSPF neighbor state becoming Down include: · Ospf Interface Parameters Changed. · Reset ospf command was performed. · Undo ospf command was performed. · Undo area command was performed. · Undo network—The undo network command is executed. · Silent Interface—The silent interface command is executed. · Ospf_iflchange—Interface logical attribute change. · Ospf_ifachange—Interface physical attribute change. · Ospf_ifvchange—Interface virtual link attribute change. · Vlink down—Virtual link interface down. · Shamlink down—Sham link interface down. · DeadInterval timer expired—Dead interval timer timeout. · Configuring stub area—Stub area configuration change. · Configuring nssa area—NSSA area configuration change. · Opaque-Capability changed—Configuration change for opaque-capability enable. · Out-of-Band Resynchronazition Capability changed—Configuration change for enable out-of-band-resynchronization. · BFD session down · Database-filter or referenced ACL changed—Configuration change for filtering LSA sent to a specific neighbor or change of the ACL rule specified for the configuration. · shutdown—The shutdown process command is configured. |
|
Severity level |
6 (Informational) |
|
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. |
|
Impact |
Service interruption might occur. |
|
Cause |
· Adjacent timer timeout · Physical interface change · The OSPF-associated BFD session goes down · OSPF configuration change · Neighbor device reasons |
|
Recommended action |
If the reason for OSPF neighbor down is adjacent timer timeout, take the following actions: 1. Execute the ping command to check if the device link is faulty (including transmission device faults). ¡ If ping fails, check the transmission device, link status, interface situation, and adjust hardware device to restore the service. ¡ If ping is successful, go to step 2. 2. Collect the configuration data, log messages, and alarm information, and then contact Technical Support for help. If the reason for OSPF neighbor down is physical interface change, take the following actions: 3. Execute the display interface [ interface-type [ interface-number | interface-number.subnumber ] ] command to check the status of the physical interface that establishes the OSPF neighbor relationship. ¡ If the physical status of the interface is DOWN, check if the transmission equipment is normal, and restore the physical interface status to eliminate the fault. ¡ If the physical status of the interface is Administratively DOWN, it means that the interface has been manually closed with the shutdown command, open the interface by executing the undo shutdown command under the interface. ¡ If the physical status of the interface is UP, go to step 2. 4. Execute the display ospf interface command to check if the interface is in a normal state under the OSPF protocol. ¡ If the OSPF interface status is Down, check if the interface is configured with an IP address, and eliminate the fault by checking the IP address. ¡ If the OSPF interface status is P-2-P, DR, BDR, or DROther, go to step 3. 5. Collect the configuration file, log file, and alarms, and then contact Technical Support. If the reason for OSPF neighbor down is BFD session down, take the following actions: 6. Execute the ping command to check if the device link is faulty (including transmission equipment faults). ¡ If ping fails, check the transmission equipment, link status, interface situation, and adjust hardware equipment to restore service. ¡ If ping is successful, go to step 2. 7. Collect the configuration data, log messages, and alarm information, and then contact Technical Support. If the reason for OSPF neighbor down is configuration change, take the following actions: 8. Use the display ospf interface command to check if the OSPF area ID configuration at both ends is consistent. ¡ If they are consistent, go to step 2. ¡ If not consistent, modify to be consistent. 9. Use the display ospf interface command to check if the network types of the local and remote interfaces are consistent. ¡ If they are not consistent, edit the settings. ¡ If they are consistent, go to step 3. 10. Use the display ospf statistics error command every 10 seconds to check the OSPF error statistics and continue for 5 minutes. ¡ If the count value corresponding to the Bad authentication type field keeps increasing, it means that the OSPF authentication types configured on the two devices establishing the neighbor are inconsistent, and the same authentication type needs to be configured on both devices. ¡ If the count value corresponding to the Hello-time mismatch field keeps increasing, it means that the values of the Hello timer on the interface are inconsistent, and the Hello timer values on both interfaces need to be set to be consistent. ¡ If the count value corresponding to the Dead-time mismatch field keeps increasing, it means that the values of the Dead timer on the interface are inconsistent, and the Dead timer values on both interfaces need to be set to be consistent. ¡ If the count value corresponding to the Ebit option mismatch field keeps increasing, it means that the area type configuration is inconsistent (one end is configured as a normal area, and the other end is configured as a Stub or NSSA area), and the area types on both ends need to be set to be consistent. 11. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_LDP_SYNC_STATUS
|
Message text |
The LDP synchronization state of OSPF [UINT16] interface [STRING] changed from [STRING] to [STRING]. (AreaId=[STRING]) |
|
Variable fields |
$1: OSPF process ID. $2:Interface name. $3: Previous state of the local device. Options include: · INIT—Initial state. · HOLD_MAX_COST—Keeps the maximum cost advertised in the IGP route. · SYNC_ACHIEVED—Synchronization completed. · UNKNOWN—Unknown state. $4: Current state of the local device. Options include: · INIT—Initial state. · HOLD_MAX_COST—Keeps the maximum cost advertised in the IGP route. · SYNC_ACHIEVED—Synchronization completed. UNKNOWN—Unknown state. |
|
Severity level |
6 (Informational) |
|
Example |
OSPF/6/OSPF_LDP_SYNC_STATUS: The LDP synchronization state of OSPF 1 interface GE1/0/1 changed from HOLD_MAX_COST to SYNC_ACHIEVED. (AreaId=[0.0.0.0]) |
|
Impact |
No negative impact on the system. |
|
Cause |
The LDP synchronization state changed. |
|
Recommended action |
No action is required. |
OSPF_LSDB_APPROACH_OVERFLOW
|
Message text |
The number of AS-external LSAs in the OSPF [UINT16] LSDB is approaching the limit [UINT32]. |
|
Variable fields |
$1: OSPF process ID. $2: Maximum number of external routes in the LSDB. |
|
Severity level |
6 (Informational) |
|
Example |
OSPF/6/OSPF_LSDB_APPROACH_OVERFLOW: The number of AS-external LSAs in the OSPF 1 LSDB is approaching the limit 10000. |
|
Impact |
When the number of Type-5 LSAs exceeds the upper limit, the system might fail to process the excess Type-5 LSAs correctly, resulting in loss of redistributed routes. |
|
Cause |
The number of external routes in the LSDB reached 90% of the upper limit. |
|
Recommended action |
1. Use the display ospf lsdb ase command to check the number of Type-5 LSAs in the LSDB. If the number is close to the upper limit and the maximum value can be adjusted, use the lsdb-overflow-limit command to edit the maximum value. If not, proceed to step 2. 2. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_LSDB_OVERFLOW_ACTIVE
|
Message text |
The number of AS-external LSAs in the LSDB of OSPF [UINT16] has exceeded the limit [UINT]. |
|
Variable fields |
$1: OSPF process ID. $2: Maximum number of external routes in the LSDB. |
|
Severity level |
5 (Notification) |
|
Example |
OSPF/5/OSPF_LSDB_OVERFLOW_ACTIVE: The number of AS-external LSAs in the LSDB of OSPF 1 has exceeded the limit 10000. |
|
Impact |
The system cannot process the excess Type-5 LSAs correctly, resulting in loss of redistributed routes. |
|
Cause |
The number of external routes in the LSDB has exceeded the upper limit supported by the system. |
|
Recommended action |
1. Use the display ospf lsdb ase command to check the number of Type-5 LSAs in the LSDB. If the number of external routes reaches the upper limit, use the lsdb-overflow-limit command to edit the maximum value. If the number of external routes has not reached the upper limit, proceed to step 2. 2. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_LSDB_OVERFLOW_CLEAR
|
Message text |
The number of AS-external LSAs in the LSDB of OSPF [UINT16] has dropped below the limit [UINT]. |
|
Variable fields |
$1: OSPF process ID. $2: Maximum number of external routes in the LSDB. |
|
Severity level |
6 (Informational) |
|
Example |
OSPF/6/OSPF_LSDB_OVERFLOW_CLEAR: The number of AS-external LSAs in the LSDB of OSPF 1 has dropped below the limit 10000. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of external routes in the LSDB drops below the upper limit specified with the lsdb-overflow-limit command. |
|
Recommended action |
No action is required. |
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: Original neighbor state. $5: New neighbor state. |
|
Severity level |
3 (Error) |
|
Example |
OSPF/3/OSPF_NBR_CHG: OSPF 1 Neighbor 2.2.2.2 (Vlan-interface100) changed from Full to Down. |
|
Impact |
The sequence of OSPF neighbor state changes from low to high is: Down->Init->2-Way->ExStart->Exchange->Loading->Full. If the neighbor state changes from a lower state to a higher state, no action is required. If the neighbor state changes from a higher state to a lower state, service interruption might occur. |
|
Cause |
The following reasons might cause the OSPF neighbor state to change from the 2-way or Full state to other states: · Link fault. OSPF packets are discarded. · DR priority configuration of the interface is not appropriate. · The OSPF MTU values configured on both ends are different. · The adjacency timer times out. · The BFD session associated with OSPF goes down. |
|
Recommended action |
1. Execute the display ospf peer command to check the State field, which indicates the neighbor state. If the neighbor state is Full, no action is required. If not, proceed to step 2. 2. Execute the display interface interface-type interface-number command to view the state of the interface connected to the neighbor. ¡ If the physical interface state is Up, proceed to step 3. ¡ If the physical interface state is Down, identify whether the shutdown command is configured for the interface. If the shutdown command is configured for the interface, execute the undo shutdown command, and then proceed to step 3. If the shutdown command is not configured, proceed to step 3. 3. Identify whether the IP address of the peer interface can be pinged. ¡ If the ping operation fails, proceed to step 6. ¡ If the ping operation succeeds, proceed to step 4. 4. Execute the display ospf interface command to check the State field, which indicates the OSPF interface state. ¡ If the interface with neighbor relationship established is down, proceed to step 6. ¡ If the interface with neighbor relationship established is not down, proceed to step 5. 5. Execute the display ospf interface verbose command to identify whether the hello timer, dead timer, poll timer, OSPF network type, and authentication settings are consistent on the local and peer devices. If the settings are consistent, proceed to step 6. If the settings are inconsistent, use the following commands to edit the settings: ¡ ospf timer hello ¡ ospf timer dead ¡ ospf timer poll ¡ ospf network-type ¡ ospf authentication-mode 6. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_NBR_CHG_REASON
|
Message text |
OSPF [UINT32] Area [STRING] Router [STRING]([STRING]) CPU usage: [STRING], VPN name: [STRING], IfMTU: [UINT32], Neighbor address: [STRING], NbrID [STRING] changed from [STRING] to [STRING] at [STRING]. Last 4 hello packets received at: [STRING] Last 4 hello packets sent at: [STRING] |
|
Variable fields |
$1: OSPF process ID. $2: Area ID. $3: Router ID. $4: Abbreviated interface name. $5: CPU usage. $6: VPN instance name. It is displayed in neighbor state change log information for only OSPF multi-instance processes. $7: Interface MTU. $8: IP address of the neighbor. $9: Router ID of the neighbor. $10: Neighbor state before the change. $11: Neighbor state after the change and the reason for the state change: · to DOWN because OSPF interface parameters changed · to DOWN because the OSPF process was reset · to DOWN because the OSPF process was deleted · to DOWN because the OSPF area was deleted · to DOWN because OSPF was disabled (Interface: interface, peer address: address) · to DOWN because OSPF packet receiving and sending are disabled (Interface: interface, peer address: address) · to DOWN because the interface address was deleted or OSPF was disabled on interface · to DOWN because the interface went down or MTU changed · to DOWN because the virtual link was deleted or the route it relies on was deleted · to DOWN because to DOWN because the virtual link interface went down or the virtual link settings were deleted · to DOWN because the sham link was deleted or the route it relies on was deleted · to DOWN because the dead timer expired · to DOWN because the stub configuration changed in area area-id · to DOWN because the NSSA configuration changed in area area-id · to DOWN because the Opaque LSA capability configuration changed · to DOWN because the out-of-band resynchronization capability configuration changed · to DOWN because BFD session went down · to INIT because a 1-way hello packet was received · to DOWN because database-filter configuration changed or database-filter ACL configuration changed · to EXSTART because a BadLSReq event was triggered upon the request for a nonexistent LSA · to EXSTART because the LSA requested and then learned is the same as that in local · to EXSTART because the LSA requested and then learned is older than that in local · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a non-retransmitted DD packet from the Loading or Full peer during the DD retransmit interval · to EXSTART because a SeqNumberMismatch event was triggered by the change of the OSPF peer’s capability to link-local signaling attribute · to EXSTART because a SeqNumberMismatch event was triggered by the OSPF peer’s multi-topology attribute change · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a retransmitted DD packet from the Loading or Full peer after the DD retransmit interval expired · to EXSTART because a SeqNumberMismatch event was triggered by the change of the OSPF peer’s capability to receive AS external LSA · to EXSTART because a SeqNumberMismatch event was triggered by the master-slave relationship change · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of an unexpected initial DD packet after DD transmission started · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a DD packet with a wrong sequence number from the slave · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a DD packet with a wrong sequence number from the master · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a DD packet containing local opaque LSA without enabling the opaque capability · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a DD packet containing area opaque LSA without enabling the opaque capability · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a DD packet containing AS opaque LSA without enabling the opaque capability · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a DD packet containing NSSA external LSA in a non-NSSA area · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a DD packet containing invalid LSA · to EXSTART because a SeqNumberMismatch event was triggered upon the receipt of a DD packet containing AS external LSA in the stub area or on the virtual link $12: Time when the neighbor state changed. $13: Time when the last four hello packets were received before neighbor state change. $14: Time when the last four hello packets were sent before neighbor state change. |
|
Severity level |
5 (Notification) |
|
Example |
OSPF/5/OSPF_NBR_CHG_REASON: OSPF 1 Area 0.0.0.0 Router 2.2.2.2(GE1/0/1) CPU usage:3.80%, VPN name: a, IfMTU:1500, Neighbor address:10.1.1.2, NbrID:1.1.1.1 changed from Full to Down because OSPF interface parameters changed at 2019-04-01 15:20:57:034. Last 4 hello packets received at: 2019-09-01 15:19:46:225 2019-09-01 15:19:56:224 2019-09-01 15:20:06:225 2019-09-01 15:20:16:225 Last 4 hello packets sent at: 2019-09-01 15:20:22:033 2019-09-01 15:20:32:033 2019-09-01 15:20:42:032 2019-09-01 15:20:52:033 |
|
Impact |
The sequence of OSPF neighbor state changes from low to high is: Down->Init->2-Way->ExStart->Exchange->Loading->Full. If the neighbor state changes from a lower state to a higher state, no action is required. If the neighbor state changes from a higher state to a lower state, service interruption might occur. |
|
Cause |
· The OSPF adjacency state transitions from the Attempt state to 1-way or Down state, or from the Down state to 2-way or Full state. · Configuration parameters of the local end or peer interface (such as hello timer, dead timer, and interface authentication) are inconsistent. · Restart the OSPF protocol by executing the reset ospf process command. · The interface adjacency state on the NBMA network or broadcast network changes from Full to other states, or from other states to Full. |
|
Recommended action |
1. Execute the display ospf peer command to check the State field, which indicates the neighbor state. If the neighbor state is Full, no action is required. If not, proceed to step 2. 2. Execute the display interface interface-type interface-number command to view the state of the interface connected to the neighbor. ¡ If the physical interface state is Up, proceed to step 3. ¡ If the physical interface state is Down, identify whether the shutdown command is configured for the interface. If the shutdown command is configured for the interface, execute the undo shutdown command, and then proceed to step 3. If the shutdown command is not configured, proceed to step 3. 3. Identify whether the IP address of the peer interface can be pinged. ¡ If the ping operation fails, proceed to step 6. ¡ If the ping operation succeeds, proceed to step 4. 4. Execute the display ospf interface command to check the State field, which indicates the OSPF interface state. ¡ If the interface with neighbor relationship established is down, proceed to step 6. ¡ If the interface with neighbor relationship established is not down, proceed to step 5. 5. Execute the display ospf interface verbose command to identify whether the parameter settings are consistent on the local and peer devices. ¡ If the settings are inconsistent, edit the parameter settings. ¡ If the settings are consistent, proceed to step 6. 6. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_NBR_GR_HELPER_STATUS
|
Message text |
The GR helper status of OSPF [UINT16]’s neighbor on interface [STRING] changed to [STRING]. (RouterID=[STRING], AreaID=[STRING], NbrIPAddr=[STRING], NbrRtrID=[STRING], GRHelperAge=[UINT], GRHelperExitReason=[STRING]) |
|
Variable fields |
$1: OSPF process ID. $2: Interface name. $3: New state of the GR helper, Normal or Helper. $4: Router ID of the local process. $5: OSPF area ID. $6: IP address of the neighbor. $7: Router ID of the neighbor. $8: Remaining time for the neighbor to complete GR. $9: Reason why the neighbor quits helper state. · Success—GR completes. · Recv1WayHello—A one-way hello packet is received. · RecvNoLRBitHello—A hello packet with the LSDB Resynchronization (LR) bit not set is received. · RecvNoLRBitDD—A DD packet with the LR bit not set is received. · RecvNoEABitDD—A DD packet with the EA bit not set is received. · RecvNoRBitDD—A DD packet with the R bit not set is received. · WaitTimerExpire—The timer expires. · OOBResyncTimerExpire—OOB sync timer expires. · GracePeriodExpire—Grace period expires. · TopoChange—Topology change. · NbrReset—Neighbor restart. |
|
Severity level |
4 (Warning) |
|
Example |
OSPF/4/OSPF_NBR_GR_HELPER_STATUS: The GR helper status of OSPF 1’s neighbor on interface GE1/0/1 changed to Normal. (RouterID=1.1.1.1, AreaID=0.0.0.0, NbrIPAddr=10.0.0.11, NbrRtrID=2.2.2.2, GRHelperAge=10, GRHelperExitReason=NbrReset) |
|
Impact |
If the neighbor's GR helper status changes and GR fails, route calculation will be affected, and services will be impacted. |
|
Cause |
The OSPF neighbor enters or exits the GR helper state. |
|
Recommended action |
1. If an active/standby switchover or process restart was performed, no action is required. If this log message is generated without manual intervention, proceed to step 2. 2. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_PEER_FLAPPING_STATUS
|
Message text |
The peer flapping suppression status of OSPF [UINT16] on interface [STRING] changed to [STRING] due to [STRING].(AreaID=[STRING]) |
|
Variable fields |
$1: Process ID. $2: Interface name. $3: Neighbor flapping suppression state. Options include: · NoSuppress—No suppression. · HoldDown—Hold-down mode. · HoldMaxCost—Hold-max-cost mode. $4: Reason for the neighbor flapping suppression state change: · ExitSuppress—Quits the suppression state when the flapping detection resume threshold is reached. · ConfigurationChanged—Configuration change (for example, OSPF process reset). · PeerFlapping—Frequent neighbor flappings. · ExitHoldDownAndEnterHoldMaxCost—Quits the hold-down mode and enters the hold-max-cost mode. $5: OSPF area ID. |
|
Severity level |
6 (Informational) |
|
Example |
OSPF/6/OSPF_PEER_FLAPPING_STATUS: The peer flapping suppression status of OSPF 1 on interface GE1/0/1 changed to HoldMaxCost due to ExitHoldDownAndEnterHoldMaxCost. (AreaID=0.0.0.0) |
|
Impact |
The interface that flaps frequently within a certain period might advertise the maximum link cost or delay the establishment of neighbor relationship. |
|
Cause |
The OSPF interface enters the neighbor flapping suppression phase, or exits the neighbor flapping suppression phase. |
|
Recommended action |
· If the reason for the neighbor flapping suppression state change is ExitSuppress, no action is required. · If the reason for the neighbor flapping suppression state change is PeerFlapping, identify whether the interface in the log message flaps frequently. ¡ If the interface flaps frequently, troubleshoot the flapping issue. ¡ If the interface does not flap frequently, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. · If the reason for the neighbor flapping suppression state change is ConfigurationChanged or ExitHoldDownAndEnterHoldMaxCost, no action is required. |
OSPF_PREFIX_SID_OVER_RANGE
|
Message text |
OSPF [UINT16] received prefix SID [UINT32]. The prefix SID is not included in the local SRGB range. (Prefix=[STRING], AdvertiseSource=[STRING], localSRGB=[UINT32]-[UINT32]) |
|
Variable fields |
$1: OSPF process ID. $2: Received prefix SID. $3: Prefix address and mask. $4: Advertising source. $5: Minimum value of the local SRGB. $6: Maximum value of the local SRGB. |
|
Severity level |
4 (Warning) |
|
Example |
OSPF/4/OSPF_PREFIX_SID_OVER_RANGE: OSPF 1 received prefix SID 16020. The prefix SID is not included in the local SRGB range. (Prefix=10.1.1.0/24, AdvertiseSource=2.2.2.2, localSRGB=16000-16010) |
|
Impact |
Invalid labels might result in forwarding failure. |
|
Cause |
The value for the remote prefix SID received by OSPF is out of the local SRGB range. |
|
Recommended action |
1. Obtain the router ID of the advertising source based on the value of AdvertiseSource field in the log message. 2. Locate the source device based on the router ID, and then edit the prefix SID value on the source device. Make sure the prefix SID value is in the local SRGB range. Then identify whether the log message is still generated. ¡ If the log message is not generated, the processing is completed. ¡ If the log message is still generated, proceed to step 3. 3. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_PREFIXSID_CONFLICT
|
Message text |
OSPF failed to allocate prefix SID [UINT32] for IP address [STRING] because of SID conflict. |
|
Variable fields |
$1: Prefix SID. $2: IP address and subnet mask. |
|
Severity level |
4 (Warning) |
|
Example |
OSPF/4/OSPF_PREFIXSID_CONFLICT: OSPF failed to allocate prefix SID 18020 for IP address 103.0.0.1/32 because of SID conflict. |
|
Impact |
If SID conflict occurs, the system selects one SID. The same SID advertised by other devices will be ignored. |
|
Cause |
Multiple devices in the network advertise the same prefix SID. |
|
Recommended action |
1. Locate the advertising source based on the prefix SID, and then edit the SID configuration for the loopback interface of the source device. Before editing the prefix SID configuration, use the display mpls label command to verify that the prefix SID is free. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_PREFIXSID_CONFLICT_CLEAR
|
Message text |
OSPF prefix SID conflict is resolved. (PrefixSID=[UINT32], PrefixAddr=[STRING]) |
|
Variable fields |
$1: Prefix SID. $2: Prefix address. |
|
Severity level |
5 (Notification) |
|
Example |
OSPF/5/OSPF_PREFIXSID_CONFLICT_CLEAR: OSPF prefix SID conflict is resolved. (PrefixSID=18020, PrefixAddr=103.0.0.1/32) |
|
Impact |
No negative impact on the system. |
|
Cause |
The prefix SID of the loopback interface no longer conflicts with that of any other devices in the network. The conflict has been cleared. |
|
Recommended action |
No action is required. |
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 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
The user changed the router ID or the interface IP used, which caused the OSPF router ID to change. Manual restart of the OSPF process is required to make the new router ID take effect. |
|
Recommended action |
To have the new Router ID take effect, make sure the process restart will not affect services, and 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 (Informational) |
|
Example |
OSPF/6/OSPF_RTRID_CONFILICT_INTER: OSPF 1 Received newer self-originated ase-LSAs. Possible conflict of router ID 11.11.11.11. |
|
Impact |
AS External LSA continues to refresh, and external routes redistributed by ASBR continue to flap. |
|
Cause |
Two indirectly connected devices within the same OSPF area might have the same router ID configured, with one device being the ASBR. |
|
Recommended action |
1. Take an action based on the ways to obtain the router ID for the OSPF process: ¡ If the OSPF process uses the global router ID, execute the router id command to edit the router ID. ¡ If the OSPF process uses a manually specified router ID, execute the ospf router-id command to edit the router ID. ¡ If the OSPF process uses an automatically obtained router ID, execute the ip address command to edit the IP address of the corresponding interface. 2. Execute the reset ospf process command to enable the new router ID to 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 |
4 (Warning) |
|
Example |
OSPF/4/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. |
|
Impact |
Router LSA continues to refresh, causing route flapping. |
|
Cause |
Two indirectly connected devices in the same OSPF area have the same router ID configured. |
|
Recommended action |
1. Take an action based on the ways to obtain the router ID for the OSPF process: ¡ If the OSPF process uses the global router ID, execute the router id command to edit the router ID. ¡ If the OSPF process uses a manually specified router ID, execute the ospf router-id command to edit the router ID. ¡ If the OSPF process uses an automatically obtained router ID, execute the ip address command to edit the IP address of the corresponding interface. 2. Execute the reset ospf process command to enable the new router ID to take effect. |
OSPF_VIF_CONFIG_ERROR
|
Message text |
OSPF [UINT16] dropped a [STRING] packet on a virtual interface due to incorrect configuration. (RouterID=[STRING], VirtNbrAreaID=[STRING], VirtNbrRtrID=[STRING], PacketSrc=[STRING], ConfigErrorType=[STRING]) |
|
Variable fields |
$1: OSPF process ID. $2: Packet type. Options include Hello, DD, LSR, LSU, and LSAck. $3: Router ID of the local process. $4: Area ID of the virtual link. $5: Router ID of the virtual link neighbor. $6: Source IP address of the packet. $7: Error type: · VersionMismatch—Version number mismatch. · AreaMismatch—Area mismatch. · AuthTypeMismatch—Authentication type mismatch. · AuthCheckFail—Authentication failure. · NetworkMaskMismatch—Network mask mismatch. · HelloTimeMismatch—Hello time mismatch. · DeadTimeMismatch—Dead timer mismatch. · OptionMismatch—Option field mismatch. · OtherReason—Unknown error. |
|
Severity level |
4 (Warning) |
|
Example |
OSPF/4/OSPF_VIF_CONFIG_ERROR: OSPF 1 dropped a hello packet on a virtual interface due to incorrect configuration. (RouterID=1.1.1.1, VirtNbrAreaID=0.0.0.1, VirtNbrRtrID=2.2.2.2, PacketSrc=10.0.0.1, ConfigErrorType= HelloTimeMismatch) |
|
Impact |
The virtual link fails to be established. |
|
Cause |
The virtual link interface parameter settings are inconsistent. |
|
Recommended action |
1. Execute the display ospf vlink command to check the virtual link interface configuration, and resolve the configuration mismatch issue. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_VIR_INTF_CHG
|
Message text |
The status of OSPF [UNIT16] virtual interface change to [STRING]. (RouterID=[STRING], VirtIfAreaID=[STRING], VirtNbrRtrID=[STRING]) |
|
Variable fields |
$1: OSPF process ID. $2: Virtual link interface state, Down or P2P. $3: Router ID of the local process. $4: Transit area ID. $5: Router ID of the virtual link neighbor. |
|
Severity level |
6 (Informational) |
|
Example |
OSPF/6/OSPF_VIR_INTF_CHG: The status of OSPF 1 virtual interface changed to P2P. (RouterID=1.1.1.1, VirtIfAreaID=0.0.0.2, VirtNbrRtrID=10.1.1.3) |
|
Impact |
· No negative impact on the system if the virtual link interface state changed from Down to P2P. · If the virtual link interface state changed from P2P to Down, interface connection failure might occur. As a result, OSPF route calculation error might occur, and services might be interrupted. |
|
Cause |
· The virtual link interface state changed from P2P to Down or from Down to P2P. · The router ID of the virtual-link neighbor has changed. |
|
Recommended action |
1. Execute the display ospf vlink command to view the virtual link interface state. ¡ No action is required if the virtual link interface state changed from Down to P2P. ¡ If the virtual link interface state changed from P2P to Down, proceed to step 2. 2. Use the display ospf spf command to identify whether SpfNode associated with the router ID of the virtual link interface neighbor contains an S flag in the Flag field. The S flag indicates that the virtual link neighbor is reachable. ¡ If the flag does not exist, locate the reason for the reachability issue. ¡ If the flag exists, identify whether the virtual link interface configuration for the local and peer ends is correct. 3. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_VIR_NBR_GR_HELPER_STATUS
|
Message text |
The GR helper status of OSPF [UINT16]’s virtual neighbor changed to [STRING]. (RouterID=[STRING], VirtNbrAreaID=[STRING], VirtNbrRtrID=[STRING], GRHelperAge=[UINT], GRHelperExitReason=[STRING]) |
|
Variable fields |
$1: OSPF process ID. $2: New state of the GR helper, Normal or Helper. $3: Router ID of the local process. $4: Transit area ID of the virtual link neighbor. $5: Router ID of the virtual link neighbor. $6: Remaining time for the virtual link neighbor to complete GR. · $7: Reason why the virtual link neighbor quits GR: · Success—GR completes. · Recv1WayHello—A one-way hello packet is received. · RecvNoLRBitHello—A hello packet with the LSDB Resynchronization (LR) bit not set is received. · RecvNoLRBitDD—A DD packet with the LR bit not set is received. · RecvNoEABitDD—A DD packet with the EA bit not set is received. · RecvNoRBitDD—A DD packet with the R bit not set is received. · WaitTimerExpire—The timer expires. · OOBResyncTimerExpire—OOB sync timer expires. · GracePeriodExpire—Grace period expires. · TopoChange—Topology change. · NbrReset—Neighbor restart. |
|
Severity level |
4 (Warning) |
|
Example |
OSPF/4/OSPF_VIR_NBR_GR_HELPER_STATUS: The GR helper status of OSPF 1’s virtual neighbor changed to Normal. (RouterID=1.1.1.1, VirtNbrAreaID=0.0.0.1, VirtNbrRtrID=2.2.2.2, GRHelperAge=112, GRHelperExitReason= Success) |
|
Impact |
If the virtual link interface neighbor's GR helper status changes and GR fails, route calculation will be affected, and services will be impacted. |
|
Cause |
· The virtual link neighbor enters helper state. · The virtual link neighbor quits helper state. |
|
Recommended action |
1. If an active/standby switchover or process restart was performed, no action is required. If this log message is generated without manual intervention, proceed to step 2. 2. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
OSPF_VLINKID_CHG
|
Message text |
OSPF [UINT32] Router ID changed, reconfigure Vlink on peer |
|
Variable fields |
$1: OSPF process ID. |
|
Severity level |
5 (Notification) |
|
Example |
OSPF/5/OSPF_VLINKID_CHG:OSPF 1 Router ID changed, reconfigure Vlink on peer |
|
Impact |
The virtual link configuration on the peer device needs to be edited. |
|
Cause |
A new OSPF router ID takes effect on the local end. |
|
Recommended action |
1. Use the display ospf process-id command to obtain the router ID of the OSPF process from the log message. 2. Use the undo vlink-peer command to remove the existing virtual link configuration. Then, use the vlink-peer command to configure the virtual link again, specify the router ID in step 1 for the virtual link neighbor. |
OSPFV3 messages
This section contains OSPFv3 messages.
OSPFV3_IF_CONFIG_ERROR
|
Message text |
OSPFv3 [UINT16] dropped a [STRING] packet on interface [STRING] due to incorrect configuration. (RouterID=[STRING], AreaID=[STRING], IfInstID=[UINT8], PacketSrc=[STRING], ConfigErrorType=[STRING]) |
|
Variable fields |
$1: OSPFv3 process ID. $2: Packet type. Options include Hello, DD, LSR, LSU, and LSAck. $3: Interface name. $4: Router ID of the local process. $5: Area ID of the interface. $6: Instance ID of the interface. $7: Source IPv6 address of the packet. $8: Error type: · VersionMismatch—Version number mismatch. · AreaMismatch—Area mismatch. · UnknownNbmaNbr—Unknown NBMA neighbor. · AuthTypeMismatch—Authentication type mismatch. · AuthCheckFail—Authentication failure. · HelloTimeMismatch—Hello time mismatch. · DeadTimeMismatch—Dead timer mismatch. · OptionMismatch—Option field mismatch. · MtuMismatch—MTU mismatch. · RouterIdConflict—Router ID conflict. OtherReason—Unknown error. |
|
Severity level |
4 (Warning) |
|
Example |
OSPFV3/4/OSPFV3_IF_CONFIG_ERROR: OSPFv3 1 dropped a Hello packet on interface GE1/0/1 due to incorrect configuration. (RouterID=1.1.1.1, AreaID=0.0.0.0, IfInstID=0, PacketSrc=FE80::212, ConfigErrorType=HelloTimeMismatch) |
|
Impact |
The neighbor relationship cannot be established, and routes cannot be learned. |
|
Cause |
The interface parameter settings are inconsistent. |
|
Recommended action |
1. Use the display ospfv3 interface command to identify whether the settings are consistent on both ends. ¡ If the settings are consistent, proceed to step 3. ¡ If the settings are inconsistent, proceed to step 2. 2. If you are allowed to configure consistent settings on both ends, proceed to step 3. If not, proceed to step 4. 3. Configure consistent hello, dead, and poll timers on both ends. Identify whether the log message is still generated. ¡ If the log message is not generated, the processing is completed. ¡ If the log message is still generated, proceed to step 4. 4. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
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 for the OSPFv3 neighbor down event: · 1-Way · SeqMsmatch · BadLsreq · Ospfv3 Interface Parameters Changed · Reset ospfv3 command was performed · Undo ospfv3 command was performed · Undo area command was performed · Undo ospfv3 interface · Ospfv3 iflchange · Ospfv3 ifachange · DeadInterval timer expired · BFD session down · Silent Interface · Configuring stub area · Vlink down · Configuring nssa area · Shamlink down |
|
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. |
|
Impact |
Service interruption might occur. |
|
Cause |
This message is generated when one of the following conditions exists: · The OSPFv3 dead timer expires. · The physical interfaces change. · The BFD session collaborating with OSPFv3 goes down. · OSPFv3 configuration changes. · Issues occur on the OSPFv3 neighbor. |
|
Recommended action |
If the OSPFv3 neighbor down event occurs because of dead timer expiration, perform the following operations: 1. Execute the ping command to check for link failures (including transport device failures). ¡ If the local device cannot ping the neighbor, identify whether the related transport device, links, and interfaces are operating correctly. If a hardware issue exists, troubleshoot it for service recovery. ¡ If the local device can ping the neighbor, go to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support. If the OSPFv3 neighbor down event occurs because of interface status changes, perform the following operations: 3. Execute the display ipv6 interface [ interface-type [ interface-number | interface-number.subnumber ] ] command to view the status of the local interface used for OSPFv3 neighbor relationship establishment: ¡ If the local interface is in DOWN state, identify whether the related transport device is operating correctly, and then recover the physical interfaces. ¡ If the local interface is in Administratively DOWN state, the interface is shut down by the shutdown command. You can use the undo shutdown command to bring up the interface. ¡ If the local interface is in UP state, go to step 2. 4. Execute the display ospfv3 interface command to view the OSPFv3 status of the local interface used for OSPFv3 neighbor relationship establishment: ¡ If the local interface is in DOWN state, go to step 4. ¡ If the local interface is in P-2-P, DR, BDR, or DROther state, go to step 3. 5. Execute the display ospfv3 interface verbose command to view the OSPFv3 settings on the local and remote devices. ¡ If the local and remote devices use the same OSPFv3 settings, go to step 4. ¡ If the local and remote devices use different OSPFv3 settings, modify their OSPFv3 settings to ensure that they use the same OSPFv3 settings. 6. Collect alarm information, log messages, and configuration data, and then contact Technical Support. If the OSPFv3 neighbor down event occurs because the related BFD session goes down, perform the following operations: 7. Execute the ping command to check for link failures (including transport device failures). ¡ If the local device cannot ping the neighbor, identify whether the related transport device, links, and interfaces are operating correctly. If a hardware issue exists, troubleshoot it for service recovery. ¡ If the local device can ping the neighbor, go to step 2. 8. Collect alarm information, log messages, and configuration data, and then contact Technical Support. If the OSPFv3 neighbor down event occurs because of configuration changes, perform the following operations: 9. Execute the display ospfv3 interface command to view the OSPFv3 area ID setting on the local and remote devices. ¡ If the local and remote devices use the same OSPFv3 area ID, go to step 2. ¡ If the local and remote devices use different OSPFv3 area IDs, modify their OSPFv3 area IDs to ensure that they use the same OSPFv3 area ID. 10. Execute the display ospfv3 interface command to view the network type setting on the local and remote interfaces. ¡ If the local and remote interfaces use the same network type setting, go to step 3. ¡ If the local and remote interfaces use different network type settings, modify their network type settings to ensure that they use the same network type setting. 11. Execute the display ospfv3 statistics error command every 10 seconds for 5 minutes to observe the OSPFv3 error statistics: ¡ If the Authentication failure field keeps increasing, the local and remote devices use different OSPFv3 authentication methods. Make sure they use the same OSPFv3 authentication method. ¡ If the Hello-time mismatch field keeps increasing, the local and remote devices use different OSPFv3 hello timers. Make sure they use the same OSPFv3 hello timer. ¡ If the Dead-time mismatch field keeps increasing, the local and remote devices use different OSPFv3 dead timers. Make sure they use the same OSPFv3 dead timer. ¡ If the Ebit option mismatch field keeps increasing, the local and remote devices use different OSPFv3 area type settings (one is in a common area, and the other is in a stub or NSSA area. Make sure they use the same OSPFv3 area type setting. 12. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
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 |
3 (Error) |
|
Example |
OSPFV3/3/OSPFV3_NBR_CHG: OSPFv3 1 Neighbor 2.2.2.2 (Vlan100) received 1-Way and its state changed from Full to Init. |
|
Impact |
The OSPFv3 neighbor state ascends in the following order: Down > Init > 2-Way > ExStart > Exchange > Loading > Full. If the neighbor state transitions from a lower state to a higher state, you can ignore this log message. If the neighbor state transitions from a higher state to a lower state, service interruption might occur. |
|
Cause |
This message is generated when one of the following conditions exists: · Link failure occurs and OSPFv3 packets are discarded. · The local and remote ends use different DR priority settings. · The local and remote ends use different OSPFv3 MTU settings. · The OSPFv3 dead timer expires. · The BFD session collaborating with OSPFv3 goes down. |
|
Recommended action |
1. Execute the display ospfv3 peer command to view the OSPFv3 neighbor state. ¡ If the State field displays Full, no action is required. ¡ If the State field does not display Full, go to step 2. 2. Execute the display interface interface-type interface-number command to view the physical state of the neighbor-facing interface on the local device: ¡ If the interface is up, go to step 3. ¡ If the interface is down, identify whether the interface is shut down by the shutdown command. If the interface is shut down by the shutdown command, use the undo shutdown command to bring up the interface, and then go to step 3. If the interface is not shut down by the shutdown command, go to step 3. 3. Ping the neighbor interface (interface that connects the neighbor to the local device). ¡ If the local device cannot ping the neighbor interface, go to step 6. ¡ If the local device can ping the neighbor interface, go to step 4. 4. Execute the display ospfv3 interface command to view the OSPFv3 state of the neighbor-facing interface on the local device: ¡ If the State field displays Down, go to step 6. ¡ If the State field does not display Down, go to step 5. 5. Execute the display ospfv3 interface verbose command to view the OSPFv3 settings on the local device and the neighbor, including hello timer, dead timer, poll timer, OSPFv3 network type, and OSPFv3 authentication method. · If the local device and the neighbor use the same OSPFv3 settings, go to step 6. · If the local device and the neighbor use different OSPFv3 settings, use the following commands to modify their OSPFv3 settings, ensuring that they use the same OSPFv3 settings. ¡ ospfv3 timer hello ¡ ospfv3 timer dead ¡ ospfv3 timer poll ¡ ospfv3 network-type ¡ ospfv3 authentication-mode 6. Collect alarm information, log messages, and configuration data, and then contact Technical Support. |
OSPFV3_NBR_GR_HELPER_STATUS
|
Message text |
The GR helper status of OSPFv3 [UINT16]’s neighbor on interface [STRING] changed to [STRING]. (RouterID=[STRING], AreaID=[STRING], IfInstID=[UINT8], NbrRtrID=[STRING], GRHelperAge=[UINT], GRHelperExitReason=[STRING]) |
|
Variable fields |
$1: OSPFv3 process ID. $2: Interface name. $3: New state of the GR helper, Normal or Helper. $4: Router ID of the local process. $5: OSPFv3 area ID. $6: Instance ID of interface. $7: Router ID of the neighbor. $8: Remaining time for the neighbor to complete GR. $9: Reason why the neighbor quits helper state. · Success—GR completes. · GracePeriodExpire—Grace period expires. · LSAChange—LSA change. · NbrReset—Neighbor restart. |
|
Severity level |
4 (Warning) |
|
Example |
OSPFV3/4/OSPFV3_NBR_GR_HELPER_STATUS: The GR helper status of OSPFv3 1’s neighbor on interface GE1/0/1 changed to Normal. (RouterID=1.1.1.1, AreaID=0.0.0.0, IfInstID=0, NbrRtrID=2.2.2.2, GRHelperAge=10, GRHelperExitReason= NbrReset) |
|
Impact |
If the neighbor's GR helper status changes and GR fails, route calculation will be affected, and services will be impacted. |
|
Cause |
The OSPFv3 neighbor enters or exits the GR helper state. |
|
Recommended action |
1. If an active/standby switchover or process restart was performed, no action is required. If this log message is generated without manual intervention, proceed to step 2. 2. Collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
PBR messages
This section contains PBR messages.
PBR_HARDWARE_BIND_ERROR
|
Message text |
Failed to apply the policy [STRING] to interface [STRING] because of [STRING].. |
|
Variable fields |
$1: Policy name. $2: Interface name. $3: Hardware processing failure reasons: · insufficient hardware resources. · unsupported operations. · insufficient hardware resources and unsupported operations. |
|
Severity level |
4 (Warning) |
|
Example |
PBR/4/PBR_HARDWARE_BIND_ERROR: Failed to apply the policy abc to interface GigabitEthernet1/0/1 because of unsupported operations. |
|
Impact |
The interface cannot use PBR to forward packets. |
|
Cause |
Unicast PBR policy failed to be configured on the interface. |
|
Recommended action |
Edit the PBR policy configuration according to the failure reason: · If hardware resources are insufficient, check PBR configuration on the device and delete unnecessary settings. · If the system does not support the operation, identify whether the PBR configuration contains the if-match or apply clauses that are not supported by the device. · If hardware resources are insufficient, and the system does not support the operation, check for unnecessary PBR settings on the device, and identify whether the PBR configuration contains unsupported clauses. |
PBR_HARDWARE_ERROR
|
Message text |
Failed to update policy [STRING] because of [STRING]. |
|
Variable fields |
$1: Policy name. $2: Hardware error reasons: · insufficient hardware resources. · unsupported operations. · insufficient hardware resources and unsupported operations. |
|
Severity level |
4 (Warning) |
|
Example |
PBR/4/PBR_HARDWARE_ERROR: Failed to update policy aaa because of insufficient hardware resources and not supported operations. |
|
Impact |
You cannot use the most recent PBR configuration to guide packet forwarding. |
|
Cause |
The device failed to update PBR configuration. |
|
Recommended action |
Modify the PBR policy configuration according to the failure reason: · If hardware resources are insufficient, check PBR configuration on the device and delete unnecessary settings. · If the system does not support the operation, identify whether the PBR configuration contains the if-match or apply clauses that are not supported by the device. · If hardware resources are insufficient, and the system does not support the operation, check for unnecessary PBR settings on the device, and identify whether the PBR configuration contains unsupported clauses. |
PBR_NEXTHOP_CHANGE
|
Message text |
Policy name=[STRING], node ID=[STRING], VPN instance=[STRING], next hop=[STRING], next hop unreachable because of [STRING]. |
|
Variable fields |
$1: Policy name. $2: Node ID. $3: VPN instance name. For the public network, this field displays public. $4: Next hop IP address. $5: Next hop change reason: · FIB information change—The FIB information changed. · track entry status change—The track entry status changed. · configuration change—The PBR configuration on the device was edited. |
|
Severity level |
4 (Warning) |
|
Example |
PBR/4/PBR_NEXTHOP_CHANGE: Policy name=a, node ID=0, VPN instance=public, next hop=1.1.1.2, next hop unreachable because of FIB information change. |
|
Impact |
Packet forwarding might fail. |
|
Cause |
The link to the next hop specified in the PBR policy became unreachable. |
|
Recommended action |
Take the action based on the reason why the next hop became unreachable: · For FIB information change, identify whether the FIB entry associated with the next hop is correct. · For track entry status change, locate the change reason and troubleshoot the associated issue. · For PBR configuration change, identify whether the edited PBR configuration meets forwarding requirements. |
PCE messages
This section contains PCE messages.
PCE_PCEP_SESSION_CHG
|
Message text |
Session ([STRING], [STRING]) is [STRING]. |
|
Variable fields |
$1: Peer address of the session. $2: VPN instance name. Value unknown indicates that the VPN instance cannot be obtained. $3: State of the session, up or down. When the state is down, this field also displays the reason for the down state error. |
|
Severity level |
3 (Error) |
|
Example |
PCE/3/PCE_PCEP_SESSION_CHG: Session (22.22.22.2, public instance) is up. PCE/3/PCE_PCEP_SESSION_CHG: Session (22.22.22.2, public instance) is down (dead timer expired). |
|
Impact |
The state of the LSP established based on the PCEP session might change, affecting service traffic forwarding. |
|
Cause |
The session state changed. Possible reasons for a down state include: · TCP connection down. · received a close message. ¡ No explanation provided. ¡ DeadTimer expired. ¡ Reception of a malformed PCEP message. ¡ Reception of an unacceptable number of unknown requests/replies. ¡ Reception of an unacceptable number of unrecognized PCEP messages. · reception of a malformed PCEP message. · internal error. · memory in critical state. · dead timer expired. · process deactivated. · remote peer unavailable/untriggered. · reception of an unacceptable number of unrecognized PCEP messages. · reception of an unacceptable number of unknown requests/replies. · PCE address changed. · initialization failed. |
|
Recommended action |
When the session state is up, no action is required. When the session state is down, verify the network and configuration according to the reason displayed. |
PFILTER
This section contains packet filtering messages.
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 version. $2: ACL number. $3: Traffic direction. $4: ACL type. $5: ACL number. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
When filtering global application messages, the called ACL rules cannot match the messages properly. |
|
Cause |
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 (Error) |
|
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. |
|
Impact |
When calling IPv4 ACL rules for global application message filtering, the default action of applying or modifying message filtering does not take effect. |
|
Cause |
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 |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
Example |
PFILTER/3/PFILTER_GLB_IPV4_DACT_UNK_ERR: Failed to apply or refresh the IPv4 default action to the inbound direction globally. |
|
Impact |
When the global application message filtering calls the IPv4 ACL rules, the default action of applying or modifying the message filtering does not take effect |
|
Cause |
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 |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When calling IPv6 ACL rules for global application message filtering, the default action for applying or modifying message filtering does not take effect |
|
Cause |
Due to insufficient hardware resources, when applying global message filtering and calling IPv6 ACL rules in a certain orientation, the default action for applying or modifying message filtering does not take effect |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
Example |
PFILTER/3/PFILTER_GLB_IPV6_DACT_UNK_ERR: Failed to apply or refresh the IPv6 default action to the inbound direction globally. |
|
Impact |
When the global application message filtering calls the IPv6 ACL rule, the default action of applying or modifying the message filtering does not take effect |
|
Cause |
Due to abnormal faults, when the global application message filtering and calling the IPv6 ACL rule in a certain orientation, the default action of applying or modifying the message filtering does not take effect |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When the global application message filtering calls the Layer 2 ACL rules, the default action of applying or modifying the message filtering does not take effect |
|
Cause |
Due to insufficient hardware resources, when the global application message filtering is applied and Layer 2 ACL rules are called in a certain direction, the default action of applying or modifying the message filtering does not take effect |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
Example |
PFILTER/3/PFILTER_GLB_MAC_DACT_UNK_ERR: Failed to apply or refresh the MAC default action to the inbound direction globally. |
|
Impact |
When the global application message filtering calls Layer 2 ACL rules, the default action of applying or modifying message filtering does not take effect |
|
Cause |
Due to abnormal faults, when the global application message filtering and Layer 2 ACL rules are called in a certain direction, the default action of applying or modifying message filtering does not take effect |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
Global application message filtering does not take effect |
|
Cause |
Due to insufficient hardware resources, the system is unable to globally apply or update an ACL rule in a certain orientation |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
Global application message filtering does not take effect |
|
Cause |
Due to the system not supporting parameters in the ACL rules, it is not possible to globally apply message filtering in a certain direction and invoke ACL rules |
|
Recommended action |
Check the ACL rules called by the message filtering and remove the unsupported parameters in the ACL rules. The specific unsupported parameters are related to the device model, please refer to the actual situation of the device |
PFILTER_GLB_UNK_ERR
|
Message text |
Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction globally. |
|
Variable fields |
$1: ACL version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. |
|
Severity level |
3 (Error) |
|
Example |
PFILTER/3/PFILTER_GLB_UNK_ERR: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction globally. |
|
Impact |
The global application message filtering does not take effect |
|
Cause |
Due to system malfunction, the message filtering and ACL invocation cannot be globally applied in a certain orientation |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying message filtering under the interface to invoke IPv4 ACL rules, the default action of applying or modifying message filtering does not take effect |
|
Cause |
Due to insufficient hardware resources, when applying message filtering and invoking IPv4 ACL rules in a certain direction of the interface, the default action of applying or modifying message filtering does not take effect |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying message filtering at the interface level and invoking IPv4 ACL rules, the default action of applying or modifying message filtering does not take effect |
|
Cause |
Due to abnormal faults, when applying message filtering and invoking IPv4 ACL rules in a certain orientation of the interface, the default action of applying or modifying message filtering does not take effect |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying IPv6 ACL rules for application message filtering under the interface, the default action of applying or modifying message filtering does not take effect |
|
Cause |
due to insufficient hardware resources, the default action of applying or modifying message filtering does not take effect when applying message filtering and invoking IPv6 ACL rules in a certain orientation of the interface |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying message filtering under the interface to invoke IPv6 ACL rules, the default action of applying or modifying message filtering does not take effect |
|
Cause |
due to abnormal faults, the default action of applying or modifying message filtering does not take effect when applying message filtering and invoking IPv6 ACL rules in a certain orientation of the interface |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying packet filtering under the interface to call Layer 2 ACL rules, the default action of applying or modifying packet filtering does not take effect |
|
Cause |
Due to insufficient hardware resources, when applying packet filtering and calling Layer 2 ACL rules in a certain direction under the interface, the default action of applying or modifying packet filtering does not take effect |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying message filtering at the interface and invoking Layer 2 ACL rules, the default action for applying or modifying message filtering does not take effect |
|
Cause |
Due to abnormal faults, when applying message filtering and invoking Layer 2 ACL rules in a certain direction at the interface, the default action for applying or modifying message filtering does not take effect |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. $5: Interface name. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
The message filtering applied under the interface is not effective |
|
Cause |
Due to insufficient hardware resources, the system is unable to apply message filtering and call ACL rules in a certain direction of the interface |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. $5: Interface name. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
The message filtering applied under the interface does not take effect |
|
Cause |
Because the system does not support the parameters in the ACL rules, it is impossible to apply message filtering and call ACL rules in a certain direction under the interface |
|
Recommended action |
Check the ACL rules called by the message filtering and delete the parameters not supported in the ACL rules. The specific parameters not supported are related to the device model, please refer to the actual situation of the device |
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 version. $2: ACL number. $3: Traffic direction. $4: Interface name. $5: ACL type. $6: ACL number. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
When filtering application messages under the interface, the called ACL rules cannot match the messages normally |
|
Cause |
If filtering application messages in a certain orientation under the interface, and calling ACL rules of IPv4, IPv6, or MAC type, and then applying message filtering or modifying global message filtering in the same orientation on the same interface, call the same type of ACL rules again |
|
Recommended action |
Please delete the same type of ACL called by the message filtering |
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 version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. $5: Interface name. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
The application message filtering under the interface does not take effect |
|
Cause |
Due to a system failure, the message filtering and ACL invocation cannot be applied in a certain orientation of the interface |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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: ACL rule ID and contents. $5: Number of packets that matched the rule. |
|
Severity level |
6 (Informational) |
|
Example |
ACL/6/PFILTER_IPV6_STATIS_INFO: Ethernet0/4/0 (inbound): Packet-filter IPv6 2000 rule 0 permit source 1:1::/64 logging 1000 packet(s). |
|
Impact |
No negative impacts on the system. |
|
Cause |
The number of packets matching the packet-filter IPv6 ACL rule changed. |
|
Recommended action |
No action is required. |
PFILTER_STATIS_INFO
|
Message text |
[STRING] ([STRING]): Packet-filter [UINT32] [STRING] [UINT64] packet(s). |
|
Variable fields |
$1: Destination to which packet filter applies. $2: Traffic direction. $3: ACL number. $4: ACL rule ID and contents. $5: Number of packets that matched the rule. |
|
Severity level |
6 (Informational) |
|
Example |
ACL/6/PFILTER_STATIS_INFO: Ethernet0/4/0 (inbound): Packet-filter 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s). |
|
Impact |
No negative impacts on the system. |
|
Cause |
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 (Error) |
|
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. |
|
Impact |
When applying VLAN for packet filtering and calling IPv4 ACL rules, the default action of applying or modifying packet filtering does not take effect |
|
Cause |
Due to insufficient hardware resources, when applying packet filtering in a certain direction of VLAN and calling IPv4 ACL rules, the default action of applying or modifying packet filtering does not take effect |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying the message filtering in VLAN and invoking IPv4 ACL rules, the default action for applying or modifying the message filtering does not take effect |
|
Cause |
Due to abnormal faults, when applying the message filtering in a certain orientation of VLAN and invoking IPv4 ACL rules, the default action for applying or modifying the message filtering does not take effect |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying IPv6 ACL rules to filter packets in VLAN, the default action of applying or modifying packet filtering does not take effect. |
|
Cause |
Due to insufficient hardware resources, when applying packet filtering and calling IPv6 ACL rules in a certain direction of VLAN, the default action of applying or modifying packet filtering does not take effect. |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying VLAN message filtering to IPv6 ACL rules, the default action for applying or modifying message filtering does not take effect |
|
Cause |
Due to abnormal faults, when applying message filtering and calling IPv6 ACL rules in a certain orientation of VLAN, the default action of applying or modifying message filtering does not take effect |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying or modifying packet filtering in VLAN using Layer 2 ACL rules, the default action of applying or modifying packet filtering does not take effect |
|
Cause |
Due to insufficient hardware resources, when applying packet filtering and calling Layer 2 ACL rules in a certain direction of VLAN, the default action of applying or modifying packet filtering does not take effect |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Error) |
|
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. |
|
Impact |
When applying Layer 2 ACL rules for packet filtering in VLAN, the default action for applying or modifying packet filtering does not take effect |
|
Cause |
Due to abnormal faults, when applying packet filtering and invoking Layer 2 ACL rules in a certain orientation of the VLAN, the default action for applying or modifying packet filtering does not take effect |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. $5: VLAN ID |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
The packet filtering applied in VLAN is not effective |
|
Cause |
Due to insufficient hardware resources, the system is unable to apply packet filtering in a certain orientation of VLAN and invoke ACL rules |
|
Recommended action |
Execute the display qos-acl resource command to check the hardware resource usage information, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. $5: VLAN ID |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
The packet filtering applied in VLAN is not effective |
|
Cause |
Due to the system not supporting the parameters in the ACL rules, it is not possible to apply packet filtering and call ACL rules in a certain direction in VLAN |
|
Recommended action |
Check the ACL rules called by the packet filtering and remove the unsupported parameters in the ACL rules. The specific unsupported parameters are device-specific, please refer to the actual situation of the device |
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 version. $2: ACL number. $3: Traffic direction. $4: VLAN ID $5: ACL type. $6: ACL number. |
|
Severity level |
3 (Error) |
|
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. |
|
Impact |
When applying packet filtering in VLAN, the called ACL rules cannot match the packet normally |
|
Cause |
If packet filtering is applied in a certain direction of VLAN and ACL rules of IPv4, IPv6, or MAC type are called, and then packet filtering or modifying global packet filtering is applied again in the same direction of the same VLAN, call the same type of ACL rules |
|
Recommended action |
Please delete the same type of ACL called by packet filtering |
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 version. $2: ACL number. $3: ACL rule ID and contents. $4: Traffic direction. $5: VLAN ID |
|
Severity level |
3 (Error) |
|
Example |
PFILTER/3/PFILTER_VLAN_UNK_ERR: Failed to apply or refresh ACL 2000 rule 1 to the inbound direction of VLAN 1. |
|
Impact |
Packet filtering not working in VLAN |
|
Cause |
Due to system malfunction, unable to apply packet filtering and call ACL in a certain orientation within VLAN |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
PIM messages
This section contains PIM messages.
CRT_PIM_SG_FAIL
|
Message text |
Failed to create the (S,G) entry in the multicast routing table. (VPNName=[STRING], ProtocolType=[STRING], SrcAddr=[STRING], GrpAddr=[STRING]) |
|
Variable fields |
$1: VPN instance name. $2: PIM mode, which is PIM-SM or PIM-DM. $3: Multicast source address. $4: Multicast group address. |
|
Severity level |
4 (Warning) |
|
Example |
PIM/4/CRT_PIM_SG_FAIL: Failed to create the (S,G) entry in the multicast routing table. (VPNName=_public_, ProtocolType=PIM-SM, SrcAddr=10.0.0.10, GrpAddr=30.0.0.10) |
|
Cause |
A (S,G) entry is created after the maximum number of (S,G) entries is already reached. |
|
Recommended action |
1. Use the display multicast global statistics command to identify whether the upper limit of (S,G) entries is too low. ¡ If yes, proceed to step 2. ¡ If no, proceed to step 3. 2. Use the multicast global limit command to increase the upper limit of (S,G) entries. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CRT_PIM_WC_FAIL
|
Message text |
Failed to create the (*,G) entry in the multicast routing table. (VPNName=[STRING], ProtocolType=[STRING], GrpAddr=[STRING]) |
|
Variable fields |
$1: VPN instance name. $2: PIM mode, which is PIM-SM or PIM-DM. $3: Multicast source address. $4: Multicast group address. |
|
Severity level |
4 (Warning) |
|
Example |
PIM/4/CRT_PIM_WC_FAIL: Failed to create the (*,G) entry in the multicast routing table. (VPNName=_public_, ProtocolType=PIM-DM, GrpAddr=10.0.0.10) |
|
Cause |
A (*,G) entry is created after the maximum number of (*,G) entries is already reached. |
|
Recommended action |
1. Use the display multicast global statistics command to identify whether the upper limit of (*,G) entries is too low. ¡ If yes, proceed to step 2. ¡ If no, proceed to step 3. 2. Use the multicast global limit command to increase the upper limit of (*,G) entries. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PIM_CHANGE_TO_NON_DR
|
Message text |
The interface is no longer a DR. (IfIndex:[UINT32], IfName:[STRING], IfAddr:[UINT32], VPNName:[STRING]). The new DR is [UINT32]. |
|
Variable fields |
$1: Interface index. $2: Interface name. $3: Interface address. $4: VPN instance name. $5: Address of the new DR. |
|
Severity level |
5 (Notification) |
|
Example |
PIM/5/PIM_CHANGE_TO_NON_DR: The interface is no longer a DR. (IfIndex:12, IfName:iftest,IfAddr:10.1.1.1, VPNName:vpntest). The new DR is 1.1.1.1. |
|
Impact |
If the multicast source-side RP changes, incorrect register messages might be received. If the multicast receiver-side RP changes, incorrect join messages might be received. |
|
Cause |
This message is generated when an interface is no longer a DR. When a device receives a hello message with a higher DR priority or the neighbor has a higher IP address, the device becomes a non-DR device. |
|
Recommended action |
If the new DR is not the expected one, configure a lower DR priority or a lower IP address for the new DR. |
PIM_DR_ELECTION
|
Message text |
The interface is elected as a DR. (IfIndex:[UINT32], IfName:[STRING], IfAddr:[STRING], VPNName:[STRING]) |
|
Variable fields |
$1: Interface index. $2: Interface name. $3: Interface address. $4: VPN instance name. |
|
Severity level |
5 (Notification) |
|
Example |
PIM/5/PIM_DR_ELECTION: The interface is elected as a DR. (IfIndex:12, IfName:iftest, IfAddr:10.1.1.1, VPNName:vpntest) |
|
Impact |
If the multicast source-side RP changes, incorrect register messages might be received. If the multicast receiver-side RP changes, incorrect join messages might be received. |
|
Cause |
The device has the highest DR priority or IP address. |
|
Recommended action |
Identify whether the elected DR is expected. · If yes, no action is required. · If no, set a lower DR priority or assign a lower IP address to the interface. |
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 |
4 (Warning) |
|
Example |
PIM/4/PIM_NBR_DOWN: Neighbor 10.1.1.1(Vlan-interface10) is down. |
|
Impact |
PIM neighbor relationship setup will fail and data forwarding will be terminated. |
|
Cause |
· The hold timer of the PIM neighbor has expired. · The interface where the PIM neighbor resides went down. · The PIM neighbor was deleted. · The device received a neighbor message with the hold time as 0. · The BFD session of the neighbor went down. |
|
Recommended action |
1. Use the display this command to identify whether the pim neighbor-policy or ipv6 pim neighbor-policy command is executed on the interface. ¡ If yes, go to step 2. ¡ If no, go to step 3. 2. Use the display acl or display acl ipv6 command to identify whether the neighbor is permitted by the ACL. ¡ If yes, go to step 3. ¡ If no, reconfigure the ACL to permit the neighbor. 3. Use the display interface command on the local device and the neighbor device to identify the physical state of the interface. ¡ If the physical state is Administratively DOWN, execute the undo shutdown command. ¡ If the physical state is Down, check the physical connection (including whether the network cable and transceiver module are loose or disconnected), and reconnect the physical connection. ¡ If the physical state is Up, go to step 4. 4. Use the display ip interface or display ipv6 interface command on the local device and the neighbor device to identify the protocol state of the interface. ¡ If the protocol state is Up, go to step 5. ¡ If the protocol state is Down, use the ip address or ipv6 address command to assign an IP address to the interface. 5. Use the display this command on the local device and the neighbor device to identify whether the interface is enabled with PIM SM or IPv6 PIM SM. ¡ If yes, go to step 6. ¡ If no, execute the pim sm or ipv6 pim sm command on the interface. 6. Use the display current-configuration command on the local device and the neighbor device to identify whether the VPN instance is enabled with multicast routing or IPv6 multicast routing. ¡ If yes, go to step 7. ¡ If no, execute the multicast routing or ipv6 multicast routing command on the interface. 7. Use the display memory command on the local device and the neighbor device to identify the memory usage. ¡ If the memory is insufficient, address the memory issue. ¡ If the memory is sufficient, go to step 8. 8. Use the ping or ping ipv6 command on the local device to test the connectivity with the neighbor device. ¡ If the ping succeeds, go to step 10. ¡ If the ping fails, go to step 9. 9. Use the display ip routing-table or display ipv6 routing-table command on the local device and the neighbor device to identify the unicast routes to each other are normal. ¡ If the unicast routes are normal, go to step 10. ¡ If the unicast routes are abnormal, address the route issues. 10. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 |
4 (Warning) |
|
Example |
PIM/4/PIM_NBR_UP: Neighbor 10.1.1.1(Vlan-interface10) is up. |
|
Impact |
No negative impact on the system. |
|
Cause |
A PIM interface received a hello packet and a PIM neighbor was created. |
|
Recommended action |
No action is required. |
PIM_ROUTE_EXCEED_ACTIVE
|
Message text |
The number of existed routing entries exceeded the global upper limit.(LimitType=[UINT32], AddressFamily=[STRING], CurrentCount=[UINT32], LimitCount=[UINT32],SrcAddr=[STRING], GrpAddr=[STRING], InstanceName=[STRING], ReasonType=[STRING]) |
|
Variable fields |
$1: PIM entry type: ¡ PIM-SM (*, G) entry ¡ PIM-SM (S, G) entry ¡ PIM-DM (*, G) entry ¡ PIM-DM (S, G) entry $2: Address family. $3: Current number of global PIM entries. $4: Maximum number of global PIM entries allowed. $5: Multicast source address. $6: Multicast group address. $7: VPN instance name. $8: Alarm reason, for example, entry change or configuration change. |
|
Severity level |
4 (Warning) |
|
Example |
PIM/4/PIM_ROUTE_EXCEED_active: The number of existed routing entries exceeded the global upper limit. (LimitType=PIM-DM, AddressFamily=ipv6, CurrentCount=100, LimitCount=100,SrcAddr=10.0.0.10, GrpAddr=30.0.0.10, InstanceName=_public_, ReasonType=Entry added) |
|
Impact |
New entries cannot be created. |
|
Cause |
The number of global PIM entries reaches the maximum number of global PIM entries allowed. |
|
Recommended action |
1. Use the display multicast global statistics command to identify whether the maximum number of global PIM entries allowed is too low. ¡ If yes, proceed to step 2. ¡ If no, proceed to step 3. 2. Use the multicast global limit command to increase the maximum number of global PIM entries allowed. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PIM_ROUTE_EXCEED_CLEAR
|
Message text |
The number of existed routing entries falls below the global upper limit.(LimitType=[UINT32], AddressFamily=[STRING], CurrentCount=[UINT32], LimitCount=[UINT32,SrcAddr=[STRING], GrpAddr=[STRING], InstanceName=[STRING], ReasonType=[STRING]) |
|
Variable fields |
$1: PIM entry type: ¡ PIM-SM (*, G) entry ¡ PIM-SM (S, G) entry ¡ PIM-DM (*, G) entry ¡ PIM-DM (S, G) entry $2: Address family. $3: Current number of global PIM entries. $4: Maximum number of global PIM entries allowed. $5: Multicast source address. $6: Multicast group address. $7: VPN instance name. $8: Alarm reason, for example, entry change or configuration change. |
|
Severity level |
5 (Notification) |
|
Example |
PIM/5/PIM_ROUTE_EXCEED_clear: The number of existed routing entries falls below the global upper limit.(LimitType=PIM-DM, AddressFamily=ipv6, CurrentCount=100, LimitCount=100,SrcAddr=10.0.0.10, GrpAddr=30.0.0.10, InstanceName=_public_, ReasonType=Entry deleted) |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of global PIM entries falls below the maximum number of global PIM entries allowed. |
|
Recommended action |
No action is required. |
PIM_ROUTE_THRESHOLD_ACTIVE
|
Message text |
The number of existed routing entries exceeded the global upper threshold.(LimitType=[UINT32], AddressFamily=[STRING], CurrentCount=[UINT32], LimitCount=[UINT32], ThresholdCount=[UINT32], ReasonType=[STRING]) |
|
Variable fields |
$1: LimitType: PIM entry type. ¡ PIM-SM (*, G) entry ¡ PIM-SM (S, G) entry ¡ PIM-DM (*, G) entry ¡ PIM-DM (S, G) entry $2: Address family: IPv4 or IPv6. $3: Current number of global PIM entries. $4: Maximum number of global PIM entries allowed. $5: Upper limit of global PIM entries that causes a log message to be generated. $6: Alarm reason, for example, entry change or configuration change. |
|
Severity level |
4 (Warning) |
|
Example |
PIM/5/PIM_ROUTE_THRESHOLD_CLEAR: The number of existed routing entries falls below the global lower threshold.(LimitType=PIM-SM, AddressFamily=ipv6, CurrentCount=59, LimitCount=100, ThresholdCount=60, ReasonType=Entry deleted. |
|
Impact |
New entries might fail to be created. |
|
Cause |
The ratio of the number of global PIM entries to the maximum number of global PIM entries allowed reaches the upper limit. |
|
Recommended action |
1. Use the display multicast global statistics command to identify whether the upper limit of global PIM entries is too low. ¡ If yes, go to step 2. ¡ If no, go to step 3. 2. Use the multicast global limit command to increase the upper limit of global PIM entries. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PIM_ROUTE_THRESHOLD_CLEAR
|
Message text |
The number of existed routing entries falls below the global lower threshold.(LimitType=[UINT32], AddressFamily=[STRING], CurrentCount=[UINT32], LimitCount=[UINT32], ThresholdCount=[UINT32], ReasonType=[STRING]). |
|
Variable fields |
$1: LimitType: PIM entry type. ¡ PIM-SM (*, G) entry ¡ PIM-SM (S, G) entry ¡ PIM-DM (*, G) entry ¡ PIM-DM (S, G) entry $2: Address family: IPv4 or IPv6. $3: Current number of global PIM entries. $4: Maximum number of global PIM entries allowed. $5: Lower limit of global PIM entries that causes a log message to be generated. $6: Alarm reason, for example, entry change or configuration change. |
|
Severity level |
5 (Notification) |
|
Example |
PIM/4/PIM_ROUTE_THRESHOLD_ACTIVE: The number of existed routing entries exceeded the global upper threshold.(LimitType=PIM-SM, AddressFamily=ipv6, CurrentCount=80, LimitCount=100, ThresholdCount=80, ReasonType=Entry added) |
|
Impact |
No negative impact on the system. |
|
Cause |
The ratio of the number of global PIM entries to the maximum number of global PIM entries allowed falls below the lower limit. |
|
Recommended action |
No action is required. |
PIM_RP_CHANGED
|
Message text |
The RP changes. (RPType:[STRING], GrpAddr:[STRING], GrpPfxLen:[UINT32], RPAddr:[STRING], PimMode:[STRING], Priority:[UINT32], VPNName:[STRING]) |
|
Variable fields |
$1: RP type: ¡ static-rp ¡ auto-rp ¡ bsr-rp ¡ embedded $2: Multicast group address. $3: Mask length for the multicast group address. $4: Address of the new RP. $5: Current PIM mode: PIM-SM or Bidir-PIM $6: RP priority. $7: VPN instance name. |
|
Severity level |
5 (Notification) |
|
Example |
PIM/5/PIM_RP_CHANGED: The RP changes. (RPType:static-rp, GrpAddr:224.0.0.0, GrpPfxLen:4, RPAddr:10.1.1.1, PimMode:PIM-SM, Priority:64, VPNName:vpntest) |
|
Impact |
The multicast source and multicast receivers cannot communicate, affecting multicast services. |
|
Cause |
The RP configuration changed, the old RP failed, or a new RP was added. |
|
Recommended action |
Identify whether the RP change is expected. · If no, configure the current device as a static RP or increase the RP priority so that it can be elected as again. · If yes, no action is required. |
PING messages
This section contains ping messages.
PING6_SRV6_STATISTICS
|
Message text |
Ping6 SRv6 statistics: [UINT32] packet(s) transmitted, [UINT32] packet(s) received, [DOUBLE]% packet loss. |
|
Variable fields |
$1: Number of sent echo requests. $2: Number of received echo replies. $3: Percentage of the non-replied packets to the total request packets. |
|
Severity level |
6 (Informational) |
|
Example |
PING/6/PING6_SRV6_STATISTICS: Ping6 SRv6 statistics: 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss. |
|
Impact |
No negative impact on the system. |
|
Cause |
The ping ipv6-sid command is executed to verify SRv6 forwarding path connectivity. |
|
Recommended action |
· If the packet loss rate in the statistics is 0, it indicates normal communication, and no action is required. · If the packet loss rate is greater than 0 but less than 100%, packet loss has occurred. The reason might be unstable links or sudden traffic congesting the bandwidth. Perform the following tasks: ¡ Execute the display interface command to check the interface status. If the interface status changes frequently between up and down, it might be a cable fault or an issue with interface components. Please further identify and resolve the issue. ¡ Execute the display counter command to display packet rate statistics for interfaces that are up during the last statistics collection period. If there is a significant increase in traffic, burst traffic might exist. You can capture or mirror the traffic for analysis and set ACLs to filter unauthorized traffic. · If the packet loss rate in the statistics is 100%, check the route and SID information of each device on the SRv6 forwarding path. For more information about SRv6, see “Configuring SRv6" in Segment Routing Configuration Guide. · If the packet loss rate is 100%, perform the following tasks: ¡ Execute the display interface command to identify whether the interface is down. If the interface is down, follow the prompts in the output to troubleshoot the issue. · Execute the display ipv6 routing-table command to check the public network routing table for routes to the destination. If there are no routes, manually add a route or introduce it through a dynamic routing protocol. |
PING_STATISTICS
|
Message text |
[STRING] statistics for [STRING]: [UINT32] packet(s) transmitted, [UINT32] packet(s) 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 (Informational) |
|
Example |
PING/6/PING_STATISTICS: Ping statistics for 1.1.1.2: 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss, round-trip min/avg/max/std-dev = 0.000/0.600/2.000/0.800 ms. |
|
Impact |
No negative impact on the system. |
|
Cause |
A user uses the ping command to identify whether a destination in the public network is reachable. |
|
Recommended action |
· If the packet loss rate in the statistics is 0, it indicates normal communication, and no action is required. · If the packet loss rate is greater than 0 but less than 100%, packet loss has occurred. The reason might be unstable links or sudden traffic congesting the bandwidth. Perform the following tasks: ¡ Execute the display interface command to check the interface status. If the interface status changes frequently between up and down, it might be a cable fault or an issue with interface components. Please further identify and resolve the issue. ¡ Execute the display counter command to display packet rate statistics for interfaces that are up during the last statistics collection period. If there is a significant increase in traffic, burst traffic might exist. You can capture or mirror the traffic for analysis and set ACLs to filter unauthorized traffic. · If the packet loss rate is 100%, perform the following tasks: ¡ Execute the display interface command to identify whether the interface is down. If the interface is down, follow the prompts in the output to troubleshoot the issue. ¡ Execute the display routing-table or display ipv6 routing-table command to check the public network routing table for routes to the destination. If there are no routes, manually add a route or introduce it through a dynamic routing protocol. |
PING_VPN_STATISTICS
|
Message text |
[STRING] statistics for [STRING] in VPN instance [STRING] [UINT32] packet(s) transmitted, [UINT32] packet(s) 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 (Informational) |
|
Example |
PING/6/PING_VPN_STATISTICS: Ping statistics for 192.168.0.115 in VPN instance vpn1: 5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss, round-trip min/avg/max/std-dev = 0.000/0.800/2.000/0.748 ms. |
|
Impact |
No negative impact on the system. |
|
Cause |
A user uses the ping command to identify whether a destination in a private network is reachable. |
|
Recommended action |
· If the packet loss rate in the statistics is 0, it indicates normal communication, and no action is required. · If the packet loss rate is greater than 0 but less than 100%, packet loss has occurred. The reason might be unstable links or sudden traffic congesting the bandwidth. Perform the following tasks: ¡ Execute the display interface command to check the interface status. If the interface status changes frequently between up and down, it might be a cable fault or an issue with interface components. Please further identify and resolve the issue. ¡ Execute the display counter command to display packet rate statistics for interfaces that are up during the last statistics collection period. If there is a significant increase in traffic, burst traffic might exist. You can capture or mirror the traffic for analysis and set ACLs to filter unauthorized traffic. · If the packet loss rate is 100%, perform the following tasks: ¡ Execute the display interface command to identify whether the interface is down. If the interface is down, follow the prompts in the output to troubleshoot the issue. ¡ Execute the display routing-table or display ipv6 routing-table command with the vpn keyword specified to check the VPN routing table for routes to the destination. If there are no routes, manually add a route or introduce it through a dynamic routing protocol. |
PKG messages
This section contains package management messages.
PKG_VERSION_CONSISTENT
|
Message text |
Pattern 1: Software images on slot [STRING] are not consistent with those on the active MPU. The slot will reboot to reload the images of the active MPU. Pattern 2: Software images on chassis [STRING] slot [STRING] are not consistent with those on the local active MPU. The slot will reboot to reload the images of the local active MPU. |
|
Variable fields |
Pattern 1: $1: Slot number. Pattern 2: $1: Chassis number. $2: Slot number. |
|
Severity level |
5 (Notification) |
|
Example |
Pattern 1: PKG/5/PKG_VERSION_CONSISTENT: Software images on slot 2 are not consistent with those on the active MPU. The slot will reboot to reload the images of the active MPU. Pattern 2: PKG/5/PKG_VERSION_CONSISTENT: Software images on chassis 2 slot 2 are not consistent with those on the local active MPU. The slot will reboot to reload the images of the local active MPU. |
|
Impact |
Service cards were rebooted. |
|
Cause |
If you perform an installation, uninstallation, or upgrade operation when a card is being started, the results of the operation cannot be synchronized to that card. As a result, the card runs different software images than the active MPU after it completes startup. The system will restart the card to load the new software images from the active MPU. Before the system restarts the card, it prints this log. |
|
Recommended action |
Use the display system stable command to verify that the system is stable before you perform an installation, uninstallation, or upgrade operation. If the System State field displays Stable, the system is stable. |
PKG_VERSION_VM_CONSISTENT
|
Message text |
Software images of [STRING] on slot [STRING] are inconsistent with those on the other [STRING]. |
|
Variable fields |
$1: VM type: CTRL-VM, FWD-VM, or BRAS-VM. $2: Slot number. $3: VM type: CTRL-VM, FWD-VM, or BRAS-VM. |
|
Severity level |
5 (Notification) |
|
Example |
PKG/5/PKG_VERSION_ VM_INCONSISTENT: Software images of BRAS-VM on slot 66 are inconsistent with those on the other BRAS-VM. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated if a newly online VM runs a different software version than an existing VM of the same type in the vBRAS-CP. |
|
Recommended action |
Upgrade the software version of the new VM. |
PKI messages
This section contains PKI messages.
PKI_CA_CERT_INVALID
|
Message text |
CA certificate is invalid. Issuer: [STRING]; Subject: [STRING]; Not before: [STRING]; Not after: [STRING]. |
|
Variable fields |
$1: Issuer of the CA certificate. $2: Subject of the CA certificate. $3: Time when the CA certificate becomes valid. $4: Time when the CA certificate expires. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_CA_CERT_INVALID: CA certificate is invalid, Issuer: C=cn, O=docm, OU=rnd, CN=rootca; Subject: C=cn, O=ccc, OU=ppp, CN=rootca; Not before: 2021-06-28T03:27:46; Not after: 2022-06-29T03:20:34. |
|
Impact |
The certificate-related service features are unavailable. |
|
Cause |
· The device time and the CA server time are not synchronized. · The fingerprint used to verify the CA root certificate is incorrect. · Invalid CA certificate format. · In FIPS mode, the signature algorithm and public key length of the CA certificate do not meet the requirements. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Check if the fingerprint used to verify the CA root certificate is correct. ¡ If not, configure a correct fingerprint by using the root-certificate fingerprint command. ¡ If yes, proceed to step 3. 3. Apply for a new CA certificate by either submitting an online request or importing the CA certificate offline. If the alarm still persists, execute step 4. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_CA_CERT_VALID
|
Message text |
CA certificate is valid. Issuer: [STRING]; Subject: [STRING]; Not before: [STRING]; Not after: [STRING]. |
|
Variable fields |
$1: Issuer of the CA certificate. $2: Subject of the CA certificate. $3: Time when the CA certificate becomes valid. $4: Time when the CA certificate expires. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_CA_CERT_VALID: CA certificate is valid, Issuer: C=cn, O=docm, OU=rnd, CN=rootca; Subject: C=cn, O=ccc, OU=ppp, CN=rootca; Not before: 2021-06-28T03:27:46; Not after: 2022-06-29T03:20:34. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device verifies that the CA certificate is valid. |
|
Recommended action |
No action is required. |
PKI_CRL_INVALID
|
Message text |
CRL is invalid. Issuer: [STRING]; Not before: [STRING]; Not after: [STRING]. |
|
Variable fields |
$1: Issuer of the CRL. $2: Time when the CRL becomes valid. $3: Time when the CRL expires. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_CRL_INVALID: CRL is invalid, Issuer: /C=cn/O=docm/OU=sec/CN=therootca; Not before: 2021-06-28T03:27:46; Not after: 2022-06-29T03:20:34. |
|
Impact |
The certificate-related service features are unavailable. |
|
Cause |
· The device time and the CA server time are not synchronized. · The public key of the CA certificate fails to verify the CRL. · In FIPS mode, the CRL signature algorithm does not meet the requirements. |
|
Recommended action |
Obtain a new CRL. |
PKI_CRL_VALID
|
Message text |
CRL is valid. Issuer: [STRING]; Not before: [STRING]; Not after: [STRING]. |
|
Variable fields |
$1: Issuer of the CRL. $2: Time when the CRL becomes valid. $3: Time when the CRL expires. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_CRL_VALID: CRL is valid, Issuer: /C=cn/O=docm/OU=sec/CN=therootca; Not before: 2021-06-28T03:27:46; Not after: 2022-06-29T03:20:34. |
|
Impact |
No negative impact on the system. |
|
Cause |
After CRL checking is enabled, the device verifies that the obtained CRL is valid. |
|
Recommended action |
No action is required. |
PKI_GET_CRL_FAIL_HTTP
|
Message text |
Failed to obtain CRL through the HTTP protocol. Domain name: [STRING]; URL path of CRL: [STRING]; VPN instance name: [STRING]. |
|
Variable fields |
$1: PKI domain name. $2: URL of the CRL. $3: VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_GET_CRL_FAIL_HTTP: Failed to obtain CRL through the HTTP protocol, Domain name: abc; URL path of CRL: http://169.254.0.1/certsrv/mscep/mscep.dll; VPN instance name: abc. |
|
Impact |
· If the system does not have a CRL, the certificate-related services will be unavailable. · After the CRL expires, the certificate-related services become unavailable. |
|
Cause |
· The device time and the HTTP server time are not synchronized. · The device and the HTTP server cannot reach each other. · The CA server did not issue a CRL. · The CRL repository is set incorrectly. · The HTTP server is not functioning properly. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Use ping to test whether the device and the HTTP server can reach each other. ¡ If not, check the route and physical link to ensure connectivity between them. ¡ If yes, proceed to step 3. 3. Check if the CA server has issued a CRL. ¡ If not, issue the CRL on the CA. ¡ If yes, proceed to step 4. 4. Check if the CRL repository is set correctly: ¡ If not, use crl url to configure it correctly. ¡ If yes, proceed to step 5. 5. Check if the HTTP server is functioning correctly. ¡ If not, make sure the HTTP server is functioning correctly. ¡ If yes, proceed to step 6. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_GET_CRL_FAIL_LDAP
|
Message text |
Failed to obtain CRL through the LDAP protocol. Domain name: [STRING]; URL path of CRL: [STRING]; VPN instance name: [STRING]. |
|
Variable fields |
$1: PKI domain name. $2: URL of the CRL . $3: VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_GET_CRL_FAIL_LDAP: Failed to obtain CRL through the LDAP protocol, Domain name: abc; URL path of CRL: http://169.254.0.1/certsrv/mscep/mscep.dll; VPN instance name: abc. |
|
Impact |
· If the system does not have a CRL, the certificate-related services will be unavailable. · After the CRL expires, the certificate-related services become unavailable. |
|
Cause |
· The device time and the LDAP server time are not synchronized. · The device and the LDAP server cannot reach each other. · The CA server did not issue a CRL. · The CRL repository is set incorrectly. · The CRL repository URL does not contain the host name, and the LDAP server address is not configured in the PKI domain either. · The LDAP server is not functioning properly. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Use ping to test whether the device and the LDAP server are reachable to each other. ¡ If not, check the route and physical link to ensure connectivity between them. ¡ If yes, proceed to step 3. 3. Check if the CA server has issued a CRL. ¡ If not, issue the CRL on the CA. ¡ If yes, proceed to step 4. 4. Check if the CRL repository is set correctly: ¡ If not, use crl url to configure it correctly. ¡ If yes, proceed to step 5. 5. If the CRL repository URL does not contain the host name, check whether the LDAP server address is configured in the PKI domain and whether it is set correctly. ¡ If the LDAP server address is not set or set incorrectly, use the ldap-server command to configure it. ¡ If the LDAP server address is set correctly, proceed to step 6. 6. Check if the LDAP server is functioning correctly. ¡ If not, make sure the LDAP server is functioning correctly. ¡ If yes, proceed to step 7. 7. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_GET_CRL_FAIL_SCEP
|
Message text |
Failed to obtain CRL through the SCEP protocol. Domain name: [STRING]; URL path of certificate: [STRING]; VPN instance name: [STRING]. |
|
Variable fields |
$1: PKI domain name. $2: URL of the certificate. $3: VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_GET_CRL_FAIL_SCEP: Failed to obtain CRL through the SCEP protocol, Domain name: abc; URL path of certificate: http://4.4.4.1:8080/certsrv/mscep/mscep.dll; VPN instance name: abc. |
|
Impact |
· If the system does not have a CRL, the certificate-related services will be unavailable. · After the CRL expires, the certificate-related services become unavailable. |
|
Cause |
· The device time and the CA server time are not synchronized. · The device and the CA server cannot reach each other. · Obtain the local certificate and key pair before retrieving the CRL. · The designated acceptance agency is either not set or set incorrectly. · The source IP address of the PKI protocol message from the unspecified CA server is either not specified or incorrect. · The CA server is not functioning properly. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Use ping to test whether the device and the CA server can reach each other. ¡ If not, check the route and physical link to ensure connectivity between them. ¡ If yes, proceed to step 3. 3. Check if the local certificate and corresponding key pair have been obtained. ¡ If not, request a new local certificate online or import it offline, and obtain the corresponding key pair. ¡ If yes, proceed to step 4. 4. Check if the certificate request reception authority is set and set correctly. ¡ If not, use certificate request from to configure it correctly. ¡ If yes, proceed to step 5. 5. Check if the correct source IP address for PKI protocol packets is specified on the CA server. ¡ If not, contact the CA server administrator to configure the correct source IP address by using the source command. ¡ If yes, proceed to step 6. 6. Check if the CA server is functioning correctly. ¡ If not, make sure the CA server is functioning correctly. ¡ If yes, proceed to step 7. 7. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_GET_CRL_SUCCESS_HTTP
|
Message text |
CRL was successfully obtained through the HTTP protocol. Domain name: [STRING]; URL path of CRL: [STRING]; VPN instance name: [STRING]. |
|
Variable fields |
$1: PKI domain name. $2: URL of the CRL. $3: VPN instance name. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_GET_CRL_SUCCESS_HTTP: CRL is successfully obtained through the HTTP protocol, Domain name: abc; URL path of CRL: http://169.254.0.1/certsrv/mscep/mscep.dll; VPN instance name: abc. |
|
Impact |
No negative impact on the system. |
|
Cause |
Successfully obtained the CRL through the HTTP protocol. |
|
Recommended action |
No action is required. |
PKI_GET_CRL_SUCCESS_LDAP
|
Message text |
CRL was successfully obtained through the LDAP protocol. Domain name: [STRING]; URL path of CRL: [STRING]; VPN instance name: [STRING]. |
|
Variable fields |
$1: PKI domain name. $2: URL of the CRL. $3: VPN instance name. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_GET_CRL_SUCCESS_LDAP: CRL is successfully obtained through the LDAP protocol. Domain name: abc; URL path of CRL: http://169.254.0.1/certsrv/mscep/mscep.dll; VPN instance name: abc. |
|
Impact |
No negative impact on the system. |
|
Cause |
Obtained the CRL successfully through the LDAP protocol. |
|
Recommended action |
No action is required. |
PKI_GET_CRL_SUCCESS_SCEP
|
Message text |
CRL was successfully obtained through the SCEP protocol. Domain name: [STRING]; URL path of certificate: [STRING]; VPN instance name: [STRING]. |
|
Variable fields |
$1: PKI domain name. $2: URL of the certificate. $3: VPN instance name. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_GET_CRL_SUCCESS_SCEP: CRL is successfully obtained through the SCEP protocol, Domain name: abc; URL path of certificate: http://4.4.4.1:8080/certsrv/mscep/mscep.dll; VPN instance name: abc. |
|
Impact |
No negative impact on the system. |
|
Cause |
Obtained the CRL successfully through the SCEP protocol. |
|
Recommended action |
No action is required. |
PKI_LOCAL_CERT_HAS_EXPIRED
|
Message text |
Local [STRING] certificate in domain [STRING] has expired for [UINT64] days. |
|
Variable fields |
$1: Functions of the local certificate: · General—For both encryption and signature. · Signature—For signature. · Encryption—For encryption. $2: PKI domain name. $3: Period of time for which the local certificate has expired. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_LOCAL_CERT_HAS_EXPIRED: Local general certificate in domain abc has expired for 2 days. |
|
Impact |
The certificate-related service features are unavailable. |
|
Cause |
· The device time and the CA server time are not synchronized. · The certificate's expiration time is later than the current device time. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Apply for a new certificate online using the SCEP/LDAP protocol, or apply for a new certificate offline. If the alarm persists, proceed to step 3. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_LOCAL_CERT_INVALID
|
Message text |
Local certificate is invalid. Domain name: [STRING]; Issuer: [STRING]; Subject: [STRING]; Not before: [STRING]; Not after: [STRING]. |
|
Variable fields |
$1: PKI domain name. $2: Issuer of the local certificate. $3: Subject of the local certificate. $4: Time when the local certificate becomes valid. $5: Time when the local certificate expires. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_LOCAL_CERT_INVALID: Local certificate is invalid, Domain name:abc; Issuer: C=CN, O=sec, OU=software, CN=abdfdc; Subject: O=OpenCA Labs, OU=Users, CN=abcde abcde-sec; Not before: 2021-06-28T03:27:46; Not after: 2022-06-29T03:20:34. |
|
Impact |
The certificate-related service features are unavailable. |
|
Cause |
· The device time and the CA server time are not synchronized. · The public key of the CA certificate failed to verify the local certificate. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Apply for a new certificate online using the SCEP/LDAP protocol, or apply for a new certificate offline. If the alarm persists, proceed to step 3. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_LOCAL_CERT_VALID
|
Message text |
Local certificate is valid. Domain name: [STRING]; Issuer: [STRING]; Subject: [STRING]; Not before: [STRING]; Not after: [STRING]. |
|
Variable fields |
$1: PKI domain name. $2: Issuer of the local certificate. $3: Subject of the local certificate. $4: Time when the local certificate becomes valid. $5: Time when the local certificate expires. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_LOCAL_CERT_VALID: Local certificate is valid, Domain name:abc; Issuer: C=CN, O=sec, OU=software, CN=abdfdc; Subject: O=OpenCA Labs, OU=Users, CN=abcde abcde-sec; Not before: 2021-06-28T03:27:46; Not after: 2022-06-29T03:20:34. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device verifies that the obtained local certificate is valid. |
|
Recommended action |
No action is required. |
PKI_LOCAL_CERT_WILL_EXPIRED
|
Message text |
Local [STRING] certificate in domain [STRING] will expire in [UINT64] days. |
|
Variable fields |
$1: Functions of the local certificate: · General—For both encryption and signature. · Signature—For signature. · Encryption—For encryption. $2: PKI domain name. $3: Remaining validity period of the certificate. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_LOCAL_CERT_WILL_EXPIRED: Local general certificate in domain abc will expire in 2 days. |
|
Impact |
After the local certificate expires, the certificate-related services become unavailable. |
|
Cause |
· The device time and the CA server time are not synchronized. · The current device time is within 30 days (including 30 days) before the certificate expiration date. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Apply for a new certificate online using the SCEP/LDAP protocol, or apply for a new certificate offline. If the alarm persists, proceed to step 3. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_REQUEST_LOCAL_CERT_FAIL_LDAP
|
Message text |
Failed to request [STRING] certificate of domain [STRING] through the LDAP protocol. VPN instance name: [STRING]; URL path of certificate: [STRING]; Entity name: [STRING]; Saved certificate file name: [STRING]. |
|
Variable fields |
$1: Functions of the local certificate: · General—For both encryption and signature. · Signature—For signature. · Encryption—For encryption. $2: PKI domain name. $3: VPN instance name. $4: URL of the certificate. $5: PKI entity name. $6: Saved certificate file name. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_REQUEST_LOCAL_CERT_FAIL_LDAP: Failed to request [STRING] certificate of domain abc through the LDAP protocol. VPN instance name: abc;URL path of certificate: ldap://1.1.2.22:389/CN=mycert; Entity name: abc; Saved certificate file name: lo-8f14e45fceea167a5a36dedd4bea2543-1.cer. |
|
Impact |
· If the system does not have a certificate, the certificate-related services will be unavailable. · After the certificate expires, the certificate-related services become unavailable. |
|
Cause |
· The device time and the CA server time are not synchronized. · The device and the LDAP server cannot reach each other. · The LDAP server is not functioning properly. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Use ping to test whether the device and the LDAP server are reachable to each other. ¡ If not, check the route and physical link to ensure connectivity between them. ¡ If yes, proceed to step 2. 3. Check if the LDAP server is operating properly. ¡ If not, make sure the LDAP server is functioning correctly. ¡ If yes, proceed to step 4. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_REQUEST_LOCAL_CERT_FAIL_SCEP
|
Message text |
Failed to request [STRING] certificate of domain [STRING] through the SCEP protocol. URL path of certificate: [STRING]; Saved certificate file name: [STRING]. |
|
Variable fields |
$1: Functions of the local certificate: · General—For both encryption and signature. · Signature—For signature. · Encryption—For encryption. $2: PKI domain name. $3: URL of the certificate. $4: Saved certificate file name. |
|
Severity level |
4 (Warning) |
|
Example |
PKI/4/PKI_REQUEST_LOCAL_CERT_FAIL_SCEP: Failed to request general certificate of domain abc through the SCEP protocol, URL path of certificate: http://4.4.4.1:8080/certsrv/mscep/mscep.dll; Saved certificate file name: lo-8f14e45fceea167a5a36dedd4bea2543-1.cer. |
|
Impact |
· If the system does not have a certificate, the certificate-related services will be unavailable. · After the certificate expires, the certificate-related services become unavailable. |
|
Cause |
· The device time and the CA server time are not synchronized. · The device and the CA server cannot reach each other. · The key pair specified in the PKI domain does not match the obtained local certificate. · The URL of the certificate request reception authority is configured incorrectly in the PKI domain. · The CA server is not functioning properly. |
|
Recommended action |
1. Execute the display clock command to check if the device time is correct. ¡ If not, use clock datetime in user view to change the device time. ¡ If yes, proceed to step 2. 2. Use ping to test whether the device and the CA server are reachable to each other. ¡ If not, check the route and physical link to ensure connectivity between them. ¡ If yes, proceed to step 3. 3. Check if the correct key pair is specified in the PKI domain. ¡ If not, use the public-key command to specify the key pair and ensure it matches the local certificate to be obtained. ¡ If yes, proceed to step 4. 4. Check if the correct URL for the certificate request reception authority is specified in the PKI domain. ¡ If not, use the certificate request url command to specify the correct URL. ¡ If yes, proceed to step 5. 5. Check if the CA server is operating properly. ¡ If not, make sure the CA server is functioning correctly. ¡ If yes, proceed to step 6. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKI_REQUEST_LOCAL_CERT_SUCCESS_LDAP
|
Message text |
Requested [STRING] certificate of domain [STRING] successfully through LDAP. VPN instance name: [STRING];URL path of certificate: [STRING]; Entity name: [STRING]; Saved certificate file name: [STRING]. |
|
Variable fields |
$1: Functions of the local certificate: · General—For both encryption and signature. · Signature—For signature. · Encryption—For encryption. $2: PKI domain name. $3: VPN instance name. $4: URL of the certificate. $5: PKI entity name. $6: Saved certificate file name. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_REQUEST_LOCAL_CERT_SUCCESS_LDAP: Requested general certificate of domain abc successfully through LDAP. VPN instance name: abc;URL path of certificate: ldap://1.1.2.22:389/CN=mycert; Entity name: abc; Saved certificate file name: lo-8f14e45fceea167a5a36dedd4bea2543-1.cer. |
|
Impact |
No negative impact on the system. |
|
Cause |
Requested a local certificate for the PKI domain successfully through LDAP. |
|
Recommended action |
No action is required. |
PKI_REQUEST_LOCAL_CERT_SUCCESS_SCEP
|
Message text |
Requested [STRING] certificate of domain [STRING] successfully through SCEP. URL path of certificate: [STRING]; Saved certificate file name: [STRING]. |
|
Variable fields |
$1: Functions of the local certificate: · General—For both encryption and signature. · Signature—For signature. · Encryption—For encryption. $2: PKI domain name. $3: URL path of the certificate. $4: Saved certificate file name. |
|
Severity level |
5 (Notification) |
|
Example |
PKI/5/PKI_REQUEST_LOCAL_CERT_SUCCESS_SCEP: Requested general certificate of domain abc successfully through SCEP, URL path of certificate: http://4.4.4.1:8080/certsrv/mscep/mscep.dll; Saved certificate file name: lo-8f14e45fceea167a5a36dedd4bea2543-1.cer. |
|
Impact |
No negative impact on the system. |
|
Cause |
Requested a local certificate for the PKI domain successfully through SCEP. |
|
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 (Warning) |
|
Example |
PKT2CPU/4/PKT2CPU_NO_RESOURCE: -Interface=Ethernet0/0/2-ProtocolType=21-MacAddr=0180-c200-0014; The resources are insufficient. |
|
Impact |
The service processing capability is affected, because the hardware resources are insufficient. |
|
Cause |
This message is generated when the hardware resources were insufficient. |
|
Recommended action |
1. Cancel the configuration that is not needed. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
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 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_AP_OFFLINE: Failed to start packet capture. Reason: AP was offline. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packet capture failed to start because the AP configured with packet capture was offline. |
|
Recommended action |
Execute the display wlan ap all command to check the state of the AP. If the State field displays R, R/M, or R/B, it means that the AP is online and running stably, and the packet capture feature can be enabled. |
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 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_AREADY_EXIT: Failed to start packet capture. Reason: The AP was uploading frames captured during the previous capturing operation. |
|
Impact |
No negative impact on the system. |
|
Cause |
When packet capture is stopped on the AC, the fit AP might be still uploading the captured frames. This message is generated when the user restarted packet capture at that time. |
|
Recommended action |
Restart packet capture later. |
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 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_CONN_FAIL: Failed to start packet capture. Reason: Failed to connect to the FTP server. |
|
Impact |
No negative impact on the system. |
|
Cause |
When packet capture is configured, the captured packets will be saved to the specified FTP server. Packet capture failed to start because the device failed to be connected to the FTP server. |
|
Recommended action |
1. Ping the FTP server address. If the ping operation fails, resolve the ping failure first. 2. Restart the packet capture feature. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_INVALD_FILTER: Failed to start packet capture. Reason: Invalid expression for matching packets to be captured. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packet capture failed to start because the capture filter expression was invalid. |
|
Recommended action |
Correct the capture filter expression. |
PKTCPT_LOGIN_DENIED
|
Message text |
Packet capture aborted. Reason: FTP server login failure. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_LOGIN_DENIED: Packet capture aborted. Reason: FTP server login failure. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packet capture stopped because the user failed to log in to the FTP server. |
|
Recommended action |
Identify whether the username and password used for logging in to the FTP server match those configured on the FTP server. If not, you cannot log in to the FTP server. Execute the ftp command on the device, enter the username and password, and attempt to upload a file to the FTP server. If the test fails, troubleshoot and resolve the FTP upload failure issue. |
PKTCPT_MEMORY_ALERT
|
Message text |
Packet capture aborted. Reason: Memory threshold reached. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_MEMORY_ALERT: Packet capture aborted. Reason: Memory threshold reached. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packet capture stopped because the memory threshold was reached. |
|
Recommended action |
1. Release memory resources. For example, execute the logfile save command to manually save the contents of the log file buffer to the log file and release the memory resources occupied by the log file buffer. 2. Execute the display memory command to check the memory usage: ¡ If the memory usage has not dropped below the threshold, execute the display process command to check the memory usage of user-state processes. If a particular process is consuming a significant amount of memory, you can enable or disable the corresponding software functionality of that process to release memory. ¡ If the memory usage drops below the alarm threshold, the memory alarm will be cleared. The Tcl monitoring policy will continue to be effective, so no additional action is required. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_OPEN_FAIL: Failed to start packet capture. Reason: File for storing captured frames not opened. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packer capture failed to start because the file for storing the captured frames cannot be opened. |
|
Recommended action |
· If the current logged-in user does not have the permission to write the file, the administrator must use the RBAC feature to configure the permission to write the file for the user. Alternatively, switch to a user with the permission to write the file, log in to the device again, and then enable the packet capture feature. · If the specified file is currently being accessed by another process, try again by using a different file name. |
PKTCPT_OPERATION_TIMEOUT
|
Message text |
Failed to start or continue packet capture. Reason: Operation timed out. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_OPERATION_TIMEOUT: Failed to start or continue packet capture. Reason: Operation timed out. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated in the following situations: · Packet capture failed to start because the FTP server in a different network segment is not reachable and the connection timed out. · Packet capture stopped because the FTP server in a different network segment is offline and uploading the captured frames timed out. |
|
Recommended action |
1. Ping the FTP server to identify whether the FTP server is reachable. If the ping fails, resolve the connectivity issue with the FTP server. 2. Identify whether the FTP server is providing services properly. On the device, execute the ftp command, provide the username and password, and attempt to upload a file to the FTP server. If the test fails, identify and resolve the issue causing the FTP upload failure. |
PKTCPT_SERVICE_FAIL
|
Message text |
Failed to start packet capture. Reason: TCP or UDP port binding faults. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_SERVICE_FAIL: Failed to start packet capture. Reason: TCP or UDP port binding faults. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packet capture failed to start because an error occurs during TCP or UDP port binding. |
|
Recommended action |
Perform packet capture with a new port number: 1. Execute the display tcp and display udp commands on the device to check the current TCP and UDP port numbers being used by the device. 2. Use an unused TCP or UDP port number as the RPCAP service listening port number when executing the packet-capture remote command. 3. Connect the client to the device and specify the device IP address as the server-side IP address and the port value configured in the packet-capture remote command as the server-side listening port value. The client will establish an RPCAP connection to the device by using the specified IP address and port number. 4. The device will send the captured packets to the client through the RPCAP connection. 5. The client can parse and display the received packets. |
PKTCPT_UNKNOWN_ERROR
|
Message text |
Failed to start or continue packet capture. Reason: Unknown error. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_UNKNOWN_ERROR: Failed to start or continue packet capture. Reason: Unknown error. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packet capture failed to start or packet capture stopped because of an unknown error. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PKTCPT_UPLOAD_ERROR
|
Message text |
Packet capture aborted. Reason: Failed to upload captured frames. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_UPLOAD_ERROR: Packet capture aborted. Reason: Failed to upload captured frames. |
|
Impact |
No negative impact on the system. |
|
Cause |
If the specified directory for saving captured data packets does not exist or you do not have permissions to write the directory, the captured data packets will fail to be uploaded and the packet capture process will stop. |
|
Recommended action |
1. Identify whether the specified directory in the packet-capture command exists on the FTP server: If the directory does not exist, create it on the FTP server before performing the packet capture operation on the device. 2. Identify whether you have permissions to write the specified directory in the packet-capture command: Execute the ftp command on the device. Enter the username and password for the FTP server. Try to upload a file to the directory specified in the packet-capture command: ¡ If the upload is successful, it means you have permissions to write the directory. ¡ If the upload fails, it means you do not have permissions to write the directory. Try a different directory within the FTP server's working path and try again. |
PKTCPT_WRITE_FAIL
|
Message text |
Packet capture aborted. Reason: Not enough space to store captured frames. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PKTCPT/6/PKTCPT_WRITE_FAIL: Packet capture aborted. Reason: Not enough space to store captured frames. |
|
Impact |
No negative impact on the system. |
|
Cause |
Packet capture stopped because the memory space is not enough for storing captured frames. |
|
Recommended action |
Execute the dir command in user view to view the file information in the device's storage media. To release storage space, you can use the delete /unreserved command to delete unnecessary files. |
PORT
This section contains port messages.
LINK_FLAP_FREQ
|
Message text |
The link of [STRING] flaps frequently. Please check the hardware link! |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
PORT/4/LINK_FLAP_FREQ: The link of Ten-GigabitEthernet5/0/1 flaps frequently. Please check the hardware link! |
|
Impact |
The interface cannot operate correctly, or packet loss or error will occur on the port. |
|
Cause |
Possible causes include: · The interface came up or went down frequently. · Unstable transceiver module, optical fiber, or network cable connection. · Interface fault. |
|
Recommended action |
1. Check and ensure link connectivity. 2. Check and ensure that the peer interface is operating correctly. 3. Restart the card where the peer interface resides. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PORT_BW_NOTENOUGH
|
Message text |
Not enough limit resources. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PORT/3/PORT_BW_NOTENOUGH: -MDC=1-Slot=2; Not enough limit resources. |
|
Impact |
GE/XGE switching cannot be performed. |
|
Cause |
Rate limiting resources are insufficient for GE/XGE switching. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PORT_FMEA_ERR
|
Message text |
Hardware error detected on subslot [INT32]. (ErrCode = [STRING]). |
|
Variable fields |
$1: Subslot ID. $2: Fault type. ¡ 0000000: FPGA PCIe access failure. ¡ 2000000: FPGA PLL out of lock. ¡ 300000x: Interlaken interface failure on the NP side. When x is 1, interface 1 has failed. When x is 2, interface 2 has failed. When x is 3, interfaces 1 and 2 have failed. ¡ 400000x: Interlaken interface failure on the FPGA side. When x is 1, interface 1 has failed. When x is 2, interface 2 has failed. When x is 3, interfaces 1 and 2 have failed. ¡ 5000000: Clock chip PLL on the subcard is out of lock. ¡ 6000000: Uncorrectable error on the SEU ¡ 70000xx: XFI interface failure on the NPA side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. ¡ a000000: QSGMII interface failure on the NP side. ¡ d0000xx: XFI interface failure on the NPB side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. ¡ 110000xx: XFI interface failure on the NPC side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. ¡ 170000xx: PHY A chip read/write failure. When xx is a value in the range of 1 to 30, read/write to the interface with that number has failed. When xx is ff, read/write to all interfaces have failed. ¡ 180000xx: PHY B chip read/write failure. When xx is a value in the range of 1 to 30, read/write to the interface with that number has failed. When xx is ff, read/write to all interfaces have failed. ¡ 190000xx: PHY C chip read/write failure. When xx is a value in the range of 1 to 30, read/write to the interface with that number has failed. When xx is ff, read/write to all interfaces have failed. ¡ 1d000000: MAC and PHY chip connection failure. |
|
Severity level |
2 (Critical) |
|
Example |
PORT/2/PORT_FMEA_ERR: -MDC=1-Slot=2; Hardware error detected on subslot 2. (ErrCode = 6000000). |
|
Impact |
The interface card cannot operate correctly. The following lists the system impacts corresponding to the fault types in the description for the variable fields one by one from top to bottom: · The system is slowing down or gets stuck, and will reboot the subcard if the issue persists after three attempts to resolve the issue. · A functional anomaly occurs on the subcard. · A forwarding anomaly occurs on the subcard. · A forwarding anomaly occurs on the subcard. · A functional anomaly occurs on the subcard. · A functional anomaly occurs on the subcard. · Interfaces go down. · Interfaces go down. · Interfaces go down. · Interfaces go down. · A functional anomaly occurs on the subcard. · A functional anomaly occurs on the subcard. · A functional anomaly occurs on the subcard. · Interfaces go down. |
|
Cause |
A hardware error was detected on the subcard. |
|
Recommended action |
1. Reboot the subard. 2. Reboot the card where the subcard resides. 3. Replace the card/subcard. 4. Check whether a card connection fault or subcard/card slot fault is present. Fix it if such a fault is present. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PORT_FMEA_RECOVER
|
Message text |
Hardware error recovered on subslot [INT32]. (ErrCode = [STRING]). |
|
Variable fields |
$1: Subslot ID. $2: Fault type. ¡ 0000000: FPGA PCIe access failure. ¡ 2000000: FPGA PLL out of lock. ¡ 300000x: Interlaken interface failure on the NP side. When x is 1, interface 1 has failed. When x is 2, interface 2 has failed. When x is 3, interfaces 1 and 2 have failed. ¡ 400000x: Interlaken interface failure on the FPGA side. When x is 1, interface 1 has failed. When x is 2, interface 2 has failed. When x is 3, interfaces 1 and 2 have failed. ¡ 5000000: Clock chip PLL on the subcard is out of lock. ¡ 6000000: Uncorrectable error on the SEU ¡ 70000xx: XFI interface failure on the NPA side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. ¡ d0000xx: XFI interface failure on the NPB side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. ¡ 110000xx: XFI interface failure on the NPC side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. ¡ 170000xx: PHY A chip read/write failure. When xx is a value in the range of 1 to 30, read/write to the interface with that number has failed. When xx is ff, read/write to all interfaces have failed. ¡ 180000xx: PHY B chip read/write failure. When xx is a value in the range of 1 to 30, read/write to the interface with that number has failed. When xx is ff, read/write to all interfaces have failed. ¡ 190000xx: PHY C chip read/write failure. When xx is a value in the range of 1 to 30, read/write to the interface with that number has failed. When xx is ff, read/write to all interfaces have failed. ¡ 1d000000: MAC and PHY chip connection failure. |
|
Severity level |
2 (Critical) |
|
Example |
PORT/2/PORT_FMEA_RECOVER: -MDC=1-Slot=2; Hardware error recovered on subslot 2. (ErrCode = 6000000). |
|
Impact |
No negative impact on the system. |
|
Cause |
The subcard recovered from a hardware error. |
|
Recommended action |
No action is required. |
PORT_HW_ERROR_REBOOT
|
Message text |
Hardware error detected on subslot [INT32]. (ErrCode = [STRING]). Rebooting the [STRING]… |
|
Variable fields |
$1: Subslot ID. $2: Fault type. ¡ 0000000: FPGA PCIe access failure. ¡ 1000000: FPGA local-bus access failure. ¡ 300000x: Interlaken interface failure on the NP side. When x is 1, interface 1 has failed. When x is 2, interface 2 has failed. When x is 3, interfaces 1 and 2 have failed. ¡ 400000x: Interlaken interface failure on the FPGA side. When x is 1, interface 1 has failed. When x is 2, interface 2 has failed. When x is 3, interfaces 1 and 2 have failed. ¡ 70000xx: XFI interface failure on the NPA side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. ¡ d0000xx: XFI interface failure on the NPB side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. ¡ 110000xx: XFI interface failure on the NPC side. When xx is a value in the range of 1 to 30, the interface with that number has failed. When xx is ff, all XFI interfaces have failed. $3: Card or subard where the error errors.. ¡ subcard. ¡ board. |
|
Severity level |
2 (Critical) |
|
Example |
PORT/2/PORT_HW_ERROR_REBOOT: -MDC=1-Slot=2; Hardware error detected on subslot 2. (ErrCode = 1000000). Rebooting the subcard… |
|
Impact |
· The subard/card might be rebooted. · The subard/card cannot operate correctly. |
|
Cause |
· Access channel or interface failure on the subcard/card. · Hardware link status error on the subcard/card. You can see the fault types in the description for the variable fields. |
|
Recommended action |
1. Reboot the subard/card 2. Replace the card/subcard. 3. Check whether a card connection fault or subcard/card slot fault is present. Fix it if such a fault is present. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
TRANS_IO_FAULT
|
Message text |
[STRING]: Transceiver module has I/O errors. Please check the transceiver module. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
PORT/4/TRANS_IO_FAULT: -MDC=1-Slot=2; GigabitEthernet2/1/1: Transceiver module has I/O errors. Please check the transceiver module. |
|
Impact |
The transceiver module cannot operate correctly. |
|
Cause |
· The transceiver module is not supported. · The transceiver module is faulty. |
|
Recommended action |
1. Check if the interface supports the transceiver module. ¡ Check is a message "Transceiver type not supported" is display. ¡ Execute the display transceiver interface command to identify the transceiver module type and determine whether the interface supports the transceiver module. 2. If the interface supports the transceiver module, replace the faulty transceiver module. If the interface does not support the transceiver module, replace it with one supported by the interface. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
Portal messages
This section contains portal messages.
PORTAL_LIMIT_GLOBAL
|
Message text |
User failed to come online. Reason=BAS global access limit already reached. |
|
Variable fields |
No negative impact on the system. |
|
Severity level |
6 (Informational) |
|
Example |
PORTAL/6/PORTAL_LIMIT_GLOBAL: User failed to come online. Reason=BAS global access limit already reached. |
|
Impact |
New portal users cannot come online. |
|
Cause |
The number of portal users online has reached the global maximum. |
|
Recommended action |
· Use the portal max-user command to increase the global maximum number of portal users. · Use the portal delete-user command to log out idle online portal users. |
PORTAL_LIMIT_IF
|
Message text |
User failed to come online through interface [STRING]. Reason=BAS access limit of the interface already reached. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
PORTAL/6/PORTAL_LIMIT_IF: User failed to come online through interface GigabitEthernet1/0/1. Reason=BAS access limit of the interface already reached. |
|
Impact |
New portal users cannot come online from the interface. |
|
Cause |
The number of portal users online has reached the maximum allowed on the interface. |
|
Recommended action |
· Use the portal { ipv4-max-user | ipv6-max-user } command to increase the maximum number of portal users allowed on the interface. · Use the portal delete-user command to log out idle online portal users. |
PORTAL_USER_LOGOFF
|
Message text |
-UserName=[STRING]-IPAddr=[STRING]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[STRING]-Reason=[STRING]-Input Octets=[UINT32]-Output Octets=[UINT32]-Input Gigawords=[UINT32]-Output Gigawords=[UINT32]; User went offline. |
|
Variable fields |
$1: Username. $2: IP address. $3: Interface name. $4: Outer VLAN ID. $5: Inner VLAN ID. $6: MAC address. $7: User request. $8: Input Octets. $9: Output Octets. $10: Input Gigawords. $11: Output Gigawords. |
|
Severity level |
6 (Informational) |
|
Example |
PORTAL/6/PORTAL_USER_LOGOFF: -UserName=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000- OuterVLAN=100-InnerVLAN=4000-MACAddr=0230-0103-5601-Reason=User request-Input Octets=100-Output Octets=200-Input Gigawords=100-Output Gigawords=200; User went offline. |
|
Impact |
No negative impact on the system. |
|
Cause |
The portal user normally went offline. |
|
Recommended action |
No action is required. |
PORTAL_USER_LOGOFF_ABNORMAL
|
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]; User went offline abnormally. |
|
Variable fields |
$1: Username. $2: IP address. $3: Interface name. $4: Outer VLAN ID $5: Inner VLAN ID. $6: MAC address. $7: Offline reason. For possible reasons, see Table 8. $8: Input Octets. $9: Output Octets. $10: Input Gigawords. $11: Output Gigawords. |
|
Severity level |
6 (Informational) |
|
Example |
PORTAL/6/PORTAL_USER_LOGOFF_ABNORMAL: -UserName=abc-IPAddr=1.1.1.2-IfName=Route-Aggregation1023.4000- OuterVLAN=100-InnerVLAN=4000-MACAddr=0230-0103-5601-Reason=Port down-Input Octets=100-Output Octets=200-Input Gigawords=100-Output Gigawords=200; User went offline abnormally. |
|
Impact |
This portal user cannot access the network and needs to reauthenticate again by portal. |
|
Cause |
The user went offline abnormally. For the abnormal offline reasons, see Table 8. |
|
Recommended action |
Take the corresponding measures according to the failure reason. For more information, see Table 8. |
Table 13 Reasons for abnormal offline
|
Offline Reason |
Description |
Recommended action |
|
DHCP lease timeout. |
DHCP lease expired. |
No negative impact on the system. |
|
DHCP user request. |
The client proactively requests the release of the IP address. |
No negative impact on the system. |
|
DHCP configuration changed. |
Changes in DHCP configuration cause the user to go offline. |
Please check the DHCP server configuration. |
|
Idle timeout. |
The user's traffic did not reach the set threshold within the specified time. |
No negative impact on the system. |
|
Session timeout. |
The user's online time has reached the set limit. |
No negative impact on the system. |
|
User detection failure |
User online detection failed. |
No negative impact on the system. |
|
The user was logged off by the RADIUS server. |
No negative impact on the system. |
|
|
Interface down. |
The access interface went down. |
Ensure the network connection for the user's access interface is normal and the shutdown command is not executed on the interface. |
|
Interface inactive. |
The access interface state is inactive. |
· Ensure the network connection for the user's access interface is normal. · Ensure that the user connected card or subcard is in place and functioning normally. |
|
Port was removed from VLAN. |
Portal authentication is enabled on the VLAN interface, but the Layer 2 access port for the user was removed from the VLAN. |
Ensure that the Layer 2 port users access has portal-roaming enabled. |
|
Authorization ACL for the online user was deleted. |
The authorization ACL assigned to the online user has been deleted. |
No negative impact on the system. |
|
The device forcibly logged out the user. |
The user was logged off by the device. |
Ensure the portal feature on the interface is functioning properly. |
|
Failed to synchronize user information with the server. |
The device and server failed to synchronize user information. |
· Ensure the server configures the user heartbeat interval to be less than or equal to the user sync timeout set on the device. · Make sure the server is reachable. |
|
User recovery failure |
User info restoration failed. |
· Ensure that the access interface is in Up state. · Ensure that the portal feature is functioning properly on the access interface. · Ensure that the user’s online duration has not reached the maximum allowed. |
|
Authorization ACL for the online user changed. |
Changes to the content of the authorization ACL for online users causes them to go offline. |
· Ensure the ACL reauthorization is successful. · Ensure the interface does not have strict ACL checking configured. |
|
Authorization user profile for the online user changed. |
Changes to the content of the authorization user profile for online users causes them to go offline. |
· Use the display user profile command check if the authorization failed. Ensure the user profile authorization is successful. · Ensure the interface does not have user profile strict checking configured. |
|
The RADIUS server doesn't reply to the accounting request. |
The RADIUS server cannot respond to accounting requests. |
· Ensure that the device communicates properly with the RADIUS server. · Ensure that the RADIUS server is in a normal state. |
|
Accounting update failure. |
Accounting failed to be updated |
· Ensure that the device communicates properly with the RADIUS server. · Ensure that the RADIUS server is in a normal state. |
|
No AAA response for the accounting start packet was received. |
If the user does not receive a response from the authentication server within the message timeout period (during the accounting initiation phase). |
· Ensure that the device communicates properly with the RADIUS server. · Ensure that the RADIUS server is in a normal state. |
|
Failed to send the accounting request for the user. |
User accounting request sending failed. |
· Ensure that the device communicates properly with the RADIUS server. · Ensure that the RADIUS server is in a normal state. |
|
Traffic threshold for the user was reached. |
The user's traffic has reached the threshold. |
No negative impact on the system. |
PORTAL_USER_LOGON_FAIL
|
Message text |
-UserName=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]-Reason=[STRING]; 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: Online failure reason. For possible reasons, see Table 9. |
|
Severity level |
6 (Informational) |
|
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 failure; User failed to come online. |
|
Impact |
The portal user cannot log in to use portal services. |
|
Cause |
The user failed to come online. For the failure reasons, see Table 9. |
|
Recommended action |
Take the corresponding measures according to the failure reason. For more information, see Table 9. |
Table 14 Causes for failure to come online
|
Cause for failure to come online |
Remarks |
Recommended action |
|
Authentication failure. |
Authentication failed. |
· Ensure that the communication between the device and the authentication server is functioning properly. · Ensure that the shared key between the device and the authentication server is the same. · Ensure the username is valid. · Ensure the password is correct. · Ensure the authentication domain on the device is configured correctly. |
|
Authorization failure. |
Authorization failed. |
· Ensure that the device communicates properly with the authorization server. · Ensure that the authorization attributes issued by the authorization server exist and are correctly configured on the device. · Ensure the device supports the authorization attributes issued by the authorization server. |
|
Authentication ACK message was not received from the RADIUS server. |
The device does not receive the authentication ACK packet from the RADIUS server. |
Ensure the device can reach the RADIUS server through routing. |
|
The device failed to send the authentication request to the RADIUS server. |
The device failed to send an authentication request to the RADIUS server. |
· Ensure that the device communicates properly with the RADIUS server. · Use the display radius scheme command to check the RADIUS server state and make sure the state is active. |
|
The RADIUS server rejected the authentication request. |
The RADIUS server rejected the authentication request of the user. |
Ensure the username and password are correct. |
|
Failed to add authorization information for the user. |
Failed to add authorization information for the user. |
Make sure the authorization attributes issued by the authorization server exist on the device and are configured correctly. |
|
Local authentication request was rejected. |
Local authentication request for the user was rejected. |
Make sure the username and password of the local user are correct. |
|
AAA with Authentication no response. |
The user does not receive a response from the authentication server within the authentication timeout period. |
· Make sure the communication between the device and the RADIUS server is normal. · Make sure the RADIUS server is functioning properly. |
|
Maximum number of concurrent logins for the account already reached. |
The number of users accessing one account has exceeded the limit. |
· Check the maximum number of users allowed to use one account. · Modify the limit by using the access-limit command. |
|
Local user doesn't exist on the device. |
The device does not have this local user configured. |
Check the local user configuration on the device. |
|
Failed to assign a user rule. |
User rule deployment failed. |
The hardware memory space is not enough. Please release memory. |
|
Failed to obtain physical information. |
Failed to obtain physical information during the online process. |
No negative impact on the system. |
|
Authorization ACL doesn't exist. |
The authorization ACL does not exist. |
Make sure the authorization ACL has been configured. |
PORTAL_USER_LOGON_SUCCESS
|
-UserName=[STRING]-IPAddr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]; 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 (Informational) |
|
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 came online successfully. |
|
Impact |
No negative impact on the system. |
|
Cause |
The portal user have successfully come online. |
|
Recommended action |
No action is required. |
PPP messages
This section contains PPP messages.
PPP_SESSIONS_LOWER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
The PPP session number is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower alarm threshold for the online PPP session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPP/4/PPP_SESSIONS_LOWER_THRESHOLD: The PPP session number is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of users might go offline because of abnormal reasons. Identify whether a large number of users go offline abnormally. |
|
Cause |
· The device-level lower alarm threshold for the number of online PPP users is too high. · Users go offline, and the number of PPP users on the device reaches the lower alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the ppp session-threshold command, and identify whether the lower alarm threshold configured is appropriate. ¡ If the configured lower alarm threshold is too high, proceed with step 2. ¡ If the configured lower alarm threshold is appropriate, proceed with step 3. 2. Execute the ppp session-threshold command in system view on the device to modify the lower alarm threshold. 3. Execute the display aaa abnormal-offline-record access-type ppp command to identify whether a large number of PPP users are going offline abnormally. ¡ If yes, process accordingly based on the specific reason for going offline. ¡ If not, execute the display aaa offline-record access-type ppp command to view the reasons for PPP users to go offline and resolve the issues accordingly. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPP_SESSIONS_LOWER_THRESHOLD (vBRAS-CPs)
|
Message text |
The PPP session number on slot [INT32] is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Lower alarm threshold for the online PPP session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPP/4/PPP_SESSIONS_LOWER_THRESHOLD: The PPP session number on slot 97 is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of users might go offline because of abnormal reasons. Identify whether a large number of users go offline abnormally. |
|
Cause |
· The device-level lower alarm threshold for the number of online PPP users is too high. · Users go offline, and the number of PPP users on the device reaches the lower alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the ppp session-threshold command, and identify whether the lower alarm threshold configured is appropriate. ¡ If the configured lower alarm threshold is too high, proceed with step 2. ¡ If the configured lower alarm threshold is appropriate, proceed with step 3. 2. Execute the ppp session-threshold command in system view on the device to modify the lower alarm threshold. 3. Execute the display aaa abnormal-offline-record access-type ppp command to identify whether a large number of PPP users are going offline abnormally. ¡ If yes, process accordingly based on the specific reason for going offline. ¡ If not, execute the display aaa offline-record access-type ppp command to view the reasons for PPP users to go offline and resolve the issues accordingly. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPP_SESSIONS_LOWER_RECOVER (non-vBRAS-CPs)
|
Message text |
The PPP session number has recovered to normal state from below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower alarm threshold for the online PPP session count. |
|
Severity level |
5 (Notification) |
|
Example |
PPP/5/PPP_SESSIONS_LOWER_RECOVER: The PPP session number has recovered to normal state from below the lower warning threshold (LowerThreshold=20). |
|
Impact |
The number of PPP users on the device meets the expectation. |
|
Cause |
PPP user comes online, and the online PPP session count recovers from below the lower alarm threshold to the normal range. |
|
Recommended action |
No action is required. |
PPP_SESSIONS_LOWER_RECOVER (vBRAS-CPs)
|
Message text |
The PPP session number on slot [INT32] has recovered to normal state from below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Lower alarm threshold for the online PPP session count. |
|
Severity level |
5 (Notification) |
|
Example |
PPP/5/PPP_SESSIONS_LOWER_RECOVER: The PPP session number on slot 97 has recovered to normal state from below the lower warning threshold (LowerThreshold=20). |
|
Impact |
The number of PPP users on the device meets the expectation. |
|
Cause |
PPP user comes online, and the online PPP session count recovers from below the lower alarm threshold to the normal range. |
|
Recommended action |
No action is required. |
PPP_SESSIONS_UPPER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
The PPP session number is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper alarm threshold for the online PPP session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPP/4/PPP_SESSIONS_UPPER_THRESHOLD: The PPP session number is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online PPP users might exceed the device capability, and the subsequent PPP users might fail to come online. |
|
Cause |
· The device-level upper alarm threshold for the number of online PPP users is too low. · Users come online, and the number of PPP users on the device reaches the upper alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the ppp session-threshold command, and identify whether the upper alarm threshold configured is appropriate. ¡ If the configured upper alarm threshold is too low, proceed with step 2. ¡ If the configured upper alarm threshold is appropriate, proceed with step 3. 2. Execute the ppp session-threshold command in system view on the device to modify the upper alarm threshold. 3. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPP_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
|
Message text |
The PPP session number on slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Upper alarm threshold for the online PPP session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPP/4/PPP_SESSIONS_UPPER_THRESHOLD: The PPP session number on slot 97 is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online PPP users might exceed the device capability, and the subsequent PPP users might fail to come online. |
|
Cause |
· The device-level upper alarm threshold for the number of online PPP users is too low. · Users come online, and the number of PPP users on the device reaches the upper alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the ppp session-threshold command, and identify whether the upper alarm threshold configured is appropriate. ¡ If the configured upper alarm threshold is too low, proceed with step 2. ¡ If the configured upper alarm threshold is appropriate, proceed with step 3. 2. Execute the ppp session-threshold command in system view on the device to modify the upper alarm threshold. 3. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPP_SESSIONS_UPPER_RECOVER (non-vBRAS-CPs)
|
Message text |
The PPP session number has recovered to normal state from above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper alarm threshold for the online PPP session count. |
|
Severity level |
5 (Notification) |
|
Example |
PPP/5/PPP_SESSIONS_UPPER_RECOVER: The PPP session number has recovered to normal state from above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online PPP users decreases and does not exceed the device capability. The subsequent PPP users can come online successfully. |
|
Cause |
Some users go offline, and the number of online PPP sessions has been restored from above the upper alarm threshold to the set normal range. |
|
Recommended action |
No action is required. |
PPP_SESSIONS_UPPER_RECOVER (vBRAS-CPs)
|
Message text |
The PPP session number on slot [INT32] has recovered to normal state from above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Upper alarm threshold for the online PPP session count. |
|
Severity level |
5 (Notification) |
|
Example |
PPP/5/PPP_SESSIONS_UPPER_RECOVER: The PPP session number on slot 97 has recovered to normal state from above the upper warning threshold (UpperThreshold =20). |
|
Impact |
The number of online PPP users decreases and does not exceed the device capability. The subsequent PPP users can come online successfully. |
|
Cause |
Some users go offline, and the number of online PPP sessions has been restored from above the upper alarm threshold to the set normal range. |
|
Recommended action |
No action is required. |
PPPOES_LIMIT
|
Message text |
Maximum number of PPPoE sessions already reached. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PPPOES/3/PPPOES_LIMIT: Maximum number of PPPoE sessions already reached. |
|
Impact |
New users cannot come online. |
|
Cause |
When the number of online PPPoE users reaches the upper limit for the system, new users cannot come online. |
|
Recommended action |
1. Execute the display this command in system view to check the pppoe-server session-limit total configuration. 2. Execute the display pppoe-server session summary slot command in any view to identify whether the number of PPPoE sessions on the card has reached the maximum number of PPPoE sessions allowed for the system. 3. If new users cannot come online for reasons other than the preceding reasons, collect the following information and contact Technical Support for help: ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPPOES_LIMIT_VLAN
|
Message text |
Maximum number of PPPoE sessions for the VLAN already reached. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PPPOES/3/PPPOES_LIMIT_VLAN: Maximum number of PPPoE sessions for the VLAN already reached. |
|
Impact |
New users cannot come online. |
|
Cause |
When the number of online PPPoE users reaches the upper limit for each VLAN, new users cannot come online. |
|
Recommended action |
1. Execute the display this command in the view of the user access interface to check the pppoe-server session-limit per-vlan configuration. 2. Execute the display pppoe-server session summary interface command in any view to identify whether the number of PPPoE sessions on the current interface has reached the maximum number of PPPoE sessions allowed for each VLAN. 3. If new users cannot come online for reasons other than the preceding reasons, collect the following information and contact Technical Support for help: ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPPOES_LIMIT_IF
|
Message text |
Maximum number of PPPoE sessions for the interface already reached. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PPPOES/3/PPPOES_LIMIT_IF: Maximum number of PPPoE sessions for the interface already reached. |
|
Impact |
New users cannot come online. |
|
Cause |
When the number of online PPPoE users reaches the upper limit for the interface, new users cannot come online. |
|
Recommended action |
1. Execute the display this command in the view of the user access interface to check the pppoe-server session-limit configuration. 2. Execute the display pppoe-server session summary interface command in any view to identify whether the number of PPPoE sessions on the current interface has reached the maximum number of PPPoE sessions allowed for each interface. 3. If new users cannot come online for reasons other than the preceding reasons, collect the following information and contact Technical Support for help: ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPPOES_LIMIT_MAC
|
Message text |
Maximum number of PPPoE sessions for the user already reached. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PPPOES/3/PPPOES_LIMIT_MAC: Maximum number of PPPoE sessions for the user already reached. |
|
Impact |
New users cannot come online. |
|
Cause |
When the number of online PPPoE users reaches the maximum number of sessions for each user, new users cannot come online. |
|
Recommended action |
1. Execute the display this command in the view of the user access interface to check the pppoe-server session-limit per-mac configuration. 2. Execute the display pppoe-server session summary interface command in any view to identify whether the number of PPPoE sessions on the current interface has reached the maximum number of PPPoE sessions allowed for each user. 3. If new users cannot come online for reasons other than the preceding reasons, collect the following information and contact Technical Support for help: ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPPOES_LOSS_RATIO_EXCEED_THRESHOLD
|
Message text |
Centralized devices: The keepalive packet loss ratio on the interface [STRING] is [UINT32]%, and exceeds [UINT32]%. Distributed devices in standalone mode: Centralized IRF devices: The keepalive packet loss ratio on the interface [STRING] on slot [UINT32] is [UINT32]%, and exceeds [UINT32]%. Distributed devices in IRF mode: The keepalive packet loss ratio on the interface [STRING] on chassis [UINT32] slot [UINT32] is [UINT32]%, and exceeds [UINT32]%. |
|
Variable fields |
$1: Interface name. $2: Chassis number. (Distributed devices in IRF mode.) $3: Slot number. (Distributed devices in standalone mode.)(Centralized IRF devices.)(Distributed devices in IRF mode.) $4: Packet loss ratio of detection packets. $5: Alarm threshold for the packet loss ratio of detection packets. |
|
Severity level |
4 (Warning) |
|
Example |
Centralized devices: PPP/4/PPPOES_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio on the interface GigabitEthernet1/0/1 is 50%, and exceeds 30%. Distributed devices in standalone mode: Centralized IRF devices: PPP/4/PPPOES_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio on the interface GigabitEthernet1/0/1 on slot 1 is 50%, and exceeds 30%. Distributed devices in IRF mode: PPP/4/PPPOES_LOSS_RATIO_EXCEED_THRESHOLD: The keepalive packet loss ratio on the interface GigabitEthernet1/0/1 on chassis 1 slot 1 is 50%, and exceeds 30%. |
|
Impact |
A high packet loss ratio might force users to go offline due to detection failure. |
|
Cause |
· The upper threshold configured is too low. · Device interface connection faults and other issues can lead to poor link quality, causing the number of lost packets for online users to reach the alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to filter and find the access-user user-detect packet-loss-ratio-threshold command. Identify whether the current alarm threshold configured for the packet loss ratio of access user detection packets is appropriate. ¡ If the configured threshold is too low, proceed with step 2. ¡ If the configured threshold is appropriate, proceed with step 3. 2. Execute the access-user user-detect packet-loss-ratio-threshold command in system view on the device to modify the alarm threshold for the packet loss ratio of access user detection packets. 3. Identify whether the device interface cable connections and network configuration are normal: ¡ If abnormal, troubleshoot the faults. ¡ If normal, proceed with step 4. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPPOES_LOSS_RATIO_RECOVER_NORMAL
|
Message text |
Centralized devices: The keepalive packet loss ratio on the interface [STRING] has recovered to normal state. Distributed devices in standalone mode: Centralized IRF devices: The keepalive packet loss ratio on the interface [STRING] on slot [UINT32] has recovered to normal state. Distributed devices in IRF mode: The keepalive packet loss ratio on the interface [STRING] on chassis [UINT32] slot [UINT32] has recovered to normal state. |
|
Variable fields |
$1: Interface name. $2: Chassis number. (Distributed devices in IRF mode.) $3: Slot number. (Distributed devices in standalone mode.)(Centralized IRF devices.)(Distributed devices in IRF mode.) |
|
Severity level |
4 (Warning) |
|
Example |
Centralized devices: PPP/4/PPPOES_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio on the interface GigabitEthernet1/0/1 has recovered to normal state. Distributed devices in standalone mode: Centralized IRF devices: PPP/4/PPPOES_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio on the interface GigabitEthernet1/0/1 on slot 1 has recovered to normal state. Distributed devices in IRF mode: PPP/4/PPPOES_LOSS_RATIO_RECOVER_NORMAL: The keepalive packet loss ratio on the interface GigabitEthernet1/0/1 on chassis 1 slot 1 has recovered to normal state. |
|
Impact |
The network jitter and latency drop to reasonable levels to restore normal service quality for users. |
|
Cause |
The link quality is restored to normal after you troubleshoot device interface connectivity faults. |
|
Recommended action |
No action is required. |
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 (Notification) |
|
Example |
PPPOES/5/PPPOES_MAC_THROTTLE: The MAC 001b-21a8-0949 triggered MAC throttle on interface GigabitEthernet1/0/1. |
|
Impact |
A user is blocked and cannot come online. |
|
Cause |
The number of session requests from a PPPoE user within the monitoring time reached the per-user session request limit on the access interface. The access interface discarded the session requests from the user within the blocking time. |
|
Recommended action |
1. Execute the display this command in the view of the user access interface to check the pppoe-server throttle per-mac configuration. 2. Use the display pppoe-server throttled-mac command in any view to view the left blocking time for the blocked user on the access interface. 3. If new users cannot come online for reasons other than the preceding reasons, collect the following information and contact Technical Support for help: ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPPOES_SESSION_ADD_DRIVER_FAILED
|
Message text |
Failed to add a PPPoE session: Ifname=[STRING], SessionID=[UINT16]. Cause: Not enough hardware resources. |
|
Variable fields |
$1: Name of the interface where the PPPoE user came online. $2: PPPoE session ID. |
|
Severity level |
4 (Warning) |
|
Example |
PPPOES/4/PPPOES_SESSION_ADD_DRIVER_FAILED: Failed to add a PPPoE session: Ifname=GigabitEthernet1/0/1, SessionID=100. Cause: Not enough hardware resources. |
|
Impact |
The PPPoE session failed to be created. |
|
Cause |
Insufficient hardware resources cause PPPoE session addition to fail. |
|
Recommended action |
Collect the following information and contact Technical Support: · Results of each step. · Configuration data, log messages, and alarm information. |
PPPOES_SESSIONS_LOWER_THRESHOLD
|
Message text |
The PPPoE session number is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower alarm threshold for the online PPPoE session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPPOES/4/PPPOES_SESSIONS_LOWER_THRESHOLD: The PPPoE session number is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of users might go offline because of abnormal reasons. Identify whether a large number of users go offline abnormally. |
|
Cause |
The device-level lower alarm threshold for the online PPPoE user count is too high. Users go offline, and the number of PPPoE users on the device reaches the lower alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the pppoe-server session-threshold command, and identify whether the lower alarm threshold configured is appropriate. ¡ If the configured lower alarm threshold is too high, proceed with step 2. ¡ If the configured lower alarm threshold is appropriate, proceed with step 3. 2. Execute the pppoe-server session-threshold command in system view on the device to modify the lower alarm threshold. 3. Execute the display aaa abnormal-offline-record access-type ppp command to identify whether a large number of PPP users are going offline abnormally. ¡ If yes, process accordingly based on the specific reason for going offline. ¡ If not, execute the display aaa offline-record access-type ppp command to view the reasons for PPP users to go offline and resolve the issues accordingly. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
|
Message text |
The PPPoE session number on slot [INT32] is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number. $2: Lower alarm threshold for the online PPPoE session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPPOES/4/PPPOES_SESSIONS_LOWER_THRESHOLD: The PPPoE session number on slot 1 is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of users might go offline because of abnormal reasons. Identify whether a large number of users go offline abnormally. |
|
Cause |
· The device-level lower alarm threshold for the online PPPoE user count is too high. · Users go offline, and the number of PPPoE users on the device reaches the lower alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the pppoe-server session-threshold command, and identify whether the lower alarm threshold configured is appropriate. ¡ If the configured lower alarm threshold is too high, proceed with step 2. ¡ If the configured lower alarm threshold is appropriate, proceed with step 3. 2. Execute the pppoe-server session-threshold command in system view on the device to modify the lower alarm threshold. 3. Execute the display aaa abnormal-offline-record access-type ppp command to identify whether a large number of PPPoE users are going offline abnormally. ¡ If yes, process accordingly based on the specific reason for going offline. ¡ If not, execute the display aaa offline-record access-type ppp command to view the reasons for PPPoE users to go offline and resolve the issues accordingly. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
|
Message text |
The PPPoE session number on chassis [INT32] slot [INT32] is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Chassis number. $2: Slot number. $3: Lower alarm threshold for the online PPPoE session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPPOES/4/PPPOES_SESSIONS_LOWER_THRESHOLD: The PPPoE session number on chassis 1 slot 1 is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of users might go offline because of abnormal reasons. Identify whether a large number of users go offline abnormally. |
|
Cause |
· The device-level lower alarm threshold for the online PPPoE user count is too high. · Users go offline, and the number of PPPoE users on the device reaches the lower alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the pppoe-server session-threshold command, and identify whether the lower alarm threshold configured is appropriate. ¡ If the configured lower alarm threshold is too high, proceed with step 2. ¡ If the configured lower alarm threshold is appropriate, proceed with step 3. 2. Execute the pppoe-server session-threshold command in system view on the device to modify the lower alarm threshold. 3. Execute the display aaa abnormal-offline-record access-type ppp command to identify whether a large number of PPPoE users are going offline abnormally. ¡ If yes, process accordingly based on the specific reason for going offline. ¡ If not, execute the display aaa offline-record access-type ppp command to view the reasons for PPPoE users to go offline and resolve the issues accordingly. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPPOES_SESSIONS_RECOVER_NORMAL
|
Message text |
The PPPoE session number has recovered to normal state. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
PPPOES/5/PPPOES_SESSIONS_RECOVER_NORMAL: The PPPoE session number has recovered to normal state. |
|
Impact |
The number of PPPoE users on the device meets the expectation. |
|
Cause |
PPPoE users come online or go offline, and the number of online PPPoE sessions has been restored to the set normal range. |
|
Recommended action |
No action is required. |
|
Message text |
The PPPoE session number on slot [INT32] has recovered to normal state. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
PPPOES/5/PPPOES_SESSIONS_RECOVER_NORMAL: The PPPoE session number on slot 1 has recovered to normal state. |
|
Impact |
The number of PPPoE users on the device meets the expectation. |
|
Cause |
PPPoE users come online or go offline, and the number of online PPPoE sessions on the specified slot has been restored from the alarm state to the set normal range. |
|
Recommended action |
No action is required. |
|
Message text |
The PPPoE session number on chassis [INT32] slot [INT32] has recovered to normal state. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
PPPOES/5/PPPOES_SESSIONS_RECOVER_NORMAL: The PPPoE session number on chassis 1 slot 1 has recovered to normal state. |
|
Impact |
The number of PPPoE users on the device meets the expectation. |
|
Cause |
PPPoE users come online or go offline, and the number of online PPPoE sessions on the specified slot of the specified chassis has been restored from the alarm state to the set normal range. |
|
Recommended action |
No action is required. |
PPPOES_SESSIONS_UPPER_THRESHOLD
|
Message text |
The PPPoE session number is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper alarm threshold for the online PPPoE session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPPOES/4/PPPOES_SESSIONS_UPPER_THRESHOLD: The PPPoE session number is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online PPPoE users might exceed the device capability, and the subsequent PPPoE users might fail to come online. |
|
Cause |
The device-level upper alarm threshold for the online PPPoE user count is too low. Users come online, and the number of PPPoE users on the device reaches the upper alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the pppoe-server session-threshold command, and identify whether the upper alarm threshold configured is appropriate. ¡ If the configured upper alarm threshold is too low, proceed with step 2. ¡ If the configured upper alarm threshold is appropriate, proceed with step 3. 2. Execute the pppoe-server session-threshold command in system view on the device to modify the upper alarm threshold. 3. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
|
The PPPoE session number on slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
|
Variable fields |
$1: Slot number. $2: Upper alarm threshold for the online PPPoE session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPPOES/4/PPPOES_SESSIONS_UPPER_THRESHOLD: The PPPoE session number on slot 1 is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online PPPoE users might exceed the device capability, and the subsequent PPPoE users might fail to come online. |
|
Cause |
· The device-level upper alarm threshold for the online PPPoE user count is too low. · Users come online, and the number of PPPoE users on the device reaches the upper alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the pppoe-server session-threshold command, and identify whether the upper alarm threshold configured is appropriate. ¡ If the configured upper alarm threshold is too low, proceed with step 2. ¡ If the configured upper alarm threshold is appropriate, proceed with step 3. 2. Execute the pppoe-server session-threshold command in system view on the device to modify the upper alarm threshold. 3. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
|
Message text |
The PPPoE session number on chassis [INT32] slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Chassis number. $2: Slot number. $3: Upper alarm threshold for the online PPPoE session count. |
|
Severity level |
4 (Warning) |
|
Example |
PPPOES/4/PPPOES_SESSIONS_UPPER_THRESHOLD: The PPPoE session number on chassis 1 slot 1 is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online PPPoE users might exceed the device capability, and the subsequent PPPoE users might fail to come online. |
|
Cause |
· The device-level upper alarm threshold for the online PPPoE user count is too low. · Users come online, and the number of PPPoE users on the device reaches the upper alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the pppoe-server session-threshold command, and identify whether the upper alarm threshold configured is appropriate. ¡ If the configured upper alarm threshold is too low, proceed with step 2. ¡ If the configured upper alarm threshold is appropriate, proceed with step 3. 2. Execute the pppoe-server session-threshold command in system view on the device to modify the upper alarm threshold. 3. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
PPPoE messages
This section contains PPPoE messages.
VBRAS_ACL_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DPPPOE/4/VBRAS_ACL_NORES: -MDC=1-Slot=3; No enough resource. |
|
Explanation |
When the device is configured as a DP in control-/data-plane separated mode, the hardware resources are insufficient for adding vBRAS protocols. |
|
Recommended action |
1. Use the display qos-acl resource command to check the IPv4 ACL and IPv6 ACL resource usage on the card. 2. If the problem persists, contact Technical Support. |
PADIDEFEND_ACL_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DPPPOE/4/PADIDEFEND_ACL_NORES: -MDC=1-Slot=3; No enough resource. |
|
Explanation |
For PADI anti-attack on a card, the upper limit of ACL resources has been reached. |
|
Recommended action |
Contact Technical Support. |
PADIDEFEND_MAC_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DPPPOE/4/PADIDEFEND_MAC_NORES: -MDC=1-Slot=3; No enough resource. |
|
Explanation |
For PADI anti-attack on a card, the upper limit of ARP MAC entries has been reached. |
|
Recommended action |
No action is required. |
PPPOE_DHCPV6_NORES
|
Message text |
The resources are insufficient. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DPPPOE/4/PPPOE_DHCPV6_NORES: -MDC=1-Slot=3; The resources are insufficient. |
|
Explanation |
When an interface with PPPoE server enabled was bound to a VT interface, the system failed to deploy the DHCPv6 protocol because of insufficient TCAM resources. |
|
Recommended action |
1. Release TCAM resources by disabling inactive protocols on the VT interface or unbinding inactive interfaces from the VT interface, unbind the interface from the VT interface, and then bind the interface to the VT interface. 2. If DHCPv6 is used only for IPv6 address assignment, assign IP addresses to clients through other address assignment methods. For example, clients can obtain IPv6 prefixes from the RA packets of the ND protocol and generate IPv6 addresses based on the prefixes. |
SESSION_LIMITED
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DPPPOE/4/SESSION_LIMITED: -MDC=1-Slot=3; No enough resource. |
|
Explanation |
The PPPoE session or hardware resources were insufficient for completing the operation. For example, when the number of online PPPoE users reached the upper limit, new users cannot come online. |
|
Recommended action |
1. Check whether the number of existing PPPoE sessions on the card reached the card specifications by using the display pppoe-server session summary slot command. 2. If the problem persists, contact Technical Support. |
SESSION_TB_NORES
|
Message text |
No enough resource |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DPPPOE/4/SESSION_TB_NORES: -MDC=1-Slot=3; No enough resource |
|
Explanation |
The PPPoE TB resources were insufficient for completing the operation. For example, when the online PPPoE users have used all TB resources, new users cannot come online. |
|
Recommended action |
1. Use the display qos-acl resource command to check the TB resource usage on the card. 2. If the problem persists, contact Technical Support. |
REDIRECT_ACL_NORES
|
Message text |
No enough resource |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DPPPOE/4/REDIRECT_ACL_NORES: -MDC=1-Slot=3; No enough resource |
|
Explanation |
When PPPoE is enabled, the ACL resources for redirection are insufficient. |
|
Recommended action |
1. Use the display qos-acl resource command to check the IPv4 ACL and IPv6 ACL resource usage on the card. 2. If the problem persists, contact Technical Support. |
PPPoE messages
This section contains PPPoE messages.
VBRAS_ACL_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DPPPOE/4/VBRAS_ACL_NORES: -MQC=1-Slot=3; No enough resource. |
|
Impact |
The device cannot switch to the UP mode, and the CUPS network does not take effect. |
|
Cause |
The hardware resources are insufficient for the device to switch to a UP operating in CUPS mode. |
|
Recommended action |
1. Execute the display qos-acl resource command to view the IPv4 ACL resource usage on the specified card. 2. Execute the display acl all command to view the usage of all IPv4 ACL resources on the specified card. 3. Check the ACL and QoS configurations on the device, and delete any unnecessary configurations based on the actual situation. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PADIDEFEND_ACL_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DPPPOE/4/PADIDEFEND_ACL_NORES: -MQC=1-Slot=3; No enough resource. |
|
Impact |
The PPPoE protocol packet attack prevention feature does not take effect. |
|
Cause |
The PADI attack prevention entries on the card have reached the limit. |
|
Recommended action |
1. Execute the display pppoe-server chasten per-interface command to display the ports that have suffered PADI attacks. 2. Execute the display acl all command to view the usage of all IPv4 ACL resources on the specified card. 3. Check the ACL and QoS configurations on the device, and delete any unnecessary configurations based on the actual situation. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PADIDEFEND_MAC_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DPPPOE/4/PADIDEFEND_MAC_NORES: -MQC=1-Slot=3; No enough resource. |
|
Impact |
The PPPoE user blocking feature does not take effect. |
|
Cause |
The MAC resources used for the PPPoE user blocking feature on the card have reached the limit. |
|
Recommended action |
1. Execute the display pppoe-server chasten statistics command to view statistics on PPPoE users detected by the blocking feature. 2. Execute the pppoe-server connection chasten per-interface command to configure PPPoE protocol packet attack prevention. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PPPOE_DHCPV6_NORES
|
Message text |
The resources are insufficient. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DPPPOE/4/PPPOE_DHCPV6_NORES: -MDC=1-Slot=3; The resources are insufficient. |
|
Impact |
The users that use DHCPv6 negotiation cannot come online. |
|
Cause |
When the PPPoE server protocol is enabled on an interface and the interface is bound to a Virtual-Template interface, the DHCPv6 protocol fails to be deployed because of insufficient TCAM resources. |
|
Recommended action |
1. In Virtual-Template interface view, use the display this command to view the configuration of the Virtual-Template interface. Disable unused configurations on the Virtual-Template interface to release TCAM resources. 2. Execute the display interface virtual-template brief command to view summary information of all Virtual-Template interfaces. Then, execute the undo pppoe-server bind command on the corresponding interface to unbind the Virtual-Template interface in down state to release the TCAM resources. 3. If only IPv6 addresses are allocated through DHCPv6, you can allocate addresses to clients through other allocation methods (for example, configure clients to obtain IPv6 address prefixes through RA messages in the ND protocol) without releasing TCAM resources. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SESSION_LIMITED
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DPPPOE/4/SESSION_LIMITED: -MQC=1-Slot=3; No enough resource. |
|
Impact |
New users cannot come online. |
|
Cause |
The current operation cannot be completed, because the PPPoE session or hardware resources are insufficient. For example, when the online PPPoE users reach the limit, new users cannot come online. |
|
Recommended action |
1. Execute the display pppoe-server session summary slot slot-number command to view the number of PPPoE sessions on the specified card. 2. If the number of PPPoE sessions on the card exceeds the limit, move the users waiting to come online to other cards. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SESSION_TB_NORES
|
Message text |
No enough resource |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
DPPPOE/4/SESSION_TB_NORES: -MDC=1-Slot=3; No enough resource |
|
Impact |
New users cannot come online. |
|
Cause |
The current operation cannot be completed, because the PPPoE TB resources are insufficient. For example, if the online PPPoE users have exhausted the TB resources, new users cannot come online. |
|
Recommended action |
1. Execute the display qos-acl resource command to check the usage of TB resources on the specified card. 2. If the usage of TB resources on the card exceeds the limit, move the users waiting to come online to interfaces of other chips of the same card or to other cards. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PTP
This section contains PTP messages.
PTP_EXT_TIME_PORT_DISCONNECT
|
Message text |
The external time port became disconnect. (ExtTimePortType=[STRING]) |
|
Variable fields |
$1: External clock source type, including: · ToD0: First ToD clock · ToD1: Second ToD clock |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_EXT_TIME_PORT_DISCONNECT: The external time port became disconnect. (ExtTimePortType=ToD0) |
|
Impact |
The device is unable to synchronize with the clock source |
|
Cause |
The device is unable to receive the clock signal from the external clock source or the connection between the external clock source and the local device is disconnected |
|
Recommended action |
Please acknowledge if the PTP interface connecting the external clock source is UP: · If the PTP interface is UP, collect the configuration file, log file, and alarms, and then contact Technical Support. · If the PTP interface is DOWN, it indicates a link fault or interface DOWN, troubleshoot and recover the fault link |
PTP_EXT_TIME_PORT_RECOVER
|
Message text |
The external time port status resumed. (ExtTimePortType=[STRING]) |
|
Variable fields |
$1: External clock source type, including: · ToD0: First ToD clock · ToD1: Second ToD clock |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_EXT_TIME_PORT_RECOVER: The external time port status resumed. (ExtTimePortType=ToD0) |
|
Impact |
No negative impacts on the system. |
|
Cause |
The device receives the clock signal from the external clock source again, and the physical link connected to the external clock source and this device is restored |
|
Recommended action |
No action is required. |
PTP_FREQUENCY_LOCK
|
Message text |
Clock frequency resumed to locked state. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PTP/3/PTP_FREQUENCY_LOCK: Clock frequency resumed to locked state. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The clock recovers from frequency loss of lock state to normal. |
|
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 (Error) |
|
Example |
PTP/3/PTP_FREQUENCY_NOT_LOCK: Clock frequency not in locked state. |
|
Impact |
Will affect the accuracy of the system clock |
|
Cause |
Clock frequency unlock alarm, reasons include: the output frequency offset of the system clock exceeds +/-10ppm |
|
Recommended action |
After the device prints this alarm, did it print the PTP_FREQUENCY_LOCK log? · If the PTP_FREQUENCY_LOCK log is viewed, it means the device has just started or the frequency is flapping, No action is required. · If the PTP_FREQUENCY_LOCK log is not viewed, collect the configuration file, log file, and alarms, and then 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: Original Master Clock ID $2: Current Master Clock ID $3: New Clock Source Index $4: Interface Number that Previously Provided Clock Source for this Device $5: Current Interface Number Providing Clock Source for this Device $6: Interface Name that Previously Provided Clock Source for this Device $7: Interface Name Currently Providing Clock Source for this Device |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_MASTER_CLOCK_CHANGE: PTP master clock property changed. (OldMasterClockId=000FE2-FFFE-FF0000, CurrentMasterClockId=000FE2-FFFE-FF0001, NewSourceIfIndex=3, OldSourcePortNum=2, CurrentSourcePortNum=1, OldSourcePortName=GigabitEthernet1/0/2, CurrentSourcePortName=GigabitEthernet1/0/1) |
|
Impact |
No negative impacts on the system. |
|
Cause |
Master Clock Source attribute has changed, reasons include: · Changes in clock device attributes within the PTP domain, resulting in a higher priority clock source or a change in the path to obtain the clock source · Access to a higher priority clock source · Link fault where PTP interface receiving clock source signal is down or the PTP interface is DOWN |
|
Recommended action |
Normal operation information, No action is required. You can also continue to determine if the original PTP interface is faulty causing the clock source switchover. Execute the 'display ptp interface' command to check if there are any PTP interfaces in Disabled state. If there are interfaces in Disabled state, it indicates a PTP interface fault, please address the interface fault first. |
PTP_PKT_ABNORMAL
|
Message text |
Received an abnormal PTP packet. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PTP/6/PTP_PKT_ABNORMAL: Received an abnormal PTP packet. |
|
Impact |
· Occasionally receiving one or two abnormal PTP packets has no impact on the system. · If multiple abnormal PTP packets are continuously received, distinguish the source of the abnormal PTP packets: ¡ If the source of the abnormal PTP packets is the clock source, this issue will affect clock synchronization between the device and the clock source. ¡ If the source of the abnormal PTP packets is a downstream device, this issue will affect clock synchronization between the device and the downstream device. |
|
Cause |
When the device receives the first abnormal PTP packet, it generates this log message, creates a 10-minute timer, and calculates the number of abnormal PTP packets received within the 10 minutes. After the timer expires, the device generates log message PTP_PKT_ABNORMALCOUNT and deletes the 10-minute timer. When a processing cycle ends and the device receives abnormal PTP packets again, the device will start a new processing cycle. Possible reasons for abnormal PTP packets: · Error packets occur during network transmission. · The PTP packets generated by the peer end have defects. For example, the TimeSource, TimeTraceable, or FreqencyTraceable field does not meet the requirement. |
|
Recommended action |
1. Execute the display ptp statistics command to identify the incoming interface and packet type of abnormal PTP packets. ¡ If the incoming interface is the interface connected to the clock source, execute the display ptp corrections command to view the value of the Corrections(s,ns) field. If the seconds part is 0, it indicates that the device and the clock source are synchronized, and no action is required. If the seconds part is non-zero, it indicates that the device and the clock source are not synchronized. In this case, proceed to step 2. ¡ If the incoming interface is not the interface connected to the clock source, proceed to step 2. 2. Execute the debugging ptp packet receive command to enable received PTP packet debugging, and view the detailed information about the received PTP packets. Pay attention to the encapsulation format, source address, destination address, PTP protocol type (profile), PTP domain number (domain), and Flag bit values carried in the PTP packets. If the value of a certain field does not match the corresponding configuration of this device, modify the value of that field to be consistent at both ends. 3. If the issue persists, collect the device configuration file, log information, and alarm information, and contact Technical. |
PTP_PKT_ABNORMALCOUNT
|
Message text |
Received [ULONG] abnormal PTP packets in the last 10 minutes. |
|
Variable fields |
$1: Number of PTP defect packets in the last 10 minutes. |
|
Severity level |
6 (Informational) |
|
Example |
PTP/6/PTP_PKT_ABNORMALCOUNT: Received 300 abnormal PTP packets in the last 10 minutes. |
|
Impact |
· Occasionally receiving one or two abnormal PTP packets has no impact on the system. · If multiple abnormal PTP packets are continuously received, distinguish the source of the abnormal PTP packets: ¡ If the source of the abnormal PTP packets is the clock source, this issue will affect clock synchronization between the device and the clock source. ¡ If the source of the abnormal PTP packets is a downstream device, this issue will affect clock synchronization between the device and the downstream device. |
|
Cause |
When the device receives the first abnormal PTP packet, it generates this log message, creates a 10-minute timer, and calculates the number of abnormal PTP packets received within the 10 minutes. After the timer expires, the device generates log message PTP_PKT_ABNORMALCOUNT and deletes the 10-minute timer. When a processing cycle ends and the device receives abnormal PTP packets again, the device will start a new processing cycle. Possible reasons for abnormal PTP packets: · Error packets occur during network transmission. · The PTP packets generated by the peer end have defects. For example, the TimeSource, TimeTraceable, or FreqencyTraceable field does not meet the requirement. |
|
Recommended action |
1. Execute the display ptp statistics command to identify the incoming interface and packet type of abnormal PTP packets. ¡ If the incoming interface is the interface connected to the clock source, execute the display ptp corrections command to view the value of the Corrections(s,ns) field. If the seconds part is 0, it indicates that the device and the clock source are synchronized, and no action is required. If the seconds part is non-zero, it indicates that the device and the clock source are not synchronized. In this case, proceed to step 2. ¡ If the incoming interface is not the interface connected to the clock source, proceed to step 2. 2. Execute the debugging ptp packet receive command to enable received PTP packet debugging, and view the detailed information about the received PTP packets. Pay attention to the encapsulation format, source address, destination address, PTP protocol type (profile), PTP domain number (domain), and Flag bit values carried in the PTP packets. If the value of a certain field does not match the corresponding configuration of this device, modify the value of that field to be consistent at both ends. 3. If the issue persists, collect the device configuration file, log information, and alarm information, and contact Technical. |
PTP_PKTLOST
|
Message text |
PTP packets were lost. (PktType=[STRING]) |
|
Variable fields |
$1: PTP message types, including: ¡ Delay_Resp: PTP Delay_Resp message ¡ Announce: PTP Announce message ¡ Sync: PTP Sync message ¡ Pdelay_Resp: PTP Pdelay_Resp message |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_PKTLOST: PTP packets were lost. (PktType=Announce) |
|
Impact |
Occasional packet loss does not affect time synchronization. If packet loss persists for a long time, it will affect clock synchronization |
|
Cause |
The slave port detects Announce, Delay_Resp, and Sync messages. If no messages are received after the detection time, the messages are considered lost |
|
Recommended action |
Use the 'display ptp statistics' command on the PTP slave clock device to check if the receive message statistics count is increasing when printing this log · If it is increasing, it indicates a timeout caused by excessive link delay, and N/A should be processed · If it is not increasing, use the 'display ptp statistics' command on the PTP master clock device to check if the send message statistics count is increasing ¡ If it is increasing, it indicates a link fault causing the remote end to timeout without receiving the message. Troubleshoot and recover the fault link ¡ If it is not increasing, collect the configuration file, log file, and alarms, and then contact Technical Support. |
PTP_PKTLOST_RECOVER
|
Message text |
PTP packets lost were recovered. (PktType=[STRING]) |
|
Variable fields |
$1: PTP message types, including: ¡ Delay_Resp: PTP Delay_Resp message ¡ Announce: PTP Announce message ¡ Sync: PTP Sync message ¡ Pdelay_Resp: PTP Pdelay_Resp message |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_PKTLOST_RECOVER: PTP packets lost were recovered. (PktType =Announce) |
|
Impact |
No negative impacts on the system. |
|
Cause |
Recovery from PTP message loss alarm state. This log will only be printed when the Slave port detects a timeout for Announce, Delay_Resp, or Sync messages and then receives them again, or when the device itself transitions from a Slave clock to a Master clock due to a long timeout period |
|
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 received by the PTP interface $4: Clock source port number received by the PTP interface $5: Clock source hop count received by the PTP interface $6: Current device's master clock ID |
|
Severity level |
5 (Notification) |
|
Example |
PTP/5/PTP_PORT_BMCINFO_CHANGE: The BMC info for port 1 changed. (PortName=GigabitEthernet1/0/1, PortSourceId=000FE2-FFFE-FF0001, PortSourcePortNum=1, PortSourceStepsRemoved=5, CurrentMasterClockId=000FE2-FFFE-FF0000) |
|
Impact |
May result in clock source change |
|
Cause |
Changes in clock source information such as clock source ID, clock source port number, or clock source hop count received by the PTP interface |
|
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: The current status of the PTP interface, including: ¡ Master: Interface status is Master, broadcasting time information externally ¡ Slave: Interface status is Slave, tracking external time information ¡ Passive: Interface status is Passive (calculated after receiving the peer's Announce message), not tracking external time information, and not broadcasting time information externally ¡ Listening: Interface status is Listening (after initialization, entering Listening status), not tracking external time information, and not broadcasting time information externally ¡ Faulty: Interface status is Faulty, this status is an error status of the PTP protocol (i.e., error detection), the interface does not process PTP protocol messages ¡ Initializing: Interface status is Initializing, the interface is in the initialization state, and the interface does not process protocol messages ¡ Premaster: Interface status is Premaster, a temporary status before the Master status ¡ Disable: Interface status is Disabled, the PTP protocol is not running on the interface, and the interface does not process protocol messages ¡ Uncalibrated: Interface status is Uncalibrated, a temporary status before the Slave status $4: The status of the PTP interface before the change, including: ¡ Master: Interface status is Master, broadcasting time information externally ¡ Slave: Interface status is Slave, tracking external time information ¡ Passive: Interface status is Passive (calculated after receiving the peer's Announce message), not tracking external time information, and not broadcasting time information externally ¡ Listening: Interface status is Listening (after initialization, entering Listening status), not tracking external time information, and not broadcasting time information externally ¡ Faulty: Interface status is Faulty, this status is an error status of the PTP protocol (i.e., error detection), the interface does not process PTP protocol messages ¡ Initializing: Interface status is Initializing, the interface is in the initialization state, and the interface does not process protocol messages ¡ Premaster: Interface status is Premaster, a temporary status before the Master status ¡ Disable: Interface status is Disabled, the PTP protocol is not running on the interface, and the interface does not process protocol messages ¡ Uncalibrated: Interface status is Uncalibrated, a temporary status before the Slave status |
|
Severity level |
5 (Notification) |
|
Example |
PTP/5/PTP_PORT_STATE_CHANGE: PTP port state changed. (IfIndex=2, PortName=GigabitEtherne1/0/1, PortState=Slave, OldPortState=Master) |
|
Impact |
No negative impacts on the system. |
|
Cause |
The reasons for the change in the PTP interface status include: · The clock device attribute in the PTP domain has changed, such as precedence, clock grade, clock accuracy, and the NotSlave attribute of the interface · A higher priority clock source is accessed · The PTP interface is in a link fault or the PTP interface is DOWN |
|
Recommended action |
Faulty and Disable states need attention, other states are transient intermediate states, No action is required. · The number of PdelayResp messages received by the interface is not equal to the number of PdelayRespFollowUp messages, which will cause the interface to be in the Faulty state. The following measures can be taken: · Execute the 'display ptp statistics' command on the peer to check the values of the PdelayResp and PdelayRespFollowUp fields in the Sent packets. If these values are not equal, the PTP function on the peer is abnormal. Try to recover by disabling and then enabling the PTP function on the interface a. Execute the 'display ptp statistics' command on this end and check the values of the PdelayResp and PdelayRespFollowUp fields in the Received packets. If these values are not equal to the values of the PdelayResp and PdelayRespFollowUp fields on the peer's Sent packets, locate the network packet loss problem b. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. · The interface does not receive Announce messages, which will cause the interface to be in the Disable state. The following measures can be taken: c. Calculate the number of Announce messages that should be sent by the peer during a specified time period based on the configuration of the 'ptp announce-interval' command, and execute the 'display ptp statistics' command on the peer to check the value of the Announce field in the Sent packets. If these two values are not equal, locate the problem of the peer not sending Announce messages d. Execute the 'display ptp statistics' command on this end and check the value of the Announce field in the Received packets. If this value is not equal to the value of the Announce field in the Sent packets on the peer, locate the Announce message network packet loss problem e. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical 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, values include: ¡ Local: Local clock ¡ Tod0: First ToD clock ¡ Tod1: Second ToD clock $2: First priority $3: Second priority $4: Time level of the clock source $5: Time accuracy of the clock source $6: Category of the best clock, values include: ¡ Atomic clock: Atomic clock ¡ GPS: Global Positioning System ¡ Handset: Handheld device ¡ Internal oscillator: Internal oscillator ¡ NTP: Network Time Protocol ¡ Other: Other ¡ PTP: Precision Time Protocol ¡ Terrestrial radio: Terrestrial radio ¡ Unknown. |
|
Severity level |
5 (Notification) |
|
Example |
PTP/5/PTP_SRC_CHANGE: Clock source property changed.(SourceName=LOCAL,Priority1=128,Priority2=128,ClockClass=248,ClockAccuracy=254,ClockSourceType=(Internal oscillator)). |
|
Impact |
No negative impacts on the system. |
|
Cause |
Clock source attributes change, reasons include: · User changed the clock source attributes through the command line · Received a higher accuracy external clock source |
|
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 (Warning) |
|
Example |
PTP/4/PTP_SRC_CLASS_BELOW_THRESHOLD: The clock source class fell below the threshold. |
|
Impact |
It affects time synchronization between the device and the clock source. |
|
Cause |
The alarm threshold for clock source class is exceeded. Possible reasons include: · When the device obtains a clock source through group packets on the PTP input interface, the clock class of the currently selected PTP local clock source is higher than the clock class threshold, and the stepsRemoved value of the PTP clock source is 0. · When the device obtains a clock source through the TOD input interface, the clock class of the currently selected external TOD clock source is higher than the clock class threshold. |
|
Recommended action |
1. Use the display ptp clock command to view the current clock source class in the Class field. If the class does not comply with network planning, increase the clock class on the clock source device or switch to a clock source with a higher clock class. 2. Or use the ptp alarm-threshold clock-source-class command in system view to modify the alarm threshold for clock source class. 3. If the issue persists, collect the device configuration file, log information, and alarm information, and contact Technical. |
PTP_SRC_CLASS_RECOVER
|
Message text |
The clock source class crossed the threshold. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_SRC_CLASS_RECOVER: The clock source class crossed the threshold. |
|
Impact |
No negative impact on the system. |
|
Cause |
The input clock class of the clock source is higher than or equal to the clock source alarm threshold. |
|
Recommended action |
No action is required. |
PTP_SRC_SWITCH
|
Message text |
Clock source switched. (LastClockID=[STRING], CurrentClockID=[STRING]) |
|
Variable fields |
$1: ID of the previous clock source. $2: ID of the current clock source. |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_SRC_SWITCH: Clock source switched.(LastClockID=4CBD4E-FFFE-C00100,CurrentClockID=AA479F-FFFE-EE0200). |
|
Impact |
No negative impact on the system. |
|
Cause |
A new, better clock source joins the PTP domain, resulting in a switch of the clock source tracked by the device. |
|
Recommended action |
No action is required. |
PTP_TIME_LOCK
|
Message text |
Time resumed to locked state. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PTP/3/PTP_TIME_LOCK: Time resumed to locked state. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The clock recovers from the unlocked state to normal |
|
Recommended action |
No action is required. |
PTP_TIME_NOT_LOCK
|
Message text |
Time not in locked state. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PTP/3/PTP_TIME_NOT_LOCK: Time not in locked state. |
|
Impact |
Will affect the accuracy of the local clock |
|
Cause |
Clock unlocking alarm, reasons include: · When the time offset of the PTP clock source is greater than the unlock value, the PTP time is in an unlocked state, triggering clock unlocking logs · Daughtercard logical OR clock subboard hardware failure · The timestamp received by the DSP remains unchanged or the timestamp is incorrect |
|
Recommended action |
1. Execute the 'display interface' command to check if the PTP Slave interface has a link fault or interface down. If there is a link fault or interface down, exclude the fault recovery link 2. Measure network delay using functions such as iNQA and iFIT to confirm whether the increase in network delay has caused the clock offset provided by the clock source to be too large. If so, solve the problem of excessive network delay first ¡ Execute the 'display current-configuration | include "time-unlock"' command to check if the PTP time unlock threshold configuration is reasonable. If not, it can be modified using the 'ptp alarm-threshold time-unlock unlock-value' command |
PTP_TIME_OFFSET_EXCEED_THRESHOLD
|
Message text |
The PTP time offset exceeded the threshold. (TimeOffset=[UINT16], AlarmThresholdTimeOffset=[UINT16]) |
|
Variable fields |
$1: Source absolute time difference. $2: Alarm threshold for source absolute time difference. |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_TIME_OFFSET_EXCEED_THRESHOLD: The PTP time offset exceeded the threshold. (TimeOffset=500, AlarmThresholdTimeOffset=400) |
|
Impact |
No negative impact on the system. |
|
Cause |
The PTP source absolute time difference exceeded the threshold. The system compares the external reference time and PTP time, obtain the time difference between them, and generates this message if the difference exceeds the time deviation alarm threshold. |
|
Recommended action |
1. Log in to the clock source, and execute the display clock command to view the system time of the clock source. If the clock source undergoes a leap second, causing the clock to jump by 1 second (leap seconds generally occur at the end of June or December), it is a normal phenomenon and does not require handling. You can visit the website of Bureau International des Poids et Mesures (BIPM) to check if a time jump is necessary. 2. Use functions such as iNQA and iFIT to measure network latency and determine if an increase in network delay has caused excessive clock deviation from the clock source. If yes, resolve the network latency issue. 3. Use the display current-configuration | include "ptp alarm-threshold time-offset” command to verify if the log output parameters configured for PTP source absolute time difference are proper. If the configuration is not proper, use the ptp alarm-threshold time-offset command to modify the parameters. 4. The clock source quality might degrade. Please replace the clock source. |
PTP_TIME_OFFSET_RECOVER
|
Message text |
The PTP standard time offset resumed. (TimeOffset=[UINT16], AlarmThresholdTimeOffset=[UINT16]) |
|
Variable fields |
$1: Source absolute time difference. $2: Alarm threshold for source absolute time difference. |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_STANDARD_TIME_OFFSET_RECOVER: The PTP standard time offset resumed. (TimeOffset=300, AlarmThresholdTimeOffset=400) |
|
Impact |
No negative impact on the system. |
|
Cause |
The clock deviation provided by the clock source has returned to a normal range from being excessively large. |
|
Recommended action |
No action is required. |
PTP_TIME_SYNC
|
Message text |
Time resumed to synchronized state. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_TIME_SYNC: Time resumed to synchronized state. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device has returned to a normal state of clock synchronization. |
|
Recommended action |
No action is required. |
PTP_TIME_UNSYNC
|
Message text |
Time changed to unsynchronized state. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_TIME_UNSYNC: Time changed to unsynchronized state. |
|
Impact |
The system clock accuracy is affected. |
|
Cause |
The device is in a state where clock synchronization cannot be performed. Possible reasons include: · Link failure or interface DOWN occurs, causing the device to have no clock source to track. · The clock source priority on this device is configured too high, causing the local device to be in local state and unable to synchronize with the time signals of other devices. |
|
Recommended action |
1. Use the display ptp interface brief command to identify whether the device has a PTP Slave interface. ¡ If yes, collect the device configuration file, log information, and alarm information, and contact Technical Support. ¡ If no, proceed to step 2. 2. Use the display ptp clock command to identify whether the Clock type field displays a ToD type. ¡ If yes, proceed to step 3. ¡ If no, it indicates that the device does not a clock source for synchronization. Please connect the device to a clock source correctly. 3. Identify whether the receiving delay correction time for the ToD clock signal's input direction is configured through the ptp tod0 input command. ¡ If yes, collect the device configuration file, log information, and alarm information, and contact Technical Support. ¡ If no, proceed to step 4. 4. Use the ptp tod0 input command to modify the receiving delay correction time for the ToD clock signal's input direction, and identify whether the device has output the PTP_TIME_SYNC log message. ¡ If yes, the issue has been resolved. ¡ If no, collect the device configuration file, log information, and alarm information, and contact Technical Support. |
PTP_TIMESTAMP_CHANGE
|
Message text |
The timestamp state turned to normal. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PTP/3/PTP_TIMESTAMP_CHANGE: The timestamp state turned to normal. |
|
Impact |
No negative impact on the system. |
|
Cause |
The timestamps carried in the packets received by this device have returned to a state of continuous change, indicating that the timestamp status is normal. Under normal circumstances, the timestamps in the PTP packets received by the device are continuously changing. A static timestamp indicates an abnormal state. This log is only output when the timestamps transition from an abnormal to a normal state. |
|
Recommended action |
No action is required. |
PTP_TIMESTAMP_UNCHANGE
|
Message text |
The timestamp state turned to abnormal. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PTP/3/PTP_TIMESTAMP_UNCHANGE: The timestamp state turned to abnormal. |
|
Impact |
The system clock accuracy is affected. |
|
Cause |
The timestamps carried in the packets received by this device are not changing, indicating an abnormal timestamp status. Under normal circumstances, the timestamps in the PTP packets received by the device are continuously changing. A static timestamp indicates an abnormal state. |
|
Recommended action |
Execute the debugging ptp packet command in user view on the local device to enable PTP packet debugging to output information about the received PTP packets. 1. Observe whether the timestamps in the Sync or Follow_up packets increase steadily with the growth of the packet sequence number. Theoretically, timestamps should increase linearly as the packet sequence number increases. 2. If the timestamp remains unchanged, it indicates an anomaly in the upstream device. Resolve issues on the upstream device. 3. If the timestamps increase steadily, collect the device configuration file, log information, and alarm information, and contact Technical 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 deviation cumulative sum and peak-to-peak value. $2: Alarm threshold for the PTP time deviation cumulative sum and peak-to-peak value. |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_TIMOFFSUM_PK-PK_ALARM: The PTP time offset sum exceeded the threshold. (TimeOffsetSum=500, TimeOffsetSumAlarmThreshold=400) |
|
Impact |
Clock synchronization accuracy might be affected. |
|
Cause |
The PTP time deviation cumulative sum and peak-to-peak value exceeded the threshold. |
|
Recommended action |
1. Use functions such as iNQA and iFIT to measure network latency and determine if an increase in network delay has caused excessive clock deviation from the clock source. If yes, resolve the network latency issue. 2. The clock source quality might degrade. Please replace the clock source. 3. Execute the display current-configuration | include "time-offset-sum pk-pk" command to check if the configured log output parameters for the PTP source time deviation cumulative sum and peak-to-peak value are reasonable. If they are not reasonable, you can use the ptp alarm-threshold time-offset-sum pk-pk command to modify the parameters. 4. If the issue persists, collect the device configuration file, log information, and alarm information, and contact Technical. |
PTP_TIMOFFSUM_PK-PK_RECOVER
|
Message text |
The PTP time offset sum resumed. (TimeOffsetSum=[UINT16], TimeOffsetSumAlarmThreshold=[UINT16]) |
|
Variable fields |
$1: PTP time deviation cumulative sum and peak-to-peak value. $2: Alarm threshold for the PTP time deviation cumulative sum and peak-to-peak value. |
|
Severity level |
4 (Warning) |
|
Example |
PTP/4/PTP_TIMOFFSUM_PK-PK_RECOVER: The PTP time offset sum resumed. (TimeOffsetSum=300, TimeOffsetSumAlarmThreshold=400) |
|
Impact |
No negative impact on the system. |
|
Cause |
The PTP time deviation cumulative sum and peak-to-peak value have returned to the normal range. |
|
Recommended action |
No action is required. |
PWDCTL messages
This section contains password control messages.
PWDCTL_ADD_BLACKLIST
|
Message text |
User [STRING] from [IPADDR] was added to the blacklist for wrong password input. |
|
Variable fields |
$1: Username. $1: User IP address. |
|
Severity level |
4 (Warning) |
|
Example |
PWDCTL/4/PWDCTL_ADD_BLACKLIST: User hhh from 1.1.1.1 was added to the blacklist for wrong password input. |
|
Impact |
The user is added to the blacklist without being locked. However, when the maximum login attempts with incorrect passwords are reached, the user account will be locked. |
|
Cause |
The user entered an incorrect password for login and is added to the password control blacklist. |
|
Recommended action |
Enter the correct password to log in to the device. |
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 (Informational) |
|
Example |
PWDCTL/6/PWDCTL_CHANGE_PASSWORD: hhh changed the password because It is the first login of the account. |
|
Impact |
No negative impact on the system. |
|
Cause |
A user must change the password in one of the following conditions: · A user logs in to the device for the first time and the password change at first login feature is enabled. · The user password has exceeded the password aging time. · The user password length is less than the minimum password length. · The user password does not match the password complexity checking policy. · Device management users log in to the device with the default password via Telnet, SSH, HTTP, and HTTPS. This message is generated after you change the password. |
|
Recommended action |
After a user changes the password, log in to the device again with the new password. |
PWDCTL_DELETE_BLACKLIST
|
Message text |
User [STRING] was deleted from the blacklist. |
|
Variable fields |
$1: Username. |
|
Severity level |
5 (Notification) |
|
Example |
PWDCTL/5/PWDCTL_DELETE_BLACKLIST: User hhh was deleted from the blacklist. |
|
Impact |
No negative impact on the system. |
|
Cause |
· The user account is removed from the password control blacklist. · The administrator uses the reset password-control blacklist command to remove the user account from the password control blacklist. |
|
Recommended action |
Use the username that is removed from the blacklist to log in to the device again. |
PWDCTL_FAILED_TO_OPENFILE
|
Message text |
Failed to create or open the password file. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PWDCTL/3/PWDCTL_FAILED_TO_OPENFILE: Failed to open the password file. |
|
Impact |
The password control feature is not available. |
|
Cause |
· The storage space is insufficient in the system. · The running memory is insufficient in the system. |
|
Recommended action |
1. Execute the dir command in user view to view the remaining storage space. If the remaining storage space is insufficient, delete unnecessary files to release the space. If the remaining storage space is sufficient, go to step 2. 2. Release memory resources. For example, execute the logfile save command to save the content from the log file buffer to the log file to release memory resources occupied by the log file buffer. 3. Execute the display memory to display memory usage information. ¡ If the memory usage does not drop below the alarm threshold, execute the display process command to check the memory usage of the user-mode processes. If a process uses a large amount of memory and is not required, you can enable or disable the corresponding software feature for that process to release memory. ¡ If the memory usage drops below the alarm threshold, the memory alarm is cleared and the password control feature will continue to take effect. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PWDCTL_FAILED_TO_WRITEPWD
|
Message text |
Failed to write the password records to file. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PWDCTL/3/PWDCTL_FAILED_TO_WRITEPWD: Failed to write the password records to file. |
|
Impact |
A user failed to log in to the device. |
|
Cause |
The storage space is insufficient in the system. |
|
Recommended action |
Execute the dir command in user view to view the remaining storage space: · If the remaining storage space is insufficient, delete unnecessary files to release the space. · If the remaining storage space is sufficient, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PWDCTL_NOENOUGHSPACE
|
Message text |
Not enough free space on the storage media where the file is located. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PWDCTL/3/PWDCTL_NOENOUGHSPACE: Not enough free space on the storage media where the file is located. |
|
Impact |
The password control feature failed to be configured. |
|
Cause |
The memory space is insufficient 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 view the remaining storage space in the system. · If the remaining storage space is insufficient, delete unnecessary files to release the space. · If the remaining storage space is sufficient, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PWDCTL_NOTFOUNDUSER
|
Message text |
Can't find the username in the file. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
PWDCTL/3/PWDCTL_NOTFOUNDUSER: Can't find the username in the file. |
|
Impact |
The user password failed to be configured. The user cannot log in to the device. |
|
Cause |
· The LAUTHD process is abnormal. · The local user configuration is abnormal. |
|
Recommended action |
1. Disable the password control feature and then enable the password control feature. If the issue persists, go to step 2. 2. Create a local user. If the issue persists, go to step 3. 3. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PWDCTL_UPDATETIME
|
Message text |
Last login time updated after clock update. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
PWDCTL/6/PWDCTL_UPDATETIME: Last login time updated after clock update. |
|
Impact |
No negative impact on the system. |
|
Cause |
This message is generated when the last login time is updated. |
|
Recommended action |
No action is required. |
PWDCTL_USER_LOCK
|
Message text |
User [STRING] from [IPADDR] was [STRING] after making the maximum login attempts. |
|
Variable fields |
$1: Username. $2: User IP address. $3: The locking action to be taken after the user fails the maximum number of consecutive login attempts: ¡ locked in lock-time minutes—Locks the user account for a period of time. When the locking timer expires, users can use this user account to log in. ¡ permanently locked—Locks the user account permanently. |
|
Severity level |
4 (Warning) |
|
Example |
1. PWDCTL/4/PWDCTL_USER_LOCK: User hhh from 1.1.1.1 was locked in 1 minutes after making the maximum login attempts. 2. PWDCTL/4/PWDCTL_LOCKBLACKLIST: User hhh from 1.1.1.1 was permanently locked after making the maximum login attempts. |
|
Impact |
A user cannot log in to the device before the locking period expires. |
|
Cause |
The action to be taken after the user fails the maximum number of consecutive login attempts depends on the password-control login-attempt command. |
|
Recommended action |
Execute the display password-control blacklist command to identify whether the user account is locked because the maximum number of consecutive login attempts was exceeded. · If yes, make login attempts after the locking timer expires or remove the user account from the blacklist by executing reset password-control blacklist. · If no, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
PWDCTL_USER_UNLOCK
|
Message text |
User [STRING] was unlocked when the lock time expired. |
|
Variable fields |
$1: Username. |
|
Severity level |
5 (Notification) |
|
Example |
PWDCTL/5/PWDCTL_USER_UNLOCK: User hhh was unlocked when the lock time expired. |
|
Impact |
No negative impact on the system. |
|
Cause |
The user account is unlocked after the locking timer expires. |
|
Recommended action |
No action is required. |
PWDCTL_USER_INLOCKING
|
Message text |
User [STRING] from [IPADDR] has been locked due to exceeding the maximum number of login attempts. |
|
Variable fields |
$1: Username. $2: User IP address. |
|
Severity level |
5 (Notification) |
|
Example |
PWDCTL/5/PWDCTL_USER_INLOCKING: User hhh from 1.1.1.1 has been locked due to exceeding the maximum number of login attempts. |
|
Impact |
A user cannot log in to the device before the locking period expires. |
|
Cause |
Login attempts were made during the locking period of the user account. |
|
Recommended action |
Execute the display password-control blacklist command to identify whether the user account is locked because the maximum number of consecutive login attempts was exceeded. · If yes, make login attempts after the locking timer expires or remove the user account from the blacklist by executing reset password-control blacklist. · If no, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QACL messages
This section contains ACL and QoS messages.
ACL_PORTAL_NORES
|
Message text |
Insufficient resources for the portal session. Some functions of the session didn't take effect. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/ACL_PORTAL_NORES: -MDC=1-Slot=5 Insufficient resources for the portal session. Some functions of the session didn't take effect. |
|
Impact |
Some functions of the session (such as accounting and rate limiting) do not take effect. |
|
Cause |
During the portal session establishment, ACL resource insufficiency caused that some functions, such as session accounting and rate limit, did not take effect. |
|
Recommended action |
1. Use the display qos-acl resource command to check the ACL resource usage on the card. Use the display qos policy, display ip policy-based-route, and display packet-filter commands to view the ACLs that are referenced. Delete unnecessary ACLs to release resources. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
AGGPORT_CAR_NORES
|
Message text |
Due to insufficient hardware resources, the CAR action and the CBQ action applied to interface [STRING] did not work as expected. |
|
Variable fields |
$1: Layer 3 aggregate interface name. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/AGGPORT_CAR_NORES: -MDC=1-Slot=4; Due to insufficient hardware resources, the CAR action and the CBQ action applied to interface RAGG1000 did not work as expected. |
|
Impact |
The CAR action or the CBQ action in the QoS policy does not take effect. |
|
Cause |
This message is generated if hardware resources are insufficient when the state of a member port of the Layer 3 aggregate interface changes between Selected and Unselected. |
|
Recommended action |
1. Reconfigure the CAR settings and CBQ settings. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CHANNEL_BANDWIDTH_EXCEED
|
Message text |
The sum of channel bandwidth and network-slice bandwidth ([INT 32]) exceeds the bandwidth ([INT 32]) of interface [STRING]. |
|
Variable fields |
$1: Total channel bandwidth. $2: Interface bandwidth. $3: Interface name or interface index. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/CHANNEL_BANDWIDTH_EXCEED: -MDC=1-Slot=3; The sum of channel bandwidth and network-slice bandwidth (1100000 kbps) exceeds the bandwidth (1000000 kbps) of interface GigabitEthernet 3/0/1. |
|
Impact |
The channel bandwidth or network-slice bandwidth does not take effect. |
|
Cause |
This message is generated when the sum of channel bandwidth and network slice bandwidth exceeded the interface bandwidth. |
|
Recommended action |
1. Use the mode channel-bandwidth or slice-id flex-channel command to modify the channel bandwidth or network slice bandwidth. 2. Use the bandwidth command to modify the interface bandwidth. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
CHANNEL_EXCEED_MAXIMUM
|
Message text |
The sum of channel bandwidth and network-slice bandwidth ([INT 32]) exceeds the maximum bandwidth ([INT 32]). |
|
Variable fields |
$1: Sum of the channel bandwidth and network slice bandwidth. $2: Maximum channel bandwidth and network slice bandwidth issued by the interface. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/CHANNEL_EXCEED_MAXIMUM: -MDC=1-Slot=3; The sum of channel bandwidth and network-slice bandwidth (855000000 kbps) exceeds the maximum bandwidth (2000000000 kbps). |
|
Impact |
The channel bandwidth or network-slice bandwidth does not take effect. |
|
Cause |
This message is generated when the sum of channel bandwidth and network slice bandwidth exceeded the maximum bandwidth. |
|
Recommended action |
1. Use the mode channel-bandwidth or slice-id flex-channel command to modify the channel bandwidth or network slice bandwidth. 2. Use the bandwidth command to modify the interface bandwidth. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
COPP_RATE_EXCEED
|
Message text |
Security cpu-defend drop packets alarmed. SlotId=$1, Chip=$2, ClassifierName=$3, DropPkts=$4, Speed=$5 (DropThreshold=$6, Interval=$7, SpeedTh=$8). |
|
Variable fields |
$1: Slot number. $2: Chip number. $3: Traffic class name. $4: Number of dropped packets. $5: Rate of dropping packets. $6: Packet drop count threshold. $7: Statistics collection period. $8: Packet drop rate threshold. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/COPP_RATE_EXCEED: -MDC=1-Slot=4; Security cpu-defend drop packets alarmed. SlotId=4, Chip=0, ClassifierName=class1, DropPkts=53416502, Speed=821792(DropThreshold=1, Interval=65, SpeedTh=1000000). |
|
Impact |
The number or rate of packets of a traffic class dropped by the control plane exceeds the specified threshold. |
|
Cause |
This message is generated when the number or rate of packets of a traffic class dropped by the control plane exceeds the specified threshold. |
|
Recommended action |
1. Use the logging packet-drop { count-threshold | rate-threshold } * command modify the packet drop thresholds. 2. Lower the rate of packets sent to the control plane. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_AGGPORT_POLICY
|
Message text |
Failed to synchronize the QoS policy on an aggregate interface to a new member port. Not enough hardware resources available. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QOS_AGGPORT_POLICY:-MDC=1-Slot=5; Failed to synchronize the QoS policy on an aggregate interface to a new member port. Not enough hardware resources available. |
|
Impact |
The QoS policy applied to a Layer 3 aggregate interface does not take effect on new member ports. |
|
Cause |
The system failed to synchronize the QoS policy on a Layer 3 aggregate interface to a new member port, because hardware resources were insufficient. |
|
Recommended action |
1. Use the undo port link-aggregation group command to remove the member port from the Layer 3 aggregate interface. 2. Use the undo qos apply policy command to remove the QoS policy from the Layer 3 aggregate interface and use the qos apply policy command to reapply the QoS policy to the Layer 3 aggregate interface. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_CONGESTION_DETECTED
|
Message text |
Congestion is detected on an interface of chip [INT 32] in slot [INT 32]. |
|
Variable fields |
$1: Chip number. $2: Slot number of the card. |
|
Severity level |
3 (Error) |
|
Example |
QACL/3/QOS_CONGESTION_DETECTED: -MDC=1-Slot=3; Congestion is detected on an interface of chip 0 in slot 3. |
|
Impact |
The interface cannot forward traffic. |
|
Cause |
This message is generated when congestion is detected on an interface. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_CPUQUE_BLOCK
|
Message text |
The CPU protocol queue ([UINT32]) is blocked. |
|
Variable fields |
$1: CPU output queue ID in the range of 0 to 127. |
|
Severity level |
3 (Error) |
|
Example |
QACL/3/QOS_CPUQUE_BLOCK: -MDC=1-Slot=4; The CPU protocol queue (112) is blocked. |
|
Impact |
Protocol packets to the CPU cannot be sent out. |
|
Cause |
Hardware errors occur. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_CPUQUE_DROP
|
Message text |
The CPU protocol queue ([UINT32]) is congested. |
|
Variable fields |
$1: CPU output queue ID in the range of 0 to 127. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QOS_CPUQUE_DROP: -MDC=1-Slot=4; The CPU protocol queue (112) is congested. |
|
Impact |
Protocol packets to the CPU are dropped. |
|
Cause |
The command is executed, and the rate of protocol packets to the CPU exceeds the rate limit value. |
|
Recommended action |
1. Increase the rate limit value. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
NETSTREAM_SAMPLER_NORES
|
Message text |
Not enough sampler resources for NetStream. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/NETSTREAM_SAMPLER_NORES:-MDC=1-Slot=4; Not enough sampler resources for NetStream. |
|
Impact |
NetStream collects statistics on all traffic, consuming a large number of hardware resources and causing high CPU usage. |
|
Cause |
This message is generated when you configure a sampler for NetStream and sampler resources are insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_WFQ_NORES
|
Message text |
Not enough WFQ resources to modify the weight value of queue [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QOS_WFQ_NORES : -MDC=1-Slot=9; Not enough WFQ resources to modify the weight value of queue [INT 32] in a queue scheduling profile. |
|
Impact |
The system failed to modify the WFQ weight value of a queue in a queue scheduling profile. |
|
Cause |
WFQ resources are insufficient. |
|
Recommended action |
1. Use the undo queue command to delete unnecessary WFQ settings to release WFQ resources and use the queue command to reconfigure the weight value. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QMPROFILE_QUEUE_NORES
|
Message text |
Not enough Limit resources to modify the max-bandwidth value of queue [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QMPROFILE_QUEUE_NORES : -MDC=1-Slot=9; Not enough Limit resources to modify the max-bandwidth value of queue [INT 32] in a queue scheduling profile. |
|
Impact |
The system failed to modify the maximum bandwidth value of a queue in a queue scheduling profile. |
|
Cause |
Rate limiting resources are insufficient. |
|
Recommended action |
1. Use the undo queue and undo qos gts commands to delete unnecessary maximum bandwidth settings and queue-based GTS settings. Execute the queue command to modify the maximum bandwidth. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MAXBAND_EXCEED_10G
|
Message text |
Not support to modify the max-bandwidth value of queue [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/MAXBAND_EXCEED_10G : -MDC=1-Slot=9; Not support to modify the max-bandwidth value of queue [INT 32] in a queue scheduling profile. |
|
Impact |
The system failed to modify the maximum bandwidth value of a queue in a queue scheduling profile. |
|
Cause |
The maximum bandwidth in a queue scheduling profile is beyond the capabilities of the device. |
|
Recommended action |
1. Modify the maximum bandwidth to a value smaller than 10 Gbps. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_SHAPING_NORES
|
Message text |
The rate limiting configuration on interface [STRING] didn't work as expected due to insufficient hardware resources. |
|
Variable fields |
$1: Layer 3 aggregate interface name. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QOS_SHAPING_NORES:-MDC=1-Slot=4; The rate limiting configuration on interface RAGG1 didn't work as expected due to insufficient hardware resources. |
|
Impact |
The rate limiting configuration on a Layer 3 aggregate interface does not take effect. |
|
Cause |
The member ports of the aggregate interface change between Selected state and Unselected state when hardware resources are insufficient: You can identify the state of a member port through the Port Status field in the display link-aggregation verbose command output. If a member port flaps, it might change between Selected state and Unselected state. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_AGGPORT_SLICE_NORES
|
Message text |
The network-slice (id $1) bandwidth configuration on interface $2 didn't work as expected due to insufficient hardware resources. |
|
Variable fields |
$1: Network slice ID. $2: Layer 3 aggregate interface name. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QOS_SHAPING_NORE: -MDC=1-Slot=4; The network-slice(id 1) bandwidth configuration on interface RAGG1 didn't work as expected due to insufficient hardware resources. |
|
Impact |
The network-slice bandwidth configuration on a Layer 3 aggregate interface does not take effect. |
|
Cause |
The bandwidth of the Layer 3 aggregate interface changes, and hardware resources are insufficient. If the state of a member port changes or a member port joins or leaves a Layer 3 aggregation group, the bandwidth of the Layer 3 aggregate interface changes. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_SLICE_RELEASE_NORES
|
Message text |
The network-slice bandwidth configuration didn't work as expected due to insufficient hardware resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QOS_SHAPING_NORE: -MDC=1-Slot=4; The network-slice bandwidth configuration didn't work as expected due to insufficient hardware resources. |
|
Impact |
The network-slice bandwidth configuration didn't work as expected |
|
Cause |
Hardware resources are insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_PSID_NORES
|
Message text |
Due to insufficient hardware resources, the outgoing traffic for the newly added member port of a Layer 3 aggregation group was sent out of another Selected port. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QOS_PSID_NORES:-MDC=1-Slot=4; Due to insufficient hardware resources, the outgoing traffic for the newly added member port of Layer 3 aggregation group was sent out of another member port. |
|
Impact |
Congestion might occur on other member ports. |
|
Cause |
A new member port is added to a Layer 3 aggregation group with eight member ports, and hardware resources are insufficient. |
|
Recommended action |
1. Use the undo port link-aggregation group command to remove one or more Unselected ports from the Layer 3 aggregation group. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ATM_QUEUE_NORES
|
Message text |
Not enough hardware queue resources for ATM interfaces. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/ATM_QUEUE_NORES:-MDC=1-Slot=4; Not enough hardware queue resources for ATM interfaces. |
|
Impact |
Failed to create a PVC or switch the PVC service type on an ATM interface. |
|
Cause |
Hardware queue resources are insufficient on the card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MOD_MINBANDPCT_NOTSPT
|
Message text |
Not support to modify the min-bandwidth-pct value of queue [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/MOD_MINBANDPCT_NOTSPT: -Slot=9; Not support to modify the min-bandwidth-pct value of queue 1 in a queue scheduling profile. |
|
Impact |
The modification fails. |
|
Cause |
This message is generated when you modify the minimum guaranteed bandwidth of a queue in a queue scheduling profile already applied from an absolute value to a percentage value. |
|
Recommended action |
1. Use the queue command to modify the minimum guaranteed bandwidth also as an absolute value. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MPLSTE_RSVBAND_NORSC
|
Message text |
Hardware resources not enough. Can't deploy [string]'s MPLS TE bandwidth configuration to [string] when [string] is added to [string]. |
|
Variable fields |
$1: Name of a Layer 3 aggregate interface. $2: Name of a member port for a Layer 3 aggregate interface. $3: Name of a member port for a Layer 3 aggregate interface. $4: Name of a Layer 3 aggregate interface. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/ MPLSTE_RSVBAND_NORSC: -MDC=1; Hardware resources not enough. Can't deploy Route-Aggregation1's MPLS TE bandwidth configuration to GigabitEthernet0/0/9 when GigabitEthernet0/0/9 is added to Route-Aggregation1. |
|
Impact |
The MPLS TE bandwidth fails to take effect on the new member port. |
|
Cause |
Hardware entry resources are insufficient on the module. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QMPROFILE_GROUP_NORES
|
Message text |
Not enough rate limit resources to modify the maximum bandwidth value of group [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Group ID. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QMPROFILE_GROUP_NORES: -MDC=1-Slot=4; Not enough rate limit resources to modify the maximum bandwidth value of group 1 in a queue scheduling profile. |
|
Impact |
Failed to modify the maximum bandwidth value of a group in a queue scheduling profile. |
|
Cause |
Rate limit resources are insufficient. |
|
Recommended action |
1. Use the undo queue and undo qos gts commands to delete unnecessary queue scheduling and GTS settings to release resources. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_QMPROFILE_RESTORE_FAIL
|
Message text |
Failed to restore the configuration of queue scheduling profile [STRING] on interface [STRING], because [STRING]. |
|
Variable fields |
$1: Queue scheduling profile name. $2: Interface name. $3: Failure cause: ¡ the minimum bandwidth exceeds the interface bandwidth. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_QMPROFILE_RESTORE_FAIL: Failed to restore the configuration of queue scheduling profile b on interface GigabitEthernet1/0/1, because the minimum bandwidth exceeds the interface bandwidth. |
|
Impact |
Failed to restore the configuration of a queue scheduling profile on an interface. |
|
Cause |
The minimum bandwidth exceeds the interface bandwidth.. |
|
Recommended action |
1. Use the undo qos apply qmprofile command to remove the queue scheduling profile from the interface. Use the queue command to modify the minimum bandwidth in the queue scheduling profile or use the bandwidth command to modify the interface bandwidth, and apply the queue scheduling profile again. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_QUEUE_NORMAL
|
Message text |
The interface $1's queue congestion state is restored to normal. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
%Oct 25 15:02:01:751 2021 H3C QACL/4/QOS_QUEUE_NORMAL: -MDC=1-Slot=6; The interface Ten-GigabitEthernet6/2/8's queue congestion state is restored to normal. |
|
Impact |
None. |
|
Cause |
The interface queue state restored from congested to normal. |
|
Recommended action |
No action is required. |
AGGP_MPLSTERSV_NORSC
|
Message text |
The MPLS TE reservable bandwidth configuration on Layer 3 aggregate interface [STRING] didn't work as expected due to insufficient hardware resources. |
|
Variable fields |
$1: Layer 3 aggregate interface number. |
|
Severity level |
6 (Informational) |
|
Example |
QACL/6/AGGP_MPLSTERSV_NORSC:-MDC=1-Slot=4; The MPLS TE reservable bandwidth configuration on Layer 3 aggregate interface 1 didn't work as expected due to insufficient hardware resources. |
|
Impact |
The MPLS TE reservable bandwidth configuration on a Layer 3 aggregate interface does not take effect. |
|
Cause |
The member ports of the aggregate interface change between Selected state and Unselected state when hardware resources are insufficient: You can identify the state of a member port through the Port Status field in the display link-aggregation verbose command output. If a member port flaps, it might change between Selected state and Unselected state. |
|
Recommended action |
1. Use the mpls te max-reservable-bandwidth command to reconfigure MPLS TE reservable bandwidth settings on the Layer 3 aggregate interface. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INTF_QUEUE_BLOCK
|
Message text |
All queues of interface [STRING] are blocked. |
|
Variable fields |
$1: Interface name |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/INTF_QUEUE_BLOCK: -MDC=1-Slot=2; All queues of interface Ten-GigabitEthernet 2/2/3 are blocked. |
|
Impact |
The interface cannot forward packets. |
|
Cause |
The rate limit value is small. This message is generated when the number of forwarded packets on each queue remains unchanged but the number of dropped packets increases between two polls. The system polls packet statistics on queues at 500-millisecond intervals. |
|
Recommended action |
1. Increase the rate limiting value on the interface. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MOD_QUEUEMAXBANDPCT_NOTSPT
|
Message text |
Failed to modify the maximum allowed bandwidth as a percentage for queue [INT 32] in a queue scheduling profile already applied. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/MOD_QUEUEMAXBANDPCT_NOTSPT: -MDC=1-Slot=9; Failed to modify the maximum allowed bandwidth as a percentage for queue 1 in a queue scheduling profile already applied. |
|
Impact |
The modification fails. |
|
Cause |
This message is generated when you modify the maximum allowed queue bandwidth for queue scheduling profile already applied from an absolute value to a percentage value. |
|
Recommended action |
1. Use the queue command to modify the maximum allowed bandwidth also as an absolute value. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MOD_GROUPMAXBANDPCT_NOTSPT
|
Message text |
Failed to modify the maximum allowed bandwidth as a percentage for group [INT 32] in a queue scheduling profile already applied. |
|
Variable fields |
$1: Group number. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/ MOD_GROUPMAXBANDPCT_NOTSPT: -MDC=1-Slot=9; Failed to modify the maximum allowed bandwidth as a percentage for group 1 in a queue scheduling profile already applied. |
|
Impact |
The modification fails. |
|
Cause |
This message is generated when you modified the maximum allowed group bandwidth for a queue scheduling profile already applied from an absolute value to a percentage value. |
|
Recommended action |
1. Use the queue command to modify the maximum allowed bandwidth also as an absolute value. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
MPLSTE_CHANNEL_CONFLICT
|
Message text |
The MPLS TE configuration failed to take effect because it conflicts with the channel bandwidth configuration or network-slice configuration. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/MPLSTE_CHANNEL_CONFLICT: -MDC=1-Slot=3; The MPLS TE configuration failed to take effect because it conflicts with the channel bandwidth configuration or network-slice configuration. |
|
Impact |
The MPLS TE configuration failed to take effect. |
|
Cause |
The MPLS TE configurations conflict with the channel bandwidth or network slice bandwidth configuration on the same interface. |
|
Recommended action |
1. Use the undo mpls te max-reservable-bandwidth command to delete MPLS TE configurations on the interface. 2. Use the undo mode channel-bandwidth and undo slice-id flex-channel commands to delete channel bandwidth and network slice bandwidth configurations on the interface. |
QOS_WEIGHT_EXCEED
|
Message text |
Failed to modify the weight value of queue [INT 32] in a queue scheduling profile already applied because the modified value exceeds the maximum value 1023. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/QOS_WEIGHT_EXCEED: -MDC=1-Slot=9; Failed to modify the weight value of queue 1 in a queue scheduling profile already applied because the modified value exceeds the maximum value 1023. |
|
Impact |
Failed to modify the weight value of a queue in a queue scheduling profile already applied. |
|
Cause |
This message is generated when the modified weight value of a queue in a queue scheduling profile already applied exceeds 1023. The weight value range for a queue scheduling profile is 0 to 310. When deploying a weight value to a 100GE port, the system multiplies the value by 10, which might cause the weight value to exceed the upper limit (1023). |
|
Recommended action |
1. Modify the weight value of the queue to a value smaller than 1023. If the queue scheduling profile is applied to a 100 GE interface, the weight value cannot be greater than 102. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_WREDPF_NOTSPT
|
Message text |
Failed to specify or change a WRED profile for queue $1 in a queue scheduling profile authorized to online users. |
|
Variable fields |
$1: ID for a queue in a queue scheduling profile. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_WREDPF_NOTSPT: Failed to specify or change a WRED profile for queue 3 in a queue scheduling profile authorized to online users. |
|
Impact |
Failed to specify or change a WRED profile for a queue in a queue scheduling profile authorized to online users. |
|
Cause |
This message is generated when you add or modify a WRED profile for a queue in a queue scheduling profile authorized to IPoE or PPPoE users. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BPA_INBOUND_NORES
|
Message text |
No resources for inbound BGP policy accounting. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/BPA_INBOUND_NORES: -MDC=1-Slot=2; No resources for inbound BGP policy accounting. |
|
Impact |
Inbound BGP policy accounting does not take effect. |
|
Cause |
Resources were exhausted for inbound BGP policy accounting. |
|
Recommended action |
1. Use the undo bgp-policy accounting command to disable inbound BGP policy accounting on the other interfaces. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BPAIN_ALLOC_FAIL
|
Message text |
Failed to allocate resources to inbound BGP policy accounting. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
QACL/3/BPAIN_ALLOC_FAIL: -MDC=1-Slot=2; Failed to allocate resources to inbound BGP policy accounting. |
|
Impact |
Inbound BGP policy accounting does not take effect. |
|
Cause |
This message is generated when the system fails to allocate resources for inbound BGP policy accounting for reasons other than resource exhaustion. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BPA_OUTBOUND_NORES
|
Message text |
No resources for outbound BGP policy accounting. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
QACL/3/ BPA_OUTBOUND_NORES: -MDC=1-Slot=2; Failed to allocate resources to outbound BGP policy accounting. |
|
Impact |
Outbound BGP policy accounting does not take effect. |
|
Cause |
Resources were exhausted for outbound BGP policy accounting. |
|
Recommended action |
1. Use the undo bgp-policy accounting command to disable outbound BGP policy accounting on the other interfaces. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
BPAOUT_ALLOC_FAIL
|
Message text |
Failed to allocate resources to outbound BGP policy accounting. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
QACL/3/BPAOUT_ALLOC_FAIL: -MDC=1-Slot=2; Failed to allocate resources to outbound BGP policy accounting. |
|
Impact |
Outbound BGP policy accounting does not take effect. |
|
Cause |
This message is generated when the system fails to allocate resources for outbound BGP policy accounting for reasons other than resource exhaustion. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INTF_BPAOUT_NOTSPT
|
Message text |
Failed to configure outbound BGP policy accounting on [STRING] because the configuration on the interface is different from that on other interfaces. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/INTF_BPAOUT_NOTSPT: -MDC=1-Slot=7; Failed to configure outbound BGP policy accounting on Route-Aggregation1024.1 because the configuration on the interface is different from that on other interfaces. |
|
Impact |
The outbound BGP policy accounting configuration on the interface does not take effect. |
|
Cause |
The outbound BGP policy accounting configuration on the interface is different from the configuration on the other interfaces on the following cards: |
|
Recommended action |
1. Use the undo bgp-policy accounting command to delete the outbound BGP policy accounting configuration on the interface and use the bgp-policy accounting command to re-enable BGP policy accounting. Make sure the outbound BGP policy accounting configuration on the interface is consistent with the configuration on the other interfaces on the same card. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INTF_BPAOUT_CONFLICT
|
Message text |
Failed to configure BGP policy accounting on [STRING] because of configuration conflicts. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
QACL/4/INTF_BPAOUT_CONFLICT: -MDC=1-Slot=7; Failed to configure BGP policy accounting on Route-Aggregation1024.1 because of configuration conflicts. |
|
Impact |
The BGP policy accounting configuration on the interface does not take effect. |
|
Cause |
The BGP policy accounting configuration conflicts with the other statistics collection configurations on the interface, for example, the ac statistics enable or ip subscriber l2vpn-leased command. |
|
Recommended action |
1. Execute the undo ac statistics enable or undo ip subscriber l2vpn-leased command, and then enable BGP policy accounting . 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QoS
This section contains QoS messages.
EDSG_CONFIG_CONFLICT
|
Message text |
Failed to activate service [UINT32] on user [UINT32]. The EDSG service policy conflicts with existing configurations in the [STRING] direction. |
|
Variable fields |
$1: EDSG service policy ID. $2: User ID. $3: Direction. |
|
Severity level |
3 (Error) |
|
Example |
QOS/3/EDSG_CONFIG_CONFLICT: Failed to activate service 1 on user 0x30000072. The EDSG service policy conflicts with existing configurations in the outbound direction. |
|
Impact |
The EDSG service policy does not take effect. |
|
Cause |
The system failed to activate an EDSG service policy on a user, because the EDSG service policy conflicts with the following configurations: · Queue scheduling profile, GTS, or the queue specified for session packets in user profile view. · HQoS configuration in interface view. |
|
Recommended action |
1. Modify the configuration that conflicts with the EDSG service policy. 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
EDSG_EXCEED_LIMIT
|
Message text |
Failed to activate service [UINT32] on user [UINT32]. The EDSG service policy ID is out of range. |
|
Variable fields |
$1: EDSG service policy ID. $2: User ID. |
|
Severity level |
3 (Error) |
|
Example |
QOS/3/EDSG_EXCEED_LIMIT: Failed to activate service 1 on user 0x30000072. The EDSG service policy ID is out of range. |
|
Impact |
The EDSG service policy does not take effect. |
|
Cause |
The EDSG service policy ID is out of range. |
|
Recommended action |
1. Identify whether multiple EDSG service policies can be activated on one user. ¡ If only one EDSG service policy can be activated on one user, the EDSG service policy ID must be 1. ¡ If multiple (for example, N) EDSG service policies can be activated on one user, the value range for the policy ID is 1 to N. 2. Modify the EDSG service policy ID to an ID supported by the device. |
EDSG_LRMODE_CONFLICT
|
Message text |
Failed to activate service [UINT32] on user [UINT32]. The rate limit mode for the EDSG service policy is different from the rate limit mode for an existing EDSG service policy. |
|
Variable fields |
$1: EDSG service policy ID. $2: User ID. |
|
Severity level |
3 (Error) |
|
Example |
QOS/3/EDSG_LRMODE_CONFLICT: Failed to activate service 1 on user 0x30000072. The rate limit mode for the EDSG service policy is different from the rate limit mode for an existing EDSG service policy. |
|
Impact |
The new EDSG service policy does not take effect. |
|
Cause |
The rate limit mode for the EDSG service policy is different from the rate limit mode for an existing EDSG service policy. |
|
Recommended action |
Modify the rate limit mode for the EDSG service policy. |
EDSG_MODE_CONFLICT
|
Message text |
Failed to activate service [UINT32] on user [UINT32]. The status of the separate rate limiting function for the EDSG service policy is different from the status of this function for an existing EDSG service policy. |
|
Variable fields |
$1: EDSG service policy ID. $2: User ID. |
|
Severity level |
3 (Error) |
|
Example |
QOS/3/EDSG_MODE_CONFLICT: Failed to activate service 1 on user 0x30000072. The status of the separate rate limiting function for the EDSG service policy is different from the status of this function for an existing EDSG service policy. |
|
Impact |
The new EDSG service policy does not take effect. |
|
Cause |
The status of the separate rate limiting function for the EDSG service policy is different from the status of this function for an existing EDSG service policy. |
|
Recommended action |
Modify the separate rate limiting function for the EDSG service policy. |
EDSG_NOT_SUPPORT
|
Message text |
Failed to activate service [UINT32] on user [UINT32]. The EDSG service policy is not supported. |
|
Variable fields |
$1: EDSG service policy ID. $2: User ID. |
|
Severity level |
3 (Error) |
|
Example |
QOS/3/EDSG_NOT_SUPPORT: Failed to activate service 1 on user 0x30000072. The EDSG service policy is not supported. |
|
Impact |
The EDSG service policy does not take effect. |
|
Cause |
The EDSG service policy is not supported. |
|
Recommended action |
Modify and reapply the EDSG service policy. |
QOS_CAR_APPLYIF_FAIL
|
Message text |
[STRING]; Failed to apply the [STRING] CAR in [STRING] profile [STRING] to interface [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Interface name. $2: CAR application direction: inbound or outbound. $3: Profile type: ¡ user ¡ session group ¡ user group $4: Profile name. $5: Interface name. $6: Failure cause. ¡ The CAR is not supported. ¡ The resources are insufficient. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_CAR_APPLYIF_FAIL: Port=GigabitEthernet1/0/1; Failed to apply the inbound CAR in user profile a to interface GigabitEthernet1/0/1. Reason: The resources are insufficient. |
|
Impact |
The traffic policing configured in the user profile, user group profile, or session group profile applied to an interface does not take effect. |
|
Cause |
· The CAR configured in the user profile, user group profile, or session group profile applied to an interface does not take effect. · The modification or addition of CAR in the user profile, user group profile, or session group profile does not take effect. |
|
Recommended action |
1. Delete the CAR configuration in the user profile, user group profile, or session group profile. 2. Use the display resource-monitor command to identify whether the available bras_car resources are sufficient. If no, delete unused CAR settings. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 ID Information $2: CAR Application Orientation $3: Profile Type $4: Profile Name $5: Failure cause. ¡ The resources are insufficient. ¡ The operation is not supported. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
The traffic policing configured in the User Profile, User Group Profile, or Session Group Profile bound to the online user is invalid. |
|
Cause |
· The CAR configured in the User Profile, User Group Profile, or Session Group Profile delivered during the user online process has failed. · The modification or addition of CAR in the User Profile, User Group Profile, or Session Group Profile bound to the already online user has failed. |
|
Recommended action |
1. Please delete the CAR configuration under this User Profile, User Group Profile, or Session Group Profile. 2. Please execute the 'display resource-monitor' command to check if the remaining resources corresponding to bras_car in the displayed fields are sufficient. If the resources are insufficient, delete some unnecessary traffic policing configurations. 3. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
QOS_CBQ_REMOVED
|
Message text |
CBQ is removed from [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_CBQ_REMOVED: CBQ is removed from GigabitEthernet4/0/1. |
|
Impact |
For the traffic behavior in the QoS policy applied on the interface, if class-based queuing is configured, packets that comply with the traffic classification in the QoS policy on the interface do not follow the CBQ queue scheduling defined in the traffic behavior |
|
Cause |
When the maximum available bandwidth or interface rate on the interface is changed to be lower than the minimum guaranteed bandwidth required by the original CBQ configuration on the interface, the system removes the CBQ from the interface |
|
Recommended action |
Please execute the 'bandwidth' command to modify the maximum available bandwidth on the interface so that it meets the bandwidth requirement in CBQ, then reapply the QoS policy containing CBQ traffic behavior on the interface |
QOS_CHANNEL_APPLYIF_FAIL
|
Message text |
[STRING]; Failed to apply QoS channel bandwidth setting to the outbound direction of interface [STRING]. [STRING]. |
|
Variable fields |
$1: User identity. $2: Interface name. $3: Failure cause: ¡ The channel bandwidth function conflicts with the exclusive bandwidth configuration. ¡ The channel bandwidth function conflicts with HQoS. ¡ The channel bandwidth function conflicts with TE. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_CHANNEL_APPLYIF_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2-SVLAN=100-VPN=”N/A”-Port=GigabitEthernet5/1/1.1; Failed to apply QoS channel bandwidth setting to the outbound direction of interface GigabitEthernet5/1/1.1 . The channel bandwidth function conflicts with exclusive. |
|
Impact |
The channel bandwidth setting does not take effect. |
|
Cause |
The channel bandwidth setting conflicts with an existing configuration on the interface. |
|
Recommended action |
Modify the configuration according to the failure cause. |
QOS_COPP_ALARM_ACTIVE
|
Message text |
Packets to the control plane dropped due to rate violation. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_COPP_ALARM_ACTIVE: Packets to the control plane dropped due to rate violation. |
|
Impact |
Protocol packets cannot be processed. |
|
Cause |
The rate limit is exceeded. |
|
Recommended action |
Identify whether an attack occurs in the network. If yes, enable the corresponding attack defense function or limit the rate of the packets to the control plane. |
QOS_COPP_ALARM_CLEAR
|
Message text |
No packets to the control plane dropped. |
|
Severity level |
5 (Notification) |
|
Example |
QOS/4/QOS_COPP_ALARM_CLEAR: No packets to the control plane dropped. |
|
Impact |
No negative impact on the system. |
|
Cause |
No packets to the control plane are dropped in a minute. |
|
Recommended action |
No action is required. |
QOS_DIFFSERV_CFG_FAIL
|
Message text |
Failed to configure the MPLS Diffserv mode in VPN instance [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: VPN instance name. $2: Failure cause: ¡ The card does not support MPLS Diffserv mode. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_DIFFSERV_CFG_FAIL: Failed to configure the MPLS Diffserv mode in VPN instance vpn1. Reason: The card does not support MPLS Diffserv mode. |
|
Impact |
Packets in the VPN instance cannot be processed according to the MPLS Diffserv mode when entering and leaving the public network. |
|
Cause |
The system failed to configure the MPLS Diffserv mode in a VPN instance. |
|
Recommended action |
1. Use another interface on the card to process traffic or replace the card. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_GTS_APPLYIF_FAIL
|
Message text |
[STRING]; Failed to apply the [STRING] GTS in [STRING] profile [STRING] to interface [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: User identity. $2: Application direction. $3: Profile type, which is user. $4: Profile name. $5: Interface name. $6: Failure cause: ¡ The resources are insufficient. ¡ The configuration in the user profile to be applied conflicts with the existing configuration on the interface. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_GTS_APPLYIF_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2/16-CVLAN=100-Port=GigabitEthernet5/1/5; Failed to apply the inbound GTS in user profile u1 to interface GigabitEthernet5/1/5. Reason: The resources are insufficient. |
|
Cause |
The system failed to perform one of the following actions: · Apply the GTS settings when applying a user profile to an interface. · Add or modify GTS settings in a user profile already applied to an interface. |
|
Recommended action |
1. Delete the GTS settings in the user profile. 2. Use the display resource-monitor command to identify whether the available queue_shape resources are sufficient. If no, delete unused GTS settings. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_GTS_APPLYINT_FAIL
|
Message text |
Failed to apply the gts configuration to the interface [STRING]. [STRING] |
|
Variable fields |
$1: Interface name. $2: Failure cause. ¡ The operation is not supported. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_GTS_APPLYINT_FAIL: Failed to apply the gts configuration to the interface Route-Aggregation1. The operation is not supported. |
|
Impact |
GTS does not take effect on the interface. |
|
Cause |
The interface does not support GTS. |
|
Recommended action |
1. Configure GTS on an interface that supports GTS. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_GTS_APPLYUSER_FAIL
|
Message text |
[STRING]; Failed to apply the [STRING] GTS to the traffic of [STRING] profile [STRING] in queue [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: Interface name. $2: GTS application direction. $3: Profile type: ¡ user group ¡ session group $4: Profile name. $5: Queue ID. $6: Failure cause. ¡ The resources are insufficient. ¡ The GTS configuration conflicts with the CAR configuration in an EDSG service policy. |
|
Severity level |
4 (Warning) |
|
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 the inbound GTS to the traffic of session group profile a in queue 0. Reason: The GTS configuration conflicts with the CAR configuration in an EDSG service policy. |
|
Impact |
The GTS configuration does not take effect. |
|
Cause |
The GTS information issued during user online process failed. The user has already gone online, but the modification or addition of GTS information failed. |
|
Recommended action |
1. Delete or modify the GTS configuration in the user group profile or session group profile. 2. Use the display resource-monitor command to identify whether the available queue_shape resources are sufficient. If no, delete unused GTS settings. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_ITACAR_APPLYUSER_FAIL
|
Message text |
[STRING]; Failed to apply the ITA CAR at level [STRING] to the user. Reason: [STRING]. |
|
Variable fields |
$1: User identity. $2: ITA CAR level. $3: Failure cause: ¡ The ITA CAR is not supported. ¡ The resources are insufficient. ¡ The value is out of range. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_ITACAR_APPLYUSER_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2/16-SVLAN=100-Port=GigabitEthernet5/1/5; Failed to apply the ITA CAR at level 7 to the user. Reason: The ITA CAR is not supported. |
|
Impact |
The ITA CAR does not take effect. |
|
Cause |
The system failed to apply or modify traffic policing parameters in the ITA CAR policy. |
|
Recommended action |
1. Use the display resource-monitor command to identify whether the available bras_car resources are sufficient. If no, delete unused CAR settings. 2. Cancel the ITA CAR policy or modify the traffic policing parameters. |
QOS_LR_APPLYIF_FAIL
|
Message text |
Failed to apply the [STRING] rate limit in user profile [STRING] to interface [STRING]. [STRING]. |
|
Variable fields |
$1: Traffic direction. $2: User profile name. $3: Interface name. $3: Failure cause. ¡ The rate limit is not supported. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_LR_APPLYIF_FAIL: Failed to apply the inbound rate limit in user profile a2 to interface Ten-GigabitEthernet4/1/4.1. Reason: The rate limit is not supported. |
|
Impact |
The rate limit settings in the user profile applied to the interface do not take effect. |
|
Cause |
The card does not support the rate limit configuration. |
|
Recommended action |
1. Apply the user profile to an interface on another card that supports the rate limit configuration. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_LR_APPLYIF_CONFIGFAIL
|
Message text |
Failed to apply the rate limiting configuration to the [STRING] direction of the interface [STRING]. [STRING]. |
|
Variable fields |
$1: Traffic direction. $2: Interface name. $3: Failure cause. ¡ The operation is not supported. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_LR_APPLYIF_CONFIGFAIL: Failed to apply the rate limiting configuration to the outbound direction of the interface Bridge-Aggregation 1. The operation is not supported. |
|
Impact |
The rate limit settings do not take effect on the interface. |
|
Cause |
The card does not support the rate limit configuration. |
|
Recommended action |
1. Apply the user profile to an interface on another card that supports the rate limit configuration. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_LR_APPLYUSER_FAIL
|
Message text |
STRING]; Failed to apply the [STRING] rate limit to the traffic of user profile [STRING] in all queues. Reason: [STRING] |
|
Variable fields |
$1: User identity. $2: Application direction. $3: User profile name. $4: Failure cause: ¡ The resources are insufficient. ¡ The rate limit is not supported. ¡ The rate limit configuration conflicts with the CAR configuration in a EDSG service policy. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_LR_APPLYUSER_FAIL: -MAC=0010-9400-1f38-VPN=N/A-SVLAN=4008-CVLAN=992-Port=Route-Aggregation1024.4093; Failed to apply the outbound rate limit to the traffic of user profile u1 in all queues. Reason: The resources are insufficient. |
|
Impact |
The rate limit settings in the user profile do not take effect. |
|
Cause |
See the failure cause. |
|
Recommended action |
1. Delete the CIR configuration in the qos user-queue command. 2. Use the display resource-monitor command to identify whether the available bras_car resources are sufficient. If no, delete unused CAR settings. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
QOS_NOT_ENOUGH_BANDWIDTH
|
Message text |
Policy [STRING] request bandwidth [UINT32](kbps). Only [UINT32](kbps) available on [STRING]. |
|
Variable fields |
$1: QoS policy name. $2: Bandwidth required by CBQ $3: Available bandwidth on the interface $4: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_NOT_ENOUGH_BANDWIDTH: Policy d request bandwidth 10000(kbps). Only 80(kbps) available on GigabitEthernet4/0/1. |
|
Impact |
Class-based queuing (CBQ) applied on the interface is not effective |
|
Cause |
CBQ configuration fails because the minimum guaranteed bandwidth required by CBQ is greater than the interface's maximum available bandwidth |
|
Recommended action |
Adjust the minimum guaranteed bandwidth in the CBQ configuration, then reapply the QoS policy containing CBQ traffic behavior on the interface, or execute the 'bandwidth' command to modify the maximum available bandwidth on the interface to meet the bandwidth requirements in CBQ |
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: CB to name $2: QoS policy name. $3: Traffic direction. $4: Slot number. $5: Failure cause. ¡ The behavior is empty. ¡ Only one rate-limiting action is supported in one behavior to be applied to the control plane. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
Apply QoS policy on the control plane, and a traffic behavior in the QoS policy does not take effect |
|
Cause |
Add or modify the configuration of a CB pair in a certain orientation on the control plane |
|
Recommended action |
Please modify the configuration of the traffic behavior in the QoS policy according to the failure reason |
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: QoS policy name. $2: Traffic direction. $3: Slot number. $4: Failure cause. The operation is not supported. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
The QoS policy applied on the control plane is not taking effect |
|
Cause |
Applying or updating the QoS policy in a certain orientation on the control plane has failed |
|
Recommended action |
1. Please modify the QoS policy and reapply it on the control plane 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
QOS_POLICY_APPLYGLOBAL_CBFAIL
|
Message text |
Failed to apply classifier-behavior [STRING] in policy [STRING] to the [STRING] direction globally. [STRING]. |
|
Variable fields |
$1: CB against name $2: QoS policy name. $3: Traffic direction. $4: Failure cause. The behavior is empty: traffic behavior is empty |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
Apply global QoS policy, but a traffic behavior in this policy is not taking effect |
|
Cause |
Add or modify a CB pair configuration in a global direction of the QoS policy |
|
Recommended action |
1. Please modify the CB pair in this QoS policy and reapply it in the control plane 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
QOS_POLICY_APPLYGLOBAL_FAIL
|
Message text |
Failed to apply or refresh QoS policy [STRING] to the [STRING] direction globally. [STRING]. |
|
Variable fields |
$1: QoS policy name. $2: Traffic direction. $3: Failure cause. The operation is not supported. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
The global QoS policy does not take effect |
|
Cause |
A newly configured or modified QoS policy is applied to a specific orientation globally |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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: CB pair name. $2: QoS policy name. $3: Traffic direction. $4: Interface name. $5: Failure cause. ¡ The behavior is empty.: Traffic behavior is empty, no action is configured ¡ Only one service class marking action is supported for the same EXP value on the same interface and the service class value can't be modified except that the old value has been deleted.: Only one service class marking action is supported for the same EXP value on the same interface, and the service class value can't be modified except that the old value has been deleted |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
QoS policy is applied on the interface, and a traffic behavior in this QoS policy does not take effect |
|
Cause |
Add or modify a CB pair configuration in a certain direction of the interface's QoS policy |
|
Recommended action |
1. Please modify the CB pair configuration in the QoS policy according to the failure reason 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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: QoS policy name. $2: Traffic direction. $3: Interface name. $4: Failure cause. The operation is not supported. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
The QoS policy configured under the interface does not take effect |
|
Cause |
Configure or modify the QoS policy on a certain orientation of the interface |
|
Recommended action |
Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 ID (UID) information $2: Orientation of QoS policy application $3: QoS policy name. $4: User profile name. $5: Failure cause. The QoS policy is not supported.: The QoS policy is not supported under User Profile |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
QoS policy for applications under User Profile is not effective |
|
Cause |
· During user login, the QoS policy configured in the User Profile is issued · The user has already logged in, modify the QoS policy information in the User Profile or add a new QoS policy |
|
Recommended action |
1. Please delete or modify the QoS policy configured in the User Profile 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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: CB to name $2: QoS policy name. $3: Traffic direction. $4: VLAN ID $5: Failure cause. The behavior is empty. |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
Based on VLAN, apply QoS policy, and a traffic behavior in the QoS policy is not effective |
|
Cause |
Add or modify a CB pair configuration in a certain orientation of VLAN |
|
Recommended action |
1. Please modify the CB pair configuration in the QoS policy based on the failure reason 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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: QoS policy name. $2: Traffic direction. $3: VLAN ID $4: Failure cause. The operation is not supported.: VLAN does not support this QoS policy |
|
Severity level |
4 (Warning) |
|
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. |
|
Impact |
QoS policy based on VLAN application does not take effect |
|
Cause |
Add or modify QoS policy on a certain orientation of VLAN |
|
Recommended action |
1. Please delete or modify the QoS policy applied on a certain orientation of VLAN 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
QOS_PRIORITY_APPLYUSER_FAIL
|
Message text |
Failed to identify the [STRING] priority of the user. Reason: [STRING]. |
|
Variable fields |
$1: Traffic direction. $2: Failure cause. ¡ The priority type is not supported. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_PRIORITY_APPLYUSER_FAIL: Failed to identify the inbound priority of the user. Reason: The priority type is not supported. |
|
Impact |
The device cannot obtain the priority of the user and cannot schedule packets for the user based on the user priority. |
|
Cause |
The system failed to modify the priority of incoming packets or enqueue packets according to the RADIUS-assigned user priority. |
|
Recommended action |
On the RADIUS server, disable the RADIUS server from assigning the user priority or modify the user priority to be assigned by the RADIUS server. |
QOS_PROFILE_AUTHOR_FAIL
|
Message text |
[STRING]; Failed to authorize the QoS configuration to the user. Reason: [STRING] |
|
Variable fields |
$1: User identity. $2: Failure cause: ¡ The session group profile conflicts with the user profile configured with user queue settings. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_PROFILE_AUTHOR_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2-SVLAN=100-VPN=”N/A”-Port=GigabitEthernet5/1/5; Failed to authorize the QoS configuration to the user. Reason: The session group profile conflicts with the user profile configured with user queue settings. |
|
Impact |
The user profile, session group profile, and QoS settings do not take effect. |
|
Cause |
The system failed to authorize the user profile or session group profile to online users because the session group profile conflicts with the user profile configured with user queue settings. |
|
Recommended action |
1. Use the display access-user command to determine the inactive profile. 2. Modify the user profile or session group profile settings to avoid authorizing both the user profile and session group profile to online users. |
QOS_PROFILE_NOTEXIST
|
Message text |
[STRING]; The [STRING] [STRING] profile [STRING] doesn't exist. |
|
Variable fields |
$1: User identity. $2: Profile application direction. $3: Profile type: ¡ user ¡ session group $4: Profile name. |
|
Severity level |
5 (Notification) |
|
Example |
QOS/5/QOS_PROFILE_NOTEXIST: -MAC=1111-2222-3333-IP=192.168.1.2-SVLAN=100-VPN=”N/A”-Port=GigabitEthernet5/1/5; The inbound user profile a doesn't exist. |
|
Impact |
The user profile or session group profile does not take effect. |
|
Cause |
The user profile or session group profile does not exist. |
|
Recommended action |
Create the user profile or session group profile. |
QOS_QMPROFILE_APPLYIF_FAIL
|
Message text |
[STRING]; Failed to apply the [STRING] queue scheduling profile [STRING] in [STRING] profile [STRING] to interface [STRING]. Reason: [STRING]. |
|
Variable fields |
$1: User identity. $2: Application direction: inbound or outbound. $3: Queue scheduling profile name. $4: User profile type. $5: User profile name. $6: Interface name. $7: Failure cause. ¡ The QMProfile is not supported. ¡ The configuration in the user profile to be applied conflicts with the existing configuration on the interface. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_QMPROFILE_APPLYIF_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2/16-SVLAN=100-Port=GigabitEthernet5/1/5; Failed to apply the inbound queue scheduling profile b in user profile a to interface GigabitEthernet5/1/5. Reason: The QMProfile is not supported. QOS/4/QOS_QMPROFILE_APPLYIF_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2/16-CVLAN=100-Port=GigabitEthernet5/1/5; Failed to apply the inbound queue scheduling profile b in user profile a to interface GigabitEthernet5/1/5. Reason: The configuration in the user profile to be applied conflicts with the existing configuration on the interface. |
|
Impact |
The queue scheduling profile applied to the interface does not take effect. |
|
Cause |
A user profile containing a queue scheduling profile fails to be applied to an interface, or the queue scheduling profile in a user profile that has been applied to an interface fails to be added or modified. |
|
Recommended action |
Delete or modify the queue scheduling profile in the user profile. |
QOS_QMPROFILE_APPLYINT_FAIL
|
Message text |
Failed to apply the queue scheduling profile to the [STRING] direction of interface [STRING]. [STRING] |
|
Variable fields |
$1: Traffic direction: inbound or outbound. $2: Interface name. $3: Failure cause: ¡ The operation is not supported. ¡ Resources are insufficient. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_QMPROFILE_APPLYINT_FAIL: Failed to apply the queue scheduling profile to the outbound direction of interface Route-Aggregation1. The operation is not supported. |
|
Impact |
The applied queue scheduling profile does not take effect. |
|
Cause |
The interface does not support queue scheduling profiles. |
|
Recommended action |
· If the interface does not queue scheduling profiles, collect the configuration file, log file, and alarms, and then contact Technical Support for help. · If resources are insufficient, delete some ACLs to release resources |
QOS_QMPROFILE_APPLYUSER_FAIL
|
Message text |
[STRING]; Failed to apply the [STRING] queue scheduling profile [STRING] in [STRING] profile [STRING] to the user. Reason: [STRING]. |
|
Variable fields |
$1: User ID information. $2: Application direction. $3: Queue scheduling profile name. $4: User profile type. $5: User profile name. $4: Failure cause. ¡ The QMProfile is not supported. ¡ The queue scheduling profile configuration conflicts with the CAR configuration in an EDSG service policy. |
|
Severity level |
4 (Warning) |
|
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 the inbound queue scheduling profile b in session group profile a to the user. Reason: The QMProfile is not supported. QOS/4/QOS_QMPROFILE_APPLYUSER_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2/16-CVLAN=100-Port=GigabitEthernet5/1/5; Failed to apply the inbound queue scheduling profile b in session group profile a to the user. Reason: The queue scheduling profile configuration conflicts with the CAR configuration in an EDSG service policy. |
|
Impact |
The queue scheduling profile configured in the user profile, user group profile, or session group profile for authorized online users does not take effect. |
|
Cause |
See the failure cause. |
|
Recommended action |
Delete or modify the queue scheduling profile in the user profile, user group profile, or session group profile. |
QOS_QMPROFILE_MODIFYQUEUE_FAIL
|
Message text |
Failed to configure queue [UINT32] in queue scheduling profile [STRING]. [STRING]. |
|
Variable fields |
$1: Queue number $2: Name of queue scheduling policy $3: Failure cause. The value is out of range. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_QMPROFILE_MODIFYQUEUE_FAIL: Failed to configure queue 1 in queue scheduling profile myqueue. The value is out of range. |
|
Impact |
Queue scheduling in the scheduling policy cannot be modified, and still takes effect according to the original queue scheduling method and parameters |
|
Cause |
After applying the queue scheduling policy at the interface, if the configuration of a queue in the queue scheduling policy is modified, and the new configuration parameters exceed the port capacity |
|
Recommended action |
1. Please delete the applied queue scheduling policy at the interface before modifying the queue parameters in the queue scheduling policy 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
QOS_QMPROFILE_RESTORE_FAIL
|
Message text |
Failed to restore the configuration of queue scheduling profile [STRING] on interface [STRING], because [STRING]. |
|
Variable fields |
$1: Queue scheduling profile name. $2: Interface name. $3: Failure cause: ¡ The minimum guaranteed bandwidth exceeds the interface bandwidth. ¡ The queue-based GTS configuration conflicts with the maximum bandwidth setting in the queue scheduling profile. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_QMPROFILE_RESTORE_FAIL: -MDC=1; Failed to restore the configuration of queue scheduling profile abc on interface GigabitEthernet3/0/3, because the minimum guaranteed bandwidth exceeds the interface bandwidth. |
|
Impact |
The queue scheduling profile does not take effect. |
|
Cause |
See the failure cause. The message is generated when a card is inserted after the queue-based GTS and queue scheduling profile settings are configured. |
|
Recommended action |
· If the minimum guaranteed bandwidth exceeds the interface bandwidth, use the bandwidth queue command to modify the minimum guaranteed bandwidth. · If the queue-based GTS configuration conflicts with the maximum bandwidth setting in the queue scheduling profile, modify the GTS configuration or use the group command to modify the maximum bandwidth setting in the queue scheduling profile. |
QOS_WEIGHT_APPLYUSER_FAIL
|
Message text |
[STRING]; Failed to apply the [STRING] weight in [STRING] profile [STRING] to the user. Reason: [STRING]. |
|
Variable fields |
$1: User identity. $2: Direction. $3: User profile type. $4: User profile name. $5: Failure cause. ¡ The resources are insufficient. ¡ The weight configuration conflicts with the CAR configuration in an EDSG service policy. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_WEIGHT_APPLYUSER_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2-SVLAN=100-VPN=”N/A”-Port=GigabitEthernet5/1/5; Failed to apply the outbound weight in user profile a to the user. Reason: The resources are insufficient. QOS/4/QOS_WEIGHT_APPLYUSER_FAIL: -MAC=1111-2222-3333-IP=192.168.1.2-SVLAN=100-VPN=”N/A”-Port=GigabitEthernet5/1/5; Failed to apply the outbound weight in user profile a to the user. Reason: The weight configuration conflicts with the CAR configuration in an EDSG service policy. |
|
Impact |
The configured weight does not take effect. |
|
Cause |
The system failed to apply or dynamically modify the weight value due to insufficient resources. Or The system failed to dynamically modify the weight value, because the weight configuration conflicts with the CAR configuration in an EDSG service policy. |
|
Recommended action |
Delete or modify the weight value. |
QOS_WRED_APPLYINT_FAIL
|
Message text |
Failed to apply WRED profile to interface [STRING]. Not enough hardware resources available. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
QOS/4/QOS_WRED_APPLYINT_FAIL: Failed to apply WRED profile to interface GigabitEthernet 1/0/1. Not enough hardware resources available. |
|
Impact |
The WRED profile does not take effect. |
|
Cause |
Hardware resources are insufficient. |
|
Recommended action |
1. Remove unused WRED profiles from the interface, reapply the WRED profile to the interface again. 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support for help. |
RADIUS messages
This section contains RADIUS messages.
RADIUS_ACCT_CACHE_DISCARD
|
Message text |
Dropped buffered stop-accounting packets or stop-accounting packets to be buffered, because the memory usage reached the minor alarm threshold: MemoryUsage=[[UINT32]%], CachePackets=[[UINT32]]. |
|
Variable fields |
$1: Current memory usage. $2: Number of cached RADIUS stop-accounting packets. |
|
Severity level |
4 (Warning) |
|
Example |
RADIUS/4/RADIUS_ACCT_CACHE_DISCARD :Dropped buffered stop-accounting packets or stop-accounting packets to be buffered, because the memory usage reached the minor alarm threshold: MemoryUsage=[95%], CachePackets=[100]. |
|
Impact |
When the memory threshold is reached, if radius stop-accounting-buffer memory-minor-threshold overwrite-oldest is configured, the system discards the longest cached packets. If the command is not configured, the system drops the packets to be cached. When the connection between the device and the RADIUS server recovers, some users cannot go offline in time. |
|
Cause |
The memory usage has reached the minor alarm threshold. |
|
Recommended action |
1. Use the display memory-threshold command in any view, and verify if the memory usage of the MPU has reached the alarm threshold. ¡ If yes, proceed to step 2. ¡ If no, no action is required. 2. Verify if the set MPU memory threshold is low. ¡ If the threshold is low, execute the memory-threshold command in system view to set a proper MPU memory threshold. ¡ If no, proceed to step 3. 3. Execute the radius stop-accounting-buffer cache command in system view, reduce the maximum number of cached RADIUS stop-accounting packets to release the burden on memory resources. Then, proceed to the next step. 4. Execute the test-aaa command in user view to verify if errors exist for interaction between the device and the RADIUS server. ¡ If the test result is success, it indicates that the server is reachable. ¡ If the test result is failure, it indicates that the link between the device and the server is faulty. Resolve the link issue. If the link is reachable but the alarm cannot be cleared, ignore the alarm. 5. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
RADIUS_ACCT_CACHE_LOWER_THRES
|
Message text |
The ratio of the number of buffered stop-accounting packets to the max number has dropped below the lower threshold: MaxCachePackets=[[UINT32]], LowerThreshold=[[UINT32]%]. |
|
Variable fields |
$1: Maximum number of cached RADIUS stop-accounting packets. $2: Recovery threshold for RADIUS stop-accounting packet cache alarm. |
|
Severity level |
5 (Notification) |
|
Example |
RADIUS/5/RADIUS_ACCT_CACHE_LOWER_THRES :The ratio of the number of buffered stop-accounting packets to the max number has dropped below the lower threshold: MaxCachePackets=[256], LowerThreshold=[30%]. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of cached RADIUS stop-accounting packets dropped below the recovery threshold set by radius stop-accounting-buffer warning-threshold. |
|
Recommended action |
No action is required. |
RADIUS_ACCT_CACHE_UPPER_THRES
|
Message text |
The ratio of the number of buffered stop-accounting packets to the max number has reached the upper threshold: MaxCachePackets=[[UINT32]], UpperThreshold=[[UINT32]%]. |
|
Variable fields |
$1: Maximum number of cached RADIUS stop-accounting packets. $2: Alarm threshold for RADIUS stop-accounting packet cache alarm. |
|
Severity level |
4 (Warning) |
|
Example |
RADIUS/4/RADIUS_ACCT_CACHE_UPPER_THRES :The ratio of the number of buffered stop-accounting packets to the max number has reached the upper threshold: MaxCachePackets=[256], UpperThreshold=[90%]. |
|
Impact |
No negative impact on the system. If the number of cached RADIUS stop-accounting packets continue to increase to the maximum number of packets allowed to be cached, subsequently generated stop-accounting packets will be discarded or will overwrite the longest cached stop-accounting packets. The action of discarding or overwriting is determined by the radius stop-accounting-buffer overwrite-oldest command. |
|
Cause |
The caching rate of RADIUS stop-accounting packets first reaches the alarm threshold set by the radius stop-accounting-buffer warning-threshold command, or grows from below or equal to the recovery threshold set by this command to the alarm threshold. |
|
Recommended action |
1. Verify if the alarm threshold for RADIUS stop-accounting packet cache is proper. ¡ If yes, proceed to step 2. ¡ If no, execute the radius stop-accounting-buffer warning-threshold command in system view to increase the alarm threshold. 2. Execute the test-aaa command in user view to verify if errors exist for interaction between the device and the RADIUS server. ¡ If the test result is success, it indicates that the server is reachable. Proceed to step 3. ¡ If the test result is failure, it indicates that the link between the device and the server is faulty. Resolve the link issue. If the link is reachable but the alarm cannot be cleared, proceed to step 3. 3. Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
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 (Warning) |
|
Example |
RADIUS/4/RADIUS_ACCT_SERVER_DOWN: RADIUS accounting server was blocked: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
The server cannot be reached and user association fails. |
|
Cause |
The device detected that the status of the RADIUS accounting server changed from active to block. |
|
Recommended action |
1. Execute the display interface command to verify that the accounting server interface has started up. If the server interface is not up, verify that the physical link connection is correct. 2. Execute the ping command to ping the accounting server to verify that the server is reachable. If the server is not reachable, check the network reachability between the device and the RADIUS accounting server, and then examine whether firewalls or similar devices exist in the network. 3. Execute the display current-configuration command to verify that the RADIUS accounting server configuration is correct on the device. For more information, see AAA Command Reference and AAA Configuration Guide. 4. If the issue persists, collect the configuration file, log information, and alarm information, and then contact Technical 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 (Informational) |
|
Example |
RADIUS/6/RADIUS_ACCT_SERVER_UP: RADIUS accounting server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device detected that the status of the RADIUS accounting server changed from block to active. |
|
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 (Warning) |
|
Example |
RADIUS/4/RADIUS_AUTH_SERVER_DOWN: RADIUS authentication server was blocked: Server IP= 1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
This will lead to user authentication failure. If no backup authentication server exists, this issue may result in user disconnection. |
|
Cause |
The status of the RADIUS authentication server changed from active to block. |
|
Recommended action |
1. Execute the display interface command to verify that the accounting server interface has started up. If the server interface is not up, verify that the physical link connection is correct. 2. Execute the ping command to ping the accounting server to verify that the server is reachable. If the server is not reachable, check the network reachability between the device and the RADIUS accounting server, and then examine whether firewalls or similar devices exist in the network. 3. Execute the display current-configuration command to verify that the RADIUS accounting server configuration is correct on the device. For more information, see AAA Command Reference and AAA Configuration Guide. 4. If the issue persists, collect the configuration file, log information, and alarm information, and then contact Technical 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 (Informational) |
|
Example |
RADIUS/6/RADIUS_AUTH_SERVER_UP: RADIUS authentication server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device detected that the status of the RADIUS authentication server changed from block to active. |
|
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 (Warning) |
|
Example |
RADIUS/4/RADIUS_DELETE_HOST_FAIL: Failed to delete servers in scheme abc. |
|
Impact |
Depends on the actual situation. |
|
Cause |
Failed to delete servers from a RADIUS scheme through the CLI. |
|
Recommended action |
Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
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 (Warning) |
|
Example |
RESMON/4/RESMON_MINOR: -Resource=AA-Total=100%-Used=83%-Free=17%; Free resource decreased to or below minor threshold 20%. |
|
Impact |
No negative impact on the system temporarily. Pay attention to whether the remaining hardware resource amount continues to decrease. |
|
Cause |
When the available hardware resource amount decreases to or below the minor resource depletion threshold, the device enters minor alarm state and generates this log message. |
|
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 (Notification) |
|
Example |
RESMON/5/RESMON_MINOR_RECOVER: -Resource=AA-Total=100%-Used=77%-Free=23%; Free resource increased above minor threshold 20%. |
|
Impact |
No negative impact on the system. |
|
Cause |
When the available hardware resource amount increases above the minor resource depletion threshold, the device removes the minor resource depletion alarm and generates this log message. The hardware resource usage recovers to normal. |
|
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 (Error) |
|
Example |
RESMON/3/RESMON_SEVERE: -Resource=AA-Total=100%-Used=93%-Free=7%; Free resource decreased to or below severe threshold 10%. |
|
Impact |
The services that use this type of hardware resource will be limited or become unavailable. |
|
Cause |
When the available hardware resource amount decreases to or below the severe resource depletion threshold and the hardware resources are not exhausted, the device enters severe alarm state and generates 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 (Notification) |
|
Example |
RESMON/5/RESMON_SEVERE_RECOVER: -Resource=AA-Total=100%-Used=83%-Free=17%; Free resource increased above severe threshold 10%. |
|
Impact |
No negative impact on the system. |
|
Cause |
When the available resource amount increases above the severe resource depletion threshold, the device removes the severe resource depletion alarm and generates 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 (Critical) |
|
Example |
RESMON/2/RESMON_USEDUP: -Resource=vlaninterface-Total=2048-Used=2048-Free=0; Resources used up. |
|
Impact |
The services that use this type of hardware resource will be limited or become unavailable. |
|
Cause |
When the available resource amount decreases to zero, the device outputs this log message. |
|
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 (Notification) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
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.
RIPLOG
|
Message text |
RIP: Interfaces [STRING] [STRING] Multicast group failed, return value [STRING] |
|
Variable fields |
$1: Interface name. $2: Multicast group quitting or joining failure. Options are: · Quitting: Failed to quit the multicast group. · Joining: Failed to join the multicast group. $3: Error code. Options include: · 22: Invalid parameter. · 99: Incorrect multicast source address. · 105: Insufficient device memory. |
|
Severity level |
6 (Informational) |
|
Example |
RIP/6/RIPLOG:RIP: Interfaces GigabitEthernet1/0/1 Joining Multicast group failed, return value 22. |
|
Impact |
No negative impact on the system |
|
Cause |
The interface failed to join or quit the multicast group, and cannot start or stop receiving/sending RIP multicast packets. |
|
Recommended action |
1. Restart the interface or device. 2. If the issue persists, collect log messages, and then contact Technical Support for help. |
RIPNG messages
This section contains RIPng messages.
RIPNGLOG
|
Message text |
RIPng: Interfaces [STRING] [STRING] Multicast group failed, return value [STRING]. |
|
Variable fields |
$1: Interface name. $2: Multicast group quitting or joining failure. Options are: · Quitting: Failed to quit the multicast group. · Joining: Failed to join the multicast group. $3: Error code. Options include: · 22: Invalid parameter. · 99: Incorrect multicast source address. · 105: Insufficient device memory. |
|
Severity level |
6 (Informational) |
|
Example |
RIPng/6/RIPNGLOG:RIPng: Interfaces GigabitEthernet1/0/1 Joining Multicast group failed, return value 22. |
|
Impact |
No negative impact on the system |
|
Cause |
The interface failed to join or quit the multicast group, and cannot start or stop receiving/sending RIPng multicast packets. |
|
Recommended action |
1. Restart the interface or device. 2. If the issue persists, collect log messages, and then contact Technical Support for help. |
|
Message text |
RIPng Socket Set-option failed on [STRING], this packet will be sent next time. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
RIPng/6/RIPNGLOG:RIPng Socket Set-option failed on GigabitEthernet1/0/1, this packet will be sent next time. |
|
Impact |
No negative impact on the system |
|
Cause |
Failed to set the Socket option when the RIPng interface is sending packets. |
|
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_SID_ROUTE_CONFLICT_ACTIVE
|
Message text |
Conflict between an SRv6 local SID and a route.(SID=[STRING]/[UINT32]) |
|
Variable fields |
$1: SRv6 SID value. $2: Prefix length of the SRv6 SID. |
|
Severity level |
4 |
|
Example |
RM/4/RM_SID_ROUTE_CONFLICT_ACTIVE: -MDC=1; Conflict between an SRv6 local SID and a route.(SID=100::22/128) |
|
Explanation |
A conflict occurred between the SRv6 SID in the SRv6 local SID forwarding table and that in a route entry. |
|
Recommended action |
Check the routing and SRv6 SID settings, and edit the settings if they are not appropriate. |
RM_SID_ROUTE_CONFLICT_CLEAR
|
Message text |
The conflict between the SRv6 local SID and a route was removed. (SID=[STRING]/[UINT32]) |
|
Variable fields |
$1: SRv6 SID value. $2: Prefix length of the SRv6 SID. |
|
Severity level |
4 |
|
Example |
RM/4/RM_SID_ROUTE_CONFLICT_CLEAR: -MDC=1; The conflict between the SRv6 local SID and a route was removed.(SID=100::22/128) |
|
Explanation |
The conflict between the SRv6 SID in the SRv6 local SID forwarding table and that in a route entry was removed. |
|
Recommended action |
No action is required. |
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. |
RM_TOTAL_THRESHLD_VALUE_REACH
|
Message text |
Threshold value [UINT32] reached for active [STRING] routes in all URTs. |
|
Variable fields |
$1: Maximum number of active routes. $2: IPv4 or IPv6. |
|
Severity level |
4 |
|
Example |
RM/4/ RM_TOTAL_THRESHLD_VALUE_REACH: Threshold value 1000 reached for active IPv4 routes in all URTs. |
|
Explanation |
The total number of active routes in the public network and all VPN instances reached the alarm threshold. |
|
Recommended action |
Check the routing table and take relevant actions, for example, configure a routing policy to reduce the number of route entries. |
RM_TOTAL_THRESHLD_VALUE_CLEAR
|
Message text |
Threshold value [UINT32] of active [STRING] routes fell below the limit in all URTs. |
|
Variable fields |
$1: Maximum number of active routes. $2: IPv4 or IPv6. |
|
Severity level |
4 |
|
Example |
RM/4/RM_TOTAL_THRESHLD_VALUE_CLEAR: Threshold value 1000 of active IPv4 routes fell below the limit in all URTs. |
|
Explanation |
The total number of active routes in the public network and all VPN instances dropped below the alarm threshold. |
|
Recommended action |
No action is required. |
RM messages
This section contains RM messages.
RM_ACRT_BELOW_THRESVALUE
|
Message text |
Threshold value [UINT32] of max active [STRING] routes fell below in URT of [STRING]. |
|
Variable fields |
$1: Threshold of the maximum number of active routes in percentage. $2: IPv4 or IPv6. $3: Public network instance or VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_ACRT_BELOW_THRESVALUE: Threshold value 50% of max active IPv4 routes fell below in URT of vpn1. |
|
Impact |
No negative impact on the system. The device still allows new route prefixes to be activated. |
|
Cause |
The number of active routes in the unicast routing table of the public network instance or VPN instance is lower than the alarm threshold of the maximum number of active routes. |
|
Recommended action |
No action is required. |
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: Public instance or VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_ACRT_REACH_THRESVALUE: Threshold value 50% of max active IPv4 routes reached in URT of vpn1 |
|
Impact |
No negative impact on the system. The device still allows new route prefixes to be activated. |
|
Cause |
The alarm threshold of the maximum number of active routes is reached in the unicast routing table of the public or VPN instance. |
|
Recommended action |
Identify whether to increase the maximum number of route prefixes or change the alarm threshold for the maximum number of active routes for the public or VPN instance. |
RM_ADD_DEFAULTRT
|
Message text |
The default route is added.(AddrFamily=[STRING], VPN=[STRING], ProcessID=[UINT32], Protocol=[STRING], SubProtocol=[STRING](UINT32), Interface=[STRING], Nexthop=[STRING], Neighbor=[STRING], Preference=[UCHAR], Cost=[UINT32], NibID=[UINT32]). |
|
Variable fields |
$1: IPv4 or IPv6. $2: VPN instance name. This parameter is displayed as default-vrf on the public network. $3: Process ID. $4: Routing protocol type. $5: Sub routing protocol. $6: Sub routing protocol ID. $7: Output interface. $8: Next hop IP address. $9: Neighboring address determined by the routing protocol. $10: Route preference. $11: Route cost. $12: Next hop ID of the route. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_ADD_DEFAULTRT: The default route is added.(AddrFamily=IPv4, VPN=default-vrf, ProcessID=0, Protocol=STATIC, SubProtocol=Static(0x1), Interface=GigabitEthernet0/0/1, Nexthop=10.1.1.2, Neighbor=0.0.0.0, Preference=60, Cost=0, NibID= 0x11000001). |
|
Impact |
The device can use the default route for packet forwarding. Packets that do not match any other routing table entries will be forwarded using the default route. |
|
Cause |
The default route was added to the routing table. |
|
Recommended action |
No action is required. |
RM_DELETE_DEFAULTRT
|
Message text |
The default route is deleted.(AddrFamily=[STRING], VPN=[STRING], ProcessID=[UINT32], Protocol=[STRING], SubProtocol=[STRING](UINT32), Interface=[STRING], Nexthop=[STRING], Neighbor=[STRING], Preference=[UCHAR], Cost=[UINT32], NibID=[UINT32]). |
|
Variable fields |
$1: IPv4 or IPv6. $2: VPN instance name. This parameter is displayed as default-vrf on the public network. $3: Process ID. $4: Routing protocol type. $5: Sub routing protocol. $6: Sub routing protocol ID. $7: Output interface. $8: Next hop IP address. $9: Neighboring address determined by the routing protocol. $10: Route preference. $11: Route cost. $12: Next hop ID of the route. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_DELETE_DEFAULTRT: The default route is deleted.(AddrFamily=IPv4, VPN=default-vrf, ProcessID=0, Protocol=Static, SubProtocol=Static(0x1), Interface=GigabitEthernet0/0/1, Nexthop=10.1.1.2, Neighbor=0.0.0.0, Preference=60, Cost=0, NibID= 0x11000001). |
|
Impact |
The device cannot use the default route for packet forwarding. Packets that do not match any other routing table entries will be discarded. |
|
Cause |
The default route was deleted. |
|
Recommended action |
No action is required. |
RM_ROUTE_BELOW_LIMIT
|
Message text |
Max active [STRING] routes [UINT32] fell below in URT of [STRING]. |
|
Variable fields |
$1: IPv4 or IPv6. $2: Maximum number of active routes. $3: Public network instance or VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_ROUTE_BELOW_LIMIT: Max active IPv4 routes 100000 fell below in URT of vpn1. |
|
Impact |
The device still allows new route prefixes to be activated. |
|
Cause |
The number of active routes in the unicast routing table of the public network instance or VPN instance dropped below the maximum number of active routes. |
|
Recommended action |
No action is required. |
RM_ROUTE_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: Public network instance or VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_ROUTE_REACH_LIMIT: Max active IPv4 routes 100000 reached in URT of vpn1. |
|
Impact |
Too many active routes occupy resources such as system memory. |
|
Cause |
The number of active routes reached the upper limit in the unicast routing table of a public network instance or VPN instance. |
|
Recommended action |
Delete routes not in use. |
RM_SID_ROUTE_CONFLICT_ACTIVE
|
Message text |
Conflict between an SRv6 local SID and a route.(SID=[STRING]/[UINT32]) |
|
Variable fields |
$1: SRv6 SID value. $2: SRv6 SID prefix length. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_SID_ROUTE_CONFLICT_ACTIVE: -MDC=1; Conflict between an SRv6 local SID and a route.(SID=100::22/128) |
|
Impact |
A configuration conflict will occur, causing packet forwarding failure. |
|
Cause |
A conflict exists between the SRv6 SID in the SRv6 local SID table and the SRv6 SID in the route configuration. |
|
Recommended action |
Identify whether the routing configuration and SRv6 SID configuration are reasonable. If not, edit the routing or SRv6 SID configuration accordingly. |
RM_SID_ROUTE_CONFLICT_CLEAR
|
Message text |
The conflict between the SRv6 local SID and a route was removed. (SID=[STRING]/[UINT32]) |
|
Variable fields |
$1: SRv6 SID value. $2: SRv6 SID prefix length. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_SID_ROUTE_CONFLICT_CLEAR: -MDC=1; The conflict between the SRv6 local SID and a route was removed.(SID=100::22/128) |
|
Impact |
The conflict between the SRv6 SID in the SRv6 local SID table and the SRv6 SID in the route configuration will be resolved. |
|
Cause |
The conflict between the SRv6 SID in the SRv6 local SID table and the SRv6 SID in the route configuration was resolved. |
|
Recommended action |
No action is required. |
RM_THRESHLD_VALUE_BELOW
|
Message text |
Threshold value [UINT32] of active [STRING] routes fell below in URT of [STRING]. |
|
Variable fields |
$1: Maximum number of active routes. $2: IPv4 or IPv6. $3: Public network instance or VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_THRESHLD_VALUE_REACH: Threshold value 10000 of active IPv4 routes fell below in URT of vpn1. |
|
Impact |
The device still allows new route prefixes to be activated. |
|
Cause |
The number of active routes in the unicast routing table of the public network instance or VPN instance dropped below the supported maximum number of active routes. |
|
Recommended action |
No action is required. |
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: Public or VPN instance name. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_THRESHLD_VALUE_REACH: Threshold value 10000 of active IPv4 routes reached in URT of vpn1. |
|
Impact |
Too many active routes occupy resources such as system memory. |
|
Cause |
The number of active routes reached the upper limit in the unicast routing table of a public or VPN instance. New route prefixes can be activated. |
|
Recommended action |
Identify whether to increase the maximum number of route prefixes for the public network instance or VPN instance. |
RM_TOTAL_THRESHLD_VALUE_CLEAR
|
Message text |
Number of active [STRING] routes fell below threshold value [UINT32] in all URTs. |
|
|
Variable fields |
$1: IPv4 or IPv6. $2: Maximum number of active routes. |
|
|
Severity level |
4 (Warning) |
|
|
Example |
RM/4/RM_TOTAL_THRESHLD_VALUE_CLEAR: Number of active IPv4 routes fell below threshold value 100000 in all URTs. |
|
|
Impact |
The device still allows new route prefixes to be activated. |
|
|
Cause |
The total number of IPv4/IPv6 active routes for the public network instance and all VPN instances dropped below the upper limit. |
|
|
Recommended action |
No action is required. |
|
RM_TOTAL_THRESHLD_VALUE_REACH
|
Message text |
Threshold value [UINT32] reached for active [STRING] routes in all URTs |
|
Variable fields |
$1: Maximum number of active routes. $2: IPv4 or IPv6. |
|
Severity level |
4 (Warning) |
|
Example |
RM/4/RM_TOTAL_THRESHLD_VALUE_REACH: Threshold value 1000 reached for active IPv4 routes in all URTs. |
|
Impact |
Too many active routes occupy resources such as system memory. New route prefixes cannot be activated. |
|
Cause |
The number of active routes in the public network and all VPN instances reached the alarm threshold. |
|
Recommended action |
Identify whether to increase the maximum number of route prefixes for the public network instance or VPN instance. |
RSVP messages
This section contains RSVP messages.
RSVP_FRR_SWITCH
|
Message text |
Session ([STRING]): FRR is [STRING]. Bypass tunnel is [USORT]. |
|
Variable fields |
$1: Information about the protected tunnel. $2: Session status. This field also displays the FRR bypass tunnel information if an FRR bypass tunnel exists. · ready—Bound to an FRR bypass tunnel. No FRR has occurred. · used—Bound to an FRR bypass tunnel. An FRR has occurred. · disabled—Unbound from the FRR bypass tunnel. $3: ID of the bypass tunnel. |
|
Severity level |
5 (Notification) |
|
Example |
|
|
Impact |
No negative impact on the system. |
|
Cause |
This log is generated when FRR protection is enabled or disabled, or an FRR has occurred. |
|
Recommended action |
No action is required. |
RSVP_P2MP_FRR_SWITCH
|
Message text |
P2MP session ([STRING]): FRR is [STRING]. Bypass tunnel is [USORT]. |
|
Variable fields |
$1: Information about the protected tunnel. $2: Session status. This field also displays the FRR bypass tunnel information if an FRR bypass tunnel exists. · ready—Bound to an FRR bypass tunnel. No FRR has occurred. · used—Bound to an FRR bypass tunnel. an FRR has occurred. · disabled—Unbound from the FRR bypass tunnel. $3: ID of the bypass tunnel. |
|
Severity level |
5 (Notification) |
|
Example |
RSVP/5/RSVP_P2MP_FRR_SWITCH: P2MP session (DIP 2.2.2.2, SIP 1.1.1.1, P2MPID 0x1010101, TID 3, LSPID 5): FRR is ready. Bypass tunnel is Tunnel5. |
|
Impact |
No negative impact on the system. |
|
Cause |
This log is generated when FRR protection is enabled or disabled, or an FRR has occurred. |
|
Recommended action |
No action is required. |
RTM messages
This section contains RTM messages.
RTM_ENVIRONMENT
|
Message text |
Can't find environment variable [STRING]. |
|
Variable fields |
$1: Name of the EAA environment variable. |
|
Severity level |
4 (Warning) |
|
Example |
RTM/4/RTM_ENVIRONMENT: Can't find environment variable eee. |
|
Impact |
The CLI monitoring policy failed to be executed. |
|
Cause |
No EAA environment variable is created. |
|
Recommended action |
Execute the rtm environment command to define an EAA environment variable before using the variable. |
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 (Warning) |
|
Example |
RTM/4/RTM_TCL_LOAD_FAILED: Failed to load the Tcl script file of policy TEST. |
|
Impact |
The Tcl-defined policy does not take effect. |
|
Cause |
The memory resource is insufficient. |
|
Recommended action |
1. Release the memory resources. Fr example, execute the logfile save command to save all the content in the log file buffer to the log file to release the memory resources occupied by the log file buffer. 2. Execute the display memory command to view display memory usage information. ¡ If the memory usage does not drop below the alarm threshold, execute the display process command to view the memory usage of user-mode processes. If a process occupies too much memory, enable or disable the software feature for that process to release the memory resources. ¡ If the memory usage drops below the alarm threshold, the alarm will be cleared. No action is required. 3. If the issue persists, collect alarm information and configuration data, and then contact Technical Support for help. |
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 (Warning) |
|
Example |
RTM/4/RTM_TCL_MODIFY: Failed to execute Tcl-defined policy aaa because the policy's Tcl script file had been modified. |
|
Impact |
The Tcl-defined policy failed to be executed. |
|
Cause |
The Tcl script file for the policy was modified. |
|
Recommended action |
Delete the Tcl policy. Then, create a new Tcl policy and bind the edited Tcl script file. |
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 (Warning) |
|
Example |
RTM/4/RTM_TCL_NOT_EXIST: Failed to execute Tcl-defined policy aaa because the policy's Tcl script file was not found. |
|
Impact |
The Tcl-defined policy failed to be executed. |
|
Cause |
The system did not find the Tcl script file for the policy while executing the policy. |
|
Recommended action |
To delete the Tcl policy if the Tcl policy is not necessary, execute the undo rtm tcl-policy command in system view. If the Tcl policy is necessary, execute the display current-configuration | include "rtm tcl-policy" command to view the name and path of the Tcl script file for the Tcl policy, and then copy the backup Tcl script file to the path specified by the rtm tcl-policy command. The name of the copied Tcl script file must be the same as the name of the Tcl script file specified by the rtm tcl-policy command. If the event specified in the Tcl policy is triggered, the device will automatically execute the Tcl policy. |
RXTX messages
This section contains RXTX messages.
PRO_ATTACK
|
Message text |
The [STRING] protocol packet input rate is greater than the speed limit, dropped packets: [UINT32]. |
|
Variable fields |
$1: Protocol name. $2: Number of packets dropped. |
|
Severity level |
4 (Warning) |
|
Example |
RXTX/4/PRO_ATTACK: The ARP protocol packet input rate is greater than the speed limit, dropped packets: 100. |
|
Impact |
Users go offline or the system gets stuck. |
|
Cause |
The input rate of abnormal protocol packets such as attack or oversize packets exceeds the speed limit. |
|
Recommended action |
· If the input rate of FTP, HTTP, IPGW, IP-IPoE, or TFTP protocol packets, perform the following operations: a. Execute the user-defined protocol-group command to adjust the speed limit. b. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. · If the input rate of other protocol packets exceeds the speed limit, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
The [STRING] allowlist protocol dropped packets due to queue congestion: [UINT32]. |
|
Variable fields |
$1: Protocol name. $2: Number of packets dropped. |
|
Severity level |
4 (Warning) |
|
Example |
RXTX/4/PRO_ATTACK: The BGP allowlist protocol dropped packets due to queue congestion: 100. |
|
Impact |
Users go offline or the system gets stuck. |
|
Cause |
Protocol packets in the allowlist are dropped due to untimely processing of queue congestion. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SAVA messages
This section contains SAVA messages.
SAVA_SET_DRV_FAILED
|
Message text |
Failed to set the driver for enabling IPv6 SAVA on interface [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 |
|
Example |
SAVA/5/SAVA_SET_DRV_FAILED: Failed to set the driver for enabling IPv6 SAVA on interface GigabitEthernet1/0/1. |
|
Impact |
The SAVA feature cannot be used normally. |
|
Cause |
The device failed to issue the command of enabling IPv6 SAVA on an interface to the driver. |
|
Recommended action |
1. Re-execute the ipv6 sava enable command to enable IPv6 SAVA on the interface. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
SAVA_SET_DRV_NO_RESOURCE
|
Message text |
Insufficient resources to set the driver for enabling IPv6 SAVA on interface [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
5 (Notification) |
|
Example |
SAVA/5/SAVA_SET_DRV_NO_RESOURCE: Insufficient resources to set the driver for enabling IPv6 SAVA on interface GigabitEthernet1/0/1. |
|
Impact |
The SAVA feature is not operating correctly. |
|
Cause |
The device failed to issue the command of enabling IPv6 SAVA on an interface to the driver due to insufficient resources. |
|
Recommended action |
1. Re-execute the ipv6 sava enable command to enable IPv6 SAVA on the interface. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
SAVA_SPOOFING_DETECTED
|
Message text |
Source IP address [STRING] spoofing packet detected : destination IP [STRING], protocol [STRING], source port [UNIT], destination port [UNIT] on interface [STRING]. |
|
Variable fields |
$1: Spoofed source IPv6 address. $2: Destination IP address. $3: IP packet protocol number. $4: Source port number. $5: Destination port number. $6: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
SAVA/6/SAVA_SPOOFING_DETECTED: Source IP address 2000::1 spoofing packet detected : destination IP 3000::2, protocol 6, source port 200, destination port 3000 on interface GigabitEthernet1/0/1. |
|
Impact |
The spoofing packet is dropped. |
|
Cause |
The device detected a source IPv6 address spoofing packet. An illegal host used the IP address of a legal user. |
|
Recommended action |
1. Check whether the packet source is legal: ¡ If the packet source is illegal, no action is required. ¡ If the packet source is legal, first execute the undo ipv6 sava packet-drop enable command to disable dropping of SAVA-detected spoofing packets. Then analyze and adjust the network configuration based on the content of the output spoofing packet log message, and execute the ipv6 sava enable command to enable dropping of SAVA-detected spoofing packets. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
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 (Warning) |
|
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. |
|
Impact |
If the process has a standby process, this issue does not have a negative impact on the system. If the process does not have a standby process, the device cannot provide the corresponding service. |
|
Cause |
A service exited abnormally. |
|
Recommended action |
1. Use the display process command to identify whether the process exists. If the process exists, the process is recovered. a. Execute the view /var/log/trace.log > trace.log command in probe view. b. Upload the trace.log file saved in the storage media of the device to the server through FTP or TFTP (in binary mode). c. Contact Technical Support. Do not reboot the device so Technical Support can help you locate the problem. |
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 (Warning) |
|
Example |
SCMD/4/PROCESS_ACTIVEFAILED: The standby process [STRING] failed to switch to the active process due to uncompleted synchronization, and was restarted. |
|
Impact |
If the active process can continue to work, this issue does not have a negative impact on the system. If the active process cannot continue to work, the device cannot provide the corresponding service. |
|
Cause |
The active process exited abnormally when the standby process has not completed synchronization. |
|
Recommended action |
Collect the device configuration file, log information, and alarm information, and then contact Technical Support. |
PROCESS_CORERECORD
|
Message text |
Exceptions occurred with process [STRING]. A core dump file was generated. |
|
Variable fields |
$1: Process name. |
|
Severity level |
5 (Notification) |
|
Example |
SCMD/5/PROCESS_CORERECORD: Exceptions occurred with process diagd. A core dump file was generated. |
|
Impact |
If the process has a standby process, this issue does not have a negative impact on the system. If the process does not have a standby process, the device cannot provide the corresponding service. |
|
Cause |
A process exited abnormally. |
|
Recommended action |
1. Execute the display exception context command to collect process exception information, and save the information to a file. 2. Execute the display exception filepath command to display the core file. 3. Upload the core file and the file that stores the process exception information to the server through FTP or TFTP (in binary mode). 4. Contact Technical Support. Do not reboot the device so Technical Support can help you locate the problem. |
SCM_ABNORMAL_REBOOT
|
Message text |
Failed to restore process [STRING]. Rebooting [STRING]. |
|
Variable fields |
Pattern 1: $1: Process name. Pattern 2: $1: Process name. $2: Chassis number and slot number, slot number, or the system. |
|
Severity level |
3 (Error) |
|
Example |
SCMD/3/SCM_ABNORMAL_REBOOT: Failed to restore process ipbased. Rebooting slot 1. |
|
Impact |
If the process has a standby process, this issue does not have a negative impact on the system. If the process does not have a standby process, the device cannot provide the corresponding service. |
|
Cause |
The process exited abnormally during the device or slot 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 issue persists, collect the device configuration file, log information, and alarm information, and then contact Technical 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 (Error) |
|
Example |
SCMD/3/SCM_ABNORMAL_REBOOTMDC: Failed to restore process ipbased on MDC 2. Rebooting MDC 2. |
|
Impact |
The MDC or context cannot provide services. |
|
Cause |
The process exited abnormally during the startup of the user 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 issue persists, collect the device configuration file, log information, and alarm information, and then contact Technical Support. |
SCM_ABORT_RESTORE
|
Message text |
|
|
Variable fields |
$1: Process name. |
|
Severity level |
3 (Error) |
|
Example |
SCMD/3/SCM_ABORT_RESTORE: Failed to restore process ipbased. Restoration aborted. |
|
Impact |
The device cannot provide the corresponding service. |
|
Cause |
The process exited abnormally during the system operation. If the process cannot recover after multiple automatic restart attempts, the device will stop restoring 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. If the issue persists, collect the output from the display process log command, and then contact Technical 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 (Warning) |
|
Example |
SCMD/4/SCM_KERNEL_INIT_TOOLONG: Kernel init in sequence 0x25e7 function 0x6645ffe2 is still starting for 15 minutes. |
|
Impact |
The device cannot start up. |
|
Cause |
A function at a phase during kernel initialization ran too long. |
|
Recommended action |
1. Wait for the device to start up. 2. If the device fails to start up within 1 hour, restart the module. 3. If the issue persists, collect the device configuration file, log information, and alarm information, and contact Technical 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 [UINT32] 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 (Warning) |
|
Example |
SCMD/4/ SCM_PROCESS_STARTING_TOOLONG: The process ipbased has not finished starting in 1 hours. |
|
Impact |
The device cannot provide the corresponding service and even cannot operate correctly. |
|
Cause |
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. If the issue persists, collect the device configuration file, log information, and alarm information, and contact Technical 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 |
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 |
6 (Informational) |
|
Example |
SCMD/6/SCM_PROCESS_STILL_STARTING: The process ipbased is still starting for 20 minutes. |
|
Impact |
No negative impact on the system. |
|
Cause |
A process is always in startup state. |
|
Recommended action |
No action is required. |
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 (Error) |
|
Example |
SCMD/3/SCM_SKIP_PROCESS: The process ipbased was skipped because it failed to start within 6 hours. |
|
Impact |
The device cannot provide the corresponding service. |
|
Cause |
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. If the issue persists, collect the device configuration file, log information, and alarm information, and contact Technical Support. |
SCRLSP messages
This section contains static CRLSP messages.
SCRLSP_LABEL_DUPLICATE
|
Message text |
Incoming label [INT32] for static CRLSP [STRING] is duplicate. |
|
Variable fields |
$1: Incoming label value. $2: Static CRLSP name. |
|
Severity level |
4 (Warning) |
|
Example |
SCRLSP/4/SCRLSP_LABEL_DUPLICATE: Incoming label 1024 for static CRLSP aaa is duplicate. |
|
Impact |
The static CRLSP cannot forward service traffic. |
|
Cause |
The incoming label of a static CRLSP was occupied by a static PW or static LSP. This message is generated when one of the following events occurs: · When MPLS is enabled, configure a static CRLSP with an incoming label which is already occupied by a static PW or static LSP. · Enable MPLS when a static CRLSP exists with an incoming label that is occupied by a static PW or static LSP. |
|
Recommended action |
Remove this static CRLSP, and reconfigure it with another incoming label. |
SESSION messages
This section contains session messages.
SESSION_DRV_EXCEED
|
Message text |
The number of session entries ([UINT32]) supported by hardware already reached. |
|
Variable fields |
$1: The maximum number of supported session entries. |
|
Severity level |
2 (Critical) |
|
Example |
SESSION/2/SESSION_DRV_EXCEED: The number of session entries (65535) supported by hardware already reached. |
|
Impact |
The CPU usage might be high when a large number of sessions are created. |
|
Cause |
The maximum number of supported session entries was reached. |
|
Recommended action |
No action is required. |
SESSION_DRV_RECOVERY
|
Message text |
Session resources supported by hardware had been released. |
|
Variable fields |
None. |
|
Severity level |
2 (Critical) |
|
Example |
SESSION/2/SESSION_DRV_RECOVERY: Session resources supported by hardware had been released. |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of session entries fell below the maximum number of supported session entries. |
|
Recommended action |
No action is required. |
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 two asterisks (**). $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 (Informational) |
|
Example |
SHELL/6/SHELL_CMD: -Line=aux0-IPAddr=**-User=**; Command is quit |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Informational) |
|
Example |
SHELL/6/SHELL_CMD_CONFIRM: Confirm option of command save is no. |
|
Impact |
No negative impact on the system. |
|
Cause |
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: Current command mode. |
|
Severity level |
4 (Warning) |
|
Example |
SHELL/4/SHELL_CMD_EXECUTEFAIL: -User=**-IPAddr=192.168.62.138; Command save in view system failed to be executed. |
|
Impact |
The command failed to be executed. |
|
Cause |
A command that a background program issued failed to be executed. |
|
Recommended action |
1. Execute the command again. 2. Verify that the command view is correct. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SHELL_CMD_INPUT
|
Message text |
|
|
Variable fields |
$1: Command string. $2: String entered by the user. |
|
Severity level |
6 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Informational) |
|
Example |
SHELL/6/SHELL_CMD_INPUT_TIMEOUT: Operation timed out: Getting input for the fdisk command. |
|
Impact |
The command failed to be executed. |
|
Cause |
The user did not respond to the input requirement of a command before the timeout timer expired. |
|
Recommended action |
Execute the command again and input the required information in time for the next step. |
SHELL_CMD_LOCKEDBYOTHER
|
Message text |
The system has been locked by [STRING]. |
|
Variable fields |
$1: Session type. |
|
Severity level |
6 (Informational) |
|
Example |
SHELL/6/SHELL_CMD_LOCKEDBYOTHER: The system has been locked by NETCONF. |
|
Impact |
The command failed to be executed. |
|
Cause |
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: Current command mode. |
|
Severity level |
4 (Warning) |
|
Example |
SHELL/4/SHELL_CMD_MATCHFAIL: -User=**-IPAddr=192.168.62.138; Command description 10 in view system failed to be matched. |
|
Impact |
The command failed to be executed. |
|
Cause |
The command string has errors, or the view does not support the command. |
|
Recommended action |
1. Verify the command is correct. 2. Verify that the command view is correct. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SHELL_CMDDENY
|
Message text |
-Line=[STRING]-IPAddr=[STRING]-User=[STRING]; Command [STRING] is permission denied. |
|
Variable fields |
$1: User line type and number. If there is not user line information, this field displays two asterisks (**). $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 |
5 (Notification) |
|
Example |
SHELL/5/SHELL_CMDDENY: -Line=vty0-IPAddr=192.168.62.138-User=**; Command vlan 10 is permission denied. |
|
Impact |
The command failed to be executed. |
|
Cause |
The user did not have the right to execute the command. |
|
Recommended action |
Verify that the user has the permission to execute the command. |
SHELL_CMDFAIL
|
Message text |
The [STRING] command failed to restore the configuration. |
|
Variable fields |
$1: Command string. |
|
Severity level |
6 (Informational) |
|
Example |
SHELL/6/SHELL_CMDFAIL: The “vlan 1024” command failed to restore the configuration. |
|
Impact |
The system failed to run the specified configuration file. |
|
Cause |
The specified command failed to be restored during a configuration restoration from a .cfg file. |
|
Recommended action |
1. Verify that the configuration file is the file saved on the device. 2. Identify whether a card is replaced on the device. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 two asterisks (**). $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 (**). |
|
Severity level |
4 (Warning) |
|
Example |
SHELL/4/SHELL_COMMIT_FAIL: -Line=aux0-IPAddr=**-User=**; Failed to commit the target configuration. |
|
Impact |
The system does not operate with the target configuration. |
|
Cause |
A target configuration commit operation failed in private or exclusive mode. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SHELL_COMMIT_ROLLBACK
|
Message text |
The configuration commit delay is overtime, a configuration rollback will be performed. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
SHELL/5/SHELL_COMMIT_ROLLBACK: The configuration commit delay is overtime, a configuration rollback will be performed. |
|
Impact |
After the configuration rollback, the system runs the configuration before the commit operation. |
|
Cause |
A timeout rollback timer was specified for submitting the target configuration. When the timeout rollback timer reaches, the device will start configuration rollback. This message is the prompt before the start of configuration rollback. |
|
Recommended action |
Complete and commit the configuration within the configuration commit delay timer. |
SHELL_COMMIT_ROLLBACKDONE
|
Message text |
The configuration rollback has been performed. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
SHELL/5/SHELL_COMMIT_ROLLBACKDONE: The configuration rollback has been performed. |
|
Impact |
The system runs the configuration before the commit operation. |
|
Cause |
A timeout rollback timer was specified for submitting the target configuration. When the timeout rollback timer reaches, the device will start configuration rollback. This message is generated when configuration rollback is completed. |
|
Recommended action |
Complete and commit the configuration within the configuration commit delay timer. |
SHELL_COMMIT_ROLLBACKFAIL
|
Message text |
Failed to roll back the configuration from the uncommitted changes. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
SHELL/5/ SHELL_COMMIT_ROLLBACKFAIL: Failed to roll back the configuration from the uncommitted changes. |
|
Impact |
Configuration rollback failed. The system fails to run the configuration before the commit operation. |
|
Cause |
A timeout rollback timer was specified for submitting the target configuration. When the timeout rollback timer reaches, the device will start configuration rollback. This message is generated when configuration rollback fails. |
|
Recommended action |
Manually perform the operations as needed. |
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 two asterisks (**). $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 (**). |
|
Severity level |
5 (Notification) |
|
Example |
SHELL/5/SHELL_COMMIT_SUCCESS: -Line=aux0-IPAddr=**-User=**; Target configuration successfully committed. |
|
Impact |
The system runs the configuration with the target configuration successfully. |
|
Cause |
A target configuration commit operation succeeded in private or exclusive mode. |
|
Recommended action |
No action is required. |
SHELL_CRITICAL_CMDFAIL
|
Message text |
-User=[STRING]-IPAddr=[STRING]; Command is [STRING] . |
|
Variable fields |
$1: Username. $2: IP address. $3: Command string. |
|
Severity level |
6 (Informational) |
|
Example |
SHELL/6/SHELL_CRITICAL_CMDFAIL: -User=admin-IPAddr=169.254.0.7; Command is save. |
|
Impact |
No negative impact on the system. |
|
Cause |
A command failed to be executed. Only the FIPS mode is supported. |
|
Recommended action |
1. Identify the failure cause and take actions as instructed. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SHELL_LOGIN
|
Message text |
[STRING] logged in from [STRING]. |
|
Variable fields |
$1: Username. $2: User line type and number. |
|
Severity level |
5 (Notification) |
|
Example |
SHELL/5/SHELL_LOGIN: Console logged in from console0. |
|
Impact |
No negative impact on the system. |
|
Cause |
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. |
|
Severity level |
5 (Notification) |
|
Example |
SHELL/5/SHELL_LOGOUT: Console logged out from console0, reason: exit normally. |
|
Impact |
No negative impact on the system. |
|
Cause |
A user logged out. If the user logged out from the standby MPU, the user line type and number field displays local. |
|
Recommended action |
No action is required. |
SHELL_SAVE_FAILED
|
Message text |
Failed to save running configuration to configuration file for configuration rollback. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
SHELL/5/SHELL_SAVE_FAILED: Failed to save running configuration to configuration file for configuration rollback. |
|
Impact |
After the target configuration command lines are committed, the system cannot restore the original running configuration before the commit operation. |
|
Cause |
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: · After the commit command is executed, the device fails to commit the target configuration command lines. · 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 (Notification) |
|
Example |
SHELL/5/SHELL_SAVE_SUCCESS: Saved running configuration to configuration file for configuration rollback. |
|
Impact |
No negative impact on the system. |
|
Cause |
The system saved the running configuration to the configuration file successfully and supports a rollback. The system saves the running configuration to the configuration file in the following situations: · After the commit command is executed, the device fails to commit the target configuration command lines. · 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 (Notification) |
|
Example |
SHELL/5/SHELL_SAVEPOINT_EXIST: The running configuration at this rollback point is the same as the configuration at the previous rollback point. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Notification) |
|
Example |
SHELL/5/SHELL_SAVEPOINT_FAILED: Failed to create a new rollback point. |
|
Impact |
The system failed to quickly restore the current configuration to the configuration in the specified configuration file. |
|
Cause |
An attempt to create a new rollback point failed. |
|
Recommended action |
To save the rollback point: 1. Manually roll back to the rollback point. 2. Verify the file system. For example, verify that the remaining space of the file system is sufficient. 3. Execute the commit command again. |
SHELL_SAVEPOINT_SUCCESS
|
Message text |
Created a new rollback point. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
SHELL/5/SHELL_SAVEPOINT_SUCCESS: Created a new rollback point. |
|
Impact |
No negative impact on the system. |
|
Cause |
An attempt to create a new rollback point succeeded. |
|
Recommended action |
No action is required. |
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 (Warning) |
|
Example |
SLSP/4/SLSP_LABEL_DUPLICATE: Incoming label 1024 for static LSP aaa is duplicate. |
|
Impact |
The static LSP is unavailable and cannot be used to forward service traffic. |
|
Cause |
The incoming label of the static LSP was occupied by a static PW, static CRLSP, or a static SRLSP. This message is generated under one of the following circumstances: · A static LSP with an incoming label that is already occupied by a static PW, static CRLSP, or static SRLSP is configured while MPLS is enabled. · MPLS is enabled when there is already a static LSP on the device with an incoming label occupied by a static PW, static CRLSP, or static SRLSP. |
|
Recommended action |
Remove this static LSP, and reconfigure it with another incoming label. |
SNMP
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. $2: IP address of the NMS. |
|
Severity level |
3 (Error) |
|
Example |
SNMP/3/SNMP_ACL_RESTRICTION: SNMP community public from 192.168.1.100 is rejected due to ACL restrictions. |
|
Impact |
The NMS cannot access the device. |
|
Cause |
The IP address and other parameters of the NMS did not match the SNMP ACL. |
|
Recommended action |
Identify whether the IP address in the prompt is a valid NMS IP address: · If the IP address is a valid NMS IP address, identify whether the ACL configuration is correct. · Use the display snmp-agent community command to check the ACL number referenced by the SNMP community name in the log message. Execute the display snmp-agent group and display snmp-agent usm-user commands to view the ACL number referenced by the SNMP username/group name in the log message. Then, execute the display acl command to review the configuration of the ACL. If the ACL configuration is incorrect, execute the rule command in ACL view to edit the filter rule in the ACL. · If the IP address is an invalid NMS IP address, no action is required. |
SNMP_AUTHEN_FAILURES
|
Message text |
[UINT32] SNMP authentication failures in the most recent 60s. |
|
Variable fields |
$1: Number of suppressed SNMP authentication failures. |
|
Severity level |
4 (Warning) |
|
Example |
SNMP/4/SNMP_AUTHEN_FAILURES: 17 SNMP authentication failures in the most recent 60s. |
|
Impact |
The NMS cannot access the device. |
|
Cause |
When the device receives the first SNMP request and the authentication fails, it generates the SNMP_AUTHENTICATION_FAILURE message and starts a 60-minute timer. If the device continuously receives multiple SNMP requests within 60 seconds and all the requests fail authentication, the agent generates this message to record the total number of SNMP authentication failures within that period. This can prevent frequent log outputs that could consume system resources. |
|
Recommended action |
See the recommended action in SNMP_AUTHENTICATION_FAILURE. |
SNMP_AUTHENTICATION_FAILURE
|
Message text |
|
|
Variable fields |
N/A. |
|
Severity level |
4 (Warning) |
|
Example |
SNMP/4/SNMP_AUTHENTICATION_FAILURE: Failed to authenticate SNMP message. |
|
Impact |
The NMS cannot access the device. |
|
Cause |
The NMS initiates an SNMP request to the device, but fails to pass authentication. |
|
Recommended action |
Execute the display snmp-agent sys-info command to check the SNMP version used by the device. Different SNMP versions support different security authentication methods. · For SNMPv1 and SNMPv2c, authentication and encryption are not supported and community names are used for security authentication. The device and NMS must use the same community name. Execute the display snmp-agent community command to view the community name used on the device. To access the device from the NMS, use the same community name, or create a community on the device by using the snmp-agent community command and make sure the community name is the same as that on the NMS. · For SNMPv3, authentication and encryption are supported and the device and NMS must use the same security authentication parameters, including username, whether to authenticate, whether to encrypt, the password for authentication, and the password for encryption. Execute the display snmp-agent group and display snmp-agent usm-user commands to view the device's security authentication parameters. If they differ from those on the NMS, edit the NMS's security authentication parameters, or use the snmp-agent group and snmp-agent usm-user v3 commands to change the authentication parameters. |
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 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device has SNMP logging enabled and received a get request sent by the NMS. |
|
Recommended action |
No action is required. |
SNMP_INFORM_LOST
|
Message text |
Inform failed to reach NMS [STRING]: Inform [STRING][STRING]. |
|
Variable fields |
$1: NMS host address and port number. $2: Notification name and OID. $3: Variable-binding field of notifications. ¡ If no MIB object exists, NMS host address and port number and 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 |
3 (Error) |
|
Example |
SNMP/3/SNMP_INFORM_LOST: Inform failed to reach NMS 192.168.111.222(163): Inform coldStart(1.3.6.1.6.3.1.1.5.1). |
|
Impact |
No negative impact on the system. |
|
Cause |
The device sent an inform message to the NMS, and has not received a response until the inform message times out. Possible causes: · The NMS is unreachable. · The SNMP service of the NMS is unavailable. · Configuration error. The network latency is large between the device and the NMS in both directions, exceeding the timeout period for inform messages. |
|
Recommended action |
· Execute the ping command to ping the NMS at the IP address displayed in the log message. If the ping operation fails, the NMS is unreachable. Resolve the issue as required. · Configure the NQA SNMP operation on the device to identify whether the NMS service is available. If the operation fails, resolve the issue as required. · Execute the display current-configuration | include snmp-agent inform source command and check the output from the command: ¡ Check the configuration of the snmp-agent target-host inform command in the output to verify that the NMS's IP address, UDP port, VPN, SNMP version number, and security authentication parameters match those on the NMS. If not, execute the snmp-agent target-host inform command to edit them. ¡ Check the output for the snmp-agent inform source command to identify whether a source interface is configured for inform messages. If a source interface is configured, the interface must be in up state, and the interface IP address must be reachable to the NMS's IP address. If not, resolve the issue with the unavailable source interface or specify a new source interface. Use ping to check the round-trip latency and packet loss rate in both directions. If the latency is too high (configurable using the snmp-agent trap periodical-interval command, with a default value of 60 seconds) or the packet loss rate exceeds 20%, the network is in poor condition. Address the network quality issues or switch to the backup link. |
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 (Informational) |
|
Example |
Example of a complete message: 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. Example of a fragmented message: SNMP/6/SNMP_NOTIFY: -MDC=1; -PART=1; Notification syslogMsgNotification(1.3.6.1.2.1.192.0.1) with syslogMsgFacility(1.3.6.1.2.1.192.1.2.1.2.1)=23;syslogMsgSeverity(1.3.6.1.2.1.192.1.2.1.3.1)=6;syslogMsgVersion(1.3.6.1.2.1.192.1.2.1.4.1)=1;syslogMsgTimeStamp(1.3.6.1.2.1.192.1.2.1.5.1)=07-e2-04-12-12-26-35-00-00-00-2d-00-00[hex];syslogMsgHostName(1.3.6.1.2.1.192.1.2.1.6.1)=H3C;syslogMsgAppName(1.3.6.1.2.1.192.1.2.1.7.1)=SHELL;syslogMsgProcID(1.3.6.1.2.1.192.1.2.1.8.1)=-;syslogMsgMsgID(1.3.6.1.2.1.192.1.2.1.9.1)=SHELL_CMD;syslogMsgSDParams(1.3.6.1.2.1.192.1.2.1.10.1)=4;syslogMsgMsg(1.3.6.1.2.1.192.1.2.1.11.1)= Command is snmp-agent trap enable syslog;syslogMsgSDParamValue(1.3.6.1.2.1.192.1.3.1.4.1.1.12.83.121.115.76.111.99.64.50.53.53.48.54.3.77.68.67)=1;syslogMsgSDParamValue(1.3.6.1.2.1.192.1.3.1.4.1.2.12.65.112.112.76.111.99.64.50.53.53.48.54.4.76.105.110.101)=con0. SNMP/6/SNMP_NOTIFY: -MDC=1; -PART=2; Notification syslogMsgNotification(1.3.6.1.2.1.192.0.1) with syslogMsgSDParamValue(1.3.6.1.2.1.192.1.3.1.4.1.3.12.65.112.112.76.111.99.64.50.53.53.48.54.6.73.80.65.100.100.114)=**;syslogMsgSDParamValue(1.3.6.1.2.1.192.1.3.1.4.1.4.12.65.112.112.76.111.99.64.50.53.53.48.54.4.85.115.101.114)=**. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device has SNMP notifications feature and the device sent SNMP notifications to the NMS. |
|
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 (Informational) |
|
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. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device has SNMP logging enabled and received a get request sent by the NMS. |
|
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 (Warning) |
|
Example |
SNMP/4/SNMP_USM_NOTINTIMEWINDOW: -User=admin-IPAddr=169.254.0.7; SNMPv3 message is not in the time window. |
|
Impact |
No negative impact on the system. |
|
Cause |
When the timeout timer expires, the device still has not received an SNMPv3 response. |
|
Recommended action |
1. Resend SNMPv3 requests. 2. After re-establishing the SNMPv3 connection, retransmit the SNMPv3 request. If a response is received from the peer, no further processing is required; if not, proceed to step 3. 3. Ping the IP address of the NMS. If the ping operation fails, first identify the issue that causes the failure. 4. Identify whether the SNMP server on the NMS is operating correctly. If not, restart the SNMP server on the NMS. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
SNMP_IPLOCK
|
Message text |
The source IP was locked for [UINT] seconds because of the failure of login through SNMP.(SourceIP=[STRING], VPN=[STRING]) |
|
Variable fields |
$1: Locking period for the IP address, 8, 16, 32, or 300, in seconds. $2: IP address with failed connection. $3: VPN instance number. |
|
Severity level |
4 (Warning) |
|
Example |
SNMP/4/SNMP_IPLOCK: The source IP was locked for 8 seconds because of the failure of login through SNMP.(SourceIP=192.168.1.0, VPN=0) |
|
Impact |
No negative impact on the system. |
|
Cause |
The SNMP IP blacklist feature is enabled and the NMS failed to log in to the device. |
|
Recommended action |
Identify whether the IP address in the prompt is a valid NMS IP address: · If the IP address is an invalid NMS IP address, no action is required. · If the IP address is a valid NMS IP address, the SNMP access parameters used by the NMS are incorrect. See the SNMP_AUTHEN_FAILURES log to take actions as needed. After the locking period expires, the device will automatically unlock this IP address, and the NMS can access the device by using correct parameters. |
SNMP_IPUNLOCK
|
Message text |
The source IP was unlocked(SourceIP=[STRING], VPN=[STRING]) |
|
|
Variable fields |
$1: IP address with failed connection. $2: VPN number. |
|
|
Severity level |
5 (Notification) |
|
|
Example |
SNMP/5/SNMP_IPUNLOCK: The source IP was unlocked(SourceIP=192.168.1.0, VPN=0). |
|
|
Impact |
No negative impact on the system. |
|
|
Cause |
The IP address locking timer has expired and no NMS login failures occur within the timeout period. |
|
|
Recommended action |
No action is required. |
|
SNMP_IPLOCKSTAT
|
Message text |
In the last 5 minutes, [UINT32] IP addresses were locked. (IPList=(IP=[STRING])) |
|
Variable fields |
$1: Number of IP addresses locked in the past five minutes. $2: List of locked IP addresses. |
|
Severity level |
4 (Warning) |
|
Example |
SNMP/4/SNMP_IPLOCKSTAT: In the last 5 minutes,2 IP addresses were locked.(IPList=(IP=192.168.73.43),( IP=192.168.73.44)) |
|
Impact |
No negative impact on the system. |
|
Cause |
When the number of IP addresses locked by the SNMP IP blacklist feature exceeds three, the system no longer outputs the SNMP_IPLOCK log for newly locked IP addresses. Instead, it outputs a statistical log every five minutes. |
|
Recommended action |
See the recommended action in the SNMP_IPLOCK log. |
SNMP_IPUNLOCKSTAT
|
Message text |
In the last 5 minutes, [UINT32] IP addresses were unlocked. (IPList=(IP=[STRING])) |
|
Variable fields |
$1: Number of IP addresses unlocked in the past five minutes. $2: List of unlocked IP addresses. |
|
Severity level |
5 (Notification) |
|
Example |
SNMP/5/SNMP_IPUNLOCKSTAT: In the last 5 minutes,2 IP addresses were unlocked.(IPList=(IP=192.168.73.43),( IP=192.168.73.44)) |
|
Impact |
No negative impact on the system. |
|
Cause |
The IP address locking timer has expired and no NMS login failures occur within the timeout period. |
|
Recommended action |
No action is required. |
SNMP_USER_DENYLIST
|
Message text |
[STRING] added into the username denylist. |
|
Variable fields |
$1: SNMPv3 username. |
|
Severity level |
4 (Warning) |
|
Example |
SNMP/4/SNMP_USER_DENYLIST: aaa added into the username denylist. |
|
Impact |
No negative impact on the system. |
|
Cause |
If the number of authentication failures for an SNMP user exceeds the upper limit within the specified period, SNMP will lock the user by adding it to the denylist. |
|
Recommended action |
Identify whether the device has been subjected to an SNMP attack: · If the device is subjected to an SNMP attack, and an unauthorized NMS fails to access the device by using an invalid SNMPv3 username, causing the SNMPv3 username to be locked, no action is required. · If the device has not been subjected to an SNMP attack, and the NMS is legitimate but has been locked due to incorrect access parameters, perform the following steps: ¡ For SNMPv3, authentication and encryption are supported and the device and NMS must use the same security authentication parameters, including username, whether to authenticate, whether to encrypt, the password for authentication, and the password for encryption. Execute the display snmp-agent group and display snmp-agent usm-user commands to view the device's security authentication parameters. If they differ from those on the NMS, edit the NMS's security authentication parameters, or use the snmp-agent group and snmp-agent usm-user v3 commands to change the authentication parameters. ¡ If the SNMPv3 username used by the NMS is correct, but it gets locked due to other security authentication parameter errors, use the snmp-agent denylist user activate command to immediately unlock the user, or wait until the locking timer expires for automatic unlocking. ¡ Access the device by using the correct security authentication parameters on the NMS. · If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
SNMP_USER_DENYLIST_RELEASE
|
Message text |
[STRING] released from the username denylist. |
|
Variable fields |
$1: SNMPv3 username. |
|
Severity level |
5 (Notification) |
|
Example |
SNMP/5/SNMP_USER_DENYLIST_RELEASE: aaa released from the username denylist. |
|
Impact |
No negative impact on the system. |
|
Cause |
· The snmp-agent denylist user activate command was executed to immediately unlock a locked username. · The locking timer expired, the locked username automatically unlocked. |
|
Recommended action |
No action is required. |
SRP
This section contains SR-MPLS TE policy messages.
SRP_BSID_CONFLICT
|
Message text |
Allocating a binding SID to an SR-TE policy failed. (Color [UINT32], Endpoint [STRING], BSID [UINT32], Reason [STRING], ConflictState [STRING]). |
|
Variable fields |
$1: Color value of the SR-MPLS TE policy. $2: End-point address of the SR-MPLS TE policy. $3: BSID of the SR-MPLS TE policy. $4: Reason why the BSID conflict occurred. Possible reasons include: · The binding SID of a manually configured SR-TE policy is the same as that of a different SR-TE policy delivered by BGP. · Different SR-TE policies dynamically delivered by BGP have the same binding SID. · Different manually configured SR-TE policies have the same binding SID. · Binding SID is out of the SRGB and SRLB ranges. $5: Conflict state. inConflict means that the BSID is in a conflict state. |
|
Severity level |
2 (Critical) |
|
Example |
SRP/2/SRP_BSID_CONFLICT: Allocating a binding SID to an SR-TE policy fails.(Color 10, Endpoint 1.2.3.4, BSID 15000, Reason The binding SID of a manually configured SR-TE policy is the same as that of a different SR-TE policy delivered by BGP, ConflictState inConflict). |
|
Impact |
The failure to allocate a BSID for an SR-MPLS TE Policy will result in the policy becoming ineffective and unable to be used for forwarding. |
|
Cause |
The device detected a BSID conflict or allocation failure for an SR-MPLS TE policy. |
|
Recommended action |
1. Use the display segment-routing te policy command to identify the SR-MPLS TE policy that uses the conflicted BSID, and then change the BSID of that SR-MPLS TE policy. Then, execute the display segment-routing te policy command to verify if the Request state field displays Succeeded. If this field displays Succeeded, it indicates that BSID allocation is normal. If not, proceed to the next step. 2. Collect the device configuration file, log information, and alarm information, and contact H3C Support. |
SRP_BSID_CONFLICT_CLEAR
|
Message text |
The binding SID allocation failure is resolved.(Color [UINT32], Endpoint [STRING], BSID [UINT32], Reason [STRING], ConflictState [STRING]). |
|
Variable fields |
$1: Color value of the SR-MPLS TE policy. $2: End-point address of the SR-MPLS TE policy. $3: BSID of the SR-MPLS TE policy. $4: Reason why the BSID conflict was resolved. · The binding SID that failed to be allocated was deleted. · The SR-TE policy with a binding SID allocation failure was deleted. · Binding SID allocation succeeded. $5: Current conflict state. conflictResolved means that the conflict has been resolved. |
|
Severity level |
2 (Critical) |
|
Example |
SRP/2/SRP_BSID_CONFLICT_CLEAR: The binding SID allocation failure is resolved.( Color 10, Endpoint 1.2.3.4, BSID 16, Reason The binding SID that failed to be allocated was deleted., ConflictState conflictResolved). |
|
Impact |
No negative impact on the system. |
|
Cause |
The BSID conflict for an SR-MPLS TE policy has been resolved, probably because the conflict BSID has been deleted or the SR-MPLS TE policy that uses the BSID has been deleted. |
|
Recommended action |
No action is required. |
SRP_PATH_STATE_DOWN
|
Message text |
SR-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 SR-MPLS TE policy. $2: End-point address of the SR-MPLS TE policy. $3: Candidate path origin. Options include: · CLI—Manually configured. · BGP—Obtained from the BGP SR Policy route. · PCEP—Obtained through PCEP. $4: BGP instance number. This field is available only when the candidate path origin is BGP. $5: Head node of the candidate path, represented in the form of ASN Nodeaddress, where ASN is the AS number and Nodeaddress is the router ID of the BGP peer. This field is available only when the candidate path origin is BGP. $6: Discriminator of the candidate path. $7: Preference of the candidate path. $8: Role of the candidate path, Primary or Backup. $9: Reason why the candidate path went down. Possible reasons include: · Higher preference path exists. · Candidate path is shutdown. · Candidate path is deleted. · No valid SID lists. · Candidate path has empty SID lists. · SBFD session was down. · BFD session was down. · The color and endpoint were deleted. |
|
Severity level |
5 (Notification) |
|
Example |
SRP/5/SRP_PATH_STATE_DOWN: SR-TE policy candidate path is down: Color 10, EndPoint 1.2.3.4, Origin BGP, Instance 0, Originator 10 1.1.1.1, Discriminator 100, Preference 100, PreviousRole Primary, Reason Higher preference path exists. |
|
Impact |
This candidate path cannot be used for traffic forwarding. |
|
Cause |
The candidate path of an SR-MPLS TE policy went down. |
|
Recommended action |
Process according to the reason displayed. |
SRP_POLICY_STATUS_CHG
|
Message text |
SR-TE policy (Color [UINT32], EndPoint [STRING]) status changed from [STRING] to [STRING]. Down Reason: [STRING]. |
|
Variable fields |
$1: Color value of the SR-MPLS TE policy. $2: End-point address of the SR-MPLS TE policy. $3: Old state, which can only be up. $4: New state, which can only be down. $5: Reason why the forwarding state of the SR-MPLS TE policy became down. Possible reasons include: · SBFD session was down. · Administratively down. · No candidate paths. · No valid candidate paths. · No valid SID lists. · The color and endpoint were deleted. |
|
Severity level |
4 (Warning) |
|
Example |
SRP/4/SRP_POLICY_STATUS_CHG: SR-TE policy Color 10 EndPont 1.2.3.4 status changed from up to down. Down Reason: The color and end-point were deleted. |
|
Impact |
The SR-MPLS TE Policy is unavailable. |
|
Cause |
The forwarding state of an SR-MPLS TE policy changed from up to down. |
|
Recommended action |
Process according to the reason displayed. |
SRP_SEGLIST_STATE_DOWN
|
Message text |
SR-TE policy SID list forwarding state down event: Color [UINT32], EndPoint [STRING], Origin [STRING], Instance [UINT32], Originator [STRING], Discriminator [UINT32], SegListID [UINT32], Reason [STRING]. |
|
Variable fields |
$1: Color value of the SR-MPLS TE policy. $2: End-point address of the SR-MPLS TE policy. $3: Candidate path origin. Options include: · CLI—Manually configured. · BGP—Obtained from the BGP SR Policy route. · PCEP—Obtained through PCEP. $4: BGP instance number. This field is available only when the candidate path origin is BGP. $5: Head node of the candidate path, represented in the form of ASN Nodeaddress, where ASN is the AS number and Nodeaddress is the router ID of the BGP peer. This field is available only when the candidate path origin is BGP. $6: Discriminator of the SID list. $7: Index of the SID list. $8: Reason why the forwarding state of the SID list became down. Possible reasons include: · Segment list was unavailable. · SBFD session was down. · BFD session was down. |
|
Severity level |
5 (Notification) |
|
Example |
SRP/5/SRP_SEGLIST_STATE_DOWN: SR-TE policy SID list forwarding state down event: Color 10, EndPoint 1.1.1.1, Origin BGP, Instance 0, Originator 10 2.2.2.2, Discriminator 100, SegListID 1, Reason Segment list was unavailable. |
|
Impact |
Traffic is switched to other segment lists in the candidate path for forwarding. If no other segment lists exist, it switches to another candidate for forwarding. If no valid alternative candidate paths exist, traffic forwarding fails. |
|
Cause |
The forwarding state of a SID list went down. |
|
Recommended action |
Examine the link status of the forwarding path identified by the SID list according to the reason displayed, and verify that the SBFD settings are correct. |
SRP_SEGLIST_STATE_DOWN_CLEAR
|
Message text |
SR-TE policy SID list forwarding down is resolved. (Color [UINT32], EndPoint [STRING], Origin [STRING], Instance [UINT32], Originator [STRING], Discriminator [UINT32], SegListID [UINT32]) |
|
Variable fields |
$1: Color value of the SR-MPLS TE policy. $2: End-point address of the SR-MPLS TE policy. $3: Candidate path origin. Options include: · CLI—Manually configured. · BGP—Obtained from the BGP SR Policy route. · PCEP—Obtained through PCEP. $4: BGP instance number. This field is available only when the candidate path origin is BGP. $5: Head node of the candidate path, represented in the form of ASN Nodeaddress, where ASN is the AS number and Nodeaddress is the router ID of the BGP peer. This field is available only when the candidate path origin is BGP. $6: Discriminator of the SID list. $7: Index of the SID list. |
|
Severity level |
5 (Notification) |
|
Example |
SRP/5/SRP_SEGLIST_STATE_DOWN _CLEAR: SR-TE policy SID list forwarding down is resolved. (Color 10, EndPoint 1.1.1.1, Origin BGP, Instance 0, Originator 10 2.2.2.2, Discriminator 100, SegListID 1) |
|
Impact |
No negative impact on the system. |
|
Cause |
The forwarding state of a SID list became up, and the down state alarm has been cleared. |
|
Recommended action |
No action is required. |
SRP_STATE_DOWN
|
Message text |
SR-TE policy (Color [UINT32], EndPoint [STRING]) forwarding state went down: [STRING]. |
|
Variable fields |
$1: Color value of the SR-MPLS TE policy. $2: End-point address of the SR-MPLS TE policy. $3: Reason when the SR-MPLS TE policy went down. Possible reasons include: · SBFD session was down. · No candidate paths. · No valid candidate paths. · No valid SID lists. · The color and endpoint were deleted. · Administratively down. |
|
Severity level |
2 (Critical) |
|
Example |
SRP/2/SRP_STATE_DOWN: SR-TE policy (Color 10, EndPoint 1.1.1.1) forwarding state went down: No candidate paths. |
|
Impact |
Traffic cannot be forwarded through the SR-MPLS TE Policy. |
|
Cause |
An SR-MPLS TE policy went down. |
|
Recommended action |
Process according to the reason displayed. |
SRP_STATE_DOWN_CLEAR
|
Message text |
SR-TE policy (Color [UINT32], EndPoint [STRING]) down alarm was cleared. |
|
Variable fields |
$1: Color value of the SR-MPLS TE policy. $1: End-point address of the SR-MPLS TE policy. |
|
Severity level |
2 (Critical) |
|
Example |
SRP/2/SRP_STATE_DOWN_CLEAR: SR-TE policy (Color 10, EndPoint 1.1.1.1) down alarm was cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The forwarding state of an SR-MPLS TE policy became up, and the down state alarm has been cleared. |
|
Recommended action |
No action is required. |
SRPM messages
This section contains SRPM messages.
SRPM_IC
|
Message text |
No enough resources. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
SRPM/4/ SRPM_IC: -MDC=1-Slot=4; No enough resources. |
|
Impact |
The SRPM feature might fail to take effect. |
|
Cause |
Resources were insufficient. |
|
Recommended action |
1. Delete unused configuration to release resources. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SRPM_IC
|
Message text |
This module does not support SRPM. Please check your configuration. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
SRPM/4/SRPM_IC: -MDC=1-Slot=4; This module does not support SRPM. Please check your configuration. |
|
Impact |
The SRPM feature cannot be used. |
|
Cause |
The module does not support SRPM. |
|
Recommended action |
1. Change the card: 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SRPM messages
This section contains Segment Routing Performance Measurement (SRPM) messages.
SRPM_DRV
|
Message text |
Interface [STRING] failed to issue the configuration to the driver in the slot. |
|
Variable fields |
$1: Layer 3 interface/subinterface name. |
|
Severity level |
5 (Notification) |
|
Example |
SRPM/5/SRPM_DRV: -MDC=1-Slot=1; Interface Route-Aggregation1 failed to issue the configuration to the driver in the slot. |
|
Impact |
Configuration deployment fails. |
|
Cause |
Failed to issue the srpm delay-profile link-based query enable or srpm delay-profile link-based response enable command configured on a Layer 3 Ethernet interface/subinterface or a Layer 3 aggregate interface/subinterface to the driver in the slot. The reason might be insufficient hardware resources of the slot associated with the Layer 3 Ethernet interface or aggregation group member port. |
|
Recommended action |
Collect the device configuration file, log information, and alarm information, and contact H3C Support. |
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 (Critical) |
|
Example |
SRPV6/2/SRPV6_BSID_CONFLICT: Allocating a binding SID to an SRv6-TE Policy failed.(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). |
|
Impact |
Failure in assigning the BSID for SRv6 TE Policy will result in the SRv6 TE Policy becoming invalid and unusable for forwarding. |
|
Cause |
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. Then, execute display segment-routing ipv6 te policy to verify if the Request state field displays Succeeded. If this field displays Succeeded, it indicates that BSID application is normal. If not, proceed to the next step. 2. Collect the device configuration file, log information, and alarm information, and 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 (Critical) |
|
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). |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Notification) |
|
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. |
|
Impact |
The candidate path cannot be used for traffic forwarding. |
|
Cause |
The SRv6 TE policy candidate path went down. |
|
Recommended action |
Resolve the issue based on the candidate path down reason. |
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 (Warning) |
|
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. |
|
Impact |
The SRv6 TE Policy is unavailable. |
|
Cause |
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. |
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 (Warning) |
|
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). |
|
Impact |
New SRv6 TE Policies or SRv6 TE Policy groups cannot be created, which might lead to traffic forwarding anomalies in the SRv6 TE Policy or SRv6 TE Policy group used for traffic forwarding. |
|
Cause |
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 (Warning) |
|
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). |
|
Impact |
No negative impact on the system. |
|
Cause |
The number of SRv6 TE policy resources has returned to normal from an exceeded state. |
|
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 (Notification) |
|
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. |
|
Impact |
Traffic is switched to another segment list in the candidate path for forwarding. If no other segment list exists, it switches to another candidate. If no valid alternative candidate path exists, traffic forwarding will fail. |
|
Cause |
The SID list forwarding state went down. |
|
Recommended action |
Examine the link status for the SID list forwarding path and the SBFD configuration based on the list down reason. |
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 (Notification) |
|
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) |
|
Impact |
No negative impact on the system. |
|
Cause |
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 why the forwarding state of the SRv6 TE policy went down: · SBFD session was down—The SBFD session used to detect the SRv6 TE policy went down. · BFD session was down—The BFD session used to detect the SRv6 TE policy went down. · Administrately down—The SRv6 TE policy was manually shut down with the shutdown command. · No candidate path—No candidate path exists in the SRv6 TE policy. · No valid candidate path—No valid candidate path exists in the SRv6 TE policy · No valid segment list—No valid SID list exists in the candidate path of the SRv6 TE policy. · The color and end-point were deleted—The color value and endpoint node address of the SRv6 TE policy were deleted. |
|
Severity level |
2 (Critical) |
|
Example |
SRPV6/2/SRPV6_STATE_DOWN: SRv6-TE policy (Color 10, EndPoint 10::10) forwarding state went down: SBFD session was down. |
|
Impact |
Traffic cannot be forwarded by the SRv6 TE policy . |
|
Cause |
The forwarding state of the SRv6 TE policy went down. |
|
Recommended action |
Take an action based on the reason why the forwarding state of the SRv6 TE policy went down: · SBFD session was down—Execute the bfd trigger path-down disable command to disable BFD session down events from triggering SRv6 TE policy path switchover, or check the network status to ensure the SBFD session can operate correctly. · BFD session was down—Execute the bfd trigger path-down disable command to disable BFD session down events from triggering SRv6 TE policy path switchover, or check the network status to ensure the BFD session can operate correctly. · Administrately down—Execute the undo shutdown command to bring up the SRv6 TE policy. · No candidate path—Configure a valid candidate path for the SRv6 TE policy. · No valid candidate path—Configure a valid candidate path for the SRv6 TE policy. · No valid segment list—Specify a valid SID list for the candidate path. · The color and end-point were deleted—Execute the color end-point command to configure the color and endpoint node address for the SRv6 TE policy again, and make sure the endpoint node address is routable. |
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 (Critical) |
|
Example |
SRPV6/2/SRPV6_STATE_DOWN_CLEAR: SRv6-TE policy (Color 10, EndPoint 10 10::10) down alarm was cleared. |
|
Impact |
No negative impact on the system. |
|
Cause |
The alarm that the forwarding state of the SRv6 TE policy went down has been cleared. That is, the forwarding state of the SRv6 TE policy became up. |
|
Recommended action |
No action is required. |
SRv6 messages
This section contains SRv6 messages.
SRV6_NO_SUPPORT
|
Message text |
SRv6 is not supported in this slot. |
|
Severity level |
5 (Notification) |
|
Example |
SRV6/5/SRV6_NO_SUPPORT: SRv6 is not supported in this slot. |
|
Impact |
The slot cannot process SRv6 services. |
|
Cause |
The slot does not support the SRv6 feature. |
|
Recommended action |
Replace the card in the slot with a card that supports SRv6. |
SSHC messages
This section contains SSH client messages.
SSHC_ALGORITHM_MISMATCH
|
Message text |
Failed to log in to SSH server [STRING] because of [STRING] algorithm mismatch. |
|
Variable fields |
$1: IP address of the SSH server. $2: Type of the algorithm: ¡ encryption—Encryption algorithm. ¡ key exchange—Key exchange algorithm. ¡ MAC—HMAC algorithm. ¡ public key—Public key algorithm. |
|
Severity level |
6 (Informational) |
|
Example |
SSHC/6/SSHC_ALGORITHM_MISMATCH: Failed to log in to SSH server 192.168.30.11 because of encryption algorithm mismatch. |
|
Impact |
SSH clients cannot log in to the server. |
|
Cause |
The SSH client and server algorithms do not match. |
|
Recommended action |
Change algorithms used by the SSH client to ensure that the SSH client and the SSH server use algorithms of the same type. |
SSHC_CONFIRM
|
Message text |
Confirm option of "[STRING]" is [STRING]. |
|
Variable fields |
$1: SSH client confirm information. $2: Confirm result for the information: · yes—The information was executed. · no—The information was not executed. · Timeout—The information was not confirmed within a specified time. |
|
Severity level |
6 (Informational) |
|
Example |
SSHC/6/SSHC_CONFIRM: Confirm option of "The file with the same name already exists, Overwrite it?" is yes. |
|
Impact |
No negative impact on the system. |
|
Cause |
The user confirmed SSH client confirm information. |
|
Recommended action |
No action is required. |
SSHS
This section contains SSH server messages.
SSHS_ACL_DENY
|
Message text |
The SSH Connection [IPADDR]([STRING]) request was denied according to ACL rules. |
|
Variable fields |
$1: IP address of the SSH client. $2: IP address of the SSH client in the VPN |
|
Severity level |
5 (Notification) |
|
Example |
SSHS/5/SSH_ACL_DENY: The SSH Connection 1.2.3.4(vpn1) request was denied according to ACL rules. |
|
Impact |
SSH client login failed |
|
Cause |
The device has access control configured for the SSH client, and the client's IP address is not within the permit range defined in the ACL |
|
Recommended action |
Confirm if the user corresponding to this IP address is unauthorized: · If yes, no action is required. · If not, modify the ACL configuration to include the client's IP address in the permit rules |
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: Algorithm type: ¡ encryption. ¡ key exchange. ¡ MAC. public key. |
|
Severity level |
6 (Informational) |
|
Example |
SSHS/6/SSHS_ALGORITHM_MISMATCH: SSH client 192.168.30.117 failed to log in because of encryption algorithm mismatch. |
|
Impact |
SSH client login failed |
|
Cause |
SSH client and server-side algorithms do not match |
|
Recommended action |
Modify the algorithm to make the SSH client and server use the same type of 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: Username. $2: IP address of the SSH client. |
|
Severity level |
6 (Informational) |
|
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. |
|
Impact |
The system may be under attack by unauthorized users |
|
Cause |
The maximum number of SSH user authentication attempts is reached |
|
Recommended action |
1. Check the log to see if the user is unauthorized: ¡ If so, modify the ACL configuration to exclude the unauthorized client's IP address from the permit rules ¡ If not, contact the administrator for the correct username and password. If the alarm persists, go to step 2 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 reason: · wrong public key algorithm. · wrong public key. · wrong digital signature. |
|
Severity level |
5 (Notification) |
|
Example |
SSHS/5/SSHS_AUTH_FAIL: SSH user David (IP: 192.168.30.117) didn't pass public key authentication for wrong public key algorithm. |
|
Impact |
SSH client login failed |
|
Cause |
SSH user failed public key authentication |
|
Recommended action |
Reason 1: wrong public key algorithm 1. Check if the SSH client authentication uses the DSA algorithm in FIPS mode: ¡ If so, switch to another supported algorithm. ¡ If not, If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. Reason 2: wrong public key 2. Check if the specified SSH user is configured with a public key using the display ssh user-information command: ¡ If not, configure it using the ssh user command. ¡ If yes, go to step 2. 3. Check if the configured public key matches the one specified on the client using the display public-key peer command: ¡ If not, import the specified public key to the device and configure it to the specified user using the ssh user command. ¡ If it matches, it may be due to mismatched public and private keys on the SSH client, regenerate the key pair on the SSH client. 4. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. Reason 3: wrong digital signature 5. Check the validity of the server's CA certificate and the client's local certificate. 6. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
SSHS_AUTH_TIMEOUT
|
Message text |
Authentication timed out for [IPADDR]. |
|
Variable fields |
$1: User IP. |
|
Severity level |
6 (Informational) |
|
Example |
SSHS/6/SSHS_AUTH_TIMEOUT: Authentication timed out for 1.1.1.1. |
|
Impact |
SSH user login authentication failed |
|
Cause |
SSH users did not complete authentication within the set authentication timeout period |
|
Recommended action |
Check if the SSH user authentication timeout is set too short by using the 'display ssh server status' command: · If it is not set too short, enter user information promptly to complete the authentication · If it is set too short, use the 'ssh server authentication-timeout' command to increase the authentication timeout |
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 (Informational) |
|
Example |
SSHS/6/SSHS_CONNECT: SSH user David (IP: 192.168.30.117) connected to the server successfully. |
|
Impact |
No negative impacts on the system. |
|
Cause |
SSH user successfully logged in to the server |
|
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 (Notification) |
|
Example |
SSHS/5/SSHS_DECRYPT_FAIL: The packet from 192.168.30.117 failed to be decrypted with aes256-cbc. |
|
Impact |
SSH user login failure or disconnection |
|
Cause |
Packet decryption failure from SSH client |
|
Recommended action |
Configure the SSH user to try logging in again. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Informational) |
|
Example |
SSHS/6/SSHS_DISCONNECT: SSH user David (IP: 192.168.30.117) disconnected from the server. |
|
Impact |
No negative impacts on the system. |
|
Cause |
SSH user exits the login |
|
Recommended action |
Check if the SSH client is unauthorized: · If yes, modify the ACL configuration to exclude the unauthorized client's IP address from the permit rules in the ACL, and update the user authentication configuration used by the client. · If not, 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 (Notification) |
|
Example |
SSHS/5/SSHS_ENCRYPT_FAIL: The packet to 192.168.30.117 failed to be encrypted with aes256-cbc. |
|
Impact |
SSH user login failure or disconnection |
|
Cause |
Message encryption failed to be sent to the SSH client |
|
Recommended action |
SSH user to re-login and try again, If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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: IP address of the SSH client. $2: Username. $3: Port number. |
|
Severity level |
6 (Informational) |
|
Example |
SSHS/6/SSHS_LOG: Authentication failed for David from 140.1.1.46 port 16266 because of invalid username or wrong password. |
|
Impact |
SSH users cannot log in to the SSH server |
|
Cause |
· Invalid SSH username · Incorrect SSH user login password |
|
Recommended action |
1. Check if the username meets the format requirements: ¡ If not, re-enter a username that meets the format requirements ¡ If it meets the requirements, go to step 2 2. Check if the login password is correct: ¡ If not, re-enter the correct password ¡ If correct, go to step 3 3. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Informational) |
|
Example |
SSHS/6/SSHS_MAC_ERROR: SSH server received a packet with wrong message authentication code (MAC) from 192.168.30.117. |
|
Impact |
SSH user login to fail or drop |
|
Cause |
SSH server side fails to verify the integrity of SSH client message |
|
Recommended action |
Configure the SSH users to log in again. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
SSHS_REACH_SESSION_LIMIT
|
Message text |
SSH client [STRING] failed to log in. The current number of [STRING] sessions is [NUMBER]. The maximum number allowed is ([NUMBER]). |
|
Variable fields |
$1: IP address of the SSH client. $2: SSH/Stelnet/SFTP/SCP/NETCONF $3: Total number of SSH sessions or various types of SSH sub-sessions (Stelnet/SFTP/SCP/NETCONF over SSH) $4: Total number of SSH sessions or various types of SSH sub-sessions allowed by the device (Stelnet/SFTP/SCP/NETCONF over SSH) |
|
Severity level |
6 (Informational) |
|
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). |
|
Impact |
SSH client login to server failed |
|
Cause |
SSH client login failed, maximum number of SSH sessions reached |
|
Recommended action |
1. Increase the upper limit by executing the aaa session-limit ssh command 2. If the maximum user connection limit is already configured to the maximum value, you can take offline idle clients to allow new SSH users to come online 3. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Informational) |
|
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. |
|
Impact |
SSH client login failed |
|
Cause |
Number of VTY users on SSH server has reached the upper limit of allowed users |
|
Recommended action |
Use the display users command to check for idle subscriber lines, then use the free line vty command to release idle VTY subscriber lines, allowing new SSH users to connect |
SSHS_SCP_OPER
|
Message text |
User [STRING] at [IPADDR] requested operation: [STRING]. |
|
Variable fields |
$1: Username. $2: User IP. $3: User request content, including file operation information · get file "name": Download a file named name · put file "name": Upload a file named name |
|
Severity level |
6 (Informational) |
|
Example |
SSHS/6/SSHS_SCP_OPER: -MDC=1; User user1 at 1.1.1.1 requested operation: put file "aa". |
|
Impact |
No negative impacts on the system. |
|
Cause |
SCP server receives SCP user request to execute related operations |
|
Recommended action |
No action is required. |
SSHS_SFTP_OPER
|
Message text |
User [STRING] at [IPADDR] requested operation: [STRING]. |
|
Variable fields |
$1: Username. $2: User IP. $3: User requests content, including file operations and directory operations · open dir "path": Open directory path · open "file" (attribute code code) in MODE mode: Open file file in MODE mode, with attribute code code · remove file "path": Delete file path · mkdir "path" (attribute code code): Create new directory path with attribute code code · rmdir "path": Delete directory path · rename old "old-name" to new "new-name": Change the name of old file or folder from old-name to new-name |
|
Severity level |
6 (Informational) |
|
Example |
SSHS/6/SSHS_SFTP_OPER: User user1 at 1.1.1.1 requested operation: open dir "flash:/". |
|
Impact |
No negative impacts on the system. |
|
Cause |
SFTP server receives SFTP user requests to perform related operations |
|
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. Options include Stelnet, SCP, SFTP, and NETCONF. |
|
Severity level |
6 (Informational) |
|
Example |
SSHS/6/SSHS_SRV_UNAVAILABLE: The SCP server is disabled or the SCP service type is not supported. |
|
Impact |
Server is disconnecting, SSH user login to SSH server failed |
|
Cause |
Stelnet/SCP/SFTP/NETCONF over SSH service is unavailable, the server is disconnecting from the service, or the class type is not supported |
|
Recommended action |
1. Check if the corresponding SSH class type is enabled: ¡ If not enabled, enable the corresponding service. ¡ If already enabled, go to step 2 2. Execute the ssh user command in the device system view to modify the SSH user's class type to match the client type |
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 (Informational) |
|
Example |
SSHS/6/SSHS_VERSION_MISMATCH: SSH client 192.168.30.117 failed to log in because of version mismatch. |
|
Impact |
No negative impacts on the system. |
|
Cause |
SSH client and server SSH version numbers do not match |
|
Recommended action |
1. Execute the 'display ssh server status' command on the device to check the SSH version field for confirmation of SSH version: ¡ If SSH version displays as 1.99, it means the device is compatible with SSH1 client, go to step 2 ¡ If SSH version displays as 2.0, execute the 'ssh server compatible-ssh1x enable' command on the device to enable compatibility with SSH1 client 2. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Warning) |
|
Example |
STM/4/STM_AUTO_UPDATE_FAILED: Slot 5 auto-update failed. Reason: Timeout when loading. |
|
Impact |
The device cannot join the IRF fabric. |
|
Cause |
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 |
To resolve the issue: 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 (Notification) |
|
Example |
STM/5/STM_AUTO_UPDATE_FINISHED: File loading finished on slot 3. |
|
Impact |
No negative impact on the system. |
|
Cause |
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 (Notification) |
|
Example |
STM/5/STM_AUTO_UPDATING: Don't reboot the slot 2. It is loading files. |
|
Impact |
No negative impact on the system. |
|
Cause |
Pattern 1: If the member device is loading a file, do not restart the device. Pattern 2: If the MPU is loading a file, do not restart the MPU. |
|
Recommended action |
No action is required. |
STM_LINK_DOWN
|
Message text |
IRF port [UINT32] went down. |
|
Variable fields |
$1: IRF port index. |
|
Severity level |
3 (Error) |
|
Example |
STM/3/STM_LINK_DOWN: IRF port 2 went down. |
|
Impact |
This issue causes IRF split. |
|
Cause |
All physical interfaces bound to an IRF port have been 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 information and configuration data, and then contact Technical Support for help. |
STM_LINK_TIMEOUT
|
Message text |
IRF port [UINT32] went down because the heartbeat timed out. |
|
Variable fields |
$1: IRF port index. |
|
Severity level |
2 (Critical) |
|
Example |
STM/2/STM_LINK_TIMEOUT: IRF port 1 went down because the heartbeat timed out. |
|
Impact |
This issue causes IRF split. |
|
Cause |
IRF heartbeat timed out. |
|
Recommended action |
Check the IRF links for link failures. For this purpose, 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 information and configuration data, and then contact Technical Support for help. |
STM_LINK_UP
|
Message text |
IRF port [UINT32] came up. |
|
Variable fields |
$1: IRF port index. |
|
Severity level |
6 (Informational) |
|
Example |
STM/6/STM_LINK_UP: IRF port 1 came up. |
|
Impact |
This issue causes IRF merge. |
|
Cause |
An IRF link recovered from failure. |
|
Recommended action |
No action is required. |
STM_MERGE
|
Message text |
IRF merge occurred. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
STM/4/STM_MERGE: IRF merge occurred. |
|
Impact |
No negative impact on the system. |
|
Cause |
An IRF link came up. |
|
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 (Warning) |
|
Example |
STM/4/STM_MERGE_NEED_REBOOT: IRF merge occurred. This IRF system needs a reboot. |
|
Impact |
The local IRF system cannot provide services during reboot. |
|
Cause |
An IRF link came up, which led to IRF merge. In addition, the local IRF system failed in the master election. |
|
Recommended action |
Reboot the local IRF system. After it reboots, all its member devices join the IRF system that has won the master election as subordinate devices. |
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 (Notification) |
|
Example |
STM/5/STM_MERGE_NOT_NEED_REBOOT: IRF merge occurred. This IRF system does not need to reboot. |
|
Impact |
No negative impact on the system. |
|
Cause |
An IRF link came up, which led to IRF merge. In addition, the local IRF system succeeded in the master election. |
|
Recommended action |
No action is required. |
STM_SAMEMAC
|
Message text |
Failed to stack because of the same bridge MAC addresses. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
STM/4/STM_SAMEMAC: Failed to stack because of the same bridge MAC addresses. |
|
Impact |
No negative impact on the system. |
|
Cause |
A new member device uses the same bridge MAC address as an existing member device. |
|
Recommended action |
A device is typically shipped with a bridge MAC address, which cannot be modified through command lines. To resolve the issue, collect alarm information and configuration data, and then contact Technical Support for help. |
STM_SOMER_CHECK
|
Message text |
Neighbor of IRF port [UINT32] cannot be stacked. |
|
Variable fields |
$1: IRF port index. |
|
Severity level |
3 (Error) |
|
Example |
STM/3/STM_SOMER_CHECK: Neighbor of IRF port 1 cannot be stacked. |
|
Impact |
No negative impact on the system. |
|
Cause |
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
This section contains STP messages.
STP_BPDU_PROTECTION
|
Message text |
BPDU-Protection port [STRING] received BPDUs. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
STP/4/STP_BPDU_PROTECTION: BPDU-Protection port GigabitEthernet1/0/1 received BPDUs. |
|
Impact |
The port is closed by the device |
|
Cause |
The interface with BPDU guard enabled receives BPDUs. |
|
Recommended action |
The closed port will be re-activated after a certain time interval. If the interface with BPDU guard function enabled is frequently closed due to receiving BPDU, check if the BPDU message on this port is from a malicious attack: · If yes, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. · If not, execute the stp port bpdu-protection disable command on the port to disable BPDU guard. |
STP_BPDU_RECEIVE_EXPIRY
|
Message text |
[STRING] [UINT32]'s port [STRING] received no BPDU within the rcvdInfoWhile interval. Information of the port aged out. |
|
Variable fields |
$1: STP instance or VLAN. $2: STP instance number or VLAN ID. $3: Interface name. |
|
Severity level |
5 (Notification) |
|
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. |
|
Impact |
Topology changes in the spanning tree network |
|
Cause |
The corresponding device on the port has not enabled the spanning tree function or there is a link fault with the device on the other end. |
|
Recommended action |
1. On the device connected through this port, execute the command 'display stp' to check if the spanning tree function is enabled: ¡ If yes, go to step 2 ¡ If no, enable the global and port spanning tree function on the device on the other end using the 'stp global enable' and 'stp enable' commands. If the device on the other end still cannot receive BPDU after enabling the spanning tree function, go to step 2 2. Check if there is a link fault between this device and the device on the other end: ¡ If yes, repair the link fault between the devices. If unable to locate the fault or repair the link fault, go to step 3 ¡ If no, go to step 3 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
STP_CONSISTENCY_RESTORATION
|
Message text |
Consistency restored on VLAN [UINT32]'s port [STRING]. |
|
Variable fields |
$1: VLAN ID $2: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
STP/6/STP_CONSISTENCY_RESTORATION: Consistency restored on VLAN 10's port GigabitEthernet1/0/1. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The PVID or port type at both ends of the link port becomes consistent |
|
Recommended action |
No action is required. |
STP_DETECTED_TC
|
Message text |
[STRING] [UINT32]'s port [STRING] detected a topology change. |
|
Variable fields |
$1: STP instance or VLAN. $2: STP instance number or VLAN ID. $3: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
STP/6/STP_DETECTED_TC: Instance 0's port GigabitEthernet1/0/1 detected a topology change. |
|
Impact |
Spanning Tree Topology changes, triggering a recalculation of the Spanning Tree Protocol |
|
Cause |
Port status changes on the device |
|
Recommended action |
Check if the topology change is normal: · If yes, no action is required. · If not, troubleshoot the related issues, and recover the spanning tree topology. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
STP_DISABLE
|
Message text |
STP is now disabled on the device. |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
STP/6/STP_DISABLE: STP is now disabled on the device. |
|
Impact |
Devices are unable to use the Spanning Tree Protocol (STP) function and cannot process or send BPDUs. |
|
Cause |
The spanning tree protocol is disabled globally on the device by using the undo stp global enable command. |
|
Recommended action |
No action is required. |
STP_DISCARDING
|
Message text |
[STRING] [UINT32]'s port [STRING] has been set to discarding state. |
|
Variable fields |
$1: STP instance or VLAN. $2: STP instance number or VLAN ID. $3: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
STP/6/STP_DISCARDING: Instance 0's port GigabitEthernet1/0/1 has been set to discarding state. |
|
Impact |
This port cannot forward user traffic |
|
Cause |
The spanning tree topology of the port in the MSTP instance has changed. |
|
Recommended action |
1. Check if there have been changes in the devices or links in the network topology: ¡ If yes, go to step 2 ¡ If no, go to step 3 2. Check if the changes in the devices or links in the network topology are in line with the requirements: ¡ If yes, go to step 3 ¡ If no, proceed to step 4 3. Execute the command 'display stp' to check if the current status calculation results of each port are in line with the requirements: ¡ If yes, no action is required. ¡ If no, go to step 4 4. Deploy the network topology correctly. If the issue persists after deploying the network topology correctly, go to step 5 5. Collect alarm information, log messages, and configuration data, and then contact Technical Support. |
STP_DISPUTE_RESTORATION
|
Message text |
[STRING] [UINT32]'s port [STRING] exited the dispute state. |
|
Variable fields |
$1: STP instance or VLAN. $2: STP instance number or VLAN ID. $3: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
STP/6/STP_DISPUTE_RESTORATION: Instance 0's port GigabitEthernet1/0/2 exited the dispute state. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The port recovers and it receives a normal priority BPDU, or the user manually executes the undo stp dispute-protection command to disable the Dispute protection function. |
|
Recommended action |
No action is required. |
STP_EDGEPORT_INACTIVE
|
Message text |
Port [STRING] became a non-edge port after receiving a BPDU. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
STP/4/STP_EDGEPORT_INACTIVE: Port GigabitEthernet1/0/1 became a non-edge port after receiving a BPDU. |
|
Impact |
A change occurred in the spanning tree network topology |
|
Cause |
The edge port received a BPDU message. |
|
Recommended action |
1. Determine if the port should be planned as an edge port: ¡ If yes, go to step 2 ¡ If no, go to step 3 2. Determine if the BPDU message received on this port is from a malicious attack: ¡ If yes, go to step 4 ¡ If no, go to step 3 3. On this port, execute the 'undo stp edged-port' command to configure the port as a non-edge port 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support. |
STP_ENABLE
|
Message text |
STP is now enabled on the device. |
|
Variable fields |
No |
|
Severity level |
6 (Informational) |
|
Example |
STP/6/STP_ENABLE: STP is now enabled on the device. |
|
Impact |
Some ports may be blocked due to the calculation results of the Spanning Tree Protocol (STP) |
|
Cause |
On the device, the global enable command for STP has been executed to enable the global Spanning Tree Protocol |
|
Recommended action |
No action is required. |
STP_FORWARDING
|
Message text |
[STRING] [UINT32]'s port [STRING] has been set to forwarding state. |
|
Variable fields |
$1: STP instance or VLAN. $2: STP instance number or VLAN ID. $3: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
STP/6/STP_FORWARDING: Instance 0's port GigabitEthernet1/0/1 has been set to forwarding state. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The network topology changes |
|
Recommended action |
1. Execute the display stp command to check if the current status calculation results of each port meet the requirements: ¡ If yes, then no action is required. ¡ If no, go to step 2. 2. Correctly deploy the network topology. If the issue persists after correct deployment, go to step 3. 3. Collect the configuration file, log file, and alarms, and then contact Technical Support. |
STP_LOOP_PROTECTION
|
Message text |
[STRING] [UINT32]'s LOOP-Protection port [STRING] failed to receive configuration BPDUs. |
|
Variable fields |
$1: STP instance or VLAN. $2: STP instance number or VLAN ID. $3: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
STP/4/STP_LOOP_PROTECTION: Instance 0's LOOP-Protection port GigabitEthernet1/0/1 failed to receive configuration BPDUs. |
|
Impact |
Ports with loop protection enabled will remain in Discarding state until receiving BPDU |
|
Cause |
Reason 1: Spanning tree function is not enabled on the opposite device of the port with loop protection enabled Reason 2: Link fault occurred on the port with loop protection enabled |
|
Recommended action |
1. Execute the display stp command on the opposite device connected to this port to check if the spanning tree function is enabled on that device: ¡ If yes, go to step 2 ¡ If not, enable the global and port spanning tree functions on the opposite device with the stp global enable and stp enable commands. If the opposite device enables the spanning tree function and this end still cannot receive BPDU, go to step 2 2. Check if there is a link fault between this device and the opposite device: ¡ If yes, repair the link fault between the devices. If the cause of the fault cannot be located or the link fault cannot be repaired, go to step 3 ¡ If not, execute step 3 3. If the issue persists, collect the configuration file, log file, and alarms, and then contact Technical Support. |
STP_NOT_ROOT
|
Message text |
The current switch is no longer the root of instance [UINT32]. |
|
Variable fields |
$1: STP instance number. |
|
Severity level |
5 (Notification) |
|
Example |
STP/5/STP_NOT_ROOT: The current switch is no longer the root of instance 0. |
|
Impact |
Device roles are recalculated, which may cause a brief disruption to the business. |
|
Cause |
Possible reasons include: · A device with a smaller root bridge ID has been added to the spanning tree network topology · A device's priority in the original spanning tree network topology has been modified |
|
Recommended action |
For a device with a smaller root bridge ID added to the spanning tree network topology: 1. On the newly added device, execute the 'display stp root' command to check if the device's root bridge ID is the smallest: ¡ If yes, go to step 2 ¡ If no, go to step 4 2. confirm whether the root bridge ID of the newly added device should be planned as the smallest root bridge ID: ¡ If yes, then no action is required. ¡ If no, go to step 3 3. modify the priority and other configurations of the newly added device to change the root bridge role to the device planned by the user. If the issue persists, go to step 4 4. Collect the configuration file, log file, and alarms, and then contact Technical Support. For devices with modified priorities in the original spanning tree network topology: 5. Execute the 'display stp' command to check if the device priority modification configuration in the spanning tree network topology is normal: ¡ If yes, then no action is required. ¡ If no, go to step 2 6. Execute the 'stp priority' command to modify the priority of each device to the value planned by the user. If the issue persists, go to step 3 7. Collect the configuration file, log file, and alarms, and then contact Technical Support. |
STP_NOTIFIED_TC
|
Message text |
[STRING] [UINT32]'s port [STRING] was notified a topology change. |
|
Variable fields |
$1: STP instance or VLAN. $2: STP instance number or VLAN ID. $3: Interface name. |
|
Severity level |
6 (Informational) |
|
Example |
STP/6/STP_NOTIFIED_TC: Instance 0's port GigabitEthernet1/0/1 was notified a topology change. |
|
Impact |
Spanning Tree topology changes, triggering re-calculation of the Spanning Tree Protocol |
|
Cause |
Device receives a BPDU with the TC flag set |
|
Recommended action |
Check if the topology change is normal: · If yes, no action is required. · If not, troubleshoot the related faults and recover the Spanning Tree topology. If unable to troubleshoot, collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Warning) |
|
Example |
STP/4/STP_PORT_TYPE_INCONSISTENCY: Access port GigabitEthernet1/0/1 in VLAN 10 received PVST BPDUs from a trunk or hybrid port. |
|
Impact |
Due to the difference in BPDU format sent by Access ports and Trunk as well as Hybrid ports, it may cause errors in the Spanning Tree Protocol calculation |
|
Cause |
Access ports received PVST format BPDUs sent by Trunk or Hybrid ports |
|
Recommended action |
1. Check if the type of the port specified in the log is consistent with its peer port: ¡ If yes, go to step 2 ¡ If no, change the port types on both ends to the same type. If the issue persists, go to step 2 2. Collect the configuration file, log file, and alarms, and then contact Technical Support. |
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 (Warning) |
|
Example |
STP/4/STP_PVID_INCONSISTENCY: Port GigabitEthernet1/0/1 with PVID 10 received PVST BPDUs from a port with PVID 20. |
|
Impact |
PVST calculation may have errors |
|
Cause |
This end port does not match the remote port's PVID |
|
Recommended action |
determine if the inconsistency of PVIDs on both ends of the port complies with the network planning requirements: · If yes, execute the 'stp ignore-pvid-inconsistency' command to disable PVST's PVID inconsistency protection function · If not, modify the PVIDs on both ends of the port to match |
STP_PVST_BPDU_PROTECTION
|
Message text |
PVST BPDUs were received on port [STRING], which is enabled with PVST BPDU guard. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
STP/4/STP_PVST_BPDU_PROTECTION: PVST BPDUs were received on port GigabitEthernet1/0/1, which is enabled with PVST BPDU guard. |
|
Impact |
The port receiving the PVST message was closed. |
|
Cause |
In MSTP mode, the port with PVST message protection function enabled received a PVST message. |
|
Recommended action |
1. Determine if the device publishing the PVST message needs to do so: ¡ If yes, No action is required. ¡ If no, modify the configuration on the device to stop publishing PVST messages. If the issue persists, go to step 2 2. Collect the configuration file, log file, and alarms, and then contact Technical Support. |
STP_ROOT_PROTECTION
|
Message text |
[STRING] [UINT32]'s ROOT-Protection port [STRING] received superior BPDUs. |
|
Variable fields |
$1: STP instance or VLAN. $2: STP instance number or VLAN ID. $3: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
STP/4/STP_ROOT_PROTECTION: Instance 0's ROOT-Protection port Ethernet1/0/2 received superior BPDUs. |
|
Impact |
The port that receives a BPDU with a higher precedence will transition to the listening state and stop forwarding user messages. If no better BPDU is received within twice the Forward Delay time, the port will recover to its original normal state. |
|
Cause |
A new device has been added to the spanning tree network topology, or an existing device has undergone a precedence change. |
|
Recommended action |
1. Execute the 'display stp' command on other devices in the spanning tree network to check the current root bridge calculation results and port calculation results to see if they comply with the network plan: ¡ If yes, go to step 2 ¡ If no, go to step 3 2. Execute the 'undo stp root-protection' command on the port with root protection enabled to disable the root protection function on that port. If the issue persists, go to step 4 3. Reconfigure the precedence of devices in the network as needed to make the device with root protection enabled the root bridge device. If the issue persists, go to step 4 4. Collect the configuration file, log file, and alarms, and then contact Technical Support. |
STP_STG_NUM_DETECTION
|
Message text |
STG count [UINT32] is smaller than the MPU's STG count [UINT32]. |
|
Variable fields |
$1: Number of specified board STG $2: Number of MPU STG |
|
Severity level |
4 (Warning) |
|
Example |
STP/4/STP_STG_NUM_DETECTION: STG count 64 is smaller than the MPU's STG count 65. |
|
Impact |
Spanning Tree Protocol cannot run normally |
|
Cause |
Detected that the number of STG on the specified board is less than the number of STG on the MPU |
|
Recommended action |
The number of STP instances configured on the MPU cannot exceed the minimum number of STG on all boards. For example: If the number of STP instances configured is m, and the minimum number of STG on any board is n, then m cannot be greater 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 (Warning) |
|
Example |
STRUNK/4/STRUNK_DROPPACKET_INCONSISTENCY: Smart trunk 10 dropped the S-Trunk protocol packet because key verification failed. |
|
Impact |
The smart trunk failed to be created. |
|
Cause |
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 (Notification) |
|
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). |
|
Impact |
The service traffic might be dropped. |
|
Cause |
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 |
4 (Warning) |
|
Example |
STRUNK/5/STRUNK_PDUINTERVAL_MISMATCH: Smart trunk 1 has a packet transmission interval different than the peer device. |
|
Impact |
The smart trunk failed to be created. |
|
Cause |
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 (Warning) |
|
Example |
STRUNK/4/STRUNK_RECEIVE_TIMEOUT: Hello timeout timer expired on smart trunk 1. |
|
Impact |
The smart trunk failed to be created due to the negotiation failure. |
|
Cause |
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 (Notification) |
|
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) |
|
Impact |
The service traffic might be dropped. |
|
Cause |
The smart trunk role changed. |
|
Recommended action |
Verify that the link between the devices in the smart trunk is Layer 3 reachable. |
SWFA
This section contains SWFA messages.
UNKNOWN
|
Message text |
Congestion is detected on an interface of chip [UINT32] in slot [UINT32]. |
|
Variable fields |
$1: Chip number. $2: Slot number of the card. |
|
Severity level |
3 (Error) |
|
Example |
SWFA/3/UNKNOWN: -MDC=1-Slot=10; Congestion is detected on an interface of chip 0 in slot 16. |
|
Impact |
Packet drop or erroneous packets are detected on the device. |
|
Explanation |
· The service module and the switching fabric module were not installed correctly. · An error occurred on the link between the service module and the switching fabric module. · A chip error occurred inside the service module or the switching fabric module. |
|
Recommended action |
1. Verify that the specified card is installed correctly. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Seu error detected on slot [UINT32] |
|
Variable fields |
$1: Slot number of the card. |
|
Severity level |
3 (Error) |
|
Example |
SWFA/3/UNKNOWN: -Slot=2; Seu error detected on slot 2 |
|
Impact |
The card cannot operate correctly. |
|
Explanation |
A chip error occurred on the card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SYSEVENT
This section contains system event messages.
EVENT_TIMEOUT
|
Message text |
Module [UINT32]'s processing for event [UINT32] timed out. Module [UINT32]'s processing for event [UINT32] on [STRING] timed out. |
|
Variable fields |
$1: Module ID. $2: Event ID. $3: MDC MDC-ID or Context Context-ID. |
|
Severity level |
6 (Informational) |
|
Example |
SYSEVENT/6/EVENT_TIMEOUT: -MDC=1; Module 0x1140000's processing for event 0x20000010 timed out. SYSEVENT/6/EVENT_TIMEOUT: -Context=1; Module 0x33c0000's processing for event 0x20000010 on context 16 timed out. |
|
Impact |
Evaluate the impact on the system as required. |
|
Cause |
A module's processing for an event timed out on an MDC or context. Logs generated on non-default MDCs or contexts do not include the MDC MDC-ID or Context Context-ID. Logs generated on the default MDC or context include the following types: · Logs of the default MDC or context, which do not include the MDC MDC-ID or Context Context-ID. · Logs of non-default MDCs or contexts, which include their MDC MDC-ID or Context Context-ID. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
SYSLOG
This section contains syslog messages.
SYSLOG_FILE_DECOMPRESS_ERROR
|
Message text |
Failed to decompress [STRING]. |
|
Variable fields |
$1: Name and path of the log file to be compressed. |
|
Severity level |
4 (Warning) |
|
Example |
SYSLOG/4/SYSLOG_FILE_DECOMPRESS_ERROR: Failed to decompress flash:/logfile/logfile1.log.gz. |
|
Impact |
No negative impact on the system. |
|
Cause |
Insufficient storage media space. |
|
Recommended action |
1. In user view, use the dir command to identify whether the storage media space is insufficient. If it is, use the delete /unreserved command to delete some unused files. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact H3C Support for help. |
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 (Warning) |
|
Example |
SYSLOG/4/SYSLOG_LOGBUFFER_FAILURE: Log cannot be sent to the logbuffer because of communication timeout between syslog and DBM processes. |
|
Impact |
The log buffer is unable to store logs. |
|
Cause |
The communication timed out between syslog and DBM processes. |
|
Recommended action |
Collect the device configuration file, log information, and alarm information, and contact Technical Support. |
SYSLOG_LOGFILE_FULL
|
Message text |
Log file space is full. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
SYSLOG/4/SYSLOG_LOGFILE_FULL: Log file space is full. |
|
Impact |
New logs cannot be stored to the log file. |
|
Cause |
The log file is full. |
|
Recommended action |
1. Back up the log file, and delete the log file. 2. Execute the undo info-center logfile overwrite-protection command to disable the log file overwrite protection feature. With this feature disabled, when the log file is full, new logs can overwrite existing logs and be saved to the log file. 3. Execute the info-center logfile size-quota command to modify the maximum storage space that a single log file can occupy. |
SYSLOG_RESTART
|
Message text |
System restarted -- [STRING] [STRING] Software. |
|
Variable fields |
$1: Company name. $2: Software name. |
|
Severity level |
6 (Informational) |
|
Example |
SYSLOG/6/SYSLOG_RESTART: System restarted -- H3C Comware Software |
|
Impact |
The system restarts and the device cannot operate correctly. |
|
Cause |
The device is restarted. |
|
Recommended action |
No action is required. |
SYSLOG_RELAY_PORT_FAILED
|
Message text |
Failed to configure port [USHORT] as a syslog relay port. |
|
Variable fields |
$1: Listening port for the CTRL-VM log relay feature. |
|
Severity level |
5 (Notification) |
|
Example |
SYSLOG/5/SYSLOG_RELAY_PORT_FAILED: Failed to configure port 2000 as a syslog relay port. |
|
Impact |
The CTRL-VM log relay feature cannot run correctly. |
|
Cause |
The listening port for the CTRL-VM log relay feature might be used by other service modules. |
|
Recommended action |
1. Execute the display tcp and display udp commands to check for the IPv4 address and port number used by the local end in the Local Addr:port field in the output. 2. Execute the display ipv6 tcp and display ipv6 udp commands to check for the IPv6 address and port number used by the local end in the Laddr->port field in the output. 3. Use the info-center loghost relay port command to configure an unused port number as the listening port for the CTRL-VM log relay feature. |
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 (Notification) |
|
Example |
SYSLOG/5/SYSLOG_RTM_EVENT_BUFFER_FULL: In the last minute, 100 syslog logs were not monitored because the buffer was full. |
|
Impact |
This issue might affect the execution of EAA monitoring policies. |
|
Cause |
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 |
1. Execute the display logbuffer command to locate a large number of logs generated in a short time, identify the service module generating the logs, and determine based on the log information whether the service module's function is abnormal or under attack. First address the issues with the service module's abnormalities or attacks to reduce the generation of logs. 2. Execute the rtm event syslog buffer-size command to increase the log buffer size. |
SYSM messages
This section contains system management messages.
DrvDebug
|
Message text |
The board [INT32] is not steady! |
|
Variable fields |
$1: Slot number of the interface module. |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: The board 2 is not steady! |
|
Impact |
The interface module cannot operate correctly. |
|
Cause |
The interface module was not correctly installed or there might be hardware failures. |
|
Recommended action |
1. Verify the interface module installation. 2. Use the display device command to identify whether the interface module is in position. 3. Install the module in another slot if the interface module information is not displayed. 4. Use the display device command to identify whether the interface module is in position. 5. If the interface module is in position, the slot might be damaged, and contact Technical Support. 6. If the interface module is not in position, the interface module might be damaged, and contact Technical Support for help. |
|
Message text |
Warning: Overtemperature condition is detected on power module [INT32] Please check it. |
|
Variable fields |
$1: Power module ID. |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: Warning: Overtemperature condition is detected on power module 2. Please check it. |
|
Impact |
Overtemperature might cause device failure. |
|
Cause |
A power module was in an overtemperature condition. |
|
Recommended action |
1. Verify that the ventilation system in the equipment room is operating correctly. 2. Verify that the air outlet vents are not blocked. 3. Verify that the fan trays are operating correctly and air can exhaust from the air outlet vents. 4. Verify that cards or filler panels are correctly installed. 5. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Warning: Fan of power module [INT32] fails to operate. Please check it. |
|
Variable fields |
$1: Power module ID. |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: Warning: Fan of power module 2 fails to operate. Please check it. |
|
Impact |
The power module cannot correctly supply power. |
|
Cause |
Power module fan failure. |
|
Recommended action |
1. Replace the power module with a new power model. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Power Error, there is no input in Power 1. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug:Power Error, there is no input in Power 1 |
|
Impact |
The power module cannot correctly supply power. |
|
Cause |
The power module had no power input. |
|
Recommended action |
1. Verify the power cord installation. ¡ If the power cord is loose, reinstall it. ¡ If the power cord is damaged, replace the power cord. 2. Verify that the power module makes good contact with the backplane. 3. Verify that the power source is providing power correctly and the voltage is in the acceptable range. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Power Error, there is no input in Power 2. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug:Power Error, there is no input in Power 2 |
|
Impact |
The power module cannot correctly supply power. |
|
Cause |
The power module had no power input. |
|
Recommended action |
1. Verify the power cord installation. ¡ If the power cord is loose, reinstall it. ¡ If the power cord is damaged, replace the power cord. 2. Verify that the power module makes good contact with the backplane. 3. Verify that the power source is providing power correctly and the voltage is in the acceptable range. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Frame [INT32] fan [STRING] state error! |
|
Variable fields |
$1: ID of a fan tray. $2: ID of a fan. |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: Frame 1 fan 2 state error! |
|
Impact |
The temperature of the device might be abnormal. |
|
Cause |
A state error occurred on a fan. The possible reason might be communication error between the fan and the active MPU. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
The airflow directions for the two fan trays must be the same. Please check it. |
|
Variable fields |
N/A |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: The airflow directions for the two fan trays must be the same. Please check it. |
|
Impact |
The temperature of the device might be abnormal. |
|
Cause |
The system prints this log and then automatically performs the following tasks when it detects both a fan tray that draws cooling air and a fan tray that exhausts warm air: · Enables the fan tray that draws cooling air to operate at full speed. · Enables the fan tray that exhausts warm air to operate at the lowest speed. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Warning: Fan [INT32] is absent! |
|
Variable fields |
$1: ID of a fan tray. |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: Warning: Fan 2 is absent! |
|
Impact |
The temperature of the device might be abnormal. |
|
Cause |
The system detected no fan tray in the specified slot. |
|
Recommended action |
1. Install a fan tray. 2. Examine the fan tray LED on the MPU. If the LED is steady on, the fan tray is securely installed in the slot. 3. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
The device does not support board in slot [INT32] ,type is unknown(0x[STRING]), Please check. |
|
Variable fields |
$1: Slot ID of a card. $2: Type of the card. |
|
Severity level |
5 (Notification) |
|
Example |
DRVPLAT/5/DrvDebug: The device does not support board in slot3 ,type is unknown(0x80), Please check. |
|
Impact |
The card cannot operate correctly. |
|
Cause |
The device does not support the card. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
|
Message text |
Power modules in power frame [UINT32] are of different models. |
|
Variable fields |
$1: Power frame ID. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Power modules in power frame 1 are of different models. |
|
Impact |
The power modules might fail to supply power to the device. As a result, cards cannot operate correctly. |
|
Cause |
The power modules in the specified power frame are not of the same model. |
|
Recommended action |
Replace power modules in the specified power frame so all the power modules are of the same model. |
|
Message text |
Only one power module is installed in power frame [UINT32]. |
|
Variable fields |
$1: Power frame ID. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Only one power module is installed in power frame 1. |
|
Impact |
The power module might fail to supply power to the device. As a result, cards cannot operate correctly. |
|
Cause |
Only one power module is installed in the specified power frame. |
|
Recommended action |
Install a second power module in the specified power frame. |
|
Message text |
Power modules in power frames [UINT32] and [UINT32] are of different models. |
|
Variable fields |
$1: Power frame ID. $2: Power frame ID. |
|
Severity level |
2 (Critical) |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Power modules in power frames 1 and 2 are of different models. |
|
Impact |
The power modules might fail to supply power to the device. As a result, cards cannot operate correctly. |
|
Cause |
The power modules in the specified power frames are not of the same model. |
|
Recommended action |
Replace power modules so the power modules in the power frames are of the same model. |
SUBCARD_INSTALL_FAULT
|
Message text |
The subcard in subslot [INT32] is not installed correctly. Please remove the subcard and install it again. |
|
Variable fields |
$1: Subslot ID of a subcard. |
|
Severity level |
1 (Alert) |
|
Example |
PORT/1/SUBCARD_INSTALL_FAULT: -MDC=1-Slot=7; The subcard in subslot 1 is not installed correctly. Please remove the subcard and install it again. |
|
Impact |
The subcard cannot operate correctly, which affects services. |
|
Cause |
The specified subcard was not securely installed. |
|
Recommended action |
1. Remove the subcard and securely install the subcard. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
SUBCARD_MISMATCH_PREV
|
Message text |
The type of current board is [STRING]. It doesn't match with the previous board [STRING] in Slot [INT32]. |
|
Variable fields |
$1: Model of the new interface module. $2: Model of the replaced interface module. $3: Slot number of the interface module. |
|
Severity level |
2 (Critical) |
|
Example |
DSYSM/2/SUBCARD_MISMATCH_PREV: The type of current board is MIC-PSP4L. It doesn't match with the previous board MIC-CLP4L in Slot 6. |
|
Impact |
Services on the interface module might be affected. |
|
Cause |
An interface module was replaced with a module of a different model. |
|
Recommended action |
Do replace a correctly operating interface module with an interface module of a different model. |
SUBCARD_NOTSPT_SLOT
|
Message text |
The board is not supported in slot [INT32]. |
|
Variable fields |
$1: Slot number of the interface module. |
|
Severity level |
2 (Critical) |
|
Example |
DSYSM/2/SUBCARD_NOTSPT_SLOT: -MDC=1-Slot=2; The board is not supported in slot 2. |
|
Impact |
Services on the interface module might be affected. |
|
Cause |
The slot does not support the interface module. |
|
Recommended action |
Replace the interface module with a supported one, or insert the interface module into a slot that supports the module. |
|
Message text |
The [STRING] interface module is not supported in slot [INT32]. It can be installed in the following slots: [INT32]. |
|
Variable fields |
$1: Interface module name. $2: Slot number of the interface module. $3: List of slots supported by the interface module. |
|
Severity level |
2 (Critical) |
|
Example |
DSYSM/2/SUBCARD_NOTSPT_SLOT: -MDC=1-Slot=18; The MIC-XP10L-M interface module is not supported in slot 2. It can be installed in the following slots: 6 7 8 9 10 11 12 13. |
|
Impact |
Services on the interface module might be affected. |
|
Cause |
This message is sent when an interface module is installed in a slot not supported by the interface module. |
|
Recommended action |
Install the interface module in a slot supported by the interface module. |
GET_FPGAFILE_FAILED
|
Message text |
Get fpga file([STRING]) failed! |
|
Variable fields |
$1: FPGA file name. |
|
Severity level |
3 (Error) |
|
Example |
SYSM/3/GET_FPGAFILE_FAILED:Get fpga file(NPS_1812X_E.bin) failed! |
|
Impact |
Cards cannot start up correctly. |
|
Cause |
The system failed to obtain the FPGA file of a card. The card might fail to start. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
LOAD_FPGAFILE_FAILED
|
Message text |
Download fpga file([STRING])failed! |
|
Variable fields |
$1: FPGA file name. |
|
Severity level |
3 (Error) |
|
Example |
SYSM/3/LOAD_FPGAFILE_FAILED: Downloadfpga file(NPS_1812X_E.bin) failed! |
|
Impact |
Cards cannot start up correctly. |
|
Cause |
The system failed to download the FPGA file of a card. The card might fail to start. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
INNERLINK_EXCEPTION
|
Message text |
An exception has occured on an internal link. |
|
Variable fields |
N/A |
|
Severity level |
3 (Error) |
|
Example |
SYSM/3/INNERLINK_EXCEPTION：An exception has occured on an internal link. |
|
Impact |
The issue affects the normal operation of the device. |
|
Cause |
Hardware failure, resulting in a large number of error packets on the internal link. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
Introduction
This document includes all system messages for H3C Comware V7 software. It is intended for system administrators who are responsible for managing Comware V7 systems.
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 the following RFC 3164-compliant format:
<PRI>TIMESTAMP HOSTNAME %%vendorMODULE/ severity /MNEMONIC: location; CONTENT
Table 15 System log message elements
|
Element |
Description |
|
<PRI> |
Priority identifier. 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 11. Different log hosts might present the priority identifier element in different formats. |
|
TIMESTAMP |
Date and time when the event occurred. You can use the info-center timestamp loghost command to specify the format. |
|
HOSTNAME |
Device name. |
|
%%vendor |
Manufacturer flag. This element is %%10 for H3C. |
|
MODULE |
Name of the module that produced the message. |
|
severity |
Severity level of the message. (For more information about severity levels, see Table 11.) |
|
MNEMONIC |
Text string that uniquely identifies the system message. |
|
location |
Optional. This element presents location information for the message in the following format: -attribute1=x-attribute2=y…-attributeN=z 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 12. 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.
Table 16 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 |
Notice |
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 |
Debugging |
Debugging message. |
For variable fields in the message text, this document uses the representations in Table 12. The values are case insensitive, even though the representations are uppercase letters.
Table 17 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. |
Software module list
Table 13 lists all software modules that might produce system log messages.
|
Module name representation |
Module name expansion |
|
AAA |
Authentication, Authorization and Accounting |
|
ACL |
Access Control List |
|
AFT |
Address Family Translation |
|
ANCP |
Access Node Control Protocol |
|
APMGR |
Access Point Management |
|
ARP |
Address Resolution Protocol |
|
ATK |
ATK Detect and Defense |
|
ATM |
Asynchronous Transfer Mode |
|
BFD |
Bidirectional Forwarding Detection |
|
BGP |
Border Gateway Protocol |
|
BIER |
Bit Index Explicit Replication |
|
BLS |
Blacklist |
|
CFD |
Connectivity Fault Detection |
|
CFGMAN |
Configuration Management |
|
CLKM |
Clock Monitoring |
|
CONNLMT |
Connect Limit |
|
CPDR |
Control Plane Disaster Recovery |
|
CUSP |
Control-/User-plane Separation Protocol |
|
DEV |
Device Management |
|
DHCP |
Dynamic Host Configuration Protocol |
|
DHCPR |
IPv4 DHCP Relay |
|
DHCPR6 |
IPv6 DHCP Relay |
|
DHCPS |
IPv4 DHCP Server |
|
DHCPS6 |
IPv6 DHCP Server |
|
DHCPSP4 |
IPv4 DHCP snooping |
|
DHCPSP6 |
IPv6 DHCP snooping |
|
DIAG |
Diagnosis |
|
DLDP |
Device Link Detection Protocol |
|
DOMAIN |
DOMAIN |
|
DOT1X (Layer 2) |
802.1X |
|
DOT1X (Layer 3) |
802.1X |
|
EDEV |
Extender Device Management |
|
EIGRP |
Enhanced Interior Gateway Routing Protocol |
|
EM |
Ear & Mouth or rEceive & transMit |
|
ERPS |
Ethernet Ring Protection Switching |
|
ETH |
Ethernet |
|
ETHOAM |
Ethernet Operation, Administration and Maintenance |
|
EVB |
Ethernet Virtual Bridging |
|
EVIISIS |
Ethernet Virtual Interconnect Intermediate System-to-Intermediate System |
|
FCLINK |
Fibre Channel Link |
|
FCOE |
Fibre Channel Over Ethernet |
|
FCZONE |
Fibre Channel Zone |
|
FIB |
Forwarding Information Base |
|
FILTER |
Filter |
|
FIPSNG |
FIP Snooping |
|
FTP |
File Transfer Protocol |
|
gRPC |
Google Remote Procedure Call |
|
HA |
High Availability |
|
HQOS |
Hierarchical QoS |
|
HTTPD |
Hypertext Transfer Protocol Daemon |
|
iFIT |
in-situ Flow Information Telemetry |
|
IFMON |
Interface Monitor |
|
IFNET |
Interface Net Management |
|
IGMP |
Internet Group Management Protocol |
|
IKE |
Internet Key Exchange |
|
iNQA |
Intelligent Network Quality Analyzer |
|
INTRACE |
INTRACE |
|
IP6ADDR |
IPv6 address |
|
IP6FW |
IPv6 Forwarding |
|
IPADDR |
IP address |
|
IPFW |
IP Forwarding |
|
IPOE |
IP Over Ethernet |
|
IPSEC |
IP Security |
|
IPSG |
IP Source Guard |
|
IRDP |
ICMP Router Discovery Protocol |
|
IRF |
Intelligent Resilient Framework |
|
ISIS |
Intermediate System-to-Intermediate System |
|
ISSU |
In-Service Software Upgrade |
|
KHTTP |
Kernel Hypertext Transfer Protocol |
|
L2PT |
Layer 2 Protocol Tunneling |
|
L2TPV2 |
Layer 2 Tunneling Protocol Version 2 |
|
L2VPN |
Layer 2 VPN |
|
L3VPN |
Layer 3 VPN |
|
LAGG |
Link Aggregation |
|
LB |
Load Balance |
|
LDP |
Label Distribution Protocol |
|
LIPC |
Leopard Inter-process Communication |
|
LIC |
License |
|
LLDP |
Link Layer Discovery Protocol |
|
LOAD |
Load Management |
|
LOCAL |
Local |
|
LOGIN |
Login |
|
LPDT |
Loopback Detection |
|
LS |
Local Server |
|
LSM |
Label Switch Management |
|
LSPV |
LSP Verification |
|
MAC |
Media Access Control |
|
MACA |
MAC Authentication |
|
MACSEC |
MAC Security |
|
MBFD |
MPLS BFD |
|
MBUF |
Memory Buffer |
|
MDC |
Multitenant Device Context |
|
MFIB |
Multicast Forwarding Information Base |
|
MGROUP |
Mirroring group |
|
MPLS |
Multiprotocol Label Switching |
|
MSC |
Media Stream Control |
|
MSDP |
Multicast Source Discovery Protocol |
|
MTLK |
Monitor Link |
|
MTP |
Maintain Probe |
|
NAT |
Network Address Translate |
|
NCM |
Netconf Client Management |
|
ND |
Neighbor Discovery |
|
NETCONF |
Network Configuration Protocol |
|
NETSLICE |
SRv6 Network Slicing |
|
NQA |
Network Quality Analyzer |
|
NTP |
Network Time Protocol |
|
OAM |
VM internal link OAM |
|
OBJP |
Object Policy |
|
OFP |
OpenFlow Protocol |
|
OPENSRC(DB-VM) |
Open Source(Database virtual machine) |
|
OPENSRC(RSYNC) |
Open Source(Remote Synchronize) |
|
OPTMOD |
Optical Module |
|
OSPF |
Open Shortest Path First |
|
OSPFV3 |
Open Shortest Path First Version 3 |
|
PathMTU |
VM Path MTU |
|
PBB |
Provider Backbone Bridge |
|
PBR |
Policy Based Route |
|
PCE |
Path Computation Element |
|
PEX |
Port Extender |
|
PFILTER |
Packet Filter |
|
PIM |
Protocol Independent Multicast |
|
PING |
Packet Internet Groper |
|
PKG |
Package management |
|
PKI |
Public Key Infrastructure |
|
PKT2CPU |
Packet to CPU |
|
PKTCPT |
Packet Capture |
|
PORTAL |
Portal |
|
PORTSEC |
Port Security |
|
PPP |
Point to Point Protocol |
|
PTP |
Precision Time Protocol |
|
PWDCTL |
Password Control |
|
QOS |
Quality of Service |
|
RADIUS |
Remote Authentication Dial In User Service |
|
RDDC |
Redundancy |
|
RESMON |
RESOURCE MONITER |
|
RIP |
Routing Information Protocol |
|
RIPNG |
Routing Information Protocol Next Generation |
|
RM |
Routing Management |
|
RPR |
Resilient Packet Ring |
|
RMDB |
Remote Database |
|
RRPP |
Rapid Ring Protect Protocol |
|
RSVP |
Resource Reservation Protocol |
|
RTM |
Real-Time Management |
|
SAVA |
Source Address Validation Architecture |
|
SCMD |
Service Control Manager |
|
SCRLSP |
Static CRLSP |
|
SESSION |
Session |
|
SFLOW |
Sampler Flow |
|
SHELL |
Shell |
|
SLSP |
Static LSP |
|
SMLK |
Smart Link |
|
SNMP |
Simple Network Management Protocol |
|
SRP |
SR-MPLS TE Policy |
|
SRPM |
Segment Routing Performance Measurement |
|
SRPV6 |
SRv6 TE Policy |
|
SRV6 |
SRv6 |
|
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 |
|
TE |
Traffic Engineering |
|
TELNETD |
Telnet Daemon |
|
TRILL |
Transparent Interconnect of Lots of Links |
|
UCM |
User Connection Management |
|
UNICFG |
Unified Configuration Management |
|
UPBAK |
User Plane Backup |
|
UPLB |
User Plane Load Balance |
|
UPMGR |
User Plane Management |
|
URPF |
Unicast Reverse Path Forwarding |
|
USER |
User |
|
VLAN |
Virtual Local Area Network |
|
VMMGR |
VM Manager |
|
VRRP |
Virtual Router Redundancy Protocol |
|
VSRP |
Virtual Service Redundancy Protocol |
|
VXLAN |
Virtual eXtensible LAN |
|
WEB |
Web |
|
WIPS |
Wireless Intrusion Prevention System |
Using this document
This document categorizes system log messages by software modules. The modules appear in this document in alphabetic order. For each module, the system log messages are also listed in alphabetic order of their mnemonic names.
This document explains messages in tables. Table 14 describes information provided in these tables.
Table 19 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 |
Provide a real message example. The example does not include the "<Int_16>TIMESTAMP HOSTNAME %%vendor" part, because information in this part varies with system settings. |
ACL/6/ACL_STATIS_INFO: ACL 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s). |
|
Explanation |
Explains the message, including the event or error cause. |
Number of packets that matched an ACL rule. This message is sent when the packet counter changes. |
|
Recommended action |
Provides recommended actions. For informational messages, no action is required. |
No action is required. |
API messages
This section contains API messages.
PORT_BW_NOTENOUGH
|
Message text |
Not enough limit resources. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
PORT/3/PORT_BW_NOTENOUGH: -MDC=1-Slot=2; Not enough limit resources. |
|
Explanation |
The rate-limiting resources are insufficient for an XGE/GE switchover. |
|
Recommended action |
Make sure the rate-limiting resources are sufficient. |
PORT_INTERNAL_FAULT
|
Message text |
A fault has been detected for the internal link used by the interface side. Please check the hardware! |
|
Severity level |
3 |
|
Example |
PORT/3/PORT_INTERNAL_FAULT: -MDC=1-Slot=2; A fault has been detected for the internal link used by the interface side. Please check the hardware! |
|
Explanation |
The interface used by the internal link is incorrect. |
|
Recommended action |
· Please contact Technical Support. |
BRAS_COM messages
This section contains common BRAS messages.
BRAS_FUNC
|
Message text |
Not enough resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DBRAS/4/BRAS_FUNC: -MDC=1 -Slot=4; Not enough resources. |
|
Explanation |
When you configure the maximum number of users allowed by using a single account, the rate limiting configuration does not take effect because the BRAS service rate limiting resources are insufficient. |
|
Recommended action |
1. Execute the display qos-acl resource slot slot-number command in system view to view the usage of BRAS service rate limiting resources on the current slot. 2. Contact Technical Support. |
BFD messages
This section contains BFD messages.
BFD_NORESOURCE
|
Message text |
No hardware resource for session LD [INT32]. |
|
Variable fields |
$1: BFD local identifier. |
|
Severity level |
5 |
|
Example |
BFD/5/BFD_NORESOURCE: -Slot=8; No hardware resource for session LD [1]. |
|
Explanation |
This message is generated when BFD hardware resources were exhausted, and BFD failed at this time. |
|
Recommended action |
· Verify whether services overlap, which causes the amount of used resources to exceed the total resources. · Release resources of other services. |
CFD messages
This section contains CFD messages.
HRD_TIMER_NORES
|
Message text |
No hardware resource for CFD detecting. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
CFD/4/HRD_TIMER_NORES: -MDC=1-Slot=5; No hardware resource for CFD detecting. |
|
Explanation |
The CFD feature is not available because of insufficient hardware timer resources. |
|
Recommended action |
Contact Technical Support. |
HRD_MEPNODE_NORES
|
Message text |
No hardware resource for ServiceInstance (INT32) MEP (INT32) RMEP (INT32). |
|
Variable fields |
$1: Service instance ID. $2: Local MEP ID. $3: Remote MEP ID. |
|
Severity level |
4 |
|
Example |
CFD/4/HRD_MEPNODE_NORES: -MDC=1-Slot=5; No hardware resource for ServiceInstance(1) MEP(2) RMEP(3). |
|
Explanation |
The CFD feature is not available because of insufficient hardware memory space. |
|
Recommended action |
Contact Technical Support. |
WATCHDOG_NORES
|
Message text |
No hardware resource for ServiceInstance (INT32) MEP (INT32) RMEP (INT32). |
|
Variable fields |
$1: Service instance ID. $2: Local MEP ID. $3: Remote MEP ID. |
|
Severity level |
4 |
|
Example |
CFD/4/WATCHDOG_NORES: -MDC=1-Slot=5; No hardware resource for ServiceInstance(1) MEP(2) RMEP(3). |
|
Explanation |
The CFD feature is not available because of insufficient hardware timer resources. |
|
Recommended action |
Contact Technical Support. |
COUNTERID_NORES
|
Message text |
No hardware resource for ServiceInstance (INT32) MEP (INT32). |
|
Variable fields |
$1: Service instance ID. $2: Local MEP ID. |
|
Severity level |
4 |
|
Example |
CFD/4/COUNTERID_NORES: -MDC=1-Slot=5; No hardware resource for ServiceInstance(1) MEP(2). |
|
Explanation |
The CFD feature is not available because of insufficient hardware counter resources. |
|
Recommended action |
Contact Technical Support. |
WATCHDOG_ADDR_NORES
|
Message text |
No hardware resource for ServiceInstance (INT32) MEP (INT32) RMEP (INT32). |
|
Variable fields |
$1: Service instance ID. $2: Local MEP ID. $3: Remote MEP ID. |
|
Severity level |
4 |
|
Example |
CFD/4/WATCHDOG_ADDR_NORES: -MDC=1-Slot=5; No hardware resource for ServiceInstance(1) MEP(2) RMEP(3). |
|
Explanation |
The CFD feature is not available because of insufficient hardware memory resources. |
|
Recommended action |
Contact Technical Support. |
BRIPRO messages
This section contains BRIPRO messages.
PVST_NOT_SUPPORT
|
Message text |
PVST is not supported on this board. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
BRIPRO/6/PVST_NOT_SUPPORT: -MDC=1-Slot=5; PVST is not supported on this board. |
|
Explanation |
PVST was enabled on a card that does not support this feature. |
|
Recommended action |
Do not configure PVST on the cards that do not support this feature. |
VLAN_TPID_CFGERR
|
Message text |
Operation failed because TPID value [INT32] was configured on [STRING]. Restore TPID value to default on this interface and try again. |
|
Variable fields |
$1: TPID value in the SVLAN tag. $2: Interface name. |
|
Severity level |
2 |
|
Example |
BRIPRO/2/VLAN_TPID_CFGERR: -MDC=1-Slot=4; Operation failed because TPID value 2000 was configured on Bridge-Aggregation200. Restore TPID value to default on this interface and try again. |
|
Explanation |
, only one interface can be configured with a TPID value in the SVLAN tag other than the default TPID value. Restore the TPID value in the SVLAN tag to the default for the interface prompted in the message before you modify the TPID value on the target interface. |
|
Recommended action |
1. Restore the TPID value in the SVLAN tag to the default for the interface prompted in the message as follows: 2. If the interface is a Layer 2 interface, use the undo qinq ethernet-type service-tag command. 3. If the interface is a Layer 3 interface, use the undo dot1q ethernet-type command. 4. Modify the TPID value in the SVLAN tag on the target interface. |
LAGG_SHARE_NOT_SPT
|
Message text |
Link aggregation load sharing not supported. |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
BRIPRO/6/LAGG_SHARE_NOT_SPT: -MDC=1-Slot=2; Link aggregation load sharing not supported. |
|
Explanation |
An aggregation group does not support the set global load sharing modes if its member ports are on certain cards. |
|
Recommended action |
No action is required. |
CFD_CFG_NOTSPT
|
Message text |
Interface [INT32].does not support CFD. Please check your configuration. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 |
|
Example |
BRIPRO/6/CFD_CFG_NOTSPT: -Slot=3; Interface XGE3/0/1 does not support CFD. Please check your configuration. |
|
Explanation |
The interface does not support CFD. |
|
Recommended action |
No action is required. |
NQA messages
SESSION_NOTSPT
|
Message text |
The board on slot [STRING] doesn't support NQA sessions. |
|
Variable fields |
$1: Slot number. |
|
Severity level |
4 |
|
Example |
NQA/4/SESSION_NOTSPT: -MDC=1-Slot=3; The board on slot 2 doesn't support NQA sessions. |
|
Explanation |
The card does not support NQA sessions. |
|
Recommended action |
Contact Technical Support. |
REFLECTOR_NOTSPT
|
Message text |
The board on slot [STRING] doesn't support reflectors on the NQA server. |
|
Variable fields |
$1: Slot number. |
|
Severity level |
4 |
|
Example |
NQA/4/REFLECTOR_NOTSPT: -MDC=1-Slot=3; The board on slot 3 doesn't support reflectors on the NQA server. |
|
Explanation |
The card does not support NQA reflector settings configured by the nqa reflector command. |
|
Recommended action |
Contact Technical Support. |
CLK messages
This section contains clock monitoring messages.
CLK_GET_CFG_OK
|
Message text |
Get clock global config succeed. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
DSYSM/5/CLK_GET_CFG_OK: Get clock global config succeed. |
|
Explanation |
The following settings were successfully obtained: · The contribution of the SSM quality level to automatic reference selection. · The clock reference selection mode. |
|
Recommended action |
No action is required. |
CLK_TRACE_CHG
|
Message text |
Traced reference change alarm, current traced reference is PTP. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_TRACE_CHG: Traced reference change alarm, current traced reference is PTP. |
|
Explanation |
The PTP clock source was selected as the clock reference for the device. |
|
Recommended action |
No action is required. |
CLK_TRACE_NOREF
|
Message text |
Traced reference change alarm, no reference traced now. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_TRACE_NOREF:Traced reference change alarm, no reference traced now. |
|
Explanation |
No clock reference was selected for the device. |
|
Recommended action |
1. Use the display network-clock status command to display the operating state of the network clock monitoring module. ¡ For automatic reference selection, verify that the device is connected to clock sources. ¡ For manual reference selection, first use the display network-clock source command to display the states of all clock sources. Then use the network-clock work-mode manual source command to specify a clock reference in Normal state. 2. If the problem persists, contact Technical Support. |
CLK_BE_TRACED
|
Message text |
Traced reference change alarm, current traced reference is [INT32]. |
|
Variable fields |
$1: ID of the current clock reference. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_BE_TRACED: Traced reference change alarm, current traced reference is 5. |
|
Explanation |
The current clock source was selected as the clock reference for the device. |
|
Recommended action |
No action is required. |
CLK_REF_RECOVER
|
Message text |
Reference [INT32] is recovered. |
|
Variable fields |
$1: ID of a clock source recovered from the Lost state. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_REF_RECOVER: References 5 is recovered. |
|
Explanation |
A clock source of the device recovered to its Normal state. Only a clock source in Normal state can be selected as the clock reference. You can use the display network-clock source command to display the states of clock sources. |
|
Recommended action |
No action is required. |
CLK_REF_LOST
|
Message text |
Reference [INT32] is lost. |
|
Variable fields |
$1: ID of a lost clock source. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_REF_LOST: References 5 is lost. |
|
Explanation |
A clock source of the device was lost because the clock source was disconnected or the specified line clock input port was down. |
|
Recommended action |
1. Verify that the device is disconnected from the clock source. 2. Verify that the line clock input port on the device is down. 3. If the problem persists, contact Technical Support. |
CLK_ALLREF_LOST
|
Message text |
All references are lost. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_ALLREF_LOST: All references are lost. |
|
Explanation |
All clock sources of the device were lost because clock sources were disconnected or the specified line clock input port was down. |
|
Recommended action |
1. Verify that the device is disconnected from each clock source. 2. Verify that the line clock input port on the device is down. 3. If the problem persists, contact Technical Support. |
CLK_PTP_PRICHG
|
Message text |
Priority alarm, current priority of PTP is [INT32]. |
|
Variable fields |
$1: Priority of the current PTP clock source. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_PTP_PRICHG Priority alarm, current priority of PTP is 8. |
|
Explanation |
The priority of the PTP clock source for the device was changed. |
|
Recommended action |
No action is required. |
CLK_REF_PRICHG
|
Message text |
Priority alarm, current priority of reference [INT32] is [INT32]. |
|
Variable fields |
$1: ID of a clock source. $2: Priority of the clock source. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_REF_PRICHG: Priority alarm, current priority of reference 2 is 8. |
|
Explanation |
The priority of a clock source for the device was changed. |
|
Recommended action |
No action is required. |
CLK_SSM_CHG
|
Message text |
SSM level alarm, current SSM level of reference [INT32] is [STRING]. |
|
Variable fields |
$1: ID of a clock source. $2: SSM quality level. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_SSM_CHG: SSM level alarm, current SSM level of reference 2 is SSUB. |
|
Explanation |
The SSM quality level of a clock source for the device was changed. |
|
Recommended action |
No action is required. |
CLK_PTPSSM_CHG
|
Message text |
SSM level alarm, current SSM level of PTP is [STRING]. |
|
Variable fields |
$1: SSM quality level. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_PTPSSM_CHG: SSM level alarm, current SSM level of PTP is SSUA. |
|
Explanation |
The SSM quality level of the PTP clock source for the device was changed. |
|
Recommended action |
No action is required. |
CLK_LOCKED
|
Message text |
Phase lock alarm, current phase lock mode is [STRING]. |
|
Variable fields |
$1: Phase lock state. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_LOCKED: Phase lock alarm, current phase lock mode is Locked. |
|
Explanation |
The phase lock state of the clock monitoring module was Locked. The clock reference was selected for the device. |
|
Recommended action |
No action is required. |
CLK_SSM_OUTLEVEL
|
Message text |
SSM out level alarm, current SSM out level is [STRING]. |
|
Variable fields |
$1: SSM quality level. |
|
Severity level |
5 |
|
Example |
DRIVER/5/CLK_SSM_OUTLEVEL: SSM out level alarm, current SSM out level is SSUB. |
|
Explanation |
The SSM quality level of the selected clock reference for the device was changed. |
|
Recommended action |
No action is required. |
DrvDebug
|
Message text |
Failed to receive ToD signals from the GPS device. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; Failed to receive ToD signals from the GPS device. |
|
Explanation |
This message is sent when the FPGA detects anomalies in ToD signals from the GPS device. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
Failed to receive 1PPS signals from the GPS device. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; Failed to receive 1PPS signals from the GPS device. |
|
Explanation |
This message is sent when the FPGA detects anomalies in 1PPS signals from the GPS device. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
On the MPU, the FPGA failed to transmit frequency signals to the clock chip. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; On the MPU, the FPGA failed to transmit frequency signals to the clock chip. |
|
Explanation |
This message is sent when the clock chip detects anomalies in 8 KHz signals from the FPGA. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
The clock chip on the MPU failed to distribute frequency signals to the FPGA. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; The clock chip on the MPU failed to distribute frequency signals to the FPGA. |
|
Explanation |
This message is sent when the FPGA detects anomalies in 8 KHz signals from the clock chip. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
The clock chip on the MPU failed to distribute 1PPS signals to the FPGA. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; The clock chip on the MPU failed to distribute 1PPS signals to the FPGA. |
|
Explanation |
This message is sent when the FPGA detects anomalies in 1PPS signals from the clock chip. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
On the MPU, the FPGA failed to transmit frequency signals to the clock chip. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The MPU failed to distribute ToD signals to the interface module. |
|
Explanation |
This message is sent when the interface module logic detects anomalies in ToD signals from the MPU. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
The MPU failed to distribute 1PPS signals to the interface module. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The MPU failed to distribute 1PPS signals to the interface module. |
|
Explanation |
This message is sent when the interface module logic detects anomalies in 1PPS signals from the MPU. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
The MPU failed to distribute frequency signals to the interface module. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The MPU failed to distribute frequency signals to the interface module. |
|
Explanation |
This message is sent when the interface module clock chip detects anomalies in frequency signals from the MPU. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
The interface module failed to distribute frequency signals to the interface. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The interface module failed to distribute frequency signals to the interface. |
|
Explanation |
This message is sent when the interface module clock chip detects anomalies in frequency signals from the service processing unit (SPU). |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
The interface failed to transmit frequency signals to the interface module. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1-Slot=8; The interface failed to transmit frequency signals to the interface module. |
|
Explanation |
This message is sent when the interface module clock chip detects anomalies in frequency signals from the interface. |
|
Recommended action |
Contact Technical Support. |
DEV messages
This section contains device management messages.
CPLD_STAT_CONFLICT
|
Message text |
The CPLD on the standby MPU in slot [INT32] mistakenly reported a switchover to the active MPU role. The active MPU is in slot [INT32]. |
|
Variable fields |
$1: Slot number of the standby MPU. $2: Slot number of the active MPU. |
|
Severity level |
4 |
|
Example |
DEVD/4/CPLD_STAT_CONFLICT: -MDC=1-Slot=0; The CPLD on the standby MPU in slot 0 mistakenly reported a switchover to the active MPU role. The active MPU is in slot 1. |
|
Explanation |
The CPLD on the standby MPU mistakenly reported a switchover to the active MPU role. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
Over-current occurred to the USB port on the MPU. Please remove and check the USB device. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: -MDC=1; Over-current occurred to the USB port on the MPU. Please remove and check the USB device. |
|
Explanation |
The current of a USB port on the MPU is too high. The connected USB device failed. |
|
Recommended action |
1. Replace the USB device. 2. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
Temperature of the board is too high! |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DRVPLAT/4/DrvDebug: Temperature of the board is too high! |
|
Explanation |
The card temperature is too high. Fans failed or the ambient temperature is too high. |
|
Recommended action |
1. Check the ambient temperature. If the ambient temperature is too high, verify that the air conditioner for the room is operating correctly. 2. Verify that the air inlet and outlet for the device are not blocked. 3. Check the fans of the device. If the fans in a fan tray are not operating correctly, replace the fan tray. 4. Verify that all cards are installed correctly and all blank slots are covered by filler panels. 5. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
Warning: Chip [INT32] temperature([STRING]) in slot [INT32] is too high, please check it. |
|
Variable fields |
$1: Chip ID. $2: Temperature of the chip. $3: Slot number of the card. |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: Warning:Chip 1 temperature(80) in slot 2 is too high, please check it. |
|
Explanation |
The temperature of a chip is too high. |
|
Recommended action |
1. Check the ambient temperature. If the ambient temperature is too high, verify that the air conditioner for the room is operating correctly. 2. Verify that the air outlet for the device is not blocked. 3. Check the fans of the device. If the fans in a fan tray are not operating correctly, replace the fan tray. 4. Verify that all cards are installed correctly and all blank slots are covered by filler panels. 5. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
hotspot [STRING] in slot [INT32] temperature([STRING]) is too high, please check it. |
|
Variable fields |
$1: Hotspot sensor ID. $2: Slot number of the card. $3: Temperature value. |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: hotspot 1 in slot 2 temperature(80) is too high, please check it. |
|
Explanation |
A hotspot sensor on a card detected that the temperature was too high. |
|
Recommended action |
1. Check the ambient temperature. If the ambient temperature is too high, verify that the air conditioner for the room is operating correctly. 2. Verify that the air outlet for the device is not blocked. 3. Check the fans of the device. If the fans in a fan tray are not operating correctly, replace the fan tray. 4. Verify that all cards are installed correctly and all blank slots are covered by filler panels. 5. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
Warning: cpu temperature([STRING]) in slot [INT32] is too high, please check it. |
|
Variable fields |
$1: Temperature value. $2: Slot number of the card. In IRF mode, this value indicates the global slot number, which is calculated by using the following equation: Global number = (Member ID – 1) * 18 + slot number of the card in the chassis.) |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: Warning: cpu temperature(80) in slot 2 is too high, please check it. |
|
Explanation |
The temperature of the CPU on a card is too high. |
|
Recommended action |
1. Check the ambient temperature. If the ambient temperature is too high, verify that the air conditioner for the room is operating correctly. 2. Verify that the air inlet and outlet for the device are not blocked. 3. Check the fans of the device. If the fans in a fan tray are not operating correctly, replace the fan tray. 4. Verify that all cards are installed correctly and all blank slots are covered by filler panels. 5. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
Warning: The LPU board on slot [STRING] is not compatible with MPU board. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Warning: The LPU board on slot 4 is not compatible with MPU board. |
|
Explanation |
The specified card has a different device identifier than the MPU. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
Warning: Standby board on slot [STRING] is not compatible with MPU board. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Warning: Standby board on slot 1 is not compatible with MPU board. |
|
Explanation |
The specified MPU has different device identification than the active MPU. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
Warning: Two power modules have different power specifications. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
Warning: Two power modules have different power specifications. |
|
Explanation |
Power modules in the router have different power specifications. |
|
Recommended action |
Use power modules of the same power specifications in the router. |
DrvDebug
|
Message text |
Current temperature on slot [STRING] is [STRING] degrees centigrade, which is higher than the shutdown threshold. The board is being shut down. |
|
Variable fields |
$1: Slot number of the card. $2: Temperature. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Current temperature on slot 4 is 101 degrees centigrade, which is higher than the shutdown threshold. The board is being shut down. |
|
Explanation |
The temperature of a card exceeded the shutdown threshold and was going to be shut down. |
|
Recommended action |
1. Verify that all fans are installed firmly. If a fan has been pulled out, install the fan firmly and power on the card after the fan operates correctly. 2. If the problem persists, check the operating status of fans. If one or more fans are not operating correctly, replace the fans. 3. If the problem persists, replace the card or wait for the card to cool down. 4. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
The card in slot [UINT32] failed to start up. The card is not compatible with the chassis. |
|
Variable fields |
$1: Slot number of the card. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; The card in slot 4 failed to start up. The card is not compatible with the chassis. |
|
Explanation |
The specified card was not compatible with the chassis. |
|
Recommended action |
1. Replace the card with a card that is compatible with the chassis. 2. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
In Mode [STRING], the card in slot [INT32] is not supported. Now rebooting. |
|
Variable fields |
$1: System operating mode of the device. $2: Slot number of the card. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: In Mode sdn-wan, the card in slot 6 is not supported. Now rebooting. |
|
Explanation |
The specified interface module is not supported in the current system operating mode, and is to reboot. |
|
Recommended action |
Determine whether to continue using the specified system operating mode: · To continue using the specified system operating mode, replace the interface module with an interface module that supports the specified system operating mode. · To stop using the specified system operating mode, execute the system-working-mode command to specify a new system operating mode. |
DrvDebug
|
Message text |
Power supply in power [UINT32] became abnormal. The power supply might be powered off. |
|
Variable fields |
$1: Power supply slot. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1;Power supply in power 1 became abnormal. The power supply might be powered off. |
|
Explanation |
The system detected a power supply failure. The power supply might be powered off. |
|
Recommended action |
· Check the power supply on the device. · Replace the abnormal power supply. |
SFC_CHANGED
|
Message text |
Warning: Short circuit sfc has been changed, it will take effect only after system restart. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
DEVD/4/SFC_CHANGED:Warning: Short circuit sfc has been changed, it will take effect only after system restart. |
|
Explanation |
The number of switching fabric modules was reduced, and the chassis is no longer fully configured with switching fabric modules. You must reboot the system for the switching fabric modules to take effect. |
|
Recommended action |
Reboot the system. |
CPLD_STAT_CONFLICT
|
Message text |
The CPLD on the standby MPU in slot [UINT32] mistakenly reported a switchover to the active MPU role. The active MPU is in slot [UINT32]. |
|
Variable fields |
$1: Slot number. $2: Slot number. |
|
Severity level |
4 |
|
Example |
DEVD/4/CPLD_STAT_CONFLICT:The CPLD on the standby MPU in slot 1 mistakenly reported a switchover to the active MPU role. The active MPU is in slot 0. |
|
Explanation |
The CPLD on the standy MPU reported a switchover to the active MPU role mistakenly. |
|
Recommended action |
Contact Technical Support. |
DEVD
This section contains DEVD messages.
CARD_NOT_CMPT
|
Message text |
The board installed in slot [UINT32] cannot start up.The board model is different from the preprovisioned model. |
|
Variable fields |
$1: Slot number of the card. |
|
Severity level |
3 |
|
Example |
DEVD/3/CARD_NOT_CMPT: -MDC=1; The board installed in slot 8 cannot start up. The board model is different from the preprovisioned model. |
|
Explanation |
In standalone mode, the specified card cannot start up because the model of the card is different from the preprovisioned model. |
|
Recommended action |
1. Replace the card with a card of the preprovisioned model. 2. If the problem persists, contact Technical Support. |
EDEV_CMD_SET_RSA_RESULT
|
Message text |
Check can't pass! |
|
Variable fields |
· N/A |
|
Severity level |
4 |
|
Example |
DEVD/4/EDEV_CMD_SET_RSA_RESULT: Check can't pass!. |
|
Explanation |
This message is generated when software images do not exist or are invalid. |
|
Recommended action |
Upload valid software images. |
DOMAIN messages
This section contains DOMAIN messages.
DOMAIN_IP_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolLowerValue=[STRING]; IP resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: Low alarm threshold for IP address usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IP_LOWTHR_ALM: -Domain=abc-IPUsage=10%-IPPoolLowerValue=20%; IP resource usage reached or dropped below the lower threshold. |
|
Explanation |
The usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or dropped below the low alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_IP_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolLowerValue=[STRING]; Low IP resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: Low alarm threshold for IP address usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IP_LOWTHR_ALM_REMOVE: -Domain=dom1-IPUsage=50%-IPPoolLowerValue=20%; Low IP resource usage alarm condition cleared. |
|
Explanation |
The usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or exceeded the value calculated by using the formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IP_UPTHR_ALM
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolUpperValue=[STRING]; IP resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: High alarm threshold for IP address usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IP_UPTHR_ALM: -Domain=dom1-IPUsage=90%-IPPoolUpperValue=80%; IP resource usage reached or exceeded the upper threshold. |
|
Explanation |
The usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or exceeded the high alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_IP_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPUsage=[STRING]-IPPoolUpperValue=[STRING]; High IP resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IP address usage. $3: High alarm threshold for IP address usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IP_UPTHR_ALM_REMOVE: -Domain=dom1-IPUsage=50%-IPPoolUpperValue=80%; High IP resource usage alarm condition cleared. |
|
Explanation |
The usage of IP addresses in the authorization IP pool or IP pool group for an ISP domain reached or dropped below the value calculated by using the formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolLowerValue=[STRING]; IPv6 address resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IPV6_LOWTHR_ALM: -Domain=abc-IPv6Usage=10%-IPv6PoolLowerValue=20%; IPv6 address resource usage reached or dropped below the lower threshold. |
|
Explanation |
The usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the low alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolLowerValue=[STRING]; Low IPv6 address resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IPV6_LOWTHR_ALM_REMOVE: -Domain=dom1-IPv6Usage=50%-IPv6PoolLowerValue=20%; Low IPv6 address resource usage alarm condition cleared. |
|
Explanation |
The usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the value calculated by using the formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_UPTHR_ALM
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolUpperValue=[STRING]; IPv6 address resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolUpperValue=[STRING]; IPv6 address resource usage reached or exceeded the upper threshold. |
|
Explanation |
The usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the high alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_IPV6_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-IPv6Usage=[STRING]-IPv6PoolUpperValue=[STRING]; High IPv6 address resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: IPv6 address usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_IPV6_UPTHR_ALM_REMOVE: -Domain=dom1-IPv6Usage=50%-IPv6PoolUpperValue=80%; High IPv6 address resource usage alarm condition cleared. |
|
Explanation |
The usage of IPv6 addresses in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the value calculated by using the formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; ND prefix resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. ND prefixes refer to IPv6 prefixes assigned by ND. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_ND_PREF_LOWTHR_ALM: -Domain=abc-NDPrefixUsage=10%-IPv6PoolLowerValue=20%; ND prefix resource usage reached or dropped below the lower threshold. |
|
Explanation |
The usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or dropped below the low alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; Low ND prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_ND_PREF_LOWTHR_ALM_REMOVE: -Domain=abc-NDPrefixUsage=50%-IPv6PoolLowerValue=20%; Low ND prefix resource usage alarm condition cleared. |
|
Explanation |
The usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or exceeded the value calculated by using the formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_UPTHR_ALM
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; ND prefix resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_ND_PREF_UPTHR_ALM: -Domain=abc-NDPrefixUsage=90%-IPv6PoolUpperValue=80%; ND prefix resource usage reached or exceeded the upper threshold. |
|
Explanation |
The usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or exceeded the high alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_ND_PREF_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-NDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; High ND prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: ND prefix usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_ND_PREF_UPTHR_ALM_REMOVE: -Domain=abc-NDPrefixUsage=50%-IPv6PoolUpperValue=80%; High ND prefix resource usage alarm condition cleared. |
|
Explanation |
The usage of ND prefixes in the authorization ND prefix pool or ND prefix pool group for an ISP domain reached or dropped below the value calculated by using the formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_LOWTHR_ALM
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; PD prefix resource usage reached or dropped below the lower threshold. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. PD prefixes refer to IPv6 prefixes assigned by DHCPv6 PD. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_PD_PREF_LOWTHR_ALM: -Domain=abc-PDPrefixUsage=10%-IPv6PoolLowerValue=20%; PD prefix resource usage reached or dropped below the lower threshold. |
|
Explanation |
The usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the low alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolLowerValue=[STRING]; Low PD prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: Low alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_PD_PREF_LOWTHR_ALM_REMOVE: -Domain=abc-PDPrefixUsage=50%-IPv6PoolLowerValue=20%; Low PD prefix resource usage alarm condition cleared. |
|
Explanation |
The usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the value calculated by using the formula: Low alarm threshold + (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_UPTHR_ALM
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; PD prefix resource usage reached or exceeded the upper threshold. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_PD_PREF_UPTHR_ALM: -Domain=abc-PDPrefixUsage=90%-IPv6PoolUpperValue=80%; PD prefix resource usage reached or exceeded the upper threshold. |
|
Explanation |
The usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or exceeded the high alarm threshold. |
|
Recommended action |
No action is required. |
DOMAIN_PD_PREF_UPTHR_ALM_REMOVE
|
Message text |
-Domain=[STRING]-PDPrefixUsage=[STRING]-IPv6PoolUpperValue=[STRING]; High PD prefix resource usage alarm condition cleared. |
|
Variable fields |
$1: ISP domain name. $2: PD prefix usage. $3: High alarm threshold for IPv6 address or prefix usage. |
|
Severity level |
5 |
|
Example |
DOMAIN/5/DOMAIN_PD_PREF_UPTHR_ALM_REMOVE: -Domain=abc-PDPrefixUsage=50%-IPv6PoolUpperValue=80%; High PD prefix resource usage alarm condition cleared. |
|
Explanation |
The usage of PD prefixes in the authorization IPv6 address pool or IPv6 address pool group for an ISP domain reached or dropped below the value calculated by using the formula: High alarm threshold – (high alarm threshold – low alarm threshold)*10%. |
|
Recommended action |
No action is required. |
DIAG messages
This section contains DIAG messages. These messages are output only if the system is configured to take an action in response to hardware failures.
FMEA_ERR_REBOOT
|
Message text |
Hardware error detected on slot [UINT32]. Rebooting the card… |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
2 |
|
Example |
DIAG/2/FMEA_ERR_REBOOT: Hardware error detected on slot 2. Rebooting the card… |
|
Explanation |
FMEA detected an interface module hardware failure. The system was rebooting the interface module. |
|
Recommended action |
Contact Technical Support. |
FMEA_ERR
|
Message text |
Hardware error detected on slot [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
4 |
|
Example |
DIAG/4/FMEA_ERR: Hardware error detected on slot 2. |
|
Explanation |
FMEA detected an interface module hardware failure. The system only sent a log message and did not try to resolve the issue. |
|
Recommended action |
Contact Technical Support. |
FMEA_ERR
|
Message text |
EMMC storage media error or storage insufficiency detected on slot [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
3 |
|
Example |
DIAG/3/FMEA_ERR: -MDC=1; EMMC storage media error or storage insufficiency detected on slot 1. |
|
Explanation |
EMMC storage media error or storage insufficiency was detected. |
|
Recommended action |
Contact Technical Support. |
FMEA_ERR
|
Message text |
LVDS timeout on slot [UINT32] was detected on slot [UINT32]. |
|
Variable fields |
$1: Slot number of the switching fabric module in the device. $1: Slot number of the interface module in the device. |
|
Severity level |
3 |
|
Example |
DIAG/3/FMEA_ERR: -Slot=10; LVDS timeout on slot 10 was detected on slot 4. |
|
Explanation |
Access from the LVDS port on the switching fabric module to the CPLD on the interface module timed out. |
|
Recommended action |
Contact Technical Support. |
DSYSM messages
This section contains DSYSM messages.
INNERLINK_EXCEPTION
|
Message text |
An exception has occured on an internal link. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
DSYSM/3/INNERLINK_EXCEPTION: -MDC=1; An exception has occured on an internal link. |
|
Explanation |
Error occurred on the MPU hardware, which resulted in an exception on an internal chip link. |
|
Recommended action |
Contact Technical Support. |
EKDM messages
This section contains EKDM messages.
EKDM_REBOOT_PREVNT
|
Message text |
Standby MPU in slot [UINT32] rebooted abnormally [UINT32] times and was prevented from rebooting again. |
|
Variable fields |
$1: Slot number of the card in the device. $2: Number of reboot times. |
|
Severity level |
2 |
|
Example |
DEVD/2/EKDM_REBOOT_PREVNT: -MDC=1; Global standby MPU in chassis 3 slot 1 rebooted abnormally 4 times and was prevented from rebooting again. |
|
Explanation |
The system did not start the standby MPU again after the standby MPU exceptionally rebooted the specified number of times. |
|
Recommended action |
1. Replace the standby MPU. 2. If the problem persists, contact Technical Support. |
FDB messages
This section contains FDB messages.
MAC_REACH_LIMIT
|
Message text |
The number of MAC address received in interface [STRING] reaches the upper limit. The number of MAC address received in VLAN [INT32] reaches the upper limit. |
|
Variable fields |
$1: Interface name. $2: VLAN ID. |
|
Severity level |
3 |
|
Example |
FDB/3/MAC_REACH_LIMIT: -MDC=1-Slot=3; The number of MAC address received in interface Ten-GigabitEthernet3/0/5 reaches the upper limit. |
|
Explanation |
The number of MAC addresses learned by an interface or VLAN reached the upper limit. |
|
Recommended action |
No action is required. |
FIB messages
This section contains FIB messages.
FIB_BOARDMSG_CONGEST
|
Message text |
· Text 1: The FIB message on the board is congested: SlotID=[UINT32]. · Text 2: The FIB message on the board is congested: Chassis=[UINT32], SlotID=[UINT32]. |
|
Variable fields |
In text 1: $1: Slot number. In text 2: $1: Chassis number. $2: Slot number. |
|
Severity level |
4 |
|
Example |
· Text 1: FIB/4/FIB_BOARDMSG_CONGEST: The FIB message on the board is congested: SlotID=2. · Text 2: FIB/4/FIB_BOARDMSG_CONGEST: The FIB message on the board is congested: Chassis=1, SlotID=2. |
|
Explanation |
Packet forwarding congestion occurred on the current card. |
|
Recommended action |
Check whether a packet attack exists. |
FIB_BOARDMSG_CONGESTRESUME
|
Message text |
· Text 1: The FIB message congestion is resolved: SlotID=[UINT32]. · Text 2: The FIB message congestion is resolved: Chassis=[UINT32], SlotID=[UINT32]. |
|
Variable fields |
In text 1: $1: Slot number. In text 2: $1: Chassis number. $2: Slot number. |
|
Severity level |
5 |
|
Example |
· Text 1: FIB/4/FIB_BOARDMSG_CONGESTRESUME: The FIB message congestion is resolved: SlotID =2. · Text 2: FIB/4/FIB_BOARDMSG_CONGESTRESUME: The FIB message congestion is resolved: Chassis=1, SlotID =2. |
|
Explanation |
Packet forwarding congestion was resolved on the current card. |
|
Recommended action |
No action is required. |
FIB_FILE
|
Message text |
Failed to save the IP forwarding table due to lack of storage resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
FIB/4/FIB_FILE: -MDC=1; Failed to save the IP forwarding table due to lack of storage resources. |
|
Explanation |
Failed to save the IP forwarding table due to lack of storage resources. |
|
Recommended action |
Delete unused files to release storage space. |
FIB_OVERLOAD_FORWARD
|
Message text |
The system is in the overload forwarding state because the FIB module is overloaded: FibOverloadModule=[STRING]. |
|
Variable fields |
$1: FIB entry type: · FIB4—The number of IPv4 FIB entries has reached 80% of the upper limit. · FIB6—The number of IPv6 FIB entries has reached 80% of the upper limit. |
|
Severity level |
4 |
|
Example |
FIB/4/FIB_OVERLOAD_FORWARD: The system is in the overload forwarding state because the FIB module is overloaded: FibOverloadModule=FIB4. |
|
Explanation |
The number of FIB entries has reached 80% of the upper limit on the device. |
|
Recommended action |
Check whether a packet attack exists. |
FIB_OVERLOAD_FORWARDRESUME
|
Message text |
The system changes from the overload forwarding state to the normal state: FibOverloadModule=[STRING]. |
|
Variable fields |
$1: FIB entry type: · FIB4—The number of IPv4 FIB entries has dropped to 50% of the upper limit. · FIB6—The number of IPv6 FIB entries has dropped to 50% of the upper limit. |
|
Severity level |
5 |
|
Example |
FIB/4/FIB_OVERLOAD_FORWARDRESUME: The system changes from the overload forwarding state to the normal state: FibOverloadModule=FIB4. |
|
Explanation |
The number of FIB entries has restored to normal state on the device. |
|
Recommended action |
No action is required. |
IBC
This section contains IBC messages.
CTRL_PATH_FAULT
|
Message text |
A link fault occurred on a control path. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
IBC/3/CTRL_PATH_FAULT: -MDC=1; A link fault occurred on a control path. |
|
Explanation |
A link fault occurred on a control path of the device. |
|
Recommended action |
Contact Technical Support. |
IF
This section contains interface management messages.
RAGG_MACADDR_NOTSPT
|
Message text |
Member port of Route-Aggregation doesn't support the mac-address command. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
LIF/3/RAGG_MACADDR_NOTSPT: -MDC=1-Slot=3; Member port of Route-Aggregation doesn't support the mac-address command. |
|
Explanation |
The mac-address command cannot be executed on a Layer 3 Ethernet interface that is already assigned to an aggregation group. |
|
Recommended action |
Execute the mac-address command on the Layer 3 aggregate interface. |
MACADDR_NOTSPT_RAGG
|
Message text |
[STRING] has been configured with a MAC address and can't be assigned to [STRING]. |
|
Variable fields |
$1: Interface name. If the device fails to obtain the interface name, The interface is displayed. $2: Layer 3 aggregate interface name. If the device fails to obtain the interface name, the interface number is not displayed. |
|
Severity level |
3 |
|
Example |
LIF/3/MACADDR_NOTSPT_RAGG: -MDC=1-Slot=3; Ten-GigabitEthernet3/0/5 has been configured with a MAC address and can't be assigned to Route-Aggregation100. LIF/3/MACADDR_NOTSPT_RAGG: -MDC=1-Slot=3; The interface has been configured with a MAC address and can't be assigned to Route-Aggregation. |
|
Explanation |
A Layer 3 Ethernet interface cannot be assigned to an aggregation group if it has been assigned a MAC address by using the mac-address command. |
|
Recommended action |
Execute the undo mac-address command on the Layer 3 Ethernet interface before you assign it to an aggregation group. |
RAGGSUB_NORES
|
Message text |
Operation failed because of insufficient resources on Route-Aggregation [INT32] |
|
Variable fields |
$1: Aggregate subinterface number. |
|
Severity level |
2 |
|
Example |
LIF/2/RAGGSUB_NORES: -MDC=1-Slot=2; Operation failed because of insufficient resources on Route-Aggregation1.1. |
|
Explanation |
System resources were not enough to enable the traffic statistics feature. |
|
Recommended action |
1. Use the undo traffic-statistic enable command to disable the traffic statistics feature for the aggregate subinterface. 2. If the problem persists, contact Technical Support. |
RAGGSUB_L2VPN_ CONFLICT
|
Message text |
The operation is not supported because configuration conflicts on Route-Aggregation[INT32] |
|
Variable fields |
$1: Aggregate subinterface number. |
|
Severity level |
2 |
|
Example |
LIF/2/RAGGSUB_L2VPN_ CONFLICT: -MDC=1-Chassis=1-Slot=3; The operation is not supported because configuration conflicts on Route-Aggregation1.1. |
|
Explanation |
The traffic statistics feature and the L2VPN feature are mutually exclusive on the aggregate subinterface. If you configure both of the features, the traffic statistics feature does not take effect. |
|
Recommended action |
1. Use the undo traffic-statistic enable command to disable the traffic statistics feature for the aggregate subinterface. 2. Disable L2VPN configuration for the aggregate subinterface. 3. Execute the traffic-statistic enable command for the aggregate subinterface. 4. If the problem persists, contact Technical Support. |
OP_INF_NORES
|
Message text |
Operation failed because of insufficient hardware resources. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
LIF/3/OP_INF_NORES: -MDC=1-Slot=4; Operation failed because of insufficient hardware resources. |
|
Explanation |
A created interface (for example, a VLAN interface) is unavailable because of insufficient hardware resources. |
|
Recommended action |
1. Use the undo command to delete the interface. 2. Use the display interface interface-type brief command to displays brief interface information. 3. Delete unnecessary interfaces to release resources and re-create the interface. 4. If the problem persists, contact Technical Support. |
OP_SUBINT_NORES
|
Message text |
Operation failed on [STRING] because of insufficient hardware resources. |
|
Variable fields |
$1: Interface name or VLAN number. |
|
Severity level |
3 |
|
Example |
LIF/3/OP_SUBINT_NORES: -MDC=1-Slot=4; Operation failed on Route-Aggregation3.2 because of insufficient hardware resources. LIF/3/OP_SUBINT_NORES: -MDC=1-Slot=4; Operation failed on VLAN222 because of insufficient hardware resources. |
|
Explanation |
A created interface (for example, a Layer 3 aggregate subinterface) or sub-VLAN is unavailable because of insufficient hardware resources. |
|
Recommended action |
1. Use the undo command to delete the interface or VLAN. 2. Use the display interface interface-type brief command to displays brief interface information. Alternatively, use the display supervlan command to display information about super VLANs and their associated sub-VLANs. 3. Delete unnecessary interfaces or sub-VLANs to release resources and re-create the interface or VLAN. 4. If the problem persists, contact Technical Support. |
INT_QINQ_NORES
|
Message text |
Not enough resources for [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 |
|
Example |
LIF/6/INT_QINQ_NORES: -MDC=1-Slot=5; Not enough resources for Route-Aggregation1.1. |
|
Explanation |
Failed to enable the QinQ termination feature because of insufficient hardware resources. |
|
Recommended action |
1. Use the display current-configuration | include second-dot1q command to display the current QinQ termination configuration. 2. Use the undo vlan-type dot1q vid second-dot1q command to disable QinQ termination to release resources. 3. If the problem persists, contact Technical Support. |
L2VPN_NOTSPT
|
Message text |
This board doesn’t support VE-L2VPN subinterfaces. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
LIF/3/L2VPN_NOTSPT: -MDC=1-Slot=3; This board doesn’t support VE-L2VPN subinterfaces. |
|
Explanation |
operating in standard mode do not support VE-L2VPN subinterfaces. |
|
Recommended action |
No action is required. |
IFIT messages
This section contains in-situ Flow Information Telemetry (iFit) messages.
IFIT_COUNTER_NORES
|
Message text |
Not enough counter resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IFIT/4/IFIT_COUNTER_NORES: Not enough counter resource. |
|
Explanation |
Counter resources were exhausted for the system to measure new target flows by using iFIT. |
|
Recommended action |
Delete unnecessary iFIT configurations to release counter resources. |
IFIT_FLOW_NORES
|
Message text |
Not enough Flow resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IFIT/4/IFIT_FLOW_NORES: Not enough Flow resource. |
|
Explanation |
The amount of target flows for iFIT measurement exceeded the system upper limit, which causes resource exhaustion. The system cannot measure the newly-learned target flows by using iFIT. |
|
Recommended action |
Delete unnecessary iFIT configurations to reduce the amount of iFIT target flows in the system. |
IFIT_MAPPING_NORES
|
Message text |
Not enough iFit Mapping resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IFIT/4/IFIT_MAPPING_NORES: Not enough iFit Mapping resource. |
|
Explanation |
iFIT mapping resources were exhausted for the system to measure the newly-learned target flows by using iFIT. |
|
Recommended action |
Delete unnecessary iFIT configurations to release iFIT mapping resources. |
IFIT_ACL_NORES
|
Message text |
Not enough ACL resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IFIT/4/IFIT_ACL_NORES: Not enough ACL resource. |
|
Explanation |
ACL resources were exhausted for the system to measure the newly-learned target flows by using iFIT. |
|
Recommended action |
1. Delete unnecessary iFIT configurations to release ACL resources 2. Delete other unnecessary service configurations that use ACL to release ACL resources. |
IFNET messages
This section contains interface management messages.
VLAN_MODE_CHG
|
Message text |
Dynamic VLAN [INT32] has changed to a static VLAN. |
|
Variable fields |
$1: VLAN ID. |
|
Severity level |
5 |
|
Example |
IFNET/5/VLAN_MODE_CHG: -MDC=1; Dynamic VLAN 20 has changed to a static VLAN. |
|
Explanation |
Creating a VLAN interface changed the dynamic VLAN to a static VLAN. |
|
Recommended action |
No action is required. |
INQA messages
This section contains iNQA messages.
INQA_COUNTER_NORES
|
Message text |
Not enough counter resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
INQA/4/INQA_COUNTER_NORES: Not enough counter resource. |
|
Explanation |
The system failed to perform iNQA operations on the newly learned target flows because of insufficient counter resources. |
|
Recommended action |
Delete unused iNQA configuration to release resources. |
INQA_ACL_NORES
|
Message text |
Not enough ACL resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
INQA/4/INQA_ACL_NORES: Not enough ACL resource. |
|
Explanation |
The system failed to perform iNQA operations on the newly learned target flows because of insufficient ACL resources. |
|
Recommended action |
1. Delete unused iNQA configuration to release resources. 2. Delete unused service configuration that consumes ACL resources to release resources. |
IP ROUTING messages
This section contains IP routing messages.
ROUTE_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
L3/3/ROUTE_NORES: -MDC=1-Slot=4; No enough resource |
|
Explanation |
Failed to perform the operation because of insufficient hardware resources. For example, packet statistics collection cannot be performed because of insufficient statistics-collection resources. |
|
Recommended action |
Contact Technical Support. |
ECMP_NORES
|
Message text |
Not enough ECMP-ID resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/ECMP_NORES: -MDC=1-Slot=5; Not enough ECMP-ID resource. |
|
Explanation |
Failed to learn a new ECMP route because of insufficient ECMP-ID resources on the card. |
|
Recommended action |
Contact Technical Support. |
ROUTE6_ECMP_NORES
|
Message text |
Not enough ECMP-ID resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/ROUTE6_ECMP_NORES: -MDC=1-Slot=5; Not enough ECMP-ID resource. |
|
Explanation |
Failed to learn a new ECMP route because of insufficient ECMP-ID resources on the card. |
|
Recommended action |
Contact Technical Support. |
VN_NORES
|
Message text |
No enough VN index resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/VN_NORES: -MDC=1-Slot=3; No enough VN index resource. |
|
Explanation |
Failed to learn a new non-host route because of insufficient VN index resources on the card. |
|
Recommended action |
Contact Technical Support. |
VN_ECMP_NORES
|
Message text |
Not enough ECMP-ID resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/VN_ECMP_NORES: -MDC=1-Slot=3; Not enough ECMP-ID resource. |
|
Explanation |
Failed to learn a new ECMP route because of insufficient ECMP-ID resources on the card. |
|
Recommended action |
Contact Technical Support. |
IPoE messages
This section contains IPoE messages.
DIAG
|
Message text |
The ip subscriber enable, redirect URL may not take effect on interface [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
DIPOE/4/DIAG: -MDC=1-Slot=3; The ip subscriber enable, redirect URL may not take effect on interface Route-Aggregation138.2. |
|
Explanation |
After IPoE is enabled on an interface, ACL resources on the card of the interface are insufficient. As a result, the URL redirection feature does not take effect for IPoE users on the interface. |
|
Recommended action |
1. Use the display qos-acl resource command to check the ACL resource usage. Delete unnecessary ACLs to release resources, and enable IPoE again. 2. If the problem persists, contact Technical Support. |
IPOE_ACCOUNT_NORES
|
Message text |
Insufficient BRAS statistics or BRAS rate-limiting profile resources for IPoE. The statistics or rate-limiting function of the session(UserID = [int32]) does not take effect. |
|
Variable fields |
$1: User ID. |
|
Severity level |
4 |
|
Example |
DIPOE/4/IPOE_ACCOUNT_NORES:Insufficient BRAS statistics or BRAS rate-limiting profile resources for IPoE. The statistics or rate-limiting function of the session(UserID = 0x38200002) does not take effect. |
|
Explanation |
Because of insufficient ACL and BAS resources, functions such as session accounting and rate limit are unavailable for the following items: · New IPoE sessions. · New IPoE users using an existing IPoE session. |
|
Recommended action |
1. Use the display qos-acl resource command to check the ACL and BAS resource usage on the card. Delete unnecessary ACLs and BRASCar to release resources. 2. If the problem persists, contact Technical Support. |
IPOE_ACCOUNT_NORES
|
Message text |
Insufficient BRAS statistics or BRAS rate-limiting profile resources for IPoE. The statistics or rate-limiting function of the session(UserID = [int32]) does not take effect according to the account number. |
|
Variable fields |
$1: User ID. |
|
Severity level |
4 |
|
Example |
DIPOE/4/IPOE_ACCOUNT_NORES:Insufficient BRAS statistics or BRAS rate-limiting profile resources for IPoE. The statistics or rate-limiting function of the session(UserID = 0x38200002) does not take effect according to the account number. |
|
Explanation |
Because of insufficient statistics or rate-limiting profile resources, accounting and rate-limiting by account number does not take effect on new IPoE sessions. |
|
Recommended action |
1. Use the display qos-acl resource command to check the ACL and BAS resource usage on the card. Delete unnecessary ACLs and BRASCar to release resources. 2. If the problem persists, contact Technical Support. |
IPOE_IPV4_HTTP_ATTACK_EXCEED_ERROR
|
Message text |
The number of anti-HTTP attack IPv4 ACLs exceeded 30 percent of the total number of IPv4 ACLs. The percentage is [STRING]. |
|
Variable fields |
$1: Percentage of IPv4 ACLs for HTTP attack defense against the total IPv4 ACLs on the card. |
|
Severity level |
4 |
|
Example |
%Mar 15 01:18:25:071 2020 H3C DIPOE/4/DIAG: -MDC=1-Slot=4; The number of anti-HTTP attack IPv4 ACLs exceeded 30 percent of the total number of IPv4 ACLs. The percentage is 31%. |
|
Explanation |
The percentage of IPv4 ACLs for HTTP attack defense against the total IPv4 ACLs on the card reached 31%, which exceeded 30%. |
|
Recommended action |
Execute the display ip subscriber http-defense attack ip [ slot slotnum ] command to view HTTP attack statistics entries. |
IPOE_IPV4_REMAIN_ACL_BELOW_ERROR
|
Message text |
The number of remaining IPv4 ACLs dropped below 20 percent of the total number of IPv4 ACLs. The percentage is [STRING]. |
|
Variable fields |
$1: Percentage of remaining IPv4 ACLs against the total IPv4 ACLs on the card. |
|
Severity level |
4 |
|
Example |
%Mar 15 00:06:06:766 2020 H3C DIPOE/4/DIAG: -MDC=1-Slot=4; The number of remaining IPv4 ACLs dropped below 20 percent of the total number of IPv4 ACLs. The percentage is 18%. |
|
Explanation |
The percentage of remaining IPv4 ACLs against the total IPv4 ACLs on the card reached 18%, which dropped below 20%. |
|
Recommended action |
Verify the services that consume a large number of IPv4 ACLs. |
IPOE_IPV6_HTTP_ATTACK_EXCEED_ERROR
|
Message text |
The number of anti-HTTP attack IPv6 ACLs exceeded 30 percent of the total number of IPv6 ACLs. The percentage is [STRING]. |
|
Variable fields |
$1: Percentage of IPv6 ACLs for HTTP attack defense against the total IPv6 ACLs on the card. |
|
Severity level |
4 |
|
Example |
%Mar 15 01:18:25:071 2020 H3C DIPOE/4/DIAG: -MDC=1-Slot=4; The number of anti-HTTP attack IPv6 ACLs exceeded 30 percent of the total number of IPv6 ACLs. The percentage is 31%. |
|
Explanation |
The percentage of IPv6 ACLs for HTTP attack defense against the total IPv6 ACLs on the card reached 31%, which exceeded 30%. |
|
Recommended action |
Execute the display ip subscriber http-defense attack ip [ slot slotnum ] command to view HTTP attack statistics entries. |
IPOE_IPV6_REMAIN_ACL_BELOW_ERROR
|
Message text |
The number of remaining IPv6 ACLs dropped below 20 percent of the total number of IPv6 ACLs. The percentage is [STRING]. |
|
Variable fields |
$1: Percentage of remaining IPv6 ACLs against the total IPv6 ACLs on the card. |
|
Severity level |
4 |
|
Example |
%Mar 15 00:06:06:766 2020 H3C DIPOE/4/DIAG: -MDC=1-Slot=4; The number of remaining IPv6 ACLs dropped below 20 percent of the total number of IPv6 ACLs. The percentage is 18%. |
|
Explanation |
The percentage of remaining IPv6 ACLs against the total IPv6 ACLs on the card reached 18%, which dropped below 20%. |
|
Recommended action |
Verify the services that consume a large number of IPv6 ACLs. |
IPoE_USERVLAN_CONFLICT
|
Message text |
The [STRING] configuration conflicts with user-vlan configuration. To avoid conflicts, do not configure both features on interface [STRING]. |
|
Variable fields |
$1: Configuration name. Options include: · ip subscriber l2vpn-leased—IPoE L2VPN-leased user. · ip subscriber routed enable—IPoE in Layer 3 access mode. $2: Subinterface name. |
|
Severity level |
4 |
|
Example |
DIPOE/4/IPOE_USERVLAN_CONFLICT: -MDC=1-Slot=4; The ip subscriber routed enable configuration conflicts with user-vlan configuration. To avoid conflicts, do not configure both features on interface Route-Aggregation1.2. |
|
Explanation |
A conflict exists when user VLAN termination is configured on a subinterface together with one of the following features: · IPoE L2VPN-leased user (ip subscriber l2vpn-leased). · IPoE in Layer 3 access mode (ip subscriber routed enable). |
|
Recommended action |
1. Execute the display this command in subinterface view to identify whether user VLAN termination is configured together with IPoE L2VPN-leased user or IPoE in Layer 3 access mode. If they are both configured, delete one configuration by using the undo form of the corresponding command. 2. If the problem persists, contact Technical Support. |
L2MC messages
This section contains Layer 2 multicast messages.
L2MC_CFD_NOTSPT
|
Message text |
Interface [STRING] does not support CFD. Please check your configuration. |
|
Variable fields |
$1: Interface number. |
|
Severity level |
6 |
|
Example |
L2MC/6/L2MC_CFD_NOTSPT: -MDC=1-Slot=3; Interface GigabitEthernet3/1/1.1 does not support CFD. Please check your configuration. |
|
Explanation |
The interface does not support CFD. |
|
Recommended action |
Do not configure CFD on the interface. |
L3 messages
This section contains Layer 3 messages.
BIER_TNLDIP_NORES
|
Message text |
No enough bier tunnel dip index resource |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/BIER_TNL_DIP_NORES: -MDC=1-Slot=3; No enough bier tunnel dip index resource |
|
Explanation |
BIER tunnel index resources are insufficient. |
|
Recommended action |
1. Check the environment and roll back unused configuration. 2. If the issue persists, contact Technical Support. |
STATIS_NORES
|
Message text |
Operation failed on [string] because of insufficient resources. |
|
Variable fields |
$1: Interface number obtained based on the interface index. |
|
Severity level |
2 |
|
Example |
L3/2/STATIS_NORES: -MDC=1-Slot=2; Operation failed on Ten-GigabitEthernet3/0/1.1 because of insufficient resources. |
|
Explanation |
The device failed to enable statistics counting for IPv4 and IPv6 packets on the interface because this interface does not have enough token bucket resources for incoming and outgoing packets. |
|
Recommended action |
Release token bucket resources on the interface. |
IFINDEX_STATIS_NORES
|
Message text |
Operation failed on [string] because of insufficient resources. |
|
Variable fields |
$1: Interface index. |
|
Severity level |
2 |
|
Example |
L3/2/IFINDEX_STATIS_NORES: -MDC=1-Slot=2; Operation failed on 9728 because of insufficient resources. |
|
Explanation |
The device failed to enable statistics counting for IPv4 and IPv6 packets on the interface because this interface does not have enough token bucket resources for incoming and outgoing packets. |
|
Recommended action |
Release token bucket resources on the interface. |
STATIS_CONF_CONFLICT
|
Message text |
The operation is not supported because configuration conflict on [string]. |
|
Variable fields |
$1: Interface number obtained based on the interface index. |
|
Severity level |
2 |
|
Example |
L3/2/STATIS_CONF_CONFLICT: -MDC=1-Slot=2; The operation is not supported because configuration conflict on Ten-GigabitEthernet3/0/1.1. |
|
Explanation |
The device failed to enable statistics counting for IPv4 and IPv6 packets on an interface because of the configuration conflict. |
|
Recommended action |
Examine whether the following configurations exist on the interface: · An L2VPN-leased user is configured on the interface. · The VLAN to which the interface belongs is enabled with packet statistics for Ethernet service instances of the VLAN. |
INFINDEX_STATIS_CONFLICT
|
Message text |
The operation is not supported because configuration conflict on [string]. |
|
Variable fields |
$1: Interface index. |
|
Severity level |
2 |
|
Example |
L3/2/INFINDEX_STATIS_CONFLICT: -MDC=1-Slot=2; The operation is not supported because configuration conflict on 9728. |
|
Explanation |
The device failed to enable statistics counting for IPv4 and IPv6 packets on an interface because of the configuration conflict. |
|
Recommended action |
Examine whether the following configurations exist on the interface: · An L2VPN-leased user is configured on the interface. · The VLAN to which the interface belongs is enabled with packet statistics for Ethernet service instances of the VLAN. |
ARPINDEX_NORES
|
Message text |
Not enough ARP index resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/23.8 ARPINDEX_NORES: -MDC=1; Not enough ARP index resource. |
|
Explanation |
The device failed to learn new ARP or ND entries because of insufficient ARP index resources. |
|
Recommended action |
Contact Technical Support. |
NEXTHOP_NORES
|
Message text |
Not enough NextHop resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/NEXTHOP_NORES: -MDC=1-Slot=3; Not enough NextHop resource. |
|
Explanation |
The card failed to learn new ARP or ND entries or unequal cost routes because of insufficient next hop resources. Traffic forwarding failures might occur. |
|
Recommended action |
Contact Technical Support. |
V4PREFIX_NORES
|
Message text |
Not enough IPv4 prefix resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/V4PREFIX_NORES: -MDC=1-Slot=3; Not enough IPv4 prefix resource. |
|
Explanation |
The card failed to learn new IPv4 routes because of insufficient IPv4 prefix resources. |
|
Recommended action |
Contact Technical Support. |
V6PREFIX_NORES
|
Message text |
Not enough IPv6 prefix resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/V6PREFIX_NORES: -MDC=1-Slot=3; Not enough IPv6 prefix resource. |
|
Explanation |
The card failed to learn new IPv6 routes because of insufficient IPv6 prefix resources. |
|
Recommended action |
Contact Technical Support. |
ARP_ATTACK
|
Message text |
Arp Attack!!! |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/ARP_ATTACK: -MDC=1-Slot=3; Arp Attack!!! |
|
Explanation |
An ARP attack was detected. |
|
Recommended action |
Contact Technical Support. |
ICMP_ATTACK
|
Message text |
ICMP Attack! |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/ICMP_ATTACK: -MDC=1-Slot=3; ICMP Attack! |
|
Explanation |
An ICMP attack was detected. |
|
Recommended action |
Contact Technical Support. |
IPV4_ACL_EXCEED
|
Message text |
The IPv4 ACL resource usage exceeds 80%. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IPV4/4/IPV4_ACL_EXCEED: -MDC=1-Slot=3; The IPv4 ACL resource usage exceeds 80%. |
|
Explanation |
The usage of IPv4 ACL resources exceeded 80%. In this case, the device cannot assign DHCP flood attack prevention entries. |
|
Recommended action |
Execute the display qos-acl resource command in system view to examine the ACL resource usage for the card, and then release some IPv4 ACL resources. |
IPV6_ACL_EXCEED
|
Message text |
The IPv6 ACL resource usage exceeds 80%. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IPV4/4/IPV6_ACL_EXCEED: -MDC=1-Slot=3; The IPv6 ACL resource usage exceeds 80%. |
|
Explanation |
The usage of IPv6 ACL resources exceeded 80%. In this case, the device cannot assign DHCPv6 flood attack prevention entries. |
|
Recommended action |
Execute the display qos-acl resource command in system view to examine the ACL resource usage for the card, and then release some IPv6 ACL resources. |
IPV4_ACL_NORES
|
Message text |
Not enough IPv4 ACL resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IPV4/4/IPV4_ACL_NORES: -MDC=1-Slot=3; Not enough IPv4 ACL resources. |
|
Explanation |
· This message is sent when ACL hardware entries fail to be deployed due to insufficient IPv4 ACL resources. GTSM cannot work in this case. · After TCP SYN flood attack prevention is enabled, the system deploys ACL hardware entries when an attack occurs. This message is sent when ACL hardware entries fail to be deployed due to insufficient IPv4 ACL resources. TCP SYN flood attack prevention cannot work in this case. |
|
Recommended action |
1. Execute the display qos-acl resource slot slot-number command in system view to view ACL resource usage. 2. Collect ACL resource usage information and contact Technical Support. |
IPV6_ACL_NORES
|
Message text |
Not enough IPv6 ACL resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IPV4/4/IPV6_ACL_NORES: -MDC=1-Slot=3; Not enough IPv6 ACL resources. |
|
Explanation |
· This message is sent when ACL hardware entries fail to be deployed due to insufficient IPv6 ACL resources. GTSM cannot work in this case. · After TCP SYN flood attack prevention is enabled, the system deploys ACL hardware entries when an attack occurs. This message is sent when ACL hardware entries fail to be deployed due to insufficient IPv6 ACL resources. TCP SYN flood attack prevention cannot work in this case. |
|
Recommended action |
1. Execute the display qos-acl resource slot slot-number command in system view to view ACL resource usage. 2. Collect ACL resource usage information and contact Technical Support. |
MTU_NORES
|
Message text |
Insufficient system resources! |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
IPV4/3/MTU_NORES: -MDC=1-Slot=3; Insufficient system resources! |
|
Explanation |
MTU index resources were insufficient. The system restored the MTU setting to the default. |
|
Recommended action |
Contact Technical Support. |
P2C_CONF_CONFLICT
|
Message text |
The operation is not supported. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3/4/P2C_CONF_CONFLICT: -MDC=1-Slot=3; The operation is not supported. |
|
Explanation |
The device does not support the ipv6 option source-route enable command. |
|
Recommended action |
Do not execute the ipv6 option source-route enable command on the device. |
STATIS_NORES
|
Message text |
Failed to enable packet drop statistics collection on interface [UINT32] because of insufficient resources. |
|
Variable fields |
$1: Interface index. |
|
Severity level |
4 |
|
Example |
L3/4/STATIS_NORES: -MDC=1-Slot=3; Failed to enable packet drop statistics collection on interface 1153 because of insufficient resources. |
|
Explanation |
After you enable SAVA, the system notifies the QACL module of assigning TB counter resources. This message is generated when the TB counter resources are insufficient. |
|
Recommended action |
Contact Technical Support. |
L3MC messages
This section contains Layer 3 multicast messages.
IPV4_HW_NORES
|
Message text |
No enough resource! |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
L3MC/3/IPV4_HW_NORES: -MDC=1-Slot=4; No enough resource! |
|
Explanation |
The operation failed because not enough resources were available. For example, no more multicast forwarding entries can be created if the existing hardware resources are insufficient. |
|
Recommended action |
1. Execute the display hardware internal l3mc slot slot-number global command in probe view and collect the resource usage statistics of the card. 2. Contact Technical Support. |
IPV4_ACL_NORES
|
Message text |
Not enough ACL resource |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3MC/4/IPV4_ACL_NORES: -MDC=1-Slot=4; Not enough ACL resource |
|
Explanation |
With the interface-based IGMP suppression enabled, the device deploys ACLs when detecting IGMP attacks. This message is sent when the hardware resources are not enough to deploy ACLs. |
|
Recommended action |
1. Execute the display qos-acl resource slot slot-number command in system view and collect the resource usage statistics of the card. 2. Contact Technical Support. |
IPV4_IC_IPV6_ACL_NORES
|
Message text |
This board no enough acl resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3MC/4/IPV4_IC_IPV6_ACL_NORES: -MDC=1-Slot=4; This board no enough acl resource. |
|
Explanation |
ACL resources on the card are insufficient. |
|
Recommended action |
1. Execute the display qos-acl resource slot slot-number command in system view and collect the resource usage statistics of the card. 2. Contact Technical Support. |
BRAS_HW_NORES
|
Message text |
No enough resource! |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
L3MC/3/BRAS_HW_NORES: -MDC=1; Slot=4; No enough resource! |
|
Explanation |
IGMP attack defense could not take effect on the IPoE user access interface because not enough ACL resources were available on the card. |
|
Recommended action |
1. Execute the display qos-acl resource slot slot-number command and collect the ACL resource usage statistics of the card. 2. Contact Technical Support. |
IPV6_HW_NORES
|
Message text |
No enough resource! |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
L3MC/3/IPV6_HW_NORES: -MDC=1-Slot=4; No enough resource! |
|
Explanation |
The operation failed because not enough resources were available. For example, no more multicast forwarding entries can be created if the existing hardware resources are insufficient. |
|
Recommended action |
1. Execute the display hardware internal l3mc slot slot-number global command in probe view and collect the resource usage statistics of the card. 2. Contact Technical Support. |
IPV6_ACL_NORES
|
Message text |
Not enough IPv6 ACL resources |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
L3MC/4/IPV6_ACL_NORES: -MDC=1-Slot=4; Not enough IPv6 ACL resources |
|
Explanation |
With the interface-based MLD suppression enabled, the device deploys ACLs when detecting MLD attacks. This message is sent when the hardware resources are not enough to deploy ACLs. |
|
Recommended action |
1. Execute the display qos-acl resource slot slot-number command in system view and collect the resource usage statistics of the card. 2. Contact Technical Support. |
L3MC_IPV4_ACL_NORES_INFO
|
Message text |
No enough ACL resource , P1=[UINT32]. |
|
Variable fields |
$1: Interface index. |
|
Severity level |
3 |
|
Example |
L3MC/3/L3MC-IPV4_ACL_NORES_INFO: -MDC=1-Slot=4; No enough ACL resource, p1=1153. |
|
Explanation |
ACL resources deployed by the device are insufficient. |
|
Recommended action |
1. Execute the display qos-acl resource slot slot-number command in system view and collect the resource usage statistics of the card. 2. Contact Technical Support. |
MVPN_MTUNNEL_NORES
|
Message text |
MtunnelCreate No enough resource! |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
L3MC/3/MVPN_MTUNNEL_NORES: -MDC=1; MtunnelCreate No enough resource! |
|
Explanation |
The device failed to create an Mtunnel interface because the hardware resources used by the multicast VPN have reached the upper limit. |
|
Recommended action |
No action is required. |
SRPM_NORES
|
Message text |
This module does not support SRPM. Please check your configuration. |
|
Variable fields |
N/A |
|
Severity level |
2 |
|
Example |
L3MC/2/SRPM_NORES: -MDC=1; This module does not support SRPM. Please check your configuration. |
|
Explanation |
This message is generated when a new member port is added to the Layer 3 aggregate group after you enable SRPM on a Layer 3 aggregate interface or a Layer 3 aggregate subinterface. |
|
Recommended action |
After you enable SRPM on a Layer 3 aggregate interface or a Layer 3 aggregate subinterface, do not add a new member to the Layer 3 aggregate group. If you add a new member to the aggregate group, networking performance measurement errors might occur. |
LIF messages
This section contains LIF messages.
OUTLIFID_NORES
|
Message text |
Not enough OutlifID resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
LIF/4/OUTLIFID_NORES: -MDC=1-Slot=3; Not enough OutlifID resource. |
|
Explanation |
The card failed to learn new ARP entries, ND entries, or non-host routes because of insufficient OutlifID resources. Traffic forwarding failures might occur. |
|
Recommended action |
Contact Technical Support. |
HW_NORES
|
Message text |
Not enough resources for [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
6 |
|
Example |
LIF/6/HW_NORES: -MDC=1-Slot=5; Not enough resources for Route-Aggregation1.1. |
|
Explanation |
Hardware resources were insufficient for enabling QinQ termination on the interface. |
|
Recommended action |
1. View the QinQ termination configurations by using the display current-configuration | include second-dot1q command. 2. Delete the unused configurations by using the undo vlan-type dot1q vid second-dot1q command. 3. If the problem persists, contact Technical Support. |
SUB_SPT_VID
|
Message text |
Subinterface [STRING] only supports VLAN termination by commands starting with vlan-type dot1q vid [INT32]. |
|
Variable fields |
$1: Subinterface name. $2: VLAN ID. |
|
Severity level |
5 |
|
Example |
LIF/5/SUB_SPT_VID: -MDC=1-Slot=1; Subinterface Ten-GigabitEthernet3/0/1.2048 only supports VLAN termination by commands starting with vlan-type dot1q vid 2048. |
|
Explanation |
A subinterface only supports terminating packets with the Layer 1 VLAN ID as the subinterface number. |
|
Recommended action |
When configuring dot1q termination or QinQ termination on a subinterface, make sure the Layer 1 VLAN ID to be terminated is the same as the subinterface number. |
PKTCNT_NOTSPT
|
Message text |
This board does not support traffic statistics on the VLAN interface. |
|
Variable fields |
N/A |
|
Severity level |
2 |
|
Example |
LIF/2/IF: -MDC=1-Slot=3; This board does not support traffic statistics on the VLAN interface. |
|
Explanation |
An interface on a board does not support traffic statistics for the VLAN interface of a VLAN to which the interface belongs. |
|
Recommended action |
No action is required. |
IF_RAGG_FAILED
|
Message text |
Failed to assign the interface to the link aggregation group, because the corresponding aggregate interface has subinterfaces with some VLAN termination configuration not supported by the board of this interface. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
LIF/3/IF_RAGG_FAILED: -MDC=1; Failed to assign the interface to the link aggregation group, because the corresponding aggregate interface has subinterfaces with some VLAN termination configuration not supported by the board of this interface. |
|
Explanation |
Failed to assign the Ethernet interface to the link aggregation group, because the corresponding aggregate interface has subinterfaces with some VLAN termination configuration not supported by the card of this Ethernet interface. |
|
Recommended action |
Contact Technical Support. |
MAC_INCORRECT
|
Message text |
Incorrect MAC address. The MAC address of [STRING] must range from [UCHAR] [UCHAR] -[UCHAR] [UCHAR]- [UCHAR][UCHAR] to [UCHAR] [UCHAR] -[UCHAR] [UCHAR]- [UCHAR][UCHAR]. Or Incorrect MAC address. The MAC address of the interface must range from [UCHAR] [UCHAR] -[UCHAR] [UCHAR]- [UCHAR][UCHAR] to [UCHAR] [UCHAR] -[UCHAR] [UCHAR]- [UCHAR][UCHAR]. |
|
Variable fields |
$1: Interface name. $2-$7: Configured start MAC addresses. $8-$13: Configured end MAC addresses. |
|
Severity level |
3 |
|
Example |
LIF/3/MAC_INCORRECT: -MDC=1-Slot=3; Incorrect MAC address. The MAC address of Ten-GigabitEthernet3/0/1 must range from 0000-1111-2222 to 1111-2222-3333 Or LIF/3/MAC_INCORRECT: -MDC=1-Slot=3; Incorrect MAC address. The MAC address of the interface must range from 0000-1111-2222 to 1111-2222-3333 |
|
Explanation |
In BRAS mode, make sure the configured MAC address is in the specified range. |
|
Recommended action |
Configure a MAC address in the specified range. |
QINQ_SUBVLAN_STARTERR
|
Message text |
Subinterface [STRING] only supports VLAN termination by commands starting with vlan-type dot1q vid [INT32]. |
|
Variable fields |
$1: Subinterface name. $2: VLAN ID. |
|
Severity level |
5 |
|
Example |
LIF/5/QINQ_SUBVLAN_STARTERR: -MDC=1-Slot=3; Subinterface Ten-GigabitEthernet3/0/1.2048 only supports VLAN termination by commands starting with vlan-type dot1q vid 2048. |
|
Explanation |
A subinterface only supports terminating packets with the Layer 1 VLAN ID as the subinterface number. |
|
Recommended action |
When configuring dot1q termination or QinQ termination on a subinterface, make sure the Layer 1 VLAN ID to be terminated is the same as the subinterface number. |
QINQ_SUBVLAN_CFGERR
|
Message text |
Subinterface [STRING] only supports VLAN termination by the vlan-type dot1q vid [INT32] command. |
|
Variable fields |
$1: Subinterface name. $2: VLAN ID. |
|
Severity level |
5 |
|
Example |
LIF/5/QINQ_SUBVLAN_CFGERR: -MDC=1; Subinterface VE-L3VPN1.1 only supports VLAN termination by the vlan-type dot1q vid 1 command. |
|
Explanation |
The specified L3VE subinterface supports only dot1q termination, and can terminate only packets with the Layer 1 VLAN ID as the subinterface number. |
|
Recommended action |
When configuring dot1q termination on a subinterface, make sure the Layer 1 VLAN ID to be terminated is the same as the subinterface number. |
QINQ_USERVLAN_NORES
|
Message text |
Not enough resources for user-vlan QINQ termination on [STRING]. Or Not enough resources for user-vlan QINQ termination on [INT32]. |
|
Variable fields |
$1: Subinterface name. $2: Interface index. |
|
Severity level |
4 |
|
Example |
LIF/4/QINQ_USERVLAN_NORES: -MDC=1-Slot=5; Not enough resources for user-vlan QINQ termination on Route-Aggregation1.1. |
|
Explanation |
QinQ termination configured by using the user-vlan dot1q vid second-dot1q command failed to be enabled on an interface because of insufficient hardware resources. |
|
Recommended action |
1. When resources are insufficient for configure user VLAN termination on a subinterface, use the display current-configuration | include second-dot1q command to view the current user VLAN QinQ termination configuration. Use the undo user-vlan dot1q vid second-dot1q command to remove the current configuration, and then remove configurations that are not used currently to release resources. 2. When resources are insufficient for adding an interface to an aggregate interface, use the display link-aggregation verbose command to view the aggregate interface configuration. Use the undo port link-aggregation group command to remove the current configuration, and then remove member ports that are not used currently from the aggregation group to release resources. Alternatively, you can use step 1 to view and delete configurations that are not used currently on the subinterface to release resources. 3. Contact Technical Support. |
QINQ_VLAN_NORES
|
Message text |
Not enough resources for QinQ termination. |
|
Variable fields |
N/A |
|
Severity level |
2 |
|
Example |
LIF/2/QINQ_VLAN_NORES: -MDC=1-Slot=3; Not enough resources for QinQ termination. |
|
Explanation |
The card does not have enough hardware resources for user VLAN QinQ termination probably due to one of the following reasons: · A large number of IPoE or PPPoE users have come online. · A majority of interfaces on the card are used for user VLAN QinQ termination. |
|
Recommended action |
1. If Layer 3 aggregate subinterfaces on the card are used for user VLAN QinQ termination, alleviate the card load by reducing the number of member ports that join aggregation groups. 2. If the problem persists, contact Technical Support. |
QINQ_USERVLAN_CHK
|
Message text |
The user-vlan configuration conflicts with [STRING] configuration. To avoid conflicts, do not configure both features on interface [STRING]. |
|
Variable fields |
$1: Feature configuration: · ip subscriber l2vpn-leased—IPoE L2VPN-leased user configuration. · ip subscriber routed enable—IPoE configuration in Layer 3 access mode. · portal—Portal authentication configuration. $2: Subinterface name. |
|
Severity level |
4 |
|
Example |
LIF/4/QINQ_USERVLAN_CHK: -MDC=1-Slot=4; The user-vlan configuration conflicts with portal configuration. To avoid conflicts, do not configure both features on interface Route-Aggregation1.2. |
|
Explanation |
User VLAN termination conflicts with one of the following configurations on the subinterface: · Portal authentication configuration. · IPoE L2VPN-leased user configuration (ip subscriber l2vpn-leased). · IPoE configuration in Layer 3 access mode (ip subscriber routed enable). |
|
Recommended action |
1. Execute the display this command in subinterface view to check for conflicting configurations. User VLAN termination cannot be configured with one of the following features on the same interface: ¡ IPoE L2VPN-leased user configuration (portal [ ipv6 ] enable). ¡ IPoE configuration in Layer 3 access mode (ip subscriber l2vpn-leased). ¡ Portal authentication configuration (ip subscriber routed enable). 2. Remove user VLAN termination configuration from the subinterface or use the undo form of the following commands to remove IPoE or portal configuration from the subinterface. ¡ portal [ ipv6 ] enable ¡ ip subscriber l2vpn-leased ¡ ip subscriber routed enable 3. If the problem persists, contact Technical Support. |
QINQ_SUBVLAN_NOTSPT
|
Message text |
Subinterface [STRING] not supports QINQ VLAN termination. |
|
Variable fields |
$1: Subinterface name. |
|
Severity level |
5 |
|
Example |
LIF/5/QINQ_SUBVLAN_NOTSPT: -MDC=1-Slot=3; Subinterface Ten-GigabitEthernet3/0/1.2048 not supports QINQ VLAN termination. |
|
Explanation |
The specified VE-L3VPN or VE-L2VPN subinterface does not support QinQ termination. |
|
Recommended action |
Do not configure QinQ termination on a VE-L3VPN or VE-L2VPN subinterface. |
QINQ_UNTAG_DEFAULT_NOTSPT
|
Message text |
The board in slot [UINT16] doesn't support untagged or default termination. Or The board doesn't support untagged or default termination. |
|
Variable fields |
$1: Slot number. |
|
Severity level |
3 |
|
Example |
LIF/3/QINQ_UNTAG_DEFAULT_NOTSPT: -MDC=1-Slot=3; The board in slot 3 doesn't support untagged or default termination. |
|
Explanation |
¡ a member port does not support untagged termination or default termination. The system will prompt that the card does not support untagged termination or default termination. |
|
Recommended action |
1. Do not configure untagged termination or default termination on a subinterface. |
MAC messages
This section contains MAC messages.
MAC_CAPACITY_LIMIT
|
Message text |
The number of MAC address entries exceeded the maximum number [UNIT32]. |
|
Variable fields |
$1: Maximum number of MAC address entries on the LPU. |
|
Severity level |
5 |
|
Example |
MAC/5/MAC_CAPACITY_LIMIT: -MDC=1-Slot=3; The number of MAC address entries exceeded the maximum number 1048576. |
|
Explanation |
The number of MAC address entries on the LPU exceeded the supported maximum number. |
|
Recommended action |
No action is required. |
MPLS messages
This section contains MPLS messages.
LABEL_NORES
|
Message text |
No enough resource |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
MPLS/3/LABEL_NORES: -MDC=1-Slot=4; No enough resource |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the tunnel label resources are insufficient, the system cannot create an MPLS tunnel. |
|
Recommended action |
Contact Technical Support. |
TNL_TBORPROFILE_NORES
|
Message text |
Hardware resources not enough. The rate limits set by QoS rate limit or MPLS TE traffic policing for [STRING] do not take effect. |
|
Variable fields |
$1: Name of MPLS TE tunnel. |
|
Severity level |
4 |
|
Example |
MPLS/4/TNL_TBORPROFILE_NORES: -MDC=1-Slot=5; Hardware resources not enough. The rate limits set by QoS rate limit or MPLS TE traffic policing for Tunnel256 do not take effect. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the Tbindex or Profile resources are insufficient on a card, rate limit settings cannot take effect on the TE tunnels on the card. |
|
Recommended action |
Contact Technical Support. |
P2MPTE_TUNNEL_NORES
|
Message text |
Not enough hardware resources for P2MP-TE tunnel. |
|
Variable fields |
N/A |
|
Severity level |
2 |
|
Example |
MPLS/2/P2MPTE_TUNNEL_NORES: -MDC=1-Slot=5; Not enough hardware resources for P2MP-TE tunnel. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the tunnel resources are insufficient, the system cannot create an MPLS tunnel. |
|
Recommended action |
Contact Technical Support. |
OUTLIF_NORES
|
Message text |
Not enough outlif resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/OUTLIF_NORES: -MDC=1-Slot=5; Not enough outlif resource. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the outlif resources are insufficient on a card, MPLS tunnels on the card cannot forward traffic. |
|
Recommended action |
Contact Technical Support. |
REMOTEMAC_NORES
|
Message text |
Not enough remoteMac resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/REMOTEMAC_NORES: -MDC=1-Slot=5; Not enough remoteMac resource. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the remoteMac resources are insufficient, FRR does not take effect. |
|
Recommended action |
Contact Technical Support. |
CFDORACSTAT_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
VPLS/3/CFDORACSTAT_NORES: -MDC=1-Slot=2; No enough resource. |
|
Explanation |
Hardware resources were insufficient for enabling CFD or packet statistics on the AC. In this case, packet forwarding is normal but packet statistics is disabled. |
|
Recommended action |
Contact Technical Support. |
CFDORACSTAT_CONFLICTS_INTF
|
Message text |
Operation conflicts with the configuration on this interface. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
VPLS/3/CFDORACSTAT_CONFLICTS_INTF: -MDC=1-Slot=5; Operation conflicts with the configuration on this interface. |
|
Explanation |
This message is sent if you enable CFD or packet statistics for an AC (interface) where subinterface statistics is configured. |
|
Recommended action |
Delete the configuration not needed. |
CFDORAC_STAT_NORES
|
Message text |
No enough resource. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
VLL/3/CFDORAC_STAT_NORES: -MDC=1-Slot=2; No enough resource. |
|
Explanation |
Hardware resources were insufficient for enabling packet statistics on the AC. In this case, packet forwarding is normal but packet statistics is disabled. |
|
Recommended action |
Contact Technical Support. |
CFDORAC_CONFLICTS_INTFSTAT
|
Message text |
Operation conflicts with the configuration on this interface. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
VLL/3/CFDORAC_CONFLICTS_INTFSTAT: -MDC=1-Slot=5; Operation conflicts with the configuration on this interface. |
|
Explanation |
This message is sent if you enable CFD or packet statistics for an AC (interface) where subinterface statistics is configured. |
|
Recommended action |
Delete the configuration not needed. |
NDSUPR_DUALFORWARD_NOTSPT
|
Message text |
In standard mode, the card does not support vpws nd suppression or dual-forward. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VLL/4/NDSUPR_DUALFORWARD_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpws nd suppression or dual-forward. |
|
Explanation |
The standard mode does not support ND suppression or dual-forward for VPWS. |
|
Recommended action |
Contact Technical Support. |
ARPSUPR_DUALFORWARD_NOTSPT
|
Message text |
In standard mode, the card does not support vpws arp suppression or dual-forward. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VLL/4/ARPSUPR_DUALFORWARD_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpws arp suppression or dual-forward. |
|
Explanation |
The standard mode does not support ARP suppression or dual-forward for VPWS. |
|
Recommended action |
Contact Technical Support. |
DOUBLEBYPASS_NOTSPT
|
Message text |
In standard mode, the card does not support vpws double bypass. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VLL/4/DOUBLEBYPASS_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpws double bypass. |
|
Explanation |
The standard mode does not support dual bypass PWs for VPWS. |
|
Recommended action |
Contact Technical Support. |
EVPN_MULTIHOME_NOTSPT
|
Message text |
In standard mode, the card does not support evpn vpws multihoming. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VLL/4/EVPN_MULTIHOME_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support evpn vpws multihoming. |
|
Explanation |
The standard mode does not support EVPN VPWS dual homing. |
|
Recommended action |
Contact Technical Support. |
AC_REACH_MAXNUM
|
Message text |
The number of ACs or PWs in the VSI has reached the limit. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VPLS/4/AC_REACH_MAXNUM: -MDC=1; The number of ACs or PWs in the VSI has reached the limit. |
|
Explanation |
This message is sent when the number of ACs or PWs configured in a VSI exceeds the maximum allowed. |
|
Recommended action |
Contact Technical Support. |
PW_REACH_MAXNUM
|
Message text |
The number of ACs or PWs in the VSI has reached the limit. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VPLS/4/PW_REACH_MAXNUM: -MDC=1; The number of ACs or PWs in the VSI has reached the limit. |
|
Explanation |
This message is sent when the number of ACs or PWs configured in a VSI exceeds the maximum allowed. |
|
Recommended action |
Contact Technical Support. |
EVPNORSRV6_NOTSPT
|
Message text |
In standard mode, the card does not support evpn vpls or srv6. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VPLS/4/EVPNORSRV6_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support evpn vpls or srv6. |
|
Explanation |
The standard mode does not support EVPN VPLS or EVPN VPLS over SRv6. |
|
Recommended action |
Contact Technical Support. |
ARPSUP_NOTSPT
|
Message text |
In standard mode, the card does not support vpls arp suppression. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VPLS/4/ARPSUP_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpls arp suppression. |
|
Explanation |
The standard mode does not support VPLS ARP suppression. |
|
Recommended action |
Contact Technical Support. |
ONEHUB_SUPPORT
|
Message text |
The device supports only one HUB. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
VPLS/3/ONEHUB_SUPPORT: -MDC=1-Slot=5; The device supports only one HUB. |
|
Explanation |
In a hub-spoke network, each VPLS instance supports only one hub. |
|
Recommended action |
Make sure a VPLS instance has only one hub configured. |
LEAFSTAT_NORES
|
Message text |
No enough leaf stat index resource. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/LEAFSTAT_NORES: -MDC=1-Slot=4; No enough leaf stat index resource. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the leaf statistics counter resources for PWs are insufficient, the leaf statistics feature does not take effect. |
|
Recommended action |
Contact Technical Support. |
PW_REACH_MAXNUM
|
Message text |
Tnl num of vsi is max, num = [INT32]. |
|
Variable fields |
$1: Maximum number of VXLAN tunnels supported in the VSI. |
|
Severity level |
3 |
|
Example |
VPLS/3/PW_REACH_MAXNUM: -MDC=1-Slot=5; Tnl num of vsi is max, num = 128. |
|
Explanation |
The maximum number of VXLAN tunnels that can be configured in a VSI is 128. |
|
Recommended action |
Make sure the number of VXLAN tunnels configured in the VSI does not exceed the maximum allowed. |
PRIVATESID_NORES
|
Message text |
Not enough Private-SID resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/PRIVATESID_NORES: -MDC=1-Slot=4; Not enough Private-SID resources. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the private-SID resources on a card are insufficient, the card cannot use the EVPN VPWS/VPLS over SRv6 service or the MPLS/EVPN L3VPN over SRv6 service. |
|
Recommended action |
Contact Technical Support. |
DT2_NORES
|
Message text |
Not enough DT2 resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/DT2_NORES: -MDC=1-Slot=4; Not enough DT2 resources. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the DT2 resources on a card are insufficient, the card cannot use the EVPN VPWS/VPLS over SRv6 service. |
|
Recommended action |
Contact Technical Support. |
SRV6_POLICYSTAT_NORES
|
Message text |
Not enough resources for SRv6-TE policy statistics. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/SRV6_POLICYSTAT_NORES: -MDC=1-Slot=2; Not enough resources for SRv6-TE policy statistics. |
|
Explanation |
Statistical resources were insufficient for completing an operation. For example, when the SRv6-TE policy statistical resources on a card are insufficient, the card cannot collect SRv6-TE policy statistics but it can use the SRv6 tunnel. |
|
Recommended action |
Contact Technical Support. |
SRV6_TNLINLIF_NORES
|
Message text |
Not enough tunnel INLIF resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/SRV6_TNLINLIF_NORES: -MDC=1-Slot=2; Not enough tunnel INLIF resources. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the INLIF resources on a card are insufficient, the card cannot create an SRv6 tunnel. |
|
Recommended action |
Contact Technical Support. |
SRV6_SRLIST_NORES
|
Message text |
Not enough IPv6_SR_List resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/SRV6_SRLIST_NORES: -MDC=1-Slot=2; Not enough IPv6_SR_List resources. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the IPV6_SR_LIST resources on a card are insufficient, the card cannot create an SRv6 tunnel. |
|
Recommended action |
Contact Technical Support. |
SRV6_CBTSSTAT_NORES
|
Message text |
Not enough resources for SRv6-TE Policy service class-based statistics. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/SRV6_CBTSSTAT_NORES: -MDC=1-Slot=2; Not enough resources for SRv6-TE Policy service class-based statistics. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the CBTS statistical resources for SRv6-TE policies on a card are insufficient, the card cannot perform CBTS-based traffic statistics for the SRv6 tunnels on the card. |
|
Recommended action |
Contact Technical Support. |
SRV6_TBORPROFILE_NORES
|
Message text |
Hardware resources are not enough. The rate limit set for the SRv6-TE policy does not take effect. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/SRV6_TBORPROFILE_NORES:-MDC=1;Hardware resources are not enough. The rate limit set for the SRv6-TE policy does not take effect. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the Tbindex or Profile resources on a card are insufficient, rate limit settings cannot take effect on the SRv6 policy tunnels. |
|
Recommended action |
Contact Technical Support. |
SRV6_NOTSPT
|
Message text |
In standard mode, the card does not support vpws srv6. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VLL/4/SRV6_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vpws srv6. |
|
Explanation |
The standard mode does not support VPWS over SRv6. |
|
Recommended action |
Contact Technical Support. |
CBTSACL_NORES
|
Message text |
Not enough acl resource to add vxlan cbts acl. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VXLAN/4/CBTSACL_NORES: -MDC=1-Slot=5; Not enough acl resource to add vxlan cbts acl. |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the CBTS ACL resources for VXLANs on a card are insufficient, the card cannot perform CBTS for VXLAN packets. |
|
Recommended action |
Contact Technical Support. |
SERVICECLASS_NOTSPT
|
Message text |
In standard mode, the card does not support vxlan config service class. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VXLAN/4/SERVICECLASS_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vxlan config service class. |
|
Explanation |
The standard mode does not support configuring service class values for VXLAN packets. |
|
Recommended action |
Contact Technical Support. |
DSCP_NOTSPT
|
Message text |
In standard mode, the card does not support vxlan config dscp. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
VXLAN/4/DSCP_NOTSPT: -MDC=1-Slot=5; In standard mode, the card does not support vxlan config dscp. |
|
Explanation |
The standard mode does not support VXLAN tunnel DSCP operations. |
|
Recommended action |
Contact Technical Support. |
MPLS_PWSTAT_NORES
|
Message text |
MPLS L2VPN does not support PW statistics. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/MPLS_PWSTAT_NOTSPT: -MDC=1; MPLS L2VPN does not support PW statistics. |
|
Explanation |
MPLS L2VPN does not support PW statistics collection. |
|
Recommended action |
Contact Technical Support. |
VP_NORES
|
Message text |
Not enough VP resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/VP_NORES: -MDC=1-Slot=4; Not enough VP resources. |
|
Explanation |
Hardware resources on the card were insufficient for completing an operation. For example, when the VP resources on a card are insufficient, the card cannot use the VPWS over MPLS/VPLS over MPLS/EVPN VPWS/VPLS over SRv6 service. |
|
Recommended action |
Contact Technical Support. |
FAST_SWITCH_NORES
|
Message text |
Not enough Fast_Switch resources |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
MPLS/4/ FAST_SWITCH_NORES: -MDC=1-Slot=2; Not enough Fast_Switch resources. |
|
Explanation |
Fast switching resources on the card were insufficient for completing an operation. For example, when the fast switching resources on a card are insufficient, the fast switching feature loses effect but the SRv6 tunnel can be used normally. |
|
Recommended action |
Contact Technical Support. |
NP messages
This section contains NP messages.
LINK_FLAP_FREQ
|
Message text |
The link of [STRING] flaps frequently. Please check the hardware link! |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
PORT/4/LINK_FLAP_FREQ: The link of Ten-GigabitEthernet 5/0/1 flaps frequently. Please check the hardware link! |
|
Explanation |
The interface goes down and comes up frequently. |
|
Recommended action |
1. Verify that the physical link is normal. 2. Verify that the peer interface is operating correctly. 3. Reset the card where the peer interface resides. 4. If the issue persists, contact Technical Support. |
NPD
This section contains NPD messages.
ECC_ERROR
|
Message text |
ECC reset-level error occurred on slot [UINT32]. Error not corrected after three fast reset actions. |
|
Variable fields |
$1: Slot number of a card. |
|
Severity level |
2 |
|
Example |
NPD/2/ECC_ERROR: -MDC=1-Slot=5; ECC reset-level error occurred on slot 5. Error not corrected after three fast reset actions. |
|
Explanation |
On the specified card, a reset-level error occurred. The error has not been corrected after three fast reset actions. |
|
Recommended action |
Replace the card. |
NPS_ECC_ERROR
|
Message text |
ECC reset-level error occurred on slot [UINT32]. |
|
Variable fields |
$1: Slot number of a card. |
|
Severity level |
2 |
|
Example |
NPD/2/NPS_ECC_ERROR: -MDC=1-Slot=5; ECC reset-level error occurred on slot 5. |
|
Explanation |
On the specified card, a reset-level error occurred. |
|
Recommended action |
Replace the card. |
MACTX_FIFO_ERR
|
Message text |
MAC TX FIFO error detected on interface. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
NPD/3/MACTX_FIFO_ERR: MAC TX FIFO error detected on interface. |
|
Explanation |
The MAC TX FIFO queue was congested on an interface. |
|
Recommended action |
Contact Technical Support. |
MACTX_FIFO_ERR
|
Message text |
MAC TX FIFO error detected on slot [UINT32]. |
|
Variable fields |
$1: Slot number of the card in the device. |
|
Severity level |
3 |
|
Example |
NPD/3/MACTX_FIFO_ERR: -MDC=1-Slot=5; MAC TX FIFO error detected on slot 5. |
|
Explanation |
The MAC TX FIFO queue was congested on the card. |
|
Recommended action |
Contact Technical Support. |
PORT messages
This section contains port messages.
TRANS_IO_FAULT
|
Message text |
[STRING]: Transceiver module has I/O errors. Please check the transceiver module. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
PORT/4/TRANS_IO_FAULT: -MDC=1-Slot=2; GigabitEthernet2/1/1: Transceiver module has I/O errors. Please check the transceiver module. |
|
Explanation |
I/O errors occurred to the transceiver module on the interface. |
|
Recommended action |
1. Identify whether the interface supports the transceiver module. ¡ If not, replace the transceiver module with a supported transceiver module. ¡ If yes, the transceiver module might have failed. Replace the transceiver module with a transceiver module that can operate correctly. 2. If the problem persists, contact Technical Support. |
QACL messages
This section contains ACL and QoS messages.
ACL_PORTAL_NORES
|
Message text |
Insufficient resources for the portal session. Some functions of the session didn't take effect. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/4/ACL_PORTAL_NORES: -MDC=1-Slot=5 Insufficient resources for the portal session. Some functions of the session didn't take effect. |
|
Explanation |
During the portal session establishment, ACL resource insufficiency caused that some functions, such as session accounting and rate limit, did not take effect. |
|
Recommended action |
1. Use the display qos-acl resource command to check the ACL resource usage on the card. Delete unnecessary ACLs to release resources. 2. If the problem persists, contact Technical Support. |
AGGPORT_CAR_NORES
|
Message text |
Due to insufficient hardware resources, the CAR action and the CBQ action applied to interface [STRING] did not work as expected. |
|
Variable fields |
$1: Layer 3 aggregate interface name. |
|
Severity level |
4 |
|
Example |
QACL/4/AGGPORT_CAR_NORES: -MDC=1-Slot=4; Due to insufficient hardware resources, the CAR action and the CBQ action applied to interface RAGG1000 did not work as expected. |
|
Explanation |
This message is generated if hardware resources are insufficient when the state of a member port of the Layer 3 aggregate interface changes between Selected and Unselected. |
|
Recommended action |
1. Reconfigure the CAR settings and CBQ settings. 2. If the problem persists, contact Technical Support. |
CHANNEL_BANDWIDTH_EXCEED
|
Message text |
The sum of channel bandwidth and network-slice bandwidth ([INT 32]) exceeds the bandwidth ([INT 32]) of interface [STRING]. |
|
Variable fields |
$1: Channel bandwidth. $2: Interface name or interface index. $3: Interface bandwidth. |
|
Severity level |
4 |
|
Example |
QACL/4/CHANNEL_BANDWIDTH_EXCEED: -MDC=1-Slot=3; The sum of channel bandwidth and network-slice bandwidth (1100000 kbps) exceeds the bandwidth (1000000 kbps) of interface GigabitEthernet 3/0/1. |
|
Explanation |
This message is generated when the sum of channel bandwidth and network slice bandwidth exceeded the interface bandwidth. |
|
Recommended action |
· Modify the channel bandwidth or network slice bandwidth. · Change the interface rate. |
CHANNEL_EXCEED_MAXIMUM
|
Message text |
The sum of channel bandwidth and network-slice bandwidth ([INT 32]) exceeds the maximum bandwidth ([INT 32]). |
|
Variable fields |
$1: Sum of the channel bandwidth and network slice bandwidth. $2: Maximum channel bandwidth and network slice bandwidth issued by the interface. $3: Interface number. |
|
Severity level |
4 |
|
Example |
QOS/4/CHANNEL_EXCEED_MAXIMUM: -MDC=1-Slot=3; The sum of channel bandwidth and network-slice bandwidth (855000000 kbps) exceeds the maximum bandwidth (2000000000 kbps). |
|
Explanation |
This message is generated when the sum of channel bandwidth and network slice bandwidth exceeded the maximum bandwidth. |
|
Recommended action |
Modify the channel bandwidth and network slice bandwidth. |
COPP_RATE_EXCEED
|
Message text |
Security cpu-defend drop packets alarmed. SlotId=$1, Chip=$2, ClassifierName=$3, DropPkts=$4, Speed=$5 (DropThreshold=$6, Interval=$7, SpeedTh=$8). |
|
Variable fields |
$1: Slot number. $2: Chip number. $3: Traffic class name. $4: Number of dropped packets. $5: Rate of dropping packets. $6: Packet drop count threshold. $7: Statistics collection period. $8: Packet drop rate threshold. |
|
Severity level |
4 |
|
Example |
QACL/4/COPP_RATE_EXCEED: -MDC=1-Slot=4; Security cpu-defend drop packets alarmed. SlotId=4, Chip=0, ClassifierName=class1, DropPkts=53416502, Speed=821792(DropThreshold=1, Interval=65, SpeedTh=1000000). |
|
Explanation |
This message is generated when the number or rate of packets of a traffic class dropped by the control plane exceeds the specified threshold. |
|
Recommended action |
1. Modify the packet drop thresholds. 2. Lower the rate of packets sent to the control plane. 3. If the issue persists, contact Technical Support. |
QOS_AGGPORT_POLICY
|
Message text |
Failed to synchronize the QoS policy on an aggregate interface to a new member port. Not enough hardware resources available. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/4/QOS_AGGPORT_POLICY:-MDC=1-Slot=5; Failed to synchronize the QoS policy on an aggregate interface to a new member port. Not enough hardware resources available. |
|
Explanation |
The system failed to synchronize the QoS policy on a Layer 3 aggregate interface to a new member port, because hardware resources were insufficient. |
|
Recommended action |
1. Remove the member port from the Layer 3 aggregate interface. 2. Reapply the QoS policy to the Layer 3 aggregate interface. 3. If the issue persists, contact Technical Support. |
QOS_CONGESTION_DETECTED
|
Message text |
Congestion is detected on an interface of chip [INT 32] in slot [INT 32]. |
|
Variable fields |
$1: Chip number. $2: Slot number of the card. |
|
Severity level |
3 |
|
Example |
QACL/3/QOS_CONGESTION_DETECTED: -MDC=1-Slot=3; Congestion is detected on an interface of chip 0 in slot 3. |
|
Explanation |
This message is generated when congestion is detected on an interface. |
|
Recommended action |
1. Contact Technical Support. |
NETSTREAM_SAMPLER_NORES
|
Message text |
Not enough sampler resources for NetStream. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/4/NETSTREAM_SAMPLER_NORES:-MDC=1-Slot=4; Not enough sampler resources for NetStream. |
|
Explanation |
This message is generated when you configure a sampler for NetStream and sampler resources are insufficient. |
|
Recommended action |
Contact Technical Support. |
QOS_WFQ_NORES
|
Message text |
Not enough WFQ resources to modify the weight value of queue [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 |
|
Example |
QACL/4/QOS_WFQ_NORES : -MDC=1-Slot=9; Not enough WFQ resources to modify the weight value of queue [INT 32] in a queue scheduling profile. |
|
Explanation |
The system failed to modify the WFQ weight value of a queue in a queue scheduling profile, because WFQ resources were insufficient. |
|
Recommended action |
1. Delete unnecessary WFQ weight values to release WFQ resources. 2. If the problem persists, contact Technical Support. |
QMPROFILE_QUEUE_NORES
|
Message text |
Not enough Limit resources to modify the max-bandwidth value of queue [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 |
|
Example |
QACL/4/QMPROFILE_QUEUE_NORES : -MDC=1-Slot=9; Not enough Limit resources to modify the max-bandwidth value of queue [INT 32] in a queue scheduling profile. |
|
Explanation |
This message is generated when you dynamically modify the maximum bandwidth in a queue scheduling profile and rate limiting resources are insufficient. |
|
Recommended action |
1. Delete unnecessary maximum bandwidth settings and queue-based GTS settings. 2. If the problem persists, contact Technical Support. |
MAXBAND_EXCEED_10G
|
Message text |
Not support to modify the max-bandwidth value of queue [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 |
|
Example |
QACL/4/MAXBAND_EXCEED_10G : -MDC=1-Slot=9; Not support to modify the max-bandwidth value of queue [INT 32] in a queue scheduling profile. |
|
Explanation |
This message is generated when you dynamically modify the maximum bandwidth in a queue scheduling profile and the bandwidth value is beyond the capabilities of the device. |
|
Recommended action |
1. Modify the maximum bandwidth to a value smaller than 10 Gbps. 2. If the problem persists, contact Technical Support. |
QOS_SHAPING_NORES
|
Message text |
The rate limiting configuration on interface [STRING] didn't work as expected due to insufficient hardware resources. |
|
Variable fields |
$1: Layer 3 aggregate interface name. |
|
Severity level |
4 |
|
Example |
QACL/4/QOS_SHAPING_NORES:-MDC=1-Slot=4; The rate limiting configuration on interface RAGG1 didn't work as expected due to insufficient hardware resources. |
|
Explanation |
The following configurations on a Layer 3 aggregate interface might not work as expected if the member ports of the aggregate interface change between Selected state and Unselected state when hardware resources are insufficient: · Rate limiting configuration. · Exclusive bandwidth configuration. · Both rate limiting configuration and exclusive bandwidth configuration. |
|
Recommended action |
1. Contact Technical Support. |
QOS_SHAPING_NORES
|
Message text |
The network-slice (id $1) bandwidth configuration on interface $2 didn't work as expected due to insufficient hardware resources. |
|
Variable fields |
$1: Network slice ID. $2: Interface name. |
|
Severity level |
4 |
|
Example |
QACL/4/QOS_SHAPING_NORE: -MDC=1-Slot=4; The network-slice(id 1) bandwidth configuration on interface RAGG1 didn't work as expected due to insufficient hardware resources. |
|
Explanation |
The bandwidth of the Layer 3 aggregate interface changes, but the network slice configured on the interface cannot function as expected due to insufficient hardware resources. |
|
Recommended action |
Contact Technical Support. |
QOS_SHAPING_NORES
|
Message text |
The network-slice bandwidth configuration didn't work as expected due to insufficient hardware resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/4/QOS_SHAPING_NORE: -MDC=1-Slot=4; The network-slice bandwidth configuration didn't work as expected due to insufficient hardware resources. |
|
Explanation |
Network slice bandwidth is deleted on an interface, but the system cannot update rate limit for non-network slice bandwidth due to insufficient hardware resources. |
|
Recommended action |
Contact Technical Support. |
QOS_PSID_NORES
|
Message text |
Due to insufficient hardware resources, the outgoing traffic for the newly added member port of a Layer 3 aggregation group was sent out of another Selected port. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/4/QOS_PSID_NORES:-MDC=1-Slot=4; Due to insufficient hardware resources, the outgoing traffic for the newly added member port of Layer 3 aggregation group was sent out of another member port. |
|
Explanation |
A new member port added to a Layer 3 aggregation group with eight member ports cannot sent traffic after it is become Selected. Its outgoing traffic is sent out of another Selected port. |
|
Recommended action |
1. Remove one or more Unselected ports from the Layer 3 aggregation group. 2. If the problem persists, contact Technical Support. |
ATM_QUEUE_NORES
|
Message text |
Not enough hardware queue resources for ATM interfaces. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/4/ATM_QUEUE_NORES:-MDC=1-Slot=4; Not enough hardware queue resources for ATM interfaces. |
|
Explanation |
Failed to create a PVC or switch the PVC service type on an ATM interface because of insufficient hardware queue resources on the card. |
|
Recommended action |
If the problem persists, contact Technical Support. |
MOD_MINBANDPCT_NOTSPT
|
Message text |
Not support to modify the min-bandwidth-pct value of queue [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 |
|
Example |
QACL/4/MOD_MINBANDPCT_NOTSPT: -Slot=9; Not support to modify the min-bandwidth-pct value of queue 1 in a queue scheduling profile. |
|
Explanation |
This message is generated when you modify the minimum guaranteed bandwidth of a queue in a queue scheduling profile already applied from an absolute value to a percentage value. |
|
Recommended action |
Modify the minimum guaranteed bandwidth also as an absolute value. |
MPLSTE_RSVBAND_NORSC
|
Message text |
Hardware resources not enough. Can't deploy [string]'s MPLS TE bandwidth configuration to [string] when [string] is added to [string]. |
|
Variable fields |
$1: Name of a Layer 3 aggregate interface. $2: Name of a member port for a Layer 3 aggregate interface. $3: Name of a member port for a Layer 3 aggregate interface. $4: Name of a Layer 3 aggregate interface. |
|
Severity level |
4 |
|
Example |
QACL/4/ MPLSTE_RSVBAND_NORSC: -MDC=1; Hardware resources not enough. Can't deploy Route-Aggregation1's MPLS TE bandwidth configuration to GigabitEthernet0/0/9 when GigabitEthernet0/0/9 is added to Route-Aggregation1. |
|
Explanation |
Hardware entry resources are insufficient on the module. The system fails to obtain the reserved TE bandwidth on the Layer 3 aggregate interface when a member port joins the aggregate interface. |
|
Recommended action |
Contact Technical Support. |
QMPROFILE_GROUP_NORES
|
Message text |
Not enough rate limit resources to modify the maximum bandwidth value of group [INT 32] in a queue scheduling profile. |
|
Variable fields |
$1: Group ID. |
|
Severity level |
4 |
|
Example |
QACL/4/QMPROFILE_GROUP_NORES: -MDC=1-Slot=4; Not enough rate limit resources to modify the maximum bandwidth value of group 1 in a queue scheduling profile. |
|
Explanation |
This message is generated when you modify the maximum bandwidth value of a group in a queue scheduling profile but the rate limit resources are insufficient. |
|
Recommended action |
1. Delete unnecessary rate limit settings to release resources. 2. If the problem persists, contact Technical Support. |
QOS_QMPROFILE_RESTORE_FAIL
|
Message text |
Failed to restore the configuration of queue scheduling profile [STRING] on interface [STRING], because [STRING]. |
|
Variable fields |
$1: Queue scheduling profile name. $2: Interface name. $3: Failure cause: ¡ the minimum bandwidth exceeds the interface bandwidth. |
|
Severity level |
4 |
|
Example |
QOS/4/QOS_QMPROFILE_RESTORE_FAIL: Failed to restore the configuration of queue scheduling profile b on interface GigabitEthernet1/0/1, because the minimum bandwidth exceeds the interface bandwidth. |
|
Explanation |
Failed to restore the configuration of a queue scheduling profile. |
|
Recommended action |
Modify the minimum bandwidth in the queue scheduling profile or the interface bandwidth, and apply the queue scheduling profile again. |
QOS_QUEUE_NORMAL
|
Message text |
The interface $1's queue congestion state is restored to normal. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
%Oct 25 15:02:01:751 2021 H3C QACL/4/QOS_QUEUE_NORMAL: -MDC=1-Slot=6; The interface Ten-GigabitEthernet6/2/8's queue congestion state is restored to normal. |
|
Explanation |
The interface queue state restored from congested to normal. |
|
Recommended action |
Contact Technical Support. |
AGGP_MPLSTERSV_NORSC
|
Message text |
The MPLS TE reservable bandwidth configuration on Layer 3 aggregate interface [STRING] didn't work as expected due to insufficient hardware resources. |
|
Variable fields |
$1: Layer 3 aggregate interface number. |
|
Severity level |
6 |
|
Example |
QACL/6/AGGP_MPLSTERSV_NORSC:-MDC=1-Slot=4; The MPLS TE reservable bandwidth configuration on Layer 3 aggregate interface 1 didn't work as expected due to insufficient hardware resources. |
|
Explanation |
This message is generated if hardware resources are insufficient when the state of a member port of a Layer 3 aggregate interface changes between Selected and Unselected. |
|
Recommended action |
1. Reconfigure MPLS TE reservable bandwidth settings on the Layer 3 aggregate interface. 2. If the problem persists, contact Technical Support. |
INTF_QUEUE_BLOCK
|
Message text |
All queues of interface [STRING] are blocked. |
|
Variable fields |
$1: Interface name |
|
Severity level |
4 |
|
Example |
QACL/4/INTF_QUEUE_BLOCK: -MDC=1-Slot=2; All queues of interface Ten-GigabitEthernet 2/2/3 are blocked. |
|
Explanation |
This message is generated when the number of forwarded packets on each queue remains unchanged but the number of dropped packets increases between two polls. The system polls packet statistics on queues at 500-millisecond intervals. |
|
Recommended action |
1. Modify the rate limiting settings on the interface. 2. If the problem persists, contact Technical Support. |
MOD_QUEUEMAXBANDPCT_NOTSPT
|
Message text |
Failed to modify the maximum allowed bandwidth as a percentage for queue [INT 32] in a queue scheduling profile already applied. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 |
|
Example |
QACL/4/MOD_QUEUEMAXBANDPCT_NOTSPT: -MDC=1-Slot=9; Failed to modify the maximum allowed bandwidth as a percentage for queue 1 in a queue scheduling profile already applied. |
|
Explanation |
This message is generated when you modify the maximum allowed queue bandwidth for queue scheduling profile already applied from an absolute value to a percentage value. |
|
Recommended action |
Specify the maximum allowed bandwidth as an absolute value. |
MOD_GROUPMAXBANDPCT_NOTSPT
|
Message text |
Failed to modify the maximum allowed bandwidth as a percentage for group [INT 32] in a queue scheduling profile already applied. |
|
Variable fields |
$1: Group number. |
|
Severity level |
4 |
|
Example |
QACL/4/ MOD_GROUPMAXBANDPCT_NOTSPT: -MDC=1-Slot=9; Failed to modify the maximum allowed bandwidth as a percentage for group 1 in a queue scheduling profile already applied. |
|
Explanation |
This message is generated when you modified the maximum allowed group bandwidth for a queue scheduling profile already applied from an absolute value to a percentage value. |
|
Recommended action |
Specify the maximum allowed bandwidth as an absolute value. |
MPLSTE_CHANNEL_CONFLICT
|
Message text |
The MPLS TE configuration failed to take effect because it conflicts with the channel bandwidth configuration or network-slice configuration. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/4/MPLSTE_CHANNEL_CONFLICT: -MDC=1-Slot=3; The MPLS TE configuration failed to take effect because it conflicts with the channel bandwidth configuration or network-slice configuration. |
|
Explanation |
The MPLS TE configurations conflict with the channel bandwidth or network slice bandwidth configuration on the same interface. |
|
Recommended action |
· Delete MPLS TE configurations on the interface. · To configure MPLS TE, first delete channel bandwidth and network slice bandwidth configurations on the interface. |
QOS_WEIGHT_EXCEED
|
Message text |
Failed to modify the weight value of queue [INT 32] in a queue scheduling profile already applied because the modified value exceeds the maximum value 1023. |
|
Variable fields |
$1: Queue ID. |
|
Severity level |
4 |
|
Example |
QACL/4/QOS_WEIGHT_EXCEED: -MDC=1-Slot=9; Failed to modify the weight value of queue 1 in a queue scheduling profile already applied because the modified value exceeds the maximum value 1023. |
|
Explanation |
This message is generated when the modified weight value of a queue in a queue scheduling profile already applied exceeds 1023. The weight value range for a queue scheduling profile is 0 to 310. When deploying a weight value to a 100GE port, the system multiplies the value by 10, which might cause the weight value to exceed the upper limit (1023). |
|
Recommended action |
Reduce the weight value of the queue. |
QOS_WREDPF_NOTSPT
|
Message text |
Failed to specify or change a WRED profile for queue $1 in a queue scheduling profile authorized to online users. |
|
Variable fields |
$1: ID for a queue in a queue scheduling profile. |
|
Severity level |
4 |
|
Example |
QOS/4/QOS_WREDPF_NOTSPT: Failed to specify or change a WRED profile for queue 3 in a queue scheduling profile authorized to online users. |
|
Explanation |
This message is generated when you add or modify a WRED profile for a queue in a queue scheduling profile authorized to IPoE or PPPoE users. |
|
Recommended action |
Contact Technical Support. |
BPA_INBOUND_NORES
|
Message text |
No resources for inbound BGP policy accounting. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/4/BPA_INBOUND_NORES: -MDC=1-Slot=2; No resources for inbound BGP policy accounting. |
|
Explanation |
This message is generated when resources were exhausted for inbound BGP policy accounting. |
|
Recommended action |
Disable inbound BGP policy accounting on the other interfaces. |
BPAIN_ALLOC_FAIL
|
Message text |
Failed to allocate resources to inbound BGP policy accounting. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
QACL/3/BPAIN_ALLOC_FAIL: -MDC=1-Slot=2; Failed to allocate resources to inbound BGP policy accounting. |
|
Explanation |
This message is generated when the system fails to allocate resources for inbound BGP policy accounting for reasons other than resource exhaustion. |
|
Recommended action |
No action is required. |
BPA_OUTBOUND_NORES
|
Message text |
No resources for outbound BGP policy accounting. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
QACL/3/ BPA_OUTBOUND_NORES: -MDC=1-Slot=2; Failed to allocate resources to outbound BGP policy accounting. |
|
Explanation |
This message is generated when resources were exhausted for outbound BGP policy accounting. |
|
Recommended action |
No action is required. |
BPAOUT_ALLOC_FAIL
|
Message text |
Failed to allocate resources to outbound BGP policy accounting. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
QACL/3/BPAOUT_ALLOC_FAIL: -MDC=1-Slot=2; Failed to allocate resources to outbound BGP policy accounting. |
|
Explanation |
This message is generated when the system fails to allocate resources for outbound BGP policy accounting for reasons other than resource exhaustion. |
|
Recommended action |
No action is required. |
INTF_BPAOUT_NOTSPT
|
Message text |
Failed to configure outbound BGP policy accounting on [STRING] because the configuration on the interface is different from that on other interfaces. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
QACL/4/INTF_BPAOUT_NOTSPT: -MDC=1-Slot=7; Failed to configure outbound BGP policy accounting on Route-Aggregation1024.1 because the configuration on the interface is different from that on other interfaces. |
|
Explanation |
This message is generated when the outbound BGP policy accounting configuration on the interface is different from the configuration on the other interfaces. |
|
Recommended action |
Delete the outbound BGP policy accounting configuration on the interface. Make sure the outbound BGP policy accounting configuration on the interface is consistent with the configuration on the other interfaces. |
INTF_BPAOUT_CONFLICT
|
Message text |
Failed to configure BGP policy accounting on [STRING] because of configuration conflicts. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 |
|
Example |
QACL/4/INTF_BPAOUT_CONFLICT: -MDC=1-Slot=7; Failed to configure BGP policy accounting on Route-Aggregation1024.1 because of configuration conflicts. |
|
Explanation |
This message is generated when the BGP policy accounting configuration conflicts with the other statistics collection configurations on the interface. |
|
Recommended action |
· Delete the BGP policy accounting configuration on the interface. · To configure BGP policy accounting, first delete service statistics collection configuration that might cause conflicts. |
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_SID_ROUTE_CONFLICT_ACTIVE
|
Message text |
Conflict between an SRv6 local SID and a route.(SID=[STRING]/[UINT32]) |
|
Variable fields |
$1: SRv6 SID value. $2: Prefix length of the SRv6 SID. |
|
Severity level |
4 |
|
Example |
RM/4/RM_SID_ROUTE_CONFLICT_ACTIVE: -MDC=1; Conflict between an SRv6 local SID and a route.(SID=100::22/128) |
|
Explanation |
A conflict occurred between the SRv6 SID in the SRv6 local SID forwarding table and that in a route entry. |
|
Recommended action |
Check the routing and SRv6 SID settings, and edit the settings if they are not appropriate. |
RM_SID_ROUTE_CONFLICT_CLEAR
|
Message text |
The conflict between the SRv6 local SID and a route was removed. (SID=[STRING]/[UINT32]) |
|
Variable fields |
$1: SRv6 SID value. $2: Prefix length of the SRv6 SID. |
|
Severity level |
4 |
|
Example |
RM/4/RM_SID_ROUTE_CONFLICT_CLEAR: -MDC=1; The conflict between the SRv6 local SID and a route was removed.(SID=100::22/128) |
|
Explanation |
The conflict between the SRv6 SID in the SRv6 local SID forwarding table and that in a route entry was removed. |
|
Recommended action |
No action is required. |
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. |
RM_TOTAL_THRESHLD_VALUE_REACH
|
Message text |
Threshold value [UINT32] reached for active [STRING] routes in all URTs. |
|
Variable fields |
$1: Maximum number of active routes. $2: IPv4 or IPv6. |
|
Severity level |
4 |
|
Example |
RM/4/ RM_TOTAL_THRESHLD_VALUE_REACH: Threshold value 1000 reached for active IPv4 routes in all URTs. |
|
Explanation |
The total number of active routes in the public network and all VPN instances reached the alarm threshold. |
|
Recommended action |
Check the routing table and take relevant actions, for example, configure a routing policy to reduce the number of route entries. |
RM_TOTAL_THRESHLD_VALUE_CLEAR
|
Message text |
Threshold value [UINT32] of active [STRING] routes fell below the limit in all URTs. |
|
Variable fields |
$1: Maximum number of active routes. $2: IPv4 or IPv6. |
|
Severity level |
4 |
|
Example |
RM/4/RM_TOTAL_THRESHLD_VALUE_CLEAR: Threshold value 1000 of active IPv4 routes fell below the limit in all URTs. |
|
Explanation |
The total number of active routes in the public network and all VPN instances dropped below the alarm threshold. |
|
Recommended action |
No action is required. |
SWFA
This section contains SWFA messages.
FMEA_ERRPKT_DETECT
|
Message text |
Erroneous packets detected on an internal port of slot [UINT32]. |
|
Variable fields |
$1: Slot number of a card. |
|
Severity level |
3 |
|
Example |
SWFA/3/FMEA_ERRPKT_DETECT: Erroneous packets detected on an internal port of slot 3. |
|
Explanation |
Erroneous packets were detected on an internal port (HG port). Syslog messages were output, but the failure will not be fixed. |
|
Recommended action |
Contact Technical Support. |
SYSM messages
This section contains system management messages.
CTRL_CHANNEL_IS_ERR
|
Message text |
The control channel status was abnormal. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
DSYSM/3/CTRL_CHANNEL_IS_ERR: -MDC=1; The control channel status was abnormal. |
|
Explanation |
The control channel keeps in abnormal state and the massage is generated every 10 minutes. The reason might be hardware control link errors. |
|
Recommended action |
· Reboot the card. · Replace the card. |
CTRL_CHANNEL_TO_OK
|
Message text |
The control channel status changed to normal. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
DSYSM/3/CTRL_CHANNEL_TO_OK: -MDC=1; The control channel status changed to normal. |
|
Explanation |
The control channel state changed to normal. |
|
Recommended action |
No action is required. |
CTRL_CHANNEL_TO_ERR
|
Message text |
The control channel status changed to abnormal. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
DSYSM/3/CTRL_CHANNEL_TO_ERR: -MDC=1; The control channel status changed to abnormal. |
|
Explanation |
The control channel state changed to abnormal, which might be caused by hardware control link errors. |
|
Recommended action |
· Reboot the card. · Replace the card. |
DrvDebug
|
Message text |
The board [INT32] is not steady! |
|
Variable fields |
$1: Slot number of the interface module. |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: The board 2 is not steady! |
|
Explanation |
The interface module was not correctly installed or there might be hardware failures. |
|
Recommended action |
1. Verify the interface module installation. 2. Use the display device command to identify whether the interface module is in position. 3. Install the module in another slot if the interface module information is not displayed. 4. Use the display device command to identify whether the interface module is in position. 5. If the interface module is in position, the slot might be damaged, and contact Technical Support. 6. If the interface module is not in position, the interface module might be damaged, and contact Technical Support. |
DrvDebug
|
Message text |
Warning: Overtemperature condition is detected on power module [INT32] Please check it. |
|
Variable fields |
$1: Power module ID. |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: Warning: Overtemperature condition is detected on power module 2. Please check it. |
|
Explanation |
A power module was in an overtemperature condition. |
|
Recommended action |
1. Verify that the ventilation system in the equipment room is operating correctly. 2. Verify that the air outlet vents are not blocked. 3. Verify that the fan trays are operating correctly and air can exhaust from the air outlet vents. 4. Verify that cards or filler panels are correctly installed. 5. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
Warning: Fan of power module [INT32] fails to operate. Please check it. |
|
Variable fields |
$1: Power module ID. |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: Warning: Fan of power module 2 fails to operate. Please check it. |
|
Explanation |
The fans on the power module cannot operate correctly. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
Power Error, there is no input in Power 1. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug:Power Error, there is no input in Power 1 |
|
Explanation |
The power module had no power input. |
|
Recommended action |
1. Verify the power cord installation. ¡ If the power cord is loose, reinstall it. ¡ If the power cord is damaged, replace the power cord. 2. Verify that the power module makes good contact with the backplane. 3. Verify that the power source is providing power correctly and the voltage is in the acceptable range. 4. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
Power Error, there is no input in Power 2. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug:Power Error, there is no input in Power 2 |
|
Explanation |
The power module had no power input. |
|
Recommended action |
1. Verify the power cord installation. ¡ If the power cord is loose, reinstall it. ¡ If the power cord is damaged, replace the power cord. 2. Verify that the power module makes good contact with the backplane. 3. Verify that the power source is providing power correctly and the voltage is in the acceptable range. 4. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
Frame [INT32] fan [STRING] state error! |
|
Variable fields |
$1: ID of a fan tray. $2: ID of a fan. |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: Frame 1 fan 2 state error! |
|
Explanation |
A state error occurred on a fan. The possible reason might be communication error between the fan and the active MPU. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
The airflow directions for the two fan trays must be the same. Please check it. |
|
Variable fields |
N/A |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: The airflow directions for the two fan trays must be the same. Please check it. |
|
Explanation |
The system prints this log and then automatically performs the following tasks when it detects both a fan tray that draws cooling air and a fan tray that exhausts warm air: · Enables the fan tray that draws cooling air to operate at full speed. · Enables the fan tray that exhausts warm air to operate at the lowest speed. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
Warning: Fan [INT32] is absent! |
|
Variable fields |
$1: ID of a fan tray. |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: Warning: Fan 2 is absent! |
|
Explanation |
The system detected no fan tray in the specified slot. |
|
Recommended action |
1. Install a fan tray. 2. Examine the fan tray LED on the MPU. If the LED is steady on, the fan tray is securely installed in the slot. 3. If the problem persists, contact Technical Support. |
DrvDebug
|
Message text |
The device does not support board in slot [INT32] ,type is unknown(0x[STRING]), Please check. |
|
Variable fields |
$1: Slot ID of a card. $2: Type of the card. |
|
Severity level |
5 |
|
Example |
DRVPLAT/5/DrvDebug: The device does not support board in slot3 ,type is unknown(0x80), Please check. |
|
Explanation |
In standalone mode, the device does not support the card. |
|
Recommended action |
Contact Technical Support. |
DrvDebug
|
Message text |
Power modules in power frame [UINT32] are of different models. |
|
Variable fields |
$1: Power frame ID. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Power modules in power frame 1 are of different models. |
|
Explanation |
The power modules in the specified power frame are not of the same model. |
|
Recommended action |
Replace power modules in the specified power frame so all the power modules are of the same model. |
DrvDebug
|
Message text |
Only one power module is installed in power frame [UINT32]. |
|
Variable fields |
$1: Power frame ID. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Only one power module is installed in power frame 1. |
|
Explanation |
Only one power module is installed in the specified power frame. |
|
Recommended action |
Install a second power module in the specified power frame. |
DrvDebug
|
Message text |
Power modules in power frames [UINT32] and [UINT32] are of different models. |
|
Variable fields |
$1: Power frame ID. $2: Power frame ID. |
|
Severity level |
2 |
|
Example |
DRVPLAT/2/DrvDebug: -MDC=1; Power modules in power frames 1 and 2 are of different models. |
|
Explanation |
The power modules in the specified power frames are not of the same model. |
|
Recommended action |
Replace power modules so the power modules in the power frames are of the same model. |
SUBCARD_INSTALL_FAULT
|
Message text |
The subcard in subslot [INT32] is not installed correctly. Please remove the subcard and install it again. |
|
Variable fields |
$1: Subslot ID of a subcard. |
|
Severity level |
1 |
|
Example |
PORT/1/SUBCARD_INSTALL_FAULT: -MDC=1-Slot=7; The subcard in subslot 1 is not installed correctly. Please remove the subcard and install it again. |
|
Explanation |
The specified subcard was not securely installed. |
|
Recommended action |
1. Remove the subcard and securely install the subcard. 2. If the problem persists, contact Technical Support. |
SUBCARD_MISMATCH_PREV
|
Message text |
The type of current board is [STRING]. It doesn't match with the previous board [STRING] in [INT32] Slot [INT32]. |
|
Variable fields |
$1: Model of the new board. $2: Model of the replaced board. $3: Slot number of the board. |
|
Severity level |
2 |
|
Example |
DSYSM/2/SUBCARD_MISMATCH_PREV: The type of current board is MIC-PSP4L. It doesn't match with the previous board MIC-CLP4L in Slot 6. |
|
Explanation |
An interface module was replaced with a module of a different model. |
|
Recommended action |
Do replace a correctly operating interface module with an interface module of a different model. |
SUBCARD_NOTSPT_SLOT
|
Message text |
The board is not supported in slot [INT32]. |
|
Variable fields |
$1: Slot number of the board. |
|
Severity level |
2 |
|
Example |
DSYSM/2/SUBCARD_NOTSPT_SLOT: -MDC=1-Slot=2; The board is not supported in slot 2. |
|
Explanation |
The slot does not support the interface module. |
|
Recommended action |
Replace the interface module with a supported one. |
SUBCARD_NOTSPT_SLOT
|
Message text |
The [STRING] interface module is not supported in slot [INT32]. It can be installed in the following slots: [INT32]. |
|
Variable fields |
$1: Interface module name. $2: Slot number of the interface module. $3: List of slots supported by the interface module. |
|
Severity level |
2 |
|
Example |
DSYSM/2/SUBCARD_NOTSPT_SLOT: -MDC=1-Slot=18; The MIC-XP10L-M interface module is not supported in slot 2. It can be installed in the following slots: 6 7 8 9 10 11 12 13. |
|
Explanation |
This message is sent when an interface module is installed in a slot not supported by the interface module. |
|
Recommended action |
Install the interface module in a slot supported by the interface module. |
CTRL_PATH_FAULT
|
Message text |
A link fault occurred on a control path. |
|
Variable fields |
N/A |
|
Severity level |
3 |
|
Example |
IBC/3/CTRL_PATH_FAULT: A link fault occurred on a control path. |
|
Explanation |
A link fault occurred on a control path. |
|
Recommended action |
Contact Technical Support. |
GET_FPGAFILE_FAILED
|
Message text |
Get fpga file([STRING]) failed! |
|
Variable fields |
$1: FPGA file name. |
|
Severity level |
3 |
|
Example |
SYSM/3/GET_FPGAFILE_FAILED:Get fpga file(NPS_1812X_E.bin) failed! |
|
Explanation |
The system failed to obtain the FPGA file of a card. The card might fail to start. |
|
Recommended action |
Contact Technical Support. |
LOAD_FPGAFILE_FAILED
|
Message text |
Download fpga file([STRING])failed! |
|
Variable fields |
$1: FPGA file name. |
|
Severity level |
3 |
|
Example |
SYSM/3/LOAD_FPGAFILE_FAILED: Downloadfpga file(NPS_1812X_E.bin) failed! |
|
Explanation |
The system failed to download the FPGA file of a card. The card might fail to start. |
|
Recommended action |
Contact Technical Support. |
TE messages
This section contains MPLS TE messages.
TE_BACKUP_SWITCH
|
Message text |
Tunnel [UNIT] ( [STRING] ): [STRING]. [STRING]. |
|
Variable fields |
$1: ID of the main tunnel. $2: LSP information. $3: Tunnel protection status: · Backup tunnel ready—The backup tunnel is ready. No switchover has occurred. · Backup tunnel used—The backup tunnel is being used. A switchover has occurred. · Backup tunnel disabled—The backup tunnel is disabled. · Main tunnel recovered—The main tunnel has recovered and the traffic has been switched back to the main tunnel. $4: LSP information, including the interface IP addresses, LSR IDs, or used labels of the LSRs along the path. This field is displayed only if the tunnel protection status is Backup tunnel used or Main tunnel recovered. |
|
Severity level |
5 |
|
Example |
TE/5/TE_BACKUP_SWITCH: Tunnel 5 ( IngressLsrID=1.1.1.8 EgressLsrID=2.2.2.8 LSPID=100 Bandwidth=1000kbps ): Backup tunnel used. Current LSP path is 10.1.1.1/32(flag=0x00) - 10.1.1.2/32(flag=0x00) - 1151(flag=0x01) - 2.2.2.8/32(flag=0x20). |
|
Explanation |
A backup or SR tunnel was established or removed, or a switchover occurred. |
|
Recommended action |
No action is required. |
TE_MBB_SWITCH
|
Message text |
Tunnel [STRING] ( [STRING] ): Make before break triggered by [STRING]. [STRING]. |
|
Variable fields |
$1: ID of the main tunnel. $2: LSP information. $3: Event that triggered the make-before-break mechanism to re-establish a tunnel: · configuration change—The configuration changed. · FRR used—FRR was used. The system was triggered to re-establish the main tunnel. · reoptimize timer expiration—The tunnel reoptimization timer expired. · automatic bandwidth adjustment—Automatic bandwidth adjustment occurred. · stateful PCE updated—A Stateful PCE PCUpd message was received. $4: LSP information. |
|
Severity level |
5 |
|
Example |
TE/5/TE_MBB_SWITCH: Tunnel 5 ( IngressLsrID=1.1.1.8 EgressLsrID=2.2.2.8 LSPID=100 Bandwidth=1000kbps ): Make-before-break triggered by configuration change. Current LSP path is 10.1.1.1/32(flag=0x00) - 10.1.1.2/32(flag=0x00) - 1151(flag=0x01) - 2.2.2.8/32(flag=0x20). |
|
Explanation |
An event triggered the make-before-break mechanism to re-establish a tunnel. |
|
Recommended action |
No action is required. |
Tunnel messages
This section contains tunnel messages.
GRE_CREATE_NORES
|
Message text |
No enough resource |
|
Variable fields |
N/A |
|
Severity level |
6 |
|
Example |
L3/6/GRE_CREATE_NORES: -MDC=1-Slot=4; No enough resource |
|
Explanation |
Hardware resources were insufficient for completing an operation. For example, when the tunnel resources are not sufficient, the system cannot create a GRE tunnel. |
|
Recommended action |
Contact Technical Support. |
TUNNEL_CREATE_NORES
|
Message text |
The Board Slot [INT32] Create Tunnel Failed, Because No Enough Resource! |
|
Variable fields |
$1: Slot number of the card. |
|
Severity level |
3 |
|
Example |
|
|
Explanation |
A tunnel was created when the next hop resources of the card has exhausted or the L3 INTF resources on the MPU were insufficient. This tunnel cannot be used. You need to re-create the tunnel when the resources are sufficient. |
|
Recommended action |
1. Use the debug ipv4-drv show statistics slot slot-number command in probe view to display the card resource usage information. 2. Clear ARP entries to release resources. 3. Display the card resource usage information again to verify that the resources on the card have recovered. 4. Use the display hardware internal l3 np tunnel index index command in probe view to display the tunnel interface number according to the tunnel index ID. Then, re-create the tunnel. 5. If this message is displayed again, execute the display hardware internal indexq handle 1234FF00 slot slot-number chip chip-number command in probe view to display MPU resource usage information. 6. If the problem persists, contact Technical Support. |
TUN_VXLAN_NOTSPT
|
Message text |
In standard mode, the card does not support vxlan or vxlan-dci ipv6 tunnel. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IPV4/4/TUN_VXLAN_NOTSPT: -MDC=1-Slot=4; In standard mode, the card does not support vxlan or vxlan-dci ipv6 tunnel. |
|
Explanation |
In standard mode, a card does not support IPv6 VXLAN or VXLAN-DCI tunnel establishment. |
|
Recommended action |
Contact Technical Support. |
TUN_SRV6_NOTSPT
|
Message text |
In standard mode, the card does not support srv6 tunnel. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IPV4/4/TUN_SRV6_NOTSPT: -MDC=1-Slot=4; In standard mode, the card does not support srv6 tunnel. |
|
Explanation |
In standard mode, a card does not support SRv6 tunnel establishment. |
|
Recommended action |
Contact Technical Support. |
TUN_SPT_MAX_SID
|
Message text |
The card in this slot supports a maximum of five segment identifiers (SIDs). |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
IPV4/4/TUN_SPT_MAX_SID: -MDC=1-Slot=4; The card in this slot supports a maximum of five segment identifiers (SIDs). |
|
Explanation |
A card in a slot supports a maximum of five SIDs. |
|
Recommended action |
Contact Technical Support. |
WAN messages
This section contains WAN messages.
ALARM_PATH
|
Message text |
[STRING] : Path [STRING] Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: Higher-order path number. $3: Alarm name. Values include AIS, LOF, LOS, RDI, SD, SLM, TIM, and UNEQ. $4: Alarm state. Values include recover and report. $5: Time when the alarm was recovered or reported. The format is Y-M-D H:M:S:MS. |
|
Severity level |
4 |
|
Example |
WAN/4/ALARM_PATH: -MDC=1-Slot=5; Cpos5/1/1 : Path 1 Alarm AIS report! Start Time : 2014-04-04 11:40:53:533! |
|
Explanation |
A higher-order path alarm occurred on or was removed on a CPOS interface. A higher-order path alarm occurs in the following situations: · The peer CPOS interface is shut down by using the shutdown command. · The two ends use different higher-order path overhead bytes. |
|
Recommended action |
No action is required if the alarm state is recover. Perform the following tasks if the alarm state is report: 7. Use the display interface cpos command to check the physical state of the interface. a. If the physical state is UP, the interface is both administratively and physically up. Go to step 2. b. If the physical state is DOWN (Administratively), the interface has been shut down by using the shutdown command. To bring the interface up, use the undo shutdown command. c. If the physical state is DOWN, the interface is administratively up but physically down. Verify that the cable is securely connected and is in a good condition. 8. Use the display transceiver alarm command to check for a transceiver module failure. 9. Use the display this command in interface view to verify that the two interfaces have the same settings for the C2 and J1 overhead bytes. 10. If the problem persists, contact Technical Support. |
ALARM_SDH_AU4E1
|
Message text |
[STRING] : VC4 1 TUG-3 [STRING] TUG-2 [STRING] TU12 [STRING] E1 Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: TUG-3 number. $3: TUG-2 number. $4: TU-12 number. $5: Alarm name. Values include AIS, LOF, LOS, RDI, SD, SLM, TIM, and UNEQ. $6: Alarm state. Values include recover and report. $7: Time when the alarm was recovered or reported. The format is Y-M-D H:M:S:MS. |
|
Severity level |
4 |
|
Example |
WAN/4/ALARM_SDH_AU4E1: -MDC=1-Slot=4; Cpos4/1/1 : VC4 1 TUG-3 1 TUG-2 1 TU12 1 E1 Alarm AIS report! Start Time : 2014-04-04 14:16:51:213! |
|
Explanation |
An E1 channel alarm occurred or was removed on a CPOS interface. The framing format of the CPOS interface is SDH and the AUG multiplexing mode is AU-4. An E1 channel alarm occurs in the following situations: · The remote E1 channel is shut down by using the shutdown command. · The peer E1 channels use different overhead byte settings. |
|
Recommended action |
No action is required if the alarm state is recover. Perform the following tasks if the alarm state is report: 11. Use the display interface cpos e1 command to check the physical state of the CPOS interface. a. If the physical state is UP, the interface is both administratively and physically up. Go to step 2. b. If the physical state is DOWN (Administratively), the interface has been shut down by using the shutdown command. To bring the interface up, use the undo shutdown command. c. If the physical state is DOWN, the interface is administratively up but physically down. Verify that the cable is securely connected and is in a good condition. 12. Use the display transceiver alarm command to check for a transceiver module failure. 13. Use the display this command in interface view to verify that the peer E1 channels have the same settings for the C2 and J2 overhead bytes. 14. If the problem persists, contact Technical Support. |
ALARM_SDH_AU3E1
|
Message text |
[STRING] : AUG 1 VC3 [STRING] TUG-2 [STRING] TU12 [STRING] E1 Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: VC3 number. $3: TUG-2 number. $4: TUG-12 number. $5: Alarm name. Values include AIS, LOF, LOS, RDI, SD, SLM, TIM, and UNEQ. $6: Alarm state. Values include recover and report. $7: Time when the alarm was recovered or reported. The format is Y-M-D H:M:S:MS. |
|
Severity level |
4 |
|
Example |
WAN/4/ALARM_SDH_AU3E1: -MDC=1-Slot=4; Cpos4/1/1 : AUG 1 VC3 1 TUG-2 1 TU12 1 E1 Alarm AIS report! Start Time : 2014-04-04 14:17:55:977! |
|
Explanation |
An E1 channel alarm occurred or was removed on a CPOS interface. The framing format of the CPOS interface is SDH, and the AUG multiplexing mode is AU-3. An E1 channel alarm occurs in the following situations: · The remote E1 channel is shut down by using the shutdown command. · The peer E1 channels use different overhead byte settings. |
|
Recommended action |
No action is required if the alarm state is recover. Perform the following tasks if the alarm state is report: 15. Use the display interface cpos e1 command to check the physical state of the CPOS interface. a. If the physical state is UP, the interface is both administratively and physically up. Go to step 2. b. If the physical state is DOWN (Administratively), the interface has been shut down by using the shutdown command. To bring the interface up, use the undo shutdown command. c. If the physical state is DOWN, the interface is administratively up but physically down. Verify that the cable is securely connected and is in a good condition. 16. Use the display transceiver alarm command to check for a transceiver module failure. 17. Use the display this command in interface view to verify that the peer E1 channels have the same settings for the C2 and J2 overhead bytes. 18. If the problem persists, contact Technical Support. |
ALARM_SONET_E1
|
Message text |
[STRING] : OC-3 1 STS [STRING] VTG [STRING] VT2 [STRING] E1 Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: STS number. $3: VTG number. $4: VT2 number. $5: Alarm name. Values include AIS, LOF, LOS, RDI, SD, SLM, TIM, and UNEQ. $6: Alarm state. Values include recover and report. $7: Time when the alarm was recovered or reported. The format is Y-M-D H:M:S:MS. |
|
Severity level |
4 |
|
Example |
WAN/4/ALARM_SONET_E1: -MDC=1-Slot=4; Cpos4/1/1 : OC-3 1 STS 1 VTG 1 VT2 1 E1 Alarm AIS recover! Start Time : 2014-04-04 14:23:04:125! |
|
Explanation |
An E1 channel alarm occurred or removed on a CPOS interface. The framing format of the CPOS interface is SONET. An E1 channel alarm occurs in the following situations: · The remote E1 channel is shut down by using the shutdown command. · The peer E1 channels use different overhead byte settings. |
|
Recommended action |
No action is required if the alarm state is recover. Perform the following tasks if the alarm state is report: 19. Use the display interface cpos e1 command to check the physical state of the CPOS interface. a. If the physical state is UP, the interface is both administratively and physically up. Go to step 2. b. If the physical state is DOWN (Administratively), the interface has been shut down by using the shutdown command. To bring the interface up, use the undo shutdown command. c. If the physical state is DOWN, the interface is administratively up but physically down. Verify that the cable is securely connected and is in a good condition. 20. Use the display transceiver alarm command to check for a transceiver module failure. 21. Use the display this command in interface view to verify that the peer E1 channels have the same settings for the C2 and J2 overhead bytes. 22. If the problem persists, contact Technical Support. |
ALARM_SECTION_LINE
|
Message text |
[STRING] : Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: Alarm name. Values include AIS, LOF, LOS, RDI, SD, SLM, TIM, and UNEQ. $3: Alarm state. Values include recover and report. $4: Time when the alarm was recovered or reported. The format is Y-M-D H:M:S:MS. |
|
Severity level |
4 |
|
Example |
WAN/4/ALARM_SECTION_LINE: -MDC=1-Slot=4; Cpos4/1/1 : Alarm LOS report! Start Time : 2014-04-04 14:14:47:263! |
|
Explanation |
A regenerator section or multiplexer section alarm occurred or was removed on a CPOS interface. A regenerator section or multiplexer section alarm occurs in the following situations: · The peer CPOS interface is shut down by using the shutdown command. · The two ends use different overhead byte settings for SONET or SDH. · The two ends use the same clock mode. |
|
Recommended action |
No action is required if the alarm state is recover. Perform the following tasks if the alarm state is report: 23. Use the display interface cpos command to check the physical state of the CPOS interface. a. If the physical state is UP, the interface is both administratively and physically up. Go to step 2. b. If the physical state is DOWN (Administratively), the interface has been shut down by using the shutdown command. To bring the interface up, use the undo shutdown command. c. If the physical state is DOWN, the interface is administratively up but physically down. Verify that the cable is securely connected and is in a good condition. 24. Use the display transceiver alarm command to check for a transceiver module failure. 25. Use the display this command in interface view to verify that: 26. The two ends have the same J0 overhead byte setting. 27. The two ends use different clock modes (master at one end and slave at the other end). 28. If the problem persists, contact Technical Support. |
ALARM_LEVEL
|
Message text |
[STRING] : [STRING] [STRING] [STRING]. |
|
Variable fields |
$1: WAN interface name. $2: Alarm state, including recovers and reports. $3: Section or path on which the alarm occurred: ¡ Section—Regenerator section. ¡ Line—Multiplexer section. ¡ High Path—Higher-order path. ¡ Low Path—Lower-order path. $4: Alarm name. Values include AIS, LOF, LOS, RDI, SD, SLM, TIM, and UNEQ. |
|
Severity level |
4 |
|
Example |
WAN/4/ALARM_LEVEL: -MDC=1-Slot=2; Pos2/4/1 : reports Section TIM. WAN/4/ALARM_LEVEL: -MDC=1-Slot=2; Pos2/4/1 : reports High Path TIM. |
|
Explanation |
An alarm occurred or was removed on a WAN interface. An alarm occurs in the following situations: · The remote WAN interface is shut down by using the shutdown command. · The two ends use different overhead byte settings for SONET or SDH. · The two ends use the same clock mode. |
|
Recommended action |
No action is required if the alarm state is recovers. Perform the following tasks if the alarm state is reports: 29. Use the display interface command to check the physical state of the interface. a. If the physical state is UP, the interface is both administratively and physically up. Go to step 2. b. If the physical state is DOWN (Administratively), the interface has been shut down by using the shutdown command. To bring the interface up, use the undo shutdown command. c. If the physical state is DOWN, the interface is administratively up but physically down. Verify that the cable is securely connected and is in a good condition. 30. Use the display transceiver alarm command to check for a transceiver module failure. 31. Use the display this command in interface view to verify that: 32. The two ends have the same settings for the J0, J1, and C2 overhead bytes. 33. The two ends use different clock modes (master at one end and slave at the other end). 34. If the problem persists, contact Technical Support. |
ALARM_STATUS_CHG
|
Message text |
[STRING] : [STRING] of [STRING] has lasted link-delay time! |
|
Variable fields |
$1: WAN interface name. $2: Alarm state. Values include Recovering and Reporting. $3: Alarm name. Values include SD, SF, and RDI. |
|
Severity level |
4 |
|
Example |
WAN/4/ALARM_STATUS_CHG: -MDC=1-Slot=2; Pos2/4/1 Reporting of Line RDI has lasted link-delay time! |
|
Explanation |
An alarm has lasted or has been removed from the WAN interface for a time period. This message is available only for interfaces that are monitored in track entries created by using the track interface command. · The negative-time argument of the command specifies the delay before the alarm report message is generated. · The positive-time argument of the command specifies the delay before the alarm recovery message is generated. |
|
Recommended action |
No action is required if the alarm state is Recovering. Perform the following tasks if the alarm state is Reporting: 35. Use the display interface command to check the physical state of the interface. a. If the physical state is UP, the interface is both administratively and physically up. Go to step 2. b. If the physical state is DOWN (Administratively), the interface has been shut down by using the shutdown command. To bring the interface up, use the undo shutdown command. c. If the physical state is DOWN, the interface is administratively up but physically down. Verify that the cable is securely connected and is in a good condition. 36. Use the display transceiver alarm command to check for a transceiver module failure. 37. If the problem persists, contact Technical Support. |
RXTX messages
This section contains RXTX messages.
PRO_ATTACK
|
Message text |
The [STRING] protocol packet input rate is greater than the speed limit, dropped packets: [UINT32]. |
|
Variable fields |
$1: Protocol name. $2: Number of packets dropped. |
|
Severity level |
4 |
|
Example |
RXTX/4/PRO_ATTACK: The ARP protocol packet input rate is greater than the speed limit, dropped packets: 100. |
|
Explanation |
The protocol packet input rate is greater than the speed limit and the number of dropped packets is displayed. |
|
Recommended action |
Contact Technical Support. |
PRO_ATTACK
|
Message text |
The [STRING] protocol dropped packets due to queue congestion: [UINT32]. |
|
Variable fields |
$1: Protocol name. $2: Number of packets dropped. |
|
Severity level |
4 |
|
Example |
RXTX/4/PRO_ATTACK: The DHCP protocol dropped packets due to queue congestion: 100. |
|
Explanation |
In a CP and UP separation network, DHCP, IPoE, CUSP, or VXLAN packets are dropped due to queue congestion and the number of dropped packets is displayed. |
|
Recommended action |
Contact Technical Support. |
PRO_ATTACK
|
Message text |
The [STRING] whitelist protocol dropped packets due to queue congestion: [UINT32]. |
|
Variable fields |
$1: Protocol name. $2: Number of packets dropped. |
|
Severity level |
4 |
|
Example |
RXTX/4/PRO_ATTACK: The BGP whitelist protocol dropped packets due to queue congestion: 100. |
|
Explanation |
Protocol packets in the whitelist are dropped due to queue congestion and the number of dropped packets is displayed. |
|
Recommended action |
Contact Technical Support. |
TTL1
|
Message text |
The TTL1 protocol packet input rate is greater than the speed limit. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
RXTX/4/TTL1: The ARP protocol packet input rate is greater than the speed limit. |
|
Explanation |
The input rate of a packet whose TTL is 1 exceeds the software speed limit. |
|
Recommended action |
Contact Technical Support. |
SRPM messages
This section contains SRPM messages.
SRPM_IC
|
Message text |
No enough resources. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
SRPM/4/ SRPM_IC: -MDC=1-Slot=4; No enough resources. |
|
Explanation |
Resources were insufficient. |
|
Recommended action |
Delete unused configuration to release resources or contact Technical Support. |
SRPM_IC
|
Message text |
This module does not support SRPM. Please check your configuration. |
|
Variable fields |
N/A |
|
Severity level |
4 |
|
Example |
SRPM/4/ SRPM_IC: -MDC=1-Slot=4; This module does not support SRPM. Please check your configuration. |
|
Explanation |
The module does not support SRPM. |
|
Recommended action |
Contact Technical Support. |
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 (Warning) |
|
Example |
TACACS/4/TACACS_ACCT_SERVER_DOWN: TACACS accounting server was blocked: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
A server becomes unreachable, which causes the user to fail to come online. |
|
Cause |
An accounting server became blocked from active. |
|
Recommended action |
1. Use the display interface command to identify whether the interface connected to the TACACS accounting server is up: ¡ If no, troubleshoot the physical links. ¡ If yes, go to step 2. 2. Use the ping command to identify whether the TACACS accounting server is reachable: ¡ If no, first check the network reachability between the device and the TACACS accounting server, and then identify whether firewalls exist in the network. Make sure the TACACS accounting server is reachable. ¡ If yes, go to step 3. 3. Use the display current-configuration command to identify whether the TACACS accounting server is configured correctly: ¡ If no, modify the TACACS accounting server settings. For more information about TACACS server configuration, see AAA commands in Security Command Reference and AAA configuration in Security Configuration Guide of the device. ¡ If yes, go to step 4. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
TACACS/6/TACACS_ACCT_SERVER_UP: TACACS accounting server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device detected that a TACACS accounting server became active from blocked. |
|
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 (Warning) |
|
Example |
TACACS/4/TACACS_AUTH_SERVER_DOWN: TACACS authentication server was blocked: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
This issue will result in user authentication failures during login. If no secondary authentication servers are available, users might be disconnected. |
|
Cause |
The device detected that a TACACS authentication server became blocked from active. |
|
Recommended action |
1. Use the display interface command to identify whether the interface connected to the TACACS accounting server is up: ¡ If no, troubleshoot the physical links. ¡ If yes, go to step 2. 2. Use the ping command to identify whether the TACACS accounting server is reachable: ¡ If no, first check the network reachability between the device and the TACACS accounting server, and then identify whether firewalls exist in the network. Make sure the TACACS accounting server is reachable. ¡ If yes, go to step 3. 3. Use the display current-configuration command to identify whether the TACACS accounting server is configured correctly: ¡ If no, modify the TACACS accounting server settings. For more information about TACACS server configuration, see AAA commands in Security Command Reference and AAA configuration in Security Configuration Guide of the device. ¡ If yes, go to step 4. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
TACACS/6/TACACS_AUTH_SERVER_UP: TACACS authentication server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device detected that a TACACS authentication server became active from blocked. |
|
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 (Warning) |
|
Example |
TACACS/4/TACACS_AUTHOR_SERVER_DOWN: TACACS authorization server was blocked: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
This issue will result in user authentication failures during login. If no secondary authentication servers are available, users might be disconnected. |
|
Cause |
The device detected that a TACACS authorization server became blocked from active. |
|
Recommended action |
1. Use the display interface command to identify whether the interface connected to the TACACS accounting server is up: ¡ If no, troubleshoot the physical links. ¡ If yes, go to step 2. 2. Use the ping command to identify whether the TACACS accounting server is reachable: ¡ If no, first check the network reachability between the device and the TACACS accounting server, and then identify whether firewalls exist in the network. Make sure the TACACS accounting server is reachable. ¡ If yes, go to step 3. 3. Use the display current-configuration command to identify whether the TACACS accounting server is configured correctly: ¡ If no, modify the TACACS accounting server settings. For more information about TACACS server configuration, see AAA commands in Security Command Reference and AAA configuration in Security Configuration Guide of the device. ¡ If yes, go to step 4. 4. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
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 (Informational) |
|
Example |
TACACS/6/TACACS_AUTHOR_SERVER_UP: TACACS authorization server became active: Server IP=1.1.1.1, port=1812, VPN instance=public. |
|
Impact |
No negative impact on the system. |
|
Cause |
The device detected that a TACACS authorization server became active from blocked. |
|
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 (Warning) |
|
Example |
TACACS/4/TACACS_DELETE_HOST_FAIL: Failed to delete servers in scheme abc. |
|
Impact |
The impact on the system is determined based on the actual situation. |
|
Cause |
Failed to use a command line to delete servers from a TACACS scheme. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
TE messages
This section contains MPLS TE messages.
TE_BACKUP_SWITCH
|
Message text |
Tunnel [UNIT] ( [STRING] ): [STRING]. [STRING]. |
|
Variable fields |
$1: ID of the main tunnel. $2: LSP information. $3: Tunnel protection status: · Backup tunnel ready—The backup tunnel is ready. No switchover has occurred. · Backup tunnel used—The backup tunnel is being used. A switchover has occurred. · Backup tunnel disabled—The backup tunnel is disabled. · Main tunnel recovered—The main tunnel has recovered and the traffic has been switched back to the main tunnel. $4: LSP information, including the interface IP addresses, LSR IDs, or used labels of the LSRs along the path. This field is displayed only if the tunnel protection status is Backup tunnel used or Main tunnel recovered. |
|
Severity level |
5 |
|
Example |
TE/5/TE_BACKUP_SWITCH: Tunnel 5 ( IngressLsrID=1.1.1.8 EgressLsrID=2.2.2.8 LSPID=100 Bandwidth=1000kbps ): Backup tunnel used. Current LSP path is 10.1.1.1/32(flag=0x00) - 10.1.1.2/32(flag=0x00) - 1151(flag=0x01) - 2.2.2.8/32(flag=0x20). |
|
Explanation |
A backup or SR tunnel was established or removed, or a switchover occurred. |
|
Recommended action |
No action is required. |
TE_MBB_SWITCH
|
Message text |
Tunnel [STRING] ( [STRING] ): Make before break triggered by [STRING]. [STRING]. |
|
Variable fields |
$1: ID of the main tunnel. $2: LSP information. $3: Event that triggered the make-before-break mechanism to re-establish a tunnel: · configuration change—The configuration changed. · FRR used—FRR was used. The system was triggered to re-establish the main tunnel. · reoptimize timer expiration—The tunnel reoptimization timer expired. · automatic bandwidth adjustment—Automatic bandwidth adjustment occurred. · stateful PCE updated—A Stateful PCE PCUpd message was received. $4: LSP information. |
|
Severity level |
5 |
|
Example |
TE/5/TE_MBB_SWITCH: Tunnel 5 ( IngressLsrID=1.1.1.8 EgressLsrID=2.2.2.8 LSPID=100 Bandwidth=1000kbps ): Make-before-break triggered by configuration change. Current LSP path is 10.1.1.1/32(flag=0x00) - 10.1.1.2/32(flag=0x00) - 1151(flag=0x01) - 2.2.2.8/32(flag=0x20). |
|
Explanation |
An event triggered the make-before-break mechanism to re-establish a tunnel. |
|
Recommended action |
No action is required. |
TE messages
This section contains TE messages.
TE_BACKUP_SWITCH
|
Message text |
Tunnel [UNIT] ( [STRING] ): [STRING]. [STRING] |
|
Variable fields |
$1: Primary tunnel information. $2: LSP information. $3: Session status: · Backup tunnel ready—Hot standby is enabled. No primary/backup tunnel switchover is triggered. · Backup tunnel used—Hot standby is enabled. Traffic is switched from the primary tunnel to the backup tunnel. · Backup tunnel disabled—Hot standby is disabled. · Main tunnel recovered—The primary tunnel has recovered. The traffic is switched back to the primary tunnel. $4: LSP path information, including IP addresses of the LSR interfaces, and LSR IDs or flag values of the LSRs that the LSP path traverses. This field is displayed only when the session status is Backup tunnel used or Main tunnel recovered. |
|
Severity level |
5 (Notification) |
|
Example |
TE/5/TE_BACKUP_SWITCH: Tunnel 5 ( IngressLsrID=1.1.1.8 EgressLsrID=2.2.2.8 LSPID=100 Bandwidth=1000kbps ): Backup tunnel used. Current LSP path is 10.1.1.1/32(flag=0x00) - 10.1.1.2/32(flag=0x00) - 1151(flag=0x01) - 2.2.2.8/32(flag=0x20). |
|
System |
No negative impact on the device. |
|
Impact |
This log is generated when a hot standby or segment routing tunnel is established or removed, or a primary/backup tunnel switchover is triggered. |
|
Recommended action |
No action is required. |
TE_MBB_SWITCH
|
Message text |
Tunnel [STRING] ( [STRING] ): Make before break triggered by [STRING]. [STRING] |
|
Variable fields |
$1: Primary tunnel information. $2: LSP information. $3: Events that have triggered make-before-break: · configuration change. · FRR used. · reoptimize timer expiration. · automatic bandwidth adjustment. · stateful PCE updated. · stateful PCE state reverted to local configuration. $4: LSP path information, including IP addresses of the LSR interfaces, and LSR IDs or flag values of the LSRs that the LSP path traverses. |
|
Severity level |
5 (Notification) |
|
Example |
TE/5/TE_MBB_SWITCH: Tunnel 5 ( IngressLsrID=1.1.1.8 EgressLsrID=2.2.2.8 LSPID=100 Bandwidth=1000kbps ): Make before break triggered by configuration change. Current LSP path is 10.1.1.1/32(flag=0x00) - 10.1.1.2/32(flag=0x00) - 1151(flag=0x01) - 2.2.2.8/32(flag=0x20). |
|
System |
No negative impact on the device. |
|
Cause |
This message is generated when make-before-break is triggered to reestablish the tunnel. |
|
Recommended action |
No action is required. |
TE_TUNNEL_NESTING
|
Message text |
Tunnel [STRING] had the nesting issue. |
|
Variable fields |
$1: Tunnel ID. |
|
Severity level |
4 (Warning) |
|
Example |
TE/4/TE_TUNNEL_NESTING: -MDC=1; Tunnel1002 had the nesting issue. |
|
System |
Service traffic forwarding might fail. |
|
Cause |
The explicit path used by the tunnel contains a SID node that identifies a tunnel (which was configured by using the nextsid [ index index-number ] label label-value type binding-sid command). However, the tunnel nesting was wrong, causing packet forwarding failure. |
|
Recommended action |
· Delete the configuration set by the nextsid [ index index-number ] label label-value type binding-sid command for the tunnel. · Check the nextsid configuration for the tunnel to eliminate the following errors: ¡ Self-nesting. The tunnel specified by the binding SID is the current tunnel itself. ¡ Multi-level nesting. The device supports only one-level of tunnel nesting. ¡ Looped nesting. For example, the tunnel (tunnel A) nested another tunnel (tunnel B), and tunnel B nested tunnel A. |
TE_LABEL_DUPLICATE
|
Message text |
Binding SID label [STRING] for tunnel [STRING] is duplicate. |
|
Variable fields |
$1: Value of the BSID label for the tunnel. $2: Tunnel ID. |
|
Severity level |
4 (Warning) |
|
Example |
TE/4/TE_LABEL_DUPLICATE: -MDC=1; Binding SID label 1200 for tunnel 1 is duplicate. |
|
Impact |
The MPLS TE tunnel cannot forward service traffic. |
|
Cause |
The BSID label assigned to the MPLS TE tunnel has already been occupied. |
|
Recommended action |
· Keep using the specified BSID label: a. Execute the display mpls label command to view the protocol that is using the label, and then release the label. b. Delete the BSID configuration of the tunnel, and then respecify the BSID for the tunnel. · Use another label as the BSID of the tunnel: delete the current BSID configuration of the tunnel, and then respecify an unused label as the BSID for the tunnel. |
TELNETD messages
This section contains Telnet daemon messages.
TELNETD_ACL_DENY
|
Message text |
The Telnet Connection [IPADDR]([STRING]) request was denied according to ACL rules. |
|
Variable fields |
$1: IP address of the Telnet client. $2: IP address of the server. $3: VPN instance to which the Telnet client belongs. |
|
Severity level |
5 (Notification) |
|
Example |
TELNETD/5/TELNETD_ACL_DENY: The Telnet Connection 1.2.3.4(vpn1) request was denied according to ACL rules. |
|
Impact |
The system might be under attack. |
|
Cause |
The Telnet server has detected an illegal client attempting to log in. |
|
Recommended action |
Contact Technical Support to check ACL rules to ensure that the Telnet connection complies with the ACL rules. |
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 |
|
|
Impact |
The Telnet user cannot access the system. |
|
Cause |
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, it indicates that the device is using the default setting. 2. To set a greater limit, execute the aaa session-limit command. |
Tunnel messages
This section contains tunnel messages.
GRE_CREATE_NORES
|
Message text |
No enough resource |
|
Variable fields |
N/A |
|
Severity level |
6 (Informational) |
|
Example |
L3/6/GRE_CREATE_NORES: -MDC=1-Slot=4; No enough resource |
|
Impact |
Hardware resources become insufficient and GRE tunnels cannot be created. |
|
Cause |
Excessive creation of tunnels causes insufficient hardware resources for creating a GRE tunnel. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
TUNNEL_CREATE_NORES
|
Message text |
The Board Slot [INT32] Create Tunnel Failed, Because No Enough Resource! |
|
Variable fields |
$1: Slot number of the card. |
|
Severity level |
3 (Error) |
|
Example |
L3/3/TUNNEL_CREATE_NORES: -MDC=1-Slot=2; The Board Slot 2 Create Tunnel Failed, Because No Enough Resource! |
|
Impact |
Tunnels cannot be created on the current card. |
|
Cause |
A tunnel was created when the next hop resources of the card has exhausted or the L3 INTF resources on the MPU were insufficient. This tunnel cannot be created. You need to re-create the tunnel when the resources are sufficient. |
|
Recommended action |
1. Use the debug ipv4-drv show statistics slot slot-number command in probe view to display the card resource usage information. 2. Clear ARP entries to release resources. 3. Display the card resource usage information again to verify that the resources on the card have recovered. 4. Use the display hardware internal l3 np tunnel index index command in probe view to display the tunnel interface number according to the tunnel index ID. Then, re-create the tunnel. 5. If this message is displayed again, execute the display hardware internal indexq handle 1234FF00 slot slot-number chip chip-number command in probe view to display MPU resource usage information. 6. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
TUN_VXLAN_NOTSPT
|
Message text |
In standard mode, the card does not support vxlan or vxlan-dci ipv6 tunnel. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPV4/4/TUN_VXLAN_NOTSPT: -MDC=1-Slot=4; In standard mode, the card does not support vxlan or vxlan-dci ipv6 tunnel. |
|
Impact |
VXLAN over IPv6 tunnels or VXLAN-DCI over IPv6 tunnels cannot be created on the current card. |
|
Cause |
When the device operates in standard mode, the current type of card does not support IPv6 VXLAN or VXLAN-DCI tunnel establishment. |
|
Recommended action |
Contact Technical Support, and then perform the following: · If you are allowed to change the system operating mode, use the system-working-mode command to change the system operating mode to SDN-WAN. · If conditions permit, replace the current card with a card of NP5 type. |
TUN_SRV6_NOTSPT
|
Message text |
In standard mode, the card does not support srv6 tunnel. |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPV4/4/TUN_SRV6_NOTSPT: -MDC=1-Slot=4; In standard mode, the card does not support srv6 tunnel. |
|
Impact |
SRv6 tunnels cannot be created on the current card. |
|
Cause |
When the device operates in standard mode, the current type of card does not support SRv6 tunnel establishment. |
|
Recommended action |
Contact Technical Support. If you are allowed to change the system operating mode, use the system-working-mode command in system view to change the system operating mode to SDN-WAN. |
TUN_SPT_MAX_SID
|
Message text |
The card in this slot supports a maximum of five segment identifiers (SIDs). |
|
Variable fields |
N/A |
|
Severity level |
4 (Warning) |
|
Example |
IPV4/4/TUN_SPT_MAX_SID: -MDC=1-Slot=4; The card in this slot supports a maximum of five segment identifiers (SIDs). |
|
Impact |
SRv6 tunnels cannot be created. |
|
Cause |
This message is sent when the number of SIDs configured for a SID list for an SRv6 tunnel exceeds the maximum number (5) supported. |
|
Recommended action |
1. Delete unused SIDs and then create the SRv6 tunnel again. 2. If the issue persists, collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
UCM messages
This section contains UCM messages.
UCM_APPLY_PPPOEA_FWD_POLICY_FAIL (non-vBRAS-CPs)
|
Message text |
Failed to [STRING] a PPPoEA forwarding policy to the driver: UserGroupName=[STRING], AclType=[STRING], AclEventType=[STRING], FailedReason=[STRING]. |
|
Variable fields |
$1: Action type of the PPPoEA forwarding policy: · add · modify · delete $2: User group name. $3: ACL type: · IPv4 · IPv6 $4: ACL event type: · Cfg change · Add rule · Delete rule · Modify rule · Rule active · Rule inactive · Create ACL group · Delete ACL group · Modify ACL step · Create L3VPN rule · Delete L3VPN rule · Bulk delete rules $5: Reason for failing to deploy the PPPoEA forwarding policy to the driver: · Failed—Hardware match counting failed to be applied. · Not enough resources to complete the operation. · The operation is not supported. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_APPLY_PPPOEA_FWD_POLICY_FAIL: Failed to add a PPPoEA forwarding policy to the driver: UserGroupName=g1, AclType=IPv4, AclEventType=Add rule, FailedReason=Failed. |
|
Impact |
The PPPoEA forwarding policy does not take effect, preventing the device from providing agency services to users. |
|
Cause |
The pppoe-agency forward command fails to be issued to the driver. |
|
Recommended action |
· If the failure reason is Failed, execute the pppoe-agency forward command again later. If the issue persists, contact Technical Support. · If the failure reason is one of the other two reasons, collect the following information and contact Technical Support: ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_IFBACKUPSTATUS_DRIVER_FAILED (pUPs)
|
Message text |
Failed to notify interface backup status: IfName=[ STRING], MACAddr=[MAC], OpType=[STRING], LACNID=[UINT], Status=[STRING], SRv6SID=[IPADDR]. Cause: [STRING]. |
|
Variable fields |
$1: Interface name. $2: Virtual MAC address of an interface. $3: Operation type. Possible values are: · Add—Notify the driver to add the interface master/backup state information. · Delete—Notify the driver to delete the interface master/backup state information. · Modify—Notify the driver to modify the interface master/backup state information. $4: ID for the protection tunnel on the LAC. $5: Interface backup state. Possible values are: · Master—The interface is the master interface. · Backup—The interface is the backup interface. $6: SRv6 SID information. $7: Failure reason. Possible values are: · Insufficient hardware resources. · Not supported. · Unknown error. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_IFBACKUPSTATUS_DRIVER_FAILED: Failed to notify interface backup status: IfName=GigabitEthernet1/0/1, MACAddr=0000-005e-0001, OpType=Add, LACNID=10, Status=Master, SRv6SID=2::2. Cause: Insufficient hardware resources. |
|
Impact |
The protection tunnel is unavailable: · If an active/standby switchover occurs on the LAC UPs, the uplink device will fail to import downlink L2TP packets entering the LAC into the protection tunnel, which will disrupt the user's downlink traffic. · If no active/standby switchover occurs on the LAC UPs, user traffic is normal. |
|
Cause |
On a UP backup network, the protection tunnel resource fails to be issued to the driver because of insufficient hardware resources. |
|
Recommended action |
Collect the following information and contact Technical Support: · Results of each step. · Configuration data, log messages, and alarm information. |
UCM_IPV4_PPPOEA_BOUND_SUCCESS (non-vBRAS-CPs)
|
Message text |
-UserName=[STRING]-IPv4Addr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]–PPPoEAgency-IPv4Addr=[IPADDR]; The PPPoEA user was bound to a BRAS user successfully. |
|
Variable fields |
$1: Username used by an internal campus user to come online. $2: IPv4 address of an internal campus user. $3: Access interface name of an internal campus user. $4: Outer VLAN ID of an internal campus user. $5: Inner VLAN ID of an internal campus user. $6: MAC address of an internal campus user. $7: IPv4 address that the service provider allocates to a PPPoE agency user. |
|
Severity level |
6 (Informational) |
|
Example |
UCM/6/UCM_IPV4_PPPOEA_BOUND_SUCCESS: -UserName=123-IPv4Addr=1.1.1.1-IfName=GigabitEthernet1/0/1-OuterVLAN=100-InnerVLAN=200-MACAddr=0010-9400-000a–PPPoEAgency-IPv4Addr=12.1.1.2; The PPPoEA user was bound to a BRAS user successfully. |
|
Impact |
N/A |
|
Cause |
A PPPoEA user is successfully bound to an internal campus BRAS user. Based on the order in which an internal campus BRAS user comes online in the IPv4 and IPv6 protocol stacks, the following rules apply: · IPv4 and then IPv6 protocol stack—When the internal campus user comes online in the IPv4 protocol stack to trigger the PPPoEA user to come online, if the PPPoEA user successfully comes online and is successfully bound to the BRAS user in the IPv4 protocol stack, this message is generated. If not, this message is not generated. · IPv6 and then IPv6 protocol stack—When the internal campus user comes online in the IPv4 protocol stack, if the device detects that the PPPoEA user has come online successfully and is successfully bound to the BRAS user in the IPv4 protocol stack, this message is generated. If not, this message is not generated. |
|
Recommended action |
No action is required. |
UCM_LOSS_RATIO_EXCEED_THRESHOLD
|
Message text |
Centralized devices: The [STRING] detection packet loss ratio on the interface [STRING] is [UINT32]%, and exceeds [UINT32]%. Distributed devices in standalone mode: Centralized IRF devices: The [STRING] detection packet loss ratio on the interface [STRING] on slot [UINT32] is [UINT32]%, and exceeds [UINT32]%. Distributed devices in IRF mode: The [STRING] detection packet loss ratio on the interface [STRING] on chassis [UINT32] slot [UINT32] is [UINT32]%, and exceeds [UINT32]%. |
|
Variable fields |
$1: Detection packet type. Options include: · ARP: ARP packets. · ND: ND packets. · ICMPv4: ICMPv4 packets. · ICMPv6: ICMPv6 packets. $2: Interface name. $3: Chassis number. (Distributed devices in IRF mode.) $4: Slot number. (Distributed devices in standalone mode.)(Centralized IRF devices.)(Distributed devices in IRF mode.) $5: Packet loss ratio of detection packets. $6: Alarm threshold for the packet loss ratio of detection packets. |
|
Severity level |
4 (Warning) |
|
Example |
Centralized devices: UCM/4/UCM_LOSS_RATIO_EXCEED_THRESHOLD: The ARP detection packet loss ratio on the interface GigabitEthernet1/0/1 is 50%, and exceeds 30%. Distributed devices in standalone mode: Centralized IRF devices: UCM/4/UCM_LOSS_RATIO_EXCEED_THRESHOLD: The ARP detection packet loss ratio on the interface GigabitEthernet1/0/1 on slot 1 is 50%, and exceeds 30%. Distributed devices in IRF mode: UCM/4/UCM_LOSS_RATIO_EXCEED_THRESHOLD: The ARP detection packet loss ratio on the interface GigabitEthernet1/0/1 on chassis 1 slot 1 is 50%, and exceeds 30%. |
|
Impact |
A high packet loss ratio might force users to go offline due to detection failure. |
|
Cause |
· The upper threshold configured is too low. · Device interface connection faults and other issues can lead to poor link quality, causing the number of lost packets for online users to reach the alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to filter and find the access-user user-detect packet-loss-ratio-threshold command. Verify that the current alarm threshold configured for the packet loss ratio of the access user detection packets is appropriate. ¡ If the configured threshold is too low, proceed with step 2. ¡ If the configured threshold is appropriate, proceed with step 3. 2. Execute the access-user user-detect packet-loss-ratio-threshold command in system view on the device to modify the alarm threshold for the packet loss ratio of the access user detection packets. 3. Identify whether the device interface cable connections and network configuration are normal: ¡ If abnormal, troubleshoot the faults. ¡ If normal, proceed with step 4. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_LOSS_RATIO_RECOVER_NORMAL
|
Message text |
Centralized devices: The [STRING] detection packet loss ratio on the interface [STRING] has recovered to normal state. Distributed devices in standalone mode: Centralized IRF devices: The [STRING] detection packet loss ratio on the interface [STRING] on slot [ UINT32] has recovered to normal state. Distributed devices in IRF mode: The [STRING] detection packet loss ratio on the interface [STRING] on chassis [ UINT32] slot [ UINT32] has recovered to normal state. |
|
Variable fields |
$1: Detection packet type. Options include: · ARP: ARP packets. · ND: ND packets. · ICMPv4: ICMPv4 packets. · ICMPv6: ICMPv6 packets. $2: Interface name. $3: Chassis number. (Distributed devices in IRF mode.) $4: Slot number. (Distributed devices in standalone mode.)(Centralized IRF devices.)(Distributed devices in IRF mode.) $5: Packet loss ratio of detection packets. |
|
Severity level |
4 (Warning) |
|
Example |
Centralized devices: UCM/4/UCM_LOSS_RATIO_RECOVER_NORMAL: The ARP detection packet loss ratio on the interface GigabitEthernet1/0/1 has recovered to normal state. Distributed devices in standalone mode: Centralized IRF devices: UCM/4/UCM_LOSS_RATIO_RECOVER_NORMAL: The ARP detection packet loss ratio on the interface GigabitEthernet1/0/1 on slot 1 has recovered to normal state. Distributed devices in IRF mode: UCM/4/UCM_LOSS_RATIO_RECOVER_NORMAL: The ARP detection packet loss ratio on the interface GigabitEthernet1/0/1 on chassis 1 slot 1 has recovered to normal state. |
|
Impact |
The network jitter and latency drop to reasonable levels to restore normal service quality for users. |
|
Cause |
The link quality is restored to normal after you troubleshoot device interface connectivity faults. |
|
Recommended action |
No action is required. |
UCM_SESSION_ADD_DRIVER_FAILED
|
Message text |
Failed to add an UCM session: UserLabel=[UINT16], IPv4Addr=[IPADDR], IPv6Addr=[IPADDR], IfName=[STRING], MACAddr=[MAC]. Cause: [STRING]. |
|
Variable fields |
$1: User label. $2: User IPv4 address. $3: User IPv6 address. $4: Name of the interface where the user came online. $5: User MAC address. $6: Failure reason. Possible values are: · Insufficient hardware resources for BRAS user statistics or BRAS rate-limiting profile. · Insufficient hardware resources for user VLAN QinQ. · Insufficient hardware resources for BRAS user entries. · Maximum number of BRAS users already reached. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_SESSION_ADD_DRIVER_FAILED: Failed to add an UCM session: UserLabel=0x80004c7, IPv4Addr=143.0.0.1, IPv6Addr=N/A, IfName=GigabitEthernet1/0/1, MACAddr=307b-ac83-90df. Cause: Insufficient hardware resources for BRAS user entries. |
|
Impact |
Users cannot come online. |
|
Cause |
Insufficient driver hardware resources lead to the failure to add UCM sessions. |
|
Recommended action |
Collect the following information and contact Technical Support: · Results of each step. · Configuration data, log messages, and alarm information. |
UCM_SESSIONS_LOWER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
The access user session number is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower alarm threshold for the online access user session count. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_SESSIONS_LOWER_THRESHOLD: The access user session number is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of users might go offline because of abnormal reasons. Identify whether a large number of users go offline abnormally. |
|
Cause |
· The device-level lower alarm threshold for the number of online access users is too high. · Users go offline, and the number of users on the device reaches the lower alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the access-user session-threshold command, and identify whether the lower alarm threshold configured is appropriate. ¡ If the configured lower alarm threshold is too high, proceed with step 2. ¡ If the configured lower alarm threshold is appropriate, proceed with step 3. 2. Execute the access-user session-threshold command in system view on the device to modify the lower alarm threshold. 3. Execute the display aaa abnormal-offline-record command to identify whether a large number of access users are going offline abnormally. ¡ If yes, process accordingly based on the specific reason for going offline. ¡ If not, execute the display aaa offline-record command to view the reasons for users to go offline and resolve the issues accordingly. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_SESSIONS_LOWER_THRESHOLD (vBRAS-CPs)
|
Message text |
The access user session number on slot [INT32] is below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Lower alarm threshold for the online access user session count. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_SESSIONS_LOWER_THRESHOLD: The access user session number on slot 97 is below the lower warning threshold (LowerThreshold=20). |
|
Impact |
A large number of users might go offline because of abnormal reasons. Identify whether a large number of users go offline abnormally. |
|
Cause |
· The device-level lower alarm threshold for the number of online access users is too high. · Users go offline, and the number of users on the device reaches the lower alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the access-user session-threshold command, and identify whether the lower alarm threshold configured is appropriate. ¡ If the configured lower alarm threshold is too high, proceed with step 2. ¡ If the configured lower alarm threshold is appropriate, proceed with step 3. 2. Execute the access-user session-threshold command in system view on the device to modify the lower alarm threshold. 3. Execute the display aaa abnormal-offline-record command to identify whether a large number of access users are going offline abnormally. ¡ If yes, process accordingly based on the specific reason for going offline. ¡ If not, execute the display aaa offline-record command to view the reasons for users to go offline and resolve the issues accordingly. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_SESSIONS_LOWER_RECOVER (non-vBRAS-CPs)
|
Message text |
The access user session number has recovered to normal state from below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Lower alarm threshold for the online access user session count. |
|
Severity level |
5 (Notification) |
|
Example |
UCM/5/UCM_SESSIONS_LOWER_RECOVER: The access user session number has recovered to normal state from below the lower warning threshold (LowerThreshold=20). |
|
Impact |
The number of BRAS access users on the device meets the expectation. |
|
Cause |
When users go online, the number of online user sessions recovers from below the lower alarm threshold to the set normal range. |
|
Recommended action |
No action is required. |
UCM_SESSIONS_LOWER_RECOVER (vBRAS-CPs)
|
Message text |
The access user session number on slot [INT32] has recovered to normal state from below the lower warning threshold (LowerThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Lower alarm threshold for the online access user session count. |
|
Severity level |
5 (Notification) |
|
Example |
UCM/5/UCM_SESSIONS_LOWER_RECOVER: The access user session number on slot 97 has recovered to normal state from below the lower warning threshold (LowerThreshold=20). |
|
Impact |
The number of BRAS access users on the device meets the expectation. |
|
Cause |
When users go online, the number of online user sessions recovers from below the lower alarm threshold to the set normal range. |
|
Recommended action |
No action is required. |
UCM_SESSIONS_UPPER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
The access user session number is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper alarm threshold for the online access user session count. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_SESSIONS_UPPER_THRESHOLD: The access user session number is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online BRAS users might exceed the device capability, and the subsequent BRAS users might fail to come online. |
|
Cause |
· The device-level upper alarm threshold for the number of online access users is too low. · Users come online, and the number of users on the device reaches the upper alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the access-user session-threshold command, and identify whether the upper alarm threshold configured is appropriate. ¡ If the configured upper alarm threshold is too low, proceed with step 2. ¡ If the configured upper alarm threshold is appropriate, proceed with step 3. 2. Execute the access-user session-threshold command in system view on the device to modify the upper alarm threshold. 3. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
|
Message text |
The access user session number on slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Upper alarm threshold for the online access user session count. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_SESSIONS_UPPER_THRESHOLD: The access user session number on slot 97 is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online BRAS users might exceed the device capability, and the subsequent BRAS users might fail to come online. |
|
Cause |
· The device-level upper alarm threshold for the number of online access users is too low. · Users come online, and the number of users on the device reaches the upper alarm threshold. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the access-user session-threshold command, and identify whether the upper alarm threshold configured is appropriate. ¡ If the configured upper alarm threshold is too low, proceed with step 2. ¡ If the configured upper alarm threshold is appropriate, proceed with step 3. 2. Execute the access-user session-threshold command in system view on the device to modify the upper alarm threshold. 3. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_SESSIONS_UPPER_RECOVER (non-vBRAS-CPs)
|
Message text |
The access user session number has recovered to normal state from above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Upper alarm threshold for the online access user session count. |
|
Severity level |
5 (Notification) |
|
Example |
UCM/5/UCM_SESSIONS_UPPER_RECOVER: The access user session number has recovered to normal state from above the upper warning threshold (UpperThreshold=20) |
|
Impact |
The number of online BRAS users decreases and does not exceed the device capability. The subsequent BRAS users can come online successfully. |
|
Cause |
Some users go offline, and the number of online access user sessions has been restored from above the upper alarm threshold to the set normal range. |
|
Recommended action |
No action is required. |
UCM_SESSIONS_UPPER_RECOVER (vBRAS-CPs)
|
Message text |
The access user session number on slot [INT32] has recovered to normal state from above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Upper alarm threshold for the online access user session count. |
|
Severity level |
5 (Notification) |
|
Example |
UCM/5/UCM_SESSIONS_UPPER_RECOVER: The access user session number on slot 97 has recovered to normal state from above the upper warning threshold (UpperThreshold=20). |
|
Impact |
The number of online BRAS users decreases and does not exceed the device capability. The subsequent BRAS users can come online successfully. |
|
Cause |
Some users go offline, and the number of online access user sessions has been restored from above the upper alarm threshold to the set normal range. |
|
Recommended action |
No action is required. |
UCM_UP_SESSIONS_UPPER_THRESHOLD (vBRAS-CPs)
|
Message text |
The access user session number on UP [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: UP ID. $2: Upper alarm threshold for the online access user session count. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_UP_SESSIONS_UPPER_THRESHOLD: The access user session number on UP 1024 is above the upper warning threshold (UpperThreshold=20). |
|
Impact |
· The performance pressure on the UP might increase, and the services for online BRAS users might be affected. · The number of online BRAS users on the UP might exceed the device capability, and the subsequent BRAS users might fail to come online. |
|
Cause |
· The upper threshold configured is too low. · Users come online, and the number of users on the UP exceeds the maximum number of user resources supported by the UP. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the CP to check the access-user up-session-threshold command, and identify whether the upper threshold configured is appropriate. ¡ If the upper threshold configured is too low, proceed with step 2. ¡ If the upper threshold configured is appropriate, proceed with step 3. 2. In system view or UP-manage view on the CP, execute the access-user up-session-threshold command to modify the upper threshold for configurable user resources. The configuration in system view applies to all UPs managed by the current CP, while the configuration in UP-manage view only applies to the current UP. The configuration in UP-manage view takes priority.) 3. Execute the display access-user up-id command in any view to view the number of users on the UP. ¡ If the number of users reaches or approaches the configured upper threshold, add an interface card. ¡ If the number of users does not approach the upper threshold configured, proceed with step 4. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_UP_SESSIONS_RECOVER_NORMAL (vBRAS-CPs)
|
Message text |
The access user session number on UP [INT32] has recovered to normal state. |
|
Variable fields |
$1: UP ID. |
|
Severity level |
5 (Notification) |
|
Example |
UCM/5/UCM_UP_SESSIONS_RECOVER_NORMAL: The access user session number on UP 1024 has recovered to normal state. |
|
Impact |
The performance pressure on the UP recovers, and the subsequent BRAS users can normally come online through this UP. |
|
Cause |
Some users go offline, and the number of online access user sessions has been restored to the set normal range. |
|
Recommended action |
No action is required. |
UCM_UPBAK_STATE_CHANGE (vBRAS-CPs)
|
Message text |
Virtual MAC address [STRING] in UP backup profile [USHORT16] has been switched from interface [STRING] to interface [STRING]. This switch has affected [STRING] users. |
|
Variable fields |
$1: Virtual MAC address. $2: UP backup profile ID. $3: Remote interface where the original virtual MAC is located. If the value is Invalid, it indicates that the interface is faulty and invalid. $4: Remote interface after the virtual MAC address migrates. If the value is Invalid, it indicates that the interface is faulty and invalid. $5: Number of users affected by the switchover, which is the sum of users who successfully switched over and those who went offline during switchover. Users who successfully switched over represent those who have moved from the original interface to the target interface without going offline. Users who went offline during switchover represent the users that went offline due to unstable conditions during the switchover process. |
|
Severity level |
6 (Informational) |
|
Example |
UCM/6/UCM_UPBAK_STATE_CHANGE: Virtual MAC address 0000-5e00-0121 in UP backup profile 2 has been switched from interface Remote-GE1024/1/4/0 to interface Remote-GE1025/1/4/0. This switch has affected 2000 users. |
|
Impact |
User service traffic corresponding to the virtual MAC will undergo a switchover. |
|
Cause |
In a UP backup profile, a pair of master and backup interfaces corresponds to a unique virtual MAC address. The UP uses this virtual MAC address to respond to user online requests from these interfaces. When the operating states of the master and backup interfaces changes, the virtual MAC will migrate between them. For example, when the master interface switches from active state to standby state, the virtual MAC address will migrate from the master interface to the backup interface. |
|
Recommended action |
1. Take actions according to the UP backup modes: ¡ In 1:1 hot standby mode, see the recommended action in the UPBAK_IF_STATE_SWITCH log for troubleshooting. ¡ In 1:N warm load sharing mode and N:1 warm standby mode, see the recommended actions in UPBAK_IF_STATE_CHANGE and UPBAK_MAC_STATE_CHANGE logs. 2. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_USER_RECOVER_NORMAL (non-vBRAS-CPs)
|
Message text |
Slot-level alarm: The user number on slot [INT32] has recovered to normal state (CurrentThreshold=[FLOAT]). Chip-level alarm: The user number on slot [INT32] chip [INT32] has recovered to normal state (CurrentThreshold=[FLOAT]). |
|
Variable fields |
$1: Slot number. $2: Chip number. This field is displayed only when the slot hosting the user access interface supports chip-level alarms. $3: User count threshold when the access user count alarm is cleared. |
|
Severity level |
5 (Notification) |
|
Example |
Slot-level alarm: UCM/5/UCM_USER_RECOVER_NORMAL: The user number on slot 1 has recovered to normal state (CurrentThreshold=60%). Chip-level alarm: UCM/5/UCM_USER_RECOVER_NORMAL: The user number on slot 1 chip 0 has recovered to normal state (CurrentThreshold=60%). |
|
Impact |
The performance pressure on the card or chip of the device recovers, and the subsequent BRAS users can normally come online. |
|
Cause |
Some users go offline, and the number of online access users on the specified slot or chip has been restored to the set normal range. |
|
Recommended action |
No action is required. |
|
Message text |
Slot-level alarm: The user number on chassis [INT32] slot [INT32] has recovered to normal state (CurrentThreshold=[FLOAT]). Chip-level alarm: The user number on chassis [INT32] slot [INT32] chip [INT32] has recovered to normal state (CurrentThreshold=[FLOAT]). |
|
Variable fields |
$1: Chassis number. $2: Slot number. $3: Chip number. This field is displayed only when the slot hosting the user access interface supports chip-level alarms. $4: User count threshold when the access user count alarm is cleared. |
|
Severity level |
5 (Notification) |
|
Example |
Slot-level alarm: UCM/5/UCM_USER_RECOVER_NORMAL: The user number on chassis 1 slot 1 has recovered to normal state (CurrentThreshold=60%). Chip-level alarm: UCM/5/UCM_USER_RECOVER_NORMAL: The user number on chassis 1 slot 1 chip 0 has recovered to normal state (CurrentThreshold=60%). |
|
Impact |
The performance pressure on the card or chip of the device recovers, and the subsequent BRAS users can normally come online. |
|
Cause |
Some users go offline, and the number of online access users on the specified slot or chip has been restored to the set normal range. |
|
Recommended action |
No action is required. |
UCM_USER_RECOVER_NORMAL (vBRAS-CPs)
|
Message text |
The user number on slot [INT32] has recovered to normal state (CurrentThreshold=[FLOAT]). |
|
Variable fields |
$1: Slot number of a BRAS-VM. $2: User count threshold when the access user count alarm is cleared. |
|
Severity level |
5 (Notification) |
|
Example |
UCM/5/UCM_USER_RECOVER_NORMAL: The user number on slot 1 has recovered to normal state (CurrentThreshold=60%). |
|
Impact |
The performance pressure on the slot recovers, and the subsequent BRAS users can normally come online. |
|
Cause |
Some users go offline, and the number of online access users on the specified slot has been restored to the set normal range. |
|
Recommended action |
No action is required. |
|
Message text |
Slot-level alarm: The user number on UP [INT32] slot [INT32] has recovered to normal state (CurrentThreshold=[FLOAT]). Chip-level alarm: The user number on UP [INT32] slot [INT32] chip [INT32] has recovered to normal state (CurrentThreshold=[FLOAT]). |
|
Variable fields |
$1: UP ID. $2: Slot number of a UP. $3: Chip number of a UP. This field is displayed only when the slot hosting the user access interface supports chip-level alarms. $4: User count threshold when the access user count alarm is cleared. |
|
Severity level |
5 (Notification) |
|
Example |
Slot-level alarm: UCM/5/UCM_USER_RECOVER_NORMAL: The user number on UP 1024 slot 1 has recovered to normal state (CurrentThreshold=60%). Chip-level alarm: UCM/5/UCM_USER_RECOVER_NORMAL: The user number on UP 1024 slot 1 chip 0 has recovered to normal state (CurrentThreshold=60%). |
|
Impact |
The performance pressure on the card or chip in a UP recovers, and the subsequent BRAS users can normally come online. |
|
Cause |
Some users go offline, and the number of online access users on the specified slot or chip has been restored to the set normal range. |
|
Recommended action |
No action is required. |
UCM_USER_UPPER_THRESHOLD (non-vBRAS-CPs)
|
Message text |
Slot-level alarm: The user number on slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). Chip-level alarm: The user number on slot [INT32] chip [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number. $2: Chip number. This field is displayed only when the slot hosting the user access interface supports chip-level alarms. $3: Upper alarm threshold configured for the online access user count. |
|
Severity level |
4 (Warning) |
|
Example |
Slot-level alarm: UCM/4/UCM_USER_UPPER_THRESHOLD: The user number on slot 1 is above the upper warning threshold (UpperThreshold=20%). Chip-level alarm: UCM/4/UCM_USER_UPPER_THRESHOLD: The user number on slot 1 chip 0 is above the upper warning threshold (UpperThreshold=20%). |
|
Impact |
· The performance pressure on the card or chip in the device might increase, and the services for online BRAS users might be affected. · The number of online BRAS users on the card or chip in the device might exceed the device capability, and the subsequent BRAS users might fail to come online. |
|
Cause |
· The upper threshold configured is too low. · Users come online, and the number of users on the card or chip in the device exceeds the maximum number of user resources supported by the card or chip. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the slot-user-warning-threshold command, and identify whether the upper threshold configured is appropriate. ¡ If the upper threshold configured is too low, proceed with step 2. ¡ If the upper threshold configured is appropriate, proceed with step 3. 2. Execute the slot-user-warning-threshold command in system view on the device to modify the upper threshold for the user resources. 3. Execute the display access-user slot command in any view on the device to view the number of users on the interface module in the specified slot. ¡ If the number of users reaches or approaches the upper threshold configured, add subcards. ¡ If the number of users does not approach the upper threshold configured, proceed with step 4. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
|
Message text |
Slot-level alarm: The user number on chassis [INT32] slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). Chip-level alarm: The user number on chassis [INT32] slot [INT32] chip [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Chassis number. $2: Slot number. $3: Chip number. This field is displayed only when the slot hosting the user access interface supports chip-level alarms. $4: Upper alarm threshold configured for the online access user count. |
|
Severity level |
4 (Warning) |
|
Example |
Slot-level alarm: UCM/4/UCM_USER_UPPER_THRESHOLD: The user number on chassis 1 slot 1 is above the upper warning threshold (UpperThreshold=20%). Chip-level alarm: UCM/4/UCM_USER_UPPER_THRESHOLD: The user number on chassis 1 slot 1 chip 0 is above the upper warning threshold (UpperThreshold=20%). |
|
Impact |
· The performance pressure on the card or chip in the device might increase, and the services for online BRAS users might be affected. · The number of online BRAS users on the card or chip in the device might exceed the device capability, and the subsequent BRAS users might fail to come online. |
|
Cause |
· The upper threshold configured is too low. · Users come online, and the number of users on the card or chip in the device exceeds the maximum number of user resources supported by the card or chip. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the device to check the slot-user-warning-threshold command, and identify whether the upper threshold configured is appropriate. ¡ If the upper threshold configured is too low, proceed with step 2. ¡ If the upper threshold configured is appropriate, proceed with step 3. 2. Execute the slot-user-warning-threshold command in system view on the device to modify the upper threshold for the user resources. 3. Execute the display access-user slot command in any view on the device to view the number of users on the interface module in the specified slot. ¡ If the number of users reaches or approaches the upper threshold configured, add subcards. ¡ If the number of users does not approach the upper threshold configured, proceed with step 4. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_USER_UPPER_THRESHOLD (vBRAS-CPs)
|
Message text |
The user number on slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: Slot number of a BRAS-VM. $2: Upper alarm threshold configured for the online access user count. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_USER_UPPER_THRESHOLD: The user number on slot 97 is above the upper warning threshold (UpperThreshold=20%). |
|
Impact |
· The performance pressure on the slot might increase, and the services for online BRAS users might be affected. The number of online BRAS users on the specified slot might exceed the device capability, and the subsequent BRAS users might fail to come online. |
|
Cause |
· The upper threshold configured is too low. · Users come online, and the number of users on the specified slot exceeds the maximum number of user resources supported by the slot. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the CP to check the access-user bras-vm user-warning-threshold command, and identify whether the upper threshold configured is appropriate. ¡ If the upper threshold configured is too low, proceed with step 2. ¡ If the upper threshold configured is appropriate, proceed with step 3. 2. Execute the access-user bras-vm user-warning-threshold command in system view on the CP to modify the upper threshold for the configurable user resources. 3. Execute the display access-user slot command in any view on the CP to view the number of users on the specified slot. ¡ If the number of users reaches or approaches the upper threshold configured, add BRAS-VMs. ¡ If the number of users does not approach the upper threshold configured, proceed with step 4. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
|
Message text |
Slot-level alarm: The user number on UP [INT32] slot [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). Chip-level alarm: The user number on UP [INT32] slot [INT32] chip [INT32] is above the upper warning threshold (UpperThreshold=[INT32]). |
|
Variable fields |
$1: UP ID. $2: Slot number of a UP. $3: Chip number of a UP. This field is displayed only when the slot hosting the user access interface supports chip-level alarms. $4: Upper alarm threshold configured for the online access user count. |
|
Severity level |
4 (Warning) |
|
Example |
Slot-level alarm: UCM/4/UCM_USER_UPPER_THRESHOLD: The user number on UP 1024 slot 1 is above the upper warning threshold (UpperThreshold=20%). Chip-level alarm: UCM/4/UCM_USER_UPPER_THRESHOLD: The user number on UP 1024 slot 1 chip 0 is above the upper warning threshold (UpperThreshold=20%). |
|
Impact |
· The performance pressure on the card or chip in the UP might increase, and the services for online BRAS users might be affected. · The number of online BRAS users on the card or chip in the UP might exceed the device capability, and the subsequent BRAS users might fail to come online. |
|
Cause |
· The upper threshold configured is too low. · Users come online, and the number of users on the card or chip in the UP exceeds the maximum number of user resources supported by the card or chip. |
|
Recommended action |
1. Execute the display current-configuration command in any view on the CP to check the slot-user-warning-threshold command, and identify whether the upper threshold configured is appropriate. ¡ If the upper threshold configured is too low, proceed with step 2. ¡ If the upper threshold configured is appropriate, proceed with step 3. 2. In system view or UP-manage view on the CP, execute the slot-user- warning-threshold command to modify the upper threshold for configurable user resources. The configuration in system view applies to all UPs managed by the current CP, while the configuration in UP-manage view only applies to the current UP. The configuration in UP-manage view takes priority.) 3. Execute the display access-user user-plane command in any view on the UP to view the number of users on the specified interface module in the UP. ¡ If the number of users reaches or approaches the upper threshold configured, add subcards. ¡ If the number of users does not approach the upper threshold configured, proceed with step 4. 4. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_USER_LOGON_SUCCESS
|
Message text |
-UserName=[STRING]-IPv4Addr=[IPADDR]-IPv6Addr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]-RemoteTunnelIPAddr=[STRING]-RemoteTunnelName=[STRING]; The user came online successfully. |
|
Variable fields |
$1: Username. $2: User IPv4 address. $3: User IPv6 address. $4: Interface name. $5: Outer VLAN ID. $6: Inner VLAN ID. $7: MAC address. $8: Remote tunnel address. $9: Remote tunnel name. |
|
Severity level |
6 (Informational) |
|
Example |
UCM/6/UCM_USER_LOGON_SUCCESS: -UserName=user1-IPv4Addr=1.1.0.1-IPv6Addr=N/A-IfName=Bas-interface0-OuterVLAN=N/A-InnerVLAN=N/A-MACAddr=FFFF-FFFF-FFFF-RemoteTunnelIPAddr=123.1.1.2-RemoteTunnelName=LAC; The user came online successfully. |
|
Impact |
N/A |
|
Cause |
The users have successfully come online |
|
Recommended action |
No action is required. |
UCM_USER_LOGON_FAILED
|
Message text |
-UserName=[STRING]-IPv4Addr=[IPADDR]-IPv6Addr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]-RemoteTunnelIPAddr=[STRING]-RemoteTunnelName=[STRING]-Reason=[STRING]; The user failed to come online. |
|
Variable fields |
$1: Username. $2: User IPv4 address. $3: User IPv6 address. $4: Interface name. $5: Outer VLAN ID. $6: Inner VLAN ID. $7: MAC address. $8: Remote tunnel IP address. $9: Remote tunnel name. $10: Cause (see Table 15). |
|
Severity level |
6 (Informational) |
|
Example |
UCM/6/UCM_USER_LOGON_FAILED: -UserName=user1-IPv4Addr=N/A-IPv6Addr=N/A-IfName=Bas-interface0-OuterVLAN=N/A-InnerVLAN=N/A-MACAddr=FFFF-FFFF-FFFF-RemoteTunnelIPAddr=123.1.1.2-RemoteTunnelName=LNS1-Reason= Invalid username or password ; The user failed to come online. |
|
Impact |
A user failed to come online |
|
Cause |
For the online failure causes, see Table 15. |
|
Recommended action |
For more information, see Table 15. |
Table 20 Causes for failure to come online
|
Cause for failure to come online |
Remarks |
Recommended action |
|
The number of users on this interface has reached the upper limit |
The number of users on this interface has reached the upper limit. |
Use the access-limit command to adjust the maximum number of users allowed on an interface as needed. |
|
The number of users on this device has reached the upper limit |
The number of users on this device has reached the upper limit. |
Purchase a license that allows more users as needed. |
|
The VPN bound to the IPoE static user and the authorized VPN are different |
The VPN bound to the IPoE static user and the VPN authorized to the IPoE static user by AAA are different. |
Make sure the VPN bound to the IPoE static user and the VPN authorized to the IPoE static user by AAA are the same. |
|
Maximum concurrent users for the account has been reached |
The maximum number of concurrent users for the account has been reached. |
Adjust the maximum number of concurrent users for the account in one of the following methods: · Execute the users-per-account command in ISP domain view to adjust the maximum number of concurrent users for the account. · Use attribute 62 (port-limit) on the RADIUS server to adjust the maximum number of users to be provided to the account. |
|
The configured master interface has no backup subinterface |
During the UP hot backup or warm backup network, after the configured backup UP becomes a running active UP, a user cannot come online when the following conditions exist: · The user comes online through a subinterface on the running active UP. · The subinterface is not configured with a backup subinterface on the configured active UP. |
Verify that the VLAN of the subinterface of the interface on the configured active UP is the same as the VLAN of the interface on the configured backup UP. |
|
Only static leased users are permitted |
The interface is configured with static leased users, and other dynamic users cannot come online. |
Check the static leased user configuration. For users except static leased users to come online, execute the undo ip subscriber session static-leased command to delete the static leased user configuration. |
|
IPoE access mode or authentication method error |
A global static session with a PD prefix is configured on the interface, but the access mode is not Layer 2 access mode or the authentication method is not bind on the interface. Therefore, static users cannot come online. |
Verify that the access mode of the interface is Layer 2 access mode, and the bind authentication method is used on the interface. |
|
IPv6 PD prefix conflict |
IPv6 PD prefix conflict. |
Verify that the PD prefix configuration of the user is correct. For example, for a global static user, identify whether a session already exists with the IPv6 address in the global static session but a different PD prefix. |
For more information about additional causes of online failures and fault troubleshooting methods, see BRAS Service Troubleshooting Guide.
UCM_USER_LOGOFF
|
Message text |
-UserName=[STRING]-IPv4Addr=[IPADDR]-IPv6Addr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]-RemoteTunnelIPAddr=[STRING]-RemoteTunnelName=[STRING]-Reason=[STRING]; The user logged off. |
|
Variable fields |
$1: Username. $2: User IPv4 address. $3: User IPv6 address. $4: Interface name. $5: Outer VLAN ID. $6: Inner VLAN ID. $7: MAC address. $8: Remote tunnel IP address. $9: Remote tunnel name. $10: Cause (see Table 16). |
|
Severity level |
6 (Informational) |
|
Example |
UCM/6/UCM_USER_LOGOFF: -UserName=user1-IPv4Addr=1.1.0.1-IPv6Addr=N/A-IfName=Bas-interface0-OuterVLAN=N/A-InnerVLAN=N/A-MACAddr=FFFF-FFFF-FFFF-RemoteTunnelIPAddr=123.1.1.2-RemoteTunnelName=LNS1-Reason=user logoff; The user logged off. |
|
Impact |
N/A |
|
Cause |
The user went offline normally. |
|
Recommended action |
No action is required. |
Table 21 Causes for abnormally going offline
|
Cause for going offline |
Remarks |
|
Re-DHCP for IPoE Web authentication |
In a transparent MAC authentication application with re-DHCP enabled, a user successfully comes online in the Web authentication phase through a common Web authentication process first. After the device receives accounting reply packets from the AAA server, the DHCP user is forcibly logged out, so that the user can come online again through the transparent MAC authentication process. |
For more reasons for normal offline events, see BRAS Service Troubleshooting Guide.
UCM_USER_LOGOFF_ABNORMAL
|
Message text |
-UserName=[STRING]-IPv4Addr=[IPADDR]-IPv6Addr=[IPADDR]-IfName=[STRING]-OuterVLAN=[UINT16]-InnerVLAN=[UINT16]-MACAddr=[MAC]-RemoteTunnelIPAddr=[STRING]-RemoteTunnelName=[STRING]-Reason=[STRING]; The user logged off abnormally. |
|
Variable fields |
$1: Username. $2: User IPv4 address. $3: User IPv6 address. $4: Interface name. $5: Outer VLAN ID. $6: Inner VLAN ID. $7: MAC address. $8: Remote tunnel IP address. $9: Remote tunnel name. $10: Cause for going online. For possible values, see Table 17. |
|
Severity level |
6 (Informational) |
|
Example |
UCM/6/UCM_USER_LOGOFF_ABNORMAL: -UserName=user1-IPv4Addr=1.1.0.1-IPv6Addr=N/A-IfName=Bas-interface0-OuterVLAN=N/A-InnerVLAN=N/A-MACAddr=FFFF-FFFF-FFFF-RemoteTunnelIPAddr=123.1.1.2-RemoteTunnelName=LNS1-Reason=session time out; The user logged off abnormally. |
|
Impact |
The user went offline abnormally. |
|
Cause |
For the abnormal offline causes, see Table 17. |
|
Recommended action |
For more information, see Table 17. |
Table 22 Causes for abnormally going offline
|
Cause for going offline |
Remarks |
Recommended action |
|
Logged out by the RADIUS proxy |
For an 802.1X user and an IPoE user that come online through a wireless service in a RADIUS proxy network, the IPoE user goes offline when the 802.1X user goes offline. |
Troubleshoot the issue that the 802.1X user goes offline. |
|
UP switchover |
In the UP backup network, the active/standby UP switchover causes users to go offline. |
Contact Technical Support. |
|
UP switchover without backup interface |
In the UP hot backup or warm backup network, the active/standby UP switchover causes users without backup interfaces to go offline. |
· In warm backup mode: ¡ Verify that the backup-interface command has been executed to configure backup interfaces. ¡ If a user accesses through a subinterface, identify whether the subinterface has the corresponding backup subinterface. If yes, verify that the backup subinterface operates normally. · In hot backup mode, identify whether the subinterface through which the user comes online has a backup subinterface. If yes, verify that the backup subinterface operates normally. If yes, verify that the backup subinterface operates normally. |
|
UP backup status change |
The process of the module (for example, UP backup module) restarts or the active/standby switchover occurs, which causes the UP backup group state change. As a result, the users go offline. |
Identify whether the UP backup group state is normal. If the state is abnormal, verify that the UP backup configuration is correct. |
|
UP backup configuration change |
The UP backup configuration changes cause the users to go offline. |
Check the recent configuration changes. |
For more causes for abnormal offline events and fault troubleshooting methods, see BRAS Service Troubleshooting Guide.
UCM_USER_ONLINE_FAIL_ALARM (non-vBRAS-CPs)
|
Message text |
The number of online failure records is above the warning threshold. (OnlineFailThreshold=[INT32]). |
|
Variable fields |
$1: Alarm threshold for the user online failure count. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_USER_ONLINE_FAIL_ALARM: The number of online failure records is above the warning threshold. (OnlineFailThreshold=90). |
|
Impact |
If the user is valid, the user might fail to log in due to forgetting the username or password. If the user is invalid, network attacks might exist that deplete system resources. |
|
Cause |
· The alarm threshold for the number of user online failures within a certain period is too low. · The number of user online failures within a certain period reaches the alarm threshold. |
|
Recommended action |
1. Execute the display aaa online-fail-record command to view user online failure records. Analyze the user online failure reasons according to the user online failure records, identify whether the users go offline normally or abnormally, and resolve the issue in advance. 2. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
UCM_USER_ONLINE_FAIL_ALARM (vBRAS-CPs)
|
Message text |
The number of online failure records on slot [INT32] is above the warning threshold. (OnlineFailThreshold=[INT32]) |
|
Variable fields |
$1: Slot number of the master BRAS-VM. $2: Alarm threshold for the user online failure count. |
|
Severity level |
4 (Warning) |
|
Example |
UCM/4/UCM_USER_ONLINE_FAIL_ALARM: The number of online failure records on slot 97 is above the warning threshold. (OnlineFailThreshold=90). |
|
Impact |
If the user is valid, the user might fail to log in due to forgetting the username or password. If the user is invalid, network attacks might exist that deplete system resources. |
|
Cause |
· The threshold for the number of user online failures within a certain period is too low. · The number of user online failures within a certain period reaches the alarm threshold. |
|
Recommended action |
1. Execute the display aaa online-fail-record command to view user online failure records. Analyze the user online failure reasons according to the user online failure records, identify whether the users go offline normally or abnormally, and resolve the issue in advance. 2. If the issue persists, collect the following information, and then contact Technical Support. ¡ Results of each step. ¡ Configuration data, log messages, and alarm information. |
USER
This section contains service tracing messages.
USER_TRACEINFO
|
Message text |
[objectID=[UINT16]][slotID=[UINT16]][STRING][user info: [STRING] ][trace info:[STRING]] |
|
Variable fields |
$1: Service tracing object ID. $2: Slot number of the access user. $3: Service tracing phase. Possible values include PPPoE, L2TP, PPP, IPoE, portal, UCM, and AAA. $4: User information. For more information about user information, see Table 18. $5: Detailed service tracing information. For detailed service tracing information in each service tracing phase, see the following information: ¡ For detailed information in PPPoE phases, see Table 19. ¡ For detailed information in L2TP phases, see Table 20. ¡ For detailed information in PPP phases, see Table 21. ¡ For detailed information in IPoE phases, see Table 22. ¡ For detailed information in portal phases, see Table 23. ¡ For detailed information in UCM phases, see Table 24. ¡ For detailed information in AAA phases, see Table 25. ¡ For detailed information in DHCP phases, see Table 26. ¡ For detailed information in ARP phases, see Table 27. ¡ For detailed information in ND phases, see Table 28. ¡ For detailed information in IGMP phases, see Table 29. ¡ For detailed information in MLD phases, see Table 30. |
|
Severity level |
7 (Debug) |
|
Example |
USER/7/USER_TRACEINFO:[objectID=1][slotID=0][UCM][user info: MAC address: 0000-0000-0020 IP address: 2.2.2.8 Access interface: GigabitEthernet1/0/1 User name: 2.2.2.8 Access mode: IPoE ] [trace info:[Adapt State]UserID:4, ConnectID:0, Receive MODIFY event, current state is ADDED] |
|
Impact |
The impact on the system depends on the actual situation. |
|
Cause |
The service tracing object with ID 1 in the UCM phase received a MODIFY event message from GigabitEthernet 1/0/1 in slot 1. |
|
Recommended action |
No action is required. |
Traced user information description table
Table 23 Traced user information description table
|
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. |
|
Tunnel ID |
L2TP tunnel 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. |
Detailed information of traced objects
1. PPPoE
Table 24 Detailed information of traced objects (PPPoE)
|
Field |
Description |
|
Received a PADI packet |
The PPPoE sever received a PADI packet from the PPPoE client. |
|
Sent a PADO packet |
The PPPoE sever sent a PADO packet to the PPPoE client. |
|
Received a PADR packet |
The PPPoE sever received a PADR packet from the PPPoE client. |
|
Established a PPPoE session successfully. Notified PPP to create session (session ID=sessionid) |
A PPPoE session was successfully established. UCM notified PPP to create the session with the specified session ID. |
|
Sent a PADS packet |
The PPPoE sever sent a PADS packet to the PPPoE client. |
|
Established a PPPoE session successfully. Notified PPP to start session negotiation (session ID=sessionid) |
A PPPoE session was successfully established. UCM notified PPP to start session negotiation with the specified session ID. |
|
Received a PADT packet |
The PPPoE sever received a PADT packet from the PPPoE client or the PPPoE agency received a PADT packet from the PPPoE server. |
|
Deleted the PPPoE session successfully. |
The PPPoE session was successfully deleted. |
|
Sent a PADT packet |
The PPPoE sever sent a PADT packet to the PPPoE client or the PPPoE agency sent a PADT packet to the PPPoE server. |
|
Sent a PADI packet |
The PPPoE agency sent a PADI packet to the PPPoE server. |
|
Received a PADO packet |
The PPPoE agency received a PADO packet from the PPPoE server. |
|
Sent a PADR packet |
The PPPoE agency sent a PADR packet to the PPPoE server. |
|
Received a PADS packet |
The PPPoE agency received a PADS packet from the PPPoE server. |
|
Deleted the PPPoEA session successfully. |
The PPPoEA session was successfully deleted. |
2. L2TP
Table 25 Detailed information of traced objects (L2TP)
|
Field |
Description |
|
PPP notified LAC up and L2TP started a tunnel establishment process |
PPP notified the LAC up event, and the LAC started L2TP tunnel negotiation. |
|
PPP notified LAC up and L2TP started establishing a session within a middle state L2TP tunnel |
PPP notified the LAC up event, and the LAC started L2TP session negotiation in an L2TP tunnel in a middle state. |
|
PPP notified LAC up and L2TP started establishing a session within an L2TP tunnel |
PPP notified the LAC up event, and the LAC started L2TP session negotiation in an established L2TP tunnel. |
|
Sent an ICRQ packet to LNS, TunnelID=tunnelid, SessionID=sessionid |
The LAC sent an ICRQ to the LNS. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
Received an ICRP packet, TunnelID=tunnelid, SessionID=sessionid |
The LAC received an ICRP packet. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
Sent an ICCN packet to LNS, TunnelID=tunnelid, SessionID=sessionid |
The LAC sent an ICCN packet to the LNS. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
Received an ICCN packet and processed successfully, TunnelID=tunnelid, SessionID=sessionid |
The LNS received an ICCN packet and successfully processed the packet. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
Received an invalid ICCN packet and failed to process it, TunnelID=tunnelid, SessionID=sessionid |
The LNS received an ICCN packet and failed to process the packet. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
Received an ICCN packet but failed to allocate resources, TunnelID=tunnelid, SessionID=sessionid |
The LNS received an ICCN packet, and failed to process the packet due to insufficient resources. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
Received an ICCN packet but failed to process it, TunnelID=tunnelid, SessionID=sessionid |
The LNS received an ICCN packet but failed to process the packet. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
An L2TP session on LAC was going offline, TunnelID=tunnelid, SessionID=sessionid |
An L2TP session on the LAC was going offline. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
An L2TP session on LNS was going offline, TunnelID=tunnelid, SessionID=sessionid |
An L2TP session on the LNS was going offline. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
Sent a CDN packet to the peer, TunnelID=tunnelid, SessionID=sessionid |
The local end sent a CDN packet to the peer. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
|
Received a CDN packet, TunnelID=tunnelid, SessionID=sessionid |
The local end received a CDN packet to the peer. |
|
Deleted an L2TP session, TunnelID=tunnelid, SessionID=sessionid |
A local L2TP session was deleted. The parameters are as follows: · TunnelID—L2TP tunnel ID. · SessionID—L2TP session ID. |
3. PPP
Table 26 Detailed information of traced objects (PPP)
|
Field |
Description |
|
Received interface up event |
PPP received interface up event. |
|
LCP FSM open event |
The PPP LCP state machine was opened. |
|
Determined negotiation parameters during LCP initialization |
PPP determined negotiation parameters during LCP initialization. |
|
LCP FSM up event |
The PPP LCP state machine came up. |
|
Sent an LCP Configuration Request packet |
PPP sent an LCP Configure-Request packet. |
|
Received an LCP negotiation packet or Echo keepalive packet |
PPP received an LCP negotiation packet or Echo keepalive packet. |
|
Received an LCP Configuration Request packet |
PPP received an LCP Configure-Request packet. |
|
Sent an LCP Configuration Ack packet |
PPP sent an LCP Configure-Ack packet. |
|
Received an LCP Configuration Ack packet |
PPP received an LCP Configure-Ack packet. |
|
LCP up event |
PPP LCP negotiation succeeded. |
|
LCP FSM down event |
The PPP LCP state machine went down. |
|
LCP down event |
PPP received an LCP down event. |
|
LCP FSM close event |
The PPP LCP state machine was closed. |
|
Started authentication after LCP negotiation succeeded |
PPP LCP negotiation succeeded and entered the authentication phase. |
|
Sent a CHAP Challenge packet |
PPP sent a Challenge packet in the PPP CHAP authentication phase. |
|
Received a CHAP authentication packet in authentication phase |
PPP received a CHAP authentication packet in the authentication phase. |
|
Received a CHAP Request packet |
PPP received a CHAP request packet. |
|
Sent an authentication request to UCM |
PPP sent an authentication request to UCM for authentication. |
|
Received a CHAP authentication success message from AAA |
PPP received a CHAP authentication success message from AAA. |
|
Sent a CHAP Ack packet |
PPP sent a CHAP ACK packet to the client. |
|
CHAP authentication succeeded |
PPP CHAP authentication succeeded. |
|
Received a CHAP authentication failure message from AAA |
PPP received a CHAP authentication failure message from AAA. |
|
Sent a CHAP Nak packet |
PPP sent a CHAP NAK packet to the client. |
|
Received a PAP authentication packet in authentication phase |
PPP received a PAP authentication packet in the authentication phase. |
|
Received a PAP Request packet |
PPP received a PAP request packet. |
|
Received a PAP authentication success message from AAA |
PPP received a PAP authentication success message from AAA. |
|
Sent a PAP Ack packet |
PPP sent a PAP ACK packet to the client. |
|
PAP authentication succeeded |
PPP PAP authentication succeeded |
|
PAP authentication failed |
PPP PAP authentication failed |
|
Received a PAP authentication failure message from AAA |
PPP received a PAP authentication failure message from AAA. |
|
Sent a PAP Nak packet |
PPP sent a PAP NAK packet to the client. |
|
Received an LCP Termination Request packet |
PPP received an LCP termination request packet. |
|
Sent an LCP Termination Ack packet |
PPP sent an LCP termination ACK packet. |
|
Started NCP negotiation |
PPP entered the NCP negotiation phase. |
|
IPCP FSM open event |
The PPP IPCP state machine is opened. |
|
Determined negotiation parameters during IPCP initialization |
The IPCP negotiation parameters are initialized. |
|
IPCP FSM up event |
The PPP IPCP state machine is up. |
|
Sent an IPCP Configuration Request packet |
PPP sent an IPCP configuration request packet. |
|
Received an IPCP negotiation packet in IPCP negotiation phase |
PPP received an IPCP negotiation packet in IPCP negotiation phase. |
|
Received an IPCP Configuration Request packet |
PPP received an IPCP configuration request packet. |
|
Received an IPCP Configuration Ack packet |
PPP received an IPCP configuration ACK packet. |
|
Sent an IPCP Configuration Nak packet |
PPP sent an IPCP configuration NAK packet. |
|
Sent an IPCP Configuration Ack packet |
PPP sent an IPCP configuration ACK packet. |
|
IPCP negotiation succeeded |
PPP IPCP negotiation succeeded. |
|
Sent an LCP Echo Request packet |
PPP sent an LCP echo request packet. |
|
Received an LCP Echo Reply packet |
PPP received an LCP echo reply packet. |
|
Received interface down event |
PPP received interface down event. |
|
IPCP FSM down event |
The PPP IPCP state machine went down. |
|
IPCP down event |
PPP received an IPCP down event. |
|
IPCP FSM close event |
The PPP IPCP state machine was closed. |
|
Notify NCP down |
LCP notified the upper layer protocol of the NCP down event. |
|
PPP L2TP prenego started |
PPP L2TP prenegotiation started. |
|
PPP L2TP prenego finished |
PPP L2TP prenegotiation ended. |
|
Mandatory-lcp, LCP renego started |
LCP renegotiation was mandatory, and LCP renegotiation started. |
|
Mandatory-chap, CHAP renego started |
CHAP authentication was mandatory, and CHAP authentication started. |
|
L2TP mandatory-chap needed the authentication mode of CHAP on VT |
Mandatory CHAP authentication was configured, but CHAP authentication was not configured on the VT interface. |
|
LCP prenego for L2TP failed |
LCP prenegotiation failed. |
|
PPP L2TP prenego CHAP started |
CHAP authentication prenegotiation started. |
|
PPP L2TP prenego CHAP finished |
CHAP authentication prenegotiation ended. |
|
PPP L2TP prenego PAP started |
PAP authentication prenegotiation started. |
|
PPP L2TP prenego PAP finished |
PAP authentication prenegotiation ended. |
|
PPP L2TP prenego MSCHAP started |
MSCHAP authentication prenegotiation started. |
|
PPP L2TP prenego MSCHAP finished |
MSCHAP authentication prenegotiation ended. |
|
PPP L2TP prenego authentication failed |
PPP L2TP authentication prenegotiation failed. |
|
Received an LCP Configuration Nak packet |
PPP received an LCP configuration NAK packet. |
|
Sent an LCP Configuration Nak packet |
PPP sent an LCP configuration NAK packet. |
|
Received an LCP Configuration Reject packet |
PPP received an LCP configuration reject packet. |
|
Sent an LCP Configuration Reject packet |
PPP sent an LCP configuration reject packet. |
|
Received an LCP Termination Ack packet |
PPP received an LCP termination ACK packet. |
|
Sent an LCP Termination Request packet |
PPP sent an LCP termination request packet. |
|
Received an LCP Code Reject packet |
PPP received an LCP code reject packet. |
|
Sent an LCP Code Reject packet |
PPP sent an LCP code reject packet. |
|
Received an LCP Protocol Reject packet |
PPP received an LCP protocol reject packet. |
|
Sent an LCP Protocol Reject packet |
PPP sent an LCP protocol reject packet. |
|
Received an LCP Echo Request packet |
PPP received an LCP echo request packet. |
|
Sent an LCP Echo Reply packet |
PPP sent an LCP echo reply packet. |
|
Received an LCP Identification packet |
PPP received an LCP identification packet. |
|
Sent an LCP Identific packet |
PPP sent an LCP identification packet. |
|
Received an IPCP Configuration Nak packet |
PPP received an IPCP configuration NAK packet. |
|
Sent an IPCP Configuration Reject packet |
PPP sent a IPCP configuration reject packet. |
|
Received an IPCP Configuration Reject packet |
PPP received a IPCP configuration reject packet. |
|
Sent an IPCP Termination Request packet |
PPP sent a IPCP termination request packet. |
|
Received an IPCP Termination Request packet |
PPP received a IPCP termination request packet. |
|
Sent an IPCP Termination Ack packet |
PPP sent a IPCP termination ACK packet. |
|
Received an IPCP Termination Ack packet |
PPP received a IPCP termination ACK packet. |
|
Sent an IPCP Code Reject packet |
PPP sent a IPCP code reject packet. |
|
Received an IPCP Code Reject packet |
PPP received a IPCP code reject packet. |
|
Sent a CHAP Request packet |
PPP sent a CHAP request packet. |
|
Received a CHAP Challenge packet |
PPP received a CHAP challenge packet. |
|
Received a CHAP Ack packet |
PPP received a CHAP ACK packet. |
|
Received a CHAP Nak packet |
PPP received a CHAP NAK packet. |
|
Sent a MS-CHAP-V2 CHGPWD packet |
PPP sent an MS-CHAP-V2 change password packet. |
|
Received a PAP Ack packet |
PPP received a PAP ACK packet. |
|
Received a PAP Nak packet |
PPP received a PAP NAK packet. |
|
Sent a PAP Request packet |
PPP sent a PAP request packet. |
|
Authentication failed |
Authentication failed. |
|
Authentication succeeded |
Authentication succeeded. |
|
CHAP authentication failed |
CHAP authentication failed. |
|
Received an authentication failure message from UCM |
PPP received an authentication failure message from UCM. |
|
Received an authentication success message from UCM |
Received an authentication success message from UCM. |
|
Sent a conn request to UCM |
PPP sent a connection request to UCM. |
|
Sent a conn-down request to UCM |
PPP sent a connection-down request to UCM. |
|
Sent a conn-up request to UCM |
PPP sent a connection-up request to UCM. |
|
Sent an MP bundle request to UCM |
PPP sent an MP bundle request to UCM. |
|
Sent an offline request to UCM |
PPP sent an offline request to UCM. |
4. IPoE
Table 27 Detailed information of traced objects (IPoE)
|
Field |
Description |
|
Received an IP packet, VPN=vpn |
IPoE received a n user IP packet. The VPN indicates the VPN instance to which the user belongs. If the user is in a public network, the VPN field is not displayed. |
|
Sent a packet to UCM for authentication, VPN=vpn |
IPoE sent a packet to UCM for authentication. The VPN indicates the VPN instance to which the user belongs. If the user is in a public network, the VPN field is not displayed. |
|
Received a Reject message from UCM, VPN=vpn |
IPoE received a reject message from UCM. The VPN indicates the VPN instance to which the user belongs. If the user is in a public network, the VPN field is not displayed. |
5. Portal
Table 28 Detailed information of traced objects (Portal)
|
Field |
Description |
|
Sent logon request to UCM |
Portal sent a logon request to UCM. |
|
Received logon success message from UCM |
Portal received a logon success message from UCM. |
|
Received logon failure message from UCM |
Portal received a logon failure message from UCM. |
|
Sent logoff request to UCM |
Portal sent a logoff request to UCM. |
|
Received logoff response from UCM |
Portal received a logoff response from UCM. |
|
Received forced-logoff message from UCM |
Portal received a forced-logoff message from UCM. |
|
Received message for user information transparent transmission from UCM |
Portal received a message for user information transparent transmission from UCM. |
|
Received MAC binding query request from IPoE |
Portal received a MAC binding query request from IPoE. |
|
Sent MAC binding query response to IPoE |
Portal sent a MAC binding query response to IPoE. |
|
Received MAC-trigger user online message from UCM |
Portal received a MAC-trigger user online message from UCM. |
|
Received MAC-trigger user offline message from UCM. |
Portal received a MAC-trigger user offline message from UCM. |
|
Received user roaming message from UCM |
Portal received a user roaming message from UCM. |
|
Received authentication-continue message from UCM |
Portal received an authentication-continue message from UCM. |
|
Received packet from portal server newpt |
UCM received a packet from the portal server newpt. |
|
Sent packet to portal server newpt |
UCM sent a packet to the portal server newpt. |
|
Ver |
Portal protocol packet version number: · 1.0. · 2.0. · 3.0. |
|
Type |
Portal protocol packet type: · REQ_CHALLENGE · ACK_CHALLENGE · REQ_AUTH · ACK_AUTH · REQ_LOGOUT · ACK_LOGOUT · AFF_ACK_AUTH · NTF_LOGOUT · REQ_INFO · ACK_INFO · NTF_USER_DISCOVER · NTF_USER_IP_CHANGE · AFF_NTF_USER_IP_CHANGE · ACK_NTF_LOGOUT · NTF_HEART · NTF_USER_HEART · ACK_NTF_USER_HEART · NTF_CHALLENGE · NTF_USER_NOTIFY · AFF_NTF_USER_NOTIFY · REQ_MACBIND_INFO · ACK_MACBIND_INFO · NTF_USER_LOGON · NTF_USER_LOGOUT · REQ_USER_OFFLINE · UNKNOWN |
|
Method |
Portal authentication method: · EAP. · CHAP. · PAP. |
|
SerialNo |
Portal packet sequence number. |
|
ReqID |
Portal packet request ID. |
|
UserIP |
Portal user IP address. |
|
ErrCode |
Error code. |
|
AttrNum |
Number of attributes carried in the portal packet. |
6. UCM
Table 29 Detailed information of traced objects (UCM)
|
Field |
Description |
|
Failed to send msgtype. |
UCM failed to send message of the msgtype type to PAM. Possible msgtype values include: · UCM_UIA_PAM_MSG_COA—Change of Authorization (COA) messages, which are used to change the user's authorization information. · UCM_UIA_PAM_MSG_DM—Disconnect messages (DM), which are used to log out users. |
|
UserID: userid, VASID: vasid, Received AAA reply (MsgType: msgtype) |
UCM received a reply from AAA. The parameters are as follows: · UserID—User ID. · VASID—Value-added service ID (ITA service accounting level or EDSG service ID) · MsgType—Message type. Possible values include: ¡ AUTH_REQ_ACK. ¡ AUTH_REQ_REJ. ¡ AUTH_REQ_CONTINUE. ¡ AUTHOR_REQ_ACK. ¡ AUTHOR_REQ_REJ. ¡ ACCT_START_ACK. ¡ ACCT_START_REJ. ¡ ACCT_START_BROADCAST_ACK. ¡ ACCT_UPDATE_ACK. ¡ ACCT_UPDATE_REJ. ¡ ACCT_UPDATE_BROADCAST_ACK. ¡ ACCT_STOP_ACK. ¡ ACCT_STOP_REJ. ¡ ACCT_STOP_BROADCAST_ACK. ¡ DM_REQ. ¡ COA_REQ. ¡ DOMAIN_CUT. ¡ GET_DATA. |
|
UserID: userid, Sent account start request to AAA |
UCM sent an accounting start request to AAA. |
|
UserID: userid, Sent account update request to AAA |
UCM sent an accounting update request to AAA. |
|
UserID: userid, ConnectID: connectid, Received msgname from accessname. |
UCM received a message named msgname from access method accessname. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. · accessname—Access method name. Possible values include: ¡ PPP—PPP access. ¡ IPOE4—IPv4 IPoE access. ¡ DHCP4—DHCPv4 access. ¡ IPOE6—IPv6 IPoE access. ¡ DHCP6—DHCPv6 access. ¡ ARP—ARP access. ¡ NDRS—NDRS access. ¡ NDNS—NDNS access. ¡ IPOEWEB—IPoE Web access. ¡ L2IFLEASE—Layer 2 IPoE interface-leased access. ¡ L3IFLEASE—Layer 3 IPoE interface-leased access. ¡ L3SUBLEASE—Layer 3 IPoE subnet-leased access. ¡ L2VPNLEASE—IPoE L2VPN-leased access. ¡ PAM—PAM access. ¡ DOT1X—802.1X access. · msgname—Message name. Possible values include: ¡ UCM_UIA_PPP_MSG_AUTH_REQ—PPP authentication request. ¡ UCM_UIA_PPP_MSG_CONN_REQ—PPP connection request. ¡ UCM_UIA_PPP_MSG_CONN-UP_REQ—PPP connection-up request. ¡ UCM_UIA_PPP_MSG_CONN-DOWN_REQ—PPP connection-down request. ¡ UCM_UIA_PPP_MSG_OFFLINE_REQ—PPP offline request. ¡ UCM_UIA_PPP_MSG_OFFLINE_INF—PPP offline information. ¡ UCM_UIA_IPOEIP4_MSG_CONN_REQ—IPv4 IPoE connection request. ¡ UCM_UIA_IPOEIP6_MSG_CONN_REQ—IPv6 IPoE connection request. ¡ UCM_UIA_IPOEIP6_MGG_CONN_MODIFYUSR_NTF—IPv6 IPoE username modification notification. ¡ UCM_UIA_DHCP_MSG_CONN_REQ—DHCPv4 connection request. ¡ UCM_UIA_DHCP_MSG_CONN-UP_REQ—DHCPv4 connection-up request. ¡ UCM_UIA_DHCP_MSG_RENEW_REQ—DHCPv4 renewal request. ¡ UCM_UIA_DHCP_MSG_CONN-DOWN_REQ—DHCPv4 connection-down request. ¡ UCM_UIA_DHCP_MSG_DISCONN_INF—DHCPv4 disconnection information ¡ UCM_UIA_DHCP6_MSG_CONN_REQ—DHCPv6 connection request ¡ UCM_UIA_DHCP6_MSG_CONN-UP_REQ—DHCPv6 connection-up request ¡ UCM_UIA_DHCP6_MSG_RENEW_REQ—DHCPv6 connection renewal request. ¡ UCM_UIA_DHCP6_MSG_CONN-DOWN_REQ—DHCPv6 connection-down request. ¡ UCM_UIA_DHCP6_MSG_DISCONN_INF—DHCPv6 disconnection information ¡ UCM_UIA_ARP_MSG_CONN_REQ—ARP connection request ¡ UCM_UIA_ARP_MSG_CONN-UP_REQ—ARP connection-up request ¡ UCM_UIA_ARP_MSG_DTC_TIMEOUT—ARP detection timeout. ¡ UCM_UIA_NDRS_MSG_CONN_REQ—NDRS connection request ¡ UCM_UIA_NDRS_MSG_CONN-UP_REQ—NDRS connection-up request ¡ UCM_UIA_NDRS_MSG_MODIFYUSRIP_REQ—NDRS user IP modification request. ¡ UCM_UIA_NDNSNA_MSG_CONN_REQ—NDNS connection request ¡ UCM_UIA_NDNSNA_MSG_CONN-UP_REQ—NDNS connection-up request ¡ UCM_UIA_ND_MSG_DTC_TIMEOUT—NDNS detection timeout ¡ UCM_UIA_PORTAL_MSG_AUTH_REQ—IPoE Web authentication request. ¡ UCM_UIA_PORTAL_MSG_AUTH_REQ_CONTINUE—IPoE Web continuous authentication request ¡ UCM_UIA_PORTAL_MSG_DISCONN_REQ—IPoE Web authentication disconnection request ¡ UCM_UIA_PORTAL_MSG_DISCONN_INF—IPoE Web authentication disconnection information ¡ UCM_UIA_PORTAL_MSG_SERVERINFO—IPoE Web authentication server information. ¡ UCM_UIA_PORTAL_MSG_ROAM—IPoE Web user roaming. ¡ UCM_UIA_PORTAL_MSG_MT_ONLINE—IPoE Web user online information. ¡ UCM_UIA_PORTAL_MSG_MT_OFFLINE—IPoE Web user offline information. ¡ UCM_UIA_LEASE_MSG_CONN_REQ—IPoE leased connection request ¡ UCM_UIA_LEASE_MSG_CONN-UP_REQ—IPoE leased connection-up request ¡ UCM_UIA_LEASE_MSG_CONDOWN_REQ—IPoE leased connection-down request ¡ UCM_UIA_PAM_MSG_AUTH_REQ—PAM authentication request ¡ UCM_UIA_PAM_MSG_ACCT_START_REQ—PAM accounting start request. ¡ UCM_UIA_PAM_MSG_ACCT_UPDATE_REQ—PAM accounting update request. ¡ UCM_UIA_PAM_MSG_ACCT_STOP_REQ—PAM accounting stop request. ¡ UCM_UIA_PAM_MSG_USER_DELETE—PAM user deletion. ¡ UCM_UIA_PAM_MSG_USER_RECOVER—PAM user recovery. ¡ UCM_UIA_PAM_MSG_GETDATA_ACK—PAM data getting ACK. ¡ UCM_UIA_PAM_MSG_SMOOTH_USERDELETE—PAM user deletion sync. ¡ UCM_UIA_DOT1X_MSG_AUTH_REQ—802.1X authentication request. ¡ UCM_UIA_DOT1X_MSG_AFF_ACK_AUTH—802.1X reauthentication request. ¡ UCM_UIA_DOT1X_MSG_DISCONN_REQ—802.1X disconnection request. ¡ UCM_UIA_DOT1X_MSG_PRIORITY_AUTH_REJ—802.1X-authentication-first rejection. ¡ UCM_UIA_DOT1X_MSG_SMOOTH_USERDELETE—802.1X user deletion sync. |
|
UserID: userid, Sent RejMsg to Access, Reason: cause |
Sent a Reject message to the access module. The parameters are as follows: · UserID—User ID. · Cause—Failure reason. In the current software version, only the Static user not config reason is supported, which means IPoE static users are not configured. |
|
[Adapt State]UserID: userid, ConnectID: connectid, Received event event, current state is state. |
Adapter state machine received an event of the even type, and the current state is state. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. · event—Adapter state machine event. Possible values include: ¡ ADD—Add. ¡ MODIFY—Modify information. ¡ DEL—Delete. ¡ TRAFFIC_DELCOMPLETE—Traffic deletion completed. ¡ PROXY_DELCOMPLETE—Issuing to the interface module for deletion completed. ¡ FWD-DELCOMPLETE—Issuing to the kernel for deletion completed. ¡ FWD-SUCC—Successfully issued to the kernel. ¡ FWD-FAIL—Failed to be issued to the kernel. ¡ PROXY-SUCC—Successfully issued to the interface module. ¡ PROXY-FAIL—Failed to be issued to the interface module. · state—Current state. Possible values include: ¡ INIT—Initial. ¡ FWD—Issued to the kernel. ¡ FWD-MODIFY—Issued to the kernel for modifying information. ¡ PROXY—Issued to the interface module and backup interface module. ¡ PROXY-MODIFY—Issued to the interface module for modifying information. ¡ ADDED—Successfully added. ¡ DELETING—Deleting. |
|
[Adapt State]UserID: userid, ConnectID: connectid, Received event event, State changed from oldstate to newstate |
Adapter state machine received an event of the event type, and the state changed from oldstate to newstate. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. For values, see the ConnectionID in the preceding message. · event—Adapter state machine event. For values, see the event field in the preceding message. · oldstate—State before the switching. For values, see the state field in the preceding message. · newstate—State after the switching. For values, see the state field in the preceding message. |
|
[Conn state]UserID: userid, ConnectID: connectid, Received event event, Current state is state. |
The connection state machine received an event of the event type, and the current state is state. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. · event—Connection state machine event. Possible values include: ¡ USER-AUTH-PASSED—The user passed authentication. ¡ CONNREQ-PASSED—The connection request passed. ¡ ADDR-REQ-ACK—The address request passed. ¡ CONN-UP-WITH-NAT—Connection-up with the NAT event. ¡ CONN-UP-WITHOUT-NAT—Connection-up without the NAT event. ¡ NAT-REQ-ACK—The NAT request passed. ¡ USER-ADD-ACK—The user adding request passed. ¡ USER-DEL-ACK—The user deletion request passed. ¡ CLOSE—The connection is closed. ¡ DOWN —The connection is down. ¡ EXTRA-CONNREQ—Extra connection request ¡ EXTRA-CONN-UP—Extra connection-up request ¡ RENEW—Connection renewal information (for example, leases). · state—Current state. Possible values include: ¡ INIT—Initialization. ¡ ADDR-REQ-SENT—Address request sent. ¡ AUTHED—Authenticated. ¡ NAT-REQ-SENT—NAT request sent. ¡ USER-ADDING—Adding users. ¡ OPEN—Connection established. ¡ DELETING—Deleting. ¡ DELETED—Deleted. |
|
[Conn State]UserID: userid, Received event event, State changed from oldstate to newstate. |
Connection state machine received an event of the event type, and the state changed from oldstate to newstate. The parameters are as follows: · UserID—User ID. · event—Connection state machine event. For values, see the event field in the preceding message. · oldstate—State before the switching. For values, see the state field in the preceding message. · newstate—State after the switching. For values, see the state field in the preceding message. |
|
[LOGOUT State]UserID: userid, Received event event, Current state is state. |
Logout state machine received an event of the event type, and the current state is state. The parameters are as follows: · UserID—User ID. · event—Logout state machine event. Possible values include: ¡ AUTHREQ—Authentication requested. ¡ AUTHSUCC—Authentication succeeded. ¡ USER_MODIFYACK—User modification succeeded. · state—Current state. Possible values include: ¡ INIT—Initialization. ¡ AUTHING—Authenticating. ¡ USER_UPDATE—User updated. |
|
[LOGOUT State]UserID: userid, Received event event, State changed from oldstate to newstate. |
Logout state machine received an event of the event type, and the state changed from oldstate to newstate. The parameters are as follows: · UserID—User ID. · event—Logout state machine event. For values, see the event field in the preceding message. · oldstate—State before the switching. For values, see the state field in the preceding message. · newstate—State after the switching. For values, see the state field in the preceding message. |
|
[Reauth State]UserID: userid, Received event event, Current state is state. |
Reauthentication state machine received an event of the event type, and the current state is state. The parameters are as follows: · UserID—User ID. · event—Reauthentication state machine event. Possible values include: ¡ AUTHREQ—Authentication requested. ¡ AUTHSUCC—Authentication succeeded. ¡ AUTHCONTINUE—The user authentication continues. ¡ AUTH-FAIL—Authentication failed. ¡ USER_MODIFYACK—User service parameters modified. ¡ USER_MODIFYREJ—User service parameter modification rejected. ¡ WEB_AUTHACK_RESP—Web authentication ACK replied. ¡ MACAUTH_ACK—MAC authentication succeeded. ¡ DOWN—UCM received a disconnection request. · state—Current state. Possible values include: ¡ INIT—Initialization. ¡ AUTHING—Authenticating. ¡ USER_UPDATE—User data updated. ¡ WAIT_WEBRESP_ACK—Waiting for ACK from Web ¡ WAIT_MACAUTH_ACK—Waiting for ACK from MAC authentication |
|
[Reauth State]UserID: userid, Received event event, State changed from oldstate to newstate. |
Reauthentication state machine received an event of the event type, and the state changed from oldstate to newstate. The parameters are as follows: · UserID—User ID. · event—Reauthentication state machine event. For values, see the event field in the preceding message. · oldstate—State before the switching. For values, see the state field in the preceding message. · newstate—State after the switching. For values, see the state field in the preceding message. |
|
[Shell Phase]UserID: userid, ConnectID: connectid, Received event event, Current phase is phase. |
Shell state machine received an event of the event type, and the current state is phase. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. · event—Shell state machine event. Possible values include: ¡ AUTH-REQ—Authentication request. ¡ CONN-REQ—UCM received a connection request. ¡ CONN-UP—Connection-up request. ¡ CONN-DOWN—Connection-down request. ¡ RENEW-REQ—Connection renewal request (for example, lease) ¡ MODIFY-USERIP—User IP modification. ¡ DISCONN-REQ—Disconnection request. ¡ MPBIND-REQ—MP bundling request. ¡ ACCT-START-REQ—Accounting start request. ¡ ACCT-UPDATE-REQ—Accounting update request. ¡ ACCT-STOP-REQ—Accounting stop request. ¡ RECOVER-REQ—Recovery request. ¡ GETDATA-ACK—Processing GetData ACK. ¡ WEB-AUTHREQ—Web authentication request ¡ WEB-AUTHACK-RESPONSE—Web authentication ACK response. ¡ DOWN-REQ—Down request. ¡ STOP-MT—Stop MAC transparent authentication. ¡ MAC-AUTH—MAC authentication. ¡ TERMINATE—User termination. ¡ GROUPID-CHG—Group ID change. ¡ AUTH-SUCC—Authentication success. ¡ AUTH-FAIL—Authentication failure. ¡ AUTH-CONTINUE—User authentication continued. ¡ ACC-START-SUCC—Accounting start succeeded. ¡ ACC-START-FAIL—Accounting start failed. ¡ ACC-UPDATE-SUCC—Accounting update succeeded. ¡ ACC-STOP-FAIL—Accounting stop failed. ¡ ACCESS-MSG-PASS—Access message passed. ¡ MPBIND-SUCCESS—MP bundling succeeded. ¡ MPBIND-FAILURE—MP binding failed. ¡ PAM-AUTH-SUCC—PAM authentication succeeded. ¡ PAM-AUTH-FAIL—PAM authentication failed. ¡ PAM-AUTH-CONTINUE—PAM authentication continued. ¡ PAM-ACCT-START-SUCC—PAM accounting start succeeded. ¡ PAM-ACCT-START-FAIL—PAM accounting start failed. ¡ PAM-ACCT-UPDATE-SUCC—PAM accounting update succeeded. ¡ PAM-ACCT-UPDATE-FAIL—PAM accounting update failed. ¡ PAM-ACCT-STOP-SUCC—PAM accounting stop succeeded. ¡ PAM-ACCT-STOP-FAIL—PAM accounting stop failed. ¡ COA—Authentication information changed. ¡ MODIFY-ACK—Modification succeeded. ¡ NEGSLOTCHG—User negotiation slot changed. ¡ TERMINATE—User termination. ¡ ADDRREQ-ACK—Address request succeeded. ¡ ADDRREQ-REJ—Address request failed. ¡ NATREQ-ACK—NAT event request succeeded. ¡ NATREQ-REJ—NAT event request failed. ¡ FWD-SYNC-SUCC—Forwarding entry adding succeeded. ¡ FWD-SYNC-FAIL—Forwarding entry adding failed. ¡ PROXY-SYNC-SUCC—Notifying the interface module to add forwarding entries succeeded. ¡ PROXY-SYNC-FAIL—Notifying the interface module to add forwarding entries failed. ¡ FWD-SYNC-DELCOMPLETE—Deleting users in the kernel completed. ¡ PROXY-SYNC-DELCOMPLETE—Deleting users on the interface module completed. ¡ AUTH-PASS—Authentication passed. ¡ ADAPT-ADD-ACK—Adding users succeeded. ¡ ADAPT-ADD-REJ—Adding users rejected. ¡ ADAPT-MODIFY-ACK—User modification succeeded. ¡ ADAPT-MODIFY-REJ—User modification rejected. ¡ UP—A user came online. ¡ ADAPT-DEL-ACK—A user was successfully deleted. ¡ DEL-COMPLETE—Deletion completed. ¡ REAUTH-AUTH-PASS—Reauthentication passed. ¡ REAUTH-AUTH-CONTINUE—Reauthentication continued. ¡ REAUTH-AUTH-FAIL—Reauthentication failed. ¡ REAUTH-MACAUTH-SUCC—Reauthentication succeeded. ¡ REAUTH-COMPLETE—Reauthentication completed. ¡ REAUTH-DOWN—Reauthentication stopped. ¡ WEB-CLOSE—Web disconnection request. ¡ LOGOUT-AUTH-PASS—An IPoE Web user returned to the preauthentication phase from the Web authentication phase, and the authentication succeeded. ¡ LOGOUT-COMPLETE—An IPoE Web user successfully came online in the Web authentication phase. ¡ USER-MODIFY-ACK—User modification succeeded. ¡ OPEN—Connection completed. · phase—Current phase. Possible values include: ¡ INITIAL—Initialization phase. ¡ AUTHENTICATION—Authentication phase. AAA sent an authentication request but received no reply. ¡ AUTHED—Authenticated phase. An authentication success reply was received from AAA. ¡ NETWORK—Network negotiation phase. An IP address has been requested and starts to be issued to the kernel, interface module, and backup interface module. ¡ ONLINE—The user successfully came online. ¡ TERMINATE—The user went offline. ¡ REAUTH—Reauthentication phase. An IPoE web user performed authentication in the Web authentication phase. ¡ LOGOUT—Logout phase. An (IPoE web user returned back to the preauthentication phase from the web authentication phase. ¡ PRE_AUTHENTICATION—802.1X user authentication phase. ¡ PRE_AUTHED—802.1X user authentication completed phase. |
|
[Shell Phase]UserID: userid, ConnectID: connectid, Received event event, Phase changed from oldphase to newphase. |
The shell state machine received an event of the event type, and the state changed from oldphase to newphase. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. For values, see the ConnectionID in the preceding message. · event—Shell state machine event. For values, see the event field in the preceding message. · oldphase—State before the switching. For values, see the state field in the preceding message. · newphase—State after the switching. For values, see the state field in the preceding message. |
|
[User State]UserID: userid, Received event event, Current state is state. |
The user state machine received an event of the event type and the current state is state. The parameters are as follows: · UserID—User ID. · event—User state machine event. Possible values include: ¡ AUTHREQ—UCM received an access authentication request ¡ AUTHSUCC—UCM received a AAA authentication success event. ¡ AUTHSUCC-ADMIN—Management user authentication succeeded. ¡ AUTH-FAIL—UCM received an AAA authentication failure event. ¡ AUTH-CONTINUE—UCM received an AAA user authentication continual event. ¡ CONNREQ—UCM received an access connection request ¡ CONN-UP—UCM received a connection-up event. ¡ USERADD-ACK—User adding succeeded. ¡ USERDEL-ACK—User adding succeeded. ¡ CLOSE—Internal errors of UCM caused user to go offline. ¡ DOWN—Connection-down event initiated by access. ¡ MPBINDREQ—MP bundling request. ¡ MPBINDSUCCESS—MP bundling succeeded. ¡ MPBINDFAILURE—MP bundling failed. ¡ PAM_AUTHREQ—PAM authentication request ¡ PAM_ACCTSTARTREQ—PAM accounting start request. ¡ PAM_ACCTUPDATEREQ—PAM accounting update request. ¡ PAM_ACCTSTOPREQ—PAM accounting stop request. ¡ PAM_AUTHSUCCESS—PAM authentication succeeded. ¡ PAM_AUTHFAILURE—PAM authentication failed. ¡ PAM_AUTHCONTINUE—PAM user authentication failed. ¡ PAM_USERDELETE—PAM user deleted. ¡ REAUTH—IPoE Web preauthentication reauthenticated. ¡ REAUTH_SUCC—Reauthentication succeeded. ¡ REAUTH_FAIL—Reauthentication failed. ¡ LOGOUT—An IPoE Web user exited the postauthentication domain. ¡ LOGOUT_SUCC—An IPoE Web user successfully exited the postauthentication domain. ¡ MODIFY—User modified. ¡ MODIFY-ACK—User modified successfully. · state—Current state. Possible values include: ¡ INIT—Initialization. ¡ AUTHING—Authenticating. ¡ ALLOC—Intermediate state between authentication failure and user logout. Only PPP has this state. ¡ AUTHED—Authenticated. ¡ USER-ADDING—Intermediate state between issuing to the kernel and notifying the backup interface module and interface module. ¡ UP—Coming online successfully. ¡ DELETING—Deleting. ¡ DELETED—Deleted. ¡ BINDING—Binding phase (supported only by PPP MP) ¡ REAUTH—Reauthentication phase. An IPoE Web user performed authentication in the Web authentication phase. ¡ LOGOUT—An IPoE Web user returned to the preauthentication phase from the Web authentication phase. ¡ MODIFY—User authentication modification (COA). |
|
[User State]UserID: userid, Received event event, State changed from oldstate to newstate |
The user state machine received an event of the event type, and the state changed from oldstate to newstate. The parameters are as follows: · UserID—User ID. · event—User state machine event. For values, see the event field in the preceding message. · oldphase—State before the switching. For values, see the state field in the preceding message. · newphase—State after the switching. For values, see the state field in the preceding message. |
|
UserID userid group ID changed. |
The user group ID of the user changed. |
|
UserID: userid, Received assigned IP address ipaddr from AM. |
The user received an assigned IP address ipaddr from AM. |
|
UserID userid will be terminated, the cause is cause. |
The user connection will be terminated for the cause cause. |
|
UserID: userid, Sent authentication request to AAA, the access user type is type. |
UCM sent an authentication request to AAA. The parameters are as follows: · UserID—User ID. · type—User access type. Possible values include: ¡ PPPoE—PPP over Ethernet user. ¡ PPPoA—PPP over ATM user. ¡ PPPoFR—PPP over FR user. ¡ PPPoPhy—PPP user directly carried over a physical link. ¡ VPPP—L2TP user auto-dialed on a LAC. ¡ LNS—L2TP user on an LNS. ¡ MAC auth—MAC authentication user. ¡ Dot1x—802.1X user. ¡ Web auth—Web authentication user. ¡ Telnet—Telnet user. ¡ FTP—FTP user. ¡ Terminal—User logging in through the Console port, AUX port, or Asyn port. ¡ SSH—SSH user. ¡ Portal—Portal user. ¡ PAD—PAD user. ¡ Command—Command authorization and accounting user. ¡ Super—User that can switch the user role. ¡ IPoE L2VPN leased—IPoE L2VPN-leased user. ¡ NETCONF SOAP HTTP—HTTP web user. ¡ NETCONF RESTful HTTP—NETCONF over SOAP over HTTP user. ¡ HTTP Web—HTTP web user. ¡ NETCONF SOAP HTTPS—NETCONF over SOAP over HTTPS user. ¡ NETCONF RESTful HTTPS—NETCONF over RESTful over HTTPS user. ¡ HTTPS Web—HTTPS web user. ¡ L2 IPoE dynamic—Layer 2 IPoE dynamic user. ¡ L2 IPoE static—Layer 2 IPoE static user. ¡ L2 IPoE interface leased—Layer 2 IPoE interface-leased user. ¡ L2 IPoE leased subuser—Layer 2 leased subuser. ¡ L3 IPoE dynamic—Layer 3 IPoE dynamic user. ¡ L3 IPoE static—Layer 3 IPoE static user. ¡ L3 IPoE interface leased—Layer 3 IPoE interface-leased user. ¡ L3 IPoE subnet leased—Layer 3 subnet-leased user. ¡ IKE—IKE user. ¡ SSLVPN—SSL VPN user. ¡ DVPN—DVPN user. ¡ PPPoEA—PPPoE agency user. |
|
UserID: userid, session key: key, New SocketPAM (usertype) user is created. |
A socket PAM user was created. The parameters are as follows: · UserID—User ID. · session key—PAM access user index. · usertype—User type. Possible values include: ¡ Telnet—Telnet user. ¡ FTP—FTP user. ¡ Terminal—User logging in through the Console port, AUX port, or Asyn port. ¡ SSH—SSH user. ¡ PAD—PAD user. ¡ Command—Command authorizing and accounting user. ¡ Super—User that can switch the user role. |
|
UserID: userid, session key: key, New SessionPAM (usertype) user is created. |
A session PAM user was created. The parameters are as follows: · UserID—User ID. · session key—PAM access user index. · usertype—User type. Possible values include: ¡ NETCONF SOAP HTTPS—NETCONF over SOAP over HTTPS user. ¡ NETCONF RESTful HTTP—NETCONF over SOAP over HTTP user. ¡ HTTP Web—HTTP web user. ¡ NETCONF SOAP HTTPS—NETCONF over SOAP over HTTPS user. ¡ NETCONF RESTful HTTPS—NETCONF over RESTful over HTTPS user. ¡ HTTPS Web—HTTPS web user. ¡ IKE—IKE user. ¡ SSLVPN—SSL VPN user. ¡ DVPN—DVPN user. |
|
UserID: userid, session Key: key, New Portal user is created |
A portal user was created. The parameters are as follows: · UserID—User ID. · session key—PAM access user index. |
|
UserID: userid, ConnectID: connectid, New PPP user is created |
A PPP user was created. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. |
|
UserID: userid, ConnectID: connectid, New IPoE4 user is created |
An IPv4 IPoE user was created. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. |
|
UserID: userid, ConnectID: connectid, New IPoE6 user is created. |
An IPv6 IPoE user was created. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. |
|
UserID: userid, ConnectID: connectid, New leased user is created. |
An IPoE leased user was created. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. |
|
UserID: userid, ConnectID: connectid, New Dot1X user is created |
A user was created. The parameters are as follows: · UserID—User ID. · ConnectID—UCM connection type ID. Possible values include: ¡ 0—Auto-dialed L2TP connection on a LAC or L2TP connection and 802.1X user on an LNS. ¡ 1—DHCP, IPoE, or ARP connection. ¡ 2—DHCPv6, IPoEv6, or ND connection. ¡ 3—PPP, IP6CP, or ND connection. |
|
UserID: userid, UCM received COA request for PPPoEA from AAA. |
UCM received a COA request for PPPoE agency user from AAA. |
7. AAA
Table 30 Detailed information of traced objects (AAA)
|
Field |
Description |
|
Domain domain-name rejected the user. |
The domain name domain-name rejected the user. |
|
Domain domain-name is in blocked state. |
The domain named domain-name is in blocked state. |
|
The user failed to access domain domain-name because the maximum number of users already reached. |
The user failed to access the domain named domain-name because the maximum number of users was already reached. |
|
Received an authentication request. |
AAA received an authentication request from a UCM user. |
|
Received an accounting-start request. |
AAA received an accounting-start request from an UCM user. |
|
Received an accounting-update request. |
AAA received an accounting-update request from a UCM user. |
|
Received an accounting-stop request. |
AAA received an accounting-stop request from a UCM user. |
|
Received a get-data reply. |
AAA received a get-data reply from UCM. |
|
Received an LDAP authentication response. |
AAA received a LDAP authentication response packet. |
|
Received an LDAP authorization response. |
AAA received a LDAP authorization response packet. |
|
RADIUS authentication: Request initiated. |
RADIUS authentication: Request packet was initiated. |
|
RADIUS accounting start: Request initiated. |
RADIUS accounting start: Request packet was initiated. |
|
RADIUS accounting update: Request initiated. |
RADIUS accounting update: Request packet was initiated. |
|
RADIUS accounting stop: Request initiated. |
RADIUS accounting stop: Request packet was initiated. |
|
RADIUS accounting start: Failed. Reason: reason. |
RADIUS accounting start failed for the reason reason. |
|
RADIUS accounting update: Failed. Reason: reason. |
RADIUS accounting update failed for the reason reason. |
|
RADIUS accounting stop: Failed. Reason: reason. |
RADIUS accounting stop failed for the reason reason. |
|
RADIUS authentication: Succeeded. |
RADIUS authentication succeeded. |
|
RADIUS accounting start: Succeeded. |
RADIUS accounting start succeeded. |
|
RADIUS accounting update: Succeeded. |
RADIUS accounting update succeeded. |
|
RADIUS accounting stop: Succeeded. |
RADIUS accounting stop succeeded. |
|
RADIUS authentication: Failed. Reason: reason. |
RADIUS authentication failed for a reason. Possible reasons include: · Server rejected. |
|
RADIUS authorization: Failed. Reason: reason. |
RADIUS authorization failed for a reason. Possible reasons are: · Data error. |
|
TACACS authentication: Request initiated. |
TACACS authentication: Request packet was initiated. |
|
TACACS continue authentication: Request initiated. |
TACACS continue authentication: Request packet was initiated. |
|
TACACS accounting start: Request initiated. |
TACACS accounting start: Request packet was initiated. |
|
TACACS accounting update: Request initiated. |
TACACS accounting update: Request packet was initiated. |
|
TACACS accounting stop: Request initiated. |
TACACS accounting stop: Request packet was initiated. |
|
TACACS authentication: Failed. Reason: reason. |
TACACS authentication failed for the reason reason. |
|
TACACS continue authentication: Failed. Reason: reason. |
TACACS continue authentication failed for the reason reason. |
|
TACACS authorization: Failed. Reason: reason. |
TACACS authorization failed for the reason reason. |
|
TACACS accounting start: Failed. Reason: reason. |
TACACS accounting start failed for the reason reason. |
|
TACACS accounting update: Failed. Reason: reason. |
TACACS accounting update failed for the reason reason. |
|
TACACS accounting stop: Failed. Reason: reason. |
TACACS accounting stop failed for the reason reason. |
|
TACACS authentication: Succeeded. |
TACACS authentication succeeded. |
|
TACACS continue authentication: Succeeded. |
TACACS continue authentication succeeded. |
|
TACACS accounting start: Succeeded. |
TACACS accounting start succeeded. |
|
TACACS accounting update: Succeeded. |
TACACS accounting update succeeded. |
|
TACACS accounting stop: Succeeded. |
TACACS accounting stop succeeded. |
8. DHCP
Table 31 Detailed information of traced objects (DHCP)
|
Field |
Description |
|
DHCPACC received a message type, UserID userid, DHCPACCIndex index, state state |
The DHCP access module received a DHCP client message of the type type from UCM. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of type include: · UCM_UIA_DHCP_MSG_CONN_REQ_ACK—A connection is successfully established. · UCM_UIA_DHCP_MSG_CONN_REQ_REJ—Connection establishment was rejected. · UCM_UIA_DHCP_MSG_CONNUP_REQ_ACK—The DHCP client successfully came online. · UCM_UIA_DHCP_MSG_CONNUP_REQ_REJ—The online request of the DHCP client was rejected. · UCM_UIA_DHCP_MSG_DISCONN_INF—The user successfully went offline. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—The DHCP access module is waiting for the reply to the connection request message from UCM. · DHCPACC_WAIT_UCM_UP_ACK—The DHCP access module is waiting for the reply to the online request from UCM. · DHCPACC_WAIT_UCM_DOWN_ACK—The DHCP access module is waiting for the replay to the offline request from UCM. |
|
DHCPACC sent a message type, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module sent a DHCP client message of the type type to UCM. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of type include: · UCM_UIA_DHCP_MSG_CONNUP_REQ—The DHCP client comes online. · UCM_UIA_DHCP_MSG_CONNDOWN_REQ—The DHCP client went offline. Possible values of state include: · DHCPACC_WAIT_SERVER_ACK—Waiting for the DHCP-ACK packet from the DHCP server. · DHCPACC_WORKING—The DHCP client successfully comes online. |
|
DHCPACC would change to state after-state, UserID userid, DHCPACCIndex index, current state before-state. |
The state of the DHCP access module will switch to the after-state. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the before-state state currently. Possible values of after-state and before-state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent a DHCP-DISCOVER packet to AM. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module forwarded the DHCP-DISCOVER packet to the AM module. In the DHCP-DISCOVER packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC received a DHCP-OFFER packet from AM. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module received a DHCP-OFFER packet from the AM module. In the DHCP-OFFER packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC received a DHCP-NAK packet from AM. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module received a DHCP-NAK packet from the AM module. In the DHCP-NAK packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent a DHCP-OFFER packet to client. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state |
The DHCP access module forwarded the DHCP-OFFER packet to the DHCP client. In the DHCP-OFFER packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent a DHCP-NAK packet to client. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state |
The DHCP access module forwarded the DHCP-NAK packet to the DHCP client. In the DHCP-NAK packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC received a DHCP-REQUEST packet from client. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state |
The DHCP access module received a DHCP-REQUEST packet from the DHCP client. In the DHCP-REQUEST packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent a DHCP-REQUEST packet to AM. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state |
The DHCP access module forwarded the DHCP-REQUEST packet to the AM module. In the DHCP-REQUEST packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC receive a DHCP-ACK packet from AM. Giaddr giaddr, Yiaddr yiaddr, DHCPACCIndex index, state state. |
The DHCP access module received a DHCP-ACK packet from the AM module. In the DHCP-ACK packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent a DHCP-ACK packet to client. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state |
The DHCP access module forwarded the DHCP-ACK packet to the AM module. In the DHCP-ACK packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC received a DHCP-REQUEST packet from client. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module received a DHCP-REQUEST packet from the DHCP client. In the DHCP-REQUEST packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent a DHCP-REQUEST packet to AM. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module forwarded the DHCP-REQUEST packet to the AM module. In the DHCP-REQUEST packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC received a DHCP-ACK packet from AM. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module received a DHCP-ACK packet from the AM module. In the DHCP-ACK packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent a DHCP-ACK packet to CLIENT. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module forwarded a DHCP-ACK packet to the DHCP client. In the DHCP-ACK packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the DHCP client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully comes online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC received Release packet from client Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module received a Release packet from a DHCP client. In the DHCP-REQUEST packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, and the local index of the DHCP client is index. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the reply to the DHCP online packet from UCM. · DHCPACC_WORKING—The DHCP client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent Release packet to AM Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module forwarded a Release packet to the AM module. In the Release packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the current state of the DHCP client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the reply to the DHCP online packet from UCM. · DHCPACC_WORKING—The DHCP client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC received Release packet from AM. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module received a Release packet from the AM module. In the Release packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the current state of the DHCP client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC received Decline packet from client. Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module received a Decline packet from a DHCP client. The user ID is userid. In the DHCP-REQUEST packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The local index of the DHCP client is index. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent Decline packet to AM Giaddr giaddr, Yiaddr yiaddr, UserID userid, DHCPACCIndex index, state state. |
The DHCP access module forwarded a Decline packet to the AM module. In the Decline packet, the Giaddr field is giaddr, and the Yiaddr field is yiaddr. The user ID is userid, the local index of the DHCP client is index, and the current state of the DHCP client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the DHCP-OFFER packet from the AM module. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCP client to send a DHCP-REQUEST packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCP client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the DHCP client offline request ACK message from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the DHCP-RENEW packet from the AM module. |
|
DHCPACC sent a Solicit packet to AM. IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module forwarded the Solicit packet to the AM module. In the Solicit packet, the IA_NA field is IAAddr, and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the DHCPv6 client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the Reply packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the reply to the DHCPv6 online packet from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC received an Advertise packet from AM. IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module received an Advertise packet from the AM module. In the Advertise packet, the IA_NA field is IAAddr. The local index of the DHCPv6 client is index, and the DHCPv6 client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the Reply packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the reply to the DHCPv6 online packet from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC sent an Advertise packet to client. IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module forwarded an Advertise packet to the DHCPv6 client. In the Advertise packet, the IA_NA field is IAAddr, and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the DHCPv6 client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the Reply packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the reply to the DHCPv6 online packet from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC received a Reply packet from AM. IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module received a Reply packet from the AM module. In the Reply packet, the IA_NA field is IAAddr, and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the DHCPv6 client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the Reply packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the reply to the DHCPv6 online packet from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC sent a Reply packet to client. IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module forwarded a Reply packet to the DHCPv6 client. In the Reply packet, the IA_NA field is IAAddr, and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the DHCPv6 client is in the state state. Possible values of state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the Reply packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the reply to the DHCPv6 online packet from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC received a Release packet from client. IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module received a Release packet from a DHCP client. In the Release packet, the IA_NA field is IAAddr (iaid), and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the current state of the DHCPv6 client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCPv6 client online request ACK message from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC sent a Release packet to AM IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module forwarded a Release packet to the AM module. In the Release packet, the IA_NA field is IAAddr (iaid), and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the current state of the DHCPv6 client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCPv6 client online request ACK message from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC sent a Rebind packet to AM IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module forwarded a Rebind packet to the AM module. In the Rebind packet, the IA_NA field is IAAddr (iaid), and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the current state of the DHCPv6 client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC sent a Renew packet to AM IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module forwarded a Renew packet to the AM module. In the Renew packet, the IA_NA field is IAAddr (iaid), and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the current state of the DHCPv6 client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC received a Decline packet from client. IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module received a Decline packet from a DHCP client. In the Decline packet, the IA_NA field is IAAddr (iaid), and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the current state of the DHCPv6 client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
|
DHCPACC sent a Decline packet to AM IA_NA IAAddr(iaid iaid), IA_PD IAPD(iaid iaid) UserID userid, DHCPACCIndex index, state state. |
The DHCPv6 access module forwarded a Decline packet to the AM module. In the Decline packet, the IA_NA field is IAAddr (iaid), and the IA_PD field is IAPD(iaid). The user ID is userid, the local index of the DHCPv6 client is index, and the current state of the DHCPv6 client is state. Available values for state include: · DHCPACC_WAIT_UCM_REQ_ACK—Waiting for the connection request ACK message from UCM. · DHCPACC_WAIT_AM_OFFER—Waiting for the AM module to reply to the Advertise packet. · DHCPACC_WAIT_CLIENT_REQ—Waiting for the DHCPv6 client to send a Request packet. · DHCPACC_WAIT_AM_ACK—Waiting for the DHCP-ACK packet from the AM module. · DHCPACC_WAIT_UCM_UP_ACK—Waiting for the DHCP client online request ACK message from UCM. · DHCPACC_WORKING—The DHCPv6 client successfully came online. · DHCPACC_WAIT_AM_DOWN_ACK—Waiting for the reply to the DHCPv6 offline packet from the AM module. · DHCPACC_WAIT_UCM_DOWN_ACK—Waiting for the reply to DHCPv6 client offline request from UCM. · DHCPACC_RENEW_WAIT_SERACK—Waiting for the reply to the Renew packet from the AM module. |
9. ARP
Table 32 Detailed information of traced objects (ARP)
|
Field |
Description |
|
Add user |
UCM notified ARP to add a user. |
|
Modify user by UID uid |
ARP modified the session parameters of the ARP user with UID uid. |
|
Modify user |
ARP modified the session parameters of ARP users. |
|
Delete user |
UCM notified ARP to delete a user. |
|
Receive a connection ACK message from UCM |
ARP received a connection ACK message from UCM. |
|
Receive a connection reject message from UCM |
ARP receive a connection reject message from UCM. |
|
Work slot has been changed to the local slot, start ARP user detection through |
The slot that initiated ARP user detection has been switched to the local slot, and the local slot started ARP user detection. |
|
Work slot has been changed to slot slot-number, stop ARP user detection |
The slot that initiated ARP user detection has been switched to the slot slot-number, and the local slot stopped ARP user detection. |
|
Receive an ARP type packet: DstIP: dst-ip, DstMAC: dst-mac, SrcIP: src-ip, SrcMAC: src-mac |
An ARP packet was received, with the packet type as type, destination IP address as dst-ip, destination MAC address as dst-mac, sender IP address as src-ip, and sender MAC address as src-mac. |
|
Send an ARP reply to user |
ARP sent an ARP reply to a user. |
|
[DetectTimer] Create ARP user detection timer |
ARP created the ARP user detection timer. |
|
[DetectTimer] ARP user detection timer timed out |
The ARP user detection timer timed out. |
|
[DetectTimer] ARP request successfully sent |
During the ARP user detection process, the ARP request was successfully sent. |
|
[DetectTimer] User detection attempts reached. Send cut message to UCM |
The maximum user detection attempts were reached. ARP sent a cut message to UCM. |
|
[DetectTimer] Set ARP user detection flag |
ARP set the ARP user detection flag. |
|
[DetectTimer] The detection configuration has been changed. Ifindex: ifindex, Retries: retries, Interval: interval |
The ARP user detection configuration has been changed. The interface initiating ARP user detection was changed to interface with index ifindex, the maximum user detection attempts were changed to retries, and the detection interval was changed to interval. |
10. ND
Table 33 Detailed information of traced objects (ND)
|
Field |
Description |
|
Add user with IPv6 prefix prefix |
UCM notified ND to add a user. UCM allocated IPv6 prefix prefix to the ND user. |
|
Modify user by UID uid |
ND modified the session parameters of the ARP user with UID uid. |
|
Modify user |
ND modified the session parameters of ND users. |
|
Delete user |
UCM notified ND to delete users. |
|
Receive a connection ACK message from UCM |
ND received a connection ACK message from UCM. |
|
Receive a connection reject message from UCM |
ND received a connection reject message from UCM. |
|
Forbid to renew link-local address |
ND forbade users from renewing link-local addresses. |
|
Work slot has been changed to the local slot, start ND user detection |
The slot that initiated ND user detection has been switched to the local slot, and the local slot started ND user detection. |
|
Work slot has been changed to slot slot-number, stop ND user detection |
The slot that initiated ND user detection has been switched to the slot slot-number, and the local slot stopped ND user detection. |
|
Send an RA message. User MAC: mac_address, IPv6 prefix: prefix |
ND sent an RA message with the user MAC as mac_address and IPv6 prefix as prefix. |
|
[DetectTimer] Create ND user detection timer |
ND created the ND user detection timer. |
|
[DetectTimer] ND user detection timer timed out |
The ND user detection timer timed out. |
|
[DetectTimer] NS message successfully sent |
During the ND user detection process, the NS message was successfully sent. |
|
[DetectTimer] User detection attempts reached. Send cut message to UCM |
The maximum user detection attempts were reached. ND sent a cut message to UCM. |
|
[DetectTimer] Set ND user detection flag |
ND set the ND user detection flag. |
|
[DetectTimer] The detection configuration has been changed. Ifindex: ifindex, Retries: retries, Interval: interval |
The ND user detection configuration has been changed. The interface initiating ND user detection was changed to interface with index ifindex, the maximum user detection attempts were changed to retries, and the detection interval was changed to interval. |
|
[DetectTimer] Invalid user IPv6 address. Detection failed |
The user IPv6 address was invalid. As a result, ND user detection failed. |
11. IGMP
Table 34 Detailed information of traced objects (IGMP)
|
Field |
Description |
|
Multicast user comes online. |
ICMP received multicast user coming online messages from UCM. |
|
Multicast user goes offline. |
ICMP received multicast user going offline messages from UCM. |
|
Multicast authentication information change. |
Multicast authentication information changed. |
12. MLD
Table 35 Detailed information of traced objects (MLD)
|
Field |
Description |
|
Multicast user comes online. |
MLD received multicast user coming online messages from UCM. |
|
Multicast user goes offline. |
MLD received multicast user going offline messages from UCM. |
|
Multicast authentication information change. |
Multicast authentication information changed. |
uRPF
This section contains uRPF messages.
URPF_CONFIG
|
Message text |
Pattern 1: Failed to enable uRPF. uRPF is not supported. Pattern 2: Failed to enable uRPF on [STRING]. uRPF is not supported on [STRING]. Pattern 3: Failed to enable uRPF on [STRING] slot [INT32]. uRPF is not supported on [STRING] slot [INT32]. Pattern 4: Failed to enable uRPF on [STRING] slot [INT32] cpu [INT32]. uRPF is not supported on [STRING] slot [INT32] cpu [INT32]. Pattern 5: Failed to enable uRPF on [STRING] chassis [INT32] slot [INT32]. uRPF is not supported on [STRING] chassis [INT32] slot [INT32]. Pattern 6: Failed to enable uRPF on [STRING] chassis [INT32] slot [INT32] cpu [INT32]. uRPF is not supported on [STRING] chassis [INT32] slot [INT32] cpu [INT32] |
|
Variable fields |
Pattern 2: $1: Interface. Pattern 3: $1: Interface or security zone. $2: Slot number. Pattern 4: $1: Interface or security zone. $2: Slot number. $3: CPU number Pattern 5: $1: Interface or security zone. $2: Chassis number. $3: Slot number. Pattern 6: $1: Interface or security zone. $2: Chassis number. $3: Slot number. $4: CPU number |
|
Severity level |
4 (Warning) |
|
Example |
URPF/4/URPF_CONFIG: -MDC=1-Chassis=2-Slot=2; Failed to enable uRPF on Vlan-interface2 chassis 2 slot 2. |
|
Impact |
The uRPF feature is not available. |
|
Cause |
Pattern 1: Failed to enable IPv4 uRPF globally. The device does not support enabling IPv4 uRPF globally. Pattern 2: Failed to enable IPv4 uRPF on the specified interface or security zone. The device does not support enabling IPv4 uRPF on specified interfaces or security zones. Pattern 3: Failed to enable IPv4 uRPF on the specified slot or security zone. The device does not support enabling IPv4 uRPF on specified slots or security zones. Pattern 4: Failed to enable IPv4 uRPF on the specified interface or security zone in the specified slot and CPU. The device does not support enabling IPv4 uRPF on specified interface or security zone in the specified slot and CPU. Pattern 5: Failed to enable IPv4 uRPF on the specified interface or security zone in the specified chassis and slot. The device does not support enabling IPv4 uRPF on specified interface or security zone in the specified chassis and slot. Pattern 4: Failed to enable IPv4 uRPF on the specified interface or security zone in the specified chassis, slot, and CPU. The device does not support enabling IPv4 uRPF on specified interface or security zone in the specified chassis, slot, and CPU. |
|
Recommended action |
Check if the device supports the uRPF feature. |
URPF6_CONFIG
|
Message text |
Pattern 1: Failed to enable IPv6 uRPF. IPv6 uRPF is not supported. Pattern 2: Failed to enable IPv6 uRPF on [STRING]. IPv6 uRPF is not supported on [STRING]. Pattern 3: Failed to enable IPv6 uRPF on [STRING] slot [INT32]. IPv6 uRPF is not supported on [STRING] slot [INT32]. Pattern 4: Failed to enable IPv6 uRPF on [STRING] slot [INT32] cpu [INT32]. IPv6 uRPF is not supported on [STRING] slot [INT32] cpu [INT32]. Pattern 5: Failed to enable IPv6 uRPF on [STRING] chassis [INT32] slot [INT32]. IPv6 uRPF is not supported on [STRING] chassis [INT32] slot [INT32]. Pattern 6: Failed to enable IPv6 uRPF on [STRING] chassis [INT32] slot [INT32] cpu [INT32]. IPv6 uRPF is not supported on [STRING] chassis [INT32] slot [INT32] cpu [INT32] |
|
Variable fields |
Pattern 2: $1: Interface or security zone. Pattern 3: $1: Interface or security zone. $2: Slot number. Pattern 4: $1: Interface or security zone. $2: Slot number. $3: CPU number Pattern 5: $1: Interface or security zone. $2: Chassis number. $3: Slot number. Pattern 6: $1: Interface or security zone. $2: Chassis number. $3: Slot number. $4: CPU number |
|
Severity level |
4 (Warning) |
|
Example |
URPF/4/URPF6_CONFIG: -MDC=1-Chassis=2-Slot=2; Failed to enable IPv6 uRPF on Vlan-interface2 chassis 2 slot 2. |
|
Impact |
The IPv6 uRPF feature is not available. |
|
Cause |
Pattern 1: Failed to enable IPv6 uRPF globally. The device does not support enabling IPv6 uRPF globally. Pattern 2: Failed to enable IPv6 uRPF on the specified interface or security zone. The device does not support enabling IPv6 uRPF on specified interfaces or security zones. Pattern 3: Failed to enable IPv6 uRPF on the specified interface or security zone in the specified slot. The device does not support enabling IPv6 uRPF on specified interface or security zone in the specified slot. Pattern 4: Failed to enable IPv6 uRPF on the specified interface or security zone in the specified slot and CPU. The device does not support enabling IPv6 uRPF on specified interface or security zone in the specified slot and CPU. Pattern 5: Failed to enable IPv6 uRPF on the specified interface or security zone in the specified chassis and slot. The device does not support enabling IPv6 uRPF on specified interface or security zone in the specified chassis and slot. Pattern 4: Failed to enable IPv6 uRPF on the specified interface or security zone in the specified chassis, slot, and CPU. The device does not support enabling IPv6 uRPF on specified interface or security zone in the specified chassis, slot, and CPU. |
|
Recommended action |
Check if the device supports the IPv6 uRPF feature. |
VLAN messages
This section contains VLAN messages.
VLAN_FAILED
|
Message text |
Failed to add interface [STRING] to the default VLAN. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
VLAN/4/VLAN_FAILED: Failed to add interface GigabitEthernet1/0/1 to the default VLAN. |
|
Impact |
The port specified in this log message cannot receive packets carrying the default VLAN tag. |
|
Cause |
An interface was created when hardware resources were insufficient. |
|
Recommended action |
Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
VLAN_VLANMAPPING_FAILED
|
Message text |
The configuration failed because of resource insufficiency or conflicts on [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
VLAN/4/VLAN_VLANMAPPING_FAILED: The configuration failed because of resource insufficiency or conflicts on GigabitEthernet1/0/1.. |
|
Impact |
The VLAN mapping feature on this port cannot run properly. |
|
Cause |
Hardware resources are insufficient or the port joins or leaves a Layer 2 aggregation group. |
|
Recommended action |
1. Reconfigure VLAN mapping on the port. If the issue persists, proceed to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
VLAN_VLANTRANSPARENT_FAILED
|
Message text |
The configuration failed because of resource insufficiency or conflicts on [STRING]. |
|
Variable fields |
$1: Interface name. |
|
Severity level |
4 (Warning) |
|
Example |
VLAN/4/VLAN_VLANTRANSPARENT_FAILED: The configuration failed because of resource insufficiency or conflicts on GigabitEthernet1/0/1. |
|
Impact |
The VLAN transparent transmission feature on this port cannot run properly. |
|
Cause |
Hardware resources are insufficient or the port joins or leaves a Layer 2 aggregation group. |
|
Recommended action |
1. Reconfigure VLAN transparent transmission on the port. If the issue persists, proceed to step 2. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
VRRP4
This section contains IPv4 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: Network protocol type, which is IPv4. $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 IP address of the interface configured with the VRRP group is deleted. ¡ The status of the tracked object changed—The status of the associated track entry changed. ¡ VRRP packet received—A VRRP advertisement was received. ¡ Current device has changed to IP address owner—The current device has become the IP address owner. ¡ Master-down-timer expired—The master down timer (3 × VRRP advertisement interval + Skew_Time) expired. ¡ Zero priority packet received—A VRRP packet containing priority 0 was received. ¡ Preempt—Preemption occurred. ¡ Master group drove—The state of the master group changed. |
|
Severity level |
6 (Informational) |
|
Example |
VRRP4/6/VRRP_STATUS_CHANGE: The status of IPv4 virtual router 10 (configured on Ethernet0/0) changed from Backup to Master: Master-down-timer expired. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The VRRP group status changed because of the following reasons: 1. An interface event was received. 2. The virtual IP address has been deleted. 3. The status of the associated track entry changed. 4. A VRRP advertisement was received. 5. The current device has become the IP address owner. 6. The master down timer (3 × VRRP advertisement interval + Skew_Time) expired. 7. A VRRP packet containing priority 0 was received. 8. Preemption occurred. 9. The state of the master group changed. |
|
Recommended action |
Take an action according to the reason for the change in VRRP status carried in the log: · For reason 1, identify whether the interface where the VRRP group is located has failed · Execute the display interface command on both local and remote ends to check the status of the interface connected to the VRRP group. If the interface state is down, locate and handle the interface fault according to the output information. · For reason 2, identify whether the interface IP address is deleted. Execute the display interface brief command on the local end to view the device interface IP address. If the interface IP address is deleted, execute the ip address or ipv6 address command in interface view to configure an IP address again. · For reason 3, first execute the display vrrp command to obtain the associated track entry ID, and then use the display track command to locate and resolve the track entry fault. · For reason 4, no action is required · For reason 5, the recommended action is as follows: · Identify whether it is necessary to configure the local device as the IP address owner of the VRRP group: Execute the display vrrp command without parameters on the local device to view the virtual IP address of the VRRP group. Execute the display interface brief command on the local device to view the IP address of the device interface, and locate the interface with the same IP address as the VRRP group. A device with an interface IP address the same as the virtual IP address is called the IP address owner. An IP address owner in the VRRP group is the master as long as it is working correctly. ¡ If the device needs to be configured as the IP address owner, no action is required ¡ If the device does not need to be configured as the IP address owner, use the vrrp vrid command in interface view to edit the virtual IP address of the VRRP group · For reason 6, the recommended action is as follows: ¡ Identify whether the remote device is faulty. Execute the display vrrp command on the remote device. If the State field value is Initialize, the device is faulty. Locate the cause and recover the remote device. ¡ Identify whether the interface connected to the VRRP group is faulty. Execute the display interface command on both the local and remote ends to check the state of the interface connected to the VRRP group. If the interface state is down, locate and resolve the interface fault according to the output information. ¡ Identify whether a VRRP configuration error exists. Execute the display current-configuration | inculde vrrp command on both the local and remote ends to filter VRRP configuration. ¡ For VRRPv4, the version number must be consistent. If it is not consistent, use the vrrp version command in interface view to edit the version. IPv6 VRRP supports only VRRPv3 version that cannot be edited. ¡ For VRRPv4, the authentication mode must be consistent. If an authentication key is configured, the authentication key must also be consistent. If it is not consistent, use the vrrp vrid authentication-mode command in interface view to edit the setting. VRRPv6 does not support authentication · For reason 7, the recommended action is as follows: ¡ Execute the display vrrp verbose command on both the local and remote ends to view the configured VRRP priority (Config pri field): ¡ If the configuration is correct, no action is required. ¡ If the configuration is incorrect, use the vrrp vrid priority command in interface view to edit the configuration. ¡ Execute the display vrrp verbose command on both the local and remote ends to view the configured VRRP priority (Config pri field) and the actual effective VRRP priority (Running pri field). If the two values are different, further check the associated track entry ID, and use the display track command to locate and resolve the track entry fault · For reason 8, if the preemption is manually triggered by the administrator, no action is required. For automatic preemption, the monitored object is faulty, and further confirmation of the cause of automatic preemption is needed. · For reason 9, execute the display vrrp verbose command on the local device, locate the associated management VRRP group name according to the value of the Follow Name field, and then take further actions according to the value of the reason in the management VRRP group trap. · If the issue persists, collect the configuration data, log messages, and alarm information, and then contact Technical Support for help. |
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: Network protocol type, which is IPv4. $2: VRRP group number. $3: Name of the interface where the VRRP group is configured. $4: VF ID. $5: Original status of VF. Options include: · Active—The VF is forwarding data. · Listening—The VF is in backup state. · Initialize—The VF is in initialization state. $6: Current status of VF. Options include: · Active—The VF is forwarding data. · Listening—The VF is in backup state. · Initialize—The VF is in initialization state. $7: Reason for the status change. Options include: · Weight changed · Adding virtual MAC address failed · Conceded—Received a message with VF priority 0, and actively removed the forwarding permissions · Learnt from Advertisement · Reply received—Received a reply message. · Release received—Received release message. · Active timer expired · Time-out timer expired · Self-allocated—The master allocated a virtual MAC address to itself. · VRRP down—The VRRP group went down. · Take over—Took over as the AVF. · The status of the tracked object changed |
|
Severity level |
6 (Informational) |
|
Example |
VRRP4/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. |
|
Impact |
No negative impact on the system for normal switchover. If the VF status is abnormal after the switchover, services might be interrupted. |
|
Cause |
Possible reasons include: 1. Weight change. 2. Failed to add virtual MAC address. 3. Received a message with VF priority 0, and actively removed the forwarding permissions 4. Learned from an advertisement message 5. Received a reply message 6. Received a release message 7. Active timer timed out 8. Timeout timer timed out 9. The master allocated a virtual MAC address to itself. 10. The VRRP group went down 11. Took over as the AVF. 12. The status of the tracked object changed |
|
Recommended action |
Take an action based on the VRRP status change reason in the log message: · For reason 1, check the configured VRRP priority (Config pri field) and the actual effective VRRP priority (Running pri field). If the two values are different, further check the associated track entry number. Use the display track command to locate and resolve the track entry fault. · For reason 2, locate the root cause of the MAC operation failure and resolve it · For reason 3, identify whether a VRRP group with a priority higher than the local priority exists in the network: ¡ If the configuration is correct, no action is needed ¡ If the configuration is incorrect, edit the configuration by using the vrrp vrid priority command in interface view · For reason 4, no action is required. · For reason 5, no action is required. · For reason 6, no action is required. · For reason 7, no action is required. · For reason 8, no action is required. · For reason 9, no action is required. · For reason 10, identify whether the interface configured with the VRRP group has failed: Use the display interface command to check the state of the interface connected to the VRRP group. If the interface state is down, locate and resolve the interface fault according to the output information. · For reason 11, the original highest-priority AVF's weight has failed. Check the reason for the change in the original AVF priority. · For reason 12, check the track entry state. You can use the display track command to locate and resolve the track entry fault. |
VRRP_VMAC_INEFFECTIVE
|
Message text |
The [STRING] virtual router [UINT32] (configured on [STRING]) failed to add virtual MAC: [STRING]. |
|
Variable fields |
$1: Network protocol type, which is IPv4. $2: VRRP group number. $3: Name of the interface where the VRRP group is configured. $4: The reason for the error is Insufficient hardware resources, indicating a lack of hardware resources |
|
Severity level |
3 (Error) |
|
Example |
VRRP4/3/VRRP_VMAC_INEFFECTIVE: The IPv4 virtual router 10 (configured on Ethernet0/0) failed to add virtual MAC: Insufficient hardware resources. |
|
Impact |
The VRRP group of this device cannot work correctly. |
|
Cause |
Failed to add the virtual MAC address. |
|
Recommended action |
1. In probe view, execute the display system internal vrrp kernel virtual-route command to view the virtual router information of the VRRP kernel and collect output information. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
VRRP6
This section contains IPv6 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: Network protocol type, which is IPv6. $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 IP address of the interface configured with the VRRP group is deleted. ¡ The status of the tracked object changed—The status of the associated track entry changed. ¡ VRRP packet received—A VRRP advertisement was received. ¡ Current device has changed to IP address owner—The current device has become the IP address owner. ¡ Master-down-timer expired—The master down timer (3 × VRRP advertisement interval + Skew_Time) expired. ¡ Zero priority packet received—A VRRP packet containing priority 0 was received. ¡ Preempt—Preemption occurred. ¡ Master group drove—The state of the master group changed. |
|
Severity level |
6 (Informational) |
|
Example |
VRRP6/6/VRRP_STATUS_CHANGE: The status of IPv6 virtual router 10 (configured on Ethernet0/0) changed from Backup to Master: Master-down-timer expired. |
|
Impact |
No negative impacts on the system. |
|
Cause |
The VRRP group status changed because of the following reasons: 1. An interface event was received. 2. The virtual IP address has been deleted. 3. The status of the associated track entry changed. 4. A VRRP advertisement was received. 5. The current device has become the IP address owner. 6. The master down timer (3 × VRRP advertisement interval + Skew_Time) expired. 7. A VRRP packet containing priority 0 was received. 8. Preemption occurred. 9. The state of the master group changed. |
|
Recommended action |
Take an action according to the reason for the change in VRRP status carried in the log: · For reason 1, identify whether the interface where the VRRP group is located has failed · Execute the display interface command on both local and remote ends to check the status of the interface connected to the VRRP group. If the interface state is down, locate and handle the interface fault according to the output information. · For reason 2, identify whether the interface IP address is deleted. Execute the display interface brief command on the local end to view the device interface IP address. If the interface IP address is deleted, execute the ip address or ipv6 address command in interface view to configure an IP address again. · For reason 3, first execute the display vrrp command to obtain the associated track entry ID, and then use the display track command to locate and resolve the track entry fault. · For reason 4, no action is required · For reason 5, the recommended action is as follows: · Identify whether it is necessary to configure the local device as the IP address owner of the VRRP group: Execute the display vrrp command without parameters on the local device to view the virtual IP address of the VRRP group. Execute the display interface brief command on the local device to view the IP address of the device interface, and locate the interface with the same IP address as the VRRP group. A device with an interface IP address the same as the virtual IP address is called the IP address owner. An IP address owner in the VRRP group is the master as long as it is working correctly. ¡ If the device needs to be configured as the IP address owner, no action is required ¡ If the device does not need to be configured as the IP address owner, use the vrrp vrid command in interface view to edit the virtual IP address of the VRRP group · For reason 6, the recommended action is as follows: ¡ Identify whether the remote device is faulty. Execute the display vrrp command on the remote device. If the State field value is Initialize, the device is faulty. Locate the cause and recover the remote device. ¡ Identify whether the interface connected to the VRRP group is faulty. Execute the display interface command on both the local and remote ends to check the state of the interface connected to the VRRP group. If the interface state is down, locate and resolve the interface fault according to the output information. ¡ Identify whether a VRRP configuration error exists. Execute the display current-configuration | inculde vrrp command on both the local and remote ends to filter VRRP configuration. ¡ For VRRPv4, the version number must be consistent. If it is not consistent, use the vrrp version command in interface view to edit the version. IPv6 VRRP supports only VRRPv3 version that cannot be edited. ¡ For VRRPv4, the authentication mode must be consistent. If an authentication key is configured, the authentication key must also be consistent. If it is not consistent, use the vrrp vrid authentication-mode command in interface view to edit the setting. VRRPv6 does not support authentication. · For reason 7, the recommended action is as follows: ¡ Execute the display vrrp verbose command on both the local and remote ends to view the configured VRRP priority (Config pri field): ¡ If the configuration is correct, no action is required. ¡ If the configuration is incorrect, use the vrrp vrid priority command in interface view to edit the configuration. ¡ Execute the display vrrp verbose command on both the local and remote ends to view the configured VRRP priority (Config pri field) and the actual effective VRRP priority (Running pri field). If the two values are different, further check the associated track entry ID, and use the display track command to locate and resolve the track entry fault · For reason 8, if the preemption is manually triggered by the administrator, no action is required. For automatic preemption, the monitored object is faulty, and further confirmation of the cause of automatic preemption is needed. · For reason 9, execute the display vrrp verbose command on the local device, locate the associated management VRRP group name according to the value of the Follow Name field, and then take further actions according to the value of the reason in the management VRRP group trap. · If the issue persists, collect the configuration data, log messages, and alarm information, and then contact Technical Support for help. |
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: Network protocol type, which is IPv6. $2: VRRP group number. $3: Name of the interface where the VRRP group is configured. $4: VF ID. $5: Original status of VF. Options include: · Active—The VF is forwarding data. · Listening—The VF is in backup state. · Initialize—The VF is in initialization state. $6: Current status of VF. Options include: · Active—The VF is forwarding data. · Listening—The VF is in backup state. · Initialize—The VF is in initialization state. $7: Reason for the status change. Options include: · Weight changed · Adding virtual MAC address failed · Conceded—Received a message with VF priority 0, and actively removed the forwarding permissions · Learnt from Advertisement · Reply received—Received a reply message. · Release received—Received release message. · Active timer expired · Time-out timer expired · Self-allocated—The master allocated a virtual MAC address to itself. · VRRP down—The VRRP group went down. · Take over—Took over as the AVF. · The status of the tracked object changed |
|
Severity level |
6 (Informational) |
|
Example |
VRRP6/6/VRRP_VF_STATUS_CHANGE: The IPv6 virtual router 10 (configured on GigabitEthernet5/1) virtual forwarder 2 detected status change (from Active to Initialize): Weight changed. |
|
Impact |
No negative impact on the system for normal switchover. If the VF status is abnormal after the switchover, services might be interrupted. |
|
Cause |
Possible reasons include: 1. Weight change. 2. Failed to add virtual MAC address. 3. Received a message with VF priority 0, and actively removed the forwarding permissions 4. Learned from an advertisement message 5. Received a reply message 6. Received a release message 7. Active timer timed out 8. Timeout timer timed out 9. The master allocated a virtual MAC address to itself. 10. The VRRP group went down 11. Took over as the AVF. 12. The status of the tracked object changed |
|
Recommended action |
Take an action based on the VRRP status change reason in the log message: · For reason 1, check the configured VRRP priority (Config pri field) and the actual effective VRRP priority (Running pri field). If the two values are different, further check the associated track entry number. Use the display track command to locate and resolve the track entry fault. · For reason 2, locate the root cause of the MAC operation failure and resolve it · For reason 3, identify whether a VRRP group with a priority higher than the local priority exists in the network: ¡ If the configuration is correct, no action is needed ¡ If the configuration is incorrect, edit the configuration by using the vrrp vrid priority command in interface view · For reason 4, no action is required. · For reason 5, no action is required. · For reason 6, no action is required. · For reason 7, no action is required. · For reason 8, no action is required. · For reason 9, no action is required. · For reason 10, identify whether the interface configured with the VRRP group has failed: Use the display interface command to check the state of the interface connected to the VRRP group. If the interface state is down, locate and resolve the interface fault according to the output information. · For reason 11, the original highest-priority AVF's weight has failed. Check the reason for the change in the original AVF priority. · For reason 12, check the track entry state. You can use the display track command to locate and resolve the track entry fault. |
VRRP_VMAC_INEFFECTIVE
|
Message text |
The [STRING] virtual router [UINT32] (configured on [STRING]) failed to add virtual MAC: [STRING]. |
|
Variable fields |
$1: Network protocol type, which is IPv6. $2: VRRP group number. $3: Name of the interface where the VRRP group is configured. $4: The reason for the error is Insufficient hardware resources, indicating a lack of hardware resources |
|
Severity level |
3 (Error) |
|
Example |
VRRP6/3/VRRP_VMAC_INEFFECTIVE: The IPv6 virtual router 10 (configured on Ethernet0/0) failed to add virtual MAC: Insufficient hardware resources. |
|
Impact |
The VRRP group of this device cannot work correctly. |
|
Cause |
Failed to add the virtual MAC address. |
|
Recommended action |
1. In probe view, execute the display system internal vrrp [ ipv6 ] kernel virtual-route command to view the virtual router information of the VRRP kernel and collect output information. 2. If the issue persists, collect configuration data, log messages, and alarm information, and then contact Technical Support for help. |
VSRP messages
This section contains VSRP messages.
VSRP_BIND_FAILED
|
Message text |
Failed to bind the IP addresses and the port on VSRP peer [STRING]. |
|
Variable fields |
$1: VSRP peer name. |
|
Severity level |
6 (Informational) |
|
Example |
VSRP/6/VSRP_BIND_FAILED: Failed to bind the IP addresses and the port on VSRP peer aaa. |
|
Impact |
The control channel for the VSRP instance might fail to be established. When the VSRP-associated service module cannot determine the master and backup devices, VSRP might not determine the master and backup devices either, affecting correct operation of VSRP. |
|
Cause |
The system memory resources are insufficient. |
|
Recommended action |
1. Release the memory. For example, execute the logfile save command to manually save all content in the log file buffer to log files, releasing memory resources occupied by the log file buffer. 2. Execute the display memory command to view process memory usage: ¡ If the memory usage drops below the alarm threshold, the memory alarm is cleared, and no further action is required. ¡ If the memory usage does not drop below the alarm threshold, execute the display process command to view memory usage of user processes. If a specific process occupies too much memory, you can enable or disable the process-associated software feature to release the memory. 3. If the issue persists, collect alarm information and configuration data, and then contact Technical Support for help. |
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 (Error) |
|
Example |
VXLAN/3/VXLAN_LICENSE_UNAVAILABLE: The VXLAN feature is disabled, because no licenses are valid. |
|
Impact |
VXLAN-related features are unavailable. |
|
Cause |
VXLAN was disabled because no licenses were valid. |
|
Recommended action |
Install valid licenses for VXLAN. |
WAN messages
This section contains WAN messages.
ALARM_PATH
|
Message text |
[STRING] : Path [STRING] Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: Higher order path number. $3: Higher order path alarm name (for example, AIS/LOF/LOS/RDI/SD/SLM/TIM/UNEQ). $4: State of the higher order path alarm. Options include recover and report. $5: Time when the alarm was cleared or reported, in the format of Y-M-D H:M:S:MS. |
|
Severity level |
4 (Warning) |
|
Example |
WAN/4/ALARM_PATH: -MDC=1-Slot=5; Cpos5/1/1 : Path 1 Alarm AIS report! Start Time : 2014-04-04 11:40:53:533! |
|
Impact |
The higher order path of the CPOS interface has an alarm. Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
· When the state of the higher order path alarm is recover, this message displays the specific clearing time and alarm type of the higher order path alarm on the CPOS interface. · When the state of the higher order path alarm is report, this message displays the specific triggering time and alarm type of the higher order path alarm on the CPOS interface. Possible reasons for this log message include: ¡ The peer CPOS interface is shut down by using the shutdown command. ¡ The transceiver module or line fails. ¡ The framing format of the local interface is different from that of the peer interface. ¡ The multiplexing mode of the local interface is different from that of the peer interface. ¡ The higher order path overhead byte configuration is inconsistent on the two ends. |
|
Recommended action |
· When the state of the higher order path alarm is recover, no action is required. · When the state of the higher order path alarm is report, perform the following tasks: a. Use the display controller cpos command to identify whether the physical state of the interface is up. b. The state of UP indicates the physical state of the interface is normal. Proceed to the next step. c. The state of DOWN (Administratively) indicates the interface is shut down by using the shutdown command. In this case, bring up the interface by using the undo shutdown command. d. The state of DOWN indicates that the interface is administratively up but physically down, possibly because the line fails or the peer interface is shut down by using the shutdown command. In this case, resolve the corresponding issue. e. Use the display transceiver alarm command to identify whether the transceiver module fails. f. Verify that the optical fibers are normal. g. If the framing format of the interface is inconsistent, use the frame-format or e1 frame-format command to configure the framing format of the interface. h. If the multiplexing mode of the interface is inconsistent, use the multiplex mode command to configure the multiplexing mode of the interface. i. Enter interface view and use the display this command j. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ALARM_SDH_AU3E1
|
Message text |
[STRING] : AUG 1 VC3 [STRING] TUG-2 [STRING] TU12 [STRING] E1 Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: VC3 number. $3: TUG-2 number. $4: TUG-12 number. $5: Alarm name (for example, AIS/LOF/LOS/RDI/SD/SLM/TIM/UNEQ). $6: Alarm state. Options include recover and report. $7: Time when the alarm was cleared or reported, in the format of Y-M-D H:M:S:MS. |
|
Severity level |
4 (Warning) |
|
Example |
WAN/4/ALARM_SDH_AU3E1: -MDC=1-Slot=4; Cpos4/1/1 : AUG 1 VC3 1 TUG-2 1 TU12 1 E1 Alarm AIS report! Start Time : 2014-04-04 14:17:55:977! |
|
Impact |
The CPOS interface has an alarm. Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
· When the state of the alarm is recover, this message displays the specific clearing time and alarm type of the lower order E1 channel alarm when the framing format and AUG multiplexing mode of the CPOS interface are SDH and AU-3, respectively. · When the state of the alarm is report, this message displays the specific triggering time and alarm type of the lower order E1 channel alarm when the framing format and AUG multiplexing mode of the CPOS interface are SDH and AU-3, respectively. Possible reasons for this log message include: ¡ The E1 channel on the peer CPOS interface has been shut down. ¡ The transceiver module or line fails. ¡ The framing format of the local interface is different from that of the peer interface. ¡ The multiplexing mode of the local interface is different from that of the peer interface. ¡ The overhead byte configuration of the E1 channel is inconsistent on the two ends. |
|
Recommended action |
· When the state of the alarm is recover, no action is required. · When the state of the alarm is report, perform the following tasks: k. Use the display controller cpos e1 command to identify whether the physical state of the interface is up. l. The state of UP indicates the physical state of the interface is normal. Proceed to the next step. m. The state of DOWN (Administratively) indicates the interface is shut down by using the shutdown command. In this case, bring up the interface by using the undo shutdown command. n. The state of DOWN indicates that the interface is administratively up but physically down, possibly because the line fails or the peer interface is shut down by using the shutdown command. In this case, resolve the corresponding issue. o. Use the display transceiver alarm command to identify whether the transceiver module fails. p. Verify that the optical fibers are normal. q. If the framing format of the interface is inconsistent, use the frame-format or e1 frame-format command to configure the framing format of the interface. r. If the multiplexing mode of the interface is inconsistent, use the multiplex mode command to configure the multiplexing mode of the interface. s. Enter interface view and use the display this command t. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ALARM_SDH_AU4E1
|
Message text |
[STRING] : VC4 1 TUG-3 [STRING] TUG-2 [STRING] TU12 [STRING] E1 Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: TUG-3 number. $3: TUG-2 number. $4: TU-12 number. $5: Alarm name (for example, AIS/LOF/LOS/RDI/SD/SLM/TIM/UNEQ). $6: Alarm state. Options include recover and report. $7: Time when the alarm was cleared or reported, in the format of Y-M-D H:M:S:MS. |
|
Severity level |
4 (Warning) |
|
Example |
WAN/4/ALARM_SDH_AU3E1: -MDC=1-Slot=4; Cpos4/1/1 : VC4 1 TUG-3 1 TUG-2 1 TU12 1 E1 Alarm AIS report! Start Time : 2014-04-04 14:16:51:213! |
|
Impact |
The CPOS interface has an alarm. Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
· When the state of the alarm is recover, this message displays the specific clearing time and alarm type of the lower order E1 channel alarm when the framing format and AUG multiplexing mode of the CPOS interface are SDH and AU-4, respectively. · When the state of the alarm is report, this message displays the specific triggering time and alarm type of the lower order E1 channel alarm when the framing format and AUG multiplexing mode of the CPOS interface are SDH and AU-4, respectively. Possible reasons for this log message include: ¡ The E1 channel on the peer CPOS interface has been shut down. ¡ The transceiver module or line fails. ¡ The framing format of the local interface is different from that of the peer interface. ¡ The multiplexing mode of the local interface is different from that of the peer interface. ¡ The overhead byte configuration of the E1 channel is inconsistent on the two ends. |
|
Recommended action |
· When the state of the alarm is recover, no action is required. · When the state of the alarm is report, perform the following tasks: u. Use the display controller cpos e1 command to identify whether the physical state of the interface is up. v. The state of UP indicates the physical state of the interface is normal. Proceed to the next step. w. The state of DOWN (Administratively) indicates the interface is shut down by using the shutdown command. In this case, bring up the interface by using the undo shutdown command. x. The state of DOWN indicates that the interface is administratively up but physically down, possibly because the line fails or the peer interface is shut down by using the shutdown command. In this case, resolve the corresponding issue. y. Use the display transceiver alarm command to identify whether the transceiver module fails. z. Verify that the optical fibers are normal. aa. If the framing format of the interface is inconsistent, use the frame-format or e1 frame-format command to configure the framing format of the interface. bb. If the multiplexing mode of the interface is inconsistent, use the multiplex mode command to configure the multiplexing mode of the interface. cc.
Enter interface view and use the display this command dd. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ALARM_SECTION_LINE
|
Message text |
[STRING] : Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS or POS interface name. $2: Alarm name (for example, AIS/LOF/LOS/RDI/SD/SLM/TIM/UNEQ). $3: Alarm state. Options include report and recover. $4: Time when the alarm was reported or cleared, in the format of Y-M-D H:M:S:MS. |
|
Severity level |
4 (Warning) |
|
Example |
WAN/4/ALARM_SECTION_LINE: -MDC=1-Slot=4; Cpos4/1/1 : Alarm LOS report! Start Time : 2014-04-04 14:14:47:263! |
|
Impact |
The CPOS interface has an alarm. Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
· When the state of the alarm is recover, this message displays the specific clearing time and alarm type of the regenerator section or multiplex section alarm on the CPOS interface. · When the state of the alarm is report, this message displays the specific triggering time and alarm type of the regenerator section or multiplex section alarm on the CPOS interface. Possible reasons for this log message include: ¡ The peer CPOS interface has been shut down. ¡ The transceiver module or line fails. ¡ The overhead byte configuration for SONET/SDH frames is inconsistent on the CPOS interfaces on both ends. ¡ The line clock mode of the peer CPOS interface is the same as that of the local CPOS interface. |
|
Recommended action |
· When the state of the alarm is recover, no action is required. · When the state of the alarm is report, perform the following tasks: ee. Use the display controller cpos command to identify whether the physical state of the interface is up. ff. The state of UP indicates the physical state of the interface is normal. Proceed to the next step. gg. The state of DOWN (Administratively) indicates the interface is shut down by using the shutdown command. In this case, bring up the interface by using the undo shutdown command. hh. The state of DOWN indicates that the interface is administratively up but physically down, possibly because the line fails or the peer interface is shut down by using the shutdown command. In this case, resolve the corresponding issue. ii. Use the display transceiver alarm command to identify whether the transceiver module fails. jj. Verify that the optical fibers are normal. kk.
Enter interface view and use the display this command ll. Use the display this command to identify whether the clock mode is master on one end and slave on the other end. If not, modify the clock mode. mm. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ALARM_SONET_E1
|
Message text |
[STRING] : OC-3 1 STS [STRING] VTG [STRING] VT2 [STRING] E1 Alarm [STRING] [STRING]! Start Time : [STRING]! |
|
Variable fields |
$1: CPOS interface name. $2: STS number. $3: VTG number. $4: VT2 number. $5: Alarm name (for example, AIS/LOF/LOS/RDI/SD/SLM/TIM/UNEQ). $6: Alarm state. Options include recover and report. $7: Time when the alarm was cleared or reported, in the format of Y-M-D H:M:S:MS. |
|
Severity level |
4 (Warning) |
|
Example |
WAN/4/ALARM_SDH_AU3E1: -MDC=1-Slot=4; Cpos4/1/1 : OC-3 1 STS 1 VTG 1 VT2 1 E1 Alarm AIS recover! Start Time : 2014-04-04 14:23:04:125! |
|
Impact |
The CPOS interface has an alarm. Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
· When the state of the alarm is recover, this message displays the specific clearing time and alarm type of the lower order E1 channel alarm when the framing format of the CPOS interface is SONET. · When the state of the alarm is report, this message displays the specific triggering time and alarm type of the lower order E1 channel alarm when the framing format of the CPOS interface is SONET. Possible reasons for this log message include: ¡ The E1 channel on the peer CPOS interface has been shut down. ¡ The transceiver module or line fails. ¡ The framing format of the local interface is different from that of the peer interface. ¡ The multiplexing mode of the local interface is different from that of the peer interface. ¡ The overhead byte configuration of the E1 channel is inconsistent on the two ends. |
|
Recommended action |
· When the state of the alarm is recover, no action is required. · When the state of the alarm is report, perform the following tasks: nn. Use the display controller cpos e1 command to identify whether the physical state of the interface is up. oo. The state of UP indicates the physical state of the interface is normal. Proceed to the next step. pp. The state of DOWN (Administratively) indicates the interface is shut down by using the shutdown command. In this case, bring up the interface by using the undo shutdown command. qq. The state of DOWN indicates that the interface is administratively up but physically down, possibly because the line fails or the peer interface is shut down by using the shutdown command. In this case, resolve the corresponding issue. rr. Use the display transceiver alarm command to identify whether the transceiver module fails. ss. Verify that the optical fibers are normal. tt. If the framing format of the interface is inconsistent, use the frame-format or e1 frame-format command to configure the framing format of the interface. uu. If the multiplexing mode of the interface is inconsistent, use the multiplex mode command to configure the multiplexing mode of the interface. vv.
Enter interface view and use the display this command ww. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
ALARM_STATUS_CHG
|
Message text |
[STRING] : [STRING] of [STRING] has lasted link-delay time! |
|
Variable fields |
$1: WAN interface name. $2: Alarm state. Options include Reporting and Recovering. $3: Alarm type (for example, SD/SF/RDI). |
|
Severity level |
4 (Warning) |
|
Example |
WAN/4/ALARM_STATUS_CHG: -MDC=1-Slot=2; Pos2/4/1 Reporting of Line RDI has lasted link-delay time! |
|
Impact |
The WAN interface has generated an alarm. Comprehensively assess the impact on the system according to the actual situation. |
|
Cause |
· When the state of the alarm is recover, it means that the WAN interface has cleared the SD, SF, or RDI alarm specified by using the alarm-detect command within the physical state change suppression interval configured by using the link-delay command. · When the state of the alarm is report, it means that the WAN interface has received the SD, SF, or RDI alarm specified by using the alarm-detect command within the physical state change suppression interval configured by using the link-delay command. |
|
Recommended action |
· When the state of the alarm is recover, no action is required. · When the state of the alarm is report, perform the following tasks: xx. Check optical fiber connectivity by re-plugging or replacing the optical fibers. yy. Use the display interface command to identify whether the physical state of the interface is up. zz. The state of DOWN indicates that the interface is administratively up but physically down, possibly because the line fails or the peer interface is shut down by using the shutdown command. In this case, resolve the corresponding issue. aaa. Use the display transceiver alarm command to identify whether the transceiver module fails. bbb. Use the alarm-detect command to configure the action to take when an alarm occurs on an interface. When an alarm is detected, the device automatically sets the physical state of the interface to down. Check the following alarms: Remote defect indication (RDI) alarm, signal degrade (SD) alarm, and signal fail (SF) alarm. ccc. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
POS_CLK_CHK
|
Message text |
The clock mode configuration of [STRING] must be the same as [STRING]. Otherwise, the configuration does not take effect. |
|
Variable fields |
$1: Interface name. $2: Interface name. |
|
Severity level |
5 (Notification) |
|
Example |
WAN/5/POS_CLK_CHK: -MDC=1-Slot=4; The clock mode configuration of Pos2/4/1 must be the same as Pos2/4/2. Otherwise, the configuration does not take effect. |
|
Impact |
For the configuration to take effect, make sure the clock mode configuration is the same on the two interfaces. |
|
Cause |
The clock mode configurations of the two interfaces are different. |
|
Recommended action |
1. Set the same clock mode for the two interfaces. 2. Collect alarm information, log messages, and configuration data, and then contact Technical Support for help. |
