In our case as we had used iSCSI units to hold the disks we ran a pair of cables from the iSCSI to the server and then on the iSCSI we mapped 3 drives to each of its ethernet interfaces
on 06/09/2009 – Made popular on 06/09/2009
The environment is a CentOS 6.2 server running on a VM host with a HP P2000 iSCSI disk system attached via Ethernet (dedicated iSCSI network). The P2000 has two controllers A & B and 12 drives. Co... [by rarebearnm]
I don't know if I'm missing something but when I'm mounting additional iSCSI volumes to a said server to add additional storage to a server I'm not seeing a way to mount the volume after running a discovery command.
The reasoning I want to be able to do this is that we're running an application that would require downtime everytime we add additional iSCSI volumes to this server.
I'm trying to set up my Ubuntu 12.04 file server as an iSCSI target to use with my VMWare ESXi VM server. I started out by following this tutorial, and other than what I remember from being present while an iSCSI SAN was set up on an ESXi server at work 3 years ago, I don't know much about iSCSI.
I'm evaluating the possibility to use two off the shelf servers to build a cheap iSCSI redundant SAN. The idea is to run linux, pacemaker, and an iSCSI target - something like the SAN Active-Passive on linux-ha-examples.
The same page scares me a little when I read:
During the switchover of the iscsi-target one can detect a gap in the
protocol of write-test.log.
This question is a follow-on from Dedicated NIC or dedicated port for iSCSI?
Excluding the hardware iSCSI initiator point that was made in the accepted answer to the above question, it seems that using separate port(s) on a multi-port NIC for iSCSI is pretty much going to meet the recommendation of using "seperate NICs" for iSCSI traffic.
I'm in the process of planning a small iSCSI installation