> From: Cardoza, Eric [mailto:[EMAIL PROTECTED]
> Sent: Saturday, November 15, 2008 9:38 PM
> From: Cardoza, Eric D.
> Sent: Friday, November 14, 2008 3:03 PM
Resending a message that has not been answered is OK, but it's best to
wait until after the weekend, as a good portion of everyday participants have
the weekend off.
> I apologize for my ignorance of community support list usage.
> I am an old IBMer and not familiar with the proper open
> source community behavior.
It's all good. The general principole is to keep list related
discussions as list discussions. This keeps the information available in the
archives for folk to find later, and also keeps an enviroment where everyone is
welcome to jump into the discussion, which is generally a good thing. You
should only call p;eople out by name when asking a question to them directly,
as I will do now to you.
> Also, I notice as I read the postings on the list that my
> posting is the only one that does not have a Topic heading.
> Please let me know how I can establish a Topic for my posting.
I'm not sure. Are you talking about a web interface to the archives
here?
> Thank you for your help and patience. Here is the
> information you requested.
>
> OS:
> Linux 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 2006 i686
> i686 i386
> GNU/Linux
>
> NET-SNMP build from Red Hat Network:
> net-snmp-devel-5.1.2-13.el4_7.2
> net-snmp-libs-5.1.2-13.el4_7.2
> net-snmp-utils-5.1.2-13.el4_7.2
> net-snmp-5.1.2-13.el4_7.2
>
> I did not explicitly set the engineID. I had read in the
> Net-SNMP docs
Hmmm - the kernel isn't the most recent, but should be good. The
package is darn old, though - we're on 5.4.2 now, and the revs don't come
quickly - I'd estimate you have a 4 or 5 year old package. But even that
shouldn't have this problem.
You may want to do a `yum upgrade -y` on that system, if you are
comfortable doing so.
If someone on the list could point us to thye most recent RPMs, please?
Once you have upgraded or not, as befits, please post the following:
1) The snmpd log (tip: use the -Le flag and cut and paste from the
console, or use `-Le 2>&1 | tee snmpd.log` to save it to a file while keeping
it on the console.
2) The command and response for a successful get or getnext.
3) The command and response for a failing get or getnext.
4) The text of snmpd.conf
I need a lot of info because I have no idea why this may happen.
Thanks,
Mike
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
