Server Alarms - Avaya Support

Table 410: RMC Power/Fan Query Test (#77) 2 of 2
Error
Code
Test
Result
1 FAIL
(cont’d)
Description / Recommendation
RMC Power/Fan Query Test (#77)
5. If the fans are running at high speed, check the following items. Any
one of these could be restricting or redirecting the cabinet’s air flow.
● Check the filter. If the filter is dirty or clogged, it should be cleaned
or replaced. The filter can either be washed with soap and water
or vacuumed.
● Verify that nothing other than circuit packs are in the carrier slots
that could be restricting air flow.
● Verify that no circuit-pack blanks or carrier faceplates are
missing. Install and/or replace them as necessary.
● Verify the cabinet’s doors are properly closed. The doors must be
closed to enable the fans to properly cool the cabinet. Wait 5
minutes to allow the fans to cool the cabinet. Rerun the test. If the
test still fails, proceed to Step 6.
6. At this point, there should be nothing impeding the air flow and the
fans should be running at high speed. Check the temperatures for
the 5- to 60 0 -C criteria.
● If the 5 to 60 0 C criteria exists, a temperature problem exists, and
the fans (at high speed) should cool down the switch. Wait 5
minutes, and rerun the test. If the test still fails, the ambient room
temperature is probably too high, and the room should be cooled.
If not, the fans are defective. Replace the fan assembly and rerun
the test. Failures can occur on the Processor circuit pack which
are not detected but can cause many, if not every, environment
test to fail. If several environment tests are failing, the suspected
circuit pack, depending on the system configuration, should be
replaced and the test rerun.
FAIL There is a problem with the environment of the power system. The
power unit for the cabinet may be defective.
1. Verify and, if necessary, replace the power unit.
2. Rerun the test. If the test still fails, escalate the problem.
PASS The cabinet does not have a power or fan problem. If a problem is
reported, troubleshoot by using the previous procedures for the FAIL
cases.
2 of 2
Communication Manager Release 5.0 Issue 4 January 2008 1539