COMWARE V5 Platform System Log Message

COMWARE System Log Message
Table of Contents
1 Introduction................................................................................................................................... 16
1.1 Overview ............................................................................................................................ 16
1.2 System Log Message Format............................................................................................ 16
1.3 System Log Message Module List..................................................................................... 18
2 802.1X Messages......................................................................................................................... 21
2.1 DOT1X_LOG ..................................................................................................................... 21
2.2 DOT1X_LOG ..................................................................................................................... 22
2.3 DOT1X_LOG ..................................................................................................................... 22
2.4 DOT1XSOP_ACL_NOT_SUPPORT ................................................................................. 23
2.5 DOT1XSOP_ACL_NOT_CONFIGURED .......................................................................... 23
2.6 DOT1XSOP_ACL_DEL_FAILED....................................................................................... 23
2.7 DOT1XSOP_ACL_ADD_FAILED ...................................................................................... 24
2.8 DOT1XSOP_ACL_RESOUCE_EXHAUSTED .................................................................. 24
2.9 DOT1XSOP_ACL_CONFLICT_WITH_ MQC ................................................................... 24
2.10 DOT1XSOP_ACL_CONFLICT_WITH_ USERMAC........................................................ 25
2.11 DOT1XSOP_ACL_CONFLICT_WITH_FLOW_TEMPLATE ........................................... 25
2.12 DOT1XEAD_LOG ............................................................................................................ 26
2.13 DOT1XEAD_LOG ............................................................................................................ 26
2.14 DOT1XEAD_LOG ............................................................................................................ 26
2.15 DOT1XEAD_LOG ............................................................................................................ 27
2.16 DOT1XEAD_LOG ............................................................................................................ 27
3 ADDR Messages .......................................................................................................................... 28

3.1 Information ......................................................................................................................... 28
3.2 Information ......................................................................................................................... 28
3.3 RESOURCE....................................................................................................................... 28
4 ARP Messages............................................................................................................................. 29
4.1 ROUTECONFLICT ............................................................................................................ 29
4.2 DUPIFIP............................................................................................................................. 29
4.3 DUPVRRPIP ...................................................................................................................... 30
4.4 DUPGLOBALIP.................................................................................................................. 30
4.5 ARPDTC ............................................................................................................................ 31
4.6 SRC-MAC .......................................................................................................................... 31
Hangzhou H3C Technologies Co., Ltd. 1/220
5 ASPF Messages........................................................................................................................... 32
5.1 SESS_LOG........................................................................................................................ 32
5.2 SMTP_INVALID_COMMAND............................................................................................ 33
5.3 HTTP_JAVA_BLOCK ........................................................................................................ 33
5.4 ASPF_LOGID_FTP_SESS_NOT_AUTH .......................................................................... 33
5.5 HOST_TCP_ALERT_ON................................................................................................... 34
6 BFD Messages ............................................................................................................................. 34

6.1 FSM ................................................................................................................................... 34
6.2 no_echo_source_ip ........................................................................................................... 35
7 CFM Messages ............................................................................................................................ 35

7.1 CFM_LOG.......................................................................................................................... 35
8 CLST Messages ........................................................................................................................... 37

8.1 Info ..................................................................................................................................... 37
8.2 Member.............................................................................................................................. 37
8.3 MemberJoinCluster............................................................................................................ 38
8.4 JoinStack ........................................................................................................................... 38
8.5 DeleteCluster ..................................................................................................................... 39
8.6 DeleteStack........................................................................................................................ 39
8.7 RejoinCluster ..................................................................................................................... 39
8.8 AlreadyDown...................................................................................................................... 40
8.9 SwitchJoinCluster .............................................................................................................. 40
8.10 SwitchJoinStack............................................................................................................... 41
8.11 SwitchDeleteCluster ........................................................................................................ 41
8.12 SwitchDeleteStack........................................................................................................... 41
8.13 CommandDown ............................................................................................................... 42
8.14 SwitchRejoinCluster......................................................................................................... 42
8.15 LOG ................................................................................................................................. 43
8.16 LOG ................................................................................................................................. 43
9 CMD Messages ............................................................................................................................ 43

9.1 REBOOT............................................................................................................................ 43
9.2 REBOOT............................................................................................................................ 44
9.3 REBOOT............................................................................................................................ 44
9.4 REBOOT............................................................................................................................ 45
10 CSPF Messages......................................................................................................................... 45
10.1 LOG ................................................................................................................................. 45

11 DEVM Messages........................................................................................................................ 46
11.1 BOARDREMOVE............................................................................................................. 46
11.2 BOARDOK ....................................................................................................................... 46
11.3 BOARDFAULT................................................................................................................. 47
11.4 BOARDLOADING ............................................................................................................ 47
11.5 CARDREMOVE ............................................................................................................... 48
11.6 CARDINSERT.................................................................................................................. 48
11.7 CARDFAULT ................................................................................................................... 49
11.8 POWERRECOVER ......................................................................................................... 49
11.9 MPOWERRECOVER ...................................................................................................... 50
11.10 SPOWERRECOVER ..................................................................................................... 50
11.11 POWERFAIL.................................................................................................................. 51
11.12 POWERABSENT........................................................................................................... 51
11.13 FANRECOVER .............................................................................................................. 51
11.14 FANFAIL ........................................................................................................................ 52
11.15 FANABSENT ................................................................................................................. 52
11.16 TEMPOK........................................................................................................................ 52
11.17 TEMPLOW..................................................................................................................... 53
11.18 TEMPUP ........................................................................................................................ 53
11.19 RPSNORMAL ................................................................................................................ 54
11.20 RPSABSENT ................................................................................................................. 54
11.21 CFINSERT ..................................................................................................................... 55
11.22 CFREMOVE................................................................................................................... 55
11.23 SYSTEMREBOOT......................................................................................................... 56
11.24 BOARDREBOOT........................................................................................................... 56
11.25 SUBCARDREBOOT ...................................................................................................... 57
11.26 CURRENTNORMAL...................................................................................................... 57
11.27 CURRENTSMALL ......................................................................................................... 58
11.28 CURRENTBIG ............................................................................................................... 58
11.29 VOLTNORMAL .............................................................................................................. 59
11.30 VOLTLOW ..................................................................................................................... 59
11.31 VOLTHIGH..................................................................................................................... 60
11.32 NOENOUGHMEM ......................................................................................................... 60
11.33 SAMEREQUEST ........................................................................................................... 61
11.34 ABORTLOAD................................................................................................................. 61
11.35 REQUESTINVALID ....................................................................................................... 62
11.36 LOADFAIL...................................................................................................................... 62
11.37 LOADFINISH ................................................................................................................. 63
11.38 READFAIL ..................................................................................................................... 63
11.39 STARTSELF .................................................................................................................. 64
11.40 CANNOTOPEN.............................................................................................................. 64
11.41 MANYRESENT .............................................................................................................. 65
11.42 MANYINVALID............................................................................................................... 65
11.43 CHECKSUMERR........................................................................................................... 65
12 DHCP Messages ........................................................................................................................ 66

12.1 DHCPC_LOCAL_SERVER ............................................................................................. 66
12.2 DHCPC_FSM_TO_HALT ................................................................................................ 66
12.3 DHCPC_BOOTP_ALLOC_FAIL ...................................................................................... 67
13 DHCPR Messages ..................................................................................................................... 67

13.1 DHCPR_DETECT_SERVER........................................................................................... 67
14 DHCPS Messages...................................................................................................................... 68
14.1 DHCPS_LOCAL_SERVER.............................................................................................. 68
15 DHCPSNOOP Messages........................................................................................................... 69
15.1 dhcpsnoop_log................................................................................................................. 69
15.2 dhcpsnoop_log................................................................................................................. 69
15.3 dhcpsnoop_log................................................................................................................. 69
15.4 dhcpsnoop_log................................................................................................................. 70
15.5 dhcpsnoop_log................................................................................................................. 70
16 DLDP Messages......................................................................................................................... 70
16.1 AuthenticationFailed ........................................................................................................ 71
16.2 UnidirectionalAuto............................................................................................................ 71
16.3 UnidirectionalManual ....................................................................................................... 71
16.4 UnidirectionalAutoEnhance ............................................................................................. 72
16.5 UnidirectionalManualEnhance ......................................................................................... 72
17 DPURPF Messages ................................................................................................................... 73

17.1 DPURPF .......................................................................................................................... 73
18 ETHOAM Messages................................................................................................................... 74
18.1 OAMENABLE................................................................................................................... 74
18.2 OAMDISABLE.................................................................................................................. 75
18.3 OAMDISOK...................................................................................................................... 75
18.4 OAMDISFAIL ................................................................................................................... 75

18.5 OAMDISTIMEOUT .......................................................................................................... 76

18.6 OAMPORTDOWN ........................................................................................................... 76
18.7 EnUnderControl ............................................................................................................... 77
18.8 DisUnderControl .............................................................................................................. 77
18.9 EnControl ......................................................................................................................... 77
18.10 DisControl ...................................................................................................................... 78
18.11 LoopbackExit ................................................................................................................. 78
18.12 StateError....................................................................................................................... 79
18.13 LINKFAULT.................................................................................................................... 79
18.14 REMOTELINKFAULT .................................................................................................... 79
18.15 LOCALERRFRAME....................................................................................................... 80
18.16 REMOTEERRFRAME ................................................................................................... 80
18.17 LOCALERRFRAMEPERIOD ......................................................................................... 81
18.18 REMOTEERRFRAMEPERIOD ..................................................................................... 81
18.19 LOCALERRFRAMESEC ............................................................................................... 82
18.20 REMOTEERRFRAMESEC............................................................................................ 82
18.21 REMOTEDYINGGASP .................................................................................................. 83
18.22 REMOTECRITICALE..................................................................................................... 83
19 FIBV4 Messages ........................................................................................................................ 84

19.1 log_fib .............................................................................................................................. 84
19.2 log_fib .............................................................................................................................. 84
19.3 log_fib .............................................................................................................................. 85
19.4 Log_fib_MemShortage .................................................................................................... 85
19.5 Log_fib_MemResume...................................................................................................... 86
20 FILTER Messages...................................................................................................................... 86
20.1 IPFILTER ......................................................................................................................... 86
21 FTP Server Messages................................................................................................................ 86

21.1 USERIN ........................................................................................................................... 87
21.2 USEROUT ....................................................................................................................... 87
21.3 USERIN ........................................................................................................................... 87
21.4 USERFAIL ....................................................................................................................... 88
21.5 REQUEST........................................................................................................................ 88
21.6 SENDDATA ..................................................................................................................... 88
21.7 RECVDATA ..................................................................................................................... 89
21.8 RUNERROR .................................................................................................................... 89

22 GARP Messages ........................................................................................................................ 90

22.1 Wrong Protocol Id ............................................................................................................ 90
22.2 Wrong message............................................................................................................... 90
22.3 Wrong Msg Length .......................................................................................................... 90
22.4 Wrong attribute ................................................................................................................ 91
22.5 Malloc Failed.................................................................................................................... 91
23 HA Messages ............................................................................................................................. 92
23.1 LOG ................................................................................................................................. 92
24 HABP Messages ........................................................................................................................ 94

24.1 HABPSTART ................................................................................................................... 94
24.2 HABPSTOP ..................................................................................................................... 95
25 HTTPD Messages ...................................................................................................................... 95

25.1 Log ................................................................................................................................... 95
26 HTTPS Messages ...................................................................................................................... 95

26.1 LOG ................................................................................................................................. 96
27 HWCM Messages....................................................................................................................... 96
27.1 EXIT ................................................................................................................................. 96
27.2 TRAPLOG........................................................................................................................ 96
27.3 CCOPY ............................................................................................................................ 97
28 IGMP Messages ......................................................................................................................... 97

28.1 INFO ................................................................................................................................ 97
28.2 ERR ................................................................................................................................. 98
29 IFNET Messages........................................................................................................................ 98
29.1 PORTTAG........................................................................................................................ 98
29.2 UPDOWN......................................................................................................................... 99
29.3 UPDOWN......................................................................................................................... 99
29.4 LINK UPDOWN................................................................................................................ 99
29.5 FLUX EXCEED UPPER LIMIT ...................................................................................... 100
29.6 FLUX BELLOW LOWER LIMIT ..................................................................................... 100
29.7 PORT STATUS TURNS TO CONTROLLED ................................................................ 101
29.8 PORT STATUS RETURNS TO NORMAL..................................................................... 102
30 IKE Messages .......................................................................................................................... 102

30.1 DROP............................................................................................................................. 102
31 IPDBG Messages ..................................................................................................................... 103

31.1 IP Info............................................................................................................................. 103
32 IPCIM Messages ...................................................................................................................... 103

32.1 ipcim_log........................................................................................................................ 103
33 IPsec Messages ....................................................................................................................... 104

33.1 DROP............................................................................................................................. 104
34 IPV6FIBC Messages ................................................................................................................ 105

34.1 Log_fibc_MemShortage................................................................................................. 105
34.2 Log_fibc_MemResume.................................................................................................. 105
35 IPV6PP Messages.................................................................................................................... 106

35.1 ReassError..................................................................................................................... 106
35.2 QueueFull ...................................................................................................................... 106
36 ISIS Messages ......................................................................................................................... 106

36.1 ADJLOG......................................................................................................................... 106
37 L2TP Messages........................................................................................................................ 107

37.1 CLVPDN1 ...................................................................................................................... 107
37.2 CLVPDN2 ...................................................................................................................... 107
38 L2V Messages.......................................................................................................................... 108

38.1 LOG ............................................................................................................................... 108
39 L3VPN Messages..................................................................................................................... 111

39.1 L3VPNLOG .................................................................................................................... 111
40 LAGG Messages ...................................................................................................................... 112

40.1 LAGG_LOG ................................................................................................................... 112
40.2 LAGG_LOG ................................................................................................................... 113
41 LDP Messages ......................................................................................................................... 113

41.1 SessionUp...................................................................................................................... 113
41.2 SessionDown ................................................................................................................. 114
41.3 LDP ................................................................................................................................ 114
42 LLC2 Messages........................................................................................................................ 114
43 LLDP Messages ....................................................................................................................... 115

43.1 CREREM ....................................................................................................................... 115
43.2 DELREM ........................................................................................................................ 115
43.3 AGEOUTREM................................................................................................................ 116
43.4 TOOMANGREM ............................................................................................................ 116
43.5 NONTOOMANGREM .................................................................................................... 117
44 LS Messages............................................................................................................................ 117

44.1 CNAHGEPASSWORD .................................................................................................. 117

44.2 CNAHGEPASSWORD .................................................................................................. 117
44.3 CNAHGEPASSWORD .................................................................................................. 118
44.4 CNAHGEPASSWORD .................................................................................................. 118
44.5 WRITEPASSTOFILE ..................................................................................................... 119
45 LSPM Messages ...................................................................................................................... 119

45.1 LSPM ............................................................................................................................. 119
46 LWPS Messages ...................................................................................................................... 120

46.1 LOG ............................................................................................................................... 120
46.2 LOG ............................................................................................................................... 121
47 MCS Messages ........................................................................................................................ 121

47.1 LOG ............................................................................................................................... 121
48 MFIB Messages........................................................................................................................ 122

48.1 LOG ............................................................................................................................... 122
49 MLD Messages......................................................................................................................... 122

49.1 ERROR .......................................................................................................................... 122
50 MPLS OAM Messages ............................................................................................................. 123

50.1 OAM_LOG_INFO .......................................................................................................... 123
50.2 OAM_LOG_INFO .......................................................................................................... 123
51 QoS Messages ......................................................................................................................... 124

51.1 warning .......................................................................................................................... 124
51.2 warning .......................................................................................................................... 125
51.3 warning .......................................................................................................................... 125
51.4 warning .......................................................................................................................... 126
51.5 warning .......................................................................................................................... 126
51.6 warning .......................................................................................................................... 127
51.7 NOT ENOUGH BANDWIDTH........................................................................................ 127
51.8 CBWFQ REMOVED ...................................................................................................... 128
52 MCDP BRIDGE Messages....................................................................................................... 128

52.1 MACFULL ...................................................................................................................... 128
53 MRM Messages........................................................................................................................ 129

53.1 MRM .............................................................................................................................. 129
54 MSDP Messages...................................................................................................................... 129

54.1 PEER_UP ...................................................................................................................... 129

54.2 PEER_DOWN................................................................................................................ 130

54.3 SA_LIMIT ....................................................................................................................... 130
54.4 PEER_ACCEPT............................................................................................................. 131
55 MSTP Messages ...................................................................................................................... 132

55.1 STPSTART .................................................................................................................... 132
55.2 STPSTOP ...................................................................................................................... 132
55.3 ROOT............................................................................................................................. 133
55.4 IVBPDU.......................................................................................................................... 133
55.5 RGSUP .......................................................................................................................... 133
55.6 LGEXP ........................................................................................................................... 134
55.7 BPDUFORMATERROR................................................................................................. 134
55.8 BPDUFORMATCONFIGERROR................................................................................... 135
55.9 BPDUFORMATCONFIGRIGHT .................................................................................... 135
55.10 BPDURCVDEXPIRY ................................................................................................... 135
56 NATPT Messages .................................................................................................................... 136

56.1 TRANS........................................................................................................................... 136
56.2 TRANS........................................................................................................................... 136
57 ND Messages ........................................................................................................................... 137

57.1 ConfigConflict................................................................................................................. 137
57.2 ConfigConflict................................................................................................................. 138
57.3 ConfigConflict................................................................................................................. 138
57.4 ConfigConflict................................................................................................................. 138
57.5 ConfigConflict................................................................................................................. 139
57.6 TimeError ....................................................................................................................... 139
58 NDP Messages......................................................................................................................... 139

58.1 NDPSTART.................................................................................................................... 139
59 NETSTREAM Messages.......................................................................................................... 140

59.1 MALLOC_FAIL............................................................................................................... 140
59.2 FREE_FAIL.................................................................................................................... 140
59.3 NDPSTOP...................................................................................................................... 141
60 NTDP Messages ...................................................................................................................... 141

60.1 NTDPSTART ................................................................................................................. 141
60.2 NTDPSTOP ................................................................................................................... 141
61 NTP Messages ......................................................................................................................... 142

61.1 NTP_LOG ...................................................................................................................... 142

62 OAM Messages ........................................................................................................................ 142

62.1 LOCALERRFRAME....................................................................................................... 142
62.2 REMOTEERRFRAME ................................................................................................... 143
62.3 LOCALERRFRAMEPERIOD ......................................................................................... 143
62.4 REMOTEERRFRAMEPERIOD ..................................................................................... 144
62.5 LOCALERRFRAMESEC ............................................................................................... 144
62.6 REMOTEERRFRAMESEC............................................................................................ 144
62.7 REMOTEDYINGGASP .................................................................................................. 145
62.8 REMOTECRITICALE..................................................................................................... 145
63 OPTMOD Messages ................................................................................................................ 146

63.1 BIAS_HIGH.................................................................................................................... 146
63.2 TX_POW_HIGH............................................................................................................. 146
63.3 TYPE_ERR .................................................................................................................... 147
63.4 CFG_ERR...................................................................................................................... 147
63.5 MODULE_OUT .............................................................................................................. 147
63.6 MODULE_IN .................................................................................................................. 148
63.7 IO_ERR.......................................................................................................................... 148
63.8 CHKSUM_ERR.............................................................................................................. 149
63.9 TX_ALM_ON.................................................................................................................. 149
63.10 TX_ALM_OFF.............................................................................................................. 149
63.11 RX_ALM_ON ............................................................................................................... 150
63.12 RX_ALM_OFF ............................................................................................................. 150
63.13 MOD_ALM_ON............................................................................................................ 151
63.14 MOD_ALM_OFF.......................................................................................................... 151
63.15 TEMP_HIGH ................................................................................................................ 151
63.16 TEMP_LOW................................................................................................................. 152
63.17 TEMP_NORMAL ......................................................................................................... 152
63.18 VOLT_HIGH................................................................................................................. 153
63.19 VOLT_LOW ................................................................................................................. 153
63.20 VOLT_NORMAL .......................................................................................................... 153
63.21 RX_POW_HIGH .......................................................................................................... 154
63.22 RX_POW_LOW ........................................................................................................... 154
63.23 RX_POW_NORMAL.................................................................................................... 154
63.24 BIAS_LOW................................................................................................................... 155
63.25 BIAS_NORMAL ........................................................................................................... 155

63.26 TX_POW_LOW ........................................................................................................... 155

63.27 TX_POW_NORMAL .................................................................................................... 156
63.28 PHONY_MODULE....................................................................................................... 156
64 PBR6 Messages....................................................................................................................... 157

64.1 PBR6_LOG .................................................................................................................... 157
65 PIM Messages.......................................................................................................................... 157

65.1 INFO .............................................................................................................................. 158
65.2 ERR ............................................................................................................................... 158
66 PKEY Messages....................................................................................................................... 158

66.1 KEY_GENERATE.......................................................................................................... 158
66.2 KEY_GENERATE.......................................................................................................... 159
66.3 KEY_GENERATE.......................................................................................................... 159
66.4 KEY_ZEROIZE .............................................................................................................. 159
66.5 KEY_ZEROIZE .............................................................................................................. 160
66.6 KEY_ZEROIZE .............................................................................................................. 160
66.7 KEY_EXPORT ............................................................................................................... 161
66.8 KEY_EXPORT ............................................................................................................... 161
66.9 KEY_BACKUP ............................................................................................................... 161
66.10 KEY_BACKUP............................................................................................................. 162
67 PKI Messages .......................................................................................................................... 162

67.1 Local_Cert_Retrieval ..................................................................................................... 162
67.2 Local_Cert_Retrieval ..................................................................................................... 162
67.3 CA_Cert_Retrieval......................................................................................................... 163
67.9 Local_Cert_Request ...................................................................................................... 165
67.10 Local_Cert_Request .................................................................................................... 165
67.11 Local_Cert_Request .................................................................................................... 166
67.12 Import_Cert_File .......................................................................................................... 166
67.13 Import_Local_Cert ....................................................................................................... 166


67.18 Import_Local_Key........................................................................................................ 168
67.19 Import_Local_Key........................................................................................................ 169
67.20 Import_CA_Cert........................................................................................................... 169
67.21 Import_CA_Cert........................................................................................................... 169
67.22 Import_CA_Cert........................................................................................................... 170
67.23 Import_CA_Cert........................................................................................................... 170
67.24 Import_CA_Cert........................................................................................................... 170
67.25 Import_CA_Cert........................................................................................................... 171
67.26 Import_CA_Cert........................................................................................................... 171
67.27 Import_CA_Cert........................................................................................................... 172
67.28 Update_CA_Cert ......................................................................................................... 172
67.29 Update_CA_Cert ......................................................................................................... 172
67.30 Delete_CA_Cert........................................................................................................... 173
67.31 Delete_CA_Cert........................................................................................................... 173
67.32 Delete_CA_Cert........................................................................................................... 174
67.33 Delete_Local_Cert ....................................................................................................... 174
67.34 Delete_Local_Cert ....................................................................................................... 174
67.35 Verify_Cert ................................................................................................................... 175
67.36 Verify_Cert ................................................................................................................... 175
67.37 Verify_CA_Root_Cert .................................................................................................. 175
67.38 Verify_CA_Root_Cert .................................................................................................. 176
67.39 Retrieval_CRL.............................................................................................................. 176
67.40 Retrieval_CRL.............................................................................................................. 176
67.41 Update_CRL ................................................................................................................ 177
67.42 Update_CRL ................................................................................................................ 177
67.43 Update_CRL ................................................................................................................ 177
68 PORTAL Messages.................................................................................................................. 178

68.1 PORTAL_LOG ............................................................................................................... 178
68.2 PORTAL_LOG ............................................................................................................... 178
68.3 PORTAL_LOG ............................................................................................................... 178
68.4 PORTAL_LOG ............................................................................................................... 179
68.5 PORTAL_LOG ............................................................................................................... 179
69 Q921 Messages ....................................................................................................................... 179

69.1 Q921_Log ...................................................................................................................... 180
70 RDS Messages......................................................................................................................... 180

70.1 LOGIN............................................................................................................................ 180
70.2 LOGIN............................................................................................................................ 181
70.3 LOGIN............................................................................................................................ 181
70.4 LOGIN............................................................................................................................ 181
71 RM Messages........................................................................................................................... 182
71.1 RMLOG.......................................................................................................................... 182
72 RMON Messages ..................................................................................................................... 182

72.1 ADDINFO....................................................................................................................... 183
72.2 DELINFO ....................................................................................................................... 183
73 RMX Messages ........................................................................................................................ 183

73.1 LOG ............................................................................................................................... 183
74 RPR Messages......................................................................................................................... 184

74.1 TOPOINCONS............................................................................................................... 184
74.2 TOPOINCONSOVER .................................................................................................... 184
74.3 TOPOINSTAB................................................................................................................ 185
74.4 TOPOINSTABOVER ..................................................................................................... 185
74.5 STATNUMEXCED ......................................................................................................... 185
74.6 STATNUMEXCEEDOVER ............................................................................................ 186
74.7 MACDUP ....................................................................................................................... 186
74.8 MACDUPOVER ............................................................................................................. 186
74.9 IPDUP ............................................................................................................................ 187
74.10 IPDUPOVER................................................................................................................ 187
74.11 LRTTINCOMP.............................................................................................................. 188
74.12 LRTTINCOMPOVER ................................................................................................... 188
74.13 PROTINCONS............................................................................................................. 188
74.14 PROTINCONSOVER................................................................................................... 189
74.15 JBINCONS................................................................................................................... 189
74.16 JBINCONSOVER ........................................................................................................ 189
74.17 RESERBWEXCEED.................................................................................................... 190
74.18 RESERBWEXCEEDOVER.......................................................................................... 190
74.19 MISCABLING............................................................................................................... 191
74.20 MISCABLINGOVER .................................................................................................... 191
74.21 IDLEISOLATE.............................................................................................................. 191

74.22 IDLEISOLATEOVER ................................................................................................... 192
75 RRPP Messages ...................................................................................................................... 192

75.1 FAIL ............................................................................................................................... 192
75.2 RESTORE...................................................................................................................... 192
76 RSVP Messages ...................................................................................................................... 193

76.1 RSVP_LOG_INFO......................................................................................................... 193
77 SHELL Messages..................................................................................................................... 193

77.1 LOGIN............................................................................................................................ 194
77.2 LOGOUT........................................................................................................................ 194
77.3 CLI ................................................................................................................................. 194
77.4 CMD............................................................................................................................... 195
77.5 LOGINFAIL .................................................................................................................... 195
78 SNMP Messages...................................................................................................................... 196

78.1 GET................................................................................................................................ 196
78.2 SET ................................................................................................................................ 196
79 SOCKET Messages ................................................................................................................. 197

79.1 TCP MD5 ....................................................................................................................... 197
79.2 TCP NAPTHA ................................................................................................................ 198
79.3 SOCKETLOG................................................................................................................. 198
80 SSH Messages......................................................................................................................... 198

80.1 ACCEPTFAIL................................................................................................................. 198
80.2 LOGOUT........................................................................................................................ 199
80.3 LOGIN............................................................................................................................ 199
80.4 LOGINFAIL .................................................................................................................... 200
80.5 LOGINFAIL .................................................................................................................... 200
80.6 LOGINFAIL .................................................................................................................... 201
80.7 AUTHFAIL...................................................................................................................... 201
80.8 AUTHSUCC ................................................................................................................... 202
80.9 LOGOUT........................................................................................................................ 202
80.10 SFTPOPER.................................................................................................................. 203
81 TFTP Client Messages............................................................................................................. 203

81.1 TFTP_LOG .................................................................................................................... 203
82 TNLM Messages ...................................................................................................................... 204

82.1 LOG ............................................................................................................................... 204
83 TUNNEL Messages.................................................................................................................. 205

83.1 NOTICE ......................................................................................................................... 205

83.2 NOTICE ......................................................................................................................... 206
83.3 WARNING...................................................................................................................... 206
84 UDPH ....................................................................................................................................... 207

84.1 UDPH_LOG ................................................................................................................... 207
85 USERLOG Messages .............................................................................................................. 207

85.1 NAT................................................................................................................................ 207
85.2 FLOW1.0........................................................................................................................ 208
85.3 FLOW3.0........................................................................................................................ 209
86 VFS Messages ......................................................................................................................... 210

86.1 LOG ............................................................................................................................... 210
86.2 LOG ............................................................................................................................... 211
86.3 LOG ............................................................................................................................... 211
86.4 LOG ............................................................................................................................... 212
87 VMIB Messages ....................................................................................................................... 212

87.1 SIP Authenticate Failure ................................................................................................ 212
87.2 SIP Register Failure....................................................................................................... 213
87.3 SIP Server Switch.......................................................................................................... 213
88 VOS Messages......................................................................................................................... 213

88.1 ASSERT......................................................................................................................... 214
89 VRFFIB Messages ................................................................................................................... 214

89.1 log_vrffib ........................................................................................................................ 214
89.2 log_vrffib ........................................................................................................................ 215
89.3 log_vrffib ........................................................................................................................ 215
90 VRRP Messages ...................................................................................................................... 215

90.1 LogAuthFailed................................................................................................................ 216
90.2 PacketError .................................................................................................................... 216
90.3 ConfigError..................................................................................................................... 217
90.4 MasterChange ............................................................................................................... 217
90.5 SetDriver ........................................................................................................................ 218
90.6 SetDriver ........................................................................................................................ 219
90.7 TrapBecomeNewMaster ................................................................................................ 219
90.8 TrapAuthFailed .............................................................................................................. 219

1 Introduction
1.1 Overview
About the table in which the details of system log messages are filled, the
explanations of all the items of the table are stated here:
Item Description
Mnemonic The text string that uniquely describes the system message
Severity Level Single-digit code from 0 to 7 that indicates the severity of the message
This portion of the message might contain detailed information about the
event, such as terminal port numbers, network addresses, or addresses
that correspond to locations in the system memory address space.
Syslog Message
Because the information in these variable fields changes from message
to message, it is represented here by short strings enclosed in square
brackets ([ ]). A text string, for example, is represented as [string].
Variable Field The signification of the variable fields in syslog message format string
Explanation The signification indicated when system sends a syslog message
The action which triggers off system to send a syslog message. For the
Trigger Action
same syslog message, there is more than one trigger action possibly.
Example The instance of system log message
Recommended
The action to be done when such system log message occurs
Action
Trigger Action, Example and Recommended Action fields might occur many times in
the same table, if there are different trigger actions for that message. These three
fields should be bundled and sequenced by “Trigger Action->Example-
>Recommended Action” order.
1.2 System Log Message Format
This section describes system log messages as defined by the syslog protocol
(RFC3164) and how to understand the syslog message format.
<Int_16>TIMESTAMP HOSTNAME %%nnAAA/B/CCC(l):- -DevIP=x.x.x.x-Slot=k–XXX; YYYY
① ② ③ ④/⑤/⑥ ⑦ ⑧
Element Description

Element Description
① Combination of Facility and Severity defined in RFC3164
The time of event or error. The format can be configured by command

②
line.
③ The name of the device
④ Module name
⑤ Severity level. See the following table about severity level.
⑥ Mnemonic. The text string that uniquely describes the system message
⑦ Reserved section. It is used for system extendibility
The text string containing detailed information about the event or error
⑧
being reported
System log message severity level ranges from 0 to 7 and reflects the severity of the
condition, as defined in RFC3164. The lower the number is, the more serious the
situation is. The following table lists the severity levels.
Level Description
0 - emergency System is unusable
1 - alert Action must be taken immediately
2 - critical Critical conditions
3 - error Error conditions
4 - warning Warning conditions
5 - notification Normal but significant condition
6 - informational Informational messages
7- debugging Debug-level messages
There are some variable fields representation in system log message format. The
representations (no case-sensitive) of variable fields and the type of information in the
fields as follows:
Representation Description
LONG Decimal number
ULONG Decimal number
SHORT Decimal number
USHORT Decimal number

