public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS]  Re: SNMP lockup
Date: Sat, 09 May 2009 08:48:00 -0000	[thread overview]
Message-ID: <gu3g0c$e07$1@ger.gmane.org> (raw)
In-Reply-To: <4A04BD1C.7000207@mlbassoc.com>

On 2009-05-08, Gary Thomas <gary@mlbassoc.com> wrote:

>>> The problem occurs when cyg_snmp_get_if() is called with if_num <= 0.
[...]
>>> I'm surprised nobody else has run into this.  I'm told all our
>>> customers who have HP or Cisco SNMP managers have had to
>>> disable SNMP support in our products to keep them from locking
>>> up every few minutes.
>> 
>> I was just googling +'ifPhysAddress.0'
>> 
>> It seems you are not alone :-)
>> 
>> http://mtsc.moxa.com:8888/Software/DN/NPort/Firmware/NPort%205000/NPort%205600/ver3.2/VERSION.TXT

That's interesting -- I hadn't found that.  Since the bug was
in eCos-specific code, do we assume that Moxa is using eCos for
the NPort?

>> UCD-SNMP had a lot of holes. eCos UCD-SNMP implementation has
>> even more holes :-(

Um... I blame Dick Cheney and Karl Rove!

> Feel free to improve this

Workin' on it...

> - much of the networking code, including SNMP, is more than
> seven (7!) years old.  A lot has gone on in the world in that
> time...

What I'd like a pointer on is the interface numbering in SNMP
OIDs.  Are the interfaces supposed to be numbered 1..N with
interface 0 being non-existent?  Or are eCos interface numbers
off by one and they should really be 0,1 instead of 1,2? [I
tried looking through the OID/ASN.1 docs, but got lost rather
quickly.]

If SNMP interface numbers are supposed to start at #1, why do
HP and Cisco SNMP managers ask for attributes of interface #0?

I looked at network traces for one customer site using, I
believe, HP Insight. It does read the interface attributes for
interfaces 1 and 2.  I don't see it attempt to read attributes
for interface 3 (which doesn't exist). I do see it attempt to
read attributes for interface 0 (which also doesn't exist).

If interface numbers are supposed to start at #0, will
renumbering the interfaces at this point (after product has
been shipping for 7 years) cause more problems that it will
solve?

-- 
Grant



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2009-05-09  8:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 20:52 [ECOS] " Grant Edwards
2009-05-08 21:22 ` [ECOS] " Grant Edwards
2009-05-08 21:29   ` Grant Edwards
2009-05-08 21:35     ` Grant Edwards
2009-05-08 22:05     ` Grant Edwards
2009-05-08 22:10       ` Sergei Gavrikov
2009-05-08 22:38         ` Grant Edwards
2009-05-08 23:10           ` Sergei Gavrikov
2009-05-08 23:15             ` Gary Thomas
2009-05-08 23:44               ` Sergei Gavrikov
2009-05-09  8:48               ` Grant Edwards [this message]
2009-05-09  9:20                 ` Sergei Gavrikov
2009-05-09  9:47                   ` Grant Edwards
2009-05-09 10:28                     ` Grant Edwards
2009-05-09 12:38                       ` Sergei Gavrikov
2009-05-14  8:26                       ` [ECOS] " Danny Sade
2009-05-14 15:03                         ` [ECOS] " Grant Edwards
2009-05-14 19:50                         ` Grant Edwards
2009-05-08 22:11       ` Grant Edwards
2009-05-09  8:22       ` Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='gu3g0c$e07$1@ger.gmane.org' \
    --to=grante@visi.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).