_images/openl2m_logo.png

Switch Requirements

Juniper PyEZ

  • any Juniper device that supports the XML api, via the PyEZ library. Device access needs to be configured properly.

Aruba AOS-CX

  • any device that supports the Aruba AOS-CX API v10.08 is supported, via the pyaoscx library. Device access needs to be configured properly.

SNMP

For the device that use standard SNMP OpenL2M supports v2c and v3. SNMP v1 is not supported. We recommend all devices are configured with v3.

OpenL2M uses the following standard and vendor MIBs to learn and be able to manage the interfaces of a device:

Standard MIBs

Vendor Specific MIBs

Several vendor specific MIB are supported at this time.

  • Cisco VTP MIB Used for VLAN information on Cisco Switches.

  • Cisco Extended PoE MIB Get enhanced PoE info on the switches that support it.

  • Cisco Stacking MIB For stack member info, if supported.

  • Cisco L2L3-INTERFACE-CONFIG MIB Used to see if interface is in switching or routing mode on Cisco devices.

  • Cisco Syslog-Mib Used to read log messages from Cisco devices (if configured).

  • HP Aruba/Procure HP-ICF-POE-MIB Get enhanced PoE info on the Aruba/Procurve switches that support it.

  • HP HP-ENTITY-POWER MIB Old power mib, supported by some Aruba/Procurve switches to get enhanced PoE info.

  • HP HPN-ICF-IF-EXT MIB Interface extension to get switching or routing mode on HP devices.

  • HPE HH3C-PoE MIB Get enhanced PoE info on the Comware switches that support it.

  • HPE HH3C-LswINF MIB Used for additional layer 2 interface information in HPE Comware switches.

  • HPE HH3C-LswVLAN MIB Used for additional VLAN data in HPE Comware switches.

  • HPE HH3C-IF-EXT MIB Used for additional information about interfaces in HPE Comware switches (route mode, PoE capable).

  • HPE HH3C-Config-Man MIB Used to save running configuration on HPE Comware switches.

  • Juniper Networks L2ALD MIB Used for vendor-specific vlan information.

Napalm

Any device supported by the Napalm library is supported in Read-Only mode.