12-21-2011
SAN-based LUNs
running Solaris10 with Qlogic FC adapters connected to a multi-host FC array..using VXFS/VXVM..
Is there in Solaris10 or using some Qlogic drivers to filter out only the LUNs this host can see ??
Normally this is done by LUN masking in the FC switch or the FC array itself..however, neither is available on this case.
Currently this host sees LUNs from other servers..??
10 More Discussions You Might Find Interesting
1. Solaris
Hi everyone,
I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN?
At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies
2. HP-UX
Hi, This is my first post and I hope I can present my questions the right way. I am going to be asked to create logical volumes for a Hitachi SAN device on a New HP 11 server. Currently, They are running their data on a EMC (prod server). They are looking to convert the data and filesystems over to... (3 Replies)
Discussion started by: Uni-dev
3 Replies
3. AIX
Hi,
I'd like to share this...
I see all the luns on my aix when I do lspv, 10 of them, configured by the san contractor. I defined the first sanvg no problem, the second one no problem, but the third got problem and so on. It's random after the second, I think. The error is 0516-024 mkvg:... (5 Replies)
Discussion started by: itik
5 Replies
4. HP-UX
salut admin,
Normalement mon serveur doit voir un de mes LDEV à partir de deux chemins sur le SAN et ainsi lui attribuer seulement deux Target LUNs. Or il lui en a attribué 8!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Très bizzare!
Auriez vous une idée.
Merci pour votre aide appréciée (2 Replies)
Discussion started by: hmaiida
2 Replies
5. Solaris
Hi
I would like to remove SAN luns from system and do not want them even after system reboot,
format
Searching for disks...done
df -kh
I know last 4 partitions are from SAN but there could be more.
Can someone please help me correct steps to remove SAN Luns.
vxdisk list
... (2 Replies)
Discussion started by: upengan78
2 Replies
6. Solaris
Is it possible to use zvol from SAN LUN to install LDOM OS ? I 'm using following VDS from my service domain
VDS
NAME LDOM VOLUME DEVICE
primary-vds0 primary iso sol-10-u6-ga1-sparc-dvd.iso
cdrom ... (16 Replies)
Discussion started by: fugitive
16 Replies
7. Solaris
how to create luns plzzzzzz (1 Reply)
Discussion started by: nsusheelgoud
1 Replies
8. AIX
Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage.
DS5020 mentions Enhanced Remote Mirror to multi-LUN applications
I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies
9. Solaris
Hello everyone.
I've been asked to check if something is wrong with the storage setup on these two SunOS 5.10 machines, which are being used as database servers with Oracle RAC configuration. Seems to be that the DB guy is complaining, telling that they are nearly out of space, which sounds... (4 Replies)
Discussion started by: kacareu
4 Replies
10. Filesystems, Disks and Memory
hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB.
i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new... (6 Replies)
Discussion started by: rino19ny
6 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