Tag: S-Series

Categories
Knowledge Support Support exacqVision Server Categories Products exacqVision Hardware

When trying to connect to S-Series archive target the status is “Disconnected”

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

  • An Exacq NVR with Windows OS
  • Exacq S-series storage server

Steps to Reproduce

  1. Create a volume for Archiving on the S-Series system.
  2. Try to connect to that archiving target from NVR.
  3. Apply the settings.

Expected Result

Arching target is ‘Connected’

Actual Result

Archiving target is ‘Disconnected’

Work Around

None

Solution

The local group policy Network Security: LAN Manager authentication level must be set to “send NTLMv2 response only. Refuse LM and NTLM”

<br>

Categories
Knowledge Support Support exacqVision Enterprise exacqVision Client exacqVision Server Categories exacqVision Webservice 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 exacqVision Client Categories Products

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:

  1. Exporting settings from exacqVision Client with network adapter bonding configuration (which is the default on S-Series systems).
  2. Importing settings on a system with no bonding, or a system with a bond name that is different from the name in the exported settings.

If this occurs, the following lines will be logged in the server’s log file:

{{{

StreamPI Warning Error enabling interface eth1 –
/etc/network/interfaces:21: interface eth0 declared allow-auto twice
/sbin/ifup: couldn’t read interfaces file “/etc/network/interfaces” .
StreamPI Warning Error enabling interface eth0 –
/etc/network/interfaces:21: interface eth0 declared allow-auto twice
/sbin/ifup: couldn’t read interfaces file “/etc/network/interfaces” .
}}}

<br>

Workaround

  1. After importing the settings, manually edit /etc/network/interfaces and remove duplicate adapter entries.
  2. Restart networking with sudo /etc/init.d/networking restart, or restart the system.
Categories
Knowledge Support Support exacqVision Client Categories Products

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 returned, the following command with add the program to your path.

$ sudo ln -s /opt/MegaRAID/storcli/storcli /usr/local/bin/storcli

Finally, restart the server service and your drives should be fully configurable.

Categories
Knowledge Support Support exacqVision Server Categories Products

“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 these steps:

  1. Open a Terminal window.
  2. Type cd /var/log.
  3. Type sudo ls -lh to view a list of directory files and the size of each file (this might require root access).
  4. Look for files that use a large amount of space, perhaps 100KB or larger.
  5. Delete the large files by typing sudo rm immediately folllowed by the filename. For example, type sudo rm tw_mgmt.log.
  6. Type cd /var/log/samba.
  7. Repeat steps 3 to 5 in this location to list, find, and remove large files.
Categories
Knowledge Support Support exacqVision Server Categories Products

Extended storage (iSCSI target) recreation steps

If S-Series storage page does not populate: IQN, NVR IP, extended storage type)

On the S-Series

  1. On S-Series > Storage page > Drive tab:
    Disable S-Series volumes.

  2. On Extended tab:
    Disable S-Series targets, then delete S-Series portal.

  3. Reboot the S-Series.

  4. If the IQN still does not populate, continue with steps 5-7.

  5. On the S-Series, open Terminal and perform the following:
    1. sudo gedit /etc/tgt/targets.conf
      (Delete all lines without a # sign)

    2. sudo tgt-admin --delete all -f

    3. sudo service tgt restart

    4. sudo tgt-admin -s | grep Target
      (If S-Series volumes appear: sudo tgt-admin --offline tid=# )

  6. On S-Series Storage > Network tab:
    Select the quantitiy of volumes needed.

  7. On S-Series Storage > Network tab:
    Re-add extended storage settings and NVR IP address

<br>

If NVR storage page does not populate: Healthy status

On the NVR

  1. On the Storage page > Drive tab:
    Disable S-Series volumes.

  2. On Storage page > Extended tab:
    Disable S-Series targets, then delete S-Series portal.

  3. Open Terminal and perform the following:
    1. grep mnt /proc/mounts
      (If S-Series volumes appear: sudo umount -l /mnt/edvr/# )

    2. ls /mnt/edvr
      (If S-Series volumes appear: sudo rm -r /mnt/edvr/#

    3. sudo ls /etc/iscsi/nodes
      (If IQNs appear: sudo iscsiadm -m discovery -o delete -p SSRS-IP )

    4. grep mnt /etc/fstab
      (If S-Series volumes appear: sudo gedit /etc/fstab then delete lines containing S-Series volumes)

    5. sudo rm /usr/local/exacq/server/psfpi.xml

    6. sudo rm /usr/local/exacq/server/archivepi.xml

    7. sudo service edvrserver restart

  4. On Storage page > Extended tab:
    Re-add S-Series volumes.

<br>

Categories
Knowledge Support Support exacqVision Enterprise Categories Products

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:

  1. On the S-Series system, download the udev_gen.sh script (attached below).
  2. cd to the location where the script was downloaded and run sudo ./udev_gen.sh.

The script will request storage updates from the kernel, and the disks should appear on the Network tab.

Categories
Knowledge Support Support Categories Products exacqVision Hardware

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 sda*brw-rw---- 1 root disk   8,  0 May 22 12:34 sdabrw-rw---- 1 root disk   8,  1 May 22 12:34 sda1brw-rw---- 1 root disk   8, 10 May 22 12:34 sda10brw-rw---- 1 root disk   8, 11 May 22 12:34 sda11brw-rw---- 1 root disk   8, 12 May 22 12:34 sda12brw-rw---- 1 root disk   8, 13 May 22 12:34 sda13brw-rw---- 1 root disk   8, 14 May 22 12:34 sda14brw-rw---- 1 root disk   8, 15 May 22 12:34 sda15brw-rw---- 1 root disk 259,  2 May 22 12:34 sda16brw-rw---- 1 root disk 259,  3 May 22 12:34 sda17brw-rw---- 1 root disk 259,  4 May 22 12:34 sda18brw-rw---- 1 root disk 259,  6 May 22 12:34 sda19brw-rw---- 1 root disk   8,  2 May 22 12:34 sda2-rw-r--r-- 1 root root 2097152 May 22 12:34 sda20brw-rw---- 1 root disk 259, 11 May 22 12:34 sda21brw-rw---- 1 root disk   8,  3 May 22 12:34 sda3brw-rw---- 1 root disk   8,  4 May 22 12:34 sda4brw-rw---- 1 root disk   8,  5 May 22 12:34 sda5brw-rw---- 1 root disk   8,  6 May 22 12:34 sda6brw-rw---- 1 root disk   8,  7 May 22 12:34 sda7brw-rw---- 1 root disk   8,  8 May 22 12:34 sda8brw-rw---- 1 root disk   8,  9 May 22 12:34 sda9 

<br>

Workaround

Reboot the system after partitioning the RAID volume, but before attempting to set partition(s) to extended storage or archiving.

<br>

Version Affected

Ubuntu 18.04
exacqVision Server versions lower than 20.06.1

<br>

Version Fixed

exacqVision Server 20.06.1

Categories
User Guides Documentation Categories Products exacqVision Hardware

exacqVision S-Series Enterprise

exacqVision-S-Series-Enterprise.pdf
Categories
Documentation Data Sheets Categories Products exacqVision Hardware

KSA Declaration S Series

KSA-Declaration-S-Series.pdf