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,
Wellsburg & Lewisburg SATA chipset based Software RAID, 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
===================


LWM version = 008.018.012.000
OS supported = RHEL 9.6, RHEL 9.7, RHEL 9.8, RHEL 10, RHEL 10.1, RHEL 10.2, SLES 15 SP5, SLES 15 SP6 ,SLES 15 SP7, SLES 16,  Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, Open Euler 24.03 SP3
Language(s) supported = English

This package is intended only for x64 system (or) Platform.

This package contains gcc_8.3.x, gcc_11.2.x and gcc_14.2.x. Below are the corresponding OS support:

gcc_8.3.x -  SLES 15 SPx
gcc_11.2.x - RHEL 9.x, OpenEuler 24.03
gcc_14.2.x - RHEL 10.x, SLES 16, Ubuntu 24.04 LTS, Ubuntu 26.04

NOTE:
gcc_8.3.x -> LSA Installer in this folder supports gcc_8.3.x 
gcc_11.2.x ->LSA Installer in this folder supports gcc_11.2.x 
gcc_14.2.x ->LSA Installer in this folder supports gcc_14.2.x

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

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

http://www.openslp.org/download.html

   If OpenSLP is not installed, internally packaged OpenSLP binaries shall be installed in alternate location during LWM installation.
   User also has an option to continue with the LWM installation after proceeding with the installation of OpenSLP from the OS installation sources.
2. LWM 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.
3. 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 LWM 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 LWM installation.


=========================
Known Restrictions/Issues
=========================
1. LWM is limited to display the history of persistent events only for IR/IT Controller.
2. For SLES15 and above platforms, one of the dependent rpms - 'insserv-compat' is required during installation/uninstallation. This is needed because LWM startup script is based on SysV/init script
    and insserv adds as a bridge between SysV/init script and systemctl.
3. LWM displays connector and enclosure postion as "-" in PD related events, in the case of corresponding element is removed from the FW stack
4. It is recommended to set LD_LIBRARY_PATH to use the LSA console when LSA not able to find the relative path.
    export LD_LIBRARY_PATH="${INSTALL_ROOT}/bin:$LD_LIBRARY_PATH"
    export LD_LIBRARY_PATH="${INSTALL_ROOT}/plugins:$LD_LIBRARY_PATH"
    Assume INSTALL_ROOT is "/opt/lsi/LSIStorageAuthority"
5. During LWM installation/upgrade users may see the error "pubKey.asc: key 1 import failed" from RHEL 9 OS, though LSA gone through all the necessary signing process (Note: this error not seen in previous RHEL flavors), Users can ignore this error.
6. Due to the build-id Unique Identification of binaries, user can have only a single copy of SL library (libstorelibit*.so) installed across multiple applications. During installation, If user seen any conflict with the existing rpm's binary then remove the old rpm to proceed with current installation.
7. In Ubuntu, if the user encounters any errors during LSA Installation, one common cause is having two files with very similar names and identical contents, then the user should create a symbolic link to the other
    Below are the sample errors during installation:
       /sbin/ldconfig.real: /usr/local/lib/libldap_r-2.4.so.2 is not a symbolic link
       /sbin/ldconfig.real: /usr/local/lib/liblber-2.4.so.2 is not a symbolic link
       /sbin/ldconfig.real: /usr/local/lib/libldap-2.4.so.2 is not a symbolic link
    Steps to be taken care before Installtion of LSA for libldap* errors:      
    1) To check if the two files are the same, you can use the following command:
          cd /usr/local/lib
          diff libldap-2.4.so.2 libldap-2.4.so.2.10.12
    2) If files are the same, the `diff` command will not return any output.
    3) If files are the same delete libldap-2.4.so.2 and make a symbolic link to the other file with that name.
            sudo rm libldap-2.4.so.2
            sudo ln -s libldap-2.4.so.2.10.12 libldap-2.4.so.2
    Perform the same steps for other errors.
