INTEL SOFTWARE LICENSE AGREEMENT

(OEM / ODM/IHV / ISV Distribution & Single End User) IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.

Do not use or load Software from this site or any associated Documentation until You have carefully read the following terms and conditions. By loading or using the Software or associated Documentation, You agree to the terms of this Agreement. If You do not wish to so agree, do not install or use the Software or associated Documentation.

To the extent that the Software includes any Open Source Software, the terms of the Open Source Software license accompanying such Open Source Software will govern the use of such software. The terms of this Agreement will not apply to such software.

DEFINITIONS:

“Confidential Information” means any Software, Documentation or other materials that are marked as “Intel Confidential” or that, given the nature of the information or the circumstances surrounding its disclosure, reasonably should be considered as confidential.

“Copyrights” means all worldwide copyrights, copyright applications, copyright registrations, and any rights in any jurisdiction that are analogous to those described in this definition, including any extension of these rights.

“Derivative Work” means a derivative work, as defined in 17 U.S.C. § 101, of the Software Source Code, that You developed.

“End User” means the ultimate consumer for the hardware device which makes use of the
Software.

“Documentation” means the user manuals and other written materials that describe the Software, its operation and matters related to its use, that Intel provides in connection with, under, or subject to, this Agreement, and any updated, improved or modified version(s) of those materials, whether provided in published written material, on magnetic media or communicated by electronic means

“Executable Code” means computer programming code in binary form suitable for machine execution by a processor without the intervening steps of interpretation or compilation.

“Materials” means collectively the Software and Documentation.

“Object Code” means computer programming code in binary form suitable for machine execution by a processor without the intervening steps of interpretation or compilation

“Open Source Software” means

(A)	any software that requires as a condition of use, modification or distribution of the software that that software or other software incorporated into, derived from or distributed with that software:


•	be disclosed or distributed in Source Code;

•	be licensed by the user to third parties for the purpose of making or distributing derivative works; or

•	be redistributable at no charge.

(B)	Open Source Software includes, without limitation, software licensed or distributed under any of the following licenses or distribution models, or licenses or distribution models substantially similar to any of the following:

•	GNU’s General Public License (GPL) or Lesser/Library GPL (LGPL);
•	the Artistic License (e.g., PERL);
•	the Mozilla Public License;
•	the Netscape Public License;

•	the Sun Community Source License (SCSL);
•	the Sun Industry Source License (SISL); and
•	the Common Public License (CPL).

“Software” means the computer program, in Executable Code and Source Code and any accompanying documentation as delivered by Intel to You, and any updated or improved version of the program that Intel provides to You under this Agreement, if any, but does not include Open Source Software or any computer programming code that is subject to an agreement, obligation or license (whether or not accompanying the computer program) intended to supersede or override this Agreement.

“Source Code” means a form in which a computer program’s logic is easily deduced by a human being with skill in the art, such as a printed listing of the program or a form from which a printed listing can be easily recognized.

COPYRIGHT LICENSE.

(A)	If You are an Original Equipment Manufacturer, reseller, distributor, installer, integrator,

or other entity in the business of providing computer hardware products in the chain of manufacture or distribution to End Users:

You are granted a limited copyright license to copy, install and distribute these Materials to others in the chain of manufacture or to End Users. You may only copy, install and distribute the Materials on a computer system which contains the Intel server board or the Intel RAID controller for which the Materials were provided as indicated on the website from which You download the Materials.

You may not copy, distribute or sublicense the Materials by any mode or method other than as described in preceding sentence, unless You have signed a license which expressly grants You such rights. Contact Your Intel sales office if You require such a license.


You may not (1) modify, publicly display, perform, decompile, reverse engineer or disassemble the Materials except as permitted by applicable law, or (2) remove any copyright or other proprietary notices from the Materials.

(B)	If You are an End User:

You are granted a limited copyright license to download, copy and install the Materials onto one computer system which includes the Intel server board or the Intel RAID controller for which the Materials were provided as indicated on website from which You downloaded the Materials.

You may not (1) modify, publicly display, perform, or sublicense, sell or rent the

Materials, (2) disassemble, decompile or reverse engineer the Materials except and only to the extent permitted by applicable law, (3) remove any copyright or other proprietary notices from the Materials, or (4) transfer the Materials to another person or entity unless You also transfer the Intel server board or system for which the Materials were provided as indicated the website from which You downloaded the Materials, and Your transferee agrees to be bound by the terms of this Agreement. This copyright license also applies to the Materials after You have installed them on the computer system which contains the Intel server board or the Intel RAID controller for which the Materials were provided.

LIMITATIONS.

(A)	All rights, title and interest in and to the Materials are and will remain the exclusive property of Intel. Unless expressly permitted above, You will not, and will not allow any third party to:

(1)	use, copy or distribute the Materials;

(2)	modify, adapt, enhance, disassemble, decompile, reverse engineer, change or create Derivative Works from the Software or Documentation; or

(3)	use the Software to process the data of, or make the Software available online for the use of, third parties.

