Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Troubleshooting EX2300 Components

Understand Alarm Types and Severity Levels on EX Series Switches

Note:

This topic applies only to the J-Web Application package.

Alarms alert you to conditions that might prevent normal operation of the switch. Before monitoring alarms on a Juniper Networks EX Series Ethernet switch, become familiar with the terms defined in Table 1.

Table 1: Alarm Terms

Term

Definition

alarm

Signal alerting you to conditions that might prevent normal operation. On a switch, the alarm signal is the ALM LED lit on the front of the chassis.

alarm condition

Failure event that triggers an alarm.

alarm severity

Seriousness of the alarm. If the Alarm (ALM) LED is red, this indicates a major alarm. If the Alarm LED is yellow or amber, this indicates a minor alarm. If the Alarm LED is unlit, there is no alarm or the switch is halted.

chassis alarm

Preset alarm triggered by a physical condition on the switch such as a power supply failure, excessive component temperature, or media failure.

system alarm

Preset alarm triggered by a missing rescue configuration or failure to install a license for a licensed software feature.

Note:

On EX6200 switches, a system alarm can be triggered by an internal link error.

Alarm Types

The switch supports these alarms:

  • Chassis alarms indicate a failure on the switch or one of its components. Chassis alarms are preset and cannot be modified.

  • System alarms indicate a missing rescue configuration. System alarms are preset and cannot be modified, although you can configure them to appear automatically in the J-Web interface display or the CLI display.

Alarm Severity Levels

Alarms on switches have two severity levels:

  • Major (red)—Indicates a critical situation on the switch that has resulted from one of the following conditions. A red alarm condition requires immediate action.

    • One or more hardware components have failed.

    • One or more hardware components have exceeded temperature thresholds.

    • An alarm condition configured on an interface has triggered a critical warning.

  • Minor (yellow or amber)—Indicates a noncritical condition on the switch that, if left unchecked, might cause an interruption in service or degradation in performance. A yellow or amber alarm condition requires monitoring or maintenance.

    A missing rescue configuration generates a yellow or amber system alarm.

See Also

Chassis Component Alarm Conditions on EX2300 Switches

This topic describes the chassis component alarm conditions on EX2300 switches.

Table 2 lists the alarm conditions on EX2300 switches, their severity levels, and the actions you can take to respond to them.

Table 2: Alarm Conditions on EX2300 Switches

Chassis Component

Alarm Condition

Alarm Severity

Remedy
Temperature

The temperature inside the chassis reaches the yellow alarm limit.

Minor (yellow)

  • Check the fan.

  • Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-5822 (toll-free within the United States and Canada) or 1-408-745-9500 (from outside the United States).

The temperature inside the chassis reaches the red alarm limit.

Major (red)

  • Check the fan.

  • Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-5822 (toll-free within the United States and Canada) or 1-408-745-9500 (from outside the United States).

The temperature sensor has failed.

Major (red)

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-5822 (toll-free within the United States and Canada) or 1-408-745-9500 (from outside the United States).
Management Ethernet interface

Management Ethernet link is down.

Major (red)

  • Check whether a cable is connected to the management Ethernet interface, or whether the cable is defective. Replace the cable if required.

  • If you are unable to resolve the problem, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-5822 (toll-free within the United States and Canada) or 1-408-745-9500 (from outside the United States).
Routing Engine

/var partition usage is high.

Minor (yellow)

Clean up the system file storage space on the switch. For more information, see Freeing Up System Storage Space.

/var partition is full.

Major (red)

Clean up the system file storage space on the switch. For more information, see Freeing Up System Storage Space.

Rescue configuration is not set.

Minor (yellow)

Use the request system configuration rescue save command to set the rescue configuration.

Feature usage requires a license or the license for the feature usage has expired.

Minor (yellow)

Install the required license for the feature specified in the alarm. For more information, see Understanding Software Licenses for EX Series Switches.

See Also

Check Active Alarms with the J-Web Interface

Purpose

Note:

This topic applies only to the J-Web Application package.

