This release note and the software that accompanies it are (c)Copyright 2026
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 maybe
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,
SAS3816 based IOC, SAS3808 based IOC, SAS3008 based HBAs, Initiator-Target 3 (IT3) controller
9660 Family RAID Adapters, 9670 Family RAID Adapters, 9600 Family eHBA Adapters, 9620 Family eHBA Adapters

===================
Package Information
===================
LSA version = 008.018.012.000
OS supported = VMware ESXi 9.0, VMware ESXi 9.1
Browsers = IE9 or later, Microsoft Edge 94.0, Firefox9 or later and Chrome16 or later
Language(s) supported = English

This package can be installed on ESXi x64 systems (or) platforms.

===========================
Firewall ruleset and status
===========================
LWA vib is packaged with the required firewall ruleset. By default, it will be in its disabled state and user can change it using esxcli command.

#check firewall ruleset list and status
$esxcli network firewall ruleset list | grep lwmd
Name                         Enabled
---------------------------  -------
lwmd                         false

# enable the ruleset 
$esxcli network firewall ruleset set -e 1 -r lwmd

#check firewall ruleset list and status
$esxcli network firewall ruleset list | grep lwmd
lwmd                         Inbound    TCP       Dst             35557     35557
lwmd                         Outbound   TCP       Dst               465       465
lwmd                         Outbound   TCP       Dst                25        25

===================
Port Numbers used
===================
Inbound:
35557 - WebServer Port
Outbound:
25    - Mail Port
465   - Mail Port

=========================
Known Restrictions/Issues
=========================

1. LSA 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 (Can be Physical Drives (or) Virtual Drives).
   This is due to an issue in underlying layer, and CLI can be used to overcome this.
3. Localization-Events are always shown in "English".
4. 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 timeout in server.
   To fix it, user will have to change the lighttdp fastcgi_read_timeout variable in <LSA_HOME>/data/server/conf/lighttdp.conf to "300"seconds.
5. 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.
6. if data is not updated in LSA  as soon as secured Foreign drives are unlocked, as FW is not giving the event to Cache module of LSA.
   Work Around: Stop and Start the LSA services.
7. Recommendation is to clear the browser history every time user upgrades/downgrades or installs the software.
8. LSA does not allow to select PD from non-spanned VD and from Spanned VD
9. Whenever auto rebuild is enabled multi click PD actions are not updated properly(intermittent) , user has to refresh the page manually.
10. If user "Add the Virtual Drive(s)" from existing free space on drive group or "Delete virtual drive(s)" from existing drive group then LSA
    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.
11. On fresh installation, LSA can process only the latest 30 events and perform the corresponding alert delivery methods.
12. VMWare Platform only - Sever may take few minute(s) to populate cache during first login. User will see delay in login response.
13. Sign in button is not getting enabled by default in Mozilla when user name and password is saved.
    Work Around: Dont save the user name and password or click on the user name text box to enable the checkbox
14. For IT controllers, after Updating/Erasing the UEFI/BIOS from any utility other than LSA ,User should REBOOT the server to 
	take this into effect.
    Till reboot is complete, LSA will display old UEFI/BIOS details.
15. Below are the limitations in-case  a TR Ready DG present in LSA
	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 LSA.
	Recommendation : Please clear the TR from DG and perform the respective operations.
16. 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 LSA client browser(F5).
17. It is recommended NOT to perform any operation in LSA during Online Controller Reset
18. Chrome latest Version 61.0.3163.100 & above has a problem with popup positioning.
19. View Event Log table will be empty When there are only progress related events.
20. Please edit LSA.conf file present under "<LSA_HOME>\vital" directory to configure LSA parameters. Each parameter and its usage is
    described in LSA.conf file
21. LSA displays connector and enclosure position as "-" in PD related events, in the case of corresponding element is removed from the FW
    stack
22. LSA displays extra line separators in other hardware tab during expansion of tree node. Note: This cosmetic observation is not same with
    different browser and monitor resolutions.
