This post describes how to select the firmware, the firmware upgrade method and upgrade the system firmware on Sun Fire  T1000 and Sun Fire  T2000 server

Firmware Verification

1. To determine the current System Firmware revision installed on the system, from the System Controller command-line interface (CLI) use the output from the following commands:

From the ‘showhost’ output, find the version of  System Firmware and the versions of the following firmware components:

-Hypervisor

-OBP

-Integrated POST

Example:

sc> showhost

System Firmware 6.2.6 Sun Fire[TM] T2000 2006/10/06 12:36

Host flash versions:

Hypervisor 1.2.3 2006/08/18 12:25

OBP 4.23.4 2006/08/04 20:46

Sun Fire[TM] T2000 POST 4.23.4 2006/08/04 21:15

From the “showsc version -v” output, find the versions of

-Advanced Lights Out Manager CMT (ALOM-CMT)

-vBSC

Example:  sc> showsc version -v Advanced Lights Out Manager CMT v1.2.6 SC Firmware version: CMT 1.2.5 SC Bootmon version: CMT 1.2.5 VBSC 1.2.4 VBSC firmware built Aug 18 2006, 12:27:38………………………….

2. Compare the current System Firmware revision with the latest available revision, which can be obtained from the latest FW patch install.info file. If the ‘showhost’ command doesn’t provide the System Firmware revision (this may happen on some systems), you may need to compare the versions of the separate firmware components, which are also available from the patch install.info file:

System Firmware 6.2.6 Sun Fire[TM] T2000 2006/10/06

ALOM-CMT v1.2.6  Oct  6 2006  12:33:12

VBSC 1.2.4  Aug 18 2006  12:27:38

Hypervisor 1.2.3 2006/08/18 12:25

OBP 4.23.4 2006/08/04 20:46

Sun Fire[TM] T2000 POST 4.23.4 2006/08/04

3. In case your firmware revision is lower that the latest version available, proceed to upgrading the system firmware in order to get the latest fixes and avoid known issues. The firmware versions in step 2 & 3 are only examples, the latest firmware can be found on MOS, Patches & Updates (for example System Firmware 6.7.11, patch 139434-08).

NOTE: When upgrading the firmware make sure that the system is running a compatible OS version, otherwise you may have boot or other problems. Use the patch README to verify what is the supported (compatible) OS  for this firmware version, for example

Upgrading to Sun System Firmware 6.2.4 (or later) requires Solaris[TM] 10 Update 1 (or later) to be installed. The system may experience boot or other problems with earlier version of Solaris

Updating the Firmware

The flashupdate command updates both the ALOM-CMT System Controller firmware and the host firmware. To use the features and fixes in subsequent firmware releases, perform this procedure.

To Update the Firmware

1. Ensure that the ALOM-CMT System Controller network management port is configured.  This is required to access the new flash image over the network.

2. Open a Telnet or SSH session and connect to the system controller. The following example is for Telnet.

% telnet xxx.xxx.xx.xx   Trying xxx.xxx.xx.xx… Connected to xxx.xxx.xx.xx. Escape character is’^]’. Copyright 2006 Sun Microsystems, Inc.  All rights reserved. Use is subject to license terms. Sun(tm) Advanced Lights Out Manager CMT v1.2 Please login:

3. Login as admin, using the password you defined during the configuration of the system controller.

Please login: admin   Please Enter password: password sc>

4. Execute the flashupdate command.

The flashupdate SC command updates the system controller flash image and the host firmware. The flashupdate command requires the following information:

• IP address of an FTP server on the network that can access the flash image.
• Full path name to the flash image that the IP address can access.
• Username and password of an account registered on the system that is specified by the IP address.

The command usage is as follows:

flashupdate [-s IPaddr -f pathname] [-v]

where:

• -sIPaddr is the IP address of any FTP server on the network that can access the flash image
• -fpathname is the full path name to the flash image
• -v is the flag to turn on verbose message output

sc> flashupdate -s xxx.xxx.xx.xx -f pathname   Username: username Password: password ……………………………………………………… . Update complete. Reset device to use new image. sc>

5. Reset the system controller.

After the flash has been updated, you must reset the system controller for the new image to take affect. To reset the system controller, issue the resetsc command, as shown below.

