Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.164.6.1.12.3.8 | radAce3200 | 5.0.2 |
| 1.3.6.1.4.1.164.6.1.12.3.16 | radAce3600 | 5.0.2 |
Currently, enabling RADIUS authentication on the device is not supported by the driver and will lead to task failures.
Certain tasks, including the Update Device Software task, are likely to fail when NA is configured to use SSH as a connection method.
The textual configuration contains information captured from the screen menus of the device, but does not include all of the sub-menus and configuration options of the device. Due to the large number of interface types and ports, by default, the driver captures only the configuration of the first two interfaces of each type.
You can modify this settings using a custom access variable named maxNrInterfaces. The maxNrInterfaces value represents the maximum number of interfaces, regardless of their type, that will be captured and stored in the snapshot and in the Interface diagnostic.
1. Login to NA.
2. From the Device Details page, select the Edit & Provision menu option and click Edit Device.
3. On the Edit Device page, scroll down to the Device Access Settings field.
4. Enter a new value for the maxNrInterfaces variable.
5. Click the Save button.
In addition, there may appear differences between configurations captured by NA via different access protocols (telnet and ssh).
The Rad Ace 3200 and 3600 devices do not have any command or menu screen from where to extract the amount of total memory. However, the amount of free memory is displayed by the devices. As result, the Total Memory was arbitrary set to the default shipment value, as indicated by the vendor.
Rad Ace 3200 and 3600 devices are menu mode, therefore sequence of commands have to be entered through their corresponding numerical value from the menu. Also, the result of the commands is represented by the output device screen as displayed by the device immediately after entering the command. Some special unprintable characters may appear in the output.
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.