Re: I have implemted a Vacm table and register to my Subagent(agentx) ::Implemented a snmpcommunity-Table and snmptargetTable but Agentis taking snmpcommunity string form snmpd.conf

Hi Mike,
    Thank's for ur help.
        I have attached the snmpd.conf file. In the snmpd.conf file I am
using "public" as community string , so my agent and subagent will start
with that snmpd.conf,   (  by using ::  snmpd -Lo -f -c /path/snmpd.conf
).    Later I will start my subagent ( ./subagent1 ) .
      After ...some time..i will get a callback call which was implemented
to get some VACM access related objects , eg:
        communitystring                 access    subOID   Max
                private_vlindia           include      .1.3.6        80
                private_vlus                exclude     .1.3.6      80

       So I have implemented snmpcommunitytabel and VacmaccessTable,
TargetAddexttable etc..(access realated tables) and able to register with
Subagent  .  After that I did snmpwalk to snmpcommunityTable and it gives
list of objects  "private_vlindia and private_vlus "

            I tried:
                            [manu@localhost ~]$ snmpwalk -v2c -On -c public
localhost SNMP-COMMUNITY-MIB::snmpCommunityTable
        .1.3.6.1.6.3.18.1.1.1.2.64.83.84.66.99.111.110.102.105.103.95.48 =
STRING: "private_vlindia"

.1.3.6.1.6.3.18.1.1.1.2.64.83.84.66.99.111.110.102.105.103.95.49 = STRING:
"private_vlus"

           I tried:     snmpwalk -v2c -On -c public localhost
SNMP-TARGET-MIB::snmpTargetAddrTable
                           .1.3.6.1.6.3.12.1.2 = No Such Object available on
this agent at this OID

          -v2c -On -c public localhost
SNMP-VIEW-BASED-ACM-MIB::vacmAccessTable  //These deatils are of snmpd.conf
file , My updated details are reflecting in this table it always gives the
snmpd.conf access deatils only

.1.3.6.1.6.3.16.1.4.1.4.9.77.121.82.87.71.114.111.117.112.0.0.1 = INTEGER:
exact(1)

.1.3.6.1.6.3.16.1.4.1.5.9.77.121.82.87.71.114.111.117.112.0.0.1 = STRING:
roview

            Then I try snmpwalk using private_vlInda it says Timeout
response (eg: snmpwalk -v2c  -c private_vlIndia  localhost xxx.OID resutl ::
TImeout responce)

                  snmpwalk -v2c  -c private_vlIndia  localhost xxx.OID
resutl
                   result :: TImeout responce
                 snmpwalk -v2c  -c private_vlIndia  localhost xxx.OID resutl

           result :: TImeout responce


On Tue, Sep 23, 2008 at 10:23 AM, Mike Ayers <[email protected]> wrote:

> > From: kumar undurthi [mailto:[email protected]]
> > Sent: Monday, September 22, 2008 8:48 PM
>
> >      I have a problem in implementing snmpcommunity and
> > snmptargetTable etc (access realted tables).
>
>         "Implement"?  These tables are already implemented for the agent.
>  If you are attempting to implement your own version, you are doomed.  If
> you are attempting to configure the existing tables, read on...
>
> > My requirement
> > is I have to implement those table so the while run time ,  I
> > can configure the snmp-agent by creating a new rows for the
> > access controling Tables (snmpCommuntiyTable,
> > snmpTargetAddTable ,vacm etc )
>
>         This is part of the specification for these tables, and is an
> achievable goal.  You will, however, need to understand the interactions
> between the various tables.
>
> >    so by default the snmpd will take a access configuration
> > form snmpd.conf file , so how to reset those snmpd.conf data
> > by using snmpcommunitytable etc..,  how to replace those
> > snmpd.conf  or how to use the snmpcommunitytable,
> > snmpaddressTable , vacm, etc. to have access control along
> > with or without snmpd.conf access support.
>
>         This is part of normal operations.  Most likely you are making
> common mistakes, but we will need details.
>
> >    Please give me some idea to solve this problem.
>
>         Please post your snmpd.conf and all the commands you execute trying
> to configure it, up to the first command that, in your view, "fails".
>
>
>        Thanks,
>
> Mike
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

 
###########################################################################
#
# snmpd.conf
#
#   - created by the snmpconf configuration program
#
###########################################################################

#sec.name source community

#       sec.name  source           community

com2sec local default public

group MyRWGroup	v1         local
group MyRWGroup	v2c        local
group MyRWGroup	usm         local

# Third, create a view for us to let the groups have rights to:

#           incl/excl subtree                          mask
view all    included  .1                               80
view roview    included  .1                               80

access MyRWGroup ""      any       noauth    exact  roview    all   all



###########################################################################
# SECTION: System Information Setup
#
#   This section defines some of the information reported in
#   the "system" mib group in the mibII tree.

# syslocation: The [typically physical] location of the system.
#   Note that setting this value here means that when trying to
#   perform an snmp SET operation to the sysLocation.0 variable will make
#   the agent return the "notWritable" error code.  IE, including
#   this token in the snmpd.conf file will disable write access to
#   the variable.
#   arguments:  location_string

 # syslocation  

# syscontact: The contact information for the administrator
#   Note that setting this value here means that when trying to
#   perform an snmp SET operation to the sysContact.0 variable will make
#   the agent return the "notWritable" error code.  IE, including
#   this token in the snmpd.conf file will disable write access to
#   the variable.
#   arguments:  contact_string

 # syscontact  [email protected]

# sysservices: The proper value for the sysServices object.
#   arguments:  sysservices_number

#sysservices 79

master agentx
agentXSocket   tcp:localhost:705