This release note and the software that accompanies it are (c)Copyright 2020
Broadcom Inc or its suppliers, and may only be installed and used in accordance
with the license that accompanies the software. All rights reserved.

This Software is furnished under license and may only be used or copied in accordance with
the terms of that license. No license, express or implied, by estoppel or otherwise,
to any intellectual property rights is granted by this document. The Software is subject
to change without notice, and should not be construed as a commitment by Broadcom Inc
or its suppliers to market, license, sell or support any product or technology.
Unless otherwise provided for in the license under which this Software is provided,
the Software is provided AS IS, with no warranties of any kind, express or implied.
Except as expressly permitted by the Software license, None of its suppliers assumes any
responsibility or liability for any errors or inaccuracies that may appear herein.
Except as expressly permitted by the Software license, no part of the Software may be
reproduced, stored in a retrieval system, transmitted in any form, or distributed by any
means without the express written consent of Broadcom Inc.

=====================
Supported Controllers
=====================
Broadcom 3916 SAS3/PCIe4 Tri-mode RAID on Chip, SAS 3516 Ventura based MegaRAID and iMR, SAS 3108 (Invader) based MegaRAID and iMR, SAS 3008 (Fury) based HBAs,
Wellsburg & Lewisburg SATA chipset based Software RAID

====================
Package Information
====================
LSA version = 007.014.010.000
OS supported = Windows Server 2016 (LTSC / RS1), Windows Server 2019 (LTSC / 18H2), Windows Server 2019 (19H2), Windows Server 2019 (20H1), Windows 10 Client (RS1), Windows 10 Client (RS5), Windows 10 Client (1909 /19H2), ESXi 6.7 U1/U2/U3, ESxi 7.0.
Browsers = IE9 or later, Firefox9 or later and Chrome16 or later
Language(s) supported = English

This package can be installed on both x86 and x64 systems (or) Platform.

===================
Pre-Requisites
===================
1. Prior to the first time installation of LSA builds,if "openslp_2.0.0_beta2_x86" is installed in the server(s), please un-install the "openslp_2.0.0_beta2_x86" from
  "Control Panel".
2. As part of LSA Pre-Requisite, we will be installing OpenSLPv2.0.0 32bit if no other version of OpenSLP is present.
   Please ensure there are no older OpenSLP versions present.
   If user wanted to install on own, can download from http://www.openslp.org/download.html
   Please ensure we are installing 32 bit version of OpenSLP, during the manual installation.
3. For VMware ESXi 5.x, and 6.x to work with LSA, depending on your VMware ESXi environment, ensure latest SMI-S Provider is being installed from 7.9 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.
4. 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 : - esxcli system wbem set -e 0
						   - esxcli system wbem set -e 1
      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 it is the responsibility of the user to configure both LSA Gateway and VMware under same subnet
     (or) workaround this with adding irrelevant subnet IP address to LSA configuration file (conf\LSA.conf -> private_ip_range=*) to avoid registering the wrong IP to VMWare.
   e) CURL error in CIMOM server results in AEN blocked by CIMOM server to upper layer(CIMProvider-->LSA). 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_LSA_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_LSA_127.0.0.1
      3) In case if the above command did not work in latest versions of VMware ESXi, User can use command 'indcfg' options.
	      - To View the existing subscriptions: indcfg -l
		  - To Clear subscriptions: indcfg -c
      Either restart of sfcb service or reboot the server is recommended after any change in VMware server.
	  Command to restart:
			- esxcli system wbem set -e 0
			- esxcli system wbem set -e 1
   f) To Manage VMware ESXi from RHEL 7.x user has to execute below commands before installation of LSA Gateway.
       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.

=========================
Known Restrictions/Issues
=========================
1. After installation of the LSIStorageAuthority package, LSA process will be executed as a service named as "LSAService".
	- There is no dependency created between "NginxService" and "LSAService"

 	Please follow the below steps to Start/Stop (both) the "NginxService" and "LSAService"

 	Stop Sequence Order:
 	- First stop the "NginxService"
 	- Then stop the "LSAService"

	 Start Sequence Order:
	- First start the "NginxService"
 	- Then start the "LSAService"
2. "Modify" option for the existing "setup.exe" will not work. So user(s) has to un-install and install the build instead of using the "Modify" option.	
3. When only IPv6 NIC is enabled (No IPv4), OpenSLP registration is failing for LSA with error code "-23" due to a bug in OpenSLP.
    Due to which LSA 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.
