<?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: ethernet vc in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619516#M10046</link>
    <description>You can handle failover at the server level, as an example, you create 2 networks on VC, NetA using uplink ports on VC bay 1 and NetB using uplink ports on VC bay 2 (Smartlink enabled on both), each VC connected to each external switch. On the server profile, NIC 1 will be assigned to NetA and NIC 2 to NetB, At the OS level you can configure NIC teaming or Bonding, then if the connection between VC bay 1 and the external switch goes down, the OS will handle the failover, same behavior if the entire VC module goes down.</description>
    <pubDate>Mon, 19 Apr 2010 01:06:53 GMT</pubDate>
    <dc:creator>Lmm_1</dc:creator>
    <dc:date>2010-04-19T01:06:53Z</dc:date>
    <item>
      <title>ethernet vc</title>
      <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619515#M10045</link>
      <description>hi experts i have ethernet vc installed in bay 1 and 2 in c7000 also i have to redundant external swtiches i want to configure redundant ethernet connection. &lt;BR /&gt;1)is it possible to use vc in bay 2 as acrive vc also and configure network redundancy at the server level?&lt;BR /&gt;2)if not. for example i have a bl460c in bay 1 so the nic 1 is connected to the port 1 to vc in bay 1 one nic 2 is connected to the port 1 of the vc in bay 2 now if i configure a vlan that connect the nic 1 of the server to the uplink one and now the vc in bay 1 go down what happen ? what happen?</description>
      <pubDate>Sat, 17 Apr 2010 23:55:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619515#M10045</guid>
      <dc:creator>ilayy</dc:creator>
      <dc:date>2010-04-17T23:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: ethernet vc</title>
      <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619516#M10046</link>
      <description>You can handle failover at the server level, as an example, you create 2 networks on VC, NetA using uplink ports on VC bay 1 and NetB using uplink ports on VC bay 2 (Smartlink enabled on both), each VC connected to each external switch. On the server profile, NIC 1 will be assigned to NetA and NIC 2 to NetB, At the OS level you can configure NIC teaming or Bonding, then if the connection between VC bay 1 and the external switch goes down, the OS will handle the failover, same behavior if the entire VC module goes down.</description>
      <pubDate>Mon, 19 Apr 2010 01:06:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619516#M10046</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2010-04-19T01:06:53Z</dc:date>
    </item>
    <item>
      <title>Re: ethernet vc</title>
      <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619517#M10047</link>
      <description>Look at the scenario 11 or 12 of this cookbook:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01471917/c01471917.pdf" target="_blank"&gt;http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c01471917/c01471917.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 19 Apr 2010 01:10:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619517#M10047</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2010-04-19T01:10:49Z</dc:date>
    </item>
    <item>
      <title>Re: ethernet vc</title>
      <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619518#M10048</link>
      <description>so what you meant is both of the vc are active on the same time and what is failing over is just the web interface. my second question is can i connect an msa directly to an fc vc or it should be seperated by a san switch and here i ask fc vc support zoning?</description>
      <pubDate>Mon, 19 Apr 2010 16:22:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619518#M10048</guid>
      <dc:creator>ilayy</dc:creator>
      <dc:date>2010-04-19T16:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: ethernet vc</title>
      <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619519#M10049</link>
      <description>I think that you need the SAN switch the middle, someone else can confirm it here.</description>
      <pubDate>Mon, 19 Apr 2010 16:27:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619519#M10049</guid>
      <dc:creator>Lmm_1</dc:creator>
      <dc:date>2010-04-19T16:27:58Z</dc:date>
    </item>
    <item>
      <title>Re: ethernet vc</title>
      <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619520#M10050</link>
      <description>The VC FC are not like a SAN switch, you cannot direct connect i.e. a disk array to it, as mentioned you do need a SAN switch in between.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Kris&lt;BR /&gt;</description>
      <pubDate>Mon, 19 Apr 2010 19:51:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619520#M10050</guid>
      <dc:creator>kris rombauts</dc:creator>
      <dc:date>2010-04-19T19:51:51Z</dc:date>
    </item>
    <item>
      <title>Re: ethernet vc</title>
      <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619521#M10051</link>
      <description>so if i use borcade san switch i will be able to connect it directly to the msa? and in which c3000 or c7000 switch bay can i install? can i install it in bay 1 and 2?</description>
      <pubDate>Tue, 20 Apr 2010 17:22:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619521#M10051</guid>
      <dc:creator>ilayy</dc:creator>
      <dc:date>2010-04-20T17:22:27Z</dc:date>
    </item>
    <item>
      <title>Re: ethernet vc</title>
      <link>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619522#M10052</link>
      <description>The above replies are talking about using an external SAN switch as an intermediary between your FC VC modules and the storage sub-system.    In this case, the SAN switch does not install in the c7000/c3000 enclosure.&lt;BR /&gt;&lt;BR /&gt;There are SAN switch modules which can be plugged directly into the c7000/c3000, (e.g. Brocade 8Gb SAN Switch 8/12c - Switch - 12 ports - 8Gb Fibre Channel - plug-in module)&lt;BR /&gt;however this is not a "Virtual Connect" device, it would actually replace your VC FC modules and would not be configurable using VCM.&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Dave.</description>
      <pubDate>Thu, 22 Apr 2010 12:32:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/ethernet-vc/m-p/4619522#M10052</guid>
      <dc:creator>The Brit</dc:creator>
      <dc:date>2010-04-22T12:32:46Z</dc:date>
    </item>
  </channel>
</rss>

