Updating the Firmware

To use the features and fixes in subsequent firmware releases, perform To Update the Firmware.

To Update the Firmware

Ensure that the ILOM service processor network management (NET MGT) port is configured.

This action is required to access the new flash image over the network. See Configuring the Service Processor Network Management Port.

Open an SSH session to connect to the service processor ILOM CLI.

% ssh root@xx.xxx.xx.x 
...
Are you sure you want to continue connecting (yes/no)? yes 
...
Password: password (nothing displayed) 
Waiting for daemons to initialize... 
 
Daemons ready 
 
Sun(TM) Integrated Lights Out Manager 
 
Version 2.0.0.0 
 
Copyright 2007 Sun Microsystems, Inc. All rights reserved. 
Use is subject to license terms. 
 
->

Verify that the host is powered off.

If the host is not powered off, type the stop /SYS command.
-> stop /SYS

Verify that the keyswitch_state parameter is set to normal.
-> set /SYS keyswitch_state=normal

Type the load command.

The load command updates the service processor flash image and the host firmware. The load command requires the following information:

IP address of a TFTP server on the network that can access the flash image

Full path name to the flash image that the IP address can access

The command usage is as follows:

where:
```
load [-script] -source tftp://xxx.xxx.xx.xx/pathname
```

-script – Do not prompt for confirmation and act as if yes was specified

-source – Specifies the IP address and full path name (URI) to the flash image

-> load -source tftp://xxx.xxx.xx.xx/pathname 
 NOTE: A firmware upgrade will cause the server and ILOM to 
       be reset. It is recommended that a clean shutdown of 
       the server be done prior to the upgrade procedure. 
       An upgrade takes about 6 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 
Do you want to preserve the configuration (y/n)? y 
...............................................................
 
Firmware update is complete. 
ILOM will now be restarted with the new firmware.
Update complete. Reset device to use new image. 
 
->

After the flash image has been updated, the system will automatically reset.

The service processor resets, runs diagnostics, and returns to the login prompt (on the serial console), similar to EXAMPLE A-1.

**EXAMPLE A-1 Typical Boot Sequence Following Firmware Update (Continued)**
U-Boot 1.1.1 (May 23 2007 - 21:30:12) ... POST cpu PASSED POST ethernet PASSED Hit any key to stop autoboot: 0 ## Booting image at fe080000 ... IP Protocols: ICMP, UDP, TCP, IGMP Checking all file systems... fsck 1.37 (21-Mar-2005) Setting kernel variables ... ... done. Mounting local filesystems... Cleaning /tmp /var/run /var/lock. Identifying DOC Device Type(G3/G4/H3) ... OK Configuring network interfaces...Internet Systems Consortium DHCP Client V3.0.1 Copyright 2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/products/DHCP eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. Listening on LPF/eth0/00:14:4f:3f:8c:af Sending on LPF/eth0/00:14:4f:3f:8c:af Sending on Socket/fallback DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 eth0: link up, 100 Mbps Full Duplex, auto-negotiation complete. DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 Hostname: hostname. Starting portmap daemon: portmap. Initializing random number generator...done. INIT: Entering runlevel: 3 Starting system log daemon: syslogd and klogd. Starting periodic command scheduler: cron. Starting IPMI Stack...... Done. Starting OpenBSD Secure Shell server: sshd. Starting Servicetags listener: stlistener. Starting FRU update program: frutool. hostname login:

EXAMPLE A-1 Typical Boot Sequence Following Firmware Update (Continued)

U-Boot 1.1.1 (May 23 2007 - 21:30:12)
...
POST cpu PASSED
POST ethernet PASSED
Hit any key to stop autoboot:  0
## Booting image at fe080000 ...
 
IP Protocols: ICMP, UDP, TCP, IGMP
 
Checking all file systems...
fsck 1.37 (21-Mar-2005)
Setting kernel variables ... 
... done. 
Mounting local filesystems... 
Cleaning /tmp /var/run /var/lock. 
 
Identifying DOC Device Type(G3/G4/H3) ... 
OK 
 
Configuring network interfaces...Internet Systems Consortium DHCP 
Client V3.0.1 
Copyright 2007 Internet Systems Consortium. 
All rights reserved. 
For info, please visit http://www.isc.org/products/DHCP 
 
eth0: config: auto-negotiation on, 100FDX, 100HDX, 10FDX, 10HDX. 
Listening on LPF/eth0/00:14:4f:3f:8c:af 
Sending on   LPF/eth0/00:14:4f:3f:8c:af 
Sending on   Socket/fallback 
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 
eth0: link up, 100 Mbps Full Duplex, auto-negotiation complete. 
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 
Hostname: hostname. 
Starting portmap daemon: portmap. 
Initializing random number generator...done. 
INIT: Entering runlevel: 3 
Starting system log daemon: syslogd and klogd. 
Starting periodic command scheduler: cron. 
Starting IPMI Stack...... Done. 
Starting OpenBSD Secure Shell server: sshd. 
Starting Servicetags listener: stlistener. 
Starting FRU update program: frutool. 
 
hostname login: