<?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: switch problem in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851073#M8986</link>
    <description>The most logical explanation is that the duplex setting on the 4000M or the 4104gl changed so that it caused a mismatch and brought the link down. Possibly someone else logged into the switch and changed this? Was there anything interesting in the logs for either switch?</description>
    <pubDate>Sun, 27 Aug 2006 23:37:15 GMT</pubDate>
    <dc:creator>Matt Hobbs</dc:creator>
    <dc:date>2006-08-27T23:37:15Z</dc:date>
    <item>
      <title>switch problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851068#M8981</link>
      <description>I have a building with 20 users connected to hp4104gl Procurve, this switch connected to another HP4000 in another building through fibre cable sudenly the network went down in the first bulding, at the begining  I checked the fibre but it was ok then I changed the the speed from auto to fix 1000 and everything start to work a gain I am not sure why this was a problem because before it was working with this setup????</description>
      <pubDate>Sun, 27 Aug 2006 06:03:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851068#M8981</guid>
      <dc:creator>badro</dc:creator>
      <dc:date>2006-08-27T06:03:59Z</dc:date>
    </item>
    <item>
      <title>Re: switch problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851069#M8982</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Do you have any port monitoring running? ro any kind of utilization monitoring ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 27 Aug 2006 09:04:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851069#M8982</guid>
      <dc:creator>Mohieddin Kharnoub</dc:creator>
      <dc:date>2006-08-27T09:04:24Z</dc:date>
    </item>
    <item>
      <title>Re: switch problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851070#M8983</link>
      <description>By default the fibre ports on the 4000M default to 1000-FDX, whereas the 4100 default to Auto. &lt;BR /&gt;&lt;BR /&gt;It sounds as though your 4000M had been reset to default configuration for some reason.</description>
      <pubDate>Sun, 27 Aug 2006 15:11:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851070#M8983</guid>
      <dc:creator>Matt Hobbs</dc:creator>
      <dc:date>2006-08-27T15:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: switch problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851071#M8984</link>
      <description>I have checked the 4000 it was on 1000-FDX&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sun, 27 Aug 2006 23:21:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851071#M8984</guid>
      <dc:creator>badro</dc:creator>
      <dc:date>2006-08-27T23:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: switch problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851072#M8985</link>
      <description>sorry I am not monitoring any port in any of the two switches.</description>
      <pubDate>Sun, 27 Aug 2006 23:30:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851072#M8985</guid>
      <dc:creator>badro</dc:creator>
      <dc:date>2006-08-27T23:30:48Z</dc:date>
    </item>
    <item>
      <title>Re: switch problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851073#M8986</link>
      <description>The most logical explanation is that the duplex setting on the 4000M or the 4104gl changed so that it caused a mismatch and brought the link down. Possibly someone else logged into the switch and changed this? Was there anything interesting in the logs for either switch?</description>
      <pubDate>Sun, 27 Aug 2006 23:37:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851073#M8986</guid>
      <dc:creator>Matt Hobbs</dc:creator>
      <dc:date>2006-08-27T23:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: switch problem</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851074#M8987</link>
      <description>The message alert shows the following message in the hp4000 "Excessive Broadcasts on port I1" but the the fibre was connected in J1. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Aug 2006 04:27:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/switch-problem/m-p/3851074#M8987</guid>
      <dc:creator>badro</dc:creator>
      <dc:date>2006-08-28T04:27:03Z</dc:date>
    </item>
  </channel>
</rss>