23. 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.
24. User may observe "504 - Gateway Timeout" error during enclosure(s) insertion with more Foreign (or) UBAD (or) combination of Foreign and
    UBAD drives. 
	Since under layer line also contributing for this behavior, as a workaround user should refresh the LSA page manually after waiting adequate time.
25. Intermittently Client pages might not get refreshed, when user modifies the default settings in a conf file.
	Workaround: Refresh the browser manually
26. It is recommended NOT to perform zoom related operation on browser until monitor resolution is low
27. If user performs any action(like Configuration,etc.,) from Server summary page and perform manual refresh anytime user will be
    redirected to the initially selected Action page. 

28.	LSA when launched with Linux Native Mozilla Firefox and kept idle for more than half an hour, LSA will become slow.
    Root Cause: Mozilla is sending multiple long poll calls on page refresh or moving across server landing and control console page.
	Similar bugs has been Raised with bugzilla, please find below the reference links
	https://bugzilla.mozilla.org/show_bug.cgi?id=1126689, https://bugzilla.mozilla.org/show_bug.cgi?id=1522781
	Work Around: Logout, Close the browser and relaunch the LSA.
29. User will see the default values displayed initially , once the user gets response table will be populated with proper data.
30. Converting JBOD PD from  JBOD to UG, applications will display different action menu name LSA displays it as "Make unconfigured good"
31. If the same Dedicated Hot Spare is assigned to multiple Drive Groups, User may see inconsistency in Element Count and DHSP Element
    selection checkboxes(Controller Page).
32. In MR, though the PR is running at the PD level, it is a controller level operation. So, Individual PD Patrol Read progress bar will not
    disappear after completing 100%,  When all the PD's progress bar completes 100%, then only all PDs progress bars disappears.
33. Due to lower layer behavior, all EPD related events follows the FW event description and can not be localized.
34. As per lower layer behavior, only limited non-persistent events are maintained in its memory. In this case, those non-persistent event's sequence number would not be constant but it would be aligned with persisted events in sequential order.

35. ESXI specific  
a. SLP is not packaged, hence this LSA shall be used as standalone
b. ldap is not supported in this build
c. In LW VMAgent (LWA) if user wants to initiate scheduler wrapper, configure "server":2. refer "How to configure LSA Client"

36. Issues such as failing to download reports can occur if there is not enough free disk space on the ESXi host. In this case, user may requires to restart the LSA service to come out of download progress.
37. Due to lower layer limitation, in the case of offline FW update, LSA not updating the health message or icon regarding system reboot required
38. User can not clear the configuration when VD(s)/JBOD(s) with OS/FS/Unknown Boot partition (cannot be read). In this case, user has to go to specific VD(s) and delete them.	
39. User is expected to refresh the browser on drive removal and insertion to see the updated data
40. After LWA uninstallation, delete the folder  lwmd from the location /opt. This step can be ignored if the user reboots the server after LSA uninstallation.
41. Since openssl communication failure, Email feature with SSL support is not working in ESXi 7.0 U1. Note: Issue not seen in ESXi 7.0 U3c
42. User(s) will not be able to see the PBLP component image and it's version details, if user(s) is trying to flash/upgrade the fw using the Vision(vsn) package.
43. LSA will consider the VD health instead of VD status when showing the VD health icon from 7.22 onwards
44. lighttpd v1.4.45 is being used in LWA due to compatibility with later versions.
45. Boost version v1_79 being used in LWA due to c++ version compatibilty with later versions of boost
    Refer below link for more details:
    https://www.boost.org/users/history/version_1_80_0.html
    BREAKING: The required minimum C++ version is changed from from C++11 to C++14. Currently, large parts of GIL still compile with a C++11 compiler. 
	However, there is no guarantee that it stays that way, and any compilers that do not support at least C++14 are considered unsupported as of now.
