March 2010 – Exacq

Retrieved From HowtoForge

Setting Up The Initiator

Install the initiator:

sudo apt-get install open-iscsi

Next we open /etc/iscsi/iscsid.conf…

sudo nano /etc/iscsi/iscsid.conf

… and set node.startup to automatic:

Then we restart the initiator:

sudo /etc/init.d/open-iscsi restart

Now we connect to the target (server2) and check what storage devices it has to offer:

sudo iscsiadm -m discovery -t st -p IP_Address_of_ISCSI_Server

server1:~# iscsiadm -m discovery -t st -p 192.168.0.101 192.168.0.101:3260,1 iqn.2001-04.com.example:storage.lun1 server1:~#

sudo iscsiadm -m node

server1:~# iscsiadm -m node 192.168.0.101:3260,1 iqn.2001-04.com.example:storage.lun1 server1:~#

The settings for the storage device iqn.2001-04.com.example:storage.lun1 on 192.168.0.101:3260,1 are stored in the file /etc/iscsi/nodes/iqn.2001-04.com.example:storage.lun1/192.168.0.101,3260,1/default.

We need to set the username and password for the target in that file; instead of editing that file manually, we can use the iscsiadm command to do this for us:

sudo iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --op=update --name node.session.auth.authmethod --value=CHAP sudo iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --op=update --name node.session.auth.username --value=iSCSI_username sudo iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --op=update --name node.session.auth.password --value=iSCSI_password

Now we can log in, either by running…

sudo iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --login

server1:~# iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --login Logging in to [iface: default, target: iqn.2001-04.com.example:storage.lun1, portal: 192.168.0.101,3260] Login to [iface: default, target: iqn.2001-04.com.example:storage.lun1, portal: 192.168.0.101,3260]: successful server1:~#

… or by restarting the initiator:

sudo /etc/init.d/open-iscsi restart

(If you want to log out, you can run iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --logout)

If your iSCSI device has already been formated, and contains data, please skip to Mounting your drive.

Continue on ONLY if your device is being set up for the first time, or you instructed to do so by tech support.

In the output of

sudo fdisk -l

you should now find a new hard drive (/dev/sdb in this example); that’s our iSCSI storage device:

server1:~# fdisk -l

Disk /dev/sda: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00031334

Device Boot Start End Blocks Id System /dev/sda1 * 1 3749 30113811 83 Linux /dev/sda2 3750 3916 1341427+ 5 Extended /dev/sda5 3750 3916 1341396 82 Linux swap / Solaris Disk /dev/sdb: 21.4 GB, 21474836480 bytes 64 heads, 32 sectors/track, 20480 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Disk identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table server1:~#

To use that device, we must format it (replace /dev/sdX with the value obtained from the last command):

sudo fdisk /dev/sdX

server1:~# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x882944df.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won’t be recoverable.

The number of cylinders for this disk is set to 20480.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

Command (m for help): <– m
Command action
 a toggle a bootable flag
 b edit bsd disklabel
 c toggle the dos compatibility flag
 d delete a partition
 l list known partition types
 m print this menu
 n add a new partition
 o create a new empty DOS partition table
 p print the partition table
 q quit without saving changes
 s create a new empty Sun disklabel
 t change a partition’s system id
 u change display/entry units
 v verify the partition table
 w write table to disk and exit
 x extra functionality (experts only)

Command (m for help): <– n
Command action
e extended
p primary partition (1-4)
<– p
Partition number (1-4): <– 1
First cylinder (1-20480, default 1): <– ENTER
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-20480, default 20480): <– ENTER
Using default value 20480

Command (m for help): <– t
Selected partition 1
Hex code (type L to list codes): <– L

