General Information About XCP 1080

This section includes the following sections:

What’s New in XCP 1080

Supported Firmware and Operating System

Solaris Patch Information

Obtaining Solaris Patches

Upgrading to XCP 1080

Functionality Issues and Limitations

Additional Information and Procedures

What’s New in XCP 1080

In XCP Version 1080, the following new XSCF commands are supported:

dumpconfig(8)

ping(8)

restoreconfig(8)

traceroute(8)

For detail, see the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF Reference Manual or the manual pages for each command.

Supported Firmware and Operating System

TABLE 1 lists the firmware and operating system (OS) versions that are supported in this release.

TABLE 1 Firmware and Operating System Versions
Software or Firmware	Version
XSCF Control Package SPARC64 VII processors: Capacity on Demand (COD) support:	1080 XCP 1071 XCP 1050
Solaris Operating System SPARC64 VI processors: SPARC64 VII processors:	Solaris 10 11/06 or later, with required patches Solaris 10 8/07 or later, with required patches ^[1]

Note - You cannot boot a domain mounted with the SPARC64 VII processors using the Solaris 10 8/07 installation DVD. Use the Solaris 10 5/08 installation DVD to boot a domain mounted with the SPARC64 VII processors.

Many web browsers support the XSCF Web. The browsers in TABLE 2 have demonstrated compatibility with the XSCF Web through testing.

TABLE 2 Tested Web Browser Versions
Web Browser Application	Version
Firefox	2.0 and 3.0
Microsoft Internet Explorer	6.0 and 7.0

Solaris Patch Information

This section lists mandatory patches for the M4000/M5000 servers.

Always refer to the patch README for information about patch requirements and special installation instructions.

The patch identifiers listed in this section represent the minimum level of the patches that must be installed. The two-digit suffix represents the minimum revision level of the patch.

Check http://sunsolve.sun.com for the latest patch revision.

Apply patches in the order listed. For the procedures of CPU upgrade including the patches, see CPU Upgrade (Service Representatives Only).

For additional Solaris OS information see Solaris OS Issues and Workarounds.

Patches for Solaris 10 10/08

Patches are not required for servers running Solaris 10 10/08 OS or later.

Patches for Solaris 10 5/08

The following patch is required for all M4000/M5000 servers running Solaris 10 5/08:

137137-09

Solaris 10 5/08 OS might panic/trap during normal domain operation (CR 6720261). To prevent this you must set the following parameter in the system specification file (/etc/system):

set heaplp_use_stlb=0

Then reboot the domain.

Patches for Solaris 10 8/07

The following patches are required for Solaris 10 8/07 OS only on servers containing SPARC64 VII CPUs. Install them in the order in which they are listed:

1. 119254-51 - SunOS 5.10: Install and Patch Utilities Patch

2. 125891-01 - SunOS 5.10: libc_psr_hwcap.so.1 patch

3. 127755-01 - SunOS 5.10: Fault Manager patch

4. 127127-11 - SunOS 5.10: kernel patch

Solaris 10 8/07 OS with patch 127127-11 might panic/trap during normal domain operation (CR 6720261). To prevent this you must set the following parameter in the system specification file (/etc/system):

set heaplp_use_stlb=0

Then reboot the domain.

Patches for Solaris 10 11/06

The following patches are required for Solaris 10 11/06 OS. Note that Solaris 10 11/06 does not support SPARC64 VII processors, even with these required patches. Install the patches in the order in which they are listed:

1. 118833-36 - Reboot your domain before proceeding.

2. 125100-10 - See the patch README file for a list of other patch requirements.

3. 123839-07

4. 120068-03

5. 125424-01

6. 118918-24

7. 120222-21

8. 125127-01 - Reboot your domain before proceeding.

9. 125670-02

10. 125166-05

Patches for Emulex PCI Express (PCIe) Cards

The following Emulex cards require drivers supplied in patch 120222-26:

