<?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: Strange Failover Issue in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150071#M2158</link>
    <description>&lt;BR /&gt;This is on a c7000 enclosure, under 1 year in age, so the warranty is good.&lt;BR /&gt;&lt;BR /&gt;I'm think of swapping the OA's around, so OA in bay one is placed in to bay 2 etc, to see if the problem reverses.&lt;BR /&gt;&lt;BR /&gt;Julian.</description>
    <pubDate>Wed, 27 Feb 2008 10:24:23 GMT</pubDate>
    <dc:creator>Julian Stenning</dc:creator>
    <dc:date>2008-02-27T10:24:23Z</dc:date>
    <item>
      <title>Strange Failover Issue</title>
      <link>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150067#M2154</link>
      <description>I have two OA's, using firmware 2.12 and two VC enet modules using firmware 1.22 (in bays one and two).&lt;BR /&gt;&lt;BR /&gt;If I set my OA1 as the active OA, the VC modules complain with 'one or more of a domain's subsystems are not properly operating, causing a slgith impact to domain functions'. Making OA2 active again resolves all alerts.&lt;BR /&gt;&lt;BR /&gt;If OA1 is left as the active OA, the blades in the enclosure will loose their network connectivity after a while.&lt;BR /&gt;&lt;BR /&gt;Any ideas on how to resolve this? I'd like to get my OA's redundant again.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Julian.&lt;BR /&gt;</description>
      <pubDate>Mon, 25 Feb 2008 16:29:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150067#M2154</guid>
      <dc:creator>Julian Stenning</dc:creator>
      <dc:date>2008-02-25T16:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: Strange Failover Issue</title>
      <link>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150068#M2155</link>
      <description>Have you tried to upgrade the firmware on both OA.</description>
      <pubDate>Wed, 27 Feb 2008 10:09:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150068#M2155</guid>
      <dc:creator>Tavrez_1</dc:creator>
      <dc:date>2008-02-27T10:09:04Z</dc:date>
    </item>
    <item>
      <title>Re: Strange Failover Issue</title>
      <link>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150069#M2156</link>
      <description>Yes, both OA's are running the same version of firmware and flash without problems.&lt;BR /&gt;&lt;BR /&gt;Julian.</description>
      <pubDate>Wed, 27 Feb 2008 10:10:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150069#M2156</guid>
      <dc:creator>Julian Stenning</dc:creator>
      <dc:date>2008-02-27T10:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: Strange Failover Issue</title>
      <link>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150070#M2157</link>
      <description>Which classs blade server is this c3000 or c7000,i have some notes on OA but not right now. I can go through this and have a look.Is the OA1 mulfuntioning. Is it under warranty period.</description>
      <pubDate>Wed, 27 Feb 2008 10:19:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150070#M2157</guid>
      <dc:creator>Tavrez_1</dc:creator>
      <dc:date>2008-02-27T10:19:03Z</dc:date>
    </item>
    <item>
      <title>Re: Strange Failover Issue</title>
      <link>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150071#M2158</link>
      <description>&lt;BR /&gt;This is on a c7000 enclosure, under 1 year in age, so the warranty is good.&lt;BR /&gt;&lt;BR /&gt;I'm think of swapping the OA's around, so OA in bay one is placed in to bay 2 etc, to see if the problem reverses.&lt;BR /&gt;&lt;BR /&gt;Julian.</description>
      <pubDate>Wed, 27 Feb 2008 10:24:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150071#M2158</guid>
      <dc:creator>Julian Stenning</dc:creator>
      <dc:date>2008-02-27T10:24:23Z</dc:date>
    </item>
    <item>
      <title>Re: Strange Failover Issue</title>
      <link>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150072#M2159</link>
      <description>Any luck with the OAs&lt;BR /&gt;Try this link &lt;A href="http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00291270/c00291270.pdf" target="_blank"&gt;http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00291270/c00291270.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You can the call with HP since its under warranty.</description>
      <pubDate>Mon, 03 Mar 2008 09:12:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/strange-failover-issue/m-p/4150072#M2159</guid>
      <dc:creator>Tavrez_1</dc:creator>
      <dc:date>2008-03-03T09:12:15Z</dc:date>
    </item>
  </channel>
</rss>

