<?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: I/O mismatch / Port Mismatch in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/i-o-mismatch-port-mismatch/m-p/4625501#M10150</link>
    <description>Christian,&lt;BR /&gt;&lt;BR /&gt;you can't really workaround that issue.  the 2x220c's require ethernet modules in bays 3 and 4.&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 28 Apr 2010 15:06:04 GMT</pubDate>
    <dc:creator>HEM_2</dc:creator>
    <dc:date>2010-04-28T15:06:04Z</dc:date>
    <item>
      <title>I/O mismatch / Port Mismatch</title>
      <link>https://community.hpe.com/t5/bladesystem-general/i-o-mismatch-port-mismatch/m-p/4625500#M10149</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm working with a c7000 Enclosure with several ProLiant BL2x220c G5 blades sitting in device bay 1(a/b), 2(a/b), 3(a/b), 9(a/b) and 10 (a/b).&lt;BR /&gt;&lt;BR /&gt;There are also two ProLiant BL460c G6 blades in device bay 7 and 8.&lt;BR /&gt;&lt;BR /&gt;Several interconnect bays are filled with interconnect modules. &lt;BR /&gt;&lt;BR /&gt;Interconnect Bay 1: HP 1:10Gb Ethernet Blade Switch (Ethernet)&lt;BR /&gt;Interconnect Bay 2: HP 1:10Gb Ethernet Blade Switch (Ethernet)&lt;BR /&gt;Interconnect Bay 3+4: 4X DDR IB Switch Module for HP c-Class BladeSystem (Infiniband)&lt;BR /&gt;Interconnect Bay 5: Brocade 4/12 SAN Switch for HP c-Class BladeSystem (Fibre Channel)&lt;BR /&gt;Interconnect Bay 7: Brocade 4/12 SAN Switch for HP c-Class BladeSystem&lt;BR /&gt;&lt;BR /&gt;Now, all ProLiant BL2x220c G5 blades and the Infiniband 4X DDR IB Switch Module show this error message&lt;BR /&gt;&lt;BR /&gt;"I/O mismatch detected. Please see port mapping information."&lt;BR /&gt;&lt;BR /&gt;The ProLiant BL2x220c G5 blades want the Ethernet modules in Interconnect Bay 1 and Bay 3 but this is impossible because of the width of the Infiniband module.&lt;BR /&gt;&lt;BR /&gt;What can I do at this point?&lt;BR /&gt;&lt;BR /&gt;The c7000 Onboard Administrator and all blades have all the latest firmware version.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;&amp;nbsp; &amp;nbsp; Christian</description>
      <pubDate>Wed, 28 Apr 2010 14:49:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/i-o-mismatch-port-mismatch/m-p/4625500#M10149</guid>
      <dc:creator>Christian Baun</dc:creator>
      <dc:date>2010-04-28T14:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: I/O mismatch / Port Mismatch</title>
      <link>https://community.hpe.com/t5/bladesystem-general/i-o-mismatch-port-mismatch/m-p/4625501#M10150</link>
      <description>Christian,&lt;BR /&gt;&lt;BR /&gt;you can't really workaround that issue.  the 2x220c's require ethernet modules in bays 3 and 4.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Apr 2010 15:06:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/i-o-mismatch-port-mismatch/m-p/4625501#M10150</guid>
      <dc:creator>HEM_2</dc:creator>
      <dc:date>2010-04-28T15:06:04Z</dc:date>
    </item>
    <item>
      <title>Re: I/O mismatch / Port Mismatch</title>
      <link>https://community.hpe.com/t5/bladesystem-general/i-o-mismatch-port-mismatch/m-p/4625502#M10151</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;does this mean my boss has to buy a second c7000 Enclosure for the ProLiant BL460c G6 blades and the Infiniband module? &lt;BR /&gt;&lt;BR /&gt;:-(&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;   Christian</description>
      <pubDate>Wed, 28 Apr 2010 19:56:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/i-o-mismatch-port-mismatch/m-p/4625502#M10151</guid>
      <dc:creator>Christian Baun</dc:creator>
      <dc:date>2010-04-28T19:56:22Z</dc:date>
    </item>
  </channel>
</rss>

