Re: overwrite standard mib2/interfaces

On 18/03/2008, Masoud Fatollahy <masoud.fatollahy@t2data.se> wrote:
> what should vi change in our configuration below to allow cust1_grp and
> cust2_grp see our added mibs with context "my_context"?


> com2sec cust1_sec 192.168.55.0/24 public
> com2sec cust2_sec 192.168.56.0/24 public

Firstly, you need to use *different* community strings
for these two lines.

As it stands, the first directive says
"map a request coming in from the network 192.168.56.x
with the community 'public' to the internal name 'cust1_sec'"
and the second directive says
"map a request coming in from the network 192.168.56.x
with the community 'public' to the internal name 'cust2_sec'"

So if the agent receives a request from the network 192.168.56.x
with the community 'public' - what internal name should it
be mapped to???


But in answer to your question, try

com2sec -Cn my_context cust1_sec 192.168.55.0/24 public1
com2sec -Cn my_context cust2_sec 192.168.55.0/24 public2

And tweak the access lines:

> access cust1_grp "" any noauth exact cust1_v none none
> access cust2_grp "" any noauth exact cust2_v none none

to be

access cust1_grp "" any noauth prefix cust1_v none none
access cust2_grp "" any noauth prefix cust2_v none none

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/...net-snmp-users