<?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: Blade issues when moving between Chassis in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/blade-issues-when-moving-between-chassis/m-p/6966644#M30164</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;yes they are all sperate pre-defined networks&lt;/P&gt;&lt;P&gt;Chassis 1 is using HP Pre-defined 1 for WWN and MAC&lt;/P&gt;&lt;P&gt;Chassis 2 is using HP Predefined 3 for WWN and MAC&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i cannot seem to find anything to link them together to see the issues&lt;/P&gt;&lt;P&gt;VC Firmware: 4.45&lt;/P&gt;&lt;P&gt;OA Firmwware: 4.5&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;these are within the matrix for our blades and was recommended by professional services when we had them installed at the time&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jun 2017 08:08:32 GMT</pubDate>
    <dc:creator>Lagcat</dc:creator>
    <dc:date>2017-06-01T08:08:32Z</dc:date>
    <item>
      <title>Blade issues when moving between Chassis</title>
      <link>https://community.hpe.com/t5/bladesystem-general/blade-issues-when-moving-between-chassis/m-p/6966621#M30162</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;background:&lt;/P&gt;&lt;P&gt;4x C7000s - all half populated with BL460c Gen9's&lt;/P&gt;&lt;P&gt;all Virtual Connected up&lt;/P&gt;&lt;P&gt;2x 8GB FC connections from each virtual connect to Netapp/3par/MSA via cisco MDS&lt;/P&gt;&lt;P&gt;2x10GB uplinks from each virtual connect to our core switches&lt;/P&gt;&lt;P&gt;there is no links between chassis and each chassis is set to its own virtual domain&lt;/P&gt;&lt;P&gt;all vmware esx hosts&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;so my problem:&lt;/P&gt;&lt;P&gt;i have moved&amp;nbsp;a blade&amp;nbsp;from chassis 1 BAY&amp;nbsp;4&amp;nbsp;to chassis 3 BAY 5 -&amp;nbsp; no problems and everything carries on working correctly&lt;/P&gt;&lt;P&gt;but if i take a new blade and build ESX whilst placed in Chassis 1 BAY 4 if seems to effect the network of the host in Chassis 3 BAY 5 - i dont see how this can be possible?&lt;/P&gt;&lt;P&gt;i have set my bay profiles the same so if i needed to move blades around to work on a chassis i should be able to powerdown and move&lt;/P&gt;&lt;P&gt;also this allows me to provision the WWNs for the storage at the beginning as the so i can keep static wwns against each bay&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;am i doing something wrong or would this not work? i dont want to have to keep deleting and recreating bay profiles and having to go back to all the storage and adding new WWNs&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;the switches do not show any isues in the logs for duplicate IPs or MAC issues - the storage looks to be okay but the maangement network seems to drop off for VMware as it it was a duplicate IP - i have been through the host logs and see nothing that points to a duplicate entry or a mac that matches&lt;/P&gt;&lt;P&gt;but somewhere something is effecting this bay move between switches - is there anything additional i can check?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2017 21:38:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/blade-issues-when-moving-between-chassis/m-p/6966621#M30162</guid>
      <dc:creator>Lagcat</dc:creator>
      <dc:date>2017-05-31T21:38:59Z</dc:date>
    </item>
    <item>
      <title>Re: Blade issues when moving between Chassis</title>
      <link>https://community.hpe.com/t5/bladesystem-general/blade-issues-when-moving-between-chassis/m-p/6966638#M30163</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;How did you configure the MAC and WWN ranges on enclosures? each enclosure should have a unique range.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 07:08:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/blade-issues-when-moving-between-chassis/m-p/6966638#M30163</guid>
      <dc:creator>msh_it</dc:creator>
      <dc:date>2017-06-01T07:08:25Z</dc:date>
    </item>
    <item>
      <title>Re: Blade issues when moving between Chassis</title>
      <link>https://community.hpe.com/t5/bladesystem-general/blade-issues-when-moving-between-chassis/m-p/6966644#M30164</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;yes they are all sperate pre-defined networks&lt;/P&gt;&lt;P&gt;Chassis 1 is using HP Pre-defined 1 for WWN and MAC&lt;/P&gt;&lt;P&gt;Chassis 2 is using HP Predefined 3 for WWN and MAC&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;i cannot seem to find anything to link them together to see the issues&lt;/P&gt;&lt;P&gt;VC Firmware: 4.45&lt;/P&gt;&lt;P&gt;OA Firmwware: 4.5&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;these are within the matrix for our blades and was recommended by professional services when we had them installed at the time&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2017 08:08:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/blade-issues-when-moving-between-chassis/m-p/6966644#M30164</guid>
      <dc:creator>Lagcat</dc:creator>
      <dc:date>2017-06-01T08:08:32Z</dc:date>
    </item>
  </channel>
</rss>

