H3C S6800 Switch Series System Log Messages Reference-6W100

HomeSupportResource CenterSwitchesH3C S6800 Switch SeriesH3C S6800 Switch SeriesTechnical DocumentsMaintainMessage ReferencesH3C S6800 Switch Series System Log Messages Reference-6W100

 

H3C S6800 Switch Series

System Log Messages Reference

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 6W100-20171220

 

H3C_彩色.emf

 


Contents

Introduction· 1

System log message format 1

Managing and obtaining system log messages· 3

Obtaining log messages from the console terminal 3

Obtaining log messages from the log buffer 3

Obtaining log messages from a monitor terminal 3

Obtaining log messages from the log file· 4

Obtaining log messages from a log host 4

Software module list 4

Using this document 7

AAA messages· 9

AAA_FAILURE· 9

AAA_LAUNCH·· 9

AAA_SUCCESS· 10

ACL messages· 11

ACL_ACCELERATE_NO_RES· 11

ACL_ACCELERATE_NONCONTIGUOUSMASK· 11

ACL_ACCELERATE_NOT_SUPPORT· 11

ACL_ACCELERATE_NOT_SUPPORTHOPBYHOP· 12

ACL_ACCELERATE_NOT_SUPPORTMULTITCPFLAG·· 12

ACL_ACCELERATE_UNK_ERR·· 12

ACL_IPV6_STATIS_INFO·· 13

ACL_NO_MEM·· 13

ACL_STATIS_INFO·· 13

PFILTER_GLB_IPV4_DACT_NO_RES· 14

PFILTER_GLB_IPV4_DACT_UNK_ERR·· 14

PFILTER_GLB_IPV6_DACT_NO_RES· 15

PFILTER_GLB_IPV6_DACT_UNK_ERR·· 15

PFILTER_GLB_MAC_DACT_NO_RES· 16

PFILTER_GLB_MAC_DACT_UNK_ERR·· 16

PFILTER_GLB_NO_RES· 17

PFILTER_GLB_NOT_SUPPORT· 17

PFILTER_GLB_ RES_CONFLICT· 18

PFILTER_GLB_UNK_ERR·· 18

PFILTER_IF_IPV4_DACT_NO_RES· 19

PFILTER_IF_IPV4_DACT_UNK_ERR·· 19

PFILTER_IF_IPV6_DACT_NO_RES· 20

PFILTER_IF_IPV6_DACT_UNK_ERR·· 20

PFILTER_IF_MAC_DACT_NO_RES· 21

PFILTER_IF_MAC_DACT_UNK_ERR·· 21

PFILTER_IF_NO_RES· 22

PFILTER_IF_NOT_SUPPORT· 22

PFILTER_IF_RES_CONFLICT· 23

PFILTER_IF_UNK_ERR·· 23

PFILTER_IPV6_STATIS_INFO·· 24

PFILTER_STATIS_INFO·· 24

PFILTER_VLAN_IPV4_DACT_NO_RES· 25

PFILTER_VLAN_IPV4_DACT_UNK_ERR·· 25

PFILTER_VLAN_IPV6_DACT_NO_RES· 26

PFILTER_VLAN_IPV6_DACT_UNK_ERR·· 26

PFILTER_VLAN_MAC_DACT_NO_RES· 27

PFILTER_VLAN_MAC_DACT_UNK_ERR·· 27

PFILTER_VLAN_NO_RES· 28

PFILTER_VLAN_NOT_SUPPORT· 28

PFILTER_VLAN_RES_CONFLICT· 29

PFILTER_VLAN_UNK_ERR·· 29

ANCP messages· 30

ANCP_INVALID_PACKET· 30

APMGR messages· 31

APMGR_AC_MEM_ALERT· 31

APMGR_ADD_AP_FAIL· 31

APMGR_ADDBAC_INFO·· 32

APMGR_AP_OFFLINE· 32

APMGR_AP_ONLINE· 32

APMGR_CWC_IMG_DOWNLOAD_COMPLETE· 33

APMGR_CWC_IMG_DOWNLOAD_START· 33

APMGR_CWC_IMG_NO_ENOUGH_SPACE· 33

APMGR_CWC_LOCAL_AC_DOWN·· 34

APMGR_CWC_LOCAL_AC_UP· 34

APMGR_CWC_REBOOT· 35

APMGR_CWC_RUN_DOWNLOAD_COMPLETE· 35

APMGR_CWC_RUN_DOWNLOAD_START· 35

APMGR_CWC_RUN_NO_ENOUGH_SPACE· 36

APMGR_CWC_TUNNEL_DOWN·· 36

APMGR_CWC_TUNNEL_UP· 37

APMGR_CWS_IMG_DOWNLOAD_COMPLETE· 37

APMGR_CWS_IMG_DOWNLOAD_START· 37

APMGR_CWS_LOCAL_AC_DOWN·· 38

APMGR_CWS_LOCAL_AC_UP· 38

APMGR_CWS_RUN_DOWNLOAD_COMPLETE· 39

APMGR_CWS_RUN_DOWNLOAD_START· 39

APMGR_CWS_TUNNEL_DOWN·· 40

APMGR_CWS_TUNNEL_UP· 40

APMGR_DELBAC_INFO·· 41

APMGR_LOCAL_AC_OFFLINE· 41

APMGR_LOCAL_AC_ONLINE· 41

ARP messages· 42

ARP_ACTIVE_ACK_NO_REPLY· 42

ARP_ACTIVE_ACK_NOREQUESTED_REPLY· 42

ARP_BINDRULETOHW_FAILED·· 43

ARP_DETECTION_LOG·· 43

ARP_DUPLICATE_IPADDR_DETECT· 44

ARP_ENTRY_CONFLICT· 45

ARP_HOST_IP_CONFLICT· 45

ARP_RATE_EXCEEDED·· 46

ARP_SENDER_IP_INVALID·· 46

ARP_SENDER_MAC_INVALID·· 46

ARP_SENDER_SMACCONFLICT· 47

ARP_SENDER_SMACCONFLICT_VSI 47

ARP_SRC_MAC_FOUND_ATTACK· 48

ARP_SUP_ENABLE_FAILED·· 48

ARP_TARGET_IP_INVALID·· 48

ARP_THRESHOLD_REACHED·· 49

DUPIFIP· 49

DUPIP· 49

DUPVRRPIP· 50

ATK messages· 51

ATK_ICMP_ADDRMASK_REQ·· 51

ATK_ICMP_ADDRMASK_REQ_RAW·· 52

ATK_ICMP_ADDRMASK_REQ_RAW_SZ· 53

ATK_ICMP_ADDRMASK_REQ_SZ· 54

ATK_ICMP_ADDRMASK_RPL· 55

ATK_ICMP_ADDRMASK_RPL_RAW·· 56

ATK_ICMP_ADDRMASK_RPL_RAW_SZ· 57

ATK_ICMP_ADDRMASK_RPL_SZ· 58

ATK_ICMP_ECHO_REQ·· 59

ATK_ICMP_ECHO_REQ_RAW·· 60

ATK_ICMP_ECHO_REQ_RAW_SZ· 61

ATK_ICMP_ECHO_REQ_SZ· 62

ATK_ICMP_ECHO_RPL· 63

ATK_ICMP_ECHO_RPL_RAW·· 64

ATK_ICMP_ECHO_RPL_RAW_SZ· 65

ATK_ICMP_ECHO_RPL_SZ· 66

ATK_ICMP_FLOOD·· 67

ATK_ICMP_FLOOD_SZ· 67

ATK_ICMP_INFO_REQ·· 68

ATK_ICMP_INFO_REQ_RAW·· 69

ATK_ICMP_INFO_REQ_RAW_SZ· 70

ATK_ICMP_INFO_REQ_SZ· 71

ATK_ICMP_INFO_RPL· 72

ATK_ICMP_INFO_RPL_RAW·· 73

ATK_ICMP_INFO_RPL_RAW_SZ· 74

ATK_ICMP_INFO_RPL_SZ· 75

ATK_ICMP_LARGE· 76

ATK_ICMP_LARGE_RAW·· 77

ATK_ICMP_LARGE_RAW_SZ· 77

ATK_ICMP_LARGE_SZ· 78

ATK_ICMP_PARAPROBLEM·· 79

ATK_ICMP_PARAPROBLEM_RAW·· 80

ATK_ICMP_PARAPROBLEM_RAW_SZ· 81

ATK_ICMP_PARAPROBLEM_SZ· 82

ATK_ICMP_PINGOFDEATH·· 83

ATK_ICMP_PINGOFDEATH_RAW·· 84

ATK_ICMP_PINGOFDEATH_RAW_SZ· 84

ATK_ICMP_PINGOFDEATH_SZ· 85

ATK_ICMP_REDIRECT· 86

ATK_ICMP_REDIRECT_RAW·· 87

ATK_ICMP_REDIRECT_RAW_SZ· 88

ATK_ICMP_REDIRECT_SZ· 89

ATK_ICMP_SMURF· 90

ATK_ICMP_SMURF_RAW·· 91

ATK_ICMP_SMURF_RAW_SZ· 92

ATK_ICMP_SMURF_SZ· 93

ATK_ICMP_SOURCEQUENCH·· 94

ATK_ICMP_SOURCEQUENCH_RAW·· 95

ATK_ICMP_SOURCEQUENCH_RAW_SZ· 96

ATK_ICMP_SOURCEQUENCH_SZ· 97

ATK_ICMP_TIMEEXCEED·· 98

ATK_ICMP_TIMEEXCEED_RAW·· 99

ATK_ICMP_TIMEEXCEED_RAW_SZ· 100

ATK_ICMP_TIMEEXCEED_SZ· 101

ATK_ICMP_TRACEROUTE· 102

ATK_ICMP_TRACEROUTE_RAW·· 103

ATK_ICMP_TRACEROUTE_RAW_SZ· 103

ATK_ICMP_TRACEROUTE_SZ· 104

ATK_ICMP_TSTAMP_REQ·· 105

ATK_ICMP_TSTAMP_REQ_RAW·· 106

ATK_ICMP_TSTAMP_REQ_RAW_SZ· 107

ATK_ICMP_TSTAMP_REQ_SZ· 108

ATK_ICMP_TSTAMP_RPL· 109

ATK_ICMP_TSTAMP_RPL_RAW·· 110

ATK_ICMP_TSTAMP_RPL_RAW_SZ· 111

ATK_ICMP_TSTAMP_RPL_SZ· 112

ATK_ICMP_TYPE· 113

ATK_ICMP_TYPE_RAW·· 114

ATK_ICMP_TYPE_RAW_SZ· 115

ATK_ICMP_TYPE_SZ· 116

ATK_ICMP_UNREACHABLE· 117

ATK_ICMP_UNREACHABLE_RAW·· 118

ATK_ICMP_UNREACHABLE_RAW_SZ· 119

ATK_ICMP_UNREACHABLE_SZ· 120

ATK_ICMPV6_DEST_UNREACH·· 121

ATK_ICMPV6_DEST_UNREACH_RAW·· 122

ATK_ICMPV6_DEST_UNREACH_RAW_SZ· 122

ATK_ICMPV6_DEST_UNREACH_SZ· 123

ATK_ICMPV6_ECHO_REQ·· 124

ATK_ICMPV6_ECHO_REQ_RAW·· 125

ATK_ICMPV6_ECHO_REQ_RAW_SZ· 125

ATK_ICMPV6_ECHO_REQ_SZ· 126

ATK_ICMPV6_ECHO_RPL· 127

ATK_ICMPV6_ECHO_RPL_RAW·· 128

ATK_ICMPV6_ECHO_RPL_RAW_SZ· 128

ATK_ICMPV6_ECHO_RPL_SZ· 129

ATK_ICMPV6_FLOOD·· 130

ATK_ICMPV6_FLOOD_SZ· 130

ATK_ICMPV6_GROUPQUERY· 131

ATK_ICMPV6_GROUPQUERY_RAW·· 131

ATK_ICMPV6_GROUPQUERY_RAW_SZ· 132

ATK_ICMPV6_GROUPQUERY_SZ· 132

ATK_ICMPV6_GROUPREDUCTION·· 133

ATK_ICMPV6_GROUPREDUCTION_RAW·· 133

ATK_ICMPV6_GROUPREDUCTION_RAW_SZ· 134

ATK_ICMPV6_GROUPREDUCTION_SZ· 135

ATK_ICMPV6_GROUPREPORT· 136

ATK_ICMPV6_GROUPREPORT_RAW·· 136

ATK_ICMPV6_GROUPREPORT_RAW_SZ· 137

ATK_ICMPV6_GROUPREPORT_SZ· 137

ATK_ICMPV6_LARGE· 138

ATK_ICMPV6_LARGE_RAW·· 138

ATK_ICMPV6_LARGE_RAW_SZ· 139

ATK_ICMPV6_LARGE_SZ· 139

ATK_ICMPV6_PACKETTOOBIG·· 140

ATK_ICMPV6_PACKETTOOBIG_RAW·· 140

ATK_ICMPV6_PACKETTOOBIG_RAW_SZ· 141

ATK_ICMPV6_PACKETTOOBIG_SZ· 141

ATK_ICMPV6_PARAPROBLEM·· 142

ATK_ICMPV6_PARAPROBLEM_RAW·· 142

ATK_ICMPV6_PARAPROBLEM_RAW_SZ· 143

ATK_ICMPV6_PARAPROBLEM_SZ· 143

ATK_ICMPV6_TIMEEXCEED·· 144

ATK_ICMPV6_TIMEEXCEED_RAW·· 144

ATK_ICMPV6_TIMEEXCEED_RAW_SZ· 145

ATK_ICMPV6_TIMEEXCEED_SZ· 145

ATK_ICMPV6_TRACEROUTE· 146

ATK_ICMPV6_TRACEROUTE_RAW·· 147

ATK_ICMPV6_TRACEROUTE_RAW_SZ· 148

ATK_ICMPV6_TRACEROUTE_SZ· 149

ATK_ICMPV6_TYPE· 150

ATK_ICMPV6_TYPE _RAW_SZ· 150

ATK_ICMPV6_TYPE_RAW·· 151

ATK_ICMPV6_TYPE_SZ· 151

ATK_IP_OPTION·· 152

ATK_IP_OPTION_RAW·· 153

ATK_IP_OPTION_RAW_SZ· 154

ATK_IP_OPTION_SZ· 155

ATK_IP4_ACK_FLOOD·· 156

ATK_IP4_ACK_FLOOD_SZ· 156

ATK_IP4_DIS_PORTSCAN·· 157

ATK_IP4_DIS_PORTSCAN_SZ· 157

ATK_IP4_DNS_FLOOD·· 158

ATK_IP4_DNS_FLOOD_SZ· 158

ATK_IP4_FIN_FLOOD·· 159

ATK_IP4_FIN_FLOOD_SZ· 159

ATK_IP4_FRAGMENT· 160

ATK_IP4_FRAGMENT_RAW·· 161

ATK_IP4_FRAGMENT_RAW_SZ· 162

ATK_IP4_FRAGMENT_SZ· 163

ATK_IP4_HTTP_FLOOD·· 164

ATK_IP4_HTTP_FLOOD_SZ· 164

ATK_IP4_IMPOSSIBLE· 165

ATK_IP4_IMPOSSIBLE_RAW·· 166

ATK_IP4_IMPOSSIBLE_RAW_SZ· 166

ATK_IP4_IMPOSSIBLE_SZ· 167

ATK_IP4_IPSWEEP· 168

ATK_IP4_IPSWEEP_SZ· 168

ATK_IP4_PORTSCAN·· 169

ATK_IP4_PORTSCAN_SZ· 169

ATK_IP4_RST_FLOOD·· 170

ATK_IP4_RST_FLOOD_SZ· 170

ATK_IP4_SYN_FLOOD·· 171

ATK_IP4_SYN_FLOOD_SZ· 171

ATK_IP4_SYNACK_FLOOD·· 172

ATK_IP4_SYNACK_FLOOD_SZ· 172

ATK_IP4_TCP_ALLFLAGS· 173

ATK_IP4_TCP_ALLFLAGS_RAW·· 173

ATK_IP4_TCP_ALLFLAGS_RAW_SZ· 174

