Hello Dave,
Thanks for your quick reply.
If agent has to create a row based on the SET request, how can it
differentiate between a
->SET request which has been sent to modify the existing entry, but by
mistake the user has sent a request with invalid value for index
(Sending 1.1.1.1 instead of 1.1.1.2)
->SET request to create a new entry. (1.1.1.1)
Also, how can user be able to delete an existing conceptual row in the
table? (One possible way I can think of is to set the type of the
mapping in the table to invalid.)
Or is it because of the above problems which cannot be solved, the
RowStatus concept has been defined?
Thanks in Advance for your support,
Regards,
Mahesh.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Dave Shield
Sent: Thursday, March 27, 2008 3:04 PM
To: Mahesh Akula (WT01 - TES-Transport Infrastructure)
Cc: [email protected]
Subject: Re: IPNetToMediaTable
On 27/03/2008,<[EMAIL PROTECTED]> wrote:
> Is any one aware, how we can implement, adding a conceptual row
dynamically
> in IpNetToMediaTable.
In principle, simply issue a SET command containing the new values.
> I see that all the objects in this table are read-create, but I don't
see any object
> which is of type RowStatus....
> I am under impression that we need one object in a Table to be of type
RowStatus
> in order to allow the SNMP manager to create a row in a table
dynamically.
No - that's not correct.
RowStatus is the standard mechanism for controlling the
creation/deletion
of rows dynamically, but it's not essential. A given MIB table can use
a
different approach. [The replacement ipNetToPhysicalTable *does* use
a RowStatus object, but ipNetToMediaTable was defined much earlier,
before RowStatus really took off]
In the case of the ipNetToMediaTable, rows can be created by simply
issuing
a SET request, containing the desired Physical and IP addresses, and the
type of the entry (typically 'dynamic(3)')
Always assuming that the agent supports SET requests on this table.
> I need to implement this in a Sub Agent.
The Subagent<->master agent communication doesn't include support
for SET (or GET) requests from the subagent to the master agent.
You'll basically need to treat this as an external SNMP client
application
(i.e. equivalent to the 'snmpset' command) - which just happens to be
a subagent as well.
See the code for 'snmpset.c' for details.
Dave
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
