System Alarm/Event Troubleshooting

Alarm Summary - A summary of the alarm or event information including the ID, alarm name, and its severity.
Description - A short description of the alarm. This description is what appears in the ViewRunner for Windows Event History window.
Impact - A short discussion of the probable impact of the alarm or event. For example, how many subscribers could be affected by this problem.
Action - A step-by-step procedure for handling the alarm or event described in the section.

If none of the actions presented on the alarm page are successful, please contact Cisco TAC for support.

The Event History window shows all the alarms that have been asserted and cleared for a particular Cisco 6100 system. ViewRunner will poll the node for new alarms/events at 15-second intervals by default throughout a session. The user may change this poll interval by selecting the Options > > ViewRunner Preferences menu option.

Note ViewRunner displays only the alarms/events as they are reported by the 6100 or as they are generated by ViewRunner itself. Alarms from other network elements in the end-to-end ATM connection are not reported by ViewRunner.

The 6100 node saves up to 200 events at a time, beginning with number "1" and incrementing indefinitely. When the node event log exceeds 200 events, the oldest event in the queue, Event 1, is removed, and the newest event is added to the bottom of the queue as Event 201. Therefore, depending on how many alarms/events are generated, the node queue could begin with sequence Event 101 and end with Event 300.

ViewRunner, on the other hand, can save more than 200 events at a time. That is, if the node alarm/event queue is showing Event 101 through 300, the ViewRunner may be displaying alarm/Event 50 through 300 depending on how long the ViewRunner session has been active and what the node was showing at the time the session began. There is a one-to-one correspondence between the sequence number of an alarm/event in the node with the Sequence Id of an alarm/event displayed by the ViewRunner for the most recent 200 events. However, if alarms/events have been removed from the top of queue at the node between ViewRunner sessions or between polls, the user will never see them. For example, if more than 200 events occur since the last ViewRunner session, you would not see those that had already been removed from the node queue when you begin the new session. ViewRunner does, however, generate its own alarm indicating that alarms/events have been missed during its current poll.

If the ViewRunner detects a system controller (SC) reset during an active session, all displayed alarms/events are removed from the Event History window, and only alarms/events occurring after the reset are displayed. The 6100 node itself loses alarm history and begins numbering again at "1" after an SC reset.

ViewRunner Event History Window Illustration

The figure below is an example of the Event History window for ViewRunner for Windows.

Figure 5-1: Event History Window

Note Once the Event History window has been opened, it cannot be closed. Notice that the "x" in the upper right hand corner of the window is disabled. You can iconify the window, however, to get it off the screen.

The fields in this figure are described in the following table.

Field	Field Description
Sequence Id	The sequence number of the alarm/event in the ViewRunner's event log for this session. The field also contains an alarm icon in which the color indicates something about the severity of the alarm: Red - Critical/Asserted Orange - Major/Asserted Yellow - Minor/Asserted Green - Critical/Cleared, Major/Cleared, and Minor/Cleared, Blue - Undefined White - Information
Severity	The severity of the alarm/event as determined by Cisco. The alarm/event severities are defined as follows: Service outage is defined as either line down or no cell throughput. Service impairment is defined as cell loss not associated with network congestion, but is great enough to result in a noticeable throughput loss. Undefined - indicates that the format of the data returned from the node was faulty Severities include info, critical, minor, and major.
Log Time	The date and time on which the alarm/event occurred.
Entity	The module against which the alarm/event is asserted. The information in this field can be used to help track down the alarm/event in this chapter. The entity can be any one of the following: ATU-C, SC, NI, LIM controller, LIM, Slot, ViewRunner, and Unknown. An "Unknown" entity is returned only when the format of the data from the node is faulty.
AID	The Access Identifier as in the chassis and slot number associated with the alarm/event. The information in this field can pinpoint the source of the alarm/event and thus help the user to further diagnose what the problem might be. ViewRunner will display "Unknown" in the AID field if an alarm/event was asserted by an entity which was later deleted, or by an entity that was added but not yet "auto-discovered" by ViewRunner before generating an alarm. By clicking on this underlined text in this field, you can navigate directly to the entity and slot from which the alarm was received.
Status	The current status of the alarm as in: Asserted - an alarm/event has been generated by an entity. Cleared - a previously asserted alarm has been cleared. Info - informational event only. Undefined - indicates that the format of the data returned from the node was faulty
Description	A short description of the alarm/event. This description should be the same as the descriptions found in the alarm/event tables in the subsections of this chapter. This description is a predefined string based on the entity and event code from the node. See the ViewRunner for Windows Provisioning and Operation Manual for exceptions to this definition.

Table 5-1: Event History Window Field Definitions

Field Field Description

Sequence Id

The sequence number of the alarm/event in the ViewRunner's event log for this session. The field also contains an alarm icon in which the color indicates something about the severity of the alarm:

Red - Critical/Asserted
Orange - Major/Asserted
Yellow - Minor/Asserted
Green - Critical/Cleared, Major/Cleared, and Minor/Cleared,
Blue - Undefined
White - Information

Severity

The severity of the alarm/event as determined by Cisco. The alarm/event severities are defined as follows:

Service outage is defined as either line down or no cell throughput. Service impairment is defined as cell loss not associated with network congestion, but is great enough to result in a noticeable throughput loss.
Undefined - indicates that the format of the data returned from the node was faulty

Severities include info, critical, minor, and major.

Log Time

The date and time on which the alarm/event occurred.

Entity

The module against which the alarm/event is asserted. The information in this field can be used to help track down the alarm/event in this chapter. The entity can be any one of the following: ATU-C, SC, NI, LIM controller, LIM, Slot, ViewRunner, and Unknown. An "Unknown" entity is returned only when the format of the data from the node is faulty.

AID

The Access Identifier as in the chassis and slot number associated with the alarm/event. The information in this field can pinpoint the source of the alarm/event and thus help the user to further diagnose what the problem might be. ViewRunner will display "Unknown" in the AID field if an alarm/event was asserted by an entity which was later deleted, or by an entity that was added but not yet "auto-discovered" by ViewRunner before generating an alarm.

By clicking on this underlined text in this field, you can navigate directly to the entity and slot from which the alarm was received.

Status

The current status of the alarm as in:

Asserted - an alarm/event has been generated by an entity.
Cleared - a previously asserted alarm has been cleared.
Info - informational event only.
Undefined - indicates that the format of the data returned from the node was faulty

Description

A short description of the alarm/event. This description should be the same as the descriptions found in the alarm/event tables in the subsections of this chapter. This description is a predefined string based on the entity and event code from the node. See the ViewRunner for Windows Provisioning and Operation Manual for exceptions to this definition.

AID=Access Identifier
NI=network interface
LIM=line interface module

The contents of the ViewRunner Event History window can be sorted by any one of the fields in the preceding table by clicking on the field header. Clicking on more than one column heading allows the user to nest sorts in the order of column selection. If there are more entries than can fit in the window, a scroll bar will appear to allow scrolling through the entries.

It is also possible for the user to selectively remove entries from the display simply by selecting those entries and deleting them. Events can be selected in the Event History View and deleted by clicking the Alarm toolbar deletion button (looks like an X - see toolbar). This does not remove the alarms/events permanently from the 6100. They are removed only from the ViewRunner display. You select by clicking the Sequence Id number of each row. Use Shift or Ctrl to select multiple entries.

Logical service oriented screen navigation is available in the Event History window. Click on the blue underlined text, and ViewRunner will take you to the Properties window of the chassis, slot, and port where the alarm was asserted.

5.1 Current Alarm Window

The Current Alarms window displays a concise list of all currently asserted alarms in the system, including module, slot, and image alarms. The window format is similar to the Event History window, except that it has fewer columns.

In the Current Alarms window, current alarms are retrieved and displayed when the window is first opened and when the user manually requests a refresh.

Note The Current Alarms window is not updated dynamically using the existing ViewRunner Preferences >> Alarm and Event polling interval.

The following figure is an example of the Current Alarms window.

Figure 5-2: Current Alarm Window

Logical service oriented screen navigation is available in the Current Alarms window. Click on the blue underlined text and ViewRunner will take you to the properties window of the chassis, slot, and port where the alarm was asserted.

Note Once the Current Alarms window has been opened, it cannot be closed. Notice that the "x" in the upper right hand corner of the window is disabled. You can iconify the window, however, to get it off the screen.

Alarm/Event Status Changes

Alarms that have been "Asserted" by the 6100 are either followed by a "Cleared" event or by an "Info" (128) event which in effect clears all alarms associated with a particular entity at a particular slot. For example, some alarms can be "Cleared" if the problem was caused by congestion or single parity errors. Other times, the module generating the alarm must be reset and/or reinserted. In this case, the only event returned is Event 128 "Module was detected." which effectively clears whatever outstanding alarms were asserted against that module.

The current alarms are displayed in ViewRunner in the Module/Port Property Status dialogs. They are also represented by the color of the ejector tabs on the modules in the Configuration View. The total number of current alarms is listed by severity on the ViewRunner toolbar under Alarm Window. These objects define the set of alarms currently asserted for a slot/board/port, and the severity levels. When an alarm is cleared, it is removed from the set. These alarms correspond to the active alarms in the 6100. They may differ from the ViewRunner Event History window display in that alarms are not removed from the Event History window display when they are cleared. Both "Asserted" and "Cleared" alarms remain in the Event History window display as long as the session is active to serve as a history of alarms/events.

Alarm Severity Guidelines

Given the wide variety of severity mapping decisions that could be selected based on the previous factors, a set of paradigms must be established to treat like events in a similar fashion, and thus ensure that severity is set in a practical fashion. These guidelines will become arbitrary with the introduction of network provider controlled alarm severity mapping. Additionally, with the advent of more sophisticated 6100 and ViewRunner performance monitoring, threshold alarming, and so on, these guidelines will be replaced by well known rules for handling network element anomalies and faults, as defined in GR-820-CORE. For this release, however, the guidelines established are as follows.

The following rules are used to define an event versus an alarm, and the severity therein:

