https://wiki.ipbrick.com/api.php?action=feedcontributions&feedformat=atom&user=Daraujo 2026-05-13T12:25:24Z User contributions MediaWiki 1.23.2 https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T14:38:44Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> Connection to the Internet<br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/sdb<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/sdb /home3 ext4 defaults,usrquota,grpquota,user_xattr,acl 0 2<br /> <br /> Now, you need to run this script so as home3 can be added to the IPBRICK web interface.<br /> <br /> /opt/system/scripts/system_add_new_workareas.php 1<br /> <br /> You will get the following notification:<br /> <br /> Work Area 3 was successfully inserted!<br /> Don't forget to Apply Configurations to commit the changes.<br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Origin IP: [Storage IPs]<br /> Policy: ACCEPT<br /> <br /> <br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T14:33:10Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> Connection to the Internet<br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/sdb<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/sdb /home3 ext4<br /> <br /> Now, you need to run this script so as home3 can be added to the IPBRICK web interface.<br /> <br /> /opt/system/scripts/system_add_new_workareas.php 1<br /> <br /> You will get the following notification:<br /> <br /> Work Area 3 was successfully inserted!<br /> Don't forget to Apply Configurations to commit the changes.<br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Origin IP: [Storage IPs]<br /> Policy: ACCEPT<br /> <br /> <br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T13:52:27Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> Connection to the Internet<br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/sdb<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/sdb home3 ext4<br /> <br /> Now, you need to run this script so as home3 can be added to the IPBRICK web interface.<br /> <br /> /opt/system/scripts/system_add_new_workareas.php 1<br /> <br /> You will get the following notification:<br /> <br /> Work Area 3 was successfully inserted!<br /> Don't forget to Apply Configurations to commit the changes.<br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Origin IP: [Storage IPs]<br /> Policy: ACCEPT<br /> <br /> <br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T13:44:20Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> Connection to the Internet<br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/sdb<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/sdb home3 ext4<br /> noauto,defaults,usrquota,grpquota 0 2<br /> <br /> Now, you need to run this script so as home3 can be added to the IPBRICK web interface.<br /> <br /> /opt/system/scripts/system_add_new_workareas.php 1<br /> <br /> You will get the following notification:<br /> <br /> Work Area 3 was successfully inserted!<br /> Don't forget to Apply Configurations to commit the changes.<br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> NOTE: When you explicit a firewall rule, you must include the storage IPs!<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Policy: ACCEPT<br /> <br /> <br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T13:23:01Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> Connection to the Internet<br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/sdb<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/sdb home3 ext4<br /> noauto,defaults,usrquota,grpquota 0 2<br /> <br /> Now, you need to run this script so as home3 can be added to the IPBRICK web interface.<br /> <br /> /opt/system/scripts/system_add_new_workareas.php 1<br /> <br /> You will get the following notification:<br /> <br /> Work Area 3 was successfully inserted!<br /> Don't forget to Apply Configurations to commit the changes.<br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Policy: ACCEPT<br /> <br /> NOTE: When you explicit a firewall rule, you must include the storage IPs!<br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T13:19:57Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> Connection to the Internet<br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/sdb<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/sdb home3 ext4<br /> noauto,defaults,usrquota,grpquota 0 2<br /> <br /> Now, you need to run this script so as IPBRICK can detect the new home3<br /> <br /> /opt/system/scripts/system_add_new_workareas.php 1<br /> <br /> You will get the following notification:<br /> <br /> Work Area 3 was successfully inserted!<br /> Don't forget to Apply Configurations to commit the changes.<br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Policy: ACCEPT<br /> <br /> NOTE: When you explicit a firewall rule, you must include the storage IPs!<br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T12:53:20Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> Connection to the Internet<br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The /etc/iscsi/initiatorname.iscsi file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/sdb<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/sdb home3 ext4<br /> noauto,defaults,usrquota,grpquota 0 2<br /> <br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Policy: ACCEPT<br /> <br /> NOTE: When you explicit a firewall rule, you must include the storage IPs!<br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T12:24:15Z

<p>Daraujo: Daraujo moved page Isci to ISCSI</p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> <br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The \verb|/etc/iscsi/initiatorname.iscsi| file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/mapper<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/mapper home3 ext4<br /> noauto,defaults,usrquota,grpquota 0 2<br /> <br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Policy: ACCEPT<br /> <br /> NOTE: When you explicit a firewall rule, you must include the storage IPs!<br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/Isci 2015-02-11T12:24:15Z

<p>Daraujo: Daraujo moved page Isci to ISCSI</p> <hr /> <div>#REDIRECT [[ISCSI]]</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T12:21:23Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v6.0<br /> <br /> <br /> <br /> == Installation ==<br /> <br /> The installation process is done via sources list update.<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The \verb|/etc/iscsi/initiatorname.iscsi| file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.ext4 /dev/sdb<br /> <br /> fstab mapping is done by device and it can be captured via /dev/mapper<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> /dev/mapper home3 ext4<br /> noauto,defaults,usrquota,grpquota 0 2<br /> <br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Policy: ACCEPT<br /> <br /> NOTE: When you explicit a firewall rule, you must include the storage IPs!<br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T11:04:59Z

<p>Daraujo: </p> <hr /> <div><br /> == Introduction ==<br /> <br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> <br /> == Requirements ==<br /> <br /> <br /> IPBrick v5.3 or later versions.<br /> <br /> <br /> <br /> == Software ==<br /> <br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> <br /> <br /> == Installation ==<br /> <br /> <br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> <br /> == Configuration ==<br /> <br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The \verb|/etc/iscsi/initiatorname.iscsi| file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - '''NO AUTHENTICATION''': If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - '''WITH AUTHENTICATION - CHAP''': <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.xfs /dev/sdb<br /> <br /> To create a label follow this example:<br /> <br /> mkfs.xfs -L SANSERVER /dev/sdb<br /> <br /> NOTE: XFS filesystem labels can be at most 12 characters long; if label is longer than 12 characters, mkfs.xfs will not proceed with creating the filesystem.<br /> <br /> Execute these commands to access the new disc and check if all is OK:<br /> <br /> mount LABEL=SANSERVER /mnt<br /> df -h<br /> umount /mnt<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> LABEL=SANSERVER home3 xfs<br /> noauto,defaults,usrquota,grpquota 0 2<br /> <br /> The following scripts will enable automount.<br /> <br /> Execute the transcribed script (iscsi-aux.sh) at the server (the transfer can be made by scp):<br /> <br /> #!/bin/bash<br /> <br /> TMPFILE=/tmp/iscsi_aux.txt<br /> TMPFILE2=/tmp/iscsi_aux.tgz<br /> <br /> <br /> echo &quot;begin-base64 644 ola<br /> H4sIAGVBGVAAA+3UX0+CUBgGcK7Pp3ib3XShHA5/TpvrwgzrLAInVtdIZ5Mt<br /> wQlubc3v3gFqmTNdm5qt93cDcl7EnccHWcR6kiZF60kX/cvmJJunRTPJ4zxp<br /> 5WNtN6jCbbs6KqtHanKqGYxSh5nccdR1w+Im14Du6PkbzfMimgFosywrNs1t<br /> W/+jGif6KEn1UZSPCSGNgdv3RLczdKEXeF7wKPxr8ITvhurzANxO9wZE2A0F<br /> XLkPouvCXXDvD6EfCH9IqgXjQh9nE2kSEke5hNNXYwFJSgDKbS7O1Empemb1<br /> X1MT9X2L96V2uxrOpl9m5+uHl9eaz+u+S+ZRTEqNnvA7HpEvSQGUkN/e92Mh<br /> Vf9nMVP1Dw1nT2+Aqv+cf9v/8vyj/5btaJQxRh0NmC73/3b65/2v86dqg2/P<br /> jV/P36JmeZ0xw7Yw/0Oo83eOJn/GrSp/jvkfxHL/WTaVab29O33Gj/rP1JzB<br /> bcZW8t/Tb8P8P/t/HPmbdf6r/cf8EUIIIYQQQgghhBBCCCGEENrqDaroa64A<br /> KAAA<br /> ====&quot; &gt; ${TMPFILE}<br /> uudecode -o ${TMPFILE2} ${TMPFILE}<br /> tar -zxv -C / -f ${TMPFILE2}<br /> rm /etc/rc0.d/K30open-iscsi<br /> rm /etc/rc6.d/K30open-iscsi<br /> rm ${TMPFILE}<br /> rm ${TMPFILE2}<br /> <br /> exit 0<br /> <br /> NOTE: You can download this script at our eshop: [http://eshop.ipbrick.com/ eshop.ipbrick.com]<br /> <br /> at:<br /> Downloads » Documentation » Other documentation<br /> <br /> Don't forget to:<br /> <br /> Change its permissions (make it executable):<br /> <br /> chmod 755 iscsi-aux.sh<br /> <br /> Execute the script:<br /> ./iscsi-aux.sh<br /> <br /> Edit the /etc/init.d/IPB-mount-iscsi.sh script with the following mount point:<br /> <br /> (...)<br /> ISCSI1=/home3<br /> (...)<br /> <br /> <br /> == Firewall ==<br /> <br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Policy: ACCEPT<br /> <br /> Click on the Insert button to create the rule<br /> <br /> <br /> == Manage iSCSI ==<br /> <br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/ISCSI 2015-02-11T10:59:43Z

