Multiplexer Chassis Events

This chapter explains how to diagnose and handle multiplexer chassis (MC) events generated by the Cisco 6100 Series system. The following information is presented for each of the events:

Event summary---A summary of the event information including the ID, event name, and its severity.
Description---A short description of the event. Appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser.
Impact---A short discussion of the probable impact of the event. It lists, for example, the number of subscribers who could be affected by this problem.
Action---A step-by-step procedure for handling the event described in the section.

If none of the actions presented for the event are successful, contact the Cisco Technical Assistance Center (TAC) for additional support.

Note Refer to "Cisco 6100 Series System Event Troubleshooting" for detailed information on viewing events in the ViewRunner management software. Refer to "Event Guidelines and Definitions" for detailed information on event severity guidelines and alarm event status changes.

Table 8-1 lists MC chassis events and their IDs, definition, severity, and description. A detailed explanation of these events and corrective actions required (if any) is located in subsections in this chapter.

Table 8-1: Multiplexer Chassis Events
ID Definition Severity Description

1

MC_FAN_FAILURE

Critical

A fan tray is supposed to be present, but it is not detected as present and operational

2

MC_FAN_REQUIRED

Critical

No fan tray has been detected or pre-provisioned, but the current configuration requires one (for example, DMT-2 ATU-C modules are present)

Table 8-1: **Multiplexer Chassis Events**
ID	Definition	Severity	Description
1	MC_FAN_FAILURE	Critical	A fan tray is supposed to be present, but it is not detected as present and operational
2	MC_FAN_REQUIRED	Critical	No fan tray has been detected or pre-provisioned, but the current configuration requires one (for example, DMT-2 ATU-C modules are present)

Note Events with an id less than 128 are specific to the module in alarm. Events with an id value greater than or equal to 128 are system-wide events.

8.1 Fan Tray Not Present and Operational

Event Summary

ID	Event Name	Severity
1	MC_FAN_FAILURE	Critical

Description

The following description appears in the ViewRunner for Windows Event History View dialog box or the ViewRunner for HP OpenView Error Events Browser:

A fan tray is supposed to be present, but is not detected as present and operational

Impact

If the Cisco 6100 Series system detects or was preprovisioned to use an operational fan tray, the system checks the status of the fan tray. If the fan tray is disconnected or not fully operational, the system asserts this alarm event. Because an operational fan tray is necessary to maintain temperature control when you use a Cisco 6130, this critical alarm event stops all DSL traffic through the system.

Action

If a fan tray is required for operation of the system (for instance, a Cisco 6130 is present), use the following steps to clear the alarm event:

Step 1 Verify that the fan tray alarm contacts are connected correctly. Figure 8-1 shows how the fan tray connector (P2) connects to the fan tray alarm contacts (P14, pin 7 and 8) on the MC backplane. If necessary, reconnect the fan tray to the MC backplane. Refer to the Cisco 6100 Series Direct Connect Installation Guide for additional information on connecting the fan tray alarm contacts.

Figure 8-1: Fan Tray Alarm Contacts Connection

Step 2 If the fan tray connector and the fan tray alarm contacts are connected correctly and the fan tray is not operational, verify that all three fans in the fan tray are running. If one no longer functions, refer to the Cisco 6100 Series System Fan Tray Configuration Notes for fan replacement procedures. Replace the non-operational fan and verify that this procedure clears the alarm event.

Step 3 If you have checked the connectors and replaced the fans, and the fan tray is not operational, replace the fan tray with a spare fan tray.

If the spare fan tray executes properly, return the initial fan tray to Cisco for repair. Contact TAC for the nearest Cisco service center.
If the spare fan tray does not execute properly, contact TAC for further assistance.

If the fan tray is not required for operation of the system (for instance, a Cisco 6130 is not present), uncheck the Fan Tray Present setting in the ViewRunner System Configuration dialog box or change the MIB value lrChassisFanTray.1 to absent.

Note If the fan tray is suffering an intermittent failure, you must disconnect the fan tray from the MC to prevent the fan tray from being detected, thereby changing the fan tray setting back to present.

8.2 No Required Fan Tray Detected or Preprovisioned