According rfc 3416 ( http://tools.ietf.org/html/rfc3416#section-4.2.1 ), when the variable binding's name does not have an OBJECT IDENTIFIER prefix which exactly matches the OBJECT IDENTIFIER prefix of any (potential) variable accessible by this request, then its value field is set to "noSuchObject".
And:
"the value of the Response-PDU's error-status field is set to "noError", and the value of its error-index field is zero."
Nevertheless, ROS reply with error-status "noSuchName"(2) in this case.
Example:
I try to request OID
.1.3.6.1.4.1.14988.1.1.3.10.0
from CRS125-24G-1S-RM - it's correct request, i receive response with temperature.
OK, i try to request this OID from RB951Ui-2HnD / RB941-2nD-TC(hAP lite). This is wrong request ... but i receive error-status 2(noSuchName) for whole response instead of "noSuchInstance/noSuchObject" reply for this oid...
Other examples:
.1.3.6.1.2.1.25.2.3.1.5.65536 - good oid (Memory Size)
.1.3.6.1.2.1.25.2.3.1.5.6553 - wrong oid,good response: noSuchInstance
.1.3.6.1.2.1.25.2.3.1.8.65536 - wrong oid,good response: noSuchInstance
.1.3.6.1.2.1.25.2.3.2.5.65536 - wrong oid, wrong responce: noSuchName instead of noSuchInstance/noSuchObject
.1.3.6.1.2.1.2.2.3.1.5.65536 - wrong oid, the same response as above.
-----
Then i try to get 1 oid - it's not so bad
But, in multiple oid - it's a problem!
It occurs with 6.35.1 and 6.35.2.
It occurs also SNMPv3
Re: SNMP v2 (v3) response for wrong oid's.
try
Also like this in the terminal:
system health print oid :
active-fan: .1.3.6.1.4.1.14988.1.1.3.9.0
voltage: .1.3.6.1.4.1.14988.1.1.3.8.0
temperature: .1.3.6.1.4.1.14988.1.1.3.10.0
processor-temperature: .1.3.6.1.4.1.14988.1.1.3.11.0
current: .1.3.6.1.4.1.14988.1.1.3.13.0
power-consumption: .1.3.6.1.4.1.14988.1.1.3.12.0
psu1-state: .1.3.6.1.4.1.14988.1.1.3.15.0
psu2-state: .1.3.6.1.4.1.14988.1.1.3.16.0
Also like this in the terminal:
system health print oid :
active-fan: .1.3.6.1.4.1.14988.1.1.3.9.0
voltage: .1.3.6.1.4.1.14988.1.1.3.8.0
temperature: .1.3.6.1.4.1.14988.1.1.3.10.0
processor-temperature: .1.3.6.1.4.1.14988.1.1.3.11.0
current: .1.3.6.1.4.1.14988.1.1.3.13.0
power-consumption: .1.3.6.1.4.1.14988.1.1.3.12.0
psu1-state: .1.3.6.1.4.1.14988.1.1.3.15.0
psu2-state: .1.3.6.1.4.1.14988.1.1.3.16.0
Re: SNMP v2 (v3) response for wrong oid's.
Kleanto,
Values of other oid - offtopic.
For this example, i use RB951Ui-2HnD (ver. 6.35.2) & linux net-snmp tool "snmpget"(ver 5.5):
I want to get 4 parameters: memory usage, termperature, cpu usage, disk usage.
I construct multiple request:
Now, i receive:
Where other info?
Why i receive error for total request, when only one oid is wrong?
-------------------------------
Should(according rfc 3416):
Values of other oid - offtopic.
For this example, i use RB951Ui-2HnD (ver. 6.35.2) & linux net-snmp tool "snmpget"(ver 5.5):
I want to get 4 parameters: memory usage, termperature, cpu usage, disk usage.
I construct multiple request:
Code: Select all
snmpget -v 2c -c community -On ip.ad.dr.ess .1.3.6.1.2.1.25.2.3.1.6.65536 .1.3.6.1.4.1.14988.1.1.3.10.0 .1.3.6.1.2.1.25.3.3.1.2.1 .1.3.6.1.2.1.25.2.3.1.6.131072Code: Select all
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: .1.3.6.1.4.1.14988.1.1.3.10.0
.1.3.6.1.2.1.25.2.3.1.6.65536 = INTEGER: 26396Why i receive error for total request, when only one oid is wrong?
-------------------------------
Should(according rfc 3416):
Code: Select all
.1.3.6.1.2.1.25.2.3.1.6.65536 = INTEGER: 26364
.1.3.6.1.4.1.14988.1.1.3.10.0 = No Such Object available on this agent at this OID
.1.3.6.1.2.1.25.3.3.1.2.1 = INTEGER: 1
.1.3.6.1.2.1.25.2.3.1.6.131072 = INTEGER: 17932Re: SNMP v2 (v3) response for wrong oid's.
Fixed in 6.36rc16 (2016-May-24 07:04):
Who is online
Users browsing this forum: snowzach and 51 guests