All events are not alarms. Events with a severity of "Info" (Informational) are not alarms.
Events that are not alarms (informational events) are not followed in the event log by a cleared message.
An informational event is not defined as service affecting. Service affecting is defined in a binary sense for the purposes of alarm characterization - the subscriber is only service affected if it is taken out of service. Temporary traffic throughput impairments (loss of ATM cells, buffer overflows, parity errors, and so forth) result in an informational event, but are typically expected to be recoverable in a reasonably transparent fashion to the subscriber.
Repeated informational events of this type (as defined in the actions below) may trigger an alarm in a future release.
Alarms have a severity of minor, major, or critical.
Alarm severity is based on guidelines set forth in TR-NWT-000057, Functional Criteria for DLC Systems; pp. 13-2 to 13-3, as follows:
- Critical - greater than 128 customer lines are out of service
- Major - greater than 24 customer lines are out of service
- Minor - 2 to 23 customer lines are out of service

Exceptions to the above guidelines are used as follows.

Even though a loss of an ATU-C does not necessarily affect any customer lines (if other modems in the logical pool are idle), a minor alarm is generated. As the loss of a modem can affect service levels for all subscribers in a given logical pool, a minor alarm will typically trigger a craft recovery action.
In the Impact section of the alarm documentation, some alarm events note that a significant number of subscribers will be affected. If the nature of the alarm condition is such that the system is likely to recover given time (for instance, buffer overflow), the alarm will be categorized as "Informational". Impact and Alarm Description will be modified in the next software release to make this consistent. This is based on the logic that craft-activation alarms should really only be triggered when subscriber lines are out of service.

Fundamentally, an alarm-related event (there are events that are not alarm related) will either result in a service impairment or a service outage. However, it is possible to receive alarm events that are not necessarily service affecting in any manner. A "service impairment" typically results in a loss of end to end traffic for some number of subscriber connections (one to many) for some period of time (milliseconds to seconds, but normally less than a minute unless repeat occurrences are encountered). A "service outage" is the absolute loss of the ability to connect one or more subscribers. The severities below are mapped according to the following philosophy:

All "service impairments" are given a severity of "Minor". The rationale for this decision is that if a single event of this nature occurs, the system will be able to recover quickly enough to essentially be transparent to the affected subscriber(s).

Note With the advent of more comprehensive performance management in a subsequent release, multiple occurrences of many of the events currently supported within the 6100 will cause a threshold to be crossed. In most cases, that will generate a higher severity trap. Until that time, the philosophy chosen for this release is to assume the event's severity is a function of a single occurrence.

"Service Outage" severities are coded to either "Major" or "Critical", depending upon the number of affected subscribers. If four or fewer subscribers are out of service, the event is coded "Major". All other service outages will result in a critical event.
Non-service affecting events are coded to "Minor" and include those events that are not directly associated with service impairment or loss, but should be resolved nonetheless.

Checklist of System Alarms/Events

The checklist of alarms appears in a table under each aspect of the system for which the alarm is relevant. The tables include the ID, definition, severity, and description of the each alarm.

All of those tables are concatenated here for easy reference. Each table is repeated in its own section with detailed information which includes alarm summary, description, impact, and action.

ID	Definition	Severity	Description
2	SAC_SOFTWARE_FAILED_CRC	Major	Software failed CRC check during download.
3	SAC_OUT_OF_MEMORY	Critical	Application was unable to allocate memory.
128	LR_CREATE_OBJ	Info	Module was detected.
129	LR_PING_FAIL	Critical	Module did not respond to system monitor.

ID	Definition	Severity	Description
2	SC_IP_MISMATCH	Minor	The IP number assigned to the 6100 is unusable.
3	SC_SUBNET_ERROR	Minor	The subnet mask for the IP number is incorrect.
4	SC_DOWNLOAD_DONE	Info	Download to the SC is complete.
127		Critical	Loss of communication with SC

ID	Definition	Severity	Description
128	LR_CREATE_OBJ	Info	Module was detected.
129	LR_PING_FAIL	Critical	Module did not respond to the system monitor.

ID	Definition	Severity	Description
0	FC_ALM_EXT_MEM_PAR_ERR	Minor	ATM chipset external memory parity error.
1	FC_ALM_IN_RCV_PAR_ERR	Minor	ATM chipset, cell dropped due to ingress receive side UTOPIA bus parity error.
2	FC_ALM_EG_RCV_PAR_ERR	Minor	ATM chipset, cell dropped due to egress receive side UTOPIA bus parity error.
3	FC_ALM_UTOPIA_SYNC_ERR	Minor	ATM chipset, UTOPIA bus synchronization error detected.
4	FC_ALM_POL_EU_TIMEOUT_ERR	Minor	ATM chipset, parity error detected on policing EU word access.
5	FC_ALM_VCI_SIZE_ERR	Minor	ATM chipset, ingress VCI value above max value.
6	FC_ALM_VPI_SIZE_ERR	Minor	ATM chipset, ingress VPI value above max value.
7	FC_ALM_MPHY_PORT_OVERRUN	Minor	ATM chipset, ingress UTOPIA synchronization error detected.
8	FC_ALM_IN_FIFO_FULL	Minor	ATM chipset, ingress cells are being dropped due to ingress capture fifo full condition. Fabric control driver software will attempt to clear the condition.
9	FC_ALM_EG_CAP_SYNC_ERR	Minor	ATM chipset, an egress capture fifo synchronization error is detected. The device will be reset by fabric control driver software. Device must be re-initialized and connections re-established.
10	FC_ALM_IN_CAP_SYNC_ERR	Minor	ATM chipset, an ingress capture fifo synchronization error is detected. The device will be reset by fabric control driver software. Device must be re-initialized and connections re-established.
11	FC_ALM_INSERT_SYNC_ERR	Minor	ATM chipset, ingress insertion fifo synch error. Fabric control driver software resets fifo.
12	FC_ALM_FULL_MEM_TEST_FAILURE	Minor	ATM chipset, diagnostic memory test detects memory failure.
13	FC_ABM_SEQ_ERROR_ILL	Minor	ATM chipset, a sequence error in the ingress linked list was detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.
14	FC_ABM_PAR_ERR_ING_CELL	Minor	ATM chipset, cell dropped due to ingress parity error.
15	FC_ABM_SEQ_ERROR_ELL	Minor	ATM chipset, a sequence error in the egress linked list was detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.
16	FC_ABM_PAR_ERR_ING_STORED	Minor	ATM chipset, parity error detected in ingress buffer RAM.
17	FC_ABM_PAR_ERR_ING_STORED	Minor	ATM chipset, parity error detected in egress buffer RAM.
18	FC_ABM_PAR_ERR_PRAM	Minor	ATM chipset, external pointer RAM parity error detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.
19	FC_ABM_PRAM_ILL_ERROR	Minor	ATM chipset, ingress linked list empty. Cell processing halts until pointers become available.
20	FC_ABM_PRAM_ELL_ERROR	Minor	ATM chipset, egress linked list empty. Cell processing halts until pointers become available.
21	FC_ABM_PRAM_EIPLL_ERROR	Minor	ATM chipset, egress IP free list empty. Cell processing halts until pointers become available.
22	FC_ABM_ING_SYNC_ERROR	Minor	ATM chipset, cell dropped due to ingress UTOPIA sync error.
23	FC_ABM_EG_SYNC_ERROR	Minor	ATM chipset, cell dropped due to egress UTOPIA sync error.
24	FC_ABM_PTR_MEM_TEST_FAILURE	Minor	ATM chipset, diagnostic detected external memory failure.
25	FC_ASX_CRCERR	Minor	ATM chipset, CRC error detected on incoming cell. Cell dropped.
26	FC_ASX_IPRTOERR	Minor	ATM chipset, input port overrun error.
27	FC_ASX_LLERR	Minor	ATM chipset, linked list error detected. Fabric control driver software must reset and re-initialize the device.
28	FC_ASX_PARITY_ERR	Minor	ATM chipset, input parity error detected. Cell dropped.
29	FC_CD_INIT_FAILURE	Minor	Cell delineator initialization failure.
30	FC_SONET_INIT_FAILURE	Minor	OC3 hardware initialization failure.
31	NO_IPC_QUEUE_DEFINED	Minor	IPC does not recognize User Plane queue request.
32	FC_CD_RX_ERROR	Minor	Cell Delineator receive error.
33	FC_CD_TX_ERROR	Minor	Cell Delineator transmit error.
34	FC_CD_CFG_FAILURE	Minor	Cell Delineator configuration failure.
38	FC_ABM_BP_OVERRIDE	Minor	ATM chipset, backpressure indications from switch are being overridden to prevent cell loss.
39	FC_ATM_CNX_FAIL_ERROR	Info	Fabric control was unable to complete a requested connection.
42	FC_SUBTEND_PORT_BUFFER_OVERFLOW	Info	Buffer overflow in the cell buffer on the subtend module.
43	FC_SUBTEND_PORT_UTOPIA_ERROR	Info	Error in UTOPIA chip.
46	FC_SUBTEND_PORT_EGRESS_PARITY	Info	Parity error in cell egress path.

ID	Definition	Severity	Description
48	FC_OC3_LCD_FAULT	Info	SONET, loss of cell delineation.
49	FC_OC3_OCD_FAULT	Critical	SONET, out of cell delineation.
50	FC_OC3_FIFO_FULL	Critical	SONET, framer FIFO overflow.
51	FC_OC3_C2_MISMATCH	Critical	SONET, received payload incorrect type.
52	FC_OC3_PRDI	Critical	SONET, path RDI received.
53	FC_OC3_PAIS	Critical	SONET, path AIS received.
54	FC_OC3_APS_CHANGE	Critical	SONET, auto protection switch.
55	FC_OC3_APS_IAB	Minor	SONET, auto protection switch byte is corrupted 3 of 12 times.
56	FC_OC3_POINTER_CHANGE	Info	SONET, data pointer changed.
57	FC_OC3_LOP	Critical	SONET, loss of pointer condition.
58	FC_OC3_LRDI	Critical	SONET, line RDI received.
59	FC_OC3_LAIS	Critical	SONET, line AIS received.
60	FC_OC3_LOF	Info	SONET, loss of frame condition.
61	FC_OC3_OOF	Critical	SONET, out of frame condition detected.
62	FC_OC3_LOSY	Critical	SONET, loss of signal detected by optical transceiver.
63	FC_OC3_LOS	Critical	SONET, loss of signal detected by SONET device.

