The latest C-Series systems from exacqVision provide ready-to-go live-monitoring stations for your exacqVision users, without the need to design your own systems or check specifications to display multiple video streams. These systems are built to achieve specific decoding and frame rates to meet the needs of video security users.<br><br>
Chapters<br>
00:00 Intro<br>
00:27 Unboxing<br>
01:21 Model Comparison<br>
02:26 Port Identification<br>
03:26 Setup<br>
03:42 VESA Mount<br>
04:47 First Startup<br>
Reports of 23.09.9.0 Server would cause the Capture Card to show video loss on live page. This was not affecting video recording as live and recorded video were searchable.
Product
Server 20.09.9.0
Steps to Reproduce
Update server from server version prior to 23.09.9.0
It has been discovered that Illustra firmware SS018.24.03.00.0010 is missing key Cloudvue components and is there for NOT supported on C2C devices. The primary indicator is no data centers will be displayed when converting to Cloudvue mode.
Products
C2C#
Illustra#
Description
TCCF42V032
IFS02IFS02-D12-ITA4
2MP , 2.7-13.5 MFZ , Mini-Dome
TCCF44V032
IFS04-D12-ITA4
4MP , 2.7-13.5 MFZ , Mini-Dome
TCCF48V032
IFS08-D13-ITA4
8MP , 3.6-11 MFZ , Mini-Dome
TCCF42VI032
IFS02-D12-OIA4
2MP , 2.7-13.5 MFZ , IR Mini-Dome
TCCF44VI032
IFS04-D12-OIA4
4MP , 2.7-13.5 MFZ , IR Mini-Dome
TCCF48VI032
IFS08-D13-OIA4
8MP , 3.6-11 MFZ , IR Mini-Dome
NOTE: It should be assumed that this issue will affect any Gen4 Flex using Illustra SS018.24.03.00.0010 not just those listed.
Solution
Downgrade the camera firmware to the prior firmware version Illustra.SS018.06.05.00.0005, available HERE.
This guide will outline the steps needed to configure the tool SEQ on a PC in order to use scripts provided by Engineers at Exacq Technologies to aid in debugging Enterprise Manager Support Diagnostic Logs.
Pre-Requisites:
This guide will assume you have downloaded Enterprise Manager support diagnostic logs for the purpose of debugging.
This guide will assume you have downloaded the importEMlogs.ps1 powershell script.
This guide will assume you have downloaded the latest available version of the SEQ application program.
Initial installation and configuration steps
You must first install latest version of SEQ on your PC
You must then configure SEQ as follows: 2.A. change to the directory of saved log file in Powershell in example: cd C:\Users\youruser\Downloads\Diagnostics_year_month_day_time\EnterpriseManager
generate an API key by accessing the SEQ UI, located at http://localhost:5341 > Settings > API KEYS
open the importEMlogs.ps1 file provided by Engineering in notepad and observe the following commands:
To set a default server URL and API key, run the commands below: seqcli config -k connection.serverUrl -v https://your-seq-server
in example – you could run the following commands: (use HTTP unless certs are configured) seqcli config -k connection.serverUrl -v http://localhost:5341 seqcli config -k connection.apiKey -v YOURAPIKEY123456789
5. It may be necessary to set the system environmental variable for SEQCLI to work properly. You can do so by searching Windows for ” Environmental Variables “. Open the windows and add the entry for SEQCLI, as listed in the photo below:
Your SEQ instance should now be properly configured for use allowing you to send the Diagnostic Data to the SEQ server now installed.
Additional steps are now required after completion of the initial configuration in order to start using SEQ to debug Enterprise Manager Support Diagnostic Logs, as follows:
1. You must first place importEMlogs.ps1 powershell script provided by Engineering inside the unzipped “EnterpriseManager” directory of the support diagnostic log file you wish to debug.
2. change directory to the proper logfile directory “EnterpriseManager” listed above, and then run the following command:
You may now view the logs in the SEQ UI by navigating to Events and setting the proper filters. More documentation regarding the usage of SEQ can be found at: https://docs.datalust.co/docs/the-seq-query-language <br>
Documentation for SEQ filtering can be found HERE.
A few Customers have seen Needs Prep in the Exacq Client on the Storage Page under Volume and Hardware. The Drive Tab drives will all show healthy. The only issue seen is a false negative indicating that the Unit 1 c0/v0 shows “Needs Prep”, seen below. None of the drives listed under Unit 1 will indicate any issue and show up as healthy.
The Volume tab on the Storage page will also show that the volume “Needs Prep” and is only cosmetic.
Product
exacqVision Server versions 23.09.9.0 and 24.03
Steps to Reproduce
Update exacqVision Server to versions 23.09.9.0 or 24.03. The Hardware tab and Volume tab will show the Status “Needs Prep”.
Expected Results
Drive Status is “Healthy”. “Needs Prep” should not be shown unless the drive needs to be prepped or formatted for newly added drives.
Actual Results
Needs Prep is displayed on Volume tab and the Unit under the Hardware tab.
Solution
If a this issue is seen, update exacqVision Server to version 24.03.7.0.
exacqVision Enterprise Manager (EM) provides a web-based dashboard to monitor system health, maximize surveillance uptime, manage large numbers of exacqVision system users, transfer camera licenses, and perform software updates across distributed exacqVision systems.
Some level of enterprise management may be performed via the exacqVision Client for Enterprise licensed NVRs. But Enterprise licensing allows you to use Enterprise Manager for no extra cost and take advantage of even more enterprise level features, such as:
Automatic Failover, providing redundancy to NVRs
Camera Inspection, a tool assisting with maintenance
License Transfer, allowing the migration of camera licenses between NVRs, or allotted from a license pool
Schedule singular or recurring configuration backups
Without Enterprise Manager
Without EM, a user with the exacqVision Client will connect to each exacqVision Server to manage system licenses, check cameras individually for issues, and update exacqVision software. Though it is possible to use the Enterprise page in the Client to manage users, configure notifications, and perform manual failovers. As the number of exacqVision Servers in your organization increases this can become much more time consuming and complex.
With Enterprise Manager
EM provides a singular web-based dashboard to instantly view the health status of hundreds of exacqVision Servers and camera connections across your entire organization. EM also provides the ability to configure spare systems providing automated Failover should a system encounter a power, storage, or maintenance issue. Transfer camera licenses between systems as needed or utilize a license pool to instantly add licenses to systems after hours.
Enterprise Manager also provides the ability to schedule tasks to take place in the future, or schedule recurring tasks, including configuration backups or software updates.
Enterprise Manager also allows administrators to logically group exacqVision Server instances to their choosing, such as by geographical area, building, or functional level. This provides better control of system and user management, as well as user access to system resources.
Each user’s exacqVision Desktop Client instance may also have their system lists automatically synchronized with EM permitting administrators to auto update the list of NVRs each user connects with.
Enterprise Manager communicates with each exacqVision Server using the same port the Desktop Client software uses, by default this is port 22609. Failover and Failback features utilize port 28744.
After reboot of server or restarting the service the camera will exhibit a invalid credential along with a 401 Error.
This was seen on a system that required restarting the system after every Windows Update.
Product
Server 23.06.1.0
Windows Server 2016
Camera: Samsung QNV-C8083R FW 2.21.10.20230908_R
Steps to Reproduce
Restart system and the camera would be locked out of the user attempt to log into the camera and would need to power cycle the camera to enable it to connect. You can confirm this by logging into the cameras gui and finding the following error:
In our client we will show the following logs:
2/25/2024 10:11:25.925 AM (GMT-5:00) SamsungPI Error 7.230.122.80 - Initial discovery failed with error 401. The connection will NOT be retried.
2/25/2024 10:11:25.925 AM (GMT-5:00) SamsungPI Verbose 7.230.122.80 Network error 401 from request https://7.230.122.80/stw-cgi/system.cgi?msubmenu=deviceinfo&action=view using scheme https.
Expected Results
We should be able to reconnect to the camera with no log in failures after a system / server restart.
Actual Results
Camera will fail to connect to Exacq until you power cycle the camera.
Solution
Update the fw to FW version 2.21.10b_20240227-R6 by contacting Samsung to get this fw. AES- 758 is still being investigated and requested that the IP Camera Integration page Be Updated with new test Records form FirmWare Version 2.21.10b_20240227-R6.
There are some reports that after setting up Global At Most Rules the data is not removing older content off the drives. For example if recording has been taking place for a year and Global At Most Rule is set up after a year of recording some of the older content is not being removed from the data drives.
Product
Server 23.09.9.0
Linux 18.04
Steps to Reproduce
Oldest content on the storage drive will show content past the current Global At Most Rule that are configured. This was seen on units that had been recording for a long amount of time. Then at some point a Global At Most Rule was created. After the 30 days the data was not being removed from the system.
Expected Results
We should purge older data. However if there is a year worth of data we may need to give it a hand to clear out in special cases where customer need to see a certain amount of Oldest content on the Storage page.
Actual Results
If data is on the unit for 365 days, then it can take time for that data to be purged. It will keep showing Oldest content of 365 days until it successfully purges the data.
Solution
A work around is to delete some of the older content outside their current Global At Most Rule.
1. Stop the server and check the data folders on the drives.
2. NOTE: ALWAYS HOLD SHIFT and then hit the Delete Key. If you do not do this it can fill up the OS drive’s recycling bin. Remove Years, Months as needed from the data folder.
3. Start the exacqVision Server Service and allow up to 5 minutes for the Sweeper to run. We delay the Sweeper service from starting right away on purpose.
4. Monitor the logs on the server around the 5 minutes, and search for a sweeper event, and then look for a fscleanup event in the logs. If this is seen you can validate on the Storage page if the Oldest Content numbers change within the next several minutes down to the size of the At Most Rule 30 Days.
In the following example we stopped the service and removed data off the drives down to 62 days and 9 hours. After removing the data we started the service and waited 5 minutes.
After 5 minutes you should see the following in the logs.
PSFPI Verbose Sweeper - expiring all files older than Tue Apr 2 10:20:58 2024.
This indicates that the Sweeper is looking at the older content on the drive and preparing it to be removed.
After a few more minutes the oldest content was reduced down to the target Global At Most Rule of 30 days.