ATK_IP4_TCP_ALLFLAGS_SZ· 174

ATK_IP4_TCP_FINONLY· 175

ATK_IP4_TCP_FINONLY_RAW·· 175

ATK_IP4_TCP_FINONLY_RAW_SZ· 176

ATK_IP4_TCP_FINONLY_SZ· 176

ATK_IP4_TCP_INVALIDFLAGS· 177

ATK_IP4_TCP_INVALIDFLAGS_RAW·· 178

ATK_IP4_TCP_INVALIDFLAGS_RAW_SZ· 179

ATK_IP4_TCP_INVALIDFLAGS_SZ· 180

ATK_IP4_TCP_LAND·· 181

ATK_IP4_TCP_LAND_RAW·· 182

ATK_IP4_TCP_LAND_RAW_SZ· 182

ATK_IP4_TCP_LAND_SZ· 183

ATK_IP4_TCP_NULLFLAG·· 184

ATK_IP4_TCP_NULLFLAG_RAW·· 184

ATK_IP4_TCP_NULLFLAG_RAW_SZ· 185

ATK_IP4_TCP_NULLFLAG_SZ· 185

ATK_IP4_TCP_SYNFIN·· 186

ATK_IP4_TCP_SYNFIN_RAW·· 186

ATK_IP4_TCP_SYNFIN_RAW_SZ· 187

ATK_IP4_TCP_SYNFIN_SZ· 187

ATK_IP4_TCP_WINNUKE· 188

ATK_IP4_TCP_WINNUKE_RAW·· 189

ATK_IP4_TCP_WINNUKE_RAW_SZ· 189

ATK_IP4_TCP_WINNUKE_SZ· 190

ATK_IP4_TEARDROP· 191

ATK_IP4_TEARDROP_RAW·· 191

ATK_IP4_TEARDROP_RAW_SZ· 192

ATK_IP4_TEARDROP_SZ· 193

ATK_IP4_TINY_FRAGMENT· 194

ATK_IP4_TINY_FRAGMENT_RAW·· 195

ATK_IP4_TINY_FRAGMENT_RAW_SZ· 195

ATK_IP4_TINY_FRAGMENT_SZ· 196

ATK_IP4_UDP_BOMB· 197

ATK_IP4_UDP_BOMB_RAW·· 198

ATK_IP4_UDP_BOMB_RAW_SZ· 198

ATK_IP4_UDP_BOMB_SZ· 199

ATK_IP4_UDP_FLOOD·· 200

ATK_IP4_UDP_FLOOD_SZ· 200

ATK_IP4_UDP_FRAGGLE· 201

ATK_IP4_UDP_FRAGGLE_RAW·· 202

ATK_IP4_UDP_FRAGGLE_RAW_SZ· 202

ATK_IP4_UDP_FRAGGLE_SZ· 203

ATK_IP4_UDP_SNORK· 204

ATK_IP4_UDP_SNORK_RAW·· 204

ATK_IP4_UDP_SNORK_RAW_SZ· 205

ATK_IP4_UDP_SNORK_SZ· 206

ATK_IP6_ACK_FLOOD·· 207

ATK_IP6_ACK_FLOOD_SZ· 207

ATK_IP6_DIS_PORTSCAN·· 208

ATK_IP6_DIS_PORTSCAN_SZ· 208

ATK_IP6_DNS_FLOOD·· 209

ATK_IP6_DNS_FLOOD_SZ· 209

ATK_IP6_FIN_FLOOD·· 210

ATK_IP6_FIN_FLOOD_SZ· 210

ATK_IP6_FRAGMENT· 211

ATK_IP6_FRAGMENT_RAW·· 212

ATK_IP6_FRAGMENT_RAW_SZ· 212

ATK_IP6_FRAGMENT_SZ· 213

ATK_IP6_HTTP_FLOOD·· 214

ATK_IP6_HTTP_FLOOD_SZ· 214

ATK_IP6_IMPOSSIBLE· 215

ATK_IP6_IMPOSSIBLE_RAW·· 216

ATK_IP6_IMPOSSIBLE_RAW_SZ· 216

ATK_IP6_IMPOSSIBLE_SZ· 217

ATK_IP6_IPSWEEP· 217

ATK_IP6_IPSWEEP_SZ· 218

ATK_IP6_PORTSCAN·· 218

ATK_IP6_PORTSCAN_SZ· 219

ATK_IP6_RST_FLOOD·· 219

ATK_IP6_RST_FLOOD_SZ· 220

ATK_IP6_SYN_FLOOD·· 220

ATK_IP6_SYN_FLOOD_SZ· 221

ATK_IP6_SYNACK_FLOOD·· 221

ATK_IP6_SYNACK_FLOOD_SZ· 222

ATK_IP6_TCP_ALLFLAGS· 222

ATK_IP6_TCP_ALLFLAGS_RAW·· 223

ATK_IP6_TCP_ALLFLAGS_RAW_SZ· 223

ATK_IP6_TCP_ALLFLAGS_SZ· 224

ATK_IP6_TCP_FINONLY· 224

ATK_IP6_TCP_FINONLY_RAW·· 225

ATK_IP6_TCP_FINONLY_RAW_SZ· 225

ATK_IP6_TCP_FINONLY_SZ· 226

ATK_IP6_TCP_INVALIDFLAGS· 227

ATK_IP6_TCP_INVALIDFLAGS_RAW·· 228

ATK_IP6_TCP_INVALIDFLAGS_RAW_SZ· 229

ATK_IP6_TCP_INVALIDFLAGS_SZ· 230

ATK_IP6_TCP_LAND·· 231

ATK_IP6_TCP_LAND_RAW·· 231

ATK_IP6_TCP_LAND_RAW_SZ· 232

ATK_IP6_TCP_LAND_SZ· 232

ATK_IP6_TCP_NULLFLAG·· 233

ATK_IP6_TCP_NULLFLAG_RAW·· 233

ATK_IP6_TCP_NULLFLAG_RAW_SZ· 234

ATK_IP6_TCP_NULLFLAG_SZ· 234

ATK_IP6_TCP_SYNFIN·· 235

ATK_IP6_TCP_SYNFIN_RAW·· 235

ATK_IP6_TCP_SYNFIN_RAW_SZ· 236

ATK_IP6_TCP_SYNFIN_SZ· 236

ATK_IP6_TCP_WINNUKE· 237

ATK_IP6_TCP_WINNUKE_RAW·· 237

ATK_IP6_TCP_WINNUKE_RAW_SZ· 238

ATK_IP6_TCP_WINNUKE_SZ· 238

ATK_IP6_UDP_FLOOD·· 239

ATK_IP6_UDP_FLOOD_SZ· 239

ATK_IP6_UDP_FRAGGLE· 240

ATK_IP6_UDP_FRAGGLE_RAW·· 240

ATK_IP6_UDP_FRAGGLE_RAW_SZ· 241

ATK_IP6_UDP_FRAGGLE_SZ· 241

ATK_IP6_UDP_SNORK· 242

ATK_IP6_UDP_SNORK_RAW·· 242

ATK_IP6_UDP_SNORK_RAW_SZ· 243

ATK_IP6_UDP_SNORK_SZ· 243

ATK_IPOPT_ABNORMAL· 244

ATK_IPOPT_ABNORMAL_RAW·· 245

ATK_IPOPT_ABNORMAL_RAW_SZ· 246

ATK_IPOPT_ABNORMAL_SZ· 247

ATK_IPOPT_LOOSESRCROUTE· 248

ATK_IPOPT_LOOSESRCROUTE_RAW·· 249

ATK_IPOPT_LOOSESRCROUTE_RAW_SZ· 250

ATK_IPOPT_LOOSESRCROUTE_SZ· 251

ATK_IPOPT_RECORDROUTE· 252

ATK_IPOPT_RECORDROUTE_RAW·· 253

ATK_IPOPT_RECORDROUTE_RAW_SZ· 254

ATK_IPOPT_RECORDROUTE_SZ· 255

ATK_IPOPT_ROUTEALERT· 256

ATK_IPOPT_ROUTEALERT_RAW·· 257

ATK_IPOPT_ROUTEALERT_RAW_SZ· 258

ATK_IPOPT_ROUTEALERT_SZ· 259

ATK_IPOPT_SECURITY· 260

ATK_IPOPT_SECURITY_RAW·· 261

ATK_IPOPT_SECURITY_RAW_SZ· 262

ATK_IPOPT_SECURITY_SZ· 263

ATK_IPOPT_STREAMID·· 264

ATK_IPOPT_STREAMID_RAW·· 265

ATK_IPOPT_STREAMID_RAW_SZ· 266

ATK_IPOPT_STREAMID_SZ· 267

ATK_IPOPT_STRICTSRCROUTE· 268

ATK_IPOPT_STRICTSRCROUTE_RAW·· 269

ATK_IPOPT_STRICTSRCROUTE_RAW_SZ· 270

ATK_IPOPT_STRICTSRCROUTE_SZ· 271

ATK_IPOPT_TIMESTAMP· 272

ATK_IPOPT_TIMESTAMP_RAW·· 273

ATK_IPOPT_TIMESTAMP_RAW_SZ· 274

ATK_IPOPT_TIMESTAMP_SZ· 275

ATK_IPV6_EXT_HEADER·· 276

ATK_IPV6_EXT_HEADER_RAW·· 277

ATK_IPV6_EXT_HEADER_RAW_SZ· 277

ATK_IPV6_EXT_HEADER_SZ· 278

ATM·· 279

ATM_PVCDOWN·· 279

ATM_PVCUP· 280

BFD messages· 281

BFD_CHANGE_FSM·· 281

BFD_REACHED_UPPER_LIMIT· 281

BGP messages· 282

BGP_EXCEED_ROUTE_LIMIT· 282

BGP_EXCEEDS_THRESHOLD·· 282

BGP_LOG_ROUTE_FLAP· 283

BGP_MEM_ALERT· 283

BGP_PEER_LICENSE_REACHED·· 283

BGP_ROUTE_LICENSE_REACHED·· 284

BGP_STATE_CHANGED·· 284

BLS messages· 285

BLS_ENTRY_ADD·· 285

BLS_ENTRY_DEL· 285

BLS_IPV6_ENTRY_ADD·· 286

BLS_IPV6_ENTRY_DEL· 286

CFD messages· 287

CFD_CROSS_CCM·· 287

CFD_ERROR_CCM·· 287

CFD_LOST_CCM·· 288

CFD_RECEIVE_CCM·· 288

CFGMAN messages· 289

CFGMAN_ARCHIVE_SCP_FAIL· 289

CFGMAN_CFGCHANGED·· 290

CFGMAN_EXIT_FROM_CONFIGURE· 291

CFGMAN_OPTCOMPLETION·· 292

CONNLMT messages· 293

CONNLMT_IPV4_OVERLOAD·· 293

CONNLMT_IPV4_RECOVER·· 294

CONNLMT_IPV6_OVERLOAD·· 295

CONNLMT_IPV6_RECOVER·· 296

DEV messages· 297

BOARD_REBOOT· 297

BOARD_REMOVED·· 297

BOARD_STATE_FAULT· 298

BOARD_STATE_NORMAL· 298

CFCARD_INSERTED·· 299

CFCARD_REMOVED·· 299

CHASSIS_REBOOT· 300

DEV_CLOCK_CHANGE· 300

DEV_FAULT_TOOLONG·· 300

DYINGGASP· 301

FAN_ABSENT· 301

FAN_DIRECTION_NOT_PREFERRED·· 302

FAN_FAILED·· 302

FAN_RECOVERED·· 303

MAD_DETECT· 303

POWER_ABSENT· 304

POWER_FAILED·· 304

POWER_MONITOR_ABSENT· 305

POWER_MONITOR_FAILED·· 305

POWER_MONITOR_RECOVERED·· 306

POWER_RECOVERED·· 306

RPS_ABSENT· 307

RPS_NORMAL· 307

SUBCARD_FAULT· 308

SUBCARD_INSERTED·· 309

SUBCARD_REBOOT· 310

SUBCARD_REMOVED·· 311

SYSTEM_REBOOT· 311

TEMPERATURE_ALARM·· 312

TEMPERATURE_LOW·· 313

TEMPERATURE_NORMAL· 314

TEMPERATURE_SHUTDOWN·· 315

TEMPERATURE_WARNING·· 316

VCHK_VERSION_INCOMPATIBLE· 317

DHCP· 318

DHCP_NOTSUPPORTED·· 318

DHCP_NORESOURCES· 318

DHCPR· 319

DHCPR_SERVERCHANGE· 319

DHCPR_SWITCHMASTER·· 319

DHCPS messages· 320

DHCPS_ALLOCATE_IP· 320

DHCPS_CONFLICT_IP· 320

DHCPS_EXTEND_IP· 321

DHCPS_FILE· 321

DHCPS_RECLAIM_IP· 321

DHCPS_VERIFY_CLASS· 322

DHCPS6 messages· 323

DHCPS6_ALLOCATE_ADDRESS· 323

DHCPS6_ALLOCATE_PREFIX· 323

DHCPS6_CONFLICT_ADDRESS· 324

DHCPS6_EXTEND_ADDRESS· 324

DHCPS6_EXTEND_PREFIX· 325

DHCPS6_FILE· 325

DHCPS6_RECLAIM_ADDRESS· 326

DHCPS6_RECLAIM_PREFIX· 326

DHCPSP4· 327

DHCPSP4_FILE· 327

DHCPSP6· 328

DHCPSP6_FILE· 328

DIAG messages· 329

CPU_MINOR_RECOVERY· 329

CPU_MINOR_THRESHOLD·· 329

CPU_SEVERE_RECOVERY· 329

CPU_SEVERE_THRESHOLD·· 330

MEM_ALERT· 330

MEM_BELOW_THRESHOLD·· 331

MEM_EXCEED_THRESHOLD·· 332

DLDP messages· 333

DLDP_AUTHENTICATION_FAILED·· 333

DLDP_LINK_BIDIRECTIONAL· 333

DLDP_LINK_SHUTMODECHG·· 334

DLDP_LINK_UNIDIRECTIONAL· 334

DLDP_NEIGHBOR_AGED·· 335

DLDP_NEIGHBOR_CONFIRMED·· 335

DLDP_NEIGHBOR_DELETED·· 336

DOT1X messages· 337

DOT1X_CONFIG_NOTSUPPORT· 337

DOT1X_LOGIN_FAILURE· 337

DOT1X_LOGIN_SUCC·· 338

DOT1X_LOGIN_SUCC (in open mode) 338

DOT1X_LOGOFF· 339

DOT1X_LOGOFF (in open mode) 339

DOT1X_LOGOFF_ABNORMAL· 340

DOT1X_LOGOFF_ABNORMAL (in open mode) 340

DOT1X_MACBINDING_EXIST· 341

DOT1X_NOTENOUGH_EADFREEIP_RES· 341

DOT1X_NOTENOUGH_EADFREERULE_RES· 341

DOT1X_NOTENOUGH_EADMACREDIR_RES· 342

DOT1X_NOTENOUGH_EADPORTREDIR_RES· 342

DOT1X_NOTENOUGH_ENABLEDOT1X_RES· 342

DOT1X_SMARTON_FAILURE· 343

DOT1X_UNICAST_NOT_EFFECTIVE· 343

DRNI 344

DRNI_IFEVENT_DR_BIND·· 344

DRNI_IFEVENT_DR_GLOBALDOWN·· 344

DRNI_IFEVENT_DR_GLOBALUP· 344

DRNI_IFEVENT_DR_NOSELECTED·· 345

DRNI_IFEVENT_DR_PEER_NOSELECTED·· 345

DRNI_IFEVENT_DR_PEER_SELECTED·· 345

DRNI_IFEVENT_DR_SELECTED·· 346

DRNI_IFEVENT_DR_UNBIND·· 346

DRNI_IFEVENT_IPP_BIND·· 346

DRNI_IFEVENT_IPP_DOWN·· 347

DRNI_IFEVENT_IPP_UNBIND·· 347

DRNI_IFEVENT_IPP_UP· 347

DRNI_IPP_BLOCK· 348

DRNI_IPP_UNBLOCK· 348