Sun StorageTek Enterprise Class 4-gigabit Dual-Port Fibre Channel PCIe HBA (part SG-XPCIE2FC-EM4)

Sun StorageTek Enterprise Class 4-gigabit Single-Port Fibre Channel PCIe HBA (part SG-XPCIE1FC-EM4)

Patches for QLogic PCIe Cards

The following QLogic cards require drivers supplied in patch 125166-10:

Sun StorageTek Enterprise Class 4-gigabit Dual-Port Fibre Channel PCIe HBA (part SG-XPCIE2FC-QF4)

Sun StorageTek Enterprise Class 4-gigabit Single-Port Fibre Channel PCIe HBA (part SG-XPCIE1FC-QF4)

Obtaining Solaris Patches

The Sun^sm Connection Update Manager can be used to reinstall the patches if necessary or to update the system with the latest set of mandatory patches. For more Information about the Sun Connection Update Manager, refer to the Sun Update Connection System Administration Guide at:

http://docs.sun.com/app/docs/prod/updconn.sys

Or visit:

http://wikis.sun.com/display/SunConnection/Update+Manager

There are two options available to register your system and to use the Sun Connection Update Manager to obtain the latest Solaris OS patches:

Using the Update Manager GUI to Obtain Patches

Using the smpatch CLI to Obtain Patches

Installation information and README files are included in the patch downloads.

Caution - For Sun SPARC Enterprise M4000/M5000 servers running Solaris 10 11/06 OS, patches 123003-03 and 124171-06 must be installed on your system prior to using Sun Connection Update Manager. These patches can be downloaded from http://sunsolve.sun.com/if needed. These patches are not required for servers running later versions of Solaris 10 OS.

Using the Update Manager GUI to Obtain Patches

1. As root, launch the Update Manager from either of the following:

From JDS Launch menu:

Click Launch->Applications->System Tools->Update Manager

From a terminal window:

Type /usr/bin/updatemanager

2. Complete the registration.

If you have already registered, proceed to Step 3.

If you have not yet registered, the Update Manager interface guides you through the registration process. Follow the onscreen instructions.

Note - If you are unable to complete registration using the Sun Connection Update Manager GUI, use the command-line interface (CLI) option to obtain patches. See Using the smpatch CLI to Obtain Patches.

3. In the Available tab in the Update Manager, open the Update Collection drop-down menu and select Sun SPARC Enterprise M4000/M5000/M8000/M9000 Servers.

Update Manager analyzes your system for any patches that are needed.

4. If a kernel patch is recommended, select it by clicking the box to the left of the patch ID, then click the Install button.

The patch is downloaded to /var/sadm/spool.

Note - Kernel patches (such as patch 118833-xx, for example) require special instructions for installation (see the patch README for specifics). They are often download-only (interactive) patches, requiring manual installation. You must install kernel patches before any others in order for any remaining patches in the patch set to be installed.

5. For a kernel patch, continue by typing:

# cd /var/sadm/spool

# unzip patchid-xx.jar

6. Follow the installation instructions in the file
/var/sadm/spool/patchid-xx/README.patchid-xx.

7. After installing patchid-xx, restart the system with the shutdown command.

Using the reboot command does not complete installations of patches that require a restart. You must use the Update Manager or the shutdown command.

# shutdown -i6

8. Launch the Update Manager again, and select the collection, as in Step 3.

9. If the Update Manager does not automatically start a new analysis, click the Check for Updates button.

10. Select any patches that are listed by checking the boxes to the left of the patch IDs.

11. Click the Install button.

Update Manager downloads and installs the patches.

12. If any of the patches require a system restart, follow the instructions in Step 7.

If any patches are installed that require restart, Update Manager offers to restart the system. Alternatively, you can use the shutdown command, as described in Step 7. For patches that require restart, you must perform the restart in order for the installation to take effect.

The patch installation is now complete.

Using the `smpatch` CLI to Obtain Patches

1. Copy the file /usr/lib/breg/data/RegistrationProfile.properties to your /tmp directory.

