Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Related Documentation


    Junos Space Fabric Architecture

    To support the rapid growth in network size, Junos Space is designed to be highly scalable. You can cluster multiple Junos Space appliances to create a single management fabric, which is accessible from a single virtual IP (VIP) address.

    All graphical user interface (GUI) and northbound interface (NBI) clients use the Junos Space VIP address to connect to the Junos Space fabric. The fabric incorporates a front-end load balancer that distributes client sessions across all the active Junos Space nodes within the fabric. You can increase or decrease the fabric by simply adding or deleting nodes to or from the Junos Space Network Management Platform user interface, and the Junos Space system automatically starts applications and services on the active nodes. Each node in the cluster is fully utilized and all nodes work together to provide automated resource management and service availability.

    Tested with up to six appliances connected in a cluster (fabric), the JA1500 Junos Space Appliance has the proven ability to manage up to 15,000 devices without the Network Monitoring functionality enabled and can support up to 30 concurrent login sessions. Tested with up to eight appliances (four Junos Space nodes, two database nodes, and two fault monitoring and performance monitoring [FMPM] nodes) connected in a cluster (fabric), the JA2500 Junos Space Appliance has the proven ability to manage up to 25,000 devices with up to 100 concurrent login sessions.

    In addition, a Junos Space fabric architecture comprising multiple appliances eliminates any single point of failure. When a node in the fabric goes down, all client sessions and device connections currently served by that node are automatically migrated to the active nodes in the fabric without any user-initiated action.


    Related Documentation


    Modified: 2016-11-28