<?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: Virtual Connect Firmware Failure &amp;quot;Some Server Error&amp;quot; in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152646#M15372</link>
    <description>Resolved by HP Support</description>
    <pubDate>Wed, 06 Apr 2011 00:24:20 GMT</pubDate>
    <dc:creator>IT Network Administrato</dc:creator>
    <dc:date>2011-04-06T00:24:20Z</dc:date>
    <item>
      <title>Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152633#M15359</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;When I connect to the Virtual Connect Manager on one of my C7000 Chassis, if I try to view the Local Users I receive the error "The soap response packet was unparseable. There might be a problem with the soap server."&lt;BR /&gt;&lt;BR /&gt;After talking to HP they recommended that I upgrade the firmware to version 2.01.&lt;BR /&gt;So, in order to do that I had to upgrade the Onboard Administrator Firmware, and before I could do that, I had to upgrade the System ROM on all of the blade servers.&lt;BR /&gt;&lt;BR /&gt;After finally get all the pre-requisites done, I tried to upgrade the firmware on the Virtual Connect.&lt;BR /&gt;&lt;BR /&gt;After sitting there for 5-10 mins "uploading local firmware image", I then get the error "Some Server Error" (yep, such a descriptive error).&lt;BR /&gt;&lt;BR /&gt;I've looked through the System Log but found nothing, and HP Tech Support doesn't have anything I can try.&lt;BR /&gt;&lt;BR /&gt;Has anyone ever seen this error before or found a way around it?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Chris</description>
      <pubDate>Mon, 26 Jan 2009 21:53:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152633#M15359</guid>
      <dc:creator>IT Network Administrato</dc:creator>
      <dc:date>2009-01-26T21:53:01Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152634#M15360</link>
      <description>Try clearing the browser cache.</description>
      <pubDate>Mon, 26 Jan 2009 23:19:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152634#M15360</guid>
      <dc:creator>Ken Henault</dc:creator>
      <dc:date>2009-01-26T23:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152635#M15361</link>
      <description>Hi Ken, thanks for the tip. I cleared the cache (cookies, temporary files, etc) and I'm still receiving the same error.&lt;BR /&gt;&lt;BR /&gt;I've tried the firmware update on a second C7000 enclouse I have and receive the same error.</description>
      <pubDate>Mon, 26 Jan 2009 23:30:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152635#M15361</guid>
      <dc:creator>IT Network Administrato</dc:creator>
      <dc:date>2009-01-26T23:30:52Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152636#M15362</link>
      <description>Check the pre-reqs in the document called&lt;BR /&gt;"HP BladeSystem c-Class Virtual Connect Support Utility Version 1.3.2 User Guide"</description>
      <pubDate>Tue, 27 Jan 2009 11:43:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152636#M15362</guid>
      <dc:creator>Adrian Clint</dc:creator>
      <dc:date>2009-01-27T11:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152637#M15363</link>
      <description>Hi Chris&lt;BR /&gt;&lt;BR /&gt;Ive seen the same error on one enclosure.&lt;BR /&gt;&lt;BR /&gt;In the end i reset the active VCM module, waited 20mins and all was ok.&lt;BR /&gt;&lt;BR /&gt;One thing i would say is definitely use the Virtual Connect Support Utility to upgrade the software rather than using the VCM itself, seems to be a lot quicker and more reliable and it report any errors prior to upgrade.&lt;BR /&gt;&lt;BR /&gt;Rgds&lt;BR /&gt;&lt;BR /&gt;Mark</description>
      <pubDate>Tue, 27 Jan 2009 14:42:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152637#M15363</guid>
      <dc:creator>MarkE_2</dc:creator>
      <dc:date>2009-01-27T14:42:47Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152638#M15364</link>
      <description>My previous experience of SOAP errors.&lt;BR /&gt;&lt;BR /&gt;Go away and have a bath ... come back and restart the browser.. it will be ok.</description>
      <pubDate>Tue, 27 Jan 2009 16:36:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152638#M15364</guid>
      <dc:creator>Adrian Clint</dc:creator>
      <dc:date>2009-01-27T16:36:40Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152639#M15365</link>
      <description>Hey guys,&lt;BR /&gt;&lt;BR /&gt;I tried using the Virtual Connect Support Utility, using the -report option to check that the firmware will work. However, this failed stating: "Initializing, 28% complete...ERROR: Initialization process failed. Firmware update cannot continue."&lt;BR /&gt;&lt;BR /&gt;I have a second C7000 and I've tried to do the same on it and get the exact same results.&lt;BR /&gt;&lt;BR /&gt;I spent about an hour this morning go through each Compatibility Matrix and ensuring I have the correct System ROMs, Mezzanine ROMs, Fibre Switch Firmware, etc, and everything is listed as being supported by this firmware.</description>
      <pubDate>Wed, 28 Jan 2009 03:59:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152639#M15365</guid>
      <dc:creator>IT Network Administrato</dc:creator>
      <dc:date>2009-01-28T03:59:48Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152640#M15366</link>
      <description>Ive seen this as well, again resetting the module that needed upgrading fixed the issue.</description>
      <pubDate>Wed, 28 Jan 2009 11:53:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152640#M15366</guid>
      <dc:creator>MarkE_2</dc:creator>
      <dc:date>2009-01-28T11:53:15Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152641#M15367</link>
      <description>Sorry, I thought I'd mentioned this.&lt;BR /&gt;&lt;BR /&gt;Over the weekend we had an entire site outage, so all power was completely removed from the Blade Enclosure (effectively the same as a reset).&lt;BR /&gt;&lt;BR /&gt;We also, just to be sure, removed all of the Virtual Connect Modules and reinserted them.&lt;BR /&gt;&lt;BR /&gt;Chris</description>
      <pubDate>Wed, 28 Jan 2009 22:13:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152641#M15367</guid>
      <dc:creator>IT Network Administrato</dc:creator>
      <dc:date>2009-01-28T22:13:59Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152642#M15368</link>
      <description>The last option for us (we had the same issue) was having HP to replace the module.</description>
      <pubDate>Mon, 09 Feb 2009 10:09:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152642#M15368</guid>
      <dc:creator>carlosgu</dc:creator>
      <dc:date>2009-02-09T10:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152643#M15369</link>
      <description>&lt;!--!*#--&gt;Chris,&lt;BR /&gt;&lt;BR /&gt;Just curious, what VC firmware version did you have installed when you tried to update it?&lt;BR /&gt;&lt;BR /&gt;Also, you should try to update the firmware using the command line interface (CLI) of the VC manager.  You can login via SSH, and then enter a command like this:&lt;BR /&gt;&lt;BR /&gt;update firmware URL=http://&lt;IP&gt;/vcfw134.bin&lt;BR /&gt;&lt;BR /&gt;where &lt;IP&gt; is a local webserver on your network.  The process will take a while, but it will show you status along the way.  Also, I recommend that you access the VCM through the OA CLI, using the "connect interconnect &lt;BAY number=""&gt;" command.  That will keep you connected to the VCM console throughout the upgrade and its reboot process.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;John&lt;/BAY&gt;&lt;/IP&gt;&lt;/IP&gt;</description>
      <pubDate>Wed, 11 Mar 2009 13:42:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152643#M15369</guid>
      <dc:creator>John Cagle</dc:creator>
      <dc:date>2009-03-11T13:42:50Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152644#M15370</link>
      <description>saw this today attempting to upgrade to 2.01.&lt;BR /&gt;&lt;BR /&gt;tried cli and vcutil but got same problem turned out one of my fc modules had got knacked and wasnt displaying an address in ebipa.&lt;BR /&gt;&lt;BR /&gt;bounced the fc module and did an auto update via the gui and all worked fine.</description>
      <pubDate>Wed, 11 Mar 2009 15:54:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152644#M15370</guid>
      <dc:creator>cjb_1</dc:creator>
      <dc:date>2009-03-11T15:54:31Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152645#M15371</link>
      <description>Hi John,&lt;BR /&gt;&lt;BR /&gt;Thanks so much for your help. Using the CLI (connecting to the OA and then to the VCM) I was able to update the firmware on the VC-Enet Modules and the VC-FC Modules to 2.01 and 1.20 respectively.&lt;BR /&gt;&lt;BR /&gt;Hopefully HP can now help me troubleshoot this further.&lt;BR /&gt;&lt;BR /&gt;Thanks so much!&lt;BR /&gt;&lt;BR /&gt;Chris&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 11 Mar 2009 22:00:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152645#M15371</guid>
      <dc:creator>IT Network Administrato</dc:creator>
      <dc:date>2009-03-11T22:00:27Z</dc:date>
    </item>
    <item>
      <title>Re: Virtual Connect Firmware Failure "Some Server Error"</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152646#M15372</link>
      <description>Resolved by HP Support</description>
      <pubDate>Wed, 06 Apr 2011 00:24:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connect-firmware-failure-quot-some-server-error-quot/m-p/5152646#M15372</guid>
      <dc:creator>IT Network Administrato</dc:creator>
      <dc:date>2011-04-06T00:24:20Z</dc:date>
    </item>
  </channel>
</rss>