46. During VD creation adding drives some of the non-mixing drives row's style is not updating to disable look.
47. Mail Port can be configured on port number 25 and 465 only
48. Persistent and configuration files of LWA are available in vital folder.
49. When heavy IOs are active, LSA will be slow  and user might see stale data. Please refresh the browser or Restart LSA service to get the updated data.
50. When user enable/disable controller, Controller will not be loaded/unloaded in LSA by default. This needs LSA service restart to get the updated controller list.
51. Client's debug logs (corpus) will not be part of "server report".
52. JBOD(s) sorting is not supported under the Make JBOD Secure table.
53. When user sees the error page 50x "try again" will work when resources are available else please Check LSAService and Nginxservice status.
54. If lower layer does not populate the corresponding element's property value then LSA displays those property value as 'NA' , '-' or the property itself will not be part of the UI screen.
55. When user performs  Foreign configuration import, LSA shows Clear button enabled in the case of drive re-provision, even though there is no foreign configuration found. Clicking on clear will fail the call.
56.During LD creation users will not be allowed to enter less than 1 MB size and user can not enter values in KB from GUI, but during adding LD to the existing Array user will be allowed to enter less than 1 MB from GUI and LSA server will fail it. 
56.a.Depending on controller max stripe size, Minimum VD size may vary and could be less than 1 MB. 
57. There may be delayed response observed in LSA with operations performed on IR/IT Controller.
58. Sorting might not work properly with the Tape Drive present in the topology. However, users can filter the tape using media.
59. For a PD with 0 size or a bad PD, LSA shows the size and sector size as "-."
60. For PerfIT, LSA might show the drive media type as HDD instead of SSD after the cable pull/push. It indicates correctly after the refresh.
=======================
Contents of the package
=======================
   LSA_ESXi.zip
     BCM_bootbank_lwmd_<version>.vib
     LSA_ESXi9x_64_readme.txt
=========================
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 LSA 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,

	1. VIB Installation
		a. Download BCM_bootbank_lwmd_xxxxxxxxx-0x.vib (x86_64 arch only)
		b. Copy it to host esxi machine. 
		c. Run esxcli command to install the vib
			i. esxcli software vib install --viburl=/vmfs/volumes/datastore1/BCM_bootbank_lwmd_xxxxxxxxx-0x.vib
		d. This will install LSA to /opt/lwmd directory and start the service. Since, no live-install-allowed, system will ask for reboot.
		   Service can be managed using esxcli daemon control {start|stop|restart}
		h. LSA service will run along with the lighttpd server
	2. Component Installation
		a. Download vmware-lwmd-00x.xxx.xxx.xxx-0x.zip (x86_64 arch only)
		b. Copy it to host esxi machine. 
		c. Run esxcli command to install the component
			i. esxcli software component apply -d /vmfs/volumes/datastore1/vmware-lwmd-00x.xxx.xxx.xxx-0x.zip
		d. This will install LSA to /opt/lwmd directory and start the service. Since, no live-install-allowed, system will ask for reboot.
		   Service can be managed using esxcli daemon control {start|stop|restart}
		h. LSA service will run along with the lighttpd server
		
	Note: In the unsigned environment, user have to use --no-sig-check argument during installation
	
===========================
Un-installation Instructions
===========================
 esxcli software vib remove -n lwmd
 LSA package name can be derived using 
 esxcli software vib list |grep -i BCM
 
============================
LSA & web Service Status:
============================
	1: To Start LSA and lighttpd, run "esxcli daemon control start -s lwmd".
	2: To Stop LSA and lighttpd, run "esxcli daemon control stop -s lwmd".
	3: To ReStart LSA and lighttpdn run "esxcli daemon control restart -s lwmd".
	4: To check the status of LSA and lighttpd, run "esxcli daemon info get -s lwmd"

============================
How to configure LSA Client
============================
1. Based on your requirement update any available parameters in /opt/lwmd/vital/LSA.conf file
2. Retstart LSA Service

Available parameters,
#client's maximum number of elements can be selectable at a time (32=default)
clt_max_element_select_cnt = 32

#client's Server mode can be 0,1 and 2 (0=default)
clt_server_mode = 0

#client's Schedule mode either 0 OR 1 (1=default)
clt_schedule_mode = 1

#client's maximum response time for vd element in milli seconds (4000=default)
clt_max_resp_time_vd = 4000

#client's maximum response time for pd element in milli seconds (8000=default)
clt_max_resp_time_pd = 8000