Comware V3 Switch System Log Message

Comware V3 Switch System Log Message Secret

2006-02-15 Copyright by Huawei 3Com, disclosure is forbidden Page1, Total 176

Title: COMWARE V3 Switch System Log

Message

Authors: Platform MIB Team

Revision: 0.01

Creation Date: 14/02/2006 15:37

Modification Date: 25/03/2016

Abstract:



Title: COMWARE V3 Switch System Log Message ............................................ 1

i Revision History ........................................................................................................... 15

ii References .................................................................................................................. 15

Purpose ......................................................................................................................... 16

Introduction .................................................................................................................... 17

System Log Message Format ........................................................................................ 18

System Log Message Module List ................................................................................. 19

1 802.1X Messages .................................................................................................... 20

1.1 DOT1X_LOG ..................................................................................................... 20

2 ARP Messages ........................................................................................................ 20

2.1 DUPIP ............................................................................................................... 20

2.2 DUPIFIP ............................................................................................................ 21

2.3 DUPVRRPIP ...................................................................................................... 21

2.4 ARP TABLE FULL ............................................................................................. 22

3 CFAX Messages ..................................................................................................... 22

3.1 SENDFAIL ......................................................................................................... 22

3.2 TIMEOUT .......................................................................................................... 23

3.3 PROCINFO ........................................................................................................ 23

3.4 WREVFAIL ........................................................................................................ 23

3.5 CFAX_LOGID_WRQUEFAIL ............................................................................. 24

4 CFM Messages ....................................................................................................... 24

4.1 CFM_LOG ......................................................................................................... 24

4.2 CFM_LOG ......................................................................................................... 25

4.3 CFM_LOG ......................................................................................................... 25

4.4 CFM_LOG ......................................................................................................... 26

4.5 CFM_LOG ......................................................................................................... 26

4.6 CFM_LOG ......................................................................................................... 26

4.7 CFM_LOG ......................................................................................................... 27

4.8 CFM_LOG ......................................................................................................... 27

4.9 CFM_LOG ......................................................................................................... 27

4.10 CFM_LOG ......................................................................................................... 28

4.11 CFM_LOG ......................................................................................................... 28

4.12 CFM_LOG ......................................................................................................... 29

4.13 CFM_LOG ......................................................................................................... 29

4.14 CFM_LOG ......................................................................................................... 29



4.15 CFM_LOG ......................................................................................................... 30

4.16 CFM_LOG ......................................................................................................... 30

4.17 CFM_LOG ......................................................................................................... 30

4.18 CFM_LOG ......................................................................................................... 31

4.19 CFM_LOG ......................................................................................................... 31

4.20 CFM_LOG ......................................................................................................... 31

4.21 CFM_LOG ......................................................................................................... 32

4.22 CFM_LOG ......................................................................................................... 32

4.23 CFM_LOG ......................................................................................................... 33

4.24 CFM_LOG ......................................................................................................... 33

4.25 CFM_LOG ......................................................................................................... 33

4.26 CFM_LOG ......................................................................................................... 34

4.27 CFM_LOG ......................................................................................................... 34

4.28 CFM_LOG ......................................................................................................... 34

4.29 CFM_LOG ......................................................................................................... 35

5 CLST Messages ...................................................................................................... 35

5.1 LOG ................................................................................................................... 35

5.2 LOG ................................................................................................................... 36

5.3 LOG ................................................................................................................... 36

5.4 LOG ................................................................................................................... 37

5.5 LOG ................................................................................................................... 37

5.6 LOG ................................................................................................................... 37

5.7 LOG ................................................................................................................... 38

5.8 LOG ................................................................................................................... 38

5.9 LOG ................................................................................................................... 38

5.10 LOG ................................................................................................................... 39

5.11 LOG ................................................................................................................... 39

5.12 LOG ................................................................................................................... 40

5.13 LOG ................................................................................................................... 40

5.14 LOG ................................................................................................................... 40

5.15 LOG ................................................................................................................... 41

5.16 LOG ................................................................................................................... 41

5.17 LOG ................................................................................................................... 41

5.18 LOG ................................................................................................................... 42

5.19 LOG ................................................................................................................... 42

5.20 LOG ................................................................................................................... 43



5.21 LOG ................................................................................................................... 43

5.22 LOG ................................................................................................................... 43

6 CMD Messages ....................................................................................................... 44

6.1 REBOOT ........................................................................................................... 44

6.2 REBOOT ........................................................................................................... 44

6.3 REBOOT ........................................................................................................... 45

6.4 REBOOT ........................................................................................................... 45

6.5 REBOOT ........................................................................................................... 45

6.6 REBOOT ........................................................................................................... 46

6.7 REBOOT ........................................................................................................... 46

6.8 REBOOT ........................................................................................................... 47

7 DHCPS Messages .................................................................................................. 47

7.1 DHCPS_LOCAL_SERVER ................................................................................ 47

8 FIB Messages ......................................................................................................... 48

8.1 log_fib ................................................................................................................ 48

8.2 log_fib ................................................................................................................ 49

9 FTP Server Messages ............................................................................................. 49

9.1 USERIN ............................................................................................................. 49

9.2 USEROUT ......................................................................................................... 49

9.3 USERIN ............................................................................................................. 50

9.4 USERFAIL ......................................................................................................... 50

9.5 REQUEST ......................................................................................................... 51

9.6 SENDDATA ....................................................................................................... 51

9.7 RECVDATA ....................................................................................................... 52

9.8 RUNERROR ...................................................................................................... 52

9.9 FTPS_LOG ........................................................................................................ 52

10 GARP Messages ............................................................................................... 53

10.1 Wrong Protocol Id .............................................................................................. 53

10.2 Wrong message ................................................................................................ 53

10.3 Valid Msg ........................................................................................................... 53

10.4 Wrong Msg ........................................................................................................ 54

10.5 Wrong Msg Length ............................................................................................ 54

10.6 Wrong attribute .................................................................................................. 55

10.7 Add Entry To GID Failed ................................................................................... 55

10.8 Malloc Failed ..................................................................................................... 55

11 HTTPD Messages ............................................................................................. 56



11.1 Log .................................................................................................................... 56

12 HWCM Messages .............................................................................................. 56

12.1 EXIT .................................................................................................................. 56

12.2 TRAPLOG ......................................................................................................... 57

12.3 CCOPY .............................................................................................................. 57

13 IP Messages ...................................................................................................... 58

13.1 ReassError ........................................................................................................ 58

13.2 QueueFull .......................................................................................................... 58

13.3 MSG .................................................................................................................. 58

13.4 MSG .................................................................................................................. 59

13.5 MSG .................................................................................................................. 59

13.6 MFC ................................................................................................................... 60

14 L2INF Messages ............................................................................................... 60

14.1 PORT LINK ST .................................................................................................. 60

14.2 PORT LINK ST .................................................................................................. 60

14.3 VLANIF LINK ..................................................................................................... 61

14.4 VLANIF LINK ..................................................................................................... 61

14.5 PORT PHY TYP ................................................................................................ 61

14.6 PORT STATUS ................................................................................................. 62

14.7 PORT STATUS ................................................................................................. 62

14.8 PORT LOOPBAC .............................................................................................. 62

14.9 PORT LOOPBAC .............................................................................................. 63

14.10 PORT LOOPBAC ........................................................................................ 63

14.11 VOICE VLAN A ............................................................................................ 63

15 LACL Messages ................................................................................................ 64

15.1 APPLYERR ....................................................................................................... 64

15.2 APPLYERR ....................................................................................................... 64

15.3 APPLYERR ....................................................................................................... 65

15.4 APPLYERR ....................................................................................................... 65

15.5 APPLYERR ....................................................................................................... 65

15.6 APPLYERR ....................................................................................................... 66

15.7 APPLYERR ....................................................................................................... 66

15.8 APPLYERR ....................................................................................................... 66

15.9 DELETEERR ..................................................................................................... 67

15.10 DELETEERR ............................................................................................... 67

15.11 DELETEERR ............................................................................................... 68



15.12 DELETEERR ............................................................................................... 68

15.13 DELETED .................................................................................................... 68

16 LACP Messages ................................................................................................ 69

16.1 PartnerNoLacp .................................................................................................. 69

16.2 AggCreFail ......................................................................................................... 69

16.3 AggCreFail ......................................................................................................... 70

17 LQOS Messages ............................................................................................... 70

17.1 APPLYERR ....................................................................................................... 70

17.2 ADDEXIST ......................................................................................................... 71

17.3 NOTSUPPORT .................................................................................................. 71

17.4 ACTIONERR ..................................................................................................... 71

17.5 ACLERR ............................................................................................................ 72

17.6 RESOURCE ...................................................................................................... 72

17.7 REGISTER ........................................................................................................ 73

17.8 CONFLICT ......................................................................................................... 73

17.9 DELERR ............................................................................................................ 74

17.10 NOTEXIST ................................................................................................... 74

18 MSDP Messages ............................................................................................... 74

18.1 PEER_UPDOWN .............................................................................................. 74

18.2 PEER_UPDOWN .............................................................................................. 75

18.3 SA_LIMIT........................................................................................................... 75

19 MSTP Messages ............................................................................................... 76

19.1 STPSTART ........................................................................................................ 76

19.2 STPSTOP .......................................................................................................... 76

19.3 PFWD ................................................................................................................ 77

19.4 PDISC ............................................................................................................... 77

19.5 ROOT ................................................................................................................ 78

19.6 IVBPDU ............................................................................................................. 78

19.7 RGSUP .............................................................................................................. 78

19.8 LGEXP .............................................................................................................. 79

19.9 UNSUPPORT .................................................................................................... 79

19.10 PSTPDISA ................................................................................................... 79

19.11 MIRRORSTPDISA ....................................................................................... 80

19.12 QUEFILL ...................................................................................................... 80

19.13 EVENTERROR ............................................................................................ 81

19.14 AGEDOUT ................................................................................................... 81



19.15 FORMATERR .............................................................................................. 81

19.16 FRMTINCMPGUARD .................................................................................. 82

20 NDP Messages .................................................................................................. 82

20.1 NDPSTART ....................................................................................................... 82

20.2 NDPSTOP ......................................................................................................... 83

21 NTDP Messages ............................................................................................... 83

21.1 NTDPSTART ..................................................................................................... 83

21.2 NTDPSTOP ....................................................................................................... 84

22 NTP Messages .................................................................................................. 84

22.1 NTP_LOG .......................................................................................................... 84

22.2 NTP_LOG .......................................................................................................... 84

22.3 NTP_LOG .......................................................................................................... 85

22.4 NTP_LOG .......................................................................................................... 85

22.5 NTP_LOG .......................................................................................................... 85

22.6 NTP_LOG .......................................................................................................... 86

22.7 NTP_LOG .......................................................................................................... 86

23 OADP Messages ............................................................................................... 87

23.1 OADPSTART ..................................................................................................... 87

23.2 OADPSTOP ....................................................................................................... 87

23.3 CDPSTART ....................................................................................................... 87

23.4 CDPSTOP ......................................................................................................... 88

24 PKI Messages ................................................................................................... 88

24.1 Local_Cert_Retrieval ......................................................................................... 88

24.2 Local_Cert_Retrieval ......................................................................................... 88

24.3 CA_Cert_Retrieval ............................................................................................. 89






24.9 Local_Cert_Request .......................................................................................... 91

24.10 Local_Cert_Request .................................................................................... 91

24.11 Local_Cert_Request .................................................................................... 92

24.12 Import_Cert_File .......................................................................................... 92

24.13 Import_Local_Cert ....................................................................................... 92







24.18 Import_Local_Key ........................................................................................ 94

24.19 Import_Local_Key ........................................................................................ 95

24.20 Import_CA_Cert ........................................................................................... 95

24.21 Import_CA_Cert ........................................................................................... 95

24.22 Import_CA_Cert ........................................................................................... 96

24.23 Import_CA_Cert ........................................................................................... 96

24.24 Import_CA_Cert ........................................................................................... 97

24.25 Import_CA_Cert ........................................................................................... 97

24.26 Import_CA_Cert ........................................................................................... 98

24.27 Import_CA_Cert ........................................................................................... 98

24.28 Update_CA_Cert ......................................................................................... 98

24.29 Update_CA_Cert ......................................................................................... 99

24.30 Delete_CA_Cert ........................................................................................... 99

24.31 Delete_CA_Cert ......................................................................................... 100

24.32 Delete_CA_Cert ......................................................................................... 100

24.33 Delete_Local_Cert ..................................................................................... 100

24.34 Delete_Local_Cert ..................................................................................... 101

24.35 Verify_Cert ................................................................................................. 101

24.36 Verify_Cert ................................................................................................. 101

24.37 Verify_CA_Root_Cert ................................................................................ 102

24.38 Verify_CA_Root_Cert ................................................................................ 102

24.39 Retrieval_CRL ........................................................................................... 103

24.40 Retrieval_CRL ........................................................................................... 103

24.41 Update_CRL .............................................................................................. 103

24.42 Update_CRL .............................................................................................. 104

24.43 Update_CRL .............................................................................................. 104

25 RDS Messages ................................................................................................ 104

25.1 LOGIN ............................................................................................................. 105

25.2 LOGIN ............................................................................................................. 105

25.3 LOGIN ............................................................................................................. 106

25.4 LOGIN ............................................................................................................. 106

26 RM Messages .................................................................................................. 107

26.1 RTLOG ............................................................................................................ 107



26.2 RTLOG ............................................................................................................ 107

26.3 RTLOG ............................................................................................................ 107

26.4 RTLOG ............................................................................................................ 108

26.5 RTLOG ............................................................................................................ 108

26.6 RTLOG ............................................................................................................ 109

26.7 RTLOG ............................................................................................................ 109

26.8 RTLOG ............................................................................................................ 109

26.9 RTLOG ............................................................................................................ 110

26.10 RTLOG ...................................................................................................... 110

26.11 RTLOG ...................................................................................................... 111

26.12 RTLOG ...................................................................................................... 111

26.13 RTLOG ...................................................................................................... 112

26.14 RTLOG ...................................................................................................... 112

26.15 RTLOG ...................................................................................................... 113

26.16 RTLOG ...................................................................................................... 113

26.17 RTLOG ...................................................................................................... 113

26.18 RTLOG ...................................................................................................... 114

26.19 RTLOG ...................................................................................................... 114

26.20 RTLOG ...................................................................................................... 115

26.21 RTLOG ...................................................................................................... 115

26.22 RTLOG ...................................................................................................... 115

26.23 RTLOG ...................................................................................................... 116

26.24 RTLOG ...................................................................................................... 116

26.25 RTLOG ...................................................................................................... 116

26.26 RTLOG ...................................................................................................... 117

26.27 RTLOG ...................................................................................................... 117

26.28 RTLOG ...................................................................................................... 118

26.29 RTLOG ...................................................................................................... 118

26.30 RTLOG ...................................................................................................... 118

26.31 RTLOG ...................................................................................................... 119

26.32 RTLOG ...................................................................................................... 119

26.33 RTLOG ...................................................................................................... 120

26.34 RTLOG ...................................................................................................... 120

26.35 RTLOG ...................................................................................................... 120

26.36 RTLOG ...................................................................................................... 121

26.37 RTLOG ...................................................................................................... 121



26.38 RTLOG ...................................................................................................... 121

26.39 RTLOG ...................................................................................................... 122

26.40 RTLOG ...................................................................................................... 122

26.41 RTLOG ...................................................................................................... 123

26.42 RTLOG ...................................................................................................... 123

26.43 RTLOG ...................................................................................................... 123

26.44 RTLOG ...................................................................................................... 124

26.45 RTLOG ...................................................................................................... 124

26.46 RTLOG ...................................................................................................... 124

26.47 RTLOG ...................................................................................................... 125

26.48 RTLOG ...................................................................................................... 125

26.49 RTLOG ...................................................................................................... 126

26.50 RTLOG ...................................................................................................... 126

26.51 RTLOG ...................................................................................................... 126

26.52 RTLOG ...................................................................................................... 127

26.53 RTLOG ...................................................................................................... 127

26.54 RTLOG ...................................................................................................... 127

26.55 RTLOG ...................................................................................................... 128

26.56 RTLOG ...................................................................................................... 128

26.57 RTLOG ...................................................................................................... 129

26.58 RTLOG ...................................................................................................... 129

26.59 RTLOG ...................................................................................................... 130

26.60 RTLOG ...................................................................................................... 130

26.61 RTLOG ...................................................................................................... 131

26.62 RTLOG ...................................................................................................... 131

26.63 RTLOG ...................................................................................................... 131

27 RMON Messages ............................................................................................ 132

27.1 ADDINFO ........................................................................................................ 132

27.2 DELINFO ......................................................................................................... 132

28 RSA Messages ................................................................................................ 133

28.1 Key_create ...................................................................................................... 133

28.2 Key_create ...................................................................................................... 133

28.3 Key_create ...................................................................................................... 134

28.4 Key_create ...................................................................................................... 134

28.5 Key_create ...................................................................................................... 134

28.6 Key_create ...................................................................................................... 135



28.7 Key_create ...................................................................................................... 135

28.8 Key_create ...................................................................................................... 135

28.9 Key_destroy ..................................................................................................... 136

28.10 Key_destroy ............................................................................................... 136

28.11 Key_destroy ............................................................................................... 137

%Jan 1 01:27:05 2003 Quidway RSA/5/ Key_destroy ............................................. 137

28.12 Key_destroy ............................................................................................... 137

28.13 Key_destroy ............................................................................................... 137

28.14 Key_destroy ............................................................................................... 138

28.15 Write_flash ................................................................................................. 138

28.16 Save_keys ................................................................................................. 138

28.17 Save_keys ................................................................................................. 139

28.18 Save_keys ................................................................................................. 139

28.19 Save_keys ................................................................................................. 140

28.20 Read_keys ................................................................................................. 140

28.21 Read_keys ................................................................................................. 140

28.22 Read_keys ................................................................................................. 141

28.23 Backup_Keys ............................................................................................. 141

28.24 Backup_Keys ............................................................................................. 141

29 SHELL Messages ............................................................................................ 142

29.1 LOGIN ............................................................................................................. 142

29.2 LOGOUT ......................................................................................................... 142

29.3 CMD ................................................................................................................ 143

29.4 SYN_ERROR .................................................................................................. 143

29.5 SYN_ERROR .................................................................................................. 144

30 SNMP Messages ............................................................................................. 144

30.1 GET ................................................................................................................. 144

30.2 SET ................................................................................................................. 145

31 SOCKET Messages ........................................................................................ 145

31.1 SOCKETLOG .................................................................................................. 145

31.2 TCP MD5 ......................................................................................................... 146

32 SSH Messages ................................................................................................ 146

32.1 ver_len_err ...................................................................................................... 146

32.2 ver_major_err .................................................................................................. 146

32.3 ver_minor_err .................................................................................................. 147

32.4 ver_minor_unspt .............................................................................................. 147



32.5 buf_len_zero .................................................................................................... 147

32.6 session_msg_err ............................................................................................. 148

32.7 cipher_err ........................................................................................................ 148

32.8 cookie_err ........................................................................................................ 149

32.9 user_msg_err .................................................................................................. 149

32.10 auth_retryt_out ........................................................................................... 149

32.11 auth_msg_err ............................................................................................. 150

32.12 passwd_len_err ......................................................................................... 150

32.13 passwd_err ................................................................................................ 150

32.14 authrsa_msg_err ........................................................................................ 151

32.15 rsarspn_msg_err ........................................................................................ 151

32.16 challenge_err ............................................................................................. 152

32.17 getckey_err ................................................................................................ 152

32.18 username_len_err ...................................................................................... 152

32.19 user_not_exist ........................................................................................... 153

32.20 user_noauth ............................................................................................... 153

32.21 rsa_n_err ................................................................................................... 153

32.22 fsm_move .................................................................................................. 154

32.23 err_dissconnect ......................................................................................... 154

32.24 unexpected_msg ....................................................................................... 155

32.25 bad_cmd_length ........................................................................................ 155

32.26 msg_disconnect ......................................................................................... 155

32.27 bad_plaintext_length .................................................................................. 156

32.28 bad_cryptograph_len ................................................................................. 156

32.29 bad_key_length ......................................................................................... 156

32.30 bad_iv_len ................................................................................................. 157

32.31 bad_string_len ........................................................................................... 157

32.32 bignum_len_wrong .................................................................................... 158

32.33 bignum_not_full ......................................................................................... 158

32.34 unknown_cipher_type ................................................................................ 158

32.35 send_length_wrong ................................................................................... 159

32.36 send_buf_null ............................................................................................ 159

32.37 send_fail .................................................................................................... 159

32.38 msg_length_slop ........................................................................................ 160

32.39 read_length_wrong .................................................................................... 160

32.40 read_crc_wrong ......................................................................................... 160



32.41 user_exist .................................................................................................. 161

32.42 add_success .............................................................................................. 161

32.43 del_success ............................................................................................... 161