(B)	The consideration under this Agreement is only for the licenses that Intel expressly grants above. Any other rights including, but not limited to, additional patent rights, will require an additional license and additional consideration. Nothing in this Agreement requires or will be treated to require Intel to grant any additional license. You acknowledge that an essential basis of the bargain in this Agreement is that Intel grants You no licenses or other rights including, but not limited to, patent, copyright, trademark, trade name, service mark or other intellectual property licenses or rights with respect to the Materials, by implication, estoppel or otherwise, except for the licenses expressly granted above. Specifically, except for the licenses that Intel expressly granted You above, Intel grants no licenses or other rights, expressly or by implication, estoppel or otherwise, to:

(1)	make, use, sell, offer for sale, or import modifications of the Materials;

(2)	sell or offer to sell the Materials;

(3)	combine the Software or modified versions of the Software with other items or to use any such combination; or
(4)	any claims of any patents, patent applications, or other patent rights of Intel.

(C)	The consideration for the license in this Agreement reflects Intel’s continuing right to assert patent claims against any modifications or Derivative Works (including, without limitation, error corrections and bug fixes) of, or combinations with, the Software that You or third parties make that infringe any Intel patent claim.

USER SUBMISSIONS. You agree that any material, information or other communication, including all data, images, sounds, text, and other things embodied therein, You transmit or post to an Intel website or provide to Intel under this Agreement will be considered non-confidential communications ("Communications"). Intel will have no confidentiality obligations with respect to the Communications. You agree that Intel and its designees will be free to copy, modify, create derivative works, publicly display, disclose, distribute, license and sublicense through multiple tiers of distribution and licensees, incorporate and otherwise use the Communications, including derivative works thereto, for any and all commercial or non-commercial purposes.

ACCESS; USE OF CONTRACTORS. Except as expressly permitted herein, You will not allow the Materials to be accessed or used by third parties or anyone other than Your employees whose duties require access or use. Notwithstanding the foregoing, Your authorized consultants and subcontractors may access the Software in source code form where the access is incidental to their performing services on Your behalf consistent with the license granted to You under this Agreement, provided: You first require those consultants and subcontractors to sign written agreements obligating them to observe the same restrictions concerning the Materials as are contained in this Agreement; and You are fully liable to Intel for the actions and inaction of those consultants and subcontractors.

OPEN SOURCE SOFTWARE. You may not subject any non-Open Source Software included with the Software, in whole or in part, to any license obligations of Open Source Software including without limitation combining or distributing the Software with Open Source Software in a manner that subjects the Software or any portion of the Software provided by Intel hereunder to any license obligations of such Open Source Software.

MEDIA FORMAT CODECS AND DIGITAL RIGHTS MANAGEMENT. You acknowledge and agree that Your use of the Software or distribution thereof with Your products as permitted by this license may require You to procure license(s) from one or more third parties that may hold intellectual property rights applicable to the media format transcoding and/or digital rights management capabilities of the Software, if any.

CONFIDENTIALITY. If You wish to have a third party consultant or subcontractor ("Contractor") perform work on Your behalf which involves access to or use of Materials, You will obtain a written confidentiality agreement from the Contractor which contains terms and obligations with respect to access to or use of Materials no less restrictive than those set forth in this Agreement and excluding any distribution rights, and use for any other purpose. Otherwise, You will not disclose the terms or existence of this Agreement or use Intel's Name in any publications, advertisements, or other announcements without Intel's prior written consent. You do not have any rights to use any Intel trademarks or logos.


OWNERSHIP. Title to all copies of the Materials remains with Intel or its suppliers. The Materials are copyrighted and protected by the laws of the United States and other countries, and international treaty provisions. You may not remove any copyright notices from the Materials. Intel may make changes to the Materials, or to items referenced therein, at any time without notice, but is not obligated to support or update the Materials. Except as otherwise expressly provided, Intel grants no express or implied right under Intel patents, copyrights, trademarks, or other intellectual property rights. You may transfer the Materials only if the recipient agrees to be fully bound by these terms and if You retain no copies of the Materials.

SUPPORT. Intel may make changes to the Materials or to items referenced therein, at any time without notice, but is not obligated to support, update or provide training for the Software. Intel may in its sole discretion offer such services under separate terms at Intel’s then-current rates. You may request additional information on Intel’s service offerings from an Intel sales representative. You agree to be solely responsible to Your End Users for any update or support obligation or other liability which may arise from the distribution of the Software.

