The command you want to look at is "server_iscsi".  You can use it to list a wide variety of information about iSCSI-attached hosts.  It also supports using iSCSI Target aliases, to help simplify organization (I used to make aliases that included the hostname of the connected server, so that we can easily see mismatched connections or missing servers.  You might have to try creating aliases for servers that you do know, just to limit the list of servers you don't know anything about.  Here some iSCSI output from my box:  [nasadmin[NAME]-cs0 ~]$ server_iscsi server_2 -target -list server_2 : alias_name          portal_groups      iscsi_name SAP-PROD            1                  iqn.1992-05.com.emc:apm001046016340000-1 SAP-PORTAL01        1                  iqn.1992-05.com.emc:apm001046016340000-2 SAP-PORTAL02        1                  iqn.1992-05.com.emc:apm001046016340000-3 SAP-PORTAL03        1                  iqn.1992-05.com.emc:apm001046016340000-4 SAP-PORTAL04        1                  iqn.1992-05.com.emc:apm001046016340000-5  Each of the iSCSI names in the far right field is the iSCSI initiator's connection. It doesn't have the IP hostname, but you can see that when you use server_iscsi -target -info and carefully check the connected initiator field:  [nasadmin[NAME]-cs0 ~]$ server_iscsi server_2 -target -info -all server_2 : Target Alias Name: SAP-PROD Target iSCSI Name: iqn.1992-05.com.emc:apm001046016340000-1 Serial Number: 1 Portal Group Tag: 1   Portal: 172.19.232.201:3260 Logical Units:   0  : (Production) fsid=44 size=256000MB alloc=247901MB dense  path=/ifs1/fs44_T1_LUN0_APM001046016340000/fs44_T1_LUN0_APM001046016340000 Connected Initiators:   iqn.1991-05.com.microsoft:sap1prodsrvr01.mycorp.com  Target Alias Name: SAP-PORTAL01 Target iSCSI Name: iqn.1992-05.com.emc:apm001046016340000-2 Serial Number: 2 Portal Group Tag: 1   Portal: 172.19.232.201:3260 Logical Units:   0  : (Production) fsid=21 size=81920MB alloc=58318MB dense  path=/ifs3/fs21_T2_LUN0_APM001046016340000/fs21_T2_LUN0_APM001046016340000 Connected Initiators:   iqn.1991-05.com.microsoft:sapsrvr01.mycorp.com  Target Alias Name: SAP-PORTAL02 Target iSCSI Name: iqn.1992-05.com.emc:apm001046016340000-3 Serial Number: 3 Portal Group Tag: 1   Portal: 172.19.232.201:3260 Logical Units:   0  : (Production) fsid=41 size=40960MB alloc=21575MB dense  path=/ifs_pbludb01/fs41_T3_LUN0_APM001046016340000/fs41_T3_LUN0_APM001046016340000 Connected Initiators:   iqn.1991-05.com.microsoft:sapsrvr02.mycorp.com  Target Alias Name: SAP-PORTAL03 Target iSCSI Name: iqn.1992-05.com.emc:apm001046016340000-4 Serial Number: 4 Portal Group Tag: 1   Portal: 172.19.232.201:3260 Logical Units:   0  : (Production) fsid=42 size=97280MB alloc=40489MB dense  path=/ifs_tpapaltdb03_f/fs42_T4_LUN0_APM001046016340000/fs42_T4_LUN0_APM001046016340000   1  : (Production) fsid=43 size=15360MB alloc=15354MB dense  path=/ifs_tpapaltdb03_i/fs43_T4_LUN1_APM001046016340000/fs43_T4_LUN1_APM001046016340000 Connected Initiators:   iqn.1991-05.com.microsoft:sapsbackup01.mycorp.com  Target Alias Name: SAP-PORTAL04 Target iSCSI Name: iqn.1992-05.com.emc:apm001046016340000-5 Serial Number: 5 Portal Group Tag: 1   Portal: 172.19.232.201:3260 Logical Units:   0  : (Production) fsid=32 size=153600MB alloc=137473MB dense  path=/ifs78/fs32_T5_LUN0_APM001046016340000/fs32_T5_LUN0_APM001046016340000 Connected Initiators:   iqn.1991-05.com.microsoft:sapsbackup02.mycorp.com  You've probably exhausted all the fields in the server_stats commands - I have yet to find any per-initiator statistics; I don't think they programmed any.  At this point, you might have to rely on server_netstat commands.  You can see each iSCSI connection in the output, since they'll connect to the Celerra on port 3260 to establish the session.  You can use this list to generate a list of hostnames, then match them up in the initiator output.  Let us know if that helps!  Karl
Hi all,  In a Celerra environment, what is the quickest way to find the iSCSI initiatiors who are actually using your system?  In Unisphere GUI only iSCSI luns and targets are visible. On each target I can see a list with connected initiators.  The server_stats -monitor iscsi gives info about iSCSI reads/writes, but I cannot find initiators in the stats. The system here has a lot of luns, and a lot of targets with a lot of clients connected. However customer doesn't know who the users are, and we have to migrate to a new box...  Questions: 1. How can I translate the connected-initiator names (i.e. iqn.1994-05.com.redhat:2987a8787) to a hostname or IP-address? 2. How can I see which initiator is actually performing IO's? Are there additional server_stats available which provide stats on iSCSI-clients/initiators?   Thanks for any tips!
Celerra iSCSI - how to find the iSCSI users?