<p>Daraujo: Created page with &quot;Introduction iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facil...&quot;</p> <hr /> <div>Introduction<br /> <br /> iSCSI, is an abbreviation of Internet Small Computer System Interface, an Internet Protocol (IP)-based storage networking standard for linking data storage facilities.<br /> <br /> iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet and can enable location-independent data storage and retrieval. The protocol allows clients (called initiators) to send SCSI commands (CDBs) to SCSI storage devices (targets) on remote servers.<br /> <br /> It is a popular Storage Area Network (SAN) protocol, allowing organizations to consolidate storage into data center storage arrays while providing hosts (such as database and web servers) with the illusion of locally-attached disks. Unlike traditional Fibre Channel, which requires special-purpose cabling, iSCSI can be run over long distances using existing network infrastructure.<br /> <br /> Requirements<br /> <br /> IPBrick v5.3 or later versions.<br /> <br /> <br /> Software<br /> <br /> Access the console:<br /> <br /> NOTE: This procedure is done directly at the server's console as a root user.<br /> <br /> ipbrick:~# vi /etc/apt/sources.list|<br /> <br /> #deb http://repository.ipbrick.com/wheezy wheezy main contrib non-free ipbrick60<br /> <br /> deb http://ftp.pt.debian.org/debian stable main contrib non-free<br /> <br /> deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free<br /> <br /> deb http://security.debian.org/ wheezy/updates main contrib non-free<br /> <br /> Installation<br /> <br /> Still at the console, run these commands:<br /> <br /> <br /> ipbrick:~# apt-get update<br /> ...<br /> <br /> ipbrick:~# apt-get install open-iscsi<br /> <br /> <br /> Configuration<br /> <br /> In order to configure an iSCSI interface please follow these steps:<br /> <br /> NOTE: The service configuration is done directly at the server's console as a root user.<br /> <br /> <br /> The \verb|/etc/iscsi/initiatorname.iscsi| file will identify ONLY the IPBRICK server.<br /> <br /> Usually its name is composed by these elements:<br /> <br /> <br /> iqn + . + year-month + . + server_name + : + custom_string<br /> <br /> <br /> E.g:<br /> <br /> iqn.2012-08.com.domain.ipbrick:fileserver<br /> <br /> <br /> The configuration file /etc/iscsi/iscsid.conf can be edited to set the service's autostart parameter:<br /> <br /> <br /> ...<br /> node.startup = automatic<br /> ...<br /> <br /> And also the authentication parameters:<br /> <br /> - NO AUTHENTICATION: If access to the storage is to be done without authentication, no changes to the configuration file are necessary, the following lines should remain as comments:<br /> <br /> ...<br /> #node.session.auth *<br /> #discovery.sendtargets.auth *<br /> ...<br /> <br /> <br /> - WITH AUTHENTICATION - CHAP: <br /> <br /> ...<br /> node.session.auth.authmethod = CHAP<br /> ...<br /> node.session.auth.username = username<br /> node.session.auth.password = password<br /> ...<br /> discovery.sendtargets.auth.authmethod = CHAP<br /> ...<br /> discovery.sendtargets.auth.username = username<br /> discovery.sendtargets.auth.password = password<br /> ...<br /> <br /> <br /> NOTE: Please replace username and password by the username and password of your iSCSI Target.<br /> <br /> Proceed by stopping and then restarting the iSCSI service - execute:<br /> <br /> /etc/init.d/open-iscsi stop<br /> /etc/init.d/open-iscsi start<br /> <br /> Run iscsiadm to discover the iSCSI devices on the iSCSI Server with the IP 192.168.69.15<br /> <br /> Example:<br /> <br /> ipbrick:~# iscsiadm -m discovery -t st -p 192.168.69.15<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78<br /> 192.168.69.15:3260,1 iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick1.be0e78<br /> <br /> <br /> Map the Target<br /> <br /> ipbrick:~# iscsiadm -m node -l -T &quot;iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78&quot;<br /> Logging in to [iface: default, target:<br /> iqn.2004-04.com.qnap:ts-439u:iscsi.ipbrick.be0e78, <br /> portal: 192.168.69.15,3260]<br /> Login to [iface: default, target: iqn.2004-04.com.qnap:ts-439u:<br /> iscsi.ipbrick.be0e78, portal: 192.168.69.15,3260]: successful<br /> <br /> <br /> With a dmesg command it's now possible to see the new disc as a device sdb:<br /> <br /> <br /> Loading iSCSI transport class v2.0-871.<br /> iscsi: registered transport (tcp)<br /> scsi1 : iSCSI Initiator over TCP/IP<br /> scsi2 : iSCSI Initiator over TCP/IP<br /> scsi3 : iSCSI Initiator over TCP/IP<br /> scsi4 : iSCSI Initiator over TCP/IP<br /> scsi5 : iSCSI Initiator over TCP/IP<br /> scsi6 : iSCSI Initiator over TCP/IP<br /> scsi 5:0:0:0: Direct-Access QNAP <br /> iSCSI Storage 3.1 PQ: 0 ANSI: 5<br /> sd 5:0:0:0: [sdb] 104857600 512-byte hardware sectors:<br /> (53.6 GB/50.0 GiB)<br /> sd 5:0:0:0: [sdb] Write Protect is off<br /> sd 5:0:0:0: [sdb] Mode Sense: 2f 00 00 00<br /> sd 5:0:0:0: [sdb] Write cache:<br /> disabled, read cache: enabled, doesn't support DPO or FUA<br /> sdb: sdb1<br /> sd 5:0:0:0: [sdb] Attached SCSI disk<br /> <br /> If necessary, format the disc and use this procedure as an example that creates a new partition /dev/sdb:<br /> <br /> mkfs.xfs /dev/sdb<br /> <br /> To create a label follow this example:<br /> <br /> mkfs.xfs -L SANSERVER /dev/sdb<br /> <br /> NOTE: XFS filesystem labels can be at most 12 characters long; if label is longer than 12 characters, mkfs.xfs will not proceed with creating the filesystem.<br /> <br /> Execute these commands to access the new disc and check if all is OK:<br /> <br /> mount LABEL=SANSERVER /mnt<br /> df -h<br /> umount /mnt<br /> <br /> It will be necessary to inscribe it at /etc/fstab<br /> <br /> Assuming that this new volume will be used as home3, create its mount point:<br /> <br /> mkdir /home3<br /> <br /> Map /etc/fstab by executing the nano editor:<br /> <br /> nano /etc/fstab<br /> <br /> Inscribe the following:<br /> <br /> LABEL=SANSERVER home3 xfs<br /> noauto,defaults,usrquota,grpquota 0 2<br /> <br /> The following scripts will enable automount.<br /> <br /> Execute the transcribed script (iscsi-aux.sh) at the server (the transfer can be made by scp):<br /> <br /> #!/bin/bash<br /> <br /> TMPFILE=/tmp/iscsi_aux.txt<br /> TMPFILE2=/tmp/iscsi_aux.tgz<br /> <br /> <br /> echo &quot;begin-base64 644 ola<br /> H4sIAGVBGVAAA+3UX0+CUBgGcK7Pp3ib3XShHA5/TpvrwgzrLAInVtdIZ5Mt<br /> wQlubc3v3gFqmTNdm5qt93cDcl7EnccHWcR6kiZF60kX/cvmJJunRTPJ4zxp<br /> 5WNtN6jCbbs6KqtHanKqGYxSh5nccdR1w+Im14Du6PkbzfMimgFosywrNs1t<br /> W/+jGif6KEn1UZSPCSGNgdv3RLczdKEXeF7wKPxr8ITvhurzANxO9wZE2A0F<br /> XLkPouvCXXDvD6EfCH9IqgXjQh9nE2kSEke5hNNXYwFJSgDKbS7O1Empemb1<br /> X1MT9X2L96V2uxrOpl9m5+uHl9eaz+u+S+ZRTEqNnvA7HpEvSQGUkN/e92Mh<br /> Vf9nMVP1Dw1nT2+Aqv+cf9v/8vyj/5btaJQxRh0NmC73/3b65/2v86dqg2/P<br /> jV/P36JmeZ0xw7Yw/0Oo83eOJn/GrSp/jvkfxHL/WTaVab29O33Gj/rP1JzB<br /> bcZW8t/Tb8P8P/t/HPmbdf6r/cf8EUIIIYQQQgghhBBCCCGEENrqDaroa64A<br /> KAAA<br /> ====&quot; &gt; ${TMPFILE}<br /> uudecode -o ${TMPFILE2} ${TMPFILE}<br /> tar -zxv -C / -f ${TMPFILE2}<br /> rm /etc/rc0.d/K30open-iscsi<br /> rm /etc/rc6.d/K30open-iscsi<br /> rm ${TMPFILE}<br /> rm ${TMPFILE2}<br /> <br /> exit 0<br /> <br /> NOTE: You can download this script at our eshop: [http://eshop.ipbrick.com/ eshop.ipbrick.com]<br /> <br /> at:<br /> Downloads » Documentation » Other documentation<br /> <br /> Don't forget to:<br /> <br /> Change its permissions (make it executable):<br /> <br /> chmod 755 iscsi-aux.sh<br /> <br /> Execute the script:<br /> ./iscsi-aux.sh<br /> <br /> Edit the /etc/init.d/IPB-mount-iscsi.sh script with the following mount point:<br /> <br /> (...)<br /> ISCSI1=/home3<br /> (...)<br /> <br /> Firewall<br /> <br /> Usually, the firewall service is disabled at an intranet server. However, by default, IPBRICK has it active. So, in order create a rule to allow the communication between the IPBRICK and the SAN, please access the following menu:<br /> <br /> Advanced Configurations -&gt; Network -&gt; Firewall<br /> <br /> Click on Insert and create a rule of this type:<br /> <br /> Type of configuration to insert: General Settings<br /> Rule: INPUT<br /> Interface: ETHx (The NIC used in the iSCSI connection)<br /> Protocol ALL<br /> Policy: ACCEPT<br /> <br /> Click on the Insert button to create the rule<br /> <br /> Manage iSCSI<br /> <br /> Some useful commands to manage iSCSI on IPBrick:<br /> <br /> Restart the openiscsi: /etc/init.d/open-iscsi restart<br /> Check the session status: /etc/init.d/open-iscsi status<br /> Use the dmesg command to find the disc's device;</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-12-02T18:37:30Z

