* Re: Question about nvmetcli (tcp)
[not found] <CABnqofwdPfb=RfCDUh6kU2CUV4v0xxVaT--rfQOZMJy6DG3MTQ@mail.gmail.com>
@ 2019-12-20 23:42 ` Sagi Grimberg
[not found] ` <CABnqofzJybjHwLhuoC26bt7W05dc3ZjWa9OkmuD1_7-Y7ma3Xg@mail.gmail.com>
2019-12-26 22:50 ` Sudheendra Sampath
1 sibling, 1 reply; 3+ messages in thread
From: Sagi Grimberg @ 2019-12-20 23:42 UTC (permalink / raw)
To: Sudheendra Sampath, linux-nvme; +Cc: james.p.freyensee, chaitanya.kulkarni
On 12/20/19 11:38 AM, Sudheendra Sampath wrote:
> Hi,
>
> Apologies for flooding your inbox. I got your contact information from
> the linux-nvme mailing list.
>
> I am trying to setup a target -> initiator using nvmetcli. Below is my
> json file :
>
> {
> "hosts": [],
> "ports": [
> {
> "addr": {
> "adrfam": "ipv4",
> "traddr": "192.168.123.32",
> "treq": "not specified",
> "trsvcid": "4420",
> "trtype": "tcp"
> },
> "portid": 1,
> "referrals": [],
> "subsystems": []
You are missing the soft link that binds the subsystem to the port.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread
* Fwd: Question about nvmetcli (tcp)
[not found] <CABnqofwdPfb=RfCDUh6kU2CUV4v0xxVaT--rfQOZMJy6DG3MTQ@mail.gmail.com>
2019-12-20 23:42 ` Question about nvmetcli (tcp) Sagi Grimberg
@ 2019-12-26 22:50 ` Sudheendra Sampath
1 sibling, 0 replies; 3+ messages in thread
From: Sudheendra Sampath @ 2019-12-26 22:50 UTC (permalink / raw)
To: linux-nvme
Hi,
Apologies for flooding your inbox.
I am trying to setup a target -> initiator using nvmetcli. Below is
my json file :
{
"hosts": [],
"ports": [
{
"addr": {
"adrfam": "ipv4",
"traddr": "192.168.123.32",
"treq": "not specified",
"trsvcid": "4420",
"trtype": "tcp"
},
"portid": 1,
"referrals": [],
"subsystems": []
}
],
"subsystems": [
{
"allowed_hosts": [],
"attr": {
"allow_any_host": "1",
"serial": "a33829313050f265",
"version": "1.3"
},
"namespaces": [
{
"device": {
"nguid": "00000000-0000-0000-0000-000000000000",
"path": "/dev/nvme0n1",
"uuid": "e8b0ccf0-9fce-4efc-877a-07c0f1ecc086"
},
"enable": 1,
"nsid": 1
}
],
"nqn": "simnqn"
}
]
}
When I run 'nvmetcli restore foo.json", I see the following in dmesg :
[Fri Dec 20 11:20:53 2019] nvmet: adding nsid 1 to subsystem simnqn
(On target system) <<<<<
Now, from the client machine when I try to connect using 'nvme
connect', I get 'connection refused'.
root@initiator01:/home/ssgroot# nvme connect -t tcp -n simnqn -a
192.168.123.32 -s 4420
Failed to write to /dev/nvme-fabrics: Connection refused
The 'dmesg' output on the client system shows :
[Fri Dec 20 11:35:55 2019] nvme nvme0: failed to connect socket: -111
(On initiator system) <<<<<
Any help appreciated.
--
Regards
Sudheendra Sampath
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
^ permalink raw reply [flat|nested] 3+ messages in thread