R12.1-JA-2025June05

Multi-Vendor Support List (SDN)

The table below describes the SDN (including SD-WAN) device types and vendors supported in the system:

TechnologyDevice Type Supported LevelDiscovered via
Tier 1Tier 2Tier 3
SDN-WANCloudGenix ION SD-WAN√√ CLI/API
VeloCloud Edge√√ SNMP/CLI
VeloCloud Gateway√√ SNMP/CLI
VeloCloud Orchestrator√  SNMP
Versa Analytics√√ CLI
Versa Controller√√ API
Versa Director√√ CLI
Versa FlexVNF√√ API
Viptela vBond√√ API
Viptela vEdge√√ SNMP/CLI
Viptela vManage√√ API
Viptela vSmart√√ API
 Cisco Meraki Z3 √ API
 Cisco MX  √ API
 Aryaka router√√ SNMP
Cisco ACICisco ACI APIC√√ API
Cisco ACI Leaf Switch√√ API
Cisco ACI Spine Switch√√ API
EXSiVM Host√√ API
vSphere Distributed Switch√√ API
vSphere Standard Switch√√ API
VM NSX-V (for vSphere)NSX Manager√√ API
NSX Controller√√ API
NSX Logical Switch√√ API
NSX Edge Security Gateway√√ API
NSX Distributed Logical Router√√ API
AVIAVI Controller√  API
AVI Service Engine√  API
Big Switch Big Switch Controller√√ SNMP/CLI/API
Big Switch Spine Switch √ API
 Big Switch Leaf Switch √ API

 

The limitations of SDN support include the following:

      • Cisco ACI
        • Remote Leaf is not supported.
        • Cannot map out EoMPLS devices between Transit Leaf and Spine for Stretched Fabric deployment that uses EoMPLS to interconnect Transit Leaf and Spine.
        • Running Qapps on logic nodes (like Tenant, VRF, EPG, etc.) is not supported.
      • NSX-V
        • Overlay L2 topology and underlay paths are not supported.
      • Big Switch
        • Only support spine/leaf switches' L2 link(NDP) table. Other data is retrieved from the controller as NCT tables.
      • Cisco Meraki Z3 and MX
        • SD-WAN routing table is populated by NetworkBrain's algorithm but not exported by API.
        • The netmask of some interfaces cannot be accurately retrieved by API. However,  the netmask of the VLAN interface can be retrieved by API.

 

Multi-Vendor Support List OUI Information