TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".25 = Gauge32: 1250
> > TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".111 = Gauge32: 951
> > TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".8053 = Gauge32: 976
> > TCP-MIB::tcpListenerProcess.ipv4."0.
quot;.111 = Gauge32: 951
TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".8053 = Gauge32: 976
TCP-MIB::tcpListenerProcess.ipv4."0.0.0.0".43677 = Gauge32: 956
TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".53 = Gauge32: 976
TCP-MIB::tcpListenerProcess.ipv4."127
.53 = Gauge32: 976
TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".53 = Gauge32: 976
Error: OID not increasing:
TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".53
>= TCP-MIB::tcpListenerProcess.ipv4."127.0.0.1".53
Only have trouble with this one OID.
Res
DSCPWREDMapDropPkts.10.0.0.0.1 = Counter64:
> > 0
> > ATT-VROUTER-QOS-MIB::qosDSCPWREDMapDropPkts.10.1.0.0.1 = Counter64:
> > 0
> > VM-1:$
> >
> > But if the underlying object has not been defined, I get:
> >
> > VM-1:$ snmpwalk -v2c -c public localhost ATT
-
> MIB::qosDSCPWREDMapTable
> ATT-VROUTER-QOS-MIB::qosShaperClass.7.0 = INTEGER: 7
> Error: OID not increasing: ATT-VROUTER-QOS-MIB::qosDSCPWREDMapTable
> >= ATT-VROUTER-QOS-MIB::qosShaperClass.7.0
>
> VM-1:$ snmpwalk -On -v2c -c public localhost ATT-VROUTER-QOS-
> MIB::q
object has not been defined, I get:
VM-1:$ snmpwalk -v2c -c public localhost ATT-VROUTER-QOS-
MIB::qosDSCPWREDMapTable
ATT-VROUTER-QOS-MIB::qosShaperClass.7.0 = INTEGER: 7
Error: OID not increasing: ATT-VROUTER-QOS-MIB::qosDSCPWREDMapTable
>= ATT-VROUTER-QOS-MIB::qosShaperClass.7.0
VM-1:$ snmp
On Thu, Feb 18, 2010 at 1:09 AM, Dave Shield wrote:
> If your handler isn't checking the column information
> properly, that might well result in the behaviour that you
> are seeing.
I'm not sure why this is a problem. But, I have fixed it by putting
this in the handler code:
if (!entry)
c
On 18 February 2010 01:29, slowpoison wrote:
> I do see that internally my agent returns SNMP_NOSUCHINSTANCE after
> the last row, but it receives a repeat request from the master agent,
> to which it replies with the first row.
How many columns are there in the table?
Are you checking which colu
he agent is working, but when I walk the agent, snmpwalk command ends
with the error
Error: OID not increasing
This is because after the agent serves the last row, it returns the
first row again. Is this inherent to the way generated code works, or
am I seeing a bug?
I do see that internally my ag
times. There are 2 problems comming. First
is SIGPIPE signal because probably time out occur of snmpwalk (well
resolved using signal(SIGPIPE, SIG_IGN);) and socket closed to write.
and second is sometime snmpwalk did not travel whole table and says
Error: OID not increasing:
and used -Cc to
times. There are 2 problems comming. First
is SIGPIPE signal because probably time out occur of snmpwalk (well
resolved using signal(SIGPIPE, SIG_IGN);) and socket closed to write.
and second is sometime snmpwalk did not travel whole table and says
Error: OID not increasing:
and used -Cc to
On Wed, 2005-11-16 at 21:22 +0100, Ole Bjørn Hessen wrote:
> 1. Is there a way for the perl SNMP bulkwalk to discover non-increasing
> OIDs ? The "snmpbulkwalk"-commands discovers this error, and stops
> processing. Why does not the perl discover this and returns the handle?
Because no-one has w
TTMON-MIB::rttMonStatsCaptureCompletions.2642.62906171.1.1.1 = INTEGER: 0
CISCO-RTTMON-MIB::rttMonStatsCaptureCompletions.2642.62906171.1.1.1 = INTEGER: 0
Error: OID not increasing:
CISCO-RTTMON-MIB::rttMonStatsCaptureCompletions.2642.62906171.1.1.1
>= CISCO-RTTMON-MIB::rttMonStatsCaptureComple
: Jim Su [mailto:[EMAIL PROTECTED]
Sent: Friday, July 15, 2005 4:06 PM
To: net-snmp-users@lists.sourceforge.net
Subject: RE: Error: OID not increasing
I have collected more data.
The agent seems to fall into the situation to handle a bogus "lowest" oid list
so it "walk" all the wa
known [55.6E.6B.6E.6F.77.6E (hex)]
9: sysORLastChange.0 (timeticks) 0 days 00h:00m:00s.00th (0)
...
Endless loop
-Original Message-
From: Jim Su [mailto:[EMAIL PROTECTED]
Sent: Friday, July 15, 2005 11:55 AM
To: net-snmp-users@lists.sourceforge.net
Subject: RE: Error: OID not inc
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Robert Story
Sent: Friday, July 15, 2005 3:24 AM
To: Jim Su
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: Error: OID not increasing
On Thu, 14 Jul 2005 15:04:06 +0800 Jim wrote:
JS> My net-snmp version is 5.1
On Thu, 14 Jul 2005 15:04:06 +0800 Jim wrote:
JS> My net-snmp version is 5.1.2.
JS> Yes, it is very consistent. If I run snmpd with the following command line
JS> options it doesn't give me the error message.
JS>
JS> /usr/sbin/snmpd -Lsd -L -f -Dgenie -p /var/run/snmpd.pid
JS>
JS> But if I star
rn;
case: ...
}
Thanks,
Jim
-Original Message-
From: Robert Story [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 13, 2005 8:32 PM
To: Jim Su
Cc: Jim Su; Net-Snmp-Users
Subject: Re: Error: OID not increasing
On Mon, 11 Jul 2005 15:50:43 +0800 Jim wrote:
JS> I n
On Mon, 11 Jul 2005 15:50:43 +0800 Jim wrote:
JS> I noticed the difference as following -
JS> If the snmpd is started with the following options : -f -L -Dge it's okay.
JS> No error occurred.
JS> If snmpd is started with the following options:-Lsd -Lf
JS> /dev/null -p
AM
To: Net-Snmp-Users
Subject: Error: OID not increasing
Hi Greeting:
I imitated the agent implementation of ipAddr table. Instead of scan the
if and get ip address. I use tcp to get the ip address list from another
process and compare the oid to return the value of ip address. The return
IpAddress: 192.168.0.3
GENIE-ATM-SYSTEM-MIB::geAtmExporterIpAddr.192.168.0.3 = IpAddress: 192.168.0.3
Error: OID not increasing: GENIE-ATM-SYSTEM-MIB::geAtmExporterIpAddr.192.168.0.3
>= GENIE-ATM-SYSTEM-MIB::geAtmExporterIpAddr.192.168.0.3
The following is the out put of the snmpwalk after the snmpd
On Wed, 9 Mar 2005 10:24:43 +0100 MAUGER wrote:
MFER> >>>>MFER> SNMPv2-MIB::sysServices.0 = INTEGER: 2
MFER> >>>>MFER> SNMPv2-MIB::sysServices.0 = INTEGER: 34
MFER> >>>>MFER> Error: OID not increasing: SNMPv2-MIB::sysS
>>>>MFER> management station to the agent 1 using the proxy. At the end of the
>>>>MFER> result i've got the follwing error:
>>>>MFER>
>>>>MFER> SNMPv2-MIB::sysLocation.0 = STRING: seoul
>>>>MFER> SNMPv2-MIB::
an "snmpwalk" from the
MFER> management station to the agent 1 using the proxy. At the end of the
MFER> result i've got the follwing error:
MFER>
MFER> SNMPv2-MIB::sysLocation.0 = STRING: seoul
MFER> SNMPv2-MIB::sysServices.0 = INTEGER: 2
MFER> SNMPv2-MIB::sysS
will eventually hit the same
node that caused the error and fall into a loop, hence the 'Error: OID not
increasing' message
Hope this helps
Andy
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MAUGER Fabien
ext ROSI/DPS
Sent: Friday,
s.0 = INTEGER: 2
SNMPv2-MIB::sysServices.0 = INTEGER: 34
Error: OID not increasing: SNMPv2-MIB::sysServices.0
>= SNMPv2-MIB::sysServices.0
my snmpwalk is construct as follow:
snmpwalk -v 3 -u "snmpV3_user_agent2" -A "my_pwd" -a MD5 -l
26 matches
Mail list logo
