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
ISCSI(4)						   BSD Kernel Interfaces Manual 						  ISCSI(4)

NAME
iscsi -- iSCSI initiator SYNOPSIS
To compile this driver into the kernel, place the following line in the kernel configuration file: device iscsi Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): iscsi_load="YES" DESCRIPTION
The iscsi subsystem provides the kernel component of an iSCSI initiator. The initiator is the iSCSI client, which connects to an iSCSI tar- get, providing local access to a remote block device. The userland component is provided by iscsid(8) and both the kernel and userland are configured using iscsictl(8). The iscsi subsystem is responsible for implementing the "Full Feature Phase" of the iSCSI protocol. SYSCTL VARIABLES
The following variables are available as both sysctl(8) variables and loader(8) tunables: kern.iscsi.ping_timeout The number of seconds to wait for the target to respond to a NOP-Out PDU. In the event that there is no response within that time the session gets forcibly restarted. kern.iscsi.iscsid_timeout The number of seconds to wait for ctld(8) to establish a session. After that time iscsi will abort and retry. kern.iscsi.login_timeout The number of seconds to wait for a login attempt to succeed. After that time iscsi will abort and retry. kern.iscsi.maxtags The maximum number of outstanding IO requests. kern.iscsi.fail_on_disconnection Controls the behavior after an iSCSI connection has been dropped due to network problems. When set to 1, a dropped connection causes the iSCSI device nodes to be destroyed. After reconnecting, they will be created again. By default, the device nodes are left intact. While the connection is down all input/output operations are suspended, to be retried after the connection is reestablished. SEE ALSO
iscsi.conf(5), iscsictl(8), iscsid(8) HISTORY
The iscsi subsystem first appeared in FreeBSD 10.0. AUTHORS
The iscsi subsystem was developed by Edward Tomasz Napierala <trasz@FreeBSD.org> under sponsorship from the FreeBSD Foundation. BSD
September 11, 2014 BSD