Tag: LSI Storage Authority

Categories
Knowledge Support Support exacqVision Server Categories

Error Code 49: Invalid Credentials When Logging Into LSA (LSI Storage Authority)

Description 

LSI Storage Authority (LSA) fully supports English OS only, other languages are supported but a change to the LSA.conf file is necessary before you can login to LSA.

Product 

  • MegaRAID
  • LSI Storage Authority (LSA)

Steps to Reproduce 

  • Launch LSA from the desktop 
  • Enter the administrators username and password

Expected Results 

  • Login is successful and the LSI Storage Authority Landing Page is displayed

Actual Results 

  • Login fails with Error Code 49: Invalid Credentials

Solution

LSA fully supports English OS only.If you are using native German, French or Spanish OS, you need to edit the LSA.conf file and translate “Administrators” to your native language.
Resolve Error Code 49: Invalid Credentials with the following steps:

  • Stop the exacqVision Server Service
  • Stop the LSAService Service
  • Edit LSA config file (LSA.conf)
    • C:\Program Files(x86)\LSI\LSIStorageAuthority\conf\LSA.conf
    • Locate this line:  full_access_groups = Administrators
    • Depending on the OS language change the key word Administrators to  Administrateurs (French) Administratoren (German) or Administradores (Spanish)
      • French
        • full_access_groups = Administrateurs
      • German
        • full_access_groups = Administratoren
      • Spanish
        • full_access_groups = Administradores
      • Russian
        • full_access_groups = Администраторы or Administratory
    • Save the changes
  • Start the LSAService Service
  • Start exacqVision Server Service

Source: Broadcom Knowledge Base Article 1211236746276

Error-Code-49-Invalid-Credentials-when-trying-to-login-to-LSA-management-software.pdf
Categories
Knowledge Support Support exacqVision Enterprise exacqVision Client exacqVision Server exacqVision Webservice Categories exacqVision Hardware

exacqVision Default Ports

Description 

The following is a list of default port numbers used by exacqVision software.

NOTE: Many ports listed below may only used with certain configurations or by optional services and integrations.

Products

  • exacqVision Client
  • exacqVision Enterprise Manager
  • exacqVision Integrator Service Portal
  • exacqVision Server
  • exacqVision Web Service
  • LSI Storage Authority
  • MegaRAID Storage Manager
  • PostgreSQL
  • SQL Server

Port List

PortDescription
25Simple Mail Transfer Protocol (SMTP)
80exacqVision Web Server/exacqVision Enterprise Manager (HTTP)
How to change Web Service ports
How to change EM web ports
389LDAP (Lightweight Directory Access Protocol)
443exacqVision Web Service/exacqVision Enterprise Manager/ exacqVision Relay (HTTPS )
How to change Web Service ports
How to change EM web ports
445SMB Archiving and Microsoft-DS (Directory Services)
465Secure SMTP (Legacy)
587SMTP (TLS/SSL)
636LDAPS (Lightweight Directory Access Protocol over TLS/SSL)
1433exacqVision Enterprise Manager (SQL Server)
2463LSI Storage Authority (Webserver)
3071MegaRAID Storage Manager
3260exacqVision Server S-Series Extended Storage (iSCSI)
3702exacqVision Server – Web Services Dynamic Discovery (WS-Discovery)
5432exacqVision Enterprise Manager (PostgreSQL)
5571MegaRAID Storage Manager
8082exacqVision Web Service (Web Socket) – Web Sockets only used in Web Service 7.2 to 9.4
How to change Web Service ports
8083exacqVision Web Service (Web Socket Secure) – Web Sockets only used in Web Service 7.2 to 9.4
How to change Web Service ports
8443Server connections from exacqVision Mobile 24.09 and above.
How to change exacqVision Mobile listening port
8554exacqVision RTSP Server
9000LSI Storage Authority (LSA Server)
22609exacqVision Client
How to change exacqVision Server port
22610exacqVision Server Interprocess Communication [RESERVED – DO NOT USE]
22717exacqVision Web Service NVRG Gateway
28744exacqVision Enterprise Manager (Failback – vfba)
35111Integrator Service Portal (ExacqCloud Outbound Connections)

Related Articles

<br>

Categories
Knowledge Support Support Categories exacqVision Hardware

MegaRAID Definitions and Drive States

Description 

Common definitions and drive states used in relation to MegaRAID RAID Controllers.

Product 

  • MegaRAID Storage Manager
  • LSI Storage Authority

Virtual Drive

A virtual drive is a partition in a drive group that is made up of contiguous data segments on the drives. A virtual drive can consist of these components:

  • An entire drive group
  • A part of a drive group
  • A combination of any two of these conditions

Drive Group

A drive group is a group of physical drives. These drives are managed in partitions known as virtual drives. You can create one or more virtual drives on a group of drives attached to a controller card. However, this is based on the support of sliced VD and RAID level of the controller.

Virtual Drive States

A virtual drive property indicating the condition of the virtual drive. A virtual drive can be in any one of the following states

