NEC EXP320R, EXP320S, Express5800/R320f-M4, Express5800/R320e-M4, Express5800/R320f-E4 Maintance Manual
...Page 1
Chapter 1 Maintenance
Chapter 2 Configuring and Upgrading the System
Chapter 3 Useful Features
Express5800/R320e-E4
Express5800/R320e-M4
Express5800/R320f-E4
Express5800/R320f-M4
EXP320R, EXP320S
Maintenance Guide (VMware)
NEC Express Server
Express5800 Series
30.103.02-104.01
December 2017
© NEC Corporation 2017
Page 2
Manuals
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
2
Manuals
Manuals for this product are provided as booklets ( ) and as electronic manuals ( ) in the
EXPRESSBUILDER DVD ( ).
Safety Precautions and Regulatory Notices
Describes points of caution to ensure the safe use of this server.
Read these cautions before using this server.
User’s Guide
Chapter 1: General Description Overviews, names, and functions of the server components
Chapter 2: Preparations Installation of additional options, connection of peripheral devices,
and suitable location for this server
Chapter 3: Setup System BIOS configurations and summary of EXPRESSBUILDER
Chapter 4: Appendix Specifications
Installation Guide
Chapter 1: Installing OS Installation of OS and drivers, and precautions for installation
Chapter 2: Installing Bundled
Software
Installation of bundled software, such as NEC ESMPRO
Chapter 3: Configuring the
Separate Log Server
Configure the log server using other than ftSys Management Appliance
Maintenance Guide
Chapter 1: Maintenance Server maintenance, error messages, and troubleshooting
Chapter 2: Configuring and
Upgrading the System
Changing hardware configuration, installing additional devices and
setting up management tools
Chapter 3: Useful Features The detail of system BIOS settings, SAS Configuration Utility, and
EXPRESSBUILDER
Other manuals
The detail of NEC ESMPRO, BMC Configuration, and other features.
PDF
PDF
PDF
PDF
PDF
PDF
EXPRESSBUILDER
Page 3
Contents
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
3
Contents
Manuals ................................................................................................................................................................. 2
Contents ................................................................................................................................................................ 3
Conventions Used in This Document .................................................................................................................... 7
Signs and symbols for safety ........................................................................................................................ 7
Notations used in the text .............................................................................................................................. 8
Optical disk drive ........................................................................................................................................... 8
Hard disk drive .............................................................................................................................................. 8
Removable media ......................................................................................................................................... 8
POST ........................................................................................................................................................... 9
BMC ........................................................................................................................................................... 9
Trademarks ......................................................................................................................................................... 10
License Notification ............................................................................................................................................. 11
Warnings and Additions to This Product and Document ...................................................................................... 14
Latest editions ............................................................................................................................................. 14
Safety notes ................................................................................................................................................ 14
Chapter 1 Maintenance .................................................................................................................................... 15
1. Relocation and Storage .................................................................................................................................. 17
2. Daily Maintenance .......................................................................................................................................... 19
2.1 Checking and Applying Updates .......................................................................................................... 19
2.2 Checking Alerts .................................................................................................................................... 19
2.3 Checking STATUS LED ....................................................................................................................... 20
2.4 Making Backup Copies ........................................................................................................................ 21
2.5 Cleaning ............................................................................................................................................... 21
2.5.1 Cleaning the server ................................................................................................................. 22
2.5.2 Cleaning Tape Drive ................................................................................................................ 22
2.5.3 Cleaning the Keyboard and Mouse ......................................................................................... 22
3. User Support ................................................................................................................................................... 23
3.1 Maintenance Services .......................................................................................................................... 23
3.2 Before Asking for Repair ...................................................................................................................... 23
4. Maintenance of Express5800/ft series ............................................................................................................ 24
4.1 ftsmaint Command ............................................................................................................................... 24
4.1.1 Component information ........................................................................................................... 24
4.1.2 Start/stop the component ........................................................................................................ 24
4.1.3 MTBF clear .............................................................................................................................. 25
4.1.4 Diagnostics .............................................................................................................................. 25
4.1.5 BMC firmware update .............................................................................................................. 25
4.1.6 BIOS update ............................................................................................................................ 25
4.2 Device Path Enumeration .................................................................................................................... 26
4.3 ftsmaint Examples ................................................................................................................................ 29
4.3.1 Displaying System Status ........................................................................................................ 29
4.3.2 Displaying the Status of a Single System Component ............................................................ 31
4.3.3 Bringing System Components Down and Up .......................................................................... 32
4.3.4 Stopping and Starting the Internal Disk Controller .................................................................. 33
4.3.5 Diagnostics .............................................................................................................................. 33
4.3.6 Updating BMC firmware .......................................................................................................... 34
4.3.7 Updating BIOS ........................................................................................................................ 36
Page 4
Contents
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
4
4.4 Disabling Auto Reinstallation of CPU Module ...................................................................................... 38
4.4.1 Disabling auto reinstallation of CPU module ........................................................................... 38
4.4.2 Scheduling for auto reinstallation of CPU module ................................................................... 39
5. Checking the Duplicating Operation of Modules ............................................................................................. 40
5.1 Evaluate Start and Stop of I/O Modules ............................................................................................... 40
5.2 Evaluate Start and Stop of CPU Modules ............................................................................................ 43
6. Error Messages .............................................................................................................................................. 45
6.1 Error Messages by LED Indication ....................................................................................................... 46
6.2 POST Error Message ........................................................................................................................... 53
7. Collecting Failure Information ......................................................................................................................... 60
7.1 Collection of Collect Logs .................................................................................................................... 60
7.2 Collection of System Information ......................................................................................................... 61
7.3 Collecting Memory Dump ..................................................................................................................... 62
8. Troubleshooting .............................................................................................................................................. 64
8.1 Problems When Turning on the Server ................................................................................................ 65
8.2 Problems When Starting EXPRESSBUILDER ..................................................................................... 66
8.3 Problems When Installing VMware ESXi and the ft control software ................................................... 67
8.4 Problems When starting ESXi .............................................................................................................. 68
8.5 Problems When Occurring Failures ..................................................................................................... 69
8.6 Problems with Internal Devices and Other Hardware .......................................................................... 70
8.7 Problems with System Operation ......................................................................................................... 71
8.8 Problems When Starting EXPRESSBUILDER on Windows ................................................................ 72
8.9 Problems with Bundled Software ......................................................................................................... 73
8.10 Problems with Optical Disk Drive and Flash FDD ............................................................................. 76
9. Resetting and Clearing the Server .................................................................................................................. 77
9.1 Software Reset .................................................................................................................................... 77
9.2 Forced Shutdown ................................................................................................................................. 77
9.3 Clearing BIOS Settings (CMOS Memory) ............................................................................................ 78
10. System Diagnostics ...................................................................................................................................... 82
10.1 Test Items .......................................................................................................................................... 82
10.2 Startup and Exit of System Diagnostics ............................................................................................. 82
11. Offline Tools .................................................................................................................................................. 85
11.1 Starting Offline Tools ......................................................................................................................... 85
11.2 Functions of Offline Tools .................................................................................................................. 86
12. Precautions for Operation............................................................................................................................. 87
Chapter 2 Configuring and Upgrading the System ........................................................................................... 88
1. ftSys Management Appliance ......................................................................................................................... 89
1.1 Overview .............................................................................................................................................. 89
1.2 Steps for Accessing ftSys Management Appliance .............................................................................. 90
1.3 Precautions for Using ftSys Management Appliance ........................................................................... 90
2. Hard Disk Drive Operations ............................................................................................................................ 92
2.1 Operable disk configuration ................................................................................................................. 92
2.2 esxcli Command Syntax ...................................................................................................................... 95
2.3 Confirm Hard Disk Drives status .......................................................................................................... 96
2.4 Replacing a hard disk drive .................................................................................................................. 97
2.4.1 Identifying a failing disk ........................................................................................................... 97
2.4.2 Restoring the redundant configuration manually ..................................................................... 98
2.4.3 Reducing resync time ............................................................................................................ 100
2.5 Adding Hard Disk Drives .................................................................................................................... 101
2.5.1 Inserting Additional Hard Disk Drives .................................................................................... 101
2.5.2 Configuring a RAID Device ................................................................................................... 101
2.5.3 Creating and Mounting a Filesystem ..................................................................................... 103
Page 5
Contents
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
5
3. Duplex LAN Configuration ............................................................................................................................ 106
3.1 Functional Overview .......................................................................................................................... 106
3.2 Operable Network Configuration ........................................................................................................ 106
4. Miscellaneous Configuration ......................................................................................................................... 108
4.1 Changing Datastore Name ................................................................................................................ 108
5. Installing and Replacing Optional Devices .................................................................................................... 109
5.1 Precautions ........................................................................................................................................ 109
5.1.1 Safety precautions ................................................................................................................ 109
5.1.2 Verification before installing optional devices ........................................................................ 110
5.1.3 Basics of Installation, Removal, and replacement ................................................................. 111
5.2 Optional Devices That Can Be Installed, Removed, or Replaced ...................................................... 112
5.3 Installation, Removal and Replacement of 2.5-inch Hard Disk Drive ................................................. 113
5.3.1 Installation ............................................................................................................................. 114
5.3.2 Removal ................................................................................................................................ 116
5.3.3 Replacement ......................................................................................................................... 118
5.4 Removing and Installing CPU/IO Module ........................................................................................... 119
5.4.1 Removal ................................................................................................................................ 120
5.4.2 Installation ............................................................................................................................. 123
5.5 Installing, Removing and Replacing DIMM ........................................................................................ 125
5.5.1 Installation ............................................................................................................................. 127
5.5.2 Removal ................................................................................................................................ 129
5.5.3 Replacement ......................................................................................................................... 131
5.6 Installing, Removing and Replacing Processor (CPU) ....................................................................... 132
5.6.1 Installation ............................................................................................................................. 133
5.6.2 Removal ................................................................................................................................ 137
5.6.3 Replacement ......................................................................................................................... 137
5.7 Installing, Removing and Replacing PCI Card ................................................................................... 138
5.7.1 Precautions ........................................................................................................................... 138
5.7.2 Installation ............................................................................................................................. 140
5.7.3 Removal ................................................................................................................................ 144
5.7.4 Replacement ......................................................................................................................... 145
5.7.5 Setup of Optional PCI Board ................................................................................................. 146
Chapter 3 Useful Features ............................................................................................................................. 147
1. System BIOS ................................................................................................................................................ 148
1.1 Starting SETUP .................................................................................................................................. 148
1.2 Parameter Descriptions ..................................................................................................................... 148
1.2.1 Main ...................................................................................................................................... 149
1.2.2 Advanced .............................................................................................................................. 150
1.2.3 Security ................................................................................................................................. 171
1.2.4 Server .................................................................................................................................... 173
1.2.5 Boot ....................................................................................................................................... 179
1.2.6 Save & Exit ............................................................................................................................ 181
2. BMC Configuration ....................................................................................................................................... 182
2.1 Overview ............................................................................................................................................ 182
2.1.1 Offline Tools ........................................................................................................................... 182
2.2 Activating BMC Configuration ............................................................................................................ 183
2.3 Main Menu of BMC Configuration ...................................................................................................... 184
2.4 Setting BMC Configuration ................................................................................................................ 185
2.4.1 Network ................................................................................................................................. 186
2.4.2 User Management ................................................................................................................. 189
2.4.3 Mail Alert ............................................................................................................................... 191
2.4.4 SNMP Alert ............................................................................................................................ 193
2.4.5 System Operation ................................................................................................................. 194
2.4.6 Miscellaneous ....................................................................................................................... 195
2.5 BMC Initialization ............................................................................................................................... 196
2.6 BMC Reset......................................................................................................................................... 196
3. SAS Configuration Utility ............................................................................................................................... 197
3.1 Starting the SAS Configuration utility ................................................................................................. 197
Page 6
Contents
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
6
3.2 Quitting the SAS Configuration Utility ................................................................................................ 198
3.3 Physical Formatting of the Hard Disk Drive ....................................................................................... 199
4. Flash FDD ..................................................................................................................................................... 202
4.1 Notes on Using Flash FDD ................................................................................................................ 203
4.1.1 Compensation for recorded data ........................................................................................... 203
4.1.2 Handling Flash FDD .............................................................................................................. 203
4.1.3 Use with EXPRESSBUILDER ............................................................................................... 203
5. Details of EXPRESSBUILDER ..................................................................................................................... 204
5.1 Starting EXPRESSBUILDER ............................................................................................................. 204
5.2 Menu of EXPRESSBUILDER............................................................................................................. 204
5.3 Utilities Provided by EXPRESSBUILDER .......................................................................................... 206
6. EXPRESSSCOPE Engine 3 ......................................................................................................................... 207
7. NEC ESMPRO .............................................................................................................................................. 208
7.1 NEC ESMPRO Agent ......................................................................................................................... 208
7.2 NEC ESMPRO Manager .................................................................................................................... 208
7.2.1 Monitoring the ESXi status of the ft server (ESXi 6.5 or later) ............................................... 208
Glossary ............................................................................................................................................................ 210
Revision Record ................................................................................................................................................ 211
Page 7
Conventions Used in This Document
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
7
Conventions Used in This Document
Signs and symbols for safety
WARNING and CAUTION are used in this guide as following meaning.
WARNING
Indicates there is a risk of death or serious personal injury
CAUTION
Indicates there is a risk of burns, other personal injury, or property damage
Precautions and notices against hazards are presented with one of the following three symbols. The individual
symbols are defined as follows:
Attention This symbol indicates the presence of a hazard if
the instruction is ignored.
An image in the symbol illustrates the hazard type.
(Example)
Prohibited
Action
This symbol indicates prohibited actions. An image
in the symbol illustrates a particular prohibited
action.
(Example)
(Do not disassemble)
Mandatory
Action
This symbol indicates mandatory actions. An
image in the symbol illustrates a mandatory action
to avoid a particular hazard.
(Example)
(Disconnect a plug)
(Example in this guide)
WARNING
Use only the specified outlet
Use a grounded outlet with the specified voltage. Use of an improper power source
may cause a fire or a power leak.
Symbol to draw
attention
Description of a warning Term indicating a degree of danger
(Electric shock risk)
Page 8
Conventions Used in This Document
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
8
Notations used in the text
In addition to safety-related symbols urging caution, three other types of notations are used in this document.
These notations have the following meanings.
Important
Indicates critical items that must be followed when handling hardware or operating software. If
the procedures described are not followed, hardware failure, data loss, and other serious
malfunctions could occur.
Note
Indicates items that must be confirmed when handling hardware or operating software.
Tips
Indicates information that is helpful to keep in mind when using this server.
Optical disk drive
This server is equipped with one of the following drives. These drives are referred to as optical disk drive in this
document.
DVD Super MULTI drive
Hard disk drive
Unless otherwise stated, hard disk drive described in this document refers to both of the following.
Hard disk drive (HDD)
Solid state drive (SSD)
Removable media
Unless otherwise stated, removable media described in this document refers to both of the following.
USB flash drive
Flash FDD
Page 9
Conventions Used in This Document
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
9
POST
POST described in this document refers to the following.
Power On Self-Test
BMC
BMC described in this document refers to the following.
Baseboard Management Controller
Page 10
Trademarks
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
10
Trademarks
EXPRESSSCOPE is a registered trademark of NEC Corporation
Microsoft, Windows, and Windows Server are registered trademarks or trademarks of Microsoft Corporation in the United States and
other countries.
Intel, and Xeon are registered trademarks of Intel Corporation of the United States.
AT is a registered trademark of International Business Machines Corporation of the United States and other countries.
Adobe, the Adobe logo, and Acrobat are trademarks of Adobe Systems Incorporated.
PCI Express is a trademark of Peripheral Component Interconnect Special Interest Group.
VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents.
VMware is a registered trademark or trademark of VMware, Inc in the United States and/or other jurisdictions.
U.S. Patent Numbers: 5,732,212/5,937,176/6,633,905/6,681,250/6,701,380 and "Other Patents Pending"
Taiwanese Patent Number: 173784
European Patent Number: 0 740 811
All other product, brand, or trade names used in this publication are the trademarks or registered trademarks of their respective
trademark owners.
Page 11
License Notification
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
11
License Notification
Open source software of following license is included in the part of this product (system BIOS).
EDK/EDKII
UEFI Network Stack II and iSCSI
Crypto package using WPA Supplicant
Open source software of following license is included in the part of this product (Off-line Tools).
EDK/EDKII
EDK/EDKII
BSD License from Intel
Copyright (c) 2012, Intel Corporation
All rights reserved.
Copyright (c) 2004, Intel Corporation
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
Neither the name of the Intel Corporation nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Page 12
License Notification
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
12
UEFI NETWORK STACK II and iSCSI
OpenSSL License
-------
Copyright (c) 1998-2011 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following
acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit.
(http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products
derived from this software without prior written permission. For written permission, please contact
openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their
names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL
PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
CRYPTO PACKAGE USING WPA SUPPLICANT
WPA Supplicant
-------
Copyright (c) 2003-2012, Jouni Malinen <j@w1.fi> and contributors
All Rights Reserved.
This program is licensed under the BSD license (the one with advertisement clause removed).
If you are submitting changes to the project, please see CONTRIBUTIONS file for more instructions.
License
-------
This software may be distributed, used, and modified under the terms of
BSD license:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name(s) of the above-listed copyright holder(s) nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written permission.
Page 13
License Notification
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
13
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Page 14
Warnings and Additions to This Product and Document
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
14
Warnings and Additions to This Product and Document
1. Unauthorized reproduction of the contents of this document, in part or in its entirety, is prohibited.
2. This document is subject to change at any time without notice.
3. Do not make copies or alter the document content without permission from NEC Corporation.
4. If you have any concerns, or discover errors or omissions in this document, contact your sales
representative.
5. Regardless of article 4, NEC Corporation assumes no responsibility for effects resulting from your
operations.
6. The sample values used in this document are not the actual values.
Keep this document for future use.
Latest editions
This document was created based on the information available at the time of its creation. The screen images,
messages and procedures are subject to change without notice. Substitute as appropriate when content has
been modified.
The most recent version of the guide, as well as other related documents, is also available for download from
the following website.
http://www.nec.com/
Safety notes
To use this server safely, read thoroughly Safety Precautions and Regulatory Notices that comes with your
server.
Page 15
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
15
NEC Express5800 Series
Express5800/R320e-E4, R320e-M4,
R320f-E4, R320f-M4
Maintenance
This chapter explains maintenance of server, and what actions are to be taken in case of trouble when operating
this server.
1. Relocation and Storage
Describes how to relocate and store this server.
2. Daily Maintenance
Describes what you must confirm for daily use, how to manage files, and how to clean the server.
3 User Support
Describes various services on this product.
4. Maintenance of Express5800/ft series
Describes how to start, stop, diagnose each components of ft server, and how to update firmware.
5. Checking the Duplicating Operation of Modules
Describes how to check if the system runs properly after system installation or reinstallation.
6, Error Messages
Describes error messages and actions to be taken at occurrence of an error.
7. Collecting Failure Information
Describes how to collect information about the location where a failure occurred and its cause when the
server malfunctions. Refer to this section in case of a failure.
8. Troubleshooting
Describes how to identify the causes of problems and what actions are to be taken to address them. Refer to
this section when you suspect a failure.
9. Resetting and Clearing the Server
Describes how to reset or clear the server. Refer to this section when the server is not working or when you
want to restore BIOS settings to the factory settings.
Page 16
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
16
10. System Diagnostics
Describes the system diagnostics of this server.
11. Offline Tools
Describes tools for preventive maintenance of this product.
12. Precautions for Operation
Page 17
1. Relocation and Storage
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
17
Chapter 1 Maintenance
1.
Relocation and Storage
Follow the steps below if you want to relocate or store this server.
WARNING
Be sure to observe the following precautions to use the server safety. Failure to
observe the precautions may cause death or serious injury. For details, see
Safety Precautions and Regulatory Notices.
Do not disassemble, repair, or alter the server.
Do not remove the lithium battery, NiMH, or Li-ion battery.
Disconnect the power plug before installing or removing the server.
CAUTION
Be sure to observe the following precautions to use the server safely. Failure to
observe the precautions may cause burns, injury, and property damage. For
details, see Safety Precautions and Regulatory Notices.
Make sure to complete installation.
Do not get your fingers caught.
Be careful of handling internal components that may be at high
temperatures.
Note
If the server needs to be relocated/stored due to a change in the floor layout to
a great extent, contact your service representative.
If the server has hard disk drives, move the server while being careful not to
damage the drive.
When storing the server, monitor the environmental conditions of the storage
area (temperature: 10C to 55C, humidity: 20% to 80%). (No dew
condensation is permitted)
Tips Make backup copies of important data stored in the hard disk drive.
1. Remove the media from the optical disk drive.
2. Power off the server (POWER LED is unit).
3. Unplug the power cord of the server from the power outlet.
4. Disconnect all the cables from the server.
5. Remove CPU/IO modules and 4U frame.
6. Carry the removed CPU/IO modules and 4U frame separately.
7. Pack the server securely to protect from damage, shock, and vibration.
Page 18
1. Relocation and Storage
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
18
Chapter 1 Maintenance
Important If this server and internal optional devices are suddenly moved from a cold
place to a warm place, condensation will occur and cause malfunctions and
failures when these are used in such state. Wait for a sufficient period of time
before using the server and other components in the operating environment.
Note Check and adjust the system clock before operating after relocating or storing the
server.
Page 19
2. Daily Maintenance
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
19
Chapter 1 Maintenance
2.
Daily Maintenance
To use this server under top conditions at all times, periodically check and perform maintenance as follows. If
abnormalities are found, ask your sales representative, avoiding impossible operation.
2.1
Checking and Applying Updates
Express5800 Series posts update information for BIOS, FW (firmware), driver, and others of the server and
peripheral devices on our website. We recommend that the latest update always be applied for stable system.
NEC corporate site: http://www.nec.com/
[Support & Downloads]
Tips
Download and apply the latest update yourself.
NEC recommends that you back up data for a rainy day before applying the
latest update.
2.2
Checking Alerts
Use NEC ESMPRO Manager (for Windows) to constantly verify that no abnormalities are detected on the
monitored server and that no alerts have been issued.
Example image of NEC ESMPRO Manager
NEC ESMPRO Manager
A
lertViewer
Page 20
2. Daily Maintenance
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
20
Chapter 1 Maintenance
2.3
Checking STATUS LED
Check LEDs located at front of the server for any abnormalities after the server is powered on or before shutting
down the server and the server is powered off. Check LEDs for any abnormalities also while the server is
running.
Check LED indication when:
Power on the server and while the server is running.
Before shutting down the server.
LEDs to be checked:
LEDs located at front of the server
LEDs on hard disk drives installed in 2.5-inch hard disk drive bay
If the indicator shows the server abnormality, contact your salses representative.
For the functions and descriptions of the LED, refer to Chapter 1 (6.1 Error Messages by LED Indication).
Slot 0 Slot 2 Slot 4 Slot 6
Slot 1 Slot 3 Slot 5 Slot 7
Slot 0 Slot 2 Slot 4 Slot 6
Slot 1 Slot 3 Slot 5 Slot 7
DISK ACCESS LED
System POWER LED
System FAULT LED
System FT LED
Page 21
2. Daily Maintenance
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
21
Chapter 1 Maintenance
2.4
Making Backup Copies
NEC recommends you make backup copies of your valuable data stored in hard disks of the server on a regular
basis. For backup storage devices suitable for the server and backup tools, consult with your sales agent.
When you have changed the hardware configuration or BIOS configuration, make a backup copy of the system
information according to Chapter 1 (1.14 Backing Up System Information) in Installation Guide.
2.5
Cleaning
Regularly clean the server to keep it in good condition.
WARNING
Be sure to observe the following precautions to use the server safety. Failure to
observe the precautions may cause death or serious injury. For details, see
Safety Precautions and Regulatory Notices.
Do not disassemble, repair, or alter the server.
Disconnect the power plug before cleaning the server.
Page 22
2. Daily Maintenance
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
22
Chapter 1 Maintenance
2.5.1
Cleaning the server
For daily cleaning, wipe the external surfaces of the server with a dry soft cloth. Follow the procedure below if
stains remain on the surfaces:
Important
To avoid altering the material and color of the server, do not use volatile solvents
such as thinner or benzene to clean the server.
The power receptacle, the cables, the connectors on the rear panel of server, and
the inside of the server must be kept dry. Do not moisten them with water.
1. Power off the server.
1. Make sure that the server is powered off.
2. Unplug the power cord of the server from a power outlet.
2. Clean the power plug.
Wipe off dust from the power cord plug with a dry cloth.
3. Clean the server.
1. Soak a soft cloth in neutral detergent that is diluted with cold or warm water, and squeeze it firmly.
2. Rub off stains on the server with the cloth prepared in Step 1.
3. Soak a soft cloth in water, squeeze it firmly and wipe the server with it once again.
4. Wipe the server with a dry cloth.
4. Clean the rear panel of the server.
Wipe off dust from the fan exhaust opening on the rear of the server with a dry cloth.
2.5.2
Cleaning Tape Drive
A dirty tape drive head causes unsuccessful file backup and damages the tape cartridge. Periodically clean the
tape drive with the designated cleaning tape.
For the cleaning interval and method, the estimated usable period and lifetime of the tape cartridge, refer to the
instructions attached to the tape drive.
2.5.3
Cleaning the Keyboard and Mouse
Check that the entire system including the server and peripheral devices is powered off (POWER LED is unlit),
and then wipe the surface of the keyboard with a dry cloth.
If an optical sensor of the mouse is dusty, it cannot work normally. Wipe the optical sensor with a dry cloth to
remove any dirt or dust.
Page 23
3. User Support
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
23
Chapter 1 Maintenance
3.
User Support
Before getting after-sales service, check the contents of the warranty and service.
3.1
Maintenance Services
Service representatives from NEC subsidiary companies or companies authorized by NEC provide
maintenance services. For the services, contact your sales representative.
3.2
Before Asking for Repair
If you think that a failure occurred, follow the steps below:
1. Check if the power cord and cables to other products are properly connected.
2. Check LED indications and alarm messages on display unit. Refer to Chapter 1 (6. Error Messages).
3. Refer to Chapter 1 (8. Troubleshooting). If you find a symptom similar to your problem, take the action
as instructed.
4. Confirm that the required software has been properly installed.
5. Scan for viruses using a commercial Antivirus Software.
If the problem persists after taking the measures above, contact your sales representative. Take notes on LED
indications and the display on the screen at the failure, which will be useful information for the repair.
Page 24
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
24
Chapter 1 Maintenance
4.
Maintenance of Express5800/ft series
For Express5800/ft server maintenance tasks, use the /opt/ft/bin/ftsmaint command on console of ftSys
Management Appliance. For information about using the ftsmaint command and using device path enumeration
to manage specific devices in your system, see the following sections:
4.1 ftsmaint Command
4.2 Device Path Enumeration
4.3 ftsmaint Examples
4.1
ftsmaint Command
4.1.1
Component information
ftsmaint ls path
This command displays the status of the hardware specified by the enumerated path. Specifying a path displays
a detailed status of the hardware at that path.
Omitting the path argument displays a less-detailed table of all fault-tolerant devices on the system. Refer to
Chapter 1 (4.2 Device Path Enumeration) for more information.
Output from ftsmaint ls path reflects what the management software reports about the state of a given
component. Because of system latency, this may not reflect the immediate state of the device.
To verify the actual state of the device, check the state of its LED.
Note
Running this command may fail if the necessary process does not run immediately after the
system startup. In this case, wait for a while (several minutes or so), and try again.
4.1.2
Start/stop the component
ftsmaint bringDown path
This command removes from service the CPU module, I/O module, or internal disk specified by path. No other
devices are supported. When you bring down a device, the effect on the system is the same as physically
removing it.
Important
When manually bringing down a component, it is possible that a whole CPU/IO
module will be taken out of service. Be careful to bring down a component only
when the system is fully duplexed.
Note
This command is valid only for CPU module, I/O module, and internal hard disk drives.
Page 25
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
25
Chapter 1 Maintenance
ftsmaint bringUp path
This command brings into service the CPU module, I/O module, or internal disk specified by path. No other
devices are supported.
Tips
Running the ftsmaint bringUp command on a CPU module degrades system performance
and halts network communications for up to a minute.
Note
This command is valid only for CPU module, I/O module, and internal hard disk drives.
4.1.3
MTBF clear
ftsmaint clearMtbf path
This command clears the MTBF value of the CPU module, I/O module, or I/O module slot specified by path.
Important
Do not use this feature to retain a faulty or degraded device in service.
4.1.4
Diagnostics
ftsmaint runDiag path
This command starts diagnostics on the CPU module or I/O module specified by path.
4.1.5
BMC firmware update
ftsmaint burnBmcs fw_file
This command updates the BMC firmware using BMC firmware file specified by fw_file argument.
Important
Shutdown the guest OS except for ftSys Management Appliance.
Make sure that I/O modules and BMC are duplicated before starting update of
BMC firmware.
Do not operate the machine and power supply unit while the firmware is
updated. The firmware is destroyed and modules may need to be replaced.
4.1.6
BIOS update
ftsmaint burnProm fw_file path
This command updates BIOS of CPU module specified by path argument using the BIOS firmware file
specified by fw_file argument.
Important
Shutdown the guest OS except for ftSys Management Appliance.
Make sure that CPU modules are duplicated before starting update of BIOS.
Do not operate the machine and power supply unit while the firmware is
updated. The firmware is destroyed and modules may need to be replaced.
Page 26
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
26
Chapter 1 Maintenance
4.2
Device Path Enumeration
Some subsystems and components of the server system are addressable by device path IDs. Device path IDs
uniquely identify the devices in the server system.
Table 1 lists the device path IDs for devices in the server system. In Table 1, IDs in the format **:nn.n (for
example, 7c:00.0) indicate PCI bus, slot, and function.
These numbers may change as a result of normal system events. Therefore, devices in your system may
appear with different IDs in command output from ftsmaint and other commands. The values for such devices
are provided here as representative sample data only.
Table 1. Device Paths of the Server Devices
Device
Path
CPU/IO Module 0 CPU/IO Module 1
CPU Module 0 1
DIMMs (addressed by slot) 0/1 - 0/16 1/1 - 1/16
Processors 0/21,0/22 1/21,1/22
Temperature #n sensor 0/130 1/130
Fan #n sensors 0/140 - 0/144 1/140 - 1/144
I/O Module 10 11
PCI Slot devices (in slots on motherboards) 10/1,10/2 11/1,11/2
PCI Slot devices (in optional high-profile PCIe slots) 10/3,10/4 11/3,11/4
Internal Disk controller 10/5 11/5
Network controller
Ethernet controller: Intel® Corporation I350 Gigabit
network connection
Network interface
10/6
07:00.0, 07:00.1
vmnic_100600
vmnic_100601
11/ 6
41:00.0, 41:00.1
vmnic_110600
vmnic_110601
Display controller
VGA compatible controller: Matrox® Graphics, Inc.
MGA G200e
10/7
2c:00.0
11/7
66:00.0
Serial bus controllers
USB controller: Intel Corporation DH82029
10/8
2b:00.0, 2b:00.1
11/8
65:00.0, 65:00.1
Bridge
10/10, 10/11 11/10, 10/11
Network controller
Ethernet controller: Intel Corporation Ethernet
Controller 10-Gigabit X540-AT2
10/12
9e:00.0, 9e:00.1
vmnic_101200
vmnic_101201
11/12
d8:00.0, d8:00.1
vmnic_111200
vmnic_111201
Internal disk controller
Hard disk drive 1-8
10/40
10/40/1 - 10/40/8
11/40
11/40/1 - 11/40/8
2xPCIe 10/70 11/70
Baseboard Management Controller 10/120 11/120
Page 27
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
27
Chapter 1 Maintenance
Figure 1 and Figure 2 show the locations of the major enumerated devices.
Figure 1. Locations of Major Enumerated Devices (Front View)
Callout Device Device ID Physical Label
0 CPU/IO Module 0 (CPU-0, I/O-10) 0
1 Internal hard disk drive 1 10/40/1 0
2 Internal hard disk drive 2 10/40/2 1
3 Internal hard disk drive 3 10/40/3 2
4 Internal hard disk drive 4 10/40/4 3
5 Internal hard disk drive 5 10/40/5 4
6 Internal hard disk drive 6 10/40/6 5
7 Internal hard disk drive 7 10/40/7 6
8 Internal hard disk drive 8 10/40/8 7
9 CPU/IO Module 1 (CPU-1, I/O-11) 1
10 Internal hard disk drive 1 11/40/1 0
11 Internal hard disk drive 2 11/40/2 1
12 Internal hard disk drive 3 11/40/3 2
13 Internal hard disk drive 4 11/40/4 3
14 Internal hard disk drive 5 11/40/5 4
15 Internal hard disk drive 6 11/40/6 5
16 Internal hard disk drive 7 11/40/7 6
17 Internal hard disk drive 8 11/40/8 7
0 1 2 3 4 5 6 7 8
9 11 10 13 12 15 14 17 16
Page 28
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
28
Chapter 1 Maintenance
Figure 2. Locations of Major Enumerated Devices (Rear View)
Callout Device Device ID
1 I/O module 0 PCI Slot 1 10/1
2 I/O module 0 PCI Slot 2 10/2
3 I/O module 0 PCI Slot 3 10/3
4 I/O module 0 PCI Slot 4 10/4
5 I/O module 1 PCI Slot 1 11/1
6 I/O module 1 PCI Slot 2 11/2
7 I/O module 1 PCI Slot 3 11/3
8 I/O module 1 PCI Slot 4 11/4
3 4 1 2
7 8 5 6
Page 29
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
29
Chapter 1 Maintenance
4.3
ftsmaint Examples
The following sections provide examples of how to use the ftsmaint command.
4.3.1
Displaying System Status
To display the status of the fault-tolerant devices and subsystems in your server system, use the following
command:
# /opt/ft/bin/ftsmaint ls
Example 1 shows typical output for this command.
Example 1. Displaying System Status with the ftsmaint Command
H/W Path Description State OPState FRev Fct
=================================================================================
0 Combined CPU/IO ONLINE DUPLEX * 0
0/1 DIMM ONLINE ONLINE - 0/1/130 DIMM 1 Temp#0 Sensor - NORMAL - 0/2 DIMM MISSING EMPTY - ...
0/21 Intel(R) Xeon(R) CPU E5-2671 v4 @ 2.30GHz ONLINE ONLINE - ...
0/130 Baseboard Temp#0 Sensor - NORMAL - 0/140 Baseboard Fan0#0 Sensor - NORMAL - ...
1 Combined CPU/IO ONLINE DUPLEX * 0
1/1 DIMM ONLINE ONLINE - 1/1/130 DIMM 1 Temp#1 Sensor - NORMAL - 1/2 DIMM MISSING EMPTY - ...
1/21 Intel(R) Xeon(R) CPU E5-2671 v4 @ 2.30GHz ONLINE ONLINE - ...
1/130 Baseboard Temp#1 Sensor - NORMAL - 1/140 Baseboard Fan0#1 Sensor - NORMAL - 1/141 Baseboard Fan1#1 Sensor - NORMAL - ...
10 Combined CPU/IO ONLINE DUPLEX - 0
10/1 Network Ctlr ONLINE DUPLEX - 0
0000:09:00.0 Ethernet controller: Intel Corporation Et ONLINE DUPLEX - vmnic_100100 Network Interface ONLINE DUPLEX - -
10/2 - MISSING EMPTY - 10/3 Fibre Channel Serial Bus Ctlr ONLINE DUPLEX - 0
0000:7d:00.0 Fibre Channel: QLogic Corp. ISP8324-based ONLINE DUPLEX - 10/4 - MISSING EMPTY - 10/5 Mass Storage Ctlr ONLINE DUPLEX - 0
0000:1a:00.0 Mass storage controller: LSI Logic / Symb ONLINE DUPLEX - 10/6 Network Ctlr ONLINE DUPLEX - 0
0000:07:00.0 Ethernet controller: Intel Corporation I3 ONLINE DUPLEX - vmnic_100600 Network Interface ONLINE DUPLEX - 0000:07:00.1 Ethernet controller: Intel Corporation I3 BROKEN BROKEN - vmnic_100601 Network Interface BROKEN BROKEN - 10/7 Display Ctlr ONLINE DUPLEX - 0
0000:2c:00.0 VGA compatible controller: Matrox Electro ONLINE DUPLEX - 10/8 USB Serial Bus Ctlr ONLINE ONLINE - 0
0000:2b:00.0 USB Controller: Intel Corporation Wellsbu ONLINE ONLINE - 0000:2b:00.1 USB Controller: Intel Corporation Wellsbu ONLINE ONLINE - 10/10 PCI to PCI Bridge ONLINE ONLINE - 0
10/11 PCI to PCI Bridge ONLINE ONLINE - 0
10/12 Network Ctlr ONLINE DUPLEX - 0
0000:9e:00.0 Ethernet controller: Intel Corporation Et ONLINE DUPLEX - vmnic_101200 Network Interface ONLINE DUPLEX - 0000:9e:00.1 Ethernet controller: Intel Corporation Et BROKEN BROKEN - vmnic_101201 Network Interface BROKEN BROKEN - -
Page 30
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
30
Chapter 1 Maintenance
10/40 Internal Disk Enclosure - - - 10/40/1 Disk Drive ONLINE DUPLEX A920 0
10/40/5 Disk Drive ONLINE DUPLEX A920 0
10/40/6 Disk Drive ONLINE DUPLEX A920 0
10/70 2x PCI-E2(X8) Riser Card - - - 10/120 Baseboard Management Ctlr ONLINE DUPLEX * 10/130 BB Rear Temp#0 Sensor - NORMAL - 11 Combined CPU/IO ONLINE DUPLEX - 0
11/1 Network Ctlr ONLINE DUPLEX - 0
0000:43:00.0 Ethernet controller: Intel Corporation Et ONLINE DUPLEX - -
vmnic_110100 Network Interface ONLINE DUPLEX - 11/2 - MISSING EMPTY - 11/3 Fibre Channel Serial Bus Ctlr ONLINE DUPLEX - 0
0000:b7:00.0 Fibre Channel: QLogic Corp. ISP8324-based ONLINE DUPLEX - 11/4 - MISSING EMPTY - 11/5 Mass Storage Ctlr ONLINE DUPLEX - 0
0000:54:00.0 Mass storage controller: LSI Logic / Symb ONLINE DUPLEX - 11/6 Network Ctlr ONLINE DUPLEX - 0
0000:41:00.0 Ethernet controller: Intel Corporation I3 ONLINE DUPLEX - vmnic_110600 Network Interface ONLINE DUPLEX - 0000:41:00.1 Ethernet controller: Intel Corporation I3 BROKEN BROKEN - vmnic_110601 Network Interface BROKEN BROKEN - 11/7 Display Ctlr ONLINE DUPLEX - 0
0000:66:00.0 VGA compatible controller: Matrox Electro ONLINE DUPLEX - 11/8 USB Serial Bus Ctlr ONLINE ONLINE - 0
0000:65:00.0 USB Controller: Intel Corporation Wellsbu ONLINE ONLINE - 0000:65:00.1 USB Controller: Intel Corporation Wellsbu ONLINE ONLINE - 11/10 PCI to PCI Bridge ONLINE ONLINE - 0
11/11 PCI to PCI Bridge ONLINE ONLINE - 0
11/12 Network Ctlr ONLINE DUPLEX - 0
0000:d8:00.0 Ethernet controller: Intel Corporation Et ONLINE DUPLEX - vmnic_111200 Network Interface ONLINE DUPLEX - 0000:d8:00.1 Ethernet controller: Intel Corporation Et BROKEN BROKEN - vmnic_111201 Network Interface BROKEN BROKEN - 11/40 Internal Disk Enclosure - - - 11/40/1 Disk Drive ONLINE DUPLEX A920 0
11/40/5 Disk Drive ONLINE DUPLEX A920 0
11/40/6 Disk Drive ONLINE DUPLEX A920 0
11/70 2x PCI-E2(X8) Riser Card - - - 11/120 Baseboard Management Ctlr ONLINE DUPLEX * 11/130 BB Rear Temp#1 Sensor - NORMAL - -
IO Enclosure 10 is the Active Compatibility Node.
This is an Express5800/R320f-M4 system, P-Package N8800-219F, Serial# 0000000000.
* Use lsLong to see this value.
Page 31
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
31
Chapter 1 Maintenance
4.3.2
Displaying the Status of a Single System Component
Before you remove a component that is duplexed for fault tolerance, verify that it is not in a simplex state. To
verify the state of a component, type a command in the following format:
# /opt/ft/bin/ftsmaint ls path
For path, specify the correct device ID for the component, as listed in Table 1.
The value of Op State shows the state of device. DUPLEX is shown if the system is duplicated, and SIMPLEX
is shown if the system is not duplicated.
The following examples demonstrate some common commands and the resulting output.
In Example 2, the I/O module 1 is listed as having a State of ONLINE and an OP State of DUPLEX. The value
of SECONDARY for Reason indicates that it is operating as the backup I/O element.
Example 2. Viewing the State of the Bottom I/O module 1
# /opt/ft/bin/ftsmaint ls 11
H/W Path : 11
Description : Combined CPU/IO
State : ONLINE
Op State : DUPLEX
Reason : SECONDARY
Modelx : 243-634944
Artwork Rev : 0
ECO Level : 0
Min Partner ECO Level : 0
Serial # : DBA2BE460004
Active Compat Node : false
Logic Revision : 2800028
MTBF Policy : useThreshold
MTBF fault class: uncorrectable
Fault Count: 0
Last Timestamp: Replace Threshold: 0
Evict Threshold: 21600
Value: 0
Minimum Count: 4
Page 32
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
32
Chapter 1 Maintenance
In Example 3, the internal hard disk drive in the I/O module 1 is listed as having a State of ONLINE and an Op
State of DUPLEX.
Example 3. Viewing the State of Hard Disk Drive 11/40/1
# ftsmaint ls 11/40/1
H/W Path : 11/40/1
Description : Disk Drive
State : ONLINE
Op State : DUPLEX
Reason : NONE
Modelx : HGST:HUC101812CSS200
Firmware Rev : A920
Serial : 06G0971H
Device Name : disk_i
Udev Device Names : Kernel Device Names : vmhba1:C0:T1:L0
Endurance : MTBF Policy : useThreshold
MTBF fault class: critical noncritical removal
Fault Count: 0 0 0
Last Timestamp: - - Replace Threshold: 0 0 0
Evict Threshold: 2147483647 604800 86400
Value: 0 0 0
Minimum Count: 1 4 2
MTBF fault class: aborts
Fault Count: 0
Last Timestamp: Replace Threshold: 0
Evict Threshold: 86400
Value: 0
Minimum Count: 2
4.3.3
Bringing System Components Down and Up
You can use the ftsmaint command to bring down and restart fault-tolerant components. After bringing up a
component, the system synchronizes and duplexes the corresponding component automatically.
When you use the bringDown command, the I/O module 1 stops.
# /opt/ft/bin/ftsmaint bringDown 11
Completed bringDown on the device at path 11.
When you use the bringUp command, the I/O module 1 starts. The system automatically synchronizes I/O
module 1 with I/O module 0. The RAID array drives are updated and become mirrored, and the system should
resume duplex operation.
# /opt/ft/bin/ftsmaint bringUp 11
Completed bringUp on the device at path 11.
Page 33
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
33
Chapter 1 Maintenance
4.3.4
Stopping and Starting the Internal Disk Controller
To stop the internal disk controller, use the ftsmaint command as well. For example, use the following
command to stop the disk drive 1 of internal disk controller.
# /opt/ft/bin/ftsmaint bringDown 11/40/1
Completed bringDown on the device at path 11/40/1.
Typing the following command starts the internal disk controller again.
# /opt/ft/bin/ftsmaint bringUp 11/40/1
Completed bringUp on the device at path 11/40/1.
4.3.5
Diagnostics
To start diagnostics on the CPU module and I/O module, use the following command.
# /opt/ft/bin/ftsmaint runDiag path
Before starting diagnostics, you need to bring down the module to be diagnosed. For example, use the
following commands to start diagnostics on CPU module 1.
# /opt/ft/bin/ftsmaint bringDown 1
Completed bringDown on the device at path 1.
# /opt/ft/bin/ftsmaint runDiag 1
Completed diagnostics on the device at path 1.
Check the Op State shows "DIAGNOSTICS_PASSED" by the following command.
# /opt/ft/bin/ftsmaint ls 1
H/W Path : 1
Description : Combined CPU/IO
State : UNKNOWN
Op State : DIAGNOSTICS_PASSED
Reason : NONE
Modelx : 243-634944
Firmware Rev : BIOS Version 9.1:31
Artwork Rev : 0
ECO Level : 0
Min Partner ECO Level : 0
Serial # : DBA2BE460004
Logic Revision : 2800028
MTBF Policy : useThreshold
MTBF fault class: correctable uncorrectable microsync
Fault Count: 0 0 0
Last Timestamp: - - Replace Threshold: 0 0 1728
Evict Threshold: 1800 21600 0
Value: 0 0 0
Minimum Count: 8 4 50
Note
Upon completion of diagnostics, run bringUp command to start the relevant module.
Page 34
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
34
Chapter 1 Maintenance
4.3.6
Updating BMC firmware
Use the following command to update the BMC firmware.
# /opt/ft/bin/ftsmaint burnBmcs fw_file
Important
Shutdown the guest OS except for ftSys Management Appliance.
1. Login to ftSys Management Appliance as a root user.
2. Use the SCP command or Host Client to store the BMC firmware file in the desired directory of ftSys
Management Appliance.
In the example below, ft control software Install DVD is mounted and BMC firmware file is copied to ftSys
Management Appliance.
# cp /mnt/cdrom/firmware/bmc/2800_4800_6800/062-03711bmc_bnn.nnrnn.nnsnn.
nn.bin/opt/ft/firmware/bmc/2800_4800_6800
Tips
See Chapter 2 (1.1.2 Install NEC ESMPRO Agent) in Installation Guide for how to
mount/unmount ft control software Install DVD.
3. Run the following command to check the State shows "ONLINE" and Op State shows "DUPLEX" for I/O
modules 0 and 1.
# /opt/ft/bin/ftsmaint ls 10
H/W Path : 10
...
State : ONLINE
Op State : DUPLEX
...
# /opt/ft/bin/ftsmaint ls 11
H/W Path : 11
...
State : ONLINE
Op State : DUPLEX
...
4. Run the following command to check the State shows "ONLINE" and Op State shows "DUPLEX" for
BMCs of I/O modules 0 and 1.
# /opt/ft/bin/ftsmaint ls 10/120
H/W Path : 10/120
...
State : ONLINE
Op State : DUPLEX
......
# /opt/ft/bin/ftsmaint ls 11/120
H/W Path : 11/120
...
State : ONLINE
Op State : DUPLEX
......
Page 35
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
35
Chapter 1 Maintenance
5. Run the following command to update BMC firmware. For bmc_file, specify the file path you have copied
in Step 2.
It takes approximately 30 minutes until update completes.
# /opt/ft/bin/ftsmaint burnBmcs bmc_file
When the following messages are displayed, update completes.
Updated firmware on the device at path 11/120.
Updated firmware on the device at path 10/120.
Important
Do not operate the machine and power supply unit while the firmware is updated.
The firmware is destroyed and modules may need to be replaced.
6. Run the following command to check that Op State of BMC shows "DUPLEX" and Firmware Rev shows
the new BMC version.
# /opt/ft/bin/ftsmaint ls 10/120
Op State : DUPLEX
:
Firmware Rev : 04.71/01.03/04.08 Version is indicated in the underlined part.
# /opt/ft/bin/ftsmaint ls 11/120
Op State : DUPLEX
:
Firmware Rev : 04.71/01.03/04.08 Version is indicated in the underlined part.
7. Run the following command to check that Op State of I/O module shows "DUPLEX".
# /opt/ft/bin/ftsmaint ls 10
:
Op State : DUPLEX
# /opt/ft/bin/ftsmaint ls 11
:
Op State : DUPLEX
8. Unmount ft control software Install DVD, if mounted. Then, disconnect the DVD drive.
Page 36
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
36
Chapter 1 Maintenance
4.3.7
Updating BIOS
Use the following command to update the BIOS.
# /opt/ft/bin/ftsmaint burnProm fw_file path
Important
Shutdown the guest OS except for ftSys Management Appliance.
1. Login to ftSys Management Appliance as a root user.
2. Use the SCP command or Host Client to store the BIOS file in the desired directory of ftSys Management
Appliance.
In the example below, ft control software Install DVD is mounted and BIOS file is copied to ftSys
Management Appliance.
# cp /mnt/cdrom/firmware/bios/2800_4800_6800/062-03711biosn.n.nn.rom
/opt/ft/firmware/bios/2800_4800_6800
Tips
See Chapter 2 (1.1.2 Install NEC ESMPRO Agent) in Installation Guide for how to
mount/unmount ft control software Install DVD.
3. Run the following command to check the State shows "ONLINE" and Op State shows "DUPLEX" for
CPU modules 0 and 1.
# /opt/ft/bin/ftsmaint ls 0
H/W Path : 0
...
State : ONLINE
Op State : DUPLEX
...
# /opt/ft/bin/ftsmaint ls 1
H/W Path : 1
...
State : ONLINE
Op State : DUPLEX
...
4. Run the following command to update the BIOS of CPU modules 0 and 1.
(1) Stop the CPU module 0.
# /opt/ft/bin/ftsmaint bringDown 0
Completed bringDown on the device at path 0.
(2) Update the BIOS of CPU module 0. For bios_file, specify the file path you have copied in Step 2.
# /opt/ft/bin/ftsmaint burnProm bios_file 0
Updated firmware on the device at path 0.
(3) Start the CPU module 0, and stop the CPU module 1.
# /opt/ft/bin/ftsmaint jumpSwitch 0
Transferred processing to the device at path 0.
Page 37
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
37
Chapter 1 Maintenance
(4) Diagnosis is performed when CPU module 1 is started. The new BIOS is applied to CPU module
1 from CPU module 0 automatically, and duplication process is performed.
# /opt/ft/bin/ftsmaint bringUp 1
Completed bringUp on the device at path 1.
Important
Do not operate the machine and power supply unit while the firmware is updated.
The firmware is destroyed and modules may need to be replaced.
5. Run the following command to check that Op State of CPU module shows "DUPLEX" and Firmware Rev
shows the new BIOS version.
# /opt/ft/bin/ftsmaint ls 0
Op State : DUPLEX
:
Firmware Rev : BIOS Version 9.1:31 Version is indicated in the underlined part.
# /opt/ft/bin/ftsmaint ls 1
Op State : DUPLEX
:
Firmware Rev : BIOS Version 9.1:31 Version is indicated in the underlined part.
6. Unmount ft control software Install DVD, if mounted. Then, disconnect the DVD drive.
Page 38
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
38
Chapter 1 Maintenance
4.4
Disabling Auto Reinstallation of CPU Module
If the failure is corrected and the CPU module is restarted, the Auto Reinstallation of CPU Module feature
reconfigures the system and automatically brings up the module relevant to that failure.
Auto Reinstallation of CPU Module feature is enabled by default. It works when ft server is started, recovered
from system fault, or recovered from pseudo fault.
This feature may be disabled because it may take time to automatically reinstall the CPU module depending
on system configuration. Take the steps below to disable this feature.
You can shift the timing of no communication that occurs during the installation process of CPU module by
disabling the auto reinstallation of CPU module and manually enabling the installation of the CPU module.
Important
You need to perform this configuration as a root user.
Note
This configuration just shifts the timing of the no-communication and does not control the
no-communication status. Furthermore, this configuration does not prevent timeout error
due to no communication from occurring.
Tips
Even if auto reinstallation of CPU is disabled, it is enabled and the installation process
occurs when the system is starting up by a reboot.
4.4.1
Disabling auto reinstallation of CPU module
Run the following command to disable auto reinstallation of CPU module.
# /opt/ft/bin/ftsmaint bringupPolicy defer
Successfully deferred cpuBringupPolicy
If auto reinstallation of CPU module is disabled, run the ftsmaint bringup command to install the CPU module
manually, or restart the system.
Run the following command to enable auto reinstallation of CPU module.
# /opt/ft/bin/ftsmaint bringupPolicy enable
Successfully enabled cpuBringupPolicy
Run the following command to confirm the current setting.
# /opt/ft/bin/ftsmaint bringupPolicy list
CPU bringup policy is enabled
Page 39
4. Maintenance of Express5800/ft series
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
39
Chapter 1 Maintenance
4.4.2
Scheduling for auto reinstallation of CPU module
You can also limit the time to perform auto reinstallation of CPU by combination with cron daemon.
1. Add configuration to /etc/crontab
Example: Disable auto reinstallation of CPU module from 6:00 to 18:15 everyday.
Add the following lines to /etc/crontab.
# Defer CPU bringup at 6:00 every day
# Enable CPU bringup at 18:15 every day
0 6 * * * root /opt/ft/bin/ftsmaint bringupPolicy defer
15 18 * * * root /opt/ft/bin/ftsmaint bringupPolicy enable
2. Reflect the configuration file of cron daemon.
# crontab -u root /etc/crontab
Page 40
5. Checking the Duplicating Operation of Modules
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
40
Chapter 1 Maintenance
5.
Checking the Duplicating Operation of Modules
This section describes how to check if the system runs properly after system installation or reinstallation.
CPU/IO module has a processor function part and IO function part.
Tips
Processor function part and IO function exists in the CPU/IO module, which monitor and
control for each part. In this section, the processor function part is referred to as CPU
module and IO function part I/O module.
5.1
Evaluate Start and Stop of I/O Modules
This section describes how to confirm the continuous system operation by failover after stopping the primary
I/O module.
1. Check which is the primary I/O module.
Tips
The I/O module with the PRIMARY LED lit is the primary module.
2. Check whether the I/O modules are duplicated.
Tips
To check if the I/O modules are duplicated, see the System FT LED.
(1)
(2)
(3)
Page 41
5. Checking the Duplicating Operation of Modules
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
41
Chapter 1 Maintenance
[Indications of the status LED when I/O modules are duplicated]
* When I/O module 0 is defined as primary module
LED I/O module 0 I/O module 1
(1) PRIMARY LED Green –
(2) DISK ACCESS LED Green(Blinking) Green (Blinking)
LED System
(3) System FT LED Green
*Each number in the table corresponds to the numbers in the above figure.
DISK ACCESS LED (2) is lit when there is access to the hard disk drive.
3. Stop the operation of the primary I/O module using the ftsmaint Command.
If the I/O Module 0 is primary, run the following command.
* Specify the device path ID of the primary I/O module.
When you stop the operation of the primary I/O module, failover occurs and the secondary I/O
module becomes the primary module.
The status LED of I/O module changes as shown below:
[Indications of status LED]
LED I/O module 0 I/O module 1
(1) PRIMARY LED – Green
(2) DISK ACCESS LED –
Amber or Green blinking
(Green when accessing to
HDD)
LED System
(3) System FT LED –
4. Start the I/O module stopped in step 3.
Run the following command to start the stopped I/O module 0.
When the I/O module is started, diagnosis of I/O module, and duplication of I/O module are
performed.
The status LED of I/O module changes as shown below:
# cd /opt/ft/bin
# ./ftsmaint bringdown 10 (*)
# cd /opt/ft/bin
# ./ftsmaint brin
gup
10
Page 42
5. Checking the Duplicating Operation of Modules
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
42
Chapter 1 Maintenance
[Indications of status LED]
Immediately after the I/O module startup until the completion of diagnosis:
LED I/O module 0 I/O module 1
(1) PRIMARY LED – Green
(2)
DISK ACCESS LED
–
Amber or Green blinking
(Green when accessing to
HDD)
LED System
(3) System FT LED –
When duplication of disks is started after the completion of diagnosis of I/O module:
LED I/O module 0 I/O module 1
(1) PRIMARY LED – Green
(2)
DISK ACCESS LED
Amber or Green blinking
(Green when accessing to
HDD)
Amber or Green blinking
(Green when accessing to
HDD)
LED System
(3) System FT LED –
After the completion of disk duplication and when the I/O modules are duplicated:
LED I/O module 0 I/O module 1
(1) PRIMARY LED – Green
(2)
DISK ACCESS LED
Green (Blinking)
(Green when accessing to
HDD)
Green (Blinking)
(Green when accessing to
HDD)
LED System
(3) System FT LED Green
Page 43
5. Checking the Duplicating Operation of Modules
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
43
Chapter 1 Maintenance
5.2
Evaluate Start and Stop of CPU Modules
This section describes how to confirm the continuous system operation after stopping one of the CPU
modules.
1. Confirm that the CPU modules are duplicated.
To check if the CPU modules are duplicated, see the status LEDs of the CPU modules.
[Indications of status LED when CPU modules are duplicated]
LED System
(3) System FT LED Green
2. Use the ftsmaint command to stop the operation of the CPU module to be removed.
To stop the CPU Module 0, run the following command.
When the CPU module is stopped, the status LED changes as follows. This indicates that one CPU
module is operating now.
[Indications of status LED]
LED System
(3) System FT LED –
# cd /opt/ft/bin
# ./ftsmaint brin
g
d
own 0
(1)
(2)
(3)
Page 44
5. Checking the Duplicating Operation of Modules
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
44
Chapter 1 Maintenance
3. Start the stopped CPU module.
Run the following command to start the operation of the CPU module stopped in step 2.
When the CPU module is started, Hardware diagnosis, Memory Synchronization (Memory Copy),
and then the Duplication Completion are performed.
Note that the system is paused temporarily for copying memory during memory synchronization.
[Indications of status LED after completion of duplication]
LED System
(3) System FT LED Green
# cd /opt/ft/bin
# ./ftsmaint bringup 0
Page 45
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
45
Chapter 1 Maintenance
6.
Error Messages
If the server enters the abnormal state, the error is posted by various means. This section explains the types of
error messages.
LED indication is unusual.
Refer to "6.1 Error Messages by LED Indication".
An error message appeared.
Refer to "6.2 POST Error Message".
Page 46
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
46
Chapter 1 Maintenance
6.1
Error Messages by LED Indication
The LEDs on the front and rear panels of the server and near the handles of hard disk drives inform the user of
the various server statuses by the colors and the patterns of going on, going off, and flashing. If trouble seems
to have occurred, check the LED indication.
This Maintenance Guide describes actions to be taken for watch error message. However, if replacement of
modules is necessary, contact your sales agent.
System POWER LED
System FAULT LED
System FT LED
<With Front Bezel mounted>
System POWER LED
System FAULT LED
Module POWER LED
DISK Access LED
EXPRESSSCOPE
Optical DISK ACCESS LED
<With Front Bezel removed>
Module ID LED
Management LAN port
SPEED LED
LINK/ACT LED
1GLAN connector
10GLAN connector
(R320e-M4, R320f-M4
only)
Power Unit LED
<Rear Panel>
System FT LED
Page 47
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
47
Chapter 1 Maintenance
System POWER LED
(1)
LED indication Description Action
On (green) Either or both of CPU/IO modules are powered on. –
Off Both of CPU/IO modules are powered off. –
System FAULT LED
(2)
LED indication Description Action
Off
Both of CPU/IO modules are offline or normal. System FAULT LED does not notify
of disk status. Check it according to
(5) Disk Access LED indication.
On (amber) One of the CPU/IO modules failed. Take a note of LED indications on
EXPRESSSCOPE, then contact your
service representative.
Blinking (amber) One of the CPU/IO modules failed. However, the
failed CPU/IO module cannot be identified.
Contact your service representative.
System FT LED
(3)
LED indication Description Action
On (green) The system is operating under duplex condition. –
Off The system is not duplexed. –
System ID LED
(4)
LED indication Description Action
On (blue) The UID switch is pressed. –
Blinking (blue) The device identification request is issued from
remote site.
–
Off – –
Page 48
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
48
Chapter 1 Maintenance
Disk Access LED
(5)
Conditions of DISK LED
Description Action
DISK LED 1 DISK LED 2
Off Off The disk is in the idle state. –
Blinking
(green)
Off The disk is being accessed. –
Off On
(amber)
The disk is failing. Contact your sales
representative.
Off Blinking
(amber)
The mirror of the disk is disconnected. Perform mirroring.
Blinking in green and
amber in turn
The mirror of the disk is being rebuilt or disconnected. Check whether the mirror of
the disk is disconnected.
Access LED on optical disk drive
(6)
LED indication Description Action
Off The optical disk is not accessed. –
On The optical disk is being accessed. –
LEDs on Management LAN Connector and LAN connectors
(7)
LINK/ACT LED
LED indication Description Action
On (green) Power is supplied to the main unit and hub, and they
are connected correctly ("LINK").
–
Blinking (green) The network port is sending or receiving data (ACT). –
Off Disconnected from network. Check the network status and cable
connection.
SPEED LED (Management port)
LED indication Description Action
On (green) The port is operating on 100BASE-TX. –
Off The port is operating on 10BASE-T. –
DISK LED 1 (green)
DISK LED 2 (amber)
Page 49
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
49
Chapter 1 Maintenance
SPEED LED (1G LAN connector)
LED indication Description Action
On (amber) The port is operating on 1000BASE-T. –
On (green) The port is operating on 100BASE-TX. –
SPEED LED (10G LAN connector)
LED indication Description Action
On (amber) The port is operating on 1000BASE-T. –
On (green) The port is operating on 10GBASE-T. –
Off The port is operating on 100BASE-TX. –
EXPRESSSCOPE
(8)
If any module fails, LED on EXPRESSSCOPE relevant to the failed module lights in amber.
(1) Module POWER LED
LED indication Description Action
On (green) The power of CPU/IO module is ON. –
Off
The AC power is not supplied to the CPU/IO
module.
(It may take about 1 minute until standby state (this
LED is blinking) after the AC power is supplied.)
–
Blinking (green) The CPU/IO module is in standby state. –
(5)-1
(5)-2(5)-3(5)-4(1)
(2) (3) (4)
(11) (10)
(9)
(8)
(7)
(6)
Page 50
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
50
Chapter 1 Maintenance
(2) SAFE TO PULL (SAFE TO PULL LED)
This LED indicates the possibility to remove CPU/IO module safely.
LED indication Description Action
On (green) The CPU/IO module can be removed. –
Blinking (green) The CPU/IO module cannot be removed. –
Off The CPU/IO module is in offline state. –
(3) Module ID (ID LED)
The Module ID LED is used for identifying the device that requires maintenance among devices mounted
on the rack.
LED indication Description Action
On (green) The UID switch is pressed. –
Blinking (green) The device identification requests was sent from
remote site.
–
Off – –
(4) CPU (CPU FAULT LED)
The LED lights in amber when the CPU part (CPU module) of CPU/IO modules fails. Contact your service
representative.
Page 51
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
51
Chapter 1 Maintenance
(5) MEM NUMBER (Memory slot error LED)
The LED lights amber when failure occurs on the memory slot of CPU/IO module.
Memory slots with errors can be identified by lighting status of the (5)-1 to (5)-4 as shown in the table
below.
Status of memory slot error LED
Description
Action
(5)-1
(MSB)
(5)-2 (5)-3 (5)-4
(LSB)
–
–
–
– Operating normally. –
–
–
–
An error occurred on memory slot 1. Contact your sales representative.
–
–
– An error occurred on memory slot 2. Contact your sales representative.
–
–
An error occurred on memory slot 3. Contact your sales representative.
–
–
– An error occurred on memory slot 4. Contact your sales representative.
–
–
An error occurred on memory slot 5. Contact your sales representative.
–
– An error occurred on memory slot 6. Contact your sales representative.
–
An error occurred on memory slot 7. Contact your sales representative.
–
–
– An error occurred on memory slot 8. Contact your sales representative.
–
–
–
An error occurred on memory slot 9. Contact your sales representative.
–
–
– An error occurred on memory slot 10. Contact your sales representative.
–
–
An error occurred on memory slot 11. Contact your sales representative.
–
–
– An error occurred on memory slot 12. Contact your sales representative.
–
–
An error occurred on memory slot 13. Contact your sales representative.
–
– An error occurred on memory slot 14. Contact your sales representative.
–
An error occurred on memory slot 15. Contact your sales representative.
–
–
– An error occurred on memory slot 16. Contact your sales representative.
An error occurred on unknown memory
slot. Or the memory is unpopulated.
Contact your sales representative.
: LED is lit.
: LED is blinking.
–: LED is unlit.
(6) TEMP (Abnormal temperature LED)
The LED lights in amber when temperature in CPU/IO module becomes abnormal. Contact your service
representative.
(7) VLT (Power error LED)
The LED lights in amber when electric voltage failure occurs in CPU/IO module. Contact your service
representative.
(8) PSU (Power supply unit error LED)
The LED lights in amber when failure occurs on the power supply unit of CPU/IO module. Contact your
service representative.
Page 52
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
52
Chapter 1 Maintenance
(9) FAN (Fan error LED)
The LED lights in amber when failure occurs on the cooling fan for CPU of CPU/IO module. Contact your
service representative.
(10) I/O (I/O FAULT LED)
The LED lights in amber when failure occurs on the I/O (I/O module) part of CPU/IO module. Contact your
service representative.
(11) PRIMARY (PRIMARY LED)
The LED lights in green when CPU/IO module is primary. This LED may blink in green while the DUMP
(NMI) switch is pressed.
Power Unit LED
(9)
Power Unit LED is located at power supply unit at the rear of the server.
LED indication Description Action
Off The power unit does not receive the AC power. –
Blinking (green) The power unit receives the AC power. –
On (green) The server is powered on. –
On (amber)
Blinking (amber)
The power supply unit fails. Contact your service representative.
Page 53
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
53
Chapter 1 Maintenance
6.2
POST Error Message
When POST detects any error, it displays an error message on the display unit.
The following table lists error messages and the actions to take in response to them.
Tips
Write down the displayed messages before contacting your sales
representative.
The list only contains messages for the server. For details about error
messages of optional devices, and the actions to take, refer to the instructions
that come with each product.
System Monitoring Check
... Passed
ERROR
:
Press <F1> to resume, <F2> to setup
Example of error message
This message indicates that date and time
set on realtime clock is incorrect.
Page 54
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
54
Chapter 1 Maintenance
Error messages
(1)
Error Message Cause Solution
8000 System variable is
corrupted.
Illegal setup information of BIOS
occurred.
Start BIOS Setup Utility (SETUP), and then
execute Load Setup Defaults and specify the
necessary settings.
If the same error is detected repeatedly in spite
of re-setting, contact your sales representative.
8001 Real time clock error
Real time clock error occurred. Start SETUP, and then specify the correct date
and time.
If the same error is detected repeatedly in spite
of re-setting, contact your sales representative.
8002 Check date and time
settings
Incorrect date and time set on real time
clock occurred.
8006 System configuration
data cleared by Jumper.
The setup utility settings were cleared
using the jumper.
Follow the steps described in Chapter 1 (9.
Resetting and Clearing the Server).
8007 SETUP Menu Password
cleared by Jumper.
The setup utility password was cleared
using the jumper.
8800 DXE_NB_ERROR
An error occurred during initialization of
chipset.
Contact your sales representative.
8801 DXE_NO_CON_IN
An error occurred during initialization of
console.
8802 DXE_NO_CON_OUT
8803 PEI_DXE_CORE_NOT_FOUND
A flash ROM is corrupt.
8804 PEI_DXEIPL_NOT_FOUND
8805 DXE_ARCH_PROTOCOL_NOT_A
VAILABLE
8806 PEI_RESET_NOT_AVAILABLE
The system was not reset correctly.
8807 DXE_RESET_NOT_AVAILABLE
8808 DXE_FLASH_UPDATE_FAILED
The Flash ROM was not written to
correctly.
B000 Expansion ROM not
initialized
Failed to expand option ROM. Disable expansion of option ROM of the board
that is not used for OS boot.
B001 Expansion ROM not
initialized - PCI
Slot 1
Option ROM expansion in PCI slot 1
failed.
Disable expansion of option ROM of the option
board that is not used for OS boot.
Start SETUP, and select Advanced PCI
Configuration PCI Device Controller and
Option ROM Settings PCIx Slot Option
ROM Disabled. (x: PCI slot number)
B002 Expansion ROM not
initialized - PCI
Slot 2
Option ROM expansion in PCI slot 2
failed.
B003 Expansion ROM not
initialized - PCI
Slot 3
Option ROM expansion in PCI slot 3
failed.
B004 Expansion ROM not
initialized - PCI
Slot 4
Option ROM expansion in PCI slot 4
failed.
B022 Serial Port
Configuration
Overlapped.
Overlapping serial port configuration
occurred.
Start SETUP, select Advanced Serial Port
Configuration, and specify the setting again in
a way that the values of Base I/O or Interrupt in
Serial Port A and Serial Port B will not be the
same.
B800 DXE_PCI_BUS_OUT_OF_RESO
URCES
PCI device resource allocation failed.
Check the connection of the optional board.
C010 The error occurred during
temperature sensor
reading
An error occurred while reading
temperature sensor.
Contact your sales representative.
C011 System Temperature out of
the range.
A temperature abnormality occurred.
It is possible that a fan has failed or is clogged.
Contact your sales representative.
Page 55
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
55
Chapter 1 Maintenance
Error Message Cause Solution
C061 1st SMBus device Error
detected.
An error occurred on 1st SM Bus. Contact your sales representative.
C062 2nd SMBus device Error
detected.
An error occurred on 2nd SM Bus.
C063 3rd SMBus device Error
detected.
An error occurred on 3rd SM Bus.
C064 4th SMBus device Error
detected.
An error occurred on 4th SM Bus.
C065 5th SMBus device Error
detected.
An error occurred on 5th SM Bus.
C066 6th SMBus device Error
detected.
An error occurred on 6th SM Bus.
C067 7th SMBus device Error
detected.
An error occurred on 7th SM Bus.
C101 BMC Memory Test
Failed..
An error occurred on BMC. Unplug the power cord, wait for at least 30
seconds, then restart the server. If the same
error is detected repeatedly, contact your sales
representative.
C102 BMC Firmware Code
Area CRC check
Failed.
C103 BMC core hardware
failure.
C104 BMC IBF or OBF check
failed.
An error occurred while accessing
BMC.
C105 BMC SEL area full.
There is not enough space to store the
system event log.
Delete the event logs with following the steps
described in Chapter 3 (1.2.4 (3) Event Log
Configuration submenu).
C10C BMC update firmware
corrupted.
An illegality occurred while updating
BMC firmware.
Unplug the power cord, wait for at least 30
seconds, then restart the server. If the same
error is detected repeatedly, contact your sales
representative.
C10D Internal Use Area of BMC
FRU corrupted.
An illegality occurred in FRU containing
the device information.
C10E BMC SDR Repository empty.
An error occurred on BMC SDR.
C10F IPMB signal lines do not
respond.
Failure of Satellite Management
Controller occurred.
C110 BMC FRU device failure.
An error occurred in FRU that contains
device information.
C111 BMC SDR Repository
failure.
Failure occurred in SROM that stores
the SDR.
C112 BMC SEL device failure.
Device failure occurred in BMC SEL.
C113 BMC RAM test error.
An error occurred in BMC RAM.
C114 BMC Fatal hardware error.
A hardware error occurred in BMC.
C115 Management controller
not responding
Management controller does not
respond.
Update the BMC firmware.
If the same error is detected repeatedly,
contact your sales representative.
C116 Private I2C bus not
responding.
Private I2C bus does not respond. Unplug the power cord, wait for at least 30
seconds, then restart the server. If the same
error is detected repeatedly, contact your sales
representative.
C117 BMC internal exception
BMC internal error occurred.
C118 BMC A/D timeout error.
BMC A/D timeout error occurred.
C119 SDR repository corrupt.
BMC error or illegal SDR data
occurred.
C11A SEL corrupt.
BMC error or illegal system event log
data occurred.
Page 56
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
56
Chapter 1 Maintenance
Error Message Cause Solution
C11B BMC Mezzanine card is not
found.
BMC Mezzanine card is not installed. Contact your sales representative.
C11C BMC Mezzanine partition
is invalid.
A format error occurred in BMC
Mezzanine card.
C11D BMC is in Forced Boot
Mode.
Detected that BMC is in Forced Boot
Mode.
Unplug the power cord, wait for at least 30
seconds, then restart the server. At that time,
check the jumper switch setting on
motherboard. If the same error is detected
repeatedly, contact your sales representative.
D483 BP SROM data invalid
An invalid data occurred in system
backplane.
Contact your sales representative.
D484 BP SROM data read error
Failed to read data in system
backplane.
D485 MB SROM data invalid
An invalid data occurred in CPU/IO
board.
D486 MB SROM data read error
Failed to read data in CPU/IO board.
Page 57
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
57
Chapter 1 Maintenance
Error messages on a virtual LCD
(2)
In EXPRESSSCOPE Engine 3 web browser window, you can confirm virtual LCD error messages (for details on
the virtual LCD, refer to "EXPRESSSCOPE Engine 3 User’s Guide").
The table below shows the error messages displayed on upper and lower lines, cause, and solution.
Messages displayed on an upper LCD line
Message
on Upper LCD Line
Description Solution
XXXX BIOSXXXX Displayed while POST is running. This is not an error.
POST Completed
Successfully
Displayed when POST completes normally. This is not an error.
POST ERROR
XXXX
Error XXXX was detected during POST. Check the message displayed on LCD, and take an
appropriate action.
System Simplex The system is operating in simplex mode. This is not an error.
System Duplex CPU/IO module is operating in duplex
mode.
This is not an error.
CPU Broken A CPU failure was detected. Contact your sales representative.
IO Broken An I/O unit failure was detected. Contact your sales representative.
Message displayed on upper
LCD line
Message displayed on lower
LCD line
Page 58
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
58
Chapter 1 Maintenance
Messages displayed on a lower LCD line
Message on Lower LCD Line Description Solution
VBAT Lower Non-Critical A voltage abnormality was
detected.
Contact your sales representative.
VBAT Upper Non-Critical
VBAT Lower Critical
VBAT Upper Critical
Baseboard Temperature1 Lower Non-Critical A temperature abnormality was
detected.
It is possible that a fan has failed or is
clogged. Contact your sales
representative and request repairs.
Baseboard Temperature1 Upper Non-Critical
Baseboard Temperature1 Lower Critical
Baseboard Temperature1 Upper Critical
Baseboard Temperature2 Lower Non-Critical
Baseboard Temperature2 Upper Non-Critical
Baseboard Temperature2 Lower Critical
Baseboard Temperature2 Upper Critical
CPU1_DIMM Area Temperature Lower
Non-Critical
CPU1_DIMM Area Temperature Upper
Non-Critical
CPU1_DIMM Area Temperature Lower
Critical
CPU1_DIMM Area Temperature Upper
Critical
CPU2_DIMM Area Temperature Lower
Non-Critical
CPU2_DIMM Area Temperature Upper
Non-Critical
CPU2_DIMM Area Temperature Lower
Critical
CPU2_DIMM Area Temperature Upper
Critical
Processor1 Thermal Control Upper
Non-Critical
Processor1 Thermal Control Upper Critical
Processor2 Thermal Control Upper
Non-Critical
Processor2 Thermal Control Upper Critical
DUMP Request ! The dump button was pressed. Wait until collecting the memory dump
data has finished.
Power Supply1 Failure detected A power supply unit abnormality
occurred.
Make sure that the power cord is
plugged in. If this does not resolve the
problem, contact your sales
representative and request repairs.
Processor Missing No CPU is installed. Contact your sales representative.
Processor1 Thermal Trip The power was forcibly turned off
due to a CPU temperature
abnormality.
Processor2 Thermal Trip
Page 59
6. Error Messages
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
59
Chapter 1 Maintenance
Message on Lower LCD Line Description Solution
Sensor Failure Detected. Abnormality in a sensor was
detected.
Contact your sales representative.
SMI timeout A timeout occurred while
servicing system management
interrupts.
IPMI Watchdog timer timeout (Power off) A watchdog timer timeout
occurred.
System Front FAN1 Lower Non-Critical A fan alarm was detected. It is possible that a fan has failed or is
clogged. Contact your sales
representative and request repairs.
System Front FAN2 Lower Non-Critical
System Front FAN3 Lower Non-Critical
System Front FAN4 Lower Non-Critical
System Front FAN5 Lower Non-Critical
Page 60
7. Collecting Failure Information
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
60
Chapter 1 Maintenance
7.
Collecting Failure Information
If the server fails, you can collect failure information by using the following method.
The failure information is to be collected only at the request of your sales representative.
Important When the system restarts after a failure has occurred, a message may appear
indicating virtual memory shortage. Ignore this message and proceed with
starting the system. Restarting the system may result in an inability to
properly dump the data.
7.1
Collection of Collect Logs
When you collect NEC ESMPRO Agent collect logs, log in to the log server on which NEC ESMPRO Agent is
installed as the root user and run the following command.
The collected data is created in the following file.
Note It may take certain period of time to create collectsa.tgz file.
# cd /opt/nec/esmpro_sa/tools/
# ./collectsa.sh
/opt/nec/esmpro_sa/tools/collectsa.tgz
Page 61
7. Collecting Failure Information
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
61
Chapter 1 Maintenance
7.2
Collection of System Information
The ESX system information is recorded in syslog, etc. When you collect system information in the
server, log in to ftSys Management Appliance as a root user and run the following command.
The following message is displayed.
If the IP address or the host name of the ESXi host enclosed with brackets ([]) is correct, press the <Enter> key.
The following message is displayed.
If the root user name of the ESXi host enclosed with brackets ([]) is correct, press the <Enter> key.
If the following message appears, enter the root password for ESXi host.
The collected data is created in the following directory. (YYYYMMDD denotes created date.)
Note
It may take certain period of time to create Bug_YYYYMMDD.tar file.
Tips
If the information shown in the brackets is not correct, set the correct data on the
system by executing the configure-appliance command, and then execute the
buggrabber command again.
For details of the configure-appliance command, see the following section in
Installation Guide.
Chapter 1, Installing OS 2.3.1 If the network settings of the ESXi host or root user
password has been changed
# /opt/ft/sbin/buggrabber.pl
Enter Name or IP address of the host ftServer
[
xxx.
xxx.
xxx.
xxx]
:
Enter Administrative user for xxx
.
xxx.
xxx.
xxx[
xxx]
:
Enter Administrative password for xxx.xxx.xxx.xxx []:
/tmp/BugPool/Bug_YYYYMMDD.tar
Page 62
7. Collecting Failure Information
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
62
Chapter 1 Maintenance
7.3
Collecting Memory Dump
If an error occurs, the dump file should be saved to acquire necessary information.
The dumps for the ESXi host are saved to the following files under /var/core.
- vmkernel-zdump-MMDDYY.HH:mm.n
- vmkernel-dumpinfo-MMDDYY.HH.mm.txt
- vmkernel-ring-MMDDYY.HH.mm
* MMDDYY denotes the created date, and HH:mm.n denotes the created time.
* It may take certain time to create dump data file.
* Names of the dump files may differ from the ones as above depending on the server state at which dump data
were collected (for example, 'vmkernel-zdump.1').
Consult with your sales representative before dumping the memory. Dumping the memory while the server is in
operating normally may affect the system operation.
Important
A message indicating insufficient virtual memory may appear when
restarting the system due to an error. Ignore this message and proceed.
Restarting the system may result in an inability to properly dump the
data.
If a physical processor of CPU #0 is allowed to be used for the virtual
machine, memory dump may not be collected even when pressing the
DUMP switch. To operate the machine assuming to collect memory
dump, set the value other than "0" for the property of "Scheduling
Affinity” of the virtual machine.
Use the DUMP (NMI) switch to collect the memory dump in case of a failure.
The procedure for use of the DUMP (NMI) switch is described below.
Important If you perform these steps, the system is made offline automatically, and is
rebooted. Note that the system is not ready for use for that period.
Page 63
7. Collecting Failure Information
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
63
Chapter 1 Maintenance
Hold and press the DUMP switch on the primary CPU/IO module for 4 to 8 seconds.
The PRIMARY LED blinks when pressing the DUMP switch. Release your finger when the LED goes off.
Press the DUMP switch by inserting the pointed tool such as ballpoint pen into the switch hole.
<How to press the DUMP switch>
<Location of the DUMP switch>
Important
Pressing the DUMP switch excessively shorter or longer will fail to
collect memory dump.
Do not use anything that easily breaks such as pencil, toothpicks, or
plastic.
The memory dump is stored when DUMP switch is pressed. (Memory dump may not be collected at CPU stall.)
Tips
The dump files cannot be deleted automatically. Check the /var/core directory size
periodically in order not to run out of the capacity.
The size of a dump file is approximately 100 MB.
After executing memory dump using the DUMP switch, the server may fail to restart. In such a case, forcibly
reset the server according to Chapter 1 (9.2 Forced Shutdown).
Press the DUMP switch
0 sec 4 sec
Release the switch
Press and hold
Do not press the switch for
9 seconds or longer.
1 sec 2 sec 3 sec 9 sec 10 sec 11 s e c5 sec 6 sec 7 sec 8 sec
DUMP(NMI) switch
PRIMARY LED blinks PRIMARY LED off
PRIMARY LED on
Page 64
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
64
Chapter 1 Maintenance
8.
Troubleshooting
If this system does not operate as intended, check it according to the contents of the following checklist before
sending it for repair. If an item in the checklist corresponds with a problem you are experiencing, follow the
subsequent check and processing instructions.
The server does not work normally.
Refer to "8.1 Problems When Turning on the Server".
Refer to "8.4 Problems When starting ESXi".
Refer to "8.5 Problems When Occurring Failures".
Refer to "8.6 Problems with Internal Devices and Other Hardware".
Refer to "8.7 Problems with System Operation".
Refer to "8.10 Problems with Optical Disk Drive and Flash FDD".
Failed to start from EXPRESSBULDER.
Refer to "8.2 Problems When Starting EXPRESSBUILDER".
Refer to "8.8 Problems When Starting EXPRESSBUILDER on Windows".
Failed to install OS.
Refer to "8.3 Problems When Installing VMware ESXi and the ft control software".
NEC ESMPRO does not work normally.
Refer to "8.9 Problems with Bundled Software".
Refer to User’s Guide stored in ft control software Install DVD.
If the server still does not work normally, refer to the following topics in this chapter before suspecting failure.
Error message
Refer to "6. Error Messages".
NEC ESMPRO Manager
Refer to NEC ESMPRO Manager Installation Guide stored in EXPRESSBUILDER.
Collect failure information
Refer to "7. Collecting Failure Information".
If the trouble persists, contact your service representative.
Page 65
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
65
Chapter 1 Maintenance
8.1
Problems When Turning on the Server
[?] Fail to power on the server:
Is the server properly supplied with power?
Check if the power cord is connected to a power outlet (or UPS) that meets the power
specifications for the server.
Check the power cord for broken shield or bent plugs.
Make sure the power breaker for the connected power outlet is on.
If the power cord is plugged to a UPS, make sure the UPS is powered and it supplies power. See
the manual that comes with the UPS for details.
Check the linkage between power supply to the server and the connected UPS using the BIOS
SETUP utility of the server.
Did you press the POWER switch?
When power cord is connected, the initialization of management controller starts. During
initialization, the Module POWER LED is unlit. To power on the server, press the POWER switch
after the Module POWER LED is lit green. (It may take about 1 minute until the Module POWER
LED blinks in green after connecting the power cord.)
Did you install the CPU/IO module properly?
Check if the CPU/IO module is properly installed in the server. Secure the CPU/IO module with
screw located on the module removable handle.
[?] The screen does not turn on.
Wait until the NEC logo appears.
[?] The screen showing nothing (black screen) appears several times during POST execution.
This sever may switch the screen to the black screen several times during POST execution, but there
is not any problem.
[?] POST fails to complete:
Are the DIMMs installed?
Check if DIMMs are installed correctly.
Is the memory size large?
The memory check may take a time if the memory size is large. Wait for a while.
Did you perform any keyboard or mouse operation immediately after you started the server?
If you perform any keyboard or mouse operation immediately after start-up, POST may
accidentally detect a keyboard controller error and stops proceeding. In such a case, restart the
server. Do not perform any keyboard or mouse operation until the BIOS start-up message
appears when you restart the server.
Does the server have appropriate memory boards or PCI card?
Operation of the server with unauthorized devices is not guaranteed.
Did you install the CPU/IO module properly?
Check if the CPU/IO module is properly installed in the server. Secure the CPU/IO module with
screw located on the module removable handle.
Page 66
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
66
Chapter 1 Maintenance
8.2
Problems When Starting EXPRESSBUILDER
[?] Unable to start EXPRESSBUILDER
Did you insert EXPRESSBUILDER DVD?
Insert the DVD and restart the server.
Are BIOS settings correct?
Configure the boot order in BIOS SETUP so that the optical disk drive will be the first to start up.
Did an error message appear at startup?
→ Take an appropriate action described below according to the on-screen message.
Error [Message ID:Z3002] :
Failed to detect a DVD drive or a flash drive.
Meaning: A DVD drive or a built-in flash drive cannot be detected.
Action: Check the hardware connections.
Error [Message ID:Z3003] :
Failed to read a file.
Meaning: A file cannot be read from a DVD.
Action: Check if a DVD is scratched.
Is a message popped up?
Take an appropriate action according to the on-screen message.
Message Action
This EXPRESSBUILDER is not for this
computer. Insert the EXPRESSBUILDER disc
for this computer and click OK
t
o restart
the computer.
Use EXPRESSBUILDER provided with the server. If
the same error occurs, contact your sales
representative.
Failed to get the hardware parameters on
the motherboard. Check if EXPRESSBUILDER
is for this computer, and check if the
motherboard is broken. Click OK
t
o restart
the computer.
Contact your sales representative.
Failed to find a file. Click OK to restart
the computer.
Media may be defective or the optical disk drive may
be faulty.
Contact your sales representative.
Failed to open a file. Click OK to restart
the computer.
Failed to get the parameters of a file.
Click OK to restart the computer.
Failed to read a file.
Failed to copy a file.
An undefined error occurred.
Click OK to restart the computer.
Page 67
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
67
Chapter 1 Maintenance
8.3
Problems When Installing VMware ESXi and the ft control software
[?] Unable to install VMware ESXi
Is the Hard Disk Drive properly installed?
Make sure that the Hard Disk Drive is installed securely and that cables are properly connected.
Have you configured Boot Mode and QLogic BIOS?
The settings are different from the default values. Refer to Chapter 1 (1.3 Enabling Internal Hard
Disk Drive or 1.4 Enabling Fiber Channel card) and (1.7 Setting HBA configuration by using
QLogic) in Installation Guide.
Have you checked precautions for installation?
Refer to Chapter 1 (1.8 Installing VMware ESXi) in Installation Guide.
[?] ft control software UPDATE Disk is not included.
ft control software UPDATE disk is used to update ft control software; it may not be shipped with
the equipment.
[?] OS can be operated after a setup but each module or PCI board is not duplicated. (System FT LED
on the CPU/IO module does not light on green).
Did you abort the installation during a setup such as by closing a window of the programs that are
running?
Installation will be aborted if you finish the programs that are running. Although the operation on
OS will be feasible, modules or PCI boards will not be duplicated properly if you abort the
installation. In this case, you need to reinstall OS according to Chapter 1 (1. Setup procedure) in
Installation Guide.
[?] DISK ACCESS LED blinks in amber.
Did you properly setup the duplex of HDDs?
DISK ACCESS LED lights in amber, if a setup for duplex is not performed. Refer to Chapter 1
(6.1 Error Messages by LED Indication) for details about the indication status of LED.
Refer to Chapter 2 (2. Hard Disk Drive Operations), and set up the duplex of HDDs.
[?] The ft control software does not work even after VMware ESXi has been updated.
Do not update VMware ESXi independently. Also, do not apply any patch data that is not described in
Installation Guide or Update Procedure.
When updating VMware ESXi, the relevant ft control software is required. Follow instructions in
Update Procedure of ft control software. If VMware ESXi is updated independently, ft control
software will not work properly. In this case, you need to re-install ft control software according to
Chapter 1 (1. Setup Procedure) in Installation Guide.
Page 68
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
68
Chapter 1 Maintenance
8.4
Problems When starting ESXi
[?] Unable to start ESXi:
Are Hard Disk Drives properly installed?
Install Hard Disk Drives properly.
Have you changed the BIOS setting?
The set values are different from the default values. Refer to Chapter 1 (1.3 Enabling Internal
Hard Disk Drive) or Chapter 1 (1.4 Enabling Fiber Channel card) (1.7 Setting HBA configuration
by using QLogic) in Installation Guide for details to make correct settings.
Is the internal SAS cable connected to Hard Disk Drive correctly?
Connect the SAS cable properly.
If the SAS cable is not recognized as connected although the above action has been taken, the
Hard Disk Drive may be faulty. Contact your sales representative.
Is the EXPRESSBUILDER DVD inserted?
Eject the EXPRESSBUILDER DVD and reboot.
Is a Flash FDD connected to the server?
Take out the Flash FDD and restart the server.
[?] Machine repeats rebooting at startup:
Is the value of [OS Boot Monitoring Timeout] in the BIOS setting appropriate?
Change the value of [OS Boot Monitoring Timeout] to suit your environment. Refer to Chapter 3
(1. System BIOS) for details.
[?] Wake On LAN does not function:
Is the AC power supplied to both CPU/IO modules?
If the AC power supplied to only one of the CPU/IO module, Wake On LAN may become
unavailable. Supply the AC power to both of CPU/IO modules.
Is Hub/Client fixed as 1000M?
Check the following configurations:
– Set the Hub as "Auto-Negotiation".
– Set the Client as "Auto-negotiate best speed".
Important For both Hub/Client, you cannot use Wake On LAN feature from standby state with
the 1000M fixed configuration.
Do you send Magic Packet to only one of the duplexed LAN?
If you use Wake On LAN under duplexed LAN, you need to send Magic Packets to all of the
duplexed LAN pair(s).
Did you send Magic Packet to 10G LAN connector?
Wake On LAN feature is not supported for the 10G LAN connector.
[?] Fail to duplex CPUs:
Check if the memory configuration is correct.
Check if CPUs or memory (DIMM) recommended by NEC are used.
Page 69
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
69
Chapter 1 Maintenance
8.5
Problems When Occurring Failures
[?] Memory dump (debug information) cannot be collected when a failure occurs:
Do you press the DUMP switch correctly?
Hold down the DUMP switch for 4 to 8 seconds if you would like to collect memory dump by
pressing the switch. If you press DUMP switch shorter than 4 seconds or longer than 8 seconds,
you will not be able to collect memory dump.
Check if you are not using a physical processor of CPU #0 for the virtual machine.
If a physical processor of CPU #0 is allowed to be used for the virtual machine, memory dump
may not be collected even when pressing the DUMP switch. To operate the machine assuming
to collect memory dump, set the value other than "0" for the property of "Scheduling Affinity" of
the virtual machine.
* Setting procedure for "Scheduling Affinity"
Select the target virtual machine from Host Client, and select “Edit Settings” from the menu
displayed by right-clicking. Select “CPU” from “Virtual Hardware” on the displayed Edit Settings
screen to change “Scheduling Affinity”.
Page 70
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
70
Chapter 1 Maintenance
8.6
Problems with Internal Devices and Other Hardware
[?] Fail to access the internal or external devices (or such devices fail to operate)
Are cables properly connected?
Make sure that the interface cables and power cord are properly connected. Also make sure that
the cables are connected in the correct order.
Is the power-on order correct?
When the server has any external devices connected, power on the external devices first, then
the server.
Did you install drivers for connected optional devices?
Some optional devices require specific device drivers. Refer to the manual that comes with the
device to install its driver.
Is option board setting correct?
Usually, no PCI device settings need to be changed. However, depending on the board to be set,
special setting may be required. Refer to the manual that comes with the board for details to
make correct settings.
[?] The keyboard or mouse does not work
Is the cable properly connected?
Make sure that the cable is connected to the connector on the front or rear of the server.
Are the keyboard and mouse are compliant with your server?
Operation of the server with unauthorized devices is not guaranteed.
[?] Screen freezes, keyboard and mouse are disabled:
If the amount of memory is large, it takes time to copy the memory in dual mode and the system
stops working temporarily during the copying, but it is not system trouble.
[?] Unable to access the Hard Disk Drive
Is the Hard Disk Drive supported by the server?
Operation of any device that is not authorized by NEC is not guaranteed.
Is the Hard Disk Drive properly installed?
Check the Hard Disk Drive installation status and the cable connections.
[?] Unable to configure duplexing for Hard Disk Drive:
Unless you perform mirroring (including reconfiguration after failed disks are replaced) in correct
order of Chapter 2 (2. Hard Disk Drive Operations), the mirror may not be (re)configured. Check
if the steps were correct.
[?] Disk ACCESS LEDs on the disks are off:
The LEDs may seem to be off when an excessive amount of access causes the frequent blinking.
Check if the LEDs are blinking green when the access is reduced.
Page 71
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
71
Chapter 1 Maintenance
8.7
Problems with System Operation
[?] The server is not found on the network:
Is the cable connected properly?
Securely connect the proper cable to the network port on the rear of the server. Additionally,
make sure that the cable conforms to the network interface standards.
Are BIOS settings correct?
You can disable the internal network controller using the BIOS setup utility. Check the settings
with BIOS setup utility.
Have you completed protocol and services settings?
Verity that the network driver for the server network controller has been installed. Also verify that
protocol such as TCP/IP or various services have been properly specified.
Is the transfer speed correct?
You can change the transfer speed or configure the setting for onboard LAN controller from Host
Client. Be sure to specify the same transfer speed and duplex mode as those on connected hub.
If you specify "Auto negotiate", make sure that "Auto negotiate" is also specified for the
connected hub.
[?] A CPU/IO module cannot be integrated:
When a component fails and is reintegrated, the following message may be recorded to the
system log and the process is stopped. Such event indicates that the component’s MTBF is
below the threshold and it is judged that repair is necessary. Thus the reintegration process
cannot be completed. Generally replacement of the component will be required, so contact your
sales representative. If reintegrating the component without repair is required for some reason,
consult your sales agent. It is possible to perform reintegration forcefully.
EVLOG: ERROR - x is now STATE_BROKEN / REASON_BELOW_MTBF
(x is a device number)
[?] Screen under changing (distorted display) can be seen when screen resolution is changed:
If screen resolution is changed while the entire system is under high load, screen under changing
(distorted display) may be seen.
This is because screen update is taking time to complete due to high load in the system. This is
not because an error is occurring. The screen will return to normal if you wait awhile.
[?] While setting up a cluster configuration using VMware with EVC enabled, some EVC modes
cannot be set
The following EVC modes are not available for the ft server because the use of some functions of
Intel
®
Xeon® processor are limited in order to implement the synchronization of processors.
- Intel "Haswell" Generation
- Intel "Ivy Bridge" Generation
- Intel "Sandy Bridge" Generation
When enabling EVC for the cluster configuration in the environment such as this server, use the
EVC mode with the setting of Intel "Westmere" Generation or below.
Page 72
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
72
Chapter 1 Maintenance
8.8
Problems When Starting EXPRESSBUILDER on Windows
[?] Unable to read the manuals
Have you installed Adobe Reader to your computer?
To read the manuals, install Adobe Reader in your computer.
Does the "Internet explorer has stopped working" error appear?
Close the dialog box and continue with the operation. If the same error occurs, double-click the
"version.xml" of the root folder on DVD, and then click Yes on the dialog box. After that, you can
read the manual by clicking the link of manual again.
[?] The menu does not appear
Is the file association correct?
Make sure that the ".hta" file extension is associated to "Microsoft HTML application host".
Did you run the menu on this computer?
The autorun function of this computer is not available. Run the following file on DVD directly.
\autorun\dispatcher_x64.exe
Is the OS in the proper state?
The menu does not appear depending on the system registry setting or the timing to set the
DVD/CD. In such case, choose Computer from Explorer and double-click the icon of the set
DVD drive.
[?] Some menu items are gray
Is your system environment correct?
Some software requires administrator authority or needs to be operated on the server. Run on
the appropriate environment.
Page 73
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
73
Chapter 1 Maintenance
8.9
Problems with Bundled Software
[?] NEC ESMPRO Agent (for Linux)
For details of NEC ESMPRO Agent, refer to User’s Guide stored in ft control software Install
DVD.
[?] Device ID in Alert Report
Some Express5800/ft series reports use unique device IDs which correspond to the devices
listed in Chapter 1 (4.2 Device Path Enumeration).
Supplementary explanation for NEC ESMPRO Agent
Notice on Operation of NEC ESMPRO Agent
It may become unable to send report after recovering from hardware failure.
<Workaround>
Perform the following operation after recovered from hardware failure. After replacing the
hardware, confirm that System FT LED is lit green (duplex mode), log in as a root user, and run
the following command.
# /opt/nec/esmpro_sa/bin/ESMRestart
* For the location of System FT LED, refer to Chapter 1 (6.1 Error Messages by LED Indication).
About rpcbind
NEC ESMPRO Agent uses rpcbind function. If rpcbind stops or NEC ESMPRO Agent reboots
while NEC ESMPRO Agent is operating, NEC ESMPRO Agent does not work appropriately.
Run the following command and reboot NEC ESMPRO Agent
# /opt/nec/esmpro_sa/bin/ESMRestart
ntagent Memory Usage
When [Information of server state/constitution] appears, the memory usage of ntagent increases
about 10KB per hour. Do not always display [Information of server state/constitution], but display
it only when failure occurs. When memory usage is enlarged, run the following command and
reboot NEC ESMPRO Agent.
# /opt/nec/esmpro_sa/bin/ESMRestart
Network (LAN) Monitoring Report
The network (LAN) monitoring function defines the line status depending on the number of
transmission packets and the number of packet errors within a certain period. Thus, the LAN
monitoring function may report a line fault or high line load only in a temporary high line
impedance state. If a normal state recovery is reported immediately, temporal high line
impedance may have occurred thus there is not any problem.
Network (LAN)Monitoring Threshold
Because the Express5800/ft series detects hardware faults on the network in the driver level,
NEC ESMPRO Agent does not monitor line faults.
Change of SNMP Community
If the security setting of the SNMP Service of a system, where NEC ESMPRO Agent is installed,
is changed from the default "public" to a community name, change the community settings of
NEC ESMPRO Agent, too.
1. Log in as a root user.
2. Move to the directory where the control panel of NEC ESMPRO Agent is stored.
# cd/opt/nec/esmpro_sa/bin
3. Start the control panel.
# ./ESMagntconf
The Control Panel window appears.
Page 74
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
74
Chapter 1 Maintenance
4. Click [General].
The [General Properties] window appears.
5. Select a SNMP community name used when you retrieve local machine information
in the [SNMP Community] box. (Select by "" key or "" key.)
6. Click [OK] to quit.
The Detail Information of Alert
Detail information of some alert displayed on the alert viewer may be displayed as "Unknown."
File System Monitoring Function
vmfs area is not monitored.
Change Settings of File System Monitoring Function
New settings in thresholds of monitoring interval and free space monitoring are not reflected
immediately after they are changed. They are reflected at the next monitoring interval of
monitoring service.
CPU Load Ratio of snmpd Service
While monitoring the server from NEC ESMPRO Manager, the CPU load ratio of snmpd Service
on NEC ESMPRO Agent side may increase at every monitoring interval (default: 1 minute).
NEC ESMPRO Manager and NEC ESMPRO Agent exchange information through snmpd
Service. If the server status monitoring by NEC ESMPRO Manager is on (default: ON), NEC
ESMPRO Manager regularly issues a request to NEC ESMPRO Agent to get the current status
of the server. In response, NEC ESMPRO Agent checks the status of the server. As a result, the
CPU load ratio of snmpd Service increases temporarily.
If you have trouble of terminating a movie player application, turn off the server status monitoring
by NEC ESMPRO Manager or extend the monitoring interval.
Hang of snmpd Service
Snmpd Service has a module called "SNMP Extended Agent." This module may be registered
when you install some software that uses snmpd Service.
If you start snmpd Service, SNMP Extended Agent is also loaded at the initialization. However, if
the initialization is not completed within a specified period, snmpd Service will hang. It may take
time to complete the initialization due to temporary high load on the system. In this case, wait for
the system load become low enough before restarting snmpd Service.
[?] NEC ESMPRO Manager
For details of NEC ESMPRO Manager, refer to "NEC ESMPRO Manager Installation Guide" in
EXPRESSBUILDER or its help.
Supplementary explanation about [Information of server state/constitution] of NEC ESMPRO
Manager
Display immediately after system startup
If you open [Information of server state/constitution] immediately after the system starts up, the
tree or the state may not be displayed correctly due to high load of the system. In about 20
minutes after the system startup, open [Information of server state/constitution] again.
Display of an Unmounted Sensor
An unmounted sensor is indicated as "Unknown" on [Information of server state/constitution].
Ex: [Information of server state/constitution] - [Enclosure] - [Temperature]
Temperature information
Location: DIMM2 Temp#0
Temperature: Unknown
Threshold: Disabled
Status: Unknown
Page 75
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
75
Chapter 1 Maintenance
Pop-up "Constitution Information has changed." is displayed.
If you are seeing [Information of server state/constitution], pop-up is displayed when hardware
constitution on the monitored server is changed (such as attaching or removing CPU module or
PCI module (I/O module)). The information on the screen is updated afterwards.
System Environment Monitoring
The monitoring of temperature, fan and voltage under [Enclosure] in [Information of server
state/constitution] is set to enable and cannot be changed to disable by default.
"Monitoring" is displayed on the following screen if NEC ESMPRO Manager is used for
monitoring.
[Information of server state/constitution] - [Enclosure] - [Temperature]
[Information of server state/constitution] - [Enclosure] - [Fan]
[Information of server state/constitution] - [Enclosure] - [Voltage]
CPU Information
Check the [CPU] screen under [System] of [Information of server state/constitution] for details of
the CPU information.
* You cannot check the correct information on the [CPU] screen under the [ft system] tree,
The detail information of alert
Detail information of some alert displayed on the AlertViewer may be displayed as "Unknown".
Page 76
8. Troubleshooting
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
76
Chapter 1 Maintenance
8.10
Problems with Optical Disk Drive and Flash FDD
[?] Unable to access or play optical disks such as CD-ROM/DVD-ROMs
Is the CD-ROM properly set in the optical disk drive tray?
There is a holder in the tray to secure the disk. Make sure that the disk is securely placed in the
holder.
Is the ft control software installed?
The DVD drive of the server is available only when ESXi OS is installed for the first time. If you
want to use DVD with the guest OS, connect the DVD drive of the machine on which Host Client
is running to guest OS.
Is the DVD/CD-ROM supported by the server?
For a disk such as a CD with copy guard which does not conform to the CD standard, the
playback of such a disk with the optical disk drive is not guaranteed.
The DVD/CD-ROM for Macintosh is not supported.
[?] Unable to eject a disk using the eject button
Eject the disk in the following procedure.
1. Press the POWER switch to turn off the server (System POWER LED is off).
2. Use a 100 mm long metal pin that is 1.2 mm in
diameter (or uncoil a thick paper clip) and insert it
into the forced eject hole at the front of the tray.
Keep pressing slowly until the tray comes out.
Important Do not use anything that easily breaks such as toothpicks or plastic.
If you still cannot eject the disk, contact the maintenance service
company.
3. Pull the tray out with your hands.
4. Remove the disk.
5. Push the tray back to its original position.
[?] Fail to access (read or write) to the Flash FDD:
Is the Flash FDD write-protected?
Place the write-protect switch on the Flash FDD to the "Write-enabled" Position.
Is the Flash FDD formatted?
Use a formatted Flash FDD. Refer to the manual that comes with the OS for formatting.
Is another Flash FDD connected to this server besides this Flash FDD?
One Flash FDD can only be connected to a USB connector of this server.
[?] The Flash FDD doesn’t operate normally after failover.
Reconnect Flash FDD once after removing.
When the server process failover with the Flash FDD connected, the Flash FDD is not normally
recognized. In that case, once remove the Flash FDD, and reconnect it to this server.
Forced eject hole
Page 77
9. Resetting and Clearing the Server
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
77
Chapter 1 Maintenance
9.
Resetting and Clearing the Server
Refer to this section if the server does not work or if you want to set BIOS settings back to the factory settings.
9.1
Software Reset
If the server halts before starting the OS, press Ctrl + Delete + Alt. This clears all the data in progress in
memory, and restarts the server.
Note To reset the server when it is not frozen, make sure that no processing is in
progress
9.2
Forced Shutdown
Use this function to turn off the power forcibly when an OS command does not shut down the server, POWER
Switch does not turn off the server, or software reset does not work.
Continue to hold POWER Switch of the server for at least 4 seconds. The power is forcibly turned off.
(To turn on the power back again, wait at least 30 seconds after turning off the power).
Note If the remote power-on function is used, cycle the power once to load the OS after
the power has been forcibly turned off, and then turn off the power again by
shutting down the OS.
Press the POWER switch for 4 seconds or longer.
The server is forcedly powered off.
Press this switch for 4 seconds or longer.
Page 78
9. Resetting and Clearing the Server
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
78
Chapter 1 Maintenance
9.3
Clearing BIOS Settings (CMOS Memory)
To set the BIOS settings back to the factory default settings (clearing CMOS memory), use the internal jumper
switch.
You can also clear the password set in the BIOS Setup utility (SETUP) by using the same way.
Tips When the server works, use the BIOS setup utility (SETUP) to return the settings to
the factory defaults.
To clear the password or the CMOS memory, use the corresponding jumper switch illustrated in the figure
below.
Important Do not change any other jumper switch settings. Any change may cause the
server to fail or malfunction.
CMOS Clear Jumper
(CMOSCLR)
PASSWORD Clear Jumper
(PASSCLR)
Protect (factory default) Protect (factory default)
Clear
Clear
Page 79
9. Resetting and Clearing the Server
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
79
Chapter 1 Maintenance
The following instructions show how to clear the CMOS memory and the password.
WARNING
Be sure to observe the following precautions to use the server safety. Failure to
observe the precautions may cause death or serious injury. For details, refer to
Safety Precautions and Regulatory Notices.
Do not disassemble, repair, or alter the server.
Do not remove lithium batteries.
Disconnect the power plug before installing or removing the server.
CAUTION
Be sure to observe the following precautions to use the server safely. Failure to
observe the precautions may cause burns, injury, and property damage. For
details, refer to Safety Precautions and Regulatory Notices.
Make sure to complete installation.
Do not get your fingers caught.
Avoid installing under extreme temperature conditions.
Important Take anti-static measures before operating the server. For detailed
information on static electricity, refer to Chapter 1 (1.8 Anti-static measures)
in Safety Precautions and Regulatory Notices.
Page 80
9. Resetting and Clearing the Server
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
80
Chapter 1 Maintenance
Clearing CMOS memory
1. Disconnect AC power cords from CPU/IO modules 0 and 1.
2. Remove CPU/IO module 0.
Refer to Chapter 2 (5.4 Removing and Installing CPU/IO Module).
3. Remove the top cover.
4. Confirm the position of Clear CMOS Jumper.
5. Change jumper switch to "CMOS CLR" position.
6. Assemble the CPU/IO module 0 and install it to the server.
7. Connect AC power cords to CPU/IO modules 0 and 1 at the same time.
8. Confirm that PRIMARY LED of CPU/IO module 0 lights after a while.
If PRIMARY LED of CPU/IO module 1 lights, disconnect AC power cords from both CPU/IO modules,
wait for 30 seconds, and connect them at the same time.
9. Check that the Module POWER LEDs on CPU/IO modules 0 and 1 starts blinking, and then press the
POWER switch to turn on the server.
10. If the following warning message appears, press the POWER switch to power off the server.
(POST proceeds even when the warning message is displayed.)
WARING
8006: System configuration data cleared by Jumper.
11. Disconnect AC power cords from CPU/IO modules 0 and 1.
12. Remove CPU/IO module 0, and remove its top cover.
13. Change jumper switch setting to its original position (Protect).
14. Assemble the CPU/IO module 0 and install it to the server.
15. Connect AC power cords to CPU/IO modules 0 and 1 at the same time.
16. Confirm that PRIMARY LED of CPU/IO module 0 lights after a while.
If PRIMARY LED of CPU/IO module 1 lights, disconnect AC power cords from both CPU/IO modules,
wait for 30 seconds, and connect them at the same time.
17. Check that the POWER LEDs on CPU/IO modules 0 and 1 starts blinking, and then press the POWER
switch to turn on the server.
18. When the following message appears, press F2 to start BIOS SETUP utility.
Press <F2> SETUP, <F4> ROM Utility, <F12> Network
19. BIOS SETUP starts. On [Save & Exit] menu of BIOS SETUP, select [Load Setup Defaults], and then
[Save Changes and Exit].
Page 81
9. Resetting and Clearing the Server
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
81
Chapter 1 Maintenance
Clearing a password
1. Disconnect AC power cords from CPU/IO modules 0 and 1.
2. Remove CPU/IO module 0.
Refer to Chapter 2 (5.4 Removing and Installing CPU/IO Module).
3. Remove the top cover
4. Confirm the position of Clear Password Jumper.
5. Change jumper switch to "PASS CLR" position.
6. Assemble the CPU/IO module 0, and install it to the server.
7. Connect AC power cords to CPU/IO modules 0 and 1 at the same time.
8. Confirm that PRIMARY LED of CPU/IO module 0 lights after a while.
If PRIMARY LED of CPU/IO module 1 lights, disconnect AC power cords from both CPU/IO modules,
wait for 30 seconds, and connect them at the same time.
9. Check that the Module POWER LEDs on CPU/IO modules 0 and 1 starts blinking, and then press the
POWER switch to turn on the server.
10. If the following warning message appears, press the POWER switch to power off the server.
(POST proceeds even when the warning message is displayed.)
WARING
8007:SETUP Menu Password cleared by Jumper.
11. Disconnect AC power cords from CPU/IO modules 0 and 1.
12. Remove CPU/IO module 0, and remove its top cover.
13. Change jumper switch setting to its original position (Protect).
14. Assemble the CPU/IO module 0, and install it to the server.
15. Connect AC power cords to CPU/IO modules 0 and 1.
Page 82
10. System Diagnostics
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
82
Chapter 1 Maintenance
10.
System Diagnostics
The System Diagnostics runs several tests on the server.
10.1
Test Items
The following items are tested in System Diagnostics.
Memory
CPU cache memory
Hard disk drive
Important To avoid affecting a network and storage system, disconnect a LAN cable,
Fibre Channel, NEC Storage, and other external storage before running
System Diagnostics.
Tips No data is written to the disk on checking hard disk drives.
10.2
Startup and Exit of System Diagnostics
Start up System Diagnostics in the following procedure. (If the server is running, shutdown the system.)
1. Start up EXPRESSBUILDER and select Tool menu from Boot menu.
For information on starting up EXPRESSBUILDER, refer to Chapter 3 (5. Details of
EXPRESSBUILDER).
Note
Choose English if Language Selection Menu appears.
2. Select Test and diagnostics.
3. Select End-User Mode (Basic) to start System Diagnostics. This process takes about three
minutes.
When the diagnostics is completed, the screen display changes as shown below.
See eupro_ug_en.pdf in the \isolinux\diag folder of EXPRESSBUILDER for the End-User Mode
(Professional) feature.
Supervisor-Mode is intended for maintenance personnel.
Page 83
10. System Diagnostics
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
83
Chapter 1 Maintenance
Diagnostics tool title
Shows the name and version of the diagnostic tool.
Test window title
Shows the progress of the diagnostics. "Test End" is displayed when the diagnostics completes.
Test results
Shows the start, end, and elapsed time and completion status of the diagnostics.
Guideline
Shows the details of the keys to operate window.
Test summary window
Shows the results of each test. Move the cursor and press Enter on the cursor line to display the
details of the test.
When an error is detected by the System Diagnostics, the relevant test result in the Test summary
window is highlighted in red, and "Abnormal End" is displayed in the result on the right side.
Move the cursor to the test that detected the error, and press Enter. Take notes about the error
message that has been output to the Detail Information screen and contact the store where you
purchased the product or your maintenance service company.
Test window title
Test results
Test summary window
Guideline
Diagnostics tool title
Page 84
10. System Diagnostics
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
84
Chapter 1 Maintenance
4. Follow the guideline shown at the bottom of the screen, and press Esc.
The Enduser Menu below is displayed.
<Test Result>
Shows the diagnostics completion screen of the above diagnostics.
<Device List>
Shows a list of connected devices.
<Log Info>
Shows the log information of the diagnostics. To save it, connect FAT formatted removable media,
and then select [Save(F)].
<Option>
Optional features can be used from this menu.
<Reboot>
Reboots the server.
5. Select Reboot in Enduser Menu.
The server restarts. Remove EXPRESSBUILDER DVD from the drive.
System Diagnostics is now completed.
Page 85
11. Offline Tools
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
85
Chapter 1 Maintenance
11.
Offline Tools
Offline tools are used for preventive maintenance, failure analysis, and their settings for this product.
11.1
Starting Offline Tools
Start up the offline tools at the following steps.
1. Turn on the peripheral devices and then the server.
2. Press F4 while the message below is displayed.
Press <F2> SETUP, <F4> ROM Utility, <F12> Network
3. Keyboard Selection Menu appears after POST completion.
When you select a keyboard type, the following menu is displayed.
4. Select Maintenance Utility or BMC Configuration to start each tool.
Refer to the next section for more information.
Off-line TOOL MENU
Maintenance Utility
BMC Configuration
Exit
Page 86
11. Offline Tools
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
86
Chapter 1 Maintenance
11.2
Functions of Offline Tools
Offline Tools offers the following functions.
Note When you start the offline tools while RDX is connected to the server, disable RDX
before starting the offline tools by setting RDX to hibernate mode.
Off-line Maintenance Utility
Off-line Maintenance Utility is started when Maintenance Utility is selected. Off-line Maintenance Utility is
used for preventive maintenance and failure analysis for this product. When you are unable to start NEC
ESMPRO due to a failure, Off-line Maintenance Utility can be used to check the cause of the failure.
Note The Off-line Maintenance Utility is intended for maintenance personnel. Consult
with your service representative if any trouble that requires Off-line Maintenance
Utility occurred.
After starting up the Off-line Maintenance Utility, the following features are available to run.
– IPMI Information Viewer
Displays System Event Log (SEL), Sensor Data Record (SDR), and Field Replaceable Unit (FRU)
in IPMI (Intelligent Platform Management Interface) and also back up such information.
Using this feature, system errors and events can be investigated to locate the parts to be replaced.
You can also clear the SEL area, and specify the operation when the SEL area becomes full.
Tips DIMM information (DIMMx FRU#y) displayed when you select Display Most
Recent IPMI Data Field Replaceable Unit (FRU) List is the one for CPU/IO
module on primary side.
For the CPU/IO module on opposite side, the following message will be displayed,
however, it is not a failure.
WARNING!
No Information.
The Device is not detected or it is broken.
– System Information Viewer
Displays information on processor (CPU), BIOS.
Also output the information to a text file.
– System Information Management
Set the information specific to your server (Product information, Chassis information).
BMC Configuration
– It is used for setups of alert functions by BMC (Baseboard Management Controller) and remote
control functions by Management PC.
Refer to Chapter 3 (2. BMC Configuration) for more information.
Page 87
12. Precautions for Operation
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
87
Chapter 1 Maintenance
12.
Precautions for Operation
If a shutdown request is sent to the ESXi host while the CPU module is reinstalled after the server boot or a
synchronization failure, the server may not be shut down successfully. Wait until CPU module has been
reinstalled before making a shutdown request. If the shutdown fails in the case as mentioned above, restart the
server forcibly by pressing the DUMP(NMI) switch. For details on how to use the DUMP(NMI) switch, see
Chapter 1 (7.3 Collecting Memory Dump).
Page 88
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
88
NEC Express5800 Series
Express5800/R320e-E4, R320e-M4,
R320f-E4, R320f-M4
Configuring and Upgrading the System
This chapter describes procedure for change configuration and installing internal option devices.
1. ftSys Management Appliance
Describes the specifications of ftSys Management Appliance (virtual machine).
2. Hard Disk Drive Operations
Describes how to duplex hard disk drives and how to replace the failed hard disk drives.
3. Duplex LAN Configuration
Describes how to configure duplex LAN.
4. Miscellaneous Configuration
5. Installing and Replacing Optional Devices
Describes procedure for installing, replacing, or removing internal option devices.
Page 89
1. ftSys Management Appliance
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
89
Chapter 2 Configuring and Upgrading the System
1.
ftSys Management Appliance
1.1
Overview
The ftSys Management Appliance is a CentOS-based virtual machine hosted by the VMware ESXi hypervisor
on your ftServer system. ft control software runs on ftSys Management Appliance. ft control software
monitors/manages the state of the ESXi host system at all times and provides commands to change the
system settings and access the system information.
The specifications of ftSys Management Appliance (virtual machine) are as follows.
CPU 1vCPU
Memory 2048MB
Disk 16GB
Network 1port
Guest OS CentOS 7.3
Tips For detailed information on CentOS, refer to the Web site below.
http://www.centos.org/
ftSys Management Appliance
ft Server
ft control
software
VMware ESXi
Page 90
1. ftSys Management Appliance
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
90
Chapter 2 Configuring and Upgrading the System
1.2
Steps for Accessing ftSys Management Appliance
Access the ft management appliance by using Host Client installed on the management PC. Right-click the ft
management appliance of the Navigator of Host Client and select [Console] and [Launch remote console].
You can select this item by clicking the “Console” tab displayed on the left-hand pane or from the “Actions”
tab.
All the administrative commands that are described in this document are supposed to run on ftSys
Management Appliance.
For Host Client, refer to the “Installation Guide” of this series.
1.3
Precautions for Using ftSys Management Appliance
To enable the ft server to operate continuously, it is necessary to operate the ft Management Appliance
continuously. If the ft Management Appliance is shut down for any other product than maintenance, the
redundancy of the ft server may be lost. Specifically, note the following precautions when operating the ft
Management Appliance.
● Do not migrate or delete the ftSys Management Appliance. To ensure continuous uptime, the
appliance must be present and running on your ftServer system at all times.
● Do not restart or shutdown the ftSys Management Appliance, unless instructed to do so for updates or
troubleshooting purposes. The appliance is also configured to start and shut down automatically with
your ESXi host. Do not change this configuration.
● Deploy only one ftSys Management Appliance per system, and configure it to manage only the ESXi
host on which it is installed.
● Deploy the ftSys Management Appliance only in the VMFS volume located on the boot disk for your
system, whether the boot disk is an internal disk or external storage volume. Check that the boot disk
can be accessed only from the supported ft server.
● For configuration changes below, running appropriate commands is required. For details, refer to
Chapter 1 (2.3 Precautions for Changing the Configuration after Setup) of Installation Guide.
- To change the IP address or hostname of ESXi host, root user password
- To change the IP address or host name of log server
- To change the firewall rules for ftSys Management Appliance
● Please ensure that the appliance remains on the same network as the ESXi host, and that the
appliance and host can still communicate with each other.
● Do not enable SELinux in the ftSys Management Appliance.
Page 91
1. ftSys Management Appliance
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
91
Chapter 2 Configuring and Upgrading the System
● As long as there are no directions from maintenance personnel, ft peculiar service on ftSys
Management Appliance or an ESXi host is not stopped, or a starting setup is not changed.
● Use only the root user to run administrative commands in the appliance. Avoid creating additional
administrative users in the appliance. The default root password is "ftServer" and changing the
password is recommended from the security viewpoint.
● To avoid directly logging in to ftSys Management Appliance with the root user from security viewpoint,
log in to ftSys Management Appliance with the ftadmin user, and then, gain root privileges by the su
command before running the administrative commands. The default ftadmin password is "ftadmin" and
changing the password is recommended as well as that of the root user.
● Avoid deploying your own scripts and third-party agents in the ftSys Management Appliance.
● Avoid manually updating the CentOS software or manually adding and removing RPM software
packages in the ftSys Management Appliance.
● ftSys Management Appliance is monitored by the ESXi host, and even if it stops, it is automatically
restarted.
● The duplicated state continues even when ftSys Management Appliance stops. However, when a
module is isolated and duplication ends while ftSys Management Appliance is stopped, the module is
not embedded again while ftSys Management Appliance is stopped.
● When your ft Server is included in the VMware vSphere HA cluster, set “VM restart priority” of ftSys
Management Appliance to other than “disable”. When it is set to “disable”, the ft Server may not be
duplicated properly.
Page 92
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
92
Chapter 2 Configuring and Upgrading the System
2.
Hard Disk Drive Operations
NEC Express5800/ft series duplicates the hard disk drive to secure data integrity by Software-RAID.
Important It is recommended to create only a system partition on the disk specified at
installation of VMware ESXi.
When you have created the VMFS data store area on the disk with specified at
installation of VMware ESXi, note that all area of the disk is cleared at the time of
the reinstallation of the VMware ESXi.
2.1
Operable disk configuration
Duplication must be configured for all the internal hard disk drives in NEC Express5800/ft series.
The hard disk drives redundancy is configured by Software RAID with the internal disks of corresponding
slots.
The internal hard disk drive path and device name
Slots corresponding to the mirroring process
Corresponding slots
Slot 0 (10/40/1) Slot 0 (11/40/1)
Slot 1 (10/40/2) Slot 1 (11/40/2)
Slot 2 (10/40/3) Slot 2 (11/40/3)
Slot 3 (10/40/4) Slot 3 (11/40/4)
Slot 4 (10/40/5) Slot 4 (11/40/5)
Slot 5 (10/40/6) Slot 5 (11/40/6)
Slot 6 (10/40/7) Slot 6 (11/40/7)
Slot 7 (10/40/8) Slot 7 (11/40/8)
Slot 0
Slot 1 Slot 7
Slot 6
Slot 5
Slot 4
Slot 3
Slot 2
Slot 7
Slot 0 Slot 6
Slot 5
Slot 4
Slot 3
Slot 2
Slot 1
10/40/1 10/40/3 10/40/5 10/40/7
10/40/2
10/40/4
10/40/6
10/40/8
11/40/1
11/40/3
11/40/5 11/40/7
11/40/2 11/40/4 11/40/6 11/40/8
Page 93
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
93
Chapter 2 Configuring and Upgrading the System
To operate the internal hard disk drive, use the kernel device names. The kernel device name is decided by
being detected by system when the hard disk drive is inserted or system is booted. The kernel device name is
displayed as “vmhban:C0:Tx:L0”.
The “n” of “vmhban” represents the last digit of I/O module (10, 11). ”x” of "Tx" represents a target number.
The target number is obtained by the slot number plus one is set as the target number.
You can confirm the kernel device name corresponding to the slot by using “/opt/ft/bin/ftsmaint” command.
If you need to confirm the kernel device name of internal hard disk drive installed in the slot0 of I/O module 0
(10), run the following command. In the following example, the kernel device name is vmhba0:C0:T1:L0.
# /opt/ft/bin/ftsmaint ls 10/40/1
H/W Path : 10/40/1
Description : Disk Drive
State : ONLINE
Op State : DUPLEX
Reason : NONE
Modelx : HGST:HUC101812CSS200
Firmware Rev : A920
Serial # : 06G094AH
Device Name : disk_a
Udev Device Names : Kernel Device Names : vmhba0:C0:T1:L0
Endurance : MTBF Policy : useThreshold
MTBF fault class: critical noncritical removal
Fault Count: 0 0 0
Last Timestamp: - - Replace Threshold: 0 0 0
Evict Threshold: 2147483647 604800 86400
Value: 0 0 0
Minimum Count: 1 4 2
MTBF fault class: aborts
Fault Count: 0
Last Timestamp: Replace Threshold: 0
Evict Threshold: 86400
Value: 0
Minimum Count: 2
To configure the redundant configuration, use “esxcli storage mpm” command. On this occasion, the RAID
device name is expressed as “mpmn”(“n” is 0~7).
Page 94
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
94
Chapter 2 Configuring and Upgrading the System
The RAID device names assigned to internal hard disk drives
Important When the status of each disk becomes "resync" "recovery" "check" or "repair"
do not add a disk, insert/remove HDD, power off or restart the system. Wait until
the status indication of Raid device disappears and the status of each disks
become "in_sync". Check the status of RAID using the "esxcli storage mpm"
command, which is described later in this document.
Use only the hard disk drives specified by NEC. There is a risk of hard disk as
well as the entire device breakdown when you install a third-party hard disk
drive.
Purchase two, paired hard disk drive of the same model to configure the hard
drive redundancy. For information on which HDD suits this device the best, ask
your sales agent.
Page 95
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
95
Chapter 2 Configuring and Upgrading the System
2.2
esxcli Command Syntax
The esxcli command syntax used in this document is as follows.
• To check the state of the disk
esxcli -s <IP address or hostname of ESXi host> storage mpm list
• To isolate a disk from the RAID configuration
esxcli -s <IP address or hostname of ESXi host> storage mpm fail –v <Device name>
-d <Kernel device name>
• To remove a disk from the RAID configuration
esxcli -s <IP address or hostname of ESXi host> storage mpm remove –v <Device
name> -d <Kernel device name>
• To stop a disk from the RAID configuration
esxcli -s <IP address or hostname of ESXi host> storage mpm stop –v <Device name>
• To add a disk to the RAID configuration
esxcli -s <IP address or hostname of ESXi host> storage mpm add –v <Device name>
-d <Kernel device name>
• To add disks (RAID configuration)
esxcli -s <IP address or hostname of ESXi host> storage mpm create –v <Device
name> --disk1= <Kernel device name> --disk2=<Kernel device name>
Tips In some cases, the following error message may be displayed as the result of the esxcli
command.
# esxcli -s ftESXi storage mpm list
Enter username: root
Connect to ftESXi failed. Server SHA-1 thumbprint:
48:01:F6:82:E1:92:F7:35:BE:C4:37:E3:9C:89:58:E6:03:9B:FE:95 (not
trusted).
If the above error message is output, execute the esxcli command with '--thumbprint'
option. Specify the thumbprint shown in the error message for the '--thumbprint' option.
# esxcli
--thumbprint=48:01:F6:82:E1:92:F7:35:BE:C4:37:E3:9C:89:58:E6:03:9B
:FE:95 -s ftESXi storage mpm list
For details of the esxcli command, see the documents from VMware.
Page 96
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
96
Chapter 2 Configuring and Upgrading the System
2.3
Confirm Hard Disk Drives status
To confirm the hard disk drive status, use esxcli storage mpm list command.
The following display is an example when esxcli storage mpm list command is run.
Note
The kernel device name is defined at the time when disk is detected. Accordingly, it is
subject to be changed if the hard disk drive is relocated or the system is rebooted. You
need to confirm the current disk status by running the esxcli storage mpm list
command every time you perform disk operation.
# esxcli –s xxx.xxx.xxx.xxx storage mpm list
Info
-----------------------------------------------------mpm0 : 292968640 blocks (286102 MB) [2/2]
\_ vmhba0:C0:T1:L0 (10/40/1) [ in_sync ]
\_ vmhba1:C0:T1:L0 (11/40/1) [ in_sync ]
Page 97
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
97
Chapter 2 Configuring and Upgrading the System
2.4
Replacing a hard disk drive
To replace a failing hard disk drive, follow the steps below. Replace a hard disk drive when the CPU/IO
module 0 and 1 are powered on.
2.4.1
Identifying a failing disk
This section provides information on how to identify a failing hard disk drive.
Important This must be operated by root user.
1. Run esxcli -s <IP address or hostname of ESXi host> storage mpm list.
2. Check the failed disk form the displayed info.
The following example shows that a failure occurs in the built-in hard disk drive inserted into slot 0 of I/O
module 1, and the status is [faulty]. The hard disk drive may be separated from the RAID configuration
depending on the failure condition, and may become the Unused status.
When you confirm the slot0 of I/O Module1 by “/opt/ft/bin/ftsmaint ls” command, it is displayed as follows.
# esxcli –s xxx.xxx.xxx.xxx storage mpm list
Info
-----------------------------------------------------mpm0 : 292968640 blocks (286102 MB) [2/2]
\_ vmhba0:C0:T1:L0 (10/40/1) [ in_sync ]
\_ vmhba1:C0:T1:L0 (11/40/1) [ faulty ]
# cd /opt/ft/bin/
# ./ftsmaint ls 11/40/1
H/W Path : 11/40/1
Description : Disk Drive
State : BROKEN
Op State : SHOT
Reason : NONE
. . . . . . .
. . . . . . .
Page 98
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
98
Chapter 2 Configuring and Upgrading the System
2.4.2
Restoring the redundant configuration manually
This section provides information on how to replace a failing internal hard disk drive and restore duplication.
Important This must be operated by root user.
While the replaced hard disk drive is restoring to the RAID configuration, do not
stop/restart the system when the reconfigured each RAID device is in
RECOVERY. Wait until the status indication of them disappears and the status
of each disks become "in_sync". (It comes to take time depending on disk
space.)
1. To isolate the failing hard disk drive from redundant configuration, run the esxcli storage mpm fail
and esxcli storage mpm remove commands with device name and kernel device name specified.
Note
The remove command will fail if hard disk drive status is other than [faulty]. You should
change disk status by running fail command in advance. Run the remove command
without intermission because the disk status returns to [in_sync] in a short time after
running the fail command.
The following is an example of command prompt for the procedure from isolating the internal hard disk
stored in the slot 0 of I/O Module 1.
# esxcli –s xxx.xxx.xxx.xxx storage mpm list
Info
-----------------------------------------------------mpm0 : 292968640 blocks (286102MB) [2/2]
\_ vmhba0:C0:T1:L0 (10/40/1) [ in_sync ]
\_ vmhba1:C0:T1:L0 (11/40/1) [ faulty ]
# esxcli –s xxx.xxx.xxx.xxx storage mpm fail –v mpm0 –d vmhba1:C0:T1:L0
# esxcli –s xxx.xxx.xxx.xxx storage mpm remove -v mpm0 –d vmhba1:C0:T1:L0
# esxcli –s xxx.xxx.xxx.xxx storage mpm list
Info
----------------------------------------------------- mpm0 : 292968640 blocks (286102MB) [1/2]
\_ vmhba0:C0:T1:L0 (10/40/1) [ in_sync ]
Unused disks:
- vmhba1:C0:T1:L0 (11/40/1)
Page 99
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
99
Chapter 2 Configuring and Upgrading the System
2. Remove the hard disk drive from the system, and then, insert a new disk.
Please wait while the system to recognize the disk.
3. To restore the redundant configuration, run the "esxcli storage mpm add" command with RAID device
name and kernel device name corresponding to the hard disk drive specified.
Note Synchronization may start automatically when a new hard disk drive is inserted.
In this case, restoration by running add command is not necessary.
4. Confirm that resync is started.
In the example below, it is shown that the progress ratio of synchronization is 51.6%, and 32.8 minutes is
required to complete synchronization. When the progress is no longer displayed and both kernel devices
show [in_sync], the synchronization is completed.
# esxcli –s xxx.xxx.xxx.xxx storage mpm list
Info
-----------------------------------------------------mpm0 : 292968640 blocks (286102MB) [1/2]
\_ vmhba0:C0:T1:L0 (10/40/1) [ in_sync ]
:
:
:
# esxcli –s xxx.xxx.xxx.xxx storage mpm list
Info
-----------------------------------------------------mpm0 : 292968640 blocks (286102MB) [1/2]
\_ vmhba0:C0:T1:L0 (10/40/1) [ in_sync ]
Unused disks:
- vmhba1:C0:T1:L0 (11/40/1)
# esxcli –s xxx.xxx.xxx.xxx storage mpm add -v mpm0 –d vmhba1:C0:T1:L0
# esxcli –s xxx.xxx.xxx.xxx storage mpm list
Info
------------------------------------------------------------------mpm0 : 292968640 blocks (286102 MB) [2/2]
| recover=51.6% (73879680/292968640) finish=32.8min (35088K/s)
\_ vmhba0:C0:T1:L0 (10/40/1) [ in_sync ]
\_ vmhba1:C0:T1:L0 (11/40/1) [ syncing ]
# esxcli –s xxx.xxx.xxx.xxx storage mpm list
Info
-----------------------------------------------------mpm0 : 292968640 blocks (286102 MB) [2/2]
\_ vmhba0:C0:T1:L0 (10/40/1) [ in_sync ]
\_ vmhba1:C0:T1:L0 (11/40/1) [ in_sync ]
Page 100
2. Hard Disk Drive Operations
Express5800/R320e-E4, R320e-M4, R320f-E4, R320f-M4 Maintenance Guide (VMware)
100
Chapter 2 Configuring and Upgrading the System
2.4.3
Reducing resync time
If resynchronization of the hard disk drive requires much time, you can reduce the resync time to change the
minimum/maximum resync speed to 0 KB/sec.
Tips By specifying 0 (zero) for the minimum/maximum synchronization speed, the
synchronization speed will not be limited and the synchronization will work with the best
effort.
Note
The minimum/maximum resync speed affects system performance. If it is changed, the
system performance may become lower, therefore care must be taken in changing
configuration.
Run the following command to confirm the current speed.
The example below shows the default setting (minimum resync speed: 1,000 KB/sec, maximum resync
speed: 0 KB/sec).
Run the following command to specify the minimum/maximum resync speed to 0 KB/sec for all hard disk
drives.
To confirm or specify the minimum/maximum resync speed for individual hard disk drive, run the command
with "-v <Device name>". The example below shows that the command is run for device name mpm1.
Note
The minimum/maximum resync speed is reverted when the ESXi host is rebooted. To use
the setting persistently, let this command be run every time when the ESXi host is started.
Describe the following line in "/etc/rc.local.d/local.sh" file of ESXi host.
esxcli storage mpm speedLimit --min=0 --max=0
Describe the above command in the line above "exit 0".
Refer to the Knowledge Base of VMware for how to describe the /etc/rc.local.d/local.sh file.
<VMware, Knowledge Base - Modifying the rc.local or local.sh file in ESX/ESXi to run
commands while booting (2043564)>
https://kb.vmware.com/kb/2043564
# esxcli –s xxx.xxx.xxx.xxx storage mpm speedLimit
Volume Minimum Maximum
------ ------- -------
volume 1000 0
# esxcli –s xxx.xxx.xxx.xxx storage mpm speedLimit --min=0 --max=0
Volume Minimum Maximum
------ ------- -------
volume 0 0
# esxcli –s xxx.xxx.xxx.xxx storage mpm speedLimit -v mpm1 --min=0
--max=0
Volume Minimum Maximum
------ ------- -------
volume 0 0
Loading...