<?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 Access Violations in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817777#M8392</link>
    <description>I've heard of something similar to this. I believe a reboot will fix it, but definitely go with the firmware update at the same time.</description>
    <pubDate>Wed, 05 Jul 2006 16:30:40 GMT</pubDate>
    <dc:creator>Matt Hobbs</dc:creator>
    <dc:date>2006-07-05T16:30:40Z</dc:date>
    <item>
      <title>SNMP Access Violations</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817773#M8388</link>
      <description>I've got a 2848 switch which, despite have a correct config, refuses to be accessed via snmp from both PCM and Inmon Traffic Sentinel / Sflowtrend.&lt;BR /&gt;&lt;BR /&gt;The log has many SNMP violation entries but I've triple checked the community strings and authorised managers are correct. We have around 100 other HP switches, including 4 2848s and these all work fine.&lt;BR /&gt;&lt;BR /&gt;Any suggestions?</description>
      <pubDate>Wed, 05 Jul 2006 09:50:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817773#M8388</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2006-07-05T09:50:30Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Access Violations</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817774#M8389</link>
      <description>The first few things i would check (In terms of PCM+ accessing the device) is the Telnet/CLI username and password combo, also, check that there isn;t an operator account setup with the same password.&lt;BR /&gt;&lt;BR /&gt;Also, check that the switch is set to go straight to CLI mode and not to MENU mode when accessed. &lt;BR /&gt;&lt;BR /&gt;None of these should be causing the SNMP access violations though... &lt;BR /&gt;</description>
      <pubDate>Wed, 05 Jul 2006 10:06:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817774#M8389</guid>
      <dc:creator>Jonathan Axford</dc:creator>
      <dc:date>2006-07-05T10:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Access Violations</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817775#M8390</link>
      <description>Jason,&lt;BR /&gt;Check out my recent thread &lt;A href="https://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1040250" target="_blank"&gt;https://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1040250&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;I ran into an issue where the global setting changed and recently discovered switches were getting denied yet older discovered switches were fine.&lt;BR /&gt;&lt;BR /&gt;Double check your global settings if you use them, otherwise check the per-device settings.  Run the Test Communication Parms wizard to verify.</description>
      <pubDate>Wed, 05 Jul 2006 10:32:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817775#M8390</guid>
      <dc:creator>Les Ligetfalvy</dc:creator>
      <dc:date>2006-07-05T10:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Access Violations</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817776#M8391</link>
      <description>Yep, all checked. The config is almost a mirror image (aside from ip details etc) of our other HP switches, all of which work ok. Its baffling.&lt;BR /&gt;&lt;BR /&gt;The switch is running 08.56 software so I'm going to schedule an upgrade.</description>
      <pubDate>Wed, 05 Jul 2006 10:32:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817776#M8391</guid>
      <dc:creator>Jason Scott</dc:creator>
      <dc:date>2006-07-05T10:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Access Violations</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817777#M8392</link>
      <description>I've heard of something similar to this. I believe a reboot will fix it, but definitely go with the firmware update at the same time.</description>
      <pubDate>Wed, 05 Jul 2006 16:30:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817777#M8392</guid>
      <dc:creator>Matt Hobbs</dc:creator>
      <dc:date>2006-07-05T16:30:40Z</dc:date>
    </item>
    <item>
      <title>Re: SNMP Access Violations</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817778#M8393</link>
      <description>I have the same problem a few years ago. After change or remove the public community, I get "snmp access violations". With a sniffer I found out, that HP JetAdmin causes this error messages. On some PC was this software installed, and this polled around the network for HP printers...&lt;BR /&gt;In my case, I added the public community with read only rights until I have removed all JetAdmins installations....&lt;BR /&gt;Maybe there is a similar software installed on a PC?</description>
      <pubDate>Thu, 06 Jul 2006 01:35:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/snmp-access-violations/m-p/3817778#M8393</guid>
      <dc:creator>Werner Weiss</dc:creator>
      <dc:date>2006-07-06T01:35:57Z</dc:date>
    </item>
  </channel>
</rss>

