This release note and the software that accompanies it are (c)Copyright 2017-2018 Avago Technologies 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 Avago Technologies 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 Avago Technologies. ===================== Supported Controllers ===================== 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 = 004.134.000.000 OS supported = Window 8, Windows 8.1, Windows Server 2012, Windows 2012 R2, Windows 2012 R2 U1, Windows 10 Client RS1/RS2/RS3, Windows 10 LSTB, Windows 2016 RS1/RS3, ESXi 6.5, ESXi 6.5 U1, ESXi 6.0 U1, U2, U3. Browsers = IE9 or later, Firefox9 or later and Chrome16 or later This package can be installed on both x86 and x64 systems. =================== 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://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.6 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 --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 timeout 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-->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: - To remove Subscription : 'host-ind -d -k "" Example : host-ind -d -k dhcp-x.y.z.k.dhcp.company.net_LSA_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 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. 5. Only Light Weight Monitor Installation: LSA 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. ========================= 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. LSA is limited to display the history of persistent events only for IR/IT Controller. 3. LSA server response of IPv4 and IPv6 addresses groups are intermixed in the presence of multi NIC cards. 4. LSA allows the "Guest" user to login when the "Guest" user is disabled through the "User Accounts". Potential work-around to overcome this as below 1. Open Command Prompt 2. Type “lusrmgr.msc” 3. Select “Users” option 4. Under the “Users” option, select the “Guest” Option 5. Right Click on the “Guest” user and select the “Properties” option. 6. Select the check box, “Account is Disabled”, if it not already selected. 5. 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. 6. Remote Discovery/Managed Server Page- a. VMWare health status will be displayed as "UNKNOWN". b. Health status is displayed with stale information. 7.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. 8.View Event Log table will be empty When there are only progress related events. 9.Localization-Events are always shown in "English". 10.LSA HTTP status code(s) undergoes next level of fine tuning. Please check with support team for the latest. 11.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. 12. After un-installation/Cancellation of LSA, OpenSLP which has been installed as part of LSA Pre-Requisite will still remain be present in the system. 13."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. 14. Due to issues with VMware ESXi5.5/ESXi6.0/ESXi6.5 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 15.Gateway server and the accessing server (other gateway,standalone,direct agent) should have should have Same release LSA versions. 16.With recent VMWare releases when the User is trying to update/flash the MegaRAID firmware through LSA, it might fail. The reason being as below 1. In-case of VMWare LSA 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 17.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. 18.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. 19.Recommendation is to clear the browser history every time user upgrades/downgrades or installs the software. 20.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|--" 21. 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. 22. On fresh installation, LSA can process only the latest 30 events and perform the corresponding alert delivery methods. 23. Due to the changes to the Base Installer downgrade to previous version from lastest version (004.003.000.000 and above/higher) is not suggested/recommended as un-installation of Old/Previous version might be erratic. Recommendation is to un-install the lastest version (004.003.000.000 and above/higher) and perform the installation of the earlier version(s). 24. VMWare Platform only - Sever may take few minute(s) to populate cache during first login. User will see delay in login response. 25. 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 26. 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. 27. 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. 28. 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). 29. It is recommended NOT to perform any operation in LSA during Online Controller Reset 30. 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 "C:\Program Files (x86)\LSI\LSIStorageAuthority\server\html\files". 31. Chrome latest Version 61.0.3163.100 & later versions has a problem with popup positioning. ======================= 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 \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 \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 ADDLOCAL=Gateway INSTALLATIONCHOICES=0 EVENTNOTIFICATIONCHOICES=3" 2)setup.exe /s /v"/qn ADDLOCAL=StandAlone INSTALLATIONCHOICES=1 EVENTNOTIFICATIONCHOICES=3" 3)setup.exe /s /v"/qn ADDLOCAL=DirectAgent INSTALLATIONCHOICES=2 EVENTNOTIFICATIONCHOICES=3" 4)setup.exe /s /v"/qn 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 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 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 ADDLOCAL=Gateway INSTALLATIONCHOICES=0 EVENTNOTIFICATIONCHOICES=3" 2)setup.exe /s /v"/qn ADDLOCAL=StandAlone INSTALLATIONCHOICES=1 EVENTNOTIFICATIONCHOICES=3" 3)setup.exe /s /v"/qn ADDLOCAL=DirectAgent INSTALLATIONCHOICES=2 EVENTNOTIFICATIONCHOICES=3" 4)setup.exe /s /v"/qn 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 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. =========================== 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 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 file. For ex: msiexec.exe /x {20660CCB-7C70-4D61-8D18-FB7FA3C476C9} /qn Note: If user has placed/copied any file(s) manually in the 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. ========================================== 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 Windows platform, this will be installed in below mentioned path. [ProgramFilesFolder]\LSI\LSIStorageAuthority 2. Go to the path to monitor under [ProgramFilesFolder]\LSI\LSIStorageAuthority\conf [ProgramFilesFolder]\LSI\LSIStorageAuthority\conf\monitor 3.Make the required changes in below file under monitor Open config-current.JSON file in any editor 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. i) Launch Command Prompt in Windows ii) Stop LightWeightMonitor service by executing the command -> sc stop LSAService iii) Start LightWeightMonitor service by executing the command -> sc start LSAService