<?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: Changing EVA Host Definition in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514362#M33019</link>
    <description>and are there any ramifications - what does the mswindows vs vmware host mode actually do?</description>
    <pubDate>Wed, 14 Oct 2009 22:13:59 GMT</pubDate>
    <dc:creator>Brad Gabrielse</dc:creator>
    <dc:date>2009-10-14T22:13:59Z</dc:date>
    <item>
      <title>Changing EVA Host Definition</title>
      <link>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514360#M33017</link>
      <description>EVA6000 Environment running XCS 6220. Customer with 4 ESX hosts sharing 25 Lun presentations.  One of four ESX hosts has OS defined as "mswindows" in host definition properties.&lt;BR /&gt;&lt;BR /&gt;How to change OS definition - is it as simple as editing to reflect "vmware", or is there a documented procedure?  Also, what ramifications of making a change back?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 14 Oct 2009 18:07:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514360#M33017</guid>
      <dc:creator>Brad Gabrielse</dc:creator>
      <dc:date>2009-10-14T18:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: Changing EVA Host Definition</title>
      <link>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514361#M33018</link>
      <description>short answer... you need to change the host mode to vmware, unpresent and represent the luns to reflect the change otherwise it will keep working in windows mode</description>
      <pubDate>Wed, 14 Oct 2009 21:56:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514361#M33018</guid>
      <dc:creator>gabbar</dc:creator>
      <dc:date>2009-10-14T21:56:04Z</dc:date>
    </item>
    <item>
      <title>Re: Changing EVA Host Definition</title>
      <link>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514362#M33019</link>
      <description>and are there any ramifications - what does the mswindows vs vmware host mode actually do?</description>
      <pubDate>Wed, 14 Oct 2009 22:13:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514362#M33019</guid>
      <dc:creator>Brad Gabrielse</dc:creator>
      <dc:date>2009-10-14T22:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: Changing EVA Host Definition</title>
      <link>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514363#M33020</link>
      <description>OS mode are set because every OS has its own SCSI Commands. So it would be helpful for the EVA to interpet if it knoww what kind of device he is dealing wiht..  if you dont set this correctly(especially for vmware) you might come up with issues like scsi reservation conflicts</description>
      <pubDate>Wed, 14 Oct 2009 22:30:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/changing-eva-host-definition/m-p/4514363#M33020</guid>
      <dc:creator>gabbar</dc:creator>
      <dc:date>2009-10-14T22:30:16Z</dc:date>
    </item>
  </channel>
</rss>