Representation Description
UCHAR Character
STRING Character string
IPADDR IP address
DATE Date
TIME Time
INTEGER Decimal number
COUNTER 32 bit Counter
GAUGE Gauge
TIMETICK Time
OCTET Character string
OPAQUE Character string
OID Object identifier
COUNTER64 64 bit Counter
1.3 System Log Message Module List

Module Name Full spelling
802.1X - 基于端口的网络接入控制协议
ADDR Address Management 地址管理
ARP Address Resolution Protocol 地址解析协议
ASPF Application Specific Packet Filter 基于应用层状态的包过滤
BFD Bidirectional Forwarding Detection 双向转发检测
CFM Configuration File Management 配置文件管理
CLST Cluster 集群
CMD Command 命令行
Constraint-based Shortest Path

CSPF 基于约束的最短路径优先
First
DEVM Device Management 设备管理
Dynamic Host Configuration

DHCP 动态主机配置协议
Protocol
DHCPR DHCP Relay DHCP中继
DHCPS DHCP Server DHCP服务器
DHCPSNOOP DHCP Snooping DHCP侦听

DLDP Device Link Detection Protocol 设备链路检测协议
Data Plane Unicast Reverse Path 数据平面单播反向路径转发（多

DPURPF
Forwarding 核）
ETHOAM Ethernet OAM 以太网OAM
FIBV4 IPv4 Forward Information Base IPv4转发信息表
FILTER 包过滤防火墙
FTP Server File Transfer Protocol Server FTP服务器
Generic Attribute Registration

GARP 通用属性注册协议
Protocol
HA High Availability 高可靠性
HW Authentication Bypass
HABP HW旁路认证协议
Protocol
HTTPD Hypertext Transfer Protocol 超文本传输协议
HTTPS Secure HTTP 安全的HTTP
HWCM H3C-CONFIG-MAN-MIB H3C配置管理MIB
Internet Group Management

IGMP 互联网组管理协议
Protocol
IFNET Interface Management 接口管理
IKE Internet Key Exchange 因特网密钥交换
IPDBG IP Debug IP模块调试日志
IP Customer Information
IPCIM IP用户信息管理
Management
IPSec IP Security IP安全
IPv6 Forward Information Base

IPV6FIBC IPv6转发信息表
Cache
IPV6PP IPv6 Packet Processing IPv6报文处理
Intermediate System-to-
Intermediate System intra-domain 中间系统到中间系统的域内路由信
ISIS
routing information exchange 息交换协议
protocol
L2TP Layer 2 Tunnel Protocol 二层隧道协议
L2V Layer 2 VPN 二层VPN
L3VPN Layer 3 VPN 三层VPN
LAGG Link Aggregation Group 链路聚合组
LDP Label Distribution Protocol 标签分发协议
LLC2 Logical Link Control (type 2) 第二类逻辑链路控制

LLDP Link Layer Discovery Protocol 链路层发现协议
LS Local Server 本地服务器
LSPM Label Switched Path Management 标签交换路径管理
LWPS
MCS Multicast Snooping 组播窥探
Multicast Forwarding Information

MFIB 组播转发信息库
Base
Multicast Listener Discovery

MLD 组播侦听者发现协议
Protocol
MPLS Operation, Administration

MPLS OAM MPLS操作、管理和维护
and Maintenance
QoS Quality of Service 服务质量
MCDP BRIDGE Multiple Core Data Plane Bridge 多核桥模块
MRM Multicast Routing Management 组播路由管理
Multicast Source Discovery

MSDP 组播源发现协议
Protocol
MSTP Multiple Spanning Tree Protocol 多生成树协议
Network Address Translation-

NATPT 附带协议转换的网络地址转换
Protocol Translation
ND Neighbor Discovery 邻居发现协议
NDP Neighbor Discovery Protocol 邻居发现协议
Neighbor Topology Discover

NTDP 邻居拓扑发现协议
Protocol
NTP Network Time Protocol 网络时间协议
Operation, Administration and

OAM 操作、管理和维护
Maintenance
OPTMOD
PBR6 Policy-based-route for IPv6 IPv6单播策略路由
PIM Protocol Independent Multicast 协议无关组播
PKEY public key 公开密钥管理
PKI Public Key Infrastructure 公钥基础设施
PORTAL -
D信道的数据链路层协议（它定义
了网络接口上第2层实体间经D信道
Q921 -
交换信息的规则，同时支持第3层
实体的接入）

RADIUS (Remote Authentication

RDS 远程认证拨号用户服务
Dial-In User Service)
RM Routing Management 路由管理
RMON Remote Monitoring 远程网络监视
RMX IPX Routing Management IPX路由管理
RPR Resilient Packet Ring 弹性分组环
RRPP Rapid Ring Protection Protocol 快速环网保护协议
RSVP Resource reSerVation Protocol 资源预留协议
SHELL - 终端用户
Simple Network Management

SNMP 简单网络管理协议
Protocol
SOCKET
SSH Secure Shell 安全外壳
TFTP Client Trivial File Transfer Protocol Client 简单文件传输协议客户端
TNLM Tunnel Management MPLS隧道管理
TUNNEL - 隧道
UDPH UDP Helper UDP中继
USERLOG User log 用户日志
VFS File System Management 文件系统管理
VMIB Voice MIB 语音MIB
VOS Virtual Operation System 虚拟操作系统
VRFFIB Virtual Routing and Forwarding 虚拟路由转发
Virtual Router Redundancy

VRRP 虚拟路由器冗余协议
Protocol
2 802.1X Messages
This section contains the entire system log messages related to 802.1X.
2.1 DOT1X_LOG
Mnemonic DOT1X_LOG Severity Level 3
Port:[STRING],Auth:[ULONG],Authentication failed: 802.1X

Syslog Message
authentication failed.

$1: Port number

Variable Fields
$2: Authentication Index
Explanation The authentication of an 802.1x user failed.
Trigger Action Failed to authenticate an 802.1x user.
%Apr 26 12:07:04:802 2000 SysName 8021X/3/DOT1X_LOG:

Example
Port:11,Auth:0,Authentication failed: 802.1X authentication failed.
Recommended
No action is recommended.
Action
2.2 DOT1X_LOG
Port:[STRING],Auth:[ULONG],SmartOn authentication failed: The

Syslog Message
SwitchID is mismatched.
$1: Port number

Variable Fields
Trigger Action The SwitchID is mismatched.

Example Port: 11,Auth:0,SmartOn authentication failed: The SwitchID is
mismatched.
Recommended
Action
2.3 DOT1X_LOG
Port:[STRING],Auth:[ULONG],SmartOn authentication failed: The

Syslog Message
Password is mismatched.
$1: Port number

Variable Fields
Trigger Action The Password is mismatched.

Example Port:11,Auth: 0,SmartOn authentication failed: The Password is
mismatched.
Recommended
Input correct username or password.
Action

2.4 DOT1XSOP_ACL_NOT_SUPPORT
Mnemonic DOT1XSOP_ACL_NOT_SUPPORT Severity Level 3
Syslog Message [STRING]
Variable Fields $1: the log string
Explanation The type of authorization ACL can’t be supported by 802.1X.
Trigger Action The authorization ACL from AAA server can’t be supported.
%Apr 26 12:07:04:802 2000 SysName 8021X/3/DOT1XSOP_LOG:

Example
Port: 11, Auth: 0, This type of ACL is not supported.
Recommended Reconfigure the authorization ACL and make sure the ACL group
Action number is between 2000~4999.
2.5 DOT1XSOP_ACL_NOT_CONFIGURED
Severity
Mnemonic DOT1XSOP_ACL_NOT_CONFIGURED 3
Level
Explanation The authorization ACL is not configured on the device.
AAA server assigned an authorization ACL which is not configured on

Trigger Action
the device.

Example
Port: 11, Auth: 0, Specified ACL does not exist.
Recommended Reconfigure the authorization ACL on AAA server or configure the

Action ACL group on device.
2.6 DOT1XSOP_ACL_DEL_FAILED
Mnemonic DOT1XSOP_ACL_DEL_FAILED Severity Level 3
Something error when the driver removes the authorization ACL

Explanation
from port.
Trigger Action Remove authorization ACL from port failed.


Example
Port: 11, Auth: 0, Failed to delete the specified ACL.
Recommended When this information occurs, there is some hardware fault with the
Action device. Please turn to technical support engineer.
2.7 DOT1XSOP_ACL_ADD_FAILED
Mnemonic DOT1XSOP_ACL_ADD_FAILED Severity Level 3
Something error when the driver applies the authorization ACL to

Explanation
port.
Trigger Action Apply authorization ACL to port failed.

Example
Port: 11, Auth: 0, Failed to apply the specified ACL.
Recommended When this information occurs, it seems that there is some hardware
Action fault with the device. Please turn to technical support engineer.
2.8 DOT1XSOP_ACL_RESOUCE_EXHAUSTED
Severity
Mnemonic DOT1XSOP_ACL_RESOUCE_EXHAUSTED 3
Level
Apply authorization ACL to port failed because the hardware resource

Explanation
is not enough.
Trigger Action The authorization ACL contains too many rules.

Example Port: 11, Auth: 0, Hardware resource is not enough. Can't apply the
specified ACL.
Recommended
Configure the authorization ACL correctly.
Action
2.9 DOT1XSOP_ACL_CONFLICT_WITH_ MQC

DOT1XSOP_ACL_CONFLICT_WITH_ Severity
Mnemonic 3
MQC Level

Apply authorization ACL to port failed because MQC is configured on

Explanation
this port.
Trigger Action Apply authorization ACL to a port that MQC is configured on it.

Example
Port: 11, Auth: 0, ACL conflicts with MQC. Can't apply it.
Recommended
Undo the MQC configuration on this port.
Action
2.10 DOT1XSOP_ACL_CONFLICT_WITH_ USERMAC

DOT1XSOP_ACL_CONFLICT_WITH_ Severity
Mnemonic 3
USERMAC Level
Apply authorization ACL to port failed because the MAC information

Explanation
in the rules conflict with the user’s MAC.
Apply a link layer ACL to a port of which rules contain source MAC
Trigger Action
information.
%Apr 26 12:07:04:802 2000 SysName

Example 8021X/3/DOT1XSOP_LOG:Port:11,Auth:0, ACL contains source
MAC information. Can't apply it.
Recommended Don’t configure the source MAC field of the rules in authorization
Action ACL.
2.11 DOT1XSOP_ACL_CONFLICT_WITH_FLOW_TEMPLATE
Severity
Mnemonic DOT1XSOP_ACL_CONFLICT_WITH_FLOW_TEMPLATE 3
Level
Syslog
[STRING]
Message
Apply authorization ACL to port failed because it conflicts with the flow
Explanation
template configured on this port.
Trigger Action The flow template conflicts with the authorization ACL.
%Apr 26 12:07:04:802 2000 SysName 8021X/3/DOT1XSOP_LOG: Port:

Example
11, Auth: 0, ACL conflicts with the flow template. Can't apply it.

Recommended
Reconfigure the flow-template on this port.
Action
2.12 DOT1XEAD_LOG
Mnemonic DOT1XEAD_LOG Severity Level 3
Setting an EAD rule on the port failed because the operation is

Explanation
wrong.
Trigger Action The operation is wrong.
%Apr 26 12:07:04:802 2000 SysName 8021X/3/DOT1XEAD_LOG:

Example Slot: 1,Port: Ethernet1/0/11, 802.1X EAD failed to set EAD rule :
The operation is wrong!
Recommended
Continue to set an EAD rule for another port.
Action
2.13 DOT1XEAD_LOG
Setting an EAD rule on the port failed because the rule does not
Explanation
exist.
Trigger Action The rule does not exist.
%Apr 26 12:07:04:802 2000 SysName

Example 8021X/3/DOT1XEAD_LOG:Slot: 1,Port: Ethernet1/0/11, The driver
ACL does not include the rule!
Recommended
Action
2.14 DOT1XEAD_LOG

Setting an EAD rule on the port failed because the number of driver
Explanation
ACLs has reached the maximum!
Trigger Action The number of driver ACLs has reached the maximum!
%Apr 26 12:07:04:802 2000 SysName

Example 8021X/3/DOT1XEAD_LOG:Slot: 1,Port: Ethernet1/0/11, The
number of driver ACLs has reached the maximum!
Recommended
Action
2.15 DOT1XEAD_LOG
Setting an EAD rule on the port failed because the driver does not
Explanation
support the operation.
Trigger Action The driver does not support the operation.
%Apr 26 12:07:04:802 2000 SysName

Example 8021X/3/DOT1XEAD_LOG:Slot: 1,Port: Ethernet1/0/11, The driver
does not support the operation!
Recommended
Action
2.16 DOT1XEAD_LOG
Setting an EAD rule on the port failed because the rule already
Explanation
exists.
Trigger Action The rule already exists.
%Apr 26 12:07:04:802 2000 SysName

Example 8021X/3/DOT1XEAD_LOG:Slot: 1,Port: Ethernet1/0/11, The rule
already exists!
Recommended
Action

3 ADDR Messages
This section contains the entire system log messages related to IPV6 AM.
3.1 Information
Mnemonic Information Severity Level 2
Syslog Message [string]
Variable Fields $1: Information for getting control or add address
Explanation The information when failing to get control block or add address
Failed to get control block

Trigger Action IO board fails to add address when receiving address by IPC from
main board.
Example IPV6 ADDRESS 2::2 add error on slot 3
Recommended
Action
3.2 Information
Mnemonic Information Severity Level 2
Variable Fields $1: The information for DAD message
Explanation Failed to send DAD message to IO board
Trigger Action Failed to send DAD message to IO board
Example Failed to send DAD message to slot 3
Recommended
Action
3.3 RESOURCE

Mnemonic RESOURCE Severity Level 4
Syslog Message Hardware resources insufficient.
Variable Fields
Explanation The driver has no resource.
The log is displayed when the driver no enough resource for

Trigger Action
complete command.
%Apr 26 12:22:32:877 2000 SysName ADDR/5/RESOURCE:

Example
Hardware resources insufficient.
Recommended
Action
4 ARP Messages
This section contains the entire system log messages related to ARP.
4.1 ROUTECONFLICT
Mnemonic ROUTECONFLICT Severity Level 3
Syslog Message Route conflict found, IP:[ipaddr], VrfIndex:[ULONG]
$1: IP address
Variable Fields
$2: VrfIndex
The driver returns route conflict when the ARP entry is added to the
Explanation
driver.
If route conflict is found when ARP entry is added to the driver, this
Trigger Action
log is displayed.
%Aug 15 20:23:38:664 2007 SysName ARP/3/ROUTECONFLICT:

Example
Slot=1;Route conflict found, IP:80.1.1.1, VrfIndex:0
Recommended
Action
4.2 DUPIFIP

Mnemonic DUPIFIP Severity Level 3
Syslog Message Duplicate address [ipaddr] on interface [string], sourced by [string]
$1: IP address
Variable Fields $2: interface name
$3: MAC Address
Explanation The ARP checks the Duplicate address.
Trigger Action The ARP checks the Duplicate address.
%Aug 15 20:23:38:664 2007 SysName ARP/3/DUPIFIP: Slot=1;

Example Duplicate address 1.1.1.1 on interface eth1/1/1, sourced by 0015-
e944-a947
Recommended
Action
4.3 DUPVRRPIP
Mnemonic DUPVRRPIP Severity Level 3
IP address [ipaddr] collision with VRRP virtual IP address on

Syslog Message
interface [string], sourced by [string]
$1: IP address
Variable Fields $2: interface name
$3: MAC Address
Explanation The ARP checks VRRP virtual IP address collision.
Trigger Action The ARP checks VRRP virtual IP address collision.
%Aug 15 20:23:38:664 2007 SysName ARP/3/DUPIFIP: Slot=1;

Example IP address 1.1.1.1 collision with VRRP virtual IP address on interface
eth1/1/1, sourced by 0015-e944-a947
Recommended
Action
4.4 DUPGLOBALIP

Mnemonic DUPGLOBALIP Severity Level 3
IP address [ipaddr] collision with Global or Import IP address,

Syslog Message
sourced by [string]
$1: IP address
Variable Fields
$2: MAC Address
Explanation The ARP checks Global or Import IP address collision.
Trigger Action The ARP checks Global or Import IP address collision.
%Dec 7 15:49:48:498 2007 SysName ARP/3/DUPGLOBALIP:IP

Example address 30.1.1.1 collision with Global or Import IP address, sourced
by 0000-0000-0001
Recommended
Action
4.5 ARPDTC
Mnemonic ARPDTC Severity Level 4
\r\n ARP Detection found illegal ARP packet on interface [string],

Syslog Message
forged IP: [string].
$1:interface name
Variable Fields
$2:ip address
Explanation An invalid ARP packet is detected and dropped by ARP Detection.
Trigger Action An invalid ARP packet is detected and dropped by ARP Detection.
%Feb 27 08:37:25:806 2008 SysName ARP/4/ARPDTC:

Example ARP Detection found illegal ARP packet on interface
Ethernet0/1/0, forged IP: 192.168.20.14.
Recommended
Action
4.6 SRC-MAC

Mnemonic SRC-MAC Severity Level 4
Syslog Message \r\n An attack from MAC [string] was detected on interface [string].
$1:MAC address
Variable Fields
$2:interface name
Explanation Attack is detected by ARP fixed source MAC address anti-attack.
Trigger Action Attack is detected by ARP fixed source MAC address anti-attack.
%Feb 27 08:36:25:939 2008 SysName ARP/4/SRC-MAC:

Example An attack from MAC 0000-5e14-0e00 is detected on interface
Ethernet0/1/0.
Recommended
Action
5 ASPF Messages
This section contains the entire system log messages related to ASPF.
5.1 SESS_LOG
Mnemonic SESS_LOG Severity Level 3
[string] session originator ([string]:[ulong]) sent [ulong] bytes --

Syslog Message
destination ([string]:[ulong]) sent [ulong] bytes
$1: Protocol name
$2:.Source IP address
$3: Source port

Variable Fields
$4: Destnation IP address
$5: Destnation port
$6: The number of transmitted bytes
Explanation The total bytes sent by the two parts of session
Trigger Action Delete an established session
%Feb 20 19:22:57:719 2007 SysName ASPF/4/SESS_LOG: ftp

session originator (
Example
100.0.0.1:1025) sent 1116 bytes -- destination (200.0.0.1:21) sent
1105 bytes
Recommended
Action

5.2 SMTP_INVALID_COMMAND
Mnemonic SMTP_INVALID_COMMAND Severity Level 2
Syslog Message Invalid SMTP command transmitted from [string]
Variable Fields $1: Source IP address
Explanation Invalid SMTP command transmitted
Trigger Action ASPF detects unknown SMTP command
%Feb 20 19:22:57:719 2007 SysName ASPF/3/

Example SMTP_INVALID_COMMAND: Invalid SMTP command transmitted
from 100.1.1.1 25
Recommended
Action
5.3 HTTP_JAVA_BLOCK
Mnemonic HTTP_JAVA_BLOCK Severity Level 2
Syslog Message JAVA program from [string]:[ulong] to [string]:[ulong] is blocked
$2: Source port

Variable Fields
$4: Destnation port
Explanation ASPF block a request of Java applet
Trigger Action ASPF detects a request form user for java applet
%Feb 20 19:22:57:719 2007 SysName ASPF/3/

Example HTTP_JAVA_BLOCK: JAVA program from 192.168.0.120:8080 to
220.0.0.100:1026 is blocked
Recommended
Action
5.4 ASPF_LOGID_FTP_SESS_NOT_AUTH
Severity
Mnemonic FTP_SESSION_NOT_AUTHENTICATED 2
Level
The session transmitted command before ID authentication -- FTP

Syslog Message
client [string] FTP server [string]
Variable Fields

Explanation The session transmits command before ID authentication
Trigger Action ASPF detects wrong command before ID authentication
%Feb 20 19:22:57:719 2007 SysName ASPF/3/

FTP_SESSION_NOT_AUTHENTICATED: The session transmitted
Example
command before ID authentication -- FTP client 172.0.0.1 FTP server
200.0.0.50
Recommended
Action
5.5 HOST_TCP_ALERT_ON
Mnemonic HOST_TCP_ALERT_ON Severity Level 2
Connections to the host [string] exceeds the maximum incomplete

Syslog Message
connection number ([ulong])
$1:.IP address
Variable Fields
$2: Incomplete connection number
Connections to the host exceeds the maximum incomplete

Explanation
connection number
Trigger Action no longer to be used
%Feb 20 19:22:57:719 2007 SysName ASPF/3/

Example HOST_TCP_ALERT_ON:Connections to the host 20.0.0.1 exceeds
the maximum incomplete connection number 10000
Recommended
Action
6 BFD Messages
This section contains the entire system log messages related to BFD
6.1 FSM
Mnemonic FSM Severity Level 4

Sess[[STRING]/ [STRING], [STRING], [STRING]], Sta: [STRING]->

Syslog Message
[STRING], Diag: [ULONG]
$1: The source address of bfd session
$2: The destination address of bfd session
$3: The interface name
Variable Fields $4: The working mode of bfd session
$5: The name of fsm before changing
$6: The name of fsm after changing
$7: The code of diagnostics
Explanation The fsm of bfd session has been changed
Trigger Action The fsm of bfd session has been changed
%Dec 27 14:23:16:194 2007 SysName BFD/4/LOG: Sess [3.3.3.4/

Example
3.3.3.3, S0/2/0, Ctrl], Sta: DOWN->INIT, Diag: 0
Recommended
Action
6.2 no_echo_source_ip
Mnemonic No_echo_source_ip Severity Level 4
The source address located in bfd echo packet has not been
Syslog Message
specified, please set it
Variable Fields
Explanation Source address of bfd echo packet has not been configured.
Trigger Action Source address of bfd echo packet has not been configured.
%Dec 27 14:30:41:547 2007 5500 BFD/4/LOG:The source address

Example
located in bfd echo packet has not been specified, please set it
Recommended
Please specify source address under system view.
Action
7 CFM Messages
This section contains the entire system log messages related to CFM.
7.1 CFM_LOG
Mnemonic CFM_LOG Severity Level 4

#1 \r\nCommand %s fails to recover configuration.
Variable Fields $1: Command string.
Explanation Configuration recovery failed.
Trigger Action Recover configuration.
%Feb 25 01:04:56:662 2007 SysName CFM/4/CFM_LOG:

Example
Command vlan 100 fails to recover configuration.
Recommended
Check sequence of the command string in configuration file.
Action
\r\nThe size of configuration file is too large. \r\nConfiguration file is

#2
skipped.
Variable Fields
Explanation The size of configuration file is too large.
Trigger Action The size of configuration file is too large.
Example The size of configuration file is too large.
Configuration file is skipped.
Recommended
Check the configuration file
Action
\r\nThe size of configuration gotten from auto-configuration is too

#3
large. \r\n Configuration is skipped.
Variable Fields
The size of configuration gotten from auto-configuration is too

Explanation
large.
The size of configuration gotten from auto-configuration is too

Trigger Action
large.
%Feb 25 01:04:56:662 2007 SysName CFM/4/CFM_LOG: The

Example size of configuration gotten from auto-configuration is too large.
Configuration is skipped.
Recommended
Check the configuration gotten from auto-configuration
Action
Running configuration is too large. The master board fails to send

#4
configuration to the slave board.
Variable Fields
Explanation Running configuration is too large
Trigger Action Running configuration is too large

%Feb 25 01:04:56:662 2007 SysName CFM/4/CFM_LOG: Running

Example configuration is too large. The master board fails to send
configuration to the slave board.
Recommended
Check the configuration
Action
#5 \r\nCommand %s fails to match in cmdmode %s, because %s.
$1: command string
Variable Fields $2: command mode
$3: reason of match unsuccessfully
Explanation Command fails to match when recover configuration.
Trigger Action Command fails to match when recover configuration.

Example Command controller E3 8/0 fails to match in cmdmode system,
because Unrecognized command.
Recommended
Check the configuration.
Action
8 CLST Messages
This section contains the entire system log messages related to CLST.
8.1 Info
Mnemonic Info Severity Level 5
Syslog Message [string].
Variable Fields $1: some common info
Mostly used to define the SNMP, IP address and password in

Explanation
HGMP.
Trigger Action Configure SNMP, IP address, and password.
%Apr 27 16:38:44:752 2000 SysName CLST/5/LOG: ip:** user:**

Example command:snmp-agent target-host trap address udp-domain 1.1.1.1
params securityname cluster
Recommended
Action
8.2 Member

Mnemonic Member Severity Level 4
Syslog Message [string].
Variable Fields $1: some common info
Explanation Mostly used for member remote control in HGMP.
The administrator upgrades, configures or transmits files to a

Trigger Action
member device.
%Apr 27 16:38:44:752 2000 SysName CLST/4/LOG:

Example
member 1 : auto restore cfg timeout
Recommended
Action
8.3 MemberJoinCluster
Mnemonic MemberJoinCluster Severity Level 4
Syslog Message Member[string]is joined in cluster [string].
$1: The number of member device.

Variable Fields
$2: The name of cluster.
A member with the $1 number has joined in the cluster $2.

Explanation
(Information displayed on the administrator)
Trigger Action When A member has joined in the cluster.

Example
Member 00e0-5502-0000 is joined in cluster cluster1.
Recommended
Action
8.4 JoinStack
Mnemonic JoinStack Severity Level 4
Syslog Message Member[string]is joined in stack.
Variable Fields $1: The number of the member device.
A member with the $1 number has joined in the stack. (Information

Explanation
displayed on the administrator)
Trigger Action When A member has joined in the stack.

Example
Member 00e0-5502-0000 joined in stack.

Recommended
Action
8.5 DeleteCluster
Mnemonic DeleteCluster Severity Level 4
Syslog Message Member[string]in cluster is deleted.
Variable Fields $1: The number of member device.
A member with the $1 number has deleted from the cluster.

Explanation
(Information displayed on the administrator)
Trigger Action When A member has deleted from the cluster.

Example
Member 00e0-5502-0000 in cluster is deleted.
Recommended
Action
8.6 DeleteStack
Mnemonic DeleteStack Severity Level 4
Syslog Message Member[string]in stack is deleted.
A member in stack is deleted. (Information displayed on the

Explanation
administrator)
Trigger Action When A member in stack is deleted.
%Apr 27 16:40:50:592 2000 SysName CLST/4/LOG Member00e0-

Example
5502-0000 in stack is deleted.
Recommended
Action
8.7 RejoinCluster
Mnemonic RejoinCluster Severity Level 4
Syslog Message Member[string]in cluster is rejoined.

When shakehand error between the administrator and the member

device, without delete operation. The member device can rejoin the
Explanation
cluster when shakehand recover to usual. (Information displayed on
the administrator)
When he member device rejoined the cluster after shakehand error

Trigger Action
for sometime.

Example
Member 00e0-5502-0000 in cluster is rejoined.
Recommended
Action
8.8 AlreadyDown
Mnemonic AlreadyDown Severity Level 4
Syslog Message Member[string]in cluster is down.
When the administrator hasn’t received the member’s shakehand

Explanation packet for sometime. The administrator will think the member is
down. (Information displayed on the administrator)
When the command hasn’t received the member’s shakehand

Trigger Action
packet. And the time is long than the holdtime.

Example
Member 00e0-5502-0000 in cluster is down.
Recommended Check that if the communication between the administrator and the
Action member error or the member device is down.
8.9 SwitchJoinCluster
Severity
Mnemonic SwitchJoinCluster 4
Level
Syslog Message Switch is joined in cluster [string]
Variable Fields $1: The name of cluster
A member is added into cluster. (Information displayed on the

Explanation
member device)
Trigger Action When a member device is added into cluster.

Example
switch 00e0-5502-0000 is joined in cluster cluster1.
Recommended
Action

8.10 SwitchJoinStack
Severity
Mnemonic SwitchJoinStack 4
Level
Syslog Message Switch is joined in stack.
Variable Fields -
A member is added into a cluster. (Information displayed on the

Explanation
member device)
Trigger Action When a member is added into a stack.

Example
Switch is joined in stack.
Recommended
Action
8.11 SwitchDeleteCluster
Severity
Mnemonic SwitchDeleteCluster 4
Level
Syslog Message Switch is deleted by cluster [string].
Variable Fields $1: The name of cluster
A member is deleted from cluster. (Information displayed on the

Explanation
member device)
Trigger Action When a member device is deleted.

Example
Switch is deleted by cluster cluster1.
Recommended
Action
8.12 SwitchDeleteStack
Severity
Mnemonic SwitchDeleteStack 4
Level
Syslog Message Switch is deleted by stack.
Variable Fields -

A member in stack is deleted. (Information displayed on the member

Explanation
device)
Trigger Action When a member in stack is deleted.

Example
Switch is deleted by stack.
Recommended
Action
8.13 CommandDown
Severity
Mnemonic CommandDown 4
Level
Syslog Message Cluster administrator is down.
Variable Fields
When the member hasn’t received the administrator’s shakehand

Explanation packet for sometime. The member will think the administrator is
down. (Information displayed on the member device)
When the member hasn’t received the administrator’s shakehand

Trigger Action
packet. And the time is long than the hold time.

Example
Member 00e0-5502-0000 in cluster is down.
Recommended Check that if the communication between the administrator and the
Action member error or the administrator is down.
8.14 SwitchRejoinCluster
Severity
Mnemonic SwitchRejoinCluster 4
Level
Syslog Message Switch is rejoined in cluster.
Variable Fields
When shakehand error between the administrator and the member

device, without delete operation. The member device can rejoin the
Explanation
cluster when shakehand recover to usual. (Information displayed on
the member device)
When he member switch rejoind the cluster after shakehand error for
Trigger Action
sometime.
%Apr 27 16:46:22:681 2000 SysName CLST/4/LOG: Switch is

Example
rejoined in cluster.
Recommended
Action

8.15 LOG
Mnemonic LOG Severity Level 4
Syslog Message Member [string] succeeded in the web-user configuration.
Variable Fields $1: Member ID.
Explanation The specific member finished configuring the web user.
Trigger Action The member is added into white list of cluster.
%Apr 26 12:02:26:525 2000 4500G CLST/4/LOG:

Example
Member 1 succeeded in the web-user configuration.
Recommended
No action is recommended
Action
8.16 LOG
Syslog Message Member [string] failed to configure the web-user command.
Variable Fields $1: Member ID.
Explanation The specific member failed to configure the web user.
Trigger Action The member is added into white list of cluster.
%Apr 26 12:15:52:412 2000 4500G CLST/4/LOG:

Example
Member 1 failed to configure the web-user command.
Recommended
Check whether the member switch is in the white list.
Action
9 CMD Messages
This section contains the entire system log messages related to CMD.
9.1 REBOOT
Mnemonic REBOOT Severity Level 4

Syslog Message \r\n [string]: Cancel reboot parameters at [string].
$1: The configuration user.

Variable Fields
$2: The date and time when the schedule reboot is cancelled.
Explanation The schedule reboot is cancelled.
Trigger Action The schedule reboot is cancelled.
%Feb 26 05:36:20:876 2007 SysName CMD/4/REBOOT:

Example
con0: Cancel reboot parameters at 05:36:20 2007/02/26.
Recommended
Action
9.2 REBOOT
Syslog Message \r\n***\r\n*** --- REBOOT IN ONE MINUTE ---\r\n***
Variable Fields
Explanation Device will reboot in one minute.
Trigger Action There is one minute to the schedule reboot time.
***
Example
*** --- REBOOT IN ONE MINUTE ---
***
Recommended
The device will reboot.
Action
9.3 REBOOT

