The hyperbus is part of netcpad (/etc/init.d/netcpad) and should be pushed when you prepare your hosts as transport nodes. You can use nsxcli on the ESXi host to check its status (get hyperbus connection info). If you're saying that it isn't available, then you have a problem somewhere and I'd start with the logs on Manager and the ESXi hosts to see what happened there. Ensure that you're using supported versions of the components all the way around as well.
Thank you for your answer. Are you saying that the vib isn't part of the local control plane vibs that are packaged with nsx kernel files?
What I find strange is that if I compare my install with nsx-t hands on labs install I see:
- the esxi hosts in HoL do have nsx-hyperbus vib installed
- the manifest file in the nsx manager repository (in http://<nsx-manager-ip-address>:8080/repository/<target-nsx-t-version>/metadata/manifest) does show nsx-hyperbus vib in Hands on labs
- my install has none of these
Is there any specific know I should've turned on to say that my install should be "container-ready"? Licensing editions do not appear to indicate that.
Just an update.
Apparently the VIB nsx-hyperbus has disappeared from the lcp files since NSX-T 2.3 (was there in NSX-T 2.2 lcp file), but there's absolutely no notice on release notes or documentation on how did the behaviour change.
My get nsx-hyperbus connection is empty and due to this my node-agent containers are failing their liveness probes, which stops container deployment.
If anybody has an idea, it is more than welcome.
I should recommend if possible to use the 2.4 version instead. otherwise, paste your logs in order to see was is painted there.