Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Viewing Nodes in the Fabric

The Fabric Monitoring inventory page allows the administrator to monitor each node in the Junos Space fabric. You can also monitor the status of the database, load balancer, and application logic functions running on each node, identify nodes that are overloaded or down, and view when the node was rebooted. The Fabric inventory page refreshes every 10 seconds, by default.

Changing Views

You can display fabric monitoring in tabular view. The fabric nodes appear in a table sorted by node name. Each fabric is a row in the Fabric Monitoring table.

To change views:

  1. Select Administration > Fabric. The Fabric page appears.
  2. Click a view indicator at the left of the title bar of the Fabric page.

Viewing Fabric Node Details

To view detailed runtime and status information for a node:

  1. On the Junos Space Network Management Platform user interface, select Administration > Fabric.

    The Fabric page that appears displays all the nodes in the Junos Space Platform fabric.

  2. Right-click a node and select View Fabric Node Details or double-click inside a row corresponding to a node.

    The View Node Detail pop-up window that appears displays three tabs: Node Detail, Reboot Detail, and Process Detail.

  3. To view the node details, click the Node Detail tab.

    Table 1 describes the details of the node.

    Table 1: Information on the Node Detail Tab

    Information

    Description

    Node name

    Logical name assigned to the node

    Note:

    For the first node, Junos Space uses the node name that the user specifies during the initial configuration of the Junos Space Appliance (physical or virtual). For each subsequent node, the user must specify a node name when adding the node to the fabric.

    Management IP (IPv4)

    IPv4 address for the node

    Management IP (IPv6)

    IPv6 address for the node

    Host Name

    Host name of the node

    Device Connection IP (IPv4)

    IPv4 address for connecting to the device

    Device Connection IP (IPv6)

    IPv6 address for connecting to the device

    Status

    Connection status for the node

    • UP—Node is connected to the fabric

    • DOWN—Node is disconnected from the fabric

    % CPU

    Percentage of CPU resource utilized by the node; from 0 to 100%

    • Unknown—Percentage of CPU utilized is unknown, for example, because the node is not connected

    % Memory

    Percentage of memory resource utilized by the node; from 0 to 100%

    • Unknown—Percentage of memory utilized is unknown, for example, because the node is not connected

    % SWAP

    Percentage of swap memory used

    • Unknown—Percentage of SWAP memory utilized is unknown, for example, because the node is not connected

    % DISK

    Percentage of the /var directory utilized by the node; from 0 to 100%

    • Unknown—Percentage of the /var directory utilized by the node is unknown, for example, because the node is not connected

    App Logic

    Application logic function status for the node

    • UP—Application logic function is running on the node

    • DOWN—Application logic function enabled on the node but is not running

    • Unknown—Status for the application logic function is unknown, for example, because the node is not connected

    • NA— Application logic function is not configured to run on the node

    • (Primary)—Configured primary Junos Space node in the fabric

    • FMPM (Primary)—The configured primary Fault Monitoring and Performance Monitoring (FMPM) node in the fabric

    • FMPM—The configured secondary FMPM node in the fabric

    • Deploying—Junos Space Platform and its applications are initializing after a recent JBoss restart

    • Parsing Schema—Device schema files are being parsed after a recent JBoss restart

    Database

    Database function status for the node

    • UP(Primary)—Database function is running on the node and the node is the primary database node

    • Up—Database function is running on the node

      In the case of dedicated database nodes, the secondary database node is always UP.

    • Down—Database function that is enabled on the node but is not running

    • Standby—Database function is on standby and could potentially transition to the UP state on failover

    • Unknown—Status for the database function is unknown, for example, because the node is not connected

    • NA—Database function is not configured to run on the node

      Note:

      By default, the database function is enabled on no more than two nodes in the fabric.

    • Out of Sync— Database is out of sync with the node. View Status provides a detailed report of errors with remedies.

    Load balancer

    Load balancer function for the node

    • Up—Load balancer function is running on the node

    • Down—Load balancer function that is enabled on the node is not running

    • Standby—Load balancer function is on standby and could potentially transition to the UP state on failover

    • Unknown—Status for the Load balancer function is unknown, for example, because the node might not be connected

    • NA—Load balancer function is not running because it is not configured to run on the node

      Note:

      By default, the Load balancer function is enabled on no more than two nodes in the fabric.

    • (VIP)—Configured virtual IP node in the fabric

    Hardware model

    Model of the Junos Space Appliance

    Note:

    The hardware model, which is applicable only to the hardware appliance, appears when you double-click a table row for a detailed view of the node.

    Software version

    Junos Space Network Management Platform release version

    Note:

    Software version appears when you double-click a table row for a detailed view of the node.

    Serial number

    The serial number for the Junos Space Appliance

    Note:

    Serial number appears when you double-click a table row for a detailed view of the node.

    Cluster Member IPs

    IP addresses of the nodes in the fabric

    Is Primary Node

    Indicates whether the node is a primary node:

    • TRUE—The node is a primary node

    • FALSE—The node is not a primary node

    Is VIP Node

    Indicates whether the node is a virtual IP (VIP) node. The first (active) node and second (standby) node are VIP nodes.

    • TRUE—The node is a VIP node.

    • FALSE—The node is not a VIP node.

    Virtual Machine(s)

    Lists the virtual machine IPs hosted by the node.

    Host IP

    IP address of the hosted virtual machine. This field is not applicable to Junos Space nodes and Fault Monitoring and Performance Monitoring (FMPM) nodes.
  4. To view the details of the last reboot performed, select the Reboot Detail tab.

    Table 2 lists the information related to the last reboot performed on this node.

    Table 2: Information on the Reboot Detail Tab

    Information

    Description

    Last Boot Time

    Time at which the node was rebooted

    Last Boot Reason

    Reason why the node was rebooted

    Last Rebooted By

    Username of the user who rebooted the node
    Note:

    If the node was rebooted from the CLI, or as a result of an upgrade or a fresh installation, the Last Rebooted By column displays #system.

    Table 3 lists the default messages displayed to the user for different types of reboot actions.

    Table 3: Default Messages for Different Reboot Actions

    Reboot Action

    Default Message

    Rebooting after changing the network settings of the node from the Junos Space user interface

    Reboot after Space Network Settings change

    Upgrading Junos Space Platform

    Space reboot after Software Upgrade

    Rebooting from the CLI

    Reboot from Shell/Other

    Starting up Junos Space Platform for the first time

    Junos Space startup after Installation/Software Upgrade
  5. To view the details of the processes on this node, select the Process Detail tab.

    Table 4 lists the columns that specify the details of the following processes: JBoss, Apache Web Proxy, MySQL, OpenNMS, and PostgreSQL.

    Table 4: Columns on the Process Detail Tab

    Column Name

    Description

    Process

    Name of the process

    Status

    Status of the process: UP, DOWN, STANDBY, or N/A

    %CPU

    Percentage of CPU resources used by the process on the node

    %MEMORY

    Percentage of memory used by the process on the node

    Start Time

    Time at which the process is initiated
    Note:

    The status of the process and the percentage of CPU resources used by the process is queried once every 30 seconds.

    Table 5 lists the different statuses of the following processes: JBoss, Apache Web Proxy, MySQL, OpenNMS, PostgresSQL, and Cassandra.

    Table 5: Process Status

    Process Status

    Description

    UP

    The process is up and active.

    DOWN

    The process is down and inactive.

    STANDBY

    The process is in standby mode and could potentially transition to the UP state on failover.

    N/A

    The process is never expected to be active on the node.
    Note:

    If the MySQL database replication between nodes is broken, the MySQL process displays the status OUT OF SYNC. If the secondary database is in the process of receiving data and the primary database is still executing transactions then the status is Syncing. If the MySQL transactions are up-to-date between nodes, the MySQL process displays the status UP.

