H3C S12500R Switch Router Series System Log Messages Reference(R51xx)-6W100

HomeSupportResource CenterSwitchesH3C S12500R Switch Router SeriesH3C S12500R Switch Router SeriesTechnical DocumentsReference GuidesLog Message ReferencesH3C S12500R Switch Router Series System Log Messages Reference(R51xx)-6W100

 

H3C S12500R Switch Router Series

System Log Messages Reference

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 6W100-20220216

 

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 4

Obtaining log messages from a monitor terminal 4

Obtaining log messages from the log file· 4

Obtaining log messages from a log host 4

Software module list 4

Using this document 8

AAA messages· 1

AAA_FAILURE· 1

AAA_LAUNCH· 1

AAA_SUCCESS· 2

ACL messages· 2

ACL_ACCELERATE_NO_RES· 2

ACL_ACCELERATE_NONCONTIGUOUSMASK· 3

ACL_ACCELERATE_NOT_SUPPORT· 3

ACL_ACCELERATE_NOT_SUPPORTHOPBYHOP· 3

ACL_ACCELERATE_NOT_SUPPORTMULTITCPFLAG·· 4

ACL_ACCELERATE_UNK_ERR· 4

ACL_IPV6_STATIS_INFO·· 4

ACL_NO_MEM·· 5

ACL_STATIS_INFO·· 5

ARP messages· 5

ARP_ACTIVE_ACK_NO_REPLY· 6

ARP_ACTIVE_ACK_NOREQUESTED_REPLY· 6

ARP_BINDRULETOHW_FAILED·· 7

ARP_DETECTION_LOG·· 8

ARP_DUPLICATE_IPADDR_DETECT· 8

ARP_DYNAMIC· 9

ARP_DYNAMIC_IF· 9

ARP_DYNAMIC_SLOT· 10

ARP_ENTRY_CONFLICT· 11

ARP_HOST_IP_CONFLICT· 11

ARP_LOCALPROXY_ENABLE_FAILED·· 12

ARP_RATE_EXCEEDED·· 12

ARP_RATELIMIT_NOTSUPPORT· 13

ARP_SENDER_IP_INVALID·· 13

ARP_SENDER_MAC_INVALID·· 14

ARP_SENDER_SMACCONFLICT· 14

ARP_SENDER_SMACCONFLICT_VSI 15

ARP_SRC_MAC_FOUND_ATTACK· 15

ARP_SUP_ENABLE_FAILED·· 16

ARP_TARGET_IP_INVALID·· 16

ARP_THRESHOLD_REACHED·· 16

ARP_USER_DUPLICATE_IPADDR_DETECT· 17

ARP_USER_MOVE_DETECT· 18

DUPIFIP· 18

DUPIP· 19

DUPVRRPIP· 19

BFD messages· 19

BFD_CHANGE_FSM·· 20

BFD_CHANGE_SESS· 21

BFD_REACHED_UPPER_LIMIT· 21

BGP messages· 21

BGP_EXCEED_ROUTE_LIMIT· 22

BGP_REACHED_THRESHOLD·· 22

BGP_LOG_ROUTE_FLAP· 23

BGP_MEM_ALERT· 23

BGP_PEER_LICENSE_REACHED·· 23

BGP_ROUTE_LICENSE_REACHED·· 24

BGP_STATE_CHANGED·· 24

CFD messages· 24

CFD_CROSS_CCM·· 25

CFD_DRVRET_NOTSUCCESS· 25

CFD_ERROR_CCM·· 26

CFD_LOST_CCM·· 26

CFGMAN messages· 27

CFGMAN_CFGCHANGED·· 27

CFGMAN_OPTCOMPLETION· 27

CGROUP messages· 28

CGROUP_STATUS_CHANGE· 29

DHCP·· 29

DHCP_NORESOURCES· 29

DHCP_NOTSUPPORTED·· 29

DHCPR·· 30

DHCPR_SERVERCHANGE· 30

DHCPR_SWITCHMASTER· 30

DHCPS messages· 30

DHCPS_ALLOCATE_IP· 31

DHCPS_CONFLICT_IP· 31

DHCPS_EXTEND_FAILURE· 32

DHCPS_EXTEND_IP· 32

DHCPS_FILE· 32

DHCPS_RECLAIM_IP· 33

DHCPS_UNAVAILABLE_POOL· 33

DHCPS_VERIFY_CLASS· 33

DHCPS6 messages· 34

DHCPS6_ALLOCATE_ADDRESS· 34

DHCPS6_ALLOCATE_PREFIX· 34

DHCPS6_CONFLICT_ADDRESS· 35

DHCPS6_EXTEND_ADDRESS· 35

DHCPS6_EXTEND_ADDRESS_FAILURE· 36

DHCPS6_EXTEND_PREFIX· 36

DHCPS6_EXTEND_PREFIX_FAILURE· 37

DHCPS6_FILE· 37

DHCPS6_RECLAIM_ADDRESS· 38

DHCPS6_RECLAIM_PREFIX· 38

DHCPS6_UNAVAILABLE_POOL· 39

DHCPSP4· 39

DHCPSP4_FILE· 39

DHCPSP6· 39

DHCPSP6_FILE· 40

DIAG messages· 40

CPU_MINOR_RECOVERY· 40

CPU_MINOR_THRESHOLD·· 40

CPU_SEVERE_RECOVERY· 41

CPU_SEVERE_THRESHOLD·· 41

MEM_ALERT· 42

MEM_BELOW_THRESHOLD·· 43

MEM_EXCEED_THRESHOLD·· 43

DLDP messages· 43

DLDP_AUTHENTICATION_FAILED·· 44

DLDP_LINK_BIDIRECTIONAL· 44

DLDP_LINK_SHUTMODECHG·· 45

DLDP_LINK_UNIDIRECTIONAL· 45

DLDP_NEIGHBOR_AGED·· 46

DLDP_NEIGHBOR_CONFIRMED·· 46

DLDP_NEIGHBOR_DELETED·· 47

DRNI 47

DRNI_GLBCONSISTENCYCHECK_SUCCESS· 47

DRNI_GLBCONSISTENCYCHECK_FAILURE· 47

DRNI_IFCONSISTENCYCHECK_SUCCESS· 48

DRNI_IFCONSISTENCYCHECK_FAILURE· 48

DRNI_IFEVENT_DR_BIND·· 48

DRNI_IFEVENT_DR_GLOBALDOWN· 49

DRNI_IFEVENT_DR_GLOBALUP· 49

DRNI_IFEVENT_DR_NOSELECTED·· 49

DRNI_IFEVENT_DR_PEER_NOSELECTED·· 50

DRNI_IFEVENT_DR_PEER_SELECTED·· 50

DRNI_IFEVENT_DR_SELECTED·· 50

DRNI_IFEVENT_DR_UNBIND·· 51

DRNI_IFEVENT_IPP_BIND·· 51

DRNI_IFEVENT_IPP_DOWN· 51

DRNI_IFEVENT_IPP_UNBIND·· 52

DRNI_IFEVENT_IPP_UP· 52

DRNI_IPP_BLOCK· 52

DRNI_IPP_UNBLOCK· 53

DRNI_KEEPALIVEINTERVAL_MISMATCH· 53

DRNI_KEEPALIVELINK_DOWN· 53

DRNI_KEEPALIVELINK_UP· 54

DRNI_SECONDARY_MADDOWN· 54

DRNI_SYSEVENT_DEVICEROLE_CHANGE· 54

DRNI_SYSEVENT_MAC_CHANGE· 55

DRNI_SYSEVENT_NUMBER_CHANGE· 55

DRNI_SYSEVENT_PRIORITY_CHANGE· 55

DRVPLAT messages· 55

DrvDebug· 55

ERPS messages· 83

ERPS_FSM_CHANGED·· 83

ETHOAM messages· 83

ETHOAM_CONNECTION_FAIL_DOWN· 83

ETHOAM_CONNECTION_FAIL_TIMEOUT· 84

ETHOAM_CONNECTION_FAIL_UNSATISF· 84

ETHOAM_CONNECTION_SUCCEED·· 84

ETHOAM_DISABLE· 85

ETHOAM_DISCOVERY_EXIT· 85

ETHOAM_ENABLE· 85

ETHOAM_ENTER_LOOPBACK_CTRLLED·· 86

ETHOAM_ENTER_LOOPBACK_CTRLLING·· 86

ETHOAM_LOCAL_DYING_GASP· 86

ETHOAM_LOCAL_ERROR_FRAME· 87

ETHOAM_LOCAL_ERROR_FRAME_PERIOD·· 87

ETHOAM_LOCAL_ERROR_FRAME_SECOND·· 87

ETHOAM_LOCAL_ERROR_SYMBOL· 88

ETHOAM_LOCAL_LINK_FAULT· 88

ETHOAM_LOOPBACK_EXIT· 88

ETHOAM_LOOPBACK_EXIT_ERROR_STATU· 89

ETHOAM_LOOPBACK_NO_RESOURCE· 89

ETHOAM_LOOPBACK_NOT_SUPPORT· 89

ETHOAM_QUIT_LOOPBACK_CTRLLED·· 90

ETHOAM_QUIT_LOOPBACK_CTRLLING·· 90

ETHOAM_REMOTE_CRITICAL· 90

ETHOAM_REMOTE_DYING_GASP· 91

ETHOAM_REMOTE_ERROR_FRAME· 91

ETHOAM_REMOTE_ERROR_FRAME_PERIOD·· 91

ETHOAM_REMOTE_ERROR_FRAME_SECOND·· 92

ETHOAM_REMOTE_ERROR_SYMBOL· 92

ETHOAM_REMOTE_EXIT· 92

ETHOAM_REMOTE_FAILURE_RECOVER· 93

ETHOAM_REMOTE_LINK_FAULT· 93

ETHOAM_NO_ENOUGH_RESOURCE· 93

ETHOAM_NOT_CONNECTION_TIMEOUT· 94

FGROUP messages· 94

FLOWGROUP_APPLY_FAIL· 94

FLOWGROUP_MODIFY_FAIL· 95

FNOTIFY messages· 95

NOTIFY· 95

FS messages· 96

FS_UNFORMATTED_PARTITION· 96

FTPD messages· 96

FTP_REACH_SESSION_LIMIT· 96

gRPC messages· 96

GRPC_LOGIN· 97

GRPC_LOGIN_FAILED·· 97

GRPC_LOGOUT· 97

GRPC_SERVER_FAILED·· 98

GRPC_SUBSCRIBE_EVENT_FAILED·· 98

GRPC_RECEIVE_SUBSCRIPTION· 98

HTTPD messages· 98

HTTPD_CONNECT· 99

HTTPD_CONNECT_TIMEOUT· 99

HTTPD_DISCONNECT· 99

HTTPD_FAIL_FOR_ACP· 100

HTTPD_REACH_CONNECT_LIMIT· 100

IFNET messages· 100

IF_BUFFER_CONGESTION_OCCURRENCE· 101

IF_BUFFER_CONGESTION_CLEAR· 101

IF_JUMBOFRAME_WARN· 102

INTERFACE_NOTSUPPRESSED·· 102

INTERFACE_SUPPRESSED·· 102

LINK_UPDOWN· 103

PFC_WARNING·· 103

PHY_UPDOWN· 103

PROTOCOL_UPDOWN· 104

STORM_CONSTRAIN_BELOW·· 104

STORM_CONSTRAIN_CONTROLLED·· 105

STORM_CONSTRAIN_EXCEED·· 105

STORM_CONSTRAIN_NORMAL· 106

TUNNEL_LINK_UPDOWN· 106

TUNNEL_PHY_UPDOWN· 106

VLAN_MODE_CHANGE· 107

IP6ADDR·· 107

IP6ADDR_CREATEADDRESS_ERROR· 107

IP6ADDR_CREATEADDRESS_INVALID·· 108

IP6FW messages· 108

IP6FW_ABNORMAL_HEADERS· 108

IP6FW_SETTING_FAILED_HOPLIMITEXCEED·· 109

IP6FW_SETTING_FAILED_HOPLIMITUNVARIED·· 109

IP6FW_SETTING_FAILED_NDFW·· 110

IPADDR messages· 110

IPADDR_HA_EVENT_ERROR· 111

IPADDR_HA_STOP_EVENT· 112

IPFW messages· 112

IPFW_SETTING_FAILED_ARPFW·· 112

IPFW_SETTING_FAILED_TTLEXCEED·· 113

IPFW_SETTING_FAILED_TTLUNVARIED·· 113

IPoE messages· 113

IPoE_USER_LOGOFF· 114

IPoE_USER_LOGOFF_ABNORMAL· 115

