<?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: RSTP + Path Costs in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480052#M19465</link>
    <description>that is the problem, no ports show as blocked. Attched is output of sh span...</description>
    <pubDate>Mon, 17 Aug 2009 09:20:16 GMT</pubDate>
    <dc:creator>RICHARDM001</dc:creator>
    <dc:date>2009-08-17T09:20:16Z</dc:date>
    <item>
      <title>RSTP + Path Costs</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480050#M19463</link>
      <description>Hi. How can I confirm that my RSTP and allocated path costs are actually following the path with the least cost. I have 2 core switches, one priorit 0 and the backup 1. I have a trunk between them with a cost of 200 and priority 64, from the root I have a fiber to the first edge switch (edge01), that fiber has a cost of  2000 and priority 64. From the second core switch I have a fiber to edge02, that fiber has a cost of 40000 and priority of 128. From edge02  there is another fiber to edge03, the fiber has a cost of 40000 and pririty of 128. edge03 and edge01 are interlinked with copper gigabit. I am finding that the path for traffic always seems to go via edge02 and not via edge01, I figured this because if I continual icmp to root and boot edge02 we drop a few packets. The path via root to edge01 is a direct fiber link to get to aux data centre from main data center, the path via edge02 needs to go via that switch to get to our aux data centre? i tried setting switch priorities, but made no diff. &lt;BR /&gt;&lt;BR /&gt;Sincerely</description>
      <pubDate>Sat, 15 Aug 2009 07:39:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480050#M19463</guid>
      <dc:creator>RICHARDM001</dc:creator>
      <dc:date>2009-08-15T07:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: RSTP + Path Costs</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480051#M19464</link>
      <description>log onto edge03, and "show span"&lt;BR /&gt;&lt;BR /&gt;If everything is as you expect you should see the correct root MAC address, root path cost, and root port. Also the backup link should show as blocking. &lt;BR /&gt;</description>
      <pubDate>Mon, 17 Aug 2009 09:04:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480051#M19464</guid>
      <dc:creator>Richard Brodie_1</dc:creator>
      <dc:date>2009-08-17T09:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: RSTP + Path Costs</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480052#M19465</link>
      <description>that is the problem, no ports show as blocked. Attched is output of sh span...</description>
      <pubDate>Mon, 17 Aug 2009 09:20:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480052#M19465</guid>
      <dc:creator>RICHARDM001</dc:creator>
      <dc:date>2009-08-17T09:20:16Z</dc:date>
    </item>
    <item>
      <title>Re: RSTP + Path Costs</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480053#M19466</link>
      <description>The blocked link must be on one of the other switches, I suppose.&lt;BR /&gt;&lt;BR /&gt;If you do a "show span" and "show lldp info remote" round the set, that should be enough to reconstruct the full topology.&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Aug 2009 09:50:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/rstp-path-costs/m-p/4480053#M19466</guid>
      <dc:creator>Richard Brodie_1</dc:creator>
      <dc:date>2009-08-17T09:50:36Z</dc:date>
    </item>
  </channel>
</rss>