2. Edit the file /tmp/RegistrationProfile.properties to add your user name, password, network proxy (if necessary), and port (if required).

Note - The user name and password is a Sun Online Account. To create an account, go to http://sunsolve.sun.com.

3. Register your system.

# sconadm register -a -r /tmp/RegistrationProfile.properties

4. Obtain the correct patches.

# smpatch set patchpro.patchset=sem4k5k8k9k

5. Install any kernel patches.

Kernel patches, such as 118833-xx, can be downloaded through the Sun Connection Update Manager.

a. Download the patch to your /var/sadm/spool directory.

# smpatch update -i patchid-xx

b. Unzip the patch.

# cd /var/sadm/spool

# unzip patchid-xx.jar

c. Install the patch by following the installation instructions in the file: /var/sadm/spool/patchid-xx/README.patchid-xx.

6. Restart the system

Using the reboot command does not complete installation of patches that require a restart. You must use the Update Manager or the shutdown command.

# shutdown -i6

7. Display a list of patches.

# smpatch analyse

8. Download and install the patches.

# smpatch update

9. If any of the patches requires a system restart, see Step 6.

If any patches are installed that require restart, Update Manager offers to restart the system. Alternatively, you can use the shutdown command, as described in Step 6. For patches that require restart, you must perform the restart in order for the installation to take effect.

The patch installation is now complete.

Upgrading to XCP 1080

You can upgrade to XCP 1080 from XCP version 1050 or higher. Refer to the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for instructions.

Resetting the XSCF Firmware

After updating the XCP firmware to 1080 or later use the rebootxscf(8) command to reset the XSCF.

Updating the OpenBoot PROM Firmware

To complete updating the OpenBoot trademark PROM (OBP) firmware in the target domain, be sure to restart the domain. You should restart the domain as soon as possible after completing the update.

Updating From a Version Earlier Than XCP 1050

You cannot directly update to XCP 1080 or later. If you are currently running a version earlier than XCP 1050, you must first update to an interim version of XCP (between 1050 and 1061 inclusive) before updating to XCP 1080 or later. Refer to the product notes document for the interim version for instructions.

Use the deleteuser(8) command to delete any accounts named admin prior to updating to XCP 1050 or later. The admin account name is reserved in XCP 1050 and higher.

Updating From a Version Earlier Than XCP 1080

On a domain that has been in operation during the XCP update to XCP 1080 or later, when you perform dynamic reconfiguration (DR) to add or replace the SPARC64 VII processors, you need to update the OpenBoot PROM firmware. The OpenBoot PROM firmware is updated as you update the XCP and restart the domain. For this reason, restart all the domains after you update the firmware to XCP 1080 or later, regardless of whether you added or replaced the SPARC64 VII processors.

Functionality Issues and Limitations

This section describes known issues in this release.

Limitations for SPARC64 VII Processors

Caution - You must complete the upgrades to the XCP firmware and to the Solaris OS before inserting SPARC 64 VII processors into the chassis.

General Functionality Issues and Limitations

Caution - For dynamic reconfiguration (DR) and hot-plug issues, see Solaris OS Issues and Workarounds.

Note - For power-on after power-off, wait at least 30 seconds before turning the system power back on, by using the main line switch or the circuit breakers on the distribution panel.

You cannot use the following user account names, as they are reserved for system use: root, bin, daemon, adm, operator, nobody, sshd, rpc, rpcuser, ldap, apache, ntp, admin, and default.

Do not use the Service Processor (SP) as the Network Time Protocol (NTP) server. Using an independent NTP server provides optimal reliability in maintaining consistent time on the SP and the domains. For more information about NTP, see the Sun BluePrints document, Using NTP to Control and Synchronize System Clocks: http://www.sun.com/blueprints/0701/NTP.pdf

When you use the external power control interface of the external power controller, the following notification signals are not supported:

The OS panic or the server hardware error signal (*CPUN/RTNU)

