When adding the NVMe over TCP controllers the non-vVOL targets are discovered but the vVVOL targets are not automatically discovered.
non-vvol:
vmkernel: cpu34:2099527 opID=bdd27c70)NVMFDEV:1245 Controller 979 (nqn.####.discovery#vmhba##<ipaddr>:8009) registered successfully.
vmkernel: cpu32:2099548 opID=9fbf08c)NVMFDEV:1245 Controller 980 (nqn.####vmhba##<ipaddr>:4420) registered successfully.
vmkernel: cpu32:2099548 opID=9fbf08c)NVMFDEV:1245 Controller 981 (nqn.####vmhba##<ipaddr>:4420) registered successfully.
vvol:
vmkwarning: cpu50:2098709)WARNING: NvmeDiscover: 2344: No IO handle to issue requests to controller nqn.####vvol#vmhba##<ipaddr>:4420
vmkernel: cpu50:2098709)NvmeDiscover: 3543: Update of controller nqn.####vvol#vmhba##<ipaddr>:4420 failed with No connection
vmkernel: cpu50:2098709)NvmeDiscover: 7974: controller probe failed status:No connection nqn.####vvol#vmhba##<ipaddr>:4420
VMware vSphere ESXi 8.0 U3
Rescan Storage Providers to discover the vVOL targets.
If targets do not appear following rescan please open a case with Broadcom Support.