<?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: Upgrade to Secure Path 3.0C SP1 for Solaris in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220622#M5870</link>
    <description>I would wait until 3.0D, the fix is in this version.. Thanks</description>
    <pubDate>Wed, 24 Mar 2004 19:04:56 GMT</pubDate>
    <dc:creator>David Ell</dc:creator>
    <dc:date>2004-03-24T19:04:56Z</dc:date>
    <item>
      <title>Upgrade to Secure Path 3.0C SP1 for Solaris</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220618#M5866</link>
      <description>We have just upgraded to 3.0C SP1 from 3.0B SP1 on Solaris. We are getting spagent core dumps on the servers after reboot. We tried to reboot several subsequent times but that didn't make a difference. &lt;BR /&gt;&lt;BR /&gt;Has anyone run into this?</description>
      <pubDate>Tue, 16 Mar 2004 16:22:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220618#M5866</guid>
      <dc:creator>David Ell</dc:creator>
      <dc:date>2004-03-16T16:22:17Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade to Secure Path 3.0C SP1 for Solaris</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220619#M5867</link>
      <description>Hi David,&lt;BR /&gt;&lt;BR /&gt;What version  of the platform kit do you have installed?&lt;BR /&gt;&lt;BR /&gt;Craig</description>
      <pubDate>Mon, 22 Mar 2004 21:50:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220619#M5867</guid>
      <dc:creator>Craig_83</dc:creator>
      <dc:date>2004-03-22T21:50:17Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade to Secure Path 3.0C SP1 for Solaris</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220620#M5868</link>
      <description>PlatformKit 8.7B  fcraid 2.5b</description>
      <pubDate>Tue, 23 Mar 2004 09:37:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220620#M5868</guid>
      <dc:creator>David Ell</dc:creator>
      <dc:date>2004-03-23T09:37:36Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade to Secure Path 3.0C SP1 for Solaris</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220621#M5869</link>
      <description>I hear engineering is working on this issue. I was going to apply SP1 myself in a couple of weeks. Thanks for posting this information.</description>
      <pubDate>Wed, 24 Mar 2004 14:48:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220621#M5869</guid>
      <dc:creator>Craig_83</dc:creator>
      <dc:date>2004-03-24T14:48:42Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade to Secure Path 3.0C SP1 for Solaris</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220622#M5870</link>
      <description>I would wait until 3.0D, the fix is in this version.. Thanks</description>
      <pubDate>Wed, 24 Mar 2004 19:04:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/upgrade-to-secure-path-3-0c-sp1-for-solaris/m-p/3220622#M5870</guid>
      <dc:creator>David Ell</dc:creator>
      <dc:date>2004-03-24T19:04:56Z</dc:date>
    </item>
  </channel>
</rss>