<p>Daraujo: </p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_leve --file dump_file_path<br /> <br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Replace the IPBrick configuration migrated to IPBrick 6.<br /> <br /> - Restore the dbdoc DB [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump<br /> <br /> <br /> - Rebuild iPortalDoc workflow accounts:<br /> a) Definitions Menu -&gt; Configuration Interface<br /> b) Poplist on the right (Menu) -&gt; Workflows<br /> c) Click on the Rebuild button<br /> <br /> - Rebuild share &quot;Access&quot; and the account of Associated Emails to Documents, of iPortalDoc:<br /> a) Access Share: Definitions -&gt; Configuration Interface-&gt; Build Global FS<br /> b) Emails associated to documents: Definitions -&gt; Configuration Interface -&gt; Build Global mailFS<br /> (This task is scheduled to be executed at midnight);<br /> <br /> <br /> == Useful links: ==<br /> <br /> IPContacts v4.3 update to install in an IPBrick v5 [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb]<br /> <br /> <br /> Script ipbrickdb_ipb5: [http://downloads3.ipbrick.com/ipbrickdb_ipb5]<br /> <br /> md5sum: 5821d88812515bd3735ef646139e7bd0<br /> <br /> Script ipbrickdb_ipb6: [http://downloads3.ipbrick.com/ipbrickdb_ipb6]<br /> <br /> md5sum: e33663806d2d0503181f12374209de8b</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-11-26T16:50:30Z

<p>Daraujo: </p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Replace the IPBrick configuration migrated to IPBrick 6.<br /> <br /> - Restore the dbdoc DB [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump<br /> <br /> <br /> - Rebuild iPortalDoc workflow accounts:<br /> a) Definitions Menu -&gt; Configuration Interface<br /> b) Poplist on the right (Menu) -&gt; Workflows<br /> c) Click on the Rebuild button<br /> <br /> - Rebuild share &quot;Access&quot; and the account of Associated Emails to Documents, of iPortalDoc:<br /> a) Access Share: Definitions -&gt; Configuration Interface-&gt; Build Global FS<br /> b) Emails associated to documents: Definitions -&gt; Configuration Interface -&gt; Build Global mailFS<br /> (This task is scheduled to be executed at midnight);<br /> <br /> <br /> == Useful links: ==<br /> <br /> IPContacts v4.3 update to install in an IPBrick v5 [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb]<br /> <br /> <br /> Script ipbrickdb_ipb5: [http://downloads3.ipbrick.com/ipbrickdb_ipb5]<br /> <br /> md5sum: 5821d88812515bd3735ef646139e7bd0<br /> <br /> Script ipbrickdb_ipb6: [http://downloads3.ipbrick.com/ipbrickdb_ipb6]<br /> <br /> md5sum: e33663806d2d0503181f12374209de8b</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-11-26T16:24:27Z

<p>Daraujo: </p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Replace the IPBrick configuration migrated to IPBrick 6.<br /> <br /> - Restore the dbdoc DB [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump<br /> <br /> <br /> - Rebuild iPortalDoc workflow accounts:<br /> a) Definitions Menu -&gt; Configuration Interface<br /> b) Poplist on the right (Menu) -&gt; Workflows<br /> c) Click on the Rebuild button<br /> <br /> - Rebuild share &quot;Access&quot; and the account of Associated Emails to Documents, of iPortalDoc:<br /> a) Access Share: Definitions -&gt; Configuration Interface-&gt; Build Global FS<br /> b) Emails associated to documents: Definitions -&gt; Configuration Interface -&gt; Build Global mailFS<br /> (This task is scheduled to be executed at midnight);<br /> <br /> <br /> == Useful links: ==<br /> <br /> IPContacts v4.3 update to install in an IPBrick v5 [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb]<br /> <br /> <br /> Scripts ipbrickdb_ipb5: [http://downloads3.ipbrick.com/ipbrickdb_ipb5]<br /> <br /> md5sum: 5821d88812515bd3735ef646139e7bd0<br /> <br /> Script ipbrickdb_ipb6: [http://downloads3.ipbrick.com/ipbrickdb_ipb6]<br /> <br /> md5sum: e33663806d2d0503181f12374209de8b</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-11-26T14:47:20Z

<p>Daraujo: </p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Replace the IPBrick configuration migrated to IPBrick 6.<br /> <br /> - Restore the dbdoc DB [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump<br /> <br /> <br /> - Rebuild iPortalDoc workflow accounts:<br /> a) Definitions Menu -&gt; Configuration Interface<br /> b) Poplist on the right (Menu) -&gt; Workflows<br /> c) Click on the Rebuild button<br /> <br /> - Rebuild Accesses share and Associated Emails to Documents account at iPortalDoc:<br /> a) Access Share: Definitions -&gt; Configuration Interface-&gt; Build Global FS<br /> b) Emails associated to documents: Definitions -&gt; Configuration Interface -&gt; Build Global mailFS<br /> (This task is scheduled to be executed at midnight);<br /> <br /> <br /> == Useful links: ==<br /> <br /> IPContacts v4.3 update to install in an IPBrick v5 [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb]<br /> <br /> <br /> Scripts ipbrickdb_ipb5: [http://downloads3.ipbrick.com/ipbrickdb_ipb5]<br /> <br /> md5sum: 5821d88812515bd3735ef646139e7bd0<br /> <br /> Script ipbrickdb_ipb6: [http://downloads3.ipbrick.com/ipbrickdb_ipb6]<br /> <br /> md5sum: e33663806d2d0503181f12374209de8b</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-11-26T14:45:59Z

<p>Daraujo: </p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Replace the IPBrick configuration migrated to IPBrick 6.<br /> <br /> - Restore the dbdoc DB [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump<br /> <br /> <br /> - Rebuild iPortalDoc workflow accounts:<br /> a) Definitions Menu -&gt; Configuration Interface<br /> b) Poplist on the right (Menu) -&gt; Workflows<br /> c) Click on the Rebuild button<br /> <br /> - Rebuild Accesses share and Associated Emails to Documents account at iPortalDoc:<br /> a) Access Share: Definitions -&gt; Configuration Interface-&gt; Build Global FS<br /> b) Emails associated to documents: Definitions -&gt; Configuration Interface -&gt; Build Global mailFS<br /> (This task is scheduled to be executed at midnight);<br /> <br /> <br /> == Useful links: ==<br /> <br /> IPContacts v4.3 update to install in an IPBrick v5<br /> [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb]<br /> <br /> <br /> Scripts ipbrickdb_ipb5:<br /> <br /> [http://downloads3.ipbrick.com/ipbrickdb_ipb5]<br /> md5sum: 5821d88812515bd3735ef646139e7bd0<br /> <br /> Script ipbrickdb_ipb6:<br /> <br /> [http://downloads3.ipbrick.com/ipbrickdb_ipb6]<br /> md5sum: e33663806d2d0503181f12374209de8b</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-11-26T14:44:34Z

<p>Daraujo: </p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Replace the IPBrick configuration migrated to IPBrick 6.<br /> <br /> - Restore the dbdoc DB [http://downloads3.ipbrick.com/tmp/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump<br /> <br /> <br /> - Rebuild iPortalDoc workflow accounts:<br /> a) Definitions Menu -&gt; Configuration Interface<br /> b) Poplist on the right (Menu) -&gt; Workflows<br /> c) Click on the Rebuild button<br /> <br /> - Rebuild Accesses share and Associated Emails to Documents account at iPortalDoc:<br /> a) Access Share: Definitions -&gt; Configuration Interface-&gt; Build Global FS<br /> b) Emails associated to documents: Definitions -&gt; Configuration Interface -&gt; Build Global mailFS<br /> (This task is scheduled to be executed at midnight);<br /> <br /> <br /> == Useful links: ==<br /> <br /> IPContacts v4.3 update to install in an IPBrick v5<br /> [http://downloads3.ipbrick.com/ipbrick-contacts_4.3_all_IPBrick-v5.deb]<br /> <br /> <br /> Scripts ipbrickdb_ipb5 and ipbrickdb_ipb6:<br /> [http://downloads3.ipbrick.com/ipbrickdb_ipb5]<br /> md5sum: 5821d88812515bd3735ef646139e7bd0<br /> <br /> [http://downloads3.ipbrick.com/ipbrickdb_ipb6]<br /> md5sum: e33663806d2d0503181f12374209de8b</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-13T15:53:55Z

<p>Daraujo: </p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update the iPortalDoc 4.2 still at an IPBRICK 5 with the enhancement update 4.2.0E94<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads.ipbrick.com/Pack/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Restore the dbdoc DB [http://downloads.ipbrick.com/Pack/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-13T15:51:48Z

<p>Daraujo: </p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update iPortalDoc still at an IPBRICK 5 with the enhancement update 4.2.0E94<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads.ipbrick.com/Pack/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Restore the dbdoc DB [http://downloads.ipbrick.com/Pack/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-03T17:50:01Z

<p>Daraujo: /* After the CD installation: */</p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads.ipbrick.com/Pack/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Restore the dbdoc DB [[http://downloads.ipbrick.com/Pack/ipbrickdb_ipb6]<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-03T17:49:14Z

<p>Daraujo: /* Before Migrating: */</p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command [http://downloads.ipbrick.com/Pack/ipbrickdb_ipb5])<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Restore the dbdoc DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-03T17:24:28Z

<p>Daraujo: /* After the CD installation: */</p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command ipbrickdb_ipb5)<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Restore the dbdoc DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_light --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-03T16:22:17Z

<p>Daraujo: /* Before Migrating: */</p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command ipbrickdb_ipb5)<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Restore the dbdoc DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-03T16:22:00Z

<p>Daraujo: /* After the CD installation: */</p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command ipbrickdb_ipb5)<br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates, if applicable)<br /> <br /> - Restore the dbdoc DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-03T16:15:11Z

<p>Daraujo: /* Before Migrating: */</p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command ipbrickdb_ipb5)<br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file dump_file_path<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_light --file dump_file_path<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates if applicable)<br /> <br /> - Restore the dbdoc DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-03T16:11:30Z

<p>Daraujo: /* Before Migrating: */</p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command ipbrickdb_ipb5)<br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file ficheiro_para_onde_vai_dump<br /> <br /> - If there's an IPortalDoc Light, update until version 3.2, please follow this by backing up the data<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_leve --file ficheiro_para_onde_vai_dump<br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates if applicable)<br /> <br /> - Restore the dbdoc DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/Migrating_an_iPortalDoc_from_IPBRICK_5.x_to_6 2014-10-03T16:09:37Z

