12.4.16  

HiPath 3000-Error mess. (Entries in the event log for HiPath 3000) 
 

Classification  
Accrued errors are classified according to error class and error number. The three different error classes are described below:
 •   Error Class A = Customer-related error
HiPath 3000/5000 Manager E fails to issue a signal/message. Class A errors are indicated on the optiPoint Attendant display. They can be corrected by the customer without service support.
    The following error messages are implemented at present:
   -   "Printer Alarm" (caused by paper out, for example)
   -   "Fan Failure" (caused by failure of the fan with HiPath 3500 or HiPath 3300)
   -   "Revisor Alarm" (caused by overflow of the log part of the MMC, for example).
   -   "Too Many Key Modules" (caused by attaching more than the maximum possible number of optiPoint key modules specified in Table 10-9)
 •   Error Class B = Service-related errors
Class B errors can be read out via the HiPath 3000/5000 Manager E Event Log, which can be automatically forwarded to a service center.
Errors of this class are, for example, failure of the boards, individual ports, or trunks. You can generally correct these errors by replacing the hardware, re-configuring the customer database, or by working together with the carrier. Table 12-7 lists all Class B errors.
 •   Error Class C = Development-related errors
HiPath 3000/5000 Manager E fails to issue a signal/message.
Class C errors require diagnosis and problem analysis by specialists.

 Table 12-7   HiPath 3000 Class B Error Messages
 No.  
 HiPath 3000/5000 Manager E:
Event Log Entry  
 Meaning  
 Required Measures  
 Note  
Error Class 01 - General Messages  
01-003  
!System Restart  
Hard restart (reset) of entire system with current CDB.  
None  
 
01-010  
!SNMP System Restart  
Hard restart of entire system via SNMP.  
None  
 
01-014  
local DB changes  
"On site" changes to the database.  
None  
 
01-015  
remote DB changes  
"Remote" changes to the database.  
None  
 
01-016  
!SNMP APSXF result  
APS transfer acknowledgement message via SNMP.  
None  
 
01-017  
!SNMP authentication fail  
Unauthorized access attempt.  
Check firewall settings in HiPath 3000/5000 Manager E (Network - Firewall).  
 
01-018  
!SNMP 80 % high watermark of log-file  
Changes logged internally in the system: 80 % of write capacity used.  
Read out data using HiPath 3000/5000 Manager E (Transfer - Security - Protocol).  
 
01-019  
!Sensor Alarm  
Temperature in HiPath 3500/HiPath 3300 19" housing is too high.  
Check the fan and air supply in the 19" housing. Note the ambient temperature.  
 
01-020  
!CDR buffer limit reached  
Overflow in the CDR buffer (CDR information).  
Check that the interfaces (V.24, LAN), ports and the connection are functioning or read out call data.  
 
01-021  
!Authentication Failure  
Unauthorized access attempt.  
Check firewall settings in HiPath 3000/5000 Manager E (Network - Firewall).  
 
01-022  
!Flash deleted  
Flash area deleted.  
None  
APS transfer possible again.  
01-023  
!Process stopped  
Process stopped.  
Perform hard restart (reset).  
 
01-024  
!unauthorized application  
Attempted access via an unauthorized application.  
Check firewall settings in HiPath 3000/5000 Manager E (Network - Firewall).  
 
01-025  
!manual switchback from HiPath Manager  
 
 
 
Error Class 02 - License Management Messages  
02-002  
!START Grace Period  
HiPath License Management: Start of grace period.  
None  
The remaining license validity period is shown on the display.  
02-003  
!START Reg. Linc File  
HiPath License Management: Start of regular licensing.  
None  
 
Error Class 09 - Hardware Module Messages  
09-000  
!microprocessor fault on, common  
Microprocessor error.  
Check power at the power supply unit.  
If this error persists, replace the central control board.  
 
09-001  
!microprocessor fault off, common  
The microprocessor error has been corrected.  
None  
 
09-002  
!loadware memory fault on, common  
Error in loadware memory.  
Replace the board if necessary.  
 
09-003  
!loadware memory fault off, common  
Error in loadware memory has been corrected.  
None  
 
09-029  
!line interruption (error on)  
Line interruption  
Check the line and terminal.  
 
09-030  
!short circuit (error on)  
Short circuit on the board specified.  
Check the line, terminal, and port.  
 
09-031  
!under voltage (error on)  
Under voltage.  
Check the power and line at the terminal's power supply unit.  
 
09-032  
!thermal overload (error on)  
The specified board is overheated.  
Check the fan and air supply in the 19" housing. Note the ambient temperature.  
 
09-036  
!slip detected on (STMD)  
A bit slip has occurred on an ISDN line.  
Check the S0 line.  
If necessary, reload the board or perform a hard restart.  
If the error persists, set up an ISDN trace.  
The problem may be caused by asynchronous internal and external clock rates.  
Data loss possible/connection may be terminated.  
09-037  
!slip detected off (STMD)  
The bit slip on the ISDN line has been corrected.  
None  
 
09-038  
!alarm indication signal error on (TMS2M)  
Alarm display: An S2M error has occurred.  
Physical line/board problem (too many CRC/SLIP errors).  
Check the S2M line and board.  
Replace the board if necessary.  
If the error persists, set up an ISDN trace.  
 
09-039  
!alarm indication signal error off(TMS2M)  
Alarm display: The S2M error has been corrected.  
None  
 
09-042  
!no signal error on (TMS2M/STMD)  
Alarm display: An S2M error has occurred.  
No physical connection available.  
Check the S2M line and board.  
If necessary, reload the board or perform a hard restart.  
If the error persists, set up an ISDN trace.  
 
09-043  
!no signal error off (TMS2M/STMD)  
Alarm display: The S2M error has been corrected.  
None  
 
09-044  
!receive remote alarm error on (TMS2M)  
Alarm display: An S2M error has occurred.  
Physical problem with the communication partner (too many CRC/SLIP errors).  
Check the board and partner system or arrange for a technician to do so.  
 
09-045  
!receive remote alarm error off (TMS2M)  
Alarm display: The S2M error has been corrected.  
None  
 
09-048  
!bitslip error on (TMS2M)  
A bit slip has occurred on an ISDN line.  
Check the S2M line.  
If necessary, reload the board or perform a hard restart.  
If the error persists, set up an ISDN trace.  
The problem may be caused by asynchronous internal and external clock rates.  
Data loss possible/connection may be terminated.  
09-049  
!bitslip error off (TMS2M)  
The bit slip on the ISDN line has been corrected.  
None  
 
09-050  
!loss of synchronization error on (TMS2M)  
A synchronization error has occurred.  
Check the S2M line.  
If necessary, reload the board or perform a hard restart.  
If the error persists, set up an ISDN trace.  
The problem may be caused by asynchronous internal and external clock rates.  
Data loss possible/connection may be terminated.  
09-051  
!loss of synchronization error off (TMS2M)  
The synchronization error has been corrected.  
None  
 
09-058  
!Self test error on (SLMO)  
Error while self-testing the specified SLMO board.  
If necessary, replace the board or change the slot.  
 
09-059  
!Self test error off (SLMO)  
Error while self-testing the specified SLMO board has been corrected.  
None  
 
09-061  
!Overcurrent on power controller on (SLMO)  
Overcurrent on the specified SLMO board.  
Check the power and line on the terminal and power supply unit.  
Replace hardware if necessary.  
 
