_images/openl2m_logo.png

Supported Devices

OpenL2M supports a number of different drivers. Each drivers support a different method to communicate with the network device (typically a switch). Below are a list of devices the various drivers have been tested against.

Notes on Drivers

  • SNMP - OpenL2M supports network devices that implement the relevant, standard IETF MIBs. Many vendors stray away from these standards to either implement their own vendor-proprietary MIBs, or not support the standard MIBs as intended.

  • AOS-CX - this uses the ‘pyaoscx’ library provided by HPE. Any AOS-CX device properly configured, and running current firmware, should be supported.

  • Arista eAPI - this is fast driver using the Arista REST api (aka. eAPI). All features, except PoE, are supported. (Note that we don’t have a PoE-capable device to develop and test against.)

  • Juniper JunOS - this uses the ‘PyEZ’ library provided by Juniper. Most Juniper devices properly configured, and running current firmware, should be supported, barring device-specific interface names, etc.

  • Napalm - the Napalm driver is read-only, and should support any device supported by the Napalm library.

Switches Tested

The following devices (in alphabetical order), are likely supported by OpenL2M.

While an attempt has been made to verify all functionality, we strongly encourage you to test your devices before using them “in production” with OpenL2M. Also see the terms of the GPL v3 license!

For SNMP devices, an attempt has been made to make OpenL2M adhere to ‘IETF standard’ SNMP. However, we recognize there is no such thing as completely ‘standard’ SNMP.

We have tested OpenL2M on the following hardware, with the listed limitations.

Arista

  • Any Arista switch via SNMP, as they all support the same MIBs. Tested on 7050SX3 and 7280CR3 series. PoE may function, but is untested!

  • The Arista eAPI is also supported. Tested on 7050SX3 and 7280CR3. PoE is not support, as we don’t have a PoE-capable device to develop and test against.

Cisco

Via SNMP.

  • Catalyst 2960 series; single and stacked units.

  • Catalyst 4500-E series, with Sup6L-E and Sup7L-E.

  • CBS series, withouth PoE. Tested on CBS350-8T-E-2G

HP/Aruba (ProCurve/ArubaOS)

Via SNMP:

  • HP 1920 series; single units.

  • HP 2520 series; single units.

  • HP 2530 series; single units.

  • HP 2810 series, single units.

  • HP 4200 series, specifically 4204vl (J8770A).

  • Aruba 2530 series; single units.

  • Aruba 2540 series; single units.

  • Aruba 2930F/M series; single units.

  • Aruba 5400 series; chassis based, regular, zl, and zl2.

Via REST api:

Any device that can run v16.x of AOS-S, and has the REST api enabled (see configuration page). We recommend firmware v16.11.0029 or newer. This was tested on:

  • 2930F JL693A (WC.16.11.0029 firmware)

  • 2930M JL319A (WC.16.11.0029 firmware)

  • 2940 JL357A (YC.16.11.0029 firmware)

Aruba AOS-CX

Via AOS-CX driver, and nearly full via SNMP.

  • Aruba CX 6000 series; single units. (R/W support via the REST API v10.08)

  • Aruba CX 6100 series; single units. (R/W support via the REST API v10.08)

  • Aruba CX 6300 series; single units. (R/W support via the REST API v10.08)

HP Enterprise (HPE)

Via SNMP:

  • HPE 1950 series switches, running Comware 7; single and IRF-stacked units.

  • HPE J3400CL-24G (J4905A)

  • HPE 5120v3 series switches, running Comware 7; single units.

  • HPE 5130EI series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5140EI series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5150EI series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5500 series switches, running Comware 5; single units.

  • HPE 5510HI series switches, running Comware 7; single units.

  • HPE 5550HI series switches, running Comware 9; single units.

  • HPE 5600HI series switches, running Comware 7; single units.

  • HPE 5900AF series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5930 series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5940 series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5945 series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5950 series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5960 series switches, running Comware 9; single units.

Via REST API:

  • HPE 5130EI series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5140EI series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5150EI series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5940 series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5945 series switches, running Comware 7; single and IRF-Stacked units.

  • HPE 5960 series switches, running Comware 9; single units.

Juniper Networks

Full with Junos PyEZ, R/O support with SNMP.

  • EX2300 series switch, running JUNOS 18.2R3-S2.9; single unit.

  • QFX5120 series switch, running JUNOS 20.4R3-S3.4; single unit.

  • SRX series firewalls, with “Commands-Only” configurations to run command-templates.

MikroTik

Via SNMP.

  • Only one MikroTik device has been tested: HexS (RB760iGS). Limited functionality, as MikroTik does not supports VLANs, LLDP, and more via SNMP.

Netgear

Via SNMP.

  • Only one current Netgear device has been tested: M4250 series.

Generic

Several generic snmp implementations on ‘home wireless routers’ and ‘commodity’ switches have been tested, with varying results, depending on the level of SNMP support in the devices.

Napalm devices

Any device supported by the python Napalm library, in read-only mode. Note this was implemented primarily as an example of the Connector() API. See source code for more.

SSH/Command-Only devices

Any device supported by the python Netmiko library. Devices configured as such do NOT poll interfaces, but only allow for commands to be executed on the device.