The server hardware error signal (power fail, temperature error, and fan error) (*ALARM)

When you import XCP or update the firmware using the XSCF you might see Web session ID errors displayed on the web browser. When you specify the timeout period as over 30 minutes in the Autologout setting Internal Server Errors might be displayed. To reconnect to the XSCF Web, close the current browser and open the new browser.

For this XCP release, the XSCF browser user interface (XSCF Web) does not support the External I/O Expansion Unit Manager feature.

Disable pop-up blocking and remove any plug-ins such as the search tool installed with the browser when you use the XSCF Web.

To use XSCF Web, disable the cache function of your browser. If you leave the browser cache function enabled, the old cached data might be displayed. To disable the cache function:

Internet Explorer 6 & 7

Tools->Internet Options...->Advanced tab and check the “Do not save encrypted pages to disk” box.

Firefox 2 & 3

Type about:config in the address box, and then type cache in filter box.

Change the Browser.Cache.Check.Doc.Frequency settings value to 1.

XSCF-LAN is compliant with autonegotiation. Set the network device which connects with XSCF-LAN to the autonegotiation mode. Otherwise when you connect the XSCF-LAN and the network device (fixed to the full-duplex mode, according to the IEEE 802.3 rule) the XSCF-LAN communicates in half-duplex mode and network communication speed might slow down or communication errors occur.

Domains using the ZFS file system cannot use dynamic reconfiguration (DR).

The M4000/M5000 servers are cold service machines. Hot-swapping of the CPU module (CPUM), memory board (MEMB), I/O unit (IOU), or XSCF unit is not supported.

For 1027A-Z/X1027A-Z, PCIe Dual 10-Gigabit Ethernet Fiber XFP cards, these limits apply:

Do not use more than two cards per domain.

Do not use these cards in an External I/O Expansion Unit.

For 4447A-Z/X4447A-Z, PCIe Quad-port Gigabit Ethernet Adapter UTP cards, these maximum limits apply:

No more than four cards in an External I/O Expansion Unit (two per PCIe I/O boat).

No more than four cards in a M4000 server domain.

No more than eight cards in a M5000 server domain.

Do not use the CD-RW/DVD-RW drive unit and the TAPE drive unit at the same time.

The use of the External I/O Expansion Unit to connect the host server to an external boot disk drive is not supported.

DR is not compatible with XSCF failover or XSCF reset. Do not start an XSCF failover or reset while a DR operation is running. Wait for a DR operation to finish before starting the failover or reset. If you start the failover or reset first, wait for the failover or reset to finish before starting the DR operation.

Additional Information and Procedures

This section describes additional known issues and limitations at the time of this release.

Logging Into the System

In addition to the standard default login, the servers is delivered with a temporary login called admin to enable remote initial login, through a serial port. The server’s privileges are fixed to useradm and cannot be changed. You cannot log in as temporary admin using the standard UNIX user name and password authentication or SSH public key authentication. The temporary admin account has no password, and one cannot be added for it.

The temporary admin account is disabled after someone logs in as the default user, or after someone logged in as temporary admin has successfully added the first user with valid password and privileges.

If, before the default login is used, you cannot log in as temporary admin, you can determine if someone else has done so by executing the showuser -l command.

Sun Crypto Accelerator 6000 Cards

If you are not using the correct version of the Sun Crypto Accelerator (SCA) 6000 card driver, hot-plug operations on SCA 6000 cards can cause M4000/M5000 servers to panic or hang. Version 1.1 of the SCA6000 driver and firmware supports hot-plug operations after the required bootstrap firmware upgrade has been performed. Version 1.0 of the SCA6000 driver does not support hot-plug and should not be used.

U320 PCIe SCSI Card

U320 PCIe SCSI card, part numbers 375-3357-01/02, is not supported in PCI cassettes for Sun SPARC Enterprise M4000/M5000 servers. Customers must use
375-3357-03 or later.