Use the monitoring functionality to view alarm information for the EX Series switches including alarm type, alarm severity, and a brief description for each active alarm on the switching platform.

Action

To view the active alarms:

  1. Select Monitor > Events and Alarms > View Alarms in the J-Web interface.

  2. Select an alarm filter based on alarm type, severity, description, and date range.

  3. Click Go.

    All the alarms matching the filter are displayed.

Note:

When the switch is reset, the active alarms are displayed.

Meaning

Table 3 lists the alarm output fields.

Table 3: Summary of Key Alarm Output Fields

Field

Values

Type

Category of the alarm:

  • Chassis—Indicates an alarm condition on the chassis (typically an environmental alarm such as one related to temperature).

  • System—Indicates an alarm condition in the system.

Severity

Alarm severity—either major (red) or minor (yellow or amber).

Description

Brief synopsis of the alarm.

Time

Date and time when the failure was detected.

See Also

Monitor System Log Messages

Purpose

Note:

This topic applies only to the J-Web Application package.

Use the monitoring functionality to filter and view system log messages for EX Series switches.

Action

To view events in the J-Web interface, select Monitor > Events and Alarms > View Events.

Apply a filter or a combination of filters to view messages. You can use filters to display relevant events. Table 4 describes the different filters, their functions, and the associated actions.

To view events in the CLI, enter the following command:

show log

Table 4: Filtering System Log Messages

Field

Function

Your Action

System Log File

Specifies the name of a system log file for which you want to display the recorded events.

Lists the names of all the system log files that you configure.

By default, a log file, messages, is included in the /var/log/ directory.

To specify events recorded in a particular file, select the system log filename from the list— for example, messages.

Select Include archived files to include archived files in the search.

Process

Specifies the name of the process generating the events you want to display.

To view all the processes running on your system, enter the CLI command show system processes.

For more information about processes, see the Junos OS Installation and Upgrade Guide.

To specify events generated by a process, type the name of the process.

For example, type mgd to list all messages generated by the management process.

Date From

To

Specifies the time period in which the events you want displayed are generated.

Displays a calendar that allows you to select the year, month, day, and time. It also allows you to select the local time.

By default, the messages generated during the last one hour are displayed. End Time shows the current time and Start Time shows the time one hour before End Time.

To specify the time period:

  • Click the Calendar icon and select the year, month, and date— for example, 02/10/2007.

  • Click the Calendar icon and select the year, month, and date— for example, 02/10/2007.

  • Click to select the time in hours, minutes, and seconds.

Event ID

Specifies the event ID for which you want to display the messages.

Allows you to type part of the ID and completes the remainder automatically.

An event ID, also known as a system log message code, uniquely identifies a system log message. It begins with a prefix that indicates the generating software process or library.

To specify events with a specific ID, type the partial or complete ID— for example, TFTPD_AF_ERR.

Description

Specifies text from the description of events that you want to display.

Allows you to use regular expressions to match text from the event description.

Note:

Regular expression matching is case-sensitive.

To specify events with a specific description, type a text string from the description with regular expression.

For example, type ^Initial* to display all messages with lines beginning with the term Initial.

Search

Applies the specified filter and displays the matching messages.

To apply the filter and display messages, click Search.

Reset

Resets all the fields in the Events Filter box.

To reset the field values that are listed in the Events Filter box, click Reset.

Generate Raw Report

Note:

  • Starting in Junos OS Release 14.1X53, a Raw Report can be generated from the log messages being loaded in the Events Detail table. The Generate Raw Report button is enabled after the event log messages start loading in the Events Detail table.

  • After the log messages are completely loaded in the Events Detail table, Generate Raw Report changes to Generate Report.

Generates a list of event log messages in nontabular format.

To generate a raw report:

  1. Click Generate Raw Report.

    The Opening filteredEvents.html window appears.

  2. Select Open with to open the HTML file or select Save File to save the file.

  3. Click OK.

Generate Report

Note:

Starting in Junos OS Release 14.1X53, a Formatted Report can be generated from event log messages being loaded in an Events Detail table. The Generate Report button appears only after event log messages are completely loaded in the Events Detail table. The Generate Raw Report button is displayed while event log messages are being loaded.

Generates a list of event log messages in tabular format, which shows system details, events filter criteria, and event details.

To generate a formatted report:

  1. Click Generate Report.

    The Opening Report.html window appears.

  2. Select Open with to open the HTML file or select Save File to save the file.

  3. Click OK.

Meaning

Table 5 describes the Event Summary fields.

Note:

By default, the View Events page in the J-Web interface displays the most recent 25 events, with severity levels highlighted in different colors. After you specify the filters, Event Summary displays the events matching the specified filters. Click the First, Next, Prev, and Last links to navigate through messages.
Table 5: Viewing System Log Messages

Field

Function

Additional Information

Process

Displays the name and ID of the process that generated the system log message.

The information displayed in this field is different for messages generated on the local Routing Engine than for messages generated on another Routing Engine (on a system with two Routing Engines installed and operational). Messages from the other Routing Engine also include the identifiers re0 and re1 that identify the Routing Engine.

Severity

Severity level of a message is indicated by different colors.

  • Unknown—Gray—Indicates no severity level is specified.

  • Debug/Info/Notice—Green—Indicates conditions that are not errors but are of interest or might warrant special handling.

  • Warning—Yellow or Amber—Indicates conditions that warrant monitoring.

  • Error—Blue—Indicates standard error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels.

  • Critical—Pink—Indicates critical conditions, such as hard-drive errors.

  • Alert—Orange—Indicates conditions that require immediate correction, such as a corrupted system database.

  • Emergency—Red—Indicates system panic or other conditions that cause the switch to stop functioning.

A severity level indicates how seriously the triggering event affects switch functions. When you configure a location for logging a facility, you also specify a severity level for the facility. Only messages from the facility that are rated at that level or higher are logged to the specified file.

Event ID

Displays a code that uniquely identifies the message.

The prefix on each code identifies the message source, and the rest of the code indicates the specific event or error.

The event ID begins with a prefix that indicates the generating software process.

Some processes on a switch do not use codes. This field might be blank in a message generated from such a process.

An event can belong to one of the following type categories:

  • Error—Indicates an error or failure condition that might require corrective action.

  • Event—Indicates a condition or occurrence that does not generally require corrective action.

Event Description

Displays a more detailed explanation of the message.

  

Time

Displays the time at which the message was logged.

  

See Also

Troubleshooting PoE Voltage Injection Failure in EX2300, ​EX3400, EX4300, or EX4400 Switch Models with PoE Capability

Problem

Description

Devices that draw power from EX2300, EX3400, EX4300 or EX4400 switch models with Power over Ethernet (PoE) capability do not get power from those switches. The problem persists after rebooting the switches or upgrading to the latest version of Junos OS. PoE stops working on Juniper EX3400, EX2300, EX4300, or EX4400 devices during initial installation. It is noticed that the new PDs connected to the POE devices do not power up.

  • When the PoE ports of the Switches - EX2200, EX3200, EX4200, and EX4400 are connected to the PoE ports of EX3400, EX4300, EX2300, EX4400, the PoE functionality would be affected on EX4300, EX3400, EX2300, EX4400 switches. This is an expected behavior.

  • When an EX3400 is connected to another EX3400 or an EX4300 is connected to an EX3400 the PoE operates in a normal manner - This is an expected behavior.

Debugging and confirming voltage injection by analyzing the PoE port status on Juniper switches

Voltage injection on PoE port scan can be identified by enabling syslog any any on EX3400, EX2300, EX4300, and EX4400.

In show log messages, any POE voltage injection port with status 36 indicates this problem. This is caused due to PoE power injected to the ports on EX3400, EX4300, EX2300, and EX4400.

Port status 36 is due to the mutual powering of switches. This is because Juniper switches support legacy device detection. Switches that supports legacy detection will detect other switches as a legacy device, and power each other.