EXCLUSION OF OTHER WARRANTIES. THE MATERIALS ARE PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the accuracy or completeness of any information, text, graphics, links or other items contained within the Materials.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR INABILITY TO USE THE MATERIALS EVEN IF INTEL HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION. THE SOFTWARE LICENSED HEREUNDER IS NOT DESIGNED OR INTENDED FOR USE IN ANY MEDICAL, LIFE SAVING OR LIFE SUSTAINING SYSTEMS, TRANSPORTATION SYSTEMS, NUCLEAR SYSTEMS, OR FOR ANY OTHER MISSION CRITICAL APPLICATION IN WHICH THE FAILURE OF THE SOFTWARE COULD LEAD TO PERSONAL INJURY OR DEATH. YOU SHALL INDEMNIFY AND HOLD INTEL AND THE INTEL PARTIES HARMLESS AGAINST ALL CLAIMS, COSTS, DAMAGES, AND EXPENSES, AND REASONABLE ATTORNEY FEES ARISING OUT OF, DIRECTLY OR INDIRECTLY, THE DISTRIBUTION OF THE SOFTWARE AND ANY CLAIM OF PRODUCT LIABILITY, PERSONAL INJURY OR DEATH ASSOCIATED WITH ANY UNINTENDED USE, EVEN IF SUCH CLAIM ALLEGES THAT AN INTEL PARTY WAS NEGLIGENT REGARDING THE DESIGN OR MANUFACTURE OF THE SOFTWARE. THE LIMITED REMEDIES, WARRANTY DISCLAIMER AND LIMITED LIABILITY ARE FUNDAMENTAL ELEMENTS OF THE BASIS OF THE BARGAIN BETWEEN INTEL AND YOU. INTEL WOULD NOT BE ABLE TO PROVIDE THE SOFTWARE WITHOUT SUCH LIMITATIONS.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement immediately, upon notice to You, if You violate its terms. Upon termination, You will immediately destroy the Materials (including providing certification of such destruction back to Intel) or return all copies of the Materials to Intel. In the event of termination of this Agreement, all licenses granted to You hereunder will immediately terminate, except for licenses that You have previously distributed to Your end-users pursuant to the license grant above.

APPLICABLE LAWS. Any claims arising under or relating to this Agreement will be governed by the internal substantive laws of the State of Delaware or federal courts located in Delaware, without regard to


principles of conflict of laws. Each Party hereby agrees to jurisdiction and venue in the courts of the State of Delaware for all disputes and litigation arising under or relating to this Agreement. The Parties agree that the United Nations Convention on Contracts for the International Sale of Goods is specifically excluded from application to this Agreement. The Parties consent to the personal jurisdiction of the above courts.

EXPORT REGULATIONS / EXPORT CONTROL. You will not export, re-export, divert, transfer or disclose, directly or indirectly, the Materials and any related technical information or materials without complying strictly with all legal requirements including, without limitation, obtaining the prior approval of the U.S. Department of Commerce and, if necessary, other agencies or departments of the U.S. Government. Please access Intel’s website,  http://www.intel.com/content/www/us/en/legal/export-compliance.html, for information regarding the export classification of the Software that may be necessary to assist Your compliance with this provision. You will execute and deliver to Intel “Letters of Assurance” as may be required under applicable export regulations. You will indemnify Intel against any loss related to Your failure to conform to these requirements. You will ensure that the distribution and export/re-export or import of the product is in compliance with all laws, regulations, orders, or other restrictions of the U.S. Export Administration Regulations and the appropriate foreign government. You agree that neither You nor any of Your subsidiaries will export/re-export any technical data, process, product, or service, directly or indirectly, to any country for which the United States government or any agency thereof or the foreign government from where it is shipping requires an export license, or other governmental approval, without first obtaining such license or approval.

GOVERNMENT RESTRICTED RIGHTS. The Software is a "commercial item" as that term is defined in 48 C.F.R. 2.101, consisting of "commercial computer software" and "commercial computer software documentation" as such terms are used in 48 C.F.R. 12.212. Consistent with 48 C.F.R. 12.212 and 48 C.F.R 227.7202-1 through 227.7202-4, You will provide the Materials to the U.S. Government as an End User only pursuant to the terms and conditions therein. Contractor or Manufacturer is Intel Corporation, 2200 Mission College Blvd., Santa Clara, CA 95052.

ASSIGNMENT. You may not delegate, assign or transfer this Agreement, the license(s) granted or any of Your rights or duties hereunder, expressly, by implication, by operation of law, by way of merger (regardless of whether You are the surviving entity) or acquisition, or otherwise and any attempt to do so, without Intel’s express prior written consent, will be null and void. Intel may assign this Agreement, and its rights and obligations hereunder, in its sole discretion.

ENTIRE AGREEMENT. The terms and conditions of this Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof, and merges and supersedes all prior, contemporaneous agreements, understandings, negotiations and discussions. Neither of the parties hereto will be bound by any conditions, definitions, warranties, understandings or representations with respect to the subject matter hereof other than as expressly provided for herein. Intel is not obligated under any other agreements unless they are in writing and signed by an authorized representative of Intel. Without limiting the foregoing, terms and conditions on any purchase orders or similar materials submitted by You to Intel, and any terms contained in Intel’s standard acknowledgment form that are in conflict with these terms, will be of no force or effect.

ATTORNEYS’ FEES. In the event any proceeding or lawsuit is brought by Intel or You in connection with this Agreement, the prevailing party in such proceeding will be entitled to receive its costs, expert witness fees and reasonable attorneys’ fees, including costs and fees on appeal.


