I'm testing the QNAP TS-873A using _templateqnap(snmpv2)_, which has the first two slots dedicated to SSD M2. However, there seems to be a bug with #HDDINDEX in the template, which is not displaying its correct state:
I'm getting INTEGER: 0 for HDDINDEX in all other keys (so much so that I can collect data as in print), but only for the key: 'hdd.state[{#HDDINDEX}]' the value displayed is -5, probably because it is getting the code from the first slots, which are the M2 SSDs (which I don't use).
I'm testing the QNAP TS-873A using _templateqnap(snmpv2)_, which has the first two slots dedicated to SSD M2. However, there seems to be a bug with #HDDINDEX in the template, which is not displaying its correct state:
Testing with snmpget: snmpget -v2c -c public 10.182.100.3 1.3.6.1.4.1.24681.1.3.11.1.4.1 (this is the m2 ssd slot (unused)) iso.3.6.1.4.1.24681.1.3.11.1.4.1 = INTEGER: -5 snmpget -v2c -c public 10.182.100.3 1.3.6.1.4.1.24681.1.3.11.1.4.2 (this is the m2 ssd slot (unused)) iso.3.6.1.4.1.24681.1.3.11.1.4.2 = INTEGER: -5
snmpget -v2c -c public 10.182.100.3 1.3.6.1.4.1.24681.1.3.11.1.4.3 (THIS IS THE 10TB HDD 1) iso.3.6.1.4.1.24681.1.3.11.1.4.3 = INTEGER: 0 snmpget -v2c -c public 10.182.100.3 1.3.6.1.4.1.24681.1.3.11.1.4.4 (THIS IS THE 10TB HDD 2) iso.3.6.1.4.1.24681.1.3.11.1.4.4 = INTEGER: 0
snmpget -v2c -c public 10.182.100.3 1.3.6.1.4.1.24681.1.3.11.1.4.5 (another unused slot) iso.3.6.1.4.1.24681.1.3.11.1.4.5 = INTEGER: -5 snmpget -v2c -c public 10.182.100.3 1.3.6.1.4.1.24681.1.3.11.1.4.6 (another unused slot) iso.3.6.1.4.1.24681.1.3.11.1.4.6 = INTEGER: -5 snmpget -v2c -c public 10.182.100.3 1.3.6.1.4.1.24681.1.3.11.1.4.7 (another unused slot) iso.3.6.1.4.1.24681.1.3.11.1.4.7 = INTEGER: -5 snmpget -v2c -c public 10.182.100.3 1.3.6.1.4.1.24681.1.3.11.1.4.8 (another unused slot) iso.3.6.1.4.1.24681.1.3.11.1.4.8 = INTEGER: -5
I'm getting INTEGER: 0 for HDDINDEX in all other keys (so much so that I can collect data as in print), but only for the key: 'hdd.state[{#HDDINDEX}]' the value displayed is -5, probably because it is getting the code from the first slots, which are the M2 SSDs (which I don't use).