Chapter 4 Managed Server Firmware Problems

This chapter lists problems that can occur with manageable server firmware, their causes, and the solution for each problem. The following topics are discussed:

• Cannot Determine the Firmware Version on a Managed Server

• Exception Occurs When Updating Sun Fire V20z Firmware

• Firmware Update for a Sun Fire V20z or Sun Fire V40z Fails

Cannot Determine the Firmware Version on a Managed Server

If the firmware version cannot be reported by the N1 System Manager, one or all of the following situations might be the cause:

• The IP address of the manageable server's management processor has not been set, and thus the server cannot be discovered.

  Check whether the management processor IP address has been set. If it has been set, see whether it is accessible by the N1 System Manager.

  If the management processor IP address is not correct, assign an IP address to the processor as described in the hardware documentation.

  If the IP address is correct, go to the next item in this list.

• The manageable server's management processor account credentials (login account and password) are not recognized by the N1 System Manager.

  Check the credentials used by the N1 System Manager, and then try accessing the manageable server's management processor account. For information about the processor accounts, see SPARC Architecture Manageable Server Credentials in Sun N1 System Manager 1.3 Site Preparation Guide and x86 Architecture Manageable Server Credentials in Sun N1 System Manager 1.3 Site Preparation Guide.

  If you cannot access the management processor, reset the manageable server to the factory defaults as described in the hardware documentation, and reassign an IP address to the manageable server's management processor. When you have completed resetting the manageable server, run discovery on the server as described in SP-Based Discovery in Sun N1 System Manager 1.3 Discovery and Administration Guide.

  If discovery is successful, verify the managed server's firmware version as described in To List the Firmware Updates Installed on a Managed Server in Sun N1 System Manager 1.3 Operating System Provisioning Guide.

  If the firmware version still cannot be reported by the N1 System Manager, manually check the managed server's firmware by logging into the service processor on the managed server and running a specific service processor command as described in the server's hardware documentation. For example, to view all of the firmware for an ALOM-enabled server, log in to the service processor and type the following command:

  showsc version -v Advanced Lights Out Manager v1.5.3 SC Firmware version: 1.5.3 SC Bootmon version: 1.5.3 SC Bootmon Build Release: 02 SC bootmon checksum: 4F888E28 SC Bootmon built Jan 6 2005, 17:05:24 SC Build Release: 02 SC firmware checksum: 6FFB200D SC firmware built Jan 6 2005, 17:05:12 SC firmware flashupdate MAY 25 2005, 01:33:55 SC System Memory Size: 8 MB SC NVRAM Version = b SC hardware type: 0

  Compare the service processor firmware versions to the supported firmware versions. See Manageable Server Firmware Requirements in Sun N1 System Manager 1.3 Site Preparation Guide, and update the firmware to a supported version as described in the hardware documentation.

Exception Occurs When Updating Sun Fire V20z Firmware

Starting with Sun Fire V20z Firmware Version 2.2, the firmware versions do not support the PIC firmware upgrade. The upgrade of PIC firmware will fail, and the job step will show the following error message.

An exception occurred trying to update SP-IPaddress. 
Please refer to the log file for more information.

When updating Sun Fire V20z firmware, do not load PIC firmware to the Sun Fire V20z servers.

Firmware Update for a Sun Fire V20z or Sun Fire V40z Fails

If the Auto-negotiate link speed feature on the management network switch has not been enabled for all management network connections, V20z and V40z firmware updates will fail. Refer to your switch documentation and enable the auto-negotiate link speed feature.