Cisco NSO has the broadest multivendor support in the industry. We currently support more than 100 different device types, physical and virtual, including those listed below. These Network Element Drivers (NEDs) use legacy communication mechanisms and protocols, such as CLI, TL1, REST, etc. to communicate with the devices. These are sold at a fixed price, and there is no additional charge for incremental feature development for a productized NED.
If a device/system, e.g. Cisco ESC, supports NETCONF/YANG, and is well behaved, then a NED can be easily generated automatically, as described in the NSO user documentation. Cisco does not develop or sell such a NETCONF/YANG NED, and hence the integration is free - no integration taxation http://info.tail-f.com/noadaptertax
Here is a non-exhaustive list of NEDs for legacy protocols (i.e. not NETCONF/YANG). If you need to orchestrate devices not on this list, then we will in most cases support, either because we have the NED already, or we can very quickly (in a matter of weeks) develop the required NED. New NED types are added at a rate of around one per month.
Cisco ACI (APIC DC)
Cisco APIC EM
Cisco IOS & IOS XE
Cisco IOS XR
Palo Alto Networks Panos
Quagga BGP AOS
Telco Systems Binox
Network Element Drivers (NED) provide the connectivity between the NSO Software and Network Elements. Network Elements and their associated functionality are constantly evolving and therefore, NEDs will not support all possible devices, capabilities, or use cases. Customers may request additional NED functionality from Cisco by discussing with their Cisco Sales representative, or may choose to develop their own NEDs using documented Cisco APIs (although we would strongly discourage this as these would make the NED fall outside of our support model/contract.)