<?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 Virtual Connect links between enclosures in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-links-between-enclosures/m-p/5729033#M31526</link>
    <description>&lt;P&gt;&lt;STRONG&gt;A question from Barry:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it possible to link 2 enclosures, that are each in a separate VC domain? So that traffic that is on the same vlan ID (and vc network name) goes through that link and not an uplink to a core switch??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The customer doesn’t want to go down the multi-enclosure VC domain.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’ve got 2 connected together now, but I’m not seeing any indication that they are seeing each other. I’m only using 1Gb SFP. The customer is going to 10Gb once they settle on a switch…. Usual story.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;****************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Input from Dan:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You can do a “back to back” connection between 2 Enclosures (or really any 2 domains if you have MES in one/both of them) but there are 2 things to consider.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You have to turn the Failover Mode from Auto to Manual and then make sure both sides have the same link as Primary.&amp;nbsp; An auto failover will only occur if the link is disconnected or the VC module on either side fails causing the other side to go Link Down.&lt;/P&gt;&lt;P&gt;2)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Whatever Networks/VLANs/SUSs you associate with this back2back connection will ONLY exist within both VC Domains and CANNOT leave either enclosure through a normal SUS uplink to a Core Switch.&amp;nbsp; This is because we do not allow traffic to come in through an uplink (what the back2back is considered) and then leave another uplink.&amp;nbsp; And any 1 Network/VLAN can only be associated with 1 uplink.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So for a RAC Cluster, MSCS Cluster or vMotion network that will only exist between the 2 enclosures, this is probably ok.&amp;nbsp; But you will not be able to ping anything on that network from outside.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just imagine you took 2 DL380s and ran a crossover cable between the 2 machines, as that’s effectively what you are building.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;And some input from Anton:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Think this scenario is described here(connecting VC modules in different domains) : p. 26/27 in &lt;A href="http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01732252/c01732252.pdf" target="_blank"&gt;http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01732252/c01732252.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Other comments or suggestions?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Jul 2012 14:57:52 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2012-07-18T14:57:52Z</dc:date>
    <item>
      <title>Virtual Connect links between enclosures</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-links-between-enclosures/m-p/5729033#M31526</link>
      <description>&lt;P&gt;&lt;STRONG&gt;A question from Barry:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is it possible to link 2 enclosures, that are each in a separate VC domain? So that traffic that is on the same vlan ID (and vc network name) goes through that link and not an uplink to a core switch??&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The customer doesn’t want to go down the multi-enclosure VC domain.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I’ve got 2 connected together now, but I’m not seeing any indication that they are seeing each other. I’m only using 1Gb SFP. The customer is going to 10Gb once they settle on a switch…. Usual story.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;****************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Input from Dan:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;You can do a “back to back” connection between 2 Enclosures (or really any 2 domains if you have MES in one/both of them) but there are 2 things to consider.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; You have to turn the Failover Mode from Auto to Manual and then make sure both sides have the same link as Primary.&amp;nbsp; An auto failover will only occur if the link is disconnected or the VC module on either side fails causing the other side to go Link Down.&lt;/P&gt;&lt;P&gt;2)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Whatever Networks/VLANs/SUSs you associate with this back2back connection will ONLY exist within both VC Domains and CANNOT leave either enclosure through a normal SUS uplink to a Core Switch.&amp;nbsp; This is because we do not allow traffic to come in through an uplink (what the back2back is considered) and then leave another uplink.&amp;nbsp; And any 1 Network/VLAN can only be associated with 1 uplink.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So for a RAC Cluster, MSCS Cluster or vMotion network that will only exist between the 2 enclosures, this is probably ok.&amp;nbsp; But you will not be able to ping anything on that network from outside.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just imagine you took 2 DL380s and ran a crossover cable between the 2 machines, as that’s effectively what you are building.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;And some input from Anton:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Think this scenario is described here(connecting VC modules in different domains) : p. 26/27 in &lt;A href="http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01732252/c01732252.pdf" target="_blank"&gt;http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01732252/c01732252.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;**************&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Other comments or suggestions?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jul 2012 14:57:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-links-between-enclosures/m-p/5729033#M31526</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2012-07-18T14:57:52Z</dc:date>
    </item>
  </channel>
</rss>