Note – To bypass the confirmation prompt, you can use the -y flag with the resetsc command. If resetsc is issued from a Telnet or SSH session, upon reset the Telnet or SSH session will be terminated. The output from the reset will be displayed on the serial console on the system controller.

 

sc> resetsc   Are you sure you want to reset the SC [y/n]? y User Requested SC Shutdown

The system controller resets, runs diagnostics, and returns to the login prompt (on the serial console).

CODE EXAMPLE A-1 Boot Sequence Example ALOM BOOTMON v1.2.0   ALOM Build Release: 000 Reset register: f0000000 EHRS ESRS LLRS SWRS ALOM POST 1.0 Dual Port Memory Test, PASSED. TTY External – Internal Loopback Test TTY External – Internal Loopback Test, PASSED. TTYC – Internal Loopback Test TTYC – Internal Loopback Test, PASSED. … ETHERNET CPU LOOPBACK TEST, PASSED Full VxDiag Tests – PASSED Status summary  -  Status = 7FFF VxDiag    -          -  PASSED POST      -          -  PASSED LOOPBACK  -          -  PASSED I2C       -          -  PASSED EPROM     -          -  PASSED FRU PROM  -          -  PASSED ETHERNET  -          -  PASSED MAIN CRC  -          -  PASSED BOOT CRC  -          -  PASSED TTYD      -          -  PASSED TTYC      -          -  PASSED MEMORY    -          -  PASSED MPC885    -          -  PASSED sc>

To Configure the System Controller Network Management Port

Note – If your network allows the use of DHCP and SSH, this configuration is performed automatically at the first time you boot the system.

Use this procedure only if:

• If you are unable to use DHCP and SSH on your network.
• If you need to modify the SC network management port settings.

In this procedure you connect to the ALOM-CMT System Controller using the serial management port to manually reconfigure the network management port.

Note – For more information on configuring ALOM-CMT, refer to the Advanced Lights Out Management (ALOM) CMT Guide.

You set these network parameters according to the specific details of your network configuration:

• if_network – Specifies whether the SC is on the network or not
• netsc_ipaddr – IP address of the system controller
• netsc_ipgateway – IP address of the gateway for the subnet
• netsc_ipnetmask – Netmask for the system controller subnet

To configure these parameters, use the setsc command. The usage is:

sc> setscparameter

1. Set the if_network parameter to true.

sc> setsc if_network true

2. Set the if_connection parameter to the connection type, either telnet or ssh.

 

sc> setsc if_connection value

where the value can be one of the following:

• none
• telnet
• ssh
• netsc_dhcp (The system controller obtains its network interface configuration through a DHCP server.)

See the ALOM-CMT v1.2 guide for more information about SSH support in ALOM-CMT.

3. Choose one of these methods to configure the system controller using information from your network administrator:

• Use DHCP to retrieve the network settings. Go to Step 4.
• Configure a static IP configuration. Go to Step 5.

4. If you choose to use DHCP, set netsc_dhcp to true.

sc> setsc netsc_dhcp true

Go to Step 6.

5. If you choose to use a static IP configuration, set the parameters netsc_ipaddr, netsc_ipgateway, and netsc_ipnetmask, as follows.

a. Set the IP address for the system controller.

sc> setsc netsc_ipaddr service-processor-IPaddr

b. Set the IP address for the system controller gateway.

sc> setsc netsc_ipgateway gateway-IPaddr

c. Set the netmask for the system controller.

sc> setsc netsc_ipnetmask 255.255.255.0

This example uses 255.255.255.0 to set the netmask. Your network environment subnet might require a different netmask. Use a netmask number most appropriate to your environment.

6. Use the showsc command to verify that the parameters were set correctly.

sc> showsc   Advanced Lights Out Manager CMT v1.2 parameter                value ———                —– if_network               true if_connection            ssh if_emailalerts           false netsc_dhcp               true netsc_ipaddr             xxx.xxx.xxx.xxx netsc_ipnetmask          255.255.255.0 netsc_ipgateway          0.0.0.0 mgt_mailhost mgt_mailalert sc_customerinfo sc_escapechars           #. sc_powerondelay          false sc_powerstatememory      false sc_clipasswdecho         true sc_cliprompt             sc sc_clitimeout            0 sc_clieventlevel         2 sc_backupuserdata        true diag_trigger             power-on-reset error-reset diag_verbosity           normal diag_level               max diag_mode                normal sys_autorunonerror       false ser_baudrate             9600 ser_parity               none ser_stopbits             1 ser_data                 8 netsc_enetaddr           xx:xx:xx:xx:xx:xx sys_enetaddr             yy:yy:yy:yy:yy:yy

 

 