09-062  
!Overcurrent on power controller off (SLMO  
Overcurrent on the specified SLMO board has been corrected.  
None  
 
09-065  
!Out of buffers for card error on  
Insufficient pool capacity on the specified SLMO board.  
Check lines and terminals. Set up a default trace.  
 •   High traffic load: -> Distribute load to several boards.
 •   Board is faulty: -> Replace board.
 
09-066  
!Out of buffers for card error off  
Insufficient pool capacity on the specified SLMO board has been corrected.  
None  
 
Error Class 11 - General Messages  
11-058  
!Too many L1 errors  
Too many layer 1 errors.  
Check the lines, terminal, and port.  
A short circuit may have occurred.  
 
Error Class 12 - Processor Exceptions  
12-000  
Initial Stack Ptr  
Reset: Initial Stack Pointer  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-001  
Initial Prg. Counter  
Reset: Initial Program Counter  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-002  
bus_error  
Interrupt Bus Error  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
In the case of HiPath 3550 or HiPath 3500, this problem may be caused by a software error -> Upgrade required.  
 
12-003  
address_error  
Interrupt Address Error  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-004  
illegal_instruction  
Interrupt Illegal Instruction  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-005  
zero_division  
Interrupt Zero Division  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-006  
Invalid opcode  
Invalid Opcode Exception  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-007  
TRAP V Instructions  
TRAPcc, TRAP V Instructions  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-008  
Privilege Violation  
Privilege Violation  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-009  
Trace  
Trace  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-010  
Line 1010 Emulator  
Line 1010 Emulator  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-011  
Line 1111 Emulator  
Line 1111 Emulator  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-012  
Hardware Breakpoint  
Hardware Breakpoint  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-013  
Reserved Coproc. Violation  
Reserved Coprocessor Violation  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-014  
Format Error Uninit. Inter.  
Format Error Uninitialized Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-015  
Format Error Uninit. Inter.  
Format Error Uninitialized Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-017  
critical input interrupt  
HiPath 3800, Offset 0x0100, Critical Input Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-018  
machine check interrupt  
HiPath 3800, Offset 0x0200, Machine Check Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-019  
data storage interrupt  
HiPath 3800, Offset 0x0300, Data Storage Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-020  
instr. storage interrupt  
HiPath 3800, Offset 0x0400, Instruction Storage Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-021  
alignment interrupt  
HiPath 3800, Offset 0x0600, Alignment Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-022  
program interrupt  
HiPath 3800, Offset 0x0700, Program Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-023  
system call interrupt  
HiPath 3800, Offset 0x0C00, System Call Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-025  
watchdog timer interrupt  
HiPath 3800, Offset 0x1020, Watchdog Timer Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-026  
Data TLB interrupt  
HiPath 3800, Offset 0x1100, Data TLB Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-027  
Instruction TLB interrupt  
HiPath 3800, Offset 0x1200, Instruction TLB Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
12-028  
debug interrupt  
HiPath 3800, Offset 0x2000, Debug Interrupt  
Create a trace.  
Create a stack dump.  
Save a snapshot.  
 
Error Class 15 - Messages Concerning APS Transfer and Saving on Flash  
15-000  
!Req to switch over APSXF  
Request for APS transfer.  
None  
 
15-001  
!APS switched over KDS ok  
APS transfer was successful.  
None  
 
15-002  
!APS switched over def. KDS  
APS transfer was not successful.  
Default CDB loaded.  
Check CDB version.  
 
15-003  
!CRC checksum error  
Error in CRC checksum.  
Check APS version.  
Transfer APS again.  
If the error persists, replace the MMC module.  
 
15-004  
!APS switched back def. KDS  
APS transfer was not successful.  
Default CDB loaded.  
Load stored CDB onto the system.  
Check APS version.  
Provide snapshot and stack dump for analysis.  
Restart APS transfer or perform a speed upgrade.  
If the error persists, replace the MMC module.  
An error occurred while starting up the new APS. The system has switched back to the old APS. As a result, the CDB was set to "Default".  
15-005  
!APS switched back old KDS  
APS transfer was not successful.  
Old CDB loaded.  
Load stored CDB onto the system.  
Check APS version.  
Provide snapshot and stack dump for analysis.  
Restart APS transfer or perform a speed upgrade.  
If the error persists, replace the MMC module.  
An error occurred while starting up the new APS. The system has switched back to the old APS.  
15-006  
!APS Transfer disconnected  
APS transfer interrupted.  
Check the transmission link and interface.  
Restart APS transfer.  
 
15-007  
!Country-text transferred  
Country-specific texts successfully transferred.  
None  
 
15-008  
!Error by deleting MMC  
Shadow APS cannot be deleted.  
Check APS version.  
Restart APS transfer.  
If the error persists, replace the MMC module.  
 
15-009  
!Blck_length err apsxf/ctxt  
Block length error during country-specific text transfer.  
Check the transmission link and interface.  
Transfer APS again.  
 
15-010  
!Rest_length err apsxf/ctxt  
Remaining length error during country-specific text transfer.  
Check the transmission link and interface.  
Transfer APS again.  
 
15-011  
!Speed-Upgrade  
Speed upgrade was successful.  
None  
Software was updated. Previous CDB is still used.  
15-012  
!APSXF aborted  
APS transfer was manually stopped.  
None  
 
Error Class 16 - Operating System Messages  
16-001  
GET-POOL xx, xx from=xx addr=xxxxxxxx  
Error in system pool administration.  
Set up a trace using information from BLS (Back Level Support).  
Create a stack dump.  
Save a snapshot.  
 
16-002  
RELPL xxxxxxxxx len=xxxx, from=xx  
Error in system pool administration.  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
16-004  
!Error in Cosmos-Send  
COSMOS send error (software message transmission).  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
16-005  
!Error in Cosmos-Timer  
COSMOS timer error (software timer administration).  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
16-006  
!Error in Cosmos-Receive  
COSMOS receive error (software message receipt).  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
16-007  
COSMOS ID=xx opcode=0xnnnn ercode=0xnnnn  
COSMOS error during restart  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
16-009  
RESTARTED: watchdog  
Overload or continuous loops during software operation.  
System watchdog restarted the system.  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
The system was un able to reach idle status within approximately ten minutes.  
16-010  
RESTARTED: manual Reset  
Hard restart (reset) was manually triggered.  
None  
 
16-011  
RESTARTED: manual Reload  
Manual reload.  
None  
The CDB is reset to default status.  
16-012  
RESTARTED: Power down  
No power  
Check line voltage.  
Check power supply.  
 
16-013  
!KDS backup not performed  
Customer data was not backed up to MMC.  
Check the MMC module and replace if necessary.  
 
16-014  
RESTARTED: unknown rest. HW-ind. mismatched  
Hardware reports an unknown reset reason.  
Check environmental influences (for example, grounding).  
Central control board problem: -> Replace board.  
 
16-015  
!general error logging  
Error while writing the log file to the MMC module.  
Check the MMC module and replace if necessary.  
 
16-017  
!CTXT take over failed  
Country-specific texts cannot be applied.  
Retransfer country-specific texts and change the language again.  
 
16-020  
!CSTA: length out of range  
CSTA interface: Required length exceeds the permitted range. Incorrect internal parameters.  
Use the CSTA browser (application emulation) to check the CSTA interface.  
Set up a CSTA trace and a default system trace.  
Check whether or not the application has been released.  
 
16-021  
!CSTA: Alloc() error  
CSTA interface: Allocation fails.  
Use the CSTA browser (application emulation) to check the CSTA interface.  
Set up a default trace with CSTA.  
 
16-023  
APS x fetched from MMC  
Startup acknowledgement after speed upgrade.  
None  
 
16-024  
!idle arrived after restart  
System has reached idle status after restart.  
None  
 
16-030  
!exceed. of CSTA mon. pts  
Number of CSTA monitor points exceeded.  
Check the number of subscribers, lines, and ACD groups configured.  
 
Error Class 18 - Messages Concerning Database Handling and License Management  
18-012  
HLM:Start grace period  
HiPath License Management: Grace period was started.  
If necessary, load license from the CLS and relicense the system.  
The remaining license validity period is shown on the display.  
18-016  
HLM:Feat-ID: xxx expiration started  
HiPath License Management: The specified feature is still valid for up to 30 days.  
If the customer still requires this feature, a new license file must be ordered and loaded to the system.  
The remaining license validity period is shown on the display.  
18-017  
HLM:Feat-ID: xxx expired  
HiPath License Management: The validity period of the specified feature has expired.  
If the customer still requires this feature, a new license file must be ordered and loaded to the system.  
 
18-018  
HLM: set license to default  
HiPath License Management: All licenses were deleted.  
Load license from the CLS and relicense the system.  
This error only occurs in combination with the following error messages:  
1. HLM: Invalid license data.  
2. HLM: MAC ID mismatch.  
3. HLM: Lic failure period stopped default lic.  
4. HLM: Grace period stopped, default license.  
All licenses are deleted in each of these cases.  
18-019  
HLM: Invalid license data  
HiPath License Management: The license file is invalid or has been manipulated.  
Check licensing.  
Load the original license file from the CLS and relicense the system.  
 
18-020  
HLM:Lic failure period started  
HiPath License Management: The system is no longer connected to HiPath 5000 RSM.  
Check and reestablish the connection to HiPath 5000 RSM.  
The system was licensed in a network and is now no longer connected to HiPath 5000 RSM.  
You have 30 days to reestablish the connection. All system licenses will be deleted after this period.  
18-021  
HLM:Lic failure period stopped license ok  
HiPath License Management: The connection between the system and HiPath 5000 RSM is reestablished.  
None  
 
18-022  
HLM: Lic failure period stopped default lic  
HiPath License Management: The connection between the system and HiPath 5000 RSM was not reestablished within 30 days. All licenses were deleted.  
Check and reestablish the connection to HiPath 5000 RSM.  
Load license from the CLS and relicense the system.  
 
Error Class 19 - Network Services Messages  
19-002  
!SNTP-Server not responding  
No connection to the SNTP server.  
Check the application and the connection.  
 
Error Class 20 - Call Processing Messages  
20-002  
!RS232: DSR not Ready  
The RS232/V.24 interface is out of order.  
Check the interface, the line, and the application.  
 
20-011  
!RS232: DSR ready  
The RS232/V.24 interface is now operational.  
None  
 
20-013  
!not connected ways  
The maximum number of connection paths permitted has been exceeded.  
Use the project planning tool to test the system configuration.  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
20-017  
!int. charg buf ovflw  
Internal call data memory overflow.  
Read out call data.  
If the error persists, check the call data application interface.  
 
20-029  
!Forced trunk disconnection  
Manual line release (for U.S. only).  
None  
 
20-032  
!CDR Mem. alloc. failed  
Advanced call data memory cannot be created.  
 •   System with MMC module: MMC module is faulty. Replace the MMC.
 •   HiPath 2000: File system in flash is full or faulty.
 
20-033  
!CDR Cache alloc. failed  
Read cache for reading out CDR data cannot be created.  
Perform a hard restart (normally occurs automatically).  
This is caused by insufficient system memory capacity.  
20-034  
!CDR Data write failed  
Error while writing CDR data to the advanced call data memory.  
MMC module: If necessary, read out call data via TFTP. The internal administration structure is also corrected, if this is required.  
 
20-035  
!CDR Adm. write failed  
Error while writing the administration structure to the advanced call data memory.  
MMC module: If necessary, read out call data via TFTP. After this, replace the MMC module.  
 
20-036  
!CDR Data read failed  
Error while reading CDR data from the advanced call data memory.  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
20-037  
!CDR Adm. read failed  
Error while reading administration structure from the advanced call data memory.  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
20-038  
!CDR Data detected  
An advanced call data memory was found during system startup.  
None  
 
20-039  
!CDR Data overflow  
The advanced call data memory is full.  
Read out call data.  
 
20-040  
!CDR Mem. allocated  
The advanced call data memory was successfully created.  
None  
 
20-041  
!CDR Mem. released  
The advanced call data memory was temporarily released.  
None  
This message is issued after the call data memory has been completely read out. It must be followed by the "CDR Mem. allocated" message.  
20-042  
!MMC-size  
Output of MMC module size  
None  
During system startup, the size of the MMC module is read out and hexadecimally output in bytes 1 and 2 of the info bytes. Value "00 10" describes the 16-MB MMC, value "00 40" describes the 64-MB MMC.  
This does not apply to HiPath 2000.  
20-043  
!CDR-MMC MMC full  
Memory on the MMC module or in the HiPath 2000 file system is insufficient for creating the advanced call data memory.  
 
 
Error Class 21 - Device Handler Messages  
21-000  
!no dial tone detected  
No dial tone detected.  
Use headset to check dial tone.  
Replace port or terminal if necessary.  
 
21-001  
!dial tone detected  
Dial tone detected.  
None  
 
21-007  
!Clock ON  
ISDN clock found.  
None  
 
21-008  
!Clock OFF  
ISDN clock lost.  
Check that the clock is available on the S0/S2M line.  
If necessary, use HiPath 3000/5000 Manager E to correct the clock's allowed/denied numbers list (Trunk - Clock parameters).  
If necessary, perform a hard restart (reset).  
 
21-011  
!Fan Alarm ON  
Fan error.  
Check the fan and air supply in the 19" housing. Note the ambient temperature.  
 
21-012  
!Fan Alarm OFF  
The fan error has been corrected.  
None  
 
21-013  
!no ack from temp. sensor  
No response from temperature sensor.  
 
 
21-014  
!overload at code receiver  
Not enough DTMF receivers.  
Use a larger system.  
 
21-015  
!overload at code transmit.  
Not enough DTMF transmitters.  
Use a larger system.  
 
21-019  
!Shorten Msg not successful  
Internal error: An overlong ISDN message could not be shortened by deleting Facility IEs.  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
21-028  
!Power Alarm on  
Emergency battery operation due to power outage.  
Check line voltage.  
Note battery capacity.  
 
21-029  
!Power Alarm off  
Power supply restored.  
None  
 
Error Class 23 - Messages from the Device Handler Network  
23-060  
!system hold, no buffer available  
System hold, no more free buffer available.  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
23-061  
!Check config rules for TMDID  
For U.S. only: TMDID boards incorrectly configured.  
Check TMDID board configuration using information from Page 4-48 and correct if necessary.  
 
Error Class 26 - Board Administration Messages  
26-000  
!unknown card type  
Unknown board.  
System does not support the board type. Replace the board with a valid board type or remove it from the system.  
The board may be too old or too new for the system.  
26-001  
!card out of service  
The specified board is out of order.  
None  
 
26-002  
!More than allowed amount of cards  
The maximum number permitted for a certain board type is exceeded.  
Reduce the number of boards of this board type. Note the maximum configuration.  
 
26-003  
!other card type than old card type  
Incompatible board type. The slot is already pre-assigned with a different board type.  
Replace the board or use Assistant T to delete the preassigned board type so that the new board is recognized.  
 
26-004  
!card in service  
The specified board is operational.  
None  
 
26-007  
!Reload after load-LW-Code error  
The specified board has been reloaded due to a startup error.  
If this error persists, replace the board.  
The board is reloaded due to a load error (length, checksum error) or a missing or delayed acknowledgement during startup.  
Error Class 28 - Recovery Messages  
28-000  
!not possible to send a message  
Error while transmitting message via COSMOS (insufficient resources).  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
28-004  
!SLC-Trace finished  
SLC LW trace transferred to trace memory.  
Trace memory can now be read out.  
 
28-006  
--- tttttttt -> hh:mm:ss --- DD.MM.YY ---  
Time stamp set in event log B memory.  
None  
A time stamp (current time and date) is entered when the event log B memory is copied. This facilitates analysis.  
28-008  
--- APS: Hexxxxx.xx.xxx:xx xxx ----  
Current APS version entered in event log B memory.  
None  
The current APS version is entered when the event log B memory is copied. This facilitates analysis.  
Error Class 29 - Messages Concerning Board Communication  
29-000  
!error from COSMOS  
COSMOS error.  
Set up a trace using information from BLS.  
Create a stack dump.  
Save a snapshot.  
 
29-010  
!receive buffer not free  
Receive buffer is not free.  
Set up a trace using information from BLS.  
The board receive buffer cannot receive messages from the system (performance problems).  
29-014  
!illegal pointer  
Invalid pointer.  
Set up IOP trace.  
 
29-024  
!polling time out  
The specified board has malfunctioned.  
If this error persists, check the board and the slot.  
 
29-025  
!card ist present-LW has reset itself  
Loadware of specified board restarted.  
If this error persists, check the board and the slot.  
 
29-035  
!ELIC deadlock no Interrupt from ELIC  
ELIC clock supply malfunction.  
Check clock supply.  
Check central control board.  
Possible causes:  
 •   Faulty clock supply
 •   Environmental influences
 •   Faulty control board
Error Class 30 - Board Software Messages  
30-006  
!XCSEPBC: PBC error  
PBC or ELIC error on the specified board.  
Replace board.  
 
30-016  
!HEATER ON - HXG3  
Temperature in HiPath 3550/HiPath 3350 wall housing is too high.  
Check the fan kit and the air supply in the wall housing. Note the ambient temperature.  
 
30-017  
!HEATER OFF - HXG3  
Temperature in HiPath 3550/HiPath 3350 wall housing is normal.  
None  
 
30-061  
!short circuit on Upoe Port SLMC on  
Short circuit in base station line.  
Check lines.  
Replace base stations.  
 
30-062  
!short circuit on Upoe Port SLMC off  
Short circuit in base station line has been corrected.  
None  
 
Error Class 32 - Messages Concerning IVM (HiPath Xpressions Compact) and EVM (Entry Voice Mail)  
32-000  
!Configuration link up  
 
 
 
32-001  
!Configuration link down  
 
 
 
32-008  
!TIMEOUT during server-msg  
 
 
 
32-010  
!IVM: Exception (unexpected error)  
IVM: An unexpected error has occurred.  
Set up an IVM trace.  
 
32-011  
!IVM: SW-error  
IVM: A software error has occurred.  
Set up an IVM trace.  
Upgrade IVM if necessary.  
 
32-013  
!IVM: HD assignment of memory space 80%  
IVM: 80% of hard disk used.  
Search IVM statistics for mailboxes with too many undeleted messages.  
 
32-014  
!IVM: HD full  
IVM: Hard disk is full.  
Search IVM statistics for mailboxes with too many undeleted messages.  
 
32-015  
!IVM: Mailbox not available  
IVM: Mailbox is not available.  
Check whether the subscriber in question is available in the event log.  
Set up IVM system mailbox if necessary.  
 
32-016  
!IVM: SW_Upgrade not possible  
IVM: Software upgrade is not possible.  
Reload the board if necessary.  
Upgrade software again.  
 
32-017  
!IVM: Reload occurred  
IVM: Reload performed.  
None  
 
32-018  
!IVM: Restore faulty  
IVM: Faulty restore.  
Perform restore again.  
 
32-019  
!IVM: HD assignment of memory space <70 %  
IVM: Hard disk load less than 70%.  
None  
 
32-020  
!IVM: Unauthorized call attempt  
IVM: Unauthorized call attempt.  
If the attempt is unintentional, deactivate the station number length.  
If the attempt is intentional, create an IVM trace to determine the subscriber who made the attempt.  
 
32-030  
VMM Cmd-resp timeout  
EVM: Command response timeout.  
Reload the board.  
If the error persists, replace the board.  
 
32-032  
memory level of 80%  
EVM: 80 % of memory used.  
Check EVM mailboxes for too many undeleted messages.  
 
32-033  
Presence evt from EVM  
EVM: Presence Event from EVM.  
 
 
32-041  
VMM msg limit reached  
EVM: Message limit reached.  
Check EVM mailboxes for too many undeleted messages.  
 
32-042  
no language available  
EVM: No language file available.  
Check available languages on the EVM.  
Load a language if necessary.  
 
32-044  
VMM buffer overflow  
EVM: VMM buffer overflow.  
 
 
32-046  
EVM error during DM  
EVM: EVM error during Data Mode.  
 
 
32-049  
DH_EVM->reset EVM  
EVM: System - DH_EVM -> reset EVM.  
 
 
32-052  
AM com during DM  
EVM: AM Command during Data Mode.  
 
 
32-053  
Memory Full  
EVM: Memory Full.  
 
 
32-055  
No Pill File selected  
EVM: No Pill File Selected.  
Check available languages on the EVM.  
Load a language if necessary.  
 
32-058  
Philips API ERROR  
EVM: Philips API ERROR.  
 
 
32-059  
I2C failure detected  
EVM: I2C failure detected.  
 
 
Error Class 40 - Messages Concerning MMC Module Access  
40-000  
!MMC not plugged or defective  
MMC module cannot be accessed during startup.  
 •   MMC module is not connected: -> Connect the MMC.
 •   MMC module is faulty: -> Replace the MMC.