Re: module ip-mib broken on CVS MAIN

2004-07-16 Thread OpenMacNews
On Wed, 14 Jul 2004 09:31:44 -0600, Bruce Shaw <[EMAIL PROTECTED]> said: Bruce> configure: error: mib module "ip-mib" requires module Bruce> "ip-mib/ipSystemStatsTable" but ip-mib/ipSystemStatsTable.h or Bruce> ip-mib/ipSystemStatsTable.c could not be found in Bruce> ./agent/mibgroup Fixed. verifie

Re: continued compile errors on OSX 10.3.4 w/ net-snmp-5.1.2.pre3

2004-07-16 Thread Wes Hardaker
> On Thu, 15 Jul 2004 15:27:51 -0700, OpenMacNews <[EMAIL PROTECTED]> said: OpenMacNews> re: bug report [ 967895 ] "5.1.1 compile error on macosx10.3.4", i noted that some fixes were tried w/ 512pre2. Unfortunately, to get those modules you want compiled and working we'll need someone willin

Re: SCO UNix

2004-07-16 Thread Wes Hardaker
> On Mon, 12 Jul 2004 17:04:07 -0400, "Srini Tipirneni" <[EMAIL PROTECTED]> said: Srini> is the agent supported on SCO UNIX? If you read our FAQ, it'll tell you that it isn't explicitly supported but it will help you figure out which pieces are and are not. -- Wes Hardaker Sparta

Re: AgentX configuration

2004-07-16 Thread Wes Hardaker
> On Tue, 13 Jul 2004 13:51:17 +0100, Dave Shield <[EMAIL PROTECTED]> said: Dave> init_snmp("snmpd:agentx") Dave> would readsnmp.conf Dave> snmpd.conf Dave> agentx.conf I like it. -- Wes Hardaker Sparta --- This SF.Net em

Re: module ip-mib broken on CVS MAIN

2004-07-16 Thread Wes Hardaker
> On Wed, 14 Jul 2004 09:31:44 -0600, Bruce Shaw <[EMAIL PROTECTED]> said: Bruce> configure: error: mib module "ip-mib" requires module Bruce> "ip-mib/ipSystemStatsTable" but ip-mib/ipSystemStatsTable.h or Bruce> ip-mib/ipSystemStatsTable.c could not be found in Bruce> ./agent/mibgroup Fixed.

Re: Make options

2004-07-16 Thread Wes Hardaker
> On Thu, 15 Jul 2004 12:31:10 +0200, "Willem Jan Withagen" <[EMAIL PROTECTED]> > said: ./configure --with-cflags="-W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts -Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wredundant-decls -Ws

Re: configure Problem on Linux

2004-07-16 Thread Wes Hardaker
> On Tue, 13 Jul 2004 07:30:41 -0500, Andy Smith <[EMAIL PROTECTED]> said: Andy> I have run into an error while configuring the main branch on Mandrake Andy> Linux 9.0. From config.log: Fixed earlier today. -- Wes Hardaker Sparta --- Thi

Re: Counter64 objects retrieval

2004-07-16 Thread Wes Hardaker
> On Wed, 14 Jul 2004 11:40:34 +0530, "Karthikeyan N" <[EMAIL PROTECTED]> said: Karthikeyan> Currently , I am trying to implement the counter64 Karthikeyan> objects in ifXTable ( example : ifHCInOctets). I Karthikeyan> generated the code in uce-snmp style and it generates the Karthikeyan> code

Re: Ipv6 route table

2004-07-16 Thread Wes Hardaker
> On Fri, 16 Jul 2004 17:46:30 +0700, Le Dinh An <[EMAIL PROTECTED]> said: Le> I'm having to implement this on Linux, but it looks vague to me. I Le> found this subject on the list archive, hoping some one out there Le> could give me some hints. First off, you definitely need to look into the

Re: variables in traps

2004-07-16 Thread Norio Nakamoto
One more thing. Can you tell me which RFC gives this idea or convention? On Fri, 16 Jul 2004 18:14:25 -0700 "David T. Perkins" <[EMAIL PROTECTED]> san wrote: > HI, > > Variables in notifications (TRAPv1, TRAPv2, INFORM) always have instance > sub-ids. If they are scalars, it's always 0. For col

Re: variables in traps

2004-07-16 Thread Norio Nakamoto
David, Thanks for such a quick answer. So you should treat the variables in both notifications and reqeust/ response with the same manner. Is that correct? Then the agent I mentioned seems right. Norio Nakamoto On Fri, 16 Jul 2004 18:14:25 -0700 "David T. Perkins" <[EMAIL PROTECTED]> san wrot

variables in traps

2004-07-16 Thread David T. Perkins
HI, Variables in notifications (TRAPv1, TRAPv2, INFORM) always have instance sub-ids. If they are scalars, it's always 0. For columnar, you have to look at the INDEX or AUGMENTS clause of the row definition. A well written DESCRIPTION clause will make it obvious which instance is returned. You NEV

Re[2]: Enterprise OID in generic traps

2004-07-16 Thread Norio Nakamoto
Andrew, David, Thanks for your answers. I read RFC 1215 and it does mention to use the value of sysObjectID istead of 'snmp(1.3.6.1.2.1.11)' for generic traps. And I also checked and found out some agents do set their own enterprise oid but it seems that it should be the value of sysObjectID as

Re: Enterprise OID in generic traps

2004-07-16 Thread David T. Perkins
HI, This is a frequently asked question, and I believe is is well covered with the correct answer in the FAQ for the SNMP News group (comp.protocols.snmp), and the book "Understanding SNMP MIBs". For the so called "generic traps" (which there are EXACTLY 6), the value returned in the enterprise f

Re: Enterprise OID in generic traps

2004-07-16 Thread Andrew Hood
Norio Nakamoto wrote: Sorry if this sounds a obvious question but what should be set in enterpise OID in generic traps (i.e. traps with generic type other than '6')? It should be 'snmp(1.3.6.1.2.1.11)' or the same OID returned by sysObjectID or it may be agent dependent? It can be any OID. Many ag

Enterprise OID in generic traps

2004-07-16 Thread Norio Nakamoto
Sorry if this sounds a obvious question but what should be set in enterpise OID in generic traps (i.e. traps with generic type other than '6')? It should be 'snmp(1.3.6.1.2.1.11)' or the same OID returned by sysObjectID or it may be agent dependent? Norio Nakammoto

RE: Ipv6 route table

2004-07-16 Thread Le Dinh An
Hi all, I'm having to implement this on Linux, but it looks vague to me. I found this subject on the list archive, hoping some one out there could give me some hints. I see that some kind of linked list of struct should be generated from the contents of /proc/net/ipv6_route. But then how is thi

Re: Excluded view with V3

2004-07-16 Thread Dave Shield
> What is the corresponding mechanism to restrict sub-tree access for V3? > > In v1/v2: > view all excluded .1.3.6.1.4.1.469.1000.2.11.1.2 80 > > In v3? view all excluded .1.3.6.1.4.1.469.1000.2.11.1.2 80 Defining a view is completely independent of the SNMP version. Defining