======================================================================
LSI SMI-S Provider (for VMware ESXi 5/6)
======================================================================
[Software name ] LSI SMI-S Provider (00.50.V0.11)
[Registered name ]
esxi50_vmware-esx-provider-lsiprovider.zip (for VMware ESXi 5.0/5.1)
esxi55_vmware-esx-provider-lsiprovider.zip (for VMware ESXi 5.5/6.0)
[Copyright (C) ] Avago Technologies
[Supported server models]
- Express5800/A1080a-D
- Express5800/A1080a-E
- Express5800/A1080a-S
- Express5800/A1040b
- Express5800/A2010b
- Express5800/A2020b
- Express5800/A2040b
- Express5800/A1040c
- Express5800/A2010c
- Express5800/A2020c
- Express5800/A2040c
[RAID Controllers]
- NE3104-001 RAID Controller (256 MB, RAID 0/1/5/6)
- NE3104-004 RAID Controller (1 GB, RAID 0/1/5/6)
- NE3303-173 RAID Controller (512MB, RAID 0/1/5/6)
- NE3303-168 RAID Controller (1GB, RAID 0/1/5/6)
- NE3303-H001 RAID Controller (1GB, RAID 0/1/5/6)
- NE3303-177 RAID Controller (1GB, RAID 0/1/5/6)
- NE3303-178 RAID Controller (2GB, RAID 0/1/5/6)
- NE3303-H004 RAID Controller (2GB, RAID 0/1/5/6)
[Supported users ] All users who use the servers above with the
VMware ESX below installed.
- VMware ESXi 5.0 Update 3 Patch 08 or later
- VMware ESXi 5.1 Update 2 Patch 05 or later
- VMware ESXi 5.5 Update 2 or later
- VMware ESXi 6.0 or later (*)
* If you manage RAID System from NEC ESMPRO
Manager, it requires VMware ESXi 6.0b or later.
[Software type ] Utility
[Format ] zip
======================================================================
[Software Introduction]
LSI SMI-S Provider (hereinafter called "this software") is a module
required to manage the RAID System on the VMWare ESXi 5 or later
virtualized platform.
To manage the above RAID Controllers from a vSphere Client or NEC
ESMPRO Manager, this module needs to be installed in the VMWare ESXi 5
or later virtualized platform.
Carefully read the following user license agreement for NEC software
before using this software.
If you do not agree to the terms of the agreement, do not download this
software. By downloading this software, you agree to be bound by the
terms of the agreement.
[User license agreement for NEC software]
This user license agreement is an agreement between you and NEC
Corporation (hereinafter called "NEC").
Under the following terms of this agreement, NEC grants you the right
to use the software program (hereinafter called "licensed program"),
and you are to agree to the terms. You are to take any responsibility
for the selection of, installation of , use of, or results from the
use of, the licensed program.
1. Term and termination
(1) This user license agreement is effective from the date you receive
this software product.
(2) You may terminate it under this license agreement at any time by
giving NEC a written notice no less than one month prior to the
date you wish to do so.
(3) NEC may terminate your right to use the licensed program at any
time, if you fail to comply with the terms of this user license
agreement.
(4) Your right to use the licensed program continues to exist until
it is terminated in accordance with the provisions of this user
license agreement.
(5) Immediately upon termination of your right to use the licensed
program, all of your other rights under this user license
agreement will terminate. You must destroy the licensed program,
all copies thereof, and related documents (e.g., manuals) provided
with the licensed program immediately upon termination of your
right to use the licensed program.
2. Use right
(1) You may use the licensed program only on NEC Express5800 series
servers in which the following VMware ESX is installed.
- VMware ESXi 5.0 Update 3 Patch 08 or later
- VMware ESXi 5.1 Update 2 Patch 05 or later
- VMware ESXi 5.5 Update 2 or later
- VMware ESXi 6.0 or later
3. Copy, modify, or merge copies of the licensed program
(1) You may make a single copy of the licensed program only for your
backup purpose in case of the licensed program data loss or
corruption; provided, however, that this does not apply to the
case where the licensed program is installed in a fixed memory.
In this case, you may make a single copy of the licensed program
only for your backup and storage puropose in case of loss or
corruption of the storage medium of the licensed program.
(2) You must display the copyright and other proprietary rights
notices that appear on and in the licensed program on all copies
of the licensed program.
(3) Unless otherwise specified in this user license agreement, you may
not use, copy, modify, or merge copies of the licensed program,
publish or distribute any information contained in or materials of
the licensed program in publications or through networks, or make
your own decision on handling it in any other way.
(4) You may not copy the related documents (e.g., manuals) provided
with the licensed program or publish them in publications or
through networks under any circumstances.
(5) This user license agreement does not transfer the intangible
property rights associated with the licensed program to you.
4. Transfer to third party
(1) You may transfer all of your rights under this user license
agreement to a third party, provided that all of the following
conditions are satisfied:
(a) You transfer this user license agreement, the licensed program
all copies of the licensed program,, and all related documents
(e.g., manuals) provided with the licensed program to the third
party, and retain none of them.
(b) The transferee agrees to the terms of this user license agreement.
(2) Unless otherwise specified in this user license agreement, you may
not rent or lease the use right in the Licensed Software, transfer
the licensed program to the third party, transport the licensed
program, or make your own decision on handling it in any other way.
5. Decompilation
You may not carry out reverse engineering of, decompile, or disassemble
the licensed program.
6. Warranty
(1) NEC does not provide any guarantee for the licensed program. You
are liable to pay for all cost arising from problems as a result
of the use of the licensed program.
(2) Irrespective of the term (1), when NEC corrects licensed-program
errors (bugs), NEC may, at its discretion, provide an error-corrected
program, a program for correction (hereinafter called a modification
program), or information for correction by an NEC-decided method.
The modification program provided to you is regarded as the licensed
program.
7. Limitation of liability
NEC assumes no liability for your lost profit, damages arising from
special circumstances (including damages which NEC can or could foresee),
or damages claimed to you by any third party.
8. Others
Disputes over this user license agreement are to be settled at the
Tokyo District Court as the exclusively agreed competent court.
----------------------------------------------------------------------
[Setup Procedure]
[Update Procedure]
(1) Select [Troubleshooting Options] from the direct console. Enable
ESXi Shell access from SSH or the direct console, and log
into ESXi Shell as a user with administrator rights. (To log into
ESXi shell from the direct console, press [Alt] + [F1].)
(2) Execute the following command to check whether the previous
version of LSI SMI-S Provider is already installed.
If the line starting with "LSIProvider" or "lsiprovider" is
displayed, previous one is already installed. Proceed to the next
step.
If nothing is displayed,, refer to [Installation Procedure] for
fresh installation.
# esxcli software vib list | grep -i lsiprovider
(3) Uninstall the previous LSI SMI-S Provider by following
[Uninstallation Procedure] for previous one.
(4) Install new SMI-S Provider by following
[Installation Procedure] below.
[Installation Procedure]
(1) Unzip the "esxi??_vmware-esx-provider-lsiprovider.zip" file and copy the
vib file from the unzipped file to the client terminal where vSphere
Client is installed.
(2) Start vSphere Client. Connect to ESXi as a user with administrator rights
and enter the Maintenance Mode.
To switch ESXi to maintenance mode, connect to ESXi with vSphere
Client, right-click the ESXi icon in the inventory, and select
[Enter Maintenance Mode].
(3) Select the ESXi icon in the inventory and click the [Configuration]
tab.
(4) Select [Storage] in [Hardware] to display a list of datastores.
Right-click the datastore to which you are going to upload the
vib file and select [Browse Datastore].
(5) The datastore browser will appear.
Click [Create New folder] from the toolbar to create a "vib"
folder.
(6) Click the [Upload] icon from the toolbar and select [Upload File].
(7) When an item upload window appears, select the vib file and then
click [Open].
(8) If a warning dialog box for upload/download appears, select [Yes].
(9) When the [Uploading] dialog box disappears, upload is completed.
(10) Select [Troubleshooting Options] from the direct console. Enable
ESXi Shell access from SSH or the direct console, and log
into ESXi Shell as a user with administrator rights. (To log into
ESXi shell from the direct console, press [Alt] + [F1].)
(11) Execute the following command to install the LSI SMI-S Provider:
# esxcli software vib install -v [vib file]
In [vib file], specify an absolute path as below.
/vmfs/volumes/datastore1/vib/vmware-esx-provider-lsiprovider.vib
Once the provider installation is complete, the following message
will appear.
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: [Provider Name]
VIBs Removed:
VIBs Skipped:
(12) Execute the reboot command to restart the server.
(13) Log into ESXi Shell and execute the following command to
check that the LSI SMI-S Provider has been successfully installed.
# esxcli software vib list | less
(14) Delete the uploaded vib file and then log out from ESXi Shell.
(If you logged into ESXi Shell from the direct console, execute
the exit command and then press [Alt] + [F2].)
(15) Select [Troubleshooting Options] from the direct console and then
return the ESXi Shell access settings to their original values.
Also connect to ESXi from vSphere Client and then exit maintenance
mode.
[Uninstallation Procedure]
(1) Start vSphere Client. Connect to ESXi as a user with administrator rights
and enter the Maintenance Mode.
To switch ESXi to maintenance mode, connect to ESXi with vSphere
Client, right-click the ESXi icon in the inventory, and select
[Enter Maintenance Mode].
(2) Select [Troubleshooting Options] from the direct console. Enable
ESXi Shell access from SSH or the direct console, and the log
into ESXi Shell as a user with administrator rights. (To log into ESXi
shell from the direct console, press [Alt] + [F1].)
(3) Execute the following command to uninstall the LSI SMI-S Provider.
# esxcli software vib remove -n lsiprovider
(4) Execute the reboot command to restart the server.
(5) Select [Troubleshooting Options] from the direct console and then
return the ESXi Shell access settings to their original values.
Also connect to ESXi from vSphere Client and then exit maintenance
mode.
[General Notices]
1. When using NEC ESMPRO Manager
(1) The version of NEC ESMPRO Manager that can manage the system in which
this software is installed must be Ver.6.01 or later.
If you want to manage RAID System in VMware ESXi 6.0b or later,
it requires NEC ESMPRO Manager Ver.6.05 or later.
(2) The following symptoms occur when you monitor RAID Controllers using
NEC ESMPRO Manager with LSI SMI-S Provider on VMware ESXi 5 or later.
See the "SMI-S_Provider_ESMPRO_SM_Notification.pdf" file attached to
this page for details.
(a) For "Disk Array Information" in Logical Drive Property, NEC
ESMPRO Manager does not display the part "order n/m," which
indicates what number drive the logical drive is in the Disk Array.
(b) In Logical Drive Property, NEC ESMPRO Manager does not display "Cache
Mode (Current)" with some RAID Controllers.
(c) You can select only one Disk Array for a Dedicated Hot Spare.
(d) When you create a Dedicated Hot Spare to Logical Drive belonging
to more than one Disk Array and then execute forcible offline to the
Physical Device, the device may be displayed as "Global Hot Spare"
instead of "Dedicated hot Spare".
(e) The "Capacity" property for SSD Cache Drive displays capacity at the
point when SSD Cache Drive was created.
(f) When you remove and insert Physical Device which constitutes SSD Cache
Drive, the Physical Device may remain to be displayed as a member of SSD
Cache Disk Array.
(g) From VMware ESXi 5 or later to NEC ESMPRO Manager, event notification
may delay in the event of HDD Power Status change (Power Saving/
Transitioning/ On).
(h) VMware ESXi 5 or later may fail to send information to NEC ESMPRO
Manager if the RAID System configuration changes frequently in a short
period of time.
(i) When Logical Drive Offline occurred, RAID System information may not
get correctly until removing failed Physical Devices.
2. When using vSphere Client
(1) The following symptoms occur when you monitor RAID Controllers using
vSphere Client with LSI SMI-S Provider on VMware ESXi 5 or later.
See the "SMI-S_Provider_vSphere_Client_Notification.pdf" file attached to
this page for details.
(a) The value of Battery Status in the Reading Colum may be "Partially
Charged" on the Hardware Health Status window in the environment where
the Flash Backup Unit is connected to the RAID controller.
(b) The value of Battery Status in the Reading Colum may be "Unknown"
on the Hardware Health Status window in the environment where the battery
is connected to the RAID controller.
(c) The status of the battery indicates "Unknown" on the Hardware Health
Status window during the battery refresh.
(d) When a problem occurs in Physical Device, the label of Physical Device
indicates "UNDEFINED" and the status becomes "Warning" on the Hardware
Health Status window.
(e) After Hot Spare rebuilding, the failed Physical Device remains in
the label of the Logical Drive on the Hardware Health Status window.
(f) In the environment with many Physical Devices or Logical Drives, when
you connect the server using vSphere Client immediately after starting
VMware ESXi 5 or later, there may be the case that no storage node is
displayed on the Health Status window.
(g) In the environment where more than one RAID Controller is connected and
the status of the RAID Controller is "Alert" or "Warning" on the Hardware
Health Status window, the RAID Controller with a problem may not be
identified.
(h) VMware ESXi 5 or later may fail to send information to vSphere Client
if the RAID System configuration changes frequently in a short period of
time.
(i) Restart vSphere Client if you want to get latest status of the battery
or Flash Backup Unit.
(j) Use WebBIOS if you want to identify which Physical Device is a part of
the Logical Drive.
3. When managing RAID System which is mixed with external SAS Controller on
VMware ESXi 5.x
(1) When managing RAID System which is mixed with external SAS Controller,
LSI SMI-S may not work correctly and getting RAID System informaion may
fail.
When mixing external SAS Controller with RAID Controller, Please take
the following steps to prevent from trouble.
(a) Start vSphere Client. Connect to ESXi as a user with administrator
rights and enter the Maintenance Mode.
To switch ESXi to maintenance mode, connect to ESXi with vSphere
Client, right-click the ESXi icon in the inventory, and select
[Enter Maintenance Mode].
(b) Select [Troubleshooting Options] from the direct console. Enable
ESXi Shell access from SSH or the direct console, and the log
into ESXi Shell as a user with administrator rights. (To log into ESXi
shell from the direct console, press [Alt] + [F1].)
(c) Execute the vi command to add following 4 lines to auto-execute file
when ESXi startup.
auto-execute file path and adding position are depending on version of
VMware ESXi.
[adding lines]
/etc/init.d/sfcbd-watchdog stop
rm -f /usr/lib/cim/libstorelibir.so
rm -f /usr/lib/cim/libstorelibir-2.so
/etc/init.d/sfcbd-watchdog start
[auto-execute file path and adding position]
- VMware ESXi5.0 or later
Add above lines at the foot of /etc/rc.local .
- VMware ESXi5.1 or later
Add above lines at just befor line of "exit 0" line on
/etc/rc.local.d/local.sh .
(d) Execute the reboot command to restart the server.
(e) Select [Troubleshooting Options] from the direct console and then
return the ESXi Shell access settings to their original values.
Also connect to ESXi from vSphere Client and then exit maintenance
mode.
(f) After these steps, following messages may log to syslog.
These messeages are harmless and please ignore.
[example of messages]
sfcbd: INTERNAL Failed to load library: /usr/lib/cim/libstorelibir.so
sfcbd: INTERNAL Error was: /usr/lib/cim/libstorelibir.so: cannot open shared object file: No such file or directory
sfcbd: INTERNAL StoreLibFacadeIT1::Constructor: Failed to load library for Controller.
sfcbd: INTERNAL StoreLibFacadeIT1::getInstance: Failed to load library for IR Controller.
sfcbd: INTERNAL StorelibAdapter::getFacadeInstanceIR2 - getFacadeInstance for storelibir2
sfcbd: INTERNAL Failed to load library: /usr/lib/cim/libstorelibir-2.so
sfcbd: INTERNAL Error was: /usr/lib/cim/libstorelibir-2.so: cannot open shared object file: No such file or directory
sfcbd: INTERNAL StoreLibFacadeIR2::Constructor: Failed to load library for Controller.
sfcbd: INTERNAL StoreLibFacadeIR2::getInstance: Failed to load library for IR2 Controller.
sfcbd: INTERNAL Failed to load library: /usr/lib/cim/libstorelibir-2.so
sfcbd: INTERNAL Error was: /usr/lib/cim/libstorelibir-2.so: cannot open shared object file: No such file or directory
sfcbd: INTERNAL StoreLibFacadeIT::Constructor: Failed to load library for Controller.
sfcbd: INTERNAL StoreLibFacadeIT::getInstance: Failed to load library for IT Controller.
4. When managing RAID System which using specific RAID Controller
If you use below RAID Controllers on VMware ESXi 5.5 Update 2/ ESXi 6.0 or
later, lsi_mr3 driver may be loaded as default driver.
- NE3303-177 RAID Controller (1GB, RAID 0/1/5/6)
- NE3303-178 RAID Controller (2GB, RAID 0/1/5/6)
- NE3303-H004 RAID Controller (2GB, RAID 0/1/5/6)
lsi_mr3 driver has no interface with LSI SMI-S Provider.
Therefore, you will not able to manage RAID System.
To enable RAID System management, switch driver from lsi_mr3 to megaraid_sas
with commands as follows.
# esxcli system module set --enabled=false --module=lsi_mr3
# esxcli system module set --enabled=true --module=megaraid_sas
# reboot
NOTICE: Reboot ESXi is needed to reflect settings.
If you want to check current driver which is loaded, use following command.
# vmkload_mod -l | grep <driver name (lsi_mr3 etc.)<
If <driver name> is not loaded, Nothing is showing on the console.
----------------------------------------------------------------------
[Attached Files]
Length Date Time Name
-------- ---- ---- ----
7549670 09-05-14 15:34 esxi50_vmware-esx-provider-lsiprovider.zip
7549673 09-05-14 15:36 esxi55_vmware-esx-provider-lsiprovider.zip
You can check the integrity of the downloaded file by comparing the
following values in the md5sum column and the MD5 checksums of the file
you have downloaded. If the checksums do not match, it means an error
occurred during download.
md5sum | Filename
---------------------------------+-----------------------------------
787a5afb7a6b18ea86ed6dfd2405e8ce esxi50_vmware-esx-provider-lsiprovider.zip
184dbda290a0c1a8ffe109f4d8b0b38c esxi55_vmware-esx-provider-lsiprovider.zip
- esxi50_vmware-esx-provider-lsiprovider.zip (for VMware ESXi 5.0/5.1)
Length Date Time Name
-------- ---- ---- ----
7728268 08-14-14 00:55 vmware-esx-provider-lsiprovider.vib
-------- -------
7728268 1 file
- esxi55_vmware-esx-provider-lsiprovider.zip (for VMware ESXi 5.5/6.0)
Length Date Time Name
-------- ---- ---- ----
7728268 08-14-14 00:47 vmware-esx-provider-lsiprovider.vib
-------- -------
7728268 1 file
----------------------------------------------------------------------
[Revision History]
2015/07/31 00.50.V0.11
* Note that there is no change in the installation image.
"Enhancement"
1. Additional support of the following RAID Controllers
- NE3303-177 RAID Controller (1GB, RAID 0/1/5/6)
- NE3303-178 RAID Controller (2GB, RAID 0/1/5/6)
- NE3303-H004 RAID Controller (2GB, RAID 0/1/5/6)
2. Additional support of the following server models
- Express5800/A2010c
- Express5800/A2020c
- Express5800/A2040c
3. Additional support of the following OS
- VMware ESXi 6.0 or later (*)
* If you manage RAID System from NEC ESMPRO Manager,
it requires VMware ESXi 6.0b or later.
2014/9/18 00.50.V0.11
First version released.
----------------------------------------------------------------------
[Trademarks and Copyright]
The copyright for this software is held by Avago Technologies.
NEC is permitted to distribute this software by Avago Technologies.
* VMware is a registered trademark of VMware, Inc. in the United States
and/or other jurisdictions.
* All other company and product names in this document are the registered
trademarks or trademarks of their respective owners.
----------------------------------------------------------------------
Copyright NEC Corporation 2015