Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.2021.250.255 | 2500 | 6.3R4 |
| 1.3.6.1.4.1.12532.0.0.0 | PSA3000 | 8.1R7 |
| 1.3.6.1.4.1.12532.0.0.0 | PSA7000 | 8.1R7 |
| 1.3.6.1.4.1.12532.252.3.1 | 2500 | 6.3R4 |
| 1.3.6.1.4.1.12532.252.5.1 | 4500 | 7.1R6 |
| 1.3.6.1.4.1.12532.252.5.2 | 4500 | 7.1R6 |
| 1.3.6.1.4.1.12532.252.6.1 | 6000 | 7.0R5.1 |
| 1.3.6.1.4.1.12532.252.7.1 | 6500 | 6.5R8 |
| 1.3.6.1.4.1.12532.254.1.1 | MAG 2600 | 7.4R6 |
| 1.3.6.1.4.1.12532.254.2.1 | MAG 4610 | 8.0R6 |
| 1.3.6.1.4.1.12532.254.3.1 | MAG 6611 SM160 | 7.x |
| 1.3.6.1.4.1.12532.254.4.1 | MAG 6611 SM360 | 7.x |
| 1.3.6.1.4.1.12532.256.2.1 | PSA-3000 | 8.2R9 |
| 1.3.6.1.4.1.12532.256.3.1 | PSA-7000 | 8.2R9 |
Juniper VPNs require a 'realm' to be specified at login. By default, the first realm that contains the label "Admin" will be selected. To override this selection, set the device access variable "admin_realm" to the name of a realm present in the dropdown menu of the administor login page. If present, the realm will be used at login.
Juniper VPNs allow exporting the binary contents of large software packages as part of normal snapshot operations. This information is not essential to the device configuration, and is removed from the configuration to prevent bloat. To keep this information from the configuration, set the device access variable "showESAP" to "true".
One checkbox in the Juniper's configuration export can be particularly large; to disable the checkbox corresponding to the item "optJamClientVersions", set the device access variable "skipClientVersions" to "true".
This note applies only for drivers that use HTTP requests for driver functions. HTTP proxy operations are supported by setting the device access variable "http_proxy" to "ip:port", replacing with the IP and port values of the proxy server. SNI-requiring devices (e.g CloudGenix & Cisco Meraki) can be supported by using the device access variable "alternate_host" to contain the DNS name of the host. The host name will be used rather than the normal management IP address for all HTTP requests, effectively supporting SNI.
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.