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 ActionsConfigure > Clear Configuration, a confirmation window will appear
    • Select Confirm and then Yes, Clear Configuration 
  • Foreign Configuraiton
    • Select Controller Actions >ConfigureForeign 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 exacqVision Enterprise Categories

Downloading exacqVision Enterprise Manager Logs

Title

Downloading exacqVision Enterprise Manager Logs

Description

This article describes various ways to obtain exacqVision Enterprise Manager logs.

Method 1 – EM Dashboard

  • click on the information icon on the EM dashboard header
  • click about
  • click Support Diagnostics
  • ensure Enterprise logs is checked 
  • click on DOWNLOAD

Method 2 – API 

  • In a browser go to  https://<emaddress>/api/logs/bundle
  • This will create and download a zip file containing the EM logs
  • Note: There may be no notification, check your browser downloads

Method 3 – File System 

  • Windows
    • C:\Program Files\exacqVision\EnterpriseManager\EnterpriseSystemManager\log
  • Linux
    • /usr/local/exacq/esm/logs
Categories
Knowledge Support Support Categories exacqVision Hardware

Are DSCP/ToS set in exacqVision Server/Client Packet Headers

Title

Are DSCP/ToS set in exacqVision Server/Client Packet Headers

Description 

exacqVision Server/Client packets do not utilize DSCP/ToS (Differentiated Services Code Point (DSCP) Type of Service (Tos).

Product 

  • exacqVision Server
  • exacqVision Client

Description 

The ToS (type of service) or DiffServ (differentiated services) field in the IPv4 header, and the Traffic Class field in the IPv6 header are used to classify IP packets so that routers can make QoS (quality of service) decisions about what path packets should traverse across the network.

Categories
Knowledge Support Support Illustra exacqVision Server Categories Products

Illustra Pro Gen3 Motion Stops Reporting in Exacq Software

Illustra Motion stops reporting from within the Exacq Software.

This has been seen on the Illustra IPS03-D12-OI03 and IPS05-D12-OI03

There is a combination of updates that need to be performed.

First, upgrade the Exacq Server Software to 22.03.4 or higher

Second, download Illustra Firmware version Illustra.Pro3.02.09.00.0003 and upload it to the individual cameras demonstrating the issue.

After it has been successfully uploaded to the camera and the device has rebooted. Disable/Re-enable the camera under Add IP Cameras and verify the camera is displaying video.

Trac:23346

Categories
Knowledge Support Support exacqVision Client Products

Enhancement for Report Mode

Report Mode Enhancement to add a column in the export to show the last motion event in the report. The idea is to allow customers to see a clear and precise indication of when the last motion event took place. The report will identify cameras not recording motion properly in the report that is exported.

Will be available in future release. Most likely after June release 22.06 and targeted for 22.09.

Case 05251919
Ticket: 23470

Categories
Knowledge Support Support exacqVision Enterprise exacqVision Client Categories

exacqVision Server Log – SysMgmtPI Error/Warning “1073741819

exacqVision Server Log – SysMgmtPI Error/Warning “1073741819”

Description 

Both warning and error messages containing Error -1073741819 found in the exacqVision Server logs. 

Product 

  • exacqVision Enterprise Manager
  • exacqVision Server
  • MegaRAID

Solution

  • The issue was first observed in exacqVision Enterprise Manager which was reporting a Storage Hardware Alarm 
  • Note:  This server had recently undergone MegaRAID Storage Manager (MSM) replacement with LSI Storage Authority (LSA) KB #7236 and it is suspected this may have been a contributing factor. 
  • The exacqVision Client storage page was showing the status for all physical drives in the drive group as Offline
  • Restarted the exacqVision Server Service
  • Checked the System Logs, filtering on “sysmgmtpi” and focusing on entries immediately after restart
  • Found the following entries 
  • Opened a command prompt and ran the same storcli command 
  • A popup window immediately appeared saying “storcli.exe has stopped working” 
  • Resolved by replacing the existing “C:\Program Files (x86)\MegaRAID Storage Manager\storcli.exe” file
  • Now works in a Command Prompt, no SysMgmtPI errors or warning after service restart and Storage Hardware tab is correct. 
  • StorCLI.zip contains a working StorCLI.exe file and can be downloaded from the related tab on Salesforce Article #000034807
Categories
Knowledge Support Support exacqVision Mobile exacqVision Webservice Categories

Enabling and Troubleshooting exacqVision Web Server Relay Service

Description 

Exacq cloud hosted relay service eliminates the need for most firewall configuration and prevents exposing the NVR directly to inbound internet traffic via port forwarding by creating a unique relay URL as a proxy to access the NVR.  

Product 

  • exacqVision Web Service
  • exacqVision Relay Service

Prerequisites 

  • exacqVision Server 19.06 or higher 
  • NVRs with expired SSA “Software Subscription Agreement” will have image size and resolution restrictions.
  • Each NVR needs to have a power user configured
  • exacqVision Default Ports

Solution

  • Each server connection will require a power user login which should be created in advance. 
  • See Adding a user to the system in the exacqVision Client User Manual here
  • Access the exacqVision Web Server landing page using localhost or the loopback IP (127.0.0.1) 
  • Select Web Service Configuration and enter the username and password 
  • Select Server Connections
  • Select an existing server connection or add one
  • If existing, select and click EDIT SELECTED
  • If adding, select DISCOVERED or ADD SERVER 
    • Either manually input the server information or select and ADD a discovered server
  • Toggle the Power User Process ON
  • Enter the Power User Username and Password, then click APPLY
  • Select Basic (Configuration > Basic)
  • Toggle the Relay Connection ON, a restart required 
  • After the restart, log into Web Service Configuration
  • Verify a Relay URL is now listed on the Service Status page

Troubleshooting 

In the event the Relay URL is missing or having any other issues.

  • Make sure all Server connections have the Power User Process enabled and the credentials are correct.
    • If necessary remove server connections, adding back one at a time until the culprit can be found. 
    • Be sure to either restart the exacqVision Web Server Service or RETEST CONNECTIVITY each time before verifying if a Relay URL has been obtained. 
  • Review Knowledge Base Article #6088 “exacqVision Web Server Relay Service Issue – FRPC”
  • Review the training video Exacq Cloud-hosted Relay Service

Categories
Knowledge Support Support exacqVision Server Categories

Cameras Added With the Wrong Plugin Causes exacqVision Server Crash Loop

Description

Adding certain cameras with the wrong plugin type causes the exacqVision Server to go into a crash loop.

Product

  • exacqVision Server

Steps to Reproduce

  • Add a camera using the wrong plugin type

Expected Results

  • Camera fails to connect

Actual Results

  • Camera fails to connect
  • The Server status alternates between “Connected” and “Address Found but Not an exacqVision Server” on the Client Systems page

Solution

  • Stop the exacqVision Server service
  • Import a saved export OR
  • Edit the associated plugin xml file, removing the section for the offending camera(s) OR
  • Delete the associated plugin xml file being mindful this could also remove cameras that are correctly using the plugin
  • Start the exacqVision Server service
  • Determine the correct plugin https://www.exacq.com/integration/ipcams/
  • Add the camera(s) using the correct plugin

NOTE:  This has been specifically observed when Illustra cameras are added with Illustraflex instead of Illustra3 and Samsung cameras are added with Onvif instead of Samsung

<br>