IPoE_USER_LOGON_FAILED·· 118

IPoE_USER_LOGON_SUCCESS· 121

USER_TraceInfo· 121

IPSG messages· 127

IPSG_ADDENTRY_ERROR· 128

IPSG_DELENTRY_ERROR· 129

IPSG_ADDEXCLUDEDVLAN_ERROR· 130

IPSG_DELEXCLUDEDVLAN_ERROR· 131

IRDP messages· 131

IRDP_EXCEED_ADVADDR_LIMIT· 131

ISIS messages· 132

ISIS_LSP_CONFLICT· 132

ISIS_MEM_ALERT· 132

ISIS_NBR_CHG·· 133

ISSU messages· 133

ISSU_PROCESSWITCHOVER· 133

ISSU_ROLLBACKCHECKNORMAL· 134

L2VPN messages· 134

L2VPN_BGPVC_CONFLICT_LOCAL· 134

L2VPN_BGPVC_CONFLICT_REMOTE· 135

L2VPN_HARD_RESOURCE_NOENOUGH· 135

L2VPN_HARD_RESOURCE_RESTORE· 135

L2VPN_LABEL_DUPLICATE· 136

LAGG messages· 136

LAGG_ACTIVE· 136

LAGG_AUTO_AGGREGATION· 137

LAGG_INACTIVE_AICFG·· 137

LAGG_INACTIVE_BFD·· 138

LAGG_INACTIVE_CONFIGURATION· 138

LAGG_INACTIVE_DUPLEX· 139

LAGG_INACTIVE_HARDWAREVALUE· 139

LAGG_INACTIVE_LOWER_LIMIT· 140

LAGG_INACTIVE_PARTNER· 140

LAGG_INACTIVE_PHYSTATE· 141

LAGG_INACTIVE_RESOURCE_INSUFICIE· 141

LAGG_INACTIVE_SPEED·· 142

LAGG_INACTIVE_UPPER_LIMIT· 142

LDP messages· 142

LDP_SESSION_CHG·· 143

LDP_SESSION_GR· 144

LDP_SESSION_SP· 144

LLDP messages· 145

LLDP_CREATE_NEIGHBOR· 145

LLDP_DELETE_NEIGHBOR· 146

LLDP_LESS_THAN_NEIGHBOR_LIMIT· 146

LLDP_NEIGHBOR_AGE_OUT· 147

LLDP_NEIGHBOR_PROTECTION_BLOCK· 147

LLDP_NEIGHBOR_PROTECTION_DOWN· 148

LLDP_NEIGHBOR_PROTECTION_UNBLOCK· 148

LLDP_NEIGHBOR_PROTECTION_UP· 148

LLDP_PVID_INCONSISTENT· 149

LLDP_REACH_NEIGHBOR_LIMIT· 149

LOAD messages· 149

BOARD_LOADING·· 150

LOAD_FAILED·· 150

LOAD_FINISHED·· 150

LOGIN messages· 151

LOGIN_AUTHENTICATION_FAILED·· 151

LOGIN_FAILED·· 151

LOGIN_ INVALID_USERNAME_PWD·· 152

LPDT messages· 152

LPDT_LOOPED·· 152

LPDT_RECOVERED·· 152

LPDT_VLAN_LOOPED·· 153

LPDT_VLAN_RECOVERED·· 153

LS messages· 153

LSM messages· 162

LSM_LABEL_CONFLICT· 162

LSM_SR_LABEL_CONFLICT· 162

LSM_SR_PREFIX_CONFLICT· 163

MAC messages· 163

MAC_DRIVER_ADD_ENTRY· 163

MAC_NOTIFICATION· 164

MAC_TABLE_FULL_GLOBAL· 165

MAC_TABLE_FULL_PORT· 165

MAC_TABLE_FULL_VLAN· 165

MAC_VLAN_LEARNLIMIT_NORESOURCE· 166

MAC_VLAN_LEARNLIMIT_NOTSUPPORT· 166

MFIB messages· 166

MFIB_MEM_ALERT· 166

MPLS messages· 167

MPLS_HARD_RESOURCE_NOENOUGH· 167

MPLS_HARD_RESOURCE_RESTORE· 167

MTLK messages· 167

MTLK_UPLINK_STATUS_CHANGE· 168

ND messages· 168

ND_CONFLICT· 168

ND_DUPADDR· 169

ND_MAC_CHECK· 169

ND_USER_DUPLICATE_IPV6ADDR· 170

ND_USER_MOVE· 171

ND_USER_OFFLINE· 171

ND_USER_ONLINE· 172

NETCONF messages· 172

CLI 172

EDIT-CONFIG·· 173

REPLY· 174

NETCONF_MSG_DEL· 174

ROW-OPERATION· 175

THREAD·· 175

NQA messages· 176

NTP messages· 178

NTP_CLOCK_CHANGE· 178

NTP_LEAP_CHANGE· 178

NTP_SOURCE_CHANGE· 179

NTP_SOURCE_LOST· 179

NTP_STRATUM_CHANGE· 179

OFP messages· 180

OFP_ACTIVE· 180

OFP_ACTIVE_FAILED·· 180

OFP_CONNECT· 180

OFP_FAIL_OPEN· 181

OFP_FLOW_ADD·· 181

OFP_FLOW_ADD_DUP· 182

OFP_FLOW_ADD_FAILED·· 182

OFP_FLOW_ADD_FAILED·· 183

OFP_FLOW_ADD_TABLE_MISS· 183

OFP_FLOW_ADD_TABLE_MISS_FAILED·· 184

OFP_FLOW_DEL· 184

OFP_FLOW_DEL_TABLE_MISS· 185

OFP_FLOW_DEL_TABLE_MISS_FAILED·· 185

OFP_FLOW_MOD·· 186

OFP_FLOW_MOD_FAILED·· 186

OFP_FLOW_MOD_TABLE_MISS· 187

OFP_FLOW_MOD_TABLE_MISS_FAILED·· 187

OFP_FLOW_RMV_GROUP· 188

OFP_FLOW_RMV_HARDTIME· 188

OFP_FLOW_RMV_IDLETIME· 188

OFP_FLOW_RMV_METER· 189

OFP_FLOW_UPDATE_FAILED·· 189

OFP_GROUP_ADD·· 190

OFP_GROUP_ADD_FAILED·· 190

OFP_GROUP_DEL· 191

OFP_GROUP_MOD·· 191

OFP_GROUP_MOD_FAILED·· 192

OFP_METER_ADD·· 192

OFP_METER_ADD_FAILED·· 192

OFP_METER_DEL· 193

OFP_METER_MOD·· 193

OFP_METER_MOD_FAILED·· 194

OFP_MISS_RMV_GROUP· 194

OFP_MISS_RMV_HARDTIME· 194

OFP_MISS_RMV_IDLETIME· 195

OFP_MISS_RMV_METER· 195

OFP_RADARDETECTION· 195

OPTMOD messages· 196

BIAS_HIGH· 196

BIAS_LOW·· 196

BIAS_NORMAL· 197

CFG_ERR· 197

CHKSUM_ERR· 197

FIBER_SFP MODULE_INVALID·· 198

FIBER_SFPMODULE_NOWINVALID·· 198

IO_ERR· 199

MOD_ALM_OFF· 199

MOD_ALM_ON· 199

MODULE_IN· 200

MODULE_OUT· 200

PHONY_MODULE· 200

RX_ALM_OFF· 201

RX_ALM_ON· 201

RX_POW_HIGH· 201

RX_POW_LOW·· 202

RX_POW_NORMAL· 202

TEMP_HIGH· 202

TEMP_LOW·· 203

TEMP_NORMAL· 203

TX_ALM_OFF· 203

TX_ALM_ON· 204

TX_POW_HIGH· 204

TX_POW_LOW·· 204

TX_POW_NORMAL· 205

TYPE_ERR· 205

VOLT_HIGH· 205

VOLT_LOW·· 206

VOLT_NORMAL· 206

OSPF messages· 206

OSPF_DUP_RTRID_NBR· 207

OSPF_IP_CONFLICT_INTRA· 207

OSPF_LAST_NBR_DOWN· 208

OSPF_MEM_ALERT· 208

OSPF_NBR_CHG·· 209

OSPF_RT_LMT· 209

OSPF_RTRID_CHG·· 209

OSPF_RTRID_CONFLICT_INTER· 210

OSPF_RTRID_CONFLICT_INTRA· 210

OSPF_VLINKID_CHG·· 210

OSPFV3 messages· 211

OSPFV3_LAST_NBR_DOWN· 211

OSPFV3_MEM_ALERT· 211

OSPFV3_NBR_CHG·· 212

OSPFV3_RT_LMT· 212

PBR messages· 212

PBR_HARDWARE_ERROR· 213

PFILTER messages· 213

PIM messages· 232

PIM_NBR_DOWN· 232

PIM_NBR_UP· 233

PING messages· 233

PING_STATISTICS· 233

PING_VPN_STATISTICS· 234

PKG messages· 234

PKG_BOOTLOADER_FILE_FAILED·· 234

PKG_BOOTLOADER_FILE_SUCCESS· 235

PKG_INSTALL_ACTIVATE_FAILED·· 235

PKG_INSTALL_ACTIVATE_SUCCESS· 235

PKI messages· 235

PKT2CPU messages· 236

PKT2CPU_NO_RESOURCE· 237

PWDCTL messages· 237

PWDCTL_ADD_BLACKLIST· 237

PWDCTL_CHANGE_PASSWORD·· 238

PWDCTL_FAILED_TO_WRITEPWD·· 238

QOS messages· 238

MIRROR_SYNC_CFG_FAIL· 239

QOS_CAR_APPLYUSER_FAIL· 239

QOS_CBWFQ_REMOVED·· 240

QOS_GTS_APPLYUSER_FAIL· 240

QOS_IFA_OUTPUT_IFFAIL· 240

QOS_IFA_REFRESH_FAIL· 241

QOS_NOT_ENOUGH_BANDWIDTH· 241

QOS_NOT_ENOUGH_NNIBANDWIDTH· 242

QOS_POLICY_APPLYCOPP_CBFAIL· 242

QOS_POLICY_APPLYCOPP_FAIL· 243

QOS_POLICY_APPLYGLOBAL_CBFAIL· 243

QOS_POLICY_APPLYGLOBAL_FAIL· 244

QOS_POLICY_APPLYIF_CBFAIL· 244

QOS_POLICY_APPLYIF_FAIL· 245

QOS_POLICY_APPLYUSER_FAIL· 245

QOS_POLICY_APPLYVLAN_CBFAIL· 246

QOS_POLICY_APPLYVLAN_FAIL· 246

QOS_QMPROFILE_APPLYUSER_FAIL· 247

QOS_QMPROFILE_MODIFYQUEUE_FAIL· 247

QOS_UNI_RESTORE_FAIL· 248

WRED_TABLE_CFG_FAIL· 248

RADIUS messages· 248

RIP messages· 250

RIP_MEM_ALERT· 250

RIP_RT_LMT· 250

RIPNG messages· 250

RIPNG_MEM_ALERT· 250

RIPNG_RT_LMT· 251

RM messages· 251

RM_ACRT_REACH_LIMIT· 251

RM_ACRT_REACH_THRESVALUE· 252

RM_THRESHLD_VALUE_REACH· 252

RRPP messages· 252

RRPP_RING_FAIL· 253

RRPP_RING_RESTORE· 253

RTM messages· 253

RTM_TCL_NOT_EXIST· 253

RTM_TCL_MODIFY· 254

RTM_TCL_LOAD_FAILED·· 254

SCMD messages· 254

PROCESS_ABNORMAL· 255

PROCESS_ACTIVEFAILED·· 255

PROCESS_CORERECORD·· 256

SCM_ABNORMAL_REBOOT· 256

SCM_ABNORMAL_REBOOTMDC· 257

SCM_ABORT_RESTORE· 257

SCM_INSMOD_ADDON_TOOLONG·· 258

SCM_KERNEL_INIT_TOOLONG·· 258

SCM_PROCESS_STARTING_TOOLONG·· 259

SCM_SKIP_PROCESS· 260

SESSION messages· 260

SESSION_IPV4_FLOW·· 261

SESSION_IPV6_FLOW·· 262

SFLOW messages· 263

SFLOW_HARDWARE_ERROR· 263

SHELL messages· 263

SHELL_CMD·· 263

SHELL_CMD_CONFIRM·· 264

SHELL_CMD_EXECUTEFAIL· 264

SHELL_CMD_INPUT· 264

SHELL_CMD_INPUT_TIMEOUT· 265

