10 More Discussions You Might Find Interesting
1. Solaris
Hello. I'm a noob, but have managed to get to the point of Solaris storage server running 4 X 3Tb in a RAIDZ pool. My current system is sharing via SMB a few different ZFS devices (puddle/TV, puddle/Movies, puddle/Music, etc).
My main server is going to be OSX, Mountain Lion. What I have set... (4 Replies)
Discussion started by: BillyPrefect
4 Replies
2. AIX
Hi,
I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name.
Please share me the steps to complete this requirements.
Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies
3. Red Hat
Hello Friends,
I am facing issue with the iSCSI configuration on some of our RHEL 5 servers,
When I restart the iSCSI service, it triggers the RHEL server reboot.
Could you please help me with this issue.
Below are the system details :
uname -a :
Linux za-rac-prd-01.abc.local... (2 Replies)
Discussion started by: Jeevanm
2 Replies
4. Linux
I am using Windows Server 2008R2 as a domain controller to 2 other servers and would like to use my Dell Powervault 770N as my NAS for data storage. I have FC that I would like to implement between the servers and the NAS (as an iSCSI target). I am brand new to this world; is this possible? I am... (2 Replies)
Discussion started by: NoviceAdmin
2 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I want to set up a iscsi high availability with sheepdog distributed storage.
Here is my system set up. Four nodes with sheepdog distributed storage and i am sharing this storage through iscsi using two nodes as well as using a virtual ip set up using ucarp.Two nodes using same iqn. And... (0 Replies)
Discussion started by: jobycxa
0 Replies
6. AIX
I have an Equallogic SAN that I connect to from AIX (as well as Windows)
I had configured the connection and created the volumes and filesystems and all was working great.
Then one day, no communication between the SAN and the AIX (I can ping though) Anything I do on the AIX box at this time... (2 Replies)
Discussion started by: oldmanjoe
2 Replies
7. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
8. Linux
Hi guys, I'd like to share experiences and knowledge about what should I use to install on a new storage server (with a lot of disks) in my network. What I want, is to move all domU's storage to this new storage server with AoE, iscsi or another thing. question:
1. Should I install openfiler or... (1 Reply)
Discussion started by: iga3725
1 Replies
9. AIX
Hi,
I have an iSCSI LUN of 200GB. I increased it to 250GB and when I try to increase the size of the vg, I'm getting an error that none of the volumes have increased in size.
How can I get the OS to see the additional 50GB?
---------- Post updated at 03:22 PM ---------- Previous update... (9 Replies)
Discussion started by: bbbngowc
9 Replies
10. AIX
I just reloaded an IBM P-Series with AIX 5.3 and would like to configure iscsi, can someone point me in the right direction to obtaining the initiator node name?
I ran lsattr -El iscsi0 - but the name that is displayed is not the correct name. I read somewhere the default node name is not... (2 Replies)
Discussion started by: bbbngowc
2 Replies
CTLD(8) BSD System Manager's Manual CTLD(8)
NAME
ctld -- CAM Target Layer / iSCSI target daemon
SYNOPSIS
ctld [-d] [-f config-file]
DESCRIPTION
The ctld daemon is responsible for managing the CAM Target Layer configuration, accepting incoming iSCSI connections, performing authentica-
tion and passing connections to the kernel part of the native iSCSI target.
Upon startup, the ctld daemon parses the configuration file and exits, if it encounters any errors. Then it compares the configuration with
the kernel list of LUNs managed by previously running ctld instances, removes LUNs no longer existing in the configuration file, and creates
new LUNs as necessary. After that it listens for the incoming iSCSI connections, performs authentication, and, if successful, passes the
connections to the kernel part of CTL iSCSI target, which handles it from that point.
When it receives a SIGHUP signal, the ctld reloads its configuration and applies the changes to the kernel. Changes are applied in a way
that avoids unnecessary disruptions; for example removing one LUN does not affect other LUNs.
When exiting gracefully, the ctld daemon removes LUNs it managed and forcibly disconnects all the clients. Otherwise - for example, when
killed with SIGKILL - LUNs stay configured and clients remain connected.
To perform administrative actions that apply to already connected sessions, such as forcing termination, use ctladm(8).
The following options are available:
-f config-file
Specifies the name of the configuration file. The default is /etc/ctl.conf.
-d Debug mode. The server sends verbose debug output to standard error, and does not put itself in the background. The server will
also not fork and will exit after processing one connection. This option is only intended for debugging the target.
FILES
/etc/ctl.conf The configuration file for ctld. The file format and configuration options are described in ctl.conf(5).
/var/run/ctld.pid The default location of the ctld PID file.
EXIT STATUS
The ctld utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
ctl(4), ctl.conf(5), ctladm(8)
HISTORY
The ctld command appeared in FreeBSD 10.0.
AUTHORS
The ctld was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation.
BSD
November 9, 2014 BSD