\r\nReboot parameters become invalid because [string] changed

Syslog Message
system clock.
Variable Fields $1: The configuration user.
Explanation Somebody changed system clock.
Trigger Action Change system clock.

Example Reboot parameters become invalid because vty0 (192.168.28.28)
changed system clock.
Recommended
Action
9.4 REBOOT
\r\n[string]: Set schedule reboot parameters at [string], and system

Syslog Message
will reboot at [string].
$1: The configuration user.
Variable Fields $2: The date and time when this schedule is set.
$3: The date and time when the device will reboot on schedule.
Explanation A schedule reboot is set successfully.
Trigger Action One user sets the schedule reboot successfully.

Example con0: Set schedule reboot parameters at 05:36:08 2007/02/26, and
system will reboot at 08:08 2007/02/28.
Recommended
Don’t forget the time when the device will reboot.
Action
10 CSPF Messages
This section contains the entire system log messages related to CSPF.
10.1 LOG
Variable Fields $1: The system log string.
Explanation Eable or disable CSPF function

Trigger Action Enable or disable CSPF
Example %Jan 20 17:00:01:469 2007 Router1 CSPF/7/LOG: Disable CSPF
Recommended
Action
11 DEVM Messages
This section contains the entire system log messages related to DEVM.
11.1 BOARDREMOVE
Mnemonic BOARDREMOVE Severity Level 4
Board is removed from Frame [INTEGER] Slot [INTEGER], type is

Syslog Message
[STRING].
$1: The frame ID
Variable Fields $2: The slot ID.
$3: The board’s type.
Explanation An IO or slave board has been removed from a slot.
Trigger Action Remove a board from slot.
%Feb 11 16:30:09:140 2007 SysName DEV/4/BOARD REMOVED:

Example
Board is removed from Frame 0 Slot 1, type is LS81VP4C.
Recommended
Action
11.2 BOARDOK
Mnemonic BOARDOK Severity Level 4
Board state changes to NORMAL on Frame [INTEGER] Slot

Syslog Message
[INTEGER], type is [STRING].
$1: The frame ID
Explanation An IO or slave board completes initialization
Trigger Action Insert an IO or slave board into a slot

%Feb 11 16:30:09:140 2007 SysName DEV/4/BOARD STATE

NORMAL:
Example
Board state changes to NORMAL on Frame 0 Slot 1, type is
LS81VP4C.
Recommended
Action
11.3 BOARDFAULT
Mnemonic BOARDFAULT Severity Level 4
Board state changes to FAULT on Frame [INTEGER] Slot

Syslog Message
$1: The frame ID.
Explanation An IO or slave board’s state changes to fault.
Insert an IO or slave board into a slot

Trigger Action
Reboot an IO or slave board
%Feb 11 16:30:09:140 2007 SysName DEV/4/BOARD STATE

FAULT:
Example
Board state changes to FAULT on Frame 0 Slot 1, type is
LS81VP4C.
Recommended
Action
11.4 BOARDLOADING
Mnemonic BOARDLOADING Severity Level 4

Syslog Message Board is loading file on Frame [INTEGER] Slot [INTEGER].
$1: The frame ID

Variable Fields
$2: The slot ID.
Explanation IO board starts to load app from master board
Trigger Action Insert an IO board into a slot.
%Feb 11 16:30:09:140 2007 SysName DEV/4/BOARD LOADING:

Example
Board is loading file on Frame 0 Slot 1.
Recommended
Action
11.5 CARDREMOVE
Mnemonic CARDREMOVE Severity Level 4
SubCard is removed from Frame [INTEGER] Slot [INTEGER]

Syslog Message
SubSlot [INTEGER], type is [STRING].
$1: The frame ID
$2: The slot ID.

Variable Fields
$3: The subslot ID
$4: The type of the subcard.
Explanation A subcard is removed from a subslot.
Trigger Action Remove a subcard from a subslot.
%Feb 11 16:30:09:140 2007 SysName DEV/4/SUBCARD

REMOVED:
Example
SubCard is removed from Frame 0 Slot 1 SubSlot 1, type is
LS81VP4C.
Recommended
Action
11.6 CARDINSERT
Mnemonic CARDINSERT Severity Level 4

SubCard is inserted in Frame [INTEGER] Slot [INTEGER] SubSlot

Syslog Message
$1: The frame ID
$2: The slot ID.

Variable Fields
$3: The subslot ID
Explanation A subcard is inserted into a subslot.
Trigger Action Insert a subcard into a subslot.

INSERTED:
Example
SubCard is inserted in Frame 0 Slot 1 SubSlot 1, type is
LS81VP4C.
Recommended
Action
11.7 CARDFAULT
Mnemonic CARDFAULT Severity Level 4
SubCard state changes to FAULT on Frame [INTEGER] slot

Syslog Message
[INTEGER] SubSlot [INTEGER], type is [STRING].
$1: The frame ID
$2: The slot ID.

Variable Fields
$3: The subslot ID
Explanation A subcard’s state changes to fault.
Trigger Action Reboot a subcard.
%Feb 11 16:30:09:156 2007 SysName DEV/4/SUBCARD FAULT:

Example SubCard state changes to FAULT on Frame 0 slot 1 SubSlot 1,
type is LS81VP4C.
Recommended
Action
11.8 POWERRECOVER
Mnemonic POWERRECOVER Severity Level 4

Syslog Message Power [INTEGER] recovered.
Variable Fields $1: The power id
Explanation A power state changes to OK from failed or absent
Trigger Action Insert a power into its slot
%Feb 11 16:30:09:156 2007 SysName DEV/4/POWER

Example RECOVERED:
Power 1 recovered.
Recommended
Action
11.9 MPOWERRECOVER
Mnemonic MPOWERRECOVER Severity Level 4
Syslog Message Master power recovered.
Variable Fields
Explanation The master power state changes from failed or absent to OK
Trigger Action Insert the master power into its slot
%Feb 11 16:30:09:156 2007 SysName DEV/4/MPOWER

Example RECOVERED:
Master power recovered.
Recommended
Action
11.10 SPOWERRECOVER
Mnemonic SPOWERRECOVER Severity Level 4
Syslog Message Slave power recovered.
Variable Fields
Explanation The slave power state changes from failed or absent to OK
Trigger Action Insert the slave power into its slot.
%Feb 11 16:30:09:156 2007 SysName DEV/4/SPOWER

Example RECOVERED:
Slave power recovered.
Recommended
Action

11.11 POWERFAIL
Mnemonic POWERFAIL Severity Level 4
Syslog Message Power [INTEGER] failed.
Variable Fields $1: The power ID
Explanation The power state changes to failed
Trigger Action The power has something wrong
%Feb 11 16:30:09:156 2007 SysName DEV/4/POWER FAILED:

Example
Power 1 failed.
Recommended
Action
11.12 POWERABSENT
Mnemonic POWERABSENT Severity Level 5
Syslog Message Power [INTEGER] is absent.
Variable Fields $1: The power id
Explanation The power has been removed
Trigger Action Remove the power
%Feb 11 16:30:09:156 2007 SysName DEV/4/POWER ABSENT:

Example
Power 1 is absent.
Recommended
Action
11.13 FANRECOVER
Mnemonic FANRECOVER Severity Level 4

Syslog Message Fan [INTEGER] recovered.
Variable Fields $1: The fan ID
Explanation The fan state changes from failed or absent to OK
Trigger Action Insert the fan into its slot and wait.
%Feb 11 16:30:09:172 2007 SysName DEV/4/FAN RECOVERED:

Example
Fan 1 recovered.
Recommended
Action
11.14 FANFAIL
Mnemonic FANFAIL Severity Level 4
Syslog Message Fan [INTEGER] failed.
Variable Fields $1: The fan ID
Explanation The fan failed to run
Trigger Action The fan has something wrong
%Feb 11 16:30:09:172 2007 SysName DEV/4/FAN FAILED:

Example
Fan 1 failed.
Recommended
Action
11.15 FANABSENT
Mnemonic FANABSENT Severity Level 4
Syslog Message Fan [INTEGER] is absent.
Variable Fields $1: The fan id
Explanation The fan has been removed
Trigger Action Remove the fan
%Feb 11 16:30:09:172 2007 SysName DEV/4/FAN ABSENT:

Example
Fan 1 is absent.
Recommended
Action
11.16 TEMPOK
Mnemonic TEMPOK Severity Level 4
Board temperature changes to normal on Frame [INTEGER] Slot

Syslog Message
[INTEGER], type is [INTEGER]
$1: The frame ID
Variable Fields $2: The slot ID
Explanation The temperature state changes to normal
The board’s temperature changes to the range between up and low

Trigger Action
limit
%Feb 11 16:30:09:172 2007 SysName DEV/4/BOARD TEMP

NORMAL:
Example
Board temperature changes to normal on Frame 0 Slot 1, type is
LS81VP4C.
Recommended
Action
11.17 TEMPLOW
Mnemonic TEMPLOW Severity Level 4
Board temperature is too low on Frame [INTEGER] Slot

Syslog Message
[INTEGER], type is [INTEGER].
$1: The frame id
Variable Fields $2: The slot id.
Explanation The temperature state changes to LOW
Trigger Action The board’s temperature changes to the range under the low limit

TOOLOW:
Example
Board temperature is too low on Frame 0 Slot 1, type is
LS81VP4C.
Recommended
Action
11.18 TEMPUP
Mnemonic TEMPUP Severity Level 4

Board temperature is too high on Frame [INTEGER] Slot

Syslog Message
$1: The frame ID
Explanation The temperature state changes to UP
Trigger Action The board’s temperature changes to the range over the up limit

TOOHIGH:
Example
Board temperature is too high on Frame 0 Slot 1, type is
LS81VP4C.
Recommended
Action
11.19 RPSNORMAL
Mnemonic RPSNORMAL Severity Level 4
Syslog Message RPS [INTEGER] is Normal
Variable Fields $1: The RPS ID
Explanation The RPS’s state changes to normal
Trigger Action Insert a RPS into its slot
%Feb 11 16:30:09:172 2007 SysName DEV/4/RPS NORMAL:

Example
RPS 1 is normal.
Recommended
Action
11.20 RPSABSENT
Mnemonic RPSABSENT Severity Level 4

Syslog Message RPS [INTEGER] is Absent
Variable Fields $1: The RPS ID
Explanation The RPS is removed.
Trigger Action Remove a RPS to its slot
%Feb 11 16:30:09:210 2007 SysName DEV/4/RPS ABSENT:

Example
RPS 1 is absent.
Recommended
Action
11.21 CFINSERT
Mnemonic CFINSERT Severity Level 4
Compact Flash Card is inserted in Frame [INTEGER] Slot

Syslog Message
[INTEGER] Compact Flash Slot [INTEGER].
$1: The frame ID
Variable Fields $2: The slot ID
$3: The flash slot ID
Explanation A flash card is inserted into its slot
Trigger Action Insert a flash card into its slot
%Feb 11 16:30:09:210 2007 SysName DEV/4/CFCARD

INSERTED:
Example
Compact Flash Card is inserted in Frame 0 Slot 1 Compact Flash
Slot 1.
Recommended
Action
11.22 CFREMOVE
Mnemonic CFREMOVE Severity Level 4

Compact Flash Card is removed from Frame [INTEGER] Slot

Syslog Message
[INTEGER] Compact Flash Slot [INTEGER].
$1: The frame id
Variable Fields $2: The slot id.
$3: The flash slot id.
Explanation An flash card is removed from its slot
Trigger Action Insert a flash card into its slot
%Feb 11 16:30:09:210 2007 SysName DEV/4/CFCARD

REMOVED:
Example
Compact Flash Card is removed from Frame 0 Slot 1 Compact
Flash Slot 1.
Recommended
Action
11.23 SYSTEMREBOOT
Mnemonic SYSTEMREBOOT Severity Level 4
Syslog Message System is rebooted now.
Variable Fields None
Explanation System is rebooting by some reason
Trigger Action System is abnormal or rebooted by user.
%Feb 11 16:30:09:210 2007 SysName DEV/4/SYSTEM REBOOT:

Example
System is rebooting now.
Recommended
Action
11.24 BOARDREBOOT
Mnemonic BOARDREBOOT Severity Level 4

Syslog Message Board is rebooted on Frame [INTEGER] Slot [INTEGER].
$1: The frame id

Variable Fields
$2: The slot id
Explanation Board is rebooting by some reason.
Trigger Action Board is abnormal or rebooted by user.
%Feb 11 16:30:09:210 2007 SysName DEV/4/BOARD REBOOT:

Example
Board is rebooting on Frame 0 Slot 1.
Recommended
Action
11.25 SUBCARDREBOOT
Mnemonic SUBCARDREBOOT Severity Level 4
SubCard is rebooted on Frame [INTEGER] Slot [INTEGER] SubSlot

Syslog Message
[INTEGER].
$1: The frame id
Variable Fields $2: The slot id
$3: The subslot id
Explanation SubCard is rebooting by some reason.
Trigger Action SubCard is abnormal or rebooted by user

Example REBOOT:
SubCard is rebooting on Frame 0 Slot 1 SubSlot 1.
Recommended
Action
11.26 CURRENTNORMAL
Mnemonic CURRENTNORMAL Severity Level 4

Board current changes to normal on Frame [INTEGER] Slot

Syslog Message
$1: The frame id
Explanation Current of the board changes to normal.
Trigger Action Current between the upper limit and lower limit.
%Feb 11 16:30:09:226 2007 SysName DEV/4/BOARD CURRENT

NORMAL:
Example
Board current changes to normal on Frame 0 Slot 1, type is
LS81VP4C.
Recommended
Action
11.27 CURRENTSMALL
Mnemonic CURRENTSMALL Severity Level 4
Board current is too small on Frame [INTEGER] Slot [INTEGER],

Syslog Message
type is [STRING].
$1: The frame id
Explanation Current of the board is too small.
Trigger Action Current below the lower limit.

Example TOOSMALL:
Board current is too small on Frame 0 Slot 1, type is LS81VP4C.
Recommended
Action
11.28 CURRENTBIG
Mnemonic CURRENTBIG Severity Level 5

Board current is too big on Frame [INTEGER] Slot [INTEGER], type

Syslog Message
is [STRING].
$1: The frame id
Explanation Current of the board is too big.
Trigger Action Current above the upper limit.

Example TOOBIG:
Board current is too big on Frame 0 Slot 1, type is LS81VP4C.
Recommended
Action
11.29 VOLTNORMAL
Mnemonic VOLTNORMAL Severity Level 4
Board voltage changes to normal on Frame [INTEGER] Slot

Syslog Message
$1: The frame id
Explanation Voltage of the board changes to normal.
Trigger Action Voltage between the upper limit and lower limit.
%Feb 11 16:30:09:226 2007 SysName DEV/4/BOARD VOLTAGE

NORMAL:
Example
Board voltage changes to normal on Frame 0 Slot 1, type is
LS81VP4C.
Recommended
Action
11.30 VOLTLOW
Mnemonic VOLTLOW Severity Level 4

Board voltage is too low on Frame [INTEGER] Slot [INTEGER],

Syslog Message
type is [STRING].
$1: The frame id
Explanation Voltage of the board is too low.
Trigger Action Voltage below the lower limit.

Example TOOLOW:
Board voltage is too low on Frame 0 Slot 1, type is LS81VP4C.
Recommended
Action
11.31 VOLTHIGH
Mnemonic VOLTHIGH Severity Level 4
Board voltage is too high on frame [INTEGER] Slot [INTEGER],

Syslog Message
type is [STRING].
$1: The frame id
Explanation Voltage of the board is too high.
Trigger Action Voltage above the upper limit.

Example TOOHIGH:
Board voltage is too high on Frame 0 Slot 1, type is LS81VP4C.
Recommended
Action
11.32 NOENOUGHMEM
Mnemonic NOENOUGHMEM Severity Level 4

Syslog Message IO Board [INTEGER] has not enough memory to load file.
Explanation The board has not enough memory to load file.
Trigger Action There is not enough memory for the board loading file.
%Feb 11 16:30:09:241 2007 SysName DEV/4/IO BOARD

Example NOMEMORY:
IO Board 1 has not enough memory to load file.
Recommended
Action
11.33 SAMEREQUEST
Mnemonic SAMEREQUEST Severity Level 4
Syslog Message IO Board [INTEGER] has a same request already, please try later.
Explanation As the board has a same request already, user should try later.
Trigger Action The board has a same request already.
%Feb 11 16:30:09:241 2007 SysName DEV/4/REPEATED

Example REQUEST:
IO Board 1 has a same request already, please try later.
Recommended
Action
11.34 ABORTLOAD
Mnemonic ABORTLOAD Severity Level 4

Syslog Message The loading message of IO Board [INTEGER] timed out, abort load.
The loading message of the board timed out, and system abort the
Explanation
load.
Trigger Action The loading message timed out.
%Feb 11 16:30:09:241 2007 SysName DEV/4/LOADING TIME

Example OUT:
The loading message of IO Board 1 timed out, abort load.
Recommended
Action
11.35 REQUESTINVALID
Mnemonic REQUESTINVALID Severity Level 4
The loading request of IO Board [INTEGER] is invalid, please check

Syslog Message
the bootrom version.
The loading request of the board is invalid, user should check the
Explanation
bootrom version.
Trigger Action The loading request is invalid
%Feb 11 16:30:09:241 2007 SysName DEV/4/REQUEST

ILLEGAL:
Example
The loading request of IO Board 1 is invalid, please check the
bootrom version.
Recommended
Action
11.36 LOADFAIL
Mnemonic LOADFAIL Severity Level 4

Syslog Message Board failed to load file in Frame [INTEGER] IO board [INTEGER].
$1: The frame id

Variable Fields
$2: The slot id
Explanation The board failed to load file.
Trigger Action The board failed to load file.
%Feb 11 16:30:09:241 2007 SysName DEV/4/BOARD LOAD

Example FAILED:
Board failed to load file in Frame 0 IO board 1.
Recommended
Action
11.37 LOADFINISH
Mnemonic LOADFINISH Severity Level 4
Board has finished loading file in Frame [INTEGER] Slot

Syslog Message
[INTEGER]
$1: The frame id

Variable Fields
$2: The slot id
Explanation The board has finished loading file.
Trigger Action The board has finished loading file.
%Feb 11 16:30:09:257 2007 SysName DEV/4/LOAD FINISHED:

Example
Board has finished loading file on Frame 0 Slot 0.
Recommended
Action
11.38 READFAIL
Mnemonic READFAIL Severity Level 4

Syslog Message Driver failed to read file.
Variable Fields
Explanation Driver failed to read file.
Trigger Action Driver failed to read file.
%Feb 11 16:30:09:257 2007 SysName DEV/4/READ FILE FAILED:

Example
Driver failed to read file.
Recommended
Action
11.39 STARTSELF
Mnemonic STARTSELF Severity Level 4
Syslog Message IO Board [INTEGER] starts from self file system.
Explanation The board starts from self file system.
Trigger Action The board starts from self file system.
%Feb 11 16:30:09:257 2007 SysName DEV/4/BOARD START

Example FROM SELF SYSTEM:
IO Board 1 starts from self file system.
Recommended
Action
11.40 CANNOTOPEN
Mnemonic CANNOTOPEN Severity Level 4
Syslog Message Cannot open the file, IO board [INTEGER] will request load again!
Explanation As cannot open the file, the board will request load again.
Trigger Action Cannot open the file.
%Feb 11 16:30:09:265 2007 SysName DEV/4/OPEN FILE FAILED:

Example
Cannot open the file, IO board 1 will request load again!
Recommended
Action

11.41 MANYRESENT
Mnemonic MANYRESENT Severity Level 4
Too many resent frames, IO board [INTEGER] will request load

Syslog Message
again.
As there are too many resent frames, the board will request load
Explanation
again.
Trigger Action Too many resent frames
%Feb 11 16:30:09:265 2007 SysName DEV/4/TOO MANY

Example RESEND:
Too many resent frames, IO board 0 will request load again.
Recommended
Action
11.42 MANYINVALID
Mnemonic MANYINVALID Severity Level 4
Too many invalid frames, IO board [INTEGER] will request load

Syslog Message
again.
As the are too many invalid frames, the board will request load
Explanation
again.
Trigger Action Too many invalid frames.
%Feb 11 16:30:09:265 2007 SysName DEV/4/TOO MANY

Example INVALID:
Too many invalid frames, IO board 1 will request load again.
Recommended
Action
11.43 CHECKSUMERR
Mnemonic CHECKSUMERR Severity Level 4

Syslog Message Checksum error, IO board [INTEGER] will request load again.
Explanation As checksum is error, the board will request load again.
Trigger Action Checksum is error.
%Feb 11 16:30:09:281 2007 SysName DEV/4/CHECKSUM

Example ERROR:
Checksum error, IO board 1 will request load again.
Recommended
Action
12 DHCP Messages
This section contains the entire system log messages related to DHCP.
12.1 DHCPC_LOCAL_SERVER
Mnemonic DHCPC_LOCAL_SERVER Severity Level 3
Local DHCP server information(detect by server):SERVER IP =

Syslog Message [IPADDR]; Source client information: interface = [STRING], type =
[STRING], CHardAddr = [STRING]
$1: The IP address of detected DHCP server.
$2: The name of DHCP client interface from which the DHCP
packets are received.
Variable Fields
$3: The type of the received DHCP packet.
$4: The hardware address of DHCP client included in the received

DHCP packet.
Explanation A new DHCP server is detected.
Receive a DHCP packet in which the IP adrress in siaddr field is

Trigger Action
different from that detected before.
%Jan 1 01:37:58 2003 SysName

DHCPC/3/DHCPC_LOCAL_SERVER:
Example Local DHCP server information(detect by server):SERVER IP =
11.0.0.1; Source client information: interface = Vlan-interface1, type
= DHCPACK, CHardAddr = 0000-5e00-4704
Recommended
Action
12.2 DHCPC_FSM_TO_HALT

Mnemonic DHCPC_FSM_TO_HALT Severity Level 3
IP address request failed on interface [STRING] because an IP

Syslog Message
address on the same network segment is being used on the device
$1: The name of DHCP client interface from which the DHCP
Variable Fields
Explanation Detect the same network segment IP address on the device.
An IP address on the same network segment is being used on the

Trigger Action
device.
%Jan 1 01:37:58 2003 SysName

DHCPC/3/DHCPC_FSM_TO_HALT:
Example IP address request failed on interface Vlan-interface1 because an
IP address on the same network segment is being used on the
device.
Recommended
Action
12.3 DHCPC_BOOTP_ALLOC_FAIL
Mnemonic DHCPC_BOOTP_ALLOC_FAIL Severity Level 4
Syslog Message Allocated IP has been used by another host!
Variable Fields
Explanation The allocated IP can not use by the local host .
Trigger Action The local host requests IP By BOOTP.
%Jan 1 01:37:58 2003 SysName

Example DHCPC/4/DHCPC_BOOTP_ALLOC_FAIL:
Allocated IP has been used by another host!
Recommended
Action
13 DHCPR Messages
This section contains the entire system log messages related to DHCPR.
13.1 DHCPR_DETECT_SERVER
Mnemonic DHCPR_DETECT_SERVER Severity Level 4
DHCP Relay information:DHCP Relay interface = [STRING],Server

Syslog Message
IP (detected by DHCP Relay) = [IPADDR]

$1: The name of interface.

Variable Fields
$2: The IP address of interface
DHCP Relay information:DHCP Relay interface =

Explanation
Ethernet0/1/0,Server IP (detected by DHCP Relay) = 1.1.1.1
Trigger Action There is a fake DHCP Server
%2007/2/16 17:07:31:290 SysName

DHCPR/4/DHCPR_DETECT_SERVER: DHCP Relay
Example
information:DHCP Relay interface = Ethernet0/1/0,Server IP
(detected by DHCP Relay) = 1.1.1.1
Recommended
Action
14 DHCPS Messages
This section contains the entire system log messages related to DHCPS.
14.1 DHCPS_LOCAL_SERVER
Mnemonic DHCPS_LOCAL_SERVER Severity Level 4
Local DHCP server information: Server IP (detected by DHCP

server) = [IPADDR], DHCP server interface = [STRING]
Syslog Message
Source client information: DHCP message type = [STRING], DHCP
client hardware address = [STRING]"
$1: The IP address of detected DHCP server.
$2: The name of DHCP server interface from which the DHCP
Variable Fields
$3: The type of the received DHCP packet.
$4: The hardware address of DHCP client included in the received

DHCP packet.
Explanation A new DHCP server is detected.
Receive a DHCP packet in which the IP adrress in siaddr field is

Trigger Action
different from that detected before.
%Oct 12 19:35:27:453 2005 SysName

DHCPS/4/DHCPS_LOCAL_SERVER:
Example Local DHCP server information: Server IP (detected by DHCP

server) = 11.0.0.1, DHCP server interface = Vlan-interface11
Source client information: DHCP message type = DHCPRELEASE,
DHCP client hardware address = 0000-5e00-4704
Recommended
Action

15 DHCPSNOOP Messages
This section contains the entire system log messages related to DHCPSNOO.
15.1 dhcpsnoop_log
Mnemonic dhcpsnoop_log Severity Level 3
DHCP Snooping: The configuration is not supported on interface

Syslog Message
[STRING]!
Variable Fields $1: The name of interface.
Explanation The configuration is not supported on the interface
Trigger Action Driver does not support DHCP Snooping configuration.
%2007/2/16 17:07:31:290 SysName DHCPSNOO/3/

Example dhcpsnoop_log: DHCP Snooping: The configuration is not
supported on interface Ethernet0/1/0!
Recommended
Action
15.2 dhcpsnoop_log
Syslog Message DHCP Snooping: Configuration conflicts on interface [STRING]!
Explanation Configuration conflicts on the interface.
Trigger Action Configuration conflicts.

Example dhcpsnoop_log : DHCP Snooping: Configuration conflicts on
interface Ethernet0/1/0!
Recommended
Action
15.3 dhcpsnoop_log
DHCP Snooping: No enough resource for new rules on interface

Syslog Message
[STRING]!
Explanation No enough resource for new rules on the interface.

Trigger Action There is no enough resource for new rules on the interface.

Example dhcpsnoop_log : DHCP Snooping: No enough resource for new
rules on interface Ethernet0/1/0!
Recommended
Action
15.4 dhcpsnoop_log
Syslog Message DHCP Snooping: Too many instances on interface [STRING]!
Explanation There are too many instances on interface
Trigger Action There are too many instances on interface

Example dhcpsnoop_log : DHCP Snooping: Too many instances on interface
Ethernet0/1/0!
Recommended
Action
15.5 dhcpsnoop_log
Syslog Message DHCP Snooping: Unknown result on interface [STRING]!
Explanation There is an unknown result on interface
Trigger Action There is an unknown result on interface

Example dhcpsnoop_log : DHCP Snooping: Unknown result on interface
Ethernet0/1/0!
Recommended
Action
16 DLDP Messages
This section contains the entire system log messages related to DLDP.

16.1 AuthenticationFailed
Mnemonic AuthenticationFailed Severity Level 2
Packet authentication isn't passed because of the unmatched

Syslog Message
[STRING].
Variable Fields $1: The packet field.
Explanation DLDP packet authentication isn't passed.
Trigger Action DLDP packet authentication isn't passed.
%Feb 26 05:36:20:876 2007 SysName DLDP/3/

AuthenticationFailed:
Example
Packet authentication isn't passed because of the unmatched
INTERVAL.
Recommended
Action
16.2 UnidirectionalAuto
Mnemonic UnidirectionalAuto Severity Level 2
DLDP detects a unidirectional link in port [STRING]. The

transceiver has malfunction in TX direction or the misconnected link
Syslog Message
between local device and neighbour. The shutdown mode is AUTO.
DLDP shuts down the port.
Variable Fields $1: The port name.
DLDP detects a unidirectional link and shuts down the port

Explanation
automatically.
DLDP detects a unidirectional link and the shutdown mode is

Trigger Action
AUTO.
%Feb 26 05:36:20:876 2007 SysName DLDP/3/ UnidirectionalAuto:
DLDP detects a unidirectional link in port GigabitEthernet1/3. The

Example transceiver has malfunction in TX direction or the misconnected link
between local device and neighbour. The shutdown mode is AUTO.
DLDP shuts down the port.
Recommended
Check the unidirectional link.
Action
16.3 UnidirectionalManual
Mnemonic UnidirectionalManual Severity Level 2

DLDP detects a unidirectional link in port [STRING]. The transceiver

has malfunction in TX direction or the misconnected link between
Syslog Message
local device and neighbour. The shutdown mode is MANUAL. The
port needs to be shut down by the user.
DLDP detects a unidirectional link and suggests that the port should
Explanation
be shutdown.
DLDP detects a unidirectional link and the shutdown mode is

Trigger Action
MANUAL.
%Feb 26 05:36:20:876 2007 SysName DLDP/3/

UnidirectionalManual:
Example DLDP detects a unidirectional link in port GigabitEthernet1/3. The

transceiver has malfunction in TX direction or the misconnected link
between local device and neighbour. The shutdown mode is
MANUAL. The port needs to be shut down by the user.
Recommended
Shutdown the port and check the unidirectional link.
Action
16.4 UnidirectionalAutoEnhance
Mnemonic UnidirectionalAutoEnhance Severity Level 2
In the enhance mode port [STRING] can not detect its aged out
neighbor. The transceiver has malfunction in TX direction or the
Syslog Message
misconnected link between local device and neighbour. The
shutdown mode is AUTO. DLDP shuts down the port.
DLDP In the enhance mode detects a unidirectional link and shuts

Explanation
down the port automatically.
DLDP In the enhance mode detects a unidirectional link and the

Trigger Action
shutdown mode is AUTO.
%Feb 26 05:36:20:876 2007 SysName DLDP/3/
UnidirectionalAutoEnhance:
Example In the enhance mode port GigabitEthernet1/3 can not detect its
aged out neighbor. The transceiver has malfunction in TX direction
or the misconnected link between local device and neighbour. The
shutdown mode is AUTO. DLDP shuts down the port.
Recommended
Check the unidirectional link.
Action
16.5 UnidirectionalManualEnhance
Mnemonic UnidirectionalManualEnhance Severity Level 2

In the enhance mode port [STRING] can not detect its aged out
neighbor. The transceiver has malfunction in TX direction or the
Syslog Message misconnected link between local device and neighbour. The
shutdown mode is MANUAL. The port needs to be shut down by the
user.
DLDP In the enhance mode detects a unidirectional link and

Explanation
suggests that the port should be shutdown.
DLDP In the enhance mode detects a unidirectional link and the

