Troubleshooting the EX4300 Components
Understand 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.
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 EX4300 Switches
This topic describes the chassis component alarm conditions on EX4300 switches.
Table 2 lists the alarms that the chassis components can generate on EX4300 switches, their severity levels, and the actions you can take to respond to them.
Chassis Component |
Alarm Condition |
Alarm Severity |
Remedy |
|---|---|---|---|
| Power supplies | A power supply has been removed from the chassis. |
Minor (yellow or amber) |
Install a power supply in the empty slot. |
A power supply output has failed. |
Major (red) |
Check power supply output connection. |
|
A power supply has failed. |
Major (red) |
Replace the failed power supply. |
|
An unknown power supply is installed. |
Major (red) |
Install a power supply recommended by Juniper Networks. |
|
Mix of power supplies with different airflow directions. |
Major (red) |
Do not mix power supplies with different directions for the airflow in the same chassis. |
|
Mix of fan modules and power supplies with different airflow directions. |
Major (red) |
Do not mix fan modules and power supplies with different directions for the airflow in the same chassis. |
|
| Fan modules | Fan module is not installed. |
Major (red) |
Install the fan module. |
A fan module has failed. |
Major (red) |
Replace the fan module. |
|
Mix of fan modules with different airflow directions. |
Major (red) |
Do not mix fan modules with different directions for the airflow in the same chassis. |
|
Mix of fan modules and power supplies with different airflow directions. |
Major (red) |
Do not mix fan modules and power supplies with different directions for the airflow in the same chassis. |
|
| Temperature | The temperature inside the chassis reaches the yellow or amber alarm limit. |
Minor (yellow or amber) |
|
The temperature inside the chassis reaches the red alarm limit. |
Major (red) |
|
|
| Management Ethernet interface | Management Ethernet link is down |
Major (red) |
|
| Routing Engine | /var partition usage is high. |
Minor (yellow or amber) |
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 or amber) |
Use the |
|
Feature usage requires a license or the license for the feature usage has expired. |
Minor (yellow or amber) |
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
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:
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.
Meaning
Table 3 lists the alarm output fields.
Field |
Values |
|---|---|
Type |
Category of the alarm:
|
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
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
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, |
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 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 |
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:
|
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:
|
Generates a list of event log messages in nontabular format. |
To generate a raw report:
|
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:
|
Meaning
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.
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.
|
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:
|
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
- Debugging and confirming voltage injection by analyzing the PoE port status on Juniper switches
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
set poe interface <interface name>
When connecting EX4200, EX3200, EX2200 to EX4400, EX4300, EX3400, and EX2300, disable PoE on legacy switches (EX4200, EX3200, EX2200) as below:
set poe interface ge-0/0/0 disable
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.
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.
-
Connect to the switch by using Telnet, and issue the
show chassis environmentcommand. 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)
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-speedTable 6 lists the output fields for the
show chassis environmentcommand. The table lists output fields in the approximate order in which they appear.Table 6: show chassis environmentOutput FieldsField Name
Field Description
ClassInformation 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
ItemInformation 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
StatusStatus of the specified chassis component. For example, if
ClassisFans, 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.
MeasurementDepends on the Class. For example, if
ClassisTemp, indicates the temperature in degrees Celsius (°C) and degrees Fahrenheit (°F). If theClassisFans, indicates actual fan RPM. -
-
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)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 95Table 7 lists the output fields for the
show chassis temperature-thresholdscommand. The table lists output fields in the approximate order in which they appear.Table 7: show chassis temperature-thresholdsOutput FieldsField 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 3exceeds 55° C, the output indicates that the fans are operating at a high speed (no alarm is triggered).If the temperature of
FPC 3exceeds 65° C, a yellow alarm is triggered to indicate that one or more fans have failed.If the temperature of
FPC 3exceeds 75° C, a yellow alarm is triggered to indicate that the temperature threshold limit is exceeded.If the temperature of
FPC 3exceeds 80° C, a red alarm is triggered to indicate that one or more fans have failed.If the temperature of
FPC 3exceeds 105° C, a red alarm is triggered to indicate that the temperature threshold limit is exceeded.If the temperature of
FPC 3exceeds 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.
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:
|
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.