Tag: iSCSI Storage

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

Video Not Recording to iSCSI  with Status “Recording Not Possible”

Description

Video is not recording to customers iSCSI targets after a reboot.  Drive was reporting a status of “Recording Not Possible” on exacqVision Server 21.03.10.  Servers running exacqVision Server version 20.06 or older were showing a status of healthy, but were not recording.

Identification

Use the following to properly identify the issue before applying the fix.

  • Update to exacqVision Server version 21.03 or later. 
  • Check the drives status on the storage page.
  • If the status is “Recording Not Possible”
    • Enable debug level logging
    • Restart the exacqVision Server service
    • Monitor for log entries similar to those listed below, specifically Store Fails and GRV Fails
    • Check Extended Storage or Enterprise Storage for conflicting entries like those displayed below.
    • Once positively identified follow the steps outlined in the resolution section

Log files (debug level enabled)

Before Fix

After Fix

Enterprise Storage page was showing the Type as Local (iSCSI) on the servers which were not recording.   Servers which were recording report the volume type as Local. Note: The server showing the Status of “Recording Not Possible” was running newer exacqVision Server software 21.03.10 vs 20.06 or older for the others.

Another indication was that the iSCSI targets populated both the Targets and Partitions Section of  the Storage page,  Extended tab.  Whereas the servers which were recording normally populated only the iSCSI Targets.section

Resolution

  • rename archivepi.xml
  • rename psfpi.xml
  • restart exacqVision Server Service
  • Verify that storage targets are only listed in the Partition section of the Storage page (Configuration > Storage > Extended Tab)
  • Verify that the volume now has a type of Local on the Enterprise Storage page (Configuration > Enterprise > Storage)
Categories
Knowledge Support Documentation Support Products exacqVision Hardware

Enabling iSCSI Support on exacqVision Systems with Windows Embedded

Early versions of exacqVision systems with the Windows Embedded operating system did not have support for iSCSI. These systems were manufactured in in January and early February 2014.


To determine whether a system supports iSCSI, complete the following steps:

  1. Open the Start menu.
  2. Right-click Computer.
  3. Select Manage from the pop-up menu.
  4. Double-click Services and Applications.
  5. Double-click Services.
  6. If Microsoft iSCSI Initiator Service is not running, start it.
  7. Click Device Manager.
  8. Expand the Storage Controllers node if necessary.
  9. If you do not see Unknown Device, your system supports iSCSI.
  1. If you do see Unknown Device, right-click it, select Properties, select Details, and select Hardware IDs. If the value is ROOT\ISCSIPRT, your system does not support iSCSI.

To enable iSCSI support on the system, complete the following steps:

  1. Download iSCSIPack.zip from https://exacq.com/files and unzip it to a flash drive or directly to the exacqVision system.
  2. On the exacqVision system, navigate to the directory containing the unzipped installation files.
  3. Double-click the install.bat file.
  4. The installer prompts for administrator rights, installs the files, and restarts the system.
Enabling-iSCSI-Support-on-exacqVision-Systems-with-Windows-Embedded.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Set iSCSI Storage to Start Before ExacqVision Server in Windows

If you are recording video to an iSCSI target in Windows, it is important to ensure the iSCSI device is available in the operating system before the ExacqVision Server starts. Please follow the instructions from the Microsoft iSCSI Software Initiator Version 2.x Users Guide:

Note: The following information was written and published by Microsoft Corporation, which is responsible for the accuracy of the information.

<br>

Running automatic start services on iSCSI disks

The disk startup sequence in Windows when using the Microsoft iSCSI software initiator kernel mode driver is different from the startup sequence when using an iSCSI or other HBA. Disks exposed by the Microsoft iSCSI initiator kernel mode driver are available for applications and services much later in the boot process and in some cases might not be available until after the service control manager begins to start automatic start services. The Microsoft iSCSI initiator service includes functionality to synchronize automatic start services and the appearance of iSCSI disk. The iSCSI service can be configured with a list of disk volumes that are required to be present before the start of automatic start services.

In order to install automatic start services on volumes created from iSCSI disks you need to follow the following steps:

  1. Login to all of the targets your machine will be using. Ensure that these are the only targets that are logged in. Be sure that you have also made them persistent logins by using the iscsicli command PersistentLoginTarget or clicking on the appropriate option in the control panel applet.
  2. Configure all volumes on top of the disks using Disk Administrator
  3. Use the iscsicli commands BindPersistentVolumes, AddPersistentVolume, RemovePersistentVolume and ClearPersistentVolumes (or appropriate button in the control panel applet) to allow the iSCSI service to configure the list of persistent volumes

On Windows 2000 only, make the automatic service dependent upon the msiscsi service.

Note: If you have made any services dependent upon the Microsoft iSCSI initiator service, you will need to manually stop the service before upgrading or removing the Microsoft iSCSI Software initiator package.

<br>