Trigger Action
shutdown mode is MANUAL.
%Feb 26 05:36:20:876 2007 SysName DLDP/3/
UnidirectionalManualEnhance:
Example In the enhance mode port GigabitEthernet1/3 can not detect its
aged out neighbor. The transceiver has malfunction in TX direction
or the misconnected link between local device and neighbour. The
shutdown mode is MANUAL. The port needs to be shut down by the
user.
Recommended
Shutdown the port and check the unidirectional link.
Action
17 DPURPF Messages
This section contains the entire system log messages related to DPURPF.
17.1 DPURPF
Mnemonic ATCKDF Severity Level 4
atckType([ULONG])=([ULONG])[STRING];rcvIfName ([ULONG])=[STRING] ;srcIPAddr([U

Syslog
[STRING];srcMacAddr([ULONG])=[STRING] ;destIPAddr([ULONG])=[STRING];destMacAddr([U
Message
[STRING];[STRING]([ULONG])=[ULONG];atckTime_cn([ULONG])=[STRING]

$1: Firewall Syslog Num
$3: Firewall Syslog Type
$5: Interface Name
$7: IP Source Address
$9: Mac Source Address

Variable Fields
$11: IP Destination Address
$13: Mac Destination Address
$14: Firewall Syslog Type
$16: Attack Speed
$18: Attack Time
Explanation The device is attacked by IP-spoofing.
Trigger Action IP-spoofing packets are received.
%Jan 14 18:55:27:728 2008 SysName DPURPF/4/ATCKDF :Slot=3;atckType(1016)=(0

ng;rcvIfName(1023)=GigabitEthernet3/0/0;srcIPAddr(1017)=3.3.3.3;
Example
srcMacAddr(1021)=;destIPAddr(1019)=2.2.2.2;
destMacAddr(1022)=;atckSpeed(1047)=0;atckTime_cn(1048 )=20080114185528
Recommended
Please check IP source address of the packets received by the device.
Action
18 ETHOAM Messages
This section contains the entire system log messages related to ETHOAM.
18.1 OAMENABLE
Mnemonicm OAMENABLE Severity Level 2
Syslog Message Port [string] starts running OAM now.
Variable Fields $1: The name of port.
Explanation A port has run OAM protocol successfully.

Trigger Action Enable OAM protocol on a port
%Feb 20 17:18:31:345 2007 SysName

Example ETHOAM/2/OAMENABLE:Slot=2;
Port GigabitEthernet2/1/6 starts running OAM now.
Recommended
Action
18.2 OAMDISABLE
Mnemonic OAMDISABLE Severity Level 2
Syslog Message Port [string] stops running OAM now.
Explanation A port has stopped running OAM protocol successfully.
Trigger Action Disable OAM protocol on a port
%Feb 20 17:26:08:514 2007 SysName

Example ETHOAM/2/OAMDISABLE:Slot=2;
Port GigabitEthernet2/1/6 stops running OAM now.
Recommended
Action
18.3 OAMDISOK
Mnemonic OAMDISOK Severity Level 2
Syslog Message Port [string] OAM discovery completed, connection succeed.
Explanation OAM connection has been established between two ports.
Both ports of a link must enable OAM protocol and at least one of
Trigger Action
them runs in active mode.
%Feb 20 17:35:23:719 2007 SysName ETHOAM/2/OAMDISOK:

Example
Port Ethernet6/4/0 OAM discovery completed, connection succeed.
Recommended
Action
18.4 OAMDISFAIL

Mnemonic OAMDISFAIL Severity Level 2
Syslog Message port [string] OAM connection failed, for remote unsatisfied.
OAM connection is not established between two ports successfully

Explanation because remote OAM entity is unsatisfied with the information of local
OAM entity.
Trigger Action Establish OAM connection.
%Feb 20 18:04:07:890 2007 SysName

Example ETHOAM/2/OAMDISTIMEOUT:port Ethernet6/4/0 OAM connection
failed, for remote unsatisfied.
Recommended
Action
18.5 OAMDISTIMEOUT
Mnemonic OAMDISTIMEOUT Severity Level 2
Syslog Message port [string] OAM connection failed, for discovery timed out.
When a OAM entity can’t receive OAMPDU in five seconds, OAM

Explanation
connection will be disconnected.
Trigger Action Partner OAM entity disable OAM protocol
%Feb 20 18:04:07:890 2007 SysName

Example ETHOAM/2/OAMDISTIMEOUT:port Ethernet6/4/0 OAM connection
failed, for discovery timed out.
Recommended
Action
18.6 OAMPORTDOWN
Mnemonic OAMPORTDOWN Severity Level 2
Syslog Message port [string] OAM connection failed, for port link Down.
When a link status changes from up to down, OAM connection will be

Explanation
disconnected.
Trigger Action Link down
%Feb 20 18:34:17:169 2007 SysName

Example ETHOAM/2/OAMPORTDOWN:port Ethernet6/4/0 OAM connection
failed, for port link Down.

Recommended
Action
18.7 EnUnderControl
Mnemonic EnUnderControl Severity Level 2
OAM Port [string]:Local OAM as controlled DTE enters remote

Syslog Message
loopback.
After partner OAM entity inputs command “oam loopback”, local OAM
Explanation
entity enters remote loopback as a controlled DTE
Trigger Action Partner OAM entity inputs command “oam loopback”
%Feb 20 18:39:45:767 2007 SysName

Example ETHOAM/2/EnUnderControl:OAM Port Ethernet6/4/0:Local OAM as
controlled DTE enters remote loopback.
Recommended
Action
18.8 DisUnderControl
Mnemonic DisUnderControl Severity Level 2
OAM Port [string]:Local OAM quits remote loopback as a controlled

Syslog Message
DTE.
After partner OAM entity inputs command “undo oam loopback”, local
Explanation
OAM entity quits remote loopback as a controlled DTE
Trigger Action Partner OAM entity inputs command “undo OAM loopback”
%Feb 20 18:41:01:819 2007 SysName

Example ETHOAM/2/DisUnderControl:OAM Port Ethernet6/4/0:Local OAM quits
remote loopback as a controlled DTE.
Recommended
Action
18.9 EnControl
Mnemonic EnControl Severity Level 2
OAM Port [string]:Local OAM enters remote loopback as a controlling

Syslog Message
DTE.

After local OAM entity inputs command “oam loopback”, local OAM
Explanation
entity enters remote loopback as a controlling DTE
Trigger Action Local OAM entity inputs command “oam loopback”
%Feb 20 18:43:04:969 2007 SysName ETHOAM/2/EnControl:

Example OAM Port Ethernet6/4/0:Local OAM enters remote loopback as a
controlling DTE.
Recommended
Action
18.10 DisControl
Mnemonic DisControl Severity Level 2
OAM Port [string]:Local OAM quits remote loopback as a controlling

Syslog Message
DTE.
After local OAM entity inputs command “undo OAM loopback”, local
Explanation
OAM entity quits remote Loopback as a controlling DTE
Trigger Action local OAM entity inputs command “undo oam loopback”
%Feb 20 18:43:04:969 2007 SysName ETHOAM/2/EnControl:

Example OAM Port Ethernet6/4/0:Local OAM enters remote loopback as a
controlling DTE.
Recommended
Action
18.11 LoopbackExit
Mnemonic LoopbackExit Severity Level 2
Syslog Message OAM Port [string]:Remote loopback exits.
When link status is down or OAM entity as controlled DTE is disabled,

Explanation
local OAM entity quits remote loopback.
Trigger Action link status is down or OAM entity as controlled DTE is disable
%Feb 20 18:45:32:246 2007 SysName ETHOAM/2/LoopbackExit:

Example
OAM Port Ethernet6/4/0:Remote loopback exits.
Recommended
Action

18.12 StateError
Mnemonic StateError Severity Level 2
Syslog Message OAM Port [string]: Remote loopback exits due to error status.
When the port is in loopback mode, Multiplexer or Parser status of

Explanation
OAM entity is wrong.
Trigger Action Multiplexer or parser status of OAM entity is wrong.
%Feb 20 19:09:11:164 2007 SysName ETHOAM/2/ StateError:OAM

Example
port Ethernet6/4/0: Remote loopback exits due to error status.
Recommended It is best for OAM entity to stop OAM protocol at once and running
Action OAM protocol over again.
18.13 LINKFAULT
Mnemonic LINKFAULT Severity Level 2
Syslog Message \r\nLocal link fault event has occured on [string]
Variable Fields $1: A Port name of local device
Explanation A link-fault event occurred on local port
Trigger Action Disconnect the receiver fiber of a local port
%Oct 23 13:44:28:254 2007 SysName

Example ETHOAM/2/LINFAULT:Slot=3;
Local link fault event has occured on GigabitEthernet3/1/19
Recommended
Reconnect the receiver fiber of local port
Action
18.14 REMOTELINKFAULT

Mnemonic REMOTELINKFAULT Severity Level 2
Syslog Message \r\nRemote link fault event has occured on [string].
Variable Fields $1: A Port name of remote device
Explanation A link-fault event occurred on remote port
Trigger Action Disconnect the receiver fiber of a remote port
%Oct 23 13:44:28:254 2007 SysName

Example ETHOAM/2/REMOTELINFAULT:Slot=3;
Remote link fault event has occured on GigabitEthernet3/1/19
Recommended
Reconnect the receiver fiber of remote port
Action
18.15 LOCALERRFRAME
Mnemonic LOCALERRFRAME Severity Level 2
Syslog Message \r\nLocal errored frame event has occured on [string].
Variable Fields $1:A Port name
Explanation A local port occurred a errored frame event
This event is generated if the errored frame count is equal to or

Trigger Action
greater than the specified threshold for a period.
%Oct 23 13:44:28:254 2007 SysName ETHOAM/2/

Example LOCALERRFRAME:Slot=3;
Local errored frame event has occured on GigabitEthernet3/1/19
Recommended
Check the link
Action
18.16 REMOTEERRFRAME

Mnemonic REMOTEERRFRAME Severity Level 2
Syslog Message \r\nRemote errored frame event has occured on [string].
Explanation A remote port occurred a errored frame event
This event is generated if the errored frame count on the remote

Trigger Action
port is equal to or greater than the specified threshold for a period.

Example REMOTEERRFRAME:Slot=3;
Remote errored frame event has occured on GigabitEthernet3/1/19
Recommended
Check the link
Action
18.17 LOCALERRFRAMEPERIOD
Mnemonic LOCALERRFRAMEPERIOD Severity Level 2
Syslog Message \r\nLocal errored frame period event has occured on [string].
Explanation A local port occurred a errored frame period event

Trigger Action greater than the specified threshold for a period. The period is
specified by a number of received frames.

LOCALERRFRAMEPERIOD:Slot=3;
Example
Local errored frame period event has occured on
GigabitEthernet3/1/19
Recommended
Check the link
Action
18.18 REMOTEERRFRAMEPERIOD

Mnemonic REMOTEERRFRAMEPERIOD Severity Level 2
Syslog Message \r\nRemote errored frame period event has occured on [string].
This event is generated if the errored frame count on the remote port
Trigger Action is equal to or greater than the specified threshold for a period.
The period is specified by a number of received frames.

REMOTEERRFRAMEPERIOD:Slot=3;
Example
Remote errored frame period event has occured on
Recommended
Check the link
Action
18.19 LOCALERRFRAMESEC
Mnemonic LOCALERRFRAMESEC Severity Level 2
\r\nLocal error frame seconds summary event has occured on

Syslog Message
[string].
Explanation A local port occurred a errored frame seconds summary event
This event is generated if the number of errored frame seconds is

Trigger Action
equal to or greater than the specified threshold for a period.

LOCALERRFRAMESEC:Slot=3;
Example
Local error frame seconds summary event has occured on
Recommended
Check the link
Action
18.20 REMOTEERRFRAMESEC

Mnemonic REMOTEERRFRAMESEC Severity Level 2
\r\nRemote error frame seconds summary event has occured on

Syslog Message
[string]..
This event is generated if the number of errored frame seconds on

Trigger Action the remote port is equal to or greater than the specified threshold for
a period.

REMOTEERRFRAMESEC:Slot=3;
Example
Remote error frame seconds summary event has occured on
Recommended
Check the link
Action
18.21 REMOTEDYINGGASP
Mnemonic REMOTEDYINGGASP Severity Level 2
Syslog Message \r\nRemote dying gasp event has occured on [string]..
Explanation A remote port occurred a dying gasp event
Trigger Action An unrecoverable remote failure condition has occurred

Example REMOTEDYINGGASP:Slot=3;
Remote dying gasp event has occured on GigabitEthernet3/1/19
Recommended
Don’t use this link until it returns to a normal condition
Action
18.22 REMOTECRITICALE

Mnemonic REMOTECRITICALE Severity Level 2
Syslog Message \r\nRemote critical event has occured on [string]
Explanation A remote port occurred a critical event
Trigger Action An unspecified critical event has occurred.

Example REMOTECRITICALE:Slot=3;
Remote critical event has occured on GigabitEthernet3/1/19
Recommended
Action
19 FIBV4 Messages
This section contains the entire system log messages related to FIBV4.
19.1 log_fib
Mnemonic log_fib Severity Level 5
Syslog Message FIB synchro state: [string] [string]
$1: The time when the operation occurs

Variable Fields
$2: The operation which is running
Explanation The operation described is running. This log is used in main board.
Trigger Action When aging or synchronizing, the action will be done.
%Feb 21 16:13:24:891 2007 SysName FIBV4/5/log_fib:

Example
FIB synchro state: 2007/02/21 16:13:24 Begin to fresh walking
Recommended
Action
19.2 log_fib
Syslog Message FIB synchro state: Board [ULONG]: [string] [string]
$1: Board number
Variable Fields $2: The time when the operation occurs
$3: which operation is running

Explanation The operation described is running. This log is used in io board.
%Feb 21 16:13:24:891 2007 SysName FIBV4/5/log_fib:

Example FIB synchro state: Board 3 2007/02/21 16:13:24 Begin to fresh
walking
Recommended
Action
19.3 log_fib
$1: IP address
Variable Fields
$2: VrfIndex
The driver returns conflict flag when the host route entry has already
Explanation
been added.
If the driver returns conflict flag when the host route entry has
Trigger Action
already been added, the log is displayed.
Aug 16 14:13:11:386 2007 SysName FIBV4/4/log_fib:Slot=1;Route

Example
conflict found, IP:40.1.31.10, VrfIndex:0
Recommended
Modify configuration.
Action
19.4 Log_fib_MemShortage
Mnemonic Log_fib_MemShortage Severity Level 4
Syslog Message Receive memory shortage notification!
Explanation It is lack of the memory.
Trigger Action Too many memory has been allocated.
%Feb 6 08:55:26:262 2007 SysName

Example FIBV4/4/log_fib_MemShortage:Slot=3;Receive memory shortage
message!
Recommended
Please check the configuration and the situation.
Action

19.5 Log_fib_MemResume
Mnemonic Log_fib_MemResume Severity Level 4
Syslog Message Receive memory shortage resume notification!
Explanation The memory that can be used returns to be normal.
Trigger Action Some module has freed some memory.
%Feb 6 08:55:26:262 2007 SysName

Example FIBV4/4/log_fib_MemResume:Slot=3;Receive memory shortage
resume notification!
Recommended
Action
20 FILTER Messages
This section contains the entire system log messages related to FILTER
20.1 IPFILTER
Mnemonic IPFILTER Severity Level 4
Variable Fields string
Explanation Firewall filter packets
Trigger Action Firewall filter packets
%Feb 20 20:23:40:94 2007 SysName

FILTER/5/IPFILTER:Ethernet0/1/1 InBound List 3000 deny udp
Example
(10.153.94.138 138)->(10.153.95.255 138) 1 Packet from interface
Ethernet0/1/1
Recommended
Action
21 FTP Server Messages

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

21.1 USERIN
Mnemonic USERIN Severity Level 4
Syslog Message User [string]([ipaddr]) login succeeded
$1: The user name of FTP client.

Variable Fields
$2: The source IP address of FTP client
Explanation A FTP user has logged in successfully.
FTP server accepts a FTP client request, and user name and
Trigger Action
password are correct.
%Feb 21 14:27:41:922 2007 SysName FTPD/4/USERIN:User

Example
ftpuser(192.168.0.99) login succeeded
Recommended
Action
21.2 USEROUT
Mnemonic USEROUT Severity Level 4
Syslog Message User [string]([ipaddr]) logged out

Variable Fields
Explanation A FTP user has logged out.
Trigger Action The user which logged in logs out from FTP server
%Feb 21 14:30:24:875 2007 SysName FTPD/4/USEROUT:User

Example
ftpuser(192.168.0.99) logged out
Recommended
Action
21.3 USERIN
Mnemonic USERIN Severity Level 4
Syslog Message User [string]([ipaddr]) login failed

Variable Fields
Explanation A FTP user has failed to logged in.
FTP Server accepts a FTP client request, and user name or

Trigger Action
password is not correct

%Feb 21 14:32:30:672 2007 SysName FTPD/4/USERIN:User

Example
ftpuser(192.168.0.99) login failed.
Recommended
Action
21.4 USERFAIL
Mnemonic USERFAIL Severity Level 4
Syslog Message User [string]([ipaddr]) transfer failed

Variable Fields
Explanation The FTP client fails to put file to server
Some errors occurr during FTP client put file to server or the space
Trigger Action
of disk of FTP server is not enough.
%Feb 21 14:40:31:203 2007 SysName FTPD/4/USERFAIL:User

Example
ftpuser(192.168.0.99) transfer failed
Recommended
Action
21.5 REQUEST
Mnemonic REQUEST Severity Level 5
Syslog Message User [string]([ipaddr]) request: [string]
Variable Fields $2: The source IP address of FTP client
$3: The request command of FTP client to Server
Explanation The FTP client sends request command to the server.
Turn on the FTP server debugging, the FTP user input some
Trigger Action
commands.
%Feb 21 14:41:31:203 2007 SysName FTPD/5/REQUEST:User

Example
ftpuser(192.168.0.99) request: PORT 192,168,0,99,18,162
Recommended
Action
21.6 SENDDATA

Mnemonic SENDDATA Severity Level 5
Syslog Message FTP server send [ULONG] bytes to client [string]([ipaddr])
$1: The file length which is transferred.
Variable Fields $2: The user name of FTP client.
Explanation The FTP client gets file successfully.
Turn on the ftp server debugging, the FTP user gets file
Trigger Action
successfully.
%Feb 21 14:42:31:203 2007 SysName FTPD/5/ SENDDATA:FTP

Example
server send 16045 bytes to client ftpuser(192.168.0.99)
Recommended
Action
21.7 RECVDATA
Mnemonic RECVDATA Severity Level 5
Syslog Message FTP server receive [ULONG] bytes from client [string]([ipaddr])
$1: The file length which is transferred.
Variable Fields $2: The user name of FTP client.
Explanation The FTP client puts file successfully.
Switch on the FTP server debugging, the FTP user put file
Trigger Action
successfully.
%Feb 21 14:43:31:203 2007 SysName FTPD/5/RECVDATA:FTP

Example
server receive 16045 bytes from client ftpuser(192.168.0.99)
Recommended
Action
21.8 RUNERROR
Mnemonic RUNERROR Severity Level 4
Syslog Message FTP server run error [ULONG] ([string])
$1: The error code

Variable Fields
$2: the error infomation
Explanation Failed to configure socket or get task ID or create queue.
Trigger Action Socket error or fail to apply for system’s source

%Feb 21 15:25:05:187 2007 SysName FTPD/4/RUNERROR: FTP

Example
server run error -11 get task id fail.
Recommended
Action
22 GARP Messages
This section contains the entire system log messages related to GARP
22.1 Wrong Protocol Id

Mnemonic Wrong Protocol Id Severity Level 3
Syslog Message The protocol Id is not 0x0001
Variable Fields
Explanation The protocol ID in received garp packet is not 0x0001.
Trigger Action Receive a garp packet in which the protocol Id field is not 0x0001.
%Aug 19 14:58:54:92186 2007 SysName GARP/3/Wrong Protocol

Example
Id:The protocol Id is not 0x0001
Recommended
Action
22.2 Wrong message

Mnemonic Wrong message Severity Level 3
Syslog Message The attribute type of message is wrong
Variable Fields
Explanation The attribute type in received garp packet is wrong.
Trigger Action Receive a gvrp packet in which attribute type field is wrong.
%Aug 19 15:02:07:169 2007 SysName GARP/3/Wrong

Example
message:The attribute type of message is wrong
Recommended
Action
22.3 Wrong Msg Length

Mnemonic Wrong Msg Length Severity Level 3
Syslog Message The attribute length of message is wrong
Variable Fields
Rceiving a gvrp packet in which the length field in message is not

Explanation
correct
When received a gvrp packet in which the length field in message

Trigger Action
is not correct.
%Aug 19 15:03:47:20582 2007 SysName GARP/3/Wrong Msg

Example
Length:The attribute length of message is wrong
Recommended
Action
22.4 Wrong attribute

Mnemonic Wrong attribute Severity Level 3
Syslog Message The attribute is unknown
Variable Fields
Explanation Receive a gvrp packet but in which the attribute field is unknown.
Trigger Action When receive a gvrp packet in which the attribute field is unknown.
%Aug 19 14:51:06:15935 2007 SysName GARP/3/Wrong

Example
attribute:The attribute is unknown
Recommended
Action
22.5 Malloc Failed

Mnemonic Malloc Failed Severity Level 3
Syslog Message Failed to allocate memory
Variable Fields
Explanation Allocate memory failed.
Trigger Action When Allocate memory failed.
%Aug 19 14:51:06:15935 2007 SysName GARP/3/Wrong Allocate

Example
memory failed.
Recommended
Action

23 HA Messages
This section contains the entire system log messages related to HA.
23.1 LOG
#1 Slave's waiting ha time becomes to [ULONG] seconds!
Variable Fields $1: Slave's waiting HA time.
Explanation Slave's waiting HA time has been changed.
Trigger Action Slave's waiting HA time has been changed.
%Feb 25 01:04:56:662 2007 SysName HA/4/LOG: Slave's waiting

Example
ha time becomes to 60 seconds!
Recommended
Action
#2 HA get board status error! DEVM return error!
Variable Fields
Explanation HA get board status error! DEVM return error!
Trigger Action HA get board status error! DEVM return error!
%Feb 25 01:04:56:662 2007 SysName HA/4/LOG: HA get board

Example
status error! DEVM return error!
Recommended
Action
#3 Slave mpu receive master mpu reload message!
Variable Fields
Explanation Reboot the slave board.
Trigger Action Reboot the slave board.
%Feb 10 09:09:39:378 2007 SysName HA/4/LOG:Slot=1;

Example
Slave mpu receive master mpu reload message!
Recommended
Action
#4 HA fails to register slot event callback functions.
Variable Fields

Explanation HA fails to register slot event callback functions.
Trigger Action HA fails to register slot event callback functions.
%Feb 25 01:04:56:662 2007 SysName HA/4/LOG: HA fails to

Example
register slot event callback functions.
Recommended
Action
Version of Master Board doesn't match with version of Slave Board

#5
Restart the Slave Board and download a new image
Variable Fields
The version of COMWARE between master board and slave board

Explanation
doesn't match.
Trigger Action Update the image file
%Feb 7 15:53:54:182 2007 SysName HA/4/LOG:
Version of Master Board doesn't match with version of Slave

Example
Board
Recommended
Action
#6 Batch backup started
Variable Fields
Explanation Batch backup started.
Trigger Action Batch backup started.
%Feb 25 01:04:56:662 2007 SysName HA/4/LOG: Batch backup

Example
started
Recommended
Action
#7 HA could not allocate memory.
Variable Fields
Explanation HA could not apply for memory.
Trigger Action HA applies for memory.
%Feb 25 01:04:56:662 2007 SysName HA/4/LOG: HA could not

Example
allocate memory.
Recommended
Action
#8 Slave board in slot [ULONG] is not ready, reboot...

Variable Fields $1:Slot number
Explanation Slave board in slot $1 is not ready, and the device will reboot.
Trigger Action Slave board in slot $1 is not ready, and the device will reboot.
%Feb 25 01:04:56:662 2007 SysName HA/4/LOG: Slave board in

Example
slot 1is not ready, reboot...
Recommended
Action
#9 Slave board in slot %d changes to master
Variable Fields
Explanation Slave board changes to master.
Trigger Action Slave board changes to master.
%Feb 25 01:04:56:662 2007 SysName HA/4/LOG: Slave board in

Example
slot 1 changes to master
Recommended
Action
#10 Batch backup is finished
Variable Fields
Explanation Batch backup is finished.
Trigger Action Batch backup is finished.
%Feb 25 01:04:56:662 2007 SysName HA/4/LOG: Batch backup is

Example
finished
Recommended
Action
24 HABP Messages
24.1 HABPSTART
Mnemonic HABPSTART Severity Level 3
Syslog Message The device starts running HABP now.
Variable Fields
Explanation The HABP is enable.
Trigger Action When The HABP status is from disable to enable.
%Apr 27 16:29:45:320 2000 SysName HABP/3/HABPSTART:The

Example
device starts running HABP now.

Recommended
Action
24.2 HABPSTOP
Mnemonic HABPSTOP Severity Level 3
Syslog Message The device stops running HABP now.
Variable Fields
Explanation The HABP is disable.
Trigger Action When The HABP status is from enable to disable.
%Apr 27 16:27:35:90 2000 SysName HABP/3/HABPSTOP:The

Example
device stops running HABP now.
Recommended
Action
25 HTTPD Messages
This section contains the entire system log messages related to HTTPD .
25.1 Log
Mnemonic Log Severity Level 4
Variable Fields $1: the output info
Explanation This is a common print info and output the parameter info.
Trigger Action Disable HTTPD function or enable HTTPD function.
%Feb 21 16:02:45:375 2007 SysName HTTPD/4/Log:Close HTTP

server.
Example
%Feb 21 16:03:14:641 2007 SysName HTTPD/4/Log:Start HTTP
server.
Recommended
Action
26 HTTPS Messages
This section contains the entire system log messages related to HTTPS.

26.1 LOG
Close https Socket error.
Closing HTTPS server succeeded.

Trigger Action
Initiation https Socket error.
Starting HTTPS server succeeded.
%Feb 21 15:31:30:47 2007 SysName HTTPS/4/LOG:

Example
Close https Socket error.
Recommended
Action
27 HWCM Messages
This section contains the entire system log messages related to HWCM.
27.1 EXIT
Mnemonic EXIT Severity Level 4
Syslog Message exit from configure mode
Variable Fields
Explanation Exit from configure mode.
Trigger Action An user exits from configure mode.
%Feb 26 05:36:20:876 2007 SysName HWCM/4/EXIT: exit from

Example
configure mode
Recommended
Action
27.2 TRAPLOG
Mnemonic TRAPLOG Severity Level 4

\r\n\t [oid] configure changed: \r\n\t

Syslog Message EventIndex=[INTEGER],CommandSource=[INTEGER],ConfigSource
=[INTEGER],ConfigDestination=[INTEGER]
$1: OID
$2: Event index
Variable Fields $3: Command source
$4: Configuration source
$5: Configuration destination
Explanation Configuration is changed
Trigger Action Change configuration
%Feb 26 06:10:25:780 2007 SysName HWCM/4/TRAPLOG:
1.3.6.1.4.1.2011.10.2.4.2.1 configure changed:

Example
EventIndex=13,CommandSource=1,ConfigSource=3,ConfigDestinati
on=2
Recommended
Action
27.3 CCOPY
Mnemonic CCOPY Severity Level 4
\r\n\t configuration copy: OptType=[INTEGER],

Syslog Message OptTime=[TIMETICK], OptState=[INTEGER],
OptEndTime=[TIMETICK]
$1: Operation type

Variable Fields
$2: Date and time
Explanation Copy configuration
Trigger Action Copy configuration
%Feb 26 06:38:24:733 2007 SysName HWCM/4/CCOPY:

Example configuration copy: OptType=6, OptTime=12, OptState=2,
OptEndTime=10682324
Recommended
Action
28 IGMP Messages
28.1 INFO

Mnemonic INFO Severity Level 4
Variable Fields $1: The error information.
After the equipment has done some unexpected operations, it

Explanation
shows what is wrong with the equipment.
Trigger Action Do some unexpected operations.
%Jan 1 01:37:58 2003 SysName IGMP/5/INFO: Unable to leave

Example
224.0.0.22 group on eth1/1/1(%1.1.1.1). (G09862)
Recommended
Action
28.2 ERR
Mnemonic ERR Severity Level 3
Variable Fields $1: The warning information.

Explanation
Example Not used yet.
Recommended
Action
29 IFNET Messages
This section contains the entire system log messages related to IFNET.
29.1 PORTTAG
Mnemonic PORTTAG Severity Level 4
Syslog Message Failed to get a porttag
Explanation Failed to allocate a porttag.
Trigger Action Create an interface.
%Jan 16 14:28:58:424 2007 SysName IFNET/4/PORTTAG:

Example
Failed to get a porttag

Recommended Clear all porttags allocated. Input “reset unused porttag” under the
Action user view.
29.2 UPDOWN
Mnemonic UPDOWN Severity Level 4
Syslog Message Line protocol on the interface [STRING] is [STRING]

Variable Fields
$2: The status of line protocol.
Explanation The status of line protocol has been changed on an interface.
Trigger Action Change the status of line protocol on an interface.
%Jan 1 01:27:05 2003 SysName IFNET/4/UPDOWN: Line

Example
protocol on the interface Ethernet6/4/1 is UP
Recommended
Action
29.3 UPDOWN
Mnemonic UPDOWN Severity Level 4
Syslog Message Protocol [STRING] on the interface [STRING] is [STRING]
$1: The name of protocol.
$3: The status of protocol.
Explanation The status of protocol has been changed on an interface.
Trigger Action Change the status of protocol on an interface.
%Jan 1 01:27:05 2003 SysName IFNET/4/UPDOWN:Protocol IPX

Example
on the interface Ethernet6/4/1 is UP
Recommended
Action
29.4 LINK UPDOWN

Mnemonic LINK UPDOWN Severity Level 4
Syslog Message [STRING]: link status is [STRING]


Variable Fields
$2: The link status
Explanation The link status has been changed on an interface.
Trigger Action Change the link status on an interface.
%Jan 1 01:27:05 2003 SysName IFNET/4/LINK

Example
UPDOWN:Ethernet6/4/1:link status is UP
Recommended
Action
29.5 FLUX EXCEED UPPER LIMIT

FLUX EXCEED UPPER
Mnemonic Severity Level 1
LIMIT
STORM-CONSTRAIN:[STRING] is in [STRING] status,[STRING]

Syslog Message
flux exceeds its upper threshold:[INTEGER]
$2: The status of the port

Variable Fields
$3: The type of packets
$4: The upper threshold
This log message is generated when any type of the flux exceeds
Explanation its upper limit on a port without configuring “storm-constrain control
[block | shutdown ]”.
This log message is generated when any type of the flux exceeds
Trigger Action its upper limit on a port without configuring “storm-constrain control
%Feb 26 05:36:20:876 2007 SysName IFNET/1/FLUX EXCEED

UPPER LIMIT:
Example
STORM-CONSTRAIN:Ethernet0/1 is in normal status,broadcast
flux exceeds its upper threshold : 1000
Recommended Check network topology or configure “storm-constrain control [block

Action | shutdown ]” on the port.
29.6 FLUX BELLOW LOWER LIMIT

FLUX BELLOW LOWER
LIMIT
STORM-CONSTRAIN:[STRING] is in [STRING] status,[STRING]

Syslog Message
flux falls bellow its lower threshold : [INTEGER]


Variable Fields
$4: The lower threshold
This log message is generated when a flux which used to overflow

Explanation its upper limit, falls below its lower limit on a port without
configuring “storm-constrain control [block | shutdown ]”.

Trigger Action its upper limit, falls below its lower limit on a port without
configuring “storm-constrain control [block | shutdown ]”.
%Feb 26 05:36:20:876 2007 SysName IFNET/1/FLUX BELLOW

LOWER LIMIT:
Example
STORM-CONSTRAIN:Ethernet0/1 is in normal status,broadcast
flux falls bellow its lower threshold : 100
Recommended configure “strom-constrain control [block | shutdown ]” on the port if

Action necessary
29.7 PORT STATUS TURNS TO CONTROLLED

PORT STATUS TURNS TO
CONTROLLED
[STRING]:turns into controlled status, port status:[STRING], packet

Syslog Message
type:[STRING], upper threshold:[INTEGER]

Variable Fields
$4: The upper threshold
This trap message is generated when any type of the flux exceeds
Explanation its upper limit on a port with configuring “storm-constrain control
This trap message is generated when any type of the flux exceeds
Trigger Action its upper limit on a port with configuring “storm-constrain control
%Feb 26 05:36:20:876 2007 SysName IFNET/1/PORT STATUS

TURNS TO CONTROLLED:
Example
Ethernet0/1:turns into controlled status, port status:controlled,
packet type:broadcast, upper threshold:1000
Check network topology of the port and configure “undo shutdown”

Recommended or “undo storm-constrain { all | broadcast | multicast | unicast }”
Action
on this port configured “storm-constrain control [block | shutdown ]”.

29.8 PORT STATUS RETURNS TO NORMAL

PORT STATUS RETURNS
TO NORMAL
[STRING]:return to normal status, port status:[STRING], packet

Syslog Message
type:[STRING], lower threshold:[INTEGER]

Variable Fields
$4: The lower threshold

Explanation its upper limit, falls below its lower limit on a port with configuring
“storm-constrain control [block | shutdown ]”.

Trigger Action its upper limit, falls below its lower limit on a port with configuring
“storm-constrain control [block | shutdown ]”.
%Feb 26 05:36:20:876 2007 SysName IFNET/1/PORT STATUS

RETURNS TO NORMAL:
Example
Ethernet0/1:return to normal status, port status:normal, packet
type:multicast, lower threshold:100
Recommended Configure “undo storm-constrain control [block | shutdown]” on the

Action port if necessary.
30 IKE Messages
This section contains the entire system log messages related to IKE.
30.1 DROP
Mnemonic DROP Severity Level 4
IKE packet dropped: (src addr: [IPADDR], dst addr: [IPADDR]) with
Syslog Message I_Cookie [STRING] and R_Cookie [STRING], because of '
[STRING] ' from payload [STRING].
$1: The source IP address of this packet.
$2: The destination IP address of this packet.
$3: The cookie of initiator.

Variable Fields
$4: The cookie of responder.
$5: The reason of dropping this packet.
$6: The error payload of IKE packet.
Explanation An IKE packet is dropped.

Trigger Action An IKE packet is dropped.
%Jan 5 16:13:13:120 2007 SysName IKE/4/DROP:
Example IKE packet dropped: (src addr: 1.0.0.2, dst addr: 1.0.0.1) with
I_Cookie 25f2c03c1ef46a5c and R_Cookie 7ae81223de52ab5d,
because of ' No IPSec policy found ' from payload PROPOSAL.
Recommended
Action
31 IPDBG Messages
31.1 IP Info
Mnemonic IP Info Severity Level 3
Syslog Message TaskId=[ULONG], TaskName=[string], BoardId=[ULONG]\r\n[string]
$1: Task ID
$2: Task name

Variable Fields
$3: Board ID
$4: Information
Explanation The information about operation on IP address
Failed to operate on IP address, such as adding ip address or

Trigger Action
synchronizing address to IO board.
%Aug 23 16:16:39:812 2007 SysName IPDBG/3/IP Info:
TaskId=1, TaskName=IP , BoardId=1

Example IP address warning:
IPC failed to synchronize ifindex 2222 ip address configuration to

slot 2
Recommended
Action
32 IPCIM Messages
This section contains the entire system log messages related to IP CIM.
32.1 ipcim_log
Mnemonic Ipcim_log Severity Level 4

"\r\n Setting user-bind rule failed.\
\r\n The user-bind information:\
Syslog Message \r\n Soure Module: [STRING] IP address: [IPADDR] \
\r\n MAC: [STRING] Interface: [STRING]\
\r\n Vlan ID: [ULONG] VPN ID: [ULONG]\r\n
$1: The Source Module name.
$2: The IP address of user-bind rule.
$3: The MAC of user-bind rule

Variable Fields
$4: The interface of user-bind rule.
$5: The Vlan ID of user-bind rule.
$6: The VPN ID of user-bind rule
Explanation Setting user-bind rule failed
Trigger Action Setting user-bind rule failed
%Feb 26 05:36:20:876 2007 SysName IP CIM/5/ Ipcim_log:
Setting user-bind rule failed.
The user-bind information:

Example
Soure Module: DHCP Snooping IP address: 1.1.1.1
MAC: 1-1-1 Interface: Ethernet 1/0/1
Vlan ID: 1 VPN ID: 0
Recommended
Action
33 IPsec Messages
This section contains the entire system log messages related to IPsec.
33.1 DROP
Mnemonic DROP Severity Level 4
IPsec Packet discarded--Src IP:[IPADDR] ||Dest IP:[IPADDR] ||

Syslog Message
SPI:[ULONG] || SN:[ULONG] || Cause:[STRING]
$1: The source IP address of this packet.
$2: The destination IP address of this packet.
Variable Fields $3: The security parameter index.
$4: Sequence number for anti-replay.
$5: The reason of dropping this packet.

Explanation An IPsec packet is dropped.
Trigger Action An IPsec packet is dropped.
%Jan 1 01:27:05 2007 SysName ipsec/4/DROP: IPsec Packet

Example discarded--Src IP:1.1.1.1 ||Dest IP:2.2.2.2 || SPI:12345 || SN:1 ||
Cause: can't find SA
Recommended
Action
34 IPV6FIBC Messages
This section contains the entire system log messages related to IPV6FIBC.
34.1 Log_fibc_MemShortage
Mnemonic Log_fibc_MemShortage Severity Level 4
Syslog Message Receive memory shortage notification!
Explanation It is lack of the memory that can be allocated.
Trigger Action Too many memory has been allocated.
%Feb608:55:26:1332007 SysName
Example IPV6FIBC/4/Log_fibc_MemShortage:Slot=3;
Receive memory shortage notification!
Recommended
Please check the configuration and the situation.
Action
34.2 Log_fibc_MemResume
Mnemonic Log_fibc_MemResume Severity Level 4
Syslog Message Receive memory shortage resume notification!
Explanation The memory that can be used returns to be normal.
Trigger Action Some module has freed some memory.
%Feb600:25:23:4952007 SysName
Example IPV6FIBC/4/Log_fibc_MemResume:Slot=3;
Receive memory shortage resume notification!
Recommended
Action

35 IPV6PP Messages
This section contains the entire system log messages related to IPV6PP.
35.1 ReassError
Mnemonic ReassError Severity Level 3
Syslog Message The number of IPv6 queues of reassemble is MAX!
Variable Fields
The number of IPv6 queues of reassemble is more than permission

Explanation
(400 queues).
Input 1st packet of a series and create a new reassembling queue,

Trigger Action
but the total number of queue exceeds the limit.
%Aug 23 16:16:39:812 2007 SysName IPV6PP/3/ReassError:The

Example
number of IPv6 queues of reassemble is MAX!
Recommended
Action
35.2 QueueFull
Mnemonic QueueFull Severity Level 3
Syslog Message The IPv6 queue of reassemble is full!
Variable Fields
The number of the assembling packet of a series is more than

Explanation
permission (1000 packets).
Trigger Action Receiving the 1001st assembling packet of a series.
%Feb 20 12:37:58 2007 SysName IPv6PP/3/QueueFull: The IPv6

Example
queue of reassemble is full!
Recommended
Action
36 ISIS Messages
This section contains the entire system log messages related to ISIS.
36.1 ADJLOG
Mnemonic ADJLOG Severity Level 5
Variable Fields $1: ADJ CHANGE information
Explanation The ISIS event is generated when ISIS ADJ change.
Trigger Action ISIS ADJ change.
%Apr 7 09:45:27:750 2007 SysName ISIS/5/ADJLOG: ISIS -1-

Example ADJCHANGE: Adjacency To 1000.0000.0000 (eth0/1/0) UP. New
level-2 Adjacency.
Recommended
Action
37 L2TP Messages
This section contains the entire system log messages related to L2TP
37.1 CLVPDN1
Mnemonic CLVPDN1 Severity Level 6
Syslog Message Clear L2TP remote name [string]
Variable Fields $1: remote tunnel name
Explanation L2TP Clear Vpdn Tunnel
Trigger Action User resets L2TP tunnel.
%Feb 20 20:23:40:94 2007 SysName L2TP/6/ CLVPDN1: Clear

Example
L2TP remote name LAC
Recommended
Action
37.2 CLVPDN2
Mnemonic CLVPDN2 Severity Level 6
Syslog Message Clear L2TP local tunnID [ULONG]
Variable Fields $1: local tunnel ID
Explanation Clear L2TP local tunnel.
Trigger Action User resets local L2TP tunnel.
%Feb 20 20:23:40:94 2007 SysName L2TP/6/ CLVPDN2: Clear

Example
L2TP local tunnID 1

Recommended
Action
38 L2V Messages
This section contains the entire system log messages related to L2V.
38.1 LOG
Explanation L2VPN process fialed events
Trigger Action Failed to remove L2vpn encaption on an interface
%Jan 20 17:16:44:59063 2007 Router1 L2V/4/LOG: ! L2VPN

Example
Remove Encap Interface failed
Recommended
Action
Trigger Action Failed to send Bgp reach NLRI message.
%Jan 20 17:16:44:59063 2007 Router1 L2V/4/LOG:! L2VPN BGP

Example
Send Reach NLRI fail
Recommended
Action
Trigger Action Failed to send Bgp un-reach NLRI message.
%Jan 20 17:16:44:59063 2007 Router1 L2V/4/LOG: ! L2VPN BGP

Example
Send UN-Reach NLRI fail
Recommended
Action
Trigger Action Failed to change L2vpn VCs state.
%Jan 20 17:16:44:59063 2007 Router1 L2V/4/LOG:! L2VPN

Example
change VCs state failed
Recommended
Action
Trigger Action Failed to remove TnlMindex from BGPVC.
%Jan 20 17:16:44:59063 2007 Router1 L2V/4/LOG: ! L2VPN

Example
Delete TnlMindex from BGPVC failed
Recommended
Action
Trigger Action Local ce can not communicate with remote ce

%Jan 20 17:16:44:59063 2007 Router1 L2V/4/LOG: ! Local CE 1 in

VPN(Route-Distinguisher 100:1) cannot communicate with remote
Example
CE 2 (PE 10.1.1.1) in VPN(Route-Distinguisher 100:1): outside
range
Recommended
Action
Trigger Action Receive Memory Shortage (or Restore) Notification.
%Mar 3 10:58:10:946 2007 SysName L2V/4/LOG:

Example !L2VPN - Memory Shortage Notification Received : Event = MEM
SHORTAGE
Recommended
Check memory usage rate.
Action
Trigger Action Insufficient memory.

Example
! Command fails: insufficient memory
Recommended
Action
Trigger Action Failed to write a message to queue.

Example
! L2VPN Queue Write Fails
Recommended
Action
Trigger Action Failed to create hash table.

Example
! L2VPN Hash Create Table Fails
Recommended
Action
Trigger Action Failed to create gads array.

Example
! GADS Create Array failure
Recommended
Action
Trigger Action Failed to create timer.

Example
! L2VPN Timer Creates fail
Recommended
Action
Trigger Action Not supported encapsulation type.

Example
! Warning: This encapsulation type currently not supported yet

Recommended
Check encapsulation type.
Action
Trigger Action Remote CEID and Local CEID are same.

Example ! Remote CEID and Local CEID same:Remote LB, CE ID: 2, from
PE: 1.1.1.1, Route-Distinguisher: 100:1
Recommended
Check the configuration of the remote CE ID and local CE ID.
Action
Trigger Action Same remote CE ID when insert RLB into VPN.

Example ! Insert RLB into VPN, same remote CE ID(2) OLD RLB from PE:
1.1.1.1, RD: 100:1 NEW RLB from PE: 2.2.2.2, RD: 100:2
Recommended
Action
Trigger Action VSI receive unsupported ldp vpls mac withdraw message.

Example ! L2VPN VSI: Receive unsupported ldp vpls mac withdraw
message.
Recommended
Action
Trigger Action Remote Site ID and Local Site ID are same.

Example Error: Remote SiteID and Local SiteID same:Remote LB, Site ID:
2, from PE: 1.1.1.1, Route-Distinguisher: 100:1
Recommended
Action
Trigger Action Same remote Site ID when insert RLB into VSI.

Example Error: Insert RLB into VSI, same remote Site ID(2) OLD RLB from
PE: 1.1.1.1, RD: 100:1 NEW RLB from PE: 2.2.2.2, RD: 100:2
Recommended
Action
Trigger Action Failed to inform BGP to send label blocks

Example
! Call BGP to inform label block send complete fail
Recommended
Action
Trigger Action VSI failed to inform BGP to send label blocks

Example
! L2VPN VSI call BGP to inform label block send complete fail

Recommended
Action
Trigger Action Remote CE ID is outside of CE range.

Example ! Cannot communicate with remote CE 2 (PE 1.1.1.1) of
VPN(Route-Distinguisher 100:1): outside range
Recommended
Check the configuration of CE connection.
Action
Trigger Action Remote CE ID is outside of CE range.
Example Error: Local Site Id 1 in VSI(Route-Distinguisher 100:1) cannot

communicate with remote site 10 (PE 2.2.2.2) in VSI(Route-
Distinguisher 100:2): outside range
Recommended
Check the configuration of CE connection.
Action
Trigger Action L2VPN VSI failed to call BGP to delete NLRI.

Example
! L2VPN VSI call BGP to delete NLRI fail
Recommended
Action
39 L3VPN Messages
This section contains the entire system log messages related to L3VPN.
39.1 L3VPNLOG
Mnemonic L3VPNLOG Severity Level 1
Explanation L3VPN process fialed events
Trigger Action CLear Vrf to Sync Master and Slave Data.
%Mar 3 11:58:13:598 2007 SysName L3VPN/1/L3VPNLOG:

Example VpnName = vpn1 is in STALE state, Cleaning this Vpn to sync
Master and Slave Data
Recommended
Action
VPN Interface Change interface index, failed to inform other

Trigger Action
module.


Example VPN Interface Change IFIndex = 0xae3ff10 failed to inform MID =
0x6000000
Recommended
Action
Trigger Action Create VPN instance, but failed to inform other module.

Example
Create VPN-INSTANCE vpn1 failed to inform MID = 0x6000000
Recommended
Action
Trigger Action Delete VPN instance, but failed to inform other module.

Example
Delete VPN-INSTANCE vpn1 failed to inform MID = 0x6000000
Recommended
Action
Trigger Action Associate vpn-instance with interface.

Slot=1;
Example
Failed to associate VPN instance vpn1 with interface Eth1/0/0 due
to no enough resource
Recommended
Action
40 LAGG Messages
This section contains the entire system log messages related to LAGG.
40.1 LAGG_LOG

Mnemonic LAGG_LOG Severity Level 2
Syslog Message Port member %s of aggregation group %s becomes INACTIVE!
$1. port name

Variable Fields
$2. Link aggregation group type and ID
Explanation Status of some port(s) in an aggregation group becomes inactive!
Trigger Action Status of some port(s) in an aggregation group becomes inactive!
%Feb 18 18:57:06:29 2008 mep 7408 LAGG/2/LAGG_LOG:

Example Port member GigabitEthernet2/0/13 of aggregation group BAGG1
becomes INACTIVE!
Recommended
Action
40.2 LAGG_LOG
Mnemonic LAGG_LOG Severity Level 2
Syslog Message Port member %s of aggregation group %s becomes ACTIVE!
$1. port name

Variable Fields
$2. Link aggregation group type and ID
Explanation Status of some port(s) in an aggregation group becomes active!
Trigger Action Status of some port(s) in an aggregation group becomes active!
%Feb 18 18:57:20:29 2008 mep 7408 LAGG/2/LAGG_LOG:

Example Port member GigabitEthernet2/0/13 of aggregation group BAGG1
becomes ACTIVE!
Recommended
Action
41 LDP Messages
This section contains the entire system log messages related to LDP.
41.1 SessionUp
Explanation LDP session up event.

Trigger Action LDP session's state change to up.
%Mar 3 15:35:04:282 2007 SysName LDP/4/SessionUp:

Example
Session(110.3.3.3:0. public Instance)'s state change to Up
Recommended
Action
41.2 SessionDown
Explanation LDP session down event.
Trigger Action LDP session's state change to down.
%Mar 3 15:34:59:250 2007 SysName LDP/4/SessionDown:

Example
Session(110.3.3.3:0. public Instance)'s state change to Down
Recommended
Action
41.3 LDP
Explanation LDP LSP or CRLDP LSP limit reached.
Trigger Action LDP LSP limit reached.
%Apr 25 17:38:35:407 2008 PPP LDP/4/LDP:Maximum LDP LSP

Example
limit reached
Recommended
No action is required.
Action
Trigger Action CRLDP LSP limit reached.
%Apr 25 17:38:35:407 2008 PPP LDP/4/LDP:Maximum CRLDP

Example
LSP limit reached
Recommended
Action
42 LLC2 Messages
The system log messages of this moudle are not supported.
43 LLDP Messages
This section contains the entire system log messages related to LLDP.
43.1 CREREM
Mnemonic CREREM Severity Level 6
Port [STRING] (IfIndex [ULONG]):Created New Neighbour, Chassis

Syslog Message
ID: [STRING]; Port ID: [STRING].
$1: The configured port name.
$2: The configured port ifIndex.

Variable Fields
$3: The neighbour’s chassis id.
$4: The neighbour’s port id.
Explanation The port creates a new neighbour
Trigger Action The port received a LLDP message
%Feb 26 05:36:20:876 2007 SysName CMD/5/ CREREM:

Example con0: Port 1 (IfIndex 587599):Created New Neighbour, Chassis ID:
00-E0-10-6C-C3-E3; Port ID: Ethernet1/3.
Recommended
Action
43.2 DELREM
Mnemonic DELREM Severity Level 6
Port [STRING] (IfIndex [ULONG]): Deleted Neighbour, Chassis ID:

Syslog Message
[STRING]; Port ID: [STRING].
$1: Port name.
$2: Port ifIndex.

Variable Fields
Explanation The port deleted a neighbour
Trigger Action The port received a shutdown message

Example con0: Port 1 (IfIndex 587599): Deleted Neighbour,Chassis ID: 00-
E0-10-6C-C3-E3; Port ID: Ethernet1/3.

Recommended
Action
43.3 AGEOUTREM
Mnemonic AGEOUTREM Severity Level 6
Port [STRING] (IfIndex [ULONG]): Neighbour Aged Out, Chassis

Syslog Message
ID: [STRING]; Port ID: [STRING].
$1: Port name.
$2: Port ifIndex.

Variable Fields
Explanation A neighbour had aged out
Trigger Action The port didn’t received message from the neighbour in time.

Example con0: Port 1 (IfIndex 587599): Neighbour Age Out, Chassis ID: 00-
E0-10-6C-C3-E3; Port ID: Ethernet1/3.
Recommended
Action
43.4 TOOMANGREM
Mnemonic TOOMANGREM Severity Level 6
Port [STRING] (IfIndex [ULONG]):The Num of Neighbors has been

Syslog Message
Larger than [ULONG] in the Port, and Can't Create New Neighbor.
$1: Port name.
Variable Fields $2: Port ifIndex.
$3: The max number of neighbour that a port can maintain.
Explanation The port received too many LLDP message
The port had max neighbours and received another LLDP

Trigger Action
message.

Example con0: Port 1 (IfIndex 587599): The Num of Neighbors has been
Larger than 16 in the Port, and Can't Create New Neighbor
Recommended
Action

43.5 NONTOOMANGREM
Mnemonic NONTOOMANGREM Severity Level 6
Port [STRING] (IfIndex [ULONG]):The Num of Neighbors has been

Syslog Message
Less than [ULONG] in the Port, and Can Create New Neighbor.
$1: Port name.
Variable Fields $2: Port ifIndex.
$3: The max number of neighbour that a port can maintenance.
Explanation The port didn’t receive too many LLDP message
Trigger Action The port didn’t receive more LLDP message.

Example con0: Port 1 (IfIndex 587599): The Num of Neighbors has been
Less than 16 in the Port, and Can Create New Neighbor
Recommended
Action
44 LS Messages
This section contains the entire system log messages related to LS.
44.1 CNAHGEPASSWORD
Mnemonic CNAHGEPASSWORD Severity Level 5
[STRING] changed password for password will age out in [ULONG]

Syslog Message
days\r\n
$1: user name

Variable Fields
$2: the number of day
When user modify the password, record the reason that password
Explanation
will age out after n day
Trigger Action As user modifying password, record the reason
%Jan 1 01:37:58 2003 SysName PWD/5/CNAHGEPASSWORD:

Example
Admin changed password for password will age out in 5 days
Recommended
Action
44.2 CNAHGEPASSWORD

Syslog Message [STRING] changed password for password has aged out
Variable Fields $1: user name.
Explanation
has aged out
%Jan 1 01:37:58 2003 SysName PWD/5/ CNAHGEPASSWORD:

Example
Admin changed password for password has aged out
Recommended
Action
44.3 CNAHGEPASSWORD
Syslog Message [STRING] changed password for the password is too short
Explanation
is too short

Example
Admin changed password for the password is too short
Recommended
Action
44.4 CNAHGEPASSWORD
Syslog Message [STRING] changed password for password composition is invalid
Explanation
composition is invalid

Example
Admin changed password for password composition is invalid
Recommended
Action

44.5 WRITEPASSTOFILE
Mnemonic WRITEPASSTOFILE Severity Level 5
Syslog Message failed to write the password records to file
Variable Fields
Explanation Failed to write password record to file.
Trigger Action Failed to write password record to file.
%Jan 1 01:37:58 2003 SysName PWD/5/WRITEPASSTOFILE:

Example
failed to write the password records to file
Recommended
Action
45 LSPM Messages
This section contains the entire system log messages related to LSPM.
45.1 LSPM
Mnemonic LSPM Severity Level 4
Explanation LSP limit reached.
Trigger Action LDP LSP limit reached.
%Apr 25 17:38:35:391 2008 PPP LSPM/4/LSPM:Maximum LDP

Example
LSP limit reached
Recommended
Action
Trigger Action CRLDP LSP limit reached.
%Apr 25 17:38:35:391 2008 PPP LSPM/4/LSPM:Maximum CRLDP

Example
LSP limit reached
Recommended
Action
Trigger Action RSVP LSP limit reached.
%Apr 25 17:38:35:391 2008 PPP LSPM/4/LSPM:Maximum RSVP

Example
LSP limit reached
Recommended
Action
Trigger Action BGP LSP limit reached.

%Apr 25 17:38:35:407 2008 PPP LSPM/4/LSPM:Maximum BGP

Example
LSP limit reached
Recommended
Action
Trigger Action VPN LSP limit reached.
%Apr 25 17:38:35:407 2008 PPP LSPM/4/LSPM:Maximum VPN

Example
LSP limit reached
Recommended
Action
Trigger Action Static LSP limit reached.
%Apr 25 17:38:35:407 2008 PPP LSPM/4/LSPM:Maximum static

Example
LSP limit reached
Recommended
Action
Trigger Action Static CRLSP limit reached.
%Apr 25 17:38:35:407 2008 PPP LSPM/4/LSPM:Maximum static

Example
CRLSP limit reached
Recommended
Action
Trigger Action BGP IPV6 LSP limit reached.
%Apr 25 17:38:35:407 2008 PPP LSPM/4/LSPM:Maximum BGP

Example
IPV6 LSP limit reached
Recommended
Action
Trigger Action LSP (total) limit reached.
%Apr 25 17:38:35:407 2008 PPP LSPM/4/LSPM:Maximum LSP

Example
limit reached
Recommended
Action
Trigger Action CRLSP (total) limit reached.
%Apr 25 17:38:35:407 2008 PPP LSPM/4/LSPM:Maximum CRLSP

Example
limit reached
Recommended
Action
46 LWPS Messages
This section contains the entire system log messages related to LWPS.
46.1 LOG

Syslog Message Failed to connect to AC for AP [string] [Serial-ID [string]].
$1: The AP name.

Variable Fields
$2: The AP serial id.
Explanation The AP failed to connect to AC.
Trigger Action The AP failed to connect to AC.
%Apr 30 15:27:03:576 2008 SysName LWPS/6/LOG :

Example Failed to connect to AC for AP ap1 [Serial-ID
210235A22W0077000091].
Recommended
Action
46.2 LOG
Syslog Message Failed to connect to AC for AP [Serial-ID [string]].
Variable Fields $1: The AP serial id.
Explanation The AP failed to connect to AC, and the system can’t get AP name.
Trigger Action The AP failed to connect to AC.
%Apr 30 15:27:03:576 2008 SysName LWPS/6/LOG :

Example Failed to connect to AC for AP [Serial-ID
210235A22W0077000091].
Recommended
Action
47 MCS Messages
This section contains the entire system log messages related to MCS.
47.1 LOG
Variable Fields $1: The warning infomation.

Explanation
shows what is wrong with the operation of the equipment.

%Jan 1 01:37:58 2003 SysName MCS/5/LOG: Memory alloc faile.

Example
(G09862)
Recommended
Action
48 MFIB Messages
48.1 LOG
Syslog Message [STRING][STRING]([STRING][STRING])
$1: The warning infomation.
$2: The index of VRF.

Variable Fields
$3: The name of the file the warning is in..
$4: The number of the line in the file the warning comes from.

Explanation
%Jan 1 01:37:58 2003 SysName MFIB/5/LOG: Memory alloc failed.

Example
(G09862)
Recommended
Action
49 MLD Messages
This section contains the entire system log messages related to MLD.
49.1 ERROR
Mnemonic ERROR Severity Level 4
Variable Fields $1: The error infomation.

Explanation
Trigger Action Failed to init MLD task.

%Jun 8 18:25:15:672 2007 Ar2 MLD/4/ERR: Failed to set

Example
ICMP6_FILTER OPTIONS for M LDv2 task (G042273).
Recommended
Action
50 MPLS OAM Messages

This section contains the entire system log messages related to MPLS OAM.
50.1 OAM_LOG_INFO
Mnemonic OAM_LOG_INFO Severity Level 4
Syslog Message LSP (Ingress Lsr Id:[STRING], Tunnel Id:[INT]) [STRING]
$1:Ingress LSR ID
$2: Tunnel ID
$3: Status, including
enter defect state!
quit defect state!
Variable Fields rlsn up!
rlsn down!
start detect!
stop detect!
enter available state!
enter unavailable state!
This log records at the tunnel egress the fact that OAM detects
Explanation
status change.
Trigger Action OAM detects status change.
%May 30 17:14:19:602 2007 SysName MPLS/4/OAM_LOG_INFO:

Example
LSP (Ingress Lsr Id:1.1.1.1, Tunnel Id:2) stop detect!
Recommended
Check the status change reason and perform corresponding action.
Action
50.2 OAM_LOG_INFO
Mnemonic OAM_LOG_INFO Severity Level 4
Syslog Message [STRING] [STRING]

$1: Tunnel name
$2: Status, including
enter defect state!
quit defect state!
rlsn up!
Variable Fields
rlsn down!
start detect!
stop detect!
enter available state!
enter unavailable state!
This log records at the tunnel ingress the fact that OAM detects
Explanation
status change.
Trigger Action OAM detects status change.
%May 30 17:14:19:602 2007 SysName MPLS/4/OAM_LOG_INFO:

Example
Tunnel1 stop detect!
Recommended
Check the status change reason and perform corresponding action.
Action
51 QoS Messages
This section contains the entire system log messages related to QoS
51.1 warning
Mnemonic warning Severity Level 4
Classifier-Behavior [STRING] in Policy [STRING] applied on

Syslog Message interface [STRING] failed.
[STRING]
$1: The Classifier-Behavior name.
$2: The Policy name.

Variable Fields
$3: The Port name.
$4: The Failed reason.
Explanation Error info for applying policy on interface.
Trigger Action The Policy applied on interface.

%Dec 25 16:00:55:401 2007 SysName QOS/4/warning:Slot=3;
Classifier-Behavior b in Policy b applied on interface Ethernet3/1/2

Example
failed.
Reason: No actions in behavior.
Recommended
Action
51.2 warning
Classifier-Behavior [STRING] in Policy [STRING] applied on vlan

Syslog Message [ULONG] failed.
[STRING]
$1: The Classifier-Behavior name.
$2: The Policy name.

Variable Fields
$3: The VLAN number.
$4: The Failed reason.
Explanation Error info for applying policy on VLAN.
Trigger Action The Policy applied on VLAN.
Example Classifier-Behavior d in Policy b applied on vlan 2 failed.
Recommended
Action
51.3 warning
Applying or refreshing QoS policy [STRING] to interface [STRING]

Syslog Message failed.
[STRING]
$1: The policy name.
$3: The failed reason.
Explanation Error info for applying a policy to an interface.

Apply a policy to an interface firstly, or modify the policy which has

Trigger Action
been applied to an interface.
Applying or refreshing QoS policy b to interface Ethernet3/1/2

Example
failed.
Reason: Not supported by hardware.
Recommended
Action
51.4 warning
Applying or refreshing QoS policy [STRING] to VLAN [ULONG]

Syslog Message failed.
[STRING]
Variable Fields $2: The VLAN number.
Explanation Error info for applying a policy to a VLAN.
Apply a policy to a VLAN firstly, or modify the policy which has

Trigger Action
been applied on a VLAN.
Example Applying or refreshing QoS policy b to VLAN 2 failed.
Recommended
Action
51.5 warning
Applying or refreshing QoS policy [STRING] to the control plane of

Syslog Message slot [ULONG] failed.
[STRING]
Variable Fields $2: The slot number.
Explanation Error info for applying a policy to a control plane.

Apply a policy to a control plane firstly, or modify the policy which

Trigger Action
has been applied to a control plane.
Applying or refreshing QoS policy b to the control plane of slot 3

Example
failed.
Recommended
Action
51.6 warning
Applying classifier-behavior [STRING] in policy [STRING] to the

Syslog Message control plane of slot [ULONG] failed.
[STRING]
$1: The classifier-behavior name.

Variable Fields
$3: The slot number.
Explanation Error info for applying a policy to a control plane.
Apply a policy to a control plane firstly, or modify the policy which

Trigger Action
has been applied on a control plane.
Applying classifier-behavior d in policy b on the control plane of slot

Example
3 failed.
Recommended
Action
51.7 NOT ENOUGH BANDWIDTH

Mnemonic NOT ENOUGH BANDWIDTH Severity Level 3
"\r\nPolicy [STRING] requested bandwidth [ULONG](Kbps).

Syslog Message
Available only [ULONG](Kbps) on [STRING]."
$1: The current available bandwidth of the interface.
Variable Fields $2: The needed bandwidth for CBWFQ.
$3: The name of the interface.

The current available bandwidth of the interface is less than the

Explanation
bandwidth of CBWFQ.
Set a max-bandwidth so that the current available bandwidth of the

interface is less than the bandwidth of CBWFQ configured in a
Trigger Action
absolute mode, or configure CBWFQ which bandwidth in absolute
mode is more than the current available bandwidth of the interface
%Oct 15 15:31:19:241 2007 SysName QOS/3/NOT ENOUGH

BANDWIDTH:
Example
Policy d requested bandwidth 10000(Kbps). Available only
80(Kbps) on GigabitEthernet4/0/1.
Recommended
Action
51.8 CBWFQ REMOVED

Mnemonic CBWFQ REMOVED Severity Level 3
Syslog Message "\r\nCBWFQ is removed on [STRING]."
Variable Fields $1: The name of the interface.
Explanation CBWFQ on the interface is removed for some reason.
Set a max-bandwidth or change speed of the interface so that the

Trigger Action
CBWFQ on the interface is removed.
%Oct 15 15:31:19:241 2007 SysName QOS/3/CBWFQ

Example REMOVED:
CBWFQ is removed on GigabitEthernet4/0/1.
Recommended
Action
52 MCDP BRIDGE Messages

This section contains the entire system log messages related to MCDP BRIDGE.
52.1 MACFULL
Mnemonic MACFULL Severity Level 4
Syslog Message MAC table is full.
Variable Fields
Explanation The MAC address table is full.
Trigger Action When the MAC address table is full, this log is dispayed.

%May 30 17:14:19:602 2007 SysName DPBRIDGE/4/MACFULL:

Example
MAC table is full.
Recommended
Action
53 MRM Messages
53.1 MRM
Syslog Message "[STRING][STRING][STRING]([STRING][STRING])"
$1: The Family, IPv4 or IPv6
Variable Fields $3: The warning information.
After the equipment has done some unexpected operations, it shows

Explanation
what is wrong with the operation of the equipment.
%Jan 1 01:37:58 2003 SysName MRM/5/MRM: Memory alloc faile.

Example
(G09862)
Recommended
Action
54 MSDP Messages
54.1 PEER_UP

Mnemonic PEER_UPDOWN Severity Level 4
[STRING]Start a session with the peer [STRING]

Syslog Message
([STRING][STRING])
$2: The address of peer.

Variable Fields
$3: The name of the file the warning is in.

Explanation
%Jan 1 01:37:58 2003 SysName MSDP/5/PEER_UPDOWN: 0

Example
Start a session with the peer 10.2.2.2 .(G09862)
Recommended
Action
54.2 PEER_DOWN
[STRING]Close a session with the peer [STRING]

Syslog Message
([STRING][STRING])

Variable Fields
$4: The number of the line in the file the warning comes from..

Explanation
%Jan 1 01:37:58 2003 SysName MSDP/5/PEER_DOWN: 0 Close

Example
a session with the peer 10.2.2.2 .(G09862)
Recommended
Action
54.3 SA_LIMIT

Mnemonic SA_LIMIT Severity Level 4
[STRING]RP: [STRING], SG Entry: ([STRING], [STRING]),

Syslog Message exceeded peer([STRING])'s SA-cache maximum: [STRING]
([STRING][STRING])
$2: The address of the RP.
$3: The address of the source.
$4: The address of the group.

Variable Fields
$6: The max number of the SA-cache.

Explanation
%Jan 1 01:37:58 2003 SysName MSDP/5/SA_LIMIT: 0 RP:

Example 10.1.1.1, SG Entry: (20.2.2.2, 225.3.3.3), exceeded peer(10.2.2.2)'s
SA-cache maximum: 5 (G09862)
Recommended
Action
54.4 PEER_ACCEPT

[STRING]When accepting a connection from peer [STRING], return

Syslog Message
error code [STRING] ([STRING][STRING])
Variable Fields $3: The error code.

Explanation
%Jan 1 01:37:58 2003 SysName MSDP/5/ PEER_ACCEPT: 0

Example When accepting a connection from peer [10.2.2.2], return error
code 2. (G09862)
Recommended
Action
55 MSTP Messages
This section contains the entire system log messages related to MSTP.
55.1 STPSTART
Mnemonic STPSTART Severity Level 2
Syslog Message STP is now enabled on the device.
Variable Fields
Explanation STP is enabled
Trigger Action STP is globally enabled.
%Aug 15 16:47:39:414 2007 SysName MSTP/2/STPSTART:STP is

Example
now enabled on the device.
Recommended
Action
55.2 STPSTOP
Mnemonic STPSTOP Severity Level 2

Syslog Message STP is now disabled on the device.
Variable Fields
Explanation STP is disabled.
Trigger Action STP is globally disabled.
%Aug 15 16:47:36:880 2007 SysName MSTP/2/STPSTOP:STP is

Example now disabled on
the device.
Recommended
Action
55.3 ROOT
Mnemonic ROOT Severity Level 2
Syslog Message ROOT: We are not the root switch of the instance [ULONG]!,
Variable Fields $ 1 Instance Identify
Explanation The switch is not the root of one instance.
Trigger Action Switch receives high priority BPDU
%Apr 27 20:29:22:920 2000 SysName MSTP/3/ROOT:We are not

Example
the root switch of the instance 0!
Recommended Ensure the configuration is correct and there is no STP packet

Action attack.
55.4 IVBPDU
Mnemonic IVBPDU Severity Level 2
Syslog Message IVBPDU:BPDU-Protection port [STRING] received BPDU packet!
Variable Fields $ 1 Interface name
Explanation BPDU-Protection port received BPDU packet.
Trigger Action BPDU-Protection port received BPDU packet.
%Apr 27 20:42:39:330 2000 SysName MSTP/3/IVBPDU:BPDU-

Example
Protection port Ethernet1/0/4 received BPDU packet!
Recommended Ensure the network connection and configuration are correct. The
Action remote port should not send STP packets.
55.5 RGSUP
Mnemonic RGSUP Severity Level 2
RGSUP: Instance[ULONG]'s ROOT-Protection port [STRING]

Syslog Message
received superior message!
$ 1 Instance Identify
Variable Fields
$ 2 Interface name
Explanation ROOT-Protection port received superior message.
Trigger Action ROOT-Protection port received superior message.
%Apr 27 11:45:32:283 2000 com5 MSTP/3/RGSUP:Instance0's

Example
ROOT-Protection port Ethernet1/0/2 received superior message!
Recommended Ensure the configuration is correct and there is no STP packet

Action attack.
55.6 LGEXP
Mnemonic LGEXP Severity Level 2
LGEXP:Instance[ULONG]'s LOOP-Protection port [STRING] did

Syslog Message
not receive message!
$ 1 Instance Identify
Variable Fields
$ 2 Port name
Explanation LOOP-Protection port did not receive message.
Trigger Action LOOP-Protection port did not receive message.
%Apr 27 20:51:20:84 2000 SysName MSTP/3/

Example LGEXP:Instance[ULONG]'s LOOP-Protection port [STRING] did
not receive message!
Recommended Ensure the lines are normal (optical fiber are bidirectional through),
Action and the uplink STP port is not disabled.
55.7 BPDUFORMATERROR
Mnemonic BPDUFORMATERROR Severity Level 2
BPDUFORMATERROR:Port [STRING] received different format of

Syslog Message BPDU packets continually! Shut it down in order to prevent
broadcast.
Variable Fields $1 Interface name
Explanation Port received different format of BPDU packets continually
Trigger Action Receive different format BPDU packets.

%Apr 27 20:51:35:84 2000 SysName MSTP/3/

BPDUFORMATERROR:Port Ethernet 1/0/1 received different
Example
format of BPDU packets continually! Shut it down in order to
prevent broadcast.
Recommended Configure the format of the BPDU packets sent from the connected
Action device the same as the local port, and restore the port to up state.
55.8 BPDUFORMATCONFIGERROR
Mnemonic BPDUFORMATCONFIGERROR Severity Level 2
BPDUFORMATCONFIGERROR: Port [STRING] received different

Syslog Message format of BPDU packets! Please change your BPDU Format
configuration.
Explanation Configure conflict.
Trigger Action Received different format BPDU packets
%Apr 27 20:51:40:84 2000 SysName MSTP/3/

BPDUFORMATCONFIGERROR:Port Ethernet 1/0/1 received
Example
different format of BPDU packets ! Please change your BPDU
Format configuration.
Recommended Configure the format of the BPDU packets sent from the connected
Action device the same as the local port.
55.9 BPDUFORMATCONFIGRIGHT
Mnemonic BPDUFORMATCONFIGRIGHT Severity Level 2
BPDUFORMATCONFIGRIGHT: Port [STRING] received the same

Syslog Message
format of BPDU packets.
Explanation Received the same format BPDU packets
After receiving BPDU packets of different formats, receive BPDU

Trigger Action
packets of the same format then.
%Apr 27 20:51:50:84 2000 SysName MSTP/3/

Example BPDUFORMATCONFIGRIGHT: Port Ethernet 1/0/1 received the
same format of BPDU packets.
Recommended
Action
55.10 BPDURCVDEXPIRY
Mnemonic BPDURCVDEXPIRY Severity Level 3
Instance [ULONG]'s Port [STRING] received no message within the

Syslog Message
rcvdInfoWhile interval. Information of the port was aged out.
$1:The instance-id
Variable Fields
$2:The port name
When non-Designated Port received no message within the

Explanation
rcvdInfoWhile interval, Information of the port became no use.
Non-Designated Port received no message within the rcvdInfoWhile

Trigger Action
interval.
(1) concentrated:
%Oct 9 09:08:47:517 2007 Sysname MSTP/2/BPDURCVD
EXPIRY: Instance 0's Port GigabitEthernet0/4/1 received no

message within the rcvdInfoWhile interval. Information of the port
was aged out.
Example
(2) Distributed:
%Oct 9 08:09:37:512 2007 Sysname MSTP/2/BPDURCVD
EXPIRY: Slot=5; Instance 29's Port GigabitEthernet5/1/6 received

no message within the rcvdInfoWhile interval. Information of the
port was aged out.
Recommended
Prolong the hello packet timeout time.
Action
56 NATPT Messages
This section contains the entire system log messages related to NATPT.
56.1 TRANS
Mnemonic TRANS Severity Level 6
Variable Fields $1: string
Explanation Normal information in NATPT module
Trigger Action No
Example %Jan 1 01:27:05 2003 SysName NATPT/6/TRANS:
Recommended
Action
56.2 TRANS
Mnemonic TRANS Severity Level 3
Variable Fields $1:information string
Explanation Error occurs in packet transmitting.
Trigger Action As transmitting packet, failed to delete address mapping on slot.
%Jan 1 01:37:58 2003 SysName NATPT/3/TRANS: Deletion of

Example
AddressMap Failed on slot 1 ... Error Code : 3
Recommended
Action
Trigger Action As transmitting packet, failed to create address mapping.
%Jan 1 01:37:58 2003 SysName NATPT/3/TRANS: Creation of

Example
AddressMap Failed on slot 3…Error Code : 3
Recommended
Action
As transmitting packet, failed to download NATPT prefix

Trigger Action
information to slot.
%Jan 1 01:37:58 2003 SysName NATPT/3/TRANS: AAM Prefix

Example
information download on slot 3 failed
Recommended
Action
57 ND Messages
This section contains the entire system log messages related to ND.
57.1 ConfigConflict
Mnemonic ConfigConflict Severity Level 4
Syslog Message The same neighbor entry has been added on the interface [string]
The neighbor entry with same global IP address has been added
Explanation
into another interface
Add a static neighbor entry on an interface when the number of

Trigger Action
entries has reached the upper limit.
Example % Error: Neighbor Entry already exists!
Recommended
Action

57.2 ConfigConflict
Syslog Message The max number of static neighbor entries is exceeded!
Variable Fields
The max number of static neighbor entries exceeds the number of

Explanation
static neighbor entries configured
Trigger Action Add a static neighbor entry on an interface
Example % Error: The max number of static neighbor entries is exceeded!
Recommended
Action
57.3 ConfigConflict
Syslog Message The max number of neighbor entries is exceeded!
Variable Fields
The max number of neighbor entries exceeds the number of

Explanation
neighbor entries configured
Trigger Action Add a new neighbor entry
Example % Error: The max number of neighbor entries is exceeded!
Recommended
Action
57.4 ConfigConflict
Syslog Message Duplicate address:[string] on the interface [string]
$1: The address configured.

Variable Fields
Explanation The same address is configured on the interface of other device
Trigger Action Configure IPv6 address on an interface
%Feb 21 17:37:04:160 2007 SysName ND/4/ConfigConflict:

Example
Duplicate address:33::8 on the interface Vlan-interface9
Recommended
A different address should be configured
Action

57.5 ConfigConflict
Syslog Message [string] is inconsistent
Variable Fields $1: The Type of configconflict.
Explanation Configured different values on two routers. interface
Trigger Action Receive a router advertisement from other routers
%Jun 16 10:54:43:462 2005 DUT1-Dis ND/4/ConfigConflict:

Example
PREFIX VALID TIME is inconsistent
Recommended
A different value should be configured
Action
57.6 TimeError
Mnemonic TimeError Severity Level 3
Syslog Message Preferred lifetime is greater than the valid lifetime, Prefix: [ipaddr].
Variable Fields $1: IPv6 Prefix
The preferred lifetime is greater than the valid lifetime in the prefix
Explanation information of RA received when address autoconfiguration is
enabled.
when address autoconfiguration is enabled, If the preferred lifetime is

Trigger Action greater than the valid lifetime in the prefix information of RA
received , this log is dispayed.
%Dec 22 11:10:05:364 2007 SysName ND/3/TimeError:

Example
Preferred lifetime is greater than the valid lifetime, Prefix:10::.
Recommended
Action
58 NDP Messages
58.1 NDPSTART
Mnemonic NDPSTART Severity Level 3
Syslog Message The device starts running NDP now.

Variable Fields
Explanation The NDP is enable.
Trigger Action When The NDP status is from disable to enable.
%Apr 27 16:35:47:200 2000 SysName NDP/3/NDPSTART:The

Example
device starts running NDP now.
Recommended
Action
59 NETSTREAM Messages
This section contains the entire system log messages related to NetStream.
59.1 MALLOC_FAIL
Mnemonic MALLOC_FAIL Severity Level 4
Syslog Message Slot [INTEGER] allocate memory fail.
Variable Fields $1: Slot NO.
Explanation Failed to allocate memory on some slot.
Trigger Action Failed to allocate memory for Netstream on some slot.
%Feb 21 15:39:10:406 2007 SysName NETSTREAM /4/

Example
MALLOC_FAIL: Slot 0 allocate memory fail.
Recommended
Action
59.2 FREE_FAIL
Mnemonic MALLOC_FAIL Severity Level 4
Syslog Message Slot [INTEGER] free memory fail.
Variable Fields $1: Slot NO.
Explanation Failed to free memory on some slot.
Trigger Action Failed to free memory for Netstream on some slot.
%Feb 21 15:39:10:406 2007 SysName NETSTREAM /4/

Example
FREE_FAIL: Slot 0 free memory fail
Recommended
Action

59.3 NDPSTOP
Mnemonic NDPSTOP Severity Level 3
Syslog Message The device stops running NDP now.
Variable Fields
Explanation The NDP is disable.
Trigger Action When The NDP status is from enable to disable.
%Apr 27 16:35:26:500 2000 SysName NDP/3/NDPSTOP:The device

Example
stops running NDP now.
Recommended
Action
60 NTDP Messages
60.1 NTDPSTART
Mnemonic NTDPSTART Severity Level 3
Syslog Message The device starts running NTDP now.
Variable Fields
Explanation The NTDP is enabled.
Trigger Action When NTDP is enabled.
%Apr 27 16:33:36:121 2000 SysName NTDP/3/NTDPSTART:The

Example
device starts running NTDP now.
Recommended
Action
60.2 NTDPSTOP
Mnemonic NTDPSTOP Severity Level 5
Syslog Message The device stops running NTDP now.
Variable Fields
Explanation The NTDP is disabled.
Trigger Action When NTDP is disabled.
%Apr 27 16:32:19:334 2000 SysName NTDP/3/NTDPSTOP:The

Example
device stops running NTDP now.

Recommended
Action
61 NTP Messages
This section contains the entire system log messages related to NTP.
61.1 NTP_LOG
Mnemonic NTP_LOG Severity Level 4
Variable Fields $1: the output information
This is a common which prints information and outputs the

Explanation
parameter information.
Trigger Action No action is recommended.
%Feb 21 15:31:30:47 2007 SysName NTP/4/NTP_LOG:

Example
NTP: Disable broadcast protocol packet to CPU error.
Recommended
Action
62 OAM Messages
This section contains the entire system log messages related to OAM.
62.1 LOCALERRFRAME
Mnemonic LOCALERRFRAME Severity Level 2
Syslog Message \r\nLocal errored frame event has occured on [string].
Explanation A local port occurred a errored frame event

Trigger Action
greater than the specified threshold for a period.
%Oct 23 13:44:28:254 2007 SysName

ETHOAM/2/NOTENTERLOOPBACK:Slot=3;
Example %Oct 23 13:44:28:254 2007 SysName

ETHOAM/2/LINFAULT:Slot=3;
Local errored frame event has occured on GigabitEthernet3/1/19

Recommended
Check the link
Action
62.2 REMOTEERRFRAME
Mnemonic REMOTEERRFRAME Severity Level 2
Syslog Message \r\nRemote errored frame event has occured on [string].
This event is generated if the errored frame count on the remote

Trigger Action
port is equal to or greater than the specified threshold for a period.
%Oct 23 13:44:28:254 2007 SysName


Remote errored frame event has occured on GigabitEthernet3/1/19
Recommended
Check the link
Action
62.3 LOCALERRFRAMEPERIOD
Mnemonic LOCALERRFRAMEPERIOD Severity Level 2
Syslog Message \r\nLocal errored frame period event has occured on [string].
Explanation A local port occurred a errored frame period event

Trigger Action greater than the specified threshold for a period. The period is
specified by a number of received frames.
%Oct 23 13:44:28:254 2007 SysName

%Oct 23 13:44:28:254 2007 SysName

Example
Local errored frame period event has occured on

Recommended
Check the link
Action

62.4 REMOTEERRFRAMEPERIOD
Mnemonic REMOTEERRFRAMEPERIOD Severity Level 2
Syslog Message \r\nRemote errored frame period event has occured on [string].
This event is generated if the errored frame count on the remote port
Trigger Action is equal to or greater than the specified threshold for a period.
The period is specified by a number of received frames.
%Oct 23 13:44:28:254 2007 SysName

%Oct 23 13:44:28:254 2007 SysName

Example
Remote errored frame period event has occured on

Recommended
Check the link
Action
62.5 LOCALERRFRAMESEC
Mnemonic LOCALERRFRAMESEC Severity Level 2
\r\nLocal error frame seconds summary event has occured on

Syslog Message
[string].
Explanation A local port occurred a errored frame seconds summary event
This event is generated if the number of errored frame seconds is

Trigger Action
equal to or greater than the specified threshold for a period.
%Oct 23 13:44:28:254 2007 SysName

%Oct 23 13:44:28:254 2007 SysName

Example
Local error frame seconds summary event has occured on

Recommended
Check the link
Action
62.6 REMOTEERRFRAMESEC

Mnemonic REMOTEERRFRAMESEC Severity Level 2
\r\nRemote error frame seconds summary event has occured on

Syslog Message
[string]..
This event is generated if the number of errored frame seconds on

Trigger Action the remote port is equal to or greater than the specified threshold for
a period.
%Oct 23 13:44:28:254 2007 SysName

%Oct 23 13:44:28:254 2007 SysName

Example
Remote error frame seconds summary event has occured on

Recommended
Check the link
Action
62.7 REMOTEDYINGGASP
Mnemonic REMOTEDYINGGASP Severity Level 2
Syslog Message \r\nRemote dying gasp event has occured on [string]..
Explanation A remote port occurred a dying gasp event
Trigger Action An unrecoverable remote failure condition has occurred
%Oct 23 13:44:28:254 2007 SysName


Remote dying gasp event has occured on GigabitEthernet3/1/19
Recommended
Action
62.8 REMOTECRITICALE

Mnemonic REMOTECRITICALE Severity Level 2
Syslog Message \r\nRemote critical event has occured on [string]
Explanation A remote port occurred a critical event
Trigger Action An unspecified critical event has occurred.
%Oct 23 13:44:28:254 2007 SysName


Remote critical event has occured on GigabitEthernet3/1/19
Recommended
Action
63 OPTMOD Messages
This section contains the entire system log messages related to OPTMOD.
63.1 BIAS_HIGH
Mnemonic BIAS_HIGH Severity Level 2
Syslog Message [STRING] : Bias current is high!
Explanation Bias current of the module is high
Trigger Action The module on this port has some fault.
%Oct 23 13:44:28:254 2008 SysName OPTMOD/2/

Example BIAS_HIGH:Slot=3;
GigabitEthernet3/1/19: Bias current is high!
Recommended
Check the module or replace it.
Action
63.2 TX_POW_HIGH
Mnemonic TX_POW_HIGH Severity Level 2
Syslog Message [STRING] : TX power is high!
Explanation TX power of the module is high!

%Oct 23 13:44:28:254 2008 SysName

Example OPTMOD/2/TX_POW_HIGH:Slot=3;
GigabitEthernet0/0/13: TX power is high!
Recommended
Action
63.3 TYPE_ERR
Mnemonic TYPE_ERR Severity Level 3
Syslog Message [STRING] : The transceiver type is not supported by port hardware!
Explanation The transceiver type is not supported by port hardware!

TYPE_ERR :Slot=3;
Example
GigabitEthernet3/1/19: The transceiver type is not supported by
port hardware!
Recommended
Action
63.4 CFG_ERR
Mnemonic CFG_ERR Severity Level 3
Syslog Message [STRING] : The transceiver type does not match port configuration!
Explanation The transceiver type does not match port configuration!

CFG_ERR:Slot=3;
Example
GigabitEthernet3/1/19: The transceiver type does not match port
configuration!
Recommended
Action
63.5 MODULE_OUT
Mnemonic MODULE_OUT Severity Level 4
Syslog Message [STRING] : The transceiver is absent.
Explanation The transceiver is plugged out.
Trigger Action The module on this port has beed plugged out.

Example MODULE_OUT:Slot=3;
GigabitEthernet3/1/19: The transceiver is absent.
Recommended
None
Action
63.6 MODULE_IN
Mnemonic MODULE_IN Severity Level 4
Syslog Message [STRING] : The transceiver is 1000_BASE_BX_U_SFP.
$1:A Port name

Variable Fields
$2:The type string of the module.
Explanation The transceiver is plugged in, it’s type is 1000_BASE_BX_U_SFP.
Trigger Action a transceiver is plugged in the inferface,

Example MODULE_IN:Slot=3;
GigabitEthernet0/0/13: The transceiver is 1000_BASE_BX_U_SFP.
Recommended
None
Action
63.7 IO_ERR
Mnemonic IO_ERR Severity Level 5
Syslog Message [STRING] : The transceiver information I/O failed!
Explanation The transceiver information I/O failed!

Example IO_ERR:Slot=3;
GigabitEthernet3/1/19: The transceiver information I/O failed!

Recommended
Action
63.8 CHKSUM_ERR
Mnemonic CHKSUM_ERR Severity Level 5
Syslog Message [STRING] : The checksum of transceiver information is bad!
Explanation The checksum of transceiver information is bad!

CHKSUM_ERR :Slot=3;
Example
GigabitEthernet3/1/19: The checksum of transceiver information is
bad!
Recommended
Action
63.9 TX_ALM_ON
Mnemonic TX_ALM_ON Severity Level 5
Syslog Message [STRING] : [STRING] is detected!
$1:A Port name

Variable Fields
$2:The fault type string of sending
Explanation A send fault of transceiver is detected!

Example TX_ALM_ON :Slot=3;
GigabitEthernet3/1/19: TX_fault is detected!
Recommended
Action
63.10 TX_ALM_OFF
Mnemonic TX_ALM_OFF Severity Level 5
Syslog Message [STRING] : [STRING] is gone.

$1:A Port name

Variable Fields
$2:The fault type string of sending
Explanation A send fault of transceiver is gone.
Trigger Action The module on this port has recovered to normal.

Example TX_ALM_OFF :Slot=3;
GigabitEthernet3/1/19: TX_fault is gone.
Recommended
None
Action
63.11 RX_ALM_ON
Mnemonic RX_ALM_ON Severity Level 5
$1:A Port name

Variable Fields
$2:The fault type string of receiveing
Explanation A receive not ready fault of the module is detected!

Example RX_ALM_ON :Slot=3;
GigabitEthernet3/1/19: RX_not_ready is detected!
Recommended
Action
63.12 RX_ALM_OFF
Mnemonic RX_ALM_OFF Severity Level 5
$1:A Port name

Variable Fields
$2:The fault type string of receiveing
Explanation A receive not ready fault of the module is gone.

Example RX_ALM_OFF:Slot=3;
GigabitEthernet3/1/19: RX_not_ready is gone.

Recommended
None
Action
63.13 MOD_ALM_ON
Mnemonic MOD_ALM_ON Severity Level 5
$1:A Port name

Variable Fields
$2:The fault type string of module
Explanation A module not ready fault of the module is detected!
%Oct 23 13:44:28:254 2008 SysName

Example OPTMOD/5/MOD_ALM_ON :Slot=3;
GigabitEthernet3/1/19: Module_not_ready is detected!
Recommended
Action
63.14 MOD_ALM_OFF
Mnemonic MOD_ALM_OFF Severity Level 5
$1:A Port name

Variable Fields
$2:The fault type string of module
Explanation A module not ready fault of the module is gone.

Example MOD_ALM_OFF:Slot=3;
GigabitEthernet3/1/19: Module_not_ready is gone.
Recommended
None
Action
63.15 TEMP_HIGH
Mnemonic TEMP_HIGH Severity Level 5
Syslog Message [STRING] : Temperature is high!

Explanation The temperature of the module is high.

Example TEMP_HIGH:Slot=3;
GigabitEthernet3/1/19: Temperature is high!
Recommended
None
Action
63.16 TEMP_LOW
Mnemonic TEMP_LOW Severity Level 5
Syslog Message [STRING] : Temperature is low!
Explanation The temperature of the module is low.

Example TEMP_LOW:Slot=3;
GigabitEthernet3/1/19: Temperature is low!
Recommended
None
Action
63.17 TEMP_NORMAL
Mnemonic TEMP_NORMAL Severity Level 5
Syslog Message [STRING] : Temperature is normal.
Explanation The temperature of the module is normal.

Example TEMP_NORMAL:Slot=3;
GigabitEthernet3/1/19: Temperature is normal.
Recommended
None
Action

63.18 VOLT_HIGH
Mnemonic VOLT_HIGH Severity Level 5
Syslog Message [STRING] : Voltage is high!
Explanation The voltage of the module is high.

Example VOLT_HIGH:Slot=3;
GigabitEthernet3/1/19: Voltage is high!
Recommended
None
Action
63.19 VOLT_LOW
Mnemonic VOLT_LOW Severity Level 5
Syslog Message [STRING] : Voltage is low!
Explanation The voltage of the module is low.

Example VOLT_LOW:Slot=3;
GigabitEthernet3/1/19: Voltage is low!
Recommended
None
Action
63.20 VOLT_NORMAL
Mnemonic VOLT_NORMAL Severity Level 5
Syslog Message [STRING] : Voltage is normal.
Explanation The voltage of the module is normal.

Example VOLT_NORMAL:Slot=3;
GigabitEthernet3/1/19: Voltage is normal.

Recommended
None
Action
63.21 RX_POW_HIGH
Mnemonic RX_POW_HIGH Severity Level 5
Syslog Message [STRING] : RX power is high!
Explanation The RX power of the module is high.

Example RX_POW_HIGH:Slot=3;
GigabitEthernet3/1/19: RX power is high!
Recommended
None
Action
63.22 RX_POW_LOW
Mnemonic RX_POW_LOW Severity Level 5
Syslog Message [STRING] : RX power is low!
Explanation The RX power of the module is low.

Example RX_POW_LOW:Slot=3;
GigabitEthernet3/1/19: RX power is low!
Recommended
None
Action
63.23 RX_POW_NORMAL
Mnemonic RX_POW_NORMAL Severity Level 5
Syslog Message [STRING] : RX power is normal.
Explanation The RX power of the module is normal.


Example RX_POW_NORMAL:Slot=3;
GigabitEthernet3/1/19: RX power is normal.
Recommended
None
Action
63.24 BIAS_LOW
Mnemonic BIAS_LOW Severity Level 5
Syslog Message [STRING] : Bias current is low!
Explanation The bias current of the module is low.

Example BIAS_LOW:Slot=3;
GigabitEthernet3/1/19: Bias current is low!
Recommended
None
Action
63.25 BIAS_NORMAL
Mnemonic BIAS_NORMAL Severity Level 5
Syslog Message [STRING] : Bias current is normal.
Explanation The bias current of the module is normal.

Example BIAS_NORMAL:Slot=3;
GigabitEthernet3/1/19: Bias current is normal.
Recommended
None
Action
63.26 TX_POW_LOW

Mnemonic TX_POW_LOW Severity Level 5
Syslog Message [STRING] : TX power is low!
Explanation The TX power of the module is low.

Example TX_POW_LOW:Slot=3;
GigabitEthernet3/1/19: TX power is low!
Recommended
None
Action
63.27 TX_POW_NORMAL
Mnemonic TX_POW_NORMAL Severity Level 5
Syslog Message [STRING] : TX power is normal.
Explanation The TX power of the module is normal.

Example TX_POW_NORMAL:Slot=3;
GigabitEthernet3/1/19: TX power is normal.
Recommended
None
Action
63.28 PHONY_MODULE
Mnemonic PHONY_MODULE Severity Level 4
[STRING] : This transceiver is NOT sold by H3C. H3C therefore

Syslog Message shall NOT guarantee the normal function of the device or assume
the maintenance responsibility thereof!
Explanation The module on this port is not sold by H3C.
Trigger Action The module on this port is not sold by H3C.


PHONY_MODULE:Slot=3;
Example GigabitEthernet3/1/19: This transceiver is NOT sold by H3C. H3C
therefore shall NOT guarantee the normal function of the device or
assume the maintenance responsibility thereof!
Recommended
None
Action
64 PBR6 Messages
This section contains the entire system log messages related to PBR6.
64.1 PBR6_LOG
Mnemonic PBR6_LOG Severity Level 4
#1 Same next-hop is being configured more than once
Variable Fields
Explanation Duplicate next-hop has been configured.
Trigger Action Duplicate next hop has been configured.
%Feb 21 15:39:10:406 2007 SysName PBR6/4/PBR6_LOG:

Example
Same next-hops are being configured more than once.
Recommended
Action
#2 Same default next-hop is being configured more than once
Variable Fields
Explanation Duplicate default next-hop has been configured.
Trigger Action Duplicate default next-hop has been configured.
%Feb 21 15:39:10:406 2007 SysName PBR6/4/PBR6_LOG:

Example
Same default next-hops are being configured more than once.
Recommended
Action
65 PIM Messages
This section contains the entire system log messages related to PIM.
65.1 INFO
Mnemonic INFO Severity Level 5
Variable Fields $1: The information given to user.
After the equipment has done some correct operations, it shows

Explanation
user the equipment’s operations.
Trigger Action Equipment has done some correct operations.
%Jan 1 01:37:58 2003 SysName PIM/5/INFO: Genid option length

Example
%d should be 4.
Recommended
Action
65.2 ERR
Mnemonic ERR Severity Level 4
Variable Fields $1: The warning infomation.
After the equipment has done some unexpected operation, it

Explanation
shows what is wrong with the operations of the equipment.
%Jan 1 01:37:58 2003 SysName PIM/5/ERR: Bad group address,

Example
Ignoring message.
Recommended
Action
66 PKEY Messages
This section contains the entire system log messages related to PKEY.
66.1 KEY_GENERATE
Mnemonic KEY_GENERATE Severity Level 4
Syslog
The public host key has been Created successfully.
Message

Variable Fields
Explanation The public host key has been Created successfully.
Trigger Action The public host key has been Created successfully.
%Sep 1 11:06:06:875 2007 SysName PKEY/4/KEY_GENERATE:The

Example
public host key has been Created successfully.
Recommended
Action
66.2 KEY_GENERATE
Syslog
The public server key has been Created successfully.
Message
Variable Fields
Explanation The public server key has been Created successfully.
Trigger Action The public server key has been Created successfully.
%Sep 1 11:06:06:875 2007 SysName PKEY/4/KEY_GENERATE:The

Example
public server key has been Created successfully.
Recommended
Action
66.3 KEY_GENERATE
Syslog
Failed to create public key pair.
Message
Variable Fields
Explanation Failed to create public key pair.
Trigger Action Failed to create public key pair.
%Sep 1 11:06:06:875 2007 SysName PKEY/4/KEY_GENERATE:Failed

Example
to create public key pair.
Recommended
Action
66.4 KEY_ZEROIZE

Mnemonic KEY_ZEROIZE Severity Level 4
Syslog
The public host key has been destroyed successfully.
Message
Variable Fields
Explanation The public host key has been destroyed successfully.
Trigger Action The public host key has been destroyed successfully.
%Sep 1 11:06:06:875 2007 SysName PKEY/4/KEY_ZEROIZE:The

Example
public host key has been destroyed successfully.
Recommended
Action
66.5 KEY_ZEROIZE
Syslog
The public server key has been destroyed successfully.
Message
Variable Fields
Explanation The public server key has been destroyed successfully.
Trigger Action The public server key has been destroyed successfully.
%Sep 1 11:06:06:875 2007 SysName PKEY/4/KEY_ZEROIZE:The

Example
public server key has been destroyed successfully.
Recommended
Action
66.6 KEY_ZEROIZE
Syslog
Failed to destroy the public key pair.
Message
Variable Fields
Explanation Failed to destroy the public key pair.
Trigger Action Failed to destroy the public key pair.
%Sep 1 11:06:06:875 2007 SysName PKEY/4/KEY_ZEROIZE:Failed to

Example
destroy the public key pair.
Recommended
Action

66.7 KEY_EXPORT
Mnemonic KEY_EXPORT Severity Level 4
Syslog
The public key has been exported to file successfully.
Message
Variable Fields
Explanation The public key has been exported to file successfully.
Trigger Action The public key has been exported to file successfully.
%Sep 1 11:06:06:875 2007 SysName PKEY/4/KEY_EXPORT:The

Example
public key has been exported to file successfully.
Recommended
Action
66.8 KEY_EXPORT
Mnemonic KEY_EXPORT Severity Level 4
Syslog
Failed to export the public key to file.
Message
Variable Fields
Explanation Failed to export the public key to file.
Trigger Action Failed to export the public key to file.
%Sep 1 11:06:06:875 2007 SysName PKEY/4/KEY_EXPORT:Failed to

Example
export the public key to file.
Recommended
Action
66.9 KEY_BACKUP
Mnemonic KEY_BACKUP Severity Level 3
Syslog
Failed to backup the public host key.
Message
Variable Fields
Explanation Failed to backup the public host key.
Trigger Action Failed to backup the public host key.
%Sep 1 11:06:06:875 2007 SysName PKEY/3/KEY_BACKUP:Failed to

Example
backup the public host key.

Recommended
Action
66.10 KEY_BACKUP
Mnemonic KEY_BACKUP Severity Level 3
Syslog
Failed to backup the public server key.
Message
Variable Fields
Explanation Failed to backup the public server key.
Trigger Action Failed to backup the public server key.
%Sep 1 11:06:06:875 2007 SysName PKEY/3/KEY_BACKUP:Failed to

Example
backup the public server key.
Recommended
Action
67 PKI Messages
This section contains the entire system log messages related to PKI.
67.1 Local_Cert_Retrieval
Mnemonic Local_Cert_Retrieval Severity Level 4
Syslog Message Retrieval local certificate of the domain [String] successfully.
Variable Fields $1: The name of PKI domain
Explanation The local certificate is retrieved successfully.
Trigger Action The local certificate is retrieved successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/

Example Local_Cert_Retrieval:Retrieval local certificate of the domain
ar29pki successfully.
Recommended
Action
67.2 Local_Cert_Retrieval
Mnemonic Local_Cert_Retrieval Severity Level 4

Syslog Message Failed to retrieval local certificate of the domain [String].
Explanation Failed to retrieve the local certificate.
Trigger Action Failed to retrieve the local certificate.
%Jan 5 16:13:13:120 2007 SysName PKI/5/

Example Local_Cert_Retrieval:Failed to retrieval local certificate of the
domain ar29pki.
Recommended
Action
67.3 CA_Cert_Retrieval
Mnemonic CA_Cert_Retrieval Severity Level 4
Syslog Message Retrieval CA certificates of the domain [String] successfully.
Explanation The CA certificate is retrieved successfully.
Trigger Action The CA certificate is retrieved successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ CA_Cert_Retrieval:

Example
Retrieval CA certificates of the domain ar29pki successfully.
Recommended
Action
Syslog Message Failed to receive a certificate from the ca domain [String].
Explanation Failed to receive CA certificates.
Trigger Action Failed to receive CA certificates.
%Jan 5 16:13:13:120 2007 COMWARE PKI/4/

Example CA_Cert_Retrieval:Failed to receive a certificate from the ca
domain rsa-domain.
Recommended
Action

Syslog Message CA certificate for the domain [String] already exists.
Explanation CA certificates of this domain already exists.
Trigger Action CA certificates of this domain existed.

Example
CA certificate for the domain ar29pki already exists.
Recommended
Action
Syslog Message CA certificates of the domain [String] error.
Explanation There are errors in CA certificates.
Trigger Action There are errors in CA certificates.

Example
CA certificates of the domain ar29pki error.
Recommended
Action
Syslog Message No root certificate of the domain [String].
Explanation No root certificate of this domain.
Trigger Action No root certificate of this domain.

Example
No root certificate of the domain ar29pki.
Recommended
Action

Syslog Message Root certificate of the domain [String] error.
Explanation Root certificate of this domain is wrong
Trigger Action Root certificate of this domain is wrong.

Example
Root certificate of the domain ar29pki error.
Recommended
Action
67.9 Local_Cert_Request
Mnemonic Local_Cert_Request Severity Level 4
Syslog Message Request local certificate of the domain [String] successfully.
Explanation Request local certificate of this domain successfully.
Trigger Action Request local certificate of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Local_Cert_Request:

Example
Request local certificate of the domain ar29pki successfully.
Recommended
Action
Syslog Message Failed to receive a certificate from the CA domain [String].
Explanation Failed to receive a certificate from the CA domain.
Trigger Action Failed to receive a certificate from the CA domain.

Example
Failed to receive a certificate from the CA domain ar29pki.

Recommended
Action
Syslog Message Local certificate of the domain [String] already exists.
Explanation Local certificate of the domain already exists.
Trigger Action Local certificate of the domain already exists.

Example
Local certificate of the domain ar29pki already exists.
Recommended
Action
67.12 Import_Cert_File
Mnemonic Import_Cert_File Severity Level 4
Syslog Message Failed to import certificate file of the domain [String].
Explanation Failed to import CA certificates of this domain.
Trigger Action Failed to import CA certificates of this domain.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Import_Cert_File:

Example
Failed to import certificate file of the domain ar29pki.
Recommended
Action
67.13 Import_Local_Cert
Mnemonic Import_Local_Cert Severity Level 4
Syslog Message Import local certificate of the domain [String] successfully.
Explanation Import local certificate of this domain successfully.
Trigger Action Import local certificate of this domain successfully.

%Jan 5 16:13:13:120 2007 SysName PKI/5/ Import_Local_Cert:

Example
Import local certificate of the domain ar29pki successfully.
Recommended
Action
Syslog Message Failed to import local certificate of the domain [String].
Explanation Failed to import local certificate of this domain.
Trigger Action Failed to import local certificate of this domain.

Example
Failed to import local certificate of the domain ar29pki.
Recommended
Action
Failed to import local certificate of the domain [String] because of

Syslog Message
BIO malloc fail.
Failed to import local certificate of this domain because of BIO

Explanation
malloc fail.
Failed to import local certificate of this domain because of BIO

Trigger Action
malloc fail.

Example Failed to import local certificate of the domain ar29pki because of
BIO malloc fail.
Recommended
Action

Syslog Message Failed to import domain [String] local certificate, no certificate in file.
Failed to import this domain’s local certificate for no certificate in

Explanation
file.
Failed to import this domain’s local certificate for no certificate in

Trigger Action
file.

Example
Failed to import domain ar29pki local certificate, no certificate in file.
Recommended
Action
Syslog Message Certificate and entity do not match.
Explanation Certificate and entity do not match.
Trigger Action Certificate and entity do not match.

Example
Certificate and entity do not match.
Recommended
Action
67.18 Import_Local_Key
Mnemonic Import_Local_Key Severity Level 4
Syslog Message Import local private key of the domain [String] successfully.
Explanation Import local private key of this domain successfully.
Trigger Action Import local private key of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Import_Local_Key:

Example
Import local private key of the domain ar29pki successfully.
Recommended
Action

67.19 Import_Local_Key
Mnemonic Import_Local_Key Severity Level 4
Syslog Message Failed to import local private key of the domain [String].
Explanation Failed to import local private key of this domain.
Trigger Action Failed to import local private key of this domain.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Import_Local_Key:

Example
Failed to import local private key of the domain ar29pki.
Recommended
Action
67.20 Import_CA_Cert
Mnemonic Import_CA_Cert Severity Level 4
Syslog Message Import CA certificates of the domain [String] successfully.
Explanation Import CA certificates of this domain successfully.
Trigger Action Import CA certificates of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Import_CA_Cert:

Example
Import CA certificates of the domain ar29pki successfully.
Recommended
Action
Syslog Message Failed to import CA certificates of the domain [String].
Explanation Failed to import CA certificates of this domain.
Trigger Action Failed to import CA certificates of this domain.

Example
Failed to import CA certificates of the domain ar29pki.
Recommended
Action

Failed to import CA certificates of the domain [String] because of

Syslog Message
malloc fail.
Failed to import CA certificates of this domain because of memory

Explanation
allocation failure.
Failed to import CA certificates of this domain because of memory

Trigger Action
allocation failure.

Example Failed to import CA certificates of the domain ar29pki because of
malloc fail.
Recommended
Action

Syslog Message
password fail.
Failed to import CA certificates of this domain because of password

Explanation
failure.
Failed to import CA certificates of this domain because of password

Trigger Action
failure.

password fail.
Recommended
Action

Syslog Message
parse fail.

Failed to import CA certificates of this domain because of parse

Explanation
failure.
Failed to import CA certificates of this domain because of parse

Trigger Action
failure.

parse fail.
Recommended
Action
Failed to import CA certificates of the domain [String] because of no

Syslog Message
root certificate.
Failed to import CA certificates of this domain because of no root

Explanation
certificate.
Failed to import CA certificates of this domain because of no root

Trigger Action
certificate.

no root certificate.
Recommended
Action

Syslog Message
root certificate error.
Failed to import CA certificates of this domain because of root

Explanation
certificate error.
Failed to import CA certificates of this domain because of root

Trigger Action
certificate error.


root certificate error.
Recommended
Action

Syslog Message
certficate chain error.
Failed to import CA certificates of this domain because of certficate

Explanation
chain error.
Failed to import CA certificates of this domain because of certficate

Trigger Action
chain error.

certficate chain error.
Recommended
Action
67.28 Update_CA_Cert
Mnemonic Update_CA_Cert Severity Level 4
Syslog Message Update CA certificates of the Domain [String] successfully.
Explanation Update CA certificates of this domain successfully.
Trigger Action Update CA certificates of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Update_CA_Cert:

Example
Update CA certificates of the Domain ar29pki successfully.
Recommended
Action
67.29 Update_CA_Cert

Mnemonic Update_CA_Cert Severity Level 4
Syslog Message Failed to update CA certificates of the domain [String].
Explanation Failed to update CA certificates of this domain.
Trigger Action Failed to update CA certificates of this domain.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Update_CA_Cert:

Example
Failed to update CA certificates of the domain ar29pki.
Recommended
Action
67.30 Delete_CA_Cert
Mnemonic Delete_CA_Cert Severity Level 4
Syslog Message Delete CA certificates of the domain [String] successfully.
Explanation Delete CA certificates of this domain successfully.
Trigger Action Delete CA certificates of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Delete_CA_Cert:

Example
Delete CA certificates of the domain ar29pki successfully.
Recommended
Action
Syslog Message Failed to delete CA certificates of the domain [String].
Explanation Failed to delete CA certificates of this domain.
Trigger Action Failed to delete CA certificates of this domain.

Example
Failed to delete CA certificates of the domain ar29pki.
Recommended
Action

Syslog Message CA certificate of the domain [String] is not exist.
Explanation CA certificate of this domain does not exist.
Trigger Action CA certificate of this domain does not exist.

Example
CA certificate of the domain ar29pki is not exist.
Recommended
Action
67.33 Delete_Local_Cert
Mnemonic Delete_Local_Cert Severity Level 4
Syslog Message Delete local certificate of the domain [String] successfully.
Explanation Delete local certificate of this domain successfully.
Trigger Action Delete local certificate of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Delete_Local_Cert:

Example
Delete local certificate of the domain ar29pki successfully.
Recommended
Action
67.34 Delete_Local_Cert
Mnemonic Delete_Local_Cert Severity Level 4
Syslog Message Failed to delete local certificate of the domain [String].
Explanation Failed to delete local certificate of this domain.
Trigger Action Failed to delete local certificate of this domain.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Delete_Local_Cert:

Example
Failed to delete local certificate of the domain ar29pki.
Recommended
Action

67.35 Verify_Cert
Mnemonic Verify_Cert Severity Level 4
Syslog Message Verify certificate [String] of the domain [String] successfully.
$1: The subject name of certificate

Variable Fields
$2: The name of PKI domain
Explanation Verify certificate of this domain successfully.
Trigger Action Verify certificate of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Verify_Cert:

Example Verify certificate cn=kkk, o = h3, cn=cn of the domain ar29pki
successfully.
Recommended
Action
67.36 Verify_Cert
Mnemonic Verify_Cert Severity Level 4
Syslog Message Failed to verify certificate [String] of the domain [String].
$1: The subject name of certificate

Variable Fields
$2: The name of PKI domain
Explanation Failed to verify certificate of the domain.
Trigger Action Failed to verify certificate of the domain.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Verify_Cert:

Example Failed to verify certificate cn=kkk, o = h3, cn=cn of the domain
ar29pki.
Recommended
Action
67.37 Verify_CA_Root_Cert
Mnemonic Verify_CA_Root_Cert Severity Level 4
Syslog Message CA root certificate of the domain [String] is trusted.
Explanation CA root certificate of this domain is trusted.

Trigger Action CA root certificate of this domain is trusted.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Verify_CA_Root_Cert:

Example
CA root certificate of the domain ar29pki is trusted.
Recommended
Action
67.38 Verify_CA_Root_Cert
Mnemonic Verify_CA_Root_Cert Severity Level 4
Syslog Message CA root certificate of the domain [String] is not trusted.
Explanation CA root certificate of this domain is not trusted.
Trigger Action CA root certificate of this domain is not trusted.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Verify_CA_Root_Cert:

Example
CA root certificate of the domain ar29pki is not trusted.
Recommended
Action
67.39 Retrieval_CRL
Mnemonic Retrieval_CRL Severity Level 4
Syslog Message Retrieval CRL of the domain [String] successfully.
Explanation Retrieve CRL of this domain successfully.
Trigger Action Retrieve CRL of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Retrieval_CRL:

Example
Retrieval CRL of the domain ar29pki successfully.
Recommended
Action
67.40 Retrieval_CRL
Mnemonic Retrieval_CRL Severity Level 4
Syslog Message Failed to retrieval CRL of the domain [String].

Explanation Failed to retrieve CRL of this domain.
Trigger Action Failed to retrieve CRL of this domain.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Retrieval_CRL: Failed

Example
to retrieval CRL of the domain ar29pki.
Recommended
Action
67.41 Update_CRL
Mnemonic Update_CRL Severity Level 4
Syslog Message Update CRL of the domain [String] successfully.
Explanation Update CRL of this domain successfully.
Trigger Action Update CRL of this domain successfully.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Update_CRL: Update

Example
CRL of the domain ar29pki successfully.
Recommended
Action
67.42 Update_CRL
Syslog Message Failed to update CRL of the domain [String].
Explanation Failed to update CRL of this domain.
Trigger Action Failed to update CRL of this domain.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Update_CRL: Failed

Example
to update CRL of the domain ar29pki.
Recommended
Action
67.43 Update_CRL
Syslog Message Update crl of the domain [String] failure.

Explanation Failed to update CRL of this domain.
Trigger Action Failed to update CRL of this domain.
%Jan 5 16:13:13:120 2007 SysName PKI/5/ Update_CRL: Update

Example
crl of the domain ar29pki failure.
68 PORTAL Messages
This section contains the entire system log messages related to PORTAL.
68.1 PORTAL_LOG
Mnemonic PORTAL_LOG Severity Level 4
Variable Fields $1: String
Explanation Normal syslog information
Trigger Action Portal failed to set ACL driver.
%Apr 26 12:07:04:802 2000 SysName PORTAL/5/ PT_LOG: Portal

Example
failed to set ACL driver, return:1
Recommended
Action
68.2 PORTAL_LOG
Trigger Action Failed to write message queue.
%Apr 26 12:07:04:802 2000 SysName PORTAL/5/ PT_LOG: Failed

Example
to write queue:6, 13, 1, 2, 3",
Recommended
Action
68.3 PORTAL_LOG
Trigger Action Failed to send Portal control message
%Apr 26 12:07:04:802 2000 SysName PORTAL/5/ PT_LOG: Failed

Example
to send Portal control message
Recommended
Action
68.4 PORTAL_LOG
Trigger Action Cannot get packets number for TCP cheat or the queue is full.
%Apr 26 12:07:04:802 2000 SysName PORTAL/5/ PT_LOG:

Example
Cannot get packets number for TCP Cheat or the queue is full!
Recommended
Action
68.5 PORTAL_LOG
Trigger Action Cannot write to packet queue of TCP Cheat
%Apr 26 12:07:04:802 2000 SysName PORTAL/5/ PT_LOG:

Example
Cannot write packet into queue of TCP Cheat!
Recommended
Action
69 Q921 Messages
This section contains the entire system log messages related to Q921.
69.1 Q921_Log
Mnemonic Q921_Log Severity Level 8
Syslog Message [string] Error [string] occurred
$1: Uport
Variable Fields
$2: the occurred error type.
Occurrence of MDL-ERROR indication within the basic states and

Explanation
actions to be taken by the management entity
Trigger Action Occurrence of MDL-ERROR indication within the basic states
%Jan 1 01:27:05 2003 SysName Q921/8/Q921_Log:interface

Example
serial 1/0:15 MDL_Error_Ind occurred.
Recommended
Action
70 RDS Messages
This section contains the entire system log messages related to RDS.
70.1 LOGIN
Mnemonic LOGIN Severity Level 6
[STRING] from Port=[STRING] Vlan=[ULONG] MAC=[STRING]

Syslog Message
IP=[IPADDR] sent authentication request
$1: The user name
$2: The port number
Variable Fields $3: The VLAN ID
$4: The MAC address
$5: The IP address
Explanation Receive a new authentication request
Trigger Action Receive a new authentication request
%2005/1/5 06:31:15:345 SysName SHELL/5/LOGIN:- 1 – test

Example
from(192.168.44.1) sent authentication request
Recommended
Action

70.2 LOGIN

Syslog Message
IP=[IPADDR] failed to be online for [STRING]
$1: The user name
$2: The port number
$3: The VLAN ID

Variable Fields
$4: The MAC address
$5: The IP address
$6:The cause of the failure
Explanation A new user has failed to log in.
Trigger Action A new user has failed to log in

Example
from(192.168.44.1) failed to be online for timeout.
Recommended
Action
70.3 LOGIN

Syslog Message
IP=[IPADDR] succeeded to be online
$1: The user name
$2: The port number
Variable Fields $3: The VLAN ID
$4: The MAC address
$5: The IP address
Explanation A new user logs in successfully.
Trigger Action A new user logs in successfully.

Example
from(192.168.44.1) succeeded to be online.
Recommended
Action
70.4 LOGIN

Syslog Message
IP=[IPADDR] quit for [STRING]
$1: The user name
$2: The port number
$3: The VLAN ID

Variable Fields
$4: The MAC address
$5: The IP address
$6:The cause of the quit
Explanation A user quits system for some reasons
Trigger Action A user quits system

Example
from(192.168.44.1) quit for timeout.
Recommended
Action
71 RM Messages
This section contains the entire system log messages related to RM.
71.1 RMLOG
Mnemonic RMLOG Severity Level 4
$1:[STRING]
Variable Fields
$2:[STRING]
Explanation The log of routing management ERROR information
Trigger Action The RM event processing failed.
%Jan 16 16:35:03:900 2007 SysName RM/4/RMLOG:

Example IFNET Physical message processing was not successful,
ulRetVal:6000011
Recommended
Action
72 RMON Messages

This section contains the entire system log messages related to RMON.
72.1 ADDINFO
Mnemonic ADDINFO Severity Level 6
[STRING] table is added a valid row with index [ULONG] by

Syslog Message
[STRING]
$1: The name of table.
Variable Fields $2: An index that uniquely identifies an entry in the alarm table.
$3: The owner of the entry.
Explanation A new entry has been added into alarm table successfully.
Trigger Action Add a new entry into alarm table.
%Jan 1 01:27:05 2003 SysName RMON/6/ADDINFO:Alarm table

Example
is added a valid row with index 15 by cl
Recommended
Action
72.2 DELINFO
Mnemonic DELINFO Severity Level 6
[STRING] table is invalidated a row with index [ULONG] by

Syslog Message
[STRING]
$1: The name of table.
Variable Fields $2: An index that uniquely identifies an entry in the alarm table.
$3: The owner of the entry.
Explanation An existed entry is removed from alarm table successfully.
Trigger Action Remove a existed entry from alarm table.
%Jan 1 01:37:58 2003 SysName RMON/6/DELINFO:Alarm table

Example
is invalidated a row with index 15 by cl.
Recommended
Action
73 RMX Messages
This section contains the entire system log messages related to RMX.
73.1 LOG
$1:[STRING]
Variable Fields
$2:[STRING]
The log of the routing management of international network packet

Explanation
exchange information.
Trigger Action The RMX event processing failed.
% Jan 16 17:28:08:678 2007 SysName RMX/5/LOG:

Example
IPXRM: Delay to free a route!
Recommended
Action
74 RPR Messages
This section contains the entire system log messages related to RPR.
74.1 TOPOINCONS
Mnemonic TOPOINCONS Severity Level 3
Syslog Message [STRING]: The inconsistent topology defect is present.
Variable Fields $1: RPR logical interface name.
Explanation Topology of the ring is inconsistent in each RPR station.
Trigger Action Topology of the ring is inconsistent.
%Feb 22 11:24:48:370 2007 SysName RPR/3/RPR_LOG: Slot=1;

Example Ten-GigabitEthernet3/1/1: The inconsistent topology defect is
present.
Recommended
Action
74.2 TOPOINCONSOVER
Mnemonic TOPOINCONSOVER Severity Level 3
Syslog Message [STRING]: The inconsistent topology defect is present.
Explanation Inconsistency of topology on the ring disappears.
Trigger Action Topology. inconsistency of the ring has been.resumed


Example
Ten-GigabitEthernet3/1/1: The inconsistent topology defect is over.
Recommended
Action
74.3 TOPOINSTAB
Mnemonic TOPOINSTAB Severity Level 3
Syslog Message [STRING]: The topology instability defect is present.
Explanation Topology is instable in the RPR ring.
Trigger Action Topology is instable in the RPR ring.

Example
Ten-GigabitEthernet3/1/1: The topology instability defect is present.
Recommended
Action
74.4 TOPOINSTABOVER
Mnemonic TOPOINSTABOVER Severity Level 3
Syslog Message [STRING]: The topology instability defect is over.
Explanation Instability of topology on the ring disappear.
Trigger Action Topology instability of the ring has been.resumed

Example
Ten-GigabitEthernet3/1/1: The topology instability defect is over.
Recommended
Action
74.5 STATNUMEXCED
Mnemonic STATNUMEXCED Severity Level 3
[STRING]: The maximum number of stations exceeded defect is

Syslog Message
present.
Explanation The number of stations on the RPR ring exceeded the maximum.

Trigger Action The number of stations on the RPR ring exceeded the maximum.

Example Ten-GigabitEthernet3/1/1: The maximum number of stations
exceeded defect is present.
Recommended
Disconnect the station that exceeded the maximum.
Action
74.6 STATNUMEXCEEDOVER
Mnemonic STATNUMEXCEEDOVER Severity Level 3
[STRING]: The maximum number of stations exceeded defect is

Syslog Message
over.
The number of stations on the RPR decreases to less than the

Explanation
maximum.
When the number of stations on the RPR decreases to less than the
Trigger Action
maximum.

Example Ten-GigabitEthernet3/1/1: The maximum number of stations
exceeded defect is over.
Recommended
Action
74.7 MACDUP
Mnemonic MACDUP Severity Level 3
Syslog Message [STRING]: The duplicate MAC address defect is present.
More than two stations on the RPR ring have the same MAC
Explanation
address.
Trigger Action Two stations on the RPR ring have the same MAC address.

Example Ten-GigabitEthernet3/1/1: The duplicate MAC address defect is
present.
Recommended Finding the stations that have same MAC address with others, and
Action changing their MAC addresses.
74.8 MACDUPOVER
Mnemonic MACDUPOVER Severity Level 3
Syslog Message [STRING]: The duplicate MAC address defect is over.
Explanation No stations on the RPR ring has same MAC address.
Trigger Action The stations with same mac address changed their mac address.

Example Ten-GigabitEthernet3/1/1: The duplicate MAC address defect is
over.
Recommended
Action
74.9 IPDUP
Mnemonic IPDUP Severity Level 3
Syslog Message [STRING]: The IP duplicate defect is present.
Explanation More than two stations on the RPR ring have the same IP address.
Trigger Action Two stations on the RPR ring have the same IP address.

Example Ten-GigabitEthernet3/1/1: The duplicate IP address defect is
present.
Recommended Finding the station that have same IP address with others, and
Action changing their IP addresses.
74.10 IPDUPOVER
Mnemonic IPDUPOVER Severity Level 3
Syslog Message [STRING]: The IP duplicate defect is over.
Explanation No more stations on the RPR ring has the same IP address.
The stations with same IP address changed their mac address to

Trigger Action
diffirent.

Example
Ten-GigabitEthernet3/1/1: The duplicate IP address defect is over.
Recommended
Action

74.11 LRTTINCOMP
Mnemonic LRTTINCOMP Severity Level 3
Syslog Message [STRING]: The LRTT incomplete defect is present.
Explanation The calculation of Lrtt is incompleted.
Trigger Action The calculation of Lrtt failed

Example
Ten-GigabitEthernet3/1/1: The LRTT incomplete defect is present.
Recommended
Action
74.12 LRTTINCOMPOVER
Mnemonic LRTTINCOMPOVER Severity Level 3
Syslog Message [STRING]: The LRTT incomplete defect is over.
Explanation The calculation of Lrtt is completed.
Trigger Action The calculation of Lrtt is successful

Example
Ten-GigabitEthernet3/1/1: The LRTT incomplete defect is over.
Recommended
Action
74.13 PROTINCONS
Mnemonic PROTINCONS Severity Level 3
Syslog Message [STRING]: The protection configuration defect is present.
More than two stations on the RPR ring with the diffirent protection
Explanation
configuration
Two stations on the RPR ring with the diffirent protection

Trigger Action
configuration.

Example Ten-GigabitEthernet3/1/1: The protection configuration defect is
present.

Recommended
Configure all the stations on the ring with same protection mode.
Action
74.14 PROTINCONSOVER
Mnemonic PROTINCONSOVER Severity Level 3
Syslog Message [STRING]: The protection configuration defect is over.
No more station on the RPR ring with the diffirent protection

Explanation
configuration.
All the stations on the ring configured their protection mode to

Trigger Action
same.

Example Ten-GigabitEthernet3/1/1: The protection configuration defect is
over.
Recommended
Action
74.15 JBINCONS
Mnemonic JBINCONS Severity Level 3
Syslog Message [STRING]: The jumbo configuration defect is present.
More than two stations on the RPR ring with the diffirent jumbo
Explanation
preference configurations
Two stations on the RPR ring with the diffirent jumbo preference
Trigger Action
configurations.

Example Ten-GigabitEthernet3/1/1: The jumbo configuration defect is
present.
Recommended Config all the stations on the ring with same jumbo preference
Action mode.
74.16 JBINCONSOVER
Mnemonic JBINCONSOVER Severity Level 3
Syslog Message [STRING]: The jumbo configuration defect is over

No more station on the RPR ring with the diffirent jumbo preference
Explanation
configurations.
All the stations on the ring configed their jumbo preference to the
Trigger Action
same.

Example
Ten-GigabitEthernet3/1/1: The jumbo configuration defect is over
Recommended
Action
74.17 RESERBWEXCEED
Mnemonic RESERBWEXCEED Severity Level 3
Syslog Message [STRING]: The excess reserved rate defect is present.
The reserved bandwidth rate exceeds the bandwith on the RPR

Explanation
ring.
The reserved bandwidth rate exceeds the bandwith on the RPR

Trigger Action
ring.

Example Ten-GigabitEthernet3/1/1: The excess reserved rate defect is
present.
Recommended Decrease the reserved bandwidth to less than the bandwidth of

Action RPR ring.
74.18 RESERBWEXCEEDOVER
Mnemonic JBINCONSOVER Severity Level 3
Syslog Message [STRING]: The excess reserved rate defect is over.
Reserved bandwidth decreases to less than the bandwidth of RPR

Explanation
ring.
Reserved bandwidth decreases to less than the bandwidth of RPR

Trigger Action
ring.

Example
Ten-GigabitEthernet3/1/1: The excess reserved rate defect is over.
Recommended
Action

74.19 MISCABLING
Mnemonic MISCABLING Severity Level 3
Syslog Message [STRING]: Miscabling warning is present.
When a station’s west/east span connects to another station’s

Explanation
west/east span, this log message is present.
A station’s west/east span connects to another station’s west/east

Trigger Action
span

Example
Ten-GigabitEthernet3/1/1: Miscabling warning is present.
Recommended Finding the station that connects its west/ease span to another
Action station’s west/east, and connects reverse span. .
74.20 MISCABLINGOVER
Mnemonic MISCABLINGOVER Severity Level 3
Syslog Message [STRING]: Miscabling warning is over.
Explanation The station with miscabling is corrected.
Trigger Action The station with miscabling is corrected.

Example
Ten-GigabitEthernet3/1/1: Miscabling warning is over.
Recommended
Action
74.21 IDLEISOLATE
Mnemonic IDLEISOLATE Severity Level 3
Syslog Message [STRING]: Idle isolate is present.
A station is in idle isolate state while its west span connects to its
Explanation
east
Trigger Action While a station’s west span connect to its east span

Example
Ten-GigabitEthernet3/1/1: Idle isolate is present.

Recommended
Action
74.22 IDLEISOLATEOVER
Mnemonic IDLEISOLATEOVER Severity Level 3
Syslog Message [STRING]: Idle isolate is over.
A station exit Idle isolate state when its west span disconnects to its
Explanation
east
Trigger Action When the station’s west span disconnect to its east.

Example
Ten-GigabitEthernet3/1/1: Idle isolate is over.
Recommended
Action
75 RRPP Messages
This section contains the entire system log messages related to RRPP.
75.1 FAIL
Mnemonic FAIL Severity Level 2
Syslog Message Domain[ULONG] ring [ULONG] failed!
$1: RRPP domain ID

Variable Fields
$2: RRPP ring ID
Explanation RRPP ring failed.
Trigger Action Link status of devices on this RRPP ring changed down.
%Aug 15 18:06:28:281 2007 SysName RRPP/2/FAIL:Domain1 ring

Example
1 failed!
Recommended To check devices on this RRPP ring,the physical topology is not a

Action ring anymore.
75.2 RESTORE

Mnemonic RESTORE Severity Level 2
Syslog Message Domain[ULONG] ring [ULONG] restored!
$1: RRPP domain ID

Variable Fields
$2: RRPP ring ID
Explanation RRPP ring restored.
RRPP protocol is enabled or link status of devices on this RRPP

Trigger Action
ring changed up.
%Aug 15 18:07:45:93 2007 SysName

Example
RRPP/2/RESTORE:Domain1 ring 1 restored!
Recommended
Action
76 RSVP Messages
This section contains the entire system log messages related to RSVP.
76.1 RSVP_LOG_INFO
Mnemonic RSVP_LOG_INFO Severity Level 6
Variable Fields $1: The system log string
RSVP module receives event or interface message.

Explanation
RSVP module receices wrong rsvp message.
Trigger Action RSVP module receives messages.
%Jan 20 17:05:54:00 2007 SysName

Example RSVP/7/RSVP_LOG_INFO:Successful Create path message from
lspm message.
Recommended
Action
Trigger Action RSVP module receives wrong rsvp message.
%Jan 20 17:05:54:00 2007 SysName RSVP/7/RSVP_LOG_INFO:

Example Warning: Found unsupported POLICY_DATA object in SREFRESH
message!
Recommended
Action
77 SHELL Messages
This section contains the entire system log messages related to SHELL.
77.1 LOGIN
Syslog Message [string] login from [string]
$1: The name of users.

Variable Fields
$2: The type of users.
Explanation A user login successfully.
Trigger Action User login.
%Feb 26 06:54:53:411 2007 SysName SHELL/4/LOGIN: Console

Example
login from con0
Recommended
Action
77.2 LOGOUT
Syslog Message [string] logout from [string]
$1: The name of users.

Variable Fields
$2: The type of users.
Explanation A user quits from system
Trigger Action A user quits from system
%Feb 26 06:54:51:74 2007 SysName SHELL/4/LOGOUT: Console

Example
logout from con0
Recommended
Action
77.3 CLI
Mnemonic CLI Severity Level 5
Syslog Message '[string]' from [string] by [string]
$1: Command string.
Variable Fields $2: User type.
$3: User name.
Explanation Record command string.

Trigger Action Command was executed successfully.
%Feb 26 06:54:51:74 2007 SysName SHELL/5/CLI:’quit’ from co0

Example
by Console
Recommended
Action
77.4 CMD
Mnemonic CMD Severity Level 4
Syslog Message task:[string] ip:[string] user:[string] command:[string]
$1: Task name, if there isn’t task name, ‘***’ instead.
$2: IP address, if there isn’t IP address, ‘**’ instead.

Variable Fields
$3: User name, if there isn’t user name, ‘**’ instead.
$4: Command string.
Explanation Record command string.
Trigger Action Command was executed successfully.
%Feb 26 06:37:44:203 2007 SysName SHELL/4/CMD:task:co0

Example
ip:** user:** command:dir
Recommended
Action
77.5 LOGINFAIL
Mnemonic LOGINFAIL Severity Level 4
Syslog Message [string] failed to login [string]
$1: the user name

Variable Fields
$2: from ip(mac) on user-interface name.
Explanation User login failed or timed out.
Trigger Action User login failed or timed out.
%Feb 10 10:22:21:790 2007 SysName SHELL/4/LOGINFAIL:

Example TELNET user failed to login from 12.130.2.19(000f-e239-1f97) on
VTY0 due to source MAC restriction.
Recommended
Action

78 SNMP Messages
This section contains the entire system log messages related to SNMP.
78.1 GET
Mnemonic GET Severity Level 6
\r\nseqNO = <[ulong]> srcIP = <[string]> op = <[string]> node =

Syslog Message
<[string]> value = <[string]\r\n
$1: The sequence number of snmp get operation log
$2: The source IP address of the NMS.
Variable Fields $3: The operation type of the NMS
$4: The MIB object name and OID
$5: The value field of the response packet
Explanation Record the information about the SNMP get request packet
NMS send the get request and the SNMP recording get operation,
Trigger Action
log function is enabled
%Sep 11 14:33:23:174 2007 SysName SNMP/6/GET:
seqNO = <1> srcIP = <169.254.76.36> op = <get> node =

Example
<sysLocation(1.3.6.1.2.1.1
.6.0)> value = <>
Recommended
Action
78.2 SET

Mnemonic SET Severity Level 6
\r\nseqNO = <[ulong]> srcIP = <[string]> op = <[string]> errorIndex

Syslog Message = <[ulong]> errorStatus = <[string]> node = <[string]> value =
<[string]\r\n
$1: The sequence number of snmp get operation log
$2: The source IP address of the NMS.
$3: The operation type of the NMS
Variable Fields $4: The error index of the set operation
$5: The error status of the set operation
$6: The MIB object name and OID
$7: The value field of the response packet
Explanation Record the information about set request and response packet
NMS send the set request and the SNMP recording set operation
Trigger Action
log function is enabled
%Sep 11 14:33:52:38 2007 SysName SNMP/6/SET:
Example seqNO = <3> srcIP = <169.254.76.36> op = <set> errorIndex = <0>

errorStatus = <noError> node = <sysLocation(1.3.6.1.2.1.1.6.0)>
value = <Hangzhou China>
Recommended
Action
79 SOCKET Messages
79.1 TCP MD5

Mnemonic TCP MD5 Severity Level 4
Received TCP packet with invalid MD5 digest. SOURCE:[STRING]

Syslog Message
FOREIGN:[STRING]
$1: source ip address:port

Variable Fields
$2: destination ip address:port
Explanation Receive TCP packet with invalid MD5 digest
Trigger Action Receive TCP packet with invalid MD5 digest
%Aug 22 20:40:05:234 2007 SysName SOCKET/4/TCP

Example MD5:Received TCP packet with invalidMD5 digest.
SOURCE:34.34.1.1:1000 FOREIGN:1.1.2.2:2000
Recommended
Action

79.2 TCP NAPTHA

Mnemonic TCP NAPTHA Severity Level 4
The number of TCP connections in [STRING] state is [ULONG],

Syslog Message
which is above the limit.
$1: TCP state

Variable Fields
$2: the number of TCP connections
The number of TCP connections in some state is above the limit

Explanation
which the user specified.
When the number of TCP connections in some state is above the

Trigger Action limit which the user specified. (The user has enabled the TCP anti-
Naptha function.)
%Aug 23 16:16:39:797 2007 SysName SOCKET/4/TCP

Example NAPTHA:The number of TCP connections in Syn_Rcvd state is 50,
which is above the limit.
Recommended
Action
79.3 SOCKETLOG
Mnemonic SOCKETLOG Severity Level 4
$1: Current task name.

Variable Fields
$2: Original task name.
Explanation There is something wrong when a task get its Task Control Block.
Some Task has forgot to release its Task Control Block When it kill
Trigger Action
itself.
%Aug 23 16:21:13:515 2007 SysName SOCKET/4/SOCKETLOG:-

Example
The task ITTP has got the TCB of task HTTP;
Recommended
Action
80 SSH Messages
This section contains the entire system log messages related to ssh.
80.1 ACCEPTFAIL

Mnemonic ACCEPTFAIL Severity Level 4
Syslog Message Acceptting fails when listenning Socket [string]
Variable Fields $1: socket ID
Explanation A socket error occurred in listening
Trigger Action Something wrong in socket module or the port of listening is in use.
%Aug 17 16:55:08:625 2007 SysName

Example
SSH/4/ACCEPTFAIL:Acceptting fails when listenning Socket [22]
Recommended
Action
80.2 LOGOUT
Mnemonic LOGOUT Severity Level 4
[string] user [string] (IP:[string]) logout because :SSH Client close

Syslog Message the connection
Current FSM is : [string]
$1: type of user
$2: name of user

Variable Fields
$3: IP address of user
$4: The status of current FSM
Explanation SSH Client close the connection.
Trigger Action SSH Client close the connection.
%Aug 17 16:55:08:625 2007 SysName SSH/4/ LOGOUT:STEL

user user1 (IP:1.1.1.1) logout because :SSH Client close the
Example connection
Current FSM is : SSH_Main_Dissconnect
Recommended
Action
80.3 LOGIN
Syslog Message [string] user [string] (IP:[string]) login succeeded!

$1: type of user
$2: name of user

Variable Fields
Explanation SSH user login successfully.
Trigger Action SSH user login successfully.
%Aug 17 16:55:08:625 2007 SysName SSH/4/LOGIN:STEL user

Example
user1 (IP:1.1.1.1) login succeeded!
Recommended
Action
80.4 LOGINFAIL
[string] user [string] (IP:[string]) login failed because: VTY [string]

Syslog Message
authentication timeout !
$1: type of user
$2: name of user

Variable Fields
$4: the port number of VTY
Explanation SSH user failed to login because of authentication timeout.
Trigger Action SSH user failed to login because of authentication timeout.
%Aug 17 16:55:08:625 2007 SysName SSH/4/LOGINFAIL:SSH

Example user user1 (IP:1.1.1.1) login failed because: VTY 0 authentication
timeout !
Recommended
Action
80.5 LOGINFAIL
[string] user [string] (IP:[string]) login failed because: The user don't
Syslog Message
support SFTP!

$1: type of user
$2: name of user

Variable Fields
Explanation SSH user failed to login because user does not support SFTP.
Trigger Action SSH user failed to login because user does not support SFTP.
%Aug 17 16:55:08:625 2007 SysName SSH/4/LOGINFAIL:SFTP

Example user user1 (IP:1.1.1.1) login failed because: The user don't support
SFTP!
Recommended
Action
80.6 LOGINFAIL
[string] user [string] (IP:[string]) login failed because: The user don't
Syslog Message
support STEL!
$1: type of user
$2: name of user

Variable Fields
Explanation SSH user failed to login because user does not support STEL.
Trigger Action SSH user failed to login because user does not support STEL.
%Aug 17 16:55:08:625 2007 SysName SSH/4/LOGINFAIL:STEL

Example user user1 (IP:1.1.1.1) login failed because: The user don't support
STEL!
Recommended
Action
80.7 AUTHFAIL
Mnemonic AUTHFAIL Severity Level 4
[string] user [string] (IP:[string]) login failed because: Failed to

Syslog Message
process version!

Mnemonic AUTHFAIL Severity Level 4
$1: type of user
$2: name of user

Variable Fields
Explanation SSH user failed to login because of version dismatches.
Trigger Action SSH user failed to login because of version dismatches.
%Aug 17 16:55:08:625 2007 SysName SSH/4/AUTHFAIL:STEL

Example user user1 (IP:1.1.1.1) login failed because: Failed to process
version!
Recommended
Action
80.8 AUTHSUCC
Mnemonic AUTHSUCC Severity Level 4
[string] user [string] (IP:[string]) success to process [string]

Syslog Message
Authentication!
$1: type of user
$2: name of user

Variable Fields
$4: type of authentication
Explanation SSH user succeeded in authentication.
Trigger Action SSH user succeeded in authentication.
%Aug 17 16:55:08:625 2007 SysName SSH/4/AUTHSUCC:SSH

Example user user1 (IP:1.1.1.1) success to process PASSWORD
Authentication!
Recommended
Action
80.9 LOGOUT
Syslog Message [string] user [string] (IP:[string]) logout

$1: type of user
$2: name of user

Variable Fields
Explanation SSH user logout.
Trigger Action SSH user logout.
%Aug 17 16:55:08:625 2007 SysName SSH/4/LOGOUT:STEL

Example
user user1 (IP:1.1.1.1) logout
Recommended
Action
80.10 SFTPOPER
Mnemonic SFTPOPER Severity Level 4
Syslog Message SFTP user [string](IP:[string]) made sftp operation -- :[string]
$1: name of user
Variable Fields $2: IP address of user
$3: current operation
Explanation SSH user’s sftp operation.
Trigger Action SSH user’s sftp operation.
%Aug 17 16:55:08:625 2007 SysName SSH/4/SFTPOPER:SFTP

Example user user1 (IP:1.1.1.1) made sftp operation -- :Read
file[flash:/logfile.txt]
Recommended
Action
81 TFTP Client Messages

This section contains the entire system log messages related to TFTP Client.
81.1 TFTP_LOG
Mnemonic TFTP_LOG Severity Level 4

Mnemonic TFTP_LOG Severity Level 4
The TFTP user transfer file.

Trigger Action
The light of transferring file will be lighted.
%Feb 21 15:39:10:406 2007 SysName TFTPC/4/TFTP_LOG:

Example
FTPC: Download ended, turn off the signal light.
Recommended
Action
82 TNLM Messages
This section contains the entire system log messages related to TNLM.
82.1 LOG
Variable Fields $1: The system log string
Explanation TNLM process fialed events
Trigger Action System running under Low Memory.
%Mar 3 14:11:06:228 2007 SysName TNLM/4/LOG:

Example
Error: Command fails: insufficient memory
Recommended
Action
Trigger Action Tunnel Event MSG is NULL.

Example
Error: Tunnel Event MSG is NULL
Recommended
Action
Trigger Action Var 2 in the MSG of TUNNEL is NULL.

Example
Error: Var 2 in the MSG of TUNNEL is NULL
Recommended
Action
Trigger Action Number of Tunnel ID exceeds the available value.


Example
Error: Number of Tunnel ID exceeds the available value
Recommended
Action
Trigger Action HSB Error, failed to send hsb message.

Example
Error: HSB Error: Send Failure
Recommended
Action
Trigger Action Cannot Create Timer.

Example
Error: Cannot Create Timer
Recommended
Action
Trigger Action TNLM received memory shortage (or restore) notification.

Example Error: Memory Shortage Notification Received : Event = MEM
SHORTAGE (or MEM RESTORE)
Recommended
Action
Trigger Action System running under low memory.

Example
Error: System running under Low Memory
Recommended
Action
83 TUNNEL Messages
This section contains the entire system log messages related to TUNNEL.
83.1 NOTICE
Mnemonic NOTICE Severity Level 2
[string]: Tunnel source address is same to the destination address,

Syslog Message
please modify it!
Variable Fields $1: tunnel interface name.

The IP address of the tunnel source interface is the same with that
Explanation of the destination of tunnel, which causes address conflict. You
must configure different addresses for them.
The IP address of the tunnel source interface is the same with that
Trigger Action
of the destination of tunnel.
%Jan 1 01:37:58 2003 SysName TUNNEL/2/NOTICE:tunnel 0/1/0:

Example Tunnel source address is same to the destination address, please
modify it!
Recommended
Modify the IP address of the tunnel source interface.
Action
83.2 NOTICE
[string]: Same tunnel exists, please modify the configuration of

Syslog Message
tunnel source interface!
Variable Fields $1: tunnel interface name.
Two tunnels have the same source address and destination

Explanation
address. You must change tunnel configuration.
Conflict occurred because the IP address you specified for the

Trigger Action source interface of the tunnel is the same as the source IP address
of another tunnel with the same destination.
%Jan 1 01:37:58 2003 SysName TUNNEL/2/NOTICE: Same

Example tunnel exists, please modify the configuration of tunnel source
interface!
Modify the source or destination address of either of the two

Recommended
tunnels to make their source address or destination address
Action
different.
83.3 WARNING
Mnemonic WARNING Severity Level 4
Syslog Message Operation failed for no enough resources
Variable Fields No
This message indicates that the device driver has no enough

Explanation
resources when creating tunnel.
Trigger Action The device driver has no enough resources when creating tunnel.

Mnemonic WARNING Severity Level 4
%Mar 31 10:51:44:189 2007 SysName

Example TUNNEL/4/WARNING:Slot=5;
Operation failed for no enough resources
Recommended
Action
84 UDPH
84.1 UDPH_LOG
Mnemonic UDPH_LOG Severity Level 4
Trigger Action No action is recommended.
%Feb 21 15:31:30:47 2007 SysName UDPH/4/UDPH_LOG:

Example
UDPH: Failed to delete L3 IF node in IF remove event.
Recommended
Action
85 USERLOG Messages
This section contains the entire system log messages related to USERLOG.
85.1 NAT

Mnemonic NAT Severity Level 6
Syslog Message "\r\n[string] "
$1:NAT log.It contains the following fields:
protocol;
source address;
NAT address;
Variable Fields destination address;
the time at which NAT session is created;
the time at which NAT session is deleted,or the time at which NAT
log is sent;
the reason why a NAT log is sent;
Explanation A NAT log is outputted by the way of syslog.
NAT log is enabled and configure that NAT log is export to info-
Trigger Action
center.
%Feb 10 14:10:07:971 2007 SysName USERLOG/6/NAT:
ICMP; 10.10.10.2:28--->12.130.2.102:12288; 12.130.2.22:28;

Example
[2007/02/10 14:09:06-2007/02/10 14:10:07];
Operator 1: Normal over
Recommended
Action
85.2 FLOW1.0

Mnemonic FLOW Severity Level 6
Syslog Message "\r\n[string]"
$1:FLOW log.It contains the following fields:
protocol;
source address;
source port;
Variable Fields destination address;
destination port;
the time at which a flow session is created;
the time at which a flow session is deleted;
the reason why a flow log is sent;
Explanation A FLOW log is outputted by the way of syslog
Trigger Action Enable FLOW log.
Example
Recommended
Action
85.3 FLOW3.0

Mnemonic FLOW Severity Level 6
Syslog Message "\r\n[string]"
$1:FLOW log.It contains the following fields:
protocol;
source address;
source port;
source nat address
source nat port
destination address;
destination port;
destination nat address
Variable Fields destination nat port
source receive package
source receive byte
source send package
source send byte
source VPN ID
destination VPN ID
the time at which a flow session is created;
the time at which a flow session is deleted;
the reason why a flow log is sent;
Explanation A FLOW log is outputted by the way of syslog
Trigger Action Enable FLOW log.
Example
Recommended
Action
86 VFS Messages
This section contains the entire system log messages related to VFS.
86.1 LOG

Syslog Message \r\n [STRING] mounted into slot [ULONG]. \r\n
$1: The device name.

Variable Fields
Explanation A mountable device mount into board.
Trigger Action A mountable device mount into board.
%Aug 17 02:06:11:908 2007 SysName VFS/4/LOG:

Example
cf: mounted into slot 4.
Recommended
Action
86.2 LOG
Syslog Message \r\n [STRING] umounted from slot [ULONG]. \r\n

Variable Fields
Explanation A mountable device umount from board.
Trigger Action A mountable device umount from board.

Example
cf: umounted from slot 4.
Recommended
Action
86.3 LOG

Syslog Message \r\n [STRING] inserted into slot [ULONG]. \r\n

Variable Fields
Explanation A mountable device insert into board.
Trigger Action A mountable device insert into board.

Example
cf: inserted into slot 4.
Recommended
Action
86.4 LOG
Syslog Message \r\n [STRING] removed from slot [ULONG]. \r\n

Variable Fields
Explanation A mountable device removed from board.
Trigger Action A mountable device removed from board.

Example
cf: removed from slot 4.
Recommended
Action
87 VMIB Messages
This section contains the entire system log messages related to VMIB.
87.1 SIP Authenticate Failure

Mnemonic SIP Authenticate Failure Severity Level 4
Syslog Message SIP Authenticate Failure
Variable Fields NA
Explanation Authentication failed while establishing a Call.
Trigger Action Authentication needed while establishing a Call.

Mnemonic SIP Authenticate Failure Severity Level 4
#Feb 20 14:53:52:918 2007 SysName VMIB/5/SIP Authenticate

Example Failure:
SIP Authenticate Failure
Recommended
Check the configuration of user and password.
Action
87.2 SIP Register Failure

Mnemonic SIP Register Failure Severity Level 4
Syslog Message SIP Register Failure
Variable Fields NA
Explanation SIP registration failure.
Trigger Action UA registers on a SIP server.
#Feb 20 14:47:52:918 2007 SysName VMIB/5/SIP Register

Example Failure:
SIP Register Failure
Recommended
Check the configuration of SIP-ID and Password.
Action
87.3 SIP Server Switch

Mnemonic SIP Server Switch Severity Level 4
Syslog Message SIP Server Switch
Variable Fields NA
Explanation Switch SIP registration server.
Trigger Action Switch SIP registration server.
#Feb 20 14:39:15:718 2007 SysName VMIB/5/SIP Server Switch:

Example
SIP Server Switch
Recommended
Action
88 VOS Messages
This section contains the entire system log messages related to VOS.

88.1 ASSERT
Mnemonic ASSERT Severity Level 4
Syslog Message slot:[ushort],[string]

Variable Fields
$2: The file path, task name, line information and call stack.
Explanation A assert occur.
Trigger Action A assert occur.
%2000-04-26 12:00:13-VOS-ASSERT:slot:0,Task:INTR(TID:-1)
Assert at file: '../../software/eth/eth_proc.c', Line: 6314
Call Stack:
StackBase ReturnIns FuncEntry
02DBB590 00B21280 FFFFFFFF UnKnown!

Example
02DBBB50 00B39EE8 FFFFFFFF UnKnown!
02DBBB60 0056DC28 FFFFFFFF UnKnown!
02DBBB80 00023050 FFFFFFFF UnKnown!
02DBBC90 01525FB4 FFFFFFFF UnKnown!
02DBBCC0 00000000 FFFFFFFF UnKnown!
Recommended
Action
89 VRFFIB Messages
This section contains the entire system log messages related to VRFFIB.
89.1 log_vrffib
Mnemonic log_vrffib Severity Level 5
Syslog Message VRFFIB synchro state: [string] [string]
$1: The time when the operation occurs

Variable Fields
Explanation The operation described is running. This log is used in main board.
%Feb 21 16:17:21:101 2007 SysName VRFFIB/5/log_vrffib:

Example
VRFFIB synchro state: 2007/02/21 16:17:21 Begin to fresh walking

Recommended
Action
89.2 log_vrffib
Syslog Message VRFFIB synchro state: Board [ULONG]: [string] [string]
$1: board number
Variable Fields $2: The time when the operation occurs
Explanation The operation described is running. This log is used in io board.
%Feb 21 16:17:21:101 2007 SysName VRFFIB/5/log_vrffib:slot 0

Example VRFFIB synchro state: Board 0 2007/02/21 16:17:21 Begin to
fresh walking
Recommended
Action
89.3 log_vrffib
$1: IP address
Variable Fields
$2: VrfIndex
The driver returns conflict flag when the private host route entry is
Explanation
added.
If the driver returns conflict flag when the private host route entry is
Trigger Action
added, the log is displayed.
Aug 16 14:20:12:211 2007 SysName

Example VRFFIB/4/log_fib:Slot=1;Route conflict found, IP:40.1.31.10,
VrfIndex:1
Recommended
Modify configuration.
Action
90 VRRP Messages
This section contains the entire system log messages related to VRRP
90.1 LogAuthFailed
Mnemonic LogAuthFailed Severity Level 3
Syslog Message [STRING] [STRING] | Virtual Router [ULONG] : [STRING]
$1: The standby version, IPv4 or IPv6.
Variable Fields $2: The interface name which the vritual router was configed to.
$3:The virtual router’s ID
Received a VRRP packet, but it can not pass the authentication

Explanation
examination.
Received VRRP packet which can not pass authentication

Trigger Action
examination.
%Feb 21 17:35:57:99 2007 SysName VRRP/3/LogAuthFailed:

Example
IPv4 Ethernet0/0 | Virtual Router 10: failed to authenticate.
Check the configuration of the virtual router on the indicated

Recommended
interface. Make sure that every virtual router with the indicated ID
Action
uses the same authentication mode and authentication key.
90.2 PacketError
Mnemonic PacketError Severity Level 3
Syslog Message [STRING] System detected a vrrp packet error of [STRING]
$1: The vrrp standby version, IPv4 or IPv6.

Variable Fields
$2: The error type of the received VRRP packet.
Explanation Received a VRRP packet, but it is not a valid VRRP packet.
Received an invalid VRRP packet. For example, when the system

Trigger Action
received a VRRP packet but the checksum is incorrect.
%Feb 21 18:00:23:922 2007 SysName VRRP/3/ConfigError:

Example
IPv4 System detected a vrrp packet error of CKSUM ERROR
Recommended Check the configuration of the virtual router on the indicated

Action interface.
The checksum of the VRRP packet is incorrect.
The TTL value of the VRRP packet is incorrect.
Trigger Action The version of the VRRP protocol is not the same as the system.
The type value of the VRRP packet’s TYPE field is incorrect.
The length of the VRRP packet is illegal.

Mnemonic PacketError Severity Level 3
Example See above
Recommended
See above
Action
90.3 ConfigError
Mnemonic ConfigError Severity Level 3
[STRING] System detected a vrrp config error of [STRING],

Syslog Message
Interface:[STRING], Virtual Router:[ULONG]
$2: The error type of configuration.

Variable Fields
$3: The interface name.
$4: The Virtual Router’s ID.
Explanation The current configuration of the virtual router is not correct.
The configuration of the virtual router is not correct. For example,

Trigger Action
the virtual ip address count of the virtual router is not the same.
%Feb 21 18:12:11:860 2007 SysName VRRP/3/ConfigError:
Example IPv4 System detected a vrrp config error of VIRTUAL IP

ADDRESS COUNT ERROR, Interface:Ethernet0/1/0, Virtual
Router:10

Recommended
interface. Make sure that every virtual router of the indicated ID
Action
uses the same virtual ip address’s list.
Failed to add virtual Mac address.
The virtual router’s virtual IP address count is not the same.
The virtual router’s IP address in the received VRRP packet is not

the same as the system itself.
Trigger Action The virtual router’s advertisement interval in the received VRRP
packet is not the same as the system itself.
There are more than one IP Owners in the virtual router group.
Virtual IP address is not in the same subnet as the interface IP

address.
Example See above.
Recommended
See above.
Action
90.4 MasterChange

Mnemonic MasterChange Severity Level 4
Syslog Message [STRING] | Virtual Router [ULONG] : [STRING] reason: [STRING]
$2: The interface name which the virtual router was configured to.
Variable Fields
$3: The Virtual Router’s ID.
$4: The reason for the status change.
Explanation The status of the rirtual router changed.
Trigger Action Timer fired.
%Feb 21 19:24:19:932 2007 SysName VRRP/4/MasterChange:

Example IPv4 Ethernet0/0 | Virtual Router 10 : BACKUP --> MASTER
reason: Timer fired
Recommended
Check the status of the Virtual Router, make sure it works well.
Action
Received VRRP packet.
Failed to add virtual MAC address.
Trigger Action Received an interface event.
The IP address of the interface has been deleted.
Added IP address is illegal.
Example See above.
Recommended
See above.
Action
90.5 SetDriver
Mnemonic SetDriver Severity Level 3
[STRING] [STRING],Virtual Router [ULONG] [STRING] Virtual

Syslog Message
MAC Failed.
$1: The standby version, IPv4 or IPv6.
$2:The interface name where the Virtual Router was configured.

Variable Fields
$3:The Virtual Router’s ID.
$4:Add or delete Virtual MAC.
Explanation Failed to add or delete Virtual MAC.
Trigger Action Failed to add or delete Virtual MAC.
%Feb 21 19:40:01:31 2007 SysName VRRP/3/SetDriver:

Example
IPv4 Vlan-Interface1, Virtual Router 1 ADD Virtual MAC Failed.
Recommended
Action

90.6 SetDriver
Mnemonic SetDriver Severity Level 3
Syslog Message Hardware resources insufficient.
Variable Fields
Explanation Failed to add or delete Virtual MAC.
Trigger Action Failed to add or delete Virtual MAC.
%Feb 21 19:40:01:31 2007 SysName VRRP/3/SetDriver:

Example
Hardware resources insufficient.
Recommended
Action
90.7 TrapBecomeNewMaster
Mnemonic TrapBecomeNewMaster Severity Level 3
Syslog Message [OID]become new master
Variable Fields $1: The OID of the MIB tree’s node.
Explanation A new vritual router turns to MASTER status.
Trigger Action Old master fails to remain MASTER status.
#Feb 21 20:14:07:906 2007 SysName

Example VRRP/3/TrapBecomeNewMaster: 1.3.6.1.2.1.68.0.1 become new
master
Recommended
Action
90.8 TrapAuthFailed
Mnemonic TrapAuthFailed Severity Level 3
Syslog Message [OID]failed to authenticate
Variable Fields $1: The OID of the MIB tree’s node.
Explanation A VRRP packet fails to pass the authentication examination.
Trigger Action Received a VRRP packet with wrong authentication information.
#Feb 21 20:16:46:688 2007 SysName VRRP/3/TrapAuthFailed:

Example
1.3.6.1.2.1.68.0 failed to authenticate


Recommended
interface. Make sure that every virtual router of the indicated ID
Action
uses the same authentication mode and authentication key.

COMWARE V5 Platform System Log Message

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

COMWARE V5 Platform System Log Message

Uploaded by

Copyright:

Available Formats

COMWARE System Log Message

3 ADDR Messages .......................................................................................................................... 28

6 BFD Messages ............................................................................................................................. 34

7 CFM Messages ............................................................................................................................ 35

8 CLST Messages ........................................................................................................................... 37

9 CMD Messages ............................................................................................................................ 43

Hangzhou H3C Technologies Co., Ltd. 2/220

12 DHCP Messages ........................................................................................................................ 66

13 DHCPR Messages ..................................................................................................................... 67

17 DPURPF Messages ................................................................................................................... 73

Hangzhou H3C Technologies Co., Ltd. 4/220

18.5 OAMDISTIMEOUT .......................................................................................................... 76

19 FIBV4 Messages ........................................................................................................................ 84

21 FTP Server Messages................................................................................................................ 86

Hangzhou H3C Technologies Co., Ltd. 5/220

22 GARP Messages ........................................................................................................................ 90

24 HABP Messages ........................................................................................................................ 94

25 HTTPD Messages ...................................................................................................................... 95

26 HTTPS Messages ...................................................................................................................... 95

28 IGMP Messages ......................................................................................................................... 97

30 IKE Messages .......................................................................................................................... 102

31 IPDBG Messages ..................................................................................................................... 103

32 IPCIM Messages ...................................................................................................................... 103

33 IPsec Messages ....................................................................................................................... 104

34 IPV6FIBC Messages ................................................................................................................ 105

35 IPV6PP Messages.................................................................................................................... 106

36 ISIS Messages ......................................................................................................................... 106

37 L2TP Messages........................................................................................................................ 107

38 L2V Messages.......................................................................................................................... 108

39 L3VPN Messages..................................................................................................................... 111

40 LAGG Messages ...................................................................................................................... 112

41 LDP Messages ......................................................................................................................... 113

42 LLC2 Messages........................................................................................................................ 114

43 LLDP Messages ....................................................................................................................... 115

Hangzhou H3C Technologies Co., Ltd. 7/220

44.1 CNAHGEPASSWORD .................................................................................................. 117

45 LSPM Messages ...................................................................................................................... 119

46 LWPS Messages ...................................................................................................................... 120

47 MCS Messages ........................................................................................................................ 121

48 MFIB Messages........................................................................................................................ 122

49 MLD Messages......................................................................................................................... 122

50 MPLS OAM Messages ............................................................................................................. 123

51 QoS Messages ......................................................................................................................... 124

52 MCDP BRIDGE Messages....................................................................................................... 128

53 MRM Messages........................................................................................................................ 129

54 MSDP Messages...................................................................................................................... 129

Hangzhou H3C Technologies Co., Ltd. 8/220

54.2 PEER_DOWN................................................................................................................ 130

55 MSTP Messages ...................................................................................................................... 132

56 NATPT Messages .................................................................................................................... 136

57 ND Messages ........................................................................................................................... 137

58 NDP Messages......................................................................................................................... 139

59 NETSTREAM Messages.......................................................................................................... 140

60 NTDP Messages ...................................................................................................................... 141

61 NTP Messages ......................................................................................................................... 142

Hangzhou H3C Technologies Co., Ltd. 9/220

62 OAM Messages ........................................................................................................................ 142

63 OPTMOD Messages ................................................................................................................ 146

Hangzhou H3C Technologies Co., Ltd. 10/220

63.26 TX_POW_LOW ........................................................................................................... 155

64 PBR6 Messages....................................................................................................................... 157

65 PIM Messages.......................................................................................................................... 157

66 PKEY Messages....................................................................................................................... 158