32.44 getkey_fail .................................................................................................. 162

32.45 accept_err .................................................................................................. 162

32.46 malloc_err .................................................................................................. 163

32.47 buf_get_wrong ........................................................................................... 163

32.48 des_setkey_fail .......................................................................................... 163

32.49 3des_setkey_fail ........................................................................................ 164

32.50 rsa_decrypt_fail ......................................................................................... 164

32.51 rsa_gethostkey_fail .................................................................................... 164

32.52 rsa_getserverkey_fail ................................................................................. 165

32.53 rsa_encrytp_fail ......................................................................................... 165

32.54 socket_send_fail. ....................................................................................... 166

32.55 no_auth_type ............................................................................................. 166

32.56 get_version_fail .......................................................................................... 166

32.57 rcv_unexpected_msg ................................................................................. 167

32.58 msg_type_illegal ........................................................................................ 167

32.59 msg_tran_close ......................................................................................... 167

32.60 msg_tran_deadloop ................................................................................... 168

32.61 msg_client_exit .......................................................................................... 168

32.62 msg_ssh_vty .............................................................................................. 168

33 VFS Messages ................................................................................................ 169

33.1 VFSLOG .......................................................................................................... 169

34 VLAN Messages .............................................................................................. 170

34.1 DETECT_FORBIDDEN ................................................................................... 170

34.2 DETECT_FORBIDDEN ................................................................................... 170

34.3 BATCH notify ................................................................................................... 170

35 VRRP Messages ............................................................................................. 171

35.1 LogAuthFailed ................................................................................................. 171

35.2 ConfigError ...................................................................................................... 171

35.3 ConfigError ...................................................................................................... 172

35.4 MasterChange ................................................................................................. 173

35.5 RunError .......................................................................................................... 173

35.6 SetDriver.......................................................................................................... 174

35.7 TrapBecomeNewMaster .................................................................................. 174



35.8 TrapAuthFailed ................................................................................................ 175

36 VTY Messages ................................................................................................ 175

36.1 VTY_LOG ........................................................................................................ 175



i Revision History

Every column should be filled

The format of Revision“” is xx.yy. And xx is major version, yy is minor version. The

initial version begins with 0.01.

Revisio

n

Date Author Reason for Change

0.01 2006-02-14 Plat mib First Draft

ii References



Purpose

This document describes all of the system log messages which are supported by

Comware V3 Switch.



Introduction

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

Syslog 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.

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 syslong message format string

Explanation The signification indicated when system sends a syslog message

Trigger Action The action which triggers off system to send a syslog message.For the same

syslog message, there is more than one trigger action possibly.

Example The instance of system log message

Recommended

Action

The action to be done when such system log message occurs

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.



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

① 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 extendability

⑧ 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 of variable fields and the type of information in the fields as follows:

Representation Description



Representation Description

[STRING]/[string] Character string

[IPADDR]/[ipaddr] IP address

[ULONG]/[ulong] Decimal number

[OID]/[oid] Object identifier

[INTEGER]/[integer] Decimal number

[USHORT]/[ushort] Decimal number

[TIMETICK]/[timetick] Time

System Log Message Module List

In this section, all syslog module supported by Comware V3 Switch are listed.

Any action to add, modify, delete and remove must be recorded in Revision History

Module Name column indicates module which system log messages belong to

Count of syslog column indicates the total count of system log messages in moudule

Current state column indicates the state of supporting system log messages.The

possible values as follows:

Full: fully supported

Partial: partially supported

Obsolete: This module is obsoleted and not longer to be supported.

None: This module is not supported.

Module Name Count of syslog Current state

FIB 2 Partial

IP

OADP

RMON 2 Full



Module Name Count of syslog Current state

1 802.1X Messages

This section contains the entire system log messages related to 802.1X.

1.1 DOT1X_LOG

Mnemonic DOT1X_LOG Severity Level 3

Syslog Message [STRING]

Variable Fields $1: the log string

Explanation The authentication of an 802.1x user failed.

Trigger Action Username or password mismatch.

Example %Apr 26 12:07:04:802 2000 Quidway

8021X/3/DOT1X_LOG:Port:11,Auth:0,Authentication failed: 8021X

authentication failed.

Recommended

Action

Input correct username or password.

Is Supported Yes

2 ARP Messages

This section contains the entire system log messages related to ARP.

2.1 DUPIP

Mnemonic DUPIP Severity Level 4

Syslog Message IP address [ipaddr] collision detected, sourced by [STRING] on

[octet] of VLAN[ushort] and [STRING] on [octet] of VLAN[ushort]

Variable Fields $1: IP Address

$2: the first MAC of the same IP Address

$3: the name of the port on which the first MAC exists

$4: VLAN id of the first MAC



$5: the second MAC of the same IP Address

$6: the name of the port on which the second MAC exists

$7: VLAN id of t

Explanation The source IP address collides with the one of existing ARP entry.

Trigger Action When receive ARP packet which has same source IP address and

different source MAC address with existing ARP entry.

Example %Mar 3 16:20:34 2005 Quidway ARP/4/DUPIP:IP address

1.1.1.5 collision detected, sourced by 0100-0300-0500 on

Ethernet0/1 of VLAN1 and 0100-0300-0512 on Ethernet0/2 of

VLAN2

Recommended

Action

No action is required.

Is Supported Yes

2.2 DUPIFIP

Mnemonic DUPIFIP Severity Level 3

Syslog Message Duplicate address [ipaddr] on VLAN[ushort], sourced by [STRING]


$2: the VLAN id of the source MAC

$3: MAC of the same IP Address

Explanation The source IP address collides with the one of local interface.

Trigger Action When receive ARP packet which has same source IP address with

local interface.

Example %Mar 3 16:20:34 2005 Quidway ARP/4/DUPIFIP:Duplicate

address 100.10.10.10 on VLAN1, sourced by 0058-9b3d-3013

Recommended

Action


Is Supported Yes

2.3 DUPVRRPIP

Mnemonic DUPVRRPIP Severity Level 3

Syslog Message IP address [ipaddr] collision with VRRP virtual IP address on

VLAN[ushort], sourced by [STRING]


$2: the name of an interface



$3: MAC of the same IP Address

Explanation The source IP address collides with virtual IP address of VRRP

Trigger Action When receive ARP packet which has same source IP address with

virtual IP address of VRRP.

Example %Mar 3 16:20:34 2005 Quidway ARP/4/DUPIFIP:Duplicate

address 100.10.10.10 on VLAN1, sourced by 0058-9b3d-3013

Recommended

Action


Is Supported Yes

2.4 ARP TABLE FULL

Mnemonic ARP TABLE FULL Severity Level 4

Syslog Message ARP table is full

Variable Fields

Explanation ARP table is full.

Trigger Action When ARP table is full or add new ARP entry after that. The interval

of each LOG should be no less than 30 seconds

Example #Apr 1 23:58:42:038 2000 5500-EI ETH/5/ARP TABLE FULL:- 1 -

ARP table is full

Recommended

Action


Is Supported Yes

3 CFAX Messages

This section contains the entire system log messages related to cfax.

3.1 SENDFAIL

Mnemonic SENDFAIL Severity Level 4

Syslog Message \r\n UNIT [ULONG] : [STRING] send message failed\r\n

Variable Fields $1: Unit ID

$2: send message type

Explanation It indicates that CFAX send message failed

Trigger Action CFAX sending message failed

Example %Mar 3 16:20:34 2005 Quidway cfax/4/SENDFAIL:



UNIT 1 : CFAX UNICAST send message failed

Recommended

Action


Is Supported Yes when XRN is supported

3.2 TIMEOUT

Mnemonic TIMEOUT Severity Level 4

Syslog Message \r\n UNIT [ULONG] : [STRING] message timeout\r\n


$2: send message type

Explanation It indicates that CFAX send message failed because of time out

Trigger Action CFAX sending message failed because of time out

Example %Mar 3 16:20:34 2005 Quidway cfax/4/SENDFAIL:

UNIT 1 : CFAX UNICAST message timeout

Recommended

Action


Is Supported NO

3.3 PROCINFO

Mnemonic PROCINFO Severity Level 4

Syslog Message \r\n UNIT [ULONG] : [STRING] process information\r\n


$2: Event information of CFAX

Explanation It indicates that CFAX receive message and process it

Trigger Action CFAX received message and process information

Example %Mar 3 16:20:34 2005 Quidway cfax/4/PROCINFO:

UNIT 1 : CFAX RECEIVE EVENT process information

Recommended

Action



3.4 WREVFAIL

Mnemonic WREVFAIL Severity Level 4

Syslog Message \r\n UNIT [ULONG] : [STRING] write event failed\r\n





Explanation It indicates that CFAX write event failed

Trigger Action CFAX write event failed

Example %Mar 3 16:20:34 2005 Quidway cfax/4/WREVFAIL:

UNIT 1 : CFAX SET DELETE FLAG write event failed

Recommended

Action



3.5 CFAX_LOGID_WRQUEFAIL

Mnemonic CFAX_LOGID_WRQUEFAIL Severity Level 4

Syslog Message \r\n UNIT [ULONG] : [STRING] write event failed\r\n



Explanation It indicates that CFAX write message queue failed

Trigger Action CFAX write message to queue failed

Example %Mar 3 16:20:34 2005 Quidway

cfax/4/CFAX_LOGID_WRQUEFAIL:

UNIT 1 : CFAX NOTIFY QUEUE write message to queue failed

Recommended

Action



4 CFM Messages

This section contains the entire system log messages related to CFM.

4.1 CFM_LOG

Mnemonic CFM_LOG Severity Level 5


Variable Fields $1: the log string

Explanation Record logs related to CFM

Trigger Action Replace buildrun, get current buildrun, show buildrun or recover

configuration occur errors



Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG: Command

interface ethernet1/0/48 fails to recover configuration.

Recommended

Action


Is Supported Yes

4.2 CFM_LOG


Syslog Message Minimum Unit[ULONG] recover configuration from temporary

configuration file.


Explanation It indicates that minimum unit recovered from temporary

configuration file

Trigger Action Unit with minimum unit id recovered from temporary configuration

file

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Minimum

Unit1 recover configuration from temporary configuration file.

Recommended

Action



4.3 CFM_LOG


Syslog Message Single unit[ULONG] recover configuration from temporary

configuration file.


Explanation It indicates that single unit recovered from temporary configuration

file

Trigger Action Single unit recovered from temporary configuration file

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Single unit1

recover configuration from temporary configuration file.

Recommended

Action





4.4 CFM_LOG


Syslog Message Unit[ULONG] synchronize configuration unsuccessfully.


Explanation It indicates that unit synchronize configuration from minimum unit

failed

Trigger Action Unit synchronize configuration from minimum unit failed

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit2

synchronize configuration unsuccessfully.

Recommended

Action



4.5 CFM_LOG


Syslog Message Unit[ULONG] 's configuration is different from the minimum unit.


Explanation It indicates that unit’s current configuration is different from

minimum unit

Trigger Action When establish fabric, unit’s current configuration is different from

minimum unit

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit2 's

configuration is different from the minimum unit.

Recommended

Action



4.6 CFM_LOG


Syslog Message Unit[ULONG] fail to save configuration.


Explanation It indicates that unit [id] saving failed

Trigger Action When saving configuration in fabric, one of the units save failed for

insufficient space and so on



Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit1 fail to

save configuration.

Recommended

Action



4.7 CFM_LOG


Syslog Message Unit[ULONG]' checksum is different from unit[ULONG]


$2: Unit ID

Explanation It indicates that configurations of units are different

Trigger Action When saving configuration in fabric, current configuration of one

unit is different from another’s

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit2'

checksum is different from unit1.

Recommended

Action



4.8 CFM_LOG


Syslog Message Minimum unit[ULONG] fails to save configuration.


Explanation It indicates that minimum unit saved failed

Trigger Action When saving configuration in fabric, minimum unit saved failed

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Minimum

unit1 fails to save configuration.

Recommended

Action



4.9 CFM_LOG


Syslog Message Unit[ULONG] save configuration successfully.




Explanation It indicates that unit saved successfully

Trigger Action When saving configuration in fabric, unit saved successfully

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit1 save

configuration successfully.

Recommended

Action



4.10 CFM_LOG


Syslog Message Unit[ULONG] erase the configuration unsuccessfully


Explanation It indicates that unit executed “reset saved-configuration” failed

Trigger Action When executing “reset saved-configuration” in fabric, unit [id] failed

to erase configuration file.

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit1 erase

the configuration unsuccessfully.

Recommended

Action


Is Supported NO

4.11 CFM_LOG


Syslog Message Unit[ULONG] erase the configuration successfully.


Explanation It indicates that unit executed “reset saved-configuration”

successfully

Trigger Action When executing “reset saved-configuration” in fabric, unit [id] erase

d configuration file successfully.

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit1 erase

the configuration successfully.

Recommended

Action


Is Supported NO



4.12 CFM_LOG


Syslog Message Calling VOS_Malloc() or VOS_RawMalloc() unsuccessfully.

Variable Fields NULL

Explanation It indicates that malloc memory failed in some cases

Trigger Action Memory malloc failed

Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG:Calling

VOS_Malloc() or VOS_RawMalloc() unsuccessfully.

Recommended

Action


Is Supported NO

4.13 CFM_LOG


Syslog Message Calling CFM_IPC_Send() unsuccessfully.


Explanation It indicates that calling CFM_IPC_Send() failed

Trigger Action Calling CFM_IPC_Send() failed


CFM_IPC_Send() unsuccessfully.

Recommended

Action


Is Supported YES

4.14 CFM_LOG


Syslog Message Calling compress() or uncompress() unsuccessfully.


Explanation It indicates that calling compress() or uncompress() failed

Trigger Action Calling compress() or uncompress()failed


compress() or uncompress() unsuccessfully.

Recommended

Action




Is Supported YES

4.15 CFM_LOG


Syslog Message Get current buildrun info unsuccessfully.


Explanation It indicates that get current configuration failed

Trigger Action Calling CFM_GetCurrentBuildRunInfoEx() to get current

configuration failed

Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG:Get current

buildrun info unsuccessfully.

Recommended

Action


Is Supported YES

4.16 CFM_LOG


Syslog Message Receiving CFM_SYNCCFG_ERR message.


Explanation It indicates that synchronizeconfiguration with minimum unit failed

Trigger Action synchronizeconfiguration with minimum unit failed

Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG:Receiving

CFM_SYNCCFG_ERR message.

Recommended

Action


Is Supported YES when XRN is supported

4.17 CFM_LOG


Syslog Message Synchronizing configuration time out.


Explanation It indicates that synchronizeconfiguration with minimum unit

because of time out

Trigger Action synchronizeconfiguration with minimum unit failed because of time

out



Example %Mar 3 16:20:34 2005 Quidway

CFM/5/CFM_LOG:Synchronizing configuration time out.

Recommended

Action



4.18 CFM_LOG


Syslog Message Save configuration file unsuccessfully.


Explanation It indicates that save configuration file failed

Trigger Action Save configuration file failed

Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG:Save

configuration file unsuccessfully.

Recommended

Action



4.19 CFM_LOG


Syslog Message Create Timer unsuccessfully.


Explanation It indicates that creating timer for synchronizing failed

Trigger Action Creating timer for synchronizing failed

Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG:Create Timer

unsuccessfully.

Recommended

Action



4.20 CFM_LOG


Syslog Message Other error.


Explanation It indicates that synchronizing configuration failed with errors not



listed before

Trigger Action Synchronizing configuration failed

Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG:Other error.

Recommended

Action



4.21 CFM_LOG


Syslog Message Unit[ULONG] CFM reboot the system.


Explanation It indicates that reboot by CFM

Trigger Action Synchronizing needs reboot

Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG:Unit1 CFM

reboot the system.

Recommended

Action



4.22 CFM_LOG


Syslog Message Reject providing configuration to [ULONG], because i'm not

minimum unit or the unit requesting configuration has not been in

fabric.


Explanation It indicates that request for configuration is rejected, for destination

is not minimum unit

Trigger Action Destination of synchronizing request is not minimum unit

Example %Mar 3 16:20:34 2005 Quidway CFM/5/CFM_LOG:Reject

providing configuration to 2, because i'm not minimum unit or the

unit requesting configuration has not been in fabric.

Recommended

Action





4.23 CFM_LOG


Syslog Message Unit[ULONG] 's configuration is same as the minimum unit.


Explanation It indicates that current unit’s configuration is same as minimum

unit

Trigger Action Current unit’s configuration is same as minimum unit

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit2 's

configuration is same as the minimum unit.

Recommended

Action



4.24 CFM_LOG


Syslog Message Unit[ULONG] fail to set configuration.


Explanation It indicates that current unit’s fail to set next start up configuration

file

Trigger Action Current unit’s fail to set next start up configuration file

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit 2 fail to

set configuration.

Recommended

Action



4.25 CFM_LOG


Syslog Message Unit[ULONG] the file does not exist.


Explanation It indicates that current unit’s fail to set next start up configuration

file because specified unit doesn’t exist

Trigger Action Current unit’s fail to set next start up configuration file because

specified unit doesn’t exist

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit1 the file



does not exist.

Recommended

Action



4.26 CFM_LOG


Syslog Message Unit[ULONG] set the configuration successfully.


Explanation It indicates that current unit’s set next start up configuration file

successfully

Trigger Action Current unit’s set next start up configuration file successfully

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit1 set the

configuration successfully.

Recommended

Action



4.27 CFM_LOG


Syslog Message Unit[ULONG] postpone notifying the result of saving configuration.


Explanation It indicates that unit[id] postpone notifying the result of saving

configuration

Trigger Action Unit[id] postpone notifying the result of saving configuration

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Unit1

postpone notifying the result of saving configuration

Recommended

Action



4.28 CFM_LOG


Syslog Message Specified boot file does not exist on current unit.




Explanation It indicates that specified boot system file doesn’t exist on unit [id]

Trigger Action Specified boot system file doesn’t exist on unit [id]

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Specified

boot file does not exist on current unit.

Recommended

Action



4.29 CFM_LOG


Syslog Message Stack can't be created for the local space is not enough to save the

temporary configuration file. Please delete some files and try

it again.


Explanation It indicates that there are not enough space to save temporary

configuration file, so fabric can’t be established.

Trigger Action There are not enough space to save temporary configuration file.

Example %Mar 3 16:20:34 2005 Quidway CFM/3/CFM_LOG:Stack can't

be created for the local space is not enough to save the temporary

configuration file. Please delete some files and try it again.

Recommended

Action



5 CLST Messages

This section contains the entire system log messages related to CLST.

5.1 LOG

Mnemonic LOG Severity Level 4

Syslog Message Member [string]is joined in cluster [string].

Variable Fields $1 Mac Address of member

$2 cluster name

Explanation A member with the $1 number has joined in the cluster $2. (On

command switch)



Trigger Action When A member has joined in the cluster.

Example %Apr 1 23:56:57:366 2000 Quidway CLST/5/LOG:- 1 -

Member 000f-2111-0011 is joined in cluster test.

Recommended

Action


Is Supported Yes

5.2 LOG


Syslog Message Member [string]is joined in stack.


Explanation A member with the $1 number has joined in the stack. (On

command switch)

Trigger Action When A member has joined in the stack.


Member 000f-2111-0011 is joined in stack.

Recommended

Action


Is Supported Yes

5.3 LOG


Syslog Message Member [string]in cluster is rejoined.


Explanation When shakehang error between the command and the member

switch , without delete operation. The member switch can rejoid the

cluster when shakehand recover to usual. (On command switch)

Trigger Action When he member switch rejoid the cluster after shakehand error

for sometime.


Member 000f-2111-0011 in cluster is rejoined.

Recommended

Action


Is Supported Yes



5.4 LOG


Syslog Message Member[string]in cluster is down.


Explanation When the command hasn’t received the member’s shakehand

packet for sometime. The member will think the command is down.

(On command switch)

Trigger Action When the command hasn’t received the member’s shakehand

packet. And the time is long than the holdtime


Member 000f-2111-0011 in cluster is down.

Recommended

Action


Is Supported Yes

5.5 LOG


Syslog Message Switch is joined in cluster [string].

Variable Fields $1 cluster name

Explanation A member is added into cluster. (On member switch)

Trigger Action When a member switch is added into cluster by command switch.


Switch is joined in cluster test.

Recommended

Action


Is Supported Yes

5.6 LOG


Syslog Message Switch is joined in stack.

Variable Fields

Explanation A member is added into a cluster.(On member switch)

Trigger Action When a member is added into a stack by the command switch.


Switch is joined in stack..



Recommended

Action


Is Supported Yes

5.7 LOG


Syslog Message Switch is deleted by cluster [string].


Explanation A member is deleted from cluster. (On member switch)

Trigger Action When a member switch is deleted by command switch.


Switch is deleted by cluster test.

Recommended

Action


Is Supported Yes

5.8 LOG


Syslog Message Switch is deleted by stack.


Explanation A member in stack is deleted.(On member switch)

