<?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 Could not access MSA2000 Web interface in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357006#M35951</link>
    <description>I could no longer access the web interface of my msa2000 from both controllers.  This happened after an HP Engineer replaced a drive on channel 0, id 4, encl 0, slot 4.&lt;BR /&gt;Hours before and after the drive was replaced, the engineer could still access the web interface but supposedly, from one controller only.  Now, I totally have no access to the web interface from any of the controllers.  I also don't receive email alerts or notifications from the device anymore.&lt;BR /&gt;Both controllers would reply though from ping requests and telnet.  I have tried accessing the web interface from almost all the available workstations with Java 6.x installed to no avail.</description>
    <pubDate>Thu, 12 Feb 2009 03:03:28 GMT</pubDate>
    <dc:creator>joel m. salamanca</dc:creator>
    <dc:date>2009-02-12T03:03:28Z</dc:date>
    <item>
      <title>Could not access MSA2000 Web interface</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357006#M35951</link>
      <description>I could no longer access the web interface of my msa2000 from both controllers.  This happened after an HP Engineer replaced a drive on channel 0, id 4, encl 0, slot 4.&lt;BR /&gt;Hours before and after the drive was replaced, the engineer could still access the web interface but supposedly, from one controller only.  Now, I totally have no access to the web interface from any of the controllers.  I also don't receive email alerts or notifications from the device anymore.&lt;BR /&gt;Both controllers would reply though from ping requests and telnet.  I have tried accessing the web interface from almost all the available workstations with Java 6.x installed to no avail.</description>
      <pubDate>Thu, 12 Feb 2009 03:03:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357006#M35951</guid>
      <dc:creator>joel m. salamanca</dc:creator>
      <dc:date>2009-02-12T03:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: Could not access MSA2000 Web interface</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357007#M35952</link>
      <description>Hi Joel&lt;BR /&gt;&lt;BR /&gt;Have you tried connecting to the controllers though a serial cable and restarting the controllers.  Baud Rate is 115,200&lt;BR /&gt;&lt;BR /&gt;Restart mc a&lt;BR /&gt;&lt;BR /&gt;Restart mc b</description>
      <pubDate>Wed, 25 Feb 2009 11:19:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357007#M35952</guid>
      <dc:creator>RM782</dc:creator>
      <dc:date>2009-02-25T11:19:18Z</dc:date>
    </item>
    <item>
      <title>Re: Could not access MSA2000 Web interface</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357008#M35953</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I've the same issue and stupidly just started another thread...&lt;BR /&gt;&lt;BR /&gt;Will restarting the controllers cause servers taht are connected to the SAN to lose their connection? Presumably it will be OK if I do one, wait for it to restart, and then do the other?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 26 Feb 2009 14:40:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357008#M35953</guid>
      <dc:creator>David Eagle</dc:creator>
      <dc:date>2009-02-26T14:40:42Z</dc:date>
    </item>
    <item>
      <title>Re: Could not access MSA2000 Web interface</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357009#M35954</link>
      <description>RM782 - I used telnet to access my MSA and restarted both controllers, I can now access the management correctly via my browser.&lt;BR /&gt;&lt;BR /&gt;If you post you solution to my thread I'll assign you some points.&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1317958" target="_blank"&gt;http://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1317958&lt;/A&gt;</description>
      <pubDate>Thu, 26 Feb 2009 15:28:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357009#M35954</guid>
      <dc:creator>David Eagle</dc:creator>
      <dc:date>2009-02-26T15:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: Could not access MSA2000 Web interface</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357010#M35955</link>
      <description>Guys, &lt;BR /&gt;Thanks for info.&lt;BR /&gt;&lt;BR /&gt;Anyway, my issue had already been resolved as I submitted a trouble ticket also to our local HP Support Center.&lt;BR /&gt;&lt;BR /&gt;The problem was corrected after we upgraded the controllers' firmware.&lt;BR /&gt;&lt;BR /&gt;My issues actually started when one of the disks failed and had to be replaced.  A few hours after the disk replacement, I couldn't access the SMU anymore. 'Glad its back to its normal condition again.&lt;BR /&gt;&lt;BR /&gt;Thanks again</description>
      <pubDate>Fri, 27 Feb 2009 02:08:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/could-not-access-msa2000-web-interface/m-p/4357010#M35955</guid>
      <dc:creator>joel m. salamanca</dc:creator>
      <dc:date>2009-02-27T02:08:19Z</dc:date>
    </item>
  </channel>
</rss>

