Re: Question about nvmetcli (tcp)

Re: Question about nvmetcli (tcp)

[Sagi Grimberg]

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

Fwd: Question about nvmetcli (tcp)

[Sudheendra Sampath]

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

Fwd: Question about nvmetcli (tcp)

[Sudheendra Sampath]

---------- Forwarded message ---------
From: Sudheendra Sampath <sudheendra.sampath@gmail.com>
Date: Thu, Dec 26, 2019 at 5:43 PM
Subject: Re: Question about nvmetcli (tcp)
To: Sagi Grimberg <sagi@grimberg.me>
Cc: <linux-nvme@lists.infradead.org>, <chaitanya.kulkarni@wdc.com>,
<james.p.freyensee@intel.com>


Issue RESOLVED:  I created the soft link in "sysfs" and was able to
connect to the target.


On Fri, Dec 20, 2019, 3:42 PM Sagi Grimberg <sagi@grimberg.me> wrote:
>
>
>
> 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.



-- 
Regards

Sudheendra Sampath

_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme