lshostiplogin
使用 svcinfo lshostiplogin 指令，可列出由其「iSCSI 完整名稱 (IQN)」識別，且已登入使用 IP 位址配置的乙太網路埠的主機登入階段作業類型及其他詳細資料。
語法
>>-svcinfo lshostiplogin--+-id---+------------------------------> '-name ' >--+--------------------------------+--+----------------+------>< '- -filtervalue--attribute=value-' '- -filtervalue?-'
參數
- （選用）指出要顯示其登入詳細資料的已配置主機 IQN 的物件 ID。該值必須為 0 到 2047 之間的數字（每個 SVC 叢集的已配置 iSCSI/iSER IQN 的上限數量 [512 x 4 = 2048]）。
- （選用）指出要顯示其登入詳細資料的已配置主機 IQN 名稱的物件名稱。
- （選用）指定符合指定值的一或多個過濾器屬性的清單；請參閱 -filtervalue? 以取得支援的屬性。
- 註： 某些過濾器容許您在輸入指令時使用萬用字元。當您在 CLI 中使用萬用字元時，會套用下列規則：
- 萬用字元是星號 (*)。
- 指令最多可包含一個萬用字元，並且該萬用字元必須是字串中的第一個或最後一個字元。
- 使用萬用字元時，必須用雙引號 ("") 將過濾項目括起：lshostiplogin -filtervalue "attribute=value*"
- （選用）在報告中包含所有有效的過濾器屬性。lshostiplogin 指令的有效過濾器屬性如下：
- login_protocol
- host_id
- host_name
如需過濾屬性的相關資訊，請參閱 -filtervalue 參數的屬性。
說明
此指令用於列出登入階段作業類型和其他明細。
這份表格提供可以顯示為輸出視圖資料的屬性值。
| 屬性 | 說明 |
|---|---|
| id | 指出要顯示其登入詳細資料的已配置主機 IQN 的物件 ID。 |
| name | iSCSI 或 iSER 主機的唯一 IQN。此 IQN 必須屬於配置的主機物件。 |
| host_id | 此 IQN 所屬的主機物件 ID。 |
| host_name | 對應於 host_id 的主機名稱。 |
| login_count | 主機建立的到所有 I/O 群組中的叢集埠的登入階段作業總數。 |
| login_protocol | 指定已配置的主機用於與使用 IP 位址配置的乙太網路埠建立階段作業的連線通訊協定。該值可以是下列任一值：
|
| login | 指示從主機到叢集中的任何節點的單個階段作業的整數。該值是 0 - 31 範圍內的一個數字。 |
| node_id | 主機 IQN 建立登入階段作業（由 login 欄位所指示）的節點的節點 ID。該值是 1 - 32 範圍內的整數。 |
| node_name | 主機 IQN 建立登入階段作業（由 login 欄位所指示）的節點的節點名稱。該值是最多為 16 個字元的字串。 |
| port_id | 指示 lsportip 視圖所顯示的乙太網路埠（建立登入）的埠 ID。該值是 1 - 12 範圍內的一個數字。 |
| host_port_grp_id | 描述其登入的埠所屬的目標埠群組 ID。該值是 1 - 64 範圍內的一個數字。 |
| 通訊協定 (protocol) | 指示配置的 IP 主機 IQN 為建立 login 欄位所指示的登入階段作業而使用的連線通訊協定。該值可以是下列任一值：
|
| ip_version | 指示 IP 定址版本。顯示的值為 IPv4 或 IPv6。 |
| failover | 指示階段作業是指示本端還是失效接手 IP 位址。顯示的值為 yes 或 no。 |
範例 1
* IQN "iqn.1996-04.de.suse:01:d4aba8f69a95" logged onto node1 (node_id 1) port 2 and 3 and node2 (node_id 2) port 2 and 3,
with IPv4 version over iSCSI connection. lshostiplogin displays login sessions as shown below.
Host Info:
# svctask mkhost -iscsiname "iqn.1996-04.de.suse:01:d4aba8f69a95"
Host, id [0], successfully created
# lshost
id name port_count iogrp_count status site_id site_name host_cluster_id host_cluster_name
0 host0 1 4 online
Concise View
# lshostiplogin
id name host_id host_name login_count login_protocol
0 iqn.1996-04.de.suse:01:d4aba8f69a95 0 host0 4 iscsi
Json View
# lshostiplogin -json
[{ "id": "0", "name": "iqn.1996-04.de.suse:01:d4aba8f69a95", "host_id": "0", "host_name": "host0", "login_count": "4",
"login_protocol": "iscsi" }]
Detailed View
# lshostiplogin 0
id 0
name iqn.1996-04.de.suse:01:d4aba8f69a95
host_id 0
host_name host0
login_count 4
login_protocol iscsi
login 0
node_id 1
node_name node1
port_id 2
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 1
node_id 1
node_name node1
port_id 3
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 2
node_id 2
node_name node2
port_id 2
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 3
node_id 2
node_name node2
port_id 3
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
Json View
# lshostiplogin -json 0
{ "id": "0", "name": "iqn.1996-04.de.suse:01:d4aba8f69a95", "host_id": "0", "host_name": "host0", "login_count": "4",
"login_protocol": "iscsi", "logins": [{ "login": "0", "node_id": "1", "node_name": "node1", "port_id": "2",
"host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover": "no" }, {"login": "1", "node_id": "1",
"node_name": "node1", "port_id": "3", "host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover":
"no"}, { "login": "2", "node_id": "2", "node_name": "node2", "port_id": "2", "host_port_grp_id": "1", "protocol":
"iscsi", "ip_version": "IPv4", "failover": "no" }, {"login": "3", "node_id": "2", "node_name": "node2", "port_id": "3",
"host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover": "no"} ] }
NOTE: This CLI does not display sorted list of logins. Order in which login requests are served to host IQN, will
dictate order of logins displayed.
Another possible Detailed view after few logouts and logins
Detailed View
# lshostiplogin 0
id 0
name iqn.1996-04.de.suse:01:d4aba8f69a95
host_id 0
host_name host0
login_count 4
login_protocol iscsi
login 1
node_id 1
node_name node1
port_id 2
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 0
node_id 1
node_name node1
port_id 3
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 2
node_id 2
node_name node2
port_id 3
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 3
node_id 2
node_name node2
port_id 2
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
Json View
# lshostiplogin -json 0
{ "id": "0", "name": "iqn.1996-04.de.suse:01:d4aba8f69a95", "host_id": "0", "host_name": "host0", "login_count": "4",
"login_protocol": "iscsi", "logins": [{ "login": "1", "node_id": "1", "node_name": "node1", "port_id": "2",
"host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover": "no"}, {"login": "0", "node_id": "1",
"node_name": "node1", "port_id": "3", "host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover":
"no"}, { "login": "2", "node_id": "2", "node_name": "node2", "port_id": "3", "host_port_grp_id": "1", "protocol":
"iscsi", "ip_version": "IPv4", "failover": "no"}, {"login": "3", "node_id": "2", "node_name": "node2", "port_id": "2",
"host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover": "no"} ] }範例 2
* This example covers failover scenario for Example 1, when node 2 is down and all logins are established on node1 port 2 and 3:
Concise View
# lshostiplogin
id name host_id host_name login_count login_protocol
0 iqn.1996-04.de.suse:01:d4aba8f69a95 0 host0 4 iscsi
Json View
# lshostiplogin -json
[{ "id": "0", "name": "iqn.1996-04.de.suse:01:d4aba8f69a95", "host_id": "0", "host_name": "host0", "login_count": "4",
"login_protocol": "iscsi" }]
Detailed View
# lshostiplogin 0
id 0
name iqn.1996-04.de.suse:01:d4aba8f69a95
host_id 0
host_name host0
login_count 4
login_protocol iscsi
login 0
node_id 1
node_name node1
port_id 2
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 1
node_id 1
node_name node1
port_id 3
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 2
node_id 1
node_name node1
port_id 2
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover yes
login 3
node_id 1
node_name node1
port_id 3
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover yes
Json View
# lshostiplogin -json 0
{ "id": "0", "name": "iqn.1996-04.de.suse:01:d4aba8f69a95", "host_id": "0", "host_name": "host0", "login_count": "4",
"login_protocol": "iscsi", "logins": [{ "login": "0", "node_id": "1", "node_name": "node1", "port_id": "2",
"host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover": "no" }, {"login": "1", "node_id": "1",
"node_name": "node1", "port_id": "3", "host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover":
"no"}, { "login": "2", "node_id": "1", "node_name": "node1", "port_id": "2", "host_port_grp_id": "1", "protocol": "iscsi",
"ip_version": "IPv4", "failover": "yes" }, {"login": "3", "node_id": "1", "node_name": "node1", "port_id": "3",
"host_port_grp_id": "1", "protocol": "iscsi", "ip_version": "IPv4", "failover": "yes"} ] }範例 3
* This example covers following scenario:
1. IQN "iqn.1996-04.de.suse:01:d4aba8f69a95" has logged onto node1 (node_id: 1 IOgrp: 0) port 2 and node2 (node_id: 2
IOgrp: 0) port 2 with IPv4 version. Both the connections are over iSCSI.
2. IQN "iqn.1996-04.de.suse:03:d3bse3e25l70" has logged onto node3 (node_id: 3 IOgrp: 1) port 5 and node4 (node_id: 4
IOgrp: 1) port 5 with IPv4 version. Both the connections are over iSER.
# svctask mkhost -iscsiname "iqn.1996-04.de.suse:03:d3bse3e25l70"
Host, id [1], successfully created
# lshost
id name port_count iogrp_count status site_id site_name host_cluster_id host_cluster_name
0 host0 1 4 online
1 host1 1 4 online
Concise View
# lshostiplogin
id name host_id host_name login_count login_protocol
0 iqn.1996-04.de.suse:01:d4aba8f69a95 0 host0 2 iscsi
1 iqn.1996-04.de.suse:03:d3bse3e25l70 1 host1 2 iser
Json View
# lshostiplogin -json
[{ "id": "0", "name": "iqn.1996-04.de.suse:01:d4aba8f69a95", "host_id": "0", "host_name": "host0", "login_count": "2",
"login_protocol": "iscsi" }, { "id": "1", "name": "iqn.1996-04.de.suse:03:d3bse3e25l70", "host_id": "1", "host_name":
"host1", "login_count": "2", "login_protocol": "iser" }]
Detailed View 0
# lshostiplogin 0
id 0
name iqn.1996-04.de.suse:01:d4aba8f69a95
host_id 0
host_name host0
login_count 2
login_protocol iscsi
login 0
node_id 1
node_name node1
port_id 2
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
login 1
node_id 2
node_name node2
port_id 2
host_port_grp_id 1
protocol iscsi
ip_version IPv4
failover no
Json View
# lshostiplogin -json 0
{ "id": "0", "name": "iqn.1996-04.de.suse:01:d4aba8f69a95", "host_id": "0", "host_name": "host0", "login_count": "2",
"login_protocol": "iscsi", "logins": [ { "login": "0", "node_id": "1", "node_name": "node1", "port_id": "2",
"host_port_grp_id": "1", "protocols": "iscsi", "ip_version": "IPv4", "failover": "no"}, { "login": "1", "node_id": "2",
"node_name": "node2", "port_id": "2", "host_port_grp_id": "1", "protocols": "iscsi", "ip_version": "IPv4", "failover":
"no" } ] }
Detailed View 1
# lshostiplogin 1
id 1
name iqn.1996-04.de.suse:03:d3bse3e25l7
host_id 1
host_name host1
login_count 2
login_protocol iser
login 0
node_id 3
node_name node3
port_id 5
host_port_grp_id 2
protocol iser
ip_version IPv4
failover no
login 1
node_id 4
node_name node4
port_id 5
host_port_grp_id 2
protocol iser
ip_version IPv4
failover no
Json View
# lshostiplogin -json 1
{ "id": "1", "name": "iqn.1996-04.de.suse.03:d3bse3e25l7", "host_id": "1", "host_name": "host1", "login_count": "2",
"login_protocol": "iser", "logins": [ { "login": "0", "node_id": "3", "node_name": "node3", "port_id": "5", "host_port_grp_id":
"2", "protocols": "iser", "ip_version": "IPv4", "failover": "no"}, { "login": "1", "node_id": "4", "node_name": "node4",
"port_id": "5", "host_port_grp_id": "2", "protocols": "iser", "ip_version": "IPv4", "failover": "no" } ] }