07-12-2016
ISCSI poor performance 1.5MB/s fresh install AIX7.1
Hi Everyone,
I have been struggling for few days with iSCSI and thought I could get some help on the forum...
fresh install of AIX7.1 TL4 on Power 710, The rootvg relies on 3 SAS disks in RAID 0, 32GB Memory
The lpar Profile is using all of the managed system's resources.
I have connected only 1 physical gigabit ports on the AIX box to my iscsi target server (RHEL6 with tgt iscsi)
The network seems ok, a ftp transfer between AIX & RHEL6 is 125Mb/s
However the iSCSI transfer has really poor performance : if I do a "dd if=/dev/hdisk1 of=/dev/null" from my AIX box (on the iscsi lun), I only get 1.5Mb/s !
(Please note that initially, I wanted to setup one LPAR as iscsi target, and one lpar as iscsi initiator, both using virtual ethernet adapter, and I got the same performance 1.5Mb/s between the 2 AIX lpar ... Then I decided to investigate further and to setup the whole system as a iSCSI initiator and using one of my RHEL6 iscsi target that I know works well.)
I also tried to setup the AIX as iSCSI target and the RHEL6 as initiator, the performance gets better 8MB/s but still not acceptable, I would at least expect 30-40MB/s
Any idea guys ? please solve my 1 week headache.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi you all, I have a BIG performance problem on an Sun E3500, the scenario is described below:
I have several users (30) accessing via samba to the E3500 using an application built on Visual Foxpro from their Windows PC , the problem is that the first guy that logs in demands 30% of the E3500... (2 Replies)
Discussion started by: alex blanco
2 Replies
2. Filesystems, Disks and Memory
Hello,
i have a a1000 connected to an e6500. There's a raid 10 (12 disks) on the a1000.
If i do a
dd if=/dev/zero of=/mnt/1 bs=1024k count=1000
and then look at iostat it tells me there's a kw/s of 25000.
But if i do a
dd of=/dev/zero if=/mnt/1 bs=1024k count=1000
then i see only a... (1 Reply)
Discussion started by: mbrenner
1 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I'm running a script on AIX to process lines in a file. I need to enclose the second column in quotation marks and write each line to a new file. I've come up with the following:
#!/bin/ksh
filename=$1
exec >> $filename.new
cat $filename | while read LINE
do
echo $LINE | awk... (2 Replies)
Discussion started by: scooter53080
2 Replies
4. UNIX for Advanced & Expert Users
Hello all
We just built a storage cluster for our new xenserver farm. Using 3ware 9650SE raid controllers with 8 x 1TB WD sata disks in a raid 5, 256KB stripe size.
While making first performance test on the local storage server using dd (which simulates the read/write access to the disk... (1 Reply)
Discussion started by: roli8200
1 Replies
5. Solaris
Hello,
we have a machine with Solaris Express 11, 2 LSI 9211 8i SAS 2 controllers (multipath to disks), multiport backplane, 16 Seagate Cheetah 15K RPM disks.
Each disk has a sequential performance of 220/230 MB/s and in fact if I do a
dd if=/dev/zero of=/dev/rdsk/<diskID_1> bs=1024k... (1 Reply)
Discussion started by: golemico
1 Replies
6. Solaris
Hello guys,
I have two servers performing the same disk operations. I believe one server is having a disk's impending failure however I have no hard evidence to prove it. This is a pair of Netra 210's with 2 drives in a hardware raid mirror (LSI raid controller). While performing intensive... (4 Replies)
Discussion started by: s ladd
4 Replies
7. AIX
Hi,
I am new registered user here in this UNIX forums.
I am a new system administrator for AIX 6.1. One of our servers performs poorly every time our application (FINACLE) runs many processes/instances. (see below for topas snapshot)
I use NMON or Topas to monitor the server utilization. I... (9 Replies)
Discussion started by: guzzelle
9 Replies
8. Solaris
Hi
We have an M3000 single physical processor and 8gb of memory running Solaris 10. This system runs two Oracle Databases one on Oracle 9i and One on Oracle 10g.
As soon as the Oracle 10g database starts we see an immediate drop in system performance, for example opening an ssh session can... (6 Replies)
Discussion started by: gregsih
6 Replies
9. Windows & DOS: Issues & Discussions
Just a quick note for macOS users.
I just installed (and removed) Parallels Desktop 15 Edition on my MacPro (2013) with 64GB memory and 12-cores, which is running the latest version of macOS Catalina as of this post. The reason for this install was to test some RIGOL test gear software which... (6 Replies)
Discussion started by: Neo
6 Replies
LEARN ABOUT NETBSD
iscsi-initiator
ISCSI-INITIATOR(8) BSD System Manager's Manual ISCSI-INITIATOR(8)
NAME
iscsi-initiator -- refuse-based iSCSI initiator
SYNOPSIS
iscsi-initiator [-46bcDfVv] [-a authentication-type] [-d digest-type] [-h target-hostname] [-p target-port-number] [-t target-number]
[-u username] mount_point
DESCRIPTION
The iscsi-initiator utility can be used to access an iSCSI target, such as iscsi-target(8), to access block storage which has been exported.
Information pertaining to the target is displayed underneath the mount point, along with the device corresponding to the storage which the
target exports.
The various arguments are as follows:
-4 Use an IPv4 connection to the target.
-6 Use an IPv6 connection to the target.
-a authentication-type
Use the specified authentication type when communicating with the target. The possible values are chap, kerberos, srp or none. The
default value is none.
-b Show the storage as a block device.
-c Show the storage as a character device.
-d digest-type
Use the specified digest type when communicating with the target. The possible values are header, data, both, all or none. The
default value is none.
-D List the LUNs on the specified target and exit (i.e. do discovery only)
-f Show the storage as a regular file.
-h hostname
Connect to the iSCSI target running on the host specified as the argument.
-p port-number
Connect to the iSCSI target running on the port specified as the argument. The default value is 3260.
-t target
Connect to the number of the iSCSI target running as the argument.
-u username
Use the specified user's credentials when logging in to the iSCSI target. There is no default.
-V Print out the version number and then exit.
-v Be verbose in operation.
The refuse(3) library is used to provide the file system features.
The mandatory parameter is the local mount point.
This iSCSI initiator presents a view of the targets underneath the mount point. Firstly, it creates a directory tree with the hostname of
the target, and, in that directory, a virtual directory is created for each target name exported by the iSCSI target program. Within that
virtual target directory, symbolic links exist for the hostname (for convenience), a textual representation of the IP address, the iSCSI tar-
get product name, the iSCSI target IQN, the iSCSI target vendor and version number. One other directory entry is presented in the virtual
target directory, relating to the storage presented by the iSCSI target. This can be in the form of a regular file, which is also the
default, a block device or a character device.
Please note that the iscsi-initiator utility needs the ``puffs'' kernel module loaded via modload(8) to operate.
EXAMPLES
# ./iscsi-initiator -u agc -h iscsi-target0.alistaircrooks.co.uk /mnt
# ls -al /mnt/target0
total 576
drwxr-xr-x 2 agc agc 512 May 11 22:24 .
drwxr-xr-x 2 agc agc 512 May 11 22:24 ..
lrw-r--r-- 1 agc agc 39 May 11 22:24 hostname -> iscsi-target0.alistaircrooks.co.uk
lrw-r--r-- 1 agc agc 14 May 11 22:24 ip -> 172.16.135.130
lrw-r--r-- 1 agc agc 16 May 11 22:24 product -> NetBSD iSCSI
-rw-r--r-- 1 agc agc 104857600 May 11 22:24 storage
lrw-r--r-- 1 agc agc 43 May 11 22:24 targetname -> iqn.1994-04.org.netbsd.iscsi-target:target0
lrw-r--r-- 1 agc agc 8 May 11 22:24 vendor -> NetBSD
lrw-r--r-- 1 agc agc 4 May 11 22:24 version -> 0
#
SEE ALSO
puffs(3), refuse(3), iscsi-target(8)
HISTORY
The iscsi-initiator utility first appeared in NetBSD 6.0. An earlier version called iscsifs was available in NetBSD 5.0 in source format
only.
AUTHORS
The iscsi-initiator utility was written by Alistair Crooks <agc@NetBSD.org>.
BUGS
iscsi-initiator currently only supports a CHAP challenge length of 16 octets. Other initiators support up to 1024 and thus it is expected
that most targets will also support such lengths. This means that CHAP compatibility with other targets apart from iscsi-target(8) is likely
to be poor. To workaround this, please use authentication type none by not specifying a username with the -u option.
BSD
February 22, 2011 BSD