Sun Java Enterprise Server

The Sun Java Enterprise Server is a comprehensive set of software and life cycle services that make the most of your software investment. For an overview and documentation, go to:

http://www.sun.com/service/javaes/index.xml

Note - Due to an issue that arises from the installation of the Java Enterprise System 5 Update 1 on your system (CR 6644798), it might be necessary to enable the Web Console SMF service.

Enabling the Web Console SMF Service

# svcadm enable svc:/system/webconsole:console

If you have to reload the software, go to the following web site for download and installation instructions:

http://www.sun.com/software/preinstall

If you download a fresh copy of software, that software might not include patches that are mandatory for your server. After installing the software, refer to Solaris Patch Information for information about checking for and installing required patches.

XSCF Web Browser Issues

The XSCF Web browser interface occasionally truncates output. For example when you select SSH on the snapshot screen, the maximum number of character input for Host, Directory, ID, and Password does not correspond to the maximum number of character input on the XSCF Shell. The Panic Log page only displays the last 50 lines of the panic message (CR 6756052). The browser interface displays only the last two digits of the non-audit log size limit (CR 6742502).

To see the full output use the XSCF Shell command-line interface (CLI).

Booting From a WAN Boot Server

The WAN boot installation method enables you to boot and install software over a wide area network (WAN) by using HTTP. To support booting the M4000/M5000 servers from a WAN boot server, you must have the appropriate wanboot executable installed and OpenBoot version 4.24 or above to provide the needed hardware support.

For information about WAN boot servers, refer to the Solaris 10 Installation Guide: Network-Based Installations for the version of Solaris 10 OS that you are using. You can find Solaris 10 OS documentation here:

http://docs.sun.com/app/docs/prod/solaris.10

If you do not upgrade the wanboot executable, the M3000 server will panic, with messages similar to the following:

krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase
panic - boot: exitto64 returned from client program

Identifying System Memory

Identifying Degraded Memory in a System

XSCF> showstatus

The following example identifies DIMM number 0A on Memory Board #5 has degraded memory.

XSCF> showstatus
    MBU_B Status:Normal;
        MEMB#5 Status:Normal;
*           MEM#0A Status:Degraded;

Using the showdevices Command to Identify Memory Size

XSCF> showdevices -d domain_id

The following example shows a display of the showdevices -d command, where 0 is the domain_id.

XSCF> showdevices -d 0 
 
...
 
Memory:
-------
          board   perm    base                domain  target deleted remaining
DID XSB   mem MB  mem MB  address             mem MB  XSB    mem MB  mem MB
00  00-0   65536    2402  0x0000000000000000  131072
00  01-0   16384       0  0x000003c000000000  131072
00  01-1   16384       0  0x0000038000000000  131072
00  01-2   16384       0  0x0000034000000000  131072
00  01-3   16384       0  0x0000030000000000  131072
 
...

This example shows that 00-0 has 64 Gbytes of memory, while the other system boards have 16 Gbytes.

Using the prtdiag Command to Identify Memory Size

In the domain, display system diagnosis information.

# prtdiag

The following example shows a display of the prtdiag command.

# prtdiag
 
...
 
============================ Memory Configuration ============================
 
Memory  Available           Memory     DIMM    # of  Mirror Interleave
LSB    Group   Size                Status     Size    DIMMs Mode Factor
---    ------  ------------------  -------    ------  ----- ------- ----------
 00    A        32768MB            okay       2048MB     16 no       8-way
 00    B        32768MB            okay       2048MB     16 no       8-way
 01    A         8192MB            okay       2048MB      4 no       2-way
 01    B         8192MB            okay       2048MB      4 no       2-way
 02    A         8192MB            okay       2048MB      4 no       2-way
 02    B         8192MB            okay       2048MB      4 no       2-way
 03    A         8192MB            okay       2048MB      4 no       2-way
 03    B         8192MB            okay       2048MB      4 no       2-way
 04    A         8192MB            okay       2048MB      4 no       2-way
 04    B         8192MB            okay       2048MB      4 no       2-way
 
