Dram_crc, Tx_buffer, Mp_dx – Brocade BigIron RX Series Configuration Guide User Manual

Page 1452: Lpm_err, Fe_rw

Advertising
background image

1374

BigIron RX Series Configuration Guide

53-1002484-04

Continuous system monitor overview

52

NOTE

If the count of tx_err or rx_data_err is greater than zero, ALARM message will be generated else INFO
message will be generated.

DRAM_CRC

The event type DRAM_CRC monitors a special type of monitoring register, which stores the number
of ingress DRAM CRC errors and detects CRC errors quickly. The ingress DRAM CRC detection has
two methods to detect errors; an interrupt routine method, which is used to detect DRAM CRC
errors quickly and trigger a shutdown of the failed TM. A Long term polling method, which is used to
detect low rate CRC errors. Here is an example from Syslog.

Sep 13 15:01:29:E:System: ALARM: LP9/TM2 has shutdown (TM DRAM CRC: LP9/TM2 (Reg:

0xa50c, Value: 0x7) (shutdown))

NOTE

The threshold to declare the TM DRAM CRC failure is 2.

TX_BUFFER

TM stuck buffer is end result of ingress DRAM CRC, once its stuck, it will stop forwarding traffic. TM
stuck buffers can be detected and recovered from egress.

Here is an example from Syslog.

Sep 13 15:01:29:E:System: ALARM: LP16/TM1 re-initialized (TM TX BUFFER Stuck:

LP16/TM1 (Reg: 0x400000b4, Value: 0x1de) (reinit))

MP_DX

This event type is checking the MP CPU communication with standby MP and line cards via internal
ethernet connectivity. Here is an example from Syslog.

Nov 19 20:21:03:E:System: ALARM:MP DISCO-DX Failure (error mask: 0x2)

LPM_ERR

Each NP on an LP has external Longest Prefix Match memory (LPM) attached to it. To ensure the
integrity of the data the NP has implemented ECC associated with this external memory. Sysmon
periodically scans these registers to detect an error condition. Here is an example from Syslog.

Feb 3 20:13:00:E:System: ALARM:LPM Error LP3/NP1 - set 3 cause ECC address 0x55d0

FE_RW

This event type tests write and read access to the switch fabrics. A Syslog message is generated to
indicate a SFM FE failure. Here is an example from Syslog.

Sep 2 14:00:39:E:System: ALARM:FE Read-Write Test Error: LP1/TM2 Reg 0x18, Read

0x4 != Written 0xffffffff

Advertising