NO AGENCY. Nothing contained herein will be construed as creating any agency, employment relationship, partnership, principal-agent or other form of joint enterprise between the parties.

SEVERABILITY. In the event that any provision of this Agreement will be unenforceable or invalid under any applicable law or be so held by applicable court decision, such unenforceability or invalidity will not render this Agreement unenforceable or invalid as a whole, and, in such event, such provision will be changed and interpreted so as to best accomplish the objectives of such unenforceable or invalid provision within the limits of applicable law or applicable court decisions.

WAIVER. The failure of either party to require performance by the other party of any provision hereof will not affect the full right to require such performance at any time thereafter; nor will the waiver by either party of a breach of any provision hereof be taken or held to be a waiver of the provision itself.

LANGUAGE. This Agreement is in the English language only, which language will be controlling in all respects, and all versions of this Agreement in any other language will be for accommodation only and will not be binding on You or Intel. All communications and notices made or given pursuant to this Agreement, and all documentation and support to be provided, unless otherwise noted, will be in the English language.

=====================
Supported Controllers
=====================
Tri-Mode modules and adapters
RMSP3AD160F
RMSP3CD080F
RMSP3HD080E
RMSP3JD160J
RSP3DD080F
RSP3GD016J
RSP3MD088F
RSP3QD160J
RSP3TD160F
RSP3WD080E

12Gb/s modules and adapters
RMS3AC160
RMS3CC040
RMS3CC080
RMS3HC080
RMS3JC080
RMS3VC160
RS3DC040
RS3DC080
RS3FC044
RS3GC008
RS3MC044
RS3SC008
RS3UC080
RS3UC080J
RS3WC080

12Gb/s Bridge boards and embedded controllers
AHWBP12GBGB (RS3LC)
AHWBP12GBGBR5 (RS3LC5)
AHWBPBGB24 (RS3PC)
AHWBPBGB24R (RMSP3LD060)
AHWKPTP12GBGB (RS3LC)
AHWKPTP12GBGBIT (RS3KC)
AHWKPTP12GBGBR5 (RS3LC5)
FHWKPTPBGB24 (RS3PC)
RS3YC

===================
Package Information
===================
RWC3 version = 004.186.000.000
OS supported = RHEL 6.7/6.8/6.9/7.3/7.4/7.5, SLES 11 SP2/SP3/SP4, SLES 12 SP1/SP2/SP3, ESXi 6.5, ESXi 6.5 U1, ESXi 6.5 U2.
Browsers = IE9 or later, Firefox9 or later and Chrome16 or later

This package can be installed on x64 systems.

=========================
Pre-Requisites
=========================

1. Prior to the installation of RWC3, we need to install OpenSLPv2.0.0 which is a Pre-Requisite. So please install it from the below location and install RWC3

http://openslp.org/download.html

   If OpenSLP is not installed, internally packaged OpenSLP binaries shall be installed in alternate location during RWC3 installation.
   User also has an option to continue with the RWC3 installation after proceeding with the installation of OpenSLP from the OS installation sources.

2. For VMware ESXi 5.x, and 6.x to work with RWC3, depending on your VMware ESXi environment, ensure latest SMI-S Provider is being installed from 7.7 releases.
	To deploy the MegaRAID SMI-S provider on an ESXi machine by using the VIB file provided by Broadcom, copy the VIB file or the offline-bundle.zip file to the ESXi machine.
	Use the esxcli file to load the MegaRAID SMI-S provider, and run the following command:
	ESXi# esxcli software vib install -v <local_file_path or file:///URL> --force
	NOTE :  A reboot is required after installing the SMI-S provider on VMware ESXi environment.

3. Steps to configure the ESXi server
   a) Ensure that the third-party application services like "slpd and sfcbd-watchdog services are up and running on ESXi
                  server".(/etc/init.d/slpd status & /etc/init.d/sfcbd-watchdog status).
   b) Ensure that firewall has been disabled on ESXi server.
      (Check Firewall status : "esxcli network firewall get" To Disable Firewall : "esxcli network firewall unload").
   c) sfcb time-out socket error in CIMOM server results in AEN blocked by sfcb-cimom and may lead to duplicate entries in client with incorrect event description.
                  To get rid of this, user is required to restart sfcb service in VMware ESXi.
                  Command to restart : /etc/init.d/sfcbd-watchdog stop.
									   /etc/init.d/sfcbd-watchdog start.
      The same has been raised against VMware. Refer to the link further details[https://www.vmdev.net/tracker/tracking/linkid/prpl1235/remcurreport/true/template/ViewIssue.vm?id=LSDM89&readonly=true]
   d) Multi-subnet Configuration : When gateway is part of multiple subnet and discovered Vmware is part of one of these subnets then user can use the manual discovery option in the remote discovery page 
    to add and manage the VMware server
   e) CURL error in CIMOM server results in AEN blocked by CIMOM server to upper layer(CIMProvider-->RWC3). This can happen if servers are in different subnet or if there is any incorrect/incomplete AEN subscriptions.
      To get rid of this, user is required to have both client and server in same subnet.
      Any incomplete AEN subscriptions needs to be removed via CIMClient (host-ind, part of ESXi installation)
	  Steps to delete the incomplete subscriptions:
	  1) To view the existing subscriptions: host-ind -s
	  2) To delete :
	     - Copy handler name from subscription list, example : handler: <dhcp-x.y.z.k.dhcp.company.net_RWC3_127.0.0.1>
		 - To remove Subscription : 'host-ind -d -k "<handler name>"
		   Example : host-ind -d  -k dhcp-x.y.z.k.dhcp.company.net_RWC3_127.0.0.1

      Either restart of sfcb service or reboot the server is recommended after any change in VMware server.
   f) To Manage VMware ESXi from RHEL 7.x user has to execute below commands before installation of RWC3
                1) service ebtables restart
                2) service iptables stop
	Note: Refer User guide for more information on "How to configure firewall", if user does not wanted to disable the firewall.