Optimal

A virtual drive whose members are all online. In the output of the StorCLI commands, Optimal is displayed as optl.

Degraded 

A virtual drive with a redundant RAID level with one or more member failures and can no longer sustain a subsequent drive failure.  In the output of the StorCLI commands, Degraded is displayed as dgrd.

Partially Degraded 

A virtual drive with a redundant RAID level that is capable of sustaining more than one member drive failure. This state also applies to the virtual drive’s member drives.Currently, a RAID 6 or RAID 60 virtual drive is the only virtual drive that can be partially degraded.In the output of the StorCLI commands, Partially Degraded is displayed as Pdgd.

Failed 

The virtual drive has failed.

Foreign

A foreign configuration is a RAID configuration that already exists on a replacement set of drives that you install in a computer system. WebBIOS Configuration Utility and the MegaRAID Storage Manager software allows you to import the existing configuration to the RAID controller or clear the configuration so you can create a new one.

Offline

The virtual drive is not available to the RAID controller, one or more member failures making the data inaccessible. In the output of the StorCLI commands, Offline is displayed as OfLn.

Physical Drive States

A physical drive can be in any one of the following states:

Unconfigured Good

A drive accessible to the RAID controller but not configured as a part of a virtual drive or as a hot spare.In the output of the StorCLI commands, Unconfigured Good is displayed as UGood.

Hot Spare

A drive that is configured as a hot spare.

Online

A drive that can be accessed by the RAID controller and will be part of the virtual drive.In the output of the StorCLI commands, Online is displayed as onln.

Rebuild

A drive to which data is being written to restore full redundancy for a virtual drive.

Failed

A drive that was originally configured as Online or Hot Spare, but on which the firmware detects an unrecoverable error.

Unconfigured Bad

A drive on which the firmware detects an unrecoverable error; the drive was Unconfigured Good or the drive could not be initialized.In the output of the StorCLI commands, Unconfigured Bad is displayed as UBad.
Note:   If an improperly removed device is reconnected to the RAID controller it will be recognized as UBAD (Unconfigured Bad). It can be incorprated back into the the Virtual Drive  by setting to UGOOD 

Missing

A drive that was Online, but which has been removed from its location.In the output of the StorCLI commands, Missing is displayed as Msng.

Offline

A drive that is part of a virtual drive but which has invalid data as far as the RAID configuration is concerned. In the output of the StorCLI commands, Offline is displayed as offln.

None

A drive with an unsupported flag set. An Unconfigured Good or Offline drive that has completed the prepare for removal operation.

Definitions

RAID

Redundant Array of Independent Disks is a group of multiple, independent drives that provide high performance by increasing the number of drives used for saving and accessing data. A RAID drive group improves input/output (I/O) performance and data availability. The group of drives appears to the host system as a single storage unit or as multiple virtual drives. Data throughput improves because several drives can be accessed simultaneously. RAID configurations also improve data storage availability and fault tolerance. Redundant RAID levels (RAID levels 1, 5, 6, 10, 50, and 60) provide data protection.

Selecting a RAID Level

To make sure of the best performance, you must choose the optimal RAID level when you create a system drive. The optimal RAID level for your drive group depends on a number of factors:

  • The number of drives in the drive group
  • The capacity of the drives in the drive group
  • The need for data redundancy
  • The disk performance required

RAID 5 

Uses data striping and parity data across three or more drives (distributed parity) to provide high data throughput and data redundancy, especially for applications that require random access. RAID 5 can survive the failure of one drive. If 2 or more drives fail then a total delete and rebuild is required.

RAID 6 

Uses data striping and parity data across three or more drives (distributed parity) to provide high data throughput and data redundancy, especially for applications that require random access. RAID 6 can survive the failure of two drives. If 3 or more drives fail then a total delete and rebuild is required.

Maximizing Fault Tolerance

Fault tolerance is achieved through the ability to perform automatic and transparent rebuilds using hot spare drives and hot swaps. A hot spare drive is an unused online available drive that the RAID controller instantly plugs into thesystem when an active drive fails. After the hot spare is automatically moved into the RAID drive group, the failed drive is automatically rebuilt on the spare drive. The RAID drive group continues to handle requests while the Rebuildoperation occurs.A hot swap is the manual substitution of a replacement unit in a disk subsystem for a defective one, where the substitution can be performed while the subsystem is running hot swap drives. An Auto-Rebuild feature in the WebBIOS Configuration Utility allows a failed drive to be replaced and automatically rebuilt by “hot-swapping” the drive in the same drive bay. The RAID drive group continues to handle requests while the Rebuild operation occurs, which provides a high degree of fault tolerance and zero downtime.

Hot spare 

