Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.8072.3.2.10 | ESX Server | 3.5, 4.0, 4.1, 5.0 |
Password Rules might not function properly for VMware devices managed by the system. It is recommended that device-specific passwords be used with all VMware devices.
ESX(i) hosts that are discovered as child devices of vCenter Servers will have the same usernames and passwords as those for the vCenter Servers. Due to an issue with Password Rules and VMware devices, you might have to manually change the usernames and passwords of the ESX(i) hosts before a successful snapshot can be taken.
This driver detects both guest VMs and virtual switches. To disable detection of VMs, set the device access variable "disable_context_vm" to "true". To disable the detection of all context devices [both VMs and Virtual Switches], set the device access variable "disable_context" to "true".
Scripting to a vSwitch is done via direct API calls to the containing ESX server. As a result, there is no way to prevent scripts from modifying ESX server settings outside those that pertain to the vSwitch. Note that this is true even in cases where MSP permissions are being granted to the vSwitch, but not the containing ESX server.
Snapshots are performed via the VMware VI SDK API version 2.5
NA uses default http/https port assignments. VMWare ESX servers can be configured to use non-standard http/https ports to connect to VMWare ESX servers so as to complete snapshots. Workaround: The "https_port" device access variable has been created to enable users to modify the ports NA uses to communicate to VMWare ESX servers so as to complete snapshots.
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.