similar to: iscsi-tools

This add an iscsi initiator name setup option to the main menu in ovirt-config-setup and can also be accessed via ovirt-config-iscsi. Also accepts AUTO setup by running ovirt-config-iscsi AUTO and generates a random name as before --- Makefile.am | 1 + ovirt-node.spec.in | 3 ++ scripts/ovirt-config-boot | 4 --- scripts/ovirt-config-iscsi | 56

I just updated one of my virtual hosts to 5.6 and on rebooted I spotted an error about iscsi. Which surprised me, since I don't use iscsi. Yet there it is... % rpm -qf /etc/init.d/iscsi iscsi-initiator-utils-6.2.0.872-6.el5 And they're configured to start iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off iscsid 0:off 1:off 2:off 3:on 4:on

I apologize if this has been covered before. I have not seen a blow-by-blow installation guide for Ubuntu onto an iSCSI target. The install guides I have seen assume that you can make a target visible to all, which is a problem if you want multiple iSCSI installations on the same COMSTAR target. During install Ubuntu generates three random initiators and you have to deal with them to get things

CentOS Errata and Bugfix Advisory 2016:1284 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1284.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8e44f277f695473fd93e4e46f507973bb20c14a3d690493b9d006969831f5a5b iscsi-initiator-utils-6.2.0.873-33.el7_2.1.i686.rpm

CentOS Errata and Bugfix Advisory 2016:1530 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1530.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 684e67a738b7dce51fd91736f404ec13e2816f48d8474478ac10336b93c03a0e iscsi-initiator-utils-6.2.0.873-33.el7_2.2.i686.rpm

Hello all. We recently purchased HP Proliant DL380 G7 server and also a HP Lefthand P4500 G2 24TB iSCSI box. The server itself has Quad Ethernet based on the BCM5709 Chipset from Broadcom (NetXtreme II). My main question is about iSCSI offload mechanism, as iSCSI itself is pretty new to me but I have gotten a good hold on it tho. I have managed to setup and configured our Lefthand box into

CentOS Errata and Bugfix Advisory 2016:1999 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1999.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 99e4b99cf132eac84807aea4eaaa2fb498b390a138ec89bc6a6342e3ae55546b iscsi-initiator-utils-6.2.0.873-22.el6_8.i686.rpm

CentOS Errata and Bugfix Advisory 2017:1725 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1725.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bb20f5019d41d5a7e53b75e8955288aa082ec9c50f924e762ccbe8a96623154b iscsi-initiator-utils-6.2.0.873-27.el6_9.i686.rpm

Hi list, I had setup my xen box with bond in active-backup mode. I had install open-iscsi as initiator to attach an external iscsi san to my box but open-iscsi didn''t work. When i run this command: #iscsiadm -m node -T iqn.2008-03.local.foo:iSCSI.test.disk1 -l I retrive, after some seconds, this error Logging in to [iface: iface0, target: iqn.2008-03.local.foo:iSCSI.test.disk1,

CentOS Errata and Bugfix Advisory 2013:0438 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0438.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8127ade8d17da59c23de745f65003917fcada41924f969c43969804ae4896e5c iscsi-initiator-utils-6.2.0.873-2.el6.i686.rpm

Hi, I could not find any option to set iSCSI initiator iqn while using guestfish, although the underlying qemu command has this option. It appears that each time guestfish tries to connect to iSCSI LUN, a randomly generated initiator iqn is being used. This is preventing guestfish to connect to the iSCSI target in our environment as the target allows incoming connection based on the preconfigured

I am confused, because I would have expected a 1-to-1 mapping, if you create an iscsi target on some system, you would have to specify which LUN it connects to. But that is not the case... I read the man pages for sbdadm, stmfadm, itadm, and iscsiadm. I read some online examples, where you first "sbdadm create-lu" which gives you a GUID for a specific device in the system, and then

Thu Jul 7 14:47:23 UTC 2016, m.roth at 5-cent.us wrote: > Hi, folks, > > I installed the iscsi packages, and I *thought* that the first thing to > do was configure /etc/tgt/target.conf. Am I wrong? Did I have to > configure iSNS on the RAID appliance? One thing to make sure you have straight is Target vs. Initiator [2], for me it originally felt like the names were backwards.

I''m posting here as this seems to be a zfs issue. We also have an open ticket with Sun support and I''ve heard another large sun customer also is reporting this as an issue. Basic Problem: Create a zfs file system and set shareiscsi to on. On a vmware esx server discover that iscsi target. It shows up as 249 luns. When attempting to then add the storage esx server eventually

Hello, I?m using ZFS to export some iscsi targets for the virtual box iscsi initiator. It works ok if I try to install the guest OS manually. However, I?d like to be able to import my already prepared guest os vdi images into the iscsi devices but I can?t figure out how to do it. Each time I tried, I cannot boot. It only works if I save the manually installed guest os and re-instate the same

I''ve recently upgraded my x4500 to Nevada build 97, and am having problems with the iscsi target. Background: this box is used to serve NFS underlying a VMware ESX environment (zfs filesystem-type datasets) and presents iSCSI targets (zfs zvol datasets) for a Windows host and to act as zoneroots for Solaris 10 hosts. For optimal random-read performance, I''ve configured a single

Hi List, I've started looking into iSCSI, and I'm wondering if there is an iSCSI target (I've found the initiator in iscsi-initiator-utils) that ships with CentOS, or if not, what the recommended target would be. I'd like to export either a partition or (preferably) a file-as-a-partition. Yours, -S -- Simen Thoresen, Wulfkit Support, Dolphin ICS

Hi, We are experiencing problems with the iscsi configuration. The /etc/iscsi/initiatorname.iscsi is randomly generated during the node build (%{_libexecdir}/ovirt-config-iscsi in ovirt-node.spec), that makes all nodes have the same "random" initiator file. The iscsi server doesn't like that very much, it believes that come from the same node (-> sessions killed,

Hi, I want to take snapshots of a iSCSI devices from a target that hasn't snapshot/cloning capabilities (it's a Infortrend A16E storage array). What method are you using to make snapshots/clones of iSCSI targets using Open-iSCSI + CentOS? What about using Open-iSCSI + LVM snapshots system? For example: - Take a LVM snapshot in the initiator with "lvcreate". - Give read-only

Paul, > While testing iscsi targets exported from thumpers via 10GbE and > imported 10GbE on T2000s I am not seeing the throughput I expect, > and more importantly there is a tremendous amount of read IO > happending on a purely sequential write workload. (Note all systems > have Sun 10GbE cards and are running Nevada b65.) The read IO activity you are seeing is a direct