• Downloads
• Fabric Management Overview    

• Related Topics
• Managing Nodes in the Fabric
• Viewing Nodes in the Fabric

Fabric Management Overview

You can deploy Junos Space appliances to create a fabric that provides the scalability and availability that your managed network requires as you add more devices, services, and users.

A Junos Space fabric comprises one or more IP-connected nodes. A node is a logical object that represents a single Junos Space JA1500 appliance or Junos Space virtual appliance, its operating system, and the Junos Space software that runs on the operating system. Each Junos Space appliance or virtual appliance that you install and configure is represented as a single node in the fabric. You can add nodes without disrupting the services that are running on the fabric. When you add nodes to the fabric, you can manage and monitor the nodes from the Administration workspace. To add, manage, and monitor nodes in the fabric, a fabric administrator connects to a single virtual IP address. See Figure 1

Single Node Functionality

When the fabric comprises a single appliance, all devices in the managed network connect to the appliance. When you install and configure the first appliance, Junos Space automatically creates a fabric with one node. By default, a fabric that consists of a single node provides complete Junos Space management functionality. The following node functions are enabled for the node:

• Load Balancer— for processing HTTP requests from remote browsers and NBI clients
• Database— for processing database requests (create, read, update, and delete operations)
• Application Logic— for processing Junos Space service requests and Data Manipulation Language (DML) workload (device connectivity, device events, and logging)

Note: A fabric that comprises a single node provides no workload balancing and no backup if the appliance goes down.

Multinode Functionality

As your network expands with new devices, services, and users, you can add Junos Space appliances to handle the increased workload. When you install and configure the first appliance, Junos Space automatically creates a fabric with one node. For each additional appliance you install and configure, you must add a node to logically represent the appliance in the fabric. Each node that you add to the fabric increases the resource pool for the node functions to meet the scalability and availability requirements of your network. By default, Junos Space automatically enables node functionality across the nodes in the fabric to distribute workload. The nodes in the fabric work together to provide a virtualized resource pool for each of the node functions: load balancer, database, and application logic.

The Junos Space node functions distribute workload across operating nodes according to the following load-distribution rules:

• Load Balancer— When a node that functions as the active load balancer server is down, all HTTP requests are automatically routed to the standby load balancer server that is running on a separate node.
• Database— When a node that functions as the active database server is down, all database requests (create, read, update, and delete) are routed to the node that functions as the standby database server.
• Application Logic— Device connections and user requests are distributed among the nodes, and device-related operations are routed to the node to which the device is connected.

  Junos Space uses the following algorithm to ensure that the number of devices connected to a node does not exceed the threshold limit for each node:

  Threshold Limit = [ (number of devices in database) / (number of nodes running) ] + 2

The following workflow describes how the node functions are enabled across the fabric as nodes are added:

• First node: The load balancer, database, and application logic functions are enabled on the node. Each node function provides both scalability and high availability. Figure 2 shows all functions enabled on a fabric comprising one node.
  

  Figure 2: Functions Enabled on Fabric Containing One Node

  

• Second node: When a second node is added to the fabric, the first node functions as the active load balancer server and active database server, and the second node functions as the standby load balancer server and standby database server. The load balancer and application logic node functions provide scalability and high availability. The database node function on the second node provides high availability only. Figure 3 shows the functions enabled on a fabric comprising two nodes.
  

  Figure 3: Functions Enabled on Fabric Containing Two Nodes

  

• Third and subsequent nodes: Only the application logic functionality is enabled on the third node to provide equal distribution of device connections and user requests across all nodes, and to route device-related operations to the node to which the device is connected. The application logic functionality provides both scalability and high availability. Figure 4 shows the functions enabled on a fabric comprising three nodes.
  

  Figure 4: Functions Enabled on Fabric Containing Three Nodes

  

Note: For the third node and each subsequent node added to the fabric, only the application logic functionality is enabled.

Node Function Availability

In a fabric comprising two or more nodes, Junos Space provides failover when a node functioning as the active server (load balancer server or database server) goes down. By default, Junos Space marks a particular node down and routes failover requests to the node that Junos Space designates as standby server. Junos Space uses a heartbeat mechanism to check whether the nodes in the fabric are running. When a node functioning as the active server fails (the appliance physically crashes or stops sending heartbeats), the node functioning as the standby server takes over all resources that were managed by the node functioning as the active server.