Tag: NIC

Categories
exacqVision Server Windows Knowledge Support Support exacqVision Server Products

Windows Server 2022 Showing Only One Network Card

Description 

Some Exacq NVRs built with Microsoft Windows Server 2022 only acknowledge one network interface, rather than two, when being configured out-of-box.

<br>

Product 

Issue has been noted on BBE systems ASRock Industrial IMB-X1313 system boards, listed below.

  • Z-Series systems
  • Some A-Series systems, depending on the system options ordered

NOTE: Windows Server OS is an optional upgrade for many systems, so this will not apply to all systems listed above.

<br>

Steps to Reproduce 

  1. Power on unit<br><br>
  2. Check Windows Device Manager for listed network interfaces<br><br>
  3. Check exacqVision Client Network Settings

<br>

Expected Results 

All network cards are recognized and appear listed.

<br>

Actual Results 

Only one interface is listed.

<br>

Solution

Attempt solution starting with Step 9 first. If this still fails, repeat steps beginning with Step 1, which requires opening the system chassis.

  1. Power the system down gracefully using the shutdown option from the OS.<br><br>
  2. Unplug system and press the power button to drain any residual power off the board.<br><br>
  3. Open the system, locate and remove the CMOS battery from the system board. Wait 5 to 10 minutes before continuing.<br><br>
  4. Replace the CMOS battery.<br><br>
  5. Reconnect power to the system.<br><br>
  6. Power on the system.<br><br>
  7. Enter the system BIOS or Boot Option menu and boot to the UEFI partition.<br><br>
  8. Check for changes in recognition of the additional network interface(s). If no change, continue with next steps.<br><br>
  9. Restart the system and enter BIOS.<br><br>
  10. Open to the Exit menu and select Load Defaults.<br><br>
  11. Reboot and enter BIOS again, select the UEFI partition as the boot option.<br><br>
  12. Check Windows Device Manager and Network Settings to validate that the additional interface(s) are detected.

<br>

AES-842 Has been created to investigate this.

<br>

Additional Steps

Pull the logs from the UEFI

  1. Open CMD.<br><br>
  2. Enter the following:
    mountvol z: /S<br><br>
  3. Type cd z: and press Enter.<br><br>
  4. Type dir and press Enter.<br><br>
  5. Type cd EXACQ and press Enter.<br><br>
  6. Open File Explorer and locate the logs in the Z partition. This is hidden by default. If you make them visible using File Explorer options, be sure to set to hidden again after you are done collecting logs.<br><br>
  7. Collect the txt and xml files from the logs and add them to a newly created ZIP file to copy from the system.<br><br>
  8. When done collecting logs, return to CMD and enter
    mountvol z: /d
    to remove the temporarily mounted volume.

<br>

Categories
Knowledge Support Support Categories Products exacqVision Integrations

Guidance on Using USB Network Interface Adapters

On occasion, Exacq Support is asked about using a USB network interface (NIC) on their system. This is more frequently asked by those with smaller units which may have only one network interface and a user is attempting to add additional network interfaces to span networks or attempt to increase network throughput by bonding/teaming multiple NICs.

Regardless of the system model or size, Exacq does not support or test USB NICs.

Exacq Support will also not recommend any specific NICs for this usage. Even NICs connected externally using USB 3.0 or USB-C may encounter issues, therefore Exacq only supports internally connected network interface cards and does not troubleshoot issues with third-party devices added by users.

<br>

Categories
Knowledge Support Cloudvue Cloudvue Gateway Support Categories Products

Configuring IP Addresses on a Cloudvue Gateway

Description 

This article describes how to set IP addresses as either static or DHCP for a Cloudvue Gateways onboard NICs.

Product 

  • Cloudvue Gateway

Prerequisites

  • Port #1 “NET” is connected to a network with internet access
  • The Cloudvue Gateway has be registered

Solutions

NOTE: Network Settings can only be viewed, not changed from cloudvue.com

Local Cloudvue

  • Open a web browser from a machine connected to the same network as the Cloudvue Gateway
  • Go to the LAN IP address of the Cloudvue Gateway for example http://192.168.1.180
    • Note: See Knowledge Base Article #15509 “Finding Cloudvue Gateway IP Addresses” for more details about finding IP Addresses
  • Login to the Local Cloudvue instance 
  • From the Navigation bar select Live
  • Expand Video Devices
  • Select the Cloudvue Gateway
  • From the Navigation bar select Settings
  • Select the Settings tab
  • Under Network Settings
    • PORT 1 “LAN”
      • This is the NIC labeled “NET” on the gateway and should be connected to the customers local area network
      • It can be configured to either obtain an IP address dynamically “DHCP” or be assigned a Static IP
      • DHCP (Default)
        • Tick DHCP
      • STATIC
        • Tick Static
        • Enter the desired IP address
        • Enter a Subnet Mask
        • Enter the IP address for DNS Server 1
        • Enter the IP address for DNS Server 2
      • Save the Changes
    • PORT 2  “Cameras”
      • This NIC is labeled POE on the gateway and should be connected to the Camera Network
      • It is intended to function as a DHCP server and assign a dynamic IP address to connected cameras
      • However, you can choose to set to static and manually IP connected cameras
      • DHCP Server (Default)
        • Tick DHCP Server
      • Static
        • To change the networking number scheme from the default 192.168.20.1
        • Enter a new IP address
        • Enter a Subnet Mask
      • NOTE: After changing PORT 2, all devices plugged into this port will need to be rebooted.
    • Once satisfied click SAVE to apply changes