0 Empty 1e Hidden W95 FAT1 80 Old Minix be Solaris boot 1 FAT12 24 NEC DOS 81 Minix / old Lin bf Solaris 2 XENIX root 39 Plan 9 82 Linux swap / So c1 DRDOS/sec (FAT- 3 XENIX usr 3c PartitionMagic 83 Linux c4 DRDOS/sec (FAT- 4 FAT16 <32M 40 Venix 80286 84 OS/2 hidden C: c6 DRDOS/sec (FAT- 5 Extended 41 PPC PReP Boot 85 Linux extended c7 Syrinx 6 FAT16 42 SFS 86 NTFS volume set da Non-FS data 7 HPFS/NTFS 4d QNX4.x 87 NTFS volume set db CP/M / CTOS / . 8 AIX 4e QNX4.x 2nd part 88 Linux plaintext de Dell Utility 9 AIX bootable 4f QNX4.x 3rd part 8e Linux LVM df BootIt a OS/2 Boot Manag 50 OnTrack DM 93 Amoeba e1 DOS access
b W95 FAT32 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O c W95 FAT32 (LBA) 52 CP/M 9f BSD/OS e4 SpeedStor e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs f W95 Ext'd (LBA) 54 OnTrackDM6 a5 FreeBSD ee EFI GPT 10 OPUS 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/
11 Hidden FAT12 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC b 12 Compaq diagnost 5c Priam Edisk a8 Darwin UFS f1 SpeedStor 14 Hidden FAT16 <3 61 SpeedStor a9 NetBSD f4 SpeedStor 16 Hidden FAT16 63 GNU HURD or Sys ab Darwin boot f2 DOS secondary 17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fd Linux raid auto 18 AST SmartSleep 65 Novell Netware b8 BSDI swap fe LANstep 1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid ff BBT 1c Hidden W95 FAT3 75 PC/IX Hex code (type L to list codes): <-- 83

Command (m for help): <– w
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.
server1:~#

Afterwards, the output of

sudo fdisk -l

should look as follows:

server1:~# fdisk -l

Disk /dev/sda: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00031334

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        3749    30113811   83  Linux
/dev/sda2            3750        3916     1341427+   5  Extended
/dev/sda5            3750        3916     1341396   82  Linux swap / Solaris

Disk /dev/sdb: 21.4 GB, 21474836480 bytes
64 heads, 32 sectors/track, 20480 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Disk identifier: 0x882944df

Device Boot Start End Blocks Id System
/dev/sdb1 1 20480 20971504 83 Linux
server1:~#

Now we create a filesystem on /dev/sdb1…

sudo mkfs.ext3 /dev/sdX1

Issue the following command, and make note of the largest number listed

ls /mnt/edvr/

server1:~# ls /mnt/edvr 0 1 server1:~#

Mount the drive with the command below, substituting Y with the the largest number returned from the previous command + 1 (2 in our example)

sudo mount /dev/sdX1 /mnt/edvr/2

You should now see the new device in the outputs of…

sudo mount

server1:~# mount /dev/sda1 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/sdX1 on /mnt/edvr/2 type ext3 (rw) server1:~#

… and

sudo df -h

server1:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1              29G  685M   27G   3% /
tmpfs                 253M     0  253M   0% /lib/init/rw
udev                   10M   88K   10M   1% /dev
tmpfs                 253M     0  253M   0% /dev/shm
/dev/sdX1              20G  173M   19G   1% /mnt/edvr/Y

server1:~#

You can unmount it like this:

sudo umount /mnt/edvr/Y

To have the device mounted automatically at boot time, e.g. in the directory /storage, we create that directory…

mkdir /storage

… and add the following line to /etc/fstab:

sudo nano /etc/fstab

For test purposes, you can now reboot the system:

sudo reboot

After the reboot, the device should be mounted:

sudo mount

df -h server1:~# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda1 29G 685M 27G 3% / tmpfs 253M 0 253M 0% /lib/init/rw udev 10M 88K 10M 1% /dev tmpfs 253M 0 253M 0% /dev/shm /dev/sdX1 20G 173M 19G 1% /mnt/edvr/Y

Depending on the model of Exacq NVR, or optional upgrades selected, your system may offer network interfaces with varying maximum data speeds. If you build your own system, or if you connect to a network with slower infrastructure, you might not achieve the maximum stated performance.

Commonly listed network interface speeds on Exacq NVRs

Name	Maximum Throughput
1000BASE-T	1,000 Gbps (1 Gbit/s)
2.5GBASE-T	2,500 Gbps (2.5 Gbit/s)
10GBASE-T	10,000 Gbps (10 Gbit/s)

Auto-negotiation

Network interfaces are normally configured for auto-negotiation, in which two connected devices agree on shared communication settings, such as communication speed and duplex mode. This means a device capable of communicating at 1000 Mbps will be limited to 100 Mbps if the other device it is connected to has a 100 Mbps maximum speed.

Use the below methods to determine your interface’s connection speed.

exacqVision Desktop Client Network Settings

Within the exacqVision Desktop Client, the negotiated network speed for a network interface can be seen by navigating to the Configure System node on the left-hand navigation tree, then clicking on the Network tab.

Highlight the chosen network interface from your list of Interfaces.

Above the interface’s IP Address Configuration section is the Status, which will also display the detected network speed.

Windows CLI

On Windows systems, you may use the PowerShell command line interface to check the negotiated network speed for the interface as well as whether it is using full-duplex or half-duplex. Enter the following command:

Get-NetAdapter | select interfaceDescription, name, status, linkSpeed, fullduplex

Ubuntu CLI

On Ubuntu systems, open a Terminal interface. Enter the following command, replacing INTERFACE with the name of your chosen interface:

ethtool INTERFACE

The example below, uses an interface named ‘ens18’ and shows the supported and advertised speeds and duplex modes the interface is capable of. However, the negotiated speed can be found further down named, ‘Speed’. This also indicates the interface is currently using full-duplex mode.