ESXi

 View Only

  • 1.  "Adapter or transport target not found" error when trying to discover NVMe/TCP target

    Posted May 07, 2024 09:28 AM

    Is it a known problem ?

    Only on ESXi 8.0 u2 when trying to discover the NVMe/TCP target - getting the error message :

    "Adapter or transport target not found"

    dmesg :

    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)World: 12321: VC opID esxcli-16-c724 maps to vmkernel opID 7efc154f
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMEDEV:1408 Ctlr 256 allocated with name nqn.2014-08.org.nvmexpress.discovery#vmhba64#172.20.47.190:4420
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:158 Controller 256, connecting using parameters:
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:161 kato:      30000
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:162 subtype:   1
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:163 cdc:       0
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:166 target type:    NVMe
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:174 vmkParams.asqsize:   32
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:175 vmkParams.cntlid:    0xffff
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:176 vmkParams.hostid:    66330d2d-2239-870c-12f0-ecf4bbca9ad4
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:178 vmkParams.hostnqn:   nqn.2014-08.com.xxxxxx.lab:nvme:localhost
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:179 vmkParams.subnqn:    nqn.2014-08.org.nvmexpress.discovery
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:196 vmkParams.trType:    TCP
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:197 vmkParams.trsvcid:   4420
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:199 vmkParams.traddr:    172.20.47.190
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)NVMFDEV:201 vmkParams.tsas.digest:    0
    2024-05-02T04:10:58.161Z cpu15:1050010 opID=7efc154f)nvmetcp:nt_ConnectController:787 vmhba64, controller 256
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)nvmetcp:nt_ConnectQueueInt:4518 [ctlr 256] queue 0, size 32, actual size 56
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)nvmetcp:nt_ConnectCM:4858 [ctlr 256, queue 0] 
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)NVMFNET:149 Uplink: vmnic0, portset: vSwitch1.
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)nvmetcp:nt_ConnectCM:4903 [ctlr 256, queue 0] Failed to get source vmknic for NVMe/TCP traffic on vmnic0: Not found
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)nvmetcp:nt_FindTxPduByCCCID:324 [ctlr 256, queue 0] txPdu 0x431208a04280 not in expected pending state, state: 0.
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)nvmetcp:nt_ConnectQueueInt:4579 [ctlr 256, queue 0] failed to connect: Not found
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)nvmetcp:nt_FreeSubmissionResources:5657 [ctlr 256, queue 0] 
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)nvmetcp:nt_ConnectController:866 Failed to connect admin queue: Not found
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)WARNING: NVMFDEV:1065 Failed to transport connect controller 256, status: Not found
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)NVMEDEV:1589 Ctlr 256 freeing
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)NVMEDEV:8811 Cancel requests of controller 256, 0 left.
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)WARNING: NVMFDEV:1816 Failed to connect to discovery controller, status: Not found
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)WARNING: NVMFEVT:2021 Failed to discover controllers, status: Not found
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)WARNING: NVMFEVT:1615 Discover and connect controller failed: Not found
    2024-05-02T04:10:58.162Z cpu15:1050010 opID=7efc154f)WARNING: NVMFVSI:1149 Failed to discover controllers: Not found

    TIA



  • 2.  RE: "Adapter or transport target not found" error when trying to discover NVMe/TCP target

    Broadcom Employee
    Posted May 07, 2024 09:41 AM

    please check https://infohub.delltechnologies.com/en-us/l/dell-powerstore-vmware-vsphere-best-practices-2/nvme-fc-host-configurations-2/


    Original Message


  • 3.  RE: "Adapter or transport target not found" error when trying to discover NVMe/TCP target

    Posted May 07, 2024 09:45 AM

    Thanks, but we are not using NVMe/FC.


    Original Message


  • 4.  RE: "Adapter or transport target not found" error when trying to discover NVMe/TCP target

    Broadcom Employee
    Posted May 07, 2024 09:56 AM

    please validate:https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-storage/GUID-5F776E6E-62B1-445D-854C-BEA689DD4C92.html


    Original Message


  • 5.  RE: "Adapter or transport target not found" error when trying to discover NVMe/TCP target

    Posted Aug 11, 2024 08:46 AM
    Edited by sfields Aug 11, 2024 08:49 AM

    I followed this document, it didn't help.

    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)World: 12321: VC opID esxcli-13-71d9 maps to vmkernel opID bc349051
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMEDEV:1408 Ctlr 260 allocated with name nqn.2014-08.org.nvmexpress.discovery#vmhba64#172.20.47.190:4420
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:158 Controller 260, connecting using parameters:
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:161 kato:      30000
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:162 subtype:   1
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:163 cdc:       0
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:166 target type:    NVMe
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:174 vmkParams.asqsize:   32
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:175 vmkParams.cntlid:    0xffff
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:176 vmkParams.hostid:    66b898c3-02d7-0226-ee67-ecf4bbd4a624
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:178 vmkParams.hostnqn:   nqn.2014-08.org.nvmexpress:uuid:66b898c3-02d7-0226-ee67-ecf4bbd4a624
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:179 vmkParams.subnqn:    nqn.2014-08.org.nvmexpress.discovery
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:196 vmkParams.trType:    TCP
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:197 vmkParams.trsvcid:   4420
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:199 vmkParams.traddr:    172.20.47.190
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFDEV:201 vmkParams.tsas.digest:    0
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)nvmetcp:nt_ConnectController:787 vmhba64, controller 260
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)nvmetcp:nt_ConnectQueueInt:4518 [ctlr 260] queue 0, size 32, actual size 56
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)nvmetcp:nt_ConnectCM:4858 [ctlr 260, queue 0] 
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMFNET:149 Uplink: vmnic0, portset: vSwitch1.
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)nvmetcp:nt_ConnectCM:4903 [ctlr 260, queue 0] Failed to get source vmknic for NVMe/TCP traffic on vmnic0: Not found
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)nvmetcp:nt_FindTxPduByCCCID:324 [ctlr 260, queue 0] txPdu 0x431268e042c0 not in expected pending state, state: 0.
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)nvmetcp:nt_ConnectQueueInt:4579 [ctlr 260, queue 0] failed to connect: Not found
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)nvmetcp:nt_FreeSubmissionResources:5657 [ctlr 260, queue 0] 
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)nvmetcp:nt_ConnectController:866 Failed to connect admin queue: Not found
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)WARNING: NVMFDEV:1065 Failed to transport connect controller 260, status: Not found
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMEDEV:1589 Ctlr 260 freeing
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)NVMEDEV:8811 Cancel requests of controller 260, 0 left.
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)WARNING: NVMFDEV:1816 Failed to connect to discovery controller, status: Not found
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)WARNING: NVMFEVT:2021 Failed to discover controllers, status: Not found
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)WARNING: NVMFEVT:1615 Discover and connect controller failed: Not found
    2024-08-11T12:43:10.354Z cpu53:1050279 opID=bc349051)WARNING: NVMFVSI:1149 Failed to discover controllers: Not found


    Original Message


  • 6.  RE: "Adapter or transport target not found" error when trying to discover NVMe/TCP target

    Posted Aug 11, 2024 08:50 AM

    "Failed to get source vmknic for NVMe/TCP traffic on vmnic0: Not found"


    Original Message


  • 7.  RE: "Adapter or transport target not found" error when trying to discover NVMe/TCP target

    Posted Aug 11, 2024 08:53 AM

    That's the problem???

    "Auto discovery of NVMe Discovery Service might fail on ESXi hosts with NVMe/TCP configurations"

    https://docs.vmware.com/en/VMware-vSphere/8.0/rn/vsphere-esxi-802-release-notes/index.html


    Original Message