oh... also, the "ovm1" server is the dom0. That system is connecting to IETD targets from within the dom0 using iscsi-initiator-utils-6.2.0.871-0.7. There are two ifaces setup to connect to two portal IP's on my CentOS 5.3, aka "storage", system. The result is this:
[r...@ovm1 ~]# iscsiadm -m session tcp: [1] 192.168.30.1:3260,1 iqn.2009-09.com.itec.storage:tgtd tcp: [2] 192.168.30.1:3260,1 iqn.2009-09.com.itec.storage:tgtd tcp: [3] 192.168.30.2:3260,1 iqn.2009-09.com.itec.storage:tgtd tcp: [4] 192.168.30.2:3260,1 iqn.2009-09.com.itec.storage:tgtd In my REAL test and production OVM 2.2 environments, we have 2 ifaces setup to connect to one load balanced Dell EqualLogic group IP, which results in something like this: [r...@oir7102901 log]# iscsiadm -m session | grep lun0 tcp: [2] 192.168.0.19:3260,1 iqn.2001-05.com.equallogic:0-8a0906-781989902-5a9000000114ae5e-ovm-t-lun0 tcp: [5] 192.168.0.19:3260,1 iqn.2001-05.com.equallogic:0-8a0906-781989902-5a9000000114ae5e-ovm-t-lun0 [r...@oir7102901 log]# In our current TEST environment (Dell EqualLogic + Dell powerconnect switch running MTU=9126 + Dell R710 with OVM 2.2 installed) we've had some strange server issues (possible hardware problems. I'm still diagnosing this). However, with regards to iSCSI, I haven't seen any issues and can see (3) dt threads going for my ovm-t-lun0, ovm-t-lun1, and ovm-t-lun2 volumes. The overall throughput is roughly only about 70MB/s TOTAL (that includes metrics from all three of those luns) for reads and writes. The iowait% is my bottleneck at the moment though. And we have not had any "iscsi disconnect" messsages. In our PROD2 environment (Dell m610 blades + Cisco switch modules in the blade chassis-- I believe m1000e-- + Dell powerconnect switch + Dell EqualLogic members) we've had absolutely no issues thus far. The dt tests have the same throughput and have been running for about 8-9 days so far without a single disconnect. On Nov 12, 2009, at 10:15 AM, Hoot, Joseph wrote: > > sorry... wrong information. Here is the correct information. I was doing > some testing in VMWare Fusion VM's for a presentation that I'm giving. The > "storage" server is CentOS 5.3, which dishes out IETD targets for my OVM > servers. The OVM 2.2 environment is as follows: > > [r...@ovm1 ~]# uname -r > 2.6.18-128.2.1.4.9.el5xen > [r...@ovm1 ~]# rpm -qa | grep iscsi > iscsi-initiator-utils-6.2.0.871-0.7.el5 > [r...@ovm1 ~]# > > > > On Nov 10, 2009, at 2:30 PM, Mike Christie wrote: > >> >> Hoot, Joseph wrote: >>> [r...@storage ~]# uname -r >>> 2.6.18-164.el5 >>> [r...@storage ~]# rpm -qa | grep iscsi >>> iscsi-initiator-utils-6.2.0.868-0.18.el5_3.1 >>> [r...@storage ~]# >>> >> >> Weird. >> >> Is 2.6.18-164.el5 the kernel being used in the virtual machine/DonU? Is >> that where you are using iscsi? It looks like the Oracle enterprise >> linux kernel is 2.6.18-164.el5, which looks like it is based on RHEL >> 5.4. The iscsi code in there is the same as RHEL/upstream. No sendwait >> patch. >> >> However, it looks like there is a 2.6.18-128.2.1.4.9 kernel (comes with >> the Oracle VM rpms). In here we have a different iscsi version. It looks >> a little older than what is in 2.6.18-164.el5, but it has the sendwait >> patch I send to dell. Do you use this kernel in the Dom0? Are you using >> this kernel with iscsi? >> >> >> >>> On Nov 10, 2009, at 12:17 PM, Mike Christie wrote: >>> >>>> Hoot, Joseph wrote: >>>>> I've had about 3 threads of dt (kicking off a bit randomly) on (3) >>>>> separate volumes for over a week and haven't had a single disconnect yet. >>>>> I am currently using whatever rpm is distributed with Oracle VM v2.2. >>>>> I know for sure that they have included the 871 base, plus I believe at >>>>> least a one off patch. I can get more details if you'd like. >>>>> >>>>> But so far so good for now >>>>> >>>> I think I have the source they are using. Could you do a uname -r, so I >>>> can see what kernel they are using. >>>> >>> >>> =========================== >>> Joseph R. Hoot >>> Lead System Programmer/Analyst >>> (w) 716-878-4832 >>> (c) 716-759-HOOT >>> joe.h...@itec.suny.edu >>> GPG KEY: 7145F633 >>> =========================== >>> >>> >>>> >> >> >>> > > =========================== > Joseph R. Hoot > Lead System Programmer/Analyst > (w) 716-878-4832 > (c) 716-759-HOOT > joe.h...@itec.suny.edu > GPG KEY: 7145F633 > =========================== > > > > =========================== Joseph R. Hoot Lead System Programmer/Analyst (w) 716-878-4832 (c) 716-759-HOOT joe.h...@itec.suny.edu GPG KEY: 7145F633 =========================== --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~----------~----~----~----~------~----~------~--~---