A standby drive that can automatically replace a failed drive in a virtual drive and prevent data from being lost. A hot spare can be dedicated to a single redundant drive group or it can be part of the global hot spare pool for all drive groups controlled by the controller. When a drive fails, MegaRAID Storage Manager or LSI Storage Authority software automatically uses a hot spare to replace it and then rebuilds the data from the failed drive to the hot spare. Hot spares can be used in RAID 1, 5, 6, 10, 50, and 60 storage configurations.A hot swap manually replaces a defective drive unit when the computer is still running. When a new drive is installed, a rebuild occurs automatically if these situations occur:

  • The newly inserted drive is the same capacity as or larger than the failed drive.
  • The newly inserted drive is placed in the same drive bay as the failed drive it is replacing.

You can configure the controller to detect the new drives and automatically rebuild the contents of the drive.

Consistency Check

An operation that verifies that all stripes in a virtual drive with a redundant RAID level are consistent and that automatically fixes any errors. For RAID 1 drive groups, this operation verifies correct mirrored data for each stripe

Fast Initialization

The firmware quickly writes zeros to the first and last 8-MB regions of the new virtual drive, and then completes the initialization in the background or with next scheduled Consistency Check. This allows you to start writing data to the virtual drive immediately.

Fault Tolerance

The capability of the drive subsystem to undergo a single drive failure per drive group without compromising data integrity and processing capability. SAS RAID controllers provide fault tolerance through redundant drive groups in RAID levels 1, 5, 6, 10, 50, and 60. They also  support hot spare drives and the auto-rebuild feature.

Foreign Configuration

A RAID configuration that already exists on a replacement set of drives that you install in a computer system. MegaRAID Storage Manager software lets you import the existing configuration to the RAID controller, or you can clear the configuration so you can create a new one.

Initialization

The process of writing zeros to the data fields of a virtual drive and, in fault-tolerant RAID levels,  generating the corresponding parity to put the virtual drive in a Ready state. Initialization erases all previous data on the drives. Drive groups will work without initializing, but they can fail a consistency check because the parity fields have not been generated

IO policy

A virtual drive property indicating whether Cached I/O or Direct I/O is being used. In Cached I/O mode, all read operations are buffered in cache memory. In Direct I/O mode, read operations are not buffered in cache memory. Data is transferred to cache and the host concurrently. If the same data block is read again, it comes from cache memory. (The IO Policy applies to read operations on a specific virtual drive. It does not affect the read-ahead cache.)

Learning Cycle

An energy pack calibration operation performed by a RAID controller periodically to determine the condition of the energy pack. You can start energy pack learn cycles manually  or automatically

Patrol Read

A process that checks the drives in a storage configuration for drive errors that could lead to drive failure and lost data. The Patrol Read operation can find and sometimes fix any potential problem with drives before host access. This enhances overall system performance because error recovery during a normal I/O operation might not be necessary.

Read Policy

A controller attribute indicating the current Read Policy mode. In Always Read Ahead mode, the controller reads sequentially ahead of the requested data and stores the additional data in cache memory, anticipating that the data will be needed soon. This speeds up read operations for sequential data, but you will see little improvement when accessing random data. In No Read Ahead mode (known as Normal mode in WebBIOS), read ahead capability is disabled.

Rebuild

The regeneration of all data to a replacement drive in a redundant virtual drive after a drive failure. A drive rebuild normally occurs without interrupting normal operations on the affected virtual drive, though some degradation of performance of the drive subsystem can occur.

Strip Size

The portion of a stripe that resides on a single drive in the drive group.

Temperature

Temperature of the energy pack, measured in Celsius

Write-Back

In Write-Back Caching mode, the controller sends a data transfer completion signal to the host when the controller cache has received all of the data in a drive write transaction. Data is written to the drive subsystem in accordance with policies set up by the controller. These policies include the amount of dirty/clean cache lines, the number of cache lines available, and elapsed time from the last cache flush.

Categories
Knowledge Support Support Categories exacqVision Hardware

Expanding a MegaRAID Virtual Drives Capacity using LSA  – Empty Slots Available

Title

Expanding a MegaRAID Virtual Drives Capacity using LSA  – Empty Slots Available

Description 

Expanding a virtual drive means increasing its capacity. Existing data on the virtual drive is not impacted by the expansion. Follow these instructions to add a physical drive and expand the virtual disk size using LSI Storage Authority.   Expanding a RAID volume by adding hard drives is only available with RAID 0, 1, 5, and 6 configurations. RAID volume expansion will not work with other RAID configurations, such as RAID 00, 10, 50, or 60.


NOTE:  Capacity expansion is only possible on RAID 0, 1, 5 and 6. Please keep in mind, there should only be “1 virtual drive” on the array. If you have more than 1 virtual drive, then you cannot enlarge your array. You will have to create a backup, delete the array, create a new RAID, and restore your backup to the new virtual drive.


Caution: Physical drives with the same or larger capacity as the existing drives should be used.  If the new drive has a larger capacity only the amount matching the current physical drives making up the Virtual drive will be used.   For example, if the existing Virtual Drive consist of 4TB drives and a new 6TB drive is used to expand the Virtual Drive, the capacity of the new drive will be reported at 4TB, and the virtual drive will only be increased by 4TB.

