|
|
Alarm condition (ALM) messages describe alarm conditions that may be present on the system. ALM messages are found within fault recovery and maintenance (FRM) messages—specifically, FRM500 through FRM521. FRM messages describe the alarm severity and the source of the alarm. Refer to "Fault Recovery and Maintenance Messages" for a description of FRM messages.
ALM messages are described in the following manner:
ALMnnn: Message
Explanation An explanation of the message.
Action A description of the action the user should take.
ALM001: Insufficient Timed IPC Memory
Explanation The system encountered an internal memory allocation error.
Action If this is a repeating condition which causes disruption to call processing, switch to the standby side and reboot the controller experiencing the problem.
ALM002: Network Manager Failure
Explanation The Network Manager subsystem failed to respond to sanity poll requests. This is a fatal alarm condition; a system reboot is imminent. All call processing will stop. The system will reboot automatically.
Action If the condition persists, check for possible hardware problems.
ALM003: Host Manager Failure
Explanation The Host Manager subsystem failed to respond to sanity poll requests. No host commands can be processed or reports generated by the system. All call processing will stop.
Action If the Host Manager subsystem does not recover and reestablish host connectivity automatically, switch to the standby side and reboot the controller experiencing the problem.
ALM004: Redundancy Manager Failure
Explanation The Redundancy Manager subsystem failed to respond to sanity poll requests. The update channel cannot maintain file synchronization between the active and standby controllers. Switch redundancy will be lost.
Action Reboot the switch. If problems continue, check for possible hardware problems.
ALM010: Host Communications Failure
Explanation A single host link failed. This message is preceded by an HST (Host Manager) message identifying the link and the condition that caused the failure. Call processing by the affected host will stop.
Action Identify the problem with the host connection. Examine the host system for problems. Check all physical host connectivity.
ALM011: No Hosts Available
Explanation All configured host links have failed (ADLC serial connections and Ethernet sockets). No host commands can be processed or reports generated by the system. Call processing will stop.
Action Identify the host connectivity problem. Check the host system for problems. Check all physical host connectivity.
ALM012: ADLC Sub-System Failure
Explanation The ADLC driver under the Host Manager failed to respond to a system sanity test. All serial input/output (SIO) ADLC links have failed. Call processing will stop for the affected serial host connections.
Action If the problem persists, switch to the standby side and reboot the controller experiencing the problem.
ALM013: Ethernet Sub-System Failure
Explanation The Ethernet communications subsystem under the Host Manager failed to respond to a system sanity test. All Ethernet socket connections have failed. Call processing will stop for all hosts connected via Ethernet.
Action If the problem persists, switch to the standby side and reboot the controller experiencing the problem.
ALM014: Overlay Sub-System Failure
Explanation The overlay subsystem controlling TeleRouter operation failed to respond to a system sanity test. The TeleRouter overlay can no longer perform routing actions. Call processing by TeleRouter will stop.
Action If the problem persists, switch to the standby side and reboot the controller experiencing the problem.
ALM015: Resource Group Limitation Pending
 |