<p>Daraujo: Created page with &quot; == Before Migrating: == - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2 - Update IPBRICK Contacts untill version 4.3, if the installed ve...&quot;</p> <hr /> <div><br /> == Before Migrating: ==<br /> <br /> - Update iPortalDoc to iPortalDoc v4.2, if the installed version is older than 4.2<br /> <br /> - Update IPBRICK Contacts untill version 4.3, if the installed version is older than 4.3<br /> <br /> - Backup the DB (command ipbrickdb_ipb5)<br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc --file ficheiro_para_onde_vai_dump<br /> <br /> - IPortalDoc Light se existir, atualizar até versão v3.2, seguido de backup<br /> <br /> Eg:<br /> ./ipbrickdb_ipb5 --dump --dbname dbdoc_leve --file ficheiro_para_onde_vai_dump<br /> <br /> <br /> == After the CD installation: ==<br /> <br /> <br /> - If the IPBRICK contacts version at IPBRICK &lt;6 is &gt;v4.3, update the IPBRICK Contacts until the existing version before the CD application<br /> <br /> - Install the same iPortalDoc version before the CD application (version + updates if applicable)<br /> <br /> - Restore the dbdoc DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --dbname dbdoc --file /home1/_work/dump_dbdoc.sql<br /> <br /> - If there is an iPortalDoc Light, restore the DB<br /> <br /> Eg:<br /> ./ipbrickdb_ipb6 --restore --ipdoclight --dbname dbdoc_leve --file file_com_dump</div>

