Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.6527.1.3.1 | 7750 SR-1 | 7.x, 8.0 |
| 1.3.6.1.4.1.6527.1.3.2 | 7750 SR-4 | 7.x, 8.0 |
| 1.3.6.1.4.1.6527.1.3.3 | 7750 SR-12 | 5.0, 9.0.R9 |
| 1.3.6.1.4.1.6527.1.3.4 | 7750 SR-7 | 8.0, 12.0.R3, 15.0.R4 |
| 1.3.6.1.4.1.6527.1.3.5 | 7750SR-6 | 7.x, 8.0 |
| 1.3.6.1.4.1.6527.1.3.6 | SR7750 | 8.0, 13.0.R4 |
| 1.3.6.1.4.1.6527.1.3.8 | Nokia SR7750 | 14.0.R6 |
| 1.3.6.1.4.1.6527.1.3.10 | Nokia SR7750 | 14.0.R5 |
| 1.3.6.1.4.1.6527.1.3.12 | Nokia SR7750 | 14.0.R5 |
| 1.3.6.1.4.1.6527.1.6.3 | 7450 | 5.0 |
| 1.3.6.1.4.1.6527.1.9.1 | SR7710SR-c12 | 7.x, 8.0 |
| 1.3.6.1.4.1.6527.1.9.2 | SR7710 | 8.0 |
| 1.3.6.1.4.1.6527.1.15.1 | 7950 | 11.0R4 |
| 1.3.6.1.4.1.6527.1.18.1 | NUAGE 7850 | 4.0.5-60 |
| 1.3.6.1.4.1.6527.6.1.1.2.1 | 7705S | 4.0, 6.1 |
| 1.3.6.1.4.1.6527.6.1.1.2.2 | 7705S-F | 3.x, 4.0 |
| 1.3.6.1.4.1.6527.6.1.1.2.11 | 7705 | 6.1.R2 |
| 1.3.6.1.4.1.6527.6.2.1.2.2.2 | 7210 | 4.0 |
| 1.3.6.1.4.1.6527.6.2.1.2.2.3 | 7210 | 4.0 |
| 1.3.6.1.4.1.6527.6.2.1.2.4.2 | SAS-D | 6.0.R6 |
The Alcatel devices have multiple command 'states' which can use different prompts than the standard enable prompt and config prompt. Use of commands that leave the device in another state [such as "system" or "router"] are not supported in the execution of scripts. It is suggested that one use the full multi-command line to not end up in this state, e.g. "system location 'test'".
Alcatel devices supported by this driver typically omit default settings from the configuration. To include default settings in the configuration, set the device access variable "showConfigAll" to "true". Note that including the extra default information could have some adverse effect on performance, given that there is much more data to be collected, cleaned up, and parsed.
The Alcatel 7450/7750 do not support config deployment as such, but do support execution of script files. Configuration deployment is implemented as an exec of the configuration block provided and acts as a merge, rather than a copy operation.
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.