...

This example displays varying memory sizes.

Identifying Permanent Memory in a Target Board

XSCF> showdevices -d domain_id

The following example shows a display of the showdevices -d command, where 0 is the domain_id.

XSCF> showdevices -d 0
 
...
 
Memory:
-------
             board     perm       base                  domain   target deleted remaining
DID XSB   mem MB  mem MB  address             mem MB  XSB    mem MB  mem MB
00  00-0   65536    2402  0x0000000000000000  131072
00  01-0   16384       0  0x000003c000000000  131072
00  01-1   16384       0  0x0000038000000000  131072
00  01-2   16384       0  0x0000034000000000  131072
00  01-3   16384       0  0x0000030000000000  131072
 
...

The entry for column 4, perm mem MB, indicates the presence of permanent memory if the value is not zero.

The example shows permanent memory on 00-0, with 2402 Mbytes.

If the board includes permanent memory, when you execute the deleteboard command or the moveboard command, the following notice is displayed:

System may be temporarily suspended, proceed? [y|n]:

CPU Upgrade (Service Representatives Only)

Note - You must be an authorized service representative to install SPARC64 VII processors in your server.

This section describes procedures for installing SPARC64 VII processors in SPARC Enterprise M4000/M5000 servers:

SPARC64 VII CPU Modules Added to a New Domain

SPARC64 VII Processors Added to an Existing Domain

Note - Before upgrading firmware to XCP 1071, refer to Upgrading to XCP 1080.

Caution - You must complete the upgrades to the XCP firmware and to Solaris before inserting SPARC 64 VII processors into the chassis.

For more information about configuring combinations of processors in domains, refer to Section 2.2.13, “Domain Mode Configuration,” in the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide. In particular, see the section “SPARC64 VI and SPARC64 VII Processors and CPU Operational Modes.”

SPARC64 VII CPU Modules Added to a New Domain

Adding a SPARC64 VII CPU Module to a New Domain

Note - If you want to install Solaris 10 8/07 on the new domain, you must install from a patched image on the installation server. (See Step 20.)

1. Log in to the XSCF using an account with platadm privileges.

2. Confirm that no FRU is currently listed in Faulted or Deconfigured status.

XSCF> showstatus

3. Turn off the power to all domains.

XSCF> poweroff -a

4. Confirm that all domains have stopped.

XSCF> showlogs power

5. Change the key position on the operator panel from Locked to Service.

6. Collect an XSCF snapshot to archive system status prior to upgrade.

If a problem should occur during the upgrade procedure, a snapshot of the system status might be helpful.

XSCF> snapshot -t user@host:directory

7. Update the XCP version to 1080.

Before updating firmware to XCP 1080, refer to Upgrading to XCP 1080. For instructions for updating the firmware, refer to the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

8. Install the CPU module (CPUM) in the server.

For instructions, refer to Chapter 12, “CPU Module Replacement,” in the Sun SPARC Enterprise M4000/M5000 Servers Service Manual. Note that this procedure involves powering down the entire server.

Caution - After installing the CPU module, you must reconnect the power cable to the power supply.

9. Log in to the XSCF again, using an account with platadm or fieldeng privileges.

10. Perform an initial diagnosis of the newly installed CPU module.

XSCF> testsb 01

The following example shows a test after adding PSB#01 to a SPARC Enterprise M5000 server:

XSCF> testsb 01 
Initial diagnosis is about to start. Continue? [y|n] : y
Initial diagnosis is executing.
Initial diagnosis has completed.
XSB Test Fault
---- ------- --------
01 Passed Normal

11. Confirm that the installed CPU module is recognized by the server and that the error indicator asterisk (*) is not displayed.

XSCF> showhardconf -M

12. Confirm that no abnormality has occurred.

XSCF> showlogs error -v 
XSCF> showstatus

