Fwd: Question about nvmetcli (tcp)

[Sudheendra Sampath <sudheendra.sampath@gmail.com>]

---------- 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