Brocade CRC errors
I've noted that in some cases I'm having CRC errors but they are not collected in graph, in other cases they are collected.
Loking at the porterrshow command there are two CRC values:
crc_err: Number of frames with CRC errors received (Rx).
crc_g_eof: Number of frames with CRC errors with a good EOF received (Rx).
I can find CRC in graph if they are counted in "crc_g_eof". When CRC are only counted as "crc_err" they are not displayed in the graphs
As stated by the description, crc_err should be the total number of crc while crc_g_eof should be a subset of crc_err. In this case it should be better colletting the "total" counter.
Comments
-
Hi,
you are right.
We used connUnitPortStatCountInvalidCRC 1.3.6.1.3.94.4.5.1.40 which is crc_g_eof in portErrShow cli command.
It is now changed to crc_err swConnUnitCRCWithBadEOF 1.3.6.1.4.1.1588.2.1.1.1.27.1.1.
Use this file as a fix:
https://download.stor2rrd.com/patch/7.61-1-11-g188b/sanperf.pl.gz
Gunzip it and copy to /home/stor2rrd/stor2rrd/bin (755, stor2rrd owner)
-rwxr-xr-x 1 stor2rrd stor2rrd 138398 Mar 14 10:24 sanperf.pl
If your web browser gunzips it automatically then just rename it: mv sanperf.pl.gz sanperf.pl
Assure that file size is the same as on above example
We've updated our repository as well.
Howdy, Stranger!
Categories
- 1.5K All Categories
- 24 XORMON NG
- 25 XORMON
- 139 LPAR2RRD
- 12 VMware
- 14 IBM i
- 2 oVirt / RHV
- 4 MS Windows and Hyper-V
- Solaris / OracleVM
- XenServer / Citrix
- Nutanix
- 6 Database
- 2 Cloud
- 10 Kubernetes / OpenShift / Docker
- 118 STOR2RRD
- 18 SAN
- 7 LAN
- 17 IBM
- 3 EMC
- 11 Hitachi
- 5 NetApp
- 15 HPE
- Lenovo
- 1 Huawei
- 1 Dell
- Fujitsu
- 2 DataCore
- INFINIDAT
- 3 Pure Storage
- Oracle