13. Change the key position on the operator panel from Service to Locked.

14. Power on the existing domains.

XSCF> poweron -a

15. Set the following for the added CPU module:

Set up XSB for the added CPU module.

Set up the domain.

Set up the CPU operational mode on the domain.

Refer to Chapter 2, “Setting Up XSCF,” in the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for information about these settings.

16. Use the setdomainmode(8) command to disable the autoboot function of the domain.

Refer to the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide and the setdomainmode(8) man page for more information.

17. Power on the new domain.

XSCF> poweron -d domain_id

18. Confirm that the target domain has been correctly started.

XSCF> showlogs power

19. Confirm that no abnormality has occurred.

XSCF> showlogs error -v 
XSCF> showstatus

20. Install a version of Solaris OS that supports SPARC64 VII processors.

Refer to Supported Firmware and Operating System for information about supported software versions.

If you are installing Solaris 10 8/07 on the new domain, you must install from a patched image on the installation server. For information about patches, refer to Solaris Patch Information. For information about network-based installations, refer to Solaris 10 8/07 Installation Guide: Network-Based Installations (part 820-0177).

21. Use the setdomainmode(8) command to enable the autoboot function of the domain.

The autoboot function is applied by a domain reboot. For more information, refer to the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide and the setdomainmode(8) man page.

SPARC64 VII Processors Added to an Existing Domain

Adding SPARC64 VII Processors to an existing domain is a two step process. First you must prepare the system (see Preparing to Add SPARC64 VII Processors to an Existing Domain) and then you must install the Processors using the instructions that correspond to your installation scenario.

Adding a SPARC64 VII CPU Module to a Domain Configured With SPARC64 VI.

Upgrading a SPARC64 VI CPU Module to SPARC64 VII on an Existing Domain

Preparing to Add SPARC64 VII Processors to an Existing Domain

1. If necessary, upgrade to a version of Solaris OS that supports SPARC64 VII processors.

Refer to Supported Firmware and Operating System for information about supported software versions. Apply any required patches.

2. Log in to the XSCF using an account with platadm privileges.

3. Confirm that no FRU is currently listed in Faulted or Deconfigured status.

XSCF> showstatus

4. Turn off the power for all the domains.

XSCF> poweroff -a

5. Confirm that the power is off for the domains.

XSCF> showlogs power

6. Change the key position on the operator panel from Locked to Service.

7. Collect an XSCF snapshot to archive system status prior to upgrade.

If a problem should occur during the upgrade procedure, a snapshot of the system status might be helpful.

XSCF> snapshot -t user@host:directory

8. Update the XCP version to 1080.

9. Log in to the XSCF again, using an account with platadm or fieldeng privileges.

10. Power on all the domains, and apply OpenBoot PROM firmware.

XSCF> poweron -a

The ok prompt is displayed. You do not need to start the Solaris OS.

11. Check the updated OpenBoot PROM version.

XSCF> version -c cmu -v

For XCP 1080, the version of OpenBoot PROM is 02.07.0000. Your output should look similar to the following:

XSCF> version -c cmu -v 
DomainID  0: 02.07.0000
DomainID  1: 02.07.0000
DomainID  2: 02.07.0000
DomainID  3: 02.07.0000
XSB#00-0:  02.07.0000(Current)     02.03.0000(Reserve) 
XSB#00-1:  02.07.0000(Current)     02.03.0000(Reserve) 
XSB#00-2:  02.07.0000(Current)     02.03.0000(Reserve) 
XSB#00-3:  02.07.0000(Current)     02.03.0000(Reserve) 
XSB#01-0:  02.07.0000(Current)     02.03.0000(Reserve) 
XSB#01-1:  02.07.0000(Current)     02.03.0000(Reserve) 
XSB#01-2:  02.07.0000(Current)     02.03.0000(Reserve) 
XSB#01-3:  02.07.0000(Current)     02.03.0000(Reserve) 
...

12. Turn off the power to all the domains.

