<?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: Virtual connect stacking in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351275#M5031</link>
    <description>Ken, thanks for the answer !&lt;BR /&gt;&lt;BR /&gt;After multi-enclosure stacking  will be available (we have 2.x firmware and don't want downgrade) - can we move VC-enet modules between VC domains ?&lt;BR /&gt;</description>
    <pubDate>Tue, 10 Feb 2009 18:29:31 GMT</pubDate>
    <dc:creator>Igor Karasik</dc:creator>
    <dc:date>2009-02-10T18:29:31Z</dc:date>
    <item>
      <title>Virtual connect stacking</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351273#M5029</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Our current environment on one of our sites:&lt;BR /&gt;- Two C7000 enclosures,&lt;BR /&gt;- In each enclosure we have &lt;BR /&gt;  * 2 HP 1/10Gb-F Virtual Connect Ethernet Modules in interconnect bays 1 and 2, connected to our network backbone&lt;BR /&gt;   * 2 HP 1/10Gb-F Virtual Connect Ethernet Modules in interconnect bays 3 and 4,  connected to our iSCSI network&lt;BR /&gt;&lt;BR /&gt;iSCSI network is physically different from our network backbone.&lt;BR /&gt;&lt;BR /&gt;VC domain "1" defined for enclosure 1 and  VC domain "2" defined for enclosure 2.&lt;BR /&gt;No stacking links exists.  VC-Enet have last firmware.&lt;BR /&gt;&lt;BR /&gt;We want to connect VC-Enet in bays 1 and 2 from Enclosure 1 to VC-Enet in bays 1 and 2 from Enclosure 2 with stacking links.&lt;BR /&gt;&lt;BR /&gt;We want to connect VC-Enet in bays 3 and 4 from Enclosure 1 to VC-Enet in bays 3 and 4 from Enclosure 2 with stacking links as well.&lt;BR /&gt;&lt;BR /&gt;We want to make VC domain "1" only for our network backbone  and VC domain "2" only for our iSCSI network  (i.e. to move VC-Enet in bays 1 and 2 from Enclosure 2 to VC domain "1", VC-Enet in bays 3 and 4 from Enclosure 1 to VC domain "2",....) &lt;BR /&gt;&lt;BR /&gt;Is all this procedure possible ?&lt;BR /&gt;Can we establish stacking links between VC's in differenet enclosures ?&lt;BR /&gt;Can we move VC-enet modules between VC domains ?&lt;BR /&gt;&lt;BR /&gt;One more question - currently we have  "Stacking link failed message" in VC manager because we don't have stacking links between VC-enet modules&lt;BR /&gt;in bay 1-2 and bay 3-4. Because we will never connect these VC-enet modules with stacking link (it is physically different networks) - can we disable this message ?&lt;BR /&gt;&lt;BR /&gt;Thanks, Igor</description>
      <pubDate>Wed, 04 Feb 2009 09:11:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351273#M5029</guid>
      <dc:creator>Igor Karasik</dc:creator>
      <dc:date>2009-02-04T09:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect stacking</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351274#M5030</link>
      <description>Stacking between enclosures is currently a beta feature in the 1.3x firmware, but not the 2.x firmware.  I think VC Manager has a link to apply for a beta license key.  &lt;BR /&gt;&lt;BR /&gt;I believe multi-enclosure stacking is planned as a production feature in future firmware, but the schedule's not publicly available.&lt;BR /&gt;&lt;BR /&gt;You can just put a 1Gb Cat 5 cable between bays 1/3 - 2/4 and the error will go away.  no traffic will be routed over the connection if it's not configured to.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Feb 2009 14:19:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351274#M5030</guid>
      <dc:creator>Ken Henault</dc:creator>
      <dc:date>2009-02-10T14:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect stacking</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351275#M5031</link>
      <description>Ken, thanks for the answer !&lt;BR /&gt;&lt;BR /&gt;After multi-enclosure stacking  will be available (we have 2.x firmware and don't want downgrade) - can we move VC-enet modules between VC domains ?&lt;BR /&gt;</description>
      <pubDate>Tue, 10 Feb 2009 18:29:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351275#M5031</guid>
      <dc:creator>Igor Karasik</dc:creator>
      <dc:date>2009-02-10T18:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect stacking</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351276#M5032</link>
      <description>Sure, you'll be deleting from one domain, then adding it to another domain as if it were a new device.  No configuration information will be carried over when you move it.</description>
      <pubDate>Tue, 10 Feb 2009 18:31:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351276#M5032</guid>
      <dc:creator>Ken Henault</dc:creator>
      <dc:date>2009-02-10T18:31:44Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual connect stacking</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351277#M5033</link>
      <description>ken &lt;BR /&gt;if i just move the vc without deleting it from the first domain. the vc will be reset to default automatically ? so when i insert it in a  new enclosure all blade servers will boot with no problem using their default mac address? &lt;BR /&gt;</description>
      <pubDate>Tue, 27 Apr 2010 23:55:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-stacking/m-p/4351277#M5033</guid>
      <dc:creator>ilayy</dc:creator>
      <dc:date>2010-04-27T23:55:07Z</dc:date>
    </item>
  </channel>
</rss>

