Hi,
Upon use of SilverCreek, I'm getting lots of failed test bearing this
phrase:
"The error-index value in a Reponse-PDU with an error-status of noSuchName
must be between 1 and the number of varbinds in the request. Instead, an
error-index of 0 was received, which does not correspond to any of the 1
variable binding(s)."
I do not really know what to make out of these errors, and how to fix them.
Attached is one of the results prompted by SilverCreek for a V1 test.
I also have lots of this on V2 tests.
Can anyone point me on what I should do to get rid of these errors? It seems
that my parameter settings were retrieved by the test suit, but what could
possibly be the failure on a "received error-index 0" mean?
TIA - Vic
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.672 / Virus Database: 434 - Release Date: 4/28/2004
1.1.11.x The purpose of these tests is to verify that the agent returns the correct
error-status when the test intentionally writes variables. The tests are run on each
of the read-write variables returned in test 1.1.2.
1.1.11.1 This test issues a SET using the current value of the variable.
The expected outcome is for the agent to return noError. (Note: some objects with
peculiar semantics, e.g. tcpConnState, will return badValue instead of noError).
Reference RFC 1157 �� 4.1.5Details for Test 1.1.11.1
[WARNING] Remarks: Possible problems in set-request operation
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
sysContact.0,
DisplayString,
"zxiv1001 <[EMAIL PROTECTED]>"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.1.4.0 sysContact
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
sysContact.0,
DisplayString,
"zxiv1001 <[EMAIL PROTECTED]>"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
sysName.0,
DisplayString,
"SKX1227"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.1.5.0 sysName
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
sysName.0,
DisplayString,
"SKX1227"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
sysLocation.0,
DisplayString,
"In My Place"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.1.6.0 sysLocation
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
sysLocation.0,
DisplayString,
"In My Place"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ifAdminStatus.1,
INTEGER,
"1"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.2.2.1.7.1 ifAdminStatus
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ifAdminStatus.1,
INTEGER,
"1"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ifAdminStatus.2,
INTEGER,
"1"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.2.2.1.7.2 ifAdminStatus
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ifAdminStatus.2,
INTEGER,
"1"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
atPhysAddress.2.1.192.168.63.85,
OctetString,
"0x08:00:46:0e:21:82"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.3.1.1.2.2.1.192.168.63.85 atPhysAddress
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
atPhysAddress.2.1.192.168.63.85,
OctetString,
"0x08:00:46:0e:21:82"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
atPhysAddress.2.1.192.168.63.102,
OctetString,
"0x00:0c:29:b0:7e:d7"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.3.1.1.2.2.1.192.168.63.102 atPhysAddress
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
atPhysAddress.2.1.192.168.63.102,
OctetString,
"0x00:0c:29:b0:7e:d7"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ipForwarding.0,
INTEGER,
"2"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.4.1.0 ipForwarding
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ipForwarding.0,
INTEGER,
"2"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ipDefaultTTL.0,
INTEGER,
"64"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.4.2.0 ipDefaultTTL
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ipDefaultTTL.0,
INTEGER,
"64"
}
}
[WARNING] Remarks: Possible problems in set-request operation
Agent returned out of range error-index value
The error-index value in a Reponse-PDU with an error-status of noSuchName must be
between 1 and the number of varbinds in the request. Instead, an error-index of 0 was
received, which does not correspond to any of the 1 variable binding(s).
This condition should only occur when testing an SNMPv2/v3 to SNMPv1 proxy that has
translated an error-status of authorizationError to noSuchName. If this is such a
case, this warning can be disregarded.
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ipRouteIfIndex.0.0.0.0,
INTEGER,
"2"
}
}
"
[FAILED] Remarks: SET on 1.3.6.1.2.1.4.21.1.2.0.0.0.0 ipRouteIfIndex
Received Message Data {
Error-Status: noSuchName,
Error-Index : 0,
Bindings {
ipRouteIfIndex.0.0.0.0,
INTEGER,
"2"
}
}
[FAILED] Remarks: Giving up after 10 failures