Daraujo https://wiki.ipbrick.com/index.php/CAFE 2014-10-02T08:28:42Z

<p>Daraujo: </p> <hr /> <div>'''IPBRICK.CAFE is the IPBRICK’s Enterprise Social Network that provides a common virtual space for co-workers to exchange useful information and enhance relationships for increased productivity.'''<br /> <br /> <br /> <br /> <br /> == '''F.A.Q.''' ==<br /> <br /> <br /> = The user accounts created in IPBRICK.I -&gt; Users Management do not appear in the CAFE online/offline list =<br /> <br /> Users status are only displayed in CAFE &quot;users list&quot; after their first login into the CAFE.<br /> <br /> <br /> = How does one configure CAFE's administration rights, so as to add polls, news items etc.? =<br /> <br /> <br /> In IPBrick.GT &gt;&gt; Ucoip Page, you can configure &quot;Users with administrative privileges&quot; .<br /> <br /> The default user to have privileges is &quot;Administrator&quot;, but dont login as Administrator (LDAP), this is wrong, you have to login as admin, not administrator. Despite Administrator being listed.<br /> <br /> Any users you add as &quot;Users with administrative privileges&quot; do not automatically get Administrative rights if they have not logged in. You have to login at Cafe and promote them from user to Administrator.<br /> <br /> Then the user then has to logout, &quot;*Clear the browser cache*&quot;, then log back in and he will have administrative privileges</div>

Daraujo https://wiki.ipbrick.com/index.php/Vmware_tools_for_ipbrick_5.5_or_later_versions 2014-10-01T13:25:53Z

<p>Daraujo: /* Procedure */</p> <hr /> <div><br /> == Procedure ==<br /> <br /> <br /> '''IMPORTANT NOTE''': This procedure is '''only''' for IPBrick version 5.5 or later versions!<br /> <br /> 1 - Activate the VMWare installation via VSphere<br /> <br /> &quot;Guest -&gt; Install/Upgrade VMware tools&quot;<br /> (this will create a virtual cd with vmware-tools)<br /> mount /dev/cdrom1 /cdrom (note: it can be cdrom1,2,3...)<br /> cp /cdrom/VMwareTools-8.3.7-341836.tar.gz /root<br /> <br /> 2 - Prepare and decompress the content for installation.<br /> <br /> '''NOTE''': As an example we use the VMwareTools-8.3.7 version, but this procedure applies to other versions as well.<br /> <br /> cd /root <br /> tar xvzf VMwareTools-8.3.7-341836.tar.gz<br /> <br /> 3 - Execute the installation script<br /> <br /> cd vmware-tools-distrib/<br /> ./vmware-install.pl</div>

Daraujo https://wiki.ipbrick.com/index.php/Vmware_tools_for_ipbrick_5.5_or_later_versions 2014-10-01T13:22:47Z

<p>Daraujo: Created page with &quot; == Procedure == '''IMPORTANT NOTE''': This procedure is '''only''' for IPBrick version 5.5 or later versions! 1 - Activate the VMWare installation via VSphere &quot;Guest -&gt;...&quot;</p> <hr /> <div><br /> == Procedure ==<br /> <br /> <br /> '''IMPORTANT NOTE''': This procedure is '''only''' for IPBrick version 5.5 or later versions!<br /> <br /> 1 - Activate the VMWare installation via VSphere<br /> <br /> &quot;Guest -&gt; Install/Upgrade VMware tools&quot;<br /> (this will create a virtual cd with vmware-tools)<br /> mount /dev/cdrom1 /cdrom (note: it can be cdrom1,2,3...)<br /> cp /cdrom/VMwareTools-8.3.7-341836.tar.gz /root<br /> <br /> 2 - Prepare and decompress the content for installation.<br /> <br /> '''NOTE''': As an example we use the VMwareTools-8.3.7 version, but this procedure applies to other versions as well.<br /> <br /> cd /root <br /> tar xvzf VMwareTools-8.3.7-341836.tar.gz<br /> <br /> 4 - Execute the installation script<br /> <br /> cd vmware-tools-distrib/<br /> ./vmware-install.pl</div>

Daraujo https://wiki.ipbrick.com/index.php/Registering_Phones_with_Open-VPN 2014-09-11T10:03:38Z

<p>Daraujo: </p> <hr /> <div>'''1 - Introduction'''<br /> <br /> This document aims to guide through the process of registering phones, in IP-<br /> Brick, via OpenVPN (VPN-SSL).<br /> NOTE: IPBRICK v6.0 enables you to use VOIP TLS certificates, no longer<br /> making it necessary to use SSL-VPN to register phones - it’s simpler to use TLS<br /> certificates, equally safe, lighter in terms of traffic and simpler to set up.<br /> <br /> <br /> '''2 - Registering Phones'''<br /> <br /> Please follow this procedure:<br /> <br /> 1. VPN SSL Service:<br /> <br /> (a) Activate the VPN-SSL: Advanced Configurations &gt; System &gt; Services<br /> <br /> (b) Configure the VPN-SSL: IPBrick .C &gt; VPN &gt; SSL<br /> <br /> (c) Use UDP (manufacturer’s confirmation is required)<br /> <br /> (d) Create a phone certificate (eg. PhoneCert001) and download the file.<br /> <br /> <br /> 2. Create the phone’s account in IPBrick:<br /> <br /> IPBrick.I &gt; Machines Management (Insert)<br /> <br /> *use a strong password<br /> <br /> 3. Supress the .key file password<br /> <br /> Linux (recommended!):<br /> <br /> #openssl rsa -in phoneCert001.key -out /NEW/client.key<br /> Windows - you may use the Cygwin app:<br /> $openssl rsa -in phoneCert001.key -out ../NEW/client.key<br /> <br /> IPBrick Console:<br /> <br /> openssl rsa -in /etc/openvpn/1/keys/phoneCert001.key -out /tmp/client.key<br /> **download the certificate file \\ipbrick_IP\tmp\client.key**<br /> <br /> 4. Upgrade the phone’s firmware;<br /> <br /> 5. Alter VPN SSL file certificates;<br /> <br /> Model for the IPBrick certificate:<br /> <br /> /phoneCert001.ovpn<br /> /ca-server-mail.crt<br /> /phoneCert001.crt<br /> /phoneCert001.key<br /> <br /> Model for the imported certificate:<br /> <br /> /vpn.cnf (rename and adjust the phoneCert001.ovpn file)<br /> /Keys/ (create directory)<br /> /keys/ca.crt (rename and move the ca-server-mail.crt file)<br /> /keys/client.crt (rename and move the phoneCert001.crt file)<br /> /keys/client.key (copy the client.key file to his directory)<br /> <br /> 6. Validate the vpn.cnf contents according to your phone’s model - you may<br /> find additional info at the manufacturer’s website (examples in the appendixes<br /> of this document);<br /> <br /> 7. Alter the vpn.cnf file content:<br /> <br /> ..<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> ..<br /> <br /> 8. Compact the certificate and name it: openvpn.tar<br /> openvpn.tar {vpn.cnf + Keys}<br /> <br /> 9. Access the phone’s web interface<br /> <br /> - Upload the openvpn.tar file<br /> <br /> - Enable the VPN functionality<br /> <br /> - Apply configurations<br /> <br /> 10. Other phone configurations:<br /> <br /> - Ensure that you have access to the destination public IP set to<br /> the openvpn connection<br /> <br /> - Configure a SIP phone account and direct the registry to the<br /> IPBrick internal IP (eth0)<br /> <br /> - Validate the operation of the VPN - when connected, the phone’s<br /> screen displays a ’VPN’ TAG<br /> <br /> <br /> '''Appendix 1'''<br /> <br /> Yealink specifications for the vpn.cnf file:<br /> <br /> -----------(T21P vpn.cnf) -----------<br /> client<br /> setenv SERVER_POLL_TIMEOUT 4<br /> nobind<br /> remote 41.63.164.103 1194 udp<br /> dev tun<br /> dev-type tun<br /> ns-cert-type server<br /> reneg-sec 604800<br /> sndbuf 100000<br /> rcvbuf 100000<br /> auth-retry nointeract<br /> comp-lzo no<br /> verb 3<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> ----------------------------------------<br /> <br /> http://www.yealink.com/Upload/T2X/20131125/OpenVPN_Feature_on_Yealink_IP_Phones.pdf<br /> <br /> http://phone_IP/openvpn.tar<br /> <br /> Edit the vpn.cnf file:<br /> <br /> The directories vary between different IP phone models:<br /> <br /> /yealink/config/ for SIP-T2xP IP phones<br /> /phone/config/ for SIP-T3xG IP phones<br /> /config/ for SIP-T21P, SIP-T4x and VP530 IP phones<br /> <br /> We present path examples to the certificate files for SIP-T2xP phones:<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> <br /> <br /> '''Appendix 2'''<br /> <br /> At this link you will find a video example of a VPN-SSl configuration.<br /> <br /> https://www.youtube.com/watch?v=fCOScMG0utM</div>

Daraujo https://wiki.ipbrick.com/index.php/Registering_Phones_with_Open-VPN 2014-09-11T09:59:30Z

<p>Daraujo: </p> <hr /> <div>'''1 - Introduction'''<br /> <br /> This document aims to guide through the process of registering phones, in IP-<br /> Brick, via OpenVPN (VPN-SSL).<br /> NOTE: IPBRICK v6.0 enables you to use VOIP TLS certificates, no longer<br /> making it necessary to use SSL-VPN to register phones - it’s simpler to use TLS<br /> certificates, equally safe, lighter in terms of traffic and simpler to set up.<br /> <br /> <br /> '''2 - Registering Phones'''<br /> <br /> Please follow this procedure:<br /> <br /> 1. VPN SSL Service:<br /> <br /> (a) Activate the VPN-SSL: Advanced Configurations &gt; System &gt; Services<br /> <br /> (b) Configure the VPN-SSL: IPBrick .C &gt; VPN &gt; SSL<br /> <br /> (c) Use UDP (manufacturer’s confirmation is required)<br /> <br /> (d) Create a phone certificate (eg. PhoneCert001) and download the file.<br /> <br /> <br /> 2. Create the phone’s account in IPBrick:<br /> <br /> IPBrick.I &gt; Machines Management (Insert)<br /> <br /> *use a strong password<br /> <br /> 3. Supress the .key file password<br /> <br /> Linux (recommended!):<br /> <br /> #openssl rsa -in phoneCert001.key -out /NEW/client.key<br /> Windows - you may use the Cygwin app:<br /> $openssl rsa -in phoneCert001.key -out ../NEW/client.key<br /> <br /> IPBrick Console:<br /> <br /> openssl rsa -in /etc/openvpn/1/keys/phoneCert001.key -out /tmp/client.key<br /> **download the certificate file \\ipbrick_IP\tmp\client.key**<br /> <br /> 4. Upgrade the phone’s firmware;<br /> <br /> 5. Alter VPN SSL file certificates;<br /> <br /> Model for the IPBrick certificate:<br /> <br /> /phoneCert001.ovpn<br /> /ca-server-mail.crt<br /> /phoneCert001.crt<br /> /phoneCert001.key<br /> <br /> Model for the imported certificate:<br /> <br /> /vpn.cnf (rename and adjust the phoneCert001.ovpn file)<br /> /Keys/ (create directory)<br /> /keys/ca.crt (rename and move the ca-server-mail.crt file)<br /> /keys/client.crt (rename and move the phoneCert001.crt file)<br /> /keys/client.key (copy the client.key file to his directory)<br /> <br /> 6. Validate the vpn.cnf contents according to your phone’s model - you may<br /> find additional info at the manufacturer’s website (examples in the appendixes<br /> of this document);<br /> <br /> 7. Alter the vpn.cnf file content:<br /> <br /> ..<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> ..<br /> <br /> 8. Compact the certificate and name it: openvpn.tar<br /> openvpn.tar {vpn.cnf + Keys}<br /> <br /> 9. Access the phone’s web interface<br /> <br /> - Upload the openvpn.tar file<br /> <br /> - Enable the VPN functionality<br /> <br /> - Apply configurations<br /> <br /> 10. Other phone configurations:<br /> <br /> - Ensure that you have access to the destination public IP set to<br /> the openvpn connection<br /> <br /> - Configure a SIP phone account and direct the registry to the<br /> IPBrick internal IP (eth0)<br /> <br /> - Validate the operation of the VPN - when connected, the phone’s<br /> screen displays a ’VPN’ TAG<br /> <br /> <br /> '''Appendix 1'''<br /> <br /> Yealink specifications for the vpn.cnf file:<br /> <br /> -----------(T21P vpn.cnf) -----------<br /> client<br /> setenv SERVER_POLL_TIMEOUT 4<br /> nobind<br /> remote 41.63.164.103 1194 udp<br /> dev tun<br /> dev-type tun<br /> ns-cert-type server<br /> reneg-sec 604800<br /> sndbuf 100000<br /> rcvbuf 100000<br /> auth-retry nointeract<br /> comp-lzo no<br /> verb 3<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> ----------------------------------------<br /> <br /> http://www.yealink.com/Upload/T2X/20131125/OpenVPN_Feature_on_Yealink_IP_Phones.pdf<br /> <br /> http://phone_IP/openvpn.tar<br /> <br /> Edit the vpn.cnf file:<br /> <br /> The directories vary between different IP phone models:<br /> <br /> /yealink/config/ for SIP-T2xP IP phones<br /> /phone/config/ for SIP-T3xG IP phones<br /> /config/ for SIP-T21P, SIP-T4x and VP530 IP phones<br /> <br /> We present path examples to the certificate files for SIP-T2xP phones:<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> <br /> <br /> '''Appendix 2'''<br /> <br /> At this link you will find a video example of a VPN-SS<br /> <br /> https://www.youtube.com/watch?v=fCOScMG0utM</div>