XSCF> poweroff -a

13. Continue with the appropriate installation procedure:

If you are adding a new SPARC64 VII-equipped CPU module to a domain configured with SPARC64 VI processors, continue with Adding a SPARC64 VII CPU Module to a Domain Configured With SPARC64 VI.

If you are upgrading an existing SPARC64 VI CPU module in an existing domain to SPARC64 VII processors, continue with Upgrading a SPARC64 VI CPU Module to SPARC64 VII on an Existing Domain.

Adding a SPARC64 VII CPU Module to a Domain Configured With SPARC64 VI

This procedure must be preceded by Preparing to Add SPARC64 VII Processors to an Existing Domain. If you have not completed that procedure, do so before continuing.

1. Install the CPUM in the server.

For instructions, refer to the “CPU Module Replacement,” chapter in the Sun SPARC Enterprise M4000/M5000 Servers Service Manual. Note that this procedure involves powering down the entire server.

Caution - After installing the CPU module, you must reconnect the power cable to the power supply.

2. Log in to the XSCF again, using an account with platadm or fieldeng privileges.

Perform an initial diagnosis of the newly installed CPU module.

XSCF> testsb 01

The following example shows a test after adding PSB#01:

XSCF> testsb 01 
Initial diagnosis is about to start. Continue? [y|n] : y
Initial diagnosis is executing.
Initial diagnosis has completed.
XSB Test Fault
---- ------- --------
01 Passed Normal

3. Confirm that the installed CPU module is recognized by the server and that the error indicator asterisk (*) is not displayed.

XSCF> showhardconf -M

4. Confirm that no abnormality has occurred.

XSCF> showlogs error -v 
XSCF> showstatus

5. Change the key position on the operator panel from Service to Locked.

6. Set the following for the CPU module:

Set up XSB.

Set up the LSB.

Add the XSB to the domain.

Set up the CPU operational mode on the domain.

Refer to Chapter 2, “Setting Up XSCF,” in the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for information about these settings.

7. Power on all the domains.

XSCF> poweron -a

8. Confirm that all the domains have been correctly started.

XSCF> showlogs power

9. Confirm that no abnormality has occurred.

XSCF> showlogs error -v 
XSCF> showstatus

Upgrading a SPARC64 VI CPU Module to SPARC64 VII on an Existing Domain

This procedure must be proceeded by Preparing to Add SPARC64 VII Processors to an Existing Domain. If you have not completed that procedure please do so before continuing.

1. Replace the SPARC64 VI CPU module with the SPARC64 VII CPU module.

Caution - After installing the CPU module, you must reconnect the power cable to the power supply.

2. Log in to the XSCF again, using an account with platadm or fieldeng privileges.

3. Perform an initial diagnosis of the newly installed CPU module.

XSCF> testsb 01

The following example shows a test after adding PSB#01 to a SPARC Enterprise M5000 server:

XSCF> testsb 01 
Initial diagnosis is about to start. Continue? [y|n] : y
Initial diagnosis is executing.
Initial diagnosis has completed.
XSB Test Fault
---- ------- --------
01 Passed Normal

4. Confirm that the installed CPU module is recognized by the server and that the error indicator asterisk (*) is not displayed.

XSCF> showhardconf -M

5. Confirm that no abnormality has occurred.

XSCF> showlogs error -v 
XSCF> showstatus

6. Change the key position on the operator panel from Service to Locked.

7. Set up and confirm the CPU operational mode of the domain.

For more information, refer to Chapter 2, “Setting Up XSCF,” in the Sun SPARC Enterprise M3000/M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

8. Power on all the domains.

XSCF> poweron -a

9. Confirm that the target domain has been correctly started.

XSCF> showlogs power

10. Confirm that no abnormality has occurred.

XSCF> showlogs error -v 
XSCF> showstatus

^{1 (TableFootnote) See Solaris Patch Information for information about patches.

Check http://sunsolve.sun.com for the latest patch revision}