S2750&S5700&S6700 V200R003 (C00&C02&C10) Log Reference 07

S2750&S5700&S6700 Series Ethernet Switches
V200R003(C00&C02&C10)
Log Reference
Issue
07
Date
2014-07-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address:
Huawei Industrial Base

Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
http://enterprise.huawei.com
Issue 07 (2014-07-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.

Log Reference
About This Document
About This Document

Intended Audience
This document describes the parameters, meaning, possible causes, and solution of logs.
This document provides a complete set of logs, which helps intended readers check the running
status of the device, analyze the network status, and locate the problem cause, so as to provide
a reference for system diagnosis and maintenance.
This document is intended for:
l
Commissioning engineers
Network monitoring engineers
System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates an imminently hazardous situation
which, if not avoided, will result in death or
serious injury.
Indicates a potentially hazardous situation
which, if not avoided, could result in death or
serious injury.
which, if not avoided, may result in minor or
moderate injury.
which, if not avoided, could result in
equipment damage, data loss, performance
deterioration, or unanticipated results.
NOTICE is used to address practices not
related to personal injury.
Issue 07 (2014-07-30)

ii

Log Reference
About This Document
Symbol
Description
Calls attention to important information, best
practices and tips.
NOTE
NOTE is used to address information not

related to personal injury, equipment damage,
and environment deterioration.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention
Description
Boldface
The keywords of a command line are in boldface.
Italic
Command arguments are in italics.
[]
Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... }
Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ]
Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }*
Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
&<1-n>
The parameter before the & sign can be repeated 1 to n times.
A line starting with the # sign is comments.
Mappings between Product Software Versions and NMS

Versions
The mappings between product software versions and NMS versions are as follows.
Issue 07 (2014-07-30)
Product Software Version
eSight
V200R003C00
V200R003C01
V200R003C02
V200R003C10

iii

Log Reference
About This Document
Product Software Version
eSight
V200R003C10
V200R005C00
Change History
Changes between document issues are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Changes in Issue 07 (2014-07-30) V200R003(C00&C02&C10)

This version has the following updates:
The documentation is updated according to product feature updates.


Changes in Issue 04 (2013-11-06) V200R003(C00&C02)

Changes in Issue 03 (2013-09-30) V200R003(C00&C02)

The following information is added:
l
95.5 SRM/4/BATCGOVERCURPROTECT
95.6 SRM/4/BATCGOVERVOLPROTECT
95.7 SRM/2/BATDGTEMPHIGH
95.8 SRM/4/BATDGTEMPHIGHRESUME
95.10 SRM/2/BATINVALID
95.11 SRM/2/BATSUPPLYTIMESHORT
95.9 SRM/4/BATLIFEENDCLEAR
95.12 SRM/2/BATREMAINLOW
95.13 SRM/4/BATREMAINLOWRESUME
Issue 07 (2014-07-30)

iv

Log Reference
95.14 SRM/4/BATTEMPDGHIGHPROTECT
95.15 SRM/2/BATTEMPLOW
95.16 SRM/4/BATTEMPLOWPROTECT
95.17 SRM/4/BATTEMPLOWRESUME
About This Document
Changes in Issue 02 (2013-07-25) V200R003C00

Changes in Issue 01 (2013-05-30) V200R003C00

Initial commercial release.
Issue 07 (2014-07-30)


Log Reference
Contents
Contents
About This Document.....................................................................................................................ii
1 Introduction....................................................................................................................................1
1.1 Log Message Format Description...................................................................................................................................2
1.2 Log Severity Description................................................................................................................................................3
2 6OVER4...........................................................................................................................................5
2.1 6OVER4/4/CAMPNUM_UNCAMP.............................................................................................................................6
2.2 6OVER4/4/MAXNUM_UNCAMP...............................................................................................................................6
3 AAA..................................................................................................................................................8
3.1 AAA/6/LOCAL_ACCOUNT_UNLOCK......................................................................................................................9
3.2 AAA/6/LOCAL_ACCOUNT_LOCK............................................................................................................................9
3.3 AAA/6/LOCAL_ACCOUNT_MODIFY.....................................................................................................................10
3.4 AAA/6/LOCAL_ACCOUNT_DEL.............................................................................................................................10
3.5 AAA/6/LOCAL_ACCOUNT_EXPIRED....................................................................................................................11
3.6 AAA/6/LOCAL_ACCOUNT_MODIFYPWD_UNLOCK.........................................................................................12
3.7 AAA/6/LOCAL_ACCOUNT_MODIFYPWD_LOCK...............................................................................................12
4 ACLE..............................................................................................................................................14
4.1 ACLE/4/ACLLOG.......................................................................................................................................................15
5 ADDR............................................................................................................................................16
5.1 ADDR/4/COLLISION_CNT_EXCEED......................................................................................................................17
6 ALML.............................................................................................................................................18
6.1 ALML/4/ENTUP..........................................................................................................................................................19
6.2 ALML/4/ENT_PLUG_IN............................................................................................................................................19
6.3 ALML/4/ENT_PULL_OUT.........................................................................................................................................20
6.4 ALML/4/TEMP_LOWER............................................................................................................................................20
6.5 ALML/4/TEMP_LOWER_RESUME..........................................................................................................................21
7 APS.................................................................................................................................................23
7.1 APS/7/DEFECT_NOTIFY_PFM.................................................................................................................................24
7.2 APS/7/PKT_PLAT_TO_PPI........................................................................................................................................24
7.3 APS/7/STATE_NOTIFY_PFM....................................................................................................................................26
7.4 APS/7/STATE_NOTIFY_PPI......................................................................................................................................27
Issue 07 (2014-07-30)

vi

Log Reference
Contents
7.5 APS/7/SYN_MES_IO_TO_MAIN..............................................................................................................................28
7.6 APS/7/SYN_MES_MAIN_TO_IO..............................................................................................................................29
8 ARP.................................................................................................................................................31
8.1 ARP/6/ARPIGNORETC..............................................................................................................................................32
8.2 ARP/6/ARP_LOG_CONFIRM....................................................................................................................................32
8.3 ARP/4/ARP_LOG_DUPLICATE_IPADDR_DETECT..............................................................................................33
8.4 ARP/4/ARP_DUPLICATE_IPADDR.........................................................................................................................34
8.5 ARP/6/RSTARPALL...................................................................................................................................................34
8.6 ARP/6/RSTARPSTATIC.............................................................................................................................................35
9 ARPLINK......................................................................................................................................37
9.1 ARPLINK/6/ARPLINK_DELETE..............................................................................................................................38
10 ASSISTANT...............................................................................................................................40
10.1 ASSISTANT/6/ASSISTANTSCHEDULE................................................................................................................41
10.2 ASSISTANT/4/JOB_DEL_CONFIRM.....................................................................................................................41
11 BFD...............................................................................................................................................43
11.1 BFD/3/ACLRUNOUT................................................................................................................................................45
11.2 BFD/3/ADDFSM_ERR..............................................................................................................................................45
11.3 BFD/3/ADDRCV_ERR..............................................................................................................................................46
11.4 BFD/4/BOARDTYPEERR........................................................................................................................................46
11.5 BFD/4/CANTFINDBFDENTRY...............................................................................................................................47
11.6 BFD/6/CREATE_SESS_ERR....................................................................................................................................48
11.7 BFD/6/CRTSESS.......................................................................................................................................................49
11.8 BFD/3/DELFSM_ERR...............................................................................................................................................50
11.9 BFD/3/DELRCV_ERR..............................................................................................................................................50
11.10 BFD/3/DELRCV_ERR_ADD..................................................................................................................................51
11.11 BFD/5/DELSESS.....................................................................................................................................................52
11.12 BFD/3/DELSESS_SYS............................................................................................................................................52
11.13 BFD/4/FPGAENTRYERR.......................................................................................................................................53
11.14 BFD/4/GETBOARDFAIL........................................................................................................................................54
11.15 BFD/4/GETPWINFOFAIL......................................................................................................................................54
11.16 BFD/4/IO_REACH_SESSLMT...............................................................................................................................55
11.17 BFD/3/IPCALLOCFAIL..........................................................................................................................................56
11.18 BFD/3/IPCSENDFAIL.............................................................................................................................................56
11.19 BFD/4/LABELALLOCFAIL...................................................................................................................................57
11.20 BFD/4/LABELFREEFAIL.......................................................................................................................................57
11.21 BFD/3/MEMORYALLOCFAIL..............................................................................................................................58
11.22 BFD/4/REACH_IF_LIM..........................................................................................................................................59
11.23 BFD/3/REALTIME_CFG_ERR..............................................................................................................................59
11.24 BFD/4/STACHG_DWNTOUP................................................................................................................................60
11.25 BFD/4/STACHG_TODWN.....................................................................................................................................61
Issue 07 (2014-07-30)

vii

Log Reference
Contents
11.26 BFD/4/STACHG_TOUP..........................................................................................................................................62
11.27 BFD/4/TCAMALLOCFAIL....................................................................................................................................63
11.28 BFD/4/TCAMFREEFAIL........................................................................................................................................64
11.29 BFD/4/UNKNOWNPDT..........................................................................................................................................65
11.30 BFD/4/UPDATEACLFAIL......................................................................................................................................65
11.31 BFD/4/UPDATEFWDFAIL.....................................................................................................................................66
12 BGP...............................................................................................................................................67
12.1 BGP/4/ASPATH_EXCEED_MAXNUM..................................................................................................................69
12.2 BGP/4/CANNOT_FIND_PEER................................................................................................................................69
12.3 BGP/6/CONFIRM_N.................................................................................................................................................70
12.4 BGP/6/CONFIRM_TIMEOUT..................................................................................................................................70
12.5 BGP/6/CONFIRM_Y.................................................................................................................................................71
12.6 BGP/6/GR_NOTIFY_ENTER...................................................................................................................................72
12.7 BGP/6/GR_NOTIFY_EXIT.......................................................................................................................................72
12.8 BGP/6/INST_EXIT_GR.............................................................................................................................................73
12.9 BGP/4/IPV4_ROUTE_LCS_EXC.............................................................................................................................73
12.10 BGP/4/IPV6_ROUTE_LCS_EXCD........................................................................................................................74
12.11 BGP/3/MEMORY_RESTORE................................................................................................................................75
12.12 BGP/6/RECV_NOTIFY...........................................................................................................................................75
12.13 BGP/3/RECV_UNSPT_AFI....................................................................................................................................76
12.14 BGP/4/ROUTEADD_REACHLMT........................................................................................................................77
12.15 BGP/4/ROUTPRIX_EXCEED................................................................................................................................77
12.16 BGP/3/ROUTTHRD_REACHED............................................................................................................................78
12.17 BGP/6/SEND_NOTIFY...........................................................................................................................................79
12.18 BGP/6/SNMP_PEER_SHUTDOWN.......................................................................................................................80
12.19 BGP/4/BGP_SPEC_RT_EXCD...............................................................................................................................81
12.20 BGP/3/STATE_CHG_UPDOWN............................................................................................................................81
12.21 BGP/4/UNKNOWN_TYPE.....................................................................................................................................82
13 CFM..............................................................................................................................................84
13.1 CFM/4/B2S_BACKUP_FAILED..............................................................................................................................86
13.2 CFM/4/CFM_INCONSISTENT_FILE_IMG............................................................................................................86
13.3 CFM/4/CFM_INCONSISTENT_FILE_CFG............................................................................................................87
13.4 CFM/6/CFM_OVERWRITESOFTWARE................................................................................................................88
13.5 CFM/4/CFM_SYNCFGFILEFAIL............................................................................................................................89
13.6 CFM/6/CFM_UNDO_SCHEDULE_NO...................................................................................................................89
13.7 CFM/6/CFM_UNDO_SCHEDULE_YES.................................................................................................................90
13.8 CFM/4/CLEAR..........................................................................................................................................................91
13.9 CFM/4/CFM_CLEARINTERFACECFG..................................................................................................................91
13.10 CFM/4/CRC_CHK...................................................................................................................................................92
13.11 CFM/5/FILE_NOTEXIST........................................................................................................................................93
13.12 CFM/4/FILELENGTH_NOTMATCH....................................................................................................................94
Issue 07 (2014-07-30)

viii

Log Reference
Contents
13.13 CFM/4/OVERWRITE_FILE....................................................................................................................................95
13.14 CFM/3/RECOVERCMDFAIL.................................................................................................................................95
13.15 CFM/4/RST_CFG....................................................................................................................................................96
13.16 CFM/4/SAVE...........................................................................................................................................................96
13.17 CFM/4/SAVE_FILE.................................................................................................................................................97
13.18 CFM/5/SAVE_FILE_RECORD..............................................................................................................................98
13.19 CFM/5/SAVECFG_NO............................................................................................................................................98
13.20 CFM/5/SAVECFG_YES..........................................................................................................................................99
13.21 CFM/3/CFM_SLAVERUNCMDFAIL....................................................................................................................99
13.22 CFM/5/SUMRULECANCEL................................................................................................................................100
13.23 CFM/5/SUMRULECHG........................................................................................................................................101
13.24 CFM/5/SUMTMRCHG..........................................................................................................................................102
14 CMD...........................................................................................................................................103
14.1 CMD/4/CLKCHGREBOOTCANCELED...............................................................................................................104
14.2 CMD/4/CMD_PRI_REARRG.................................................................................................................................104
14.3 CMD/4/DIAG_OVERWRITE.................................................................................................................................105
14.4 CMD/4/REBOOT.....................................................................................................................................................105
14.5 CMD/4/SCH_REBOOT...........................................................................................................................................106
14.6 CMD/4/SUPERLOGIN............................................................................................................................................107
15 CSPF...........................................................................................................................................108
15.1 CSPF/3/IGP_LINK_INFONULL.............................................................................................................................109
15.2 CSPF/3/IGP_NWLSA_INFONULL........................................................................................................................109
15.3 CSPF/3/IGP_RID_INFONULL...............................................................................................................................110
15.4 CSPF/3/INVAL_LINK.............................................................................................................................................111
15.5 CSPF/3/INVAL_NWLINK......................................................................................................................................111
15.6 CSPF/4/MAX_LINK_REACH................................................................................................................................112
15.7 CSPF/4/MAX_NODE_REACH...............................................................................................................................112
15.8 CSPF/4/MAX_NWLSA_REACH............................................................................................................................113
15.9 CSPF/4/MAX_SRLG_REACH................................................................................................................................113
15.10 CSPF/3/MEM_FAIL..............................................................................................................................................114
15.11 CSPF/3/PATH_ERROR.........................................................................................................................................115
15.12 CSPF/3/Q_ERROR................................................................................................................................................115
15.13 CSPF/3/TIME_FAIL..............................................................................................................................................116
16 MAD...........................................................................................................................................117
16.1 MAD/4/CONFLICT_DETECT................................................................................................................................118
16.2 MAD/4/MEMBER_LOST.......................................................................................................................................118
16.3 MAD/4/PORT_SHUTDOWN..................................................................................................................................119
16.4 MAD/4/PORT_RESTORE.......................................................................................................................................119
17 DLDP..........................................................................................................................................121
17.1 DLDP/4/GLOBAL_NB_FULL................................................................................................................................122
Issue 07 (2014-07-30)

ix

Log Reference
Contents
17.2 DLDP/4/PORT_NB_FULL......................................................................................................................................122
18 DOT1X.......................................................................................................................................124
18.1 DOT1X/4/ADD_ACL_FAILED..............................................................................................................................125
18.2 DOT1X/5/QUIETTABLE_FULL............................................................................................................................125
19 DEFD..........................................................................................................................................127
19.1 DEFD/4/CPCAR_DROP_MPU...............................................................................................................................128
19.2 DEFD/4/CPCAR_DROP_LPU................................................................................................................................128
20 DHCP.........................................................................................................................................130
20.1 DHCP/4/DHCP_CLIENT_CONFLICT_IPADDR..................................................................................................131
20.2 DHCP/0/DHCP_SERVER_DETECT......................................................................................................................131
20.3 DHCP/0/DHCPRATET_LIMIT...............................................................................................................................132
20.4 DHCP/0/DHCPV6_SERVER_DETECT.................................................................................................................133
20.5 DHCP/0/DHCPV6RATET_DETECT......................................................................................................................133
20.6 DHCP/4/DHCP_INFO_LOG_DHCP_ADD_ACL_FAILED..................................................................................134
20.7 DHCP/4/DHCP_INFO_LOG_DHCP_REMOTEBACKUP_FAILED....................................................................135
20.8 DHCP/0/ND_SERVER_DETECT...........................................................................................................................135
20.9 DHCP/4/DHCP_BINDTBL_ADDR_CONFLICT..................................................................................................136
20.10 DHCP/4/DHCP_INFO_LOG_DHCP_SLAVE_LOW_SPACE............................................................................137
20.11 DHCP/4/DHCP_RELAY_WRONG_GIADDR.....................................................................................................138
20.12 DHCP/4/DHCP_RELAY_WRONG_MAC...........................................................................................................138
21 DSA............................................................................................................................................140
21.1 DSA/4/FILE_READ_ERR.......................................................................................................................................141
21.2 DSA/4/FILE_SAVE_ERR.......................................................................................................................................141
21.3 DSA/3/HOST_PUBKEY_BAK_FAL......................................................................................................................142
21.4 DSA/4/HOSTKEY_BACKUP_ERR.......................................................................................................................142
21.5 DSA/4/HOSTKEY_BAK_DEL_ERR.....................................................................................................................143
21.6 DSA/3/HOSTKEY_DEL_ERR................................................................................................................................143
21.7 DSA/3/HOSTKEY_SAVE_ERR.............................................................................................................................144
21.8 DSA/6/KEY_SIZE...................................................................................................................................................145
21.9 DSA/4/REPLACE_KEYS........................................................................................................................................145
22 EFM............................................................................................................................................147
22.1 EFM/3/INVALID_ORGSPECIFICINFOTLV........................................................................................................148
22.2 EFM/2/NONTHRESHOLD.....................................................................................................................................148
22.3 EFM/6/REMOTE_STATE_CHANGED.................................................................................................................149
22.4 EFM/3/THRESHOLD..............................................................................................................................................150
22.5 EFM/4/TRIGGERIFNET.........................................................................................................................................151
22.6 EFM/5/ISSUSTATUS..............................................................................................................................................152
23 EOAM1AG................................................................................................................................154
23.1 EOAM1AG/3/EOAMADP_FPGAFULL................................................................................................................155
Issue 07 (2014-07-30)


Log Reference
Contents
23.2 EOAM1AG/5/ISSUSTATUS...................................................................................................................................155
24 ERPS (G.8032)...........................................................................................................................157
24.1 ERPS/5/PORTADDRINGFAILED..........................................................................................................................158
24.2 ERPS/5/PORTFWDSTATUS..................................................................................................................................158
24.3 ERPS/5/PORTSIGNALSTATUS............................................................................................................................159
24.4 ERPS/5/TOPOCHANGE.........................................................................................................................................160
25 ERRORDOWN.........................................................................................................................161
25.1 ERRDOWN/4/ERRDOWN_DOWNNOTIFY........................................................................................................162
25.2 ERRDOWN/4/ERRDOWN_DOWNRECOVER....................................................................................................163
26 ETRUNK....................................................................................................................................164
26.1 ETRUNK/4/MBR_PHYSTAT_CHG......................................................................................................................165
26.2 ETRUNK/4/MEMBER_STATE_CHG....................................................................................................................165
26.3 ETRUNK/4/STATE_CHG.......................................................................................................................................167
27 EZOP..........................................................................................................................................169
27.1 EZOP/3/UPGRADE_FAIL......................................................................................................................................170
27.2 EZOP/3/PROCESS_STOP.......................................................................................................................................170
28 FILTER.......................................................................................................................................172
28.1 FILTER/6/PKT_FLT_INFO....................................................................................................................................173
29 FSP..............................................................................................................................................174
29.1 FSP/4/MODIFY_PRIORITY...................................................................................................................................175
29.2 FSP/4/NO_PACKET................................................................................................................................................175
29.3 FSP/4/MODIFY_ID.................................................................................................................................................176
29.4 FSP/4/TOPO_CHANGE..........................................................................................................................................176
29.5 FSP/4/STACK_LEAVE...........................................................................................................................................177
29.6 FSP/4/SWTICH_REBOOTING...............................................................................................................................177
29.7 FSP/4/SWTICH_REBOOTING...............................................................................................................................178
29.8 FSP/4/NBR_DISCOVER.........................................................................................................................................179
29.9 FSP/4/NBR_LOST...................................................................................................................................................179
29.10 FSP/4/SWTICH_REBOOTING.............................................................................................................................180
29.12 FSP/4/SPDU_LOST...............................................................................................................................................181
30 FTPS........................................................................................................................................... 183
30.1 FTPS/5/ACL_DENY................................................................................................................................................184
30.2 FTPS/3/LOGINFAILED..........................................................................................................................................184
30.3 FTPS/5/LOGIN_OK.................................................................................................................................................185
30.4 FTPS/5/LOGOUT_OK.............................................................................................................................................186
30.5 FTPS/5/REQUEST...................................................................................................................................................186
30.6 FTPS/3/TRS_FAIL...................................................................................................................................................187
Issue 07 (2014-07-30)

xi

Log Reference
Contents
31 GRE............................................................................................................................................189
31.1 GRE/6/GRE_CAMP.................................................................................................................................................190
31.2 GRE/4/GRE_CAMPNUM_UNCAMP....................................................................................................................190
31.3 GRE/4/GRE_MAXNUM_UNCAMP......................................................................................................................191
31.4 GRE/4/GRE_UNIDE_SPEC_T................................................................................................................................192
32 GRESM......................................................................................................................................193
32.1 GRESM/3/TokenConflict.........................................................................................................................................194
33 GRSA.........................................................................................................................................195
33.1 GRSA/4/COPY_PUBPRIVKEY_FAILURE...........................................................................................................196
33.2 GRSA/4/CREATE_PRIVKEY_FAILURE..............................................................................................................196
33.3 GRSA/4/DECODE_PRIVKEY_FAILURE.............................................................................................................197
33.4 GRSA/4/DECODE_PUBKEY_FAILURE..............................................................................................................197
33.5 GRSA/4/DECRYPT_PRIVKEY_FAILURE...........................................................................................................198
33.6 GRSA/4/ENCODE_PRIVKEY_FAILURE.............................................................................................................199
33.7 GRSA/4/ENCODE_PUBKEY_FAILURE..............................................................................................................199
33.8 GRSA/4/ENCRYPT_PRIVKEY_FAILURE...........................................................................................................200
33.9 GRSA/4/EXTRACT_PRIVKEY_FAILURE...........................................................................................................200
33.10 GRSA/4/KEY_PAIR_GEN_FAILED....................................................................................................................201
33.11 GRSA/6/KEY_PAIR_GENERATE_SUCCESS....................................................................................................202
33.12 GRSA/4/KEYPAIR_NOT_EXISTS......................................................................................................................202
33.13 GRSA/4/PEM_DECODE_FAILURE....................................................................................................................203
33.14 GRSA/4/PEM_ENCODE_FAILURE....................................................................................................................203
33.15 GRSA/4/REALTIME_BAK_SEND_FAILURE...................................................................................................204
33.16 GRSA/4/SAVE_KEYPAIR_FAILURE.................................................................................................................205
33.17 GRSA/6/SAVE_KEYPAIR_SUCCESS................................................................................................................205
34 HA...............................................................................................................................................207
34.1 HA/6/RESTART......................................................................................................................................................208
34.2 HA/5/RESTSLA.......................................................................................................................................................208
34.3 HA/5/RSTSLA.........................................................................................................................................................209
34.4 HA/6/SWITCH_CHASSIS......................................................................................................................................209
34.5 HA/6/SWITCHOVER..............................................................................................................................................210
35 HTTP..........................................................................................................................................212
35.1 HTTP/4/FILETRANSFERFAILURE......................................................................................................................213
35.2 HTTP/5/FILETRANSFEROK.................................................................................................................................213
35.3 HTTP/3/LOGINFAIL...............................................................................................................................................214
35.4 HTTP/6/LOGINOK..................................................................................................................................................215
35.5 HTTP/5/LOGIN_TIMEOUT....................................................................................................................................216
35.6 HTTP/4/VERIFYFAIL.............................................................................................................................................216
36 HWCM.......................................................................................................................................218
Issue 07 (2014-07-30)

xii

Log Reference
Contents
36.1 HWCM/4/CCOPY....................................................................................................................................................219
36.2 HWCM/5/TRAPLOG...............................................................................................................................................219
37 IFNET.........................................................................................................................................221
37.1 IFNET/4/ACOAM_ENABLE_FAIL.......................................................................................................................223
37.2 IFNET/5/ACOAM_STATE_CHANGE...................................................................................................................223
37.3 IFNET/6/APP_NOTIFY_FAULT............................................................................................................................224
37.4 IFNET/4/BOARD_DISABLE..................................................................................................................................225
37.5 IFNET/4/BOARD_ENABLE...................................................................................................................................225
37.6 IFNET/4/BWRATE_IN_RESUME.........................................................................................................................226
37.7 IFNET/4/BWRATE_IN_RISING............................................................................................................................226
37.8 IFNET/4/BWRATE_OUT_RESUME.....................................................................................................................227
37.9 IFNET/4/BWRATE_OUT_RISING........................................................................................................................228
37.10 IFNET/4/CARD_DISABLE...................................................................................................................................228
37.11 IFNET/4/CARD_ENABLE....................................................................................................................................229
37.12 IFNET/4/CHANGE_ENCAP.................................................................................................................................230
37.13 IFNET/4/FLOWDOWN.........................................................................................................................................230
37.14 IFNET/4/FLOWUP................................................................................................................................................231
37.15 IFNET/4/IF_DISABLE..........................................................................................................................................231
37.16 IFNET/4/IF_ENABLE...........................................................................................................................................232
37.17 IFNET/4/IF_HOTTASK_CREATE.......................................................................................................................233
37.18 IFNET/4/IF_HOTTASK_DELETE.......................................................................................................................233
37.19 IFNET/6/IF_INFO_CHANGE...............................................................................................................................234
37.20 IFNET/4/IF_STATE...............................................................................................................................................234
37.21 IFNET/4/LINK_STATE.........................................................................................................................................235
37.22 IFNET/4/LINKNO_STATE...................................................................................................................................236
37.23 IFNET/6/LSP_STATE_CHANGE.........................................................................................................................236
37.24 IFNET/4/NOTIFY_BFD_FAIL.............................................................................................................................237
37.25 IFNET/4/NTF_ACOAM_STATE_FAIL...............................................................................................................238
37.26 IFNET/6/NTF_STATE_CHANGE........................................................................................................................238
37.27 IFNET/4/OUT_OF_MEMORY.............................................................................................................................239
37.28 IFNET/6/PW_STATE_CHANGE..........................................................................................................................239
37.29 IFNET/6/REPEAT_NOTIFY.................................................................................................................................240
38 IGMP..........................................................................................................................................242
38.1 IGMP/6/GLB_ENTRY.............................................................................................................................................243
38.2 IGMP/6/GLB_LIMIT...............................................................................................................................................243
38.3 IGMP/6/IF_ENTRY.................................................................................................................................................244
38.4 IGMP/6/IF_LIMIT...................................................................................................................................................245
38.5 IGMP/6/INST_ENTRY............................................................................................................................................246
38.6 IGMP/6/INST_LIMIT..............................................................................................................................................246
38.7 IGMP/4/INT_INV....................................................................................................................................................247
38.8 IGMP/4/REG_ACL_F..............................................................................................................................................248
Issue 07 (2014-07-30)

xiii

Log Reference
Contents
38.9 IGMP/4/SET_IGMP_GLBPLC_FAIL.....................................................................................................................248
38.10 IGMP/6/VER1_RECV_INV..................................................................................................................................249
38.11 IGMP/6/VER2_RECV_INV..................................................................................................................................250
38.12 IGMP/6/VER3_RECV_INV..................................................................................................................................251
39 INFO...........................................................................................................................................252
39.1 INFO/4/DBG_ALL..................................................................................................................................................253
39.2 INFO/6/LOGFILE_DELETED................................................................................................................................253
39.3 INFO/4/RST_LOGB................................................................................................................................................254
39.4 INFO/4/SUPPRESS_LOG.......................................................................................................................................254
40 IPV4-IPV6..................................................................................................................................256
40.1 IPV4-IPV6/4/MAXNUM_UNCAMP......................................................................................................................257
40.2 IPV4-IPV6/3/MTU_MIN.........................................................................................................................................257
40.3 IPV4-IPV6/4/UNIDE_SPEC_T...............................................................................................................................258
41 IPV6FIBAGENT.......................................................................................................................259
41.1 IPV6FIBAGENT/3/MEMCHECK...........................................................................................................................260
41.2 IPV6FIBAGENT/4/PLYDELE6..............................................................................................................................260
41.3 IPV6FIBAGENT/4/SENDPLYSLOT6....................................................................................................................261
41.4 IPV6FIBAGENT/4/SENDQUESLOTFAIL6..........................................................................................................262
41.5 IPV6FIBAGENT/6/TRIGDELEROUT6.................................................................................................................262
42 IPV6PP.......................................................................................................................................264
42.1 IPV6PP/3/REACHMAX..........................................................................................................................................265
42.2 IPV6PP/3/REASSERROR.......................................................................................................................................265
43 IPV6TCP....................................................................................................................................267
43.1 TCP6/3/TCP6_NOACTV_RECVKEY....................................................................................................................268
43.2 TCP6/3/TCP6_NOACTV_SENDKEY....................................................................................................................268
44 ISIS.............................................................................................................................................270
44.1 ISIS/6/AC_RT_SEL_FAIL......................................................................................................................................276
44.2 ISIS/6/AC_RT_V6_SEL_FAIL...............................................................................................................................276
44.3 ISIS/6/ADD_L1_SUMRT_FAIL.............................................................................................................................277
44.4 ISIS/6/ADD_L2_SUMRT_FAIL.............................................................................................................................278
44.5 ISIS/6/ADD_LKINFO_CSPF_FAIL.......................................................................................................................278
44.6 ISIS/6/ADD_MDF_LK_CSPF_FAIL......................................................................................................................279
44.7 ISIS/6/ADD_NTWK_MPLS_FAIL.........................................................................................................................280
44.8 ISIS/6/ADD_P2P_ADJ_ERR...................................................................................................................................281
44.9 ISIS/6/ADD_REDSTRBT_RT_FAIL......................................................................................................................282
44.10 ISIS/6/ADD_RTTO_LSP_FAIL............................................................................................................................282
44.11 ISIS/4/ADD_SRLGTOLINK_FAIL......................................................................................................................283
44.12 ISIS/6/ADD_SUMMRT_URT_FAIL....................................................................................................................284
44.13 ISIS/6/ADD_SUMRT_FAIL..................................................................................................................................285
Issue 07 (2014-07-30)

xiv

Log Reference
Contents
44.14 ISIS/6/ADD_TE_TLV_FAIL.................................................................................................................................285
44.15 ISIS/4/ADJ_CHANGE_LEVEL............................................................................................................................286
44.16 ISIS/6/ALIID_TLV_LEN_SHORT.......................................................................................................................289
44.17 ISIS/6/AREA_ADDR_INVALID..........................................................................................................................289
44.18 ISIS/6/AUTH_TLV_OVER_ONECE....................................................................................................................290
44.19 ISIS/6/BAD_TLV_LEN.........................................................................................................................................290
44.20 ISIS/6/BIND_SOKT_FAIL....................................................................................................................................291
44.21 ISIS/5/CIRC_STATE_SET....................................................................................................................................292
44.22 ISIS/6/CONFLICT_SYSTEM_ID.........................................................................................................................293
44.23 ISIS/6/CREA_AREA_TLV_FAIL.........................................................................................................................293
44.24 ISIS/6/CREATE_CIRCUIT_FAIL........................................................................................................................294
44.25 ISIS/6/CRT_BFD_SESION_FAIL........................................................................................................................294
44.26 ISIS/6/CRT_P2P_ADJ_FAIL................................................................................................................................295
44.27 ISIS/6/DEL_ATTSY_FAIL...................................................................................................................................296
44.28 ISIS/6/DEL_BFD_SESSION_FAIL......................................................................................................................296
44.29 ISIS/6/DEL_LKINFO_CSPF_FAIL......................................................................................................................297
44.30 ISIS/6/DEL_NTWK_MPLS_FAIL........................................................................................................................298
44.31 ISIS/6/DEL_SUMMRT_URT_FAIL.....................................................................................................................299
44.32 ISIS/6/DISABL_RT_FAIL....................................................................................................................................299
44.33 ISIS/6/DISABLE_ROUTELEAK_V6...................................................................................................................300
44.34 ISIS/6/DYNC_NAME_FAIL.................................................................................................................................301
44.35 ISIS/6/EN_TE_FAIL_NO_RTID...........................................................................................................................301
44.36 ISIS/6/ENABLE_TE_LV1_FAIL..........................................................................................................................302
44.37 ISIS/6/ENABLE_TE_LV2_FAIL..........................................................................................................................302
44.38 ISIS/6/FAIL_CMD_IN_AMB................................................................................................................................303
44.39 ISIS/6/FAIL_CMD_IN_SMB................................................................................................................................304
44.40 ISIS/6/FAIL_CRT_OPT_DYN_NM......................................................................................................................304
44.41 ISIS/6/FAIL_SEND_DICT....................................................................................................................................305
44.42 ISIS/6/FAIL_TRANS_P2P_CSNP........................................................................................................................306
44.43 ISIS/6/FD_CUR_IFINDEX_FAIL.........................................................................................................................306
44.44 ISIS/6/FD_SBNTADDR_BDC_FAIL...................................................................................................................307
44.45 ISIS/6/FIND_CIRCUIT_FAIL...............................................................................................................................307
44.46 ISIS/6/FIND_SYSID_FAIL...................................................................................................................................308
44.47 ISIS/6/FLO_LSP_OLO_FAIL...............................................................................................................................308
44.48 ISIS/6/FT_GT_RT_URM_FAIL............................................................................................................................309
44.49 ISIS/6/GEN_ATT_LSP_FAIL...............................................................................................................................310
44.50 ISIS/4/GENLSPDESC_FAILSMB........................................................................................................................310
44.51 ISIS/6/GET_IF_FAILSMB....................................................................................................................................311
44.52 ISIS/6/GET_IFINSTN_ID_FAIL...........................................................................................................................312
44.53 ISIS/6/GET_IFNET_BY_ALIAS..........................................................................................................................313
44.54 ISIS/6/GET_LINKINFO_FAIL.............................................................................................................................313
Issue 07 (2014-07-30)

xv

Log Reference
Contents
44.55 ISIS/6/GT_ACTVE_RT_RM_FAIL......................................................................................................................314
44.56 ISIS/6/GT_CIRC_IFINDX_FAIL..........................................................................................................................315
44.57 ISIS/6/GT_CIRCINDEX_FAIL.............................................................................................................................315
44.58 ISIS/6/GT_INFO_RDM_FAIL..............................................................................................................................316
44.59 ISIS/6/GT_ININDEX_FAIL..................................................................................................................................317
44.60 ISIS/6/GT_LGC_PHY_FAIL.................................................................................................................................317
44.61 ISIS/6/GT_LGCIF_V6ADDR_FAIL.....................................................................................................................318
44.62 ISIS/6/GT_LGCL_SUBNET_FAIL.......................................................................................................................318
44.63 ISIS/6/GT_LV_RT_URM_FAIL...........................................................................................................................319
44.64 ISIS/6/GT_LV_RT_V6_URM_FAIL....................................................................................................................320
44.65 ISIS/6/GT_MPLSTE_RM_FAIL...........................................................................................................................321
44.66 ISIS/6/GT_PHYIF_IFNET_FAIL..........................................................................................................................322
44.67 ISIS/6/GT_RTENTRY_URM_FAIL.....................................................................................................................322
44.68 ISIS/6/GT_RTID_RM_FAIL.................................................................................................................................323
44.69 ISIS/6/GT_TELK_INFO_FAIL.............................................................................................................................324
44.70 ISIS/6/GT_V6_PHYIF_FAIL................................................................................................................................324
44.71 ISIS/6/GT_V6ADDR_PHYIF_FAIL.....................................................................................................................325
44.72 ISIS/6/IF_TEMP.....................................................................................................................................................326
44.73 ISIS/4/IMPORT_LIMIT_EXCEED.......................................................................................................................326
44.74 ISIS/4/IMPORT_LIMIT_RESTORE.....................................................................................................................327
44.75 ISIS/6/INIT_DEC_FAIL........................................................................................................................................328
44.76 ISIS/4/INT_BUILDRUN_FAIL.............................................................................................................................328
44.77 ISIS/6/INTI_ISIS_FAIL.........................................................................................................................................329
44.78 ISIS/3/INVALID_DSTEMOD...............................................................................................................................330
44.79 ISIS/6/INVID_DR_CHANGE...............................................................................................................................330
44.80 ISIS/6/INVID_TLV_TYPE_REP..........................................................................................................................331
44.81 ISIS/6/JN_MTCAST_ADDR_FAIL......................................................................................................................331
44.82 ISIS/6/JOIN_L1_ADDR_FAIL..............................................................................................................................332
44.83 ISIS/6/JOIN_L2_ADDR_FAIL..............................................................................................................................333
44.84 ISIS/6/JOIN_ALLIS_ADDR_FAIL.......................................................................................................................333
44.85 ISIS/6/L3VPN_FRR_CHANGE............................................................................................................................334
44.86 ISIS/6/LDP_INFORM_RM_ENAB.......................................................................................................................334
44.87 ISIS/6/LEAVE_L1_ADDR_FAIL.........................................................................................................................335
44.88 ISIS/6/LEAVE_L2_ADDR_FAIL.........................................................................................................................336
44.89 ISIS/6/LEAVE_ALLIS_ADDR_FAIL..................................................................................................................336
44.90 ISIS/5/LOCALSYS_DIS_REST_RT.....................................................................................................................337
44.91 ISIS/6/LV_MTCAST.............................................................................................................................................337
44.92 ISIS/6/LV_MTCAST_ADDR_FAIL.....................................................................................................................338
44.93 ISIS/6/MATCH_CIRC_FAIL................................................................................................................................339
44.94 ISIS/6/MD_LV_RT_FAIL.....................................................................................................................................339
44.95 ISIS/6/MD_LV_RT_V6_FAIL..............................................................................................................................340
Issue 07 (2014-07-30)

xvi

Log Reference
Contents
44.96 ISIS/6/MDF_LKINFO_CSPF_FAIL.....................................................................................................................341
44.97 ISIS/6/MDF_NTWK_MPLS_FAIL.......................................................................................................................342
44.98 ISIS/6/MTU_EXCEED_MAXPDU.......................................................................................................................342
44.99 ISIS/6/NSR_MSG_PROC......................................................................................................................................343
44.100 ISIS/6/NSR_STATE_CHANGE..........................................................................................................................344
44.101 ISIS/6/P2P_CIRC_TX_LSP_FAIL......................................................................................................................344
44.102 ISIS/4/PEER_DOWN_BFDDOWN....................................................................................................................345
44.103 ISIS/4/PEER_DOWN_CIRC_DOWN.................................................................................................................346
44.104 ISIS/4/PEER_DOWN_DIS_CHANGE................................................................................................................347
44.105 ISIS/4/PEER_DOWN_LOW_MEMORY............................................................................................................348
44.106 ISIS/4/PEER_DOWN_NO_MEMORY...............................................................................................................349
44.107 ISIS/4/PEER_DOWN_REPTADJ........................................................................................................................350
44.108 ISIS/4/PEER_DOWN_REPTP2PADJ.................................................................................................................351
44.109 ISIS/4/PEER_DOWN_RPRDOWN.....................................................................................................................352
44.110 ISIS/4/PEER_DWN_ADJ_STATDWN...............................................................................................................353
44.111 ISIS/4/PEER_DWN_AREAMISMACH..............................................................................................................354
44.112 ISIS/4/PEER_DWN_CIRC_SILENT..................................................................................................................355
44.113 ISIS/4/PEER_DWN_HLDTMR_EXPR..............................................................................................................356
44.114 ISIS/4/PEER_DWN_ID_CONFLICT..................................................................................................................357
44.115 ISIS/4/PEER_DWN_LEVEL_CHANG...............................................................................................................358
44.116 ISIS/4/PEER_DWN_PDUMISMATCH..............................................................................................................360
44.117 ISIS/4/PEER_DWN_SYS_DISABLE.................................................................................................................361
44.118 ISIS/4/PEER_DWN_SYSTYP_UNKN...............................................................................................................362
44.119 ISIS/5/PEER_UP_ADJ_CREATE.......................................................................................................................363
44.120 ISIS/6/PROCESS_TMR_EVENT........................................................................................................................363
44.121 ISIS/6/RCV_BFD_DET_EVENT........................................................................................................................364
44.122 ISIS/4/RCV_ERRSELFLSP_SMB......................................................................................................................364
44.123 ISIS/6/RCV_NODE_DOWN_EVENT................................................................................................................366
44.124 ISIS/6/RCV_RPR_EVENT..................................................................................................................................367
44.125 ISIS/6/RCV_RPRMSG........................................................................................................................................367
44.126 ISIS/6/REA_MAX_SEQ_NUM...........................................................................................................................368
44.127 ISIS/6/REC_RM_MEM_RESTORE....................................................................................................................368
44.128 ISIS/4/REC_RM_MEM_SHORT........................................................................................................................369
44.129 ISIS/4/REDIST_THRESHOLD_REACH............................................................................................................370
44.130 ISIS/4/REDIST_THRESHOLD_REACH_CLEAR............................................................................................370
44.131 ISIS/6/RM_CIRC_CHANGE...............................................................................................................................371
44.132 ISIS/6/RM_CIRC_CHANGE_V6........................................................................................................................372
44.133 ISIS/6/RM_LOGICRC_CHGE............................................................................................................................373
44.134 ISIS/6/RM_LOGICRC_CHGE_V6.....................................................................................................................373
44.135 ISIS/6/SB_CIR_NOT_ENABLE.........................................................................................................................374
44.136 ISIS/6/SELF_LSP_EXPIRED..............................................................................................................................375
Issue 07 (2014-07-30)

xvii

Log Reference
Contents
44.137 ISIS/6/ST_LK_CNTRL_FAIL.............................................................................................................................375
44.138 ISIS/4/START_DISABLE_ISIS..........................................................................................................................376
44.139 ISIS/4/START_ENABLE_ISIS...........................................................................................................................376
44.140 ISIS/6/T1TMR_EXPIR_GR_CMD......................................................................................................................377
44.141 ISIS/6/T1TMR_LV1_CACEL_GR......................................................................................................................378
44.142 ISIS/6/T1TMR_LV1_EXPIR_GR.......................................................................................................................378
44.143 ISIS/6/T1TMR_LV1_EXPIR_GR_C...................................................................................................................379
44.144 ISIS/5/T1TMR_LV1_STOP_CMD......................................................................................................................380
44.145 ISIS/6/T1TMR_LV2_CACEL_GR......................................................................................................................380
44.147 ISIS/6/T1TMR_LV2_EXPIR_GR_C...................................................................................................................382
44.149 ISIS/6/T2TMR_LV1_CANCL_GR.....................................................................................................................383
44.152 ISIS/6/T2TMR_LV2_CANCL_GR.....................................................................................................................385
44.155 ISIS/6/T2TMR_STAR_L1_GR............................................................................................................................386
44.156 ISIS/6/T2TMR_STAR_L2_GR............................................................................................................................387
44.157 ISIS/6/T3TMR_CANCL_GR...............................................................................................................................387
44.158 ISIS/6/T3TMR_EXPIR_GR.................................................................................................................................388
44.159 ISIS/6/T3TMR_REINT_GR................................................................................................................................389
44.160 ISIS/6/T3TMR_STAR_GR..................................................................................................................................389
44.161 ISIS/5/T3TMR_STOP_CMD...............................................................................................................................390
44.162 ISIS/6/TMER_STIL_USED.................................................................................................................................390
44.163 ISIS/6/TORM_LEV_GR_DESTR.......................................................................................................................391
44.164 ISIS/6/TORM_LEV_RESTA_SMOH.................................................................................................................392
44.165 ISIS/5/TORM_LEV_RESTAR_CMD.................................................................................................................392
44.166 ISIS/5/TORM_LEV_RESTAR_SPF....................................................................................................................393
44.167 ISIS/5/TORM_RNTR_RESTAR_CMD..............................................................................................................393
44.168 ISIS/6/UNBIND_SOKT_FAIL............................................................................................................................394
44.169 ISIS/6/WRONG_VERSION................................................................................................................................395
45 Keychain....................................................................................................................................396
45.1 KEYCHAIN/3/CFG_INIT_FLD..............................................................................................................................398
45.2 KEYCHAIN/3/CMDSTRS_INIT_FLD...................................................................................................................398
45.3 KEYCHAIN/3/CORE_INIT_FLD...........................................................................................................................399
45.4 KEYCHAIN/3/GET_CORE_INTF_FLD................................................................................................................399
45.5 KEYCHAIN/3/GET_EXT_INTF_FLD...................................................................................................................400
45.6 KEYCHAIN/3/GIVE_CORE_INTF_FLD..............................................................................................................400
45.7 KEYCHAIN/3/HA_INIT_FLD................................................................................................................................401
Issue 07 (2014-07-30)

xviii

Log Reference
Contents
45.8 KEYCHAIN/6/KEYCH_ALGID_CHNG................................................................................................................401
45.9 KEYCHAIN/4/KEYCH_ALGID_CNFLCT............................................................................................................402
45.10 KEYCHAIN/6/KEYCH_APP_REG_FAIL...........................................................................................................403
45.11 KEYCHAIN/6/KEYCH_APP_REG_SUC............................................................................................................403
45.12 KEYCHAIN/6/KEYCH_APP_UNREG_FAIL.....................................................................................................404
45.13 KEYCHAIN/6/KEYCH_APP_UNREG_SUC......................................................................................................405
45.14 KEYCHAIN/6/KEYCH_CONFIG........................................................................................................................405
45.15 KEYCHAIN/6/KEYCH_ISSU_LOSLES..............................................................................................................406
45.16 KEYCHAIN/6/KEYCH_ISSU_LSY.....................................................................................................................406
45.17 KEYCHAIN/6/KEYCH_KEY_DEFAULT_A......................................................................................................407
45.18 KEYCHAIN/6/KEYCH_KEY_DEFAULT_I........................................................................................................408
45.19 KEYCHAIN/6/KEYCH_KEY_STATUS_AA......................................................................................................408
45.20 KEYCHAIN/6/KEYCH_KEY_STATUS_AI........................................................................................................409
45.21 KEYCHAIN/6/KEYCH_KEY_STATUS_IA........................................................................................................410
45.22 KEYCHAIN/6/KEYCH_KEYID_RECV_A.........................................................................................................410
45.23 KEYCHAIN/6/KEYCH_KEYID_RECV_I...........................................................................................................411
45.24 KEYCHAIN/6/KEYCH_KEYID_SEND_A..........................................................................................................411
45.25 KEYCHAIN/6/KEYCH_NO_SEND_KEYID.......................................................................................................412
45.26 KEYCHAIN/6/KEYCH_TCP_KIND_CHNG.......................................................................................................413
45.27 KEYCHAIN/6/KEYCH_TCP_REG_FAIL...........................................................................................................413
45.28 KEYCHAIN/6/KEYCH_TCP_REG_SUC............................................................................................................414
45.29 KEYCHAIN/6/KEYCH_TCP_UNREG_FAIL.....................................................................................................414
45.30 KEYCHAIN/6/KEYCH_TCP_UNREG_SUC......................................................................................................415
45.31 KEYCHAIN/6/KEYCH_UNCONFIG...................................................................................................................415
45.32 KEYCHAIN/4/MAX_KEYCHAIN_REACHED..................................................................................................416
45.33 KEYCHAIN/4/MAX_KEYID_REACHED..........................................................................................................417
45.34 KEYCHAIN/3/PAF_LCS_INIT_FLD...................................................................................................................417
45.35 KEYCHAIN/3/SHELL_INIT_FLD.......................................................................................................................418
45.36 KEYCHAIN/3/TWL_CREATE_INST_FLD........................................................................................................418
46 L2IF.............................................................................................................................................420
46.1 L2IF/6/FULLRULE..................................................................................................................................................421
46.2 L2IF/6/PORT_DOWN.............................................................................................................................................421
46.3 L2IF/6/PORT_UP.....................................................................................................................................................422
46.4 L2IF/6/ROUTER_TO_SWITCH.............................................................................................................................422
46.5 L2IF/6/SLA_RCV_INDEX_BY_BAT....................................................................................................................423
46.6 L2IF/6/SLA_RCV_PORTINDEX............................................................................................................................424
46.7 L2IF/6/SWITCH_TO_ROUTER.............................................................................................................................424
47 L2IFPPI......................................................................................................................................426
47.1 L2IFPPI/3/MAC_CFG_ERROR..............................................................................................................................427
48 L2V..............................................................................................................................................428
Issue 07 (2014-07-30)

xix

Log Reference
Contents
48.1 L2V/5/BFD_FOR_PW_DOWN...............................................................................................................................430
48.2 L2V/5/BFD_FOR_PW_UP......................................................................................................................................430
48.3 L2V/3/BGPRMTCEIDLOCIDSAME......................................................................................................................431
48.4 L2V/5/BGPVC_DWN..............................................................................................................................................431
48.5 L2V/5/BGPVC_P2W...............................................................................................................................................434
48.6 L2V/5/BGPVC_UP..................................................................................................................................................438
48.7 L2V/5/BGPVC_W2P...............................................................................................................................................440
48.8 L2V/3/CEOUTOFRANGE......................................................................................................................................444
48.9 L2V/3/CONFLICTCONN........................................................................................................................................444
48.10 L2V/4/ISSU_CHK_FL...........................................................................................................................................445
48.11 L2V/3/LDP_MSG_ERR.........................................................................................................................................446
48.12 L2V/3/OTHERCEIDSAME...................................................................................................................................447
48.13 L2V/3/PAFLCSERR..............................................................................................................................................448
48.14 L2V/5/PWE3VC_BACKUP..................................................................................................................................448
48.15 L2V/5/PWE3VC_DWN_ME.................................................................................................................................449
48.16 L2V/5/PWE3VC_P2W...........................................................................................................................................452
48.17 L2V/5/PWE3VC_UP_ME......................................................................................................................................455
48.18 L2V/5/PWE3VC_W2P...........................................................................................................................................458
48.19 L2V/3/PWLOOPDETECT.....................................................................................................................................461
48.20 L2V/5/SVC_DWN.................................................................................................................................................462
48.21 L2V/5/SVC_UP......................................................................................................................................................464
48.22 L2V/5/VPLSVC_BACKUP...................................................................................................................................467
48.23 L2V/5/VPLSVC_DWN_ME..................................................................................................................................468
48.24 L2V/5/VPLSVC_UP_ME......................................................................................................................................471
48.25 L2V/5/VPLSVSI_DWN.........................................................................................................................................474
48.26 L2V/5/VPLSVSI_UP.............................................................................................................................................477
48.27 L2V/5/VSICALINLBLERR...................................................................................................................................480
48.28 L2V/5/VSIMHMPREFSAME................................................................................................................................481
48.29 L2V/5/VSIRMTLCLIDSAME...............................................................................................................................482
48.30 L2V/5/VSISITEOUTOFRANGE...........................................................................................................................482
49 L3AD..........................................................................................................................................484
49.1 L3AD/4/RESOURCE_FULL...................................................................................................................................485
50 L3VPN........................................................................................................................................486
50.1 L3VPN/3/L3V_STATICLABEL_FAIL..................................................................................................................487
50.2 L3VPN/6/L3V_UNDOFRRNO...............................................................................................................................487
50.3 L3VPN/6/L3V_UNDOFRRTIMEOUT...................................................................................................................488
50.4 L3VPN/6/L3V_UNDOFRRYES..............................................................................................................................489
50.5 L3VPN/4/PREFIX_MAX_CLEARED....................................................................................................................489
50.6 L3VPN/4/PREFIX_MAX_EXCEEDED.................................................................................................................490
50.7 L3VPN/4/PREFIX_MID_EXCEEDED...................................................................................................................491
50.8 L3VPN/4/ROUTE_MAX_CLEARED....................................................................................................................492
Issue 07 (2014-07-30)

xx

Log Reference
Contents
50.9 L3VPN/4/ROUTE_MAX_EXCEEDED..................................................................................................................493
50.10 L3VPN/4/ROUTE_MID_EXCEEDED.................................................................................................................494
51 LACP..........................................................................................................................................496
51.1 LACP/4/LACP_SND_PDU_IO_FAIL....................................................................................................................497
51.2 LACP/4/PORT_SND_PDU_FAIL...........................................................................................................................497
51.3 LACP/6/TMR_NTT_TX..........................................................................................................................................498
52 LDP.............................................................................................................................................499
52.1 LDP/6/DATASMTHBEGAN..................................................................................................................................501
52.2 LDP/4/FAILALLOCTOKEN...................................................................................................................................501
52.3 LDP/4/FAILEXITMUL............................................................................................................................................502
52.4 LDP/4/FAILJOINMUL............................................................................................................................................503
52.5 LDP/4/FAILSENDMSG..........................................................................................................................................503
52.6 LDP/6/GRCRTFORWDTMR..................................................................................................................................504
52.7 LDP/6/GREND.........................................................................................................................................................504
52.8 LDP/4/HOLDTMREXP...........................................................................................................................................505
52.9 LDP/4/IFJIONFAIL.................................................................................................................................................506
52.10 LDP/4/IFJIONSUCC..............................................................................................................................................506
52.11 LDP/4/IMPMSGLISTEXCEED............................................................................................................................507
52.12 LDP/4/INSTAIDINVALID....................................................................................................................................508
52.13 LDP/4/JIONRETRYFAIL......................................................................................................................................508
52.14 LDP/6/NOENABLELDP.......................................................................................................................................509
52.15 LDP/6/NOTIGRSTART.........................................................................................................................................509
52.16 LDP/4/OPENRETRYTMR....................................................................................................................................510
52.17 LDP/6/PEERCLS...................................................................................................................................................511
52.18 LDP/6/PEERRESTART.........................................................................................................................................511
52.19 LDP/6/RCVFTMSG...............................................................................................................................................512
52.20 LDP/6/RMGREND................................................................................................................................................513
52.21 LDP/4/SAMADDRESS..........................................................................................................................................513
52.22 LDP/6/SMTHCOMPL............................................................................................................................................514
52.23 LDP/6/SMTHREJIONMUL...................................................................................................................................514
52.24 LDP/6/SRVREFUSE..............................................................................................................................................515
52.25 LDP/4/SSNHOLDTMREXP..................................................................................................................................515
52.26 LDP/6/SYSGRBEGIN...........................................................................................................................................516
52.27 LDP/6/SYSGREND...............................................................................................................................................517
52.28 LDP/6/SYSGRNOENABLEMPLS........................................................................................................................517
52.29 LDP/6/SYSGRNOLDPGR.....................................................................................................................................518
52.30 LDP/6/WAITPEERGR...........................................................................................................................................518
53 LINE...........................................................................................................................................520
53.1 LINE/3/AUTO_EXEC.............................................................................................................................................521
53.2 LINE/3/CLR_ONELINE..........................................................................................................................................521
Issue 07 (2014-07-30)

xxi

Log Reference
Contents
53.3 LINE/3/NO_EXEC...................................................................................................................................................522
53.4 LINE/3/SND_ALL...................................................................................................................................................523
53.5 LINE/3/SND_ONE...................................................................................................................................................523
53.6 LINE/5/UNLOCK....................................................................................................................................................524
53.7 LINE/4/UNLOCK_FAIL.........................................................................................................................................525
54 LLDP..........................................................................................................................................527
54.1 LLDP/4/BAD_PACKET..........................................................................................................................................528
54.2 LLDP/4/CREATEPORTFAIL.................................................................................................................................529
54.3 LLDP/4/DESTINATIONSLOTNOTUP..................................................................................................................530
54.4 LLDP/4/GLOBALENABLEFAIL...........................................................................................................................530
54.5 LLDP/4/PORTDISABLEFAIL................................................................................................................................531
54.6 LLDP/4/PORTENABLEFAIL.................................................................................................................................531
54.7 LLDP/4/SENDIPCFAIL..........................................................................................................................................532
54.8 LLDP/4/SENDRPCFAIL.........................................................................................................................................533
54.9 LLDP/4/TOOMANYNEIGHBORS.........................................................................................................................533
55 LOAD.........................................................................................................................................535
55.1 LOAD/6/CLIENTLEFT...........................................................................................................................................536
55.2 LOAD/6/SLOTJOINED...........................................................................................................................................536
55.3 LOAD/6/SLOTLEFT...............................................................................................................................................537
56 LSPM..........................................................................................................................................539
56.1 LSPM/6/BFD_AGE..................................................................................................................................................541
56.2 LSPM/6/BFD_FULL_CREATING..........................................................................................................................541
56.3 LSPM/3/BFD_LDP_UNABLE_INIT......................................................................................................................542
56.4 LSPM/6/DSTEMODESWITCH..............................................................................................................................542
56.5 LSPM/3/FAIL_CREATE_STALE_IF.....................................................................................................................543
56.6 LSPM/3/FAIL_DELETE_STALE_IF......................................................................................................................543
56.7 LSPM/6/FLOODFORTECLASSEVT.....................................................................................................................544
56.8 LSPM/6/GLOBALMPLSTEENABLE....................................................................................................................545
56.9 LSPM/6/GR_END_TIME........................................................................................................................................545
56.10 LSPM/6/GR_START_TIME..................................................................................................................................546
56.11 LSPM/6/GRAGINGBEGIN...................................................................................................................................546
56.12 LSPM/6/GRAGINGEND.......................................................................................................................................547
56.13 LSPM/3/GRAGINGFAIL......................................................................................................................................547
56.14 LSPM/3/GTSMMSGSENDFAIL..........................................................................................................................548
56.15 LSPM/6/HASMOOTHBEGIN...............................................................................................................................549
56.16 LSPM/6/HASMOOTHEND...................................................................................................................................549
56.17 LSPM/3/HASMOOTHFAIL..................................................................................................................................550
56.18 LSPM/3/LSPMTEST..............................................................................................................................................551
56.19 LSPM/6/NOTIFYCSPFDSTEEVT........................................................................................................................552
56.20 LSPM/6/NOTIFYLSPMDSTEEVT.......................................................................................................................552
Issue 07 (2014-07-30)

xxii

Log Reference
Contents
56.21 LSPM/6/NOTIFYRSVPDSTEEVT.......................................................................................................................553
56.22 LSPM/6/PREEMPTIONRESULT.........................................................................................................................553
56.23 LSPM/3/PROCESSTNLMSGFAILED..................................................................................................................554
56.24 LSPM/6/RECEIVEGRENDEVENT......................................................................................................................555
56.25 LSPM/6/SENTBATCHBKUPOVERHA...............................................................................................................555
56.26 LSPM/6/SENTSMOOTHFINISHHA....................................................................................................................556
56.27 LSPM/6/SLOTPLUGINOUTEVENT....................................................................................................................556
56.28 LSPM/4/SWITCH_TO_PT_FAIL.........................................................................................................................557
56.29 LSPM/4/SWITCH_TO_PTUNN............................................................................................................................558
56.30 LSPM/4/SWITCH_TO_WT_FAIL........................................................................................................................558
56.31 LSPM/4/SWITCH_TO_WTUNN..........................................................................................................................559
56.32 LSPM/4/TRAPSUPPRESS....................................................................................................................................559
56.33 LSPM/6/TRIGGERRSVPCOUNT........................................................................................................................560
56.34 LSPM/3/TRIGGERRSVPFAIL.............................................................................................................................561
56.35 LSPM/6/TWOLABELFORSAMEFEC.................................................................................................................562
57 MCAST......................................................................................................................................563
57.1 MCAST/3/ENTRY...................................................................................................................................................564
57.2 MCAST/6/FIB..........................................................................................................................................................564
57.3 MCAST/3/PORT......................................................................................................................................................565
57.4 MCAST/6/SUPPRESS_LEAVE..............................................................................................................................566
57.5 MCAST/6/SUPPRESS_REPORT............................................................................................................................567
57.6 MCAST/6/WRITE_QUEUE....................................................................................................................................568
58 MFIB...........................................................................................................................................569
58.1 MFIB/4/CNT_OVER_MAX....................................................................................................................................570
58.2 MFIB/4/DOWNNUM_EXCEED_RESTORE.........................................................................................................570
58.3 MFIB/4/ENTRY_EXCEED_RESTORE.................................................................................................................571
58.4 MFIB/4/ENTRY_OVER_MAX...............................................................................................................................572
58.5 MFIB/4/FREE_MID_TO_MAX..............................................................................................................................572
58.6 MFIB/4/GR_END....................................................................................................................................................573
58.7 MFIB/4/GR_START................................................................................................................................................574
58.8 MFIB/4/INVALID_OIF_NUM................................................................................................................................575
58.9 MFIB/4/REACH_TO_MAX....................................................................................................................................576
58.10 MFIB/4/REACH_TO_MAX_ENTRY_IO............................................................................................................576
58.11 MFIB/4/REACH_TO_MAX_ENTRY_MAIN......................................................................................................577
58.12 MFIB/4/REACH_TO_MAX_LIMIT.....................................................................................................................578
58.13 MFIB/4/SET_LMT_LESS_CRRNT......................................................................................................................579
59 MLD...........................................................................................................................................581
59.1 MLD/6/ERR_VER_PKT1........................................................................................................................................582
59.2 MLD/6/ERR_VER_PKT2........................................................................................................................................582
59.3 MLD/6/GLB_ENTRY..............................................................................................................................................583
Issue 07 (2014-07-30)

xxiii

Log Reference
Contents
59.4 MLD/6/GLB_LIMIT................................................................................................................................................584
59.5 MLD/6/IF_ENTRY..................................................................................................................................................584
59.6 MLD/6/IF_LIMIT....................................................................................................................................................585
59.7 MLD/6/INST_ENTRY.............................................................................................................................................586
59.8 MLD/6/INST_LIMIT...............................................................................................................................................587
59.9 MLD/4/REG_ACL_F...............................................................................................................................................587
59.10 MLD/4/SET_MLD_INTPLC_FAIL......................................................................................................................588
60 MPLS..........................................................................................................................................590
60.1 MPLS/5/VSI_ADD_DENYACL.............................................................................................................................591
60.2 MPLS/5/VSI_ADD_MCTBL...................................................................................................................................591
60.3 MPLS/5/VSI_ADD_VFP.........................................................................................................................................592
60.4 MPLS/5/VSI_ADD_VPTBL....................................................................................................................................592
60.5 MPLS/5/VSI_GET_MCIDX....................................................................................................................................593
61 MRM..........................................................................................................................................594
61.1 MRM/3/BACKUPSOCKET_E................................................................................................................................595
61.2 MRM/3/BATCHSOCKET_E...................................................................................................................................596
61.3 MRM/3/CHECKSOCKET_E...................................................................................................................................597
61.4 MRM/6/DOWNNUM_EXCEED_LIMIT................................................................................................................598
61.5 MRM/3/GETSOCKET_E........................................................................................................................................599
61.6 MRM/3/MIGP_NOTEXIST_FAIL..........................................................................................................................600
61.7 MRM/3/SEARCH_MIGP_FAIL..............................................................................................................................600
61.8 MRM/2/VLINKID_CHG.........................................................................................................................................601
61.9 MRM/6/VRFLIST_LIMIT.......................................................................................................................................602
62 MSDP.........................................................................................................................................604
62.1 MSDP/4/CHECK_SOCKET_FAIL.........................................................................................................................605
62.2 MSDP/6/PEER_NTFDWN......................................................................................................................................606
62.3 MSDP/6/PEER_TIMEOUT.....................................................................................................................................606
62.4 MSDP/6/PEER_UP..................................................................................................................................................607
62.5 MSDP/4/SA_LIMIT.................................................................................................................................................608
62.6 MSDP/4/SET_MSDP_GLBPLC_FAIL...................................................................................................................609
62.7 MSDP/4/SET_MSDP_GWLIST_FAIL...................................................................................................................609
63 MSTP..........................................................................................................................................611
63.1 MSTP_ADP/5/ADD_BINDVLAN..........................................................................................................................612
63.2 MSTP/4/BPDU_PROTECTION..............................................................................................................................612
63.3 MSTP/Notice/DELETE_BINDVLAN.....................................................................................................................613
63.4 MSTP/4/EDGE_PORT.............................................................................................................................................613
63.5 MSTP/4/LOOPBACK_DETECTED.......................................................................................................................614
63.6 MSTP/4/LOOP_GUARD.........................................................................................................................................615
63.7 MSTP/3/PACKET_ERR_COMPLIAN...................................................................................................................615
63.8 MSTP/6/PORT_INIT...............................................................................................................................................616
Issue 07 (2014-07-30)

xxiv

Log Reference
Contents
63.9 MSTP/6/RECEIVE_MSTITC..................................................................................................................................617
63.10 MSTP/5/ROOT_LOST...........................................................................................................................................618
63.11 MSTP/6/SET_PORT_DISCARDING....................................................................................................................618
63.12 MSTP/6/SET_PORT_FORWARDING.................................................................................................................619
63.13 MSTP/Notice/SET_PORT_INSTANCE................................................................................................................620
63.14 MSTP/6/SET_PORT_LEARNING........................................................................................................................620
63.15 MSTP/Notice/SET_PORT_STATE.......................................................................................................................621
63.16 MSTP/4/SET_CANCEL........................................................................................................................................622
63.17 MSTP/6/SET_PORT_DISABLE...........................................................................................................................622
64 NAP............................................................................................................................................624
64.1 NAP/6/NAP_GOTONEIGHBOR............................................................................................................................625
64.2 NAP/5/NAP_LINK_TIMEOUT..............................................................................................................................625
64.3 NAP/4/NAP_LOGIN................................................................................................................................................626
65 NATPT.......................................................................................................................................627
65.1 NATPT/4/ACLPRE_UNKNOWN_MAP................................................................................................................629
65.2 NATPT/4/ADD_ENABLELIST_FAIL...................................................................................................................629
65.3 NATPT/3/ADDRMAP_MEMFAIL.........................................................................................................................630
65.4 NATPT/4/ADDRMAP_RECHMAX.......................................................................................................................630
65.5 NATPT/4/ALLOC_NATPT_IOFAIL......................................................................................................................631
65.6 NATPT/4/AM_NO_FOUND...................................................................................................................................631
65.7 NATPT/4/CFGPRE_UNKNOWN_MAP................................................................................................................632
65.8 NATPT/4/CFGV4_UNKNOWN_MAP...................................................................................................................633
65.9 NATPT/4/CFGV6_UNKNOWN_MAP...................................................................................................................633
65.10 NATPT/4/CONTR_ADDR_EXHAUST................................................................................................................634
65.11 NATPT/4/DEL_ENABLELIST_FAIL..................................................................................................................634
65.12 NATPT/4/DELV4_UNKNOWN_MAP.................................................................................................................635
65.13 NATPT/4/DELV6_UNKNOWN_MAP.................................................................................................................635
65.14 NATPT/4/DISTR_ADDR_EXHAUST..................................................................................................................636
65.15 NATPT/4/DOWN_AAM_DATA_FAIL...............................................................................................................637
65.16 NATPT/4/DOWN_AM_DATA_FAIL..................................................................................................................637
65.17 NATPT/4/DOWN_ENABLELIST_FAIL..............................................................................................................638
65.18 NATPT/4/DOWN_TRATOS_FAIL......................................................................................................................638
65.19 NATPT/3/DPATMAP_MEMFAIL........................................................................................................................639
65.20 NATPT/4/DPATMAP_RECHMAX......................................................................................................................640
65.21 NATPT/4/FRAGMENT_DESTROY.....................................................................................................................640
65.22 NATPT/4/INDEX_HAS_INLIST..........................................................................................................................641
65.23 NATPT/4/INVALID_CMD...................................................................................................................................641
65.24 NATPT/4/INVALID_IF_IOENABLE...................................................................................................................642
65.25 NATPT/4/INVALIDIF_IOUNE............................................................................................................................642
65.26 NATPT/4/INVALIDIFNET_DEL.........................................................................................................................643
65.27 NATPT/3/MALLOFAIL_BKUP...........................................................................................................................644
Issue 07 (2014-07-30)

xxv

Log Reference
Contents
65.28 NATPT/4/MALLOFAIL_ENABLE......................................................................................................................644
65.29 NATPT/6/MAP_INCOMPLETE_DMAP..............................................................................................................645
65.30 NATPT/4/MAX_FRAG_REACH..........................................................................................................................645
65.31 NATPT/4/MAX_SESSION_REACH....................................................................................................................646
65.32 NATPT/4/NATPT_HAS_ENABLE......................................................................................................................646
65.33 NATPT/6/NATPT_NOTENABLE........................................................................................................................647
65.34 NATPT/4/RECURSION_IP4_PKT.......................................................................................................................648
65.35 NATPT/4/RECURSION_IP6_PKT.......................................................................................................................648
65.36 NATPT/4/SYSN_MULTI_FAIL...........................................................................................................................649
66 NETSTREAM...........................................................................................................................650
66.1 NETSTREAM/3/DEL_IPV6ENTRY_FAIL............................................................................................................651
67 NQA...........................................................................................................................................652
67.1 NQA/4/FALLING_ALARM....................................................................................................................................653
67.2 NQA/4/RISING_ALARM........................................................................................................................................653
68 NSADP......................................................................................................................................655
68.1 NSADP/4/NS_ID_RPCFAIL...................................................................................................................................656
69 NTP.............................................................................................................................................657
69.1 NTP/4/GRADUAL_SET_TIME..............................................................................................................................658
69.2 NTP/4/LEAP_CHANGE..........................................................................................................................................658
69.3 NTP/4/PEER_MAX_ASSOC..................................................................................................................................659
69.4 NTP/4/PEER_SELE.................................................................................................................................................659
69.5 NTP/4/REFCLK_EVENTS......................................................................................................................................660
69.6 NTP/4/SOURCE_LOST...........................................................................................................................................661
69.7 NTP/4/STEP_GET_TIME........................................................................................................................................663
69.8 NTP/4/STEP_SET_TIME........................................................................................................................................664
69.9 NTP/4/STRATUM_CHANGE.................................................................................................................................664
69.10 NTP/4/TIMER_INIT..............................................................................................................................................665
70 OAM...........................................................................................................................................666
70.1 OAM/4/BOARD_OUT_TUNN...............................................................................................................................668
70.2 OAM/4/LSP_EN_AVA............................................................................................................................................668
70.3 OAM/3/LSP_EN_DEF.............................................................................................................................................669
70.4 OAM/3/LSP_EN_UNAVA......................................................................................................................................669
70.5 OAM/4/LSP_QUIT_DEF.........................................................................................................................................670
70.6 OAM/4/LSP_START_DET.....................................................................................................................................671
70.7 OAM/4/LSP_STOP_DET........................................................................................................................................671
70.8 OAM/5/NOTIFY_SMOOTH...................................................................................................................................672
70.9 OAM/3/PDT_DELETE............................................................................................................................................672
70.10 OAM/3/PDT_FAIL_ADD......................................................................................................................................673
70.11 OAM/3/PDT_GET_DETECT_INFO.....................................................................................................................674
Issue 07 (2014-07-30)

xxvi

Log Reference
Contents
70.12 OAM/3/PDT_SLT..................................................................................................................................................674
70.13 OAM/3/PDTMSG_ERR.........................................................................................................................................675
70.14 OAM/4/SLSP_EN_AVA........................................................................................................................................675
70.15 OAM/3/SLSP_EN_DEF.........................................................................................................................................676
70.16 OAM/3/SLSP_EN_UNAVA..................................................................................................................................677
70.17 OAM/4/SLSP_QUIT_DEF....................................................................................................................................677
70.18 OAM/4/SLSP_START_DET.................................................................................................................................678
70.19 OAM/4/SLSP_STOP_DET....................................................................................................................................678
70.20 OAM/4/TUN_EN_AVA........................................................................................................................................679
70.21 OAM/3/TUN_EN_DEF..........................................................................................................................................679
70.22 OAM/3/TUN_EN_UNAVA...................................................................................................................................680
70.23 OAM/4/TUN_QUIT_DEF.....................................................................................................................................681
70.24 OAM/4/TUN_START_DET..................................................................................................................................681
70.25 OAM/4/TUN_STOP_DET.....................................................................................................................................682
70.26 OAM/3/UPDATA_PDT_FAIL..............................................................................................................................682
71 OSPF...........................................................................................................................................684
71.1 OSPF/6/ADD_NBR_PRLIST_VLINK....................................................................................................................689
71.2 OSPF/4/ALL_NBR_FULL_EXIT...........................................................................................................................689
71.3 OSPF/4/AUTO_CHG_RTRID.................................................................................................................................690
71.4 OSPF/6/BACKUP_AFTER_CFM...........................................................................................................................691
71.5 OSPF/6/BACKUP_BEFORE_CFM........................................................................................................................691
71.6 OSPF/6/BACKUP_LENGTH_ERR........................................................................................................................692
71.7 OSPF/6/BACKUP_TYPE_ERR..............................................................................................................................692
71.8 OSPF/6/BAD_IP_PACKET.....................................................................................................................................693
71.9 OSPF/6/BAD_LSA..................................................................................................................................................694
71.10 OSPF/6/BAD_OSPF_PACKET.............................................................................................................................695
71.11 OSPF/4/CHG_LSA_HELPER_FAIL....................................................................................................................696
71.12 OSPF/4/CONFLICT_IP_ADDRESS.....................................................................................................................697
71.13 OSPF/6/CONFLICT_ROUTERID_INTER...........................................................................................................698
71.14 OSPF/4/CONFLICT_ROUTERID_INTF..............................................................................................................698
71.15 OSPF/4/CONFLICT_ROUTERID_INTRA..........................................................................................................699
71.16 OSPF/6/DEL_NBR_PRLIST.................................................................................................................................700
71.17 OSPF/6/DEL_NBR_PRLIST_VLINK...................................................................................................................701
71.18 OSPF/3/DR_ELECT_FAILED..............................................................................................................................701
71.19 OSPF/3/END_GR_NODE_IN_LIST.....................................................................................................................702
71.20 OSPF/4/ENTER_HELPER_MODE.......................................................................................................................703
71.21 OSPF/6/FIND_NBR_SHAMLINK........................................................................................................................703
71.22 OSPF/6/FINISH_ADD_ASE.................................................................................................................................704
71.23 OSPF/6/FINISH_ADD_NSSA...............................................................................................................................704
71.24 OSPF/6/FLSH_STL_AS_LSA...............................................................................................................................705
71.25 OSPF/6/FLUSH_STAL_AREA_LSA...................................................................................................................706
Issue 07 (2014-07-30)

xxvii

Log Reference
Contents
71.26 OSPF/6/GR_ADD_NBR_PRLIST.........................................................................................................................706
71.27 OSPF/4/GR_END_SUCCESS...............................................................................................................................707
71.28 OSPF/3/GR_EXIT_GR_UNSU.............................................................................................................................708
71.29 OSPF/4/GR_EXIT_HLP_SU.................................................................................................................................708
71.30 OSPF/4/GR_HLP_TIMER_FIRED.......................................................................................................................709
71.31 OSPF/3/GR_IF_CHANGE.....................................................................................................................................709
71.32 OSPF/4/GR_NOTIFYRM_EXIT_GR...................................................................................................................710
71.33 OSPF/4/GR_RECV_1WAY_HELLO....................................................................................................................710
71.34 OSPF/4/GR_START_GR.......................................................................................................................................711
71.35 OSPF/4/HLP_EXIT_RECV_LSA..........................................................................................................................712
71.36 OSPF/6/IF_CHG_E................................................................................................................................................712
71.37 OSPF/6/IF_TYPE_CHG........................................................................................................................................713
71.38 OSPF/3/INTF_EXIT_HLP_FAIL..........................................................................................................................714
71.39 OSPF/6/INTF_NSR_EVENT.................................................................................................................................714
71.40 OSPF/4/INTF_NSR_OVERTIME_LIMIT............................................................................................................715
71.41 OSPF/6/ISSU_SMB_CMD_ERR..........................................................................................................................716
71.42 OSPF/3/ISSU_SMOOTH_ACROSS.....................................................................................................................717
71.43 OSPF/3/ISSU_SMOOTH_INSIDE........................................................................................................................717
71.44 OSPF/3/ISSU_SMOOTH_OVER..........................................................................................................................718
71.45 OSPF/6/JOIN_MULGRP_FAIL............................................................................................................................719
71.46 OSPF/6/LDP_INIT_EVENT..................................................................................................................................719
71.47 OSPF/6/LDP_SYNC_CREA..................................................................................................................................720
71.48 OSPF/6/LDP_SYNC_EVENT...............................................................................................................................720
71.49 OSPF/6/LDP_SYNC_FIRE....................................................................................................................................721
71.50 OSPF/6/LEAVE_MULGRP_FAIL........................................................................................................................722
71.51 OSPF/5/LSA_CHANGE_FREQUENT.................................................................................................................722
71.52 OSPF/3/MISMATCH_HELPER_FAIL.................................................................................................................723
71.53 OSPF/4/NBR_CHANGE_E...................................................................................................................................724
71.54 OSPF/3/NBR_CHG_DOWN.................................................................................................................................725
71.55 OSPF/3/NBR_DOWN_REASON..........................................................................................................................726
71.56 OSPF/4/NBR_STATE_HELPER_F......................................................................................................................726
71.57 OSPF/6/NOTIFY_DEL_FINISHED......................................................................................................................727
71.58 OSPF/4/NOTIFYRM_ENTER_GR.......................................................................................................................728
71.59 OSPF/6/NSR_AMB_BAKOVER_INFO...............................................................................................................728
71.60 OSPF/6/NSR_AMB_BCHOVER_INFO...............................................................................................................729
71.61 OSPF/6/NSR_AMB_ENWARM_INFO................................................................................................................729
71.62 OSPF/6/NSR_AMB_EXWARM_INFO................................................................................................................730
71.63 OSPF/6/NSR_AMB_GROVER_INFO..................................................................................................................730
71.64 OSPF/6/NSR_AMB_RM_INFO............................................................................................................................731
71.65 OSPF/6/NSR_AMB_RMCHK_INFO....................................................................................................................732
71.66 OSPF/6/NSR_AREARECV_DATA......................................................................................................................732
Issue 07 (2014-07-30)

xxviii

Log Reference
Contents
71.67 OSPF/6/NSR_AREARECV_INFO........................................................................................................................733
71.68 OSPF/6/NSR_AREARESET_INFO......................................................................................................................733
71.69 OSPF/6/NSR_PROCRECV_DATA......................................................................................................................734
71.70 OSPF/6/NSR_PROCRECV_INFO........................................................................................................................735
71.71 OSPF/6/NSR_PROCRESET_INFO.......................................................................................................................735
71.72 OSPF/6/NSR_SMB_BATCH_INFO.....................................................................................................................736
71.73 OSPF/6/NSR_SMB_GLOBAL_INFO...................................................................................................................736
71.74 OSPF/6/NSSA_STATE_ELECT...........................................................................................................................737
71.75 OSPF/6/ONE_IF_EXIT_WAITING......................................................................................................................738
71.76 OSPF/4/ONEIF_ENTER_WAITING....................................................................................................................738
71.77 OSPF/3/PAF_TYPE_LOSS_ISSU.........................................................................................................................739
71.78 OSPF/4/PLCY_FAIL_HELPER_F........................................................................................................................740
71.79 OSPF/6/RCV_MEM_RESTORE...........................................................................................................................740
71.80 OSPF/6/RCV_RM_EVNT.....................................................................................................................................741
71.81 OSPF/4/RECV_DIFF_GRACE_LSA....................................................................................................................741
71.82 OSPF/4/RECV_FIRST_GLSA..............................................................................................................................742
71.83 OSPF/6/RECV_ROUT_LIMIT_MSG...................................................................................................................743
71.84 OSPF/6/RECV_SMB_DOWN_RM.......................................................................................................................743
71.85 OSPF/6/RECV_SMOOTH_OVER_RM................................................................................................................744
71.86 OSPF/6/RECV_SWITCH_RM..............................................................................................................................744
71.87 OSPF/6/RECV_SYNC_ACROSS_RM.................................................................................................................745
71.88 OSPF/3/RECV_TWO_GRACELSA......................................................................................................................746
71.89 OSPF/6/RESET_SCHEDULE...............................................................................................................................746
71.90 OSPF/6/RESTORE_AFTER_CFM........................................................................................................................747
71.91 OSPF/6/RESTORE_BEFORE_CFM.....................................................................................................................747
71.92 OSPF/6/RM_GETROUTERID..............................................................................................................................748
71.93 OSPF/6/RM_IM.....................................................................................................................................................749
71.94 OSPF/4/RST_NBR_IN_PTIAL_GR......................................................................................................................749
71.95 OSPF/4/RTRLSA_BACKLINK_FAIL..................................................................................................................750
71.96 OSPF/6/SHAMLINK_IF_CHG_E.........................................................................................................................751
71.97 OSPF/4/SHAMLINK_NBR_CHG_E....................................................................................................................751
71.98 OSPF/3/SHAMLINK_NBR_DOWN.....................................................................................................................752
71.99 OSPF/6/SINTF_NSR_EVENT..............................................................................................................................753
71.100 OSPF/4/SINTF_NSR_OVERTIME_LIMIT........................................................................................................754
71.101 OSPF/6/SMB_GETSESSION_ERR....................................................................................................................755
71.102 OSPF/6/SMB_NSR_AREA_INFO......................................................................................................................755
71.103 OSPF/6/SMB_NSR_PROC_INFO......................................................................................................................756
71.104 OSPF/6/STUB_RT_EX_UD_STUB....................................................................................................................757
71.105 OSPF/6/STUB_RT_ONBT_TM_CRT................................................................................................................757
71.106 OSPF/6/STUB_RT_STUB_ALW........................................................................................................................758
71.107 OSPF/6/STUB_RT_TM_FIRE............................................................................................................................758
Issue 07 (2014-07-30)

xxix

Log Reference
Contents
71.108 OSPF/6/TRAP_AGE_LSA..................................................................................................................................759
71.109 OSPF/6/TRAP_HELPER_CHG...........................................................................................................................760
71.110 OSPF/4/TRAP_INTF_AUTH_FAIL...................................................................................................................761
71.111 OSPF/6/TRAP_INTF_BAD_RX.........................................................................................................................761
71.112 OSPF/4/TRAP_INTF_CFG_ERR........................................................................................................................762
71.113 OSPF/6/TRAP_INTF_CHG.................................................................................................................................763
71.114 OSPF/6/TRAP_INTF_RETX...............................................................................................................................764
71.115 OSPF/6/TRAP_LSDB_APP_OFLOW................................................................................................................765
71.116 OSPF/6/TRAP_LSDB_OVERFLOW..................................................................................................................765
71.117 OSPF/6/TRAP_NBR_CHG..................................................................................................................................766
71.118 OSPF/6/TRAP_NSSA_TRANS_CHG................................................................................................................767
71.119 OSPF/6/TRAP_ORG_LSA..................................................................................................................................767
71.120 OSPF/6/TRAP_RESTART_CHG........................................................................................................................768
71.121 OSPF/4/TRAP_VIF_AUTH_FAIL......................................................................................................................769
71.122 OSPF/4/TRAP_VIF_CFG_ERR..........................................................................................................................770
71.123 OSPF/6/TRAP_VIF_RX_BAD............................................................................................................................770
71.124 OSPF/6/TRAP_VIR_HELPER_CHG..................................................................................................................771
71.125 OSPF/6/TRAP_VIR_INTF_CHG........................................................................................................................772
71.126 OSPF/6/TRAP_VIR_INTF_RETX......................................................................................................................773
71.127 OSPF/6/TRAP_VIR_NBR_CHG.........................................................................................................................773
71.128 OSPF/4/UPLAN_MATCH_HLPFAIL................................................................................................................774
71.129 OSPF/6/VINTF_NSR_EVENT............................................................................................................................775
71.130 OSPF/4/VINTF_NSR_OVERTIME_LIMIT.......................................................................................................776
71.131 OSPF/6/VLINK_IF_CHG_E................................................................................................................................777
71.132 OSPF/3/VLINK_NBR_CHG_DOWN.................................................................................................................777
71.133 OSPF/4/VLINK_NBR_CHG_E...........................................................................................................................778
72 OSPFV3......................................................................................................................................780
72.1 OSPFV3/6/BFD_RM_EVNT...................................................................................................................................781
72.2 OSPFV3/6/BFD_SESSION_NTFY.........................................................................................................................781
72.3 OSPFV3/3/GRBCKLNKERR..................................................................................................................................782
72.4 OSPFV3/3/GRFLLALLNBRERR...........................................................................................................................783
72.5 OSPFV3/3/GRINTFDWNERR................................................................................................................................783
72.6 OSPFV3/6/GRNOHLPCNFG..................................................................................................................................784
72.7 OSPFV3/3/GRNORMALRSTERR..........................................................................................................................785
72.8 OSPFV3/6/GRNOTENBL.......................................................................................................................................785
72.9 OSPFV3/3/GRPRDEXPERR...................................................................................................................................786
72.10 OSPFV3/3/GRPROCDELERR..............................................................................................................................786
72.11 OSPFV3/3/GRSLFORGNTWKMSSERR.............................................................................................................787
72.12 OSPFV3/4/HELLO_DELAY.................................................................................................................................788
72.13 OSPFV3/6/IFSMCHG............................................................................................................................................788
72.14 OSPFV3/4/MAXEXTROUTESLIMIT..................................................................................................................789
Issue 07 (2014-07-30)

xxx

Log Reference
Contents
72.15 OSPFV3/4/MEMSHORT.......................................................................................................................................790
72.16 OSPFV3/6/NFSMCHG..........................................................................................................................................790
72.17 OSPFV3/4/PROC_UP_FAIL_MEMSHT..............................................................................................................791
72.18 OSPFV3/6/PROCUNDRGR..................................................................................................................................791
72.19 OSPFV3/4/RMMEMRESTR.................................................................................................................................792
72.20 OSPFV3/4/RMMEMSHORT.................................................................................................................................793
73 PAF.............................................................................................................................................794
73.1 PAF/6/LCS_NOT_SAME........................................................................................................................................795
73.2 PAF/6/PAF_NOT_SAME........................................................................................................................................795
73.3 PAF/4/READLCSFAIL............................................................................................................................................796
73.4 PAF/4/READPAFFAIL............................................................................................................................................796
73.5 PAF/5/WRITE_LCS_FAIL......................................................................................................................................797
73.6 PAF/5/WRITE_PAF_FAIL......................................................................................................................................798
74 PATCH.......................................................................................................................................799
74.1 PATCH/6/READ_FILE_FAIL.................................................................................................................................800
75 PDF.............................................................................................................................................801
75.1 PDF/4/CLOSEPDFRFAIL.......................................................................................................................................802
75.2 PDF/4/CLOSEPDFWFAIL......................................................................................................................................802
75.3 PDF/4/DOPOPFAIL.................................................................................................................................................803
75.4 PDF/4/OPENPDFRFAIL.........................................................................................................................................803
75.5 PDF/4/OPENPDFWFAIL........................................................................................................................................804
75.6 PDF/4/READPDFFAIL............................................................................................................................................804
75.7 PDF/4/SEEKPDFRFAIL..........................................................................................................................................805
75.8 PDF/4/SEEKPDFWFAIL.........................................................................................................................................805
75.9 PDF/4/WRITEFAIL.................................................................................................................................................806
75.10 PDF/4/WRITEPDFFAIL........................................................................................................................................807
75.11 PDF/4/WRITEPDFNOSPACE..............................................................................................................................807
75.12 PDF/4/WRITESLAVEFAIL..................................................................................................................................808
76 PIM.............................................................................................................................................810
76.1 PIM/4/ASTPKT_GADD_ERR1..............................................................................................................................812
76.2 PIM/4/BACKUPJP_NORP......................................................................................................................................812
76.3 PIM/4/BSR_GRP_SCOPE_ERR.............................................................................................................................813
76.4 PIM/4/BSR_GRPLOC..............................................................................................................................................814
76.5 PIM/4/CRPADV_FAMERR....................................................................................................................................815
76.6 PIM/4/CRPADV_GRPERR.....................................................................................................................................815
76.7 PIM/4/CRPADV_GRPINV......................................................................................................................................816
76.8 PIM/4/CRT_SG_FAIL.............................................................................................................................................817
76.9 PIM/6/DISCA_PRIADDR.......................................................................................................................................818
76.10 PIM/4/FNDNBR_DNDB_F...................................................................................................................................818
76.11 PIM/5/GR_END.....................................................................................................................................................819
Issue 07 (2014-07-30)

xxxi

Log Reference
Contents
76.12 PIM/5/GR_START.................................................................................................................................................820
76.13 PIM/6/GRP_ADDR_IS_LOCAL...........................................................................................................................821
76.14 PIM/6/GRP_ADDR_NOT_MCAST......................................................................................................................822
76.15 PIM/6/GRP_MASK_UNSUPPORTED.................................................................................................................823
76.16 PIM/6/HELPKT_UNSADDR_ERR......................................................................................................................824
76.17 PIM/3/HOLDTIME_LESS_INL............................................................................................................................825
76.18 PIM/4/INT_INV.....................................................................................................................................................825
76.19 PIM/5/INVSRC......................................................................................................................................................826
76.20 PIM/4/JP_SRCERR................................................................................................................................................827
76.21 PIM/6/MTU_IF_SHT.............................................................................................................................................827
76.22 PIM/4/NBR_DOWN..............................................................................................................................................828
76.23 PIM/4/NBR_DOWN_ALL....................................................................................................................................829
76.24 PIM/4/NBR_UP......................................................................................................................................................830
76.25 PIM/4/PIMPKT_CHKSUM_ERR.........................................................................................................................831
76.26 PIM/4/PIM_GR_FORCE_SYNC...........................................................................................................................832
76.27 PIM/3/PUTNBR_DNDB_F....................................................................................................................................832
76.28 PIM/6/SEC_ADDRFA_ERR.................................................................................................................................833
76.29 PIM/3/SOCK_ERR1..............................................................................................................................................834
76.30 PIM/6/SRC_MASK_UNSUPPORTED.................................................................................................................834
77 POE.............................................................................................................................................836
77.1 POE/4/LEGACYPD.................................................................................................................................................837
77.2 POE/6/PDOVERCURRENT....................................................................................................................................837
77.3 POE/6/PDCONNECT..............................................................................................................................................838
77.4 POE/6/PDDISCONNECT........................................................................................................................................838
77.5 POE/6/PDPOWEROFF............................................................................................................................................839
77.6 POE/6/PDPOWERON..............................................................................................................................................840
77.7 POE/6/PORTERROR...............................................................................................................................................840
77.8 POE/6/PORTPDOVERLD.......................................................................................................................................841
77.9 POE/6/PORTPW......................................................................................................................................................841
77.10 POE/6/POWERFAIL..............................................................................................................................................842
77.11 POE/6/POWERSUCCESS.....................................................................................................................................842
77.12 POE/6/RESETPORT..............................................................................................................................................843
78 Portal..........................................................................................................................................844
78.1 WEB/4/PORTALSERVER_DOWN........................................................................................................................845
78.2 WEB/4/PORTALSERVER_UP...............................................................................................................................845
78.3 WEB/4/WEBSOCK..................................................................................................................................................846
79 QinQ...........................................................................................................................................847
79.1 QINQ/5/ISSUSPEC_CHECK..................................................................................................................................848
79.2 QINQ/5/ISSU_CHECK_ERR..................................................................................................................................848
79.3 QINQ/5/ISSU_CHECK_OK....................................................................................................................................849
Issue 07 (2014-07-30)

xxxii

Log Reference
Contents
80 RDS............................................................................................................................................851
80.1 RDS/4/RDACCTDOWN..........................................................................................................................................852
80.2 RDS/6/RDACCTUP.................................................................................................................................................852
80.3 RDS/4/RDAUTHDOWN.........................................................................................................................................853
80.4 RDS/6/RDAUTHUP................................................................................................................................................854
81 RIP..............................................................................................................................................855
81.1 RIP/3/ADD_RTE_F.................................................................................................................................................856
81.2 RIP/3/DEL_SAMEADDR_PEER_F........................................................................................................................856
81.3 RIP/6/FREEZE_ENTER..........................................................................................................................................857
81.4 RIP/6/FREEZE_RECOVER....................................................................................................................................858
81.5 RIP/6/GR_ABORT...................................................................................................................................................858
81.6 RIP/6/GR_ENTER...................................................................................................................................................859
81.7 RIP/6/GR_ENTER_HELPER..................................................................................................................................860
81.8 RIP/6/GR_EXIT.......................................................................................................................................................860
81.9 RIP/6/GR_EXIT_HELPER......................................................................................................................................861
81.10 RIP/6/GR_EXIT_RT_UPDT..................................................................................................................................862
81.11 RIP/3/GR_RCV_ABORT......................................................................................................................................862
81.12 RIP/6/GR_SND_ABORT.......................................................................................................................................863
81.13 RIP/6/GR_TOPO_CHANGE.................................................................................................................................864
81.14 RIP/3/MAX_LOGIF_REACH_F...........................................................................................................................864
81.15 RIP/6/MEMSHORT_ENTER................................................................................................................................865
81.16 RIP/6/MEMSHORT_RECOVER..........................................................................................................................866
81.17 RIP/6/RIP_NBR_ADD...........................................................................................................................................866
81.18 RIP/6/RIP_NBR_DEL............................................................................................................................................867
81.19 RIP/6/RCV_HA_SMOVER...................................................................................................................................868
82 RIPNG........................................................................................................................................869
82.1 RIPNG/6/FREEZE_ENTER....................................................................................................................................870
82.2 RIPNG/6/FREEZE_RECOVER...............................................................................................................................870
82.3 RIPNG/3/INVLD_IF_MTU_F.................................................................................................................................871
82.4 RIPNG/3/IPV6_DISAB_F.......................................................................................................................................871
82.5 RIPNG/6/ISSU_COMP............................................................................................................................................872
82.6 RIPNG/3/MAX_LOGIF_REACH_F.......................................................................................................................872
82.7 RIPNG/6/MEMSHORT_ENTER............................................................................................................................873
82.8 RIPNG/6/MEMSHORT_RECOVER.......................................................................................................................874
82.9 RIPNG/6/RIPNG_NBR_ADD.................................................................................................................................874
82.10 RIPNG/6/RIPNG_NBR_DEL................................................................................................................................875
82.11 RIPNG/3/NO_GLO_SITE_ADDR_F....................................................................................................................876
83 RM..............................................................................................................................................877
83.1 RM/3/ADDHOSTRT_TBL_LMT............................................................................................................................879
83.2 RM/6/CONFIRM_N.................................................................................................................................................879
Issue 07 (2014-07-30)

xxxiii

Log Reference
Contents
83.3 RM/6/CONFIRM_TIMEOUT..................................................................................................................................880
83.4 RM/6/CONFIRM_Y.................................................................................................................................................881
83.5 RM/6/ENABLE_1MFIB..........................................................................................................................................882
83.6 RM/3/GET_VRF_TBLID_FAL...............................................................................................................................883
83.7 RM/6/HANDLE_ADD_IPMSG..............................................................................................................................883
83.8 RM/6/HANDLE_ADDED_IPMSG.........................................................................................................................884
83.9 RM/6/HANDLE_DEL_IPMSG...............................................................................................................................885
83.10 RM/6/HANDLE_DELED_IPMSG........................................................................................................................885
83.11 RM/4/INST_RCH_MAX_RT_LMT......................................................................................................................886
83.12 RM/4/INST_RCH_MAX_RT6_LMT....................................................................................................................887
83.13 RM/4/INST_RCH_MAXPFXLMT........................................................................................................................888
83.14 RM/4/INST_RCH_MAXPFXLMT6......................................................................................................................889
83.15 RM/4/IPV4_DEFT_RT_CHG................................................................................................................................890
83.16 RM/4/IPV6_DEFT_RT_CHG................................................................................................................................891
83.17 RM/3/IPV6_RCH_MAX_PFX..............................................................................................................................892
83.18 RM/3/LDP_SESSION_STATE..............................................................................................................................893
83.19 RM/3/LMTNUM_BGER_MAXPAF.....................................................................................................................893
83.20 RM/3/MAX_RPM_RCH........................................................................................................................................894
83.21 RM/3/NEW_PFX_NO_FREE_IDX.......................................................................................................................895
83.22 RM/3/NO_FREE_IDX_FOR_PFX........................................................................................................................895
83.23 RM/3/NOTIFY_ISIS_MSG...................................................................................................................................896
83.24 RM/3/NOTIFY_OSPF_MSG.................................................................................................................................897
83.25 RM/4/PFX_MAX_NUM_CLEARED...................................................................................................................897
83.26 RM/4/PFX_MID_NUM_CLEARED.....................................................................................................................898
83.27 RM/4/PFXNUM_EXCD_WARN..........................................................................................................................899
83.28 RM/4/PFXNUM_EXCD_WARN6........................................................................................................................900
83.29 RM/3/PTCL_ADD_RT_MEM_SHT.....................................................................................................................901
83.30 RM/4/RCH_ALLVRF_RT_LMT..........................................................................................................................901
83.31 RM/4/RCH_ALLVRF6_RT_LMT........................................................................................................................902
83.32 RM/4/RCH_MIGP_RT_LMT................................................................................................................................903
83.33 RM/4/RCH_PUB_RT_LMT..................................................................................................................................903
83.34 RM/4/RCH_PUB6_RT_LMT................................................................................................................................904
83.35 RM/3/RPM_ROUT_MAX_LMT...........................................................................................................................905
83.36 RM/4/RT_NUM_EXCD_WARN..........................................................................................................................905
83.37 RM/4/RT6_NUM_EXCD_WARN........................................................................................................................906
83.38 RM/3/SMTH_ADDRT_MAX_LMT.....................................................................................................................908
83.39 RM/3/SNDMSG_MEM_SHORT_FAL.................................................................................................................908
83.40 RM/4/SYS_RCH_MAX_RT_LMT.......................................................................................................................909
83.41 RM/4/SYS_RCH_MAX6_RT_LMT.....................................................................................................................910
83.42 RM/4/URT_RCH_MAX_IPPRFX.........................................................................................................................910
84 RRPP..........................................................................................................................................912
Issue 07 (2014-07-30)

xxxiv

Log Reference
Contents
84.1 RRPP/3/FAIL...........................................................................................................................................................913
84.2 RRPP/4/INSERT......................................................................................................................................................913
84.3 RRPP/5/PBLK..........................................................................................................................................................914
84.4 RRPP/5/PFWD.........................................................................................................................................................914
84.5 RRPP/5/RESTORE..................................................................................................................................................915
84.6 RRPP/3/RRPPACLFULL........................................................................................................................................916
84.7 RRPP/4/SPECCHANGE..........................................................................................................................................916
84.8 RRPP/4/SPECCHECKFAIL....................................................................................................................................917
84.9 RRPP/5/TOPOCHANGE.........................................................................................................................................918
85 RSA.............................................................................................................................................920
85.1 RSA/6/DESTROY_KEYS.......................................................................................................................................922
85.2 RSA/4/FAIL_READ_FLASH..................................................................................................................................922
85.3 RSA/4/FAIL_WRITE_FLASH................................................................................................................................923
85.4 RSA/3/HOST_PUBKEY_BAK_FAL......................................................................................................................923
85.5 RSA/4/HOSTKEY_BACKUP_ERR........................................................................................................................924
85.6 RSA/4/HOSTKEY_BAK_DEL_ERR......................................................................................................................924
85.7 RSA/3/HOSTKEY_DEL_ERR................................................................................................................................925
85.8 RSA/6/HOSTKEY_DEL_SUC................................................................................................................................926
85.9 RSA/3/HOSTKEY_GEN_FAIL..............................................................................................................................926
85.10 RSA/6/HOSTKEY_GEN_SUCCESS....................................................................................................................927
85.11 RSA/3/HOSTKEY_SAVE_ERR...........................................................................................................................927
85.12 RSA/6/KEY_SIZE..................................................................................................................................................928
85.13 RSA/6/NOT_DESTROY_KEYS...........................................................................................................................928
85.14 RSA/6/NOT_REPLACE_KEYS............................................................................................................................929
85.15 RSA/6/REPLACE_KEYS......................................................................................................................................930
85.16 RSA/4/SERVERKEY_BKUP_ERR......................................................................................................................930
85.17 RSA/3/SERVERKEY_DEL_ERR.........................................................................................................................931
85.18 RSA/6/SERVERKEY_DEL_SUC.........................................................................................................................931
85.19 RSA/3/SERVERKEY_GEN_FAIL........................................................................................................................932
85.20 RSA/6/SERVERKEY_GEN_SUC.........................................................................................................................932
85.21 RSA/3/SERVERKEY_SAVE_ERR......................................................................................................................933
85.22 RSA/3/SERVR_PUBKEY_BAK_FAL.................................................................................................................934
85.23 RSA/4/SEVEKEY_BAK_DEL_ERR....................................................................................................................934
86 RSVP..........................................................................................................................................936
86.1 RSVP/6/DISABLE_MPLS.......................................................................................................................................938
86.2 RSVP/6/ENABLE_INTF.........................................................................................................................................938
86.3 RSVP/6/ENABLE_MPLS........................................................................................................................................939
86.4 RSVP/6/FUNC_SPEC_AVAIL...............................................................................................................................939
86.5 RSVP/6/FUNC_SPEC_UNAVAIL..........................................................................................................................940
86.6 RSVP/6/GET_MPLS_MTU_FAIL..........................................................................................................................940
86.7 RSVP/7/GLOBAL_OVER_FAIL............................................................................................................................941
Issue 07 (2014-07-30)

xxxv

Log Reference
Contents
86.8 RSVP/6/GR_AGING_TIMER_END.......................................................................................................................941
86.9 RSVP/6/GR_AGING_TIMER_START..................................................................................................................942
86.10 RSVP/6/GR_RES_NBR_ENDTONOR.................................................................................................................943
86.11 RSVP/6/GR_RES_NBR_NORTOEND.................................................................................................................943
86.12 RSVP/6/GR_RES_NBR_NORTOSUP..................................................................................................................944
86.13 RSVP/6/GR_RES_NBR_SUPTOEND..................................................................................................................944
86.14 RSVP/6/GR_RES_NBR_SUPTONOR..................................................................................................................945
86.15 RSVP/6/GR_RES_NORTORES............................................................................................................................946
86.16 RSVP/6/GR_RES_RECTONOR............................................................................................................................946
86.17 RSVP/6/GR_RES_RESTONOR............................................................................................................................947
86.18 RSVP/6/GR_RES_RESTOREC.............................................................................................................................947
86.19 RSVP/6/GR_SUP_NBR_MRESTONOR..............................................................................................................948
86.20 RSVP/6/GR_SUP_NBR_MRESTORES...............................................................................................................948
86.21 RSVP/6/GR_SUP_NBR_NORTOMRES..............................................................................................................949
86.22 RSVP/6/GR_SUP_NBR_NORTORES..................................................................................................................950
86.23 RSVP/6/GR_SUP_NBR_RESTOMRES...............................................................................................................950
86.24 RSVP/6/GR_SUP_NBR_RESTONOR..................................................................................................................951
86.25 RSVP/6/INC_INTF................................................................................................................................................951
86.26 RSVP/6/INTF_SEQ_RCH_MAX..........................................................................................................................952
86.27 RSVP/3/LOOP_PATH...........................................................................................................................................953
86.28 RSVP/3/LOOP_RESV...........................................................................................................................................954
86.29 RSVP/3/LSP_DOESNOT_EXIST.........................................................................................................................954
86.30 RSVP/3/LSP_EXCEED_PAF_LIC........................................................................................................................955
86.31 RSVP/3/LSRID_GET_FAIL..................................................................................................................................956
86.32 RSVP/6/MAX_NBR_REACH...............................................................................................................................956
86.33 RSVP/6/MAX_SESSION_REACH.......................................................................................................................957
86.34 RSVP/3/NBR_NO_GR_PATH..............................................................................................................................958
86.35 RSVP/3/NBR_NO_GR_REC_PATH....................................................................................................................958
86.36 RSVP/6/NOTIFY_LSPM_GR_END.....................................................................................................................959
86.37 RSVP/6/NOTIFY_LSPM_GR_START.................................................................................................................960
86.38 RSVP/6/PSB_CLEAN_TIMEOUT........................................................................................................................960
86.39 RSVP/3/REACH_LIC_LIMIT...............................................................................................................................961
86.40 RSVP/4/REACH_LIST_MAXLEGTH..................................................................................................................962
86.41 RSVP/3/REACH_PSB_MAXNUM.......................................................................................................................962
86.42 RSVP/3/RECONSTRUCT_LSP_FAIL.................................................................................................................963
86.43 RSVP/6/RECOVERY_TIMER_END....................................................................................................................964
86.44 RSVP/6/RECOVERY_TIMER_START...............................................................................................................964
86.45 RSVP/6/RESTART_TIMER_END........................................................................................................................965
86.46 RSVP/6/RESTART_TIMER_START...................................................................................................................965
86.47 RSVP/6/RSB_CLEAN_TIMEOUT.......................................................................................................................966
86.48 RSVP/7/SD_HA_BACK_OVER_FAIL................................................................................................................967
Issue 07 (2014-07-30)

xxxvi

Log Reference
Contents
87 SDSF...........................................................................................................................................968
87.1 ALMA/4/SDFAILURE............................................................................................................................................969
87.2 ALMA/6/SDRESUME.............................................................................................................................................969
87.3 ALMA/3/SFFAILURE.............................................................................................................................................970
87.4 ALMA/6/SFRESUME..............................................................................................................................................971
88 SECE...........................................................................................................................................972
88.1 SECE/4/ARPMISS...................................................................................................................................................974
88.2 SECE/3/ARPS_DROP_PACKET_GLOBLE_SPDLMT........................................................................................974
88.3 SECE/3/ARPS_DROP_PACKET_HDADDR_LEN...............................................................................................975
88.4 SECE/3/ARPS_DROP_PACKET_IF_SPDLMT.....................................................................................................976
88.5 SECE/3/ARPS_DROP_PACKET_LENTH.............................................................................................................977
88.6 SECE/3/ARPS_DROP_PACKET_OPTYPE...........................................................................................................978
88.7 SECE/3/ARPS_DROP_PACKET_PROADDR_LEN.............................................................................................979
88.8 SECE/3/ARPS_DROP_PACKET_SRC_MAC.......................................................................................................980
88.9 SECE/3/ARPS_DROP_PACKET_VLAN_SPDLMT.............................................................................................980
88.10 SECE/4/DAI_DROP_PACKET.............................................................................................................................981
88.11 SECE/4/GWCONFLICT........................................................................................................................................982
88.12 SECE/4/ICMP_GLOBAL_RATELIMIT...............................................................................................................983
88.13 SECE/4/ICMP_INTF_RATELIMIT......................................................................................................................983
88.14 SECE/4/IPSG_DROP_PACKET...........................................................................................................................984
88.15 SECE/4/IPSG_TABLE_RESOURCE....................................................................................................................985
88.16 SECE/6/MFF_GW_MAC_CHANGED.................................................................................................................985
88.17 SECE/4/PORT_ATTACK......................................................................................................................................986
88.18 SECE/6/PORT_ATTACK_END............................................................................................................................987
88.19 SECE/4/PORT_ATTACK_OCCUR......................................................................................................................988
88.20 SECE/4/SPECIFY_SIP_ATTACK........................................................................................................................989
88.21 SECE/4/STORMCTRL_BC_BLOCKED..............................................................................................................990
88.22 SECE/4/STORMCTRL_BC_UNBLOCK..............................................................................................................990
88.23 SECE/4/STORMCTRL_IF_NORMAL.................................................................................................................991
88.24 SECE/4/STORMCTRL_IF_SHUTDOWN............................................................................................................991
88.25 SECE/4/STORMCTRL_MC_BLOCKED.............................................................................................................992
88.26 SECE/4/STORMCTRL_MC_UNBLOCK.............................................................................................................993
88.27 SECE/4/STORMCTRL_UC_BLOCKED..............................................................................................................993
88.28 SECE/4/STORMCTRL_UC_UNBLOCK.............................................................................................................994
88.29 SECE/4/STRACK_DENY.....................................................................................................................................994
88.30 SECE/4/STRACK_ERROR_DOWN.....................................................................................................................995
88.31 SECE/4/USER_ATTACK......................................................................................................................................996
89 SEP..............................................................................................................................................998
89.1 SEP/6/CFG_ADD_PORT........................................................................................................................................999
89.2 SEP/6/CFG_DEL_PORT.........................................................................................................................................999
Issue 07 (2014-07-30)

xxxvii

Log Reference
Contents
89.3 SEP/4/LSA_NUM_REACH_MAX.......................................................................................................................1000
89.4 SEP/6/MSI_LESS_MSN........................................................................................................................................1000
89.5 SEP/3/PREEMPT_REQ_FAIL..............................................................................................................................1001
89.6 SEP/6/RCV_CFM_FAULT....................................................................................................................................1002
90 SHELL......................................................................................................................................1004
90.1 SHELL/5/CMDRECORD......................................................................................................................................1005
90.2 SHELL/6/CMDCONFIRM_NOPROMPT............................................................................................................1005
90.3 SHELL/6/CMDCONFIRM_RECORD..................................................................................................................1006
90.4 SHELL/6/CMDCONFIRM_UNIFORMRECORD................................................................................................1007
90.5 SHELL/6/DISPLAY_CMDRECORD...................................................................................................................1008
90.6 SHELL/4/LOGINFAILED.....................................................................................................................................1009
90.7 SHELL/5/LOGIN...................................................................................................................................................1010
90.8 SHELL/5/LOGOUT...............................................................................................................................................1011
90.9 SHELL/4/OVERWRITE_EXEC............................................................................................................................1012
90.10 SHELL/5/SETPASS_FAIL_FIRSTLOGIN.........................................................................................................1012
90.11 SHELL/5/TIMEOUT............................................................................................................................................1013
91 SMLK.......................................................................................................................................1014
91.1 SMLK/4/MTLK_STATUS_LOG..........................................................................................................................1015
91.2 SMLK/4/SMLK_CMD_LOG................................................................................................................................1015
91.3 SMLK/4/SMLK_FLUSH_LOG.............................................................................................................................1016
91.4 SMLK/4/SMLK_FLUSH_LOG.............................................................................................................................1017
91.5 SMLK/4/SMLK_STATUS_LOG..........................................................................................................................1017
91.6 SMLK/6/SMLK_EVENT_LOG............................................................................................................................1018
91.9 SMLK/6/SMLK_FSM_LOG..................................................................................................................................1020
92 SNMP.......................................................................................................................................1022
92.1 SNMP/6/SNMP_CNFM_CHANGEUDPORT......................................................................................................1023
92.2 SNMP/6/CNFM_VERSION_DISABLE................................................................................................................1023
92.3 SNMP/4/SNMP_SET.............................................................................................................................................1024
92.4 SNMP/4/SNMP_FAIL...........................................................................................................................................1025
92.5 SNMP/6/TRAPCMDRECORD_YES....................................................................................................................1026
92.6 SNMP/6/TRAPCMDRECORD_NO......................................................................................................................1027
93 SNPG........................................................................................................................................1028
93.1 SNPG/6/BGPPWBDWEXD..................................................................................................................................1031
93.2 SNPG/6/BGPPWBDWEXDCFG...........................................................................................................................1031
93.3 SNPG/6/BGPPWCHNLBDWEXD........................................................................................................................1032
93.4 SNPG/6/BGPPWCHNLBDWEXDCFG................................................................................................................1033
93.5 SNPG/6/BGPPWCHNLCNTEXDCFG.................................................................................................................1033
93.6 SNPG/6/BGPPWCNTEXD....................................................................................................................................1034
Issue 07 (2014-07-30)

xxxviii

Log Reference
Contents
93.7 SNPG/6/BGPPWCNTEXDCFG............................................................................................................................1035
93.8 SNPG/6/GLBBDWEXD........................................................................................................................................1035
93.9 SNPG/6/GLBBDWEXDCFG................................................................................................................................1036
93.10 SNPG/6/GLBCHNLBDWEXD...........................................................................................................................1037
93.11 SNPG/6/GLBCHNLBDWEXDCFG....................................................................................................................1037
93.12 SNPG/6/GLBCHNLCNTEXD.............................................................................................................................1038
93.13 SNPG/6/GLBCHNLCNTEXDCFG.....................................................................................................................1039
93.14 SNPG/6/GLBCNTEXD........................................................................................................................................1039
93.15 SNPG/6/GLBCNTEXDCFG................................................................................................................................1040
93.16 SNPG/6/GLOBALCHANNELDENY.................................................................................................................1041
93.17 SNPG/6/LDPPWBDWEXD.................................................................................................................................1041
93.18 SNPG/6/LDPPWBDWEXDCFG.........................................................................................................................1042
93.19 SNPG/6/LDPPWCHNLBDWEXD......................................................................................................................1043
93.20 SNPG/6/LDPPWCHNLBDWEXDCFG..............................................................................................................1043
93.21 SNPG/6/LDPPWCHNLCNTEXD.......................................................................................................................1044
93.22 SNPG/6/LDPPWCHNLCNTEXDCFG...............................................................................................................1045
93.23 SNPG/6/LDPPWCNTEXD..................................................................................................................................1046
93.24 SNPG/6/LDPPWCNTEXDCFG..........................................................................................................................1046
93.25 SNPG/6/PORTBDWEXD....................................................................................................................................1047
93.26 SNPG/6/PORTBDWEXDCFG............................................................................................................................1048
93.27 SNPG/6/PORTCHNLBDWEXD.........................................................................................................................1049
93.28 SNPG/6/PORTCHNLBDWEXDCFG.................................................................................................................1049
93.29 SNPG/6/PORTCHNLCNTEXD..........................................................................................................................1050
93.30 SNPG/6/PORTCHNLCNTEXDCFG...................................................................................................................1051
93.31 SNPG/6/PORTCNTEXD.....................................................................................................................................1051
93.32 SNPG/6/PORTCNTEXDCFG..............................................................................................................................1052
93.33 SNPG/6/PORTVLANBDWEXD.........................................................................................................................1053
93.34 SNPG/6/PORTVLANBDWEXDCFG.................................................................................................................1053
93.35 SNPG/6/PORTVLANCHBDWEXDCFG............................................................................................................1054
93.36 SNPG/6/PORTVLANCHCNTEXDCFG.............................................................................................................1055
93.37 SNPG/6/PORTVLANCHNLBDWEXD..............................................................................................................1056
93.38 SNPG/6/PORTVLANCHNLCNTEXD...............................................................................................................1057
93.39 SNPG/6/PORTVLANCNTEXD..........................................................................................................................1057
93.40 SNPG/6/PORTVLANCNTEXDCFG..................................................................................................................1058
93.41 SNPG/6/QINQBDWEXDCFG............................................................................................................................1059
93.42 SNPG/6/QINQCHNLBDWEXDCFG..................................................................................................................1060
93.43 SNPG/6/QINQCHNLCNTEXDCFG...................................................................................................................1060
93.44 SNPG/6/QINQCNTEXDCFG..............................................................................................................................1061
93.45 SNPG/6/QINQIFBDWEXD.................................................................................................................................1062
93.46 SNPG/6/QINQIFCHNLBDWEXD......................................................................................................................1062
93.47 SNPG/6/QINQIFCHNLCNTEXD.......................................................................................................................1063
Issue 07 (2014-07-30)

xxxix

Log Reference
Contents
93.48 SNPG/6/QINQIFCNTEXD..................................................................................................................................1064
93.49 SNPG/6/SUBIFBDWEXD...................................................................................................................................1065
93.50 SNPG/6/SUBIFBDWEXDCFG...........................................................................................................................1065
93.51 SNPG/6/SUBIFCHNLBDWEXD........................................................................................................................1066
93.52 SNPG/6/SUBIFCHNLBDWEXDCFG................................................................................................................1067
93.53 SNPG/6/SUBIFCHNLCNTEXD.........................................................................................................................1068
93.54 SNPG/6/SUBIFCHNLCNTEXDCFG..................................................................................................................1068
93.55 SNPG/6/SUBIFCNTEXD....................................................................................................................................1069
93.56 SNPG/6/SUBIFCNTEXDCFG............................................................................................................................1070
93.57 SNPG/6/VLANBDWEXD...................................................................................................................................1070
93.58 SNPG/6/VLANBDWEXDCFG...........................................................................................................................1071
93.59 SNPG/6/VLANCHANNELDENY......................................................................................................................1072
93.60 SNPG/6/VLANCHNLBDWEXD........................................................................................................................1072
93.61 SNPG/6/VLANCHNLBDWEXDCFG................................................................................................................1073
93.62 SNPG/6/VLANCHNLCNTEXD..........................................................................................................................1074
93.63 SNPG/6/VLANCHNLCNTEXDCFG..................................................................................................................1074
93.64 SNPG/6/VLANCNTEXD....................................................................................................................................1075
93.65 SNPG/6/VLANCNTEXDCFG.............................................................................................................................1076
93.66 SNPG/6/VSIBDWEXD........................................................................................................................................1076
93.67 SNPG/6/VSIBDWEXDCFG................................................................................................................................1077
93.68 SNPG/6/VSICHANNELDENY...........................................................................................................................1078
93.69 SNPG/6/VSICHNLBDWEXD.............................................................................................................................1078
93.70 SNPG/6/VSICHNLBDWEXDCFG.....................................................................................................................1079
93.71 SNPG/6/VSICHNLCNTEXD..............................................................................................................................1080
93.72 SNPG/6/VSICHNLCNTEXDCFG......................................................................................................................1080
93.73 SNPG/6/VSICNTEXD.........................................................................................................................................1081
93.74 SNPG/6/VSICNTEXDCFG.................................................................................................................................1082
94 SOCKET..................................................................................................................................1083
94.1 SOCKET/4/ASYNACCEPTFAIL.........................................................................................................................1084
94.2 SOCKET/1/BINDPEERIP.....................................................................................................................................1084
94.3 SOCKET/4/CANTGETLSTNSOCK.....................................................................................................................1085
94.4 SOCKET/4/EXCEEDMAXQLEN.........................................................................................................................1086
94.5 SOCKET/6/FGETVPNNAME...............................................................................................................................1087
94.6 SOCKET/6/LSTNASYNQUEINFO......................................................................................................................1087
94.7 SOCKET/6/SGETVPNNAME...............................................................................................................................1089
94.8 SOCKET/4/SO_ACCEPTCFAIL..........................................................................................................................1089
94.9 SOCKET/6/SOCKCLOSED..................................................................................................................................1090
94.10 SOCKET/6/SOCKNOTEXIST............................................................................................................................1091
94.11 SOCKET/6/SUBQUEINFO.................................................................................................................................1092
94.12 SOCKET/6/TCPASYNQUEINFO.......................................................................................................................1093
94.13 SOCKET/6/TCPCONNBLK................................................................................................................................1094
Issue 07 (2014-07-30)

xl

Log Reference
Contents
94.14 SOCKET/6/TCPIOSTAT.....................................................................................................................................1095
94.15 SOCKET/6/TCPWNDCLOSE.............................................................................................................................1095
94.16 SOCKET/6/VRBSRIPSOCKINFO......................................................................................................................1096
94.17 SOCKET/6/VRBSSOCKINFO............................................................................................................................1097
94.18 SOCKET/6/VRBSTCPSOCKINFO.....................................................................................................................1098
94.19 SOCKET/6/VRBSUDPSOCKINFO....................................................................................................................1099
95 SRM..........................................................................................................................................1100
95.1 SRM/4/6300_FPGA_FAULT................................................................................................................................1102
95.2 SRM/4/6300_FPGA_FAULT_RESUME..............................................................................................................1102
95.3 SRM/3/BCM56514_XAUI_REF_CLOCK_FAULT.............................................................................................1103
95.4 SRM/3/BCM56514_XAUI_REF_CLOCK_FAULT_RESUME...........................................................................1103
95.5 SRM/4/BATCGOVERCURPROTECT.................................................................................................................1104
95.6 SRM/4/BATCGOVERVOLPROTECT.................................................................................................................1105
95.7 SRM/2/BATDGTEMPHIGH.................................................................................................................................1105
95.8 SRM/4/BATDGTEMPHIGHRESUME.................................................................................................................1106
95.9 SRM/4/BATLIFEENDCLEAR..............................................................................................................................1107
95.10 SRM/2/BATINVALID.........................................................................................................................................1107
95.11 SRM/2/BATSUPPLYTIMESHORT....................................................................................................................1108
95.12 SRM/2/BATREMAINLOW.................................................................................................................................1109
95.13 SRM/4/BATREMAINLOWRESUME................................................................................................................1110
95.14 SRM/4/BATTEMPDGHIGHPROTECT.............................................................................................................1110
95.15 SRM/2/BATTEMPLOW......................................................................................................................................1111
95.16 SRM/4/BATTEMPLOWPROTECT....................................................................................................................1112
95.17 SRM/4/BATTEMPLOWRESUME......................................................................................................................1112
95.18 SRM/3/I2C_FAULT.............................................................................................................................................1113
95.19 SRM/3/I2C_FAULT_RESUME..........................................................................................................................1114
95.20 SRM/3/USB5V_POWFAULT.............................................................................................................................1114
95.21 SRM/3/USB5V_POWFAULT_RESUME...........................................................................................................1115
95.22 SRM/3/FANEXC..................................................................................................................................................1115
95.23 SRM/3/FANOK....................................................................................................................................................1116
95.24 SRM/4/FANPLGIN..............................................................................................................................................1117
95.25 SRM/3/FANPLUGOUT.......................................................................................................................................1117
95.26 SRM/3/LIGHT_FAULT.......................................................................................................................................1118
95.27 SRM/3/LIGHT_FAULT_RESUME....................................................................................................................1119
95.28 SRM/3/INOUT.....................................................................................................................................................1119
95.29 SRM/6/SRM_LOGID_STARTUP_VERSION....................................................................................................1120
95.30 SRM/1/POWEXC.................................................................................................................................................1121
95.31 SRM/6/POWON...................................................................................................................................................1121
95.32 SRM/4/POWPLGIN.............................................................................................................................................1122
95.33 SRM/4/POWPULOUT.........................................................................................................................................1122
95.34 SRM/3/TXPOWER_EXCEEDMAJOR...............................................................................................................1123
Issue 07 (2014-07-30)

xli

Log Reference
Contents
95.35 SRM/3/RXPOWER_EXCEEDMINOR............................................................................................................... 1124

95.36 SRM/5/RXPOWER_RESUME............................................................................................................................1124
95.37 SRM/6/SFPCATEGORY_UNKNOW................................................................................................................. 1125
95.38 SRM/4/STACK_PORT_DOWN..........................................................................................................................1125
95.39 SRM/4/STACK_PORT_UP.................................................................................................................................1126
95.40 SRM/3/RXPOWER_EXCEEDMAJOR...............................................................................................................1127
95.41 SRM/3/TXPOWER_EXCEEDMINOR...............................................................................................................1127
95.42 SRM/5/TXPOWER_RESUME............................................................................................................................1128
95.43 SRM/3/WTFLSHFAIL.........................................................................................................................................1129
96 SSH...........................................................................................................................................1130
96.1 SSH/4/CMD_USERCHOICE................................................................................................................................1131
96.2 SSH/5/CMDRECORD...........................................................................................................................................1131
96.3 SSH/4/CONTINUE_KEYEXCHANGE................................................................................................................1132
96.4 SSH/4/OVERWRITE_FILE...................................................................................................................................1132
96.5 SSH/4/RENAME_FILE.........................................................................................................................................1133
96.6 SSH/4/SAVE_PUBLICKEY..................................................................................................................................1134
96.7 SSH/4/SAVEAS_PUBLICKEY.............................................................................................................................1134
96.8 SSH/4/SFTP_REQ_RECORD...............................................................................................................................1135
96.9 SSH/4/SSH_FAIL..................................................................................................................................................1136
96.10 SSH/4/STELNET_SERVER................................................................................................................................1137
96.11 SSH/4/UPDATE_PUBLICKEY..........................................................................................................................1137
97 SW_SNPG...............................................................................................................................1139
97.1 SW_SNPG/4/IGMP_PKT_INVALID....................................................................................................................1140
97.2 SW_SNPG/4/IGMPV1_PKT.................................................................................................................................1140
97.3 SW_SNPG/4/IGMPV2_PKT.................................................................................................................................1141
97.4 SW_SNPG/3/L2PORT_INVALID........................................................................................................................1142
97.5 SW_SNPG/4/PORT_EVT_IGNORE.....................................................................................................................1142
97.6 SW_SNPG/6/PORT_LEAVE................................................................................................................................1143
97.7 SW_SNPG/4/PORT_EXCEED..............................................................................................................................1143
97.8 SW_SNPG/4/RPC_FAIL.......................................................................................................................................1144
97.9 SW_SNPG/4/ROUTER_PORT_EXCEED............................................................................................................1145
97.10 SW_SNPG/3/TASK_INVALID...........................................................................................................................1145
98 TAD..........................................................................................................................................1147
98.1 TAD/6/ALARMAGING........................................................................................................................................1148
98.2 TAD/6/ALARMCEILING.....................................................................................................................................1148
98.3 TAD/6/ALARMDAMP..........................................................................................................................................1149
98.4 TAD/6/ALARMDOWN......................................................................................................................................... 1149
98.5 TAD/6/ALARMPULSE.........................................................................................................................................1150
98.6 TAD/6/ALARMREUSE.........................................................................................................................................1150
98.7 TAD/6/ALARMUP................................................................................................................................................1151
Issue 07 (2014-07-30)

xlii

Log Reference
Contents
98.8 TAD/6/FILTERTIMER..........................................................................................................................................1152
98.9 TAD/4/IFDOWN....................................................................................................................................................1152
98.10 TAD/4/IFUP.........................................................................................................................................................1153
99 TFTP.........................................................................................................................................1154
99.1 TFTP/4/OVERWRITE...........................................................................................................................................1155
100 TNLM.....................................................................................................................................1156
100.1 TNLM/5/ADD_EXTNODE.................................................................................................................................1157
100.2 TNLM/5/ADD_NODE.........................................................................................................................................1157
100.3 TNLM/5/BINDING..............................................................................................................................................1158
100.4 TNLM/5/DEL_BINDING....................................................................................................................................1158
100.5 TNLM/4/DEL_NODE..........................................................................................................................................1159
100.6 TNLM/6/FAIL_ALLOCTOKEN.........................................................................................................................1159
100.7 TNLM/5/FAIL_SETTNLPLY.............................................................................................................................1160
100.8 TNLM/5/INVALID_POLICY..............................................................................................................................1161
100.9 TNLM/5/MEM_SHORTAGE..............................................................................................................................1161
100.10 TNLM/5/NTY_VPN_APPPLCY.......................................................................................................................1162
100.11 TNLM/5/OLD_LOG..........................................................................................................................................1162
100.12 TNLM/5/REC_L3V_APPPLCY........................................................................................................................1163
100.13 TNLM/5/SEARCH_NODE................................................................................................................................1164
100.14 TNLM/5/SET_POLICY_NAME.......................................................................................................................1164
100.15 TNLM/5/TNL_IF_DEL......................................................................................................................................1165
101 TRAFSTAT...........................................................................................................................1166
101.1 TRAFSTAT/6/BATCH_BACKUP_BEGIN........................................................................................................1167
101.2 TRAFSTAT/6/BATCH_BACKUP_END............................................................................................................1167
101.3 TRAFSTAT/6/L3V_RCVSTAT..........................................................................................................................1168
101.4 TRAFSTAT/6/L3V_RESETSTATALL..............................................................................................................1168
101.5 TRAFSTAT/6/L3V_RESETSTATVRF..............................................................................................................1169
101.6 TRAFSTAT/6/L3V_SUCSTATDIS....................................................................................................................1169
101.7 TRAFSTAT/6/L3V_SUCSTATEN.....................................................................................................................1170
101.8 TRAFSTAT/5/VSIDISABLE..............................................................................................................................1170
101.9 TRAFSTAT/5/VSIDISABLEPW........................................................................................................................1171
101.10 TRAFSTAT/5/VSIENABLE..............................................................................................................................1172
101.11 TRAFSTAT/5/VSIENABLEPW........................................................................................................................1172
101.12 TRAFSTAT/5/VSIRESET.................................................................................................................................1173
101.13 TRAFSTAT/5/VSIRESETALL.........................................................................................................................1174
101.14 TRAFSTAT/5/VSIUNDOL2VPN.....................................................................................................................1174
101.15 TRAFSTAT/5/VSIUNDOVSI...........................................................................................................................1175
102 TRUNK..................................................................................................................................1176
102.1 TRUNK/5/BACKSTATE_CHANGE..................................................................................................................1177
102.2 TRUNK/5/MEMBER_DOWN............................................................................................................................1178
Issue 07 (2014-07-30)

xliii

Log Reference
Contents
102.3 TRUNK/5/MEMBER_UP....................................................................................................................................1179
102.4 TRUNK/5/STAT_INACT_TO_ACT...................................................................................................................1179
102.5 TRUNK/5/TRUNKDOWN..................................................................................................................................1180
102.6 TRUNK/5/TRUNKUP.........................................................................................................................................1181
103 TUNNEL................................................................................................................................1182
103.1 TUNNEL/6/HOT_INSERT..................................................................................................................................1183
103.2 TUNNEL/6/HOT_REMOVE...............................................................................................................................1183
104 TUNN_PS..............................................................................................................................1185
104.1 TUNN_PS/5/BATCH_BKP_SUCCESS..............................................................................................................1186
104.2 TUNN_PS/4/CLEAR_SIGNAL_FAIL................................................................................................................1186
104.3 TUNN_PS/2/DEL_PS_PTUNN_FAIL................................................................................................................1187
104.4 TUNN_PS/2/DEL_PS_WTUNN_FAIL..............................................................................................................1187
104.5 TUNN_PS/2/INFO_CMD_DISP.........................................................................................................................1188
104.6 TUNN_PS/6/NOTIFY_DELETE_AUTOTUNNEL............................................................................................1189
104.7 TUNN_PS/6/NOTIFY_VPLS..............................................................................................................................1189
104.8 TUNN_PS/2/PTUNN_ID_INVALID..................................................................................................................1190
104.9 TUNN_PS/1/REAL_BKP_MEM_FAIL..............................................................................................................1190
104.10 TUNN_PS/5/SMOOTH_SUCCESS..................................................................................................................1191
104.11 TUNN_PS/3/SWITCH_FAIL_SMOOTH.........................................................................................................1191
104.12 TUNN_PS/2/TUNN_ID_CFG_FAIL................................................................................................................1192
104.13 TUNN_PS/2/WTUNN_ID_INVALID...............................................................................................................1193
105 UCM.......................................................................................................................................1194
105.1 UCM/3/MAXIMUM_HSB_BATCHUPFAIL.....................................................................................................1195
105.2 UCM/IC_LEVEL_EMERG/USER_ADDACLFAIL..........................................................................................1195
105.3 UCM/4/USER_ADDUSERGROUPCARFAIL...................................................................................................1196
105.4 UCM/3/VM_USER_ADDACLFAIL...................................................................................................................1197
105.5 UCM/5/USER_INFO_AUTHENTICATION......................................................................................................1197
105.6 CM/5/USER_INFO_OFFLINE............................................................................................................................1198
106 VFS.........................................................................................................................................1200
106.1 VFS/5/CLOSEDIR_FAIL....................................................................................................................................1202
106.2 VFS/4/DELETE_LOG_FILE...............................................................................................................................1202
106.3 VFS/6/DEV_REG................................................................................................................................................1203
106.4 VFS/5/DEV_UNREG...........................................................................................................................................1203
106.5 VFS/5/DIR_FAIL.................................................................................................................................................1204
106.6 VFS/4/DIR_NAME_IS_OCCUPIED..................................................................................................................1204
106.7 VFS/4/DISKSPACE_NOT_ENOUGH................................................................................................................1205
106.8 VFS/3/FAILGETFILELEN..................................................................................................................................1205
106.9 VFS/4/FILE_CPY_ALL_FAIL............................................................................................................................1206
106.10 VFS/6/FILE_CPY_ALL_OK.............................................................................................................................1207
106.11 VFS/4/FILE_CPY_FAIL....................................................................................................................................1207
Issue 07 (2014-07-30)

xliv

Log Reference
Contents
106.12 VFS/5/FILE_CPY_PART_OK..........................................................................................................................1208
106.13 VFS/4/FILE_NAME_IS_OCCUP......................................................................................................................1208
106.14 VFS/5/FILE_NOT_EXIST.................................................................................................................................1209
106.15 VFS/3/FILE_SLOT_PREFIX_ERR...................................................................................................................1210
106.16 VFS/4/FILE_USED_DIR_NAME.....................................................................................................................1210
106.17 VFS/6/FILE_USR_CANCEL............................................................................................................................1211
106.18 VFS/6/FILE_USR_CANCEL_CPY...................................................................................................................1211
106.19 VFS/6/FILE_USR_CANCEL_DEL...................................................................................................................1212
106.20 VFS/5/FILE_USR_CONFIRM..........................................................................................................................1213
106.21 VFS/6/FILE_USR_CONFIRM_CPY................................................................................................................1213
106.22 VFS/6/FILE_USR_CONFIRM_DEL................................................................................................................1214
106.23 VFS/5/FILEACCESS_DENI..............................................................................................................................1215
106.24 VFS/5/FILECREATE_FAIL..............................................................................................................................1215
106.25 VFS/5/FILEDELETE_FAIL..............................................................................................................................1216
106.26 VFS/5/FILEINUSING........................................................................................................................................1216
106.27 VFS/5/FILEOPEN_FAIL...................................................................................................................................1217
106.28 VFS/5/FILEOPEN_MORE................................................................................................................................1218
106.29 VFS/5/FLASHWRITE_FAIL............................................................................................................................1218
106.30 VFS/6/IPCREGDEV_OK..................................................................................................................................1219
106.31 VFS/5/IPCUNREGDEV_OK.............................................................................................................................1219
106.32 VFS/4/NO_LOG_FILE_TO_CLEAR................................................................................................................1220
106.33 VFS/4/NO_VAL_LOG_TO_CLEAR................................................................................................................1220
106.34 VFS/4/NOT_CLEAR_CURR_LOG..................................................................................................................1221
106.35 VFS/4/NOT_CLEAR_MONTH_LOG..............................................................................................................1222
106.36 VFS/3/PSEMTOOLONG...................................................................................................................................1222
106.37 VFS/5/UNREGDEV_OK...................................................................................................................................1223
106.38 VFS/3/WRITE_ERR..........................................................................................................................................1223
107 VOSCPU................................................................................................................................1225
107.1 VOSCPU/4/CPU_USAGE_HIGH.......................................................................................................................1226
107.2 VOSCPU/4/CPU_USAGE_RESUME.................................................................................................................1226
108 VRRP......................................................................................................................................1228
108.1 VRRP/5/DELTRACK3AH..................................................................................................................................1229
108.2 VRRP/4/STATEWARNING................................................................................................................................1229
108.3 VRRP/4/STATEWARNINGEXTEND................................................................................................................1230
108.4 VRRP/4/CHKFAIL..............................................................................................................................................1232
108.5 VRRP/4/SPECCHANGED..................................................................................................................................1233
109 VTRUNK...............................................................................................................................1235
109.1 VTRUNK/5/MEMBER_DOWN..........................................................................................................................1236
109.2 VTRUNK/5/MEMBER_UP.................................................................................................................................1236
109.3 VTRUNK/5/TRUNKDOWN...............................................................................................................................1237
Issue 07 (2014-07-30)

xlv

Log Reference
Contents
109.4 VTRUNK/5/TRUNKUP......................................................................................................................................1238
110 VTY.........................................................................................................................................1239
110.1 VTY/5/ACL_DENY.............................................................................................................................................1240
Issue 07 (2014-07-30)

xlvi

Log Reference
1 Introduction
Introduction
About This Chapter

The log module of the host software records operations on a device and events that occur on a
device. The recorded operations and events are log messages.
Log messages provide evidence for diagnosing and maintaining a system. Log messages reflect
the operating status of a device and are used to analyze the conditions of a network and to find
out the causes of network failure or faults.
After logging in to a device through the console port or in telnet mode, you can display log
messages stored on the log buffer by using the display logbuffer command and save the log
messages on the device. Log messages can be output to a log server with the support of the
SYSLOG protocol.
1.1 Log Message Format Description
1.2 Log Severity Description
Issue 07 (2014-07-30)


Log Reference
1 Introduction
1.1 Log Message Format Description

Format of Log Message
The SYSLOG protocol uses UDP port 514 to transmit log messages. Any UDP packet on port
514 is considered a log message. The output format of a log message is shown in Figure 1-1.
Figure 1-1 Output format of a Log message
Fields
Field
Description
TimeStamp
UTC
It is the time when a log message is generated

and sent to the log host. By default, it is the
coordinated universal time (UTC), which can
be configured to the host time.
TimeStamp and HostName are separated by
a space.
HostName
It is the system name of a local host. The

default HostName is HUAWEI.
HostName and ModuleName are separated
by a space.
Huawei Identity
%% refers to the identity of Huawei,

indicating that the log is produced by a
Huawei product.
Version
dd is a two-digit number starting from 01. It

specifies the version of a log format.
ModuleName
It specifies the module that generates log

messages. ModuleName and Severity are
separated by a slash (/).
Severity
Log messages are classified into eight

severity levels, ranging from 0 to 7.
Severity and Brief are separated by a slash
(/).
Brief
Issue 07 (2014-07-30)
It is a phrase that summarizes information.


Log Reference
1 Introduction
Field
Description
Log Flag
It indicates the type of the log information.

l (l): Log
l (t): Trap
l (d): Debug
The flag (l) and Description are separated by
a colon (:).
Count
It specifies the log serial number.
Description
It is a string of characters that describe a

detailed log message. It is output by a module
to the information center. It is filled in by a
module at each output time.
Example
Aug 6 2011 20:34:46 HUAWEI %% 01 HWCM/5/EXIT(l)[1]: exit from configure mode
l
The log message was generated at UTC time 20:34:46, Aug 6, 2011.
The host name is HUAWEI.
The log message was sent by the HWCM module.
The severity level of this log message is 5.
The description of this log message is exit from configuration mode.
Jan 8 2013 03:58:15+07:00 HUAWEI %% 01 HWCM/5/EXIT(l)[1]: exit from configure

mode
l
The log message was generated at the local host time 10:58:15, Jan 8, 2013.
The host name is HUAWEI.
The log message was sent by the HWCM module.
The severity level of this log message is 5.
The description of this log message is exit from configuration mode.
1.2 Log Severity Description

The severity level identifies the severity of a log message. Log messages are identified by eight
severity levels. They are listed in the following table.
Issue 07 (2014-07-30)
Level
Severity
Description
Emergency
Emergency condition
Alert
Errors needing immediate

actions


Log Reference
Issue 07 (2014-07-30)
1 Introduction
Level
Severity
Description
Critical
Critical condition
Errors
Errors needing attention but

not critical
Warnings
Warning condition, meaning

errors are likely to occur
Notifications
Information requiring your

attention
Informational
Generic prompt information
Debug
Debugging information


Log Reference
2 6OVER4
6OVER4
About This Chapter

2.1 6OVER4/4/CAMPNUM_UNCAMP
2.2 6OVER4/4/MAXNUM_UNCAMP
Issue 07 (2014-07-30)


Log Reference
2 6OVER4
2.1 6OVER4/4/CAMPNUM_UNCAMP
Message
6OVER4/4/CAMPNUM_UNCAMP:The compatible number of the 6over4 tunnel module is
not compatible.
Description
The compatible number of the 6over4 tunnel module was incompatible.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The data structure of the 6over4 tunnel module was changed, causing its compatible number to
become incompatible with the current version.
Procedure
Step 1 This log message indicates a normal situation, and no action is required.
----End
2.2 6OVER4/4/MAXNUM_UNCAMP
Message
6OVER4/4/MAXNUM_UNCAMP:The number of tunnels [number1] configured on the old
main control board is greater than the maximum number of tunnels [number2] that can be
configured on the new main control board.
Description
The number of the tunnels configured on the old main board was greater than the maximum
number of tunnels that can be configured on the new main control board.
Parameters
Parameter Name Parameter Meaning
[number1]
Issue 07 (2014-07-30)
Indicates the number of tunnels configured on the old main control board.

Log Reference
2 6OVER4

[number2]
Indicates the number of tunnels configured on the new main control board.
Possible Causes
The specifications of the new version were smaller. As a result, the number of configured tunnels
on the old main control board was greater than the maximum number of tunnels that could be
Procedure
Step 1 Check specifications and configurations to make sure that the specifications of the new main
control board are larger than the configurations of the old main control board. If specifications
do not meet requirements, you can repurchase the paf license of Huawei; otherwise, some
configurations will be lost.
----End
Issue 07 (2014-07-30)


Log Reference
3 AAA
AAA
About This Chapter

3.1 AAA/6/LOCAL_ACCOUNT_UNLOCK
3.2 AAA/6/LOCAL_ACCOUNT_LOCK
3.3 AAA/6/LOCAL_ACCOUNT_MODIFY
3.4 AAA/6/LOCAL_ACCOUNT_DEL
3.5 AAA/6/LOCAL_ACCOUNT_EXPIRED
3.6 AAA/6/LOCAL_ACCOUNT_MODIFYPWD_UNLOCK
3.7 AAA/6/LOCAL_ACCOUNT_MODIFYPWD_LOCK
Issue 07 (2014-07-30)


Log Reference
3 AAA
3.1 AAA/6/LOCAL_ACCOUNT_UNLOCK
Message
AAA/6/LOCAL_ACCOUNT_UNLOCK:Local account [STRING] has been unlocked.
Description
The local account was unlocked.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the local account name.
Possible Causes
l
The local-user user-name state active command was executed.
The lock function was enabled for the local account, and the number of consecutive times
that a user entered incorrect passwords reached the maximum. The local account was
locked. The the local account was automatically unlocked when the lock duration reached.
Procedure
Step 1 This log message is informational only, and no action is required.
----End
3.2 AAA/6/LOCAL_ACCOUNT_LOCK
Message
AAA/6/LOCAL_ACCOUNT_LOCK:Local account [STRING] has been locked.
Description
The local account was locked.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Issue 07 (2014-07-30)


Log Reference
3 AAA
Possible Causes
l
The local-user user-name state block command was executed.
The lock function was enabled for the local account, and the number of consecutive times
that a user entered incorrect passwords reached the maximum.
Procedure
Step 1 Run the local-user user-name state active command to unlock the local account.
----End
3.3 AAA/6/LOCAL_ACCOUNT_MODIFY
Message
AAA/6/LOCAL_ACCOUNT_MODIFY:Local account [STRING] password has been
modified.
Description
The password of the local account was changed.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Name of the local account that is modified.
Possible Causes
The password of the local account was changed.
Procedure
----End
3.4 AAA/6/LOCAL_ACCOUNT_DEL
Message
AAA/6/LOCAL_ACCOUNT_DEL:Local account [STRING] has been deleted.
Description
The local account was deleted.
Issue 07 (2014-07-30)

10

Log Reference
3 AAA
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The local account was deleted.
Procedure
----End
3.5 AAA/6/LOCAL_ACCOUNT_EXPIRED
Message
AAA/6/LOCAL_ACCOUNT_EXPIRED:Local account [STRING] has expired.
Description
The local account expired.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
l
The expired local account was used for local authentication.
The expired local account was used for local authorization.
The expired local account was used for command line authorization.
Procedure
Step 1 Run the local-user user-name expire-date expire-date command to prolong the validity period
of the account, or run the undo local-user user-name expire-date command to set the account
permanently valid.
----End
Issue 07 (2014-07-30)

11

Log Reference
3 AAA
3.6 AAA/6/LOCAL_ACCOUNT_MODIFYPWD_UNLOCK
Message
AAA/6/LOCAL_ACCOUNT_MODIFYPWD_UNLOCK:The password of local account
[STRING] can be changed.
Description
A local user is allowed to change the password.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the local user name.
Possible Causes
l
The user account was locked. When the locking time expires, the user account is unlocked
automatically.
The administrator has set the state of the local account to active.
Procedure
----End
3.7 AAA/6/LOCAL_ACCOUNT_MODIFYPWD_LOCK
Message
AAA/6/LOCAL_ACCOUNT_MODIFYPWD_LOCK:The password of local account
[STRING] cannot be changed.
Description
A local user is not allowed to change the password.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the local user name.
Issue 07 (2014-07-30)

12

Log Reference
3 AAA
Possible Causes
l
The user has entered incorrect old passwords for specified times within the specified retry
interval, and therefore the user account is locked. During the locking period, the user cannot
change the password.
The administrator has set the state of this local user to block.
Procedure
Step 1 Ask the administrator to unlock the user account.
Step 2 Wait until the locking time expires. Then the user account is unlocked automatically.
----End
Issue 07 (2014-07-30)

13

Log Reference
4 ACLE
ACLE
About This Chapter

4.1 ACLE/4/ACLLOG
Issue 07 (2014-07-30)

14

Log Reference
4 ACLE
4.1 ACLE/4/ACLLOG
Message
ACLE/4/ACLLOG:"[STRING]"
Description
This log is displayed when logging is specified in the ACL.
Parameters
[STRING]
Indicates the ACL number, deny/permit rule, interface name, time range,
source MAC address, destination MAC address, protocol type, source IP
address, source port number in UDP or TCP packets, destination IP
address, destination port number in UDP or TCP packets.
Possible Causes
The packet matches an ACL.
Procedure
l
Limit the rate of sending packets from the address in the log.
----End
Issue 07 (2014-07-30)

15

Log Reference
5 ADDR
ADDR
About This Chapter

5.1 ADDR/4/COLLISION_CNT_EXCEED
Issue 07 (2014-07-30)

16

Log Reference
5 ADDR
5.1 ADDR/4/COLLISION_CNT_EXCEED
Message
ADDR/6/COLLISION_CNT_EXCEED: Collision count reached maximum value for IPv6
CGA address [ip-address] on interface [interface-name].
Description
Collision count reached maximum value for a IPv6 CGA address on an interface.
Parameters
Parameter Name
Parameter Meaning
ip-address
IPv6 CGA Address.
interface-name
Interface Name of the CGA address.
Possible Causes
Enough number of retry has been given to re-generate new CGA address after found as duplicate
on the interface.
Procedure
Step 1 The administrator should re-configure the CGA address with different prefix.
----End
Issue 07 (2014-07-30)

17

Log Reference
6 ALML
ALML
About This Chapter

6.1 ALML/4/ENTUP
6.2 ALML/4/ENT_PLUG_IN
6.3 ALML/4/ENT_PULL_OUT
6.4 ALML/4/TEMP_LOWER
6.5 ALML/4/TEMP_LOWER_RESUME
Issue 07 (2014-07-30)

18

Log Reference
6 ALML
6.1 ALML/4/ENTUP
Message
ALML/4/ENTUP:[STRING] registers successfully.
Description
A board is registered successfully.
Parameters
[STRING]
Information of the entity that is registered successfully. For example,

describe the information of a board through the board name, board type,
or board slot ID.
Possible Causes
Normal startup process
Procedure
Step 1 This log does not need to be processed.
----End
6.2 ALML/4/ENT_PLUG_IN
Message
ALML/4/ENT_PLUG_IN:[STRING] was plugged in.
Description
A board or a subcard is inserted.
Parameters
[STRING]
Information of the inserted entity. For example, describe the information

of a board through the board name, board type, or board slot ID.
Possible Causes
A board or a subcard is inserted.
Issue 07 (2014-07-30)

19

Log Reference
6 ALML
Procedure
----End
6.3 ALML/4/ENT_PULL_OUT
Message
ALML/4/ENT_PULL_OUT:[STRING] was pulled out.
Description
A board or a subcard is removed.
Parameters
[STRING]
Information of the removed entity. For example, describe the information

of a board through the board name, board type, or board slot ID.
Possible Causes
Reason 1:
A board or a subcard is removed manually.
Reason 2:
The connection between a board or a subcard and the slot is loose.
Procedure
Step 1 If the board or subcard is removed manually, this log does not need to be processed.
Step 2 If the connection between the board or subcard and the slot is loose, insert the board or subcard
again.
----End
6.4 ALML/4/TEMP_LOWER
Message
ALML/4/TEMP_LOWER:The "[STRING1]" temperature of sensor [STRING2](entity) fell
below the lower [STRING3] limit.(SensorNum=[ULONG], Value=[STRING4],
UpperThreshold=[STRING5], LowerThreshold=[STRING6])
Issue 07 (2014-07-30)

20

Log Reference
6 ALML
Description
The temperature sensor on a board detects that the temperature is lower than the lower limit.
Parameters
Parameter Name
Parameter Meaning
[STRING1]
Name of temperature sensor
[STRING2]
Entity name
[STRING3]
Alarm level
[STRING4]
Current temperature value
[STRING5]
Upper limit of temperature
[STRING6]
Lower limit of temperature
[ULONG]
Sensor No.
Possible Causes
The temperature sensor detects that the temperature is lower than the lower limit.
Procedure
Step 1 Check whether the ambient temperature is too low. If so, increase the ambient temperature
properly.
Step 2 Heat the device.
Step 3 End.
----End
6.5 ALML/4/TEMP_LOWER_RESUME
Message
ALML/4/TEMP_LOWER_RESUME:The "[STRING1]" temperature of sensor [STRING2]
(entity) increased above the lower [STRING3] limit.(SensorNum=[ULONG], Value=
[STRING4], UpperThreshold=[STRING5], LowerThreshold=[STRING6])
Description
The temperature sensor detects that the ambient temperature is restored to the normal range.
Issue 07 (2014-07-30)

21

Log Reference
6 ALML
Parameters
Parameter Name
Parameter Meaning
[STRING1]
Name of temperature sensor
[STRING2]
Entity name
[STRING3]
Alarm level
[STRING4]
Current temperature
[STRING5]
Upper limit of temperature
[STRING6]
Lower limit of temperature
[ULONG]
Sensor No.
Possible Causes
The temperature sensor detects that the ambient temperature is restored to the normal range.
Procedure
----End
Issue 07 (2014-07-30)

22

Log Reference
7 APS
APS
About This Chapter

7.1 APS/7/DEFECT_NOTIFY_PFM
7.2 APS/7/PKT_PLAT_TO_PPI
7.3 APS/7/STATE_NOTIFY_PFM
7.4 APS/7/STATE_NOTIFY_PPI
7.5 APS/7/SYN_MES_IO_TO_MAIN
7.6 APS/7/SYN_MES_MAIN_TO_IO
Issue 07 (2014-07-30)

23

Log Reference
7 APS
7.1 APS/7/DEFECT_NOTIFY_PFM
Message
APS/7/DEFECT_NOTIFY_PFM:Defect changed failed to notify plat. (EventType=[ULONG],
MoudleID=[ULONG], GroupIndex=[ULONG], WorkingProtectionMiss=[ULONG],
LocalSMissFarBFlag=[ULONG], ProtectionModeMiss=[ULONG], RevertiveModeMiss=
[ULONG], ErrorCode=[ULONG])
Description
After detecting inconsistency, the APS state machine notified the S2750&S5700&S6700 service
module to process the result. If the notification failed, the notified information was recorded for
later analysis.
Parameters
Parameter Name
Parameter Meaning
EventType
Indicates the type of an event.
MoudleID
Indicates the index of a module.
GroupIndex
Indicates the index of a protection group.
WorkingProtectionMiss Indicating the working link and the protection link are inconsistent.
LocalSMissFarBFlag
Indicates that the local receiving link and the remote sending link are
inconsistent.
ProtectionModeMiss
Indicates that the protection mode is inconsistent.
RevertiveModeMiss
Indicates that the revertive mode is inconsistent.
ErrorCode
Indicates an error code.
Possible Causes
After detecting inconsistency, the APS state machine failed to notify the
S2750&S5700&S6700 service module to process the result.
Procedure
Step 1 Contact Huawei technical personnel.
----End
7.2 APS/7/PKT_PLAT_TO_PPI
Issue 07 (2014-07-30)

24

Log Reference
7 APS
Message
APS/7/PKT_PLAT_TO_PPI:Plat send packet templet to adapter failed.(ModuleID=[ULONG],
ProtectionID=[ULONG], APSFastSndInterval=[ULONG], WtrTime=[ULONG],
HoldOffTimeInterval=[ULONG], ProtectionEnable=[ULONG], APSPktFlag=[ULONG],
ProtectionMode=[ULONG], ProtectionDirection=[ULONG], RevertiveMode=[ULONG],
LocalState=[ULONG], GlobalState=[ULONG], APSState=[ULONG], LocalSelector=
[ULONG], LocalBridge=[ULONG], SwitchCommand=[ULONG], WorkingLinkState=
[ULONG], ProtectionLinkState=[ULONG], ProtectionProtocol=[ULONG], StatusSlot=
[STRING], WorkingLinkManageState=[ULONG], ProtectionLinkManageState=[ULONG],
ErrorCode=[ULONG])
Description
After finishing status calculation, the APS state machine sent the packet template to the device.
If the sending failed, the information about the packet template was recorded for later analysis.
Parameters
Parameter Name
Parameter Meaning
ModuleID
ProtectionID
APSFastSndInterval
Indicates the interval for fast sending packets.
WtrTime
Indicates the wait-to-restore time.
HoldOffTimeInterval
Indicates the hold-off time.
ProtectionEnable
Indicates the flag bit for enabling the protection.
APSPktFlag
Indicates the flag bit for enabling packets.
ProtectionMode
Indicates the protection mode.
ProtectionDirection
Indicates the protection direction.
RevertiveMode
Indicates the revertive mode.
LocalState
Indicates the local status.
GlobalState
Indicates the global status.
APSState
Indicates the status of APS packets.
LocalSelector
Indicates the local tunnel for selecting and receiving services.
LocalBridge
Indicates the local tunnel for sending services.
SwitchCommand
Indicates the local manual commands.
WorkingLinkState
Indicates the status of the local working link.
ProtectionLinkState
Indicates the status of the local protection link.
ProtectionProtocol
Indicates the protection protocol.
StatusSlot
Indicates the slot where the state machine is located.
Issue 07 (2014-07-30)

25

Log Reference
7 APS
Parameter Name
Parameter Meaning
WorkingLinkManageState
Indicates the management state of the local working link.
ProtectionLinkManageState Indicates the management state of the local protection link.

ErrorCode
Possible Causes
The S2750&S5700&S6700 failed to send information about the packet template to the device.
Procedure
----End
7.3 APS/7/STATE_NOTIFY_PFM
Message
APS/7/STATE_NOTIFY_PFM:State changed failed to notify plat. (EventType=[ULONG],
MoudleID=[ULONG], GroupIndex=[ULONG], ProtectionType=[ULONG], LocalState=
[ULONG], WorkingLinkState=[ULONG], ProtectionLinkState=[ULONG],
LocalAPSRequest=[ULONG], LocalRequestedSignal=[ULONG], LocalBridgedSignal=
[ULONG], FarEndRequest=[ULONG], FarABit=[ULONG], FarBBit=[ULONG], FarDBit=
[ULONG], FarRBit=[ULONG], FarEndRequestedSignal=[ULONG], FarEndBridgedSignal=
[ULONG], ErrorCode=[ULONG])
Description
After finishing status calculation, the APS state machine notified the S2750&S5700&S6700
service module to process the result. If the notification failed, the notified information was
recorded for later analysis.
Parameters
Parameter Name
Parameter Meaning
EventType
MoudleID
GroupIndex
ProtectionType
Indicates the protection type.
LocalState
Indicates the local status.
WorkingLinkState
Indicates the status of the working link.
ProtectionLinkState
Indicates the status of the protection link.
Issue 07 (2014-07-30)

26

Log Reference
7 APS
Parameter Name
Parameter Meaning
LocalAPSRequest
Indicates the local APS request.
LocalRequestedSignal
Indicates the flag of local receiving.
LocalBridgedSignal
Indicates the flag of local sending.
FarEndRequest
Indicates the request at the far end.
FarABit
Indicates whether the far end uses APS packets.
FarBBit
Indicates the protection mode at the far end.
FarDBit
Indicates the switching mode at the far end.
FarRBit
Indicates the revertive mode at the far end.
FarEndRequestedSignal
Indicates the flag of receiving at the far end.
FarEndBridgedSignal
Indicates the flag of sending at the far end.
ErrorCode
Possible Causes
The S2750&S5700&S6700 failed to notify the S2750&S5700&S6700 service module to process
the result that was calculated on the APS state machine.
Procedure
----End
7.4 APS/7/STATE_NOTIFY_PPI
Message
APS/7/STATE_NOTIFY_PPI:State changed failed to notify ppi. (EventType=[ULONG],
MoudleID=[ULONG], ProtectionID=[ULONG], WorkingLinkIndex=[ULONG],
ProntectionLinkIndex=[ULONG], HoldoffTime=[ULONG], WTRTime=[ULONG],
FastSndInterval=[ULONG], ProtectionMode=[ULONG], ProtectionDirection=[ULONG],
RevertiveMode=[ULONG], SwitchState=[ULONG], OldGlobalState=[ULONG],
SwitchResult=[ULONG], ProtectionEnableFlag=[ULONG], SwitchCommand=[ULONG],
WorkingLinkState=[ULONG], ProtectionLinkState=[ULONG], ErrorCode=[ULONG])
Description
After finishing status calculation, the APS state machine notified the device to process the result.
If the notification failed, the notified information was recorded for later analysis.
Issue 07 (2014-07-30)

27

Log Reference
7 APS
Parameters
Parameter Name
Parameter Meaning
EventType
MoudleID
GroupIndex
ProtectionType
Indicates the index of the working link.
LocalState
Indicates the index of the protection link.
WorkingLinkState
Indicates the hold-off time.
ProtectionLinkState
Indicates the wait-to-restore time.
LocalAPSRequest
Indicates the interval for fast sending packets.
LocalRequestedSignal
Indicates the protection mode.
LocalBridgedSignal
Indicates the protection direction.
FarEndRequest
Indicates the revertive mode.
FarABit
Indicates the switching status.
FarBBit
Indicates the original priority status.
FarDBit
Indicates the switching result.
FarRBit
Indicates the flag for enabling the protection.
FarEndRequestedSignal
Indicates the command for switching.
FarEndBridgedSignal
Indicates the status of the working link.
ErrorCode
Possible Causes
The S2750&S5700&S6700 failed to notify the device to process the result that was calculated
on the APS state machine.
Procedure
----End
7.5 APS/7/SYN_MES_IO_TO_MAIN
Message
APS/7/SYN_MES_IO_TO_MAIN:IO board synchronization message to main board failed.
(Mid=[ULONG], GroupIndex=[ULONG], SwitchRequest=[ULONG], DefectDirection=
[ULONG], StatusSlot=[STRING], SourceSlot=[STRING], ErrorCode=[ULONG])
Issue 07 (2014-07-30)

28

Log Reference
7 APS
Description
The APS module on the interface board failed to send information to the main control board.
Parameters
Parameter Name
Parameter Meaning
Mid
GroupIndex
SwitchRequest
Indicates the request for switching.
DefectDirection
Indicates the switching direction.
StatusSlot
SourceSlot
Indicates the slot where the information comes from.
ErrorCode
Possible Causes
The APS module on the interface board failed to send information to the main control board.
Procedure
----End
7.6 APS/7/SYN_MES_MAIN_TO_IO
Message
APS/7/SYN_MES_MAIN_TO_IO:Main board synchronization message to IO board failed.
(Mid=[ULONG], GroupIndex=[ULONG], SwitchRequest=[ULONG], DefectDirection=
[ULONG], StatusSlot=[STRING], SourceSlot=[STRING], ErrorCode=[ULONG])
Description
The APS module on the main control board failed to send information to the interface board.
Parameters
Parameter Name
Parameter Meaning
Mid
GroupIndex
SwitchRequest
Indicates the request for switching.
Issue 07 (2014-07-30)

29

Log Reference
7 APS
Parameter Name
Parameter Meaning
DefectDirection
Indicates the switching direction.
StatusSlot
SourceSlot
Indicates the slot where the information comes from.
ErrorCode
Possible Causes
The APS module on the main control board failed to send information to the interface board.
Procedure
----End
Issue 07 (2014-07-30)

30

Log Reference
8 ARP
ARP
About This Chapter

8.1 ARP/6/ARPIGNORETC
8.2 ARP/6/ARP_LOG_CONFIRM
8.3 ARP/4/ARP_LOG_DUPLICATE_IPADDR_DETECT
8.4 ARP/4/ARP_DUPLICATE_IPADDR
8.5 ARP/6/RSTARPALL
8.6 ARP/6/RSTARPSTATIC
Issue 07 (2014-07-30)

31

Log Reference
8 ARP
8.1 ARP/6/ARPIGNORETC
Message
ARP/6/ARPIGNORETC: The user chooses [Y/N] when deciding whether to ignore topology
change.
Description
When deciding whether to ignore the changes of topology, the user chose [Y/N].
Parameters
[Y/N]
Indicates whether to ignore the changes of topology. The value is Yes or

No.
Possible Causes
The arp topology-change disable command was run in the system view, and the user needs to
decide whether to ignore the changes of topology.
Procedure
Step 1 Check whether the ARP entries are updated or not after the topology changed.
----End
8.2 ARP/6/ARP_LOG_CONFIRM
Message
ARP/6/ARP_LOG_CONFIRM:The user chose [Y/N] when deciding whether to execute the
command "[command]".
Description
The system prompted the user to execute a command.
Parameters
[Y/N]
Issue 07 (2014-07-30)
Character that a user enters to determine whether to execute a command

32

Log Reference
8 ARP

[command]
Command line
Possible Causes
After the arp fixup or arp scan command was entered, the system prompted the user to confirm
whether to continue the operation and record the result of the confirmation.
Procedure
Step 1 This log message is a normal situation, and no action is required.
----End
8.3 ARP/4/ARP_LOG_DUPLICATE_IPADDR_DETECT
Message
ARP/4/ARP_LOG_DUPLICATE_IPADDR_DETECT:Detected an IP address collision.
(IpAddress=[IpAddress], LocalMacAddress=[LocalMacAddress], LocalInterfaceName=
[LocalInterfaceName], LocalVlanId=[LocalVlanId], ReceiveMacAddress=
[ReceiveMacAddress], ReceiveInterfaceName=[ReceiveInterfaceName], ReceiveVlanId=
[ReceiveVlanId])
Description
The device detected an IP address conflict.
Parameters
Parameter Name
Parameter Meaning
IpAddress
Conflicting IP addresses
LocalMacAddress
MAC address of the local ARP entry
LocalInterfaceName
Name of the interface recorded in the local ARP entry
LocalVlanId
VLAN ID recorded in the local ARP entry
ReceiveMacAddress
MAC address in the received ARP packet
ReceiveInterfaceName
Name of the interface that has received ARP packet
ReceiveVlanId
VLAN ID that has received ARP packet
Possible Causes
When receiving a non-gratuitous ARP packet, the device found that it had saved the
corresponding ARP entry of the IP address in this ARP packet, but the MAC address in the ARP
entry was different from the source MAC address in the ARP packet.
Issue 07 (2014-07-30)

33

Log Reference
8 ARP
Procedure
Step 1 Change the IP address of a device that conflicts with the other IP address. Then, check whether
this log message is still generated.
l If this log message is still generated, go to Step 3.
l If this log message is not generated, go to Step 4.
Step 2 Contact Huawei technical support personnel.
Step 3 End.
----End
8.4 ARP/4/ARP_DUPLICATE_IPADDR
Message
ARP/4/ARP_DUPLICATE_IPADDR:Received an ARP packet with a duplicate IP address from
the interface. (IpAddress=[IPADDR], InterfaceName=[STRING], MacAddress=[STRING])
Description
Received an ARP packet with a conflictive IP address from the interface.
Parameters
Parameter Name
Parameter Meaning
IpAddress
Indicates the conflicting IP addresses.
InterfaceName
Indicates the name of an interface.
MacAddress
Indicates a MAC address.
Possible Causes
The source IP address of the ARP packet was the same as the IP address of the interface that
received the ARP packet.
Procedure
Step 1 Check whether another interface in the network is configured with the same IP address.
Step 2 Check whether the interface was attacked.
----End
8.5 ARP/6/RSTARPALL
Issue 07 (2014-07-30)

34

Log Reference
8 ARP
Message
ARP/6/RSTARPALL:The user chooses [operation-type] when deciding whether to reset arp all.
Description
Prompts the user to confirm whether to reset all the ARP entries.
Parameters
Parameter Name
Parameter Meaning
[operation-type]
Prompts the user to confirm the action.
Possible Causes
The user confirms the action before running this command.
Procedure
l
This log message indicates a normal situation, and no action is required.
----End
8.6 ARP/6/RSTARPSTATIC
Message
ARP/6/RSTARPSTATIC:The user chooses [operation-type] when deciding whether to reset arp
static.
Description
Prompts the user to confirm whether to reset the static ARP entries.
Parameters
Parameter Name
Parameter Meaning
[operation-type]
Possible Causes
The user confirms the action before running this command.
Issue 07 (2014-07-30)

35

Log Reference
8 ARP
Procedure
----End
Issue 07 (2014-07-30)

36

Log Reference
9 ARPLINK
ARPLINK
About This Chapter

9.1 ARPLINK/6/ARPLINK_DELETE
Issue 07 (2014-07-30)

37

Log Reference
9 ARPLINK
9.1 ARPLINK/6/ARPLINK_DELETE
Message
ARPLINK/6/ARPLINK_DELETE:The IP address of the interface has been changed, and the
ARP link has been deleted. (InterfaceName=[STRING]).
Description
The ARP status-detect function is disabled when the IP address newly assigned to the interface
and the IP address of ARP status-detect are in different network segments, or the IP addresses
are the same.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
Possible Causes
1. Enable the ARP status-detect function and assign an IP address to an interface. Then assign
a new IP address to the interface. If you find that the ARP status-detect function is disabled,
possible causes are as follows:
(1) The IP address newly assigned to the interface and the IP address of ARP status-detect are
in different network segment.
the same.
2. Enable the ARP status-detect function on an interface, and then assign an IP address to the
interface. If you find that the ARP status-detect function is disabled, possible causes are as
follows:
(1) The IP address newly assigned to the interface and the IP address of ARP status-detect is in
different network segments.
the same.
Procedure
Step 1 The IP address of ARP status-detect is the IP address of the interface on a directly connected
device or on a device that is connected through a switch.
1.
Issue 07 (2014-07-30)
If the IP address newly assigned to the interface and the IP address of ARP status-detect
are in different network segments, check whether the IP address of the remote interface is
newly assigned, and whether the status of the remote interface need be detected any more.
If the status of the remote interface need be detected, reconfigure the ARP status-detect
38

Log Reference
9 ARPLINK
function; if the status of the remote interface need not be detected, no configuration is
needed.
2.
If the IP address newly assigned to the interface and the IP address of ARP status-detect
are the same, check whether the subnet mask of the newly assigned IP address is changed.
Then check whether the IP address of the remote interface is newly assigned, and whether
the status of the remote interface need be detected any more. If the status of the remote
interface need be detected, reconfigure the ARP status-detect function; if the status of the
remote interface need not be detected, no configuration is needed.
----End
Issue 07 (2014-07-30)

39

Log Reference
10 ASSISTANT
10
ASSISTANT
About This Chapter

10.1 ASSISTANT/6/ASSISTANTSCHEDULE
10.2 ASSISTANT/4/JOB_DEL_CONFIRM
Issue 07 (2014-07-30)

40

Log Reference
10 ASSISTANT
10.1 ASSISTANT/6/ASSISTANTSCHEDULE
Message
ASSISTANT/6/ASSISTANTSCHEDULE: To record assistant schedule information.
(TaskName=[STRING], Action=[STRING], Result="[STRING]")
Description
The scheduling information of the maintenance assistant task was recorded.
Parameters
Parameter Name
Parameter Meaning
TaskName
Name of the maintenance assistant task
Action
Operation type of the maintenance assistant task
Result
Operation result of the maintenance assistant task
Possible Causes
After the maintenance assistant task was configured, the system recorded the task scheduling
information.
Procedure
Step 1 This log is informational only, and no action is required.
----End
10.2 ASSISTANT/4/JOB_DEL_CONFIRM
Message
ASSISTANT/4/JOB_DEL_CONFIRM: When deciding whether to delete the assistant task
[TaskName], the user chose [UserChoose].
Description
When a user decided whether to delete a maintenance assistant task, the user's choice was
recorded.
Issue 07 (2014-07-30)

41

Log Reference
10 ASSISTANT
Parameters
Parameter Name
Parameter Meaning
[TaskName]
Name of the maintenance assistant task to be deleted
[UserChoose]
User's choice. The value is Y or N.
Possible Causes
When a user decided whether to delete a maintenance assistant task, the system recorded the
user's choice.
Procedure
----End
Issue 07 (2014-07-30)

42

Log Reference
11 BFD
11
BFD
About This Chapter

11.1 BFD/3/ACLRUNOUT
11.2 BFD/3/ADDFSM_ERR
11.3 BFD/3/ADDRCV_ERR
11.4 BFD/4/BOARDTYPEERR
11.5 BFD/4/CANTFINDBFDENTRY
11.6 BFD/6/CREATE_SESS_ERR
11.7 BFD/6/CRTSESS
11.8 BFD/3/DELFSM_ERR
11.9 BFD/3/DELRCV_ERR
11.10 BFD/3/DELRCV_ERR_ADD
11.11 BFD/5/DELSESS
11.12 BFD/3/DELSESS_SYS
11.13 BFD/4/FPGAENTRYERR
11.14 BFD/4/GETBOARDFAIL
11.15 BFD/4/GETPWINFOFAIL
11.16 BFD/4/IO_REACH_SESSLMT
11.17 BFD/3/IPCALLOCFAIL
11.18 BFD/3/IPCSENDFAIL
11.19 BFD/4/LABELALLOCFAIL
11.20 BFD/4/LABELFREEFAIL
Issue 07 (2014-07-30)

43

Log Reference
11 BFD
11.21 BFD/3/MEMORYALLOCFAIL
11.22 BFD/4/REACH_IF_LIM
11.23 BFD/3/REALTIME_CFG_ERR
11.24 BFD/4/STACHG_DWNTOUP
11.25 BFD/4/STACHG_TODWN
11.26 BFD/4/STACHG_TOUP
11.27 BFD/4/TCAMALLOCFAIL
11.28 BFD/4/TCAMFREEFAIL
11.29 BFD/4/UNKNOWNPDT
11.30 BFD/4/UPDATEACLFAIL
11.31 BFD/4/UPDATEFWDFAIL
Issue 07 (2014-07-30)

44

Log Reference
11 BFD
11.1 BFD/3/ACLRUNOUT
Message
BFD/3/ACLRUNOUT:IO board([ULONG]) is run out of ACL(Error Code:[ULONG])
Description
The ACL rules on the interface board are used up.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the slot ID of the interface board.
[ULONG]
Indicates the error code.
Possible Causes
The ACL rules on the interface board are used up.
Procedure
----End
11.2 BFD/3/ADDFSM_ERR
Message
BFD/3/ADDFSM_ERR:Slot failed to add session status machine table! (SlotNumber=
[STRING], Discriminator=[ULONG])
Description
Failed to add a state machine entry of a session.
Parameters
Parameter Name
Parameter Meaning
SlotNumber
indicates the number of an interface board.
Discriminator
indicates the discriminator of a session.
Issue 07 (2014-07-30)

45

Log Reference
11 BFD
Possible Causes
Adding a state machine entry of a session failed.
Procedure
Step 1 Check the session configuration and session information. Then, try setting up a session again.
----End
11.3 BFD/3/ADDRCV_ERR
Message
BFD/3/ADDRCV_ERR:Slot failed to add session receival table! (SlotNumber=[STRING],
Discriminator=[ULONG])
Description
Failed to add a session receiving entry.
Parameters
Parameter Name
Parameter Meaning
SlotNumber
Discriminator
Possible Causes
Adding a receiving session entry failed.
Procedure
----End
11.4 BFD/4/BOARDTYPEERR
Message
BFD/4/BOARDTYPEERR:IO board([ULONG]) does not support BFD(Discriminator
[ULONG]) type([ULONG])!
Issue 07 (2014-07-30)

46

Log Reference
11 BFD
Description
The interface board does not support BFD of this type.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
[ULONG]
Indicates the BFD session identifier.
[ULONG]
Indicates the BFD type ID.
Possible Causes
The interface board does not support BFD of this type.
Procedure
Step 1 Ensure that the interface board has registered.
Step 2 Check whether the interface board supports this BFD type.
l If the interface board does not support this BFD type, replace the interface board.
----End
11.5 BFD/4/CANTFINDBFDENTRY
Message
BFD/4/CANTFINDBFDENTRY:Can't find BFD(Discriminator[ULONG]) session entry!
Description
The BFD session entry cannot be found.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The BFD session entry cannot be found.
Procedure
Step 1
Issue 07 (2014-07-30)

47

Log Reference
11 BFD
Check whether the BFD session exists.

----End
11.6 BFD/6/CREATE_SESS_ERR
Message
BFD/6/CREATE_SESS_ERR:Failed to create BFD session. It will be created again later.
(ConfigurationName=[STRING])
Description
Failed to create a BFD session and it would be re-created later.
Parameters
Parameter Name
Parameter Meaning
ConfigurationName
indicates the configuration name of the BFD session.
Possible Causes
An error occurs during the setup of the BFD session. The possible causes are as follows:
1. Failed to choose a master process board.
2. The number of BFD sessions reached the upper limit specified in the PAF.
Procedure
Step 1 Run the display bfd session command to check whether the BFD session is created.
(1) If so, go to Step 5.
(2) If not, go to Step 2.
Step 2 Run the display bfd statistics command to check whether the number of BFD sessions reaches
the upper limit.
(1) If so, delete redundant BFD sessions.
Step 3 Run the display device command to check the type of the interface board and check whether
the board supports BFD.
(1) If yes, go to Step 4.
(2) If not, replace an interface board that supports BFD.
Issue 07 (2014-07-30)

48

Log Reference
11 BFD
Step 5 End.
----End
11.7 BFD/6/CRTSESS
Message
BFD/6/CRTSESS:The BFD session has been created successfully. (Discriminator=[ULONG],
ConfigurationName=[STRING], Applications=[STRING], PeerIp=[STRING], SessionType=
[STRING], BindIFName=[STRING], BindVpnName=[STRING], SourceIp=[STRING])
Description
A BFD session was successfully created.
Parameters
Parameter Name
Parameter Meaning
Discriminator
Local discriminator
ConfigurationName
Configuration name
Applications
Application bound to a BFD session
PeerIp
Destination IP address
SessionType
Type of a BFD session
BindIFName
Name of an interface bound to a BFD session
BindVpnName
Name of a VPN instance bound to a BFD session
SourceIp
Source IP address
Possible Causes
A BFD session was successfully created.
Procedure
----End
Issue 07 (2014-07-30)

49

Log Reference
11 BFD
11.8 BFD/3/DELFSM_ERR
Message
BFD/3/DELFSM_ERR:Slot failed to delete session status machine table! (SlotNumber=
[STRING], Discriminator=[ULONG])
Description
Failed to delete a state machine entry of a session.
Parameters
Parameter Name
Parameter Meaning
SlotNumber
Discriminator
Possible Causes
Deletion of a session state machine entry failed.
Procedure
Step 1 Check the session configuration and session information. Then, try deleting the session again.
----End
11.9 BFD/3/DELRCV_ERR
Message
BFD/3/DELRCV_ERR:Slot failed to delete session receival entry! (SlotNumber=[STRING],
Discriminator=[ULONG])
Description
Failed to delete the receiving session entry.
Issue 07 (2014-07-30)

50

Log Reference
11 BFD
Parameters
Parameter Name
Parameter Meaning
SlotNumber
Discriminator
Possible Causes
The action of deleting the receiving session entry failed.
Procedure
Step 1 Check the session configuration and session information. Then, try deleting the session again.
----End
11.10 BFD/3/DELRCV_ERR_ADD
Message
BFD/3/DELRCV_ERR_ADD:Slot failed to delete session receival entry when adding session!
(SlotNumber=[STRING], Discriminator=[ULONG])
Description
Failed to delete a receiving session entry when adding a session.
Parameters
Parameter Name
Parameter Meaning
SlotNumber
Discriminator
Possible Causes
The action of deleting the receiving session entry failed.
Procedure
----End
Issue 07 (2014-07-30)

51

Log Reference
11 BFD
11.11 BFD/5/DELSESS
Message
BFD/5/DELSESS:The BFD session was deleted. (Discriminator=[ULONG], Result=
[STRING], Applications=[STRING], BindIFName=[STRING], SourceIp=[STRING], PeerIp=
[STRING])
Description
A BFD session was deleted.
Parameters
Parameter Name
Parameter Meaning
Discriminator
Local discriminator of a session
Result
Whether a BFD session is deleted:

l Succeeded
l Failed
Applications
Application bound to a BFD session
BindIFName
Name of an interface bound to a BFD session
SourceIp
Source IP address
PeerIp
Destination IP address
Possible Causes
Procedure
----End
11.12 BFD/3/DELSESS_SYS
Issue 07 (2014-07-30)

52

Log Reference
11 BFD
Message
BFD/3/DELSESS_SYS:BFD session is deleted because of [delete-reason].(Discriminator=
[ULONG])
Description
Parameters
Parameter Name
Parameter Meaning
[delete-reason]
Cause for deletion
Discriminator
Local discriminator of the BFD session
Possible Causes
A BFD session is deleted.
Procedure
Step 1 This log information is informational only, and no action is required.
----End
11.13 BFD/4/FPGAENTRYERR
Message
BFD/4/FPGAENTRYERR:FPGA entry error! Discriminator: [ULONG]!
Description
An error occurs in FPGA entries.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
An error occurs in FPGA entries.
Issue 07 (2014-07-30)

53

Log Reference
11 BFD
Procedure
----End
11.14 BFD/4/GETBOARDFAIL
Message
BFD/4/GETBOARDFAIL:Failed to get process board of BFD(Discriminator[ULONG])!
Description
The main control board fails to obtain the BFD session.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The main control board fails to obtain the BFD session.
Procedure
----End
11.15 BFD/4/GETPWINFOFAIL
Message
BFD/4/GETPWINFOFAIL:Failed to get PW information by AC IfIndex
([ULONG]),discriminator of BFD is [ULONG]!
Description
The main control board fails to obtain PW information according to AC interface indexes.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the AC interface index.
Issue 07 (2014-07-30)

54

Log Reference
11 BFD
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The main control board fails to obtain PW information according to AC interface indexes.
Procedure
Step 1
Contact Huawei technical personnel.
----End
11.16 BFD/4/IO_REACH_SESSLMT
Message
BFD/4/IO_REACH_SESSLMT:The number of sessions on the slot had reached upper limit,
new session bound on this interface board could not be created! (SlotNumber=[STRING])
Description
The number of sessions bound to an interface reached the upper limit. No more sessions bound
to the interface can be created.
Parameters
Parameter Name
Parameter Meaning
SlotNumber
Possible Causes
The number of sessions bound to an interface reached the upper limit. No more sessions bound
to the interface can be created.
Procedure
Step 1 Do not create more sessions bound to the interface on the interface board. Alternatively, delete
some useless sessions bound to the interface on the interface board.
----End
Issue 07 (2014-07-30)

55

Log Reference
11 BFD
11.17 BFD/3/IPCALLOCFAIL
Message
BFD/3/IPCALLOCFAIL:Failed to allocate IPC memory!
Description
IPC memory allocation failed.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
IPC memory allocation failed.
Procedure
Step 1
----End
11.18 BFD/3/IPCSENDFAIL
Message
BFD/3/IPCSENDFAIL:Failed to send IPC message to IO board([ULONG])(Error Code:
[ULONG])!
Description
The main control board failed to send IPC messages to the interface board.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
[ULONG]
Issue 07 (2014-07-30)

56

Log Reference
11 BFD
Possible Causes
The main control board failed to send IPC messages to the interface board.
Procedure
Step 2 View the IPC-related logs to check whether an IPC message sending failure log is recorded on
the interface board. If the log exists on the interface board, contact the Huawei technical
personnel.
----End
11.19 BFD/4/LABELALLOCFAIL
Message
BFD/4/LABELALLOCFAIL:Failed to allocate reserved label(BFD discriminator[ULONG])!
Description
Reserved label allocation failed.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
Reserved label allocation failed.
Procedure
Step 1
----End
11.20 BFD/4/LABELFREEFAIL
Message
BFD/4/LABELFREEFAIL:Failed to free reserved label(BFD discriminator[ULONG]),label is
[ULONG]!
Issue 07 (2014-07-30)

57

Log Reference
11 BFD
Description
Failed to release the reserved labels.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
[ULONG]
Indicates the label ID.
Possible Causes
Failed to release the reserved labels.
Procedure
Step 1
----End
11.21 BFD/3/MEMORYALLOCFAIL
Message
BFD/3/MEMORYALLOCFAIL:Failed to allocate memory when process [STRING]
Description
Memory allocation failed.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the task name.
Possible Causes
Procedure
Step 1
----End
Issue 07 (2014-07-30)

58

Log Reference
11 BFD
11.22 BFD/4/REACH_IF_LIM
Message
BFD/4/REACH_IF_LIM:The number of the interfaces bound with the session had reached the
upper limit set in the PAF/License file!
Description
The number of the interfaces bound to the session reached the upper limit set in the PAF or
license file.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The number of BFD sessions configured on the LPU reached the upper limit.
Procedure
----End
11.23 BFD/3/REALTIME_CFG_ERR
Message
BFD/3/REALTIME_CFG_ERR:Failed to backup the configuration entry in realtime!
(BfdName=[STRING], ErrorCode=[ULONG])
Description
Failed to back up configuration entries in real time. (Error codes: The value 0 is returned when
configuration entries are backed up successfully; error types are returned when configuration
entries are backed up unsuccessfully.)
Issue 07 (2014-07-30)

59

Log Reference
11 BFD
Parameters
Parameter Name
Parameter Meaning
BfdName
indicates the configuration name of a BFD session.
ErrorCode
indicates an error code.
Possible Causes
Failed to back up configuration entries in real time.
Procedure
----End
11.24 BFD/4/STACHG_DWNTOUP
Message
BFD/4/STACHG_DWNTOUP:BFD session changed from Down to Up. (SlotNumber=
[STRING], Discriminator=[ULONG], Applications=[STRING], BindInterfaceName=
[STRING], ProcessPST=[STRING])
Description
Configured a WTR timer and the status of a BFD session on a certain interface board changed
from Down to Up.
Parameters
SlotNumber
indicates the slot number of the interface board on which the status of a
BFD session changed.
Discriminator
indicates the discriminator of a session of which the status changes.
Applications
indicates the application that is bound to the BFD session.
BindInterfaceName indicates the name of the bound interface.

ProcessPST
Issue 07 (2014-07-30)
indicates the flag bit of the PST that is modified.

60

Log Reference
11 BFD
Possible Causes
A session was set up through negotiation between both ends.
Procedure
Step 1 The log message is informative only, and no action is required.
----End
11.25 BFD/4/STACHG_TODWN
Message
BFD/4/STACHG_TODWN:BFD session changed to Down. (SlotNumber=[STRING],
Discriminator=[ULONG], Diagnostic=[STRING], Applications=[STRING], ProcessPST=
[STRING], BindInterfaceName=[STRING], InterfacePhysicalState=[STRING],
InterfaceProtocolState=[STRING])
Description
The status of a BFD session on an interface board changed to Down.
Parameters
Parameter Name
Parameter Meaning
SlotNumber
indicates the slot number of an interface board.
Discriminator
Diagnostic
Indicates the type of the Down state. The values are as follows:
l AdminDown: The local end proactively enters the AdminDown
state.
l ReceiveAdminDown: The local end enters the Down state after
receiving a BFD packet with the AdminDown state from the remote
end.
l DetectDown: The local end enters the Down state when the
detection expires because it does not receive BFD packets from the
remote end.
l NeighborDown: The local end enters the Down state after
receiving a BFD packet with the Down state from the remote end.
Applications
ProcessPST
Issue 07 (2014-07-30)

61

Log Reference
Parameter Name
Parameter Meaning
BindInterfaceName
indicates the name of the bound interface.
11 BFD
InterfacePhysicalState indicates the physical status of the interface.

InterfaceProtocolState indicates the protocol status of the interface.
Possible Causes
The BFD session was Down because a BFD session on an interface board did not receive
corresponding BFD packets within a detection period.
Procedure
Step 1 Run the display bfd session all command to check whether the BFD session status is restored
automatically.
Step 2 Run the display current-configuration configuration bfd command to check whether one end of
the link is not enabled with BFD.
(1) If BFD is disabled, enable BFD and then go to Step 1.
(2) If BFD is enabled, go to Step 3.
Step 3 Run the display bfd session all command on both ends to check whether the BFD session is
deleted.
Step 4 Run the ping ip-addr command to check whether the link detected by the BFD session fails to
forward traffic.
Step 6 End.
----End
11.26 BFD/4/STACHG_TOUP
Issue 07 (2014-07-30)

62

Log Reference
11 BFD
Message
BFD/4/STACHG_TOUP:BFD session changed to Up. (SlotNumber=[STRING],
Discriminator=[ULONG], FormerStatus=[STRING], Applications=[STRING],
BindInterfaceName=[STRING], ProcessPST=[STRING])
Description
The status of a BFD session on an interface board changed from other status (AdminDown,
Down, or Init) to Up.
Parameters
SlotNumber
indicates the slot number of the interface board on which the status of a
BFD session changed.
Discriminator
indicates the discriminator of a session of which the status changes.
FormerStatus
indicates other status. The value can be AdminDown, Down, or Init.
Applications
BindInterfaceName indicates the name of the bound interface.

ProcessPST
Possible Causes
A session was set up through negotiation between both ends.
Procedure
Step 1 The log message is informative only, and no action is required.
----End
11.27 BFD/4/TCAMALLOCFAIL
Message
BFD/4/TCAMALLOCFAIL:Failed to allocate TCAM resource(BFD discriminator[ULONG])!
Description
TCAM resource allocation failed.
Issue 07 (2014-07-30)

63

Log Reference
11 BFD
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
TCAM resource allocation failed.
Procedure
Step 1
----End
11.28 BFD/4/TCAMFREEFAIL
Message
BFD/4/TCAMFREEFAIL:Failed to free TCAM resource(BFD discriminator
[ULONG]),TCAM index is [ULONG]!
Description
TCAM resource release failed.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
[ULONG]
Indicates the TCAM index.
Possible Causes
TCAM resource release failed.
Procedure
Step 1
----End
Issue 07 (2014-07-30)

64

Log Reference
11 BFD
11.29 BFD/4/UNKNOWNPDT
Message
BFD/4/UNKNOWNPDT:Unknown product type
Description
The board type cannot be identified.
Parameters
Parameter Name
Parameter Meaning
None
Possible Causes
The board type cannot be identified.
Procedure
Step 1
----End
11.30 BFD/4/UPDATEACLFAIL
Message
BFD/4/UPDATEACLFAIL:Failed to update ACL rules! Discriminator of BFD is [ULONG]!
Description
ACL rule update failed.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
ACL rule update failed.
Issue 07 (2014-07-30)

65

Log Reference
11 BFD
Procedure
----End
11.31 BFD/4/UPDATEFWDFAIL
Message
BFD/4/UPDATEFWDFAIL:Failed to update forward information, type of BFD is [ULONG],
discriminator of BFD is [ULONG].
Description
Failed to update forwarding information.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the BFD type.
[ULONG]
Possible Causes
Failed to update forwarding information.
Procedure
Step 1
----End
Issue 07 (2014-07-30)

66

Log Reference
12 BGP
12
BGP
About This Chapter

12.1 BGP/4/ASPATH_EXCEED_MAXNUM
12.2 BGP/4/CANNOT_FIND_PEER
12.3 BGP/6/CONFIRM_N
12.4 BGP/6/CONFIRM_TIMEOUT
12.5 BGP/6/CONFIRM_Y
12.6 BGP/6/GR_NOTIFY_ENTER
12.7 BGP/6/GR_NOTIFY_EXIT
12.8 BGP/6/INST_EXIT_GR
12.9 BGP/4/IPV4_ROUTE_LCS_EXC
12.10 BGP/4/IPV6_ROUTE_LCS_EXCD
12.11 BGP/3/MEMORY_RESTORE
12.12 BGP/6/RECV_NOTIFY
12.13 BGP/3/RECV_UNSPT_AFI
12.14 BGP/4/ROUTEADD_REACHLMT
12.15 BGP/4/ROUTPRIX_EXCEED
12.16 BGP/3/ROUTTHRD_REACHED
12.17 BGP/6/SEND_NOTIFY
12.18 BGP/6/SNMP_PEER_SHUTDOWN
12.19 BGP/4/BGP_SPEC_RT_EXCD
12.20 BGP/3/STATE_CHG_UPDOWN
Issue 07 (2014-07-30)

67

Log Reference
12 BGP
12.21 BGP/4/UNKNOWN_TYPE
Issue 07 (2014-07-30)

68

Log Reference
12 BGP
12.1 BGP/4/ASPATH_EXCEED_MAXNUM
Message
BGP/4/ASPATH_EXCEED_MAXNUM:The number of AS-PATHs exceeded the limit([limitvalue]). (Operation=[STRING])
Description
The number of AS-Paths exceeded the maximum value.
Parameters
[limit-value]
Indicates the maximum number of AS-Paths.
Operation
Indicates related operations, including discarding routes, failing to make

a policy effective, and failing to use the aggregation command.
l Discarding routes: The NLRI will be treated as Withdraw.
l Using the aggreation command without as-set: It will aggregate
without as-set.
l Failing to make a policy effective: The policy will not work.
Possible Causes
The number of AS numbers exceeded the maximum value in the AS-Path list.
Procedure
----End
12.2 BGP/4/CANNOT_FIND_PEER
Message
BGP/4/CANNOT_FIND_PEER:When the system backed up the GR capability, BGP could not
find the peer [STRING]. (AFI=[USHORT], SAFI=[USHORT])
Description
When the system backed up the GR capability, BGP could not find the peer.
Issue 07 (2014-07-30)

69

Log Reference
12 BGP
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the IP address of the peer.
AFI
Indicates the address family identifier (AFI) of the peer.
SAFI
Indicates the sub-address family identifier (SAFI) of the peer.
Possible Causes
Configurations on the AMB and the SMB were inconsistent.
Procedure
Step 1 Restart the SMB by using the configuration file as same as that of the AMB.
----End
12.3 BGP/6/CONFIRM_N
Message
BGP/6/CONFIRM_N:A user input "No" to reject the operation.
Description
When a specific operation needed to be confirmed, a user entered N to cancel the operation.
Parameters
None.
Possible Causes
Changing configurations about BGP connections requires to reset BGP sessions. Therefore,
users need to confirm the action, and users input N to cancel the operation.
Procedure
----End
12.4 BGP/6/CONFIRM_TIMEOUT
Issue 07 (2014-07-30)

70

Log Reference
12 BGP
Message
BGP/6/CONFIRM_TIMEOUT:When a user did not input any word in [timeout-time]s, the
system exited from the operation automatically.
Description
The system automatically quitted the operation because a user input nothing within the maximum
number of seconds specified by user to confirm the operation.
Parameters
[timeout-time]
Indicates the maximum number of seconds taken by a user to confirm the

operation.
Possible Causes
When BGP configurations related to connections changed, re-connection was required and a
user need input confirmation information. If the user did not input Y or N within the specified
period of time, the system quitted the confirmation and did not proceed with the operation by
default.
Procedure
----End
12.5 BGP/6/CONFIRM_Y
Message
BGP/6/CONFIRM_Y:A user input "Yes" to confirm the operation.
Description
When a specific operation needed to be confirmed, a user entered Y to proceed with the operation.
Parameters
None.
Possible Causes
Changing configurations about BGP connections requires to reset BGP sessions. Therefore,
users need to confirm the action, and users input Y to perform the operation.
Issue 07 (2014-07-30)

71

Log Reference
12 BGP
Procedure
----End
12.6 BGP/6/GR_NOTIFY_ENTER
Message
BGP/6/GR_NOTIFY_ENTER:BGP entered the GR status.
Description
BGP entered the GR status.
Parameters
None.
Possible Causes
BGP entered the GR status.
Procedure
----End
12.7 BGP/6/GR_NOTIFY_EXIT
Message
BGP/6/GR_NOTIFY_EXIT:BGP exited from the GR status.
Description
BGP exited from the GR state.
Parameters
None.
Possible Causes
BGP exited from the GR state.
Issue 07 (2014-07-30)

72

Log Reference
12 BGP
Procedure
----End
12.8 BGP/6/INST_EXIT_GR
Message
BGP/6/INST_EXIT_GR:The BGP instance [vpn-instance] exited from GR and notified the RM.
Description
The BGP instance exited from GR and notified the event to RM.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
Indicates a VPN instance.
Possible Causes
This was a normal GR process and was triggered when a BGP instance exited from GR.
Procedure
----End
12.9 BGP/4/IPV4_ROUTE_LCS_EXC
Message
BGP/4/IPV4_ROUTE_LCS_EXC:The number of IPv4 routes reached the maximum value
[max-route-value] defined in the License file.
Description
The number of IPv4 routes exceeded the maximum value defined by the license file.
Issue 07 (2014-07-30)

73

Log Reference
12 BGP
Parameters
Parameter Name
Parameter Meaning
[max-route-value]
Indicates the maximum of IPv4 routes defined in the license file.
Possible Causes
The number of IPv4 routes exceeded the maximum value defined by the license file.
Procedure
Step 1 Check the topology and the configuration of the network, and check whether excessive routes
are caused by the requirements of actual applications or incorrect topology configuration.
Step 2 If the excessive routes are caused by the requirements of actual applications, expand the license.
----End
12.10 BGP/4/IPV6_ROUTE_LCS_EXCD
Message
BGP/4/IPV6_ROUTE_LCS_EXCD:The number of IPv6 routes reached the maximum value
[max-route-value] defined in the License file.
Description
The number of IPv6 routes reached the maximum value defined in the license.
Parameters
[max-route-value] Indicates the maximum number of IPv4 routes defined in the license file.
Possible Causes
The number of IPv6 routes reached the maximum value defined in the license.
Procedure
Step 2 If the excessive routes are caused by the requirements of actual applications, expand the license.
----End
Issue 07 (2014-07-30)

74

Log Reference
12 BGP
12.11 BGP/3/MEMORY_RESTORE
Message
BGP/3/MEMORY_RESTORE:The message that memory was restored was received from the
RM.
Description
The message that memory was restored was received from RM.
Parameters
None.
Possible Causes
The memory usage of the router changed from the memory shortage status to the value below
the threshold.
Procedure
----End
12.12 BGP/6/RECV_NOTIFY
Message
BGP/6/RECV_NOTIFY:The router received NOTIFICATION message from peer [neighboraddress]. (ErrorCode=[ULONG], SubErrorCode=[ULONG], BgpAddressFamily=[STRING],
ErrorData=[STRING])
Description
The router received a Notification message from the BGP peer.
Parameters
[neighbor-address] Indicates the IP address of a neighboring router.
ErrorCode
Indicates the error code carried in a Notification message.
SubErrorCode
Indicates the error subcode carried in a Notification message.
Issue 07 (2014-07-30)

75

Log Reference
12 BGP

BgpAddressFamily Indicates the flag of a BGP address family. The flags are divided into
public flags and VPN flags.
ErrorData
Indicates the summary of error data carried in Notification messages.
Possible Causes
The router received a Notification message containing information about error codes and error
subcodes from the BGP peer.
Procedure
Step 1 Find out the reason why the BGP peer connection is torn down and check whether the reset bgp
command is used.
Step 2 Refer to BGP Error Code for the description of error codes and error subcodes, and possible
causes.
Step 3 Contact the Huawei technical personnel.
----End
12.13 BGP/3/RECV_UNSPT_AFI
Message
BGP/3/RECV_UNSPT_AFI:The UPDATE message received from peer [peer-address]
contained unknown address family [address-family-attribute] in path attribute of multi-protocol
unreachable network layer reachable information.
Description
MP_REACH_NLRI in an Update message received from a BGP peer contained an unknown
address family attribute.
Parameters
Parameter Name
Parameter Meaning
[peer-address]
IP address of a peer
[address-family-attribute]
Address family attribute value
Possible Causes
MP_REACH_NLRI in an Update message received from a BGP peer contained an unknown
address family attribute.
Issue 07 (2014-07-30)

76

Log Reference
12 BGP
Procedure
Step 1 Check whether the communication devices are of different vendors and whether the function
ranges of the devices are the same.
----End
12.14 BGP/4/ROUTEADD_REACHLMT
Message
BGP/4/ROUTEADD_REACHLMT:Failed to update the route in the [flag] instance because the
number of routes reached the maximum.(InstanceId=[USHORT], AFI=[USHORT], SAFI=
[USHORT])
Description
Failed to update the routes in the instance because the number of routes reached the maximum
value.
Parameters
Parameter Name
Parameter Meaning
flag
Flag of a BGP address family: public or VPN
InstanceId
Instance ID
AFI
Address family information (AFI)
SAFI
Sub-address family information (SAFI)
Possible Causes
Failed to add BGP routes to the routing table because the number of routes in the routing table
exceeded the maximum value.
Procedure
Step 2 If the excessive routes are caused by the requirements of actual applications, extend the license.
----End
12.15 BGP/4/ROUTPRIX_EXCEED
Issue 07 (2014-07-30)

77

Log Reference
12 BGP
Message
BGP/4/ROUTPRIX_EXCEED:Routes received from peer [neighbor-address] including the
number of prefix [receive-prefix-number] exceeded the max number of prefix [max-prefixnumber]. (BgpAddressFamily=[STRING])
Description
The number of prefixes received from a peer exceeded the maximum value.
Parameters
Parameter Name
Parameter Meaning
[neighbor-address]
Indicates the IP address of a neighboring router.
[receive-prefix-number] Indicates the number of prefixes received from the neighboring

router.
[max-prefix-number]
Indicates the maximum number of IP prefixes.
BgpAddressFamily
Indicates the flag of a BGP address family. The flags are divided into
Possible Causes
The number of routes received from a peer exceeded the maximum value.
Procedure
Step 2 If excessive routes are caused by the requirements of actual applications, modify the
configuration of the peer route-limit command.
----End
12.16 BGP/3/ROUTTHRD_REACHED
Message
BGP/3/ROUTTHRD_REACHED:The number of routes received from peer [neighbor-address]
reached route threshold value [threshold-value]. (BgpAddressFamily=[STRING],
CurrentRouteNumber=[ULONG], MaxRouteNumber=[ULONG])
Description
The number of routes received by a neighboring router exceeded the set threshold.
Issue 07 (2014-07-30)

78

Log Reference
12 BGP
Parameters
Parameter Name
Parameter Meaning
[neighbor-address]
Indicates the IP address of a neighboring router.
[threshold-value]
Indicates the threshold of the number of routes.
BgpAddressFamily
Indicates a BGP address family.
CurrentRouteNumber
Indicates the number of current routes.
MaxRouteNumber
Indicates the maximum number of routes.
Possible Causes
The number of routes received by a neighboring router exceeded the set threshold.
Procedure
Step 2 If excessive routes are caused by the requirements of actual applications, modify the peer routelimit.
----End
12.17 BGP/6/SEND_NOTIFY
Message
BGP/6/SEND_NOTIFY:The router sent a NOTIFICATION message to peer [peer-address].
(ErrorCode=[ULONG], SubErrorCode=[ULONG], BgpAddressFamily=[STRING],
ErrorData=[STRING])
Description
The router sent a Notification message to the BGP peer.
Parameters
[peer-address]
Indicates the IP address of a BGP peer.
ErrorCode
Indicates the error code carried in a sent message.
SubErrorCode
Indicates the value of an error subcode.
BgpAddressFamily Indicates the flag of a BGP address family. The flags are divided into
Issue 07 (2014-07-30)

79

Log Reference
12 BGP

ErrorData
indicates the summary of error data carried in a sent packet.
Possible Causes
The router sent a Notification message that contained information about error codes and error
subcodes to the BGP peer.
Procedure
Step 1 Find out the reason why the BGP peer connection is torn down and check whether the reset
bgp command is used.
Step 2 Refer to BGP Error Code for the description of error codes and error subcodes, and possible
causes.
----End
12.18 BGP/6/SNMP_PEER_SHUTDOWN
Message
BGP/6/SNMP_PEER_SHUTDOWN:An SNMP command was received to suspend the peer
session for [peer-address]. (InstanceName:[STRING])
Description
BGP received an SNMP command to suspend the peer session.
Parameters
Parameter Name
Parameter Meaning
[peer-address]
Indicates the IP address of a peer.
InstanceName
Indicates the name of a BGP instance.
Possible Causes
Set a Stop operation by using the MIB software to interrupt the connection.
Procedure
----End
Issue 07 (2014-07-30)

80

Log Reference
12 BGP
12.19 BGP/4/BGP_SPEC_RT_EXCD
Message
BGP/4/BGP_SPEC_RT_EXCD:The number of BGP [route-type] routes reached the maximum
value [max-route-value].
Description
The number of a specific type of BGP routes reached the maximum.
Parameters
Parameter Name
Parameter Meaning
[route-type]
Type of a route, for example, BGP L2VPN-AD
[max-route-value]
Maximum number of routes
Possible Causes
The number of a specific type of BGP routes reached the maximum. For example, the number
of L2VPN-AD routes reached the maximum.
Procedure
Step 1 Check the topology and the configuration of the network to see whether excess routes are
required based on actual applications or caused by the incorrect topology configuration.
Step 2 If excess routes are required based on actual applications, contact Huawei technical support
personnel for capacity expansion.
----End
12.20 BGP/3/STATE_CHG_UPDOWN
Message
BGP/3/STATE_CHG_UPDOWN:The status of the peer [peer-address] changed from
[previous-state] to [current-state]. (InstanceName=[STRING], StateChangeReason=
[STRING])
Description
The status of the peer changed.
Issue 07 (2014-07-30)

81

Log Reference
12 BGP
Parameters
Parameter Name
Parameter Meaning
[peer-address]
Address of a BGP peer
[previous-state]
Previous status
[current-state]
Current status
InstanceName
Instance name
StateChangeReason
Cause of the status change
Possible Causes
The status of the BGP connection changed.
Procedure
----End
12.21 BGP/4/UNKNOWN_TYPE
Message
BGP/4/UNKNOWN_TYPE:Type of the backup data was unknown. (ID=[USHORT], Length=
[USHORT])
Description
The backup data of the AMB cannot be identified on the SMB.
Parameters
Parameter Name
Parameter Meaning
ID
Indicates the ID of the backup data.
Length
Indicates the length of the backup data.
Possible Causes
The versions of the AMB and SMB were inconsistent.
Issue 07 (2014-07-30)

82

Log Reference
12 BGP
Procedure
Step 1 Restart the SMB by using the version as same as that of the AMB.
----End
Issue 07 (2014-07-30)

83

Log Reference
13 CFM
13
CFM
About This Chapter

13.1 CFM/4/B2S_BACKUP_FAILED
13.2 CFM/4/CFM_INCONSISTENT_FILE_IMG
13.3 CFM/4/CFM_INCONSISTENT_FILE_CFG
13.4 CFM/6/CFM_OVERWRITESOFTWARE
13.5 CFM/4/CFM_SYNCFGFILEFAIL
13.6 CFM/6/CFM_UNDO_SCHEDULE_NO
13.7 CFM/6/CFM_UNDO_SCHEDULE_YES
13.8 CFM/4/CLEAR
13.9 CFM/4/CFM_CLEARINTERFACECFG
13.10 CFM/4/CRC_CHK
13.11 CFM/5/FILE_NOTEXIST
13.12 CFM/4/FILELENGTH_NOTMATCH
13.13 CFM/4/OVERWRITE_FILE
13.14 CFM/3/RECOVERCMDFAIL
13.15 CFM/4/RST_CFG
13.16 CFM/4/SAVE
13.17 CFM/4/SAVE_FILE
13.18 CFM/5/SAVE_FILE_RECORD
13.19 CFM/5/SAVECFG_NO
13.20 CFM/5/SAVECFG_YES
Issue 07 (2014-07-30)

84

Log Reference
13 CFM
13.21 CFM/3/CFM_SLAVERUNCMDFAIL
13.22 CFM/5/SUMRULECANCEL
13.23 CFM/5/SUMRULECHG
13.24 CFM/5/SUMTMRCHG
Issue 07 (2014-07-30)

85

Log Reference
13 CFM
13.1 CFM/4/B2S_BACKUP_FAILED
Message
CFM/4/B2S_BACKUP_FAILED:Failed to transfer the configuration file to server [server-ip]
through [transport-type] when automatically backing up the configuration.
Description
Failed to transfer the configuration data to the server when backing up the configuration file to
the server.
Parameters
Parameter Name
Parameter Meaning
[server-ip]
Indicates the IP address of the server.
[transport-type]
Indicates the file transfer mode, such as FTP, TFTP, or SFTP.
Possible Causes
1.
The password was incorrect.
2.
The user name was inexistent or the path to the server was inexistent.
3.
The server was unreachable during the transfer of the configuration file due to a network
fault.
Run the ping command on the device to ping the server to check whether the server is
reachable.
Set the device as a client to access the server.
Re-configure the path to the server if it is incorrect.
If the configuration file fails to be transferred only once, it is probably caused by the network
status of the time, and no action is required.
Procedure
If the configuration file fails to be transferred repeatedly, check the link connecting the
device to the server.
----End
13.2 CFM/4/CFM_INCONSISTENT_FILE_IMG
Issue 07 (2014-07-30)

86

Log Reference
13 CFM
Message
CFM/4/CFM_INCONSISTENT_FILE_IMG: If the image file in master and slave board is
inconsistent when system reboot, the slave board will fail to register. (File in master=[STRING],
File in slave=[STRING])
Description
The slave board cannot be registered if the image files on the master and slave boards are
inconsistent when the system reboots.
Parameters
Parameter Name
Parameter Meaning
File in master
Name of the file on the master board
File in slave
Name of the file on the slave board
Possible Causes
The image files on the master and slave boards are inconsistent.
Procedure
Step 1 Ensure the consistency of the image files on the master and slave boards.
----End
13.3 CFM/4/CFM_INCONSISTENT_FILE_CFG
Message
CFM/4/CFM_INCONSISTENT_FILE_CFG: If the configuration file in master and slave board
is inconsistent when system reboot, the configuration in master board may lose. (File in master=
[File in master], File in slave=[File in slave], Reason=[Reason])
Description
The configuration file on the master main control board would be lost if configuration files on
the master and slave main control boards were inconsistent when the system reboots.
Parameters
File in master
Name of the configuration file on the master main control board
File in slave
Name of the configuration file on the slave main control board
Issue 07 (2014-07-30)

87

Log Reference
13 CFM

Reason
The reason for the inconsistency of configuration files on the master and
slave main control boards:
l 1: The sizes of configuration files were different.
l 2. Other reasons.
Possible Causes
Configuration files on the master and slave main control boards were inconsistent.
Procedure
Step 1 Ensure that configuration files on the master and slave main control boards are consistent.
----End
13.4 CFM/6/CFM_OVERWRITESOFTWARE
Message
CFM/6/CFM_OVERWRITESOFTWARE: When deciding whether to overwrite the system
software file, the user chose [Y/N].
Description
The user chose Y or N to decide whether to overwrite the system software file.
Parameters
Parameter Name
Parameter Meaning
Y/N
A user can decide whether to overwrite the system software file:

l Y: Overwrite the system software file.
l N: Do not overwrite the system software file.
Possible Causes
When you set the next startup system software file, the system prompted you to decide whether
to overwrite the system software file if system software files with the same name exist on the
slave main control board.
Procedure
----End
Issue 07 (2014-07-30)

88

Log Reference
13 CFM
13.5 CFM/4/CFM_SYNCFGFILEFAIL
Message
CFM/4/CFM_SYNCFGFILEFAIL: Failed to synchronize the next startup configuration file to
slave board. (FileName=[FileName], SlotNum=[SlotNum])
Description
The next startup configuration file failed to be synchronized to the slave main control board.
Parameters
FileName
Name of the next startup configuration file
SlotNum
Number of the slot in which the slave main control board is installed
Possible Causes
Failed to synchronize the next startup configuration file on the master main control board to the
slave main control board.
Procedure
Step 1 Because next startup configuration files on the master and slave main control boards may be
inconsistent, run the startup saved-configuration command on the slave main control board to
synchronize the next startup configuration file on the master main control board to the slave
main control board after the device starts.
----End
13.6 CFM/6/CFM_UNDO_SCHEDULE_NO
Message
CFM/6/CFM_UNDO_SCHEDULE_NO: When being asked whether to undo schedule reboot
function, the user chose N.
Description
The user selects N when being asked whether to remove the scheduled reboot function.
Issue 07 (2014-07-30)

89

Log Reference
13 CFM
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
When a user sets the startup files or configuration files, if the scheduled reboot function is
configured, the system prompts the user to check whether to remove this function.
l
If the user selects Y, the scheduled reboot function is removed and the process of setting
the startup files or configuration files continues.
If the user selects N, the process of setting the startup files or configuration files is
terminated.
This log message is generated when the user selects N.
Procedure
----End
13.7 CFM/6/CFM_UNDO_SCHEDULE_YES
Message
CFM/6/CFM_UNDO_SCHEDULE_YES: When being asked whether to undo schedule reboot
function, the user chose Y.
Description
The user selects Y when being asked whether to remove the scheduled reboot function.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
When a user sets the startup files or configuration files, if the scheduled reboot function is
configured, the system prompts the user to check whether to remove this function.
l
If the user selects Y, the scheduled reboot function is removed and the process of setting
the startup files or configuration files continues.
If the user selects N, the process of setting the startup files or configuration files is
terminated.
Issue 07 (2014-07-30)

90

Log Reference
13 CFM
This log message is generated when the user selects Y.
Procedure
----End
13.8 CFM/4/CLEAR
Message
CFM/4/CLEAR:When deciding whether to clear inactive configuration of slot [STRING], the
user chose [STRING].
Description
The user chose Y/N when deciding whether to clear the configuration of the board that is not
installed in a specified slot.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the name of a slot.
[STRING]
Indicates the operation that the user chooses.
Possible Causes
The user chose Y/N when deciding whether to clear the configuration of the board that is not
installed in a specified slot.
Procedure
----End
13.9 CFM/4/CFM_CLEARINTERFACECFG
Message
CFM/4/CFM_CLEARINTERFACECFG: When deciding whether to clear configuration(s) of
the interface [interface-name], the user chose [Y/N].
Issue 07 (2014-07-30)

91

Log Reference
13 CFM
Description
The user chose Y or N when the system prompted the user to clear the configuration of an
interface.
Parameters
Parameter Name
Parameter Meaning
interface-name
Interface name
Y/N
Letter that the user input
Possible Causes
The system required the user to determine whether to clear the configuration of an interface
during command execution.
Procedure
----End
13.10 CFM/4/CRC_CHK
Message
CFM/4/CRC_CHK:The user chose [STRING] when deciding whether to check CRC of the
resource file.
Description
The user decided whether to check the CRC of the resource file before running the command.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the character input by the user to confirm the operation:

Y: indicates that the CRC of the resource file will be checked.
N: indicates that the CRC of the resource file will not be checked.
Possible Causes
The user decided whether to check the CRC of the resource file before running the command.
Issue 07 (2014-07-30)

92

Log Reference
13 CFM
Procedure
----End
13.11 CFM/5/FILE_NOTEXIST
Message
CFM/5/FILE_NOTEXIST: Failed to set the [object] because the system file does not exist on
[slot-id].
Description
Failed to set the system file to be loaded at the next startup of the cluster because the file did not
exist.
Parameters
Parameter Name
Parameter Meaning
[object]
Indicates the type of the file:

l Startup file
l PAF file
l License file
l Configuration file
[slot-id]
Indicates the name of a board.
Possible Causes
The system file specified in the startup command did not exist on the relevant board.
Procedure
Step 1 Run the dir command to check whether the system file specified in the startup command exists
on the relevant board.
l If the system file exists, go to Step 3.
l If the system file does not exist, go to Step 2.
Step 2 Upload the relevant system file and then run the startup command again. Then, check whether
the configuration succeeds.
l If the configuration succeeds, go to Step 4.
l If the configuration fails, go to Step 3.
Step 3 Run the display diagnostic-information command and save the command output; contact
Huawei technical support personnel.
Issue 07 (2014-07-30)

93

Log Reference
13 CFM
Step 4 End.
----End
13.12 CFM/4/FILELENGTH_NOTMATCH
Message
CFM/4/FILELENGTH_NOTMATCH:Failed to set the [object] because the size of the system
file is inconsistent with that of the homonymous file on [slot-id].
Description
The configuration failed because the size of the system file was inconsistent with that of the
existing file.
Parameters
Parameter Name
Parameter Meaning
[object]
Indicates the type of the file:

l Startup file
l PAF file
l License file
l Configuration file
[slot-id]
Indicates the name of a board.
Possible Causes
The configuration failed because the size of the system file was inconsistent with that of the
existing file.
Procedure
Step 1 Run the dir command to check whether the size of the system file specified in the startup
command is consistent with that of the system file on the main control board.
l If the sizes of the system files are consistent, go to Step 3.
l If the sizes of the system files are inconsistent, go to Step 2.
Step 2 Delete the system file specified in the startup command from the relevant board and upload the
file again. Then run the startup command to set the system file to be loaded at the next startup
and check whether the configuration succeeds.
l If the configuration succeeds, go to Step 4.
l If the configuration fails, go to Step 3.
Step 3 Run the display diagnostic-information command and save the command output; contact
Issue 07 (2014-07-30)

94

Log Reference
13 CFM
Step 4 End.
----End
13.13 CFM/4/OVERWRITE_FILE
Message
CFM/4/OVERWRITE_FILE:When deciding whether to overwrite the configuration file
[STRING], the user chose [STRING].
Description
The user decided whether to overwrite the configuration file before running the command.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the filename used to save configurations.
[STRING]
Possible Causes
The user decided whether to overwrite the configuration file before running the command.
Procedure
----End
13.14 CFM/3/RECOVERCMDFAIL
Message
CFM/3/RECOVERCMDFAIL:Failed to recover configuration [command] under view [view].
Description
Failed to recover a command in a certain view.
Parameters
Parameter Name
Parameter Meaning
[command]
Command string
Issue 07 (2014-07-30)

95

Log Reference
13 CFM
Parameter Name
Parameter Meaning
[view]
Name of a view
Possible Causes
During configuration restoration, a command failed to be restored.
Procedure
----End
13.15 CFM/4/RST_CFG
Message
CFM/4/RST_CFG:The user chose [Y/N] when deciding whether to reset the saved
configuration.
Description
The user decided whether to reset the saved configuration before running the command.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Possible Causes
The user decided whether to reset the saved configuration before running the command.
Procedure
----End
13.16 CFM/4/SAVE
Message
CFM/4/SAVE:The user chose [Y/N] when deciding whether to save the configuration to the
device.
Issue 07 (2014-07-30)

96

Log Reference
13 CFM
Description
The user decided whether to save the configuration to the device before running the command.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Possible Causes
The user determined whether to save the configuration to the device before running the
command.
Procedure
----End
13.17 CFM/4/SAVE_FILE
Message
CFM/4/SAVE_FILE:When deciding whether to save the configuration to the file [STRING],
the user chose [STRING].
Description
The user decided whether to create the configuration file before running the command.
Parameters
Parameter Name
Parameter Meaning
[STRING]
[STRING]
Possible Causes
The user decided whether to create the configuration file before running the command.
Procedure
----End
Issue 07 (2014-07-30)

97

Log Reference
13 CFM
13.18 CFM/5/SAVE_FILE_RECORD
Message
CFM/5/SAVE_FILE_RECORD: The system automatically saved the current configuration to
the file. (FileName=[STRING])
Description
The system automatically saved the current configuration to the file.
Parameters
Parameter Name
Parameter Meaning
FileName
Possible Causes
When the ISSU was used, or automatic protection was enabled, the system stored the current
configurations into the configuration file.
Procedure
----End
13.19 CFM/5/SAVECFG_NO
Message
CFM/5/SAVECFG_NO:When being asked whether to save current configuration, the user chose
N.
Description
The user chose N when being asked whether to save the configuration before restart.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

98

Log Reference
13 CFM
Possible Causes
Before the system was restarted, the user chose not to save the configuration.
Procedure
----End
13.20 CFM/5/SAVECFG_YES
Message
CFM/5/SAVECFG_YES:When being asked whether to save current configuration, the user
chose Y.
Description
The user chose Y when being asked whether to save the configuration before restart.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Before the system was restarted, the user chose to save the configuration.
Procedure
----End
13.21 CFM/3/CFM_SLAVERUNCMDFAIL
Message
CFM/3/CFM_SLAVERUNCMDFAIL: Failed to execute command on slave board. (Task
name=[STRING], IP address=[STRING], User name=[STRING], Command=[STRING])
Description
Failed to execute commands on the SMB.
Issue 07 (2014-07-30)

99

Log Reference
13 CFM
Parameters
Task name
Task name
IP address
IP address
When the device fails to obtain the user IP address, for example, in a
scenario where the user logs in using a Console interface or AUX
interface, asterisks (**) are used to indicate the IP address.
User name
Name of a login user

When the device fails to obtain the user name, for example, in a passwordbased user authentication scenario, asterisks (**) are used to indicate the
user name.
Command
Executed command
Possible Causes
Commands fail to be backed up to the SMB in real time after being configured on the AMB.
Procedure
l
Collect log information and configuration information, and contact Huawei technical
support personnel.
----End
13.22 CFM/5/SUMRULECANCEL
Message
CFM/5/SUMRULECANCEL:The daylight-saving-time config is canceled.
Description
The configuration of the daylight saving time is canceled.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The undo clock daylight-saving-time command is run to cancel the configuration of the
daylight saving time.
Issue 07 (2014-07-30)

100

Log Reference
13 CFM
Procedure
----End
13.23 CFM/5/SUMRULECHG
Message
CFM/5/SUMRULECHG:The daylight-saving-time config is changed. (DstName=[STRING],
Mode=[STRING], StartConfigType=[STRING], StartDate=[STRING], StartWeek=
[STRING], StartTime=[STRING], EndConfigType=[STRING], EndDate=[STRING],
EndWeek=[STRING], EndTime=[STRING], OffsetTime=[STRING])
Description
The daylight saving time is configured and related information is recorded.
Parameters
Parameter Name
Parameter Meaning
DstName
Name of the daylight saving time
Mode
Mode of the daylight saving time
StartConfigType
Start rule of the daylight saving time
StartDate
Start date of the daylight saving time
StartWeek
Start week of the daylight saving time
StartTime
Start time of the daylight saving time
EndConfigType
End rule of the daylight saving time
EndDate
End date of the daylight saving time
EndWeek
End week of the daylight saving time
EndTime
End time of the daylight saving time
OffsetTime
Offset of the daylight saving time
Possible Causes
The clock daylight-saving-time command is run to configure the daylight saving time.
Procedure
----End
Issue 07 (2014-07-30)

101

Log Reference
13 CFM
13.24 CFM/5/SUMTMRCHG
Message
CFM/5/SUMTMRCHG:The system is changed to [para1] and the system time is changed from
[para2] to [para3].
Description
When the system time changes along with the change of the daylight saving time, the system
time before and after the change is recorded.
Parameters
para1
Type of the system time, daylight saving time or non-daylight saving time
para2
System time before the change of the daylight saving time
para3
System time after the change of the daylight saving time
Possible Causes
The system time changes due to the change of the daylight saving time.
Procedure
----End
Issue 07 (2014-07-30)

102

Log Reference
14 CMD
14
CMD
About This Chapter

14.1 CMD/4/CLKCHGREBOOTCANCELED
14.2 CMD/4/CMD_PRI_REARRG
14.3 CMD/4/DIAG_OVERWRITE
14.4 CMD/4/REBOOT
14.5 CMD/4/SCH_REBOOT
14.6 CMD/4/SUPERLOGIN
Issue 07 (2014-07-30)

103

Log Reference
14 CMD
14.1 CMD/4/CLKCHGREBOOTCANCELED
Message
CMD/4/CLKCHGREBOOTCANCELED:Scheduled reboot will be canceled because [username] changed system clock.
Description
The timed reboot was cancelled.
Parameters
Parameter Name
Parameter Meaning
[user-name]
Indicates the user name.
Possible Causes
The timed reboot was cancelled.
Procedure
----End
14.2 CMD/4/CMD_PRI_REARRG
Message
CMD/4/CMD_PRI_REARRG:The user chose [Y/N] when deciding whether to rearrange the
command level.
Description
The user decides whether to rearrange the command level before running this command.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Possible Causes
The user decides whether to rearrange the command level before running this command.
Issue 07 (2014-07-30)

104

Log Reference
14 CMD
Procedure
----End
14.3 CMD/4/DIAG_OVERWRITE
Message
CMD/4/DIAG_OVERWRITE:The user chose [Y/N] when deciding whether to overwrite the
file.
Description
The user decides whether to overwrite the file before running this command.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Possible Causes
The user decides whether to overwrite the file before running this command.
Procedure
----End
14.4 CMD/4/REBOOT
Message
CMD/4/REBOOT:The user chose [Y/N] when deciding whether to reboot the system.(Task=
[STRING], Ip=[STRING], User=[STRING])
Description
The user decides whether to reboot the system before running this command.
Issue 07 (2014-07-30)

105

Log Reference
14 CMD
Parameters
[Y/N]
Task
The name of the task.
Ip
The IP address of the user.

User
The name of the user.

user name.
Possible Causes
The user decides whether to reboot the system before running this command.
Procedure
----End
14.5 CMD/4/SCH_REBOOT
Message
CMD/4/SCH_REBOOT:The user chose [Y/N] when deciding whether to reboot according to
the schedule.
Description
The user decides whether to reboot the system according to the schedule.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Issue 07 (2014-07-30)

106

Log Reference
14 CMD
Possible Causes
The user decides whether to reboot the system according to the schedule.
Procedure
----End
14.6 CMD/4/SUPERLOGIN
Message
CMD/4/SUPERLOGIN:User changed level. (User=[string], IpAddress=[string], Level=
[USHORT], LoginResult=[string])
Description
The level of the current terminal user is changed by using a command line.
Parameters
User

user name.
IpAddress
Indicates an IP address.
Level
Indicates the user level.
LoginResult
Indicates whether the user successfully logs in.
Possible Causes
The level of the current terminal user is changed by using a command line.
Procedure
----End
Issue 07 (2014-07-30)

107

Log Reference
15 CSPF
15
CSPF
About This Chapter

15.1 CSPF/3/IGP_LINK_INFONULL
15.2 CSPF/3/IGP_NWLSA_INFONULL
15.3 CSPF/3/IGP_RID_INFONULL
15.4 CSPF/3/INVAL_LINK
15.5 CSPF/3/INVAL_NWLINK
15.6 CSPF/4/MAX_LINK_REACH
15.7 CSPF/4/MAX_NODE_REACH
15.8 CSPF/4/MAX_NWLSA_REACH
15.9 CSPF/4/MAX_SRLG_REACH
15.10 CSPF/3/MEM_FAIL
15.11 CSPF/3/PATH_ERROR
15.12 CSPF/3/Q_ERROR
15.13 CSPF/3/TIME_FAIL
Issue 07 (2014-07-30)

108

Log Reference
15 CSPF
15.1 CSPF/3/IGP_LINK_INFONULL
Message
CSPF/3/IGP_LINK_INFONULL: Received a link event with null information from IGP
[IgpName].
Description
A link event that did not contain any link information was received from the IGP protocol.
Parameters
Parameter Name
Parameter Meaning
[IgpName]
Indicates the name of an IGP protocol, such as IS-IS and OSPF.
Possible Causes
Received nework-lsa information is not valid.
Procedure
Step 1 1. Verify IGP database.
l If IGP is OSPF use display ospf lsdb opaque-link and display ospf lsdb opaque-area
command.
l If IGP is ISIS use display isis traffic-eng link and display isis traffic-eng network
command.
Step 2 2. Reset OSPF or IS-IS process.
----End
15.2 CSPF/3/IGP_NWLSA_INFONULL
Message
CSPF/3/IGP_NWLSA_INFONULL: Received a Network-LSA with null information from IGP
[IgpName].
Description
A network-LSA event that did not contain any network-LSA information was received from the
IGP protocol.
Issue 07 (2014-07-30)

109

Log Reference
15 CSPF
Parameters
Parameter Name
Parameter Meaning
[IgpName]
Possible Causes
Network LSA event does not contain any network lsa information.
Procedure
command.
command.
----End
15.3 CSPF/3/IGP_RID_INFONULL
Message
CSPF/3/IGP_RID_INFONULL: Received an invalid router ID from IGP.
Description
The invalid router ID was received from the IGP protocol.
Parameters
None.
Possible Causes
Invalid Router ID from IGP.
Procedure
command.
command.
Issue 07 (2014-07-30)

110

Log Reference
15 CSPF

----End
15.4 CSPF/3/INVAL_LINK
Message
CSPF/3/INVAL_LINK: Received invalid link information from IGP [IgpName].
Description
Invalid link information was received from the IGP protocol.
Parameters
Parameter Name
Parameter Meaning
[IgpName]
Possible Causes
Received link information is not valid.
Procedure
command.
command.
----End
15.5 CSPF/3/INVAL_NWLINK
Message
CSPF/3/INVAL_NWLINK:Received invalid Network-LSA information from IGP [IgpName].
Description
Invalid network-LSA information was received from the IGP protocol.
Issue 07 (2014-07-30)

111

Log Reference
15 CSPF
Parameters
Parameter Name
Parameter Meaning
[IgpName]
Possible Causes
Received nework-lsa information is not valid.
Procedure
command.
command.
----End
15.6 CSPF/4/MAX_LINK_REACH
Message
CSPF/4/MAX_LINK_REACH: Reached the maximum number of links of CSPF.
Description
The number of links reached the maximum.
Parameters
None.
Possible Causes
CSPF cannot add more links in TEDB.
Procedure
Step 1 Increase the upper limit of CSPF links in PAF.
----End
15.7 CSPF/4/MAX_NODE_REACH
Issue 07 (2014-07-30)

112

Log Reference
15 CSPF
Message
CSPF/4/MAX_NODE_REACH: Reached the maximum number of nodes of CSPF.
Description
The number of CSPF nodes reached the maximum.
Parameters
None.
Possible Causes
CSPF cannot add more link nodes in TEDB.
Procedure
Step 1 Increase the upper limit of CSPF nodes in PAF.
----End
15.8 CSPF/4/MAX_NWLSA_REACH
Message
CSPF/4/MAX_NWLSA_REACH: Reached the maximum number of Network-LSAs of CSPF.
Description
The number of network-LSAs reached the maximum.
Parameters
None.
Possible Causes
CSPF cannot add more network-lsa nodes in TEDB.
Procedure
Step 1 Increase the upper limit of CSPF network-LSAs in PAF.
----End
15.9 CSPF/4/MAX_SRLG_REACH
Issue 07 (2014-07-30)

113

Log Reference
15 CSPF
Message
CSPF/4/MAX_SRLG_REACH: The number of SRLGs reached the upper limit of CSPF.
Description
The number of SRLGs reached the upper limit of CSPF.
Parameters
None.
Possible Causes
CSPF cannot add more SRLG in TEDB since the number of SRLGs configured has reached the
maximum value that CSPF supports.
Procedure
Step 1 If better service is needed, please contact with Huawei engineer to increase corresponding PAF
value.
----End
15.10 CSPF/3/MEM_FAIL
Message
CSPF/3/MEM_FAIL: Failed to allocate memory.
Description
Failed to allocate memory.
Parameters
None.
Possible Causes
Memory was insufficient, causing the memory allocation failure.
Procedure
Step 1 Use display memory-usage command and free some memory by cutting down topology or
configuration.
----End
Issue 07 (2014-07-30)

114

Log Reference
15 CSPF
15.11 CSPF/3/PATH_ERROR
Message
CSPF/3/PATH_ERROR: Failed to calculate the path due to [PathError].
Description
Path computation fails.
Parameters
Parameter Name
Parameter Meaning
[PathError]
Path error string, including:

l configuration of two interface address
l configuration of next hop after
l configuration of next hop after egress
l configuration of egress node directly as strict is not permitted
l configuration of next hop after egress node is not permitted
Possible Causes
Path computation fails.
Procedure
Step 1 Check explicit path using display explicit-path and verify path for errors specified in log
message and correct explicit path configuration.
----End
15.12 CSPF/3/Q_ERROR
Message
CSPF/3/Q_ERROR: Failed to fill in [EventName] queue.
Description
Failed to fill in event queue.
Issue 07 (2014-07-30)

115

Log Reference
15 CSPF
Parameters
Parameter Name
Parameter Meaning
[EventName]
Failed event information. CSPF_LSPM or CSPF_RM.
Possible Causes
Failed to fill in event queue. Maybe the queue is full or the system function is wrong.
Procedure
Step 1 Wait for a while.
Step 2 Cancel and re-configure CSPF.
----End
15.13 CSPF/3/TIME_FAIL
Message
CSPF/3/TIME_FAIL:Failed to create the timer. (ReturnValue=[ULONG])
Description
Failed to create the timer used for detecting a link.
Parameters
ReturnValue
Indicates the value returned by the function used for creating a timer.
Possible Causes
Create timer fails.
Procedure
Step 1 1. Display mpls te cspf tedb node and check for inactive links.
Step 2 2. Reset OSPF or ISIS.
----End
Issue 07 (2014-07-30)

116

Log Reference
16 MAD
16
MAD
About This Chapter

16.1 MAD/4/CONFLICT_DETECT
16.2 MAD/4/MEMBER_LOST
16.3 MAD/4/PORT_SHUTDOWN
16.4 MAD/4/PORT_RESTORE
Issue 07 (2014-07-30)

117

Log Reference
16 MAD
16.1 MAD/4/CONFLICT_DETECT
Message
MAD/4/CONFLICT_DETECT:Multi-active scenario is detected.
Description
A multi-active scenario was detected.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1.
The stack link was faulty.
Rectify the stack link fault.
Procedure
----End
16.2 MAD/4/MEMBER_LOST
Message
MAD/4/MEMBER_LOST:A member of the device is lost.
Description
Detecting the stack neighbor failed and the stack split.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1.
2.
The stack was faulty.
Issue 07 (2014-07-30)

118

Log Reference
16 MAD
Procedure
l
Rectify the stack fault.
----End
16.3 MAD/4/PORT_SHUTDOWN
Message
MAD/4/PORT_SHUTDOWN:The state of this device changes to recovery. All interfaces
(except interfaces configured to be excluded from shutdown) of this device is going to be
shutdown.
Description
The device entered the recovery state and shut down all of its service interfaces except those
excluded from shutdown.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1.
After the stack split, a multi-active scenario occurred and the local device was determined
to be the standby switch.
Procedure
----End
16.4 MAD/4/PORT_RESTORE
Message
MAD/4/PORT_RESTORE:All interfaces been shutdown is going to restore.
Description
All the service interfaces that were shut down need to be restored.
Issue 07 (2014-07-30)

119

Log Reference
16 MAD
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1.
2.
The stack was faulty.
Run the restore command.
Procedure
----End
Issue 07 (2014-07-30)

120

Log Reference
17 DLDP
17
DLDP
About This Chapter

17.1 DLDP/4/GLOBAL_NB_FULL
17.2 DLDP/4/PORT_NB_FULL
Issue 07 (2014-07-30)

121

Log Reference
17 DLDP
17.1 DLDP/4/GLOBAL_NB_FULL
Message
DLDP/4/GLOBAL_NB_FULL:New neighbor cannot be added, because the number of global
neighbors reached the upper limit (4096). (PortName=[STRING])
Description
Neighbors in the DLDP are generally direct-connection ports, and global neighbors refer to all
neighbors on the equipment. The MAC address of the equipment and a port ID uniquely identify
a neighbor. When the number of global neighbors reaches the upper limit (4096), no more
neighbors can be added.
Parameters
Parameter Name
Parameter Meaning
PortName
Port name
Possible Causes
The number of global neighbors exceeds the upper limit. The number of global neighbors ranges
from 0 to 4096.
Procedure
Step 1 In any view, run the display dldp command to check whether the number of global neighbors
reaches the maximum value, that is, 4096.
1) Yes=>2.
2) No=>3.
Step 2 Disable the DLDP function of other ports so that the equipment automatically deletes the
neighbors under the ports where the DLDP function is disabled, or do not process the log.
Step 3 Contact Huawei technical support engineers.
----End
17.2 DLDP/4/PORT_NB_FULL
Message
DLDP/4/PORT_NB_FULL:New neighbor cannot be added, because the number of neighbors
of the port reached the upper limit (128). (PortName=[STRING])
Issue 07 (2014-07-30)

122

Log Reference
17 DLDP
Description
Neighbors in the DLDP are generally direct-connection ports, and neighbors under a port refer
to all neighbors under the port. The MAC address of the equipment and a port ID uniquely
identify a neighbor. When the number of neighbors under a port reaches the upper limit (128),
no more neighbors can be added.
Parameters
Parameter Name
Parameter Meaning
PortName
Port name
Possible Causes
The number of neighbors under a port exceeds the upper limit. The number of neighbors ranges
from 0 to 128.
Procedure
Step 1 This log is normal operation information and does not need to be processed.
----End
Issue 07 (2014-07-30)

123

Log Reference
18 DOT1X
18
DOT1X
About This Chapter

18.1 DOT1X/4/ADD_ACL_FAILED
18.2 DOT1X/5/QUIETTABLE_FULL
Issue 07 (2014-07-30)

124

Log Reference
18 DOT1X
18.1 DOT1X/4/ADD_ACL_FAILED
Message
DOT1X/4/ADD_ACL_FAILED:Add ACL failed because of no enough ACL resources.
Description
ACL cannot be delivered because of insufficient ACL resources.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
l
The ACL resource is exhausted.
Procedure
----End
18.2 DOT1X/5/QUIETTABLE_FULL
Message
DOT1X/5/QUIETTABLE_FULL: The user cannot be authenticated temporarily, because the
number of entries in the quiet table exceeds the upper limit. (MAC Address=[STRING])
Description
The silent table is full and the user cannot be authenticated.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the MAC address of the user.
Possible Causes
The silent table was full.
Issue 07 (2014-07-30)

125

Log Reference
18 DOT1X
Procedure
Step 1 Check whether the device is attacked by packets. If so, process these attack packets first.
Step 2 The user can be authenticated after the silent table is aged.
Step 3 If the fault persists, contact Huawei technical personnel.
----End
Issue 07 (2014-07-30)

126

Log Reference
19 DEFD
19
DEFD
About This Chapter

19.1 DEFD/4/CPCAR_DROP_MPU
19.2 DEFD/4/CPCAR_DROP_LPU
Issue 07 (2014-07-30)

127

Log Reference
19 DEFD
19.1 DEFD/4/CPCAR_DROP_MPU
Message
DEFD/4/CPCAR_DROP_MPU:Rate of packets to cpu exceeded the CPCAR limit on the MPU.
(Protocol=[STRING], CIR/CBS=[ULONG]/[ULONG], ExceededPacketCount=[STRING])
Description
The rate of packets delivered to the CPU exceeds the CPCAR limit on the MPU.
Parameters
Parameter Name
Parameter Meaning
Protocol
Indicates the protocol type.
CIR/CBS
Indicates the committed information rate and committed burst size.
ExceededPacketCount Specifies the number of packets whose rate exceeds the CPCAR.
Possible Causes
The rate of packets sent to the CPU of the MPU exceeds the CPCAR.
Procedure
Step 1 Limit the rate of packets sent to the CPU within the CPCAR or increase the CPCAR value.
----End
19.2 DEFD/4/CPCAR_DROP_LPU
Message
DEFD/4/CPCAR_DROP_LPU:Rate of packets to cpu exceeded the CPCAR limit on the LPU
in slot [STRING]. (Protocol=[STRING], CIR/CBS=[ULONG]/[ULONG],
ExceededPacketCount=[STRING])
Description
The rate of packets delivered to the CPU exceeds the CPCAR limit on the LPU.
Issue 07 (2014-07-30)

128

Log Reference
19 DEFD
Parameters
Parameter Name
Parameter Meaning
slot
l The value is 0 on a single device.

l Specifies the stack ID if stacking is configured.
Protocol
Indicates the protocol type.
CIR/CBS
Indicates the committed information rate and committed burst size.
ExceededPacketCount Specifies the number of packets whose rate exceeds the CPCAR.
Possible Causes
The rate of packets sent to the CPU of the LPU exceeds the CPCAR.
Procedure
Step 1 Run the auto-defend enable command to configure attack source tracing. If a possible attack
source is detected, check on the network to determine whether it is a real attack source.
Step 2 If a real attack source exists, run the blacklist command to add the attack source to the blacklist
or run the auto-defend action command to configure a punish action for the attack source. If
no attack source exists, run the car (attack defense policy view) command to increase the
CPCAR value properly.
----End
Issue 07 (2014-07-30)

129

Log Reference
20 DHCP
20
DHCP
About This Chapter

20.1 DHCP/4/DHCP_CLIENT_CONFLICT_IPADDR
20.2 DHCP/0/DHCP_SERVER_DETECT
20.3 DHCP/0/DHCPRATET_LIMIT
20.4 DHCP/0/DHCPV6_SERVER_DETECT
20.5 DHCP/0/DHCPV6RATET_DETECT
20.6 DHCP/4/DHCP_INFO_LOG_DHCP_ADD_ACL_FAILED
20.7 DHCP/4/DHCP_INFO_LOG_DHCP_REMOTEBACKUP_FAILED
20.8 DHCP/0/ND_SERVER_DETECT
20.9 DHCP/4/DHCP_BINDTBL_ADDR_CONFLICT
20.10 DHCP/4/DHCP_INFO_LOG_DHCP_SLAVE_LOW_SPACE
20.11 DHCP/4/DHCP_RELAY_WRONG_GIADDR
20.12 DHCP/4/DHCP_RELAY_WRONG_MAC
Issue 07 (2014-07-30)

130

Log Reference
20 DHCP
20.1 DHCP/4/DHCP_CLIENT_CONFLICT_IPADDR
Message
DHCP/4/DHCP_CLIENT_CONFLICT_IPADDR:"DHCP client receive an ARP packet with a
conflict IP address. (IpAddress=[STRING1], MacAddress=[STRING2], InterfaceName=
[STRING3])."
Description
A device whose IP address conflicts with the IP address of the VLANIF interface through DHCP
exists on the network.
Parameters
[STRING1]
Conflicting IP address.
[STRING2]
Conflicting MAC address of the host.
[STRING3]
Name of the interface that receives the conflicting MAC address of the
host.
Possible Causes
The DHCP client receives ARP response packets with conflicting the IP address.
Procedure
Step 1 Determine the device where a conflict occurs and change the IP address according to the name
of the interface that receives the conflicting MAC address of the host, conflicting IP address,
and conflicting MAC address of the host.
----End
20.2 DHCP/0/DHCP_SERVER_DETECT
Message
DHCP/0/DHCP_SERVER_DETECT(l):"A NEW SERVER IS FOUND.(SERVER INFO : IP
Address = [STRING1], MAC Address = [STRING2], Interface = [STRING3], AP MAC Address
= [STRING4])"
Description
A rogue DHCP server was found.
Issue 07 (2014-07-30)

131

Log Reference
20 DHCP
Parameters
[STRING1]
Indicates the IP address of the server.
[STRING2]
Indicates the MAC address of the server.
[STRING3]
Indicates the port to which the server is connected.
[STRING4]
Indicates the MAC address of the AP to which the server is connected.
Possible Causes
A rogue DHCP server was found.
Procedure
Step 1 Enable the DHCP trusted interface function to discard packets from the rogue DHCP server.
----End
20.3 DHCP/0/DHCPRATET_LIMIT
Message
DHCP/0/DHCPRATET_LIMIT: The rate of DHCP packets exceeds the speed limit.
[INTEGER] packets have been discarded.
Description
DHCPv4 messages exceed the rate and the number of discarded DHCPv4 messages reaches the
threshold.
Parameters
Parameter Name
Parameter Meaning
[INTEGER]
Number of discarded packets.
Possible Causes
threshold.
Procedure
Step 1 The device receives a large number of DHCPv4 messages, indicating that an attack occurs on
the network. In this case, check the network.
----End
Issue 07 (2014-07-30)

132

Log Reference
20 DHCP
20.4 DHCP/0/DHCPV6_SERVER_DETECT
Message
DHCP/0/DHCPV6_SERVER_DETECT:"A NEW SERVER IS FOUND.(SERVER INFO : IP
Address = [STRING1], MAC Address = [STRING2],Interface = [STRING3])"
Description
The DHCPv6 server information is recorded.
Parameters
Parameter Name
Parameter Meaning
[STRING1]
IP address of the server.
[STRING2]
[STRING3]
Name of the interface that receives the MAC address of the server.
Possible Causes
Messages from the new DHCPv6 server are received.
Procedure
Step 1 If a small number of log messages are displayed, this log is normal. If a large number of log
messages are displayed, you need to search for the unauthorized server according to the interface
name, MAC address, and IP address in the log.
----End
20.5 DHCP/0/DHCPV6RATET_DETECT
Message
DHCP/0/DHCPV6RATET_DETECT:"The rate of DHCPV6 packets exceeds the speed limit.
[INTEGER] packets have been discarded."
Description
threshold.
Issue 07 (2014-07-30)

133

Log Reference
20 DHCP
Parameters
Parameter Name
Parameter Meaning
[INTEGER]
Number of discarded packets.
Possible Causes
threshold.
Procedure
Step 1 The device receives a large number of DHCPv6 messages, indicating that an attack occurs on
the network. In this case, check the network.
----End
20.6 DHCP/4/
DHCP_INFO_LOG_DHCP_ADD_ACL_FAILED
Message
DHCP/4/DHCP_INFO_LOG_DHCP_ADD_ACL_FAILED(l)[0]:Add ACL failed because of
no enough ACL resources.
Description
ACL rules failed to be delivered because ACL resources were insufficient.
Parameters
None
Possible Causes
When configuring DHCP commands, the commands do not take effect if the ACL resources are
insufficient.
Procedure
Step 1 Release some of the ACL resources that are not used and delete DHCP commands. Configure
DHCP commands when ACL resources are sufficient.
----End
Issue 07 (2014-07-30)

134

Log Reference
20 DHCP
20.7 DHCP/4/
DHCP_INFO_LOG_DHCP_REMOTEBACKUP_FAILED
Message
DHCP/4/DHCP_INFO_LOG_DHCP_REMOTEBACKUP_FAILED:Saving the dynamic
binding table to a remote server failed. Ensure that the FTP/SFTP server address is reachable
and the FTP/SFTP user name and password and the file path are correct.
Description
DHCP snooping binding entries fail to be backed up on the remote FTP/SFTP server. Ensure
that the device can connect to the FTP/SFTP server, the entered FTP/SFTP user name and
password are correct, and the path for storing the binding table file is correct.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
l
The device cannot connect to the remote FTP/SFTP server.
The input FTP/SFTP user name or password is incorrect.
The path for storing the binding table file is incorrect.
Procedure
Step 1 Check whether the IP address of the remote FTP/SFTP server is correct. Ensure that the device
can correctly connect to the FTP/SFTP server.
Step 2 Ensure that the input FTP/SFTP user name or password is correct.
Step 3 Ensure that the path for storing the binding table file is correct.
----End
20.8 DHCP/0/ND_SERVER_DETECT
Message
DHCP/0/ND_SERVER_DETECT:AN UNTRUSTED ND SERVER IS FOUND.(SERVER
INFO : IP Address = [STRING1], MAC Address = [STRING],Interface Name =
[STRING],Prefix = [STRING],Prefix len = [ULONG])
Issue 07 (2014-07-30)

135

Log Reference
20 DHCP
Description
The ND server information is recorded.
Parameters
Parameter Name
Parameter Meaning
[STRING1]
[STRING2]
MAC address of the server.
[STRING3]
Interface name.
[STRING4]
Prefix name.
[ULONG]
Prefix length.
Possible Causes
The non-trusted interface receives RA messages from a new server on a network where ND
snooping is enabled.
Procedure
Step 1 Check the network and search for the unauthorized server according to the server IP address.
----End
20.9 DHCP/4/DHCP_BINDTBL_ADDR_CONFLICT
Message
DHCP/4/DHCP_BINDTBL_ADDR_CONFLICT:Delete dhcp bind-table because IP address
conflict.(Bind-table info: InterfaceName=[STRING], Pvlan=[ULONG], Cvlan=[ULONG], IP
Address=[IPADDR], MAC Address=[STRING])
Description
A user binding table was deleted because of an IP address conflict.
Parameters
InterfaceName
Indicates the interface connected to a user in the binding table.
Pvlan
Indicates information about the outer VLAN of the user in the binding
table.
Issue 07 (2014-07-30)

136

Log Reference
20 DHCP

Cvlan
Indicates information about the inner VLAN of the user in the binding
table.
IP Address
Indicates the IP address of the user in the binding table.
MAC Address
Indicates the MAC address of the user in the binding table.
Possible Causes
The IP address of a user in the binding table conflicted with the IP address of another user.
Procedure
----End
20.10 DHCP/4/
DHCP_INFO_LOG_DHCP_SLAVE_LOW_SPACE
Message
DHCP/4/DHCP_INFO_LOG_DHCP_SLAVE_LOW_SPACE:There is no space for DHCP on
the slave board.
Description
The slave board does not have sufficient space for the DHCP service.
Parameters
None
Possible Causes
When the service is being stored, the storage space of the slave board is insufficient.
Procedure
Step 1 Release the storage space of the slave board.
----End
Issue 07 (2014-07-30)

137

Log Reference
20 DHCP
20.11 DHCP/4/DHCP_RELAY_WRONG_GIADDR
Message
DHCP/4/DHCP_RELAY_WRONG_GIADDR: DHCP relay receive a dhcp packet with wrong
giaddr address. (InterfaceName=[STRING]).
Description
The DHCP relay agent received a DHCP packet with an incorrect giaddr field value.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the interface name.
Possible Causes
The giaddr field value in the DHCP packet that the DHCP relay agent received in invalid.
Procedure
Step 1 Check whether DHCP relay is correctly configured after the DHCP relay agent receives a DHCP
Request packet with an incorrect giaddr field value.
----End
20.12 DHCP/4/DHCP_RELAY_WRONG_MAC
Message
DHCP/4/DHCP_RELAY_WRONG_MAC: DHCP relay receive a dhcp packet with wrong
MAC address. (InterfaceName=[STRING]).
Description
The DHCP relay receives a DHCP packet with the incorrect client MAC address.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
Interface name.
Issue 07 (2014-07-30)

138

Log Reference
20 DHCP
Possible Causes
The DHCP relay receives a DHCP packet in which the client MAC address field is set to a
broadcast or unicast address. To prevent attacks, the device considers this packet as an invalid
packet.
Procedure
Step 1 Check whether there are DHCP attacks based on the client MAC address and the name of the
interface that receives the packet.
l Y=>2.
l N=>3.
Step 2 Configure DHCP snooping to check validity of DHCP packets.
Step 3 End.
----End
Issue 07 (2014-07-30)

139

Log Reference
21 DSA
21
DSA
About This Chapter

21.1 DSA/4/FILE_READ_ERR
21.2 DSA/4/FILE_SAVE_ERR
21.3 DSA/3/HOST_PUBKEY_BAK_FAL
21.4 DSA/4/HOSTKEY_BACKUP_ERR
21.5 DSA/4/HOSTKEY_BAK_DEL_ERR
21.6 DSA/3/HOSTKEY_DEL_ERR
21.7 DSA/3/HOSTKEY_SAVE_ERR
21.8 DSA/6/KEY_SIZE
21.9 DSA/4/REPLACE_KEYS
Issue 07 (2014-07-30)

140

Log Reference
21 DSA
21.1 DSA/4/FILE_READ_ERR
Message
DSA/4/FILE_READ_ERR:The file operation failed when the DSA key is read from file.
(Operation=[STRING])
Description
Failed to read the DSA key from the file.
Parameters
Parameter Name
Parameter Meaning
Operation
File operation type
Possible Causes
A user failed to read the DSA key from the file.
Procedure
Step 1 Collect log and configuration information, and contact Huawei technical support personnel.
----End
21.2 DSA/4/FILE_SAVE_ERR
Message
DSA/4/FILE_SAVE_ERR:The file operation failed when the DSA key is saved to file.
(Operation=[STRING])
Description
Failed to save the DSA key to the file.
Parameters
Parameter Name
Parameter Meaning
Operation
File operation type
Possible Causes
A user failed to save the DSA key to the file.
Issue 07 (2014-07-30)

141

Log Reference
21 DSA
Procedure
----End
21.3 DSA/3/HOST_PUBKEY_BAK_FAL
Message
DSA/3/HOST_PUBKEY_BAK_FAL:Failed to save DSA host key on the slave board.
Description
Failed to save the DSA host key to the SMB.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
A user failed to save the DSA host key due to the insufficient memory of the SMB.
Procedure
----End
21.4 DSA/4/HOSTKEY_BACKUP_ERR
Message
DSA/4/HOSTKEY_BACKUP_ERR:Failed to backup DSA host key.
Description
Failed to back up the DSA host key.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

142

Log Reference
21 DSA
Possible Causes
The possible causes are as follows:
l
The data to be backed up was null.
Memory failed to be allocated for data backup.
Sending the backup message failed.
Procedure
----End
21.5 DSA/4/HOSTKEY_BAK_DEL_ERR
Message
DSA/4/HOSTKEY_BAK_DEL_ERR:Succeeded in destroying DSA host key in the main board,
but failed to destroy DSA host key in the slave board.
Description
Succeeded in destroying the DSA host key on the AMB, but failed to destroy the DSA host key
on the SMB.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The possible causes are as follows:
l
The data to be backed up was null.
Memory failed to be allocated for data backup.
Sending the backup message failed.
Procedure
----End
21.6 DSA/3/HOSTKEY_DEL_ERR
Issue 07 (2014-07-30)

143

Log Reference
21 DSA
Message
DSA/3/HOSTKEY_DEL_ERR:Failed to destroy DSA host key.
Description
Failed to destroy the DSA host key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The DSA host key file failed to be cleared.
Procedure
----End
21.7 DSA/3/HOSTKEY_SAVE_ERR
Message
DSA/3/HOSTKEY_SAVE_ERR:Failed to save DSA host key on the main board.
Description
Failed to save the DSA host key to the AMB.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
A user failed to save the DSA host key due to the insufficient memory of the AMB.
Procedure
----End
Issue 07 (2014-07-30)

144

Log Reference
21 DSA
21.8 DSA/6/KEY_SIZE
Message
DSA/6/KEY_SIZE:The user inputs the size of key [key-length].
Description
The user inputted the length of the key.
Parameters
Parameter Name
Parameter Meaning
[key-length]
indicates the length of a key.
Possible Causes
After the dsa local-key-pair create command is run, the system prompts the user to input the
key length.
Procedure
l
----End
21.9 DSA/4/REPLACE_KEYS
Message
DSA/4/REPLACE_KEYS:The user choose [Y/N] when being asked if the existing DSA keys
should be replaced.
Description
Failed to back up the DSA host key.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Operation type
Possible Causes
A user failed to create a new key without deleting the original key on the device.
Issue 07 (2014-07-30)

145

Log Reference
21 DSA
Procedure
----End
Issue 07 (2014-07-30)

146

Log Reference
22 EFM
22
EFM
About This Chapter

22.1 EFM/3/INVALID_ORGSPECIFICINFOTLV
22.2 EFM/2/NONTHRESHOLD
22.3 EFM/6/REMOTE_STATE_CHANGED
22.4 EFM/3/THRESHOLD
22.5 EFM/4/TRIGGERIFNET
22.6 EFM/5/ISSUSTATUS
Issue 07 (2014-07-30)

147

Log Reference
22 EFM
22.1 EFM/3/INVALID_ORGSPECIFICINFOTLV
Message
EFM/3/INVALID_ORGSPECIFICINFOTLV:Remote Organization Specific Information TLV
was invalid. (InterfaceName=[STRING], ErrCode=[ULONG], TLVLength=[ULONG],
RemoteState=[ULONG])
Description
The specific TLV of the manufacturer was invalid.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
ErrCode
TLVLength
Indicates the length of the TLV.
RemoteState
Indicates the master/slave status of the peer device.
Possible Causes
EFM OAM resolved the specific TLV of the manufacturer and found it invalid.
Procedure
Step 1 Confirm the type of the error code.
l If the error code is 1, it indicates that the organization TLV length is invalid.
l If the error code is 2, it indicates that the organization TLV value is invalid.
Step 2 Query the configuration of the remote wireless equipment and consult the part describing EFM
in the troubleshooting guide.
----End
22.2 EFM/2/NONTHRESHOLD
Message
EFM/2/NONTHRESHOLD:Non-threshold-crossing event occurred. (InterfaceName=
[STRING], EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], EventLogOui=
Issue 07 (2014-07-30)

148

Log Reference
22 EFM
[OPAQUE], EventLogType=[GAUGE], EventLogLocation=[INTEGER],

EventLogRunningTotal=[COUNTER64])
Description
The non-threshold-crossing event occurred on the EOAM 3AH module.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
EventLogIndex
Indicates the index of an event.
EventLogTimestamp
Indicates the time when the event occurs.
EventLogOui
Indicates the unique identifier of a manufacturer.
EventLogType
Indicates the log type.
EventLogLocation
Indicates the location (1 indicates local end, 2 indicates peer end) of

the event.
EventLogRunningTotal Indicates the total of non-threshold-crossing events after the OAM

is reset.
Possible Causes
The non-threshold-crossing event was detected.
Procedure
Step 1 An abnormality occurs on the local end or the peer end.
----End
22.3 EFM/6/REMOTE_STATE_CHANGED
Message
EFM/6/REMOTE_STATE_CHANGED:Remote equipment's state changed from [State1] to
[State2]. (InterfaceName=[STRING])
Description
The status of the peer device was changed from master to slave or from slave to master.
Issue 07 (2014-07-30)

149

Log Reference
22 EFM
Parameters
State1
Indicates the original master/slave status of the peer device:

171: Indicates the peer device is in the master state.
186: Indicates the peer device is in the slave state.
0: Indicates that packets from the peer device do not carry information
about the master/slave status, or the master/slave status cannot be
obtained.
State2
Indicates the current master/slave status of the peer device:

171: indicates the peer device is in the master state.
186: indicates the peer device is in the slave state.
0: indicates that packets from the peer device do not carry information
about the master/slave status, or the master/slave status cannot be
obtained.
InterfaceName
Possible Causes
1. The status of the peer device was changed from master to slave or from slave to master.
2. The peer device changed from lacking of master/slave information to taking master/slave
information.
3. The master/slave status of the peer device could not be obtained owing to link faults.
Procedure
----End
22.4 EFM/3/THRESHOLD
Message
EFM/3/THRESHOLD:Threshold-crossing event occurred. (InterfaceName=[STRING],
EventLogIndex=[GAUGE], EventLogTimestamp=[TIMETICK], EventLogOui=[OPAQUE],
EventLogType=[GAUGE], EventLogLocation=[INTEGER], EventLogWindowHi=
[GAUGE], EventLogWindowLo=[GAUGE], EventLogThresholdHi=[GAUGE],
EventLogThresholdLo=[GAUGE], EventLogValue=[COUNTER64],
EventLogRunningTotal=[COUNTER64], EventLogEventTotal=[GAUGE])
Issue 07 (2014-07-30)

150

Log Reference
22 EFM
Description
The threshold-crossing event occurred on the EOAM 3AH module.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
EventLogIndex
Indicates the index of an event.
EventLogTimestamp
Indicates the time when the event occurs.
EventLogOui
Indicates the unique identifier of a manufacturer.
EventLogType
Indicates the log type.
EventLogLocation
Indicates the location (1 indicates local end, 2 indicates peer end) of

the event.
EventLogWindowHi
Indicates the higher 4-byte interval.
EventLogWindowLo
Indicates the lower 4-byte interval.
EventLogThresholdHi
Indicates the higher 4-byte threshold.
EventLogThresholdLo
Indicates the lower 4-byte threshold.
EventLogValue
Indicates the number of errors within the interval (error frames or

error codes).
EventLogRunningTotal Indicates the total number of errors after OAM is reset.

EventLogEventTotal
Indicates the total number of threshold-crossing events after OAM

is reset.
Possible Causes
The events of error frames, error frame seconds, and error codes were detected. The number of
link faults reached the set threshold within the set interval.
Procedure
Step 1 Check the link and the environment, and analyze the cause of excessive error frames and error
codes.
----End
22.5 EFM/4/TRIGGERIFNET
Message
EFM/4/TRIGGERIFNET:EFM trigger interface. (InterfaceName=[STRING], Result=
[INTEGER])
Issue 07 (2014-07-30)

151

Log Reference
22 EFM
Description
The service of interface was blocked by the EOAM 3AH module.
Parameters
InterfaceName
Result
Indicates the Status of fault. The detailed information is as followings:

l Trigger interface up means fault recovery
l Trigger interface down means fault occurence
Possible Causes
The interface service block function of 802.3AH was configured, and 802.3AH sense the fault.
Procedure
Step 1 Check the configurations at both ends of the link.
----End
22.6 EFM/5/ISSUSTATUS
Message
EFM/5/ISSUSTATUS: The ISSU working status of EFM is [STRING]. (Time=[ULONG])
Description
The ISSU working status of the EFM module.
Issue 07 (2014-07-30)

152

Log Reference
22 EFM
Parameters
STRING
The ISSU working status of the EFM module.

l ISSU batch backup of main board in phase 1 started: The first phase
for the ISSU batch backup of the main board started.
l ISSU batch backup of main board in phase 1 over: The first phase for
the ISSU batch backup of the main board was over.
l ISSU batch backup of interface board in phase 1 started: The first phase
for the ISSU batch backup of the interface board started.
l ISSU batch backup of interface board in phase 1 over: The first phase
for the ISSU batch backup of the interface board was over.
l ISSU batch backup recovery of main board in phase 1 started: The first
phase for the ISSU configuration recovery of the main board started.
l ISSU batch backup recovery of main board in phase 1 over: The first
phase for the ISSU configuration recovery of the main board was over.
l ISSU batch backup recovery of interface board in phase 1 started: The
first phase for the ISSU configuration recovery of the interface board
started.
l ISSU batch backup recovery of interface board in phase 1 over: The
was over.
Time
Period from the system startup to now, in milliseconds.
Possible Causes
Cause:
The EFM module was performing the ISSU.
Procedure
----End
Issue 07 (2014-07-30)

153

Log Reference
23 EOAM1AG
23
EOAM1AG
About This Chapter

23.1 EOAM1AG/3/EOAMADP_FPGAFULL
23.2 EOAM1AG/5/ISSUSTATUS
Issue 07 (2014-07-30)

154

Log Reference
23 EOAM1AG
23.1 EOAM1AG/3/EOAMADP_FPGAFULL
Message
EOAM1AG/3/EOAM_ADP_FPGAFULL:FPGA table is Full. (mod:[ULONG], port:
[ULONG], vlan:[ULONG])
NOTE
Only the S5700HI supports this log.
Description
The number of logical entry resources reaches the upper limit.
Parameters
Parameter Name
Parameter Meaning
mod
Chip ID.
port
Port number.
vlan
VLAN ID.
Possible Causes
The number of ports added to the VLAN associated with the maintenance association (MA)
defined in 802.1ag exceeds the upper limit.
Procedure
Step 1 Remove unnecessary ports from the VLAN associated with the MA.
----End
23.2 EOAM1AG/5/ISSUSTATUS
Message
EOAM1AG/5/ISSUSTATUS:The ISSU working status of EOAM 1AG is [STRING]. (Time=
[ULONG])
Description
The ISSU working status of the EOAM 1AG module.
Issue 07 (2014-07-30)

155

Log Reference
23 EOAM1AG
Parameters
STRING
The ISSU working status of the EOAM 1AG module.

l ISSU batch backup of main board in phase 1 started: The first phase
for the ISSU batch backup of the main board started.
l ISSU batch backup of main board in phase 1 over: The first phase for
the ISSU batch backup of the main board was over.
l ISSU batch backup of interface board in phase 1 started: The first phase
for the ISSU batch backup of the interface board started.
l ISSU batch backup of interface board in phase 1 over: The first phase
for the ISSU batch backup of the interface board was over.
l ISSU batch backup recovery of main board in phase 1 started: The first
phase for the ISSU configuration recovery of the main board started.
l ISSU batch backup recovery of main board in phase 1 over: The first
phase for the ISSU configuration recovery of the main board was over.
l ISSU batch backup recovery of interface board in phase 1 started: The
started.
l ISSU batch backup recovery of interface board in phase 1 over: The
was over.
Time
Period from the system startup to now, in milliseconds.
Possible Causes
Cause:
The EOAM1AG module is performing the ISSU.
Procedure
----End
Issue 07 (2014-07-30)

156

Log Reference
24 ERPS (G.8032)
24
ERPS (G.8032)
About This Chapter

24.1 ERPS/5/PORTADDRINGFAILED
24.2 ERPS/5/PORTFWDSTATUS
24.3 ERPS/5/PORTSIGNALSTATUS
24.4 ERPS/5/TOPOCHANGE
Issue 07 (2014-07-30)

157

Log Reference
24 ERPS (G.8032)
24.1 ERPS/5/PORTADDRINGFAILED
Message
ERPS/5/PORTADDRINGFAILED:The interface failed to be added to the ring. (Interface=
[STRING], RingID=[ULONG])
Description
The interface failed to be added to the ERPS ring.
Parameters
Parameter Name
Parameter Meaning
Interface
Interface name.
RingID
ID of the ERPS ring.
Possible Causes
The lower layer resources of devices were exhausted.
Procedure
Step 1 Check whether the lower layer resources of devices were exhausted and plan the service capacity
of devices properly.
----End
24.2 ERPS/5/PORTFWDSTATUS
Message
ERPS/5/PORTFWDSTATUS:The forwarding status of the interface is changed. (RingID=
[ULONG], InterfaceName=[STRING], CurrentStatus=[STRING])
Description
The forwarding status of the interface added to the ERPS ring was changed.
Parameters
Parameter Name
Parameter Meaning
RingID
Ring ID.
Issue 07 (2014-07-30)

158

Log Reference
24 ERPS (G.8032)
Parameter Name
Parameter Meaning
InterfaceName
Interface name.
CurrentStatus
Current forwarding status of an interface.
Possible Causes
The ERPS forwarding status of an interface was changed from forwarding to blocked or from
blocked to forwarding.
Procedure
----End
24.3 ERPS/5/PORTSIGNALSTATUS
Message
ERPS/5/PORTSIGNALSTATUS:The signal status of the interface is changed. (RingID=
[ULONG], InterfaceName=[STRING], CurrentStatus=[STRING])
Description
The signal status of an interface added to an ERPS ring changed. The signal status includes
physical status and protocol status of an interface.
Parameters
Parameter Name
Parameter Meaning
RingID
Ring ID
InterfaceName
Interface name
CurrentStatus
Current signal status of an interface
Possible Causes
The physical status or protocol status of an interface added to the ERPS ring changed.
Procedure
Step 1 Check that whether the physical status or protocol status of the interface changes.
----End
Issue 07 (2014-07-30)

159

Log Reference
24 ERPS (G.8032)
24.4 ERPS/5/TOPOCHANGE
Message
ERPS/5/TOPOCHANGE:The ring topology changed. (RingID=[ULONG])
Description
The ERPS ring topology changed.
Parameters
Parameter Name
Parameter Meaning
RingID
ID of an ERPS ring
Possible Causes
The ERPS ring topology changed.
Procedure
Step 1 Check that whether status of interfaces on nodes on the RRPP ring changes.
----End
Issue 07 (2014-07-30)

160

Log Reference
25 ERRORDOWN
25
ERRORDOWN
About This Chapter

25.1 ERRDOWN/4/ERRDOWN_DOWNNOTIFY
25.2 ERRDOWN/4/ERRDOWN_DOWNRECOVER
Issue 07 (2014-07-30)

161

Log Reference
25 ERRORDOWN
25.1 ERRDOWN/4/ERRDOWN_DOWNNOTIFY
Message
ERRDOWN/4/ERRDOWN_DOWNNOTIFY: Notify interface to change status to error-down.
(InterfaceName=[STRING], Cause=[STRING])
Description
After an error-down event occurred on an interface, the log was displayed, indicating the
interface name and the error down cause.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
Interface name
Cause
Cause of the errordown event
Possible Causes
The faults detected by service modules triggered errordown events. The possible causes are as
follows:
l
EFM detected a link fault, which can be a fault that occurred on the remote end or a
threshold-crossing event.
The MSTP edge port received BPDU packets.
Procedure
Step 1 Run the display error-down recovery command to check the values of the interface and errordown cause fields.
l If the value of the error-down cause field is bpdu-protection, go to Step 2.
l If the value of the error-down cause field is port security, See Port Security to check
whether the nunber of secure MAC addresses reaches the threshold.
l If the value of the error-down cause field is efm-threshold-event, rectify the fault according
to the log 22.4 EFM/3/THRESHOLD.
l If the value of the error-down cause field is efm-remote-failure, rectify the fault according
to the log 22.2 EFM/2/NONTHRESHOLD.
Step 2 Check whether the interface is specified as an edge port.
l If the interface is not specified as an edge port, go to Step 3.
l If the interface is specified as an edge port, go to Step 4.
Step 3 Perform the following steps.
Issue 07 (2014-07-30)

162

Log Reference
25 ERRORDOWN
l Run:
interfaceinterface-type interface-num
The interface view is displayed.

l Run:
undo stp edged-port and undo shutdown
The edge port configuration is removed. Check whether the log still exists. If the log still
exists, go to Step 4.
Step 4 Collect log messages and contact Huawei technical support personnel.
----End
25.2 ERRDOWN/4/ERRDOWN_DOWNRECOVER
Message
ERRDOWN/4/ERRDOWN_DOWNRECOVER: Notify interface to recover state from errordown. (InterfaceName=[STRING])
Description
The errordown fault on an interface was rectified.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
Interface name
Possible Causes
The errordown fault on an interface was rectified.
Procedure
----End
Issue 07 (2014-07-30)

163

Log Reference
26 ETRUNK
26
ETRUNK
About This Chapter

26.1 ETRUNK/4/MBR_PHYSTAT_CHG
26.2 ETRUNK/4/MEMBER_STATE_CHG
26.3 ETRUNK/4/STATE_CHG
Issue 07 (2014-07-30)

164

Log Reference
26 ETRUNK
26.1 ETRUNK/4/MBR_PHYSTAT_CHG
Message
ETRUNK/4/MBR_PHYSTAT_CHG:The physical status of an E-Trunk member changed.
(MemberType=[STRING], MemberId=[ULONG], State=[STRING])
Description
The physical status of an E-Trunk member changed.
Parameters
MemberType
Indicates the member type. Only one member type is supported: EthTrunk.
MemberId
Indicates the member ID.
State
Indicates the state

l Up
l Down
Possible Causes
The physical status of an E-Trunk member (only the Eth-Trunk type is supported) changed.
Procedure
----End
26.2 ETRUNK/4/MEMBER_STATE_CHG
Message
ETRUNK/4/MEMBER_STATE_CHG:The status of an E-Trunk member changed.
(MemberType=[STRING], MemberId=[ULONG], OldState=[STRING], OldReason=
[STRING], NewState=[STRING], NewReason=[STRING])
Description
The status of an E-Trunk member changed.
Issue 07 (2014-07-30)

165

Log Reference
26 ETRUNK
Parameters
MemberType
Indicates the member type. Only one member type is supported: EthTrunk.
MemberId
Indicates the member ID.
OldState
Indicates the old state

l Backup: Indicates the backup state.
l Master: Indicates the master state.
l Negot: Indicates the negotiation state.
OldReason
Indicates the causes of the old state

l FORCE_BACKUP: Indicates the forcible backup state.
l FORCE_MASTER: Indicates the forcible master state.
l ETRUNK_INIT: Indicates the E-Trunk initialization.
l ETRUNK_BACKUP: Indicates that the E-Trunk is the backup.
l ETRUNK_MASTER: Indicates that the E-Trunk is the master.
l PEER_MEMBER_DOWN: Indicates that the peer member is Down.
l PEER_MEMBER_UP: Indicates that the peer member is Up.
NewState
Indicates the new state.

l Negot: Indicates the negotiation state.
NewReason
Indicates the causes of the new state

l FORCE_BACKUP: Indicates the forcible backup state.
l FORCE_MASTER: Indicates the forcible master state.
l ETRUNK_INIT: Indicates the E-Trunk initialization.
l ETRUNK_BACKUP: Indicates that the E-Trunk is the backup.
l ETRUNK_MASTER: Indicates that the E-Trunk is the master.
l PEER_MEMBER_DOWN: Indicates that the peer member is Down.
l PEER_MEMBER_UP: Indicates that the peer member is Up.
Possible Causes
The status of an E-Trunk member changed or the cause of status changed. For example, the ETrunk member was the master; when it was set to the forcible backup state through command
lines, it became the backup.
Procedure
----End
Issue 07 (2014-07-30)

166

Log Reference
26 ETRUNK
26.3 ETRUNK/4/STATE_CHG
Message
ETRUNK/4/STATE_CHG:The status of an E-Trunk changed. (ETrunkId=[ULONG],
OldState=[STRING], OldReason=[STRING], NewState=[STRING], NewReason=[STRING])
Description
The status of an E-Trunk changed.
Parameters
Parameter Name
Parameter Meaning
ETrunkId
Indicates the E-Trunk ID.
OldState
Indicates the old state

l Init: Indicates the initialization state.
OldReason
Indicates the causes of the old state

l PRI: Indicates the priority calculation.
l TIMEOUT: Indicates the timeout.
l PEER_TIMEOUT: Indicates that the peer device times out.
l INIT: Indicates the initialization.
NewState
Indicates the new state

l Init: Indicates the initialization state.
NewReason
Indicates the causes of the new state

l PRI: Indicates the priority calculation.
l TIMEOUT: Indicates the timeout.
l PEER_TIMEOUT: Indicates that the peer device times out.
l INIT: Indicates the initialization.
Possible Causes
The status of an E-Trunk changed or the cause of status changed. For example, the E-Trunk was
the backup; when the E-Trunk did not receive protocol packets from the peer device within the
timeout period, it became the master.
Issue 07 (2014-07-30)

167

Log Reference
26 ETRUNK
Procedure
----End
Issue 07 (2014-07-30)

168

Log Reference
27 EZOP
27
EZOP
About This Chapter

27.1 EZOP/3/UPGRADE_FAIL
27.2 EZOP/3/PROCESS_STOP
Issue 07 (2014-07-30)

169

Log Reference
27 EZOP
27.1 EZOP/3/UPGRADE_FAIL
Message
EZOP/3/UPGRADE_FAIL: Failed to upgrade device. (Reason=[STRING])
Description
The device fails to be upgraded using EasyDeploy.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the reason why the upgrade fails.
Possible Causes
The reasons for an EasyDeploy upgrade failure include but not limit to the following:
l
1: The file specified on the Commander or DHCP server does not exist.
2: The file server is unreachable or the password used to access the file server is incorrect.
3: The specified system software package already exists on the device.
Modify the configuration according to the reason displayed in the log. In an unconfigured
device deployment or faulty device replacement scenario, restart the device after modifying
the configuration. In a batch upgrade scenario, issue the EasyDeploy upgrade command.
Procedure
----End
27.2 EZOP/3/PROCESS_STOP
Message
EZOP/3/PROCESS_STOP: Easy-operation upgrade process has been stopped. (Reason=
[STRING])
Description
An EasyDeploy upgrade has stopped.
Issue 07 (2014-07-30)

170

Log Reference
27 EZOP
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the reason why the upgrade process stops.
Possible Causes
The reasons why an EasyDeploy upgrade stops include but not limit to the following:
l
1: The device detects inputs on the serial port.
2: The device already has a configuration file.
3: The device is upgrading using a USB flash drive.
If reason 1 is displayed, stops the operation on the serial port and restart the EasyDeploy
upgrade process. No input is allowed on the serial port during an EasyDeploy upgrade
process.
If reason 2 is displayed, delete the configuration file if it is unnecessary. In an unconfigured

device deployment or faulty replacement scenario, the device cannot have a configuration
file.
If reason 3 is displayed, select either EasyDeploy upgrade or USB-based upgrade.
Procedure
----End
Issue 07 (2014-07-30)

171

Log Reference
28 FILTER
28
FILTER
About This Chapter

28.1 FILTER/6/PKT_FLT_INFO
Issue 07 (2014-07-30)

172

Log Reference
28 FILTER
28.1 FILTER/6/PKT_FLT_INFO
Message
FILTER/6/PKT_FLT_INFO:Packet filter information: [packet-filter-information].
Description
Information on the filtered packets was displayed.
Parameters
Parameter Name
Parameter Meaning
[packet-filter-information]
Indicates the information about packet filtering.
Possible Causes
After the packet filtering rule was configured, each packet matching the rule for the first time
was logged. (The log was printed according to the ACL.)
Procedure
----End
Issue 07 (2014-07-30)

173

Log Reference
29 FSP
29
FSP
About This Chapter

29.1 FSP/4/MODIFY_PRIORITY
29.2 FSP/4/NO_PACKET
29.3 FSP/4/MODIFY_ID
29.4 FSP/4/TOPO_CHANGE
29.5 FSP/4/STACK_LEAVE
29.6 FSP/4/SWTICH_REBOOTING
29.8 FSP/4/NBR_DISCOVER
29.9 FSP/4/NBR_LOST
29.12 FSP/4/SPDU_LOST
Issue 07 (2014-07-30)

174

Log Reference
29 FSP
29.1 FSP/4/MODIFY_PRIORITY
Message
FSP/4/MODIFY_PRIORITY: Modify stack [ULONG1] priority as [ULONG2].
Description
The stack priority of the local device has been changed.
Parameters
Parameter Name
Parameter Meaning
[ULONG1]
Indicates the stack ID of the local device.
[ULONG2]
Indicates the stack priority of the device.
Possible Causes
The stack priority of a member device in a stack system has been changed.
Procedure
l
This log message is informational only, and no action is required.
----End
29.2 FSP/4/NO_PACKET
Message
FSP/4/NO_PACKET:Port [ULONG1] no receive packet [ULONG2] seconds.
Description
An interface does not receive any packets within a period.
Parameters
[ULONG1]
Indicates the number of a stack interface.
[ULONG2]
Indicates the period during which the stack interface does not receive any
packets.
Issue 07 (2014-07-30)

175

Log Reference
29 FSP
Possible Causes
The stack interface is physically Down.
Procedure
l
Check whether the stack card or stack cable is faulty. If so, replace the stack card or stack
cable.
----End
29.3 FSP/4/MODIFY_ID
Message
FSP/4/MODIFY_ID: Modify stack [ULONG1] as stack [ULONG2].
Description
The stack ID of the local device has been changed.
Parameters
Parameter Name
Parameter Meaning
[ULONG1]
Indicates the original stack ID.
[ULONG2]
Indicates the new stack ID.
Possible Causes
The stack ID of a member device in a stack system has been changed.
Procedure
l
----End
29.4 FSP/4/TOPO_CHANGE
Message
FSP/4/TOPO_CHANGE:Topo change from [ULONG1] to [ULONG2].
Description
The topology of a stack system has changed (from a ring topology to a chain topology or from
a chain topology to a ring topology).
Issue 07 (2014-07-30)

176

Log Reference
29 FSP
Parameters
Parameter Name
Parameter Meaning
[ULONG1]
Indicates the original topology of the stack system.
[ULONG2]
Indicates the new topology of the stack system.
Possible Causes
Some member devices have left or joined the stack system.
Procedure
l
No action is required if these devices left or joined the stack system normally.
----End
29.5 FSP/4/STACK_LEAVE
Message
FSP/4/STACK_LEAVE:Stack [ULONG] leave.
Description
A member device has left the stack system.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the stack ID of the local device.
Possible Causes
The stack interfaces of the member device are in Down state.
Procedure
l
----End
Message
FSP/4/SWTICH_REBOOTING:Different stack id [ULONG] assigned.
Issue 07 (2014-07-30)

177

Log Reference
29 FSP
Description
The master switch assigns two different stack IDs to the slave switch.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Stack ID.
Possible Causes
The device may be abnormal.
Procedure
l
The slave switch will restart automatically. In this case, if the slave switch joins the stack,
the master switch assigns the stack ID to the slave switch again. If the fault persists after
restart, contact Huawei technical personnel.
----End
Message
FSP/4/SWTICH_REBOOTING: Active master can't identify stack [ULONG].
Description
The master device cannot identify the stack member.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Stack ID.
Possible Causes
The device cannot join the stack.
Procedure
l
The device that cannot be identified will restart automatically and no action is required.
----End
Issue 07 (2014-07-30)

178

Log Reference
29 FSP
29.8 FSP/4/NBR_DISCOVER
Message
FSP/4/NBR_DISCOVER: Stack [ULONG1] NBR Discover on port : [ULONG2].
Description
The port of the member in the stack discovers a new neighbor.
Parameters
Parameter Name
Parameter Meaning
[ULONG1]
Stack ID.
[ULONG2]
Interface number.
Possible Causes
A new number joins the stack.
Procedure
l
This log is informational and no action is required.
----End
29.9 FSP/4/NBR_LOST
Message
FSP/4/NBR_LOST: Stack [ULONG1] NBR Lost on port : [ULONG2].
Description
The port of the member in the stack detects that a neighbor is lost.
Parameters
Parameter Name
Parameter Meaning
[ULONG1]
Stack ID.
[ULONG2]
Interface number.
Possible Causes
A member leaves the stack or is faulty.
Issue 07 (2014-07-30)

179

Log Reference
29 FSP
Procedure
l
----End
Message
FSP/4/SWTICH_REBOOTING:Slave stack [ULONG] collection timeout.
Description
The slave device connection expires.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Stack ID.
Possible Causes
An exception occurs on the device.
Procedure
l
The slave switch where an exception occurs will restart automatically. If the fault persists
after restart, contact Huawei technical personnel.
----End
Message
FSP/4/SWTICH_REBOOTING:Stack [ULONG] lost master spdu not in run state.
Description
Heartbeat packets from the master switch are lost on the slave switch when the slave switch is
in non-running state.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Stack ID.
Issue 07 (2014-07-30)

180

Log Reference
29 FSP
Possible Causes
An exception occurs on the slave switch or the master switch interface connected to the slave
switch is faulty.
Procedure
l
The slave switch where an exception occurs will restart automatically. If the fault persists
after restart, contact Huawei technical personnel.
----End
29.12 FSP/4/SPDU_LOST
Message
FSP/4/SPDU_LOST: Stack [ULONG] lost master spdu packet.
Description
SPDUs from the master device are lost on the member in the stack.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Stack ID.
Possible Causes
SPDUs from the master device are lost on the member in the stack.
Procedure
l
The device where an exception occurs will restart automatically and no action is required.
----End
Message
FSP/4/SWTICH_REBOOTING:Stack [ULONG] standalone.
Description
The device enters the standalone state.
Issue 07 (2014-07-30)

181

Log Reference
29 FSP
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Stack ID.
Possible Causes
The stack splits.
Procedure
l
----End
Issue 07 (2014-07-30)

182

Log Reference
30 FTPS
30
FTPS
About This Chapter

30.1 FTPS/5/ACL_DENY
30.2 FTPS/3/LOGINFAILED
30.3 FTPS/5/LOGIN_OK
30.4 FTPS/5/LOGOUT_OK
30.5 FTPS/5/REQUEST
30.6 FTPS/3/TRS_FAIL
Issue 07 (2014-07-30)

183

Log Reference
30 FTPS
30.1 FTPS/5/ACL_DENY
Message
FTPS/5/ACL_DENY:The TCP request was denied according to ACL rules. (IpAddress=
[IpAddress])
Description
The TCP request was denied according to the ACL rule.
Parameters
Parameter Name
Parameter Meaning
IpAddress
Indicates the IP address of the client.
Possible Causes
The TCP request does not match the ACL rule.
Procedure
----End
30.2 FTPS/3/LOGINFAILED
Message
FTPS/3/LOGINFAILED:Failed to login. (UserName="[string]", IpAddress=[string],
VpnInstanceName="[string]")
Description
An FTP user failed to log in to an FTP server.
Issue 07 (2014-07-30)

184

Log Reference
30 FTPS
Parameters
UserName
User name
user name.
IpAddress
User IP address
VpnInstanceName VPN instance name
Possible Causes
An FTP user failed to log in to an FTP server.
Procedure
Step 1 Check whether the user name and password are correct.
l If either the user name or the password is incorrect, enter the correct user name or password.
l If the user name and password are correct, collect log information and configuration
information, and contact Huawei technical support personnel.
----End
30.3 FTPS/5/LOGIN_OK
Message
FTPS/5/LOGIN_OK:The user succeeded in login. (UserName="[string]", IpAddress=[string],
VpnInstanceName="[string]")
Description
The user successfully logged in to an FTP server.
Parameters
Parameter Name
Parameter Meaning
UserName
IpAddress
Indicates the IP address of a user.
VpnInstanceName
Indicates the name of a VPN instance.
Possible Causes
The user successfully logged in to an FTP server.
Issue 07 (2014-07-30)

185

Log Reference
30 FTPS
Procedure
l
----End
30.4 FTPS/5/LOGOUT_OK
Message
FTPS/5/LOGOUT_OK:The user left. (UserName="[string]", IpAddress=[string],
VpnInstanceName="[string]", Reason="[string]")
Description
The user logged out of the FTP server.
Parameters
Parameter Name
Parameter Meaning
UserName
IpAddress
VpnInstanceName
Reason
Indicates the reason for the offline of the FTP user.
Possible Causes
The user logged out of the FTP server.
Procedure
l
----End
30.5 FTPS/5/REQUEST
Message
FTPS/5/REQUEST:The user had a request. (UserName="[string]", IpAddress=[string],
VpnInstanceName="[string]", Request=[string])
Description
The user sent a request message.
Issue 07 (2014-07-30)

186

Log Reference
30 FTPS
Parameters
Parameter Name
Parameter Meaning
UserName
IpAddress
VpnInstanceName
Request
Indicates the request of a user, such as PASS.
Possible Causes
After logging in to the FTP server, the user sent a request message to the FTP server.
Procedure
l
This log is informational only, and no action is required.
----End
30.6 FTPS/3/TRS_FAIL
Message
FTPS/3/TRS_FAIL:The user failed to transfer data. (UserName="[string]", IpAddress=[string],
VpnInstanceName="[string]", Reason="[string]")
Description
The user failed to transfer files through FTP.
Parameters
Parameter Name
Parameter Meaning
UserName
IpAddress
VpnInstanceName
Reason
Indicates the reason for the failure of file transfer.
Possible Causes
The user failed to transfer files through FTP.
Issue 07 (2014-07-30)

187

Log Reference
30 FTPS
Procedure
l
Check whether the transmission connection is normal or whether both ends can ping
through each other. If the connection is normal but the transmission fails, contact Huawei
technical personnel.
----End
Issue 07 (2014-07-30)

188

Log Reference
31 GRE
31
GRE
About This Chapter

31.1 GRE/6/GRE_CAMP
31.2 GRE/4/GRE_CAMPNUM_UNCAMP
31.3 GRE/4/GRE_MAXNUM_UNCAMP
31.4 GRE/4/GRE_UNIDE_SPEC_T
Issue 07 (2014-07-30)

189

Log Reference
31 GRE
31.1 GRE/6/GRE_CAMP
Message
GRE/6/GRE_CAMP:The specification of the GRE module is compatible, and lossless upgrade
is supported.
Description
The module was compatible in specifications and supported the lossless ISSU.
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
The GRE module was compatible in specifications.
Procedure
l
----End
31.2 GRE/4/GRE_CAMPNUM_UNCAMP
Message
GRE/4/GRE_CAMPNUM_UNCAMP:The compatible number of the GRE module is not
compatible.
Description
Data of two versions in the GRE module is not compatible according to the compatible ID check.
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
Data of two versions in the GRE module is not compatible according to the compatible ID check.
Issue 07 (2014-07-30)

190

Log Reference
31 GRE
Procedure
l
Lossy ISSU is performed, and no action is required.
----End
31.3 GRE/4/GRE_MAXNUM_UNCAMP
Message
GRE/4/GRE_MAXNUM_UNCAMP:The number of GRE tunnels [tunnel-number1]
configured on the old main control board is greater than the maximum number of GRE tunnels
[tunnel-number2] that can be configured on the new main control board.
Description
The number of GRE tunnels on the main control board running the system software of the
previous version before the master-slave switchover was larger than the maximum number of
GRE tunnels permitted on the main control board running the system software of the new version.
Parameters
[tunnel-number1]
Number of the current GRE tunnels on the main control board running
the system software of the previous version before the master-slave
switchover
[tunnel-number2]
Maximum number of configurable GRE tunnels permitted on the main

control board running the system software of the new version after the
master-slave switchover
Possible Causes
The number of permitted GRE tunnels on the main control board is reduced in the new system
software version. As a result, the number of GRE tunnels on the master main control board
running the old system software version was larger than the maximum number of GRE tunnels
permitted on the main control board running the new system software version.
Procedure
l
Check specifications and configurations and ensure that, after the mater-slave switchover
the maximum number of configurable GRE tunnels on the main control board running the
system software of the new version is larger than the number of GRE tunnels on the main
control board running the system software of the previous version. You can purchase more
PAF files/licenses from Huawei to make specifications satisfied. Otherwise, some
----End
Issue 07 (2014-07-30)

191

Log Reference
31 GRE
31.4 GRE/4/GRE_UNIDE_SPEC_T
Message
GRE/4/GRE_UNIDE_SPEC_T:Obtain an unknown object type when parsing the GRE tunnel
specification. (Type=[ULONG])
Description
An unknown object type was obtained in the process of parsing the specifications of the TLVencapsulated GRE tunnel.
Parameters
Parameter Name
Parameter Meaning
Type
Object type
Possible Causes
An incorrect object type was obtained.
Procedure
l
Contact Huawei technical support personnel.
----End
Issue 07 (2014-07-30)

192

Log Reference
32 GRESM
32
GRESM
About This Chapter

32.1 GRESM/3/TokenConflict
Issue 07 (2014-07-30)

193

Log Reference
32 GRESM
32.1 GRESM/3/TokenConflict
Message
GRESM/3/TokenConflict: Tokens resources conflicted when a specified token was applied for.
(OldAppId=[ULONG], TokenHandle=[ULONG], NewAppId=[ULONG], TunnelID=
[ULONG]).
Description
When being saved to the slave main control board, the token resource allocated to a service
module conflicted with the token resource being used by another service module on the slave
main control board.
Parameters
Parameter Name
Parameter Meaning
OldAppId
ID of the service module that is using the token resource.
TokenHandle
Token space address.
NewAppId
ID of the service module to which the token resource is allocated.
TunnelID
Tunnel ID.
Possible Causes
The token resource allocated to the service module had the same token ID as the token resource
being used by another service module on the slave main control board.
Procedure
l
----End
Issue 07 (2014-07-30)

194

Log Reference
33 GRSA
33
GRSA
About This Chapter

33.1 GRSA/4/COPY_PUBPRIVKEY_FAILURE
33.2 GRSA/4/CREATE_PRIVKEY_FAILURE
33.3 GRSA/4/DECODE_PRIVKEY_FAILURE
33.4 GRSA/4/DECODE_PUBKEY_FAILURE
33.5 GRSA/4/DECRYPT_PRIVKEY_FAILURE
33.6 GRSA/4/ENCODE_PRIVKEY_FAILURE
33.7 GRSA/4/ENCODE_PUBKEY_FAILURE
33.8 GRSA/4/ENCRYPT_PRIVKEY_FAILURE
33.9 GRSA/4/EXTRACT_PRIVKEY_FAILURE
33.10 GRSA/4/KEY_PAIR_GEN_FAILED
33.11 GRSA/6/KEY_PAIR_GENERATE_SUCCESS
33.12 GRSA/4/KEYPAIR_NOT_EXISTS
33.13 GRSA/4/PEM_DECODE_FAILURE
33.14 GRSA/4/PEM_ENCODE_FAILURE
33.15 GRSA/4/REALTIME_BAK_SEND_FAILURE
33.16 GRSA/4/SAVE_KEYPAIR_FAILURE
33.17 GRSA/6/SAVE_KEYPAIR_SUCCESS
Issue 07 (2014-07-30)

195

Log Reference
33 GRSA
33.1 GRSA/4/COPY_PUBPRIVKEY_FAILURE
Message
GRSA/4/COPY_PUBPRIVKEY_FAILURE: Copy public or private key from key-pair with
label [label] failed.
Description
Failed to copy RSA Key.
Parameters
Parameter Name
Parameter Meaning
label
Indicates the unique label name associated with a key-pair created.
Possible Causes
The possible cause is due to an internal error like memory allocation failure, invalid key or
invalid algorithm.
Procedure
Step 1 Collect the log.
----End
33.2 GRSA/4/CREATE_PRIVKEY_FAILURE
Message
GRSA/4/CREATE_PRIVKEY_FAILURE: Constructing the PKCS structure from private key
failed
Description
Failed to construct the Public-key Cryptography Standard (PKCS) private key.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

196

Log Reference
33 GRSA
Possible Causes
The possible cause is due to an internal error like memory allocation failure, invalid version or
encoding failure.
Procedure
----End
33.3 GRSA/4/DECODE_PRIVKEY_FAILURE
Message
GRSA/4/DECODE_PRIVKEY_FAILURE: Decode private key from byte stream failed
Description
Failed to decode RSA private key from byte stream.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The possible cause is due to an internal error.
Procedure
----End
33.4 GRSA/4/DECODE_PUBKEY_FAILURE
Message
GRSA/4/DECODE_PUBKEY_FAILURE: Decode public key from byte stream failed
Issue 07 (2014-07-30)

197

Log Reference
33 GRSA
Description
Failed to decode RSA public key from byte stream.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
33.5 GRSA/4/DECRYPT_PRIVKEY_FAILURE
Message
GRSA/4/DECRYPT_PRIVKEY_FAILURE: Decrypting the encrypted private key in PKCS
private key structure failed
Description
Failed to decrypt Public-key Cryptography Standard (PKCS) private key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The possible cause is due to internal error like memory allocation fail, invalid algorithm or
decrypt failure.
Procedure
----End
Issue 07 (2014-07-30)

198

Log Reference
33 GRSA
33.6 GRSA/4/ENCODE_PRIVKEY_FAILURE
Message
GRSA/4/ENCODE_PRIVKEY_FAILURE: Encode private key to byte stream failed
Description
Failed to encode private key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
33.7 GRSA/4/ENCODE_PUBKEY_FAILURE
Message
GRSA/4/ENCODE_PUBKEY_FAILURE: Encode public key to byte stream failed
Description
Failed to encode RSA public key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Issue 07 (2014-07-30)

199

Log Reference
33 GRSA
Procedure
----End
33.8 GRSA/4/ENCRYPT_PRIVKEY_FAILURE
Message
GRSA/4/ENCRYPT_PRIVKEY_FAILURE: Encrypting the private key in PKCS private key
structure failed
Description
Failed to Encrypt Public-key Cryptography Standard (PKCS) private key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
33.9 GRSA/4/EXTRACT_PRIVKEY_FAILURE
Message
GRSA/4/EXTRACT_PRIVKEY_FAILURE: Extracting the private key from the PKCS
structure failed
Description
Failed to extract Public-key Cryptography Standard (PKCS) private key.
Issue 07 (2014-07-30)

200

Log Reference
33 GRSA
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The possible cause is due to internal error like invalid algorithm, memory allocation failure or
fail to decode.
Procedure
----End
33.10 GRSA/4/KEY_PAIR_GEN_FAILED
Message
GRSA/4/KEY_PAIR_GEN_FAILED: Generate RSA key-pair with label [label-name] failed.
Description
Key pair generation failed.
Parameters
Parameter Name
Parameter Meaning
[label-name]
Indicates the unique name associated with an RSA key-pair created.
Possible Causes
The possible cause is due to Internal error like memory allocation failure, invalid modulus, fail
to initialize library or invalid algorithm.
Procedure
----End
Issue 07 (2014-07-30)

201

Log Reference
33 GRSA
33.11 GRSA/6/KEY_PAIR_GENERATE_SUCCESS
Message
GRSA/6/KEY_PAIR_GENERATE_SUCCESS:Generate RSA key-pair with label [labelname] success.
Description
Successful creation of key pair.
Parameters
Parameter Name
Parameter Meaning
[label-name]
Indicates the unique name associated with a key-pair created.
Possible Causes
Key pair is generated.
Procedure
l
----End
33.12 GRSA/4/KEYPAIR_NOT_EXISTS
Message
GRSA/4/KEYPAIR_NOT_EXISTS: RSA key-pair with label [label-name] does not exists
Description
Key-pair with label does not exists.
Parameters
Parameter Name
Parameter Meaning
[label-name]
Possible Causes
The possible cause is due to key pair not created.
Issue 07 (2014-07-30)

202

Log Reference
33 GRSA
Procedure
l
Create a key pair before you delete the key pair.
----End
33.13 GRSA/4/PEM_DECODE_FAILURE
Message
GRSA/4/PEM_DECODE_FAILURE: Decoding the private key from PEM format failed
Description
Failed to decode PEM.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
33.14 GRSA/4/PEM_ENCODE_FAILURE
Message
GRSA/4/PEM_ENCODE_FAILURE: Encode the private key to PEM format failed
Description
Failed to encode PEM.
Issue 07 (2014-07-30)

203

Log Reference
33 GRSA
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
33.15 GRSA/4/REALTIME_BAK_SEND_FAILURE
Message
GRSA/4/REALTIME_BAK_SEND_FAILURE: Send RSA key-pair with label [label-name]
for real time backup failed.
Description
Real time backup failed.
Parameters
Parameter Name
Parameter Meaning
[label-name]
Possible Causes
The possible cause is due to an internal errors like:
l
Memory allocation failure
Failed to send key to slave board
Failed to send key to IO board
Fail to receive ACK from slave board
Fail to create key-pair file in slave board because of low disk space
Procedure
Step 1 Check if slave is normal and has enough free space in its flash.
Issue 07 (2014-07-30)

204

Log Reference
33 GRSA
Step 2 If the problem still continues, contact Huawei technical support personnel.
----End
33.16 GRSA/4/SAVE_KEYPAIR_FAILURE
Message
GRSA/4/SAVE_KEYPAIR_FAILURE: Save RSA key-pair to file with label [label-name]
failed.
Description
Failed to save the key pair to file.
Parameters
Parameter Name
Parameter Meaning
[label-name]
Possible Causes
The possible cause is due to an internal error like fail to save in file or no space left to create a
file.
Procedure
Step 1 Check for free space available in master and slave flash.
Step 2 If problem still continues, contact Huawei technical support personnel.
----End
33.17 GRSA/6/SAVE_KEYPAIR_SUCCESS
Message
GRSA/6/SAVE_KEYPAIR_SUCCESS: Save RSA key-pair to file with label [label-name]
success.
Description
Key pair save to file successful.
Issue 07 (2014-07-30)

205

Log Reference
33 GRSA
Parameters
Parameter Name
Parameter Meaning
[label-name]
Possible Causes
Normal Flow. No error. Key-pair is successfully saved into a file.
Procedure
l
This log message is informational only, and no action is required
----End
Issue 07 (2014-07-30)

206

Log Reference
34 HA
34
HA
About This Chapter

34.1 HA/6/RESTART
34.2 HA/5/RESTSLA
34.3 HA/5/RSTSLA
34.4 HA/6/SWITCH_CHASSIS
34.5 HA/6/SWITCHOVER
Issue 07 (2014-07-30)

207

Log Reference
34 HA
34.1 HA/6/RESTART
Message
HA/6/RESTART:When deciding whether to restart slave board, the user choose [Y/N].
Description
The user determined whether to reset the standby main board.
Parameters
[Y/N]
Users chosed [Y/N] to determine whether to reset the standby main board.
l Y: indicates that the user determines to reset the standby main board.
l N: indicates that the user determines to cancel the operation.
Possible Causes
After running the slave restart command, the user needs to confirm.
Procedure
----End
34.2 HA/5/RESTSLA
Message
HA/5/RESTSLA:Rebooted the slave board. (Slot=[STRING])
Description
The slave board was restarted.
Parameters
Parameter Name
Parameter Meaning
Slot
Indicates the lost where the slave board resides.
Issue 07 (2014-07-30)

208

Log Reference
34 HA
Possible Causes
The slave switchover command was run, and the slave board restarted after Y was typed.
Procedure
----End
34.3 HA/5/RSTSLA
Message
HA/5/RSTSLA:Rebooted the slave board, because the messages in the queue were too much.
(Slot=[STRING])
Description
The slave board was restarted.
Parameters
Parameter Name
Parameter Meaning
Slot
Possible Causes
Failed to resend for many times because the message queue was full.
Procedure
Step 1 The message queue is full and the HA restarts the slave board.
----End
34.4 HA/6/SWITCH_CHASSIS
Message
HA/6/SWITCH_CHASSIS:When deciding whether to switch the active main board to the
standby main board in [Slot], the user chose [Y/N].
Description
The user needs to confirm whether to perform active/standby switchover.
Issue 07 (2014-07-30)

209

Log Reference
34 HA
Parameters
[Slot]
[Y/N]
Users chosed [Y/N] to switch the active main board to the standby main
board.
l Y: indicates that the user determines to switch the active main board
to the standby main board.
l N: indicates that the user determines to cancel the operation.
Possible Causes
After running the slave switchover chassis command, the user needs to confirm.
Procedure
----End
34.5 HA/6/SWITCHOVER
Message
HA/6/SWITCHOVER:When deciding whether to switch slave to master, the user choose
[STRING].
Description
The user needs to confirm whether to perform active/standby switchover.
Parameters
[STRING]
Users chose [STRING] to determine whether to perform the active/

standby switchover.
Y: indicates that the user determines to perform the active/standby
switchover.
N: indicates that the user determines to cancel the operation.
Possible Causes
After running the slave switchover command, the user needs to confirm.
Issue 07 (2014-07-30)

210

Log Reference
34 HA
Procedure
----End
Issue 07 (2014-07-30)

211

Log Reference
35 HTTP
35
HTTP
About This Chapter

35.1 HTTP/4/FILETRANSFERFAILURE
35.2 HTTP/5/FILETRANSFEROK
35.3 HTTP/3/LOGINFAIL
35.4 HTTP/6/LOGINOK
35.5 HTTP/5/LOGIN_TIMEOUT
35.6 HTTP/4/VERIFYFAIL
Issue 07 (2014-07-30)

212

Log Reference
35 HTTP
35.1 HTTP/4/FILETRANSFERFAILURE
Message
HTTP/4/FILETRANSFERFAILURE: Failed to transfer file by HTTP. ( UserName=
[UserName], IPAddress=[IPAddress], FileName=[FileName])
Description
Failed to transmit files using HTTP.
Parameters
Parameter Name
Parameter Meaning
UserName
User name
IPAddress
IP address of a user
FileName
Name of the file to be uploaded or downloaded
Possible Causes
File transmission failed, which may be caused because the network is unstable or the the browser
is closed during the file transmission.
Procedure
l
Collect log messages and contact Huawei technical support personnel.
----End
35.2 HTTP/5/FILETRANSFEROK
Message
HTTP/5/FILETRANSFEROK: Succeeded in transferring file by HTTP. ( UserName=
[UserName], IPAddress=[IPAddress], FileName=[FileName])
Description
Succeeded in transmitting files using HTTP.
Issue 07 (2014-07-30)

213

Log Reference
35 HTTP
Parameters
Parameter Name
Parameter Meaning
UserName
User name
IPAddress
FileName
Name of the file to be uploaded or downloaded
Possible Causes
Uploading or downloading files using HTTP is successful.
Procedure
l
----End
35.3 HTTP/3/LOGINFAIL
Message
HTTP/3/LOGINFAIL: User login failed. (UserName=[UserName], IPAddr=[IPAddr], Info=
[Info])
Description
A user failed to log in.
Parameters
Parameter Name
Parameter Meaning
UserName
User name
IPAddr
User IP address
Info
Lgin failed information
Possible Causes
A user failed to log in by using HTTP.
Procedure
l If the user name and password are correct, go to Step 2.
Issue 07 (2014-07-30)

214

Log Reference
35 HTTP
l If the user name or password is incorrect, use the correct user name and password to log in
again. If the user successfully logs in, go to Step 4. Otherwise, go to Step 2.
Step 2 Check whether the HTTP configuration on the server to which the user attempts to log in is
correct.
1.
Run the display http server command to check whether HTTP is enabled.
l If HTTP is enabled, go to Step b.
l If HTTP is disabled, run the http server enable command to enable HTTP. Then, use
the user name and password to log in. If the login succeeds, go to Step 4. Otherwise, go
to Step b.
NOTE
If running the http server enable command fails, run the dir [ /all ] [ filename ] command to
check whether an HTTP loading file exists. The default file is web.7z. If the default HTTP loading
file does not exist, do as follows to handle the problem:
l If a non-default HTTP loading file exists, run the http server load file-name command to
load the file.
l If no HTTP loading file exists, upload an HTTP loading file by using FTP.
2.
Run the display current-configuration | include local-user command to check whether

the HTTP user name and password exist.
l If the HTTP user name and password exist, go to Step 3.
l If the HTTP user name or password does not exist, run the local-user user-name
password { irreversible-cipher | cipher } password command to create the user name
and password. Run the local-user user-name service-type http command to specify
this user as an HTTP user. Then, use the user name and password to log in. If the login
succeeds, go to Step 4. Otherwise, go to Step 3.
Step 3 Collect displayed information and contact Huawei technical support personnel.
Step 4 End.
----End
35.4 HTTP/6/LOGINOK
Message
HTTP/6/LOGINOK: User logged in successfully.(UserName=[UserName],IPAddr=[IPAddr]).
Description
A user successfully logged in.
Parameters
Parameter Name
Parameter Meaning
UserName
User name
Issue 07 (2014-07-30)

215

Log Reference
35 HTTP
Parameter Name
Parameter Meaning
IPAddr
User IP address
Possible Causes
A user successfully logged in by using HTTP.
Procedure
l
----End
35.5 HTTP/5/LOGIN_TIMEOUT
Message
HTTP/5/LOGIN_TIMEOUT:HTTP user timed out. (UserName=[STRING], ConfigTimeout
(min)=[INTEGER])
Description
An HTTP user was disconnected from the network.
Parameters
Parameter Name
Parameter Meaning
UserName
User name of the HTTP user
ConfigTimeout(min)
Timeout interval, in minutes
Possible Causes
The HTTP connection timed out.
Procedure
Step 1 The trap is informational only, and no action is required.
----End
35.6 HTTP/4/VERIFYFAIL
Message
HTTP/4/VERIFYFAIL: Failed to validate HTTP verification code. (UserName=[UserName],
IPAddress=[IPAddress])
Issue 07 (2014-07-30)

216

Log Reference
35 HTTP
Description
Failed to log in to an HTTP server.
Parameters
Parameter Name
Parameter Meaning
UserName
User name
IPAddress
Possible Causes
The user failed to log in to the HTTP server due to the authentication failure.
Procedure
l
If the authentication fails with a correct password, collect log messages and contact Huawei
technical support personnel.
----End
Issue 07 (2014-07-30)

217

Log Reference
36 HWCM
36
HWCM
About This Chapter

36.1 HWCM/4/CCOPY
36.2 HWCM/5/TRAPLOG
Issue 07 (2014-07-30)

218

Log Reference
36 HWCM
36.1 HWCM/4/CCOPY
Message
HWCM/4/CCOPY:Configuration copy. (OperationType=[integer], OptTime=[TIMETICK],
OptState=[integer], OptEndTime=[TIMETICK])
Description
The copy operation was recorded.
Parameters
Parameter Name
Parameter Meaning
OperationType
indicates the type of the operation.
OptTime
indicates the time of the operation.
OptState
indicates the status of the operation.
OptEndTime
indicates the end time of the operation.
Possible Causes
The user can save the configuration file through MIB.
Procedure
----End
36.2 HWCM/5/TRAPLOG
Message
HWCM/5/TRAPLOG:OID [oid] configure changed. (EventIndex=[integer], CommandSource=
[integer], ConfigSource=[integer], ConfigDestination=[integer])
Description
The configuration changed.
Issue 07 (2014-07-30)

219

Log Reference
36 HWCM
Parameters
Parameter Name
Parameter Meaning
oid
indicates the trap OID.
EventIndex
indicates the index of an event.
CommandSource
indicates the source of a command.
ConfigSource
indicates the source of the configuration.
ConfigDestination
indicates the destination of the configuration.
Possible Causes
The log was generated when the configuration changed.
Procedure
----End
Issue 07 (2014-07-30)

220

Log Reference
37 IFNET
37
IFNET
About This Chapter

37.1 IFNET/4/ACOAM_ENABLE_FAIL
37.2 IFNET/5/ACOAM_STATE_CHANGE
37.3 IFNET/6/APP_NOTIFY_FAULT
37.4 IFNET/4/BOARD_DISABLE
37.5 IFNET/4/BOARD_ENABLE
37.6 IFNET/4/BWRATE_IN_RESUME
37.7 IFNET/4/BWRATE_IN_RISING
37.8 IFNET/4/BWRATE_OUT_RESUME
37.9 IFNET/4/BWRATE_OUT_RISING
37.10 IFNET/4/CARD_DISABLE
37.11 IFNET/4/CARD_ENABLE
37.12 IFNET/4/CHANGE_ENCAP
37.13 IFNET/4/FLOWDOWN
37.14 IFNET/4/FLOWUP
37.15 IFNET/4/IF_DISABLE
37.16 IFNET/4/IF_ENABLE
37.17 IFNET/4/IF_HOTTASK_CREATE
37.18 IFNET/4/IF_HOTTASK_DELETE
37.19 IFNET/6/IF_INFO_CHANGE
37.20 IFNET/4/IF_STATE
Issue 07 (2014-07-30)

221

Log Reference
37 IFNET
37.21 IFNET/4/LINK_STATE
37.22 IFNET/4/LINKNO_STATE
37.23 IFNET/6/LSP_STATE_CHANGE
37.24 IFNET/4/NOTIFY_BFD_FAIL
37.25 IFNET/4/NTF_ACOAM_STATE_FAIL
37.26 IFNET/6/NTF_STATE_CHANGE
37.27 IFNET/4/OUT_OF_MEMORY
37.28 IFNET/6/PW_STATE_CHANGE
37.29 IFNET/6/REPEAT_NOTIFY
Issue 07 (2014-07-30)

222

Log Reference
37 IFNET
37.1 IFNET/4/ACOAM_ENABLE_FAIL
Message
IFNET/4/ACOAM_ENABLE_FAIL:Failed to notify Application module of the AC OAM CFG
event. (Application=[STRING])
Description
Failed to notify the application module of the AC OAM configuration.
Parameters
Parameter Name
Parameter Meaning
Application
indicates the application module name.
Possible Causes
Failed to notify the application module of the AC OAM configuration.
Procedure
Step 1 Run the display diagnostic-information command, save the command output, and then contact
----End
37.2 IFNET/5/ACOAM_STATE_CHANGE
Message
IFNET/5/ACOAM_STATE_CHANGE:The OAM Manager detected interface states change.
(InterfaceName=[STRING], State=[STRING])
Description
The OAM manager detected that the interface status changed.
Parameters
InterfaceName
Issue 07 (2014-07-30)
indicates the interface name.

223

Log Reference
37 IFNET

State
indicates the status of the link layer protocol on the interface. The details
are as follows:
1. Up: indicates that the status of the link layer protocol on the interface
is normal.
2. Down: indicates that the status of the link layer protocol on the interface
is abnormal.
Possible Causes
After the oam detect command was run, the OAM manager received the message that AC OAM
status changed.
Procedure
----End
37.3 IFNET/6/APP_NOTIFY_FAULT
Message
IFNET/6/APP_NOTIFY_FAULT:The Application module [module] of the interface [interfacename].
Description
The application module reported the fault.
Parameters
Parameter Name
Parameter Meaning
[module]
indicates the module name.
[interface-name]
Possible Causes
The application module reported the fault.
Procedure
----End
Issue 07 (2014-07-30)

224

Log Reference
37 IFNET
37.4 IFNET/4/BOARD_DISABLE
Message
IFNET/4/BOARD_DISABLE:Board [board-number] has been unavailable.
Description
The board became unavailable.
Parameters
Parameter Name
Parameter Meaning
[board-number]
indicates the interface board number.
Possible Causes
The interface board was pulled out.
Procedure
----End
37.5 IFNET/4/BOARD_ENABLE
Message
IFNET/4/BOARD_ENABLE:Board [board-number] has been available.
Description
The board became available.
Parameters
Parameter Name
Parameter Meaning
[board-number]
Possible Causes
The interface board was plugged in the frame.
Issue 07 (2014-07-30)

225

Log Reference
37 IFNET
Procedure
----End
37.6 IFNET/4/BWRATE_IN_RESUME
Message
IFNET/4/BWRATE_IN_RESUME:Interface input flow bandwidth usage was restored to the
log threshold. (Interface=[interface], BandWidthUsage=[usage], LogThreshold=[threshod])
Description
Bandwidth usage for traffic received by an interface was lower than the configured threshold
for generating a log about bandwidth usage.
Parameters
Parameter Name
Parameter Meaning
Interface
Interface name
BandWidthUsage
Current bandwidth usage
LogThreshold
Configured threshold
Possible Causes
Bandwidth usage for traffic received by an interface is lower than the configured threshold for
generating a log about bandwidth usage.
Procedure
----End
37.7 IFNET/4/BWRATE_IN_RISING
Message
IFNET/4/BWRATE_IN_RISING:Interface input flow bandwidth usage exceeded the log
threshold. (Interface=[interface], BandWidthUsage=[usage], LogThreshold=[threshod])
Issue 07 (2014-07-30)

226

Log Reference
37 IFNET
Description
Bandwidth usage for traffic received by an interface exceeded the configured threshold for
Parameters
Parameter Name
Parameter Meaning
Interface
Interface name
BandWidthUsage
LogThreshold
Possible Causes
Bandwidth usage for traffic received by an interface exceeds the configured threshold for
Procedure
Step 1 If the log named BWRATE_IN_RESUME is not displayed for a long time after the preceding
log is displayed, expand the device.
----End
37.8 IFNET/4/BWRATE_OUT_RESUME
Message
IFNET/4/BWRATE_OUT_RESUME:Interface output flow bandwidth usage was restored to
the log threshold. (Interface=[interface], BandWidthUsage=[usage], LogThreshold=[threshod])
Description
Bandwidth usage for traffic sent by an interface was lower than the configured threshold for
Parameters
Parameter Name
Parameter Meaning
Interface
Interface name
BandWidthUsage
LogThreshold
Issue 07 (2014-07-30)

227

Log Reference
37 IFNET
Possible Causes
Bandwidth usage for traffic sent by an interface is lower than the configured configured threshold
for generating a log about bandwidth usage.
Procedure
----End
37.9 IFNET/4/BWRATE_OUT_RISING
Message
IFNET/4/BWRATE_OUT_RISING:Interface output flow bandwidth usage exceeded the log
threshold. (Interface=[interface], BandWidthUsage=[usage], LogThreshold=[threshod])
Description
Bandwidth usage for traffic sent by an interface exceeded the configured threshold for generating
a log about bandwidth usage.
Parameters
Parameter Name
Parameter Meaning
Interface
Interface name
BandWidthUsage
LogThreshold
Possible Causes
Bandwidth usage for traffic sent by an interface exceeds the configured threshold of the
bandwidth usage upper limit.
Procedure
Step 1 If the log named BWRATE_OUT_RESUME is not displayed for a long time after the preceding
log is displayed, expand the device.
----End
37.10 IFNET/4/CARD_DISABLE
Issue 07 (2014-07-30)

228

Log Reference
37 IFNET
Message
IFNET/4/CARD_DISABLE:Board [board-number] card [card-number] has been unavailable.
Description
The interface card on the board became unavailable.
Parameters
Parameter Name
Parameter Meaning
[board-number]
[card-number]
indicates the interface card number.
Possible Causes
The interface card was pulled out.
Procedure
----End
37.11 IFNET/4/CARD_ENABLE
Message
IFNET/4/CARD_ENABLE:Board [board-number] card [card-number] has been available.
Description
The interface card on the board became available.
Parameters
Parameter Name
Parameter Meaning
[board-number]
[card-number]
indicates the interface card number.
Possible Causes
The interface card was plugged in the board.
Issue 07 (2014-07-30)

229

Log Reference
37 IFNET
Procedure
----End
37.12 IFNET/4/CHANGE_ENCAP
Message
IFNET/4/CHANGE_ENCAP:The user performed the configuration that will change the
encapsulation protocol of the link and then selected [STRING].
Description
The current configuration can be validated only after it is confirmed because it will change the
link layer protocol.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates whether the link layer protocol is changed.

l Y: changes the link layer protocol.
l N: does not change the link layer protocol.
Possible Causes
The user intends to change the link layer protocol.
Procedure
----End
37.13 IFNET/4/FLOWDOWN
Message
IFNET/4/FLOWDOWN:The state of interface turned to DOWN because of FLOW DOWN.
(Interface=[STRING], SysUpTime=[ULONG])
Description
The status of the interface changed.
Issue 07 (2014-07-30)

230

Log Reference
37 IFNET
Parameters
Parameter Name
Parameter Meaning
Interface
SysUpTime
indicates the startup time of the system.
Possible Causes
The status of the traffic changed.
Procedure
----End
37.14 IFNET/4/FLOWUP
Message
IFNET/4/FLOWUP:The state of interface turned to UP because of FLOW UP. (Interface=
[STRING], SysUpTime=[ULONG])
Description
Parameters
Parameter Name
Parameter Meaning
Interface
SysUpTime
indicates the startup time of the system.
Possible Causes
The status of the traffic changed.
Procedure
----End
37.15 IFNET/4/IF_DISABLE
Issue 07 (2014-07-30)

231

Log Reference
37 IFNET
Message
IFNET/4/IF_DISABLE:Interface [interface-name] has been unavailable.
Description
The interface became unavailable.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
Procedure
----End
37.16 IFNET/4/IF_ENABLE
Message
IFNET/4/IF_ENABLE:Interface [interface-name] has been available.
Description
The interface became available.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

232

Log Reference
37 IFNET
37.17 IFNET/4/IF_HOTTASK_CREATE
Message
IFNET/4/IF_HOTTASK_CREATE:Task [task-name] has created.
Description
The HOT task was created.
Parameters
Parameter Name
Parameter Meaning
[task-name]
The name of HOT task.
Possible Causes
The HOT task was created.
Procedure
----End
37.18 IFNET/4/IF_HOTTASK_DELETE
Message
IFNET/4/IF_HOTTASK_DELETE:Task [task-name] has deleted.
Description
The HOT task was deleted.
Parameters
Parameter Name
Parameter Meaning
[task-name]
The name of HOT task.
Possible Causes
The HOT task was deleted.
Issue 07 (2014-07-30)

233

Log Reference
37 IFNET
Procedure
----End
37.19 IFNET/6/IF_INFO_CHANGE
Message
IFNET/6/IF_INFO_CHANGE:The interface [interface-name] changed the [property-name]
from [old-value] to [new-value].
Description
The value of the property of the interface changed.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
interface name
[property-name]
property name
[old-value]
old value of the property
[new-value]
new value of the property
Possible Causes
The value of the property of the interface changed.
Procedure
----End
37.20 IFNET/4/IF_STATE
Message
IFNET/4/IF_STATE:Interface [interface-name] has turned into [state] state.
Description
Issue 07 (2014-07-30)

234

Log Reference
37 IFNET
Parameters
[interface-name]
[state]
indicates the status of the link layer protocol. The details are as follows
is normal.
is abnormal.
Possible Causes
Procedure
----End
37.21 IFNET/4/LINK_STATE
Message
IFNET/4/LINK_STATE:The line protocol [line-protocol] on the interface [interface-name] has
entered the [state] state.
Description
The link layer protocol of the interface changed.
Parameters
[line-protocol]
indicates the name of the link layer protocol.
[interface-name]
[state]
indicates the status of the link layer protocol. The details are as follows:
is normal.
is abnormal.
Issue 07 (2014-07-30)

235

Log Reference
37 IFNET
Possible Causes
The link layer protocol of the interface changed.
Procedure
----End
37.22 IFNET/4/LINKNO_STATE
Message
IFNET/4/LINKNO_STATE:The line protocol on the interface [interface-name] has entered the
[state] state.
Description
The PPP link protocol(PPP IPCP excluded) status of the interface changed; when the network
protocol is IP, but non-PPP link protocol status of the interface changed.
Parameters
[interface-name]
[state]
indicates the status of the link layer protocol. The details are as follows
is normal.
is abnormal.
Possible Causes
The PPP link protocol(PPP IPCP excluded) status of the interface changed; when the network
protocol is IP, but non-PPP link protocol status of the interface changed.
Procedure
----End
37.23 IFNET/6/LSP_STATE_CHANGE
Issue 07 (2014-07-30)

236

Log Reference
37 IFNET
Message
IFNET/6/LSP_STATE_CHANGE:The OAM Manager received the BFD for LSP state changed
message. (State=[STRING], Session=[ULONG])
Description
The OAM manager received the message that the status of BFD for LSP changed.
Parameters
Parameter Name
Parameter Meaning
State
indicates the status of BFD for LSP.
Session
indicates the BFD session.
Possible Causes
The message that the status of BFD for LSP changed was received.
Procedure
----End
37.24 IFNET/4/NOTIFY_BFD_FAIL
Message
IFNET/4/NOTIFY_BFD_FAIL:Failed to notify Application module of the BFD state change
event. (Application=[STRING])
Description
Failed to notify the application module of the event that the BFD status changed.
Parameters
Parameter Name
Parameter Meaning
Application
indicates the name of the application module.
Possible Causes
Failed to notify the application module of the event that the BFD status changed.
Issue 07 (2014-07-30)

237

Log Reference
37 IFNET
Procedure
----End
37.25 IFNET/4/NTF_ACOAM_STATE_FAIL
Message
IFNET/4/NTF_ACOAM_STATE_FAIL:Failed to notify Application module of the AC OAM
state change event. (Application=[STRING])
Description
Failed to notify the application module of the event that AC OAM status changed.
Parameters
Parameter Name
Parameter Meaning
Application
indicates the application module name.
Possible Causes
Failed to notify the application module of the event that AC OAM status changed.
Procedure
----End
37.26 IFNET/6/NTF_STATE_CHANGE
Message
IFNET/6/NTF_STATE_CHANGE:The OAM Manager interface fault notify state change.
Description
The status change was notified after the OAM manager became faulty.
Issue 07 (2014-07-30)

238

Log Reference
37 IFNET
Parameters
Parameter Name
Parameter Meaning
InterfaceName
State
indicates the status.
Possible Causes
After the oam notify command was run, the OAM manager received the message that APP status
changed.
Procedure
----End
37.27 IFNET/4/OUT_OF_MEMORY
Message
IFNET/4/OUT_OF_MEMORY:Insufficient memory.
Description
Memory is insufficient.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Memory is insufficient.
Procedure
----End
37.28 IFNET/6/PW_STATE_CHANGE
Issue 07 (2014-07-30)

239

Log Reference
37 IFNET
Message
IFNET/6/PW_STATE_CHANGE:The OAM Manager received the BFD for PW state changed
message. (State=[STRING], Session=[ULONG])
Description
The OAM manager received the message that the status of BFD for PW changed.
Parameters
Parameter Name
Parameter Meaning
State
indicates the status.
Session
indicates the index of a BFD session.
Possible Causes
The message that the status of BFD for PW changed was received.
Procedure
----End
37.29 IFNET/6/REPEAT_NOTIFY
Message
IFNET/6/REPEAT_NOTIFY:The Application module repeatedly notified the fault.
Description
The application module repeatedly reported the fault.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
State
indicates the status of the link layer protocol.
Possible Causes
The application module repeatedly reported the fault.
Issue 07 (2014-07-30)

240

Log Reference
37 IFNET
Procedure
----End
Issue 07 (2014-07-30)

241

Log Reference
38 IGMP
38
IGMP
About This Chapter

38.1 IGMP/6/GLB_ENTRY
38.2 IGMP/6/GLB_LIMIT
38.3 IGMP/6/IF_ENTRY
38.4 IGMP/6/IF_LIMIT
38.5 IGMP/6/INST_ENTRY
38.6 IGMP/6/INST_LIMIT
38.7 IGMP/4/INT_INV
38.8 IGMP/4/REG_ACL_F
38.9 IGMP/4/SET_IGMP_GLBPLC_FAIL
38.10 IGMP/6/VER1_RECV_INV
Issue 07 (2014-07-30)

242

Log Reference
38 IGMP
38.1 IGMP/6/GLB_ENTRY
Message
IGMP/6/GLB_ENTRY:In VPN instance \"[vpn-instance-name]\", IGMP discarded the received
report ([source-address], [group-address]) because the number of IGMP group memberships in
all VPN instances reached the limit. The current statistical number of IGMP group memberships
is [statistical-number]. (FlCode=[STRING][ULONG])
Description
The received IGMP Report message was discarded because the number of IGMP entries in all
instances reached the limit.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name] Indicates the name of a VPN instance.

[source-address]
Indicates the source address.
[group-address]
Indicates the group address.
[statistical-number]
Indicates the upper limit of the number of IGMP entries.
FlCode
Indicates the name of the source code file and the line number of this
log message.
Possible Causes
In the case that IGMP limit for all instances was set, when the total number of IGMP entries in
all instances reached the limit, the received IGMP Report message was discarded.
Procedure
----End
38.2 IGMP/6/GLB_LIMIT
Message
IGMP/6/GLB_LIMIT:In all VPN instances, the number of existed IGMP group memberships
exceeded the limit. (FlCode=[STRING][ULONG])
Issue 07 (2014-07-30)

243

Log Reference
38 IGMP
Description
The total number of IGMP entries in all current instances exceeded the configured limit.
Parameters
FlCode
Indicates the name of the source code file and the line number of this log
message.
Possible Causes
In the case that all instances were configured with the IGMP limit, this log message was
generated when the total number of IGMP entries in all instances exceeded the limit.
Procedure
----End
38.3 IGMP/6/IF_ENTRY
Message
IGMP/6/IF_ENTRY:In VPN instance \"[vpn-instance-name]\", IGMP discarded the received
report ([source-address], [group-address]) because the number of IGMP group memberships
reached the limit on the interface [interface-name]. The current statistical number of IGMP group
memberships is [statistical-number]. (FlCode=[STRING][ULONG])
Description
The IGMP Report message received from the interface was discarded because the number of
IGMP entries on the interface reached the upper limit.
Parameters
Parameter Name
Parameter Meaning

[source-address]
[group-address]
[interface-name]
Issue 07 (2014-07-30)

244

Log Reference
38 IGMP
Parameter Name
Parameter Meaning
FlCode
log message.
Possible Causes
In the case that the current interface was configured with the IGMP limit, when the number of
IGMP entries on the interface reached the limit, the received IGMP Report message was
discarded.
Procedure
----End
38.4 IGMP/6/IF_LIMIT
Message
IGMP/6/IF_LIMIT:In VPN instance \"[vpn-instance-name]\", the number of existed IGMP
group memberships exceeded the limit on this interface. (FlCode=[STRING][ULONG])
Description
The number of IGMP entries on the current interface exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
In the case that the current interface was configured with the IGMP limit, the number of IGMP
entries on the interface exceeded the limit.
Procedure
----End
Issue 07 (2014-07-30)

245

Log Reference
38 IGMP
38.5 IGMP/6/INST_ENTRY
Message
IGMP/6/INST_ENTRY:In VPN instance \"[vpn-instance-name]\", IGMP discarded the
received report ([source-address], [group-address]) because the number of IGMP group
memberships in this VPN instance reached the limit. The current statistical number of IGMP
group memberships is [statistical-number]. (FlCode=[STRING][ULONG])
Description
The received IGMP Report message was discarded because the number of IGMP entries in the
instance reached the upper limit.
Parameters
Parameter Name
Parameter Meaning

[source-address]
[group-address]
FlCode
log message.
Possible Causes
In the case that the current instance was configured with the IGMP limit, when the number of
IGMP entries in the instance reached the limit, the received IGMP Report message was
discarded.
Procedure
----End
38.6 IGMP/6/INST_LIMIT
Message
IGMP/6/INST_LIMIT:In VPN instance \"[vpn-instance-name]\", the number of existed IGMP
group memberships exceeded the limit. (FlCode=[STRING][ULONG])
Issue 07 (2014-07-30)

246

Log Reference
38 IGMP
Description
The number of IGMP entries in the current instance exceeded the configured limit.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
In the case that the current instance was configured with the IGMP limit, the number of IGMP
entries in the current instance exceeded the limit.
Procedure
----End
38.7 IGMP/4/INT_INV
Message
IGMP/4/INT_INV:In VPN instance \"[vpn-instance-name]\", a Mtrace packet received on an
unknown interface was discarded. (FlCode=[STRING][ULONG])
Description
A Mtrace packet was received on an unknown interface.
Parameters
Parameter Name
Parameter Meaning

FlCode
Indicates information about an output log. The information contains the

document ID and row number.
Possible Causes
The interface was not configured with the IP address.
Issue 07 (2014-07-30)

247

Log Reference
38 IGMP
Procedure
Step 1 Run the display this command in the interface view to check whether the IP address is
configured.
Step 2 Run the ip address ip-address { mask | mask-length } command to assign an IP address for the
interface.
Step 3 End.
----End
38.8 IGMP/4/REG_ACL_F
Message
IGMP/4/REG_ACL_F:In VPN instance \"[vpn-instance-name]\", registering ACL update
callback functions failed. (FlCode=[STRING][ULONG])
Description
IGMP failed to register the ACL update callback function with the MRM.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name] Indicates the name of the VPN instance.

FlCode
indicates the name of the source code file and the line number of this
log message.
Possible Causes
Failed to call the MRM interface to add the ACL name to the MRM.
Procedure
Step 1 Reconfigure the commands for Named ACLs.
----End
38.9 IGMP/4/SET_IGMP_GLBPLC_FAIL
Message
IGMP/4/SET_IGMP_GLBPLC_FAIL:In VPN instance \"[vpn-instance-name]\", failed to set
the IGMP global application policy. (FlCode=[STRING][ULONG])
Issue 07 (2014-07-30)

248

Log Reference
38 IGMP
Description
Failed to set the IGMP application policy on the interface.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
Failed to deliver the interface application policy when IGMP was configured on the interface.
Procedure
Step 1 Run the undo igmp enable command and reconfigure IGMP on the interface.
Step 2 If this log message is generated after each reconfiguration, contact Huawei technical support
personnel.
----End
Message
IGMP/6/VER1_RECV_INV:In VPN instance \"[vpn-instance-name]\", ignored the received
IGMP query of version [version] on IGMPv1 interface [interface-name] ([ip-address]).
(FlCode=[STRING][ULONG])
Description
The received IGMP Query message of higher version was ignored by the IGMPv1 interface.
Parameters
Parameter Name
Parameter Meaning

[version]
Indicates the version number.
[interface-name]
[ip-address]
Indicates the IP address of an interface.
FlCode
log message.
Issue 07 (2014-07-30)

249

Log Reference
38 IGMP
Possible Causes
1. The IGMPv1 interface received the IGMP Query message of other versions.
2. The IGMPv1 interface received the IGMP Query message of higher version 60 seconds later
again.
Procedure
----End
Message
Description
The received IGMP Query message of higher version or invalid IGMP Query message was
ignored by the IGMPv2 interface.
Parameters
Parameter Name
Parameter Meaning

[version]
[interface-name]
[ip-address]
FlCode
log message.
Possible Causes
again.
Procedure
----End
Issue 07 (2014-07-30)

250

Log Reference
38 IGMP
Message
Description
The received IGMP Query message of other versions was ignored by the IGMPv3 interface.
Parameters
Parameter Name
Parameter Meaning

[version]
[interface-name]
[ip-address]
FlCode
log message.
Possible Causes
again.
Procedure
----End
Issue 07 (2014-07-30)

251

Log Reference
39 INFO
39
INFO
About This Chapter

39.1 INFO/4/DBG_ALL
39.2 INFO/6/LOGFILE_DELETED
39.3 INFO/4/RST_LOGB
39.4 INFO/4/SUPPRESS_LOG
Issue 07 (2014-07-30)

252

Log Reference
39 INFO
39.1 INFO/4/DBG_ALL
Message
INFO/4/DBG_ALL:When deciding whether to turning on all the debugging switches, the user
chose [Y/N].
Description
The user confirmed whether to enable all debugging functions by selecting "Y" or "N".
Parameters
[Y/N]
prompts the user to confirm the action. If "Y" is selected, the action will
be performed; if "N" is selected, the action will not be performed.
Possible Causes
The debugging all command was run.
Procedure
----End
39.2 INFO/6/LOGFILE_DELETED
Message
INFO/6/LOGFILE_DELETED:The log file [STRING] is deleted successfully.
Description
The log file is deleted successfully.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the name of the deleted log file.
Possible Causes
The number of log files exceeds the threshold or the available disk space is smaller than 30 M.
Issue 07 (2014-07-30)

253

Log Reference
39 INFO
Procedure
Step 1 Check whether the old log files to be automatically deleted from the device need be saved.
----End
39.3 INFO/4/RST_LOGB
Message
INFO/4/RST_LOGB:When deciding whether to reset the logbuffer, the user chose [Y/N].
Description
The user confirmed whether to reset the log buffer by selecting "Y" or "N".
Parameters
[Y/N]
prompts the user to confirm the action. If "Y" is selected, the action will
be performed; if "N" is selected, the action will not be performed.
Possible Causes
The reset logbuffer command was run.
Procedure
----End
39.4 INFO/4/SUPPRESS_LOG
Message
INFO/4/SUPPRESS_LOG:Last message repeated [number] times.([STRING])
Description
The same log has been generated number times before this log.
Parameters
Parameter Name
Parameter Meaning
[number]
The count of repeat times.
Issue 07 (2014-07-30)

254

Log Reference
39 INFO
Parameter Name
Parameter Meaning
[STRING]
Basic information about the repeated logs.
Possible Causes
If the information center processes the same logs, only the first log is recorded and the following
logs are recorded duplicated times. When different logs processed or suppress timeout, the
SUPPRESS_LOG is processed.
Procedure
----End
Issue 07 (2014-07-30)

255

Log Reference
40 IPV4-IPV6
40
IPV4-IPV6
About This Chapter

40.1 IPV4-IPV6/4/MAXNUM_UNCAMP
40.2 IPV4-IPV6/3/MTU_MIN
40.3 IPV4-IPV6/4/UNIDE_SPEC_T
Issue 07 (2014-07-30)

256

Log Reference
40 IPV4-IPV6
40.1 IPV4-IPV6/4/MAXNUM_UNCAMP
Message
IPV4-IPV6/4/MAXNUM_UNCAMP:The number of tunnels [tunnel-number1] configured on
the old main control board is greater than the maximum number of tunnels [tunnel-number2]
that can be configured on the new main control board.
Description
The number of tunnels configured on the old main control board was greater than the allowable
maximum number of tunnels configured on the new main control board.
Parameters
[tunnel-number1]
Indicates the number of tunnels configured on the old main control board.
[tunnel-number2]
Indicates the allowable maximum number of tunnels configured on the

new main control board.
Possible Causes
The specifications of the new version were smaller. As a result, the number of tunnels configured
on the old main control board was greater than the allowable maximum number of tunnels
Procedure
Step 1 Check specifications and configurations to make sure that the specifications of the new main
control board are larger than the configurations of the old main control board. If specifications
do not meet requirements, you can repurchase the paf license of Huawei; otherwise, some
----End
40.2 IPV4-IPV6/3/MTU_MIN
Message
IPV4-IPV6/3/MTU_MIN:The path MTU or IPv6 MTU of the outgoing interface on [interfacename] is less than the lower threshold 1280 bytes.
Description
The path MTU or IPv6 MTU of the outgoing interface was less than 1280 bytes.
Issue 07 (2014-07-30)

257

Log Reference
40 IPV4-IPV6
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Indicates the name of a tunnel interface.
Possible Causes
The path MTU or IPv6 MTU of the outgoing interface was less than 1280 bytes.
Procedure
Step 1 Check related information on the IPv6 MTU or path MTU in the log.
Step 2 Run the display ipv6 interface command to view the IPv6 MTUs of the interfaces on the link,
find the interface whose IPv6 MTU is less than 1280 bytes, and modify the IPv6 MTU on this
interface.
----End
40.3 IPV4-IPV6/4/UNIDE_SPEC_T
Message
IPV4-IPV6/4/UNIDE_SPEC_T:Obtain an unknown object type when parsing the tunnel
specification. (Type=[ULONG])
Description
An unknown object type was obtained in the process of parsing tunnel specifications.
Parameters
Parameter Name
Parameter Meaning
Type
Indicates the object type.
Possible Causes
An unknown object type was obtained.
Procedure
Step 1 Contact the Huawei technical support personnel.
----End
Issue 07 (2014-07-30)

258

Log Reference
41 IPV6FIBAGENT
41
IPV6FIBAGENT
About This Chapter

41.1 IPV6FIBAGENT/3/MEMCHECK
41.2 IPV6FIBAGENT/4/PLYDELE6
41.3 IPV6FIBAGENT/4/SENDPLYSLOT6
41.4 IPV6FIBAGENT/4/SENDQUESLOTFAIL6
41.5 IPV6FIBAGENT/6/TRIGDELEROUT6
Issue 07 (2014-07-30)

259

Log Reference
41 IPV6FIBAGENT
41.1 IPV6FIBAGENT/3/MEMCHECK
Message
IPV6FIBAGENT/3/MEMCHECK:Memory was checked after the routes were deleted due to
policy change, and the return value was [return-value].
Description
Memory checking was performed after route deletion.
Parameters
Parameter Name
Parameter Meaning
[return-value]
indicates types of returned values, including

1: indicates that memory is insufficient.
2: indicates that memory is seriously insufficient.
Possible Causes
Memory checking was performed after route deletion.
Procedure
Step 1 Run the display diagnostic-information command and save the output of this command and
then contact the Huawei technical personnel.
----End
41.2 IPV6FIBAGENT/4/PLYDELE6
Message
IPV6FIBAGENT/4/PLYDELE6:The routes were deleted due to FIB6 policy change.
(QueueLength=[ULONG], MaxLength=[ULONG], UnreadNumber=[ULONG])
Description
FIB6 entries were being deleted according to the changes of FIB6 policies.
Issue 07 (2014-07-30)

260

Log Reference
41 IPV6FIBAGENT
Parameters
Parameter Name
Parameter Meaning
QueueLength
indicates the length of a queue.
MaxLength
indicates the maximum length of a queue.
UnreadNumber
indicates the number of unread messages in the IPC queue.
Possible Causes
When the FIB6 module on the interface board read the IPC message queue, the queue length
was longer than the specified value and the length of the queue containing unread messages was
also longer than the set value.
Procedure
----End
41.3 IPV6FIBAGENT/4/SENDPLYSLOT6
Message
IPV6FIBAGENT/4/SENDPLYSLOT6:FIB6 failed to send a policy to slot [slot-number].
Description
FIB6 failed to send a policy-change message to the interface board.
Parameters
Parameter Name
Parameter Meaning
[slot-number]
Possible Causes
The main control board failed to send a policy-change message to the interface board during hot
plugging.
Procedure
Step 1 Run the display fib-policy slot [ slot-number ] command to view of FIB policies on the interface
board and save the output of this command.
----End
Issue 07 (2014-07-30)

261

Log Reference
41 IPV6FIBAGENT
41.4 IPV6FIBAGENT/4/SENDQUESLOTFAIL6
Message
IPV6FIBAGENT/4/SENDQUESLOTFAIL6:FIB6 failed to send a query to slot [slot-number].
Description
The FIB6 module failed to send a query to the interface board.
Parameters
Parameter Name
Parameter Meaning
[slot-number]
Possible Causes
After active/standby switchover, the main control board must query the status of the interface
board.
Procedure
Step 1 Run the display fib overload state slot [ slot-number ] command to view overload status of the
interface board and save the output of this command.
----End
41.5 IPV6FIBAGENT/6/TRIGDELEROUT6
Message
IPV6FIBAGENT/6/TRIGDELEROUT6:The routes were deleted due to FIB6 policy change.
The type of deletion was [process-type].
Description
Deleting FIB6 entries according to the changes of FIB policies was triggered.
Issue 07 (2014-07-30)

262

Log Reference
41 IPV6FIBAGENT
Parameters
[process-type]
indicates types of operations, including

1: indicates that the FIB6 entries must be deleted if overload suspension
happens.
2: indicates that FIB6 entries must be deleted if overload suspension
happens.
Possible Causes
Deleting FIB6 entries according to the changes of FIB policies was triggered.
Procedure
----End
Issue 07 (2014-07-30)

263

Log Reference
42 IPV6PP
42
IPV6PP
About This Chapter

42.1 IPV6PP/3/REACHMAX
42.2 IPV6PP/3/REASSERROR
Issue 07 (2014-07-30)

264

Log Reference
42 IPV6PP
42.1 IPV6PP/3/REACHMAX
Message
IPV6PP/3/REACHMAX:The number of the IPv6 fragments reached the upper limit!
Description
The number of fragments reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The number of fragments reached the upper limit.
Procedure
Step 1 View related logs.
Step 2 Run the debugging ipv6 packet command to enable IPv6 packet debugging, view fragment
information, and perform adjustment to reduce fragments.
----End
42.2 IPV6PP/3/REASSERROR
Message
IPV6PP/3/REASSERROR:The number of the reassembly IPv6 queues reached the upper limit!
Description
The number of IPv6 reassembly queues reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

265

Log Reference
42 IPV6PP
Possible Causes
The number of IPv6 reassembly queues reached the upper limit.
Procedure
Step 1 View related logs.
Step 2 Run the debugging ipv6 packet command to enable IPv6 packet debugging, view fragment
information, and perform adjustment to reduce fragments.
----End
Issue 07 (2014-07-30)

266

Log Reference
43 IPV6TCP
43
IPV6TCP
About This Chapter

43.1 TCP6/3/TCP6_NOACTV_RECVKEY
43.2 TCP6/3/TCP6_NOACTV_SENDKEY
Issue 07 (2014-07-30)

267

Log Reference
43 IPV6TCP
43.1 TCP6/3/TCP6_NOACTV_RECVKEY
Message
TCP6/3/TCP6_NOACTV_RECVKEY:TCP segment from source [source-address] to
destination [destination-address] dropped due to the absence of Active Receive Key.
Description
TCP segment from source address to destination address dropped due to the absence of Active
Receive Key.
Parameters
Parameter Name
Parameter Meaning
[source-address]
Indicates the source IP address.
[destination-address]
Indicates the destination IP address.
Possible Causes
No Active Receive Key present in the Keychain.
Procedure
Step 1 Configure the appropriate Keychain.
----End
43.2 TCP6/3/TCP6_NOACTV_SENDKEY
Message
TCP6/3/TCP6_NOACTV_SENDKEY:Transmission of TCP segment from source [sourceaddress] to destination [destination-address] failed due to the absence of Active Send Key.
Description
Transmission of TCP segment from source address to destination address failed due to the
absence of Active Send Key.
Parameters
Parameter Name
Parameter Meaning
[source-address]
Issue 07 (2014-07-30)

268

Log Reference
43 IPV6TCP
Parameter Name
Parameter Meaning
[destination-address]
Possible Causes
No Active Send Key present in the Keychain.
Procedure
Step 1 Configure the appropriate Keychain.
----End
Issue 07 (2014-07-30)

269

Log Reference
44 ISIS
44
ISIS
About This Chapter

44.1 ISIS/6/AC_RT_SEL_FAIL
44.2 ISIS/6/AC_RT_V6_SEL_FAIL
44.3 ISIS/6/ADD_L1_SUMRT_FAIL
44.5 ISIS/6/ADD_LKINFO_CSPF_FAIL
44.6 ISIS/6/ADD_MDF_LK_CSPF_FAIL
44.7 ISIS/6/ADD_NTWK_MPLS_FAIL
44.8 ISIS/6/ADD_P2P_ADJ_ERR
44.9 ISIS/6/ADD_REDSTRBT_RT_FAIL
44.10 ISIS/6/ADD_RTTO_LSP_FAIL
44.11 ISIS/4/ADD_SRLGTOLINK_FAIL
44.12 ISIS/6/ADD_SUMMRT_URT_FAIL
44.13 ISIS/6/ADD_SUMRT_FAIL
44.14 ISIS/6/ADD_TE_TLV_FAIL
44.15 ISIS/4/ADJ_CHANGE_LEVEL
44.16 ISIS/6/ALIID_TLV_LEN_SHORT
44.17 ISIS/6/AREA_ADDR_INVALID
44.18 ISIS/6/AUTH_TLV_OVER_ONECE
44.19 ISIS/6/BAD_TLV_LEN
44.20 ISIS/6/BIND_SOKT_FAIL
Issue 07 (2014-07-30)

270

Log Reference
44 ISIS
44.21 ISIS/5/CIRC_STATE_SET
44.22 ISIS/6/CONFLICT_SYSTEM_ID
44.23 ISIS/6/CREA_AREA_TLV_FAIL
44.24 ISIS/6/CREATE_CIRCUIT_FAIL
44.25 ISIS/6/CRT_BFD_SESION_FAIL
44.26 ISIS/6/CRT_P2P_ADJ_FAIL
44.27 ISIS/6/DEL_ATTSY_FAIL
44.28 ISIS/6/DEL_BFD_SESSION_FAIL
44.29 ISIS/6/DEL_LKINFO_CSPF_FAIL
44.30 ISIS/6/DEL_NTWK_MPLS_FAIL
44.31 ISIS/6/DEL_SUMMRT_URT_FAIL
44.32 ISIS/6/DISABL_RT_FAIL
44.33 ISIS/6/DISABLE_ROUTELEAK_V6
44.34 ISIS/6/DYNC_NAME_FAIL
44.35 ISIS/6/EN_TE_FAIL_NO_RTID
44.36 ISIS/6/ENABLE_TE_LV1_FAIL
44.38 ISIS/6/FAIL_CMD_IN_AMB
44.39 ISIS/6/FAIL_CMD_IN_SMB
44.40 ISIS/6/FAIL_CRT_OPT_DYN_NM
44.41 ISIS/6/FAIL_SEND_DICT
44.42 ISIS/6/FAIL_TRANS_P2P_CSNP
44.43 ISIS/6/FD_CUR_IFINDEX_FAIL
44.44 ISIS/6/FD_SBNTADDR_BDC_FAIL
44.45 ISIS/6/FIND_CIRCUIT_FAIL
44.46 ISIS/6/FIND_SYSID_FAIL
44.47 ISIS/6/FLO_LSP_OLO_FAIL
44.48 ISIS/6/FT_GT_RT_URM_FAIL
44.49 ISIS/6/GEN_ATT_LSP_FAIL
44.50 ISIS/4/GENLSPDESC_FAILSMB
44.51 ISIS/6/GET_IF_FAILSMB
44.52 ISIS/6/GET_IFINSTN_ID_FAIL
Issue 07 (2014-07-30)

271

Log Reference
44 ISIS
44.53 ISIS/6/GET_IFNET_BY_ALIAS
44.54 ISIS/6/GET_LINKINFO_FAIL
44.55 ISIS/6/GT_ACTVE_RT_RM_FAIL
44.56 ISIS/6/GT_CIRC_IFINDX_FAIL
44.57 ISIS/6/GT_CIRCINDEX_FAIL
44.58 ISIS/6/GT_INFO_RDM_FAIL
44.59 ISIS/6/GT_ININDEX_FAIL
44.60 ISIS/6/GT_LGC_PHY_FAIL
44.61 ISIS/6/GT_LGCIF_V6ADDR_FAIL
44.62 ISIS/6/GT_LGCL_SUBNET_FAIL
44.63 ISIS/6/GT_LV_RT_URM_FAIL
44.64 ISIS/6/GT_LV_RT_V6_URM_FAIL
44.65 ISIS/6/GT_MPLSTE_RM_FAIL
44.66 ISIS/6/GT_PHYIF_IFNET_FAIL
44.67 ISIS/6/GT_RTENTRY_URM_FAIL
44.68 ISIS/6/GT_RTID_RM_FAIL
44.69 ISIS/6/GT_TELK_INFO_FAIL
44.70 ISIS/6/GT_V6_PHYIF_FAIL
44.71 ISIS/6/GT_V6ADDR_PHYIF_FAIL
44.72 ISIS/6/IF_TEMP
44.73 ISIS/4/IMPORT_LIMIT_EXCEED
44.74 ISIS/4/IMPORT_LIMIT_RESTORE
44.75 ISIS/6/INIT_DEC_FAIL
44.76 ISIS/4/INT_BUILDRUN_FAIL
44.77 ISIS/6/INTI_ISIS_FAIL
44.78 ISIS/3/INVALID_DSTEMOD
44.79 ISIS/6/INVID_DR_CHANGE
44.80 ISIS/6/INVID_TLV_TYPE_REP
44.81 ISIS/6/JN_MTCAST_ADDR_FAIL
44.82 ISIS/6/JOIN_L1_ADDR_FAIL
44.84 ISIS/6/JOIN_ALLIS_ADDR_FAIL
Issue 07 (2014-07-30)

272

Log Reference
44 ISIS
44.85 ISIS/6/L3VPN_FRR_CHANGE
44.86 ISIS/6/LDP_INFORM_RM_ENAB
44.87 ISIS/6/LEAVE_L1_ADDR_FAIL
44.89 ISIS/6/LEAVE_ALLIS_ADDR_FAIL
44.90 ISIS/5/LOCALSYS_DIS_REST_RT
44.91 ISIS/6/LV_MTCAST
44.92 ISIS/6/LV_MTCAST_ADDR_FAIL
44.93 ISIS/6/MATCH_CIRC_FAIL
44.94 ISIS/6/MD_LV_RT_FAIL
44.95 ISIS/6/MD_LV_RT_V6_FAIL
44.96 ISIS/6/MDF_LKINFO_CSPF_FAIL
44.97 ISIS/6/MDF_NTWK_MPLS_FAIL
44.98 ISIS/6/MTU_EXCEED_MAXPDU
44.99 ISIS/6/NSR_MSG_PROC
44.100 ISIS/6/NSR_STATE_CHANGE
44.101 ISIS/6/P2P_CIRC_TX_LSP_FAIL
44.102 ISIS/4/PEER_DOWN_BFDDOWN
44.103 ISIS/4/PEER_DOWN_CIRC_DOWN
44.104 ISIS/4/PEER_DOWN_DIS_CHANGE
44.105 ISIS/4/PEER_DOWN_LOW_MEMORY
44.106 ISIS/4/PEER_DOWN_NO_MEMORY
44.107 ISIS/4/PEER_DOWN_REPTADJ
44.108 ISIS/4/PEER_DOWN_REPTP2PADJ
44.109 ISIS/4/PEER_DOWN_RPRDOWN
44.110 ISIS/4/PEER_DWN_ADJ_STATDWN
44.111 ISIS/4/PEER_DWN_AREAMISMACH
44.112 ISIS/4/PEER_DWN_CIRC_SILENT
44.113 ISIS/4/PEER_DWN_HLDTMR_EXPR
44.114 ISIS/4/PEER_DWN_ID_CONFLICT
44.115 ISIS/4/PEER_DWN_LEVEL_CHANG
44.116 ISIS/4/PEER_DWN_PDUMISMATCH
Issue 07 (2014-07-30)

273

Log Reference
44 ISIS
44.117 ISIS/4/PEER_DWN_SYS_DISABLE
44.118 ISIS/4/PEER_DWN_SYSTYP_UNKN
44.119 ISIS/5/PEER_UP_ADJ_CREATE
44.120 ISIS/6/PROCESS_TMR_EVENT
44.121 ISIS/6/RCV_BFD_DET_EVENT
44.122 ISIS/4/RCV_ERRSELFLSP_SMB
44.123 ISIS/6/RCV_NODE_DOWN_EVENT
44.124 ISIS/6/RCV_RPR_EVENT
44.125 ISIS/6/RCV_RPRMSG
44.126 ISIS/6/REA_MAX_SEQ_NUM
44.127 ISIS/6/REC_RM_MEM_RESTORE
44.128 ISIS/4/REC_RM_MEM_SHORT
44.129 ISIS/4/REDIST_THRESHOLD_REACH
44.130 ISIS/4/REDIST_THRESHOLD_REACH_CLEAR
44.131 ISIS/6/RM_CIRC_CHANGE
44.132 ISIS/6/RM_CIRC_CHANGE_V6
44.133 ISIS/6/RM_LOGICRC_CHGE
44.134 ISIS/6/RM_LOGICRC_CHGE_V6
44.135 ISIS/6/SB_CIR_NOT_ENABLE
44.136 ISIS/6/SELF_LSP_EXPIRED
44.137 ISIS/6/ST_LK_CNTRL_FAIL
44.138 ISIS/4/START_DISABLE_ISIS
44.139 ISIS/4/START_ENABLE_ISIS
44.140 ISIS/6/T1TMR_EXPIR_GR_CMD
44.141 ISIS/6/T1TMR_LV1_CACEL_GR
44.142 ISIS/6/T1TMR_LV1_EXPIR_GR
44.143 ISIS/6/T1TMR_LV1_EXPIR_GR_C
44.144 ISIS/5/T1TMR_LV1_STOP_CMD
Issue 07 (2014-07-30)

274

Log Reference
44 ISIS
44.149 ISIS/6/T2TMR_LV1_CANCL_GR
44.155 ISIS/6/T2TMR_STAR_L1_GR
44.157 ISIS/6/T3TMR_CANCL_GR
44.158 ISIS/6/T3TMR_EXPIR_GR
44.159 ISIS/6/T3TMR_REINT_GR
44.160 ISIS/6/T3TMR_STAR_GR
44.161 ISIS/5/T3TMR_STOP_CMD
44.162 ISIS/6/TMER_STIL_USED
44.163 ISIS/6/TORM_LEV_GR_DESTR
44.164 ISIS/6/TORM_LEV_RESTA_SMOH
44.165 ISIS/5/TORM_LEV_RESTAR_CMD
44.166 ISIS/5/TORM_LEV_RESTAR_SPF
44.167 ISIS/5/TORM_RNTR_RESTAR_CMD
44.168 ISIS/6/UNBIND_SOKT_FAIL
44.169 ISIS/6/WRONG_VERSION
Issue 07 (2014-07-30)

275

Log Reference
44 ISIS
44.1 ISIS/6/AC_RT_SEL_FAIL
Message
ISIS/6/AC_RT_SEL_FAIL:ISIS [process-id] failed to invoke the active route [route] selection.
(RouteEntryTable=[ULONG], EntryId=[ULONG], MTID=[USHORT], ReturnValue=
[STRING])
Description
IS-IS failed to select AN active route.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the ID of an IS-IS process.
[route]
Indicates a route.
RouteEntryTable
Indicates a routing table.
EntryId
Indicates a routing entry.
MTID
Indicates the ID of a topology.
ReturnValue
Indicates a returned value.
Possible Causes
Failed to select an active route.
Procedure
Step 1 Check the current routing information.
----End
44.2 ISIS/6/AC_RT_V6_SEL_FAIL
Message
ISIS/6/AC_RT_V6_SEL_FAIL:ISIS [process-id] failed to invoke the IPv6 active route [route]
selection. (RouteEntryTable=[ULONG], EntryId=[ULONG], MTID=[USHORT],
ReturnValue=[STRING])
Issue 07 (2014-07-30)

276

Log Reference
44 ISIS
Description
IS-IS failed to select an IPv6 active route.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[route]
Indicates a route.
RouteEntryTable
EntryId
MTID
ReturnValue
Possible Causes
Failed to select an IPv6 active route.
Procedure
----End
Message
ISIS/6/ADD_L1_SUMRT_FAIL:ISIS [process-id] failed to add the Level-1 summary route.
(MTID=[USHORT])
Description
IS-IS failed to add a summarized Level-1 route.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

277

Log Reference
44 ISIS
Parameter Name
Parameter Meaning
MTID
Possible Causes
Failed to add a summarized Level-1 route.
Procedure
----End
Message
ISIS/6/ADD_L2_SUMRT_FAIL:ISIS [process-id] failed to add the Level-2 summary route.
(MTID=[USHORT])
Description
IS-IS failed to add a summarized Level-2 route.
Parameters
Parameter Name
Parameter Meaning
[process-id]
MTID
Possible Causes
Failed to add a summarized Level-2 route.
Procedure
----End
44.5 ISIS/6/ADD_LKINFO_CSPF_FAIL
Issue 07 (2014-07-30)

278

Log Reference
44 ISIS
Message
ISIS/6/ADD_LKINFO_CSPF_FAIL:ISIS [process-id] failed to add TE link information to
CSPF. (ReturnValue=[ULONG], NeighborSystemId=[STRING], NeighborPseudoNodeId=
[USHORT], NodeStatus=[USHORT], FragmentNumber=[USHORT])
Description
IS-IS failed to add TE link information to CSPF.
Parameters
Parameter Name
Parameter Meaning
[process-id]
ReturnValue
specifies a returned value.
NeighborSystemId
Indicates the system ID of a neighbor.
NeighborPseudoNodeId
Indicates the pseudo node ID of a neighbor.
NodeStatus
Indicates the status of a node.
FragmentNumber
Indicates the fragment number.
Possible Causes
1. CSPF was not enabled.
2. The message queue of CSPF was full.
Procedure
----End
44.6 ISIS/6/ADD_MDF_LK_CSPF_FAIL
Message
ISIS/6/ADD_MDF_LK_CSPF_FAIL:ISIS [process-id] failed to modify TE link information in
Issue 07 (2014-07-30)

279

Log Reference
44 ISIS
Description
IS-IS failed to modify the TE link information in the CSPF.
Parameters
Parameter Name
Parameter Meaning
[process-id]
ReturnValue
NeighborSystemId
NodeStatus
FragmentNumber
Possible Causes
2. The message queue of CSPF was full.
Procedure
Step 1 Check whether CSPF is enabled.
l If so, go to Step 3.
l If not, go to Step 2.
Step 2 Enable CSPF, and check whether the log message is displayed again.
Step 4 End.
----End
44.7 ISIS/6/ADD_NTWK_MPLS_FAIL
Message
ISIS/6/ADD_NTWK_MPLS_FAIL:ISIS [process-id] failed to add network information to
MPLS TE. (ReturnValue=[ULONG])
Issue 07 (2014-07-30)

280

Log Reference
44 ISIS
Description
IS-IS failed to add network information to MPLS TE.
Parameters
Parameter Name
Parameter Meaning
[process-id]
ReturnValue
Possible Causes
1. The message queue of the CSPF module was full.
2. An internal error occurred.
Procedure
----End
44.8 ISIS/6/ADD_P2P_ADJ_ERR
Message
ISIS/6/ADD_P2P_ADJ_ERR:Advertising P2P adjacency failed. (InterfaceName=[STRING],
MTID=[USHORT])
Description
Failed to add a P2P neighbor.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
MTID
Possible Causes
Internal processing.
Issue 07 (2014-07-30)

281

Log Reference
44 ISIS
Procedure
----End
44.9 ISIS/6/ADD_REDSTRBT_RT_FAIL
Message
ISIS/6/ADD_REDSTRBT_RT_FAIL:ISIS [process-id] failed to add the Level-[level]
redistributed route [route] into the forwarding table. (MTID=[USHORT])
Description
IS-IS failed to add an imported route.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[level]
Indicates the IS-IS level.
[route]
Indicates a route.
MTID
Indicates the ID of topology.
Possible Causes
Failed to add an imported route.
Procedure
Step 1 Check information about the route.
----End
44.10 ISIS/6/ADD_RTTO_LSP_FAIL
Message
ISIS/6/ADD_RTTO_LSP_FAIL:ISIS [process-id] failed to add the route to the LSP. (MTID=
[USHORT])
Description
IS-IS failed to add a route to an LSP.
Issue 07 (2014-07-30)

282

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
MTID
Possible Causes
Failed to add a route to an LSP.
Procedure
----End
44.11 ISIS/4/ADD_SRLGTOLINK_FAIL
Message
ISIS/4/ADD_SRLGTOLINK_FAIL:ISIS [process-id] failed to add SRLG information to TE
link. (NewSrlgNum=[USHORT], CurrentSrlgNum=[USHORT], NeighborSystemId=
[STRING], NeighborPseudoNodeId=[USHORT], FragmentNumber=[USHORT])
Description
IS-IS failed to add the SRLG information to a TE link.
Parameters
Parameter Name
Parameter Meaning
[process-id]
NewSrlgNum
Indicates the number of new SRLGs.
CurrentSrlgNum
Indicates the number of SRLGs on the current link.
NeighborSystemId
FragmentNumber
Indicates the number of the LSP fragment.
Issue 07 (2014-07-30)

283

Log Reference
44 ISIS
Possible Causes
1. No SRLG is added.
2. Failed to apply memory for the key data structure when adding the SRLG information.
3. The internal logic was incorrect.
Procedure
Step 1 Run the debugging isis receiving-packet-regular-content command and the debugging isis
update-packet command, and then analyze the received packet according to the packet type
and the system ID; check whether the packet does not carry an SRLG.
Step 2 If the TLV type is normal, perform the following:
l Run the display memory-usage command in the user view to check whether the system
memory usage is too high. If so, analyze the cause.
l If the memory usage is normal, contact the Huawei technical support personnel.
Step 3 If abnormality occurs in the TLV, check whether the switch sending the LSP is faulty.
Step 4 If the router is faulty, contact the Huawei technical support personnel.
Step 5 End.
----End
44.12 ISIS/6/ADD_SUMMRT_URT_FAIL
Message
ISIS/6/ADD_SUMMRT_URT_FAIL:ISIS [process-id] failed to add NULL0 route to URT for
summary. (MTID=[USHORT])
Description
IS-IS failed to add a null 0 summarized route to the URT.
Parameters
Parameter Name
Parameter Meaning
[process-id]
MTID
Possible Causes
Failed to add a null 0 summarized route to the URT.
Issue 07 (2014-07-30)

284

Log Reference
44 ISIS
Procedure
----End
44.13 ISIS/6/ADD_SUMRT_FAIL
Message
ISIS/6/ADD_SUMRT_FAIL:ISIS [process-id] failed to add the summary route for redistribute
route. (MTID=[USHORT])
Description
IS-IS failed to summarize the imported routes.
Parameters
Parameter Name
Parameter Meaning
[process-id]
MTID
Possible Causes
A summarized route was added.
Procedure
Step 1 Check why IS-IS failed to aggregate imported routes.
----End
44.14 ISIS/6/ADD_TE_TLV_FAIL
Message
ISIS/6/ADD_TE_TLV_FAIL:ISIS [process-id] failed to add tunnel neighbour TLV to link state
database.
Description
IS-IS failed to add the tunnel neighbor TLV to the LSDB.
Issue 07 (2014-07-30)

285

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to add the tunnel neighbor TLV to the LSDB.
Procedure
----End
44.15 ISIS/4/ADJ_CHANGE_LEVEL
Message
ISIS/4/ADJ_CHANGE_LEVEL:The neighbor of ISIS was changed. (IsisProcessId=
[USHORT], Neighbor=[STRING], InterfaceName=[STRING], CurrentState=[STRING],
ChangeType=[STRING], Level=[STRING])
Description
The IS-IS neighbor changed.
Parameters
IsisProcessId
Neighbor
InterfaceName
CurrentState
Indicates the current status, including the following:

l UP
l INIT
l DOWN
Issue 07 (2014-07-30)

286

Log Reference
44 ISIS

ChangeType
Indicates the type of a change.

l MULTIPLE_P2P_AD: indicates that repeated P2P neighbors appear.
l L1_CIRCUIT_DOWN: indicates that the Level-1 interface is Down.
l L2_CIRCUIT_DOWN: indicates that the Level-2 interface is Down.
l CIRCUIT_DOWN: indicates that the P2P interface is Down.
l CLEAR_L1_NEIGHBOUR: indicates that the Level-1 neighbor
changes after the undo isis command is used.
l CLEAR_L2_NEIGHBOUR: indicates that the Level-2 neighbor
changes after the undo isis command is used.
l CLEAR_NEIGHBOUR: indicates that the P2P neighbor changes after
the undo isis command is used.
l P2P_HOLDTIMER_EXPIRED: indicates the P2P neighbor times out.
l L1_HOLDTIMER_EXPIRED: indicates that the Level-1 neighbor
times out.
l L2_HOLDTIMER_EXPIRED: indicates that the Level-2 neighbor
times out.
l NEW_L1_ADJ: indicates a new Level-1 neighbor.
l NEW_L2_ADJ: indicates a new Level-2 neighbor.
l USGAGE_MISMATCH: indicates that the type of the neighbor is
different from that of the Hello message.
l UPDT_LSP_FAILED: indicates that updating the neighbor status in
the LSP fails.
l NO_MEMORY_FOR_HIGER_PRIORITY_ADJ: indicates that
there is no available memory for neighbors with high priorities.
l DIFFERENT_NET: indicates that the network address of the neighbor
changes.
l P2P_CIRCUIT_ID_CONFLT: indicates that IDs of P2P interfaces
conflict.
l NEW_ADJ: indicates a new P2P neighbor.
l AREA_MISMATCH: indicates the area address of the neighbor does
not match the local area address.
l 3_WAY_DOWN: indicates that the neighbor is Down during threeway handshake.
l 3_WAY_INIT: indicates that the neighbor is Init during three-way
handshake.
l 3_WAY_UP: indicates that the neighbor is Up during three-way
handshake.
l P2P_INIT_MEMORY_SHORTAGE: indicates that the memory is
not enough and the P2P neighbor is in the init state.
l PROTOCOL_V4_6_TO_V4: indicates that the neighbor type changes
from IPv4 and IPv6 to IPv4.
Issue 07 (2014-07-30)

287

Log Reference
44 ISIS

l PROTOCOL_V4_6_TO_V6: indicates that the neighbor type changes
from IPv4 and IPv6 to IPv6.
l PROTOCOL_V4_TO_V4_6: indicates that the neighbor type changes
from IPv4 to IPv4 and IPv6.
l PROTOCOL_V6_TO_V4_6: indicates that the neighbor type changes
from IPv6 to IPv4 and IPv6.
l PROTOCOL_V4_TO_V6: indicates that the neighbor type changes
from IPv4 to IPv6.
l PROTOCOL_V6_TO_V4: indicates that the neighbor type changes
from IPv6 to IPv4.
l L1_BFD_DOWN: indicates that Level-1 BFD is Down.
l L2_BFD_DOWN: indicates that Level-2 BFD is Down.
l L12_BFD_DOWN: indicates that Level-1-2 BFD is Down.
l TUNNEL_LEVEL_CHANGE: indicates that the tunnel level
changes.
l TUNNEL_L1_NEW: indicates that a Level-1 tunnel neighbor is
generated.
l TUNNEL_L2_NEW: indicates that a Level-2 tunnel neighbor is
generated.
l TUNNEL_L1_DOWN: indicates the Level-1 tunnel neighbor is
Down.
l TUNNEL_L2_DOWN: indicates the Level-2 tunnel neighbor is
Down.
l TUNNEL_L2_TO_L12: indicates that the neighbor changes from a
Level-2 neighbor to a Level-1-2 neighbor.
l TUNNEL_L1_TO_L12: indicates that the neighbor changes from a
Level-1 neighbor to a Level-1-2 neighbor.
l NEW_ADJ_CREATE: indicates that a new neighbor is generated.
l NO_COMMON_TOPOLOGY: indicates that the topology
information carried in the received Hello message is different from
that of the neighbor.
l REMOTE_IS_PACKET_CHANGED: indicates that the Hello
message sent by the remote neighbor changes.
l NO_SNPA_IN_IIH: indicates that the received Hello message does
not contain the SNPA address.
Level
Indicates the neighbor type.
Possible Causes
The IS-IS neighbor changed.
Issue 07 (2014-07-30)

288

Log Reference
44 ISIS
Procedure
----End
44.16 ISIS/6/ALIID_TLV_LEN_SHORT
Message
ISIS/6/ALIID_TLV_LEN_SHORT:ISIS [system-index] ALIAS ID TLV was shorter than valid
size. (ValidSize=[UCHAR])
Description
The IS-IS ALIAS ID TLV was too short.
Parameters
Parameter Name
Parameter Meaning
[system-index]
Indicates the ISIS system index.
ValidSize
Indicates the length of the TLV.
Possible Causes
The IS-IS ALIAS ID TLV was too short.
Procedure
----End
44.17 ISIS/6/AREA_ADDR_INVALID
Message
ISIS/6/AREA_ADDR_INVALID:ISIS manual area address instance was invalid.
Description
The IS-IS instance with a manually configured area address was invalid.
Issue 07 (2014-07-30)

289

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
An internal error of the system.
Procedure
----End
44.18 ISIS/6/AUTH_TLV_OVER_ONECE
Message
ISIS/6/AUTH_TLV_OVER_ONECE:ISIS [process-id] ignored the LSP because the
authentication TLV occurred more than one time.
Description
IS-IS ignored the LSP because the authentication TLV appeared for more than one time.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The authentication TLV appeared for more than one time.
Procedure
----End
44.19 ISIS/6/BAD_TLV_LEN
Issue 07 (2014-07-30)

290

Log Reference
44 ISIS
Message
ISIS/6/BAD_TLV_LEN:ISIS [process-id] received an LSP packet with invalid TLV length.
Description
IS-IS received an LSP packet with the TLV of an invalid length.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The length of the TLV in the received LSP packet was incorrect.
Procedure
----End
44.20 ISIS/6/BIND_SOKT_FAIL
Message
ISIS/6/BIND_SOKT_FAIL:ISIS [process-id] failed to bind the socket to the interface [interfacename]. (InterfaceIndex=[STRING], ReturnValue=[ULONG])
Description
IS-IS failed to bind a socket to an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
InterfaceIndex
Indicates the interface index.
ReturnValue
Issue 07 (2014-07-30)

291

Log Reference
44 ISIS
Possible Causes
Failed to bind a socket to an interface.
Procedure
Step 1 Check the configuration of the current link.
----End
44.21 ISIS/5/CIRC_STATE_SET
Message
ISIS/5/CIRC_STATE_SET:The status of the ISIS [process-id] interface is [interface-state].
(interface=[STRING])
Description
The log message was generated when the IS-IS interface status was changed.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-state]
The status of the IS-IS interface.

l MTU UP
l MTU DOWN
l IP UP,
l IP DOWN,
l LINK UP,
l LINK DOWN
interface
Possible Causes
reset isis all
isis enable
isis ipv6 enable
Issue 07 (2014-07-30)

292

Log Reference
44 ISIS
Procedure
----End
44.22 ISIS/6/CONFLICT_SYSTEM_ID
Message
ISIS/6/CONFLICT_SYSTEM_ID:ISIS [process-id] maybe detect conflicting System ID.
(System ID=[STRING])
Description
IS-IS detected conflicting system IDs.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Number of the IS-IS process
System ID
Conflicting system ID
Possible Causes
Two IS-IS routers in the topology have the same system ID.
Procedure
Step 1 Change the conflicting system ID.
----End
44.23 ISIS/6/CREA_AREA_TLV_FAIL
Message
ISIS/6/CREA_AREA_TLV_FAIL:ISIS [process-id] failed to create the area address TLV
option in extended LSP set.
Description
IS-IS failed to create the area address TLV option in extended LSP set.
Issue 07 (2014-07-30)

293

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The LSP fragment mode changed, and the area address TLV option should be created in the
LSP.
Procedure
Step 1 Check the cause of the failure to create the address TLV option in the extended LSP set.
----End
44.24 ISIS/6/CREATE_CIRCUIT_FAIL
Message
ISIS/6/CREATE_CIRCUIT_FAIL:ISIS [process-id] failed to create the interface.
Description
IS-IS failed to create the interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
44.25 ISIS/6/CRT_BFD_SESION_FAIL
Issue 07 (2014-07-30)

294

Log Reference
44 ISIS
Message
ISIS/6/CRT_BFD_SESION_FAIL:ISIS [process-id] failed to create the BFD session with peer
[system-id] [level] on the interface. (InterfaceName=[STRING], UserData=[ULONG])
Description
ISIS failed to set up a BFD session with its neighbor on an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[system-id]
Indicates the system ID.
[level]
InterfaceName
UserData
Indicates the address used to store the data structure of adjacencies.
Possible Causes
Failed to create a BFD session.
Procedure
Step 1 Run the display diagnostic-information command, save the display of the command, and
contact Huawei technical personnel.
----End
44.26 ISIS/6/CRT_P2P_ADJ_FAIL
Message
ISIS/6/CRT_P2P_ADJ_FAIL:ISIS [process-id] failed to create the P2P adjacency.
Description
IS-IS failed to create a P2P adjacency.
Issue 07 (2014-07-30)

295

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to create a P2P adjacency.
Procedure
----End
44.27 ISIS/6/DEL_ATTSY_FAIL
Message
ISIS/6/DEL_ATTSY_FAIL:ISIS [process-id] failed to delete the local attached system.
Description
IS-IS failed to delete the locally associated system.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
44.28 ISIS/6/DEL_BFD_SESSION_FAIL
Message
ISIS/6/DEL_BFD_SESSION_FAIL:ISIS [process-id] failed to delete the BFD session with peer
[system-id] [level] on the interface. (InterfaceName=[STRING], UserData=[ULONG])
Issue 07 (2014-07-30)

296

Log Reference
44 ISIS
Description
IS-IS failed to delete the BFD session with its neighbor on an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[system-id]
Indicates the system ID.
[level]
InterfaceName
UserData
Indicates the address used to store the data structure of adjacencies.
Possible Causes
Failed to delete a BFD session.
Procedure
Step 1 Run the display diagnostic-information command, save the display of the command, and
----End
44.29 ISIS/6/DEL_LKINFO_CSPF_FAIL
Message
ISIS/6/DEL_LKINFO_CSPF_FAIL:ISIS [process-id] failed to delete the TE link information
from CSPF. (ReturnValue=[ULONG], NeighborSystemId=[STRING],
NeighborPseudoNodeId=[USHORT], NodeStatus=[USHORT], FragmentNumber=
[USHORT])
Description
IS-IS failed to delete TE link information from CSPF.
Issue 07 (2014-07-30)

297

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
ReturnValue
NeighborSystemId
NodeStatus
FragmentNumber
Possible Causes
1. An internal error of the system.
Procedure
Step 1 Run the display mpls te cspf destination command to check whether there are paths that meet
specified restriction conditions.
----End
44.30 ISIS/6/DEL_NTWK_MPLS_FAIL
Message
ISIS/6/DEL_NTWK_MPLS_FAIL:ISIS [process-id] failed to delete the network information
in MPLS TE. (ReturnValue=[ULONG])
Description
IS-IS failed to delete network information from MPLS TE.
Issue 07 (2014-07-30)

298

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
ReturnValue
Possible Causes
Failed to delete network information from MPLS TE.
Procedure
----End
44.31 ISIS/6/DEL_SUMMRT_URT_FAIL
Message
ISIS/6/DEL_SUMMRT_URT_FAIL:ISIS [process-id] failed to delete the NULL0 route from
the URT for summary. (MTID=[USHORT])
Description
IS-IS failed to delete the null 0 summarized route from the URT.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the ID of an IS-S process.
MTID
Possible Causes
Failed to delete the null 0 summarized route from the URT.
Procedure
----End
44.32 ISIS/6/DISABL_RT_FAIL
Issue 07 (2014-07-30)

299

Log Reference
44 ISIS
Message
ISIS/6/DISABL_RT_FAIL:ISIS [process-id] failed to disable ISIS IP route on the interface
[interface-name].
Description
IS-IS failed to disable IS-IS IP routing on the interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Procedure
Step 1 Check the status of the route on the interface.
----End
44.33 ISIS/6/DISABLE_ROUTELEAK_V6
Message
ISIS/6/DISABLE_ROUTELEAK_V6:ISIS [process-id] failed to disable IPv6 route leaking.
Description
IS-IS failed to disable IPv6 route leaking.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Issue 07 (2014-07-30)

300

Log Reference
44 ISIS
Procedure
----End
44.34 ISIS/6/DYNC_NAME_FAIL
Message
ISIS/6/DYNC_NAME_FAIL:ISIS [process-id] failed to create the dynamic hostname TLV.
Description
ISIS failed to create a dynamic hostname TLV.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
44.35 ISIS/6/EN_TE_FAIL_NO_RTID
Message
ISIS/6/EN_TE_FAIL_NO_RTID:ISIS [process-id] failed to enable TE because no router ID is
configured.
Description
IS-IS failed to enable TE because no router ID is configured.
Issue 07 (2014-07-30)

301

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to obtain the router ID.
Procedure
Step 1 Check the status of the switch .
----End
Message
ISIS/6/ENABLE_TE_LV1_FAIL:ISIS [process-id] failed to enable TE for Level-1.
Description
IS-IS failed to enable TE for the Level-1 interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to enable TE for the Level-1 interface.
Procedure
Step 1 Run the display this command in a specified IS-IS process to check whether a NET is configured.
If no NET is configured, configure a NET.
Step 2 Run the traffic-eng command in a specified IS-IS process to re-enable TE.
----End
Issue 07 (2014-07-30)

302

Log Reference
44 ISIS
Message
ISIS/6/ENABLE_TE_LV2_FAIL:ISIS [process-id] failed to enable TE for Level-2.
Description
IS-IS failed to enable TE for the Level-2 interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to enable TE for the Level-2 interface.
Procedure
Step 1 Run the display this command in a specified IS-IS process to check whether a NET is configured.
If no NET is configured, configure a NET.
Step 2 Run the traffic-eng command in a specified IS-IS process to re-enable TE.
----End
44.38 ISIS/6/FAIL_CMD_IN_AMB
Message
ISIS/6/FAIL_CMD_IN_AMB:ISIS on the AMB failed to run commands.(Function ID=
[ULONG], DisableFlag=[ULONG])
Description
IS-IS failed to run the command on the AMB.
Parameters
Parameter Name
Parameter Meaning
Function ID
Indicates the ID of the command line.
DisableFlag
Indicates the identifier of disabling the command line.
Issue 07 (2014-07-30)

303

Log Reference
44 ISIS
Possible Causes
This log message was caused by an unpredictable reason.
Procedure
Step 1 Run the display diagnostic-information command and save the command output; contact the
----End
44.39 ISIS/6/FAIL_CMD_IN_SMB
Message
ISIS/6/FAIL_CMD_IN_SMB:ISIS on the SMB failed to run commands.(Function ID=
[ULONG], DisableFlag=[ULONG])
Description
IS-IS failed to run the command on the SMB.
Parameters
Parameter Name
Parameter Meaning
Function ID
Indicates the ID of the command line.
DisableFlag
Indicates the identifier of disabling the command line.
Possible Causes
IS-IS failed to run the command line on the SMB.
Procedure
----End
44.40 ISIS/6/FAIL_CRT_OPT_DYN_NM
Message
ISIS/6/FAIL_CRT_OPT_DYN_NM:ISIS [process-id] failed to create the option for dynamic
host name.
Issue 07 (2014-07-30)

304

Log Reference
44 ISIS
Description
IS-IS failed to create the dynamic host name option.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
44.41 ISIS/6/FAIL_SEND_DICT
Message
ISIS/6/FAIL_SEND_DICT:ISIS [process-id] failed to send protocol dictionary to the low layer.
(InterfaceIndex=[STRING])
Description
IS-IS failed to deliver the protocol dictionary.
Parameters
Parameter Name
Parameter Meaning
[process-id]
InterfaceIndex
Possible Causes
Processing the protocol dictionary failed.
Procedure
----End
Issue 07 (2014-07-30)

305

Log Reference
44 ISIS
44.42 ISIS/6/FAIL_TRANS_P2P_CSNP
Message
ISIS/6/FAIL_TRANS_P2P_CSNP:ISIS [process-id] failed to transmit P2P CSNP on the
interface [interface-name].
Description
IS-IS failed to transmit P2P CSNP packets on the interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
An error occurred during restart.
Procedure
----End
44.43 ISIS/6/FD_CUR_IFINDEX_FAIL
Message
ISIS/6/FD_CUR_IFINDEX_FAIL:ISIS [process-id] failed to find circuit entry according to the
interface index [interface-index].
Description
IS-IS failed to find the link according to the interface index.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-index]
Issue 07 (2014-07-30)

306

Log Reference
44 ISIS
Possible Causes
Failed to find the link according to the interface index.
Procedure
Step 1 Check information about the specified interface.
----End
44.44 ISIS/6/FD_SBNTADDR_BDC_FAIL
Message
ISIS/6/FD_SBNTADDR_BDC_FAIL:ISIS [process-id] failed to find the matched subnet
address [subnet-address] in broadcast network.
Description
IS-IS failed to find a matching subnet address in a broadcast network.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[subnet-address]
Indicates the subnet address.
Possible Causes
Failed to obtain a subnet address.
Procedure
Step 1 Check the interface status of the switch.
----End
44.45 ISIS/6/FIND_CIRCUIT_FAIL
Message
ISIS/6/FIND_CIRCUIT_FAIL:Failed to find ISIS interface according to the interface index
[interface-index].
Description
Failed to find an IS-IS interface according to the interface index.
Issue 07 (2014-07-30)

307

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[interface-index]
the interface index.
Possible Causes
Procedure
----End
44.46 ISIS/6/FIND_SYSID_FAIL
Message
ISIS/6/FIND_SYSID_FAIL:Failed to find the ISIS process ID. (InterfaceIndex=[STRING])
Description
Failed to find the IS-IS process ID.
Parameters
Parameter Name
Parameter Meaning
InterfaceIndex
Possible Causes
Procedure
----End
44.47 ISIS/6/FLO_LSP_OLO_FAIL
Message
ISIS/6/FLO_LSP_OLO_FAIL:ISIS [process-id] failed to flood the LSP with overload bit set.
Issue 07 (2014-07-30)

308

Log Reference
44 ISIS
Description
IS-IS failed to flood the LSP with the overload bit.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to flood the LSP with the overload bit.
Procedure
----End
44.48 ISIS/6/FT_GT_RT_URM_FAIL
Message
ISIS/6/FT_GT_RT_URM_FAIL:ISIS [process-id] failed to obtain the route entry [route] from
URM. (RouteEntryTable=[ULONG], EntryId=[ULONG], MTID=[USHORT], ReturnValue=
[STRING])
Description
IS-IS failed to obtain a routing entry from URM.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[route]
Indicates a route.
RouteEntryTable
EntryId
Indicates the number of a routing entry.
MTID
ReturnValue
Issue 07 (2014-07-30)

309

Log Reference
44 ISIS
Possible Causes
Failed to obtain a routing entry from URM.
Procedure
----End
44.49 ISIS/6/GEN_ATT_LSP_FAIL
Message
ISIS/6/GEN_ATT_LSP_FAIL:ISIS [process-id] failed to generate an LSP with the ATT bit
being set.
Description
IS-IS failed to generate an LSP with the ATT bit.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to generate an LSP with the ATT bit.
Procedure
----End
44.50 ISIS/4/GENLSPDESC_FAILSMB
Message
ISIS/4/GENLSPDESC_FAILSMB:ISIS [process-id] failed to generate the Level-[level] LSP
fragment on the slave board. (LspId=[STRING], SeqNo=[ULONG])
Description
The IS-IS process on the slave board failed to originate the LSP fragment.
Issue 07 (2014-07-30)

310

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
indicates the ID of an IS-IS process.
[level]
indicates the IS-IS level.

l 1: Level-1
l 2: Level-2
LspId
indicates the ID of an LSP.
SeqNo
indicates the sequence number of an LSP.
Possible Causes
1. The slave board cannot find the corresponding LSP fragment.
2. Failed to allocate memory for the fragment data structure.
Procedure
----End
44.51 ISIS/6/GET_IF_FAILSMB
Message
ISIS/6/GET_IF_FAILSMB:ISIS [process-id] failed to obtain the interface according to the
interface index on the slave board. (InterfaceIndex=[STRING], MessageType=[STRING])
Description
The IS-IS process on the slave board failed to obtain the interface according to the interface
index.
Parameters
[process-id]
InterfaceIndex
Issue 07 (2014-07-30)

311

Log Reference
44 ISIS

MessageType
Indicates the message type of LSPs:

l Self LSP: indicates the self-originated LSPs.
l Other LSP: indicates other LSPs.
l AdjDelete: indicates neighbor information is deleted.
l AdjHello: indicates the Hello message received by the slave board.
l CircDis: indicates DIS information.
Possible Causes
1. The current interface on the slave board was inconsistent with the interface on the main board.
2. The backup interface index was incorrect.
Procedure
Step 1 Run the display rm interface command to check whether the interface index on the main board
is the same as that in the log.
Step 2 (Restart with caution.) You can restart the interface if services are not affected.
Step 4 End.
----End
44.52 ISIS/6/GET_IFINSTN_ID_FAIL
Message
ISIS/6/GET_IFINSTN_ID_FAIL:Failed to obtain interface instance ID according to the alias.
Description
Failed to obtain the ID of the instance on the interface through the alias.
Issue 07 (2014-07-30)

312

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to obtain the ID of the instance on the interface through the alias.
Procedure
----End
44.53 ISIS/6/GET_IFNET_BY_ALIAS
Message
ISIS/6/GET_IFNET_BY_ALIAS:Failed to obtain IFNET through alias.
Description
Failed to obtain IFNET through the alias.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
44.54 ISIS/6/GET_LINKINFO_FAIL
Issue 07 (2014-07-30)

313

Log Reference
44 ISIS
Message
ISIS/6/GET_LINKINFO_FAIL:ISIS [process-id] failed to obtain link information.
Description
IS-IS failed to obtain link information.
Parameters
Parameter Name
Parameter Meaning
[process-id]
InterfaceIndex
Possible Causes
Failed to obtain link information.
Procedure
Step 1 Check the configuration of the interface.
----End
44.55 ISIS/6/GT_ACTVE_RT_RM_FAIL
Message
ISIS/6/GT_ACTVE_RT_RM_FAIL:ISIS [process-id] failed to obtain active route from RM.
(MTID=[USHORT])
Description
IS-IS failed to obtain an active route from RM.
Parameters
Parameter Name
Parameter Meaning
[process-id]
MTID
Indicates the ID of topology.
Possible Causes
Issue 07 (2014-07-30)

314

Log Reference
44 ISIS
Procedure
----End
44.56 ISIS/6/GT_CIRC_IFINDX_FAIL
Message
ISIS/6/GT_CIRC_IFINDX_FAIL:ISIS [process-id] failed to obtain the circuit entry according
to the interface index [interface-index].
Description
IS-IS failed to find an interface according to the interface index.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-index]
Possible Causes
Procedure
----End
44.57 ISIS/6/GT_CIRCINDEX_FAIL
Message
ISIS/6/GT_CIRCINDEX_FAIL:ISIS [process-id] failed to obtain interface number [interfacename].
Description
IS-IS failed to obtain the interface number.
Issue 07 (2014-07-30)

315

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Procedure
Step 1 Check the configuration of the current interface.
----End
44.58 ISIS/6/GT_INFO_RDM_FAIL
Message
ISIS/6/GT_INFO_RDM_FAIL:ISIS [process-id] failed to obtain information from RDM.
Description
IS-IS failed to obtain information from URM.
Parameters
Parameter Name
Parameter Meaning
[process-id]
InterfaceIndex
Possible Causes
Failed to obtain information from URM.
Procedure
----End
Issue 07 (2014-07-30)

316

Log Reference
44 ISIS
44.59 ISIS/6/GT_ININDEX_FAIL
Message
ISIS/6/GT_ININDEX_FAIL:ISIS [process-id] failed to obtain interface index [interface-index].
Description
IS-IS failed to obtain an interface number.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-index]
Possible Causes
Failed to obtain an interface number.
Procedure
Step 1 Check the status of the interface.
----End
44.60 ISIS/6/GT_LGC_PHY_FAIL
Message
ISIS/6/GT_LGC_PHY_FAIL:ISIS [process-id] failed to obtain the primary logical index
[logical-index] through physical index [physical-index].
Description
IS-IS failed to obtain a logical interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[logical-index]
Indicates the logical interface number.
Issue 07 (2014-07-30)

317

Log Reference
44 ISIS
Parameter Name
Parameter Meaning
[physical-index]
Indicates the physical interface number.
Possible Causes
Failed to obtain a logical interface.
Procedure
Step 1 Check the physical interface.
----End
44.61 ISIS/6/GT_LGCIF_V6ADDR_FAIL
Message
ISIS/6/GT_LGCIF_V6ADDR_FAIL:ISIS [process-id] failed to obtain logical index [logicalindex] from IPv6 link local address [ipv6-address].
Description
IS-IS failed to obtain the logical index from an IPv6 link-local address.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[logical-index]
Indicates the logical interface number.
[ipv6-address]
Indicates an IPv6 address.
Possible Causes
Failed to obtain the logical index from an IPv6 link-local address.
Procedure
Step 1 Check the configuration of the local IP address.
----End
44.62 ISIS/6/GT_LGCL_SUBNET_FAIL
Issue 07 (2014-07-30)

318

Log Reference
44 ISIS
Message
ISIS/6/GT_LGCL_SUBNET_FAIL:ISIS [process-id] failed to obtain the logical index for local
subnet while matching the nexthop address [nexthop]. (PhysicalIndex=[ULONG])
Description
IS-IS failed to obtain the logical index for the local subnet when matching the next hop address.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[nexthop]
Indicates the IP address of the next hop.
PhysicalIndex
Possible Causes
Failed to obtain the logical index for the local subnet.
Procedure
----End
44.63 ISIS/6/GT_LV_RT_URM_FAIL
Message
ISIS/6/GT_LV_RT_URM_FAIL:ISIS [process-id] failed to obtain Level-[level] route entry
[route] from URM. (RouteEntryTable=[ULONG], EntryId=[ULONG], MTID=[USHORT],
ReturnValue=[STRING])
Description
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

319

Log Reference
44 ISIS
Parameter Name
Parameter Meaning
[level]
[route]
Indicates a route.
RouteEntryTable
EntryId
MTID
ReturnValue
Possible Causes
Procedure
----End
44.64 ISIS/6/GT_LV_RT_V6_URM_FAIL
Message
ISIS/6/GT_LV_RT_V6_URM_FAIL:ISIS [process-id] failed to obtain Level-[level] IPv6 route
entry [route] from URM. (RouteEntryTable=[ULONG], EntryId=[ULONG], MTID=
[USHORT], ReturnValue=[STRING])
Description
IS-IS failed to obtain an IPv6 routing entry from URM.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[level]
[route]
Indicates a route.
Issue 07 (2014-07-30)

320

Log Reference
44 ISIS
Parameter Name
Parameter Meaning
RouteEntryTable
EntryId
MTID
ReturnValue
Possible Causes
Failed to obtain an IPv6 routing entry from URM.
Procedure
----End
44.65 ISIS/6/GT_MPLSTE_RM_FAIL
Message
ISIS/6/GT_MPLSTE_RM_FAIL:ISIS [process-id] failed to obtain MPLS TE status from RM.
Description
IS-IS failed to obtain the MPLS TE status from RM.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to obtain the TE status.
Procedure
Step 1 Run the display current-configuration configuration mpls command to check the MPLS TE
configuration.
----End
Issue 07 (2014-07-30)

321

Log Reference
44 ISIS
44.66 ISIS/6/GT_PHYIF_IFNET_FAIL
Message
ISIS/6/GT_PHYIF_IFNET_FAIL:ISIS [process-id] failed to obtain physical index from the
Description
IS-IS failed to obtain the physical index from an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Failed to obtain the physical index from an interface.
Procedure
Step 1 Check the physical interface.
----End
44.67 ISIS/6/GT_RTENTRY_URM_FAIL
Message
ISIS/6/GT_RTENTRY_URM_FAIL:ISIS [process-id] failed to obtain the route entry from
URM. (EntryId=[ULONG], MTID=[USHORT])
Description
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

322

Log Reference
44 ISIS
Parameter Name
Parameter Meaning
EntryId
Indicates the ID of an entry.
MTID
Possible Causes
Procedure
----End
44.68 ISIS/6/GT_RTID_RM_FAIL
Message
ISIS/6/GT_RTID_RM_FAIL:ISIS [process-id] failed to obtain router ID from RM. (RouterId=
[ULONG])
Description
IS-IS failed to obtain the router ID from RM.
Parameters
Parameter Name
Parameter Meaning
[process-id]
RouterId
Indicates the ID of a switch.
Possible Causes
Failed to obtain the router ID from RM.
Procedure
Step 1 Check the router ID again.
----End
Issue 07 (2014-07-30)

323

Log Reference
44 ISIS
44.69 ISIS/6/GT_TELK_INFO_FAIL
Message
ISIS/6/GT_TELK_INFO_FAIL:ISIS [process-id] failed to obtain TE link information.
(InterfaceNumber=[STRING])
Description
IS-IS failed to obtain TE link information.
Parameters
Parameter Name
Parameter Meaning
[process-id]
InterfaceNumber
Indicates the number of an interface.
Possible Causes
Failed to obtain TE information.
Procedure
Step 1 Retry to obtain TE information.
----End
44.70 ISIS/6/GT_V6_PHYIF_FAIL
Message
ISIS/6/GT_V6_PHYIF_FAIL:ISIS [process-id] failed to obtain the IPv6 physical index
[physical-index] from the interface. (InterfaceIndex=[STRING])
Description
IS-IS failed to obtain the IPv6 physical index from an interface.
Issue 07 (2014-07-30)

324

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
[physical-index]
InterfaceIndex
Possible Causes
Failed to obtain the IPv6 physical index from an interface.
Procedure
Step 1 Check the current status of the interface.
----End
44.71 ISIS/6/GT_V6ADDR_PHYIF_FAIL
Message
ISIS/6/GT_V6ADDR_PHYIF_FAIL:ISIS [process-id] failed to obtain the IPv6 link local
address [ipv6-address] from the physical interface [physical-interface].
Description
IS-IS failed to obtain the IPv6 link-local address from a physical interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[ipv6-address]
Indicates an IPv6 address.
[physical-interface]
Possible Causes
Failed to obtain the IPv6 link-local address from a physical interface.
Procedure
Step 1 Check the current status of the interface.
----End
Issue 07 (2014-07-30)

325

Log Reference
44 ISIS
44.72 ISIS/6/IF_TEMP
Message
ISIS/6/IF_TEMP:The interface was a temporary interface. (IsisProcessId=[USHORT],
InterfaceIndex=[STRING])
Description
The interface was a temporary interface.
Parameters
Parameter Name
Parameter Meaning
IsisProcessId
InterfaceIndex
Possible Causes
Procedure
----End
44.73 ISIS/4/IMPORT_LIMIT_EXCEED
Message
ISIS/4/IMPORT_LIMIT_EXCEED:ISIS [process-id] The number of level-[level] imported
routes has exceeded the maximum limit. (sysMTIndex=[USHORT], sysMaxLimit=[ULONG],
sysTotalRedist=[ULONG])
Description
The number of external routes imported to an IS-IS area exceeded the maximum limit.
Issue 07 (2014-07-30)

326

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
ID of an IS-IS process
[level]
IS-IS level
sysMTIndex
Topology ID
sysMaxLimit
Maximum number of routes that can be imported
sysTotalRedist
Number of imported routes
Possible Causes
The number of external routes imported to the IS-IS process exceeded the maximum limit
configured for advertising routes.
Procedure
Step 1 Delete some imported routes.
----End
44.74 ISIS/4/IMPORT_LIMIT_RESTORE
Message
ISIS/4/IMPORT_LIMIT_RESTORE:ISIS [process-id] The number of level-[level] imported
routes is restored to less than or equal to the maximum limit. (sysMTIndex=[USHORT],
sysMaxLimit=[ULONG], sysTotalRedist=[ULONG])
Description
The number of imported routes in an IS-IS process fell below the maximum limit.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[level]
IS-IS level
sysMTIndex
Topology ID
sysMaxLimit
sysTotalRedist
Possible Causes
The number of imported routes in the IS-IS area fell below the maximum limit.
Issue 07 (2014-07-30)

327

Log Reference
44 ISIS
Procedure
----End
44.75 ISIS/6/INIT_DEC_FAIL
Message
ISIS/6/INIT_DEC_FAIL:ISIS [process-id] failed to initialize the decision module.
Description
IS-IS failed to initialize the decision module.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Failed to initialize the decision module.
Procedure
----End
44.76 ISIS/4/INT_BUILDRUN_FAIL
Message
ISIS/4/INT_BUILDRUN_FAIL:ISIS failed to buildrun for interface [STRING],operate code=
[USHORT],return value=[USHORT].
Description
IS-IS failed to generate the Build Run information of the interface.
Issue 07 (2014-07-30)

328

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the name of the interface.
[USHORT]
The value of operate code.

l 1: To obtain the number of the interface index.
l 2: To obtain the name of the interface.
[USHORT]
Indicates the return value of the oepration.
Possible Causes
Failed to obtain the interface.
Procedure
----End
44.77 ISIS/6/INTI_ISIS_FAIL
Message
ISIS/6/INTI_ISIS_FAIL:ISIS [process-id] failed to initialize ISIS protocol modules.
Description
IS-IS failed to initialize IS-IS protocol modules.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

329

Log Reference
44 ISIS
44.78 ISIS/3/INVALID_DSTEMOD
Message
ISIS/3/INVALID_DSTEMOD:IS-IS obtained incorrect information about the DS-TE mode
from RM. (ProcessId=[USHORT], ModeInfo=[ULONG])
Description
IS-IS obtained incorrect DS-TE mode information from the RM.
Parameters
Parameter Name
Parameter Meaning
ProcessId
ModeInfo
Indicates the DS-TE mode.
Possible Causes
1. An error occurred in the callback function between IS-IS and the RM.
2. An error occurred in MPLS processing.
Procedure
Step 1 Re-configure the DS-TE mode in the MPLS view. Check whether the corresponding log is
displayed.
l If IS-IS successfully obtains the DS-TE mode information, go to Step 2.
l If IS-IS fails to obtain the information after several reconfigurations, go to Step 3.
Step 2 Services are not affected, no action is required.
----End
44.79 ISIS/6/INVID_DR_CHANGE
Message
ISIS/6/INVID_DR_CHANGE:The DIS change event is invalid. (IsisProcessId=[USHORT])
Description
The DIS change event was invalid.
Issue 07 (2014-07-30)

330

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
IsisProcessId
Possible Causes
The DR change event was invalid.
Procedure
Step 1 Check why the DIS change event was invalid.
----End
44.80 ISIS/6/INVID_TLV_TYPE_REP
Message
ISIS/6/INVID_TLV_TYPE_REP:ISIS failed to replace the old TLV because TLV type is
invalid. (IsisProcessId=[USHORT])
Description
IS-IS failed to replace the old TLV because the TLV type was invalid.
Parameters
Parameter Name
Parameter Meaning
IsisProcessId
Possible Causes
IS-IS failed to replace the old TLV because the TLV type was invalid.
Procedure
Step 1 Check the TLV type.
----End
44.81 ISIS/6/JN_MTCAST_ADDR_FAIL
Issue 07 (2014-07-30)

331

Log Reference
44 ISIS
Message
ISIS/6/JN_MTCAST_ADDR_FAIL:Failed to join the multicast group. (InterfaceIndex=
[STRING], ReturnValue=[LONG])
Description
Failed to join a multicast group.
Parameters
Parameter Name
Parameter Meaning
InterfaceIndex
ReturnValue
Possible Causes
Procedure
----End
Message
ISIS/6/JOIN_L1_ADDR_FAIL:ISIS [process-id] failed to join all Level-1 multicast group for
the interface [interface-name].
Description
IS-IS failed to join any Level-1 multicast group on an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Issue 07 (2014-07-30)

332

Log Reference
44 ISIS
Procedure
----End
Message
ISIS/6/JOIN_L2_ADDR_FAIL:ISIS [process-id] failed to join all Level-2 multicast group for
Description
IS-IS failed to join any Level-2 multicast group on an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Procedure
----End
44.84 ISIS/6/JOIN_ALLIS_ADDR_FAIL
Message
ISIS/6/JOIN_ALLIS_ADDR_FAIL:ISIS [process-id] failed to join ALLIS multicast group for
Description
IS-IS failed to join multicast groups on an interface.
Issue 07 (2014-07-30)

333

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Failed to call the socket function.
Procedure
----End
44.85 ISIS/6/L3VPN_FRR_CHANGE
Message
ISIS/6/L3VPN_FRR_CHANGE:L3VPN notified IS-IS that FRR changed.(VrfId=[USHORT])
Description
L3VPN notified IS-IS of the change of the Fast Reroute (FRR).
Parameters
Parameter Name
Parameter Meaning
VrfId
Indicates the ID of the Virtual Route Forwarding (VRF).
Possible Causes
The ip frr route-policy route-policy-name command was run in the system view to enable IP
FRR of the public network.
Procedure
----End
44.86 ISIS/6/LDP_INFORM_RM_ENAB
Issue 07 (2014-07-30)

334

Log Reference
44 ISIS
Message
ISIS/6/LDP_INFORM_RM_ENAB:IS-IS [process-id] informed RM that ldp-sync was enabled
Description
IS-IS notified the RM that LDP synchronization was enabled on the interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
IS-IS and LDP synchronization was enabled.
Procedure
----End
Message
ISIS/6/LEAVE_L1_ADDR_FAIL:ISIS [process-id] failed to leave all Level-1 multicast group
on the circuit [interface-name].
Description
IS-IS failed to leave any Level-1 multicast group on an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Failed to leave a multicast group.
Issue 07 (2014-07-30)

335

Log Reference
44 ISIS
Procedure
----End
Message
ISIS/6/LEAVE_L2_ADDR_FAIL:ISIS [process-id] failed to leave all Level-2 multicast group
Description
IS-IS failed to leave any Level-2 multicast group on an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Procedure
----End
44.89 ISIS/6/LEAVE_ALLIS_ADDR_FAIL
Message
ISIS/6/LEAVE_ALLIS_ADDR_FAIL:ISIS [process-id] failed to leave ALLIS multicast group
Description
IS-IS failed to leave multicast groups on an interface.
Issue 07 (2014-07-30)

336

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Failed to call the socket function.
Procedure
----End
44.90 ISIS/5/LOCALSYS_DIS_REST_RT
Message
ISIS/5/LOCALSYS_DIS_REST_RT:Local system was DIS among ISIS restarted capable
routers.
Description
The local system was elected as the DIS among switch enabled with IS-IS GR.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
The IIH packet in which the restart TLV has the RA bit was received during IS-IS GR.
Procedure
----End
44.91 ISIS/6/LV_MTCAST
Issue 07 (2014-07-30)

337

Log Reference
44 ISIS
Message
ISIS/6/LV_MTCAST:ISIS leaves multicast groups because ISIS received packet on unknown
Description
IS-IS left a multicast group because IS-IS received a packet on an unknown interface.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
Received a packet on an unknown interface.
Procedure
----End
44.92 ISIS/6/LV_MTCAST_ADDR_FAIL
Message
ISIS/6/LV_MTCAST_ADDR_FAIL:Failed to leave the multicast group. (InterfaceIndex=
[STRING], ReturnValue=[LONG])
Description
Parameters
Parameter Name
Parameter Meaning
InterfaceIndex
ReturnValue
Possible Causes
Issue 07 (2014-07-30)

338

Log Reference
44 ISIS
Procedure
----End
44.93 ISIS/6/MATCH_CIRC_FAIL
Message
ISIS/6/MATCH_CIRC_FAIL:ISIS [process-id] failed to match interface address.
Description
IS-IS failed to match an interface address.
Parameters
Parameter Name
Parameter Meaning
[process-id]
InterfaceIndex
Possible Causes
Failed to match an interface address.
Procedure
Step 1 Reconfigure the interface address.
----End
44.94 ISIS/6/MD_LV_RT_FAIL
Message
ISIS/6/MD_LV_RT_FAIL:ISIS [process-id] failed to modify Level-[level] route entry [route].
(EntryId=[ULONG], MTID=[USHORT], ReturnValue=[STRING])
Description
IS-IS failed to change a routing entry.
Issue 07 (2014-07-30)

339

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
[level]
[route]
Indicates a route.
EntryId
MTID
ReturnValue
Indicates a return value.
Possible Causes
Failed to change a routing entry.
Procedure
----End
44.95 ISIS/6/MD_LV_RT_V6_FAIL
Message
ISIS/6/MD_LV_RT_V6_FAIL:ISIS [process-id] failed to modify Level-[level] IPv6 route entry
[route]. (EntryId=[ULONG], MTID=[USHORT], ReturnValue=[STRING])
Description
IS-IS failed to change an IPv6 routing entry.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[level]
[route]
Indicates a route.
Issue 07 (2014-07-30)

340

Log Reference
44 ISIS
Parameter Name
Parameter Meaning
EntryId
MTID
ReturnValue
Indicates a return value.
Possible Causes
Failed to change an IPv6 routing entry.
Procedure
----End
44.96 ISIS/6/MDF_LKINFO_CSPF_FAIL
Message
ISIS/6/MDF_LKINFO_CSPF_FAIL:ISIS [process-id] failed to modify TE link information to
Description
IS-IS failed to modify TE link information in CSPF.
Parameters
Parameter Name
Parameter Meaning
[process-id]
ReturnValue
NeighborSystemId
NodeStatus
FragmentNumber
Issue 07 (2014-07-30)

341

Log Reference
44 ISIS
Possible Causes
1. An internal error of the system.
Procedure
----End
44.97 ISIS/6/MDF_NTWK_MPLS_FAIL
Message
ISIS/6/MDF_NTWK_MPLS_FAIL:ISIS [process-id] failed to modify network information in
MPLS TE. (ReturnValue=[ULONG])
Description
IS-IS failed to modify network information in MPLS TE.
Parameters
Parameter Name
Parameter Meaning
[process-id]
ReturnValue
Possible Causes
Failed to modify network information in MPLS TE.
Procedure
----End
44.98 ISIS/6/MTU_EXCEED_MAXPDU
Message
ISIS/6/MTU_EXCEED_MAXPDU:The MTU size [mtu-size] exceeded the maximum PDU
size [pdu-size], and set the MTU to the maximum PDU size. (IsisProcessId=[USHORT],
InterfaceIndex=[STRING])
Issue 07 (2014-07-30)

342

Log Reference
44 ISIS
Description
The MTU size exceeded the maximum PDU size, and was set to the maximum PDU size.
Parameters
Parameter Name
Parameter Meaning
[mtu-size]
Indicates the size of the MTU.
[pdu-size]
Indicates the size of the PDU.
IsisProcessId
InterfaceIndex
Possible Causes
The size of the MTU was too large.
Procedure
Step 1 Reconfigure the size of the MTU.
----End
44.99 ISIS/6/NSR_MSG_PROC
Message
ISIS/6/NSR_MSG_PROC:ISIS received a message from RM. TaskID is [task-id], MsgType is
[message-type], NSR configuration is [nsr-status].
Description
During NSR, the IS-IS process received a message.
Parameters
Parameter Name
Parameter Meaning
[task-id]
indicates the task ID.
[message-type]
indicates the message type.
[nsr-status]
indicates the NSR status.

l 0: indicates that NSR is not configured.
l 1: indicates that NSR is configured.
Issue 07 (2014-07-30)

343

Log Reference
44 ISIS
Possible Causes
RM instructed IS-IS to enable NSR, perform backup, and smooth configurations.
Procedure
----End
44.100 ISIS/6/NSR_STATE_CHANGE
Message
ISIS/6/NSR_STATE_CHANGE:ISIS on the slave board received the message that NSR was
enabled.
Description
ISIS on the slave board received the message that NSR was enabled.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Global data was backed up on the slave board when NSR was enabled.
Procedure
----End
44.101 ISIS/6/P2P_CIRC_TX_LSP_FAIL
Message
ISIS/6/P2P_CIRC_TX_LSP_FAIL:ISIS [process-id] failed to transmit LSP on the p2p circuit.
(CircuitName=[string])
Description
IS-IS failed to transmit LSPs on a P2P link.
Issue 07 (2014-07-30)

344

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
CircuitName
Possible Causes
Failed to transmit LSPs on a P2P interface.
Procedure
Step 1 Check information about the current packet.
----End
44.102 ISIS/4/PEER_DOWN_BFDDOWN
Message
ISIS/4/PEER_DOWN_BFDDOWN:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because the BFD node was down. The Hello packet was received at
[hello-time] last time; the maximum interval for sending Hello packets was [max-interval]; the
local switch sent [send-number] Hello packets and received [receive-number] packets; the type
of the Hello packet was [packet-type].
Description
The IS-IS neighbor went Down on the interface because the BFD node became Down.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
Indicates the time when a Hello packet was received last time.
[max-interval]
Indicates the maximum interval for sending Hello packets.
[send-number]
Indicates the number of Hello packets that were sent.
[receive-number]
Indicates the number of Hello packets that were received.
Issue 07 (2014-07-30)

345

Log Reference
44 ISIS

[packet-type]
Indicates the type of the Hello packet. The type can be

l P2P: indicates the P2P Hello packet.
l Lan Level-1: indicates the Hello packet in the Level-1 broadcast
network.
network.
Possible Causes
The BFD node became Down, and thus the IS-IS neighbor went Down.
Procedure
----End
44.103 ISIS/4/PEER_DOWN_CIRC_DOWN
Message
ISIS/4/PEER_DOWN_CIRC_DOWN:ISIS [process-id] neighbor [neighbor] was Down
because interface [interface-name] was Down. The Hello packet was received at [hello-time]
last time; the maximum interval for sending Hello packets was [max-interval]; the local
switch sent [send-number] Hello packets and received [receive-number] packets; the type of the
Hello packet was [packet-type].
Description
The IS-IS neighbor went Down because the interface became Down.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
Issue 07 (2014-07-30)

346

Log Reference
44 ISIS

[packet-type]

network.
network.
Possible Causes
1. The shutdown command was run on the interface.
2: Abnormality occurred on the interface.
Procedure
Step 1 Judge whether the neighbor relationship needs to be established on the interface. If so, go to
Step 2; if not, go to Step 3.
Step 2 Run the display rm interface verbose command and save the command output; contact the
Step 3 End.
----End
44.104 ISIS/4/PEER_DOWN_DIS_CHANGE
Message
ISIS/4/PEER_DOWN_DIS_CHANGE:IS-IS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because the DIS changed. The Hello packet was received at [hellotime] last time; the maximum interval for sending Hello packets was [max-interval]; the local
Description
The IS-IS neighbor went Down on the interface because the Designated Intermediate System
(DIS) changed.
Parameters
[process-id]
[neighbor]
Issue 07 (2014-07-30)

347

Log Reference
44 ISIS

[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The DIS of the broadcast network changed, and thus the IS-IS neighbor went Down.
Procedure
Step 1 If a small number of logs are generated, wait for a while to see whether the normal state is entered.
If so, no action is required.
Step 2 If a large number of logs are generated, contact the Huawei technical support personnel.
----End
44.105 ISIS/4/PEER_DOWN_LOW_MEMORY
Message
ISIS/4/PEER_DOWN_LOW_MEMORY:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because memory was not enough. The Hello packet was received at
of the Hello packet was [packet-type]; CPU usage was [cpu-percent]%.
Description
The IS-IS neighbor went Down on the interface because the memory was insufficient.
Parameters
[process-id]
Issue 07 (2014-07-30)

348

Log Reference
44 ISIS

[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
[cpu-percent]
Indicates the CPU usage.
Possible Causes
The insufficient memory caused the IS-IS neighbor to become Down.
Procedure
----End
44.106 ISIS/4/PEER_DOWN_NO_MEMORY
Message
ISIS/4/PEER_DOWN_NO_MEMORY:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because the memory of RM was not enough. The Hello packet was
received at [hello-time] last time; the maximum interval for sending Hello packets was [maxinterval]; the local switch sent [send-number] Hello packets and received [receive-number]
packets; the type of the Hello packet was [packet-type];CPU usage was [cpu-percent]%.
Description
The IS-IS neighbor went Down on the interface because the RM memory was insufficient.
Issue 07 (2014-07-30)

349

Log Reference
44 ISIS
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
[cpu-percent]
Possible Causes
The insufficient RM memory caused the IS-IS neighbor to become Down.
Procedure
----End
44.107 ISIS/4/PEER_DOWN_REPTADJ
Message
ISIS/4/PEER_DOWN_REPTADJ:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because a repeated neighbor was found. The Hello packet was
packets; the type of the Hello packet was [packet-type].
Description
The IS-IS neighbor went Down on the interface because two same neighbors were detected.
Issue 07 (2014-07-30)

350

Log Reference
44 ISIS
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
A repeated neighbor was found, and thus the IS-IS neighbor went Down.
Procedure
----End
44.108 ISIS/4/PEER_DOWN_REPTP2PADJ
Message
ISIS/4/PEER_DOWN_REPTP2PADJ:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because repeated P2P neighbors were found. The Hello packet was
packets; the type of the Hello packet was [packet-type].
Description
The IS-IS neighbor went Down on the interface because two same P2P neighbors were detected.
Issue 07 (2014-07-30)

351

Log Reference
44 ISIS
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
Two same P2P neighbors were found, and thus the IS-IS neighbor went Down.
Procedure
----End
44.109 ISIS/4/PEER_DOWN_RPRDOWN
Message
ISIS/4/PEER_DOWN_RPRDOWN:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because the RPR node was Down. The Hello packet was received at
local router sent [sent-number] Hello packets and received [receive-number] packets; the type
Description
The IS-IS neighbor went Down on the interface because the RPR node became Down.
Issue 07 (2014-07-30)

352

Log Reference
44 ISIS
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[sent-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The RPR node became Down, and thus the IS-IS neighbor went Down.
Procedure
----End
44.110 ISIS/4/PEER_DWN_ADJ_STATDWN
Message
ISIS/4/PEER_DWN_ADJ_STATDWN:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because the adjacency status changed into Down. The Hello packet
was received at [hello-time] last time; the maximum interval for sending Hello packets was
[max-interval]; the local switch sent [send-number] Hello packets and received [receivenumber] packets; the type of the Hello packet was [packet-type].
Description
The adjacency status changed to Down, and thus the IS-IS neighbor became Down.
Issue 07 (2014-07-30)

353

Log Reference
44 ISIS
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The IS-IS neighbor went Down because the adjacency status became Down.
Procedure
Step 2 Check the status of the switchs between which the neighbor relationship is established.
Step 4 End.
----End
44.111 ISIS/4/PEER_DWN_AREAMISMACH
Message
ISIS/4/PEER_DWN_AREAMISMACH:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because area mismatched. The Hello packet was received at [hellotime] last time; the maximum interval for sending Hello packets was [max-interval]; the local
Issue 07 (2014-07-30)

354

Log Reference
44 ISIS
Description
The IS-IS neighbor went Down on the interface because areas were mismatched.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The area addresses were mismatched, and thus the IS-IS neighbor became Down.
Procedure
Step 2 Run the is-level command to configure proper levels for the two switchs between which the
neighbor relationship is established. If the levels are correct, run the network-entity command
to reconfigure NET for the switchs.
Step 3 End.
----End
44.112 ISIS/4/PEER_DWN_CIRC_SILENT
Message
ISIS/4/PEER_DWN_CIRC_SILENT:ISIS [process-id] neighbor [neighbor] was Down because
silent is set on interface [interface-name]. The Hello packet was received at [hello-time] last
time; the maximum interval for sending Hello packets was [max-interval]; the local switch sent
Issue 07 (2014-07-30)

355

Log Reference
44 ISIS
[send-number] Hello packets and received [receive-number] Hello packets; the type of the Hello
packet was [packet-type].
Description
The IS-IS neighbor went Down because the interface was configured as a silent interface.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The interface was configured as a silent interface, that is, the interface was suppressed, and thus
the IS-IS neighbor went Down.
Procedure
Step 2 Run the undo isis silent command to restore the interface to the default mode.
Step 3 End.
----End
44.113 ISIS/4/PEER_DWN_HLDTMR_EXPR
Message
ISIS/4/PEER_DWN_HLDTMR_EXPR:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because hold timer expired. The Hello packet was received at [helloIssue 07 (2014-07-30)

356

Log Reference
44 ISIS
time] last time; the maximum interval for sending Hello packets was [max-interval]; the local
Hello packet was [packet-type]; CPU usage was [cpu-percent]%.
Description
The IS-IS neighbor went Down on the interface because the Hold timer expired.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
[cpu-percent]
Possible Causes
A Hello packet was not received from the neighbor within the time period specified by the Hold
timer, and thus the IS-IS neighbor became Down.
Procedure
Step 2 Check the status of the switchs between which the neighbor relationship is established.
Step 4 End.
----End
44.114 ISIS/4/PEER_DWN_ID_CONFLICT
Issue 07 (2014-07-30)

357

Log Reference
44 ISIS
Message
ISIS/4/PEER_DWN_ID_CONFLICT:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because P2P circuit ID conflict. The Hello packet was received at
Description
The IS-IS neighbor went Down on the interface due to the conflicting P2P circuit IDs.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The circuit IDs on the P2P link conflicted, and thus the IS-IS neighbor went Down.
Procedure
----End
44.115 ISIS/4/PEER_DWN_LEVEL_CHANG
Issue 07 (2014-07-30)

358

Log Reference
44 ISIS
Message
ISIS/4/PEER_DWN_LEVEL_CHANG:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because adjacency level was changed. The Hello packet was received
at [hello-time] last time; the maximum interval for sending Hello packets was [max-interval];
the local switch sent [send-number] Hello packets and received [receive-number] packets; the
type of the Hello packet was [packet-type].
Description
The IS-IS neighbor went Down on the interface because the level of the neighbor changed.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The change of neighbor levels caused the IS-IS neighbor to become Down.
Procedure
Step 2 Run the is-level command to configure proper levels for the two switchs between which the
neighbor relationship is established.
Step 3 End.
----End
Issue 07 (2014-07-30)

359

Log Reference
44 ISIS
44.116 ISIS/4/PEER_DWN_PDUMISMATCH
Message
ISIS/4/PEER_DWN_PDUMISMATCH:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because the PDU mismatched. The Hello packet was received at
Description
The IS-IS neighbor went Down on the interface because the received PDU did not match the
local specifications.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The mismatched PDU caused the IS-IS neighbor to become Down.
Procedure
----End
Issue 07 (2014-07-30)

360

Log Reference
44 ISIS
44.117 ISIS/4/PEER_DWN_SYS_DISABLE
Message
ISIS/4/PEER_DWN_SYS_DISABLE:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because ISIS was disabled. The Hello packet was received at [hellotime] last time; the maximum interval for sending Hello packets was [max-interval]; the local
Description
The IS-IS neighbor went Down on the interface because ISIS was disabled.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
IS-IS was disabled, and thus the IS-IS neighbor went Down.
Procedure
----End
Issue 07 (2014-07-30)

361

Log Reference
44 ISIS
44.118 ISIS/4/PEER_DWN_SYSTYP_UNKN
Message
ISIS/4/PEER_DWN_SYSTYP_UNKN:ISIS [process-id] neighbor [neighbor] was Down on
interface [interface-name] because the system type was unknown. The Hello packet was received
at [hello-time] last time; the maximum interval for sending Hello packets was [max-interval];
the local switch sent [send-number] Hello packets and received [receive-number] packets; the
type of the Hello packet was [packet-type].
Description
The IS-IS neighbor went Down on the interface because the system type was unknown.
Parameters
[process-id]
[neighbor]
[interface-name]
[hello-time]
[max-interval]
[send-number]
[receive-number]
[packet-type]

network.
network.
Possible Causes
The unknown system type of the neighbor caused the IS-IS neighbor to become Down.
Procedure
----End
Issue 07 (2014-07-30)

362

Log Reference
44 ISIS
44.119 ISIS/5/PEER_UP_ADJ_CREATE
Message
ISIS/5/PEER_UP_ADJ_CREATE:ISIS process id [process-id] neighbor [system-id] on the
interface [interface-name] is up.
Description
IS-IS neighbor is Up.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[system-id]
[interface-name]
Possible Causes
IS-IS neighbor is Up.
Procedure
----End
44.120 ISIS/6/PROCESS_TMR_EVENT
Message
ISIS/6/PROCESS_TMR_EVENT:A timer expired when ISIS process was invalid.
(TimerEvent=[ULONG], ProcessId=[ULONG])
Description
A timer expired when IS-IS process was invalid.
Issue 07 (2014-07-30)

363

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
TimerEvent
Indicates the type of a timer.
ProcessId
Possible Causes
A timer expired when IS-IS process was invalid.
Procedure
----End
44.121 ISIS/6/RCV_BFD_DET_EVENT
Message
ISIS/6/RCV_BFD_DET_EVENT:The BFD detection down event was received.
Description
The BFD detect Down event was received.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
A BFD message from RM was received, which was helpful for locating problems between
modules.
Procedure
----End
44.122 ISIS/4/RCV_ERRSELFLSP_SMB
Issue 07 (2014-07-30)

364

Log Reference
44 ISIS
Message
ISIS/4/RCV_ERRSELFLSP_SMB:ISIS [process-id] received an incorrect backup self LSP on
the slave board. (LspId=[STRING], Level=[STRING], Reason=[STRING], SeqNum=
[STRING], TlvType=[USHORT], TlvLength=[USHORT])
Description
The slave board received the incorrect self-LSP.
Parameters
[process-id]
indicates the ID of an IS-IS process.
LspId
indicates the ID of an LSP.
Level
indicates the IS-IS level.

l 1: Level-1
l 2: Level-2
Reason
indicates the cause for the error:

l Wrong LSP length: indicates that the length of the received LSP is
incorrect.
l Wrong TLV length: indicates that the TLV length is incorrect.
l Receive reduplicate TLV: indicates that the duplicated TLV is
received.
l Wrong TLV place: indicates that the location of the TLV is incorrect.
l Encoding after Nbr TLV: indicates that the IS-IS process receives the
area address TLV after receiving the NBR TLV.
l Detect invalid MT ID: indicates that the unavailable MT ID is detected.
l Wrong TLV format: indicates that the TLV format is incorrect.
l Unknown TLV type: indicates the unknown TLV type.
l Had received more than three area address(es): indicates that the ISIS process has received more than three area addresses.
l Received too long area address: indicates that the too long area address
is received.
l Received wrong area address length: indicates that the length of the
area address TLV is incorrect.
l Received invalid area address: indicates that the current area address
is unavailable.
l Received more than three area address(es): indicates that there are
more than three area addresses in the TLV.
Issue 07 (2014-07-30)

365

Log Reference
44 ISIS

SeqNum
indicates the sequence number of an LSP.
TlvType
indicates the TLV type.
TlvLength
indicates the TLV length.
Possible Causes
The slave board received the incorrect self-LSP.
Procedure
Step 1 Collect the debugging information and the log to check the contents of the LSP on the slave
board and then compare it with the LSP on the main board to locate the fault.
----End
44.123 ISIS/6/RCV_NODE_DOWN_EVENT
Message
ISIS/6/RCV_NODE_DOWN_EVENT:The node Down event sent by RPR was received.
Description
A node Down event notified by the RPR was received.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
A BFD message from the RM was received, which was helpful for locating problems between
modules.
Procedure
----End
Issue 07 (2014-07-30)

366

Log Reference
44 ISIS
44.124 ISIS/6/RCV_RPR_EVENT
Message
ISIS/6/RCV_RPR_EVENT:The RPR [message-type] event was received.
Description
An RPR event was received.
Parameters
[message-type]
Indicates the type of a message. The types of messages are as follows

1) NODE DOWN: indicates a Down node.
2) UNEXPECTED: indicates an unexpected node.
Possible Causes
Received an RPR message from RM, which was helpful for locating problems between modules.
Procedure
----End
44.125 ISIS/6/RCV_RPRMSG
Message
ISIS/6/RCV_RPRMSG:The RPR message was received from RM. (MessageType=[ULONG],
IfnetIndex=[STRING], NodeNumber=[ULONG])
Description
The Resilient Packet Ring (RPR) message was received from the RM.
Parameters
Parameter Name
Parameter Meaning
MessageType
Indicates the message type.
Issue 07 (2014-07-30)

367

Log Reference
44 ISIS
Parameter Name
Parameter Meaning
IfnetIndex
Indicates the IFNET index.
NodeNumber
Indicates the number of nodes.
Possible Causes
Received an RPR message from the RM, which was helpful for locating problems between
modules.
Procedure
----End
44.126 ISIS/6/REA_MAX_SEQ_NUM
Message
ISIS/6/REA_MAX_SEQ_NUM:ISIS [process-id] reached maximum sequence number.
Description
IS-IS LSP sequence number reached the maximum value.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The LSP sequence number was updated and reached the maximum value.
Procedure
----End
44.127 ISIS/6/REC_RM_MEM_RESTORE
Issue 07 (2014-07-30)

368

Log Reference
44 ISIS
Message
ISIS/6/REC_RM_MEM_RESTORE:ISIS [process-id] received memory restoration
notification from RM.
Description
IS-IS received a notification for memory restoration from the RM.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Memory was restored from shortage to the normal state.
Procedure
----End
44.128 ISIS/4/REC_RM_MEM_SHORT
Message
ISIS/4/REC_RM_MEM_SHORT:ISIS [process-id] received memory shortage notification
from RM.
Description
IS-IS received the memory shortage notification from RM.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Received the memory shortage notification from RM.
Issue 07 (2014-07-30)

369

Log Reference
44 ISIS
Procedure
----End
44.129 ISIS/4/REDIST_THRESHOLD_REACH
Message
ISIS/4/REDIST_THRESHOLD_REACH: ISIS [process-id] The number of level-[level]
imported routes has reached the upper threshold value. (sysMTIndex=[USHORT],
sysMaxLimit=[ULONG], sysUpperThresholdValue=[ULONG], sysLowerThresholdValue=
[ULONG], sysTotalRedist=[ULONG])
Description
The number of external routes imported to an IS-IS area reached the alarm upper threshold.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[level]
IS-IS level
sysMTIndex
Topology ID
sysMaxLimit
sysUpperThresholdValue
Alarm upper threshold
sysLowerThresholdValue
Alarm lower threshold
sysTotalRedist
Possible Causes
The number of external routes imported to the IS-IS area reached the alarm upper threshold.
Procedure
Step 1 Delete some imported routes.
----End
44.130 ISIS/4/REDIST_THRESHOLD_REACH_CLEAR
Issue 07 (2014-07-30)

370

Log Reference
44 ISIS
Message
ISIS/4/REDIST_THRESHOLD_REACH_CLEAR: ISIS [process-id] The number of level[level] imported routes has been less than the lower threshold value. (sysMTIndex=[USHORT],
sysMaxLimit=[ULONG], sysUpperThresholdValue=[ULONG], sysLowerThresholdValue=
[ULONG], sysTotalRedist=[ULONG])
Description
The number of external routes imported to an IS-IS area fell below the alarm lower threshold.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[level]
IS-IS level
sysMTIndex
Topology ID
sysMaxLimit
sysUpperThresholdValue
Alarm upper threshold
sysLowerThresholdValue
Alarm lower threshold
sysTotalRedist
Possible Causes
The number of external routes imported to the IS-IS area fell below the alarm lower threshold.
Procedure
----End
44.131 ISIS/6/RM_CIRC_CHANGE
Message
ISIS/6/RM_CIRC_CHANGE:ISIS [process-id] failed to send the message that the physical
interface changed.
Description
IS-IS failed to send the message that reported the change of the physical interface.
Issue 07 (2014-07-30)

371

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
IS-IS failed to send the message that reported the change of the physical interface.
Procedure
----End
44.132 ISIS/6/RM_CIRC_CHANGE_V6
Message
ISIS/6/RM_CIRC_CHANGE_V6:ISIS [process-id] failed to send the message that the IPv6
physical interface changed.
Description
IS-IS failed to send the message that reported the change of the IPv6 physical interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
IS-IS failed to send the message that reported the change of the IPv6 physical interface.
Procedure
----End
Issue 07 (2014-07-30)

372

Log Reference
44 ISIS
44.133 ISIS/6/RM_LOGICRC_CHGE
Message
ISIS/6/RM_LOGICRC_CHGE:ISIS [process-id] failed to send the message that the logical
interface changed.
Description
IS-IS failed to send the message that reported the change of the logical interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
IS-IS failed to send the message that reported the change of the logical interface.
Procedure
----End
44.134 ISIS/6/RM_LOGICRC_CHGE_V6
Message
ISIS/6/RM_LOGICRC_CHGE_V6:ISIS [process-id] failed to send the message that the IPv6
logical interface changed.
Description
IS-IS failed to send the message that reported the change of the IPv6 logical interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

373

Log Reference
44 ISIS
Possible Causes
IS-IS failed to send the message that reported the change of the IPv6 logical interface.
Procedure
----End
44.135 ISIS/6/SB_CIR_NOT_ENABLE
Message
ISIS/6/SB_CIR_NOT_ENABLE:ISIS [process-id] static BFD was not enabled on interface
[interface-name].(InterfaceIndex=[STRING])
Description
IS-IS static BFD was not enabled on the interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
InterfaceIndex
Possible Causes
The static BFD function was not enabled on the interface.
Procedure
Step 1 Judge whether the static BFD function needs to be enabled on the interface. If so, go to Step 2;
if not, go to Step 3.
Step 2 Run the isis bfd static command.
Step 3 End.
----End
Issue 07 (2014-07-30)

374

Log Reference
44 ISIS
44.136 ISIS/6/SELF_LSP_EXPIRED
Message
ISIS/6/SELF_LSP_EXPIRED:ISIS [process-id] the LSP generated by local system are expired.
Description
The LSP generated by the local system expired.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The life time of the LSP expired
Procedure
----End
44.137 ISIS/6/ST_LK_CNTRL_FAIL
Message
ISIS/6/ST_LK_CNTRL_FAIL:ISIS [process-id] failed to set link control. (InterfaceIndex=
[STRING])
Description
IS-IS failed to set link control.
Parameters
Parameter Name
Parameter Meaning
[process-id]
InterfaceIndex
Issue 07 (2014-07-30)

375

Log Reference
44 ISIS
Possible Causes
Failed to set link control.
Procedure
Step 1 Check the status of the interface.
----End
44.138 ISIS/4/START_DISABLE_ISIS
Message
ISIS/4/START_DISABLE_ISIS:ISIS [process-id] disabled all ISIS modules.
Description
IS-IS closed all ISIS modules.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The undo isis command was used to disable IS-IS.
Procedure
----End
44.139 ISIS/4/START_ENABLE_ISIS
Message
ISIS/4/START_ENABLE_ISIS:ISIS [process-id] enabled all ISIS modules.
Description
IS-IS started all IS-IS modules.
Issue 07 (2014-07-30)

376

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The isis command was used to enable IS-IS.
Procedure
----End
44.140 ISIS/6/T1TMR_EXPIR_GR_CMD
Message
ISIS/6/T1TMR_EXPIR_GR_CMD:In ISIS [process-id], level-[level] T1 timer expired on
[interface-name] during ISIS GR and RR is set.
Description
The Level-2 T1 timer was stopped on an interface during IS-IS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[level]
Indicates the level of IS-IS.

l 1: level-1
l 2: level-2
[interface-name]
Possible Causes
The Level-2 T1 timer timed out for the second time during IS-IS GR.
Procedure
----End
Issue 07 (2014-07-30)

377

Log Reference
44 ISIS
Message
ISIS/6/T1TMR_LV1_CACEL_GR:ISIS [process-id] cancelled level-1 T1 timer on [interfacename] during ISIS GR.(Counter=[USHORT])
Description
IS-IS cancelled the Level-1 T1 timer on an interface during IS-IS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Counter
Indicates a counter.
Possible Causes
During IS-IS GR, the Level-1 interface received an IIH packet with the RA bit and all series
CSNPs.
Procedure
----End
Message
ISIS/6/T1TMR_LV1_EXPIR_GR:In ISIS [USHORT], level-1 T1 timer expired on [STRING]
during ISIS GR.
Description
The Level-1 T1 timer terminated during the IS-IS GR.
Issue 07 (2014-07-30)

378

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[USHORT]
[STRING]
Possible Causes
Procedure
----End
Message
ISIS/6/T1TMR_LV1_EXPIR_GR_C:In ISIS [process-id], level-1 T1 timer expired on
[interface-name] during ISIS GR.(Counter=[USHORT])
Description
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Counter
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

379

Log Reference
44 ISIS
Message
ISIS/5/T1TMR_LV1_STOP_CMD:ISIS [process-id] stopped level-1 T1 timer on [interfacename] because of restart disable.(Counter=[USHORT])
Description
IS-IS stopped the Level-1 T1 timer on an interface because the restart command was deleted.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Counter
Possible Causes
When canceling restart, ensure that related the Level-1 T1 timer is stopped.
Procedure
----End
Message
ISIS/6/T1TMR_LV2_CACEL_GR:ISIS [process-id] cancelled level-2 T1 timer on [interfacename] during ISIS GR.(Counter=[USHORT])
Description
IS-IS deleted the Level-2 T1 timer on an interface during IS-IS GR.
Issue 07 (2014-07-30)

380

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Counter
Possible Causes
During IS-IS GR, the Level-2 interface received an IIH packet with the RA bit and all series
CSNPs.
Procedure
----End
Message
ISIS/6/T1TMR_LV2_EXPIR_GR:In ISIS [USHORT], level-2 T1 timer expired on [STRING]
during ISIS GR.
Description
Parameters
Parameter Name
Parameter Meaning
[USHORT]
[STRING]
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

381

Log Reference
44 ISIS
Message
ISIS/6/T1TMR_LV2_EXPIR_GR_C:In ISIS [process-id], level-2 T1 timer expired on
[interface-name] during ISIS GR.(Counter=[USHORT])
Description
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Counter
Possible Causes
Procedure
----End
Message
ISIS/5/T1TMR_LV2_STOP_CMD:ISIS [process-id] stopped level-2 T1 timer on [interfacename] because of restart disable.(Counter=[USHORT])
Description
Issue 07 (2014-07-30)

382

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Counter
Possible Causes
When canceling restart, ensure that the related Level-2 T1 timer is stopped.
Procedure
----End
Message
ISIS/6/T2TMR_LV1_CANCL_GR:In ISIS [process-id], level-1 T2 timer cancelled during ISIS
GR.
Description
The Level-1 T2 timer was cancelled during ISIS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the ID of the IS-IS process.
Possible Causes
Level-1 LSDB synchronization was complete during IS-IS GR.
Procedure
----End
Issue 07 (2014-07-30)

383

Log Reference
44 ISIS
Message
ISIS/6/T2TMR_LV1_EXPIR_GR:In ISIS [process-id], level-1 T2 timer expired during ISIS
GR.
Description
The Level-1 T2 timer timed out during ISIS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The Level-1 T2 timer timed out during ISIS GR.
Procedure
----End
Message
ISIS/5/T2TMR_LV1_STOP_CMD:ISIS [process-id] stopped level-1 T2 timer because of
restart disable.
Description
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
When canceling restart, ensure that related the Level-1 T2 timer is stopped.
Issue 07 (2014-07-30)

384

Log Reference
44 ISIS
Procedure
----End
Message
ISIS/6/T2TMR_LV2_CANCL_GR:In ISIS [process-id], level-2 T2 timer cancelled during ISIS
GR.
Description
The Level-2 T2 timer was cancelled during ISIS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
During ISIS GR, Level-2 LSDB synchronization was complete and the Level-2 T2 timer was
cancelled.
Procedure
----End
Message
ISIS/6/T2TMR_LV2_EXPIR_GR:In ISIS [process-id], level-2 T2 timer expired during ISIS
GR.
Description
The Level-2 TB timer timed out during IS-IS GR.
Issue 07 (2014-07-30)

385

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The Level-2 T2 timer timed out during IS-IS GR.
Procedure
----End
Message
ISIS/5/T2TMR_LV2_STOP_CMD:ISIS [process-id] stopped level-2 T2 timer because of
restart disable.
Description
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
When canceling restart, ensure that the related Level-2 T2 timer is stopped.
Procedure
----End
Message
ISIS/6/T2TMR_STAR_L1_GR:T2 timer started on level-1 during ISIS [process-id] GR.
Issue 07 (2014-07-30)

386

Log Reference
44 ISIS
Description
The Level-1 T2 timer was started during IS-IS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
During restart or active/standby switch, ISIS entered GR.
Procedure
----End
Message
ISIS/6/T2TMR_STAR_L2_GR:T2 timer started on level-2 during ISIS [process-id] GR.
Description
The Level-2 T2 timer was started during IS-IS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
During restart or active/standby switchover, IS-IS entered the GR state.
Procedure
----End
44.157 ISIS/6/T3TMR_CANCL_GR
Issue 07 (2014-07-30)

387

Log Reference
44 ISIS
Message
ISIS/6/T3TMR_CANCL_GR:In ISIS [process-id], T3 timer cancelled during ISIS GR.
Description
The T3 timer was cancelled during ISIS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The T3 timer was cancelled during ISIS GR.
Procedure
----End
44.158 ISIS/6/T3TMR_EXPIR_GR
Message
ISIS/6/T3TMR_EXPIR_GR:In ISIS [process-id], T3 timer expired during ISIS GR.
Description
The T3 timer was stopped during ISIS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The T3 timer timed out because IS-IS GR was not complete within a specified period.
Procedure
----End
Issue 07 (2014-07-30)

388

Log Reference
44 ISIS
44.159 ISIS/6/T3TMR_REINT_GR
Message
ISIS/6/T3TMR_REINT_GR:In ISIS [process-id], T3 timer re-initialized to [time] seconds on
[interface-name] during ISIS GR when received Hello package.
Description
During IS-IS GR, the T3 timer was re-initialized after a Hello packet was received on a link.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[time]
Indicates the time.
[interface-name]
Possible Causes
The IIH packet in which the restart TLV has the RA bit was received during IS-IS GR.
Procedure
----End
44.160 ISIS/6/T3TMR_STAR_GR
Message
ISIS/6/T3TMR_STAR_GR:T3 timer started during ISIS [process-id] GR.
Description
The T3 timer was started during IS-IS GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

389

Log Reference
44 ISIS
Possible Causes
Procedure
----End
44.161 ISIS/5/T3TMR_STOP_CMD
Message
ISIS/5/T3TMR_STOP_CMD:ISIS [process-id] stopped T3 timer because of restart disable.
Description
IS-IS stopped the T3 timer on an interface because the restart command was deleted.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
When canceling restart, ensure that the related T3 timer is stopped.
Procedure
----End
44.162 ISIS/6/TMER_STIL_USED
Message
ISIS/6/TMER_STIL_USED:The timer is in use. (TimerType=[ULONG], UsageCount=
[ULONG], IsisProcessId=[USHORT])
Description
The timer was in use.
Issue 07 (2014-07-30)

390

Log Reference
44 ISIS
Parameters
Parameter Name
Parameter Meaning
TimerType
Indicates the type of a timer.
UsageCount
Indicates the number of timers in use.
IsisProcessId
Possible Causes
Internal processing.
Procedure
----End
44.163 ISIS/6/TORM_LEV_GR_DESTR
Message
ISIS/6/TORM_LEV_GR_DESTR:ISIS [USHORT] notifies RM that the process is leaving
restart because process was destroyed.
Description
IS-IS notified the RM that the IS-IS process would exit from the restarting because the process
itself was destroyed.
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Possible Causes
IS-IS notified the RM that the IS-IS process would exit from the restarting because the process
itself was destroyed.
Procedure
----End
Issue 07 (2014-07-30)

391

Log Reference
44 ISIS
44.164 ISIS/6/TORM_LEV_RESTA_SMOH
Message
ISIS/6/TORM_LEV_RESTA_SMOH:ISIS [process-id] notifies RM that the process is leaving
restart in consistency smooth.
Description
IS-IS notified RM that the process was to leave the restart state during the consistency smoothing.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
IS-IS GR was not configured during the HA smoothing.
Procedure
----End
44.165 ISIS/5/TORM_LEV_RESTAR_CMD
Message
ISIS/5/TORM_LEV_RESTAR_CMD:ISIS [process-id] notifies RM that the process is leaving
restart because of restart disable.
Description
IS-IS notified RM that the process was to leave the restart state because the restart command
was deleted.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

392

Log Reference
44 ISIS
Possible Causes
The restart was canceled.
Procedure
----End
44.166 ISIS/5/TORM_LEV_RESTAR_SPF
Message
ISIS/5/TORM_LEV_RESTAR_SPF:ISIS [process-id] notifies RM that the process is leaving
restart after SPF is run.
Description
After the SPF algorithm was used, IS-IS notified RM that the system left the restart state.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
After IS-IS GR and the ISPF calculation were complete, IS-IS notified RM that the system left
the GR state.
Procedure
----End
44.167 ISIS/5/TORM_RNTR_RESTAR_CMD
Message
ISIS/5/TORM_RNTR_RESTAR_CMD:ISIS [process-id] notifies RM that the process is
entering restart because of restart enable.
Issue 07 (2014-07-30)

393

Log Reference
44 ISIS
Description
IS-IS notified RM that the process was to enter the restart state because the restart command
was used.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
44.168 ISIS/6/UNBIND_SOKT_FAIL
Message
ISIS/6/UNBIND_SOKT_FAIL:ISIS [process-id] failed to unbind socket for the circuit
[interface-name]. (InterfaceIndex=[STRING], ReturnValue=[LONG])
Description
IS-IS failed to unbind a socket for an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
InterfaceIndex
ReturnValue
Possible Causes
Failed to unbind a socket for an interface.
Issue 07 (2014-07-30)

394

Log Reference
44 ISIS
Procedure
----End
44.169 ISIS/6/WRONG_VERSION
Message
ISIS/6/WRONG_VERSION:ISIS [process-id] dropped the PDU because the PDU version was
wrong.
Description
ISIS discarded the PDU packet because the PDU version was wrong.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The PDU packet was discarded because the PDU version was wrong.
Procedure
----End
Issue 07 (2014-07-30)

395

Log Reference
45 Keychain
45
Keychain
About This Chapter

45.1 KEYCHAIN/3/CFG_INIT_FLD
45.2 KEYCHAIN/3/CMDSTRS_INIT_FLD
45.3 KEYCHAIN/3/CORE_INIT_FLD
45.4 KEYCHAIN/3/GET_CORE_INTF_FLD
45.5 KEYCHAIN/3/GET_EXT_INTF_FLD
45.6 KEYCHAIN/3/GIVE_CORE_INTF_FLD
45.7 KEYCHAIN/3/HA_INIT_FLD
45.8 KEYCHAIN/6/KEYCH_ALGID_CHNG
45.9 KEYCHAIN/4/KEYCH_ALGID_CNFLCT
45.10 KEYCHAIN/6/KEYCH_APP_REG_FAIL
45.11 KEYCHAIN/6/KEYCH_APP_REG_SUC
45.12 KEYCHAIN/6/KEYCH_APP_UNREG_FAIL
45.13 KEYCHAIN/6/KEYCH_APP_UNREG_SUC
45.14 KEYCHAIN/6/KEYCH_CONFIG
45.15 KEYCHAIN/6/KEYCH_ISSU_LOSLES
45.16 KEYCHAIN/6/KEYCH_ISSU_LSY
45.17 KEYCHAIN/6/KEYCH_KEY_DEFAULT_A
45.18 KEYCHAIN/6/KEYCH_KEY_DEFAULT_I
45.19 KEYCHAIN/6/KEYCH_KEY_STATUS_AA
45.20 KEYCHAIN/6/KEYCH_KEY_STATUS_AI
Issue 07 (2014-07-30)

396

Log Reference
45 Keychain
45.21 KEYCHAIN/6/KEYCH_KEY_STATUS_IA
45.22 KEYCHAIN/6/KEYCH_KEYID_RECV_A
45.23 KEYCHAIN/6/KEYCH_KEYID_RECV_I
45.24 KEYCHAIN/6/KEYCH_KEYID_SEND_A
45.25 KEYCHAIN/6/KEYCH_NO_SEND_KEYID
45.26 KEYCHAIN/6/KEYCH_TCP_KIND_CHNG
45.27 KEYCHAIN/6/KEYCH_TCP_REG_FAIL
45.28 KEYCHAIN/6/KEYCH_TCP_REG_SUC
45.29 KEYCHAIN/6/KEYCH_TCP_UNREG_FAIL
45.30 KEYCHAIN/6/KEYCH_TCP_UNREG_SUC
45.31 KEYCHAIN/6/KEYCH_UNCONFIG
45.32 KEYCHAIN/4/MAX_KEYCHAIN_REACHED
45.33 KEYCHAIN/4/MAX_KEYID_REACHED
45.34 KEYCHAIN/3/PAF_LCS_INIT_FLD
45.35 KEYCHAIN/3/SHELL_INIT_FLD
45.36 KEYCHAIN/3/TWL_CREATE_INST_FLD
Issue 07 (2014-07-30)

397

Log Reference
45 Keychain
45.1 KEYCHAIN/3/CFG_INIT_FLD
Message
KEYCHAIN/3/CFG_INIT_FLD:Failed to initialize configuration.
Description
Failed to initialize with CLI sub-module.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Problem in registering with CFG module.
Procedure
Step 1 Check all the parameters send while registering with CFG module.
----End
45.2 KEYCHAIN/3/CMDSTRS_INIT_FLD
Message
KEYCHAIN/3/CMDSTRS_INIT_FLD:Failed to initialize command strings.
Description
Error in initializing command string.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Number of command strings not same as specified.
Issue 07 (2014-07-30)

398

Log Reference
45 Keychain
Procedure
Step 1 Check whether the number of command string is equal to as specified, if not then debug it.
----End
45.3 KEYCHAIN/3/CORE_INIT_FLD
Message
KEYCHAIN/3/CORE_INIT_FLD:Failed to initialize the core.
Description
Initialization of Core failed.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Error in allocating memory for resources in core at the time of initialization.
Procedure
Step 1 Sufficient memory space should be available.
----End
45.4 KEYCHAIN/3/GET_CORE_INTF_FLD
Message
KEYCHAIN/3/GET_CORE_INTF_FLD:Error in obtaining core interfaces.
Description
Interfaces provided by the core is not obtained properly by the shell.
Parameters
Parameter Name
Parameter Meaning
none
none
Issue 07 (2014-07-30)

399

Log Reference
45 Keychain
Possible Causes
Problem in getting the Vtable.
Procedure
Step 1 Check why problem is occurring in getting the Vtable.
----End
45.5 KEYCHAIN/3/GET_EXT_INTF_FLD
Message
KEYCHAIN/3/GET_EXT_INTF_FLD:Error in obtaining external interfaces.
Description
Shell is not able to get interfaces provided by the external module.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Provided interface/s is/are not correct.
Procedure
Step 1 Look for the interfaces provided by the external module.
Step 2 Check whether the provided interfaces are correct or not.
----End
45.6 KEYCHAIN/3/GIVE_CORE_INTF_FLD
Message
KEYCHAIN/3/GIVE_CORE_INTF_FLD:Failed to provide interfaces for the core.
Description
Shell interfaces are not available to the core.
Issue 07 (2014-07-30)

400

Log Reference
45 Keychain
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Interfaces provided by the shell to core is not correct.
Procedure
Step 1 Check for the different interfaces provided by the core to shell.
----End
45.7 KEYCHAIN/3/HA_INIT_FLD
Message
KEYCHAIN/3/HA_INIT_FLD:Failed to initialize with HA.
Description
Failed to initialize with HA module.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Problem in registering with HA module.
Procedure
Step 1 Check all the parameters send while registering with HA module.
----End
45.8 KEYCHAIN/6/KEYCH_ALGID_CHNG
Message
KEYCHAIN/6/KEYCH_ALGID_CHNG:In keychain [keychain-name], the TCP algorithm ID
is changed to [tcp-algorithm-id] for [algorithm-name] algorithm.
Issue 07 (2014-07-30)

401

Log Reference
45 Keychain
Description
TCP algorithm id is changed for an algorithm type.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
tcp-algorithm-id
TCP algorithm id
algorithm-name
Algorithm name
Possible Causes
Configuration/re-configuration/un-configuration of TCP algorithm id for an algorithm in a
keychain.
Procedure
----End
45.9 KEYCHAIN/4/KEYCH_ALGID_CNFLCT
Message
KEYCHAIN/4/KEYCH_ALGID_CNFLCT:In keychain [keychain-name], the TCP algorithm
ID of [algorithm-name1] conflicts with the TCP algorithm ID of [algorithm-name2].
Description
TCP algorithm id of an algorithm conflicts with the TCP algorithm id of some other algorithm
in a keychain.
Parameters
Parameter Name
Parameter Meaning
[keychain-name]
Keychain name
[algorithm-name1]
Algorithm name
[algorithm-name2]
Algorithm name
Possible Causes
1. When configured TCP algorithm id of an algorithm conflicts with the algorithm id of some
other algorithm in a keychain.
Issue 07 (2014-07-30)

402

Log Reference
45 Keychain
Procedure
Step 1 User should change the TCP algorithm ID such that there is no conflict.
----End
45.10 KEYCHAIN/6/KEYCH_APP_REG_FAIL
Message
KEYCHAIN/6/KEYCH_APP_REG_FAIL:The application with MID [ULONG] and PID
[ULONG] failed to register with keychain because of [STRING].
Description
When an application failed to register with keychain.
Parameters
ULONG
MID
ULONG
PID
STRING
Invalid parameter, application already registered, memory allocation

failure
Possible Causes
1. When an application tries to register with keychain but it is already registered.
2. When an application tries to register with keychain by passing invalid parameter for callback
function.
Procedure
Step 1 Check whether this application is already registered.
Step 2 Check whether the parameter is correct.
----End
45.11 KEYCHAIN/6/KEYCH_APP_REG_SUC
Message
KEYCHAIN/6/KEYCH_APP_REG_SUC:The application with MID [ULONG] and PID
[ULONG] successfully registered with keychain.
Issue 07 (2014-07-30)

403

Log Reference
45 Keychain
Description
When an application successfully registered with keychain.
Parameters
Parameter Name
Parameter Meaning
ULONG
MID
ULONG
PID
Possible Causes
When an application tries to register with keychain.
Procedure
----End
45.12 KEYCHAIN/6/KEYCH_APP_UNREG_FAIL
Message
KEYCHAIN/6/KEYCH_APP_UNREG_FAIL:The application with MID [ULONG] and PID
[ULONG] failed to unregister because of [STRING].
Description
An application failed to unregister from keychain.
Parameters
Parameter Name
Parameter Meaning
ULONG
MID
ULONG
PID
STRING
Application not registered
Possible Causes
When an application failed to unregister from keychain.
Issue 07 (2014-07-30)

404

Log Reference
45 Keychain
Procedure
----End
45.13 KEYCHAIN/6/KEYCH_APP_UNREG_SUC
Message
KEYCHAIN/6/KEYCH_APP_UNREG_SUC:The application with MID [ULONG] and PID
[ULONG] successfully unregistered from keychain.
Description
An application successfully unregistered from keychain.
Parameters
Parameter Name
Parameter Meaning
ULONG
MID
ULONG
PID
Possible Causes
When an application successfully unregistered from keychain.
Procedure
----End
45.14 KEYCHAIN/6/KEYCH_CONFIG
Message
KEYCHAIN/6/KEYCH_CONFIG:Configure Keychain [keychain-name].
Description
A new keychain is configured.
Issue 07 (2014-07-30)

405

Log Reference
45 Keychain
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
Possible Causes
A new keychain is configured.
Procedure
----End
45.15 KEYCHAIN/6/KEYCH_ISSU_LOSLES
Message
KEYCHAIN/6/KEYCH_ISSU_LOSLES:Keychain module upgrade is lossless.
Description
When keychain module specification comparison returns lossless upgradation.
Parameters
Parameter Name
Parameter Meaning
None
none
Possible Causes
During ISSU, ISSU manager calls compare specification function for each module.
Procedure
----End
45.16 KEYCHAIN/6/KEYCH_ISSU_LSY
Message
KEYCHAIN/6/KEYCH_ISSU_LSY:Keychain module upgrade is lossy.
Issue 07 (2014-07-30)

406

Log Reference
45 Keychain
Description
When keychain module specification comparison returns lossy upgradation.
Parameters
Parameter Name
Parameter Meaning
None
none
Possible Causes
During ISSU, ISSU manager calls compare specification function for each module.
Procedure
----End
45.17 KEYCHAIN/6/KEYCH_KEY_DEFAULT_A
Message
KEYCHAIN/6/KEYCH_KEY_DEFAULT_A:In keychain [keychain-name], the status of
default send key-id [key-id] is changed to send active.
Description
Status of default send key-id is changed to active in a keychain.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
key-id
Key-id
Possible Causes
1. When a non-default send key-id becomes inactive and default send key-id becomes active.
2. If a keystring is configured for a default send key-id when no other send key-id is active.
3. If a key-id which has valid key string is configured as default when no other send key-id is
active.
Issue 07 (2014-07-30)

407

Log Reference
45 Keychain
Procedure
----End
45.18 KEYCHAIN/6/KEYCH_KEY_DEFAULT_I
Message
KEYCHAIN/6/KEYCH_KEY_DEFAULT_I:In keychain [keychain-name], the status of
default send key-id [key-id] is changed to send inactive.
Description
Status of default send key-id is changed to inactive in a keychain.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
key-id
Key-id
Possible Causes
1. When a default send key-id is un-configured when it is active.
2. When a keystring is un-configured for default send key-id when it is active.
3. When a key-id is un-configured which is marked as default and is active.
Procedure
----End
45.19 KEYCHAIN/6/KEYCH_KEY_STATUS_AA
Message
KEYCHAIN/6/KEYCH_KEY_STATUS_AA:Keychain [keychain-name] key-id [key-id] info
is changed, the send status is active, and the receive status is active.
Description
Both Send Status and receive status is active for the specified key-id.
Issue 07 (2014-07-30)

408

Log Reference
45 Keychain
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
key-id
Key-id
Possible Causes
Re-configuration of key-string when the key-id is both send and receive active.
Procedure
----End
45.20 KEYCHAIN/6/KEYCH_KEY_STATUS_AI
Message
KEYCHAIN/6/KEYCH_KEY_STATUS_AI:Keychain [keychain-name] key-id [key-id] info
is changed, the send status is active, and the receive status is inactive.
Description
Send Status is active and receive status is inactive for the specified key-id.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
key-id
Key-id
Possible Causes
Re-configuration of key-string when the key-id is send active and receive inactive.
Procedure
----End
Issue 07 (2014-07-30)

409

Log Reference
45 Keychain
45.21 KEYCHAIN/6/KEYCH_KEY_STATUS_IA
Message
KEYCHAIN/6/KEYCH_KEY_STATUS_IA:Keychain [keychain-name] key-id [key-id] info
is changed, the send status is inactive, and the receive status is active.
Description
Send Status is inactive and receive status is active for the specified key-id.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
key-id
Key-id
Possible Causes
Re-configuration of key-string when the key-id is send inactive and receive active.
Procedure
----End
45.22 KEYCHAIN/6/KEYCH_KEYID_RECV_A
Message
KEYCHAIN/6/KEYCH_KEYID_RECV_A:Keychain [keychain-name] key-id [key-id]
became receive active.
Description
A receive key becomes active.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
key-id
Key-id
Issue 07 (2014-07-30)

410

Log Reference
45 Keychain
Possible Causes
Change of clock occurred or receive time window for the key-id commences.
Procedure
----End
45.23 KEYCHAIN/6/KEYCH_KEYID_RECV_I
Message
KEYCHAIN/6/KEYCH_KEYID_RECV_I:Keychain [keychain-name] key-id [key-id] became
receive inactive.
Description
A receive key becomes inactive.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
key-id
Key-id
Possible Causes
Change of clock occurred or receive time window for the key-id expired.
Procedure
----End
45.24 KEYCHAIN/6/KEYCH_KEYID_SEND_A
Message
KEYCHAIN/6/KEYCH_KEYID_SEND_A:Keychain [keychain-name] key-id [key-id]
became send active.
Description
A send key becomes active.
Issue 07 (2014-07-30)

411

Log Reference
45 Keychain
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
key-id
Key-id
Possible Causes
Change of clock occurred or send time window for any of the key-id present in the keychain is
active.
Procedure
----End
45.25 KEYCHAIN/6/KEYCH_NO_SEND_KEYID
Message
KEYCHAIN/6/KEYCH_NO_SEND_KEYID:Keychain [keychain-name] has no active send
key.
Description
Specified keychain does not contains any active send key.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
Possible Causes
Change of clock occurred or send time window for any of the key-id present in the keychain is
not active.
Procedure
Step 1 This event notifies no active send key-id is present in the particular keychain.
Step 2 User should not use this key-id further for encoding packets till it's status remains in-active.
----End
Issue 07 (2014-07-30)

412

Log Reference
45 Keychain
45.26 KEYCHAIN/6/KEYCH_TCP_KIND_CHNG
Message
KEYCHAIN/6/KEYCH_TCP_KIND_CHNG:In keychain [keychain-name], the TCP kind
value is changed to [tcp-kind-value].
Description
TCP Kind value is changed.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
tcp-kind-value
TCP-kind value
Possible Causes
Configuration/re-configuration/un-configuration of TCP kind value in a keychain.
Procedure
----End
45.27 KEYCHAIN/6/KEYCH_TCP_REG_FAIL
Message
KEYCHAIN/6/KEYCH_TCP_REG_FAIL:[STRING] failed to register with keychain because
the application had already registered.
Description
When TCP application failed to register with keychain because the application had already
registered.
Parameters
Parameter Name
Parameter Meaning
STRING
TCP Version
Issue 07 (2014-07-30)

413

Log Reference
45 Keychain
Possible Causes
When TCP application tries to register with keychain when it is already registered.
Procedure
----End
45.28 KEYCHAIN/6/KEYCH_TCP_REG_SUC
Message
KEYCHAIN/6/KEYCH_TCP_REG_SUC:[STRING] successfully registered with keychain.
Description
When TCP4/TCP6 application successfully registered with keychain.
Parameters
Parameter Name
Parameter Meaning
STRING
TCP Version
Possible Causes
When TCP tries to register with Keychain.
Procedure
----End
45.29 KEYCHAIN/6/KEYCH_TCP_UNREG_FAIL
Message
KEYCHAIN/6/KEYCH_TCP_UNREG_FAIL:[STRING] failed to unregister from keychain
because the application had not registered.
Description
When TCP application failed to unregister from keychain because the application had not
registered.
Issue 07 (2014-07-30)

414

Log Reference
45 Keychain
Parameters
Parameter Name
Parameter Meaning
STRING
TCP Version
Possible Causes
When TCP application tries to unregister from keychain when it is not registered.
Procedure
----End
45.30 KEYCHAIN/6/KEYCH_TCP_UNREG_SUC
Message
KEYCHAIN/6/KEYCH_TCP_UNREG_SUC:[STRING] successfully unregistered from
keychain.
Description
When TCP4/TCP6 application successfully unregistered from keychain.
Parameters
Parameter Name
Parameter Meaning
STRING
TCP Version
Possible Causes
When TCP tries to unregister from keychain.
Procedure
----End
45.31 KEYCHAIN/6/KEYCH_UNCONFIG
Message
KEYCHAIN/6/KEYCH_UNCONFIG:Unconfigure Keychain [keychain-name].
Issue 07 (2014-07-30)

415

Log Reference
45 Keychain
Description
An existing keychain is un-configured.
Parameters
Parameter Name
Parameter Meaning
keychain-name
Keychain name
Possible Causes
An existing keychain is un-configured.
Procedure
----End
45.32 KEYCHAIN/4/MAX_KEYCHAIN_REACHED
Message
KEYCHAIN/4/MAX_KEYCHAIN_REACHED:Maximum number of keychains already
configured.
Description
Maximum number of allowable keychain configuration, according to PAF already configured.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Maximum keychain configured.
Procedure
Step 1 User should not try to configure more keychains as the maximum limit is already achieved.
----End
Issue 07 (2014-07-30)

416

Log Reference
45 Keychain
45.33 KEYCHAIN/4/MAX_KEYID_REACHED
Message
KEYCHAIN/4/MAX_KEYID_REACHED:Maximum number of key-ids already configured.
Description
Maximum number of allowable key-id configuration in a keychain, according to PAF already
configured.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Maximum key-id in a keychain configured.
Procedure
Step 1 User should not try to configure more key-id's within the particular keychain as the maximum
limit is already achieved.
----End
45.34 KEYCHAIN/3/PAF_LCS_INIT_FLD
Message
KEYCHAIN/3/PAF_LCS_INIT_FLD:Error in initializing PAF/License values.
Description
Values from PAF cannot be read because of some error.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Data is not in the proper format in PAF.
Issue 07 (2014-07-30)

417

Log Reference
45 Keychain
Procedure
Step 1 Look for the data provided in PAF is correct or not.
Step 2 If incorrect, then change the format.
----End
45.35 KEYCHAIN/3/SHELL_INIT_FLD
Message
KEYCHAIN/3/SHELL_INIT_FLD:Error in shell initialization.
Description
Shell cannot be initialized properly because of some errors.
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Failure for initialization of command strings/registration for HA Callback with HA module/
providing interfaces to the core/initialization of configuration.
Procedure
Step 1 Look whether the following initialization, registration and check are proper or not:
l Initialization of command strings
l Registration for HA Callback with HA module
l Providing interfaces to the core
l Initialization of configuration
l Number of waitlists implemented in core is within permissible limits
----End
45.36 KEYCHAIN/3/TWL_CREATE_INST_FLD
Message
KEYCHAIN/3/TWL_CREATE_INST_FLD:Failed to create instances with Timer wheel.
Issue 07 (2014-07-30)

418

Log Reference
45 Keychain
Description
Creation of Timer-Wheel is failed
Parameters
Parameter Name
Parameter Meaning
none
none
Possible Causes
Parameters passed for instantiating a timer wheel are not proper.
Procedure
Step 1 Check all the parameters send while instantiating a timer wheel.
----End
Issue 07 (2014-07-30)

419

Log Reference
46 L2IF
46
L2IF
About This Chapter

46.1 L2IF/6/FULLRULE
46.2 L2IF/6/PORT_DOWN
46.3 L2IF/6/PORT_UP
46.4 L2IF/6/ROUTER_TO_SWITCH
46.5 L2IF/6/SLA_RCV_INDEX_BY_BAT
46.6 L2IF/6/SLA_RCV_PORTINDEX
46.7 L2IF/6/SWITCH_TO_ROUTER
Issue 07 (2014-07-30)

420

Log Reference
46 L2IF
46.1 L2IF/6/FULLRULE
Message
L2IF/6/FULLRULE:New entries cannot take effect when the number of the active mac-limit
entries has reached the upper limit.
Description
The number of the limited MAC entries reached the maximum.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The number of the limited MAC entries reached the maximum.
Procedure
Step 1 Check MAC limit rules:
l If the rules are configured based on either an Ethernet interface or a VLAN:
1.
Run the undo mac-limit command in the current interface or VLAN view to delete
unneeded rules.
2.
Run the mac-limit { action { discard | forward } | alarm { disable | enable }

maximum max rate interval }* command in the current interface or VLAN view to add
rules based on the Ethernet interface or the VLAN.
l If the rules are configured based on both an interface and a VLAN:

1.
Run the undo mac-limit vlan vlan-id1 [ to vlan-id2 ] command in the current interface
view to delete unneeded rules.
2.
Run the mac-limit vlan vlan-id1 [ to vlan-id2 ] { action { discard | forward } |

alarm { disable | enable } maximum max rate interval }* command in the current
interface view to add rules based on both the interface and the VLAN.
----End
46.2 L2IF/6/PORT_DOWN
Message
L2IF/6/PORT_DOWN:The status of port [port-name] turns DOWN.
Issue 07 (2014-07-30)

421

Log Reference
46 L2IF
Description
The status of the port [port-name] was switched to Down.
Parameters
Parameter Name
Parameter Meaning
[port-name]
indicates the name of a Layer 2 port.
Possible Causes
The status of the port [port-name] changed.
Procedure
----End
46.3 L2IF/6/PORT_UP
Message
L2IF/6/PORT_UP:The status of port [port-name] turns UP.
Description
The status of the port [port-name] was switched to Up.
Parameters
Parameter Name
Parameter Meaning
[port-name]
Possible Causes
The status of the port [port-name] changed.
Procedure
----End
46.4 L2IF/6/ROUTER_TO_SWITCH
Issue 07 (2014-07-30)

422

Log Reference
46 L2IF
Message
L2IF/6/ROUTER_TO_SWITCH:Start to switch port [port-name] from L3 mode to L2 mode.
Description
The Layer 3 port [port-name] was switched to a Layer 2 port.
Parameters
Parameter Name
Parameter Meaning
[port-name]
Possible Causes
Procedure
----End
46.5 L2IF/6/SLA_RCV_INDEX_BY_BAT
Message
L2IF/6/SLA_RCV_INDEX_BY_BAT:The slave control board obtains the L2 port index from
the main control board through batch backup. The port name is [port-name].
Description
The slave board obtained the index of the Layer 2 port [port-name] from the main control board
through batch backup.
Parameters
Parameter Name
Parameter Meaning
[port-name]
Possible Causes
The slave board allocated the index backed up in batches from the main control board to the
Layer 2 port.
Issue 07 (2014-07-30)

423

Log Reference
46 L2IF
Procedure
----End
46.6 L2IF/6/SLA_RCV_PORTINDEX
Message
L2IF/6/SLA_RCV_PORTINDEX:The slave control board obtains the L2 port index from the
main control board through realtime backup. The port name is [port-name].
Description
The slave board obtained the index of the Layer 2 port [port-name] from the main board through
real-time backup.
Parameters
Parameter Name
Parameter Meaning
[port-name]
Possible Causes
The slave board backed up the index of the specified Layer 2 port.
Procedure
----End
46.7 L2IF/6/SWITCH_TO_ROUTER
Message
L2IF/6/SWITCH_TO_ROUTER:Start to switch port [port-name] from L2 mode to L3 mode.
Description
Issue 07 (2014-07-30)

424

Log Reference
46 L2IF
Parameters
Parameter Name
Parameter Meaning
[port-name]
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

425

Log Reference
47 L2IFPPI
47
L2IFPPI
About This Chapter

47.1 L2IFPPI/3/MAC_CFG_ERROR
Issue 07 (2014-07-30)

426

Log Reference
47 L2IFPPI
47.1 L2IFPPI/3/MAC_CFG_ERROR
Message
L2IFPPI/3/MAC_CFG_ERROR:"The system MAC address [STRING] has been configured as
a static or blackhole MAC address."
Description
The system MAC address is configured as a static or blackhole MAC address.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the system MAC address.
Possible Causes
In a stack, if the system MAC address of the standby switch is configured as a static or blackhole
MAC address, when an active/standby switchover occurs, the system MAC address is the same
as the configured static or blackhole MAC address.
Procedure
Step 1 Run the undo mac-address command to delete the static or blackhole MAC address.
----End
Issue 07 (2014-07-30)

427

Log Reference
48 L2V
48
L2V
About This Chapter

48.1 L2V/5/BFD_FOR_PW_DOWN
48.2 L2V/5/BFD_FOR_PW_UP
48.3 L2V/3/BGPRMTCEIDLOCIDSAME
48.4 L2V/5/BGPVC_DWN
48.5 L2V/5/BGPVC_P2W
48.6 L2V/5/BGPVC_UP
48.7 L2V/5/BGPVC_W2P
48.8 L2V/3/CEOUTOFRANGE
48.9 L2V/3/CONFLICTCONN
48.10 L2V/4/ISSU_CHK_FL
48.11 L2V/3/LDP_MSG_ERR
48.12 L2V/3/OTHERCEIDSAME
48.13 L2V/3/PAFLCSERR
48.14 L2V/5/PWE3VC_BACKUP
48.15 L2V/5/PWE3VC_DWN_ME
48.16 L2V/5/PWE3VC_P2W
48.17 L2V/5/PWE3VC_UP_ME
48.18 L2V/5/PWE3VC_W2P
48.19 L2V/3/PWLOOPDETECT
48.20 L2V/5/SVC_DWN
Issue 07 (2014-07-30)

428

Log Reference
48 L2V
48.21 L2V/5/SVC_UP
48.22 L2V/5/VPLSVC_BACKUP
48.23 L2V/5/VPLSVC_DWN_ME
48.24 L2V/5/VPLSVC_UP_ME
48.25 L2V/5/VPLSVSI_DWN
48.26 L2V/5/VPLSVSI_UP
48.27 L2V/5/VSICALINLBLERR
48.28 L2V/5/VSIMHMPREFSAME
48.29 L2V/5/VSIRMTLCLIDSAME
48.30 L2V/5/VSISITEOUTOFRANGE
Issue 07 (2014-07-30)

429

Log Reference
48 L2V
48.1 L2V/5/BFD_FOR_PW_DOWN
Message
L2V/5/BFD_FOR_PW_DOWN:The status of BFD for PW turned DOWN. (VcId=[ULONG],
VcType=[STRING])
Description
The status of BFD for PW became Down.
Parameters
Parameter Name
Parameter Meaning
VcId
Indicates the ID of the VC.
VcType
Indicates the type of the VC.
Possible Causes
BFD detected that the link was not available and notified the L2VPN module that the link of the
current PW was Down.
Procedure
----End
48.2 L2V/5/BFD_FOR_PW_UP
Message
L2V/5/BFD_FOR_PW_UP:The status of BFD for PW turned UP. (VcId=[ULONG], VcType=
[STRING])
Description
The status of BFD for PW became Up.
Parameters
Parameter Name
Parameter Meaning
VcId
Issue 07 (2014-07-30)

430

Log Reference
48 L2V
Parameter Name
Parameter Meaning
VcType
Possible Causes
BFD detected that the link was available and notified the L2VPN module that the link of the
current PW went Up.
Procedure
----End
48.3 L2V/3/BGPRMTCEIDLOCIDSAME
Message
L2V/3/BGPRMTCEIDLOCIDSAME:Remote CE ID is the same with local CE ID. (CeId=
[ULONG], Pe=[STRING], Rd=[STRING])
Description
The remote CE ID was the same as the local CE ID.
Parameters
Parameter Name
Parameter Meaning
CeId
Indicates the CE ID.
Pe
Indicates the IP address of the remote PE.
Rd
Indicates the remote Route Distinguisher (RD).
Possible Causes
The remote CE ID and the local CE ID were the same.
Procedure
Step 1 Change the ID of either the remote CE or the local CE.
----End
48.4 L2V/5/BGPVC_DWN
Issue 07 (2014-07-30)

431

Log Reference
48 L2V
Message
L2V/5/BGPVC_DWN:The status of the Kompella VC turned DOWN. (VcVpnName=
[STRING], CeId=[ULONG], RemoteCeId=[ULONG], InterfaceName=[STRING],
SecondaryVc=[STRING], Reason=[STRING])
Description
This log message explained why the Kompella VC went Down.
Parameters
VcVpnName
Indicates the name of the Virtual Private Network (VPN).
CeId
Indicates the ID of the Customer Edge (CE).
RemoteCeId
Indicates the ID of the remote CE.
InterfaceName
SecondaryVc
Indicates the secondary VC.
Issue 07 (2014-07-30)

432

Log Reference
48 L2V

Reason
Indicates the cause, including

1 Invalid reason type
2 VC was created
3 VC was deleted
4 LDP session was Down
5 LDP session was Up
6 Same LDP mapping was received with different label and MTU
7 Same LDP mapping was received with matching interface parameters
8 LDP mapping was received with mismatching interface parameters
9 LDP mapping was received with unpass Cbit check
10 LDP mapping was received with unpass PW loop check
11 New LDP mapping was received
12 New LDP mapping was received but remote Vc or local Vc is Down
13 LDP withdrawn message was received
14 LDP release message was received
15 LDP request message was received
16 LDP GR ended processing
17 RSVP message was received
18 Interface was Up
19 Interface was Down
20 Interface encapsulation changed
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
25 VC state changed when New RLB was received
26 RLB was Deleted
27 VC was created or connected to another remote CE
28 Outgoing interface was unavailable
29 Outgoing interface was available
30 LDP notification message was forwarded
Issue 07 (2014-07-30)

433

Log Reference
48 L2V

31 LDP notification message was not forwarded
32 PW was recreated
33 Download FTN & ILM for EthernetTrunk
34 AC OAM fault detection was disabled
35 Remote AC fault
36 Remote AC fault was resumed
37 Local AC fault
38 Local AC fault was resumed
39 Remote PSN fault
40 Remote PSN fault was resumed
41 Local PSN fault
42 Local PSN fault was resumed
43 Bfd for pw status changed toDown
44 Bfd for pw status changed to UP
45 Bfd for pw status changed to ADMIN DOWN
46 Bfd for pw was disabled
47 Manual set was enabled
48 Manual set was disabled
49 Delay timed out
50 Resume Timed Out
Possible Causes
The VC went Down.
Procedure
Step 1 Identify the cause of the VC status change.
----End
48.5 L2V/5/BGPVC_P2W
Issue 07 (2014-07-30)

434

Log Reference
48 L2V
Message
L2V/5/BGPVC_P2W:The status of the Kompella VC turned working from protecting.
(VcVpnName=[STRING], CeId=[ULONG], RemoteCeId=[ULONG], InterfaceName=
[STRING], PrimaryVcRemoteCeId=[ULONG], Reason=[STRING])
Description
This log message explained why the Kompella VC changed from a protection link to a working
link.
Parameters
Parameter Name
Parameter Meaning
VcVpnName
CeId
RemoteCeId
InterfaceName
PrimaryVcRemoteCeId Indicates the secondary VC.
Issue 07 (2014-07-30)

435

Log Reference
48 L2V
Parameter Name
Parameter Meaning
Reason

2 VC was created
3 VC was deleted
7 Same LDP mapping was received with matching interface
parameters
12 New LDP mapping was received but remote Vc or local Vc is
Down
18 Interface was Up
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
26 RLB was Deleted
Issue 07 (2014-07-30)

436

Log Reference
Parameter Name
48 L2V
Parameter Meaning
32 PW was recreated
35 Remote AC fault
37 Local AC fault
39 Remote PSN fault
41 Local PSN fault
43 Bfd for pw status changed to Down
49 Delay timed out
50 Resume Timed Out
Possible Causes
The VC changed from a protection link to a working link.
Procedure
Step 1 Identify the cause of the switchover between the primary VC and the secondary VC according
to the recorded reason.
----End
Issue 07 (2014-07-30)

437

Log Reference
48 L2V
48.6 L2V/5/BGPVC_UP
Message
L2V/5/BGPVC_UP:The status of the Kompella VC turned UP. (VcVpnName=[STRING],
CeId=[ULONG], RemoteCeId=[ULONG], InterfaceName=[STRING], SecondaryVc=
[STRING], Reason=[STRING])
Description
This log message explained why the Kompella VC went Up.
Parameters
VcVpnName
CeId
RemoteCeId
InterfaceName
SecondaryVc
Indicates the secondary VC.
Issue 07 (2014-07-30)

438

Log Reference
48 L2V

Reason

2 VC was created
3 VC was deleted
18 Interface was Up
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
26 RLB was Deleted
Issue 07 (2014-07-30)

439

Log Reference
48 L2V

32 PW was recreated
35 Remote AC fault
37 Local AC fault
39 Remote PSN fault
41 Local PSN fault
49 Delay timed out
50 Resume Timed Out
Possible Causes
The VC went Up.
Procedure
----End
48.7 L2V/5/BGPVC_W2P
Issue 07 (2014-07-30)

440

Log Reference
48 L2V
Message
L2V/5/BGPVC_W2P:The status of the Kompella VC turned protecting from working.
(VcVpnName=[STRING], CeId=[ULONG], RemoteCeId=[ULONG], InterfaceName=
[STRING], SecondaryVcRemoteCeId=[ULONG], Reason=[STRING])
Description
This log message explained why the Kompella VC changed from a working link to a protection
link.
Parameters
Parameter Name
Parameter Meaning
VcVpnName
CeId
RemoteCeId
InterfaceName
SecondaryVcRemoteCeId Indicates the secondary VC.
Issue 07 (2014-07-30)

441

Log Reference
48 L2V
Parameter Name
Parameter Meaning
Reason

2 VC was created
3 VC was deleted
7 Same LDP mapping was received with matching interface
parameters
8 LDP mapping was received with mismatching interface
parameters
12 New LDP mapping was received but remote Vc or local Vc is
Down
18 Interface was Up
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
26 RLB was Deleted
Issue 07 (2014-07-30)

442

Log Reference
Parameter Name
48 L2V
Parameter Meaning
32 PW was recreated
35 Remote AC fault
37 Local AC fault
39 Remote PSN fault
41 Local PSN fault
49 Delay timed out
50 Resume Timed Out
Possible Causes
The VC changed from a working link to a protection link.
Procedure
Step 1 Identify the cause of the switchover between the primary VC and the secondary VC according
to the recorded reason.
----End
Issue 07 (2014-07-30)

443

Log Reference
48 L2V
48.8 L2V/3/CEOUTOFRANGE
Message
L2V/3/CEOUTOFRANGE: The local CE cannot communicate with the remote CE because the
CE ID exceeds the range. (Local: CeId=[ULONG], VpnRd=[STRING]; Remote: CeId=
[ULONG], Pe=[STRING], VpnRd=[STRING])
Description
The local CE cannot communicate with the remote CE because the CE ID exceeds the range.
Parameters
Parameter Name
Parameter Meaning
Local:
Indicates the local decvice.
CeId
Indicates the local CE ID.
VpnRd
Indicates the local vpn Route Distinguisher (RD).
Remote:
Indicates the remote device.
CeId
Indicates the remote CE ID.
Pe
VpnRd
Indicates the remote vpn Route Distinguisher (RD).
Possible Causes
When the Kompella VLL is configured, the ID of the local CE was beyond the range on the
remote CE.
Procedure
Step 1 Change the ID of the local CE to be smaller one or extend the range on the remote CE.
----End
48.9 L2V/3/CONFLICTCONN
Message
L2V/3/CONFLICTCONN:There are conflicting connections which have the same VC ID and
VC type!
Issue 07 (2014-07-30)

444

Log Reference
48 L2V
Description
The same VC ID and VC type led to connection conflict.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Conflicted connections with the same VC ID and VC type existed.
Procedure
Step 1 Check the configurations and ensure each connection is configured with a unique VC ID and
VC type.
----End
48.10 L2V/4/ISSU_CHK_FL
Message
L2V/4/ISSU_CHK_FL:ISSU Check failed. (Reason=[STRING])
Description
The ISSU check on the L2VPN module failed because of problems in compatibility,
specifications, and configurations.
Issue 07 (2014-07-30)

445

Log Reference
48 L2V
Parameters
Reason
Indicates possible causes:

l starting the ISSU check failed: indicates that the ISSU check cannot
be performed.
l compatibility failed: indicates that the compatibility check failed.
l getting spec data failed: indicates that specification data cannot be
obtained.
l data did not contain specs: indicates that there were no specifications
in the data.
l specs were inconsistent: indicates that specifications in earlier and
later versions were inconsistent.
l config was greater than the new spec: indicates that the configured
value was greater than the value specified in the new specification.
l new spec did not exist: indicates that the new specification did not
exist.
Possible Causes
After the ISSU check was performed to check the version, specifications, and configurations of
the L2VPN module, lossless ISSU cannot be performed on the L2VPN module.
Procedure
l
Perform lossy ISSU on the L2VPN module.
----End
48.11 L2V/3/LDP_MSG_ERR
Message
L2V/3/LDP_MSG_ERR:Received an error or unknown signal message. (MessageType=
[STRING], PeerIpAddress=[STRING], ErrorReason=[STRING])
Description
Received an error or unknown signal message.
Parameters
Parameter Name
Parameter Meaning
MessageType
Indicates the type of message.
Issue 07 (2014-07-30)

446

Log Reference
48 L2V
Parameter Name
Parameter Meaning
PeerIpAddress
Indicates the remote ip address.
ErrorReason
Indicates the reason of the error.
Possible Causes
The received L2VPN LDP signaling packets had an error or unknown field. The remote device
might be a non-Huawei device.
Procedure
Step 1 Check whether the signaling packet sent from the remote device complies with the RFC.
----End
48.12 L2V/3/OTHERCEIDSAME
Message
L2V/3/OTHERCEIDSAME:When inserting RLB into VPN, found the same remote CE ID RLB
already existed. (CeId=[ULONG], Old Rlb: Pe=[STRING], Rd=[STRING]; New Rlb: Pe=
[STRING], Rd=[STRING])
Description
An RLB with the same remote CE ID already existed when the RLB was inserted into VPN.
Parameters
Parameter Name
Parameter Meaning
CeId
Indicates the ID of the CE.
Old Rlb: Pe
Indicates the IP address of the PE in the original RLB.
Rd
Indicates the route distinguisher of the original label block.
New Rlb: Pe
Indicates the IP address of the PE in the new RLB.
Rd
Indicates the route distinguisher of the new label block.
Possible Causes
The local site ID was the same as the remote site ID.
Procedure
Step 1 Re-configure the two site IDs.
----End
Issue 07 (2014-07-30)

447

Log Reference
48 L2V
48.13 L2V/3/PAFLCSERR
Message
L2V/3/PAFLCSERR:PAF LCS inconsistency: avail value exceeded max! (Item=[STRING],
AvailValue=[ULONG], MaxValue=[ULONG])
Description
The actual value exceeded the maximum value defined in the PAF license file.
Parameters
Parameter Name
Parameter Meaning
Item
Indicate the name of the item.
AvailValue
Indicates the available number.
MaxValue
Indicates the maximum number.
Possible Causes
The available value of the PAF License exceeded the maximum value.
Procedure
Step 1 Change the available value and the maximum value of the PAF License to make them consistent.
----End
48.14 L2V/5/PWE3VC_BACKUP
Message
L2V/5/PWE3VC_BACKUP:The status of the PWE3 VC turned BACKUP. (VcId=[ULONG],
VcType=[string], InterfaceName=[string], SecondaryPw=[string], Reason=[string],
SysUpTime=[TIMETICK])
Description
The PWE3 VC turned to the backup state.
Issue 07 (2014-07-30)

448

Log Reference
48 L2V
Parameters
VcId
VcType
InterfaceName
SecondaryPw
Indicates the secondary PW.
Reason
Indicates the cause of VC status change:

The bound VRRP backup group entered the non-master state.
The bound VRRP backup group entered the backup state.
The interface board bound to the VRRP backup group was pulled out.
SysUpTime
Indicates the startup time of the system.
Possible Causes
The cause of a VC status change can be one of the following: the bound VRRP backup group
entered the non-master state; the bound VRRP backup group entered the backup state; the
interface board bound to the VRRP backup group was pulled out.
Procedure
----End
48.15 L2V/5/PWE3VC_DWN_ME
Message
L2V/5/PWE3VC_DWN_ME:The status of the PWE3 VC turned DOWN. (VcId=[ULONG],
VcType=[STRING], InterfaceName=[STRING], SecondaryPw=[STRING], Reason=
[STRING], SysUpTime=[TIMETICK])
Description
This log message explained why the PWE3 VC went Down.
Parameters
VcId
Issue 07 (2014-07-30)
Indicates the VC ID.

449

Log Reference
48 L2V

VcType
Indicates the VC type:

0. unsupport
2. atm aal5 adu
3. atm trans cell
4. vlan
5. ethernet
6. hdlc
7. ppp
8. cem
9. atm nto1 vcc
10. atm nto1 vpc
11. ip layer2
12. atm 1to1 vcc
13. atm 1to1 vpc
14. atm aal5 pdu
15. mpls
16. vpls
17. interworking
18. vlan if
19. unsuppprt
InterfaceName
SecondaryPw
Issue 07 (2014-07-30)

450

Log Reference
48 L2V

Reason
Indicates the cause:

1. Invalid reason type
2. VC was created
3. VC was deleted
4. LDP session was Down
5. LDP session was Up
6. Same LDP mapping was received with different label and MTU
7. Same LDP mapping was received with matching interface parameters
8. LDP mapping was received with mismatching interface parameters
9. LDP mapping was received with unpass Cbit check
10. LDP mapping was received with unpass PW loop check
11. New LDP mapping was received
12. New LDP mapping was received but remote Vc or local Vc is Down
13. LDP withdrawn message was received
14. LDP release message was received
15. LDP request message was received
16. LDP GR ended processing
17. RSVP message was received
18. Interface was Up
19. Interface was Down
20. Interface encapsulation changed
21. Refresh
22. Download again
23. Tunnel was Up
24. Tunnel was Down
25. VC state changed when New RLB was received
26. RLB was Deleted
27. VC was created or connected to another remote CE
28. Outgoing interface was unavailable
29. Outgoing interface was available
30. LDP notification message was forwarded
Issue 07 (2014-07-30)

451

Log Reference
48 L2V

31. LDP notification message was not forwarded
32. PW was recreated
33. Download FTN & ILM for Eth-Trunk
34. AC OAM fault detection was disabled
35. Remote AC fault
36. Remote AC fault was resumed
37. Local AC fault
38. Local AC fault was resumed
39. Remote PSN fault
40. Remote PSN fault was resumed
41. Local PSN fault
42. Local PSN fault was resumed
43. BFD for PW status changed to Down
44. BFD for PW status changed to UP
45. BFD for PW status changed to ADMIN DOWN
46. BFD for PW was disabled
47. Manual set was enabled
48. Manual set was disabled
49. Delay timed out
50. Resume timed out
Indicates the Tick time for the system being Up.
SysUpTime
Possible Causes
The VC went Down.
Procedure
----End
48.16 L2V/5/PWE3VC_P2W
Issue 07 (2014-07-30)

452

Log Reference
48 L2V
Message
L2V/5/PWE3VC_P2W:The status of the PWE3 VC turned working from protecting. (VcId=
[ULONG], VcType=[STRING], PrimaryPwId=[ULONG], Reason=[STRING])
Description
This log message explained why the PWE3 VC changed from a protection link to a working
link.
Parameters
VcId
VcType

0. unsupport
2. atm aal5 adu
3. atm trans cell
4. vlan
5. ethernet
6. hdlc
7. ppp
8. cem
9. atm nto1 vcc
10. atm nto1 vpc
11. ip layer2
12. atm 1to1 vcc
13. atm 1to1 vpc
14. atm aal5 pdu
15. mpls
16. vpls
17. interworking
18. vlan if
19. unsuppprt
PrimaryPwId
Issue 07 (2014-07-30)
Indicates the VC ID of the primary PW.

453

Log Reference
48 L2V

Reason

2. VC was created
3. VC was deleted
21. Refresh
22. Download again
23. Tunnel was Up
24. Tunnel was Down
26. RLB was Deleted
Issue 07 (2014-07-30)

454

Log Reference
48 L2V

35. Remote AC fault
37. Local AC fault
41. Local PSN fault
44. BFD for PW status changed to UP
49. Delay timed out
Possible Causes
The service was switched from the secondary PW to the primary PW.
Procedure
----End
48.17 L2V/5/PWE3VC_UP_ME
Issue 07 (2014-07-30)

455

Log Reference
48 L2V
Message
L2V/5/PWE3VC_UP_ME:The status of the PWE3 VC turned UP. (VcId=[ULONG], VcType=
[STRING], InterfaceName=[STRING], SecondaryPw=[STRING], Reason=[STRING],
SysUpTime=[TIMETICK])
Description
The PWE3 VC goes Up.
Parameters
VcId
VcType
Indicates the type of a VC, which can be any of the following:

0. unsupport
2. atm aal5 adu
3. atm trans cell
4. vlan
5. ethernet
6. hdlc
7. ppp
8. cem
9. atm nto1 vcc
10. atm nto1 vpc
11. ip layer2
12. atm 1to1 vcc
13. atm 1to1 vpc
14. atm aal5 pdu
15. pls
16. vpls
17. interworking
18. vlan if
19. unsuppport
InterfaceName
SecondaryPw
Issue 07 (2014-07-30)

456

Log Reference
48 L2V

Reason
Indicates the reason why the log is generated, which can be any of the
following:
2 VC was created
3 VC was deleted
18 Interface was Up
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
26 RLB was Deleted
Issue 07 (2014-07-30)

457

Log Reference
48 L2V

32 PW was recreated
35 Remote AC fault
37 Local AC fault
39 Remote PSN fault
41 Local PSN fault
49 Delay timed out
50 Resume Timed Out
SysUpTime
Possible Causes
The VC went Up.
Procedure
Step 1 Identify the reason for the VC status change.
----End
48.18 L2V/5/PWE3VC_W2P
Issue 07 (2014-07-30)

458

Log Reference
48 L2V
Message
L2V/5/PWE3VC_W2P:The status of the PWE3 VC turned protecting from working. (VcId=
[ULONG], VcType=[STRING], SecondaryPwId=[ULONG], Reason=[STRING])
Description
This log message explained why the PWE3 VC changed from a working link to a protection
link.
Parameters
VcId
VcType

0. unsupport
2. atm aal5 adu
3. atm trans cell
4. vlan
5. ethernet
6. hdlc
7. ppp
8. cem
9. atm nto1 vcc
10. atm nto1 vpc
11. ip layer2
12. atm 1to1 vcc
13. atm 1to1 vpc
14. atm aal5 pdu
15. mpls
16. vpls
17. interworking
18. vlan if
19. unsuppprt
SecondaryPwId
Issue 07 (2014-07-30)
Indicates the remote VC ID of the secondary PW.

459

Log Reference
48 L2V

Reason

2. VC was created
3. VC was deleted
21. Refresh
22. Download again
23. Tunnel was Up
24. Tunnel was Down
26. RLB was Deleted
Issue 07 (2014-07-30)

460

Log Reference
48 L2V

33. Download FTN & ILM for EthernetTrunk
35. Remote AC fault
37. Local AC fault
41. Local PSN fault
44. BFD for PW status changed to Up
49. Delay timed out
Possible Causes
Services were switched from the primary PW to the secondary PW.
Procedure
----End
48.19 L2V/3/PWLOOPDETECT
Issue 07 (2014-07-30)

461

Log Reference
48 L2V
Message
L2V/3/PWLOOPDETECT:A PW loop is detected. (VcId=[ULONG], VcType=[STRING],
LoopIpAddress=[STRING])
Description
A PW loop was detected.
Parameters
Parameter Name
Parameter Meaning
VcId
VcType
Indicates the type of VC.
LoopIpAddress
Indicates the ip address that causes the loop.
Possible Causes
PW links formed a loop.
Procedure
Step 1 Adjust the configuration on the device based on VcId, VcType, and LoopIpAddress to prevent
loops.
----End
48.20 L2V/5/SVC_DWN
Message
L2V/5/SVC_DWN:The status of the SVC turned DOWN. (InterfaceName=[STRING],
Reason=[STRING])
Description
This log message explained why the Static Virtual Circuit (SVC) went Down.
Parameters
InterfaceName
Issue 07 (2014-07-30)

462

Log Reference
48 L2V

Reason

2 VC was created
3 VC was deleted
18 Interface was Up
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
26 RLB was Deleted
Issue 07 (2014-07-30)

463

Log Reference
48 L2V

32 PW was recreated
35 Remote AC fault
37 Local AC fault
39 Remote PSN fault
41 Local PSN fault
49 Delay timed out
50 Resume Timed Out
Possible Causes
The SVC went Down.
Procedure
Step 1 Identify the cause of the SVC status change.
----End
48.21 L2V/5/SVC_UP
Issue 07 (2014-07-30)

464

Log Reference
48 L2V
Message
L2V/5/SVC_UP:The status of the SVC turned UP. (InterfaceName=[STRING], Reason=
[STRING])
Description
This log message explained why the SVC went Up.
Parameters
InterfaceName
Issue 07 (2014-07-30)

465

Log Reference
48 L2V

Reason

2 VC was created
3 VC was deleted
18 Interface was Up
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
26 RLB was Deleted
Issue 07 (2014-07-30)

466

Log Reference
48 L2V

32 PW was recreated
35 Remote AC fault
37 Local AC fault
39 Remote PSN fault
41 Local PSN fault
49 Delay timed out
50 Resume Timed Out
Possible Causes
The SVC went Up.
Procedure
Step 1 Identify the cause of the SVC status change.
----End
48.22 L2V/5/VPLSVC_BACKUP
Issue 07 (2014-07-30)

467

Log Reference
48 L2V
Message
L2V/5/VPLSVC_BACKUP:The status of the VPLS VC turned BACKUP. (VsiName=[string],
RemoteIp=[IPADDR], PwId=[ULONG], Reason=[string], SysUpTime=[TIMETICK])
Description
The VPLS VC turned to the backup state.
Parameters
VsiName
Indicates the name of the VSI.
RemoteIp
Indicates the IP address of the remote end.
PwId
Indicates the ID of the PW.
Reason
Indicates the cause of VC status change:

l The bound VRRP turned to a non-master state, such as the backup
state.
l The interface board bound to VRRP was pulled out.
SysUpTime
Indicates the startup time of the system.
Possible Causes
The bound VRRP turned to a non-master state, such as the backup state or the interface board
bound to VRRP was pulled out.
Procedure
----End
48.23 L2V/5/VPLSVC_DWN_ME
Message
L2V/5/VPLSVC_DWN_ME:The status of the VPLS VC turned DOWN. (VsiName=
[STRING], RemoteIp=[IPADDR], PwId=[ULONG], Reason=[STRING], SysUpTime=
[TIMETICK])
Description
This log message explained why the Virtual Private LAN Service (VPLS) VC interface went
Down.
Issue 07 (2014-07-30)

468

Log Reference
48 L2V
Parameters
VsiName
Indicates the name of the Virtual Switching Instance (VSI).
RemoteIp
PwId
Indicates the ID of the pseudo wire (PW).
Issue 07 (2014-07-30)

469

Log Reference
48 L2V

Reason

2. VC was created
3. VC was deleted
21. Refresh
22. Download again
23. Tunnel was Up
24. Tunnel was Down
26. RLB was Deleted
Issue 07 (2014-07-30)

470

Log Reference
48 L2V

35. Remote AC fault
37. Local AC fault
41. Local PSN fault
49. Delay timed out
SysUpTime
Possible Causes
The VC went Down.
Procedure
----End
48.24 L2V/5/VPLSVC_UP_ME
Issue 07 (2014-07-30)

471

Log Reference
48 L2V
Message
L2V/5/VPLSVC_UP_ME:The status of the VPLS VC turned UP. (VsiName=[STRING],
RemoteIp=[IPADDR], PwId=[ULONG], Reason=[STRING], SysUpTime=[TIMETICK])
Description
This log message explained why the VPLS VC interface went Up.
Parameters
VsiName
Indicates the name of the Virtual Switching Instance (VSI).
RemoteIp
PwId
Indicates the ID of the pseudo wire (PW).
Issue 07 (2014-07-30)

472

Log Reference
48 L2V

Reason

2. VC was created
3. VC was deleted
21. Refresh
22. Download again
23. Tunnel was Up
24. Tunnel was Down
26. RLB was Deleted
Issue 07 (2014-07-30)

473

Log Reference
48 L2V

35. Remote AC fault
37. Local AC fault
41. Local PSN fault
49. Delay timed out
SysUpTime
Possible Causes
The VC went Up.
Procedure
----End
48.25 L2V/5/VPLSVSI_DWN
Issue 07 (2014-07-30)

474

Log Reference
48 L2V
Message
L2V/5/VPLSVSI_DWN:The status of the VPLS VSI turned DOWN. (VsiName=[STRING],
Reason=[STRING])
Description
This log message explained why the VPLS VSI went Down.
Parameters
VsiName
Issue 07 (2014-07-30)

475

Log Reference
48 L2V

Reason

2 VC was created
3 VC was deleted
18 Interface was Up
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
26 RLB was Deleted
Issue 07 (2014-07-30)

476

Log Reference
48 L2V

32 PW was recreated
35 Remote AC fault
37 Local AC fault
39 Remote PSN fault
41 Local PSN fault
49 Delay timed out
50 Resume Timed Out
Possible Causes
The VSI went Down.
Procedure
----End
48.26 L2V/5/VPLSVSI_UP
Issue 07 (2014-07-30)

477

Log Reference
48 L2V
Message
L2V/5/VPLSVSI_UP:The status of the VPLS VSI turned UP. (VsiName=[STRING], Reason=
[STRING])
Description
This log message explained why the VPLS VSI went Up.
Parameters
VsiName
Issue 07 (2014-07-30)

478

Log Reference
48 L2V

Reason

2 VC was created
3 VC was deleted
18 Interface was Up
21 Refresh
22 Download again
23 Tunnel was Up
24 Tunnel was Down
26 RLB was Deleted
Issue 07 (2014-07-30)

479

Log Reference
48 L2V

32 PW was recreated
35 Remote AC fault
37 Local AC fault
39 Remote PSN fault
41 Local PSN fault
49 Delay timed out
50 Resume Timed Out
Possible Causes
The VSI went Up.
Procedure
----End
48.27 L2V/5/VSICALINLBLERR
Issue 07 (2014-07-30)

480

Log Reference
48 L2V
Message
L2V/5/VSICALINLBLERR:The remote site ID exceeded local label block range. (SiteId=
[ULONG])
Description
The remote site ID exceeded the local label block range.
Parameters
Parameter Name
Parameter Meaning
SiteId
Indicates the ID of the remote site.
Possible Causes
The remote site ID exceeded the local label block range.
Procedure
Step 1 Enlarge the local label block range.
----End
48.28 L2V/5/VSIMHMPREFSAME
Message
L2V/5/VSIMHMPREFSAME:In the CE dual-homing scenario, the multi-homing preference of
the local PE is the same as that of the remote PE, and thus the connection may not be established.
(VsiName=[STRING], Rlb: Preference=[ULONG], Pe=[STRING], Rd=[STRING])
Description
In the CE dual-homing scenario, the multi-homing preference of the local PE is the same as that
of the remote PE, and thus the connection may not be established.
Parameters
Parameter Name
Parameter Meaning
VsiName
Indicates the name of VSI.
Rlb
Indicates the remote label block.
Preference
Indicates the preference of the RLB.
PE
Indicates the IP address of the PE in the RLB.
Rd
Indicates the route distinguisher of the RLB.
Issue 07 (2014-07-30)

481

Log Reference
48 L2V
Possible Causes
In the CE dual-homing scenario of Kompella mode VPLS, the multi-homing preference of the
local PE is the same as that of the remote PE.
Procedure
Step 1 Lower the multi-homing preference of one end.
----End
48.29 L2V/5/VSIRMTLCLIDSAME
Message
L2V/5/VSIRMTLCLIDSAME:The remote site ID is the same as the local site ID, and the
connection may not be established. (VsiName=[STRING], Rlb: SiteId=[ULONG], Pe=
[STRING], Rd=[STRING])
Description
The remote site ID is the same as the local site ID, and the connection may not be established.
Parameters
Parameter Name
Parameter Meaning
VsiName
Indicates the name of VSI.
Rlb
Indicates the remote label block.
SiteId
Indicates the site ID of the RLB.
Pe
Indicates the IP address of the PE in the RLB.
Rd
Indicates the route distinguisher of the RLB.
Possible Causes
The site IDs on the two PEs connected through Komeplla VPLS were the same.
Procedure
Step 1 Change any one of the two site IDs.
----End
48.30 L2V/5/VSISITEOUTOFRANGE
Issue 07 (2014-07-30)

482

Log Reference
48 L2V
Message
L2V/5/VSISITEOUTOFRANGE:The local site cannot communicate with remote site because
site ID exceeded the range. (Local: SiteId=[ULONG], VsiRd=[STRING]; Remote: SiteId=
[ULONG], Pe=[STRING], VsiRd=[STRING])
Description
The local site cannot communicate with the remote site because the local site ID exceeds the
range.
Parameters
Parameter Name
Parameter Meaning
Local: SiteId
Indicates the ID of the local site.
VsiRd
Indicates the route distinguisher of the local VSI.
Remote: SiteId
Indicates the ID of the remote site.
Pe
VsiRd
Indicates the route distinguisher of the remote VSI.
Possible Causes
The local site ID exceeded the remote ID range. Therefore, no remote label was allocated for
the local site.
Procedure
Step 1 Modify the configuration to enlarge the ID range of the remote site or to decrease the local site
ID.
----End
Issue 07 (2014-07-30)

483

Log Reference
49 L3AD
49
L3AD
About This Chapter

49.1 L3AD/4/RESOURCE_FULL
Issue 07 (2014-07-30)

484

Log Reference
49 L3AD
49.1 L3AD/4/RESOURCE_FULL
Message
L3AD/4/RESOURCE_FULL: The resource of the table on the chip is not enough.(Type=
[STRING])
Description
The entry resources of a chip are allocated, and the current resources are insufficient.
Parameters
Parameter Name
Parameter Meaning
Type
entry type of a chip, including:

l L3INTF: layer-3 egress entry
l L3EGRESS: next-hop entry
l L3EGRESS: next-hop group entry
Possible Causes
The usage of entry resources is beyond the range. It is recommended to release part of resources.
Procedure
Step 1 Check whether a resource usage alarm is reported.
If the number of layer-3 egress entry resources is not enough, delete redundant vlanif and Tunnel
interfaces.
If the number of next-hop entry resources is not enough, shut down certain egresses.
If the number of next-hop group entry resources is not enough, delete certain equivalent routes.
Allocate resources properly according to the specifications
----End
Issue 07 (2014-07-30)

485

Log Reference
50 L3VPN
50
L3VPN
About This Chapter

50.1 L3VPN/3/L3V_STATICLABEL_FAIL
50.2 L3VPN/6/L3V_UNDOFRRNO
50.3 L3VPN/6/L3V_UNDOFRRTIMEOUT
50.4 L3VPN/6/L3V_UNDOFRRYES
50.5 L3VPN/4/PREFIX_MAX_CLEARED
50.6 L3VPN/4/PREFIX_MAX_EXCEEDED
50.7 L3VPN/4/PREFIX_MID_EXCEEDED
50.8 L3VPN/4/ROUTE_MAX_CLEARED
50.9 L3VPN/4/ROUTE_MAX_EXCEEDED
50.10 L3VPN/4/ROUTE_MID_EXCEEDED
Issue 07 (2014-07-30)

486

Log Reference
50 L3VPN
50.1 L3VPN/3/L3V_STATICLABEL_FAIL
Message
L3VPN/3/L3V_STATICLABEL_FAIL:Failed to allocate static label [label-value] to VPN
instance [vpn-instance]. The static label configuration was deleted.
Description
A VPN instance failed to obtain a static label and static label configurations were deleted.
Parameters
Parameter Name
Parameter Meaning
[label-value]
Value of the static label configured for a VPN instance.
[vpn-instance]
Name of a VPN instance
Possible Causes
A VPN instance attempted to obtain a static label based on existing static label configurations
but failed during MPLS enabling.
Procedure
----End
50.2 L3VPN/6/L3V_UNDOFRRNO
Message
L3VPN/6/L3V_UNDOFRRNO:When deciding whether to delete [configuration]
configuration, the user chose NO.
Description
After a user entered the undo ip frr all command to delete the IP FRR configuration or the
undo vpn frr all command to delete the VPN FRR configuration, the user entered No to cancel
the operation.
Issue 07 (2014-07-30)

487

Log Reference
50 L3VPN
Parameters
Parameter Name
Parameter Meaning
[configuration]
Name of the FRR configuration to be deleted. The value can be:

l all IP FRR
l all VPN FRR
Possible Causes
After a user enters the undo ip frr all command to delete the IP FRR configuration or the undo
vpn frr all command to delete the VPN FRR configuration, if the user enters No, the described
log message is generated.
Procedure
----End
50.3 L3VPN/6/L3V_UNDOFRRTIMEOUT
Message
L3VPN/6/L3V_UNDOFRRTIMEOUT:When a user did not input any word in [time]s, the
system exited from the operation automatically.
Description
undo vpn frr all command to delete the VPN FRR configuration, the system displayed a
confirmation message. The user did not confirm the operation within a specified period of time
and the system canceled the operation.
Parameters
[time]
Waiting period for a user to confirm an operation. The default value is

30s.
Possible Causes
vpn frr all command to delete the VPN FRR configuration, the system displays a confirmation
message. If the user does not confirm the operation within the specified time, the system cancels
the operation and generates the described log.
Issue 07 (2014-07-30)

488

Log Reference
50 L3VPN
Procedure
----End
50.4 L3VPN/6/L3V_UNDOFRRYES
Message
L3VPN/6/L3V_UNDOFRRYES:When deciding whether to delete [configuration]
configuration, the user chose YES.
Description
undo vpn frr all command to delete the VPN FRR configuration, the system displayed a
confirmation message. The user entered Yes to continue the operation.
Parameters
Parameter Name
Parameter Meaning
[configuration]
Name of the FRR configuration to be deleted. The value can be:

l all IP FRR
l all VPN FRR
Possible Causes
vpn frr all command to delete the VPN FRR configuration. If the user enters Yes, the described
log message is generated.
Procedure
----End
50.5 L3VPN/4/PREFIX_MAX_CLEARED
Message
L3VPN/4/PREFIX_MAX_CLEARED:The number of route prefixes in VPN instance [vpninstance] reduced to [prefixes-number], which was below the maximum value [max-value].
Issue 07 (2014-07-30)

489

Log Reference
50 L3VPN
Description
The number of added route prefixes fell below the upper limit.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
Indicates the name of the VPN instance.
[prefixes-number]
Indicates the number of the current route prefixes.
[max-value]
Indicates the upper limit for the number of route prefixes.
Possible Causes
The number of route prefixes in the routing table fell below the upper limit.
Procedure
----End
50.6 L3VPN/4/PREFIX_MAX_EXCEEDED
Message
L3VPN/4/PREFIX_MAX_EXCEEDED:The number of route prefixes in VPN instance [vpninstance] was [prefixes-number], which exceeded the maximum value [max-value].
Description
The number of added route prefixes exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
[prefixes-number]
[max-value]
the upper limit for the number of route prefixes.
Possible Causes
After the number of route prefixes in the routing table reached the upper limit, new routes
continued to be added.
Issue 07 (2014-07-30)

490

Log Reference
50 L3VPN
Procedure
Step 1 Run the display ip routing-table vpn-instance [ vpn-instance-name ] statistics command to
check the total number and types of routes in this VPN instance.
Step 2 Analyze the sources of routes and check whether the number of current private prefixes in the
VPN instance meets the requirement.
Step 3 Delete unnecessary private prefixes, and then check whether the number of prefixes still reaches
or exceeds the alarm threshold.
Step 4 Enter the VPN instance view and run the display this command to check the configuration of
prefix limit to check whether the set alarm threshold of private prefixes is proper.
l If not, run the prefix limit number { alert-percent | simply-alert } command to re-configure
a proper alarm threshold. Then, go to Step 6.
Step 6 End.
----End
50.7 L3VPN/4/PREFIX_MID_EXCEEDED
Message
L3VPN/4/PREFIX_MID_EXCEEDED:The number of route prefixes in VPN instance [vpninstance] was [prefixes-number], which exceeded the [threshold-value].
Description
The number of added route prefixes exceeded the alarm threshold for the number of route
prefixes.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
[prefixes-number]
[threshold-value]
the upper limit for the number of route prefixes.
Issue 07 (2014-07-30)

491

Log Reference
50 L3VPN
Possible Causes
After the number of route prefixes in the routing table reached the alarm threshold, new route
prefixes continued to be added.
Procedure
Step 2 Analyze the sources of routes and check whether the number of current private prefixes in the
Step 3 Delete unnecessary private prefixes, and then check whether the number of prefixes still reaches
prefix limit to check whether the set alarm threshold of private prefixes is proper.
l If not, run the prefix limit number { alert-percent | simply-alert } command to re-configure
Step 6 End.
----End
50.8 L3VPN/4/ROUTE_MAX_CLEARED
Message
L3VPN/4/ROUTE_MAX_CLEARED:The total number of routes in VPN instance [vpninstance] reduced to [route-number], which was below the maximum value [maximum-value].
Description
The number routes fell below the upper limit.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
[route-number]
Indicates the number of the current routes.
Issue 07 (2014-07-30)

492

Log Reference
50 L3VPN
Parameter Name
Parameter Meaning
[maximum-value]
Indicates the maximum of the routes.
Possible Causes
The number of routes in the routing table fell below the upper limit.
Procedure
----End
50.9 L3VPN/4/ROUTE_MAX_EXCEEDED
Message
L3VPN/4/ROUTE_MAX_EXCEEDED:The total number of routes in VPN instance [vpninstance] was [route-number], which exceeded the maximum value [maximum-value].
Description
The number of added routes exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
[route-number]
[maximum-value]
Indicates the maximum of the routes.
Possible Causes
After the number of routes in the routing table reached the upper limit, new routes continuted
to be added.
Procedure
Step 2 Analyze the source of each route and check whether the number of current routes in the VPN
instance meets the actual requirement.
Issue 07 (2014-07-30)

493

Log Reference
50 L3VPN
Step 3 Delete unnecessary private routes, and then check whether the number of routes still reaches or
exceeds the alarm threshold.
routing-table limit to check whether the set alarm threshold of private routes is proper.
l If not, run the routing-table limit number { alert-percent | simply-alert } command to reconfigure a proper alarm threshold. Then, go to Step 6.
Step 6 End.
----End
50.10 L3VPN/4/ROUTE_MID_EXCEEDED
Message
L3VPN/4/ROUTE_MID_EXCEEDED:The total number of routes in VPN instance [vpninstance] was [route-number], which exceeded the alarm threshold [threshold-value].
Description
The number of routes exceeded the alarm threshold for the number of routes.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
[route-number]
[threshold-value]
Indicates the alarm threshold for the number of routes.
Possible Causes
After the number of routes in the routing table reached the alarm threshold, new routes continuted
to be added.
Procedure
instance meets the requirement.
Issue 07 (2014-07-30)

494

Log Reference
50 L3VPN
route limit to check whether the set alarm threshold of private routes is proper.
l If not, run the routing-table limit number { alert-percent | simply-alert } command to reconfigure a proper alarm threshold. Then, go to Step 6.
Step 6 End.
----End
Issue 07 (2014-07-30)

495

Log Reference
51 LACP
51
LACP
About This Chapter

51.1 LACP/4/LACP_SND_PDU_IO_FAIL
51.2 LACP/4/PORT_SND_PDU_FAIL
51.3 LACP/6/TMR_NTT_TX
Issue 07 (2014-07-30)

496

Log Reference
51 LACP
51.1 LACP/4/LACP_SND_PDU_IO_FAIL
Message
LACP/4/LACP_SND_PDU_IO_FAIL:The main board failed to send LACP packet to the port.
(TrunkName=[STRING], PortName=[STRING])
Description
A trunk interface failed to send PDU packets.
Parameters
Parameter Name
Parameter Meaning
TrunkName
indicates the name of a trunk interface.
PortName
indicates names of member ports.
Possible Causes
The main control board failed to send LACP packets to the interface board.
Procedure
Step 1 This log message is informational, and no action is required.
----End
51.2 LACP/4/PORT_SND_PDU_FAIL
Message
LACP/4/PORT_SND_PDU_FAIL:The port failed to send LACP packet. (TrunkName=
[STRING], PortName=[STRING])
Description
A member port failed to send a PDU.
Parameters
Parameter Name
Parameter Meaning
PortName
TrunkName
Issue 07 (2014-07-30)

497

Log Reference
51 LACP
Possible Causes
A member port failed to send a PDU.
Procedure
----End
51.3 LACP/6/TMR_NTT_TX
Message
LACP/6/TMR_NTT_TX:The TX state machine is run because PDU NTT of the trunk is zero
in timer. (TrunkName=[STRING])
Description
The TX state machine started to run because PDU NTT of the trunk in the timer was zero.
Parameters
Parameter Name
Parameter Meaning
TrunkName
Possible Causes
The LACP function was enabled.
Procedure
----End
Issue 07 (2014-07-30)

498

Log Reference
52 LDP
52
LDP
About This Chapter

52.1 LDP/6/DATASMTHBEGAN
52.2 LDP/4/FAILALLOCTOKEN
52.3 LDP/4/FAILEXITMUL
52.4 LDP/4/FAILJOINMUL
52.5 LDP/4/FAILSENDMSG
52.6 LDP/6/GRCRTFORWDTMR
52.7 LDP/6/GREND
52.8 LDP/4/HOLDTMREXP
52.9 LDP/4/IFJIONFAIL
52.10 LDP/4/IFJIONSUCC
52.11 LDP/4/IMPMSGLISTEXCEED
52.12 LDP/4/INSTAIDINVALID
52.13 LDP/4/JIONRETRYFAIL
52.14 LDP/6/NOENABLELDP
52.15 LDP/6/NOTIGRSTART
52.16 LDP/4/OPENRETRYTMR
52.17 LDP/6/PEERCLS
52.18 LDP/6/PEERRESTART
52.19 LDP/6/RCVFTMSG
52.20 LDP/6/RMGREND
Issue 07 (2014-07-30)

499

Log Reference
52 LDP
52.21 LDP/4/SAMADDRESS
52.22 LDP/6/SMTHCOMPL
52.23 LDP/6/SMTHREJIONMUL
52.24 LDP/6/SRVREFUSE
52.25 LDP/4/SSNHOLDTMREXP
52.26 LDP/6/SYSGRBEGIN
52.27 LDP/6/SYSGREND
52.28 LDP/6/SYSGRNOENABLEMPLS
52.29 LDP/6/SYSGRNOLDPGR
52.30 LDP/6/WAITPEERGR
Issue 07 (2014-07-30)

500

Log Reference
52 LDP
52.1 LDP/6/DATASMTHBEGAN
Message
LDP/6/DATASMTHBEGAN:LDP data smooth began.
Description
LDP data smooth began.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The local entity event was created when the route was started.
Procedure
----End
52.2 LDP/4/FAILALLOCTOKEN
Message
LDP/4/FAILALLOCTOKEN:Cannot allocate a token to FEC [ip-address]. (NextHop=
[ULONG1], ErrorStatus=[ULONG2])
Description
Failed to allocate a token for FEC.
Parameters
[ip-address]
Indicates the IP address of FEC.
NextHop
Issue 07 (2014-07-30)

501

Log Reference
52 LDP

ErrorStatus
Indicates the returned errored status when allocating a token was failed
1: indicates the LSPM ERR.
l Failed to allocate a token because obtaining interface information by
interface index was failed.
l Failed to allocate a token because the system resources were
insufficient.
Possible Causes
The management module failed to allocate a token for LDP.
Procedure
Step 1 Run the display tunnel-info statistic command to check whether the tunnel management module
has enough tunnels.
Step 2 Run the debugging mpls management interface command to check whether the tunnel
management module has enough tunnels. If Allocate tunnel fail is displayed, this indicates that
tunnels are not enough.
----End
52.3 LDP/4/FAILEXITMUL
Message
LDP/4/FAILEXITMUL:Cannot exit the UDP multicast group. (ErrorCode=[LONG])
Description
Failed to exit the UDP multicast group.
Parameters
Parameter Name
Parameter Meaning
ErrorCode
Indicates the error code, such as -107, 0, -105, -108, -106, -22.
Possible Causes
Failed to exit the UDP multicast group.
Procedure
Step 1 Run the debugging mpls ldp socket command to collect debugging information.
Issue 07 (2014-07-30)

502

Log Reference
52 LDP

----End
52.4 LDP/4/FAILJOINMUL
Message
LDP/4/FAILJOINMUL:Cannot join the UDP multicast group. (ErrorCode=[LONG])
Description
Failed to add to the UDP multicast group.
Parameters
Parameter Name
Parameter Meaning
ErrorCode
Indicates the error code, such as -107, 0, -105, -108, -106, -22.
Possible Causes
Failed to add to the UDP multicast group.
Procedure
----End
52.5 LDP/4/FAILSENDMSG
Message
LDP/4/FAILSENDMSG:Cannot send TCP message. (PeerIP=[STRING], MessageLength=
[ULONG], SocketId=[ULONG], ErrorSocketStatus=[LONG])
Description
Failed to send the TCP message.
Parameters
PeerIP
Issue 07 (2014-07-30)

503

Log Reference
52 LDP

MessageLength
Indicates the message length.
SocketId
Indicates the socket ID.
ErrorSocketStatus
Indicates the error socket state, such as -107, 0, -105, -108, -106, -22.
Possible Causes
Failed to send the TCP packet with the following attributes.
Procedure
----End
52.6 LDP/6/GRCRTFORWDTMR
Message
LDP/6/GRCRTFORWDTMR:LDP System-level GR timer interval was set to [interval]
seconds.
Description
The LDP system-level GR timer interval was set to required seconds.
Parameters
Parameter Name
Parameter Meaning
[interval]
Indicates the system-level timer interval.
Possible Causes
LDP created a timer for MPLS GR.
Procedure
----End
52.7 LDP/6/GREND
Issue 07 (2014-07-30)

504

Log Reference
52 LDP
Message
LDP/6/GREND:LDP GR was complete.
Description
LDP GR was complete.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
LDP GR was complete.
Procedure
----End
52.8 LDP/4/HOLDTMREXP
Message
LDP/4/HOLDTMREXP:Sessions were deleted because the hello hold timer expired. (PeerId=
[STRING])
Description
Sessions were deleted because the neighbor hold timer expired.
Parameters
Parameter Name
Parameter Meaning
PeerId
Indicates the LSR ID of the peer.
Possible Causes
Sessions were deleted because the Hello hold timer expired.
Issue 07 (2014-07-30)

505

Log Reference
52 LDP
Procedure
Step 1 Run the display ip routing-table command to check whether the peer system is stable and the
network status is normal.
----End
52.9 LDP/4/IFJIONFAIL
Message
LDP/4/IFJIONFAIL:The interface [interface-name] cannot join the multicast group. Retry times
exceeded the maximum retries [times].
Description
The interface failed to add to the multicast group. Retry times exceeded the maximum retries.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[times]
Indicates the maximum retry times, 60 times.
Possible Causes
1: The configuration of the interface that applied for adding to the multicast group was incorrect.
2: The ID of the instance that applied for adding to the multicast group was invalid.
Procedure
Step 1 Run the debugging mpls ldp session command to collect debugging information.
----End
52.10 LDP/4/IFJIONSUCC
Message
LDP/4/IFJIONSUCC:The interface [interface-name] succeeded in joining the multicast group
after retrying [times] times.
Description
The interface succeeded in adding to the multicast group after retrying multiple times.
Issue 07 (2014-07-30)

506

Log Reference
52 LDP
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[times]
Possible Causes
The interface succeeded in adding to the multicast group.
Procedure
----End
52.11 LDP/4/IMPMSGLISTEXCEED
Message
LDP/4/IMPMSGLISTEXCEED:The length of the LDP important message list reached the
alarm threshold [threshold].
Description
The length of the LDP important message list reached the alarm threshold.
Parameters
Parameter Name
Parameter Meaning
[threshold]
Indicates the alarm threshold of the LDP message list.
Possible Causes
After a large number of LDP messages were received, these messages were not processed in
time, causing the queue length to the alarm threshold.
Procedure
Step 1 Run the display memory-usage command to check memory usage.
Step 2 If necessary and allowed, run the reset mpls ldp command in the user view to clean the linked
list. Exercise caution when running this command because all LDP sessions will be reset.
----End
Issue 07 (2014-07-30)

507

Log Reference
52 LDP
52.12 LDP/4/INSTAIDINVALID
Message
LDP/4/INSTAIDINVALID:The interface [interface-name] cannot join the multicast group
because the private network ID was invalid.
Description
Failed to add to the multicast group because the private network ID was invalid.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
Failed to add to the multicast group.
Procedure
Step 1 Run the debugging mpls ldp session command to collect debugging information.
----End
52.13 LDP/4/JIONRETRYFAIL
Message
LDP/4/JIONRETRYFAIL:The interface [interface-name] cannot join the multicast group after
retrying [times] times.
Description
The number of times that the interface failed to add to the multicast group.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[times]
Issue 07 (2014-07-30)

508

Log Reference
52 LDP
Possible Causes
LDP instance failed to add to the multicast group because of timeout.
Procedure
Step 1 Check whether the configuration of the interface that applies for adding to the multicast group
is correct.
Step 2 Check whether the number of instances that apply for adding to the multicast group is too large.
----End
52.14 LDP/6/NOENABLELDP
Message
LDP/6/NOENABLELDP:LDP System-level GR processing was complete because LDP is not
enabled globally.
Description
LDP System-level GR processing was complete because LDP is not enabled globally.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
LDP was not enabled globally.
Procedure
Step 1 Run the display current-configuration command to check whether the MPLS LDP is enabled
globally.
----End
52.15 LDP/6/NOTIGRSTART
Message
LDP/6/NOTIGRSTART:The system notified L2VPN and other features that LDP system-level
GR processing started after LDP GR was enabled.
Issue 07 (2014-07-30)

509

Log Reference
52 LDP
Description
The system notified L2VPN and other features that LDP system-level GR processing started
after LDP GR was enabled.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
LDP notified the GR event to the L2VPN.
Procedure
----End
52.16 LDP/4/OPENRETRYTMR
Message
LDP/4/OPENRETRYTMR:When the interface [interface-name] cannot join the multicast
group, the retry timer was opened.
Description
When the interface failed to add to the multicast group, the reconnection timer was restarted.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
1: Incorrect configurations of the interface that applies for adding to the multicast group resulted
in failing to add to the multicast group. Restarted the timer that added to the multicast group.
The precondition was that the interval of the timer did not exceed the maximum interval.
2: The invalid ID of the instance that applies for adding to the multicast group resulted in failing
to add to the multicast group. Restarted the timer that added to the multicast group. The
precondition was that the interval of the timer did not exceed the maximum interval.
Issue 07 (2014-07-30)

510

Log Reference
52 LDP
Procedure
Step 1 Run the display current-configuration command to check the configuration of the interface that
applies for adding to multicast is correct.
Step 2 Check whether the number of instances that applies for adding to the multicast group is too large.
----End
52.17 LDP/6/PEERCLS
Message
LDP/6/PEERCLS:The message that the peer closed was received from TCP Socket ID [socketid].
Description
The message that the peer closed was received from the TCP socket ID
Parameters
Parameter Name
Parameter Meaning
[socket-id]
Possible Causes
LDP received the event that the peer closed from the TCP.
Procedure
Step 1 Run the display interface command to check whether the link status is stable.
----End
52.18 LDP/6/PEERRESTART
Message
LDP/6/PEERRESTART:The peer LSR [peer-id] was restarting.
Description
The peer LSR was being restarted.
Issue 07 (2014-07-30)

511

Log Reference
52 LDP
Parameters
Parameter Name
Parameter Meaning
[peer-id]
Indicates the peer LSR ID.
Possible Causes
The local end set up the session with the peer end when the neighboring device was restarted or
the session flapped. The precondition was that the LDP GR was configured before the LSR
connection was established.
Procedure
Step 1 If the peer is restarted, this log message indicates a normal situation, and no action is required.
Step 2 If the session flaps, run the display interface command to check whether links between the two
devices are normal and run the display tcp status command to check whether TCP connections
are normal.
----End
52.19 LDP/6/RCVFTMSG
Message
LDP/6/RCVFTMSG:Received FT message from peer [peer-id].
Description
The message that the peer enabled graceful restart was received from the peer.
Parameters
Parameter Name
Parameter Meaning
[peer-id]
Possible Causes
The initialization message that the peer enabled graceful restart was received.
Procedure
----End
Issue 07 (2014-07-30)

512

Log Reference
52 LDP
52.20 LDP/6/RMGREND
Message
LDP/6/RMGREND:The event that GR of the route management (RM) module was complete
was received.
Description
The event that GR of the route management module was complete was received.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The relevant module completed GR after the device was restarted, and notified the module.
Procedure
----End
52.21 LDP/4/SAMADDRESS
Message
LDP/4/SAMADDRESS:Received same address from different sessions. (Address=[STRING],
OldPeer=[STRING], NewPeer=[STRING])
Description
The same address from different sessions was received.
Parameters
Parameter Name
Parameter Meaning
Address
OldPeer
Indicates the LSR ID of the old peer.
NewPeer
Indicates the LSR ID of the new peer.
Issue 07 (2014-07-30)

513

Log Reference
52 LDP
Possible Causes
The same address from different peers was received.
Procedure
Step 1 Run the display current-configuration command to check whether the same address is
configured.
Step 2 Operators should check whether network attacks exist.
----End
52.22 LDP/6/SMTHCOMPL
Message
LDP/6/SMTHCOMPL:LDP data smooth was complete.
Description
LDP data smooth was complete.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Data smooth backup was complete.
Procedure
----End
52.23 LDP/6/SMTHREJIONMUL
Message
LDP/6/SMTHREJIONMUL:The interface [interface-name] retried joining the multicast group
during data smooth.
Description
The interface retried to add to the multicast group during data smooth.
Issue 07 (2014-07-30)

514

Log Reference
52 LDP
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
The switchover between the master board and the slave board was performed.
Procedure
----End
52.24 LDP/6/SRVREFUSE
Message
LDP/6/SRVREFUSE:The server refused the request of the instance [instance-name]. (PeerIP=
[STRING], SocketId=[USHORT])
Description
The server refused the request of the instance [instance-name].
Parameters
Parameter Name
Parameter Meaning
[instance-name]
Indicates the name of instance.
PeerIP
SocketId
Possible Causes
The client establishing the TCP connection did not receive the message for establishing the
connection from the peer when sending the connection request.
Procedure
----End
52.25 LDP/4/SSNHOLDTMREXP
Issue 07 (2014-07-30)

515

Log Reference
52 LDP
Message
LDP/4/SSNHOLDTMREXP:Sessions were deleted because the session hold timer expired and
the notification of the expiry was sent to the peer [peer-id].
Description
The session was deleted because the session hold timer timed out and the notification that the
timer timed out was sent to the peer.
Parameters
Parameter Name
Parameter Meaning
[peer-id]
Possible Causes
The session hold timer timed out and the notification that the timer timed out was sent to the
peer.
Procedure
----End
52.26 LDP/6/SYSGRBEGIN
Message
LDP/6/SYSGRBEGIN:LDP System-level GR processing began.
Description
LDP System-level GR processing began.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The slave board was started.
Issue 07 (2014-07-30)

516

Log Reference
52 LDP
Procedure
----End
52.27 LDP/6/SYSGREND
Message
LDP/6/SYSGREND:LDP System-level GR processing was complete.
Description
LDP System-level GR processing was complete.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
System-level GR processing was complete.
Procedure
----End
52.28 LDP/6/SYSGRNOENABLEMPLS
Message
LDP/6/SYSGRNOENABLEMPLS:LDP System-level GR processing was complete because
mpls is not enabled globally.
Description
LDP System-level GR processing was complete because mpls is not enabled globally.
Issue 07 (2014-07-30)

517

Log Reference
52 LDP
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
MPLS is not enabled globally.
Procedure
----End
52.29 LDP/6/SYSGRNOLDPGR
Message
LDP/6/SYSGRNOLDPGR:The system notified other features that LDP system-level GR ended
when LDP GR was not enabled.
Description
The system notified other features that LDP system-level GR ended when LDP GR was not
enabled.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
LDP GR was not enabled.
Procedure
----End
52.30 LDP/6/WAITPEERGR
Issue 07 (2014-07-30)

518

Log Reference
52 LDP
Message
LDP/6/WAITPEERGR:Wait for peer restart, peer session subject to graceful restart.
Description
The neighbor GR was being restarted and waited GR of the peer to be restarted.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The LDP session was negotiated to be re-established when the peer LSR was enabled with
graceful restart.
Procedure
----End
Issue 07 (2014-07-30)

519

Log Reference
53 LINE
53
LINE
About This Chapter

53.1 LINE/3/AUTO_EXEC
53.2 LINE/3/CLR_ONELINE
53.3 LINE/3/NO_EXEC
53.4 LINE/3/SND_ALL
53.5 LINE/3/SND_ONE
53.6 LINE/5/UNLOCK
53.7 LINE/4/UNLOCK_FAIL
Issue 07 (2014-07-30)

520

Log Reference
53 LINE
53.1 LINE/3/AUTO_EXEC
Message
LINE/3/AUTO_EXEC:The user chose [STRING] when deciding whether to automatically
execute the command.
Description
The user needed to determine whether to automatically run the command before running the
command.
Parameters
Parameter Name
Parameter Meaning
[STRING]

l Y: Yes.
l N: No.
Possible Causes
The user needed to determine whether to automatically run the command before running the
command.
Procedure
----End
53.2 LINE/3/CLR_ONELINE
Message
LINE/3/CLR_ONELINE:The user chose [STRING] when deciding whether to disconnect the
specified user interface.
Description
The user needed to determine whether to disconnect from the specified user interface before
running the command.
Issue 07 (2014-07-30)

521

Log Reference
53 LINE
Parameters
Parameter Name
Parameter Meaning
[STRING]

l Y: Yes.
l N: No.
Possible Causes
The user needed to determine whether to disconnect the specified user interface before running
the command.
Procedure
----End
53.3 LINE/3/NO_EXEC
Message
LINE/3/NO_EXEC:The user chose [STRING] when deciding whether to cancel the current
configuration.
Description
The user needed to determine whether to cancel the current configuration before running the
command.
Parameters
Parameter Name
Parameter Meaning
[STRING]

l Y: Yes.
l N: No.
Possible Causes
The user needed to determine whether to cancel the current configuration before running the
command.
Procedure
----End
Issue 07 (2014-07-30)

522

Log Reference
53 LINE
53.4 LINE/3/SND_ALL
Message
LINE/3/SND_ALL:The user chose [STRING] when deciding whether to send messages to all
the users.
Description
The user needed to determine whether to send messages to all the users before running the
command.
Parameters
Parameter Name
Parameter Meaning
[STRING]

l Y: Yes.
l N: No.
Possible Causes
The user needed to determine whether to send messages to all the users before running the
command.
Procedure
----End
53.5 LINE/3/SND_ONE
Message
LINE/3/SND_ONE:The user chose [STRING] when deciding whether to send messages to the
specified user.
Description
The user needed to determine whether to send messages to the specified user before running the
command.
Issue 07 (2014-07-30)

523

Log Reference
53 LINE
Parameters
Parameter Name
Parameter Meaning
[STRING]

l Y: Yes.
l N: No.
Possible Causes
The user needed to determine whether to send messages to the specified user before running the
command.
Procedure
----End
53.6 LINE/5/UNLOCK
Message
LINE/5/UNLOCK: The user unlocked the user-interface [user-interface] successfully.
(UserName=[UserName], IPAddress=[IPAddress], TriedTimes=[TriedTimes])
Description
The user unlocked the user interface.
Parameters
user-interface
User interface type and number
UserName
User name
user name.
IPAddress
User IP address
Issue 07 (2014-07-30)

524

Log Reference
53 LINE

TriedTimes
Number of times the password is entered
Possible Causes
After the user ran the lock command to lock the user interface and set a locking password, the
user attempted to enter the locking password to unlock the user interface. The log was recorded
after the user unlocked the user interface.
Procedure
----End
53.7 LINE/4/UNLOCK_FAIL
Message
LINE/4/UNLOCK_FAIL: The user failed to unlock the user-interface [user-interface].
(UserName=[UserName], IPAddress=[IPAddress], FailedTimes=[FailedTimes])
Description
The user failed to unlock the user interface.
Parameters
user-interface
Indicates the user interface type and number.
UserName

user name.
IPAddress
Indicates the user IP address.

FailedTimes
Issue 07 (2014-07-30)
Indicates the number of times the password is incorrectly entered.

525

Log Reference
53 LINE
Possible Causes
After the user ran the lock command to lock the user interface and set a locking password, the
user attempted to enter the locking password to unlock the user interface. When the number of
times the password is incorrectly entered reaches three, the log was generated.
Procedure
----End
Issue 07 (2014-07-30)

526

Log Reference
54 LLDP
54
LLDP
About This Chapter

54.1 LLDP/4/BAD_PACKET
54.2 LLDP/4/CREATEPORTFAIL
54.3 LLDP/4/DESTINATIONSLOTNOTUP
54.4 LLDP/4/GLOBALENABLEFAIL
54.5 LLDP/4/PORTDISABLEFAIL
54.6 LLDP/4/PORTENABLEFAIL
54.7 LLDP/4/SENDIPCFAIL
54.8 LLDP/4/SENDRPCFAIL
54.9 LLDP/4/TOOMANYNEIGHBORS
Issue 07 (2014-07-30)

527

Log Reference
54 LLDP
54.1 LLDP/4/BAD_PACKET
Message
LLDP/4/BAD_PACKET:[ULONG] invalid packets were received after latest notification. The
last invalid packet came from interface [STRING].
Description
When a neighbor device is faulty, the format of an LLDP packet may be incorrect. As a result,
the network management system (NMS) may not know the topology information. In this case,
related information must be recorded and reported. The mechanism is as follows:
If an invalid packet is detected for the first time, an alarm is reported immediately and the invalid
packet counter is set to 1.
In the following 30 seconds, if another invalid packet is received, 1 is added to the number of
invalid packets.
30 seconds later, if another invalid packet is still received, an alarm containing the number of
invalid packets and the port where this invalid packet is received is reported and the invalid
packet counter is cleared to zero.
Parameters
[PacketNumber]
number of invalid packets
[InterfaceName]
name of interface where invalid packets are received, for example,

GigabitEthernet 1/0/0
Possible Causes
Reason 1:
The format of a received LLDP packet is invalid.
Reason 2:
An invalid packet is used for malicious attack.
Procedure
Step 1 The administrator can run a command to check whether the neighbor device connected with the
port where an invalid packet is received is in the normal status.
l In the system view, run display interface to check whether the status of the port is UP.
l If both the local device and the neighbor device enable DLDP, run display dldp to check
whether the link status is UP.
1) If yes, go to step 3.
Issue 07 (2014-07-30)

528

Log Reference
54 LLDP
2) If no, go to step 2.
Step 2 Check whether the connection cable is connected properly.
1) If no, connect the cable properly and go to step 4.
Step 3 Check whether there are invalid connections.
1) If yes, remove the cables and go to step 4.
Step 4 30 seconds later, check whether this log still exists in the log buffer.
Step 6 End.
----End
54.2 LLDP/4/CREATEPORTFAIL
Message
LLDP/4/CREATEPORTFAIL:Interface [STRING] is not created successfully
Description
Failed to create the local interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

529

Log Reference
54 LLDP
54.3 LLDP/4/DESTINATIONSLOTNOTUP
Message
LLDP/4/DESTINATIONSLOTNOTUP:Destination slot [ULONG] is not up.(Message type=
[ULONG])
Description
The board in the specified slot does not work.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the slot ID of the board.
[ULONG]
Possible Causes
The board in the specified slot does not work.
Procedure
Step 1
Check whether the board is registered.
----End
54.4 LLDP/4/GLOBALENABLEFAIL
Message
LLDP/4/GLOBALENABLEFAIL:GLOBAL LLDP is not enabled successfully
Description
Failed to enable LLDP globally.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

530

Log Reference
54 LLDP
Possible Causes
Failed to enable LLDP globally.
Procedure
----End
54.5 LLDP/4/PORTDISABLEFAIL
Message
LLDP/4/PORTDISABLEFAIL:LLDP is not disabled on port [ULONG] successfully
Description
Failed to disable LLDP on an interface.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The PCT entry failed to be delivered.
Procedure
Step 1
----End
54.6 LLDP/4/PORTENABLEFAIL
Message
LLDP/4/PORTENABLEFAIL:LLDP is not enabled on port [ULONG] successfully
Description
Failed to enable LLDP on an interface.
Issue 07 (2014-07-30)

531

Log Reference
54 LLDP
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The PCT entry failed to be delivered.
Procedure
Step 1
----End
54.7 LLDP/4/SENDIPCFAIL
Message
LLDP/4/SENDIPCFAIL:Failed to send IPC message.(Destination slot=[ULONG],Message
type=[ULONG])
Description
Failed to send IPC messages to a board.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
[ULONG]
Possible Causes
Failed to send IPC messages to a board.
Procedure
Step 1
----End
Issue 07 (2014-07-30)

532

Log Reference
54 LLDP
54.8 LLDP/4/SENDRPCFAIL
Message
LLDP/4/SENDRPCFAIL:Failed to send RPC message.(Destination slot=[ULONG],Message
type=[ULONG])
Description
Failed to send RPC messages to a board.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
[ULONG]
Possible Causes
Failed to send RPC messages to a board.
Procedure
Step 1
----End
54.9 LLDP/4/TOOMANYNEIGHBORS
Message
LLDP/4/TOOMANYNEIGHBORS:No enough resources to save neighbors
Description
The number of neighbor entries at the remote end exceeds the maximum value
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

533

Log Reference
54 LLDP
Possible Causes
In general, the topology does not generate the event that the number of neighbors exceeds the
maximum value (the maximum number of global neighbors is 4096, and the maximum number
of neighbors under a port is 256). The event happens because the peer device connected to the
current device enables the LLDP transparent transmission function so that a large number of
non-direct connection devices become the neighbors of the current device.
Procedure
Step 1 Disable the LLDP function on the ports whose topology information is less important (in the
view of the ports, run the undo lldp enable command) to release space for new neighbors.
----End
Issue 07 (2014-07-30)

534

Log Reference
55 LOAD
55
LOAD
About This Chapter

NOTE
The following logs are generated only in stack scenarios but not on a standalone device.
55.1 LOAD/6/CLIENTLEFT
55.2 LOAD/6/SLOTJOINED
55.3 LOAD/6/SLOTLEFT
Issue 07 (2014-07-30)

535

Log Reference
55 LOAD
55.1 LOAD/6/CLIENTLEFT
Message
LOAD/6/CLIENTLEFT:The client that is loading system-software has left the stack, and the
server slot is [ULONG].
Description
A new member switch that is downloading system software has left a stack system, and the ID
of the member switch that provides system software is specified.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Stack ID, which is an integer that ranges from 0 to 8.
Possible Causes
If the system software versions of the member switches in a stack are different, a new member
switch proactively sends a request to a neighboring member switch to download system software
when the stack is established or merged. If the new switch powers off when downloading system
software or the stack cable is faulty, this log is generated in the stack system.
Procedure
l
Rectify the fault using the same method as that used when a stack system is divided. For
details, see the troubleshooting procedure in 55.3 LOAD/6/SLOTLEFT.
----End
55.2 LOAD/6/SLOTJOINED
Message
LOAD/6/SLOTJOINED:Slot [ULONG] joined the stack.
Description
A member switch joined a stack system.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Issue 07 (2014-07-30)

536

Log Reference
55 LOAD
Possible Causes
The stack is merged and new member switches join the stack system.
Procedure
l
----End
55.3 LOAD/6/SLOTLEFT
Message
LOAD/6/SLOTLEFT:Slot [ULONG] left the stack.
Description
A member switch left a stack system.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The stack is divided and member switches leave the stack system.
Procedure
Step 1 Check whether the user divides the stack system. If yes, no action is required. If no, go to the
next step.
Step 2 Check whether the member switch powers off. If yes, power on it and the device automatically
merges the stack. If no, go to the next step.
Step 3 Check whether the stack configuration is deleted or modified by other user mistakenly.
Run the display stack current-configuration command to check whether the stack
configuration is modified. If the stack configuration is modified, restore the original
configuration and check whether the stack is merged. If the stack configuration is not modified
or the stack is not merged, go to the next step.
Step 4 Check whether the stack link is faulty.
Run the display interface stack-port command to check whether the stack links are in Up state
and whether packets are sent and received properly. If the ports are in Down state or a small
number of packets are sent and received, the stack links connected to the port are faulty. Replace
the stack cables or optical modules.
Issue 07 (2014-07-30)

537

Log Reference
55 LOAD
If the stack links are normal and the stack is still not merged, go to the next step.
----End
Issue 07 (2014-07-30)

538

Log Reference
56 LSPM
56
LSPM
About This Chapter

56.1 LSPM/6/BFD_AGE
56.2 LSPM/6/BFD_FULL_CREATING
56.3 LSPM/3/BFD_LDP_UNABLE_INIT
56.4 LSPM/6/DSTEMODESWITCH
56.5 LSPM/3/FAIL_CREATE_STALE_IF
56.6 LSPM/3/FAIL_DELETE_STALE_IF
56.7 LSPM/6/FLOODFORTECLASSEVT
56.8 LSPM/6/GLOBALMPLSTEENABLE
56.9 LSPM/6/GR_END_TIME
56.10 LSPM/6/GR_START_TIME
56.11 LSPM/6/GRAGINGBEGIN
56.12 LSPM/6/GRAGINGEND
56.13 LSPM/3/GRAGINGFAIL
56.14 LSPM/3/GTSMMSGSENDFAIL
56.15 LSPM/6/HASMOOTHBEGIN
56.16 LSPM/6/HASMOOTHEND
56.17 LSPM/3/HASMOOTHFAIL
56.18 LSPM/3/LSPMTEST
56.19 LSPM/6/NOTIFYCSPFDSTEEVT
56.20 LSPM/6/NOTIFYLSPMDSTEEVT
Issue 07 (2014-07-30)

539

Log Reference
56 LSPM
56.21 LSPM/6/NOTIFYRSVPDSTEEVT
56.22 LSPM/6/PREEMPTIONRESULT
56.23 LSPM/3/PROCESSTNLMSGFAILED
56.24 LSPM/6/RECEIVEGRENDEVENT
56.25 LSPM/6/SENTBATCHBKUPOVERHA
56.26 LSPM/6/SENTSMOOTHFINISHHA
56.27 LSPM/6/SLOTPLUGINOUTEVENT
56.28 LSPM/4/SWITCH_TO_PT_FAIL
56.29 LSPM/4/SWITCH_TO_PTUNN
56.30 LSPM/4/SWITCH_TO_WT_FAIL
56.31 LSPM/4/SWITCH_TO_WTUNN
56.32 LSPM/4/TRAPSUPPRESS
56.33 LSPM/6/TRIGGERRSVPCOUNT
56.34 LSPM/3/TRIGGERRSVPFAIL
56.35 LSPM/6/TWOLABELFORSAMEFEC
Issue 07 (2014-07-30)

540

Log Reference
56 LSPM
56.1 LSPM/6/BFD_AGE
Message
LSPM/6/BFD_AGE:Notified BFD to age the unrefreshed BFD sessions for LSP.
Description
LSPM notified BFD to age the unrefreshed BFD sessions of LSP.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
BFD aged the unrefreshed BFD sessions before GR ended.
Procedure
----End
56.2 LSPM/6/BFD_FULL_CREATING
Message
LSPM/6/BFD_FULL_CREATING: BFD return session full while creating BFD session.
Description
The number of sessions reached the upper limit of the PAF or the license when the BFD session
was created.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The number of sessions reached the upper limit of the PAF or the License.
Issue 07 (2014-07-30)

541

Log Reference
56 LSPM
Procedure
Step 1 Delete redundant BFD sessions.
----End
56.3 LSPM/3/BFD_LDP_UNABLE_INIT
Message
LSPM/3/BFD_LDP_UNABLE_INIT:Unable to initialize BFD for LDP LSP.
Description
The BFD of the LDP LSP cannot be initialized.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to initialize the LDP BFD.
Procedure
----End
56.4 LSPM/6/DSTEMODESWITCH
Message
LSPM/6/DSTEMODESWITCH:DS-TE mode switched from [mode1] to [mode2].
Description
The DS-TE mode was switched from one mode to the other.
Issue 07 (2014-07-30)

542

Log Reference
56 LSPM
Parameters
[mode1]
Indicates the DS-TE mode1, including standard and non-standard DS-TE

modes.
[mode2]
Indicates the DS-TE mode1, including standard and non-standard DS-TE

modes.
Possible Causes
A user switched the DS-TE mode.
Procedure
----End
56.5 LSPM/3/FAIL_CREATE_STALE_IF
Message
LSPM/3/FAIL_CREATE_STALE_IF:Cannot create the stale interface [interface-name]
because the stale interface number reaches limit.
Description
Failed to create the stale interface.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Indicates the name of interface.
Possible Causes
Failed to create the stale interface.
Procedure
----End
56.6 LSPM/3/FAIL_DELETE_STALE_IF
Issue 07 (2014-07-30)

543

Log Reference
56 LSPM
Message
LSPM/3/FAIL_DELETE_STALE_IF:Failed to delete the stale interface [interface-name].
Description
Failed to delete the stale interface.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
Failed to delete the stale interface.
Procedure
----End
56.7 LSPM/6/FLOODFORTECLASSEVT
Message
LSPM/6/FLOODFORTECLASSEVT:Flooded TE resource information for TE-Class change
event.
Description
TE resources were flooded when TE-Class changed.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The TE-Class mapping table was changed.
Procedure
----End
Issue 07 (2014-07-30)

544

Log Reference
56 LSPM
56.8 LSPM/6/GLOBALMPLSTEENABLE
Message
LSPM/6/GLOBALMPLSTEENABLE:Global MPLS TE capability was enabled.
Description
MPLS TE was globally enabled.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
MPLS TE was globally enabled.
Procedure
----End
56.9 LSPM/6/GR_END_TIME
Message
LSPM/6/GR_END_TIME:RSVP GR ended at time [time].
Description
End time of RSVP GR.
Parameters
Parameter Name
Parameter Meaning
[time]
Indicates the end time.
Possible Causes
When GR ended, RSVP notified LSM. LSPM recorded the time when the message for RSVP
GR end was received.
Issue 07 (2014-07-30)

545

Log Reference
56 LSPM
Procedure
----End
56.10 LSPM/6/GR_START_TIME
Message
LSPM/6/GR_START_TIME:RSVP GR began at time [time].
Description
Start time of RSVP GR.
Parameters
Parameter Name
Parameter Meaning
[time]
Indicates the start time.
Possible Causes
When GR started, RSVP notified LSM. LSPM recorded the time when the message for RSVP
GR start was received.
Procedure
----End
56.11 LSPM/6/GRAGINGBEGIN
Message
LSPM/6/GRAGINGBEGIN:LSPM started RSVP aging at time [time].
Description
LSPM GR began to age.
Issue 07 (2014-07-30)

546

Log Reference
56 LSPM
Parameters
Parameter Name
Parameter Meaning
[time]
Indicates the time at which LSPM GR began to age.
Possible Causes
MPLS TE performed protocol-level GR or the system-level GR ended.
Procedure
----End
56.12 LSPM/6/GRAGINGEND
Message
LSPM/6/GRAGINGEND:LSPM finished RSVP aging at time [time].
Description
LSPM GR aging ended.
Parameters
Parameter Name
Parameter Meaning
[time]
Indicates the time at which LSPM GR finished aging.
Possible Causes
Procedure
----End
56.13 LSPM/3/GRAGINGFAIL
Issue 07 (2014-07-30)

547

Log Reference
56 LSPM
Message
LSPM/3/GRAGINGFAIL:An error occurred when the aging of an RSVP LSP was in process.
(ErrorCode=[ULONG], IngressLsrId=[IPADDR], SessionTunnelId=[ULONG], LcalLspId=
[ULONG])
Description
LSPM failed to delete the LSP that was not updated during aging process.
Parameters
Parameter Name
Parameter Meaning
ErrorCode
IngressLsrId
Indicates the ID of the ingress LSR.
SessionTunnelId
Indicates the tunnel ID.
LcalLspId
Indicates the ID of the local LSP.
Possible Causes
LSPM failed to delete LSP or notify the agent module during GR aging.
Procedure
Step 1 Run the debugging mpls management graceful-restart process command to check the specific
cause.
----End
56.14 LSPM/3/GTSMMSGSENDFAIL
Message
LSPM/3/GTSMMSGSENDFAIL:Failed to send GTSM policy. (Protocol=[STRING], Flag=
[STRING], Address=[STRING])
Description
LSPM failed to send GTSM policy.
Parameters
Parameter Name
Parameter Meaning
Protocol
Name of the protocol sent the GTSM policy.
Issue 07 (2014-07-30)

548

Log Reference
56 LSPM
Parameter Name
Parameter Meaning
Flag
Flag of the enable state.
Address
Indicates the peer address.
Possible Causes
Internal causes of system malfunctions.
Procedure
----End
56.15 LSPM/6/HASMOOTHBEGIN
Message
LSPM/6/HASMOOTHBEGIN:LSPM started smoothing at time [time]. (SmoothType=
[ULONG])
Description
LSPM HA smoothing was started.
Parameters
Parameter Name
Parameter Meaning
[time]
Indicates the time when the LSPM starts traffic smoothing.
SmoothType
Indicates the type of smoothing.
Possible Causes
Active/standby switchover.
Procedure
----End
56.16 LSPM/6/HASMOOTHEND
Issue 07 (2014-07-30)

549

Log Reference
56 LSPM
Message
LSPM/6/HASMOOTHEND:LSPM finished smoothing at time [time]. (SmoothType=
[ULONG])
Description
LSPM HA smoothing was finished.
Parameters
Parameter Name
Parameter Meaning
[time]
Indicates the time when the LSPM ends traffic smoothing.
SmoothType
Indicates the type of smoothing.
Possible Causes
Active/standby switchover.
Procedure
----End
56.17 LSPM/3/HASMOOTHFAIL
Message
LSPM/3/HASMOOTHFAIL:An error occurred when LSPM was processing smoothing.
(ErrorCode=[ULONG1], IngressLsrId=[IPADDR], SessionTunnelId=[ULONG2],
LocalLspId=[ULONG3], LspIndex=[ULONG4])
Description
LSPM smoothing failed. Four cases of the failure were as follows:
0: indicates the unknown error.
1: indicates that active LSP smoothing failed.
2: indicates that modifying LSP smoothing failed.
3: indicates that backing up LSP smoothing failed.
Issue 07 (2014-07-30)

550

Log Reference
56 LSPM
Parameters
ErrorCode
Indicates the errored code for smoothing failure.Four cases of the failure
are as follows:
l 0: indicates the unknown error.
l 1: indicates that active LSP smoothing failed.
l 2: indicates that modifying LSP smoothing failed.
l 3: indicates that backing up LSP smoothing failed.
IngressLsrId
Indicates the ID of the ingress LSR.
SessionTunnelId
Indicates the session tunnel ID of a tunnel.
LocalLspId
Indicates the local LSP ID of a tunnel.
LspIndex
Indicates the LSP index.
Possible Causes
An error occurred in active board backup or the backup failed.
Procedure
cause.
----End
56.18 LSPM/3/LSPMTEST
Message
LSPM/3/LSPMTEST: Notify resource info to RM failed.
Description
Failed to notify the resource information to RM.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
LSPM failed to notify the resource information to RM.
Issue 07 (2014-07-30)

551

Log Reference
56 LSPM
Procedure
Step 1 Check the interface between LSPM and RM.
----End
56.19 LSPM/6/NOTIFYCSPFDSTEEVT
Message
LSPM/6/NOTIFYCSPFDSTEEVT:Notified CSPF of TE-Class change event.
Description
Constraint Shortest Path First (CSPF) was notified when TE-Class changed.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
56.20 LSPM/6/NOTIFYLSPMDSTEEVT
Message
LSPM/6/NOTIFYLSPMDSTEEVT:Notified LSPM of TE-Class change event. (Event=
[STRING])
Description
Label Switched Path Management (LSPM) was notified when TE-Class changed.
Issue 07 (2014-07-30)

552

Log Reference
56 LSPM
Parameters
Parameter Name
Parameter Meaning
Event
Indicates the configuration event of TE-Class.
Possible Causes
Procedure
----End
56.21 LSPM/6/NOTIFYRSVPDSTEEVT
Message
LSPM/6/NOTIFYRSVPDSTEEVT:Notified RSVP of TE-Class change event. (Event=
[STRING])
Description
RSVP was notified when TE-Class changed.
Parameters
Parameter Name
Parameter Meaning
Event
Indicates the configuration event of TE-Class.
Possible Causes
Procedure
----End
56.22 LSPM/6/PREEMPTIONRESULT
Issue 07 (2014-07-30)

553

Log Reference
56 LSPM
Message
LSPM/6/PREEMPTIONRESULT:The number of CR-LSPs to be preempted is [crlsp-number].
These LSPs would be down.
Description
The number of CR-LSPs to be occupied was displayed.
Parameters
Parameter Name
Parameter Meaning
[crlsp-number]
Indicates the number of CR-LSPs to be occupied.
Possible Causes
The LSP of higher priority took precedence on resources over that of lower priority.
Procedure
----End
56.23 LSPM/3/PROCESSTNLMSGFAILED
Message
LSPM/3/PROCESSTNLMSGFAILED:Cannot process HA tunnel message. (TunnelName=
[STRING], EventType=[ULONG])
Description
Failed to process the HA tunnel message.
Parameters
Parameter Name
Parameter Meaning
TunnelName
Indicates the name of a tunnel.
EventType
Indicates the type of a tunnel event.
Possible Causes
Processing of the tunnel event received from the tunnel interface module failed.
Issue 07 (2014-07-30)

554

Log Reference
56 LSPM
Procedure
Step 1 Run the debugging mpls management process command to collect debugging information.
----End
56.24 LSPM/6/RECEIVEGRENDEVENT
Message
LSPM/6/RECEIVEGRENDEVENT:Receive GR end event from RM.
Description
The GR end event was received from the RM module.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The GR end event was received from the RM module.
Procedure
----End
56.25 LSPM/6/SENTBATCHBKUPOVERHA
Message
LSPM/6/SENTBATCHBKUPOVERHA:LSPM notified HA batch backup finished.
Description
LSPM notified HA that the batch backup was complete.
Issue 07 (2014-07-30)

555

Log Reference
56 LSPM
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The batch backup was started after the slave board was inserted. After the batch backup was
complete, LSPM notified HA.
Procedure
----End
56.26 LSPM/6/SENTSMOOTHFINISHHA
Message
LSPM/6/SENTSMOOTHFINISHHA:LSPM notified HA SMOOTH finished.
Description
LSPM notified HA that the data smoothing was complete.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Data smoothing was done after the active/standby switchover. When the data smoothing was
complete, LSPM notified HA.
Procedure
----End
56.27 LSPM/6/SLOTPLUGINOUTEVENT
Issue 07 (2014-07-30)

556

Log Reference
56 LSPM
Message
LSPM/6/SLOTPLUGINOUTEVENT:Received slot event [event-id] from slot [slot-id].
Description
The event that the hot swap changed on the interface board was received.
Parameters
Parameter Name
Parameter Meaning
[event-id]
Indicates the type of the hot swap event on the interface.
[slot-id]
Indicates the number of the slot where the interface board resides.
Possible Causes
The event that the hot swap changed on the interface board was received.
Procedure
----End
56.28 LSPM/4/SWITCH_TO_PT_FAIL
Message
LSPM/4/SWITCH_TO_PT_FAIL:Can not switch to protection tunnel, the protection tunnel is
unavailable.
Description
Failed to switch the working tunnel to the protection tunnel because the protection tunnel was
unavailable.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Switching the working tunnel to the protection tunnel cannot be performed because the
protection tunnel was unavailable.
Issue 07 (2014-07-30)

557

Log Reference
56 LSPM
Procedure
Step 1 Configure the protection group and perform tunnel switching.
Step 2 Check the status of the protection tunnel.
----End
56.29 LSPM/4/SWITCH_TO_PTUNN
Message
LSPM/4/SWITCH_TO_PTUNN:Switch to protection tunnel. (WorkTunnel is [Index])
Description
The working tunnel was switched to the protection tunnel.
Parameters
Parameter Name
Parameter Meaning
[Index]
indicates the index of a working tunnel.
Possible Causes
The working tunnel was switched to the protection tunnel.
Procedure
----End
56.30 LSPM/4/SWITCH_TO_WT_FAIL
Message
LSPM/4/SWITCH_TO_WT_FAIL:Can not switch to work tunnel, the work tunnel is
unavailable.
Description
Failed to switch the protection tunnel to the working tunnel because the working tunnel was
unavailable.
Issue 07 (2014-07-30)

558

Log Reference
56 LSPM
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Switching the protection tunnel to the working tunnel cannot be performed because the working
tunnel was unavailable.
Procedure
Step 1 Configure the protection group and perform tunnel switching.
Step 2 Check the status of the working tunnel.
----End
56.31 LSPM/4/SWITCH_TO_WTUNN
Message
LSPM/4/SWITCH_TO_WTUNN:Switch to work tunnel. (WorkTunnel is [Index])
Description
The protection tunnel was switched to the working tunnel.
Parameters
Parameter Name
Parameter Meaning
[Index]
Possible Causes
The protection tunnel was switched to the working tunnel.
Procedure
----End
56.32 LSPM/4/TRAPSUPPRESS
Issue 07 (2014-07-30)

559

Log Reference
56 LSPM
Message
LSPM/4/TRAPSUPPRESS:In the latest [value] seconds, the number of times that the trap of
[feature-name] is suppressed is [times].
Description
Show the number of times that the trap is suppressed in the latest [value] seconds.
Parameters
Parameter Name
Parameter Meaning
[value]
Indicates the value of time in second.
[feature-name]
Indicates the name of feature which the trap belongs to.
[times]
Indicates the number of times that the trap is suppressed.
Possible Causes
This log message indicates a normal situation.
Procedure
----End
56.33 LSPM/6/TRIGGERRSVPCOUNT
Message
LSPM/6/TRIGGERRSVPCOUNT:The number of times that the LSPM triggered RSVP during
GR was [time].
Description
The number of times that LSPM triggered RSVP during GR.
Parameters
Parameter Name
Parameter Meaning
[time]
The number of times that the LSPM triggered the RSVP during GR.
Possible Causes
Issue 07 (2014-07-30)

560

Log Reference
56 LSPM
Procedure
----End
56.34 LSPM/3/TRIGGERRSVPFAIL
Message
LSPM/3/TRIGGERRSVPFAIL:Failed to trigger RSVP during GR. (ErrorCode=[ULONG],
SessionTunnelId=[ULONG], LocalLspId=[ULONG], LspIndex=[ULONG])
Description
Failed to trigger RSVP during GR. Four cases of failure are as follows:
1: indicates that the corresponding LSP cannot be found.
2: indicates that the corresponding explicit path cannot be found.
3: indicates that the sending of the message failed.
Parameters
ErrorCode
Indicates the error code for failing in triggering the RSVP. The types of
error codes are as follows:
1: indicates that the corresponding LSP cannot be found.
2: indicates that the corresponding explicit path cannot be found.
3: indicates that the sending of the message is failed.
SessionTunnelId
Indicates the session tunnel ID of a tunnel.
LocalLspId
Indicates the local LSP ID of a tunnel.
LspIndex
Indicates the LSP index.
Possible Causes
An error occurred in active board backup or the backup failed.
Issue 07 (2014-07-30)

561

Log Reference
56 LSPM
Procedure
cause.
----End
56.35 LSPM/6/TWOLABELFORSAMEFEC
Message
LSPM/6/TWOLABELFORSAMEFEC:Found different in-labels for the same FEC in LDP GR
process. (NewLabel=[ULONG], OldLabel=[ULONG])
Description
Found different in-labels for the same FEC in LDP GR process.
Parameters
Parameter Name
Parameter Meaning
NewLabel
Indicates the first label.
OldLabel
Indicates the second label.
Possible Causes
There are different in-labels for the same FEC.
Procedure
Step 1 Check the data of LSPM module to get the in-label information for the FEC.
----End
Issue 07 (2014-07-30)

562

Log Reference
57 MCAST
57
MCAST
About This Chapter

57.1 MCAST/3/ENTRY
57.2 MCAST/6/FIB
57.3 MCAST/3/PORT
57.4 MCAST/6/SUPPRESS_LEAVE
57.5 MCAST/6/SUPPRESS_REPORT
57.6 MCAST/6/WRITE_QUEUE
Issue 07 (2014-07-30)

563

Log Reference
57 MCAST
57.1 MCAST/3/ENTRY
Message
MCAST/3/ENTRY:Failed to set forwarding table(group ip= [STRING],group mac=
[STRING],source ip=[STRING] in-VlanID=[ULONG]) in switch board(SLOTID=
[ULONG]) .The operation is [STRING] and the result is [ULONG].
Description
Sending an entry to a chip fails.
Parameters
Parameter Name
Parameter Meaning
SlotID
ID of slot where an interface board is inserted
Group-IP
Group IP address
Group-MAC
Group MAC address
In-VlanID
In VLAN ID
[STRING]
Adding or failure
Source-IP
Source IP address
[ULONG]
Operation result
Possible Causes
Adding an entry to a chip or deleting an entry entries from a chip fails due to certain reasons,
for example, a delete command is received but the entry does not exist in the chip.
Procedure
Step 1 Run the display igmp-snooping port-info and display l2-multicast forwarding-table
commands to view entries. Check whether the number of entries exceeds the upper limit.
Step 2 If yes, this log is normal and does not need to be processed.
Step 3 Otherwise, contact Huawei technical support engineers.
----End
57.2 MCAST/6/FIB
Message
MCAST/6/FIB:there is no flow in the fib entry(group ip= [STRING],source ip=[STRING] inVlanID=[ULONG]).
Issue 07 (2014-07-30)

564

Log Reference
57 MCAST
Description
There is no data flow corresponding to the FIB entry.
Parameters
Parameter Name
Parameter Meaning
group ip
Indicates the group IP address.
in-VlanID
Indicates the inbound VLAN ID.
[STRING]
Indicates the operation type.
source ip
[ULONG]
Indicates the operation result.
Possible Causes
Multicast services are interrupted. As a result, there is no data flow corresponding to the FIB
entry.
Procedure
Step 1 Run the display igmp-snooping port-info and display l2-multicast forwarding-table
commands to check multicast entries.
----End
57.3 MCAST/3/PORT
Message
MCAST/3/PORT:Failed to set FIB(group ip= [STRING],group mac=[STRING],source ip =
[STRING],in-VlanID = [ULONG]) outgoing port(port-index = [ULONG],out-VlanID =
[ULONG]) in switch board(SLOTID = [ULONG]).The operation is [STRING] and the result is
[ULONG].
Description
Sending an entry from the egress to a chip fails.
Parameters
Parameter Name
Parameter Meaning
SLOTID
ID of slot where an interface board is inserted
group ip
group IP address
Issue 07 (2014-07-30)

565

Log Reference
57 MCAST
Parameter Name
Parameter Meaning
group mac
group MAC address
in-VlanID
in VLAN ID
[STRING]
operation type
port-index
index of port
out-VlanID
out VLAN ID
source ip
source IP address
[ULONG]
operation result
Possible Causes
An invalid port is added, or the layer-3 interface out of the VLAN does not exist.
Procedure
Step 1 Run display igmp-snooping port-info and display l2-multicast forwarding-table commands to
view entries. Check whether the number of entries exceeds the upper limit.
Step 2 If yes, this log is normal and does not need to be processed.
Step 3 Otherwise, contact Huawei technical support engineers.
----End
57.4 MCAST/6/SUPPRESS_LEAVE
Message
MCAST/6/SUPPRESS_LEAVE:Suppress leave packet. (VlanID=[ULONG], GroupIp=
[IPADDR], ReceiveInterface=[STRING])
Description
Leave messages are suppressed on an interface.
Parameters
Parameter Name
Parameter Meaning
VlanID
Indicates a VLAN ID.
Group ip
Indicates a multicast group address.
ReceiveInterface
Indicates an interface that receives Leave messages.
Issue 07 (2014-07-30)

566

Log Reference
57 MCAST
Possible Causes
Leave message suppression is enabled by default after Layer 2 multicast is configured. The
device sends only one Leave message for a group within 10s.
Procedure
Step 1 Leave message suppression does not affect services on the device. To disable Leave message
suppression, run the igmp-snooping suppress-time suppress-time command to set the
suppression time to 0.
Step 2 Check whether the log is still recorded.
Step 3 If the log is still recorded, contact Huawei technical personnel.
----End
57.5 MCAST/6/SUPPRESS_REPORT
Message
MCAST/6/SUPPRESS_REPORT:Suppress report packet. (VlanID=[ULONG], Group ip=
[IPADDR], ReceiveInterface=[STRING]).
Description
Report messages are suppressed on an interface.
Parameters
Parameter Name
Parameter Meaning
VlanID
Indicates a VLAN ID.
Group ip
Indicates a multicast group address.
ReceiveInterface
Indicates the interface that receives Report messages.
Possible Causes
Report message suppression is enabled by default after Layer 2 multicast is configured. The
device sends only one Report message for a group within 10s.
Procedure
Step 1 Report message suppression does not affect services on the device. To disable Report message
suppression, run the igmp-snooping suppress-time suppress-time command to set the
suppression time to 0.
Issue 07 (2014-07-30)

567

Log Reference
57 MCAST

----End
57.6 MCAST/6/WRITE_QUEUE
Message
MCAST/6/WRITE_QUEUE:Failed to write message queue! (QueueId=[ULONG])
Description
Failed to write data to the message queue.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the queue ID.
Possible Causes
The message queue is full.
Procedure
----End
Issue 07 (2014-07-30)

568

Log Reference
58 MFIB
58
MFIB
About This Chapter

58.1 MFIB/4/CNT_OVER_MAX
58.2 MFIB/4/DOWNNUM_EXCEED_RESTORE
58.3 MFIB/4/ENTRY_EXCEED_RESTORE
58.4 MFIB/4/ENTRY_OVER_MAX
58.5 MFIB/4/FREE_MID_TO_MAX
58.6 MFIB/4/GR_END
58.7 MFIB/4/GR_START
58.8 MFIB/4/INVALID_OIF_NUM
58.9 MFIB/4/REACH_TO_MAX
58.10 MFIB/4/REACH_TO_MAX_ENTRY_IO
58.11 MFIB/4/REACH_TO_MAX_ENTRY_MAIN
58.12 MFIB/4/REACH_TO_MAX_LIMIT
58.13 MFIB/4/SET_LMT_LESS_CRRNT
Issue 07 (2014-07-30)

569

Log Reference
58 MFIB
58.1 MFIB/4/CNT_OVER_MAX
Message
MFIB/4/CNT_OVER_MAX:The muticast forword table counter [current-value] exceeds the
max valid value [max-value]. It should be [updated-value]. (Protocol=[STRING], Vpn=
[STRING], FileLine=[STRING][STRING])
Description
The counter of the multicast forwarding table reached the maximum count, which should be
updated.
Parameters
[current-value]
Indicates the current count of the counter.
[max-value]
Indicates the maximum count of the counter.
[updated-value]
Indicates the value to be updated.
Protocol
Indicates the flag of IPv4 or IPv6. The values are Protocol=IPv4 and
Protocol=IPv6.
Vpn
FileLine
message.
Possible Causes
The counter of the multicast forwarding table reached the maximum count.
Procedure
l
Run the display diagnostic-information command to save the command output, and
contact the Huawei technical personnel.
----End
58.2 MFIB/4/DOWNNUM_EXCEED_RESTORE
Message
MFIB/4/DOWNNUM_EXCEED_RESTORE:The number of downstream interfaces in the
entry ([source-address], [group-address])'s downstream list falls below the set limit. The limit
on the number of downstream interfaces is [OIF_LIMIT]. (Protocol=[STRING], Vpn=
Issue 07 (2014-07-30)

570

Log Reference
58 MFIB
Description
The number of downstream interfaces in an MFIB entry fell below the set limit.
Parameters
[source-address]
Source address
[group-address]
Group address
[OIF_LIMIT]
Limit on the number of downstream interfaces in an MFIB entry.
Protocol
Protocol=IPv6.
Vpn
VPN name
FileLine
Name of the source code file and the line number of this log message
Possible Causes
The number of downstream interfaces in an MFIB entry fell below the set limit.
Procedure
l
----End
58.3 MFIB/4/ENTRY_EXCEED_RESTORE
Message
MFIB/4/ENTRY_EXCEED_RESTORE:The number of entries falls below the limit. (Protocol=
[STRING], Vpn=[STRING], FileLine=[STRING][STRING])
Description
The number of MFIB entries fell below the limit.
Parameters
Protocol
Protocol=IPv6.
Vpn
VPN name
FileLine
Issue 07 (2014-07-30)

571

Log Reference
58 MFIB
Possible Causes
The number of MFIB entries fell below the limit.
Procedure
l
----End
58.4 MFIB/4/ENTRY_OVER_MAX
Message
MFIB/4/ENTRY_OVER_MAX:Total number of route entry for all VPN [current-entry] has
reached or beyond the limit: [limit-entry] on IO board. (Protocol=[STRING], Vpn=[STRING],
FileLine=[STRING][STRING])
Description
The route entries of all VPN instances on the interface reached the upper limit.
Parameters
[current-entry]
Indicates the number of current route entries.
[limit-entry]
Indicates the maximum number of route entries supported by the device.
Protocol
Indicates the flag of IPv4 or IPv6. The values are protocol=IPv4 and
Protocol=IPv6.
Vpn
FileLine
message.
Possible Causes
The number of route entries reached the maximum value.
Procedure
l
----End
58.5 MFIB/4/FREE_MID_TO_MAX
Issue 07 (2014-07-30)

572

Log Reference
58 MFIB
Message
MFIB/4/FREE_MID_TO_MAX: MID allocation fails because the number of MIDs allocated
to instances [current-number] has reached the upper limit: [max-number]. (Protocol=[STRING],
Vpn=[STRING], FileLine=[STRING][STRING])
Description
Failed to allocate an MID because the number of allocated MIDs of all instances reached the
upper limit.
Parameters
Parameter Name
Parameter Meaning
[current-number]
Indicates the number of current allocated MIDs.
[max-number]
Indicates the permitted maximum number of allocated MIDs.
Protocol
Indicates the flag of IPv4 or IPv6.
Vpn
FileLine
Indicates the name of the source code file and the line number.
Possible Causes
The number of allocated MIDs of all instances reached the upper limit.
Procedure
----End
58.6 MFIB/4/GR_END
Message
MFIB/4/GR_END:GR end ([STRING]). (Protocol=[STRING], Vpn=[STRING], FileLine=
[STRING][STRING])
Description
The MFIB enters the GR final state.
Issue 07 (2014-07-30)

573

Log Reference
58 MFIB
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the identification of VPN.
Protocol
Vpn
FileLine
Indicates the name of the source code file and the line number.
Possible Causes
GR is complete after the master-slave switchover.
Procedure
l
Run the display diagnostic-information command, save the command output, and then
contact Huawei technical support personnel.
----End
58.7 MFIB/4/GR_START
Message
MFIB/4/GR_START:GR start ([STRING]). (Protocol=[STRING], Vpn=[STRING], FileLine=
[STRING][STRING])
Description
The MFIB enters the GR initialization state.
Parameters
[STRING]
Indicates the identification of VPN.
Protocol
Vpn
FileLine
message.
Possible Causes
GR begins after the master-slave switchover.
Issue 07 (2014-07-30)

574

Log Reference
58 MFIB
Procedure
l
----End
58.8 MFIB/4/INVALID_OIF_NUM
Message
MFIB/4/INVALID_OIF_NUM:The entry ([source-address], [group-address])'s OIF num
([current-oif-number]) exceeds downstream limit([limit-oif-number]).(Protocol=[STRING],
Vpn=[STRING], FileLine=[STRING][STRING])
Description
The total number of the outgoing interfaces of the current entries reached the maximum number
allowed by the device.
Parameters
Parameter Name
Parameter Meaning
[source-address]
[group-address]
[current-oif-number] Indicates the total number of the outgoing interfaces of the current
entries.
[limit-oif-number]
Indicates the maximum number of interfaces supported by the device.
Protocol
Vpn
FileLine
log message.
Possible Causes
The total number of the outgoing interfaces of the current entry reached the maximum number
allowed by the device.
Procedure
l
----End
Issue 07 (2014-07-30)

575

Log Reference
58 MFIB
58.9 MFIB/4/REACH_TO_MAX
Message
MFIB/4/REACH_TO_MAX:Current route number [route-number] reached the route limit:
[route-limit]. (Protocol=[STRING], Vpn=[STRING], FileLine=[STRING][STRING])
Description
The current routing entries reached the maximum value supported by the device.
Parameters
[route-number]
Number of routing entries.
[route-limit]
Maximum number of routing entries supported by the device.
Protocol
Vpn
VPN name.
FileLine
Name of the source code file and the line number of this log message.
Possible Causes
The current routing entries reached the maximum value supported by the device.
Procedure
l
----End
58.10 MFIB/4/REACH_TO_MAX_ENTRY_IO
Message
MFIB/4/REACH_TO_MAX_ENTRY_IO:The number of multicast forwarding entries reached
the upper threshold. The number of existing entries in the instance [current-instance-entry], the
maximum number of entries in the instance [current-instance-limit], the number of existing
entries on a device [current-device-entry], the maximum number of entries on a device [currentdevice-limit], resources consumed by forwarding entries [entry-resource], maximum resources
[max-resource], remaining resoruces [remain-resource]. (Protocol=[STRING], Vpn=
Issue 07 (2014-07-30)

576

Log Reference
58 MFIB
Description
The number of multicast forwarding entries on the interface board reached the maximum limit.
Parameters
Parameter Name
Parameter Meaning
[current-instance-entry] Number of multicast forwarding entries of the instance.

[current-instance-limit] Maximum number of multicast forwarding entries of the instance.
[current-device-entry]
Number of multicast forwarding entries of the device.
[current-device-limit]
Maximum number of multicast forwarding entries of the device.
[entry-resource]
Resources occupied by the forwarding entries.
[max-resource]
Maximum resources.
[remain-resource]
Remaining resources.
Protocol
Protocol=IPv6.
Vpn
VPN instance name.
FileLine
Possible Causes
The number of multicast forwarding entries on the interface board reached the maximum limit.
Procedure
l
----End
58.11 MFIB/4/REACH_TO_MAX_ENTRY_MAIN
Message
MFIB/4/REACH_TO_MAX_ENTRY_MAIN:The number of multicast forwarding entries
reached the upper threshold. The number of existing entries in the instance [current-instanceentry], the maximum number of entries in the instance [current-instance-limit], the number of
existing entries on a device [current-device-entry], the maximum number of entries on a device
[current-device-limit]. (Protocol=[STRING], Vpn=[STRING], FileLine=[STRING]
[STRING])
Description
The number of multicast forwarding entries on the MPU reached the maximum limit.
Issue 07 (2014-07-30)

577

Log Reference
58 MFIB
Parameters
Parameter Name
Parameter Meaning
[current-instance-entry] Number of multicast forwarding entries of the instance.

[current-instance-limit] Maximum number of multicast forwarding entries of the instance.
[current-device-entry]
Number of multicast forwarding entries of the device.
[current-device-limit]
Maximum number of multicast forwarding entries of the device.
Protocol
Protocol=IPv6.
Vpn
VPN instance name.
FileLine
Possible Causes
The number of multicast forwarding entries on the MPU reached the maximum limit.
Procedure
l
----End
58.12 MFIB/4/REACH_TO_MAX_LIMIT
Message
MFIB/4/REACH_TO_MAX_LIMIT:Can not add entry ([source-address], [group-address]).
Total number of route entry [current-route-number] for all VPN has reached or beyond the limit:
[limit-route-number]. (Protocol=[STRING], Vpn=[STRING], FileLine=[STRING][STRING])
Description
The current route entries reached the maximum value supported by the device.
Parameters
Parameter Name
Parameter Meaning
[source-address]
[group-address]
Indicates the address of a group.
[current-route-number] Indicates the total number of current routes.

[limit-route-number]
Issue 07 (2014-07-30)
Indicates the maximum routes supported by the device.

578

Log Reference
58 MFIB
Parameter Name
Parameter Meaning
Protocol
Protocol=IPv6.
Vpn
FileLine
log message.
Possible Causes
The current route entries reached the maximum value supported by the device.
Procedure
l
----End
58.13 MFIB/4/SET_LMT_LESS_CRRNT
Message
MFIB/4/SET_LMT_LESS_CRRNT:The new setting route limit [new-max-entry] is less than
current entry number [current-entry]. This change will take effect after resetting multicast
forwarding-table. (Protocol=[STRING], Vpn=[STRING], FileLine=[STRING][STRING])
Description
The newly set the maximum number of entries was smaller than the number of current entries.
The new maximum value will take effect after the multicast forwarding table is cleared.
Parameters
[new-max-entry]
Indicates the maximum number of entries in the multicast forwarding

table.
[current-entry]
Indicates the number of current entries in the multicast forwarding table.
Protocol
Protocol=IPv6.
Vpn
FileLine
message.
Possible Causes
The newly set the maximum number of entries was smaller than the number of current entries.
Issue 07 (2014-07-30)

579

Log Reference
58 MFIB
Procedure
l
Check that the newly configured maximum number of entries is correct.
----End
Issue 07 (2014-07-30)

580

Log Reference
59 MLD
59
MLD
About This Chapter

59.1 MLD/6/ERR_VER_PKT1
59.3 MLD/6/GLB_ENTRY
59.4 MLD/6/GLB_LIMIT
59.5 MLD/6/IF_ENTRY
59.6 MLD/6/IF_LIMIT
59.7 MLD/6/INST_ENTRY
59.8 MLD/6/INST_LIMIT
59.9 MLD/4/REG_ACL_F
59.10 MLD/4/SET_MLD_INTPLC_FAIL
Issue 07 (2014-07-30)

581

Log Reference
59 MLD
Message
MLD/6/ERR_VER_PKT1:In VPN instance \"[vpn-instance-name]\", ignored the Query
received with the version of MLDv[version] on the MLDv1 interface [interface-name]
([interface-address]). (FlCode=[STRING][ULONG])
Description
An MLDv2 Query message was received on the interface enabled with MLDv1.
Parameters
Parameter Name
Parameter Meaning

[version]
Indicates the version of a Query message.
[interface-name]
[interface-address]
FlCode
log message.
Possible Causes
Procedure
l
----End
Message
MLD/6/ERR_VER_PKT2:In VPN instance \"[vpn-instance-name]\", ignored the Query
received with the version of MLDv[version] on the MLDv2 interface [interface-name]
([interface-address]). (FlCode=[STRING][ULONG])
Description
Issue 07 (2014-07-30)

582

Log Reference
59 MLD
Parameters
Parameter Name
Parameter Meaning

[version]
Indicates the version of a Query message.
[interface-name]
[interface-address]
FlCode
log message.
Possible Causes
Procedure
l
----End
59.3 MLD/6/GLB_ENTRY
Message
MLD/6/GLB_ENTRY:In VPN instance \"[vpn-instance-name]\", MLD discarded the received
report ([source-address], [group-address]) because the number of MLD group memberships in
all VPN instances reached the limit. The current statistical number of MLD group memberships
Description
The received MLD Report message was discarded because the number of MLD entries in all
instances reached the limit.
Parameters
Parameter Name
Parameter Meaning

[source-address]
[group-address]
Indicates the upper limit of the number of MLD entries.
FlCode
log message.
Issue 07 (2014-07-30)

583

Log Reference
59 MLD
Possible Causes
In the case that the MLD limit for all instances was set, when the total number of MLD entries
in all instances reached the limit, the received MLD Report message was discarded.
Procedure
l
----End
59.4 MLD/6/GLB_LIMIT
Message
MLD/6/GLB_LIMIT:In all VPN instances, the number of existed MLD group memberships
exceeded the limit. (FlCode=[STRING][ULONG])
Description
The total number of MLD entries in all current instances exceeded the configured limit.
Parameters
FlCode
message.
Possible Causes
In the case that all instances were configured with the MLD limit, this log message was generated
when the total number of MLD entries in all instances exceeded the limit.
Procedure
l
----End
59.5 MLD/6/IF_ENTRY
Message
MLD/6/IF_ENTRY:In VPN instance \"[vpn-instance-name]\", MLD discarded the received
report ([source-address], [group-address]) because the number of MLD group memberships
reached the limit on the interface [interface-name]. The current statistical number of MLD group
memberships is [statistical-number]. (FlCode=[STRING][ULONG])
Issue 07 (2014-07-30)

584

Log Reference
59 MLD
Description
The MLD Report message received from the interface was discarded because the number of
MLD entries on the interface reached the upper limit.
Parameters
Parameter Name
Parameter Meaning

[source-address]
[group-address]
[interface-name]
FlCode
log message.
Possible Causes
In the case that the current interface was configured with the MLD limit, when the number of
MLD entries on the interface reached the limit, the received MLD Report message was discarded.
Procedure
l
----End
59.6 MLD/6/IF_LIMIT
Message
MLD/6/IF_LIMIT:In VPN instance \"[vpn-instance-name]\", the number of existed MLD group
memberships exceeded the limit on this interface. (FlCode=[STRING][ULONG])
Description
The number of MLD entries on the current interface exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning

FlCode
Issue 07 (2014-07-30)
log message.
585

Log Reference
59 MLD
Possible Causes
In the case that the current interface was configured with the MLD limit, the number of MLD
entries on the interface exceeded the limit.
Procedure
l
----End
59.7 MLD/6/INST_ENTRY
Message
MLD/6/INST_ENTRY:In VPN instance \"[vpn-instance-name]\", MLD discarded the received
report ([source-address], [group-address]) because the number of MLD group memberships in
this VPN instance reached the limit. The current statistical number of MLD group memberships
Description
The received MLD Report message was discarded because the number of MLD entries in the
instance reached the upper limit.
Parameters
Parameter Name
Parameter Meaning

[source-address]
[group-address]
FlCode
log message.
Possible Causes
In the case that the current instance was configured with the MLD limit, when the number of
MLD entries in the instance reached the limit, the received MLD Report message was discarded.
Procedure
l
----End
Issue 07 (2014-07-30)

586

Log Reference
59 MLD
59.8 MLD/6/INST_LIMIT
Message
MLD/6/INST_LIMIT:In VPN instance \"[vpn-instance-name]\", the number of existed MLD
group memberships exceeded the limit. (FlCode=[STRING][ULONG])
Description
The number of MLD entries in the current instance exceeded the configured limit.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
In the case that the current instance was configured with the MLD limit, the number of MLD
entries in the current instance exceeded the limit.
Procedure
l
----End
59.9 MLD/4/REG_ACL_F
Message
MLD/4/REG_ACL_F:In VPN instance \"[vpn-instance-name]\", registering ACL update
callback functions failed. (FlCode=[STRING][ULONG])
Description
MLD failed to register the ACL update callback function with the MRM.
Issue 07 (2014-07-30)

587

Log Reference
59 MLD
Parameters
Parameter Name
Parameter Meaning

FlCode
indicates the name of the source code file and the line number of this
log message.
Possible Causes
Failed to call the MRM interface to add the ACL name to the MRM.
Procedure
Step 1 Reconfigure the commands for Named ACLs.
----End
59.10 MLD/4/SET_MLD_INTPLC_FAIL
Message
MLD/4/SET_MLD_INTPLC_FAIL:In VPN instance \"[vpn-instance-name]\", failed to set the
MLD application policy for interface [interface-name]. (FlCode=[STRING][ULONG])
Description
Failed to set the MLD application policy on the interface.
Parameters
Parameter Name
Parameter Meaning

[interface-name]
FlCode
log message.
Possible Causes
Failed to deliver the interface application policy when MLD was configured on the interface.
Procedure
Step 1 Run the undo mld enable command and reconfigure MLD on the interface.
Issue 07 (2014-07-30)

588

Log Reference
59 MLD
Step 2 If this log message is generated after each reconfiguration, contact Huawei technical support
personnel.
----End
Issue 07 (2014-07-30)

589

Log Reference
60 MPLS
60
MPLS
About This Chapter

60.1 MPLS/5/VSI_ADD_DENYACL
60.2 MPLS/5/VSI_ADD_MCTBL
60.3 MPLS/5/VSI_ADD_VFP
60.4 MPLS/5/VSI_ADD_VPTBL
60.5 MPLS/5/VSI_GET_MCIDX
Issue 07 (2014-07-30)

590

Log Reference
60 MPLS
60.1 MPLS/5/VSI_ADD_DENYACL
Message
MPLS/5/VSI_ADD_DENYACL: Add VSI deny ACL failed (SlotID=[ULONG]).
Description
The device failed to deliver the ACL that rejects VSI packets.
Parameters
Parameter Name
Parameter Meaning
SlotID
Indicates the slot ID.
Possible Causes
ACL resources are exhausted.
Procedure
Step 1 Run the display acl resource command to check whether the ACL resources are exhausted.
Step 2 If they are exhausted, delete the unneeded ACL entries under the guidance of Huawei technical
support personnel.
----End
60.2 MPLS/5/VSI_ADD_MCTBL
Message
MPLS/5/VSI_ADD_MCTBL: Add multicast table failed when create forwarding entry for vsi
[ULONG].
Description
The device failed to deliver multicast entries.
Parameters
[ULONG]
Issue 07 (2014-07-30)
Indicates the VSI index for which the multicast entry failed to be
delivered.
591

Log Reference
60 MPLS
Possible Causes
The multicast (IPMC) entry resources are exhausted.
Procedure
----End
60.3 MPLS/5/VSI_ADD_VFP
Message
MPLS/5/VSI_ADD_VFP: Add VFP Entry failed (SlotID=[ULONG]).
Description
The device failed to add VFP entries.
Parameters
SlotID
Indicates the numbers of the card and device where resources are
exhausted.
Possible Causes
1. VFP entry resources are exhausted.
2. The operation of adding the VFP entry is incorrect.
Procedure
Step 1 Run the display acl resource command to check usage of VLAN-ACL (VFP) resources.
Step 2 If the VFP entry resources are exhausted, delete the unneeded entries and reconfigure the VSI.
Step 3 If the VFP entry resources are not exhausted, collect information and contact Huawei technical
personnel.
----End
60.4 MPLS/5/VSI_ADD_VPTBL
Message
MPLS/5/VSI_ADD_VPTBL: Add source_vp table failed when create forwarding entry for
l2vpn [ULONG].
Issue 07 (2014-07-30)

592

Log Reference
60 MPLS
Description
The device failed to deliver the VP index.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the VP index.
Possible Causes
The number of VP indexes exceeds the maximum number of VPs supported by the card.
Procedure
----End
60.5 MPLS/5/VSI_GET_MCIDX
Message
MPLS/5/VSI_GET_MCIDX: Get multicast index failed when create forwarding entry for vsi
[STRING].
Description
The device failed to obtain the multicast index when delivering VSI forwarding entries.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the name of a VSI.
Possible Causes
When creating a VSI, the device needs to obtain the multicast index to create a multicast entry.
If the multicast entry resources are exhausted, the device cannot obtain the multicast index
Procedure
Step 1 Check deployment of multicast service and VSI service on the device, and delete unneeded
multicast entry resources. If an error already occurs in a VSI, recreate the VSI.
----End
Issue 07 (2014-07-30)

593

Log Reference
61 MRM
61
MRM
About This Chapter

61.1 MRM/3/BACKUPSOCKET_E
61.2 MRM/3/BATCHSOCKET_E
61.3 MRM/3/CHECKSOCKET_E
61.4 MRM/6/DOWNNUM_EXCEED_LIMIT
61.5 MRM/3/GETSOCKET_E
61.6 MRM/3/MIGP_NOTEXIST_FAIL
61.7 MRM/3/SEARCH_MIGP_FAIL
61.8 MRM/2/VLINKID_CHG
61.9 MRM/6/VRFLIST_LIMIT
Issue 07 (2014-07-30)

594

Log Reference
61 MRM
61.1 MRM/3/BACKUPSOCKET_E
Message
MRM/3/BACKUPSOCKET_E:In VPN instance \"[vpn-instance-name]\", MRM failed to
backup [protocol-name] socket ID [socket-id]. The error code was [error-code].(FlCode=
[STRING][ULONG])
Description
The MRM module on the main control board failed to back up the socket ID.
Parameters
Parameter Name
Parameter Meaning

[protocol-name]
Indicates the name of the protocol. The value can be:

l GMP
l PIM
l MRM PUBLIC
[socket-id]
[error-code]
Indicates the error code. The value can be:

l 0: The value is successfully returned.
l 1: The main control board in use is not the master one.
l 2: The slave main control board does not exist.
l 3: Fail to allocate memory.
l 4: Fail to write data to the buffer.
l 5: Fail to access data from the buffer.
l 6: Fail to send messages.
l 7: The backup is canceled
FlCode
log message.
Possible Causes
1:
Communication fails, and the socket ID cannot be backed up normally.
2:
Programs or cooperative programs are processed abnormally.
Issue 07 (2014-07-30)

595

Log Reference
61 MRM
Procedure
Step 1 Restart the slave board.
Step 2 Run the undo multicast routing-enable command or the undo multicast ipv6 routingenable command to delete multicast configurations, and then reconfigure related multicast
commands.
----End
61.2 MRM/3/BATCHSOCKET_E
Message
MRM/3/BATCHSOCKET_E:MRM failed to backup socket ID in batches. The error code was
[error-code]. (FlCode=[STRING][ULONG])
Description
The MRM module on the main control board failed to back up the socket ID in batches.
Parameters
[error-code]

l 0: The value is successfully returned.
l 1: The main control board in use is not the master one.
l 2: The slave main control board does not exist.
l 4: Fail to write data to the buffer.
l 5: Fail to access data from the buffer.
l 6: Fail to send messages.
l 7: The backup is canceled
FlCode
message.
Possible Causes
1:
Communication fails, and the socket ID cannot be backed up normally.
2:
Programs or cooperative programs are processed abnormally.
Issue 07 (2014-07-30)

596

Log Reference
61 MRM
Procedure
commands.
----End
61.3 MRM/3/CHECKSOCKET_E
Message
MRM/3/CHECKSOCKET_E:In VPN instance \"[vpn-instance-name]\", MRM failed to check
socket ID [protocol-name]. The error code was [error-code]. (FlCode=[STRING][ULONG])
Description
The MRM module on the slave board failed to check the socket ID.
Parameters
Parameter Name
Parameter Meaning

[protocol-name]

l GMP
l PIM
l MRM PUBLIC
[error-code]

l 1048660: Fail to allocate sockets.
l 1048662: The task ID is invalid.
l 1048663: The instance number is invalid.
l -22: The parameter is invalid.
l -107: There is no TCB structure.
FlCode
log message.
Possible Causes
1:
Programs on the slave board or cooperative programs on the master or slave board are processed
abnormally, causing the socket ID to be incorrect.
Issue 07 (2014-07-30)

597

Log Reference
61 MRM
2:
The socket does not support the checking operation.
Procedure
commands.
----End
61.4 MRM/6/DOWNNUM_EXCEED_LIMIT
Message
MRM/6/DOWNNUM_EXCEED_LIMIT:In VPN instance \"[vpn-instance-name]\", the
number of the interfaces that deliver to MFIB exceeded the upper limit. The current number of
downstream interfaces that deliver to MFIB is [downstream-interface-number] and the upper
limit is [downstream-interface-limit]. [ignored-log-number]logs have been ignored.(FlCode=
[STRING][ULONG])
Description
The number of the outbound interfaces that are delivered to the MFIB exceeded the upper limit,
and the extra outbound interfaces were no longer delivered.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
[downstream-interface-number] Indicates the number of the outbound interfaces that have

already been delivered to the MFIB.
[downstream-interface-limit]
Indicates the number of the outbound interfaces that can be

delivered to the MFIB.
[ignored-log-number]
Indicates the number of logs that are ignored.
FlCode
Indicates the name of the source code file and the line
number of this log message.
Possible Causes
1:
When an entry is being created, the number of the outbound interfaces in this entry exceeds the
upper limit.
Issue 07 (2014-07-30)

598

Log Reference
61 MRM
2:
Outbound interfaces are continuously added to a certain entry, causing the number of the
outbound interfaces in this entry exceeds the upper limit.
Procedure
Step 1 When creating an entry, note that the number of the outbound interfaces in this entry does not
exceed the upper limit.
Step 2 Do not add more outbound interfaces to the same entry.
Step 3 Delete some outbound interfaces from the entry before adding new outbound interfaces.
----End
61.5 MRM/3/GETSOCKET_E
Message
MRM/3/GETSOCKET_E:In VPN instance \"[vpn-instance-name]\", MRM failed to get backup
socket ID of [protocol-name]. The error code was [error-code]. (FlCode=[STRING][ULONG])
Description
When creating a socket, the slave board failed to obtain the backup socket ID from the master
board.
Parameters
Parameter Name
Parameter Meaning

[protocol-name]

l GMP
l PIM
l MRM PUBLIC
[error-code]

l -1: The socket is invalid.
FlCode
log message.
Possible Causes
1:
Communication fails, causing the backup failure of the socket ID.
2:
Issue 07 (2014-07-30)

599

Log Reference
61 MRM
Programs on the slave board or cooperative programs on the master or slave board are processed
abnormally.
Procedure
commands.
----End
61.6 MRM/3/MIGP_NOTEXIST_FAIL
Message
MRM/3/MIGP_NOTEXIST_FAIL:In VPN instance \"[vpn-instance-name]\", the MIGP table
did not exist. (FlCode=[STRING][ULONG])
Description
The MIGP table does not exist.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
An error occurred when the system is initialized.
Procedure
Step 1 Record this log message, and then contact Huawei technical support personnel.
----End
61.7 MRM/3/SEARCH_MIGP_FAIL
Message
MRM/3/SEARCH_MIGP_FAIL:In VPN instance \"[vpn-instance-name]\", finding the
specified route [source-address] in the MIGP table failed. (FlCode=[STRING][ULONG])
Issue 07 (2014-07-30)

600

Log Reference
61 MRM
Description
Failed to find the specified route in the MIGP table.
Parameters
Parameter Name
Parameter Meaning

[source-address]
FlCode
log message.
Possible Causes
The MIGP table does not contain related entries or RM failed to search the MIGP table.
Procedure
----End
61.8 MRM/2/VLINKID_CHG
Message
MRM/2/VLINKID_CHG:In VPN instance \"[vpn-instance-name]\", virtual link index changed.
(Interface=[STRING], OldPeer=[STRING], NewPeer=[STRING], OldVlinkindex=[ULONG],
NewVlinkindex=[ULONG], Event=0x[STRING], FlCode=[STRING][ULONG])
Description
The index of the virtual link changed after the active/standby switchover.
Parameters
Parameter Name
Parameter Meaning

Interface
OldPeer
Indicates the IP address of the original peer.
NewPeer
Indicates the IP address of the new peer.
OldVlinkindex
Indicates the index of the virtual link before the active/standby

switchover.
Issue 07 (2014-07-30)

601

Log Reference
61 MRM
Parameter Name
Parameter Meaning
NewVlinkindex
Indicates the index of the virtual link after the active/standby

switchover.
Event
Indicates the event.
FlCode
log message.
Possible Causes
The index of the virtual link changed.
Procedure
l
----End
61.9 MRM/6/VRFLIST_LIMIT
Message
MRM/6/VRFLIST_LIMIT:In VPN instance [vpn-instance-name], the number of VRFs
delivered to the MFIB exceeded the upper limit. The current number of VRFs that deliver to
MFIB is [CurrentNumber] and the upper limit is [UpperLimit]. [IgnoreNumber] logs have been
ignored.(FlCode=[STRING][ULONG])
Description
The number of VPNs delivered by MRM to the MFIB exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning

[CurrentNumber]
Indicates the number of VPNs that has been delivered by MRM to the
MFIB.
[UpperLimit]
Indicates the upper limit on the number of VPNs that can be delivered
by MRM to the MFIB.
[IgnoreNumber]
Indicates the number of ignored logs.
FlCode
log message.
Issue 07 (2014-07-30)

602

Log Reference
61 MRM
Possible Causes
When the number of VPNs delivered by MRM to the MFIB exceeded the upper limit, MRM
did not deliver any VPN to the MFIB.
Procedure
Step 1 Check whether the total number of VPNs that can be delivered to the MFIB can be controlled
by purchasing license files. If so, increase the total number of VPNs that can be delivered to the
MFIB.
----End
Issue 07 (2014-07-30)

603

Log Reference
62 MSDP
62
MSDP
About This Chapter

62.1 MSDP/4/CHECK_SOCKET_FAIL
62.2 MSDP/6/PEER_NTFDWN
62.3 MSDP/6/PEER_TIMEOUT
62.4 MSDP/6/PEER_UP
62.5 MSDP/4/SA_LIMIT
62.6 MSDP/4/SET_MSDP_GLBPLC_FAIL
62.7 MSDP/4/SET_MSDP_GWLIST_FAIL
Issue 07 (2014-07-30)

604

Log Reference
62 MSDP
62.1 MSDP/4/CHECK_SOCKET_FAIL
Message
MSDP/4/CHECK_SOCKET_FAIL:In VPN instance \"[vpn-instance-name]\", failed to handle
msdp socket. The socket ID was [socket-id], the peer was [peer-address], the operation code was
[operation-code], the error code was [error-code].(FlCode=[STRING][ULONG])
Description
The backup MSDP socket information is incorrect or the configurations on the standby main
board are incorrect.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name] Name of a VPN instance

[socket-id]
Socket ID
[peer-address]
Peer address
[operation-code]
Operation code
l 1: The standby main board checks the socket.
l 2: The standby main board obtains the local port number and address
information.
l 3: The standby main board obtains the remote port number and
address information.
l 4: The MD5 option is set.
l 5: The KeyChain option is set.
l 6: The standby main board checks the boundary of the received
packet.
l 7: Attributes for socket backing up are set.
l 8: The application-ready option is set.
l 9: Asynchronization attributes are set.
[error-code]
Error code
FlCode
Possible Causes
The set socket option was incorrect.
Issue 07 (2014-07-30)

605

Log Reference
62 MSDP
Procedure
l
----End
62.2 MSDP/6/PEER_NTFDWN
Message
MSDP/6/PEER_NTFDWN:In VPN instance \"[vpn-instance-name]\", a session with the peer
[peer-address] was closed because a Notification TLV was received from this peer. (FlCode=
[STRING][ULONG])
Description
The session with the peer was closed because a Notification message was received from the
peer.
Parameters
Parameter Name
Parameter Meaning

[peer-address]
FlCode
log message.
Possible Causes
The session was closed.
Procedure
l
----End
62.3 MSDP/6/PEER_TIMEOUT
Message
MSDP/6/PEER_TIMEOUT:In VPN instance \"[vpn-instance-name]\", a session with peer
[peer-address] was closed because the peer holding time expired. (FlCode=[STRING]
[ULONG])
Issue 07 (2014-07-30)

606

Log Reference
62 MSDP
Description
The session with the peer was closed because the connection with the peer timed out.
Parameters
Parameter Name
Parameter Meaning

[peer-address]
FlCode
log message.
Possible Causes
The Connection timer timed out.
Procedure
Step 1 Check that the physical lines are normally connected.
Step 2 Check whether the peer configurations change.
Step 3 Re-establish the connection if the route changes and the peer becomes unreachable.
Step 4 End.
----End
62.4 MSDP/6/PEER_UP
Message
MSDP/6/PEER_UP:In VPN instance \"[vpn-instance-name]\", a session with the peer [peeraddress] was initiated. (FlCode=[STRING][ULONG])
Description
A session with the peer was started.
Parameters
Parameter Name
Parameter Meaning

[peer-address]
FlCode
log message.
Issue 07 (2014-07-30)

607

Log Reference
62 MSDP
Possible Causes
A session with the peer was started.
Procedure
l
----End
62.5 MSDP/4/SA_LIMIT
Message
MSDP/4/SA_LIMIT:In VPN instance \"[vpn-instance-name]\", (S,G) entry whose RP was [rpaddress] was ([source-address], [group-address]), it exceeded the peer ([peer-address])'s SAcache maximum [maximum-number]. (FlCode=[STRING][ULONG])
Description
The number of the (S, G) entries reached the upper limit of the peer SA cache.
Parameters
Parameter Name
Parameter Meaning

[rp-address]
Indicates the IP address of the RP.
[source-address]
[group-address]
[peer-address]
[maximum-number] Indicates the maximum number.

FlCode
log message.
Possible Causes
The number of the (S, G) entries reached the upper limit of the peer SA cache.
Procedure
Step 1 Run the peer peer-address sa-policy { import | export } [ acl advanced-acl-number ] command
to configure the policy guiding the receiving and forwarding of SA messages.
Step 2 Run the peer peer-address sa-cache-maximum sa-limit command to adjust the maximum
number of (S, G) entries that can be learned by the device cache from the specified MSDP peer.
Issue 07 (2014-07-30)

608

Log Reference
62 MSDP
Step 3 End.
----End
62.6 MSDP/4/SET_MSDP_GLBPLC_FAIL
Message
MSDP/4/SET_MSDP_GLBPLC_FAIL:In VPN instance \"[vpn-instance-name]\", failed to set
the MSDP global application policy. (FlCode=[STRING][ULONG])
Description
Failed to set an MSDP global application policy.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
Failed to set an MSDP global application policy for the lower layer when configuring MSDP.
Procedure
Step 1 Run the undo msdp command to reconfigure MSDP.
Step 2 If this log is generated each time the configuration is performed, contact Huawei technical
support personnel.
----End
62.7 MSDP/4/SET_MSDP_GWLIST_FAIL
Message
MSDP/4/SET_MSDP_GWLIST_FAIL:In VPN instance \"[vpn-instance-name]\", failed to set
the MSDP global white list application policy. (FlCode=[STRING][ULONG])
Description
Failed to set an MSDP global whitelist application policy.
Issue 07 (2014-07-30)

609

Log Reference
62 MSDP
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
Failed to set an MSDP global whitelist application policy for the lower layer when configuring
MSDP.
Procedure
Step 1 Run the undo msdp command to reconfigure MSDP.
Step 2 If this log is generated each time the configuration is performed, contact Huawei technical
support personnel.
----End
Issue 07 (2014-07-30)

610

Log Reference
63 MSTP
63
MSTP
About This Chapter

63.1 MSTP_ADP/5/ADD_BINDVLAN
63.2 MSTP/4/BPDU_PROTECTION
63.3 MSTP/Notice/DELETE_BINDVLAN
63.4 MSTP/4/EDGE_PORT
63.5 MSTP/4/LOOPBACK_DETECTED
63.6 MSTP/4/LOOP_GUARD
63.7 MSTP/3/PACKET_ERR_COMPLIAN
63.8 MSTP/6/PORT_INIT
63.9 MSTP/6/RECEIVE_MSTITC
63.10 MSTP/5/ROOT_LOST
63.11 MSTP/6/SET_PORT_DISCARDING
63.12 MSTP/6/SET_PORT_FORWARDING
63.13 MSTP/Notice/SET_PORT_INSTANCE
63.14 MSTP/6/SET_PORT_LEARNING
63.15 MSTP/Notice/SET_PORT_STATE
63.16 MSTP/4/SET_CANCEL
63.17 MSTP/6/SET_PORT_DISABLE
Issue 07 (2014-07-30)

611

Log Reference
63 MSTP
63.1 MSTP_ADP/5/ADD_BINDVLAN
Message
MSTP_ADP/5/ADD_BINDVLAN:"These Vlan [STRING] bind instance [ULONG],
[STRING]."
Description
The VLAN is bound to the MSTI.
Parameters
Parameter Name
Parameter Meaning
[STRING1]
VLAN ID.
[ULONG]
MSTI ID.
[STRING2]
Added information.
Possible Causes
The binding between the MSTI and the VLAN changes.
Procedure
l
----End
63.2 MSTP/4/BPDU_PROTECTION
Message
MSTP/4/BPDU_PROTECTION:This edged-port [port-name] that enabled BPDU-Protection
will be shutdown, because it received BPDU packet!
Description
The edge port that was enabled with the BPDU protection function received a BPDU. Then the
port was shut down.
Parameters
Parameter Name
Parameter Meaning
[port-name]
indicates the name of an edge port.
Issue 07 (2014-07-30)

612

Log Reference
63 MSTP
Possible Causes
The edge port that was enabled with the BPDU protection received the BPDU.
Procedure
l
Check whether the BPDU is attacked to decide whether to restore the port status to be Up.
----End
63.3 MSTP/Notice/DELETE_BINDVLAN
Message
MSTP/Notice/DELETE_BINDVLAN:These Vlan [STRING] delete bind instance [ULONG],
[STRING].
Description
A VLAN is unbound from an instance.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the VLAN list.
[ULONG]
Indicates the instance ID.
[STRING]
Possible Causes
A VLAN is unbound from an instance.
Procedure
Step 1
----End
63.4 MSTP/4/EDGE_PORT
Message
MSTP/4/EDGE_PORT:Edged-port [port-name] received BPDU packet, then the active state of
the edged-port will be disabled!
Issue 07 (2014-07-30)

613

Log Reference
63 MSTP
Description
After an edge port received a BPDU, the port turned to inactive.
Parameters
Parameter Name
Parameter Meaning
[port-name]
indicates the name of an edge port.
Possible Causes
The edge port received the BPDU.
Procedure
l
Run the stp edged-port enable command in the interface view to reconfigure the status of
the edge port.
----End
63.5 MSTP/4/LOOPBACK_DETECTED
Message
MSTP/4/LOOPBACK_DETECTED:The port [port-name] was blocked because it received the
BPDU packets sent by itself.
Description
STP detected a self loop when an interface received the BPDUs sent by itself.
Parameters
Parameter Name
Parameter Meaning
port-name
Name of the port where loopback detection is enabled
Possible Causes
An STP-capable interface received BPDUs with the designated bridge ID as the local bridge ID
and the designated interface ID as the local interface ID, it determined that a self loop occurs.
Procedure
Step 1 Run the display current-configuration interface interface-name command to check whether
the interface generating this alarm has been configured with the loopback function.
Issue 07 (2014-07-30)

614

Log Reference
63 MSTP
Step 2 Check whether there is a loop formed by hubs and devices that are connected to the interface.
Step 3 Collect log information and configuration information, and then contact Huawei technical
support personnel.
Step 4 Run the undo loopback command in the interface view to delete the local loopback
configuration.
Step 5 Remove the self-loop network cable from the hub to resolve the problem.
----End
63.6 MSTP/4/LOOP_GUARD
Message
MSTP/4/LOOP_GUARD:MSTP process [process-id] Instance[instance-id]'s LOOP-Protection
port [port-name] did not receive message in prescriptive time!
Description
The port that was enabled with the loop protection function in the instance did not receive a
BPDU within the specified period.
Parameters
Parameter Name
Parameter Meaning
[process-id]
indicates the ID of an MSTP instance.
[instance-id]
indicates the ID of an instance.
[port-name]
indicates the port enabled with the loop protection function.
Possible Causes
The loop protection port did not receive the BPDU within the specified period.
Procedure
Step 1 Find out the cause that the BPDU is not received.
----End
63.7 MSTP/3/PACKET_ERR_COMPLIAN
Issue 07 (2014-07-30)

615

Log Reference
63 MSTP
Message
MSTP/3/PACKET_ERR_COMPLIAN:The port compliance protocol type of the packet
received by MSTP from the port [port-name] is invalid.
Description
The MSTP port received a BPDU with an unknown format.
Parameters
Parameter Name
Parameter Meaning
[port-name]
indicates the name of a port.
Possible Causes
The MSTP module received an invalid BPDU. This BPDU might be an attack BPDU or a BPDU
with the private MSTP format of a non-Huawei device.
Procedure
Step 1 Use a tool to get the received invalid BPDU.
Step 2 Query and record the information about the remote end, including the manufacturer, version,
and configuration.
l If a Huawei device is used, run the display version and display interface commands or the
display current-configuration command.
l If a non-Huawei device is used, run the related commands provided by the manufacturer to
obtain information on the device.
Step 3 If the packet received by MSTP was invalid and hence the STP status was wrong, loops may
occur at Layer 2. It is recommended to shut down the interface to prevent broadcast storms. To
view STP status and check whether loops occur, run the display stp brief command. After
confirming that loops are removed, run the undo shutdown command to enable the interface.
Step 4 Report the statistics on error packets and the collected information to the Huawei technical
personnel for further analysis.
----End
63.8 MSTP/6/PORT_INIT
Message
MSTP/6/PORT_INIT:MSTP port initialization finished, MSTP process [process-id] instance
[instance-id], port name is [port-name].
Description
The MSTP port in the instance was initialized.
Issue 07 (2014-07-30)

616

Log Reference
63 MSTP
Parameters
Parameter Name
Parameter Meaning
[process-id]
[instance-id]
[port-name]
Possible Causes
The MSTP port was initialized.
Procedure
----End
63.9 MSTP/6/RECEIVE_MSTITC
Message
MSTP/6/RECEIVE_MSTITC:MSTP received BPDU with TC, MSTP process [process-id]
instance [instance-id], port name is [port-name].
Description
The MSTP MSTI received the BPDU with a TC flag. The MSTP process ID was [process-id],
the instance ID was [instance-id] and the port name was [port-name].
Parameters
Parameter Name
Parameter Meaning
[process-id]
[instance-id]
[port-name]
Possible Causes
MSTP received the BPDU with the TC.
Procedure
----End
Issue 07 (2014-07-30)

617

Log Reference
63 MSTP
63.10 MSTP/5/ROOT_LOST
Message
MSTP/5/ROOT_LOST:This bridge is no longer the root bridge of the MSTP process [processid] instance [instance-id].
Description
The switch was no longer the root bridge in the instance.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[instance-id]
Possible Causes
The topology changed.
Procedure
Step 1 Run the display stp command to check whether the priority of the switch or the connected switch
is reconfigured.
----End
63.11 MSTP/6/SET_PORT_DISCARDING
Message
MSTP/6/SET_PORT_DISCARDING:In MSTP process [process-id] instance [instance-id],
MSTP set port [port-name] state as discarding.
Description
The MSTP module set the status of the port [port-name] in instance [instance-id] of the process
[process-id] to Discarding.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

618

Log Reference
63 MSTP
Parameter Name
Parameter Meaning
[instance-id]
[port-name]
Possible Causes
MSTP set the port status to Discarding.
Procedure
----End
63.12 MSTP/6/SET_PORT_FORWARDING
Message
MSTP/6/SET_PORT_FORWARDING:In MSTP process [process-id] instance [instance-id],
MSTP set port [port-name] state as forwarding.
Description
The MSTP module set the status of the port [port-name] in the instance [instance-id] of the
process [process-id] to Forwarding.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[instance-id]
[port-name]
Possible Causes
MSTP set the port status to Forwarding.
Procedure
----End
Issue 07 (2014-07-30)

619

Log Reference
63 MSTP
63.13 MSTP/Notice/SET_PORT_INSTANCE
Message
MSTP/Notice/SET_PORT_INSTANCE:Vlanlist has been bound on instance [ULONG] on
iochip slot [ULONG].
Description
A VLAN list is bound to an instance in a slot.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
[ULONG]
Possible Causes
A VLAN list is bound to an instance in a slot.
Procedure
Step 1
----End
63.14 MSTP/6/SET_PORT_LEARNING
Message
MSTP/6/SET_PORT_LEARNING:In process [process-id] instance [instance-id], MSTP set
port [port-name] state as learning.
Description
The MSTP module set the status of the port [port-name] in the instance [instance-id] of the
process [process-id] to Learning.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

620

Log Reference
63 MSTP
Parameter Name
Parameter Meaning
[instance-id]
[port-name]
Possible Causes
MSTP set the port status to Learning.
Procedure
----End
63.15 MSTP/Notice/SET_PORT_STATE
Message
MSTP/Notice/SET_PORT_STATE:Instance [ULONG]'s port [STRING] has been set to
[STRING].
Description
The instance's port status is changed.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
[STRING]
[ULONG]
Possible Causes
The instance's port status is changed.
Procedure
Step 1
----End
Issue 07 (2014-07-30)

621

Log Reference
63 MSTP
63.16 MSTP/4/SET_CANCEL
Message
MSTP/4/SET_CANCEL:The user has cancelled the operation of enable/disable MSTP!
Description
The user canceled the operation of changing the global MSTP status.
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
The operation of changing the global MSTP status was cancelled.
Procedure
l
This log message is informational, and no action is required.
----End
63.17 MSTP/6/SET_PORT_DISABLE
Message
MSTP/6/SET_PORT_DISABLE:Set port [port-name] MSTP disabled.
Description
MSTP was disabled on the port [port-name].
Parameters
Parameter Name
Parameter Meaning
[port-name]
Possible Causes
The port was disabled with MSTP.
Issue 07 (2014-07-30)

622

Log Reference
63 MSTP
Procedure
l
This log message is informational, and no action is required.
----End
Issue 07 (2014-07-30)

623

Log Reference
64 NAP
64
NAP
About This Chapter

64.1 NAP/6/NAP_GOTONEIGHBOR
64.2 NAP/5/NAP_LINK_TIMEOUT
64.3 NAP/4/NAP_LOGIN
Issue 07 (2014-07-30)

624

Log Reference
64 NAP
64.1 NAP/6/NAP_GOTONEIGHBOR
Message
NAP/6/NAP_GOTONEIGHBOR:Log in to another router through [STRING] with NAP
protocol successfully.
Description
Logged in to the slave device through the master interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
Logged in to the slave device from the master device through NAP.
Procedure
----End
64.2 NAP/5/NAP_LINK_TIMEOUT
Message
NAP/5/NAP_LINK_TIMEOUT:NAP link timed out. (PeerDevName=[STRING],
PeerPortName=[STRING])
Description
A NAP link timed out.
Parameters
PeerDevName
Name of a peer device

The system can save a device name with a maximum of 15 characters.
PeerPortName
Issue 07 (2014-07-30)
Name of a peer port

625

Log Reference
64 NAP
Possible Causes
The NAP link timed out.
Procedure
Step 1 Check whether the link to the network is disconnected due to timeout.
----End
64.3 NAP/4/NAP_LOGIN
Message
NAP/4/NAP_LOGIN:NAP user login from [ip-address].
Description
A NAP user logged in.
Parameters
Parameter Name
Parameter Meaning
ip-address
IP address of the NAP user
Possible Causes
A NAP user logged in.
Procedure
----End
Issue 07 (2014-07-30)

626

Log Reference
65 NATPT
65
NATPT
About This Chapter

65.1 NATPT/4/ACLPRE_UNKNOWN_MAP
65.2 NATPT/4/ADD_ENABLELIST_FAIL
65.3 NATPT/3/ADDRMAP_MEMFAIL
65.4 NATPT/4/ADDRMAP_RECHMAX
65.5 NATPT/4/ALLOC_NATPT_IOFAIL
65.6 NATPT/4/AM_NO_FOUND
65.7 NATPT/4/CFGPRE_UNKNOWN_MAP
65.8 NATPT/4/CFGV4_UNKNOWN_MAP
65.10 NATPT/4/CONTR_ADDR_EXHAUST
65.11 NATPT/4/DEL_ENABLELIST_FAIL
65.12 NATPT/4/DELV4_UNKNOWN_MAP
65.14 NATPT/4/DISTR_ADDR_EXHAUST
65.15 NATPT/4/DOWN_AAM_DATA_FAIL
65.16 NATPT/4/DOWN_AM_DATA_FAIL
65.17 NATPT/4/DOWN_ENABLELIST_FAIL
65.18 NATPT/4/DOWN_TRATOS_FAIL
65.19 NATPT/3/DPATMAP_MEMFAIL
65.20 NATPT/4/DPATMAP_RECHMAX
Issue 07 (2014-07-30)

627

Log Reference
65 NATPT
65.21 NATPT/4/FRAGMENT_DESTROY
65.22 NATPT/4/INDEX_HAS_INLIST
65.23 NATPT/4/INVALID_CMD
65.24 NATPT/4/INVALID_IF_IOENABLE
65.25 NATPT/4/INVALIDIF_IOUNE
65.26 NATPT/4/INVALIDIFNET_DEL
65.27 NATPT/3/MALLOFAIL_BKUP
65.28 NATPT/4/MALLOFAIL_ENABLE
65.29 NATPT/6/MAP_INCOMPLETE_DMAP
65.30 NATPT/4/MAX_FRAG_REACH
65.31 NATPT/4/MAX_SESSION_REACH
65.32 NATPT/4/NATPT_HAS_ENABLE
65.33 NATPT/6/NATPT_NOTENABLE
65.34 NATPT/4/RECURSION_IP4_PKT
65.36 NATPT/4/SYSN_MULTI_FAIL
Issue 07 (2014-07-30)

628

Log Reference
65 NATPT
65.1 NATPT/4/ACLPRE_UNKNOWN_MAP
Message
NATPT/4/ACLPRE_UNKNOWN_MAP:Unknown ACL or prefix parameter when configuring
IPv6 dynamic address mapping.
Description
Unknown ACLs or prefixes existed during the creation of IPv6 dynamic address mappings.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Unknown ACLs or prefixes existed during the creation of IPv6 dynamic address mappings.
Procedure
l
Contact the Huawei technical personnel.
----End
65.2 NATPT/4/ADD_ENABLELIST_FAIL
Message
NATPT/4/ADD_ENABLELIST_FAIL:Unable to add the interface to NATPT-enabled-list on
slot [slot-number].
Description
Failed to add the specified interface to the list of NAT-PT interfaces.
Parameters
Parameter Name
Parameter Meaning
[slot-number]
indicates the slot number.
Possible Causes
RPC failed.
Issue 07 (2014-07-30)

629

Log Reference
65 NATPT
Procedure
l
----End
65.3 NATPT/3/ADDRMAP_MEMFAIL
Message
NATPT/3/ADDRMAP_MEMFAIL:Failed to allocate memory when creating new address
mapping.
Description
Memory allocation failed when a new address mapping table was generated.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Memory allocation failed when a new address mapping table was generated.
Procedure
l
Run the display diagnostic-information command, save the output of this command, and
----End
65.4 NATPT/4/ADDRMAP_RECHMAX
Message
NATPT/4/ADDRMAP_RECHMAX:The amount of address mappings has reached the upper
limit, some mappings need to be deleted before new ones can be added.
Description
The address mapping table was full. Delete some old address mappings to inject new address
mappings.
Issue 07 (2014-07-30)

630

Log Reference
65 NATPT
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The address mapping table was full.
Procedure
l
Delete some address mappings.
----End
65.5 NATPT/4/ALLOC_NATPT_IOFAIL
Message
NATPT/4/ALLOC_NATPT_IOFAIL:Failed to allocate memory of NATPT structure when
enabling NATPT on IO board.
Description
Failed to create the NAT-PT control block after enabling NAT-PT on the interface board.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to create the NAT-PT control block after NAT-PT was enabled.
Procedure
l
Run the display diagnostic-information command to save the output of this command and
----End
65.6 NATPT/4/AM_NO_FOUND
Issue 07 (2014-07-30)

631

Log Reference
65 NATPT
Message
NATPT/4/AM_NO_FOUND:Address mapping was not found when decreasing the count of the
mapping.
Description
The address mapping to be deleted was not found when the count of mappings was decreased.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The address mapping to be deleted was not found when the count of mappings was decreased.
Procedure
l
----End
65.7 NATPT/4/CFGPRE_UNKNOWN_MAP
Message
NATPT/4/CFGPRE_UNKNOWN_MAP:Unknown prefix type when configuring prefix.
Description
Unknown prefix types existed during the configuration of prefixes.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Unknown prefix types existed during the configuration of prefixes.
Procedure
l
Contact the Huawei technical personnel
----End
Issue 07 (2014-07-30)

632

Log Reference
65 NATPT
Message
NATPT/4/CFGV4_UNKNOWN_MAP:Unknown mapping type when configuring IPv4
dynamic address mapping.
Description
Unknown mapping types existed during the creation of the IPv4 dynamic address mappings.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Unknown mapping types existed during the creation of the IPv4 dynamic address mappings.
Procedure
l
----End
Message
NATPT/4/CFGV6_UNKNOWN_MAP:Unknown mapping type when configuring IPv6
dynamic address mapping.
Description
Unknown mapping types existed during the creation of IPv6 dynamic address mappings.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Unknown mapping types existed during the creation of IPv6 dynamic address mappings.
Issue 07 (2014-07-30)

633

Log Reference
65 NATPT
Procedure
l
----End
65.10 NATPT/4/CONTR_ADDR_EXHAUST
Message
NATPT/4/CONTR_ADDR_EXHAUST:Address-group [address-pool-number] exhausted
when applying free address from the address-group in centralized system.
Description
Failed to apply for unused addresses in the address pool in a centralized system because addresses
were exhausted.
Parameters
Parameter Name
Parameter Meaning
[address-pool-number]
indicates the address pool number.
Possible Causes
The address pool was too small or excessive sessions were set up in this address pool.
Procedure
l
----End
65.11 NATPT/4/DEL_ENABLELIST_FAIL
Message
NATPT/4/DEL_ENABLELIST_FAIL:Unable to delete the interface from NATPT-enabled-list
on slot [slot-number] or NATPT is not enabled on the interface.
Description
Failed to delete the interface from the list of NAT-PT interfaces or the interface was not enabled
with NAT-PT.
Issue 07 (2014-07-30)

634

Log Reference
65 NATPT
Parameters
Parameter Name
Parameter Meaning
[slot-number]
indicates the slot number.
Possible Causes
The interface cannot be deleted from the list of NAT-PT interfaces or the interface was not
enabled with NAT-PT.
Procedure
l
----End
Message
NATPT/4/DELV4_UNKNOWN_MAP:Unknown mapping type when deleting IPv4 dynamic
address mapping.
Description
Unknown mapping types existed during the deletion of the IPv4 dynamic address mappings.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Unknown mapping types existed during the deletion of the IPv4 dynamic address mappings.
Procedure
l
----End
Issue 07 (2014-07-30)

635

Log Reference
65 NATPT
Message
NATPT/4/DELV6_UNKNOWN_MAP:Unknown mapping type when deleting IPv6 dynamic
address mapping.
Description
Unknown mapping types existed during the deletion of IPv6 dynamic address mappings.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Unknown mapping types existed during the deletion of IPv6 dynamic address mappings.
Procedure
l
----End
65.14 NATPT/4/DISTR_ADDR_EXHAUST
Message
NATPT/4/DISTR_ADDR_EXHAUST:Address-group [address-pool-number] exhausted when
applying free address from the address-group in distributed system.
Description
Failed to apply for unused addresses in the address pool in a distributed system because addresses
were exhausted.
Parameters
Parameter Name
Parameter Meaning
[address-pool-number]
indicates the address pool number.
Possible Causes
The address pool was too small or excessive sessions were set up in this address pool.
Issue 07 (2014-07-30)

636

Log Reference
65 NATPT
Procedure
l
----End
65.15 NATPT/4/DOWN_AAM_DATA_FAIL
Message
NATPT/4/DOWN_AAM_DATA_FAIL:Failed to download data of address allocation
management.
Description
Failed to download address management data to the interface board after NAT-PT was enabled
on the interface.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
After NAT-PT was enabled on the interface, downloading the address management data to the
interface board failed.
Procedure
l
----End
65.16 NATPT/4/DOWN_AM_DATA_FAIL
Message
NATPT/4/DOWN_AM_DATA_FAIL:Failed to download data of address mapping.
Description
Failed to download address mapping data to the interface board after NAT-PT was enabled on
the interface.
Issue 07 (2014-07-30)

637

Log Reference
65 NATPT
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
After NAT-PT was enabled on the interface, downloading AM data to the interface board failed.
Procedure
l
----End
65.17 NATPT/4/DOWN_ENABLELIST_FAIL
Message
NATPT/4/DOWN_ENABLELIST_FAIL:Failed to download data of enable-list.
Description
Failed to deliver the list of NAT-PT interfaces to the interface board after NAT-PT was enabled
on the interface.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to deliver the list of NAT-PT interfaces to the interface board after NAT-PT was enabled
on the interface.
Procedure
l
----End
65.18 NATPT/4/DOWN_TRATOS_FAIL
Message
NATPT/4/DOWN_TRATOS_FAIL:Failed to download data of traffic class or TOS.
Issue 07 (2014-07-30)

638

Log Reference
65 NATPT
Description
Failed to deliver the data of traffic class or service type after NAT-PT was enabled on the
interface.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
After NAT-PT was enabled on the interface, delivering data of traffic class or service type failed.
Procedure
l
----End
65.19 NATPT/3/DPATMAP_MEMFAIL
Message
NATPT/3/DPATMAP_MEMFAIL:Failed to allocate memory when creating new destination
port address mapping.
Description
Memory allocation failed when a new destination port address mapping table was generated.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Memory allocation failed when a new destination port address mapping table was generated.
Procedure
l
Run the display diagnostic-information command, save the output of this command, and
----End
Issue 07 (2014-07-30)

639

Log Reference
65 NATPT
65.20 NATPT/4/DPATMAP_RECHMAX
Message
NATPT/4/DPATMAP_RECHMAX:The amount of destination port address mappings has
reached the upper limit, some mappings need to be deleted before new ones can be added.
Description
The destination port address mapping table was full. Delete some old address mappings so as
to inject new address mappings.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The destination port address mappings table was full. Delete some old address mappings so as
to inject new address mappings.
Procedure
l
----End
65.21 NATPT/4/FRAGMENT_DESTROY
Message
NATPT/4/FRAGMENT_DESTROY:The IPv6 packet is not the first fragmented packet, so the
packet is destroyed.
Description
The received IPv6 fragment was not the first fragment. So the packet was released.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

640

Log Reference
65 NATPT
Possible Causes
The order of IPv6 fragmented packets was incorrect and the first fragment was not firstly
received.
Procedure
l
----End
65.22 NATPT/4/INDEX_HAS_INLIST
Message
NATPT/4/INDEX_HAS_INLIST:Index is already in enable-list when enabling NATPT on the
interface.
Description
The interface had been added to the list of NAT-PT interfaces before it was enabled with NATPT.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The interface had been added into the list of NAT-PT interfaces.
Procedure
l
----End
65.23 NATPT/4/INVALID_CMD
Message
NATPT/4/INVALID_CMD:Invalid command.
Description
The command word was invalid.
Issue 07 (2014-07-30)

641

Log Reference
65 NATPT
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The command word was invalid.
Procedure
l
----End
65.24 NATPT/4/INVALID_IF_IOENABLE
Message
NATPT/4/INVALID_IF_IOENABLE:Invalid IFNET structure when enabling NATPT on IO
board.
Description
The IFNET was invalid when the interface board in a distributed system was enabled with NATPT.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The IFNET was invalid when the interface board was enabled with NAT-PT in a distributed
system.
Procedure
l
----End
65.25 NATPT/4/INVALIDIF_IOUNE
Issue 07 (2014-07-30)

642

Log Reference
65 NATPT
Message
NATPT/4/INVALIDIF_IOUNE:Invalid IFNET structure when disabling NATPT on IO board.
Description
The IFNET was invalid when NAT-PT was disabled.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The IFNET was invalid when NAT-PT was disabled.
Procedure
l
----End
65.26 NATPT/4/INVALIDIFNET_DEL
Message
NATPT/4/INVALIDIFNET_DEL:Invalid IFNET structure when deleting interface.
Description
Failed to delete the NAT-PT configuration on the interface because the specified interface was
null.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The specified interface was null.
Procedure
l
----End
Issue 07 (2014-07-30)

643

Log Reference
65 NATPT
65.27 NATPT/3/MALLOFAIL_BKUP
Message
NATPT/3/MALLOFAIL_BKUP:Failed to allocate memory when batch backup.
Description
Memory allocation for batch backup failed.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Memory allocation for batch backup failed.
Procedure
l
----End
65.28 NATPT/4/MALLOFAIL_ENABLE
Message
NATPT/4/MALLOFAIL_ENABLE:Failed to allocate memory for NATPT when enabling
NATPT on the interface.
Description
When the interface was enabled with NAT-PT, memory allocation for the NAT-PT control block
failed.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

644

Log Reference
65 NATPT
Possible Causes
When the interface was enabled with NAT-PT, memory allocation for the NAT-PT control block
failed.
Procedure
l
Run the display diagnostic-information command to save the output of this command and
----End
65.29 NATPT/6/MAP_INCOMPLETE_DMAP
Message
NATPT/6/MAP_INCOMPLETE_DMAP:New dynamic mapping can not be created till the
reset is completed on all the boards.
Description
The NAT-PT address mapping was performed before the NAT-PT dynamic mapping was
complete.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The NAT-PT address mapping was performed before the NAT-PT dynamic mapping was
complete.
Procedure
l
----End
65.30 NATPT/4/MAX_FRAG_REACH
Message
NATPT/4/MAX_FRAG_REACH:The amount of fragment sessions reached maximum.
Issue 07 (2014-07-30)

645

Log Reference
65 NATPT
Description
New sessions cannot be set up because the number of fragment sessions reached the maximum.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Excessive fragment sessions were set up.
Procedure
l
----End
65.31 NATPT/4/MAX_SESSION_REACH
Message
NATPT/4/MAX_SESSION_REACH:The amount of sessions reached maximum.
Description
The router failed to set up new sessions because the number of the current sessions exceeded
the maximum (0 to 10001).
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
No session could be established on the router because the number of sessions exceeded the range
(0 to 10001).
Procedure
l
----End
65.32 NATPT/4/NATPT_HAS_ENABLE
Issue 07 (2014-07-30)

646

Log Reference
65 NATPT
Message
NATPT/4/NATPT_HAS_ENABLE:NATPT is already enabled on the interface.
Description
NAT-PT was enabled on the interface.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
NAT-PT was enabled on the interface.
Procedure
l
----End
65.33 NATPT/6/NATPT_NOTENABLE
Message
NATPT/6/NATPT_NOTENABLE:NATPT is not enabled when disabling NATPT on the
interface.
Description
Failed to disable NAT-PT on the interface because the interface was not enabled with NAT-PT.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The interface was not enabled with NAT-PT.
Procedure
l
----End
Issue 07 (2014-07-30)

647

Log Reference
65 NATPT
Message
NATPT/4/RECURSION_IP4_PKT:Recursion occurred and IPv4 packet was dropped.
Description
NAT-PT recursion occurred and the packet was discarded.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
l
----End
Message
NATPT/4/RECURSION_IP6_PKT:Recursion occurred and IPv6 packet was dropped.
Description
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Issue 07 (2014-07-30)

648

Log Reference
65 NATPT
Procedure
l
----End
65.36 NATPT/4/SYSN_MULTI_FAIL
Message
NATPT/4/SYSN_MULTI_FAIL:Failed to remove the index from the list on IO board.
Description
The main control board failed to synchronize with the interface board in deleting the NAT-PT
interface.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The main control board failed to synchronize with the interface board in deleting the NAT-PT
interface.
Procedure
l
----End
Issue 07 (2014-07-30)

649

Log Reference
66 NETSTREAM
66
NETSTREAM
About This Chapter

66.1 NETSTREAM/3/DEL_IPV6ENTRY_FAIL
Issue 07 (2014-07-30)

650

Log Reference
66 NETSTREAM
66.1 NETSTREAM/3/DEL_IPV6ENTRY_FAIL
Message
NETSTREAM/3/DEL_IPV6ENTRY_FAIL:Failed to age IPv6 entry.
Description
Failed to age an IPv6 NetStream entry.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to age an IPv6 NetStream entry.
Procedure
Step 1 Run the reset ip netstream statistics command to forcibly age a NetStream entry.
1.
If the NetStream entry is successfully aged, perform Step 3.
2.
If the NetStream entry fails to be aged, perform Step 3.

Step 3 End.
----End
Issue 07 (2014-07-30)

651

Log Reference
67 NQA
67
NQA
About This Chapter

67.1 NQA/4/FALLING_ALARM
67.2 NQA/4/RISING_ALARM
Issue 07 (2014-07-30)

652

Log Reference
67 NQA
67.1 NQA/4/FALLING_ALARM
Message
NQA/4/FALLING_ALARM:The [alarm-node] defined in nqa alarm table(OwnerIndex =
[OCTET] TestName = [OCTET] AlarmEntryNumber = [INTEGER]) has alarm value [alarmvalue],less than threshold [threshold]. It's alarm sample type is [alarm-sample-type].
Description
The value of the monitored node was below the lower limit.
Parameters
Parameter Name
Parameter Meaning
[alarm-node]
Indicates the node that generates the alarm.
OwnerIndex
Indicates the administrator of the NQA test instance.
TestName
Indicates the name of the NQA test instance.
AlarmEntryNumber
Indicates the index of the alarm table.
[alarm-value]
Indicates the value of the node that generates the alarm.
[threshold]
Indicates the user-defined lower limit.
[alarm-sample-type]
Indicates the type of the sampled alarm.
Possible Causes
The value of the monitored node was below the lower limit.
Procedure
Step 1 Run the display nqa-agent command to check whether the lower limit is proper.
1.
If the lower limit is too large, run the alarm command to set the lower limit to be a proper
value, and then go to 3.
2.
If the lower limit is proper, go to 2.
Step 2 If the alarm is generated because of a network problem, check the configurations and services
of the network.
Step 3 End.
----End
67.2 NQA/4/RISING_ALARM
Issue 07 (2014-07-30)

653

Log Reference
67 NQA
Message
NQA/4/RISING_ALARM:The [alarm-node] defined in nqa alarm table (OwnerIndex =
[OCTET] TestName = [OCTET] AlarmEntryNumber = [INTEGER]) has alarm value [alarmvalue], going out of threshold [threshold].It's alarm sample type is [alarm-sample-type].
Description
The value of the monitored node was over the upper limit.
Parameters
Parameter Name
Parameter Meaning
[alarm-node]
Indicates the node that generates the alarm.
OwnerIndex
Indicates the administrator of the NQA test instance.
TestName
Indicates the name of the NQA test instance.
AlarmEntryNumber
Indicates the index of the alarm table.
[alarm-value]
Indicates the value of the node that generates the alarm.
[threshold]
Indicates the user-defined upper limit.
[alarm-sample-type]
Indicates the type of the sampled alarm.
Possible Causes
The value of the monitored node was over the upper limit.
Procedure
Step 1 Run the display nqa-agent command to check whether the upper limit is proper.
1.
If the upper limit is too small, run the alarm command to set the upper limit to be a proper
value, and then go to 3.
2.
If the upper limit is proper, go to 2.
Step 2 If the alarm is generated because of a network problem, check the configurations and services
of the network.
Step 3 End.
----End
Issue 07 (2014-07-30)

654

Log Reference
68 NSADP
68
NSADP
About This Chapter

68.1 NSADP/4/NS_ID_RPCFAIL
Issue 07 (2014-07-30)

655

Log Reference
68 NSADP
68.1 NSADP/4/NS_ID_RPCFAIL
Message
NSADP/4/NS_ID_RPCFAIL: Failed to send message to slot [ULONG]. ( Message type=
[ULONG], Error code=[ULONG])
NOTE
Only the S5710EI, S5700HI, and S5710HI support this log.
Description
After the transmission of RPC/IPC messages failed, the NetStream module records the slot ID,
message type, and error code.
Parameters
Parameter Name
Parameter Meaning
slot
Message type
Indicates message type.
Error code
Possible Causes
RPC or IPC communication between cards failed.
Procedure
----End
Issue 07 (2014-07-30)

656

Log Reference
69 NTP
69
NTP
About This Chapter

69.1 NTP/4/GRADUAL_SET_TIME
69.2 NTP/4/LEAP_CHANGE
69.3 NTP/4/PEER_MAX_ASSOC
69.4 NTP/4/PEER_SELE
69.5 NTP/4/REFCLK_EVENTS
69.6 NTP/4/SOURCE_LOST
69.7 NTP/4/STEP_GET_TIME
69.8 NTP/4/STEP_SET_TIME
69.9 NTP/4/STRATUM_CHANGE
69.10 NTP/4/TIMER_INIT
Issue 07 (2014-07-30)

657

Log Reference
69 NTP
69.1 NTP/4/GRADUAL_SET_TIME
Message
NTP/4/GRADUAL_SET_TIME:Failed to set system time adjustment in the process of gradual
adjustment.
Description
Failed to set the system time during gradual adjustment.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to set the system time during gradual adjustment.
Procedure
----End
69.2 NTP/4/LEAP_CHANGE
Message
NTP/4/LEAP_CHANGE:System leap changes from [leap1] to [leap2] after clock update.
Description
The leap second of the system changed after the system clock was updated.
Parameters
Parameter Name
Parameter Meaning
[leap1]
Indicates the leap second of the system.
[leap2]
Indicates the leap second of the system.
Issue 07 (2014-07-30)

658

Log Reference
69 NTP
Possible Causes
1: The system had just selected the source reference clock.
2: The switchover of source reference clocks was performed during clock synchronization.
Procedure
----End
69.3 NTP/4/PEER_MAX_ASSOC
Message
NTP/4/PEER_MAX_ASSOC:The number of peers exceeded the upper limit 128.
(CurrentPeerNumber=[string])
Description
The number of peers reached the maximum value [CurrentPeerNumber].
Parameters
Parameter Name
Parameter Meaning
CurrentPeerNumber
Indicates the number of current peers.
Possible Causes
During peer establishment, the number of current sessions reached the maximum value
[CurrentPeerNumber] that the system supports.
Procedure
Step 1 Control the number of the established peers to be within [CurrentPeerNumber].
----End
69.4 NTP/4/PEER_SELE
Message
NTP/4/PEER_SELE:The peer selected by the system is [source-address].
Description
The IP address of the source reference clock selected by the system was displayed.
Issue 07 (2014-07-30)

659

Log Reference
69 NTP
Parameters
[source-address]
Indicates the IP address of the source reference clock selected by the

system.
Possible Causes
Procedure
----End
69.5 NTP/4/REFCLK_EVENTS
Message
NTP/4/REFCLK_EVENTS:The reference clock is not synchronized.
(ReferenceClockIpAddress=[string], EventDescription=[string], EventCode=[string])
Description
The local reference clock was not synchronized.
Parameters
Parameter Name
Parameter Meaning
ReferenceClockIpAddress
indicates the IP address of the reference clock.
EventDescription
indicates event description.
EventCode
indicates an event code.
Possible Causes
The distance from the local reference clock to the superior reference clock was unreachable.
Procedure
----End
Issue 07 (2014-07-30)

660

Log Reference
69 NTP
69.6 NTP/4/SOURCE_LOST
Message
NTP/4/SOURCE_LOST:System synchronization source lost. (SourceAddress=[STRING],
Reason=[STRING])
Description
The source reference clock was lost.
Parameters
SourceAddress
Issue 07 (2014-07-30)
Indicates IP address of the source reference clock, whose synchronization

is lost.

661

Log Reference
69 NTP

Reason
Indicates the reason for the loss of source reference clock:

l Unknown
l Autokey configuration changed
l NTP IPv4 service disabled
l NTP IPv6 service disabled
l Clock change detected
l Clock change detected
l Authentication expected
l Autokey failure
l DENY/RSTR received
l RATE received
l CRPTO-NAK received
l Authentication failure
l Clock selection failed - No intersection
l System peer change detected
l Peer reachability lost
l Source address change detected. Autokey dance restarted
l Reference clock unreachable
l Peer clock unsynchronized/unselectable
l Stratum increase detected
l Clock selection failed - No selectable clock
l Clock selection failed - Too many falsetickers
l Broadcast client's interface unavailable
l Broadcast client's interface VPN changed
l Authentication configuration changed
l IPv6 service disabled
l Source interface unavailable
l VPN change detected
l Manycast discovery restarted
l Configuration changed
l Manycast parent deleted
Possible Causes
This log message was generated when the current source reference clock was lost because of
some reasons and no candidate reference clock can be found.
Issue 07 (2014-07-30)

662

Log Reference
69 NTP
Procedure
Step 1 Check whether the network is normal.
Step 2 Run the display ntp-service sessions command to check whether candidate reference clocks
exist.
1.
If candidate reference clocks exist, perform Step 3.
2.
If candidate reference clocks does not exist, run the ntp-service unicast-peer ip-address
command or the ntp-service unicast-server ip-address command to configure the source
reference clock.
Step 3 Run the display ntp-service status command to check whether the server status is stable.
1.
If the server status is stable, perform Step 4.
2.
If the server status is unstable, perform Step 5.
Step 4 Run the display clock command to check whether the system clock is normal.
1.
If the clock of the hardware is normal, perform Step 6.
2.
If the clock of the hardware is abnormal, perform Step 5.

Step 6 End.
----End
69.7 NTP/4/STEP_GET_TIME
Message
NTP/4/STEP_GET_TIME:Failed to get system time in the process of step adjustment.
Description
Failed to obtain the system time during step adjustment.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to obtain the system time during step adjustment.
Procedure
----End
Issue 07 (2014-07-30)

663

Log Reference
69 NTP
69.8 NTP/4/STEP_SET_TIME
Message
NTP/4/STEP_SET_TIME:Failed to set system time in the process of step adjustment.
Description
Failed to set the system time during step adjustment.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to set the system time during step adjustment.
Procedure
----End
69.9 NTP/4/STRATUM_CHANGE
Message
NTP/4/STRATUM_CHANGE:System stratum changes from [stratum1] to [stratum2].
(SourceAddress = [STRING])
Description
The stratum of the source reference clock is changed.
Parameters
Parameter Name
Parameter Meaning
[stratum1]
Indicates the stratum of the system before clock update.
[stratum2]
Indicates the stratum of the system after clock update.
SourceAddress
Indicates the IP address of the source reference clock.
Issue 07 (2014-07-30)

664

Log Reference
69 NTP
Possible Causes
Procedure
----End
69.10 NTP/4/TIMER_INIT
Message
NTP/4/TIMER_INIT:Failed to initialize the timer when creating the timer.
Description
Timer initialization failed during the creation of a timer.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1:Memory allocation failed.
2: The queue was full.
Procedure
----End
Issue 07 (2014-07-30)

665

Log Reference
70 OAM
70
OAM
About This Chapter

70.1 OAM/4/BOARD_OUT_TUNN
70.2 OAM/4/LSP_EN_AVA
70.3 OAM/3/LSP_EN_DEF
70.4 OAM/3/LSP_EN_UNAVA
70.5 OAM/4/LSP_QUIT_DEF
70.6 OAM/4/LSP_START_DET
70.7 OAM/4/LSP_STOP_DET
70.8 OAM/5/NOTIFY_SMOOTH
70.9 OAM/3/PDT_DELETE
70.10 OAM/3/PDT_FAIL_ADD
70.11 OAM/3/PDT_GET_DETECT_INFO
70.12 OAM/3/PDT_SLT
70.13 OAM/3/PDTMSG_ERR
70.14 OAM/4/SLSP_EN_AVA
70.15 OAM/3/SLSP_EN_DEF
70.16 OAM/3/SLSP_EN_UNAVA
70.17 OAM/4/SLSP_QUIT_DEF
70.18 OAM/4/SLSP_START_DET
70.19 OAM/4/SLSP_STOP_DET
70.20 OAM/4/TUN_EN_AVA
Issue 07 (2014-07-30)

666

Log Reference
70 OAM
70.21 OAM/3/TUN_EN_DEF
70.22 OAM/3/TUN_EN_UNAVA
70.23 OAM/4/TUN_QUIT_DEF
70.24 OAM/4/TUN_START_DET
70.25 OAM/4/TUN_STOP_DET
70.26 OAM/3/UPDATA_PDT_FAIL
Issue 07 (2014-07-30)

667

Log Reference
70 OAM
70.1 OAM/4/BOARD_OUT_TUNN
Message
OAM/4/BOARD_OUT_TUNN:[TunnelName] had been removed but not deleted in OAM
table!
Description
The tunnel interface was pulled out, but the tunnel was not deleted.
Parameters
Parameter Name
Parameter Meaning
TunnelName
indicates the tunnel name.
Possible Causes
The Tunnel interface board that was detected by OAM was pulled out.
Procedure
----End
70.2 OAM/4/LSP_EN_AVA
Message
OAM/4/LSP_EN_AVA:LSP enter available state. (Ingress LsrId=[STRING], Tunnel
SessionId=[ULONG])
Description
The LSP entered the available state.
Parameters
Parameter Name
Parameter Meaning
Ingress LsrId
indicates the LSR ID on the ingress.
Tunnel SessionId
indicates the tunnel ID.
Issue 07 (2014-07-30)

668

Log Reference
70 OAM
Possible Causes
Procedure
----End
70.3 OAM/3/LSP_EN_DEF
Message
OAM/3/LSP_EN_DEF:LSP enter defect state! (Ingress LsrId=[STRING], Tunnel SessionId=
[ULONG])
Description
The LSP entered the defect state.
Parameters
Parameter Name
Parameter Meaning
Ingress LsrId
Tunnel SessionId
Possible Causes
The LSP entered the defect state, or the OAM configuration was incorrect.
Procedure
Step 1 Check whether the OAM configuration is correct.
Step 2 If the OAM configuration is incorrect, reconfigure OAM.
Step 3 Check whether the current network is normal.
----End
70.4 OAM/3/LSP_EN_UNAVA
Message
OAM/3/LSP_EN_UNAVA:LSP enter unavailable state! (Ingress LsrId=[STRING], Tunnel
SessionId=[ULONG])
Issue 07 (2014-07-30)

669

Log Reference
70 OAM
Description
The LSP entered the unavailable state.
Parameters
Parameter Name
Parameter Meaning
Ingress LsrId
Tunnel SessionId
Possible Causes
The LSP entered the unavailable state, or the OAM configuration was incorrect.
Procedure
Step 1 Check whether the OAM configuration is correct.
Step 2 If the OAM configuration is incorrect, reconfigure OAM.
----End
70.5 OAM/4/LSP_QUIT_DEF
Message
OAM/4/LSP_QUIT_DEF:LSP quit defect state. (Ingress LsrId=[STRING], Tunnel SessionId=
[ULONG])
Description
The LSP quitted the defect state.
Parameters
Parameter Name
Parameter Meaning
Ingress LsrId
Tunnel SessionId
Possible Causes
The LSP quitted the defect state.
Issue 07 (2014-07-30)

670

Log Reference
70 OAM
Procedure
----End
70.6 OAM/4/LSP_START_DET
Message
OAM/4/LSP_START_DET:LSP start detect. (Ingress LsrId=[STRING], Tunnel SessionId=
[ULONG])
Description
Detection on the LSP started.
Parameters
Parameter Name
Parameter Meaning
Ingress LsrId
Tunnel SessionId
Possible Causes
Detection on the LSP started.
Procedure
----End
70.7 OAM/4/LSP_STOP_DET
Message
OAM/4/LSP_STOP_DET:LSP stop detect. (Ingress LsrId=[STRING], Tunnel SessionId=
[ULONG])
Description
Detection on the LSP was stopped.
Issue 07 (2014-07-30)

671

Log Reference
70 OAM
Parameters
Parameter Name
Parameter Meaning
Ingress LsrId
Tunnel SessionId
Possible Causes
Detection on the LSP was stopped manually.
Procedure
----End
70.8 OAM/5/NOTIFY_SMOOTH
Message
OAM/5/NOTIFY_SMOOTH:Notify hardware adapter to smooth.
Description
The hardware was notified to perform data smoothing.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The hardware was notified to perform data smoothing.
Procedure
Step 1 Check whether the active/standby switchover is performed or the slave board is inserted, and
view the current status of the system.
----End
70.9 OAM/3/PDT_DELETE
Issue 07 (2014-07-30)

672

Log Reference
70 OAM
Message
OAM/3/PDT_DELETE:Failed to delete the OAM entry. (Index=[ULONG])
Description
Failed to delete the OAM instance.
Parameters
Parameter Name
Parameter Meaning
Index
Indicates the index of OAM.
Possible Causes
Failed to delete the OAM instance.
Procedure
Step 1 Reconfigure OAM. If this log message is no longer displayed, it indicates that the fault is
rectified.
Step 2 Collect log files, configuration files, and the current version of the router, and contact Huawei
----End
70.10 OAM/3/PDT_FAIL_ADD
Message
OAM/3/PDT_FAIL_ADD:Failed to add the OAM entry. (Index=[ULONG])
Description
The product failed to add the OAM instance.
Parameters
Parameter Name
Parameter Meaning
Index
Indicates the index of OAM.
Possible Causes
Failed to add the OAM entry.
Issue 07 (2014-07-30)

673

Log Reference
70 OAM
Procedure
rectified.
----End
70.11 OAM/3/PDT_GET_DETECT_INFO
Message
OAM/3/PDT_GET_DETECT_INFO:Failed to get batch defect result!
Description
Failed to obtain the OAM detection result.
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
Failed to obtain the OAM detection result.
Procedure
rectified.
----End
70.12 OAM/3/PDT_SLT
Message
OAM/3/PDT_SLT:Failed to select another board when selected IO board was plugged out!
Description
Failed to re-select the board when the interface board was pulled out.
Issue 07 (2014-07-30)

674

Log Reference
70 OAM
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
Failed to select the board.
Procedure
Step 1 Check whether or not another LPU is available on the device. If no LPU is installed on the device,
install an LPU.
Step 2 If the problem persists, collect log files, configuration files, and the current version of the router,
and contact Huawei technical support personnel.
----End
70.13 OAM/3/PDTMSG_ERR
Message
OAM/3/PDTMSG_ERR:The type of message received is wrong! (Type=[ULONG])
Description
The type of the message was incorrect.
Parameters
Parameter Name
Parameter Meaning
Type
Possible Causes
The type of message reported by the hardware adaptation was incorrect.
Procedure
----End
70.14 OAM/4/SLSP_EN_AVA
Issue 07 (2014-07-30)

675

Log Reference
70 OAM
Message
OAM/4/SLSP_EN_AVA:Static LSP (Name=[STRING]) enter available state.
Description
The static LSP entered the available state.
Parameters
Parameter Name
Parameter Meaning
Name
Indicates the name of an LSP.
Possible Causes
The static LSP entered the available state.
Procedure
----End
70.15 OAM/3/SLSP_EN_DEF
Message
OAM/3/SLSP_EN_DEF:Static LSP (Name=[STRING]) enter defect state!
Description
The static LSP entered the defect state.
Parameters
Parameter Name
Parameter Meaning
Name
Possible Causes
The LSP entered the defect state or the user configuration was incorrect.
Procedure
Step 1 Check whether the OAM configuration was correct. If not, try to restore the OAM configuration
manually.
Issue 07 (2014-07-30)

676

Log Reference
70 OAM
Step 2 Check whether the network is normal. If not, try to rectify the fault of the network.
----End
70.16 OAM/3/SLSP_EN_UNAVA
Message
OAM/3/SLSP_EN_UNAVA:Static LSP (Name=[STRING]) enter unavailable state.
Description
The static LSP entered the unavailable state.
Parameters
Parameter Name
Parameter Meaning
Name
Possible Causes
The LSP entered unavailable state or the configuration command was incorrect.
Procedure
Step 1 Check whether the OAM configuration was correct. If not, try to restore the OAM configuration
manually.
----End
70.17 OAM/4/SLSP_QUIT_DEF
Message
OAM/4/SLSP_QUIT_DEF:Static LSP (Name=[STRING]) quit defect state.
Description
The static LSP left the defect state.
Parameters
Parameter Name
Parameter Meaning
Name
Issue 07 (2014-07-30)

677

Log Reference
70 OAM
Possible Causes
The static LSP left the defect state.
Procedure
----End
70.18 OAM/4/SLSP_START_DET
Message
OAM/4/SLSP_START_DET:Static LSP start detect. (InLabel=[ULONG])
Description
Detection of the static LSP started.
Parameters
Parameter Name
Parameter Meaning
InLabel
Indicates the incoming label.
Possible Causes
Detection of the static LSP started.
Procedure
----End
70.19 OAM/4/SLSP_STOP_DET
Message
OAM/4/SLSP_STOP_DET:Static LSP stop detect. (InLabel=[ULONG])
Description
Detection of the static LSP was stopped.
Issue 07 (2014-07-30)

678

Log Reference
70 OAM
Parameters
Parameter Name
Parameter Meaning
InLabel
Indicates the incoming label.
Possible Causes
Detection of the static LSP was stopped.
Procedure
----End
70.20 OAM/4/TUN_EN_AVA
Message
OAM/4/TUN_EN_AVA:[TunnelName] enter available state.
Description
Parameters
Parameter Name
Parameter Meaning
TunnelName
Indicates the tunnel name.
Possible Causes
Procedure
----End
70.21 OAM/3/TUN_EN_DEF
Message
OAM/3/TUN_EN_DEF:[TunnelName] enter defect state.
Issue 07 (2014-07-30)

679

Log Reference
70 OAM
Description
OAM entered the defect state.
Parameters
Parameter Name
Parameter Meaning
TunnelName
Indicates the name of a tunnel.
Possible Causes
The LSP entered the defect state or the user configuration was incorrect.
Procedure
Step 1 Check whether the OAM configuration was correct.
Step 2 If the OAM configuration was incorrect, try to restore OAM configuration manually.
----End
70.22 OAM/3/TUN_EN_UNAVA
Message
OAM/3/TUN_EN_UNAVA:[TunnelName] enter unavailable state.
Description
Parameters
Parameter Name
Parameter Meaning
TunnelName
Possible Causes
Procedure
Step 1 Check whether the OAM configuration is correct. If not, try to restore the OAM configuration
manually.
Issue 07 (2014-07-30)

680

Log Reference
70 OAM

----End
70.23 OAM/4/TUN_QUIT_DEF
Message
OAM/4/TUN_QUIT_DEF:[TunnelName] quit defect state.
Description
OAM left the defect state.
Parameters
Parameter Name
Parameter Meaning
TunnelName
indicates the name of a tunnel
Possible Causes
OAM left the defect state.
Procedure
----End
70.24 OAM/4/TUN_START_DET
Message
OAM/4/TUN_START_DET:[TunnelName] start detect.
Description
OAM detection started.
Parameters
Parameter Name
Parameter Meaning
TunnelName
Issue 07 (2014-07-30)

681

Log Reference
70 OAM
Possible Causes
OAM detection started.
Procedure
----End
70.25 OAM/4/TUN_STOP_DET
Message
OAM/4/TUN_STOP_DET:[TunnelName] stop detect.
Description
OAM detection was stopped.
Parameters
Parameter Name
Parameter Meaning
TunnelName
Possible Causes
OAM detection was stopped manually.
Procedure
----End
70.26 OAM/3/UPDATA_PDT_FAIL
Message
OAM/3/UPDATA_PDT_FAIL:Failed to update the hardware adapter information on io board!
Description
Failed to update the software adaptation information.
Issue 07 (2014-07-30)

682

Log Reference
70 OAM
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
Information about the hardware adaptation of an LPU failed to be updated.
Procedure
rectified.
----End
Issue 07 (2014-07-30)

683

Log Reference
71 OSPF
71
OSPF
About This Chapter

71.1 OSPF/6/ADD_NBR_PRLIST_VLINK
71.2 OSPF/4/ALL_NBR_FULL_EXIT
71.3 OSPF/4/AUTO_CHG_RTRID
71.4 OSPF/6/BACKUP_AFTER_CFM
71.5 OSPF/6/BACKUP_BEFORE_CFM
71.6 OSPF/6/BACKUP_LENGTH_ERR
71.7 OSPF/6/BACKUP_TYPE_ERR
71.8 OSPF/6/BAD_IP_PACKET
71.9 OSPF/6/BAD_LSA
71.10 OSPF/6/BAD_OSPF_PACKET
71.11 OSPF/4/CHG_LSA_HELPER_FAIL
71.12 OSPF/4/CONFLICT_IP_ADDRESS
71.13 OSPF/6/CONFLICT_ROUTERID_INTER
71.14 OSPF/4/CONFLICT_ROUTERID_INTF
71.15 OSPF/4/CONFLICT_ROUTERID_INTRA
71.16 OSPF/6/DEL_NBR_PRLIST
71.17 OSPF/6/DEL_NBR_PRLIST_VLINK
71.18 OSPF/3/DR_ELECT_FAILED
71.19 OSPF/3/END_GR_NODE_IN_LIST
71.20 OSPF/4/ENTER_HELPER_MODE
Issue 07 (2014-07-30)

684

Log Reference
71 OSPF
71.21 OSPF/6/FIND_NBR_SHAMLINK
71.22 OSPF/6/FINISH_ADD_ASE
71.23 OSPF/6/FINISH_ADD_NSSA
71.24 OSPF/6/FLSH_STL_AS_LSA
71.25 OSPF/6/FLUSH_STAL_AREA_LSA
71.26 OSPF/6/GR_ADD_NBR_PRLIST
71.27 OSPF/4/GR_END_SUCCESS
71.28 OSPF/3/GR_EXIT_GR_UNSU
71.29 OSPF/4/GR_EXIT_HLP_SU
71.30 OSPF/4/GR_HLP_TIMER_FIRED
71.31 OSPF/3/GR_IF_CHANGE
71.32 OSPF/4/GR_NOTIFYRM_EXIT_GR
71.33 OSPF/4/GR_RECV_1WAY_HELLO
71.34 OSPF/4/GR_START_GR
71.35 OSPF/4/HLP_EXIT_RECV_LSA
71.36 OSPF/6/IF_CHG_E
71.37 OSPF/6/IF_TYPE_CHG
71.38 OSPF/3/INTF_EXIT_HLP_FAIL
71.39 OSPF/6/INTF_NSR_EVENT
71.40 OSPF/4/INTF_NSR_OVERTIME_LIMIT
71.41 OSPF/6/ISSU_SMB_CMD_ERR
71.42 OSPF/3/ISSU_SMOOTH_ACROSS
71.43 OSPF/3/ISSU_SMOOTH_INSIDE
71.44 OSPF/3/ISSU_SMOOTH_OVER
71.45 OSPF/6/JOIN_MULGRP_FAIL
71.46 OSPF/6/LDP_INIT_EVENT
71.47 OSPF/6/LDP_SYNC_CREA
71.48 OSPF/6/LDP_SYNC_EVENT
71.49 OSPF/6/LDP_SYNC_FIRE
71.50 OSPF/6/LEAVE_MULGRP_FAIL
71.51 OSPF/5/LSA_CHANGE_FREQUENT
71.52 OSPF/3/MISMATCH_HELPER_FAIL
Issue 07 (2014-07-30)

685

Log Reference
71 OSPF
71.53 OSPF/4/NBR_CHANGE_E
71.54 OSPF/3/NBR_CHG_DOWN
71.55 OSPF/3/NBR_DOWN_REASON
71.56 OSPF/4/NBR_STATE_HELPER_F
71.57 OSPF/6/NOTIFY_DEL_FINISHED
71.58 OSPF/4/NOTIFYRM_ENTER_GR
71.59 OSPF/6/NSR_AMB_BAKOVER_INFO
71.60 OSPF/6/NSR_AMB_BCHOVER_INFO
71.61 OSPF/6/NSR_AMB_ENWARM_INFO
71.62 OSPF/6/NSR_AMB_EXWARM_INFO
71.63 OSPF/6/NSR_AMB_GROVER_INFO
71.64 OSPF/6/NSR_AMB_RM_INFO
71.65 OSPF/6/NSR_AMB_RMCHK_INFO
71.66 OSPF/6/NSR_AREARECV_DATA
71.67 OSPF/6/NSR_AREARECV_INFO
71.68 OSPF/6/NSR_AREARESET_INFO
71.69 OSPF/6/NSR_PROCRECV_DATA
71.70 OSPF/6/NSR_PROCRECV_INFO
71.71 OSPF/6/NSR_PROCRESET_INFO
71.72 OSPF/6/NSR_SMB_BATCH_INFO
71.73 OSPF/6/NSR_SMB_GLOBAL_INFO
71.74 OSPF/6/NSSA_STATE_ELECT
71.75 OSPF/6/ONE_IF_EXIT_WAITING
71.76 OSPF/4/ONEIF_ENTER_WAITING
71.77 OSPF/3/PAF_TYPE_LOSS_ISSU
71.78 OSPF/4/PLCY_FAIL_HELPER_F
71.79 OSPF/6/RCV_MEM_RESTORE
71.80 OSPF/6/RCV_RM_EVNT
71.81 OSPF/4/RECV_DIFF_GRACE_LSA
71.82 OSPF/4/RECV_FIRST_GLSA
71.83 OSPF/6/RECV_ROUT_LIMIT_MSG
71.84 OSPF/6/RECV_SMB_DOWN_RM
Issue 07 (2014-07-30)

686

Log Reference
71 OSPF
71.85 OSPF/6/RECV_SMOOTH_OVER_RM
71.86 OSPF/6/RECV_SWITCH_RM
71.87 OSPF/6/RECV_SYNC_ACROSS_RM
71.88 OSPF/3/RECV_TWO_GRACELSA
71.89 OSPF/6/RESET_SCHEDULE
71.90 OSPF/6/RESTORE_AFTER_CFM
71.91 OSPF/6/RESTORE_BEFORE_CFM
71.92 OSPF/6/RM_GETROUTERID
71.93 OSPF/6/RM_IM
71.94 OSPF/4/RST_NBR_IN_PTIAL_GR
71.95 OSPF/4/RTRLSA_BACKLINK_FAIL
71.96 OSPF/6/SHAMLINK_IF_CHG_E
71.97 OSPF/4/SHAMLINK_NBR_CHG_E
71.98 OSPF/3/SHAMLINK_NBR_DOWN
71.99 OSPF/6/SINTF_NSR_EVENT
71.100 OSPF/4/SINTF_NSR_OVERTIME_LIMIT
71.101 OSPF/6/SMB_GETSESSION_ERR
71.102 OSPF/6/SMB_NSR_AREA_INFO
71.103 OSPF/6/SMB_NSR_PROC_INFO
71.104 OSPF/6/STUB_RT_EX_UD_STUB
71.105 OSPF/6/STUB_RT_ONBT_TM_CRT
71.106 OSPF/6/STUB_RT_STUB_ALW
71.107 OSPF/6/STUB_RT_TM_FIRE
71.108 OSPF/6/TRAP_AGE_LSA
71.109 OSPF/6/TRAP_HELPER_CHG
71.110 OSPF/4/TRAP_INTF_AUTH_FAIL
71.111 OSPF/6/TRAP_INTF_BAD_RX
71.112 OSPF/4/TRAP_INTF_CFG_ERR
71.113 OSPF/6/TRAP_INTF_CHG
71.114 OSPF/6/TRAP_INTF_RETX
71.115 OSPF/6/TRAP_LSDB_APP_OFLOW
71.116 OSPF/6/TRAP_LSDB_OVERFLOW
Issue 07 (2014-07-30)

687

Log Reference
71 OSPF
71.117 OSPF/6/TRAP_NBR_CHG
71.118 OSPF/6/TRAP_NSSA_TRANS_CHG
71.119 OSPF/6/TRAP_ORG_LSA
71.120 OSPF/6/TRAP_RESTART_CHG
71.121 OSPF/4/TRAP_VIF_AUTH_FAIL
71.122 OSPF/4/TRAP_VIF_CFG_ERR
71.123 OSPF/6/TRAP_VIF_RX_BAD
71.124 OSPF/6/TRAP_VIR_HELPER_CHG
71.125 OSPF/6/TRAP_VIR_INTF_CHG
71.126 OSPF/6/TRAP_VIR_INTF_RETX
71.127 OSPF/6/TRAP_VIR_NBR_CHG
71.128 OSPF/4/UPLAN_MATCH_HLPFAIL
71.129 OSPF/6/VINTF_NSR_EVENT
71.130 OSPF/4/VINTF_NSR_OVERTIME_LIMIT
71.131 OSPF/6/VLINK_IF_CHG_E
71.132 OSPF/3/VLINK_NBR_CHG_DOWN
71.133 OSPF/4/VLINK_NBR_CHG_E
Issue 07 (2014-07-30)

688

Log Reference
71 OSPF
71.1 OSPF/6/ADD_NBR_PRLIST_VLINK
Message
OSPF/6/ADD_NBR_PRLIST_VLINK:OSPF [process-id] adds virtual neighbor to pre-restart
neighbor list. (RouterId=[IPADDR], TransitAreaId=[IPADDR], HelperVirtNbrCount=
[ULONG], HelperShamLinkNbrCount=[ULONG], HelperNormalNbrCount=[ULONG])
Description
OSPF detected a pre-restart neighbor on the virtual link.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the ID of an OSPF process.
RouterId
Indicates the ID of a router.
TransitAreaId
Indicates the ID of the transit area.
HelperVirtNbrCount
Indicates the number of neighbors that establish the virtual link

with the Helper.
HelperShamLinkNbrCount Indicates the number of the sham link.

HelperNormalNbrCount
Indicates the number of normal neighbors.
Possible Causes
OSPF detected a pre-restart neighbor on the virtual link.
Procedure
----End
71.2 OSPF/4/ALL_NBR_FULL_EXIT
Message
OSPF/4/ALL_NBR_FULL_EXIT:OSPF [process-id] exited GR successfully.
Description
The OSPF process successfully exited from GR.
Issue 07 (2014-07-30)

689

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
71.3 OSPF/4/AUTO_CHG_RTRID
Message
OSPF/4/AUTO_CHG_RTRID: OSPF automatically changes the router ID when detecting
router ID conflict in the area. (ProcessId=[USHORT], NewRouterId=[IPADDR], OldRouterId=
[IPADDR], ConflictRtrIdNum=[ULONG])
Description
OSPF automatically changed the router ID when two or more same IDs were detected for a
switch in an area.
Parameters
Parameter Name
Parameter Meaning
ProcessId
Process ID
NewRouterId
New ID for a switch
OldRouterId
Original ID for a switch
ConflictRtrIdNum
Number of conflict switch IDs
Possible Causes
The same router ID was configured for at least two indirectly connected routers within one area,
which caused the router lSA to be refreshed frequently. As a result, route flapping occurred.
Procedure
Step 1 If the ospf router-id auto-recover disable command is enabled by default, the system will be
automatically restored after two or more same router IDs are detected.
Issue 07 (2014-07-30)

690

Log Reference
71 OSPF
Step 2 If the system cannot be restored automatically, change a router ID manually.

----End
71.4 OSPF/6/BACKUP_AFTER_CFM
Message
OSPF/6/BACKUP_AFTER_CFM:OSPF backed up data in batches after CFM.
Description
OSPF backed up the data in batches.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
OSPF received the backup invoking message from the RM.
Procedure
----End
71.5 OSPF/6/BACKUP_BEFORE_CFM
Message
OSPF/6/BACKUP_BEFORE_CFM:OSPF backed up data in batches before CFM.
Description
OSPF backed up the data in batches.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

691

Log Reference
71 OSPF
Possible Causes
OSPF received the backup callback message from the RM.
Procedure
----End
71.6 OSPF/6/BACKUP_LENGTH_ERR
Message
OSPF/6/BACKUP_LENGTH_ERR:The data length was unidentifiable in the restoration
process. (Type=[STRING], Length=[USHORT])
Description
During data restoration on the SMB, the length of TLV messages cannot be recognized.
Parameters
Parameter Name
Parameter Meaning
Type
Indicates the type of the data.
Length
Indicates the length of the data.
Possible Causes
The length of TLV messages was inconsistent.
Procedure
Step 1 Run the display current-configuration ospf command to check whether configurations on the
AMB and SMB are the same. If so, go to Step 3; if not, go to Step 2.
Step 2 If some commands are only used on the AMB, configure them on the SMB.
----End
71.7 OSPF/6/BACKUP_TYPE_ERR
Message
OSPF/6/BACKUP_TYPE_ERR:The data type was unidentifiable in the restoration process.
(Type=[USHORT])
Issue 07 (2014-07-30)

692

Log Reference
71 OSPF
Description
During data restoration on the SMB, the type of TLV messages cannot be recognized.
Parameters
Parameter Name
Parameter Meaning
Type
Indicates the type of the data.
Possible Causes
The types of TLV messages was inconsistent.
Procedure
Step 2 Configure inconsistent commands on the SMB.
----End
71.8 OSPF/6/BAD_IP_PACKET
Message
OSPF/6/BAD_IP_PACKET: Received the first bad IP packet within an interval of 15 minutes.
(ErrorType=[STRING], ErrorInformation=[STRING], InterfaceName=[STRING],
SourceAddress=[IPADDR], DestinationAddress=[IPADDR], Count=[ULONG],
PacketContent=[STRING])
Description
The first incorrect IP packet was received within 15 minutes. Each packet error type has a specific
suppression measure, and suppression measures do not affect each other.
Parameters
ErrorType
Packet error type
ErrorInformation
Key packet error information
InterfaceName
Interface name
SourceAddress
Source IP address of packets
DestinationAddress Destination IP address of packets

Issue 07 (2014-07-30)

693

Log Reference
71 OSPF

Count
Number of incorrect packets (The number is reset after being displayed.

This means the number of incorrect packets in the displayed log only
indicates the number of incorrect packets generated since the last time
the number of incorrect packets was displayed.)
PacketContent
Packet contents, in the hexadecimal format
Possible Causes
This log is displayed if a router receives incorrect IP packets (for example, the IP packet length
is smaller that the minimum OSPF packet header length). Incorrect packets of the same type are
suppressed for 15 minutes.
Procedure
----End
71.9 OSPF/6/BAD_LSA
Message
OSPF/6/BAD_LSA: Received the first bad LSA within an interval of 15 minutes. (ErrorType=
[STRING], ErrorInformation=[STRING], ProcessId=[USHORT], InterfaceName=[STRING],
LsaType=[USHORT], AdvertisingRouter=[IPADDR], LinkStateId=[IPADDR], Count=
[ULONG], LsaContent=[STRING])
Description
The first incorrect LSA was received within 15 minutes. Each packet error type has a specific
suppression measure, and suppression measures do not affect each other.
Parameters
ErrorType
Packet error type
ErrorInformation
ProcessId
Process ID
InterfaceName
Interface name
LsaType
LSA type
AdvertisingRouter LSA advertising router

LinkStateId
Issue 07 (2014-07-30)
Link state ID
694

Log Reference
71 OSPF

Count
Number of error packets (The number is reset after being displayed. This
means that the number of incorrect packets displayed in the log only
indicates the number of incorrect packets generated since the last time the
number of incorrect packets was displayed.)
LsaContent
LSA contents, in the hexadecimal format.
Possible Causes
This log is displayed if the router receives an incorrect LSA (for example, the checksum of the
LSA is incorrect). Incorrect LSAs of the same type are suppressed for 15 minutes.
Procedure
Step 1 Check the device that sends the incorrect LSAs.
----End
71.10 OSPF/6/BAD_OSPF_PACKET
Message
OSPF/6/BAD_OSPF_PACKET: Received the first bad OSPF packet within an interval of 15
minutes. (ErrorType=[STRING], ErrorInformation=[STRING], ProcessId=[USHORT],
InterfaceName=[STRING], SourceAddress=[IPADDR], DestinationAddress=[IPADDR],
NeighborRouterId=[IPADDR], PacketType=[USHORT], Count=[ULONG], PacketLength=
[USHORT], PacketContent=[STRING])
Description
The first incorrect OSPF packet was received within 15 minutes. Each packet error type has a
specific suppression measure, and suppression measures do not affect each other.
Parameters
ErrorType
Packet error type
ErrorInformation
ProcessId
Process ID
InterfaceName
Interface name
SourceAddress
Source IP address of packets
DestinationAddress Destination IP address of packets

Issue 07 (2014-07-30)

695

Log Reference
71 OSPF

NeighborRouterId
Neighboring router ID
PacketType
Packet type
Count
Number of incorrect packets (The number is reset after being displayed.

This means that the number of incorrect packets in a displayed log only
indicates the number of incorrect packets generated since the last time
the number of incorrect packets was displayed.)
PacketLength
Packet length
PacketContent
Packet contents, in the hexadecimal format
Possible Causes
This log is displayed if a router receives OSPF error packets (for example, the OSPF packets
fail the authentication or fail to be parsed).The 15-minute suppression is performed on the error
packets of the same type.
Procedure
Step 1 Locate the fault based on packet error types:
l If OSPF packets fail the authentication, verify configurations of the local router.
l If the OSPF packets fail to be parsed, verify configurations of the packet-sending router.
----End
71.11 OSPF/4/CHG_LSA_HELPER_FAIL
Message
OSPF/4/CHG_LSA_HELPER_FAIL:OSPF [process-id] can not enter helper mode, changed
LSA in retransmition list for restarting neighbor [neighbor-ip-address].
Description
OSPF cannot enter the helper mode because the LSA was changed in the retransmission list of
the restarting neighbor.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[neighbor-ip-address]
Issue 07 (2014-07-30)

696

Log Reference
71 OSPF
Possible Causes
OSPF cannot enter the helper mode because the LSA was changed in the retransmission list of
the restarting neighbor.
Procedure
----End
71.12 OSPF/4/CONFLICT_IP_ADDRESS
Message
OSPF/4/CONFLICT_IP_ADDRESS: OSPF interface IP address conflict is detected on intraarea. (ProcessId=[USHORT], RouterId=[IPADDR], AreaId=[IPADDR], InterfaceName=
[STRING], IpAddr=[IPADDR], AdvertiseRouterId=[IPADDR])
Description
Conflicting interface addresses were detected in an OSPF area.
Parameters
Parameter Name
Parameter Meaning
ProcessId
Indicates the ID of a process.
RouterId
Indicates the router ID of a device.
AreaId
Indicates the ID of an area.
InterfaceName
IpAddr
AdvertiseRouterId
Indicates the ID of the advertising router.
Possible Causes
Two indirectly connected routers in an area were configured with the same IP address, and one
of the routers functioned as the DR and advertised network LSAs, causing constant route
flapping.
Procedure
Step 1 Modify the IP addresses of the routers to ensure that each router in the area is configured with
a unique IP address.
----End
Issue 07 (2014-07-30)

697

Log Reference
71 OSPF
71.13 OSPF/6/CONFLICT_ROUTERID_INTER
Message
OSPF/6/CONFLICT_ROUTERID_INTER: OSPF Router id conflict maybe occur on inter-area.
(ProcessId=[USHORT], RouterId=[IPADDR])
Description
The router IDs of OSPF devices in different areas might conflict because external routes were
constantly refreshed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
Possible Causes
At least two indirectly connected routers were configured with the same router ID, causing router
LSAs to be constantly refreshed. As a result, route flapping occurs.
Procedure
Step 1 Check why external routes flap. If the router IDs of devices in different areas conflict, modify
the router IDs of these devices.
----End
71.14 OSPF/4/CONFLICT_ROUTERID_INTF
Message
OSPF/4/CONFLICT_ROUTERID_INTF: OSPF Router id conflict is detected on interface.
(ProcessId=[USHORT], RouterId=[IPADDR], AreaId=[IPADDR], InterfaceName=
[STRING], IpAddr=[IPADDR], PacketSrcIp=[IPADDR])
Description
A router ID conflict was detected on an OSPF interface.
Issue 07 (2014-07-30)

698

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
AreaId
InterfaceName
IpAddr
PacketSrcIp
Indicates the source address of a packet.
Possible Causes
The router IDs of directly connected interfaces conflicted.
Procedure
Step 1 Find out the conflicting router IDs based on interfaces, and modify the router IDs to ensure that
they are not conflicting.
----End
71.15 OSPF/4/CONFLICT_ROUTERID_INTRA
Message
OSPF/4/CONFLICT_ROUTERID_INTRA:OSPF Router id conflict is detected on intra-area.
(ProcessId=[USHORT], RouterId=[IPADDR], AreaId=[IPADDR], NbrInterfaceIp1=
[IPADDR], NbrInterfaceIp2=[IPADDR])
Description
A router ID conflict was detected in an OSPF area.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
Indicates the router ID of a router.
AreaId
NbrInterfaceIp1
Indicates the IP address of the neighbor 's interface.
NbrInterfaceIp2
Indicates the IP address of the neighbor 's interface.
Issue 07 (2014-07-30)

699

Log Reference
71 OSPF
Possible Causes
At least two indirectly routers were configured with the same router ID, causing router LSAs to
be constantly refreshed. As a result, route flapping occurs.
Procedure
Step 1 Modify the router IDs of the routers to ensure that each router in the area has a unique router
ID.
----End
71.16 OSPF/6/DEL_NBR_PRLIST
Message
OSPF/6/DEL_NBR_PRLIST:OSPF [process-id] deletes neighbor from pre-restart neighbor list.
(RouterId=[IPADDR], IpAddress=[IPADDR], HelperVirtNbrCount=[ULONG],
HelperShamLinkNbrCount=[ULONG], HelperNormalNbrCount=[ULONG]).
Description
The OSPF process deleted the neighbor from the pre-restart neighbor list.
Parameters
Parameter Name
Parameter Meaning
[process-id]
RouterId
Indicates the ID of the neighboring router.
IpAddress
Indicates the IP address of the interface performing GR on the

local router.
HelperVirtNbrCount
Indicates the number of virtual-link neighbors functioning as GR

Helpers.
HelperShamLinkNbrCount Indicates the number of shame-link neighbors functioning as GR

Helpers.
Indicates the number of normal neighbors functioning as GR

Helpers.
Possible Causes
For a GR Restarter, when the status of the neighbor relationship between the Restarter and the
Helper is Full, its Helper neighbors are deleted from the pre-restart neighbor list.
For a partly GR Restarter, when it fails to perform GR and exits from GR, all the Helper neighbors
of this Restarter are deleted from the pre-restart neighbor list.
Issue 07 (2014-07-30)

700

Log Reference
71 OSPF
Procedure
----End
71.17 OSPF/6/DEL_NBR_PRLIST_VLINK
Message
OSPF/6/DEL_NBR_PRLIST_VLINK:OSPF [process-id] deletes virtual neighbor from prerestart neighbor list. (RouterId=[IPADDR], TransitAreaId=[IPADDR], HelperVirtNbrCount=
[ULONG], HelperShamLinkNbrCount=[ULONG], HelperNormalNbrCount=[ULONG])
Description
The OSPF process deleted the neighbor on the virtual link from the pre-restart neighbor list.
Parameters
Parameter Name
Parameter Meaning
[process-id]
RouterId
TransitAreaId
Indicates the ID of the transit area.
HelperVirtNbrCount
Indicates the virtual link of the helper neighbor.
HelperShamLinkNbrCount
Indicates the sham link.
Indicates the number of normal links.
Possible Causes
The OSPF process deleted the neighbor on the virtual link from the pre-restart neighbor list.
Procedure
----End
71.18 OSPF/3/DR_ELECT_FAILED
Message
OSPF/3/DR_ELECT_FAILED:OSPF [process-id] DR election failed. Exit GR unsuccefully as
DR election failed.
Issue 07 (2014-07-30)

701

Log Reference
71 OSPF
Description
Exit from GR because the DR election failed.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The DR election during GR failed.
Procedure
----End
71.19 OSPF/3/END_GR_NODE_IN_LIST
Message
OSPF/3/END_GR_NODE_IN_LIST:OSPF [process-id] GR period expired. Exit GR
unsuccessfully as pre-restart neighbor list still has [prerestart-neighbor-count] node(s).
Description
GR period expired. Failed to exit from GR because the pre-restarted neighbor list was not empty.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[prerestart-neighbor-count]
Indicates the number of pre-started neighbor nodes.
Possible Causes
No pre-restarted neighbor was found during GR.
Procedure
----End
Issue 07 (2014-07-30)

702

Log Reference
71 OSPF
71.20 OSPF/4/ENTER_HELPER_MODE
Message
OSPF/4/ENTER_HELPER_MODE:OSPF [process-id] neighbor [neighbor-information] enters
helper on interface [interface-ip-address].
Description
The OSPF neighbor entered the helper mode.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[neighbor-information]
[interface-ip-address]
Indicates the IP address of a neighbor.
Possible Causes
The OSPF process on the interface entered the helper mode.
Procedure
----End
71.21 OSPF/6/FIND_NBR_SHAMLINK
Message
OSPF/6/FIND_NBR_SHAMLINK:OSPF [process-id] finds pre-restart neighbor [prerestartneighbor-id], on sham-link source=[sham-link-ip-address] destination=[destination-ipaddress]. Route to destination is found.
Description
The OSPF process found the pre-restarted neighbor on the sham link.
Issue 07 (2014-07-30)

703

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
[process-id]
[prerestart-neighbor-id]
Indicates the ID of a pre-restarted neighbor.
[sham-link-ip-address]
Indicates the source address of the sham link.
[destination-ip-address]
Possible Causes
The OSPF process found the pre-restarted neighbor on the sham link.
Procedure
----End
71.22 OSPF/6/FINISH_ADD_ASE
Message
OSPF/6/FINISH_ADD_ASE:OSPF [process-id] finished flooding of AS-external LSAs.
Description
The helper received a 1-way Hello packet from the neighbor and then discarded the packet.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
OSPF needs to flood AS-external before the partial GR finishes.
Procedure
----End
71.23 OSPF/6/FINISH_ADD_NSSA
Issue 07 (2014-07-30)

704

Log Reference
71 OSPF
Message
OSPF/6/FINISH_ADD_NSSA:OSPF [process-id] finished flooding of NSSA LSAs.
Description
The helper received a 1-way Hello packet from the neighbor and then discarded the packet.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
OSPF needs to flood NSSA LSAs before the partial GR finishes.
Procedure
----End
71.24 OSPF/6/FLSH_STL_AS_LSA
Message
OSPF/6/FLSH_STL_AS_LSA:Finish flushing stale As-external-LSAs and NSSA LSAs.
(ProcessId=[USHORT])
Description
Finished discarding stale AS-external-LSAs and NSSA LSAs.
Parameters
Parameter Name
Parameter Meaning
ProcessId
Possible Causes
Stale AS-external-LSAs and NSSA LSAs were discarded.
Procedure
----End
Issue 07 (2014-07-30)

705

Log Reference
71 OSPF
71.25 OSPF/6/FLUSH_STAL_AREA_LSA
Message
OSPF/6/FLUSH_STAL_AREA_LSA:Flush stale area LSAs. (ProcessId=[USHORT])
Description
Started to discard stale area LSAs.
Parameters
Parameter Name
Parameter Meaning
ProcessId
Possible Causes
Stale area LSAs were discarded.
Procedure
----End
71.26 OSPF/6/GR_ADD_NBR_PRLIST
Message
OSPF/6/GR_ADD_NBR_PRLIST:OSPF [process-id] adds neighbor to pre-restart neighbor list.
(RouterId=[IPADDR], IPAddress=[IPADDR], HelperVirtNbrCount=[ULONG],
HelperShamLinkNbrCount=[ULONG], HelperNormalNbrCount=[ULONG])
Description
The OSPF process added the neighbor to the pre-restart neighbor list.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the ID of the OSPF process.
RouterId
Issue 07 (2014-07-30)

706

Log Reference
71 OSPF
Parameter Name
Parameter Meaning
IpAddress
Indicates the IP address of the interface performing GR on the

local router.
HelperVirtNbrCount
Indicates the number of virtual-link neighbors functioning as GR

Helpers.
HelperShamLinkNbrCount Indicates the number of shame-link neighbors functioning as GR

Helpers.
Indicates the number of normal neighbors functioning as GR

Helpers.
Possible Causes
The OSPF process added the neighbor to the pre-restart neighbor list.
Procedure
----End
71.27 OSPF/4/GR_END_SUCCESS
Message
OSPF/4/GR_END_SUCCESS:OSPF [process-id] GR period expired. Exit GR successfully as
pre-restart neighbor list being empty.
Description
GR period expired. Succeeded in exiting from GR because the pre-restarted neighbor list was
empty.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Succeeded in exiting from GR.
Procedure
----End
Issue 07 (2014-07-30)

707

Log Reference
71 OSPF
71.28 OSPF/3/GR_EXIT_GR_UNSU
Message
OSPF/3/GR_EXIT_GR_UNSU:OSPF [process-id] exited GR Unsuccessfully.
Description
The OSPF process failed to exit from GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The OSPF process failed to exit from GR.
Procedure
----End
71.29 OSPF/4/GR_EXIT_HLP_SU
Message
OSPF/4/GR_EXIT_HLP_SU:OSPF [process-id] neighbor [neighbor-information] exits helper
successfully on interface [interface-ip-address].
Description
The OSPF neighbor successfully exited from GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

708

Log Reference
71 OSPF
Possible Causes
Procedure
----End
71.30 OSPF/4/GR_HLP_TIMER_FIRED
Message
OSPF/4/GR_HLP_TIMER_FIRED:OSPF [process-id] helper waits for timer to be fired,
because grace period expired on interface [interface-name].
Description
The helper waited for the timer to be activated for an interface.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
The helper waited for the timer to be activated for an interface.
Procedure
----End
71.31 OSPF/3/GR_IF_CHANGE
Message
OSPF/3/GR_IF_CHANGE:OSPF [process-id] exited GR mode as interface status changed.
(InterfaceName=[STRING], IpAddress=[IPADDR])
Description
The OSPF process exited from GR because the interface status changed.
Issue 07 (2014-07-30)

709

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
[process-id]
InterfaceName
IpAddress
Indicates the IP address.
Possible Causes
The OSPF process exited from GR because the interface status changed.
Procedure
----End
71.32 OSPF/4/GR_NOTIFYRM_EXIT_GR
Message
OSPF/4/GR_NOTIFYRM_EXIT_GR:OSPF [process-id] notified that RM process exited GR.
Description
The OSPF exited from GR and instructed RM to exit from GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The OSPF exited from GR and instructed RM to exit from GR.
Procedure
----End
71.33 OSPF/4/GR_RECV_1WAY_HELLO
Issue 07 (2014-07-30)

710

Log Reference
71 OSPF
Message
OSPF/4/GR_RECV_1WAY_HELLO:OSPF [process-id] exits GR mode as 1-way hello is
received from neighbor [neighbor-ip-address], on interface [interface-name].
Description
The OSPF process exited from GR after receiving a 1-way Hello packet from the neighbor.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
The OSPF process received a 1-way Hello packet.
Procedure
----End
71.34 OSPF/4/GR_START_GR
Message
OSPF/4/GR_START_GR:OSPF [process-id] starting IETF GR.........
Description
The OSPF process started GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The OSPF process started GR.
Issue 07 (2014-07-30)

711

Log Reference
71 OSPF
Procedure
----End
71.35 OSPF/4/HLP_EXIT_RECV_LSA
Message
OSPF/4/HLP_EXIT_RECV_LSA:OSPF [process-id] exits the helper mode because flooding
received changed LSA. (InterfaceName=[STRING], LsaType=[USHORT],
AdvertisingRouter=[IPADDR], LinkId=[IPADDR]).
Description
The OSPF process exited from the helper mode after receiving changed LSAs.
Parameters
Parameter Name
Parameter Meaning
[process-id]
InterfaceName
LsaType
Indicates the type of an LSA.
AdvertisingRouter
Indicates the advertising router.
LinkId
Indicates the ID of the link.
Possible Causes
Procedure
----End
71.36 OSPF/6/IF_CHG_E
Message
OSPF/6/IF_CHG_E:Interface [interface-address] received event [interface-event], interface
state changed from [interface-previous-state] to [interface-current-state]. (ProcessId=[processid])
Issue 07 (2014-07-30)

712

Log Reference
71 OSPF
Description
The interface status changed.
Parameters
Parameter Name
Parameter Meaning
[interface-address]
indicates the IP address of a neighbor.
[interface-event]
Indicates the events on the interface.
[interface-previous-state]
Indicates the previous status of the interface.
[interface-current-state]
Indicates the current status of the interface.
ProcessId
Possible Causes
Procedure
Step 1 Run the display ospf interface command to check status of the interface.
----End
71.37 OSPF/6/IF_TYPE_CHG
Message
OSPF/6/IF_TYPE_CHG:Physical interface type changed. (InterfaceName=[STRING],
InterfaceIndex=[STRING], PreviousPhysicalInterfaceType=[ULONG],
CurrentPhysicalInterfaceType=[ULONG])
Description
Information on the OSPF physical interface changed.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
InterfaceIndex
Indicates the index of an interface.
PreviousPhysicalInterfaceType
Indicates the previous physical type of an interface.
CurrentPhysicalInterfaceType
Indicates the current physical type of an interface.
Issue 07 (2014-07-30)

713

Log Reference
71 OSPF
Possible Causes
The type of the physical interface changed.
Procedure
----End
71.38 OSPF/3/INTF_EXIT_HLP_FAIL
Message
OSPF/3/INTF_EXIT_HLP_FAIL:OSPF [process-id] exiting interface level helper mode
unsuccessfully for Interface [interface-ip-address] due to [neighbor-information].
Description
The OSPF interface failed to exit from the interface-level helper mode.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the information of a neighbor.
Possible Causes
The OSPF interface failed to exit from the interface-level helper mode.
Procedure
----End
71.39 OSPF/6/INTF_NSR_EVENT
Message
OSPF/6/INTF_NSR_EVENT: Interface of the [STRING] received event [STRING], and NSR
state changed from [STRING] to [STRING]. (IfName=[STRING], IpAddr=[IPADDR],
ProcessId=[USHORT], AreaId=[STRING])
Issue 07 (2014-07-30)

714

Log Reference
71 OSPF
Description
The NSR state on an OSPF interface on the AMB or SMB changed.
Parameters
Parameter Name
Parameter Meaning
[STRING]
AMB or SMB to which an interface belongs
[STRING]
Event causing the NSR state of the interface to change
[STRING]
Previous NSR status of the interface
[STRING]
New NSR status of the interface
IfName
Interface name
IpAddr
Interface IP address
ProcessId
ID of the process to which the interface belongs
AreaId
ID of the area to which the interface belongs
Possible Causes
When the data on OSPF NSR interfaces was backed up, an OSPF interface on the AMB
communicated with an OSPF interface on the SMB or the communication between the two
interfaces was interrupted.
Procedure
----End
71.40 OSPF/4/INTF_NSR_OVERTIME_LIMIT
Message
OSPF/4/INTF_NSR_OVERTIME_LIMIT: The interface go on process, as slave's ack didn't
come for [ULONG] seconds. (IfName=[STRING1], IpAddr=[IPADDR], ProcessId=
[USHORT], AreaId=[STRING2])
Description
If the OSPF interface on the active board receives no response from the standby board within a
specified interval, the active board considers that the standby board has responded and does not
require retransmission of backup messages.
Issue 07 (2014-07-30)

715

Log Reference
71 OSPF
Parameters
[ULONG]
Total time that the interface waits for the response from the standby board,
in seconds
IfName
Interface name
IpAddr
IP address of the interface
ProcessId
Process ID to which the interface belongs
AreaId
Area ID to which the interface belongs
Possible Causes
After the OSPF interface on the active board initiates a handshake with the standby board, the
interface waits for a response from the standby board. If the total waiting time exceeds the upper
limit (equal to or less than 600 seconds, generally 40 times of the retransmission interval), it
may be caused by inconsistent OSPF interface statuses on the active board and the standby board,
blocked backup channel, or loss of backup messages.
Procedure
Step 1 Run the display ospf interface command to check whether the statuses of OSPF interfaces on
the active board and the standby board are consistent.
l If they are consistent, ignore this log message.
l If they are inconsistent, contact the Huawei technical support personnel.
----End
71.41 OSPF/6/ISSU_SMB_CMD_ERR
Message
OSPF/6/ISSU_SMB_CMD_ERR:The SMB failed to run Command ([command]).
Description
Failed to run the command on the SMB.
Parameters
Parameter Name
Parameter Meaning
[command]
Indicates the command fails to be run.
Possible Causes
Failed to run the command on the SMB.
Issue 07 (2014-07-30)

716

Log Reference
71 OSPF
Procedure
Step 2 If some commands are only used on the AMB, configure them on the SMB.
----End
71.42 OSPF/3/ISSU_SMOOTH_ACROSS
Message
OSPF/3/ISSU_SMOOTH_ACROSS:The OSPF backup module received the
ISSU_SMOOTH_ACROSS event from the ISSU management module.
Description
The message that recorded the ISSU_SMOOTH_ACROSS event was received during the OSPF
ISSU upgrade.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The message that recorded the ISSU_SMOOTH_ACROSS event was received during the ISSU
backup.
Procedure
----End
71.43 OSPF/3/ISSU_SMOOTH_INSIDE
Message
OSPF/3/ISSU_SMOOTH_INSIDE:The OSPF backup module received the
ISSU_SMOOTH_INSIDE event from the ISSU management module.
Issue 07 (2014-07-30)

717

Log Reference
71 OSPF
Description
The message that recorded the ISSU_SMOOTH_INSIDE event was received during the OSPF
ISSU upgrade.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The message that recorded the ISSU_SMOOTH_INSIDE event was received during the ISSU
backup.
Procedure
----End
71.44 OSPF/3/ISSU_SMOOTH_OVER
Message
OSPF/3/ISSU_SMOOTH_OVER:The OSPF backup module received the
ISSU_SMOOTH_OVER event from the ISSU management module.
Description
The message that recorded the ISSU_SMOOTH_OVER event was received during the OSPF
ISSU upgrade.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The message that recorded the ISSU_SMOOTH_OVER event was received during the ISSU
backup.
Procedure
----End
Issue 07 (2014-07-30)

718

Log Reference
71 OSPF
71.45 OSPF/6/JOIN_MULGRP_FAIL
Message
OSPF/6/JOIN_MULGRP_FAIL:Failed to join the multicast group. (MulticastGroup Address=
[IPADDR], ReturnValue=[STRING], InterfaceNetworkIndex=[ULONG], PhysicalIndex=
[ULONG], InterfaceName=[STRING])
Description
The OSPF interface failed to join the multicast group.
Parameters
Parameter Name
Parameter Meaning
Multicast group address
Indicates the multicast group address.
ReturnValue
Indicates the returned value.
InterfaceNetworkIndex
Indicates the index of the network where an interface resides.
PhysicalIndex
Indicates the index of a physical interface.
InterfaceName
Possible Causes
Failed to add an interface to the multicast group.
Procedure
Step 1 Check whether the multicast function on the interface was available.
----End
71.46 OSPF/6/LDP_INIT_EVENT
Message
OSPF/6/LDP_INIT_EVENT:Interface [interface-name] initial LDP synchronization state
[initial-state].
Description
The initial LDP synchronization state is recorded in this log message.
Issue 07 (2014-07-30)

719

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[initial-state]
Indicates the initial LDP synchronization state.
Possible Causes
The LDP synchronization is initialized.
Procedure
----End
71.47 OSPF/6/LDP_SYNC_CREA
Message
OSPF/6/LDP_SYNC_CREA:Interface [STRING] LDP synchronization hold maximum cost
timer created.
Description
The LDP synchronization hold max cost timer was created.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The LDP synchronization hold max cost timer was created.
Procedure
----End
71.48 OSPF/6/LDP_SYNC_EVENT
Issue 07 (2014-07-30)

720

Log Reference
71 OSPF
Message
OSPF/6/LDP_SYNC_EVENT:Interface [interface-name] received [ldp-synchronizationmessage] from RM, LDP synchronization state [previous-state] change to [current-state].
Description
The LDP synchronization state changed.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[ldp-synchronization-message]
Indicates an LDP synchronization message.
[previous-state]
Indicates the previous status of the local device.
[current-state]
Indicates the current status of the local device.
Possible Causes
The LDP synchronization state changed.
Procedure
----End
71.49 OSPF/6/LDP_SYNC_FIRE
Message
OSPF/6/LDP_SYNC_FIRE:Interface [interface-name] LDP synchronization hold maximum
cost timer expired.
Description
LDP synchronization hold max cost timer timed out.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
The hold max cost timer timed out.
Issue 07 (2014-07-30)

721

Log Reference
71 OSPF
Procedure
----End
71.50 OSPF/6/LEAVE_MULGRP_FAIL
Message
OSPF/6/LEAVE_MULGRP_FAIL:Failed to leave the multicast group.
(MulticastGroupAddress=[IPADDR], ReturnValue=[STRING], InterfaceNetworkIndex=
[ULONG], PhysicalIndex=[ULONG], InterfaceName=[STRING])
Description
The OSPF interface failed to leave the multicast group.
Parameters
Parameter Name
Parameter Meaning
MulticastGroupAddress
Indicates the multicast group address.
ReturnValue
InterfaceNetworkIndex
Indicates the index of the network where an interface resides.
PhysicalIndex
Indicates the index of a physical interface.
InterfaceName
Possible Causes
The interface failed to leave the multicast group.
Procedure
Step 1 Check whether the multicast function on the interface was available.
----End
71.51 OSPF/5/LSA_CHANGE_FREQUENT
Message
OSPF/5/LSA_CHANGE_FREQUENT: LSAs change frequently now. (ProcessId=[USHORT],
AdvertiseRouterId=[IPADDR], TotalCount=[ULONG], BeginTime=[STRING], EndTime=
[STRING], Type-1LsaCount=[ULONG], Type-2LsaCount=[ULONG], Type-3LsaCount=
[ULONG], Type-4LsaCount=[ULONG], Type-5LsaCount=[ULONG], Type-7LsaCount=
Issue 07 (2014-07-30)

722

Log Reference
71 OSPF
[ULONG], Type-9LsaCount=[ULONG], Type-10LsaCount=[ULONG], Type-11LsaCount=

[ULONG])
Description
LSAs were frequently updated.
Parameters
Parameter Name
Parameter Meaning
ProcessId
Process ID
AdvertiseRouterId
Advertising router ID
TotalCount
Total number of LSA updates
BeginTime
Begin time for counting
EndTime
End time for counting
Type-1LsaCount
Number of updates for a router LSA
Type-2LsaCount
Number of updates for a network LSA
Type-3LsaCount
Number of updates for a summary-network LSA
Type-4LsaCount
Number of updates for a summary-ASBR LSA
Type-5LsaCount
Number of updates for an ASE LSA
Type-7LsaCount
Number of updates for type-7 LSA
Type-9LsaCount
Type-10LsaCount
Type-11LsaCount
Possible Causes
An advertising router calculated the number of updates for LSAs and the results were recorded
once an hour. Select the top 10 history records based on the number of updates for LSAs. The
total number of updates for LSAs exceeded 100.
Procedure
Step 1 This trap message is informational only, and no action is required.
----End
71.52 OSPF/3/MISMATCH_HELPER_FAIL
Issue 07 (2014-07-30)

723

Log Reference
71 OSPF
Message
OSPF/3/MISMATCH_HELPER_FAIL:OSPF [process-id] can not enter helper mode,
neighbor-ID mismatch with restarting neighbor [interface-name].
Description
The OSPF process cannot enter the helper mode because the neighbor ID saved on the local side
did not match the neighbor ID contained in the grace LSA sent by the restarter.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
The OSPF process cannot enter the helper mode because the neighbor ID did not match the
neighbor ID contained in the grace LSA sent by the restarter.
Procedure
----End
71.53 OSPF/4/NBR_CHANGE_E
Message
OSPF/4/NBR_CHANGE_E:Neighbor changes event: neighbor status changed. (ProcessId=
[process-id], NeighborAddress=[neighbor-address], NeighborEvent=[neighbor-event],
NeighborPreviousState=[neighbor-previous-state], NeighborCurrentState=[neighbor-currentstate])
Description
The neighbor status changed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
NeighborAddress
NeighborEvent
Issue 07 (2014-07-30)

724

Log Reference
71 OSPF
Parameter Name
Parameter Meaning
NeighborPreviousState
Indicates the previous status of a neighbor.
NeighborCurrentState
Indicates the current status of a neighbor.
Possible Causes
The neighbor status changed.
Procedure
----End
71.54 OSPF/3/NBR_CHG_DOWN
Message
OSPF/3/NBR_CHG_DOWN: Neighbor event: neighbor state changed to Down. (ProcessId=
[USHORT], NeighborAddress=[IPADDR], NeighborEvent=[STRING],
NeighborPreviousState=[STRING], NeighborCurrentState=[STRING])
Description
The neighbor turned Down.
Parameters
Parameter Name
Parameter Meaning
ProcessId
NeighborAddress
NeighborEvent
Indicates the event triggered by a neighbor.
Possible Causes
The neighbor status changed because the neighbor received an OSPF message or the event
affecting the neighbor relationship occurred.
Procedure
----End
Issue 07 (2014-07-30)

725

Log Reference
71 OSPF
71.55 OSPF/3/NBR_DOWN_REASON
Message
OSPF/3/NBR_DOWN_REASON:Neighbor state leaves full or changed to Down. (ProcessId=
[USHORT], NeighborRouterId=[IPADDR], NeighborAreaId=[ULONG], NeighborInterface=
[STRING],NeighborDownImmediate reason=[STRING], NeighborDownPrimeReason=
[STRING], NeighborChangeTime=[STRING])
Description
Parameters
Parameter Name
Parameter Meaning
ProcessId
NeighborRouterId
Indicates the ID of a neighbor router.
NeighborAreaId
Indicates the IP address of an area.
NeighborInterface
Indicates a neighbor interface.
NeighborDownImmediate reason Indicates the direct reason that the neighbor turns down.
NeighborDownPrimeReason
Indicates the original reason that the neighbor turns down.
NeighborChangeTime
Indicates the time when the neighbor status changes.
Possible Causes
The neighbor status changed because the neighbor received an OSPF message or the event
affecting the neighbor relationship occurred.
Procedure
----End
71.56 OSPF/4/NBR_STATE_HELPER_F
Message
OSPF/4/NBR_STATE_HELPER_F:OSPF [process-id] cannot enter the helper mode because
neighbor status of the restarting neighbor [neighbor-ip-address] is not FULL.
Issue 07 (2014-07-30)

726

Log Reference
71 OSPF
Description
The OSPF process cannot enter the helper mode because the restarter status is not Full.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The OSPF process cannot enter the helper mode because the restarter status is not Full.
Procedure
----End
71.57 OSPF/6/NOTIFY_DEL_FINISHED
Message
OSPF/6/NOTIFY_DEL_FINISHED: OSPF has finished deleting all routes and notified route
management. (Instance ID=[USHORT])
Description
The OSPF instance notified the routing management module that all routes had been deleted.
Parameters
Parameter Name
Parameter Meaning
Instance ID
Possible Causes
The limit on the maximum number of route prefixes was changed, and the number of route
prefixes exceeded the limit.
Procedure
----End
Issue 07 (2014-07-30)

727

Log Reference
71 OSPF
71.58 OSPF/4/NOTIFYRM_ENTER_GR
Message
OSPF/4/NOTIFYRM_ENTER_GR:OSPF [process-id] notified RM that it started GR.
Description
OSPF notified RM that it started GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
OSPF started GR.
Procedure
----End
71.59 OSPF/6/NSR_AMB_BAKOVER_INFO
Message
OSPF/6/NSR_AMB_BAKOVER_INFO: The AMB received acknowledgement from the SMB,
and then notified RM that batch backup was complete.
Description
The AMB received acknowledgement from the SMB, and then notified RM that batch backup
was complete.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Issue 07 (2014-07-30)

728

Log Reference
71 OSPF
Possible Causes
The AMB received acknowledgement from the SMB, and then notified RM that batch backup
was complete
Procedure
----End
71.60 OSPF/6/NSR_AMB_BCHOVER_INFO
Message
OSPF/6/NSR_AMB_BCHOVER_INFO: The AMB notified the SMB that all processes finished
batch backup, and then waited for the acknowledgement.
Description
The AMB notified the SMB that all processes finished batch backup, and then waited for the
acknowledgement.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
The AMB notified the SMB that all processes finished batch backup, and then waited for the
acknowledgement.
Procedure
----End
71.61 OSPF/6/NSR_AMB_ENWARM_INFO
Message
OSPF/6/NSR_AMB_ENWARM_INFO: RM was notified that process [USHORT] entered the
NSR-WarmUp phase.
Issue 07 (2014-07-30)

729

Log Reference
71 OSPF
Description
An OSPF process notified RM that it entered the NSR-WarmUp phase.
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Process ID
Possible Causes
After an AMB/SMB switchover, the new AMB started the NSR-WarmUp process.
Procedure
----End
71.62 OSPF/6/NSR_AMB_EXWARM_INFO
Message
OSPF/6/NSR_AMB_EXWARM_INFO: RM was notified that process [USHORT] exited the
NSR-WarmUp phase.
Description
An OSPF process notified RM that it exited from the NSR-WarmUp phase.
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Process ID
Possible Causes
After an AMB/SMB switchover, the new AMB completed the NSR-WarmUp process.
Procedure
----End
71.63 OSPF/6/NSR_AMB_GROVER_INFO
Issue 07 (2014-07-30)

730

Log Reference
71 OSPF
Message
OSPF/6/NSR_AMB_GROVER_INFO: Instance [USHORT] received the notification from RM
that WarmUp was complete.
Description
An instance received a notification from RM that the NSR-WarmUp process was complete.
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Instance ID
Possible Causes
RM notified the instance that the NSR-WarmUp process was complete.
Procedure
----End
71.64 OSPF/6/NSR_AMB_RM_INFO
Message
OSPF/6/NSR_AMB_RM_INFO: OSPF NSR received [STRING] notification from RM.
Description
OSPF NSR received a series of notifications from RM.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Type of notifications received from RM
Possible Causes
During normal operation, OSPF NSR received a series of notifications from RM.
Procedure
----End
Issue 07 (2014-07-30)

731

Log Reference
71 OSPF
71.65 OSPF/6/NSR_AMB_RMCHK_INFO
Message
OSPF/6/NSR_AMB_RMCHK_INFO: OSPF notified RM that batch backup check is finished.
Description
OSPF notified RM that batch backup check was finished.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
OSPF notified RM that batch backup check was finished.
Procedure
----End
71.66 OSPF/6/NSR_AREARECV_DATA
Message
OSPF/6/NSR_AREARECV_DATA: The AMB notified SMB that area [ULONG]'s data is
acceptable now. (InstanceId=[USHORT], ProcId=[USHORT])
Description
The AMB notified the SMB that the area's data can be accepted.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Area ID
InstanceId
Instance ID
ProcId
Process ID
Issue 07 (2014-07-30)

732

Log Reference
71 OSPF
Possible Causes
NSR was enabled and the OSPF area was restarted.
Procedure
----End
71.67 OSPF/6/NSR_AREARECV_INFO
Message
OSPF/6/NSR_AREARECV_INFO: The SMB received the notification from the AMB. Now
area [ULONG]'s data is acceptable. (InstanceId=[USHORT], ProcId=[USHORT])
Description
The SMB received a notification from the AMB that the area's data can be accepted.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Area ID
InstanceId
Instance ID
ProcId
Process ID
Possible Causes
Procedure
----End
71.68 OSPF/6/NSR_AREARESET_INFO
Message
OSPF/6/NSR_AREARESET_INFO: The AMB received the notification from the SMB. Now
area [ULONG] can be activated or freed. (InstanceId=[USHORT], ProcId=[USHORT])
Issue 07 (2014-07-30)

733

Log Reference
71 OSPF
Description
The AMB received a notification from the SMB that the area can be activated or released.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Area ID
InstanceId
Instance ID
ProcId
Process ID
Possible Causes
Procedure
----End
71.69 OSPF/6/NSR_PROCRECV_DATA
Message
OSPF/6/NSR_PROCRECV_DATA: The AMB notified the SMB that process [USHORT]'s data
is acceptable now . (InstanceId=[USHORT])
Description
The AMB notified the SMB that the process's data can be accepted.
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Process ID
InstanceId
Instance ID
Possible Causes
Issue 07 (2014-07-30)

734

Log Reference
71 OSPF
Procedure
----End
71.70 OSPF/6/NSR_PROCRECV_INFO
Message
OSPF/6/NSR_PROCRECV_INFO: The SMB received the notification from the AMB. Now
process [USHORT]'s data is acceptable. (InstanceId=[USHORT])
Description
The SMB received a notification from the AMB that the process's data can be accepted.
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Process ID
InstanceId
Instance ID
Possible Causes
Procedure
----End
71.71 OSPF/6/NSR_PROCRESET_INFO
Message
OSPF/6/NSR_PROCRESET_INFO: The AMB received the notification from the SMB. Now
process [USHORT] can be activated or freed. (InstanceId=[USHORT])
Description
The AMB received a notification from the SMB that the process can be activated or released.
Issue 07 (2014-07-30)

735

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Process ID
InstanceId
Instance ID
Possible Causes
Procedure
----End
71.72 OSPF/6/NSR_SMB_BATCH_INFO
Message
OSPF/6/NSR_SMB_BATCH_INFO: The SMB received the notification from the AMB that
batch backup is complete.
Description
The SMB received a notification from the AMB that batch backup was complete.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
The AMB notified the SMB that batch backup was complete.
Procedure
----End
71.73 OSPF/6/NSR_SMB_GLOBAL_INFO
Issue 07 (2014-07-30)

736

Log Reference
71 OSPF
Message
OSPF/6/NSR_SMB_GLOBAL_INFO: The SMB received the notification from the AMB that
global data backup is complete.
Description
The SMB received a notification from the AMB that global data backup was complete.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
The AMB notified the SMB that global data backup was complete.
Procedure
----End
71.74 OSPF/6/NSSA_STATE_ELECT
Message
OSPF/6/NSSA_STATE_ELECT:The status of the NSSA translator is set to [STRING].
(ProcessId=[USHORT], AreaId=[IPADDR])
Description
The state of the Not-So-Stubby Area (NSSA) translator was set to elected, enable, or disable.
Parameters
[STRING]
The state of the Not-So-Stubby Area (NSSA) translator was set to elected,
enable, or disable.
Process ID
Area ID
Possible Causes
A router was elected as the translator in the NSSA.
Issue 07 (2014-07-30)

737

Log Reference
71 OSPF
Procedure
----End
71.75 OSPF/6/ONE_IF_EXIT_WAITING
Message
OSPF/6/ONE_IF_EXIT_WAITING:OSPF [process-id] Interface [interface-name] exits
waiting state, interface in waiting state count is [waitng-state-count].
Description
The OSPF interface exited from the Waiting state, and the number of interfaces in the Waiting
state is X.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[Interface-name]
[waitng-state-count]
Indicates the number of nodes in the Waiting state.
Possible Causes
The OSPF process finished GR with the neighbor on the sham link.
Procedure
----End
71.76 OSPF/4/ONEIF_ENTER_WAITING
Message
OSPF/4/ONEIF_ENTER_WAITING:OSPF [process-id] interface [interface-name] enters
waiting state, waiting state count is [interface-in-waiting-state-number].
Description
The interface entered the Waiting state. The number of the interfaces in the Waiting state is
recorded in this log.
Issue 07 (2014-07-30)

738

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[interface-in-waiting-state-number] Indicates the number of the interfaces that enter the

Waiting state.
[process-id]
Possible Causes
The interface received the Hello packet or the Waiting timer timed out.
Procedure
----End
71.77 OSPF/3/PAF_TYPE_LOSS_ISSU
Message
OSPF/3/PAF_TYPE_LOSS_ISSU:OSPF performs lossy upgrade because of the inconsistent
PAF [paf] file.
Description
A PAF item that affected the upgrade was detected during the OSPF ISSU upgrade.
Parameters
Parameter Name
Parameter Meaning
[paf]
Indicates a configuration item in the PAF file.
Possible Causes
The inconsistent PAF configuration item was detected during the ISSU checking.
Procedure
Step 1 Record PAF items that affect system upgrade and contact the Huawei technical support
personnel.
----End
Issue 07 (2014-07-30)

739

Log Reference
71 OSPF
71.78 OSPF/4/PLCY_FAIL_HELPER_F
Message
OSPF/4/PLCY_FAIL_HELPER_F:OSPF [process-id] cannot enter the helper mode because
configuring policies for restarting peer [interface-name] failed.
Description
The OSPF cannot enter the helper mode because configuring policies for the restarting peer
failed.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
The OSPF cannot enter the helper mode because configuring policies for the restarting peer
failed.
Procedure
----End
71.79 OSPF/6/RCV_MEM_RESTORE
Message
OSPF/6/RCV_MEM_RESTORE:OSPF received memory restoration notification.
Description
OSPF received the memory restoration notification.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

740

Log Reference
71 OSPF
Possible Causes
Memory shortage was restored.
Procedure
Step 1 Check the memory usage on the router.
----End
71.80 OSPF/6/RCV_RM_EVNT
Message
OSPF/6/RCV_RM_EVNT:OSPF(AMB) backup process receive [RM-backup-event] event
from RM. (SlaveHsbState=[ULONG])
Description
OSPF received a backup event from the RM.
Parameters
Parameter Name
Parameter Meaning
[RM-backup-event]
Indicates the backup events received from the RM.
SlaveHsbState
Indicates the hot standby state of the slave board.
Possible Causes
The slave board started to backing up data.
Procedure
----End
71.81 OSPF/4/RECV_DIFF_GRACE_LSA
Message
OSPF/4/RECV_DIFF_GRACE_LSA:OSPF [process-id] receives a grace LSA different from
the one in LSDB on interface [interface-ip-address].
Description
The interface received a Grace LSA during GR.
Issue 07 (2014-07-30)

741

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
When performing GR, the restarter received a grace LSA different from the one in the LSDB
from the other router or the helper received a grace LSA different from the one in the LSDB
from its neighbor router.
Procedure
----End
71.82 OSPF/4/RECV_FIRST_GLSA
Message
OSPF/4/RECV_FIRST_GLSA:OSPF [process-id] attempted to enter helper mode and received
first grace LSA from neighbor [neighbor-ip-address], on interface [interface-ip-address].
Description
The helper received a grace LSA from the restarter.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
The restarter wanted to perform GR.
Procedure
----End
Issue 07 (2014-07-30)

742

Log Reference
71 OSPF
71.83 OSPF/6/RECV_ROUT_LIMIT_MSG
Message
OSPF/6/RECV_ROUT_LIMIT_MSG: OSPF received route limit message from route
management. (Instance ID=[USHORT], Message Type=[STRING])
Description
The routing management module notified the OSPF instance to delete or re-add routes.
Parameters
Parameter Name
Parameter Meaning
Instance ID
Message Type
Possible Causes
The limit on the maximum number of route prefixes was changed, and the number of route
prefixes exceeded the limit.
Procedure
----End
71.84 OSPF/6/RECV_SMB_DOWN_RM
Message
OSPF/6/RECV_SMB_DOWN_RM:OSPF backup receives slave mainboard Down event from
RM. (SlaveHsbState=[ULONG])
Description
OSPF backed up the message received from the RM. The message notified that data smooth
finished.
Parameters
Parameter Name
Parameter Meaning
SlaveHsbState
Issue 07 (2014-07-30)

743

Log Reference
71 OSPF
Possible Causes
OSPF backed up the message received from the RM. The message notified that data smooth
finished.
Procedure
----End
71.85 OSPF/6/RECV_SMOOTH_OVER_RM
Message
OSPF/6/RECV_SMOOTH_OVER_RM:OSPF backup receives smooth over event from RM.
(SlaveHsbState=[ULONG])
Description
OSPF backed up the synchronization-cross event received from the RM.
Parameters
Parameter Name
Parameter Meaning
SlaveHsbState
Possible Causes
OSPF backed up the synchronization-cross messages received from the RM.
Procedure
----End
71.86 OSPF/6/RECV_SWITCH_RM
Message
OSPF/6/RECV_SWITCH_RM:OSPF backup receives switch event from RM. (SlaveHsbState=
[ULONG])
Issue 07 (2014-07-30)

744

Log Reference
71 OSPF
Description
OSPF backed up the event received from the RM. The message notified that the slave board was
Down.
Parameters
Parameter Name
Parameter Meaning
SlaveHsbState
Possible Causes
OSPF backed up the message received from the RM. The message notified that the slave board
was Down.
Procedure
----End
71.87 OSPF/6/RECV_SYNC_ACROSS_RM
Message
OSPF/6/RECV_SYNC_ACROSS_RM:OSPF backup receives synchronization across event
from RM. (SlaveHsbState=[ULONG])
Description
RM returned an error code.
Parameters
Parameter Name
Parameter Meaning
SlaveHsbState
Possible Causes
RM returned an error code.
Procedure
----End
Issue 07 (2014-07-30)

745

Log Reference
71 OSPF
71.88 OSPF/3/RECV_TWO_GRACELSA
Message
OSPF/3/RECV_TWO_GRACELSA:OSPF [process-id] exited GR mode as grace LSA received
from neighbor [neighbor-ip-address], on interface [interface-name].
Description
The OSPF process exited from GR after receiving a grace LSA from a neighbor.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Procedure
----End
71.89 OSPF/6/RESET_SCHEDULE
Message
OSPF/6/RESET_SCHEDULE:OSPF [USHORT] reset schedule table. (ScheduleType=
[STRING])
Description
OSPF reset the schedule table.
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Indicates the OSPF process.
Issue 07 (2014-07-30)

746

Log Reference
71 OSPF
Parameter Name
Parameter Meaning
ScheduleType
Indicates the schedule type.
Possible Causes
OSPF reset the schedule table.
Procedure
----End
71.90 OSPF/6/RESTORE_AFTER_CFM
Message
OSPF/6/RESTORE_AFTER_CFM:OSPF restored data in batches after CFM.
Description
OSPF started to restore the data in batches.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
71.91 OSPF/6/RESTORE_BEFORE_CFM
Message
OSPF/6/RESTORE_BEFORE_CFM:OSPF restored data in batches before CFM.
Issue 07 (2014-07-30)

747

Log Reference
71 OSPF
Description
OSPF started to restore data in batches before the data was restored by using command lines.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
71.92 OSPF/6/RM_GETROUTERID
Message
OSPF/6/RM_GETROUTERID:Invoking the RM GetRouterID failed. (FID=[STRING], LN=
[ULONG], ReturnValue=[STRING])
Description
Failed to invoke the RM GetRouterID.
Parameters
Parameter Name
Parameter Meaning
FID
Indicates the ID of a file.
LN
Indicates the row ID.
ReturnValue
Possible Causes
Failed to invoke the RM GetRouterID.
Procedure
----End
Issue 07 (2014-07-30)

748

Log Reference
71 OSPF
71.93 OSPF/6/RM_IM
Message
OSPF/6/RM_IM:Invoking the RM IM failed. (FID=[STRING], LN=[ULONG], ReturnValue=
[STRING])
Description
Failed to invoke the RM IM.
Parameters
Parameter Name
Parameter Meaning
FID
Indicates the ID of a file.
LN
Indicates the row ID.
ReturnValue
Possible Causes
Failed to invoke the RM IM.
Procedure
----End
71.94 OSPF/4/RST_NBR_IN_PTIAL_GR
Message
OSPF/4/RST_NBR_IN_PTIAL_GR:OSPF [process-id] entered the partial GR mode and exited
GR for neighbor [neighbor-information] on [network-type] interface [interface-name].
Description
The OSPF process entered the partial GR mode and exited GR.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

749

Log Reference
71 OSPF
Parameter Name
Parameter Meaning
Indicates the IP address of an neighbor.
[network-type]
Indicates the type of a network.
[Interface-name]
Possible Causes
The OSPF process entered the partial GR mode and exited GR.
Procedure
----End
71.95 OSPF/4/RTRLSA_BACKLINK_FAIL
Message
OSPF/4/RTRLSA_BACKLINK_FAIL:OSPF [process-id] exits GR mode as Back link
checking failed on neighbor [neighbor-ip-address], on interface [interface-name].
Description
The OSPF process exited from GR after the back link check of the LSA received from the
neighbor failed.
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interface-name]
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

750

Log Reference
71 OSPF
71.96 OSPF/6/SHAMLINK_IF_CHG_E
Message
OSPF/6/SHAMLINK_IF_CHG_E:Shamlink interface [shamlink-interface-address] received
event [interface-event], interface state changed from [interface-previous-state] to [interfacecurrent-state]. (ProcessId=[USHORT])
Description
The interface on the sham link [Slink-int] changed from the state [pre-state] to the state [curstate] after receiving an event [event].
Parameters
Parameter Name
Parameter Meaning
[shamlink-interface-address] Indicates the IP address of the interface on the shamlink link.

[interface-event]
ProcessId
Possible Causes
The status of the interface on the shame link changed.
Procedure
----End
71.97 OSPF/4/SHAMLINK_NBR_CHG_E
Message
OSPF/4/SHAMLINK_NBR_CHG_E:Shamlink peer event: neighbor status changed.
(ProcessId=[USHORT], ShamlinkNeighborAddress=[IPADDR], NeighborEvent=[STRING],
Issue 07 (2014-07-30)

751

Log Reference
71 OSPF
Description
The status of the neighboring node on the sham link changed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
ShamlinkNeighborAddress Indicates the IP addresses of neighboring nodes on the sham link.

NeighborEvent
Indicates the events received by the neighboring node.
Indicates the previous status of the neighboring node.
Indicates the current status of the neighboring node.
Possible Causes
The status of the neighboring node on the sham link changed.
Procedure
Step 1 Run the display ospf peer command to check the status of the neighbor.
----End
71.98 OSPF/3/SHAMLINK_NBR_DOWN
Message
OSPF/3/SHAMLINK_NBR_DOWN:Shamlink neighbor event: neighbor state changed to
Down. (ProcessId=[USHORT], NeighborAddress=[IPADDR], NeighborEvent=[STRING],
Description
Parameters
Parameter Name
Parameter Meaning
ProcessId
NeighborAddress
NeighborEvent
Issue 07 (2014-07-30)

752

Log Reference
71 OSPF
Parameter Name
Parameter Meaning
Possible Causes
The neighbor on the sham link turned Down because the neighbor received an OSPF message
or the event affecting the neighbor relationship occurred.
Procedure
----End
71.99 OSPF/6/SINTF_NSR_EVENT
Message
OSPF/6/SINTF_NSR_EVENT: Shamlink interface of the [board-name] received event [event],
and NSR state changed from [previous-state] to [current-state]. (DestIp=[STRING], SourceIp=
[IPADDR], ProcessId=[USHORT], AreaId=[STRING])
Description
The NSR state of an interface over a sham link on a master or slave main control board changed.
Parameters
[board-name]
Indicates the master or slave main control board on which the interface
over the sham link resides.
[event]
Indicates the event that triggers the NSR state change of the interface over
the sham link.
[previous-state]
Indicates the original NSR state.
[current-state]
Indicates the new NSR state.
DestIp
Indicates the destination IP address of the sham link.
SourceIp
Indicates the source IP address of the sham link.
ProcessId
Indicates the ID of the process to which the interface over the sham link
belongs.
AreaId
Indicates the ID of the area to which the interface over the sham link
belongs.
Issue 07 (2014-07-30)

753

Log Reference
71 OSPF
Possible Causes
Packets were exchanged or the exchange was disabled during data backup between the interfaces
over sham links on the master and slave main control boards.
Procedure
----End
71.100 OSPF/4/SINTF_NSR_OVERTIME_LIMIT
Message
OSPF/4/SINTF_NSR_OVERTIME_LIMIT: The shamlink interface go on process, as slave's
ack didn't come for [ULONG] seconds. (DestIp=[STRING], SourceIp=[IPADDR], ProcessId=
[USHORT], AreaId=[STRING])
Description
If the OSPF sham link interface on the active board receives no response from the standby board
within a specified interval, the active board considers that the standby board has responded and
does not require retransmission of backup messages.
Parameters
[ULONG]
Total time that the sham link interface waits for the response from the
standby board, in seconds
DestIp
Destination IP address of the sham link interface
SourceIp
IP address of the sham link interface
ProcessId
Process ID to which the sham link interface belongs
AreaId
Area ID to which the sham link interface belongs
Possible Causes
After the sham link interface on the active board initiates a handshake with the standby board,
the interface waits for a response from the standby board. If the total waiting time exceeds the
upper limit (equal to or less than 600 seconds, generally 40 times of the retransmission interval),
it may be caused by inconsistent OSPF interface statuses on the active board and the standby
board, blocked backup channel, or loss of backup messages.
Procedure
Step 1 Run the display ospf sham-link command to check whether the statuses of sham link interfaces
on the active board and the standby board are consistent.
Issue 07 (2014-07-30)

754

Log Reference
71 OSPF

----End
71.101 OSPF/6/SMB_GETSESSION_ERR
Message
OSPF/6/SMB_GETSESSION_ERR: The SMB failed to get the destination of backup
information. (SessionType=[USHORT], DataLen=[USHORT], Key1=[ULONG], Key2=
[ULONG], Key3=[ULONG], Key4=[ULONG], Key5=[ULONG], ErrCode=[ULONG])
Description
The SMB failed to get the destination of backup information.
Parameters
Parameter Name
Parameter Meaning
SessionType
Backup data type
DataLen
Backup data length
Key1
Key word 1 of backup data
Key2
Key3
Key4
Key5
ErrCode
Error code
Possible Causes
The SMB failed to get the destination of backup data and cannot accept the backup data.
Procedure
Step 1 No action is required generally. If an exception occurs, the log message can be used as a
reference.
----End
71.102 OSPF/6/SMB_NSR_AREA_INFO
Issue 07 (2014-07-30)

755

Log Reference
71 OSPF
Message
OSPF/6/SMB_NSR_AREA_INFO: The SMB notified the AMB to activate or free area
[ULONG]. (InstanceId=[USHORT], ProcId=[USHORT])
Description
The SMB notified the AMB that the area can be activated or released.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Area ID
InstanceId
Instance ID
ProcId
Process ID
Possible Causes
Procedure
----End
71.103 OSPF/6/SMB_NSR_PROC_INFO
Message
OSPF/6/SMB_NSR_PROC_INFO: The SMB notified the AMB to activate or free process
[process-id]. (InstanceId=[USHORT])
Description
The slave main control board notified the master main control board to activate or release an
OSPF process.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates a process ID.
InstanceId
Issue 07 (2014-07-30)

756

Log Reference
71 OSPF
Possible Causes
The OSPF process was restarted during NSR.
Procedure
Step 1 This log informational only, and no action is required.
----End
71.104 OSPF/6/STUB_RT_EX_UD_STUB
Message
OSPF/6/STUB_RT_EX_UD_STUB:OSPF [process-id] quits stub router state by undoing stub.
Description
The local device left the Stub state.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
71.105 OSPF/6/STUB_RT_ONBT_TM_CRT
Message
OSPF/6/STUB_RT_ONBT_TM_CRT:OSPF [process-id] creates TIMER of [interval-for-stubstate] seconds to measure stub router state.
Description
The local device became a stub router.
Issue 07 (2014-07-30)

757

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
[process-id]
[interval-for-stub-state]
Indicates the timeout period of the timer of stub router status.
Possible Causes
The local device entered the Stub state.
Procedure
----End
71.106 OSPF/6/STUB_RT_STUB_ALW
Message
OSPF/6/STUB_RT_STUB_ALW:OSPF [USHORT] deletes the stub router timer, as new
configuration is always stub.
Description
The OSPF process deleted the stub router timer.
Parameters
Parameter Name
Parameter Meaning
[USHORT]
Possible Causes
The OSPF process deleted the stub router timer.
Procedure
----End
71.107 OSPF/6/STUB_RT_TM_FIRE
Issue 07 (2014-07-30)

758

Log Reference
71 OSPF
Message
OSPF/6/STUB_RT_TM_FIRE:OSPF [process-id] quits stub router state for overtime.
Description
Parameters
Parameter Name
Parameter Meaning
[process-id]
Possible Causes
Procedure
----End
71.108 OSPF/6/TRAP_AGE_LSA
Message
OSPF/6/TRAP_AGE_LSA:Notify LSA aged out. (ProcessId=[USHORT], RouterId=
[IPADDR], LsdbAreaId=[IPADDR], LsdbType=[ULONG], LsdbLsId=[IPADDR],
LsdbRouterId=[IPADDR])
Description
OSPF notified that the LSA aged out.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
LsdbAreaId
Indicates the area ID of the LSDB.
LsdbType
Indicates the type of the LSDB.
LsdbLsId
Indicates the ID of an LSA in the LSDB.
LsdbRouterId
Indicates the ID of a router in the LSDB.
Issue 07 (2014-07-30)

759

Log Reference
71 OSPF
Possible Causes
OSPF notified that the LSA aged out.
Procedure
----End
71.109 OSPF/6/TRAP_HELPER_CHG
Message
OSPF/6/TRAP_HELPER_CHG:Notify the change in restart helper. (ProcessId=[USHORT],
RouterId=[IPADDR], NeighborIpAddress=[IPADDR], NeighborAddressLessIndex=
[ULONG], NeighborRouterId=[IPADDR], NeighborRestartHelperStatus=[ULONG],
NeighborRestartHelperAge=[ULONG], NeighborRestartHelperExitReason=[ULONG])
Description
OSPF notified that the status of the GR helper changed.
Parameters
Parameter Name
Parameter Meaning
Process ID
RouterId
NeighborIpAddress
NeighborAddressLessIndex
Indicates the index of the IP address of a neighbor.
NeighborRouterId
NeighborRestartHelperStatus
Indicates the status of the neighbor GR helper.
NeighborRestartHelperAge
Indicates the duration of the neighbor GR helper.
NeighborRestartHelperExitReason Indicates the reason why the neighbor exits from the GR
helper.
Possible Causes
OSPF notified that the status of the GR helper changed.
Procedure
----End
Issue 07 (2014-07-30)

760

Log Reference
71 OSPF
71.110 OSPF/4/TRAP_INTF_AUTH_FAIL
Message
OSPF/4/TRAP_INTF_AUTH_FAIL:Interface authentication has failed. (ProcessId=
[USHORT], RouterId=[IPADDR], IpAddress=[IPADDR], AddressLessIndex=[ULONG],
PacketSource=[IPADDR], ErrorType=[ULONG], PacketType=[ULONG])
Description
The interface authentication failed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
IpAddress
AddressLessIndex
Indicates the index of the IP address.
PacketSource
ErrorType
Indicates the error type.
PacketType
Indicates the packet type.
Possible Causes
The interface authentication failed.
Procedure
Step 1 Run the display ospf interface command to check the authentication configuration of the virtual
interface and the neighbor router.
----End
71.111 OSPF/6/TRAP_INTF_BAD_RX
Message
OSPF/6/TRAP_INTF_BAD_RX:Interface received bad packet. (ProcessId=[USHORT],
RouterId=[IPADDR], IpAddress=[IPADDR], AddressLessIndex=[ULONG], PacketSource=
[IPADDR], PacketType=[ULONG])
Issue 07 (2014-07-30)

761

Log Reference
71 OSPF
Description
An error packet was received on the interface.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
IpAddress
AddressLessIndex
PacketSource
PacketType
Possible Causes
An error packet was received on the interface.
Procedure
Step 1 Check the source address of the error packet.
----End
71.112 OSPF/4/TRAP_INTF_CFG_ERR
Message
OSPF/4/TRAP_INTF_CFG_ERR:Interface configuration error has occurred. (ProcessId=
[USHORT], RouterId=[IPADDR], IpAddress=[IPADDR], AddressLessIndex=[ULONG],
PacketSource=[IPADDR], ErrorType=[ULONG], PacketType=[ULONG])
Description
The interface was incorrectly configured.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
IpAddress
Issue 07 (2014-07-30)

762

Log Reference
71 OSPF
Parameter Name
Parameter Meaning
AddressLessIndex
PacketSource
ErrorType
PacketType
Possible Causes
The interface was incorrectly configured.
Procedure
Step 1 Run the display ospf interface command to check the configuration of the interface.
----End
71.113 OSPF/6/TRAP_INTF_CHG
Message
OSPF/6/TRAP_INTF_CHG:Interface state has changed. (ProcessId=[USHORT], RouterId=
[IPADDR], IpAddress=[IPADDR], InterfaceIndex=[ULONG], InterfaceState=[ULONG])
Description
Parameters
Parameter Name
Parameter Meaning
Process Id
RouterId
IpAddress
InterfaceIndex
InterfaceState
Indicates the status of an interface.
Possible Causes
Issue 07 (2014-07-30)

763

Log Reference
71 OSPF
Procedure
----End
71.114 OSPF/6/TRAP_INTF_RETX
Message
OSPF/6/TRAP_INTF_RETX:Interface has retransmitted. (ProcessId=[USHORT], RouterId=
[IPADDR], IpAddress=[IPADDR], AddressLessIndex=[ULONG], NeighborRouterId=
[IPADDR], PacketType=[ULONG], NeighborIpAddress=[IPADDR],
NeighborAddressLessIndex=[ULONG], LsdbAreaId=[IPADDR], LsdbType=[ULONG],
LsdbLsId=[IPADDR], LsdbRouterId=[IPADDR])
Description
Packets were resent through the interface.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
IpAddress
AddressLessIndex
NeighborRouterId
PacketType
Indicates the type of the packet.
NeighborIpAddress
NeighborAddressLessIndex Indicates the index of the IP address of a neighbor.

LsdbAreaId
Indicates the area ID of an LSA in the Link-State DataBase

(LSDB).
LsdbType
Indicates the type of an LSA in the LSDB.
LsdbLsId
LsdbRouterId
Indicates the router ID in the LSDB.
Possible Causes
Packets were resent through the interface.
Issue 07 (2014-07-30)

764

Log Reference
71 OSPF
Procedure
----End
71.115 OSPF/6/TRAP_LSDB_APP_OFLOW
Message
OSPF/6/TRAP_LSDB_APP_OFLOW:Notify LSDB approaching overflow. (ProcessId=
[USHORT], RouterId=[IPADDR], ExtLsdbLimit=[ULONG])
Description
OSPF notified that the LSDB would overflow soon.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
ExtLsdbLimit
Indicates the limit of LSDB extension.
Possible Causes
OSPF notified that the LSDB would overflow soon.
Procedure
----End
71.116 OSPF/6/TRAP_LSDB_OVERFLOW
Message
OSPF/6/TRAP_LSDB_OVERFLOW:Notify LSDB overflow. (ProcessId=[USHORT],
RouterId=[IPADDR], ExtLsdbLimit=[ULONG])
Description
OSPF notified that the LSDB overflowed.
Issue 07 (2014-07-30)

765

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
ExtLsdbLimit
Indicates the limit of LSDB extension.
Possible Causes
OSPF notified that the LSDB overflowed.
Procedure
----End
71.117 OSPF/6/TRAP_NBR_CHG
Message
OSPF/6/TRAP_NBR_CHG:Neighbor state has changed. (ProcessId=[USHORT], RouterId=
[IPADDR], NeighborIpAddress=[IPADDR], NeighborAddressLessIndex=[ULONG],
NeighborRouterId=[IPADDR], NeighborState=[ULONG])
Description
The status of the neighbor changed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
NeighborIpAddress
NeighborAddressLessIndex
Indicates the index of the IP address of a neighbor.
NeighborRouterId
NeighborState
Indicates the status of the neighbor.
Possible Causes
Issue 07 (2014-07-30)

766

Log Reference
71 OSPF
Procedure
----End
71.118 OSPF/6/TRAP_NSSA_TRANS_CHG
Message
OSPF/6/TRAP_NSSA_TRANS_CHG:Notify the change in NSSA translator role. (ProcessId=
[USHORT], RouterId=[IPADDR], AreaId=[IPADDR], NssaTranslatorState=[ULONG])
Description
OSPF notified that the NSSA translator role changed.
Parameters
Parameter Name
Parameter Meaning
Process ID
RouterId
AreaId
NssaTranslatorState
Indicates the reason why the NSSA role changes.
Possible Causes
OSPF notified that the NSSA translator role changed.
Procedure
----End
71.119 OSPF/6/TRAP_ORG_LSA
Message
OSPF/6/TRAP_ORG_LSA:Router originating LSA. (ProcessId=[USHORT], RouterId=
[IPADDR], LsdbAreaId=[IPADDR], LsdbType=[ULONG], LsdbLsId=[IPADDR],
Description
The router generated an LSA.
Issue 07 (2014-07-30)

767

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
LsdbAreaId
Indicates the area ID of the LSDB.
LsdbType
Indicates the type of the LSDB.
LsdbLsId
LsdbRouterId
Possible Causes
The router generated an LSA.
Procedure
----End
71.120 OSPF/6/TRAP_RESTART_CHG
Message
OSPF/6/TRAP_RESTART_CHG:Notify the change in restart. (ProcessId=[USHORT],
RouterId=[IPADDR], RestartStatus=[ULONG], RestartInterval=[ULONG],
RestartExitReason=[ULONG])
Description
OSPF notified that GR status changed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
RestartStatus
Indicates the status of Graceful Restart (GR).
RestartInterval
Indicates the interval for GR.
RestartExitReason
Indicates the reason why the router exits from GR.
Issue 07 (2014-07-30)

768

Log Reference
71 OSPF
Possible Causes
OSPF notified that GR status changed.
Procedure
----End
71.121 OSPF/4/TRAP_VIF_AUTH_FAIL
Message
OSPF/4/TRAP_VIF_AUTH_FAIL:Virtual interface authentication has failed. (ProcessId=
[USHORT], RouterId=[IPADDR], Area=[IPADDR], Neighbor=[IPADDR], ErrorType=
[ULONG], PacketType=[ULONG])
Description
The virtual interface authentication failed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
Area
Neighbor
ErrorType
PacketType
Possible Causes
The virtual interface authentication failed.
Procedure
Step 1 Run the display ospf interface command to check the authentication configuration of the virtual
interface and the neighbor router.
----End
Issue 07 (2014-07-30)

769

Log Reference
71 OSPF
71.122 OSPF/4/TRAP_VIF_CFG_ERR
Message
OSPF/4/TRAP_VIF_CFG_ERR:Virtual interface configuration error has occurred. (ProcessId=
[USHORT], RouterId=[IPADDR], Area=[IPADDR], Neighbor=[IPADDR], ErrorType=
[ULONG], PacketType=[ULONG])
Description
The virtual interface was incorrectly configured.
Parameters
Parameter Name
Parameter Meaning
Process ID
RouterId
Area
Neighbor
ErrorType
PacketType
Possible Causes
The virtual interface was incorrectly configured.
Procedure
Step 1 Run the display ospf vlink command to check the authentication configuration of the virtual
interface.
----End
71.123 OSPF/6/TRAP_VIF_RX_BAD
Message
OSPF/6/TRAP_VIF_RX_BAD:Virtual interface received bad packet. (ProcessId=[USHORT],
RouterId=[IPADDR], Area=[IPADDR], Neighbor=[IPADDR], PacketType=[ULONG])
Issue 07 (2014-07-30)

770

Log Reference
71 OSPF
Description
An error packet was received on the virtual interface.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
Area
Neighbor
PacketType
Possible Causes
An error packet was received on the virtual interface.
Procedure
Step 1 Check the source address of the error packet.
----End
71.124 OSPF/6/TRAP_VIR_HELPER_CHG
Message
OSPF/6/TRAP_VIR_HELPER_CHG:Notify the change in virtual neighbor restart helper.
(ProcessId=[USHORT], RouterId=[IPADDR], VirtualNeighborArea=[IPADDR],
VirtualNeighborRouterId=[IPADDR], VirtualNeighborRestartHelperStatus=[ULONG],
VirtualNeighborRestartHelperAge=[ULONG], VirtualNeighborRestartHelperExitReason=
[ULONG])
Description
The status of the virtual neighbor changed.
Parameters
Parameter Name
Parameter Meaning
Process ID
RouterId
Issue 07 (2014-07-30)

771

Log Reference
71 OSPF
Parameter Name
Parameter Meaning
VirtualNeighborArea
Indicates the area ID of a virtual neighbor.
VirtualNeighborRouterId
Indicates the router ID of a virtual neighbor.
VirtualNeighborRestartHelperStatus
Indicates the status of the virtual neighbor GR

helper.
VirtualNeighborRestartHelperAge
Indicates the duration of the virtual neighbor GR

helper.
VirtualNeighborRestartHelperExitReason Indicates the reason why the virtual neighbor exits

from the GR helper.
Possible Causes
The link status changed.
Procedure
----End
71.125 OSPF/6/TRAP_VIR_INTF_CHG
Message
OSPF/6/TRAP_VIR_INTF_CHG:Virtual interface state has changed. (ProcessId=[USHORT],
RouterId=[IPADDR], AreaId=[IPADDR], NeighborId=[IPADDR], InterfaceState=[ULONG])
Description
The status of the virtual interface changed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
AreaId
Indicates the ID of area.
NeighborId
Indicates the ID of the neighbor router.
InterfaceState
Indicates the status of an interface.
Possible Causes
The status of the virtual interface changed.
Issue 07 (2014-07-30)

772

Log Reference
71 OSPF
Procedure
----End
71.126 OSPF/6/TRAP_VIR_INTF_RETX
Message
OSPF/6/TRAP_VIR_INTF_RETX:Virtual interface has retransmitted. (ProcessId=
[USHORT], RouterId=[IPADDR], Area=[IPADDR], Neighbor=[IPADDR], PacketType=
[ULONG], LsdbAreaId=[IPADDR], LsdbType=[ULONG], LsdbLsId=[IPADDR],
Description
Packets were resent through the virtual interface.
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
Area
Neighbor
PacketType
LsdbAreaId
Indicates the area ID of an LSA in the LSDB.
LsdbType
Indicates the type of an LSA in the LSDB.
LsdbLsId
LsdbRouterId
Possible Causes
Packets were resent through the virtual interface.
Procedure
----End
71.127 OSPF/6/TRAP_VIR_NBR_CHG
Issue 07 (2014-07-30)

773

Log Reference
71 OSPF
Message
OSPF/6/TRAP_VIR_NBR_CHG:Virtual neighbor state has changed. (ProcessId=[USHORT],
RouterId=[IPADDR], Area=[IPADDR], VirtualNeighborRouterId=[IPADDR],
VirtualNeighborState=[ULONG])
Description
Parameters
Parameter Name
Parameter Meaning
ProcessId
RouterId
Area
VirtualNeighborRouterId
Indicates the IP address of a virtual neighbor.
VirtualNeighborState
Indicates the status of a virtual neighbor.
Possible Causes
Procedure
----End
71.128 OSPF/4/UPLAN_MATCH_HLPFAIL
Message
OSPF/4/UPLAN_MATCH_HLPFAIL:OSPF [process-id] can not enter helper, unplanned
configuration mismatch with restart peer [interface-name].
Description
The OSPF process cannot enter the helper mode because the helper GR configurations did not
match information contained in the grace LSA sent by the restarter.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Issue 07 (2014-07-30)

774

Log Reference
71 OSPF
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
The OSPF process cannot enter the helper mode because the helper GR configurations did not
match information contained the grace LSA sent by the restarter.
Procedure
----End
71.129 OSPF/6/VINTF_NSR_EVENT
Message
OSPF/6/VINTF_NSR_EVENT: Virtual link interface of the [STRING] received event
[STRING], and NSR state changed from [STRING] to [STRING]. (NbrID=[STRING], IpAddr=
[IPADDR], ProcessId=[USHORT], TransitAreaId=[STRING])
Description
The NSR state on an OSPF virtual-link interface on the AMB or SMB changed.
Parameters
Parameter Name
Parameter Meaning
[STRING]
AMB or SMB to which a virtual-link interface belongs
[STRING]
Event causing the NSR state of the virtual-link interface to change
[STRING]
Previous NSR status of the virtual-link interface
[STRING]
New NSR status of the virtual-link interface
NbrID
ID of a neighboring router
IpAddr
IP address of the virtual-link interface
ProcessId
ID of the process to which the virtual-link interface belongs
TransitAreaId
ID of the transit area to which the virtual-link interface belongs.
Possible Causes
When the data on OSPF NSR interfaces was backed up, an OSPF virtual-link interface on the
AMB communicated with an OSPF vitual-link interface on the SMB or the communication
between the two interfaces was interrupted.
Issue 07 (2014-07-30)

775

Log Reference
71 OSPF
Procedure
----End
71.130 OSPF/4/VINTF_NSR_OVERTIME_LIMIT
Message
OSPF/4/VINTF_NSR_OVERTIME_LIMIT: The virtual link interface go on process, as slave's
ack didn't come for [ULONG] seconds. (NbrID=[STRING], IpAddr=[IPADDR], ProcessId=
[USHORT], TransitAreaId=[STRING])
Description
If the OSPF virtual interface on the active board receives no response from the standby board
within a specified interval, the active board considers that the standby board has responded and
does not require retransmission of backup messages.
Parameters
[ULONG]
Total time that the virtual interface waits for the response from the standby
board, in seconds
NbrID
Name of the virtual interface
IpAddr
IP address of the virtual interface
ProcessId
Process ID to which the virtual interface belongs
TransitAreaId
Area ID to which the virtual interface belongs
Possible Causes
After the virtual interface on the active board initiates a handshake with the standby board, the
interface waits for a response from the standby board. If the total waiting time exceeds the upper
limit (equal to or less than 600 seconds, generally 40 times of the retransmission interval), it
may be caused by inconsistent OSPF interface statuses on the active board and the standby board,
blocked backup channel, or loss of backup messages.
Procedure
Step 1 Run the display ospf vlink command to check whether the statuses of virtual interfaces on the
active board and the standby board are consistent.
----End
Issue 07 (2014-07-30)

776

Log Reference
71 OSPF
71.131 OSPF/6/VLINK_IF_CHG_E
Message
OSPF/6/VLINK_IF_CHG_E:Virtual link interface [vlink-interface-address] received event
[interface-event], interface state changed from [interface-previous-state] to [interface-currentstate]. (ProcessId=[USHORT])
Description
The status of the interface on the virtual link changed.
Parameters
Parameter Name
Parameter Meaning
[vlink-interface-address]
Indicates the IP address of the interface on the virtual link.
[interface-event]
ProcessId
Possible Causes
The status of the interface on the virtual link changed.
Procedure
----End
71.132 OSPF/3/VLINK_NBR_CHG_DOWN
Message
OSPF/3/VLINK_NBR_CHG_DOWN:Virtual link peer event: neighbor state changed to Down.
(ProcessId=[USHORT], NeighborAddress=[IPADDR], NeighborEvent=[STRING],
Description
Issue 07 (2014-07-30)

777

Log Reference
71 OSPF
Parameters
Parameter Name
Parameter Meaning
ProcessId
NeighborAddress
NeighborEvent
Possible Causes
The neighbor on the virtual link turned Down because the neighbor received an OSPF message
or the event affecting the neighbor relationship occurred.
Procedure
----End
71.133 OSPF/4/VLINK_NBR_CHG_E
Message
OSPF/4/VLINK_NBR_CHG_E:Virtual link peer event: neighbor status changed. (ProcessId=
[USHORT], VirtualLinkNeighborAddress=[IPADDR], NeighborEvent=[STRING],
Description
The status of the neighboring node on the virtual link changed.
Parameters
Parameter Name
Parameter Meaning
ProcessId
VirtualLinkNeighborAddress Indicates the IP addresses of neighboring nodes on the virtual

link.
NeighborEvent
Indicates the events received by the neighboring node.
Indicates the previous status of the neighboring node.
Indicates the current status of the neighboring node.
Issue 07 (2014-07-30)

778

Log Reference
71 OSPF
Possible Causes
The status of the neighboring node on the virtual link changed.
Procedure
Step 1 Run the display ospf peer command to check the status of the neighbor.
----End
Issue 07 (2014-07-30)

779

Log Reference
72 OSPFV3
72
OSPFV3
About This Chapter

72.1 OSPFV3/6/BFD_RM_EVNT
72.2 OSPFV3/6/BFD_SESSION_NTFY
72.3 OSPFV3/3/GRBCKLNKERR
72.4 OSPFV3/3/GRFLLALLNBRERR
72.5 OSPFV3/3/GRINTFDWNERR
72.6 OSPFV3/6/GRNOHLPCNFG
72.7 OSPFV3/3/GRNORMALRSTERR
72.8 OSPFV3/6/GRNOTENBL
72.9 OSPFV3/3/GRPRDEXPERR
72.10 OSPFV3/3/GRPROCDELERR
72.11 OSPFV3/3/GRSLFORGNTWKMSSERR
72.12 OSPFV3/4/HELLO_DELAY
72.13 OSPFV3/6/IFSMCHG
72.14 OSPFV3/4/MAXEXTROUTESLIMIT
72.15 OSPFV3/4/MEMSHORT
72.16 OSPFV3/6/NFSMCHG
72.17 OSPFV3/4/PROC_UP_FAIL_MEMSHT
72.18 OSPFV3/6/PROCUNDRGR
72.19 OSPFV3/4/RMMEMRESTR
72.20 OSPFV3/4/RMMEMSHORT
Issue 07 (2014-07-30)

780

Log Reference
72 OSPFV3
72.1 OSPFV3/6/BFD_RM_EVNT
Message
OSPFV3/6/BFD_RM_EVNT: OSPFv3 BFD Received event notification [ULONG] from RM
on interface [STRING] for remote IPv6 address [STRING].
Description
When RM notifies any BFD related event change, this dialog is displayed.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the BFD event value from RM
[STRING]
Indicates the Interface name

l Create/update BFD sessions
l Delete BFD sessions
[STRING]
Indicates the IPv6 address.
Possible Causes
RM notifies any BFD related event change.
Procedure
----End
72.2 OSPFV3/6/BFD_SESSION_NTFY
Message
OSPFV3/6/BFD_SESSION_NTFY: OSPFv3 BFD sending session [STRING] notification to
RM on interface [STRING] for remote IPv6 address [STRING]. (MinTransmitInterval=
[ULONG], MinReceiveInterval=[ULONG], DetectMultiplier=[ULONG]).
Description
When OSPFv3 notifies RM to create, delete or update BFD session, this dialog is displayed.
Issue 07 (2014-07-30)

781

Log Reference
72 OSPFV3
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the BFD event value from RM
[STRING]
Indicates the Interface name

l Create/update BFD sessions
l Delete BFD sessions
[STRING]
Indicates the IPv6 address.
MinTransmitInterval Indicates minimum transmit interval for BFD support in OSPFv3 on a

given OSPFv3 process.
MinReceiveInterval
Indicates minimum receive interval for BFD support in OSPFv3 on a

given OSPFv3 process.
DetectMultiplier
Indicates detect multiplier value for BFD support in OSPFv3 on a given

OSPFv3 process.
Possible Causes
BFD enabled OSPFv3 adjacency is formed or broken down.
Procedure
----End
72.3 OSPFV3/3/GRBCKLNKERR
Message
OSPFV3/3/GRBCKLNKERR: There is no link to restarting router in the received LSA, so
prematurely exit graceful restart and reset OSPFv3 [ULONG] process.
Description
No link to the GR router existed in the new LSA. Then GR was quitted.
Issue 07 (2014-07-30)

782

Log Reference
72 OSPFV3
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the process ID.
Possible Causes
No link to the GR router existed in the new LSA. Then GR was prematurely quitted and the
OSPFv3 protocol was reset.
Procedure
----End
72.4 OSPFV3/3/GRFLLALLNBRERR
Message
OSPFV3/3/GRFLLALLNBRERR: OSPFv3 [ULONG] restarting router is full with all the
neighbors, hence exiting graceful restart.
Description
The OSPFv3 process became full with all the neighbors. Then GR was quitted.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The OSPFv3 process became full with all the neighbors during GR.
Procedure
----End
72.5 OSPFV3/3/GRINTFDWNERR
Issue 07 (2014-07-30)

783

Log Reference
72 OSPFV3
Message
OSPFV3/3/GRINTFDWNERR: Interface [STRING] state changed in restarting router, so
prematurely exit graceful restart and reset OSPFv3 [ULONG] process.
Description
The OSPFv3-GR interface was Down during GR.
Parameters
Parameter Name
Parameter Meaning
[STRING]
[ULONG]
Possible Causes
The OSPFv3-GR interface was Down during GR. Then GR was prematurely quitted and the
OSPFv3 protocol was reset.
Procedure
----End
72.6 OSPFV3/6/GRNOHLPCNFG
Message
OSPFV3/6/GRNOHLPCNFG: OSPFv3 [ULONG] helper is not configured.
Description
No helper configuration was present.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
No helper configuration was present.
Issue 07 (2014-07-30)

784

Log Reference
72 OSPFV3
Procedure
----End
72.7 OSPFV3/3/GRNORMALRSTERR
Message
OSPFV3/3/GRNORMALRSTERR: Exited from graceful restart because normal reset is
executed on OSPFv3 process [ULONG].
Description
The normal reset was finished, and GR was quitted.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The OSPFv3 process was reset during GR. Then GR was prematurely quitted and the OSPFv3
protocol was reset.
Procedure
----End
72.8 OSPFV3/6/GRNOTENBL
Message
OSPFV3/6/GRNOTENBL: OSPFv3 [ULONG] graceful restart is not enabled.
Description
The GR function was not enabled.
Issue 07 (2014-07-30)

785

Log Reference
72 OSPFV3
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The GR function was not configured.
Procedure
Step 1 Configure the GR function and run the reset ospfv3 command to restart the OSPFv3 protocol.
----End
72.9 OSPFV3/3/GRPRDEXPERR
Message
OSPFV3/3/GRPRDEXPERR: OSPFv3 [ULONG] grace period timer expired.
Description
The GR period timer expired.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The GR period timer in the OSPFv3 process expired.
Procedure
----End
72.10 OSPFV3/3/GRPROCDELERR
Message
OSPFV3/3/GRPROCDELERR: Exited from graceful restart because OSPFv3 process
[ULONG] is deleted.
Issue 07 (2014-07-30)

786

Log Reference
72 OSPFV3
Description
GR was quitted because the GR process was deleted.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The OSPFv3 process was deleted during GR. Then GR was prematurely quitted and the OSPFv3
protocol was reset.
Procedure
----End
72.11 OSPFV3/3/GRSLFORGNTWKMSSERR
Message
OSPFV3/3/GRSLFORGNTWKMSSERR: Exited graceful restart as self originated NetworkLSAs were not received from the neighbor [STRING] on interface [STRING] during database
synchronization for OSPFv3 process [ULONG].
Description
During the period of Database Description packets exchange, the pre-restart network LSAs that
were self originated were not received. Then GR was quitted.
Parameters
Parameter Name
Parameter Meaning
[STRING]
[STRING]
[ULONG]
Possible Causes
No pre-restart network LSA that was self originated was received. This showed that at least one
neighbor was not the helper. Then GR was prematurely quitted and the OSPFv3 protocol was
reset.
Issue 07 (2014-07-30)

787

Log Reference
72 OSPFV3
Procedure
----End
72.12 OSPFV3/4/HELLO_DELAY
Message
OSPFV3/4/HELLO_DELAY: Sending hello packet on the interface [STRING] is delayed more
than 3 times of the hello interval.
Description
Interval between last sending hello packet and current hello packet sending is greater than three
times hello interval which may indicate task schedule delay.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
Interval between last sending hello packet and current hello packet sending is greater than three
times hello interval which may indicate task schedule delay.
Procedure
----End
72.13 OSPFV3/6/IFSMCHG
Message
OSPFV3/6/IFSMCHG:Interface [interface-name] state changed from [old-interface-state] to
[new-interface-state]. (Event=[STRING], ProcessId=[ULONG])
Description
The interface status changed from status 1 to status 2.
Issue 07 (2014-07-30)

788

Log Reference
72 OSPFV3
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[old-interface-state]
Indicates the old interface status.
[new-interface-state]
Indicates the new interface status.
Event
Indicates the interface event.
ProcessId
Possible Causes
Procedure
----End
72.14 OSPFV3/4/MAXEXTROUTESLIMIT
Message
OSPFV3/4/MAXEXTROUTESLIMIT: OSPFv3 [ULONG] external route addition is
unsuccessful due to maximum limit.
Description
The maximum number of configurable external routes was reached.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The maximum number of configurable external routes was reached.
Procedure
Step 1 Change the PAF/LCS of the router or reduce the route count.
----End
Issue 07 (2014-07-30)

789

Log Reference
72 OSPFV3
72.15 OSPFV3/4/MEMSHORT
Message
OSPFV3/4/MEMSHORT:Received memory shortage notification from memory management.
Description
Received the memory shortage notification from the memory management module.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The memory was insufficient.
Procedure
Step 1 Run the display diagnostic-information command to save the displayed result and contact
----End
72.16 OSPFV3/6/NFSMCHG
Message
OSPFV3/6/NFSMCHG:Neighbor state changed from [neighbor-old] to [neighbor-new].
(Event=[STRING], RouterId=[STRING], Interface=[STRING], ProcessId=[ULONG])
Description
The neighbor state changed from state 1 to state 2.
Parameters
Parameter Name
Parameter Meaning
[neighbor-old]
Indicates the old status of the neighbor.
[neighbor-new]
Indicates the new status of the neighbor.
Event
Indicates the neighbor event.
Issue 07 (2014-07-30)

790

Log Reference
72 OSPFV3
Parameter Name
Parameter Meaning
RouterId
Interface
Indicates the interface to the neighbor.
ProcessId
Possible Causes
Procedure
----End
72.17 OSPFV3/4/PROC_UP_FAIL_MEMSHT
Message
OSPFV3/4/PROC_UP_FAIL_MEMSHT: OSPFv3 [ULONG] process cannot come up due to
memory shortage.
Description
The process failed to go Up because of insufficient memory.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The process failed to go Up because of insufficient memory.
Procedure
----End
72.18 OSPFV3/6/PROCUNDRGR
Issue 07 (2014-07-30)

791

Log Reference
72 OSPFV3
Message
OSPFV3/6/PROCUNDRGR: OSPFv3 [ULONG] process is undergoing reset.
Description
The process was undergoing reset.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
When the GR hold timer expired, the process is undergoing reset.
Procedure
----End
72.19 OSPFV3/4/RMMEMRESTR
Message
OSPFV3/4/RMMEMRESTR:Received memory restore notification from RM.
Description
Received the memory restoring notification from the route management.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The memory was restored.
Procedure
----End
Issue 07 (2014-07-30)

792

Log Reference
72 OSPFV3
72.20 OSPFV3/4/RMMEMSHORT
Message
OSPFV3/4/RMMEMSHORT:Received memory shortage notification from RM.
Description
Received the memory shortage notification from the route management.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

793

Log Reference
73 PAF
73
PAF
About This Chapter

73.1 PAF/6/LCS_NOT_SAME
73.2 PAF/6/PAF_NOT_SAME
73.3 PAF/4/READLCSFAIL
73.4 PAF/4/READPAFFAIL
73.5 PAF/5/WRITE_LCS_FAIL
73.6 PAF/5/WRITE_PAF_FAIL
Issue 07 (2014-07-30)

794

Log Reference
73 PAF
73.1 PAF/6/LCS_NOT_SAME
Message
PAF/6/LCS_NOT_SAME:The license file on this board is not the same as that on the system
main control board.
Description
The License file on this board is different from that on the main control board of the system.
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
The License file on this board is different from that on the main control board of the system.
Procedure
----End
73.2 PAF/6/PAF_NOT_SAME
Message
PAF/6/PAF_NOT_SAME:The PAF file on this board is not the same as that on the system main
control board.
Description
The PAF file on this board is different from that on the main control board of the system.
Parameters
Parameter Name
Parameter Meaning
None
None.
Issue 07 (2014-07-30)

795

Log Reference
73 PAF
Possible Causes
The PAF file on this board is different from that on the main control board of the system.
Procedure
----End
73.3 PAF/4/READLCSFAIL
Message
PAF/4/READLCSFAIL:Failed to read License file when initializing LCS. (ErrorCode=
[LONG])
Description
Failed to read the License file in initialization.
Parameters
Parameter Name
Parameter Meaning
ErrorCode
Indicates the error code:

-2: indicates that the handle is invalid.
-3: indicates the pointer is invalid.
-4: indicates the opening type is incorrect.
-5: indicates that the parameter is incorrect.
Possible Causes
Failed to read the License file when initializing the License file.
Procedure
Step 1 Run the dir license.txt command to check whether the license.txt exists. If so, check whether
the length of the file is longer than zero. If so, run the copy license.txtslave#flash:/ command
to copy the license to the slave board. Then, run the slave restart command to restart the slave
board.
----End
73.4 PAF/4/READPAFFAIL
Issue 07 (2014-07-30)

796

Log Reference
73 PAF
Message
PAF/4/READPAFFAIL:Failed to read PAF file when initializing PAF. (ErrorCode=[LONG])
Description
Failed to read the PAF file when initializing PAF file.
Parameters
Parameter Name
Parameter Meaning
ErrorCode
Indicates the error code:

l -2: indicates that the handle is invalid.
l -3: indicates the pointer is invalid.
l -4: indicates the incorrect opening type.
l -5: indicates that the parameter is incorrect.
Possible Causes
Failed to read the PAF file when initializing PAF file.
Procedure
l
Run the dir license.txt command to check whether the license.txt exists. If so, check
whether the length of the file is longer than zero. If so, run the copy license.txt
slave#flash:/ command to copy the license to the slave board. Then, run the slave
restart command to restart the slave board.
----End
73.5 PAF/5/WRITE_LCS_FAIL
Message
PAF/5/WRITE_LCS_FAIL:Failed to write License file when synchronizing the License file
from the target main control board.
Description
Failed to write the License file when synchronizing the License file from the target main control
board.
Issue 07 (2014-07-30)

797

Log Reference
73 PAF
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
Failed to write the License file when synchronizing the License file from the target main control
board.
Procedure
----End
73.6 PAF/5/WRITE_PAF_FAIL
Message
PAF/5/WRITE_PAF_FAIL:Failed to write PAF file when synchronizing the PAF file from the
target main control board.
Description
Failed to write the PAF file when synchronizing the PAF file from the target main control board.
Parameters
Parameter Name
Parameter Meaning
None
None.
Possible Causes
Failed to write the PAF file when synchronizing the PAF file from the target main control board.
Procedure
----End
Issue 07 (2014-07-30)

798

Log Reference
74 PATCH
74
PATCH
About This Chapter

74.1 PATCH/6/READ_FILE_FAIL
Issue 07 (2014-07-30)

799

Log Reference
74 PATCH
74.1 PATCH/6/READ_FILE_FAIL
Message
PATCH/6/READ_FILE_FAIL:On slot [slot-num], read patch file [file-name] failed.
Description
Failed to read the patch file.
Parameters
Parameter Name
Parameter Meaning
[slot-num]
Indicates the slot number of a board.
[file-name]
Indicates the name of a patch file.
Possible Causes
Failed to read the patch file.
Procedure
----End
Issue 07 (2014-07-30)

800

Log Reference
75 PDF
75
PDF
About This Chapter

75.1 PDF/4/CLOSEPDFRFAIL
75.2 PDF/4/CLOSEPDFWFAIL
75.3 PDF/4/DOPOPFAIL
75.4 PDF/4/OPENPDFRFAIL
75.5 PDF/4/OPENPDFWFAIL
75.6 PDF/4/READPDFFAIL
75.7 PDF/4/SEEKPDFRFAIL
75.8 PDF/4/SEEKPDFWFAIL
75.9 PDF/4/WRITEFAIL
75.10 PDF/4/WRITEPDFFAIL
75.11 PDF/4/WRITEPDFNOSPACE
75.12 PDF/4/WRITESLAVEFAIL
Issue 07 (2014-07-30)

801

Log Reference
75 PDF
75.1 PDF/4/CLOSEPDFRFAIL
Message
PDF/4/CLOSEPDFRFAIL:Failed to close PDF file when reading private data.
Description
Failed to close the PDF file.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
l
----End
75.2 PDF/4/CLOSEPDFWFAIL
Message
PDF/4/CLOSEPDFWFAIL:Failed to close PDF file when writing private data.
Description
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Issue 07 (2014-07-30)

802

Log Reference
75 PDF
Procedure
----End
75.3 PDF/4/DOPOPFAIL
Message
PDF/4/DOPOPFAIL:Failed to do P operation when writing current data to flash.
Description
Failed to read data from the data area before writing data to the flash.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The P operation failed.
Procedure
----End
75.4 PDF/4/OPENPDFRFAIL
Message
PDF/4/OPENPDFRFAIL:Failed to open PDF file in binary read mode when reading private
data.
Description
Failed to open the binary PDF file in read mode.
Issue 07 (2014-07-30)

803

Log Reference
75 PDF
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to open the binary PDF file in read mode.
Procedure
----End
75.5 PDF/4/OPENPDFWFAIL
Message
PDF/4/OPENPDFWFAIL:Failed to open PDF file in binary write mode when writing private
data.
Description
Failed to open the binary PDF file in write mode.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to open the binary PDF file in write mode.
Procedure
----End
75.6 PDF/4/READPDFFAIL
Message
PDF/4/READPDFFAIL:Failed to read PDF file when reading private data.
Issue 07 (2014-07-30)

804

Log Reference
75 PDF
Description
Failed to read the PDF file.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to read the PDF file.
Procedure
----End
75.7 PDF/4/SEEKPDFRFAIL
Message
PDF/4/SEEKPDFRFAIL:Failed to seek the PDF file header when reading private data.
Description
Failed to skip to the PDF header.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
75.8 PDF/4/SEEKPDFWFAIL
Issue 07 (2014-07-30)

805

Log Reference
75 PDF
Message
PDF/4/SEEKPDFWFAIL:Failed to seek the PDF file header when writing private data.
Description
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
75.9 PDF/4/WRITEFAIL
Message
PDF/4/WRITEFAIL:Failed to write PDF file when writing current data to flash.
Description
Failed to write the PDF file before writing data to the flash.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to write the PDF file before writing data to the flash.
Procedure
----End
Issue 07 (2014-07-30)

806

Log Reference
75 PDF
75.10 PDF/4/WRITEPDFFAIL
Message
PDF/4/WRITEPDFFAIL:Failed to write PDF file when writing private data.
Description
Failed to write the PDF file.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to write the PDF file.
Procedure
----End
75.11 PDF/4/WRITEPDFNOSPACE
Message
PDF/4/WRITEPDFNOSPACE:Failed to write PDF file because the storage space is not enough.
(FreeSpace=[STRING]Bytes, FileLength=[STRING]Bytes)
Description
Failed to update the PDF file because the remaining storage space was insufficient.
Parameters
Parameter Name
Parameter Meaning
FreeSpace
Indicates the remaining space.
FileLength
Indicates the file length.
Issue 07 (2014-07-30)

807

Log Reference
75 PDF
Possible Causes
The PDF file was updated when the remaining storage space was smaller than the size of the
PDF file.
Procedure
Step 1 Enter the device directory.
1.
If the switch has a hard disk, run the cd hda1: command to enter the hard disk directory.
2.
If the switch has a flash rather than a hard disk, run the cd flash: command to enter the
flash directory.
Step 2 Run the dir command to check the size of the remaining storage space. If the remaining space
is not enough, run the delete command to delete unneeded files.
Step 3 Run the dir command to check whether the size of the remaining storage space is greater than
the size of the PDF file.
Step 5 End.
----End
75.12 PDF/4/WRITESLAVEFAIL
Message
PDF/4/WRITESLAVEFAIL:Failed to write PDF file in the slave board when writing current
data to flash.
Description
Failed to write the PDF file before writing data to the flash on the slave board.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to write the PDF file before writing data to the flash on the slave board.
Issue 07 (2014-07-30)

808

Log Reference
75 PDF
Procedure
----End
Issue 07 (2014-07-30)

809

Log Reference
76 PIM
76
PIM
About This Chapter

76.1 PIM/4/ASTPKT_GADD_ERR1
76.2 PIM/4/BACKUPJP_NORP
76.3 PIM/4/BSR_GRP_SCOPE_ERR
76.4 PIM/4/BSR_GRPLOC
76.5 PIM/4/CRPADV_FAMERR
76.6 PIM/4/CRPADV_GRPERR
76.7 PIM/4/CRPADV_GRPINV
76.8 PIM/4/CRT_SG_FAIL
76.9 PIM/6/DISCA_PRIADDR
76.10 PIM/4/FNDNBR_DNDB_F
76.11 PIM/5/GR_END
76.12 PIM/5/GR_START
76.13 PIM/6/GRP_ADDR_IS_LOCAL
76.14 PIM/6/GRP_ADDR_NOT_MCAST
76.15 PIM/6/GRP_MASK_UNSUPPORTED
76.16 PIM/6/HELPKT_UNSADDR_ERR
76.17 PIM/3/HOLDTIME_LESS_INL
76.18 PIM/4/INT_INV
76.19 PIM/5/INVSRC
76.20 PIM/4/JP_SRCERR
Issue 07 (2014-07-30)

810

Log Reference
76 PIM
76.21 PIM/6/MTU_IF_SHT
76.22 PIM/4/NBR_DOWN
76.23 PIM/4/NBR_DOWN_ALL
76.24 PIM/4/NBR_UP
76.25 PIM/4/PIMPKT_CHKSUM_ERR
76.26 PIM/4/PIM_GR_FORCE_SYNC
76.27 PIM/3/PUTNBR_DNDB_F
76.28 PIM/6/SEC_ADDRFA_ERR
76.29 PIM/3/SOCK_ERR1
76.30 PIM/6/SRC_MASK_UNSUPPORTED
Issue 07 (2014-07-30)

811

Log Reference
76 PIM
76.1 PIM/4/ASTPKT_GADD_ERR1
Message
PIM/4/ASTPKT_GADD_ERR1:In VPN instance \"[vpn-instance-name]\", the received Assert
packet with an incorrect group address was ignored. (FlCode=[STRING][ULONG])
Description
The Assert packet was discarded because the group address was invalid.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
The Assert packet was discarded because the group address was invalid.
Procedure
Step 1 If this fault occurs occasionally, this log message can be ignored.
Step 2 If the fault frequently occurs, record this log message, and then contact Huawei technical support
personnel.
----End
76.2 PIM/4/BACKUPJP_NORP
Message
PIM/4/BACKUPJP_NORP:In VPN instance \"[vpn-instance-name]\", when trying to send a (*,
[group-address]) Join message, PIM cannot obtain the RP. (FlCode=[STRING][ULONG])
Description
The PIM failed to obtain the RP when trying to send a Join message (*,G).
Issue 07 (2014-07-30)

812

Log Reference
76 PIM
Parameters
Parameter Name
Parameter Meaning

[group-address]
FlCode
log message.
Possible Causes
The RP is not backed up to the slave board, causing the PIM unable to find the RP after the GR
process.
Procedure
Step 1 Run the display pim [ vpn-instance vpn-instance-name | all-instance ] rp-info command to
check whether the RP exists.
Step 2 Run the static-rp or c-rp command in the PIM view to configure the RP.
----End
76.3 PIM/4/BSR_GRP_SCOPE_ERR
Message
PIM/4/BSR_GRP_SCOPE_ERR:In VPN instance \"[vpn-instance-name]\", the BSR packet
received from [bsr-address] and with wrong group [group-address]'s scope was ignored.
Description
In the multicast NSR scenario, the slave MPU received incorrect BSR messages when the master
MPU backs up information to the slave MPU.
Parameters
Parameter Name
Parameter Meaning

[bsr-address]
Indicates the address of the BSR.
[group-address]
FlCode
log message.
Issue 07 (2014-07-30)

813

Log Reference
76 PIM
Possible Causes
In the multicast NSR scenario, the slave MPU received incorrect BSR messages when the master
MPU backs up information to the slave MPU.
Procedure
Step 2 If the fault frequently occurs, check the packet source, record this log message, and then contact
----End
76.4 PIM/4/BSR_GRPLOC
Message
PIM/4/BSR_GRPLOC:In VPN instance \"[vpn-instance-name]\", the BSR packet whose group
address [group-address]/[mask] was the local multicast address was ignored. (FlCode=
[STRING][ULONG])
Description
The BSR packet whose group address was the local multicast address was ignored.
Parameters
Parameter Name
Parameter Meaning

[group-address]
[mask]
Indicates the mask of the group address.
FlCode
log message.
Possible Causes
A BSR packet with an invalid group address was received.
Procedure
personnel.
----End
Issue 07 (2014-07-30)

814

Log Reference
76 PIM
76.5 PIM/4/CRPADV_FAMERR
Message
PIM/4/CRPADV_FAMERR:In VPN instance \"[vpn-instance-name]\", the group address
family [group-address-family] was invalid, ignored this group [group-address]. (FlCode=
[STRING][ULONG])
Description
The CRP_ADV packet with invalid group address family was discarded.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
[group-address-family] Indicates the address family of a group.

[group-address]
FlCode
log message.
Possible Causes
An invalid CRP_ADV packet was received.
Procedure
----End
76.6 PIM/4/CRPADV_GRPERR
Message
PIM/4/CRPADV_GRPERR:In VPN instance \"[vpn-instance-name]\", the packet with an
incorrect group address was ignored. (FlCode=[STRING][ULONG])
Description
The packet with an incorrect group address was discarded.
Issue 07 (2014-07-30)

815

Log Reference
76 PIM
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
Procedure
personnel.
----End
76.7 PIM/4/CRPADV_GRPINV
Message
PIM/4/CRPADV_GRPINV:In VPN instance \"[vpn-instance-name]\", the group whose group
address [group-address]/[mask] was not the multicast address was ignored. (FlCode=[STRING]
[ULONG])
Description
A packet with a non-multicast group address was discarded.
Parameters
Parameter Name
Parameter Meaning

[group-address]
[mask]
Indicates the mask of the group address.
FlCode
log message.
Possible Causes
Issue 07 (2014-07-30)

816

Log Reference
76 PIM
Procedure
personnel.
----End
76.8 PIM/4/CRT_SG_FAIL
Message
PIM/4/CRT_SG_FAIL:In VPN instance \"[vpn-instance-name]\", PIM-SSM failed to create the
(S,G) entry in the multicast routing table. (FlCode=[STRING][ULONG])
Description
Failed to create the (S, G) entry.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
1. The multicast source was filtered out.
2. The memory was not enough.
3. The current route entries reached the upper limit.
Procedure
Step 1 Run the display acl { acl-number | all } command to ensure the (S, G) will not be filtered out,
that is, ensure that the source address and group address will not be denied by the ACL applied
to multicast.
Step 2 Ensure that system memory is enough.
Step 3 Run the display pim routing-table, display multicast routing-table, and display multicast
forwarding-table commands to check the total number of PIM entries and forwarding entries.
Ensure that the total number does not reach the upper limit specified in the current PIM version.
Step 4 If the fault persists, contact Huawei technical support personnel.
----End
Issue 07 (2014-07-30)

817

Log Reference
76 PIM
76.9 PIM/6/DISCA_PRIADDR
Message
PIM/6/DISCA_PRIADDR:In VPN instance \"[vpn-instance-name]\", the address was ignored
because it was the same as the link-local address of the PIM IPv6 neighbor or the primary address
of the PIM IPv4 neighbor. (FlCode=[STRING][ULONG])
Description
A message with an incorrect primary address was discarded.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
A Hello message with an incorrect primary address was discarded.
Procedure
----End
76.10 PIM/4/FNDNBR_DNDB_F
Message
PIM/4/FNDNBR_DNDB_F:In VPN instance \"[vpn-instance-name]\", finding neighbor
[neighbor-address] on interface [interface-name] ([interface-address]) from entry ([sourceaddress]/[source-address-mask], [group-address]/[group-address-mask])'s DNDB failed.
Description
Failed to find the corresponding neighbor record in the DNDB.
Issue 07 (2014-07-30)

818

Log Reference
76 PIM
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
[neighbor-address]
[interface-name]
[interface-address]
[source-address]
[source-address-mask] Indicates the mask of the source address.

[group-address]
[group-address-mask] Indicates the mask of the group address.

FlCode
log message.
Possible Causes
Failed to find the corresponding neighbor record in the DNDB.
Procedure
----End
76.11 PIM/5/GR_END
Message
PIM/5/GR_END:In VPN instance \"[vpn-instance-name]\", PIM left the GR status. The reason
code was [reason-code]. (FlCode=[STRING][ULONG])
Description
The VPN instance exited from the PIM GR state.
Parameters
Parameter Name
Parameter Meaning
Issue 07 (2014-07-30)

819

Log Reference
Parameter Name
Parameter Meaning
[reason-code]
Indicates the reason code. The value can be:
76 PIM
l 0: The parameter is invalid.

l 1: The GR timer expires and the GR process is ended normally.
l 2: Multicast is disabled to end GR.
l 3: PIM SM is disabled to end GR.
l 4: GR of the VPN instance is ended.
l 5: The Force timer expires and the GR process is ended.
l 6: GR is not enabled and is directly ended.
l 7: Other components are terminated and thus GR is ended.
log message.
FlCode
Possible Causes
1:
The GR timer expires.
2:
The VPN instance that perform PIM GR is deleted.
3:
The interface board where the last PIM-SM interface resides is removed.
4:
The GR timer of the IPv4 public network expires. When the GR processes of the VPN instances
that depend on the IPv4 public network are ended, the GR process of the IPv4 public network
is ended.
Procedure
l
----End
76.12 PIM/5/GR_START
Message
PIM/5/GR_START:In VPN instance \"[vpn-instance-name]\", PIM entered the GR status. The
minimum holding time was [gr-period] seconds. (FlCode=[STRING][ULONG])
Issue 07 (2014-07-30)

820

Log Reference
76 PIM
Description
The VPN instance entered the PIM GR state.
Parameters
Parameter Name
Parameter Meaning

[gr-period]
Indicates the GR period.
FlCode
log message.
Possible Causes
PIM GR is enabled in the VPN instance, and the master/slave switchover is performed.
Procedure
l
----End
76.13 PIM/6/GRP_ADDR_IS_LOCAL
Message
PIM/6/GRP_ADDR_IS_LOCAL:In VPN instance [vpn-instance-name], because the group
address [group-address]/[group-mask-length] is a link/node local address, the [message-type]
message received from the interface [interface-name] was ignored. (FlCode=[STRING]
[ULONG])
Description
The group address contained in a PIM message, which was a local multicast address, was
ignored.
Parameters
Parameter Name
Parameter Meaning

[group-address]
[group-mask-length] Indicates the mask length of group address.
Issue 07 (2014-07-30)

821

Log Reference
Parameter Name
Parameter Meaning
[message-type]
Indicates the message type. The value can be:
76 PIM
l PIM Join/Prune message

l PIM SM Assert message
l PIM SM Register-Stop message
l PIM SSM Assert message
[interface-name]
FlCode
log message.
Possible Causes
The PIM-SM-enabled interface receives a PIM message, the group address contained in which
is a local multicast address.
Procedure
l
----End
76.14 PIM/6/GRP_ADDR_NOT_MCAST
Message
PIM/6/GRP_ADDR_NOT_MCAST:In VPN instance [vpn-instance-name], because the group
address [group-address]/[group-mask-length] is not a multicast address, the [message-type]
message received from the interface [interface-name] was ignored. (FlCode=[STRING]
[ULONG])
Description
The group address contained in a PIM message, which was not a multicast address, was ignored.
Parameters
Parameter Name
Parameter Meaning

[group-address]
Issue 07 (2014-07-30)

822

Log Reference
Parameter Name
Parameter Meaning
[message-type]
76 PIM

[interface-name]
FlCode
log message.
Possible Causes
The PIM-SM-enabled interface receives a PIM message, the group address contained in which
is not a multicast address.
Procedure
l
----End
76.15 PIM/6/GRP_MASK_UNSUPPORTED
Message
PIM/6/GRP_MASK_UNSUPPORTED:In VPN instance [vpn-instance-name], because the
length of the mask of the group address [group-address]/[group-mask-length] is unsupported,
the [message-type] message received from the interface [interface-name] was ignored. (FlCode=
[STRING][ULONG])
Description
The group address contained in a PIM message was ignored, because the mask length of the
group address was not supported by PIM.
Parameters
Parameter Name
Parameter Meaning

[group-address]
Issue 07 (2014-07-30)

823

Log Reference
Parameter Name
Parameter Meaning
[message-type]
76 PIM

[interface-name]
FlCode
log message.
Possible Causes
The PIM-SM-enabled interface receives a PIM message, the mask length of the group address
contained in which is not supported by PIM.
Procedure
l
----End
76.16 PIM/6/HELPKT_UNSADDR_ERR
Message
PIM/6/HELPKT_UNSADDR_ERR:In VPN instance \"[vpn-instance-name]\", the incorrect
unicast source address of this Hello packet was ignored. (FlCode=[STRING][ULONG])
Description
A Hello message with an incorrect unicast source address was discarded.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
A Hello message with an incorrect unicast source address was discarded.
Issue 07 (2014-07-30)

824

Log Reference
76 PIM
Procedure
----End
76.17 PIM/3/HOLDTIME_LESS_INL
Message
PIM/3/HOLDTIME_LESS_INL:In VPN instance \"[vpn-instance-name]\", when the BSR
holdtime and sending interval were configured, the BSR holdtime [holdtime] was less than the
sending interval [interval]. (FlCode=[STRING][ULONG])
Description
The BSR holdtime is smaller than the BSR sending interval.
Parameters
Parameter Name
Parameter Meaning

[holdtime]
Indicates the BSR holdtime.
[interval]
Indicates the interval for sending BSR messages.
FlCode
log message.
Possible Causes
This log message is generated when BSR parameters are configured or modified.
Procedure
Step 1 Run the c-bsr holdtime interval command to reconfigure the BSR holdtime. Run the c-bsr
interval interval command to reconfigure the interval for the BSR to send Bootstrap messages.
Ensure that the BSR holdtime is greater than the BSR sending interval.
----End
76.18 PIM/4/INT_INV
Issue 07 (2014-07-30)

825

Log Reference
76 PIM
Message
PIM/4/INT_INV:In VPN instance \"[vpn-instance-name]\", a PIM packet received on an
unknown interface was discarded. (FlCode=[STRING][ULONG])
Description
The PIM packet was received on an unknown interface and was then discarded.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
An unexpected interface event occurred.
Procedure
Step 1 Collect information about manufacturers and versions of other devices in the shared network,
network topology, and all configurations and log messages of the device itself. Contact Huawei
----End
76.19 PIM/5/INVSRC
Message
PIM/5/INVSRC:In VPN instance \"[vpn-instance-name]\", the invalid source address [sourceaddress] was ignored. (FlCode=[STRING][ULONG])
Description
The source address of the received protocol packet was invalid.
Parameters
Parameter Name
Parameter Meaning

[source-address]
FlCode
log message.
Issue 07 (2014-07-30)

826

Log Reference
76 PIM
Possible Causes
The source address of the (S, G) entry to be created is unreachable.
Procedure
----End
76.20 PIM/4/JP_SRCERR
Message
PIM/4/JP_SRCERR:In VPN instance \"[vpn-instance-name]\", the Join/Prune packet with an
incorrect source address was ignored when being processed. (FlCode=[STRING][ULONG])
Description
The Join/Prune message with an incorrect source address was discarded.
Parameters
Parameter Name
Parameter Meaning

FlCode
log message.
Possible Causes
The Join/Prune message with an incorrect source address was discarded.
Procedure
----End
76.21 PIM/6/MTU_IF_SHT
Issue 07 (2014-07-30)

827

Log Reference
76 PIM
Message
PIM/6/MTU_IF_SHT:In VPN instance \"[vpn-instance-name]\", the MTU of the interface
[interface-name] was [mtu], which was too small to send pim Hello packet. (FlCode=[STRING]
[ULONG])
Description
Failed to send the PIM Hello message because the MTU of the interface was too small.
Parameters
Parameter Name
Parameter Meaning

[interface-name]
[mtu]
Indicates the Maximum Transmission Unit (MTU).
FlCode
log message.
Possible Causes
Failed to send the PIM Hello message because the MTU of the interface was too small.
Procedure
----End
76.22 PIM/4/NBR_DOWN
Message
PIM/4/NBR_DOWN:In VPN instance \"[vpn-instance-name]\", a neighbor was deleted from
the interface. The reason is [reason] (NeighborIpAddress=[STRING], Interface=[STRING],
FlCode=[STRING][ULONG])
Description
A neighbor was deleted from the neighbor list of the interface.
Issue 07 (2014-07-30)

828

Log Reference
76 PIM
Parameters
Parameter Name
Parameter Meaning

[reason]
Indicates the possible causes of PIM neighbor loss:

l Hold time expired
l Receive hello message with holdTime zero
l BFD session down
l PIM status of the interface changes
NeighborIpAddress
Interface
FlCode
log message.
Possible Causes
1. The interface did not receive any Hello message within a certain period, which caused the
timeout of the PIM neighbor relationship.
2. The interface received a Hello message with the Holdtime field being 0.
3. The BFD session on the interface was Down.
4. PIM status of the interface changes.
Procedure
Step 1 Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface verbose
command to check whether the interface is in the Up state and check the BFD session status.
Ensure that the link can work normally.
----End
76.23 PIM/4/NBR_DOWN_ALL
Message
PIM/4/NBR_DOWN_ALL:In VPN instance \"[vpn-instance-name]\", all neighbors were
deleted from the interface because the interface was down or PIM was disabled on the interface.
(Interface=[STRING], FlCode=[STRING][ULONG])
Description
All PIM neighbors were deleted from the interface because the interface became Down or PIM
was disabled on the interface.
Issue 07 (2014-07-30)

829

Log Reference
76 PIM
Parameters
Parameter Name
Parameter Meaning

Interface
FlCode
log message.
Possible Causes
1. The interface became Down.
2. PIM was disabled.
Procedure
Step 1 Run the display pim [ vpn-instance vpn-instance-name | all-instance ] interface verbose
command to check whether the interface is in the Up state. Ensure that the link works normally.
----End
76.24 PIM/4/NBR_UP
Message
PIM/4/NBR_UP:In VPN instance \"[vpn-instance-name]\", a new neighbor was created on the
interface. (NeighborIpAddress=[STRING], Interface=[STRING], FlCode=[STRING]
[ULONG])
Description
A neighbor was added to the neighbor list of the interface.
Parameters
Parameter Name
Parameter Meaning

NeighborIpAddress
Interface
FlCode
log message.
Issue 07 (2014-07-30)

830

Log Reference
76 PIM
Possible Causes
A PIM Hello message was received from a new neighbor.
Procedure
l
----End
76.25 PIM/4/PIMPKT_CHKSUM_ERR
Message
PIM/4/PIMPKT_CHKSUM_ERR:In VPN instance \"[vpn-instance-name]\", the PIM packet
received from [source-address] was discarded because the checksum of this packet was incorrect.
Description
The received PIM packet was discarded because the checksum was incorrect.
Parameters
Parameter Name
Parameter Meaning

[source-address]
FlCode
log message.
Possible Causes
1. Bad conditions of the link lead to the transmission error.
2. The received packet is an attack PIM packet.
Procedure
Step 1 If the fault occurs occasionally, the fault may be caused by link transmission, and this log
message can be ignored.
Step 2 If the fault occurs frequently, check the link conditions and use the packet hearder obtaining tool
to obtain PIM packets. Obtain information about manufacturers and versions of other devices
in the shared network and network topology, and then contact Huawei technical support
personnel.
----End
Issue 07 (2014-07-30)

831

Log Reference
76 PIM
76.26 PIM/4/PIM_GR_FORCE_SYNC
Message
PIM/4/PIM_GR_FORCE_SYNC:In VPN instance \"[vpn-instance-name]\", PIM was forced to
enter the GR Synchronous state. (FlCode=[STRING][ULONG])
Description
PIM was forced to enter the GR Synchronous state.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name] Name of a VPN instance

FlCode
Possible Causes
Unicast GR was not complete, but the PIM GR force timer expired.
Procedure
Step 1 Record the log information and contact Huawei technical support personnel.
----End
76.27 PIM/3/PUTNBR_DNDB_F
Message
PIM/3/PUTNBR_DNDB_F:In VPN instance \"[vpn-instance-name]\", adding neighbor
[neighbor-address] on interface [interface-name] ([group-address]) to entry ([source-address]/
[source-address-mask], [group-address]/[group-address-mask])'s DNDB failed. (FlCode=
[STRING][ULONG])
Description
Failed to add information about a neighbor into the DNDB.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
Issue 07 (2014-07-30)

832

Log Reference
Parameter Name
Parameter Meaning
[neighbor-address]
[interface-name]
[group-address]
[source-address]
76 PIM
[source-address-mask] Indicates the mask of the source address.

[group-address-mask] Indicates the mask of the group address.
FlCode
log message.
Possible Causes
Failed to add information about a neighbor into the DNDB.
Procedure
Step 1 Check that the number of neighbors does not exceed 128.
----End
76.28 PIM/6/SEC_ADDRFA_ERR
Message
PIM/6/SEC_ADDRFA_ERR:In VPN instance \"[vpn-instance-name]\", the packet with an
unknown secondary address family [address-family] was ignored. (FlCode=[STRING]
[ULONG])
Description
A Hello message with an unknown secondary address family was discarded.
Parameters
Parameter Name
Parameter Meaning

[address-family]
Indicates the address family.
FlCode
log message.
Issue 07 (2014-07-30)

833

Log Reference
76 PIM
Possible Causes
A Hello message with an unknown secondary address family was discarded.
Procedure
----End
76.29 PIM/3/SOCK_ERR1
Message
PIM/3/SOCK_ERR1:In VPN instance \"[vpn-instance-name]\", PIM failed to set socket option
that multicast joined the PIM group. The error code was [error-code]. (FlCode=[STRING]
[ULONG])
Description
Failed to join the PIM group by setting the Socket option.
Parameters
Parameter Name
Parameter Meaning

[error-code]
FlCode
log message.
Possible Causes
Failed to join the PIM router group by setting the Socket option.
Procedure
Step 1 Collect all configurations, and then contact Huawei technical support personnel.
----End
76.30 PIM/6/SRC_MASK_UNSUPPORTED
Issue 07 (2014-07-30)

834

Log Reference
76 PIM
Message
PIM/6/SRC_MASK_UNSUPPORTED:In VPN instance [vpn-instance-name], the length of the
mask of the source address [source-address]/[source-mask-length] in the Join/Prune message
was unsupported, so this source was ignored. (FlCode=[STRING][ULONG])
Description
The source address contained in the Join/Prune message was ignored, because PIM-SM did not
support the mask length of the source address.
Parameters
Parameter Name
Parameter Meaning

[source-address]
[source-mask-length] Indicates the mask length of source address.

FlCode
log message.
Possible Causes
The PIM-SM-enabled interface receives a Join/Prune message, the mask length of the source
address contained in which is not supported by PIM-SM.
Procedure
l
----End
Issue 07 (2014-07-30)

835

Log Reference
77 POE
77
POE
About This Chapter

77.1 POE/4/LEGACYPD
77.2 POE/6/PDOVERCURRENT
77.3 POE/6/PDCONNECT
77.4 POE/6/PDDISCONNECT
77.5 POE/6/PDPOWEROFF
77.6 POE/6/PDPOWERON
77.7 POE/6/PORTERROR
77.8 POE/6/PORTPDOVERLD
77.9 POE/6/PORTPW
77.10 POE/6/POWERFAIL
77.11 POE/6/POWERSUCCESS
77.12 POE/6/RESETPORT
Issue 07 (2014-07-30)

836

Log Reference
77 POE
77.1 POE/4/LEGACYPD
Message
POE/4/LEGACYPD:PD on the interface [STRING] is non-standard.
Description
A non-standard powered device (PD) is connected to an interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the interface number.
Possible Causes
A non-standard PD is connected to the interface.
Procedure
l
If the PD is not powered on, run the poe legacy enable command on the specified interface
to power on the PD.
----End
77.2 POE/6/PDOVERCURRENT
Message
POE/6/PDOVERCURRENT: PD on the interface [STRING] is overcurrent.
Description
The current from the PD connected to a port is too high.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates a port ID.
Possible Causes
The current from the PD connected to the port is too high.
Issue 07 (2014-07-30)

837

Log Reference
77 POE
Procedure
Step 1 Run the poe high-inrush enable command in the system view to configure the device to allow
high inrush current.
Step 2 If the problem persists, replace the PD.
Step 3 If the problem persists, contact Huawei technical personnel.
----End
77.3 POE/6/PDCONNECT
Message
POE/6/PDCONNECT: PD on the interface [STRING] is connected.
Description
A PD is connected to a port.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
l
A PD is connected to the port.
Procedure
----End
77.4 POE/6/PDDISCONNECT
Message
POE/6/PDDISCONNECT: PD on the interface [STRING] is disconnected.
Description
A PD is disconnected from a port.
Issue 07 (2014-07-30)

838

Log Reference
77 POE
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
l
The PD is disconnected from the port.
Procedure
----End
77.5 POE/6/PDPOWEROFF
Message
POE/6/PDPOWEROFF: PD on the interface [STRING] is powered off.
Description
The PD on a port is powered off.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
l
The PD is disconnected from the port.
The available PoE power is insufficient for the PD.
The PD is manually powered off.
The current time is within the configured power-off time range.
Procedure
Step 1 Run the display poe power-state command to check the PoE power supply status. If the
STATUS field displays Time-range power-off, the current time is within the power-off time
range.
Step 2 Run the display poe information command to check PoE configuration on the device. If the
Power-Management Mode field displays manual, the PD has been manually powered off.
Step 3 If neither of the preceding configurations is displayed, check whether the physical link between
the PD and the port is disconnected.
Issue 07 (2014-07-30)

839

Log Reference
77 POE
Step 4 If the PD is connected to the port properly, run the display poe information command to check
the available PoE power (Available Total Power(mW) field value in the command output). If
the available PoE power is insufficient, the PD may fail the preemption for PoE power.
----End
77.6 POE/6/PDPOWERON
Message
POE/6/PDPOWERON: PD on the interface [STRING] is powered on.
Description
The PD on a port is powered on.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The PD connected to the port is powered on.
Procedure
l
----End
77.7 POE/6/PORTERROR
Message
POE/6/PORTERROR: Port [STRING] error.
Description
A port is faulty and cannot provide PoE power.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Issue 07 (2014-07-30)

840

Log Reference
77 POE
Possible Causes
The chip on the dual in-line memory module (DIMM) fails.
Procedure
Step 1 Reset the port.
Step 2 If the problem persists after the reset, contact Huawei technical support personnel.
----End
77.8 POE/6/PORTPDOVERLD
Message
POE/6/PORTPDOVERLD: PD on port [STRING] over load.
Description
The power of PD connected to a port exceeds the maximum power of the port.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The power of the PD exceeds the maximum power of the port.
Procedure
l
Run the poe power command to increase the maximum power of the port.
----End
77.9 POE/6/PORTPW
Message
POE/6/PORTPW: Port [STRING] current power is [ULONG].
Description
This log shows the current power of the PD on a port.
Issue 07 (2014-07-30)

841

Log Reference
77 POE
Parameters
Parameter Name
Parameter Meaning
[STRING]
[ULONG]
Power of the PD on the port. The unit is in mW.
Possible Causes
Procedure
l
----End
77.10 POE/6/POWERFAIL
Message
POE/6/POWERFAIL: PD on the interface [STRING] powered fail.
Description
The PD connected to port fails to be powered on.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The system fails to read or write chip register values.
Procedure
l
----End
77.11 POE/6/POWERSUCCESS
Message
POE/6/POWERSUCCESS: PD on the interface [STRING] powered success.
Issue 07 (2014-07-30)

842

Log Reference
77 POE
Description
The PD connected to a port is successfully powered on.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
Procedure
l
----End
77.12 POE/6/RESETPORT
Message
POE/6/RESETPORT: Reset this port [STRING].
Description
A port is reset some time after it failed.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The chip on the dual in-line memory module (DIMM) fails.
Procedure
l
If the problem persists after the reset, contact Huawei technical support personnel.
----End
Issue 07 (2014-07-30)

843

Log Reference
78 Portal
78
Portal
About This Chapter

78.1 WEB/4/PORTALSERVER_DOWN
78.2 WEB/4/PORTALSERVER_UP
78.3 WEB/4/WEBSOCK
Issue 07 (2014-07-30)

844

Log Reference
78 Portal
78.1 WEB/4/PORTALSERVER_DOWN
Message
WEB/4/PORTALSERVER_DOWN: The portal server is down.(IP:[IPADDR])
Description
The Portal server is Down.
Parameters
Parameter Name
Parameter Meaning
IP
Indicates the IP address of the Portal server.
Possible Causes
The device detects that the Portal server changes from Up to Down.
Procedure
Step 1 Check whether the Portal server can work properly and whether the Portal service can be used
properly.
l If the Portal server works properly, check the network connectivity between the Portal server
and device. If the network connection is disconnected, restore the network connection.
l If the Portal server cannot work properly, restore the Portal server to the normal state.
----End
78.2 WEB/4/PORTALSERVER_UP
Message
WEB/4/PORTALSERVER_UP: The portal server is up.(IP:[IPADDR])
Description
The Portal server is Up.
Parameters
Parameter Name
Parameter Meaning
IP
Indicates the IP address of the Portal server.
Issue 07 (2014-07-30)

845

Log Reference
78 Portal
Possible Causes
The device detects that the Portal server changes from Down to Up.
Procedure
----End
78.3 WEB/4/WEBSOCK
Message
WEB/4/WEBSOCK:Failed to start web authentication server listening port.
Description
The listening port of the Portal authentication server cannot start.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
l
The listening port of the Portal authentication server is occupied.
Procedure
Step 1 Use an available listening port.
----End
Issue 07 (2014-07-30)

846

Log Reference
79 QinQ
79
QinQ
About This Chapter

79.1 QINQ/5/ISSUSPEC_CHECK
79.2 QINQ/5/ISSU_CHECK_ERR
79.3 QINQ/5/ISSU_CHECK_OK
Issue 07 (2014-07-30)

847

Log Reference
79 QinQ
79.1 QINQ/5/ISSUSPEC_CHECK
Message
QINQ/5/ISSUSPEC_CHECK:The QinQ specifications were changed in the new version.
(Spec=[STRING], Value=[ULONG])
Description
QinQ specifications were changed in the new version.
Parameters
Parameter Name
Parameter Meaning
Spec
Specifications
Value
Value
Possible Causes
QinQ specifications were changed in the new version.
Procedure
Step 1 Stop the ISSU.
Step 2 Perform the lossy ISSU.
----End
79.2 QINQ/5/ISSU_CHECK_ERR
Message
QINQ/5/ISSU_CHECK_ERR:The ISSU check failed because of the [STRING].
Description
The specification change or incompatibility cause the ISSU check on the QinQ module to be
failed.
Issue 07 (2014-07-30)

848

Log Reference
79 QinQ
Parameters
STRING
Causes for the ISSU check failure may be:

l failure in getting specification data: Failed to obtain the specification
data.
l specification change: Specifications were changed.
l incompatible version: Versions were incompatible.
l existing configuration: Other configurations existed.
Possible Causes
After checking specifications, incompatibility, and configurations, the QinQ module finds that
it does not support the lossless ISSU.
Procedure
----End
79.3 QINQ/5/ISSU_CHECK_OK
Message
QINQ/5/ISSU_CHECK_OK:The ISSU check succeeded.
Description
The ISSU check succeeded.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
After checking, the QinQ module can perform the lossless ISSU.
Issue 07 (2014-07-30)

849

Log Reference
79 QinQ
Procedure
----End
Issue 07 (2014-07-30)

850

Log Reference
80 RDS
80
RDS
About This Chapter

80.1 RDS/4/RDACCTDOWN
80.2 RDS/6/RDACCTUP
80.3 RDS/4/RDAUTHDOWN
80.4 RDS/6/RDAUTHUP
Issue 07 (2014-07-30)

851

Log Reference
80 RDS
80.1 RDS/4/RDACCTDOWN
Message
RDS/4/RDACCTDOWN:"RADIUS accounting server ( IP:[STRING] ) is down!."
Description
The communication of the RADIUS accounting server is interrupted.
Parameters
IP:[STRING]
Indicates the IP address and VPN instance name of the RADIUS

accounting server.
Possible Causes
The communication of the RADIUS accounting server is interrupted.
Procedure
Step 1 Check whether the RADIUS accounting server is shut down.
1.
If the RADIUS accounting server is shut down by the user, no action is required.
2.
If the RADIUS accounting server is not shut down, go to step 2.
Step 2 Check whether the link is normal.

1.
If the link is abnormal, restore the link.
2.
If the link is normal, go to step 3.
Step 3 Check that the client is added to the RADIUS accounting server, and the shared key is configured
correctly on the RADIUS accounting server.
1.
If the configuration is incorrect, correct the configuration.
2.
If the configuration is correct, go to step 4.

----End
80.2 RDS/6/RDACCTUP
Message
RDS/6/RDACCTUP:"RADIUS accounting server ( IP:[STRING] ) is up."
Issue 07 (2014-07-30)

852

Log Reference
80 RDS
Description
The communication of the RADIUS accounting server is restored.
Parameters
IP:[STRING]

accounting server.
Possible Causes
The communication of the RADIUS accounting server is restored.
Procedure
Step 1 This log indicates that the RADIUS accounting server is restored, and no action is required.
----End
80.3 RDS/4/RDAUTHDOWN
Message
RDS/4/RDAUTHDOWN:"RADIUS authentication server ( IP:[STRING] ) is DOWN."
Description
The communication of the RADIUS authentication server is interrupted.
Parameters
IP:[STRING]

authentication server.
Possible Causes
The communication of the RADIUS authentication server is interrupted.
Procedure
Step 1 Check whether the RADIUS authentication server is shut down.
1.
If the RADIUS authentication server is shut down by the user, no action is required.
2.
If the RADIUS authentication server is not shut down, go to step 2.
Step 2 Check whether the link is normal.

Issue 07 (2014-07-30)

853

Log Reference
1.
If the link is abnormal, restore the link.
2.
If the link is normal, go to step 3.
80 RDS
Step 3 Check that the client is added to the RADIUS authentication server, and the shared key is
configured correctly on the RADIUS authentication server.
1.
If the configuration is incorrect, correct the configuration.
2.
If the configuration is correct, go to step 4.

----End
80.4 RDS/6/RDAUTHUP
Message
RDS/6/RDAUTHUP:"RADIUS authentication server ( IP:[STRING] ) is up."
Description
The communication of the RADIUS authentication server is restored.
Parameters
IP:[STRING]

authentication server.
Possible Causes
The communication of the RADIUS authentication server is restored.
Procedure
Step 1 This log indicates that the RADIUS authentication server is restored, and no action is required.
----End
Issue 07 (2014-07-30)

854

Log Reference
81 RIP
81
RIP
About This Chapter

81.1 RIP/3/ADD_RTE_F
81.2 RIP/3/DEL_SAMEADDR_PEER_F
81.3 RIP/6/FREEZE_ENTER
81.4 RIP/6/FREEZE_RECOVER
81.5 RIP/6/GR_ABORT
81.6 RIP/6/GR_ENTER
81.7 RIP/6/GR_ENTER_HELPER
81.8 RIP/6/GR_EXIT
81.9 RIP/6/GR_EXIT_HELPER
81.10 RIP/6/GR_EXIT_RT_UPDT
81.11 RIP/3/GR_RCV_ABORT
81.12 RIP/6/GR_SND_ABORT
81.13 RIP/6/GR_TOPO_CHANGE
81.14 RIP/3/MAX_LOGIF_REACH_F
81.15 RIP/6/MEMSHORT_ENTER
81.16 RIP/6/MEMSHORT_RECOVER
81.17 RIP/6/RIP_NBR_ADD
81.18 RIP/6/RIP_NBR_DEL
81.19 RIP/6/RCV_HA_SMOVER
Issue 07 (2014-07-30)

855

Log Reference
81 RIP
81.1 RIP/3/ADD_RTE_F
Message
RIP/3/ADD_RTE_F: Because of unsuccessful validation, routes not added to database. Total
[number] occurrences since [date] [time].(Destination=[IPADDR]/[STRING], Interface=
[STRING], ProcessId=[ULONG]).
Description
Failed to add routes to the database due to unsuccessful validation.
Parameters
[number]
Indicates the number of failed attempts to authenticate RIP routes and

install RIP routes to the database.
[date]
Indicates the date when the last RIP classful node was added to the update
list.
[time]
Indicates the time when the last RIP classful node was added to the update
list.
Destination
Interface
ProcessId
Possible Causes
Failed to add routes to the database due to unsuccessful validation.
Procedure
----End
81.2 RIP/3/DEL_SAMEADDR_PEER_F
Issue 07 (2014-07-30)

856

Log Reference
81 RIP
Message
RIP/3/DEL_SAMEADDR_PEER_F:Deleted the peer [IPADDR] configuration with the same
address as the local interface. (ProcessId=[ULONG], Interface=[STRING])
Description
The configuration of the neighboring interface with the same IP address as the local interface
was deleted.
Parameters
Parameter Name
Parameter Meaning
[IPADDR]
Interface address
ProcessId
Process ID
Interface
Interface name
Possible Causes
The local interface and the neighboring interface had the same IP address.
Procedure
Step 1 Change the IP address of the neighboring interface or the local interface.
----End
81.3 RIP/6/FREEZE_ENTER
Message
RIP/6/FREEZE_ENTER:The number of routes on RIP process [process-id] reached the upper
threshold, and thus the RIP process was suspended.
Description
The number of routes on the RIP process reached the upper threshold, and thus the RIP process
was suspended and did not process the received packets.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the RIP process ID.
Possible Causes
The number of routes on the RIP process reached the upper threshold.
Issue 07 (2014-07-30)

857

Log Reference
81 RIP
Procedure
----End
81.4 RIP/6/FREEZE_RECOVER
Message
RIP/6/FREEZE_RECOVER:The number of routes reached the lower threshold, and thus RIP
process [process-id] recovered from the suspension state and resumed processing packets.
Description
The number of routes reached the lower threshold, and thus the RIP process recovered from the
suspension state and resumed processing packets.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the RIP process ID.
Possible Causes
The number of routes reached the lower threshold.
Procedure
----End
81.5 RIP/6/GR_ABORT
Message
RIP/6/GR_ABORT: Aborted Graceful Restart. (AbortReason=[STRING], ProcessId=
[ULONG])
Description
The GR process was aborted exceptionally.
Issue 07 (2014-07-30)

858

Log Reference
81 RIP
Parameters
AbortReason
Indicates the cause of abort.

l Virtual interface delete or Virtual interface went UP to Down event.
l 1. An abort message wass received from the Helper because of the
topology changed.
l 2. An interface was added to the Restarter.
l 3. The Restarter deleted existing interface.
l 4. The status was changed.
l 5. An event of deleting an interface or an event that interface status
changes from Up to Down occurred.
ProcessId
Possible Causes
The GR process was aborted exceptionally.
Procedure
Step 1 Services will be interrupted temporarily and then restored after the GR process is complete.
----End
81.6 RIP/6/GR_ENTER
Message
RIP/6/GR_ENTER: Entering Graceful Restart mode. (Mode=[STRING], ProcessId=
[ULONG])
Description
The GR process started on the switch.
Parameters
Parameter Name
Parameter Meaning
Mode
Indicates the GR mode.

l 1: planned
l 2: unplanned
ProcessId
Issue 07 (2014-07-30)

859

Log Reference
81 RIP
Possible Causes
The GR process started on the switch.
Procedure
----End
81.7 RIP/6/GR_ENTER_HELPER
Message
RIP/6/GR_ENTER_HELPER: Entering helper mode for restarting neighbor [ip-address] for
[timer-value] seconds. (ProcessId=[ULONG])
Description
The switch started to function as GR Helper for the neighbor functioning as GR Restarter.
Parameters
Parameter Name
Parameter Meaning
[ip-address]
Indicates the IP address of a switch functioning as GR Helper.
[timer-value]
Indicates the value of a GR cut-off timer.
ProcessId
Possible Causes
The switch started to function as GR Helper for the neighbor functioning as GR Restarter.
Procedure
----End
81.8 RIP/6/GR_EXIT
Message
RIP/6/GR_EXIT: Exiting Graceful Restart mode. (Mode=[STRING], ProcessId=[ULONG])
Issue 07 (2014-07-30)

860

Log Reference
81 RIP
Description
The switch functioning as GR Restarter exited from the GR process.
Parameters
Parameter Name
Parameter Meaning
Mode
Indicates the GR mode.
ProcessId
Possible Causes
The GR process was complete on the switch functioning as GR Restarter.
Procedure
----End
81.9 RIP/6/GR_EXIT_HELPER
Message
RIP/6/GR_EXIT_HELPER: Exiting helper mode for restarting neighbor [IPAddress]. (Reason=
[STRING], ProcessId=[ULONG])
Description
After the GR process was complete, the switch functioning as GR Helper exited from the Helper
mode.
Parameters
Parameter Name
Parameter Meaning
IPAddress
Indicates the IP address of the switch functioning as GR Helper.
Reason
Indicates the cause of abort.
ProcessId
Possible Causes
After the GR process was complete, the switch was no longer the GR Helper for the neighbor.
Issue 07 (2014-07-30)

861

Log Reference
81 RIP
Procedure
----End
81.10 RIP/6/GR_EXIT_RT_UPDT
Message
RIP/6/GR_EXIT_RT_UPDT: Exiting route update phase. (Reason=[STRING], ProcessId=
[ULONG])
Description
The update of routes was complete.
Parameters
Parameter Name
Parameter Meaning
Reason
Indicates the cause of stopping updating routes.
ProcessId
Possible Causes
After the Restarter received the UCN(Update Complete Notification) from the Helper, the
Restarter updated routes and sent routes to the RM.
Procedure
----End
81.11 RIP/3/GR_RCV_ABORT
Message
RIP/3/GR_RCV_ABORT: Received abort notification from helper [IPADDR] on interface
[InterfaceName]. (ProcessId=[ULONG])
Description
The Restarter switch received an exceptional abort message from the Helper switch.
Issue 07 (2014-07-30)

862

Log Reference
81 RIP
Parameters
Parameter Name
Parameter Meaning
[IPADDR]
Indicates the IP address of the switch functioning as GR Helper.
[InterfaceName]
ProcessId
Possible Causes
The topology or configuration was changed.
Procedure
Step 1 This log message indicates that the GR process is terminated, and no action is required.
----End
81.12 RIP/6/GR_SND_ABORT
Message
RIP/6/GR_SND_ABORT: Sending abort notification to neighbor [IPADDR] on interface
[InterfaceName]. (ProcessId=[ULONG])
Description
An exceptional abort notification was sent to the neighbor.
Parameters
Parameter Name
Parameter Meaning
[IPADDR]
Indicates the IP address of the switch functioning as GR Restarter.
[InterfaceName]
ProcessId
Possible Causes
An exceptional abort notification, indicating that the topology or configuration was changed,
was sent to the neighbor.
Procedure
----End
Issue 07 (2014-07-30)

863

Log Reference
81 RIP
81.13 RIP/6/GR_TOPO_CHANGE
Message
RIP/6/GR_TOPO_CHANGE: Detected topology change on interface [interface-name].
(ProcessId=[ULONG])
Description
The Restarter switch sent a message indicating the topology change.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
ProcessId
Possible Causes
The topology was changed after some routes were deleted.
Procedure
----End
81.14 RIP/3/MAX_LOGIF_REACH_F
Message
RIP/3/MAX_LOGIF_REACH_F: The number of supported logical interfaces reached the
maximum value. Total [ULONG] occurrences since [STRING] [STRING]. (ProcessId=
[ULONG]).
Description
The number of supported logical interfaces in the process reached the maximum. Total
[ULONG] occurrences since [STRING] [STRING].
Issue 07 (2014-07-30)

864

Log Reference
81 RIP
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Maximum number of packets requested.
[STRING]
Day of the last packet requested.
[STRING]
Time of the last packet requested.
ProcessId
Possible Causes
The number of supported logical interfaces in the process reached the maximum.
Procedure
Step 1 Collect the log message and contact Huawei technical personnel.
----End
81.15 RIP/6/MEMSHORT_ENTER
Message
RIP/6/MEMSHORT_ENTER:RIP received memory shortage notification.
Description
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
Step 1 Run the display diagnostic-information command to save the displayed result, and contact
Huawei technical personnel.
----End
Issue 07 (2014-07-30)

865

Log Reference
81 RIP
81.16 RIP/6/MEMSHORT_RECOVER
Message
RIP/6/MEMSHORT_RECOVER:RIP received memory shortage recovery notification.
Description
The system recovered from memory shortage.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
81.17 RIP/6/RIP_NBR_ADD
Message
RIP/6/RIP_NBR_ADD: RIP neighbor is added on the interface. (ProcessId=[ULONG],
Interface=[STRING], Neighbor=[IPADDR])
Description
A RIP neighbor is added on the interface.
Parameters
Parameter Name
Parameter Meaning
ProcessId
ID of a RIP process
Interface
Interface name
Issue 07 (2014-07-30)

866

Log Reference
81 RIP
Parameter Name
Parameter Meaning
Neighbor
IP address of a neighbor
Possible Causes
The router receives information about the new neighbor.
Procedure
----End
81.18 RIP/6/RIP_NBR_DEL
Message
RIP/6/RIP_NBR_DEL: RIP Neighbor is deleted from the interface. (ProcessId=[ULONG],
Interface=[STRING], Neighbor=[IPADDR], Reason=[STRING])
Description
A RIP neighbor is deleted from the interface.
Parameters
Parameter Name
Parameter Meaning
ProcessId
ID of a RIP process
Interface
Interface name
Neighbor
IP address of a neighbor
Reason
Reason for deleting a RIP neighbor
Possible Causes
The RIP neighbor may be deleted due to the following reasons:
l
The RIP neighbor interface went Down or was deleted.
Configurations of similar versions were changed.
Information about the BFD session in the Down state was received.
The timer expired.
Issue 07 (2014-07-30)

867

Log Reference
81 RIP
Procedure
----End
81.19 RIP/6/RCV_HA_SMOVER
Message
RIP/6/RCV_HA_SMOVER:Received the notification that HA Smooth is complete.
Description
The notification that GR is complete was received.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The notification that GR is complete was received.
Procedure
----End
Issue 07 (2014-07-30)

868

Log Reference
82 RIPNG
82
RIPNG
About This Chapter

82.1 RIPNG/6/FREEZE_ENTER
82.2 RIPNG/6/FREEZE_RECOVER
82.3 RIPNG/3/INVLD_IF_MTU_F
82.4 RIPNG/3/IPV6_DISAB_F
82.5 RIPNG/6/ISSU_COMP
82.6 RIPNG/3/MAX_LOGIF_REACH_F
82.7 RIPNG/6/MEMSHORT_ENTER
82.8 RIPNG/6/MEMSHORT_RECOVER
82.9 RIPNG/6/RIPNG_NBR_ADD
82.10 RIPNG/6/RIPNG_NBR_DEL
82.11 RIPNG/3/NO_GLO_SITE_ADDR_F
Issue 07 (2014-07-30)

869

Log Reference
82 RIPNG
82.1 RIPNG/6/FREEZE_ENTER
Message
RIPNG/6/FREEZE_ENTER:The number of routes on RIPng process [process-id] reached the
upper threshold, and thus the RIPng process was suspended.
Description
The number of routes on the RIPng process reached the upper threshold, and thus the RIPng
process was suspended and did not process the received packets.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the RIPng process ID.
Possible Causes
The number of routes on the RIPng process reached the upper threshold.
Procedure
----End
82.2 RIPNG/6/FREEZE_RECOVER
Message
RIPNG/6/FREEZE_RECOVER:The number of routes reached the lower threshold, and thus
RIPng process [process-id] recovered from the suspension state and resumed processing packets.
Description
The number of routes reached the lower threshold, and thus the RIPng process recovered from
the suspension state and resumed processing packets.
Parameters
Parameter Name
Parameter Meaning
[process-id]
Indicates the RIPng process ID.
Issue 07 (2014-07-30)

870

Log Reference
82 RIPNG
Possible Causes
The number of routes reached the lower threshold.
Procedure
----End
82.3 RIPNG/3/INVLD_IF_MTU_F
Message
RIPNG/3/INVLD_IF_MTU_F:RIPng could not run on interface [interface-name] with the MTU
as [mtu-value].
Description
The RIPng can not run on the interface with improper MTU.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[mtu-value]
Indicates the value of the maximum transmission unit.
Possible Causes
The MTU value on the interface was modified.
Procedure
Step 1 Reconfigure the MTU value.
----End
82.4 RIPNG/3/IPV6_DISAB_F
Message
RIPNG/3/IPV6_DISAB_F:IPv6 was not enabled globally. (ProcessId=[ULONG])
Description
IPv6 was not enabled globally.
Issue 07 (2014-07-30)

871

Log Reference
82 RIPNG
Parameters
Parameter Name
Parameter Meaning
ProcessId
Possible Causes
IPv6 was not enabled globally.
Procedure
Step 1 Enable IPv6 in the system view.
----End
82.5 RIPNG/6/ISSU_COMP
Message
RIPNG/6/ISSU_COMP: RIPNG finished PAF comparison. The upgrade type is [upgradetype].
Description
RIPNG completed the operation of comparing the upgrade type in the PAF/license file with that
on the local router and confirmed the upgrade type.
Parameters
Parameter Name
Parameter Meaning
[upgradetype]
Indicates the upgrade type.

l 1: lossless
l 2: lossy
Possible Causes
RIPNG completed the operation of comparing the upgrade type in the PAF/license file with that
on the local router and confirmed the upgrade type.
Procedure
----End
82.6 RIPNG/3/MAX_LOGIF_REACH_F
Issue 07 (2014-07-30)

872

Log Reference
82 RIPNG
Message
RIPNG/3/MAX_LOGIF_REACH_F:The number of RIPng configurable logical interfaces
reached the maximum value. (ProcessId=[ULONG])
Description
The maximum number of networks supported by RIPng was reached.
Parameters
Parameter Name
Parameter Meaning
ProcessId
Possible Causes
The maximum number of networks supported by RIPng was reached.
Procedure
Step 1 Delete some networks in RIPng.
----End
82.7 RIPNG/6/MEMSHORT_ENTER
Message
RIPNG/6/MEMSHORT_ENTER: RIPng received memory shortage notification.
Description
RIPng received the notfication because system memory usage is high.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The system memory usage is high.
Procedure
----End
Issue 07 (2014-07-30)

873

Log Reference
82 RIPNG
82.8 RIPNG/6/MEMSHORT_RECOVER
Message
RIPNG/6/MEMSHORT_RECOVER: RIPng received memory shortage recovery notification.
Description
RIPng received the notification that system memory shortage was recovered.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
----End
82.9 RIPNG/6/RIPNG_NBR_ADD
Message
RIPNG/6/RIPNG_NBR_ADD:RIPng neighbor is added on the interface. (ProcessId=
[ULONG], Interface=[STRING], Neighbor=[STRING])
Description
A RIPng neighbor is added on the interface.
Parameters
Parameter Name
Parameter Meaning
ProcessId
ID of a RIPng process
Interface
Interface name
Issue 07 (2014-07-30)

874

Log Reference
82 RIPNG
Parameter Name
Parameter Meaning
Neighbor
IPv6 address of a neighbor
Possible Causes
The RIPng process receives information about the new neighbor.
Procedure
----End
82.10 RIPNG/6/RIPNG_NBR_DEL
Message
RIPNG/6/RIPNG_NBR_DEL:RIPng neighbor is deleted from the interface. (ProcessId=
[ULONG], Interface=[STRING], Neighbor=[IPADDR], Reason=[STRING])
Description
A RIPng neighbor is deleted from the interface.
Parameters
Parameter Name
Parameter Meaning
ProcessId
ID of a RIPng process
Interface
Interface name
Neighbor
IPv6 address of a neighbor
Reason
Reason for deleting a RIPng neighbor
Possible Causes
The RIPng neighbor may be deleted due to the following reasons:
l
The physical or logical interface went Down or was deleted.
Configurations were changed.
The timer expired.
Issue 07 (2014-07-30)

875

Log Reference
82 RIPNG
Procedure
----End
82.11 RIPNG/3/NO_GLO_SITE_ADDR_F
Message
RIPNG/3/NO_GLO_SITE_ADDR_F:Specific request is dropped, because global or site-local
address is not assigned for interface [interface-name]. (ProcessId=[ULONG])
Description
The request of RIPng is dropped because there was no global or site-local address assigned for
interface.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
ProcessId
Possible Causes
If an Update packet was sent to a non-RIPng interface, the global address or the local address
was considered as the source address.
Procedure
Step 1 Configure a global address or a local address on the interface.
----End
Issue 07 (2014-07-30)

876

Log Reference
83 RM
83
RM
About This Chapter

83.1 RM/3/ADDHOSTRT_TBL_LMT
83.2 RM/6/CONFIRM_N
83.3 RM/6/CONFIRM_TIMEOUT
83.4 RM/6/CONFIRM_Y
83.5 RM/6/ENABLE_1MFIB
83.6 RM/3/GET_VRF_TBLID_FAL
83.7 RM/6/HANDLE_ADD_IPMSG
83.8 RM/6/HANDLE_ADDED_IPMSG
83.9 RM/6/HANDLE_DEL_IPMSG
83.10 RM/6/HANDLE_DELED_IPMSG
83.11 RM/4/INST_RCH_MAX_RT_LMT
83.12 RM/4/INST_RCH_MAX_RT6_LMT
83.13 RM/4/INST_RCH_MAXPFXLMT
83.14 RM/4/INST_RCH_MAXPFXLMT6
83.15 RM/4/IPV4_DEFT_RT_CHG
83.17 RM/3/IPV6_RCH_MAX_PFX
83.18 RM/3/LDP_SESSION_STATE
83.19 RM/3/LMTNUM_BGER_MAXPAF
83.20 RM/3/MAX_RPM_RCH
Issue 07 (2014-07-30)

877

Log Reference
83 RM
83.21 RM/3/NEW_PFX_NO_FREE_IDX
83.22 RM/3/NO_FREE_IDX_FOR_PFX
83.23 RM/3/NOTIFY_ISIS_MSG
83.24 RM/3/NOTIFY_OSPF_MSG
83.25 RM/4/PFX_MAX_NUM_CLEARED
83.26 RM/4/PFX_MID_NUM_CLEARED
83.27 RM/4/PFXNUM_EXCD_WARN
83.28 RM/4/PFXNUM_EXCD_WARN6
83.29 RM/3/PTCL_ADD_RT_MEM_SHT
83.30 RM/4/RCH_ALLVRF_RT_LMT
83.31 RM/4/RCH_ALLVRF6_RT_LMT
83.32 RM/4/RCH_MIGP_RT_LMT
83.33 RM/4/RCH_PUB_RT_LMT
83.34 RM/4/RCH_PUB6_RT_LMT
83.35 RM/3/RPM_ROUT_MAX_LMT
83.36 RM/4/RT_NUM_EXCD_WARN
83.37 RM/4/RT6_NUM_EXCD_WARN
83.38 RM/3/SMTH_ADDRT_MAX_LMT
83.39 RM/3/SNDMSG_MEM_SHORT_FAL
83.40 RM/4/SYS_RCH_MAX_RT_LMT
83.41 RM/4/SYS_RCH_MAX6_RT_LMT
83.42 RM/4/URT_RCH_MAX_IPPRFX
Issue 07 (2014-07-30)

878

Log Reference
83 RM
83.1 RM/3/ADDHOSTRT_TBL_LMT
Message
RM/3/ADDHOSTRT_TBL_LMT:The number of routes in URT reached the maximum when a
direct route was added to URT. (DestinationAddress=[STRING])
Description
The number of routes in the routing table reached the upper limit when a direct route was added
to the routing table.
Parameters
Parameter Name
Parameter Meaning
DestinationAddress
Indicates the destination address.
Possible Causes
Excessive routes were added.
Procedure
Step 1 Purchase a new license.
----End
83.2 RM/6/CONFIRM_N
Message
RM/6/CONFIRM_N:The operation of [STRING]: A user input \"No\" to cancel the operation.
Description
When a specific operation needed to be confirmed, a user entered N.
Issue 07 (2014-07-30)

879

Log Reference
83 RM
Parameters
[STRING]
Indicates the specific operation that needs to be confirmed by a user. The

types of operations include the following:
l erase all multicast static routes: Delete all multicast static routes.
l erase all public IPv4 static routes and their configurations: Delete all
public IPv4 static routes and the configurations of the routes.
l erase all IPv4 static routes in this instance and their configurations:
Delete all IPv4 static routes that belong to the instance and delete the
configurations of the routes.
l erase all IPv4 static routes track bfd session: Delete all IPv4 static
routes tracing BFD session status and delete the configurations of the
routes.
l erase information about specific routing counters: Delete information
about the specified routing counter.
Possible Causes
When static routes and related configurations or specified route statistics were deleted on the
RM, a user input N to cancel the operation.
Procedure
----End
83.3 RM/6/CONFIRM_TIMEOUT
Message
RM/6/CONFIRM_TIMEOUT:The operation of [STRING]: A user did not input any word in
[ULONG]s, and the system automatically exited from the operation.
Description
The system automatically quitted the operation if a user input nothing within the specified
maximum number of seconds to confirm the operation.
Issue 07 (2014-07-30)

880

Log Reference
83 RM
Parameters
[STRING]

l erase all multicast static routes:Delete all multicast static routes.
routes.
[ULONG]
indicates the maximum number of seconds taken by a user to confirm the

operation.
Possible Causes
When the RM module deleted static routes and related configurations or deleted specified route
statistics, a user did not input Y to proceed with or N to cancel the operation within the permitted
period of time specified by [ULONG]. Therefore, the system quitted the confirmation and did
not proceed with the operation by default.
Procedure
----End
83.4 RM/6/CONFIRM_Y
Message
RM/6/CONFIRM_Y:The operation of [STRING]: A user input \"Yes\" to confirm the operation.
Description
When a specific operation needed to be confirmed, a user entered Y.
Issue 07 (2014-07-30)

881

Log Reference
83 RM
Parameters
[STRING]

l erase all multicast static routes: Delete all multicast static routes.
routes.
Possible Causes
When static routes and related configurations or specified route statistics were deleted on the
RM, a user input Y to proceed with the operation.
Procedure
----End
83.5 RM/6/ENABLE_1MFIB
Message
RM/6/ENABLE_1MFIB:Million FIB feature was enabled.
Description
The million FIB feature was enabled.
Issue 07 (2014-07-30)

882

Log Reference
83 RM
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The million FIB feature was enabled.
Procedure
----End
83.6 RM/3/GET_VRF_TBLID_FAL
Message
RM/3/GET_VRF_TBLID_FAL:Failed to obtain the table ID of the VPN instance [instance-id].
Description
Failed to obtain the routing table ID of the VPN instance.
Parameters
Parameter Name
Parameter Meaning
[instance-id]
Indicates the ID of an instance.
Possible Causes
Failed to obtain the routing table ID of the VPN instance.
Procedure
----End
83.7 RM/6/HANDLE_ADD_IPMSG
Message
RM/6/HANDLE_ADD_IPMSG:RM IM received the event of adding an IP address.
(IpAddress=[string], Mask=[string], Interface=[string])
Issue 07 (2014-07-30)

883

Log Reference
83 RM
Description
RM received the event of adding an IP address.
Parameters
Parameter Name
Parameter Meaning
IpAddress
Indicates an IP address in dotted decimal notation.
Mask
Indicates a mask in dotted decimal notation.
Interface
Indicates the type and the name of an interface.
Possible Causes
The IP module reported the event of adding an IP address.
Procedure
----End
83.8 RM/6/HANDLE_ADDED_IPMSG
Message
RM/6/HANDLE_ADDED_IPMSG:RM IM processed the event of adding an IP address
successfully. (IpAddress=[string], Mask=[string], Interface=[string])
Description
RM responded to the event of adding an IP address successfully.
Parameters
Parameter Name
Parameter Meaning
IpAddress
Mask
Interface
Possible Causes
The IP module reported the event of adding an IP address, and RM processed the event
successfully.
Issue 07 (2014-07-30)

884

Log Reference
83 RM
Procedure
----End
83.9 RM/6/HANDLE_DEL_IPMSG
Message
RM/6/HANDLE_DEL_IPMSG:RM IM received the event of deleting an IP address.
(IpAddress=[string], Mask=[string], Interface=[string])
Description
RM received the event of deleting an IP address.
Parameters
Parameter Name
Parameter Meaning
IpAddress
Mask
Interface
Possible Causes
The IP module reported the event of deleting an IP address.
Procedure
----End
83.10 RM/6/HANDLE_DELED_IPMSG
Message
RM/6/HANDLE_DELED_IPMSG:RM IM processed the event of deleting an IP address
successfully. (IpAddress=[string], Mask=[string], Interface=[string])
Description
RM responded to the event of deleting an IP address successfully.
Issue 07 (2014-07-30)

885

Log Reference
83 RM
Parameters
Parameter Name
Parameter Meaning
IpAddress
Mask
Interface
Possible Causes
The IP module reported the event of deleting an IP address, and RM processed the event
successfully.
Procedure
----End
83.11 RM/4/INST_RCH_MAX_RT_LMT
Message
RM/4/INST_RCH_MAX_RT_LMT:The number of routes in [vpn-instance-name] was
[current-number], which reached or exceeded the maximum value [max-value]. (InstanceId=
[ULONG], AcceptOrRejectFlag=[STRING])
Description
The number of routes in a specific VPN instance reached or exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning

[current-number]
Indicates the current number of routes.
[max-value]
InstanceId
Indicates the ID of a VPN instance.
AcceptOrRejectFlag Indicates the flag representing whether it is allowed or rejected to add

routes. The values are as follows:
l Accept: indicates that adding routes is allowed.
l Reject: indicates that adding routes is rejected.
Issue 07 (2014-07-30)

886

Log Reference
83 RM
Possible Causes
The number of routes in a specific VPN instance reached or exceeded the upper limit.
Procedure
Step 1 Run the display ip routing-table [ vpn-instance vpn-instance-name ] statistics command to
instance meets the requirement.
l If not, run the routing-table limit number { alert-percent | simply-alert } command to
reconfigure a proper alarm threshold. Then, go to Step 6.
Step 6 End.
----End
83.12 RM/4/INST_RCH_MAX_RT6_LMT
Message
RM/4/INST_RCH_MAX_RT6_LMT:The number of routes in IPv6 [vpn-instance-name] was
[current-number], which reached or exceeded the maximum value [max-value]. (InstanceId=
[ULONG], AcceptOrRejectFlag=[STRING])
Description
The number of routes in a specific IPv6 VPN instance reached or exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name] Indicates the name of an IPv6 VPN instance.

Issue 07 (2014-07-30)

887

Log Reference
Parameter Name
Parameter Meaning
[max-value]
[current-number]
Indicates the current number of routes.
InstanceId
Indicates the ID of an IPv6 VPN instance.
83 RM
AcceptOrRejectFlag Indicates the flag representing whether it is allowed or rejected to add

routes. The values are as follows:
l Accept: indicates that adding routes is allowed.
l Reject: indicates that adding routes is rejected.
Possible Causes
The number of routes in a specific IPv6 VPN instance reached or exceeded the upper limit.
Procedure
Step 1 Run the display ipv6 routing-table [ vpn-instance vpn-instance-name ] statistics command to
check the total number and types of routes in this IPv6 VPN instance.
Step 2 Analyze the source of each route and check whether the number of current routes in the IPv6
Step 4 Enter the IPv6 VPN instance view and run the display this command to check the configuration
of routing-table limit to check whether the set alarm threshold of private routes is proper.
Step 6 End.
----End
83.13 RM/4/INST_RCH_MAXPFXLMT
Message
RM/4/INST_RCH_MAXPFXLMT:The number of prefixes in [vpn-instance-name] was
[current-number], which reached the maximum value [maximum-value]. (InstanceId=
[ULONG], AddFlag=[STRING])
Issue 07 (2014-07-30)

888

Log Reference
83 RM
Description
This log message is displayed when the number of route prefixes exceeds the permitted
maximum value and a new route is to be added. The interval for displaying this log message can
be set through a command.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
[current-number]
Indicates the number of current route prefixes.
[maximum-value]
Indicates the permitted maximum number of route prefixes.
InstanceId
AddFlag
Indicates whether the route can be added:

l Accept: The route can be added.
l Deny: The route cannot be added.
Possible Causes
Procedure
Step 1 Check whether the permitted maximum number of route prefixes needs to be increased.
----End
83.14 RM/4/INST_RCH_MAXPFXLMT6
Message
RM/4/INST_RCH_MAXPFXLMT6:The number of prefixes in IPv6 [vpn-instance-name] was
[current-number], which reached the maximum value [maximum-value]. (InstanceId=
[ULONG], AddFlag=[STRING])
Description
This log message is displayed when the number of IPv6 route prefixes exceeds the permitted
Issue 07 (2014-07-30)

889

Log Reference
83 RM
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
Indicates the name of a IPv6 VPN instance.
[current-number]
[maximum-value]
InstanceId
AddFlag
Indicates whether the route can be added:

l Accept: The route can be added.
l Deny: The route cannot be added.
Possible Causes
Procedure
Step 1 Check whether the permitted maximum number of route prefixes needs to be increased.
----End
Message
RM/4/IPV4_DEFT_RT_CHG:IPV4 default Route is changed. (ChangeType=[STRING],
InstanceId=[USHORT], Protocol=[STRING], ExitIf=[STRING], Nexthop=[STRING],
Neighbour=[STRING], Preference=[ULONG], Label=[STRING], Metric=[ULONG])
Description
The default IPv4 route changed.
Parameters
Parameter Name
Parameter Meaning
ChangeType
Indicates the type of route change:

l Delete: A route is deleted.
l Modify: A route is modified.
InstanceId
Issue 07 (2014-07-30)

890

Log Reference
83 RM
Parameter Name
Parameter Meaning
Protocol
Indicates the protocol.
ExitIf
Indicates the outgoing interface.
Nexthop
Indicates the next hop.
Neighbour
Indicates the neighbor.
Preference
Indicates the route preference.
Label
Indicates the route label.
Metric
Indicates the route metric.
Possible Causes
1. A default route is deleted.
2. The attributes, which can be delivered to the RM, of a default route, is modified.
Procedure
----End
Message
RM/4/IPV6_DEFT_RT_CHG:IPV6 default Route is changed. (ChangeType=[STRING],
InstanceId=[USHORT], Protocol=[STRING], ExitIf=[STRING], Nexthop=[STRING],
Neighbour=[STRING], Preference=[ULONG], Label=[STRING], Metric=[ULONG])
Description
The default IPv6 route changed.
Issue 07 (2014-07-30)

891

Log Reference
83 RM
Parameters
Parameter Name
Parameter Meaning
ChangeType
Indicates the type of route change:

l Add: A route is added.
l Delete: A route is deleted.
l Modify: A route is modified.
InstanceId
Protocol
Indicates the protocol.
ExitIf
Indicates the outgoing interface.
Nexthop
Indicates the next hop.
Neighbour
Indicates the neighbor.
Preference
Indicates the route preference.
Label
Indicates the route label.
Metric
Indicates the route metric.
Possible Causes
1. A default route is added or deleted.
2. The attributes, which can be delivered to the RM, of a default route, is modified.
Procedure
----End
83.17 RM/3/IPV6_RCH_MAX_PFX
Message
RM/3/IPV6_RCH_MAX_PFX:The number of IPv6 prefixes reached the maximum prefix limit
[max-prefix-limit].
Description
The number of IPv6 prefixes in the routing table reached the maximum value.
Issue 07 (2014-07-30)

892

Log Reference
83 RM
Parameters
Parameter Name
Parameter Meaning
[max-prefix-limit]
Indicates the maximum number of IPv6 prefixes.
Possible Causes
The number of IPv6 prefixes reached the upper limit when a route was added.
Procedure
Step 1 Confirm the network requirements, and check whether the configuration is correct.
Step 2 Purchase a new license file if the configuration is correct and a lot of routes are required.
----End
83.18 RM/3/LDP_SESSION_STATE
Message
RM/3/LDP_SESSION_STATE:RM received the status [ldp-session] of the LDP session on the
[interface-name].
Description
RM received the status of the LDP session on an interface.
Parameters
Parameter Name
Parameter Meaning
[ldp-session]
Indicates an LDP session.
[interface-name]
Indicates the name of an interface
Possible Causes
RM received the status of the LDP session on an interface.
Procedure
----End
83.19 RM/3/LMTNUM_BGER_MAXPAF
Issue 07 (2014-07-30)

893

Log Reference
83 RM
Message
RM/3/LMTNUM_BGER_MAXPAF:RM rejected the setting of routing table limit for instance
(ID) [instance-id] because the limit number [limit-route-number] was greater than the maximum
route limit defined in PAF [paf-route-limit].
Description
Failed to set the maximum number of routes for the instance because the number of routes
exceeded the maximum value defined in the PAF file.
Parameters
Parameter Name
Parameter Meaning
[instance-id]
Indicates the ID of an instance.
[limit-route-number]
[paf-route-limit]
Indicates the maximum number of routes defined in the PAF file.
Possible Causes
The number of VPN routes exceeded the maximum value defined in the PAF file.
Procedure
----End
83.20 RM/3/MAX_RPM_RCH
Message
RM/3/MAX_RPM_RCH:The number of elements of the routing policy reached the maximum
when an AS-PATH list filter was created.
Description
When the AS_Path filter was created, the number of elements of the routing policy exceeded
the maximum value.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

894

Log Reference
83 RM
Possible Causes
The number of elements of the routing policy exceeded the maximum value.
Procedure
Step 1 Delete useless AS_Path filters.
----End
83.21 RM/3/NEW_PFX_NO_FREE_IDX
Message
RM/3/NEW_PFX_NO_FREE_IDX:No idle index was available for the new IP prefix node
when a prefix list filter was created for the specified prefix list name and instance.
Description
No idle index was available for a new IP prefix node when a prefix list was created for the given
prefix list name and the instance.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1. The largest sequence number was greater than 65535.
2. The sequence number of the prefix list was smaller than 65535.
3. The sequence number of the temporary node was 0.
Procedure
Step 1 Check the number of configured IP prefix lists.
Step 2 Check the configurations of IP prefix lists.
----End
83.22 RM/3/NO_FREE_IDX_FOR_PFX
Message
RM/3/NO_FREE_IDX_FOR_PFX:No idle index was available for the new IPv6-prefix node
when a prefix list filter was created.
Issue 07 (2014-07-30)

895

Log Reference
83 RM
Description
When the prefix list was created, no idle index value can be used to create a new IPv6 prefix
node.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
When the prefix list was created, no idle index value could be used.
Procedure
Step 1 Delete useless prefix list indexes.
----End
83.23 RM/3/NOTIFY_ISIS_MSG
Message
RM/3/NOTIFY_ISIS_MSG:RM notified ISIS of the status [ldp-session] of the LDP session on
the [interface-name].
Description
RM notified IS-IS of the status of the LDP session on an interface.
Parameters
Parameter Name
Parameter Meaning
[ldp-session]
[interface-name]
Possible Causes
RM notified IS-IS of the status of the LDP session on an interface.
Procedure
Step 1 Record the tunnel ID and the number of slots defined in the PAF file, that is, the value of
PAF_LCS_SYSTEM_TOTAL_SLOT_NUM.
----End
Issue 07 (2014-07-30)

896

Log Reference
83 RM
83.24 RM/3/NOTIFY_OSPF_MSG
Message
RM/3/NOTIFY_OSPF_MSG:RM notified OSPF of the status [ldp-session] of the LDP session
on the [interface-name].
Description
RM notified OSPF of the status of the LDP session on an interface.
Parameters
Parameter Name
Parameter Meaning
[ldp-session]
[interface-name]
Possible Causes
RM notified OSPF of the status of the LDP session on an interface.
Procedure
----End
83.25 RM/4/PFX_MAX_NUM_CLEARED
Message
RM/4/PFX_MAX_NUM_CLEARED:The number of [table_name] prefixes in public instance
reduced to [current_prefix_number], which was below the maximum value
[maximum_prefix_number].
Description
The number of route prefixes fell below that supported by the system.
Parameters
Parameter Name
Parameter Meaning
[table_name]
Indicates an IPv4 or IPv6 routing table.
Issue 07 (2014-07-30)

897

Log Reference
83 RM
Parameter Name
Parameter Meaning
[current_prefix_number]
Indicates the number of route prefixes in the routing table.
[maximum_prefix_number] Indicates the maximum number of route prefixes supported by

the system.
Possible Causes
Cause 1:
The network administrator deleted some routes from the routing table or the number of routes
learned by dynamic protocols decreased due to network topology changes.
Cause 2:
The maximum number of route prefixes supported by the system was increased or the limit on
the number of route prefixes was deleted.
Procedure
Step 1 This alarm message is informational only, and no action is required.
----End
83.26 RM/4/PFX_MID_NUM_CLEARED
Message
RM/4/PFX_MID_NUM_CLEARED:The number of [table_name] prefixes in public instance
reduced to [current_prefix_number], which was below the threshold value [threshold_number].
Description
The number of route prefixes fell below that supported by the system.
Parameters
Parameter Name
Parameter Meaning
[table_name]
Indicates an IPv4 or IPv6 routing table.
[current_prefix_number] Indicates the number of route prefixes in the routing table.

[threshold_number]
Indicates the maximum number of route prefixes supported by the

system.
Possible Causes
Cause 1:
The network administrator deleted some routes from the routing table or the number of routes
learned by dynamic protocols decreased due to network topology changes.
Issue 07 (2014-07-30)

898

Log Reference
83 RM
Cause 2:
The threshold of route prefixes supported by the system was increased or the limit on the number
of route prefixes was deleted.
Procedure
Step 1 This alarm message is informational only, and no action is required.
----End
83.27 RM/4/PFXNUM_EXCD_WARN
Message
RM/4/PFXNUM_EXCD_WARN:The number of prefixes in [vpn-instance-name] was [currentnumber], which exceeded the alarm threshold [threshold]. (InstanceId=[ULONG],
MaxPrefixLimit=[ULONG])
Description
This log message is displayed when the number of route prefixes exceeds the alarm threshold
but does not exceed the permitted maximum value and a new route is to be added. The interval
for displaying this log message can be set through a command.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
[current-number]
[threshold]
Indicates the alarm threshold for the number of route prefixes.
InstanceId
MaxPrefixLimit
Possible Causes
This log message is displayed when the number of route prefixes exceeds the alarm threshold
but does not exceed the permitted maximum value and a new route is to be added. The interval
for displaying this log message can be set through a command.
Procedure
Step 1 Check whether the permitted maximum number of route prefixes or alarm threshold needs to be
increased.
----End
Issue 07 (2014-07-30)

899

Log Reference
83 RM
83.28 RM/4/PFXNUM_EXCD_WARN6
Message
RM/4/PFXNUM_EXCD_WARN6:The number of prefixes in IPv6 [vpn-instance-name] was
[current-number], which exceeded the alarm threshold [threshold-value]. (InstanceId=
[ULONG], MaxPrefixLimit=[ULONG])
Description
The number of prefixes for the specified IPv6 private network instance exceeded the trap
threshold.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
Indicates the name of an IPv6 VPN instance.
[current-number]
Indicates the current number of prefixes.
[threshold-value]
Indicates the value of the alarm threshold.
InstanceId
MaxPrefixLimit
Indicates the maximum number of prefixes.
Possible Causes
The number of prefixes for the specified IPv6 private network instance exceeded the trap
threshold.
Procedure
check the total number of prefixes in this IPv6 VPN instance.
Step 2 Analyze the source of each prefix and check whether the number of current prefixes in the IPv6
Step 3 Delete unnecessary private routes, and then check whether the number of prefixes still reaches
of prefix limit to check whether the set alarm threshold of private prefixes is proper.
Issue 07 (2014-07-30)

900

Log Reference
83 RM
l If not, run the prefix limit number { alert-percent | simply-alert } command to reconfigure
Step 6 End.
----End
83.29 RM/3/PTCL_ADD_RT_MEM_SHT
Message
RM/3/PTCL_ADD_RT_MEM_SHT:The system memory was insufficient when a specified
route was added to the routing table according to the protocol ID [protocol-id].
Description
When a route was added to the routing table according to the protocol ID, the system memory
was not enough.
Parameters
Parameter Name
Parameter Meaning
[protocol-id]
Indicates the ID of a protocol.
Possible Causes
When a route was added to the routing table according to the protocol ID, the system memory
was not enough.
Procedure
Step 1 Run the display diagnostic-information command, save the output of the command, and
----End
83.30 RM/4/RCH_ALLVRF_RT_LMT
Message
RM/4/RCH_ALLVRF_RT_LMT:The number of VPN-Instances routes reached the upper limit
[paf-vpn-route-limit] in the system when the upper limit of routes in the routing table in all
instances was checked.
Issue 07 (2014-07-30)

901

Log Reference
83 RM
Description
The number of VPN routes reached the upper limit in the entire system when the maximum
number of routes was checked.
Parameters
Parameter Name
Parameter Meaning
[paf-vpn-route-limit] Indicates the maximum number of VPN routes defined in the PAF file.
Possible Causes
The number of VPN routes reached the upper limit in the entire system when the maximum
number of routes in the routing table was checked.
Procedure
Step 1 Check the total number of VPN routes.
----End
83.31 RM/4/RCH_ALLVRF6_RT_LMT
Message
RM/4/RCH_ALLVRF6_RT_LMT:The number of VPN6-Instances routes reached the upper
limit [paf-vpn-route-limit] in the system when the upper limit of routes in the IPv6 routing table
in all instances was checked.
Description
The number of IPv6 VPN routes reached the upper limit in the entire system when the maximum
number of routes in the IPv6 routing table was checked.
Parameters
Parameter Name
Parameter Meaning
[paf-vpn-route-limit] Indicates the maximum number of VPN routes defined in the PAF file.
Possible Causes
The number of IPv6 VPN routes reached the upper limit in the entire system when the maximum
number of routes in the IPv6 routing table was checked.
Issue 07 (2014-07-30)

902

Log Reference
83 RM
Procedure
Step 1 Check the total number of IPv6 VPN routes.
----End
83.32 RM/4/RCH_MIGP_RT_LMT
Message
RM/4/RCH_MIGP_RT_LMT:The number of routes in MIGP routing table reached the upper
limit [migp-route-limit].
Description
The number of routes in the MIGP routing table reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
[migp-route-limit]
Indicates the maximum number of routes in the MIGP routing table.
Possible Causes
The number of routes in the MIGP routing table reached the upper limit.
Procedure
----End
83.33 RM/4/RCH_PUB_RT_LMT
Message
RM/4/RCH_PUB_RT_LMT:The number of IPv4 routes for the public network reaches the
upper limit [paf-pub-limit], when the number of IPv4 routes in the routing table is checked.
Description
The number of IPv4 public network routes reached the upper limit when the number of IPv4
routes in the routing table was checked.
Issue 07 (2014-07-30)

903

Log Reference
83 RM
Parameters
[paf-pub-limit]
Maximum number of IPv4 public network routes defined in the PAF
Possible Causes
The number of IPv4 public network routes reached the upper limit.
Procedure
Step 1 Check whether routes are correct.
Step 2 Delete invalid routes.
Step 3 Check whether the configuration meets networking requirements. Purchase a new license file if
the configuration is correct and a lot of routes are required.
----End
83.34 RM/4/RCH_PUB6_RT_LMT
Message
RM/4/RCH_PUB6_RT_LMT:The number of IPv6 routes for the public network reaches the
upper limit [paf-pub-limit], when the number of IPv6 routes in the routing table is checked.
Description
The number of IPv6 public network routes reached the upper limit when the number of IPv6
routes in the routing table was checked.
Parameters
[paf-pub-limit]
Maximum number of IPv6 public network routes defined in the PAF
Possible Causes
The number of IPv6 public network routes reached the upper limit.
Procedure
Step 1 Check whether routes are correct.
Step 2 Delete invalid routes.
Issue 07 (2014-07-30)

904

Log Reference
83 RM
Step 3 Check whether the configuration meets networking requirements. Purchase a new license file if
the configuration is correct and a lot of routes are required.
----End
83.35 RM/3/RPM_ROUT_MAX_LMT
Message
RM/3/RPM_ROUT_MAX_LMT:The number of policies in the route policy management
reached maximum limit when a prefix list filter was created for the specified prefix list name
and instance.
Description
The number of elements in the routing policy management reached the upper limit when a prefix
list was created for the given prefix list name and the instance.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The number of elements in the routing policy management reached the upper limit.
Procedure
----End
83.36 RM/4/RT_NUM_EXCD_WARN
Message
RM/4/RT_NUM_EXCD_WARN:The number of routes in [vpn-instance-name] was [currentnumber], which exceeded the alarm threshold [threshold-value]. (InstanceId=[ULONG],
MaximumRouteLimit=[ULONG])
Description
The number of routes in a specific VPN instance reached or exceeded the alarm threshold of
this VPN instance.
Issue 07 (2014-07-30)

905

Log Reference
83 RM
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
[threshold-value]
Indicates the value of the alarm threshold.
InstanceId
Indicates the ID of a VPN instance.
MaximumRouteLimit
[current-number]
Indicates the actual number of routes.
Possible Causes
The number of routes in a specific VPN instance reached or exceeded the alarm threshold of
this VPN instance.
Procedure
Step 1 Run the display ip routing-table [ vpn-instance vpn-instance-name ] statistics command to
instance meets the actual requirement.
Step 6 End.
----End
83.37 RM/4/RT6_NUM_EXCD_WARN
Issue 07 (2014-07-30)

906

Log Reference
83 RM
Message
RM/4/RT6_NUM_EXCD_WARN:The number of routes in IPv6 [vpn-instance-name] was
[current-number], which exceeded the alarm threshold [threshold-value]. (InstanceId=
[ULONG], MaximumRouteLimit=[ULONG])
Description
The number of routes for the specified IPv6 private network instance exceeded the upper limit
of the trap threshold.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance-name]
Indicates the name of an IPv6 VPN instance.
[threshold-value]
Indicates the value of the trap threshold.
InstanceId
MaximumRouteLimit
[current-number]
Indicates the actual number of routes.
Possible Causes
The number of routes for the specified IPv6 private network instance exceeded the upper limit
of the trap threshold.
Procedure
check the total number and types of routes in this IPv6 VPN instance.
Step 2 Analyze the source of each route and check whether the number of current routes in the IPv6
of routing-table limit to check whether the set alarm threshold of private routes is proper.
Issue 07 (2014-07-30)

907

Log Reference
83 RM

Step 6 End.
----End
83.38 RM/3/SMTH_ADDRT_MAX_LMT
Message
RM/3/SMTH_ADDRT_MAX_LMT:The number of routes in the routing table reached the
maximum when a route was added to the URT smoothly. (DestinationAddress=[STRING])
Description
The number of routes in the routing table reached the upper limit when a route was added to the
routing table in smooth backup mode.
Parameters
Parameter Name
Parameter Meaning
DestinationAddress
Indicates the destination address.
Possible Causes
The routing table was full when a route was added during smooth backup.
Procedure
----End
83.39 RM/3/SNDMSG_MEM_SHORT_FAL
Message
RM/3/SNDMSG_MEM_SHORT_FAL:The system memory was insufficient when the IP
message was written to the message queue.
Description
The system memory was not enough when the IP message was written to the message queue.
Issue 07 (2014-07-30)

908

Log Reference
83 RM
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1. The memory was not enough.
2. Excessive IP messages existed.
Procedure
----End
83.40 RM/4/SYS_RCH_MAX_RT_LMT
Message
RM/4/SYS_RCH_MAX_RT_LMT:The number of routes reached upper limit [paf-route-limit]
in the whole system when the route limit in the routing table was checked.
Description
The number of routes exceeded the upper limit in the entire system when the maximum number
of routes in the routing table was checked.
Parameters
Parameter Name
Parameter Meaning
[paf-route-limit]
Indicates the maximum number of routes defined in the PAF file.
Possible Causes
The number of routes exceeded the upper limit in the entire system when the maximum number
of routes in the routing table was checked.
Procedure
----End
Issue 07 (2014-07-30)

909

Log Reference
83 RM
83.41 RM/4/SYS_RCH_MAX6_RT_LMT
Message
RM/4/SYS_RCH_MAX6_RT_LMT:The number of IPv6 routes reached the upper limit [pafipv6-route-limit] in the system when the upper limit of routes in the IPv6 URT was checked.
Description
The number of IPv6 routes reached the upper limit in the entire system when the maximum
number of routes in the IPv6 URT was checked.
Parameters
Parameter Name
Parameter Meaning
[paf-ipv6-route-limit] Indicates the maximum number of IPv6 routes defined in the PAF file.
Possible Causes
The number of IPv6 routes exceeded the upper limit in the entire system when the maximum
number of IPv6 routes in the routing table was checked.
Procedure
Step 1 Check the maximum number of IPv6 routes.
----End
83.42 RM/4/URT_RCH_MAX_IPPRFX
Message
RM/4/URT_RCH_MAX_IPPRFX:The number of prefixes reached the maximum prefix limit
[max-prefix-limit] in the routing table. (RoutingTableId=[ULONG])
Description
The number of prefixes in the routing table reached the maximum value.
Parameters
Parameter Name
Parameter Meaning
[max-prefix-limit]
Indicates the maximum number of IP prefixes.
RoutingTableId
Indicates the ID of a routing table.
Issue 07 (2014-07-30)

910

Log Reference
83 RM
Possible Causes
The number of prefixes reached the upper limit when a route was added.
Procedure
----End
Issue 07 (2014-07-30)

911

Log Reference
84 RRPP
84
RRPP
About This Chapter

84.1 RRPP/3/FAIL
84.2 RRPP/4/INSERT
84.3 RRPP/5/PBLK
84.4 RRPP/5/PFWD
84.5 RRPP/5/RESTORE
84.6 RRPP/3/RRPPACLFULL
84.7 RRPP/4/SPECCHANGE
84.8 RRPP/4/SPECCHECKFAIL
84.9 RRPP/5/TOPOCHANGE
Issue 07 (2014-07-30)

912

Log Reference
84 RRPP
84.1 RRPP/3/FAIL
Message
RRPP/3/FAIL:Domain [domain-id] ring [ring-id] failed.
Description
The RRPP ring failed.
Parameters
Parameter Name
Parameter Meaning
[domain-id]
indicates the ID of an RRPP domain.
[ring-id]
indicates the ID of an RRPP ring.
Possible Causes
The RRPP ring failed.
Procedure
Step 1 Run the display rrpp brief command to check that the status of all RRPP nodes is normal so
as to check whether the node failed or the master node did not receive the Hello packet.
----End
84.2 RRPP/4/INSERT
Message
RRPP/4/INSERT:Another type of board inserted, reconfigure RRPP please.
Description
The inserted interface board was a different type. So, you need to reconfigure RRRP.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

913

Log Reference
84 RRPP
Possible Causes
An interface board or card of a different type is inserted into the slot of the interface enabled
with RRPP.
Procedure
Step 1 Reconfigure RRPP.
----End
84.3 RRPP/5/PBLK
Message
RRPP/5/PBLK:Domain [domain-id] ring [ring-id] port [port-name] has been set to block state.
Description
The port along the RRPP ring was blocked.
Parameters
Parameter Name
Parameter Meaning
[domain-id]
[ring-id]
[port-name]
indicates the name of the port along the RRPP ring.
Possible Causes
The port changed to the block state.
Procedure
----End
84.4 RRPP/5/PFWD
Message
RRPP/5/PFWD:Domain [domain-id] ring [ring-id] port [port-name] has been set to forwarding
state.
Issue 07 (2014-07-30)

914

Log Reference
84 RRPP
Description
The port along the RRPP ring changed to the forwarding state.
Parameters
Parameter Name
Parameter Meaning
[domain-id]
[ring-id]
[port-name]
indicates the name of the port along the RRPP ring.
Possible Causes
The port changed to the forwarding state.
Procedure
----End
84.5 RRPP/5/RESTORE
Message
RRPP/5/RESTORE:Domain [domain-id] ring [ring-id] restored.
Description
The RRPP ring restored.
Parameters
Parameter Name
Parameter Meaning
[domain-id]
[ring-id]
Possible Causes
The RRPP ring returned to the normal state.
Procedure
Step 1 Run the display rrpp brief command to check whether the status of all RRPP nodes is normal.
l If the status of all RRPP nodes is normal, no action is required.
Issue 07 (2014-07-30)

915

Log Reference
84 RRPP
l If the status of all RRPP nodes is abnormal, contact the Huawei technical support personnel.
----End
84.6 RRPP/3/RRPPACLFULL
Message
RRPP/3/RRPPACLFULL:Failed to configure the ring in domain because the hardware
resources are insufficient. (DomainID=[ULONG], RingID=[ULONG])
Description
Failed to configure the ring in domain because the hardware resources are insufficient.
Parameters
Parameter Name
Parameter Meaning
DomainID
RingID
Possible Causes
The hardware resources are insufficient.
Procedure
Step 1 Delete the RRPP ring that fails to be configured.
----End
84.7 RRPP/4/SPECCHANGE
Message
RRPP/4/SPECCHANGE:The RRPP specifications were changed in the new version. (Spec=
[STRING], Value=[ULONG])
Description
The RRPP specifications changed when ISSU was implemented on RRPP modules.
Issue 07 (2014-07-30)

916

Log Reference
84 RRPP
Parameters
Spec
Indicates the items of RRPP specifications. The items are as follows:

l RRPP_MAX_RING_NUM
l RRPP_MAX_DOMAIN_NUM
l RRPP_MAX_RING_ID
l RRPP_MIN_RING_ID
l RRPP_MAX_DOMAIN_ID
l RRPP_MIN_DOMAIN_ID
l RRPP_CTRLVLAN_UPPER
l RRPP_CTRLVLAN_LOWER
l RRPP_HELLO_TIMER_UPPER
l RRPP_HELLO_TIMER_LOWER
l RRPP_FAIL_TIMER_UPPER
l RRPP_FAIL_TIMER_LOWER
Value
Indicates the values of RRPP specifications. The values are as follows:

l Maximum number of supported RRPP rings.
l Maximum number of supported RRPP domains.
l Largest ring ID supported.
l Smallest ring ID supported.
l Largest domain ID supported.
l Smallest domain ID supported.
l Largest control VLAN ID supported.
l Smallest control VLAN ID supported.
l Maximum value of the Hello timer supported.
l Minimum value of the Hello timer supported.
l Maximum value of the Fail timer supported.
l Minimum value of the Fail timer supported.
Possible Causes
The RRPP specifications changed when ISSU was implemented on RRPP modules.
Procedure
----End
84.8 RRPP/4/SPECCHECKFAIL
Issue 07 (2014-07-30)

917

Log Reference
84 RRPP
Message
RRPP/4/SPECCHECKFAIL:The ISSU check failed because of the [reason].
Description
The ISSU check on RRPP modules failed.
Parameters
[reason]
Indicates the causes for the ISSU check failure. The causes are as follows:
l Failed to obtain the RRPP specifications.
l The RRPP specifications changed.
l The versions were incompatible.
Possible Causes
1. Failed to obtain the RRPP specifications.
2. The RRPP specifications changed.
3. The versions were incompatible.
Procedure
Step 1 Check the RRPP specifications or system software version according to the specific causes
recorded in the log message.
----End
84.9 RRPP/5/TOPOCHANGE
Message
RRPP/5/TOPOCHANGE:RRPP informs VPLS of topology change.
Description
RRPP informed VPLS of updating MAC entries and ARP entries when the port enabled RRPP
snooping receives RRPP FDB packets.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

918

Log Reference
84 RRPP
Possible Causes
A fault occurred on the RRPP ring network or the RRPP ring network recovered.
Procedure
----End
Issue 07 (2014-07-30)

919

Log Reference
85 RSA
85
RSA
About This Chapter

85.1 RSA/6/DESTROY_KEYS
85.2 RSA/4/FAIL_READ_FLASH
85.3 RSA/4/FAIL_WRITE_FLASH
85.4 RSA/3/HOST_PUBKEY_BAK_FAL
85.5 RSA/4/HOSTKEY_BACKUP_ERR
85.6 RSA/4/HOSTKEY_BAK_DEL_ERR
85.7 RSA/3/HOSTKEY_DEL_ERR
85.8 RSA/6/HOSTKEY_DEL_SUC
85.9 RSA/3/HOSTKEY_GEN_FAIL
85.10 RSA/6/HOSTKEY_GEN_SUCCESS
85.11 RSA/3/HOSTKEY_SAVE_ERR
85.12 RSA/6/KEY_SIZE
85.13 RSA/6/NOT_DESTROY_KEYS
85.14 RSA/6/NOT_REPLACE_KEYS
85.15 RSA/6/REPLACE_KEYS
85.16 RSA/4/SERVERKEY_BKUP_ERR
85.17 RSA/3/SERVERKEY_DEL_ERR
85.18 RSA/6/SERVERKEY_DEL_SUC
85.19 RSA/3/SERVERKEY_GEN_FAIL
85.20 RSA/6/SERVERKEY_GEN_SUC
Issue 07 (2014-07-30)

920

Log Reference
85 RSA
85.21 RSA/3/SERVERKEY_SAVE_ERR
85.22 RSA/3/SERVR_PUBKEY_BAK_FAL
85.23 RSA/4/SEVEKEY_BAK_DEL_ERR
Issue 07 (2014-07-30)

921

Log Reference
85 RSA
85.1 RSA/6/DESTROY_KEYS
Message
RSA/6/DESTROY_KEYS:The user confirms that the keys need to be destroyed.
Description
The user confirms to destroy the key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
After the rsa local-key-pair destroy command was run, the user confirmed to destroy the key.
Procedure
l
----End
85.2 RSA/4/FAIL_READ_FLASH
Message
RSA/4/FAIL_READ_FLASH:Failed to read flash!
Description
Failed to read the key in the flash.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Reading the key in the flash failed.
Issue 07 (2014-07-30)

922

Log Reference
85 RSA
Procedure
l
Re-open the flash file to read the key.
----End
85.3 RSA/4/FAIL_WRITE_FLASH
Message
RSA/4/FAIL_WRITE_FLASH:Failed to write flash!
Description
Failed to write the key to the flash.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Writing the key to the flash failed.
Procedure
l
Regenerate the host key pair or server key pair.
----End
85.4 RSA/3/HOST_PUBKEY_BAK_FAL
Message
RSA/3/HOST_PUBKEY_BAK_FAL:Failed to backup host public key!
Description
Failed to back up the host public key.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

923

Log Reference
85 RSA
Possible Causes
Backing up the host public key to the storage media failed.
Procedure
l
Run the rsa local-key-pair create command to create the host key pair.
----End
85.5 RSA/4/HOSTKEY_BACKUP_ERR
Message
RSA/4/HOSTKEY_BACKUP_ERR:Failed to backup RSA host encryption key!
Description
Failed to back up the RSA host encryption key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1. The data to be backed up was null.
2. Memory allocation for the data to be backed up failed.
3. Sending the Backup message failed.
Procedure
l
Though the backup of the RSA host encryption key failed, the system will back up the key
in batches; therefore, no action is required.
----End
85.6 RSA/4/HOSTKEY_BAK_DEL_ERR
Message
RSA/4/HOSTKEY_BAK_DEL_ERR:Succeeded in destroying RSA host key in the main board,
but failed to destroy RSA host key in the slave board!
Issue 07 (2014-07-30)

924

Log Reference
85 RSA
Description
Succeeded in destroying the RSA host key in the main board, but failed to destroy the RSA host
key in the slave board.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Procedure
l
----End
85.7 RSA/3/HOSTKEY_DEL_ERR
Message
RSA/3/HOSTKEY_DEL_ERR:Failed to destroy RSA host key!
Description
Succeeded in destroying the RSA host key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Destroying the RSA host key failed.
Procedure
l
Run the rsa local-key-pair destroy command to destroy the host key pair.
----End
Issue 07 (2014-07-30)

925

Log Reference
85 RSA
85.8 RSA/6/HOSTKEY_DEL_SUC
Message
RSA/6/HOSTKEY_DEL_SUC:Destroy RSA host key successfully.
Description
Succeeded in destroying the RSA host key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Destroying the RSA host key succeeded.
Procedure
l
----End
85.9 RSA/3/HOSTKEY_GEN_FAIL
Message
RSA/3/HOSTKEY_GEN_FAIL:Failed to create RSA host encryption key!
Description
Failed to create the RSA host encryption key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1.
The length of the key name was 0 or the length exceeded the maximum value.
2.
The number of key bits was invalid.
Issue 07 (2014-07-30)

926

Log Reference
85 RSA
3.
Generating the key pair failed.
4.
Saving the key to hardware failed.
Procedure
----End
85.10 RSA/6/HOSTKEY_GEN_SUCCESS
Message
RSA/6/HOSTKEY_GEN_SUCCESS:Create RSA host encryption key successfully.
Description
Creating the RSA host encryption key succeeded.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Creating the RSA host encryption key succeeded.
Procedure
l
----End
85.11 RSA/3/HOSTKEY_SAVE_ERR
Message
RSA/3/HOSTKEY_SAVE_ERR:Failed to save RSA host encryption key!
Description
Failed to save the RSA host encryption key.
Issue 07 (2014-07-30)

927

Log Reference
85 RSA
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to write the RSA host encryption key to the storage media.
Procedure
l
----End
85.12 RSA/6/KEY_SIZE
Message
RSA/6/KEY_SIZE:The user inputs the size of key [key-length].
Description
The user inputted the length of the key.
Parameters
Parameter Name
Parameter Meaning
[key-length]
indicates the length of a key.
Possible Causes
After the rsa local-key-pair create command is run, the system prompts the user to input the key
length.
Procedure
l
----End
85.13 RSA/6/NOT_DESTROY_KEYS
Message
RSA/6/NOT_DESTROY_KEYS:The user confirms that the keys cannot be destroyed.
Issue 07 (2014-07-30)

928

Log Reference
85 RSA
Description
The user confirmed that the key need not be destroyed.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
After the rsa local-key-pair destroy command is run, the user confirmed that the key need not
be destroyed.
Procedure
l
----End
85.14 RSA/6/NOT_REPLACE_KEYS
Message
RSA/6/NOT_REPLACE_KEYS:The user confirms that the keys cannot be replaced.
Description
The user confirmed that the key need not be replaced.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
After the rsa local-key-pair create command is run, the system prompts a user to confirm whether
to replace the original key if the host key and server key coexist. This log message is generated
if the user confirms that the key need not be replaced.
Procedure
l
----End
Issue 07 (2014-07-30)

929

Log Reference
85 RSA
85.15 RSA/6/REPLACE_KEYS
Message
RSA/6/REPLACE_KEYS:The user confirms that the keys need to be replaced.
Description
The user confirmed to replace the original key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
After the rsa local-key-pair create command is run, the system prompts a user to confirm whether
to replace the original key if the host key and server key coexist. This log message is generated
if the user confirms to replace the original key.
Procedure
l
----End
85.16 RSA/4/SERVERKEY_BKUP_ERR
Message
RSA/4/SERVERKEY_BKUP_ERR:Failed to backup RSA server encryption key!
Description
Failed to back up the RSA server encryption key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Issue 07 (2014-07-30)

930

Log Reference
85 RSA

Procedure
l
Though the backup of the RSA host encryption key failed, the system will back up the key
in batches; therefore, no action is required.
----End
85.17 RSA/3/SERVERKEY_DEL_ERR
Message
RSA/3/SERVERKEY_DEL_ERR:Failed to destroy RSA server key!
Description
Failed to destroy the RSA server key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Destroying the RSA server key failed.
Procedure
l
Run the rsa local-key-pair destroy command to destroy the server key pair again.
----End
85.18 RSA/6/SERVERKEY_DEL_SUC
Message
RSA/6/SERVERKEY_DEL_SUC:Destroy RSA server key successfully.
Description
Succeeded in destroying the RSA server key.
Issue 07 (2014-07-30)

931

Log Reference
85 RSA
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Destroying the RSA server key succeeded.
Procedure
l
----End
85.19 RSA/3/SERVERKEY_GEN_FAIL
Message
RSA/3/SERVERKEY_GEN_FAIL:Failed to create RSA server encryption key!
Description
Failed to create the RSA server encryption key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1. The length of the key name was 0 or the length exceeded the maximum value.
2. The number of key bits was invalid.
3. Transferring to the storage format failed.
Procedure
l
Run the rsa local-key-pair create command to create the server key pair.
----End
85.20 RSA/6/SERVERKEY_GEN_SUC
Issue 07 (2014-07-30)

932

Log Reference
85 RSA
Message
RSA/6/SERVERKEY_GEN_SUC:Create RSA server encryption key successfully.
Description
Creating the RSA server encryption key succeeded.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Creating the RSA server encryption key succeeded.
Procedure
l
----End
85.21 RSA/3/SERVERKEY_SAVE_ERR
Message
RSA/3/SERVERKEY_SAVE_ERR:Failed to save RSA server encryption key!
Description
Failed to save the RSA server encryption key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to write the RSA server encryption key to the storage media.
Procedure
l
----End
Issue 07 (2014-07-30)

933

Log Reference
85 RSA
85.22 RSA/3/SERVR_PUBKEY_BAK_FAL
Message
RSA/3/SERVR_PUBKEY_BAK_FAL:Failed to backup server public key!
Description
Failed to back up the server public key.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Backing up the server public key to the storage media failed.
Procedure
l
----End
85.23 RSA/4/SEVEKEY_BAK_DEL_ERR
Message
RSA/4/SEVEKEY_BAK_DEL_ERR:Succeeded in destroying RSA server key in the main
board, but failed to destroy RSA server key in the slave board!
Description
Succeeded in destroying the RSA server key in the main board, but failed to destroy the RSA
server key in the slave board.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Issue 07 (2014-07-30)

934

Log Reference
85 RSA

Procedure
l
----End
Issue 07 (2014-07-30)

935

Log Reference
86 RSVP
86
RSVP
About This Chapter

86.1 RSVP/6/DISABLE_MPLS
86.2 RSVP/6/ENABLE_INTF
86.3 RSVP/6/ENABLE_MPLS
86.4 RSVP/6/FUNC_SPEC_AVAIL
86.5 RSVP/6/FUNC_SPEC_UNAVAIL
86.6 RSVP/6/GET_MPLS_MTU_FAIL
86.7 RSVP/7/GLOBAL_OVER_FAIL
86.8 RSVP/6/GR_AGING_TIMER_END
86.9 RSVP/6/GR_AGING_TIMER_START
86.10 RSVP/6/GR_RES_NBR_ENDTONOR
86.11 RSVP/6/GR_RES_NBR_NORTOEND
86.12 RSVP/6/GR_RES_NBR_NORTOSUP
86.13 RSVP/6/GR_RES_NBR_SUPTOEND
86.14 RSVP/6/GR_RES_NBR_SUPTONOR
86.15 RSVP/6/GR_RES_NORTORES
86.16 RSVP/6/GR_RES_RECTONOR
86.17 RSVP/6/GR_RES_RESTONOR
86.18 RSVP/6/GR_RES_RESTOREC
86.19 RSVP/6/GR_SUP_NBR_MRESTONOR
86.20 RSVP/6/GR_SUP_NBR_MRESTORES
Issue 07 (2014-07-30)

936

Log Reference
86 RSVP
86.21 RSVP/6/GR_SUP_NBR_NORTOMRES
86.22 RSVP/6/GR_SUP_NBR_NORTORES
86.23 RSVP/6/GR_SUP_NBR_RESTOMRES
86.24 RSVP/6/GR_SUP_NBR_RESTONOR
86.25 RSVP/6/INC_INTF
86.26 RSVP/6/INTF_SEQ_RCH_MAX
86.27 RSVP/3/LOOP_PATH
86.28 RSVP/3/LOOP_RESV
86.29 RSVP/3/LSP_DOESNOT_EXIST
86.30 RSVP/3/LSP_EXCEED_PAF_LIC
86.31 RSVP/3/LSRID_GET_FAIL
86.32 RSVP/6/MAX_NBR_REACH
86.33 RSVP/6/MAX_SESSION_REACH
86.34 RSVP/3/NBR_NO_GR_PATH
86.35 RSVP/3/NBR_NO_GR_REC_PATH
86.36 RSVP/6/NOTIFY_LSPM_GR_END
86.37 RSVP/6/NOTIFY_LSPM_GR_START
86.38 RSVP/6/PSB_CLEAN_TIMEOUT
86.39 RSVP/3/REACH_LIC_LIMIT
86.40 RSVP/4/REACH_LIST_MAXLEGTH
86.41 RSVP/3/REACH_PSB_MAXNUM
86.42 RSVP/3/RECONSTRUCT_LSP_FAIL
86.43 RSVP/6/RECOVERY_TIMER_END
86.44 RSVP/6/RECOVERY_TIMER_START
86.45 RSVP/6/RESTART_TIMER_END
86.46 RSVP/6/RESTART_TIMER_START
86.47 RSVP/6/RSB_CLEAN_TIMEOUT
86.48 RSVP/7/SD_HA_BACK_OVER_FAIL
Issue 07 (2014-07-30)

937

Log Reference
86 RSVP
86.1 RSVP/6/DISABLE_MPLS
Message
RSVP/6/DISABLE_MPLS:RSVP was disabled successfully in the MPLS view.
Description
Succeeded in disabling RSVP in the MPLS view.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Succeeded in disabling RSVP in the MPLS view.
Procedure
----End
86.2 RSVP/6/ENABLE_INTF
Message
RSVP/6/ENABLE_INTF:RSVP TE was enabled successfully on interface [InterfaceName].
Description
Succeeded in enabling RSVP in the interface view.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
Possible Causes
Succeeded in enabling RSVP in the interface view.
Issue 07 (2014-07-30)

938

Log Reference
86 RSVP
Procedure
----End
86.3 RSVP/6/ENABLE_MPLS
Message
RSVP/6/ENABLE_MPLS:RSVP was enabled successfully in the MPLS view.
Description
Succeeded in enabling RSVP in the MPLS view.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Succeeded in enabling RSVP in the MPLS view.
Procedure
----End
86.4 RSVP/6/FUNC_SPEC_AVAIL
Message
RSVP/6/FUNC_SPEC_AVAIL:RSVP function was enabled.
Description
The RSVP function was enabled.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

939

Log Reference
86 RSVP
Possible Causes
The RSVP function was enabled.
Procedure
Step 1 This log message is informational only. RSVP specifications are controlled using a license file.
----End
86.5 RSVP/6/FUNC_SPEC_UNAVAIL
Message
RSVP/6/FUNC_SPEC_UNAVAIL:RSVP function was disabled.
Description
The RSVP function was disabled.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The RSVP function was disabled.
Procedure
Step 1 This log message is informational only. RSVP specifications are controlled using a license file.
----End
86.6 RSVP/6/GET_MPLS_MTU_FAIL
Message
RSVP/6/GET_MPLS_MTU_FAIL:Cannot obtain MPLS MTU for interface index
[InterfaceIndex].
Description
Failed to obtain the MPLS MTU.
Issue 07 (2014-07-30)

940

Log Reference
86 RSVP
Parameters
Parameter Name
Parameter Meaning
InterfaceIndex
Possible Causes
Failed to obtain the MPLS MTU during the creation of interface entries.
Procedure
----End
86.7 RSVP/7/GLOBAL_OVER_FAIL
Message
RSVP/7/GLOBAL_OVER_FAIL: Failed to send global backup end event to HA.
Description
Failed to send a global backup end event to the HA module.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The system works abnormally.
Procedure
----End
86.8 RSVP/6/GR_AGING_TIMER_END
Message
RSVP/6/GR_AGING_TIMER_END:The GR aging timer expired. (InterfaceName=[STRING],
InterfaceAddress=[STRING], NeighborAddress=[STRING])
Issue 07 (2014-07-30)

941

Log Reference
86 RSVP
Description
The GR Aging timer expired.
Parameters
Parameter Name
Parameter Meaning
InterfaceName
InterfaceAddress
Indicates the interface address.
NeighborAddress
Indicates the neighbor address.
Possible Causes
When the local node helped the neighbor to perform GR, the GR Aging timer expired.
Procedure
----End
86.9 RSVP/6/GR_AGING_TIMER_START
Message
RSVP/6/GR_AGING_TIMER_START:The GR aging timer of neighbor [NeighborAddress]
was started.
Description
The GR Aging timer was started.
Parameters
Parameter Name
Parameter Meaning
NeighborAddress
Possible Causes
When the local node helped the neighbor to perform GR and GR ended, the GR Aging timer
was started.
Procedure
----End
Issue 07 (2014-07-30)

942

Log Reference
86 RSVP
86.10 RSVP/6/GR_RES_NBR_ENDTONOR
Message
RSVP/6/GR_RES_NBR_ENDTONOR:RSVP GR neighbour state changed from end to normal
on the restarting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP restarting node changed from end to normal.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Indicates the address of the restarting neighbor.
Possible Causes
After the local router finished GR, the status of the neighbor changed from end to normal.
Procedure
----End
86.11 RSVP/6/GR_RES_NBR_NORTOEND
Message
RSVP/6/GR_RES_NBR_NORTOEND:RSVP GR neighbour state changed from normal to end
on the restarting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP restarting node changed from normal to end.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Issue 07 (2014-07-30)

943

Log Reference
86 RSVP
Possible Causes
The neighbor no longer helped the local node to perform GR, and the status of the local node
changed to end.
Procedure
----End
86.12 RSVP/6/GR_RES_NBR_NORTOSUP
Message
RSVP/6/GR_RES_NBR_NORTOSUP:RSVP GR neighbour state changed from normal to
supporting on the restarting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP restarting node changed from normal to supporting.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
When the local node performed GR and received the Support message from the neighbor, the
local node changed the neighbor status from normal to supporting.
Procedure
----End
86.13 RSVP/6/GR_RES_NBR_SUPTOEND
Message
RSVP/6/GR_RES_NBR_SUPTOEND:RSVP GR neighbour state changed from supporting to
end on the restarting node. (NeighbourAddress=[IPADDR])
Issue 07 (2014-07-30)

944

Log Reference
86 RSVP
Description
The GR status on the RSVP restarting node changed from supporting to end.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
After the local node finished GR, the status of the neighbor changed from supporting to end.
Procedure
----End
86.14 RSVP/6/GR_RES_NBR_SUPTONOR
Message
RSVP/6/GR_RES_NBR_SUPTONOR:RSVP GR neighbour state changed from supporting to
normal on the restarting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP restarting node changed from supporting to normal.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
When the neighbor helped the local node to perform GR and the local node finished GR, the
local node changed the neighbor status from supporting to normal.
Procedure
----End
Issue 07 (2014-07-30)

945

Log Reference
86 RSVP
86.15 RSVP/6/GR_RES_NORTORES
Message
RSVP/6/GR_RES_NORTORES:RSVP GR state changed from normal to restarting on the
restarting node.
Description
The GR status on the RSVP restarting node changed from normal to restarting.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The active/standby switchover occurred.
Procedure
----End
86.16 RSVP/6/GR_RES_RECTONOR
Message
RSVP/6/GR_RES_RECTONOR:RSVP GR state changed from recovering to normal on the
restarting node.
Description
The GR status on the RSVP restarting node changed from recovering to normal.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
GR normally ended.
Issue 07 (2014-07-30)

946

Log Reference
86 RSVP
Procedure
----End
86.17 RSVP/6/GR_RES_RESTONOR
Message
RSVP/6/GR_RES_RESTONOR:RSVP GR state changed from restarting to normal on the
restarting node.
Description
The GR status on the RSVP restarting node changed from restarting to normal.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
When the local node was performing GR, no neighbor helped the local node to perform GR.
Procedure
----End
86.18 RSVP/6/GR_RES_RESTOREC
Message
RSVP/6/GR_RES_RESTOREC:RSVP GR state changed from restarting to recovering on the
restarting node.
Description
The GR status on the RSVP restarting node changed from restarting to recovering.
Issue 07 (2014-07-30)

947

Log Reference
86 RSVP
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The Restart timer ended during GR.
Procedure
----End
86.19 RSVP/6/GR_SUP_NBR_MRESTONOR
Message
RSVP/6/GR_SUP_NBR_MRESTONOR:RSVP GR neighbour state changed from mayberestarting to normal on the supporting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP supporting node changed from maybe-normal to normal.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
Before the timer expired, the local node did not receive the Hello message sent from the neighbor,
and thus the local node judged that the neighbor was performing GR. After receiving the Hello
message sent from the neighbor, the local node changed the neighbor status.
Procedure
----End
86.20 RSVP/6/GR_SUP_NBR_MRESTORES
Issue 07 (2014-07-30)

948

Log Reference
86 RSVP
Message
RSVP/6/GR_SUP_NBR_MRESTORES:RSVP GR neighbour state changed from mayberestarting to restarting on the supporting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP supporting node changed from maybe-restarting to restarting.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
The local node received the GR message of the neighbor and judged that the neighbor was
performing GR, and then the status of the supporting node changed.
Procedure
----End
86.21 RSVP/6/GR_SUP_NBR_NORTOMRES
Message
RSVP/6/GR_SUP_NBR_NORTOMRES:RSVP GR neighbour state changed from normal to
maybe-restarting on the supporting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP supporting node changed from normal to maybe-restarting.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
When the local node supported GR and Hello detection with the neighbor expired, the local node
judged that the neighbor might be performing GR and set the flag bit.
Issue 07 (2014-07-30)

949

Log Reference
86 RSVP
Procedure
----End
86.22 RSVP/6/GR_SUP_NBR_NORTORES
Message
RSVP/6/GR_SUP_NBR_NORTORES:RSVP GR neighbour state changed from normal to
restarting on the supporting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP supporting node changed from normal to restarting.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
The local node received the Hello message from the neighbor and found the neighbor performing
GR.
Procedure
----End
86.23 RSVP/6/GR_SUP_NBR_RESTOMRES
Message
RSVP/6/GR_SUP_NBR_RESTOMRES:RSVP GR neighbour state changed from restarting to
maybe-restarting on the supporting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP supporting node changed from restarting to maybe-restarting.
Issue 07 (2014-07-30)

950

Log Reference
86 RSVP
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
When the neighbor was performing GR, the Hello message between the local node and the
neighbor expired again.
Procedure
----End
86.24 RSVP/6/GR_SUP_NBR_RESTONOR
Message
RSVP/6/GR_SUP_NBR_RESTONOR:RSVP GR neighbour state changed from restarting to
normal on the supporting node. (NeighbourAddress=[IPADDR])
Description
The GR status on the RSVP supporting node changed from restarting to normal.
Parameters
Parameter Name
Parameter Meaning
NeighbourAddress
Possible Causes
The neighbor finished GR, and the local node changed from restarting to normal.
Procedure
----End
86.25 RSVP/6/INC_INTF
Issue 07 (2014-07-30)

951

Log Reference
86 RSVP
Message
RSVP/6/INC_INTF:Cannot obtain interface from RSVP message. (IncomingInterfaceIndex=
[ULONG], InterfaceName=[STRING])
Description
Failed to read interface information.
Parameters
Parameter Name
Parameter Meaning
IncomingInterfaceIndex
Indicates the incoming interface index.
InterfaceName
Possible Causes
Failed to resolve the RSVP message.
Procedure
----End
86.26 RSVP/6/INTF_SEQ_RCH_MAX
Message
RSVP/6/INTF_SEQ_RCH_MAX:Authentication send: Interface sequence number reached the
greatest value.
Description
The sequence number of the interface reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
When the authentication sequence number of the interface reached the upper limit, the sequence
number was reset, and the sequence flag bit increased by 1.
Issue 07 (2014-07-30)

952

Log Reference
86 RSVP
Procedure
----End
86.27 RSVP/3/LOOP_PATH
Message
RSVP/3/LOOP_PATH:A loop existed in path message (IngressLsrId=[IPADDR], TunnelId=
[USHORT], EgressLsrId=[IPADDR]), the IP address [LoopAddress] conflicted with other
router.
Description
A loop occurred in the Path message.
Parameters
Parameter Name
Parameter Meaning
IngressLsrId
Indicates the LSR ID of the ingress in the Path message.
TunnelId
EgressLsrId
Indicates the LSR ID of the egress in the Path message.
[LoopAddress]
Indicates the address that causes the loop.
Possible Causes
An incorrect configuration caused a loop. For example, a device on a TE tunnel is configured
with an IP address that is the same as the IP address of an interface along the TE tunnel.
Procedure
Step 1 Run the display ip interface brief command on the involved device to check IP addresses of
all interfaces and find the interfaces whose IP addresses are the same as that displayed in the
LoopAddr field.
Step 2 Log in to the ingress based on the LSR ID displayed in the IngressLsrId field. Then run the
display mpls te tunnel path command on the ingress to check nodes along the TE tunnel.
Step 3 Run the display ip interface brief command on each node to check the IP address and find the
IP address the same as that displayed in the LoopAddr field.
Step 4 Change either of two identical IP addresses to be a different one.
----End
Issue 07 (2014-07-30)

953

Log Reference
86 RSVP
86.28 RSVP/3/LOOP_RESV
Message
RSVP/3/LOOP_RESV:There is a loop in resv message (IngressLsrId=[IPADDR], TunnelId=
[USHORT], EgressLsrId=[IPADDR]), the IP address [LoopAddress] conflicted with other
router.
Description
A loop was found during the RSVP loop detection.
Parameters
Parameter Name
Parameter Meaning
IngressLsrId
Indicates the LSR ID of the ingress in the Resv message.
TunnelId
EgressLsrId
Indicates the LSR ID of the egress in the Resv message.
[LoopAddress]
Indicates the address that causes the loop.
Possible Causes
A loop was found during the RSVP loop detection because of incorrect configuration.
Procedure
Step 1 Run the display ip interface brief command on the involved device to check IP addresses of
all interfaces and find the interfaces whose IP addresses are the same as that displayed in the
LoopAddr field.
Step 2 Log in to the ingress based on the LSR ID displayed in the IngressLsrId field. Then run the
display mpls te tunnel path command on the ingress to check nodes along the TE tunnel.
Step 3 Run the display ip interface brief command on each node to check the IP addresses and find
the IP addresses the same as that displayed in the LoopAddr field.
Step 4 Change either of two identical IP addresses to be a different one.
----End
86.29 RSVP/3/LSP_DOESNOT_EXIST
Issue 07 (2014-07-30)

954

Log Reference
86 RSVP
Message
RSVP/3/LSP_DOESNOT_EXIST:LSP did not exist. (EgressAddress=[STRING], SessionId=
[USHORT], IngressAddress=[STRING], LspId=[USHORT])
Description
The LSP did not exist.
Parameters
Parameter Name
Parameter Meaning
EgressAddress
Indicates the egress address.
SessionId
Indicates the session discriminator.
IngressAddress
Indicates the ingress address.
LspId
Indicates the LSP ID.
Possible Causes
During the active/standby switchover, the LSP was not backed up to the SMB after GR.
Procedure
----End
86.30 RSVP/3/LSP_EXCEED_PAF_LIC
Message
RSVP/3/LSP_EXCEED_PAF_LIC:Number of LSPs to be recovered given by LSPM exceeded
actual PAF licence number. (GivenNumber=[ULONG])
Description
The number of LSPs to be restored reached the maximum value specified in the License.
Parameters
Parameter Name
Parameter Meaning
GivenNumber
The number of LSPs to be restored.
Issue 07 (2014-07-30)

955

Log Reference
86 RSVP
Possible Causes
The local node was configured with self-GR. During the active/standby switchover and GR, the
number of LSPs in the License was modified to a value smaller than the number of current LSPs
in the SMB.
Procedure
----End
86.31 RSVP/3/LSRID_GET_FAIL
Message
RSVP/3/LSRID_GET_FAIL:Cannot obtain LSR ID from both RRO and CSPF. (IngressLsrId=
[STRING], SessionId=[USHORT], IngressAddress=[STRING], LspId=[USHORT])
Description
Failed to obtain the LSR ID.
Parameters
Parameter Name
Parameter Meaning
IngressLsrId
Indicates the ingress LSR ID.
SessionId
Indicates the session ID.
IngressAddress
LspId
Possible Causes
Failed to obtain the LSR ID from RRO and CSPF during the processing of the Path message.
Procedure
----End
86.32 RSVP/6/MAX_NBR_REACH
Issue 07 (2014-07-30)

956

Log Reference
86 RSVP
Message
RSVP/6/MAX_NBR_REACH:The number of the neighbours on the interface [InterfaceName]
reached the maximum value [maximum]. (CurrentNumber=[ULONG])
Description
The number of neighbors on the interface reached the maximum.
Parameters
[InterfaceName]
[maximum]
Indicates the maximum number of neighbors permitted on the interface.
CurrentNumber
Indicates the number of current neighbors.
Possible Causes
The interface corresponded to too many neighbors.
Procedure
Step 1 Check the specification and increase the configured number of neighbors.
----End
86.33 RSVP/6/MAX_SESSION_REACH
Message
RSVP/6/MAX_SESSION_REACH:Reached the maximum value of session [maximum].
Description
The number of sessions reached the maximum.
Parameters
Parameter Name
Parameter Meaning
maximum
Indicates the maximum number of sessions.
Possible Causes
The number of sessions reached the maximum during the creation of sessions.
Issue 07 (2014-07-30)

957

Log Reference
86 RSVP
Procedure
----End
86.34 RSVP/3/NBR_NO_GR_PATH
Message
RSVP/3/NBR_NO_GR_PATH:Received a path message from neighbor [NeighborAddress],
but the neighbor was not enabled GR.
Description
A Recovery Path message received from the neighbor that was not enabled with GR.
Parameters
Parameter Name
Parameter Meaning
[NeighborAddress]
Possible Causes
The local node could help the downstream neighboring node to perform GR. When the
downstream neighboring node was performing GR, the GR supporting capability or Hello
detection was disabled on the local node.
Procedure
Step 1 Check whether the neighbor needs to be enabled with the RSVP GR supporting capability.
----End
86.35 RSVP/3/NBR_NO_GR_REC_PATH
Message
RSVP/3/NBR_NO_GR_REC_PATH:Received a recovery-path message from neighbor
[NeighborAddress], but the neighbor was not enabled GR.
Description
A neighbor without the GR capability received a Recovery Path message.
Issue 07 (2014-07-30)

958

Log Reference
86 RSVP
Parameters
Parameter Name
Parameter Meaning
[NeighborAddress]
Possible Causes
The local node could help the upstream neighboring node to perform GR. When the upstream
neighboring node was performing GR, the GR supporting capability or Hello detection was
disabled on the local node.
Procedure
Step 1 Check whether the neighbor needs to be enabled with the RSVP GR supporting capability.
----End
86.36 RSVP/6/NOTIFY_LSPM_GR_END
Message
RSVP/6/NOTIFY_LSPM_GR_END:RSVP GR ends.
Description
RSVP notified LSPM that RSVP GR ended.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1. Before the active/standby switchover, the GR capability was not configured on the device.
2. No LSP existed on the device.
3. The neighboring node did not have the RSVP GR supporting capability.
4. GR was complete.
Procedure
----End
Issue 07 (2014-07-30)

959

Log Reference
86 RSVP
86.37 RSVP/6/NOTIFY_LSPM_GR_START
Message
RSVP/6/NOTIFY_LSPM_GR_START:RSVP GR starts.
Description
RSVP notified LSPM that RSVP GR started.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1. RSVP GR was configured, but the undo mpls rsvp-te command was run immediately, and
then the LSP was not deleted.
2. Before the active/standby switchover, the router already had the RSVP GR capability.
Procedure
----End
86.38 RSVP/6/PSB_CLEAN_TIMEOUT
Message
RSVP/6/PSB_CLEAN_TIMEOUT:The cleanup timer of PSB expired. (IngressLsrId=
[IPADDR], TunnelId=[USHORT], EgressLsrId=[IPADDR], LspId=[USHORT],
LastRecRefreshTime [ULONG]:[ULONG]:[ULONG](Hour:Minute:Second), CleanupTime=
[ULONG](Second))
Description
The timer of PSB expired.
Issue 07 (2014-07-30)

960

Log Reference
86 RSVP
Parameters
Parameter Name
Parameter Meaning
IngressLsrId
Indicates the LSR ID of the ingress.
TunnelId
Indicates the ID of a tunnel.
EgressLsrId
Indicates the LSR ID of the egress in the Path message.
LspId
Indicates the local LSP ID.
LastRecRefreshTime
Indicates the last time when receiving a Resv Refresh message.
CleanupTime
Indicates the timeout period of the PSB cleanup timer
Possible Causes
The PSB failed to be updated, causing the clean timer to expire. Between two directly-connected
devices, if one directly-connected interface of a device fails, the device cannot send a Path
Refresh message. As failing to receiving the Path Refresh message, the other device deletes the
TE tunnel after the PSB cleanup timer expires.
Procedure
Step 1 Check whether there is an operation that shuts down the interface or interrupts services.
----End
86.39 RSVP/3/REACH_LIC_LIMIT
Message
RSVP/3/REACH_LIC_LIMIT:The number of CR-LSPs reached the upper limit of Paf/License.
Description
The number of CR-LSPs reached the maximum value specified in the Paf/License.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The number of CR-LSPs created by the local device reached the maximum.
Issue 07 (2014-07-30)

961

Log Reference
86 RSVP
Procedure
Step 1 This log message is informational only. To create more CR-LSPs, modify the License.
----End
86.40 RSVP/4/REACH_LIST_MAXLEGTH
Message
RSVP/4/REACH_LIST_MAXLEGTH:The length of the RSVP message list reached the
maximum. (MaxLength=[ULONG])
Description
The length of the RSVP message list reached the maximum value.
Parameters
Parameter Name
Parameter Meaning
MaxLength
Indicates the maximum length of the RSVP message list.
Possible Causes
RSVP messages were not processed in time, and thus the length of the RSVP message list reached
the maximum value.
Procedure
Step 1 Run the display memory-usage command to view the status of the memory usage.
Step 2 If it is necessary and possible, run the reset mpls rsvp-te command in the user view to clear the
list. Note that this command may result in the reestablishment of all LSPs related to RSVP, so
use it with caution.
Step 3 Contact Huawei technical personnel to locate which module occupies too much CPU, which
slows down packet processing and causes the message list to be full.
----End
86.41 RSVP/3/REACH_PSB_MAXNUM
Message
RSVP/3/REACH_PSB_MAXNUM:Reached the maximum of PSBs. (MaxNumber=
[ULONG])
Issue 07 (2014-07-30)

962

Log Reference
86 RSVP
Description
During the creation of PSBs, the number of PSBs reached the maximum.
Parameters
Parameter Name
Parameter Meaning
MaxNumber
Indicates the maximum number of PW LSPs.
Possible Causes
The number of PSBs reached the maximum value specified in the License.
Procedure
Step 1 Check whether the number of TE tunnels reached the maximum value specified in the License.
----End
86.42 RSVP/3/RECONSTRUCT_LSP_FAIL
Message
RSVP/3/RECONSTRUCT_LSP_FAIL:Cannot reconstruct RSVP states for LSP.
(EgressAddress=[STRING], SessionId=[USHORT], IngressAddress=[STRING], LspId=
[USHORT])
Description
Failed to restore the LSP.
Parameters
Parameter Name
Parameter Meaning
EgressAddress
Indicates the egress address.
SessionId
Indicates the session ID.
IngressAddress
LspId
Possible Causes
Failed to use the received GR message to reestablish PSB or RSB. Possible causes are as follows:
1. The system had insufficient memory.
2. Routing information on the SMB was lost.
Issue 07 (2014-07-30)

963

Log Reference
86 RSVP
3. The TTL value was smaller than 1.

4. The system detected a loop.
Procedure
----End
86.43 RSVP/6/RECOVERY_TIMER_END
Message
RSVP/6/RECOVERY_TIMER_END:The recovery timer of neighbor [neighbor-address]
expired.
Description
The Recovery timer expired.
Parameters
Parameter Name
Parameter Meaning
[neighbor-address]
Possible Causes
When the local node or the GR supporting node was performing GR, the Recovery timer expired.
Procedure
----End
86.44 RSVP/6/RECOVERY_TIMER_START
Message
RSVP/6/RECOVERY_TIMER_START:The recovery timer of neighbor [neighbor-address]
was started.
Description
The Recovery timer was started.
Issue 07 (2014-07-30)

964

Log Reference
86 RSVP
Parameters
Parameter Name
Parameter Meaning
[neighbor-address]
Possible Causes
When the local node or the GR supporting node was performing GR, the Recovery timer was
started.
Procedure
----End
86.45 RSVP/6/RESTART_TIMER_END
Message
RSVP/6/RESTART_TIMER_END:The restart timer of neighbor [neighbor-address] expired.
Description
The Restart timer expired.
Parameters
Parameter Name
Parameter Meaning
[neighbor-address]
Possible Causes
When the local node or the GR supporting node was performing GR, the Restart timer expired.
Procedure
----End
86.46 RSVP/6/RESTART_TIMER_START
Issue 07 (2014-07-30)

965

Log Reference
86 RSVP
Message
RSVP/6/RESTART_TIMER_START:The restart timer of neighbor [neighbor-address] was
started.
Description
The Restart timer was started.
Parameters
Parameter Name
Parameter Meaning
[neighbor-address]
Possible Causes
When the local node or the GR supporting node was performing GR, the Restart timer was
started.
Procedure
----End
86.47 RSVP/6/RSB_CLEAN_TIMEOUT
Message
RSVP/6/RSB_CLEAN_TIMEOUT:The cleanup timer of RSB expired. (IngressLsrId=
[IPADDR], TunnelId=[USHORT], EgressLsrId=[IPADDR], LspId=[USHORT],
LastRecRefreshTime [ULONG]:[ULONG]:[ULONG](Hour:Minute:Second), CleanupTime=
[ULONG](Second))
Description
The RSB's cleanup timer expired.
Parameters
Parameter Name
Parameter Meaning
IngressLsrId
Indicates the LSR ID of the ingress in the Resv message.
TunnelId
Indicates the ID of a tunnel.
EgressLsrId
Indicates the LSR ID of the egress in the Resv message.
LspId
Issue 07 (2014-07-30)

966

Log Reference
86 RSVP
Parameter Name
Parameter Meaning
LastRecRefreshTime
Indicates the last time when receiving a Resv Refresh message.
CleanupTime
Indicates the timeout period of the RSB cleanup timer
Possible Causes
The RSB failed to be updated, causing its cleanup timer to expire. For example, between two
directly-connected devices, if one directly-connected interface of a device fails, the device
cannot send a Resv Refresh message. As failing to receiving the Resv Refresh message, the other
device deletes the TE tunnel after the RSB cleanup timer expires.
Procedure
Step 1 Check whether there is an operation that shuts down the interface or interrupts services.
----End
86.48 RSVP/7/SD_HA_BACK_OVER_FAIL
Message
RSVP/7/SD_HA_BACK_OVER_FAIL:Failed to sent batch backup end event to HA.
Description
Failed to send the event that batch backup ended to the HA module.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to inform the slave board that batch backup ended.
Procedure
----End
Issue 07 (2014-07-30)

967

Log Reference
87 SDSF
87
SDSF
About This Chapter

87.1 ALMA/4/SDFAILURE
87.2 ALMA/6/SDRESUME
87.3 ALMA/3/SFFAILURE
87.4 ALMA/6/SFRESUME
Issue 07 (2014-07-30)

968

Log Reference
87 SDSF
87.1 ALMA/4/SDFAILURE
Message
ALMA/4/SDFAILURE:Card [ULONG1] Port [ULONG2] is abnormal due to SD(signal
degrade) fault.
Description
Signals on a POS subcard degraded.
Parameters
Parameter Name
Parameter Meaning
ULONG1
Indicates the ID of a POS subcard.
ULONG2
Indicates the number of a POS interface.
Possible Causes
l
Cause 1: The B2 bit error rate has reached the signal degrade (SD) threshold.
Cause 2: The POS interface receives no optical signal or its optical power is out of the
normal range (too high or too low).
Procedure
Step 1 Check that the POS subcard and optical modules on the subcard are working properly.
Step 2 If the fault persists, contact Huawei technical support engineers.
----End
87.2 ALMA/6/SDRESUME
Message
ALMA/6/SDRESUME:Card [ULONG1] Port [ULONG2] SD(signal degrade) fault resumes
normal.
Description
A POS subcard has recovered from a signal degrade fault.
Issue 07 (2014-07-30)

969

Log Reference
87 SDSF
Parameters
Parameter Name
Parameter Meaning
ULONG1
ULONG2
Possible Causes
l
Cause 1: The B2 error bit rate decreased.
Cause 2: The power of the optical module recovered to the normal range.
Procedure
----End
87.3 ALMA/3/SFFAILURE
Message
ALMA/3/SFFAILURE:Card [ULONG1] Port [ULONG2] is abnormal due to SF(signal failure)
fault.
Description
A signal failure occurred on a POS subcard.
Parameters
Parameter Name
Parameter Meaning
ULONG1
ULONG2
Possible Causes
l
Cause 1: The B2 bit error rate has reached the signal failure (SF) threshold.
Cause 2: The POS interface receives no optical signal or its optical power is out of the
normal range (too high or too low).
Procedure
Step 1 Check that the POS subcard and optical modules on the subcard are working properly.
Step 2 If the fault persists, contact Huawei technical support engineers.
----End
Issue 07 (2014-07-30)

970

Log Reference
87 SDSF
87.4 ALMA/6/SFRESUME
Message
ALMA/6/SFRESUME:Card [ULONG1] Port [ULONG2] SF(signal failure) fault resumes
normal.
Description
A POS subcard has recovered from a signal failure.
Parameters
Parameter Name
Parameter Meaning
ULONG1
ULONG2
Possible Causes
l
Cause 1: The B2 error bit rate decreased.
Cause 2: The power of the optical module recovered to the normal range.
Procedure
----End
Issue 07 (2014-07-30)

971

Log Reference
88 SECE
88
SECE
About This Chapter

88.1 SECE/4/ARPMISS
88.2 SECE/3/ARPS_DROP_PACKET_GLOBLE_SPDLMT
88.3 SECE/3/ARPS_DROP_PACKET_HDADDR_LEN
88.4 SECE/3/ARPS_DROP_PACKET_IF_SPDLMT
88.5 SECE/3/ARPS_DROP_PACKET_LENTH
88.6 SECE/3/ARPS_DROP_PACKET_OPTYPE
88.7 SECE/3/ARPS_DROP_PACKET_PROADDR_LEN
88.8 SECE/3/ARPS_DROP_PACKET_SRC_MAC
88.9 SECE/3/ARPS_DROP_PACKET_VLAN_SPDLMT
88.10 SECE/4/DAI_DROP_PACKET
88.11 SECE/4/GWCONFLICT
88.12 SECE/4/ICMP_GLOBAL_RATELIMIT
88.13 SECE/4/ICMP_INTF_RATELIMIT
88.14 SECE/4/IPSG_DROP_PACKET
88.15 SECE/4/IPSG_TABLE_RESOURCE
88.16 SECE/6/MFF_GW_MAC_CHANGED
88.17 SECE/4/PORT_ATTACK
88.18 SECE/6/PORT_ATTACK_END
88.19 SECE/4/PORT_ATTACK_OCCUR
88.20 SECE/4/SPECIFY_SIP_ATTACK
Issue 07 (2014-07-30)

972

Log Reference
88 SECE
88.21 SECE/4/STORMCTRL_BC_BLOCKED
88.22 SECE/4/STORMCTRL_BC_UNBLOCK
88.23 SECE/4/STORMCTRL_IF_NORMAL
88.24 SECE/4/STORMCTRL_IF_SHUTDOWN
88.25 SECE/4/STORMCTRL_MC_BLOCKED
88.26 SECE/4/STORMCTRL_MC_UNBLOCK
88.27 SECE/4/STORMCTRL_UC_BLOCKED
88.28 SECE/4/STORMCTRL_UC_UNBLOCK
88.29 SECE/4/STRACK_DENY
88.30 SECE/4/STRACK_ERROR_DOWN
88.31 SECE/4/USER_ATTACK
Issue 07 (2014-07-30)

973

Log Reference
88 SECE
88.1 SECE/4/ARPMISS
Message
SECE/4/ARPMISS: Attack occurred.(AttackType=Arp Miss Attack, SourceInterface=
[STRING], SourceIP=[STRING], AttackPackets=[ULONG] packets per second)
Description
The rate exceeds the global ARP Miss rate limit.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Interface name.
[STRING]
Source IP address of attack packet.
[ULONG]
Rate of attack packets, in pps.
Possible Causes
The rate of ARP Miss packets sent by the attacker exceeds the limit.
Procedure
l
Run the display this command in the system view to view the ARP Miss rate limit.
Run the arp-miss anti-attack rate-limit packet-number [ interval-value ] command in the

system view to reconfigure the rate limit.
If the log is generated frequently, contact Huawei technical support engineers; otherwise,
you do not need to take any measure.
----End
88.2 SECE/3/ARPS_DROP_PACKET_GLOBLE_SPDLMT
Message
SECE/3/ARPS_DROP_PACKET_GLOBLE_SPDLMT:Rate of global arp packets exceeds the
limit.(SourceMAC=[STRING], SourceIP=[STRING], SourceInterface=[STRING],
DropTime=[STRING])
Description
The rate of ARP packets on the device exceeds the threshold.
Issue 07 (2014-07-30)

974

Log Reference
88 SECE
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the source MAC address of the ARP packets.
[STRING]
Indicates the source IP address of the ARP packets.
[STRING]
Indicates the source interface of the ARP packets.
[STRING]
Indicates the packet discard time.
Possible Causes
The rate of ARP packets on the device exceeds the threshold.
Procedure
l
If the processing speed becomes slow or the CPU usage is too high, run the arp anti-attack
rate-limit command to adjust the threshold.
----End
88.3 SECE/3/ARPS_DROP_PACKET_HDADDR_LEN
Message
SECE/3/ARPS_DROP_PACKET_HDADDR_LEN:Invalid hard address length.
(HardAddressLength=[ULONG], SourceMAC=[STRING], SourceIP=[STRING],
SourceInterface=[STRING], DropTime=[STRING])
Description
The hardware address length in the ARP packet is invalid.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the MAC address length of the ARP packets.
[STRING]
[STRING]
[STRING]
Issue 07 (2014-07-30)

975

Log Reference
88 SECE
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The device receives an ARP packet with the hardware address that has an invalid length.
Procedure
l
Find out the interface that initiates the attack according to the SourceInterface field in the
alarm message.
Find out the user who sends attack packets according to the SourceMAC field.
Check whether the user host runs abnormally; if not, the user may be an attacker. In this
case, you can take measures to prevent the user, for example, disconnect the user from the
network.
----End
88.4 SECE/3/ARPS_DROP_PACKET_IF_SPDLMT
Message
SECE/3/ARPS_DROP_PACKET_IF_SPDLMT:Rate of arp packets on interface exceeds the
limit.(SourceMAC=[STRING], SourceIP=[STRING], SourceInterface=[STRING],
DropTime=[STRING])
Description
The rate of ARP packets on the interface exceeds the threshold.
Parameters
Parameter Name
Parameter Meaning
[STRING]
[STRING]
[STRING]
[STRING]
Possible Causes
The rate of ARP packets on the interface exceeds the threshold.
Issue 07 (2014-07-30)

976

Log Reference
88 SECE
Procedure
l
----End
88.5 SECE/3/ARPS_DROP_PACKET_LENTH
Message
SECE/3/ARPS_DROP_PACKET_LENTH:Invalid packet length.(PacketLength=[ULONG],
SourceMAC=[STRING], SourceIP=[STRING], SourceInterface=[STRING],DropTime=
[STRING])
Description
The length of ARP packet is invalid.
Parameters
[ULONG]
Indicates the length of the ARP packet. The length ranges from 60 to 1518.
[STRING]
[STRING]
[STRING]
[STRING]
Possible Causes
The device receives an ARP packet of invalid length.
Procedure
l
alarm message.
network.
----End
Issue 07 (2014-07-30)

977

Log Reference
88 SECE
88.6 SECE/3/ARPS_DROP_PACKET_OPTYPE
Message
SECE/3/ARPS_DROP_PACKET_OPTYPE:Invalid packet optype.(OperateType=[ULONG],
SourceMAC=[STRING], SourceIP=[STRING], SourceInterface=[STRING], DropTime=
[STRING])
Description
The type of ARP packet is invalid.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the type of ARP packets.
[STRING]
[STRING]
[STRING]
[STRING]
Possible Causes
The device receives an ARP packet of invalid type.
Procedure
l
alarm message.
network.
----End
Issue 07 (2014-07-30)

978

Log Reference
88 SECE
88.7 SECE/3/ARPS_DROP_PACKET_PROADDR_LEN
Message
SECE/3/ARPS_DROP_PACKET_PROADDR_LEN:Invalid protocol address length.
(ProAddressLength=[ULONG], SourceMAC=[STRING], SourceIP=[STRING],
SourceInterface=[STRING], DropTime=[STRING])
Description
The protocol address length in the ARP packet is invalid.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the length of ARP packets.
[STRING]
[STRING]
[STRING]
[STRING]
Possible Causes
The device receives an ARP packet with the protocol address that has an invalid length.
Procedure
l
alarm message.
network.
----End
Issue 07 (2014-07-30)

979

Log Reference
88 SECE
88.8 SECE/3/ARPS_DROP_PACKET_SRC_MAC
Message
SECE/3/ARPS_DROP_PACKET_SRC_MAC:Invalid source mac address.(SourceMAC=
[STRING], SourceIP=[STRING], SourceInterface=[STRING], DropTime=[STRING])
Description
The source MAC address in the ARP packet is invalid.
Parameters
Parameter Name
Parameter Meaning
[STRING]
[STRING]
[STRING]
[STRING]
Possible Causes
The device receives an ARP packet with invalid source MAC address.
Procedure
l
alarm message.
network.
----End
88.9 SECE/3/ARPS_DROP_PACKET_VLAN_SPDLMT
Message
SECE/3/ARPS_DROP_PACKET_VLAN_SPDLMT:Rate of arp packets in vlan exceeds the
limit.(SourceMAC=[STRING], SourceIP=[STRING], SourceInterface=[STRING], Vlan=
[ULONG], DropTime=[STRING])
Issue 07 (2014-07-30)

980

Log Reference
88 SECE
Description
The rate of ARP packets in the VLAN exceeds the threshold.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the outer VLAN ID of packets.
[STRING]
[STRING]
[STRING]
[STRING]
Possible Causes
The rate of ARP packets in the VLAN exceeds the threshold.
Procedure
l
----End
88.10 SECE/4/DAI_DROP_PACKET
Message
SECE/4/DAI_DROP_PACKET:Not hit the user-bind table.(SourceMAC=[STRING],
SourceIP=[STRING], SourceInterface=[STRING], DropTime=[STRING])
Description
The ARP packet does not match any entry in the DHCP snooping binding table.
Parameters
Parameter Name
Parameter Meaning
[STRING]
[STRING]
Issue 07 (2014-07-30)

981

Log Reference
88 SECE
Parameter Name
Parameter Meaning
[STRING]
[STRING]
Possible Causes
The device receives an ARP packet that does not match any entry in the DHCP snooping binding
table.
Procedure
l
Find out the interface where attacks occur according to Interface in the alarm message.
Run the display dhcp snooping user-bind command to check whether users who are not
in the DHCP snooping binding table range are connected.
If new users are connected, run related DHCP snooping commands to generate the DHCP
snooping binding entry.
----End
88.11 SECE/4/GWCONFLICT
Message
SECE/4/GWCONFLICT:Attack occurred.(AttackType=Gateway Attack, SourceInterface=
[STRING], SourceMAC=[STRING], PVlanID=[ULONG])
Description
An address conflicts with the gateway address.
Parameters
[STRING]
Indicates the interface that initiates the attack.
[STRING]
Indicates the MAC address of the attack source.
[ULONG]
Indicates the outer VLAN ID or single VLAN ID of the attack source.
Possible Causes
An address conflicts with the gateway address.
Issue 07 (2014-07-30)

982

Log Reference
88 SECE
Procedure
l
1. Run the display arp anti-attack gateway-duplicate item command to view the attacker.
----End
88.12 SECE/4/ICMP_GLOBAL_RATELIMIT
Message
SECE/4/ICMP_GLOBAL_RATELIMIT:The rate of global ICMP packets exceeded the limit.
(Threshold=[ULONG] packets per second)
Description
The total rate of ICMP packets on all interfaces has exceeded the rate limit.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the global rate limit for ICMP packets.
Possible Causes
The rate of ICMP packets received in the system exceeds the configured global rate limit.
Procedure
l
If the global rate limit for ICMP packets is too low and affects the response to ping
operations, increase the rate limit.
----End
88.13 SECE/4/ICMP_INTF_RATELIMIT
Message
SECE/4/ICMP_INTF_RATELIMIT:The rate of ICMP packets on the interface exceeded the
limit.(SourceInterface=[STRING], Threshold=[ULONG] packets per second)
Description
The rate of IGMP packets on an interface has exceeded the rate limit.
Issue 07 (2014-07-30)

983

Log Reference
88 SECE
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the source interface of ICMP packets.
[ULONG]
Specifies the rate limit for ICMP packets.
Possible Causes
The rate of ICMP packets received on an interface exceeds the configured rate limit.
Procedure
l
If the rate limit configured for ICMP packets on an interface is too small and affects the
response to ping operations, increase the rate limit on the interface. If the rate of IGMP
packets received on the interface exceeds the global rate limit, increase the global rate limit.
----End
88.14 SECE/4/IPSG_DROP_PACKET
Message
SECE/4/IPSG_DROP_PACKET:IP packets,dropped by IPSG.(SourceInterface=
[STRING],DropPacketNumber=[ULONG],DroptTime=[STRING])
Description
IP packets are discarded by IPSG.
Parameters
[STRING]
Indicates the source interface of the packets.
[ULONG]
Indicates the number of discarded packets.
[STRING]
On the S5700EI, this parameter indicates packet discard time and

information about the user with the most packets dropped, including the
VLAN ID, source MAC address, and source IP address. On other models,
this parameter indicates the packet discard time.
Possible Causes
The device receives an IP packet that does not match any entry in the DHCP snooping binding
table.
Issue 07 (2014-07-30)

984

Log Reference
88 SECE
Procedure
l
Find out the interface where attacks occur according to Interface in the alarm message.
Run the display dhcp snooping user-bind command to check whether users who are not
in the DHCP snooping binding table range are connected.
If new users are connected, run related DHCP snooping commands to generate the DHCP
snooping binding entry.
----End
88.15 SECE/4/IPSG_TABLE_RESOURCE
Message
SECE/4/IPSG_TABLE_RESOURCE:Resource for [STRING1] in slot [STRING2] is not
enough.
Description
The hardware resources on the device are insufficient.
Parameters
Parameter Name
Parameter Meaning
[STRING1]
Indicates a resource type.
[STRING2]
Indicates a stack ID.
Possible Causes
The IP source guard function is enabled, but the device does not have enough hardware resources
for the IP source guard function. The IP source guard function may not take effect.
Procedure
l
----End
88.16 SECE/6/MFF_GW_MAC_CHANGED
Message
SECE/6/MFF_GW_MAC_CHANGED:The MAC address of a gateway changed. (IP=
[IPADDR], old MAC=[OCTET], new MAC=[OCTET])
Issue 07 (2014-07-30)

985

Log Reference
88 SECE
Description
The MAC address matching the MFF gateway's IP address changes.
Parameters
Parameter Name
Parameter Meaning
IP
Indicates the IP address of the MFF gateway.
old MAC
Indicates the original MAC address of the MFF gateway.
new MAC
Indicates the changed MAC address of the MFF gateway.
Possible Causes
The MAC address matching the MFF gateway's IP address changes.
Procedure
Step 1 Check whether the gateway has changed its MAC address.
Step 2 If the MAC address of the gateway is changed, no operation is required.
Step 3 If the MAC address of the gateway is not changed, run the display mac-address command to
check whether the VLAN ID and interface matching the changed MAC address are valid.
Step 4 If the MAC address belongs to an authorized user, the user's MAC address conflict with the
MFF gateway's MAC address. Request the network administrator to change the user's MAC
address or MFF gateway's MAC address.
Step 5 If the MAC address belongs to an unauthorized user, run the mac-address blackhole command
to discard the packets from this user.
Step 6 If the fault persists, contact the Huawei technical personnel.
----End
88.17 SECE/4/PORT_ATTACK
Message
SECE/4/PORT_ATTACK:Port attack occurred.(Slot=[STRING], SourceAttackInterface=
[STRING], OuterVlan/InnerVlan=[ULONG]/[ULONG], AttackProtocol=[STRING],
AttackPackets=[ULONG] packets per second)
Description
A lot of attack packets from the corresponding VLAN are received on the interface.
Issue 07 (2014-07-30)

986

Log Reference
88 SECE
Parameters
Parameter Name
Parameter Meaning
Slot
l The value is 0 if stacking is not configured.

l Indicates the stack ID if stacking is configured.
SourceAttackInterface Indicates the interface that initiates the attack.

OuterVlan
InnerVlan
Indicates the inner VLAN ID of the attack source.
AttackProtocol
Indicates the protocol type of attack packets.
AttackPackets
Indicates the rate of attack packets, in pps.
Possible Causes
A lot of attack packets from the corresponding VLAN are received on the interface.
Procedure
Step 1 Run the display auto-defend attack-source command to check whether attack packets exist on
the interfaces.
Step 2 Analyze the packet characteristics. Configure static ACL and CAR according to the packet
characteristics.
Step 3 Apply the policy to the device.
----End
88.18 SECE/6/PORT_ATTACK_END
Message
The log on the S5700EI is SECE/6/PORT_ATTACK_END:Auto port-defend stop.
(SourceAttackInterface=[STRING], AttackProtocol=[STRING]), VLAN=[ULONG]).
The log on other models is SECE/6/PORT_ATTACK_END:Auto port-defend stop.
(SourceAttackInterface=[STRING], AttackProtocol=[STRING]).
Description
Port attack defense is canceled.
Issue 07 (2014-07-30)

987

Log Reference
88 SECE
Parameters
Parameter Name
Parameter Meaning
SourceAttackInterface
Indicates the attack source interface.
AttackProtocol
VLAN
Indicates the VLAN where attack packets are sent from.
Possible Causes
After you exclude an attack source, the device cancels attack defense on the interface.
Procedure
----End
88.19 SECE/4/PORT_ATTACK_OCCUR
Message
The log on the S5700EI is SECE/4/PORT_ATTACK_OCCUR:Auto port-defend started.
(SourceAttackInterface=[STRING], AttackProtocol=[STRING], VLAN=[ULONG]).
The log on other models is SECE/4/PORT_ATTACK_OCCUR:Auto port-defend started.
(SourceAttackInterface=[STRING], AttackProtocol=[STRING]).
Description
Port attack defense is started.
Parameters
Parameter Name
Parameter Meaning
SourceAttackInterface
Indicates the attack source interface.
AttackProtocol
VLAN
Indicates the VLAN where attack packets are sent from.
Possible Causes
When the device detects attack packets on an interface, the device starts attack defense on the
interface.
Procedure
Step 1 Check whether the attack actually occurs on the interface.
Issue 07 (2014-07-30)

988

Log Reference
88 SECE
Step 2 If an attack actually occurs, locate the attack source. If no attack occurs, reconfigure the port
attack defense function to ensure that valid protocol packets can be sent to the CPU.
----End
88.20 SECE/4/SPECIFY_SIP_ATTACK
Message
SECE/4/SPECIFY_SIP_ATTACK:The specified source IP address attack occurred.(Slot=
[STRING], SourceAttackIP = [STRING], AttackProtocol=[STRING], AttackPackets=
[ULONG] packets per second)
Description
The attack source is displayed when a device is attacked.
Parameters
Parameter Name
Parameter Meaning
Slot

SourceAttackIP
Indicates the source IP address of an attack.
AttackProtocol
AttackPackets
Possible Causes
A lot of attack packets from the corresponding IP address were received on the interface.
Procedure
Step 1 Run the display auto-defend attack-source command to check whether the user attack packets
exist.
Step 2 If so, run the auto-defend action deny command to discard the attack packets.
Step 3 If the fault persists, contact Huawei technical personnel.
----End
Issue 07 (2014-07-30)

989

Log Reference
88 SECE
88.21 SECE/4/STORMCTRL_BC_BLOCKED
Message
SECE/4/STORMCTRL_BC_BLOCKED:Broadcast packets are blocked at interface
[STRING].
Description
Broadcast packets are blocked on the interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The broadcast traffic on interfaces exceeds the upper limit of storm control.
Procedure
l
Find out the reason why the broadcast storm occurs.
----End
88.22 SECE/4/STORMCTRL_BC_UNBLOCK
Message
SECE/4/STORMCTRL_BC_UNBLOCK:Broadcast packets are unblocked at interface
[STRING].
Description
Broadcast packets are forwarded on the interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The broadcast traffic on interfaces does not reach the lower limit of storm control.
Issue 07 (2014-07-30)

990

Log Reference
88 SECE
Procedure
l
This log message is informational and no action is required.
----End
88.23 SECE/4/STORMCTRL_IF_NORMAL
Message
SECE/4/STORMCTRL_IF_NORMAL:Interface [STRING] is normal for storm-control.
Description
The interface status is recovered.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
1. The interface status is changed from shutdown to normal.
2. The upper and lower limits of storm control are deleted.
3. The storm suppression action is canceled.
Procedure
l
----End
88.24 SECE/4/STORMCTRL_IF_SHUTDOWN
Message
SECE/4/STORMCTRL_IF_SHUTDOWN:Interface [STRING] is shutdown for storm-control.
Description
The interface is shut down.
Issue 07 (2014-07-30)

991

Log Reference
88 SECE
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The interface is shut down because the broadcast, multicast, or unicast traffic on the interface
exceeds the limit.
Procedure
l
Find out the reason why the broadcast storm occurs.
Perform undo shutdown on the interface.
----End
88.25 SECE/4/STORMCTRL_MC_BLOCKED
Message
SECE/4/STORMCTRL_MC_BLOCKED:Multicast packets are blocked at interface
[STRING].
Description
Multicast packets are blocked on the interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The multicast traffic on interfaces exceeds the upper limit of storm control.
Procedure
l
Find out the reason why multicast storm occurs.
----End
Issue 07 (2014-07-30)

992

Log Reference
88 SECE
88.26 SECE/4/STORMCTRL_MC_UNBLOCK
Message
SECE/4/STORMCTRL_MC_UNBLOCK:Multicast packets are unblocked at interface
[STRING].
Description
Multicast packets are forwarded on the interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The multicast traffic on interfaces does not reach the lower limit of storm control.
Procedure
l
----End
88.27 SECE/4/STORMCTRL_UC_BLOCKED
Message
SECE/4/STORMCTRL_UC_BLOCKED:Unicast packets are blocked at interface [STRING].
Description
Unknown unicast packets are blocked on the interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The unknown unicast traffic on interfaces exceeds the upper limit of storm control.
Issue 07 (2014-07-30)

993

Log Reference
88 SECE
Procedure
l
Find out the reason why multicast storm occurs.
----End
88.28 SECE/4/STORMCTRL_UC_UNBLOCK
Message
SECE/4/STORMCTRL_UC_UNBLOCK:Uniccast packets are unblocked at interface
[STRING].
Description
Unknown unicast packets are forwarded on the interface.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The unknown unicast traffic on interfaces does not reach the lower limit of storm control.
Procedure
l
----End
88.29 SECE/4/STRACK_DENY
Message
SECE/4/STRACK_DENY: Some packets are dropped because an attack is detected.(Interface=
[OCTET], sourceMAC=[OCTET], sourceIP=[IPADDR], CVLAN=[INTEGER], PVLAN=
[INTEGER], )
NOTE
The S2750, S5700SI, S5700EI, S5700LI, and S5700S-LI do not support the STRACK_DENY log.
Description
The switch discards some packets because it detects an attack.
Issue 07 (2014-07-30)

994

Log Reference
88 SECE
Parameters
Parameter Name
Parameter Meaning
Interface
Indicates the interface that receives attack packets.
sourceMAC
Indicates the source MAC address of attack packets.
sourceIP
Indicates the source IP address of attack packets.
CVLAN
Indicates the inner VLAN ID of attack packets.
PVLAN
Indicates the outer VLAN ID of attack packets.
Possible Causes
The attack tracing module detects an attack, and the attack defense action is set to deny.
Procedure
Step 1 Check whether the discarded packets are sent from an authorized user.
Step 2 If the sender is an authorized user, run the auto-defend whitelist whitelist-num { acl
acl_number | interface interface-type interface-number } command to add the user to the
whitelist. Then packets sent from this user are not discarded.
Step 3 If the sender is an attacker, you do not need to perform any operation.
----End
88.30 SECE/4/STRACK_ERROR_DOWN
Message
SECE/4/STRACK_ERROR_DOWN: Interface's status is changed to error-down because an
attack is detected. Interface=[OCTET].
Description
An interface transitions to error-down state because an attack is detected on the interface.
Parameters
Parameter Name
Parameter Meaning
Interface
Indicates the interface that receives attack packets.
Possible Causes
The attack tracing module detects an attack, and the attack defense action is set to errordown.
Issue 07 (2014-07-30)

995

Log Reference
88 SECE
Procedure
Step 1 Check whether the discarded packets are sent from an authorized user.
Step 2 If the sender is an authorized user, run the auto-defend whitelist whitelist-num { acl
acl_number | interface interface-type interface-number } command to add the user to the
whitelist. Then packets sent from this user are not discarded.
Step 3 If the sender is an attacker, you do not need to perform any operation.
----End
88.31 SECE/4/USER_ATTACK
Message
SECE/4/USER_ATTACK:User attack occurred.(Slot=[STRING], SourceAttackInterface=
[STRING], OuterVlan/InnerVlan=[ULONG]/[ULONG], UserMacAddress=[STRING],
AttackProtocol=[STRING], AttackPackets=[ULONG] packets per second)
Description
User attack information is generated on the device.
Parameters
Parameter Name
Parameter Meaning
Slot

SourceAttackInterface Indicates the interface that initiates the attack.

OuterVlan
InnerVlan
Indicates the inner VLAN ID of the attack source.
UserMacAddress
Indicates the MAC address of the attack source.
AttackProtocol
AttackPackets
Possible Causes
A lot of attack packets from the corresponding VLAN or MAC address are received on the
interface.
Issue 07 (2014-07-30)

996

Log Reference
88 SECE
Procedure
Step 1 Run the display auto-defend attack-source command to check whether user attack packets
exist.
Step 2 Analyze the packet characteristics. Configure static ACL and CAR according to the packet
characteristics.
Step 3 Apply the policy to the device.
----End
Issue 07 (2014-07-30)

997

Log Reference
89 SEP
89
SEP
About This Chapter

89.1 SEP/6/CFG_ADD_PORT
89.2 SEP/6/CFG_DEL_PORT
89.3 SEP/4/LSA_NUM_REACH_MAX
89.4 SEP/6/MSI_LESS_MSN
89.5 SEP/3/PREEMPT_REQ_FAIL
89.6 SEP/6/RCV_CFM_FAULT
Issue 07 (2014-07-30)

998

Log Reference
89 SEP
89.1 SEP/6/CFG_ADD_PORT
Message
SEP/6/CFG_ADD_PORT:Added the port to the SEP segment.(port name=[STRING], segment
ID=[ULONG])
Description
The interface was added to the SEP segment.
Parameters
Parameter Name
Parameter Meaning
port name
Name of the interface added to the SEP segment
segment ID
ID of the SEP segment
Possible Causes
The interface was added to the SEP segment.
Procedure
----End
89.2 SEP/6/CFG_DEL_PORT
Message
SEP/6/CFG_DEL_PORT:Deleted the port from the SEP segment. (port name=[STRING],
segment ID=[ULONG])
Description
The interface was removed from the SEP segment.
Parameters
Parameter Name
Parameter Meaning
port name
Name of the interface removed from the SEP segment
segment ID
Issue 07 (2014-07-30)

999

Log Reference
89 SEP
Possible Causes
The interface was removed from the SEP segment.
Procedure
----End
89.3 SEP/4/LSA_NUM_REACH_MAX
Message
SEP/4/LSA_NUM_REACH_MAX:The number of LSAs in the SEP segment reached the upper
limit.(segment ID=[ULONG], LSA number=[ULONG])
Description
The number of Link State Advertisements (LSAs) on the SEP segment reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
segment ID
LSA number
Number of LSAs
Possible Causes
The number of nodes on the SEP segment reached the upper limit defined in the PAF file.
Procedure
Step 1 Collect configurations and log messages, and then contact Huawei technical support personnel
to replace the PAF file.
----End
89.4 SEP/6/MSI_LESS_MSN
Message
SEP/6/MSI_LESS_MSN:The maximum SEP segment ID is smaller than the maximum number
of SEP segments that can be supported by the device.
Issue 07 (2014-07-30)

1000

Log Reference
89 SEP
Description
The largest SEP segment ID is smaller than the maximum number of SEP segments supported
by the device.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
The specification defined in the PAF file was incorrect.
Procedure
Step 1 Collect configurations and log messages, and then contact Huawei technical support personnel
to replace the PAF file.
----End
89.5 SEP/3/PREEMPT_REQ_FAIL
Message
SEP/3/PREEMPT_REQ_FAIL:Preemption failed because the number of preempt request
packets reached the upper limit. (preempt number=[ULONG])
Description
Preemption failed because the number of preemption request packets reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
preempt number
Number of preemption request packets
Possible Causes
1. Failed to send preemption request packets.
2. The peer device failed to receive preemption request packets.
Procedure
Step 1 1. Failed to send preemption request packets.
Issue 07 (2014-07-30)

1001

Log Reference
89 SEP
The chip of the device may fail. In this case, collect configurations and log messages, and then
Step 2 2. The remote device failed to receive preemption request packets.
1.
Run the reset sep interface interface-type interface-number statistics command on the
local and remote devices to clear the statistics about the SEP protocol packets on the
specified interface on the SEP segment.
2.
Run the display sep interface interface-type interface-number [ verbose ] command on

the local device to view the PREEMPT REQ TLV field. Check whether there is count
displayed in the tx sub-field.
l If there is count displayed in the tx sub-field in the PREEMPT REQ TLV field, it
indicates that the local device has sent preemption request packets. In this case, go to
c.
l If there is no count displayed in the tx sub-field in the PREEMPT REQ TLV field, it
indicates that the local device has not sent preemption request packets. In this case, go
to e.
3.
Run the display sep interface interface-type interface-number [ verbose ] command on

the remote device to view the PREEMPT ACK TLV field. Check whether there is count
displayed in the rx sub-field.
l If there is count displayed in the rx sub-field in the PREEMPT ACK TLV field, it
indicates that the remote device has received preemption request packets. In this case,
go to e.
l If there is no count displayed in the rx sub-field in the PREEMPT ACK TLV field, it
indicates that the remote device has not received preemption request packets. In this
case, go to d.
4.
Check whether the link frequently alternates between Up and Down states.
l If the link frequently alternates between Up and Down states, replace the hardware or
optical fibers.
l If the link status remains unchanged, go to e.
5.
Collect configurations and log messages, and then contact Huawei technical support
personnel.
----End
89.6 SEP/6/RCV_CFM_FAULT
Message
SEP/6/RCV_CFM_FAULT:The SEP receives an error notification from the CFM. (Segment
ID=[ULONG], Port Name=[STRING], Fault State=[STRING])
Description
After the SEP segment was associated with CFM, CFM sends a fault notification to the SEP
segment through the OAM module when detecting a connectivity fault or a fault recovery event.
Issue 07 (2014-07-30)

1002

Log Reference
89 SEP
Parameters
Parameter Name
Parameter Meaning
Segment ID
Port Name
Name of the interface added to the SEP segment
Fault State
Fault state
Possible Causes
1. After the SEP segment was associated with CFM, CFM detected that the fault was rectified.
2. After the SEP segment was associated with CFM, CFM detected a connectivity fault.
Procedure
Step 1 1. After the SEP segment was associated with CFM, CFM detected that the fault was rectified.
Step 2 2. After the SEP segment was associated with CFM, CFM detected a connectivity fault.
1.
Run the display cfm remote-mep command to view the CFM Status field.
l If the CFM Status field is displayed as Up, it indicates that the CC link is normal. In
this case, go to Step 2.2.
l If the CFM Status field is displayed as Up, it indicates that CFM detects a CC link fault.
In this case, go to Step 2.2.
2.
Collect configurations and log messages, and then contact Huawei technical support
personnel.
----End
Issue 07 (2014-07-30)

1003

Log Reference
90 SHELL
90
SHELL
About This Chapter

90.1 SHELL/5/CMDRECORD
90.2 SHELL/6/CMDCONFIRM_NOPROMPT
90.3 SHELL/6/CMDCONFIRM_RECORD
90.4 SHELL/6/CMDCONFIRM_UNIFORMRECORD
90.5 SHELL/6/DISPLAY_CMDRECORD
90.6 SHELL/4/LOGINFAILED
90.7 SHELL/5/LOGIN
90.8 SHELL/5/LOGOUT
90.9 SHELL/4/OVERWRITE_EXEC
90.10 SHELL/5/SETPASS_FAIL_FIRSTLOGIN
90.11 SHELL/5/TIMEOUT
Issue 07 (2014-07-30)

1004

Log Reference
90 SHELL
90.1 SHELL/5/CMDRECORD
Message
SHELL/5/CMDRECORD:Record command information. (Task=[string], Ip=[string], User=
[string], Command="[string]",, Result=[string])
Description
The user command was recorded.
Parameters
Task
Indicates the task name. For details about the task name, see Description
of the display cpu-usage command output.
Ip
scenario where the user logs in using a Console interface, asterisks (**)
are used to indicate the IP address.
User
Indicates the name of a user.

user name.
Command
Indicates a command.
Result
Indicates a command execution result, which includes Success,

ExecutionFailure, and AuthenticationFailure.
Possible Causes
Procedure
----End
90.2 SHELL/6/CMDCONFIRM_NOPROMPT
Issue 07 (2014-07-30)

1005

Log Reference
90 SHELL
Message
SHELL/6/CMDCONFIRM_NOPROMPT:Record command information. (Task=[Task], IP=
[IP], User=[User], Command="[Command]", UserInput=[UserInput])
Description
The system logged confirm information of interactive commands.
Parameters
Task
Indicates the task name, such as VTn and JOB.
IP
User
Indicates user name.

user name.
Command
Indicates the command executed by the user.
UserInput
Indicates users' selection. The value is Y or N.
Possible Causes
Users ran interactive commands.
Procedure
----End
90.3 SHELL/6/CMDCONFIRM_RECORD
Message
SHELL/6/CMDCONFIRM_RECORD: When being asked whether to execute the command
"[command]", the user chose [Y/N].(Task=[Task], IP=[IP], User=[User])
Description
The user chose Y or N to decide whether to disable the command "[command]".
Issue 07 (2014-07-30)

1006

Log Reference
90 SHELL
Parameters
command
Command line
Y/N
A user can decide whether to disable the command "[command]":

l Y: Disable the command "[command]".
l N: Do not disable the command "[command]".
Task
Task ID
Ip
IP address
User
User name
user name.
Possible Causes
When you intended to disable the command "[command]", the system prompted you to decide
whether to execute.
Procedure
----End
90.4 SHELL/6/CMDCONFIRM_UNIFORMRECORD
Message
SHELL/6/CMDCONFIRM_UNIFORMRECORD:Record command information. (Task=
[Task], IP=[IP], User=[User], Command="[Command]", PromptInfo="[PromptInfo]",
UserInput=[UserInput])
Description
The system logged confirm information of interactive commands.
Issue 07 (2014-07-30)

1007

Log Reference
90 SHELL
Parameters
Task
Indicates the task name, such as VTn and JOB.
IP
User
Indicates user name.

user name.
Command
Indicates the command executed by the user.
PromptInfo
Indicates the prompt output on terminals.
UserInput
Indicates users' selection. The value is Y or N.
Possible Causes
Users ran interactive commands.
Procedure
----End
90.5 SHELL/6/DISPLAY_CMDRECORD
Message
SHELL/6/DISPLAY_CMDRECORD: Record display command information. (Task=[string],
Ip=[string], User=[string], Command="[string]")
Description
The user display command was recorded.
Parameters
Task
Issue 07 (2014-07-30)
Indicates the ID of a task.

1008

Log Reference
90 SHELL

Ip
User

user name.
Command
Indicates a command.
Possible Causes
Procedure
----End
90.6 SHELL/4/LOGINFAILED
Message
SHELL/4/LOGINFAILED:Failed to login. (Ip=[Ip], UserName=[UserName], Times=[Times],
AccessType=[AccessType])
Description
Failed to login.
Parameters
Ip
Issue 07 (2014-07-30)

1009

Log Reference
90 SHELL

UserName

user name.
Times
Indicates the number of failed logins.
AccessType
Indicates the type of logins.
Possible Causes
The user name or password of the user was incorrect.
Procedure
l If either the user name or the password is incorrect, enter the correct user name or password.
l If the user name and password are correct, collect log information and configuration
information, and contact Huawei technical support personnel.
----End
90.7 SHELL/5/LOGIN
Message
SHELL/5/LOGIN: The user succeeded in logging in to [UserIndex]. (UserType=[STRING],
UserName=[STRING], Ip=[STRING], VpnName=[STRING])
Description
The user logged in.
Parameters
UserIndex
Indicates the index of a user.
UserType
Indicates the type of a user.
UserName

When the device fails to obtain the user name, for example, in a passwordbased user authentication scenario, the value of this parameter is empty.
Issue 07 (2014-07-30)

1010

Log Reference
90 SHELL

Ip

interface, the value of this parameter is empty.
VpnName
Indicates the vpn-instance name.
Possible Causes
The user logged in.
Procedure
----End
90.8 SHELL/5/LOGOUT
Message
SHELL/5/LOGOUT: The user succeeded in logging out of [UserIndex]. (UserType=[STRING],
UserName=[STRING], Ip=[STRING], VpnName=[STRING])
Description
The user logged out.
Parameters
Parameter Name
Parameter Meaning
UserIndex
Indicates the index of a user.
UserType
Indicates the type of a user.
UserName
Ip
VpnName
Indicates the vpn-instance name.
Possible Causes
The user logged out.
Issue 07 (2014-07-30)

1011

Log Reference
90 SHELL
Procedure
----End
90.9 SHELL/4/OVERWRITE_EXEC
Message
SHELL/4/OVERWRITE_EXEC:The user chose [Y/N] when deciding whether to overwrite the
existing file.
Description
The user decides whether to overwrite the existing file before running this command.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
prompts the user to confirm the action.
Possible Causes
The user decides whether to overwrite the existing file before running this command.
Procedure
----End
90.10 SHELL/5/SETPASS_FAIL_FIRSTLOGIN
Message
SHELL/5/SETPASS_FAIL_FIRSTLOGIN: Failed to set password when login firstly.
Description
A user failed to set a password during the first login.
Issue 07 (2014-07-30)

1012

Log Reference
90 SHELL
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
The user set a whose complexity did not meet the requirement during the first login.
Procedure
Step 1 Check whether the complexity of the password meets the requirement.
l If yes, go to Step 2.
l If no, enter a new password whose complexity meets the requirement. If you fail to set a new
password, go to Step 2.
----End
90.11 SHELL/5/TIMEOUT
Message
SHELL/5/TIMEOUT:[user-name] login from [ip-address] is time out.
Description
The event that the user did not do anything in specified time was record.
Parameters
Parameter Name
Parameter Meaning
user-name
Username.
ip-address
IP address
Possible Causes
The user did not do anything in specified time
Procedure
----End
Issue 07 (2014-07-30)

1013

Log Reference
91 SMLK
91
SMLK
About This Chapter

91.1 SMLK/4/MTLK_STATUS_LOG
91.2 SMLK/4/SMLK_CMD_LOG
91.3 SMLK/4/SMLK_FLUSH_LOG
91.5 SMLK/4/SMLK_STATUS_LOG
91.6 SMLK/6/SMLK_EVENT_LOG
91.9 SMLK/6/SMLK_FSM_LOG
Issue 07 (2014-07-30)

1014

Log Reference
91 SMLK
91.1 SMLK/4/MTLK_STATUS_LOG
Message
SMLK/4/MTLK_STATUS_LOG:The state of monitor link group [mtlkgroup-id] changed to
[mtlkgroup-state].
Description
The status of the monitor link group changes.
Parameters
Parameter Name
Parameter Meaning
[mtlkgroup-id]
MTLK group ID.
[mtlkgroup-state]
MTLK group status

l DOWNLINKCLOSE
l DOWNLINKOPEN
Possible Causes
The MTLK status changes.
Procedure
----End
91.2 SMLK/4/SMLK_CMD_LOG
Message
SMLK/4/SMLK_CMD_LOG:The Smart link group [smlkgroup-id] config [config-type], flow
may be interrupted.
Description
The configuration traffic of the smart link group may be interrupted.
Parameters
Parameter Name
Parameter Meaning
[smlkgroup-id]
SMLK group ID
Issue 07 (2014-07-30)

1015

Log Reference
91 SMLK
Parameter Name
Parameter Meaning
[config-type]
configuration type
l LOCK
l FORCE
Possible Causes
A lock or force is configured.
Procedure
----End
Message
SMLK/4/SMLK_FLUSH_LOG:The tag [vlan-id] flush packet from port [port-name] was dealt
successfully.
Description
The flush packets received from a port are processed.
Parameters
Parameter Name
Parameter Meaning
[vlan-id]
VLAN ID
[port-name]
port name
Possible Causes
The flush packets received from a port are processed.
Procedure
----End
Issue 07 (2014-07-30)

1016

Log Reference
91 SMLK
Message
SMLK/4/SMLK_FLUSH_LOG:Port [port name] was attacked by flush message.
Description
The smart link port receive two flush packets within 5 seconds,it may be a flush attack.
Parameters
Parameter Name
Parameter Meaning
[port name]
Port name
Possible Causes
The smart link port receive two flush packets within 5 seconds.
Procedure
----End
91.5 SMLK/4/SMLK_STATUS_LOG
Message
SMLK/4/SMLK_STATUS_LOG:The state of Smart link group [smlkgroup-id] changed to
[smlkgroup-state].
Description
The status of the smart link group changes.
Parameters
Parameter Name
Parameter Meaning
[smlkgroup-id]
SMLK group ID
Issue 07 (2014-07-30)

1017

Log Reference
91 SMLK
Parameter Name
Parameter Meaning
[smlkgroup-state]
SMLK group status

l IDLE
l INIT
l MASTER
l SLAVE
Possible Causes
The SMLK status changes.
Procedure
----End
Message
SMLK/6/SMLK_EVENT_LOG:The Smart Link group [ULONG] send QuickSwitch
information to Broad [ULONG] for [STRING].
Description
The smart link group sends a quick switch message to an interface board.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the index of the smart link group.
[ULONG]
Possible Causes
The smart link group sends a quick switch message to an interface board.
Procedure
Step 1
----End
Issue 07 (2014-07-30)

1018

Log Reference
91 SMLK
Message
SMLK/6/SMLK_EVENT_LOG:Port [STRING]'s ifpdt memory has been clear from [STRING]
group [ULONG] as [STRING] in function [STRING].
Description
Port memory is cleared.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the port name.
[STRING]
Indicates the smart link group name.
[ULONG]
[STRING]
Indicates the interface status: master or slave.
[STRING]
Indicates the function name.
Possible Causes
Port memory is cleared.
Procedure
----End
Message
SMLK/6/SMLK_EVENT_LOG:Port [STRING]'s ifpdt memory has been set to [STRING]
group [ULONG] as [STRING] in function [STRING].
Description
A memory block is used for the smart link group data.
Issue 07 (2014-07-30)

1019

Log Reference
91 SMLK
Parameters
Parameter Name
Parameter Meaning
[STRING]
[STRING]
[ULONG]
Indicates the smart link group index.
[STRING]
[STRING]
Possible Causes
A memory block is used for the smart link group data.
Procedure
Step 1
----End
91.9 SMLK/6/SMLK_FSM_LOG
Message
SMLK/6/SMLK_FSM_LOG:The Smart link group [ULONG]'s CurrentState is [STRING],
TransEvent is [STRING].
Description
The smart link group status changes.
Parameters
[ULONG]
[STRING]
IDLE/INIT/MASTER/SLAVE
[STRING]
Smart Link Enable/Smart Link Disable/Master Link Down/Master Link

Up/Slave Link Down/Slave Link Up/Add Master Port/Add Slave Port/
Delete Master Port/Delete Slave Port/Undo Lock/Undo Force Lock/Force
Manual/Timer Expired/Unkown cause
[STRING]
[STRING]
Issue 07 (2014-07-30)

1020

Log Reference
91 SMLK

[ULONG]
[STRING]
[STRING]
Possible Causes
The following events may occur:
l
Smart Link Enable
Smart Link Disable
Master Link Down
Master Link Up
Slave Link Down
Slave Link Up
Add Master Port
Add Slave Port
Delete Master Port
Delete Slave Port
Undo Lock
Undo Force Lock
Force Manual
Timer Expired
Unknown cause
Procedure
----End
Issue 07 (2014-07-30)

1021

Log Reference
92 SNMP
92
SNMP
About This Chapter

92.1 SNMP/6/SNMP_CNFM_CHANGEUDPORT
92.2 SNMP/6/CNFM_VERSION_DISABLE
92.3 SNMP/4/SNMP_SET
92.4 SNMP/4/SNMP_FAIL
92.5 SNMP/6/TRAPCMDRECORD_YES
92.6 SNMP/6/TRAPCMDRECORD_NO
Issue 07 (2014-07-30)

1022

Log Reference
92 SNMP
92.1 SNMP/6/SNMP_CNFM_CHANGEUDPORT
Message
SNMP/6/SNMP_CNFM_CHANGEUDPORT: When being asked whether to execute the
command "[command]", the user chose [Y/N].
Description
The user chose yes or no when being prompted whether to execute a command.
Parameters
Parameter Name
Parameter Meaning
[command]
The command snmp-agent udp-port is executed
[Y/N]
Whether to execute a command or not
Possible Causes
The user confirmed whether execute a command or not.
Procedure
Step 1 The log is informational only, and no action is required.
----End
92.2 SNMP/6/CNFM_VERSION_DISABLE
Message
SNMP/6/CNFM_VERSION_DISABLE:The user chose [Y/N] when deciding whether to
disable all SNMP versions.
Description
The user decided whether to disable all SNMP versions.
Issue 07 (2014-07-30)

1023

Log Reference
92 SNMP
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Indicates the character input by the user to confirm the action.

l Indicates that all SNMP versions need be disabled.
l Indicates that SNMP versions need not be all disabled.
Possible Causes
The user need decide whether to disable all SNMP versions before the command was performed.
Procedure
----End
92.3 SNMP/4/SNMP_SET
Message
SNMP/4/SNMP_SET:MIB node set. (UserName=[STRING], SourceIP=[STRING], Version=
[STRING], RequestId=[ULONG], ErrorStatus=[ULONG], ErrorIndex=[ULONG], [STRING])
Description
The MIB object was set.
Parameters
UserName
Indicates the name of user.
SourceIP
Version
Indicates the version.
RequestId
Indicates the ID of a request.
Issue 07 (2014-07-30)

1024

Log Reference
92 SNMP

ErrorStatus
Indicates error status, including:

l 0: noError
l 1: tooBig
l 2: noSuchName
l 3: badValue
l 4: readOnly
l 5: genError
l 6: noAccess
l 7: wrongType
l 8: wrongLength
l 9: wrongEncoding
l 10: wrongValue
l 11: noCreation
l 12: inconsistentValue
l 13: resourceUnavailable
l 14: commitFailed
l 15: undoFailed
l 16: authorizationError
l 17: notWritable
l 18: inconsistentName
ErrorIndex
Indicates the index of a variable that fails to be set. This log records all
variables that need to be set by the NMS. For example, if the fifth variable
fails to be set, the value of ErrorIndex is 5.
[STRING]
Indicates the name of set operation.
Possible Causes
The information about the SET operation on an MIB object was recorded into the log.
Procedure
----End
92.4 SNMP/4/SNMP_FAIL
Message
SNMP/4/SNMP_FAIL:Failed to login through SNMP. (Ip=[STRING], Times=[ULONG],
Reason=[STRING])
Issue 07 (2014-07-30)

1025

Log Reference
92 SNMP
Description
An SNMP user failed to log in to the system. Then the IP address and login times were recorded.
Parameters
Parameter Name
Parameter Meaning
Ip
Times
Indicates times of login failures.
Reason
Indicates causes for login failures.
Possible Causes
The SNMP user failed to log in to the system because a wrong community name was used.
Procedure
Step 1 Run the snmp community command to configure the correct community name.
----End
92.5 SNMP/6/TRAPCMDRECORD_YES
Message
SNMP/6/TRAPCMDRECORD_YES:When being asked whether to commit the command
"[STRING]", the user chose Y.
Description
The user chose Y when the system prompted the user to confirm whether to execute a global
SNMP trap command.
Parameters
Parameter Name
Parameter Meaning
STRING
Indicates the command that needs to be confirmed by the user.
Possible Causes
The user chose Y when the system prompted the user to confirm whether to execute a global
SNMP trap command.
Issue 07 (2014-07-30)

1026

Log Reference
92 SNMP
Procedure
----End
92.6 SNMP/6/TRAPCMDRECORD_NO
Message
SNMP/6/TRAPCMDRECORD_NO:When being asked whether to commit the command
"[STRING]", the user chose N.
Description
The user chose N when the system prompted the user to confirm whether to execute a global
SNMP trap command.
Parameters
Parameter Name
Parameter Meaning
STRING
Indicates the command that needs to be confirmed by the user.
Possible Causes
The user chose N when the system prompted the user to confirm whether to execute a global
SNMP trap command.
Procedure
----End
Issue 07 (2014-07-30)

1027

Log Reference
93 SNPG
93
SNPG
About This Chapter

93.1 SNPG/6/BGPPWBDWEXD
93.2 SNPG/6/BGPPWBDWEXDCFG
93.3 SNPG/6/BGPPWCHNLBDWEXD
93.4 SNPG/6/BGPPWCHNLBDWEXDCFG
93.5 SNPG/6/BGPPWCHNLCNTEXDCFG
93.6 SNPG/6/BGPPWCNTEXD
93.7 SNPG/6/BGPPWCNTEXDCFG
93.8 SNPG/6/GLBBDWEXD
93.9 SNPG/6/GLBBDWEXDCFG
93.10 SNPG/6/GLBCHNLBDWEXD
93.11 SNPG/6/GLBCHNLBDWEXDCFG
93.12 SNPG/6/GLBCHNLCNTEXD
93.13 SNPG/6/GLBCHNLCNTEXDCFG
93.14 SNPG/6/GLBCNTEXD
93.15 SNPG/6/GLBCNTEXDCFG
93.16 SNPG/6/GLOBALCHANNELDENY
93.17 SNPG/6/LDPPWBDWEXD
93.18 SNPG/6/LDPPWBDWEXDCFG
93.19 SNPG/6/LDPPWCHNLBDWEXD
93.20 SNPG/6/LDPPWCHNLBDWEXDCFG
Issue 07 (2014-07-30)

1028

Log Reference
93 SNPG
93.21 SNPG/6/LDPPWCHNLCNTEXD
93.22 SNPG/6/LDPPWCHNLCNTEXDCFG
93.23 SNPG/6/LDPPWCNTEXD
93.24 SNPG/6/LDPPWCNTEXDCFG
93.25 SNPG/6/PORTBDWEXD
93.26 SNPG/6/PORTBDWEXDCFG
93.27 SNPG/6/PORTCHNLBDWEXD
93.28 SNPG/6/PORTCHNLBDWEXDCFG
93.29 SNPG/6/PORTCHNLCNTEXD
93.30 SNPG/6/PORTCHNLCNTEXDCFG
93.31 SNPG/6/PORTCNTEXD
93.32 SNPG/6/PORTCNTEXDCFG
93.33 SNPG/6/PORTVLANBDWEXD
93.34 SNPG/6/PORTVLANBDWEXDCFG
93.35 SNPG/6/PORTVLANCHBDWEXDCFG
93.36 SNPG/6/PORTVLANCHCNTEXDCFG
93.37 SNPG/6/PORTVLANCHNLBDWEXD
93.38 SNPG/6/PORTVLANCHNLCNTEXD
93.39 SNPG/6/PORTVLANCNTEXD
93.40 SNPG/6/PORTVLANCNTEXDCFG
93.41 SNPG/6/QINQBDWEXDCFG
93.42 SNPG/6/QINQCHNLBDWEXDCFG
93.43 SNPG/6/QINQCHNLCNTEXDCFG
93.44 SNPG/6/QINQCNTEXDCFG
93.45 SNPG/6/QINQIFBDWEXD
93.46 SNPG/6/QINQIFCHNLBDWEXD
93.47 SNPG/6/QINQIFCHNLCNTEXD
93.48 SNPG/6/QINQIFCNTEXD
93.49 SNPG/6/SUBIFBDWEXD
93.50 SNPG/6/SUBIFBDWEXDCFG
93.51 SNPG/6/SUBIFCHNLBDWEXD
93.52 SNPG/6/SUBIFCHNLBDWEXDCFG
Issue 07 (2014-07-30)

1029

Log Reference
93 SNPG
93.53 SNPG/6/SUBIFCHNLCNTEXD
93.54 SNPG/6/SUBIFCHNLCNTEXDCFG
93.55 SNPG/6/SUBIFCNTEXD
93.56 SNPG/6/SUBIFCNTEXDCFG
93.57 SNPG/6/VLANBDWEXD
93.58 SNPG/6/VLANBDWEXDCFG
93.59 SNPG/6/VLANCHANNELDENY
93.60 SNPG/6/VLANCHNLBDWEXD
93.61 SNPG/6/VLANCHNLBDWEXDCFG
93.62 SNPG/6/VLANCHNLCNTEXD
93.63 SNPG/6/VLANCHNLCNTEXDCFG
93.64 SNPG/6/VLANCNTEXD
93.65 SNPG/6/VLANCNTEXDCFG
93.66 SNPG/6/VSIBDWEXD
93.67 SNPG/6/VSIBDWEXDCFG
93.68 SNPG/6/VSICHANNELDENY
93.69 SNPG/6/VSICHNLBDWEXD
93.70 SNPG/6/VSICHNLBDWEXDCFG
93.71 SNPG/6/VSICHNLCNTEXD
93.72 SNPG/6/VSICHNLCNTEXDCFG
93.73 SNPG/6/VSICNTEXD
93.74 SNPG/6/VSICNTEXDCFG
Issue 07 (2014-07-30)

1030

Log Reference
93 SNPG
93.1 SNPG/6/BGPPWBDWEXD
Message
SNPG/6/BGPPWBDWEXD:The bandwidth of multicast groups reached the upper limit.
(RemoteSiteId=[INTEGER], ConfiguredValue=[INTEGER], CurrentMulticastGroup=
[STRING])
Description
New Join messages were received after the bandwidth of multicast groups on the PW reached
the upper limit.
Parameters
Parameter Name
Parameter Meaning
RemoteSiteId
Remote site ID
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the PW
CurrentMulticastGroup
Multicast group address of the denied Join message
Possible Causes
The bandwidth of multicast groups on the PW reached the upper limit.
Procedure
----End
93.2 SNPG/6/BGPPWBDWEXDCFG
Message
SNPG/6/BGPPWBDWEXDCFG:The bandwidth of multicast groups has already exceeded the
limit configured. (RemoteSiteId=[INTEGER], ConfiguredValue=[INTEGER],
StatisticsValue=[INTEGER])
Description
The bandwidth of current multicast groups on the BGP PW exceeded the upper limit.
Issue 07 (2014-07-30)

1031

Log Reference
93 SNPG
Parameters
Parameter Name
Parameter Meaning
RemoteSiteId
Remote site ID
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the BGP PW
StatisticsValue
Bandwidth of current multicast groups on the BGP PW
Possible Causes
The bandwidth of current multicast groups on the BGP PW exceeded the upper limit.
Procedure
Step 1 This log message is informational only, and no action is required. Alternatively, you can run the
undo l2-multicast dynamic-group group-address group-address command to delete some
dynamic multicast groups forcibly.
----End
93.3 SNPG/6/BGPPWCHNLBDWEXD
Message
SNPG/6/BGPPWCHNLBDWEXD:The bandwidth of multicast groups reached the upper limit.
(ChannelName=[STRING], RemoteSiteId=[INTEGER], ConfiguredValue=[INTEGER],
CurrentMulticastGroup=[STRING])
Description
New Join messages were received after the bandwidth of multicast groups in the channel on the
PW reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
RemoteSiteId
Remote site ID
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the channel on

the PW
CurrentMulticastGroup Multicast group address of the denied Join message
Possible Causes
The bandwidth of multicast groups in the channel on the PW reached the upper limit.
Issue 07 (2014-07-30)

1032

Log Reference
93 SNPG
Procedure
----End
93.4 SNPG/6/BGPPWCHNLBDWEXDCFG
Message
SNPG/6/BGPPWCHNLBDWEXDCFG:The bandwidth of multicast groups has already
exceeded the limit configured. (ChannelName=[STRING], RemoteSiteId=[INTEGER],
ConfiguredValue=[INTEGER], StatisticsValue=[INTEGER])
Description
The bandwidth of current multicast groups in the channel on the BGP PW exceeded the upper
limit.
Parameters
ChannelName
Channel name
RemoteSiteId
Remote site ID
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the channel on the

BGP PW
StatisticsValue
Bandwidth of current multicast groups in the channel on the BGP PW
Possible Causes
The bandwidth of current multicast groups in the channel on the BGP PW exceeded the upper
limit.
Procedure
----End
93.5 SNPG/6/BGPPWCHNLCNTEXDCFG
Message
SNPG/6/BGPPWCHNLCNTEXDCFG:The number of multicast groups has already exceeded
the limit configured. (ChannelName=[STRING], RemoteSiteId=[INTEGER],
Issue 07 (2014-07-30)

1033

Log Reference
93 SNPG
Description
The number of current multicast groups in the channel on the BGP PW exceeded the upper limit.
Parameters
ChannelName
Channel name
RemoteSiteId
Remote site ID
ConfiguredValue
Upper limit of the number of multicast groups in the channel on the BGP
PW
StatisticsValue
Number of current multicast groups in the channel on the BGP PW
Possible Causes
The number of current multicast groups in the channel on the BGP PW exceeded the upper limit.
Procedure
----End
93.6 SNPG/6/BGPPWCNTEXD
Message
SNPG/6/BGPPWCNTEXD:The number of multicast groups reached the upper limit.
(RemoteSiteId=[INTEGER], ConfiguredValue=[INTEGER], CurrentMulticastGroup=
[STRING])
Description
New Join messages were received after the number of multicast groups on the PW reached the
upper limit.
Parameters
Parameter Name
Parameter Meaning
RemoteSiteId
Remote site ID
ConfiguredValue
Upper limit of the number of multicast groups on the PW
Issue 07 (2014-07-30)

1034

Log Reference
93 SNPG
Possible Causes
The number of multicast groups on the PW reached the upper limit.
Procedure
----End
93.7 SNPG/6/BGPPWCNTEXDCFG
Message
SNPG/6/BGPPWCNTEXDCFG:The number of multicast groups has already exceeded the limit
configured. (RemoteSiteId=[INTEGER], ConfiguredValue=[INTEGER], StatisticsValue=
[INTEGER])
Description
The number of current multicast groups on the BGP PW exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
RemoteSiteId
Remote site ID
ConfiguredValue
Upper limit of the number of multicast groups on the BGP PW
StatisticsValue
Number of current multicast groups on the BGP PW
Possible Causes
The number of current multicast groups on the BGP PW exceeded the upper limit.
Procedure
----End
93.8 SNPG/6/GLBBDWEXD
Message
SNPG/6/GLBBDWEXD:The bandwidth of multicast groups reached the upper limit.
(ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING])
Issue 07 (2014-07-30)

1035

Log Reference
93 SNPG
Description
New Join messages were received after the bandwidth of multicast groups reached the globally
configured upper limit.
Parameters
Parameter Name
Parameter Meaning
ConfiguredValue
Globally configured upper limit of the bandwidth of multicast groups
Possible Causes
The bandwidth of multicast groups reached the globally configured upper limit.
Procedure
----End
93.9 SNPG/6/GLBBDWEXDCFG
Message
SNPG/6/GLBBDWEXDCFG:The bandwidth of multicast groups has already exceeded the limit
configured. (ConfiguredValue=[INTEGER], StatisticsValue=[INTEGER])
Description
The bandwidth of current multicast groups exceeded the globally configured upper limit.
Parameters
ConfiguredValue
StatisticsValue
Bandwidth of current multicast groups
Possible Causes
The bandwidth of current multicast groups exceeded the globally configured upper limit.
Procedure
----End
Issue 07 (2014-07-30)

1036

Log Reference
93 SNPG
93.10 SNPG/6/GLBCHNLBDWEXD
Message
SNPG/6/GLBCHNLBDWEXD:The bandwidth of multicast groups reached the upper limit.
(ChannelName=[STRING], ConfiguredValue=[INTEGER], CurrentMulticastGroup=
[STRING])
Description
New Join messages were received after the bandwidth of multicast groups in the current channel
reached the globally configured upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
ConfiguredValue

in the channel
Possible Causes
The bandwidth of multicast groups in the current channel reached the globally configured upper
limit.
Procedure
----End
93.11 SNPG/6/GLBCHNLBDWEXDCFG
Message
SNPG/6/GLBCHNLBDWEXDCFG:The bandwidth of multicast groups has already exceeded
the limit configured. (ChannelName=[STRING], ConfiguredValue=[INTEGER],
Description
The bandwidth of current multicast groups in the channel exceeded the globally configured upper
limit.
Issue 07 (2014-07-30)

1037

Log Reference
93 SNPG
Parameters
ChannelName
Channel name
ConfiguredValue
Globally configured upper limit of the bandwidth of multicast groups in

the channel
StatisticsValue
Bandwidth of current multicast groups in the channel
Possible Causes
The bandwidth of current multicast groups in the channel exceeded the globally configured upper
limit.
Procedure
----End
93.12 SNPG/6/GLBCHNLCNTEXD
Message
SNPG/6/GLBCHNLCNTEXD:The number of multicast groups reached the upper limit.
(ChannelName=[STRING], ConfiguredValue=[INTEGER], CurrentMulticastGroup=
[STRING])
Description
New Join messages were received after the number of multicast groups in the current channel
reached the globally configured upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
ConfiguredValue
Globally configured upper limit of the number of multicast groups in

the channel
Possible Causes
The number of multicast groups in the current channel reached the globally configured upper
limit.
Issue 07 (2014-07-30)

1038

Log Reference
93 SNPG
Procedure
----End
93.13 SNPG/6/GLBCHNLCNTEXDCFG
Message
SNPG/6/GLBCHNLCNTEXDCFG:The number of multicast groups has already exceeded the
limit configured. (ChannelName=[STRING] , ConfiguredValue=[INTEGER], StatisticsValue=
[INTEGER])
Description
The number of current multicast groups in the channel exceeded the globally configured upper
limit.
Parameters
ChannelName
Channel name
ConfiguredValue
Globally configured upper limit of the number of multicast groups in the

channel
StatisticsValue
Number of current multicast groups in the channel
Possible Causes
The number of current multicast groups in the channel exceeded the globally configured upper
limit.
Procedure
----End
93.14 SNPG/6/GLBCNTEXD
Message
SNPG/6/GLBCNTEXD:The number of multicast groups reached the upper limit.
(ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING])
Issue 07 (2014-07-30)

1039

Log Reference
93 SNPG
Description
New Join messages were received after the number of multicast groups reached the globally
configured upper limit.
Parameters
Parameter Name
Parameter Meaning
ConfiguredValue
Globally configured upper limit of the number of multicast groups
Possible Causes
The number of learnt multicast groups reached the globally configured upper limit.
Procedure
----End
93.15 SNPG/6/GLBCNTEXDCFG
Message
SNPG/6/GLBCNTEXDCFG:The number of multicast groups has already exceeded the limit
configured. (ConfiguredValue=[INTEGER], StatisticsValue=[INTEGER])
Description
The number of current multicast groups exceeded the globally configured upper limit.
Parameters
Parameter Name
Parameter Meaning
ConfiguredValue
Globally configured upper limit of the number of multicast groups
StatisticsValue
Number of current multicast groups
Possible Causes
The number of current multicast groups exceeded the globally configured upper limit.
Procedure
----End
Issue 07 (2014-07-30)

1040

Log Reference
93 SNPG
93.16 SNPG/6/GLOBALCHANNELDENY
Message
SNPG/6/GLOBALCHANNELDENY:The unspecified-channel deny configuration exists in
global channel. (CurrentMulticastGroup=[STRING])
Description
Join messages for an unknown multicast group in the channel were received after the
unspecified-channel deny command is configured for the global channels.
Parameters
Parameter Name
Parameter Meaning
Possible Causes
unspecified-channel deny command is configured for the global channels.
Procedure
----End
93.17 SNPG/6/LDPPWBDWEXD
Message
SNPG/6/LDPPWBDWEXD:The bandwidth of multicast groups reached the upper limit. (PwId=
[INTEGER], RemoteIpAddress=[STRING], ConfiguredValue=[INTEGER],
Description
New Join messages were received after the bandwidth of multicast groups on the PW reached
the upper limit.
Issue 07 (2014-07-30)

1041

Log Reference
93 SNPG
Parameters
Parameter Name
Parameter Meaning
PwId
PW ID
RemoteIpAddress
Remote IP address
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the PW
Possible Causes
The bandwidth of multicast groups on the PW reached the upper limit.
Procedure
----End
93.18 SNPG/6/LDPPWBDWEXDCFG
Message
SNPG/6/LDPPWBDWEXDCFG:The bandwidth of multicast groups has already exceeded the
limit configured. (PwId=[INTEGER], RemoteIpAddress=[STRING], ConfiguredValue=
[INTEGER], StatisticsValue=[INTEGER])
Description
The bandwidth of current multicast groups on the LDP PW exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
PwId
PW ID
RemoteIpAddress
Remote IP address
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the LDP PW
StatisticsValue
Bandwidth of current multicast groups on the LDP PW
Possible Causes
Issue 07 (2014-07-30)

1042

Log Reference
93 SNPG
Procedure
----End
93.19 SNPG/6/LDPPWCHNLBDWEXD
Message
SNPG/6/LDPPWCHNLBDWEXD:The bandwidth of multicast groups reached the upper limit.
(ChannelName=[STRING], PwId=[INTEGER], RemoteIpAddress=[STRING],
ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING])
Description
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
PwId
PW ID
RemoteIpAddress
Remote IP address
ConfiguredValue

the PW
Possible Causes
The bandwidth of multicast groups in the channel on the PW reached the upper limit.
Procedure
----End
93.20 SNPG/6/LDPPWCHNLBDWEXDCFG
Issue 07 (2014-07-30)

1043

Log Reference
93 SNPG
Message
SNPG/6/LDPPWCHNLBDWEXDCFG:The bandwidth of multicast groups has already
exceeded the limit configured. (ChannelName=[STRING], PwId=[INTEGER],
RemoteIpAddress=[STRING], ConfiguredValue=[INTEGER], StatisticsValue=[INTEGER])
Description
The bandwidth of current multicast groups in the channel on the LDP PW exceeded the upper
limit.
Parameters
ChannelName
Channel name
PwId
PW ID
RemoteIpAddress
Remote IP address
ConfiguredValue

LDP PW
StatisticsValue
Bandwidth of current multicast groups in the channel on the LDP PW
Possible Causes
Procedure
----End
93.21 SNPG/6/LDPPWCHNLCNTEXD
Message
SNPG/6/LDPPWCHNLCNTEXD:The number of multicast groups reached the upper limit.
(ChannelName=[STRING], PwId=[INTEGER], RemoteIpAddress=[STRING],
Description
New Join messages were received after the number of multicast groups in the channel on the
Issue 07 (2014-07-30)

1044

Log Reference
93 SNPG
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
PwId
PW ID
RemoteIpAddress
Remote IP address
ConfiguredValue
Upper limit of the number of multicast groups in the channel on the

PW
Possible Causes
The number of multicast groups in the channel on the PW reached the upper limit.
Procedure
----End
93.22 SNPG/6/LDPPWCHNLCNTEXDCFG
Message
SNPG/6/LDPPWCHNLCNTEXDCFG:The number of multicast groups has already exceeded
the limit configured. (ChannelName=[STRING], PwId=[INTEGER], RemoteIpAddress=
[STRING], ConfiguredValue=[INTEGER], StatisticsValue=[INTEGER])
Description
The number of current multicast groups in the channel on the LDP PW exceeded the upper limit.
Parameters
ChannelName
Channel name
PwId
PW ID
RemoteIpAddress
Remote IP address
ConfiguredValue
Upper limit of the number of multicast groups in the channel on the LDP
PW
StatisticsValue
Number of current multicast groups in the channel on the LDP PW
Issue 07 (2014-07-30)

1045

Log Reference
93 SNPG
Possible Causes
The number of current multicast groups in the channel on the LDP PW exceeded the upper limit.
Procedure
----End
93.23 SNPG/6/LDPPWCNTEXD
Message
SNPG/6/LDPPWCNTEXD:The number of multicast groups reached the upper limit. (PwId=
[INTEGER], RemoteIpAddress=[STRING], ConfiguredValue=[INTEGER],
Description
New Join messages were received after the number of multicast groups on the PW reached the
upper limit.
Parameters
Parameter Name
Parameter Meaning
PwId
PW ID
RemoteIpAddress
Remote IP address
ConfiguredValue
Upper limit of the number of multicast groups on the PW
Possible Causes
The number of multicast groups on the PW reached the upper limit.
Procedure
----End
93.24 SNPG/6/LDPPWCNTEXDCFG
Issue 07 (2014-07-30)

1046

Log Reference
93 SNPG
Message
SNPG/6/LDPPWCNTEXDCFG:The number of multicast groups has already exceeded the limit
configured. (PwId=[INTEGER], RemoteIpAddress=[STRING], ConfiguredValue=
Description
The number of current multicast groups on the LDP PW exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
PwId
PW ID
RemoteIpAddress
Remote IP address
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the LDP PW
StatisticsValue
Number of current multicast groups on the LDP PW
Possible Causes
The number of current multicast groups on the LDP PW exceeded the upper limit.
Procedure
----End
93.25 SNPG/6/PORTBDWEXD
Message
SNPG/6/PORTBDWEXD:The bandwidth of multicast groups reached the upper limit.
(IfName=[STRING], ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING])
Description
New Join messages were received after the bandwidth of multicast groups on an interface
reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
IfName
Layer 2 interface
Issue 07 (2014-07-30)

1047

Log Reference
93 SNPG
Parameter Name
Parameter Meaning
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the Layer 2

interface
Possible Causes
New Join messages were received after the bandwidth of multicast groups learnt by an interface
Procedure
----End
93.26 SNPG/6/PORTBDWEXDCFG
Message
SNPG/6/PORTBDWEXDCFG:The bandwidth of multicast groups has already exceeded the
limit configured. (IfName=[STRING], ConfiguredValue=[INTEGER], StatisticsValue=
[INTEGER])
Description
The bandwidth of current multicast groups on the Layer 2 interface exceeded the upper limit.
Parameters
IfName
Name of the Layer 2 interface
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the Layer 2 interface
StatisticsValue
Bandwidth of current multicast groups on the Layer 2 interface
Possible Causes
The bandwidth of current multicast groups on the Layer 2 interface exceeded the upper limit.
Procedure
----End
Issue 07 (2014-07-30)

1048

Log Reference
93 SNPG
93.27 SNPG/6/PORTCHNLBDWEXD
Message
SNPG/6/PORTCHNLBDWEXD:The bandwidth of multicast groups reached the upper limit.
(ChannelName=[STRING], IfName=[STRING], ConfiguredValue=[INTEGER],
Description
interface reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
IfName
Layer 2 interface
ConfiguredValue

the Layer 2 interface
Possible Causes
The bandwidth of multicast groups in the channel on the interface reached the upper limit.
Procedure
----End
93.28 SNPG/6/PORTCHNLBDWEXDCFG
Message
SNPG/6/PORTCHNLBDWEXDCFG:The bandwidth of multicast groups has already exceeded
the limit configured. (ChannelName=[STRING], IfName=[STRING], ConfiguredValue=
Description
The bandwidth of current multicast groups in the channel on the Layer 2 interface exceeded the
upper limit.
Issue 07 (2014-07-30)

1049

Log Reference
93 SNPG
Parameters
ChannelName
Channel name
IfName
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the Layer 2 interface
StatisticsValue
Bandwidth of current multicast groups in the channel on the Layer 2

interface
Possible Causes
The bandwidth of current multicast groups in the channel on the Layer 2 interface exceeded the
upper limit.
Procedure
----End
93.29 SNPG/6/PORTCHNLCNTEXD
Message
SNPG/6/PORTCHNLCNTEXD:The number of multicast groups reached the upper limit.
Description
interface reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
IfName
Layer 2 interface
ConfiguredValue

Layer 2 interface
Possible Causes
The number of multicast groups in the channel on the interface reached the upper limit.
Issue 07 (2014-07-30)

1050

Log Reference
93 SNPG
Procedure
----End
93.30 SNPG/6/PORTCHNLCNTEXDCFG
Message
SNPG/6/PORTCHNLCNTEXDCFG:The number of multicast groups has already exceeded the
limit configured. (ChannelName=[STRING], IfName=[STRING], ConfiguredValue=
Description
The number of current multicast groups in the channel on the Layer 2 interface exceeded the
upper limit.
Parameters
ChannelName
Channel name
IfName
ConfiguredValue
Upper limit of the number of multicast groups in the channel on the Layer
2 interface
StatisticsValue
Number of current multicast groups in the channel on the Layer 2 interface
Possible Causes
The number of current multicast groups in the channel on the Layer 2 interface exceeded the
upper limit.
Procedure
----End
93.31 SNPG/6/PORTCNTEXD
Message
SNPG/6/PORTCNTEXD:The number of multicast groups reached the upper limit. (IfName=
[STRING], ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING])
Issue 07 (2014-07-30)

1051

Log Reference
93 SNPG
Description
New Join messages were received after the number of multicast groups on an interface reached
the upper limit.
Parameters
Parameter Name
Parameter Meaning
IfName
Layer 2 interface
ConfiguredValue
Upper limit of the number of multicast groups on the Layer 2 interface
Possible Causes
The number of multicast groups learnt by the interface reached the upper limit.
Procedure
----End
93.32 SNPG/6/PORTCNTEXDCFG
Message
SNPG/6/PORTCNTEXDCFG:The number of multicast groups has already exceeded the limit
configured. (IfName=[STRING], ConfiguredValue=[INTEGER], StatisticsValue=
[INTEGER])
Description
The number of current multicast groups on the Layer 2 interface exceeded the upper limit.
Parameters
IfName
ConfiguredValue
Upper limit of the number of multicast groups on the Layer 2 interface
StatisticsValue
Number of current multicast groups on the Layer 2 interface
Possible Causes
The number of current multicast groups on the Layer 2 interface exceeded the upper limit.
Issue 07 (2014-07-30)

1052

Log Reference
93 SNPG
Procedure
----End
93.33 SNPG/6/PORTVLANBDWEXD
Message
SNPG/6/PORTVLANBDWEXD:The bandwidth of multicast groups reached the upper limit.
(VlanId=[INTEGER], IfName=[STRING], ConfiguredValue=[INTEGER],
Description
New Join messages were received after the bandwidth of multicast groups on the interface in
the specified VLAN reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
VlanId
VLAN ID
IfName
Layer 2 interface
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the interface in

the specified VLAN
Possible Causes
The bandwidth of multicast groups on the interface in the specified VLAN reached the upper
limit.
Procedure
----End
93.34 SNPG/6/PORTVLANBDWEXDCFG
Message
SNPG/6/PORTVLANBDWEXDCFG:The bandwidth of multicast groups has already exceeded
the limit configured. (VlanId=[INTEGER], IfName=[STRING], ConfiguredValue=
Issue 07 (2014-07-30)

1053

Log Reference
93 SNPG
Description
The bandwidth of current multicast groups on the interface in the specified VLAN exceeded the
upper limit.
Parameters
VlanId
VLAN ID
IfName
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the interface in the

specified VLAN
StatisticsValue
Bandwidth of current multicast groups on the interface in the specified

VLAN
Possible Causes
The bandwidth of current multicast groups on the interface in the specified VLAN exceeded the
upper limit.
Procedure
----End
93.35 SNPG/6/PORTVLANCHBDWEXDCFG
Message
SNPG/6/PORTVLANCHBDWEXDCFG:The bandwidth of multicast groups has already
exceeded the limit configured. (ChannelName=[STRING], VlanId=[INTEGER], IfName=
[STRING], ConfiguredValue=[INTEGER], StatisticsValue=[INTEGER])
Description
The bandwidth of current multicast groups in the channel on the interface in the specified VLAN
exceeded the upper limit.
Parameters
ChannelName
Channel name
VlanId
VLAN ID
Issue 07 (2014-07-30)

1054

Log Reference
93 SNPG

IfName
ConfiguredValue

interface in the specified VLAN
StatisticsValue
Bandwidth of current multicast groups in the channel on the interface in

the specified VLAN
Possible Causes
The bandwidth of current multicast groups in the channel on the interface in the specified VLAN
Procedure
----End
93.36 SNPG/6/PORTVLANCHCNTEXDCFG
Message
SNPG/6/PORTVLANCHCNTEXDCFG:The number of multicast groups has already exceeded
the limit configured. (ChannelName=[STRING], VlanId=[INTEGER], IfName=[STRING],
Description
The number of current multicast groups in the channel on the interface in the specified VLAN
Parameters
ChannelName
Channel name
VlanId
VLAN ID
IfName
ConfiguredValue

StatisticsValue
Number of current multicast groups in the channel on the interface in the

specified VLAN
Issue 07 (2014-07-30)

1055

Log Reference
93 SNPG
Possible Causes
The number of current multicast groups in the channel on the interface in the specified VLAN
Procedure
----End
93.37 SNPG/6/PORTVLANCHNLBDWEXD
Message
SNPG/6/PORTVLANCHNLBDWEXD:The bandwidth of multicast groups reached the upper
limit. (ChannelName=[STRING], VlanId=[INTEGER], IfName=[STRING],
Description
interface in the specified VLAN reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
VlanId
VLAN ID
IfName
Layer 2 interface
ConfiguredValue

the interface in the specified VLAN
Possible Causes
The bandwidth of multicast groups in the channel on the interface in the specified VLAN reached
the upper limit.
Procedure
----End
Issue 07 (2014-07-30)

1056

Log Reference
93 SNPG
93.38 SNPG/6/PORTVLANCHNLCNTEXD
Message
SNPG/6/PORTVLANCHNLCNTEXD:The number of multicast groups reached the upper limit.
(ChannelName=[STRING], VlanId=[INTEGER], IfName=[STRING], ConfiguredValue=
[INTEGER], CurrentMulticastGroup=[STRING])
Description
interface in the specified VLAN reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
VlanId
VLAN ID
IfName
Layer 2 interface
ConfiguredValue

Possible Causes
The number of multicast groups in the channel on the interface in the specified VLAN reached
the upper limit.
Procedure
----End
93.39 SNPG/6/PORTVLANCNTEXD
Message
SNPG/6/PORTVLANCNTEXD:The number of multicast groups reached the upper limit.
(VlanId=[INTEGER], IfName=[STRING], ConfiguredValue=[INTEGER],
Issue 07 (2014-07-30)

1057

Log Reference
93 SNPG
Description
New Join messages were received after the number of multicast groups on the interface in the
specified VLAN reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
VlanId
VLAN ID
IfName
Layer 2 interface
ConfiguredValue
Upper limit of the number of multicast groups on the interface in the

specified VLAN
Possible Causes
The number of multicast groups on the interface in the specified VLAN reached the upper limit.
Procedure
----End
93.40 SNPG/6/PORTVLANCNTEXDCFG
Message
SNPG/6/PORTVLANCNTEXDCFG:The number of multicast groups has already exceeded the
limit configured. (VlanId=[INTEGER], IfName=[STRING], ConfiguredValue=[INTEGER],
Description
The number of current multicast groups on the interface in the specified VLAN exceeded the
upper limit.
Parameters
VlanId
VLAN ID
IfName
ConfiguredValue
Upper limit of the number of multicast groups on the interface in the

specified VLAN
Issue 07 (2014-07-30)

1058

Log Reference
93 SNPG

StatisticsValue
Number of current multicast groups on the interface in the specified

VLAN
Possible Causes
The number of current multicast groups on the interface in the specified VLAN exceeded the
upper limit.
Procedure
----End
93.41 SNPG/6/QINQBDWEXDCFG
Message
SNPG/6/QINQBDWEXDCFG:The bandwidth of multicast groups has already exceeded the
[INTEGER])
Description
The bandwidth of multicast groups on the sub-interface for QinQ VLAN tag termination
Parameters
IfName
Name of the sub-interface for QinQ VLAN tag termination
ConfiguredValue
Upper limit of the bandwidth of multicast groups on the sub-interface
StatisticsValue
Statistics about the bandwidth of multicast groups on the sub-interface
Possible Causes
The bandwidth of multicast groups on the sub-interface for QinQ VLAN tag termination
Procedure
----End
Issue 07 (2014-07-30)

1059

Log Reference
93 SNPG
93.42 SNPG/6/QINQCHNLBDWEXDCFG
Message
SNPG/6/QINQCHNLBDWEXDCFG:The bandwidth of multicast groups has already exceeded
the limit configured. (ChannelName=[STRING], IfName=[STRING], ConfiguredValue=
Description
The bandwidth of multicast groups in the channel on the sub-interface for QinQ VLAN tag
termination exceeded the upper limit.
Parameters
ChannelName
Name of the channel
IfName
ConfiguredValue
StatisticsValue
Statistics about the bandwidth of multicast groups on the sub-interface
Possible Causes
The bandwidth of multicast groups in the channel on the sub-interface for QinQ VLAN tag
Procedure
----End
93.43 SNPG/6/QINQCHNLCNTEXDCFG
Message
SNPG/6/QINQCHNLCNTEXDCFG:The number of multicast groups has already exceeded the
Description
The number of multicast groups in the channel on the sub-interface for QinQ VLAN tag
Issue 07 (2014-07-30)

1060

Log Reference
93 SNPG
Parameters
Parameter Name
Parameter Meaning
ChannelName
Name of the channel
IfName
ConfiguredValue
Upper limit of the number of multicast groups on the sub-interface
StatisticsValue
Statistics about the number of multicast groups on the sub-interface
Possible Causes
Procedure
----End
93.44 SNPG/6/QINQCNTEXDCFG
Message
SNPG/6/QINQCNTEXDCFG:The number of multicast groups has already exceeded the limit
[INTEGER])
Description
The number of multicast groups on the sub-interface for QinQ VLAN tag termination exceeded
the upper limit.
Parameters
Parameter Name
Parameter Meaning
IfName
ConfiguredValue
StatisticsValue
Statistics about the number of multicast groups on the sub-interface
Possible Causes
The number of multicast groups on the sub-interface for QinQ VLAN tag termination exceeded
the upper limit.
Issue 07 (2014-07-30)

1061

Log Reference
93 SNPG
Procedure
----End
93.45 SNPG/6/QINQIFBDWEXD
Message
SNPG/6/QINQIFBDWEXD:The bandwidth of multicast groups reached the upper limit.
(IfName=[STRING], ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING],PEVid=[INTEGER], CE-Vid=[INTEGER])
Description
The bandwidth of multicast groups on the sub-interface for QinQ VLAN tag termination reached
the upper limit.
Parameters
Parameter Name
Parameter Meaning
IfName
ConfiguredValue

PE-Vid
Outer VLAN ID
CE-Vid
Inner VLAN ID
Possible Causes
The bandwidth of multicast groups on the sub-interface for QinQ VLAN tag termination reached
the upper limit.
Procedure
----End
93.46 SNPG/6/QINQIFCHNLBDWEXD
Issue 07 (2014-07-30)

1062

Log Reference
93 SNPG
Message
SNPG/6/QINQIFCHNLBDWEXD:The bandwidth of multicast groups reached the upper limit.
CurrentMulticastGroup=[STRING],PE-Vid=[INTEGER], CE-Vid=[INTEGER])
Description
The bandwidth of multicast groups learnt by the sub-interface for QinQ VLAN tag termination
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
IfName
ConfiguredValue

PE-Vid
Outer VLAN ID
CE-Vid
Inner VLAN ID
Possible Causes
The bandwidth of multicast groups learnt by the sub-interface for QinQ VLAN tag termination
Procedure
----End
93.47 SNPG/6/QINQIFCHNLCNTEXD
Message
SNPG/6/QINQIFCHNLCNTEXD:The number of multicast groups reached the upper limit.
CurrentMulticastGroup=[STRING],PE-Vid=[INTEGER], CE-Vid=[INTEGER])
Description
termination reached the upper limit.
Issue 07 (2014-07-30)

1063

Log Reference
93 SNPG
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
IfName
ConfiguredValue

PE-Vid
Outer VLAN ID
CE-Vid
Inner VLAN ID
Possible Causes
termination reached the upper limit.
Procedure
----End
93.48 SNPG/6/QINQIFCNTEXD
Message
SNPG/6/QINQIFCNTEXD:The number of multicast groups reached the upper limit. (IfName=
[STRING], ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING],PE-Vid=
[INTEGER], CE-Vid=[INTEGER])
Description
The number of multicast groups learnt by the sub-interface for QinQ VLAN tag termination
Parameters
Parameter Name
Parameter Meaning
IfName
ConfiguredValue

PE-Vid
Outer VLAN ID
CE-Vid
Inner VLAN ID
Issue 07 (2014-07-30)

1064

Log Reference
93 SNPG
Possible Causes
The number of multicast groups learnt by the sub-interface for QinQ VLAN tag termination
Procedure
----End
93.49 SNPG/6/SUBIFBDWEXD
Message
SNPG/6/SUBIFBDWEXD:The bandwidth of multicast groups reached the upper limit.
(IfName=[STRING], ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING])
Description
New Join messages were received after the bandwidth of multicast groups on the sub-interface
Parameters
Parameter Name
Parameter Meaning
IfName
Sub-interface name
ConfiguredValue
Possible Causes
The bandwidth of multicast groups on the sub-interface reached the upper limit.
Procedure
----End
93.50 SNPG/6/SUBIFBDWEXDCFG
Issue 07 (2014-07-30)

1065

Log Reference
93 SNPG
Message
SNPG/6/SUBIFBDWEXDCFG:The bandwidth of multicast groups has already exceeded the
[INTEGER])
Description
The bandwidth of current multicast groups on the sub-interface exceeded the upper limit.
Parameters
IfName
Sub-interface name
ConfiguredValue
StatisticsValue
Bandwidth of current multicast groups on the sub-interface
Possible Causes
The bandwidth of current multicast groups on the sub-interface exceeded the upper limit.
Procedure
----End
93.51 SNPG/6/SUBIFCHNLBDWEXD
Message
SNPG/6/SUBIFCHNLBDWEXD:The bandwidth of multicast groups reached the upper limit.
Description
sub-interface reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
IfName
Sub-interface name
Issue 07 (2014-07-30)

1066

Log Reference
93 SNPG
Parameter Name
Parameter Meaning
ConfiguredValue

the sub-interface
Possible Causes
The bandwidth of multicast groups in the channel on the sub-interface reached the upper limit.
Procedure
----End
93.52 SNPG/6/SUBIFCHNLBDWEXDCFG
Message
SNPG/6/SUBIFCHNLBDWEXDCFG:The bandwidth of multicast groups has already
exceeded the limit configured. (ChannelName=[STRING], IfName=[STRING],
Description
The bandwidth of current multicast groups in the channel on the sub-interface exceeded the
upper limit.
Parameters
ChannelName
Channel name
IfName
Sub-interface name
ConfiguredValue

sub-interface
StatisticsValue
Bandwidth of current multicast groups in the channel on the sub-interface
Possible Causes
The bandwidth of current multicast groups in the channel on the sub-interface exceeded the
upper limit.
Issue 07 (2014-07-30)

1067

Log Reference
93 SNPG
Procedure
----End
93.53 SNPG/6/SUBIFCHNLCNTEXD
Message
SNPG/6/SUBIFCHNLCNTEXD:The number of multicast groups reached the upper limit.
Description
sub-interface reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
IfName
Sub-interface name
ConfiguredValue

sub-interface
Possible Causes
The number of multicast groups in the channel on the sub-interface reached the upper limit.
Procedure
----End
93.54 SNPG/6/SUBIFCHNLCNTEXDCFG
Message
SNPG/6/SUBIFCHNLCNTEXDCFG:The number of multicast groups has already exceeded the
Issue 07 (2014-07-30)

1068

Log Reference
93 SNPG
Description
The number of current multicast groups in the channel on the sub-interface exceeded the upper
limit.
Parameters
ChannelName
Channel name
IfName
Sub-interface name
ConfiguredValue

sub-interface
StatisticsValue
Number of current multicast groups in the channel on the sub-interface
Possible Causes
The number of current multicast groups in the channel on the sub-interface exceeded the upper
limit.
Procedure
----End
93.55 SNPG/6/SUBIFCNTEXD
Message
SNPG/6/SUBIFCNTEXD:The number of multicast groups reached the upper limit. (IfName=
Description
New Join messages were received after the number of multicast groups on the sub-interface
Parameters
Parameter Name
Parameter Meaning
IfName
Sub-interface name
ConfiguredValue

Issue 07 (2014-07-30)

1069

Log Reference
93 SNPG
Possible Causes
The number of multicast groups on the sub-interface reached the upper limit.
Procedure
----End
93.56 SNPG/6/SUBIFCNTEXDCFG
Message
SNPG/6/SUBIFCNTEXDCFG:The number of multicast groups has already exceeded the limit
[INTEGER])
Description
The number of current multicast groups on the sub-interface exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
IfName
Sub-interface name
ConfiguredValue
StatisticsValue
Number of current multicast groups on the sub-interface
Possible Causes
The number of current multicast groups on the sub-interface exceeded the upper limit.
Procedure
----End
93.57 SNPG/6/VLANBDWEXD
Message
SNPG/6/VLANBDWEXD:The bandwidth of multicast groups reached the upper limit.
(VlanId=[INTEGER], ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING])
Issue 07 (2014-07-30)

1070

Log Reference
93 SNPG
Description
New Join messages were received after the bandwidth of multicast groups in the VLAN reached
the upper limit.
Parameters
Parameter Name
Parameter Meaning
VlanId
VLAN ID
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the VLAN
Possible Causes
The bandwidth of multicast groups in the VLAN reached the upper limit.
Procedure
----End
93.58 SNPG/6/VLANBDWEXDCFG
Message
SNPG/6/VLANBDWEXDCFG:The bandwidth of multicast groups has already exceeded the
limit configured. (VlanId=[INTEGER], ConfiguredValue=[INTEGER], StatisticsValue=
[INTEGER])
Description
The bandwidth of current multicast groups in the VLAN exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
VlanId
VLAN ID
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the VLAN
StatisticsValue
Bandwidth of current multicast groups in the VLAN
Possible Causes
The bandwidth of current multicast groups in the VLAN exceeded the upper limit.
Issue 07 (2014-07-30)

1071

Log Reference
93 SNPG
Procedure
----End
93.59 SNPG/6/VLANCHANNELDENY
Message
SNPG/6/VLANCHANNELDENY:The unspecified-channel deny configuration exists in
VLAN channel. (VlanId=[INTEGER], CurrentMulticastGroup=[STRING])
Description
unspecified-channel deny command is configured for the channel in the VLAN.
Parameters
Parameter Name
Parameter Meaning
VlanId
VLAN ID
Possible Causes
unspecified-channel deny command is configured for the channel in the VLAN.
Procedure
----End
93.60 SNPG/6/VLANCHNLBDWEXD
Message
SNPG/6/VLANCHNLBDWEXD:The bandwidth of multicast groups reached the upper limit.
(ChannelName=[STRING], VlanId=[INTEGER], ConfiguredValue=[INTEGER],
Description
New Join messages were received after the bandwidth of multicast groups in the channel of the
VLAN reached the upper limit.
Issue 07 (2014-07-30)

1072

Log Reference
93 SNPG
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
VlanId
VLAN ID
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the channel of

the VLAN
Possible Causes
The bandwidth of multicast groups in the channel of the VLAN reached the upper limit.
Procedure
----End
93.61 SNPG/6/VLANCHNLBDWEXDCFG
Message
SNPG/6/VLANCHNLBDWEXDCFG:The bandwidth of multicast groups has already exceeded
the limit configured. (ChannelName=[STRING], VlanId=[INTEGER], ConfiguredValue=
Description
The bandwidth of current multicast groups in the channel of the VLAN exceeded the upper limit.
Parameters
ChannelName
Channel name
VlanId
VLAN ID
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the channel of the

VLAN
StatisticsValue
Bandwidth of current multicast groups in the channel of the VLAN
Possible Causes
The bandwidth of current multicast groups in the channel of the VLAN exceeded the upper limit.
Issue 07 (2014-07-30)

1073

Log Reference
93 SNPG
Procedure
----End
93.62 SNPG/6/VLANCHNLCNTEXD
Message
SNPG/6/VLANCHNLCNTEXD:The number of multicast groups reached the upper limit.
(ChannelName=[STRING], VlanId=[INTEGER], ConfiguredValue=[INTEGER],
Description
New Join messages were received after the number of multicast groups in the channel of the
VLAN reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
VlanId
VLAN ID
ConfiguredValue
Upper limit of the number of multicast groups in the channel of the

VLAN
Possible Causes
The number of multicast groups in the channel of the VLAN reached the upper limit.
Procedure
----End
93.63 SNPG/6/VLANCHNLCNTEXDCFG
Message
SNPG/6/VLANCHNLCNTEXDCFG:The number of multicast groups has already exceeded the
limit configured. (ChannelName=[STRING], VlanId=[INTEGER], ConfiguredValue=
Issue 07 (2014-07-30)

1074

Log Reference
93 SNPG
Description
The number of current multicast groups in the channel of the VLAN exceeded the upper limit.
Parameters
ChannelName
Channel name
VlanId
VLAN ID
ConfiguredValue
Upper limit of the number of multicast groups in the channel of the VLAN
StatisticsValue
Number of current multicast groups in the channel of the VLAN
Possible Causes
The number of current multicast groups in the channel of the VLAN exceeded the upper limit.
Procedure
----End
93.64 SNPG/6/VLANCNTEXD
Message
SNPG/6/VLANCNTEXD:The number of multicast groups reached the upper limit.(VlanId=
[INTEGER], ConfiguredValue=[INTEGER], CurrentMulticastGroup=[STRING])
Description
New Join messages were received after the number of multicast groups in the VLAN reached
the upper limit.
Parameters
Parameter Name
Parameter Meaning
VlanId
VLAN ID
ConfiguredValue
Upper limit of the number of multicast groups in the VLAN
Possible Causes
The number of multicast groups in the VLAN reached the upper limit.
Issue 07 (2014-07-30)

1075

Log Reference
93 SNPG
Procedure
----End
93.65 SNPG/6/VLANCNTEXDCFG
Message
SNPG/6/VLANCNTEXDCFG:The number of multicast groups has already exceeded the limit
configured. (VlanId=[INTEGER], ConfiguredValue=[INTEGER], StatisticsValue=
[INTEGER])
Description
The number of current multicast groups in the VLAN exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
VlanId
VLAN ID
ConfiguredValue
Upper limit of the number of multicast groups in the VLAN
StatisticsValue
Number of current multicast groups in the VLAN
Possible Causes
The number of current multicast groups in the VLAN exceeded the upper limit.
Procedure
----End
93.66 SNPG/6/VSIBDWEXD
Message
SNPG/6/VSIBDWEXD:The bandwidth of multicast groups reached the upper limit. (VsiName=
Description
New Join messages were received after the bandwidth of multicast groups in the VSI reached
the upper limit.
Issue 07 (2014-07-30)

1076

Log Reference
93 SNPG
Parameters
Parameter Name
Parameter Meaning
VsiName
VSI name
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the VSI
Possible Causes
The bandwidth of multicast groups in the VSI reached the upper limit.
Procedure
----End
93.67 SNPG/6/VSIBDWEXDCFG
Message
SNPG/6/VSIBDWEXDCFG:The bandwidth of multicast groups has already exceeded the limit
configured. (VsiName=[STRING], ConfiguredValue=[INTEGER], StatisticsValue=
[INTEGER])
Description
The bandwidth of current multicast groups in the VSI exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
VsiName
VSI name
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the VSI
StatisticsValue
Bandwidth of current multicast groups in the VSI
Possible Causes
The bandwidth of current multicast groups in the VSI exceeded the upper limit.
Procedure
----End
Issue 07 (2014-07-30)

1077

Log Reference
93 SNPG
93.68 SNPG/6/VSICHANNELDENY
Message
SNPG/6/VSICHANNELDENY:The unspecified-channel deny configuration exists in VSI
channel. (VsiName=[STRING], CurrentMulticastGroup=[STRING])
Description
unspecified-channel deny command is configured for the channel in the VSI.
Parameters
Parameter Name
Parameter Meaning
VsiName
VSI name
Possible Causes
unspecified-channel deny command is configured for the channel in the VSI.
Procedure
----End
93.69 SNPG/6/VSICHNLBDWEXD
Message
SNPG/6/VSICHNLBDWEXD:The bandwidth of multicast groups reached the upper limit.
(ChannelName=[STRING], VsiName=[STRING], ConfiguredValue=[INTEGER],
Description
New Join messages were received after the bandwidth of multicast groups in the channel of the
VSI reached the upper limit.
Issue 07 (2014-07-30)

1078

Log Reference
93 SNPG
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
VsiName
VSI name
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the channel of

the VSI
Possible Causes
The bandwidth of multicast groups in the channel of the VSI reached the upper limit.
Procedure
----End
93.70 SNPG/6/VSICHNLBDWEXDCFG
Message
SNPG/6/VSICHNLBDWEXDCFG:The bandwidth of multicast groups has already exceeded
the limit configured. (ChannelName=[STRING], VsiName=[STRING], ConfiguredValue=
Description
The bandwidth of current multicast groups in the channel of the VSI exceeded the upper limit.
Parameters
ChannelName
Channel name
VsiName
VSI name
ConfiguredValue
Upper limit of the bandwidth of multicast groups in the channel of the

VSI
StatisticsValue
Bandwidth of current multicast groups in the channel of the VSI
Possible Causes
The bandwidth of current multicast groups in the channel of the VSI exceeded the upper limit.
Issue 07 (2014-07-30)

1079

Log Reference
93 SNPG
Procedure
----End
93.71 SNPG/6/VSICHNLCNTEXD
Message
SNPG/6/VSICHNLCNTEXD:The number of multicast groups reached the upper limit.
(ChannelName=[STRING], VsiName=[STRING], ConfiguredValue=[INTEGER],
Description
New Join messages were received after the number of multicast groups in the channel of the
VSI reached the upper limit.
Parameters
Parameter Name
Parameter Meaning
ChannelName
Channel name
VsiName
VSI name
ConfiguredValue
Upper limit of the number of multicast groups in the channel of the

VSI
Possible Causes
The number of multicast groups in the channel of the VSI reached the upper limit.
Procedure
----End
93.72 SNPG/6/VSICHNLCNTEXDCFG
Message
SNPG/6/VSICHNLCNTEXDCFG:The number of multicast groups has already exceeded the
limit configured. (ChannelName=[STRING], VsiName=[STRING], ConfiguredValue=
Issue 07 (2014-07-30)

1080

Log Reference
93 SNPG
Description
The number of current multicast groups in the channel of the VSI exceeded the upper limit.
Parameters
ChannelName
Channel name
VsiName
VSI name
ConfiguredValue
Upper limit of the number of multicast groups in the channel of the VSI
StatisticsValue
Number of current multicast groups in the channel of the VSI
Possible Causes
The number of current multicast groups in the channel of the VSI exceeded the upper limit.
Procedure
----End
93.73 SNPG/6/VSICNTEXD
Message
SNPG/6/VSICNTEXD:The number of multicast groups reached the upper limit. (VsiName=
Description
New Join messages were received after the number of multicast groups in the VSI reached the
upper limit.
Parameters
Parameter Name
Parameter Meaning
VsiName
VSI name
ConfiguredValue
Upper limit of the number of multicast groups in the VSI
Possible Causes
The number of multicast groups in the VSI reached the upper limit.
Issue 07 (2014-07-30)

1081

Log Reference
93 SNPG
Procedure
----End
93.74 SNPG/6/VSICNTEXDCFG
Message
SNPG/6/VSICNTEXDCFG:The number of multicast groups has already exceeded the limit
configured. (VsiName=[STRING], ConfiguredValue=[INTEGER], StatisticsValue=
[INTEGER])
Description
The number of current multicast groups in the VSI exceeded the upper limit.
Parameters
Parameter Name
Parameter Meaning
VsiName
VSI name
ConfiguredValue
Upper limit of the number of multicast groups in the VSI
StatisticsValue
Number of current multicast groups in the VSI
Possible Causes
The number of current multicast groups in the VSI exceeded the upper limit.
Procedure
----End
Issue 07 (2014-07-30)

1082

Log Reference
94 SOCKET
94
SOCKET
About This Chapter

94.1 SOCKET/4/ASYNACCEPTFAIL
94.2 SOCKET/1/BINDPEERIP
94.3 SOCKET/4/CANTGETLSTNSOCK
94.4 SOCKET/4/EXCEEDMAXQLEN
94.5 SOCKET/6/FGETVPNNAME
94.6 SOCKET/6/LSTNASYNQUEINFO
94.7 SOCKET/6/SGETVPNNAME
94.8 SOCKET/4/SO_ACCEPTCFAIL
94.9 SOCKET/6/SOCKCLOSED
94.10 SOCKET/6/SOCKNOTEXIST
94.11 SOCKET/6/SUBQUEINFO
94.12 SOCKET/6/TCPASYNQUEINFO
94.13 SOCKET/6/TCPCONNBLK
94.14 SOCKET/6/TCPIOSTAT
94.15 SOCKET/6/TCPWNDCLOSE
94.16 SOCKET/6/VRBSRIPSOCKINFO
94.17 SOCKET/6/VRBSSOCKINFO
94.18 SOCKET/6/VRBSTCPSOCKINFO
94.19 SOCKET/6/VRBSUDPSOCKINFO
Issue 07 (2014-07-30)

1083

Log Reference
94 SOCKET
94.1 SOCKET/4/ASYNACCEPTFAIL
Message
SOCKET/4/ASYNACCEPTFAIL:Failed to allocate the file describer for the sub socket when
accept was called to accept incoming connection request. (Time=[ULONG], TaskName=
[STRING], TaskId=[ULONG], SocketId=[ULONG], ErrorCode=[LONG])
Description
Failed to allocate the file descriptor to the socket when the Accept function was called to receive
the connection request.
Parameters
Parameter Name
Parameter Meaning
Time
indicates the time when the log is generated.
TaskName
indicates the task name.
TaskId
SocketId
indicates the socket ID.
ErrorCode
indicates the error codes, that is, -101, -24, and -55.
Possible Causes
1. Because the system memory was insufficient, namely, the memory was used up or nearly used
up, the TCP listening socket could not receive the connection request from the client, and the
connection failed.
2. During the current task, the number of sockets exceeded the upper limit defined by the system,
and no file descriptor could be allocated to the sockets. Then the connection failed.
Procedure
Step 1 If the fault is caused by the insufficient memory, cancel some memory-consuming and
unnecessary applications.
Step 2 If the fault is caused by the insufficient file descriptors, cancel some applications that occupy a
large number of file descriptors. In this manner, you can release enough file descriptors for
current applications.
----End
94.2 SOCKET/1/BINDPEERIP
Issue 07 (2014-07-30)

1084

Log Reference
94 SOCKET
Message
SOCKET/1/BINDPEERIP:Failed to bind the peer IP because a socket with same state already
existed.
Description
Failed to bind the peer IP address because a socket in the system had the same status as that of
the current socket.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1. The peer IP address was repeatedly set.
2. The system had a socket with the same local IP address, local port number, remote IP address,
remote port number, and VPN index as that of the socket to be set.
Procedure
Step 1 The log is generated when the system faces an unknown fault. The fault causes the relevant
routing protocol unavailable. Then you need disable the routing protocol and then enable it.
----End
94.3 SOCKET/4/CANTGETLSTNSOCK
Message
SOCKET/4/CANTGETLSTNSOCK:Failed to obtain the ID of the listening socket. (TaskId=
[ULONG], SocketId=[ULONG], ErrorCode=[LONG])
Description
Failed to acquire the listening socket ID.
Parameters
Parameter Name
Parameter Meaning
TaskId
SocketId
ErrorCode
indicates the error codes, that is, -22 and -107.
Issue 07 (2014-07-30)

1085

Log Reference
94 SOCKET
Possible Causes
A software error occurred in the system. Then the relevant task control block could not be found
according to the task ID, or the relevant socket could not be found according to the file descriptor.
You can consider that the fault has nearly no chance to occur.
Procedure
----End
94.4 SOCKET/4/EXCEEDMAXQLEN
Message
SOCKET/4/EXCEEDMAXQLEN:The number of messages in the asynchronous message
queue was greater than the message upper limit. (Time=[ULONG], TaskName=[STRING],
TaskId=[ULONG], SocketId=[ULONG], ErrorCode=[LONG])
Description
The number of messages in the asynchronous message queue exceeded the defined upper limit.
Parameters
Parameter Name
Parameter Meaning
Time
TaskName
TaskId
SocketId
ErrorCode
indicates the error code, that is, -8.
Possible Causes
Each asynchronous socket has a queue to receive messages. This log indicates that the message
queue was full and no new message could be received. The cause is that the speed in which the
CPU read messages was slower than the speed to generate messages. In most cases, the fault is
caused when a large number of packets are generated in the network, and the CPU is too busy
to handle received messages in time. Therefore, the message queue becomes full and the received
subsequent data is discarded.
Procedure
Step 1 Reduce the workload of the CPU by canceling some processes that are CPU-time consuming
and unnecessary.
Issue 07 (2014-07-30)

1086

Log Reference
94 SOCKET
Step 2 If possible, wait till the CPU is idle and then configure relevant tasks.
----End
94.5 SOCKET/6/FGETVPNNAME
Message
SOCKET/6/FGETVPNNAME:The current socket failed to obtain the VPN name. (ErrorCode=
[ULONG])
Description
The current socket failed to acquire the VPN name.
Parameters
Parameter Name
Parameter Meaning
ErrorCode
indicates an error code. The error codes are shown as follows

4: indicates that the input parameter is invalid.
5: indicates that the VRF name is inexistent.
7: indicates that the VRF is in the inactive state.
Possible Causes
A socket was closed, and then the VPN information about the closed socket was being recorded
into the log. During the process to acquire the VPN information, a fault occurred, and the relevant
VPN information could not be acquired.
Procedure
----End
94.6 SOCKET/6/LSTNASYNQUEINFO
Message
SOCKET/6/LSTNASYNQUEINFO:The verbose information about the current asynchronous
queue in listening state was displayed. (Read=[ULONG], Write=[ULONG], Connect=
[ULONG], Close=[ULONG], PeerClose=[ULONG], Accept=[ULONG], KeepAliveDown=
[ULONG], Crammed at: [ULONG]:[ULONG]:[ULONG](Hour:Minute:Seconds),
LostMessage=[ULONG], MessageType=[ULONG])
Issue 07 (2014-07-30)

1087

Log Reference
94 SOCKET
Description
The detailed information about the asynchronous message queue in the listening status was
described in the log.
Parameters
Read
indicates the number of Read messages.
Write
indicates the number of Write messages.
Connect
indicates the number of Connect messages.
Close
indicates the number of Close messages.
PeerClose
indicates the number of PeerClose messages.
Accept
indicates the number of Accept messages.
KeepAliveDown
indicates the number of Keep Alive Down messages.
Crammed at
indicates the time when the asynchronous message queue becomes full.
The format is HH:MM:SS.
LostMessage
indicates the number of lost messages.
MessageType
indicates the type of lost messages. The types of lost messages are shown
as follows
1. Read
2. Write
3. Connect
4. Close
5. Accept
6. PeerClose
7. KeepAliveDown
Possible Causes
The TCP listening socket was closed for a certain cause, and then the information about the
asynchronous message queue at the closed TCP listening socket was recorded.
Procedure
----End
Issue 07 (2014-07-30)

1088

Log Reference
94 SOCKET
94.7 SOCKET/6/SGETVPNNAME
Message
SOCKET/6/SGETVPNNAME:The current socket succeeded to obtain the VPN name.
(VPNName=[STRING])
Description
The current socket successfully acquired a VPN name.
Parameters
Parameter Name
Parameter Meaning
VPNName
indicates the name of a VPN instance.
Possible Causes
A socket was closed, and then the VPN information about the closed socket was recorded into
the log.
Procedure
----End
94.8 SOCKET/4/SO_ACCEPTCFAIL
Message
SOCKET/4/SO_ACCEPTCFAIL:The error code of SO_Accept was returned. (Time=
[ULONG], TaskName=[STRING], TaskId=[ULONG], SocketId=[ULONG], ErrorCode=
[LONG])
Description
The Accept function failed and an error code was returned.
Parameters
Parameter Name
Parameter Meaning
Time
TaskName
Issue 07 (2014-07-30)

1089

Log Reference
94 SOCKET
Parameter Name
Parameter Meaning
TaskId
SocketId
ErrorCode
indicates the error code -55.
Possible Causes
Because the system memory was insufficient, namely, the memory was used up or nearly used
up, the TCP listening socket could not receive the connection request from the client, and the
connection failed.
Procedure
Step 1 Run the display diagnostic-information command to save the displayed result, and contact
Huawei technical personnel.
----End
94.9 SOCKET/6/SOCKCLOSED
Message
SOCKET/6/SOCKCLOSED:The current socket was closed. (ProtocolName=[STRING],
Cause=[STRING])
Description
The current socket was turned off.
Parameters
ProtocolName
indicates the protocol name. The protocol names are shown as follows
1. RAWLINK
2. RAWIP
3. TCP
4. UDP
Issue 07 (2014-07-30)

1090

Log Reference
94 SOCKET

Cause
indicates the triggering condition. The triggering conditions are shown as

follows
1. Application closed socket
2. Received reset fragment
3. Retransfer timeout
4. Keepalive timeout
Possible Causes
1. The user called the Close function to turn off the socket.
2. The TCP server received RST packets from the TCP client.
3. TCP retransmission timed out.
4. Failed to perform TCP keepalive detection.
Procedure
----End
94.10 SOCKET/6/SOCKNOTEXIST
Message
SOCKET/6/SOCKNOTEXIST:The current socket did not exist. (TaskName=[STRING],
Socket=[STRING], ProtocolName=[STRING])
Description
The current socket was inexistent.
Parameters
Parameter Name
Parameter Meaning
TaskName
Socket
ProtocolName
indicates the protocol name.
Possible Causes
Failed to find the socket control block in the system.
Issue 07 (2014-07-30)

1091

Log Reference
94 SOCKET
Procedure
----End
94.11 SOCKET/6/SUBQUEINFO
Message
SOCKET/6/SUBQUEINFO:The verbose information about the current subqueue was
displayed. (Full at: [ULONG]:[ULONG]:[ULONG](Hour:Minute:Seconds), Ready at:
[ULONG]:[ULONG]:[ULONG](Hour:Minute:Seconds), CurrentState=[STRING], Number of
refused connections=[ULONG])
Description
The detailed information about the current connected sub-queues was described in the log.
Parameters
Parameter Name
Parameter Meaning
Full at
indicates the time when the sub-queue at the TCP listening

socket is full. The format is HH:MM:SS.
Ready at
indicates the time when the sub-queue at the TCP listening

socket is ready to accept packets after being full. The format
is HH:MM:SS.
CurrentState
indicates a current state. The current states are shown as

follows
(1) full
(2) ready
Number of refused connections indicates the number of connections refused by the server.
Possible Causes
The TCP listening socket was closed for a certain cause, and then the information about the
closed TCP listening socket was recorded.
Procedure
----End
Issue 07 (2014-07-30)

1092

Log Reference
94 SOCKET
94.12 SOCKET/6/TCPASYNQUEINFO
Message
SOCKET/6/TCPASYNQUEINFO:The verbose information about the asynchronous queue of
the current TCP socket was displayed. (Read=[ULONG], Write=[ULONG], Connect=
[ULONG], Close=[ULONG], PeerClose=[ULONG], Accept=[ULONG], KeepAliveDown=
[ULONG], Full at: [ULONG]:[ULONG]:[ULONG] (Hour:Minute:Second), LostMessage=
[ULONG], MessageType=[ULONG])
Description
The detailed information about the asynchronous message queue of the current TCP socket was
described in the log.
Parameters
Read
indicates the number of Read messages.
Write
indicates the number of Write messages.
Connect
indicates the number of Connect messages.
Close
indicates the number of Close messages.
PeerClose
indicates the number of PeerClose messages.
Accept
indicates the number of Accept messages.
KeepAliveDown
indicates the number of Keep Alive Down messages.
Full at
indicates the time when the asynchronous message queue becomes full.
LostMessage
indicates the number of lost messages.
MessageType
indicates the type of lost messages. The types of lost messages are shown
as follows
1. Read
2. Write
3. Connect
4. Close
5. Accept
6. PeerClose
7. KeepAliveDown
Issue 07 (2014-07-30)

1093

Log Reference
94 SOCKET
Possible Causes
Procedure
----End
94.13 SOCKET/6/TCPCONNBLK
Message
SOCKET/6/TCPCONNBLK:The current TCP connection was blocked at [ULONG]:
[ULONG]:[ULONG] (Hour:Minute:Second)
Description
The current TCP connection was blocked.
Parameters
blocked at
indicates the time when the TCP connection or disconnection is cut off.
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

1094

Log Reference
94 SOCKET
94.14 SOCKET/6/TCPIOSTAT
Message
SOCKET/6/TCPIOSTAT:The statistic of the packets sent and received through the current TCP
connection was displayed. (Input=[ULONG], ReceivedPackets=[ULONG], SentPackets=
[ULONG])
Description
The statistics of the input and output traffic in the current TCP connection were described in the
log.
Parameters
Input
indicates the total number of TCP packets received by the socket. Note
that TCP packets include TCP control packets and TCP data packets.
ReceivedPackets
indicates the total number of TCP data packets received by the socket.
SentPackets
indicates the total number of TCP packets output by the socket.
Possible Causes
Procedure
----End
94.15 SOCKET/6/TCPWNDCLOSE
Message
SOCKET/6/TCPWNDCLOSE:The peer closed the TCP receival window, namely, the size of
the peer's receival window was zero and the local end could not send data. (Started at [ULONG]:
[ULONG]:[ULONG] (Hour:Minute:Second), Total times of closing the window=[ULONG])
Issue 07 (2014-07-30)

1095

Log Reference
94 SOCKET
Description
The remote end in a TCP connection closed the sliding window, which means that the value of
the sliding window was zero and the local end could not send data any more.
Parameters
Parameter Name
Parameter Meaning
Started at
indicates the time when remote end in a TCP connection

lastly notifies that the value of its sliding window is 0. The
format is HH:MM:SS.
Total times of closing the window indicates the times that the sliding window of the remote
end in a TCP connection is not available.
Possible Causes
Procedure
l
----End
94.16 SOCKET/6/VRBSRIPSOCKINFO
Message
SOCKET/6/VRBSRIPSOCKINFO:The verbose information about the current RawIP socket
was displayed. (SocketPair: [STRING], ProtocolNumber=[ULONG])
Description
The detailed information about the current RAWIP socket was described in the log.
Parameters
Parameter Name
Parameter Meaning
SocketPair
indicates the information about the RAWIP address.
ProtocolNumber
indicates the protocol number of RAWIP.
Issue 07 (2014-07-30)

1096

Log Reference
94 SOCKET
Possible Causes
A RAWIP socket was closed, and then the current status, local IP address, and remote IP addressr
of the closed RAWIP socket were recorded into the log.
Procedure
l
----End
94.17 SOCKET/6/VRBSSOCKINFO
Message
SOCKET/6/VRBSSOCKINFO:The verbose information about the current socket was
displayed. (Task=[STRING]([ULONG]), Socket=[ULONG]([STRING]), ProtocolNumber=
[ULONG])
Description
The detailed information about the current socket was described in the log.
Parameters
Task
indicates a task, including the task name and task ID.
Socket
indicates the ID and the protocol type of a socket. The protocol types are
shown as follows
l RAWLINK
l RAWIP
l TCP
l UDP
ProtocolNumber
indicates the number of the transport layer protocol. The value ranges
from 1 to 255.
Possible Causes
Issue 07 (2014-07-30)

1097

Log Reference
94 SOCKET
Procedure
l
----End
94.18 SOCKET/6/VRBSTCPSOCKINFO
Message
SOCKET/6/VRBSTCPSOCKINFO:The verbose information about the current TCP socket was
displayed. (State=[STRING], SocketPair: [STRING])
Description
The detailed information about the current TCP socket was described in the log.
Parameters
Parameter Name
Parameter Meaning
State
indicates the TCP state. The TCP states are shown as follows
1. Closed
2. Listening
3. Syn_Sent
4. Syn_Rcvd
5. Established
6. Close_Wait
7. Fin_Wait1
8. Closing
9. Last_Ack
10.Fin_Wait2
11.Time_Wait
SocketPair
indicates the socket pair, that is, TCP quadbit.
Possible Causes
Issue 07 (2014-07-30)

1098

Log Reference
94 SOCKET
Procedure
l
----End
94.19 SOCKET/6/VRBSUDPSOCKINFO
Message
SOCKET/6/VRBSUDPSOCKINFO:The verbose information about the current UDP socket
was displayed. (SocketPair: [STRING])
Description
The detailed information about the current UDP socket was described in the log.
Parameters
Parameter Name
Parameter Meaning
SocketPair
indicates the socket pair, that is, UDP quadbit.
Possible Causes
A UDP socket was closed, and then the current status, local IP address, local port number, remote
IP address, and remote port number of the closed UDP socket were recorded in the log.
Procedure
----End
Issue 07 (2014-07-30)

1099

Log Reference
95 SRM
95
SRM
About This Chapter

95.1 SRM/4/6300_FPGA_FAULT
95.2 SRM/4/6300_FPGA_FAULT_RESUME
95.3 SRM/3/BCM56514_XAUI_REF_CLOCK_FAULT
95.4 SRM/3/BCM56514_XAUI_REF_CLOCK_FAULT_RESUME
95.18 SRM/3/I2C_FAULT
95.19 SRM/3/I2C_FAULT_RESUME
95.20 SRM/3/USB5V_POWFAULT
Issue 07 (2014-07-30)

1100

Log Reference
95 SRM
95.21 SRM/3/USB5V_POWFAULT_RESUME
95.22 SRM/3/FANEXC
95.23 SRM/3/FANOK
95.24 SRM/4/FANPLGIN
95.25 SRM/3/FANPLUGOUT
95.26 SRM/3/LIGHT_FAULT
95.27 SRM/3/LIGHT_FAULT_RESUME
95.28 SRM/3/INOUT
95.29 SRM/6/SRM_LOGID_STARTUP_VERSION
95.30 SRM/1/POWEXC
95.31 SRM/6/POWON
95.32 SRM/4/POWPLGIN
95.33 SRM/4/POWPULOUT
95.34 SRM/3/TXPOWER_EXCEEDMAJOR
95.35 SRM/3/RXPOWER_EXCEEDMINOR
95.36 SRM/5/RXPOWER_RESUME
95.37 SRM/6/SFPCATEGORY_UNKNOW
95.38 SRM/4/STACK_PORT_DOWN
95.39 SRM/4/STACK_PORT_UP
95.40 SRM/3/RXPOWER_EXCEEDMAJOR
95.41 SRM/3/TXPOWER_EXCEEDMINOR
95.42 SRM/5/TXPOWER_RESUME
95.43 SRM/3/WTFLSHFAIL
Issue 07 (2014-07-30)

1101

Log Reference
95 SRM
95.1 SRM/4/6300_FPGA_FAULT
Message
SRM/4/6300_FPGA_FAULT:FPGA abnormal
Description
Field Programmable Gate Array (FPGA) worked improperly.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The hardware logic worked improperly.
Procedure
Step 1 Check whether the fault can be automatically rectified by determing whether the recovery log
is generated.
Step 2 If not, reset the board manually.
Step 3 If you fail to reset the board or if the fault persists after the board is reset, contact Huawei technical
support personnel.
----End
95.2 SRM/4/6300_FPGA_FAULT_RESUME
Message
SRM/4/6300_FPGA_FAULT_RESUME:FPGA normal.
Description
FPGA recovered and worked properly.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

1102

Log Reference
95 SRM
Possible Causes
The hardware logic component fault was rectified.
Procedure
l
----End
95.3 SRM/3/BCM56514_XAUI_REF_CLOCK_FAULT
Message
SRM/3/BCM56514_XAUI_REF_CLOCK_FAULT:"LANSWITCH #[ULONG] XAUI
Reference Clock is fault. CAUTION: board will be reset if three continuous faults occur!"
Description
The XAUI interface reference clock failed. If this fault occurs continuously, the board may be
reset.
NOTE
Only the S5700EI supports the log.
Parameters
Parameter Name
Parameter Meaning
ULONG
Indicates the chip ID.
Possible Causes
The XAUI interface reference clock failed.
Procedure
l
----End
95.4 SRM/3/
BCM56514_XAUI_REF_CLOCK_FAULT_RESUME
Message
SRM/3/BCM56514_XAUI_REF_CLOCK_FAULT_RESUME:"LANSWITCH #[ULONG]
XAUI Reference Clock normal."
Issue 07 (2014-07-30)

1103

Log Reference
95 SRM
Description
The XAUI interface reference clock recovers from a fault.
NOTE
Only the S5700EI supports the log.
Parameters
Parameter Name
Parameter Meaning
ULONG
Indicates the chip ID.
Possible Causes
The XAUI interface reference clock recovers from a fault.
Procedure
l
----End
Message
SRM/4/BATCGOVERCURPROTECT: The system started lithium battery group charge
overcurrent protection.(SlotID=[ULONG], CardID=[ULONG]).
Description
During a charge of the lithium battery group, the current exceeded the overcurrent protection
threshold.
NOTE
This log is available only on the S5700-28P-LI-BAT and S5700-28P-LI-24S-BAT.
Parameters
Parameter Name
Parameter Meaning
SlotID
Indicates a slot ID.
CardID
Indicates a card ID.
Possible Causes
The charge overcurrent protection threshold for a lithium battery group is 1.5 A. If the current
exceeds 1.5 A during a charge, the lithium battery group stops charging, and the system records
this log.
Issue 07 (2014-07-30)

1104

Log Reference
95 SRM
Procedure
l
This is a protection function of the lithium battery, and no action is required.
----End
Message
SRM/4/BATCGOVERVOLPROTECT: The system started lithium battery group charge
overvoltage protection.(SlotID=[ULONG], CardID=[ULONG]).
Description
During a charge of the lithium battery group, the voltage exceeded the overvoltage protection
threshold.
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Possible Causes
The charge overvoltage protection threshold for a lithium battery group is 12.6 V. If the voltage
exceeds 12.6 V during a charge, the lithium battery group stops charging, and the system records
this log.
Procedure
l
----End
Message
SRM/2/BATDGTEMPHIGH: The discharge temperature of the lithium battery is higher than
the threshold.(SlotID=[ULONG], CardID=[ULONG]).
Issue 07 (2014-07-30)

1105

Log Reference
95 SRM
Description
During a single-cell discharge of the lithium battery, the temperature exceeded the upper
threshold.
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Possible Causes
The normal single-cell discharge temperature for a lithium battery is -5C to +50C. If the
temperature of the lithium battery exceeds the upper threshold during a single-cell discharge,
the system records this log.
Procedure
l
Check whether the air vent for the lithium battery is blocked and whether the fans are
running normally.
----End
Message
SRM/4/BATDGTEMPHIGHRESUME: The discharge temperature of the lithium battery
restored to the normal range.(SlotID=[ULONG], CardID=[ULONG])
Description
During a single-cell discharge of the lithium battery, the temperature restored to the normal
range.
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Issue 07 (2014-07-30)

1106

Log Reference
95 SRM
Possible Causes
The normal single-cell discharge temperature for a lithium battery is -5C to +50C. During a
single-cell discharge, if the temperature of the lithium battery exceeds the upper threshold and
then restores to the normal range, the system records this log.
Procedure
l
----End
Message
SRM/4/BATLIFEENDCLEAR: Battery service life expiration recovered.(SlotID=[ULONG],
CardID=[ULONG]).
Description
The lithium battery whose lifetime expired has been removed.
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Possible Causes
The lithium battery whose lifetime expired has been removed.
Procedure
l
Install a new lithium battery in the device.
----End
Message
SRM/2/BATINVALID: Battery is invalid for some reason.(SlotID=[ULONG], CardID=
[ULONG], reason=[STRING]).
Issue 07 (2014-07-30)

1107

Log Reference
95 SRM
Description
The lithium battery has an internal fault.
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
reason
Indicates the cause of the fault.
Possible Causes
l
The charge switch of the lithium battery is in a short-circuit condition.
The charge switch of the lithium battery is in an open-circuit condition.
The discharge switch of the lithium battery is in a short-circuit condition.
The discharge switch of the lithium battery is in an open-circuit condition.
Both the charge and discharge switches of the lithium battery are in a short-circuit condition.
Both the charge and discharge switches of the lithium battery are in an open-circuit
condition.
The electrochemical cell of the lithium battery is faulty.
An error occurs when the system is collecting temperature of the lithium battery.
Another type of fault has occurred.
Replace the lithium battery.
Procedure
----End
Message
SRM/2/BATSUPPLYTIMESHORT: The battery's supply time is below threshold value.
(SlotID=[ULONG], CardID=[ULONG]).
Description
The lithium battery's supply time is below threshold value.
NOTE
Issue 07 (2014-07-30)

1108

Log Reference
95 SRM
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Possible Causes
The lithium battery has an internal fault.
Procedure
l
Replace the lithium battery.
----End
Message
SRM/2/BATREMAINLOW: The spare battery power fell below [ULONG]% of total power.
(SlotID=[ULONG], BatRemain=[ULONG]%).
Description
The available power of the lithium battery is too low.
NOTE
Parameters
SlotID
BatRemain
Indicates the available power of the battery. The value is 5, 10, or 20,
indicating a percentage.
Possible Causes
The lithium battery is supplying power to the device, and the available power of the battery is
less than 20%, 10%, or 5% of the full power.
Procedure
l
The lithium battery can be charged automatically after the power supply of the device is
turned on.
----End
Issue 07 (2014-07-30)

1109

Log Reference
95 SRM
Message
SRM/4/BATREMAINLOWRESUME: The spare battery power increased to above [ULONG]
% of total power.(SlotID=[ULONG], BatRem ain=[ULONG]%).
Description
The available power of the lithium battery restored to more than 20% of its total power.
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
BatRemain
Indicates the available power of the lithium battery.
Possible Causes
The power supply of the device has been turned on and automatically charged the lithium battery.
Then the available power of the lithium battery increased to more than 20% of the total power.
Procedure
l
----End
Message
SRM/4/BATTEMPDGHIGHPROTECT: The system started lithium battery single-cell charge
overtemperature protection.(SlotID=[ULONG], CardID=[ULONG]).
Description
During a single-cell charge of the lithium battery, the temperature exceeded the protection
threshold.
NOTE
Issue 07 (2014-07-30)

1110

Log Reference
95 SRM
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Possible Causes
The normal single-cell charge temperature for a lithium battery is 0C to 45C. If the ambient
temperature retains in this range during a single-cell charge, the lithium battery does not take
protective measures. If the temperature is out of this range, the lithium battery enters the
protection state and stops charging. The system records this log.
Procedure
l
----End
Message
SRM/2/BATTEMPLOW: The lithium battery temperature fell below the lower threshold.
(SlotID=[ULONG], CardID=[ULONG]).
Description
The temperature of the lithium battery is below the lower threshold.
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Possible Causes
The single-cell discharge temperature range for a lithium battery is -5C to +50C, and the charge
temperature range is 0C to 45C. When the charge or discharge temperature of the lithium
battery is below the lower threshold, the system records this log.
Issue 07 (2014-07-30)

1111

Log Reference
95 SRM
Procedure
l
Increase the ambient temperature.
----End
Message
SRM/4/BATTEMPLOWPROTECT: The system started lithium battery under-temperature
protection.(SlotID=[ULONG], CardID=[ULONG]).
Description
The temperature of the lithium battery is below the under-temperature protection threshold.
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Possible Causes
temperature range is 0C to 45C. When the charge or discharge temperature of the lithium
battery is below the under-temperature protection threshold, the system records this log.
Procedure
l
Increase the ambient temperature.
----End
Message
SRM/4/BATTEMPLOWRESUME: The lithium battery temperature raised above the lower
threshold.(SlotID=[ULONG], CardID=[ULONG])
Description
The temperature of the lithium battery restored to the normal range.
Issue 07 (2014-07-30)

1112

Log Reference
95 SRM
NOTE
Parameters
Parameter Name
Parameter Meaning
SlotID
CardID
Possible Causes
temperature range is 0C to 45C. When the temperature of the lithium battery increases above
the lower threshold, the system records this log.
Procedure
l
----End
95.18 SRM/3/I2C_FAULT
Message
SRM/3/I2C_FAULT:[STRING] I2C is abnormal.
Description
I2C worked improperly.
Parameters
Parameter Name
Parameter Meaning
STRING
Indicates the name of a subcard.
Possible Causes
The I2C channel was faulty.
Procedure
is generated.
Issue 07 (2014-07-30)

1113

Log Reference
95 SRM
support personnel.
----End
95.19 SRM/3/I2C_FAULT_RESUME
Message
SRM/3/I2C_FAULT_RESUME:[STRING] I2C is normal.
Description
I2C recovered and worked properly.
Parameters
Parameter Name
Parameter Meaning
STRING
Indicates the name of a subcard.
Possible Causes
The I2C channel fault was rectified.
Procedure
l
----End
95.20 SRM/3/USB5V_POWFAULT
Message
SRM/3/USB5V_POWFAULT:Usb power5v fault.
Description
USB 5 V power supply was faulty.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

1114

Log Reference
95 SRM
Possible Causes
USB 5 V power supply was faulty.
Procedure
is generated.
support personnel.
----End
95.21 SRM/3/USB5V_POWFAULT_RESUME
Message
SRM/3/USB5V_POWFAULT_RESUME:Usb power resumes.
Description
USB 5 V power supply fault was rectified.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
USB 5 V power supply fault was rectified.
Procedure
l
----End
95.22 SRM/3/FANEXC
Message
SRM/3/FANEXC:Fault occurs in the fan in slot [ULONG].
Issue 07 (2014-07-30)

1115

Log Reference
95 SRM
Description
The fan does not work.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Indicates the slot ID of the fan.
Possible Causes
1:
The fan hardware is faulty.
2:
The fan is not installed properly.
Procedure
l
Check whether the fan is installed properly.
If so, the fan hardware is faulty. Replace the fan.
If not, install the fan properly.
----End
95.23 SRM/3/FANOK
Message
SRM/3/FANOK:Fan in slot [ULONG] recovers.
Description
The fan recovers.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
The fan starts to work.
Issue 07 (2014-07-30)

1116

Log Reference
95 SRM
Procedure
l
----End
95.24 SRM/4/FANPLGIN
Message
SRM/4/FANPLGIN:Fan in slot [ULONG] is plugged in.
Description
A fan is installed.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Possible Causes
A fan is installed.
Procedure
l
----End
95.25 SRM/3/FANPLUGOUT
Message
SRM/3/FANPLUGOUT:Fan in slot [ULONG] is pulled out.
Description
A fan is removed.
Parameters
Parameter Name
Parameter Meaning
[ULONG]
Issue 07 (2014-07-30)

1117

Log Reference
95 SRM
Possible Causes
1:
The fan is not installed properly.
2:
The fan is removed manually.
Procedure
Step 1 Check whether the fan is removed manually.
l If so, no action is required.
l If not, go to step 2.
Step 2 Check whether the fan is installed properly.
l If not, reinstall the fan.
l If so, go to step 3.
Step 3 Check whether the device has detected the fan.
----End
95.26 SRM/3/LIGHT_FAULT
Message
SRM/3/LIGHT_FAULT:[STRING] indicator is abnormal.
Description
An interface card indicator or power supply indicator is faulty.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the name of the interface card or power supply unit.
Possible Causes
An interface card indicator or power supply indicator is faulty.
Issue 07 (2014-07-30)

1118

Log Reference
95 SRM
Procedure
l
Collect the alarm information, log information, and configuration information, and then
----End
95.27 SRM/3/LIGHT_FAULT_RESUME
Message
SRM/3/LIGHT_FAULT_RESUME:[STRING] indicator is normal.
Description
The interface card indicator or power supply indicator is recovered.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the name of the interface card or power supply unit.
Possible Causes
The interface card indicator or power supply indicator is recovered.
Procedure
l
----End
95.28 SRM/3/INOUT
Message
SRM/3/INOUT:The optical module on interface [STRING1] is plugged [STRING2].
Description
The optical module on the interface is inserted or removed.
Parameters
STRING1
Issue 07 (2014-07-30)
Indicates the interface number.

1119

Log Reference
95 SRM

STRING2
Indicates the optical module status, IN or OUT. This parameter

determines whether the optical module is inserted or removed.
Possible Causes
An optical module is inserted into or removed from an interface.
NOTE
Each CSFP optical module occupies two interfaces; therefore, two logs are generated when a CSFP optical
module is removed.
Procedure
l
This log message notifies that the optical module status changes. If the optical module status
changes unexpectedly, insert or remove the optical module as required.
----End
95.29 SRM/6/SRM_LOGID_STARTUP_VERSION
Message
SRM/6/SRM_LOGID_STARTUP_VERSION:Load information : The current software version
in slot [slot-id] is [software-version]. The patch version is [patch-version].
Description
Load information, which provides the software and patch versions in the current restart of the
device.
Parameters
Parameter Name
Parameter Meaning
[slot-id]
Slot ID of the device.
[software-version]
Software version number.
[patch-version]
Patch version.
Possible Causes
This log records the version information of the current startup.
Procedure
l
----End
Issue 07 (2014-07-30)

1120

Log Reference
95 SRM
95.30 SRM/1/POWEXC
Message
SRM/1/POWEXC:Power supply in slot [ULONG] is abnormal, or no current input.
Description
A power supply unit is faulty.
Parameters
Parameter Name
Parameter Meaning
slot [ULONG]
Indicates the slot ID of the power supply unit.
Possible Causes
A power supply unit is faulty.
Procedure
l
Run the display power command to check whether the power supply unit status is normal.
If the power supply unit is not present, install the power supply unit properly.
If the power supply unit is present and in normal state, contact Huawei technical support
personnel.
----End
95.31 SRM/6/POWON
Message
SRM/6/POWON:Power supply in slot [ULONG] works normally.
Description
The power supply unit is recovered.
Parameters
Parameter Name
Parameter Meaning
slot [ULONG]
Possible Causes
The power supply unit is recovered.
Issue 07 (2014-07-30)

1121

Log Reference
95 SRM
Procedure
l
----End
95.32 SRM/4/POWPLGIN
Message
SRM/4/POWPLGIN:Power supply in slot [ULONG] is plugged in.
Description
A power supply unit is installed.
Parameters
Parameter Name
Parameter Meaning
slot [ULONG]
Possible Causes
A power supply unit is installed.
Procedure
l
----End
95.33 SRM/4/POWPULOUT
Message
SRM/4/POWPULOUT:Power supply in slot [ULONG] is plugged out.
Description
A power supply unit is removed.
Parameters
Parameter Name
Parameter Meaning
slot [ULONG]
Issue 07 (2014-07-30)

1122

Log Reference
95 SRM
Possible Causes
A power supply unit is removed.
Procedure
Step 1 Check whether the power supply unit is removed manually.
Step 2 Check whether the power supply unit is installed properly.
l If not, install the power supply unit properly.
Step 3 Run the display power command to check whether the power supply unit is present.
l If not, install the power supply unit properly.
Step 4 If the fault persists, contact Huawei technical support personnel.
----End
95.34 SRM/3/TXPOWER_EXCEEDMAJOR
Message
SRM/3/TXPOWER_EXCEEDMAJOR:Optical module in interface [STRING] exception, TX
power is too high.
Description
The transmit power of an optical module is too high.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates an interface name.
Possible Causes
The transmit power of the optical module exceeds the upper threshold.
Procedure
l
Run the display transceiver verbose command in the user view to check whether the
transmit power of the optical module is within the allowed range.
Issue 07 (2014-07-30)

1123

Log Reference
95 SRM
If the transmit power is within the allowed range, collect the related alarm, log, and
configuration information, and contact Huawei technical support personnel. If the transmit
power is out of the allowed range, replace the optical module.
----End
95.35 SRM/3/RXPOWER_EXCEEDMINOR
Message
SRM/3/RXPOWER_EXCEEDMINOR:Optical module in interface [STRING] exception, RX
power is too low.
Description
The receive power of an optical module is too low.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The receive optical power of the optical module is below the lower threshold.
Procedure
l
receive power of the optical module is within the allowed range.
If the receive power is within the allowed range, collect the related alarm, log, and
configuration information, and contact Huawei technical support personnel. If the receive
----End
95.36 SRM/5/RXPOWER_RESUME
Message
SRM/5/RXPOWER_RESUME:Optical module in interface [STRING], RX power resume.
Description
The receive power of an optical module has restored to the allowed range.
Issue 07 (2014-07-30)

1124

Log Reference
95 SRM
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The receive power of the optical module has restored to the allowed range.
Procedure
l
This alarm is informational, and no action is required.
----End
95.37 SRM/6/SFPCATEGORY_UNKNOW
Message
SRM/6/SFPCATEGORY_UNKNOW:Optical module in slot [ULONG1] port [ULONG2]
exception, bandwidth unknow.
Description
The bandwidth of the optical module on the port is unknown.
Parameters
Parameter Name
Parameter Meaning
ULONG1
Possible Causes
Failed to obtain the bandwidth of the optical module on the port.
Procedure
l
Contact Huawei technical support personnel to check whether the optical module is
working normally.
----End
95.38 SRM/4/STACK_PORT_DOWN
Message
SRM/4/STACK_PORT_DOWN:Stack port [STRING] goes to Down.
Issue 07 (2014-07-30)

1125

Log Reference
95 SRM
Description
A stack interface goes Down.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
A stack interface goes Down.
Procedure
l
Check whether the interface is properly connected and configured. If so, collect the alarm
information, log information, and configuration information, and then contact Huawei
----End
95.39 SRM/4/STACK_PORT_UP
Message
SRM/4/STACK_PORT_UP:Stack port [STRING] goes to UP.
Description
A stack interface goes Up.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
A stack interface goes Up.
Procedure
l
----End
Issue 07 (2014-07-30)

1126

Log Reference
95 SRM
95.40 SRM/3/RXPOWER_EXCEEDMAJOR
Message
SRM/3/RXPOWER_EXCEEDMAJOR:Optical module in interface [STRING] exception, RX
power is too high.
Description
The receive power of an optical module is too high.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The receive optical power of the optical module exceeds the upper threshold.
Procedure
l
receive power of the optical module is within the allowed range.
If the receive power is within the allowed range, collect the related alarm, log, and
configuration information, and contact Huawei technical support personnel. If the receive
----End
95.41 SRM/3/TXPOWER_EXCEEDMINOR
Message
SRM/3/TXPOWER_EXCEEDMINORR:Optical module in interface [STRING] exception, TX
power is too low.
Description
The transmit power of an optical module is too low.
Issue 07 (2014-07-30)

1127

Log Reference
95 SRM
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The transmit power of the optical module on the interface is below the lower threshold.
Procedure
l
transmit power of the optical module is within the allowed range.
If the transmit power is within the allowed range, collect the related alarm, log, and
configuration information, and contact Huawei technical support personnel. If the transmit
----End
95.42 SRM/5/TXPOWER_RESUME
Message
SRM/5/TXPOWER_RESUME:Optical module in interface [STRING], TX power resume.
Description
The transmit optical power of an optical module has restored to the normal range.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
The transmit optical power of the optical module has restored to the normal range.
Procedure
l
This alarm is informational, and no action is required.
----End
Issue 07 (2014-07-30)

1128

Log Reference
95 SRM
95.43 SRM/3/WTFLSHFAIL
Message
SRM/3/WTFLSHFAIL:Failed to write flash memory.
Description
Data cannot be written to the flash memory.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Data cannot be written to the flash memory.
Procedure
l
Collect the alarm information, log information, and configuration information, and then
----End
Issue 07 (2014-07-30)

1129

Log Reference
96 SSH
96
SSH
About This Chapter

96.1 SSH/4/CMD_USERCHOICE
96.2 SSH/5/CMDRECORD
96.3 SSH/4/CONTINUE_KEYEXCHANGE
96.4 SSH/4/OVERWRITE_FILE
96.5 SSH/4/RENAME_FILE
96.6 SSH/4/SAVE_PUBLICKEY
96.7 SSH/4/SAVEAS_PUBLICKEY
96.8 SSH/4/SFTP_REQ_RECORD
96.9 SSH/4/SSH_FAIL
96.10 SSH/4/STELNET_SERVER
96.11 SSH/4/UPDATE_PUBLICKEY
Issue 07 (2014-07-30)

1130

Log Reference
96 SSH
96.1 SSH/4/CMD_USERCHOICE
Message
SSH/4/CMD_USERCHOICE:When deciding whether to run the command [command], the user
chose [Y/N].
Description
When deciding whether to run the command, the user needs to confirm.
Parameters
Parameter Name
Parameter Meaning
[command]
indicates the command.
[Y/N]
prompts a user to confirm the action.
Possible Causes
A confirmation is required for the user to run a command.
Procedure
----End
96.2 SSH/5/CMDRECORD
Message
SSH/5/CMDRECORD:Record command information. (Task=[STRING], IP=[STRING],
User=[STRING], Command="[STRING]")
Description
Logged the command run on the SFTP client.
Parameters
Parameter Name
Parameter Meaning
Task
indicates the name of a task.
IP
indicates an IP address.
Issue 07 (2014-07-30)

1131

Log Reference
96 SSH
Parameter Name
Parameter Meaning
User
indicates the name of a user.
Command
indicates a command.
Possible Causes
The command run on the SFTP client was logged.
Procedure
----End
96.3 SSH/4/CONTINUE_KEYEXCHANGE
Message
SSH/4/CONTINUE_KEYEXCHANGE:The server had not been authenticated in the process
of exchanging keys. When deciding whether to continue, the user chose [Y/N].
Description
The server had not been authenticated in the process of exchanging keys. When deciding whether
to continue, the user need to confirm.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Possible Causes
Procedure
----End
96.4 SSH/4/OVERWRITE_FILE
Issue 07 (2014-07-30)

1132

Log Reference
96 SSH
Message
SSH/4/OVERWRITE_FILE:When deciding whether to overwrite the file [file-name], the user
chose [Y/N].
Description
When deciding whether to overwrite the file , the user need to confirm.
Parameters
Parameter Name
Parameter Meaning
[file-name]
indicates the name of a file.
[Y/N]
Possible Causes
Procedure
----End
96.5 SSH/4/RENAME_FILE
Message
SSH/4/RENAME_FILE:When deciding whether to rename file [old-file-name] as [new-filename], the user chose [Y/N].
Description
When deciding whether to rename the file , the user need to confirm.
Parameters
Parameter Name
Parameter Meaning
[old-file-name]
indicates the old name of a file.
[new-file-name]
indicates the new name of a file.
[Y/N]
Possible Causes
Issue 07 (2014-07-30)

1133

Log Reference
96 SSH
Procedure
----End
96.6 SSH/4/SAVE_PUBLICKEY
Message
SSH/4/SAVE_PUBLICKEY:When deciding whether to save the server's public key [publickey-name], the user chose [Y/N].
Description
When deciding whether to save the server's public key , the user need to confirm.
Parameters
Parameter Name
Parameter Meaning
[public-key-name]
indicates the name of a public key.
[Y/N]
Possible Causes
Procedure
----End
96.7 SSH/4/SAVEAS_PUBLICKEY
Message
SSH/4/SAVEAS_PUBLICKEY:When deciding whether to save the server's public key [publickey-name] as another name, the user chose [Y/N].
Description
When deciding whether to save the server's public key as another name, the user need to confirm.
Issue 07 (2014-07-30)

1134

Log Reference
96 SSH
Parameters
Parameter Name
Parameter Meaning
[public-key-name]
[Y/N]
Possible Causes
Procedure
----End
96.8 SSH/4/SFTP_REQ_RECORD
Message
SSH/4/SFTP_REQ_RECORD:The SFTP server received an operation request from a client.
(UserName=[string], IpAddress=[string], VpnInstanceName=[string], Request=[string])
Description
The SFTP server received an operation request from a client.
Parameters
UserName
User name of the SFTP client
IpAddress
IP address of the SFTP client
VpnInstanceName VPN instance name. This parameter is specified if the SFTP user logs in
to the SFTP server using private network routes. This parameter is empty
if the SFTP user logs in to the SFTP server using public network routes.
Request
Type of the operation request sent by the SFTP client
Possible Causes
The user logged in to the SFTP server and performed an operation on the server.
Procedure
----End
Issue 07 (2014-07-30)

1135

Log Reference
96 SSH
96.9 SSH/4/SSH_FAIL
Message
SSH/4/SSH_FAIL: Failed to login through SSH. (IP=[STRING], UserName=[STRING],
Times=[ULONG], FailedReason=[STRING])
Description
An SSH user failed to log in.
Parameters
Parameter Name
Parameter Meaning
IP
IP address of the SSH user
UserName
User name of the SSH user
Times
Number of login failures
FailedReason
Cause for the login failure
Possible Causes
An SSH user failed to log in. Information, including the IP address, user name, and numbers of
the login failures, was logged.
Procedure
Step 1 Based on FailedReason, determine how to rectify the fault.
1.
If FailedReason indicates that the login failed due to an authentication failure, use the
correct user name and password to log in.
2.
If FailedReason indicates that the login failed due to a low SSH user level, perform the
following operations:
a.
Run the display ssh user-information command to view the authentication mode of
the SSH user.
1)
2)
Issue 07 (2014-07-30)
If the authentication mode is RSA or DSA, run the user-interface vty command
to enter the VTY channel to which the user attempts to log in.
1)
Run the display this command to check whether the SSH user is an
administrator.
2)
If the SSH user is not an administrator, run the user privilege level
command to set the SSH user to an administrator.
If the authentication mode is not RSA or DSA, run the aaa command to enter
the AAA view. If the SSH user is authenticated by a remote server, set the SSH
user to an administrator on the remote server.
1136

Log Reference
96 SSH
3)
Run the display this command to check whether the SSH user is authenticated
by a remote or local server.
4)
If the SSH user is authenticated by a local server and the SSH user is not an
administrator, run the user privilege level command to set the SSH user to an
administrator.
5)
If the SSH user is authenticated by a remote server, set the SSH user to an
administrator on the remote server.
Step 2 If the problem persists, contact Huawei technical support personnel.

----End
96.10 SSH/4/STELNET_SERVER
Message
SSH/4/STELNET_SERVER:The STELNET server is not started. Use the command' stelnet
server enable' to start it.
Description
The STelnet service was disabled on the server when the SSH client requested the STelnet
service.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The STelnet service was disabled on the server when the SSH client requested the STelnet
service.
Procedure
Step 1 Enable the STelnet service on the server.
----End
96.11 SSH/4/UPDATE_PUBLICKEY
Message
SSH/4/UPDATE_PUBLICKEY:When deciding whether to update the key [public-key-name]
which already existed, the user chose [Y/N].
Issue 07 (2014-07-30)

1137

Log Reference
96 SSH
Description
When deciding whether to update the key which already existed, the user need to confirm.
Parameters
Parameter Name
Parameter Meaning
[public-key-name]
[Y/N]
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

1138

Log Reference
97 SW_SNPG
97
SW_SNPG
About This Chapter

97.1 SW_SNPG/4/IGMP_PKT_INVALID
97.2 SW_SNPG/4/IGMPV1_PKT
97.4 SW_SNPG/3/L2PORT_INVALID
97.5 SW_SNPG/4/PORT_EVT_IGNORE
97.6 SW_SNPG/6/PORT_LEAVE
97.7 SW_SNPG/4/PORT_EXCEED
97.8 SW_SNPG/4/RPC_FAIL
97.9 SW_SNPG/4/ROUTER_PORT_EXCEED
97.10 SW_SNPG/3/TASK_INVALID
Issue 07 (2014-07-30)

1139

Log Reference
97 SW_SNPG
97.1 SW_SNPG/4/IGMP_PKT_INVALID
Message
SW_SNPG/4/IGMP_PKT_INVALID:Received an IGMP packet from [STRING] to [STRING]
with unsupported type. (Type=[LONG])
Description
The switch does not support the type of received IGMP message.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the source IP address of the message.
[STRING]
Indicates the destination IP address of the message.
[ULONG]
Indicates the IGMP message type.
Possible Causes
The switch does not support the type of received IGMP message.
Procedure
----End
Message
SW_SNPG/4/IGMPV1_PKT:Received IGMP version '[LONG]' query on IGMPv1 port. (Port=
[STRING])
Description
An IGMPv1 enabled interface receives an IGMP query message with a higher version.
Parameters
[LONG]
Issue 07 (2014-07-30)
Indicates the version of the received IGMP query message.

1140

Log Reference
97 SW_SNPG

[STRING]
Indicates the name of the interface that has received the IGMP query
message.
Possible Causes
Procedure
Step 1 Check the IGMP version on the interface.
l If the message version is IGMPv2, set the IGMP snooping version on the interface to
IGMPv2.
l If the message version is IGMPv3, set the IGMP snooping version on the interface to
IGMPv3.
----End
Message
SW_SNPG/4/IGMPV2_PKT:Received IGMP version '[LONG]' query on IGMPv2 port. (Port=
[STRING])
Description
Parameters
[LONG]
Indicates the version of the received IGMP query message.
[STRING]
Indicates the name of the interface that has received the IGMP query
message.
Possible Causes
Procedure
Step 1 Check the IGMP version on the interface.
l If the message needs to be processed, set the IGMP snooping version on the interface to
IGMPv3.
Issue 07 (2014-07-30)

1141

Log Reference
97 SW_SNPG
l If the message does not need to be processed, go to step 2.

Step 2 End.
----End
97.4 SW_SNPG/3/L2PORT_INVALID
Message
An event of port up is ignored due to incorrect state of a physical port in IGMP Snooping.
(L2Port=[STRING])
Description
A port Up event is ignored because the status of the physical interface configured with IGMP
snooping is incorrect.
Parameters
Parameter Name
Parameter Meaning
L2Port
Possible Causes
The IGMP snooping module receives a port Up event, but the interface status is Down in the
display command output.
Procedure
Step 1 Run the display interface brief command to check whether the interface status is flapping.
----End
97.5 SW_SNPG/4/PORT_EVT_IGNORE
Message
SW_SNPG/4/PORT_EVT_IGNORE:An event of port notification is ignored by IGMP
Snooping.
Description
An error occurs in instance information, so a port notification message is ignored.
Issue 07 (2014-07-30)

1142

Log Reference
97 SW_SNPG
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The VRF index is greater than the threshold (1023).
Procedure
Step 1 Ensure that the VRF index is smaller than the threshold (1023).
----End
97.6 SW_SNPG/6/PORT_LEAVE
Message
SW_SNPG/6/PORT_LEAVE:Querier received an IGMP Leave packet. (Group/Port=
[STRING])
Description
The IGMP querier receives an IGMP Leave message.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the address and inbound interface of a multicast group.
Possible Causes
The IGMP querier receives an IGMP Leave message.
Procedure
----End
97.7 SW_SNPG/4/PORT_EXCEED
Message
SW_SNPG/4/PORT_EXCEED:The number of ports exceeded the maximum value.
([STRING])
Issue 07 (2014-07-30)

1143

Log Reference
97 SW_SNPG
Description
The number of outbound interfaces exceeds the upper limit.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the VLAN, VSI, multicast source, or multicast group.
Possible Causes
The number of outbound interfaces exceeds the upper limit.
Procedure
----End
97.8 SW_SNPG/4/RPC_FAIL
Message
SW_SNPG/4/RPC_FAIL:Failed to send the configuration to LPU because of the failure of RPC.
(Slot=[STRING])
Description
Configuration cannot be delivered because of RPC failure.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Possible Causes
1:
The board is not registered.
2:
The RPC channel is blocked.
Procedure
Issue 07 (2014-07-30)

1144

Log Reference
97 SW_SNPG
Step 2 View the RPC-related logs to check whether an RPC message sending failure log is recorded.
Step 3 Contact Huawei technical personnel and provide the collected information.
----End
97.9 SW_SNPG/4/ROUTER_PORT_EXCEED
Message
SW_SNPG/4/ROUTER_PORT_EXCEED:The number of router ports exceeded the maximum
value. ([STRING])
Description
The number of router interfaces exceeds the upper limit.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the VLAN or VSI.
Possible Causes
The number of router interfaces in the VLAN or VSI exceeds the upper limit.
Procedure
Step 1 Display router interface information in the multicast group: display l2-multicast forwarding
{ vlan vlan-id | vsi vsi-name } group-address group-address
Step 2 Check whether the number of outbound interfaces exceeds the upper limit.
Step 3 Delete unneeded static interfaces: undo l2-multicast static group group-address groupaddress
----End
97.10 SW_SNPG/3/TASK_INVALID
Message
SW_SNPG/3/TASK_INVALID:An event of port notification is ignored by IGMP Snooping for
the task of IGMP Snooping is invalid.
Issue 07 (2014-07-30)

1145

Log Reference
97 SW_SNPG
Description
Task information or port information is invalid, so the port notification message is ignored.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Task information cannot be obtained or port information is invalid.
Procedure
Step 1 View the task status.
Step 2 View and collect the log related to task initialization.
Step 3 View and collect error information.
Step 4 Contact Huawei technical personnel and provide the collected information.
----End
Issue 07 (2014-07-30)

1146

Log Reference
98 TAD
98
TAD
About This Chapter

98.1 TAD/6/ALARMAGING
98.2 TAD/6/ALARMCEILING
98.3 TAD/6/ALARMDAMP
98.4 TAD/6/ALARMDOWN
98.5 TAD/6/ALARMPULSE
98.6 TAD/6/ALARMREUSE
98.7 TAD/6/ALARMUP
98.8 TAD/6/FILTERTIMER
98.9 TAD/4/IFDOWN
98.10 TAD/4/IFUP
Issue 07 (2014-07-30)

1147

Log Reference
98 TAD
98.1 TAD/6/ALARMAGING
Message
TAD/6/ALARMAGING:On interface [interface-name], [alarm-type] aged.
Description
The alarm on the interface was aged.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[alarm-type]
Indicates the alarm type.
Possible Causes
The alarm was aged.
Procedure
----End
98.2 TAD/6/ALARMCEILING
Message
TAD/6/ALARMCEILING:On interface [interface-name], [alarm-type] reached the ceiling.
Description
The number of alarm on the interface reached the maximum.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[alarm-type]
Issue 07 (2014-07-30)

1148

Log Reference
98 TAD
Possible Causes
The figure of merit of the alarm reached the ceiling threshold.
Procedure
----End
98.3 TAD/6/ALARMDAMP
Message
TAD/6/ALARMDAMP:On interface [interface-name], [alarm-type] was suppressed.
Description
The alarm on the interface was suppressed.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[alarm-type]
Possible Causes
The alarm was suppressed.
Procedure
----End
98.4 TAD/6/ALARMDOWN
Message
TAD/6/ALARMDOWN:On interface [interface-name], [alarm-type] disappeared.
Description
The alarm on the interface was cleared.
Issue 07 (2014-07-30)

1149

Log Reference
98 TAD
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[alarm-type]
Possible Causes
The alarm clearance signal sent by the lower layer was received.
Procedure
----End
98.5 TAD/6/ALARMPULSE
Message
TAD/6/ALARMPULSE:On interface [interface-name], [alarm-type] was filtered.
Description
The alarm on the interface was filtered.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[alarm-type]
Possible Causes
The alarm was filtered.
Procedure
----End
98.6 TAD/6/ALARMREUSE
Issue 07 (2014-07-30)

1150

Log Reference
98 TAD
Message
TAD/6/ALARMREUSE:On interface [interface-name], [alarm-type] was reused.
Description
The alarm on the interface became available.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[alarm-type]
Possible Causes
The alarm entered the available state.
Procedure
----End
98.7 TAD/6/ALARMUP
Message
TAD/6/ALARMUP:On interface [interface-name], [alarm-type] generated.
Description
An alarm was generated on the interface.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
[alarm-type]
Possible Causes
The alarm generation signal sent by the lower layer was received.
Issue 07 (2014-07-30)

1151

Log Reference
98 TAD
Procedure
----End
98.8 TAD/6/FILTERTIMER
Message
TAD/6/FILTERTIMER:Filter timer of [alarm-type] on interface [interface-name] expired.
Description
The alarm filtering timer timed out on the interface.
Parameters
Parameter Name
Parameter Meaning
[alarm-type]
[interface-name]
Possible Causes
The filtering timer timed out.
Procedure
----End
98.9 TAD/4/IFDOWN
Message
TAD/4/IFDOWN:"Owing to the alarm message(s), [interface-name] went Down. (AlarmType=
[STRING])"
Description
An alarm is generated, and the interface cannot be used.
Issue 07 (2014-07-30)

1152

Log Reference
98 TAD
Parameters
Parameter Name
Parameter Meaning
[interface-name]
AlarmType
Possible Causes
Procedure
----End
98.10 TAD/4/IFUP
Message
TAD/4/IFUP:"Owing to the alarm message(s), [interface-name] went Up. (AlarmType=
[STRING])"
Description
The alarm is cleared, and the interface is restored.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
AlarmType
Possible Causes
Procedure
----End
Issue 07 (2014-07-30)

1153

Log Reference
99 TFTP
99
TFTP
About This Chapter

99.1 TFTP/4/OVERWRITE
Issue 07 (2014-07-30)

1154

Log Reference
99 TFTP
99.1 TFTP/4/OVERWRITE
Message
TFTP/4/OVERWRITE: The user chose [Y/N] when deciding whether to overwrite current
configuration file.
Description
The user decided whether to overwrite the configuration file.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
prompts the user to confirm the action.
Possible Causes
The user decided whether to overwrite the configuration file.
Procedure
----End
Issue 07 (2014-07-30)

1155

Log Reference
100 TNLM
100
TNLM
About This Chapter

100.1 TNLM/5/ADD_EXTNODE
100.2 TNLM/5/ADD_NODE
100.3 TNLM/5/BINDING
100.4 TNLM/5/DEL_BINDING
100.5 TNLM/4/DEL_NODE
100.6 TNLM/6/FAIL_ALLOCTOKEN
100.7 TNLM/5/FAIL_SETTNLPLY
100.8 TNLM/5/INVALID_POLICY
100.9 TNLM/5/MEM_SHORTAGE
100.10 TNLM/5/NTY_VPN_APPPLCY
100.11 TNLM/5/OLD_LOG
100.12 TNLM/5/REC_L3V_APPPLCY
100.13 TNLM/5/SEARCH_NODE
100.14 TNLM/5/SET_POLICY_NAME
100.15 TNLM/5/TNL_IF_DEL
Issue 07 (2014-07-30)

1156

Log Reference
100 TNLM
100.1 TNLM/5/ADD_EXTNODE
Message
TNLM/5/ADD_EXTNODE:Failed to add the extnode to radix tree(IP address =
[ULONG],Mask = [ULONG]).
Description
Failed to add the external node to the binary tree.
Parameters
Parameter Name
Parameter Meaning
IP address
Mask
Indicates the mask.
Possible Causes
Failed to add the external node to the binary tree.
Procedure
----End
100.2 TNLM/5/ADD_NODE
Message
TNLM/5/ADD_NODE:Failed to add RadixNode to tunnel binding tree(NextHopIpAddr =
[ULONG],TunnelIfIndex = [ULONG]).
Description
Failed to add the node to the tunnel binding tree.
Parameters
Parameter Name
Parameter Meaning
NextHopIpAddr
TunnelIfIndex
Indicates the index of the tunnel interface.
Issue 07 (2014-07-30)

1157

Log Reference
100 TNLM
Possible Causes
Failed to add the node to the tunnel binding tree.
Procedure
----End
100.3 TNLM/5/BINDING
Message
TNLM/5/BINDING:Failed to set tunnel binding(Errcode = [ULONG]).
Description
Tunnel binding failed.
Parameters
Parameter Name
Parameter Meaning
Errcode
Possible Causes
Tunnel binding failed.
Procedure
----End
100.4 TNLM/5/DEL_BINDING
Message
TNLM/5/DEL_BINDING:Failed to delete tunnel binding(PolicyID = [ULONG],IP address =
[ULONG]).
Description
Deleting tunnel binding failed.
Issue 07 (2014-07-30)

1158

Log Reference
100 TNLM
Parameters
Parameter Name
Parameter Meaning
PolicyID
Indicates the ID of the policy.
IP address
Possible Causes
Deleting tunnel binding failed.
Procedure
----End
100.5 TNLM/4/DEL_NODE
Message
TNLM/4/DEL_NODE:It could not delete the all node from the Radix tree(Errcode = [ULONG]).
Description
Nodes on the binary tree cannot be deleted.
Parameters
Parameter Name
Parameter Meaning
Errcode
Possible Causes
Failed to delete nodes on the binary tree.
Procedure
----End
100.6 TNLM/6/FAIL_ALLOCTOKEN
Issue 07 (2014-07-30)

1159

Log Reference
100 TNLM
Message
TNLM/6/FAIL_ALLOCTOKEN:The number of tunnel ID(s) exceeds the maximum value
defined in the PAF file. (AllocationSpace=[STRING])
Description
The number of tunnel IDs exceeded the maximum value specified in the PAF file, and thus the
specified token space failed to be allocated.
Parameters
Parameter Name
Parameter Meaning
AllocationSpace
Indicates the token space to be allocated.
Possible Causes
All tokens of the specified space were already used.
Procedure
----End
100.7 TNLM/5/FAIL_SETTNLPLY
Message
TNLM/5/FAIL_SETTNLPLY:Failed to set tnl-policy of type [type]. Policy name is [policy].
Description
Failed to add the tunneling policy.
Parameters
Parameter Name
Parameter Meaning
[type]
Indicates the type of the tunneling policy.
[policy]
Indicates the name of the tunneling policy.
Possible Causes
Failed to add the tunneling policy.
Issue 07 (2014-07-30)

1160

Log Reference
100 TNLM
Procedure
----End
100.8 TNLM/5/INVALID_POLICY
Message
TNLM/5/INVALID_POLICY:The policy node is null according to policy ID [policy-id].
Description
The tunnel policy node corresponding to the policy ID is null.
Parameters
Parameter Name
Parameter Meaning
[policy-id]
Indicates the tunnel policy ID.
Possible Causes
The tunnel policy node corresponding to the policy ID is null.
Procedure
Step 1 Use the display tunnel-policy [ tunnel-policy-name ] command to view and save the
configuration information of tunnel policies.
Step 3 End.
----End
100.9 TNLM/5/MEM_SHORTAGE
Message
TNLM/5/MEM_SHORTAGE:Memory shortage in [vpn-instance].
Description
Memory was insufficient.
Issue 07 (2014-07-30)

1161

Log Reference
100 TNLM
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
Possible Causes
Memory was insufficient.
Procedure
Step 1 Increase the memory.
----End
100.10 TNLM/5/NTY_VPN_APPPLCY
Message
TNLM/5/NTY_VPN_APPPLCY:Tnlm notify the application module the event of vpn instance
[vpn-instance] using tnl-policy.
Description
The tunnel management module notified the application module of the event that the VPN
instance adopted the tunnel policy.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
Possible Causes
The tunnel management module notified the application module of the event that the VPN
instance adopted the tunnel policy.
Procedure
----End
100.11 TNLM/5/OLD_LOG
Issue 07 (2014-07-30)

1162

Log Reference
100 TNLM
Message
TNLM/5/OLD_LOG:Reserved for old log.
Description
Reserve the log for the old log.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
None.
Procedure
----End
100.12 TNLM/5/REC_L3V_APPPLCY
Message
TNLM/5/REC_L3V_APPPLCY:Vpn instance [vpn-instance] uses tnl-policy [policy], event
type is [event].
Description
This log message recorded the information about the tunnel policy adopted by the VPN instance.
Parameters
Parameter Name
Parameter Meaning
[vpn-instance]
[policy]
Indicates the name of the tunneling policy.
[event]
Possible Causes
This log message recorded the information about the tunnel policy adopted by the VPN instance.
Issue 07 (2014-07-30)

1163

Log Reference
100 TNLM
Procedure
----End
100.13 TNLM/5/SEARCH_NODE
Message
TNLM/5/SEARCH_NODE:Failed to search RadixNode from tunnel binding tree
(NextHopIpAddr = [ULONG])
Description
Failed to search the tunnel binding tree for the node.
Parameters
Parameter Name
Parameter Meaning
NextHopIpAddr
Possible Causes
Failed to search the tunnel binding tree for the node.
Procedure
----End
100.14 TNLM/5/SET_POLICY_NAME
Message
TNLM/5/SET_POLICY_NAME:Failed to set the tunnel policy name.(ReturnValue=
[ULONG])
Description
The value returned by the function includes VOS_ERR, TNLM_INFO_PolicyNotAvail,
TNLM_INFO_LowMemory, and TNLM_MEMORY_FAILURE.
Issue 07 (2014-07-30)

1164

Log Reference
100 TNLM
Parameters
Parameter Name
Parameter Meaning
ReturnValue
Indicates the value returned by the function.
Possible Causes
Failed to add the tunnel policy.
Procedure
Step 1 Run the tunnel-policy tunnel-policy-name command in the system view to save the log
information.
Step 3 End.
----End
100.15 TNLM/5/TNL_IF_DEL
Message
TNLM/5/TNL_IF_DEL:The event that the tunnel interface was deleted was processed.
(IfnetIndex=[STRING])
Description
The event that the tunnel interface was deleted was processed.
Parameters
Parameter Name
Parameter Meaning
IfnetIndex
Possible Causes
The event that the tunnel interface was deleted was processed.
Procedure
----End
Issue 07 (2014-07-30)

1165

Log Reference
101 TRAFSTAT
101
TRAFSTAT
About This Chapter

101.1 TRAFSTAT/6/BATCH_BACKUP_BEGIN
101.2 TRAFSTAT/6/BATCH_BACKUP_END
101.3 TRAFSTAT/6/L3V_RCVSTAT
101.4 TRAFSTAT/6/L3V_RESETSTATALL
101.5 TRAFSTAT/6/L3V_RESETSTATVRF
101.6 TRAFSTAT/6/L3V_SUCSTATDIS
101.7 TRAFSTAT/6/L3V_SUCSTATEN
101.8 TRAFSTAT/5/VSIDISABLE
101.9 TRAFSTAT/5/VSIDISABLEPW
101.10 TRAFSTAT/5/VSIENABLE
101.11 TRAFSTAT/5/VSIENABLEPW
101.12 TRAFSTAT/5/VSIRESET
101.13 TRAFSTAT/5/VSIRESETALL
101.14 TRAFSTAT/5/VSIUNDOL2VPN
101.15 TRAFSTAT/5/VSIUNDOVSI
Issue 07 (2014-07-30)

1166

Log Reference
101 TRAFSTAT
101.1 TRAFSTAT/6/BATCH_BACKUP_BEGIN
Message
TRAFSTAT/6/BATCH_BACKUP_BEGIN:Batch backup begin.
Description
Started to back up data in batches to the backup main control board.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
Backed up data in batches.
Procedure
l
----End
101.2 TRAFSTAT/6/BATCH_BACKUP_END
Message
TRAFSTAT/6/BATCH_BACKUP_END:Batch backup end.
Description
Backing up data in batches to the slave main control board finished.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
Backed up data in batches.
Issue 07 (2014-07-30)

1167

Log Reference
101 TRAFSTAT
Procedure
l
----End
101.3 TRAFSTAT/6/L3V_RCVSTAT
Message
TRAFSTAT/6/L3V_RCVSTAT:The L3VPN statistics had been received. (VrfId=[ULONG])
Description
L3VPN traffic statistics were obtained.
Parameters
Parameter Name
Parameter Meaning
VrfId
Possible Causes
The traffic statistics timer timed out.
Procedure
l
----End
101.4 TRAFSTAT/6/L3V_RESETSTATALL
Message
TRAFSTAT/6/L3V_RESETSTATALL:Succeeded in resetting all the statistical information of
L3VPN.
Description
Succeeded in resetting all statistics about L3VPN traffic.
Parameters
Parameter Name
Parameter Meaning
None.
None.
Issue 07 (2014-07-30)

1168

Log Reference
101 TRAFSTAT
Possible Causes
Succeeded in resetting all statistics about L3VPN traffic.
Procedure
l
----End
101.5 TRAFSTAT/6/L3V_RESETSTATVRF
Message
TRAFSTAT/6/L3V_RESETSTATVRF:Succeeded in resetting the statistics of L3VPN traffic.
(VrfId=[ULONG])
Description
Succeeded in resetting the specified statistics about L3VPN traffic.
Parameters
Parameter Name
Parameter Meaning
VrfId
Possible Causes
Succeeded in resetting the specified statistics about L3VPN traffic.
Procedure
l
----End
101.6 TRAFSTAT/6/L3V_SUCSTATDIS
Message
TRAFSTAT/6/L3V_SUCSTATDIS:Succeeded in disabling the statistical function of L3VPN.
(VrfId=[ULONG])
Description
Succeeded in disabling collection of L3VPN traffic statistics.
Issue 07 (2014-07-30)

1169

Log Reference
101 TRAFSTAT
Parameters
Parameter Name
Parameter Meaning
VrfId
Possible Causes
Collection of L3VPN traffic statistics was disabled.
Procedure
l
----End
101.7 TRAFSTAT/6/L3V_SUCSTATEN
Message
TRAFSTAT/6/L3V_SUCSTATEN:Succeeded in enabling the statistical function of L3VPN.
(VrfId=[ULONG])
Description
Succeeded in enabling collection of L3VPN traffic statistics.
Parameters
Parameter Name
Parameter Meaning
VrfId
Possible Causes
Collection of L3VPN traffic statistics was enabled.
Procedure
l
----End
101.8 TRAFSTAT/5/VSIDISABLE
Message
TRAFSTAT/5/VSIDISABLE:The statistical function of the PW was not enabled. (VsiName=
[STRING], PeerAddress=[STRING], VcId/RemoteSiteId=[ULONG])
Issue 07 (2014-07-30)

1170

Log Reference
101 TRAFSTAT
Description
When a user disabled statistics collection, the system prompted the user that statistics collection
was not enabled on the PW.
Parameters
Parameter Name
Parameter Meaning
VsiName
PeerAddress
Indicates the IP address of the peer end.
VcId/RemoteSiteId
Indicates the VC ID or the IP address of the remote end.
Possible Causes
The statistical function of the PW was not enabled.
Procedure
Step 1 Use command display current-configuration configuration vsi to check if the statistical
function of the PW is enabled, and no further action is required.
----End
101.9 TRAFSTAT/5/VSIDISABLEPW
Message
TRAFSTAT/5/VSIDISABLEPW:Succeeded in disabling PW statistics. (VsiName=[STRING],
PeerAddress=[STRING], VcId/RemoteSiteId=[ULONG])
Description
Finished disabling PW statistics.
Parameters
Parameter Name
Parameter Meaning
VsiName
PeerAddress
VcId/RemoteSiteId
Possible Causes
Succeeded in disabling PW statistics.
Issue 07 (2014-07-30)

1171

Log Reference
101 TRAFSTAT
Procedure
----End
101.10 TRAFSTAT/5/VSIENABLE
Message
TRAFSTAT/5/VSIENABLE:The statistical function of the PW had been enabled. (VsiName=
[STRING], PeerAddress=[STRING], VcId/RemoteSiteId=[ULONG])
Description
When a user enabled statistics collection, the system prompted the user that statistics collection
was enabled on the PW.
Parameters
Parameter Name
Parameter Meaning
VsiName
PeerAddress
VcId/RemoteSiteId
Possible Causes
The command was reconfigured.
Procedure
l
Run the display current-configuration configuration vsi command to check whether

statistics collection is configured, and no further action is required.
----End
101.11 TRAFSTAT/5/VSIENABLEPW
Message
TRAFSTAT/5/VSIENABLEPW:Succeeded in enabling PW statistics. (VsiName=[STRING],
Description
Finished enabling PW statistics.
Issue 07 (2014-07-30)

1172

Log Reference
101 TRAFSTAT
Parameters
Parameter Name
Parameter Meaning
VsiName
PeerAddress
VcId/RemoteSiteId
Possible Causes
Succeeded in enabling PW statistics.
Procedure
----End
101.12 TRAFSTAT/5/VSIRESET
Message
TRAFSTAT/5/VSIRESET:Succeeded in resetting PW statistics. (VsiName=[STRING],
Description
Reset designated PW statistics.
Parameters
Parameter Name
Parameter Meaning
VsiName
PeerAddress
VcId/RemoteSiteId
Possible Causes
Succeeded in resetting PW statistics.
Procedure
----End
Issue 07 (2014-07-30)

1173

Log Reference
101 TRAFSTAT
101.13 TRAFSTAT/5/VSIRESETALL
Message
TRAFSTAT/5/VSIRESETALL:Succeeded in resetting all PW statistics.
Description
Reset all PW statistics.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Succeeded in resetting all PW statistics.
Procedure
----End
101.14 TRAFSTAT/5/VSIUNDOL2VPN
Message
TRAFSTAT/5/VSIUNDOL2VPN:The statistics of all PW were deleted because L2VPN was
disable.
Description
L2VPN was disabled.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
L2VPN was disabled.
Issue 07 (2014-07-30)

1174

Log Reference
101 TRAFSTAT
Procedure
----End
101.15 TRAFSTAT/5/VSIUNDOVSI
Message
TRAFSTAT/5/VSIUNDOVSI:The statistics of PW were deleted because VSI was deleted.
Description
Undo VSI.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
VSI was deleted.
Procedure
----End
Issue 07 (2014-07-30)

1175

Log Reference
102 TRUNK
102
TRUNK
About This Chapter

102.1 TRUNK/5/BACKSTATE_CHANGE
102.2 TRUNK/5/MEMBER_DOWN
102.3 TRUNK/5/MEMBER_UP
102.4 TRUNK/5/STAT_INACT_TO_ACT
102.5 TRUNK/5/TRUNKDOWN
102.6 TRUNK/5/TRUNKUP
Issue 07 (2014-07-30)

1176

Log Reference
102 TRUNK
102.1 TRUNK/5/BACKSTATE_CHANGE
Message
TRUNK/5/BACKSTATE_CHANGE:The working status of the backup trunk changed.
(TrunkName=[STRING], Status=[ULONG])
Description
Status of the trunk (master or backup) in manual 1:1 master/backup mode changed.
Parameters
Parameter Name
Parameter Meaning
TrunkName
Name of the trunk interface
Status
Status of the trunk (master or backup)
Possible Causes
1.
The main interface for forwarding data was shut down in manual 1:1 master/backup mode.
2.
The main interface for forwarding data exited the trunk in manual 1:1 master/backup mode.
3.
The backup interface for forwarding data was shut down in manual 1:1 master/backup mode.
4.
The backup interface for forwarding data exited the trunk in manual 1:1 master/backup mode.
5.
The protect-switch command was run in manual 1:1 master/backup mode to switch the active
interface and inactive interface of the trunk.
Procedure
Step 1 When the working status of the trunk in manual 1:1 master/backup mode goes Master or Backup,
the displayed log message indicates a normal situation, and no action is required.
Step 2 When the working status of the trunk in manual 1:1 master/backup mode goes Initial, check
status the trunk member interfaces.
l If the two member interfaces in manual 1:1 master/backup mode are backup interfaces in the
Up state, configure one of the interfaces as the port-master.
Issue 07 (2014-07-30)

1177

Log Reference
102 TRUNK
l If the two member interfaces in manual 1:1 master/backup mode are in the Down state, check
whether the two member interfaces and their corresponding interface on the peer device are
shut down. If yes, run the undo shutdown command on the interfaces. If not, the link is
faulty and you need to replace the cable connecting to the interface.
l If there is only one member interface in manual 1:1 master/backup mode and the member
interface is a backup interface in the Up state, configure the interface as the port-master.
l If there is only one member interface in manual 1:1 master/backup mode and the member
interface is a master interface in the Down state, check whether the interface and its
corresponding interface on the peer device are shut down. If yes, run the undo shutdown
command on the interfaces. If not, the link is faulty and you need to replace the cable
connecting to the interface.
If the log message is still generated, collect information about the configuration and log and
----End
102.2 TRUNK/5/MEMBER_DOWN
Message
TRUNK/5/MEMBER_DOWN:The status of the trunk member went Down. (TrunkName=
Description
The status of member port is Down.
Parameters
Parameter Name
Parameter Meaning
TrunkName
PortName
indicates the name of a member interface.
Possible Causes
Cause:
The member interface goes Down.
Procedure
Step 1 Run the display this interface command in the interface view to check whether the link is
normal.
1.
If so, go to Step 2.
2.
If the interface is in the Down state, check whether the physical connection is correct.
Issue 07 (2014-07-30)

1178

Log Reference
102 TRUNK

----End
102.3 TRUNK/5/MEMBER_UP
Message
TRUNK/5/MEMBER_UP:The status of the trunk member went Up. (TrunkName=[STRING],
PortName=[STRING])
Description
The status of member port is Up.
Parameters
Parameter Name
Parameter Meaning
TrunkName
Indicates the name of a trunk interface.
PortName
Indicates the name of a member interface.
Possible Causes
Cause:
The member interface goes Up.
Procedure
----End
102.4 TRUNK/5/STAT_INACT_TO_ACT
Message
TRUNK/5/STAT_INACT_TO_ACT:The trunk port changed from inactive to active.
(TrunkName=[STRING], PortName=[STRING])
Description
The member port changed from inactive to active.
Issue 07 (2014-07-30)

1179

Log Reference
102 TRUNK
Parameters
Parameter Name
Parameter Meaning
PortName
TrunkName
Possible Causes
The member port changed from inactive to active.
Procedure
----End
102.5 TRUNK/5/TRUNKDOWN
Message
TRUNK/5/TRUNKDOWN:The status of interface [interface-name] turns Down.
Description
The trunk interface went Down.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
1. The number of trunk member interfaces that are in the Up state is smaller than the minimum
number of activated links set on the trunk interface. The state of the trunk interface turns down.
2. When the trunk interface is configured with the LACP protocol, the number of trunk member
interfaces that are in the Select state is smaller than the minimum number of activated links set
on the trunk interface. The state of the trunk interface turns down.
Procedure
----End
Issue 07 (2014-07-30)

1180

Log Reference
102 TRUNK
102.6 TRUNK/5/TRUNKUP
Message
TRUNK/5/TRUNKUP:The status of interface [interface-name] turns Up.
Description
The trunk interface went Up.
Parameters
Parameter Name
Parameter Meaning
[interface-name]
Possible Causes
1. The number of trunk member interfaces that are in the Up state is greater than the minimum
number of activated links set on the trunk interface. The state of trunk interface turns Up.
2. When the trunk interface is configured with the LACP protocol, the number of trunk member
interfaces that are in the Select state is greater than the minimum number of activated links set
on the trunk interface. The state of trunk interface turns Up.
Procedure
----End
Issue 07 (2014-07-30)

1181

Log Reference
103 TUNNEL
103
TUNNEL
About This Chapter

103.1 TUNNEL/6/HOT_INSERT
103.2 TUNNEL/6/HOT_REMOVE
Issue 07 (2014-07-30)

1182

Log Reference
103 TUNNEL
103.1 TUNNEL/6/HOT_INSERT
Message
TUNNEL/6/HOT_INSERT:IFNET module informs tunnel that slot [SlotId] has been inserted.
Description
The interface board was hot plugged.
Parameters
Parameter Name
Parameter Meaning
SlotId
indicates the ID of the slot which is hot unplugged.
Possible Causes
The interface board was hot unplugged.
Procedure
l
----End
103.2 TUNNEL/6/HOT_REMOVE
Message
TUNNEL/6/HOT_REMOVE:IFNET module informs tunnel that slot [SlotId] has been
removed.
Description
The interface board was hot unplugged.
Parameters
Parameter Name
Parameter Meaning
SlotId
indicates the ID of the slot which is hot plugged.
Possible Causes
The interface board was hot plugged.
Issue 07 (2014-07-30)

1183

Log Reference
103 TUNNEL
Procedure
l
----End
Issue 07 (2014-07-30)

1184

Log Reference
104 TUNN_PS
104
TUNN_PS
About This Chapter

104.1 TUNN_PS/5/BATCH_BKP_SUCCESS
104.2 TUNN_PS/4/CLEAR_SIGNAL_FAIL
104.3 TUNN_PS/2/DEL_PS_PTUNN_FAIL
104.4 TUNN_PS/2/DEL_PS_WTUNN_FAIL
104.5 TUNN_PS/2/INFO_CMD_DISP
104.6 TUNN_PS/6/NOTIFY_DELETE_AUTOTUNNEL
104.7 TUNN_PS/6/NOTIFY_VPLS
104.8 TUNN_PS/2/PTUNN_ID_INVALID
104.9 TUNN_PS/1/REAL_BKP_MEM_FAIL
104.10 TUNN_PS/5/SMOOTH_SUCCESS
104.11 TUNN_PS/3/SWITCH_FAIL_SMOOTH
104.12 TUNN_PS/2/TUNN_ID_CFG_FAIL
104.13 TUNN_PS/2/WTUNN_ID_INVALID
Issue 07 (2014-07-30)

1185

Log Reference
104 TUNN_PS
104.1 TUNN_PS/5/BATCH_BKP_SUCCESS
Message
TUNN_PS/5/BATCH_BKP_SUCCESS:Tunnel PS finished batch backup successfully.
Description
The batch backup of the protection group ended.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The batch backup of the protection group ended.
Procedure
----End
104.2 TUNN_PS/4/CLEAR_SIGNAL_FAIL
Message
TUNN_PS/4/CLEAR_SIGNAL_FAIL:Can not clear the Signal-Fail.
Description
The current switching result is signaling switching, and thus signaling switching cannot be
cleared.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The signaling switching command is incorrect.
Issue 07 (2014-07-30)

1186

Log Reference
104 TUNN_PS
Procedure
Step 1 Run the display current-configuration command to check whether the configuration is correct.
----End
104.3 TUNN_PS/2/DEL_PS_PTUNN_FAIL
Message
TUNN_PS/2/DEL_PS_PTUNN_FAIL:Failed to get the protection tunnel when delteing
protection group! (Index=[ULONG])
Description
The protection tunnel cannot be found during the deletion of the protection group.
Parameters
Parameter Name
Parameter Meaning
Index
indicates the index of a protection tunnel.
Possible Causes
The backup LSP cannot be found.
Procedure
Step 1 Check whether the configuration of the protection group is correct. If incorrect, reconfigure the
protection group.
----End
104.4 TUNN_PS/2/DEL_PS_WTUNN_FAIL
Message
TUNN_PS/2/DEL_PS_WTUNN_FAIL:Failed to get the work tunnel when delteing protection
group! (Index=[ULONG])
Description
The working tunnel cannot be found during the deletion of the protection group.
Issue 07 (2014-07-30)

1187

Log Reference
104 TUNN_PS
Parameters
Parameter Name
Parameter Meaning
Index
Possible Causes
During the deletion of the protection group, information about the working tunnel cannot be
found according to the index of the working tunnel.
Procedure
Step 1 Check whether the configuration of the protection group is correct.
Step 2 Check whether the status of the protection tunnel is normal.
Step 3 Collect the error information prompted by the system.
----End
104.5 TUNN_PS/2/INFO_CMD_DISP
Message
TUNN_PS/2/INFO_CMD_DISP:Cann't get the cr-lsp when executing the command of display!
Description
The CR-LSP cannot be found when the display command was processed.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The interface information obtained according to the working tunnel ID was null, and information
about the CR-LSP in the interface information was null.
Procedure
Step 1 Check whether the configuration of the protection group is correct.
Step 2 If the configuration is incorrect, reconfigure the protection group.
----End
Issue 07 (2014-07-30)

1188

Log Reference
104 TUNN_PS
104.6 TUNN_PS/6/NOTIFY_DELETE_AUTOTUNNEL
Message
TUNN_PS/6/NOTIFY_DELETE_AUTOTUNNEL:Receive Delete Auto Frr Tunnel message!
(ulIfIndex=[ULONG])
Description
Received the Delete Auto FRR Tunnel message.
Parameters
Parameter Name
Parameter Meaning
ulIfIndex
indicates the index of an interface.
Possible Causes
Received the Delete Auto FRR Tunnel message.
Procedure
----End
104.7 TUNN_PS/6/NOTIFY_VPLS
Message
TUNN_PS/6/NOTIFY_VPLS:Notify LSP status change to VPLS.
Description
The VPLS module was notified that the LSP status changed.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The LSP was unavailable, which was learned from the VPLS module.
Issue 07 (2014-07-30)

1189

Log Reference
104 TUNN_PS
Procedure
Step 1 If this error occurs, the system may be abnormal. Thus, contact Huawei technical support
personnel.
----End
104.8 TUNN_PS/2/PTUNN_ID_INVALID
Message
TUNN_PS/2/PTUNN_ID_INVALID:The protection tunnel's tunnel-id is invalid!
Description
The protection tunnel ID of the protection group did not exist.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The protection tunnel ID of the protection group did not exist.
Procedure
protection group.
----End
104.9 TUNN_PS/1/REAL_BKP_MEM_FAIL
Message
TUNN_PS/1/REAL_BKP_MEM_FAIL:Failed to allocate the momery when processing
realtime backup for PS!
Description
Failed to allocate the momery when processing realtime backup for PS.
Issue 07 (2014-07-30)

1190

Log Reference
104 TUNN_PS
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
1. The memory block applied for was too large, and there was not enough memory to allocate.
2. The memory was used up, and no available memory existed.
Procedure
Step 1 Run display diagnostic-information command and save the display information, contact Huawei
----End
104.10 TUNN_PS/5/SMOOTH_SUCCESS
Message
TUNN_PS/5/SMOOTH_SUCCESS:Tunnel PS finished smoothness successfully.
Description
The data smoothing of the protection group ended.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
After the active/standby switchover, data smoothing ended.
Procedure
----End
104.11 TUNN_PS/3/SWITCH_FAIL_SMOOTH
Issue 07 (2014-07-30)

1191

Log Reference
104 TUNN_PS
Message
TUNN_PS/3/SWITCH_FAIL_SMOOTH:Failed to process protection switch when doing HA
smooth, the work tunnel is [Index]!
Description
Failed to perform the protection switching during data smoothing.
Parameters
Parameter Name
Parameter Meaning
[Index]
Possible Causes
Failed to perform the protection switching during data smoothing.
Procedure
Step 1 If this error occurs, the system may be abnormal. Thus, contact Huawei technical support
personnel.
----End
104.12 TUNN_PS/2/TUNN_ID_CFG_FAIL
Message
TUNN_PS/2/TUNN_ID_CFG_FAIL:The configured tunnel ID of protection tunnel is wrong!
(ID=[ULONG])
Description
The configured ID of the protection tunnel is incorrect.
Parameters
Parameter Name
Parameter Meaning
ID
indicates the number of a protection tunnel.
Possible Causes
The tunnel ID is incorrect.
Issue 07 (2014-07-30)

1192

Log Reference
104 TUNN_PS
Procedure
l
Run the display current-configuration command to check whether the configuration is

correct.
----End
104.13 TUNN_PS/2/WTUNN_ID_INVALID
Message
TUNN_PS/2/WTUNN_ID_INVALID:The work tunnel's tunnel-id is invalid!
Description
The obtained working tunnel ID is invalid.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The working tunnel ID is invalid.
Procedure
protection group.
----End
Issue 07 (2014-07-30)

1193

Log Reference
105 UCM
105
UCM
About This Chapter

105.1 UCM/3/MAXIMUM_HSB_BATCHUPFAIL
105.2 UCM/IC_LEVEL_EMERG/USER_ADDACLFAIL
105.3 UCM/4/USER_ADDUSERGROUPCARFAIL
105.4 UCM/3/VM_USER_ADDACLFAIL
105.5 UCM/5/USER_INFO_AUTHENTICATION
105.6 CM/5/USER_INFO_OFFLINE
Issue 07 (2014-07-30)

1194

Log Reference
105 UCM
105.1 UCM/3/MAXIMUM_HSB_BATCHUPFAIL
Message
UCM/3/MAXIMUM_HSB_BATCHUPFAIL:UserIp: [IPADDR] UserMac: [MAC] hsb
batchup fail because the number of cib has reached maximum.
batchup fail because the number of guest entry has reached maximum.
batchup fail because the number of webs ucib has reached maximum.
Description
HSB backup failed because the number of Cib entries reached the maximum.
HSB backup failed because the number of Guest entries reached the maximum.
HSB backup failed because the number of Webs ucib entries reached the maximum.
Parameters
Parameter Name
Parameter Meaning
UserIp
UserMac
Indicates the MAC address of a user.
Possible Causes
The number of Cib, Guest, or Webs ucib entries reached the maximum.
Procedure
----End
105.2 UCM/IC_LEVEL_EMERG/USER_ADDACLFAIL
Message
UCM/IC_LEVEL_EMERG/USER_ADDACLFAIL: The ACL cannot be added for NAC users.
Ensure that this ACL is supported by the NAC service. ([STRING])
Description
A user fails to be authorized by ACL. Check whether the configured ACL is supported.
Issue 07 (2014-07-30)

1195

Log Reference
105 UCM
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the user ID and MAC address.
Possible Causes
l
The delivered ACL is not included in the RADIUS attribute document.
The ACL failed to be delivered to the physical chip because of the chip error.
Procedure
Step 1 Run the display access-user user-id user-number command to check whether the authorized
ACL is supported according to the RADIUS attribute document.
l If not, deliver the ACL included in the RADIUS attribute document to the user. Run the
display access-user user-id user-number command to check whether the ACL is delivered
successfully.
l If so, the ACL fails to be delivered to the physical chip. Go to step 2.
----End
105.3 UCM/4/USER_ADDUSERGROUPCARFAIL
Message
UCM/4/USER_ADDUSERGROUPCARFAIL:The CAR cannot be added for NAC users.
Ensure that the ACL resource is sufficient. ([STRING])
Description
The CAR setting fails.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the user's IP address and MAC address.
Possible Causes
l
The ACL resource is exhausted.
Procedure
----End
Issue 07 (2014-07-30)

1196

Log Reference
105 UCM
105.4 UCM/3/VM_USER_ADDACLFAIL
Message
UCM/IC_LEVEL_EMERG/USER_ADDACLFAIL: The ACL cannot be added for NAC users.
Ensure that this ACL is supported by the NAC service. ([STRING])
Description
ACL-based authorization fails for a virtual user. Check whether the configured ACL is
supported.
Parameters
Parameter Name
Parameter Meaning
[STRING]
Indicates the user ID and MAC address.
Possible Causes
l
The delivered ACL is not included in the RADIUS attribute document.
The ACL failed to be delivered to the physical chip because of the chip error.
Procedure
Step 1 Run the display access-user user-id user-number command to check whether the authorized
ACL is supported according to the RADIUS attribute document.
l If not, deliver the ACL included in the RADIUS attribute document to the user. Run the
display access-user user-id user-number command to check whether the ACL is delivered
successfully.
l If so, the ACL fails to be delivered to the physical chip. Go to step 2.
----End
105.5 UCM/5/USER_INFO_AUTHENTICATION
Message
UCM/5/USER_INFO_AUTHENTICATION:DEVICEMAC:[CHAR1];DEVICENAME:
[STRING1];USER:[STRING2];MAC:[CHAR2];TIME:[STRING3];ZONE:
[STRING4];DAYLIGHT:false;ERRCODE:[STRING5];RESULT:[STRING6];
Description
A user is being authenticated.
Issue 07 (2014-07-30)

1197

Log Reference
105 UCM
Parameters
Parameter Name
Parameter Meaning
DEVICEMAC
Indicates the device MAC address.
DEVICENAME
Indicates the device name.
USER
MAC
TIME
Indicates the system time.
ZONE
Indicates the time zone.
DAYLIGHT
Indicates whether the daylight saving time is used.
ERRCODE
Indicates the error code for user authentication failure.
RESULT
Indicates the authentication result.
Possible Causes
A user is being authenticated.
Procedure
----End
105.6 CM/5/USER_INFO_OFFLINE
Message
CM/5/USER_INFO_OFFLINE:DEVICEMAC:[CHAR1];DEVICENAME:
[STRING1];USER:[STRING2];MAC:[CHAR2];TIME:[STRING3];ZONE:
[STRING4];DAYLIGHT:false;ERRCODE:[STRING5];RESULT:success;
Description
A user goes offline.
Parameters
Parameter Name
Parameter Meaning
DEVICEMAC
Indicates the device MAC address.
DEVICENAME
Indicates the device name.
USER
MAC
Issue 07 (2014-07-30)

1198

Log Reference
105 UCM
Parameter Name
Parameter Meaning
TIME
Indicates the system time.
ZONE
Indicates the time zone.
DAYLIGHT
Indicates whether the daylight saving time is used.
ERRCODE
Indicates the error code for the user offline event.
RESULT
Indicates the result of the user offline event.
Possible Causes
A user goes offline.
Procedure
----End
Issue 07 (2014-07-30)

1199

Log Reference
106 VFS
106
VFS
About This Chapter

106.1 VFS/5/CLOSEDIR_FAIL
106.2 VFS/4/DELETE_LOG_FILE
106.3 VFS/6/DEV_REG
106.4 VFS/5/DEV_UNREG
106.5 VFS/5/DIR_FAIL
106.6 VFS/4/DIR_NAME_IS_OCCUPIED
106.7 VFS/4/DISKSPACE_NOT_ENOUGH
106.8 VFS/3/FAILGETFILELEN
106.9 VFS/4/FILE_CPY_ALL_FAIL
106.10 VFS/6/FILE_CPY_ALL_OK
106.11 VFS/4/FILE_CPY_FAIL
106.12 VFS/5/FILE_CPY_PART_OK
106.13 VFS/4/FILE_NAME_IS_OCCUP
106.14 VFS/5/FILE_NOT_EXIST
106.15 VFS/3/FILE_SLOT_PREFIX_ERR
106.16 VFS/4/FILE_USED_DIR_NAME
106.17 VFS/6/FILE_USR_CANCEL
106.18 VFS/6/FILE_USR_CANCEL_CPY
106.19 VFS/6/FILE_USR_CANCEL_DEL
106.20 VFS/5/FILE_USR_CONFIRM
Issue 07 (2014-07-30)

1200

Log Reference
106 VFS
106.21 VFS/6/FILE_USR_CONFIRM_CPY
106.22 VFS/6/FILE_USR_CONFIRM_DEL
106.23 VFS/5/FILEACCESS_DENI
106.24 VFS/5/FILECREATE_FAIL
106.25 VFS/5/FILEDELETE_FAIL
106.26 VFS/5/FILEINUSING
106.27 VFS/5/FILEOPEN_FAIL
106.28 VFS/5/FILEOPEN_MORE
106.29 VFS/5/FLASHWRITE_FAIL
106.30 VFS/6/IPCREGDEV_OK
106.31 VFS/5/IPCUNREGDEV_OK
106.32 VFS/4/NO_LOG_FILE_TO_CLEAR
106.33 VFS/4/NO_VAL_LOG_TO_CLEAR
106.34 VFS/4/NOT_CLEAR_CURR_LOG
106.35 VFS/4/NOT_CLEAR_MONTH_LOG
106.36 VFS/3/PSEMTOOLONG
106.37 VFS/5/UNREGDEV_OK
106.38 VFS/3/WRITE_ERR
Issue 07 (2014-07-30)

1201

Log Reference
106 VFS
106.1 VFS/5/CLOSEDIR_FAIL
Message
VFS/5/CLOSEDIR_FAIL:VOS VFS failed to close the directory when the search finished.
(ReturnValue=[ULONG])
Description
VOS VFS failed to close the directory when the search finished. (ReturnValue=[ULONG])
Parameters
Parameter Name
Parameter Meaning
ReturnValue
ReturnValue.
Possible Causes
VOS VFS failed to close the directory when the search finished.
Procedure
Step 1 Check whether the device works normally.
----End
106.2 VFS/4/DELETE_LOG_FILE
Message
VFS/4/DELETE_LOG_FILE:Succeeded in deleting log file [file-name].
Description
Succeeded in deleting the log file [STRING].
Parameters
Parameter Name
Parameter Meaning
[file-name]
Possible Causes
Deleting the file succeeded.
Issue 07 (2014-07-30)

1202

Log Reference
106 VFS
Procedure
----End
106.3 VFS/6/DEV_REG
Message
VFS/6/DEV_REG:Device [device-name] registration finished.
Description
Device registration finished.
Parameters
Parameter Name
Parameter Meaning
device-name
indicates the name of a device.
Possible Causes
Device registration finished.
Procedure
----End
106.4 VFS/5/DEV_UNREG
Message
VFS/5/DEV_UNREG:Device [device-name] unregistration finished.
Description
Device deregistration finished.
Parameters
Parameter Name
Parameter Meaning
[device-name]
indicates the name of a device.
Issue 07 (2014-07-30)

1203

Log Reference
106 VFS
Possible Causes
Device deregistration finished.
Procedure
----End
106.5 VFS/5/DIR_FAIL
Message
VFS/5/DIR_FAIL:Dir [device-file-name] operation terminated abnormally.
Description
The dir operation is abnormal.
Parameters
Parameter Name
Parameter Meaning
device-file-name
indicates the name of a file or a device.
Possible Causes
When files were found through the dir command, an illegal file existed or a device could not be
read due to a damage.
Procedure
----End
106.6 VFS/4/DIR_NAME_IS_OCCUPIED
Message
VFS/4/DIR_NAME_IS_OCCUPIED:The directory name [directory-name] of backup log file
is occupied by another file.
Description
The log directory name [directory-name] was used by another file.
Issue 07 (2014-07-30)

1204

Log Reference
106 VFS
Parameters
Parameter Name
Parameter Meaning
[directory-name]
indicates the directory of the log file.
Possible Causes
The directory name already exists.
Procedure
Step 1 Modify the file name that is the same as the name of the backup log directory.
----End
106.7 VFS/4/DISKSPACE_NOT_ENOUGH
Message
VFS/4/DISKSPACE_NOT_ENOUGH: Disk space is insufficient. The system begins to delete
unused log files.
Description
Started to delete some logs because the disk space was not enough.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The disk space is insufficient.
Procedure
----End
106.8 VFS/3/FAILGETFILELEN
Issue 07 (2014-07-30)

1205

Log Reference
106 VFS
Message
VFS/3/FAILGETFILELEN: Failed to get file length. (FileName=[file-name], ResultValue=
[result-value])
Description
The file length failed to be obtained.
Parameters
Parameter Name
Parameter Meaning
FileName
Name of the file
ResultValue
Returned value
Possible Causes
Failed to obtain the file length.
Procedure
----End
106.9 VFS/4/FILE_CPY_ALL_FAIL
Message
VFS/4/FILE_CPY_ALL_FAIL:Failed to copy file [file-name1] to [file-name2] in batches.
(ErrorCode=[ULONG])
Description
Failed to copy file [file-name1] to file [file-name2] in batches.
Parameters
Parameter Name
Parameter Meaning
[file-name1]
Indicates the name of the source file.
[file-name2]
Indicates the name of the destination file.
ErrorCode
Possible Causes
Failed to delete all files in batches.
Issue 07 (2014-07-30)

1206

Log Reference
106 VFS
Procedure
----End
106.10 VFS/6/FILE_CPY_ALL_OK
Message
VFS/6/FILE_CPY_ALL_OK:Succeeded in copying file [file-name1] to [file-name2] in batches.
Description
Succeeded in copying file [file-name1] to file [file-name2] in batches.
Parameters
Parameter Name
Parameter Meaning
[file-name1]
[file-name2]
Possible Causes
Suceeded in copying all files in batches.
Procedure
----End
106.11 VFS/4/FILE_CPY_FAIL
Message
VFS/4/FILE_CPY_FAIL:Failed to Copy file [file-name1] to [file-name2].
Description
Failed to copy file [file-name1] to file [file-name2].
Issue 07 (2014-07-30)

1207

Log Reference
106 VFS
Parameters
Parameter Name
Parameter Meaning
[file-name1]
[file-name2]
Possible Causes
Failed to copy a file.
Procedure
----End
106.12 VFS/5/FILE_CPY_PART_OK
Message
VFS/5/FILE_CPY_PART_OK:Partially succeeded in copying file [file-name1] to [file-name2]
in batches.
Description
Succeeded in partially copying file [file-name1] to file [file-name2] in batches.
Parameters
Parameter Name
Parameter Meaning
[file-name1]
[file-name2]
Possible Causes
Succeeded in copying part of all files in batches.
Procedure
----End
106.13 VFS/4/FILE_NAME_IS_OCCUP
Issue 07 (2014-07-30)

1208

Log Reference
106 VFS
Message
VFS/4/FILE_NAME_IS_OCCUP:Log file name [file-name] is occupied by a directory.
Description
The log name [file-name] was used by the directory.
Parameters
Parameter Name
Parameter Meaning
[file-name]
Indicates the name of a file.
Possible Causes
The file attribute in a directory was saved successfully.
Procedure
Step 1 Modify the file name that is the same as the name of the log directory.
----End
106.14 VFS/5/FILE_NOT_EXIST
Message
VFS/5/FILE_NOT_EXIST:File [file-name] does not exist.
Description
File [file-name] did not exist.
Parameters
Parameter Name
Parameter Meaning
[file-name]
Indicates the file name.
Possible Causes
The file did not exist.
Procedure
----End
Issue 07 (2014-07-30)

1209

Log Reference
106 VFS
106.15 VFS/3/FILE_SLOT_PREFIX_ERR
Message
VFS/3/FILE_SLOT_PREFIX_ERR:Fail to process slot [slot-id] prefix.
Description
Failed to process the prefix of the slot.
Parameters
Parameter Name
Parameter Meaning
slot-id
Indicates the string of slot ID.
Possible Causes
Failed to replace the slot ID in the file.
Procedure
Step 1 Modify the file name that is the same as the name of the log directory. Then check whether the
problem is solved.
Step 2 Collect configurations, and log messages, then contact the Huawei technical support personnel.
Step 3 End.
----End
106.16 VFS/4/FILE_USED_DIR_NAME
Message
VFS/4/FILE_USED_DIR_NAME:Log file directory name [directory-name] is occupied by a
file.
Description
The log directory name [directory-name] was used by the file.
Issue 07 (2014-07-30)

1210

Log Reference
106 VFS
Parameters
Parameter Name
Parameter Meaning
[directory-name]
indicates the directory of the log file.
Possible Causes
The directory name already existed.
Procedure
Step 1 Modify the file name that is the same as the name of the log directory.
----End
106.17 VFS/6/FILE_USR_CANCEL
Message
VFS/6/FILE_USR_CANCEL:User [user-name] cancels the operation of overwriting file [filename].
Description
User [user-name] cancelled the operation of overwriting file [file-name].
Parameters
Parameter Name
Parameter Meaning
[user-name]
[file-name]
Indicates the name of the file to be overwritten.
Possible Causes
The user cancelled the operation of overwriting a file.
Procedure
----End
106.18 VFS/6/FILE_USR_CANCEL_CPY
Issue 07 (2014-07-30)

1211

Log Reference
106 VFS
Message
VFS/6/FILE_USR_CANCEL_CPY:User [user-name] cancels the operation of copying file
[file-name1] to [file-name2].
Description
User [user-name] cancelled the operation of copying file [file-name1] to file [file-name2].
Parameters
Parameter Name
Parameter Meaning
[user-name]
[file-name1]
[file-name2]
Possible Causes
The user canceled the operation of copying a file.
Procedure
----End
106.19 VFS/6/FILE_USR_CANCEL_DEL
Message
VFS/6/FILE_USR_CANCEL_DEL:User [user-name] cancels the operation of deleting file
[file-name].
Description
User [user-name] cancelled the operation of deleting file [file-name].
Parameters
Parameter Name
Parameter Meaning
[user-name]
[file-name]
Possible Causes
The user cancelled the operation of deleting a file.
Issue 07 (2014-07-30)

1212

Log Reference
106 VFS
Procedure
----End
106.20 VFS/5/FILE_USR_CONFIRM
Message
VFS/5/FILE_USR_CONFIRM:User [user-name] confirms the operation of overwriting file
[file-name].
Description
User [user-name] confirmed the operation of overwriting file [file-name].
Parameters
Parameter Name
Parameter Meaning
[user-name]
[file-name]
Indicates the name of the file to be overwritten.
Possible Causes
The user confirmed the operation of overwriting a file.
Procedure
----End
106.21 VFS/6/FILE_USR_CONFIRM_CPY
Message
VFS/6/FILE_USR_CONFIRM_CPY:User [username] confirms the operation of copying file
[filename1] to [filename2].
Description
User [username] confirmed the operation of copying file [filename1] to [filename2].
Issue 07 (2014-07-30)

1213

Log Reference
106 VFS
Parameters
Parameter Name
Parameter Meaning
[username]
[filename1]
[filename2]
Possible Causes
The user confirmed the operation of copying a file.
Procedure
----End
106.22 VFS/6/FILE_USR_CONFIRM_DEL
Message
VFS/6/FILE_USR_CONFIRM_DEL:User [user-name] confirms the operation of deleting file
[file-name].
Description
User [user-name] confirmed the operation of deleting file [file-name].
Parameters
Parameter Name
Parameter Meaning
[user-name]
[file-name]
Possible Causes
The user confirmed the operation of deleting a file.
Procedure
----End
Issue 07 (2014-07-30)

1214

Log Reference
106 VFS
106.23 VFS/5/FILEACCESS_DENI
Message
VFS/5/FILEACCESS_DENI:Access to [file-name] was denied. (AccessMode=[STRING])
Description
The access to [file-name] was rejected (0x[access-mode]).
Parameters
Parameter Name
Parameter Meaning
[file-name]
AccessMode
indicates the access mode of this file.
Possible Causes
The file that was opened in exclusive mode is opened in write mode, or the file that was opened
in write mode is opened in exclusive mode.
Procedure
Step 1 Check whether the file access mode is correct.
----End
106.24 VFS/5/FILECREATE_FAIL
Message
VFS/5/FILECREATE_FAIL:Failed to create [file-name].
Description
When a file was to be created, no idle file or file control block existed.
Parameters
Parameter Name
Parameter Meaning
[file-name]
Issue 07 (2014-07-30)

1215

Log Reference
106 VFS
Possible Causes
When a file was to be created, no idle file or file control block existed.
Procedure
----End
106.25 VFS/5/FILEDELETE_FAIL
Message
VFS/5/FILEDELETE_FAIL:Failed to delete file [file-name] because the file is in use.
Description
Failed to delete [file-name] because the file was in use.
Parameters
Parameter Name
Parameter Meaning
[file-name]
Possible Causes
A file in use was deleted.
Procedure
----End
106.26 VFS/5/FILEINUSING
Message
VFS/5/FILEINUSING:The file [file-name] is in using(callstackinforamtion=[STRING]).
Description
Failed to access a file because the file was being used.
Issue 07 (2014-07-30)

1216

Log Reference
106 VFS
Parameters
Parameter Name
Parameter Meaning
[file-name]
Name of the file to be accessed
callstackinforamtion
Stack that calls the file
Possible Causes
The file was in use or the file was not closed.
Procedure
Step 1 Analyze the reason for not closing the file based on information about the call stack. Then, close
the file that is not in use.
----End
106.27 VFS/5/FILEOPEN_FAIL
Message
VFS/5/FILEOPEN_FAIL:Failed to open [file-name] because of access mode error.
(AccessMode=[STRING])
Description
Failed to open [file-name] due to an access mode error and the access mode was 0x[accessmode].
Parameters
Parameter Name
Parameter Meaning
[file-name]
AccessMode
indicates a file access mode.
Possible Causes
The file to be created cannot be written.
Procedure
Step 1 File access modes conflicted.
----End
Issue 07 (2014-07-30)

1217

Log Reference
106 VFS
106.28 VFS/5/FILEOPEN_MORE
Message
VFS/5/FILEOPEN_MORE:Failed to open [file-name], the file was opened with mode [accessmode].
Description
Failed to open [file-name] because the file was opened in 0x[access-mode] mode.
Parameters
Parameter Name
Parameter Meaning
[file-name]
[access-mode]
indicates the access mode of this file.
Possible Causes
No more idle blocks for file description existed to open a file.
Procedure
Step 1 Release logs that are not in use.
----End
106.29 VFS/5/FLASHWRITE_FAIL
Message
VFS/5/FLASHWRITE_FAIL:An error occurred when writing data into FLASH, please check
FLASH memory!
Description
An error occurred when writing data to the flash. Check the flash space.
Parameters
Parameter Name
Parameter Meaning
None
None
Issue 07 (2014-07-30)

1218

Log Reference
106 VFS
Possible Causes
An error occurred when writing data to the flash.
Procedure
Step 1 Check whether the device works normally.
----End
106.30 VFS/6/IPCREGDEV_OK
Message
VFS/6/IPCREGDEV_OK: Register device [board-id] to main file system through IPC
successfully.
Description
Succeeded in registering the device to the main file system.
Parameters
Parameter Name
Parameter Meaning
board-id
indicates the ID of a board where the device resides.
Possible Causes
The deregistration succeeded.
Procedure
----End
106.31 VFS/5/IPCUNREGDEV_OK
Message
VFS/5/IPCUNREGDEV_OK:Succeeded in unregistering the file system on device [board-id]
through IPC.
Description
Succeeded in deregistering the device [board-id] between boards.
Issue 07 (2014-07-30)

1219

Log Reference
106 VFS
Parameters
Parameter Name
Parameter Meaning
[board-id]
indicates the ID of a board where the device resides.
Possible Causes
Deregistering the device succeeded.
Procedure
----End
106.32 VFS/4/NO_LOG_FILE_TO_CLEAR
Message
VFS/4/NO_LOG_FILE_TO_CLEAR:All log files had been cleared!
Description
The logs were cleared completely.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
Failed to find the file.
Procedure
----End
106.33 VFS/4/NO_VAL_LOG_TO_CLEAR
Message
VFS/4/NO_VAL_LOG_TO_CLEAR:No legal log file can be cleared!
Issue 07 (2014-07-30)

1220

Log Reference
106 VFS
Description
No valid logs can be deleted.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The input value of the year is greater than 2035 and that of the month is greater than 12.
Procedure
----End
106.34 VFS/4/NOT_CLEAR_CURR_LOG
Message
VFS/4/NOT_CLEAR_CURR_LOG:The current log file can not be cleared!
Description
The current log can not be cleared.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The file name was invalid.
Procedure
Step 1 Run the delete command to delete invalid files for the purpose of releasing the disk space. Then
check whether the problem is solved.
Issue 07 (2014-07-30)

1221

Log Reference
106 VFS
Step 3 End.
----End
106.35 VFS/4/NOT_CLEAR_MONTH_LOG
Message
VFS/4/NOT_CLEAR_MONTH_LOG:The current month log file can not be cleared!
Description
The logs in the current month can not be cleared.
Parameters
Parameter Name
Parameter Meaning
None
None
Possible Causes
The eligible log file existed.
Procedure
Step 1 Run the delete command to delete invalid files for the purpose of releasing the disk space. Then
check whether the problem is solved.
Step 3 End.
----End
106.36 VFS/3/PSEMTOOLONG
Message
VFS/3/PSEMTOOLONG: The time of file system P semaphore is too long.
(CallStackInformation=[stack-information], TaskId=[task-id], StartPTime=[start-time], PTime
(ms)=[p-time])
Description
The duration time of the file system P semaphore was too long.
Issue 07 (2014-07-30)

1222

Log Reference
106 VFS
Parameters
Parameter Name
Parameter Meaning
CallStackInformation
Call stack information
TaskId
Task ID
StartPTime
Start time of the P semaphore
PTime(ms)
Duration time of the P semaphore
Possible Causes
The disk processing was too slow.
Procedure
----End
106.37 VFS/5/UNREGDEV_OK
Message
VFS/5/UNREGDEV_OK:Succeeded in unregistering the file system on device [device-name].
Description
Succeeded in deregistering file system from the device [device-name].
Parameters
Parameter Name
Parameter Meaning
[device-name]
indicates the device name.
Possible Causes
Deregistering the device succeeded.
Procedure
----End
106.38 VFS/3/WRITE_ERR
Issue 07 (2014-07-30)

1223

Log Reference
106 VFS
Message
VFS/3/WRITE_ERR: Failed to write file to slot [slot-id], which may be due to the insufficient
space of the CF card.
Description
Because the space of the CF card on the board is insufficient, users failed to write files to the
board.
Parameters
Parameter Name
Parameter Meaning
slot-id
Slot ID of a board
Possible Causes
Failed to write files to a board, which is due to the insufficient space of the CF card on the board.
Procedure
Step 1 Delete useless files to ensure that the space of the CF card is sufficient.
----End
Issue 07 (2014-07-30)

1224

Log Reference
107 VOSCPU
107
VOSCPU
About This Chapter

107.1 VOSCPU/4/CPU_USAGE_HIGH
107.2 VOSCPU/4/CPU_USAGE_RESUME
Issue 07 (2014-07-30)

1225

Log Reference
107 VOSCPU
107.1 VOSCPU/4/CPU_USAGE_HIGH
Message
VOSCPU/4/CPU_USAGE_HIGH:The CPU is overloaded(CpuUsage=[ULONG]%,
Threshold=[ULONG]%), and the tasks with top three CPU occupancy are: [CPU-resourcesusage]
Description
The CPU was overloaded, and the names of the top three tasks that occupy most CPU
resources and CPU usage of each task (if one task has a sub-task, the name and CPU usage of
the sub-task were also listed) were listed.
Parameters
Parameter Name
Parameter Meaning
[CPU-resources-usage] Names of the top three tasks that occupy most CPU resources and
CPU usage of each task together with the name and CPU usage of a
sub-task if possible.
CpuUsage
indicates the current CPU utilization rate.
Threshold
indicates the threshold of the CPU utilization rate, ranging from 1 to

100.
Possible Causes
The CPU utilization rate was too high.
Procedure
Step 1 Find the cause of the high CPU utilization rate. Delete some configurations to terminate tasks
if necessary.
----End
107.2 VOSCPU/4/CPU_USAGE_RESUME
Message
VOSCPU/4/CPU_USAGE_RESUME:CPU utilization recovered to the normal range.
Description
The CPU usage is reduced to the normal range.
Issue 07 (2014-07-30)

1226

Log Reference
107 VOSCPU
Parameters
Parameter Name
Parameter Meaning
None.
None.
Possible Causes
The CPU usage is reduced to the normal range.
Procedure
l
This alarm is informational only, and no action is required.
----End
Issue 07 (2014-07-30)

1227

Log Reference
108 VRRP
108
VRRP
About This Chapter

NOTE
The S2750, S5700LI, S5700SI, and S5700S-LI do not support this log.
108.1 VRRP/5/DELTRACK3AH
108.2 VRRP/4/STATEWARNING
108.3 VRRP/4/STATEWARNINGEXTEND
108.4 VRRP/4/CHKFAIL
108.5 VRRP/4/SPECCHANGED
Issue 07 (2014-07-30)

1228

Log Reference
108 VRRP
108.1 VRRP/5/DELTRACK3AH
Message
VRRP/5/DELTRACK3AH:Warning: The virtual router tracks EFM on an absent interface. This
causes the bound configuration to be automatically deleted. Continue?: [Y/N]
Description
When you configure VRRP track EFM session or link BFD, and meanwhile the VRRP has been
configured to an absent EFM session, the note will remind you.
Parameters
Parameter Name
Parameter Meaning
[Y/N]
Y or N. Y means continue, N means stop.
Possible Causes
reason 1:
VRRP has been configured to track an absent EFM session.
reason 2:
Then configure VRRP track EFM session or link BFD.
Procedure
----End
108.2 VRRP/4/STATEWARNING
Message
VRRP/4/STATEWARNING:Virtual Router state [State]. (Interface=[STRING], VrId=
[ULONG], InetType=[STRING])
Description
When the VRRP status changed, the following information is logged, the interface name, status
change, and reason of the status change.
Issue 07 (2014-07-30)

1229

Log Reference
108 VRRP
Parameters
Parameter Name
Parameter Meaning
[State]
indicates the status change. The value is specified as follows:

1. INITIALIZE changed to MASTER.
2. BACKUP changed to MASTER.
3. MASTER changed to BACKUP.
4. MASTER changed to INITIALIZE.
5. BACKUP changed to NOTACTIVE.
[Reason]
indicates the reason of the status change.
Interface
indicates the name of an interface.
VrId
indicates the ID of a VRRP backup group.
[Reason]
indicates the type of network.
Possible Causes
The reason corresponding to a specific error code is as follows:
1: The fault of a device or a link occurred.
2: The fault recovered on a device or a link.
3: The configuration changed.
Procedure
Step 1 For a device fault, check the status of the interface configured with VRRP.
Step 2 For a link fault, check the status of the VRRP link.
Step 3 For a device or link recovery, no action is required.
Step 4 For a configuration change, check the VRRP configuration.
----End
108.3 VRRP/4/STATEWARNINGEXTEND
Message
VRRP/4/STATEWARNINGEXTEND:Virtual Router state [State], because of [Reason].
(Interface=[STRING], VrId=[ULONG], InetType=[STRING])
Description
When the VRRP status changed, the following information is logged: the interface name, status
change, and reason of the status change.
Issue 07 (2014-07-30)

1230

Log Reference
108 VRRP
Parameters
Parameter Name
Parameter Meaning
[State]
Status change, which can be:

1. "INITIALIZE changed to MASTER"
2. "BACKUP changed to MASTER"
3. "MASTER changed to BACKUP"
4. "MASTER changed to INITIALIZE"
5. "MASTER changed to NOTACTIVE"
[Reason]
Status change reason, which can be:

1. priority calculation
2. protocol timer expired
3. track interface
4. track BFD session
5. link BFD session down
6. link BFD session up
7. link BFD session deleted
8. peer BFD session down
9. interface up
10.interface down
11.create notactive
12.create initialize
13.standby deleted
14.BFD configure deleted
15.EFM configure deleted
16.EFM session down
17.EFM session up
18.ignore interface down
19.CFM session down
20.CFM fault removal
21.interface deleted
22.status backup from the AMB to SMB
23.ipsec-instance configure deleted
24.ipsec-instance down
25.ipsec-instance up
26.other
Interface
Issue 07 (2014-07-30)
Interface name

1231

Log Reference
108 VRRP
Parameter Name
Parameter Meaning
VrId
VRID of the VRRP backup group
InetType
Network type
Possible Causes
Cause 1: The device or the link was faulty.
Cause 2: The device or the link was recovered.
Cause 3: The configuration changed.
Procedure
Step 1 If the device was faulty, check the status of the interface configured with VRRP.
Step 2 If the link was faulty, check the status of the link configured with VRRP.
Step 3 If the device or the link was recovered, no action is required.
Step 4 If the configuration changed, check the VRRP configuration.
----End
108.4 VRRP/4/CHKFAIL
Message
VRRP/4/CHKFAIL:The ISSU check failed because of the [reason].
Description
The ISSU check on VRRP modules failed because specifications changed or were incompatible.
Parameters
reason
Indicates causes for the ISSU check failure. The causes are as follows:
l failure in getting specification data: Failed to obtain the specification
data.
l specification change: Specifications changed.
l incompatible version: Versions were incompatible.
Possible Causes
Lossless ISSU was found not supported on VRRP modules after the specifications,
incompatibility, and configurations were checked.
Issue 07 (2014-07-30)

1232

Log Reference
108 VRRP
Procedure
Step 3 Perform the ISSU after the PAF is updated.
----End
108.5 VRRP/4/SPECCHANGED
Message
VRRP/4/SPECCHANGED:The VRRP specifications were changed in the new version. (Spec=
[STRING], Value=[ULONG])
Description
During the ISSU configuration recovery, the changed fields of specifications and their values
were recorded in this log message, if VRRP specifications were changed and incorrect logs were
recorded.
Issue 07 (2014-07-30)

1233

Log Reference
108 VRRP
Parameters
Spec
Indicates the specification fields. The values are as follows:

l VRRP_ISSU_SPEC_VIPMAX: indicates the number of virtual IP
addresses.
l VRRP_ISSU_SPEC_TRACK_BFD_MAX: indicates the maximum
number of bound BFD sessions.
l VRRP_ISSU_SPEC_TRACK_IF_MAX: indicates the maximum
number of bound interfaces.
l VRRP_ISSU_SPEC_PEER_BFD_MAX: indicates the maximum
number of peer BFD sessions.
l VRRP_ISSU_SPEC_LINK_BFD_MAX: indicates the maximum
number of link BFD sessions.
l VRRP_ISSU_SPEC_ADMIN_MAX: indicates the maximum
number of mVRRP groups.
l VRRP_ISSU_SPEC_SUB_OF_ADMIN_MAX: indicates the
maximum number of service VRRP backup groups that can be bound
to an mVRRP group.
l VRRP_ISSU_SPEC_VIRTUAL_REPEAT_MAX: indicates the
maximum number of VRRP backup groups that share a same VRID.
l VRRP_ISSU_SPEC_TRACK_IF_MAX: indicates the maximum
number of service interfaces that can be bound to an mVRRP group.
l VRRP_ISSU_SPEC_VIRTUAL_ROUTER_MAX: indicates the
maximum number of VRRP backup groups that can be configured on
an interface.
Value
Indicates the values of the specifications.
Possible Causes
VRRP specifications were changed in the new version.
Procedure
----End
Issue 07 (2014-07-30)

1234

Log Reference
109 VTRUNK
109
VTRUNK
About This Chapter

109.1 VTRUNK/5/MEMBER_DOWN
109.2 VTRUNK/5/MEMBER_UP
109.3 VTRUNK/5/TRUNKDOWN
109.4 VTRUNK/5/TRUNKUP
Issue 07 (2014-07-30)

1235

Log Reference
109 VTRUNK
109.1 VTRUNK/5/MEMBER_DOWN
Message
VTRUNK/5/MEMBER_DOWN:The status of the trunk member went Down. (TrunkName=
Description
The status of the trunk member interfaces went Down.
Parameters
Parameter Name
Parameter Meaning
TrunkName
Indicates the name of the trunk interface.
PortName
Indicates the name of a member port.
Possible Causes
The status of the trunk member interfaces went Down.
Procedure
Step 1 1. Run the display this interface command in the interface view to check whether the link is
normal.
l (1) If the link is normal, go to Step 2.
l (2) If the interface is in the Down state, check whether the physical connection is correct.
Step 2 2. Contact Huawei technical personnel.
----End
109.2 VTRUNK/5/MEMBER_UP
Message
VTRUNK/5/MEMBER_UP:The status of the trunk member went Up. (TrunkName=[STRING],
PortName=[STRING])
Description
The status of the trunk member interfaces went Up.
Issue 07 (2014-07-30)

1236

Log Reference
109 VTRUNK
Parameters
Parameter Name
Parameter Meaning
TrunkName
PortName
Indicates the name of a member port.
Possible Causes
The status of the trunk member interfaces went Up.
Procedure
----End
109.3 VTRUNK/5/TRUNKDOWN
Message
VTRUNK/5/TRUNKDOWN:The status of interface [Trunk] turns Down.
Description
The trunk interface went Down.
Parameters
Parameter Name
Parameter Meaning
[Trunk]
Possible Causes
l
1. The number of trunk member interfaces that are in the Up state is smaller than the
minimum number of activated links set on the trunk interface.
2. When the trunk interface is configured with the LACP protocol, the number of trunk
member interfaces that are in the Select state is smaller than the minimum number of
activated links set on the trunk interface.
Procedure
----End
Issue 07 (2014-07-30)

1237

Log Reference
109 VTRUNK
109.4 VTRUNK/5/TRUNKUP
Message
VTRUNK/5/TRUNKUP:The status of interface [Trunk] turns Up.
Description
The trunk interface went Up.
Parameters
Parameter Name
Parameter Meaning
[Trunk]
Possible Causes
l
1. The number of trunk member interfaces that are in the Up state is larger than the minimum
number of activated links set on the trunk interface.
2. When the trunk interface is configured with the LACP protocol, the number of trunk
member interfaces that are in the Select state is greater than the minimum number of
activated links set on the trunk interface.
Procedure
----End
Issue 07 (2014-07-30)

1238

Log Reference
110 VTY
110
VTY
About This Chapter

110.1 VTY/5/ACL_DENY
Issue 07 (2014-07-30)

1239

Log Reference
110 VTY
110.1 VTY/5/ACL_DENY
Message
VTY/5/ACL_DENY:The TCP request was denied according to ACL rules. (IpAddress=
[IpAddress])
Description
The TCP request was denied according to the ACL rule.
Parameters
Parameter Name
Parameter Meaning
IpAddress
Indicates the IP address of the client.
Possible Causes
The TCP request does not match the ACL rule.
Procedure
----End
Issue 07 (2014-07-30)

1240

S2750&S5700&S6700 V200R003 (C00&C02&C10) Log Reference 07

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

S2750&S5700&S6700 V200R003 (C00&C02&C10) Log Reference 07

Hochgeladen von

Copyright:

Verfügbare Formate

S2750&S5700&S6700 Series Ethernet Switches

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

About This Document

About This Document

Network monitoring engineers

System maintenance engineers

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

About This Document

NOTE is used to address information not

The keywords of a command line are in boldface.

Command arguments are in italics.

Items (keywords or arguments) in brackets [ ] are optional.

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

The parameter before the & sign can be repeated 1 to n times.

A line starting with the # sign is comments.

Mappings between Product Software Versions and NMS

Product Software Version

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

About This Document

Product Software Version

Changes in Issue 07 (2014-07-30) V200R003(C00&C02&C10)

Changes in Issue 06 (2014-05-15) V200R003(C00&C02&C10)

Changes in Issue 05 (2014-03-12) V200R003(C00&C02&C10)

Changes in Issue 04 (2013-11-06) V200R003(C00&C02)

Changes in Issue 03 (2013-09-30) V200R003(C00&C02)

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

About This Document

Changes in Issue 02 (2013-07-25) V200R003C00

Changes in Issue 01 (2013-05-30) V200R003C00

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches

Huawei Proprietary and Confidential

S2750&S5700&S6700 Series Ethernet Switches