ID	Definition	Severity	Description
81	FC_DS3_OCD	Critical	DS3, out of cell delineation.
82	FC_DS3_FIFO_FULL	Minor	DS3, framer FIFO overflow.
83	FC_DS3_IDLE	Critical	DS3, receiving idle.
84	FC_DS3_RAI	Critical	DS3, receiving remote alarm indication.
90	FC_DS3_YELLOW	Critical	DS3, receiving yellow alarm.
91	FC_DS3_AIS	Critical	DS3, receiving AIS.
93	FC_DS3_OOF	Critical	DS3, out of frame condition detected.
94	FC_DS3_LIU_LOS	Critical	DS3, loss of signal detected at LIU.
95	FC_DS3_LOS	Critical	DS3, loss of signal detected at framer.
96	FC_DS3_TX_PARITY	Minor	DS3, parity error detected on transmit UTOPIA bus.
97	FC_DS3_RX_PARITY	Minor	DS3, HEC error detected on receive UTOPIA bus.
99	FC_DS3_CPAR	Info	DS3, unexpected frame format.
101	FC_DS3_PLCP_OOF	Minor	DS3, PLCP out of frame condition detected.
102	FC_DS3_PLCP_LOF	Minor	DS3, PLCP loss of frame error detected.

ID	Definition	Severity	Description
128	LR_CREATE_OBJ	Info	Module was detected.
129	LR_PING_FAIL	Critical	Module did not respond to the system monitor.
42	FC_SUBTEND_PORT_BUFFER_OVERFLOW	Info	Buffer overflow in the cell buffer on the subtend module.
44	FC_SUBTEND_PORT_INGRESS_HEC	Info	Subtend port ingress HEC error.

ID	Definition	Severity	Description
3	SCL_OUT_OF_MEMORY	Critical	Application was unable to allocate memory.
128	LR_CREATE_OBJ	Info	Module was detected.
129	LR_PING_FAIL	Critical	Module did not respond to system monitor.

ID	Definition	Severity	Description
1	FMEVENT_LIM_DOH_CALIBRATION_FAILURE	Major	LIM was not able to perform Digital Off-Hook (DOH) calibration.
3	FMEVENT_LIM_CONNECT_FAILURE	Major	LIM was not able to connect to the switching matrix.
128	LR_CREATE_OBJ	Info	Module was detected.
129	LR_PING_FAIL	Critical	Module did not respond to system monitor.

ID	Definition	Severity	Description
1	SLOT_MISMATCH_EVENT	Minor	A module was inserted in the slot that did not match the type that was pre-provisioned for that slot.
2	SLOT_INVALID_EVENT	Minor	A module that was not valid for the slot was inserted in the slot.
3	SLOT_NO_IMAGE_EVENT	Minor	No image exists for the type module present in the slot.
4	SLOT_IMAGE_NOT_READY	Minor	Image for download is not ready
5	SLOT_DOWNLOAD_START	Info	Download of a module image to the identified slot has begun.
6	SLOT_DOWNLOAD_COMP	Info	Download of a module image to the identified slot has completed.
7	SLOT_DOWNLOAD_FAIL	Info	Download of a module image to the identified slot has failed.
8	SLOT_CURR_IMG_FAIL	Minor	Image could not be obtained for module in slot.

ID	Definition	Severity	Description
1	MUM_TFTPING_FAULT	Minor	TFTP file download failure
2	MUM_TFTP_SUCCESSFUL	Info	TFTP file download successful
3	MUM_TFTP_TIMEOUT_FAULT	Minor	TFTP timeout incurred during download
4	MUM_FILE_NOT_FOUND_FAULT	Minor	Requested TFTP file not found
5	MUM_CHKSUM_FAIL_FAULT	Minor	Checksum failed on TFTP file download
6	MUM_SIZE_CHK_FAULT	Minor	File size check failed on TFTP file download
7	MUM_DB_WRITE_FAULT	Minor	TFTP file transfer failed; image could not be written to 6100 database
8	MUM_NO_SPACE_FAULT	Minor	Insufficient SC memory to contained TFTP'd image
9	MUM_TFTP_GENERAL_FAULT	Minor	TFTP file transfer failed

Table 5-2: ATU-C Module Alarms (Reference)

ID Definition Severity Description

2

SAC_SOFTWARE_FAILED_CRC

Major

Software failed CRC check during download.

3

SAC_OUT_OF_MEMORY

Critical

Application was unable to allocate memory.

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to system monitor.

Table 5-3:

ID Definition Severity Description

2

SC_IP_MISMATCH

Minor

The IP number assigned to the 6100 is unusable.

3

SC_SUBNET_ERROR

Minor

The subnet mask for the IP number is incorrect.

4

SC_DOWNLOAD_DONE

Info

Download to the SC is complete.

127

Critical

Loss of communication with SC

System Controller Alarms (Reference)
Table 5-4:

ID Definition Severity Description

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to the system monitor.

Network Interface General Alarms (Reference)
Table 5-5:

ID Definition Severity Description

0

FC_ALM_EXT_MEM_PAR_ERR

Minor

ATM chipset external memory parity error.

1

FC_ALM_IN_RCV_PAR_ERR

Minor

ATM chipset, cell dropped due to ingress receive side UTOPIA bus parity error.

2

FC_ALM_EG_RCV_PAR_ERR

Minor

ATM chipset, cell dropped due to egress receive side UTOPIA bus parity error.

3

FC_ALM_UTOPIA_SYNC_ERR

Minor

ATM chipset, UTOPIA bus synchronization error detected.

4

FC_ALM_POL_EU_TIMEOUT_ERR

Minor

ATM chipset, parity error detected on policing EU word access.

5

FC_ALM_VCI_SIZE_ERR

Minor

ATM chipset, ingress VCI value above max value.

6

FC_ALM_VPI_SIZE_ERR

Minor

ATM chipset, ingress VPI value above max value.

7

FC_ALM_MPHY_PORT_OVERRUN

Minor

ATM chipset, ingress UTOPIA synchronization error detected.

8

FC_ALM_IN_FIFO_FULL

Minor

ATM chipset, ingress cells are being dropped due to ingress capture fifo full condition. Fabric control driver software will attempt to clear the condition.

9

FC_ALM_EG_CAP_SYNC_ERR

Minor

ATM chipset, an egress capture fifo synchronization error is detected. The device will be reset by fabric control driver software. Device must be re-initialized and connections re-established.

10

FC_ALM_IN_CAP_SYNC_ERR

Minor

ATM chipset, an ingress capture fifo synchronization error is detected. The device will be reset by fabric control driver software. Device must be re-initialized and connections re-established.

11

FC_ALM_INSERT_SYNC_ERR

Minor

ATM chipset, ingress insertion fifo synch error. Fabric control driver software resets fifo.

12

FC_ALM_FULL_MEM_TEST_FAILURE

Minor

ATM chipset, diagnostic memory test detects memory failure.

13

FC_ABM_SEQ_ERROR_ILL

Minor

ATM chipset, a sequence error in the ingress linked list was detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.

14

FC_ABM_PAR_ERR_ING_CELL

Minor

ATM chipset, cell dropped due to ingress parity error.

15

FC_ABM_SEQ_ERROR_ELL

Minor

ATM chipset, a sequence error in the egress linked list was detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.

16

FC_ABM_PAR_ERR_ING_STORED

Minor

ATM chipset, parity error detected in ingress buffer RAM.

17

FC_ABM_PAR_ERR_ING_STORED

Minor

ATM chipset, parity error detected in egress buffer RAM.

18

FC_ABM_PAR_ERR_PRAM

Minor

ATM chipset, external pointer RAM parity error detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.

19

FC_ABM_PRAM_ILL_ERROR

Minor

ATM chipset, ingress linked list empty. Cell processing halts until pointers become available.

20

FC_ABM_PRAM_ELL_ERROR

Minor

ATM chipset, egress linked list empty. Cell processing halts until pointers become available.

21

FC_ABM_PRAM_EIPLL_ERROR

Minor

ATM chipset, egress IP free list empty. Cell processing halts until pointers become available.

22

FC_ABM_ING_SYNC_ERROR

Minor

ATM chipset, cell dropped due to ingress UTOPIA sync error.

23

FC_ABM_EG_SYNC_ERROR

Minor

ATM chipset, cell dropped due to egress UTOPIA sync error.

24

FC_ABM_PTR_MEM_TEST_FAILURE

Minor

ATM chipset, diagnostic detected external memory failure.

25

FC_ASX_CRCERR

Minor

ATM chipset, CRC error detected on incoming cell. Cell dropped.

26

FC_ASX_IPRTOERR

Minor

ATM chipset, input port overrun error.

27

FC_ASX_LLERR

Minor

ATM chipset, linked list error detected. Fabric control driver software must reset and re-initialize the device.

28

FC_ASX_PARITY_ERR

Minor

ATM chipset, input parity error detected. Cell dropped.

29

FC_CD_INIT_FAILURE

Minor

Cell delineator initialization failure.

30

FC_SONET_INIT_FAILURE

Minor

OC3 hardware initialization failure.

31

NO_IPC_QUEUE_DEFINED

Minor

IPC does not recognize User Plane queue request.

32

FC_CD_RX_ERROR

Minor

Cell Delineator receive error.

33

FC_CD_TX_ERROR

Minor

Cell Delineator transmit error.

34

FC_CD_CFG_FAILURE

Minor

Cell Delineator configuration failure.

38

FC_ABM_BP_OVERRIDE

Minor

ATM chipset, backpressure indications from switch are being overridden to prevent cell loss.

39

FC_ATM_CNX_FAIL_ERROR

Info

Fabric control was unable to complete a requested connection.

42

