Go to main content

Notes de produit des serveurs de la série SPARC T7

Quitter la vue de l'impression

Mis à jour : Juin 2017
 
 

Chargement de l'image initiale du microprogramme du système


Remarque -  Le chargement de l'image du microprogramme du système peut prendre jusqu'à 15 minutes.
  1. Chargez l'image initiale du microprogramme du système. Saisissez :
    -> load -source http://<ip_address_or_hostname>/Sun_System_Firmware-9_5_2_g-SPARC_T7-4.pkg /SP/firmware
    
    NOTE: An upgrade takes several minutes to complete. ILOM
          will enter a special mode to load new firmware. No
          other tasks can be performed in ILOM until the
          firmware upgrade is complete and ILOM is reset.
    
    Are you sure you want to load the specified file (y/n)? y
    Preserve existing configuration (y/n)? y
    ..............................................................................................................................................................................................................................................................................................
    
    Firmware update is complete.
    ILOM will now be restarted with the new firmware.
    

    Une fois que l'image initiale du microprogramme du nouveau système est chargée, le SP redémarre automatiquement à partir du lecteur flash principal. Lors du redémarrage, le SP utilise les valeurs d'usine par défaut même si vous avez répondu y à la question Preserve existing configuration (y/n)?

    -> /sbin/reboot
    Stopping coredump capture...done.
    Watchdogd: Stopping patting ... Done
    Network Interface Plugging Daemon...stop eth0...done.
    Stopping kernel log daemon....
    ...
    Mounting root filesystem read-only...done.
    Will now restart.
    Restarting system.
    +****
    Primary Bootstrap.
    SYSRST     = 0x1
      Reading RO_Hw_Straps
      Searching for packages
          Good uboot CRC for data=[*000c0000, len=553b4] in pkg *0013f800 (crc: 0x44f46b65)
          Good uboot CRC for data=[*000c0000, len=80000] in pkg *00140000 (crc: 0xb0b8c9ac)
          Good kernel CRC for data=[*00142000, len=1e0de8] in pkg *00140000 (crc: 0xbf324077)
          Good root CRC for data=[*00340000, len=ef1000] in pkg *00140000 (crc: 0x5d3b8e31)
          Good vbscdir CRC for data=[*01740000, len=4c000] in pkg *00140000 (crc: 0x7a62c323)
          Good uboot CRC for data=[*018c0000, len=553b4] in pkg *0193f800 (crc: 0x2f78db1d)
          Good uboot CRC for data=[*018c0000, len=80000] in pkg *01940000 (crc: 0x97d92980)
          Good kernel CRC for data=[*01942000, len=1df2e0] in pkg *01940000 (crc: 0xf7697623)
          Good root CRC for data=[*01b40000, len=ef1000] in pkg *01940000 (crc: 0xb19fd0e5)
          Good vbscdir CRC for data=[*02f40000, len=4c000] in pkg *01940000 (crc: 0xda3cef04)
      Starting U-Boot at 0x000c0000\ufffd
    
    U-Boot 2010.03
    
    Custom Pilot3 U-Boot 0.1 (Dec  4 2015 - 11:41:49) r105871
    
    VGA buffer reserved 0x800000 bytes at 0x80000000
    sptrace allocated 0x800000 bytes at 0x9F800000
    DRAM:  496 MB
    Flash: 48 MB
    In:    serial
    Out:   serial
    Err:   serial
    
      ARM restart caused by: reboot
      hardware interface reset by: none
      Galactic1: 0x4000c900, Galactic2: 0x0
      The host is OFF(S5) (hostWantsPwr=0, powerGood=0,
    	allowPwrOn=0|0, outOfReset=0, fatalError=0).
    
    ...
    

    Le processus continue. Dans cet exemple, la section en italique indique une sortie différente de la mise à niveau de microprogramme classique. Dans ce cas, cette sortie est normale lors d'une mise à niveau du microprogramme d'une version antérieure à la version 9.5.2.g vers la version 9.5.2.g ou ultérieure.

    Loading kernel module video.
    Loading kernel module Timer.
    Mounted vbsc
    Erasing the nand ...
    Erasing 512 Kibyte @ 40000000 -- 100 % complete.
    no UBI volumes found, initializing media:
    erasing media..
    formatting media..
    UBI device number 0, total 2048 LEBs (1056964608 bytes, 1008.0 MiB), available 2024 LEBs (1044578304 bytes, 996.2 MiB), LEB size 516096 bytes (504.0 KiB)
    UBI volumes (0):
      params:	 (20.2 MB) created mounted
      persist:	 (106.3 MB) created mounted
      coredump:	 (70.4 MB) created mounted
      large:	 (64.5 MB) created mounted
      extra:	 (36.4 MB) created mounted
      package:	 (230.3 MB) created mounted
      miniroot:	 (468.1 MB) created mounted
    Available freespace: 0 MB
    
    Checking configuration files state ... 
    ... not preserving config
    ... Restoring configuration files ... 
      params:	 (20.2 MB) exists was_mounted
      persist:	 (106.3 MB) exists was_mounted
      coredump:	 (70.4 MB) exists was_mounted
      large:	 (64.5 MB) exists was_mounted
      extra:	 (36.4 MB) exists was_mounted
      package:	 (230.3 MB) exists was_mounted
      miniroot:	 (468.1 MB) exists was_mounted
    Available freespace: 0 MB
       Saving TLI data...FAILED
       Removing old configuration files
       Removing platform specific files
       Restoring default configuration files...Done
       Restoring TLI data...FAILED
    Configuration files state good
    
    1970-01-01 00:02:42 ** Error: Did not find any saved ilom package file
    sp_trace_write failed: -1
    Setting the system clock.
    System Clock set to: Mon Dec  7 18:51:52 UTC 2015.
    Initializing SP Trace Buffers
    Setting up networking....
    Will now mount local filesystems:.
    Will now activate swapfile swap:done.
    Cleaning up temporary files...Cleaning /var/run...done.
    Cleaning /var/lock...done.
    ...
    Starting ILOM Watchdog daemon.
     Done
    Running plat...Preparsing sensor.xml... ( took 12 seconds ) done
    Probing frus ...done
    Done running plat
    psnc_file_read: cannot access file '/persist/psnc_backup1.xml'
    Identifying Product Data...Backup2
    Setting poweron delay...
    Starting Dynamic FRUID Daemon early init: dynafrud_early_init  Done (0)
    INIT: Entering runlevel: 3
    Preparsing sensor.xml... ( took 1 seconds ) done
    Starting Event Manager: eventmgr  . Done
    ...
    waiting for GM ready ....GM is ready
    Starting Sppostadm:  -a Done
    
    ORACLESP-<XXXXXXXX> login: 
  2. Restaurez les propriétés réseau du SP.

    Voir la section Restauration des propriétés réseau du processeur de service.