Table 6 describes the behavior and the expected status of the processes when OpenNMS is running on the Junos Space node.

Table 6: Status of the Processes When OpenNMS Is Running on the Junos Space Node

Process

Junos Space Node with OpenNMS
 

VIP Node

Secondary Node

Other Nodes

Apache Web Proxy

UP/DOWN

STANDBY

N/A

JBoss

UP/DOWN

UP/DOWN

UP/DOWN

MySQL

UP/DOWN

UP/DOWN

N/A

OpenNMS

UP/DOWN

STANDBY

N/A

PostgresSQL

UP/DOWN

UP/DOWN

N/A

Cassandra

UP/DOWN

UP/DOWN

UP/DOWN

Table 7 describes the behavior and the expected status of the processes when OpenNMS is running on the FMPM node.

Table 7: Status of the Processes When OpenNMS Is Running on the FMPM Node

Process

Junos Space Node

FMPM Node
 

VIP Node

Secondary Node

Other Nodes

OpenNMS VIP Node

OpenNMS Secondary Node

Apache Web Proxy

UP/DOWN

STANDBY

N/A

N/A

N/A

JBoss

UP/DOWN

UP/DOWN

UP/DOWN

N/A

N/A

MySQL

UP/DOWN

UP/DOWN

N/A

N/A

N/A

OpenNMS

N/A

N/A

N/A

UP/DOWN

STANDBY

PostgresSQL

N/A

N/A

N/A

UP/DOWN

UP/DOWN

Cassandra

UP/DOWN

UP/DOWN

UP/DOWN

N/A

N/A
Note:

If an unexpected process is running on a node, the status of the process is shown as UP. If a node fails, the status of all processes on the node is shown as UNKNOWN.

For more information about modifying data on the Fabric inventory page, see Junos Space User Interface Overview.

Related Documentation