Multi-Vendor Support List （SDN)

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

Technology

Device Type

Supported Level

Discovered via

Tier 1

Tier 2

Tier 3

SDN-WAN

CloudGenix 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 ACI

Cisco ACI APIC

√

√

 

API

Cisco ACI Leaf Switch

√

√

 

API

Cisco ACI Spine Switch

√

√

 

API

EXSi

VM 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

AVI

AVI 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 on SDN support include:

▪Cisco ACI

oRemote Leaf is not supported.

oCannot map out EoMPLS devices between Transit Leaf and Spine for Stretched Fabric deployment that uses EoMPLS to interconnect Transit Leaf and Spine.

oRunning Qapps on logic nodes (like Tenant, VRF, EPG, etc.) are not supported.

▪NSX-V

oOverlay L2 topology and underlay paths are not supported.

 

▪Big Switch

oOnly can get spine/leaf switches' L2 link(NDP) table, other data is retrieved from controller as NCT tables.

▪Cisco Meraki Z3 and MX

oSD-WAN routing table is populated by NetBrain’s algorithm, but not exported by API.

o The netmask of some interfaces couldn’t be accurately retrieved by API. However,  the netmask of the VLAN interface could be retrieved by API.