I realize this MIB object can vary in size (up to 256 bytes), so I wonder if
there is a size-limitation in this? Though, I don't get this error if I use
the SNMP_Walk proc. Any ideas? Suggestions? Is there something wrong?
Follows a small script of what has happened to me:
% snmp0 walk x "dPList dBList dABConfig dDBConfig dPConfig" {puts $x}
tooBig 5 {1.3.6.1.4.1.34.2.1.3.1.6 {ASN1 NULL} {}} {1.3.6.1.4.1.34.2.1.3.1.4 {ASN1 NULL} {}} {1.3.6.1.4.1.34.2.1.3.1.10 {ASN1 NULL} {}} {1.3.6.1.4.1.34.2.1.3.1.11 {ASN1 NULL} {}} {1.3.6.1.4.1.34.2.1.3.1.9 {ASN1 NULL} {}}
% mib name 1.3.6.1.4.1.34.2.1.3.1.9
dPConfig
% snmp0 get dPConfig.0
{1.3.6.1.4.1.34.2.1.3.1.9.0 {OCTET STRING} 0.3R-0.2R-0.1R-0.0R-1.3G-1.2G-1.1G-1.0G-2.3R-2.2R-2.1R-2.0R-3.3G-3.2G-3.1G-3.0G-4.3R-4.2R-4.1R-4.0R-5.3G-5.2G-5.1G-5.0G-6.3R-6.2R-6.1R-6.0R-7.3R-7.2R-7.1R-7.0R-8.3R-8.2R-8.1R-8.0R-9.3R-9.2R-9.1R-9.0R-10.3R-10.2R-10.1R-10.0R-11.3R-11.2R-11.1R-11.0R-12.3R-12.2R-12.1R-12.0R-13.3R-13.2R-13.1R-13.0R-14.3R-14.2R-14.1R-14.0R-15.3R-15.2R-15.1R-15.0R}
% SNMP_Walk snmp0 dTable
doug [xxx.xxx.xx.xx] [Fri Nov 1 13:50:24 1996]:
dIndex.0: 0
dName.0: doug
dNumSB.0: 1
dBList.0: 2
dVersion.0: 1.2.3
dPList.0: 2.0-2.1-2.2-2.3
dBProc.0: 0
dIVector.0: -1
dPConfig.0: 0.3R-0.2R-0.1R-0.0R-1.3G-1.2G-1.1G-1.0G-2.3R-2.2R-2.1R-2.0R-3.3G-3.2G-3.1G-3.0G-4.3R-4.2R-4.1R-4.0R-5.3G-5.2G-5.1G-5.0G-6.3R-6.2R-6.1R-6.0R-7.3R-7.2R-7.1R-7.0R-8.3R-8.2R-8.1R-8.0R-9.3R-9.2R-9.1R-9.0R-10.3R-10.2R-10.1R-10.0R-11.3R-11.2R-11.1R-11.0R-12.3R-12.2R-12.1R-12.0R-13.3R-13.2R-13.1R-13.0R-14.3R-14.2R-14.1R-14.0R-15.3R-15.2R-15.1R-15.0R
dABConfig.0: 0F-1G-2G-3G
dDBConfig.0: 0G-1G
Any help is greatly appreciated. Thanks,
Jorge
BTW: we are running scotty.v2.0.1, tcl.v7.4, and tk.v.4.0 on solaris 2.5.
Our snmpd agent is SNMPv1
===================
Jorge A. Osorio
Software Engineer
SMCC - ESSG
email: jorge.osorio@west.sun.com