DRNI_KEEPALIVEINTERVAL_MISMATCH·· 348

DRNI_KEEPALIVELINK_DOWN·· 349

DRNI_KEEPALIVELINK_UP· 349

DRNI_SECONDARY_MADDOWN·· 349

DRNI_SYSEVENT_DEVICEROLE_CHANGE· 350

DRNI_SYSEVENT_MAC_CHANGE· 350

DRNI_SYSEVENT_NUMBER_CHANGE· 350

DRNI_SYSEVENT_PRIORITY_CHANGE· 351

EDEV messages· 352

EDEV_FAILOVER_GROUP_STATE_CHANGE· 352

ERPS messages· 353

ERPS_FSM_CHANGED·· 353

ETHOAM messages· 354

ETHOAM_CONNECTION_FAIL_DOWN·· 354

ETHOAM_CONNECTION_FAIL_TIMEOUT· 354

ETHOAM_CONNECTION_FAIL_UNSATISF· 354

ETHOAM_CONNECTION_SUCCEED·· 355

ETHOAM_DISABLE· 355

ETHOAM_DISCOVERY_EXIT· 355

ETHOAM_ENABLE· 356

ETHOAM_ENTER_LOOPBACK_CTRLLED·· 356

ETHOAM_ENTER_LOOPBACK_CTRLLING·· 356

ETHOAM_LOCAL_DYING_GASP· 357

ETHOAM_LOCAL_ERROR_FRAME· 357

ETHOAM_LOCAL_ERROR_FRAME_PERIOD·· 357

ETHOAM_LOCAL_ERROR_FRAME_SECOND·· 358

ETHOAM_LOCAL_ERROR_SYMBOL· 358

ETHOAM_LOCAL_LINK_FAULT· 358

ETHOAM_LOOPBACK_EXIT· 359

ETHOAM_LOOPBACK_EXIT_ERROR_STATU·· 359

ETHOAM_LOOPBACK_NO_RESOURCE· 359

ETHOAM_LOOPBACK_NOT_SUPPORT· 360

ETHOAM_QUIT_LOOPBACK_CTRLLED·· 360

ETHOAM_QUIT_LOOPBACK_CTRLLING·· 360

ETHOAM_REMOTE_CRITICAL· 361

ETHOAM_REMOTE_DYING_GASP· 361

ETHOAM_REMOTE_ERROR_FRAME· 361

ETHOAM_REMOTE_ERROR_FRAME_PERIOD·· 362

ETHOAM_REMOTE_ERROR_FRAME_SECOND·· 362

ETHOAM_REMOTE_ERROR_SYMBOL· 362

ETHOAM_REMOTE_EXIT· 363

ETHOAM_REMOTE_FAILURE_RECOVER·· 363

ETHOAM_REMOTE_LINK_FAULT· 363

ETHOAM_NO_ENOUGH_RESOURCE· 364

ETHOAM_NOT_CONNECTION_TIMEOUT· 364

EVB messages· 365

EVB_AGG_FAILED·· 365

EVB_LICENSE_EXPIRE· 365

EVB_VSI_OFFLINE· 365

EVB_VSI_ONLINE· 366

EVIISIS messages· 367

EVIISIS_LICENSE_EXPIRED·· 367

EVIISIS_LICENSE_EXPIRED_TIME· 367

EVIISIS_LICENSE_UNAVAILABLE· 367

EVIISIS_NBR_CHG·· 368

FCLINK messages· 369

FCLINK_FDISC_REJECT_NORESOURCE· 369

FCLINK_FLOGI_REJECT_NORESOURCE· 369

FCOE messages· 370

FCOE_INTERFACE_NOTSUPPORT_FCOE· 370

FCOE_LAGG_BIND_ACTIVE· 370

FCOE_LAGG_BIND_DEACTIVE· 371

FCZONE messages· 372

FCZONE_HARDZONE_DISABLED·· 372

FCZONE_HARDZONE_ENABLED·· 372

FCZONE_ISOLATE_NEIGHBOR·· 373

FCZONE_ISOLATE_ALLNEIGHBOR·· 373

FCZONE_ISOLATE_CLEAR_VSAN·· 374

FCZONE_ISOLATE_CLEAR_ALLVSAN·· 374

FCZONE_DISTRIBUTE_FAILED·· 375

FIB messages· 376

FIB_FILE· 376

FILTER messages· 377

FILTER_EXECUTION_ICMP· 377

FILTER_EXECUTION_ICMPV6· 378

FILTER_IPV4_EXECUTION·· 379

FILTER_IPV6_EXECUTION·· 380

FIPS messages· 381

FCOE_FIPS_HARD_RESOURCE_NOENOUGH·· 381

FCOE_FIPS_HARD_RESOURCE_RESTORE· 381

FS messages· 382

FS_UNFORMATTED_PARTITION·· 382

FTPD messages· 383

FTP_ACL_DENY· 383

FTPD_REACH_SESSION_LIMIT· 383

FTPD_AUTHOR_FAILED·· 384

HA messages· 385

HA_BATCHBACKUP_FINISHED·· 385

HA_BATCHBACKUP_STARTED·· 385

HA_STANDBY_NOT_READY· 385

HA_STANDBY_TO_MASTER·· 386

HQOS messages· 387

HQOS_DP_SET_FAIL· 387

HQOS_FP_SET_FAIL· 387

HQOS_POLICY_APPLY_FAIL· 388

HQOS_POLICY_APPLY_FAIL· 388

HTTPD messages· 389

HTTPD_CONNECT· 389

HTTPD_CONNECT_TIMEOUT· 389

HTTPD_DISCONNECT· 389

HTTPD_FAIL_FOR_ACL· 390

HTTPD_FAIL_FOR_ACP· 390

HTTPD_REACH_CONNECT_LIMIT· 390

IFNET messages· 391

IF_BUFFER_CONGESTION_OCCURRENCE· 391

IF_BUFFER_CONGESTION_CLEAR·· 391

INTERFACE_NOTSUPPRESSED·· 392

INTERFACE_SUPPRESSED·· 392

LINK_UPDOWN·· 392

PHY_UPDOWN·· 393

PROTOCOL_UPDOWN·· 393

TUNNEL_LINK_UPDOWN·· 393

TUNNEL_PHY_UPDOWN·· 394

VLAN_MODE_CHANGE· 394

IKE messages· 395

IKE_P1_SA_ESTABLISH_FAIL· 395

IKE_P2_SA_ESTABLISH_FAIL· 395

IKE_P2_SA_TERMINATE· 396

IPSEC messages· 397

IPSEC_FAILED_ADD_FLOW_TABLE· 397

IPSEC_PACKET_DISCARDED·· 397

IPSEC_SA_ESTABLISH·· 398

IPSEC_SA_ESTABLISH_FAIL· 398

IPSEC_SA_INITINATION·· 399

IPSEC_SA_TERMINATE· 399

IPSG messages· 400

IPSG_ADDENTRY_ERROR·· 400

IPSG_DELENTRY_ERROR·· 401

IPSG_ADDEXCLUDEDVLAN_ERROR·· 401

IPSG_DELEXCLUDEDVLAN_ERROR·· 402

IRDP messages· 403

IRDP_EXCEED_ADVADDR_LIMIT· 403

IRF· 404

IRF_LINK_BLOCK· 404

IRF_LINK_DOWN·· 404

IRF_LINK_UP· 404

IRF_MEMBERID_CONFLICT· 405

IRF_MERGE· 405

IRF_MERGE_NEED_REBOOT· 405

IRF_MERGE_NOT_NEED_REBOOT· 406

ISIS messages· 407

ISIS_LSP_CONFLICT· 407

ISIS_MEM_ALERT· 407

ISIS_NBR_CHG·· 408

ISSU messages· 409

ISSU_ROLLBACKCHECKNORMAL· 409

ISSU_PROCESSWITCHOVER·· 409

L2PT messages· 410

L2PT_SET_MULTIMAC_FAILED·· 410

L2PT_CREATE_TUNNELGROUP_FAILED·· 410

L2PT_ADD_GROUPMEMBER_FAILED·· 410

L2PT_ENABLE_DROP_FAILED·· 411

L2TP messages· 412

L2TPV2_TUNNEL_EXCEED_LIMIT· 412

L2TPV2_SESSION_EXCEED_LIMIT· 412

L2VPN messages· 413

L2VPN_BGPVC_CONFLICT_LOCAL· 413

L2VPN_BGPVC_CONFLICT_REMOTE· 413

L2VPN_HARD_RESOURCE_NOENOUGH·· 414

L2VPN_HARD_RESOURCE_RESTORE· 414

L2VPN_LABEL_DUPLICATE· 414

VXLAN_LICENSE_UNAVAILABLE· 415

LAGG messages· 416

LAGG_ACTIVE· 416

LAGG_INACTIVE_AICFG·· 416

LAGG_INACTIVE_BFD·· 417

LAGG_INACTIVE_CONFIGURATION·· 417

LAGG_INACTIVE_DUPLEX· 418

LAGG_INACTIVE_HARDWAREVALUE· 418

LAGG_INACTIVE_LOWER_LIMIT· 419

LAGG_INACTIVE_PARTNER·· 419

LAGG_INACTIVE_PHYSTATE· 419

LAGG_INACTIVE_RESOURCE_INSUFICIE· 420

LAGG_INACTIVE_SPEED·· 420

LAGG_INACTIVE_UPPER_LIMIT· 420

LDP messages· 421

LDP_MPLSLSRID_CHG·· 421

LDP_SESSION_CHG·· 422

LDP_SESSION_GR·· 423

LDP_SESSION_SP· 423

LLDP messages· 424

LLDP_CREATE_NEIGHBOR·· 424

LLDP_DELETE_NEIGHBOR·· 424

LLDP_LESS_THAN_NEIGHBOR_LIMIT· 425

LLDP_NEIGHBOR_AGE_OUT· 425

LLDP_NEIGHBOR_PROTECTION_BLOCK· 426

LLDP_NEIGHBOR_PROTECTION_DOWN·· 426

LLDP_NEIGHBOR_PROTECTION_UNBLOCK· 427

LLDP_NEIGHBOR_PROTECTION_UP· 427

LLDP_PVID_INCONSISTENT· 427

LLDP_REACH_NEIGHBOR_LIMIT· 428

LOAD messages· 429

BOARD_LOADING·· 429

LOAD_FAILED·· 429

LOAD_FINISHED·· 430

LOGIN messages· 431

LOGIN_FAILED·· 431

LOGIN_ INVALID_USERNAME_PWD·· 431

LPDT messages· 432

LPDT_LOOPED·· 432

LPDT_RECOVERED·· 432

LPDT_VLAN_LOOPED·· 432

LPDT_VLAN_RECOVERED·· 433

LS messages· 434

LS_ADD_USER_TO_GROUP· 434

LS_AUTHEN_FAILURE· 434

LS_AUTHEN_SUCCESS· 435

LS_DEL_USER_FROM_GROUP· 435

LS_DELETE_PASSWORD_FAIL· 435

LS_PWD_ADDBLACKLIST· 436

LS_PWD_CHGPWD_FOR_AGEDOUT· 436

LS_PWD_CHGPWD_FOR_AGEOUT· 436

LS_PWD_CHGPWD_FOR_COMPOSITION·· 437

LS_PWD_CHGPWD_FOR_FIRSTLOGIN·· 437

LS_PWD_CHGPWD_FOR_LENGTH·· 437

LS_PWD_FAILED2WRITEPASS2FILE· 438

LS_PWD_MODIFY_FAIL· 438

LS_PWD_MODIFY_SUCCESS· 438

LS_REAUTHEN_FAILURE· 439

LS_UPDATE_PASSWORD_FAIL· 439

LS_USER_CANCEL· 439

LS_USER_PASSWORD_EXPIRE· 440

LS_USER_ROLE_CHANGE· 440

LSPV messages· 441

LSPV_PING_STATIS_INFO·· 441

MAC messages· 442

MAC_DRIVER_ADD_ENTRY· 442

MAC_TABLE_FULL_GLOBAL· 442

MAC_TABLE_FULL_PORT· 443

MAC_TABLE_FULL_VLAN·· 443

MAC_VLAN_LEARNLIMIT_NORESOURCE· 443

MAC_VLAN_LEARNLIMIT_NOTSUPPORT· 444

MACA messages· 445

MACA_ENABLE_NOT_EFFECTIVE· 445

MACA_LOGIN_FAILURE· 445

MACA_LOGIN_SUCC·· 446

MACA_LOGIN_SUCC (in open mode) 446

MACA_LOGOFF· 447

MACA_LOGOFF (in open mode) 447

MACSEC messages· 448

MACSEC_MKA_KEEPALIVE_TIMEOUT· 448

MACSEC_MKA_PRINCIPAL_ACTOR·· 448

MACSEC_MKA_SAK_REFRESH·· 448

MACSEC_MKA_SESSION_REAUTH·· 449

MACSEC_MKA_SESSION_SECURED·· 449

MACSEC_MKA_SESSION_START· 450

MACSEC_MKA_SESSION_STOP· 450

MACSEC_MKA_SESSION_UNSECURED·· 451

MBFD messages· 452

MBFD_TRACEROUTE_FAILURE· 452

MBUF messages· 453

MBUF_DATA_BLOCK_CREATE_FAIL· 453

MDC messages· 454

MDC_CREATE_ERR·· 454

MDC_CREATE· 454

MDC_DELETE· 454

MDC_KERNEL_EVENT_TOOLONG·· 455

MDC_LICENSE_EXPIRE· 455

MDC_NO_FORMAL_LICENSE· 455

MDC_NO_LICENSE_EXIT· 456

MDC_OFFLINE· 456

MDC_ONLINE· 456

MDC_STATE_CHANGE· 457

MFIB messages· 458

MFIB_MEM_ALERT· 458

MGROUP messages· 459

MGROUP_APPLY_SAMPLER_FAIL· 459

MGROUP_RESTORE_CPUCFG_FAIL· 459

MGROUP_RESTORE_IFCFG_FAIL· 460

MGROUP_SYNC_CFG_FAIL· 460

MPLS messages· 461

MPLS_HARD_RESOURCE_NOENOUGH·· 461

MPLS_HARD_RESOURCE_RESTORE· 461

MTLK messages· 462

MTLK_UPLINK_STATUS_CHANGE· 462

NAT messages· 463

NAT_ADDR_BIND_CONFLICT· 463

NAT_FAILED_ADD_FLOW_TABLE· 463

NAT_FLOW·· 464

NAT_SERVICE_CARD_RECOVER_FAILURE· 465

NAT_SERVER_INVALID·· 466

NAT_FAILED_ADD_FLOW_RULE· 466

ND messages· 467

ND_CONFLICT· 467

ND_DUPADDR·· 467

ND_HOST_IP_CONFLICT· 468

ND_MAC_CHECK· 468

ND_RAGUARD_DROP· 469

ND_SET_PORT_TRUST_NORESOURCE· 469

ND_SET_VLAN_REDIRECT_NORESOURCE· 469

NETCONF messages· 470

CLI 470

row-operation· 471

THREAD·· 471

NQA messages· 472

NQA_LOG_UNREACHABLE· 472

NTP messages· 473

NTP_CLOCK_CHANGE· 473

NTP_LEAP_CHANGE· 473

NTP_SOURCE_CHANGE· 474

NTP_SOURCE_LOST· 474

NTP_STRATUM_CHANGE· 474

OBJP messages· 475

OBJP_ACCELERATE_NO_RES· 475

OBJP_ACCELERATE_NOT_SUPPORT· 475

OBJP_ACCELERATE_UNK_ERR·· 476

OFP messages· 477

OFP_ACTIVE· 477

OFP_ACTIVE_FAILED·· 477

OFP_CONNECT· 477

OFP_FAIL_OPEN·· 478

OFP_FLOW_ADD·· 478

OFP_FLOW_ADD_DUP· 479

OFP_FLOW_ADD_FAILED·· 479

OFP_FLOW_ADD_FAILED·· 480

OFP_FLOW_ADD_TABLE_MISS· 480

OFP_FLOW_ADD_TABLE_MISS_FAILED·· 481

OFP_FLOW_DEL· 481

OFP_FLOW_DEL_TABLE_MISS· 482

OFP_FLOW_DEL_TABLE_MISS_FAILED·· 482

OFP_FLOW_MOD·· 483

OFP_FLOW_MOD_FAILED·· 483

OFP_FLOW_MOD_TABLE_MISS· 484

OFP_FLOW_MOD_TABLE_MISS_FAILED·· 484

OFP_FLOW_RMV_GROUP· 485

OFP_FLOW_RMV_HARDTIME· 485

OFP_FLOW_RMV_IDLETIME· 485

OFP_FLOW_RMV_METER·· 486

OFP_FLOW_UPDATE_FAILED·· 486

OFP_GROUP_ADD·· 487

OFP_GROUP_ADD_FAILED·· 487

OFP_GROUP_DEL· 488

OFP_GROUP_MOD·· 488

OFP_GROUP_MOD_FAILED·· 489

OFP_METER_ADD·· 489

OFP_METER_ADD_FAILED·· 489

OFP_METER_DEL· 490

OFP_METER_MOD·· 490

OFP_METER_MOD_FAILED·· 491

OFP_MISS_RMV_GROUP· 491

OFP_MISS_RMV_HARDTIME· 491

OFP_MISS_RMV_IDLETIME· 492

OFP_MISS_RMV_METER·· 492

OFP_RADARDETECTION·· 492

OPENSRC (FreeRADIUS) messages· 493

HUP event 493

Process restart event 493

Process start event 494

User authentication· 495

OPTMOD messages· 498

BIAS_HIGH·· 498

BIAS_LOW·· 498

BIAS_NORMAL· 499

CFG_ERR·· 499

CHKSUM_ERR·· 499

FIBER_SFP MODULE_INVALID·· 500

FIBER_SFPMODULE_NOWINVALID·· 500

IO_ERR·· 501

MOD_ALM_OFF· 501

MOD_ALM_ON·· 501

MODULE_IN·· 502

MODULE_OUT· 502

PHONY_MODULE· 502

RX_ALM_OFF· 503

RX_ALM_ON·· 503

RX_POW_HIGH·· 503

RX_POW_LOW·· 504

RX_POW_NORMAL· 504

TEMP_HIGH·· 504

TEMP_LOW·· 505

TEMP_NORMAL· 505

TX_ALM_OFF· 505

TX_ALM_ON·· 506

TX_POW_HIGH·· 506

TX_POW_LOW·· 506

TX_POW_NORMAL· 507

TYPE_ERR·· 507

VOLT_HIGH·· 507

VOLT_LOW·· 508

VOLT_NORMAL· 508

OSPF messages· 509

OSPF_DUP_RTRID_NBR·· 509

OSPF_IP_CONFLICT_INTRA· 509

OSPF_LAST_NBR_DOWN·· 510

OSPF_MEM_ALERT· 510

OSPF_NBR_CHG·· 511

OSPF_RT_LMT· 511

OSPF_RTRID_CHG·· 511

OSPF_RTRID_CONFLICT_INTER·· 512

OSPF_RTRID_CONFLICT_INTRA· 512

OSPF_VLINKID_CHG·· 512

OSPFV3 messages· 513

OSPFV3_LAST_NBR_DOWN·· 513

OSPFV3_MEM_ALERT· 513

OSPFV3_NBR_CHG·· 514

OSPFV3_RT_LMT· 514

Packet capture messages· 515

PKTCPT_AP_OFFLINE· 515

PKTCPT_AREADY_EXIT· 515

PKTCPT_CONN_FAIL· 516

PKTCPT_INVALID_FILTER·· 516

PKTCPT_LOGIN_DENIED·· 516

PKTCPT_MEMORY_ALERT· 517

PKTCPT_OPEN_FAIL· 517

PKTCPT_OPERATION_TIMEOUT· 517

PKTCPT_SERVICE_FAIL· 518

PKTCPT_UNKNOWN_ERROR·· 518

PKTCPT_UPLOAD_ERROR·· 518

PKTCPT_WRITE_FAIL· 519

PBB messages· 520

PBB_JOINAGG_WARNING·· 520

PBR messages· 521

PBR_HARDWARE_ERROR·· 521

PCE messages· 522

PCE_PCEP_SESSION_CHG·· 522

PEX messages (IRF 3) 523

PEX_ASSOCIATEID_MISMATCHING·· 523

PEX_CONFIG_ERROR·· 524

PEX_CONNECTION_ERROR·· 524

PEX_FORBID_STACK· 525

PEX_LINK_BLOCK· 525

PEX_LINK_DOWN·· 526

PEX_LINK_FORWARD·· 526

PEX_REG_JOININ·· 527

PEX_REG_LEAVE· 527

PEX_REG_REQUEST· 528

PEX_STACKCONNECTION_ERROR·· 528

PEX messages (IRF 3.1) 529

PEX_AUTOCONFIG_BAGG_ASSIGNMEMBER·· 529

PEX_AUTOCONFIG_BAGG_CREATE· 529

PEX_AUTOCONFIG_BAGG_NORESOURCE· 529

PEX_AUTOCONFIG_BAGG_REMOVEMEMBER·· 530

PEX_AUTOCONFIG_CAPABILITY_ENABLE· 530

PEX_AUTOCONFIG_CASCADELIMIT· 530

PEX_AUTOCONFIG_CONNECTION_ERROR·· 531

PEX_AUTOCONFIG_DIFFGROUPNUMBER·· 531

PEX_AUTOCONFIG_DYNAMICBAGG_STP· 532

PEX_AUTOCONFIG_GROUP_CREATE· 532

PEX_AUTOCONFIG_NONUMBERRESOURCE· 532

PEX_AUTOCONFIG_NOT_CASCADEPORT· 533

PEX_AUTOCONFIG_NUMBER_ASSIGN·· 533

PEX_LLDP_DISCOVER·· 534

PEX_MEMBERID_EXCEED·· 534

PEX_PECSP_OPEN_RCVD·· 534

PEX_PECSP_OPEN_SEND·· 535

PEX_PECSP_TIMEOUT· 535

PIM messages· 536

PIM_MEM_ALERT· 536

PIM_NBR_DOWN·· 536

PIM_NBR_UP· 537

PING messages· 538

PING_STATISTICS· 538

PING_VPN_STATISTICS· 539

PKI messages· 540

REQUEST_CERT_FAIL· 540

REQUEST_CERT_SUCCESS· 540

PKT2CPU messages· 541

PKT2CPU_NO_RESOURCE· 541

Portal messages· 542

PORTAL_RULE_FAILED·· 542

PORTSEC messages· 543

PORTSEC_ACL_FAILURE· 543

PORTSEC_CAR_FAILURE· 543

PORTSEC_CREATEAC_FAILURE· 544

PORTSEC_LEARNED_MACADDR·· 544

PORTSEC_NTK_NOT_EFFECTIVE· 544

PORTSEC_PORTMODE_NOT_EFFECTIVE· 545

PORTSEC_PROFILE_FAILURE· 545

PORTSEC_URL_FAILURE· 545

PORTSEC_VIOLATION·· 546

PPP messages· 547

IPPOOL_ADDRESS_EXHAUSTED·· 547

PPP_USER_LOGON_SUCCESS· 547

PPP_USER_LOGON_FAILED·· 548

PPP_USER_LOGOFF· 548

PWDCTL messages· 550

ADDBLACKLIST· 550

CHANGEPASSWORD·· 550

FAILEDTOWRITEPWD·· 550

QOS messages· 551

MIRROR_SYNC_CFG_FAIL· 551

QOS_CAR_APPLYUSER_FAIL· 551

QOS_CBWFQ_REMOVED·· 552

QOS_GTS_APPLYUSER_FAIL· 552

QOS_NOT_ENOUGH_BANDWIDTH·· 553

QOS_POLICY_APPLYCOPP_CBFAIL· 553

QOS_POLICY_APPLYCOPP_FAIL· 554

QOS_POLICY_APPLYGLOBAL_CBFAIL· 554

QOS_POLICY_APPLYGLOBAL_FAIL· 555

QOS_POLICY_APPLYIF_CBFAIL· 555

QOS_POLICY_APPLYIF_FAIL· 556

QOS_POLICY_APPLYUSER_FAIL· 556

QOS_POLICY_APPLYVLAN_CBFAIL· 557

QOS_POLICY_APPLYVLAN_FAIL· 557

QOS_QMPROFILE_APPLYUSER_FAIL· 558

QOS_QMPROFILE_MODIFYQUEUE_FAIL· 558

WRED_TABLE_CFG_FAIL· 559

RADIUS messages· 560

RADIUS_AUTH_FAILURE· 560

RADIUS_AUTH_SUCCESS· 560

RADIUS_DELETE_HOST_FAIL· 560

RDDC messages· 561

RDDC_ACTIVENODE_CHANGE· 561

RESMON· 562

RESMON_MINOR·· 562

RESMON_MINOR_RECOVERY· 562

RESMON_SEVERE· 563

RESMON_SEVERE_RECOVERY· 563

RESMON_USEDUP· 564

RESMON_USEDUP_RECOVERY· 564

RIP messages· 565

RIP_MEM_ALERT· 565

RIP_RT_LMT· 565

RIPNG messages· 566

RIPNG_MEM_ALERT· 566

RIPNG_RT_LMT· 566

RM messages· 567

RM_ACRT_REACH_LIMIT· 567

RM_ACRT_REACH_THRESVALUE· 567

RM_THRESHLD_VALUE_REACH·· 568

RM_TOTAL_THRESHLD_VALUE_REACH·· 568

RPR messages· 569

RPR_EXCEED_MAX_SEC_MAC·· 569

RPR_EXCEED_MAX_SEC_MAC_OVER·· 569

RPR_EXCEED_MAX_STATION·· 569

RPR_EXCEED_MAX_STATION_OVER·· 570

RPR_EXCEED_RESERVED_RATE· 570

RPR_EXCEED_RESERVED_RATE_OVER·· 570

RPR_IP_DUPLICATE· 571

RPR_IP_DUPLICATE_OVER·· 571

RPR_JUMBO_INCONSISTENT· 571

RPR_JUMBO_INCONSISTENT_OVER·· 572

RPR_MISCABLING·· 572

RPR_MISCABLING_OVER·· 572

RPR_PROTECTION_INCONSISTENT· 573

RPR_PROTECTION_INCONSISTENT_OVER·· 573

RPR_SEC_MAC_DUPLICATE· 573

RPR_SEC_MAC_DUPLICATE_OVER·· 574

RPR_TOPOLOGY_INCONSISTENT· 574

RPR_TOPOLOGY_INCONSISTENT_OVER·· 574

RPR_TOPOLOGY_INSTABILITY· 575

RPR_TOPOLOGY_INSTABILITY_OVER·· 575

RPR_TOPOLOGY_INVALID·· 575

RPR_TOPOLOGY_INVALID_OVER·· 576

RRPP messages· 577

RRPP_RING_FAIL· 577

RRPP_RING_RESTORE· 577

RTM messages· 578

RTM_TCL_NOT_EXIST· 578

RTM_TCL_MODIFY· 578

RTM_TCL_LOAD_FAILED·· 578

SCM messages· 579

PROCESS_ABNORMAL· 579

PROCESS_ACTIVEFAILED·· 579

SCM_ABNORMAL_REBOOT (Distributed devices–Centralized IRF devices–In standalone mode/Distributed devices–In IRF mode) 580

SCM_ABNORMAL_REBOOT· 580

SCM_ABNORMAL_REBOOTMDC·· 581

SCM_ABORT_RESTORE· 581

SCM_INSMOD_ADDON_TOOLONG·· 582

SCM_KERNEL_INIT_TOOLONG·· 582

SCM_PROCESS_STARTING_TOOLONG·· 582

SCM_PROCESS_STILL_STARTING·· 583

SCM_SKIP_PROCESS· 583

SCM_SKIP_PROCESS· 583

SCRLSP messages· 584

SCRLSP_LABEL_DUPLICATE· 584

SESSION messages· 585

SESSION_IPV4_FLOW·· 585

SESSION_IPV6_FLOW·· 586

SFLOW messages· 588

SFLOW_HARDWARE_ERROR·· 588

SHELL messages· 589

SHELL_CMD·· 589

SHELL_CMD_CONFIRM·· 589

SHELL_CMD_EXECUTEFAIL· 590

SHELL_CMD_INPUT· 590

SHELL_CMD_INPUT_TIMEOUT· 590

SHELL_CMD_MATCHFAIL· 591

SHELL_CMDDENY· 591

SHELL_CMDFAIL· 591

SHELL_CRITICAL_CMDFAIL· 592

SHELL_LOGIN·· 592

SHELL_LOGOUT· 592

SLSP messages· 593

SLSP_LABEL_DUPLICATE· 593

SMLK messages· 594

SMLK_LINK_SWITCH·· 594

SNMP messages· 595

SNMP_ACL_RESTRICTION·· 595

SNMP_AUTHENTICATION_FAILURE· 595

SNMP_GET· 595

SNMP_NOTIFY· 596

SNMP_SET· 596

SNMP_USM_NOTINTIMEWINDOW·· 597

SSHS messages· 598

SSHS_ACL_DENY· 598

SSHS_ALGORITHM_MISMATCH·· 598

SSHS_AUTH_EXCEED_RETRY_TIMES· 598

SSHS_AUTH_FAIL· 599

SSHS_AUTH_TIMEOUT· 599

SSHS_CONNECT· 599

SSHS_DECRYPT_FAIL· 600

SSHS_DISCONNECT· 600

SSHS_ENCRYPT_FAIL· 600

SSHS_LOG·· 601

SSHS_MAC_ERROR·· 601

SSHS_REACH_SESSION_LIMIT· 601

SSHS_REACH_USER_LIMIT· 602

SSHS_SCP_OPER·· 602

SSHS_SFTP_OPER·· 603

SSHS_SRV_UNAVAILABLE· 603

SSHS_VERSION_MISMATCH·· 603

STAMGR messages· 604

STAMGR_ADD_FAILVLAN·· 604

STAMGR_ADDBAC_INFO·· 604

STAMGR_ADDSTA_INFO·· 604

STAMGR_AUTHORACL_FAILURE· 605

STAMGR_AUTHORUSERPROFILE_FAILURE· 605

STAMGR_CLIENT_OFFLINE· 606

STAMGR_CLIENT_ONLINE· 606

STAMGR_DELBAC_INFO·· 606

STAMGR_DELSTA_INFO·· 607

STAMGR_DOT1X_LOGIN_FAILURE· 607

STAMGR_DOT1X_LOGIN_SUCC·· 608

STAMGR_DOT1X_LOGOFF· 608

STAMGR_MACA_LOGIN_FAILURE· 609

STAMGR_MACA_LOGIN_SUCC·· 609

STAMGR_MACA_LOGOFF· 610

STAMGR_STAIPCHANGE_INFO·· 610

STAMGR_TRIGGER_IP· 611

STM messages· 612

STM_AUTO_UPDATE_FAILED·· 612

STM_AUTO_UPDATE_FAILED·· 613

STM_AUTO_UPDATE_FINISHED·· 613

STM_AUTO_UPDATE_FINISHED·· 614

STM_AUTO_UPDATING·· 614

STM_AUTO_UPDATING·· 614

STM_LINK_DOWN·· 615

STM_LINK_MERGE· 615

STM_LINK_TIMEOUT· 615

STM_LINK_UP· 616

STM_MERGE_NEED_REBOOT· 616

STM_MERGE_NOT_NEED_REBOOT· 616

STM_SAMEMAC·· 617

STM_SOMER_CHECK· 617

STP messages· 618

STP_BPDU_PROTECTION·· 618

STP_BPDU_RECEIVE_EXPIRY· 618

STP_CONSISTENCY_RESTORATION·· 618

STP_DETECTED_TC·· 619

STP_DISABLE· 619

STP_DISCARDING·· 619

STP_DISPUTE· 620

STP_ENABLE· 620

STP_FORWARDING·· 620

STP_LOOP_PROTECTION·· 621

STP_LOOPBACK_PROTECTION·· 621

STP_NOT_ROOT· 621

STP_NOTIFIED_TC·· 622

STP_PORT_TYPE_INCONSISTENCY· 622

