Hey @ll,
 
unfortunately Brocade has changed the counters of rxwords and txwords to a different location in the snmp tree in Fabric OS 8.x,
what leads to a crash of the brocade_fcport checks in check_mk. 
The change is noticed in their Release Notes:
 
SNMP
·         Support for 64-bit TX/RX statistics in the SW MIB under the connUnitPortStatEntry object and removal of 32-bit TX/RX statistics under the swFCPort object.
 
At the Moment check_mk gets the info from the following oids:
 
( ".1.3.6.1.4.1.1588.2.1.1.1.6.2.1",[...            11, # swFCPortTxWords            12, # swFCPortRxWords...        ])

These entries are gone now:
snmpwalk -v 2c -c community ip 1.3.6.1.4.1.1588.2.1.1.1.6.2.1.11(+12)
iso.3.6.1.4.1.1588.2.1.1.1.6.2.1.11(+12) = No Such Instance currently exists at this OID
 
As it is not 100% documented which are the new oids, i assume that these are the new counters :
 
conn unit port stat count tx elements:  1.3.6.1.3.94.4.5.1.6
The number of octets or bytes that have been transmitted by this port. One second periodic polling of the port. This value is saved and compared with the next polled value to compute net throughput. Note, for Fibre Channel, ordered sets are not included in the Count.
 
conn unit port stat count rx elements:  1.3.6.1.3.94.4.5.1.7
The number of octets or bytes that have been received. by this port. One second periodic polling of the port. This value is saved and compared with the next polled value to compute net throughput. Note, for Fibre Channel, ordered sets are not included in the Count.
 
Unfortunately the output seems to be in HEX now and switched from FC words to bytes.
 
Example output :
 
snmpwalk -v 2c -c community ip 1.3.6.1.3.94.4.5.1.6
iso.3.6.1.3.94.4.5.1.6.16.0.0.39.248.218.71.105.0.0.0.0.0.0.0.0.1 = Hex-STRING: 00 00 00 00 01 AA 1F 08
iso.3.6.1.3.94.4.5.1.6.16.0.0.39.248.218.71.105.0.0.0.0.0.0.0.0.2 = Hex-STRING: 00 00 00 00 07 2F 80 68
iso.3.6.1.3.94.4.5.1.6.16.0.0.39.248.218.71.105.0.0.0.0.0.0.0.0.3 = Hex-STRING: 00 00 00 01 EF 54 B5 D0
iso.3.6.1.3.94.4.5.1.6.16.0.0.39.248.218.71.105.0.0.0.0.0.0.0.0.4 = Hex-STRING: 00 00 00 00 3E A2 F1 40
 
Does anyone have experience with the new oids and can confirm that these are the correct values ?
Has anyone already rewritten the code to reflect the canges ? If not, i could try to rewrite the check.
 
regards,
Andre
 
 
_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Reply via email to