4. Only Light Weight Monitor Installation:
   RWC3 supports SMTP authorization using Auth Login. In this case user should configure LightWeightMonitor with SMTP credentials in config-current.json file and encoded in base64.

5. Soft links in Linux 64 bit: For RHEL/SLES on 64 bit platform(s), it is necessary to create the below soft links if openslp is not installed in "/usr/lib64/" or "/user/lib/" directory, before installing RAIDWebConsole3 (RWC3) 64 bit package.
    "ln -sf /usr/local/lib/libslp.so.1.0.0 /opt/lsi/LSIStorageAuthority/bin/libslp.so.1" or
    "ln -sf /usr/local/lib64/libslp.so.1.0.0 /opt/lsi/LSIStorageAuthority/bin/libslp.so.1"
    This is not necessary if internally packaged OpenSLP binaries is installed in alternate location during RWC3 installation.

6. An Instance of OpenSLP Was Already Installed, but RWC3 Is Unable to Display All the Registered Servers from the Remote Discovery page
   Restart the SLPD Services and RWC3 Service if RWC3 does not discover the servers from the Remote Discovery page
   a) For stopping the slpd use the command : killall slpd or /etc/init.d/slpd stop or systemctl stop slpd.service
   b) For starting the slpd use the command /etc/init.d/LsiSASH restart, where along with RWC3 service the slpd is also started.
   c) If the slpd is already installed as part of the OS package then use the command: /etc/init.d/slpd start or systemctl start slpd.service.

=========================
Known Restrictions/Issues
=========================
1. RWC3 is limited to display the history of persistent events only for IR/IT Controller.
2. Clear Configuration/Any operation- User(s) may see a time-out error(404) with large configuration.
   This is due to an issue in underlying layer, and CLI can be used to overcome this.
3. Remote Discovery/Managed Server Page- a. VMWare health status will be displayed as "UNKNOWN".
					 b. Health status is displayed with stale information.
4.In any case if the VMWare server/machine goes down, user(s) needs to stop/start the LSAService of Gateway from where the VMWare server needs/was discovered.
5.Localization-Events are always shown in "English".
6. It is possible to get a time-out from server. This time-out error is generated at the back-end if resource providing the content takes more time. eg: Fw flash may exceed the default time-out in server.
   To fix it, user will have to change the nginx fastcgi_read_timeout variable in server/conf/nginx.conf to "300"seconds.
7.Gateway server and the accessing server (other gateway,standalone,direct agent) should have Same release RWC3 versions.
8.Due to issues with VMware ESXi5.5/ESXi6.0/ESXi6.5 user cannot flash IT/IR firmware via RWC3.
    Below case has been raised in VMware:
      Project: priv-lsi-dme_TR
      Case Number: 00035498
      Summary: On ESXi6.0 OS,Failed to read header on stream error
      https://dcpn.force.com/apex/TechnicalRequestCaseRedesignPartner?Id=500i000000VYjxaAAD
	Below the workaround suggested by VMware for IT/IR firmware flash to work:
	a) Edit /etc/sfcb/sfcb.cfg
	b) Add httpMaxContentLength: 4194304
	c) Restart service /etc/init.d/sfcbd-watchdog restart
	d) Now try to flash Firmware
9.With recent VMWare releases when the User is trying to update/flash the MegaRAID firmware through RWC3, it might fail.
    The reason being as below
	1. In-case of VMWare RWC3 will interact with SMI-S Provider for any of the operations.
	2. Due to the recent changes in the VMWare Kernel API, underlying layers in VMWare has some issue.
	3. This has been resolved in MR7.2 Native Driver code as part of PR:SCGCQ01113165
10.IR/IT Firmware Downgrade is not supported from One Phase to Another Phase due to the limitation in underlying layers.
   Downgrade is possible within same Phase of firmware.
