Mike Stupalov
added a comment - As I see part of snmp output in comments, this is possible to check QSFP or not by definitions too.
Give me snmp dump from such device:
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
the problem with definitions format (i tried that before) is, that i wasn't able to check if it is a QSFP+ Transceiver or not. And i only want to display the QSFP TX-Lanes if there are some.
That's why i added the Bias (which is always positive) via definitions and the rest via discovery.
Unfortunately i can't give you access to the device as this is a core switch in a production clinical environment. But i can give you any output you need!
Florian Meyer
added a comment - Hi Mike,
the problem with definitions format (i tried that before) is, that i wasn't able to check if it is a QSFP+ Transceiver or not. And i only want to display the QSFP TX-Lanes if there are some.
That's why i added the Bias (which is always positive) via definitions and the rest via discovery.
Unfortunately i can't give you access to the device as this is a core switch in a production clinical environment. But i can give you any output you need!
Hrm, as I see need some improvements (and probably convert to definitions format).
FloMeyer can you provide snmp access to test device?
If yes, please write me personally mike@observium.org, my dev ip for snmp: 77.222.50.30.
Mike Stupalov
added a comment - Hrm, as I see need some improvements (and probably convert to definitions format).
FloMeyer can you provide snmp access to test device?
If yes, please write me personally mike@observium.org, my dev ip for snmp: 77.222.50.30.
I migrated this sensors discovery to definition style.
Pls try in r10090.