Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Troubleshoot the QFX5120 Device

Alarm Types and Severity Levels

The QFX Series switches support different alarm types and severity levels. Table 1 provides a list of alarm terms and definitions that may help you in monitoring the device.

Table 1: Alarm Terms and Definitions

Term

Definition

Alarm

Signal that alerts you to conditions that might prevent normal operation. On the device, alarm indicators might include an LCD panel and LEDs on the device. The LCD panel (if present on the device) displays the chassis alarm message count. Blinking amber or yellow LEDs indicate yellow alarm conditions for chassis components.

Alarm condition

Failure event that triggers an alarm.

Alarm severity levels

Seriousness of the alarm. The level of severity can be either major (red) or minor (yellow).

  • Major (red)—Indicates a critical situation on the device 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 device that, if left unchecked, might cause an interruption in service or a degradation in performance. A yellow alarm condition requires monitoring or maintenance. For example, a missing rescue configuration generates a yellow system alarm.

Alarm types

Alarms include the following types:

  • Chassis alarm—Predefined alarm triggered by a physical condition on the device such as a power supply failure or excessive component temperature.

  • Interface alarm—Alarm that you configure to alert you when an interface link is down. Applies to ethernet, fibre-channel, and management-ethernet interfaces. You can configure a red (major) or yellow (minor) alarm for the link-down condition, or have the condition ignored.

  • System alarm—Predefined alarm that might be triggered by a missing rescue configuration, failure to install a license for a licensed software feature, or high disk usage.

Chassis Alarm Messages

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

Chassis alarms on QFX5100, QFX5110, QFX5210, and QFX5120 devices have two severity levels:

  • Major (red)—Indicates a critical situation on the device that has resulted from one of the conditions described in Table 2. A red alarm condition requires immediate action.

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

Table 2 describes the chassis alarm messages on QFX5100, QFX5110, QFX5200, QFX5210, and QFX5120 devices.

Table 2: Chassis Alarm Messages

Component

Alarm Type

CLI Message

Recommended Action

Fans

Major (red)

Fan Failure

Replace the fan module and report the failure to customer support.

Fan I2C Failure

Check the system log for one of the following error messages and report the message to customer support:

  • CM ENV Monitor: Get fan speed failed.

  • fan-number is NOT spinning @ correct speed, where fan-number can be 1, 2, 3, 4, or 5.

Fan fan-number Not Spinning

Remove and check the fan module for obstructions, and then reinsert the fan module. If the problem persists, replace the fan module.

Minor (yellow)

Fan/Blower Absent

Check the system log for the error message fan-number Absent, where fan-number can be can be 1, 2, 3, 4, or 5.

Install fan modules in the slots where they are absent.

Power supplies

Major (red)

PEM pem-number Airflow not matching Chassis Airflow

Replace the power supply with a power supply that supports the same airflow direction as supported by the chassis.

PEM pem-number I2C Failure

Check the system log for one of the following error messages and report the message to customer support:

  • I2C Read failed for device number, where number where number ranges from 123 through 125.

  • PS number: Transitioning from online to offline, where power supply number is 1 or 2.

PEM pem-number is not powered

Check the power cord connection and reconnect, if necessary.

PEM pem-number is not supported

Replace the power supply with a supported power supply.

PEM pem-number Not OK

Indicates a problem with the incoming AC power or outgoing DC power. Report the error to customer support.

Minor (yellow)

PEM pem-number Absent

Reboot the switch after removing one of the power supply. The switch can continue to operate with a single power supply.

OR

Replace the removed power supply and reboot the switch.

PEM pem-number Power Supply Type Mismatch

Check whether there is a mix of AC and DC power supplies in the same chassis. Reboot the switch with only AC or only DC power supplies.

PEM pem-number Removed

Replace the removed power supply or reboot the switch. The switch can continue to operate with a single power supply.

Temperature sensors

Major (red)

sensor-location Temp Sensor Fail

Check the system log for the following error message and report the message to customer support:

Temp sensor sensor-number failed, where sensor-number ranges from 1 through 10.

sensor-location Temp Sensor Too Hot

Check environmental conditions and alarms on other devices. Ensure that environmental factors (such as hot air blowing around the equipment) do not affect the temperature sensor. If the condition persists, the device might shut down.

Minor (yellow)

sensor-location Temp Sensor Too Warm

Check environmental conditions and alarms on other devices. Ensure that environmental factors (such as hot air blowing around the equipment) do not affect the temperature sensor.

Routing Engine

Minor (yellow)

RE RE number /var partition usage is high

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

Major (red)

RE RE number /var partition is full

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

Minor (yellow)

Rescue configuration is not set

Use the request system configuration rescue save command to set the rescue configuration. For more information, see Setting or Deleting the Rescue Configuration.