11.When only IPv6 NIC is enabled (No IPv4), OpenSLP registration is failing for RWC3 with error code "-23" due to a bug in OpenSLP.
   Due to which RWC3 is not able to display the IPv6 address, instead of it will be showing the loop-back address (127.0.0.1).
   So please ensure we have at-least one IPv4 NIC is active so avoid the confusion related to the IP Address.
12.Recommendation is to clear the browser history every time user upgrades/downgrades or installs the software.
13.VMware Platform only - when there is any continuous issue of slowness or sfcb not responding please try the below steps from VMware as a workaround

To increase the memory limit for the HHRC:

..* Edit /etc/sfcb/sfcb.cfg
..* Into the file insert: provMemOveride: hhrc=100
..* Reboot the system.
..* Verify that the change has been made properly: memstats -r group-stats -u mb -s name:min:max:memsize:memsizepeak | grep -E "hhrc|memSizePeak|--"
14. If user "Add the Virtual Drive(s)" from existing free space on drive group or "Delete virtual drive(s)" from existing drive group then RWC3
    refresh the complete controller page to update configuration information. Due to page refresh mouse reference on page getting removed. So, page may not get scroll up/down if user scroll the page using mouse wheel. User has to click once anywhere on the page then only the page scroll works. Alternatively User can also use the scrollbar.
15. On fresh installation, RWC3 can process only the latest 30 events and perform the corresponding alert delivery methods.
16. On some SLES setups, due to delay in DHCP IP assignment, SLP service cannot be started due to which RWC3 discovery shall fail on remote machines. Users may have to restart RWC3 services on remote system using command '/etc/init.d/LsiSASH restart' to overcome this issue. For SLES 12, there is a known issue (refer https://bugzilla.suse.com/show_bug.cgi?id=951225 for more details).
17. VMWare Platform only - Sever may take few minute(s) to populate cache during first login. User will see delay in login response.
18. Default browser on CentOS/RHEL 7.4 crashes when upgrade/downgrade firmware using RWC3.
	To work around you can disable or configure selinux.Refer the link to disable selinux on rhel. "https://access.redhat.com/solutions/3176"
19. Sign in button is not getting enabled by default in Mozilla when user name and password is saved.
    Work Around: Don’t save the user name and password or click on the user name text box to enable the checkbox
20. For IT controllers, after Updating/Erasing the UEFI/BIOS from any utility other than RWC3 ,User should REBOOT the server to take this into effect.
    Till reboot is complete, RWC3 will display old UEFI/BIOS details.
21. Below are the limitations in-case  a TR Ready DG present in RWC3
	1)User cannot  Disable/Modify the security  and cannot delete the Virtual Drive (or) Clear the configuration,
	2) Irrespective of the state of controller/VD state will be optimal and some of the operations might fail on TR DG/VD which is beyond the scope of RWC3.
	Recommendation : Please clear the TR from DG and perform the respective operations.
22. User may see delay in device display, if Firmware returns wrong state for Physical device(s) call. To see the latest data, user may need to refresh RWC3 client browser(F5).
23. SLES 11 SP2\SP3 comes packaged with older libopenssl which is not accepted by Latest ESXi 6.5 OS.
   This disallows RWC3 to connect to ESXi servers.
   This is due to vulnerability present in libopenssl. Upgrading to libopenssl0_9_8-0.9.8j-0.70.1 fix this issue.
	
   To apply the patch, follow instructions mentioned in https://www.suse.com/security/cve/CVE-2015-0209/ and https://www.suse.com/support/update/announcement/2015/suse-su-20150545-2.html .
	
   or download the patch directly from https://scc.suse.com/patches for CVE-2015-0209 
24. It is recommended NOT to perform any operation in RWC3 during Online Controller Reset
25. Launch Page is hidden by default. To view the launch page change the value of field "Check Flag" to 0 in the file "LaunchPageCheck" at location "<RWC3_HOME\server\html\files>".
26. Chrome latest Version 61.0.3163.100 & above has a problem with popup positioning.
27. View Event Log table will be empty When there are only progress related events.
28. There is known slp issue in Esxi 6.7 OS and due to which Esxi 6.7 is not discovered.
29. please edit LSA.conf file present under conf directory to configure RWC3 parameters. Each parameter and its usage is described in LSA.conf file

=======================
Contents of the package
=======================
   RWC3_Linux.zip
    x86 -- Contains files for 32bit platforms
    x64 -- Contains files for 64bit platforms

=========================
Installation Instructions
=========================
See Detailed installation instructions below:

1.Log in to the system as root or as a user with root privileges.
  Depending on the operating system and security settings, it may be necessary to
  install RWC3 using root rights. This may require that, log in as root and run the installer,
  or open a command prompt as root and run the installer via the command line,

