<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Thanks, somehow I missed that.  Thanks again!<br><br><br></div><div><br>On Feb 11, 2015, at 3:33 AM, Dominik Pawlak <<a href="mailto:dominik_pawlak@yahoo.co.uk">dominik_pawlak@yahoo.co.uk</a>> wrote:<br><br></div><blockquote type="cite"><div>
  
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  
  
    Hello Jim,<br>
    <br>
    snmp application has changed between 17.1 (snmp v4.25.1) and 17.4
    (snmp v5.1.1). According to docs the address should look like:<br>
    <br>
    "Addr is the address in the transport domain, either an {IpAddr,
    IpPort} tuple or a traditional SNMP integer list containing port
    number. IpAddr is either a regular Erlang/OTP ip_address() or a
    traditional SNMP integer list not containing port number, and IpPort
    is an integer.<br>
    <br>
    ip_address() = ip4_address() | ip6_address()<br>
    ip4_address() = {0..255, 0..255, 0..255, 0..255}"<br>
    <br>
    I always used [127,0,0,1] or {127,0,0,1} and never had any problem
    with it, I have never tried with "127.0.0.1".<br>
    <br>
    Best<br>
    Dominik<br>
    <br>
    <div class="moz-cite-prefix">On 11.02.2015 05:31, jim rosenblum
      wrote:<br>
    </div>
    <blockquote cite="mid:CANnHf0NF2fYVBeBDsfsKjjy3j7JZU94XZGpNwULRdMrOp4P8bw@mail.gmail.com" type="cite">
      <div dir="ltr">More information: 
        <div><br>
        </div>
        <div>on 17.4 CentOS release 5.5 -- used to work before I
          upgraded from 17.1  </div>
        <div>> snmpm:register_agent(snmp_manager,"Hope", [{engine_id,
          "mgrEngine"},{community,"CLSENTRY"},{address,
          "10.7.42.11"},{port,161},
          {tdomain,transportDomainUdpIpv4},{sec_level,
          noAuthNoPriv},{sec_name, "initial"},{version,
          v2},{timeout,1000}]).</div>
        <div>> ok</div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div>on 17.1 CentOS release 6.2</div>
        <div>
          <div>snmpm:register_agent(snmp_manager,"Hope", [{engine_id,
            "mgrEngine"},{community,"CLSENTRY"},{address,
            "10.7.42.11"},{port,161},
            {tdomain,transportDomainUdpIpv4},{sec_level,
            noAuthNoPriv},{sec_name, "initial"},{version,
            v2},{timeout,1000}]).</div>
          <div><br>
          </div>
          <div>{error,{bad_address,{transportDomainUdpIpv4,"10.7.42.11"}}}</div>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Tue, Feb 10, 2015 at 10:40 PM, jim
            rosenblum <span dir="ltr"><<a moz-do-not-send="true" href="mailto:jim.rosenblum@gmail.com" target="_blank">jim.rosenblum@gmail.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div dir="ltr">Folks,
                <div><br>
                </div>
                <div>I have an application that uses snmp that used to
                  work and all of a sudden doesn't - I did upgrade from
                  17.1 to 17.4 - but other than that nothing has changed
                  that I know of. I am having trouble down-grading, so I
                  cannot confirm that the upgrade is the culprit.</div>
                <div><br>
                </div>
                <div>When I do the following from a machine with IP
                  address 10.6.81.19</div>
                <div>
                  <div>1> snmpm:register_agent(hope,"Hope",
                    [{engine_id,
                    "mgrEngine"},{community,"CLSENTRY"},{address,
                    "10.7.42.11"}]).</div>
                  <div><br>
                  </div>
                  <div>I get</div>
                  <div>{error,{bad_address,{snmpUDPDomain,"10.7.42.11"}}}</div>
                </div>
                <div><br>
                </div>
                <div>I have an appropriate snmpd.conf on 10.7.42.11 that
                  has</div>
                <div>
                  <div><br>
                  </div>
                  <div>com2sec sentrysrv <a moz-do-not-send="true" href="http://10.6.81.19/32" target="_blank">10.6.81.19/32</a>
                    CLSENTRY</div>
                  <div>group CLROGroup v2c sentrysrv</div>
                  <div>view all included .1 80</div>
                  <div>access CLROGroup "" v2c noauth exact all none
                    none</div>
                </div>
                <div><br>
                </div>
                <div>adding {tdomain, transportDomainUdpIpv4} to the
                  option list results in the, essentially, same error:</div>
                <div>{error,{bad_address,{{error,{bad_address,{transportDomainUdpIpv4,"10.7.42.11"}}}<br>
                </div>
                <div><br>
                </div>
                <div><br>
                </div>
                <div>Both machines can ping each other. The snmpd daemon
                  is running on .11, I have tried all kinds of
                  additional options (port, etc.), but cannot get it to
                  work</div>
                <div><br>
                </div>
                <div>This is *killing* me, can anyone point out what
                  stupid thing I am doing wrong?</div>
                <div><br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
    </blockquote>
    <br>
  

</div></blockquote></body></html>