FC_SUBTEND_PORT_BUFFER_OVERFLOW

Info

Buffer overflow in the cell buffer on the subtend module.

43

FC_SUBTEND_PORT_UTOPIA_ERROR

Info

Error in UTOPIA chip.

46

FC_SUBTEND_PORT_EGRESS_PARITY

Info

Parity error in cell egress path.

ATM Fabric Alarms (Reference)
Table 5-6:

ID Definition Severity Description

48

FC_OC3_LCD_FAULT

Info

SONET, loss of cell delineation.

49

FC_OC3_OCD_FAULT

Critical

SONET, out of cell delineation.

50

FC_OC3_FIFO_FULL

Critical

SONET, framer FIFO overflow.

51

FC_OC3_C2_MISMATCH

Critical

SONET, received payload incorrect type.

52

FC_OC3_PRDI

Critical

SONET, path RDI received.

53

FC_OC3_PAIS

Critical

SONET, path AIS received.

54

FC_OC3_APS_CHANGE

Critical

SONET, auto protection switch.

55

FC_OC3_APS_IAB

Minor

SONET, auto protection switch byte is corrupted 3 of 12 times.

56

FC_OC3_POINTER_CHANGE

Info

SONET, data pointer changed.

57

FC_OC3_LOP

Critical

SONET, loss of pointer condition.

58

FC_OC3_LRDI

Critical

SONET, line RDI received.

59

FC_OC3_LAIS

Critical

SONET, line AIS received.

60

FC_OC3_LOF

Info

SONET, loss of frame condition.

61

FC_OC3_OOF

Critical

SONET, out of frame condition detected.

62

FC_OC3_LOSY

Critical

SONET, loss of signal detected by optical transceiver.

63

FC_OC3_LOS

Critical

SONET, loss of signal detected by SONET device.

Network Interface OC3 Alarms (Reference)
Table 5-7:

ID Definition Severity Description

81

FC_DS3_OCD

Critical

DS3, out of cell delineation.

82

FC_DS3_FIFO_FULL

Minor

DS3, framer FIFO overflow.

83

FC_DS3_IDLE

Critical

DS3, receiving idle.

84

FC_DS3_RAI

Critical

DS3, receiving remote alarm indication.

90

FC_DS3_YELLOW

Critical

DS3, receiving yellow alarm.

91

FC_DS3_AIS

Critical

DS3, receiving AIS.

93

FC_DS3_OOF

Critical

DS3, out of frame condition detected.

94

FC_DS3_LIU_LOS

Critical

DS3, loss of signal detected at LIU.

95

FC_DS3_LOS

Critical

DS3, loss of signal detected at framer.

96

FC_DS3_TX_PARITY

Minor

DS3, parity error detected on transmit UTOPIA bus.

97

FC_DS3_RX_PARITY

Minor

DS3, HEC error detected on receive UTOPIA bus.

99

FC_DS3_CPAR

Info

DS3, unexpected frame format.

101

FC_DS3_PLCP_OOF

Minor

DS3, PLCP out of frame condition detected.

102

FC_DS3_PLCP_LOF

Minor

DS3, PLCP loss of frame error detected.

Network Interface DS3 Alarms (Reference)
Table 5-8: Subtend Host Module Alarms (Reference)

ID Definition Severity Description

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to the system monitor.

42

FC_SUBTEND_PORT_BUFFER_OVERFLOW

Info

Buffer overflow in the cell buffer on the subtend module.

44

FC_SUBTEND_PORT_INGRESS_HEC

Info

Subtend port ingress HEC error.

Table 5-9:

ID Definition Severity Description

3

SCL_OUT_OF_MEMORY

Critical

Application was unable to allocate memory.

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to system monitor.

LIM Control Module Alarms (Reference)
Table 5-10:

ID Definition Severity Description

1

FMEVENT_LIM_DOH_CALIBRATION_FAILURE

Major

LIM was not able to perform Digital Off-Hook (DOH) calibration.

3

FMEVENT_LIM_CONNECT_FAILURE

Major

LIM was not able to connect to the switching matrix.

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to system monitor.

Line Interface Module Alarms (Reference)
Table 5-11:

ID Definition Severity Description

1

SLOT_MISMATCH_EVENT

Minor

A module was inserted in the slot that did not match the type that was pre-provisioned for that slot.

2

SLOT_INVALID_EVENT

Minor

A module that was not valid for the slot was inserted in the slot.

3

SLOT_NO_IMAGE_EVENT

Minor

No image exists for the type module present in the slot.

4

SLOT_IMAGE_NOT_READY

Minor

Image for download is not ready

5

SLOT_DOWNLOAD_START

Info

Download of a module image to the identified slot has begun.

6

SLOT_DOWNLOAD_COMP

Info

Download of a module image to the identified slot has completed.

7

SLOT_DOWNLOAD_FAIL

Info

Download of a module image to the identified slot has failed.

8

SLOT_CURR_IMG_FAIL

Minor

Image could not be obtained for module in slot.

Slot Alarms (Reference)
Table 5-12: Software Download Alarms (Reference)

ID Definition Severity Description

1

MUM_TFTPING_FAULT

Minor

TFTP file download failure

2

MUM_TFTP_SUCCESSFUL

Info

TFTP file download successful

3

MUM_TFTP_TIMEOUT_FAULT

Minor

TFTP timeout incurred during download

4

MUM_FILE_NOT_FOUND_FAULT

Minor

Requested TFTP file not found

5

MUM_CHKSUM_FAIL_FAULT

Minor

Checksum failed on TFTP file download

6

MUM_SIZE_CHK_FAULT

Minor

File size check failed on TFTP file download

7

MUM_DB_WRITE_FAULT

Minor

TFTP file transfer failed; image could not be written to 6100 database

8

MUM_NO_SPACE_FAULT

Minor

Insufficient SC memory to contained TFTP'd image

9

MUM_TFTP_GENERAL_FAULT

Minor

TFTP file transfer failed

5.2 ATU-C Module Alarms

There are a number of events that could cause alarms in the 6100 system. Many of those events return messages that are informational only. Others are warnings or minor alarm conditions (those affecting few subscribers). Others are major or critical alarms which require prompt attention in case they affect a large number of subscribers.

The following table lists ATU-C module event codes, providing their IDs, definition, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

ID	Definition	Severity	Description
2	SAC_SOFTWARE_FAILED_CRC	Major	Software failed CRC check during download.
3	SAC_OUT_OF_MEMORY	Critical	Application was unable to allocate memory.
128	LR_CREATE_OBJ	Info	Module was detected.
129	LR_PING_FAIL	Critical	Module did not respond to system monitor.

Table 5-13: ATU-C Module Alarms

ID Definition Severity Description

2

SAC_SOFTWARE_FAILED_CRC

Major

Software failed CRC check during download.

3

SAC_OUT_OF_MEMORY

Critical

Application was unable to allocate memory.

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to system monitor.

5.2.1 Software failed CRC check during download (2)

Alarm Summary

ID	Alarm Name	Severity
2	SAC_SOFTWARE_FAILED_CRC	Major

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Software failed CRC check during download.

Description
Software failed CRC check during download.

Impact

Events of this type are not "run-time" events. They occur only during module power up and self-test, and are therefore non-service affecting (since subscriber service is typically not active yet). The module will fail self-test as a result of this event, and immediately retry the self-test. A self-test failure message will be generated with each failure, and this will occur infinitely. That is, the module will never complete a successful self-test. Without a successful self-test, the module cannot be put into service, so the node will not complete its installation cycle.

Software update events are coded to this category as well, as it is assumed that s/w updates are always monitored by an operator and therefore it is less important to code events as "critical" since the goal is to monitor node status until it becomes fully operational anyway.

Action

1. Alarms of this type are generated only during module initialization and will force a module reset automatically.

2. If reset condition continues (module never comes out of self-test mode), reinsert the module.

3. If problem persists, replace module.

5.2.2 Application unable to allocate memory (3)

Alarm Summary

ID	Alarm Name	Severity
3	SAC_OUT_OF_MEMORY	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Application was unable to allocate memory.

Description
Application was unable to allocate memory.

Impact

Events of this type would normally be tagged as "Minor", but for Release 2.0 still need to be maintained as "Critical" to preserve node software's need to couple event severity from service state impact. These will be de-coupled post Release 2.0, and this category will cease to exist.

Action

1. In some cases, a module will force itself into a self-test based on the alarm condition. In other cases, the SC will force the alarmed module to reset. A module reset forces the module to be power cycled, self-tested, and re-configured into the slot by the SC.

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.2.3 Module detected (128)

Alarm Summary

ID	Alarm Name	Severity
128	LR_CREATE_OBJ	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module was detected.

Description
Module was detected.

Impact

Events of this type are benevolent, and are not indicative of service impairment or loss.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.2.4 Module not responding to system monitor (129)

Alarm Summary

ID	Alarm Name	Severity
129	LR_PING_FAIL	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module did not respond to the system monitor.

Description
Module did not respond to the system monitor.

Impact

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.3 System Controller Alarms

The following table lists SC event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

ID	Definition	Severity	Description
2	SC_IP_MISMATCH	Minor	The IP number assigned to the 6100 is unusable.
3	SC_SUBNET_ERROR	Minor	The subnet mask for the IP number is incorrect.
4	SC_DOWNLOAD_DONE	Info	Download to the SC is complete.
127		Critical	Loss of communication with SC

Table 5-14: System Controller Alarms (Reference)

ID Definition Severity Description

2

SC_IP_MISMATCH

Minor

The IP number assigned to the 6100 is unusable.

3

SC_SUBNET_ERROR

Minor

The subnet mask for the IP number is incorrect.

4

SC_DOWNLOAD_DONE

Info

Download to the SC is complete.

127

Critical

Loss of communication with SC

5.3.1 IP number for the 6100 is unusable (2)

Alarm Summary

ID	Alarm Name	Severity
2	SC_IP_MISMATCH	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

The IP number assigned to the 6100 is unusable.

Description
The IP number assigned to the 6100 is unusable.

Impact

