A god book for this is "Understanding SNMP MIBs" ISBN 0-13-437708-7
I personally found a lot of explanations and the nested table example.
--- On Mon, 3/8/10, Prakash wrote:
> From: Prakash
> Subject: RE: Defining MIB
> To: "'Robert Story'"
>
Can you please give an example...
-Original Message-
From: Robert Story [mailto:[email protected]]
Sent: Monday, March 08, 2010 8:57 PM
To: PrakashRaju Meka
Cc: [email protected]; 'Fulko Hew'
Subject: Re: Defining MIB
On Mon, 8 Mar 2010 16:54:01 +05
On Mon, 8 Mar 2010 16:54:01 +0530 Prakash wrote:
P> Is SNMP support nested tables?
No, but you can use the index of one table as the first of 2 or more indexes
in the second table, which sort of approximates nested tables.
--
Thank you to all,
When we use OBJECT-GROUP ?.
Is SNMP support nested tables?
From: Fulko Hew [mailto:[email protected]]
Sent: Friday, March 05, 2010 7:42 PM
To: [email protected]
Subject: Re: Defining MIB
On Fri, Mar 5, 2010 at 8:58 AM, Dave Shield
wrote
On Fri, Mar 5, 2010 at 8:58 AM, Dave Shield wrote:
> On 5 March 2010 13:42, Fulko Hew wrote:
> > The closest merge to your original request would be the following
> >
> >
> >abc OBJECT IDENTIFIER ::= { application 1 }
> >xyz OBJECT IDENTIFIER ::= { application 2 }
On 5 March 2010 13:42, Fulko Hew wrote:
> The closest merge to your original request would be the following
>
>
> abc OBJECT IDENTIFIER ::= { application 1 }
> xyz OBJECT IDENTIFIER ::= { application 2 }
>
> noOfMessages OBJECT-TYPE
> SYNTAX
On Fri, Mar 5, 2010 at 7:51 AM, Prakash wrote:
>
> Thanks Dave,
>
> I have two mibs as below and I want to merge them into a single MIB.
>
According to your original definitions,
> ABC-MIB :=
>
>abc OBJECT IDENTIFIER ::= { application 1 }
>
... snip ...
> XYZ-MIB :=
>
>
On 5 March 2010 12:51, Prakash wrote:
> I have two mibs as below and I want to merge them into a single MIB.
>
> ABC-MIB :=
> =
>
> abc OBJECT IDENTIFIER
> ::= { application 1 }
> XYZ-MIB :=
>
Thanks Dave,
I have two mibs as below and I want to merge them into a single MIB.
ABC-MIB :=
=
.
.
abc OBJECT IDENTIFIER
::= { application 1 }
noOfMessagesOB
On 15 February 2010 11:11, Prakash wrote:
> But I want to access the object as
> "privete(4).enterprise(1).abc(16142).newyork(3).machine(1).app(id).noOfMessa
> gesPending(1)" not like
> "privete(4).enterprise(1).abc(16142).newyork(3).machine(1).noOfMessagesPendi
> ng(1). app(id)" leaf node should
1).
regards
Prakash
-Original Message-
From: [email protected] [mailto:[email protected]] On
Behalf Of Dave Shield
Sent: Thursday, February 11, 2010 4:27 PM
To: PrakashRaju Meka
Cc: [email protected]
Subject: Re: Defining MIB
On 11 February 2010 10:53, Prakash
On 11 February 2010 10:53, Prakash wrote:
> There are many instances of apps and each instance have unique id which is
> dynamically created
> question Is how to create dynamic oid's instead of defining statically in a
> MIB.
Use a MIB table.
Presumably the information held about each app is cons
[email protected]
Subject: Re: Defining MIB
On 10 February 2010 09:58, Prakash wrote:
> Hi Dave,
Please address queries to the list as a whole - not to me personally.
I am *not* the sole support for this project (though it sometimes
feels like it!)
> How to define a MIB for the following structur
On 10 February 2010 09:58, Prakash wrote:
> Hi Dave,
Please address queries to the list as a whole - not to me personally.
I am *not* the sole support for this project (though it sometimes
feels like it!)
> How to define a MIB for the following structure.
What do you have at the moment?
> …p
Hi Dave,
How to define a MIB for the following structure.
.privete(4).enterprise(1).abc(16142).newyork(3).machine(1).app(4).noOfMessag
esPending;
.privete(4).enterprise(1).abc(16142).newyork(3).machine(1).app(4).noOfMessag
esSent;
.privete(4).enterprise(1).abc(16142).newyork(3).machine(1).app(3)
15 matches
Mail list logo
