FUJITSU Server PRIMEQUEST 2000 Series Administration Manual C122-E175-01EN
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). Errata and addenda for the manual The PRIMEQUEST 2000 Series Errata and Addenda (C122-E182EN) provides errata and addenda for the manual.
Preface Revision History Edition 01 Date 2014-02-18 Revised location (type) (*1) ’-’ Description ‘-’ *1: Chapter, section, and item numbers in the "Revised location" column refer to those in the latest edition of the document. However, a number marked with an asterisk (*) denotes a chapter, section, or item in a previous edition of the document.
Preface Product operating environment This product is a computer intended for use in a computer room environment. For details on the product operating environment, see the following manual: PRIMEQUEST 2000 Series Hardware Installation Manual (C122-H007EN) Safety Precautions Alert messages This manual uses the following alert messages to prevent users and bystanders from being injured and to prevent property damage.
Preface iv C122-E175-01EN
Preface Warning label location (the main cabinet left) Warning label location (PCI_Box) v C122-E175-01EN
Preface Notes on Handling the Product About this product This product is designed and manufactured for standard applications. Such applications include, but are not limited to, general office work, personal and home use, and general industrial use. The product is not intended for applications that require extremely high levels of safety to be guaranteed (referred to below as "safety-critical" applications).
Preface Furthermore, if a software license agreement restricts the transfer of the software (operating system and application software) on the hard disk in the server or other product to a third party, transferring the product without deleting the software from the hard disk may violate the agreement. Adequate verification from this point of view is also necessary.
Preface Title PRIMEQUEST 2000 Series Errata and Addenda PRIMEQUEST 2000 Series General Description SPARC Enterprise/ PRIMEQUEST Common Installation Planning Manual PRIMEQUEST 2000 Series Hardware Installation Manual PRIMEQUEST 2000 Series Installation Manual PRIMEQUEST 2000 Series User Interface Operating Instructions PRIMEQUEST 2000 Series Administration Manual PRIMEQUEST 2000 Series Tool Reference PRIMEQUEST 2000 Series Message Reference PRIMEQUEST 2000 Series REMCS Installation Manual PRIMEQUEST 2000 Se
Preface Title ServerView Suite Basic Concepts ServerView Operations Manager Installation ServerView Agents for Linux ServerView Operations Manager Installation ServerView Agents for Windows ServerView Mission Critical Option User Manual ServerView RAID Manager VMware vSphere ESXi 5 Installation Guide MegaRAID SAS Software MegaRAID SAS Device Driver Installation Modular RAID Controller Installation Guide Description Manual code Describes basic concepts about ServerView Suite.
Preface Formal product name Abbreviation Novell (R) SUSE(R) LINUX Enterprise Server 11 Service Pack 3 SLES11 SP3 Trademarks - Microsoft, Windows, and Windows Server are trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. - Linux is a registered trademark of Linus Torvalds. - Red Hat, the Shadowman logo and JBoss are registered trademarks of Red Hat, Inc. in the U.S. and other countries.
Preface the form to us: https://www-s.fujitsu.com/global/contact/computing/PRMQST_feedback.html - The contents of this manual may be revised without prior notice. - In this manual, the Management Board and MMB firmware are abbreviated as "MMB." - In this manual, IOU_10GbE and IOU_1GbE are collectively referred to as IO Units. - Screenshots contained in this manual may differ from the actual product screen displays.
Preface Contents Preface................................................................................................................................................................................................................ i CHAPTER 1 Network Environment Setup and Tool Installation .............................................................................................................1 1.1 External Network Configuration ........................................................................
Preface 4.2.1 Preparing for SB hot add ....................................................................................................................................................... 59 4.2.2 Confirming the status of SB before SB hot add.................................................................................................................... 60 4.2.3 DR operation in SB hot add..................................................................................................................
Preface 6.4.2 FC card addition procedure................................................................................................................................................. 145 6.5 Hot Replacement Procedure for iSCSI.................................................................................................................................... 145 6.5.1 Confirming the incorporation of a card with MPD............................................................................................
Preface 10.2.9 Problems with partition operations ................................................................................................................................. 185 10.3 Notes on Troubleshooting ........................................................................................................................................................ 185 10.4 Collecting Maintenance Data ...........................................................................................................
Preface F.1.9 MMB ..................................................................................................................................................................................... 221 F.1.10 LAN .................................................................................................................................................................................. 221 F.1.11 OPL.......................................................................................................
Preface Figures FIGURE 1.1 External network configuration............................................................................................................................................1 FIGURE 1.2 External network functions ..................................................................................................................................................2 FIGURE 1.3 Management LAN configuration.......................................................................................
Preface FIGURE 7.3 [Restore BIOS Configuration] window (partition selection)........................................................................................... 155 FIGURE 7.4 [Backup/Restore MMB Configuration] window ............................................................................................................. 156 FIGURE 7.5 Restore confirmation dialog box .................................................................................................................................
Preface FIGURE J.12 [General] tab in the ServiewView RAID Manager....................................................................................................... 247 FIGURE J.13 Menu window................................................................................................................................................................ 248 FIGURE J.14 Device List in [Device Manager] window....................................................................................................
Preface Tables TABLE 1.1 External network names and functions.................................................................................................................................1 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.
Preface TABLE 9.1 Functions provided by the MMB Web-UI ........................................................................................................................ 169 TABLE 9.2 Functions provided by the MMB CLI ............................................................................................................................... 171 TABLE 9.3 Functions provided by the UEFI...................................................................................................................
Preface TABLE F.21 PCI_Box status and PCI_Box LED display .................................................................................................................. 222 TABLE F.22 PCI Express card status and LED display .................................................................................................................... 222 TABLE F.23 IO_PSU LED ............................................................................................................................................
CHAPTER 1 Network Environment Setup and Tool Installation 1.1 External Network Configuration 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). 1.
CHAPTER 1 Network Environment Setup and Tool Installation 1.1 External Network Configuration Letter C External network name Function - REMCS connection Operation LAN (production LAN) For job operations 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.
CHAPTER 1 Network Environment Setup and Tool Installation 1.2 How to Configure the External Networks (Management LAN/ Maintenance LAN/Production LAN) 1.2 How to Configure the External Networks (Management LAN/ Maintenance LAN/Production LAN) The PRIMEQUEST 2000 series server must be connected to the following three types of external networks. The respective external networks are dedicated to security and load distribution. (See FIGURE 1.1 External network configuration.
CHAPTER 1 Network Environment Setup and Tool Installation 1.2 How to Configure the External Networks (Management LAN/ Maintenance LAN/Production LAN) Name IP Address NIC (common) Type address (*3) IP address setting method the MMB CLI or MMB Web-UI. Description with REMCS, without using the management LAN. The MMB also uses the IP address to communicate with the maintenance terminal connected to the CE port.
CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN LAN port mounted in PCI Express slot in IOU or PCI_Box. IP address setting method each partition. Description ports in the relevant partition must have IP addresses. (Assign IP addresses to the ports used for actual operation.) *1 The default IP address (172.30.0.[partition number + 2]) is assigned during installation of SVS. The default IP address can be used unless it is in conflict with the one in the other subnet.
CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN FIGURE 1.3 Management LAN configuration No. Description (1) Physical LAN IP example (MMB #0): 10.20.30.101 (2) Physical LAN IP example (MMB #1): 10.20.30.102 (3) 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. If a failure occurs in the active MMB itself, the Virtual LAN channels become unusable.
CHAPTER 1 Network Environment Setup and Tool Installation 1.
CHAPTER 1 Network Environment Setup and Tool Installation 1.3 Management LAN Display/Setting item Description 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. SNMP Configuration: SNMP-related settings SNMP Community Specifies SNMP System Information and Community/User values.
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]. - You can edit the user name, password, permission, and status (Enable/Disable) in the [Edit User] - To deny access to a user, set [No Access] for permission or [Disable] for [Status].
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. This redundant configuration enables recovery from management LAN errors. The redundant configuration of the user port is disabled as standard, and only user port #0 is enabled.
CHAPTER 1 Network Environment Setup and Tool Installation 1.4 Maintenance LAN/REMCS LAN 1.4 Maintenance LAN/REMCS LAN The MMB provides the following LAN ports for maintenance purposes. TABLE 1.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use 1.5.2 Redundancy of the production LAN This section describes redundancy of the production LAN. Duplication of the transmission path between servers (high-speed switching method) For details on duplication of the transmission path between servers, see 'PRIMECLUSTER Global Link Service Configuration and Administration Guide Redundant Line Control Function' (J2UZ-7781).
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use - For a terminal whose operating system is Windows Vista or Windows 7, set UAC (User Account Control) or UAP (User Account Protection) to "Disabled”. - For video redirection and virtual media, a connection may not be established if the network is connected via a proxy. In such cases, change the browser setting to avoid network connection via the proxy.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Function Description zoom-out and language selection. Operate keyboard by keyboard of terminal PC. Display and operate virtual keyboard Operate mouse by mouse of terminal PC. A mouse pointer in a partition and a mouse pointer in a terminal PC run simultaneously. Display of mouse in a terminal PC can be set to enable or disable.
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. (3) You can perform partition operations from the [Video Redirection] window by using the keyboard and mouse.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Menu Bar Pause Redirection Resume Redirection Refresh Video Turn ON Host Display Video Turn OFF Host Display Low Bandwidth Mode Normal 8 bpp 8 bpp B&W 16 bpp Capture Screen Full Screen Start Record Stop Record Settings Exit Description Perform pause of [Video redirection] window. Release pause of [Video redirection] window. Refresh [Video redirection] window. Show video operation on host monitor.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Menu Bar French(Belgium) Dutch(Belgium) Russian(Russia) Japanese(QWERTY) Japanese(Hiragana) Japanese(Katakana) Turkish - F Turkish - Q Description Set to ‘French (Belgium)’. Set to ‘French.’ Set to ‘Russian’. Set to ‘Japanese (QWERTY)’. Set to ‘Japanese (Hiragana)’. Set to ‘Japanese (Katakana)’. Set to ‘Turkish -F’. Set to ‘Turkish -Q’.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use When you use two displays to operate LSI WebBIOS in Legacy Mode, use primary display of monitor 1. If you set to ‘Hide mouse mode’ in secondary display of monitor 2, cursor does not run. Even if you set to ‘Hide mouse mode’, it is no problem to use primary display and operate UEFI. (*2) Power menu is shown in only PRIMEQUEST 2800B. It is not shown in other models.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use Below description is how to connect video redirection. 1. First terminal PC is connected to a partition by video redirection with Full Virtual Console Access. 2. If you connect to same partition by video redirection, a massage requesting permission to virtual console access appears in second terminal PC. FIGURE 1.8 Message of requesting access to Virtual Console in second terminal PC 3.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.13 Popup for [Allow only video] in second terminal PC FIGURE 1.14 Popup for [Deny Access] in second terminal PC FIGURE 1.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.17 Example of setting partition #3 (1) 2. If the message “Do you really want to start the Console Redirection (yes/no)?” appears, input ‘yes’. You can connect to specified partition. FIGURE 1.18 Example of setting partition #3 (2) 3. If you connect to other partition, perform step 1 and step 2 again after closing current console redirection.
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. The terminal software of the disconnected user displays the following window. FIGURE 1.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use - - You are using the remote storage function from a terminal running one of the following Windows operating systems: - Windows XP - Windows Vista - Windows 7 - Windows Server 2008 R2 - Windows Server 2012 You are using two USB devices as remote storage devices. This issue does not occur when only one USB device is used.
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 [Browse] [Connect]/[Disconnect] [Close] Description Add image file as virtual media. Connect or disconnect selected device to a partition. Closes this 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 Look In File name File of type Open Cancel Description Displays the current search location Used to enter the device index letter (e.g., E:) Used to specify a file type. Adds the selected device to the list. Closes this window.
CHAPTER 1 Network Environment Setup and Tool Installation 1.6 Management Tool Operating Conditions and Use FIGURE 1.24 [Virtual Media] window (2) Retrying a connection after the Reserved SB is switched When changing the Home SB of the partition, connect console and video redirection again. 1.6.3 ServerView Suite ServerView Suite environment setup for Windows For details on the environmental settings of ServerView Suite for Windows, see the ServerView Suite ServerView Installation Manager.
CHAPTER 2 Operating System Installation (Link) 1.6 Management Tool Operating Conditions and Use CHAPTER 2 Operating System Installation (Link) 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.
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. 3.1 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. - 3.1.2 Setting procedure of partition in MMB Web-UI 3.1.
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. FIGURE 3.1 Conceptual diagram of the partitioning function (PRIMEQUEST 2400E) No.
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. FIGURE 3.2 Conceptual diagram of the partitioning function (PRIMEQUEST 2800E) No.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration 3.1.2 Setting procedure of partition in MMB Web-UI The procedure to set the partition in the MMB Web-UI is described below. 1. Power off the partition. For details, see "PRIMEQUEST 2000 series Tools Reference” '1.3.1 [Power Control] window'. 2. Add the SB and IOU into the partition. For details, see "PRIMEQUEST 2000 series Tools Reference” '1.3.3 [Partition Configuration] window'. 3. Set the Home SB. 4.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration FIGURE 3.3 SB hotadd No. (1) Description Dynamic addition of SB (operated by the operator) FIGURE 3.4 SB Hot remove (Disconnecting a faulty SB) No.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration FIGURE 3.5 IOU Hot add No. (1) Description Dynamic addition of IOU (operation by operator) FIGURE 3.6 IOU hot remove (removal of failed IOU) No. (1) (2) (3) Description Fault suspected Dynamic disconnection of IOU (operator operation) Replacement Rules of DR The DR is set in the UEFI. The DR applicable conditions are as follows. TABLE 3.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration TABLE 3.3 DR supported list Component Function Windows Server Windows 2008 R2 or later VMware ESXi 5 or later SB CPU (*2) DIMM (*2) Red Hat Enterprise Linux RHEL6.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration - For the partition with DR mode enable, memory size within PPAR must be 1TB or less. When hot adding SB, total memory size within the PPAR must be 1TB or less after adding a SB. - Do not perform DR operation when high load is applied to the partition since TIMEOUT may occur if DR operation is performed when high load is applied to the partition.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration 3.2.2 Reserved SB In the Reserved SB function, a spare SB is mounted in the chassis in advance, the faulty SB is automatically disconnected, the spare SB is incorporated and the partition is restarted. The spare SB intended for switching when there is a fault is called the Reserved SB. All models in the PRIMEQUEST2000 series support the Reserved SB function.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration - An SB can be set as a Reserved SB for multiple partitions. - Multiple Reserved SBs can be set for a single partition. - If a partition is configured by a single SB, the CPU and DIMM of the Reserved SB must comply with the installation rules in the Reserved SB. (*1) - Two CPUs must be mounted on a Reserved SB.
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. When these workaround steps are executed, restart is not requested when there is a switching to the Reserved SB due to SB failure. 1.
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) No. (1) Description No switching to the Reserved SB FIGURE 3.22 Example 2. When multiple SBs have failed within a partition No. (1) Description No switching to the Reserved SB FIGURE 3.9 Example 3.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration FIGURE 3.10 Example 4. where Reserved SBs (#1, #2, #3) of Partition #0 belong to other partitions 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. FIGURE 3.11 Example 5.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration FIGURE 3.12 Example 6. Example where a Reserved SB has been set in SB #0 (When the Home SB has failed) No. (1) Description Since Partition #0 is the configuration of SB #0 and SB #2, SB #0 with the lowest number becomes the Home SB. FIGURE 3.13 Example 7. Example when SB #0 is set as the Reserved SB (when an SB other than the Home SB fails) No.
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. - When the partition that incorporates the Reserved SB is powered on, the firmware instructs power off for the corresponding partition.
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. - When simultaneously using the Software RAID and the Reserved SB function, do not configure the HDD/SSD Mirror in the SB.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration Memory Operation Mode Description Memory Mirror. Mode in which the Memory Spare is used. Note The Memory Spare cannot be used when the Memory Mirror has been set. Spare Mode 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.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration - 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. The memory incorporation status before and after a partition restart is shown below. FIGURE 3.14 Status when there is an error in the memory (mirror maintenance mode) FIGURE 3.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.2 High availability configuration FIGURE 3.16 Status when there error has occurred in the memory (memory capacity maintenance mode) FIGURE 3.17 Status when an error has occurred in the memory (memory capacity maintenance mode) The patterns supported in the combination of memory mirror status and failed DIMM are listed in the table below. TABLE 3.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.
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. TABLE 3.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.3 Replacing components Since there may be a time deviation after the Home SB is replaced, set the time in the operating system when the NTP is not used. IOU_1GbE/IOU_10GbE If the DR function (IOU hot remove and IOU hot add) is used, the IOU_1GbE and IOU_10GbE can be replaced even if the partition that uses the IOU_1GbE/IOU_10GbE is powered on.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.3 Replacing components In a RAID configuration (Linux software RAID) 1. Place the faulty PCI Express card offline and remove the card. Example: # mdadm/dev/mdO --fail /dev/fiob # mdadm/dev/mdO--remove /dev/fiob 2. Power off the partition. For details on the powering off the partition, see ‘7.1.2 Powering off partitions’ in “PRIMEQUEST 2000 series Installation Manual” (C122-E174). 3. Replace the faulty PCI Express card. 4.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.4 Expansion of components Remarks If the device is used as a SWAP device, the formatting must have a 4K sector size. c fio-attach (Making the device available on the operating system) Example: # fio-detach /dev/fct0 # fio-format -b 4K /dev/fct0 # fio-attach /dev/fct0 Remarks For details on each command, see ‘Appendix A-Utility Reference’ in the ‘PCIeSSD-785GB/PCIeSSD1.2TB ioMemory VSL x.x.x User Guide for Linux’. x.x.x.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.4 Expansion of components Component name MP, PDB PCI_Box (*3) IO_PSU IO_FAN PEXU AC power off (Device stop) Expandable Expandable Expandable PCI Express card - : Outside the expansion target *1: PCI hot plug function is required *2: DR function is required *3: For only PRIMEQUEST 2400E and 2800E.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot Procedure before expansion Stop all the partitions referring to‘7.1.2 Powering off Partitions’ in the “PRIMEQUEST 2000 series Installation Manual” (C122-E174). Procedure after expansion Start the required partition referring to 7.1.1 Powering on Partitions’ in the “PRIMEQUEST 2000 series Installation Manual” C122-E174). 3.4.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot 3.5.1 Checking the status after switching to a Reserved SB and automatic rebooting The status after the partition reboot is checked in the [Partition Configuration] window, [System Status] window, [SB #x] window of the MMB Web-UI. Immediately after switching to a Reserved SB and the partition has started (booted), the status will be as follows.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.5 Process after switching to the Reserved SB and Automatic Partition Reboot 7. Start the partition. Click [Partition] - [Power Control]. In the [Power Control] window, select [Power on] from [Power Control] of the relevant partition, and click the [Apply] button. The partition will start. When setting the maintenance replaced SB as a Reserved SB Perform the following procedures for the replaced SB. 1.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.6 Replacing the Home SB No. TABLE 3.
CHAPTER 3 Component Configuration and Replacement (Add, Remove) 3.6 Replacing the Home SB No. configuration home SB Home SB of P0 Home SB of P1 Logical SB of P0 LSB0 LSB1 LSB2 LSB3 (LSB) Logical SB of P1 LSB1 LSB0 LSB2 LSB3 (LSB) As default (one partition four SB configuration), the relationship between the LSB No. and Socket No. is as follows. TABLE 3.20 Relationship between LSB No. and Socket No LSB No. 0 1 2 3 Socket No.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.1 Dynamic Reconfiguration (DR) CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 This chapter describes hot maintenance of PCI cards in Red Hat Enterprise Linux 6. 4.1 Dynamic Reconfiguration (DR) This section describes Dynamic Reconfiguration (DR). DR function has to be enabled by MMB Web-UI and Dynamic Reconfiguration Utility package has to be installed in the system to perform hot maintenance of SB and IOU.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB 4.1.2 dp Command Package Install/ Uninstall This section describes the install /uninstall of the dp command package. The dp 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. Use FJSVdp-util-RHEL-x.x.x-x-x86_64.tar.gz.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB a. Check if the size of the dump disk save area is sufficient for the memory capacity to be added. For details on how to estimate the size required, contact the distributor where you purchased your product, or your sales representative. b. Check if the points/restrictions are clear. For detail, see ‘3.2.1 Dynamic Reconfiguration (DR)’ 5. Switch to the maintenance mode. Insert the SB to be added into a free SB slot. 6.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB Above ceil (x) expresses the ceiling function. The ceil (x) is the smallest integer not less than real number x. e.g. ceil (2.15) = 3, ceil (4) = 4. For how to get 𝑃1 and 𝐶1 , see below ‘Reference’. The estimation of the time 𝑡2 and 𝑡4 when collaboration program is working is equal to the sum of the time when each program registered as collaboration program in /opt/FJSVdp-util/user_command will take to finish process.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.2 Hot add of SB 4.2.4 How to deal with when timeout occurs while OS is processing SB hot add If OS does not finish the process of SB hot add within predetermined time, timeout message “DR sequence timeout: SB hot-add OS failure” is shown on MMB CLI. It means that DR completion message from OS does not arrive at MMB. In such case, some collaboration programs may hang though DR process is still running on OS.
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. In case that the number of CPU or the size of memory does not increase though they does not reach expected quantity. 3.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU 4.3 Hot replacement of IOU This section describes the hot replacement of the IOU. There are two cases in hot replacement of the IOU: - Replacing IOU itself due to trouble of IOU itself or trouble of onboard NIC - Replacing, expanding or removing PCI Express card installed in IOU For replacing, expanding or removing PCI Express card, IOU itself does not need to be replaced.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU 0000:82:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:83:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:84:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:85:02.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:85:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:85:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:85:10.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU 1. Confirm where the NIC is mounted. Confirm the correspondence between PCI Address and interface name of NIC mounted in the IOU which is confirmed by above “dp show IOU” command. Example: When PCI Address is “0000:89:00.0”. # 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.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU Example: eth0 grep eth0 /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="2c:d4:44:f1:44:f0", ATTR{type}=="1", ¥ KERNEL=="eth*", NAME="eth0" The ¥ at the end of a line indicates that there is no line feed. You can always obtain the correct hardware address from the description in etc/udev/rules.d/70persistent-net.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU 6. Delete the entries associated with the replaced NIC from the udev function rule file. The entry to be removed is only onboard NIC for replacing IOU itself. For replacing or removing PCI Express card, the entry to be removed is the interface corresponding to the PCI Express card. a Confirm the correspondence between the interface name and hardware address in the table created in step 2.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU system.eternus-dx400:00001049.cm1ca0p0 -p 192.168.2.66:3260 –logout c Use the iscsiadm command to confirm that the target session has been disconnected. Example which confirms the state of session after disconnecting # /sbin/iscsiadm -m session tcp: [1] 192.168.1.64:3260,1 iqn.200009.com.fujitsu:storage-system.eternusdx400:00001049.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU # /opt/FJSVdp-util/sbin/dp stat IOU IOU0: empty IOU1: empty IOU2: empty IOU3: offline IOU added to partition is shown as offline state because it is power-off state at this time. 8. Execute “/opt/FJSVdp-util/sbin/dp add IOU” command on the shell of OS. The IOU to be removed will turn on. Example: turning on IOU 3 # /opt/FJSVdp-util/sbin/dp add IOU3 4.3.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU ATTR{address}=="00:19:99:d7:36:21", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x8086:0x1521 (igb) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="00:19:99:d7:36:22", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" : : The ¥ at the end of a line indicates that there is no line feed.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.3 Hot replacement of IOU under bonding. For a single NIC interface: Execute the following command to activate the interface. Activate all the necessary interfaces. # /sbin/ifup ethX Also, if the single NIC interface has a VLAN device and the VLAN interface was temporarily removed, restore the VLAN interface. If the priority option has changed, set it again. # /sbin/vconfig add ethX Y # /sbin/ifup ethX.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.4 Hot add of IOU # /opt/FJSVdp-util/sbin/dp add IOU1 4.4.3 Operation after IOU hot add This section describes the process and operation after IOU hot add. 1. Check the resource that was added. Execute the /opt/FJSVdp-util/sbin/dp show IOU command in the operating system shell. Example：When IOU1 was added # /opt/FJSVdp-util/sbin/dp show IOU1 0000:03:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0000:04:09.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove 4.5 IOU hot remove The description of the flow of the preparation is as follows. Note - If iSCSI (NIC) is mounted on an IOU, hot replacement of the IOU can be performed only if all of below conditions are satisfied. - DM-MP (Device-Mapper Multipath) or ETERNUS multi driver (EMPD) is used for storage connection.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove 0000:89:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:89:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:8c:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:8c:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01) 0000:8f:00.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.5 IOU hot remove Execute “ethtool -p” command, making the LED of NIC blinked. Check IOU or PCI_box connected to the IOU, checking in which slots the NIC is mounted, (e.g. PCI#0) Example: Blinking the LED of the NIC corresponding to interface “eth0” for ten seconds. # /sbin/ethtool p eth0 10 2. Make a table with information including interface name, hardware address and PCI bus address of NIC mounted on IOU to be replaced.
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 eth0 eth1 eth2 ... Hardware address 2c:d4:44:f1:44:f0 2c:d4:44:f1:44:f1 00:19:99:d7:36:5f Bus address 0000:89:01.0 0000:89:01.1 0000:8f:00.0 ... Location Onboard 0 Onboard 1 PCI#0 ... 3. Execute the higher-level application processing required before NIC replacement. Stop all access to the interface as follows.
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:f1", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" : : The ¥ at the end of a line indicates that there is no line feed. Example of descriptions in the file after editing (In the example, eth0 was deleted, and eth1 is commented out.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards There are two ways to perform PCI hot plug: - Operation by using sysfs - Operation by using dp commands You can perform the operation by using dp commands if Dynamic Reconfiguration utility is installed in the partition. If not, be sure to use the operation by using sysfs.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards This slot number is the identification information for operating the slot of the PCI Express card to be replaced. Note The four-digit decimal numbers shown in in D.2 Correspondence between PCI Slot Mounting Locations and Slot Numbers have the leading digits filled with zeroes. The actual slot numbers do not include the zeroes in the leading digits.
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. For the appropriate procedures, see the respective manuals.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 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.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 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. Replace it with this window displayed. See the figure in ‘B.1 Physical Mounting Locations of Components’ to confirm the location of the PCI Express card to be replaced. Note Do NOT click [Next] until replacing the PCIC. 8.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards Note Ask the administrator of your system to power on the PCI Express slot. 9. The window updating status appears. 10. Check the status of replaced PCIC and click [Next].
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards 11. 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. 4.6.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards - To prevent a device name mismatch due to the failure, addition, removal, or replacement of an FC card, access the SAN disk unit by using the by-id name (/dev/disk/by-id/...) for the device name. - If all the paths in a mounted disk become hidden when an FC card is hot replaced, unmount the disk. Then, execute PCI hot plug.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards scsi 2:0:0:0: Direct-Access FUJITSU E4000 ¥ 0000 PQ: 1 ANSI: 5 ...(*3) The ¥ at the end of a line indicates that there is no line feed. 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. (See Note below.) In this case, power off the slot once.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards In this case, check for the relevant message on the FC card incorporation by using the following procedure. a. Confirm the host number. xx in scsixx (xx is a numerical value) in the message is a host number. In the above example, the host number is 10. b. Check whether the following file exists by using the host number.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards system information. First, confirm the bus address of the PCI Express slot that has the mounted interface to be replaced. Example: eth0 interface # ls -l /sys/class/net/eth0/device lrwxrwxrwx 1 root root 0 Sep 29 10:17 ¥ /sys/class/net/eth0/device ->../../../0000:00:01.2/0000:08:00.2/0000:0b:01.0 The ¥ at the end of a line indicates that there is no line feed.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards hardware address. Example: eth0 [For a single interface] # cat /sys/class/net/eth0/address 00:0e:0c:70:c3:38 Example: eth0 [For a bonding interface] The bonding driver rewrites the values for the slave interface of the bonding device. Confirm the hardware address by executing the following command. # cat /proc/net/bonding/bondY Ethernet Channel Bonding Driver ......... . . Slave interface: eth0 .
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards If the single NIC interface has a VLAN device, you also need to remove the VLAN interface. Perform the following operations (before deactivating the real interface). # /sbin/ifdown ethX.Y # /sbin/vconfig rem ethX.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards deleted even if the NIC is removed. Leaving the entries of the removed NIC may have the following impact. - The interface names defined in the entries of the removed NIC cannot be assigned to the replacement NIC or an added NIC. For this reason, delete or comment out the entries of the removed NIC from the udev function rule file.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards Confirm that a new hardware address is defined for the bus address. Also confirm that the assigned interface name is the same as that before the NIC replacement. Also confirm that the relevant entries in the above-described table were automatically added to the udev function rule file, /etc/udev/rules.d/70-persistent-net.rules.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="00:0e:0c:70:c3:40", ATTR{type}=="1", ¥ KERNEL=="eth*", NAME="eth0" # PCI device 0x****:0x**** (e1000) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ¥ ATTR{address}=="00:0e:0c:70:c3:41", ATTR{type}=="1", ¥ KERNEL=="eth*", NAME="eth1" : : The ¥ at the end of a line indicates that there is no line feed. c Reflect the edited rules again.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards # /sbin/ifup ethX Also, if the single NIC interface has a VLAN device and the VLAN interface was temporarily removed, restore the VLAN interface. If the priority option has changed, set it again. # /sbin/vconfig add ethX Y # /sbin/ifup ethX.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.6 Hot Replacement of PCI Express Cards b Use the iscsiadm command to log out from the path (iqn) through which the iSCSI card to be replaced is routed, and disconnect the session. Example which confirms the state of session before disconnecting: # /sbin/iscsiadm -m session tcp: [1] 192.168.1.64:3260,1 iqn.200009.com.fujitsu:storage-system.eternusdx400:00001049.cm0ca0p0 tcp: [2] 192.168.2.66:3260,3 iqn.200009.com.fujitsu:storage-system.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards g 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.200009.com.fujitsu:storage-system.eternusdx400:00001049.cm0ca0p0 tcp: [3] 192.168.2.66:3260,3 iqn.200009.com.fujitsu:storage-system.eternusdx400:00001049.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 4. Powering on a PCI Express slot. 5. Performing the required operating system and software operations depending on the PCI card type Notes This section describes instructions for the operating system and subsystems (e.g., commands, configuration file editing).
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 4. Select the radio button of PCI_Box with the particular number, click [Next] Example of operation for hot replacing PCI Express card of PCIC#1 mounted on PCI_Box#0 5.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 6. Select [Hot Partition Maintenance (Target unit in a running partition.)] and click [Next] 7. Maintenance mode is set (with information area of MMB Web-UI gray out) and then replacement instruction for the particular PCIC appears. Add a new PCI Express card with this window displayed. See the figure in ‘B.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards Note Do NOT click [Next] until adding the PCIC. 8. After replacing the particular PCIC and powering on the particular PCIC slot, click [Next]. For how to power on the PCIC slot, see “Powering on and off PCI Express slots” in “4.7.2 PCI Express card addition procedure in detail”. It is the administrator of your system who power on the PCI Express slot.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 10. Check the status of added PCIC and click [Next]. 11. Confirm that maintenance mode has been released (with information area of MMB Web-UI not gray out) and click [Next].
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 4.7.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. - Although you can hot replace FC card used for dump device of sadump, collecting dump of memory fails until reconfiguring HBA UEFI or extended BIOS with the partition inactive after replacing the FC card.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards 7. Check whether there is an error in added FC card by MMB Maintenance Wizard. This step is performed by the field engineer in charge of your system. For details on the operation of replacement, see step 8 to 11 of ‘Operation for Hot replacement of PCI Express card by Maintenance Wizard’ in “4.7.2 PCI Express card addition procedure in detail”. 8.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards Lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RXbytes:0 (0.0 b) TX bytes:0 (0.0 b) 2. Confirm the slot number of the PCI slot by using the following procedure. See ‘Confirming the slot number of a PCI Express slot’ in “4.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.7 Hot Addition of PCI Express cards The explanation here assumes, as an example, that a name automatically assigned by the system is used. To install a new interface, you can use a new interface name different from the one automatically assigned by the system. Normally, there is no requirement on the name specified for a new interface.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards incorporate it into the bonding configuration. Example: bondY is the bonding interface name, and ethX is the name of the interface to be incorporated. # /sbin/ifenslave bondY ethX For a newly added bonding interface with a SLAVE interface, execute the following command to activate the interfaces. You need not execute the ifenslave command individually for the SLAVE interface. # /sbin/ifup bondY 4.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing 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”. Powering off PCI Express slots See ‘Powering on and off PCI Express slots’ in “4.6.2 PCI Express card replacement procedure in detail”. 4.8.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards FIGURE 4.5 Single NIC interface and bonding configuration interface NIC removal procedure This section describes the procedure for hot plugging only a network card. Note When removing multiple NICs, be sure to remove them one by one. If you do this with multiple cards at the same time, the correct settings may not be made. 1. Confirm the slot number of the PCI slot that has the mounted interface.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards 3. Execute the higher-level application processing required before NIC removal. Stop all access to the interface as follows. Stop the application that was confirmed in step 2 as using the interface, or exclude the interface from the target of use by the application. 4. Deactivate the NIC. Execute the following command to deactivate all the interfaces that you confirmed in step 2.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards The ¥ at the end of a line indicates that there is no line feed. [Example of descriptions in the file after editing] The entries for the eth10 interface are commented out.
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.8 Removing PCI Express cards Work to be performed before iSCSI (NIC) removal For iSCSI (NIC) hot replacement, be sure to follow the procedure below when performing Step 3 of the ‘NIC removal procedure’ in ‘4.8.4 Network card removal procedure’ 1. Perform the work for suppressing access to the iSCSI connection interface. a Confirm the state of multiple path by DM-MP (*1) or EMPD (*2).
CHAPTER 4 PCI Card Hot Maintenance in Red Hat Enterprise Linux 6 4.
CHAPTER 5 Replacement of HDD/SSD 5.1 Hot replacement of HDD/SSD with Hardware RAID configuration CHAPTER 5 Replacement of HDD/SSD This chapter describes how to replace Hard Disk Drives (HDD) or Solid State Drives (SSD). 5.1 Hot replacement of HDD/SSD with Hardware RAID configuration This section describes how to replace Hard Disk Drives (HDD) or Solid State Drives (SSD) with Hardware RAID configuration. 5.1.
CHAPTER 5 Replacement of HDD/SSD 5.2 Preventive replacement of HDD/SSD with Hardware RAID configuration - - 5.2 For replacement of a HDD or SSD included in a DU 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).
CHAPTER 5 Replacement of HDD/SSD 5.2 Preventive replacement of HDD/SSD with Hardware RAID configuration - If HDD or SSD other than target HDD or SSD for preventive replacement fails in step3, field engineers in charge of your system replace the failed HDD or SSD. - Step7 is performed by the field engineer in charge of your system. 1. Back up data in all HDDs or SSDs connected to the RAID controller card to which the target HDD or SSD for preventive replacement is connected. 2.
CHAPTER 5 Replacement of HDD/SSD 5.3 Replacement of HDD/SSD in case hot replacement cannot be performed 7. Confirm whether a rebuild of the HDD or SSD has been already completed by using the below steps depending on whether a spare disk is set or not. - - 5.3 If not set a spare disk A rebuild is automatically performed to replaced HDD or SSD. Then, the Alarm LED of the HDD or SSD starts blinking. Confirm whether a rebuild of replaced HDD or SSD has been already completed by MMB Web-UI.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.1 Overview of Hot Maintenance CHAPTER 6 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. 6.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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 No.3 of follows respectively. Addition procedure 1. Confirm physical location of added PCI card. 2. Add PCI card by using MMB Maintenance Wizard. [FE’s work] 3. Confirm added PCI card by using MMB Maintenance Wizard.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. 2. Disable target PCI cards by using Device manager. a Confirm target PCI card in Device Manager.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. a Click Icon of Safely remove devices from computer ( ) at information zone in lower-right of desktop display. b Click target identified device name with step 2-a in displayed list, and disable PCI card. 4. Replace PCI card by using MMB Maintenance Wizard.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. Power off target PCIC slot and replace PCI card with opening this page. See diagrams in ‘B.1 Physical Mounting Locations of Components’ and ‘B.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.2 Common Hot Plugging Procedure for PCI Express cards Note About powering on PCIC slot, the system administrator must perform. 9. Status updating menu will be opened. 10. Confirm status of target replaced PCI card, and click [Next] button.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. Note As the follow, right-click target device in Device Manager, if there are [Enable] in displayed menu, check [Enable].
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.2 Common Hot Plugging Procedure for PCI Express cards 6.2.2 Addition procedure 1. Confirm the physical location, segment number, and bus number. Confirm the mounting location of the PCI card. See the figure in B.1 Physical Mounting Locations of Components to check the mounting location (board and slot) of the PCI card. 2. Add PCI card by using MMB Maintenance Wizard.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. Check button of target PCIC number for adding, and click [Next] button.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. Power off target PCIC slot and add PCI card with opening this page. See diagrams in B.1 Physical Mounting Locations of Components and B.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.2 Common Hot Plugging Procedure for PCI Express cards Note Don’t click [Next] Button before adding PCI card. About powering off PCIC slot, the system administrator must perform. 8. Add target PCI card, power on target PCIC slot, and click [Next] button. About powering on PCIC slot, see Powering on and off PCI slots. About powering on PCIC slot, the system administrator will perform. Note About powering on PCIC slot, system Administrator must perform.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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]. (In case of [Disable], this work is not necessary) 6.2.3 About removal Note Windows does not support PCI card removal. 6.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. - There are some precautions on teaming with Intel PROSet(R). For details on the precautions, see ‘G.8 NIC (Network Interface Card)’. 1. Confirm physical location, segment number and bus number of NIC to be replaced.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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 ‘6.2.1 Replacement procedure’ in ‘6.2 Common Hot Plugging Procedure for PCI Express cards’. 7. Stop target NIC by using safely remove devices from computer. Stop NIC with step 3 at ‘6.2.1 Replacement procedure’ in ‘6.2 Common Hot Plugging Procedure for PCI Express cards’. 8.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. In the Device Manager, confirm that the NIC is incorporated into the team.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.4 FC Card Hot Plugging Note As the follow, right-click target device in Device Manager, if there are [Enable] in displayed menu, check [Enable]. (In case of [Disable], this work is not necessary) 6.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). Replace NIC with ‘6.2.1 Replacement procedure’ in ‘6.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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. 6.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. 1. Confirm physical location, segment number and bus number of target NIC.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.4 FC Card Hot Plugging c Confirm firmware version of target device. Select the device name of target FC card in left pane, and see [Port Information] in right pane. d Close OneCommand Manager. Case: Qlogic FC card a Open QConverge Console CLI, and identify target device from the bus number in step 2. 1. Select “1: Adapter Information” in [Main Menu].
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.4 FC Card Hot Plugging 2. Select “e1: FC Adapter Information” in [FC Adapter Information]. 3. Select the device of the same type of target FC card in [Adapter Information].
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.4 FC Card Hot Plugging 4. Confirm “PCI Bus Number” of PCI card, and look for the device which has same bus number you confirmed in step 1. b Confirm WWN and port number of target device. WWN is the information described as “WWPN:” of target FC card in [Adapter Information].
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.4 FC Card Hot Plugging c 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]. d Close QConverge Console CLI/GUI. 3. Open ETERNUS Multipath Manager and place all the devices to be replaced offline.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.4 FC Card Hot Plugging 4. Confirm target FC card by using Device Manager. Confirm FC card with step 2-a at ‘6.2.1 Replacement procedure’ in ‘6.2 Common Hot Plugging Procedure for PCI Express cards’. 5. Disable target FC card by using Device Manager. Disable FC card with step 2-a at ‘6.2.1 Replacement procedure’ in ‘6.2 Common Hot Plugging Procedure for PCI Express cards’. 6. Stop target FC card by using safely remove device from computer.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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]. (In case of [Disable], this work is not necessary) 6.4.2 FC card addition procedure Referring to 6.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.5 Hot Replacement Procedure for iSCSI 6.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 6.2.1 Replacement procedure in 6.2 Common Hot Plugging Procedure for PCI Express cards.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.5 Hot Replacement Procedure for iSCSI 6. Click the [Sessions] tab in the [Properties] window, and click the [MCS] button.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.5 Hot Replacement Procedure for iSCSI 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 2. If an IP address matches (192.168.3.150, in this example), this is the target connected to the device to be replaced. 8.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.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).
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.5 Hot Replacement Procedure for iSCSI 6.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 6.5.1 Confirming the incorporation of a card with MPD. Then, place the target device offline. For a multifunction card, it is necessary to place more than one device offline.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.5 Hot Replacement Procedure for iSCSI 6. Replace NIC by using MMB Maintenance Wizard. [FE’s work] Replace NIC with step 4 at 6.2.1 Replacement procedure in 6.2 Common Hot Plugging Procedure for PCI Express cards. Note In case of using SVagent, “Source:SVagent, ID: 25004 Error massage” is logged in SEL when replacing, it is no problem. 7. Set an IP address for the replacement device. Set the IP address and subnet mask recorded in step 2.
CHAPTER 6 PCI Express card Hot Maintenance in Windows 6.
CHAPTER 7 Backup and Restore 7.1 Backing Up and Restoring Configuration Information CHAPTER 7 Backup and Restore This chapter describes the backup and the restore operations required for restoring server data. 7.1 Backing Up and Restoring Configuration Information The PRIMEQUEST 2000 series has partitioning functions. These functions provide the user with partitions acting as independent servers. The user must configure the UEFI (Unified Extensible Firmware Interface) for each partition.
CHAPTER 7 Backup and Restore 7.1 Backing Up and Restoring Configuration Information FIGURE 7.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. The save destination dialog box of the browser appears. 2. Select the save destination path. Then, click the [OK] button. Download of the file begins.
CHAPTER 7 Backup and Restore 7.1 Backing Up and Restoring Configuration Information FIGURE 7.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. FIGURE 7.3 [Restore BIOS Configuration] window (partition selection) 2. Select the partition to restore. Then, click the [Restore] button. 7.1.
CHAPTER 7 Backup and Restore 7.1 Backing Up and Restoring Configuration Information FIGURE 7.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. The default MMB Configuration file name for the backup is as follows: MMB_(save date)_(MMB version).
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.1 Power On and Power Off the Whole System CHAPTER 8 Chapter System Startup/Shutdown and Power Control This section describes the startup, shutdown and the power control in PRIMEQUEST 2000 series. 8.1 Power On and Power Off the Whole System This section describes the power on and power off operations which are supported by the system. The power control of the whole system is operated from the [System Power Control] window of the MMB. FIGURE 8.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.2 Partition Power on and Power off 3. Wake On LAN (WOL) The partition can be power on with WOL. In this method, power on can be specified for the relevant partition containing the IOU. Notes - You can enable or disable WOL of LAN ports on IOU per IOU by MMB Web-UI. Default value of WOL is ‘disable’. If you use WOL of LAN port on IOU, set Onboard LAN Mode to ‘Enabled’ (WOL enable).
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.2 Partition Power on and Power off TABLE 8.2 Power on method and Power on unit Power off method MMB Web-UI, MMB CLI Schedule operation Power on unit: All partitions Power off is possible Power off is not possible Power on unit: Single partition Remarks Power off is possible Power off is not possible Automatic operation Notes In the following cases, confirm the details according to ‘10.2 Troubleshooting’.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.2 Partition Power on and Power off FIGURE 8.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” (C122-E177). 3. Click the [Apply] button after the [Power Control] of the partition to be powered on is set to [Power-On]. -> A confirmation dialog box appears. 4.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.2 Partition Power on and Power off FIGURE 8.3 [Power Control] Window For the details on the contents and setting items of the [Power Control] window, see ‘1.3.1 [Power Control] Window’ in “PRIMEQUEST 2000 series Tool Reference” (C122-E177). 8.2.8 Checking the Partition Power status by using the MMB This section describes the procedure by which power status of partition is confirmed. 1. Log in MMB Web-UI. -> The MMB Web-UI window appears. 2.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.2 Partition Power on and Power off FIGURE 8.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. - Log into the MMB Web-UI.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.3 Scheduled operations FIGURE 8.5 [Power Control] window The "#" column has the partition number. For details on the [Power Control] window, see ‘1.3.1 [Power Control] window’ in “PRIMEQUEST 2000 series Tool Reference” (C122-E177). 3. Set the ‘Power Control’ of the partition number to be powered off to [Power Off], and click the [Apply] button. -> The specified partition will be powered off.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.3 Scheduled operations - Time till the instruction reaches the operating system from the MMB - Time until the operating system shutdown is started and time until the start of the operating system shutdown is notified to the MMB - Even if the [Power on Delay] is set to 0 seconds, it may take 30 ~ 70 seconds from the time of turning on the power and starting, up to reset. For the scheduled setting, see ‘1.3.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.4 Automatic Partition Restart Conditions Menu Item Reset Scheduled operations Not supported NMI sadump Not supported Not supported Description Resets any partition. This reset is not followed by a reboot of the operating system. Issues an NMI interrupt for any partition. Instructs sadump for a partition. For details on setting for Windows shutdown, see ‘Appendix I Windows Shutdown Settings’. 8.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.4 Automatic Partition Restart Conditions FIGURE 8.6 [ASR (Automatic Server Restart) Control] window 2. Set the automatic restart conditions. The setting items of the [ASR Control] window are listed in the table below. TABLE 8.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.5 Power Restoration 8.5 Power Restoration In the PRIMEQUEST 2000 series, the system operations for power restoration can be set in the chassis unit. This can be set by MMB Web-UI. 8.5.1 Settings for Power Restoration When using a UPS, the following items can be set when a power failure is detected. The default is “Restore”. TABLE 8.
CHAPTER 8 Chapter System Startup/Shutdown and Power Control 8.6 Remote shutdown (Windows) - When target is work group environment The user name and password of the management terminal must match those of the target Windows to be shut down. - When the target is an Active Directory environment A user with administrative privileges for the Windows to be shut down must log in to the management terminal. 8.6.
CHAPTER 9 Configuration and Status Checking (Contents, Methods, and Procedures) 9.1 MMB Web-UI CHAPTER 9 Configuration and Status Checking (Contents, Methods, and Procedures) This chapter describes functions for checking the configuration and status of the PRIMEQUEST 2000 series server. The functions are broken down by firmware (or other software) and by tool. 9.1 MMB Web-UI The PRIMEQUEST 2000 series unifies server management via the MMB Web-UI.
CHAPTER 9 Configuration and Status Checking (Contents, Methods, and Procedures) 9.2 MMB CLI Function Reference sections in the PRIMEQUEST 2000 Series Tool Reference (C122-E177EN) 1.3.5 [Reserved SB Configuration] window 1.3.6 [Console Redirection Setup] window Sets a Reserved SB. The video redirection for each IPv4/IPv6 is set. Power Limiting of each partition is set. Displays the partition status and various information related to the partition.
CHAPTER 9 Configuration and Status Checking (Contents, Methods, and Procedures) 9.3 UEFI TABLE 9.2 Functions provided by the MMB CLI Function Sets information. Displays information. Updates firmware. Displays the version and update status of firmware. 9.3 Reference sections in the PRIMEQUEST 2000 Series Tool Reference (C122-E177EN) 2.2 Setting Commands 2.3 Display Commands 2.4.1 update ALL 2.4.2 show update_status UEFI The following lists the functions provided by the UEFI.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.1 Maintenance CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) This chapter describes the maintenance functions provided by the PRIMEQUEST 2000 series. It also describes the actions to take for any problems that occur. 10.1 Maintenance The PRIMEQUEST 2000 series supports hot maintenance of PSUs and fans. This enables maintenance of the system as it continues operating.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.1 Maintenance TABLE 10.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.1 Maintenance 2. Those who maintain it confirm all partitions that the PCI box belongs have stopped, and exchange PCI boxes (PEXU). Remarks It can be confirmed whether all partitions in the PCI box have stopped when Maintenance Wizard is used. Maintenance Wizard is recommended to use and to be exchanged (Only the charge maintenance member uses it). 10.1.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting FIGURE 10.1 REMCS linkage 10.2 Troubleshooting This section describes how to troubleshoot system problems. 10.2.1 Troubleshooting overview The following shows the basic procedure for troubleshooting.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting FIGURE 10.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.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting FIGURE 10.3 Label location No. (1) (2) Description Model name Serial number 10.2.2 Items to confirm before contacting a sales representative Before contacting your sales representative, confirm the following details. Print the sheet in Appendix L Failure Report Sheet, and enter the necessary information. - Items to confirm Model name and type of the main unit.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.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.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting FIGURE 10.5 System status display in the MMB Web-UI window No. Status in information area Description Displays the system status The MMB Web-UI window always displays the information area. [Status] in the information area displays the system status. The following table lists the Normal, Warning, and Error status indicators.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting FIGURE 10.6 Alarm E-Mail settings window Miscellaneous 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.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting FIGURE 10.7 System status display Click the icon displayed for an existing trouble spot to display a window showing the component status. If [Part Number] or [Serial Number] (the content or information area) in the MMB Web-UI window displays "Read Error," contact a field engineer or your sales representative.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting FIGURE 10.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. FIGURE 10.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting Finding out the partition error status Examine the partition error status in PRIMEQUEST 2400E and 2800E. 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.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.2 Troubleshooting 10.2.7 Problems related to the main unit or a PCI_Box This section describes problems related to the main unit or a PCI_Box. It also describes how to correct the problems. An LED on the main unit does not go on, or the orange LED is on. - Cause: The main unit may have failed. Corrective action: Contact your sales representative or a field engineer.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.3 Notes on Troubleshooting 10.2.9 Problems with partition operations - [Status] in the information area of the MMB Web-UI changes to "Error" when [Power Off], [Reset], or [Force Power Off] is executed on the partition or when the partition is shut down from the operating system. Also, the MMB Web-UI displays [Read Error] in [Part Number] and [Serial Number] of each component. - Cause: Hardware may have failed.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.4 Collecting Maintenance Data FIGURE 10.11 [System Event Log] window in PRIMEQUEST 2400E and 2800E FIGURE 10.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. Click the [Detail] button of an event to display details of the event.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.4 Collecting Maintenance Data Be sure to check with a field engineer before clearing events stored in the SEL. Remarks - If a problem occurs during operation, e-mail notification is sent. For details on how to specify whether to use e-mail notification and how to set the error level and e-mail destination for e-mail notification, see 1.5.11 [Alarm E-Mail] window in the PRIMEQUEST 2000 Series Tool Reference (C122-E177EN).
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.4 Collecting Maintenance Data FIGURE 10.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. To clear the specified conditions and return to the [System Event Log] window, click the [Cancel] button.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.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. If you select [Specified Time], you can enter the start time.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.4 Collecting Maintenance Data [Next] button: The window displays the next event according to the display order in the [System Event Log] window. TABLE 10.6 Setting and display items in the [System Event Log (Detail)] window Item Severity Date/Time Source Unit Event ID Description Part# Serial# Event Data Description Displays the severity of the event or error.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.4 Collecting Maintenance Data - The responsiveness of the mouse or keyboard is too slow. Performance deteriorates during system operation when the responsiveness of the mouse or keyboard is too slow. For details on memory dump file settings, see 10.4.3 Setting up the dump environment (Windows). To acquire memory dump, select [Partition] and then the [Power Control] window of the MMB Web-UI.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.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). *1 In a system using the Memory Mirror function, it is half the size of the mounted physical memory *2 The existing file is overwritten by default.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.4 Collecting Maintenance Data FIGURE 10.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]. 6. Click the [OK] button to close the [Startup and Recovery] dialog box. 7. Click the [OK] button to close the [System Properties] dialog box. 8. Restart the partition.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.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 Configure the paging file in the following procedure. 1. Log in to the server with Administrator privileges. 2.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.4 Collecting Maintenance Data FIGURE 10.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. Notes - No dump files and paging files can be stored at the iSCSI connection destination during internal disk boot and SAN (FC) boot.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.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. Configure the paging file in the following procedure. 1. Log in to the server with Administrator privileges. 2. Select [Control Panel] - [System]. The [System Properties] dialog box appears. 3.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.4 Collecting Maintenance Data FIGURE 10.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. Select a value in [Custom size]. Enter a value in [Initial size].
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.5 Configuring and Checking Log Information 10.4.5 sadump If a problem occurs in the partition which is operating on RHEL, memory dump is acquired as shown 10.4.4 Acquiring data for investigation (RHEL). However, acquiring memory dump sometimes fail. In such cases, memory dump is acquired by sadump in PRIMEQUEST 2400E and 2800E. PRIMEQUEST 2800B does not support sadump.
CHAPTER 10 Error Notification and Maintenance (Contents, Methods, and Procedures) 10.6 Firmware Updates - Operation log information - Physical inventory (including PCI_Boxes) information - System and partition configuration information - System and partition configuration file - Information on internal rack sensor definitions 10.6 Firmware Updates The PRIMEQUEST 2000 series server is configured with BIOS, BMC, and MMB firmware.
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.1.2 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. A.1 Function List The following lists the functions provided by the PRIMEQUEST 2000 series. A.1.1 Action TABLE A.
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.1.
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.1.
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.1.7 Security functions A.1.5 Redundancy functions TABLE A.
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.2.4 Hardware status display A.2 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.
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.2.
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 Power-on Power-off (shutdown) Reset NMI Forced power-off sadump MMB Web-UI Supported Supported Supported Supported Supported Supported Diagnosis mode selection at power on Scheduled operation Supported Supported MMB CLI UEFI Supported Supported Supported Supported Supported Supported A.2.9 OS boot settings TABLE A.
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.3 Management Network Specifications A.2.12 Maintenance TABLE A.19 Maintenance Function Batch firmware update MMB configuration information save and restore BIOS configuration information save and restore Maintenance wizard: Component Replacement Maintenance wizard: Maintenance mode setting and cancellation SB hot addition IOU hot addition A.
Appendix A Functions Provided by the PRIMEQUEST 2000 Series A.3 Management Network Specifications Component (A) Communi cation direction Duplex Compon ent (B) USER port CE port REMCS port Partition LAN port Protocol (Port No.) RMCP (UDP623 ) Port No. Protocol (Port No.) snmp (UDP161 ) snmp trap Port No. TABLE A.
Appendix B Physical Mounting Locations and Port Numbers B.1 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. B.1 Physical Mounting Locations of Components This section describes the physical mounting locations of components. FIGURE B.1 Physical mounting locations in the PRIMEQUEST 2400E (1) No.
Appendix B Physical Mounting Locations and Port Numbers B.1 Physical Mounting Locations of Components FIGURE B.2 Physical mounting locations in the PRIMEQUEST 2800E/2800B No. (1) (2) Explanation Front Rear FIGURE B.
Appendix B Physical Mounting Locations and Port Numbers B.2 Port Numbers FIGURE B.4 Physical mounting locations in the PCI_Box B.2 No. (1) Explanation Upper side (2) Front (3) (4) Right side Rear Port Numbers This section shows the numbering policy of each MMB and IOU port. Remarks The character strings used in numbering are the port numbers as viewed from firmware. These port numbers differ from the character strings in the port identification printed, stamped, or otherwise marked on units.
Appendix B Physical Mounting Locations and Port Numbers B.2 Port Numbers FIGURE B.6 IOU_1GbE port numbers FIGURE B.
Appendix C Lists of External Interfaces Physical C.2 List of External MMB Interfaces Appendix C Lists of External Interfaces Physical This appendix describes the external interfaces of the PRIMEQUEST2000 series. C.1 List of External System Interfaces The following lists the external system interfaces. TABLE C.
Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers 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 This appendix shows the correspondence between the physical locations and BUS numbers of built-in I/O in the PRIMEQUEST 2000 series server.
Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers D.
Appendix D Physical Locations and BUS Numbers of Built-in I/O, and PCI Slot Mounting Locations and Slot Numbers D.
Appendix E PRIMEQUEST 2000 Series Cabinets (Link) D.2 Correspondence between PCI Slot Mounting Locations and Slot Numbers Appendix E PRIMEQUEST 2000 Series Cabinets (Link) 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 (C122H004EN).
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. CSS LED and System Alarm LED indicate faulty status of entire system. Location LED indicates physical location of the system.
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. (*2) There is a CSS LED on an OPL, not a PSU. F.1.3 FANU The FANU comes equipped with the following LED. TABLE F.
Appendix F Status Checks with LEDs F.1. LED Type TABLE F.8 IOU LED LED type Power Alarm Location Color Green Orange Blue Function Indicates power state in an IOU. Indicates whether there is error or not in an IOU. Specifies an IOU. - Can be arbitrarily set to blink or turned off by the user. - Indicates the component undergoing maintenance when Maintenance Wizard is running. TABLE F.
Appendix F Status Checks with LEDs F.1. LED Type HDD/SSD status Rebuilding array HDD/SSD Access Blinking HDD/SSD Alarm Blinking periodically with 1 Hz Note When using SAS RAID card. 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. Location LED is used to specify the MMB. After the MMB firmware starts, the active MMB turns on the Active LED.
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. TABLE F.18 OPL LED LED type System Power CSS System Alarm System Location Color Green Function Indicates the power status of the system.
Appendix F Status Checks with LEDs F.2 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 AC Color Green DC CHECK Green Orange Function Indicates whether there is AC input to the individual PSU. Indicates the on/off status of each IO_PSU. Indicates whether there is an error in the IO_PSU. Note IO_PSU control IO_PSU control MMB-FW control TABLE F.24 IO_PSU status and LED display Status AC input to all IO_PSUs is off.
Appendix F Status Checks with LEDs F.2 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. FIGURE F.3 MMB LED mounting locations - The order of DU LEDs arranged as follows. FIGURE F.
Appendix F Status Checks with LEDs F.3 LED list F.3 LED list The following table lists the mounted LEDs for the PRIMEQUEST 2000 series. TABLE F.
Appendix F Status Checks with LEDs F.3 LED list TABLE F.
Appendix F Status Checks with LEDs F.3 LED list TABLE F.
Appendix F Status Checks with LEDs F.4 Button and switch F.4 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. - DU Attention Button Although there is the Attention button in DU, it is not used. Nothing happens if you push this button. - PCI_Box switch You can set 0 to 3 to PCI_Box as PCI_Box number by switch of PCI_Box.
Appendix G Component Mounting Conditions G.2 DIMM Appendix G Component Mounting Conditions This appendix describes the mounting conditions of components for the PRIMEQUEST 2000 series. G.1 CPU 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. (*1) - SB with two CPUs is allowed in single SB partition.
Appendix G Component Mounting Conditions G.
Appendix G Component Mounting Conditions G.2 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.
Appendix G Component Mounting Conditions G.2 DIMM TABLE G.7 DIMM mounting order at 1CPU/1SB (*1) CPU#0 0A0 0A3 0B0 0B3 0C0 0C3 0D0 0D3 DIMM 0A1 0A4 0B1 0B4 0C1 0C4 0D1 0D4 Slot# 0A2 0A5 0B2 0B5 0C2 0C5 0D2 0D5 1 3 3 2 2 4 4 Normal 1 (Perfor 5 5 7 7 6 6 8 8 mance) 9 9 11 11 10 10 12 12 1 1 1 1 2 2 2 2 Full or Partial 3 3 3 3 4 4 4 4 Mirror 5 5 5 5 6 6 6 6 1 1 3 3 2 2 4 4 Spare 1 1 3 3 2 2 4 4 1 1 3 3 2 2 4 4 (*1) See ‘TABLE G.
Appendix G Component Mounting Conditions G.2 DIMM TABLE G.
Appendix G Component Mounting Conditions G.2 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. TABLE G.
Appendix G Component Mounting Conditions G.2 DIMM TABLE G.
Appendix G Component Mounting Conditions G.2 DIMM TABLE G.
Appendix G Component Mounting Conditions G.8 NIC (Network Interface Card) G.3 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. G.4 Available internal I/O ports The following table lists the number of available internal I/O ports. TABLE G.
Appendix G Component Mounting Conditions G.8 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.
Appendix H Tree Structure of the MIB Provided with the PRIMEQUEST 2000 Series H.1 MIB Tree Structure Appendix H Tree Structure of the MIB Provided with the PRIMEQUEST 2000 Series This appendix describes the tree structure of the MIB provided with the PRIMEQUEST 2000 series. If SVS agent options are installed, MIB information of Agent can be acquired by SNMP service on the partition. For details on the MIB tree of SVS, see the MIB file of SVS. H.
Appendix H Tree Structure of the MIB Provided with the PRIMEQUEST 2000 Series H.2 MIB File Contents FIGURE H.1 MIB tree structure H.2 MIB File Contents The following table lists the contents of MIB files. TABLE H.1 MIB file contents MIB file MMBMIBs/ Purpose MMB-COM-MIB.txt Reference Partition operating system - MMB-ComTrapMIB.
Appendix I Windows Shutdown Settings I.1 Shutdown From MMB Web-UI Appendix I Windows Shutdown Settings This appendix describes how to set (arbitrarily) Windows to shut down. I.1 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.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.1 How to confirm firmware version of SAS RAID controller card Appendix J How to Confirm Firmware of SAS RAID Controller Card This section explains how to confirm the firmware of I/O device. J.1 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. Note Below figures are sample window.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.1 How to confirm firmware version of SAS RAID controller card FIGURE J.2 Boot Manager front page (2) 3. Select [EFI Internal Shell] and press [Enter] key. UEFI Shell starts up. FIGURE J.3 Boot Manager menu 4. Input below command on UEFI Shell. Shell> drivers 5. Driver list appears.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.1 How to confirm firmware version of SAS RAID controller card FIGURE J.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’. Driver list is shown by a page. 6. Check the number of UEFI driver and the number of LSI EFI SAS Driver.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.1 How to confirm firmware version of SAS RAID controller card FIGURE J.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> drvcfg -s 126 125 9. The window where you select either EFI WebBIOS menu or EFI CLI menu appears. Select [1 for EFI WebBIOS]. FIGURE J.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.1 How to confirm firmware version of SAS RAID controller card FIGURE J.8 [Adapter Selection] window of WebBIOS (1) 11. Select relevant RAID controller by [Adapter No.] radio button and click [Start] button. FIGURE J.9 [Adapter Selection] window of WebBIOS (2) 12. Click [Controller Properties] in [HOME] window of WebBIOS. FIGURE J.10 [HOME] window of WebBIOS 13. Check current version of firmware.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.2 How to confirm firmware version of SAS card FIGURE J.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. Note When click [Home] button, go back to [HOME] window. Confirming by ServerView RAID 1. Start the system and log in to the OS. 2.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.2 How to confirm firmware version of SAS card FIGURE J.13 Menu window 2. Select [LSI SAS2 MPT Controller SAS2008] from [Device List] in [Device Manager] window. FIGURE J.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 - EFI driver version: 04.30.03.00 3.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.2 How to confirm firmware version of SAS card FIGURE J.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. 5. Select [Controller Management] in [Configuration Options] window and press [Enter] key. FIGURE J.16 [Configuration Options] window 6.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card FIGURE J.17 [Controller Management] window 7. Check firmware version in [View Controller Properties] window. FIGURE J.18 [View Controller Properties] window Note Press [Esc] key sometimes and go back to top menu. J.3 How to confirm firmware version and UEFI driver version of FC card Below steps show how to confirm firmware version and UEFI driver version of FC card.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card J.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.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card FIGURE J.21 Boot Manager front page (1) Confirming UEFI driver version 1. Select [Boot Manager] and press [Enter] key. FIGURE J.22 Boot Manager front page (2) 2. [Boot Manager] window appears. Select [EFI Internal Shell] and press [Enter] key.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card FIGURE J.23 Boot Manager menu 3. UEFI Shell starts up. Input below command on EFI Shell. Shell> drivers 4. List of driver appears. FIGURE J.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).
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card FIGURE J.25 Driver list 5. Check UEFI driver version Check version of QLogic Fibre Channel Driver. Example: ‘00000224’ in version of UEFI driver means ‘2.24’. FIGURE J.26 Confirmation of UEFI driver version Note For a FC card made by Qlogic, you can confirm the firmware version only when a partition starts up. J.3.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card FIGURE J.27 Boot Manager front page (1) 2. Select [Device Manager] and press [Enter] key. FIGURE J.28 Boot Manager front page (2) 3. [Device Manager] window appears. Stating HBA setup utility 1. Select [Emulex Configuration Utility Ver: x.xxxx] in [Device Manager] window and press [Enter] key.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card FIGURE J.29 [Device Manager] window 2. [Emulex Configuration Utility] window appears. Select [Emulex Configuration Setup Utility] and press [Enter] key. FIGURE J.30 [Emulex configuration Utility] window 3. A list of HBA appears. Selecting HBA 1. Select HBA in [Adapter Selection] window and press [Enter] key.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card FIGURE J.31 [Adapter Selection] window (HBA list) 2. [Emulex Adapter Configuration Main Menu] window appears. FIGURE J.32 [Emulex Adapter Configuration Main Menu] window Confirming version of FC card. 1. Select [Display Adapter Info] in [Emulex Adapter Configuration Main Menu] window and press [Enter] key. 2. [Controller Information] window appears.
Appendix J How to Confirm Firmware of SAS RAID Controller Card J.3 How to confirm firmware version and UEFI driver version of FC card FIGURE J.33 [Controller Information] window Note Press [Esc] key sometimes and go back to top menu.
Appendix K Software (Link) J.3 How to confirm firmware version and UEFI driver version of FC card Appendix K Software (Link) 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).
Appendix L Failure Report Sheet L.1 Failure Report Sheet Appendix L Failure Report Sheet This appendix includes the failure report sheet. Use this sheet to report a failure. L.
Appendix M Information of PCI Express card L.1 Failure Report Sheet Appendix M Information of PCI Express card This appendix includes the information of PCI Express card. For components which cannot be identified by ‘Vendor ID’ and ‘Device ID’, see also ‘Subsystem ID’ and ‘Subsystem Vendor ID’. TABLE M.
