Gebruiksaanwijzing /service van het product M4000 van de fabrikant Fujitsu Siemens Computers
Ga naar pagina of 162
Dynamic Reconfiguration (DR) User’s Guide SPARC Enterprise M4000 / M5000 / M8000 / M9000 Servers Englis h.
.
SP ARC ® Enter pr ise M4000/M5000/M8000/M9000 Ser v ers Dynamic Reconfiguration (DR) User's Guide Order No . U41684-J-Z816-2-76 P ar t No .819-7898-11 September 2007, Revision A.
Please Recycle Copyright 2007 FUJITSU LIMITED, 1-1, Kamikodanaka 4-chome, Nakahara-ku, Kawasaki-shi, Kanagawa-ken 21 1-8588, Japan. All rights reserved. Sun Microsystems, Inc. pr ovided technical input and review on portions of this material. Sun Microsystems, Inc.
Copyright 2007 FUJITSU LIMITED, 1-1, Kamikodanaka 4-chome, Nakahara-ku, Kawasaki-shi, Kanagawa-ken 21 1-8588, Japon. T ous droits réservés. Entrée et revue tecnical fournies par Sun Microsystems, Incl sur des parties de ce matériel. Sun Microsystems, Inc.
.
v Contents Preface xiii 1. Overview of Dynamic Reconf iguration 1–1 1.1 DR 1–1 1.2 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 1.
vi SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 2.1.4 Checklists for System Configuration 2–1 1 2.1.5 Reservation of Domain Configuration Changes 2–12 2.2 Conditions and Settings Using XSCF 2–12 2.2.1 Conditions Using XSCF 2–12 2.
Contents vii 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 3. DR User Interface 3–1 3.1 How T o Use the DR User Interface 3–1 3.1.1 Displaying Domain Information 3–2 3.1.2 Displaying Domain Status 3–5 3.
viii SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.5 Examples: Replacing a System Board 4–12 4.5.1 Example: Replacing a Uni-XSB System Board 4–13 4.5.2 Example: Replacing a Quad-XSB System Board 4–16 4.
ix Figur es FIGURE 1-1 Uni-XSB and Quad-XSB (Midrange Servers) 1–2 FIGURE 1-2 Uni-XSB and Quad-XSB (High-end Servers 1–3 FIGURE 1-3 DR Processing Flow 1–5 FIGURE 2-1 Example of Hardware Configur.
x SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 FIGURE 4-10 Example: Reserve a System Board Add 4–20 FIGURE 4-11 Example: Reserving a System Board Delete 4.
xi T ables T ABLE 1-1 Basic DR Terms 1–3 T ABLE 1-2 Terms Related to Hardware Configurations 1–4 T ABLE 2-1 Unit of Degradation 2–14 T ABLE 2-2 Domain Status 2–18 T ABLE 2-3 System Board Manag.
xii SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 T ABLE 3-15 Options of the moveboard Command 3–20 T ABLE 3-16 DR Display Commands 3–25 T ABLE 3-17 DR O.
Preface xiii Pr eface This manual describes the Dynamic Reconfiguration (DR hereafter) function provided by SP ARC Enterprise servers. This manual is intended for users, specifically system management administrators who conduct operations on systems and domains.
xiv SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Audience This manual is intended for users, who administrate SP ARC Enterprise M4000/M5000/M8000/M9000 servers (hereinafter refer enced to as XSCF user).
Preface xv Glossary and Index ■ Glossary The glossary explains the terms used in this manual ■ Index The index provides keywor ds and corresponding r eference page numbers so that the reader can easily sear ch for items in this manual as necessary .
xvi SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Note – " x " in the order number is the version number of the manual. 1. Manuals on the W eb The latest versions of all the SP ARC Enterprise Series manuals are available at the following websites.
Preface xvii Contact the field engineer . The following files or document are pr ovided. i. Firmware pr ogram file (XSCF Control Package (XCP) f ile) ii. XSCF extension MIB definition file Note – XSCF Control Package (XCP) : XCP is a package which has the contr ol programs of har dware that conf igures a computing system.
xviii SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Models The model names used in this manual are as follows. T ext Conventions This manual uses the following fonts and symbols to express specif ic types of information.
Preface xix Pr ompt Notations The prompt notations used in this manual are as follo ws. Syntax of the Command Line Interface (CLI) The command syntax is described below . Command syntax The command syntax is as follows: ■ A variable that requir es input of a value must be enclosed in <>.
xx SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 ■ The command syntax is shown in a frame such as this one. Example:: Softwar e License The function to explain in this manual uses the softwares of GPL,LGPL and others.
Preface xxi Reader's Comment Form.
xxii SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 FOLD AND T APE FOLD AND T APE BUSINESS REPLY MAIL FIRST -CLASS MAIL PERMIT NO 74 1 SUNNYV ALE CA NO POST A.
1-1 CHAPTER 1 Overview of Dynamic Reconf iguration This chapter provides an overview of Dynamic Reconfiguration, which is controlled by the eXtended System Control Facility (XSCF).
1-2 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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 cr eate domains.
Chapter 1 Overview of Dynamic Reconfiguration 1-3 FIGURE 1-2 Uni-XSB and Quad-XSB (High-end Servers T ABLE 1-1 and T ABLE 1-2 list DR-related terms. T ABLE 1-1 Basic DR T erms T erm Definition Add T o connect a system board to a domain and conf igure it into the Solaris OS of the domain.
1-4 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Unconfigur e T o unconfigur e a system board in the Solaris OS. Reserve T o reserve a system board such that it is assigned to or unassigned from a domain on the next r eboot or power-cycle.
Chapter 1 Overview of Dynamic Reconfiguration 1-5 1.2 Basic DR Functions This section describes the basic DR functions. FIGURE 1-3 shows DR processing.
1-6 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 In the example shown in FIGURE 1-3 , system board #2 is deleted fr om domain A and added to domain B.
Chapter 1 Overview of Dynamic Reconfiguration 1-7 1.2.4 Replacing a System Boar d Y ou can use DR to remove a system board from a domain and either add it back later , or replace it with another system board, provided both boar ds satisfy DR requir ements as described in this document.
1-8 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 For details of XSCF shell commands provided for DR, see Section 3.1, “How T o Use the DR User Interface” on page 3-1 . XSCF W eb is beyond the scope of this document.
2-1 CHAPTER 2 What Y ou Must Know Befor e Using DR This chapter provides information you must know to successfully use the DR functions. 2.1 System Conf iguration This section describes the conditions, premises, and actions for operating the DR functions to construct a system.
2-2 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 FIGURE 2-1 Example of Har dware Configuration (with Uni-XSB of Midrange Server) CMU IOU Memory Memory Memor.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-3 FIGURE 2-2 Example of Har dware Configuration (with Quad-XSBs of Midrange Server) CMU IOU Memory XSB 00-2 Memory XSB 00-3 XSB 00-0 Memory I/O device .
2-4 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 FIGURE 2-3 Example of a Har dware Configuration (with Uni-XSBs of High-end Server) FIGURE 2-4 Example of a Har dware Configuration (with Quad-XSBs of High-end Server) 2.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-5 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 pr ocess.
2-6 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 ■ T o control whether a system board contains kernel memory , use one or more of the following features, which ar e described below: kernel cage, floating boar ds, and kernel memory assginment.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-7 When the kernel cage is enabled, kernel memory is assigned to system boards in the order of their addr ess spaces. The kernel cage begins in the first addr ess space (which initially corresponds to the non-floating boar d with the lowest LSB number).
2-8 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-9 Deleting or moving a user memory board fails if either of the following statements is true: ■ The swap area does not have suf ficient fr ee space to save data from the user memory to be deleted. ■ There ar e too many locked or ISM pages to be covered by the memory on other system boards.
2-10 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Note – Do not move a device that is part of a redundant configuration fr om one domain to another domain. The consequences of two domains simultaneously accessing the same device through differ ent paths could be disastrous, such as data corruption.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-11 Moreover , a system board that is pooled can be assigned to a domain only when it is register ed on DCL.
2-12 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 When kernel memory is copied, the Solaris OS is temporarily suspended.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-13 operation. As a matter of course, system boards to be deleted, moved, or replaced have alr eady been register ed in the DCL.
2-14 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Note – Enable the configuration policy option when the power supply of the domain is turned off. 2.2.2.2 Floating Board Option The floating boar d option controls kernel memory allocation.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-15 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.
2-16 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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 conf iguration.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-17 If the kernel cage is disabled, the system may run more ef ficiently , but kernel memory will be spread among all boar ds and DR operations will not work on memory .
2-18 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 XSCF manages the following aspects of domain status: T o perform a DR operation for a system board, you must determine the method of DR operation according to the status of the relevant domain.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-19 The table below lists the status types available for individual management items. XSCF changes and configur es system board status accor ding to the conditions under which a system board is installed, removed, or r egistered in the DCL, or when a domain is started or stopped.
2-20 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 T o perform a DR operation for a system board, you must determine the method of DR operation according to the status of the target system boar d. Y ou can display and reference the status of each system board via a user interface provided by XSCF .
Chapter 2 What Y ou Must Know Bef ore Using DR 2-21 FIGURE 2-5 Flow of System Board Addition Pr ocessing 2.4.3.2 Flowchart: Deleting a System Board The flow of DR operations and the transition of system board status when a system board has been deleted or r eserved for deletion are described in the schematic flowchart, below .
2-22 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Each system board status indicated in FIGURE 2-6 is the main status that is changed.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-23 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 r eserved for a move are described in the schematic flowchart, below .
2-24 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 FIGURE 2-7 Flow of System Board Move Pr ocessing Process to change domain Assignment: assigned Assignment:.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-25 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 r eplaced are described using the schematic flowchart. Each system board state indicated in FIGURE 2-8 is the main status that is changed.
2-26 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 FIGURE 2-8 Flow of System Board Replacement Processing Deletion process Deleting a system board DCL regist.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-27 2.5 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 reconf igured automatically .
2-28 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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.
Chapter 2 What Y ou Must Know Bef ore Using DR 2-29 For example, when a kernel memory board with memory mirr or mode enabled is deleted or moved, kernel memory is moved from the kernel memory boar d to another system board. Kernel memory is moved normally even if memory mirror mode is disabled for the move-destination system board.
2-30 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 2.5.8 Deletion of Boar d with DVD Drive T o 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.
3-1 CHAPTER 3 DR User Interface This chapter describes the user interfaces for DR. 3.1 How T o 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 W eb.
3-2 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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 SP ARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF Reference Manual .
Chapter 3 DR User Interface 3-3 T ABLE 3-3 Options of the showdcl Command Option Description -a Displays configuration information and status of all domains.
3-4 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 The table below lists the items displayed by the showdcl (8) command.
Chapter 3 DR User Interface 3-5 3.1.2 Displaying Domain Status The showdomainstatus (8) command lists the domains in the system and their status. This command displays the same domain status information as the showdcl (8) command. Use the showdomainstatus (8) command to check domain status before and after a DR operation.
3-6 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 The following example shows a display of the showdomainstatus (8) command.
Chapter 3 DR User Interface 3-7 The following examples show the format and options of the showboards (8) command. The table below lists the items displayed by the showboards (8) command.
3-8 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Assignment Status of assignment to domain configuration Unavailable The system board cannot be used.
Chapter 3 DR User Interface 3-9 The following examples show displays of the showboards (8) command ■ Example 1 : Display of information on all system boards T est Diagnostic status of system board Unmount The system board is not mounted or cannot be recognized because it is faulty .
3-10 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 ■ Example 2 : Display of detailed information on all system boards ■ Example 3 : Display of information on the system board in the system board pool in domain #0 3.
Chapter 3 DR User Interface 3-11 Note – The showdevices (8) command only reports information about a r unning domain. T ABLE 3-9 Options of the showdevices Command Option Description -v Specifies that the command displays information about all devices.
3-12 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 The following example shows a display by the showdevices (8) command. T ABLE 3-10 Domain Information Displayed by the showdevices command Display items Description CPU CPU information.
Chapter 3 DR User Interface 3-13 ■ Example: Display of device information on XSB00-0 3.1.5 Displaying System Boar d Conf iguration Information Use the showfru (8) command to display system board conf iguration information. The showfru (8) command displays information about the PSB division type and memory mirroring mode settings in list format.
3-14 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 The table below lists the items displayed by the showfru (8) command.
Chapter 3 DR User Interface 3-15 3.1.6 Adding a System Boar d 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 boar d must already be r egistered in the tar get domain’s DCL.
3-16 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Note – (Note 1) In the system board addition pr ocessing executed by this command, a diagnosis of the system board to be added is performed first, and then the system board is added to the tar get domain.
Chapter 3 DR User Interface 3-17 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 hardwar e resour ces may be disabled. For this reason, you should avoid using the -f option for normal DR operations.
3-18 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 T ABLE 3-14 Options of the deleteboard Command Option Description -q Specifies the suppr ession of output message display .
Chapter 3 DR User Interface 3-19 Note – (Note 1) The time requir ed for system board deletion pr ocessing depends on the amount of hardwar e resour ces mounted on the target system board. For this reason, much time may be r equired for the command to end its operation.
3-20 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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 .
Chapter 3 DR User Interface 3-21 Note – (Note 1) The time requir ed for system board deletion pr ocessing in the move-source domain depends on the amount of hardwar e resources mounted on the target system boar d.
3-22 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Note – (Note 2) If the DR processing executed by the moveboard (8) command fails, the target system boar d cannot be restored to the pr evious status.
Chapter 3 DR User Interface 3-23 Note – (Note 1) Before r eplacing a system board, you must know the division type of the replacement-tar get PSB and the configurations and operation status of all domains to which all XSBs on the PSB belong.
3-24 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 3.1.10 Reserving a Domain Conf iguration Change Use the addboard (8), deleteboard (8), or moveboard (8) command to reserve a domain configuration change.
Chapter 3 DR User Interface 3-25 3.2 Command Refer ence This section lists the DR commands and other commands related to DR. For details of the commands, refer to SP ARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF Reference Manual . For the DR commands, see Section 3.
3-26 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 T ABLE 3-18 DR-related Commands Command name Function poweron T urns on the power of all domains or a specified domain. poweroff T urns off the power of all domains or a specif ied domain.
Chapter 3 DR User Interface 3-27 3.3 XSCF W eb XSCF W eb lets you execute DR functions from a br owser . XSCF W eb is beyond the scope of this document. For details, refer to SP ARC Enterprise M4000/M5000/M8000/M9000 Servers XSCF User ’ s Guide . 3.
3-28 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007.
4-1 CHAPTER 4 Practical Examples of DR This chapter provides examples of DR operations, such as the addition, deletion, move, and replacement of system boards. Each example shows an operation procedur e using the command line interface of the XSCF shell.
4-2 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.1.1 Flow: Adding a System Boar d FIGURE 4-1 Flow: Adding a System Board Checking the domain status DR The.
Chapter 4 Practical Examples of DR 4-3 4.1.2 Flow: Deleting a System Boar d FIGURE 4-2 Flow: Deleting a System Board Checking oper ation and Checking the domain status DR operation The domain is Check.
4-4 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.1.3 Flow: Moving a System Boar d FIGURE 4-3 Flow: Moving a System Board Checking oper ation and selecting.
Chapter 4 Practical Examples of DR 4-5 4.1.4 Flow: Replacing a System Boar d FIGURE 4-4 Flow: Replacing a System Board Deletion reser vation operation f or the system board in its domain Checking oper.
4-6 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.2 Example: Adding a System Boar d 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 <LinkColor>4.
Chapter 4 Practical Examples of DR 4-7 If you need to change the PSB configuration, use the setupfru (8) command. If the system board to be added is not register ed in the DCL, register the system board in the DCL of the tar get domain by using the setdcl (8) command.
4-8 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.3 Example: Deleting a System Boar d This section provides an example of operation to delete a system board from a domain. In the example, a procedure conforming to Section 4.
Chapter 4 Practical Examples of DR 4-9 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. 4. Delete the system board.
4-10 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.4 Example: Moving a System Boar d This section provides an example of an operation to move a system board between domains. In the example, a procedure conforming to Section 4.
Chapter 4 Practical Examples of DR 4-11 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.
4-12 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 7. Check the status of the move-destination domain and moved system board.
Chapter 4 Practical Examples of DR 4-13 4.5.1 Example: Replacing a Uni-XSB System Boar d FIGURE 4-8 Example: Replacing a Uni-XSB System Board 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.
4-14 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4. Delete the system board. Execute the deleteboard (8) command to delete the system board. 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.
Chapter 4 Practical Examples of DR 4-15 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.
4-16 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.5.2 Example: Replacing a Quad-XSB System Boar d FIGURE 4-9 Example: Replacing a Quad-XSB System Board 1. Login to XSCF . 2. Check the conf igurations and status of all domains to which the relevant system boards belong.
Chapter 4 Practical Examples of DR 4-17 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 r eplaced.
4-18 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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.
Chapter 4 Practical Examples of DR 4-19 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.
4-20 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.6 Examples: Reserving Domain Conf iguration Changes This section provides examples of operations to reserve a change in domain configuration by DR.
Chapter 4 Practical Examples of DR 4-21 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 r egistration in the DCL.
4-22 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 4.6.2 Example: Reserving a System Boar d Delete FIGURE 4-11 Example: Reserving a System Board Delete 1.
Chapter 4 Practical Examples of DR 4-23 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 conf irm that deletion of the system board has been reserved.
4-24 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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.
Chapter 4 Practical Examples of DR 4-25 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- destinatio.
4-26 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007.
A-1 APPENDIX A Message Meaning and Handling This appendix explains the meaning and handling of DR-related messages. A.1 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-2 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 OS unconfigure dr@0:SB X ::memory [Explanation] Unconfigure memory on system boar d X . OS unconfigure dr@0:SB X ::pci Y [Explanation] Unconfigure PCI Y on system boar d X .
Appendix A Message Meaning and Handling A-3 [Explanation] Suspending device drivers DR: in-kernel unprobe board <board> [Explanation] Unprobing the boar d. A.1.2 P ANIC Messages URGENT_ERROR_TRAP is detected during FMA. [Explanation] A fatal HW error was encountered during copy-r ename.
A-4 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [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-r ename.
Appendix A Message Meaning and Handling A-5 [Remedy] Disable interrupt on cpu X with psradm -I and if this command fails again, respond in the manner dir ected by command message. dr_cancel_cpu: failed to online cpu X [Explanation] Failed to online CPU X .
A-6 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [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.
Appendix A Message Meaning and Handling A-7 dr_pre_release_cpu: thread(s) bound to cpu X [Explanation] The thread in the pr ocess 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 r epeat the action.
A-8 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [Remedy] Please repeat the action. If the problem r emains, please contact customer service. dr_release_mem_done: <device path>: error <error code> noted [Explanation] Error noted for a device during releasing memory .
Appendix A Message Meaning and Handling A-9 Cannot stop user thread: <pid> <pid> ... [Explanation] The DR driver cannot stop all the user processes in the list.
A-10 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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.
Appendix A Message Meaning and Handling A-11 [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 .
A-12 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [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:SB X ::cpu Y [Explanation] Failed to off-line CPU Y on board X .
Appendix A Message Meaning and Handling A-13 [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.
A-14 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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.
Appendix A Message Meaning and Handling A-15 [Remedy] Repeat the action. If this error message appears again, please contact customer service. [Output] Console and Standard Output Insufficient memory: dr@0:SB X ::cpu Y [Explanation] Lack of memory resources detected.
A-16 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Operation already in progress: dr@0:SB X ::cpu Y [Explanation] The operation on cpu Y on system board X is in progr ess. [Remedy] Repeat the action. If the problem still exists, please contact customer service.
Appendix A Message Meaning and Handling A-17 [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.
A-18 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [Explanation] A claim request with a nonzer o hint came from the fcode interpreter . [Remedy] If DR failed after this message, please contact customer service.
Appendix A Message Meaning and Handling A-19 [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.
A-20 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [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.
Appendix A Message Meaning and Handling A-21 [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.
A-22 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [Explanation] An unknown resource type was found in the r esource list that is being freed while the board is unpr obed. [Remedy] Please contact customer service.
Appendix A Message Meaning and Handling A-23 SCF error [Explanation] Internal error happened during kernel migration. [Remedy] Please contact customer service. A.2 Command Messages A.2.1 addboar d XSB#XX-X will be assigned to DomainID X. Continue? [y|n]: [Explanation] Confirming whether DR operation is going to be executed or not.
A-24 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 XSB#XX-X is currently unavailable for DR. Try again later. [Explanation] The specified system boar d (XSB#XX-X) has already been executed by another operation.
Appendix A Message Meaning and Handling A-25 [Remedy] Find out the cause of the DR failure r eferring monitoring message and errorlog. Conf irm the patch applying status and the XCP version DR failed. Domain (DomainID X) cannot communicate via DSCP path.
A-26 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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 .
Appendix A Message Meaning and Handling A-27 [Explanation] The specified system boar d (XSB#XX-X) has already been executed by another operation. [Remedy] DR or power-of f has been executing for another session. T ry again after waiting for a while, with the confirmation of the XSB status.
A-28 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 Invalid parameter. [Explanation] There is an error in the specif ied argument or operand. [Remedy] Confirm the specif ied argument or operand and execute the command once again.
Appendix A Message Meaning and Handling A-29 [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 .
A-30 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [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 har dware diagnosis did not complete.
Appendix A Message Meaning and Handling A-31 [Remedy] Find out the cause of the DR failure r eferring monitoring message and console message. T ry again after taking out cause. Invalid parameter. [Explanation] There is an error in the specif ied argument or operand.
A-32 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 [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.
Appendix A Message Meaning and Handling A-33 Invalid parameter. [Explanation] There is an error in the specif ied argument or operand. [Remedy] Confirm the specif ied argument or operand and execute the command once again. Permission denied. [Explanation] Do not have privilege.
A-34 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 The specified parameter is not supported in this model. [Explanation] Unsupported parameter in this server is specified. For this reason, the command was canceled.
Appendix A Message Meaning and Handling A-35 [Remedy] Confirm that the DSCP setting is corr ect, confirm that the dsc pr ocess is running fine on the domain.
A-36 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007.
B-1 APPENDIX B Example: Conf irm 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.
B-2 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 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 configur ed swap space.
Glossar y-1 Glossary This glossary describes some of the terms used in this manual. Capacity on Demand (COD) An option that provides additional CPU pr ocessing resour ces when needed. These additional CPUs are pr ovided on COD CPU boards that ar e installed in the system.
Glossar y-2 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007 eXtended System Control facility unit (XSCFU) The XSCF board for this server which contains system administration function and operates with independent processor .
Glossar y-3 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.
Glossar y-4 SPARC Enterprise Mx000 Servers Dynamic Reconfiguration User’s Guide • September 2007.
Index-1 Index A 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 B Basic DR T erms, 1-3 C Capacity on Demand, 2-29 configuration policy, 2-13 Con.
Index-2 SP ARC Enter prise Mx000 Ser vers Dynamic Reconfiguration User’ s Guide • September 2007 move, 1-6, 2-23, 3-19, 4-4, 4-10 moveboard, 3-2, 3-19 O omit-I/O, 2-15 omit-memory, 2-15 P Physica.
.
Herausgegeben von / Published by Fujitsu Siemens Computers Gmb H *U416 84-J-Z81 6-2-76 * U41684- J-Z816-2 -76 Bes tell- Nr ./ Order No .: U41684-J- Z816-2-7 6.
Een belangrijk punt na aankoop van elk apparaat Fujitsu Siemens Computers M4000 (of zelfs voordat je het koopt) is om de handleiding te lezen. Dit moeten wij doen vanwege een paar simpele redenen:
Als u nog geen Fujitsu Siemens Computers M4000 heb gekocht dan nu is een goed moment om kennis te maken met de basisgegevens van het product. Eerst kijk dan naar de eerste pagina\'s van de handleiding, die je hierboven vindt. Je moet daar de belangrijkste technische gegevens Fujitsu Siemens Computers M4000 vinden. Op dit manier kan je controleren of het apparaat aan jouw behoeften voldoet. Op de volgende pagina's van de handleiding Fujitsu Siemens Computers M4000 leer je over alle kenmerken van het product en krijg je informatie over de werking. De informatie die je over Fujitsu Siemens Computers M4000 krijgt, zal je zeker helpen om een besluit over de aankoop te nemen.
In een situatie waarin je al een beziter van Fujitsu Siemens Computers M4000 bent, maar toch heb je de instructies niet gelezen, moet je het doen voor de hierboven beschreven redenen. Je zult dan weten of je goed de alle beschikbare functies heb gebruikt, en of je fouten heb gemaakt die het leven van de Fujitsu Siemens Computers M4000 kunnen verkorten.
Maar de belangrijkste taak van de handleiding is om de gebruiker bij het oplossen van problemen te helpen met Fujitsu Siemens Computers M4000 . Bijna altijd, zal je daar het vinden Troubleshooting met de meest voorkomende storingen en defecten #MANUAl# samen met de instructies over hun opplosinge. Zelfs als je zelf niet kan om het probleem op te lossen, zal de instructie je de weg wijzen naar verdere andere procedure, bijv. door contact met de klantenservice of het dichtstbijzijnde servicecentrum.