STP_PVID_INCONSISTENCY· 622

STP_PVST_BPDU_PROTECTION·· 623

STP_ROOT_PROTECTION·· 623

SYSLOG messages· 625

SYSLOG_RTM_EVENT_BUFFER_FULL· 625

SYSLOG_NO_SPACE· 625

SYSLOG_LOGFILE_FULL· 625

SYSLOG_RESTART· 626

TACACS messages· 627

TACACS_AUTH_FAILURE· 627

TACACS_AUTH_SUCCESS· 627

TACACS_DELETE_HOST_FAIL· 627

TELNETD messages· 628

TELNETD_ACL_DENY· 628

TELNETD_REACH_SESSION_LIMIT· 628

TRILL messages· 629

TRILL_DUP_SYSTEMID·· 629

TRILL_INTF_CAPABILITY· 629

TRILL_LICENSE_EXPIRED·· 630

TRILL_LICENSE_EXPIRED_TIME· 630

TRILL_LICENSE_UNAVAILABLE· 630

TRILL_MEM_ALERT· 631

TRILL_NBR_CHG·· 631

VCF messages· 632

VCF_AGGR_CREAT· 632

VCF_AGGR_DELETE· 632

VCF_AGGR_FAILED·· 633

VCF_AUTO_ANALYZE_USERDEF· 633

VCF_AUTO_NO_USERDEF· 633

VCF_AUTO_START· 634

VCF_AUTO_STATIC_CMD·· 634

VCF_BGP· 634

VCF_DOWN_LINK· 635

VCF_GET_IMAGE· 635

VCF_GET_TEMPLATE· 636

VCF_INSTALL_IMAGE· 636

VCF_IRF_FINISH·· 636

VCF_IRF_FOUND·· 637

VCF_IRF_REBOOT· 637

VCF_IRF_START· 638

VCF_LOOPBACK_START· 638

VCF_LOOPBACK_START_FAILED·· 639

VCF_LOOPBACK_ALLOC·· 639

VCF_LOOPBACK_NO_FREE_IP· 640

VCF_LOOPBACK_RECLAIM·· 640

VCF_REBOOT· 640

VCF_SKIP_INSTALL· 641

VCF_STATIC_CMD_ERROR·· 641

VCF_UP_LINK· 641

VLAN messages· 642

VLAN_FAILED·· 642

VLAN_VLANMAPPING_FAILED·· 642

VLAN_VLANTRANSPARENT_FAILED·· 642

VRRP messages· 643

VRRP_STATUS_CHANGE· 643

VRRP_VF_STATUS_CHANGE· 644

VRRP_VMAC_INEFFECTIVE· 644

VSRP messages· 645

VSRP_BIND_FAILED·· 645

WIPS messages· 646

WIPS_APFLOOD·· 646

WIPS_AP_CHANNEL_CHANGE· 646

WIPS_ASSOCIATEOVERFLOW·· 646

WIPS_DOS· 647

WIPS_FLOOD·· 647

WIPS_HONEYPOT· 648

WIPS_HTGREENMODE· 648

WIPS_MALF· 649

WIPS_MAN_IN_MIDDLE· 649

WIPS_SPOOF· 650

WIPS_WEAKIV· 650

WIPS_WIRELESSBRIDGE· 650

 


Introduction

This document includes the following system messages:

·     Messages specific to Release 2609 of the switch.

·     Messages for the Comware 7 software platform version based on which Release 2609 was produced. Some platform system messages might not be available on the switch.

This document is intended only for managing S6800 switches. Do not use this document for any other device models.

This document assumes that the readers are familiar with data communications technologies and H3C networking products.

System log message format

By default, the system log messages use one of the following formats depending on the output destination:

·     Log host:

<PRI>TIMESTAMP Sysname %%vendorMODULE/severity/MNEMONIC: location; CONTENT

·     Destinations except for the log host:

Prefix TIMESTAMP Sysname MODULE/severity/MNEMONIC: CONTENT

Table 1 System log message elements

Element

Description

<PRI>

Priority identifier. It is calculated by using the following formula:

Priority identifier=facilityx8+severity

Where:

·     Facility is specified by using the info-center loghost command. A log host uses this parameter to identify log sources and filter log messages.

·     Severity represents the importance of the message. For more information about severity levels, see Table 2.

Prefix

Message type identifier. This element is contained in the system log messages sent to non-log host destinations.

The element uses the following symbols to indicate message severity:

·     Percentage sign (%)—Informational and higher levels.

·     Asterisk (*)—Debug level.

TIMESTAMP

Date and time when the event occurred.

The following are commands for configuring the timestamp format:

·     Log host—Use the info-center timestamp loghost command.

·     Non-log host destinationsUse the info-center timestamp command.

Sysname

Name or IP address of the device that generated the message.

%%vendor

Manufacturer flag. This element is %%10 for H3C.

This element is only available in messages sent to the log host.

MODULE

Name of the module that produced the message.

severity

Severity level of the message. (For more information about severity levels, see Table 2.)

MNEMONIC

Text string that uniquely identifies the system message. The maximum length is 32 characters.

location

Optional. This element presents location information for the message in the following format:

-attribute1=x-attribute2=y…-attributeN=z

This element is separated from the message description by using a semicolon (;).

CONTENT

Text string that contains detailed information about the event or error.

For variable fields in this element, this document uses the representations in Table 3.

 

System log messages are classified into eight severity levels from 0 to 7. The lower the number, the higher the severity, as shown in Table 2.

Table 2 System log message severity levels

Level

Severity

Description

0

Emergency

The system is unusable. For example, the system authorization has expired.

1

Alert

Action must be taken immediately. For example, traffic on an interface exceeds the upper limit.

2

Critical

Critical condition. For example, the device temperature exceeds the upper limit, the power module fails, or the fan tray fails.

3

Error

Error condition. For example, the link state changes or a storage card is unplugged.

4

Warning

Warning condition. For example, an interface is disconnected, or the memory resources are used up.

5

Notification

Normal but significant condition. For example, a terminal logs in to the device, or the device reboots.

6

Informational

Informational message. For example, a command or a ping operation is executed.

7

Debug

Debugging message.

 

For variable fields in the message text, this document uses the representations in Table 3. The values are case insensitive, even though the representations are uppercase letters.

Table 3 Variable field representations

Representation

Information type

INT16

Signed 16-bit decimal number.

UINT16

Unsigned 16-bit decimal number.

INT32

Signed 32-bit decimal number.

UINT32

Unsigned 32-bit decimal number.

INT64

Signed 64-bit decimal number.

UINT64

Unsigned 64-bit decimal number.

DOUBLE

Two dot-separated signed 32-bit decimal numbers. The format is [INTEGER].[INTEGER].

HEX

Hexadecimal number.

CHAR

Single character.

STRING

Character string.

IPADDR

IP address.

MAC

MAC address.

DATE

Date.

TIME

Time.

 

Managing and obtaining system log messages

You can manage system log messages by using the information center.

By default, the information center is enabled. Log messages can be output to the console, log buffer, monitor terminal, log host, and log file.

To filter log messages, use the info-center source command to specify log output rules. A log output rule specifies the source modules and the lowest severity level of log messages that can be output to a destination. A log message is output if its severity level is higher than or equal to the specified level. For example, if you specify a severity level of 6 (informational), log messages that have a severity level from 0 to 6 are output.

For more information about using the information center, see the network management and monitoring configuration guide for the product.

Obtaining log messages from the console terminal

Access the device through the console port. Real-time log messages are displayed on the console terminal.

Obtaining log messages from the log buffer

Use the display logbuffer command to display history log messages in the log buffer.

Obtaining log messages from a monitor terminal

Monitor terminals refer to terminals that access the device through the AUX, VTY, or TTY lines (for example, Telnet). To obtain log messages from a monitor terminal, use the following guidelines:

·     To display log messages on the monitor terminal, you must configure the terminal monitor command.

·     For monitor terminals, the lowest level of log messages that can be displayed is determined by both the terminal logging level and info-center source commands.

Obtaining log messages from the log file

By default, the log file feature automatically saves logs from the log file buffer to the log file every 24 hours. You can use the info-center logfile frequency command to change the automatic saving internal.

To manually save logs to the log file, use the logfile save command. The log file buffer is cleared each time a save operation is performed.

By default, you can obtain the log file from the flash:/logfile/ path .

Obtaining log messages from a log host

Use the info-center loghost command to specify the service port number and IP address of a log host. To specify multiple log hosts, repeat the command.

For a successful log message transmission, make sure the specified port number is the same as the port number used on the log host. The default service port number is 514.

Software module list

Table 4 lists all software modules that might produce system log messages. This document uses "OPENSRC" to represent all open source modules.

Table 4 Software module list

Module name representation

Module name expansion

AAA

Authentication, Authorization and Accounting

ACL

Access Control List

ANCP

Access Node Control Protocol

APMGR

Access Point Management

ARP

Address Resolution Protocol

ATK

Attack Detection and Prevention

ATM

Asynchronous Transfer Mode

BFD

Bidirectional Forwarding Detection

BGP

Border Gateway Protocol

BLS

Blacklist

CFD

Connectivity Fault Detection

CFGMAN

Configuration Management

CONNLMT

Connection Limit

DEV

Device Management

DHCP

Dynamic Host Configuration Protocol

DHCPR

IPv4 DHCP Relay

DHCPS

DHCP Server

DHCPS6

DHCPv6 Server

DHCPSP4

DHCP Snooping

DHCPSP6

DHCPv6 Snooping

DIAG

Diagnosis

DLDP

Device Link Detection Protocol

DOT1X

802.1X

DRNI

Distributed Resilient Network Interconnect

EDEV

Extended-Device Management

ERPS

Ethernet Ring Protection Switching

ETHOAM

Ethernet Operation, Administration and Maintenance

EVB

Edge Virtual Bridging

EVIISIS

Ethernet Virtual Interconnect Intermediate System-to-Intermediate System

FCOE

Fibre Channel Over Ethernet

FCLINK

Fibre Channel Link

FCZONE

Fibre Channel Zone

FIB

Forwarding Information Base

FILTER

Filter

FIPS

FIP Snooping

FS

File System

FTPD

File Transfer Protocol Daemon

HA

High Availability

HQOS

Hierarchical QoS

HTTPD

Hypertext Transfer Protocol Daemon

IFNET

Interface Net Management

IKE

Internet Key Exchange

IPSEC

IP Security

IPSG

IP Source Guard

IRDP

ICMP Router Discovery Protocol

IRF (cluster)

Intelligent Resilient Framework

ISIS

Intermediate System-to-Intermediate System

ISSU

In-Service Software Upgrade

L2TP

Layer 2 Tunneling Protocol

L2VPN

Layer 2 VPN

LAGG

Link Aggregation

LDP

Label Distribution Protocol

LLDP

Link Layer Discovery Protocol

LOAD

Load Management

LOGIN

Login

LPDT

Loopback Detection

LS

Local Server

LSPV

LSP Verification

MAC

Media Access Control

MACA

MAC Authentication

MACSEC

MAC Security

MBFD

MPLS BFD

MBUF

Memory buffer

MDC

Multitenant Device Context

MFIB

Multicast Forwarding Information Base

MGROUP

Mirroring group

MPLS

Multiprotocol Label Switching

MTLK

Monitor Link

NAT

Network Address Translation

NETCONF

Network Configuration Protocol

ND

Neighbor Discovery

NQA

Network Quality Analyzer

NTP

Network Time Protocol

OPENSRC

Open Source

OBJP

Object Policy

OFP

OpenFlow Protocol

OPTMOD

Optical Module

OSPF

Open Shortest Path First

OSPFV3

Open Shortest Path First Version 3

Packet Capture

Packet Capture

PBB

Provider Backbone Bridge

PBR

Policy-Based Routing

PCE

Path Computation Element

PEX

Port Extender

PIM

Protocol Independent Multicast

PING

Packet Internet Groper

PKI

Public Key Infrastructure

PKT2CPU

Packet to CPU

PORTSEC

Port Security

PPP

Point to Point Protocol

PORTAL

Portal

PWDCTL

Password Control

QOS

Quality of Service

RADIUS

Remote Authentication Dial In User Service

RDDC

Redundancy

RESMON

Resource Monitor

RIP

Routing Information Protocol

RIPNG

Routing Information Protocol Next Generation

RM

Routing Management

RRPP

Rapid Ring Protection Protocol

RTM

Real-Time Event Manager

SCM

Service Control Manager

SCRLSP

Static CRLSP

SESSION

Session

SFLOW

Sampler Flow

SHELL

Shell

SLSP

Static LSP

SMLK

Smart Link

SNMP

Simple Network Management Protocol

SSHS

Secure Shell Server

STAMGR

Station Management

STM

Stack Topology Management

STP

Spanning Tree Protocol

SYSEVENT

System Event

SYSLOG

System Log

TACACS

Terminal Access Controller Access Control System

TELNETD

Telnet Daemon

TRILL

Transparent Interconnect of Lots of Links

VCF

Vertical Converged Framework

VLAN

Virtual Local Area Network

VRRP

Virtual Router Redundancy Protocol

VSRP

Virtual Service Redundancy Protocol

WIPS

Wireless Intrusion Prevention System

 

Using this document

This document categorizes system log messages by software module. The modules are ordered alphabetically. Except for OPENSRC, the system log messages for each module are listed in alphabetic order of their mnemonic names. The OPENSRC messages are unordered because they use the same mnemonic name (SYSLOG). For each OPENSRC message, the section title uses a short description instead of the mnemonic name.

This document explains messages in tables. Table 5 describes information provided in these tables.

Table 5 Message explanation table contents

Item

Content

Example

Message text

Presents the message description.

ACL [UINT32] [STRING] [UINT64] packet(s).

Variable fields

Briefly describes the variable fields in the order that they appear in the message text.

The variable fields are numbered in the "$Number" form to help you identify their location in the message text.

$1: ACL number.

$2: ID and content of an ACL rule.

$3: Number of packets that matched the rule.

Severity level

Provides the severity level of the message.

6

Example

Provides a real message example. The examples do not include the "<PRI>TIMESTAMP Sysname %%vendor" part or the "Prefix TIMESTAMP Sysname" part, because information in this part varies with system settings.

ACL/6/ACL_STATIS_INFO: ACL 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s).

Explanation

Explains the message, including the event or error cause.

Number of packets that matched an ACL rule. This message is sent when the packet counter changes.

Recommended action

Provides recommended actions. For informational messages, no action is required.

No action is required.

 


AAA messages

This section contains AAA messages.

AAA_FAILURE

Message text

-AAAType=[STRING]-AAADomain=[STRING]-Service=[STRING]-UserName=[STRING]; AAA failed.

Variable fields

$1: AAA type.

$2: AAA scheme.

$3: Service.

$4: User name.

Severity level

5

Example

AAA/5/AAA_FAILURE: -AAAType=AUTHOR-AAADomain=domain1-Service=login-UserName=cwf@system; AAA failed.

Explanation

An AAA request was rejected.

The following are the common reasons:

·     No response was received from the server.

·     The user name or password was incorrect.

·     The service type that the user applied for was incorrect.

Recommended action

1.     Verify that the device is correctly connected to the server.

2.     Enter the correct user name and password.

3.     Verify that the server settings are the same as the settings on the device.

4.     If the problem persists, contact H3C Support.

 

AAA_LAUNCH

Message text

-AAAType=[STRING]-AAADomain=[STRING]-Service=[STRING]-UserName=[STRING]; AAA launched.

Variable fields

$1: AAA type.

$2: AAA scheme.

$3: Service.

$4: User name.

Severity level

6

Example

AAA/6/AAA_LAUNCH: -AAAType=AUTHEN-AAADomain=domain1-Service=login-UserName=cwf@system; AAA launched.

Explanation

An AAA request was received.

Recommended action

No action is required.

 

AAA_SUCCESS

Message text

-AAAType=[STRING]-AAADomain=[STRING]-Service=[STRING]-UserName=[STRING]; AAA succeeded.

Variable fields

$1: AAA type.

$2: AAA scheme.

$3: Service.

$4: User name.

Severity level

6

Example

AAA/6/AAA_SUCCESS: -AAAType=AUTHOR-AAADomain=domain1-Service=login-UserName=cwf@system; AAA succeeded.

