Tag: Server

Categories
Knowledge Support Support exacqVision Server Categories Products

3rd Party Linux servers and recording to a NAS?

This process is not officially supported or endorsed by Exacq. Use at your own risk.

When the exacqVision Server software starts, it will look into the following location for storage purposes:

/mnt/edvr/*

NOTE – * – This is typically a number on systems built by Exacq.

Any volume that is mounted into the /mnt/edvr location will be available for storage.

NAS Setup

Here is an example setup using FreeNAS:

  1. In the BIOS Setup, set the hardware RAID (Striped with Parity).
  2. Set up FreeNAS on the computer server hard drive.
  3. Assign the system an IP Address.
  4. Set up NFS Share using FreeNAS.

Linux NVR

  1. If needed, log off as restricted user and log back in as an admin user.
  2. Launch the Terminal application.
  3. Create storage directoryfor your NAS location by typing:
    sudo mkdir /mnt/edvr/2
    NOTE – Ensure that there is not already a “2” directory – if so, pick a higher number
  4. Edit the /etc/fstab file to include the mounting of the NAS at startup by adding line
    %servername%:%/mnt/vce-nas/% /mnt/edvr/2 nfs defaults 0 0
    NOTE: %servername% is your full server name or IP address, and %/mnt/vce-nas/% is your NAS server mount point.
  5. Restart the exacqVision NVR Server to activate NAS Mount.
    sudo service edvrserver restart
  6. In the exacqVision Client, use the Storage tab to enable recording to /mnt/edvr/2.
  7. Verify that recordings are being stored on new mount point.
Categories
Knowledge Support Support exacqVision Server Categories Products

Starting iSCSI on Startup with Linux Systems

After you reach the point where everything is logged in (you are able to type iscsiadm –m session and get output), following is the generic syntax:

iscsiadm -m node -T <targetname> -p <ip:port> –op update -n node.conn[0].startup -v automatic

<br>

The parameters between < and > are substitutions.

The syntax for persistent binding devices discovered on an internal connection under Ubuntu would look like this:

iscsiadm -m node -p 172.16.16.1 –op update -n node.conn[0].startup -v automatic

<br>

Here’s a more complete breakout, with examples from another system with two volumes (vol1-test and vol2-test), each with two connection paths, to log in to:

root@xxx:/etc/iscsi# iscsiadm -m node -l

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.4.15.164,3260]

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.3.15.102,3260]

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol2-test.600176c34e91735e80bcbba748669f4a, portal: 10.4.15.164,3260]

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol2-test.600176c34e91735e80bcbba748669f4a, portal: 10.3.15.102,3260]

<br>

The following is used for persistent binding to just the first volume, by target name:

# iscsiadm -m node -T iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a –op update -n node.conn[0].startup -v automatic

root@xxx:/etc/iscsi# /etc/init.d/open-iscsi restart

 * Disconnecting iSCSI targets                                                  Logout session [sid: 1, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.4.15.164,3260]

Logout session [sid: 2, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.3.15.102,3260]

Logout session [sid: 3, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol2-test.600176c34e91735e80bcbba748669f4a, portal: 10.4.15.164,3260]

Logout session [sid: 4, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol2-test.600176c34e91735e80bcbba748669f4a, portal: 10.3.15.102,3260]

                                                                         [ OK ]

 * Stopping iSCSI initiator service                                      [ OK ]

 * Starting iSCSI initiator service iscsid                               [ OK ]

 * Setting up iSCSI targets

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.4.15.164,3260]

Login session [iface: default, target: iqn.2003-01.com.pivot3:raige.vol:34xen.defaultpool.vol1-test.600176c30c272e438f96ea2d48669f4a, portal: 10.3.15.102,3260]

                                                                         [ OK ]

<br>

NOTE: This just pulls in that target (vol1-test). Further, we could add by –p 10.3.15.164 in a second operation and pull in one other connection that the above did not add, for vol2-test on an IP basis (or, if this were the first operation, it would have added one connection to each volume). To turn off automatic binding for a given connection, you would use –v manual instead of -v automatic.

<br>

Also, none of this takes effect until the iSCSI daemon is restarted.

<br>

Starting-iSCSI-on-Startup-with-Linux-Systems.pdf
Categories
Knowledge Support Support Categories Products exacqVision Hardware

Enumerating more than Four Serial Ports in Linux

If a system is built with the Radisys motherboard or has two or more eDVR boards, there are more then four serial ports. However, Ubuntu 8.04 enumerates only four serial ports by default. To change the number of serial ports enumerated, complete the following steps:

<br>

  1. Edit menu.lst by typing sudo nano /boot/grub/menu.lst
  2. Find the line that starts with # kopt= and ends with ro and add the following to the end: 8250.nr_uarts=16
  3. Save the file by pressing Ctrl-o and then Enter.
  4. Exit by pressing Ctrl-x.
  5. Execute the following command to refresh grub: sudo update-grub

<br>

NOTE: The first character in “lst” is the lowercase letter L and not the number 1.

<br>

Enumerating-more-than-Four-Serial-Ports-in-Linux.pdf
Categories
Knowledge Support Support exacqVision Server Categories Products

Disabling Aero in Windows Vista (Aero causes OSD to have bars behind it in exacqVision software)

To disable Aero, complete the following steps in Windows Vista:

<br>

  1. Click Start, and then select Control Panel.
  2. Click Appearance and Personalization.
  3. Under Personalization, click Change the Color Scheme.
  4. In the Appearance Settings dialog, click Windows Vista Basic
  5. Click OK.

<br>

Disabling-Aero-in-Windows-Vista-Aero-causes-OSD-to-have-bars-behind-it-in-exacqVision-software.pdf