Categories
Sales Materials Sell Sheets Documentation exacqVision Enterprise Categories Products

Enterprise Manager Diagram

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.

<br>

Related Articles

Categories
Cloudvue Cameras Cloudvue Cloudvue Gateway Documentation Quick Start Guides Categories Products

Cloudvue Networking Diagrams

Cloudvue Gateway

<br>

Cloudvue Camera to Cloud (C2C)

<br>

Categories
Documentation Quick Start Guides exacqVision Mobile exacqVision Webservice Categories

Remote exacqVision Connection Diagrams

The method used for connecting to an exacqVision system from outside the LAN it resides on will depend on your network configuration and use case. Examples are provided below based on each method.

Remote Connections

Remote Connections are supported by exacqVision Server/Client 24.09 and above to facilitate connections from the exacqVision Mobile app. When considering the network configurations Remote Connections eliminate the need to open ports or enable port forwarding rules on your router by using Exacq’s Remote Connectivity service. Users of the mobile app enter an access code generated by the system admin and the Remote Connectivity agent handles the connecting of the mobile app user and the Server.

NOTE: Remote Connectivity does not accept connections for the Desktop Client software or the earlier Exacq Mobile 3 app. Only exacqVision Mobile 24.09 and higher are supported.

<br>

Traditional

In a traditional setup, the site’s router is configured to port forward incoming external connections on each port. The ports configured for forwarding incoming traffic vary depending on whether users will connect via exacqVision Desktop Client software, the web browser client, or a mobile app.

<br>

Web Relay Service

Sites using exacqVision Web Service 19.06 and higher may wish to take advantage of the web service Relay, which provides a web-based proxy to connect to, avoiding the need to configure the router for port forwarding. When enabled, the exacqVision Web Service Status page will display the Relay Service IP. Remote users will then be able to connect their Exacq Mobile 3 app or web browser client directly to this proxy IP address.

NOTE: The Relay Service does not accept connections for the Desktop Client software, only web browser and Exacq Mobile 3 connections.

<br><br>

Related Articles

<br>

Categories
Knowledge Support Support exacqVision Enterprise exacqVision Client exacqVision Server exacqVision Mobile exacqVision Webservice Categories Products

Exacq Software/Service Connections Diagram

This diagram illustrates how the various Exacq applications work together and the ports used to communicate.

Internal (LAN)

Remote (WAN)

In cases where external users plan to connect for remote monitoring, you will may need to configure port forwarding on your router to allow traffic on those ports to pass through. exacqVision provides several ways to connect to your system from outside of your site’s LAN.

  • The Desktop Client software requires port forwarding.
  • Users of the exacqVision Mobile app may configure port forwarding or use the Remote Connectivity feature, configured within the Desktop Client.
  • Users connecting with the Web Browser Client or the Exacq Mobile 3 app may configure port forwarding, or use the Relay Service, configured within the exacqVision Web Service.

Remote Management

In the case of the Integrator Service Portal (ISP), this may connect to the server using an inbound connection to port 22609, or the server may be configured for an outbound connection to reach out to the ISP.

Additional Links

See also: exacqVision Default Ports

See also: Example Network Diagram for Multi-NIC Systems

<br>

Categories
Knowledge Support Support exacqVision Server Categories Products

Example Network Diagram for Multi-NIC Systems

Best practice for servers with more than one NIC includes isolating camera traffic to a separate scheme. This practice not only isolates camera bandwidth consumption from other network traffic, but also adds an additional layer of security to prevent workstation users from accessing cameras and video streams directly.

Whether using separate network switches or creating a VLAN on shared switches, the concept is the same.

<br>

IMPORTANT: DO NOT place both NICs within the same subnet. This is a poor network practice that WILL cause communication problems. Administrators that wish to attempt utilizing more than one NIC within a single subnet for redundancy or transfer speeds must configure NIC bonding/teaming. This is only recommended for systems with more than two NICs so that cameras may continue to be isolated from other network traffic.
See also:

<br>

External Connectivity

For administrators seeking to connect from outside the local network, across a WAN or MAN, see also:
Remote exacqVision Connection Diagrams

<br><br>