Events of this type are not "run-time" events. They occur only during node installation/configuration and only affect the node's ability to properly communicate over Ethernet.

Action

1. Refer to the ViewRunner for Windows Set Up and Installation Manual, "The Cisco 6100 Initialization Procedure" chapter for re-establishing proper IP address information.

2. Verify that ViewRunner can access node correctly.

5.3.2 Subnet mask for IP is incorrect (3)

Alarm Summary

ID	Alarm Name	Severity
3	SC_SUBNET_ERROR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

The subnet mask for the IP number is incorrect.

Impact

Events of this type are not "run-time" events. They occur only during node installation/configuration and only affect the node's ability to properly communicate over Ethernet.

Action

1. Refer to the ViewRunner for Windows Set Up and Installation Manual, "The Cisco 6100 Initialization Procedure" chapter for re-establishing proper IP address information.

2. Verify that ViewRunner can access node correctly.

5.3.3 Download to SC complete (4)

Alarm Summary

ID	Alarm Name	Severity
4	SC_DOWNLOAD_DONE	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Download to the SC is complete.

Impact

Events of this type are not "run-time" events. They occur only during node installation/configuration and only affect the node's ability to properly communicate over Ethernet.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.3.4 Loss of communication with SC (127)

Alarm Summary

ID	Alarm Name	Severity
127		Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Loss of communication with SC.

Impact

An event of this type will most likely result in loss of a single cell. Loss of a single cell is a transient event, affects only one subscriber, and is recoverable at higher layers in the protocol stack. Multiple occurrences of the event are more serious, typically indicative of a failed hardware component on the ATM Switch Module (ASM). Multiple occurrences are defined as more than a couple of occurrences in a short period of time (on the order seconds). If a problem with cell loss, and ultimately subscriber traffic throughout is suspected, service personnel should review the ViewRunner History Event Log for multiple occurrences. In a future software release, multiple occurrences will cause a threshold to be crossed, generating a higher severity alarm.

Action

1. Alarms of this type are typically due to short term (milliseconds in duration) incidents that will clear as a normal course of traffic management (buffer space becomes available, parity error recovered at a higher layer, brief loss of signal, etc.).

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.4 Network Interface General Alarms

The following table lists NI event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

Table 5-15: Network Interface General Alarms

ID Definition Severity Description

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to the system monitor.

5.4.1 Module detected (128)

Alarm Summary

ID	Alarm Name	Severity
128	LR_CREATE_OBJ	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module was detected.

Impact

Events of this type are benevolent, and are not indicative of service impairment or loss.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.4.2 Module not responding to system monitor (129)

Alarm Summary

ID	Alarm Name	Severity
129	LR_PING_FAIL	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module did not respond to the system monitor.

Impact

An event of this severity will cause loss of service for more than four subscribers. Examples include:

Loss of a LIM controller could cause loss of service for up to 80 subscribers.
Loss of an NI could cause loss of service for 64-400 subscribers, depending upon configuration.

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.5 Network Interface ATM Fabric Alarms

The following table lists ATM fabric event codes relative to the NI module, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

Table 5-16: ATM Fabric Alarms (Reference)

ID Definition Severity Description

0

FC_ALM_EXT_MEM_PAR_ERR

Minor

ATM chipset external memory parity error.

1

FC_ALM_IN_RCV_PAR_ERR

Minor

ATM chipset, cell dropped due to ingress receive side UTOPIA bus parity error.

2

FC_ALM_EG_RCV_PAR_ERR

Minor

ATM chipset, cell dropped due to egress receive side UTOPIA bus parity error.

3

FC_ALM_UTOPIA_SYNC_ERR

Minor

ATM chipset, UTOPIA bus synchronization error detected.

4

FC_ALM_POL_EU_TIMEOUT_ERR

Minor

ATM chipset, parity error detected on policing EU word access.

5

FC_ALM_VCI_SIZE_ERR

Minor

ATM chipset, ingress VCI value above max value.

6

FC_ALM_VPI_SIZE_ERR

Minor

ATM chipset, ingress VPI value above max value.

7

FC_ALM_MPHY_PORT_OVERRUN

Minor

ATM chipset, ingress UTOPIA synchronization error detected.

8

FC_ALM_IN_FIFO_FULL

Minor

ATM chipset, ingress cells are being dropped due to ingress capture fifo full condition. Fabric control driver software will attempt to clear the condition.

9

FC_ALM_EG_CAP_SYNC_ERR

Minor

ATM chipset, an egress capture fifo synchronization error is detected. The device will be reset by fabric control driver software. Device must be re-initialized and connections re-established.

10

FC_ALM_IN_CAP_SYNC_ERR

Minor

ATM chipset, an ingress capture fifo synchronization error is detected. The device will be reset by fabric control driver software. Device must be re-initialized and connections re-established.

11

FC_ALM_INSERT_SYNC_ERR

Minor

ATM chipset, ingress insertion fifo synch error. Fabric control driver software resets fifo.

12

FC_ALM_FULL_MEM_TEST_FAILURE

Minor

ATM chipset, diagnostic memory test detects memory failure.

13

FC_ABM_SEQ_ERROR_ILL

Minor

ATM chipset, a sequence error in the ingress linked list was detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.

14

FC_ABM_PAR_ERR_ING_CELL

Minor

ATM chipset, cell dropped due to ingress parity error.

15

FC_ABM_SEQ_ERROR_ELL

Minor

ATM chipset, a sequence error in the egress linked list was detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.

16

FC_ABM_PAR_ERR_ING_STORED

Minor

ATM chipset, parity error detected in ingress buffer RAM.

17

FC_ABM_PAR_ERR_ING_STORED

Minor

ATM chipset, parity error detected in egress buffer RAM.

18

FC_ABM_PAR_ERR_PRAM

Minor

ATM chipset, external pointer RAM parity error detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.

19

FC_ABM_PRAM_ILL_ERROR

Minor

ATM chipset, ingress linked list empty. Cell processing halts until pointers become available.

20

FC_ABM_PRAM_ELL_ERROR

Minor

ATM chipset, egress linked list empty. Cell processing halts until pointers become available.

21

FC_ABM_PRAM_EIPLL_ERROR

Minor

ATM chipset, egress IP free list empty. Cell processing halts until pointers become available.

22

FC_ABM_ING_SYNC_ERROR

Minor

ATM chipset, cell dropped due to ingress UTOPIA sync error.

23

FC_ABM_EG_SYNC_ERROR

Minor

ATM chipset, cell dropped due to egress UTOPIA sync error.

24

FC_ABM_PTR_MEM_TEST_FAILURE

Minor

ATM chipset, diagnostic detected external memory failure.

25

FC_ASX_CRCERR

Minor

ATM chipset, CRC error detected on incoming cell. Cell dropped.

26

FC_ASX_IPRTOERR

Minor

ATM chipset, input port overrun error.

27

FC_ASX_LLERR

Minor

ATM chipset, linked list error detected. Fabric control driver software must reset and re-initialize the device.

28

FC_ASX_PARITY_ERR

Minor

ATM chipset, input parity error detected. Cell dropped.

29

FC_CD_INIT_FAILURE

Minor

Cell delineator initialization failure.

30

FC_SONET_INIT_FAILURE

Minor

OC3 hardware initialization failure.

31

NO_IPC_QUEUE_DEFINED

Minor

IPC does not recognize User Plane queue request.

32

FC_CD_RX_ERROR

Minor

Cell Delineator receive error.

33

FC_CD_TX_ERROR

Minor

Cell Delineator transmit error.

34

FC_CD_CFG_FAILURE

Minor

Cell Delineator configuration failure.

38

FC_ABM_BP_OVERRIDE

Minor

ATM chipset, backpressure indications from switch are being overridden to prevent cell loss.

39

FC_ATM_CNX_FAIL_ERROR

Info

Fabric control was unable to complete a requested connection.

42

FC_SUBTEND_PORT_BUFFER_OVERFLOW

Info

Buffer overflow in the cell buffer on the subtend module.

43

FC_SUBTEND_PORT_UTOPIA_ERROR

Info

Error in UTOPIA chip.

46

FC_SUBTEND_PORT_EGRESS_PARITY

Info

Parity error in cell egress path.

5.5.1 ATM external memory parity error (0)

Alarm Summary

ID	Alarm Name	Severity
0	FC_ALM_EXT_MEM_PAR_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset external memory parity error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.2 ATM ingress receive side UTOPIA bus parity error (1)

Alarm Summary

ID	Alarm Name	Severity
1	FC_ALM_IN_RCV_PAR_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, cell dropped due to ingress receive UTOPIA bus parity error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.3 ATM egress receive side UTOPIA bus parity error (2)

Alarm Summary

ID	Alarm Name	Severity
2	FC_ALM_EG_RCV_PAR_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, cell dropped due to egress receive side UTOPIA bus parity error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.4 ATM UTOPIA bus synchronization error (3)

Alarm Summary

ID	Alarm Name	Severity
3	FC_ALM_UTOPIA_SYNC_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, UTOPIA bus synchronization error detected.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.5 ATM parity error on policing EU word access (4)

Alarm Summary

ID	Alarm Name	Severity
4	FC_ALM_POL_EU_TIMEOUT_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, parity error detected on policing EU word access.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.6 ATM ingress VCI value above max (5)

Alarm Summary

ID	Alarm Name	Severity
5	FC_ALM_VCI_SIZE_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, ingress VCI value above the max value.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.7 ATM ingress VPI value above max (6)

Alarm Summary

ID	Alarm Name	Severity
6	FC_ALM_VPI_SIZE_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, ingress VPI value above the max value.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.8 ATM ingress UTOPIA synchronization error (7)

Alarm Summary

ID	Alarm Name	Severity
7	FC_ALM_MPHY_PORT_OVERRUN	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, ingress UTOPIA synchronization error detected.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.9 ATM ingress capture FIFO full (8)

Alarm Summary

ID	Alarm Name	Severity
8	FC_ALM_IN_FIFO_FULL	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, ingress cells are being dropped due to ingress capture FIFO full condition. Fabric control driver software will attempt to clear the condition.

Impact

