Help Center User GuideGetting Started
User Guide
Getting Started

System View

Monitoring Chassis Information


View chassis properties, which include the status of hardware components on the device.


To view these chassis properties, select Monitor>System View>Chassis Information in the J-Web user interface.

Caution Do not install a combination of Physical Interface Modules (PIMs) in a single chassis that exceeds the maximum power and heat capacity of the chassis. If power management is enabled, PIMs that exceed the maximum power and heat limits remain offline when the chassis is powered on. To check PIM power and heat status, use the show chassis fpc and show chassis power-ratings commands.

The Chassis Information page displays the following types of information:

To control which component details appear, select a hardware component from the Select component list.

Alternatively, you can view chassis details by entering the following show commands in the CLI configuration editor:

See Also

Monitoring Cluster Status


Use the monitoring functionality to view the cluster status page.


To monitor cluster status select, Monitor>System View>Cluster Status.


Table 38 summarizes key output fields on the cluster status page.

Table 38: Cluster Status Monitoring Page



Additional Information

Refresh Interval (sec)

Displays the time interval set for page refresh.

Select the time interval from the drop-down list.


Displays the option to refresh the page.

Cluster Status

Redundancy Group

Displays the redundancy group specified for the chassis cluster.


Displays the failover options selected.

  • Counter— Displays the number of times chassis cluster failed.

    Action—Displays the active tool for users to fail over chassis cluster.


Displays the node used for the chassis cluster.


Provides an option to switch between the primary and secondary nodes.


Displays the state of the redundancy group for node 0 and node 1. The possible states are:

  • Primary—Redundancy group is active and passing traffic.

  • Secondary—Redundancy group is passive and not passing traffic.

  • Lost—Node loses contact with the other node through the control link. Most likely to occur when both nodes are in a cluster one node is rebooted, or, because of a control link failure, one node cannot exchange heartbeats with the other node.

  • Unavailable—Node has not received a single heartbeat over the control link from the other node since the other node booted up. Most likely to occur when one node boots up before the other node or if only one node is present in the cluster.


Displays the preempt option selected to initiate a failover for node 0 and 1. The possible preempt options are:

  • Yes—Mastership can be preempted based on priority.

  • No—Mastership cannot be preempted if the priority changes.

Manual Failover

Displays the priority value of node 0 for manual failover. The possible manual failover options are:

  • Yes—If the mastership is set manually, it overrides the Priority and Preempt options.

  • No—Mastership is not set manually.

Interface Monitoring


Displays the interfaces monitored by the redundancy group and shows their respective weights.


Displays the weight for the interface to be monitored.


Displays the status of the interface.

See Also

Monitoring Cluster Statistics


Use the monitoring functionality to view the cluster statistics page.


To monitor cluster statistics select Monitor>System View>Cluster Statistics.


Table 39 summarizes key output fields in the cluster statistics page.

Table 39: Cluster Statistics Monitoring Page



Additional Information

Refresh Interval (sec)




Control Link Statistics

Services Synchronized

Service Name

RTOs Sent

RTOs Received

Fabric Link Statistics

See Also

Help us to improve. Rate this article.
Feedback Received. Thank You!

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      

Additional Comments

800 characters remaining

May we contact you if necessary?


Need product assistance? Contact Juniper Support