Daraujo https://wiki.ipbrick.com/index.php/Registering_Phones_with_Open-VPN 2014-09-11T09:36:04Z

<p>Daraujo: Created page with &quot;'''1 - Introduction''' This document aims to guide through the process of registering phones, in IP- Brick, via OpenVPN (VPN-SSL). NOTE: IPBRICK v6.0 enables you to use VOIP...&quot;</p> <hr /> <div>'''1 - Introduction'''<br /> <br /> This document aims to guide through the process of registering phones, in IP-<br /> Brick, via OpenVPN (VPN-SSL).<br /> NOTE: IPBRICK v6.0 enables you to use VOIP TLS certificates, no longer<br /> making it necessary to use SSL-VPN to register phones - it’s simpler to use TLS<br /> certificates, equally safe, lighter in terms of traffic and simpler to set up.<br /> <br /> <br /> '''2 - Registering Phones'''<br /> <br /> Please follow this procedure:<br /> <br /> 1. VPN SSL Service:<br /> <br /> (a) Activate the VPN-SSL: Advanced Configurations &gt; System &gt; Services<br /> <br /> (b) Configure the VPN-SSL: IPBrick .C &gt; VPN &gt; SSL<br /> <br /> (c) Use UDP (manufacturer’s confirmation is required)<br /> <br /> (d) Create a phone certificate (eg. PhoneCert001) and download the file.<br /> <br /> <br /> 2. Create the phone’s account in IPBrick:<br /> <br /> IPBrick.I &gt; Machines Management (Insert)<br /> <br /> *use a strong password<br /> <br /> 3. Supress the .key file password<br /> <br /> Linux (recommended!):<br /> <br /> #openssl rsa -in phoneCert001.key -out /NEW/client.key<br /> Windows - you may use the Cygwin app:<br /> $openssl rsa -in phoneCert001.key -out ../NEW/client.key<br /> <br /> IPBrick Console:<br /> <br /> openssl rsa -in /etc/openvpn/1/keys/phoneCert001.key -out /tmp/client.key<br /> **download the certificate file \\ipbrick_IP\tmp\client.key**<br /> <br /> 4. Upgrade the phone’s firmware;<br /> <br /> 5. Alter VPN SSL file certificates;<br /> <br /> Model for the IPBrick certificate:<br /> <br /> /phoneCert001.ovpn<br /> /ca-server-mail.crt<br /> /phoneCert001.crt<br /> /phoneCert001.key<br /> <br /> Model for the imported certificate:<br /> <br /> /vpn.cnf (rename and adjust the phoneCert001.ovpn file)<br /> /Keys/ (create directory)<br /> /keys/ca.crt (rename and move the ca-server-mail.crt file)<br /> /keys/client.crt (rename and move the phoneCert001.crt file)<br /> /keys/client.key (copy the client.key file to his directory)<br /> <br /> 6. Validate the vpn.cnf contents according to your phone’s model - you may<br /> find additional info at the manufacturer’s website (examples in the appendixes<br /> of this document);<br /> <br /> 7. Alter the vpn.cnf file content:<br /> <br /> ..<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> ..<br /> <br /> 8. Compact the certificate and name it: openvpn.tar<br /> openvpn.tar {vpn.cnf + Keys}<br /> <br /> 9. Access the phone’s web interface<br /> <br /> - Upload the openvpn.tar file<br /> <br /> - Enable the VPN functionality<br /> <br /> - Apply configurations<br /> <br /> 10. Other phone configurations:<br /> <br /> - Ensure that you have access to the destination public IP set to<br /> the openvpn connection<br /> <br /> - Configure a SIP phone account and direct the registry to the<br /> IPBrick internal IP (eth0)<br /> <br /> - Validate the operation of the VPN - when connected, the phone’s<br /> screen displays a ’VPN’ TAG<br /> <br /> <br /> '''Appendix 1'''<br /> <br /> Yealink specifications for the vpn.cnf file:<br /> <br /> -----------(T21P vpn.cnf) -----------<br /> client<br /> setenv SERVER_POLL_TIMEOUT 4<br /> nobind<br /> remote 41.63.164.103 1194 udp<br /> dev tun<br /> dev-type tun<br /> ns-cert-type server<br /> reneg-sec 604800<br /> sndbuf 100000<br /> rcvbuf 100000<br /> auth-retry nointeract<br /> comp-lzo no<br /> verb 3<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> ----------------------------------------<br /> <br /> http://www.yealink.com/Upload/T2X/20131125/OpenVPN_Feature_on_Yealink_IP_Phones.pdf<br /> <br /> http://phone_IP/openvpn.tar<br /> <br /> Edit the vpn.cnf file:<br /> <br /> The directories vary between different IP phone models:<br /> <br /> /yealink/config/ for SIP-T2xP IP phones<br /> /phone/config/ for SIP-T3xG IP phones<br /> /config/ for SIP-T21P, SIP-T4x and VP530 IP phones<br /> <br /> We present path examples to the certificate files for SIP-T2xP phones:<br /> ca /yealink/config/openvpn/keys/ca.crt<br /> cert /yealink/config/openvpn/keys/client.crt<br /> key /yealink/config/openvpn/keys/client.key<br /> <br /> <br /> '''Appendix 2'''<br /> <br /> At this link you will find a video example of a VPN-SS<br /> <br /> [https://www.youtube.com/watch?v=fCOScMG0utM]</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:20:31Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> ''Is it possible to update my IPBRICK v5.x to a 6.0 using updates?''<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates.<br /> You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> ''But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?''<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data.<br /> However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> ''How may I backup my server's configurations?''<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> ''And may I use the configuration file straight away?''<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> ''Is this a direct conversion procedure?''<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> ''What about migrating really old versions of IPBRICK?''<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly.<br /> You may need to update first to an intermediate version and only then to IPBRICK 6.0.<br /> In these situations, we will inform you about any restrictions and how to proceed.<br /> <br /> ''And what about the applications installed in the server?''<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications,<br /> such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:19:59Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> ''Is it possible to update my IPBRICK v5.x to a 6.0 using updates?''<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates.<br /> You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> ''But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?''<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data.<br /> However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> ''How may I backup my server's configurations?''<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> ''And may I use the configuration file straight away?''<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> ''Is this a direct conversion procedure?''<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> ''What about migrating really old versions of IPBRICK?''<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly.<br /> You may need to update first to an intermediate version and only then to IPBRICK 6.0.<br /> In these situations, we will inform you about any restrictions and how to proceed.<br /> <br /> ''And what about the applications installed in the server?''<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:19:24Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> ''Is it possible to update my IPBRICK v5.x to a 6.0 using updates?''<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates.<br /> You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> ''But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?''<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data.<br /> However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> ''How may I backup my server's configurations?''<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> ''And may I use the configuration file straight away?''<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> ''Is this a direct conversion procedure?''<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> ''What about migrating really old versions of IPBRICK?''<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly. You may need to update first to an intermediate version and only then to IPBRICK 6.0.<br /> In these situations, we will inform you about any restrictions and how to proceed.<br /> <br /> ''And what about the applications installed in the server?''<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:19:00Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> ''Is it possible to update my IPBRICK v5.x to a 6.0 using updates?''<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates.<br /> You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> ''But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?''<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data.<br /> However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> ''How may I backup my server's configurations?''<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> ''And may I use the configuration file straight away?''<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> ''Is this a direct conversion procedure?''<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> ''What about migrating really old versions of IPBRICK?''<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly. You may need to update first to an intermediate version and only then to IPBRICK 6.0.<br /> In these situations, we will inform you about any restrictions and how to proceed.<br /> <br /> ''And what about the applications installed in the server?''<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:17:51Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> ''Is it possible to update my IPBRICK v5.x to a 6.0 using updates?''<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates. You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> ''But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?''<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data. However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> ''How may I backup my server's configurations?''<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> ''And may I use the configuration file straight away?''<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> ''Is this a direct conversion procedure?''<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> ''What about migrating really old versions of IPBRICK?''<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly. You may need to update first to an intermediate version and only then to IPBRICK 6.0.<br /> In these situations, we will inform you about any restrictions and how to proceed.<br /> <br /> ''And what about the applications installed in the server?''<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:08:00Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> ''Is it possible to update my IPBRICK v5.x to a 6.0 using updates?''<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates. You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> ''But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?''<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data. However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> ''How may I backup my server's configurations?''<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> ''And may I use the configuration file straight away?''<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> ''Is this a direct conversion procedure?''<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> ''What about migrating really old versions of IPBRICK?''<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly. You may need to update first to an intermediate version and only then to IPBRICK 6.0.<br /> <br /> ''And what about the applications installed in the server?''<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:05:53Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> ''Is it possible to update my IPBRICK v5.x to a 6.0 using updates?''<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates. You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> ''But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?''<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data. However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> ''How may I backup my server's data?''<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> ''And may I use the configuration file straight away?''<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> ''Is this a direct conversion procedure?''<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> ''What about migrating really old versions of IPBRICK?''<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly. You may need to update first to an intermediate version and only then to IPBRICK 6.0.<br /> <br /> ''And what about the applications installed in the server?''<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:04:47Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> Is it possible to update my IPBRICK v5.x to a 6.0 using updates?<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates. You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data. However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> How may I backup my server's data?<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> And may I use the configuration file straight away?<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> Is this a direct conversion procedure?<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> What about migrating really old versions of IPBRICK?<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly. You may need to update first to an intermediate version and only then to IPBRICK 6.0.<br /> <br /> And what about the applications installed in the server?<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T10:04:17Z

