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
list_devices(1) 														   list_devices(1)

NAME
list_devices - list allocatable devices SYNOPSIS
list_devices [-s] [ -U uid] -l [device] list_devices [-s] [ -U uid] -n [device] list_devices [-s] [ -U uid] -u [device] The list_devices utility lists the allocatable devices in the system according to specified qualifications. The device and all device special files associated with the device are listed. The device argument is optional and, if it is not present, all relevant devices are listed. The following options are supported: -l [device] Lists the pathname(s) of the device special files associated with the device that are allocatable to the current process. If device is given, lists only the files associated with the specified device. -n [device] Lists the pathname(s) of device special files associated with the device that are allocatable to the current process but are not currently allocated. If device is given, lists only the files associated with that device. -s Silent. Suppresses any diagnostic output. -u [device] Lists the pathname(s) of device special files, associated with the device that are allocated to the owner of the current process. If device is given, list only the files associated with that device. -U uid Uses the user ID uid instead of the real user ID of the current process when performing the list_devices operation. Only a user with the solaris.device.revoke authorization can use this option. The following exit values are returned: non--zero An error occurred. /etc/security/device_allocate /etc/security/device_maps /etc/security/dev/* /usr/security/lib/* See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ allocate(1), deallocate(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5) The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for more information. /etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment. 28 Mar 2005 list_devices(1)