Trigger Action When a member in stack is deleted by the command switch.


Switch is deleted by stack.

Recommended

Action


Is Supported Yes

5.9 LOG


Syslog Message Cluster administrator is down


Explanation When the member hasn’t received the command’s shakehand

packet for sometime. The member will think the command is down.

(On member switch)



Trigger Action When the member hasn’t received the command’s shakehand

packet. And the time is long than the holdtime


Cluster administrator is down.

Recommended

Action


Is Supported Yes

5.10 LOG


Syslog Message Switch is rejoined in cluster.


Explanation When shakehang error between the command and the member

switch , without delete operation. The member switch can rejoid the

cluster when shakehand recover to usual. (On member switch)

Trigger Action When he member switch rejoid the cluster after shakehand error

for sometime.


Switch is rejoined in cluster.

Recommended

Action


Is Supported Yes

5.11 LOG


Syslog Message "\r\n %u.%u.%u.%u, specify by cluster"

Variable Fields $1$2$3$4 Ip Address of member

Explanation Allocate a private IP address to each member while founding a

cluser

Trigger Action When cluster was founded

Example %Apr 15 23:30:04 2003 3026T CLST/6/LOG:

1.1.1.1, specify by cluster

Recommended

Action


Is Supported Yes



5.12 LOG


Syslog Message "\r\n community string public@cm%d, delete by cluster"

Variable Fields $1 Number of member

Explanation Delete the default configuration of snmp community name which

read-only accessed, when dissolving a cluster

Trigger Action When cluster was dissolved


community string public@cm0, delete by cluster

Recommended

Action


Is Supported Yes

5.13 LOG


Syslog Message "\r\n community string private@cm%d, delete by cluster"


Explanation Delete the default default configuration of snmp community name

which write-only accessed when dissolving a cluster

Trigger Action When cluster was dissolved


community string private@cm0, delete by cluster

Recommended

Action


Is Supported Yes

5.14 LOG


Syslog Message "\r\n community string public, delete by cluster"

Variable Fields

Explanation Delete the default configuration of snmp community name which

read-only accessed when dissolving a cluster or stack

Trigger Action When cluster or stack was dissolved




community string public, delete by cluster

Recommended

Action


Is Supported Yes

5.15 LOG


Syslog Message "\r\n community string private, delete by cluster"

Variable Fields

Explanation Delete the default configuration of snmp community name

which write-only accessed when dissolving a cluster or stack

Trigger Action When cluster or stack was dissolved


community string private, delete by cluster

Recommended

Action


Is Supported Yes

5.16 LOG


Syslog Message "\r\n snmp-agent sys-info version all, specify by cluster"

Variable Fields

Explanation Set system information of the node by default while founding a

cluser

Trigger Action When cluster or stack was founded

Example %Apr 16 14:45:54 2003 stack_0.3026T CLST/6/LOG:

snmp-agent sys-info version all, specify by cluster

Recommended

Action


Is Supported Yes

5.17 LOG


Syslog Message "\r\n community string public@cm%d, specify by cluster"




Explanation Set the configuration of snmp community name which read-only

accessed by default while founding a cluser


Example %Apr 15 23:30:19 2003 aaa_0.3026T CLST/6/LOG:

community string public@cm-2084916772, specify by cluster

Recommended

Action


Is Supported Yes

5.18 LOG


Syslog Message "\r\n community string private@cm%d, specify by cluster"


Explanation Set the configuration of snmp community name which write-only

accessed by default while founding a cluser



community string private@cm-2084916745, specify by cluster

Recommended

Action


Is Supported Yes

5.19 LOG


Syslog Message "\r\n %s, specify by cluster"

Variable Fields $1 Hostname or info-center loghost 1.1.1.1 or Snmp-agent trap

enable standard or Snmp-agent trap source Vlan-interface 1

Explanation Change the name of each member while founding a cluser



hostname 3026T, specify by cluster

Recommended

Action


Is Supported Yes



5.20 LOG


Syslog Message "\r\n community string %s@cm%d, delete by cluster"

Variable Fields $1 community string

$2 Number of member

Explanation The configuration of snmp community name which read-only

accessed configuared on the cluster view is set to each cluster

member while founding a cluser



community string public@cm0, delete by cluster

Recommended

Action


Is Supported Yes

5.21 LOG


Syslog Message "\r\n hostname %s, specify by cluster"

Variable Fields $1 Hostname

Explanation Change the name of each member while founding a cluser



hostname aaa_0.3026T, specify by cluster

Recommended

Action


Is Supported Yes

5.22 LOG


Syslog Message "\r\n super password %s, specify by cluster"

Variable Fields $1 Super password

Explanation After a cluster is founded , Synchronize cluster members and set a

super password


Example %Apr 18 11:03:04 2000 aaa_1.qx2050 CLST/6/LOG:



super password , specify by cluster

Recommended

Action


Is Supported Yes

6 CMD Messages

This section contains the entire system log messages related to CMD.

6.1 REBOOT

Mnemonic REBOOT Severity Level 5

Syslog Message [string]: cancel reboot parameters at [string].

Variable Fields $1: The information of user location

$2: The current date and time

Explanation Users and time that cancel reboot

Trigger Action Cancel reboot

Example %Mar 3 16:20:34 2005 Quidway CMD/5/REBOOT:

vty0(192.168.10.25): cancel reboot parameters at 16:20:34

2005/12/25

Recommended

Action


Is Supported Yes

6.2 REBOOT


Syslog Message \r\n***\r\n*** --- REBOOT IN ONE MINUTE ---\r\n***


Explanation There are 1 minute remained before rebooting

Trigger Action There are 1 minute remained before rebooting


***

*** --- REBOOT IN ONE MINUTE ---

***

Recommended

Action




Is Supported Yes

6.3 REBOOT


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

system clock.


Explanation There are users that change system time, so schedule reboot

parameters become invalid

Trigger Action There are users that change system time


Reboot parameters become invalid because vty0(192.168.10.25)

changed system clock

Recommended

Action


Is Supported Yes

6.4 REBOOT


Syslog Message \r\n[string]: schedule reboot parameters at [string]. And system will

reboot at [string].



$3: system reboot time

Explanation There are users setting schedule reboot, and system will reboot at

scheduled time

Trigger Action There are users setting schedule reboot


vty0(192.168.10.25): schedule reboot parameters at 16:20:34

2005/12/25. And system will reboot at 18:20 2005/12/25.

Recommended

Action


Is Supported Yes

6.5 REBOOT




Syslog Message [string]: cancel reboot regularity parameters at [string].



Explanation There are users canceling regular reboot

Trigger Action There are users canceling regular reboot


vty0(192.168.10.25): cancel reboot regularity parameters at

16:20:34 2005/12/25

Recommended

Action


Is Supported Yes

6.6 REBOOT


Syslog Message [string]: schedule reboot regularity parameters at [string]. And

system will reboot at [string]



$3: system reboot time

Explanation There are users setting regular reboot, and system will regularly

reboot

Trigger Action There are users setting regular reboot


vty0(192.168.10.25): schedule reboot regularity parameters at

16:20:34 2005/12/25. And system will reboot at 18:20 2005/12/25.

Recommended

Action


Is Supported Yes

6.7 REBOOT


Syslog Message Failed to check boot file on unit [string].





reboot. But checking boot file on specifed unit failed

Trigger Action Checking boot file on specifed unit failed


Failed to check boot file on unit 1

Recommended

Action



6.8 REBOOT


Syslog Message Specified boot file does not exist on unit [string].



reboot. But boot file doesn’t exist on specifed unit

Trigger Action Boot file doesn’t exist on specifed unit


Specified boot file does not exist on unit 1

Recommended

Action



7 DHCPS Messages

This section contains the entire system log messages related to DHCPS.

7.1 DHCPS_LOCAL_SERVER

Mnemonic DHCPS_LOCAL_SERVER Severity Level 4

Syslog Message Local DHCP server information: Server IP (detected by DHCP

server) = [IPADDR], DHCP server interface = [STRING]

Source client information: DHCP message type = [STRING], DHCP

client hardware address = [STRING]"

Variable Fields $1: The IP address of detected DHCP server.

$2: The name of DHCP server interface from which the DHCP

packets are received.

$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.

Trigger Action Receive a DHCP packet in which the IP adrress in siaddr field is

different from that detected before.

Example %Oct 12 19:35:27:453 2005 server

DHCPS/4/DHCPS_LOCAL_SERVER:

Local DHCP server information(detect by server):SERVER IP =

11.0.0.1, server in

terface = Vlan-interface11; Source client information: type =

DHCPREQUEST, CHard

Addr = 0000-5e00-4704

Recommended

Action


Is Supported Yes

8 FIB Messages

This section contains the entire system log messages related to FIB.

8.1 log_fib

Mnemonic log_fib Severity Level 5

Syslog Message FIB synchro state: [string] [string]

Variable Fields $1: The time when this message sent to the info center.

$2: The detailed description of this message.

Explanation The synchro state during the FIB’s syncronization on centralized

device with XRN/IRF support.

Trigger Action FIB’s periodical refreshing.

Example %Feb 8 07:26:01:525 2011 Quidway FIB/5/log_fib:

FIB synchro state: 2011/02/08 07:26:01 Begin FIB's periodical

refreshing

Recommended

Action


Is Supported Yes



8.2 log_fib

Mnemonic log_fib Severity Level 5

Syslog Message FIB synchro state: Board [ULONG]: [string] [string]

Variable Fields $1: The number of board.

$2: The time when this message sent to the info center.

$3: The detailed description of this message.

Explanation The synchro state during the FIB’s syncronization on distributed

device.

Trigger Action FIB’s periodical refreshing.

Example %Feb 8 07:26:01:525 2011 Quidway FIB/5/log_fib:

FIB synchro state: Board 1: 2011/02/08 07:26:01 Begin FIB's

periodical refreshing

Recommended

Action


Is Supported No

9 FTP Server Messages

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

9.1 USERIN

Mnemonic USERIN Severity Level 4

Syslog Message User [string]([ipaddr]) login succeeded

Variable Fields $1: The user name of FTP client.

$2: The source IP address of FTP client

Explanation A FTP user has logged in successfully.

Trigger Action FTP server accepts a FTP client request, and user name and

password are correct.

Example %Feb 21 14:27:41:922 2006 Quidway-wvrp FTPS/5/USERIN:User

111(192.168.0.99) login succeeded

Recommended

Action


Is Supported Yes

9.2 USEROUT



Mnemonic USEROUT Severity Level 4

Syslog Message User [string]([ipaddr]) logged out



Explanation A FTP user has logged out.

Trigger Action The user which logged in logs out from FTP server

Example %Feb 21 14:30:24:875 2006 Quidway-wvrp

FTPS/5/USEROUT:User 111(192.168.0.99) logged out

Recommended

Action


Is Supported Yes

9.3 USERIN

Mnemonic USERIN Severity Level 4

Syslog Message User [string]([ipaddr]) login failed



Explanation A FTP user has failed to logged in.

Trigger Action FTP Server accepts a FTP client request, and user name or

password is not correct

Example %Feb 21 14:32:30:672 2006 Quidway-wvrp FTPS/5/USERIN:User

fdfd(192.168.0.99) login failed.

Recommended

Action


Is Supported Yes

9.4 USERFAIL

Mnemonic USERFAIL Severity Level 4

Syslog Message User [string]([ipaddr]) transfer failed



Explanation The FTP client fails to put file to server

Trigger Action Some errors occurr during FTP client put file to server or the space

of disk of FTP server is not enough.

Example %Feb 21 14:40:31:203 2006 Quidway-wvrp

FTPS/5/USERFAIL:User 111(192.168.0.99) transfer failed



Recommended

Action


Is Supported Yes

9.5 REQUEST

Mnemonic REQUEST Severity Level 5

Syslog Message User [string]([ipaddr]) request: [string]



$3: The request command of FTP client to Server

Explanation If FTP server debugging is on, when the user sends request

command to the server, the log info will display.

Trigger Action Switch on the FTP server debugging, the FTP user input some

commands.

Example *0.9652531 Quidway-wvrp FTPS/8/REQUEST:User

111(192.168.0.99) requested: PORT 192,168,0,99,18,162

Recommended

Action


Is Supported Yes

9.6 SENDDATA

Mnemonic SENDDATA Severity Level 5

Syslog Message FTP server send [ULONG] bytes to client [string]([ipaddr])

Variable Fields $1: The file length which is transferred.

$2: The user name of FTP client.


Explanation If FTP server debugging is on, when the user get file successfully,

the log info will display.

Trigger Action Switch on the ftp server debugging, the FTP user gets file

successfully.

Example *0.9929938 Quidway-wvrp FTPS/8/RECVDATA:FTP server

received 16045 byte(s) from client 111(192.168.0.99)

Recommended

Action


Is Supported Yes



9.7 RECVDATA

Mnemonic RECVDATA Severity Level 5

Syslog Message FTP server receive [ULONG] bytes from client [string]([ipaddr])

Variable Fields $1: The file length which is transferred.

$2: The user name of FTP client.


Explanation If FTP server debugging is on, when the user put file successfully,

the log info will display.

Trigger Action Switch on the FTP server debugging, the FTP user put file

successfully.

Example *0.9954781 Quidway-wvrp FTPS/8/SENDDATA:FTP server sent

16045 byte(s) to client 111(192.168.0.99)

Recommended

Action


Is Supported Yes

9.8 RUNERROR

Mnemonic RUNERROR Severity Level 4

Syslog Message \r\nFtp server run error [ULONG] ([string])\r\n

Variable Fields $1: The error code

$2: the error infomation

Explanation Fail to configure socket or get task ID or create queue.

Trigger Action Socket error or fail to apply for system’s source

Example %Feb 21 15:25:05:187 2006 Quidway-wvrp FTPS/5/USERIN: Ftp

server run error -11 get task id fail.

Recommended

Action


Is Supported Yes

9.9 FTPS_LOG

Mnemonic FTPS_LOG Severity Level 4

Syslog Message [string]

Variable Fields $1: the output info

Explanation This is a common print info and output the parameter info.

Trigger Action Switch on the FTP server debugging, the FTP user transfer file.

The light of transferring file will be lighted.



Example %Feb 21 15:31:30:47 2006 Quidway-wvrp FTPS/5/FTPS_LOG:

FTPS: Begin to download, illumine the signal light.

Recommended

Action


Is Supported Yes

10 GARP Messages

This section contains the entire system log messages related to GARP.

10.1 Wrong Protocol Id

Mnemonic Wrong Protocol Id Severity Level 3

Syslog Message The protocol Id is not 0x0001


Explanation The value of protocol Id in GARP packet is invalid

Trigger Action Receive an invalid packet.

Example %Feb 21 08:43:21:187 2006 Quidway GARP/4/Wrong Protocol Id:

The protocol Id is not 0x0001

Recommended

Action


Is Supported Yes

10.2 Wrong message

Mnemonic Wrong message Severity Level 3

Syslog Message The message is wrong

Variable Fields

Explanation The value of attribute type in GARP packet is invalid


Example %Feb 21 08:46:11:187 2006 Quidway GARP/4/ Wrong message:

The message is wrong

Recommended

Action


Is Supported Yes

10.3 Valid Msg



Mnemonic Valid Msg Severity Level 3

Syslog Message The message parsing was successful

Variable Fields

Explanation The message in GARP packet is valid.

Trigger Action Receive a valid packet

Example %Feb 21 08:46:11:187 2006 Quidway GARP/4/ Valid Msg:

The message parsing was successful

Recommended

Action


Is Supported Yes

10.4 Wrong Msg

Mnemonic Wrong Msg Severity Level 3

Syslog Message End of message found. The message parsing was NOT successful

Variable Fields

Explanation The message in GARP packet is invalid.


Example %Feb 21 08:46:11:187 2006 Quidway GARP/4/ Wrong Msg:

End of message found. The message parsing was NOT successful

Recommended

Action


Is Supported Yes

10.5 Wrong Msg Length

Mnemonic Wrong Msg Length Severity Level 3

Syslog Message The message is wrong

Variable Fields

