Upgrade the Service Processor

Upgrade the SP at the -> prompt.

1. Log in as root.
2. Connect to the SP serial console or ssh to the SP IP address.
3. Ensure that you have a network configuration in place on the switch.
4. Use the version command to determine if the firmware version running on the SP needs to be upgraded.

   Compare the SP firmware build number to the build number in the new image.

   In ES2-72_64_SP_3.2.5.60_r109079.pkg, the build number is r109079.

5. Use TFTP, FTP, SCP, HTTP, HTTPS, SFTP, or the Oracle ILOM web interface to upgrade the SP image with the firmware image file ES2-72_64_SP_3.2.5.60_r109079.pkg.

   Answer the questions that appear on the screen as you proceed through the installation.

   The following example illustrates the upgrade process using FTP from a server with an IP address of 192.168.1.100.

   ---

   Note - The SP reboots automatically after the upgrade. The switch keeps running as normal.

   ---

   -> load -source ftp://username:password@192.168.1.100/ES2-72_64_SP_3.2.5.60_r109079.pkg
   Enter remote user password: enter password
   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.
    
    
   -> /sbin/reboot
   

6. When the SP reboots after the upgrade, verify the software build number.

   -> version
   SP firmware 3.2.5.60
   SP firmware build number: 109079 
   SP firmware date: Fri Mar  25 15:47:10 PDT 2016
   SP filesystem version: 0.2.10
   

   ---

   Note - This version allows you to explicitly set a policy to auto power on the host after a power event. If you prefer the host to power on automatically when main power is applied, set the policy as shown in the example.

   ---

   -> show /SP/policy/
    
    /SP/policy
       Targets:
    
       Properties:
           HOST_AUTO_POWER_ON = disabled
           HOST_LAST_POWER_STATE = disabled
    
   -> set /SP/policy/ HOST_AUTO_POWER_ON=enabled
   Set 'HOST_AUTO_POWER_ON' to 'enabled'
    
   -> show /SP/policy/
    
    /SP/policy
       Targets:
    
       Properties:
           HOST_AUTO_POWER_ON = enabled
           HOST_LAST_POWER_STATE = disabled