Troubleshooting The M7I Fan Tray - Juniper M7i Hardware Manual

M7i Multiservice Edge Router Hardware Guide
Related
Documentation

Troubleshooting the M7i Fan Tray

Problem
Solution
204
Table 60: SONET/SDH Interface Alarm Messages (continued)
CLI Message
interface-name so-x/x/x - SONET path mismatch
interface-name so-x/x/x - SONET path remote defect indicator
interface-name so-x/x/x - SONET PLL lock
interface-name so-x/x/x - SONET remote error indicator
interface-name so-x/x/x - SONET severely errored frame
interface-name so-x/x/x - SONET unequipped
Displaying M7i Router Components and Serial Numbers on page 213
M7i Midplane Description on page 12
M7i Router Description on page 3
Description: The fans in the fan tray are not functioning normally.
The router's single fan tray provides cooling for the router, including the CFEB or CFEB-E,
PICs, power supplies, and Routing Engine.
The cooling system draws in room air through the air intake vent on the left side of the
chassis. After entering the chassis, the air stream separates into separate flows for the
front and rear components. For a graphic depiction of the airflow, see
For the cooling system to function properly, the clearance around the chassis must be
sufficient for unobstructed airflow. See
and Hardware Maintenance" on page
During normal operation, the fans in the fan tray function at less than full speed. The
router constantly monitors the temperatures detected by sensors on the router
components, adjusting the speed of the fans as necessary. If the router temperature
exceeds the acceptable maximum, the router turns off the power supplies.
The following conditions automatically cause the fans to run at full speed and trigger
the indicated alarm:
A fan fails (red alarm).
The router temperature exceeds the "temperature warm" threshold (yellow alarm).
The temperature of the router exceeds the maximum ("temperature hot") threshold
(red alarm and automatic shutdown of the power supplies).
"M7i Router Clearance Requirements for Airflow
77.
Copyright © 2019, Juniper Networks, Inc.
Figure 9 on page 16.