SHELL_CMD_INVALID_CHARACTER· 265

SHELL_CMD_MATCHFAIL· 265

SHELL_CMDDENY· 266

SHELL_CMDFAIL· 266

SHELL_CRITICAL_CMDFAIL· 266

SHELL_LOGIN· 267

SHELL_LOGOUT· 267

SLBG messages· 267

SLSP messages· 268

SLSP_LABEL_DUPLICATE· 269

SMLK messages· 269

SMLK_LINK_SWITCH· 269

SNMP messages· 269

SNMP_ACL_RESTRICTION· 270

SNMP_AUTHENTICATION_FAILURE· 270

SNMP_GET· 270

SNMP_NOTIFY· 271

SNMP_SET· 271

SNMP_USM_NOTINTIMEWINDOW·· 272

SRP·· 272

SRP_SEGLIST_STATE_DOWN· 273

SRP_SEGLIST_STATE_DOWN_CLEAR· 274

SRP_STATE_DOWN· 275

SRP_STATE_DOWN_CLEAR· 275

SSHS messages· 275

STP messages· 283

STP_BPDU_PROTECTION· 283

STP_BPDU_RECEIVE_EXPIRY· 284

STP_CONSISTENCY_CHECK· 284

STP_CONSISTENCY_RESTORATION· 284

STP_DETECTED_TC· 285

STP_DISABLE· 285

STP_DISCARDING·· 285

STP_DISPUTE· 286

STP_DISPUTE_RESTORATION· 286

STP_EDGEPORT_INACTIVE· 287

STP_ENABLE· 287

STP_FORWARDING·· 287

STP_LOOP_PROTECTION· 288

STP_LOOPBACK_PROTECTION· 288

STP_NOT_ROOT· 288

STP_NOTIFIED_TC· 289

STP_PORT_TYPE_INCONSISTENCY· 289

STP_PVID_INCONSISTENCY· 289

STP_PVST_BPDU_PROTECTION· 290

STP_ROOT_PROTECTION· 290

SYSLOG messages· 290

TELNETD messages· 293

TELNETD_REACH_SESSION_LIMIT· 294

VLAN messages· 294

VLAN_CREATEVLAN_NO_ENOUGH_RESOUR· 294

VLAN_FAILED·· 295

VLAN_VLANMAPPING_FAILED·· 295

VLAN_VLANTRANSPARENT_FAILED·· 295

VRRP messages· 296

VRRP_STATUS_CHANGE· 296

VRRP_VF_STATUS_CHANGE· 297

VRRP_VMAC_INEFFECTIVE· 297

VXLAN messages· 297

VXLAN_LICENSE_UNAVAILABLE· 298

 


Introduction

This document includes the following system messages:

·     Messages specific to the switch.

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

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

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

System log message format

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

·     Log host:

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

·     Destinations except for the log host:

Prefix TIMESTAMP Sysname MODULE/severity/MNEMONIC: CONTENT

 

 

NOTE:

Log message examples in this document use the format for destinations except the log host. They do not contain elements available only for the log host, including the location element.

 

Table 1 System log message elements

Element

Description

<PRI>

Priority identifier. This element is contained only in messages sent to the log host.

It is calculated by using the following formula:

Priority identifier=facilityx8+severity

Where:

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

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

Prefix

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

The element uses the following symbols to indicate message severity:

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

·     Asterisk (*)—Debug level.

TIMESTAMP

Date and time when the event occurred.

The following are commands for configuring the timestamp format:

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

·     Non-log-host destinations—Use the info-center timestamp command.

Sysname

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

%%vendor

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

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

MODULE

Name of the module that produced the message.

severity

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

MNEMONIC

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

location

Optional. This element identifies where the message occurred. This element is contained only in messages sent to the log host.

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

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

The following are examples of location attributes:

·     -MDC=XX, which represents the MDC on which the message occurred.

·     -DevIp=XXX.XXX.XXX.XXX, which represents the source IP of the message.

·     -Slot=XX, which represents the slot on which the message occurred.

·     -Chassis=XX-Slot=XX, which represents the chassis and slot on which the message occurred.

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

CONTENT

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

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

 

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

Table 2 System log message severity levels

Level

Severity

Description

0

Emergency

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

1

Alert

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

2

Critical

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

3

Error

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

4

Warning

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

5

Notification

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

6

Informational

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

7

Debug

Debugging message.

 

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

Table 3 Variable field representations

Representation

Information type

INT16

Signed 16-bit decimal number.

UINT16

Unsigned 16-bit decimal number.

INT32

Signed 32-bit decimal number.

UINT32

Unsigned 32-bit decimal number.

INT64

Signed 64-bit decimal number.

UINT64

Unsigned 64-bit decimal number.

DOUBLE

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

HEX

Hexadecimal number.

CHAR

Single character.

STRING

Character string.

IPADDR

IP address.

MAC

MAC address.

DATE

Date.

TIME

Time.

 

Managing and obtaining system log messages

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

By default, the information center is enabled. Log messages can be output to the console, 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 cfa0:/logfile/ path if the CF card is not partitioned. If the CF card is partitioned, the file path is cfa1:/logfile/.

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

ARP

Address Resolution Protocol

BFD

Bidirectional Forwarding Detection

BGP

Border Gateway Protocol

CFD

Connectivity Fault Detection

CFGMAN

Configuration Management

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

DRVPLAT

Drive Plat

DRNI

Distributed Resilient Network Interconnect

EDEV

Extended-Device Management

ERPS

Ethernet Ring Protection Switching

ETH

Ethernet

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

FIPSNG

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

IP6ADDR

IPv6 Addressing

IP6FW

IPv6 Forwarding

IPADDR

IP Addressing

IPFW

IP Forwarding

IPOE

IP Over Ethernet

IPSEC

IP Security

IPSG

IP Source Guard

IRDP

ICMP Router Discovery Protocol

ISIS

Intermediate System-to-Intermediate System

ISSU

In-Service Software Upgrade

L2TPV2

Layer 2 Tunneling Protocol Version 2

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

PKTCPT

Packet Capture

PFILTER

Packet Filter

PBB

Provider Backbone Bridge

PBR

Policy-Based Routing

PCE

Path Computation Element

PEX

Port Extender

PIM

Protocol Independent Multicast

PING

Packet Internet Groper

PKG

Package

PKI

Public Key Infrastructure

PKT2CPU

Packet to CPU

PORTAL

Portal

PORTSEC

Port Security

PPP

Point to Point Protocol

PPPOES

PPP over Ethernet Server

PWDCTL

Password Control

QOS

Quality of Service

RADIUS

Remote Authentication Dial In User Service

RDDC

Redundancy

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

SLBG

Service Loopback Groups

SLSP

Static LSP

SMLK

Smart Link

SNMP

Simple Network Management Protocol

SSHC

Secure Shell Client

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

TSTREAM

Telemetry Stream

VCF

Vertical Converged Framework

VLAN

Virtual Local Area Network

VRRP

Virtual Router Redundancy Protocol

VSRP

Virtual Service Redundancy Protocol

VXLAN

Virtual eXtensible LAN

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: Username.

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 username or password was incorrect.

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

Recommended action

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

2.     Enter the correct username and password.

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

4.     If the problem persists, contact H3C Support.

 

AAA_LAUNCH

Message text

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

Variable fields

$1: AAA type.

$2: AAA scheme.

$3: Service.

$4: Username.

Severity level

6

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: Username.

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.

 

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 GigabitEthernet1/0/1.

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 GigabitEthernet1/0/1 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 GigabitEthernet1/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

ARP/6/ ARP_DUPLICATE_IPADDR_DETECT: Detected an IP address conflict. The device with MAC address 00-00-01 connected to interface GigabitEthernet1/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_DYNAMIC

Message text

The maximum number of dynamic ARP entries for the device reached.

Variable fields

N/A

Severity level

6

Example

ARP/6/ARP_DYNAMIC: The maximum number of dynamic ARP entries for the device reached.

Explanation

The maximum number of dynamic ARP entries for the device was reached.

Recommended action

No action is required.

 

ARP_DYNAMIC_IF

Message text

The maximum number of dynamic ARP entries for interface [STRING] reached.

Variable fields

$1: Interface name.

Severity level

6

Example

ARP/6/ARP_DYNAMIC_IF: The maximum number of dynamic ARP entries for interface GigabitEthernet1/0/1 reached.

Explanation

The maximum number of dynamic ARP entries for the specified interface was reached.

Recommended action

No action is required.

 

ARP_DYNAMIC_SLOT

Message text

Pattern 1:

The maximum number of dynamic ARP entries for slot [INT32] reached.

Pattern 2:

The maximum number of dynamic ARP entries for chassis [INT32] slot [INT32] reached.

Variable fields

Pattern 1:

$1: Slot number.

Pattern 2:

$1: Chassis number.

$2: Slot number.

Severity level

6

Example

ARP/6/ARP_DYNAMIC_SLOT: The maximum number of dynamic ARP entries for slot 2 reached.

Explanation

Pattern 1:

The maximum number of dynamic ARP entries for the slot was reached.

Pattern 2:

The maximum number of dynamic ARP entries for the slot on the chassis was reached.

Recommended action

No action is required.

 

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_LOCALPROXY_ENABLE_FAILED

Message text

Failed to enable local proxy ARP on interface [STRING].

Variable fields

$1: Interface name.

Severity level

4

Example

ARP/4/ARP_LOCALPROXY_ENABLE_FAILED: -MDC=1-Slot=2; Failed to enable local proxy ARP on interface VSI-interface 1.

Explanation

This message is sent when the device fails to enable local proxy ARP on an interface in a slot. If the interface resides on the MPU, the slot number is 0.

Recommended action

1.     Verify that the card supports local proxy ARP.

2.     Verify that sufficient hardware resources are available.

 

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 GigabitEthernet1/0/1 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_RATELIMIT_NOTSUPPORT

Message text

Pattern 1:

ARP packet rate limit is not support on slot [INT32].

Pattern 2:

ARP packet rate limit is not support on chassis [INT32] slot [INT32].

Variable fields

Pattern 1:

$1: Slot number.

Pattern 2:

$1: Chassis number.

$2: Slot number.

Severity level

6

Example

ARP/6/ARP_RATELIMIT_NOTSUPPORT: ARP packet rate limit is not support on slot 2.

Explanation

Pattern 1:

ARP packet rate limit is not supported on the slot.

Pattern 2:

ARP packet rate limit is not supported on the slot of the chassis was reached.

Recommended action

Verify that the host at the sender IP address is 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 GigabitEthernet1/0/1.

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 GigabitEthernet1/0/1.

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

ARP/6/ ARP_SENDER_SMACCONFLICT: Packet discarded for the sender MAC address is the same as the receiving interface.

Interface: GigabitEthernet1/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

ARP/6/ ARP_SENDER_SMACCONFLICT_VSI: 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 GigabitEthernet1/0/1.

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 make the system send the message successfully, 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 GigabitEthernet1/0/1.

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 GigabitEthernet 1/0/1.

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.

 

ARP_USER_DUPLICATE_IPADDR_DETECT

Message text

Detected a user IP address conflict. New user (MAC [STRING], SVLAN [STRING], CVLAN [STRING]) connecting on interface [STRING] and old user (MAC [STRING], SVLAN [STRING], CVLAN [STRING]) connecting on interface [STRING] were using the same IP address [IPADDR].

Variable fields

$1: MAC address of a new user.

$2: Outer VLAN to which the new user belongs.

$3: Inner VLAN to which the new user belongs.

$4: Name of the interface connecting to the new user.

$5: MAC address of an old user.

$6: Outer VLAN to which the old user belongs.

$7: Inner VLAN to which the old user belongs.

$8: Name of the interface connecting to the old user.

$9: IP address.

Severity level

6

Example

ARP/6/ARP_USER_DUPLICATE_IPADDR_DETECT: Detected a user IP address conflict. New user (MAC 0010-2100-01e1, SVLAN 100, CVLAN 10) connecting on interface GigabitEthernet1/0/1 and old user (MAC 0120-1e00-0102, SVLAN 100, CVLAN 10) connecting on interface GigabitEthernet1/0/1 were using the same IP address 192.168.1.1.

Explanation

ARP detected a user IP address conflict. The IP address of a new user is the same as the IP address of an old user.

Recommended action

Verify that all users have different IP addresses.

 

ARP_USER_MOVE_DETECT

Message text

Detected a user (IP address [IPADDR], MAC address [STRING]) moved to another interface. Before user move: interface [STRING], SVLAN [STRING], CVLAN [STRING]. After user move: interface [STRING], SVLAN [STRING], CVLAN [STRING].

Variable fields

$1: IP address of the user.

$2: MAC address of the user.

$3: Interface name before the migration.

$4: Outer VLAN to which the user belongs before the migration.

$5: Inner VLAN to which the user belongs before the migration.

$6: Interface name after the migration.

$7: Outer VLAN to which the user belongs after the migration.

$8: Inner VLAN to which the user belongs after the migration.

Severity level

6

Example

ARP/6/ARP_USER_MOVE_DETECT: Detected a user (IP address 192.168.1.1, MAC address 0010-2100-01e1) moved to another interface. Before user move: interface GigabitEthernet1/0/1, SVLAN 100, CVLAN 10. After user move: interface GigabitEthernet1/0/2, SVLAN 100, CVLAN 10.

Explanation

ARP detected a user accesses the network through another port.

Recommended action

Use the display arp user-move record command to verify that the migration is legitimate.

 

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

Example

ARP/6/DUPIFIP: Duplicate address 1.1.1.1 on interface GigabitEthernet1/0/1, sourced from 0015-E944-A947.

Explanation

ARP detected a duplicate address.

The sender IP in the received ARP packet was being used by the receiving interface.

Recommended action

Modify the IP address configuration.

 

DUPIP

Message text

IP address [STRING] conflicted with global or imported IP address, sourced from [STRING].

Variable fields

$1: IP address.

$2: MAC Address.

Severity level

6

Example

ARP/6/DUPIP: IP address 30.1.1.1 conflicted with global or imported IP address, sourced from 0000-0000-0001.

Explanation

The sender IP address of the received ARP packet conflicted with the global or imported IP address.

Recommended action

Modify the IP address configuration.

 

DUPVRRPIP

Message text

IP address [STRING] conflicted with VRRP virtual IP address on interface [STRING], sourced from [STRING].

Variable fields

$1: IP address.

$2: Interface name.

$3: MAC address.

Severity level

6

Example

ARP/6/DUPVRRPIP: IP address 1.1.1.1 conflicted with VRRP virtual IP address on interface GigabitEthernet1/0/1, sourced from 0015-E944-A947.

Explanation

The sender IP address of the received ARP packet conflicted with the VRRP virtual IP address.

Recommended action

Modify the IP address configuration.

 

BFD messages

This section contains BFD messages.

BFD_CHANGE_FSM

Message text

Sess[STRING], Ver, Sta: [STRING]->[STRING], Diag: [UINT32]

Variable fields

$1: Source address, destination address, interface, message type, and MPLS FEC of the BFD session. For LSP sessions, this field contains the destination address, mask, and next hop address of LSPs. For PW sessions, this field contains the LSR ID of the peer PE and the PW ID. For TE tunnel sessions, this field contains the source address, destination address, tunnel ID, and LSP ID.

$2: Name of FSM before changing.

$3: Name of FSM after changing.

$4: Diagnostic information:

·     0 (No Diagnostic).

·     1 (Control Detection Time Expired)—A control packet mode BFD session goes down, because local detection times out.

·     2 (Echo Function Failed)—An echo packet mode BFD session goes down, because local detection times out or the source IP address of echo packets is deleted.

·     3 (Neighbor Signaled Session Down)—The remote end notifies the local end of BFD session down.

·     7 (Administratively Down)—The local system prevents a BFD session from being established.

Severity level

5

Example

BFD/5/BFD_CHANGE_FSM: Sess[20.0.4.2/20.0.4.1,LD/RD:533/532, Interface:Vlan204, SessType:Ctrl, LinkType:INET], Ver.1, Sta: INIT->UP, Diag: 0 (No Diagnostic).

BFD/5/BFD_CHANGE_FSM: Sess[20.0.4.2/20.0.4.1,LD/RD:533/532, Interface: Vlan204, SessType: Ctrl, LinkType: LSP, FEC: LSP, 20.0.4.0/24/10.1.1.1], Ver.1, Sta: INIT->UP, Diag: 0 (No Diagnostic).

BFD/5/BFD_CHANGE_FSM: Sess[20.0.4.2/20.0.4.1,LD/RD:533/532, Interface: Vlan204, SessType: Ctrl, LinkType: LSP, FEC: PW FEC-128, 20.0.4.2/1], Ver.1, Sta: INIT->UP, Diag: 0 (No Diagnostic).

BFD/5/BFD_CHANGE_FSM: Sess[20.0.4.2/20.0.4.1,LD/RD:533/532, Interface: Vlan204, SessType: Ctrl, LinkType: LSP, FEC: TE Tunnel, 20.0.4.2/20.0.4.1/100/100], Ver.1, Sta: INIT->UP, Diag: 0 (No Diagnostic).

Explanation

The FSM of the BFD session has been changed. This informational message appears when a BFD session comes up or goes down. Unexpected session loss might indicate high error or packet loss rates in the network.

Recommended action

Check for incorrect BFD configuration or network congestion.

 

BFD_CHANGE_SESS

Message text

Sess[STRING], Ver, Sta: [STRING], Diag: [UINT32]

Variable fields

$1: Source address, destination address, interface, message type, and MPLS FEC of the BFD session. For LSP sessions, this field contains the destination address, mask, and next hop address of LSPs. For PW sessions, this field contains the LSR ID of the peer PE and the PW ID. For TE tunnel sessions, this field contains the source address, destination address, tunnel ID, and LSP ID.

$2: Session state.

$3: Diagnostic code.

Severity level

5

Example

BFD/5/BFD_CHANGE_SESS: Sess[17.1.1.2/17.1.1.1, LD/RD:1537/1537, Interface:GE1/0/1, SessType:Ctrl, LinkType:INET], Ver:1, Sta: Deleted, Diag: 7

Explanation

This informational message appears when a BFD session is deleted.

Recommended action

Check the BFD session configuration.

 

BFD_REACHED_UPPER_LIMIT

Message text

The total number of BFD sessions [ULONG] reached the upper limit. Can’t create a new session.

Variable fields

$1: Total number of BFD sessions.

Severity level

5

Example

BFD/5/BFD_REACHED_UPPER_LIMIT: The total number of BFD session 100 reached upper limit.

Explanation

The total number of BFD sessions has reached the upper limit.

Recommended action

Check the BFD session configuration.

 

BGP messages

This section contains BGP messages.

BGP_EXCEED_ROUTE_LIMIT

Message text

BGP [STRING].[STRING]: The number of routes from peer [STRING] ([STRING]) exceeds the limit [UINT32].

Variable fields

$1: BGP instance name. This field displays default for the public network.

$2: VPN instance name. This field is blank for the public network.

$3: IP address of the BGP peer.

$4: Address family of the BGP peer.

$5: Maximum number of routes.

Severity level

4

Example

BGP/4/BGP_EXCEED_ROUTE_LIMIT: BGP default.vpn1: The number of routes from peer 1.1.1.1 (IPv4-UNC) exceeds the limit 100.

Explanation

The number of routes received from a peer exceeded the maximum number of routes that can be received from the peer.

Recommended action

Determine whether it is caused by attacks:

·     If yes, configure the device to defend against the attacks.

·     If not, increase the maximum number of routes.

 

BGP_REACHED_THRESHOLD

Message text

BGP [STRING].[STRING]: The proportion of prefixes received from peer [STRING] ([STRING]) to maximum allowed prefixes reached the threshold value ([UINT32]%).

Variable fields

$1: BGP instance name. This field displays default for the public network.

$2: VPN instance name. This field is blank for the public network.

$3: IP address of the BGP peer.

$4: Address family of the BGP peer.

$5: Percentage of received routes to the maximum allowed routes.

Severity level

5

Example

BGP/5/BGP_REACHED_THRESHOLD: BGP default.vpn1: The proportion of prefixes received from peer 1.1.1.1 (IPv4-UNC) to maximum allowed prefixes reached the threshold value (60%).

Explanation

The percentage of received routes to the maximum allowed routes reached the threshold.

Recommended action

Determine whether it is caused by attacks:

·     If yes, configure the device to defend against the attacks.

·     If not, increase the threshold value or the maximum number of routes that can be received from the peer.

 

BGP_LOG_ROUTE_FLAP

Message text

BGP [STRING].[STRING]: The route [STRING] [STRING]/[UINT32] learned from peer [STRING] ([STRING]) flapped.

Variable fields

$1: BGP instance name. This field displays default for the public network.

$2: VPN instance name. This field is blank for the public network.

$3: RD of the BGP route. This field is blank for a route without an RD.

$4: BGP route prefix.

$5: Mask of the BGP route prefix.

$6: IP address of the BGP peer.

$7: Address family of the BGP peer.

Severity level

4

Example

BGP/4/BGP_LOG_ROUTE_FLAP: BGP default.vpn1: The route 15.1.1.1/24 learned from peer 1.1.1.1 (IPv4-UNC) flapped.

Explanation

The route learned from a BGP peer flapped.

Recommended action

If a large number of routes flap, determine the route flapping cause and develop a solution.

 

BGP_MEM_ALERT

Message text

BGP [STRING] instance received system memory alert [STRING] event.

Variable fields

$1: BGP instance name. This field displays default for the public network.

$2: Type of the memory alarm, stop and start.

Severity level

5

Example

BGP/5/BGP_MEM_ALERT: BGP default instance received system memory alert start event.

Explanation

BGP received a memory alarm.

Recommended action

If BGP received a system memory alert start event, check the system memory and try to free some memory by adjusting modules that occupied too much memory.

 

BGP_PEER_LICENSE_REACHED

Message text

BGP [STRING]: Number of peers in Established state reached the license limit.

Variable fields

$1: BGP instance name. This field displays default for the public network.

Severity level

5

Example

BGP/5/BGP_PEER_LICENSE_REACHED: BGP default: Number of peers in Established state reached the license limit.

Explanation

The number of peers in Established state reached the license limit.

Recommended action

Determine whether a new license is required.

 

BGP_ROUTE_LICENSE_REACHED

Message text

BGP [STRING]: Number of [STRING] routes reached the license limit.

Variable fields

$1: BGP instance name. This field displays default for the public network.

$2: BGP address family:

·     IPv4-UNC public—IPv4 unicast routes for the public network.

·     IPv6-UNC public—IPv6 unicast routes for the public network.

·     IPv4 private—IPv4 unicast routes, VPNv4 routes, and nested VPN routes for the private network.

·     IPv6 private—IPv6 unicast routes and VPNv6 routes for the private network.

Severity level

5

Example

BGP/5/BGP_ROUTE_LICENSE_REACHED: BGP default: Number of IPv4-UNC public routes reached the license limit.

Explanation

The number of routes in the specified address family reached the license limit.

Recommended action

Determine whether a new license is required.

After the number of routes in the specified family falls below the license limit or the license limit increases, you must manually restore the discarded routes.

 

BGP_STATE_CHANGED

Message text

BGP [STRING].[STRING]: [STRING] state has changed from [STRING] to [STRING].

Variable fields

$1: BGP instance name. This field displays default for the public network.

$2: VPN instance name. This field is blank for the public network.

$3: IP address of the BGP peer.

$4: Name of FSM before the state change.

$5: Name of FSM after the state change.

Severity level

5

Example

BGP/5/BGP_STATE_CHANGED: BGP default.vpn1:192.99.0.2 state has changed from ESTABLISHED to IDLE.

Explanation

The FSM of a BGP peer has changed.

This informational message appears when a BGP peer comes up or goes down.

Recommended action

If a peer goes down unexpectedly, determine whether an error or packet loss occurs.

 

CFD messages

This section contains CFD messages.

CFD_CROSS_CCM

Message text

MEP [UINT16] in SI [INT32] received a cross-connect CCM. It’s SrcMAC is [MAC], SeqNum is [INT32], RMEP is [UINT16], MD ID is [STRING], MA ID is [STRING].

Variable fields

$1: Service instance ID.

$2: Local MEP ID.

$3: Source MAC address.

$4: Sequence number.

$5: Remote MEP ID.

$6: MD ID. If no MD ID is available, "without ID" is displayed.

$7: MA ID.

Severity level

6

Example

CFD/6/CFD_CROSS_CCM: MEP 13 in SI 10 received a cross-connect CCM. Its SrcMAC is 0011-2233-4401, SeqNum is 78, RMEP is 12, MD ID is without ID, MA ID is 0.

Explanation

A MEP received a cross-connect CCM containing a different MA ID or MD ID.

Recommended action

Check the configurations of MEPs on both ends. Make sure the MEPs have consistent configurations, including MD, MA, and level.

 

CFD_DRVRET_NOTSUCCESS

Message text

Driver returned an error. Reason: [STRING]. Please check configuration or specification.

Variable fields

$1: Failure cause:

¡     CFD is not supported.

¡     No enough resources.

¡     Other.

Severity level

6

Example

CFD/6/ CFD_ DRVRET_NOTSUCCESS: Driver returned an error. Reason: No enough resources. Please check configuration or specification.

Explanation

The driver returned an error.

Recommended action

Check the configuration or specification.

 

CFD_ERROR_CCM

Message text

MEP [UINT16] in SI [INT32] received an error CCM. It’s SrcMAC is [MAC], SeqNum is [INT32], RMEP is [UINT16], MD ID is [STRING], MA ID is [STRING].

Variable fields

$1: Service instance ID.

$2: Local MEP ID.

$3: Source MAC address.

$4: Sequence number.

$5: Remote MEP ID.

$6: MD ID. If no MD ID is available, "without ID" is displayed.

$7: MA ID.

Severity level

6

Example

CFD/6/CFD_ERROR_CCM: MEP 2 in SI 7 received an error CCM. Its SrcMAC is 0011-2233-4401, SeqNum is 21, RMEP is 2, MD ID is 7, MA ID is 1.

Explanation

A MEP received an error CCM containing an unexpected MEP ID or lifetime.

Recommended action

Check the CCM configuration. Make sure the CCM intervals are consistent on both ends, and the remote MEP ID is included in the MEP list of the local end.

 

CFD_LOST_CCM

Message text

MEP [UINT16] in SI [INT32] failed to receive CCMs from RMEP [UINT16].

Variable fields

$1: Local MEP ID.

$2: Service instance ID.

$3: Remote MEP ID.

Severity level

6

Example

CFD/6/CFD_LOST_CCM: MEP 1 in SI 7 failed to receive CCMs from RMEP 2.

Explanation

A MEP failed to receive CCMs within 3.5 sending intervals because the link is faulty or the remote MEP does not send CCM within 3.5 sending intervals.

Recommended action

Check the link status and the configuration of the remote MEP. If the link is down or faulty (becomes unidirectional, for example), restore the link. If the remote MEP is configured with the same service instance, make sure the CCM sending intervals are consistent on both ends.

 

CFGMAN messages

This section contains configuration management messages.

CFGMAN_CFGCHANGED

Message text

-EventIndex=[INT32]-CommandSource=[INT32]-ConfigSource=[INT32]-ConfigDestination=[INT32]; Configuration changed.

Variable fields

$1: Event index in the range of 1 to 2147483647.

$2: Configuration change source:

¡     cli—The configuration change came from the CLI.

¡     snmp—The configuration change came from the MIB.

¡     other—The configuration change came from other sources.

$3: Source configuration:

¡     erase—Deleting or renaming a configuration file.

¡     running—Saving the running configuration.

¡     commandSource—Copying a configuration file.

¡     startup—Saving the running configuration to the next-startup configuration file.

¡     local—Saving the running configuration to a local file.

¡     networkFtp—Using FTP to transfer and save a configuration file to the device as the running configuration or next-startup configuration file.

¡     hotPlugging—A card hot swapping caused the configuration to be deleted or become ineffective.

$4: Destination configuration:

¡     erase—Deleting or renaming a configuration file.

¡     running—Saving the running configuration.

¡     commandSource—Copying a configuration file.

¡     startup—Saving the running configuration to the next-startup configuration file.

¡     local—Saving the running configuration to a local file.

¡     networkFtp—Using FTP to transfer and save a configuration file to the device as the running configuration or next-startup configuration file.

¡     hotPlugging—A card hot swapping caused the configuration to be deleted or become ineffective.

Severity level

5

Example

CFGMAN/5/CFGMAN_CFGCHANGED: -EventIndex=[6]-CommandSource=[snmp]-ConfigSource=[startup]-ConfigDestination=[running]; Configuration changed.

Explanation

The running configuration changed in the past 10 minutes.

Recommended action

No action is required.

 

CFGMAN_OPTCOMPLETION

Message text

-OperateType=[INT32]-OperateTime=[INT32]-OperateState=[INT32]-OperateEndTime=[INT32]; Operation completed.

Variable fields

$1: Operation type:

¡     running2startup—Saves the running configuration to the next-startup configuration file.

¡     startup2running—Loads the configuration in the next-startup configuration file.

¡     running2net—Saves the running configuration to a host on the network.

¡     net2running—Transfers a configuration file from a host on the network and loads the configuration.

¡     net2startup—Transfers a configuration file from a host on the network and specifies the file as the next-startup configuration file.

¡     startup2net—Copies the next-startup configuration file to a host on the network.

$2: Operation start time.

$3: Operation status:

¡     InProcess—Operation is in progress.

¡     success—Operation succeeded.

¡     InvalidOperation—Invalid operation.

¡     InvalidProtocol—Invalid protocol.

¡     InvalidSource—Invalid source file name.

¡     InvalidDestination—Invalid destination file name.

¡     InvalidServer—Invalid server address.

¡     DeviceBusy—The device is busy.

¡     InvalidDevice—Invalid device address.

¡     DeviceError—An error occurred on the device.

¡     DeviceNotWritable—The storage medium on the device is write protected.

¡     DeviceFull—The device does not have enough free storage space for the file.

¡     FileOpenError—Failed to open the file.

¡     FileTransferError—Failed to transfer the file.

¡     ChecksumError—File checksum error.

¡     LowMemory—The memory space is not sufficient.

¡     AuthFailed—User authentication failed.

¡     TransferTimeout—Transfer timed out.

¡     UnknownError—An unknown error occurred.

¡     invalidConfig—Invalid configuration.

$4: Operation end time.

Severity level

5

Example

CFGMAN/5/CFGMAN_OPTCOMPLETION: -OperateType=[running2startup]-OperateTime=[248]-OperateState=[success]-OperateEndTime=[959983]; Operation completed.

Explanation

The device is performing or has completed an operation.

Recommended action

If the operation is not successful, locate and resolve the issue.

 

CGROUP messages

This section contains interface collaboration messages.

CGROUP_STATUS_CHANGE

Message text

The status of collaboration group [UINT32] is [STRING].

Variable fields

$1: Collaboration group ID.

$2: Collaboration group state: down or up.

Severity level

6

Example

CGROUP/6/CGROUP_STATUS_CHANGE: The status of collaboration group 1 is up.

Explanation

The status of collaboration group 1 is up or down.

Recommended action

Check the links.

 

DHCP

This section contains DHCP messages.

DHCP_NORESOURCES

Message text

Failed to apply filtering rules for DHCP packets because hardware resources are insufficient.

Variable fields

N/A

Severity level

3

Example

DHCP/3/DHCP_NORESOURCES: Failed to apply filtering rules for DHCP packets because hardware resources are insufficient.

Explanation

The system failed to apply filtering rules for DHCP packets because the hardware resources are insufficient.

Recommended action

Release hardware resources and then apply the rules again.

 

DHCP_NOTSUPPORTED

Message text

Failed to apply filtering rules for DHCP packets because some rules are not supported.

Variable fields

N/A

Severity level

3

Example

DHCP/3/DHCP_NOTSUPPORTED: Failed to apply filtering rules for DHCP packets because some rules are not supported.

Explanation

The system failed to apply filtering rules for DHCP packets because some rules are not supported on the device.

Recommended action

No action is required.

 

 

DHCPR

This section contains DHCP relay agent messages.

DHCPR_SERVERCHANGE

Message text

Switched to the server at [IPADDR] because the current server did not respond.

Variable fields

$1: IP address of the DHCP server.

Severity level

3

Example

DHCPR/3/DHCPR_SERVERCHANGE: -MDC=1;

 Switched to the server at 2.2.2.2 because the current server did not respond.

Explanation

The DHCP relay agent did not receive any responses from the current DHCP server and switched to another DHCP server for IP address acquisition.

Recommended action

No action is required.

 

DHCPR_SWITCHMASTER

Message text

Switched to the master DHCP server at [IPADDR].

Variable fields

$1: IP address of the master DHCP server.

Severity level

3

Example

DHCPR/3/DHCPR_SWITCHMASTER: -MDC=1;

 Switched to the master DHCP server at 2.2.2.2.

Explanation

After a switchback delay time, the DHCP relay agent switched from a backup DHCP server back to the master DHCP server for IP address acquisition.

Recommended action

No action is required.

 

DHCPS messages

This section contains DHCP server messages.

DHCPS_ALLOCATE_IP

Message text

DHCP server received a DHCP client's request packet on interface [STRING], and allocated an IP address [IPADDR](lease [UINT32] seconds) for the DHCP client(MAC [MAC]) from [STRING] pool.

Variable fields

$1: Name of the interface on which DHCP server is configured.

$2: IPv4 address assigned to the DHCP client.

$3: Lease duration of the assigned IPv4 address.

$4: MAC address of the DHCP client.

$5: Name of the address pool to which the assigned IPv4 address belongs.

Severity level

5

Example

DHCPS/5/DHCPS_ALLOCATE_IP: DHCP server received a DHCP client’s request packet on interface Ethernet0/2, and allocated an IP address 1.0.0.91(lease 86400 seconds) for the DHCP client(MAC 0000-0000-905a) from p1 pool.

Explanation

The DHCP server assigned an IPv4 address with a lease to a DHCP client.

Recommended action

No action is required.

 

DHCPS_CONFLICT_IP

Message text

A conflict IP [IPADDR] from [STRING] pool was detected by DHCP server on interface [STRING].

Variable fields

$1: IPv4 address that is in conflict.

$2: Name of the address pool to which the conflicting IPv4 address belongs.

$3: Name of the interface on which DHCP server is configured.

Severity level

5

Example

DHCPS/5/DHCPS_CONFLICT_IP: A conflict IP 100.1.1.1 from p1 pool was detected by DHCP server on interface Ethernet0/2.

Explanation

The DHCP server deleted a conflicting IPv4 address from an address pool.

Recommended action

No action is required.

 

DHCPS_EXTEND_FAILURE

Message text

Extend request from DHCP client (IP [IPADDR], MAC [MAC]) failed, reply NAK message.

Variable fields

$1: IP address of the DHCP client.

$2: MAC address of the DHCP client.

Severity level

5

Example

DHCPS/5/DHCPS_EXTEND_FAILURE: Extend request from DHCP client (IP 1.0.0.91, MAC 0000-0000-905a) failed, reply NAK message.

Explanation

The DHCP server failed to extend the lease for a DHCP client and replied a DHCP-NAK message.

Recommended action

No action is required.

 

DHCPS_EXTEND_IP

Message text

DHCP server received a DHCP client's request packet on interface [STRING], and extended lease from [STRING] pool for the DHCP client (IP [IPADDR], MAC [MAC]).

Variable fields

$1: Name of the interface on which DHCP server is configured.

$2: Name of the address pool to which the client's IPv4 address belongs.

$3: IPv4 address of the DHCP client.

$4: MAC address of the DHCP client.

Severity level

5

Example

DHCPS/5/DHCPS_EXTEND_IP: DHCP server received a DHCP client’s request packet on interface Ethernet0/2, and extended lease from p1 pool for the DHCP client (IP 1.0.0.91, MAC 0000-0000-905a).

Explanation

The DHCP server extended the lease for a DHCP client.

Recommended action

No action is required.

 

DHCPS_FILE

Message text

Failed to save DHCP client information due to lack of storage resources.

Variable fields

N/A

Severity level

4

Example

DHCPS/4/DHCPS_FILE: Failed to save DHCP client information due to lack of storage resources.

Explanation

The DHCP server failed to back up DHCP bindings to the backup file due to lack of storage resources.

Recommended action

Delete unnecessary files to release resources.

 

DHCPS_RECLAIM_IP

Message text

DHCP server reclaimed a [STRING] pool’s lease(IP [IPADDR], lease [UINT32] seconds), which is allocated for the DHCP client (MAC [MAC]).

Variable fields

$1: Name of the address pool to which the assigned IPv4 address belongs.

$2: IPv4 address assigned to the DHCP client.

$3: Lease duration of the assigned IPv4 address.

$4: MAC address of the DHCP client.

Severity level

5

Example

DHCPS/5/DHCPS_RECLAIM_IP: DHCP server reclaimed a p1 pool’s lease(IP 1.0.0.91, lease 86400 seconds), which is allocated for the DHCP client (MAC 0000-0000-905a).

Explanation

The DHCP server reclaimed the IPv4 address assigned to a DHCP client.

Recommended action

No action is required.

 

DHCPS_UNAVAILABLE_POOL

Message text

Available address pool [STRING] cannot be found.

Variable fields

$1: Address pool name. This field is displayed if the address pool is an authorized pool or a DHCP policy-assigned pool.

