Driver Support Document
| SYSOID Mapping | ||
| SYSOID | MODEL | OS VERSION |
| 1.3.6.1.4.1.30065.1.3011.7010.427.48 | 7010T-48 | 4.14.2F |
| 1.3.6.1.4.1.30065.1.3011.7048.427.3648 | 7048T-A | 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7050.427.36 | 7050T-36 | 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7050.427.52 | 7050T-52 | 4.6.2, 4.8.2, 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7050.427.64 | 7050T-64 | 4.8.2, 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7050.1958.64 | 7050TX-64 | 4.15.2F |
| 1.3.6.1.4.1.30065.1.3011.7050.1958.72.2512 | 7050TX-72Q | 4.15.5M |
| 1.3.6.1.4.1.30065.1.3011.7050.1958.128.761 | 7050TX-128-SSD | 4.16.6M |
| 1.3.6.1.4.1.30065.1.3011.7050.2512.16 | 7050Q-16 | 4.8.2, 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7050.3095.2.32.3282 | 7050QX2-32S | 4.16.6 |
| 1.3.6.1.4.1.30065.1.3011.7050.3095.32 | 7050QX-32-R | 4.12.4 |
| 1.3.6.1.4.1.30065.1.3011.7050.3095.32.3282 | 7050QX-32S | 4.14.2F |
| 1.3.6.1.4.1.30065.1.3011.7050.3282 | 7148S-F | 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7050.3282.52 | 7050S-52 | 4.6.2, 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7050.3282.64 | 7050S-64 | 4.6.2, 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7050.3282.64.761 | 7050S-64-SSD-F | 4.10.4 |
| 1.3.6.1.4.1.30065.1.3011.7050.3741.64 | 7050SX-64 | 4.14.6 |
| 1.3.6.1.4.1.30065.1.3011.7050.3741.72.2512 | 7050SX-72Q | 4.15.3FX |
| 1.3.6.1.4.1.30065.1.3011.7050.3741.128 | 7050SX-128 | 4.13.1 |
| 1.3.6.1.4.1.30065.1.3011.7060.2733.32.3282 | 7060CX-32S | 4.15.3 |
| 1.3.6.1.4.1.30065.1.3011.7124.3741 | 7124SX | 4.6.1 |
| 1.3.6.1.4.1.30065.1.3011.7148.3282 | 7148S | 4.2.0 |
| 1.3.6.1.4.1.30065.1.3011.7148.3741 | 7148SX | 4.4.3, 4.5.1, 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7150.3282.24 | 7150S-24 | 4.10 |
| ` 1.3.6.1.4.1.30065.1.3011.7150.3282.24.2745.761 | 7150S-24-CL-SSD | 4.13.0 |
| 1.3.6.1.4.1.30065.1.3011.7150.3282.52.2745 | 7150S-52-CL | 4.11.0 |
| 1.3.6.1.4.1.30065.1.3011.7150.3282.64.2745 | 7150S-64-CL | 4.11.1 |
| 1.3.6.1.4.1.30065.1.3011.7150.3282.64.2745.761 | 7150S-64-CL-SSD | 4.13.8 |
| 1.3.6.1.4.1.30065.1.3011.7280.1964.48.2878.6 | 7280TR-48C6 | 4.17.1F |
| 1.3.6.1.4.1.30065.1.3011.7280.2727.48 | 7280CR-48 | 4.18.0F |
| 1.3.6.1.4.1.30065.1.3011.7280.3101.2878.36 | 7280QR-C36 | 4.16.6 |
| 1.3.6.1.4.1.30065.1.3011.7280.3714.64 | 7280SE-64 | 4.14.2 |
| 1.3.6.1.4.1.30065.1.3011.7280.3714.68 | 7280SE-68 | 4.14.2 |
| 1.3.6.1.4.1.30065.1.3011.7280.3714.72 | 7280SE-72 | 4.14.3F |
| 1.3.6.1.4.1.30065.1.3011.7280.3735.48.2878.6 | 7280SR-48C6 | 4.17.2F |
| 1.3.6.1.4.1.30065.1.3011.7280.3735.48.2878.6.972 | 7280SR-48C6-M | 4.17.2F |
| 1.3.6.1.4.1.30065.1.3011.7504 | 7504 | 4.6.1, 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7504.1359 | 7504N | 4.17.1.1F |
| 1.3.6.1.4.1.30065.1.3011.7508 | 7508 | 4.6.1, 4.9.5 |
| 1.3.6.1.4.1.30065.1.3011.7508.1359 | 7508N | 4.17.1.1F |
| 1.3.6.1.4.1.30065.1.3011.7512.1359 | 7512N | 4.17.3F |
Arista devices support a 'show running-config all' command that includes all default settings in the returned configuration. To retrieve this configuration, set the device access variable "showConfigAll" to "true". Note that the startup configuration and transport protocols do not support this argument, only the CLI running configuration will be altered, which can cause NA to show a difference between the startup and running configuration.
The Arista series of switches support named routing contexts. To use a non-default vrf, set the device access variable "vrf" to contain the VRF name.
Only images ending with .swi extension (Arista default extension for OS images), will be set as boot. Internal verification will run against the image, and if fails image will not be set.
During scp upload unknown error can occur. That is caused either by timeout, or by wrong access. Please make sure that the user account has enable privileges, and that only one name server is configured.
The SNMP RW community strings, are not supported by all Arista devices. Before adding RW community, verify that it is supported by the device, otherwise the task may fail.
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.