8. Following are the known vulnerabilities in glibc used in below packages
	gcc_8.3.x -> LWM Installer in this folder supports gcc_8.3.x & higher 
	(https://www.cybersecurity-help.cz/vdb/gnu/glibc/2.28/)
	gcc_11.2.x ->LWM Installer in this folder supports gcc_11.2.x & higher
	(https://www.cybersecurity-help.cz/vdb/gnu/glibc/2.32/)	
	gcc_14.2.x ->LSA Installer in this folder supports gcc_14.2.x & higher
	(https://www.cybersecurity-help.cz/vdb/gnu/glibc/2.39/)	
=========================
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 LWM 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.LWM 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. Please make a selection to configure LWM range of events used to generate alert notifications if LWM cannot find Last Processed Sequence Number:
			(1) - Since Last Shutdown
                  LWM will generate alerts from events since last clean shutdown
            (2) - Since Log Clear
                  LWM will generate alerts from events since last log clear
            (3) - Since Last Reboot
                  LWM will generate alerts from events since last reboot
            (4) - Start from Now
                  LWM will generate alerts from events now onwards
		4. Enter Nginx Server port [1-65535] default port is 2463
		5. Enter LSA port [1-65535] default port is 9000

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

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.

4. Extract the contents of the zip file and install the package.

   LSA_Linux.zip
        x64 -- Contains files for 64bit platforms

=================================
Verify RPM signature Instructions
=================================	  
1. Import the public key to RPM DB. Command : rpm --import <public-key.asc>
2. Verify the RPM signature. Command : rpm -Kv <LSA rpm>
3. Install the LSA. If imported public key is for the RPM being installed, No warnings should be shown during installation.

For Ubuntu use below commands:
1. Import the public key to GPG DB. Command Syntax : gpg --import <pubKey.asc>
2. Verify the GPG signature. Command Syntax : gpg --verify <LightWeightMonitor-xxx.xxx.xxx.xxx-1_amd64.deb.sig> <LightWeightMonitor-xxx.xxx.xxx.xxx-1_amd64.deb>
3. Install the LWM. If imported public key is for the deb being installed, No warnings should be shown during installation.
	  
==============================
Email Security Configuration:
==============================
email_password_mode - Controls content of SMTP MAIL FROM AUTH parameter

1. Secure Mode (0) - Default, Recommended
   a. MAIL FROM AUTH contains: email address only
   b. Password transmitted separately during SMTP authentication
   c. Prevents password from appearing in SMTP server logs
   
2. Full Credentials Mode (1) - NOT RECOMMENDED (Security Risk)
   a. MAIL FROM AUTH contains: email:password
   b. Password may be logged in plain text by SMTP server
   c. Use ONLY if SMTP server explicitly requires this format

Default: 0 (Secure)

When to Use Mode 1:
   Only if email authentication fails with Mode 0 AND your SMTP administrator confirms 
   the server requires credentials in MAIL FROM command. Most modern SMTP servers work with Mode 0.

Troubleshooting: 
   Verify username/password and SMTP settings (host, port, SSL/TLS) before changing to Mode 1.

Note: Both modes perform authentication. Mode 0 keeps password out of logs.

===========================
Un-installation Instructions
===========================
 The product can be uninstalled using the script uninstaller.sh.
 run the script /opt/lsi/LSIStorageAuhority/uninstaller.sh to un-install LWM.
 
============================
LWM Service Status:
	1: To Start LWM, run "/etc/init.d/LsiSASH start".
	2: To Stop LWM, run "/etc/init.d/LsiSASH stop".
	3: To ReStart LWM, run "/etc/init.d/LsiSASH restart".
    4: To check status of LWM, run "/etc/init.d/LsiSASH status".
===========================

=============
How to Rekey
=============
LSA mainatains the sensitive data in encrypted format. To encrypt, LSA uses AES algorithm with key pair.
If user wants to periodically change the key pair, follow the below steps.

1. Stop LSA Service
   /etc/init.d/LsiSASH stop
   
2. Execute rekey command in the terminal (Make sure user having the admin privilege - for other user, result may unexpected)
   >$LSA_HOME/LSA.sh -rekey
   
3. LSA automatically delete the old keys and encrypt the sensitive data with new key pair

4. Start the LSA service
  /etc/init.d/LsiSASH start
  
=========================================
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
  v) FAULT / DEAD - The controller faulted due to a catastrophic error

3. Global rule (default alert actions for different severity of an event1)
  i) INFO event - systemlog
  ii) WARNING - systemlog
  iii) CRITICAL - systemlog
  iv) FATAL / FAULT / DEAD - 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. Stop LightWeightMonitor service
   /etc/init.d/LsiSASH stop

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

5. 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 and severity for specific Event
    default:
      "events": [
		"gen7": [],
		"gen8": []
	  ]
    example change to:
      "events": {
        "gen7": [
          {
            "typeId": 4,
            "severity": "DEAD",
            "actions": [
              "systemmessage"
            ]
          }
        ],
        "gen8": [
          {
            "typeId": 4,
            "severity": "CRITICAL",
            "actions": [
              "systemmessage"
            ]
          }
        ]
      }

  IV) 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"
                    }
                }
	Execute below command:
	>$LSA_HOME/LSA.sh -console
	It will prompt the user interface to configure e-mail configuration related changes
	Note: This particular step not require any service restart. User can chage the e-mail configuration on fly.
	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": "", // The entered password could be encrypted and persisted in LSA
                    "authentication": {
                        "type": "AUTH-LOGIN"
                    }
                }
				
6.Start the LightWeightMonitor service
  /etc/init.d/LsiSASH start
  
  For Ubuntu use below command:
  service LsiSASH start
