Re: overwrite standard mib2/interfaces
This is a discussion on Re: overwrite standard mib2/interfaces within the SNMP Users forums, part of the Networking and Network Related category; --===============0758319974== Content-Type: multipart/alternative; boundary="_0319-1055-28-PART-BREAK" --_0319-1055-28-PART-BREAK Content-Type: ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
03-19-2008
|
|||
|
|||
Re: overwrite standard mib2/interfaces
--===============0758319974==
Content-Type: multipart/alternative; boundary="_0319-1055-28-PART-BREAK" --_0319-1055-28-PART-BREAK Content-Type: text/plain; charset="us-ascii" Thanks Dave, so if i used different cummonity name I will give read access to both default context "" and "my_context" to v1 and v2c clients. Regards and thanks again for your time, /Masoud -----Original Message----- From: "Dave Shield" <D.T.Shield@liverpool.ac.uk> To: "Masoud Fatollahy" <masoud.fatollahy@t2data.se> Cc: "net-snmp-users@lists.sourceforge.net" <net-snmp-users@lists.sourceforge.net> Date: Wed, 19 Mar 2008 09:36:37 +0000 Subject: 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 --_0319-1055-28-PART-BREAK Content-Type: text/html; charset="us-ascii" <HTML> <HEAD> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <STYLE title="table borders">.htmtableborders, .htmtableborders td, ..htmtableborders th {border : 1px dashed lightgrey ! important;} </STYLE> <STYLE type=text/css>html, body { border: 0px; } span.macro, span.macro ul, span.macro div, span.macro p {background : #CCCCCC;} </STYLE> <STYLE type=text/css> p{margin-bottom: 0.15em;margin-top: 0.15em;}body{font-family:tahoma;font-size:10pt;}; </STYLE> </HEAD> <BODY> <FONT style="FONT-SIZE: 10pt; FONT-FAMILY: tahoma"> <DIV>Thanks Dave,</DIV> <DIV> </DIV> <DIV>so if i used different cummonity name I will give read access to both default context "" and "my_context" to v1 and v2c clients.</DIV> <DIV> </DIV> <DIV>Regards and thanks again for your time,</DIV> <DIV> </DIV> <DIV>/Masoud<BR> </DIV></FONT><BR> <BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> -----Original Message-----<BR>From: "Dave Shield" <D.T.Shield@liverpool.ac.uk><BR>To: "Masoud Fatollahy" <masoud.fatollahy@t2data.se><BR>Cc: "net-snmp-users@lists.sourceforge.net" <net-snmp-users@lists.sourceforge.net><BR>Date: Wed, 19 Mar 2008 09:36:37 +0000<BR>Subject: Re: overwrite standard mib2/interfaces<BR><BR> <DIV style="FONT-FAMILY: monospace, courier new, courier">On 18/03/2008, Masoud Fatollahy <masoud.fatollahy@t2data.se> wrote:<BR>> what should vi change in our configuration below to allow cust1_grp and<BR>> cust2_grp see our added mibs with context "my_context"?<BR><BR> <BR>> com2sec cust1_sec 192.168.55.0/24 public<BR>> com2sec cust2_sec 192.168.56.0/24 public<BR><BR>Firstly, you need to use *different* community strings<BR>for these two lines.<BR><BR>As it stands, the first directive says<BR> "map a request coming in from the network 192.168.56.x<BR> with the community 'public' to the internal name 'cust1_sec'"<BR>and the second directive says<BR> "map a request coming in from the network 192.168.56.x<BR> with the community 'public' to the internal name 'cust2_sec'"<BR><BR>So if the agent receives a request from the network 192.168.56.x<BR> with the community 'public' - what internal name should it<BR> be mapped to???<BR><BR> <BR>But in answer to your question, try<BR><BR> com2sec -Cn my_context cust1_sec 192.168.55.0/24 public1<BR> com2sec -Cn my_context cust2_sec 192.168.55.0/24 public2<BR><BR>And tweak the access lines:<BR><BR>> access cust1_grp "" any noauth exact cust1_v none none<BR>> access cust2_grp "" any noauth exact cust2_v none none<BR> <BR>to be<BR><BR> access cust1_grp "" any noauth prefix cust1_v none none<BR> access cust2_grp "" any noauth prefix cust2_v none none<BR><BR> Dave<BR></DIV></BLOCKQUOTE></BODY> </HTML> --_0319-1055-28-PART-BREAK-- --===============0758319974== 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: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ --===============0758319974== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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 --===============0758319974==-- 
|
Linear Mode
