Fujitsu Siemens Computers SPARC M8000 Product Notes
  1. Manuals
  2. Brands
  3. Fujitsu Siemens Computers Manuals
  4. Server
  5. SPARC Enterprise M8000
  6. Product notes
Fujitsu Siemens Computers SPARC M8000 Product Notes

Fujitsu Siemens Computers SPARC M8000 Product Notes

Enterprise servers for xcp version 1072
Hide thumbs Also See for SPARC M8000:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual
SPARC
Enterprise
®
M8000/M9000 Servers
Product Notes
For XCP version 1072
Order No. U41813-J-Z816-1-76
Part No. 820-6008-10
September 2008, Revision A

Advertisement

Table of Contents
loading

Related Manuals for Fujitsu Siemens Computers SPARC M8000

Summary of Contents for Fujitsu Siemens Computers SPARC M8000

  • Page 1 SPARC Enterprise ® M8000/M9000 Servers Product Notes For XCP version 1072 Order No. U41813-J-Z816-1-76 Part No. 820-6008-10 September 2008, Revision A...
  • Page 2 Copyright 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. and FUJITSU LIMITED, 1-1, Kamikodanaka 4-chome, Nakahara-ku, Kawasaki-shi, Kanagawa-ken 211-8588, Japan. All rights reserved. Sun Microsystems, Inc. and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this document, and such products, technology and this document are protected by copyright laws, patents and other intellectual property laws and international treaties.
  • Page 3 Copyright 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. et FUJITSU LIMITED, 1-1, Kamikodanaka 4-chome, Nakahara-ku, Kawasaki-shi, Kanagawa-ken 211-8588, Japon. Tous droits réservés. Entrée et revue tecnical fournies par Fujitsu Limited sur des parties de ce matériel. Sun Microsystems, Inc.

  • Page 5: Table Of Contents

    Contents Preface vii Technical Support vii Software Resources vii Accessing Documentation viii Fujitsu Siemens Computers Welcomes Your Comments viii General Information about XCP Supported Firmware and Operating System 1 Solaris OS Patch Information 2 Patches for SPARC64 VI Processors 2...
  • Page 6 Hardware Issues and Workarounds Sun Crypto Accelerator 6000 Cards 7 Information about Software 8 XCP Issues and Workarounds 8 Solaris OS Issues and Workarounds 12 Software Documentation Updates 27 Identifying Degraded Memory in a System 29 Identifying Different Memory Sizes in a System Board 29 Using the showdevices Command 29 Using the prtdiag Command to Identify Memory Size 30 Identifying Permanent Memory in a Target Board 31...

  • Page 7: Preface

    SPARC Enterprise M8000/M9000 servers. Contact a sales representative or a certified service engineer for software resources for your SPARC Enterprise M8000/M9000 servers. Note – For latest patch information go to: http://support.fujitsu-siemens.com Installation information and README files are included in the patch download.

  • Page 8: Accessing Documentation

    Enterprise M8000/M9000 servers documentation set. Solaris documentation is available at: http://www.sun.com/documentation Fujitsu Siemens Computers Welcomes Your Comments If you have any comments or requests regarding this manual, or if you find any unclear statements in the manual, please state your points specifically, and forward it to a sales representative or a certified service engineer.

  • Page 9: General Information About Xcp

    General Information about XCP 1072 This section describes the general information about XCP 1072. Supported Firmware and Operating System ■ Updating to XCP ■ Functionality Issues and Limitations ■ Supported Firmware and Operating System The following firmware and operating system (OS) are supported in this release. Firmware and Operating System Versions TABLE 1 Firmware and Operaing System...

  • Page 10: Solaris Os Patch Information

    Note – By using the Solaris 10 8/07 installation DVD, you cannot boot the domain mounted with the SPARC64 VII processors. When you newly install Solaris OS to a domain mounted with the SPARC64 VII processors, use the Solaris 10 5/08 installation DVD to install Solaris 10 5/08.

  • Page 11: Updating To Xcp

    119254-51 or later ■ 125891-01 or later ■ 127755-01 or later ■ 127127-11 ■ The patches are not required for servers running Solaris 10 5/08 OS or later. Note – See “Software Resources” on page vii for information on how to find the latest patches.

  • Page 12: Updating From A Version Earlier Than Xcp 1070

    Updating from a Version Earlier Than XCP 1050 You cannot update to XCP 1071 or later directly. ■ If you are currently running a version earlier than XCP 1050, you must first update to an interim version of XCP between 1050 and 1070 (inclusive) before updating to XCP 1071 or later.
  • Page 13 General Functionality Issues and Limitations Caution – For dynamic reconfiguration (DR) and hot-plug issues, see TABLE 4 Domains using the ZFS file system cannot use Dynamic Reconfiguration. ■ The maximum number of IOUA (Base I/O Card) cards per domain is limited to ■...
  • Page 14 On the SPARC Enterprise M8000/M9000 servers with XCP 1050 or later, the dual ■ XSCF Unit feature is working. Therefore, you can not downgrade SPARC Enterprise M8000/M9000 servers with XCP 1050 or later to XCP 1040 or XCP 1041, which does not support dual XSCF Unit feature. You cannot use the following user account names, as they are reserved for system ■...

  • Page 15: Information About Hardware

    Information about Hardware This section describes the special instructions and the issues about the SPARC Enterprise M8000/M9000 servers hardware. Hardware Issues and Workarounds ■ Hardware Issues and Workarounds lists known hardware issues and possible workarounds. TABLE 2 Hardware Issues and Workarounds TABLE 2 CR ID Description...

  • Page 16: Information About Software

    Information about Software This section describes the special instructions and the issues about the SPARC Enterprise M8000/M9000 servers software. XCP Issues and Workarounds ■ Solaris OS Issues and Workarounds ■ Software Documentation Updates ■ Identifying Degraded Memory in a System ■...
  • Page 17 XCP Issues and Workarounds (Continued) TABLE 3 Description Workaround RTIF1- Using the XSCF Web, when you selected SSH To specify the value which exceeds the 070823-001 on the snapshot screen, the maximum number maximum number of character input for the of character input for Host, Directory, ID, and XSCF Web, use XSCF Shell.
  • Page 18 XCP Issues and Workarounds (Continued) TABLE 3 Description Workaround RTIF1- When you execute XCP Sync on the Firmware There is no workaround. However, the XCP 070914-025 Update page, after 15 minutes, the error Sync process has been continuously executed. message "Another flashupdate is now Check the XSCF update completion message processing"...
  • Page 19 XCP Issues and Workarounds (Continued) TABLE 3 Description Workaround RTIF1- When you specify "localhost" to the Do not specify "localhost" to the hostname of 080512-001 hostname of the sethostname(8) command the sethostname(8) command. and reset XSCF by using the applynetwork(8) and the rebootxscf(8) commands, a process goes down in XSCF.

  • Page 20: Solaris Os Issues And Workarounds

    Solaris OS Issues and Workarounds lists known Solaris OS issues and possible workarounds TABLE 4 Solaris OS Issues and Workarounds TABLE 4 CR ID Description Workaround 5076574 A PCIe error can lead to an invalid fault This bug has been fixed in Solaris 10 5/08. diagnosis on a large M8000/M9000 domain.
  • Page 21 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6449315 The Solaris OS cfgadm(1M) command does Disable the Volume Management Daemon not unconfigure a DVD drive from a domain (vold) before unconfiguring a DVD drive with on a SPARC Enterprise M8000/M9000 server. the cfgadm(1M) command.
  • Page 22 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6481002 Installing the Solaris OS from the network If you are using a Sun PCI-E Dual Gigabit using certain PCI-Express cards may cause a Ethernet Adapter MMF card or a Sun PCI-E panic.
  • Page 23 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6498283 Using the DR deleteboard(8) command This bug has been fixed in Solaris 10 8/07. while psradm operations are running on a For Solaris 10 11/06, this has been fixed in domain might cause a system panic.
  • Page 24 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6508432 Many correctable errors (CE) may occur, and This bug has been fixed in Solaris 10 8/07. despite these are the correctable errors, For Solaris 10 11/06, this has been fixed in domain may panic.
  • Page 25 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6515648 "Replumb Failed" error appears when Once the DR operation is complete, it can be dr@0:SB1::memory fails. plumbed up manually. Example steps to re-plumb the interface manually: # ifconfig interface plumb xxx.xxx.xxx.xxx netmask + broadcast + up # ifconfig interface group group-name # ifconfig interface addif xxx.xxx.xxx.xxx...
  • Page 26 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6522433 After the CPU hardware error occurred, the This bug has been fixed in Solaris 10 5/08. For fmdump(1M) command on the domain may Solaris 10 8/07 or earlier, this has been fixed in display an incorrect faulty component.
  • Page 27 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6531668 System hangs when executing parallel hot There is no workaround. plug operation with SP DR in suspend phase. 6532215 volfs or dscp service may fail when domain is Restart the service if the failure is observed.
  • Page 28 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6536564 showlogs(8) and showstatus(8) command This bug has been fixed in Solaris 10 5/08. on XSCF might report wrong I/O component For Solaris 10 8/07 or earlier, this has been due to wrong diagnosis by Solaris Fault fixed in patch 125369-05.
  • Page 29 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6542632 Memory leak in PCIe module if driver attach This bug has been fixed in Solaris 10 8/07. fails. For Solaris 10 11/06, this has been fixed in patch 120011-09.
  • Page 30 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6559504 Messages of the form nxge: NOTICE: This bug has been fixed in Solaris 10 5/08. nxge_ipp_eccue_valid_check: rd_ptr = nnn For Solaris 10 8/07, this has been fixed in wr_ptr = nnn will be observed on the console patch 127741-01.
  • Page 31 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6584984 On SPARC Enterprise M8000/M9000 servers, This bug has been fixed in Solaris 10 5/08. For busstat(1M) command may cause rebooting Solaris 10 8/07 or earlier, this has been fixed in of domains.
  • Page 32 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6614737 The DR deleteboard(8) and moveboard(8) This has been fixed in patch 137111-01. operations might hang if any of the following conditions exist: [Workaround] • A DIMM has been degraded. Avoid performing DR operations if any of the •...
  • Page 33 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6632549 fmd service on domain might fail to This has been fixed in patch 138050-01. maintenance mode after DR operations. [Workaround] If fmd service fails, issue the following commands on the domain to recover: # svcadm clear fmd 6660168...
  • Page 34 Solaris OS Issues and Workarounds (Continued) TABLE 4 CR ID Description Workaround 6660197 DR might cause the domain to hang if either of This has been fixed in patch 138397-01. the following conditions exist: • A domain contains 256 or more CPUs. [Workaround] •...

  • Page 35: Software Documentation Updates

    Software Documentation Updates This section contains late-breaking software information that became known after the documentation set was published and corrections in the SPARC Enterprise M8000/M9000 servers software documentation. The corrections for SPARC Enterprise M4000/M5000/M8000/M9000 servers XSCF Reference Manual, if not otherwise specified, also apply to the man pages which XSCF provides.
  • Page 36 Software Documentation Updates (Continued) TABLE 5 Title Page Number Update SPARC Enterprise The sendbreak(8) command will not work when the secure sendbreak(8) M4000/M5000/M8000/ command mode is set to on while the mode switch on the operator panel M9000 Servers XSCF is set to locked.

  • Page 37: Identifying Degraded Memory In A System

    Identifying Degraded Memory in a System 1. Log in to XSCF. 2. Type the following command: XSCF> showstatus The following example identifies DIMM number 00A on CMU#3 has degraded memory.. XSCF> showstatus CMU#3 Status:Normal; MEM#00A Status:Degraded; Identifying Different Memory Sizes in a System Board To identify if the domain contains system boards with different memory sizes, you can use either of the following commands to display the list of memory sizes:...

  • Page 38: Using The Prtdiag Command To Identify Memory Size

    2. Type the following command: XSCF> showdevices -d domain_id The following example displays 00-0 has 64GB of memory while the other system boards have 16GB. XSCF> showdevices -d 1 Memory: ------- board perm base domain target deleted remaining DID XSB mem MB mem MB address...

  • Page 39: Identifying Permanent Memory In A Target Board

    Identifying Permanent Memory in a Target Board 1. Log in to XSCF. 2. Execute the following command: 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...

  • Page 40: Cpu Upgrade

    CPU Upgrade This section describes the procedure to mount the SPARC64 VII processor on the SPARC Enterprise M8000/M9000 server. Adding a New CMU Equipped with SPARC64 VII as a New Domain ■ Upgrading an On-CMU SPARC64 VI to SPARC64 VII, or Adding SPARC64 VII to ■...

  • Page 41: Adding A New Cmu Equipped With Sparc64 Vii As A New Domain

    Adding a New CMU Equipped with SPARC64 VII as a New Domain 1. Log in to the XSCF on an account with platform administrative privileges. 2. Use the showstatus(8) command to confirm that a component in Faulted or Deconfigured status doesn't exist. XSCF>...
  • Page 42 Note – Do not fail to execute the diagnosis of newly mounted CMU in the maintenance menu of addfru(8) command. 10. Confirm that the mounted CPU module has been recognized by the server, and the error indicator asterisk (*) is not displayed. XSCF>...

  • Page 43: Upgrading An On-Cmu Sparc64 Vi To Sparc64 Vii, Or Adding Sparc64

    18. Install Solaris 10 5/08. 19. Use the setdomainmode(8) command, enable the autoboot function of the domain. For detail, see the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide. The autoboot function is applied by a domain reboot. Upgrading an On-CMU SPARC64 VI to SPARC64 VII, or Adding SPARC64 VII to an Existing CMU, to an Existing Domain Configured with SPARC64 1.
  • Page 44 8. Collect an XSCF snapshot to archive system status prior to upgrade. This will be help in case any problem occurred in this procedure. XSCF> snapshot -t user@host:directory 9. Update the XCP version to 1072. Before updating the XCP, be sure to see “Updating to XCP”...
  • Page 45 14. Turn off the power to the target domain. XSCF> poweroff -d domain_id 15. Upgrade an on-CMU SPARC64 VI processors to SPARC64 VII processors, or add SPARC64 VII processors to an existing CMU. For upgrading the CPU, operate by hot replacement, referring to "6.2 Active ■...

  • Page 46: Adding A New Cmu Equipped With Sparc64 Vii To An Existing Domain Configured With Sparc64 Vi

    21. Power on the target domains. XSCF> poweron -d domain_id 22. Confirm that the target domain has been correctly started. XSCF> showlogs power 23. Confirm no abnormality occurred by using showlogs error -v and showstatus(8) commands. XSCF> showlogs error -v XSCF>...
  • Page 47 7. Change the key position on the operator panel from Locked to Service. 8. Collect an XSCF snapshot to archive system status prior to upgrade. This will be help in case any problem occurred in this procedure. XSCF> snapshot -t user@host:directory 9.
  • Page 48 In case that the OpenBoot PROM version of the XSB to which the resource of the target CMU has been assigned is not displayed as 02.03.0000, contact a service engineer. 14. Turn off the target domain. XSCF> poweroff -d domain_id 15.
  • Page 49 Set up the CPU operational mode of the domain. ■ For each setting, see the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide. 21. Power on the target domains. XSCF> poweron -d domain_id 22. Confirm that the target domain has been correctly started. XSCF>...
  • Page 50 SPARC Enterprise M8000/M9000 Servers Product Notes for XCP Version 1072 • September 2008...

This manual is also suitable for:

Sparc m9000

Table of Contents