Driver Support Document
SYSOID Mapping | ||
SYSOID | MODEL | OS VERSION |
1.3.6.1.4.1.3417.1.1.23 | SG8000 | SGOS 5.4.1.12 |
1.3.6.1.4.1.3417.1.1.25 | SG810 | SGOS 5.4.1.12 |
1.3.6.1.4.1.3417.1.1.26 | SG210 | SGOS 4.3.5.1, 5.3.2.1, 6.1.6.1 |
1.3.6.1.4.1.3417.1.1.27 | SG510 | SGOS 5.4.3.3 |
1.3.6.1.4.1.3417.1.1.29 | SG9000 | SGOS 5.4.3.3 |
1.3.6.1.4.1.3417.1.1.31 | SG600 | SGOS 6.5.6.1 |
1.3.6.1.4.1.3417.1.1.32 | SG300 | SGOS 6.5.4.1 |
1.3.6.1.4.1.3417.1.1.34 | SG900 | SGOS 5.5.7.1 |
1.3.6.1.4.1.3417.1.1.37 | SG-400-30 | SGOS 6.5.9.9 |
1.3.6.1.4.1.3417.1.1.38 | SG-S200-20 | SGOS 6.5.8.2 |
1.3.6.1.4.1.3417.1.6.2 | ASG-S400 | ASG 6.6.5.8 |
Several tasks require a presence of at least one identical SNMP read community string on the device and an NA device password rule. Leave at least one SNMP read community string in deploy password task, which is identical with SNMP read community string on the device.
By default, the BlueCoat driver captures the expanded configuration using the command 'show config expanded noprompts'. If the brief configuration is sufficient, it can be captured using the command 'show config brief noprompts' instead. To select this option, setthe device access variable "brief_config" to "true".
Using read-only administrator the driver will initially try to capture configuration via CLI, in case of failure it will try HTTPS. To change capture configuration order to HTTPS and then CLI, set the device access variable "http_cli" to "true".
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.