An event of this type will cause an automatic recovery attempt by the ASM fabric control driver software. The duration of the automatic recovery should be on the order of milliseconds. As such, service is only momentarily impaired, is recoverable at higher layers, and is most likely transparent from an application level perspective.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.10 ATM egress FIFO capture synchronization error (9)

Alarm Summary

ID	Alarm Name	Severity
9	FC_ALM_EG_CAP_SYNC_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, an egress capture FIFO synchronization error is detected. The device will be reset by the fabric control driver software. Device must be re-initialized and connections re-established.

Impact

An event of this type will result in an ATM Switch Module reset. The service-affecting period will typically be 45 seconds in duration. ADSL layer 1 connections will not be lost, but subscriber data traffic (ATM AAL5 cells) will not be switched across the switch fabric during this period.

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.5.11 ATM ingress FIFO capture synchronization error (10)

Alarm Summary

ID	Alarm Name	Severity
10	FC_ALM_IN_CAP_SYNC_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, an ingress capture FIFO synchronization error is detected. The device will be reset by the fabric control driver software. Device must be re-initialized and connections re-established.

Impact

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.5.12 ATM ingress insertion FIFO sync error (11)

Alarm Summary

ID	Alarm Name	Severity
11	FC_ALM_INSERT_SYNC_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, ingress insertion FIFO synch error. Fabric control driver software resets FIFO.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.13 ATM diagnostic detects memory failure (12)

Alarm Summary

ID	Alarm Name	Severity
12	FC_ALM_FULL_MEM_TEST_FAILURE	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, diagnostic memory test detects memory failure.

Impact

Action

1. Alarms of this type are generated only during module initialization and will force a module reset automatically.

2. If reset condition continues (module never comes out of self-test mode), reinsert the module.

3. If problem persists, replace module.

5.5.14 ATM sequence error in ingress linked list (13)

Alarm Summary

ID	Alarm Name	Severity
13	FC_ABM_SEQ_ERROR_ILL	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, a sequence error in the ingress linked list is detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.5.15 ATM cell dropped due to ingress parity error (14)

Alarm Summary

ID	Alarm Name	Severity
14	FC_ABM_PAR_ERR_ING_CELL	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, cell dropped due to ingress parity error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.16 ATM sequence error in egress linked list (15)

Alarm Summary

ID	Alarm Name	Severity
15	FC_ABM_SEQ_ERROR_ELL	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, sequence error in egress linked list is detected. Fabric control driver software will reset, and re-initialize the device. Connections must be re-established.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.5.17 ATM parity error in ingress buffer RAM (16)

Alarm Summary

ID	Alarm Name	Severity
16	FC_ABM_PAR_ERR_ING_STORED	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, parity error detected in ingress buffer RAM.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.18 ATM parity error in egress buffer RAM (17)

Alarm Summary

ID	Alarm Name	Severity
17	FC_ABM_PAR_ERR_EG_STORED	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, parity error detected in egress buffer RAM.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.19 ATM external pointer RAM parity error (18)

Alarm Summary

ID	Alarm Name	Severity
18	FC_ABM_PAR_ERR_PRAM	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, external pointer RAM error detected. Fabric control driver software will reset and re-initialize the device. Connections must be re-established.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.5.20 ATM ingress linked list empty (19)

Alarm Summary

ID	Alarm Name	Severity
19	FC_ABM_PRAM_ILL_ERROR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, ingress linked list empty. Cell processing halts until pointers become available.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.5.21 ATM egress linked list empty (20)

Alarm Summary

ID	Alarm Name	Severity
20	FC_ABM_PRAM_ELL_ERROR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, egress linked list empty. Cell processing halts until pointers become available.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.5.22 ATM egress IP free list empty (21)

Alarm Summary

ID	Alarm Name	Severity
21	FC_ABM_PRAM_EIPLL_ERROR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, egress IP free list empty. Cell processing halts until pointers become available.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.5.23 ATM ingress UTOPIA sync error (22)

Alarm Summary

ID	Alarm Name	Severity
22	FC_ABM_ING_SYNC_ERROR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, cell dropped due to ingress UTOPIA sync error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.24 ATM egress UTOPIA sync error (23)

Alarm Summary

ID	Alarm Name	Severity
23	FC_ABM_EG_SYNC_ERROR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, cell dropped due to egress UTOPIA sync error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.25 ATM external memory failure (24)

Alarm Summary

ID	Alarm Name	Severity
24	FC_ABM_PTR_MEM_TEST_FAILURE	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, diagnostic detected external memory failure.

Impact

Action

1. Alarms of this type are generated only during module initialization and will force a module reset automatically.

2. If reset condition continues (module never comes out of self-test mode), reinsert the module.

3. If problem persists, replace module.

5.5.26 ATM incoming CRC error (25)

Alarm Summary

ID	Alarm Name	Severity
25	FC_ASX_CRCERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, CRC error detected on incoming cell, cell dropped.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.27 ATM input port overrun (26)

Alarm Summary

ID	Alarm Name	Severity
26	FC_ASX_IPRTOERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, input port overrun error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.28 ATM linked list error (27)

Alarm Summary

ID	Alarm Name	Severity
27	FC_ASX_LLERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, linked list error detected. Fabric control driver software must reset and re-initialize the device.

Impact

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.5.29 ATM input parity error (28)

Alarm Summary

ID	Alarm Name	Severity
28	FC_ASX_PARITY_ERR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, input parity error detected, cell dropped.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.30 Cell delineator initialization failure (29)

Alarm Summary

ID	Alarm Name	Severity
29	FC_CD_INIT_FAILURE	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Cell delineator initialization failure.

Impact

Action

1. Alarms of this type are generated only during module initialization and will force a module reset automatically.

2. If reset condition continues (module never comes out of self-test mode), reinsert the module.

3. If problem persists, replace module.

5.5.31 OC3 hardware initialization failure (30)

Alarm Summary

ID	Alarm Name	Severity
30	FC_SONET_INIT_FAILURE	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

OC3 hardware initialization failure.

Impact

Action

1. Alarms of this type are generated only during module initialization and will force a module reset automatically.

2. If reset condition continues (module never comes out of self-test mode), reinsert the module.

3. If problem persists, replace module.

5.5.32 IPC does not recognize queue request (31)

Alarm Summary

ID	Alarm Name	Severity
31	NO_IPC_QUEUE_DEFINED	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

IPC does not recognize a User Plane queue request.

Impact

The event is not propagated from the module to Fault Manager, and will not be registered in the ViewRunner Event History Window.

Action

1. Alarms of this type are generated only during module initialization and will force a module reset automatically.

2. If reset condition continues (module never comes out of self-test mode), reinsert the module.

3. If problem persists, replace module.

5.5.33 Cell delineator receive error (32)

Alarm Summary

ID	Alarm Name	Severity
32	FC_CD_RX_ERROR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Cell delineator receive error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.34 Cell delineator transmit error (33)

Alarm Summary

ID	Alarm Name	Severity
33	FC_CD_TX_ERROR	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Cell delineator transmit error.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.35 Cell delineator configuration failed (34)

Alarm Summary

ID	Alarm Name	Severity
34	FC_CD_CFG_FAILURE	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Cell delineator initialization failure.

Impact

Action

5.5.36 ATM backpressure indications overridden (38)

Alarm Summary

ID	Alarm Name	Severity
38	FC_ABM_BP_OVERRIDE	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

ATM chipset, backpressure indications from switch are being overridden to prevent cell loss.

Impact

Events of this type are not system problems, but occur rather as a result of normal ATM traffic congestion buildup. As cell buffers empty, a clear message will be issued. The event is coded as minor as continued events of this type are a possible indication of the need to revisit traffic-engineering assumptions. In a future software release, multiple occurrences will cause a threshold to be crossed, generating a higher severity alarm.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.5.37 Fabric control unable to connect (39)

Alarm Summary

ID	Alarm Name	Severity
39	FC_ATM_CNX_FAIL_ERROR	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Fabric control was unable to complete a requested connection.

Impact

Events of this type are not service affecting, as they occur only at configuration time. The event is coded as informational as there is no resource state change when the condition clears, and there is, therefore, no follow-on clear event.

Action

None.

5.5.38 Buffer overflow in cell buffer on subtend module (42)

Alarm Summary

ID	Alarm Name	Severity
42	FC_SUBTEND_PORT_BUFFER_OVERFLOW	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Buffer overflow in the cell buffer on the subtend module.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.5.39 Error in UTOPIA chip (43)

Alarm Summary

ID	Alarm Name	Severity
43	FC_SUBTEND_PORT_UTOPIA_ERROR	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Error in UTOPIA chip.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.5.40 Parity error in cell egress path (46)

Alarm Summary

ID	Alarm Name	Severity
46	FC_SUBTEND_PORT_EGRESS_PARITY	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Parity error in cell egress path.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6 Network Interface OC3 Alarms

The following table lists NI OC3 alarms event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

Table 5-17: Network Interface OC3 Alarms (Reference)

ID Definition Severity Description

48

FC_OC3_LCD_FAULT

Info

SONET, loss of cell delineation.

49

FC_OC3_OCD_FAULT

Critical

SONET, out of cell delineation.

50

FC_OC3_FIFO_FULL

Critical

SONET, framer FIFO overflow.

51

FC_OC3_C2_MISMATCH

Critical

SONET, received payload incorrect type.

52

FC_OC3_PRDI

Critical

SONET, path RDI received.

53

FC_OC3_PAIS

Critical

SONET, path AIS received.

54

FC_OC3_APS_CHANGE

Critical

SONET, auto protection switch.

55

FC_OC3_APS_IAB

Minor

SONET, auto protection switch byte is corrupted 3 of 12 times.

56

FC_OC3_POINTER_CHANGE

Info

SONET, data pointer changed.

57

FC_OC3_LOP

Critical

SONET, loss of pointer condition.

58

FC_OC3_LRDI

Critical

SONET, line RDI received.

59

FC_OC3_LAIS

Critical

SONET, line AIS received.

60

FC_OC3_LOF

Info

SONET, loss of frame condition.

