03-17-2017
Thanks for your reply. I tried the menthod I listed and that didn't work. Turns out, AIX set the paths to each disk, since the disk is going over iSCSI, the disk attributes has the iSCSI target name in the connection so it didn't work.
I'll seek out the EMC connectivity guide and give that a go.
Thanks.
If anyone else has done this, I'd be interested in hearing.
10 More Discussions You Might Find Interesting
1. AIX
Hi everyone,
how can I check if I have LUNs in a server and the LUNīs vpath in AiX?
thx (5 Replies)
Discussion started by: jcpetela
5 Replies
2. AIX
Hello All,
Really hoping someone can help. We have an AIX server connected to a Quantum SDLC sitting in front of an S10K library. The library has 3 logical partitions (two LTO4, one LTO3), so it requires 3 distinct medium changers. The SDLC presents the 3 luns (which are the medium... (1 Reply)
Discussion started by: jwholey
1 Replies
3. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
4. AIX
Hello Everyone,
Can someone help me to mount a SAN hdisk which contains a clone data copy(san) of the remote server to the another machine. Both servers are running in AIX.
Thanks in advance !
Regards,
Gowtham.G (3 Replies)
Discussion started by: gowthamakanthan
3 Replies
5. AIX
Hello!
I have this infraestructure:
- 1 POWER7 with single VIOS on Site A.
- 1 POWER6 with single VIOS on Site B.
- 1 LPAR called NodeA as primary node for PowerHA 6.1 on Site A.
- 1 LPAR called NodeB as secondary (cold) node for PowerHA 6.1 on SiteB.
- 1 Storage DS4700 on Site A.
- 1... (8 Replies)
Discussion started by: enzote
8 Replies
6. Solaris
Hi,
I've noticed that mpathadm states that one of our luns has no active paths:
/dev/rdsk/c6t60000970000298700009533031324333d0s2
Total Path Count: 4
Operational Path Count: 4
/dev/rdsk/c6t60000970000298700009533031333037d0s2
... (3 Replies)
Discussion started by: badoshi
3 Replies
7. AIX
Hello all!
I have not so much experience with AIX
We have test p5 server. On server was deployed VIOS + 3 LPAR + AIX6.1
There is a test HACMP cluster of two nodes, the cluster is identical to production cluster (all clusters and hosts have been configured by specialist of integrator company and... (3 Replies)
Discussion started by: Ravil Khalilov
3 Replies
8. AIX
we have an old AIX system with important data on an EMC LUN. the AIX server crashed and we had to rebuild it with the old AIX os 5.8. how do we reconnect the EMC LUN without losing the data? (15 Replies)
Discussion started by: jhudson12
15 Replies
9. Solaris
Hi
I have a server running solaris 10 in which the NetAppadmin has just presented one LUN of 200Gb, but when running:
bash-3.2# format
Searching for disks...done
c3t500A09828DE3E799d1: configured with capacity of 199.94GB
c3t500A09829DE3E799d1: configured with capacity of 199.94GB
... (5 Replies)
Discussion started by: fretagi
5 Replies
10. Post Here to Contact Site Administrators and Moderators
ssssssssssss (0 Replies)
Discussion started by: sampathenjoy
0 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