Explanation

An AAA request was accepted.

Recommended action

No action is required.

 

 


ACL messages

This section contains ACL messages.

ACL_ACCELERATE_NO_RES

Message text

Failed to accelerate [STRING] ACL [UINT32]. The resources are insufficient.

Variable fields

$1: ACL type.

$2: ACL number.

Severity level

4

Example

ACL/4/ACL_ACCELERATE_NO_RES: Failed to accelerate IPv6 ACL 2001. The resources are insufficient.

Explanation

Hardware resources were insufficient for accelerating an ACL.

Recommended action

Delete some rules or disabled ACL acceleration for other ACLs to release hardware resources.

 

ACL_ACCELERATE_NONCONTIGUOUSMASK

Message text

Failed to accelerate ACL [UINT32]. ACL acceleration supports only contiguous wildcard masks.

Variable fields

$1: ACL number.

Severity level

4

Example

ACL/4/ACL_ACCELERATE_NONCONTIGUOUSMASK: Failed to accelerate ACL 2001. ACL acceleration supports only contiguous wildcard masks.

Explanation

ACL acceleration failed because rules containing noncontiguous wildcard masks exist in the ACL.

Recommended action

Check the ACL rules and delete the unsupported configuration.

 

ACL_ACCELERATE_NOT_SUPPORT

Message text

Failed to accelerate [STRING] ACL [UINT32]. The operation is not supported.

Variable fields

$1: ACL type.

$2: ACL number.

Severity level

4

Example

ACL/4/ACL_ACCELERATE_NOT_SUPPORT: Failed to accelerate IPv6 ACL 2001. The operation is not supported.

Explanation

ACL acceleration failed because the system does not support ACL acceleration.

Recommended action

No action is required.

 

ACL_ACCELERATE_NOT_SUPPORTHOPBYHOP

Message text

Failed to accelerate IPv6 ACL [UINT32]. ACL acceleration does not support the rules that contain the hop-by-hop keywords.

Variable fields

$1: ACL number.

Severity level

4

Example

ACL/4/ACL_ACCELERATE_NOT_SUPPORTHOPBYHOP: Failed to accelerate IPv6 ACL 2001. ACL acceleration does not support the rules that contain the hop-by-hop keywords.

Explanation

ACL acceleration failed for the IPv6 ACL because rules containing the hop-by-hop keyword exist in the ACL.

Recommended action

Check the ACL rules and delete the unsupported configuration.

 

ACL_ACCELERATE_NOT_SUPPORTMULTITCPFLAG

Message text

Failed to accelerate IPv6 ACL [UINT32]. ACL acceleration does not support specifying multiple TCP flags in one rule.

Variable fields

$1: ACL number.

Severity level

4

Example

ACL/4/ACL_ACCELERATE_NOT_SUPPORTMULTITCPFLAG: Failed to accelerate IPv6 ACL 2001. ACL acceleration does not support specifying multiple TCP flags in one rule.

Explanation

ACL acceleration failed for the IPv6 ACL because rules containing multiple TCP flags exist in the ACL.

Recommended action

Check the ACL rules and delete the unsupported configuration.

 

ACL_ACCELERATE_UNK_ERR

Message text

Failed to accelerate [STRING] ACL [UINT32].

Variable fields

$1: ACL type.

$2: ACL number.

Severity level

4

Example

ACL/4/ACL_ACCELERATE_UNK_ERR: Failed to accelerate IPv6 ACL 2001.

Explanation

ACL acceleration failed because of an unknown error.

Recommended action

No action is required.

 

ACL_IPV6_STATIS_INFO

Message text

IPv6 ACL [UINT32] [STRING] [UINT64] packet(s).

Variable fields

$1: ACL number.

$2: ID and content of an IPv6 ACL rule.

$3: Number of packets that matched the rule.

Severity level

6

Example

ACL6/6/ACL_IPV6_STATIS_INFO: IPv6 ACL 2000 rule 0 permit source 1:1::/64 logging 1000 packet(s).

Explanation

The number of packets matching the IPv6 ACL rule changed.

Recommended action

No action is required.

 

ACL_NO_MEM

Message text

Failed to configure [STRING] ACL [UINT] due to lack of memory.

Variable fields

$1: ACL type.

$2: ACL number.

Severity level

3

Example

ACL/3/ACL_NO_MEM: Failed to configure ACL 2001 due to lack of memory.

Explanation

Configuring the ACL failed because memory is insufficient.

Recommended action

Use the display memory-threshold command to check the memory usage.

 

ACL_STATIS_INFO

Message text

ACL [UINT32] [STRING] [UINT64] packet(s).

Variable fields

$1: ACL number.

$2: ID and content of an IPv4 ACL rule.

$3: Number of packets that matched the rule.

Severity level

6

Example

ACL/6/ACL_STATIS_INFO: ACL 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s).

Explanation

The number of packets matching the IPv4 ACL rule changed.

Recommended action

No action is required.

 

PFILTER_GLB_IPV4_DACT_NO_RES

Message text

Failed to apply or refresh the IPv4 default action to the [STRING] direction globally. The resources are insufficient.

Variable fields

$1: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_IPV4_DACT_NO_RES: Failed to apply or refresh the IPv4 default action to the inbound direction globally. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the IPv4 default action to a specific direction globally.

·     Updating the IPv4 default action applied to a specific direction globally.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_GLB_IPV4_DACT_UNK_ERR

Message text

Failed to apply or refresh the IPv4 default action to the [STRING] direction globally.

Variable fields

$1: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_IPV4_DACT_UNK_ERR: Failed to apply or refresh the IPv4 default action to the inbound direction globally.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying the IPv4 default action to a specific direction globally.

·     Updating the IPv4 default action applied to a specific direction globally.

Recommended action

No action is required.

 

PFILTER_GLB_IPV6_DACT_NO_RES

Message text

Failed to apply or refresh the IPv6 default action to the [STRING] direction globally. The resources are insufficient.

Variable fields

$1: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_IPV6_DACT_NO_RES: Failed to apply or refresh the IPv6 default action to the inbound direction globally. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the IPv6 default action to a specific direction globally.

·     Updating the IPv6 default action applied to a specific direction globally.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_GLB_IPV6_DACT_UNK_ERR

Message text

Failed to apply or refresh the IPv6 default action to the [STRING] direction globally.

Variable fields

$1: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_IPV6_DACT_UNK_ERR: Failed to apply or refresh the IPv6 default action to the inbound direction globally.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying the IPv6 default action to a specific direction globally.

·     Updating the IPv6 default action applied to a specific direction globally.

Recommended action

No action is required.

 

PFILTER_GLB_MAC_DACT_NO_RES

Message text

Failed to apply or refresh the MAC default action to the [STRING] direction globally. The resources are insufficient.

Variable fields

$1: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_MAC_DACT_NO_RES: Failed to apply or refresh the MAC default action to the inbound direction globally. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the MAC default action to a specific direction globally.

·     Updating the MAC default action applied to a specific direction globally.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_GLB_MAC_DACT_UNK_ERR

Message text

Failed to apply or refresh the MAC default action to the [STRING] direction globally.

Variable fields

$1: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_MAC_DACT_UNK_ERR: Failed to apply or refresh the MAC default action to the inbound direction globally.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying the MAC default action to a specific direction globally.

·     Updating the MAC default action applied to a specific direction globally.

Recommended action

No action is required.

 

PFILTER_GLB_NO_RES

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction globally. The resources are insufficient.

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_NO_RES: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction globally. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying an ACL rule to a specific direction globally.

·     Updating an ACL rule applied to a specific direction globally.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_GLB_NOT_SUPPORT

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction globally. The ACL is not supported.

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_NOT_SUPPORT: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction globally. The ACL is not supported.

Explanation

The system failed to perform one of the following actions because the ACL rule is not supported:

·     Applying an ACL rule to a specific direction globally.

·     Updating an ACL rule applied to a specific direction globally.

Recommended action

Verify the ACL configuration and remove the settings that are not supported.

 

PFILTER_GLB_ RES_CONFLICT

Message text

Failed to apply or refresh [STRING] ACL [UINT] to the [STRING] direction globally. [STRING] ACL [UINT] has already been applied globally.

Variable fields

$1: ACL type.

$2: ACL number.

$3: Traffic direction.

$4: ACL type.

$5: ACL number.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_RES_CONFLICT: Failed to apply or refresh IPv6 ACL 2000 to the inbound direction globally. IPv6 ACL 3000 has already been applied globally.

Explanation

The system failed to perform one of the following actions because an ACL of the same type (IPv4 ACL, IPv6 ACL, or MAC ACL) has already been applied:

·     Applying the ACL to a specific direction globally.

·     Updating the ACL applied to a specific direction globally.

Recommended action

Remove the ACL of the same type.

 

PFILTER_GLB_UNK_ERR

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction globally.

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

Severity level

3

Example

PFILTER/3/PFILTER_GLB_UNK_ERR: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction globally.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying an ACL rule to a specific direction globally.

·     Updating an ACL rule applied to a specific direction globally.

Recommended action

No action is required.

 

PFILTER_IF_IPV4_DACT_NO_RES

Message text

Failed to apply or refresh the IPv4 default action to the [STRING] direction of interface [STRING]. The resources are insufficient.

Variable fields

$1: Traffic direction.

$2: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_IPV4_DACT_NO_RES: Failed to apply or refresh the IPv4 default action to the inbound direction of interface Ethernet 3/1/2. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the IPv4 default action to a specific direction of an interface.

·     Updating the IPv4 default action applied to a specific direction of an interface.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_IF_IPV4_DACT_UNK_ERR

Message text

Failed to apply or refresh the IPv4 default action to the [STRING] direction of interface [STRING].

Variable fields

$1: Traffic direction.

$2: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_IPV4_DACT_UNK_ERR: Failed to apply or refresh the IPv4 default action to the inbound direction of interface Ethernet 3/1/2.

Explanation

The system failed to perform one of the following actions because an unknown error:

·     Applying the IPv4 default action to a specific direction of an interface.

·     Updating the IPv4 default action applied to a specific direction of an interface.

Recommended action

No action is required.

 

PFILTER_IF_IPV6_DACT_NO_RES

Message text

Failed to apply or refresh the IPv6 default action to the [STRING] direction of interface [STRING]. The resources are insufficient.

Variable fields

$1: Traffic direction.

$2: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_IPV6_DACT_NO_RES: Failed to apply or refresh the IPv6 default action to the inbound direction of interface Ethernet 3/1/2. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the IPv6 default action to a specific direction of an interface.

·     Updating the IPv6 default action applied to a specific direction of an interface.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_IF_IPV6_DACT_UNK_ERR

Message text

Failed to apply or refresh the IPv6 default action to the [STRING] direction of interface [STRING].

Variable fields

$1: Traffic direction.

$2: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_IPV6_DACT_UNK_ERR: Failed to apply or refresh the IPv6 default action to the inbound direction of interface Ethernet 3/1/2.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying the IPv6 default action to a specific direction of an interface.

·     Updating the IPv6 default action applied to a specific direction of an interface.

Recommended action

No action is required.

 

PFILTER_IF_MAC_DACT_NO_RES

Message text

Failed to apply or refresh the MAC default action to the [STRING] direction of interface [STRING]. The resources are insufficient.

Variable fields

$1: Traffic direction.

$2: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_MAC_DACT_NO_RES: Failed to apply or refresh the MAC default action to the inbound direction of interface Ethernet 3/1/2. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the MAC default action to a specific direction of an interface.

·     Updating the MAC default action applied to a specific direction of an interface.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_IF_MAC_DACT_UNK_ERR

Message text

Failed to apply or refresh the MAC default action to the [STRING] direction of interface [STRING].

Variable fields

$1: Traffic direction.

$2: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_MAC_DACT_UNK_ERR: Failed to apply or refresh the MAC default action to the inbound direction of interface Ethernet 3/1/2.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying the MAC default action to a specific direction of an interface.

·     Updating the MAC default action applied to a specific direction of an interface.

Recommended action

No action is required.

 

PFILTER_IF_NO_RES

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of interface [STRING]. The resources are insufficient.

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

$5: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_NO_RES: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction of interface Ethernet 3/1/2. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying an ACL rule to a specific direction of an interface.

·     Updating an ACL rule applied to a specific direction of an interface.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_IF_NOT_SUPPORT

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of interface [STRING]. The ACL is not supported.

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

$5: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_NOT_SUPPORT: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction of interface Ethernet 3/1/2. The ACL is not supported.

Explanation

The system failed to perform one of the following actions because the ACL rule is not supported:

·     Applying an ACL rule to a specific direction of an interface.

·     Updating an ACL rule applied to a specific direction of an interface.

Recommended action

Verify the ACL configuration and remove the settings that are not supported.

 

PFILTER_IF_RES_CONFLICT

Message text

Failed to apply or refresh [STRING] ACL [UINT] to the [STRING] direction of interface [STRING]. [STRING] ACL [UINT] has already been applied to the interface.

Variable fields

$1: ACL type.

$2: ACL number.

$3: Traffic direction.

$4: Interface name.

$5: ACL type.

$6: ACL number.

Severity level

3

Example

PFILTER/3/PFILTER_IF_RES_CONFLICT: Failed to apply or refresh IPv6 ACL 2000 to the inbound direction of interface Ethernet 3/1/2. IPv6 ACL 3000 has already been applied to the interface.

Explanation

The system failed to perform one of the following actions because an ACL of the same type (IPv4 ACL, IPv6 ACL, or MAC ACL) has already been applied:

·     Applying the ACL to a specific direction of an interface.

·     Updating the ACL applied to a specific direction of an interface.

Recommended action

Remove the ACL of the same type.

 

PFILTER_IF_UNK_ERR

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of interface [STRING].

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

$5: Interface name.

Severity level

3

Example

PFILTER/3/PFILTER_IF_UNK_ERR: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction of interface Ethernet 3/1/2.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying an ACL rule to a specific direction of an interface.

·     Updating an ACL rule applied to a specific direction of an interface.

Recommended action

No action is required.

 

PFILTER_IPV6_STATIS_INFO

Message text

[STRING] ([STRING]): Packet-filter IPv6 [UINT32] [STRING] [STRING] [UINT64] packet(s).

Variable fields

$1: Destination to which packet filter applies.

$2: Traffic direction.

$3: ACL number.

$4: ID and content of an ACL rule.

$5: Number of packets that matched the rule.

Severity level

6

Example

ACL/6/PFILTER_IPV6_STATIS_INFO: Ethernet0/4/0 (inbound): Packet-filter IPv6 2000 rule 0 permit source 1:1::/64 logging 1000 packet(s).

Explanation

The number of packets matching the packet-filter IPv6 ACL rule changed.

Recommended action

No action is required.

 

PFILTER_STATIS_INFO

Message text

[STRING] ([STRING]): Packet-filter [UINT32] [STRING] [UINT64] packet(s).

Variable fields

$1: Destination to which packet filter applies.

$2: Traffic direction.

$3: ACL number.

$4: ID and content of an ACL rule.

$5: Number of packets that matched the rule.

Severity level

6

Example

ACL/6/PFILTER_STATIS_INFO: Ethernet0/4/0 (inbound): Packet-filter 2000 rule 0 permit source 1.1.1.1 0 logging 10000 packet(s).

Explanation

The number of packets matching the packet-filter IPv4 ACL rule changed.

Recommended action

No action is required.

 

PFILTER_VLAN_IPV4_DACT_NO_RES

Message text

Failed to apply or refresh the IPv4 default action to the [STRING] direction of VLAN [UINT16]. The resources are insufficient.

Variable fields

$1: Traffic direction.

$2: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_IPV4_DACT_NO_RES: Failed to apply or refresh the IPv4 default action to the inbound direction of VLAN 1. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the IPv4 default action to a specific direction of a VLAN.

·     Updating the IPv4 default action applied to a specific direction of a VLAN.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_VLAN_IPV4_DACT_UNK_ERR

Message text

Failed to apply or refresh the IPv4 default action to the [STRING] direction of VLAN [UINT16].

Variable fields

$1: Traffic direction.

