Transit has NSX-T on the cluster, but fare-system guests still run an old VMware Tools build that never installed Guest Introspection drivers. What should the administrator do?
Select an answer to reveal the explanation.
Short Explanation
NSX on the host is not the same as the thin agent in the guest. Old Tools without the introspection drivers are just a mute intercom. Upgrade Tools and include those GI components.
Full Explanation
Transit fare-system guests on an NSX-T cluster still need current VMware Tools that include Guest Introspection drivers. Upgrade VMware Tools and include the Guest Introspection components; host NSX preparation does not implant thin-agent drivers into old Tools builds.
Reinstalling NSX Manager while leaving the existing Tools build unchanged does not fix guest drivers. Enabling Identity Firewall on the cluster only does not make Tools version irrelevant to GI. Deploying a Carbon Black sensor does not install the missing Tools GI driver.
Exam caveat: cluster NSX ≠ guest thin agent—upgrade Tools with GI components on the guests themselves.
Operational check: upgrade Tools with GI on a fare guest, verify GI status, retest IDFW or introspection features, and schedule Tools upgrades across the fare fleet.
Tools upgrades on fare guests close the mute intercom between NSX and the VM. Schedule Tools+GI maintenance beside NSX upgrades, verify a canary host of guests, then roll forward so IDFW features are not promised on obsolete Tools builds. Keep a canary Tools+GI upgrade report for fare guests with the maintenance record so the next on-call engineer can separate host NSX health from mute guest drivers without rediscovering that split under pressure.