Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| NSX Manager | 6.x | |
The configuration of VMWare NSX is coordinated throuh the NSX Manager nodes. Other elements NSX Controllers, NSX Edges are managed by this driver, but should not be directly imported as devices. To manage an NSX environment in NA, add the NSX Manager as a device. After the Module Status diagnostic is run, associated devices like NSX Controllers, NSX Edges, Logical Switches and Logical Routers will be discovered the child devices and assigned as devices that will also be managed by this driver. All the diagnostic tasks will run only on the NSX Manager device directly. There is no provision to run any task directly on the controller devices currently.
This driver detects associated elements of NSX Manager as devices. To disable detection of these elements, set the device access variable "disable_context" to "true". This feature is enabled by default.
Scripting on the VMWare NSX is implemented with four scripting modes.
Script Mode Subject Device Result VMware NSX enable NSX Manager Commands are run in the NSX's enable mode VMware NSX config NSX Manager Commands are run in the NSX's configuration mode VMware NSX exec NSX Manager Commands are run in the NSX's exec mode VMware NSX REST NSX Manager API calls to be made from NSX Manager in all modes (POST/GET/DELETE/PUT)
Discovery tasks for Javascript drivers handle More prompts by using timeouts, which can cause problems with the third-party SSH client code, which interprets the timeout as a disconnection. There are two options to work around the problem. Setting the RCX option [<option name="Driver/Discovery/UsePollRead">true</option>] in site_options.rcx will effect the workaround for all affected devices. Alternatively, it could be applied to a single device by setting the device access variable "PollRead" to "true".
Discovery tasks for Javascript drivers use wakeup characters are sent during device connection, to ensure that the device is responding. Normally, these characters do not echo to the console, but some devices may echo them. In this case, this causes the prompt detection phase to fail, which in turn can cause More prompts to not be handled properly, and discovery may fail. If these characters are echoed from the device [check the session log to see this], then set the device access variable "skip_ctrl_u" to skip the sending of the wakeup characters. Note that setting this option on a previously working device could cause discovery tasks to fail, but it only affects CLI discovery. SNMP discovery is unaffected.