Product 

  • MegaRAID 93xx Series RAID Controller
  • LSI Storage Authority (LSA)

Overview 

  • Add Physical Drives
  • Check current drive group and virtual drive configuration 
  • Modify Drive Group
  • Expand existing partition in the operating system
  • Verify virtual drive is present, healthy and operational

Add Physcial Drives

  • Note: Drives are hot swappable so it is not necessary to shutdown or restart the server 
  • Remove an empty drive tray
  • Place the new physical drive in the tray and use screws to secure it to the tray
  • Align the drive tray into the slot and gently slide into position using a final levering action to latch the drive in place. 
  • You will feel some resistance just before the drive seats itself into the backplane and the lever arm locks in place.  DO NOT FORCE THE DRIVE INTO POSISTION.  
  • A White LED should be visible once the physical drive has been correctly seated

Check Current Drive Group and Virtual Drive Configuration 

  • Launch LSA from the desktop 
  • Enter the operating systems administrators username and password
  • Use the drop down to Select Controller, the controller dashboard will appear
  • Physical Drives Tab
    • Ensure that all Physical Drives are present and have a status of Unconfigured Good 
    • If not, please refer to the following Knowledge Base Article(s) for additional information.
      • #10632  Import or Clear Foreign Configurations Using LSA (LSI Storage Authority)
      • #10624  Managing Physical Drives using LSA (LSI Storage Authority)
    • All drives should be Unconfigured Good before continuing!

  • Drive Groups Tab
    • Make note of the current RAID level  the Element(s) Action window appears.
    • Click on the Drive Group, the Element(s) Action window appears

Note: Do NOT click  the (+) plus icon as this will not open the correct Element(s) Action window

  • Under Element(s) Action, select Modify Drive Group, the Modify Drive Group window appears 
  • Use the drop down and select the RAID Level
  • Acknowledge the warning “It is advisable to backup data before you proceed. Are you sure you want to continue?“, click Next
  • Click  Add Physical Drives, the Available Unconfigured Drive(s) window will appear
  • Check the box(s) to select available unconfigured drive(s) to be included in the expansion
  • Click Add Physical Drives, you will be returned to the Modify Drive Group Window
  • Review the Drive Group and if necessary click Back to correct settings, Close to abort or Finish to apply
  • A message indicating the change Completed should appear, click Close
  • In few moments a Background Process Section will be displayed and when expanded show the virtual drive reconstruction progress. 
  • The reconstruction can take a very long time (Days) and progress should be periodically checked.  
  • NOTE: The Drive Group will not show the new phsical drive(s) or available space until reconstruction has successfully completed.
  • When completed the Background Processes in Progress window will automatically close 
  • Verify the Virtual Drive status and note the new capacity (LSA Landing Page > Select Controller > Expand Drive Group > Select Drive Group > Expand Properties) 

Resizing the Partition

Once the reconstruction has successfully completed the partition must be resized in the operating system before being available for use.

  • Linux 
    • Follow the instructions found in Knowledge Base Article #10606  “Resizing a Partition on Ubuntu Linux“
  • Windows
    • Follow the instructions found in Knowledge Base Article #10667 “Resizing a Partition on Microsoft Windows“

exacqVision Client

The following actions should be taken to ensure that storage is configured correctly and video both past and present are being recorded.

  • Storage > Drive Tab
    • Verify the Capacity is correct
    • Verity the Status is Healthy
  • Storage > Hardware Tab
    • Graphic View – Verify all drives are present and healthy
    • Tree View
      • Verify the Controller is listed and healthy
      • Verify the Virtual Drive (Unit 1:/c0/v0) is listed and healthy
      • Verify all Physical drives (Port 0:/c0/e252/s0, Port 1:/c0/e252/s1, etc. ) are all present and healthy
  • Search for previosly recorded video
  • Search for current video or use exacqReplay from Live View

Congratulations the Virtual Drive has been successfully expanded 

Categories
Knowledge Support Support Categories exacqVision Hardware

Import or Clear Foreign Configurations Using LSA (LSI Storage Authority)

Title

Import or Clear Foreign Configurations Using LSA (LSI Storage Authority)

Description 

A foreign configuration is a RAID configuration that already exists on a replacement set of drives that you install in a computer system.

Product 

  • MegaRAID 93xx Series RAID Controller
  • LSI Storage Authority

Importing or Clearing the Foreign Configurations

A foreign configuration is a RAID configuration that already exists on a replacement set of drives that you install in a computer system. You can use the LSI Storage Authority software to import the foreign configuration to the controller or clear the foreign configuration so that you can create a new configuration using these drives.  Perform the following steps to import or clear foreign configurations.

  1. Navigate to the Controller dashboard.
  2. Click Configure and then click Foreign Configuration.
    • The Foreign Configuration window appears, which lists all of the foreign configurations.
  3. Click one of the following options:
    • • Import All: Import the foreign configurations from all the foreign drives.
    • • Clear All: Remove the configurations from all the foreign drives.
  4. Click Re-Scan to refresh the window.
Categories
Knowledge Support Support Categories exacqVision Hardware

Managing Physical Drives using LSA (LSI Storage Authority)

Description 

All physical drives connected to the MegaRAID controller can be managed using LSI Storage Authority.

Product 

  • MegaRAID 93xx Series RAID Controller
  • LSI Storage Authority

Start and Stop Locating a Drive

If the physical drives are in a disk enclosure, you can identify them by making their LEDs blink.Perform the following steps to identify the physical drives.

  1. Navigate to the physical drive on the Controller dashboard, and select the drive you want to identify, such as Unconfigured Good drive, online physical drive, configured drive, and so on.
  2. Select Element(s) Actions > Start Locate, the corresponding LED on the physical drive starts blinking.
  3. Select Element(s) Actions > Stop Locate to stop the LED from blinking.

Making a Drive Offline

Perform the following steps to place a drive offline.
ATTENTION: After you perform this procedure, all of the data on the drive will be lost.

  1. Navigate to the Controller dashboard, and click a drive group name (for example, DG_1).
    • Click the + icon that corresponds to a drive group to display its contents.
    • The virtual drives and physical drives associated with the selected drive group appear.
  2. Click the Physical Drive tab, and select a drive that you want to place offline.
  3. Select Element(s) Actions > Make Offline.  The drive status changes to Offline.

Making a Drive Online

You can change the state of a physical drive to online. In an online state, the physical drive works normally and is a part of a configured virtual drive.

  1. Navigate to the Controller dashboard, and click a drive group name (for example, DG_1).
  • Click the + icon that corresponds to a drive group to display its contents.
  • The virtual drives and physical drives associated with the selected drive group appear.
  • Click the Physical Drive tab, and select the offline drive that you want to make online.
  • Select Element(s) Actions > Make Drive Online.
    • The drive status changes to Online.

Replacing a Drive

You might want to replace a drive if the drive shows signs of failing. Before you start this operation, be sure that an available unconfigured good replacement drive is available. The replacement drive must have at least as much capacity as the drive you are replacing. Perform the following steps to replace a drive.
ATTENTION: Make sure to back up the data on the drive before you replace it.

  1. Navigate to the Controller dashboard, and click a drive group name (for example, DG_1).
    • Click the + icon that corresponds to a drive group to display its contents.
    • The virtual drives and physical drives associated with the selected drive group appear.
  2. Click the Physical Drive tab, and select a drive which you want to replace.
  3. Select Element(s) Actions > Start Replace Drive.
    • The Replace Drive dialog appears
  4. Select a replacement drive, and click Replace Physical Drive.
    • A confirmation message appears.
  5. Select Confirm and click Yes, Replace Drive to proceed with the replace operation.
    • The drive is replaced and the data is copied to the selected component.

Assigning Global Hot Spares

A global hot spare replaces a failed physical drive in any redundant array, as long as the capacity of the global hot spare is equal to or larger than the coerced capacity of the failed physical drive. Perform the following steps to assign global hot spares.

  1. Navigate to the Controller dashboard, and click the Drives tab.
    • All of the associated drives appear.
  2. Expand Unconfigured Drives, and select an unconfigured good drive.
  3. Select Element(s) Actions > Assign Global Hot Spare.
    • The unconfigured good drive is changed to a global hot spare. The status of the unconfigured good drive appears as a global hot spare in the Hot Spares section.

Removing Global Hot Spares

Perform the following steps to remove a hot spare.

  1. Navigate to the Controller dashboard, and click the Drives tab.
    • All of the associated drives appear.
  2. Expand Hot Spares, and select a hot spare that you want to remove.
  3. Select Element(s) Actions > Remove Global Hot Spare.
    • The hot spare drive is removed and is listed in the Unconfigured Drives section as an unconfigured good drive

Converting an Unconfigured Bad Drive to an Unconfigured Good Drive

Perform the following steps to convert an unconfigured bad drive to an unconfigured good drive.

  1. Navigate to the Controller dashboard, and click the Drives tab.
    • All of the associated drives appear.
  2. Expand Unconfigured Drives, and select an unconfigured bad drive.
  3. Select Element(s) Actions > Make Unconfigured.
    • A confirmation message appears.
  4. Select Confirm and click Yes, Make Unconfigured to proceed with the operation.
    • A confirmation message appears.
  5. Select Confirm and click Yes, Make Good to proceed with the operation.
    • The unconfigured bad drive is changed to unconfigured good drive. The status of the unconfigured bad drive appears as unconfigured good in the Unconfigured Drives section.

Erasing a Drive

You can erase data on non-SEDs (normal HDDs) by using the Drive Erase option. For non-SEDs, the erase operation  consists of a series of write operations to a drive that overwrites every user-accessible sector of the drive with specified patterns. It can be repeated in multiple passes using different data patterns for enhanced security. The erase operation is performed as a background task. Perform the following steps to erase a drive.

  1. Navigate to the Controller dashboard, and click the Drives tab.
    1. All of the associated drives appear.
  2. Expand Unconfigured Drives and select an unconfigured good drive.
  3. Select Element(s) Actions > More Actions > Drive Erase.
    1. The Physical Drive Erase dialog appears.
    2. The dialog shows the following modes:
      1. • Simple
      2. • Normal
      3. • Thorough
  4. Select a mode, and click Erase Physical Drive.
    1. A warning message appears asking for your confirmation.
  5. Click Yes, Erase Drive.
    1. After the drive erase operation has started, the Stop Erase option is enabled in the Element(s) Actions menu. You can monitor the progress of the erase operation.

<br>

Categories
Knowledge Support Support Categories exacqVision Hardware

Silencing a MegaRAID Alarm Using LSA (LSI Storage Authority)

Description 

Follow these instructions to silence MegaRAID alarms using LSI Storage Authority (LSA). 


Product 

  • LSI Storage Authority (LSA)
  • MegaRAID

Silence the Alarm

When the controller detects an issue an alarm will occur and a high pitched beep will be emitted.  This alarm can be silenced through the LSI Software Authority. 

  • Once Logged into LSA a red banner similar to the example below will be present 
  • Click on Silence Alarm
  • If successful an indicator will appear confirming the Alarm is Silenced. 
Categories
Knowledge Support Support Categories exacqVision Hardware

Creating a MegaRAID Virtual Drive Using LSA (LSI Storage Authority)

Title

Creating a MegaRAID Virtual Drive Using LSA (LSI Storage Authority)

Description 

Follow these instructions to create a new virtual drive using LSI Storage Authority (LSA). 

Product 

  • MegaRAID
  • LSI Storage Authority (LSA)

Overview 

  • Stop exacqVision Server service 
  • Check current drive group and virtual drive configuration 
  • Create a new drive group
  • Create a hot spare (optional) 
  • Create a new virtual drive 
  • Initialize the virtual drive in the operating system
  • Verify virtual drive is present, healthy and operational

Stop exacqVision Server Service

In order to prevent exacqVision from attempting to access or write to the controller it is considered good practice to stop the service before proceeding. 

Windows 

  • Press Windows Key+R, type services.msc in the run box then press enter
  • Locate and Stop the exacqVision Server service

Linux 

  • Launch Terminal (Applications > Systems Tools > Terminal), execute the following command in the Terminal window
  • sudo service edvrserver stop 
  • Storage drives should be unmounted, enter the command 
  • sudo umount -a 
  • Some devices will not be unmounted and a “Target is busy” message will appear, these can be ignored.

Check Current Drive Group & Virtual Drive Configuration 

  • Launch LSA from the desktop 
  • Enter the administrators username and password
  • Use the drop down to Select Controller, the controller dashboard will appear
  • Drive Group & Virtual Drives
    • Select the Drive Groups tab, verify no Drive Groups or Virtual Drives are configured.
    • Any existing Drive Groups or Virtual Drives should be deleted. See Knowledge Base Article  #10513 “Deleting a MegaRAID Virtual Drive Using LSA (LSI Storage Authority)”
  • Physical Drives
    • Ensure that all Physical Drives are present, they also must have a status of Unconfigured Good 
    • If not, clear the configuration too include Foreign configurations. 
  • Clear Configuration
    • Select Controller Actions > Configure > Clear Configuration, a confirmation window will appear
    • Select Confirm and then Yes, Clear Configuration 
  • Foreign Configuraiton
    • Select Controller Actions >Configure > Foreign Configuration, a confirmation window will appearNote: if grayed out then no drives with Foreign Configuration
    • The Foreign Configuration window appears listing all Foreign Configurations
    • Click Clear, when prompted select Clear All to remove configurations from all foreign drives 
    • Click Re-Scan to refresh the window, No Foreign configurations should not be found
    • Click Close
  • All drives should now be Unconfigured Good 

Create a Drive Group 

  • Select Controller Actions > Configure > Advanced Configuration, the Advanced Configuration window opens
  • Select a RAID level for the drive group from the drop-down box, then click NextIf the original RAID level is unknown the RAID level can be determined by the total number of drives being used to create the drive group.  RAID 5 for systems with three to eight drives and RAID 6 for systems with 9 or more drives
  • (Optional) Click Compare and Select to view the detailed information on each RAID level
  • Select Add Physical Drives
    • Click the column header “Enlcosure:Slot” until the drives are in listed in ascending order by slot with slot 0 at the top
    • Check the box to the left of the”Enlcosure:Slot” individually or next to the header to select all Available Unconfigured DrivesNote:  If a hot spare is needed leave at least 1 drive unchecked 
  • Select Add Physical Drives to add the selected physical drives to the drive group.

Add Hot Spare (Optional) 

  • If an unassigned drive is available then “Add Hot Spares” will be available 
  • Select “Add Hot Spares”
  • Check the box to the left of the Available Unconfigured Drives.
  • Click “Add Hot Spares”Note:  A Hot Spare drive can be added later if an open slot is available

