4 Replies Latest reply: Jun 18, 2010 9:56 AM by 807557 RSS

    T1000 wont boot after firmware upgrade if SCA6000 is connected

    807557
      Hi guys,

      as u may have guessed from the topic, I had a T1000 server with a sun SCA6000 crypto card mounted in the PCI slot. All worked fine until i tryed to upgrade the firmware on the server to the last available release (6.7.8 with patch 139435-06 ) . After the upgrade procedure, the system did not boot anymore. This is the console output with POST after the poweron command:
      sc> poweron -c
      Enter #. to return to ALOM.
      0:0:0>
      0:0:0>Sun Fire[TM] T1000 POST 4.30.4.a 2010/01/06 15:23 
             /export/delivery/delivery/4.30/4.30.4.a/post4.30.4-micro/Niagara/erie/integrated  (root)  
      0:0:0>Copyright 2010 Sun Microsystems, Inc. All rights reserved
      0:0:0>VBSC cmp0 arg is: 0fff0fff.00000211
      0:0:0>POST enabling threads: 00000000.0fff0fff
      0:0:0>VBSC cntl arg is: 0fff0fff.00000211
      0:0:0>VBSC selecting POST MAX Testing.
      0:0:0>VBSC setting verbosity level 2
      0:0:0>Start Selftest.....
      0:0:0>Master CPU Tests Basic....Done
      0:0:0>Init MMU.....
      0:0:0>L2 Tests....Done
      0:0:0>Test Memory....Done
      0:0:0>Setup POST Mailbox ....Done
      0:0:0>Extended CPU Tests....Done
      0:0:0>Scrub Memory....Done
      0:0:0>Functional CPU Tests....Done
      0:0:0>Extended Memory Tests....Done
      0:0:0>IO-Bridge Tests....Done
      2010-06-17 17:45:02.383 0:0:0>INFO:
      2010-06-17 17:45:02.399 0:0:0>     POST Passed all devices.
      2010-06-17 17:45:02.433 0:0:0>POST:     Return to VBSC.
      2010-06-17 17:45:02.449 0:0:0>Master set ACK for vbsc runpost command and spin...
      \
      SC Alert: Host system has shut down.
      -
      SC Alert: Host System has Reset
      JUN 17 17:45:22 ERROR: HV Abort: <Unknown?> (217f14) - PowerDown
      \
      SC Alert: Host system has shut down.
      sc> 
      Guessing an hardware compatibility problem, i tried to remove the SCA6000 board and the system booted again without an hassle.

      Unluckily, I need the SCA6000, and I don't have any other server in which to mount it, so I tried to downgrade the firmware to the release I had before the upgrade:

      firmware version: 6.6.7
      patchid: 136928-05

      but the system does not boot anymore with the SCA6000 connected. I even tried an older fw release just to be sure (fw 6.6.1, patch 136928-01), with the same result.

      I did not find mention of any incompatibility in T1000 or SCA6000 documentation.

      Any help would be REALLY appreciated

      Many thanks in advance.
        • 1. Re: T1000 wont boot after firmware upgrade if SCA6000 is connected
          796238
          Hi,

          This looks similar to the bug 6630313 :: http://sunsolve.sun.com/search/document.do?assetkey=1-1-6630313-1

          As described in the bug document, it is due to lower f/w rev. on the SCA6000 and solution is to upgrade the crypto card f/w to 1.1.0 /1.1.0 (bootstrap/operational )or later.
          Another workaround would be to install system f/w 6.2.4 or 6.2.8 which works well with crypto card f/w 1.0.4/1.0.7.

          Copying relevant part of the document for ref.

          =======================
          Work Around: The card is recognized by obp and prtdiag with firmware 6.2.4, so at this point customer is using firmware 6.2.4 as workaround.

          Customer's crypto card is currently running 1.0.4/1.0.7 bootstrap/operational firmware. Customer can upgrade the card to newer firmware such as 1.1.0/1.1.0 by moving card to a system that boots successfully such as Ontario T2000. After such upgrade, install the card back into T1000 which should boot successfully with sysfw 6.4.0, 6.5.5 or 6.5.11 posted on Sunsolve.

          Another workaround is customer can downgrade the T1000 sysfw to 6.2.8 so they can boot with the crypto card. After the T1000 is up and running with sysfw 6.2.8, customer can upgrade the crypto card fw to the latest 1.0 patch on the T1000 itself, then upgrade the T1000 sysfw to the latest
          version posted on Sunsolve. This workaround does require customer to have access to an Ontario T2000 system.

          Another workaround is customer can downgrade the T1000 sysfw to 6.2.8 so they can boot with the crypto card. After the T1000 is up and running with sysfw 6.2.8, customer can upgrade the crypto card fw to the latest 1.0 patch on the T1000 itself, then upgrade the T1000 sysfw to the latest
          version posted on Sunsolve. This workaround does not require customer to have access to an Ontario T2000 system.

          ========================

          HTH

          -Mehul
          • 2. Re: T1000 wont boot after firmware upgrade if SCA6000 is connected
            807557
            Thank you for your reply,

            I can't try with fw 6.2.4 or 6.2.8 as suggested because my T1000 needs at least 6.3.1 (?):
            Username: ctassini
            Password: **********
            
            
            SC Alert: System poweron is disabled.
            ..
            ERROR: This platform only supports system firmware 6.3.1 and after.
            
            ERROR: Image not supported on this platform.
            
            Error updating software.
            By the way, bug 6630313 says that the problem appears with t1000 firmware 6.3.7 or later, so right now I'm trying to downgrade to 6.3.1 (patch 124751-02) to see if it boots...

            However I think it's quite strange that the T1000 does not boot with the same firmware it has before my first flashupdate try...
            • 3. Re: T1000 wont boot after firmware upgrade if SCA6000 is connected
              807557
              ok, that worked

              the T1000 booted with SCA6000 and firmware 6.3.1 . Now I'll try to upgrade the board firmware and re-install 6.8.2 on the T1000...
              • 4. Re: T1000 wont boot after firmware upgrade if SCA6000 is connected
                807557
                It works! ;)

                thank you very much for your support :)