Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.89.1.1.62.6 | FireProof AS1 | 3.21.08 |
| 1.3.6.1.4.1.89.1.1.62.18 | CID OnDemand Switch | 3.11.00 |
For Radware Fireproof devices, the configuration file sent through TFTP can be encrypted. As a result, NAS will skip to CLI-only configuration retrieval. It is recommended that you modify the TFTP file-type to CLI.
For example: manage tftp file-type set 1 (where: "file-type" can be one of the following values: cli or ber)
After a software upgrade, Radware Fireproof devices require an activation password to boot the new software image. Because the password is unique for each device, the Update Device Software task has been disabled
For NAS to support an SNMP community string on Radware Fireproof devices, the View name for the access groups to which a particular SNMP community string is assigned must be the same regardless of the SNMP security model (SNMP v1 or SNMP v2).
For example:
where: The groups are group-ro and group-rw.
manage snmp access create ro_group SNMPv1 noAuthNoPriv -rvn ReadOnlyView
manage snmp access create ro_group SNMPv2c noAuthNoPriv -rvn ReadOnlyView
manage snmp access create rw_group SNMPv1 noAuthNoPriv -rvn ReadOnlyView -wvn ReadWriteView
manage snmp access create rw_group SNMPv2c noAuthNoPriv -rvn ReadOnlyView -wvn ReadWriteView
To create read/write SNMP community strings on Radware Fireproof devices, you can overwrite default values using Device Access Settings.
For example:
snmp_read_view - the name of the view (for read and write access). If not specified, the value "ReadOnlyView" is used.
snmp_write_view - the name of the view (for read and write access). If not specified, the value "ReadWriteView" is used.
snmp_read_group - the name of the read only group. If not specified, the value "ro_group" is used.
snmp_write_group - the name of the read/write group. If not specified, the value "rw_group" is used.
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.