<?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 V3 test is broken in IMC</title>
    <link>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058510#M5409</link>
    <description>&lt;P&gt;Thank you for answer. With v7.3 E0605P06 and v7.3 E0703 issue is present too. I will try downgrade to v7.3 (E0506P09)&lt;/P&gt;</description>
    <pubDate>Tue, 13 Aug 2019 10:07:31 GMT</pubDate>
    <dc:creator>sanchesrg</dc:creator>
    <dc:date>2019-08-13T10:07:31Z</dc:date>
    <item>
      <title>SNMP V3 test is broken</title>
      <link>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058394#M5407</link>
      <description>&lt;P&gt;Possible causes:&lt;/P&gt;&lt;P&gt;1. The device cannot be pinged. 2. SNMP settings/Telnet settings/SSH settings is incorrect. 3. Invalid characters are found. 4. device returns a failure.&lt;/P&gt;&lt;P&gt;but from host shell no issue found&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;$ ping -c1 10.0.220.16
PING 10.0.220.16 (10.0.220.16) 56(84) bytes of data.
64 bytes from 10.0.220.16: icmp_seq=1 ttl=255 time=0.945 ms

$ snmpget -v3 -u 123 -l authPriv -a MD5 -A 123 -x DES -X 123 10.0.220.16 SNMPv2-MIB::sysDescr.0

SNMPv2-MIB::sysDescr.0 = STRING: HP J8698A Switch 5412zl, revision K.16.02.0026, ROM K.15.30 (/ws/swbuildm/maint_spokane_qaoff/code/build/btm(swbuildm_ma)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any and all suggestions are welcome.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2019 12:08:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058394#M5407</guid>
      <dc:creator>sanchesrg</dc:creator>
      <dc:date>2019-08-12T12:08:00Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP V3 test is broken</title>
      <link>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058499#M5408</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;What version of IMC are you running? There was an SNMP Template issue in 7.3 E0605P06 and I vaguely recall an issue with SNMPv3 Test in particular that failed on earlier versions, despite it actually working correctly.&lt;/P&gt;&lt;P&gt;Please make sure you are running the latest version, the issue should be fixed:&lt;/P&gt;&lt;P&gt;&lt;A href="https://h10145.www1.hpe.com/downloads/SoftwareReleases.aspx?ProductNumber=JG747AAE" target="_blank"&gt;https://h10145.www1.hpe.com/downloads/SoftwareReleases.aspx?ProductNumber=JG747AAE&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2019 09:03:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058499#M5408</guid>
      <dc:creator>jguse</dc:creator>
      <dc:date>2019-08-13T09:03:39Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP V3 test is broken</title>
      <link>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058510#M5409</link>
      <description>&lt;P&gt;Thank you for answer. With v7.3 E0605P06 and v7.3 E0703 issue is present too. I will try downgrade to v7.3 (E0506P09)&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2019 10:07:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058510#M5409</guid>
      <dc:creator>sanchesrg</dc:creator>
      <dc:date>2019-08-13T10:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP V3 test is broken</title>
      <link>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058518#M5410</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If it's not a version issue, please check a Wireshark packet capture during IMC 'Test' with SNMPv3 credentials. That should allow you to see what's going wrong.&lt;/P&gt;&lt;P&gt;You should expect to see a GET-Request for the OID corresponding to the Hostname, followed by a SET-Request to set the hostname to the device's current hostname (leaving it unchanged - but if this works, SNMP RW should be working).&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2019 11:41:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058518#M5410</guid>
      <dc:creator>jguse</dc:creator>
      <dc:date>2019-08-13T11:41:56Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP V3 test is broken</title>
      <link>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058519#M5411</link>
      <description>&lt;P&gt;in my experience IMC is very picky about the response IP of the SNMPv3 flow.&lt;/P&gt;&lt;P&gt;Please make sure the switch is responding with the IP it is managed by IMC&lt;/P&gt;&lt;P&gt;with Procurve:&lt;/P&gt;&lt;P&gt;snmp-server resp dst&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;snmp-ser resp &amp;lt;ip in imc&amp;gt;&lt;/P&gt;&lt;P&gt;hth&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2019 11:57:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/snmp-v3-test-is-broken/m-p/7058519#M5411</guid>
      <dc:creator>AbeAbe</dc:creator>
      <dc:date>2019-08-13T11:57:12Z</dc:date>
    </item>
  </channel>
</rss>

