Configuring and Administering the Pluribus Fabric > Understanding the Netvisor® ONE Adaptive Cloud Fabric™
Was this helpful?
Understanding the Netvisor® ONE Adaptive Cloud Fabric™
In a Pluribus fabric, every node acts as a virtual module within a logically-unified physically-distributed virtual chassis abstracting the network topology. Each fabric node shares a common view of the network, including MAC and IP addresses, connections and application flows for management, as well as redundancy purposes.
In addition, due to advanced embedded telemetry technology, the Netvisor® ONE software provides fabric-wide traffic visibility to reveal network congestion issues and application performance bottlenecks to speed up troubleshooting, improve operational efficiency, and strengthen security.
The Pluribus Adaptive Cloud Fabric is a distributed application on top of a standard Layer 2 or Layer 3 network unifying the management plane for all the switches of the fabric and at the same time enhances the network control plane with the ability to automate and simplify network functions.
Figure 5- 1:  Adaptive Cloud Fabric Simplified Management with Single IP to Configure and Monitor the Fabric
A fully symmetrical, peer to peer, distributed control plane enables any node to act as a single point of management for the entire fabric. The Netvisor ONE does not require a single controller entity to guarantee the proper operation of the network.
Informational Note:The Adaptive Cloud Fabric supports any network topology, including ring, leaf-spine, and multi-site.
Netvisor ONE overcomes the intrinsic limits of a centralized control plane SDN architecture, such as split brain problems, whereas it interoperates with a centralized orchestration system controller through RESTful APIs or an OVSDB interface. This enables additional powerful management strategies when leveraging popular platforms such as Ansible or OpenDaylight.
Adaptive Cloud Fabric uses an advanced transactional model to guarantee consistent device configuration across fabric nodes and supports rollback capabilities. Therefore, a single point of provisioning provides fabric-wide configuration with commands operating on a list of dispersed fabric devices, instead of on individual ones.
Since Adaptive Cloud Fabric does not require special controllers to operate, and since it leverages standard protocols, instead of proprietary technologies, Netvisor ONE enhances the interoperability with devices from other vendors.
Figure 5- 2:  Network Orchestration with Adaptive Cloud Fabric
Adaptive Cloud Fabric open architecture provides users with a degree of interoperability compared to centralized SDN architecture. While at the same time, providing support for powerful market-leading network-wide analytics.
Each node belongs to only one fabric and multiple fabric domains can be part of the same network, so you can implement more granular management domain segregation.
For example, in a typical leaf and spine data center configuration, network administrators often prefer to provision one management domain for all leaf switches and one separate domain for all spine switches, so as to preserve homogeneity as well as provisioning and monitoring simplicity within each functional domain.
Figure 5- 3 depicts an example of data center pod topology comprising two management domains corresponding to two separate fabric instances: one for all leaf switches and one for two spine switches.
Figure 5- 3:  Two Fabric Instances to Achieve Two Management Domains
The Adaptive Cloud Fabric technology offers additional benefits including more granular management segmentation for multi-tenancy, geographically dispersed data center interconnection (DCI), and sophisticated security as well as other benefits.