County ESXi transport-node install stays stuck because the NSX VIB depot is unreachable from the host. What should the administrator check first?
Select an answer to reveal the explanation.
Short Explanation
Host prep is a delivery truck that has to reach the depot. If the VIB source is unreachable, the transport node never finishes. A DFW rule for an app VIP will not fetch those packages.
Full Explanation
When county ESXi transport-node install stays stuck because the NSX VIB depot is unreachable from the host, the administrator should check NSX Manager-to-host connectivity and depot or VIB reachability first. Host preparation is a delivery path from Manager and the VIB source to the ESXi host; if that path is broken, the transport node never finishes and civic compute never joins the NSX fabric. Fixing reachability restores the install truck's route to the depot. A Distributed Firewall allow for the permit-desk web VIP fails by concept because an application VIP allow does not fetch NSX VIBs or repair Manager-to-host prep connectivity. Identity Firewall AD group membership for clerks fails by concept because IDFW user mapping is unrelated to transport-node VIB installation. Carbon Black Cloud sensor policy on the host fails by concept because CBC sensor policy does not deliver NSX VIBs or complete host preparation. Exam caveat: stuck transport-node install means management and depot reachability first—not DFW app VIP, IDFW groups, or Carbon Black policy. Operational check: from the host, verify reachability to NSX Manager and the VIB depot, fix routing or firewall on the management path, retry host prep, confirm transport-node success, and record the management ACL change in the county NSX commissioning log for civic fabric governance.