Dear Mr.Dave,
Thanks for your reply,
Here i have to give more information
I have been implementing the snmp agent using net-snmp 5.3.1 for my product.
I have created agent which get the data from external sub modules not its own.
Then, regarding mib2c,I have used the iterator config for code conversion.I
have implemented the agent and simulated with various linux distributions like
Fedora and Suse 10.1 distributions.
I have made Get and Set request on my Mib Tables ,it was worked fine.
I have tried the same code base to Timesys linux with ppc440 as target system.
I have followed the same modification for access compatibility changes in
snmpd.config in Timesys also like
rocommunity public
rwcommunity private
master agentx
Now , we trid for the Get and Get-next request we got Request time out error.
We observed that,in Timesys distribution , the net-snmp version is 5.1.1 and I
used 5.3.1.
Is this reason for this. for your reference,I have to give that snmpd config.
# Please see /usr/share/doc/packages/net-snmp/EXAMPLE.conf for a
# more complete example and snmpd.conf(5).
#
# Writing is disabled by default for security reasons. If you'd like
# to enable it uncomment the rwcommunity line and change the community
# name to something nominally secure (keeping in mind that this is
# transmitted in clear text).
# Please see /usr/share/doc/packages/net-snmp/EXAMPLE.conf for a
# more complete example and snmpd.conf(5).
#
# Writing is disabled by default for security reasons. If you'd like
# to enable it uncomment the rwcommunity line and change the community
# name to something nominally secure (keeping in mind that this is
# transmitted in clear text).
# don't use ' < > in strings for syslocation or syscontact
# Note that if you define the following here you won't be able to change
# them with snmpset
syslocation Server Room
syscontact Sysadmin ([EMAIL PROTECTED])
# These really aren't meant for production use. They include all MIBS
# and can use considerable resources. See snmpd.conf(5) for information
# on setting up groups and limiting MIBS.
rocommunity public 127.0.0.1
# rwcommunity mysecret 127.0.0.1
###########################################################################
# SECTION: Access Control Setup
#
# This section defines who is allowed to talk to your running
# snmp agent.
# rocommunity: a SNMPv1/SNMPv2c read-only access community name
# arguments: community [default|hostname|network/bits] [oid]
rocommunity public
# rwcommunity: a SNMPv1/SNMPv2c read-write access community name
# arguments: community [default|hostname|network/bits] [oid]
rwcommunity private
###########################################################################
# SECTION: Agent Operating Mode
#
# This section defines how the agent will operate when it
# is running.
# master: Should the agent operate as a master agent or not.
# Currently, the only supported master agent type for this token
# is "agentx".
#
# arguments: (on|yes|agentx|all|off|no)
master agentx
With thanks and Regards,
D.SenthilNathan
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