Severity level

5

Example

DHCPS/5/DHCPS_UNAVAILABLE_POOL: Available address pool 1 cannot be found.

Explanation

The DHCP server cannot find an available address pool.

Recommended action

Configure an address pool available for address assignment.

 

DHCPS_VERIFY_CLASS

Message text

Illegal DHCP client-PacketType=[STRING]-ClientAddress=[MAC];

Variable fields

$1: Type of the packet.

$2: Hardware address of the DHCP client.

Severity level

5

Example

DHCPS/5/DHCPS_VERIFY_CLASS: Illegal DHCP client-PacketType= DHCPDISCOVER-ClientAddress=0000-5e01-0104;

Explanation

The DHCP server verified that the DHCP client was not on the user class whitelist.

Recommended action

Check the validity of the DHCP client.

 

DHCPS6 messages

This section contains DHCPv6 server messages.

DHCPS6_ALLOCATE_ADDRESS

Message text

DHCPv6 server received a DHCPv6 client’s request packet on interface [STRING], and allocated an IPv6 address [IPADDR] (lease [UINT32] seconds) for the DHCP client(DUID [HEX], IAID [HEX]) from [STRING] pool.

Variable fields

$1: Name of the interface on which DHCPv6 server is configured.

$2: IPv6 address assigned to the DHCPv6 client.

$3: Lease duration of the assigned IPv6 address.

$4: DUID of the DHCPv6 client.

$5: IAID of the DHCPv6 client.

$6: Name of the address pool to which the assigned IPv6 address belongs.

Severity level

5

Example

DHCPS6/5/DHCPS6_ALLOCATE_ADDRESS: DHCPv6 server received a DHCPv6 client’s request packet on interface Ethernet0/2, and allocated an IPv6 address 2000::3(lease 60 seconds) for the DHCP client(DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) from p1 pool.

Explanation

The DHCPv6 server assigned an IPv6 address with a lease to a DHCPv6 client.

Recommended action

No action is required.

 

DHCPS6_ALLOCATE_PREFIX

Message text

DHCPv6 server received a DHCPv6 client’s request packet on interface [STRING], and allocated an IPv6 prefix [IPADDR] (lease [UINT32] seconds) for the DHCP client(DUID [HEX], IAID [HEX]) from [STRING] pool.

Variable fields

$1: Name of the interface on which DHCPv6 server is configured.

$2: IPv6 prefix assigned to the DHCPv6 client.

$3: Lease duration of the assigned IPv6 prefix.

$4: DUID of the DHCPv6 client.

$5: IAID of the DHCPv6 client.

$6: Name of the address pool to which the assigned IPv6 prefix belongs.

Severity level

5

Example

DHCPS6/5/DHCPS6_ALLOCATE_PREFIX: DHCPv6 server received a DHCPv6 client’s request packet on interface Ethernet0/2, and allocated an IPv6 prefix 2000::(lease 60 seconds) for the DHCP client(DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) from p1 pool.

Explanation

The DHCPv6 server assigned an IPv6 prefix with a lease to a DHCPv6 client.

Recommended action

No action is required.

 

DHCPS6_CONFLICT_ADDRESS

Message text

A conflict IPv6 address [IPADDR] from [STRING] pool was detected by DHCPv6 server on interface [STRING].

Variable fields

$1: IPv6 address that is in conflict.

$2: Name of the address pool to which the conflicting IPv6 address belongs.

$3: Name of the interface on which DHCPv6 server is configured.

Severity level

5

Example

DHCPS6/5/DHCPS6_CONFLICT_ADDRESS: A conflict IPv6 address 33::1 from p1 pool was detected by DHCPv6 server on interface Ethernet0/2.

Explanation

The DHCPv6 server deleted a conflicting IPv6 address from an address pool.

Recommended action

No action is required.

 

DHCPS6_EXTEND_ADDRESS

Message text

DHCPv6 server received a DHCP client’s request packet on interface [STRING], and extended lease from [STRING] pool for the DHCP client (IPv6 address [IPADDR], DUID [HEX], IAID [HEX]).

Variable fields

$1: Name of the interface on which DHCPv6 server is configured.

$2: Name of the address pool to which the client's IPv6 address belongs.

$3: IPv6 address of the DHCPv6 client.

$4: DUID of the DHCPv6 client.

$5: IAID of the DHCPv6 client.

Severity level

5

Example

DHCPS6/5/DHCPS6_EXTEND_ADDRESS: DHCPv6 server received a DHCP client’s request packet on interface Ethernet0/2, and extended lease from p1 pool for the DHCP client (IPv6 address 2000::3, DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f).

Explanation

The DHCPv6 server extended the address lease for a DHCPv6 client.

Recommended action

No action is required.

 

DHCPS6_EXTEND_ADDRESS_FAILURE

Message text

Extend request for address from DHCPv6 client (IPv6 address [IPADDR], DUID [HEX], IAID [HEX]) failed.

Variable fields

$1: IPv6 address of the DHCPv6 client.

$2: DUID of the DHCPv6 client.

$3: IAID of the DHCPv6 client.

Severity level

5

Example

DHCPS6/5/DHCPS6_EXTEND_ADDRESS_FAILURE: Extend request for address from DHCPv6 client (IPv6 address 2000::3, DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) failed.

Explanation

The DHCPv6 server failed to extend the address lease for a DHCPv6 client.

Recommended action

No action is required.

 

DHCPS6_EXTEND_PREFIX

Message text

DHCPv6 server received a DHCP client’s request packet on interface [STRING], and extended lease from [STRING] pool for the DHCP client (IPv6 prefix [IPADDR], DUID [HEX], IAID [HEX]).

Variable fields

$1: Name of the interface on which DHCPv6 server is configured.

$2: Name of the address pool to which the client's IPv6 prefix belongs.

$3: IPv6 prefix of the DHCPv6 client.

$4: DUID of the DHCPv6 client.

$5: IAID of the DHCPv6 client.

Severity level

5

Example

DHCPS6/5/DHCPS6_EXTEND_PREFIX: DHCPv6 server received a DHCP client’s request packet on interface Ethernet0/2, and extended lease from p1 pool for the DHCP client (IPv6 prefix 2000::, DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f).

Explanation

The DHCPv6 server extended the prefix lease for a DHCPv6 client.

Recommended action

No action is required.

 

DHCPS6_EXTEND_PREFIX_FAILURE

Message text

Extend request for prefix from DHCPv6 client (IPv6 prefix [IPADDR], DUID [HEX], IAID [HEX]) failed.

Variable fields

$1: IPv6 prefix of the DHCPv6 client.

$2: DUID of the DHCPv6 client.

$3: IAID of the DHCPv6 client.

Severity level

5

Example

DHCPS6/5/DHCPS6_EXTEND_PREFIX_FAILURE: Extend request for prefix from DHCPv6 client (IPv6 prefix 2000::, DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f) failed.

Explanation

The DHCPv6 server failed to extend the prefix lease for a DHCPv6 client.

Recommended action

No action is required.

 

DHCPS6_FILE

Message text

Failed to save DHCP client information due to lack of storage resources.

Variable fields

N/A

Severity level

4

Example

DHCPS6/4/DHCPS6_FILE: Failed to save DHCP client information due to lack of storage resources.

Explanation

The DHCPv6 server failed to back up DHCPv6 bindings to the backup file due to lack of storage resources.

Recommended action

Delete unnecessary files to release resources.

 

DHCPS6_RECLAIM_ADDRESS

Message text

DHCPv6 server reclaimed a [STRING] pool's lease(IPv6 address [IPADDR], lease [UINT32] seconds), which is allocated for the DHCPv6 client (DUID [HEX], IAID [HEX]).

Variable fields

$1: Name of the address pool to which the assigned IPv6 address belongs.

$2: IPv6 address assigned to the DHCPv6 client.

$3: Lease duration of the assigned IPv6 address.

$4: DUID of the DHCPv6 client.

$5: IAID of the DHCPv6 client.

Severity level

5

Example

DHCPS6/5/DHCPS6_RECLAIM_ADDRESS: DHCPv6 server reclaimed a p1 pool’s lease(IPv6 address 2000::3, lease 60 seconds), which is allocated for the DHCPv6 client (DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f).

Explanation

The DHCPv6 server reclaimed the IPv6 address assigned to a DHCPv6 client.

Recommended action

No action is required.

 

DHCPS6_RECLAIM_PREFIX

Message text

DHCPv6 server reclaimed a [STRING] pool’s lease(IPv6 prefix [IPADDR], lease [INTEGER] seconds), which is allocated for the DHCPv6 client (DUID [HEX], IAID [HEX]).

Variable fields

$1: Name of the address pool to which the assigned IPv6 prefix belongs.

$2: IPv6 prefix assigned to the DHCPv6 client.

$3: Lease duration of the assigned IPv6 prefix.

$4: DUID of the DHCPv6 client.

$5: IAID of the DHCPv6 client.

Severity level

5

Example

DHCPS6/5/DHCPS6_RECLAIM_PREFIX: DHCPv6 server reclaimed a p1 pool’s lease(IPv6 prefix 2000::, lease 60 seconds), which is allocated for the DHCPv6 client (DUID 0001000118137c37b4b52facab5a, IAID 10b4b52f).

Explanation

The DHCPv6 server reclaimed the IPv6 prefix assigned to a DHCPv6 client.

Recommended action

No action is required.

 

DHCPS6_UNAVAILABLE_POOL

Message text

Available [STRING] pool [STRING] cannot be found.

Variable fields

$1: Address pool or prefix pool.

$2: Name of the address pool or prefix pool. This field is displayed in one of the following conditions:

¡     The address pool is an authorized pool or a DHCP policy-assigned pool.

¡     The prefix pool is specified in an address pool.

Severity level

5

Example

DHCPS6/5/DHCPS6_UNAVAILABLE_POOL: Available address pool 1 cannot be found.

Explanation

The DHCPv6 server cannot find an available IPv6 address or prefix pool.

Recommended action

Configure an IPv6 address pool or prefix pool available for address assignment.

 

DHCPSP4

This section contains DHCP snooping messages.

DHCPSP4_FILE

Message text

Failed to save DHCP client information due to lack of storage resources.

Variable fields

N/A

Severity level

4

Example

DHCPSP4/4/DHCPSP4_FILE: Failed to save DHCP client information due to lack of storage resources.

Explanation

The DHCP snooping device failed to back up DHCP snooping entries to the backup file due to lack of storage resources.

Recommended action

Delete unnecessary files to release resources.

 

DHCPSP6

This section contains DHCPv6 snooping messages.

DHCPSP6_FILE

Message text

Failed to save DHCP client information due to lack of storage resources.

Variable fields

N/A

Severity level

4

Example

DHCPSP6/4/DHCPSP6_FILE: Failed to save DHCP client information due to lack of storage resources.

Explanation

The DHCPv6 snooping device failed to back up DHCPv6 snooping entries to the backup file due to lack of storage resources.

Recommended action

Delete unnecessary files to release resources.

 

DIAG messages

This section contains diagnostic messages.

CPU_MINOR_RECOVERY

Message text

CPU usage recovered to normal state.

Variable fields

N/A

Severity level

5

Example

DIAG/5/CPU_MINOR_THRESHOLD: CPU usage recovered to normal state.

Explanation

The CPU usage decreased below the recovery threshold. The minor alarm was removed and the CPU usage status changed from minor alarm state to recovered state.

Recommended action

No action is required.

 

CPU_MINOR_THRESHOLD

Message text

CPU usage is in minor alarm state.

Variable fields

N/A

Severity level

4

Example

DIAG/4/CPU_MINOR_THRESHOLD: CPU usage is in minor alarm state.

Explanation

The CPU usage increased above the minor alarm threshold and entered minor alarm state. The device sends this message periodically until the CPU usage increases above the severe threshold or the minor alarm is removed.

Recommended action

Operate according to prompt information and use CPU resource reasonably.

 

CPU_SEVERE_RECOVERY

Message text

CPU usage severe alarm removed.

Variable fields

N/A

Severity level

5

Example

DIAG/5/CPU_RECOVERY: CPU usage severe alarm removed.

Explanation

The CPU usage decreased to or below the minor alarm threshold and the severe alarm was removed.

Recommended action

No action is required.

 

CPU_SEVERE_THRESHOLD

Message text

CPU usage severe alarm removed.

Variable fields

N/A

Severity level

3

Example

DIAG/3/CPU_THRESHOLD: CPU usage is in severe alarm state.

Explanation

The CPU usage increased above the severe alarm threshold and entered severe alarm state. The device sends this message periodically until the severe alarm is removed.