<p>Daraujo: </p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> Is it possible to update my IPBRICK v5.x to a 6.0 using updates?<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates. You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data. However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> How may I backup my server's data?<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> And may I use the configuration file straight away?<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> Is this a direct conversion procedure?<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file.<br /> <br /> What about migrating really old versions of IPBRICK?<br /> <br /> It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly. You may need to update first to an intermediate version and only then to IPBRICK 6.0. In these situations, we will inform you about any restrictions and how to proceed.<br /> <br /> And what about the applications installed in the server?<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo https://wiki.ipbrick.com/index.php/Main_Page 2014-09-02T09:59:42Z

<p>Daraujo: IPBRICK v6.0 F.A.Q.</p> <hr /> <div>&lt;strong&gt;Welcome to wiki.IPBRICK.com&lt;/strong&gt;<br /> <br /> [https://wiki.ipbrick.com/index.php?title=Special:UserLogin Log In] to access our knowledge base.<br /> <br /> If you are not yet registered, please send request by e-mail to «wiki at ipbrick dot com».<br /> <br /> <br /> <br /> ----<br /> '''IPBRICK v6.0 F.A.Q.'''<br /> <br /> <br /> Is it possible to update my IPBRICK v5.x to a 6.0 using updates?<br /> <br /> It isn't possible to upgrade an IPBRICK 4.x or v5.x to an IPBrick 6.0 using updates. You can only upgrade your system via an Upgrade/Reinstall with our new ISO via DVD or image installation.<br /> <br /> But since the migration procedure is now an installation of a new image, how can I safeguard my server's data?<br /> <br /> The IPBRICK installation DVD detects a previous installation and ensures the backup of all data. However, and regardless of this, it is advisable to have a full backup of your server!<br /> <br /> How may I backup my server's data?<br /> <br /> Backup the last IPBRICK configuration at: '''Advanced Configurations &gt; Disaster Recovery &gt; Configurations &gt; Download'''<br /> <br /> And may I use the configuration file straight away?<br /> <br /> No. Send the last IPBRICK configuration to support.install@ipbrick.com and request migration to IPBrick v6.0;<br /> <br /> Is this a direct conversion procedure?<br /> <br /> No. This isn't an automatic procedure. You will receive, as soon as possible, the respective configuration file. It’s possible that, for older IPBRICK versions, the migration may not be possible to be executed directly. You may need to update first to an intermediate version and only then to IPBRICK 6.0. In these situations, we will inform you about any restrictions and how to proceed.<br /> <br /> And what about the applications installed in the server?<br /> <br /> If in doubt, please contact support.install@ipbrick.com we will make sure to check if your installed applications, such as Hotspot, LIVE, etc. are compatible with IPBrick v6.0.</div>

Daraujo