How do I breakdown the Target (tx) part of a cXtXdX Iscsi device?


 
Thread Tools Search this Thread
Operating Systems Solaris How do I breakdown the Target (tx) part of a cXtXdX Iscsi device?
# 1  
Old 05-24-2010
How do I breakdown the Target (tx) part of a cXtXdX Iscsi device?

Hello,

I am trying to breakdown the cXtXdX (specifically tX) part of an iscsi device.

I know in the fibre SAN world, this tX will usually be a combination of the path to device/device WWN.

From what I understand in iscsi world it is similar, breaking down into hba-id/initator-id/Lun-id-or-0.. is this correct?

And if so, how do I seperate these out? How do I knwo which is the hba-id and son on?

Thank you,
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Linux

How to boot iSCSI target from console linux?

I need boot any images from iSCSI and I'd like to boot from linux console of a previous LiveCD booted. Is possible, without gpxe, ipxe firmware or similar? With a simple iSCSI initiator for example? (1 Reply)
Discussion started by: spark2k06
1 Replies

2. HP-UX

Unable to delete iscsi target

Hi Please can someone give me a hint on this, when I list the targets, I see two o them: #iscsiutil -p Operational Target Information ------------------------------ Target # 1 ----------- Target Name : iqn.1992-08.com.netapp:sn.142241859 Target Alias ... (2 Replies)
Discussion started by: fretagi
2 Replies

3. HP-UX

After adding new iscsi target port, still the session state of that target port is showing offline

Hi, I wanted to configure new iscsi port on HPUX system, i added the target port address and configured it, once done, went to array side and searched for that host iqn number , but was nt able to find the same, came to host, then when i ran "iscsiutil -pVS" command it gave me below result ... (0 Replies)
Discussion started by: Vinay Kumar D
0 Replies

4. UNIX for Advanced & Expert Users

Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?

I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got fdisk: "Error in ioctl DKIOCSMBOOT" Details -- According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (1 Reply)
Discussion started by: ctafret
1 Replies

5. Solaris

Can You Mount FAT32 iSCSI Target in Solaris 10 (sparc)?

I get "mount: I/O error" when trying to mount an existing FAT32 iSCSI target. I also tried formatting the iSCSI target with fdisk and got fdisk: "Error in ioctl DKIOCSMBOOT" Details -- According to the format command, the whole disk is allocated to slice 6 and /dev/rdsk shows this as:... (0 Replies)
Discussion started by: ctafret
0 Replies

6. UNIX for Advanced & Expert Users

LTO2 tape drive as iSCSI target

I'm using Bacula as my backup system, with full backups going to an LTO2 tape drive, while differentials and incrementals go to a disk array on my main server, babylon4. The tape drive is currently attached to a separate machine, because babylon4 does not have a SCSI controller, nor a free PCI-X... (0 Replies)
Discussion started by: Phil Stracchino
0 Replies

7. Solaris

Iscsi - target + initiator on the same host.

Hi all iscsiadm / iscsitadm. Ive created two devices on a host. # iscsitadm list target Target: 1-disk0 iSCSI Name: iqn.1986-03.com.sun:02:f105ddf3-52a4-ed7a-9590-c3d354b8fc32.1-disk0 Connections: 1 Target: 1-disk1 iSCSI Name:... (0 Replies)
Discussion started by: sbk1972
0 Replies

8. Solaris

iscsi device on solaris 10 (x64)

Hello! I have several disks discovered using iscsi protocol. There disks are represented in OS like c2txd0 . logs: Is it possible to change drive path, for example, from c2t6d0 to c2t7d0? It's important for me because I have to install oracle RAC on RAW devices. NIck (0 Replies)
Discussion started by: skelet
0 Replies
Login or Register to Ask a Question
st_san_safe(5)							     OBSOLETED							    st_san_safe(5)

NAME
st_san_safe - determine whether access to tape device special files without the no-rewind-on-close option is allowed (OBSOLETED) VALUES
Failsafe Default Allowed values Recommended values or DESCRIPTION
Note: this tunable is obsoleted and has been renamed to beginning with release HP-UX 11i v3. This tunable notifies the tape driver whether it should allow access to device special files without the no-rewind-on-close option. When this tunable is on the tape driver will fail any open on a tape device special file without the no-rewind-on-close option (that is, or with a status of The tunable allows the safe sharing of tape devices in SAN tape backup solution configurations. The disabling of device special files without no-rewind-on-close in a SAN tape backup solution configuration prevents the accidental sending of a rewind command on close from HP-UX systems via standard tape commands like which would corrupt a backup in process. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Tunable Be Turned On? This tunable should be turned on if the system is going to be used in a SAN tape backup solution configuration. What Are the Side Effects of Turning the Tunable On? The tape driver will fail any open to a tape device special file that does not have the no-rewind-on-close option with a status of This behavior prevents the usage of any tape device special file without the no-rewind-on-close option. When Should the Tunable Be Turned Off? This tunable should be turned off if the system is not part of a SAN tape backup solution configuration or the system utilizes will not function unless it has access to device special files without the no-rewind-on-close option. What Are the Side Effects of Turning the Tunable Off? A rewind may be issued from this system accidentally on close possibly corrupting a backup being issued from another system on the SAN. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by Hewlett-Packard. SEE ALSO
norewind_close_disabled(5), scsi_tape(7), scsimgr_estape(7). Tunable Kernel Parameters st_san_safe(5)