Hi, Suman
               Thank you for the email. We have tested ipv6 with 2 machines (target and initiator) and it can discover
Comands that I've used for your reference
Target

./app/nvmf_tgt/nvmf_tgt -c ../target_config/nvme_ipv6.conf

Initiator
nvme discover -t rdma -a fe80::7efe:90ff:fe5c:1862%ens785 -s 4420

# nvme discover -t rdma -a fe80::7efe:90ff:fe5c:1862%ens785 -s 4420


Log

Discovery Log Number of Records 1, Generation counter 4

=====Discovery Log Entry 0======

trtype:  rdma

adrfam:  ipv6

subtype: nvme subsystem

treq:    not specified

portid:  0

trsvcid: 4420

subnqn:  nqn.2016-06.io.spdk:cnode1

traddr:  fe80::7efe:90ff:fe5c:1862%enp143s0

rdma_prtype: not specified

rdma_qptype: connected

rdma_cms:    rdma-cm

rdma_pkey: 0x0000


Best Regards,
Anna

From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Suman Chakraborty
Sent: Wednesday, February 28, 2018 2:58 AM
To: spdk(a)lists.01.org
Subject: [SPDK] Nvme discover using link-local

Hi ,

I am trying to discover using my IPV6 link-local address .
nvme discover -t rdma -a fe80::0c6:11ff:fe41:0516%eth0 -s 4420.
It is unable to discover.when I check the dmesg on the initiator side I get the error "
nvme nvme0: rdma_resolve_addr wait failed (-110)."
Can someone help to resolve this issue ?

Regards
Suman Chakraborty