<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SNMP in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347747#M344432</link>
    <description>SNMP is based on UDP protocol, which does not include any mechanism for acknowledging received messages. It works on "best-effort, no guarantees" basis. As far as I know, SNMP does not implement any acknowledge mechanisms on top of the basic UDP - after all, it is "Simple".&lt;BR /&gt;&lt;BR /&gt;So, if HOST-A sends a query to HOST-B and HOST-B responds to it, HOST-B only knows if the answer was sent or not: there is no way for it to know if the answer reached HOST-A or not. &lt;BR /&gt;&lt;BR /&gt;It is the responsibility of HOST-A to retry the query if it did not receive the answer, or to report an error if repeated retries won't help.&lt;BR /&gt;&lt;BR /&gt;MK</description>
    <pubDate>Sat, 31 Jan 2009 08:55:41 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2009-01-31T08:55:41Z</dc:date>
    <item>
      <title>SNMP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347742#M344427</link>
      <description>If an external application running on HOST-A invokes snmpget command on HOST-B, is there a log maintained on HOST-B that can be used to check whether snmpget failed or succeeded?&lt;BR /&gt;&lt;BR /&gt;How can a sys admin troubleshoot whether HOST-B receives snmpget properly?</description>
      <pubDate>Thu, 29 Jan 2009 17:42:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347742#M344427</guid>
      <dc:creator>indianya</dc:creator>
      <dc:date>2009-01-29T17:42:53Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347743#M344428</link>
      <description>indianya,&lt;BR /&gt;&lt;BR /&gt;Usually in HP-UX snmpget error messages are logged into the syslog.log&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Jaime</description>
      <pubDate>Thu, 29 Jan 2009 18:08:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347743#M344428</guid>
      <dc:creator>Jaime Bolanos Rojas.</dc:creator>
      <dc:date>2009-01-29T18:08:32Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347744#M344429</link>
      <description>Jaime,&lt;BR /&gt;&lt;BR /&gt;Thank you for replying. I already checked but I do not have any messages related to SNMP in syslog.log</description>
      <pubDate>Thu, 29 Jan 2009 18:42:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347744#M344429</guid>
      <dc:creator>indianya</dc:creator>
      <dc:date>2009-01-29T18:42:18Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347745#M344430</link>
      <description>ps -ef | grep snmpd&lt;BR /&gt;&lt;BR /&gt;do you something running with -l option ?&lt;BR /&gt;if not, you are not logging snmp traffic. Since snmp chatter can be a bit too much, unless you are working on aproblem, I'd suggest not using the -l option but for this troubleshooting effort, you can kill the daemon and restart with -l &lt;LOGFILENAME&gt; option and see what's going on. Once finished, you might want to kill it again and start without logging enabled.&lt;BR /&gt;&lt;BR /&gt;Hope this helps&lt;/LOGFILENAME&gt;</description>
      <pubDate>Thu, 29 Jan 2009 19:41:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347745#M344430</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2009-01-29T19:41:16Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347746#M344431</link>
      <description>on 11.31 there is a logfile&lt;BR /&gt;&lt;BR /&gt;other option you can turn on nettl and trace port 161 and 162.</description>
      <pubDate>Sat, 31 Jan 2009 01:02:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347746#M344431</guid>
      <dc:creator>Emil Velez</dc:creator>
      <dc:date>2009-01-31T01:02:44Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347747#M344432</link>
      <description>SNMP is based on UDP protocol, which does not include any mechanism for acknowledging received messages. It works on "best-effort, no guarantees" basis. As far as I know, SNMP does not implement any acknowledge mechanisms on top of the basic UDP - after all, it is "Simple".&lt;BR /&gt;&lt;BR /&gt;So, if HOST-A sends a query to HOST-B and HOST-B responds to it, HOST-B only knows if the answer was sent or not: there is no way for it to know if the answer reached HOST-A or not. &lt;BR /&gt;&lt;BR /&gt;It is the responsibility of HOST-A to retry the query if it did not receive the answer, or to report an error if repeated retries won't help.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Sat, 31 Jan 2009 08:55:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/snmp/m-p/4347747#M344432</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-01-31T08:55:41Z</dc:date>
    </item>
  </channel>
</rss>

