Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.9148.1.1.1 | Net-Net 4250 | 6.2.0 |
| 1.3.6.1.4.1.9148.1.1.2 | Net-Net 4500 | 6.3, 6.2, 6.1 |
| 1.3.6.1.4.1.9148.1.1.3 | Net-Net 4600 | 7.3.0 |
| 1.3.6.1.4.1.9148.1.2.1 | Net-Net 9200 | 7.1, 7.2 |
| 1.3.6.1.4.1.9148.1.3.1 | Net-Net 3800 | 6.3 |
| 1.3.6.1.4.1.9148.1.3.2 | Net-Net 3820 | 6.3.0 |
| 1.3.6.1.4.1.9148.1.4.1 | Net-Net OS | 6.3.9 |
| 1.3.6.1.4.1.9148.1.5.1 | Net-Net 6300 | 7.2.0 |
If the device access variable "execAccessOnly" is set to "true", then the driver will not attempt to enter Enable mode, but will stay in Exec mode for all tasks.
Acme devices return an XML configuration when retrieving by transport methods [SFTP, FTP], which can be used when deploying configurations back to the device. A CLI backup method is provided, in the event where transport protocols are not available, but it returns its output in a tabular format that can not be safely deployed back to the device. This causes unavoidable spurious configurations differences to be seen if NA switches is made to protocols (either by selection, or failover).
In view of the differences between CLI configuration and that obtained by transport protocols, CLI snapshot is disabled by default to prevent a configuration change of 99% which can clog resources. If CLI snapshot is desired as an option, set the access variable "allow_cli" to "true". CLI will still be used only as a last resort, but will be available.
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.