<?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 ProCurve STP/IGMP problem in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698322#M24101</link>
    <description>Good Morning,&lt;BR /&gt;&lt;BR /&gt;We recently had an issue with one of our primary procurve chassis causing the following messages in our syslog server&lt;BR /&gt;&lt;BR /&gt;Access to our firewall via LAN which handling our upstream routing was disabled however I could access it if I plug into the LAN port on the firewall from my laptop.&lt;BR /&gt;&lt;BR /&gt;Access within the LAN was terrible packet loss to the switch/servers etc..&lt;BR /&gt;&lt;BR /&gt;I'm trying to get some insight of what could of caused this.&lt;BR /&gt;&lt;BR /&gt;2010-10-08 22:24:26 User.Info 192.168.X.X  Oct  9 02:24:27 192.168.X.X 00302 igmp:  DEFAULT_VLAN: This switch is no longer Querier&lt;BR /&gt;2010-10-08 22:28:41 User.Info 192.168.X.X Oct  9 02:28:42 192.168.X.X 00298 igmp:  DEFAULT_VLAN: Querier Election in process&lt;BR /&gt;2010-10-08 22:30:46 User.Info 192.168.X.X  Oct  9 02:30:47 192.168.X.X 00299 igmp:  DEFAULT_VLAN: This switch has been elected as Querier&lt;BR /&gt;2010-10-08 22:30:46 User.Info 192.168.X.X  Oct  9 02:30:47 192.168.X.X 00301 igmp:  DEFAULT_VLAN: Other Querier detected</description>
    <pubDate>Tue, 12 Oct 2010 10:48:10 GMT</pubDate>
    <dc:creator>top10</dc:creator>
    <dc:date>2010-10-12T10:48:10Z</dc:date>
    <item>
      <title>ProCurve STP/IGMP problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698322#M24101</link>
      <description>Good Morning,&lt;BR /&gt;&lt;BR /&gt;We recently had an issue with one of our primary procurve chassis causing the following messages in our syslog server&lt;BR /&gt;&lt;BR /&gt;Access to our firewall via LAN which handling our upstream routing was disabled however I could access it if I plug into the LAN port on the firewall from my laptop.&lt;BR /&gt;&lt;BR /&gt;Access within the LAN was terrible packet loss to the switch/servers etc..&lt;BR /&gt;&lt;BR /&gt;I'm trying to get some insight of what could of caused this.&lt;BR /&gt;&lt;BR /&gt;2010-10-08 22:24:26 User.Info 192.168.X.X  Oct  9 02:24:27 192.168.X.X 00302 igmp:  DEFAULT_VLAN: This switch is no longer Querier&lt;BR /&gt;2010-10-08 22:28:41 User.Info 192.168.X.X Oct  9 02:28:42 192.168.X.X 00298 igmp:  DEFAULT_VLAN: Querier Election in process&lt;BR /&gt;2010-10-08 22:30:46 User.Info 192.168.X.X  Oct  9 02:30:47 192.168.X.X 00299 igmp:  DEFAULT_VLAN: This switch has been elected as Querier&lt;BR /&gt;2010-10-08 22:30:46 User.Info 192.168.X.X  Oct  9 02:30:47 192.168.X.X 00301 igmp:  DEFAULT_VLAN: Other Querier detected</description>
      <pubDate>Tue, 12 Oct 2010 10:48:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698322#M24101</guid>
      <dc:creator>top10</dc:creator>
      <dc:date>2010-10-12T10:48:10Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve STP/IGMP problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698323#M24102</link>
      <description>the changes in the Querier status like this might indicate some issues with the other device or even the link flapping, can you please clarify the IP addresses and which other device is becoming Querier, also where it is connected.&lt;BR /&gt;&lt;BR /&gt;Please get the "show tech all" command output if possible.</description>
      <pubDate>Sun, 17 Oct 2010 06:27:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698323#M24102</guid>
      <dc:creator>Shadow13</dc:creator>
      <dc:date>2010-10-17T06:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve STP/IGMP problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698324#M24103</link>
      <description>This may sound like a silly question but, how do I go about finding which device was sending those querier requests?&lt;BR /&gt;&lt;BR /&gt;I have attached my show tech output</description>
      <pubDate>Mon, 18 Oct 2010 10:45:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698324#M24103</guid>
      <dc:creator>top10</dc:creator>
      <dc:date>2010-10-18T10:45:44Z</dc:date>
    </item>
    <item>
      <title>Re: ProCurve STP/IGMP problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698325#M24104</link>
      <description>mmm are you sure this is the correct switch from where you got the "show tech all" ?? it does not even have IGMP enabled.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;To find out what are the devices from the logs above check the IP addresses trace them to the devices that have these addresses.</description>
      <pubDate>Mon, 18 Oct 2010 15:01:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/procurve-stp-igmp-problem/m-p/4698325#M24104</guid>
      <dc:creator>Shadow13</dc:creator>
      <dc:date>2010-10-18T15:01:48Z</dc:date>
    </item>
  </channel>
</rss>

