Title: RE: Problem with mib2C
Hi Alex,
Thanks for your reply.
I did use the build.bat to compile the main package and it builds the Main Package successfully. After running the build.bat when I run the nmakeperl I get the following problem.
Thanks
- Akshatha
-Original Message-
On Thu, 14 Apr 2005 19:13:46 +0100 Dave wrote:
DS> > Permanent is used to indicate rows which can not be deleted
DS> > in contrast nonVolatile rows can be deleted.
DS>
DS> Of course! That was the thing I was missing.
DS> Presumably they should both retain any changes
DS> across an agent rest
On Thu, 14 Apr 2005 17:01:27 +0100 Dave wrote:
DS> On Thu, 2005-04-14 at 16:11, Robert Story wrote:
DS> > The question is, what should the default behaviour be?
DS> > Always delay the probe ... [or] allow a failed probe to
DS> > successfully return, and set up to retry the probe when needed.
DS>
D
On Thu, 14 Apr 2005 09:53:37 -0700 (PDT) David wrote:
DTP> I hope you allow the engineID to be specified in the API.
Yes, you can set a flag to not probe, and set the engineID directly in the
session structure.
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
un
> Permanent is used to indicate rows which can not be deleted
> in contrast nonVolatile rows can be deleted.
Of course! That was the thing I was missing.
Presumably they should both retain any changes
across an agent restart?
I don't suppose there's a style (or a need?)
for a storage type o
HI,
I hope you allow the engineID to be specified in the API.
Regards,
/david t. perkins
On Thu, 14 Apr 2005, Robert Story wrote:
> In order to fix the problem where an inform session fails to open at startup,
> I'm integrating a patch (submitted a few years ago) to delay the engineID
> probe
Permanent is used to indicate rows which can not be delete, but still have
some settable properties. something like a hardware port should probably be
permanent. in contrast nonVolatile rows can be deleted.
Mark.
- Original Message -
From: "Dave Shield" <[EMAIL PROTECTED]>
To:
Sent: Th
permanent is read-only, nonVolatile is read-write (and persist).
Dave Shield wrote:
Question:
What is the difference between 'nonVolatile(3)'
and 'permanent(4)' in the StorageType syntax ?
Dave
---
SF email is sponsored by - The IT Product G
Question:
What is the difference between 'nonVolatile(3)'
and 'permanent(4)' in the StorageType syntax ?
Dave
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Di
Hi.
[EMAIL PROTECTED] wrote:
As directed by the message, I installed the perl module
"ActivePerl-5.8.6.811-MSWin32-x86-122208" and then followed the
instructions given in the README file. When I tried to run the nmakeperl
I always keep getting the following errors:
NMAKE : fatal error U1077: 'c
On Thu, 2005-04-14 at 16:11, Robert Story wrote:
> The question is, what should the default behaviour be?
> Always delay the probe ... [or] allow a failed probe to
> successfully return, and set up to retry the probe when needed.
Either of those two would be acceptable.
At the moment, the library
In order to fix the problem where an inform session fails to open at startup,
I'm integrating a patch (submitted a few years ago) to delay the engineID probe
until it is needed.
The question is, what should the default behaviour be? Always delay the probe
(any time snmp_open is called for a v3 ses
Hello
I have installed net-snmp-5.1.2 and trying to make use of
mib2c tool on windows 2K. But when I run mib2c in the command line, I get the
following message -
"ERROR: You don"t have the SNMP perl module installed. Please obtain this by getting the latest source release of the ne
On Thu, 14 Apr 2005 09:32:05 +0100 Dave wrote:
DS> On Wed, 2005-04-13 at 18:59, Shobana Sampath wrote:
DS> > > > In the netsnmp_pdu data structure, what is the
DS> > > > field that I can use in snmp v2c to set the
DS> > > > sender's address in outgoing SNMP packets.
DS>
DS> In this particular cas
On Thu, 14 Apr 2005 09:36:28 +0100 Dave wrote:
DS> We could switch to reporting everything as
DS> Unsigned32 rather than Gauge32, I suppose.
DS> But it hardly seems worth it.
Of course, the right thing to do would be to check and see if the MIB was
loaded and we could get the intent from there to
On Thu, 2005-04-14 at 13:37, [EMAIL PROTECTED] wrote:
> Again and again, I have to fill in someTable_get_first_data_point()
> and someTable_get_next_data_point() and -- always afraid of duplicate
> code -- I don't want similar logic in both.
Always wise.
> I can almost always do something like:
As I'm writing a new MIB handler by filling in mib2c-generated code, I'm
reminded again how elegant Net-SNMP can be. I imagine part of that is a
reflection of the simplicity of SNMP itself but the Net-SNMP crew needs to take
credit, too. And I want to thank you all.
One of the best illustrati
On Thu, 2005-04-14 at 09:56, Kelvin Moss wrote:
> I agree with what you are saying but there is a slight
> difference in Gauge32 and Unsigned32
There is a slight difference in the semantics of the
*behaviour* of objects defined using these two types, yes.
But the *syntax* of the two types is id
Hi Dave,
Thanks for the reply. I agree with what you are saying but there is a slight difference in Gauge32 and Unsigned32, which was misleading at least to me.
RFC 1155
3.2.3.3. Counter This application-wide type represents a non-negative integer which monotonically increases until it r
On Thu, 2005-04-14 at 08:10, Kelvin Moss wrote:
> I have used Unsigned32 counter type in my mib
> When I later retrive it using snmpwalk/snmpget,
> it gets reported as Gauge32
> What is the reason for this ?
Because the two types are exactly the same thing.
>From RFC 2578 (defining SMIv2):
Gauge3
On Wed, 2005-04-13 at 18:59, Shobana Sampath wrote:
> > > In the netsnmp_pdu data structure, what is the
> > > field that I can use in snmp v2c to set the
> > > sender's address in outgoing SNMP packets.
Oops.
I've just spotted that you're talking about SNMP
*trap* packets, rather than more gener
Hi all,
I have used Unsigned32 counter type in my mib --
xxxEvents OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "some events" DEFVAL { 0 } ::= { myMIB 1 }
When I later retrive it using snmpwalk/snmpget, it gets reported as Ga
22 matches
Mail list logo
