Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Monitoring the System

Monitoring System Properties for SRX Series Devices

Purpose

View system properties and customize the Dashboard.

When you start the J-Web user interface on an SRX Series device, the interface opens to the Dashboard. At the top and bottom of the page, the Dashboard displays an interactive representation of your device and a current log messages pane. By default, the center panes of the Dashboard display System Information, Resource Utilization, Security Resources, and System Alarms. However, you can customize the Dashboard panes to provide the best overview of your system.

Action

1. Click the Preferences icon at the top-right corner of the page. The Dashboard Preference dialog box appears.
2. Select the types of information you want to display.
3. (Optional) Specify the Automatically Refresh Data option to specify how often you want the data on the Dashboard to be refreshed.
4. Click OK to save the configuration or Cancel to clear it.
5. On the Dashboard, minimize, maximize, or drag the individual information panes to customize the display as needed.

System Identification

—

Displays the device’s serial number, hostname, current software version, the BIOS version, the amount of time since the device was last booted, and the system’s time. Note: To view the BIOS version under system identification, delete your browser cookies. The hostname that appears in this pane is defined using the set system hostname command. On SRX Series devices, security logs were always timestamped using the UTC time zone by running set system time-zone utc and set security log utc-timestamp CLI commands. Now, time zone can be defined using the local time zone by running the set system time-zone time-zone command to specify the local time zone that the system should use when timestamping the security logs.

• To view an image of the front of the device, right-click the image and choose View Front.
• To view an image of the back of the device, right-click the image and choose View Rear.
• To enlarge or shrink the device view, use the Zoom bar.
• To return the device image to its original position and size, click Reset.

Note: To use the Chassis View, a recent version of Adobe Flash that supports ActionScript and AJAX (Version 9) must be installed. Also note that the Chassis View appears by default on the Dashboard page. You can enable or disable it using options in the Dashboard Preference dialog box. Clearing cookies in Internet Explorer also causes the Chassis View appear on the Dashboard page.

To return to the Dashboard at any time, select Dashboard in the J-Web user interface.

Alternatively, you can view system properties by entering the following show commands in the CLI:

• show system uptime
• show system users
• show system storage
• show version
• show chassis hardware

Monitoring System Properties for J Series Devices

Purpose

View the system properties on a J Series device.

Action

Select Monitor>System View>System Information in the J-Web user interface. The System Information page displays the following types of information:

• General—General tab of the System Information page displays the device’s serial number, current Junos OS version, hostname, IP address, loopback address, domain name server, and time zone.

  Note: The hostname that appears on this page is defined using the set system hostname command. On J Series devices, security logs were always timestamped using the UTC time zone by running set system time-zone utc and set security log utc-timestamp CLI commands. Now, time zone can be defined using the local time zone by running the set system time-zone time-zone command to specify the local time zone that the system should use when timestamping the security logs.

• Time—Time tab of the System Information page displays the current time for the device, the last time the device was booted, the last time protocol settings were configured on the device, and the last time the device configuration was updated. Additionally, this tab displays the CPU load averages for the last 1, 5, and 15 minutes.
• Storage Media—Storage Media tab of the System Information page displays information about the memory components installed on the device (such as flash memory or USB) and the amount of memory used compared to total memory available.
• Logged-In User Details—Logged-In User Details section of the System Information page displays information about the users who are currently logged into the device, including their usernames, the terminals and systems from which they logged in, the length of their user sessions, and how long their sessions have remained idle.
• Active User Count—Active User Count field displays the number of users currently signed into the device.

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

• show system uptime
• show system users
• show system storage
• show version
• show chassis hardware
• show interface terse

Monitoring Chassis Information

Purpose

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

Action

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 J Series 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:

• Routing Engine Details—This section of the page includes the following tabs:
  • Master—Master tab displays information about the routing engine, including the routing engine module, model number, version, part number, serial number, memory utilization, temperature, and start time. Additionally, this tab displays the CPU load averages for the last 1, 5, and 15 minutes.
  • Backup—If a backup routing engine is available, the Backup tab displays the routing engine module, model number, version, part number, serial number, memory utilization, temperature, and start time. Additionally, this tab displays the CPU load averages for the last 1, 5, and 15 minutes.

  Note: If you need to contact customer support about the device chassis, supply them with the version and serial number displayed in the Routing Engine Details section of the page.