2.RWC3 supports both interactive and non-interactive modes of installation.
	a. Interactive mode installation steps:
		1. Execute the command "./install.csh" from the installation disk.
		2. License Agreement : enter y to continue, n to exit.
		3. Type of installation:
								1- for Gateway
								2- for StandAlone
								3- for DirectAgent
								4- for Light Weight Monitor(LWM).
		4. Enter Nginx Server port [1-65535] default port is 2463
		5. Enter RWC3 port [1-65535] default port is 9000

	b.Non-interactive or silent mode installation steps:
		1. Execute command "./install.csh [-options] [nginx_port] [RWC3_port]" from the installation disk.
		2. The options are:
			-g for Gateway
			-s for StandAlone
			-d for DirectAgent
			-l for Light Weight Monitor(LWM)
		3. nginx_port and RWC3_port must be in range [1-65535] and must be different.
		   if nginx_port and RWC3_port is not specified in the command line the default values (Nginx default port 2463 and RWC3 default port 9000) will be used.

	c. Interactive upgrade instructions:
		1. Execute the command "./install.csh" from the installation disk.
		2. License Agreement : enter y to continue, n to exit.
		3. Type of installation:
								1- for Gateway
								2- for StandAlone
								3- for DirectAgent
								4- for Light Weight Monitor(LWM).
		4. Enter Nginx Server port [1-65535] default port is 2463
		5. Enter RWC3 port [1-65535] default port is 9000

	d. Silent upgrade instructions:
		1. Execute "./install.csh [-option] [nginx_port] [RWC3_port]"
		2. The options are:
			-g for Gateway
			-s for StandAlone
			-d for DirectAgent
			-l for Light Weight Monitor(LWM)
		3. nginx_port and RWC3_port must be in range [1-65535] and must be different.
		   if nginx_port and RWC3_port is not specified in the command line the default values (Nginx default port 2463 and RWC3 default port 9000) will be used.

3. The installer provides the user with four types of set-up options.
   1. Gateway - This will install all the features.
   2. StandAlone - This will install components required for Local Server Management.
   3. DirectAgent - This will install components required for Remote Server Management
   4. Light Weight Monitor - This will install Light Weight Monitor program features.
		Refer "How to configure LightWeightMonitor Agent" for more details

4. When LWM is Installed, user cannot perform installation of RWC3. Needs to do complete un-installation of LWM and then Install RWC3.
   When RWC3 is Installed, user cannot perform installation of LWM. Needs to do complete un-installation of RWC3 and then Install LWM.

5. Extract the contents of the zip file and install the appropriate package on
   32bit and 64bit operating systems.

   RWC3_Linux.zip
        x86 -- Contains files for 32bit platforms
        x64 -- Contains files for 64bit platforms

==============================
Upgrade/Downgrade Instructions
==============================
1. Downgrade is not supported.
2. User can upgrade to the same mode of installation to which he performed with earlier build.
3. During the upgrade user can move from one mode of installation to another mode of installation.
4. When LWM is Installed, user cannot perform upgrade from LWM to RWC3. Needs to do complete un-installation of LWM and then Install RWC3

Note: If user has placed/copied any file(s) manually in the <RWC3_HOME> directory, those files needs to be manually removed before the un-installation.
	  If the file(s) has not been removed, RWC3 Upgrade will not be clean.
================================
LDAP Authentication Instructions
================================
See Detailed LDAP Authentication instructions below:

For LDAP authentication RWC3 Server has to know some information about the LDAP server settings.
The following parameters need to be known by the RWC3 back-end apart from user name and password for LDAP authentication.
The following parameters need to be configured in the RWC3 parameter file "LSA.conf" placed under <RWC3_HOME/conf> directory.

a.ldap_server (LDAP server host-name or IP): This is not an optional parameter.
  This parameter value is the one used to connect to the specific LDAP Server for the user authentication.
  User can provide either the IP Address (or) the Host-name of the LDAP Server based on the configuration.

  Validation Condition:

      i. More than one value will not be accepted.

      ii.NULL (or) Empty value will not be accepted.

b.ldap_protocol_version (LDAP protocol version (default v3)): This is an Optional parameter.
  This parameter value is the one used to define the protocol needs to be used to create LDAP session.

c.ldap_binding (LDAP authentication mode. Options are BASIC or SECURE): Default is "BASIC". When an LDAP session is created,
  that is, when an LDAP client connects to the server, the authentication state of the session is set to anonymous.
  The BIND operation establishes the authentication state for a session.

  BASIC: The simplest form of client authentication is to bind to the server using a clear-text password.

  SECURE: A more secure method is to use one of the SASL authentication mechanisms, such as DIGEST-MD5[4].
	  This is based on a secret known to both the client and the server, allowing for a simple challenge-response scheme.
	  SASL is also capable of negotiating data encryption to protect subsequent operations

d.ldap_port_number (LDAP server port - optional). This is an Optional parameter. Port number of the LDAP server. If no port is specified,
  the standard LDAP port (389) is used for BASIC and for Secure Port number "636" is used based on the Authentication mode.

e.dn_details (DN name apart from username.): This is mandatory parameter."dn" is the distinguished name of the entry;
  it is neither an attribute nor a part of the entry. User needs to configure the DN details in LSA.conf in the following format.
  dn_details = {"DN":[{"key":"dc","values":["com"]},{"key":"dc","values":["ldapdomain"]},{"key":"ou","values":["DEV","TEST"]}]}