Feature usage requires a license

or

License for feature expired

Install the required license for the feature specified in the alarm. For more information, see Software Features That Require Licenses on the QFX Series.

Management Ethernet interface

Major (red)

Management Ethernet 1 Link Down

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

On models that have both em0 and em1 management interfaces available, you must connect both interfaces. If both interfaces are not connected, the alarm is raised. However, the alarm has no service impact.

If you are unable to resolve the problem, open a support case by using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-5822 (tollfree, US or 1-408-745-9500 (from outside the United States).

Creating an Emergency Boot Device for QFX Series Switches

Before you begin, you need to download the installation media image for your device and Junos OS release from https://www.juniper.net/customers/support/ .

If Junos OS on the device is damaged in some way that prevents the software from loading properly, you can use an emergency boot device to repartition the primary disk and load a fresh installation of Junos OS. Use the following procedure to create an emergency boot device.

Note:

You can create the emergency boot device on another Juniper Networks device, or any laptop or desktop PC that supports Linux. The steps you take to create the emergency boot device vary, depending on the device.

To create an emergency boot device:

  1. Use FTP to copy the installation media image into the /var/tmp directory on the device.
  2. Insert a USB storage device into the USB port.
  3. From the CLI, start the shell:
  4. Use the gunzip command to unzip the image file.
  5. Switch to the root account using the su command:
    Note:

    The password is the root password for the device. If you logged in to the device as the root user, you do not need to perform this step.

  6. Enter the following command on the device:

    The device writes the installation media image to the USB storage device:

  7. Log out of the shell:

Recovering the Installation Using an Emergency Boot Device on QFX Series Switches

If Junos OS on your device is damaged in some way that prevents the software from loading correctly, you may need to perform a recovery installation using an emergency boot device (for example, a USB flash drive) to restore the default factory installation. Once you have recovered the software, you need to restore the device configuration. You can either create a new configuration as you did when the device was shipped from the factory, or if you saved the previous configuration, you can simply restore that file to the device.

If at all possible, you should try to perform the following steps before you perform the recovery installation:

  1. Ensure that you have an emergency boot device to use during the installation. See Creating an Emergency Boot Device for QFX Series Switches for information on how to create an emergency boot device.

  2. Copy the existing configuration in the file /config/juniper.conf.gz from the device to a remote system, such as a server, or to an emergency boot device. For extra safety, you can also copy the backup configurations (the files named /config/juniper.conf.n, where n is a number from 0 through 9) to a remote system or to an emergency boot device.

    You can use the system snapshot feature to complete this step. The system snapshot feature takes a “snapshot” of the files currently used to run the QFX Series switch—the complete contents of the /config and /var directories, which include the running Junos OS, the active configuration, and the rescue configuration—and copies all of these files into a memory source. See Creating a Snapshot and Using It to Boot a QFX Series Switch.

    Note:

    System snapshot is not supported on QFX10000 and QFX5200 switches.
    CAUTION:

    The recovery installation process completely overwrites the entire contents of the internal flash storage.

  3. Copy any other stored files to a remote system as desired.

To reinstall Junos OS:

  1. Connect to the device's console port (either directly or through a console server).

  2. Insert the emergency boot device into the QFX Series switch.

  3. Reboot or power cycle the device.

  4. As soon as the device reboots, keep pressing Esc until the boot options menu opens.

    Note:

    You might have to reboot or power cycle the device more than once if you miss hitting Esc to open the boot options menu.

  5. In the boot options menu, select Boot Manager.

  6. In the Boot Manager menu, select the emergency boot device. In this example, the emergency boot device is the USB device.

    Note:

    In later releases, the Boot Manager menu might display two different entries for the same USB recovery device. Select the EFI USB Device entry.

    The Juniper Linux Installer or GNU GRUB menu opens. The menu and options may differ slightly depending on the platform and release.

  7. If you have Junos OS software from the factory installed on the emergency boot device, the software prompts you with the following options:

    Select Install Juniper Linux Platform to install the Junos OS software from the emergency boot device.

    Note:

    Depending on the platform and release, you may see different entries such as Install Juniper Linux, Install Juniper Linux Platform, or Install Juniper Linux with secure boot support.

  8. The device copies the software from the emergency boot device, occasionally displaying status messages. Copying the software can take up to 12 minutes.

  9. After the software is copied to the device, the device reboots from the internal flash storage on which the software was just installed.

    Note:

    If the Boot Manager menu includes both SSD drive and EFI HDD Device entries, manually select the EFI HDD Device option.

    When the reboot is complete, the device displays the Junos OS login prompt:

  10. Create a new configuration as you did when the device was shipped from the factory, or restore the previously saved configuration file to the device.

  11. Remove the emergency boot device.