04-21-2011
I've done that using zones in the Brocade switch. How can I do it under CAM? Do I need to do it under CAM?
Have you used CAM?
Thanks.
5 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi,
We have 12x1TB SATA disks in our array and I need to create 10TB volume. I defined new storage profile on array and when I tried to add volume, I faced with ~2TB limit for new volumes. I didn't find how to set another limit on my storage profile. Is there is a way to configure one large... (3 Replies)
Discussion started by: Sapfeer
3 Replies
2. Solaris
Hello,
Wondering if anyone can help me with mounting a file share from my Sun T2000 server running Solaris 10 to my connected 2530 disk array?
I believe I've connected the disk array correctly and I have created a volume on the array using the filesystem (Sun_SAM-FS, RAID-5).
The T2000... (15 Replies)
Discussion started by: DundeeDancer
15 Replies
3. Solaris
Hi!
I have Sun StorageTek 2540 FC array and CAM works very slowly - I can wait for software response even more than 2 minutes... I run this software on Windows machine with Firefox Web Browser but speed is terrible... How can I make it works at least a little bit faster?.. (2 Replies)
Discussion started by: Sapfeer
2 Replies
4. Filesystems, Disks and Memory
In Sun manuals, I didn't find how to backup Sun StorageTek Common Array Manager's configuration. Is there a way to do it like backing up Brocade switch configuration? CAM is under Solaris 10.
Thank you in advance! (0 Replies)
Discussion started by: aixlover
0 Replies
5. Solaris
Bought a Sun StorageTek 2540 SAN array a few years ago from a company that was going out of business. When we first set it up, we were able to get all the software (Common Array Manager) and firmware directly from Sun.
We just upgraded the drives, but the array is too large for the firmware. Now... (6 Replies)
Discussion started by: edison303
6 Replies
XPT(4) BSD Kernel Interfaces Manual XPT(4)
NAME
xpt -- CAM transport layer interface
SYNOPSIS
None.
DESCRIPTION
The xpt driver provides a way for userland applications to issue certain CAM CCBs to the kernel.
Since the xpt driver allows direct access to the CAM subsystem, system administrators should exercise caution when granting access to this
driver. If used improperly, this driver can allow userland applications to crash a machine or cause data loss.
KERNEL CONFIGURATION
There is no kernel configuration required for the xpt driver. It is enabled when SCSI support is enabled in the kernel. There is one
instance of the xpt driver per CAM transport layer instance. Since there is currently only one CAM transport layer, there will only be one
instance of this driver.
IOCTLS
CAMIOCOMMAND This ioctl takes certain kinds of CAM CCBs and passes them through to the CAM transport layer for action. Only the following
CCB types are supported:
XPT_SCAN_BUS
XPT_RESET_BUS
XPT_SCAN_LUN
XPT_ENG_INQ
XPT_ENG_EXEC
XPT_DEBUG
XPT_DEV_MATCH
XPT_PATH_INQ
The above CCBs are the only ones supported since it makes more sense to send them through a generic passthrough device rather
than a passthrough device tied to a particular underlying SCSI device.
CAMGETPASSTHRU This ioctl takes an XPT_GDEVLIST CCB, and returns the passthrough device corresponding to the device in question.
FILES
/dev/xpt0 Character device node for the xpt driver.
DIAGNOSTICS
None.
SEE ALSO
cam(3), cam_cdbparse(3), pass(4), camcontrol(8)
HISTORY
The CAM transport layer driver first appeared in FreeBSD 3.0.
AUTHORS
Kenneth Merry <ken@FreeBSD.org>
BSD
October 10, 1998 BSD