61

FC_OC3_OOF

Critical

SONET, out of frame condition detected.

62

FC_OC3_LOSY

Critical

SONET, loss of signal detected by optical transceiver.

63

FC_OC3_LOS

Critical

SONET, loss of signal detected by SONET device.

5.6.1 SONET loss of cell delineation (48)

Alarm Summary

ID	Alarm Name	Severity
48	FC_OC3_LCD_FAULT	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, Loss of cell delineation.

Impact

An event of this severity will cause loss of service for more than four subscribers. Examples include:

Loss of a LIM controller could cause loss of service for up to 80 subscribers.
Loss of an NI could cause loss of service for 64-400 subscribers, depending upon configuration.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.2 SONET out of cell delineation (49)

Alarm Summary

ID	Alarm Name	Severity
49	FC_OC3_OCD_FAULT	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, Out of cell delineation.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.3 SONET framer FIFO overflow (50)

Alarm Summary

ID	Alarm Name	Severity
50	FC_OC3_FIFO_FULL	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, Framer FIFO overflow.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.4 SONET received payload incorrect type (51)

Alarm Summary

ID	Alarm Name	Severity
51	FC_OC3_C2_MISMATCH	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, received payload incorrect type.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.5 SONET path RDI received (52)

Alarm Summary

ID	Alarm Name	Severity
52	FC_OC3_PRDI	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, path RDI received.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.6 SONET path AIS received (53)

Alarm Summary

ID	Alarm Name	Severity
53	FC_OC3_PAIS	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, path AIS received.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.7 SONET auto protection switch (54)

Alarm Summary

ID	Alarm Name	Severity
54	FC_OC3_APS_CHANGE	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, auto protection switch.

Impact

Subscriber traffic is not affected by the occurrence of this event. The event is truly informational, as there is no state change, and therefore no assert/clear cycle.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.6.8 SONET auto protection switch byte corrupted (55)

Alarm Summary

ID	Alarm Name	Severity
55	FC_OC3_APS_IAB	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, auto protection switch byte is corrupted 3 of 12 reads.

Impact

Subscriber traffic is not affected by the occurrence of this event. The event is truly informational, as there is no state change, and therefore no assert/clear cycle.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.6.9 SONET data pointer changed (56)

Alarm Summary

ID	Alarm Name	Severity
56	FC_OC3_POINTER_CHANGE	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, data pointer changed.

Impact

The event is not propagated from the module to Fault Manager, and will not be registered in the ViewRunner Event History Window.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.6.10 SONET loss of pointer condition (57)

Alarm Summary

ID	Alarm Name	Severity
57	FC_OC3_LOP	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, loss of pointer condition.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.11 SONET line RDI received (58)

Alarm Summary

ID	Alarm Name	Severity
58	FC_OC3_LRDI	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, line RDI received.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.12 SONET line AIS received (59)

Alarm Summary

ID	Alarm Name	Severity
59	FC_OC3_LAIS	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, line AIS received.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.13 SONET loss of frame condition (60)

Alarm Summary

ID	Alarm Name	Severity
60	FC_OC3_LOF	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, loss of frame condition.

Impact

The event is not propagated from the module to Fault Manager, and will not be registered in the ViewRunner Event History Window.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.6.14 SONET out of frame condition (61)

Alarm Summary

ID	Alarm Name	Severity
61	FC_OC3_OOF	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, out of frame condition detected.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.15 SONET loss of signal detected by optical transceiver (62)

Alarm Summary

ID	Alarm Name	Severity
62	FC_OC3_LOSY	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, loss of signal detected by optical transceiver.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.6.16 SONET loss of signal detected by SONET device (63)

Alarm Summary

ID	Alarm Name	Severity
63	FC_OC3_LOS	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

SONET, loss of signal detected by a SONET device.

Impact

Defined by the OC3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7 Network Interface DS3 Alarms

The following table lists the NI DS3 event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

Table 5-18: Network Interface DS3 Alarms (Reference)

ID Definition Severity Description

81

FC_DS3_OCD

Critical

DS3, out of cell delineation.

82

FC_DS3_FIFO_FULL

Minor

DS3, framer FIFO overflow.

83

FC_DS3_IDLE

Critical

DS3, receiving idle.

84

FC_DS3_RAI

Critical

DS3, receiving remote alarm indication.

90

FC_DS3_YELLOW

Critical

DS3, receiving yellow alarm.

91

FC_DS3_AIS

Critical

DS3, receiving AIS.

93

FC_DS3_OOF

Critical

DS3, out of frame condition detected.

94

FC_DS3_LIU_LOS

Critical

DS3, loss of signal detected at LIU.

95

FC_DS3_LOS

Critical

DS3, loss of signal detected at framer.

96

FC_DS3_TX_PARITY

Minor

DS3, parity error detected on transmit UTOPIA bus.

97

FC_DS3_RX_PARITY

Minor

DS3, HEC error detected on receive UTOPIA bus.

99

FC_DS3_CPAR

Info

DS3, unexpected frame format.

101

FC_DS3_PLCP_OOF

Minor

DS3, PLCP out of frame condition detected.

102

FC_DS3_PLCP_LOF

Minor

DS3, PLCP loss of frame error detected.

5.7.1 DS3 out of cell delineation (81)

Alarm Summary

ID	Alarm Name	Severity
81	FC_DS3_OCD	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, out of cell delineation.

Impact

Defined by the DS3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.2 DS3 framer FIFO overflow (82)

Alarm Summary

ID	Alarm Name	Severity
82	FC_DS3_FIFO_FULL	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, framer FIFO overflow.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.7.3 DS3 receiving idle (83)

Alarm Summary

ID	Alarm Name	Severity
83	FC_DS3_IDLE	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, receiving idle.

Impact

Defined by the DS3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.4 DS3 receiving remote alarm indication (84)

Alarm Summary

ID	Alarm Name	Severity
84	FC_DS3_RAI	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, receiving remote alarm indication.

Impact

Defined by the DS3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.5 DS3 receiving yellow alarm (90)

Alarm Summary

ID	Alarm Name	Severity
90	FC_DS3_YELLOW	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, receiving yellow alarm.

Impact

Defined by the DS3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.6 DS3 receiving AIS (91)

Alarm Summary

ID	Alarm Name	Severity
91	FC_DS3_AIS	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, receiving AIS.

Impact

Defined by the DS3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.7 DS3 out of frame condition (93)

Alarm Summary

ID	Alarm Name	Severity
93	FC_DS3_OOF	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, out of frame condition detected.

Impact

Defined by the DS3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.8 DS3 loss of signal at LIU (94)

Alarm Summary

ID	Alarm Name	Severity
94	FC_DS3_LIU_LOS	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, loss of signal detected at LIU.

Impact

Defined by the DS3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.9 DS3 loss of signal at framer (95)

Alarm Summary

ID	Alarm Name	Severity
95	FC_DS3_LOS	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, loss of signal detected at framer.

Impact

Defined by the DS3 standard as critical.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.10 DS3 parity error on transmit UTOPIA bus (96)

Alarm Summary

ID	Alarm Name	Severity
96	FC_DS3_TX_PARITY	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, parity error detected on transmit UTOPIA bus.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.7.11 DS3 HEC error on receive UTOPIA bus (97)

Alarm Summary

ID	Alarm Name	Severity
97	FC_DS3_RX_PARITY	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, HEC error detected on receive UTOPIA bus.

Impact

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.7.12 DS3 unexpected frame format (99)

Alarm Summary

ID	Alarm Name	Severity
99	FC_DS3_CPAR	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, unexpected frame format.

Impact

Subscriber traffic is not affected by the occurrence of this event. The event is truly informational, as there is no state change, and therefore no assert/clear cycle.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.7.13 DS3 PLCP out of frame condition (101)

Alarm Summary

ID	Alarm Name	Severity
101	FC_DS3_PLCP_OOF	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, PLCP out of frame condition detected.

Impact

An event of this type will result in the loss of all cell traffic until the PLCP convergence protocol is able to resynchronize to the beginning of the frame pointer. This condition could last for up to five seconds.

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.7.14 DS3 PLCP loss of frame error (102)

Alarm Summary

ID	Alarm Name	Severity
102	FC_DS3_PLCP_LOF	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

DS3, PLCP loss of frame error detected.

Impact

Action

Wait for resyncronization.

5.8 Subtend Host Module Alarms

The following table lists the DS3 Subtend Host Module (STM) event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

Table 5-19: Subtend Host Module Alarms (Reference)

ID Definition Severity Description

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to the system monitor.

42

FC_SUBTEND_PORT_BUFFER_OVERFLOW

Info

Buffer overflow in the cell buffer on the subtend module.

44

FC_SUBTEND_PORT_INGRESS_HEC

Info

Subtend port ingress HEC error.

5.8.1 Module was detected (128)

Alarm Summary

ID	Alarm Name	Severity
128	LR_CREATE_OBJ	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module was detected.

Impact

Events of this type are benevolent, and are not indicative of service impairment or loss.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.8.2 Module did not respond to system monitor (129)

Alarm Summary

ID	Alarm Name	Severity
129	LR_PING_FAIL	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module did not respond to the system monitor.

Impact

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.8.3 Buffer overflow in cell buffer on subtend module (42)

Alarm Summary

ID	Alarm Name	Severity
42	FC_SUBTEND_PORT_BUFFER_OVERFLOW	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Buffer overflow in the cell buffer on the subtend module.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.8.4 Subtend port ingress HEC error (44)

Alarm Summary

ID	Alarm Name	Severity
44	FC_SUBTEND_PORT_INGRESS_HEC	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Subtend port ingress HEC error.

Impact

Action

2. As a result, these alarms will be followed by an alarm "Cleared" event.

3. If an alarm clear is not received within one minute, reinsert the module.

4. If problem persists, replace module.

5.9 LIM Controller Module Alarms

The following table lists LIM controller module event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

Table 5-20: LIM Control Module Alarms (Reference)

ID Definition Severity Description

3

SCL_OUT_OF_MEMORY

Critical

Application was unable to allocate memory.

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to system monitor.

