Fujitsu Siemens Computers SPARC Enterprise M5000 User Manual
  1. Manuals
  2. Brands
  3. Fujitsu Siemens Computers Manuals
  4. Server
  5. SPARC Enterprise M5000
  6. User manual
Fujitsu Siemens Computers SPARC Enterprise M5000 User Manual

Fujitsu Siemens Computers SPARC Enterprise M5000 User Manual

Fujitsu siemens servers dynamic reconfiguration (dr) user's guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Dynamic Reconfiguration (DR) User's Guide
English
SPARC Enterprise
M4000 / M5000 / M8000 / M9000 Servers

Advertisement

Table of Contents
loading

Related Manuals for Fujitsu Siemens Computers SPARC Enterprise M5000

Summary of Contents for Fujitsu Siemens Computers SPARC Enterprise M5000

  • Page 1 Dynamic Reconfiguration (DR) User’s Guide English SPARC Enterprise M4000 / M5000 / M8000 / M9000 Servers...
  • Page 3 SPARC Enterprise ® M4000/M5000/M8000/M9000 Servers Dynamic Reconfiguration (DR) User's Guide Order No. U41684-J-Z816-2-76 Part No.819-7898-11 September 2007, Revision A...
  • Page 4 Copyright 2007 FUJITSU LIMITED, 1-1, Kamikodanaka 4-chome, Nakahara-ku, Kawasaki-shi, Kanagawa-ken 211-8588, Japan. All rights reserved. Sun Microsystems, Inc. provided technical input and review on portions of this material. 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 5 Copyright 2007 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 Sun Microsystems, Incl sur des parties de ce matériel. Sun Microsystems, Inc. et Fujitsu Limited détiennent et contrôlent toutes deux des droits de propriété intellectuelle relatifs aux produits et technologies décrits dans ce document.

  • Page 7: Table Of Contents

    Contents Preface xiii Overview of Dynamic Reconfiguration 1–1 DR 1–1 Basic DR Functions 1–5 1.2.1 Adding a System Board 1–6 1.2.2 Deleting a System Board 1–6 1.2.3 Moving a System Board 1–6 1.2.4 Replacing a System Board 1–7 Security 1–7 Overview of DR User Interfaces 1–7 What You Must Know Before Using DR 2–1 System Configuration 2–1...
  • Page 8 2.1.4 2.1.5 Conditions and Settings Using XSCF 2–12 2.2.1 2.2.2 Conditions and Settings Using Solaris OS 2–16 2.3.1 2.3.2 Status Management 2–17 2.4.1 2.4.2 2.4.3 Operation Management 2–27 2.5.1 2.5.2 2.5.3 2.5.4 2.5.5 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Checklists for System Configuration 2–11 Reservation of Domain Configuration Changes 2–12 Conditions Using XSCF 2–12...
  • Page 9 2.5.6 XSCF Failover 2–29 2.5.7 Kernel Memory Board Deletion 2–29 2.5.8 Deletion of Board with DVD Drive 2–30 DR User Interface 3–1 How To Use the DR User Interface 3–1 3.1.1 Displaying Domain Information 3–2 3.1.2 Displaying Domain Status 3–5 3.1.3 Displaying System Board Information 3–6 3.1.4...
  • Page 10 Examples: Replacing a System Board 4–12 4.5.1 4.5.2 Examples: Reserving Domain Configuration Changes 4–20 4.6.1 4.6.2 4.6.3 A. Message Meaning and Handling A–1 Solaris OS Messages A–1 A.1.1 A.1.2 A.1.3 Command Messages A–23 A.2.1 A.2.2 A.2.3 A.2.4 A.2.5 A.2.6 B. Example: Confirm Swap Space Size B–1 Glossary Glossary–1 Index Index–1 viii...
  • Page 11 FIGURE 2-1 Example of Hardware Configuration (with Quad-XSBs of Midrange Server) 2–3 FIGURE 2-2 Example of a Hardware Configuration (with Uni-XSBs of High-end Server) 2–4 FIGURE 2-3 Example of a Hardware Configuration (with Quad-XSBs of High-end Server) 2–4 FIGURE 2-4 Flow of System Board Addition Processing 2–21...

  • Page 12: Figure

    Example: Reserve a System Board Add 4–20 FIGURE 4-10 Example: Reserving a System Board Delete 4–22 FIGURE 4-11 Example: Reserving a System Board Move 4–23 FIGURE 4-12 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007...
  • Page 13 Tables Basic DR Terms 1–3 TABLE 1-1 Terms Related to Hardware Configurations 1–4 TABLE 1-2 Unit of Degradation 2–14 TABLE 2-1 Domain Status 2–18 TABLE 2-2 System Board Management Items 2–18 TABLE 2-3 System Board Management Items 2–19 TABLE 2-4 DR Display Commands 3–1 TABLE 3-1 DR Operation Commands 3–2...
  • Page 14 Options of the moveboard Command 3–20 TABLE 3-15 DR Display Commands 3–25 TABLE 3-16 DR Operation Commands 3–25 TABLE 3-17 DR-related Commands 3–26 TABLE 3-18 xii SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007...
  • Page 15 “Text Conventions” on page xviii ■ “Prompt Notations” on page xix ■ “Syntax of the Command Line Interface (CLI)” on page xix ■ “Software License” on page xx ■ “Fujitsu Siemens Computers Welcomes Your Comments” on page xx ■ Preface xiii...
  • Page 16 Audience This manual is intended for users, who administrate SPARC Enterprise M4000/M5000/M8000/M9000 servers (hereinafter referenced to as XSCF user). The XSCF user is required to have the following knowledge: Solaris ■ SPARC Enterprise M4000/M5000/M8000/M9000 servers and basic knowledge of ■ XSCF Structure and Contents of This Manual This manual is organized as described below:...

  • Page 17: Glossary

    SPARC Enterprise M8000/M9000 Servers Safety and Compliance Guide External I/O Expansion Unit Safety and Compliance Guide SPARC Enterprise M4000 Server Unpacking Guide SPARC Enterprise M5000 Server Unpacking Guide SPARC Enterprise M8000/M9000 Servers Unpacking Guide SPARC Enterprise M4000/M5000 Servers Installation Guide SPARC Enterprise M8000/M9000 Servers Installation Guide SPARC Enterprise M4000/M5000 Servers Service Manual Order No.
  • Page 18 Book Titles SPARC Enterprise M8000/M9000 Servers Service Manual External I/O Expansion Unit Installation and Service Manual SPARC Enterprise M4000/M5000/M8000/M9000 Servers Administration Guide SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF Reference Manual SPARC Enterprise M4000/M5000/M8000/M9000 Servers Dynamic Reconfiguration (DR) User’s Guide SPARC Enterprise M4000/M5000/M8000/M9000 Servers Capacity on Demand (COD) User’s Guide...
  • Page 19 Contact the field engineer. The following files or document are provided. i. Firmware program file (XSCF Control Package (XCP) file) ii. XSCF extension MIB definition file Note – XSCF Control Package (XCP) : XCP is a package which has the control programs of hardware that configures a computing system.

  • Page 20: Text Conventions

    AaBbCc123 Italic " " xviii SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Model name SPARC Enterprise M4000 SPARC Enterprise M5000 SPARC Enterprise M8000 SPARC Enterprise M9000 Meaning What you type, when contrasted with on-screen computer output.

  • Page 21: Command Syntax

    Prompt Notations The prompt notations used in this manual are as follows. Shell XSCF C shell C shell super user Bourne shell and Korn shell Bourne shell and Korn shell super user OpenBoot PROM Syntax of the Command Line Interface (CLI) The command syntax is described below.

  • Page 22: Software License

    The function to explain in this manual uses the softwares of GPL,LGPL and others. For the information of the license, see Appendix E, "Software License Condition" in SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide. Fujitsu Siemens Computers Welcomes Your Comments We would appreciate your comments and suggestions to improve this document.
  • Page 23 Reader's Comment Form Preface...
  • Page 24 FOLD AND TAPE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO 741 SUNNYVALE CA POSTAGE WILL BE PAID BY ADDRESSEE FUJITSU COMPUTER SYSTEMS AT TENTION ENGINEERING OPS M/S 249 1250 EAST ARQUES AVENUE P O BOX 3470 SUNNYVALE CA 94088-3470 FOLD AND TAPE...

  • Page 25: Overview Of Dynamic Reconfiguration

    C H A P T E R Overview of Dynamic Reconfiguration This chapter provides an overview of Dynamic Reconfiguration, which is controlled by the eXtended System Control Facility (XSCF). Dynamic Reconfiguration (referred to as DR, in this document) enables hardware resources such as processors, memory, and I/O to be added and deleted even while the Solaris DR has three basic functions;...

  • Page 26: Uni-Xsb And Quad-Xsb (Midrange Servers)

    into four boards is called a Quad-XSB. Each composition of physical unit of the divided PSB is called an eXtended System Board (XSB). These XSBs can be combined freely to create domains. DR functions on these servers are performed on an XSB. This manual uses the term system board unless physical units of PSB and XSB are described.

  • Page 27: Uni-Xsb And Quad-Xsb

    Uni-XSB and Quad-XSB (High-end Servers FIGURE 1-2 Uni-XSB System boards list DR-related terms. TABLE 1-1 TABLE 1-2 Basic DR Terms TABLE 1-1 Term Definition To connect a system board to a domain and configure it into the Solaris OS of the domain. Delete To unconfigure a system board from the Solaris OS of a domain and disconnect it from the domain.
  • Page 28 Basic DR Terms TABLE 1-1 Term Unconfigure Reserve Install Remove Replace Terms Related to Hardware Configurations TABLE 1-2 Term CPU/Memory board unit (CMU) Motherboard Unit (MBU) I/O board unit (IOU) Unit equipped with a PCI card and a disk drive unit. Physical System Board (PSB) eXtended System...

  • Page 29: Basic Dr Functions

    Terms Related to Hardware Configurations (Continued) TABLE 1-2 Term System board Uni-XSB Quad-XSB Basic DR Functions This section describes the basic DR functions. shows DR processing. FIGURE 1-3 DR Processing Flow FIGURE 1-3 Domain B Domain A Definition The hardware resources of a PSB or an XSB. A System board is used to describe the hardware resources for operations such as domain construction and identification.

  • Page 30: Adding A System Board

    In the example shown in added to domain B. In this way, the physical configuration of the hardware (mounting locations) is not changed but the logical configuration is changed for management of the system boards. 1.2.1 Adding a System Board You can use DR to add a system board to a domain provided that board is installed in the system and not assigned to another domain.

  • Page 31: Replacing A System Board

    After field parts replacement or other such task, the system board is re- installed and added. Note – You cannot use DR to replace a system board in a midrange server because doing so would replace an MBU. To replace a system board in a midrange server, you must turn off the power of all domains, then replace the board without using DR commands.
  • Page 32 For details of XSCF shell commands provided for DR, see Section 3.1, “How To Use the DR User Interface” on page 3-1. XSCF Web is beyond the scope of this document. See the SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide for further information.

  • Page 33: What You Must Know Before Using Dr

    System Board Components There are three types of system board components that can be added and deleted by DR: CPU, memory, and I/O device. system board of a midrange server that is divided into one Uni-XSB, and into Quad- XSBs. FIGURE 2-3 server that is divided into one Uni-XSB, and into Quad-XSBs.

  • Page 34: Figure 2-1 Example Of Hardware Configuration (With Uni-Xsb Of Midrange Server)

    Example of Hardware Configuration (with Uni-XSB of Midrange Server) FIGURE 2-1 XSB 00-0 XSB 01-0 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Memory I/O device Memory I/O device Memory Memory Memory I/O device Memory I/O device...

  • Page 35: Example Of Hardware Configuration (With Quad-Xsbs Of Midrange Server)

    Example of Hardware Configuration (with Quad-XSBs of Midrange Server) FIGURE 2-2 Memory XSB 00-0 Memory XSB 00-1 Memory XSB 00-2 Memory XSB 00-3 Memory XSB 01-0 Memory XSB 01-1 Memory XSB 01-2 Memory XSB 01-3 I/O device I/O device I/O device...

  • Page 36: Cpu

    Example of a Hardware Configuration (with Uni-XSBs of High-end Server) FIGURE 2-3 XSB 00-0 Example of a Hardware Configuration (with Quad-XSBs of High-end Server) FIGURE 2-4 XSB 00-0 XSB 00-1 XSB 00-2 XSB 00-3 2.1.1.1 Using DR to change a CPU configuration is easier than using it to change the configuration of memory or an I/O device.

  • Page 37: Memory

    A CPU to be deleted must meet the following conditions: No running process is bound to the CPU to be deleted. If a running process is ■ bound to the target CPU, you must unbind or stop the process. The CPU to be deleted does not belong to any processor set. If the target ■...
  • Page 38 To control whether a system board contains kernel memory, use one or more of ■ the following features, which are described below: kernel cage, floating boards, and kernel memory assginment. To copy kernel memory from one board to another, use the Copy-rename ■...
  • Page 39 When the kernel cage is enabled, kernel memory is assigned to system boards in the order of their address spaces. The kernel cage begins in the first address space (which initially corresponds to the non-floating board with the lowest LSB number). If the kernel requires more memory, then the kernel cage expands to the next address space (which initially corresponds to the non-floating board with the next- lowest LSB number), and so on.
  • Page 40 Once the copy-destination board has been selected, the Solaris OS performs a memory deletion on the selected user memory board. Then, the kernel memory on the system board to be deleted is copied into memory on the selected copy-destination system board. The system is suspended while the copying is in progress.

  • Page 41: I/O Device

    Deleting or moving a user memory board fails if either of the following statements is true: The swap area does not have sufficient free space to save data from the user ■ memory to be deleted. There are too many locked or ISM pages to be covered by the memory on other ■...

  • Page 42: System Board Configuration Requirements

    Note – Do not move a device that is part of a redundant configuration from one domain to another domain. The consequences of two domains simultaneously accessing the same device through different paths could be disastrous, such as data corruption. 2.1.2 System Board Configuration Requirements XSCF enables the Uni-XSB or Quad-XSB setting according to the configuration...

  • Page 43: Checklists For System Configuration

    Moreover, a system board that is pooled can be assigned to a domain only when it is registered on DCL. Pooled system boards must be properly managed. You can add and delete system boards by combining the system board pooling function with the floating board, omit-memory, and omit-I/O options described in Section 2.2, “Conditions and Settings Using XSCF”...

  • Page 44: Reservation Of Domain Configuration Changes

    When kernel memory is copied, the Solaris OS is temporarily suspended. Therefore, you must understand the effect of disconnecting the network connection with remote systems and other influences of the DR operation on job processes before determining system operations. 2.1.5 Reservation of Domain Configuration Changes Besides letting you add, delete, or move system boards dynamically, DR also lets you order such reconfiguration to take place the next time the affected domains are...

  • Page 45: Settings Using Xscf

    operation. As a matter of course, system boards to be deleted, moved, or replaced have already been registered in the DCL. You need not confirm that these boards have been registered in the DCL. For details about the DCL and how to register system boards in the DCL and to confirm registration, refer to SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide.

  • Page 46: Floating Board Option

    Note – Enable the configuration policy option when the power supply of the domain is turned off. Unit of Degradation TABLE 2-1 Value System 2.2.2.2 Floating Board Option The floating board option controls kernel memory allocation. Upon deletion of a system board on which kernel memory is loaded, the OS is temporarily suspended.

  • Page 47: Omit-Memory Option

    2.2.2.3 Omit-memory Option When the omit-memory option is enabled, the memory on a system board cannot be used in the domain. Even when a system board actually has memory, this option enables you to make the memory on the system board unavailable through a DR operation to add or move the system board.

  • Page 48: Conditions And Settings Using Solaris Os

    Note – Enable the omit-I/O option when the system board is in the system board pool or when the system board is not connected to the domain configuration. Conditions and Settings Using Solaris This section describes the operating conditions and settings required for DR operations.

  • Page 49: Status Management

    If the kernel cage is disabled, the system may run more efficiently, but kernel memory will be spread among all boards and DR operations will not work on memory. To determine whether kernel cage memory is enabled after the system has been rebooted, check the following message output from the /var/adm/messages file: NOTICE: DR kernel Cage is ENABLED If the kernel cage is disabled, the message will be:...

  • Page 50: System Board Status

    XSCF manages the following aspects of domain status: Domain Status TABLE 2-2 Status Powered Off Initialization Phase OpenBoot Executing Completed Booting Running Shutdown Started Panic State To perform a DR operation for a system board, you must determine the method of DR operation according to the status of the relevant domain.

  • Page 51: Table 2-4 System Board Management Items

    The table below lists the status types available for individual management items. System Board Management Items TABLE 2-4 Management item Status Power Power Off Power On Test unmount unknown testing passed failed Assignment unavailable available assigned Connectivity disconnected connected Configuration unconfigured configured XSCF changes and configures system board status according to the conditions under...

  • Page 52: Flow Of Dr Processing

    To perform a DR operation for a system board, you must determine the method of DR operation according to the status of the target system board. You can display and reference the status of each system board via a user interface provided by XSCF.

  • Page 53: Flowchart: Deleting A System Board

    Flow of System Board Addition Processing FIGURE 2-5 System board pool Test: passed Addition or Assignment: available reserva- tion, DCL registration Request to add process system board Diagnosis Test: testing Assignment: assigned Diagnosis completed Domain configuration change process Test: passed Assignment: assigned Connectivity: disconnected Process of addition into OS...
  • Page 54 Each system board status indicated in Flow of System Board Deletion Processing FIGURE 2-6 Status of addition into OS Test: passed Deletion/ Assignment: assigned deletion Connectivity: connected reservation Configuration: configured Domain configuration change process Test: passed Assignment: a ssigned Connectivity: connected Deletion from Domain 2-22...

  • Page 55: Flowchart: Moving A System Board

    2.4.3.3 Flowchart: Moving a System Board The flow of DR operations and the transition of system board status when a system board has been moved or reserved for a move are described in the schematic flowchart, below. Each system board status indicated in is the main status that is changed.
  • Page 56 Flow of System Board Move Processing FIGURE 2-7 Move process Deletion of system board in original domain Deletion completed Process to change domain configuration in original domain Assignment: assigned Connectivity: disconnected Configuration: unconfigured from domain Process to change configuration of destination domain Assignment: unavailable Connectivity: disconnected Configuration: unconfigured to domain...

  • Page 57: Flowchart: Replacing System Board

    2.4.3.4 Flowchart: Replacing System Board The flow of DR operations and the transition of system board status when a system board has been replaced are described using the schematic flowchart. Each system board state indicated in is the main status that is changed. FIGURE 2-8 The sample status before and after replacement as shown in the figure are explained below.

  • Page 58: Figure 2-8 Flow Of System Board Replacement Processing

    Flow of System Board Replacement Processing FIGURE 2-8 Request to delete from DCL registration status DCL registration status Assignment: assigned Replacement process Replacement completed DCL registration status Test: passed Assignment: assigned Addition process 2-26 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Deletion process Deleting a system board System board pool...

  • Page 59: Operation Management

    Operation Management This section describes the premises and the actions for DR operations. 2.5.1 I/O Device Management Upon the addition of a system board, device information is reconfigured automatically. However, addition of the system board and the reconfiguration of device information do not end at the same time. Sometimes, device link in /dev directory is not automatically cleaned up by devfsadmd(1M) daemon.

  • Page 60: Real-Time Processes

    memory contents. Be aware that some of the total swap space may be supplied by disks that are attached to the board to be deleted. When making your assessment, be certain to also account for the swap space that will be lost. If the size of available memory (e.g., 1.5 gigabytes) is larger than the size of ■...

  • Page 61: Capacity On Demand (Cod)

    For example, when a kernel memory board with memory mirror mode enabled is deleted or moved, kernel memory is moved from the kernel memory board to another system board. Kernel memory is moved normally even if memory mirror mode is disabled for the move-destination system board. However, this operation results in lowered reliability of memory on the new kernel memory board.

  • Page 62: Deletion Of Board With Dvd Drive

    2.5.8 Deletion of Board with DVD Drive To delete the system board to which the server’s DVD drive is connected, execute the following steps: 1. Stop the vold(1M) daemon by disabling the volfs service. # /usr/sbin/svcadm disable volfs 2. Execute the DR operation.

  • Page 63: Dr User Interface

    C H A P T E R DR User Interface This chapter describes the user interfaces for DR. How To Use the DR User Interface XSCF provides two user interfaces for DR: the command line interface by XSCF shell, and the browser-based user interface by XSCF Web. This section describes the main XSCF shell commands used for DR.

  • Page 64: Displaying Domain Information

    DR Operation Commands TABLE 3-2 Command name setdcl setupfru addboard deleteboard moveboard The sections below describe the DR display and DR operation commands in detail and show examples. For details of the options, operands, and usage of these commands, refer to SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF Reference Manual.

  • Page 65: Table 3-3 Options Of The Showdcl Command

    Displays usage information. -d domain_id Displays information about the specified domain, where domain_id is the domain number, possibly 0 to 23, depending on server model. Only one domain ID can be specified. -l lsb Displays information about the specified logical system board (LSB), numbered 00 to 15.
  • Page 66 Items of Domain Information to be Displayed (Continued) TABLE 3-4 Display items Description Float Setting of floating board option true false Cfg-policy Setting of configuration policy System The table below lists the items displayed by the showdcl(8) command. The following shows examples of displays by the showdcl(8) command. Example 1: Display of information on domain #0 ■...

  • Page 67: Displaying Domain Status

    Description Displays the status of all domains. Displays information about the specified domain, where domain_id is the domain number, possibly 0 to 23, depending on server model. Only one domain ID can be specified. Displays usage information. Chapter 3 DR User Interface...

  • Page 68: Displaying System Board Information

    Items of Domain Information to be Displayed (Continued) TABLE 3-6 Display items Description Status Domain status Powered Off Initialization Phase OpenBoot Executing Completed Booting/OpenBoot PROM prompt Running Shutdown Started Panic State The following example shows a display of the showdomainstatus (8) command. Example: Display of information on all domains ■...

  • Page 69: Table 3-7 Options Of The Showboards Command

    Displays the usage information. -d domain_id Displays information about the specified domain, where domain_id is the domain number, possibly 0 to 23, depending on server model. Only one domain ID can be specified. Displays information about the specified XSB. Specify xsb in the XX-Y format. (XX = 00 to 15, Y = 0 to 3). The value depends on server model.
  • Page 70 Items of System Board Information to be Displayed (Continued) TABLE 3-8 Display items Assignment Conn Conf SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Description Status of assignment to domain configuration Unavailable The system board cannot be used. The system board may be unrecognizable because it is not mounted or it is faulty, the domain or system board may not have been configured, or the system...
  • Page 71 Items of System Board Information to be Displayed (Continued) TABLE 3-8 Display items Description Test Diagnostic status of system board Unmount Unknown Testing Passed Failed Fault Normal/abnormal status of system board Normal Degraded Failed Indication of whether the system board is a COD board. The following examples show displays of the showboards(8) command Example 1: Display of information on all system boards ■...

  • Page 72: Displaying Device Information

    Example 2: Display of detailed information on all system boards ■ XSCF> showboards -v -a DID(LSB) -------------------------------------------------------------------------- 00-0 00(00) 00-1 00(01) 00-2 00-3 01(15) Example 3: Display of information on the system board in the system board pool ■ in domain #0 XSCF>...
  • Page 73 -p force with the force flag without actually executing it. Specifies a system board (XSB) number. Specify xsb in the XX-Y format. (XX = 00 to 15, Y = 0 to 3). The value depends on server model. -d domain_id Specifies ID of the specified domain, where domain_id is the domain number, possibly 0 to 23, depending on server model.

  • Page 74: Table 3-10 Domain Information Displayed By The Showdevices Command

    Domain Information Displayed by the showdevices command TABLE 3-10 Display items Memory IO Devices The following example shows a display by the showdevices(8) command. 3-12 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Description CPU information. Domain ID. System board number.

  • Page 75: Displaying System Board Configuration Information

    Example: Display of device information on XSB00-0 ■ XSCF> showdevices 00-0 CPU: ---- 00-0 00-0 Memory: ------- remaining mem MB 00-0 I/O Devices: ---------- 00-0 00-0 00-0 00-0 10.1.1.1 3.1.5 Displaying System Board Configuration Information Use the showfru(8) command to display system board configuration information. The showfru(8) command displays information about the PSB division type and memory mirroring mode settings in list format.

  • Page 76: Table 3-11 Options Of The Showfru Command

    Options of the showfru Command TABLE 3-11 Option device location The table below lists the items displayed by the showfru(8) command. Items of System Board Configuration Information to be Displayed TABLE 3-12 Display items Description Device Device type. “sb” is the corresponding device for DR. Location Mounting location of a device.

  • Page 77: Adding A System Board

    3.1.6 Adding a System Board Use the addboard(8) command to add a system board to a domain or reserve the addition of a system board to a domain based on the DCL. The system board must already be registered in the target domain’s DCL. Use the showdcl(8) command to check whether a system board is registered in the DCL.

  • Page 78: Table 3-13 Options Of The Addboard Command

    Specify xsb in the XX-Y format. (XX = 00 to 15, Y = 0 to 3). The value depends on server model. To specify multiple system boards, several XSB numbers can be specified by delimiting each with a space.

  • Page 79: Deleting A System Board

    Note – (Note 3) If a system board has been forcibly added to a domain by the addboard(8) command with the -f option specified, normal operation of all added hardware resources may be disabled. For this reason, you should avoid using the -f option for normal DR operations.

  • Page 80: Table 3-14 Options Of The Deleteboard Command

    Specify xsb in the XX-Y format. (XX = 00 to 15, Y = 0 to 3). The value depends on server model. To specify multiple system boards, several XSB numbers can be specified by delimiting each with a space.

  • Page 81: Moving A System Board

    Note – (Note 1) The time required for system board deletion processing depends on the amount of hardware resources mounted on the target system board. For this reason, much time may be required for the command to end its operation. If the system board contains kernel memory, the OS is suspended for a while.
  • Page 82 The following examples show the format and options of the moveboard(8) command. moveboard [[-q] -{y|n}][-f][-v][-c configure] -d domain_id xsb[xsb...] moveboard [[-q] -{y|n}][-f][-v] -c assign -d domain_id xsb[xsb...] moveboard [[-q] -{y|n}][-f][-v] -c reserve -d domain_id xsb[xsb...] moveboard -h Options of the moveboard Command TABLE 3-15 Option -c configure...
  • Page 83 Specify xsb in the XX-Y format. (XX = 00 to 15, Y = 0 to 3). The value depends on server model. To specify multiple system boards, several XSB numbers can be specified by delimiting each with a space.

  • Page 84: Replacing A System Board

    I/O devices, or replace the PSB of a CMU or IOU. Note – In a midrange server, you cannot use DR commands to replace a system board. Instead, turn off the power of all domains, and then replace the target system board.
  • Page 85 Note – (Note 1) Before replacing a system board, you must know the division type of the replacement-target PSB and the configurations and operation status of all domains to which all XSBs on the PSB belong. If the division type of the replacement-target PSB is Quad-XSB and the XSBs on the replacement-target PSB belong to multiple domains, you must consult with all administrators of the relevant domains in advance to adequately adjust the method of replacing the system board.

  • Page 86: Reserving A Domain Configuration Change

    3.1.10 Reserving a Domain Configuration Change Use the addboard(8), deleteboard(8), or moveboard(8) command to reserve a domain configuration change. A domain configuration change is reserved when a system board cannot be added, deleted, or moved immediately for operational reasons. The reserved addition, deletion, or move of the system board is executed when the power of the target domain is turned on or off, or the domain rebooted.

  • Page 87: Command Reference

    Command Reference This section lists the DR commands and other commands related to DR. For details of the commands, refer to SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF Reference Manual. For the DR commands, see the DR User Interface” on page Note – (Note 1) each command, you must have appropriate administrator privileges.
  • Page 88 Displays license usage information. Configures COD settings. Displays COD settings. Displays all components mounted in the server. Lists degraded components. Displays an error log, power log, event log, console log, panic log, IPL log, temperature/humidity log, and monitoring message log.

  • Page 89: Xscf Web

    XSCF Web XSCF Web lets you execute DR functions from a browser. XSCF Web is beyond the scope of this document. For details, refer to SPARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User’s Guide. RCM Script Reconfiguration Coordination Manager (RCM) is a framework used to manage the dynamic disconnection of system components.
  • Page 90 3-28 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007...

  • Page 91: Practical Examples Of Dr

    DR operations and not hardware operations (e.g., installing, removing, and replacing system boards). Refer to the service manual for each server as needed. Flow of DR Operation This section provides the flows of basic DR operations to add, delete, move, and...

  • Page 92: Flow: Adding A System Board

    4.1.1 Flow: Adding a System Board Flow: Adding a System Board FIGURE 4-1 Error Hardware maintenance SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Checking operation and selecting a DR operation - Operation status and configuration of a domain - Judgment of whether the DR operation can be performed...

  • Page 93: Flow: Deleting A System Board

    4.1.2 Flow: Deleting a System Board Flow: Deleting a System Board FIGURE 4-2 Stop status of a domain Checking operation and selecting a DR operation - Operation status and configuration of a domain - Judgment of whether the DR operation can be performed DR operation possible...

  • Page 94: Flow: Moving A System Board

    4.1.3 Flow: Moving a System Board Flow: Moving a System Board FIGURE 4-3 Checking operation and selecting a DR operation - Operation status and of the move-source domain - Operation status and configuration of the move-destination domain - Judgment of whether the DR operation can be performed Confirmation of the move-source and move-destination domains...

  • Page 95: Flow: Replacing A System Board

    4.1.4 Flow: Replacing a System Board Flow: Replacing a System Board FIGURE 4-4 Stop status of the domain Power-off of the relevant domain Start of domain Power-on of the relevant domain Checking operation and selecting a DR operation - Operation status and configuration of a domain - Adjustment between other domains - Configuration of the system board to be replaced - Checking the device status...

  • Page 96: Example: Adding A System Board

    Example: Adding a System Board This section provides an example of the DR operation to add a system board to a domain. In the example, a procedure conforming to section Adding a System added by using the XSCF shell. Example: Adding a System Board FIGURE 4-5 Domain#0 XSB#00-0...
  • Page 97 If you need to change the PSB configuration, use the setupfru(8) command. If the system board to be added is not registered in the DCL, register the system board in the DCL of the target domain by using the setdcl(8) command. XSCF>...

  • Page 98: Example: Deleting A System Board

    Example: Deleting a System Board This section provides an example of operation to delete a system board from a domain. In the example, a procedure conforming to System Board” on page deleted using the XSCF shell. Example: Deleting a System Board FIGURE 4-6 Domain#0 XSB#00-0...
  • Page 99 3. Check the status of the system board to be deleted. Execute the showboards(8) command to display system board information, and then check the status of the system board to be deleted. XSCF> showboards -a DID(LSB) Assignment ------------------------------------------------------------------- 00-0 00(00) Assigned 01-0 00(01)

  • Page 100: Example: Moving A System Board

    Example: Moving a System Board This section provides an example of an operation to move a system board between domains. In the example, a procedure conforming to System Board” on page moved using the XSCF shell. Example: Moving a System Board FIGURE 4-7 Domain#0 XSB#00-0...
  • Page 101 3. Check the status of the move-destination domain. Execute the showdcl(8) command to display domain information, and then check the operation status of the move-destination domain. Based on the operation status of the move-source and move-destination domains, determine whether to perform the DR operation or change the domain configuration. XSCF>...

  • Page 102: Examples: Replacing A System Board

    4-5, is used, and the system board shown in each figure is replaced using the XSCF shell. Note – You cannot use DR to replace a system board in a midrange server because replacing a system board replaces an MBU. To replace a system board in a midrange server, you must turn off the power for all domains, then perform a hardware replacement.

  • Page 103: Example: Replacing A Uni-Xsb System Board

    4.5.1 Example: Replacing a Uni-XSB System Board Example: Replacing a Uni-XSB System Board FIGURE 4-8 Domain#0 XSB#00-0 1. Login to XSCF. 2. Check the status of the domain. Execute the showdcl(8) command to display domain information, and then check the operation status of the domain. Based on the operation status of the domain, determine whether to perform the DR operation or replace the system board after stopping the domain.
  • Page 104 4. Delete the system board. Execute the deleteboard(8) command to delete the system board. XSCF> deleteboard -c disconnect 01-0 5. Check the status of the system board. Execute the showboards(8) command to display system board information, and then check the status of the system board. XSCF>...
  • Page 105 8. Check the status of the domain. Execute the showdcl(8) command to display domain information, and then check the operation status of the domain. Based on the operation status of the domain, determine whether to perform the DR operation or reboot the domains. XSCF>...

  • Page 106: Example: Replacing A Quad-Xsb System Board

    4.5.2 Example: Replacing a Quad-XSB System Board Example: Replacing a Quad-XSB System Board FIGURE 4-9 Domain#0 XSB#00-0 1. Login to XSCF. 2. Check the configurations and status of all domains to which the relevant system boards belong. Execute the showdcl(8) command to display domain information, and then check the configurations and operation status of all domains to which the relevant XSBs belong.
  • Page 107 XSCF> showdcl -a Status Running 00-0 01-0 01-1 ------- Running 01-2 01-3 3. Check the status of all related system boards. Execute the showboards(8) command to display system board information, and then check the status of all system boards related to the PSB to be replaced. The DR operation for replacement may not be possible if the board to be replaced does not support the DR delete operation.
  • Page 108 6. Check the status of all related system boards. Execute the showboards(8) command to display system board information, and then check the status of all related system boards. XSCF> showboards -a DID(LSB) ------------------------------------------------------------------ 00-0 00(00) 01-0 00(01) 01-1 00(02) 01-2 01(00) 01-3 01(01)
  • Page 109 9. Check the status of all related domains. Execute the showdcl(8) command to display domain information, and then check the operation status of all related domains. Based on the operation status of the domain, determine whether to perform the DR operation or reboot the domains.

  • Page 110: Examples: Reserving Domain Configuration Changes

    XSCF> showboards -a DID(LSB) ------------------------------------------------------------------ 00-0 00(00) 01-0 00(01) 01-1 00(02) 01-2 01(00) 01-3 01(01) Examples: Reserving Domain Configuration Changes This section provides examples of operations to reserve a change in domain configuration by DR. In the examples, the XSCF shell is used to reserve the addition, deletion, and movement of a system board as shown in the given configuration diagram.
  • Page 111 2. Check the status of the system board to be added. Execute the showboards(8) command to display system board information, and then check the status of the system board to be added and confirm its registration in the DCL. If you need to change the PSB configuration, use the setupfru(8) command. If the system board is not registered in the DCL, register the system board in the DCL for the target domain by using the setdcl(8) command.

  • Page 112: Example: Reserving A System Board Delete

    4.6.2 Example: Reserving a System Board Delete Example: Reserving a System Board Delete FIGURE 4-11 Domain#0 XSB#00-0 1. Login to XSCF. 2. Check the status of the domain. Execute the showdcl(8) command to display domain information, and then check the operation status of the domain. Based on the operation status of the domain, determine whether to perform the DR operation or change the domain configuration.

  • Page 113: Example: Reserving A System Board Move

    5. Check the reserved status of the system board. Execute the showboards(8) command with the -v option specified to display system board information, and then confirm that deletion of the system board has been reserved. XSCF> showboards -v 01-0 DID(LSB) -------------------------------------------------------------------------- 01-0 00(01)
  • Page 114 3. Check the status of the move-destination domain. Execute the showdcl(8) command to display domain information, and then check the operation status of the move-destination domain. Based on the operation status of the move-source and move-destination domains, determine whether to perform the DR operation or change the domain configuration. XSCF>...
  • Page 115 8. Check the status of the move-destination domain and moved system board. Execute the showdcl(8) command to check the operation status of the move- destination domain, and then execute the showboards(8) command to check the status of the system board and confirm that addition of the system board has been reserved in the move-destination domain.
  • Page 116 4-26 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007...

  • Page 117: Message Meaning And Handling

    A P P E N D I X Message Meaning and Handling This appendix explains the meaning and handling of DR-related messages. Solaris OS Messages This section explains the console messages printed by the DR driver. The output for messages that do not have an output field is console. A.1.1 Transition Messages DR: PROM detach board X...
  • Page 118 OS unconfigure dr@0:SBX::memory [Explanation] Unconfigure memory on system board X. OS unconfigure dr@0:SBX::pciY [Explanation] Unconfigure PCI Y on system board X. suspending <device name>@<device info> (aka <alias>) [Explanation] Suspending the device suspending <device name>@<device info> [Explanation] Suspending the device resuming <device name>@<device info> (aka <alias>) [Explanation] Resuming the device resuming <device name>@<device info>...

  • Page 119: Panic Messages

    [Explanation] Suspending device drivers DR: in-kernel unprobe board <board> [Explanation] Unprobing the board. A.1.2 PANIC Messages URGENT_ERROR_TRAP is detected during FMA. [Explanation] A fatal HW error was encountered during copy-rename. [Remedy] Please contact customer service. Failed to remove CMP X LSB NN [Explanation] There may be inconsistency in the system.

  • Page 120: Warning Messages

    [Explanation] Internal error during kernel migration [Remedy] Please contact customer service. CPU nn hang during Copy Rename [Explanation] A fatal HW error was encountered during copy-rename. [Remedy] Please contact customer service. A.1.3 Warning Messages # megabytes not available to kernel cage [Explanation] Lack of memory resource deleted.
  • Page 121 [Remedy] Disable interrupt on cpu X with psradm -I and if this command fails again, respond in the manner directed by command message. dr_cancel_cpu: failed to online cpu X [Explanation] Failed to online CPU X. [Remedy] Repeat the action. If this error message appears again, please contact customer service.
  • Page 122 [Explanation] There may be inconsistency in the system. [Remedy] Please contact customer service. dr_status: failed to copyout status for board # [Explanation] There may be inconsistency in the system. [Remedy] Please contact customer service. dr_status: unknown dev type (#) [Explanation] There may be inconsistency in the system. [Remedy] Please contact customer service.
  • Page 123 dr_pre_release_cpu: thread(s) bound to cpu X [Explanation] The thread in the process is bound to the detached CPU X. [Remedy] Check if the process bound to the CPU exists by pbind(1M) command. If it exists, unbind from the CPU and repeat the action. dr_pre_release_mem: unexpected kphysm_del_release return value # [Explanation] There may be inconsistency in the system.
  • Page 124 [Remedy] Please repeat the action. If the problem remains, please contact customer service. dr_release_mem_done: <device path>: error <error code> noted [Explanation] Error noted for a device during releasing memory. [Remedy] Please contact customer service. drmach_log_sysevent failed (rv #) for SBX [Explanation] There may be minor error in the system.
  • Page 125 Cannot stop user thread: <pid> <pid> ... [Explanation] The DR driver cannot stop all the user processes in the list. [Remedy] Please contact customer service. [Output] Console and Standard Output Cannot setup memory node [Explanation] DR is unable to read the HW information for the memory device. [Remedy] Please contact customer service.
  • Page 126 Invalid argument [Explanation] Invalid argument is passed to the driver or there may be inconsistency in the system. [Remedy] Repeat the action. If this error message appears again, please contact customer service. [Output] Console and Standard Output Invalid argument: ######## [Explanation] Invalid argument is passed to the driver.
  • Page 127 [Explanation] There may be inconsistency in the system. [Remedy] Please contact customer service. [Output] Console and Standard Output Cannot read property value: device node XXXXXX property: name [Explanation] Fail to get the property from OBP. [Remedy] Please contact customer service. [Output] Console and Standard Output Cannot read property value: property: scf-cmd-reg [Explanation] There may be inconsistency in the system.
  • Page 128 [Explanation] DR fails to allocate enough memory to perform copy rename. [Remedy] Retry and if the problem persists, contact customer service. Failed to off-line: dr@0:SBX::cpuY [Explanation] Failed to off-line CPU Y on board X. [Remedy] Repeat the action. If this error message appears again, please contact customer service.
  • Page 129 [Explanation] Detected lack of memory resource. [Remedy] Check the size of memory, detach the board and attach again. If the problem still exists, please contact customer service. [Output] Console and Standard Output Internal error: dr.c # [Explanation] There may be inconsistency in the system. [Remedy] Please contact customer service.
  • Page 130 Memory operation refused: dr@0:SBX::memory [Explanation] The DR operation is refused. [Remedy] Respond in the manner directed by the other message. Memory operation cancelled: dr@0:SBX::memory [Explanation] The DR operation is canceled. [Remedy] Respond in the manner directed by the other message. No device(s) on board: dr@0:SBX [Explanation] There may be inconsistency in the system.
  • Page 131 [Remedy] Repeat the action. If this error message appears again, please contact customer service. [Output] Console and Standard Output Insufficient memory: dr@0:SBX::cpuY [Explanation] Lack of memory resources detected. [Remedy] Check the size of available memory and detach the board. If the problem still exists, please contact customer service.
  • Page 132 Operation already in progress: dr@0:SBX::cpuY [Explanation] The operation on cpu Y on system board X is in progress. [Remedy] Repeat the action. If the problem still exists, please contact customer service. [Output] Console and Standard Output dr_move_memory: failed to quiesce OS for copy-rename [Explanation] There is a task not suspended in the process.
  • Page 133 [Output] Console and Standard Output Cannot setup resource map opl-fcodemem [Explanation] Resource memory mapping cannot be set up. [Remedy] Please contact customer service. opl_cfg failed to load, error=<errno> [Explanation] opl_cfg module failed to load. [Remedy] Please contact customer service. IKP: failed to read HWD header [Explanation] The header of the hardware descriptor could not be read.
  • Page 134 [Explanation] A claim request with a nonzero hint came from the fcode interpreter. [Remedy] If DR failed after this message, please contact customer service. opl_claim_memory - unable to allocate contiguous memory [Explanation] Memory allocation failed for the fcode interpreter. [Remedy] If DR failed after this message, please contact customer service. opl_get_fcode: Unable to copy out fcode image [Explanation] Failed to copy out the fcode image to the efcode daemon.
  • Page 135 [Explanation] The node was not destroyed. [Remedy] Please contact customer service. IKP: destroy chip (<board>-<chip>) failed [Explanation] The node was not destroyed. [Remedy] Please contact customer service. dr_del_mlist_query: mlist=NULL [Explanation] The memory list to be deleted is NULL. This warning is also shown at memoryless board.
  • Page 136 [Remedy] Please contact customer service. I/O callback failed in post-attach [Explanation] I/O callback failed in post-attach [Remedy] Please contact customer service. Kernel Migration fails. 0x%x [Explanation] Internal error happened during kernel migration. [Remedy] Please contact customer service. Failed to add CMP%d on board %d [Explanation] CPU failed to power-on during DR attach.
  • Page 137 [Remedy] Please contact customer service. Failed to remove CMP xx on board n [Explanation] Internal error during DR operation. [Remedy] Please contact customer service. scf_fmem_cancel() failed rv=0x<error code> [Explanation] Internal error during kernel migration. [Remedy] Please contact customer service. scf_fmem_start error [Explanation] SCF fails to start the FMEM operation.
  • Page 138 [Explanation] An unknown resource type was found in the resource list that is being freed while the board is unprobed. [Remedy] Please contact customer service. VM viability test failed: dr@0:SBX::memory [Explanation] There is not enough real memory to detach memory on system board X.

  • Page 139: Command Messages

    SCF error [Explanation] Internal error happened during kernel migration. [Remedy] Please contact customer service. Command Messages A.2.1 addboard XSB#XX-X will be assigned to DomainID X. Continue? [y|n]: [Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it. XSB#XX-Xwill be configured into DomainID X.
  • Page 140 XSB#XX-X is currently unavailable for DR. Try again later. [Explanation] The specified system board (XSB#XX-X) has already been executed by another operation. [Remedy] DR or power-off has been executing for another session. Try again after waiting for a while, with the confirmation of the XSB status. XSB#XX-X has not been registered in DCL.
  • Page 141 [Remedy] Find out the cause of the DR failure referring monitoring message and errorlog. Confirm the patch applying status and the XCP version DR failed. Domain (DomainID X) cannot communicate via DSCP path. [Explanation] DR processing cannot communicate with the domain. The reasons are that domain is powered off, the DSCP setting is wrong or the error occurs at the DSCP path.

  • Page 142: Deleteboard

    An internal error has occurred. Please contact your system administrator. [Explanation] DR failed. There is a possibility that DR failed because of an internal error in XSCF. [Remedy] Find out the cause of the DR failure referring monitoring message and error log.
  • Page 143 [Explanation] The specified system board (XSB#XX-X) has already been executed by another operation. [Remedy] DR or power-off has been executing for another session. Try again after waiting for a while, with the confirmation of the XSB status. XSB#XX-X has not been registered to DCL. [Explanation] System board (XSB#XX-X) is not registered to DCL.

  • Page 144: Moveboard

    Invalid parameter. [Explanation] There is an error in the specified argument or operand. [Remedy] Confirm the specified argument or operand and execute the command once again. Permission denied. [Explanation] Do not have privilege. [Remedy] Confirm the user privilege and the command privilege. In the case of high-end servers, please also confirm whether command is executed by XSCF on standby side.
  • Page 145 [Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it. DR operation canceled by operator. [Explanation] DR operation canceled by operator. Domain (DomainID X) is not currently running. [Explanation] Destination domain #X was not active when "-c configure"...
  • Page 146 [Remedy] Power off the domain by specifying "-c reserve". XSB#XX-X detected timeout by DR self test. [Explanation] The timeout occurred during DR processing because the hardware diagnosis did not complete. There is something wrong with the hardware. [Remedy] Find out the cause of the DR failure referring monitoring message and errorlog.
  • Page 147 [Remedy] Find out the cause of the DR failure referring monitoring message and console message. Try again after taking out cause. Invalid parameter. [Explanation] There is an error in the specified argument or operand. [Remedy] Confirm the specified argument or operand and execute the command once again.

  • Page 148: Setdcl

    [Explanation] Confirming whether DR operation is going to be executed or not. Input "y" to execute it and "n" to stop it. XSB#XX-Xwill be configured into DomainID X. Continue? [y|n]: [Explanation] Confirming whether DR operation is going to be executed or not. Input "y"...

  • Page 149: Setupfru

    Invalid parameter. [Explanation] There is an error in the specified argument or operand. [Remedy] Confirm the specified argument or operand and execute the command once again. Permission denied. [Explanation] Do not have privilege. [Remedy] Confirm the user privilege and the command privilege. In the case of high-end servers, please also confirm whether command is executed by XSCF on standby side.

  • Page 150: Showdevices

    The specified parameter is not supported in this model. [Explanation] Unsupported parameter in this server is specified. For this reason, the command was canceled. [Remedy] Confirm the specified parameter and the server model, and execute the command once again. Invalid parameter.
  • Page 151 [Remedy] Confirm that the DSCP setting is correct, confirm that the dsc process is running fine on the domain. Appendix A Message Meaning and Handling A-35...
  • Page 152 A-36 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007...

  • Page 153: Example: Confirm Swap Space Size

    A P P E N D I X Example: Confirm Swap Space Size This example shows one way to analyze the physical memory on a system board to determine whether the system has enough swap space to support deletion of a board.
  • Page 154 XSCF> showdevices 00-0 CPU: ---- 00-0 00-0 00-0 00-0 Memory: ------- 00-0 IO Devices: ---------- 00-0 Notice in the Memory section that 2048 MB (2GB) of physical memory is on this board. And in the I/O Devices section the /dev/dsk/c0t3d0s1 disk contains a configured swap space.
  • Page 155 Glossary This glossary describes some of the terms used in this manual. Capacity on Demand (COD) An option that provides additional CPU processing resources when needed. These additional CPUs are provided on COD CPU boards that are installed in the system. To access the COD CPUs, you must purchase the COD right-to use (RTU) licenses for them.
  • Page 156 System Control facility unit (XSCFU) The XSCF board for this server which contains system administration function and operates with independent processor. field-replaceable unit (FRU) A part that can be replaced by field engineers when servicing the system. firmware Firmware is the software to control the system. These servers have the following firmware;...
  • Page 157 privileges Specific permissions granted to users. This system has platform administrator, platform operator, domain administrator, domain operator, domain manager, user administrator, audit administrator, audit operator and field engineer privileges during the XSCF program running. Quad-XSB One of the division types for a PSB to be configured. Quad-XSB is a name for when a PSB is logically divided into four parts.
  • Page 158 Glossary-4 • SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide September 2007...
  • Page 159 Index Add, 1-3 addboard, 3-2, 3-15, 3-22 addfru, 3-26 addition, 1-6, 2-20, 2-27, 3-15, 4-2, 4-6 Assign, 1-3 Basic DR Terms, 1-3 Capacity on Demand, 2-29 configuration policy, 2-13 Configure, 1-3 Copy-rename, 2-7 CPU, 2-4 DCL, 1-3, 2-10 degradation, 2-13 Delete, 1-3 deleteboard, 3-2, 3-17, 3-22 deletefru, 3-26...
  • Page 160 move, 1-6, 2-23, 3-19, 4-4, 4-10 moveboard, 3-2, 3-19 omit-I/O, 2-15 omit-memory, 2-15 Physical System Board, 1-4 poweroff, 3-26 poweron, 3-26 PSB, 1-4 Quad-XSB, 1-5, 2-1, 2-10, 4-16 RCM Script, 3-27 real-time processes, 2-28 Register, 1-3 Release, 1-3 Remove, 1-4 Replace, 1-4 replacefru, 3-26 replacement, 1-7, 3-22, 4-12...
  • Page 162 Herausgegeben von / Published by Fujitsu Siemens Computers GmbH Bestell-Nr./ Order No.: U41684-J-Z816-2-76 *U41684-J-Z816-2-76 * U41684-J-Z816-2-76...

This manual is also suitable for:

Sparc enterprise m4000Sparc enterprise m8000Sparc enterprise m9000

Table of Contents