Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| N/A | Airwave | 7.4.7, 8.x |
This driver collects a configuration piece from the Airwave's REST interface [URL: /api/amp_config] and will login to the REST interface using the normally provided credentials. To use a different set of credentials for HTTP login as for the rest of the task, set the device access variable "http_username" to the username to be used for the REST interface, and set the "enable password" credential to the password to be used.
Three options are included in the driver to gain temporary root access to the device. If the the variable 'try_sudo' is set to true, the driver will issue "sudo su - root" immediately after login. If the variable 'try_su' is set, the driver will issue "su - root" immediately after login. If the variable 'try_sudo_cmd' is set, sudo will not be run a login, but any command failing with 'permission denied' will be re-run using 'sudo [cmd]'. Not all Linux-based devices support this option.
Drivers for Linux-based devices gather their configuration in a number of separate files and the output of various commands. The driver selects a list of files deemed to be essential to the device configuration, but this list can be supplemented by use of an access variable. To add files and commands to the list gathered by the driver, set the variable "configfiles" to a comma-delimited list of items. Commands should be specified using a "@" character, and a text file containing a list of files to be gathered can be specified by a leading "#" character. For example, "/etc/nsswitch.conf, @ifconfig, #/etc/config_file_list" will add the three items to the configuration.
This driver also supports a corresponding "binconfigfiles" variable, which is used to specify binary files to be collected in snapshot. Wildcards are supported, and multiple files can be specified by using a comma-delimited list. If multiple files are specified, they will be put into a TAR-GZ container after collection. The binary configuration can not be deployed to the device, but can be downloaded from the View Configuration page through a link at the top of the page.
Some devices suppoted by this driver may have IP information that routinely changes. By setting the device access variable "ignore_ips" to "true", the IP address changes in the ifconfig and netstat commands will be ignored when comparing snapshot data.
The driver supports wildcards in the configfiles variable by using the "find" command to locate files matching a filespec on the device. Files not detected by this method are skipped during the transfer stage, to reduce the number of failed SCP connections, but this can miss files that are root-protected (if try_su/try_sudo is selected). To attempt to transfer files even if they can not be located with the FIND command, set the device access variable "ignore_file_check" 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.