4. LSA server response of IPv4 and IPv6 addresses groups are intermixed in the presence of multi NIC cards.
5. 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: Firmware flash, enclosure(s) insertion with more Foreign (or) UBAD (or) combination of Foreign and UBAD drives, 
	 Clear Configuration/Any operation- User(s) may see a time-out error (404 or 504) with large configuration.
	 This is due to an issue in underlying layer, and CLI can be used to overcome this or user will have to change the nginx fastcgi_read_timeout variable in server/conf/nginx.conf to "300"seconds,
	 or user should refresh the LSA page manually after waiting adequate time.
6. Recommendation is to clear the browser history every time user upgrades/downgrades or installs the software or when user modifies the default settings in any conf file
7. LSA displays connector and enclosure position as "-" in PD related events, in the case of corresponding element is removed from the FW stack
8. New Property/Operation/Terminology/Events (mismatch) related to Personality/TFM Management:The PR:SCGCQ01816544/SCGCQ01816546 in place to handle in the future releases.
	a)LSA may not provide newly added  properties/operation(s) compared with other Apps which results the terminology/operation/events mismatch.
	b)New Events: LSA will not be handling any events and associated health changes  will not be reflected.
9. When heavy IOs are active, it is recommended NOT to perform "Download Server Report" as this may get delayed.
10. Due to lower layer behavior, all EPD releated events follows the FW event description and can not be localized.
11. LSA is limited to display the history of persistent events only for IR/IT Controller.
12. Once the drive gets removed from the stack,there is no data available corresponding to the drive in FW. In this case LSA displays the connector name as empty for drive removal event and the subsequent events.

============================================
Known Restrictions/Issues Specific TO VMware
============================================
1. 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.
2. Due to issues with VMware user cannot flash IR/IT firmware via LSA.
    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
3. 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|--"
4. VMWare Platform only - Sever may take few minute(s) to populate cache during first login. User will see delay in login response.
5. ESXi (Until ESXi6.5) contains a provider class VMware_UserAuthorizationService which provides single method called CheckPermission() to get the permission particular user has. This could be read, readwrite or view
	From ESXi 6.7 onwards VMWare has deprecated this service and VMware_UserAuthorizationService class is not available
	Impact : LSA doesn’t have a known method to check user permission on ESXi 6.7 and this will impact LSA Login
	Workaround : LSA shall avoid making the check for user permission and consider user has read-write permission

=======================
Contents of the package
=======================
The installer provides the user with Four types of set-up option.
	1) Gateway --  This option will install all program features, which are required to manage all the LSA Servers and the VMWare servers.
	2) StandAlone -- This option will only install components required for local server management.
			 This server cannot manage any other Server(s) but can be managed by the Gateway Server(s)
	3) DirectAgent -- This option will only install components required for remote server management, which will not have any Client related components.
			  This Server(s) can only be managed through other Gateway Server(s).
	4) Light Weight Monitor (LWM) -- This option will install only components required for Monitoring purpose.
	Refer "How to configure LightWeightMonitor Agent" for more details

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

1.Log in to the system as an administrator or as a user with administrative privileges.
  Depending on the operating system and security settings, it may be necessary to
  install LSA using administrative rights. This may require that, log in as administrator and run the installer,
  or open a command prompt as administrator and run the installer via the command line,
  or right click on the Setup.exe and select "Run As Administrator".

2. Extract the contents of the ZIP file and run Setup.exe from the Disk1 folder.

3. When LWM is Installed, user cannot perform installation of LSA. Needs to do complete un-installation of LWM and then Install LSA.
   When LSA is Installed, user cannot perform installation of LWM. Needs to do complete un-installation of LSA and then Install LWM.
=================================
Silent Installation Instructions
=================================
To install LSA product in a non-interactive or silent mode, the user should use the following commands.

1. If VC Redist 2010 is not installed in the Server, please follow the Step#2 for installing the same.
   If already installed please follow the step#3.
2. Install the VC Redist Package from command line "vcredist_x86.exe /Q",
   vcredist_x86.exe is available in <Package_Dir>\ISSetupPrerequisites\{270b0954-35ca-4324-bbc6-ba5db9072dad}\VC Redist 2010 Installation.
3. If OpenSLP is not installed, install the OpenSLP from command line "openslp_2.0.0_0_x86 /Q"
	"openslp_2.0.0_0_x86" is available in <Package_Dir>\ISSetupPrerequisites\{23401E90-6962-476F-9D92-F9027E91A490}\openslp_2.0.0_0_x86 Installation.