Command Line

  • The overall process is
  • Establish an SSH connection to the Cloudvue Gateway
    • Enter your machines sudo password
    • Enter the smartvue SSH password  found in the SSH Section for the device in Cloudvue Manager.
  • Using either nano or vi edit the file /etc/network/interfaces
  • Make the desired changes to any NIC to set for either static or dhcp
  • Save the changes and exit the editor
  • Down and up the NICs which were changed to apply the changes or alternatively restart the Gateway

In this example both NICs em2 (LAN) and em1 (Cameras) are being set to a static IP address

Additional /etc/network/interfaces Examples

In this example NIC em2 (LAN) is set to static and em1 (Cameras) is set to DHCP

In this example NIC em2 (LAN) is set to DHCP and em1 (Cameras) is set to Static

Categories
Knowledge Support Support exacqVision Client exacqVision Server Categories exacqVision Hardware Products

NIC Bonding with Windows Server 2016 is only available through Server Manager

Description

Servers with Windows 10 or Linux allow bonding to be configured via exacqVision Client.

However, servers with Windows Server 2016 currently do not. Instead, bonding must be configured via Windows Server Manager:

  • Start Server Manager.
  • Click “Local Server” in left pane of window.
  • Locate the “NIC Teaming” item in window, and click its “Disabled” link.
  • In the NIC Teaming window, you can add, remove, and edit bonds.

Product 

  • exacqVision Server
  • Windows Server 2016

Expected Results 

  • NIC Bonding options are available in the exacqVision Client

Actual Results 

  • NIC Bonding options are not available in the exacqVision Client on systems running Windows Server 2016.

Solution

  • Configure NIC bonding using the OS Server Manger

<br>

Categories
Knowledge Support Support Categories Products exacqVision Hardware

Second on board NIC missing

Description

There have been a couple of servers manufactured at the Bentel facility with Q87 motherboard that does not detect the second on board NIC out of the box. This is due to a bios misconfiguration during manufacturing.

<br>

Platform

Linux and Windows with Q87 motherboard

The servers we found in the field with this issue were from the 25 and 26 week of 2017 and the serial number starts with 355S.

<br>

Fix

  1. Reboot the machine and press “F2” on the BIOS splash screen.
  2. Enter “admin256” as the BIOS password.
  3. Navigate to “Advanced > Onboard Devices Configuration”
  4. Verify that “Intel I211 LAN Controller” and “Intel I218 LAN Controller” are enabled.
  5. Press “F10” to save and exit.

<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>

Categories
Knowledge Support Support exacqVision Client Categories Products

NIC Bonding on exacqVision Client and Server

Beginning with version 5.10, NIC bonding is supported on exacqVision Client and Server. The following sections contain requirements and steps for enabling NIC bonding. <br>

Linux Ubuntu 10.04 and Later

Install ifenslave-2.6 package. <br>

apt-get install ifenslave-2.6 <br>

Add bonding module to modules list by editing /etc/modules. <br>

sudo gedit /etc/modules <br>

Add “bonding” at the end of the file. <br>

Load the bonding module. <br>

sudo modprobe bonding <br>

Windows 7 Systems Manufactured Before December 2013

You must be using Powershell version 2.0 and Intel Ethernet Adapters. NIC teaming is enabled by default in the Intel driver, so no additional steps should be necessary. <br>

Categories
Knowledge Support Support exacqVision Server Categories Products

How is exacqVision NVR software licensed?

The exacqVision VMS software licenses a specific number of channels to a key based upon the server NIC’s MAC address.

A license includes the maximum number of IP devices, an SSA period for software updates, analog video channels for Hybrid NVRs, and the functional level for the software. The functional levels are:

  • Start
  • Professional
  • Enterprise

See the Features Matrix for comparison details.<br><br>

Multiple NICs

If you have multiple NICs, the MAC address of only one NIC must be licensed. MAC addresses of the individual cameras are not required for a valid license.

See also Which MAC address can I license?

Software Subscription Agreement

A license key is valid for the period chosen when ordering. This license key includes a Software Subscription Agreement (SSA) allowing the software to be updated to versions released prior to the expiration date. Updates add new functionality and features, and may address bug fixes.

When an exacqVision SSA expires, no functionality of the software is lost. The system will continue to operate as is, but you will no longer be able to update to newer versions as they are released.

Additional years of SSA are available for purchase at the time of initial purchase or at a later time.

A new license key may be imported to expand he number of connected cameras, enhance the feature level, or extend the SSA period without restarting the software.

See also How do I check the software subscription status on my exacqVision server?

Applying a License

See How do I apply a license to an exacqVision Server?

<br>