SAN questions about Sun StorageTek array


 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory SAN questions about Sun StorageTek array
# 8  
Old 05-06-2011
Everything is clear now.

Under CAM, map initiators to hosts, and map hosts to volumes. The so-call host is just a name to connect initiators (FC ports) to the disk volumes.

initiators <> hosts <> volumes

Thanks everyone again!
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Solaris

StorageTek 2540 SAN array

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

2. Filesystems, Disks and Memory

Backup Sun StorageTek Common Array Manager's configuration

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

3. Solaris

Sun StorageTek Common Array Manager 6.0 works very slowly

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. Solaris

Accessing a StorageTek 2530 Disk array from SUN, SPARC Enterprise T2000

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

5. Filesystems, Disks and Memory

Configure large volume on Sun StorageTek 2540 array

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
Login or Register to Ask a Question
TARGETS(5)						      BSD File Formats Manual							TARGETS(5)

NAME
targets -- configuration file for iSCSI targets SYNOPSIS
targets DESCRIPTION
The targets file describes the iSCSI storage which is presented to iSCSI initiators by the iscsi-target(8) service. A description of the iSCSI protocol can be found in Internet Small Computer Systems Interface RFC 3720. Each line in the file (other than comment lines that begin with a '#') specifies an extent, a device (made up of extents or other devices), or a target to present to the initiator. Each definition, an extent, a device, and a target, is specified on a single whitespace delimited line. The extent definition specifies a piece of storage that will be used as storage, and presented to initiators. It is the basic definition for an iSCSI target. Each target must contain at least one extent definition. The first field in the definition is the extent name, which must begin with the word ``extent'' and be followed by a number. The next field is the file or NetBSD device which will be used as persistent storage. The next field is the offset (in bytes) of the start of the extent. This field is usually 0. The fourth field in the definition is the size of the extent. The basic unit is bytes, and the shorthand KB, MB, GB, and TB can be used for kilobytes (1024 bytes), megabytes (1024 kilobytes), gigabytes (1024 megabytes), and terabytes (1024 gigabytes) respectively. It is possible to use the word ``size'' to use the full size of the pre-existing regular file given in the extent name. The device definition specifies a LUN or device, and is made up of extents and other devices. It is possible to create hierarchies of devices using the device definition. The first field in the definition is the device name, which must begin with the word ``device'' and be followed by a number. The next field is the type of resilience that is to be provided by the device. For simple devices, RAID0 suffices. Greater resilience can be gained by using the RAID1 resilience field. Following the resilience field is a list of extents or other devices. Large devices can be created by using multiple RAID0 extents, in which case each extent will be concatenated. Resilient devices can be cre- ated by using multiple RAID1 devices or extents, in which case data will be written to each of the devices or extents in turn. If RAID1 resilience is used, all the extents or sub-devices must be the same size. Please note that RAID1 recovery is not yet supported by the iscsi-target(8) utility. An extent or sub-device may only be used once. The target definition specifies an iSCSI target, which is presented to the iSCSI initiator. Multiple targets can be specified. The first field in the definition is the target name, which must begin with either of the words ``target'' or ``lun'' and be followed by a number. Optionally, if a target is followed by an ``='' sign and some text, the text is taken to be that of the iSCSI Qualified Name of the target. This IQN is used by the initiator to connect to the appropriate target. The next field is a selector for whether the storage should be pre- sented as writable, or merely as read-only storage. The field of ``rw'' denotes read-write storage, whilst ``ro'' denotes read-only storage. The next field is the device or extent name that will be used as persistent storage for this target. The fourth field is a slash-notation netmask which will be used, during the discovery phase, to control the network addresses to which targets will be presented. The magic val- ues ``any'' and ``all'' will expand to be the same as ``0/0''. If an attempt is made to discover a target which is not allowed by the net- mask, a warning will be issued using syslog(3) to make administrators aware of this attempt. The administrator can still use tcp wrapper functionality, as found in hosts_access(5) and hosts.deny(5) to allow or deny discovery attempts from initiators as well as using the inbuilt netmask functionality. FILES
/etc/iscsi/targets the list of exported storage targets SEE ALSO
syslog(3), hosts.deny(5), hosts_access(5), iscsi-target(8) HISTORY
The targets file first appeared in NetBSD 4.0. BSD
December 18, 2007 BSD