Recommended action

Use the display current-configuration | include "monitor cpu-usage" command to view the alarm thresholds. Use the monitor cpu-usage command to adjust the alarm thresholds as required.

 

MEM_ALERT

Message text

system memory info:

                    total           used             free        shared       buffers       cached

Mem:    [ULONG]    [ULONG]    [ULONG]    [ULONG]    [ULONG]    [ULONG]

-/+ buffers/cache:    [ULONG]    [ULONG]

Swap:    [ULONG]    [ULONG]    [ULONG]

Lowmem: [ULONG]  [ULONG]    [ULONG]

Variable fields

·     Mem—Memory information of the whole system:

¡     $1: Total size of allocatable physical memory. The system physical memory contains allocatable physical memory and unallocatable physical memory. Unallocatable physical memory is mainly used for kernel code storage, kernel management, and running of basic functions. Allocatable physical memory is used for such tasks as running service modules and storing files. The size of unallocatable physical memory is automatically calculated based on the system operation requirements. The size of allocatable physical memory is the total physical memory size minus the unallocatable physical memory size.

¡     $2: Size of the physical memory used by the system.

¡     $3: Size of free physical memory of the system.

¡     $4: Total size of physical memory shared by processes.

¡     $5: Size of physical memory used for buffers.

¡     $6: Size of physical memory used for caches.

·     -/+ buffers/cache—Memory usage information of applications:

¡     $7: -/+ Buffers/Cache:used = Mem:Used – Mem:Buffers – Mem:Cached, which indicates the size of physical memory used by applications.

¡     $8: -/+ Buffers/Cache:free = Mem:Free + Mem:Buffers + Mem:Cached, which indicates the size of physical memory available for applications.

·     Swap—Swap memory usage information:

¡     $9: Total size of swap memory.

¡     $10: Size of used swap memory.

¡     $11: Size of free swap memory.

·     Lowmem—Low memory usage information:

¡     $12: Total size of low memory.

¡     $13: Size of used low memory.

¡     $14: Size of free low memory.

Severity level

4

Example

DIAG/4/MEM_ALERT:

system memory info:

                    total         used           free     shared    buffers     cached

Mem:    1784424     920896     863528              0             0      35400

-/+ buffers/cache:    885496     898928

Swap:                0               0               0

Lowmem: 735848     637896      97952

Explanation

A memory alarm was generated, displaying memory usage information.

The system generates this message when the used memory is greater than or equal to the minor, severe, or critical threshold of memory usage.

Recommended action

You can perform the following tasks to help remove the alarm:

·     Verify that appropriate alarm thresholds are set. To view the alarm thresholds, use the display memory-threshold command. Then you can use the memory-threshold command to modify the alarm thresholds if required.

·     Verify that the device is not under attack by checking the ARP table and routing table.

·     Examine and optimize the network, for example, reduce the number of routes, or replace the device with a higher-performance device.

 

MEM_BELOW_THRESHOLD

Message text

Memory usage has dropped below [STRING] threshold.

Variable fields

$1: Memory usage threshold name: minor, severe, or critical.

Severity level

1

Example

DIAG/1/MEM_BELOW_THRESHOLD: Memory usage has dropped below critical threshold.

Explanation

A memory alarm was removed. The message is sent when the system free memory is greater than a memory alarm recovery threshold.

Recommended action

No action is required.

 

MEM_EXCEED_THRESHOLD

Message text

Memory [STRING] threshold has been exceeded.

Variable fields

$1: Memory usage threshold name: minor, severe, or critical.

Severity level

1

Example

DIAG/1/MEM_EXCEED_THRESHOLD: Memory minor threshold has been exceeded.

Explanation

A memory alarm was notified.

When the used memory size is greater than or equal to the minor, severe, or critical threshold of memory usage, the system generates this message and notifies services modules to perform auto repair, such as releasing memory and stopping requesting memory.

Recommended action

You can perform the following tasks to help remove the alarm:

·     Verify that appropriate alarm thresholds are set. To view the alarm thresholds, use the display memory-threshold command. Then you can use the memory-threshold command to modify the alarm thresholds if required.

·     Verify that the device is not under attack by checking the ARP table and routing table.

·     Examine and optimize the network, for example, reduce the number of routes or replace the device with a higher-performance device.

 

DLDP messages

This section contains DLDP messages.

DLDP_AUTHENTICATION_FAILED

Message text

The DLDP packet failed the authentication because of unmatched [STRING] field.

Variable fields

$1: Authentication field.

·     AUTHENTICATION PASSWORD—Authentication password mismatch.

·     AUTHENTICATION TYPE—Authentication type mismatch.

·     INTERVAL—Advertisement interval mismatch.

Severity level

5

Example

DLDP/5/DLDP_AUTHENTICATION_FAILED: The DLDP packet failed the authentication because of unmatched INTERVAL field.

Explanation

The packet authentication failed. Possible reasons include unmatched authentication type, unmatched authentication password, and unmatched advertisement interval.

Recommended action

Check the DLDP authentication type, authentication password, and advertisement interval are consistent with peer end.

 

DLDP_LINK_BIDIRECTIONAL

Message text

DLDP detected a bidirectional link on interface [STRING].

Variable fields

$1: Interface name.

Severity level

6

Example

DLDP/6/DLDP_LINK_BIDIRECTIONAL: DLDP detected a bidirectional link on interface Ethernet1/1.

Explanation

DLDP detected a bidirectional link on an interface.

Recommended action

No action is required.

 

DLDP_LINK_SHUTMODECHG

Message text

DLDP automatically [STRING] interface [STRING] because the port shutdown mode was changed [STRING].

Variable fields

$1: Action according to the port shutdown mode:

¡     blocked.

¡     brought up.

$2: Interface name.

$3: Shutdown mode change:

¡     from manual to auto.

¡     from manual to hybrid.

¡     from hybrid to auto.

¡     from hybrid to manual.

Severity level

5

Example

DLDP/5/DLDP_LINK_SHUTMODECHG: DLDP automatically blocked interface Ethernet1/1 because the port shutdown mode was changed from manual to auto.

Explanation

The interface was shut down or brought up because the shutdown mode changed.

Recommended action

No action is required.

 

DLDP_LINK_UNIDIRECTIONAL

Message text

DLDP detected a unidirectional link on interface [STRING]. [STRING].

Variable fields

$1: Interface name.

$2: Action according to the port shutdown mode:

·     DLDP automatically blocked the interface.

·     Please manually shut down the interface.

·     DLDP automatically shut down the interface. Please manually bring up the interface.

Severity level

3

Example

DLDP/3/DLDP_LINK_UNIDIRECTIONAL: DLDP detected a unidirectional link on interface Ethernet1/1. DLDP automatically blocked the interface.

Explanation

DLDP detected a unidirectional link on an interface.

Recommended action

Check for incorrect cable connection, cable falloff, or other problems.

 

DLDP_NEIGHBOR_AGED

Message text

A neighbor on interface [STRING] was deleted because the neighbor was aged. The neighbor's system MAC is [MAC], and the port index is [UINT16].

Variable fields

$1: Interface name.

$2: MAC address.

$3: Port index.

Severity level

5

Example

DLDP/5/DLDP_NEIGHBOR_AGED: A neighbor on interface Ethernet1/1 was deleted because the neighbor was aged. The neighbor's system MAC is 000f-e269-5f21, and the port index is 1.

Explanation

The interface deleted an aged neighbor.

Recommended action

No action is required.

 

DLDP_NEIGHBOR_CONFIRMED

Message text

A neighbor was confirmed on interface [STRING]. The neighbor's system MAC is [MAC], and the port index is [UINT16].

Variable fields

$1: Interface name.

$2: MAC address.

$3: Port index.

Severity level

6

Example

DLDP/6/DLDP_NEIGHBOR_CONFIRMED: A neighbor was confirmed on interface Ethernet1/1. The neighbor's system MAC is 000f-e269-5f21, and the port index is 1.

Explanation

The interface detected a confirmed neighbor.

Recommended action

No action is required.

 

DLDP_NEIGHBOR_DELETED

Message text

A neighbor on interface [STRING] was deleted because a [STRING] packet arrived. The neighbor's system MAC is [MAC], and the port index is [UINT16].

Variable fields

$1: Interface name.

$2: Packet type, DISABLE or LINKDOWN.

$3: MAC address.

$4: Port index.

Severity level

5

Example

DLDP/5/DLDP_NEIGHBOR_DELETED: A neighbor on interface Ethernet1/1 was deleted because a DISABLE packet arrived. The neighbor's system MAC is 000f-e269-5f21, and the port index is 1.

Explanation

The interface deleted a confirmed neighbor because it received a DISABLE or LINKDOWN packet.

Recommended action

No action is required.

 

DRNI

This section contains DRNI messages.

DRNI_GLBCONSISTENCYCHECK_SUCCESS

Message text

Global type [UINT16] configuration consistency check succeeded.

Variable fields

$1: Configuration consistency check type.

Severity level

6

Example

DRNI/6/DRNI_GLBCONSISTENCYCHECK_SUCCESS: Global type 1 configuration consistency check succeeded.

Explanation

No inconsistency was detected in global type 1 or type 2 configuration.

Recommended action

No action is required.

 

DRNI_GLBCONSISTENCYCHECK_FAILURE

Message text

Global type [UINT16] configuration consistency check failed.

Variable fields

$1: Configuration consistency check type.

Severity level

6

Example

DRNI/6/DRNI_GLBCONSISTENCYCHECK_FAILURE: Global type 1 configuration consistency check failed.

Explanation

Inconsistencies were detected in global type 1 or type 2 configuration.

Recommended action

If configuration inconsistencies exist, use the display drni consistency command to identify the inconsistent settings and modify them to be the same between the DR member devices.

 

DRNI_IFCONSISTENCYCHECK_SUCCESS

Message text

DR interface [STRING] type [UINT16] configuration consistency check succeeded.

Variable fields

$1: Layer 2 aggregate interface name.

$2: Configuration consistency check type.

Severity level

6

Example

DRNI/6/DRNI_IFCONSISTENCYCHECK_SUCCESS: DR interface Bridge-Aggregation 2 type 1 configuration consistency check succeeded.

Explanation

No inconsistency was detected in type 1 or type 2 configuration of a DR interface.

Recommended action

No action is required.

 

DRNI_IFCONSISTENCYCHECK_FAILURE

Message text

DR interface [STRING] type [UINT16] configuration consistency check failed.

Variable fields

$1: Layer 2 aggregate interface name.

$2: Configuration consistency check type.

Severity level

6

Example

DRNI/6/DRNI_IFCONSISTENCYCHECK_FAILURE: DR interface Bridge-Aggregation 2 type 1 configuration consistency check failed.

Explanation

Inconsistencies were detected in type 1 or type 2 configuration of a DR interface.

Recommended action

If configuration inconsistencies exist, use the display drni consistency command to identify the inconsistent settings and modify them to be the same between the DR member devices.

 

DRNI_IFEVENT_DR_BIND

Message text

Interface [STRING] was assigned to DR group [UINT32].

Variable fields

$1: Layer 2 aggregate interface name.

$2: DR group number.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_DR_BIND: Interface Bridge-Aggregation1 was assigned to DR group 1.

Explanation

A Layer 2 aggregate interface was assigned to a DR group.

Recommended action

No action is required.

 

DRNI_IFEVENT_DR_GLOBALDOWN

Message text

The state of DR interface [STRING] changed to globally down.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_DR_GLOBALDOWN: The state of DR interface Bridge-Aggregation1 changed to globally down.

Explanation

One DR interface changed to the globally down state because all its member interfaces and all the member interfaces of the other DR interface in the same DR group became Unselected.

Recommended action

Verify that the device and the DR peer use the same system priority and system MAC address, and different system numbers.

 

DRNI_IFEVENT_DR_GLOBALUP

Message text

The state of DR interface [STRING] changed to globally up.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_DR_GLOBALUP: The state of DR interface Bridge-Aggregation1 changed to globally up.

Explanation

A DR interface changed to the globally up state. If member interfaces of DR interfaces in a DR group become Selected for the first time, the DR interfaces become globally up.

Recommended action

No action is required.

 

DRNI_IFEVENT_DR_NOSELECTED

Message text

Local DR interface [STRING] does not have Selected member ports.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_DR_NOSELECTED: Local DR interface Bridge-Aggregation1 does not have Selected member ports.

Explanation

The local DR interface does not have member ports in Selected state.

Recommended action

Verify that the member ports of the DR interface are correctly configured and connected.

 

DRNI_IFEVENT_DR_PEER_NOSELECTED

Message text