Note This alarm is generated under the following circumstances—TeleRouter is defined and no hosts are defined (as seen in the system administration Host Configuration screen) in the VCO/4K system. |
Explanation Seventy-five percent or more of the ports in a resource group were busied (resource is unavailable), either via card administration or by the auto make-busy function. A resource limitation alarm is pending due to this condition. This alarm condition is cleared once fifty percent or more of the ports in the affected resource group return to service. There is no immediate effect on call processing.
Action If call volume is anticipated to rise significantly, more of the affected resource type should be added to the system.
ALM016: Resource Group Limitation Exists
|
Note This alarm is generated under the following circumstances—TeleRouter is defined and no hosts are defined (as seen in the system administration Host Configuration screen) in the VCO/4K system. |
Explanation No ports are available in a resource group. This alarm condition is set when a Resource Limitation ($D6) report is received from the VCO/4K. This alarm condition is cleared after three successful hunts from the affected resource group. Call processing requiring the affected resource type will be inhibited.
Action If call volumes are expected to continue at high levels, more of the affected resource type should be added to the system.
ALM017: Internet Host Ping Failure
Explanation A host that is configured for ping processing (from the Host Configuration screen) is not responding to the pings from the system. Call processing by the affected host will probably stop.
Action Check the host connections.
ALM020: Start Record Exhaust
Explanation The system is unable to assign memory space marking the start record portion of a call record. In most cases, this is a call just starting and the incoming port is presented with a reorder tone. This also may occur for an outgoing port added to a conference. The host must take action for the port. The host receives the command returned with a network status byte value of $29. The affected call will not be processed.
Action Call volume is at or near maximum capacity. Once call volume is reduced, start records should be available.
ALM021: End Record Exhaust
Explanation The system is unable to assign memory space marking the start record portion of a call record. In most cases, this is a call just starting and the incoming port is presented with a reorder tone. This also may occur for an outgoing port added to a conference. The host must take action for the port. The host receives the command returned with a network status byte value of $29. The affected call will not be processed.
Action Once call volume is reduced, end records should be available.
ALM022: D-channel pool exhaust
Explanation Call volume is at or near maximum capacity. The system is unable to allocate memory for the D-channel from the D-channel message pool.
|
Note No indication of this situation is sent to the host. The call which caused this message may fail to complete. |
Action Once call volume is reduced, memory should be available for storing D-channel messages.
ALM023: NBC Does Not Respond
Explanation The initialization task recognized but failed to reset the NBC/NBC3 as part of the system boot process. The system will not initialize.
Action Remove and reseat the NBC/NBC3. Remove and reseat the Combined Controller which houses the SWI card. Reset the system. If the problem persists, replace the NBC/NBC3 and/or SWI/Combined Controller assembly.
ALM024: NBC DMA Output Failure
Explanation An error was detected during a transmit attempt to the NBC. This is a fatal alarm condition; a system reboot is imminent. All call processing will stop.
Action The system will reboot automatically. If the problem persists, replace the NBC/NBC3 and/or SWI/Combined Controller assembly.
ALM025: CP Transmit Overrun
Explanation The active system controller overran the NBC/NBC3 due to heavy call load conditions or a processing fault on the NBC. This is a critical alarm condition that may be escalated to a fatal condition. Call processing may be interrupted or will stop if the condition becomes fatal.
Action Remove and reseat the NBC/NBC3. Remove and reseat the Combined Controller which houses the SWI card. Reset the system. If the problem persists, replace the NBC/NBC3 and/or SWI/Combined Controller assembly.
ALM026: No NBC in System
Explanation System initialization failed to detect the presence of an NBC/NBC3 card. The system controller associated with the missing NBC/NBC3 can still run as a standby but is unable to perform normal call processing.
Action Ensure that an NBC/NBC3 card is properly installed in the system.
ALM027: NBC Failure
Explanation A system disruptive failure of the NBC/NBC3 occurred. This is a fatal alarm condition; a system reboot is imminent. Call processing will stop. The system reboot will cause a switch to the standby side.
Action If the problem persists after the system reboot, replace the NBC/NBC3.
ALM028: NBC Loss of Internal Sync.
Explanation The system cannot synchronize using internal clocking. Loss of synchronization will cause PRI and T1/E1 spans to begin slipping.
Action If the system has Incoming spans defined as Master Timing Links, switch to one of the incoming links. Observe that the NBC synchronizes to the Incoming Reference. If problems persist, replace the NBC/NBC3.
ALM029: NBC Comm. Bus Failure
Explanation The internal packet communications bus between the NBC/NBC3 and other cards in the system failed. Call processing and system management activities may be interrupted.
Action This fault is normally self-correcting. The message may briefly appear several times until normal processing on the communication bus is established.
ALM030: No Tone Card in System
Explanation No DTG card came into service. This is a fatal alarm condition; a system reboot is imminent. The system will not initialize.
Action Ensure that a DTG card is properly installed in the system.
ALM031: Rack 1, Level 2 Failure
Explanation The BRC for the specified rack is defined in the database but the BRC at the location is out-of-service. Communications with the specified subrack will stop.
|
Note The BRC card is not used in VCO/20 or VCO/4K systems. |
Action Check the status of the BRC pairs.
ALM032: Rack 1, Level 3 Failure
Explanation The BRC for the specified rack is defined in the database but the BRC at the location is out-of-service. Communications with the specified subrack will stop.
|
Note The BRC card is not used in VCO/20 or VCO/4K systems. |
Action Check the status of the BRC pairs.
ALM033: Rack 2, Level 0 Failure
Explanation The BRC for the specified rack is defined in the database but the BRC at the location is out-of-service. Communications with the specified subrack will stop.
|
Note The BRC card is not used in VCO/20 or VCO/4K systems. |
Action Check the status of the BRC pairs.
ALM034: Rack 2, Level 1 Failure
Explanation The BRC for the specified rack is defined in the database but the BRC at the location is out-of-service. Communications with the specified subrack will stop.
|
Note The BRC card is not used in VCO/20 or VCO/4K systems. |
Action Check the status of the BRC pairs.
ALM035: Rack 2, Level 2 Failure
Explanation The BRC for the specified rack is defined in the database but the BRC at the location is out-of-service. Communications with the specified subrack will stop.
|
Note The BRC card is not used in VCO/20 or VCO/4K systems. |
Action Check the status of the BRC pairs.
ALM036: Rack 2, Level 3 Failure
Explanation The BRC for the specified rack is defined in the database but the BRC at the location is out-of-service. Communications with the specified subrack will stop.
|
Note The BRC card is not used in VCO/20 or VCO/4K systems. |
Action Check the status of the BRC pairs.
ALM037: Redundant Controller Failure
Explanation In a redundant system, the redundant controller failed. The system is no longer redundant.
Action Identify the cause of the redundant controller failure. Replace the failed controller.
ALM038: PRI D-Channel Failure
Explanation A PRI D-channel failure was detected or cleared. This message is followed by an FRM indicating the card for which the condition is being reported. Call setup and management via the affected D-channel will stop.
Action If the condition persists, investigate possible path problems. Swap the PRI/N, ICC, or I/O modules as appropriate.
ALM039: PRI/T1/E1 Carrier Lost
Explanation Loss of a T1/E1 carrier was detected for at least one T1/E1 card in the system. The system attempts to synchronize with the internal clock only if the alarm is for the primary or secondary timing source and the other is unavailable. Calls on the affected T1/E1 span will be lost.
Action If the condition persists, investigate possible path problems. Swap the T1/E1 or ICC card, or the I/O module as appropriate.
ALM040: PRI/T1/E1 Card Failure
Explanation A PRI or T1/E1 card failed with loss of all its channels. Calls on the affected card will be lost.
Action Try to reset the card. If problems persist, replace the affected PRI/T1/E1 or ICC card as appropriate.
ALM041: PRI/T1/E1 Remote Alarm
Explanation An alarm condition was detected at the remote end of a PRI/T1/E1 span connected to a PRI or T1/E1 card. Calls on the affected span will be lost.
Action Try to reset the card. Check for path problems. Replace the affected PRI/T1/E1 card or ICC as appropriate.
ALM042: PRI/T1/E1 Out-Of-Frame
Explanation An out-of-frame (OOF) condition was detected at a PRI or T1/E1 card. The OOF threshold counter was increased but not exceeded. Calls on the affected span will probably experience noise.
Action OOF conditions can occur as a result of timing differences between the two ends of the span. Ensure that reliable timing is being used for the affected span. Check for possible path disturbances. Replace the affected PRI/T1/E1 or ICC card as appropriate.
ALM043: PRI/T1/E1 Signaling Bit Alarm
Explanation A signaling bit error was detected at a PRI or T1/E1 card. A card alarm was also set. Incorrect signaling may occur, causing faulty call processing.
Action If the problem persists, reset the card. Check for possible path problems. Replace the affected PRI/T1/E1 or ICC card as appropriate.
ALM044: PRI/T1/E1 Slip Maint. Threshold
Explanation The number of PRI or T1/E1 slips counted exceeds the number allowed for the system (256). The slip maintenance limit alarm is set. Slips will cause noticeable noise on calls.
Action If slips are occurring at a rate high enough to reach the 256 slip system threshold, investigate possible timing problems. Ensure reliable timing is being used for the affected span. Reset the card. Replace the affected PRI/T1/E1 or ICC card as appropriate.
ALM045: PRI/T1/E1 OOF Maint. Threshold
Explanation The system threshold limit for out-of-frame (OOF) occurrences was exceeded by a PRI or T1/E1 card. The card is placed in maintenance mode. If the card serves as the master timing link, the system attempts to resynchronize itself to another incoming link or to the internal reference source. Calls on the affected span will be lost.
Action The card alarm for OOF maintenance limit remains set until the card is reset.
ALM046: PRI/T1/E1 BPV Maint. Threshold
Explanation The system threshold limit for bipolar violation (BPV) conditions was exceeded for a PRI or T1/E1 card. The card is placed in maintenance mode. If the card serves as the master timing link, the system attempts to resynchronize itself to another incoming link or to the internal reference source. Calls on the affected span will be lost.
Action The card alarm for BPV maintenance limit remains set until the card is reset.
ALM047: Loss Of All Call Progress Analyzers
Explanation Although CPA cards or CPA resources on an SPC card are defined in the database, there are no active CPA cards available in the CPA resource group. The last or only active CPA in the system is out-of-service or was removed from service via system administration. Calls requiring call progress tone detection cannot be processed.
Action Ensure that active CPA resources are available in the CPA resource group.
ALM049: Loss Of All MF Receivers
Explanation Although MRC cards or MFR resources on the SPC card are defined in the database, there are none available in the MRC resource group. The last or only active MRC or MFR resource in the system is out-of-service or was removed from service via system administration. Calls requiring MF receiver service cannot be processed.
Action Ensure that active MF receiver resources are available in the MF receiver resource group.
ALM050: Loss Of All DTMF Receivers
Explanation Although DRC cards or DTMF resources on the SPC card are defined in the database, there are none available in the DTMF resource group. The last or only active DRC or DTMF resource in the system is out-of-service or was removed from service via system administration. Calls requiring DTMF receiver service cannot be processed.
Action Ensure that active DTMF receiver resources are available in the DTMF receiver resource group.
ALM051: Loss Of Announcement Capability
Explanation The system is not equipped with an active, downloaded DVC or IPRC card in the IPRC resource group. Commands or inpulse rules which require voice prompts cannot be processed.
Action Ensure that active voice prompt resources are available in the IPRC resource group.
ALM052: Card Failure In System
Explanation A noncritical card failure was detected in the system; a single- or multi-span network card, or a service circuit card, went into the out-of-service (OOS) state, as viewed from the Card Maintenance or Card Summary screen. The card is OOS and unavailable for use in processing calls.
Action Identify the reason for the OOS condition.
ALM053: Fatal Host Alarm
Explanation A Set/Reset Host Alarms ($C0 03) command (setting a fatal alarm) was received from the host.
Action None required.
ALM054: Critical Host Alarm
Explanation A Set/Reset Host Alarms ($C0 03) command (setting a critical alarm) was received from the host.
Action None required.
ALM055: Major Host Alarm
Explanation A Set/Reset Host Alarms ($C0 03) command (setting a major alarm) was received from the host. Major alarm LED is illuminated on the AAC. Alarm relay contacts for major alarm are closed.
Action None required.
ALM056: Minor Host Alarm
Explanation A Set/Reset Host Alarms ($C0 03) command (setting a minor alarm) was received from the host. Minor alarm LED is illuminated on the AAC. Alarm relay contacts for minor alarm are closed.
Action None required.
ALM057: Aux-1 Host Alarm
Explanation A Set/Reset Host Alarms ($C0 03) command was received from the host which instructs the system to set the Aux 1 alarm. At the time of this report, the alarm is set. The Aux1 alarm LED is illuminated on the AAC. Alarm contacts for Aux1 alarm are closed.
Action The host application determines the action.
ALM058: Aux-2 Host Alarm
Explanation A Set/Reset Host Alarms ($C0 03) command was received from the host which instructs the system to set the AUX 2 alarm. At the time of this report, the alarm is set. The Aux2 alarm LED is illuminated on the AAC. Alarm contacts for Aux2 alarm are closed.
Action The host application determines the action.
ALM059: NFAS D-channel Failure
Explanation An NFAS group with four or more cards has no active D-channel. Call processing for the NFAS group will stop.
Action Identify the cause of the D-channel failure. Replace the PRI/ICC card with the affected PRI span.
ALM060: Loss Of All MFCR2 Transceivers
Explanation Although MFCR2 cards or MFR2 resources on the SPC card are defined in the database, there are none available in the MFCR2 resource group. The last or only active MFCR2 or MFR2 resource in the system is out-of-service or was removed from service via system administration. Calls requiring MFCR2 receiver service cannot be processed.
Action Ensure that active MFCR2 resources are available in the MFCR2 resource group.
ALM061: T1/E1 Blue Alarm
Explanation An unframed all ones signal has been detected. The blue alarm is sent to the far end when the span is not ready for service. When the span is configured and the system is ready to receive calls, the blue alarm is removed. Call processing is inhibited.
Action Ensure that the T1/E1 span is active. Identify any problem. Replace the T1/E1/ICC card as necessary.
ALM062: Loss Of All Subrate Functions
Explanation The Subrate Switching Card (SSC) is out-of-service (OOS). In a redundant system, both SSCs are OOS. Calls carried on the SSC are lost.
Action Identify the source of the OOS state, and bring back into service. Once brought back into service, the alarm will clear.
ALM063: Loss of Subrate Redundancy
Explanation Displays in redundant systems only. One of the Subrate Switching Cards (SSCs) is out-of-service (OOS). Calls carried on the OOS SSC are lost.
Action Identify the source of the OOS state, and bring back into service.
ALM064: Subrate Timeslot Threshold
Explanation The number of subrate time slots, which you configured from the Subrate Configuration screen, has been reached. No additional time slots can be configured.
Action Access the Subrate Configuration screen and reconfigure the time slot threshold.
ALM065: Subrate Timeslot Exhausted
Explanation All subrate time slots are in use. No additional calls can be carried by the SSC cards.
Action Reconfigure the switch to allocate more time slots.
ALM066: All Ports on Card Deactivated
Explanation The Enable All Ports Deactivated Alarm feature is enabled on the System Feature Configuration screen and all the ports on the PRI/N card are deactivated. No calls will be processed.
Action Take appropriate steps to identify the reason for all ports being deactivated and reactivate the ports.
ALM071: Wrong Hardware Installed
Explanation Incompatible hardware is installed in your system. For example, an ICC T1 I/O module may be connected to an ICC E1 card. This message pertains only to the ICC and SPC. The T1/E1/PRI spans will not activate. No calls can be processed.
Action Identify the problem with the installed hardware. Replace hardware as necessary to restore operation of the affected ICC.
ALM072: Interface Hardware Failure
Explanation Two possible scenarios exist for the receipt of this message. The first scenario indicates that one or more spans have been added to the database without the associated card(s) activated. The second scenario indicates that a single span or service engine has failed on the ICC or SPC—call processing stops on the affected hardware.
Action For the first scenario, activate the associated cards. For the second scenario, replace the failing hardware.
ALM073: Module Hardware Failure
Explanation All spans or service engines have failed on the ICC I/O module or SPC SRM. Call processing stops on the affected hardware.
Action Replace the failing hardware.
ALM074: Loss of All SPC OUTPULSERS
Explanation Although SPC outpulse cards are defined in the system, there are none available in the SPC outpulse resource groups. The last or only active SPC outpulse card(s) in the system is out-of-service (OOS) or was removed from service via system administration. Calls requiring SPC outpulse digit service cannot be processed.
Action Change the OOS SPC to in service.
ALM075: No SPC Static Tone In System
Explanation SPC-TONE span(s) is defined in the system, but available; span(s) is out-of-service (OOS).
Action Access system adminstration and change an OOS SPC-TONE span to in service. Refer to Cisco VCO/4K System Administrator's Guide for more information.
ALM076: Incoming Timing Changed to Internal
Explanation The system software changed the timing source to backup because the NBC3 lost synchronization with the incoming timing source. The backup timing source was also not available, or it failed to synchronize, and the system software changed the timing source to internal. An Alarm Condition ($F0) report is sent to the host with an alarm code of $4C.
Action Analyze the contents of alarm code $4C to verify the reason for the change in timing source. Refer to Cisco VCO/4K Extended Programming Reference for more information. Access the Master Timing Link Selection screen to change the timing source to incoming, if needed. Refer to Cisco VCO/4K System Administrator's Guide for further information.
ALM077: ICC Card Congestion Alarm
Explanation This message, which appears on the System Alarms Display screen and in the system log file, indicates when an Interface Controller Card is reset. The alarm is minor and does not change the status of the ICC; however, if the host has control of the ports on the congested span, stop sending new calls to the span listed in the Alarm Condition ($F0) report's R-L-S information. The alarm is cleared after the ICC returns to a normal volume of traffic for 30 seconds.
Action None required.
ALM078: Loss of All CONFERENCE ports
Explanation Although conference cards are defined in the system, there are none available in the conference resource group. The last or only active conference card in the system is out of service or was removed from service via system administration. Calls requiring conference card service cannot be processed.
Action Use the system administration screens to bring a conference card in service.
ALM080: Update Channel Failure
Explanation The update channel between redundant system controllers failed. One side stopped communication. This also happens when file synchronization processing reaches expiry on one side. Switch redundancy is lost. If the active side fails, a switchover failure could occur. The channel should be reestablished in 2 to 3 minutes.
Action If the channel is not reestablished, investigate the following two possibilities: the standby system is unable to boot or a SWI failed.
|
Note The SWI is part of the Combined Controller assembly in VCO/20 and VCO/4K systems. |
ALM081: UPD DMA Output Failure
Explanation An error was detected during a transmit attempt over the update channel to the standby controller. This condition occurs when one controller fails while the other is transmitting data over the update channel. Switch redundancy is lost. If the active side fails, a switchover failure could occur.
Action Verify that both controllers are operational. If a controller is rebooting, verify proper boot-up and restoration of operation. Replace the controller if necessary. This problem could also result from a malfunction of the SWI on the Combined Controller assembly.
ALM082: UPD Transmit Overrun
Explanation The system controller transmitting over the update channel exceeded the input buffer capacity of the receiving system controller. The update channel stops handling data and is reinitialized.
Action Data was lost, but the system recovers when the channel is reestablished.
ALM083: UPD Receive Overrun
Explanation The capacity of the input buffer of the receiving system controller was exceeded. The update channel stops handling data and is reinitialized. Data was lost.
Action The system recovers when the channel is reestablished.
ALM084: UPD Receive Timeout
Explanation A message was not received on the update channel for the last 15 seconds. Possible loss of update channel data. Possible loss of switch redundancy.
Action If the update channel is not restored automatically, identify the reason for the update channel problem. Check CPU and SWI operation. Reboot the affected side. Replace any suspect hardware.
ALM085: UPD DMA Output Timeout
Explanation A timeout occurred while trying to send a message across the update channel. Possible loss of update channel data. Possible loss of switch redundancy.
Action If the update channel is not restored automatically, identify the reason for the update channel problem. Check CPU and SWI operation. Reboot the affected side. Replace any suspect hardware.
ALM090: Printer Off Line
Explanation The system printer is off line or powered off. No log file messages can be written to the printer until it is activated.
Action Turn the printer on. Place the printer online.
ALM093: Available Disk Space Less Than 30 MB
Explanation Available disk space on your switch's hard drive is below 30 MB. No immediate affect on call processing.
Action Delete unnecessary files until disk space exceeds 30 MB. This alarm is cleared at midnight if the condition that set the alarm no longer exists.
ALM094: Available Disk Space Less Than 15 MB
Explanation Available disk space on your switch's hard drive has fallen below 15 MB. An attempt is being made to restore available disk space to more than 30 MB. The system deleted all but the latest core files. Further file deletions occurred in the following sequence, if more than 30 MB of disk space was not attained:
Action This alarm is cleared at midnight if the condition that set the alarm no longer exists.
ALM095: Failed to Create 30 MB of Available Disk Space
Explanation This message follows an ALM094 message if the system's attempt to provide sufficient disk space was unsuccessful. No immediate affect on call processing unless available disk space prevents access to the system log files.
Action Delete additional files until disk space exceeds 30 MB. This alarm is cleared at midnight if the condition that set the alarm no longer exists.
ALM096: Trace File Exceeded 1 MB Size
Explanation The trace file has exceeded 1 MB. No affect on call processing. The trace file may become too large to easily handle for transferring to another destination.
Action Disable Host Message Trace and NBC Message Trace from the System Trace Configuration screen, and then either delete or move the trace file to a different destination drive or diskette. Turn tracing on and allow the system to write more than 1000 time stamps to the trace file, to clear this alarm. Refer to Chapter 2 of the Cisco VCO/4K Troubleshooting Guide for further instructions.
ALM097: Log File Exceeded 1 MB Size
Explanation The log file has exceeded 1 MB. No affect on call processing. The log file may become too large to easily handle for transferring to another destination.
Action Either delete or move the log file to a different drive or diskette. After the log file has been deleted or moved, the system automatically creates a new log file. The alarm is cleared after the system writes more than 1000 date/time stamps to the new log file. Refer to Chapter 2 of the Cisco VCO/4K Troubleshooting Guide to clear this alarm.
ALM100: Queue Overflow
Explanation Fatal alarm. A queue overflow has caused a vital piece of the software to fail. This is not a recoverable situation. A system reboot is imminent. A switchover should occur. Call processing will stop on the affected controller. The affected queue should be listed in the message.
Action After the controller reboots, ensure restoration of operational condition.
ALM101: Queue Overflow
Explanation Critical alarm. A queue overflow has caused an interruption of service of a critical piece of the system. A switchover could occur. Call processing may stop on the affected controller. The affected queue should be listed in the message.
Action The system will recover automatically. Observe system performance.
ALM102: Queue Overflow
Explanation Major alarm. A queue overflow has caused an interruption of service of a major, but noncritical, piece of the system. A switchover could occur. Call processing may stop on the affected controller. The affected queue should be listed in the message.
Action The system will recover automatically. Observe system performance.
ALM103: Queue Overflow
Explanation Minor alarm. A queue overflow has caused an interruption of service of a minor piece of the system. No affect on call processing.
Action The system will recover automatically. Observe system performance.
ALM104: Queue Overflow
Explanation General alarm. A queue overflow has occurred that does not fit into one of the above categories. The affected queue should be identified in the message. Probably no affect on call processing.
Action The system will recover automatically. Observe system performance.
ALM105: Memory Allocation Failure
Explanation Fatal alarm. A memory allocation error has occurred in a vital piece of the software. This is not a recoverable situation. A system reboot is imminent. A system switchover should occur.
Action The system will reboot. Observe that the affected controller returns to normal operation.
ALM106: Memory Allocation Failure
Explanation Critical alarm. A memory allocation error has occurred and has caused an interruption of service of a critical piece of the system. Possible loss of call processing.
Action The system will recover automatically. Observe system operation.
ALM107: Memory Allocation Failure
Explanation Major alarm. A memory allocation error has occurred and has caused an interruption of service of a major piece of the system. Possible loss of call processing.
Action The system will recover automatically. Observe system operation.
ALM108: Memory Allocation Failure
Explanation Minor alarm. A memory allocation error has occurred and has caused an interruption of service of a minor piece of the system. Possible loss of call processing.
Action The system will recover automatically. Observe system operation.
ALM109: Memory Allocation Failure
Explanation General alarm. A memory allocation error has occurred that does not fit into one of the above categories. Possible loss of call processing.
Action The system will recover automatically. Observe system operation.
ALM150: Live Upgrade Start
Explanation A nonalarmed event was reported to indicate the start of a live upgrade on the switch. A live upgrade is in progress.
Action This alarm is maintained on the switch until it is cleared by a different live upgrade event or the system is reset.
ALM151: Live Upgrade Software Installed
Explanation A nonalarmed event was reported to indicate the successful completion of the software installation step during a live upgrade on the switch. A live upgrade is in progress.
Action This alarm is maintained on the switch until it is cleared by a different live upgrade event or the system is reset.
ALM152: Optional S/W Configuration Initiated
Explanation A nonalarmed event was reported to indicate the start of the enable/configure software options step for a live upgrade on the switch. A live upgrade is in progress.
Action This alarm is maintained on the switch until it is cleared by a different live upgrade event or the system is reset.
ALM153: Rebooting Generic with New Release
Explanation A nonalarmed event was reported to indicate that the system controller has been reset as part of the live upgrade procedure. The controller has been upgraded and is being rebooted.
Action This alarm is maintained on the switch until it is cleared by a different live upgrade event. Note that this alarm is maintained after the system is reset.
ALM154: Card Cutover Initiated
Explanation A nonalarmed event was reported to indicate the start of the live upgrade card cutover step. A live upgrade is in progress. Cards will be downloaded with new software.
Action This alarm is maintained on the switch until it is cleared by a different live upgrade event or the system is reset.
ALM155: Live Upgrade Failed
Explanation A nonalarmed event was reported to indicate a failed live upgrade on the switch. The cause of the failure is recorded in the live upgrade log.
Action If the cause of the failure cannot be remedied, contact the Cisco Systems TAC. This alarm is maintained on the switch until it is cleared by the Start Live Upgrade event or the system is reset.
ALM156: Live Upgrade Successful
Explanation A nonalarmed event was reported to indicate a successful live upgrade on the switch.
Action This alarm is maintained on the switch until it is cleared by the Start Live Upgrade event or the system is reset.
ALM157: Live Upgrade Aborted by User
Explanation A nonalarmed event was reported to indicate that the user aborted the live upgrade.
Action This alarm is maintained on the switch until it is cleared by the Start Live Upgrade event or the system is reset.
Posted: Sat Sep 28 15:26:04 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.