Description When the Exacq NVR you are configuring to archive to an Exacq S-Series and the recording NVR is joined to a domain, there is a local Group Policy that must be configured to prevent receiving a ‘Disconnected’ status. Product Steps to Reproduce Expected Result Arching target is ‘Connected’ Actual Result Archiving target is ‘Disconnected’… Continue reading When trying to connect to S-Series archive target the status is “Disconnected”
Tag: S-Series
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 Port List PortDescription25Simple Mail Transfer Protocol (SMTP)80exacqVision Web Server/exacqVision Enterprise Manager (HTTP)How to change Web Service portsHow to change EM web ports389LDAP (Lightweight… Continue reading exacqVision Default Ports
Incorrect Network Configuration when Importing exacqVision S-Series Settings
Importing settings from exacqVision Client to an exacqVision S-Series system can cause an incorrect network configuration. This can occur in the following situations: Exporting settings from exacqVision Client with network adapter bonding configuration (which is the default on S-Series systems).Importing settings on a system with no bonding, or a system with a bond name that… Continue reading Incorrect Network Configuration when Importing exacqVision S-Series Settings
S-Series will not allow configuring volumes via the exacqVision client
If you are configuring your S-Series volumes from the exacqVision client, but they will not initialize, do the following: Check to see if the StorCLI binary is in your path. This is the program that allows exacqVision server to communicate with, and configure drives from the exacqVision client. $ ls /usr/local/bin/storcli If no results are… Continue reading S-Series will not allow configuring volumes via the exacqVision client
“Failed to write fstab” Error Displayed while Configuring S-Series Partitions
Symptom A “Failed to write fstab” error can appear if the system is running low on space on the root “/” partition. <br> Affected Versions This affects all exacqVision S-Series versions. A fix will be released at a later date. <br> Resolution To recover from this error, free up space on the root partition using… Continue reading “Failed to write fstab” Error Displayed while Configuring S-Series Partitions
Extended storage (iSCSI target) recreation steps
If S-Series storage page does not populate: IQN, NVR IP, extended storage type) On the S-Series On S-Series > Storage page > Drive tab:Disable S-Series volumes. On Extended tab:Disable S-Series targets, then delete S-Series portal. Reboot the S-Series. If the IQN still does not populate, continue with steps 5-7. On the S-Series, open Terminal and… Continue reading Extended storage (iSCSI target) recreation steps
Configuring exacqVision S-Series Enterprise System with LSI RAID Controller with all JBOD Disks
exacqVision S-Series systems with LSI RAID controller running exacqVision Server 6.4.x display an empty Network tab on the Storage page if all disks are configured for JBOD. To fix this issue, complete the following steps: On the S-Series system, download the udev_gen.sh script (attached below).cd to the location where the script was downloaded and run sudo ./udev_gen.sh.… Continue reading Configuring exacqVision S-Series Enterprise System with LSI RAID Controller with all JBOD Disks
S-Series may fail to partition RAID volume
Issue S-Series models running Ubuntu 18.04, may fail to create some partitions. This issue is not easily noticeable in exacqVision Client, unless the end user looks closely to observe gaps in the partition list. It can be more easily detected from terminal. Notice the “b” flag is missing indicating a non-block device. root@exacqu-desktop:/dev# ls -l… Continue reading S-Series may fail to partition RAID volume