can't get single value from a OBJECT..SEQUENCE OF..
i've troubles using opmanager with snmpd.
snmpd (snmpd.conf attached) runs on a linux box to collect data from the systemboard via ipmi.
the output is stored in the mib-tree of snmpd (UCD-SNMP-MIB).
i check for ps redundancy and fan redundancy (there are exec lines in the snmpd.conf).
snmpd stores the result in a table. for each exec command in the snmpd.conf the index of the parameters will be increased.
eg.
result of pe2800.PSRedundancy will be stored with index 1.
result of pe2800.FanRedundancy will be stored with index 2.
the result can be checked with
snmpget -c public -v 1 10.130.1.17 .1.3.6.1.4.1.2021.8.1.100.1 for the first exec
snmpget -c public -v 1 10.130.1.17 .1.3.6.1.4.1.2021.8.1.100.2 for the second exec
it is possible to load the mib into opmanager, but can not get a single value.
it is only possible to browse to .1.3.6.1.4.1.2021.8.1.100. if i press get values i get both values, but that is not realy useful for alarm triggering. if i append at the oid line the index (.1 for the first,or .2 for the second) than opmanager is not able to read the value. the output from opmanager:
request failed: get response pdu received from 10.130.1.17
error indication in response: there is no such variable name in this mib.
errorindex: 1
that's true that there is no variable, because the index depends on how much exec lines are configured in the snmpd.conf.
how can i solve this?
why does opmanager need a mib? the correct oid should be enough.
i tried an other solution and it worked without a mib.
thx
arno
snmpd (snmpd.conf attached) runs on a linux box to collect data from the systemboard via ipmi.
the output is stored in the mib-tree of snmpd (UCD-SNMP-MIB).
i check for ps redundancy and fan redundancy (there are exec lines in the snmpd.conf).
snmpd stores the result in a table. for each exec command in the snmpd.conf the index of the parameters will be increased.
eg.
result of pe2800.PSRedundancy will be stored with index 1.
result of pe2800.FanRedundancy will be stored with index 2.
the result can be checked with
snmpget -c public -v 1 10.130.1.17 .1.3.6.1.4.1.2021.8.1.100.1 for the first exec
snmpget -c public -v 1 10.130.1.17 .1.3.6.1.4.1.2021.8.1.100.2 for the second exec
it is possible to load the mib into opmanager, but can not get a single value.
it is only possible to browse to .1.3.6.1.4.1.2021.8.1.100. if i press get values i get both values, but that is not realy useful for alarm triggering. if i append at the oid line the index (.1 for the first,or .2 for the second) than opmanager is not able to read the value. the output from opmanager:
request failed: get response pdu received from 10.130.1.17
error indication in response: there is no such variable name in this mib.
errorindex: 1
that's true that there is no variable, because the index depends on how much exec lines are configured in the snmpd.conf.
how can i solve this?
why does opmanager need a mib? the correct oid should be enough.
i tried an other solution and it worked without a mib.
thx
arno