Note – After setting the configuration parameters, you must reset the system controller for the new values to take affect.

 

To Reset the System Controller

 

Issue the resetsc command.

You are prompted to confirm that you want to reset the system controller. Type y when prompted.

sc> resetsc   Are you sure you want to reset the SC [y/n]? y User Requested SC Shutdown

Note – To bypass the confirmation message, specify the -y flag to the resetsc command

The system controller resets, runs diagnostics, and returns to the login prompt.

ALOM POST 1.0   Dual Port Memory Test, PASSED. TTY External – Internal Loopback Test TTY External – Internal Loopback Test, PASSED. TTYC – Internal Loopback Test TTYC – Internal Loopback Test, PASSED. TTYD – Internal Loopback Test TTYD – Internal Loopback Test, PASSED. ……………….. Full VxDiag Tests – PASSED Status summary  -  Status = 7FFF VxDiag    -          -  PASSED POST      -          -  PASSED LOOPBACK  -          -  PASSED I2C       -          -  PASSED EPROM     -          -  PASSED FRU PROM  -          -  PASSED ETHERNET  -          -  PASSED MAIN CRC  -          -  PASSED BOOT CRC  -          -  PASSED TTYD      -          -  PASSED TTYC      -          -  PASSED MEMORY    -          -  PASSED MPC885    -          -  PASSED Please login:

Using the ALOM-CMT System Controller for Common Operations

Note – For more information on using ALOM-CMT, refer to the Advanced Lights Out Management (ALOM) CMT Guide.

To Initiate the Power On Sequence

Powering on the system requires you to use the poweron command at the SC console.

To initiate the power-on sequence, issue the poweron command.

You see an sc> alert message on the system console. This indicates that the system has reset.

sc> poweron   SC Alert: Host System has Reset sc>

 

To Connect to the System Console

 

Output from POST, OpenBoot, and the Solaris OS is displayed in the system console using the console command on the system controller.

Execute the console command, and use the -f option to force the console to be attached to your session.

Multiple users can be connected to the console, but only one can be attached.

 

 

sc> console -f   #. (Enter #. to return to ALOM)

Example of a Normal System Initialization

After you issue the poweron command, the CPU and memory controllers initialize and eventually OpenBoot initializes. After a number of system messages, the ok prompt appears.

The example output below is a small section of the complete output.

et5-sc> poweron -c   Enter #. to return to ALOM SC Alert: Host System has Reset 0:0> 0:0>@(#) ERIE Integrated POST 4.x.0.build_12-erie 2005/06/14 12:19 /export/common-source/firmware_re/ontario-fireball_fio/build_12/erie-build_12/post/Niagara/erie/integrated  (firmware_re) 0:0>Copyright © 2005 Sun Microsystems, Inc. All rights reserved SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms. 0:0>VBSC selecting POST MAX Testing. 0:0>VBSC enabling L2 Cache. 0:0>VBSC enabling Full Memory Scrub. ……………….. Find dropin, Copying Done, Size 0000.0000.0000.1110 Find dropin, (copied), Decompressing Done, Size 0000.0000.0006.06e0 ^Qcpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu cpu vpci mem32base, mem64base, cfgbase: e800000000 e000000000 e900000000 pci /pci@780: Device 0 pci pci /pci@780/pci@0: Device 0 Nothing there /pci@780/pci@0: Device 1 pci pci ……………….. /pci@7c0/pci@0: Device a Nothing there /pci@7c0/pci@0: Device b Nothing there /pci@7c0/pci@0: Device c Nothing there /pci@7c0/pci@0: Device d Nothing there /pci@7c0/pci@0: Device e Nothing there /pci@7c0/pci@0: Device f Nothing there Probing I/O buses Sun Fire T1000, No Keyboard Copyright 1998-2004 Sun Microsystems, Inc.  All rights reserved. OpenBoot FW build_11***PROTOTYPE_BUILD***, 16376 MB memory installed, Serial #51454515. [firmware obp4.x #0] Ethernet address 0:3:ba:ce:a1:3d, Host ID: 83112233. {0} ok

