<?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: Stealthwatch snmp issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/stealthwatch-snmp-issue/m-p/4595682#M1089334</link>
    <description>&lt;P&gt;balaji, it wasnt working for either version. As it turns out we had a few issues, first snmp was not enabled like it should have been by default. Second there is a bug that affects version 7.3.2 that is stated to be resolved and is not, it causes the snmp service to stall and restarting docker resolves the problem. Third there is another bug that affects 7.3.2 that prevents the system from accepting the pw entered and displays pw cannot be blank. There is a rollup patch available to resolve this issue.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 19 Apr 2022 19:25:55 GMT</pubDate>
    <dc:creator>KacyHicks21882</dc:creator>
    <dc:date>2022-04-19T19:25:55Z</dc:date>
    <item>
      <title>Stealthwatch snmp issue</title>
      <link>https://community.cisco.com/t5/network-security/stealthwatch-snmp-issue/m-p/4595473#M1089320</link>
      <description>&lt;P&gt;We are using version 7.3.2 and snmp is not connecting to the network equipment, I confirmed the username and password were correct, then using Splunk checked for traffic from the SMC to random network equipment and am not seeing any traffic from the SMC or the FC to the IPs. What could be wrong and where should I start looking?&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 14:35:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/stealthwatch-snmp-issue/m-p/4595473#M1089320</guid>
      <dc:creator>KacyHicks21882</dc:creator>
      <dc:date>2022-04-19T14:35:54Z</dc:date>
    </item>
    <item>
      <title>Re: Stealthwatch snmp issue</title>
      <link>https://community.cisco.com/t5/network-security/stealthwatch-snmp-issue/m-p/4595668#M1089330</link>
      <description>&lt;P&gt;try to remove all the config and start again and check. is this SNMPv3 ? or v2 ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 19:02:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/stealthwatch-snmp-issue/m-p/4595668#M1089330</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2022-04-19T19:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: Stealthwatch snmp issue</title>
      <link>https://community.cisco.com/t5/network-security/stealthwatch-snmp-issue/m-p/4595682#M1089334</link>
      <description>&lt;P&gt;balaji, it wasnt working for either version. As it turns out we had a few issues, first snmp was not enabled like it should have been by default. Second there is a bug that affects version 7.3.2 that is stated to be resolved and is not, it causes the snmp service to stall and restarting docker resolves the problem. Third there is another bug that affects 7.3.2 that prevents the system from accepting the pw entered and displays pw cannot be blank. There is a rollup patch available to resolve this issue.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 19:25:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/stealthwatch-snmp-issue/m-p/4595682#M1089334</guid>
      <dc:creator>KacyHicks21882</dc:creator>
      <dc:date>2022-04-19T19:25:55Z</dc:date>
    </item>
  </channel>
</rss>

