Dave,
I am adding the new oids into the existed MIB file. That file uses the SMI
syntax, so I must folllow the rule. :( Thanks.
On 6/16/07, Dave Shield <[EMAIL PROTECTED]> wrote:
On 15/06/07, Aileen Han <[EMAIL PROTECTED]> wrote:
> (sorry, I just find I must use SMI syntax, not SMI-II syntx)
Hi all,
I have a trap callback function that checks the trap name against a list
of predefined names and resend the traps to other hosts if the trap name
matches a name in the list. This seems to work properly and I receive
the forwarded traps on the received hosts with the correct trap names
and
forgot to attach the files . here they are
Need Help <[EMAIL PROTECTED]> wrote: Sorry about flip flopping with this topic,
but it turns out this is still a problem for me. I forgot to remove the ".o"
previously created so that is why I did not see the warnings anymore when I
recomp
Sorry about flip flopping with this topic, but it turns out this is still a
problem for me. I forgot to remove the ".o" previously created so that is why
I did not see the warnings anymore when I recompiled.When I remove the
subagent ".o" file and recompile, the warnings are seen everytime.
What do you think about the following snmpwalk output?
Need Help <[EMAIL PROTECTED]> wrote:Here is the code I currently added in the
Table_object_lookup() routine:
if (MFD_SUCCESS != rc)
netsnmp_request_set_error_all(requests, rc);
else {
rc = ocStbHostAnalogVideoTable_r
Ok, I moved the "ocStbHostAVInterfaceTable_subagent.c" and
"ocStbHostAVInterfaceTable_subagent.o" lines to be the last ".o" and ".c" files
listed in the Makefile and the warning has gone away.
I guess I had these files out of order originally.
Need Help <[EMAIL PROTECTED]> wrote:
I create
On Fri, 15 Jun 2007 10:36:59 +0100 Dave wrote:
DS> On 14/06/07, Need Help <[EMAIL PROTECTED]> wrote:
DS> >for(req=requests; req; req = requests->next)
DS>
DS> If you've got more than two varbind in the same request,
DS> that will go into an infinite loop.
Whoops! Good catch..
DS> Tho
On Fri, 15 Jun 2007 10:21:58 +0100 Dave wrote:
DS> So what you are proposing is effectively something like:
DS>
DS> svn move agent/mibgroup/hardware agent/mibgroup/data_access
DS> (plus various similar moves, and consequent tweaking of related code)
DS>
DS> Correct?
Yep.
DS> What so
I created "ocStbHostAVInterfaceTable_subagent.c" using the mib2c.mfd.conf.
When I tried compiling it, I got the following warning as well:
ocStbHostAVInterfaceTable_subagent.c:128: warning: implicit declaration of
function `netsnmp_enable_subagent'
My "net-snmp/include/net-snmp/agent/net-snmp-
On 15/06/07, Aileen Han <[EMAIL PROTECTED]> wrote:
> (sorry, I just find I must use SMI syntax, not SMI-II syntx)
Why?
SMIv1 is obsolete, and SMIv2 has been the accepted standard for
many years. There is no good reason to define MIBs using SMIv1
syntax any more - even if you'll be using SNMPv1 t
On 15/06/07, Need Help <[EMAIL PROTECTED]> wrote:
> I added the following line to the "snmp.conf" file:
>
> mibs +OC-STB-HOST-MIB
>
> When I issue a "snmpwalk" command in a Root Shell Linux window the results
> are displayed with descriptive field names (instead of OIDs only). I guess
> the s
Vinh,
Thanks for your response...
I have a table which should include SSH client public keys such as
keyIndex(INTEGER), keyType(INTEGER), keySize(INTEGER), keyAcceptFrom(OCET
STRING), keyComments(OCET STRING). Firstly, the table have no any data.
Then I hope the user can add a row, then input t
Due to the fact that I'm not going to be touching a keyboard much
today. I'll publish it on Monday instead.
--
Wes Hardaker
Sparta, Inc.
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE ver
I added the following line to the "snmp.conf" file:
mibs +OC-STB-HOST-MIB
When I issue a "snmpwalk" command in a Root Shell Linux window the results are
displayed with descriptive field names (instead of OIDs only). I guess the
snmp "client" here is the "snmpwalk" code which knows to look
Hello,
I am a newbie. Hope get your help.
I want to implement a dynamic table, which can insert and delete the row of
the table.
After I investigate and search the net , I still can't find an answer about
how to operate the table with ROWSTATUS rows. It really made me desperate.:(
Would you ple
Wes Hardaker wrote:
> It bit me again today, but because our make test depends on perl stuff
> and the perl stuff links against libraries elsewhere, then a "make
> install" before "make test" may be necessary to ensure the perl
> modules can be properly loaded.
>
> This may be solvable using env v
On fre, 2007-06-15 at 10:31 +0100, Dave Shield wrote:
> On 15/06/07, Magnus Fromreide <[EMAIL PROTECTED]> wrote:
> > > Why did you choose to use the iterator helper?
> >
> > I managed to wrap my mind around that helper.
>
> > > One of table_data, table_tdata or even (shudder!) MfD
> >
> > Basica
On 14/06/07, Need Help <[EMAIL PROTECTED]> wrote:
>for(req=requests; req; req = requests->next)
If you've got more than two varbind in the same request,
that will go into an infinite loop.
Try
for (req=requests; req; req=req->next)
Though I'm not convinced that you should be se
On 15/06/07, Magnus Fromreide <[EMAIL PROTECTED]> wrote:
> > Why did you choose to use the iterator helper?
>
> I managed to wrap my mind around that helper.
> > One of table_data, table_tdata or even (shudder!) MfD
>
> Basically the problem is that I don't understand them enough to do what
> I
On 14/06/07, Need Help <[EMAIL PROTECTED]> wrote:
> I thought a MIB text file was not "required" at all (other than to generate
> code),
Correct.
> however, if you wanted an agent to display the results of a SNMP request
The agent doesn't display results.
The *client* displays results (and so ne
On tor, 2007-06-14 at 17:05 +0100, Dave Shield wrote:
> On 10/06/07, Magnus Fromreide <[EMAIL PROTECTED]> wrote:
> > Could someone please comment on wther these changes are useful?
>
> I haven't had the chance to look at the proposed code changes,
> but the basic idea feels definitely worthwhile.
On 14/06/07, Robert Story <[EMAIL PROTECTED]> wrote:
> DS> That sounds suspiciously like the idea of the 'hardware' directory in the
> DS> first place.
> DS> How does your proposed "data_access" directory differ from this idea?
>
> By not being specific to hardware. eg. if-mib, hrSW*, etc...
F
22 matches
Mail list logo