To understand the various devices and their path names as represented in the OpenBoot device tree, The below table identifies each of the devices, their full path name, and their location or NAC name used to identify their physical location.

TABLE 3-1 Sun Fire T1000 Device List
Identifier	Device	Device Path (Location)
MB/CMP0/Pn	cpun	/cpu@n, where n = {0..31}
MB/CMP0/CH0/R0/D0	dimm0	(CH0/R0/D0/J0501)
MB/CMP0/CH0/R0/D1	dimm1	(CH0/R0/D1/J0601)
MB/CMP0/CH0/R1/D0	dimm2	(CH0/R1/D0/J0701)
MB/CMP0/CH0/R1/D1	dimm3	(CH0/R1/D1/J0801)
MB/CMP0/CH3/R0/D0	dimm4	(CH1/R0/D0/J1001)
MB/CMP0/CH3/R0/D1	dimm5	(CH1/R0/D1/J1101)
MB/CMP0/CH3/R1/D0	dimm6	(CH1/R1/D0/J1201)
MB/CMP0/CH3/R1/D1	dimm7	(CH1/R1/D1/J1301)
MB/PCIEb	pci0	/pci@780
MB/PCIEb	pci1	/pci@7c0
PCIE0	slot0	/pci@780/pci@0
MB/GBE0	net0 net1	/pci@7c0/pci@0/network@4 /pci@7c0/pci@0/network@4,1
MB/GBE1	net2 net3	/pci@7c0/pci@0/pci@8/network@1 /pci@7c0/pci@0/pci@8/network@1,1
MB/HBA	SCSI	/pci@7c0/pci@0/pci@8/scsi@2

Booting the Solaris Operating System

The Solaris OS is preinstalled on the disk drive (for Sun Fire T1000 configurations that include a hard drive). The Solaris OS is not configured. If you boot the system from this drive, you will be prompted to configure the Solaris OS for your environment.

To Boot the Solaris Operating System

Type the boot command at the ok prompt.

You must append a target to the disk path. For example, the target can be disk0 or a device or network path.

In the following example, the system is booted from disk 0 (zero).

ok boot disk0   Boot device: /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0 File and args: Notice: Unimplemented procedure ‘encode-unit’ in /pci@7c0/pci@0/pci@2/pci@0/LSILogic,sas@4 Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54. FCode UFS Reader 1.12 00/07/17 15:48:16. Loading: /platform/SUNW,Ontario/ufsboot Loading: /platform/sun4v/ufsboot ……………….. Hostname: wgs94-181 The system is coming up. Please wait. NIS domain name is Ecd.East.Sun.COM starting rpc services: rpcbind keyserv ypbind done. Setting netmask of lo0 to 255.0.0.0 Setting netmask of bge0 to 255.255.255.0 Setting default IPv4 interface for multicast: add net 224.0/4: gateway wgs94-181 syslog service starting. volume management starting. Creating new rsa public/private host key pair Creating new dsa public/private host key pair The system is ready. wgs94-181 console login:

 

(Optional) To Reset the System

 

If it is necessary to reset the system, use the uadmin command.

# uadmin 2 1

 

To Power Cycle the System

 

If a simple reset does not clear a system problem, you can power the system off and on with this procedure.

1. Halt the Solaris OS.

At the Solaris OS prompt, issue the uadmin command to halt the Solaris OS and to return to the ok prompt.

# uadmin 2 0   WARNING: proc_exit: init exited syncing file systems… done Program terminated ok

2. Switch from the system console prompt to the SC console prompt by typing the #. escape sequence.

ok #.   sc>

3. Using the SC console, type the poweroff command.

sc> poweroff -fy   SC Alert: SC Request to Power Off Host Immediately.

4. Type the poweron command.

sc> poweron   sc> SC Alert: Host System has Reset

5. Reconnect to the system console using the console command.

sc> console -f   Enter #. to return to ALOM.

The systems displays various messages, followed by the ok prompt.