09-19-2015
A little research reveals that Oracle (Sun) partner with COMSTAR for the iSCSI connectivity and this page from 2013 says that (at that time) scsi3 PGR was not supported.
How to Configure ISCSI target in Solaris 11 ? - UnixArena
However, there are also a number of comments on the web saying that COMSTAR were about to implement PGR in an update so this is probably available now. Perhaps you might try to download it.
This User Gave Thanks to hicksd8 For This Post:
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello agian !
What is the difference between SCSI and IDE hard disks ?
I have Intel PC and when i check i have Generic IDE TYPE DISK0
is IDE hard disk is ok for Solrais ? or should i buy the SCSI hard disk ?
Thanks
Abid Malik (3 Replies)
Discussion started by: abidmalik
3 Replies
2. AIX
Hi
Is it possible to install in p5 and pSeries SCSI Disks from SUN on DELL? Will they work?
Regards,
Pit (0 Replies)
Discussion started by: piooooter
0 Replies
3. Solaris
First time writer....take it easy on me.
I had a situation where I lost all paths to EMC disk. There was a failure on the EMC frame. After that was repaired, my server had a difficult time reclaiming all disks and veritas had marked the disks as failed. Veritas was confused. What are some of... (3 Replies)
Discussion started by: Sowser
3 Replies
4. Linux
Hi,
I am installing perl and rsnapshot on the OS of a Western Digital MyBook disk.
To install perl the ./Configure command tells me that both 'tr' and 'split' are missing. I don't find them on the net.
Where can I download them?
Thanks.
Charles. (2 Replies)
Discussion started by: mosndup
2 Replies
5. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
6. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
7. Solaris
Hi All,
I am a RH Linux admin that recently started working at a company with a number of SUN Servers so it's been an interesting transition.
Considering the last person left with very little documentation left behind so I have been picking up most issues half complete, or troubleshot.
... (7 Replies)
Discussion started by: MobileGSP
7 Replies
8. HP-UX
Hi guys,
I need some help to better understand how to determine if a disk have persistent SCSI reservation. I know that we should use the "Persisten Reservation Utility" but we are not allowed to run that tool. Since we have the output from some grab utility and specifically we have the... (0 Replies)
Discussion started by: cecco16
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