Solution

When connecting uplink devices to EX3400, EX4300, EX2300, EX4400, ensure PoE is disabled on the interface (uplink device). PoE must be enabled only on interfaces where Access Points/VOIP Phones or any other PoE powered devices are connected.

Use the following command

When connecting EX4200, EX3200, EX2200 to EX4400, EX4300, EX3400, and EX2300, disable PoE on legacy switches (EX4200, EX3200, EX2200) as below:

See Also

Troubleshooting Storage Issues While Upgrading Junos OS in EX2300 and EX3400 Switches

Problem

Description

Upgrading Junos OS in EX2300 and EX3400 switches fails.

Symptoms

When you upgrade Junos OS in EX2300 and EX3400 switches, you get the error not enough space to unpack installation-pack-name.

Cause

There is not enough memory in the switch to install the upgrade installation package.

Solution

If upgrading Junos OS in EX2300 and EX3400 switches fails due to the lack of memory in the switch:

  1. Perform a system storage cleanup and delete unwanted files in the system storage by using the command:

    Note:

    You can get the list of files that this command deletes by using the command:

    This command does not delete files in the root folder; it deletes files in the folders jail, log, and tmp only.

  2. If any directory is taking up a lot of memory, delete unwanted files in that directory. Check the memory utilization by using the command:

  3. Delete non-recovery snapshots.

    • If Junos OS 15.1X53D56 or later is installed in your switch:

      1. Delete non-recovery snapshots by using the command:

    • If a version of Junos OS released earlier than Junos OS 15.1X53D56 is installed in your switch:

      1. Check for non-recovery snapshots by using the command:

      2. Note:

        Snapshot names are not completed automatically in the CLI; you must enter the snapshot name.

        Delete non-recovery snapshots by using the command:

  4. After upgrading Junos OS, delete the upgrade installation package by using the command:

See Also

Troubleshoot Temperature Alarms in EX Series Switches

Problem

Description

EX Series switches trigger a temperature alarm FPC 0 EX-PFE1 Temp Too Hot when the switch temperature becomes too hot.

Cause

Temperature sensors in the chassis monitor the temperature of the chassis. The switch triggers an alarm if a fan fails or if the temperature of the chassis exceeds permissible levels for some other reason.

Solution

When the switch triggers a temperature alarm such as the FPC 0 EX-PFE1 Temp Too Hot alarm, use the show chassis environment and the show chassis temperature-thresholds commands to identify the condition that triggered the alarm.

CAUTION:

To prevent the switch from overheating, operate it in an area with an ambient temperature within the recommended range. To prevent airflow restriction, allow at least 6 inches (15.2 cm) of clearance around the ventilation openings.

  1. Connect to the switch by using Telnet, and issue the show chassis environment command. This command displays environmental information about the switch chassis, including the temperature. The command also displays information about the fans, power supplies, and Routing Engines. Following is a sample output on an EX9208 switch. The output is similar on other EX Series switches.

    show chassis environment (EX9208 Switch)

    Table 6 lists the output fields for the show chassis environment command. The table lists output fields in the approximate order in which they appear.

    Table 6: show chassis environment Output Fields

    Field Name

    Field Description

    Class

    Information about the category or class of chassis component:

    • Temp: Temperature of air flowing through the chassis in degrees Celsius (°C) and degrees Fahrenheit (°F)

    • Fans: Information about the status of fans and blowers

    Item

    Information about the chassis components:

    • Flexible PIC Concentrators (FPCs)—that is, the line cards

    • Control Boards (CBs)

    • Routing Engines

    • Power entry modules (PEMs)—that is, the power supplies

    Status

    Status of the specified chassis component. For example, if Class is Fans, the fan status can be:

    • OK: The fans are operational.

    • Testing: The fans are being tested during initial power-on.

    • Failed: The fans have failed or the fans are not spinning.

    • Absent: The fan tray is not installed.

    Measurement

    Depends on the Class. For example, if Class is Temp, indicates the temperature in degrees Celsius (°C) and degrees Fahrenheit (°F). If the Class is Fans, indicates actual fan RPM.

  2. Issue the command show chassis temperature-thresholds . This command displays the chassis temperature threshold settings. The following is a sample output on an EX9208 switch. The output is similar on other EX Series switches.

    show chassis temperature-thresholds (EX9208 Switch)

    Table 7 lists the output fields for the show chassis temperature-thresholds command. The table lists output fields in the approximate order in which they appear.

    Table 7: show chassis temperature-thresholds Output Fields

    Field Name

    Field Description

    Item

    Chassis component. You can configure the threshold information for components such as the chassis, the Routing Engines, and FPC for each slot in each FRU to display in the output. By default, information is displayed only for the chassis and the Routing Engines.

    Fan speed

    Temperature thresholds, in degrees Celsius, for the fans to operate at normal and at high speed.

    • Normal—The temperature threshold at which the fans operate at normal speed and when all the fans are present and functioning normally.

    • High—The temperature threshold at which the fans operate at high speed or when a fan has failed or is missing.

    Note:

    An alarm is triggered when the temperature exceeds the threshold settings for a yellow, amber, or red alarm.

    Yellow or amber alarm

    Temperature threshold, in degrees Celsius, that triggers a yellow or amber alarm.

    • Normal—The temperature threshold that must be exceeded on the device to trigger a yellow or amber alarm when the fans are running at full speed.

    • Bad fan—The temperature threshold that must be exceeded on the device to trigger a yellow or amber alarm when one or more fans have failed or are missing.

    Red alarm

    Temperature threshold, in degrees Celsius, that triggers a red alarm.

    • Normal—The temperature threshold that must be exceeded on the device to trigger a red alarm when the fans are running at full speed.

    • Bad fan—The temperature threshold that must be exceeded on the device to trigger a red alarm when one or more fans have failed or are missing.

    Fire shutdown

    Temperature threshold, in degrees Celsius, at which the switch shuts down in case of fire.

When a temperature alarm is triggered, you can identify the condition that triggered it by running the show chassis environment command to display the chassis temperature values for each component and comparing those with the temperature threshold values. You can display the temperature threshold values by running the show chassis temperature-thresholds command.

For example, for FPC 3:

  • If the temperature of FPC 3 exceeds 55° C, the output indicates that the fans are operating at a high speed (no alarm is triggered).

  • If the temperature of FPC 3 exceeds 65° C, a yellow alarm is triggered to indicate that one or more fans have failed.

  • If the temperature of FPC 3 exceeds 75° C, a yellow alarm is triggered to indicate that the temperature threshold limit is exceeded.

  • If the temperature of FPC 3 exceeds 80° C, a red alarm is triggered to indicate that one or more fans have failed.

  • If the temperature of FPC 3 exceeds 105° C, a red alarm is triggered to indicate that the temperature threshold limit is exceeded.

  • If the temperature of FPC 3 exceeds 110° C, the switch is powered off.

Table 8 lists the possible causes for the switch to generate a temperature alarm. It also lists the respective remedies.

Table 8: Causes and Remedies for Temperature Alarms

Cause

Remedy

Ambient temperature is above threshold temperature.

Ensure that the ambient temperature is within the threshold temperature limit. See Environmental Requirements and Specifications for EX Series Switches.

Fan module or fan tray has failed.

 Perform the following steps:

  1. Check the fan.

  2. Replace the faulty fan module or fan tray.

  3. If the above two checks show no problems, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-5822 (toll-free within the United States and Canada) or 1-408-745-9500 (from outside the United States).

Restricted airflow through the switch due to insufficient clearance around the installed switch.

Ensure that there is sufficient clearance around the installed switch.

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release
Description
14.1X53
Starting in Junos OS Release 14.1X53, a Raw Report can be generated from the log messages being loaded in the Events Detail table.
14.1X53
Starting in Junos OS Release 14.1X53, a Formatted Report can be generated from event log messages being loaded in an Events Detail table.