$2: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_IPV4_DACT_UNK_ERR: Failed to apply or refresh the IPv4 default action to the inbound direction of VLAN 1.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying the IPv4 default action to a specific direction of a VLAN.

·     Updating the IPv4 default action applied to a specific direction of a VLAN.

Recommended action

No action is required.

 

PFILTER_VLAN_IPV6_DACT_NO_RES

Message text

Failed to apply or refresh the IPv6 default action to the [STRING] direction of VLAN [UINT16]. The resources are insufficient.

Variable fields

$1: Traffic direction.

$2: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_IPV6_DACT_NO_RES: Failed to apply or refresh the IPv6 default action to the inbound direction of VLAN 1. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the IPv6 default action to a specific direction of a VLAN.

·     Updating the IPv6 default action applied to a specific direction of a VLAN.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_VLAN_IPV6_DACT_UNK_ERR

Message text

Failed to apply or refresh the IPv6 default action to the [STRING] direction of VLAN [UINT16].

Variable fields

$1: Traffic direction.

$2: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_IPV6_DACT_UNK_ERR: Failed to apply or refresh the IPv6 default action to the inbound direction of VLAN 1.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying the IPv6 default action to a specific direction of a VLAN.

·     Updating the IPv6 default action applied to a specific direction of a VLAN.

Recommended action

No action is required.

 

PFILTER_VLAN_MAC_DACT_NO_RES

Message text

Failed to apply or refresh the MAC default action to the [STRING] direction of VLAN [UINT16]. The resources are insufficient.

Variable fields

$1: Traffic direction.

$2: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_MAC_DACT_NO_RES: Failed to apply or refresh the MAC default action to the inbound direction of VLAN 1. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying the MAC default action to a specific direction of a VLAN.

·     Updating the MAC default action applied to a specific direction of a VLAN.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_VLAN_MAC_DACT_UNK_ERR

Message text

Failed to apply or refresh the MAC default action to the [STRING] direction of VLAN [UINT16].

Variable fields

$1: Traffic direction.

$2: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_MAC_DACT_UNK_ERR: Failed to apply or refresh the MAC default action to the inbound direction of VLAN 1.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying the MAC default action to a specific direction of a VLAN.

·     Updating the MAC default action applied to a specific direction of a VLAN.

Recommended action

No action is required.

 

PFILTER_VLAN_NO_RES

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of VLAN [UINT16]. The resources are insufficient.

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

$5: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_NO_RES: Failed to apply or refresh IPv6 ACL 2000 rule 1 to the inbound direction of VLAN 1. The resources are insufficient.

Explanation

The system failed to perform one of the following actions because hardware resources are insufficient:

·     Applying an ACL rule to a specific direction of a VLAN.

·     Updating an ACL rule applied to a specific direction of a VLAN.

Recommended action

Use the display qos-acl resource command to check hardware resource usage.

 

PFILTER_VLAN_NOT_SUPPORT

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of VLAN [UINT16]. The ACL is not supported.

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

$5: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_NOT_SUPPORT: Failed to apply or refresh ACL 2000 rule 1 to the inbound direction of VLAN 1. The ACL is not supported.

Explanation

The system failed to perform one of the following actions because the ACL rule is not supported:

·     Applying an ACL rule to a specific direction of a VLAN.

·     Updating an ACL rule applied to a specific direction of a VLAN.

Recommended action

Verify the ACL configuration and remove the settings that are not supported.

 

PFILTER_VLAN_RES_CONFLICT

Message text

Failed to apply or refresh [STRING] ACL [UINT] to the [STRING] direction of VLAN [UINT16]. [STRING] ACL [UINT] has already been applied to the VLAN.

Variable fields

$1: ACL type.

$2: ACL number.

$3: Traffic direction.

$4: VLAN ID.

$5: ACL type.

$6: ACL number.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_RES_CONFLICT: Failed to apply or refresh IPv6 ACL 2000 to the inbound direction of VLAN 1. IPv6 ACL 3000 has already been applied to the VLAN.

Explanation

The system failed to perform one of the following actions because an ACL of the same type (IPv4 ACL, IPv6 ACL, or MAC ACL) has already been applied:

·     Applying the ACL to a specific direction of a VLAN.

·     Updating the ACL applied to a specific direction of a VLAN.

Recommended action

Remove the ACL of the same type.

 

PFILTER_VLAN_UNK_ERR

Message text

Failed to apply or refresh [STRING] ACL [UINT] [STRING] to the [STRING] direction of VLAN [UINT16].

Variable fields

$1: ACL type.

$2: ACL number.

$3: ACL rule ID.

$4: Traffic direction.

$5: VLAN ID.

Severity level

3

Example

PFILTER/3/PFILTER_VLAN_UNK_ERR: Failed to apply or refresh ACL 2000 rule 1 to the inbound direction of VLAN 1.

Explanation

The system failed to perform one of the following actions due to an unknown error:

·     Applying an ACL rule to a specific direction of a VLAN.

·     Updating an ACL rule applied to a specific direction of a VLAN.

Recommended action

No action is required.

 

 


ANCP messages

This section contains ANCP messages.

ANCP_INVALID_PACKET

Message text

-NeighborName=[STRING]-State=[STRING]-MessageType=[STRING]; The [STRING] value [STRING] is wrong, and the value [STRING] is expected.

Variable fields

$1: ANCP neighbor name.

$2: Neighbor state.

$3: Message type.

$4: Field:

·     Sender Instance.

·     Sender Port.

·     Sender Name.

·     Partition ID.

·     Receiver Instance.

·     Receiver Port.

·     Receiver Name.

·     Version.

·     Timer.

·     Pflag.

·     Capabilities.

$5: Wrong value of the field.

$6: Expected value of the field.

Severity level

6

Example

ANCP/6/ANCP_INVALID_PACKET: -NeighborName=Dslam-State=SYNSENT-MessageType=SYNACK; The Sender Instance value 0 is wrong, and the value 1 is expected.

Explanation

The system received an adjacency message that had a field with a wrong value.

Recommended action

No action is required.

 

 


APMGR messages

This section contains access point management messages.

APMGR_AC_MEM_ALERT

Message text

The memory utilization has reached the threshold.

Variable fields

N/A

Severity level

4

Example

APMGR/4/APMGR_AC_MEM_ALERT: The memory utilization has reached the threshold.

Explanation

The AP failed to come online because the memory utilization exceeded the limit.

Recommended action

Stop creating manual APs and prevent APs from coming online.

 

APMGR_ADD_AP_FAIL

Message text

AP [STRING] failed to come online using serial ID [STRING]: MAC address [STRING] is being used by AP [STRING].

Variable fields

$1: AP name.

$2: Serial ID.

$3: MAC address.

$4: AP name.

Severity level

4

Example

APMGR/4/ APMGR_ADD_AP_FAIL: AP ap1 failed to come online using serial ID 01247ef96: MAC address 0023-7961-5201 is being used by AP ap2.

Explanation

The AP failed to come online because a manual AP that has the same MAC address already exists on the AC.

Recommended action

Delete either the manual AP that has the MAC address or the serial ID.

 

APMGR_ADDBAC_INFO

Message text

Add BAS AC [STRING].

Variable fields

$1: MAC address of the BAS AC.

Severity level

6

Example

APMGR/6/APMGR_ADDBAC_INFO: Add BAS AC 3ce5-a616-28cd.

Explanation

The BAS AC was connected to the master AC.

Recommended action

No action is required.

 

APMGR_AP_OFFLINE

Message text

AP [STRING] went offline. State changed to Idle.

Variable fields

$1: AP name.

Severity level

6

Example

APMGR/6/APMGR_AP_OFFLINE: AP ap1 went offline. State changed to Idle.

Explanation

The AP went offline. The state of the AP changed to Idle.

Recommended action

If the AP went offline abnormally, check the debugging information to locate the issue and resolve it.

 

APMGR_AP_ONLINE

Message text

AP [STRING] went online. State changed to Run.

Variable fields

$1: AP name.

Severity level

6

Example

APMGR/6/APMGR_AP_ONLINE: AP ap1 went online. State changed to Run.

Explanation

The AP came online. The state of the AP changed to Run.

Recommended action

No action is required.

 

APMGR_CWC_IMG_DOWNLOAD_COMPLETE

Message text

System software image file [STRING] downloading through the CAPWAP tunnel to AC [STRING] completed.

Variable fields

$1: Image file name.

$2: AC IP address.

Severity level

6

Example

APMGR/6/APMGR_CWC_IMG_DOWNLOAD_COMPLETE: System software image file 5800.ipe downloading through the CAPWAP tunnel to AC 192.168.10.1 completed.

Explanation

The AP downloaded the image file from the AC successfully.

Recommended action

No action is required.

 

APMGR_CWC_IMG_DOWNLOAD_START

Message text

Started to download the system software image file [STRING] through the CAPWAP tunnel to AC [STRING].

Variable fields

$1: Image file name.

$2: AC IP address.

Severity level

6

Example

APMGR/6/APMGR_CWC_IMG_DOWNLOAD_START: Started to download the system software image file 5800.ipe through the CAPWAP tunnel to AC 192.168.10.1.

Explanation

The AP started to download the image file from the AC.

Recommended action

Make sure the AP is correctly connected to the AC.

 

APMGR_CWC_IMG_NO_ENOUGH_SPACE

Message text

Insufficient flash memory space for downloading system software image file [STRING].

Variable fields

$1: Image file name.

Severity level

6

Example

APMGR/6/APMGR_CWC_IMG_NO_ENOUGH_SPACE: Insufficient flash memory space for downloading system software image file 5800.ipe.

Explanation

The AP failed to download the image file from the AC because of insufficient flash memory.

Recommended action

Delete files not in use from the AP.

 

APMGR_CWC_LOCAL_AC_DOWN

Message text

CAPWAP tunnel to Central AC [STRING] went down. Reason: [STRING].

Variable fields

$1: IP address of the central AC.

$2: Reason:

·     Added local AC IP address.

·     Deleted local AC IP address.

·     Local AC interface used for CAPWAP tunnel went down.

·     Local AC config changed.

·     N/A

Severity level

4

Example

APMGR/4/APMGR_CWC_LOCAL_AC_DOWN: CAPWAP tunnel to Central AC 2.2.2.1 went down. Reason: Added local AC IP address.

Explanation

The CAPWAP tunnel between the central AC and the local AC was terminated for a specific reason.

Recommended action

To resolve the issue:

1.     Examine the network connection between the central AC and the local AC.

2.     Verify that the central AC is correctly configured.

3.     Verify that the local AC is correctly configured.

4.     If the issue persists, contact H3C Support.

 

APMGR_CWC_LOCAL_AC_UP

Message text

CAPWAP tunnel to Central AC [STRING] went up.

Variable fields

$1: IP address of the central AC.

Severity level

6

Example

APMGR/6/APMGR_CWC_LOCAL_AC_UP: CAPWAP tunnel to Central AC 2.2.2.1 went up.

Explanation

The central AC has established a CAPWAP tunnel with the local AC.

Recommended action

No action is required.

 

APMGR_CWC_REBOOT

Message text

AP in state [STRING] is rebooting. Reason: [STRING]

Variable fields

$1: AP state.

$2: Reason:

·     AP was reset.

·     Image was downloaded successfully.

·     AP stayed in idle state for a long time.

Severity level

6

Example

APMGR/6/APMGR_CWC_REBOOT: AP in State Run is rebooting. Reason: AP was reset.

Explanation

The AP rebooted for a specific reason.

Recommended action

No action is required.

 

APMGR_CWC_RUN_DOWNLOAD_COMPLETE

Message text

File [STRING] successfully downloaded through the CAPWAP tunnel to AC [STRING].

Variable fields

$1: File name.

$2: AC IP address.

Severity level

6

Example

APMGR/6/APMGR_CWC_RUN_DOWNLOAD_COMPLETE: File ac.cfg successfully downloaded through the CAPWAP tunnel to AC 192.168.10.1.

Explanation

The AP downloaded the file from the AC successfully.

Recommended action

No action is required.

 

APMGR_CWC_RUN_DOWNLOAD_START

Message text

Started to download the file [STRING] through the CAPWAP tunnel to AC [STRING].

Variable fields

$1: File name.

$2: AC IP address.

Severity level

6

Example

APMGR/6/APMGR_CWC_RUN_DOWNLOAD_START: Started to download the file ac.cfg through the CAPWAP tunnel to AC 192.168.10.1.

Explanation

The AP started to download the file from the AC.

Recommended action

Make sure the AP is correctly connected to the AC.

 

APMGR_CWC_RUN_NO_ENOUGH_SPACE

Message text

Insufficient flash memory space for downloading file [STRING].

Variable fields

$1: File name.

Severity level

6

Example

APMGR/6/APMGR_CWC_RUN_NO_ENOUGH_SPACE: Insufficient flash memory space for downloading file ac.cfg.

Explanation

The AP failed to download the file from the AC because of insufficient flash memory.

Recommended action

Delete files not in use from the AP.

 

APMGR_CWC_TUNNEL_DOWN

Message text

CAPWAP tunnel to AC [STRING] went down. Reason: [STRING].

Variable fields

$1: AC IP address.

$2: Reason:

·     Added AP IP address.

·     Deleted AP IP address.

·     AP interface used for CAPWAP tunnel went down.

·     AP config changed.

·     AP was reset.

·     Number of echo retransmission attempts exceeded the limit.

·     Full retransmission queue.

·     Data channel timer expired.

·     Backup AC IP address changed.

·     Backup tunnel changed to master tunnel.

·     Failed to change backup tunnel to master tunnel.

·     Backup method changed.

·     N/A.

Severity level

6

Example

APMGR/6/APMGR_CWC_TUNNEL_DOWN: CAPWAP tunnel to AC 192.168.10.1 went down. Reason: AP was reset.

Explanation

The CAPWAP tunnel between the AP and the AC was terminated for a specific reason.

Recommended action

Examine the network connection between the AP and the AC.

 

APMGR_CWC_TUNNEL_UP

Message text

[STRING] CAPWAP tunnel to AC [STRING] went up.

Variable fields

$1: Tunnel type:

·     Master.

·     Backup.

$2: AC IP address.

Severity level

6

Example

APMGR/6/APMGR_CWC_TUNNEL_UP: Master CAPWAP tunnel to AC 192.168.10.1 went up.

Explanation

The AP was connected to the AC successfully and entered Run state.

Recommended action

No action is required.

 

APMGR_CWS_IMG_DOWNLOAD_COMPLETE

Message text

System software image file [STRING] downloading through the CAPWAP tunnel for AP [STRING] completed.

Variable fields

$1: Image file name.

$2: AP name.

Severity level

6

Example

APMGR/6/APMGR_ CWS_IMG_DOWNLOAD_COMPLETE: System software image file 5800.ipe downloading through the CAPWAP tunnel for AP ap2 completed.

Explanation

The AP downloaded the image file from the AC successfully.

Recommended action

No action is required.

 

APMGR_CWS_IMG_DOWNLOAD_START

Message text

AP [STRING] started to download the system software image file [STRING].

Variable fields

$1: AP name.

$2: Image file name.

Severity level

6

Example

APMGR/6/APMGR_CWS_IMG_DOWNLOAD_START: AP ap1 started to download the system software image file 5800.ipe.

Explanation

The AP started to download the image file from the AC.

Recommended action

No action is required.

 

APMGR_CWS_LOCAL_AC_DOWN

Message text

CAPWAP tunnel to local AC [STRING] went down. Reason: [STRING].

Variable fields

$1: IP address of the local AC.

$2: Reason:

·     Neighbor dead timer expired.

·     Local AC was deleted.

·     Serial number changed.

·     Processed join request in Run state.

·     Failed to retransmit message.

·     N/A

Severity level

4

Example

APMGR/4/APMGR_CWS_LOCAL_AC_DOWN: CAPWAP tunnel to local AC 1.1.1.1 went down. Reason: Serial number changed.

Explanation

The CAPWAP tunnel between the central AC and the local AC was terminated for a specific reason.

Recommended action

To resolve the issue:

1.     Examine the network connection between the central AC and the local AC.

2.     Verify that the central AC is correctly configured.

3.     Verify that the local AC is correctly configured.