Peer DR interface [STRING] does not have Selected member ports.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_DR_PEER_NOSELECTED: Peer DR interface Bridge-Aggregation1 does not have Selected member ports.

Explanation

The peer DR interface does not have member ports in Selected state.

Recommended action

Verify that the member ports of the DR interface are correctly configured and connected.

 

DRNI_IFEVENT_DR_PEER_SELECTED

Message text

Peer DR interface [STRING] has Selected member ports.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_DR_PEER_SELECTED: Peer DR interface Bridge-Aggregation1 has Selected member ports.

Explanation

The peer DR interface has member ports in Selected state.

Recommended action

No action is required.

 

DRNI_IFEVENT_DR_SELECTED

Message text

Local DR interface [STRING] has Selected member ports.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_DR_SELECTED: Local DR interface Bridge-Aggregation1 has Selected member ports.

Explanation

The local DR interface has member ports in Selected state.

Recommended action

No action is required.

 

DRNI_IFEVENT_DR_UNBIND

Message text

Interface [STRING] was removed from DR group [UINT32].

Variable fields

$1: Layer 2 aggregate interface name.

$2: DR group number.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_DR_UNBIND: Interface Bridge-Aggregation1 was removed from DR group 1.

Explanation

A Layer 2 aggregate interface was removed from a DR group.

Recommended action

No action is required.

 

DRNI_IFEVENT_IPP_BIND

Message text

Interface [STRING] was configured as IPP [UINT16].

Variable fields

$1: Layer 2 aggregate interface name.

$2: IPP number.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_IPP_BIND: Interface Bridge-Aggregation1 was configured as IPP 1.

Explanation

A Layer 2 aggregate interface was configured as the IPP.

Recommended action

No action is required.

 

DRNI_IFEVENT_IPP_DOWN

Message text

IPP [STRING] went down.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_IPP_DOWN: IPP Bridge-Aggregation1 went down.

Explanation

The IPP went down because the DRCP timeout timer expired.

Recommended action

·     Verify that the device and the DR peer use the same system priority and system MAC address, and different system numbers.

·     Verify that the Layer 2 aggregate interface that acts as the IPP is working correctly.

 

DRNI_IFEVENT_IPP_UNBIND

Message text

Configuration for IPP [UINT16] was removed from interface [STRING].

Variable fields

$1: IPP number.

$2: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_IPP_UNBIND: Configuration for IPP 1 was removed from interface Bridge-Aggregation1.

Explanation

The IPP configuration was removed.

Recommended action

No action is required.

 

DRNI_IFEVENT_IPP_UP

Message text

IPP [STRING] came up.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IFEVENT_IPP_UP: IPP Bridge-Aggregation1 came up.

Explanation

The IPP came up because it could receive and send DRCPDUs.

Recommended action

No action is required.

 

DRNI_IPP_BLOCK

Message text

The status of IPP [STRING] changed to blocked.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IPP_BLOCK: The status of IPP Bridge-Aggregation20 changed to blocked.

Explanation

The status of the IPP changed to blocked because the device had been assigned a DR role, and the IPP went down.

Recommended action

·     Verify that the IPL is correctly connected and the cable is working correctly.

·     Verify that the device and the DR peer have correct DR settings.

 

DRNI_IPP_UNBLOCK

Message text

The status of IPP [STRING] changed to unblocked.

Variable fields

$1: Layer 2 aggregate interface name.

Severity level

6

Example

DRNI/6/DRNI_IPP_UNBLOCK: The status of IPP Bridge-Aggregation20 changed to unblocked.

Explanation

The status of the IPP changed to unblocked because the device had been assigned a DR role, and the IPP came up.

Recommended action

No action is required.

 

DRNI_KEEPALIVEINTERVAL_MISMATCH

Message text

Keepalive interval on the local DR device was different than on the neighbor.

Variable fields

N/A

Severity level

6

Example

DRNI/6/DRNI_KEEPALIVEINTERVAL_MISMATCH: Keepalive interval on the local DR device was different than on the neighbor.

Explanation

The device and the DR peer use different keepalive intervals.

Recommended action

Make sure the device and the DR peer use the same keepalive interval.

 

DRNI_KEEPALIVELINK_DOWN

Message text

Keepalive link went down.

Variable fields

N/A

Severity level

6

Example

DRNI/6/DRNI_KEEPALIVELINK_DOWN: Keepalive link went down.

Explanation

The keepalive link went down.

Recommended action

·     Verify Layer 3 connectivity for the keepalive link.

·     Verify that the device and the DR peer use consistent packet source and destination IP addresses for keepalive detection.

 

DRNI_KEEPALIVELINK_UP

Message text

Keepalive link came up.

Variable fields

N/A

Severity level

6

Example

DRNI/6/DRNI_KEEPALIVELINK_UP: Keepalive link came up.

Explanation

The keepalive link came up.

Recommended action

No action is required.

 

DRNI_SECONDARY_MADDOWN

Message text

The interfaces on the device will be placed in DRNI MAD DOWN state.

Variable fields

N/A

Severity level

4

Example

DRNI/6/DRNI_SECONDARY_MADDOWNN: The interfaces on the device will be placed in DRNI MAD DOWN state.

Explanation

All network interfaces on the secondary DR device were shut down because the IPL went down.

Recommended action

·     Verify that the IPL is correctly connected and the cable is working correctly.

·     Verify that the device and the DR peer have correct DR settings.

 

DRNI_SYSEVENT_DEVICEROLE_CHANGE

Message text

Device role changed from [STRING] to [STRING].

Variable fields

$1: Old device role.

$2: New device role.

Severity level

6

Example

DRNI/6/DRNI_SYSEVENT_DEVICEROLR_CHANGE: Device role changed from Secondary to Primary.

Explanation

The DR role of the device changed because of configuration changes on the device or the DR peer.

Recommended action

No action is required.

 

DRNI_SYSEVENT_MAC_CHANGE

Message text

System MAC address changed from [STRING] to [STRING].

Variable fields

$1: Old system MAC address.

$2: New system MAC address.

Severity level

6

Example

DRNI/6/DRNI_SYSEVENT_MAC_CHANGE: System MAC address changed from 1-1-1 to 2-2-2.

Explanation

The DR system MAC address was modified.

Recommended action

No action is required.

 

DRNI_SYSEVENT_NUMBER_CHANGE

Message text

System number changed from [STRING] to [STRING].

Variable fields

$1: Old system number.

$2: New system number.

Severity level

6

Example

DRNI/6/DRNI_SYSEVENT_NUMBER_CHANGE: System number changed from 1 to 2.

Explanation

The DR system number was modified.

Recommended action

No action is required.

 

DRNI_SYSEVENT_PRIORITY_CHANGE

Message text

System priority changed from [UINT16] to [UINT16].

Variable fields

$1: Old system priority.

$2: New system priority.

Severity level

6

Example

DRNI/6/DRNI_SYSEVENT_PRIORITY_CHANGE: System priority changed from 123 to 564.

Explanation

The DR system priority was modified.

Recommended action

No action is required.

 

DRVPLAT messages

This section contains DRVPLAT messages.

DrvDebug

Message text

Chip [UINT32] temperature([UINT32]) in slot [UINT32] is too high and the board will be shutdown.

Variable fields

$1: Chip ID.

$2: Temperature value.

$3: Slot number.

Severity level

4

Example

DRVPLAT/4/DrvDebug: Chip 0 temperature(54) in slot 3 is too high and the board will be shutdown.

Explanation

The temperature of a chip on the specified card has exceeded the upper temperature threshold. The card will be shut down.

Recommended action

1.     Check the fan tray status. Resolve the fan tray issue if any.

2.     If it is not a fan tray issue, contact technical support.

 

Message text

hotspot [UINT32] in slot [UINT32] temperature([UINT32]) is too high, please check it.

Variable fields

$1: Hotspot ID.

$2: Slot number.

$3: Temperature value.

Severity level

4

Example

DRVPLAT/4/DrvDebug: hotspot 1 in slot 2 temperature(90) is too high, please check it.

Explanation

The temperature of the specified card has exceeded the upper temperature threshold. A check is required.

Recommended action

1.     Check the fan tray status. Resolve the fan tray issue if any.

2.     If it is not a fan tray issue, contact technical support.

 

Message text

hotspot [UINT32] in slot [UINT32] temperature([UINT32]) is too high and the board will be shutdown.

Variable fields

$1: Hotspot ID.

$2: Slot number.

$3: Temperature value.

Severity level

4

Example

DRVPLAT/4/DrvDebug: hotspot 1 in slot 2 temperature(90) is too high and the board will be shutdown.

Explanation

The temperature of the specified card has exceeded the upper temperature threshold. The card will be shut down.

Recommended action

1.     Check the fan tray status. Resolve the fan tray issue if any.

2.     If it is not a fan tray issue, contact technical support.

 

Message text

Warning: cpu temperature([UINT32]) in slot [UINT32] is too high, please check it.

Variable fields

$1: Temperature value.

$2: Slot number.

Severity level

4

Example

DRVPLAT/4/DrvDebug: Warning: cpu temperature(90) in slot 2 is too high, please check it.

Explanation

The CPU temperature of the specified card has exceeded the upper temperature threshold. A check is required.

Recommended action

1.     Check the fan tray status. Resolve the fan tray issue if any.

2.     If it is not a fan tray issue, contact technical support.

 

Message text

Warning:Chip [UINT32] temperature([UINT32]) in slot [UINT32] is too high, please check it.

Variable fields

$1: Chip ID.

$2: Temperature value.

$3: Slot number.

Severity level

4

Example

DRVPLAT/4/DrvDebug: Warning:Chip 0 temperature(90) in slot 2 is too high, please check it.

Explanation

The temperature of a chip on the specified card has exceeded the upper temperature threshold. A check is required.

Recommended action

1.     Check the fan tray status. Resolve the fan tray issue if any.

2.     If it is not a fan tray issue, contact technical support.

 

Message text

FPGA [UINT32] temperature([UINT32]) in slot [UINT32] is too high and the board will be shutdown.

Variable fields

$1: FPGA chip ID.

$2: Temperature value.

$3: Slot number.

Severity level

4

Example

DRVPLAT/4/DrvDebug: FPGA 0 temperature(90) in slot 2 is too high and the board will be shutdown.

Explanation

The temperature of an FPGA chip on the card has exceeded the upper temperature threshold. The card will be shut down.

Recommended action

1.     Check the fan tray status. Resolve the fan tray issue if any.

2.     If it is not a fan tray issue, contact technical support.

 

Message text

SubCard cpu CN7809 temperature([UINT32]) in slot [UINT32] is too high and the board will be shutdown.

Variable fields

$1: Temperature value.

$2: Slot number.

Severity level

4

Example

DRVPLAT/4/DrvDebug: SubCard cpu CN7809 temperature(90) in slot 2 is too high and the board will be shutdown.

Explanation

The temperature of the subcard CPU on the specified card has exceeded the upper temperature threshold. The card will be shut down.

Recommended action

1.     Check the fan tray status. Resolve the fan tray issue if any.

2.     If it is not a fan tray issue, contact technical support.

 

Message text

Power Error, there is no input in Power [UINT32].

Variable fields

$1: Power supply ID.

Severity level

4

Example

DRVPLAT/4/DrvDebug: Power Error, there is no input in Power 1.

Explanation

The specified power supply does not have power input.

Recommended action

Check the power supply status. If the power supply is abnormal, replace it or contact technical support.

 

Message text

Warning: Only one power exist!

Variable fields

N/A

Severity level

4

Example

DRVPLAT/4/DrvDebug: Warning: Only one power exist!

Explanation

The device has only one power supply present.

Recommended action

·     Check the status of the other power supplies. If they are abnormal, replace them.

·     Install more power supplies.

 

Message text

Warning: Only one power [UINT32] exist !

Variable fields

$1: Power supply ID.

Severity level

4

Example

DRVPLAT/4/DrvDebug: Warning: Only one power [UINT32] exist !

Explanation

Only one power supply slot on the device has a power supply present.

Recommended action

·     Check the status of the power supplies in the other power supply slots. If they are abnormal, replace them.

·     Install power supplies in the other power supply slots.

 

Message text

Warning: Power [UINT32] differs from power [UINT32] in types!

Variable fields

$1: Power supply ID_1.

$2: Power supply ID_2.

Severity level

4

Example

DRVPLAT/4/DrvDebug: Warning: Power 1 differs from power 2 in types!

Explanation

The two specified power supplies are different in type.

Recommended action

Use power supplies of the same type.

 

Message text

Warning: power [UINT32] voltage is [UINT32], please check!

Variable fields