<?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: Controller Firmware in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253138#M59816</link>
    <description>Hi,&lt;BR /&gt;As long as you use the HSV200 file you should be OK.&lt;BR /&gt;The easiest way to tell if you have a HSV200 no spec is to go to the OCP of the EVA ctrl and find the menu option that tells you about RoHS compliance. If it says "no" then it is a no spec ctrl. If it says "yes" then it is A or B spec. If A or B spec then if you look at the ctrl front bezel it should be written on there what type it is - A or B.&lt;BR /&gt;&lt;BR /&gt;However you need to read the release notes for the code and the EVA compatibility matrix info that I supplied in a different post and the info Uwe sipplied.&lt;BR /&gt;When code loading the EVA you may have to do many other things before or after like:&lt;BR /&gt;Update Command view&lt;BR /&gt;new licences&lt;BR /&gt;update mpio&lt;BR /&gt;the EVA may have to be offline for the upgrade&lt;BR /&gt;and so on. That is why you must read the release notes etc to check everything and then plan for the code load.&lt;BR /&gt;Mark...</description>
    <pubDate>Thu, 26 Aug 2010 08:28:29 GMT</pubDate>
    <dc:creator>Mark...</dc:creator>
    <dc:date>2010-08-26T08:28:29Z</dc:date>
    <item>
      <title>Controller Firmware</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253132#M59810</link>
      <description>What is the difference between &lt;BR /&gt;&lt;BR /&gt;HSV-200 and HSV-200 B</description>
      <pubDate>Wed, 25 Aug 2010 17:58:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253132#M59810</guid>
      <dc:creator>Pradeep Joy_1</dc:creator>
      <dc:date>2010-08-25T17:58:36Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Firmware</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253133#M59811</link>
      <description>HSV-200 = EVA-4000/6000 controller module, 2Gbit front-end&lt;BR /&gt;HSV-200A = EVA-4000/6000 controller module, 4Gbit front-end&lt;BR /&gt;HSV-200B = EVA-4100/6100 controller module, 4Gbit front-end</description>
      <pubDate>Wed, 25 Aug 2010 18:23:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253133#M59811</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2010-08-25T18:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Firmware</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253134#M59812</link>
      <description>Hi&lt;BR /&gt;A &amp;amp; B spec are also RoHS compliant.&lt;BR /&gt;Mark...</description>
      <pubDate>Thu, 26 Aug 2010 07:44:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253134#M59812</guid>
      <dc:creator>Mark...</dc:creator>
      <dc:date>2010-08-26T07:44:54Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Firmware</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253135#M59813</link>
      <description>is it possible to upgrade HSV-200 b firmware with HSV 200..</description>
      <pubDate>Thu, 26 Aug 2010 07:47:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253135#M59813</guid>
      <dc:creator>Pradeep Joy_1</dc:creator>
      <dc:date>2010-08-26T07:47:27Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Firmware</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253136#M59814</link>
      <description>Hi&lt;BR /&gt;They all use the same f/w but it will not alter the Host connection spped if that is what you are thinking???&lt;BR /&gt;To qualify the f/w thing:&lt;BR /&gt;HSV200 has own f/w&lt;BR /&gt;HSV210 has own f/w &lt;BR /&gt;but you use the same file for each one.&lt;BR /&gt;Mark...</description>
      <pubDate>Thu, 26 Aug 2010 07:59:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253136#M59814</guid>
      <dc:creator>Mark...</dc:creator>
      <dc:date>2010-08-26T07:59:47Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Firmware</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253137#M59815</link>
      <description>HSV 200 CR0ECAxC3P-6110&lt;BR /&gt;Dear Mark , by seeing the above firmware ver. can you advice , what is my controller model.,ie is it hsv-200 ,HSV-200a or HSV 200b&lt;BR /&gt;&lt;BR /&gt;My confusion is , i have downloaded the 6220 frimware for HSV 200, and if i up load that will it make any problem in case i have a hsv 200a or 200b controller ? please advice</description>
      <pubDate>Thu, 26 Aug 2010 08:13:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253137#M59815</guid>
      <dc:creator>Pradeep Joy_1</dc:creator>
      <dc:date>2010-08-26T08:13:33Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Firmware</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253138#M59816</link>
      <description>Hi,&lt;BR /&gt;As long as you use the HSV200 file you should be OK.&lt;BR /&gt;The easiest way to tell if you have a HSV200 no spec is to go to the OCP of the EVA ctrl and find the menu option that tells you about RoHS compliance. If it says "no" then it is a no spec ctrl. If it says "yes" then it is A or B spec. If A or B spec then if you look at the ctrl front bezel it should be written on there what type it is - A or B.&lt;BR /&gt;&lt;BR /&gt;However you need to read the release notes for the code and the EVA compatibility matrix info that I supplied in a different post and the info Uwe sipplied.&lt;BR /&gt;When code loading the EVA you may have to do many other things before or after like:&lt;BR /&gt;Update Command view&lt;BR /&gt;new licences&lt;BR /&gt;update mpio&lt;BR /&gt;the EVA may have to be offline for the upgrade&lt;BR /&gt;and so on. That is why you must read the release notes etc to check everything and then plan for the code load.&lt;BR /&gt;Mark...</description>
      <pubDate>Thu, 26 Aug 2010 08:28:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253138#M59816</guid>
      <dc:creator>Mark...</dc:creator>
      <dc:date>2010-08-26T08:28:29Z</dc:date>
    </item>
    <item>
      <title>Re: Controller Firmware</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253139#M59817</link>
      <description>Thnx for the support</description>
      <pubDate>Sat, 28 Aug 2010 17:30:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/controller-firmware/m-p/5253139#M59817</guid>
      <dc:creator>Pradeep Joy_1</dc:creator>
      <dc:date>2010-08-28T17:30:26Z</dc:date>
    </item>
  </channel>
</rss>