Explanation The value of attribute type in GARP packet is invalid.`


Example %Feb 21 08:46:11:187 2006 Quidway GARP/4/ Wrong Msg

Length:The message is wrong

Recommended

Action


Is Supported Yes



10.6 Wrong attribute

Mnemonic Wrong attribute Severity Level 3

Syslog Message The attribute type is wrong

Variable Fields

Explanation The value of attribute type in GARP packet is invalid.


Example %Feb 21 08:46:11:187 2006 Quidway GARP/4/ Wrong attribute:

The attribute type is wrong

Recommended

Action


Is Supported Yes

10.7 Add Entry To GID Failed

Mnemonic Add Entry To GID Failed Severity Level 3

Syslog Message Add entry to GVRP database failed

Variable Fields

Explanation GVRP database is full

Trigger Action Unknown error

Example %Feb 21 08:46:11:187 2006 Quidway GARP/4/ Add Entry To GID

Failed: Add entry to GVRP database failed

Recommended

Action


Is Supported Yes

10.8 Malloc Failed

Mnemonic Malloc Failed Severity Level 3

Syslog Message Failed to allocate memory

Variable Fields

Explanation System memory is insufficient

Trigger Action System memory is insufficient

Example %Feb 21 08:46:11:187 2006 Quidway GARP/4/ Malloc Failed:

Malloc Failed

Recommended

Action


Is Supported Yes



11 HTTPD Messages

This section contains the entire system log messages related to HTTPD .

11.1 Log

Mnemonic Log Severity Level 4




Trigger Action Disable HTTPD function or enable HTTPD function.

Example %Feb 21 16:02:45:375 2006 Quidway-wvrp HTTPD/5/Log:Stopped

HTTP server.

%Feb 21 16:03:14:641 2006 Quidway-wvrp HTTPD/5/Log:Starting

HTTP server.

Recommended

Action


Is Supported Yes

12 HWCM Messages

This section contains the entire system log messages related to HWCM.

12.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.

Example %Feb 26 05:36:20:876 2006 6502 HWCM/5/EXIT: exit from

configure mode

Recommended

Action


Is Supported Yes



12.2 TRAPLOG Mnemonic TRAPLOG Severity Level 4

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

EventIndex=[integer],CommandSource=[integer],ConfigSource=[in

teger],ConfigDestination=[integer]

Variable Fields $1: OID

$2: Event index

$3: Command source

$4: Configuration source

$5: Configuration destination

Explanation Configuration is changed

Trigger Action Change configuration

Example %Feb 26 06:10:25:780 2006 6502 HWCM/5/TRAPLOG:

1.3.6.1.4.1.2011.10.2.4.2.1 configure changed:

EventIndex=13,CommandSource=1,ConfigSource=3,ConfigDestin

ation=2

Recommended

Action


Is Supported Yes

12.3 CCOPY Mnemonic CCOPY Severity Level 4

Syslog Message \r\n\t configuration copy: OptType=[integer], OptTime=[TIMETICK],

OptState=[integer], OptEndTime=[TIMETICK]

Variable Fields $1: Operation type

$2: Date and time

Explanation Copy configuration

Trigger Action Copy configuration

Example %Feb 26 06:38:24:733 2006 6502 HWCM/5/CCOPY:

configuration copy: OptType=6, OptTime=12,

OptState=2, OptEndTime=10682324

Recommended

Action


Is Supported Yes



13 IP Messages

This section contains the entire system log messages related to IP.

13.1 ReassError

Mnemonic ReassError Severity Level 4

Syslog Message The number of queues of reassemble is MAX!

Variable Fields None

Explanation The number of reassembling queues exceed the maximum(400

currently).

Trigger Action The number of reassembling queues exceeds 400.

Example %Apr 20 12:53:44:436 2006 SW7700 IP/4/ReassError: The

number of queues of reassemble is MAX!

Recommended

Action

This message Indicates that there are so many IP fragments in

the current traffic and the current reassmbling queus is beyond the

device’s specification. No action is required.

Is Supported Router only.

13.2 QueueFull

Mnemonic QueueFull Severity Level 4

Syslog Message The queue of reassemble is full!

Variable Fields None.

Explanation The IP packets in one reassembling queue exceed the

maximum(1000 currently).

Trigger Action The number of IP packets in one reassembling queue exceeds

1000.

Example %Apr 21 06:43:32:843 2006 SW7700 IP/4/QueueFull: The queue

of reassemble is full!

Recommended

Action

Indicate that there are too many IP fragments in one

reassmebling queue, which is beyond the device’s specification. No

action is required.

Is Supported Router only.

13.3 MSG

Mnemonic MSG Severity Level 5



Syslog Message FIB: IPC queue is full


Explanation On distributed devices such as 6500 series, the main board must

syncronize the own FIB to other I/O boards via IPC. This message

will occur when the IPC fails to send the FIB.

Trigger Action The IPC fails to send the FIB of main board.

Example %Apr 21 15:17:58 2006 Quidway S6506R IP/5/MSG: FIB: IPC

queue is full

Recommended

Action

No action is required, may check the reason of sending fail.

Is Supported No

13.4 MSG


Syslog Message FIB: IPC resends : Slot = [ULONG]

Variable Fields $1: Slot/Board number.

Explanation IPC will resend the FIB which is failed to send to the board i last

time.

Trigger Action IPC sending failed.

Example %Apr 21 15:17:58 2006 Quidway S6506R IP/5/MSG: FIB: IPC

resends : Slot = 5

Recommended

Action

No action is required, may check the reason of sending fail.

Is Supported No

13.5 MSG


Syslog Message FIB receives message type unknown


Explanation FIB module received an unkonw message from IPC.

Trigger Action After sending FIB, IPC returned a message to FIB module, but the

message type is out of the types defined previously.

Example %Apr 21 15:17:58 2006 Quidway S6506R IP/5/MSG: FIB receives

message type unknown

Recommended No action is required, may check the IPC’s information.



Action

Is Supported No

13.6 MFC

Mnemonic MFC Severity Level 5

Syslog Message MFC SYNC ERR Slot [ULONG]

Variable Fields

Explanation

Trigger Action

Example

Recommended

Action

Is Supported Not support on all devices use COMWARE V3R2

14 L2INF Messages

This section contains the entire system log messages related to L2INF.

14.1 PORT LINK ST

Mnemonic PORT LINK ST Severity Level 5

Syslog Message [STRING]: is UP

Variable Fields $1:interface

Explanation Port status is change to link-up

Trigger Action Port link status change

Example %Feb 5 05:35:05 2006 Quidway L2INF/2/PORT:

GigabitEthernet1/0/38: is UP

Recommended

Action


Is Supported Yes

14.2 PORT LINK ST


Syslog Message [STRING]: is DOWN


Explanation Port link status change to link-down.



Trigger Action Port link status change


GigabitEthernet1/0/39: is DOWN

Recommended

Action


Is Supported Yes

14.3 VLANIF LINK

Mnemonic VLANIF LINK Severity Level 5

Syslog Message [STRING]: is UP

Variable Fields $1:VLAN interface

Explanation VLAN link status change to link-up.

Trigger Action VLAN link status change


Vlan-interface1: is UP

Recommended

Action


Is Supported Yes

14.4 VLANIF LINK


Syslog Message [STRING]: is DOWN

Variable Fields $1:VLAN interface

Explanation VLAN link status change to link-up.

Trigger Action VLAN link status change


Vlan-interface1: is DOWN

Recommended

Action


Is Supported Yes

14.5 PORT PHY TYP

Mnemonic PORT PHY TYP Severity Level 5

Syslog Message [STRING]: is [STRING]




$2:interface type

Explanation Port physical type

Trigger Action Port physical type change


GigabitEthernet1/0/42: is 10_BASE_T

Recommended

Action


Is Supported Yes

14.6 PORT STATUS

Mnemonic PORT STATUS Severity Level 5

Syslog Message [STRING] has fault


Explanation Port status

Trigger Action This is something wrong with the port.


GigabitEthernet1/0/43: has fault

Recommended

Action


Is Supported Yes

14.7 PORT STATUS

Mnemonic PORT STATUS Severity Level 5

Syslog Message [STRING] becomes normal


Explanation Port status.

Trigger Action Port status is change to normal.


GigabitEthernet1/0/44: becomes normal

Recommended

Action


Is Supported Yes

14.8 PORT LOOPBAC

Mnemonic PORT LOOPBAC Severity Level 5





Explanation Loopback test on port

Trigger Action This is something wrong with loopback test.


GigabitEthernet1/0/39: is DOWN

Recommended

Action


Is Supported Yes

14.9 PORT LOOPBAC





Trigger Action Loopback test on port is successful.


Loopback testing of interface GigabitEthernet1/0/3 is successed!

Recommended

Action


Is Supported Yes

14.10 PORT LOOPBAC





Trigger Action Loopback test on port is failed


Loopback testing of interface GigabitEthernet1/0/3 is failed!

Recommended

Action


Is Supported Yes

14.11 VOICE VLAN A



Mnemonic VOICE VLAN A Severity Level 5

Syslog Message ACL set on port failed !\r\n[STRING]

Variable Fields $1:acl

Explanation Acl set on voice vlan port.

Trigger Action Acl set failed on voice vlan port.


ACL set on port failed !

Recommended

Action


Is Supported Yes

15 LACL Messages

This section contains the entire system log messages related to LACL.

15.1 APPLYERR

Mnemonic APPLYERR Severity Level 1

Syslog Message Applying [STRING] failed!

Variable Fields $1 the acl rule group number and sub rule number

Explanation Applying acl group failed.

Trigger Action Other conditions except existed items, hardware not supporting,

action error, acl error, conflicted action, unavailable resource and

register.

Example %Mar 12 18:06:00 2005 QX-S3050 LACL/2/APPLYERR:Applying

ip-group 3001 rule 115 failed!

Recommended

Action


Is Supported Yes

15.2 APPLYERR


Syslog Message Applying [STRING] failed! Reason: Applying item has existed!


Explanation Applying acl group failed,because the applying item has existed.

Trigger Action The applying item has existed.




ip-group 3001 rule 115 failed! Reason: Applying item has existed!

Recommended

Action


Is Supported Yes

15.3 APPLYERR


Syslog Message Applying [STRING] failed! Reason: Not support!


Explanation Applying acl group failed,because the hardware does not support it

Trigger Action The hardware does not support the applying item.


ip-group 3001 rule 115 failed! Reason: Not supported on this

interface!

Recommended

Action


Is Supported Yes

15.4 APPLYERR


Syslog Message Applying [STRING] failed! Reason: Action error!


Explanation Applying acl group failed,because there is action error.

Trigger Action Action error occurs.


ip-group 3001 rule 115 failed! Reason: Reason: Action error!

Recommended

Action


Is Supported Yes

15.5 APPLYERR


Syslog Message Applying [STRING] failed! Reason: ACL error!




Explanation Applying acl group failed,because there is acl error.

Trigger Action Acl error occurs.


ip-group 3001 rule 115 failed! Reason: ACL error!

Recommended

Action


Is Supported Yes

15.6 APPLYERR


Syslog Message Applying [STRING] failed! Reason: Resource unavailable!


Explanation Applying acl group failed,because resource is unavailable.

Trigger Action Resource is unavailable.


ip-group 3001 rule 115 failed! Reason: Resource unavailable!

Recommended

Action


Is Supported Yes

15.7 APPLYERR


Syslog Message Applying [STRING] failed! Reason: Register unavailable!


Explanation Applying acl group failed,because register is unavailabe.

Trigger Action Register is unavailable.


ip-group 3001 rule 115 failed! Reason: Register unavailable!

Recommended

Action


Is Supported Yes

15.8 APPLYERR


Syslog Message Applying [STRING] failed! Reason: Action conflicts!




Explanation Applying acl group failed,because action conflicts.

Trigger Action Action conflicts.


ip-group 3001 rule 115 failed! Reason: Action conflicts!

Recommended

Action


Is Supported Yes

15.9 DELETEERR

Mnemonic DELETEERR Severity Level 1

Syslog Message Deleting [STRING] failed!


Explanation Deleting acl group failed.

Trigger Action Other conditions except hardware not supporting, action error and

inexistent item.

Example %Mar 12 18:06:00 2005 QX-S3050 LACL/2/DELETEERR:Deleting


Recommended

Action


Is Supported Yes

15.10 DELETEERR


Syslog Message Deleting [STRING] failed! Reason: [STRING]


$2 the reason of failure when apply acl rule

Explanation Deleting acl group failed, because the hardware does not support

it.

Trigger Action The hardware does not support the deleting item.


ip-group 3001 rule 115 failed! Reason: Not supported on this

interface!

Recommended

Action




Is Supported Yes

15.11 DELETEERR


Syslog Message Deleting [STRING] failed! Reason: Action error!


Explanation Deleting acl group failed, because there is action error.



ip-group 3001 rule 115 failed! Reason: Action error!

Recommended

Action


Is Supported Yes

15.12 DELETEERR


Syslog Message Deleting [STRING] failed! Reason: Such item does not exist!


Explanation Deleting acl group failed, because the item does not exist.

Trigger Action The deleting item does not exist.

Example %Mar 12 18:06:00 2005 QX-S3050 LACL/2/DELETEERR:Applying

ip-group 3001 rule 115 failed! Reason: Such item does not exist!

Recommended

Action


Is Supported Yes

15.13 DELETED

Mnemonic DELETED Severity Level 1

Syslog Message [STRING] has been deleted!


Explanation Deleting acl group failed, because it has been deleted.

Trigger Action The deleting item has been deleted.

Example %Mar 12 18:06:00 2005 QX-S3050 LACL/2/DELETED:ip-group

3001 rule 115 has been deleted!

Recommended No action is required.



Action

Is Supported Yes

16 LACP Messages

This section contains the entire system log messages related to LACP

16.1 PartnerNoLacp

Mnemonic PartnerNoLacp Severity Level

Syslog Message LACP is not enabled on the remote end of port [string].

Variable Fields $1: name of port

Explanation A LACP enabled port can't receive LACP message which sent from

the remote end of this port

Trigger Action A port which is set LACP enabled can't receive LACP message.

Example %Jan 1 22:08:31:076 2005 5500G-EI LAGG/3/PartnerNoLacp:- 1

-LACP is not enabled on the remote end of port

GigabitEthernet1/0/1.

Recommended

Action


Is Supported Yes

16.2 AggCreFail

Mnemonic AggCreFail Severity Level

Syslog Message Link aggregation group [ushort] becomes a non-load-sharing

aggregation: hardware doesn't support.

Variable Fields $1: the index of Link aggregation group

Explanation There is not enough hardware resources for load-sharing

aggregation.

Trigger Action There is not enough hardware resources for load-sharing

aggregation.

Example %Jan 1 22:08:31:076 2005 5500G-EI LAGG/3/AggCreFail:- 1

-Link aggregation group 2 becomes a non-load-sharing

aggregation :hardware doesn't support.

Recommended

Action




Is Supported Yes

16.3 AggCreFail

Mnemonic AggCreFail Severity Level

Syslog Message Link aggregation group [ushort] becomes a non-load-sharing

aggregation: creating aggregation failed.

Variable Fields $1: the index of Link aggregation group

Explanation Error occurred when setting a load-sharing aggregation to

hardware.

Trigger Action Error occurred when setting a load-sharing aggregation to

hardware.

Example %Jan 1 22:08:31:076 2005 5500G-EI LAGG/3/AggCreFail:- 1

-Link aggregation group 2 becomes a non-load-sharing

aggregation :creating aggregation failed.

Recommended

Action


Is Supported Yes

17 LQOS Messages

This section contains the entire system log messages related to LQOS

17.1 APPLYERR


Syslog Message [STRING] failed to apply and has been deleted!


Explanation Acl group failed to apply and has been deleted.

Trigger Action Other conditions except existed items,hardware not

supporting,action error,acl error,conflicted action,unavailable

resource and register

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/APPLYERR:ip-group

3001 rule 115 failed to apply and has been deleted!

Recommended

Action


Is Supported Yes



17.2 ADDEXIST

Mnemonic ADDEXIST Severity Level 1

Syslog Message [STRING] failed to apply and has been deleted! Reason: applying

item has existed!


Explanation Acl group failed to apply and has been deleted, because the

applying item has existed.

Trigger Action The applying item has been existed.

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/NOTSUPPORT:

ip-group 3001 rule 115 failed to apply and has been deleted!

Reason: applying item has existed!

Recommended

Action


Is Supported Yes

17.3 NOTSUPPORT

Mnemonic NOTSUPPORT Severity Level 1

Syslog Message [STRING] failed to apply and has been deleted! Reason: not

support!


Explanation Acl group failed to apply and has been deleted,because the

hardware does not support it.

Trigger Action The hardware does not support the applying item.

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/NOTSUPPORT:

ip-group 3001 rule 81 failed to apply and has been deleted!

Reason: not support!

Recommended

Action


Is Supported Yes

17.4 ACTIONERR

Mnemonic ACTIONERR Severity Level 1

Syslog Message [STRING] failed to apply and has been deleted! Reason: action

error!




Explanation Acl group failed to apply and has been deleted,because there is

action error.


Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/ACTIONERR:ip-group

3001 rule 81 failed to apply and has been deleted! Reason: action

error!

Recommended

Action


Is Supported Yes

17.5 ACLERR

Mnemonic ACLERR Severity Level 1

Syslog Message [STRING] failed to apply and has been deleted! Reason: ACL error!


Explanation Acl group failed to apply and has been deleted,because there is acl

error.

Trigger Action Acl error occurs.

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/ACLERR:ip-group

3001 rule 81 failed to apply and has been deleted! Reason: ACL

error!

Recommended

Action


Is Supported Yes

17.6 RESOURCE

Mnemonic RESOURCE Severity Level 1

Syslog Message [STRING] failed to apply and has been deleted! Reason: resource

unavailable!


$2 the reason of failure when apply acl rule for qos

Explanation Acl group failed to apply and has been deleted,because resource is

unavailable.

Trigger Action Resource is unavailable.

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/RESOURCE:ip-group



3001 rule 81 failed to apply and has been deleted! Reason:

resource unavailable!

Recommended

Action


Is Supported Yes

17.7 REGISTER

Mnemonic REGISTER Severity Level 1

Syslog Message [STRING] failed to apply and has been deleted! Reason: register

unavailable!


Explanation Acl group failed to apply and has been deleted,because register is

unavailable.

Trigger Action Register is unavailable.

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/RESOURCE:ip-group

3001 rule 81 failed to apply and has been deleted! Reason: register

unavailable!

Recommended

Action


Is Supported Yes

17.8 CONFLICT

Mnemonic CONFLICT Severity Level 1

Syslog Message [STRING] failed to apply and has been deleted! Reason: action

conflicts!


Explanation Acl group failed to apply and has been deleted,because action

conflicts.

Trigger Action Action conflicts.

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/CONFLICT:ip-group

3001 rule 81 failed to apply and has been deleted! Reason: action

conflicts!

Recommended

Action


Is Supported Yes



17.9 DELERR

Mnemonic DELERR Severity Level 1

Syslog Message deleting [STRING] failed!


Explanation Acl group failed to delete.

Trigger Action Other conditions except inexistent item.

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/DELERR: deleting


Recommended

Action


Is Supported Yes

17.10 NOTEXIST

Mnemonic NOTEXIST Severity Level 1

Syslog Message deleting [STRING] failed! Reason: deleting item does not exist!


Explanation Acl group failed to delete,because the deleting item does not exist.

Trigger Action The deleting item does not exist.

Example %Mar 13 11:35:17 2005 QX-S3050 LQOS/2/NOTEXIST: deleting

ip-group 3001 rule 81 failed! Reason: deleting item does not exist!

Recommended

Action


Is Supported Yes

18 MSDP Messages

18.1 PEER_UPDOWN

Mnemonic PEER_UPDOWN Severity Level 5

Syslog Message [STRING]Start a session with the peer [STRING]

([STRING][STRING])

Variable Fields $1: The index of VRF.

$2: The address of peer.

$3: The filename that shows us the warning is in which file.



$4: The number of the line that shos us the warning comes from

which line in the file.

Explanation After the equipment has done some unexpected operations, it

shows what is wrong with the operation of the equipment.

Trigger Action Do some unexpected operations.

Example %Jan 1 01:37:58 2003 Quidway MSDP/5/PEER_UPDOWN: 0 Start

a session with the peer 10.2.2.2 .(G09862)

Recommended

Action


Is Supported Yes

18.2 PEER_UPDOWN

Mnemonic PEER_UPDOWN Severity Level 5

Syslog Message [STRING]Close a session with the peer [STRING]

([STRING][STRING])









Example %Jan 1 01:37:58 2003 Quidway MSDP/5/PEER_UPDOWN: 0

Close a session with the peer 10.2.2.2 .(G09862)

Recommended

Action


Is Supported Yes

18.3 SA_LIMIT

Mnemonic SA_LIMIT Severity Level 5

Syslog Message [STRING]RP: [STRING], SG Entry: ([STRING], [STRING]),

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.


$5: The max number of the SA-cache.







Example %Jan 1 01:37:58 2003 Quidway MSDP/5/SA_LIMIT: 0 RP:

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


Is Supported Yes

19 MSTP Messages

This section contains the entire system log messages related to MSTP.

19.1 STPSTART

Mnemonic STPSTART Severity Level 2

Syslog Message STP is now enabled on the device

Variable Fields

Explanation STP is now enabled on the device.

Trigger Action Configure the command “STP enable” on system view.

Example %Apr 12 13:50:22 2005 Quidway MSTP/3/STPSTART:

STP is now enabled on the device.

Recommended

Action


Is Supported Yes

19.2 STPSTOP

Mnemonic STPSTOP Severity Level 2

Syslog Message STP is now disabled on the device.



Variable Fields

Explanation The device stops running STP.

Trigger Action Configure the command “STP disable” on system view.

Example %Apr 12 13:50:15 2005 Quidway MSTP/3/STPSTOP:

STP is now disabled on the device.

Recommended

Action


Is Supported Yes

19.3 PFWD

Mnemonic PFWD Severity Level 2

Syslog Message Instance [ULONG]'s [STRING] has been set to forwarding state!

Variable Fields $ 1 Instance Identify

$ 2 Port name

Explanation One port of an instance was set to forwarding.

Trigger Action A port of an instance has been set to forwarding state

Example %Apr 12 13:49:37 2005 Quidway MSTP/3/PFWD:

Instance 0's Ethernet1/1 has been set to forwarding state!

Recommended

Action

Shutdown switch‘s port.

Is Supported No

19.4 PDISC

Mnemonic PDISC Severity Level 2

Syslog Message Instance [ULONG]'s [STRING] has been set to discarding state!


$ 2 Port name

Explanation A port of an instance has been set to discarding state

Trigger Action A port of an instance has been set to discarding state

Example %Apr 12 13:50:04 2005 Quidway MSTP/3/PDISC:

Instance 0's Ethernet1/1 has been set to discarding state!

Recommended

Action

Switch A connect to switch B by two ports, and switch A is root

switch in default state. Shutdown the port whose role is root, then

undo shutdown this port.

Is Supported No



19.5 ROOT

Mnemonic ROOT Severity Level 2

Syslog Message We are not the root switch of the instance [ULONG]!,


Explanation The switch is not the root switch of the instance

Trigger Action Switch receives high priority BPDU

Example %Apr 27 20:29:22:920 2000 QX-S3020TP MSTP/3/ROOT:We are

not the root switch of the instance 0!

Recommended

Action

Switch A connect to switch B by two ports, switch A is root switch in

default state. Configure “Stp root primary” on switch B,then

Configure “Stp root primary” on switch B .,then the log message is

printed on switch B.

Is Supported Yes

19.6 IVBPDU

Mnemonic IVBPDU Severity Level 2

Syslog Message 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.

Example %Apr 27 20:42:39:330 2000 QX-S3020TP MSTP/3/:

BPDU-Protection port Ethernet1/0/4 received BPDU packet!

Recommended

Action


default state. Configure “Stp Bpdu-protection” on switch B,then

Configure “Stp edged-port enable” on switch B ‘s one port .

Is Supported Yes

19.7 RGSUP

Mnemonic RGSUP Severity Level 2

Syslog Message Instance [ULONG]'s ROOT-Protection port [STRING] received

superior message!


$ 2 Interface name

Explanation ROOT-Protection port received superior message.

Trigger Action ROOT-Protection port received superior message.



Example %Apr 27 11:45:32:283 2000 com5 MSTP/3/:Instance0's

ROOT-Protection port Ethernet1/0/2 received superior message!

Recommended

Action


default state. Configure “Stp root-protection” on switch A’s port,

then Configure “Stp root primary” on switch B.

Is Supported Yes

19.8 LGEXP

Mnemonic LGEXP Severity Level 2

Syslog Message Instance [ULONG]'s LOOP-Protection port [STRING] did not

receive message!


$ 2 Port name

Explanation LOOP-Protection port did not receive message.

Trigger Action LOOP-Protection port did not receive message.

Example %Apr 27 20:51:20:84 2000 QX-S3020TP MSTP/3/ Instance

[ULONG]'s LOOP-Protection port [STRING] did not receive

message!

Recommended

Action


default state. Configure “Stp loop-protecton” on switch B’s

port .then configure “stp disable” on switch A’s port.

Is Supported Yes

19.9 UNSUPPORT

Mnemonic UNSUPPORT Severity Level 2

Syslog Message Multiple instances of MSTP is not supported on board [ULONG]!

Variable Fields S1 the index of board

Explanation The board does not support multiple instances

Trigger Action Insert board which does not support multiple instances.

Example %Apr 12 14:36:55 2005 Quidway MSTP/3/UNSUPPORT:

Multiple instances of MSTP is not supported on board 1!

Recommended

Action

Insert a board which does not support multiple instances.

Is Supported Yes

19.10 PSTPDISA



Mnemonic PSTPDISA Severity Level 2

Syslog Message Can not enable STP on Port [STRING] which is VlanVpn-enabled

port!

Variable Fields $1 Interface name

Explanation Can not enable STP for configure conflict

Trigger Action Enale tunnel STP then configure STP enable on one port.

Example %Apr 12 14:36:55 2005 Quidway MSTP/3/PSTPDISA:

Can not enable STP on Port Ethernet1/1 which is

VlanVpn-enabled port!

Recommended

Action

Enale tunneal stp then configure stp enable on one port.

Is Supported Yes

19.11 MIRRORSTPDISA

Mnemonic MIRRORSTPDISA Severity Level 2

Syslog Message Can not enable/disable STP on Port [STRING] which is

monitor-port or reflector-port!

Variable Fields $1 Interface name

Explanation Can not enable/disable STP on Port which is monitor-port or

reflector-port

Trigger Action Can not enable/disable STP on Port which is monitor-port or

reflector-port.

Example %Apr 12 14:36:55 2005 Quidway MSTP/3/ MIRRORSTPDISA:

Can not enable/disable STP on Port Ethernet1/1 which is

monitor-port or reflector-port!

Recommended

Action


Is Supported Yes

19.12 QUEFILL

Mnemonic QUEFILL Severity Level 2

Syslog Message MstpMsgQue is full!

Variable Fields

Explanation MstpMsgQue is full

Trigger Action MstpMsgQue is full



Example %Apr 12 13:50:22 2005 Quidway MSTP/3/QUEFILL:

MstpMsgQue is full!

Recommended

Action


Is Supported Yes

19.13 EVENTERROR

Mnemonic EVENTERROR Severity Level 2

Syslog Message Write message fail !

Variable Fields

Explanation Write message fail

Trigger Action Write message fail

Example %Apr 12 13:50:22 2005 Quidway MSTP/3/EVENTERROR:

Write message fail !

Recommended

Action


default state. Swicth B send legacy format BPDU.configure ‘Stp

compliance dot1s’ on switch A’s port ,then configure ‘Stp compliance

legacy’ on switch A’s port

Is Supported Yes

19.14 AGEDOUT

Mnemonic AGEDOUT Severity Level 2

Syslog Message The stp info of Instance [ULONG]'s [STRING] has aged out!

Variable Fields $1 the index of mstp instance

$2 name of port

Explanation The stp info of a port of an instance has aged out

Trigger Action The stp info of a port of an instance has aged out

Example %Apr 12 14:36:55 2005 Quidway MSTP/3/AGEDOUT:

The stp info of Instance0's Ethernet1/1 has aged out!

Recommended

Action


default state. Swicth B send legacy format BPDU.configure ‘Stp

compliance dot1s’ on switch A’s port ,then configure ‘Stp compliance

legacy’ on switch A’s port

Is Supported Yes

19.15 FORMATERR



Mnemonic FORMATERR Severity Level 2

Syslog Message Port [STRING] received different format of BPDU packets

continually! Shut down it in order to avoid broadcast

Variable Fields $1 name of port

Explanation Port received different format of BPDU packets continually

Trigger Action Port received different format of BPDU packets continually

Example %Apr 12 14:36:55 2005 Quidway MSTP/3/FORMATERR:

Port Ethernet1/1 received different format of BPDU packets

continually! Shut down it in order to avoid broadcast

Recommended

Action

Shut down it in order to avoid broadcast

Is Supported Yes

19.16 FRMTINCMPGUARD

Mnemonic FRMTINCMPGUARD Severity Level 2

Syslog Message Instance [ULONG]'s INCOMPLIANCE-Protection port [STRING]

receive incompliant message!

Variable Fields $1 the index of mstp instance

$2 name of port

Explanation Instance's INCOMPLIANCE-Protection port receive incompliant

message

Trigger Action Instance's INCOMPLIANCE-Protection port receive incompliant

message

Example %Apr 12 14:36:55 2005 Quidway MSTP/3/FRMTINCMPGUARD:

Instance's INCOMPLIANCE-Protection port Ethernet1/1 receive

incompliant message!

Recommended

Action


Is Supported Yes

20 NDP Messages

20.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.

Example %Apr 27 16:35:47:200 2000 Quidway NDP/3/NDPSTART:The device

starts running NDP now.

Recommended

Action


Is Supported Yes

20.2 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.

Example %Apr 27 16:35:26:500 2000 Quidway NDP/3/NDPSTOP:The device

stops running NDP now.

Recommended

Action


Is Supported Yes

21 NTDP Messages

21.1 NTDPSTART

Mnemonic NTDPSTART Severity Level 3

Syslog Message The device starts running NTDP now.

Variable Fields

Explanation The NTDP is enable.

Trigger Action When The NTDP status is from disable to enable.

Example %Apr 27 16:33:36:121 2000 Quidway NTDP/3/NTDPSTART:The

device starts running NTDP now.

Recommended

Action


Is Supported Yes



21.2 NTDPSTOP

Mnemonic NTDPSTOP Severity Level 5

Syslog Message The device stops running NTDP now.

Variable Fields

Explanation The NTDP is disable.

Trigger Action When The NTDP status is from enable to disable.

Example %Apr 27 16:32:19:334 2000 Quidway NTDP/3/NTDPSTOP:The

device stops running NTDP now.

Recommended

Action


Is Supported Yes

22 NTP Messages

This section contains the entire system log messages related to NTP.

22.1 NTP_LOG

Mnemonic NTP_LOG Severity Level 4


Variable Fields $1: the output information

Explanation system.leap = 0 means no warning

Trigger Action System Clock was synchronized

Example %Jan 5 02:35:41:346 2003 Quidway NTP/5/NTP_LOG:

System leap changes from 3 to 0 after clock update.

Recommended

Action


Is Supported Yes

22.2 NTP_LOG




Explanation the changing of System stratum.

Trigger Action System Clock was synchronized




System stratum changes from 16 to 2 after clock update.

Recommended

Action


Is Supported Yes

22.3 NTP_LOG




Explanation the max number of configed authkeys is 1024 in the system

Trigger Action the number of configed authkeys exceed 1024


Too many authkeys.

Recommended

Action


Is Supported Yes

22.4 NTP_LOG




Explanation the error happens when ntp get system time

Trigger Action system clock error


In step systime process,the function GetSystemTime fails.

Recommended

Action


Is Supported Yes

22.5 NTP_LOG




Explanation the fail of setting system clock



Trigger Action the time of setting system clock is more early than 2000


In step systime process,the function SetSystemTime fails.

Recommended

Action


Is Supported Yes

22.6 NTP_LOG




Explanation the number of NTP associations must less than 128

Trigger Action the number of NTP associations must more than 128


Too many peers!

Recommended

Action


Is Supported Yes

22.7 NTP_LOG




Explanation System unsynchronized

Trigger Action can not connect the NTP server


System synchronization source lost!

Recommended

Action


Is Supported Yes



23 OADP Messages

This section contains the entire system log messages related to OADP.

23.1 OADPSTART

Mnemonic OADPSTART Severity Level 3

Syslog Message The device starts running OADP now.


Explanation Indicate that OADP is enabled correctly and going to run on device.

Trigger Action User input oadp enable command string at system view.

Example %Apr 20 10:53:21:577 2006 SW7700 OADP/3/OADPSTART:- 1 -

The device starts running OADP now

Recommended

Action


Is Supported Only support s5600 series for NEC.

23.2 OADPSTOP

Mnemonic OADPSTOP Severity Level 3

Syslog Message The device stops running OADP now


Explanation Indicate that OADP is disabled correctly.

Trigger Action User input undo oadp enable command string at system view.

Example %Jan 1 01:37:58 2003 Quidway RMON/6/DELINFO:Alarm table

is invalidated a row with index 15 by cl.

Recommended

Action



23.3 CDPSTART

Mnemonic CDPSTART Severity Level 3

Syslog Message The device starts running CDP now.


Explanation Indicate that CDP is enabled correctly and going to run on device.

Trigger Action User input cdp enable command string at system view.

Example %Apr 20 10:54:03:858 2006 SW7700 OADP/3/CDPSTART:- 1 -



The device starts running CDP now.

Recommended

Action



23.4 CDPSTOP

Mnemonic CDPSTOP Severity Level 3

Syslog Message The device stops running CDP now.


Explanation Indicate that CDP is disabled correctly.

Trigger Action User input undo cdp enable command string at system view.

Example %Apr 20 10:54:14:749 2006 SW7700 OADP/3/CDPSTOP:- 1 - The

device stops running CDP now.

Recommended

Action



24 PKI Messages

This section contains the entire system log messages related to PKI.

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/

Local_Cert_Retrieval:Retrieval local certificate of the domain

ar29pki successfully.

Recommended

Action


Is Supported Yes

24.2 Local_Cert_Retrieval



Mnemonic Local_Cert_Retrieval Severity Level 4

Syslog Message Fail to retrieval local certificate of the domain [String].


Explanation Fail to retrieve the local certificate.

Trigger Action Fail to retrieve the local certificate.


Local_Cert_Retrieval:Fail to retrieval local certificate of the domain

ar29pki.

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ CA_Cert_Retrieval:

Retrieval CA certificates of the domain ar29pki successfully.

Recommended

Action


Is Supported Yes



Syslog Message Fail to retrieval CA certificates of the domain [String].


Explanation Fail to retrieve CA certificates.

Trigger Action Fail to retrieve CA certificates.


Fail to retrieval CA certificates of the domain ar29pki.

Recommended

Action




Is Supported Yes



Syslog Message CA certificates of the domain [String] have been existed.


Explanation CA certificates of this domain have been existed.

Trigger Action CA certificates of this domain have been existed.


CA certificates of the domain ar29pki have been existed.

Recommended

Action


Is Supported Yes



Syslog Message CA certificates of the domain [String] error.


Explanation There are errors in CA certificates.

Trigger Action There are errors in CA certificates.


CA certificates of the domain ar29pki error.

Recommended

Action


Is Supported Yes



Syslog Message No root certificate of the domain [String].


Explanation There is not root certificate of this domain.

Trigger Action There is not root certificate of this domain.


No root certificate of the domain ar29pki.



Recommended

Action


Is Supported Yes



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.


Root certificate of the domain ar29pki error.

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Local_Cert_Request:

Request local certificate of the domain ar29pki successfully.

Recommended

Action


Is Supported Yes



Syslog Message Fail to request local certificate of the domain [String].


Explanation Fail to request local certificate of this domain.

Trigger Action Fail to request local certificate of this domain.




Fail to request local certificate of the domain ar29pki.

Recommended

Action


Is Supported Yes



Syslog Message Local certificate of the domain [String] has been existed.


Explanation Local certificate of this domain has been existed.

Trigger Action Local certificate of this domain has been existed.


Local certificate of the domain ar29pki has been existed.

Recommended

Action


Is Supported Yes

24.12 Import_Cert_File

Mnemonic Import_Cert_File Severity Level 4

Syslog Message Fail to import certificate file of the domain [String].


Explanation Fail to import CA certificates of this domain.

Trigger Action Fail to import CA certificates of this domain.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Import_Cert_File:

Fail to import certificate file of the domain ar29pki.

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Import_Local_Cert:

Import local certificate of the domain ar29pki successfully.

Recommended

Action


Is Supported Yes



Syslog Message Fail to import local certificate of the domain [String].


Explanation Fail to import local certificate of this domain.

Trigger Action Fail to import local certificate of this domain.


Fail to import local certificate of the domain ar29pki.

Recommended

Action


Is Supported Yes



Syslog Message Fail to import local certificate of the domain [String] because of BIO

malloc fail.


Explanation Fail to import local certificate of this domain because of BIO malloc

fail.

Trigger Action Fail to import local certificate of this domain because of BIO malloc

fail.


Fail to import local certificate of the domain ar29pki because of BIO

malloc fail.

Recommended

Action




Is Supported Yes



Syslog Message Fail to import domain [String] local certificate, no certificate in file.


Explanation Fail to import this domain’s local certificate for no certificate in file.

Trigger Action Fail to import this domain’s local certificate for no certificate in file.


Fail to import domain ar29pki local certificate, no certificate in file.

Recommended

Action


Is Supported Yes



Syslog Message Certificate and entity do not match.


Explanation Certificate and entity do not match.

Trigger Action Certificate and entity do not match.


Certificate and entity do not match.

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Import_Local_Key:

Import local private key of the domain ar29pki successfully.



Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Import_Local_Key:

Failed to import local private key of the domain ar29pki.

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Import_CA_Cert:

Import CA certificates of the domain ar29pki successfully.

Recommended

Action


Is Supported Yes



Syslog Message Fail to import CA certificates of the domain [String].


Explanation Fail to import CA certificates of this domain.



Trigger Action Fail to import CA certificates of this domain.


Fail to import CA certificates of the domain ar29pki.

Recommended

Action


Is Supported Yes



Syslog Message Fail to import CA certificates of the domain [String] because of

malloc fail.


Explanation Fail to import CA certificates of this domain because of memory

allocation failure.

Trigger Action Fail to import CA certificates of this domain because of memory

allocation failure.


Fail to import CA certificates of the domain ar29pki because of

malloc fail.

Recommended

Action


Is Supported Yes




password fail.


Explanation Fail to import CA certificates of this domain because of password

failure.

Trigger Action Fail to import CA certificates of this domain because of password

failure.



password fail.



Recommended

Action


Is Supported Yes




parse fail.


Explanation Fail to import CA certificates of this domain because of parse

failure.

Trigger Action Fail to import CA certificates of this domain because of parse

failure.



parse fail.

Recommended

Action


Is Supported Yes



Syslog Message Fail to import CA certificates of the domain [String] because of no

root certificate.


Explanation Fail to import CA certificates of this domain because of no root

certificate.

Trigger Action Fail to import CA certificates of this domain because of no root

certificate.


Fail to import CA certificates of the domain ar29pki because of No

root certificate.

Recommended

Action


Is Supported Yes





Syslog Message Fail to import CA certificates of the domain [String] because of root

certificate error.


Explanation Fail to import CA certificates of this domain because of root

certificate error.

Trigger Action Fail to import CA certificates of this domain because of root

certificate error.


Fail to import CA certificates of the domain ar29pki because of root

certificate error.

Recommended

Action


Is Supported Yes




certficate chain error.


Explanation Fail to import CA certificates of this domain because of certficate

chain error.

Trigger Action Fail to import CA certificates of this domain because of certficate

chain error.



certficate chain error.

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Update_CA_Cert:

Update CA certificates of the Domain ar29pki successfully.

Recommended

Action


Is Supported Yes

24.29 Update_CA_Cert

Mnemonic Update_CA_Cert Severity Level 4

Syslog Message Fail to update CA certificates of the domain [String].


Explanation Fail to update CA certificates of this domain.

Trigger Action Fail to update CA certificates of this domain.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Update_CA_Cert:

Fail to update CA certificates of the domain ar29pki.

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Delete_CA_Cert:

Delete CA certificates of the domain ar29pki successfully.

Recommended

Action



2006-02-15 Copyright by Huawei 3Com, disclosure is forbidden Page100, Total

176

Is Supported Yes



Syslog Message Fail to delete CA certificates of the domain [String].


Explanation Fail to delete CA certificates of this domain.

Trigger Action Fail to delete CA certificates of this domain.


Fail to delete CA certificates of the domain ar29pki.

Recommended

Action


Is Supported Yes



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.


CA certificate of the domain ar29pki is not exist.

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Delete_Local_Cert:



176

Delete local certificate of the domain ar29pki successfully.

Recommended

Action


Is Supported Yes

24.34 Delete_Local_Cert

Mnemonic Delete_Local_Cert Severity Level 4

Syslog Message Fail to delete local certificate of the domain [String].


Explanation Fail to delete local certificate of this domain.

Trigger Action Fail to delete local certificate of this domain.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Delete_Local_Cert:

Fail to delete local certificate of the domain ar29pki.

Recommended

Action


Is Supported Yes

24.35 Verify_Cert

Mnemonic Verify_Cert Severity Level 4

Syslog Message Verify certificate [String] of the domain [String] successfully.

Variable Fields $1: The subject name of certificate

$2: The name of PKI domain

Explanation Verify certificate of this domain successfully.

Trigger Action Verify certificate of this domain successfully.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Verify_Cert:

Verify certificate cn=kkk, o = h3, cn=cn of the domain ar29pki

successfully.

Recommended

Action


Is Supported Yes

24.36 Verify_Cert

Mnemonic Verify_Cert Severity Level 4



176

Syslog Message Fail to verify certificate [String] of the domain [String].

Variable Fields $1: The subject name of certificate

$2: The name of PKI domain

Explanation Fail to verify certificate of the domain.

Trigger Action Fail to verify certificate of the domain.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Verify_Cert:

Fail to verify certificate cn=kkk, o = h3, cn=cn of the domain

ar29pki.

Recommended

Action


Is Supported Yes

24.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.


Verify_CA_Root_Cert: CA root certificate of the domain ar29pki is

trusted.

Recommended

Action


Is Supported Yes

24.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.


Verify_CA_Root_Cert: CA root certificate of the domain ar29pki is

not trusted.



176

Recommended

Action


Is Supported Yes

24.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.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Retrieval_CRL:

Retrieval CRL of the domain ar29pki successfully.

Recommended

Action


Is Supported Yes

24.40 Retrieval_CRL

Mnemonic Retrieval_CRL Severity Level 4

Syslog Message Fail to retrieval CRL of the domain [String].


Explanation Fail to retrieve CRL of this domain.

Trigger Action Fail to retrieve CRL of this domain.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Retrieval_CRL: Fail

to retrieval CRL of the domain ar29pki.

Recommended

Action


Is Supported Yes

24.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.



176

Trigger Action Update CRL of this domain successfully.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Update_CRL: Update

CRL of the domain ar29pki successfully.

Recommended

Action


Is Supported Yes

24.42 Update_CRL


Syslog Message Fail to update CRL of the domain [String].


Explanation Fail to update CRL of this domain.

Trigger Action Fail to update CRL of this domain.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Update_CRL: Fail to

update CRL of the domain ar29pki.

Recommended

Action


Is Supported Yes

24.43 Update_CRL


Syslog Message Update crl of the domain [String] failure.


Explanation Fail to update CRL of this domain.

Trigger Action Fail to update CRL of this domain.

Example %Jan 5 16:13:13:120 2006 AR29-41 PKI/5/ Update_CRL: Update

crl of the domain ar29pki failure.

Is Supported Yes

25 RDS Messages

This section contains the entire system log messages related to RDS.



176

25.1 LOGIN

Mnemonic LOGIN Severity Level 6

Syslog Message [STRING] from Port=[STRING] Vlan=[ULONG] MAC=[STRING]

IP=[IPADDR] sent authentication request

Variable Fields $1: The user name

$2: The port number

$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

Example %2005/1/5 06:31:15:345 5500G-EI SHELL/5/LOGIN:- 1 – test

from(192.168.44.1) sent authentication request

Recommended

Action


Is Supported Yes

25.2 LOGIN



IP=[IPADDR] failed to be online for [STRING]


$2: The port number

$3: The VLAN ID

$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


from(192.168.44.1) failed to be online for timeout.

Recommended

Action


Is Supported Yes



176

25.3 LOGIN



IP=[IPADDR] succeeded to be online


$2: The port number

$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.


from(192.168.44.1) succeeded to be online.

Recommended

Action


Is Supported Yes

25.4 LOGIN



IP=[IPADDR] quit for [STRING]


$2: The port number

$3: The VLAN ID

$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


from(192.168.44.1) quit for timeout.

Recommended

Action




176

Is Supported Yes

26 RM Messages

This section contains the entire system log messages related to RM.

26.1 RTLOG

Mnemonic RTLOG Severity Level 1

Syslog Message Failed to create RTPRO CMO queue.

Variable Fields

Explanation Failed to create RTPRO CMO queue.

Trigger Action Route mengment con’t create RTPRO CMO queue.

Example %Jan 1 01:27:05 2003 Quidway RM/1/RTLOG: Failed to create

RTPRO CMO queue.

Recommended

Action


Is Supported Yes

26.2 RTLOG


Syslog Message Unknown CMO message [ULONG] received.

Variable Fields $1:the value of OID

Explanation Unknown CMO message

Trigger Action RM detect unknown CMO message

Example %Apr 8 03:35:18:289 2006 Quidway RM/1/RTLOG: Unknown

CMO message 1078 received.

Recommended

Action


Is Supported Yes

26.3 RTLOG


Syslog Message Failed to create RTPRO CMO response message.



176

Variable Fields

Explanation Failed to create RTPRO CMO response message.

Trigger Action Failed to create RTPRO CMO response message.

Example %Apr 8 03:35:18:289 2006 Quidway RM/1/RTLOG: Failed to

create RTPRO CMO response message.

Recommended

Action


Is Supported Yes

26.4 RTLOG


Syslog Message rtpro malloc: Can not allocate([ULONG] bytes) for [STRING]

Variable Fields $1:the size of allocated memory

$2:the task name

Explanation Fail to allocate memory

Trigger Action RM Can not allocate memory for some bytes.

Example %Apr 8 03:35:18:289 2006 Quidway RM/3/RTLOG: Can not

allocate(512 bytes) for BGP

Recommended

Action


Is Supported Yes

26.5 RTLOG


Syslog Message inet_init: Invalid martian entry at [STRING]/[STRING]

Variable Fields $1:the destation of martian entry

$2:the mask of martian entry

Explanation Invalid martian entry

Trigger Action Invalid martian entry

Example %Apr 8 03:35:18:289 2006 Quidway RM/5/RTLOG: inet_init:

Invalid martian entry at 1.1.1.0/24

Recommended

Action


Is Supported Yes



176

26.6 RTLOG


Syslog Message task_addr_local return [LONG]

Variable Fields $1:the rerurn value

Explanation When setting local socket address, ask_addr_local reutn one cost.

Trigger Action Set local socket address.

Example %Jan 10 03:31:45:351 2006 Quidway RM/5/RTLOG:

task_addr_local return 3.

Recommended

Action


Is Supported Yes

26.7 RTLOG


Syslog Message Que is full!

Variable Fields

Explanation Queen is full.

Trigger Action Queen is full


Que is full!

Recommended

Action


Is Supported Yes

26.8 RTLOG


Syslog Message rt_free:[STRING]/[ULONG] ([STRING])

Variable Fields $1:the string of log information by the ip address of the dest.

$2: the mask length

$3:the vrf name

Explanation free

Trigger Action Delete one route entry.



176


rt_free:1.1.1.1/32(vpna)

Recommended

Action


Is Supported Yes

26.9 RTLOG


Syslog Message rt_table:[STRING]. The number of routes has exceeded the

configured route limit!

Variable Fields $1:the vrf name

Explanation The number of routes has exceeded the configured route limit.

Trigger Action The number of routes has exceeded the configured route limit


rt_table:[vpnb]. The number of routes has exceeded the

configured route limit!

Recommended

Action


Is Supported Yes

26.10 RTLOG


Syslog Message rt_table:[STRING], its routes are over the configured

threshold_routes, but are still less than the max volume ! Still

adding routes into the table.


Explanation The vrf’s its routes are over the configured threshold_routes, but

are still less than the max volume. RM still add routes into the table.

Trigger Action The vrf’s its routes are over the configured threshold_routes, but

are still less than the max volume.


rt_table:vpn1, its routes are over the configured

threshold_routes, but are still less than the max volume !

Still adding routes into the table.



176

Recommended

Action


Is Supported Yes

26.11 RTLOG


Syslog Message rt_table:[STRING], its routes are over the configured max

volume ! Not adding routes into the table.


Explanation Its routes are over the configured max volume ! Not adding routes

into the table.

Trigger Action its routes are over the configured max volume !


rt_table:vpn2, its routes are over the configured max volume !

Not adding routes into the table.

Recommended

Action


Is Supported Yes

26.12 RTLOG


Syslog Message bgp [STRING] peer update(default_route): send msg error, error

code [LONG]

Variable Fields $1:the string of log information by bgp-peer name

$2: the error code

Explanation BGP finds an error

Trigger Action BGP peer is shutdown


bgp BGP_200 peer update(default_route): send msg error, error

code 5.

Recommended

Action


Is Supported No



176

26.13 RTLOG


Syslog Message Bgp [STRING] send notify code: [ULONG] subcode: [ULONG]


$2: the error code

$3:the sub error code

Explanation BGP finds an error

Trigger Action BGP peer is shutdown


Bgp BGP_100 send notify code: 3 subcode: 2

Recommended

Action


Is Supported No

26.14 RTLOG


Syslog Message bgp peer [STRING] peer AS [ULONG]: AddRouts: [ULONG]

DelRouts: [ULONG]

TotalAddRouts: [ULONG] TotalDelRouts: [ULONG] InputUpdates:

[ULONG]


$2:the AS number

$3:the number of added routes

$4:the number of deleted routes

$5:the total number of added routes

$6:the total number of deleted routes

$7:the number of input-updated routes

Explanation Count the received BGP routers

Trigger Action NULL


bgp peer BGP_100 peer AS 200: AddRouts: 32

DelRouts: 10

TotalAddRouts: 40

TotalDelRouts: 20



176

InputUpdates: 50

Recommended

Action


Is Supported No

26.15 RTLOG


Syslog Message bnp [STRING] read msg socket return: [LONG]


$2:the return value

Explanation BGP read the msg sochet

Trigger Action Deal with the massage


bnp BGP_100 read msg socket return: -1

Recommended

Action


Is Supported No

26.16 RTLOG


Syslog Message bgp_read_message


Explanation BGP read a message.

Trigger Action BGP receive a message.


bgp_read_message

Recommended

Action


Is Supported No

26.17 RTLOG


Syslog Message bgp recv notify msg from bgp peer [STRING]




176

Explanation BGP receive notify message form bgp-peer.

Trigger Action BGP receive notify message.


bgp recv notify msg from bgp peer BGP_100

Recommended

Action


Is Supported No

26.18 RTLOG


Syslog Message bgp: peer [STRING]: received short version [LONG] message


$2:the version of the BGP

Explanation BGP received short someone version message

Trigger Action BGP receive a message.


bgp: peer BGP_100: received short version 3 message

Recommended

Action


Is Supported No

26.19 RTLOG


Syslog Message bgp: peer [STRING] receive invalid multi-protocol capability length


Explanation BGP received invalid multi-protocol capability length.

Trigger Action Connect again.


bgp: peer BGP_100 receive invalid multi-protocol capability

length

Recommended

Action


Is Supported No



176

26.20 RTLOG


Syslog Message bgp [STRING] receive invalid route refresh cap len


Explanation BGP received invalid route refresh cap length.

Trigger Action NULL


bgp BGP_100 receive invalid route refresh cap len

Recommended

Action


Is Supported No

26.21 RTLOG


Syslog Message bgp_get_open

Variable Fields

Explanation BGP_gets_open massage.

Trigger Action BGP will deal with the massage.


bgp_get_open

Recommended

Action


Is Supported No

26.22 RTLOG


Syslog Message bgp [STRING] get_open


Explanation BGP_gets_open massage.



bgp BGP_100 get_open



176

Recommended

Action


Is Supported No

26.23 RTLOG


Syslog Message bgp [STRING] recv_open


Explanation BGP_received_open massage.



bgp BGP_100 recv_open

Recommended

Action


Is Supported No

26.24 RTLOG


Syslog Message bgp [STRING] recv_open: local version < recved version


Explanation BGP received_an open massage: local version < recved version



bgp BGP_101 recv_open: local version < recved version

Recommended

Action


Is Supported No

26.25 RTLOG


Syslog Message bgp [STRING] send keepalive failed, send msg socket

return:[LONG]



176


$2:the return value

Explanation BGP failed to send keepalive message.

Trigger Action BGP failed to send keepalive message.


bgp BGP_100 send keepalive failed, send msg socket return:0

Recommended

Action


Is Supported No

26.26 RTLOG


Syslog Message bgp_recv_open: peer [STRING] accepted mismatched version: his

[LONG] mine [LONG]


$2:the version of the bgp-peer.

$3:the version of the location

Explanation BGP received an open massage.



bgp_recv_open: peer BGP_100 accepted mismatched version:

his 4 mine 3

Recommended

Action


Is Supported No

26.27 RTLOG


Syslog Message bgp_pp_recv: connection collision close the bpp


Explanation BGP’s connection is close.

Trigger Action Reconnect again




176

bgp_pp_recv: connection collision close the bpp

Recommended

Action


Is Supported No

26.28 RTLOG


Syslog Message bgp_pp_recv

Variable Fields

Explanation BGP pp received function is called

Trigger Action Deal with this process.


bgp_pp_recv

Recommended

Action


Is Supported No

26.29 RTLOG


Syslog Message bgp [STRING] recv error refresh


Explanation BGP receive error refresh message.

Trigger Action BGP receive error refresh message.


bgp BGP_100 recv error refresh

Recommended

Action


Is Supported No

26.30 RTLOG


Syslog Message bgp [STRING] sending withdraw routes failed when responding to

route refresh, socket return: [LONG]




176

$2:the return value

Explanation BGP failed to send withdraw routes when responding to route

refresh.

Trigger Action BGP failed to send withdraw routes.


bgp BGP_100 sending withdraw routes failed when responding

to route refresh, socket return: 2

Recommended

Action


Is Supported No

26.31 RTLOG


Syslog Message bgp cfg confederation nonstandard-compatible

Variable Fields

Explanation BGP configures confederation nonstandard-compatible

Trigger Action NULL


bgp cfg confederation nonstandard-compatible

Recommended

Action


Is Supported No

26.32 RTLOG


Syslog Message bgp cfg confed id

Variable Fields

Explanation BGP configured the confed id

Trigger Action NULL


bgp cfg confed id

Recommended

Action


Is Supported No



176

26.33 RTLOG


Syslog Message bgp cfg confed peers

Variable Fields

Explanation BGP configured the confed peers

Trigger Action NULL


bgp cfg confed peers

Recommended

Action


Is Supported No

26.34 RTLOG


Syslog Message bgp cfg peer group(ASSIGNING MEMBERS)

Variable Fields

Explanation BGP configured the peer group(ASSIGNING MEMBERS)

Trigger Action NULL


bgp cfg peer group(ASSIGNING MEMBERS)

Recommended

Action


Is Supported No

26.35 RTLOG


Syslog Message bgp cfg neighbor route-reflector-client

Variable Fields

Explanation BGP configured the neighbor route-reflector-client

Trigger Action NULL


bgp cfg neighbor route-reflector-client




176

Action

Is Supported No

26.36 RTLOG


Syslog Message Vpnbgp [STRING] send routes failed, socket return: [LONG]


$2:the return value

Explanation Vpnbgp failed to send routes message.

Trigger Action Vpnbgp failed to send routes message.


Vpnbgp BGP_VPN_INS_100 send routes failed, socket return: 1

Recommended

Action


Is Supported No

26.37 RTLOG


Syslog Message bgp [STRING] send open failed, send msg socket return: [LONG]


$2:the return value

Explanation BGP sent open failed,

Trigger Action NULL


bgp BGP_100 send open failed, send msg socket return: 0

Recommended

Action


Is Supported No

26.38 RTLOG


Syslog Message bgp [STRING] can not find the interface with updatesource ifname


Explanation BGP can not find the interface with updatesource ifname.



176

Trigger Action BGP can not find the interface with updatesource ifname.


bgp %s can not find the interface with updatesource ifname

task_addr_local return 1

Recommended

Action


Is Supported No

26.39 RTLOG


Syslog Message bgp [STRING] task_connect return EINPROGRESS

task_get_addr_local socket return [LONG]


$2:the return value

Explanation BGP task_connect is error.

Trigger Action Close the peer,and reconnect


bgp BGP_100 task_connect return EINPROGRESS

task_get_addr_local socket return 2

Recommended

Action


Is Supported No

26.40 RTLOG


Syslog Message bgp [STRING] bgp_ifachange


Explanation The interface is changed.

Trigger Action BGP will deal with the action.


bgp BGP_100 bgp_ifachange

Recommended

Action


Is Supported No



176

26.41 RTLOG


Syslog Message bgp [STRING] bgp_ifachange, bnp->bgp_state: [LONG]


$2:the state of the bgp-peer

Explanation The interface is changed.

Trigger Action BGP will deal with the action.


bgp BGP_100 bgp_ifachange, bnp->bgp_state: 4

Recommended

Action


Is Supported No

26.42 RTLOG


Syslog Message bgp: peer [STRING] (in state [LONG]) is closed in bgp_ifvchange()

due to virtual-link change



Explanation BGP is closed in bgp_ifvchange() due to virtual-link change

Trigger Action Close the peer.


bgp: peer BGP_100 (in state 5) is closed in bgp_ifvchange() due

to virtual-link change

Recommended

Action


Is Supported No

26.43 RTLOG


Syslog Message bgp [STRING] terminate


Explanation BGP peer is terminated



176

Trigger Action Close the peer.


bgp BGP_100 terminate

Recommended

Action


Is Supported No

26.44 RTLOG


Syslog Message bgp [STRING] terminate bgp state: [LONG]



Explanation BGP peer is terminated when peer’s state is .

Trigger Action Close the peer


bgp BGP_100 terminate bgp state: 4

Recommended

Action


Is Supported No

26.45 RTLOG


Syslog Message bgp peer [STRING] delete


Explanation Delete the BGP peer

Trigger Action NULL


bgp peer BGP_100 delete

Recommended

Action


Is Supported No

26.46 RTLOG




176

Syslog Message bgp [STRING] send Msg fail, socket return: [LONG]


$2:the return value

Explanation BGP failed to send message.

Trigger Action BGP failed to send message.


bgp BGP_100 send Msg fail, socket return: 1

Recommended

Action


Is Supported No

26.47 RTLOG


Syslog Message bgp [STRING] recv msg fail socket return: [LONG]


$2:the return value

Explanation BGP failed to receive message.

Trigger Action BGP failed to receive message.


bgp BGP_100 recv msg fail socket return: 0

Recommended

Action


Is Supported No

26.48 RTLOG


Syslog Message bgp [STRING] recv keepalive


Explanation BGP received keepalive message.

Trigger Action BGP received keepalive message.


bgp BGP_100 recv keepalive

Recommended

Action




176

Is Supported No

26.49 RTLOG


Syslog Message bgp [STRING] recv notify


Explanation BGP received the notification massage.

Trigger Action Close BGP peer and deal with the massage.


bgp BGP_100 recv notify

Recommended

Action


Is Supported No

26.50 RTLOG


Syslog Message bgp [STRING] recv update len too small


Explanation BGP receive update message of which length is too small.

Trigger Action BGP receive update message of which length is too small.


bgp BGP_100 recv update len too small

Recommended

Action


Is Supported No

26.51 RTLOG


Syslog Message ISIS: Exceed maximum circuits once!

Variable Fields $1:the string of log information by the interface name

Explanation Exceed maximum circuits for ISIS.

Trigger Action Enable ISIS on interface.


ISIS: Exceed maximum circuits once!



176

Recommended

Action


Is Supported NO

26.52 RTLOG


Syslog Message ISIS-ADJCHANGE:Adjacency To [STRING] ([STRING])

UP/DOWN/INIT, [STRING]

Variable Fields $1:the string of log information by Network Entry Title

$2:string of log information by the interface name

$3:string of log information by showing the log message

Explanation The adjacency change state.

Trigger Action The adjacency change state.

Example %Jan 10 17:18:04:610 2006 Quidway ISIS/5/ADJLOG:

ISIS-ADJCHANGE: Adjacency To cccc.cccc.cccc (Ethernet0/0)

UP , New Level-1 Adjacency

Recommended

Action


Is Supported NO

26.53 RTLOG


Syslog Message ISIS Warning: LSP [STRING] dropped

Variable Fields $1:the string of information by the isis LSP

Explanation LSP of ISIS has been dropped.

Trigger Action ISIS received wrong LSP.


ISIS Warning: LSP whose lspid is x dropped

Recommended

Action


Is Supported NO

26.54 RTLOG




176

Syslog Message ISIS Warning: Ignore Area Addresses TLV (1) in non-zero LSP

[STRING]

Variable Fields $1:the string of information by the isis LSP

Explanation Ignore Area Addresses TLV (1) in non-zero LSP.

Trigger Action ISIS received non-zero LSP that has Area Addresses TLV.


ISIS Warning: Ignore Area Addresses TLV (1) in non-zero LSP

whose lspid is x

Recommended

Action


Is Supported NO

26.55 RTLOG


Syslog Message OSPF [STRING] last neighbor down event

Variable Fields $1:the string of information by the ospf number

Explanation One last neighbor ‘state change to down for OSPF

Trigger Action One last neighbor ‘state change to down for OSPF


OSPF 1 last neighbor down event

Recommended

Action


Is Supported Yes

26.56 RTLOG


Syslog Message OSPF Neighbor State Change:[STRING]->[STRING] Router

Id:[STRING] Local Addr:[STRING] Nbr ID:[STRING]Nbr

Addr:{STRING]

Variable Fields %1:the state of the ospf-neighbor.

%2:the state of the ospf-neighbor.

%3:the ID of the local ospf-router.

%4:the ip-address of the local ospf-router..

%5:the ID of the ospf-neighbor.



176

%6:the ip-address of the ospf-neighbor.

Explanation The ospf neighbor state change form high state to low state.

Trigger Action Receive some bad packets.


OSPF Neighbor State Change:Exchange->Down Router

Id:1.1.1.1 Local Addr:10.1.1.1 Nbr ID:2.2.2.2 Nbr Addr:20.1.1.1

Recommended

Action


Is Supported Yes

26.57 RTLOG


Syslog Message ASE Export DB_WHERE(db) != ON_NSSA_LIST

Variable Fields

Explanation The nssa lsa is not a self-originated lsa.

Trigger Action When the router generate the nssa lsa of itself, the lsdb has been a

nssa lsa of the same route. But it is not a self-originated lsa..


ASE Export DB_WHERE(db) != ON_NSSA_LIST

Recommended

Action


Is Supported Yes

26.58 RTLOG


Syslog Message ASE Export DB_WHERE(db) != ON_ASE_LIST

Variable Fields

Explanation The ase lsa is not a self-originated lsa.

Trigger Action When the router generate the ase lsa of itself, the lsdb has been a

ase lsa of the same route. But it is not a self-originated lsa.


ASE Export DB_WHERE(db) != ON_ASE_LIST

Recommended

Action




176

Is Supported Yes

26.59 RTLOG


Syslog Message Too many OSPF router LSAs to run SPF for Area [STRING]

Variable Fields $1: the ospf-area ip-address

Explanation Too many OSPF router LSAs to run SPF for an area.

Trigger Action The number of router lsas of the area is lager than the max limit.


Too many OSPF router LSAs to run SPF for Area 0.0.0.1

Recommended

Action


Is Supported Yes

26.60 RTLOG


Syslog Message OSPF [ULONG] last neighbor down event: ROUTER ID:

[ULONG].[ULONG].[ULONG].[ULONG] LOCAL ADDRESS:

[ULONG].[ULONG].[ULONG].[ULONG] REMOTE ADDRESS:

[ULONG].[ULONG].[ULONG].[ULONG].REASON: [STRING]

Variable Fields $1:the OSPF process ID

$2.$3.$4.$5: the local router's ip-address

$6.$7.$8.$9: the remote router's ip-address

$10:the string of log information by the neighbour which is down

Explanation Record the imformation of OSPF last neighbor down event.

Trigger Action OSPF neighbor has been down.


OSPF 1 last neighbor down event: ROUTER ID: 10.10.2.2

LOCAL ADDRESS:192.168.2.10 REMOTE ADDRESS:

192.168.2.20 REASON: Receive error hello packet on PtP

interface.

Recommended

Action


Is Supported Yes



176

26.61 RTLOG


Syslog Message OSPF: The MTU of interface [STRING] is too small.

Variable Fields $1:the string of log information by the interface name

Explanation The MTU of one interface is too small for OSPF.

Trigger Action The MTU of one interface change to small.


OSPF: The MTU of interface ATM1/0 is too small.

Recommended

Action


Is Supported Yes

26.62 RTLOG


Syslog Message Process [LONG]'s router id has been changed.

Variable Fields $1:the OSPF process ID

Explanation One process’s router id for has been changed.

Trigger Action Router id has been changed.


OSPF: Process 1's router id has been changed.

OSPF: Reboot the system or use the 'reset ospf process ID'

command

for this to take effect.

Recommended

Action


Is Supported Yes

26.63 RTLOG


Syslog Message RIP: Exceed maximum of RIP sending routes!

Variable Fields

Explanation Exceed maximum of RIP sending routes.

Trigger Action Exceed maximum of RIP sending routes.



176


RIP: Exceed maximum of RIP sending routes!

Recommended

Action


Is Supported Yes

27 RMON Messages

This section contains the entire system log messages related to RMON.

27.1 ADDINFO

Mnemonic ADDINFO Severity Level 6

Syslog Message [STRING] table is added a valid row with index [ULONG] by

[STRING]

Variable Fields $1: The name of table.

$2: An index that uniquely identifies an entry in the alarm table.

$3: The entity that configured this entry and is therefore using the

resources assigned to it.

Explanation A new entry has been added into alarm table successfully.

Trigger Action Add a new entry into alarm table.

Example %Jan 1 01:27:05 2003 Quidway RMON/6/ADDINFO:Alarm table

is added a valid row with index 15 by cl

Recommended

Action


Is Supported Yes

27.2 DELINFO

Mnemonic DELINFO Severity Level 6

Syslog Message [STRING] table is invalidated a row with index [ULONG] by

[STRING]



176

Variable Fields $1: The name of table.

$2: An index that uniquely identifies an entry in the alarm table.

$3: The entity that configured this entry and is therefore using the

resources assigned to it.

Explanation An existed entry has been removed from alarm table successfully.

Trigger Action Remove a existed entry from alarm table.

Example %Jan 1 01:37:58 2003 Quidway RMON/6/DELINFO:Alarm table

is invalidated a row with index 15 by cl.

Recommended

Action


Is Supported Yes

28 RSA Messages

This section contains the entire system log messages related to RSA.

28.1 Key_create

Mnemonic Key_create Severity Level 4

Syslog Message Create RSA host encryption key successfully.

Variable Fields

Explanation The RSA host encryption key is created successfully.

Trigger Action Create RSA host encryption key

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_create: Create RSA

host encryption key successfully.

Recommended

Action


Is Supported Yes

28.2 Key_create


Syslog Message Fail to create RSA host encryption key.

Variable Fields

Explanation The RSA host encryption key is created unsuccessfully.

Trigger Action Create RSA host encryption key



176

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_create: Fail to

create RSA host encryption key.

Recommended

Action


Is Supported Yes

28.3 Key_create


Syslog Message Fail to save RSA host encryption key.

Variable Fields

Explanation The RSA host encryption key is not saved successfully.

Trigger Action Save RSA host encryption key

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_create: Fail to save

RSA host encryption key.

Recommended

Action


Is Supported Yes

28.4 Key_create


Syslog Message Fail to backup RSA host encryption key.

Variable Fields

Explanation The RSA host encryption key is backuped unsuccessfully.

Trigger Action Backup RSA host encryption key


backup RSA host encryption key.

Recommended

Action


Is Supported Yes

28.5 Key_create


Syslog Message Create RSA server encryption key successfully.

Variable Fields



176

Explanation The RSA server encryption key is created successfully.

Trigger Action Create RSA server encryption key.

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_create: Create RSA

server encryption key successfully.

Recommended

Action


Is Supported Yes

28.6 Key_create


Syslog Message Fail to create RSA server encryption key.

Variable Fields

Explanation The RSA server encryption key is not created successfully.

Trigger Action Create RSA server encryption key.


create RSA server encryption key.

Recommended

Action


Is Supported Yes

28.7 Key_create


Syslog Message Fail to save RSA server encryption key.

Variable Fields

Explanation The RSA server encryption key is not saved successfully.

Trigger Action Save RSA server encryption key

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_create: Fail to save

RSA server encryption key.

Recommended

Action


Is Supported Yes

28.8 Key_create




176

Syslog Message Fail to backup RSA server encryption key.

Variable Fields

Explanation The RSA server encryption key is not backuped successfully.

Trigger Action Backup RSA server encryption key


backup RSA server encryption key.

Recommended

Action


Is Supported Yes

28.9 Key_destroy

Mnemonic Key_destroy Severity Level 4

Syslog Message Destroy RSA host key successfully.

Variable Fields

Explanation The RSA host key is destroyed successfully.

Trigger Action Destroy RSA host key

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_destroy: Destroy

RSA host key successfully.

Recommended

Action


Is Supported Yes

28.10 Key_destroy


Syslog Message Success to destroy RSA host key in the main board, but fail to

destroy RSA host key in the salve board.

Variable Fields

Explanation The RSA host key in the main board is destroyed successfully, but

the RSA host key in the salve board is destroyed unsuccessfully.


Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_destroy: Success to

destroy RSA host key in the main board, but fail to destroy RSA

host key in the salve board.




176

Action

Is Supported Yes

28.11 Key_destroy


Syslog Message Fail to destroy RSA host keys.

Variable Fields

Explanation RSA host keys are not destroyed successfully.


Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_destroy

: Fail to destroy RSA host keys.

Recommended

Action


Is Supported Yes

28.12 Key_destroy


Syslog Message Destroy RSA server key successfully.

Variable Fields

Explanation The RSA server key is destroyed successfully.

Trigger Action Destroy RSA server key

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_destroy: Destroy

RSA server key successfully.

Recommended

Action


Is Supported Yes

28.13 Key_destroy


Syslog Message Success to destroy RSA server key in the main board, but fail to

destroy RSA server key in the salve board.

Variable Fields

Explanation The RSA server key in the main board is destroyed successfully,

but the RSA server key in the salve board is destroyed



176

unsuccessfully.


Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_destroy: Success to

destroy RSA server key in the main board, but fail to destroy RSA

server key in the salve board."

Recommended

Action


Is Supported Yes

28.14 Key_destroy


Syslog Message Fail to destroy RSA server key.

Variable Fields

Explanation The RSA server key is not destroyed successfully.


Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Key_destroy: Fail to

destroy RSA server key.

Recommended

Action


Is Supported Yes

28.15 Write_flash

Mnemonic Write_flash Severity Level 4

Syslog Message Fail to write flash.

Variable Fields

Explanation Fail to write data into flash.

Trigger Action Write data into flash.

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Write_flash:

Fail to write flash.

Recommended

Action


Is Supported Yes

28.16 Save_keys



176

Mnemonic Save_keys Severity Level 4

Syslog Message Fail to open file when saving keys.

Variable Fields

Explanation When saving keys, it is unsuccessfully to open file.

Trigger Action Save keys into files

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Save_keys: Fail to open

file when saving keys.

Recommended

Action


Is Supported Yes

28.17 Save_keys


Syslog Message Fail to seek when saving keys.

Variable Fields

Explanation When saving keys, it is unsuccessfully to seek.


Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Save_keys: Fail to seek

when saving keys.

Recommended

Action


Is Supported Yes

28.18 Save_keys


Syslog Message Fail to write file when saving keys.

Variable Fields

Explanation When saving keys, it is unsuccessfully to write file.


Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Save_keys: Fail to write


Recommended

Action


Is Supported Yes



176

28.19 Save_keys


Syslog Message Fail to close file when saving keys.

Variable Fields

Explanation When saving keys, it is unsuccessfully to close file.


Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Save_keys: Fail to close


Recommended

Action


Is Supported Yes

28.20 Read_keys

Mnemonic Read_keys Severity Level 4

Syslog Message Fail to open file when reading keys.

Variable Fields

Explanation When reading keys, it is unsuccessfully to open file.

Trigger Action Read keys from files

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Read_keys: Fail to open

file when reading keys.

Recommended

Action


Is Supported Yes

28.21 Read_keys


Syslog Message Fail to seek when reading keys.

Variable Fields

Explanation When reading keys, it is unsuccessfully to seek.

Trigger Action Read keys from files

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Read_keys: Fail to seek

when reading keys.




176

Action

Is Supported Yes

28.22 Read_keys


Syslog Message Fail to read flash.

Variable Fields

Explanation It is unsuccessful to read flash.

Trigger Action Read keys from flash

Example %Jan 1 01:27:05 2003 Quidway RSA/5/ Read_keys: Fail to read

flash.

Recommended

Action


Is Supported Yes

28.23 Backup_Keys

Mnemonic Backup_Keys Severity Level 3

Syslog Message Fail to backup host public key.

Variable Fields

Explanation It is unsuccessful to backup host public key.

Trigger Action Backup host public key.

Example %Jan 1 01:27:05 2003 Quidway RSA/4/ Backup_Keys: Fail to

backup host public key.

Recommended

Action


ls Supported Yes

28.24 Backup_Keys

Mnemonic Backup_Keys Severity Level 3

Syslog Message Fail to backup server public key.

Variable Fields

Explanation It is unsuccessful to backup server public key.

Trigger Action Backup server public key.

Example %Jan 1 01:27:05 2003 Quidway RSA/4/ Backup_Keys: Fail to



176

backup server public key.

Recommended

Action


Is Supported Yes

29 SHELL Messages

This section contains the entire system log messages related to EXEC.

29.1 LOGIN


Syslog Message [string]([string]) in unit[ulong] login

Variable Fields $1: user name

$2: terminal type

$3: Unit ID

Explanation Terminal type and location of login users

Trigger Action Users login

Example %Mar 3 16:20:34 2005 Quidway SHELL/5/LOGIN:aaa(2.2.2.20)

in unit 1 login

Recommended

Action



29.2 LOGOUT

Mnemonic LOGOUT Severity Level 5

Syslog Message [string]([string]) in unit[ulong] logout

Variable Fields $1: user name

$2: terminal type

$3: Unit ID

Explanation Terminal type and location of logout users

Trigger Action Users logout

Example %Mar 3 16:20:34 2005 Quidway SHELL/5/LOGIN:aaa(2.2.2.20)

in unit 1 logout



176

Recommended

Action



29.3 CMD

Mnemonic CMD Severity Level 5

Syslog Message task:[string] ip:[string] user:[string] command:[string]

Variable Fields $1: task name

$2: IP address

$3: user name

$4: command string

Explanation It shows users’ name, location, task name and commands users

executed

Trigger Action Users execute command

Example %Mar 3 16:20:34 2005 Quidway SHELL/5/CMD:task:au0 ip:**

user:aaa command:display logbuff

Recommended

Action


Is Supported Yes

29.4 SYN_ERROR

Mnemonic SYN_ERROR Severity Level 5

Syslog Message [string] synchronization failure from unit[ulong] to unit[ulong]

Variable Fields $1: terminal type

$2: unit ID of the source

$3: unit ID of the destination

Explanation It shows UI synchronizing failed

Trigger Action UI synchronizing failed

Example %Mar 3 16:20:34 2005 Quidway SHELL/5/SYN_ERROR:aux0

synchronization failure from unit2 to unit1

Recommended

Action





176

29.5 SYN_ERROR

Mnemonic SYN_ERROR Severity Level 5

Syslog Message EXEC session creation failure:[string]

Variable Fields $1: failure string

Explanation It shows creating exec session failed in fabric

Trigger Action Exec session creating failed

Example %Mar 3 16:20:34 2005 Quidway SHELL/5/SYN_ERROR:EXEC

session creation failure:Task creation failed

Recommended

Action



30 SNMP Messages

This section contains the entire system log messages related to SNMP.

30.1 GET

Mnemonic GET Severity Level 4

Syslog Message \r\nseqNO = <[ulong]> srcIP = <[string]> op = <get> node =

<[string]> value = <[string]>\r\n

Variable Fields $1: The sequence number of GET request

$2: The source IP address of GET request

$3: The name of node in a GET request

$4: The value of node in a GET request

Explanation SNMP agent received a GET request

Trigger Action SNMP agent received a GET request

Example %Apr 18 15:12:39:157 2006 Quidway SNMP/5/GET:- 1 –

seqNO = <1> srcIP = <169.254.76.200> op = <get> node =

<sysUpTime(1.3.6.1.2.1.1.3.0)> value = <>

Recommended

Action


Is Supported Yes



176

30.2 SET

Mnemonic SET Severity Level 4

Syslog Message \r\nseqNO = <[ulong]> srcIP = <[string]> op = <set> errorIndex =

<[ulong]> errorStatus = <[ulong]> node = <[string]> value =

<[string]>\r\n

Variable Fields $1: The sequence number of SET request

$2: The source IP address of SET request

$3: The error index of variable-binding list

$4: The error status of variable-binding list

$5: The name of node in SET request

$6: The value of node in SET request

Explanation SNMP agent received a SET request

Trigger Action SNMP agent received a SET request

Example %Apr 18 15:14:28:440 2006 Quidway SNMP/5/SET:- 1 -

seqNO = <3> srcIP = <169.254.76.200> op = <set> errorIndex =

<0> errorStatus =<0> node = <sysName(1.3.6.1.2.1.1.5.0)> value

= <Quidway>

Recommended

Action


Is Supported Yes

31 SOCKET Messages

31.1 SOCKETLOG

Mnemonic SOCKETLOG Severity Level 4


Variable Fields $1: information

Explanation

Trigger Action No use

Example

Recommended

Action


Is Supported No



176

31.2 TCP MD5

Mnemonic TCP MD5 Severity Level 4

Syslog Message Received TCP packet with invalid MD5 digest. SOURCE:[STRING]

FOREIGN:[STRING]

Variable Fields $1: source ip address

$2: destination ip address

Explanation Receive TCP packet with invalid MD5 digest

Trigger Action Receive a TCP packet

Example Received TCP packet with invalid MD5 digest. SOURCE:2.2.2.2

FOREIGN:3.3.3.3

Recommended

Action


Is Supported Yes

32 SSH Messages

This section contains the entire system log messages related to ssh.

32.1 ver_len_err

Mnemonic ver_len_err Severity Level 4

Syslog Message SSH version string length is greater than 256.

Variable Fields

Explanation The length of ssh version string is incorrect.

Trigger Action The length of ssh version string is greater than 256.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ ver_len_err: SSH version

string length is greater than 256.

Recommended

Action

Input correct version string.

Is Supported Yes

32.2 ver_major_err

Mnemonic ver_major_err Severity Level 4

Syslog Message Protocol major versions differ: [string] vs. [string]

Variable Fields $1: The local protocol major version.



176

$2: The remote protocol major version.

Explanation The major version is different.

Trigger Action Login with the major version other than $1.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ ver_major_err: Protocol

major versions differ: 1 vs 2.

Recommended

Action

Login with correct major version.

Is Supported Yes

32.3 ver_minor_err

Mnemonic ver_minor_err Severity Level 4

Syslog Message Protocol minor versions [string] is too old

Variable Fields $1: The remote protocol minor version.

Explanation The minor version is unsupported.

Trigger Action The minor version is smaller than 3.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ ver_minor_err: Protocol

minor versions 2 is too old.

Recommended

Action

Use the version between 3 and 5.

Is Supported Yes

32.4 ver_minor_unspt

Mnemonic ver_minor_unspt Severity Level 4

Syslog Message Protocol minor versions [string] is unsupported

Variable Fields $1: The remote version information.

Explanation The minor version is unsupported.

Trigger Action The minor version is bigger than 5.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ ver_minor_unspt:

Protocol minor versions 7 is unsupported

Recommended

Action

Use the version between 3 and 5.

Is Supported Yes

32.5 buf_len_zero



176

Mnemonic buf_len_zero Severity Level 4

Syslog Message Sending buffer length is 0 in SSH_SendToSsh

Variable Fields

Explanation The length of buffer is 0.

Trigger Action The length of buffer is 0.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ buf_len_zero: Sending

buffer length is 0 in SSH_SendToSsh.

Recommended

Action

Assign correct buffer length.

Is Supported Yes

32.6 session_msg_err

Mnemonic session_msg_err Severity Level 4

Syslog Message Received unexpected packet instead of

SSH_CMSG_SESSION_KEY: [string]

Variable Fields $1: The name of session key.

Explanation The session key is incorrect.

Trigger Action The session key is not 3.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ session_msg_err:

Received unexpected packet instead of

SSH_CMSG_SESSION_KEY: 2.

Recommended

Action

Send correct session key.

Is Supported Yes

32.7 cipher_err

Mnemonic cipher_err Severity Level 4

Syslog Message Client chose unsupported cipher mask

Variable Fields

Explanation Server does not support the cipher mask.

Trigger Action Client chose unsupported cipher mask.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ cipher_err: Client chose

unsupported cipher mask

Recommended Choose supported cipher mask.



176

Action

Is Supported Yes

32.8 cookie_err

Mnemonic cookie_err Severity Level 4

Syslog Message Client's cookie is different from server's

Variable Fields

Explanation Client's cookie is different from server's.

Trigger Action Client's cookie is different from server's.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ cookie_err: Client's

cookie is different from server's

Recommended

Action

Send correct cookie.

Is Supported Yes

32.9 user_msg_err

Mnemonic user_msg_err Severity Level 4

Syslog Message Received unexpected packet instead of SSH_CMSG_USER

packet: [string]

Variable Fields $1: The name of the packet.

Explanation The packet is incorrect.

Trigger Action The packet is not SSH_CMSG_USER.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ user_msg_err: Received

unexpected packet instead of SSH_CMSG_USER packet:

SSH_CMSG_SESSION_KEY.

Recommended

Action


Is Supported Yes

32.10 auth_retryt_out

Mnemonic auth_retryt_out Severity Level 4

Syslog Message Too many authentication failures for user [string] on VTY [string]

Variable Fields $1: The name of user.

$2: The port of VTY.



176

Explanation Fail to authenticate.

Trigger Action Too many authentication failures.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ auth_retryt_out: Too

many authentication failures for user ssh-user on VTY 0.

Recommended

Action


Is Supported Yes

32.11 auth_msg_err

Mnemonic auth_msg_err Severity Level 4

Syslog Message Received unexpected packet on Authentication state: [string]

Variable Fields $1: The name of message type.

Explanation The message type is not authentication.

Trigger Action The message type is not authentication.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ auth_msg_err

: Received unexpected packet on Authentication state:

SSH_VERSION_SEND.

Recommended

Action


Is Supported Yes

32.12 passwd_len_err

Mnemonic passwd_len_err Severity Level 4

Syslog Message The password's length is greater than 16

Variable Fields

Explanation The length of password is incorrect.

Trigger Action The length of password is greater than 16

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ passwd_len_err: The

password's length is greater than 16

Recommended

Action

Input correct password.

Is Supported Yes

32.13 passwd_err



176

Mnemonic passwd_err Severity Level 4

Syslog Message Wrong password offered by user [string] on VTY [string]

Variable Fields $1: The name of user.


Explanation The password is wrong.

Trigger Action The password is wrong.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ passwd_err: Wrong

password offered by user ssh-user on VTY 0.

Recommended

Action

Input correct password.

Is Supported Yes

32.14 authrsa_msg_err

Mnemonic authrsa_msg_err Severity Level 4

Syslog Message Received unexpected packet instead of SSH_CMSG_AUTH_RSA

packet: [string]


Explanation The message type is not SSH_CMSG_AUTH_RSA..

Trigger Action The message type is not SSH_CMSG_AUTH_RSA..

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ authrsa_msg_err:

Received unexpected packet instead of SSH_CMSG_AUTH_RSA

packet: SSH_CMSG_AUTH_PASSWORD.

Recommended

Action


Is Supported Yes

32.15 rsarspn_msg_err

Mnemonic rsarspn_msg_err Severity Level 4

Syslog Message Received unexpected packet instead of

SSH_CMSG_AUTH_RSA_RESPONSE packet: [string]


Explanation The message type is not SSH_CMSG_AUTH_RSA_RESPONSE.

Trigger Action The message type is not SSH_CMSG_AUTH_RSA_RESPONSE.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ rsarspn_msg_err:



176

Received unexpected packet instead of

SSH_CMSG_AUTH_RSA_RESPONSE packet:

SSH_CMSG_AUTH_PASSWORD

Recommended

Action


Is Supported Yes

32.16 challenge_err

Mnemonic challenge_err Severity Level 4

Syslog Message Client's MD5 challenge is different from the server's

Variable Fields

Explanation The MD5 challenge is wrong.

Trigger Action The MD5 challenge is wrong.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ challenge_err: Client's

MD5 challenge is different from the server's

Recommended

Action

Send correct MD5 challenge.

Is Supported Yes

32.17 getckey_err

Mnemonic getckey_err Severity Level 4

Syslog Message Can not get RSA peer keys from RSA module

Variable Fields

Explanation Fail to get RSA peer keys.

Trigger Action Fail to get RSA peer keys.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ getckey_err: Can not get

RSA peer keys from RSA module

Recommended

Action


Is Supported Yes

32.18 username_len_err

Mnemonic username_len_err Severity Level 4

Syslog Message The user name length is greater than 32



176

Variable Fields

Explanation The length of user name is incorrect.

Trigger Action The length of user name is greater than 32.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/username_len_err: The

user name length is greater than 32

Recommended

Action

Input correct user name.

Is Supported Yes

32.19 user_not_exist

Mnemonic user_not_exist Severity Level 4

Syslog Message The user [string] doesn't exist

Variable Fields $1: The user name.

Explanation The user is illegal.

Trigger Action Input incorrect user name.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ user_not_exist: The user

www doesn't exist

Recommended

Action

Input correct user name.

Is Supported Yes

32.20 user_noauth

Mnemonic user_noauth Severity Level 4

Syslog Message No authentication type configured for the user [string]

Variable Fields $1: The user name.

Explanation The user is not configured completely.

Trigger Action Do not configure authentication type to the user.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ user_noauth: No

authentication type configured for the user www.

Recommended

Action


Is Supported Yes

32.21 rsa_n_err



176

Mnemonic rsa_n_err Severity Level 4

Syslog Message The client sent a RSA-key-module-n which is unequal to the

server's

Variable Fields

Explanation The RSA-key-module-n is different form server’s.

Trigger Action The RSA-key-module-n is different form server’s.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ rsa_n_err: The client

sent a RSA-key-module-n which is unequal to the server's.

Recommended

Action


Is Supported Yes

32.22 fsm_move

Mnemonic fsm_move Severity Level 4

Syslog Message FSM MOVE FROM [string] TO [string]

Variable Fields $1: The name of fsm.

$2: The name of fsm.

Explanation The fsm will move.

Trigger Action The fsm will move.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ fsm_move: FSM MOVE

FROM SSH_Main_Connect TO SSH_Main_VersionMatch.

Recommended

Action


Is Supported Yes

32.23 err_dissconnect

Mnemonic err_dissconnect Severity Level 4

Syslog Message The connection is closed by SSH Server\r\nCurrent FSM is :

[string]


Explanation Fail to connect.

Trigger Action Fail to connect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ err_dissconnect: The

connection is closed by SSH Server\r\nCurrent FSM is :



176

. SSH_Main_VersionMatch.

Recommended

Action


ls Supported Yes

32.24 unexpected_msg

Mnemonic unexpected_msg Severity Level 4

Syslog Message [string] message received on VTY [string] is unexpected.

Variable Fields $1: The name of message.


Explanation The message is wrong.

Trigger Action The message is wrong.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ unexpected_msg:

SSH_VERSION_SEND message received on VTY 0 is

unexpected.

Recommended

Action


Is Supported Yes

32.25 bad_cmd_length

Mnemonic bad_cmd_length Severity Level 4

Syslog Message The command in SSH_CMSG_EXEC_CMD is too long.

Variable Fields

Explanation The command is too long.

Trigger Action The command is too long.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ bad_cmd_length: The

command in SSH_CMSG_EXEC_CMD is too long.

Recommended

Action


Is Supported Yes

32.26 msg_disconnect

Mnemonic msg_disconnect Severity Level 4

Syslog Message SSH_MSG_DISCONNECT received on VTY [string]



176

Variable Fields $1: The port of VTY.

Explanation Fail to connect.

Trigger Action Fail to connect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ msg_disconnect:

SSH_MSG_DISCONNECT received on VTY 0.

Recommended

Action


Is Supported Yes

32.27 bad_plaintext_length

Mnemonic bad_plaintext_length Severity Level 4

Syslog Message The plain text length is bad.

Variable Fields

Explanation The length of plain text is incorrect.

Trigger Action The length of plain text is incorrect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/bad_plaintext_length:

The plain text length is bad.

Recommended

Action


Is Supported Yes

32.28 bad_cryptograph_len

Mnemonic bad_cryptograph_len Severity Level 4

Syslog Message The cryptograph length is bad.

Variable Fields

Explanation The length of cryptograph is incorrect.

Trigger Action The length of cryptograph is incorrect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ bad_cryptograph_len:

The cryptograph length is bad.

Recommended

Action


Is Supported Yes

32.29 bad_key_length



176

Mnemonic bad_key_length Severity Level 4

Syslog Message The cipher key length is bad.

Variable Fields

Explanation The length of cipher key is incorrect.

Trigger Action The length of cipher key is incorrect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ bad_key_length: The

cipher key length is bad.

Recommended

Action


Is Supported Yes

32.30 bad_iv_len

Mnemonic bad_iv_len Severity Level 4

Syslog Message The cipher iv length is bad.

Variable Fields

Explanation The length of cipher iv is incorrect.

Trigger Action The length of cipher iv is incorrect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ bad_iv_len: The cipher iv

length is bad.

Recommended

Action


Is Supported Yes

32.31 bad_string_len

Mnemonic bad_string_len Severity Level 4

Syslog Message The string data length is greater than 2 * 1024.

Variable Fields

Explanation The length of string data is incorrect.

Trigger Action The length of string data is greater than 2 * 1024.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ bad_string_len: The

string data length is greater than 2 * 1024.

Recommended

Action


Is Supported Yes



176

32.32 bignum_len_wrong

Mnemonic bignum_len_wrong Severity Level 4

Syslog Message The bignum data length is bad.

Variable Fields

Explanation The length of bignum data is incorrect.

Trigger Action The length of bignum data is incorrect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ bignum_len_wrong: The

bignum data length is bad.

Recommended

Action


Is Supported Yes

32.33 bignum_not_full

Mnemonic bignum_not_full Severity Level 4

Syslog Message The bignum data is not full.

Variable Fields

Explanation The bignum data is incorrect.

Trigger Action The bignum data is incorrect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ bignum_not_full: The

bignum data is not full.

Recommended

Action


Is Supported Yes

32.34 unknown_cipher_type

Mnemonic unknown_cipher_type Severity Level 4

Syslog Message The cipher type is unknown.

Variable Fields

Explanation The ciphet type is unsupported.

Trigger Action The ciphet type is unsupported.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ unknown_cipher_type:

The cipher type is unknown.




176

Action

Is Supported Yes

32.35 send_length_wrong

Mnemonic send_length_wrong Severity Level 4

Syslog Message The SSH packet length is wrong.

Variable Fields

Explanation The length of ssh packet is incorrect.

Trigger Action The length of ssh packet is smaller than 5 or bigger than 4 * 1024.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/DELINFO:

send_length_wrong

Recommended

Action


Is Supported Yes

32.36 send_buf_null

Mnemonic send_buf_null Severity Level 4

Syslog Message The SSH packet is empty.

Variable Fields

Explanation No message is to be sended.

Trigger Action The packet has no message.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ send_buf_null: The SSH

packet is empty.

Recommended

Action


Is Supported Yes

32.37 send_fail

Mnemonic send_fail Severity Level 4

Syslog Message Sending SSH message fails.

Variable Fields

Explanation Fail to send SSH message.

Trigger Action Fail to send SSH message.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/DELINFO: Sending SSH



176

message fails.

Recommended

Action


Is Supported Yes

32.38 msg_length_slop

Mnemonic msg_length_slop Severity Level 4

Syslog Message SSH message length slops.

Variable Fields

Explanation The length of ssh message is incorrect.

Trigger Action The length of ssh message is smaller than 5 or bigger than 4 *

1024.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ msg_length_slop: SSH

message length slops.

Recommended

Action


Is Supported Yes

32.39 read_length_wrong

Mnemonic read_length_wrong Severity Level 4

Syslog Message SSH message length is wrong.

Variable Fields

Explanation The length of ssh message is incorrect.

Trigger Action The length of ssh message is incorrect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ read_length_wrong:

SSH message length is wrong.

Recommended

Action


Is Supported Yes

32.40 read_crc_wrong

Mnemonic read_crc_wrong Severity Level 4

Syslog Message SSH message CRC is wrong.

Variable Fields



176

Explanation Ssh message CRC is incorrect.

Trigger Action Ssh message CRC is incorrect.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ read_crc_wrong: SSH

message CRC is wrong.

Recommended

Action


Is Supported Yes

32.41 user_exist

Mnemonic user_exist Severity Level 4

Syslog Message AAA overwrites the current user!

Variable Fields

Explanation The current user has existed.

Trigger Action Creat a user which has existed.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ user_exist: AAA

overwrites the current user!

Recommended

Action


Is Supported Yes

32.42 add_success

Mnemonic add_success Severity Level 4

Syslog Message Add user successfully!

Variable Fields

Explanation Add an user successfully

Trigger Action Add an user successfully

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ add_success: Add user

successfully!

Recommended

Action


Is Supported Yes

32.43 del_success

Mnemonic del_success Severity Level 4



176

Syslog Message Delete user successfully!

Variable Fields

Explanation Delete an user successfully

Trigger Action Delete an user successfully

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ del_success: Delete

user successfully!

Recommended

Action


Is Supported Yes

32.44 getkey_fail

Mnemonic getkey_fail Severity Level 4

Syslog Message Can't get the client's rsa-key, it may be destroyed by RSA module!

Variable Fields

Explanation Fail to get the client’s rsa-key.

Trigger Action Fail to get the client’s rsa-key.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ getkey_fail: Can't get the

client's rsa-key, it may be destroyed by RSA module!

Recommended

Action


Is Supported Yes

32.45 accept_err

Mnemonic accept_err Severity Level 4

Syslog Message Acceptting fails when listenning Socket [string]

Variable Fields $1: The socket descriptor.

Explanation Fail to accept.

Trigger Action Fail to accept.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ accept_err: Acceptting

fails when listenning Socket 2 .

Recommended

Action


Is Supported Yes



176

32.46 malloc_err

Mnemonic malloc_err Severity Level 4

Syslog Message Malloc error at [string]

Variable Fields $1: the type of memory

Explanation Fail to allocate memory.

Trigger Action Fail to allocate memory.

Example

Recommended

Action


Is Supported Yes

32.47 buf_get_wrong

Mnemonic buf_get_wrong Severity Level 4

Syslog Message Accessing buffer fails:

\r\nBuffer' length : [string]

\r\nBuffer' Offset : [string]

\r\nBuffer' End : [string]

Variable Fields $1: Buffer’ length.

$2: Buffer' Offset

$3: Buffer' End

Explanation Fail to access buffer.

Trigger Action Fail to access buffer.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ buf_get_wrong:

Accessing buffer fails:

\r\nBuffer' length : 0.

\r\nBuffer' Offset : 2.

\r\nBuffer' End : 3.

Recommended

Action


Is Supported Yes

32.48 des_setkey_fail

Mnemonic des_setkey_fail Severity Level 4

Syslog Message Setting des key fails on VTY [string]




176

Explanation Fail to set des key.

Trigger Action Fail to set des key.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ des_setkey_fail: Setting

des key fails on VTY 0.

Recommended

Action


Is Supported Yes

32.49 3des_setkey_fail

Mnemonic 3des_setkey_fail Severity Level 4

Syslog Message Setting 3des key fails on VTY [string]


Explanation Fail to set 3des key.

Trigger Action Fail to set 3des key.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/3des_setkey_fail: Setting

3des key fails on VTY 0.

Recommended

Action


Is Supported Yes

32.50 rsa_decrypt_fail

Mnemonic rsa_decrypt_fail Severity Level 4

Syslog Message Decrypting using RSA private key fails!

Variable Fields

Explanation Fail to decrypting.

Trigger Action Fail to decrypting.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ rsa_decrypt_fail:

Decrypting using RSA private key fails!

Recommended

Action


Is Supported Yes

32.51 rsa_gethostkey_fail

Mnemonic rsa_gethostkey_fail Severity Level 4



176

Syslog Message Getting RSA host key fails!

Variable Fields Fail to get RSA host key.

Explanation Fail to get RSA host key.

Trigger Action Fail to get RSA host key.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ rsa_gethostkey_fail:

Getting RSA host key fails!

Recommended

Action


Is Supported Yes

32.52 rsa_getserverkey_fail

Mnemonic rsa_getserverkey_fail Severity Level 4

Syslog Message Getting RSA server key fails!

Variable Fields

Explanation Fail to get RSA server key.

Trigger Action Fail to get RSA server key.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ rsa_getserverkey_fail:

Getting RSA server key fails!

Recommended

Action


Is Supported Yes

32.53 rsa_encrytp_fail

Mnemonic rsa_encrytp_fail Severity Level 4

Syslog Message Encrypting using RSA public key fails!

Variable Fields

Explanation Fail to encrypt.

Trigger Action Fail to encrypt.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ rsa_encrytp_fail:

Encrypting using RSA public key fails!

Recommended

Action


Is Supported Yes



176

32.54 socket_send_fail.

Mnemonic socket_send_fail Severity Level 4

Syslog Message Sending version string fails!

Variable Fields

Explanation Fail to send version string.

Trigger Action Fail to send version string.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ socket_send_fail:

Sending version string fails!

Recommended

Action


Is Supported Yes

32.55 no_auth_type

Mnemonic no_auth_type Severity Level 4

Syslog Message No configing authentication type for the user!

Variable Fields

Explanation The user has no authentication type.

Trigger Action Configure no authentication type for the user

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ no_auth_type: No

configing authentication type for the user!

Recommended

Action


Is Supported Yes

32.56 get_version_fail

Mnemonic get_version_fail Severity Level 4

Syslog Message Get version string fail!

Variable Fields

Explanation Fail to get version string.

Trigger Action Fail to get version string.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ get_version_fail: Get

version string fail!

Recommended

Action




176

Is Supported Yes

32.57 rcv_unexpected_msg

Mnemonic rcv_unexpected_msg Severity Level 4

Syslog Message Received an unexpected message instead of

SSH_CMSG_AUTH_PASSWORD!

Variable Fields

Explanation The message is incorrect.

Trigger Action The message is not SSH_CMSG_AUTH_PASSWORD!

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ rcv_unexpected_msg:

Received an unexpected message instead of

SSH_CMSG_AUTH_PASSWORD!

Recommended

Action


Is Supported Yes

32.58 msg_type_illegal

Mnemonic msg_type_illegal Severity Level 4

Syslog Message The message type is illegal on VTY [string]!


Explanation The message type is illegal.

Trigger Action The message type is illegal.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ msg_type_illegal: The

message type is illegal on VTY 0 !

Recommended

Action


Is Supported Yes

32.59 msg_tran_close

Mnemonic msg_tran_close Severity Level 4

Syslog Message Message transport stops !

Variable Fields

Explanation Message transport stops

Trigger Action Message transport stops



176

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ msg_tran_close:

Message transport stops !

Recommended

Action


Is Supported Yes

32.60 msg_tran_deadloop

Mnemonic msg_tran_deadloop Severity Level 4

Syslog Message Message transport is in deadloop !

Variable Fields

Explanation Fail to transport message.

Trigger Action Fail to transport message.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ msg_tran_deadloop:

Message transport is in deadloop !

Recommended

Action


Is Supported Yes

32.61 msg_client_exit

Mnemonic msg_client_exit Severity Level 4

Syslog Message The connection is closed by SSH Client\r\nCurrent FSM is : [string]


Explanation The connection is closed by SSH Client.

Trigger Action The connection is closed by SSH Client.

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ msg_client_exit: The

connection is closed by SSH Client\r\nCurrent FSM is :

SSH_Main_VersionMatch.

Recommended

Action


Is Supported Yes

32.62 msg_ssh_vty

Mnemonic msg_ssh_vty Severity Level 4

Syslog Message The Connection from [string] is refused by ACL.



176

Variable Fields $1: The user’s ipaddr.

Explanation Fail to connect

Trigger Action The user’s ipaddr is unsupported by ACL..

Example %Jan 1 01:27:05 2003 Quidway SSH/5/ msg_ssh_vty:

The Connection from 192.168.1.1 is refused by ACL.

Recommended

Action


Is Supported Yes

33 VFS Messages

This section contains the entire system log messages related to VFS.

33.1 VFSLOG

Mnemonic VFSLOG Severity Level 5

Syslog Message "\r\n [string] \r\n"

Variable Fields $1: Information string.

Explanation Fail to copy or write data into flash.

Trigger Action Copy or write data into flash.

Example %Jan 30 13:42:54:970 2006 S5200 VFS/5/LOG:

Error when copying data into flash, please check flash memory!

Recommended

Action


Trigger Action CF card is removed or inserted.

Example %Jan 30 13:42:54:970 2006 AR19-61 VFS/5/LOG:

cf: removed from slot 0

Recommended

Action


Is Supported Yes



176

34 VLAN Messages

This section contains the entire system log messages related to VLAN.

34.1 DETECT_FORBIDDEN

Mnemonic DETECT_FORBIDDEN Severity Level 5

Syslog Message forbidden by [STRING] event.

Variable Fields $1: The name of the event.

Explanation

Trigger Action

Example

Recommended

Action


Is Supported No

34.2 DETECT_FORBIDDEN

Mnemonic DETECT_FORBI Severity Level 5

Syslog Message event [STRING] was received

Variable Fields $1: The name of the event

Explanation

Trigger Action

Example

Recommended

Action


Is Supported No

34.3 BATCH notify

Mnemonic BATCH notify Severity Level 5

Syslog Message BATCH notify:[STRING]

Variable Fields $1: The name of the event

Explanation to notify other modules that batch operation will happen

Trigger Action Batch operation happens

Example




176

Action

Is Supported No

35 VRRP Messages

This section contains the entire system log messages related to VRRP

35.1 LogAuthFailed

Mnemonic LogAuthFailed Severity Level 3

Syslog Message [STRING] | Virtual Router [ULONG] : [STRING]

Variable Fields $1: The interface name which the vritual router was configed to.

$2:The virtual router’s ID

Explanation Received a VRRP packet, but it can not pass the authentication

examination.

Trigger Action Received VRRP packet which can not pass authentication

examination.

Example %Feb 21 17:35:57:99 2006 S8500 VRRP/4/LogAuthFailed:

Ethernet0/0 | Virtual Router 10: failed to authenticate.

Recommended

Action

Check the configuration of the virtual router on the indicated

interface. Make sure that every virtual router of the indicated ID

uses the same authentication mode and authentication key.

Is Supported Yes

35.2 ConfigError

Mnemonic ConfigError Severity Level 3

Syslog Message System detected a vrrp packet error of [STRING]

Variable Fields $1: The error type of the received VRRP packet.

Explanation Received a VRRP packet, but it is not a valid VRRP packet.

Trigger Action Received an invalid VRRP packet. For example, when the system

received a VRRP packet but the checksum is incorrect.

Example %Feb 21 18:00:23:922 2006 S8500 VRRP/4/ConfigError:

System detected a vrrp packet error of CKSUM ERROR

Recommended

Action


interface.



176

Trigger Action The checksum of the VRRP packet is incorrect.

The TTL value of the VRRP packet is incorrect.

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.

Example See above

Recommended

Action

See above

Is Supported Yes

35.3 ConfigError

Mnemonic ConfigError Severity Level 3

Syslog Message System detected a vrrp config error of [STRING],

Interface:[STRING], Virtual Router:[ULONG]

Variable Fields $1: The error type of configuration.

$2: The interface name.

$3: The Virtual Router’s ID.

Explanation The current configuration of the virtual router is not correct.

Trigger Action The configuration of the virtual router is not correct. For example,

the virtual ip address count of the virtual router is not the same.

Example %Feb 21 18:12:11:860 2006 s8500 VRRP/4/ConfigError:

System detected a vrrp config error of VIRTUAL IP ADDRESS

COUNT ERROR, Interface:Ethernet0/1/0, Virtual Router:10

Recommended

Action



uses the same virtual ip address’s list.

Trigger Action Fail 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.

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



176

address.

Example See above.

Recommended

Action

See above.

Is Supported Yes

35.4 MasterChange

Mnemonic MasterChange Severity Level 3

Syslog Message [STRING] | Virtual Router [ULONG] : [STRING] reason:

[STRING]

Variable Fields $1: The interface name which the virtual router was configured to.

$2: The Virtual Router’s ID.

$3: The reason for the status change.

Explanation The status of the rirtual router changed.

Trigger Action Timer fired.

Example %Feb 21 19:24:19:932 2006 AR19-61 VRRP/5/MasterChange:

Ethernet0/0 | Virtual Router 10 : BACKUP --> MASTER

reason: Timer fired

Recommended

Action

Check the status of the Virtual Router, make sure it works well.

Trigger Action Received VRRP packet.

Fail to add virtual MAC address.

Received an interface event.

The IP address of the interface has been deleted.

Example See above.

Recommended

Action

See above.

Is Supported Yes

35.5 RunError

Mnemonic RunError Severity Level 3


Variable Fields $1: The error information during the system running.

Explanation An error ocures during the system running.



176

Trigger Action An error ocures during the system running.

Example %Feb 21 19:40:01:31 2006 Quidway-wvrp VRRP/4/RunError:

create Vrrp queue fail

Recommended

Action

Find out why the error ocured and fix it.

Is Supported Yes

35.6 SetDriver

Mnemonic SetDriver Severity Level 3

Syslog Message Interface:[STRING],Virtual Router:[ULONG] [STRING] Virtual MAC

Failed.

Variable Fields $1: The interface name where the virtual router was configured.

$2: The virtual router’s ID

$3: Add or delete virtual MAC.

Explanation Fail to add or delete virtual MAC.

Trigger Action Fail to add or delete virtual MAC.

Example %Feb 21 19:40:01:31 2006 Quidway-wvrp VRRP/4/ConfigError:

System detected a vrrp config error of ADD Virtual MacAddress

Fail, Interface:

Ethernet0/1/0, Virtual Router:12

Recommended

Action

Find out why fail to add or delete Virtual MAC to the driver and fix it.

Is Supported Yes

35.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.

Example #Feb 21 20:14:07:906 2006 Quidway-wvrp

VRRP/4/TrapBecomeNewMaster: 1.3.6.1.2.1.6



176

8.0.1become new master.

Recommended

Action


Is Supported Yes

35.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.

Example #Feb 21 20:16:46:688 2006 Quidway-wvrp

VRRP/4/TrapAuthFailed: 1.3.6.1.2.1.68.0.2

failed to authenticate

Recommended

Action



uses the same authentication mode and authentication key.

Is Supported Yes

36 VTY Messages

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

36.1 VTY_LOG

Mnemonic VTY_LOG Severity Level 4




Trigger Action Fail to regenerate randpool or VTY users authentication is timeout

Example %Feb 21 15:39:10:406 2006 Quidway-wvrp VTY/5/VTY_LOG:

RandPool regenerate failed!!.




176

Action

Is Supported Yes

Documents

Comware V3 Switch System Log Message