Create a Virtual Drive 

  • Click Add Virtual Drives
    • Virtual drives to create: 1 (default)
    • Capacity:  (default)The capacity is automatically calculated based on the combined capacities of the physical drives within the drive group and the RAID level chosen.
    • Virtual Drive Name: Leave as the default
    • Stripe Size: 256 (default)
    • Initialization State: Fast Initialization 
    • Read Policy: Read Ahead (default)
    • Write Policy: Write Back (default) 
    • IO Policy: Direct IO (default) 
    • Disk Cache Policy: Disabled (default)
    • Click Add Virtual Drives, Information about the newly created virtual drive appears in the Advanced Configuration window.
  • Review Settings, if necessary select Back to make corrections, once satisfied click Next
  • Select Finish to add the virtual drive to the drive group and complete Advanced Configuration
  • Select Close 

Initialize the Virtual Disk in the OS


Windows

  • Press Windows Key+R, type diskmgmt.msc in the run box then press enter
  • An Initialize Disk Window similar to the following will appear
  • The default settings should be correct, click OK
  • The Virtual Drive will be present and show Unallocated, right-click in empty space to the right of Unallocated
  • A window will appear, choose New Simple Volume
  • The New Simple Volume Wizard will launch, click Next to continue
  • Specify Volume Size, by default the maximum size should already be selected, click Next 
  • Assign a Drive Letter, click Next
  • Format the VolumeFile Systems: NTFS (default)
  • Allocation unit size: Default (default) 
  • Volume Label: Data
  • click Next
  • Review Settings, if necessary go Back to make corrections, once satisfied click Finish
  • The Virtual Disk should now be a Healthy (Primary Partition) with a Label and drive letter
  • Close Disk Management
  • Restart the machine

Linux

  • From the Desktop open Places and navigate to Computer > File System > usr/local/exacq/server/scripts
  • Right-Click in an empty spot, a context window will appear, select Open as Administrator
  • Enter the Linux Administrator password, click Authenticate, a new file explorer window will appear (as superuser)
  • Launch the raidprep.sh script, select Run in Terminal when prompted
  • A Terminal terminal window will appear, results of the script will be displayed before it automatically closes 
  • If the following error 
  • Restart the machine

Virtual Drive Verification