5.9.1 Application unable to allocate memory (3)

Alarm Summary

ID	Alarm Name	Severity
3	SCL_OUT_OF_MEMORY	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Application was unable to allocate memory.

Impact

An event of this severity will cause loss of service for more than four subscribers. Examples include:

Loss of a LIM controller could cause loss of service for up to 80 subscribers.
Loss of an NI could cause loss of service for 64-400 subscribers, depending upon configuration.

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.9.2 Module detected (128)

Alarm Summary

ID	Alarm Name	Severity
128	LR_CREATE_OBJ	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module was detected.

Impact

Events of this type are benevolent, and are not indicative of service impairment or loss.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.9.3 Module not responding to system monitor (129)

Alarm Summary

ID	Alarm Name	Severity
129	LR_PING_FAIL	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module did not respond to the system monitor.

Impact

An event of this severity will cause loss of service for more than four subscribers. Examples include:

Loss of a LIM controller could cause loss of service for up to 80 subscribers.
Loss of an NI could cause loss of service for 64-400 subscribers, depending upon configuration.

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.10 Line Interface Module Alarms

The following table lists LIM event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

Table 5-21: Line Interface Module Alarms (Reference)

ID Definition Severity Description

1

FMEVENT_LIM_DOH_CALIBRATION_FAILURE

Major

LIM was not able to perform Digital Off-Hook (DOH) calibration.

3

FMEVENT_LIM_CONNECT_FAILURE

Major

LIM was not able to connect to the switching matrix.

128

LR_CREATE_OBJ

Info

Module was detected.

129

LR_PING_FAIL

Critical

Module did not respond to system monitor.

5.10.1 LIM not able to perform DOH calibration (1)

Alarm Summary

ID	Alarm Name	Severity
1	FMEVENT_LIM_DOH_CALIBRATION_FAILURE	Major

Description

This description appears in the ViewRunner Event History Window (event log).

Description

LIM was not able to perform DOH calibration.

Impact

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.10.2 LIM not able to connect to switching matrix (3)

Alarm Summary

ID	Alarm Name	Severity
3	FMEVENT_LIM_CONNECT_FAILURE	Major

Description

This description appears in the ViewRunner Event History Window (event log).

Description

LIM was not able to connect to the switching matrix.

Impact

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.10.3 Module detected (128)

Alarm Summary

ID	Alarm Name	Severity
128	LR_CREATE_OBJ	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module was detected.

Impact

Events of this type are benevolent, and are not indicative of service impairment or loss.

Action

1. This is an informational event, not an alarm. Informational events do not represent a state change, and therefore, will not be followed by an alarm "Cleared" event.

2. Informational events are typically one-time occurrences that will be corrected by the module without a reset or will pass without service degradation.

3. No craft action required.

5.10.4 Module not responding to system monitor (129)

Alarm Summary

ID	Alarm Name	Severity
129	LR_PING_FAIL	Critical

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Module did not respond to the system monitor.

Impact

Action

2. Many alarm conditions will clear as a result of a module reset.

3. Look for the alarm to clear within one minute.

4. An alarm is cleared when the SC faceplate alarm LED changes from red to off.

5. In the ViewRunner interface, an alarm cleared is evidenced by two actions:

the receipt of an alarm "Cleared" event in the Event History Window, and
the alarmed module ejector tab changes from red to green.

6. If the alarm does not clear, remove module and reinsert. This will force a module to reset in those cases where the neither the module itself or the SC could force a reset.

7. A module reset in most cases will clear all alarm conditions.

8. Observe the SC alarm LED and/or ViewRunner ejector tabs to see if alarm condition returns. If the previous problem persists, the condition will probably reoccur within a minute or so.

9. If the alarm condition persists, replace module.

5.11 Slot Alarms

The following table lists slot event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Note Event codes having a value less than 128 are specific to the module in alarm. Event codes having a value greater than, or equal to, 128 are system-wide events.

Table 5-22: Slot Alarms (Reference)

ID Definition Severity Description

1

SLOT_MISMATCH_EVENT

Minor

A module was inserted in the slot that did not match the type that was pre-provisioned for that slot.

2

SLOT_INVALID_EVENT

Minor

A module that was not valid for the slot was inserted in the slot.

3

SLOT_NO_IMAGE_EVENT

Minor

No image exists for the type module present in the slot.

4

SLOT_IMAGE_NOT_READY

Minor

Image for download is not ready

5

SLOT_DOWNLOAD_START

Info

Download of a module image to the identified slot has begun.

6

SLOT_DOWNLOAD_COMP

Info

Download of a module image to the identified slot has completed.

7

SLOT_DOWNLOAD_FAIL

Info

Download of a module image to the identified slot has failed.

8

SLOT_CURR_IMG_FAIL

Minor

Image could not be obtained for module in slot.

5.11.1 Slot mismatch error (1)

Alarm Summary

ID	Alarm Name	Severity
1	SLOT_MISMATCH_EVENT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

A module was inserted in the slot that did not match the type that was pre-provisioned for the slot.

Impact

Action

1. Pre-provisioning may have been performed on this slot during system configuration (after SC was installed). Pre-provisioning implies that a slot has been configured for a given module type, and the SC has detected a different module is physically inserted in this slot.

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.11.2 Slot invalid error (2)

Alarm Summary

ID	Alarm Name	Severity
2	SLOT_INVALID_EVENT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

A module that was not valid for the slot was inserted in the slot.

Impact

Action

1. The configuration style being used in this node (DOH standard, DOH entry level, or direct connect) does not expect to see a module of the type inserted in this slot. Refer to the Cisco 6100 Set Up and Installation Manual for more information on configuration styles.

2. Remove inappropriate module and delete configuration using ViewRunner.

5.11.3 No image for type of module present (3)

Alarm Summary

ID	Alarm Name	Severity
3	SLOT_NO_IMAGE_EVENT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

No image exists for the type module present in the slot.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.11.4 Image for download not ready (4)

Alarm Summary

ID	Alarm Name	Severity
4	SLOT_IMAGE_NOT_READY	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Image for download is not ready.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.11.5 Module image download begun (5)

Alarm Summary

ID	Alarm Name	Severity
5	SLOT_DOWNLOAD_START	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Download of a module image to the identified slot has begun

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.11.6 Module image download complete (6)

Alarm Summary

ID	Alarm Name	Severity
6	SLOT_DOWNLOAD_COMP	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Download of a module image to the identified slot has completed.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.11.7 Module image download failed (7)

Alarm Summary

ID	Alarm Name	Severity
7	SLOT_DOWNLOAD_FAIL	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Download of a module image to the identified slot has failed.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.11.8 Imaged not obtained for module (8)

Alarm Summary

ID	Alarm Name	Severity
8	SLOT_CURR_IMG_FAIL	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Image could not be obtained for module in slot.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12 Software Download Alarms

The software download procedure can result in various minor or informational alarms. These are not service affecting and happen only when you are attempting to download software.

The following table lists software download event codes, providing their IDs, definitions, severity, and description. A detailed explanation of these events and the actions required to deal with them (if any) are to be found in subsections which follow the event code table.

Table 5-23: Software Download Alarms (Reference)

ID Definition Severity Description

1

MUM_TFTPING_FAULT

Minor

TFTP file download failure

2

MUM_TFTP_SUCCESSFUL

Info

TFTP file download successful

3

MUM_TFTP_TIMEOUT_FAULT

Minor

TFTP timeout incurred during download

4

MUM_FILE_NOT_FOUND_FAULT

Minor

Requested TFTP file not found

5

MUM_CHKSUM_FAIL_FAULT

Minor

Checksum failed on TFTP file download

6

MUM_SIZE_CHK_FAULT

Minor

File size check failed on TFTP file download

7

MUM_DB_WRITE_FAULT

Minor

TFTP file transfer failed; image could not be written to 6100 database

8

MUM_NO_SPACE_FAULT

Minor

Insufficient SC memory to contained TFTP'd image

9

MUM_TFTP_GENERAL_FAULT

Minor

TFTP file transfer failed

5.12.1 TFTP file download failure (1)

Alarm Summary

ID	Alarm Name	Severity
1	MUM_TFTPING_FAULT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

TFTP file download failure.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12.2 TFTP file download successful (2)

Alarm Summary

ID	Alarm Name	Severity
2	MUM_TFTP_SUCCESSFUL	Information

Description

This description appears in the ViewRunner Event History Window (event log).

Description

TFTP file download successful.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12.3 TFTP timeout during download (3)

Alarm Summary

ID	Alarm Name	Severity
3	MUM_TFTP_TIMEOUT_FAULT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

TFTP timeout incurred during download.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12.4 TFTP file not found (4)

Alarm Summary

ID	Alarm Name	Severity
4	MUM_FILE_NOT_FOUND_FAULT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Requested TFTP file not found.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12.5 Checksum failed on TFTP file download (5)

Alarm Summary

ID	Alarm Name	Severity
5	MUM_CHKSUM_FAIL_FAULT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Checksum failed on TFTP file download.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12.6 File size check failed on TFTP file download (6)

Alarm Summary

ID	Alarm Name	Severity
6	MUM_SIZE_CHK_FAULT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

File size check failed on TFTP file download.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12.7 TFTP file transfer failed (7)

Alarm Summary

ID	Alarm Name	Severity
7	MUM_DB_WRITE_FAULT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

TFTP file transfer failed; image could not be written to 6100 database.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12.8 Insufficient SC memory to contained TFTP'd image (8)

Alarm Summary

ID	Alarm Name	Severity
8	MUM_NO_SPACE_FAULT	Minor

Description

This description appears in the ViewRunner Event History Window (event log).

Description

Insufficient SC memory to contained TFTP'd image.

Impact

Action

2. Check ViewRunner information on the slot and either replace the wrong module type with the pre-provisioned module type, or delete module configuration for the slot.

5.12.9 TFTP file transfer failed (9)

Alarm Summary

ID	Alarm Name	Severity
9	MUM_TFTP_GENERAL_FAULT	Minor

Table of Contents

System Alarm/Event Troubleshooting