Multi-Vendor Environment icon

Service Orchestration in a Multi-Vendor Environment

The recent separation of network appliances into hardware and software components, and a deployed mix of open-source and commercial software components requires a management platform that is flexible and open, able to adapt to the vendor multiplicity, as well as the various domains. The MSActivator cuts CapEx and OpEx costs in multi-vendor, multi-domain environments drastically.

Sample Service Orchestration Implementation

Service Orchestration


The networking and security industry has become more and more complex. Service Providers and Enterprises are facing a multi-vendor management nightmare. Using vendor-specific NMS to manage device configurations, the resulting silos add complexity and increase operating expenses. Additional solutions for monitoring and troubleshooting cause yet more convolution in network management.

The industry has previously attempted to solve the multi-vendor management problem with standards like SNMP, or more recently with netconf/yang. Most, if not all, of these initiatives failed poorly.

Vendors want to remain independent. They will never agree on a common language or data model that will allow businesses to simply switch from vendor A to vendor B. Not all the vendors are yang compatible, for example. This is particularly true for security vendors or network edge vendors. Additionally, Netconf/yang compatible vendors can publish different data models, which means that even in 100% netconf/yang environment, conversion is still needed.

The only solution to the multi-vendor management nightmare is vendor-specific language abstraction.

Why the MSActivator™?

The MSActivator™ uses an agile abstraction approach, which is what makes multi-vendor management possible. The OBMF abstraction engine enables the setup of microservices to configure any features exposed by the vendors. The OBMF microservices perform the conversion to the vendor-specific language (CLI, API, Netconf, etc.), and expose unified API which simplify service and network automation. A network operator now only focuses on designing workflows without having to worry about the vendors used southbound.

OBMF microservices also provide the needed abstraction layer that ease the onboarding of any new vendor in DevOps mode. By stitching together generic microservices into workflows, the MSActivator™ eliminates the lack of alignment between service orchestration and device configuration. The MSActivator™ also collapses assurance and fulfillment layers into one framework, while adding Big data analytics. This offers Service Providers and Enterprises a cost-effective, full-service lifecycle management tool, regardless of the underlying vendor.


The MSActivator™ makes automation easy for both Service Providers and Enterprises

  • msp-blue

    MSActivator™ for Service Providers

    Replace your legacy, rigid and costly OSS stack with an agile, devops enabled, service orchestration solution fit for your SDN/NVF migration.

    Learn More >
  • me-blue

    MSActivator™ for Enterprises

    Solve the multi-vendor and hybrid network and security management problems exacerbated by the insertion of SDN and virtualization.

    Learn More >