f.ldap_user_name (DN attribute referring the user's full name): This is an Optional parameter. This parameter value will be used to display the
  LDAP Logged-in user's full name. At present we may not be using this parameter.

g.readOnly (DN attributes referring user access restriction. 1=READ-ONLY, 0=FULL-ACCESS): This is an Optional parameter.
Default will be "readOnly". This parameter value will be used to determine the LDAP user access privileges.

h. Once the RWC3 conf file is updated the Nginx and RWC3 service need to be restarted for the new RWC3 conf changes to take affect

===========================
Un-installation Instructions
===========================
 The product can be uninstalled using the script uninstaller.sh.
 run the script /opt/lsi/LSIStorageAuhority/uninstaller.sh to un-install RWC3.

 user may also un-install RWC3 suing the rpm commands.
 Run the command  "rpm -e <rpm_name>" to un-install the RPM's from the target system.
 Example:
 rpm -e RAIDWebConsole3-1.00x.xxx-xxx

============================
RWC3 & Nginx Service Status:
	1: To Start RWC3 and Nginx, run "/etc/init.d/LsiSASH start".
	2: To Stop RWC3 and Nginx, run "/etc/init.d/LsiSASH stop".
	3: To ReStart RWC3 and Nginx run "/etc/init.d/LsiSASH restart".
    4: To check status of RWC3 and Nginx, run "/etc/init.d/LsiSASH status".
===========================

=========================================
How to configure LightWeightMonitor Agent
=========================================
Except config-current.JSON none of the file shouldn't be edit by user from LightWeightMonitor package.
The configuration for LightWeightMonitor can be done on config-current.JSON, which is packaged with write permission.

Basic understanding about config file:
--------------------------------------
1. Different alert actions:
  i) email
  ii) systemlog

2. Different severity level
  i) INFO - Informational message where no user action is necessary
  ii) WARNING - when a component is close to failure point
  iii) CRITICAL - when a component fails
  iv) FATAL - when a component fails and data loss occurs

3. Global rule (default alert actions for different severity of an event1)
  i) INFO event - systemlog
  ii) WARNING - systemlog
  iii) CRITICAL - systemlog
  iv) FATAL - systemlog and email

4. global (apply global rule for that particular severity event)

Start Configuration:
--------------------
1. After installing the LightWeightMonitor in Linux platform, this will be installed in below mentioned path.
  cd /opt/lsi/LSIStorageAuthority/

2. Go to the path to monitor under /opt/lsi/LSIStorageAuthority/conf
  cd /opt/lsi/LSIStorageAuthority/conf/monitor

3.Make the required changes in below file under monitor
  vi config-current.JSON (or)
  gedit config-current.JSON

4. Changes to be made in "config-current.JSON" file:

  I) E-mail Configuration:

    default:
	  "email": {
                    "isActive": true,
                    "type": "EMAIL",
                    "sender": "lsa-monitor@server.com",
                    "server": "127.0.0.1",
                    "to": [
                        "root@localhost"
                    ],
                    "authentication": {
                        "type": "NONE"
                    }
                }

	updated:
	  "email": {
                    "isActive": true,
                    "type": "EMAIL",
                    "sender": "lsa-monitor@server.com",
                    "server": "135.24.227.243",
                    "to": [
                        "root@localhost"
                    ],
                    "authentication": {
                        "type": "NONE"
                    }
                }


  II) Change alert actions for specific Severity
    default:
      {
        "warning": [
          "systemmessage"
        ]
      },
    example change to:
      {
        "warning": [
          "systemmessage",
          "email"
        ]
      },

  III) Change alert actions for specific Event
    default:
      "events": []
    example change to:
      "events": [
	    {
            "typeId": 4,
            "severity": "INFO",
            "actions": [
                "email"
            ]
        }
	  ]

  IV) Change severity for specific Event
    default:
      "events": []
    example change to:
      "events": [
	    {
            "typeId": 4,
            "severity": "CRITICAL",
            "actions": [
                "global"
            ]
        }
	  ]

   V) Auth Login Support
    default:
	  "email": {
                    "isActive": true,
                    "type": "EMAIL",
                    "sender": "lsa-monitor@server.com",
                    "server": "127.0.0.1",
                    "to": [
                        "root@localhost"
                    ],
                    "authentication": {
                        "type": "NONE"
                    }
                }
	example change to:
      "email": {
                    "isActive": true,
                    "type": "EMAIL",
                    "sender": "lsa-monitor@server.com",
                    "server": "127.0.0.1",
                    "to": [
                        "root@localhost"
                    ],
					// if your SMTP server supports authlogin authorization protocol then add authentication information
					"username": "lsi",  // where lsi is SMTP server's Username
                    "password": "xxxx", // where xxxx is Base64 converted, SMTP configuration's password
                    "authentication": {
                        "type": "AUTH-LOGIN"
                    }
                }
5.Restart the LightWeightMonitor services to get changes effect.
  /etc/init.d/LsiSASH restart
