NetVisor UNUM Deployment Scenarios


NetVisor UNUM  is generally deployed in one of two ways:


NetVisor UNUM managing an entire NetVisor OS fabric

NetVisor UNUM managing NetVisor OS switches attached to third-party spines


NetVisor UNUM Managing a NetVisor OS Fabric


In this greenfield scenario, all switches in the leaf-spine fabric are running NetVisor OS and NetVisor UNUM communicates with each node over a management network or data network. 


NetVisor UNUM manages the fabric, collects telemetry and analyzes data for the entire fabric.  


One of the switches, chosen at the time of fabric creation, is designated a “Collector” and acts as the point of communication for the fabric. 



NetVisor UNUM NetVisor OS Fabric


NetVisor UNUM Managing NetVisor OS Switches Attached to Third-Party Spines


In this brownfield configuration, customers have existing, third-party spines in a spine-leaf topology, and only the leaf switches are running NetVisor OS.


NetVisor UNUM  manages, collects telemetry and analyzes data for the leaf switches. 


A “Collector” is still chosen at fabric creation to enable Fabric Management and Insight Analytics of the NetVisor OS switches.


NetVisor UNUM Fabric with Third-Party Spines

north
    keyboard_arrow_up
    keyboard_arrow_down
    description
    print
    feedback
    support
    business
    rss_feed
    south