Page 1 FUJITSU Server PRIMEQUEST 2000 Series Administration Manual C122-E175-02EN...
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 (C122-E171XA).
Page 3: Revision History
Preface Revision History Edition Date Revised location (type) (*1) Description 2014-02-18 2014-04-10 Updated Network Environment CHAPTER 1 Setup and Tool Installation Updated Component CHAPTER 3 Configuration and Replacement (Add, Remove) Updated PCI Card Hot CHAPTER 4 Maintenance in Red Hat Enterprise Linux 6 CHAPTER 5 Added this chapter.
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 C122-E175-02EN...
Page 6 Preface Warning label location (the main cabinet left) Warning label location (PCI_Box) C122-E175-02EN...
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 C122-H007EN Hardware Installation Manual requirements for the PRIMEQUEST 2000 series. PRIMEQUEST 2000 Series Describes how to set up the PRIMEQUEST 2000 series C122-E174EN Installation Manual server, including the steps for installation preparation, initialization, and software installation.
Page 10 None Refer to the manual from the second DVD for ServerView Suite which you can purchase optionally or from the following URL: The Fujitsu Technology Solutions manuals server http://manuals.ts.fujitsu.com/ MegaRAID SAS Device Provides technical information on using array controllers. None...
Page 11: Command Syntax
Font or symbols Meaning italics Title of a manual that you should refer to See the PRIMEQUEST 2000 Series Installation Manual (C122-E174EN). Window names as well as the names of Click the [OK] button. buttons, tabs, and drop-down menus in windows are enclosed in brackets.
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 FUJITSU LIMITED C122-E175-02EN...
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.2.1 Preparing for SB hot add ............................... 61 4.2.2 Confirming the status of SB before SB hot add........................62 4.2.3 DR operation in SB hot add ..............................62 4.2.4 How to deal with when timeout occurs while OS is processing SB hot add ............... 63 4.2.5 Operation after SB hot add ..............................
Page 15 Preface 6.1.2 Hot replacement of failed HDD/SSD with RAID 1, RAID 1E, RAID 5, RAID 6, or RAID 10 configuration ...... 154 Preventive replacement of HDD/SSD with Hardware RAID configuration ................155 6.2.1 Preventive replacement of failed HDD/SSD with RAID0 configuration ................155 6.2.2 Preventive replacement of failed HDD/SSD with RAID 1, RAID 1E, RAID 5, RAID 6, or RAID 10 configuration ..
Page 16 List of log information ..............................237 11.6 Firmware Updates ..................................238 11.6.1 Notes on updating firmware............................238 Appendix A Functions Provided by the PRIMEQUEST 2000 Series ....................... 239 Function List ....................................239 A.1.1 Action ....................................239 A.1.2 Operation ....................................239 A.1.3...
Page 17 Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers ....253 Physical Locations and BUS Numbers of Internal I/O Controllers of the PRIMEQUEST 2000 Series ....... 253 Correspondence between PCI Slot Mounting Locations and Slot Numbers ................ 253 Appendix E PRIMEQUEST 2000 Series Cabinets ............................
Page 18 Preface K.3.1 How to confirm firmware version for FC card made by Qlogic ..................294 K.3.2 How to confirm firmware version for FC card made by Emulex ................... 297 Appendix L Software ....................................302 Appendix M Failure Report Sheet ................................303 Failure Report Sheet .................................
Page 19 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 20 Preface FIGURE 5.3 Single NIC interface and bonding configuration interface..................... 145 FIGURE 5.4 Single NIC interface and bonding configuration interface..................... 149 FIGURE 8.1 [Backup BIOS Configuration] window ........................... 192 FIGURE 8.2 [Restore BIOS Configuration] window ........................... 193 FIGURE 8.3 [Restore BIOS Configuration] window (partition selection) ................... 193 FIGURE 8.4 [Backup/Restore MMB Configuration] window ......................
Page 21 FIGURE K.17 [Controller Management] window ..........................293 FIGURE K.18 [View Controller Properties] window ........................... 293 FIGURE K.19 FUJITSU logo window ..............................294 FIGURE K.20 Confirmation of UEFI driver version and firmware version ..................294 FIGURE K.21 Boot Manager front page (1) ............................295 FIGURE K.22 Boot Manager front page (2) ............................
Page 22 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 23 Preface TABLE 9.4 Privilege for power on and power off (continued) ......................197 TABLE 9.5 Relationship between scheduled operation and partition power restoration mode ............202 TABLE 9.6 Power on/off ..................................202 TABLE 9.7 [ASR Control] window display / setting items ........................204 TABLE 9.8 Power Restoration Policy ..............................
Page 24 Preface TABLE F.16 LAN LEDs ..................................260 TABLE F.17 LAN LED and Linkup Speed ............................260 TABLE F.18 OPL LED ..................................261 TABLE F.19 System status and LED display ............................. 261 TABLE F.20 PCI_Box LED ................................. 261 TABLE F.21 PCI_Box status and PCI_Box LED display ........................261 TABLE F.22 PCI Express card status and LED display ........................
Page 25: 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 (C122-B022EN).
Page 26: Figure 1.2 External Network Functions
Connect a LAN cable for User Port and a LAN cable for REMCS Port to different HUB each other or divide them by using VLAN. The following diagram shows the functions of external networks for the PRIMEQUEST 2000 series. FIGURE 1.2 External network functions...
Page 27: 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 28: 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 29: 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 30: 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 31: How To Configure The Management Lan
CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN 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 netck ifconfig netck stat show user_list help show snmp sys_location show snmp sys_contact...
Page 32 CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN Display/Setting item Description The possible settings for the respective ports depend on the MMB hardware configuration. Network Protocols: Network protocol settings HTTP, HTTPS, telnet, SSH, Specifies whether to enable or disable a protocol, the port number, and the SNMP Timeout time.
Page 33: Redundant Configuration Of The Management Lan
CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN Display/Setting item Description Remote Server Management: User settings for remote control of the MMB via RMCP Use the [Edit User] button to select the user to be edited. The default settings for all users is [No Access] and [Disable].
Page 34 CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN Because the MMB cannot recognize errors occurring in the path for accessing the MMB user port from the management LAN, it is unable to recover from them by switching the active MMB. Therefore, two user ports of the management LAN are mounted on the MMB.
Page 35: 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 36: Redundancy Of The Production Lan
(Web User Interface) Operations in the PRIMEQUEST 2000 Series Tool Reference (C122-E110EN). 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 37: 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 38: Figure 1.5 Connection Configuration For Video Redirection
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Note If you cannot access to DNS server in the terminal for video redirection, do not set up the address of DNS server. Virtual media for multiple partitions cannot be available in the same user terminal. TABLE 1.8 List of video redirection function Function Description...
Page 39: Figure 1.6 Operating Sequence Of Video Redirection
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.6 Operating sequence of video redirection In the diagram, (1) to (5) indicates the following operations. (1) Log in to the server from the terminal. (2) Display the window, and start video redirection.
Page 40 CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Menu Bar Description Pause Redirection Perform pause of [Video redirection] window. Resume Redirection Release pause of [Video redirection] window. Refresh Video Refresh [Video redirection] window. Turn ON Host Display Video Show video operation on host monitor.
Page 41 CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Menu Bar Description French(Belgium) Set to ‘French (Belgium)’. Dutch(Belgium) Set to ‘French.’ Russian(Russia) Set to ‘Russian’. Japanese(QWERTY) Set to ‘Japanese (QWERTY)’. Japanese(Hiragana) Set to ‘Japanese (Hiragana)’. Japanese(Katakana) Set to ‘Japanese (Katakana)’.
Page 42: 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 Server Information Display information of server. (*1) Set mouse mode to ‘Hide mouse mode’ when operate LSI WebBIOS since action of cursor in LSI WebBIOS is adjusted to actual action of your mouse cursor.
Page 43: 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 Display of video redirection window remains black or ‘No Signal’. Error dialog of video redirection appears and any operation cannot be performed. Window of video redirection is disconnected unintentionally. Below description is how to connect video redirection.
Page 44: Figure 1.12 Popup For [Allow Virtual Console] 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 45: 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 1. Login to MMB CLI and specify partition to which you intend to connect. If the message which confirms whether you connects or not appears, input ‘y’. FIGURE 1.17 Example of setting partition #3 (1) 2.
Page 46: 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 47: 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 48: 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 49: 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 50: 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/ C122-E175-02EN...
Page 51: 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. C122-E175-02EN...
Page 52: 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 the PPAR partition. 3.1.1 Partition Configuration (PPAR) The partition is set in MMB Web-UI.
Page 53: Figure 3.1 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 54: Figure 3.2 Conceptual Diagram Of The Partitioning Function (Primequest 2800E)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.1 Partition Configuration PRIMEQUEST 2800E For PRIMEQUEST2800E, 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 55: Setting Procedure Of Partition In Mmb Web-Ui
For details, see '1.3.3 [Partition Configuration] window' in "PRIMEQUEST 2000 series Tools Reference”. 6. Set the various types of modes. For details, see the [Mode] window of the '1.3.8 [Partition #x] Menu' in "PRIMEQUEST 2000 series Tools Reference”. 7. Power on the partition.
Page 56: Figure 3.3 Sb Hotadd
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration FIGURE 3.3 SB hotadd Description Dynamic addition of SB (operated by the operator) FIGURE 3.4 SB Hot remove (Disconnecting a faulty SB) 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...
Page 57: Figure 3.5 Iou Hot Add
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration FIGURE 3.5 IOU Hot add Description Dynamic addition of IOU (operation by operator) FIGURE 3.6 IOU hot remove (removal of failed IOU) Description Fault suspected Dynamic disconnection of IOU (operator operation) Replacement Rules of DR The DR is set in the UEFI.
Page 58: Table 3.3 Dr Supported List
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration TABLE 3.3 DR supported list Component Function Windows Server VMware Red Hat SUSE ESXi 5 or later Enterprise Enterprise Windows 2008 R2 or later Linux RHEL6.4 Linux 11 or later Hot add Not supported...
Page 59 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration In case of hot remove of the Reserved SB that belongs to a partition, the Reserved SB setting is not canceled. DR operation (SB hot add, SB hot remove, IOU hot add, IOU hot remove, hot add of PCI Express card or hot remove of PCI Express card) can't be performed in parallel at the same time in the chassis.
Page 60: Reserved Sb
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration In SB hot add, SB hot remove, IOU hot add or IOU hot remove operation, multiple SBs or multiple IOUs cannot be specified at the same time. If you perform hot add or hotremove of multiple SBs or multiple IOUs, perform the DR operation of each device one by one.
Page 61: Table 3.4 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" (C122-E174) Reserved SB definition The definition of the Reserved SB is automatically canceled after the Reserved SB operates.
Page 62 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Source SB Memory Operation SB DIMM configuration for Reserved Memory Operation Mode after Mode Reserved SB switching Normal or Mirror or Spare (*2) Mirror Spare Normal Normal Mirror Mirror Spare Spare...
Page 63: Figure 3.7 Example 1-A. Example Where Two Sbs Are Set As Reserved Sbs In Two Partitions (When Sb #0 And Sb #1 Have Simultaneously Failed)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration 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 64: Figure 3.8 Example 1-B.example When One Sb Is Set As The Reserved Sb In Two Partitions (Sb #0 And Sb #2 Have Simultaneously Failed)
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration FIGURE 3.8 Example 1-b.Example when one SB is set as the Reserved SB in two partitions (SB #0 and SB #2 have simultaneously failed) Description No switching to the Reserved SB FIGURE 3.22 Example 2.
Page 65: Figure 3.10 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 Example 4. where Reserved SBs (#1, #2, #3) of Partition #0 belong to other partitions FIGURE 3.10 In example 5, since the is no SB in a powered off partition , among SB #1, SB #2, and SB #3 in the powered-on partitions, SB #3 having the highest SB number is selected as the switching destination.
Page 66: Figure 3.12 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.12 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 67 CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration *1: SB which is incorporated in a partition, and is also set as the Reserved SB in another partition. When the partition that incorporates the Reserved SB is powered off, the corresponding SB will be disconnected.
Page 68: Memory Operation Mode
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration When using the Trusted Platform Module (TPM) function, the Reserved SB function cannot be used. Do not set a Reserved SB for a partition where the HDD/SSD on the SB is used as a boot disk or data disk.
Page 69: Memory Mirror
3.2.4 Memory Mirror In the PRIMEQUEST 2000 series, the Mirror Mode and the Partial Mirror Mode are supported as the memory mirror, in which the function with the CPU is used. Full Mirror/Partial Mirror can be selected from the MMB Web-UI.
Page 70: Figure 3.14 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 Since the memory mirror group having a failure suspected DIMM operates in the Non Mirror, the status would be Partial Memory Mirror. Since half the number of DIMMs having a failure suspected DIMM in a Partial Mirrored memory group will not be incorporated, the memory capacity seen from the operating system will be maintained.
Page 71: Figure 3.16 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.16 memory (memory capacity maintenance mode) Status when an error has occurred in the FIGURE 3.17 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 72: Hardware Raid
For details on the Server View RAID, see ‘Server View RAID Management User Manual’. 3.2.7 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 73: 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.10 Component name AC power off AC power on AC power on AC power on (Device stop)
Page 74: 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” (C122-E174) and stop the relevant partition. Procedure after replacement See ‘7.1.1 Power on of partitions’...
Page 75 4. Power off the partition. For details on powering off, see ‘7.1.2 Powering off Partitions’ in the “PRIMEQUEST 2000 series Installation Manual” (C122-E174). 5. Replace the faulty PCI Express card. 6. Power on the partition.
Page 76: Expansion Of Components
Remarks For details on each command, see ‘PCIe SSD-xx ioMemory VSL x.x.x User Guide for Linux’. xx is the capacity. x.x.x. is the version number. http://manuals.ts.fujitsu.com/ 8. Create a swap entry for the replaced PCI Express card. Remarks A partition must be created before creating a swap entry.
Page 77: Procedure Of Expansion In Hot Maintenance
Download of drivers and the bundled software of the PRIMEQUEST 2000 series. http://support.ts.fujitsu.com/ Remarks In the PRIMEQUEST 2000 series, the customer will change a part of the firmware. 3.4.1 Procedure of expansion in hot maintenance This section describes the procedures before and after expansion in hot maintenance.
Page 78: Procedure Of Expansion In Cold Maintenance
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.4 Expansion of components “Stop the relevant partition referring to ‘7.1.2 Powering off Partitions’ in the “PRIMEQUEST 2000 series Installation Manual” (C122-E174). Procedure after expansion Start the relevant partition referring to‘7.1.1 Powering on Partitions’ in the “PRIMEQUEST 2000 series Installation Manual”...
Page 79: Process After Switching To The Reserved Sb And Automatic Partition Reboot
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot Process after switching to the Reserved SB and Automatic Partition Reboot This section describes the processes after switching to the Reserved SB, and the partition has automatically rebooted (example, status check and re-configuration).
Page 80: 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 Click the radio button of the source Reserved SB; then click the [Apply] button. The source Reserved SB will be disconnected from the partition and will be in the free status. Click [Partition] - [Reserved SB Configuration].
Page 81: Replacing The Home Sb No
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.6 Replacing the Home SB No. Partition #P: SB #a -> Partition #P: SB#c Partition #Q: SB #b -> Partition #Q: SB#b Partition #R: SB #c -> Partition #R: ---- The status transition of each partition is shown from (1) to (4) of the ‘Partition status transition’ in the table below.
Page 82: Table 3.19 Example Of Home Sb No. Replacement
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.6 Replacing the Home SB No. Home SB. A number will be allocated for an SB not configured with LSB of P0/P1. An example can be seen below. TABLE 3.19 Example of Home SB No. replacement Physical SB Physical SB0 Physical SB1...
Page 83: Chapter 4 Pci Card Hot Maintenance In Red Hat Enterprise Linux 6
(DR)’. For details on the MMB Web-UI/CLI, see respective chapters in “PRIMEQUEST 2000 series Tool Reference” (C122-E177). For details on the OS CLI, see ’5.1 DR command’ in “PRIMEQUEST 2000 series Tool Reference” (C122- E177). 4.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 84: Dr Command Package Install/ Uninstall
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 85: Hot Add Of Sb
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB FJSVdr-util/RPMS/FJSVdr-util-RHEL6-x.x.x-x.noarch.rpm FJSVdr-util/SRPMS/FJSVdr-util-RHEL6-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-RHEL6-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 86: Confirming The Status Of Sb Before Sb Hot Add
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB b. Check if the points/restrictions are clear. For detail, see ‘3.2.1 Dynamic Reconfiguration (DR)’ 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.
Page 87: How To Deal With When Timeout Occurs 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 88: Operation After Sb Hot Add
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB MemTotal: 65271964 kB In case that the number of CPU or the size of memory keeps increasing: It is expected that cause of the delay is the load of the partition. The process of SB hot add can be completed sooner by reducing the load of the partition.
Page 89: Hot Replacement Of Iou
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU # /usr/sbin/srvmagt restart If CPUs and memories of SB that is added by hot add of SB is used for KVM, below steps are required. 1.
Page 90: Preparation For Iou Hot Replacement
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU PCI address (bus address) of PCI Express card on IOU may change after hot replacement of IOU. This change may be occurred for replacing, expanding or removing PCI Express card. 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 91 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU (rev ca) 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)
Page 92: Table 4.1 Correspondence Between Bus Addresses And Interface Names
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU Note You will use the bus address obtained here in steps 2 and procedure after IOU replacement. Record the bus address so that you can reference it later. Next, check the PCI slot number for this PCI bus address.
Page 93: Table 4.2 Hardware Address Description Examples
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU TABLE 4.2 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:8c:00.0 PCI#0...
Page 94 [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 95: Dr Operation Of Iou Hot Replacement
4.3 Hot replacement of IOU *1: Write down the DM-MP display contents at the session disconnection. Example of DM-MP display before disconnecting path # /sbin/multipath -ll mpath1 (36000b5d0006a0000006a104900000000) dm-0 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...
Page 96: Operation After Iou Hot Replacement
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU 9. Execute “hotadd” command on MMB console. Example: Adding IOU 3 to partition 1 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)
Page 97 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU replaced) on the IOU confirmed in step 1. Example: eth0 # /sbin/ifconfig eth0 down 3. Confirm the correspondence between the interface names before and after the NIC replacement. According to the table with the interface information about before and after the NIC replacement in steps 2 of 4.3.1 Preparation for IOU hot replacement...
Page 98 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU bonding, the file contents are partly different, but the lines to be set are the same. Example: DEVICE=eth0 NM_CONTROLLED=no BOOTPROTO=static HWADDR=2c:d4:44:f1:44:d2 BROADCAST=192.168.16.255 IPADDR=192.168.16.1 NETMASK=255.255.255.0 NETWORK=192.168.16.0 ONBOOT=yes...
Page 99: Hot Add Of Iou
[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 100: Preparation For Iou Hot Add
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.4 Hot add of IOU 4.4.1 Preparation for IOU hot add The description of the flow of preparations is given below. 1. Arrange for the IOU for addition. 2.
Page 101 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.4 Hot add of IOU Note If SVAgent is installed in the partition, perform below command with root privilege. # /usr/sbin/srvmagt restart 1. Check the resource that was added. Execute the /opt/FJSVdr-util/sbin/dr show IOU command in the operating system shell.
Page 102: Iou Hot Remove
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove Setting of NIC (including onboard NIC) Perform step 4 or later in ‘4.7.4 Network card addition procedure’. Common operation of all PCI Express cards after IOU hot replacement Execute pciinfo command on MMB CLI.
Page 103 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove 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. Device 8748 (rev ca) 0000:85:08.0 PCI bridge: PLX Technology, Inc.
Page 104: Table 4.4 Correspondence Between Bus Addresses And Interface Names
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove # ls -l /sys/class/net/*/device | grep "0000:89:00.0" lrwxrwxrwx. 1 root root 0 Aug 27 16:06 2013 /sys/class/net/eth0/ device ¥ -> ../../../ 0000:89:00.0 The ¥ at the end of a line indicates that there is no line feed. In this case, eth0 is the interface name which is correspondent to PCI bus address “0000:89:00.0”.
Page 105 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove 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 106: Table 4.5 Hardware Address Description Examples
CHAPTER 4 PCI Card 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...
Page 107 [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 108: 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 109: Hot Replacement Of Pci Express Cards
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards NIC on the IOU (including onboard NIC) 1. Restart the application which is stop at preparing for IOU hot replacement FC Card 1.
Page 110 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 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 111 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards This operation concurrently 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 112 CHAPTER 4 PCI Card 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 113 CHAPTER 4 PCI Card 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 114 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards Note Do NOT click [Next] until replacing the PCIC. 8. After replacing the particular PCIC, mount cables other than LAN cables. Note In GLS configuration with NIC switching way, mount also LAN cables.
Page 115 CHAPTER 4 PCI Card 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 116: Fc Card (Fibre Channel Card) Replacement Procedure
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 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 117 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 118: Network Card Replacement Procedure
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards Check the FC cable connection status. Confirm the Storage FC settings. Confirm that the settings that conform to the actual connection format (Fabric connection or Arbitrated Loop connection) were made.
Page 119: Figure 4.2 Single Nic Interface And Bonding Configuration Interface
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards The 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 ‘PRIMECLUSTER Global Link Service Configuration and Administration Guide Redundant Line Control Function for Linux’...
Page 120: Table 4.6 Correspondence Between Bus Addresses And Interface Names
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards ‘D.2 Correspondence between PCI Slot Mounting With the PCI Express slot number confirmed here, see Locations and Slot Numbers ’PCI Express slot to check the mounting location, and see also ‘B.1 Physical Mounting Locations of...
Page 121: Table 4.7 Hardware Address Description Examples
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards grep eth0 /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="00:0e:0c:70:c3:38", 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 122 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards For the partition with Dynamic Reconfiguration utility installed Execute /opt/FJSVdr-util/sbin/dr rm pcie<slot number> command on the shell of OS. The PCI Express card is disabled and has become to be ready for removal. The LED goes out. Example: Making the PCI Express slot with PCI Express slot number 20 power off # /opt/FJSVdr-util/sbin/dr rm pcie20 This operation concurrently removes the device associated with the relevant adapter from the system.
Page 123: Table 4.8 Example Of Interface Information About The Replacement Nic
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards [Example of descriptions in the file after editing] (In the example, eth0 was deleted, and eth1 is commented out.) # PCI device 0x****:0x**** (e1000) # SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥...
Page 124: Table 4.9 Example Of Entered Values Corresponding To The Interface Names Before And After Nic Replacement
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards d. In the table created in step 11, enter values corresponding to the interface names before and after the NIC replacement. TABLE 4.9 Example of entered values corresponding to the interface names before and after NIC replacement Interface name After replacement...
Page 125: Table 4.10 Confirmation Of Interface Names
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards Note Confirm that each specified interface name is the same as before the NIC replacement. TABLE 4.10 Confirmation of interface names Interface name Hardware address Bus address...
Page 126: Hot Replacement 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 127 [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 128: Hot Addition Of Pci Express Cards
4.7 Hot Addition of PCI Express cards ¥_ 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 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 129 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards Checking the power status of a PCI Express slot See ‘Checking the power status of a PCI Express slot’ in “4.6.2 PCI Express card replacement procedure in detail”.
Page 130 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 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] C122-E175-02EN...
Page 131 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 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 132 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards Note Ask the administrator of your system to power on the PCI Express slot. 10. The window updating status appears. 11. Check the status of added PCIC and click [Next]. C122-E175-02EN...
Page 133: Fc Card (Fibre Channel Card) Addition Procedure
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 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]. 4.7.3 FC card (Fibre Channel card) addition procedure The descriptions in this section assume that an FC card is being added.
Page 134: Network Card Addition Procedure
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards FC card addition procedure The procedure for adding new FC cards and peripherals is as follows. 1. Confirm the slot number of the PCI slot by using the following procedure. See ‘Confirming the slot number of a PCI Express slot’...
Page 135: Figure 4.4 Single Nic Interface And Bonding Configuration Interface
CHAPTER 4 PCI Card 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 136 CHAPTER 4 PCI Card 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 137: Removing Pci Express Cards
CHAPTER 4 PCI Card 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 138: Common Removal Procedures For All Pci Express Cards
CHAPTER 4 PCI Card 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 139: Network Card Removal Procedure
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards 3. Power off the PCI Express slot. See ‘Powering on and off PCI Express slots’ in “4.6.2 PCI Express card replacement procedure in detail”.
Page 140 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards Components’ to identify the physical mounting location corresponding to the PCI slot number. You can confirm that it matches the mounting location of the operational target NIC. 2.
Page 141: Hot Removal Procedure For Iscsi (Nic)
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards 8. Edit the settings in the udev function rule file. The entries of the interface assigned to the removed NIC still remain in the udev function rule file, /etc/udev/ rules.d/70-persistent-net.rules.
Page 142 [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 143 CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards mpath1 (36000b5d0006a0000006a104900000000) dm-0 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...
Page 144: Chapter 5 Pci Card Hot Maintenance In Suse Linux Enterprise Server 11
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 Hot Replacement of PCI Express Cards CHAPTER 5 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 145 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 Hot Replacement of PCI Express Cards # /sbin/lsmod | grep pciehp Pciehp 37458 0 2. If it is not installed, incorporate the PCI Hot Plug driver module into the system by executing the modprobe command.
Page 146 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 Hot Replacement of PCI Express Cards 1. Start [Maintenance Wizard] menu by MMB Web-UI and display [Maintenance Wizard] view. 2. Select [Replace Unit] and click [Next]. 3. Select [PCI_Box(PCIC)], click [Next]. 4.
Page 147 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 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] C122-E175-02EN...
Page 148 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 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 149 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 Hot Replacement of PCI Express Cards Note Ask the administrator of your system to power on the PCI Express slot. 10. The window updating status appears. 11. Check the status of replaced PCIC and click [Next]. C122-E175-02EN...
Page 150: Fc Card (Fibre Channel Card) Replacement Procedure
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 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 151 LPe1250-F8 8Gb PCIe Fibre Channel ¥ 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 ¥ C122-E175-02EN...
Page 152 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 Hot Replacement of PCI Express Cards 0000 PQ: 1 ANSI: 5 ...(*3) 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 153: Network Card Replacement Procedure
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 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 154: Table 5.1 Correspondence Between Bus Addresses And Interface Names
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.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 155: Table 5.2 Hardware Address Description Examples
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.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 156 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.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 157: Table 5.3 Example Of Interface Information About The Replacement Nic
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.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 158: Table 5.4 Example Of Entered Values Corresponding To The Interface Names Before And After Nic Replacement
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.1 Hot Replacement of PCI Express Cards 14. Deactivate each newly created interface. The interfaces created for the replacement NIC may be active because power is on to the PCI Express slot.
Page 159: Table 5.5 Confirmation Of Interface Names
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.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 160: Hot Replacement Procedure For Iscsi (Nic)
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.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 161 [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 162: 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 163: Pci Express Card Addition Procedure In Detail
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 Hot Addition of PCI Express cards 5.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 164 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 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 165 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 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 166 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 Hot Addition of PCI Express cards Note Do NOT click [Next] until adding the PCIC. 8. After adding the particular PCIC, mount cables other than LAN cables. Note In GLS configuration with NIC switching way, mount also LAN cables.
Page 167 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 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 168: Fc Card (Fibre Channel Card) Addition Procedure
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 Hot Addition of PCI Express cards 5.2.3 FC card (Fibre Channel card) addition procedure The descriptions in this section assume that an FC card is being added. Notes The FC card used for SAN boot does not support hot plugging.
Page 169: Network Card Addition Procedure
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 Hot Addition of PCI Express cards 8. 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 170 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 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...
Page 171 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.2 Hot Addition of PCI Express cards 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 172: Removing Pci Express Cards
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.3 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 173: Fc Card (Fibre Channel Card) Removal Procedure
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.3 Removing PCI Express cards Checking the power status of a PCI Express slot See ‘Checking the power status of a PCI Express slot’ in “5.1.2 PCI Express card replacement procedure in detail”.
Page 174 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.3 Removing PCI Express cards When removing multiple NICs, be sure to remove them one by one. If you do this with multiple cards at the same time, the correct settings may not be made. 1.
Page 175 CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.3 Removing PCI Express cards # /sbin/vconfig rem ethX.Y [For the interface under bonding] If the bonding device is operating in mode 1, use the following steps for safety purposes on the SLAVE interface to be removed to exclude it from operation.
Page 176: Hot Removal Procedure For Iscsi (Nic)
CHAPTER 5 PCI Card Hot Maintenance in SUSE Linux Enterprise Server 11 5.3 Removing PCI Express cards The ¥ at the end of a line indicates that there is no line feed. Do this editing for all the interfaces confirmed in step 3. 10.
Page 177 [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 178: Chapter 6 Replacement Of Hdd/Ssd
Confirm whether [Status] of replaced HDD or SSD has been already ‘Operational’ by [System] – [DU] – [DUx] window of MMB Web-UI. For details on [SBx] window, see ‘1.2.15 [DU] menu’ in “PRIMEQUEST 2000 series Tool Reference” (C122-E177EN). 6.1.2 Hot replacement of failed HDD/SSD with RAID 1, RAID 1E, RAID 5,...
Page 179: 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” (C122-E177EN). For replacement of a HDD or SSD included in a DU Confirm whether [Status] of replaced HDD or SSD has been already ‘Operational’...
Page 180: Preventive Replacement Of Failed Hdd/Ssd With Raid 1, Raid 1E, Raid 5, Raid 6, Or Raid 10 Configuration
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” (C122-E177EN). 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 181: Replacement Of Hdd/Ssd In Case Hot Replacement Cannot Be Performed
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” (C122-E177EN). For replacement of a HDD or SSD included in a DU Confirm whether [Status] of replaced HDD or SSD has been already ‘Operational’...
Page 182 CHAPTER 6 Replacement of HDD/SSD 6.3 Replacement of HDD/SSD in case hot replacement cannot be performed 5. Restore the data for backup. C122-E175-02EN...
Page 183: Chapter 7 Pci Express Card Hot Maintenance In Windows
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.1 Overview of Hot Maintenance CHAPTER 7 PCI Express card Hot Maintenance in Windows This chapter describes the hot plugging procedure for PCI Express cards in Windows. Hot plugging is supported only in Windows Server 2008 R2/ Windows Server 2012/ Windows Server 2012 R2. This procedure is for the PRIMEQUEST 2400E/2800E/2800B.
Page 184: Common Hot Plugging Procedure For Pci Express Cards
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.2 Common Hot Plugging Procedure for PCI Express cards 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. Addition procedure 1.
Page 185 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 186 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 187 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 replacement of a PCI card at PCIC#1 mounted in PCI_Box#0.
Page 188 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.2 Common Hot Plugging Procedure for PCI Express cards 5. Check button of target PCIC number for replacing, and click [Next] button. 6. Check [Hot Partition Maintenance(Target unit in a running partition.)] button, and click [Next] button. C122-E175-02EN...
Page 189 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.2 Common Hot Plugging Procedure for PCI Express cards 7. It will be Maintenance mode (Information zone: gray background), and instruction pages to remove target PCI card will be opened. Take off all cables such as LAN cable and FC cable connected the particular PCIC and replace PCI card with opening this page.
Page 190 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.2 Common Hot Plugging Procedure for PCI Express cards 9. Status updating menu will be opened. 10. Confirm status of target replaced PCI card, and click [Next] button. C122-E175-02EN...
Page 191 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.2 Common Hot Plugging Procedure for PCI Express cards 11. Confirm Maintenance Mode is released (information zone: non-gray background), and click [OK] button. 5. 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 192: Addition Procedure
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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. 7.2.2 Addition procedure 1.
Page 193 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 addition of a PCI card at PCIC#1 mounted in PCI_Box#0. 5.
Page 194 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 add target PCI card will be opened.
Page 195 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.2 Common Hot Plugging Procedure for PCI Express cards Note Don’t click [Next] Button before adding PCI card. 8. Add target PCI card and click [Next] button. 9. Status updating menu will be opened. C122-E175-02EN...
Page 196 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.2 Common Hot Plugging Procedure for PCI Express cards 10. Confirm status of target added PCI card, and click [Next] button. 11. Confirm Maintenance Mode is released. (information zone: non-gray background), and click [OK] button.
Page 197: About Removal
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.3 NIC Hot Plugging 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. Note As the follow, right-click target device in Device Manager, if there are [Enable] in displayed menu, check [Enable].
Page 198 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.3 NIC Hot Plugging 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 199 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 ‘7.2.1 Replacement procedure’ in ‘7.2 Common Hot Plugging Procedure for PCI Express cards’.
Page 200 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 201: Hot Plugging A Non-Redundant Nic
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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. 7.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 202: Hot Plugging An Fc Card Incorporated With The Eternus Multipath Driver
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.4 FC Card Hot Plugging In case of using SVagent, “Source:SVagent, ID: 25004 Error massage” is logged in SEL when replacing, it is no problem. 7.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 203 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.4 FC Card Hot Plugging Confirm firmware version of target device. Select the device name of target FC card in left pane, and see [Port Information] in right pane. The firmware version is written at “Boot Version:” and “Firmware Version” in [Port Attributes]. Close OneCommand Manager.
Page 204 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.4 FC Card Hot Plugging b. Select “e1: FC Adapter Information” in [FC Adapter Information]. c. Select the device of the same type of target FC card in [Adapter Information]. C122-E175-02EN...
Page 205 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.4 FC Card Hot Plugging d. Confirm “PCI Bus Number” of FC card, and look for the device which has same bus number you confirmed in step 1. Confirm WWN and port number of target device. WWN is the information described as “WWPN:”...
Page 206 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.4 FC Card Hot Plugging Confirm firmware version of target device. QConverge Console GUI, and select device name of target FC card in left pane, and see [Port Info]. The firmware version is the information described as “BIOS Version:” in [Port Attribute Name]. Close QConverge Console CLI/GUI.
Page 207 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.4 FC Card Hot Plugging 4. Confirm target FC card by using Device Manager. Confirm FC card with step 2-a at ‘7.2.1 Replacement procedure’ in ‘7.2 Common Hot Plugging Procedure for PCI Express cards’.
Page 208: Fc Card Addition Procedure
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.5 Hot Replacement Procedure for iSCSI 10. Confirm replaced FC card by using Device Manager. Open Device Manager, and confirm that the target device is recognized correctly. Note As the follow, right-click target device in Device Manager, if there are [Enable] in displayed menu, check [Enable].
Page 209: Confirming The Incorporation Of A Card With Mpd
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.5 Hot Replacement Procedure for iSCSI 7.5.1 Confirming the incorporation of a card with MPD This section describes the procedure for confirming that a card has been incorporated with MPD. 1. Confirm physical location, segment number and bus number of target NIC. Confirm the physical location, segment number and bus number with step 1 at 7.2.1 Replacement procedure...
Page 210 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 211 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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 212 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.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). C122-E175-02EN...
Page 213: Disconnecting Mpd
CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.5 Hot Replacement Procedure for iSCSI 7.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 7.5.1 Confirming the incorporation of a card with MPD.
Page 214 CHAPTER 7 PCI Express card Hot Maintenance in Windows 7.5 Hot Replacement Procedure for iSCSI 6. Replace NIC by using MMB Maintenance Wizard. Replace NIC with step 4 at 7.2.1 Replacement procedure 7.2 Common Hot Plugging Procedure for PCI Express cards.
Page 215: Chapter 8 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 216: Figure 8.1 [Backup Bios Configuration] Window
CHAPTER 8 Backup and Restore 8.1 Backing Up and Restoring Configuration Information FIGURE 8.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 217: Backing Up And Restoring Mmb Configuration Information
CHAPTER 8 Backup and Restore 8.1 Backing Up and Restoring Configuration Information FIGURE 8.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 218: Figure 8.4 [Backup/Restore Mmb Configuration] Window
CHAPTER 8 Backup and Restore 8.1 Backing Up and Restoring Configuration Information FIGURE 8.4 [Backup/Restore MMB Configuration] window Backing up MMB configuration information 1. Click the [Backup] button. The browser dialog box for selecting the save destination appears. 2. Select the save destination path. Then, click the [OK] button. Download of the file begins.
Page 219: Figure 9.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. 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 220: Partition Power On Unit
9.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” (C122-E177).
Page 221: Table 9.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” (C122-E177). 9.2.6 Partition Power on by MMB This section describes the procedure of powering on the partition by MMB.
Page 222: Controlling Partition Startup By Using The Mmb
CHAPTER 9 Chapter System Startup/Shutdown and Power Control 9.2 Partition Power on and Power off FIGURE 9.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 223: Figure 9.3 [Power Control] Window
FIGURE 9.3 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” (C122-E177). 9.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 224: Figure 9.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.8 [Partition#x] menu’ in “PRIMEQUEST 2000 series Tool Reference” (C122-E177). Powering off a partition by using the MMB This section describes the powering off procedure using the [MMB Web-UI] window.
Page 225: Figure 9.5 [Power Control] Window
FIGURE 9.5 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” (C122-E177). 3. Set the ‘Power Control’ of the partition number to be powered off to [Power Off], and click the [Apply] button.
Page 226: Power Off A Partition By Scheduled Operation
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” (C122-E177).
Page 227: Automatic Partition Restart Conditions
CHAPTER 9 Chapter System Startup/Shutdown and Power Control 9.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 228: Figure 9.6 [Asr (Automatic Server Restart) Control] Window
CHAPTER 9 Chapter System Startup/Shutdown and Power Control 9.4 Automatic Partition Restart Conditions FIGURE 9.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. [ASR Control] window display / setting items TABLE 9.7 Items...
Page 229: Table 9.8 Power Restoration Policy
For details on the operation of [ASR Control] window, see ‘1.3.7 [Partition#x] menu’ in “PRIMEQUEST 2000 series Tool Reference” (C122-E177). 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. 9.5.1 Settings for Power Restoration When using a UPS, the following items can be set when a power failure is detected.
Page 230: Remote Shutdown (Windows)
CHAPTER 9 Chapter System Startup/Shutdown and Power Control 9.6 Remote shutdown (Windows) 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. 9.6.1 Prerequisites for remote shutdown The following are the prerequisites for using the remote shutdown (Windows).
Page 231: Figure 9.7 Simplified Help For The Shutdown Command
CHAPTER 9 Chapter System Startup/Shutdown and Power Control 9.6 Remote shutdown (Windows) Simplified help for the shutdown command Figure 9.7 C122-E175-02EN...
Page 232: Chapter 10 Configuration And Status Checking (Contents, Methods, And Procedures)
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 (C122-E177EN). TABLE 10.1 Functions provided by the MMB Web-UI...
Page 233: Mmb Cli
For details on MMB command lines, see Chapter 2 MMB CLI (Command Line Interface) Operations in the PRIMEQUEST 2000 Series Tool Reference (C122-E177EN). For details on functions provided by the MMB CLI, see the reference sections in the PRIMEQUEST 2000 Series Tool Reference (C122-E177EN).
Page 234: Serverview Suite
6 Setting of sadump environment 10.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 235: Chapter 11 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 (C122-E177EN).
Page 236: Maintenance Of The Mmb
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.1 Maintenance TABLE 11.1 Maintenance modes Mode Meaning Operation Normal operation [Normal operation] Hot System Maintenance For maintenance work performed while the system [Active for work (system)] power is on Hot Partition Maintenance For maintenance work performed while the target [Active for work (partition)]...
Page 237: Maintenance Policy/Preventive Maintenance
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 238: Troubleshooting
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.2 Troubleshooting FIGURE 11.1 REMCS linkage 11.2 Troubleshooting This section describes how to troubleshoot system problems. 11.2.1 Troubleshooting overview The following shows the basic procedure for troubleshooting. C122-E175-02EN...
Page 239: Figure 11.2 Troubleshooting Overview
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.2 Troubleshooting FIGURE 11.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 240: Items To Confirm Before Contacting A Sales Representative
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.2 Troubleshooting FIGURE 11.3 Label location Description Model name Serial number 11.2.2 Items to confirm before contacting a sales representative Before contacting your sales representative, confirm the following details. Print the sheet in Appendix M Failure Report Sheet, and enter the necessary information.
Page 241: Finding Out About Abnormal Conditions
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.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 242: Figure 11.5 System Status Display In The Mmb Web-Ui Window
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.2 Troubleshooting FIGURE 11.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 243: Investigating Abnormal Conditions
Problems related to system startup or drivers may occur. For details on these problems, see the PRIMEQUEST 2000 Series Message Reference (C122-E178EN). 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 244: Figure 11.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 (C122-E178EN). C122-E175-02EN...
Page 245: Figure 11.8 System Event Log Display
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.2 Troubleshooting FIGURE 11.8 System event log display Finding out about a faulty partition Investigate the entire system partition configuration and the faulty partition in PRIMEQUEST 2400E and 2800E. Select [Partition] - [Partition Configuration] in the [MMB] menu window. You can find out the status of each partition.
Page 246: Checking Into Errors In Detail
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 (C122- E178EN).
Page 247: Mmb-Related Problems
11.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 248: Notes On Troubleshooting
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 249: Figure 11.11 [System Event Log] Window In Primequest 2400E And 2800E
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.4 Collecting Maintenance Data FIGURE 11.11 [System Event Log] window in PRIMEQUEST 2400E and 2800E FIGURE 11.12 [System Event log] window in PRIMEQUEST 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 250: Figure 11.13 [System Event Log Filtering Condition] Window In Primequest 2400E And 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 251: Figure 11.14 [System Event Log Filtering Condition] Window In Primequest 2800B
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.4 Collecting Maintenance Data FIGURE 11.14 [System Event Log Filtering Condition] window in PRIMEQUEST 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 252: Figure 11.15 [System Event Log (Detail)] Window
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.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 253: Collecting Data For Investigation (Windows)
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 254: Setting Up The Dump Environment (Windows)
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 255 CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.4 Collecting Maintenance Data Memory dump type Memory dump file size Minimum memory dump 32bit windows: 128 KB Create new file 64bit windows: 256 KB Automatic memory dump Depends on memory space during system Overwrite (*2) operation (max 8TB).
Page 256: Figure 11.16 [Startup And Recovery] Dialog Box
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.4 Collecting Maintenance Data FIGURE 11.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 257: Figure 11.17 [Advanced] Tab Of The Dialog Box
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.4 Collecting Maintenance Data For details on the procedure, see Chapter 1 MMB Web-UI (Web User Interface) Operations in the PRIMEQUEST 2000 Series Tool Reference (C122-E177EN). Configuring the paging file <For Windows Server 2012 or Windows Server 2012 R2>...
Page 258: Figure 11.18 [Virtual Memory] Dialog Box
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.4 Collecting Maintenance Data FIGURE 11.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 259: Figure 11.19 Advanced Options Dialog Box
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.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 260: Acquiring Data For Investigation (Rhel)
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.4 Collecting Maintenance Data FIGURE 11.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 261: Sadump
CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures) 11.5 Configuring and Checking Log Information 11.4.5 sadump If a problem occurs in the partition which is operating on RHEL, memory dump is acquired as shown 11.4.4 Acquiring data for investigation (RHEL).
Page 262: 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 (C122-E177EN).
Page 263: A.1 Function List
Operation 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 264: Table A.3 Monitoring And Reporting Functions
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.1.3 Monitoring and reporting functions 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...
Page 265: A.1.4 Maintenance
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.1.4 Maintenance operation Minor item Description (SNMP) Log type Expand contents and enhance history information of MMB-collected log - System event log - Hardware and UEFI error log - Power control and factor information...
Page 266: A.1.5 Redundancy Functions
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.1.7 Security functions 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 Dual power feed monitoring...
Page 267: A.2 Correspondence Between Functions And Interfaces
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.2.4 Hardware status display 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 268: A.2.6 Partition Configuration And Operation Setting
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.2.7 Partition operation Function MMB CLI UEFI Web-UI PSU (power supply unit) power-on count Supported and status display System power consumption display Supported FAN status monitoring and FAN speed Supported display...
Page 269: A.2.8 Partition Power Control
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.2.11 Server management network settings A.2.8 Partition power control TABLE A.15 Partition power control Function MMB CLI UEFI Web-UI Power-on Supported Supported Power-off (shutdown) Supported Supported Reset Supported Supported Supported Supported...
Page 270: A.2.12 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 271: Table A.21 Management Network Specifications
Appendix A Functions Provided by the PRIMEQUEST 2000 Series Management Network Specifications Component Communi Compon USER REMCS Partition Protocol Port cation port port port LAN port (Port direction No.) Duplex RMCP (UDP623 TABLE A.21 Management network specifications Component Communi Compon...
Page 272: Appendix B Physical Mounting Locations And Port Numbers
Appendix B Physical Mounting Locations and Port Numbers Physical Mounting Locations of Components 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.
Page 273: Figure B.2 Physical Mounting Locations In The Primequest 2800E/2800B
Appendix B Physical Mounting Locations and Port Numbers Physical Mounting Locations of Components FIGURE B.2 Physical mounting locations in the PRIMEQUEST 2800E/2800B Explanation Front Rear FIGURE B.3 Physical mounting locations in the DU C122-E175-02EN...
Page 274: Port Numbers
Appendix B Physical Mounting Locations and Port Numbers Port Numbers FIGURE B.4 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.
Page 275: Figure B.6 Iou_1Gbe Port Numbers
Appendix B Physical Mounting Locations and Port Numbers Port Numbers FIGURE B.6 IOU_1GbE port numbers FIGURE B.7 IOU_10GbE port numbers C122-E175-02EN...
Page 276: Appendix C Lists Of External Interfaces Physical
Appendix C Lists of External Interfaces Physical List of External MMB Interfaces 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...
Page 277: Appendix D Physical Locations And Bus Numbers Of Built-In I/O, And Pci Slot Mounting Locations And Slot 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 278: Table D.2 Correspondence Between Pci Slot Mounting Locations And Slot Numbers
Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers Correspondence between PCI Slot Mounting Locations and Slot Numbers Mounting location Slot number (decimal number) Board Slot PRIMEQUEST PRIMEQUEST PRIMEQUEST 2400E 2800E 2800B Port to 4132...
Page 279 Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers Correspondence between PCI Slot Mounting Locations and Slot Numbers Mounting location Slot number (decimal number) Board Slot PRIMEQUEST PRIMEQUEST PRIMEQUEST 2400E 2800E 2800B PCIC#9 PCIC#10...
Page 280: Appendix E Primequest 2000 Series Cabinets
Correspondence between PCI Slot Mounting Locations and Slot Numbers 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 (C122- H004EN).
Page 281: Appendix F Status Checks With Leds
F.1. LED Type 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 282: Fanu
Appendix F Status Checks with LEDs F.1. LED Type (*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 283: Pci Express Slot Of Iou
Appendix F Status Checks with LEDs F.1. LED Type TABLE F.8 IOU LED LED type Color Function Power Green Indicates power state in an IOU. Alarm Orange Indicates whether there is error or not in an IOU. Location Blue Specifies an IOU. Can be arbitrarily set to blink or turned off by the user.
Page 284: Mmb
Appendix F Status Checks with LEDs F.1. LED Type HDD/SSD status HDD/SSD Access HDD/SSD Alarm Note Rebuilding array Blinking Blinking periodically When using SAS RAID card. with 1 Hz F.1.9 MMB The MMB comes equipped with the Active LED, Ready LED and Location LED. The Active LED indicates the active MMB, and the Ready LED indicates the MMB firmware status.
Page 285: Opl
Appendix F Status Checks with LEDs F.1. LED Type F.1.11 OPL The OPL comes equipped with an LED indicating the status of entire system, the MMB Ready LED, and the System Alarm LED. From the OPL LED display, you can check the power status of the entire device, check for any problem, and check the MMB firmware status.
Page 286: Io_Psu
Appendix F Status Checks with LEDs LED Mounting Locations F.1.14 IO_PSU The IO_PSU comes equipped with the following LEDs. TABLE F.23 IO_PSU LED LED type Color Function Note Green Indicates whether there is AC input to the IO_PSU control individual PSU. Green Indicates the on/off status of each IO_PSU.
Page 287: Figure F.2 Mounting Locations Of Psu And Fanu
Appendix F Status Checks with LEDs LED Mounting Locations LEDs The order of PSU and FANU LEDs arranged from the left or the top is as follows: FANM#0 Alarm, Power, and FANM#1 Alarm. FIGURE F.2 Mounting locations of PSU and FANU The order of MMB LEDs arranged from the left or the top is as follows: Ready, Alarm, Active, and Location.
Page 288: Led List
Appendix F Status Checks with LEDs LED list LED list The following table lists the mounted LEDs for the PRIMEQUEST 2000 series. TABLE F.27 LED list (1/3) Component LED type Color Quantity Status Description Power/ Green/ PSU AC input off...
Page 289: Table F.28 Led List (2/3)
Appendix F Status Checks with LEDs LED list TABLE F.28 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...
Page 290: Table F.29 Led List (3/3)
Appendix F Status Checks with LEDs LED list TABLE F.29 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...
Page 291: Button And Switch
Appendix F Status Checks with LEDs Button and switch 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 292: Appendix G Component Mounting Conditions
DIMM 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. CPU mounting criteria SB with one CPU is allowed in only single SB partition.
Page 293: Table G.3 Relationship Between Dimm Size And Mutual Operability (Within An Sb)
Appendix G Component Mounting Conditions DIMM PCI address SB Number DIMM increment unit mode (CPU number) 1CPU/1SB 2CPU/1SB Partition 2SB (4CPU) 3SB (6CPU) 4SB (8CPU) Segment 1SB (1CPU) (*1) 1SB (2CPU) 2SB (4CPU) 3SB (6CPU) 4SB (8CPU) Enable 1SB (1CPU) (*1) 1SB (2CPU) 2SB (4CPU) 3SB (6CPU)
Page 294: Table G.6 Dimm Mounting Order And Dimm Mixed Mounting Condition In Each Configuration
Appendix G Component Mounting Conditions DIMM DIMM mounting order and DIMM mixed mounting condition The order of DIMM installation and the condition of DIMM mixed installation are shown below. In tables of DIMM mounting order, DIMMs are installed in order from one with small number. In tables of DIMM mixed mounting condition, the same symbol indicates the same DIMM.
Page 295: Table G.7 Dimm Mounting Order At 1Cpu/1Sb (*1)
Appendix G Component Mounting Conditions DIMM TABLE G.7 DIMM mounting order at 1CPU/1SB (*1) CPU#0 DIMM Slot# Normal (Perfor mance) Full or Partial Mirror Spare (*1) See ‘TABLE G.11 DIMM mounting order at 1CPU/1SB when a Partition includes 8 sockets with PCI Address Mode = Segment Mode, or when DR is enabled in a Partition’...
Page 296: Table G.9 Dimm Mixed Mounting Condition At 1Cpu/1Sb (*1)
Appendix G Component Mounting Conditions DIMM TABLE G.9 DIMM mixed mounting condition at 1CPU/1SB (*1) CPU#0 DIMM Slot# □ □ ○ ○ △ △ ☆ ☆ Normal □ □ ○ ○ △ △ ☆ ☆ (Perfor mance) □ □ ○ ○...
Page 297: Table G.10 Dimm Mixed Mounting Condition At 2Cpu/1Sb (*1)
Appendix G Component Mounting Conditions DIMM TABLE G.13 DIMM mixed mounting condition at 1CPU/1SB when a Partition includes 8 sockets with PCI Address Mode = Segment Mode, or when DR is enabled in a Partition’ when a Partition includes 4SBs with PCI Address Mode = Segment Mode, or DR is enabled in a Partition.
Page 298: Table G.11 Dimm Mounting Order At 1Cpu/1Sb When A Partition Includes 8 Sockets With Pci Address Mode = Segment Mode, Or When Dr Is Enabled In A Partition
Appendix G Component Mounting Conditions DIMM TABLE G.11 DIMM mounting order at 1CPU/1SB when a Partition includes 8 sockets with PCI Address Mode = Segment Mode, or when DR is enabled in a Partition CPU#0 DIMM Slot# Normal (Perfor mance) Full or Partial Mirror...
Page 299: Table G.13 Dimm Mixed Mounting Condition At 1Cpu/1Sb When A Partition Includes 8 Sockets With Pci Address Mode
Appendix G Component Mounting Conditions DIMM TABLE G.13 DIMM mixed mounting condition at 1CPU/1SB when a Partition includes 8 sockets with PCI Address Mode = Segment Mode, or when DR is enabled in a Partition CPU#0 DIMM Slot# □ □ ○...
Page 300: Configuration When Using 100 V Psu
NIC (Network Interface Card) 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 301 Appendix G Component Mounting Conditions NIC (Network Interface Card) 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.
Page 302: Appendix H Tree Structure Of The Mib Provided With The Primequest 2000 Series
You can also acquire the standard MIB information from the MMB. 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 303: Mib File Contents
Appendix H Tree Structure of the MIB Provided with the PRIMEQUEST 2000 Series MIB File Contents FIGURE H.1 MIB tree structure MIB File Contents The following table lists the contents of MIB files. TABLE H.1 MIB file contents MIB file...
Page 304: Appendix I Windows Shutdown Settings
Appendix I Windows Shutdown Settings Shutdown From MMB Web-UI 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 305: Appendix J Systemwalker Centric Manager Linkage
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 306: 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 307: 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 308 Appendix J Systemwalker Centric Manager Linkage Configuring 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. C122-E175-02EN...
Page 309: Appendix K How To Confirm Firmware Of Sas Raid Controller Card
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version of SAS RAID controller card Appendix K How to Confirm Firmware of SAS RAID Controller Card This section explains how to confirm the firmware of I/O device. How to confirm firmware version of SAS RAID controller card You can confirm firmware version of SAS RAID controller card by WebBIOS and ServerView RAID.
Page 310: Figure K.2 Boot Manager Front Page (2)
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version of SAS RAID controller card FIGURE K.2 Boot Manager front page (2) 3. Select [EFI Internal Shell] and press [Enter] key. UEFI Shell starts up. FIGURE K.3 Boot Manager menu 4.
Page 311: Figure K.4 Driver List
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version of SAS RAID controller card FIGURE K.4 Driver list For details on UEFI operation, see “PRIMEQUEST 2000 series User Interface Operating Instructions” (C122-E176EN) and “PRIMEQUEST 2000 series Tool Reference” (C122-E177EN). Note If driver list does not fall within window, input ‘drivers -b’.
Page 312: Figure K.6 Dh Command Of Uefi Shell
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version of SAS RAID controller card FIGURE K.6 dh command of UEFI Shell 8. Execute the drvcfg -s XX YY command. Specify the following for [XX] and [YY]. XX: UEFI driver number confirmed in step 2 YY: Controller number confirmed in step 3 Shell>...
Page 313: Figure K.8 [Adapter Selection] Window Of Webbios (1)
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version of SAS RAID controller card FIGURE K.8 [Adapter Selection] window of WebBIOS (1) 11. Select relevant RAID controller by [Adapter No.] radio button and click [Start] button. FIGURE K.9 [Adapter Selection] window of WebBIOS (2) 12.
Page 314: How To Confirm Firmware Version Of Sas Card
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version of SAS card FIGURE K.11 [Controller Properties] window of WebBIOS If multiple MegaRAID SAS RAID controller is mounted, click [Controller Selection] in [HOME] window. Go back to step 11 and check firmware version of remaining MegaRAID SAS RAID controller by taking same steps.
Page 315: Figure K.13 Menu Window
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version of SAS card FIGURE K.13 Menu window 2. Select [LSI SAS2 MPT Controller SAS2008] from [Device List] in [Device Manager] window. FIGURE K.14 Device List in [Device Manager] window Note If [LSI SAS2 MPT Controller SAS2008] is not shown, firmware version is below value: Firmware version: 05.00.13.00...
Page 316: Figure K.15 Efi Driver Version In [Lsi Sas2 Mpt Controller Configuration]
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version of SAS card FIGURE K.15 EFI driver version in [LSI SAS2 MPT Controller Configuration] 4. After confirming version, select [LSI SAS2 MPT Controller HII Configuration Application] and press [Enter] key.
Page 317: How To Confirm Firmware Version And Uefi Driver Version Of Fc Card
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version and UEFI driver version of FC card FIGURE K.17 [Controller Management] window 7. Check firmware version in [View Controller Properties] window. FIGURE K.18 [View Controller Properties] window Note Press [Esc] key sometimes and go back to top menu.
Page 318: K.3.1 How To Confirm Firmware Version For Fc Card Made By Qlogic
Confirming UEFI driver version and firmware version 1. Select [Force boot into EFI Boot Manager] by [Boot Selection] in [Power Control] window of MMB Web-UI. Partition is powered on and logo of FUJITSU appears. Note For a FC card made by Qlogic, you can confirm the firmware version only when a partition starts up.
Page 319: Figure K.21 Boot Manager Front Page (1)
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version and UEFI driver version of FC card FIGURE K.21 Boot Manager front page (1) Confirming UEFI driver version 1. Select [Boot Manager] and press [Enter] key. FIGURE K.22 Boot Manager front page (2) 2.
Page 320: Figure K.23 Boot Manager Menu
Shell> drivers 4. List of driver appears. FIGURE K.24 UEFI Shell For details on UEFI operation, see “PRIMEQUEST 2000 series User Interface Operating Instructions” (C122-E176EN) and “PRIMEQUEST 2000 series Tool Reference” (C122-E177EN). Note If driver list does not fall within window, input ‘drivers -b’. Driver list is shown by a page.
Page 321: K.3.2 How To Confirm Firmware Version For Fc Card Made By Emulex
K.3.2 How to confirm firmware version for FC card made by Emulex Displaying Device Manager 1. Select [Force boot into EFI Boot Manager] by [Boot Selection] in [Power Control] window of MMB Web-UI. Partition is powered on and logo of FUJITSU appears. C122-E175-02EN...
Page 322: Figure K.27 Boot Manager Front Page (1)
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version and UEFI driver version of FC card FIGURE K.27 Boot Manager front page (1) 2. Select [Device Manager] and press [Enter] key. FIGURE K.28 Boot Manager front page (2) 3.
Page 323: Figure K.29 [Device Manager] Window
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version and UEFI driver version of FC card FIGURE K.29 [Device Manager] window 2. [Emulex Configuration Utility] window appears. Select [Emulex Configuration Setup Utility] and press [Enter] key.
Page 324: Figure K.31 [Adapter Selection] Window (Hba List)
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version and UEFI driver version of FC card FIGURE K.31 [Adapter Selection] window (HBA list) 2. [Emulex Adapter Configuration Main Menu] window appears. FIGURE K.32 [Emulex Adapter Configuration Main Menu] window Confirming version of FC card.
Page 325: Figure K.33 [Controller Information] Window
Appendix K How to Confirm Firmware of SAS RAID Controller Card How to confirm firmware version and UEFI driver version of FC card FIGURE K.33 [Controller Information] window Note Press [Esc] key sometimes and go back to top menu. C122-E175-02EN...
Page 326: Appendix L Software
How to confirm firmware version and UEFI driver version of FC card Appendix L 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 (C122-B022EN).
Page 327: Appendix M Failure Report Sheet
Appendix M Failure Report Sheet Failure Report Sheet Appendix M 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: □...
Page 328: Appendix N Information Of Pci Express Card
Appendix N Information of PCI Express card Failure Report Sheet Appendix N 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’ and ‘Subsystem Vendor ID’.

This manual is also suitable for:

Primequest 2400e Primequest 2800e Primequest 2800b

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 PCI Card Hot Maintenance in Red hat Enterprise Linux 6

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

CHAPTER 6 Replacement of HDD/SSD

CHAPTER 7 PCI Express Card Hot Maintenance in Windows

CHAPTER 8 Backup and Restore

CHAPTER 9 Chapter System Startup/Shutdown and Power Control

CHAPTER 10 Configuration and Status Checking (Contents, Methods, and Procedures)

CHAPTER 11 Error Notification and Maintenance (Contents, Methods, and Procedures)

Quick Links

Troubleshooting

Related Manuals for Fujitsu PRIMEQUEST 2000 Series

Summary of Contents for Fujitsu PRIMEQUEST 2000 Series