4.     If the issue persists, contact H3C Support.

 

APMGR_CWS_LOCAL_AC_UP

Message text

CAPWAP tunnel to local AC [STRING] went up.

Variable fields

$1: IP address of the local AC.

Severity level

6

Example

APMGR/6/APMGR_CWS_LOCAL_AC_UP: CAPWAP tunnel to local AC 1.1.1.1 went up.

Explanation

The central AC has established a CAPWAP tunnel with the local AC.

Recommended action

No action is required.

 

APMGR_CWS_RUN_DOWNLOAD_COMPLETE

Message text

File [STRING] successfully downloaded through the CAPWAP tunnel for AP [STRING].

Variable fields

$1: File name.

$2: AP name.

Severity level

6

Example

APMGR/6/APMGR_CWS_RUN_DOWNLOAD_COMPLETE: File ac.cfg successfully downloaded through the CAPWAP tunnel for AP ap2.

Explanation

The AP downloaded the file from the AC successfully.

Recommended action

No action is required.

 

APMGR_CWS_RUN_DOWNLOAD_START

Message text

AP [STRING] started to download the file [STRING].

Variable fields

$1: AP name.

$2: File name.

Severity level

6

Example

APMGR/6/APMGR_CWS_RUN_DOWNLOAD_START: AP ap1 started to download the file ac.cfg.

Explanation

The AP started to download the file from the AC.

Recommended action

No action is required.

 

APMGR_CWS_TUNNEL_DOWN

Message text

CAPWAP tunnel to AP [STRING] went down. Reason: [STRING].

Variable fields

$1: AP name.

$2: Reason:

·     Neighbor dead timer expired.

·     AP was reset.

·     AP was deleted.

·     Serial number changed.

·     Processed join request in Run state.

·     Failed to retransmit message.

·     Received WTP tunnel down event from AP.

·     Backup AC closed the backup tunnel.

·     Tunnel switched.

·     N/A.

Severity level

6

Example

APMGR/6/APMGR_CWS_TUNNEL_DOWN: CAPWAP tunnel to AP ap1 went down. Reason: AP was reset.

Explanation

The AP went offline for a specific reason.

Recommended action

To resolve the issue:

1.     Examine the network connection between the AP and the AC.

2.     Verify that the AP is correctly configured.

3.     Verify that the AC is correctly configured.

4.     If the issue persists, contact H3C Support.

 

APMGR_CWS_TUNNEL_UP

Message text

[STRING] CAPWAP tunnel to AP [STRING] went up.

Variable fields

$1: Tunnel type:

·     Master.

·     Backup.

$2: AP name.

Severity level

6

Example

APMGR/6/APMGR_CWS_TUNNEL_UP: Backup CAPWAP tunnel to AP ap1 went up.

Explanation

The AP came online and entered Run state.

Recommended action

No action is required.

 

APMGR_DELBAC_INFO

Message text

Delete BAS AC [STRING].

Variable fields

$1: MAC address of the BAS AC.

Severity level

6

Example

APMGR/6/APMGR_DELBAC_INFO: Delete BAS AC 3ce5-a616-28cd.

Explanation

The BAS AC was disconnected from the master AC.

Recommended action

No action is required.

 

APMGR_LOCAL_AC_OFFLINE

Message text

Local AC [STRING] went offline. State changed to Idle.

Variable fields

$1: Name of the local AC.

Severity level

6

Example

APMGR/6/APMGR_LOCAL_AC_OFFLINE: Local AC ac1 went offline. State changed to Idle.

Explanation

The local AC went offline. The state of the local AC changed to Idle.

Recommended action

1.     If the local AC went offline abnormally, check the debugging information to locate the issue and resolve it.

2.     If the issue persists, contact H3C Support.

 

APMGR_LOCAL_AC_ONLINE

Message text

Local AC [STRING] went online. State changed to Run.

Variable fields

$1: Name of the local AC.

Severity level

6

Example

APMGR/6/APMGR_LOCAL_AC_ONLINE: Local AC ac1 went online. State changed to Run.

Explanation

The local AC came online. The state of the local AC changed to Run.

Recommended action

No action is required.

 

 

 


ARP messages

This section contains ARP messages.

ARP_ACTIVE_ACK_NO_REPLY

Message text

No ARP reply from IP [STRING] was received on interface [STRING].

Variable fields

$1: IP address.

$2: Interface name.

Severity level

6

Example

ARP/6/ARP_ACTIVE_ACK_NO_REPLY: No ARP reply from IP 192.168.10.1 was received on interface Ethernet0/1/0.

Explanation

The ARP active acknowledgement feature did not receive an ARP reply after it sent an ARP request to the sender IP of an ARP message.

This message indicates the risk of attacks.

Recommended action

1.     Verify that the learned ARP entries on the device are consistent with the existing legal devices. When gateways and servers are on the network, check the ARP entries for these devices first.

2.     If the ARP entries are correct and the attack continues, contact H3C Support.

 

ARP_ACTIVE_ACK_NOREQUESTED_REPLY

Message text

Interface [STRING] received from IP [STRING] an ARP reply that was not requested by the device.

Variable fields

$1: Interface name.

$2: IP address.

Severity level

6

Example

ARP/6/ARP_ACTIVE_ACK_NOREQUESTED_REPLY: Interface Ethernet0/1/0 received from IP 192.168.10.1 an ARP reply that was not requested by the device.

Explanation

The ARP active acknowledgement feature received an unsolicited ARP reply from a sender IP.

This message indicates the risk of attacks.

Recommended action

No action is required. The device discards the ARP reply automatically.

 

ARP_BINDRULETOHW_FAILED

Message text

Failed to download binding rule to hardware on the interface [STRING], SrcIP [IPADDR], SrcMAC [MAC], VLAN [UINT16], Gateway MAC [MAC].

Variable fields

$1: Interface name.

$2: Source IP address.

$3: Source MAC address.

$4: VLAN ID.

$5: Gateway MAC address.

Severity level

5

Example

ARP/5/ARP_BINDRULETOHW_FAILED: Failed to download binding rule to hardware on the interface Ethernet1/0/1, SrcIP 1.1.1.132, SrcMAC 0015-E944-A947, VLAN 1, Gateway MAC 00A1-B812-1108.

Explanation

The system failed to set a binding rule to the hardware on an interface. The message is sent in any of the following situations:

·     The resources are not sufficient for the operation.

·     The memory is not sufficient for the operation.

·     A hardware error occurs.

Recommended action

To resolve the problem:

1.     Execute the display qos-acl resource command to check if the ACL resources for the operation are sufficient.

¡     If yes, proceed to step 2.

¡     If no, delete unnecessary configuration to release ACL resources. If no configuration can be deleted, proceed to step 2.

2.     Execute the display memory command to check if the memory for the operation is sufficient.

¡     If yes, proceed to step 3.

¡     If no, delete unnecessary configuration to release memory. If no configuration can be deleted, proceed to step 3.

3.     Delete the configuration and perform the operation again.

 

ARP_DETECTION_LOG

Message text

Detected an ARP attack on interface [STRING]: IP [STRING], MAC [STRING], VLAN [STRING]. [UINT32] packet(s) dropped.

Variable fields

$1: Interface name.

$2: IP address.

$3: MAC address.

$4: VLAN ID.

$5: Number of dropped packets.

Severity level

5

Example

ARP/5/ARP_INSPECTION: -MDC=1; Detected an ARP attack on interface GigabitEthernet1/0/1: IP 1.1.1.1, MAC 1-1-1, VLAN 100. 2 packet(s) dropped.

Explanation

An ARP attack was detected on an interface and attack packets were dropped.

Recommended action

Check the source of the ARP attack.

 

ARP_DUPLICATE_IPADDR_DETECT

Message text

Detected an IP address conflict. The device with MAC address [STRING] connected to interface [STRING] in VSI [STRING] and the device with MAC address [STRING] connected to interface [STRING] in VSI [STRING] were using the same IP address [IPADDR].

Variable fields

$1: MAC address.

$2: Interface name. (The interface can be a tunnel interface, Layer 3 interface, or Ethernet service instance.)

$3: VSI name.

$4: MAC address.

$5: Interface name. (The interface can be a tunnel interface, Layer 3 interface, or Ethernet service instance.)

$6: VSI name.

$7: Conflicting IP address.

Severity level

6

Example

Detected an IP address conflict. The device with MAC address 00-00-01 connected to interface Ethernet0/0/1 service-instance 1000 in VSI vpna and the device with MAC address 00-00-02 connected to interface tunnel 10 in VSI vpna were using the same IP address 192.168.1.1.

Explanation

This message is sent when an interface receives an ARP message in which the sender information conflicts with an existing ARP entry. The sender IP address is the same as the IP address in the entry, but the MAC addresses are different.

Recommended action

Change the IP address on either of the two devices.

 

ARP_ENTRY_CONFLICT

Message text

The software entry for [STRING] on [STRING] and the hardware entry did not have the same [STRING].

Variable fields

$1: IP address.

$2: VPN instance name. If the ARP entry belongs to the public network, this field displays the public network.

$3: Inconsistent items:

¡     MAC address.

¡     output interface.

¡     output port.

¡     outermost layer VLAN ID.

¡     second outermost layer VLAN ID.

¡     VSI index.

¡     link ID.

Severity level

6

Example

ARP/6/ARP_ENTRY_CONFLICT: The software entry for 1.1.1.1 on the VPN a and the hardware entry did not have the same MAC address, output port, VSI index, and link ID.

ARP/6/ARP_ENTRY_CONFLICT: The software entry for 1.1.1.2 on the public  network and the hardware entry did not have the same MAC address, output port, VSI index, and link ID.

Explanation

The software entry for the specified IP address is not the same as the hardware entry. For example, they do not have the same output interface.

Recommended action

No action is required. ARP automatically refreshes the hardware entries.

 

ARP_HOST_IP_CONFLICT

Message text

The host [STRING] connected to interface [STRING] cannot communicate correctly, because it uses the same IP address as the host connected to interface [STRING].

Variable fields

$1: IP address.

$2: Interface name.

$3: Interface name.

Severity level

4

Example

ARP/4/ARP_HOST_IP_CONFLICT: The host 1.1.1.1 connected to interface GigabitEthernet1/0/1 cannot communicate correctly, because it uses the same IP address as the host connected to interface GigabitEthernet1/0/2.

Explanation

The sender IP address in a received ARP message conflicted with the IP address of a host connected to another interface.

Recommended action

Check whether the hosts that send the ARP messages are legitimate. Disconnect the illegal host from the network.

 

ARP_RATE_EXCEEDED

Message text

The ARP packet rate ([UINT32] pps) exceeded the rate limit ([UINT32] pps) on interface [STRING] in the last [UINT32] seconds.

Variable fields

$1: ARP packet rate.

$2: ARP limit rate.

$3: Interface name.

$4: Interval time.

Severity level

4

Example

ARP/4/ARP_RATE_EXCEEDED: The ARP packet rate (100 pps) exceeded the rate limit (80 pps) on interface Ethernet0/1/0 in the last 10 seconds.

Explanation

An interface received ARP messages at a higher rate than the rate limit.

Recommended action

Verify that the hosts at the sender IP addresses are legitimate.

 

ARP_SENDER_IP_INVALID

Message text

Sender IP [STRING] was not on the same network as the receiving interface [STRING].

Variable fields

$1: IP address.

$2: Interface name.

Severity level

6

Example

ARP/6/ARP_SENDER_IP_INVALID: Sender IP 192.168.10.2 was not on the same network as the receiving interface Ethernet0/1/0.

Explanation

The sender IP of a received ARP message was not on the same network as the receiving interface.

Recommended action

Verify that the host at the sender IP address is legitimate.

 

ARP_SENDER_MAC_INVALID

Message text

Sender MAC [STRING] was not identical to Ethernet source MAC [STRING] on interface [STRING].

Variable fields

$1: MAC address.

$2: MAC address.

$3: Interface name.

Severity level

6

Example

ARP/6/ARP_SENDER_MAC_INVALID: Sender MAC 0000-5E14-0E00 was not identical to Ethernet source MAC 0000-5C14-0E00 on interface Ethernet0/1/0.

Explanation

An interface received an ARP message. The sender MAC address in the message body was not identical to the source MAC address in the Ethernet header.

Recommended action

Verify that the host at the sender MAC address is legitimate.

 

ARP_SENDER_SMACCONFLICT

Message text

Packet was discarded because its sender MAC address was the MAC address of the receiving interface.

Interface: [STRING], sender IP: [STRING], target IP: [STRING].

Variable fields

$1: Interface name.

$2: Sender IP address.

$3: Target IP address.

Severity level

6

Example

Packet discarded for the sender MAC address is the same as the receiving interface.

Interface: GE1/0/1 sender IP: 1.1.2.2 target IP: 1.1.2.1,

Explanation

The sender MAC address of a received ARP packet conflicts with the MAC address of the device.

Recommended action

No action is required.

 

ARP_SENDER_SMACCONFLICT_VSI

Message text

Packet was discarded because its sender MAC address was the MAC address of the receiving interface.

Interface: [STRING], sender IP: [STRING], target IP: [STRING],VSI index: [UINT32], link ID: [UINT32].

Variable fields

$1: Interface name.

$2: Sender IP address.

$3: Target IP address.

$4: VSI index.

$5: Link ID.

Severity level

6

Example

Packet discarded for the sender MAC address is the same as the receiving interface.

Interface: VSI3 sender IP: 1.1.2.2 target IP: 1.1.2.1, VSI Index: 2, Link ID: 0

Explanation

The sender MAC address of a received ARP packet conflicts with the MAC address of the device. The receiving interface is a VSI interface.

Recommended action

No action is required.

 

ARP_SRC_MAC_FOUND_ATTACK

Message text

An attack from MAC [STRING] was detected on interface [STRING].

Variable fields

$1: MAC address.

$2: Interface name.

Severity level

6

Example

ARP/6/ARP_SRC_MAC_FOUND_ATTACK: An attack from MAC 0000-5E14-0E00 was detected on interface Ethernet0/1/0.

Explanation

The source MAC-based ARP attack detection feature received more ARP packets from the same MAC address within 5 seconds than the specified threshold.

This message indicates the risk of attacks.

Recommended action

Verify that the host at the source MAC address is legitimate.

 

ARP_SUP_ENABLE_FAILED

Message text

Failed to enable ARP flood suppression on VSI [string].

Variable fields

$1: VSI name.

Severity level

4

Example

ARP/4/ARP_SUP_ENABLE_FAILED: -MDC=1; Failed to enable ARP flood suppression on VSI vpna.

Explanation

This message is sent when the system failed to enable ARP flood suppression for a VSI. The minimum interval between two log messages is 2 seconds. To prevent the system from failing to send the message, wait for a minimum of 2 seconds before you enable ARP flood suppression for another VSI.

Recommended action

1.     Verify that the device supports ARP flood suppression.

2.     Verify that the hardware resources are sufficient.

 

ARP_TARGET_IP_INVALID

Message text

Target IP [STRING] was not the IP of the receiving interface [STRING].

Variable fields

$1: IP address.

$2: Interface name.

Severity level

6

Example

ARP/6/ARP_TARGET_IP_INVALID: Target IP 192.168.10.2 was not the IP of the receiving interface Ethernet0/1/0.

Explanation

The target IP address of a received ARP message was not the IP address of the receiving interface.

Recommended action

Verify that the host at the sender IP address is legitimate.

 

ARP_THRESHOLD_REACHED

Message text

The alarm threshold for dynamic ARP entry learning was reached on interface [STRING].

Variable fields

$1: Interface name.

Severity level

4

Example

ARP/4/ ARP_THRESHOLD_REACHED: The alarm threshold for dynamic ARP entry learning was reached on interface GigabitEthernet1/0/1.

Explanation

This message is sent when the alarm threshold for dynamic ARP learning was reached on an interface.

Recommended action

Verify that the number of learned dynamic ARP entries matches the actual number of devices in the network, and no ARP attack sources exist in the network.

 

DUPIFIP

Message text

Duplicate address [STRING] on interface [STRING], sourced from [STRING].

Variable fields

$1: IP address.

$2: Interface name.

$3: MAC Address.

Severity level

6