The virtual drive should now be fully configured, healthy and operational.

  • In the exacqVision Client, navigate to Storage 
  • Check the Drive tab, verify the virtual drive is present and healthy
  • Check the Hardware tab  Graphic view, verify 
    • Status is optimal (Optl), Background initialization (x% Complete)
    • All slots containing a physical drive are healthy
    • Note: Hot Spares should be listed and with a status of Dedicated Hot Spare
  • Check the Hardware tab Tree view, verify 
    • Controller is present and Healthy
    • Virtual Drive (Unit) is present and Healthy 
    • Physical drives (ports 0-#) are present and Healthy 
  • If a hot spare was created it should be listed and have a status of Dedicated Hot Spare
Categories
Knowledge Support Support Categories exacqVision Hardware

Deleting a MegaRAID Virtual Drive Using LSA (LSI Storage Authority)

Title

Deleting a MegaRAID Virtual Drive Using LSA (LSI Storage Authority)

Description 

Instructions for deleting a MegaRAID virtual drive using LSA (LSI Storage Authority)

Product 

  • LSI Storage Authority 
  • MegaRAID

Prerequisite

Caution:  The exacqVision Server service should be stopped before proceeding


Windows 

  • Press Windows Key+R, type services.msc in the run box then press enter
  • Locate and Stop the exacqVision Server service

Linux 

  • Launch Terminal (Applications > Systems Tools > Terminal), execute the following command in the Terminal window
  • sudo service edvrserver stop 

Deleting a Virtual Drive

There can be several reason why you may wish to delete a virtual drive 

  • The virtual drive is failed and cannot be recovered
  • Physical drive replacement to expand capacity

caution: All data on a virtual drive is lost when you delete it. Make sure to back up the data before you delete a virtual drive.

  1. Launch LSA from the desktop 
  2. Enter the administrators username and password
  3. Use the drop down to Select Controller, the controller dashboard will appear
  4. From the Controller dashboard, select the Drive Groups Tab, click the + icon next to the drive group name (example DG_0).  The Drive group will expand and the virtual and physical drives associated with the selected drive group appear. 
  5. Select the virtual drive, a check will appear to the left of the drive group name and Element(s) Action will display available actions 
  6. Select Element Action > Delete 
  7. Select Confirm and click Yes, Delete,  a message momentarily appears confirming that the virtual drive was deleted successfully, Drive Groups should show the following

Categories
Knowledge Support Support Categories exacqVision Hardware Uncategorized

Replacing MegaRAID Storage Manager (MSM) With LSI Storage Authority (LSA) – Linux

Title

Replacing MegaRAID Storage Manager (MSM) With LSI Storage Authority (LSA) – Linux

Description

MSM has been found to have some exposure to CVE-2021-44228, the Apache Log4j remote code execution vulnerability, see statement from Broadcom Log4j2 Exposure (CVE-2021-44228).   As a result you may be able to replace MSM with LSA on a Windows machine using the following instructions.

Product

  • MegaRAID 92xx Series RAID Controllers
  • MegaRAID 93xx Series RAID Controllers
  • Ubuntu 16.04 LTS and Earlier
  • Ubuntu 18.04 LTS
  • Ubunutu 20.04 LTS

Prerequisites 

First determine which version of Ubuntu the NVR is currently running using Knowledge Base Article #9996 “How to Identify the Current Linux OS Version”

Next identify the RAID controller model using Knowledge Base Article #7244 “How to Identify the MegaRAID Controller Model on an exacqVision Server”

Ubuntu 16.04 LTS or earlier Operating Systems

Broadcom has not provided an LSA version for 16.04 LTS or older versions of Ubuntu.

  • If possible, Re-image using Ubuntu 18.04 or 20.04 LTS
  • See exacqVision Field Recovery Instructions to see if your system meets the criteria for an update. 
  • If re-image is not possible then use the first option listed in the 92xx series RAID Controllers section below. 

92xx series RAID Controllers

Machines with 92xx series RAID controllers have the following options.

  • Uninstall MSM
    • Manage the array using the BIOS available on boot
    • Manage the array using storcli
  • Update MSM
    • Software, instructions, and support for your particular controller card are provided by the card Manufacturer, Broadcom
    • Information is available at https://www.broadcom.com/support/download-search (Legacy Products > Legacy RAID Controllers)

93xx series RAID Controllers

For Machines with 93xx series RAID controllers MSM can be  replaced with LSA using the following instructions.

Objectives

  • Uninstall MSM
  • Install LSA
  • Update Desktop Icon
  • Configure/ Restart LSA
  • Verify LSA can be accessed and login is working
  • Verify Storage information in exacqVision client is correct and video is being recorded

Uninstalling MSM

  • Double-click the Terminal icon on the desktop
  • Elevate to root using sudo -i 
  • Remove the MSM package using dpkg -r 
  • Ensure that the dpkg command completes with no errors.
  • Close the Terminal window
Example removing MSM


Install LSI Storage Authority (LSA)

  • Download and save LSA from https://docs.broadcom.com/docs/007.020.014.000_LSA_Linux-x64.zip
  • The LSI website will require reading a download agreement, (scrolling down to the bottom of the agreement), clicking an acknowledgement checkbox, then clicking the “I Agree” button
  • Once downloaded,  close Firefox
  • On the desktop double-click the Computer icon.
  • Select Downloads, locate and right-click on the LSA zip file and select extract here
  • Right-click the newly created x64 folder and select Open as Administrator
  • A caution window may appear, click OK to continue
  • Enter the Administrator Password and click Authenticate
  • Click File menu and Select Open in Terminal
  • In the terminal window type ./install_deb.sh and press Enter
  • The License agreement (EULA) will be displayed
  • Type Y to accept the License Agreement then press Enter
  • Type 1 to choose “Since last shutdown” and press Enter
  • Type 2  to choose “Standalone” and press Enter
  • Type 2463 for Web Server port and press Enter
  • Type 9000 for LSA Port and press Enter
  • Type Y and press Enter to install openslp
  • When you see “LSA installation successful” the install is complete
  • Close the Terminal window

Edit the Desktop Icon 

  • Right-click on the MSM desktop icon and select properties 
  • Change these fields to the following:
    • Name: LSA
    • Command: /opt/lsi/LSIStorageAuthority/startupLSAUI.sh
    • Comment: LSI Storage Authority
  • Click Close

Modify LSA.conf 

  • Double-click the Computer icon on the desktop to open a new file explorer.
  • Select File System
  • Navigate to /opt/lsi/LSIStorageAuthority/conf
  • Click the File menu and select Open as Administrator
  • Enter the Administrator Password and click Authenticate
  • In the explorer windows labeled conf (as superuser)  double-click on LSA.conf to open it for editing
  • Line 189 should read “full_access_groups = root”
  • Append “, adm” to this line so it now reads “full_access_groups = root, adm”
  • Click Save and close the file

Restart LSA Service

  • Double-click the Terminal icon on the desktop
  • Type sudo service LsiSASH restart
  • Wait for the command to complete, it will take 20-30 seconds
  • Close the Terminal Window 
Example restarting LSA Service

Verify desktop icon

  • Double-click the LSA desktop icon to launch LSA in the browser
  • Log in to LSA using Administrator credentials.

Verify Storage

  • Open the exacqVision Client 
  • Navigate to the Hardware tab on the Storage page (Configuration > YOURSERVER > Storage > Hardware tab)
  • Select Tree and verify the RAID Controller, the Unit (Virtual Drive) and the Ports (Physical Drives) are present. 
  • If possible verify video is being recorded and can be played back by searching to using exacqReplay