<?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 Stacking Procurve Switch Help in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759569#M30490</link>
    <description>Hello,&lt;BR /&gt;&lt;BR /&gt;We have one procurve switch 2524 setup with an IP and plan to stack it with 5 more 2524 switches.    &lt;BR /&gt;&lt;BR /&gt;I would like to know if we need one IP for each stacked switches.  I hope we don't, but want to have gurus to confirm this action.&lt;BR /&gt;&lt;BR /&gt;Very appreciated.&lt;BR /&gt;&lt;BR /&gt;Steven&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 08 Jul 2002 18:45:09 GMT</pubDate>
    <dc:creator>Steven Chen_1</dc:creator>
    <dc:date>2002-07-08T18:45:09Z</dc:date>
    <item>
      <title>Stacking Procurve Switch Help</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759569#M30490</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;We have one procurve switch 2524 setup with an IP and plan to stack it with 5 more 2524 switches.    &lt;BR /&gt;&lt;BR /&gt;I would like to know if we need one IP for each stacked switches.  I hope we don't, but want to have gurus to confirm this action.&lt;BR /&gt;&lt;BR /&gt;Very appreciated.&lt;BR /&gt;&lt;BR /&gt;Steven&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 08 Jul 2002 18:45:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759569#M30490</guid>
      <dc:creator>Steven Chen_1</dc:creator>
      <dc:date>2002-07-08T18:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: Stacking Procurve Switch Help</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759570#M30491</link>
      <description>Hi Steven,&lt;BR /&gt;&lt;BR /&gt;One IP address assigned to the switch that will act as the stack commander is fine.</description>
      <pubDate>Tue, 09 Jul 2002 03:56:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759570#M30491</guid>
      <dc:creator>Fotios Kotsiopoulos</dc:creator>
      <dc:date>2002-07-09T03:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Stacking Procurve Switch Help</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759571#M30492</link>
      <description>Steve,&lt;BR /&gt;just remember: one IP for the whole stack but what happens if a switch in the middle of the stack fails? Some of the switches will be unmanageble even with a redundant connection. Is it worth having this by saving IP addresses?&lt;BR /&gt;&lt;BR /&gt;Best regards</description>
      <pubDate>Tue, 09 Jul 2002 08:05:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759571#M30492</guid>
      <dc:creator>Hartmut Petroll</dc:creator>
      <dc:date>2002-07-09T08:05:29Z</dc:date>
    </item>
    <item>
      <title>Re: Stacking Procurve Switch Help</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759572#M30493</link>
      <description>If the stack is configured with a redundant STP/RSTP connection to the rest of the network, the only time you won't be able to manage the it ss when the stack commander switch fails.&lt;BR /&gt;&lt;BR /&gt;Member stack switches that don't have IP addresses assigned can fail without affecting management of the stack. However, since the commander switch is still a single point of failure (from a management point of view), you can always assign IP addresses to the member switches as a backup.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Fotios.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 25 Jul 2002 05:29:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759572#M30493</guid>
      <dc:creator>Fotios Kotsiopoulos</dc:creator>
      <dc:date>2002-07-25T05:29:55Z</dc:date>
    </item>
    <item>
      <title>Re: Stacking Procurve Switch Help</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759573#M30494</link>
      <description>Hello Steven,&lt;BR /&gt;Another thing to consider is that Toptools Device Manager discovers and manages devices by IP address, so if these other 5 switches do not have IP addresses assigned to them, Toptools will not discover and manage them.  They can still be seen through the commander, but things like firmware updates can not be completed via Toptools Device Manager.&lt;BR /&gt;Louis&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Jul 2002 14:18:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759573#M30494</guid>
      <dc:creator>Louis Goeppinger</dc:creator>
      <dc:date>2002-07-31T14:18:41Z</dc:date>
    </item>
    <item>
      <title>Re: Stacking Procurve Switch Help</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759574#M30495</link>
      <description>Can stacked, 2900-series Procurve switches receive firmware updates through the web UI?  If the stack commander is the only one with an IP address, and this is possible, should it get the firmware update first, followed by stack members?  Or the other way around?</description>
      <pubDate>Sat, 03 Oct 2009 00:16:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/stacking-procurve-switch-help/m-p/2759574#M30495</guid>
      <dc:creator>DCSloane</dc:creator>
      <dc:date>2009-10-03T00:16:48Z</dc:date>
    </item>
  </channel>
</rss>

