ON THIS PAGE
Troubleshooting EX4200 Components
Understanding Alarm Types and Severity Levels on EX Series Switches
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
Signal alerting you to conditions that might prevent normal
operation. On a switch, the alarm signal is the
Failure event that triggers an alarm.
Seriousness of the alarm. If the Alarm (
Preset alarm triggered by a physical condition on the switch such as a power supply failure, excessive component temperature, or media failure.
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.
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 alarm condition requires monitoring or maintenance.
A missing rescue configuration generates a yellow system alarm.
Chassis Component Alarm Conditions on EX4200 Switches
This topic describes the chassis component alarm conditions on EX4200 switches.
Table 2 lists the alarms that the chassis components can generate on EX4200 switches, their severity levels, and the actions you can take to respond to them.
Table 2: Chassis Component Alarm Conditions on EX4200 Switches
A power supply has been removed from the chassis.
Install a power supply in the empty slot.
The power supply is offline or the power supply output has failed.
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).
An unknown power supply is installed.
Install a Juniper networks recommended power supply.
Fan tray is not installed.
Install the fan tray.
One fan in the chassis is not spinning or is spinning at below the required speed.
Fan failure–i2c read failure.
The temperature inside the chassis has exceeded 203° F (95° C).
The temperature inside the chassis has exceeded 185° F (85° C) and a fan has failed.
The temperature inside the chassis has exceeded 176° F (80° C).
The temperature inside the chassis has exceeded 158° F (70° C) and a fan has failed.
The temperature sensor has failed.
Device booted from backup root.
Upgrade bank is empty or corrupted.
Firmware version is not the latest.
Single-bit ECC error detected.
|Redundant power system (RPS)|
RPS is disconnected.
Check the RPS connection.
RPS fan has failed.
RPS power supply has failed.
RPS is backing up the switch for the first time.
Check the reason for power supply failure.
|Management Ethernet interface|
Management Ethernet link is down
Clean up the system file storage space on the switch. For more information, see Freeing Up System Storage Space.
Clean up the system file storage space on the switch. For more information, see Freeing Up System Storage Space.
Rescue configuration is not set.
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.
Install the required license for the feature specified in the alarm. For more information, see Understanding Software Licenses for EX Series Switches.
Checking Active Alarms with the J-Web Interface
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.
To view the active alarms:
- Select Monitor > Events and Alarms > View Alarms in the J-Web interface.
- Select an alarm filter based on alarm type, severity, description, and date range.
- Click Go.
All the alarms matching the filter are displayed.
When the switch is reset, the active alarms are displayed.
Table 3 lists the alarm output fields.
Table 3: Summary of Key Alarm Output Fields
Category of the alarm:
Alarm severity—either major (red) or minor (yellow).
Brief synopsis of the alarm.
Date and time when the failure was detected.
Monitoring System Log Messages
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.
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:
Table 4: Filtering System Log Messages
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.
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.
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:
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.
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.
Applies the specified filter and displays the matching messages.
To apply the filter and display messages, click Search.
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
Generates a list of event log messages in nontabular format.
To generate a raw 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:
Table 5 describes the Event Summary fields.
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
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 level of a message is indicated by different colors.
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.
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:
Displays a more detailed explanation of the message.
Displays the time at which the message was logged.
Troubleshooting Network Interfaces on EX4200 Switches
This topic provides troubleshooting information for specific problems related to interfaces on EX4200 switches.
The interface on the port in which an SFP or SFP+ transceiver is installed is down
Description: The interface on the port in which an SFP or SFP+ transceiver is installed in an uplink module installed in an EX4200 switch is down.
Symptoms: When you check the status with the CLI command show interfaces ge or with the J-Web user interface, the disabled port is not listed.
By default, the SFP+ and SFP+ MACsec uplink modules operate in the 10-gigabit mode and support only SFP+ transceivers. The operating mode for the module is incorrectly set.
Either SFP+ or SFP transceivers can be installed in the uplink modules. You must configure the operating mode of the SFP+ or SFP+ MACsec uplink module to match the type of transceiver you want to use. For SFP+ transceivers, configure the 10-gigabit operating mode and for SFP transceivers, configure the 1-gigabit operating mode. See Setting the Mode on an SFP+ or SFP+ MACSec Uplink Module .
Troubleshooting Virtual Chassis Port Connectivity on an EX4200 Switch
This topic provides troubleshooting information for specific problems related to uplink module ports on EX4200 switches.
Virtual Chassis port (VCP) connection does not work
Description: The Virtual Chassis port (VCP) connection configured in an EX4200 switch does not work.
Environment: A port of the uplink module is set as a VCP.
The uplink module installed in the switch was replaced.
Set a port in the uplink module as a VCP. See Setting an Uplink Port on an EX Series or QFX Series Switch as a Virtual Chassis Port.
Troubleshooting Power Supply Installation Alarms on EX4200 Switches
This topic provides troubleshooting information for problems related to power supply installation on EX4200 switches.
The Switch Displays the “Unsupported PSU” Alarm
Description: The “Unsupported PSU” alarm appears on the EX4200-24PX or the EX4200-48PX switch.
A 930 W AC power supply is installed in the switch, but no power is detected on PoE+ ports.
The Alarm (ALM) LED lights red and when you check the alarm status using the show chassis alarms command, the “Unsupported PSU” alarm is displayed as shown below:
user@switch> show chassis alarms
1 alarm currently active Alarm time Class Description 2011-02-14 08:34:39 UTC Unsupported PSU
The power supply you have installed is not compatible with the switch.
EX4200-24PX and EX4200-48PX switches do not support the 930
EX-PWR-930-AC) or the 600 W (
EX-PWR-600-AC) AC power supplies that are used in the EX4200-48P and the EX4200-24P
switch models. EX4200-24PX and EX4200-48PX switches work only with
the power supplies labeled
EX-PWR3-930-AC. All EX4200 switches support
EX-PWR3-930-AC power supplies.
Check the label of the power supply you have installed in the switch. You can find the label on the top of the power supply (see Removing a Power Supply from an EX4200 Switch). If it is an incompatible power supply, remove it and install the correct power supply.
Troubleshooting PoE Voltage Injection Failure in EX2300, EX3400, or EX4300 Switch Models with PoE Capability
Description: Devices that draw power from EX2300, EX3400, or EX4300 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.
Environment: EX2300, EX3400, or EX4300 switch models with PoE capability are connected to EX2200, EX3200, or EX4200 switch models with PoE capability by using RJ-45 network ports.
When you connect EX2300, EX3400, or EX4300 switch models with PoE capability to EX2200, EX3200, or EX4200 switch models with PoE capability by using RJ-45 network ports, disable PoE on all the RJ-45 network ports used to connect the switches using the command:
user@device> set poe interface interface-name disable
Troubleshooting Temperature Alarms in EX Series Switches
Description: EX Series switches generate a temperature alarm FPC 0 EX-PFE1 Temp Too Hot.
Temperature sensors in the chassis monitor the temperature of the chassis. The switch raises an alarm if a fan fails or if the temperature of the chassis exceeds permissible levels.
When the switch raises 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.
To prevent the switch from overheating, do not operate it in an area that exceeds the maximum recommended ambient temperature. To prevent airflow restriction, allow at least 6 inches (15.2 cm) of clearance around the ventilation openings.
- 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, and 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
show chassis environment (EX9208 Switch)
user@switch> show chassis environment
Class Item Status Measurement Temp PEM 0 OK 40 degrees C / 104 degrees F PEM 1 OK 40 degrees C / 104 degrees F PEM 2 Absent PEM 3 Absent Routing Engine 0 OK 37 degrees C / 98 degrees F Routing Engine 0 CPU OK 35 degrees C / 95 degrees F Routing Engine 1 Absent Routing Engine 1 CPU Absent CB 0 Intake OK 36 degrees C / 96 degrees F CB 0 Exhaust A OK 34 degrees C / 93 degrees F CB 0 Exhaust B OK 40 degrees C / 104 degrees F CB 0 ACBC OK 39 degrees C / 102 degrees F CB 0 XF A OK 46 degrees C / 114 degrees F CB 0 XF B OK 45 degrees C / 113 degrees F CB 1 Intake Absent CB 1 Exhaust A Absent CB 1 Exhaust B Absent CB 1 ACBC Absent CB 1 XF A Absent CB 1 XF B Absent FPC 3 Intake OK 48 degrees C / 118 degrees F FPC 3 Exhaust A OK 46 degrees C / 114 degrees F FPC 3 Exhaust B OK 51 degrees C / 123 degrees F FPC 3 XL TSen OK 67 degrees C / 152 degrees F FPC 3 XL Chip OK 58 degrees C / 136 degrees F FPC 3 XL_XR0 TSen OK 67 degrees C / 152 degrees F FPC 3 XL_XR0 Chip OK 51 degrees C / 123 degrees F FPC 3 XL_XR1 TSen OK 67 degrees C / 152 degrees F FPC 3 XL_XR1 Chip OK 63 degrees C / 145 degrees F FPC 3 XQ TSen OK 67 degrees C / 152 degrees F FPC 3 XQ Chip OK 63 degrees C / 145 degrees F FPC 3 XQ_XR0 TSen OK 67 degrees C / 152 degrees F FPC 3 XQ_XR0 Chip OK 68 degrees C / 154 degrees F FPC 3 XM TSen OK 67 degrees C / 152 degrees F FPC 3 XM Chip OK 76 degrees C / 168 degrees F FPC 3 XF TSen OK 67 degrees C / 152 degrees F FPC 3 XF Chip OK 75 degrees C / 167 degrees F FPC 3 PLX PCIe Switch TSe OK 51 degrees C / 123 degrees F FPC 3 PLX PCIe Switch Chi OK 54 degrees C / 129 degrees F FPC 3 Aloha FPGA 0 TSen OK 51 degrees C / 123 degrees F FPC 3 Aloha FPGA 0 Chip OK 70 degrees C / 158 degrees F FPC 3 Aloha FPGA 1 TSen OK 51 degrees C / 123 degrees F FPC 3 Aloha FPGA 1 Chip OK 75 degrees C / 167 degrees F FPC 5 Intake Testing FPC 5 Exhaust A Testing FPC 5 Exhaust B Testing Fans Top Rear Fan OK Spinning at intermediate-speed Bottom Rear Fan OK Spinning at intermediate-speed Top Middle Fan OK Spinning at intermediate-speed Bottom Middle Fan OK Spinning at intermediate-speed Top Front Fan OK Spinning at intermediate-speed Bottom Front Fan OK Spinning at intermediate-speed
Table 6 lists the output fields for the show chassis environment command. Output fields are listed in the approximate order in which they appear.
Table 6: show chassis environment Output Fields
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.
Information about the chassis components: Flexible PIC Concentrators (FPCs)–that is, the line cards–, Control Boards (CBs), Routing Engines (REs), Power Entry Modules (PEMs)–that is, the power supplies.
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.
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.
- Issue the command show chassis temperature-thresholds. This command displays the chassis temperature threshold settings.
Following is a sample output on an EX9208 switch. The output is similar
on other EX Series switches.
show chassis temperature-thresholds (EX9208 Switch)
user@ host> show chassis temperature-thresholds
Fan speed Yellow alarm Red alarm Fire Shutdown (degrees C) (degrees C) (degrees C) (degrees C) Item Normal High Normal Bad fan Normal Bad fan Normal Chassis default 48 54 65 55 80 65 100 Routing Engine 0 70 80 95 95 110 110 112 FPC 3 55 60 75 65 105 80 110 FPC 5 55 60 75 65 90 80 95
Table 7 lists the output fields for the show chassis temperature-thresholds command. Output fields are listed in the approximate order in which they appear.
Table 7: show chassis temperature-thresholds Output Fields
Chassis component. You can configure for 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.
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 not triggered until the temperature exceeds the threshold settings for a yellow alarm or a red alarm.
Temperature threshold, in degrees Celsius, that trigger a yellow alarm.
Normal—The temperature threshold that must be exceeded on the component to trigger a yellow alarm when the fans are running at full speed.
Bad fan—The temperature threshold that must be exceeded on the component to trigger a yellow alarm when one or more fans have failed or are missing.
Temperature threshold, in degrees Celsius, that trigger a red alarm.
Normal—The temperature threshold that must be exceeded on the component to trigger a red alarm when the fans are running at full speed.
Bad fan—The temperature threshold that must be exceeded on the component to trigger a red alarm when one or more fans have failed or are missing.
Temperature threshold, in degrees Celsius, for the switch to shut down.
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, which you can display 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 and the respective remedies.
Table 8: Causes and Remedies for Temperature Alarms
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.
Restricted airflow through the switch due to insufficient clearance around the installed switch.
Ensure that there is sufficient clearance around the installed switch. See the following topics to understand the clearance requirements of various EX Series switches.