Page 1 FUJITSU Server PRIMEQUEST 2000 Series Administration Manual CA92344-0537-08...
Page 2 Preface Preface This manual describes the functions and features of the PRIMEQUEST 2000 series. The manual is intended for system administrators. For details on the regulatory compliance statements and safety precautions, see the PRIMEQUEST 2000 Series Safety and Regulatory Information (CA92344-0523).
Page 3: Revision History
Preface Revision History Edition Date Revised location (type) (*1) Description - The edition is initialized to "01" for changing manual code 2014-08-12 All pages - Added descripations about Extended Partitioning function 2014-10-07 All pages - Added description about RHEL7 - Modified and added description 2015-02-03 Chapter 3 about Extended Partitioning and...
Page 4: Safety Precautions
Similarly, one space line is inserted before and after the alert statement. Only Fujitsu certified service engineers should perform the following tasks on this product and the options provided by Fujitsu. Customers must not perform these tasks under any circumstances.
Page 5 Preface CA92344-0537-08...
Page 6 Preface Warning label location (the main cabinet left) Warning label location (PCI_Box) CA92344-0537-08...
Page 7: About This Product
For stable operation of the PRIMEQUEST 2000 series server, use only a Fujitsu-certified optional product as an added option. Note that the PRIMEQUEST 2000 series server is not guaranteed to operate with any optional product not certified by Fujitsu. Exportation/release of this product Exportation/release of this product may require necessary procedures in accordance with the regulations of the Foreign Exchange and Foreign Trade Control Law of Japan and/or US export control laws.
Page 8: Support And Service
Be sure to keep this manual in a safe and convenient location for quick reference. Fujitsu makes every effort to prevent users and bystanders from being injured and to prevent property damage. Be sure to use the product according to the instructions in this manual.
Page 9 Includes the specifications of and the installation location CA92344-0535 Hardware Installation Manual requirements for the PRIMEQUEST 2000 series. PRIMEQUEST 2000 Series Describes how to set up the PRIMEQUEST 2000 series CA92344-0536 Installation Manual server, including the steps for installation preparation, initialization, and software installation.
Page 10 RAID Ctrl SAS 6Gb 1GB (D3116C) Software MegaRAID SAS 9286CV-8e LSI MegaRAID SAS 2.0 Refer to the following URL: Device Driver Installation The Fujitsu Technology Solutions manuals server http://manuals.ts.fujitsu.com/ Provides technical information on using SAS RAID Modular RAID Controller controllers. LSI MegaRAID SAS 3.0...
Page 11: Command Syntax
This manual uses the following fonts and symbols to express specific types of information. Example Font or symbols Meaning italics See the PRIMEQUEST 2000 Series Title of a manual that you should refer to Installation Manual (CA92344-0536). Window names as well as the names of Click the [OK] button.
Page 12 The PDF file of this manual is intended for display using Adobe® Reader® in single page viewing mode at 100% zoom. This manual shall not be reproduced or copied without the permission of Fujitsu Limited. Copyright 2014 – 2016 FUJITSU LIMITED...
Page 13: Table Of Contents
External Network Configuration ..............................1 How to Configure the External Networks (Management LAN/ Maintenance LAN/Production LAN) ........3 1.2.1 IP addresses used in the PRIMEQUEST 2000 series server ....................3 Management LAN ..................................5 1.3.1 Overview of the management LAN ............................5 1.3.2...
Page 14: Preface
Preface 4.1.2 dr Command Package Install/ Uninstall ..........................85 Hot add of SB ....................................85 4.2.1 Preparing for SB hot add ............................... 85 4.2.2 Confirming the status of SB before SB hot add........................86 4.2.3 DR operation in SB hot add ..............................86 4.2.4 How to deal with timeout while OS is processing SB hot add .....................
Page 15 Preface 5.5.1 Preparation for IOU hot add ..............................162 5.5.2 DR operation of IOU hot add ............................... 162 5.5.3 Operation after IOU hot add ..............................163 IOU hot remove ..................................164 5.6.1 Preparation for IOU hot remove ............................164 5.6.2 DR operation of IOU hot remove ............................
Page 16 Preface 7.3.4 Operation after SB hot remove ............................244 Hot replacement of IOU ................................245 7.4.1 Preparation for IOU hot replacement ..........................245 7.4.2 DR operation of IOU hot replacement ..........................249 7.4.3 Operation after IOU hot replacement ..........................251 Hot add of IOU ..................................
Page 17 Preface CHAPTER 10 Backup and Restore ..............................338 10.1 Backing Up and Restoring Configuration Information ......................338 10.1.1 Backing up and restoring UEFI configuration information..................... 338 10.1.2 Backing up and restoring MMB configuration information .................... 341 CHAPTER 11 Chapter System Startup/Shutdown and Power Control ..................342 11.1 Power On and Power Off the Whole System .........................
Page 18 Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers ....402 Physical Locations and BUS Numbers of Internal I/O Controllers of the PRIMEQUEST 2000 Series ....... 402 Correspondence between PCI Slot Mounting Locations and Slot Numbers ................ 402 Appendix E PRIMEQUEST 2000 Series Cabinets ............................
Page 19 Rack Mounting ..................................428 Installation Environment ................................428 NIC (Network Interface Card) ..............................428 Appendix H Tree Structure of the MIB Provided with the PRIMEQUEST 2000 Series ................430 MIB Tree Structure ................................... 430 MIB File Contents ..................................431 Appendix I Windows Shutdown Settings ..............................432 Shutdown From MMB Web-UI ..............................
Page 20 Preface Figures FIGURE 1.1 External network configuration ............................1 FIGURE 1.2 External network functions ..............................2 FIGURE 1.3 Management LAN configuration ............................6 FIGURE 1.4 Maintenance LAN and REMCS LAN of the MMB ......................11 FIGURE 1.5 Connection configuration for video redirection ........................ 14 FIGURE 1.6 Operating sequence of video redirection .........................
Page 21 Preface FIGURE 3.25 Example 6. Example where a Reserved SB has been set in SB #0 (When the Home SB has failed) ..... 63 FIGURE 3.26 Example 7. Example when SB #0 is set as the Reserved SB (when an SB other than the Home SB) fails) ..63 FIGURE 3.27 Example 8-a.
Page 22 Preface FIGURE 13.14 [System Event Log Filtering Condition] window in PRIMEQUEST 2800B3/2800B2/2800B ......... 374 FIGURE 13.15 [System Event Log (Detail)] window.......................... 375 FIGURE 13.16 [Startup and Recovery] dialog box ..........................379 FIGURE 13.17 [Advanced] tab of the dialog box ..........................380 FIGURE 13.18 [Virtual Memory] dialog box ............................
Page 23 TABLE 1.2 IP addresses for the PRIMEQUEST 2000 series server (IP addresses set from the MMB) ..........3 TABLE 1.3 IP addresses for the PRIMEQUEST 2000 series server (set from the operating system in a partition) ......4 TABLE 1.4 Restrictions on the management LAN..........................6 TABLE 1.5 Parts of the management LAN configuration ........................
Page 24 Preface TABLE 5.1 Correspondence between bus addresses and interface names ................... 155 TABLE 5.2 Hardware address description examples ........................156 TABLE 5.3 Example of interface information about interfaces after replacement ................159 TABLE 5.4 Correspondence between bus addresses and interface names ................... 166 TABLE 5.5 Hardware address description examples ........................
Page 25 Preface TABLE A.14 Partition operation ................................392 TABLE A.15 Partition power control ..............................392 TABLE A.16 OS boot settings ................................392 TABLE A.17 MMB user account control ............................. 392 TABLE A.18 Server management network settings .......................... 392 TABLE A.19 Maintenance ................................... 393 TABLE A.20 Management network specifications ..........................
Page 26 Preface TABLE G.12 DIMM mixed mounting condition in SB ........................424 TABLE G.13 DIMM mounting order in Memory Scale-up Board ...................... 425 TABLE G.14 DIMM mixed mounting condition in Memory Scale-up Board ..................425 TABLE G.15 DIMM mounting order in special case in SB ........................ 426 TABLE G.16 DIMM mixed mounting condition in special case in SB ....................
Page 27: Chapter 1 Network Environment Setup And Tool Installation
This chapter describes the external network environment and management tool installation for the PRIMEQUEST 2000 series. For an overview of the management tools used for the PRIMEQUEST 2000 series, see Chapter 8 Operations Management Tools in the PRIMEQUEST 2000 Series General Description (CA92344-0534).
Page 28: Figure 1.2 External Network Functions
CHAPTER 1 Network Environment Setup and Tool Installation 1.1 External Network Configuration FIGURE 1.2 External network functions CA92344-0537-08...
Page 29: How To Configure The External Networks (Management Lan/ Maintenance Lan/Production Lan)
This section describes the IP addresses for the PRIMEQUEST 2000 series server. 1.2.1 IP addresses used in the PRIMEQUEST 2000 series server Each of the SB, IOU, and MMB units in the PRIMEQUEST 2000 series server has network interfaces. Each port of these network interfaces must be assigned an IP address.
Page 30: Table 1.3 Ip Addresses For The Primequest 2000 Series Server (Set From The Operating System In A Partition)
LAN inside the cabinet. The operating system assigns the IP address of the 100 Mb Ethernet port. TABLE 1.3 IP addresses for the PRIMEQUEST 2000 series server (set from the operating system in a partition) LAN port IP address setting...
Page 31: Management Lan
IP addresses of the management LAN (MMB) Each MMB has one physical IP address for the management interface of the PRIMEQUEST 2000 series server. In addition to that, the primary MMB shares a common virtual IP address in the system. You can set these IP addresses from the MMB Web-UI or CLI.
Page 32: Figure 1.3 Management Lan Configuration
CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN FIGURE 1.3 Management LAN configuration Description Physical LAN IP example (MMB #0): 10.20.30.101 Physical LAN IP example (MMB #1): 10.20.30.102 Virtual LAN IP example: 10.20.30.100 If either USER port fails, the interface redundancy function switches to the other port in the MMB to ensure continuous service.
Page 33: How To Configure The Management Lan
CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN show access_control show date show timezone show gateway show http show http_port show https show https_port show ssh show ssh_port show telnet show telnet_port show ip show network show exit_code ping netck arptbl netck arping...
Page 34 CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN Display/Setting item Description Enable/Disable setting Maintenance IP Address Specifies the REMCS/CE port. The default is ‘Disabled’. Enable/Disable setting IP Address/Subnet Mask/SMTP Address Internal LAN IP Address IP Address/Subnet Mask/Gateway Address Specifies the NIC on the MMB of the Internal (PCH-to-MMB) LAN.
Page 35 CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN Display/Setting item Description Create Selfsigned Certificate Creates a self-signed certificate. SSL certificate status: Displays the current status of self-signed certificate installation. Term: Specifies the term of validity (number of days) of the self-signed certificate.
Page 36: Redundant Configuration Of The Management Lan
CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN The subnet of the management LAN shares the virtual IP address and the physical address of the MMB, which are specified by Web-UI/CLI on the MMB. The management LAN and production LAN can be configured in the same subnet. In such case, an IP address is assigned to both the management LAN and the production LAN on the partition connected to the subnet of the LAN to which the MMB User Port is connected.
Page 37: Maintenance Lan/Remcs Lan
MMB is disabled. Remarks The active and standby MMBs in the PRIMEQUEST 2000 series server each have a CE terminal port used in maintenance and a LAN port for REMCS notification. Communication through the ports is enabled only on the active MMB and disabled on the standby MMB.
Page 38: Redundancy Of The Production Lan
(Web User Interface) Operations in the PRIMEQUEST 2000 Series Tool Reference (CA92344-0539). NTP client function setting on the MMB In the PRIMEQUEST 2000 series, the MMB acts as an NTP client to ensure synchronization with external NTP servers. 1.6.2 Remote operation (BMC)
Page 39: Table 1.7 Maximum Number Of Connections Using The Remote Operation Function
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Required Java Runtime Environment Java 6 or later Notes For a terminal whose operating system is Windows Vista or later and Windows Server 2008 or later, set UAC (User Account Control) or UAP (User Account Protection) to "Disabled”...
Page 40: Figure 1.5 Connection Configuration For Video Redirection
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use List of video redirection function is shown below. Note If you cannot access to DNS server in the terminal for video redirection, do not set up the address of DNS server.
Page 41: Figure 1.6 Operating Sequence Of Video Redirection
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use The following shows the operating sequence of video redirection. FIGURE 1.6 Operating sequence of video redirection In the diagram, (1) to (5) indicates the following operations. (1) Log in to the MMB Web-UI by browser.
Page 42: Figure 1.7 [Video Redirection] Window
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.7 [Video Redirection] window Title of [Video Redirection] window is shown as the following: For PRIMEQUEST 2400E3/2800E3, PRIMEQUEST 2400E3/2800E3 + Product serial number + partitioin number. Example of PQ 2800E3 where Product serial number is “123456789012”...
Page 43: Table 1.9 Menu Bar In [Video Redirection] Window
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use PRIMEQUEST 2400E/2800E + Product serial number + partitioin number. Example of PQ 2800E where Product serial number is “123456789012” and partition number is “3”: JViewer – PRIMEQUEST 2800E 123456789012 P#3 For PRIMEQUEST 2800B, PRIMEQUEST 2800B + Product serial number.
Page 44 CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Menu Bar Description English(United States) Set to ‘English (United States)’. English(United Kingdom) Set to ‘English (United Kingdom)’. Spanish Set to ‘Spanish’. French Set to ‘French’. German(Germany) Set to ‘German (Germany)’.
Page 45: Table 1.10 Tool Bar Menu In [Video Redirection] Window
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Menu Bar Description Immediate Reset Perform hardware reset. Pulse NMI Issue NMI. Graceful Reset (Reboot) Perform Graceful Reset (Reboot). Graceful Power off (Shutdown) Perform Graceful Power off (Shutdown) Set Boot Options Perform setup of Boot Options.
Page 46: Figure 1.8 Message Of Requesting Access To Virtual Console In Second Terminal Pc
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use When resolution of window in server is 800 x 600, a part of window displayed in video redirection may luck or track of mouse cursor may remain during installing Linux. While the video redirection is being used, a warning message indicating that the digital signature is expired may be displayed.
Page 47: Figure 1.9 Popup Window Of [Virtual Console Sharing Privileges]
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use 3. In first terminal PC, window where connection privilege of second terminal PC is selected appears. Select connection privilege from below. Allow Virtual Console permit Full Virtual Console access where all operation of video redirection can be performed. Allow only Video permit only video where display function of video redirection can be performed.
Page 48: Figure 1.14 Popup For [Deny Access] In Second Terminal Pc
FIGURE 1.16 Popup for reaching maximum number of connection in second terminal PC Console redirection PRIMEQUEST 2000 series provides console redirection to route serial output from partitions via a LAN. Console redirection conforms to the specifications of IPMI v2.0 SOL (Serial Over LAN).
Page 49: Figure 1.17 Example Of Setting Partition #3 (1)
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.17 Example of setting partition #3 (1) 2. If the message “Do you really want to start the Console Redirection (yes/no)?” appears, input ‘yes’. You can connect to specified partition.
Page 50: Figure 1.19 Forced Disconnection Of Console Redirection (1)
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.19 Forced disconnection of console redirection (1) 2. If you disconnect the console redirection of other user who has been already used, enter ‘yes’. You can use console redirection in place of current user.
Page 51: Figure 1.21 Configuration Of Virtual Media Connection
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use You may receive a STOP error message on a blue screen when using the virtual media function from your terminal. The blue screen appears on the terminal under the following circumstances. You are using the remote storage function from a terminal running one of the following Windows operating systems: Windows XP...
Page 52: Figure 1.22 [Virtual Media] Window (1)
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.22 [Virtual Media] window (1) The following lists the buttons available in the virtual media list window. TABLE 1.12 Buttons in [Virtual Media] window Item Description [Browse]...
Page 53: Figure 1.23 Image File Selection Window
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.23 Image file selection window Items in image file selection window are listed below. TABLE 1.13 Items in image file selection window Item Description Look In Displays the current search location File name...
Page 54: Serverview Suite
Installation Manager. Creating and managing server groups For details on how to create and manage server groups for individual users, see the ServerView Suite ServerView Operations Manager Server Management. For more information about ServerView Suite, see below web site. http://manuals.ts.fujitsu.com/ CA92344-0537-08...
Page 55: Chapter 2 Operating System Installation
1.6 Management Tool Operating Conditions and Use CHAPTER 2 Operating System Installation For details on how to install an operating system on a partition, see Chapter 4 Installing the Operating System and Bundled Software in the PRIMEQUEST 2000 Series Installation Manual. CA92344-0537-08...
Page 56: Chapter 3 Component Configuration And Replacement (Add, Remove)
3.1 Partition Configuration CHAPTER 3 Component Configuration and Replacement (Add, Remove) This section describes the configuration and replacement of component of the PRIMEQUEST 2000 series. Partition Configuration This section describes the configuration of physical partition and Extended Partition. 3.1.1 Physical Partition Configuration 3.1.2...
Page 57: Figure 3.1 Conceptual Diagram Of The Partitioning Function (Primequest 2400E3/2400E2)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.1 Partition Configuration PRIMEQUEST 2400E3/2400E2 For PRIMEQUEST 2400E3/2400E2, up to two partitions can be configured. An optional SB/Memory Scale-up Baord and an optional IOU can be freely combined. The partition configuration is shown below. Components with dotted line /and white background color in the diagram show the components that are not mounted.
Page 58: Figure 3.2 Conceptual Diagram Of The Partitioning Function (Primequest 2400E)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.1 Partition Configuration PRIMEQUEST 2400E For PRIMEQUEST2400E, up to two partitions can be configured. An optional SB and an optional IOU can be freely combined. The partition configuration is shown below. Components with dotted line /and white background color in the diagram show the components that are not mounted.
Page 59: Figure 3.3 Conceptual Diagram Of The Partitioning Function (Primequest 2800E3/2800E2/2800E)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.1 Partition Configuration PRIMEQUEST 2800E3/2800E2/2800E For PRIMEQUEST 2800E3/2800E2/2800E, up to four partitions can be configured. Optional SB and optional path can be freely combined. Examples of partition configuration are shown below. Components with dotted line and white background in the diagram show the components that are not mounted.
Page 60: Extended Partition Configuration
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.1 Partition Configuration 3.1.2 Extended Partition configuration Extended Partition is configured by allocating the following hardware resources. CPU core DIMM Memory can be allocated in units of 1GB. HDD/SSD PCI Express slot Onboard device (VGA, USB port) There are two ways how to allocate Onboard devices.
Page 61: Figure 3.4 Example Of Partition Configuration Where Extended Partition Is Used In Primequest 2400E3/2400E2/2400E
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.1 Partition Configuration PRIMEQUEST 2400E3/2400E2/2400E For PRIMEQUEST 2400E3/2400E2/2400E, up to four Extended Partitions can be configured. An example of partition configuration is shown below. In below figure, one physical partition and four Extended Partitions are configured. FIGURE 3.4 Example of partition configuration where Extended Partition is used in PRIMEQUEST 2400E3/2400E2/2400E CA92344-0537-08...
Page 62: Setting Procedure Of Partition In Mmb Web-Ui
FIGURE 3.5 Example of partition configuration where Extended Partition is used in PRIMEQUEST 2800E3/2800E2/2800E 3.1.3 Setting procedure of partition in MMB Web-UI For the procedure to set the partition in the MMB Web-UI, see “PRIMEQUEST 2000 series Installation manual” (CA92344-0536). CA92344-0537-08...
Page 63: High Availability Configuration
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration High availability configuration This section describes the following functions for realizing a high system availability of the PRIMEQUEST 2000 series. 3.2.1 Extended Partitioning 3.2.2 Extended Socket 3.2.3 Dynamic Reconfiguration (DR) 3.2.4 Reserved SB 3.2.5 Memory Operation Mode 3.2.6...
Page 64: Figure 3.6 Example Of [Power Control] Window (Extended Partitioning Is Enabled.)
Extended Partitions are grayed out on the window. In above figure, none of Extended Partitions are grayed out because Extended Partitioning mode is enabled on all physical partitions. For details of [Power Control] window, see ‘1.3.1 [Power Control] window’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539).
Page 65: Figure 3.7 Example Of [Partition Configuration] Window (Extended Partitioning Is Enabled.)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration [Partition Configuration] window In the [Partition Configuration] window, SB, IOU and Extended Partitioning are displayed as resources allocated to the Physical Partition. FIGURE 3.7 Example of [Partition Configuration] window (Extended Partitioning is enabled.) For details of [Partition Configuration] window, see ‘1.3.4 [Partition Configuration] window’...
Page 66: Figure 3.9 Example Of Extended Partition Of [Iou] Window
Partition’, it can be used in Extended Partition #5. If there are multiple SBs, multiple SBs are displayed under Partition#x Extended Partition Configuration in the sub menu area. For details of [SB] window of Extended Partition, see ‘1.3.5.1 [SB] window’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). [IOU] window The IOU configuring the Extended Partition is set in the [IOU] window.
Page 67: Figure 3.10 Example Of [Pci_Box] Window Of Extended Partition
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration [PCI_Box] window In the [PCI_Box] window, the PCI_Box configuring the Extended Partition will be set. FIGURE 3.10 Example of [PCI_Box] window of Extended Partition When there is one PCNC, the displayed number of PCI slots will become half, which is six. In ‘FIGURE 3.10 Example of [PCI_Box] window of Extended Partition’, two PCNCs are mounted.
Page 68: Figure 3.11 Example Of [Ipv4 Console Redirection Setup] Window
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration [IPv4 Console Redirection Setup] / [IPv6 Console Redirection Setup] window Console redirection is set in the [IPv4 Console Redirection Setup] / [IPv6 Console Redirection Setup] window. FIGURE 3.11 Example of [IPv4 Console Redirection Setup] window FIGURE 3.12 Example of [IPv6 Console Redirection Setup] window You must set IP addresses to Extended Partitions regardless of the physical partitions which are divided to Extended Partitions (Partition #0 of...
Page 69: Figure 3.13 Example Of [Mode] Window Of Physical Partition
‘FIGURE 3.11 Example of [IPv4 Console Redirection Setup] window’) will be grayed out. For details of [IPv4 Console Redirection Setup] window/ [IPv6 Console Redirection Setup] window, see ‘1.3.3 [Console Redirection Setup] window’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344- 0539). [Mode] window Enable/Disable of Extended Partitioning can be set in the [Mode] window of the physical partition.
Page 70: Table 3.5 Effect On The Menu Of The Mmb Due To Extended Partitioning Mode Change
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration For details of [Mode] window, see ‘1.3.9.4 [Mode] window’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). Setting of Extended Partitioning mode Extended Partitioning is enabled by the following procedure.
Page 71: Table 3.6 Activate/Deactivate For Extended Partition
Activating the Extended Partition 1. Using the MMB Web-UI, the free Extended Partition number is allocated to the Physical partition. For details, see '1.3.3 [Partition Configuration] window' in "PRIMEQUEST 2000 series Tools Reference” (CA92344-0539) 2. In addition, the necessary hardware resource is allocated to the Extended Partition by setting the SB, IOU and PCI_Box.
Page 72 Extended Partition is automatically cleared *1: For details, see ‘■ [Mode] window' of '1.3.9 [Partition #x] menu' in "PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). *2: For details, see ‘1.3.3 [Partition Configuration] window' of "PRIMEQUEST 2000 series Tool Reference”...
Page 73 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Power Technology Enhanced SpeedStep Turbo Mode Energy Performance P-State Coordination QPI Link Frequency Select Frequency Floor Override DIMM Speed setting Select the action of Extended Partitioning from following actions after the Watchdog timeout is detected. Continue Reset Power Cycle (*1)
Page 74: Table 3.7 Comparison Of The Operating System Installation Options
The installation of the operating system using SVIM is recommended in the PRIMEQUEST 2000 series. The DVD drive is not provided in the PRIMEQUEST 2000 series. The installation of the operating system using SVIM has the following two options, namely Remote and Local.
Page 75: Extended Socket
The module is got in following URL to installe the module; http://support.ts.fujitsu.com/Download/Index.asp For details, see ‘3.3 Replacing components".
Page 76: Figure 3.15 Overview Of Extended Socket
FIGURE 3.15 Overview of Extended Socket Enabling/Disabling Extended Socket Extended Socket is set to ‘Enable’/’Disable’ in [Mode] window of the Extended Partition of MMB Web-UI. For detail of [Mode] window, see ‘1.3.9.4 [Mode] window’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). Zoning function Zoning function allows an Extended Partition to communicate by using Extended Socket with only Extended Partitions which are allowed.
Page 77 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration VLAN function Extended Socket supports Tag-VLAN function within the Zone. How to confirm interface of Extended Socket on OS Extended Socket is normally seen as network interface of “es0”. If “es0”...
Page 78 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Extended Partitions by using Extended Socket may decrease. To avoid this problem, you must fix C state and P state of CPU to C0 and P0 respectively. To fix C state to C0, you perform following steps on OS. 1.
Page 79: Dynamic Reconfiguration (Dr)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration 3.2.3 Dynamic Reconfiguration (DR) This section describes the hot maintenance by DR. For details on the hot maintenance, see CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6, .CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 or CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server Function Overview...
Page 80: Figure 3.18 Iou Hot Add
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Description Fault suspected Dynamic disconnection of SB (operation by operator) Replacement IOU hot maintenance (IOU hot add/ IOU hot remove) Function that can incorporate an IOU into the system (IOU hot add), or disconnect an IOU from the system (IOU hot remove) without restarting the operating system.
Page 81: Table 3.12 Dr Supported List
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Item Setting / criteria PCI Address mode PCI segment mode At least 1 SB Memory (*1) Home SB 2GB + (Quantity of Logical CPUs X100MB) + (Memory capacity of the total system x0.03) + Memory capacity of HugeTLB Excluding Home SB Nothing specific...
Page 82 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration  Notes or Limitations related to setting All the SB firmware shall be of the same version number. In the partition with DR enabled, a HDD/SSD on the non-Home SB cannot be used. DR operation cannot be performed if memory operation mode is Performance mode.
Page 83 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Perform DR operation when low load is applied to the partition since TIMEOUT may occur if DR operation is performed when high load is applied to the partition during DR operation. For how to deal with if TIMEOUT occurs, see ‘4.2.4 How to deal with timeout while OS is processing SB add’.
Page 84: Reserved Sb
In a partition with one SB, recovery is possible even if the SB fails (SB degradation) In addition, in PRIMEQUEST 2000 series, SB in a running partition can be also specified as a Reserved SB. A Reserved SB can be used very efficiently by using this function.
Page 85: Table 3.13 Memory Operation Mode Before And After Reserved Sb Switching, When A Partition Is Configured From One Sb
For details on the workaround, see '● Procedure to prevent Windows restart' of ‘3.4.3 Reserved SB Setting' in "PRIMEQUEST 2000 series Installation Manual" (CA92344-0536) Reserved SB definition The definition of the Reserved SB is automatically canceled after the Reserved SB operates.
Page 86 However, the following workaround can suppress the restart request. Workaround for Windows restart In the PRIMEQUEST 2000 series, the restart request can be suppressed by identifying the Reserved SB in advance. Execute the following procedures for all the partitions with Windows installed.
Page 87: Figure 3.20 Example 1-A. Example Where Two Sbs Are Set As Reserved Sbs In Two Partitions
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration When an SB has been configured as a Reserved SB for multiple partitions, and there is simultaneous failure in multiple partitions, the partition with the lowest number takes priority for switching (Example 1). When multiple SBs fail in a partition, the SB with the lowest number takes priority for switching (Example 2).
Page 88: Figure 3.23 Example 4. Where Reserved Sbs (#1, #2, #3) Of Partition #0 Belong To Other Partitions
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration In example 4, since SB #1 and SB #2 of a powered off partition are available, the SB with the highest number is selected as the switching destination. Example 4.
Page 89: Figure 3.25 Example 6. Example Where A Reserved Sb Has Been Set In Sb #0 (When The Home Sb Has Failed)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Example FIGURE 3.25 6. Example where a Reserved SB has been set in SB #0 (When the Home SB has failed Description Since Partition #0 is the configuration of SB #0 and SB #2, SB #0 with the lowest number becomes the Home Example when an SB other than the...
Page 90: Figure 3.28 Example 8-B. Example Where A Reserved Sb Has Been Set In The Partition Including Memory Scale-Up Board (When The Memory Scale-Up Board Has Failed)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Example FIGURE 3.28 8-b. Example where a Reserved SB has been set in the partition including Memory Scale-up Board (When the Memory Scale-up Board has failed Switching policy The triggers for switching to a Reserved SB are as follows.
Page 91: Memory Operation Mode
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration The shutdown wait time for switching to a Reserved SB being used by another partition is the value that is set from the MMB Web-UI (0 to 99 minutes); the default is 10 minutes. One shutdown wait time can be set in the system (in the chassis).
Page 92: Memory Mirror
(*1) Only case where Mirror RAS mode is Mirror Keep. 3.2.6 Memory Mirror In the PRIMEQUEST 2000 series, the Mirror Mode, the Partial Mirror Mode and Address Range Mirror Mode are supported as the memory mirror, in which the function with the CPU is used. Full Mirror/Partial Mirror/Address Range Mirror can be selected from the MMB Web-UI.
Page 93: Table 3.18 Mirror Size Being Able To Mirror In Home Sb And Non-Home Sb
OS or BIOS menu in order to enable Address Range Mirror for the partition. For BIOS menu, see ‘3.4.6 [Memory Configuration] menu’ in the “PRIMEQUEST 2000 series Tool Reference’ (CA92344-0539). For setting by OS, see documents of each OS.
Page 94: Table 3.19 Memory Mirror Group
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration If the way to specify mirror size is set to “OS Request” in BIOS menu and the memory size which exceeds maximum size being able to mirror is specified by OS, the partition start up by no mirror. If the way to specify mirror size is set to “BIOS Menu Setting”...
Page 95: Figure 3.29 Status When There Is An Error In The Memory (Mirror Maintenance Mode)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration The memory incorporation status before and after a partition restart is shown below. Status when there is an error in the FIGURE 3.29 memory (mirror maintenance mode) Status when the error had occurred in the system was restarted (mirror maintenance mode) FIGURE 3.30 CA92344-0537-08...
Page 96: Figure 3.31 Status When There Error Has Occurred In The Memory (Memory Capacity Maintenance Mode)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Status when there error has occurred in the FIGURE 3.31 memory (memory capacity maintenance mode) Status when an error has occurred in the FIGURE 3.32 memory (memory capacity maintenance mode) The patterns supported in the combination of memory mirror status and failed DIMM are listed in the table below.
Page 97: Hardware Raid
For details on the Server View RAID, see ‘Server View RAID Management User Manual’. 3.2.9 Cluster configuration For inter-cabinet clustering, clustering with only PRIMEQUEST 2000 series is supported. The inter- cabinet clustering with cabinets other than PRIMEQUEST 2000 series is not supported.
Page 98: Replaceable Components
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.3 Replacing components 3.3.1 Replaceable components Replaceable components and replacement conditions are listed in the table below. Replaceable components and replacement conditions TABLE 3.21 Component name AC power off AC power on AC power on AC power on (Device stop)
Page 99: Replacement Procedures In Hot Maintenance
3.3.3 Replacement procedures in hot maintenance This section describes the procedures before and after replacement in hot maintenance. Procedure before replacement See ‘7.1.2 Power off of Partitions’ in “PRIMEQUEST 2000 series Installation Manual” (CA92344-0536) and stop the relevant partition. Procedure after replacement See ‘7.1.1 Power on of partitions’...
Page 100: Replacing The Battery Backup Unit Of The Uninterrupted Power Supply Unit (Ups)
For details on the standard monitoring function of the operating system see ‘PQ-replace-notification-en’ which can be got from below URL http://www.fujitsu.com/global/products/computing/servers/mission-critical/primequest/documents/manuals/ 3.3.6 Replacing the PCI SSD card This section describes the procedure for replacing the PCI SSD card. Note The PCI SSD card does not support hot replacement.
Page 101 X.x.x is the version number. http://manuals.ts.fujitsu.com/ 4. Power off the partition. For details on powering off, see ‘7.1.2 Powering off Partitions’ in the “PRIMEQUEST 2000 series Installation Manual” (CA92344-0536). 5. Replace the faulty PCI Express card. 6. Power on the partition.
Page 102: Expansion Of Components
You may be required to re-configure the settings after replacing a faulty card to a spare part. (*2) The configuration sheets for PCIe cards are listed and downloadable in the following sites: http://www.fujitsu.com/global/services/computing/server/primequest/ (*1) Functions of option ROM - SR-IOV setting, UMC(Universal Multi-Channel), Boot setting, etc.
Page 103: Procedure Of Expansion In Hot Maintenance
3.4.1 Procedure of expansion in hot maintenance This section describes the procedures before and after expansion in hot maintenance. Procedure before expansion “Stop the relevant partition referring to ‘7.1.2 Powering off Partitions’ in the “PRIMEQUEST 2000 series Installation Manual” (CA92344-0536). Procedure after expansion Start the relevant partition referring to‘7.1.1 Powering on Partitions’...
Page 104: Expansion Of Pci Ssd Card
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot Procedure after expansion Start the required partition referring to 7.1.1 Powering on Partitions’ in the “PRIMEQUEST 2000 series Installation Manual” CA92344-0536). 3.4.3 Expansion of PCI SSD card This section describes the procedure of expanding the PCI SSD card (PCI Express SSD card 785GB / PCI SSD card1.2TB).
Page 105: Processing After Replacement Of A Faulty Sb
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot Immediately after switching to a Reserved SB and the partition has started (booted), the status will be as follows. The Reserved SB is incorporated in the partition in place of the faulty SB. The setting of Reserved SB for multiple partitions is cancelled if the Reserved SB that was incorporated in the partition in place of the faulty SB had been the Reserved SB for multiple partitions before the incorporation.
Page 106: Checking The Source Partition Configuration Information When Switching To A Reserved Sb
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot 1. From the log, analyze all the partitions where a Reserved SB that was incorporated in a rebooted partition place of a faulty SB. For details on the analysis procedure, see ‘3.5.3 Checking the source partition setting information when switching to a Reserved SB’.
Page 107 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot Even if Partition #P, Partition #Q or Partition #R is running, the status of the partition will be as indicated in (1) in the table.
Page 108: Table 3.26 Description Of Partition Status Transition
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot TABLE 3.26 Description of partition status transition Description (the numbers correspond to the status transition) ( 1) Partition #P, Partition #Q and Partition #R are in operation. ( 2) SB #a of Partition #P becomes faulty.
Page 109: Chapter 4 Hot Maintenance In Red Hat Enterprise Linux 6
For the summary of the DR function, applicable rules and corresponding list and restrictions, see ‘3.2.3 Dynamic Reconfiguration (DR)’. For details on the MMB Web-UI/CLI, see respective chapters in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). For details on the OS CLI, see ’5.1 DR command’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344- 0539). CA92344-0537-08...
Page 110: Dr Function Configuration Setting
Enable/Disable is set for the DR function of each partition, from Partition->Partition #x->Mode window of MMB Web-UI. Items for [Dynamic Reconfiguration] of the [Mode] window can be seen below. For details on the Mode window, see respective chapters in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). FIGURE 4.1 [Mode] window (Dynamic Reconfiguration)
Page 111: Dr Command Package Install/ Uninstall
To install dr command package, it is necessary to enable DR function on MMB. The dr command can be applied using the SVIM application wizard. When installing after building the system, procure the package from Fujitsu Web download site, and install following the procedure below. <Common install /uninstall>...
Page 112: Confirming The Status Of Sb Before Sb Hot Add
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB For SB hot add, mount the same number of DIMMs in the SB to be added as that in the Home SB of target partition. Check if the configuration of CPU and DIMMs in arranged SBs to be added is the same as the Home SB in the target partition.
Page 113: How To Deal With Timeout While Os Is Processing Sb Hot Add
/var/log/messages and ‘collaboration program name.log’ made in /opt/FJSVdr-util/var/log directory, if any. Acquire the information of the collaboration program which takes a lot of time by below rpm command and ask the Fujitsu engineer about the cause of its delay. (Example) Checking the developer of the collaboration program “10-FJSVdr-util-kdump-restart”...
Page 114: Operation After Sb Hot Add
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB Dec 17 00:15:34 xxx dr-util[4457]: INFO : 802 : Add CPU30-59 (total 30) Dec 17 00:15:34 xxx dr-util[4457]: INFO : 804 : Add MEM98304-98559,114688-114943 (total 67108864 kiB) Dec 17 00:15:47 xxx dr-util[4457]: INFO : 809 : Added SB3 If “INFO : 809 : Added SBX”...
Page 115 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB # cat /proc/meminfo MemTotal: 98724424 kB MemFree: 96825552 kB Buffers: 30804 kB ：： If below command keeps to be executed, added resources are not reflected. Re-execute the command in order to reflect added resources.
Page 116: Hot Replacement Of Iou
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU Hot replacement of IOU This section describes the hot replacement of the IOU. There are two cases in hot replacement of the IOU: Replacing IOU itself due to trouble of IOU itself or trouble of onboard NIC Replacing, expanding or removing PCI Express card installed in IOU For replacing, expanding or removing PCI Express card, IOU itself does not need to be replaced.
Page 117 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU 0000:82:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:83:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:84:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:85:02.0 PCI bridge: PLX Technology, Inc.
Page 118: Table 4.1 Correspondence Between Bus Addresses And Interface Names
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU 1. Confirm where the NIC is mounted. Confirm the correspondence between PCI Address and interface name of NIC mounted in the IOU which is confirmed by above “dr show IOU” command. Example: When PCI Address is “0000:89:00.0”.
Page 119: Table 4.2 Hardware Address Description Examples
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU Example: eth0 grep eth0 /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="2c:d4:44:f1:44:f0", ATTR{type}=="1", ¥ KERNEL=="eth*", NAME="eth0" The ¥ at the end of a line indicates that there is no line feed. You can always obtain the correct hardware address from the description in etc/udev/rules.d/70- persistent-net.rules regardless of whether the interface is incorporated in bonding.
Page 120 Use the iscsiadm command to log out from the path (iqn) through which the iSCSI card to be replaced is routed, and disconnect the session. Example which confirms the state of session before disconnecting: # /sbin/iscsiadm -m session tcp: [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 tcp: [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0...
Page 121: Dr Operation Of Iou Hot Replacement
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected. Example which confirms the state of session after disconnecting # /sbin/iscsiadm -m session tcp: [1] 192.168.1.64:3260,1 iqn.2000-...
Page 122 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU IOU#3 power-off (3/3) Removing IOU#3 from partition#1 has been completed successfully. Administrator > 5. See Operation Log window or perform “show dynamic_reconfiguration status” command and confirm below messages.
Page 123: Operation After Iou Hot Replacement
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU 4.3.3 Operation after IOU hot replacement Note If SVAgent is installed in the partition, perform below command with root privilege. # /usr/sbin/srvmagt restart NIC on the IOU (including onboard NIC) 1.
Page 124 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU The ¥ at the end of a line indicates that there is no line feed. Example of descriptions in the file after editing # PCI device 0x8086:0x1521 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥...
Page 125 [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 Example which login path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-login c. Use the iscsiadm command to confirm that the target session has been activated.
Page 126: Hot Add Of Iou
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.4 Hot add of IOU ¥_ 3:0:0:0 sdb 8:16 [active][ready] Example of DM-MP display after connecting path # /sbin/multipath -ll mpath1 (36000b5d0006a0000006a104900000000) dm-0 FUJITSU,ETERNUS_DX400 [size=50G][features=0][hwhandler=0][rw] ¥_ round-robin 0 [prio=2][enabled] ¥_ 3:0:0:0 sdb 8:16 [active][ready] ¥_ 5:0:0:0 sdc 8:32 [active][ready] *2: See the ETERNUS Multipath Driver User's Guide (For Linux).
Page 127: Operation After Iou Hot Add
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.4 Hot add of IOU DR operation start (1/3) Assigning IOU#1 to partition#1 (2/3) Power on IOU#1 (3/3) Adding IOU#1 to Partition#1 has been completed successfully. Administrator > 3. See Operation Log window or perform “show dynamic_reconfiguration status” command and confirm below messages.
Page 128: Iou Hot Remove
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove 0000:0a:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:0a:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:0d:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:0d:00.1 Ethernet controller: Intel Corporation I350...
Page 129: Preparation For Iou Hot Remove
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove A NIC on the IOU to be replaced makes an interface independently. Example of single interface: If FC card used for SAN boot is mounted on an IOU to be replaced, hot replacement of the IOU cannot be performed.
Page 130 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove 0000:8f:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0000:8f:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) NIC on the IOU (including onboard NIC) The procedure describes operations where a single NIC is configured as one interface.
Page 131: Table 4.4 Correspondence Between Bus Addresses And Interface Names
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove TABLE 4.4 Correspondence between bus addresses and interface names Interface name Hardware address Bus address Location eth0 0000:89:01.0 Onboard 0 eth1 0000:89:01.1 Onboard 1 eth2 0000:8f:00.0 PCI#0 Note When recording a bus address, include the function number (number after the period).
Page 132: Table 4.5 Hardware Address Description Examples
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove TABLE 4.5 Hardware address description examples Interface name Hardware address Bus address Location eth0 2c:d4:44:f1:44:f0 0000:89:01.0 Onboard 0 eth1 2c:d4:44:f1:44:f1 0000:89:01.1 Onboard 1 00:19:99:d7:36:5f 0000:8f:00.0 PCI#0 eth2 3.
Page 133 [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 134: Dr Operation Of Iou Hot Remove
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove FUJITSU,ETERNUS_DX400 [size=50G][features=0][hwhandler=0][rw] ¥_ round-robin 0 [prio=2][active] ¥_ 3:0:0:0 sdb 8:16 [active][ready] ¥_ 4:0:0:0 sdc 8:32 [active][ready] Example of DM-MP display after disconnecting path # /sbin/multipath -ll...
Page 135: Operation After Iou Hot Remove
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 4.5.3 Operation after IOU hot remove This section describes the process and operation after IOU hot remove. Note If SVAgent is installed in the partition, perform below command with root privilege. # /usr/sbin/srvmagt restart IOU removed from the partition has become “free state”...
Page 136: Overview Of Common Replacement Procedures For Pci Express Cards
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 4.6.1 Overview of common replacement procedures for PCI Express cards This section provides an overview of common replacement procedures for all PCI Express cards. 1.
Page 137 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards For the partition without Dynamic Reconfiguration utility installed Using the PCI Express slot number confirmed in “Confirming the slot number of a PCI Express slot”, confirm that the /sys/bus/pci/ slots directory contains a directory for this slot information, which will be referenced and otherwise used.
Page 138 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 2. Select [Replace Unit] and click [Next]. 3. Select [PCI_Box(PCIC)], click [Next]. CA92344-0537-08...
Page 139 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 5.
Page 140 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears.
Page 141 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 9. Powering on the particular PCIC slot, click [Next]. For how to power on the PCIC slot, see “Powering on and off PCI Express slots” in “4.6.2 PCI Express card replacement procedure in detail”.
Page 142: Fc Card (Fibre Channel Card) Replacement Procedure
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 11. Check the status of replaced PCIC and click [Next]. 12. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next].
Page 143 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards This manual does not describe how to change the configuration of peripherals such as expanding and removing the unit of SAN disk device. To prevent a device name mismatch due to the failure, addition, removal, or replacement of an FC card, access the SAN disk unit by using the by-id name (/dev/disk/by-id/...) for the device name.
Page 144 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards scsi 2:0:0:0: Direct-Access FUJITSU E4000 ¥ 0000 PQ: 1 ANSI: 5 ...(*3) The ¥ at the end of a line indicates that there is no line feed.
Page 145: Network Card Replacement Procedure
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards In this case, check for the relevant message on the FC card incorporation by using the following procedure. a. Confirm the host number. xx in scsixx (xx is a numerical value) in the message is a host number.
Page 146: Table 4.6 Correspondence Between Bus Addresses And Interface Names
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards system information. First, confirm the bus address of the PCI Express slot that has the mounted interface to be replaced. Example: eth0 interface # ls -l /sys/class/net/eth0/device lrwxrwxrwx 1 root root 0 Sep 29 10:17 ¥...
Page 147: Table 4.7 Hardware Address Description Examples
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards hardware address. Example: eth0 [For a single interface] # cat /sys/class/net/eth0/address 00:0e:0c:70:c3:38 Example: eth0 [For a bonding interface] The bonding driver rewrites the values for the slave interface of the bonding device. Confirm the hardware address by executing the following command.
Page 148 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards If the single NIC interface has a VLAN device, you also need to remove the VLAN interface. Perform the following operations (before deactivating the real interface). # /sbin/ifdown ethX.Y # /sbin/vconfig rem ethX.Y [For the SLAVE interface of a bonding device]...
Page 149: Table 4.8 Example Of Interface Information About The Replaced Nic
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards deleted even if the NIC is removed. Leaving the entries of the removed NIC may have the following impact. The interface names defined in the entries of the removed NIC cannot be assigned to the replaced NIC or an added NIC.
Page 150: Table 4.9 Example Of Entered Values Corresponding To The Interface Names Before And After Nic Replacement
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards Confirm that a new hardware address is defined for the bus address. Also confirm that the assigned interface name is the same as that before the NIC replacement. Also confirm that the relevant entries in the above-described table were automatically added to the udev function rule file, /etc/udev/rules.d/70-persistent-net.rules.
Page 151: Table 4.10 Confirmation Of Interface Names
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="00:0e:0c:70:c3:40", ATTR{type}=="1", ¥ KERNEL=="eth*", NAME="eth0" # PCI device 0x****:0x**** (e1000) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="00:0e:0c:70:c3:41", ATTR{type}=="1", ¥ KERNEL=="eth*", NAME="eth1" The ¥...
Page 152: Hot Replacement Procedure For Iscsi (Nic)
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards # /sbin/ifup ethX Also, if the single NIC interface has a VLAN device and the VLAN interface was temporarily removed, restore the VLAN interface. If the priority option has changed, set it again. # /sbin/vconfig add ethX Y # /sbin/ifup ethX.Y (enter command to set VLAN option as needed)
Page 153 [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 154: Hot Addition Of Pci Express Cards
4.7 Hot Addition of PCI Express cards 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 Example which login path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-login c. Use the iscsiadm command to confirm that the target session has been activated.
Page 155: Common Addition Procedures For All Pci Express Cards
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards If the Extended Partitioning is enabled, dr command is not supported for PCI Express card hot replacement. 4.7.1 Common addition procedures for all PCI Express cards 1.
Page 156 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 2. Select [Replace Unit] and click [Next]. 3. Select [PCI_Box(PCIC)], click [Next]. CA92344-0537-08...
Page 157 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 5.
Page 158 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears.
Page 159 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 9. Powering on the particular PCIC slot, click [Next]. For how to power on the PCIC slot, see “Powering on and off PCI Express slots” in “4.6.2 PCI Express card replacement procedure in detail”.
Page 160: Fc Card (Fibre Channel Card) Addition Procedure
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 11. Check the status of added PCIC and click [Next]. 12. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next].
Page 161: Network Card Addition Procedure
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards If all the paths in a mounted disk become hidden when an FC card is hot replaced, unmount the disk. Then, execute PCI hot plug. FC card addition procedure The procedure for adding new FC cards and peripherals is as follows.
Page 162: Figure 4.4 Single Nic Interface And Bonding Configuration Interface
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards FIGURE 4.4 Single NIC interface and bonding configuration interface NIC addition procedure This section describes the procedure for hot plugging only a network card. Note When adding multiple NICs, be sure to add them one by one.
Page 163 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 8. Confirm the hardware address of the newly added interface. Confirm the hardware address (HWaddr) and the created interface by executing the ifconfig command. For a single NIC with multiple interfaces, confirm the hardware addresses of all the created interfaces.
Page 164: Removing Pci Express Cards
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards ONBOOT=yes Note Adding the bonding interface itself also requires the MASTER interface configuration file of the bonding configuration. 10. To add a bonding interface, configure the bonding interface driver settings. If the bonding interface has already been installed, execute the following command to check the descriptions in the configuration file and confirm the setting corresponding to the bonding interface and driver.
Page 165: Common Removal Procedures For All Pci Express Cards
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards Hereafter, description about the operation by using dr commands starts at ‘For the partition with Dynamic Reconfiguration utility installed’ and description about the operation by sysfs starts at ‘For the partition without Dynamic Reconfiguration utility installed’.
Page 166: Network Card Removal Procedure
CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards FC card removal procedure The procedure for removing an FC card and peripherals is as follows. 1. Make the necessary preparations. Stop access to the FC card by stopping applications or by other such means. 2.
Page 167 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards Read the output file path as shown below, and confirm the PCI slot number. /sys/bus/pci/slots/<slot number>/address Notes If the above file path is not output, it indicates that the NIC is not mounted in a PCI slot (e.g., GbE port in the IOU).
Page 168 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards 6. After taking of all cables connected to the NIC, remove the NIC from the PCI Express slot. 7. Remove the interface configuration file. Delete the configuration files of all the interfaces confirmed in step 2, by executing the following command. # rm /etc/sysconfig/network-scripts/ifcfg-ethX When deleting a bonding device, also delete the related bonding items (ifcfg-bondY files).
Page 169: Hot Removal Procedure For Iscsi (Nic)
[2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 170 CHAPTER 4 Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 d. You can confirm the disconnection of sessions on multipath products using DM-MP or ETERNUS multidriver. *1: Write down the DM-MP display contents at the session disconnection.
Page 171: Chapter 5 Hot Maintenance In Red Hat Enterprise Linux 7
(DR)’. For details on the MMB Web-UI/CLI, see respective chapters in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). For details on the OS CLI, see ’5.1 DR command’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344- 0539). 5.1.1 DR function configuration setting Enable/Disable is set for the DR function of each partition, from Partition->Partition #x->Mode window of...
Page 172: Dr Command Package Install/ Uninstall
To install dr command package, it is necessary to enable DR function on MMB. The dr command can be applied using the SVIM application wizard. When installing after building the system, procure the package from Fujitsu Web download site, and install following the procedure below. <Common install /uninstall>...
Page 173: Hot Add Of Sb
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.2 Hot add of SB FJSVdr-util/RPMS/FJSVdr-util-RHEL7-x.x.x-x.noarch.rpm FJSVdr-util/SRPMS/FJSVdr-util-RHEL7-x.x.x-x.noarch.rpm FJSVdr-util/DOC/README.ja_JP.EUC.txt FJSVdr-util/DOC/README.ja_JP.SJIS.txt FJSVdr-util/DOC/README.ja_JP.UTF-8.txt FJSVdr-util/DOC/README.txt FJSVdr-util/INSTALL.sh FJSVdr-util/UNINSTALL.sh <When installing> Install FJSVdr-util-RHEL7-x.x.x-x.noarch.rpm using the following procedure. Become super user. $ su - Execute INSTALL.sh in the FJSVdr-util directory. Depending on the status, the rpm package will be installed or uninstalled.
Page 174: Dr Operation In Sb Hot Add
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.2 Hot add of SB a. Check if the size of the dump disk save area is sufficient for the memory capacity to be added. For details on how to estimate the size required, contact the distributor where you purchased your product, or your sales representative.
Page 175 /var/log/messages and ‘collaboration program name.log’ made in /opt/FJSVdr-util/var/log directory, if any. Acquire the information of the collaboration program which takes a lot of time by below rpm command and ask the Fujitsu engineer about the cause of its delay. (Example) Checking the developer of the collaboration program “10-FJSVdr-util-kdump-restart”...
Page 176: Operation After Sb Hot Add
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.3 Hot remove of SB If “INFO : 808 : Executed user programs at ADD_POST timing” is not output, post-process of the collaboration program is delayed. Check which collaboration program takes a lot of time by seeing /var/log/messages and ‘collaboration program name.log’...
Page 177: Preparing For Sb Hot Remove
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.3 Hot remove of SB 5.3.1 Preparing for SB hot remove The preparation flow is described below. Check the SBs to be removed. Check the SBs to be removed by MMB Web-UI. Open Partition->Partition Configuration window Check the SB to be removed is not Home SB.
Page 178: Dr Operation In Sb Hot Remove
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.3 Hot remove of SB Mem: 132364204 25165476 107198728 10140 14647644 319328 -/+ buffers/cache: 10198504 122165700 Swap: 4194300 4194300 2. Check whether free space of memory is enough. Check memory capacity of SB to be removed. Example: When removing SB#2.
Page 179: Hot Replacement Of Iou
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.4 Hot replacement of IOU SB3: empty If below command keeps to be executed, added resources are not reflected. Re-execute the command in order to reflect added resources. iostat mpstat If SVAgent is installed in the partition, perform below command with root privilege.
Page 180: Preparation For Iou Hot Replacement
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.4 Hot replacement of IOU If FC card used for SAN boot is mounted on an IOU to be replaced, hot replacement of the IOU cannot be performed. The step of hot replacement of IOU is described below in order. 5.4.1 Preparation for IOU hot replacement The description of the flow of preparations is given below.
Page 181: Table 5.1 Correspondence Between Bus Addresses And Interface Names
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.4 Hot replacement of IOU procedure describes operations where a single NIC is configured as one interface. It also describes cases where multiple NICs are bonded together to configure one interface (bonding configuration). For bonding multiple NIC by using PRIMECLUSTER Global Link Services (GLS), see manual of PRIMECLUSTER Global Link Services.
Page 182: Table 5.2 Hardware Address Description Examples
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.4 Hot replacement of IOU Note When recording a bus address, include the function number (number after the period). Confirm the correspondence between the interface name and hardware address Execute below command, checking the correspondence between the interface name and the hardware address.
Page 183 [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 184: Dr Operation Of Iou Hot Replacement
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.4 Hot replacement of IOU *2: See the ETERNUS Multipath Driver User's Guide (For Linux). FC card 1. Stop the access to FC card on IOU by such a way as stopping application. 5.4.2 DR operation of IOU hot replacement This section describes the DR operation for IOU hot replacement.
Page 185: Operation After Iou Hot Replacement
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.4 Hot replacement of IOU Administrator > hotadd partition 1 IOU 3 Are you sure to continue adding IOU#3 to Partition#1? [Y/N] DR operation start (1/3) Assigning IOU#3 to partition#1 (2/3) Power on IOU#3 (3/3) Adding IOU#3 to Partition#1 has been completed successfully.
Page 186 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.4 Hot replacement of IOU Not to change the interface name of upper driver or network script and so on, you must do setting that interface name is assigned by the form of ethX after install. For details, see Red Hat, Inc’s networking guide.
Page 187 [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 Example which login path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-login c. Use the iscsiadm command to confirm that the target session has been activated.
Page 188: Hot Add Of Iou
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.5 Hot add of IOU Update IOU#2 PCI information in Partition#1 has been completed successfully. Administrator > Hot add of IOU This section describes the hot add of the IOU. 5.5.1 Preparation for IOU hot add The description of the flow of preparations is given below.
Page 189: Operation After Iou Hot Add
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.5 Hot add of IOU IOU1: offline IOU2: empty IOU3: empty When newly adding an IOU to a partition, it will be displayed as offline since the IOU is not recognized by the operating system.
Page 190: Iou Hot Remove
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.6 IOU hot remove 0000:28:04.0 PCI bridge: PLX Technology, Inc. Device 8764 (rev aa) 0000:28:05.0 PCI bridge: PLX Technology, Inc. Device 8764 (rev aa) 0000:28:08.0 PCI bridge: PLX Technology, Inc. Device 8764 (rev aa) 0000:28:09.0 PCI bridge: PLX Technology, Inc.
Page 191 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.6 IOU hot remove When the disk connected via the IOU to be removed is used as the dump saving area if kdump, the dump environment is changed to enable the use of another disk. 1.
Page 192: Table 5.4 Correspondence Between Bus Addresses And Interface Names
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.6 IOU hot remove Notes To perform hot replacement in a system where a bonding device is installed, design the system so that it specifies ONBOOT=YES in all interface configuration files (the /etc/sysconfig/network-scripts/ifcfg- eth*files and the /etc/sysconfig/network-scripts/ifcfg-bond*files), regardless of whether the NIC to be replaced is a configuration interface of the bonding device.
Page 193: Table 5.5 Hardware Address Description Examples
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.6 IOU hot remove hardware address. Example: eth0 for a single interface # cat /sys/class/net/eth0/address 2c:d4:44:f1:44:f0 Example: eth0 for a bonding interface # cat /proc/net/bonding/bondY Ethernet Channel Bonding Driver ..Slave interface: eth0 Permanent HW addr: 2c:d4:44:f1:44:f0 You can use this procedure only when the bonding device is active.
Page 194: Dr Operation Of Iou Hot Remove
[2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 195: Operation After Iou Hot Remove
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.6 IOU hot remove 1. Execute the /opt/FJSVdr-util/sbin/dr rm IOU command from the operating system shell. The IOU to be removal will be powered off. Example：To power off IOU3. # /opt/FJSVdr-util/sbin/dr rm IOU3 2.
Page 196: Hot Replacement Of Pci Express Cards
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards Hot Replacement of PCI Express Cards This section describes the following methods of PCI Express card replacement with the PCI Hot Plug (PHP) function: Common replacement operations for all PCI Express cards such as power supply operations Specific operations added to procedures to use a specified card function or a driver for installation...
Page 197 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards Preparing the software using a PCI Express card When a PCI Express card is replaced or removed, there must be no software using the PCI Express card. For this reason, before replacing or removing the PCI Express card, stop the software using the PCI Express card or make the software operations inapplicable.
Page 198 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards This operation installs the device associated with the relevant adapter on the system. After power-on, you need to confirm that the card and driver are correctly installed. The procedures vary depending on the card and driver specifications.
Page 199 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards 3. Select [PCI_Box(PCIC)], click [Next]. 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 CA92344-0537-08...
Page 200 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards 5. Select the radio button of the particular PCIC number and click [Next] 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] CA92344-0537-08...
Page 201 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears. Take off all cables such as LAN cable and FC cable connected to the particular PCIC and replace the particular PCIC with this window displayed.
Page 202 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards 10. The window updating status appears. 11. Check the status of replaced PCIC and click [Next]. CA92344-0537-08...
Page 203: Fc Card (Fibre Channel Card) Replacement Procedure
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards 12. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next]. Post-processing of software using a PCI Express card After replacing a PCI Express card, restart the software stopped before the PCI Express card replacement or make the software operation applicable again, as needed.
Page 204 Adapter on PCI bus 0f device 08 irq 59 ...(*1) lpfc 0000:0d:00.0: 0:1303 Link Up Event x1 received ¥ Data: x1 x0 x10 x0 x0 x0 0 ...(*2) scsi 2:0:0:0: Direct-Access FUJITSU E4000 ¥ 0000 PQ: 1 ANSI: 5 ...(*3) The ¥...
Page 205: Network Card Replacement Procedure
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards Confirm that the driver option of the FC driver (lpfc) is correctly set. For details, contact the distributor where you purchased your product, or your sales representative. Check the FC cable connection status.
Page 206: Figure 5.2 Single Nic Interface And Bonding Configuration Interface
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards Network card (referred to as NIC below) replacement using hot plugging needs specific processing before and after PCI Express slot power-on or power-off. Its procedure also includes the common PCI Express card replacement procedure.
Page 207: Table 5.6 Correspondence Between Bus Addresses And Interface Names
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards /sys/bus/pci/slots/<slot number>/address Notes If the above file path is not output, it indicates that the NIC is not mounted in a PCI Express slot (e.g., GbE port in the IOU).
Page 208: Table 5.7 Hardware Address Description Examples
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards hardware address of other interfaces by repeating the operation with the same command. The following table lists examples of descriptions. TABLE 5.7 Hardware address description examples Interface name Hardware address Bus address...
Page 209: Table 5.8 Example Of Interface Information About The Replaced Nic
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards will be referenced and otherwise used. Below, the slot number confirmed in step 1 is shown at <slot number> in the directory path in the following format, where the directory is the operational target. /sys/bus/pci/slots/<slot number>...
Page 210: Table 5.9 Example Of Entered Values Corresponding To The Interface Names Before And After Nic Replacement
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.7 Hot Replacement of PCI Express Cards c. Match the interface names to the same bus addresses before and after the NIC replacement. d. In the table created in step 10, enter values corresponding to the interface names before and after the NIC replacement.
Page 211: Figure 5.3 Example Of Single Nic Interface
Example which confirms the state of session before disconnecting: # /sbin/iscsiadm -m session tcp: [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 tcp: [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout CA92344-0537-08...
Page 212 [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 Example which login path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-login c. Use the iscsiadm command to confirm that the target session has been activated.
Page 213: Hot Addition Of Pci Express Cards
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards mpath1 (36000b5d0006a0000006a104900000000) dm-0 FUJITSU,ETERNUS_DX400 [size=50G][features=0][hwhandler=0][rw] ¥_ round-robin 0 [prio=1][active] ¥_ 3:0:0:0 sdb 8:16 [active][ready] Example of DM-MP display after connecting path # /sbin/multipath -ll...
Page 214: Pci Express Card Addition Procedure In Detail
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards 5.8.2 PCI Express card addition procedure in detail This section describes operations that must be performed in the PCI Express card addition procedure. Confirming the slot number of a PCI Express slot See ‘Confirming the slot number of a PCI Express slot’...
Page 215 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards 3. Select [PCI_Box(PCIC)], click [Next]. 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 CA92344-0537-08...
Page 216 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards 5. Select the radio button of the particular PCIC number and click [Next] 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] CA92344-0537-08...
Page 217 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears. Add a new PCI Express card with this window displayed. See the figure in ‘B.1 Physical Mounting Locations of Components’...
Page 218 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards 10. The window updating status appears. 11. Check the status of added PCIC and click [Next]. CA92344-0537-08...
Page 219: Fc Card (Fibre Channel Card) Addition Procedure
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards 12. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next]. 5.8.3 FC card (Fibre Channel card) addition procedure The descriptions in this section assume that an FC card is being added.
Page 220: Figure 5.4 Single Nic Interface And Bonding Configuration Interface
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards 6. Power on the PCI Express slot. See ‘Powering on and off PCI Express slots’ in “5.7.2 PCI Express card replacement procedure in detail”.
Page 221 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RXbytes:0 (0.0 b) TX bytes:0 (0.0 b) Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0...
Page 222 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.8 Hot Addition of PCI Express cards interface as follows. In "HWADDR," set the hardware address confirmed in step 8. If multiple NICs are added or if a NIC where multiple interfaces exist is added, create a file for all the interfaces.
Page 223: Removing Pci Express Cards
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.9 Removing PCI Express cards # /sbin/ifup ethX [For the bonding configuration] For a SLAVE interface added to an existing bonding configuration, execute the following command to incorporate it into the bonding configuration. Example: bondY is the bonding interface name, and ethX is the name of the interface to be incorporated.
Page 224: Pci Express Card Removal Procedure In Detail
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.9 Removing PCI Express cards The following sections describe card removal with the required instructions (e.g., commands, configuration file editing) for the operating system and subsystems, together with the actual hardware operations. Step 3 is performed by the field engineer in charge of your system.
Page 225: Figure 5.5 Single Nic Interface And Bonding Configuration Interface
CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.9 Removing PCI Express cards FIGURE 5.5 Single NIC interface and bonding configuration interface NIC removal procedure This section describes the procedure for hot plugging only a network card. Note When removing multiple NICs, be sure to remove them one by one.
Page 226 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.9 Removing PCI Express cards 3. Execute the higher-level application processing required before NIC removal. Stop all access to the interface as follows. Stop the application that was confirmed in step 2 as using the interface, or exclude the interface from the target of use by the application.
Page 227: Hot Removal Procedure For Iscsi (Nic)
[2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 228 CHAPTER 5 Hot Maintenance in Red Hat Enterprise Linux 7 5.9 Removing PCI Express cards # /sbin/iscsiadm -m session tcp: [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 d. You can confirm the disconnection of sessions on multipath products using DM-MP or ETERNUS multidriver.
Page 229: Chapter 6 Pci Card Hot Maintenance In Suse Linux Enterprise Server 11
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 This chapter describes hot maintenance of PCI cards in SUSE Linux Enterprise Server 11. Hot Replacement of PCI Express Cards This section describes the following methods of PCI Express card replacement with the PCI Hot Plug (PHP) function:...
Page 230 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards Confirming the installation of the PCI Hot Plug driver The Hot Plug driver must be installed on the system before you hot plug individual cards. Hot plug driver module for PCI Express cards: pciehp Confirm the installation of the Hot Plug driver by using the following procedure.
Page 231 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards Note After power-on, you need to confirm that the card and driver are correctly installed. The procedures vary depending on the card and driver specifications. For the appropriate procedures, see the respective manuals. Operation for Hot replacement of PCI Express card by Maintenance Wizard This item describes Operation for Hot replacement of PCI Express card (PCIC) by Maintenance Wizard Below works are performed by the field engineer in charge of your system.
Page 232 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 5.
Page 233 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears.
Page 234 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards 9. After replacing the particular PCIC and powering on the particular PCIC slot, click [Next]. For how to power on the PCIC slot, see “Powering on and off PCI Express slots” in “6.1.2 PCI Express card replacement procedure in detail”.
Page 235: Fc Card (Fibre Channel Card) Replacement Procedure
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards 11. Check the status of replaced PCIC and click [Next]. 12. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next].
Page 236 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards To prevent a device name mismatch due to the failure, addition, removal, or replacement of an FC card, access the SAN disk unit by using the by-id name (/dev/disk/by-id/...) for the device name. If all the paths in a mounted disk become hidden when an FC card is hot replaced, unmount the disk.
Page 237 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards Data: x1 x0 x10 x0 x0 x0 0 ...(*2) scsi 2:0:0:0: Direct-Access FUJITSU E4000 ¥ 0000 PQ: 1 ANSI: 5 ...(*3) The ¥...
Page 238: Figure 6.1 Single Nic Interface And Bonding Configuration Interface
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards In this case, check for the relevant message on the FC card incorporation by using the following procedure. a. Confirm the host number. xx in scsixx (xx is a numerical value) in the message is a host number.
Page 239: Table 6.1 Correspondence Between Bus Addresses And Interface Names
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards 2. Confirm the slot number of the PCI Express slot that has the mounted interface. Confirm the interface mounting location through the configuration file information and the operating system information.
Page 240: Table 6.2 Hardware Address Description Examples
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards Confirm the correspondence between the interface name and hardware address. Execute the following command, and confirm the correspondence between the interface name and hardware address.
Page 241 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards # /sbin/ifdown ethX If the single NIC interface has a VLAN device, you also need to remove the VLAN interface. Perform the following operations (before deactivating the real interface).
Page 242: Table 6.3 Example Of Interface Information About The Replaced Nic
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards b. Edit the udev function rule file, /etc/udev/rules.d/70-persistent-net.rules, to delete or comment out the entry lines of all the interface names and hardware addresses confirmed in the above step 2. The following example shows editing of the udev function rule file.
Page 243: Table 6.4 Example Of Entered Values Corresponding To The Interface Names Before And After Nic Replacement
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards 14. Deactivate each newly created interface. The interfaces created for the replaced NIC may be active because power is on to the PCI Express slot. In such cases, you need to deactivate them before changing the interface configuration file.
Page 244: Table 6.5 Confirmation Of Interface Names
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards The ¥ at the end of a line indicates that there is no line feed. c. Reflect the edited rules again. Repeat the process done in step 10 to reflect the rules.
Page 245: Figure 6.2 Example Of Single Nic Interface
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.1 Hot Replacement of PCI Express Cards [For SLAVE under bonding] Execute the following command to incorporate the SLAVE interface into the existing bonding configuration. Incorporate all the necessary interfaces. # /sbin/ifenslave bondY ethX The VLAN-related operation is normally not required because a VLAN is created on the bonding device.
Page 246 [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 247: Hot Addition Of Pci Express Cards
–-login c. Use the iscsiadm command to confirm that the target session has been activated. Example which confirms the state of session after connecting # /sbin/iscsiadm -m session tcp: [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 tcp: [3] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 d.
Page 248: Pci Express Card Addition Procedure In Detail
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards 6.2.2 PCI Express card addition procedure in detail This section describes operations that must be performed in the PCI Express card addition procedure. Confirming the installation of the PCI Hot Plug driver See ‘Confirming the installation of the PCI Hot Plug driver’...
Page 249 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards 3. Select [PCI_Box(PCIC)], click [Next]. 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 CA92344-0537-08...
Page 250 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards 5. Select the radio button of the particular PCIC number and click [Next] 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] CA92344-0537-08...
Page 251 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears. Add a new PCI Express card with this window displayed. See the figure in ‘B.1 Physical Mounting Locations of Components’...
Page 252 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards 10. The window updating status appears. 11. Check the status of added PCIC and click [Next]. CA92344-0537-08...
Page 253: Fc Card (Fibre Channel Card) Addition Procedure
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards 12. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next]. 6.2.3 FC card (Fibre Channel card) addition procedure The descriptions in this section assume that an FC card is being added.
Page 254: Figure 6.3 Single Nic Interface And Bonding Configuration Interface
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards 7. Power on the PCI Express slot. See ‘Powering on and off PCI Express slots’ in “6.1.2 PCI Express card replacement procedure in detail”.
Page 255 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RXbytes:0 (0.0 b) TX bytes:0 (0.0 b) Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1...
Page 256 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.2 Hot Addition of PCI Express cards 10. Create an interface configuration file. Create an interface configuration file (/etc/sysconfig/network/ifcfg-ethX) for the newly created interface as follows. In "HWADDR," set the hardware address confirmed in step 9. If multiple NICs are added or if a NIC where multiple interfaces exist is added, create a file for all the interfaces.
Page 257: Removing Pci Express Cards
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.3 Removing PCI Express cards [For a single NIC interface] Execute the following command to activate the interface. Activate all the necessary interfaces. # /sbin/ifup ethX [For the bonding configuration] For a SLAVE interface added to an existing bonding configuration, execute the following command to incorporate it into the bonding configuration.
Page 258: Fc Card (Fibre Channel Card) Removal Procedure
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.3 Removing PCI Express cards Preparing the software using a PCI Express card See ‘Preparing the software using a PCI Express card’ in “6.1.2 PCI Express card replacement procedure in detail”.
Page 259: Figure 6.4 Single Nic Interface And Bonding Configuration Interface
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.3 Removing PCI Express cards FIGURE 6.4 Single NIC interface and bonding configuration interface NIC removal procedure This section describes the procedure for hot plugging only a network card. Note When removing multiple NICs, be sure to remove them one by one.
Page 260 CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.3 Removing PCI Express cards The ¥ at the end of a line indicates that there is no line feed. As the above example shows, when more than one interface is displayed, they are on the same NIC. 4.
Page 261: Hot Removal Procedure For Iscsi (Nic)
CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 6.3 Removing PCI Express cards ATTR{address}=="00:0e:0c:70:c3:40", ATTR{type}=="1", ¥ KERNEL=="eth*", NAME="eth10" The ¥ at the end of a line indicates that there is no line feed. [Example of descriptions in the file after editing] The entries for the eth10 interface are commented out.
Page 262 [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 263: Chapter 7 Pci Card Hot Maintenance In Suse Linux Enterprise Server 12
(DR)’. For details on the MMB Web-UI/CLI, see respective chapters in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). For details on the OS CLI, see ’5.1 DR command’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344- 0539). 7.1.1 DR function configuration setting Enable/Disable is set for the DR function of each partition, from Partition->Partition #x->Mode window of...
Page 264: Figure 7.1 [Mode] Window (Dynamic Reconfiguration)
This section describes the install /uninstall of the dr command package. The dr command can be applied using the SVIM application wizard. When installing after building the system, procure the package from Fujitsu Web download site, and install following the procedure below. <Common install /uninstall>...
Page 265: Preparing For Sb Hot Add
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.2 Hot add of SB FJSVdr-util/DOC/README.ja_JP.EUC.txt FJSVdr-util/DOC/README.ja_JP.SJIS.txt FJSVdr-util/DOC/README.ja_JP.UTF-8.txt FJSVdr-util/DOC/README.txt FJSVdr-util/INSTALL.sh FJSVdr-util/UNINSTALL.sh <When installing> Install FJSVdr-util-SLES12-x.x.x-x.noarch.rpm using the following procedure. Become super user. $ su - Execute INSTALL.sh in the FJSVdr-util directory. Depending on the status, the rpm package will be installed or uninstalled.
Page 266: Dr Operation In Sb Hot Add
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.2 Hot add of SB Check for any errors in the SB to be added. Example：How to check from the MMB Web-UI Open System >SB >SB #n window. Check if the status of the [Board Information] is ‘OK’.
Page 267 /var/log/messages and ‘collaboration program name.log’ made in /opt/FJSVdr-util/var/log directory, if any. Acquire the information of the collaboration program which takes a lot of time by below rpm command and ask the Fujitsu engineer about the cause of its delay. (Example) Checking the developer of the collaboration program “10-FJSVdr-util-kdump-restart”...
Page 268: Operation After Sb Hot Add
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.3 Hot remove of SB The developer of the collaboration program can be confirmed by below rpm command. Ask the developer about the cause of its delay. (Example) Checking the developer of the collaboration program “10-FJSVdr-util-kdump-restart” $ rpm -qif /opt/FJSVdr-util/user_command/10-FJSVdr-util- kdump-restart Rebooting the partition is recommended because SB hot add process has been imperfect state.
Page 269: Confirming The Status Of Sb Before Sb Hot Remove
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.3 Hot remove of SB Check the SBs to be removed. Check the SBs to be removed by MMB Web-UI. Open Partition->Partition Configuration window Check the SB to be removed is not Home SB. If processes on operating system are fixed to CPU and node on SB to be removed, change those settings.
Page 270: Dr Operation In Sb Hot Remove
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.3 Hot remove of SB Active(anon): 7587292 kB Inactive(anon): 8864 kB Active(file): 65568 kB Inactive(file): 14901404 kB Free memory space = MemFree + Inactive(anon) + Active(file) + Inactive(file) = 107200452KB + 8864KB + 65568KB + 14901404KB = 122176288KB Free memory space after removing SB = “free memory space”...
Page 271: Hot Replacement Of Iou
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.4 Hot replacement of IOU Hot replacement of IOU This section describes the hot replacement of the IOU. There are two cases in hot replacement of the IOU: Replacing IOU itself due to trouble of IOU itself or trouble of onboard NIC Replacing, expanding or removing PCI Express card installed in IOU For replacing, expanding or removing PCI Express card, IOU itself does not need to be replaced.
Page 272 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.4 Hot replacement of IOU 0000:82:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:83:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:84:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:85:02.0 PCI bridge: PLX Technology, Inc.
Page 273: Table 7.1 Correspondence Between Bus Addresses And Interface Names
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.4 Hot replacement of IOU 1. Confirm where the NIC is mounted. Confirm the correspondence between PCI Address and interface name of NIC mounted in the IOU which is confirmed by above “dr show IOU”...
Page 274 Use the iscsiadm command to log out from the path (iqn) through which the iSCSI card to be replaced is routed, and disconnect the session. Example which confirms the state of session before disconnecting: # /sbin/iscsiadm -m session tcp: [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- CA92344-0537-08...
Page 275: Dr Operation Of Iou Hot Replacement
[2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 276 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.4 Hot replacement of IOU 4. Execute “hotremove” command on MMB console. Example: removing IOU 3 from partition 1 Administrator > hotremove partition 1 IOU 3 Are you sure to continue removing IOU#3 from Partition#1? [Y/N]: Y DR operation start (1/3) Remove IOU#3 (2/3)
Page 277: Table 7.3 Example Of Interface Information About Interfaces After Replacement
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.4 Hot replacement of IOU 13. Execute “/opt/FJSVdr-util/sbin/dr add IOU” command on the shell of OS. The IOU to be removed will turn on. Example: turning on IOU 3 # /opt/FJSVdr-util/sbin/dr add IOU3 7.4.3 Operation after IOU hot replacement Note...
Page 278 [1] 192.168.1.64:3260,1 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm0ca0p0 Example which login path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-login c. Use the iscsiadm command to confirm that the target session has been activated.
Page 279: Preparation For Iou Hot Add
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.5 Hot add of IOU tcp: [3] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 d. You can confirm the activation of sessions on multipath products using DM-MP or ETERNUS multidriver. *1: Write down the DM-MP display contents at the session activation.
Page 280: Dr Operation Of Iou Hot Add
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.5 Hot add of IOU Check if the I/O device is normally operating in the free partition. During addition, I/O pre-diagnostic process is not executed. 7.5.2 DR operation of IOU hot add This section describes the DR operation for IOU hot add.
Page 281 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.5 Hot add of IOU 0000:04:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:05:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:06:02.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:06:08.0 PCI bridge: PLX Technology, Inc.
Page 282: Iou Hot Remove
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.6 IOU hot remove IOU hot remove The description of the flow of the preparation is as follows. Note If iSCSI (NIC) is mounted on an IOU, hot replacement of the IOU can be performed only if all of below conditions are satisfied.
Page 283 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.6 IOU hot remove 0000:89:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:89:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:8c:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:8c:00.1 Ethernet controller: Intel Corporation I350...
Page 284: Table 7.4 Correspondence Between Bus Addresses And Interface Names
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.6 IOU hot remove Execute “ethtool -p” command, making the LED of NIC blinked. Check IOU or PCI_Box connected to the IOU, checking in which slots the NIC is mounted, (e.g. PCI#0) Example: Blinking the LED of the NIC corresponding to interface “eth0”...
Page 285 [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 286: Dr Operation Of Iou Hot Remove
[active][ready] ¥_ 4:0:0:0 sdc 8:32 [active][ready] Example of DM-MP display after disconnecting path # /sbin/multipath -ll mpath1 (36000b5d0006a0000006a104900000000) dm-0 FUJITSU,ETERNUS_DX400 [size=50G][features=0][hwhandler=0][rw] ¥_ round-robin 0 [prio=1][enabled] ¥_ 3:0:0:0 sdb 8:16 [active][ready] *2: See the ETERNUS Multipath Driver User's Guide (For Linux).
Page 287: Hot Replacement Of Pci Express Cards
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards If SVAgent is installed in the partition, perform below command with root privilege. # /usr/sbin/srvmagt restart IOU removed from the partition has become “free state” where it does not belong to any partition. You can perform below operations: Pull up the IOU from the cabinet physically.
Page 288: Pci Express Card Replacement Procedure In Detail
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards 2. Powering off a PCI slot 3. Replacing a PCI card This step is performed by the field engineer in charge of your system. 4.
Page 289 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards Confirm that the PCI Express card in the slot is enabled or disabled by displaying the "power" file contents in this directory. # cat /sys/bus/pci/slots/<slot number>/power When displayed, "0"...
Page 290 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards 2. Select [Replace Unit] and click [Next]. 3. Select [PCI_Box(PCIC)], click [Next]. CA92344-0537-08...
Page 291 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 5.
Page 292 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears.
Page 293 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards 9. After replacing the particular PCIC and powering on the particular PCIC slot, click [Next]. For how to power on the PCIC slot, see “Powering on and off PCI Express slots” in “7.1.2 PCI Express card replacement procedure in detail”.
Page 294: Fc Card (Fibre Channel Card) Replacement Procedure
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards 11. Check the status of replaced PCIC and click [Next]. 12. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next].
Page 295 Adapter on PCI bus 0f device 08 irq 59 ...(*1) lpfc 0000:0d:00.0: 0:1303 Link Up Event x1 received ¥ Data: x1 x0 x10 x0 x0 x0 0 ...(*2) scsi 2:0:0:0: Direct-Access FUJITSU E4000 ¥ 0000 PQ: 1 ANSI: 5 ...(*3)
Page 296 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards The ¥ at the end of a line indicates that there is no line feed. If only the message in (*1) is displayed but the next line is not displayed or if the message in (*1) is not displayed, the FC card replacement itself was unsuccessful.
Page 297: Figure 7.1 Single Nic Interface And Bonding Configuration Interface
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards a. Confirm the host number. xx in scsixx (xx is a numerical value) in the message is a host number. In the above example, the host number is 10.
Page 298: Table 7.6 Correspondence Between Bus Addresses And Interface Names
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards # ls -l /sys/class/net/eth0/device lrwxrwxrwx 1 root root 0 Sep 29 10:17 ¥ /sys/class/net/eth0/device ->../../../0000:00:01.2/0000:08:00.2/0000:0b:01.0 The ¥ at the end of a line indicates that there is no line feed. Excluding the rest of the directory path, check the part corresponding to the file name in the symbolic link destination file of the output results.
Page 299: Table 7.7 Hardware Address Description Examples
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards # cat /sys/class/net/eth0/address 00:0e:0c:70:c3:38 Example: eth0 [For a bonding interface] The bonding driver rewrites the values for the slave interface of the bonding device. Confirm the hardware address by executing the following command.
Page 300 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards # /sbin/ifdown ethX.Y # /sbin/vconfig rem ethX.Y [For the SLAVE interface of a bonding device] If the bonding device is operating in mode 1, use the following steps to exclude SLAVE interface to be replaced from the bonding configuration.
Page 301: Table 7.8 Example Of Interface Information About The Replaced Nic
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards The interface names defined in the entries of the removed NIC cannot be assigned to the replaced NIC or an added NIC. For this reason, delete or comment out the entries of the removed NIC from the udev function rule file.
Page 302: Table 7.9 Example Of Entered Values Corresponding To The Interface Names Before And After Nic Replacement
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards Also confirm that the relevant entries in the above-described table were automatically added to the udev function rule file, /etc/udev/rules.d/70-persistent-net.rules. Note The correspondence between the bus address and interface name may be different from that before NIC replacement.
Page 303: Table 7.10 Confirmation Of Interface Names
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards KERNEL=="eth*", NAME="eth0" # PCI device 0x****:0x**** (e1000) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="00:0e:0c:70:c3:41", ATTR{type}=="1", ¥ KERNEL=="eth*", NAME="eth1" The ¥ at the end of a line indicates that there is no line feed. c.
Page 304: Figure 7.2 Example Of Single Nic Interface
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.7 Hot Replacement of PCI Express Cards Also, if the single NIC interface has a VLAN device and the VLAN interface was temporarily removed, restore the VLAN interface. If the priority option has changed, set it again. # /sbin/vconfig add ethX Y # /sbin/ifup ethX.Y (enter command to set VLAN option as needed)
Page 305 [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 306: Hot Addition Of Pci Express Cards
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-login c. Use the iscsiadm command to confirm that the target session has been activated.
Page 307: Pci Express Card Addition Procedure In Detail
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards 3. Adding a PCI card This step is performed by the field engineer in charge of your system. 4. Powering on a PCI Express slot. 5.
Page 308 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards 3. Select [PCI_Box(PCIC)], click [Next]. 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 CA92344-0537-08...
Page 309 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards 5. Select the radio button of the particular PCIC number and click [Next] 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] CA92344-0537-08...
Page 310 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears. Add a new PCI Express card with this window displayed. See the figure in ‘B.1 Physical Mounting Locations of Components’...
Page 311 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards 10. The window updating status appears. 11. Check the status of added PCIC and click [Next]. CA92344-0537-08...
Page 312: Fc Card (Fibre Channel Card) Addition Procedure
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards 12. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next]. 7.8.3 FC card (Fibre Channel card) addition procedure The descriptions in this section assume that an FC card is being added.
Page 313: Figure 7.3 Single Nic Interface And Bonding Configuration Interface
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards 7. Check whether there is an error in added FC card by MMB Maintenance Wizard. This step is performed by the field engineer in charge of your system. For details on the operation of replacement, see step 8 to 11 of ‘Operation for Hot replacement of PCI Express card by Maintenance Wizard’...
Page 314 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RXbytes:0 (0.0 b) TX bytes:0 (0.0 b) 2.
Page 315 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.8 Hot Addition of PCI Express cards used. To install a new interface, you can use a new interface name different from the one automatically assigned by the system. Normally, there is no requirement on the name specified for a new interface. To use an interface name other than the one automatically assigned by the system, follow the instructions in step 14 of the ‘NIC replacement procedure’...
Page 316: Removing Pci Express Cards
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.9 Removing PCI Express cards incorporate it into the bonding configuration. Example: bondY is the bonding interface name, and ethX is the name of the interface to be incorporated. # /sbin/ifenslave bondY ethX For a newly added bonding interface with a SLAVE interface, execute the following command to activate the interfaces.
Page 317: Pci Express Card Removal Procedure In Detail
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.9 Removing PCI Express cards 7.9.2 PCI Express card removal procedure in detail This section describes operations that must be performed in the PCI Express card removal procedure. Preparing the software using a PCI Express card See ‘Preparing the software using a PCI Express card’...
Page 318: Figure 7.4 Single Nic Interface And Bonding Configuration Interface
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.9 Removing PCI Express cards FIGURE 7.5 Single NIC interface and bonding configuration interface NIC removal procedure This section describes the procedure for hot plugging only a network card. Note When removing multiple NICs, be sure to remove them one by one.
Page 319 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.9 Removing PCI Express cards 3. Execute the higher-level application processing required before NIC removal. Stop all access to the interface as follows. Stop the application that was confirmed in step 2 as using the interface, or exclude the interface from the target of use by the application.
Page 320: Hot Removal Procedure For Iscsi (Nic)
CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.9 Removing PCI Express cards The ¥ at the end of a line indicates that there is no line feed. [Example of descriptions in the file after editing] The entries for the eth10 interface are commented out.
Page 321 [2] 192.168.2.66:3260,3 iqn.2000- 09.com.fujitsu:storage-system.eternus- dx400:00001049.cm1ca0p0 Example which logout path going through a NIC to be replaced: # /sbin/iscsiadm -m node -T iqn.2000-09.com.fujitsu:storage- system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –-logout c. Use the iscsiadm command to confirm that the target session has been disconnected.
Page 322 CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12 7.9 Removing PCI Express cards CA92344-0537-08...
Page 323: Chapter 8 Replacement Of Hdd/Ssd
In PRIMEQUEST 2400E3/2800E3/2800B3/2400E2/2800E2/2800B2, it is required to use HII Configuration Utility for replacing a HDD or SSD. For details on HII Configuration Utility, see ‘SAS3 12 Gb/s MegaRAID SAS Software’. For how to start HII Configuration Utility, see “PRIMEQUEST 2000 series Installation Manual” (CA92344-0536) In PRIMEQUEST 2400E/2800E/2800B, it is required to use WebBIOS for replacing a HDD or SSD.
Page 324: Preventive Replacement Of Hdd/Ssd With Hardware Raid Configuration
Confirm whether [Status] of replaced HDD or SSD has been already ‘Operational’ by [System] – [SB] – [SBx] window of MMB Web-UI. For details on [SBx] window, see ‘1.2.13 [SB] menu’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). For replacement of a HDD or SSD included in a DU Confirm whether [Status] of replaced HDD or SSD has been already ‘Operational’...
Page 325 A HDD or SSD which S.M.A.R.T has predicted to fail is a HDD or SSD with its [status] ‘SMART error’ in [System] – [SB] – [SBx] window of MMB Web-UI. For details on [SBx] window, see ‘1.2.13 [SB] menu’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). When S.M.A.R.T predicted to fail a HDD or SSD included in a DU A HDD or SSD which S.M.A.R.T has predicted to fail is a HDD or SSD with its [status] ‘SMART error’...
Page 326: Preventive Replacement Of Failed Hdd/Ssd With Raid 1, Raid 1E, Raid 5, Raid 6, Or Raid 10 Configuration
Confirm whether [Status] of replaced HDD or SSD has been already ‘Operational’ by [System] – [SB] – [SBx] window of MMB Web-UI. For details on [SBx] window, see ‘1.2.13 [SB] menu’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). For replacement of a HDD or SSD included in a DU Confirm whether [Status] of replaced HDD or SSD has been already ‘Operational’...
Page 327: Replacement Of Hdd/Ssd In Case Hot Replacement Cannot Be Performed
CHAPTER 8 Replacement of HDD/SSD 8.3 Replacement of HDD/SSD in case hot replacement cannot be performed Replacement of HDD/SSD in case hot replacement cannot be performed In below cases, hot replacement of the failed HDD or SSD cannot be performed. Case where multiple deadlock occurs Multiple deadlock occurs when more than one hard disk fail to be recognized at the same time.
Page 328: Chapter 9 Pci Express Card Hot Maintenance In Windows
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.1 Overview of Hot Maintenance CHAPTER 9 PCI Express card Hot Maintenance in Windows This chapter describes the hot plugging procedure for PCI Express cards in Windows. This procedure is for the PRIMEQUEST 2400E3/2800E3/2800B3/2400E2/2800E2/2800B2/2400E/2800E/2800B.
Page 329: Common Hot Plugging Procedure For Pci Express Cards
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 4. Replace PCI card by using MMB Maintenance Wizard. This step is performed by the field engineer in charge of your system. 5.
Page 330 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards Note In case of multi-function card, there are some cards that have same segment number, same bus number, and different function numbers. In this case, please perform Step.2 and Step.3 of follows respectively.
Page 331 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards Follow dialog will be opened, and click [Yes]. 3. Stop target PCI card by using safely remove devices from computer. Click Icon of Safely remove devices from computer at information zone in lower-right of desktop display.
Page 332 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 2. Check [Replace Unit] button, and click [Next] button. 3. Check [PCI_Box(PCIC)] button, and click [Next] button. CA92344-0537-08...
Page 333 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 4. Check the button of the target PCI_Box number, and click [Next] button. For this example, it is a procedure of hot replacement of a PCI card at PCIC#1 mounted in PCI_Box#0.
Page 334 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 6. Check [Hot Partition Maintenance(Target unit in a running partition.)] button, and click [Next] button. 7. It will be Maintenance mode (Information zone: gray background), and instruction pages to remove target PCI card will be opened.
Page 335 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 8. After replacing target PCI card, mount cables other than LAN cables and click [Next] button. 9. Status updating menu will be opened. CA92344-0537-08...
Page 336 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 10. Confirm status of target replaced PCI card, and click [Next] button. 11. Confirm Maintenance Mode is released (information zone: non-gray background), and click [OK] button.
Page 337: Addition Procedure
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 6. Mount all cables connected to the particular PCI card. This step is performed by the field engineer in charge of your system. 9.2.2 Addition procedure 1.
Page 338 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 3. Check [PCI_Box(PCIC)] button, and click [Next] button. 4. Check the button of the target PCI_Box number, and click [Next] button. For this example, it is a procedure of hot addition of a PCI card at PCIC#1 mounted in PCI_Box#0. CA92344-0537-08...
Page 339 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 5. Check button of target PCIC number for adding, and click [Next] button. 6. Check [Hot Partition Maintenance (Target unit in a running partition.)] button, and click [Next] button. CA92344-0537-08...
Page 340 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 7. It will be Maintenance mode (Information zone: gray background), and instruction pages to add target PCI card will be opened. Add PCI card with opening this page. Note Don’t click [Next] Button before adding PCI card.
Page 341 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.2 Common Hot Plugging Procedure for PCI Express cards 9. Status updating menu will be opened. 10. Confirm status of target added PCI card, and click [Next] button. CA92344-0537-08...
Page 342: About Removal
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.3 NIC Hot Plugging 11. Confirm Maintenance Mode is released. (information zone: non-gray background), and click [OK] button. 3. Confirm replaced PCI card by using Device Manager. After replacement of target PCI card, open Device Manager, and confirm that the target device is recognized correctly.
Page 343: Hot Plugging A Nic Incorporated Into Teaming
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.3 NIC Hot Plugging 9.3.1 Hot plugging a NIC incorporated into teaming This section describes the hot plugging procedure for a NIC incorporated into teaming. Note Be sure to perform hot plugging after removing the card. If the card is not removed, the operating system may stop.
Page 344 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.3 NIC Hot Plugging 5. The following message appears. Click the [Yes] button. 6. Disable target NIC in Device manager. Disable NIC with step 2-b at ‘9.2.1 Replacement procedure’ in ‘9.2 Common Hot Plugging Procedure for PCI Express cards’.
Page 345 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.3 NIC Hot Plugging 11. On the [Teaming] tab, check [Team this adapter with other adapters], select the team into which the adapter was incorporated before the replacement, and click the [OK] button. 12.
Page 346: Hot Plugging A Non-Redundant Nic
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging 13. Mount all cables connected to the particular PCI card (PCIC). This step is performed by the field engineer in charge of your system. 9.3.2 Hot plugging a non-redundant NIC This section describes the hot plugging procedure in networks without redundancy (a NIC is not incorporated into teaming).
Page 347: Hot Plugging An Fc Card Incorporated With The Eternus Multipath Driver
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging In case of using SVAS or SVagent, “Source: SVAS or SVagent, ID: 25004 Error massage” is logged in SEL when replacing, it is no problem. 9.4.1 Hot plugging an FC card incorporated with the ETERNUS multipath driver This section describes the hot plugging procedure for an FC card incorporated with the ETERNUS multipath driver.
Page 348 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging Select Maintenance System Mode. Select [Hot Partition Maintenance], and click [Next] button. Confirm entering Maintenace Mode. Maintenance Mode is set. Information area is shown in grey. CA92344-0537-08...
Page 349 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging 3. Confirm physical location, segment number and bus number of target NIC. Confirm the physical location, segment number and bus number with step 1 at ‘9.2.1 Replacement procedure’...
Page 350 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging See WWN and port number of target device. Select Port WWN of target FC card in left pane, and select [port Information] tab in right pane. WWN is written at “Port WWN”...
Page 351 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging Close OneCommand Manager. Case: Qlogic FC card a. Open QConverge Console CLI, and identify target device from the bus number in step 3. Select “1: Adapter Information” in [Main Menu]. b.
Page 352 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging c. Select the device of the same type of target FC card in [Adapter Information]. d. Confirm “PCI Bus Number” of FC card, and look for the device which has same bus number you confirmed in step 3.
Page 353 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging Confirm WWN and port number of target device. WWN is the information described as “WWPN:” of target FC card in [Adapter Information]. Confirm firmware version of target device. QConverge Console GUI, and select device name of target FC card in left pane, and see [Port Info].
Page 354 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging Close QConverge Console CLI/GUI. 5. Open ETERNUS Multipath Manager and place all the devices to be replaced offline. Make all devices which match port numbers checked at step 4-b offline and close ETERNUS multipath manager.
Page 355 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging 8. Stop target FC card by using safely remove device from computer. Stop FC card with step 2-a at ‘9.2.1 Replacement procedure’ in ‘9.2 Common Hot Plugging Procedure for PCI Express cards’.
Page 356 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging Release Maintenance Mode. Information of the partition where you release Maintenance Mode is shown. Confirm whether the partition is the particular partition or not. Pop-up of confirmation appears. Click [Next] button. Confirm the release of Maintenance Mode.
Page 357 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.4 FC Card Hot Plugging 11. Confirm firmware version of replaced FC card. It is required that the firmware version of new FC card is same as the FC card which had been replaced. If the firmware version of new FC card is coincident with that of the FC card which had been replaced (current firmware version), it is not necessary to update the firmware version of new FC card to current firmware version.
Page 358: Fc Card Addition Procedure
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.5 Hot Replacement Procedure for iSCSI 14. Restart services for only Qlogic FC cards. Using ‘Services’ window in ‘Computer Management’, restart ‘QLogic Management Suite Java Agent’. 9.4.2 FC card addition procedure Referring to 9.2 Common Hot Plugging Procedure for PCI Express cards, add an FC card.
Page 359 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.5 Hot Replacement Procedure for iSCSI 6. Click the [Sessions] tab in the [Properties] window, and click the [MCS] button. 7. The [Source Portal] column in the [Multiple Connected Session (MCS)] window displays IP addresses. Check whether any IP address matches that recorded in step 3.
Page 360 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.5 Hot Replacement Procedure for iSCSI 8. Click the [Cancel] button to return to [Properties] window shown in step 5, and click the [Cancel] button again to return to the [iSCSI Initiator Properties] window shown in step 5. 9.
Page 361 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.5 Hot Replacement Procedure for iSCSI 10. Record the values displayed in the [Address] column in the [Devices] window (Port 2: Bus 0: Target 0: LUN 0, in this example). CA92344-0537-08...
Page 362: Disconnecting Mpd
CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.5 Hot Replacement Procedure for iSCSI 9.5.2 Disconnecting MPD This section describes the procedure for disconnecting MPD. 1. Start ETERNUS Multipath Manager. 2. Confirm the address value recorded in step 10 in 9.5.1 Confirming the incorporation of a card with MPD.
Page 363 CHAPTER 9 PCI Express card Hot Maintenance in Windows 9.5 Hot Replacement Procedure for iSCSI 6. Replace NIC by using MMB Maintenance Wizard. Replace NIC with step 4 at 9.2.1 Replacement procedure 9.2 Common Hot Plugging Procedure for PCI Express cards.
Page 364: Chapter 10 Backup And Restore
Be sure to periodically backup server configuration information in case of such events. The PRIMEQUEST 2000 series server cannot be connected to an FDD (floppy disk) for backup, restore, or other such operations. To use an FDD, connect it to a remote PC or another server connected to the PRIMEQUEST 2000 series server.
Page 365: Figure 10.1 [Backup Bios Configuration] Window
CHAPTER 10 Backup and Restore 10.1 Backing Up and Restoring Configuration Information FIGURE 10.1 [Backup BIOS Configuration] window Backing up UEFI configuration information 1. Select the radio button of the partition for which to back up the configuration information. Then, click the [Backup] button.
Page 366: Figure 10.2 [Restore Bios Configuration] Window
CHAPTER 10 Backup and Restore 10.1 Backing Up and Restoring Configuration Information FIGURE 10.2 [Restore BIOS Configuration] window 1. Select the backup BIOS Configuration file stored on the remote PC. Then, click the [Upload] button. File transfer to the MMB begins. The following window appears when the file transfer is completed.
Page 367: Figure 10.4 [Backup/Restore Mmb Configuration] Window
CHAPTER 10 Backup and Restore 10.1 Backing Up and Restoring Configuration Information 10.1.2 Backing up and restoring MMB configuration information From the Backup/Restore MMB Configuration window, you can back up and restore MMB configuration information. The procedure is as follows. FIGURE 10.4 [Backup/Restore MMB Configuration] window Backing up MMB configuration information 1.
Page 368: Figure 11.1 [System Power Control] Window
Chapter System Startup/Shutdown and Power Control This section describes the startup, shutdown and the power control in PRIMEQUEST 2000 series. 11.1 Power On and Power Off the Whole System This section describes the power on and power off operations which are supported by the system.
Page 369: Table 11.1 Power On Method And Power On Unit
11.2.2 Partition Power on unit The units that can be powered on and the power on methods are given below. For details on the privileges of the partition power on operation, see ‘1.1 WEB-UI Menu List’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539).
Page 370: Table 11.2 Power On Method And Power On Unit
Does not have permission for any partition For the details on the user privileges of the MMB Web-UI menu, see ‘1.1 Menu list of Web-UI’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). 11.2.6 Partition Power on by MMB This section describes the procedure of powering on the partition by MMB.
Page 371: Figure 11.2 [Power Control] Window
CHAPTER 11 Chapter System Startup/Shutdown and Power Control 11.2 Partition Power on and Power off FIGURE 11.2 [Power Control] window “#” column has the partition number. For the details of [Power Control] window, see ‘1.3.1 [Power Control] window’ in “PRIMEQUEST 2000 series Tool Reference”...
Page 372: Figure 11.3 [Power Control] Window
FIGURE 11.3 [Power Control] Window For the details on the contents and setting items of the [Power Control] window, see ‘1.3.1 [Power Control] Window’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). 11.2.8 Checking the Partition Power status by using the MMB This section describes the procedure by which power status of partition is confirmed.
Page 373: Figure 11.4 [Information] Window
The power status of the partition is displayed in [Power Status]. For details on the contents and setting items of the [Information] window, see ‘1.3.9 [Partition#x] menu’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). Powering off a partition by using the MMB This section describes the powering off procedure using the [MMB Web-UI] window.
Page 374: Figure 11.5 [Power Control] Window
FIGURE 11.5 [Power Control] window The “#” column has the partition number. For details on the [Power Control] window, see ‘1.3.1 [Power Control] window’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). 3. Set the ‘Power Control’ of the partition number to be powered off to [Power Off], and click the [Apply] button.
Page 375: Table 11.5 Relationship Between Scheduled Operation And Partition Power Restoration Mode
When a scheduled operation is set for a partition set, power is turned off at the set time. A daily, weekly, monthly, specific date or a combination of these options can be set a schedule. For the details on schedule settings, see ‘1.3.2 [Schedule] menu’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539).
Page 376: Automatic Partition Restart Conditions
CHAPTER 11 Chapter System Startup/Shutdown and Power Control 11.4 Automatic Partition Restart Conditions Menu Item Scheduled Description operations Reset Not supported Resets any partition. This reset is not followed by a reboot of the operating system. Not supported Issues an NMI interrupt for any partition. Sadump Not supported Instructs sadump for a partition.
Page 377: Figure 11.6 [Asr (Automatic Server Restart) Control] Window
CHAPTER 11 Chapter System Startup/Shutdown and Power Control 11.4 Automatic Partition Restart Conditions FIGURE 11.6 [ASR (Automatic Server Restart) Control] window 2. Set the automatic restart conditions. The setting items of the [ASR Control] window are listed in the table below. TABLE 11.7 [ASR Control] window display / setting items Items Description...
Page 378: Table 11.8 Power Restoration Policy
For details on the operation of [ASR Control] window, see ‘1.3.9 [Partition#x] menu’ in “PRIMEQUEST 2000 series Tool Reference” (CA92344-0539). 11.5 Power Restoration In the PRIMEQUEST 2000 series, the system operations for power restoration can be set in the chassis unit. This can be set by MMB Web-UI. 11.5.1 Settings for Power Restoration When using a UPS, the following items can be set when a power failure is detected.
Page 379: Remote Shutdown (Windows)
CHAPTER 11 Chapter System Startup/Shutdown and Power Control 11.6 Remote shutdown (Windows) 11.6 Remote shutdown (Windows) Windows with versions of Windows XP onwards, comes with a ‘shutdown.exe’ command. This command can be used for remote shutdown from a management terminal. 11.6.1 Prerequisites for remote shutdown The following are the prerequisites for using the remote shutdown (Windows).
Page 380: Figure 11.7 Simplified Help For The Shutdown Command
CHAPTER 11 Chapter System Startup/Shutdown and Power Control 11.6 Remote shutdown (Windows) FIGURE 11.7 Simplified help for the shutdown command CA92344-0537-08...
Page 381: Table 12.1 Functions Provided By The Mmb Web-Ui
The PRIMEQUEST 2000 series unifies server management via the MMB Web-UI. The following lists the functions provided by the MMB Web-UI. For details on the functions, see the reference sections in the PRIMEQUEST 2000 Series Tool Reference (CA92344-0539). TABLE 12.1 Functions provided by the MMB Web-UI...
Page 382: Mmb Cli
For details on MMB command lines, see Chapter 2 MMB CLI (Command Line Interface) Operations in the PRIMEQUEST 2000 Series Tool Reference (CA92344-0539). For details on functions provided by the MMB CLI, see the reference sections in the PRIMEQUEST 2000 Series Tool Reference (CA92344-0539).
Page 383: Table 12.2 Functions Provided By The Mmb Cli
6 Setting of sadump environment 12.4 ServerView Suite You can use ServerView Suite to visually confirm the PRIMEQUEST 2000 series configuration and the status of each part. For details on how to operate ServerView, see the ServerView Suite ServerView Operations Manager Server Management.
Page 384: Chapter 13 Error Notification And Maintenance (Contents, Methods, And Procedures)
The MMB provides system maintenance functions through the [Maintenance] menu of the Web-UI. You can use the [Maintenance] menu to back up and restore system configuration information. For details on the [Maintenance] menu, see 1.6 [Maintenance] Menu in the PRIMEQUEST 2000 Series Tool Reference (CA92344-0539).
Page 385: Table 13.1 Maintenance Modes
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.1 Maintenance The following table lists the maintenance modes and their functions. Note that Operation mode is the normal operation mode and not a maintenance mode. TABLE 13.1 Maintenance modes Mode Meaning Operation...
Page 386: Maintenance Of The Pci_Box (Pexu)
REMCS Center via the Internet or P-P connection. REMCS Agent of the PRIMEQUEST 2000 series consists of the MMB firmware as well as SVS installed in each partition. As the REMCS linkage in the figure shows, the MMB firmware monitors the entire system for problems, and reports them to the REMCS Center when it detects them.
Page 387: Figure 13.1 Remcs Linkage
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.2 Troubleshooting FIGURE 13.1 REMCS linkage 13.2 Troubleshooting This section describes how to troubleshoot system problems. 13.2.1 Troubleshooting overview The following shows the basic procedure for troubleshooting. CA92344-0537-08...
Page 388: Figure 13.2 Troubleshooting Overview
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.2 Troubleshooting FIGURE 13.2 Troubleshooting overview If a problem occurs in this product, troubleshoot the problem according to the displayed message. If the error recurs, contact your sales representative or a field engineer. Before making contact, confirm the unit, source, part number, event ID, and description of the error as well as the model name and serial number shown on the label affixed to the main unit.
Page 389: Figure 13.3 Label Location
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.2 Troubleshooting FIGURE 13.3 Label location Description Model name Serial number 13.2.2 Items to confirm before contacting a sales representative Before contacting your sales representative, confirm the following details. Print the sheet in Appendix L Failure Report Sheet, and enter the necessary information.
Page 390: Figure 13.4 Alarm Led On The Front Panel Of The Device
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.2 Troubleshooting For a repair under warranty during the warranty period For a repair not under any support service contract after expiration of the warranty period Our authorized service engineer will repair the product on site. The service engineer will go to your premises on the next business day after the contact date.
Page 391: Figure 13.5 System Status Display In The Mmb Web-Ui Window
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.2 Troubleshooting FIGURE 13.5 System status display in the MMB Web-UI window Description Status in information area Displays the system status The MMB Web-UI window always displays the information area. [Status] in the information area displays the system status.
Page 392: Figure 13.6 Alarm E-Mail Settings Window
Problems related to system startup or drivers may occur. For details on these problems, see the PRIMEQUEST 2000 Series Message Reference (CA92344-0540). If the status is one of the MMB error or warning statuses listed in the following operation interrupt criteria, stop the system and contact a field engineer or your sales representative.
Page 393: Figure 13.7 System Status Display
The information will be needed when you contact a field engineer or your sales representative. For details on how to read system event log messages, see Chapter 1 Message Overview in the PRIMEQUEST 2000 Series Message Reference (CA92344-0540). CA92344-0537-08...
Page 394: Figure 13.8 System Event Log Display
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.2 Troubleshooting FIGURE 13.8 System event log display Finding out about a faulty partition Investigate the entire system partition configuration and the faulty partition in PRIMEQUEST 2400E3/2800E3/2400E2/2800E2/2400E/2800E. Select [Partition] – [Partition Configuration] in the [MMB] menu window. You can find out the status of each partition.
Page 395: Figure 13.10 [Partition Event Log] Window
Select [System] – [Partition Event Log] in the [MMB] menu window. On the [Partition Event Log] window, you can find out about problems in the partition from the displayed log. For details on how to read agent log messages, see PRIMEQUEST 2000 Series Message Reference (CA92344-0540).
Page 396: Mmb-Related Problems
13.2.8 MMB-related problems This section describes MMB-related problems and how to correct the problems. No connection to the PRIMEQUEST 2000 series server can be established using the Web-UI. Cause 1: The setting of the IP address, subnet mask, or gateway is wrong.
Page 397: Table 13.4 System Problems And Memory Dump Collection
This section provides notes on troubleshooting. In the PRIMEQUEST 2000 series, if you unplug all the AC power cables while the device is in standby mode, the system event log records AC Lost (Severity: Info). This is neither a problem nor a failure. It is a normal situation.
Page 398: Figure 13.11 [System Event Log] Window In Primequest 2400E3/2800E3/2400E2/2800E2/2400E/2800E
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.4 Collecting Maintenance Data FIGURE 13.11 [System Event Log] window in PRIMEQUEST 2400E3/2800E3/2400E2/2800E2/2400E/2800E FIGURE 13.12 [System Event log] window in PRIMEQUEST 2800B3/2800B2/2800B 2. Confirm the displayed contents. Click the [Download] button to download the event data stored in the SEL. Alternatively, click the [Filter] button to filter the events to display.
Page 399: Figure 13.13 [System Event Log Filtering Condition] Window In Primequest 2400E3/2800E3/2400E2/2800E2/2400E/2800E
Downloading the event data stored in the SEL A Fujitsu certified service engineer needs the event data stored in the SEL to analyze the system status. Therefore, we may ask you to download the event data and submit it to a Fujitsu certified service engineer. Procedure 1.
Page 400: Figure 13.14 [System Event Log Filtering Condition] Window In Primequest 2800B3/2800B2/2800B
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.4 Collecting Maintenance Data FIGURE 13.14 [System Event Log Filtering Condition] window in PRIMEQUEST 2800B3/2800B2/2800B 2. Specify the condition to filter events. Then, click the [Apply] button. The [System Event Log] window appears again. The window displays the events matching the specified conditions.
Page 401: Figure 13.15 [System Event Log (Detail)] Window
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.4 Collecting Maintenance Data Item Description The default is [All]. Sort by Date/Time Select ascending or descending order for displaying events by using the radio buttons. The default is [New event first]. Start Date/Time Select the first event or an event of the specified time by using the radio buttons.
Page 402: Table 13.6 Setting And Display Items In The [System Event Log (Detail)] Window
SSG and DSNAP are support tools for collecting the data necessary for investigation of software problems. If a problem occurs in your system, SSG and DSNAP enable your Fujitsu certified service engineer to correctly determine the system software configuration. This leads to a smooth investigation. (The engineer uses this information to determine how the system is configured and deployed.
Page 403: Table 13.7 Memory Dump Types And Default Value
After installing the operating system and applications for operations, make settings for acquiring memory dumps. Different information collected by a memory dump The PRIMEQUEST 2000 series enables you to acquire the following four types of memory dump. Each type of memory dump gathers different information. Complete memory dump A complete memory dump records all the physical memory contents at the time when the system stops.
Page 404 CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.4 Collecting Maintenance Data Memory dump type Memory dump file size Save method operation (max 8TB). *1 In a system using the Memory Mirror function, it is half the size of the mounted physical memory *2 Although you can change this setting to not overwrite the dump file, no new dump file would be created in such cases.
Page 405: Figure 13.16 [Startup And Recovery] Dialog Box
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.4 Collecting Maintenance Data FIGURE 13.16 [Startup and Recovery] dialog box 5. Specify the following values. Select the type of memory dump file from [Write debugging information]. Set the dump file storage location in [Dump file].
Page 406: Figure 13.17 [Advanced] Tab Of The Dialog Box
[NMI] for the target partition. For details on the procedure, see Chapter 1 MMB Web-UI (Web User Interface) Operations in the PRIMEQUEST 2000 Series Tool Reference (CA92344-0539). Configuring the paging file <For Windows Server 2012 or Windows Server 2012 R2>...
Page 407: Figure 13.18 [Virtual Memory] Dialog Box
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.4 Collecting Maintenance Data FIGURE 13.18 [Virtual Memory] dialog box 6. Uncheck [Automatically manage paging file size for all drives]. [Drive] specifies the drives on which paging files are created. The selected drive under [Drive] of [Paging file size for selected drive] is displayed.
Page 408: Figure 13.19 Advanced Options Dialog Box
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.4 Collecting Maintenance Data 12. Click the [OK] button to close the [System Properties] dialog box. 13. Restart the partition. After the partition restart, the settings take effect. <For Windows Server 2008 R2> Configure the paging file in the following procedure.
Page 409: Figure 13.20 [Virtual Memory] Dialog Box
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.4 Collecting Maintenance Data FIGURE 13.20 [Virtual Memory] dialog box 6. Specify the drive on which to create the paging file. Select the system installation drive in [Drive]. [Drive] in [Paging file size for selected drive] displays the selected drive. 7.
Page 410: Sadump
CHAPTER 13 Error Notification and Maintenance (Contents, Methods, and Procedures) 13.5 Configuring and Checking Log Information 13.4.5 sadump If a problem occurs in the partition which is operating on RHEL, memory dump is acquired as shown 13.4.4 Acquiring data for investigation (RHEL).
Page 411: Firmware Updates
Each firmware is managed as a total version integrating different versions. The firmware is updated from the MMB in batch (applying to all the firmware at all locations within the system). For details on firmware updates, see 1.6.1 [Firmware Update] menu in the PRIMEQUEST 2000 Series Tool Reference (CA92344-0539).
Page 412: Table A.1 Action
Appendix A Functions Provided by the PRIMEQUEST 2000 Series Appendix A Functions Provided by the PRIMEQUEST 2000 Series This appendix lists the functions provided by the PRIMEQUEST 2000 series. It also lists management network specifications. Function List The following lists the functions provided by the PRIMEQUEST 2000 series.
Page 413: Table A.3 Monitoring And Reporting Functions
Appendix A Functions Provided by the PRIMEQUEST 2000 Series operation Minor item Description Power recovery processing Power-on control when power is restored from AC Lost Boot control Boot device selection in Web-UI Diagnosis mode selection at boot Boot device selection by UEFI Boot Manager, boot...
Page 414: Table A.4 Maintenance Functions
Appendix A Functions Provided by the PRIMEQUEST 2000 Series operation Minor item Description Temperature display Eco status acquisition from higher-level software (SNMP) Log type Expand contents and enhance history information of MMB-collected log - System event log - Hardware and UEFI error log...
Page 415: Table A.5 Redundancy Functions
Appendix A Functions Provided by the PRIMEQUEST 2000 Series operation Minor item Description - System configuration information notification A.1.5 Redundancy functions TABLE A.5 Redundancy functions operation Minor item Description Network Management LAN Management LAN duplication switching duplication Power supply Dual power feed...
Page 416: Table A.8 System Information Display
Records such as MMB operating log and login history, etc. Support of TPM function Correspondence between Functions and Interfaces The following shows the correspondence between the functions provided by PRIMEQUEST 2000 series and interfaces. A.2.1 System information display TABLE A.8 System information display...
Page 417: Table A.11 Hardware Status Display
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.2.4 Hardware status display TABLE A.11 Hardware status display Function MMB CLI UEFI Web-UI LED status display Supported LED operation (on, clear, blinking) Supported PSU (power supply unit) power-on count Supported...
Page 418: Table A.14 Partition Operation
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.2.7 Partition operation TABLE A.14 Partition operation Function MMB CLI UEFI Web-UI Video redirection/ Virtual media Supported Console redirection Supported UEFI shell Supported A.2.8 Partition power control TABLE A.15 Partition power control...
Page 419: Table A.19 Maintenance
Maintenance wizard: Maintenance mode Supported setting and cancellation SB hot addition Supported IOU hot addition Supported Management Network Specifications The following lists the management network specifications of the PRIMEQUEST 2000 series. TABLE A.20 Management network specifications Component Communi Compon USER REMCS Partition...
Page 420: Table A.21 Management Network Specifications
Appendix A Functions Provided by the PRIMEQUEST 2000 Series Component Communi Compon USER REMCS Partition Protocol Port cation port port port LAN port (Port direction No.) Duplex Used Used Not used Not used http/https Change browser (TCP able 8081) SVOM...
Page 421: Figure B.1 Physical Mounting Locations In The Primequest 2400E3/2400E2
Appendix B Physical Mounting Locations and Port Numbers Appendix B Physical Mounting Locations and Port Numbers This appendix describes the physical mounting locations of components, and shows MMB and IOU port numbers. Physical Mounting Locations of Components This section describes the physical mounting locations of components. Note In PRIMEQUEST 2400E3/2400E2, total of SB and Memory Scale-up Board can be installed up to four boards.
Page 422: Figure B.2 Physical Mounting Locations In The Primequest 2800E3/2800E2
Appendix B Physical Mounting Locations and Port Numbers FIGURE B.2 Physical mounting locations in the PRIMEQUEST 2800E3/2800E2 FIGURE B.3 Physical mounting locations in the PRIMEQUEST 2800B3/2800B2 CA92344-0537-08...
Page 423: Figure B.4 Physical Mounting Locations In The Primequest 2400E
Appendix B Physical Mounting Locations and Port Numbers FIGURE B.4 Physical mounting locations in the PRIMEQUEST 2400E Explanation Front Rear FIGURE B.5 Physical mounting locations in the PRIMEQUEST 2800E Explanation Front Rear CA92344-0537-08...
Page 424: Figure B.6 Physical Mounting Locations In The Primequest 2800B
Appendix B Physical Mounting Locations and Port Numbers FIGURE B.6 Physical mounting locations in the PRIMEQUEST 2800B Explanation Front Rear FIGURE B.7 Physical mounting locations in the DU CA92344-0537-08...
Page 425: Figure B.8 Physical Mounting Locations In The Pci_Box
Appendix B Physical Mounting Locations and Port Numbers FIGURE B.8 Physical mounting locations in the PCI_Box Explanation Upper side Front Right side Rear Port Numbers This section shows the numbering policy of each MMB and IOU port. Remarks The character strings used in numbering are the port numbers as viewed from firmware. These port numbers differ from the character strings in the port identification printed, stamped, or otherwise marked on units.
Page 426: Figure B.10 Iou_1Gbe Port Numbers
Appendix B Physical Mounting Locations and Port Numbers FIGURE B.10 IOU_1GbE port numbers FIGURE B.11 IOU_10GbE port numbers CA92344-0537-08...
Page 427: Table C.1 External System Interfaces
Appendix C Lists of External Interfaces Physical Appendix C Lists of External Interfaces Physical This appendix describes the external interfaces of the PRIMEQUEST2000 series. List of External System Interfaces The following lists the external system interfaces. TABLE C.1 External system interfaces IO interface Mounting Number of...
Page 428: Table D.1 Physical Locations Of Sb Internal I/O Controllers And Bus Numbers
Mounting Locations and Slot Numbers This appendix shows the correspondence between the physical locations and BUS numbers of built-in I/O in the PRIMEQUEST 2000 series server. It also shows the correspondence between PCI slot mounting locations and slot numbers. Physical Locations and BUS Numbers of Internal I/O Controllers of the PRIMEQUEST 2000 Series The following table shows physical location and BUS numbers of SB internal I/O controllers.
Page 429 Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers Mounting location Slot number (decimal number) Board Slot PRIMEQUEST PRIMEQUEST PRIMEQUEST 2400E 2400E3/2400E2/ 2800B3/2800B2/2800B 2800E3/2800E2/2800E IOU#2 (*1) Port to 4132 4132 IOU#3 (*1) SB#3 Port to 4145...
Page 430 Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers Mounting location Slot number (decimal number) Board Slot PRIMEQUEST PRIMEQUEST PRIMEQUEST 2400E 2400E3/2400E2/ 2800B3/2800B2/2800B 2800E3/2800E2/2800E PCIC#3 PCIC#4 PCIC#5 PCIC#6 PCIC#7 PCIC#8 PCIC#9 PCIC#10 PCIC#11 PCI_Box#3...
Page 431: Appendix E Primequest 2000 Series Cabinets
Appendix E PRIMEQUEST 2000 Series Cabinets Appendix E PRIMEQUEST 2000 Series Cabinets For details on PRIMEQUEST 2000 series cabinets and components and PCI_Box cabinets and components, see Chapter 1 Installation Information in the PRIMEQUEST 2000 Series Hardware Installation Manual (CA92344-0535).
Page 432: Table F.1 Power Led, Alarm Led, And Location Led
Appendix F Status Checks with LEDs Appendix F Status Checks with LEDs This appendix describes the types of mounted LEDs for the PRIMEQUEST 2000 series. It also describes how to check the status with LEDs. F.1. LED Type The PRIMEQUEST 2000 series has Customer Self Service (CSS) LED, System Alarm LED, and Location LED on front side of the cabinet.
Page 433: Table F.4 Fan Led
Appendix F Status Checks with LEDs (*1) If Alarm LED is turning on orange, the FANM with the particular LED fails. Even though Alarm LED remains off, SEL may be displayed which indicates the FANM error due to detecting not enough fan rotation by preventive fan monitoring function.
Page 434: Table F.8 Memory Scale-Up Board Led
Appendix F Status Checks with LEDs TABLE F.8 MEMORY SCALE-UP BOARD LED LED type Color Function Power Green Indicates power state in a Memory Scale-up Board. Alarm Orange Indicates whether there is error or not in a Memory Scale-up Board. Location Blue Specifies a Memory Scale-up Board.
Page 435: Table F.14 Hdd/Ssd Led
Appendix F Status Checks with LEDs F.1.9 HDD/SSD The HDD or SSD comes equipped with the following LEDs. HDD or SSD in an SB and HDD or SSD in a DU have same LEDs. TABLE F.14 HDD/SSD LED LED type Color Function Note...
Page 436: Table F.19 Lan Led And Linkup Speed
Appendix F Status Checks with LEDs LED type Color Function Note Speed LAN. GbE LAN Green Indicates the Link status and Activity status of Mounted only on the Link/Act (*1) a GbE LAN. IOU_1GbE GbE LAN Green/Orange Indicates the communication speed of a GbE Mounted only on the Speed (*1) LAN.
Page 437: Table F.23 Pci_Box Status And Pci_Box Led Display
Appendix F Status Checks with LEDs LED type Color Function Location Blue Identifies a PCI_Box. Can be arbitrarily set to blink or turned off by the user. Indicates the component undergoing maintenance when Maintenance Wizard is running. TABLE F.23 PCI_Box status and PCI_Box LED display Status Power Alarm...
Page 438: Figure F.1 Led Mounting Locations On Components Equipped With Lan Ports
Appendix F Status Checks with LEDs TABLE F.28 IO_FAN status and LED display Status Alarm Error in IO_FAN LED Mounting Locations This section describes the physical LED mounting locations on each component. Components equipped with Power, Alarm, and Location LEDs have the LEDs mounted as follows. The order of mounted LEDs arranged from left to right is as follows: Power, Alarm, Location.
Page 439: Figure F.4 Du Led Mounting Locations
Appendix F Status Checks with LEDs The order of DU LEDs arranged as follows. FIGURE F.4 DU LED mounting locations The order of System LEDs arranged from the left or the top is as follows: Power, Alarm, CSS, Location, MMB_Ready. FIGURE F.5 System LED mounting locations CA92344-0537-08...
Page 440: Figure F.6 Pci_Box Led Mounting Locations
Appendix F Status Checks with LEDs The order of PCI_Box LEDs arranged from the left is as follows: IO_PSU, IO_FAN#0, IO_FAN#1, Power, Alarm, Location. FIGURE F.6 PCI_Box LED mounting locations CA92344-0537-08...
Page 441: Table F.29 Led List (1/3)
Appendix F Status Checks with LEDs LED list The following table lists the mounted LEDs for the PRIMEQUEST 2000 series. TABLE F.29 LED list (1/3) Component LED type Color Quantity Status Description Power/ Green/ PSU AC input off Alarm orange...
Page 442 Appendix F Status Checks with LEDs Identify Memory Scale-up Board CA92344-0537-08...
Page 443: Table F.30 Led List (2/3)
Appendix F Status Checks with LEDs TABLE F.30 LED list (2/3) Component LED type Color Quantity Status Description Power Green IOU power off IOU power on Alarm Orange IOU normal Error in IOU Location Blue On or Blinking Component location Link/Act Green Network not link...
Page 444: Table F.31 Led List (3/3)
Appendix F Status Checks with LEDs TABLE F.31 LED list (3/3) Component LED type Color Quantity Status Description System Green Power off in all partitions Power - Power on in all partitions - PSU on, 12V feed System Orange Alarm Error occurrence in cabinet System...
Page 445: Table F.32 Usable Pci_Box Number And Models
Appendix F Status Checks with LEDs Button and switch PRIMEQUEST 2000 series comes equipped with below buttons and switches. OPL Location button When you push the Location button of OPL, Location LED turns on. Pushing this button again, Location LED turns off.
Page 446: Table G.1 Numbers Of Sbs And Cpus Per Partition
Appendix G Component Mounting Conditions Appendix G Component Mounting Conditions This appendix describes the mounting conditions of components for the PRIMEQUEST 2000 series. This section describes the number of CPUs that can be mounted and the criteria for mixing different types of CPU.
Page 447: Table G.2 Relationship Between Dimm Size, Type And Mutual Operability (Within An Sb)
Appendix G Component Mounting Conditions DIMM mounting conditions and DIMM mixing criteria of SB and Memory Scale-up Board are the same. DIMM mounting conditions At least two DIMMs are required per CPU. Up to 24 DIMMs can be mounted per CPU. DIMMs must be mounted in the following units: two DIMMs when normal mode, four DIMMs when full mirror mode or partial mirror mode, and six DIMMs when spare mode.
Page 448: Table G.5 Relationship Between Dimm Size, Type And Mutual Operability (Within An Sb)
Appendix G Component Mounting Conditions DIMM criteria for PRIMEQUEST 2400E2/2800E2/2800B2. 8 GB and 16 GB RDIMMs can be mounted in a single SB or partition. 32 GB RDIMMs cannot be mixed with DIMMs of other type and other sizes in an SB or partition. 32 GB and 64 GB LRDIMMs cannot be mixed with DIMMs of other type and other sizes in an SB or partition.
Page 449: Table G.8 Relationship Between Dimm Size And Mutual Operability (Within An Sb)
Appendix G Component Mounting Conditions DIMM criteria for PRIMEQUEST 2400E/2800E/2800B. 8 GB and 16 GB RDIMMs can be mounted in a single SB or partition. 32 GB and 64 GB LRDIMMs cannot be mixed with DIMMs of other type and other sizes in an SB or partition.
Page 450: Table G.11 Dimm Mounting Order In Sb
Appendix G Component Mounting Conditions G.2.1 DIMM mounting order and DIMM mixed mounting condition The order of DIMM installation and the condition of DIMM mixed installation are shown below. However, if any of below condition is satisfied, see next page: The partition includes total four boards of SBs and Memory Scale-up Board.
Page 451: Table G.13 Dimm Mounting Order In Memory Scale-Up Board
Appendix G Component Mounting Conditions TABLE G.13 DIMM mounting order in Memory Scale-up Board Mounting order DIMM 0A0 0A3 0B0 0B3 0C0 0C3 0D0 0D3 1A0 1A3 1B0 1B3 1C0 1C3 1D0 0D3 Slot# 0A1 0A4 0B1 0B4 0C1 0C4 0D1 0D4 1A1 1A4 1B1 1B4 1C1 1C4 1D1 0D4 0A2 0A5 0B2 0B5 0C2 0C5 0D2 0D5 1A2 1A5 1B2 1B5 1C2 1C5 1D2 0D5 Normal Full or...
Page 452: Table G.15 Dimm Mounting Order In Special Case In Sb
Appendix G Component Mounting Conditions The order of DIMM installation and the condition of DIMM mixed installation where any of below condition is satisfied are shown below: The partition includes four total four boards of SBs and Memory Scale-up Board. Dynamic Reconfiguration is enabled.
Page 453: Table G.17 Dimm Mounting Order In Special Case In Memory Scale-Up Board
Appendix G Component Mounting Conditions TABLE G.17 DIMM mounting order in special case in Memory Scale-up Board Mounting order DIMM 0A0 0A3 0B0 0B3 0C0 0C3 0D0 0D3 1A0 1A3 1B0 1B3 1C0 1C3 1D0 0D3 Slot# 0A1 0A4 0B1 0B4 0C1 0C4 0D1 0D4 1A1 1A4 1B1 1B4 1C1 1C4 1D1 0D4 0A2 0A5 0B2 0B5 0C2 0C5 0D2 0D5 1A2 1A5 1B2 1B5 1C2 1C5 1D2 0D5 Normal Full Mirror,...
Page 454: Table G.19 Available Internal I/O Ports And The Quantities
Appendix G Component Mounting Conditions Configuration when using 100 V PSU PRIMEQUEST 2000 series supports 100 V power supply in case of only PSU_S. Since power efficiency decrease when using 100V PSU, maximum quantity of component may decrease in a system.
Page 455 Appendix G Component Mounting Conditions For the WOL (Wake on LAN) support conditions of operating systems, see the respective operating system manuals and restrictions. For remote power control in an operating system that does not support WOL, perform operations from the MMB Web-UI. CA92344-0537-08...
Page 456: Appendix H Tree Structure Of The Mib Provided With The Primequest 2000 Series
MMB firmware returns MIB information according to definition of MIB file. Note The PRIMEQUEST 2000 series uses the SNMP function of the MMB to recognize changes in the partition state when each partition is started or stopped. For an MIB request received at this time from an external manager (e.g., Systemwalker Centric Manager), the MMB temporarily returns an error or time-out.
Page 457: Figure H.1 Mib Tree Structure
Appendix H Tree Structure of the MIB Provided with the PRIMEQUEST 2000 Series FIGURE H.1 MIB tree structure MIB File Contents The following table lists the contents of MIB files. MIB files can be obtained by “/SVSLocalTools/Japanese/PSA/” in DVD-ROM disk supplied with the product.
Page 458: Appendix I Windows Shutdown Settings
Appendix I Windows Shutdown Settings Appendix I Windows Shutdown Settings This appendix describes how to set (arbitrarily) Windows to shut down. Shutdown From MMB Web-UI Windows shutdown from the MMB Web-UI requires ServerView Agent. For details on how to set ServerView Agent, contact the distributor where you purchased your product or your sales representative.
Page 459: Table J.1 Files And Tools To Prepare
Systemwalker Centric Manager is an application for intensive system and network management according to the life cycle of system deployment. This section describes preparation for configuration of monitoring by the PRIMEQUEST 2000 series server in linkage with Systemwalker Centric Manager (referred to below as Systemwalker).
Page 460: J.2.2 Snmp Trap Linkage
Converted message text is displayed on the Systemwalker console. Remarks To ensure that converted text can be identified as a message from the PRIMEQUEST 2000 series server, the keyword [PRIMEQUEST] is embedded in the text.
Page 461: J.2.3 Event Monitoring Linkage
This section provides an overview of GUI linkage and describes the registration procedure. Overview of GUI linkage To permit access to the URL of the MMB login window of the PRIMEQUEST 2000 series from Systemwalker, register it from the [Operation] menu.
Page 462 Appendix J Systemwalker Centric Manager Linkage Systemwalker works together with ServerView to transmit the monitoring results from ServerView to the integrated management server of Systemwalker as well as start the ServerView console from Systemwalker. For details on the linkage procedure, see the ServerView Operations Manager User’s Guide. CA92344-0537-08...
Page 463: Appendix K Software
Appendix K Software Appendix K Software For details on bundled software and drivers supplied with the PRIMEQUEST 2000 series hardware, see Chapter 3 Software Configuration in the PRIMEQUEST 2000 Series General Description (CA92344-0534). CA92344-0537-08...
Page 464: Appendix L Failure Report Sheet
Appendix L Failure Report Sheet Appendix L Failure Report Sheet This appendix includes the failure report sheet. Use this sheet to report a failure. Failure Report Sheet □ PRIMEQUEST ( Model name □ Red Hat Enterprise Linux (Version: □ Windows Sever (Version: □...
Page 465: Table M.1 Information Of Pci Express Card (Primequest2400E3/2800E3/2800B3)
Appendix M Information of PCI Express card Appendix M Information of PCI Express card This appendix includes the information of PCI Express card. For components which cannot be identified by ‘Vendor ID’ and ‘Device ID’, see also ‘Subsystem ID’. TABLE M.1 Information of PCI Express card (PRIMEQUEST2400E3/2800E3/2800B3) Name Vendor ID Device ID...
Page 466 Appendix M Information of PCI Express card TABLE N.1 Information of PCI Express card (PRIMEQUEST2400E/2800E/2800B) Name Vendor ID Device ID Subsystem SAS Card 1000 005B 11E4 Dual Channel 6Gbps SAS Card 1000 0072 Dual Channel 6Gbps SAS RAID Card 1000 005B 9291 Single Channel 8Gbps Fibre Channel Card...

Fujitsu PRIMEQUEST 2000 Series Administration Manual

CHAPTER 1 Network Environment Setup and Tool Installation

CHAPTER 2 Operating System Installation

CHAPTER 3 Component Configuration and Replacement (Add, Remove)

CHAPTER 4 Hot Maintenance in Red hat Enterprise Linux 6

CHAPTER 5 Hot Maintenance in Red hat Enterprise Linux 7

CHAPTER 6 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11

CHAPTER 7 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 12

Quick Links

Troubleshooting

Related Manuals for Fujitsu PRIMEQUEST 2000 Series

Summary of Contents for Fujitsu PRIMEQUEST 2000 Series