4. Here is the steps that user needs to perform the mode of installation of his choice, with the default directory provided by LSA

	1)setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=Gateway INSTALLATIONCHOICES=0 EVENTNOTIFICATIONCHOICES=3"
	2)setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=StandAlone INSTALLATIONCHOICES=1 EVENTNOTIFICATIONCHOICES=3"
	3)setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=DirectAgent INSTALLATIONCHOICES=2 EVENTNOTIFICATIONCHOICES=3"
	4)setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=LightWeightMonitor INSTALLATIONCHOICES=129 EVENTNOTIFICATIONCHOICES=3"

	EVENTNOTIFICATIONCHOICES options:
	0=Since Last Shutdown
	1=Since Last Clear
	2=Since Last Reboot
	3=Since Newest

	If user wants to change from the default directory structure, needs to provide the below input also with each and every mode of installation

	For Ex: Setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=LightWeightMonitor INSTALLATIONCHOICES=129 INSTALLDIR=CustomDirecotryLocation"
5. When LWM is Installed, user cannot perform installation of LSA. Needs to do complete un-installation of LWM and then Install LSA.

Remarks:
1. If user tries to install the same version of the build again when the build is already installed, the behavior can be erratic. Recommendation would be to un-install and install the build to make any changes to the existing installer.
==============================
Upgrade/Downgrade Instructions
===============================
1. User can upgrade/downgrade to the same mode of installation to which he performed with earlier build.
2. During the upgrade/downgrade user can move from one mode of installation to another mode of installation.
3. When LWM is Installed, user cannot perform upgrade/downgrade from LWM to LSA. Needs to do complete un-installation of LWM and then Install LSA

Note: If user has placed/copied any file(s) manually in the <LSA_HOME> directory, those files needs to be manually removed before the un-installation.
	  If the file(s) has not been removed, LSA Upgrade will not be clean.

===========================
Silent Upgrade Instructions
===========================
1. User(s) needs to follow the below instructions for the Silent Upgrade of LSA, if the installation is performed with the default directory provided by LSA

	1)setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=Gateway INSTALLATIONCHOICES=0 EVENTNOTIFICATIONCHOICES=3"
	2)setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=StandAlone INSTALLATIONCHOICES=1 EVENTNOTIFICATIONCHOICES=3"
	3)setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=DirectAgent INSTALLATIONCHOICES=2 EVENTNOTIFICATIONCHOICES=3"
	4)setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=LightWeightMonitor INSTALLATIONCHOICES=129 EVENTNOTIFICATIONCHOICES=3"

	EVENTNOTIFICATIONCHOICES options:
	0=Since Last Shutdown
	1=Since Last Clear
	2=Since Last Reboot
	3=Since Newest

	If LSA has been installed in custom directory instead of the default directory structure, needs to provide the below input also with each and every mode of installation

	For Ex: setup.exe /s /v"/qn ALLUSERS=1 ADDLOCAL=LightWeightMonitor INSTALLATIONCHOICES=129 INSTALLDIR=CustomDirectoryLocation"

2. When LWM is Installed, user cannot perform upgrade from LWM to LSA. Needs to do complete un-installation of LWM and then Install LSA

Remarks:
1. If user tries to install the same version of the build again when the build is already installed, the behavior can be erratic. Recommendation would be to un-install and install the build to make any changes to the existing installer.

================================
Sign verification Instructions
================================
command : signtool.exe verify /v /pa <LSA executable name>

Note: signtool.exe is required to validate the LSA's signature.
===========================
Un-installation Instructions
===========================
1. LSIStorageAuthority can be un-installed from the Windows Start Menu by choosing "Start->LSI->LSIStorageAuthority->Uninstall LSA"
2. The product can be removed/un-install from Add/Remove Program menu.

Note: If user has placed/copied any file(s) manually in the <LSA_HOME> directory, those files needs to be manually removed before the un-installation.
	  If the file(s) has not been removed, LSA Un-installation will not be clean.

===================================
Silent Un-installation Instructions
===================================
Please perform the below steps for the Silent Un-Installation of LSA

msiexec.exe /x productcode /qn

“productcode” value is nothing but the value present in the <LSA_HOME_PATH/productcode.txt> file.

For ex: msiexec.exe /x {20660CCB-7C70-4D61-8D18-FB7FA3C476C9} /qn

Note: If user has placed/copied any file(s) manually in the <LSA_HOME> directory, those files needs to be manually removed before the un-installation.
	  If the file(s) has not been removed, LSA un-installation will not be clean.
