Network Config

Description

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

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.

Steps to Reproduce

Power on unit
Check Windows Device Manager for listed network interfaces
Check exacqVision Client Network Settings

Expected Results

All network cards are recognized and appear listed.

Actual Results

Only one interface is listed.

Solution

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

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

AES-842 Has been created to investigate this.

Additional Steps

Pull the logs from the UEFI

Open CMD.
Enter the following:
mountvol z: /S
Type cd z: and press Enter.
Type dir and press Enter.
Type cd EXACQ and press Enter.
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.
Collect the txt and xml files from the logs and add them to a newly created ZIP file to copy from the system.
When done collecting logs, return to CMD and enter
mountvol z: /d
to remove the temporarily mounted volume.

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 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” .
}}}

Workaround

After importing the settings, manually edit /etc/network/interfaces and remove duplicate adapter entries.
Restart networking with sudo /etc/init.d/networking restart, or restart the system.