AIX 6.1's iSCSI-initiator works with IETd target [SOLVED]
At the risk of looking spammy, here my final remark on this subject: I've successfully ran 'mkvg' on an iSCSI disk, exported from an RHEL5
machine running IET (http://iscsitarget.sourceforge.net/).
Thanks to everyone that helped me fix this really _really_ annoying
issue!
--edit--
Useful to add that (or at least so I think) is that the odious 'devices.iscsi.array' warning by cfgmgr no longer appears since using IET.
hey programmers!
1-why won't gcc accept as an argument? i tried the recommendations on the man page of getch(),..etc. nothing worked.
2-why it won't see <iostream> && <fstream> even if i implemented the function as follow
std::cout<<"..etc"<<endl;
3-after i type this code in it gives... (6 Replies)
I'm trying to figure out why this if statement won't work:
if || $zipcount != 6 ]]
then
echo ${myline}
echo "ZIPCODE WARNING! ${zipcode} ${zipcount}"
fi
if ]]
then
echo ${myline}
echo "STATE WARNING!... (3 Replies)
Hi All,
can anybody tell me what's wrong with this code?
# SEARCH replaced by REPLACE
#!/bin/bash
SEARCH="95$$ 0 t"
REPLACE="95$$ 1 t"
for I in `ls *000.inp | cut -c-12`;
do
echo $I
sed 's/$SEARCH/$REPLACE/' ${I}-000.inp > ${I}-100.inp
done
It don't replace the string... (5 Replies)
I typed:
echo "echo hi > at_log.txt" | at now +1minute
to test the at command on my terminal. I got the message:
job 8 at Thu Feb 25 18:42:00 2010
I waited for a minute but nothing happened. I tried listing at_log.txt, but it said there was no such file. Am I doing something... (2 Replies)
I just installed a fork of opensolaris, and I really like it.
I would hate going back to Ubuntu, But one issue, I cannot get my Dell Wireless 1450 Wireless USB Adapter working.
On Ubuntu 10.4 I just installed nonfree firmware, but I guess it doesn't work that way on Solaris, any help would be... (5 Replies)
Hi,
I have a very frustrating issue! I hope you guys can assist
When a disk is presented out the iSCSI target display a lower disk capacity
SOLARIS VERSION is SOLARIS 10 05/09 Kernel Patch 139555-31
ISCSI Patch 119090-31, 141878-11
Unix Commands To discover Target
bash-3.00# i... (0 Replies)
Hi! I'm sure that somebody here installed freeBSD from a download of a virtual disc (.iso). But I made 5 downloads of 5 differents freeBSD installation (and no one has worked).Can somebody tell me where to download and how (if needed) to prepare the cd? (8 Replies)
Hello,
Images won't work on UNIX when I try posting them on my website I'm working on. It doesn't show the image, and it's simply erroring.
Help! Thanks! (5 Replies)
Previous forum threads have noted that AIX cannot use iSCSI disks because it fails when trying to add them to a volume group using mkvg. The failure is caused by AIX's use of the SCSI "WRITE AND VERIFY"(0x2e) command which some iSCSI targets do not support.
We experienced the same problem using... (1 Reply)
Hi all,
Is there anyway i can control the naming of the disk device ?
I have added an iscsi disk on server1 using iscsiadm , devfsadm and it is now showing as
/dev/dsk/c2t0d0 in node1
However, i am worried that the same disk will appear as
/dev/dsk/cXtXd0 in node2
This iscsi disk(lun)... (0 Replies)
Discussion started by: javanoob
0 Replies
LEARN ABOUT FREEBSD
iscontrol
ISCONTROL(8) BSD System Manager's Manual ISCONTROL(8)NAME
iscontrol -- login/negotiator/control for an iSCSI initiator session
SYNOPSIS
iscontrol [-dv] [-c file [-n nickname]] [-p pidfile] [-t target] [variable=value]
DESCRIPTION
This command, along with its kernel counterpart iscsi_initiator(4), is obsolete. Users are advised to use iscsictl(8) instead.
Internet SCSI (iSCSI) is a network protocol standard, that allows the use of the SCSI protocol over TCP/IP networks, the iscontrol program is
the userland side of an iSCSI session, see iscsi_initiator(4). It has 2 modes of operation, if -d (discovery session) is specified, it will
print out the target names returned by the target and exit. In the second mode, it will, after a successful login/negotiation, run in daemon
mode, monitoring the connection, and will try to reconnect in case of a network/target failure. It will terminate/logout the session when a
SIGHUP signal is received. The flags are as follows:
-c file a file containing configuration key-options, see iscsi.conf(5).
-d do a discovery session and exit.
-n nickname if -c file is specified, then search for the block named nickname in that file, see iscsi.conf(5).
-p pidfile will write the process ID of the session to the specified pidfile
-t target the target's IP address or name.
-v verbose mode.
variable=value see iscsi.conf(5) for the complete list of variables/options and their possible values.
EXAMPLES
iscontrol -dt myiscsitarget
will start a discovery session with the target and print to stdout the list of available targetnames/targetadresses. Note: this listing does
not necessarily mean availability, since depending on the target configuration, a discovery session might not need login/access permission,
but a full session certainly does.
iscontrol -c /etc/iscsi.conf -n myiscsi
will read options from /etc/iscsi.conf, use the targetaddress found in the block nicknamed myiscsi, login and negotiate whatever options are
specified, and start an iscsi-session.
SEE ALSO da(4), iscsi_initiator(4), sa(4), iscsi.conf(5), camcontrol(8), iscsictl(8)STANDARDS
RFC 3720
BUGS
iscontrol should probably load the iscsi_initiator module if needed.
Not all functions/specifications have been implemented yet, noticeably missing are the Task Management Functions. The error recovery, though
not fully compliant does a brave effort to recover from network disconnects.
BSD October 9, 2014 BSD