<?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: EVA4000/EVA4400 - ESXi 4.1 in Operating System - VMware</title>
    <link>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720313#M1479</link>
    <description>in Englisch:&lt;BR /&gt;i have an esxi 4.1 system witch san connection. the host is seen by the eva storage with the correct WWNs. It is configured as an vmware host in commandview eva.&lt;BR /&gt;The san zoning is correct because the server runs before as an windows 2003 system an uses the luns form san.&lt;BR /&gt;reboot or new assigning the luns did not solve the problem.&lt;BR /&gt;Hradware data:&lt;BR /&gt;Product Name: ProLiant DL360 G4p &lt;BR /&gt;Proc 1: 3000 MHz &lt;BR /&gt;HBA: 4GB HP&lt;BR /&gt;Problem: teh vmware esxi system does not see any lun presented bei eva.&lt;BR /&gt;di anyone has an idea?&lt;BR /&gt;Thanks&lt;BR /&gt;mFg&lt;BR /&gt;Frank DÃ¶lz&lt;BR /&gt;</description>
    <pubDate>Mon, 06 Dec 2010 07:03:01 GMT</pubDate>
    <dc:creator>Frank Dölz</dc:creator>
    <dc:date>2010-12-06T07:03:01Z</dc:date>
    <item>
      <title>EVA4000/EVA4400 - ESXi 4.1</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720311#M1477</link>
      <description>Hallo Leute,&lt;BR /&gt;&lt;BR /&gt;ich habe hier einen ESXi im SAN.&lt;BR /&gt;Dieser ist per FC HBA angebunden und zur EVA4000/EVA4400 gezont. Diese sieht den HOST und er ist als OS Type VMware konfiguriert.&lt;BR /&gt;Nun sieht der ESXi die LUNS nicht, auch ein reboot oder Speicher prüfen ist nicht zielführend.&lt;BR /&gt;Hat jemand einen Vorschlag?&lt;BR /&gt;Hardware:&lt;BR /&gt;Product Name: ProLiant DL360 G4p &lt;BR /&gt;Proc 1: 3000 MHz &lt;BR /&gt;HBA:  4GB HP&lt;BR /&gt;Dieser Server war vorher als Windows 2003 server an beiden EVA Systemen. Wurde als Host entfernt im Commandview und neu angelegt.&lt;BR /&gt;Keine Luns zu sehen.&lt;BR /&gt;WWNs werden korrekt an beiden EVA System gesehen.&lt;BR /&gt;Bin für jeden Hinweis dankbar.&lt;BR /&gt;MfG&lt;BR /&gt;&lt;BR /&gt;Frank Dölz</description>
      <pubDate>Wed, 01 Dec 2010 13:22:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720311#M1477</guid>
      <dc:creator>Frank Dölz</dc:creator>
      <dc:date>2010-12-01T13:22:59Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000/EVA4400 - ESXi 4.1</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720312#M1478</link>
      <description>In English please</description>
      <pubDate>Wed, 01 Dec 2010 23:29:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720312#M1478</guid>
      <dc:creator>Oscar_Maimó</dc:creator>
      <dc:date>2010-12-01T23:29:07Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000/EVA4400 - ESXi 4.1</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720313#M1479</link>
      <description>in Englisch:&lt;BR /&gt;i have an esxi 4.1 system witch san connection. the host is seen by the eva storage with the correct WWNs. It is configured as an vmware host in commandview eva.&lt;BR /&gt;The san zoning is correct because the server runs before as an windows 2003 system an uses the luns form san.&lt;BR /&gt;reboot or new assigning the luns did not solve the problem.&lt;BR /&gt;Hradware data:&lt;BR /&gt;Product Name: ProLiant DL360 G4p &lt;BR /&gt;Proc 1: 3000 MHz &lt;BR /&gt;HBA: 4GB HP&lt;BR /&gt;Problem: teh vmware esxi system does not see any lun presented bei eva.&lt;BR /&gt;di anyone has an idea?&lt;BR /&gt;Thanks&lt;BR /&gt;mFg&lt;BR /&gt;Frank DÃ¶lz&lt;BR /&gt;</description>
      <pubDate>Mon, 06 Dec 2010 07:03:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720313#M1479</guid>
      <dc:creator>Frank Dölz</dc:creator>
      <dc:date>2010-12-06T07:03:01Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000/EVA4400 - ESXi 4.1</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720314#M1480</link>
      <description>Hello,&lt;BR /&gt;first - I doubt your old server is supported on ESXi4.1&lt;BR /&gt;second - do you see HBA's under configuration of ESXi? Heva you tried to rescan them?&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Tue, 07 Dec 2010 09:13:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720314#M1480</guid>
      <dc:creator>Jan Soska</dc:creator>
      <dc:date>2010-12-07T09:13:01Z</dc:date>
    </item>
    <item>
      <title>Re: EVA4000/EVA4400 - ESXi 4.1</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720315#M1481</link>
      <description>Hello Guys,&lt;BR /&gt;the problem is solved. &lt;BR /&gt;Solution: the eva remembers all wwns, that was seen to her. So as i deletet the host, there were the wwns already seen, but in real the server has not an connection to the eva. I discovered the complete zoning configuration and there was the old zone already removed. So i set up an new zone for esxi and eva4000 and then the esxi saw the luns.&lt;BR /&gt;&lt;BR /&gt;I know that this hardware was not supported, but for our test environment it is very usefull because there is an fc hba in.&lt;BR /&gt;&lt;BR /&gt;Thanks for the help and ideas&lt;BR /&gt;&lt;BR /&gt;mFg&lt;BR /&gt;&lt;BR /&gt;Frank DÃ¶lz</description>
      <pubDate>Tue, 07 Dec 2010 13:39:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/eva4000-eva4400-esxi-4-1/m-p/4720315#M1481</guid>
      <dc:creator>Frank Dölz</dc:creator>
      <dc:date>2010-12-07T13:39:10Z</dc:date>
    </item>
  </channel>
</rss>