• Power and Fan Tray Details—This Details section of the page includes the following tabs:
  • Power—Power tab displays the names of the device’s power supply units and their statuses.
  • Fan—Fan tab displays the names of the device’s fans and their speeds (normal or high). (The fan speeds are adjusted automatically according to the current temperature.)
• Chassis Component Details—This section of the page includes the following tabs:
  • General—General tab displays the version number, part number, serial number, and description of the selected device component.
  • Temperature—Temperature tab displays the temperature of the selected device component (if applicable).
  • Resource—Resource tab displays the state, total CPU DRAM, and start time of the selected device component (if applicable).

    Note: On some devices, you can have an FPC state as “offline.” You may want to put an FPC offline because of an error or if the FPC is not responding. You can put the FPC offline by using the CLI command request chassis fpc slot number offline.

  • Sub-Component—Sub-Component tab displays information about the device’s sub-components (if applicable). Details include the sub-component’s version, part number, serial number, and description.

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:

• show chassis hardware
• show chassis routing-engine
• show chassis environment
• show chassis redundant-power-supply
• show redundant-power-supply status

Monitoring Process Details for J Series Devices

Purpose

View the process details that indicate the status of each of the processes running on the J Series device.

Action

Select Monitor>System View>Process Details in the J-Web user interface.

The Process Details page displays the following types of information for the entire device:

• CPU Load—Displays the average CPU usage of the device over the last minute in the form of a graph.
• Total Memory Utilization—Displays the current total memory usage of the device in the form of a graph.

• PID—Displays the unique number identifying the process.
• Value—Displays the name of the process.
• State—Displays the current state of the process (runnable, sleeping, or unknown).
• CPU Load—Displays the current CPU usage of the process.
• Memory Utilization—Displays the current memory usage of the process.
• Start Time—Displays the time that the process started running.

Alternatively, you can view chassis details from the Dashboard on an SRX Series device or by entering the following show commands in the CLI configuration editor:

• show chassis routing-engine
• show system process

System Health Management for Branch SRX Series Devices

Purpose

Tracking the utilization of critical resources in the system ensures that all parameters are within normal limits and the system remains functional.

In the event of a malfunction caused by abnormal resource usage, the system health management feature provides the right diagnostic information to identify the source of the problem.

When the system health management action is configured by the user, the system takes appropriate monitoring, preventive, and recovery actions to ensure that the system is accessible. The system configuration might be updated based on the information collected by system health management feature to ensure that the system stays in the normal operating environment. For example, when a system runs out of memory, then the configuration associated with applications identified to be consuming memory resources can be updated to bring down the memory resource consumption.

Action

The system health management feature periodically monitors critical system resources against configurable thresholds. The resources that can be monitored include CPU usage, memory, storage, open-file-descriptor, process-count, and temperature. The system health management feature collects usage information for each resource at the configured interval and compares it against the three levels of thresholds: moderate, high, and critical. Based on the configurations, appropriate action is taken.

• Default configuration level— Default configuration is applied when system health monitoring is enabled, and neither a global nor a resource-specific configuration is present.
• Global configuration level—Configuration that is applied to resources when no resource-specific configuration is available.
• Resource-specific configuration level—Configuration that, if available, overrides both the global and the default configurations.

Per-resource configurations take precedence over the global configuration, and a global configuration takes precedence over the defaults.

When resource usage exceeds the configured thresholds, the system collects information that can be used to find the source of the increased usage and saves it in history for analysis and action.

When resource utilization exceeds the high threshold, a minor system alarm is generated, and the alarm LED lights yellow. When resource utilization exceeds the critical threshold, a major alarm is generated, and the alarm LED lights red.

An SNMP trap is also sent to the remote monitoring server (NMS) for all events that exceed the threshold.

To enable the system health monitor, use the set snmp health-monitor routing engine command. You can view system properties by using CLI show commands.