similar to: CentOS 4.1 iSCSI support

Hi. Anyone using CentOS 4.2 iscsi-initiator-utils-4.0.3.0-2 in a production setup? I'm planning to do so shortly, and would like to hear about any experiences (good/bad) or recommendations. The target is going to be a Dell AX100i. Br, Morten

I just tried an iSCSI connection to a NetAPP filer. I first tried using CentOS-4.2, but the iscsi initiator would not work. Using the command iscsi-ls would not show anything. Without spending too much time trying to figure out why, I tried from a CentOS-3 box. Connecting from the CentOS-3 box worked without a problem the first time. I will try further to get the CentOS-4 box to connect, but

Microsoft has their "boot" version of their iSCSI software initiator. Apparently this still requires that the network card be iSCSI Boot "enabled." Intel seems to be the only obvious company out there supporting it on their Server adapters - I was wondering if there are any thoughts/plans on implementing iSCSI Boot functionality in the HVM Boot ROM? Or maybe there''s

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 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

Hi everyone! I have 2 hosts + 1 ISCSI device. I want to create a shared storage repository and both hosts use together. I wont use NFS. prepared sr: xe sr-create host-uuid=xxx content-type=user name-label=NAS1 shared=true type=iscsi device-config:target=xxxx device-config:targetIQN=xxxx hosts see the iscsi device: scsi4 : iSCSI Initiator over TCP/IP scsi 4:0:0:0: Direct-Access NAS

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

I am getting the following error on boot on a new install Centos 51: #/bin/sh ro no such file or directory then a kernel panic I have traced it to the call ''switchroot'' in the init script in the initrd. the exact same build without zen has no problems. the boot messages look like: Attaching to iSCSI storage iscsistart: transport class version 2.0-724. iscsid version 2.0-865

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

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''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 there, I have one server acting as a iscsi target running windows storage server r2 sp2 and the other server is running centos as an initiator. They are connected to a switch over a 1Gbit ethernet connection. the target is a Dell NF600 and the server running centos is a Poweredge R900. We want to move this configuration to a FC based installation using a Dell QLE2462 HBA (this is the hba we can

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''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 looking for test users for new iSCSI target software designed for multipath failover cluster nodes. I'm very interested in the virtual machine such as Hyper-V. So I'm also tuning the target for using VMs. I need an environmental report in particular other than FreeBSD 7.1 RELEASE p3 i386/PAE kernel w/ZFS. I welcome the report with other initiators below. If you are

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, i have a debian Etch x86_64 with a xen 3.1 on a kernel 2.6.18-xen. I have some DomU with Debian Etch. I installed open-iscsi, configure /etc/iscsi/iscsid.conf: --- node.active_cnx = 1 node.startup = automatic #node.session.auth.username = dima #node.session.auth.password = aloha node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 10

I have set up an iSCSI ZFS target that seems to connect properly from the Microsoft Windows initiator in that I can see the volume in MMC Disk Management. When I shift over to Mac OS X Tiger with globalSAN iSCSI, I am able to set up the Targets with the target name shown by `iscsitadm list target` and when I actually connect or "Log On" I see that one connection exists on the Solaris

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

Hi all, I have the strangest problem on one of our backup server. iscsi doesn't start at all, and gives the following error: [root at 2U-NAS ~]# /etc/init.d/iscsi status iscsid is stopped [root at 2U-NAS ~]# /etc/init.d/iscsi start iscsid is stopped Starting iSCSI daemon: Unable to create pid file: /var/run/brcm_iscsiuio.pid [FAILED] Setting up iSCSI targets: iscsiadm: No records