This is a discussion on Get Request on TimeSys linux distribution - SNMP ; This is a multi-part message in MIME format. --===============0143745820== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C78B1A.209F0909" This is a multi-part message in MIME format. ------_=_NextPart_001_01C78B1A.209F0909 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear Mr.Dave, Thanks for your reply, Here i have to give more ...
This is a multi-part message in MIME format.
--===============0143745820==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C78B1A.209F0909"
This is a multi-part message in MIME format.
------_=_NextPart_001_01C78B1A.209F0909
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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.=20
I have followed the same modification for access compatibility changes =
in snmpd.config in Timesys also like=20
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.=20
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).
=20
# 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 (root@localhost)
=20
# 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
=20
################################################## #######################=
##
# SECTION: Access Control Setup
#
# This section defines who is allowed to talk to your running
# snmp agent.
=20
# rocommunity: a SNMPv1/SNMPv2c read-only access community name
# arguments: community [default|hostname|network/bits] [oid]
=20
rocommunity public
=20
# rwcommunity: a SNMPv1/SNMPv2c read-write access community name
# arguments: community [default|hostname|network/bits] [oid]
=20
rwcommunity private
=20
################################################## #######################=
##
# SECTION: Agent Operating Mode
#
# This section defines how the agent will operate when it
# is running.
=20
# 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)
=20
master agentx
With thanks and Regards,
D.SenthilNathan
------_=_NextPart_001_01C78B1A.209F0909
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
charset=3Diso-8859-1">
6.5.7651.59">
Get Request on TimeSys linux distribution
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 (root@localhost)
# 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
------_=_NextPart_001_01C78B1A.209F0909--
--===============0143745820==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
-------------------------------------------------------------------------
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/
--===============0143745820==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders
--===============0143745820==--