You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enabling CDP on the pnic displays some references which can be used to cable vhosts to switches, also can be used to add neighbour devices directly to netbox.
devId/systemName is the device name of the connected switch - which should be existing already or can be created by the script. linking the pnic with a cable to the portId of the given systemName would be awesome.
Enabling CDP on the pnic displays some references which can be used to cable vhosts to switches, also can be used to add neighbour devices directly to netbox.
You can get the PhysicalNicCdpInfo info with QueryNetworkHint when quering the hostSystem -> configManager-> networkSystem and using the method queryNetworkHint (vmnicXX as parameter or empty) on the returned networkSystem. This will return a PhysicalNicHintInfo with a PhysicalNicCdpInfo below connectedSwitchPort.
Took me a while to find out. Hidden like the most secret information on earth.
The returned PhysicalNicCdpInfo can be used to import network devices and cables to the vhost automatically, if cdp is enabled.
I would suggest that this feature needs to be opt-in, if the infrastructure below the vcenter has cdp enabled through all devices.
The text was updated successfully, but these errors were encountered: