Nortel Meridian Meridian 1 Maintenance Manual page 281

Table 12
Application messages that appear in the SysLog file (continued)
Message
hlinkX25: disp_msg( ) lseek
failed
hlinkX25: Invalid State: 'state
number'
hlinkX25: bad event:'event
number' - state:'state number'
hlinkX25: above event not
processed
hlinkX25: X.25 Link Reset -
Cause:'cause number'
Diagnostic:'diagnostic number'
hlinkX25: Message Buffer
Overflow Condition Cleared
hlinkX25: Message Buffer
Overflow - Messages May Be
Lost
hlinkX25: invalid ipc state sent
from Hlink
hlinkX25: 'file name': can't open
hlinkX25: disp_msg( ) lseek
failed
hlinkX25: xopen( ) - errno
='UNIX error
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
Chapter 5: Application Module and IPE Module error messages 269
Description
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
It is normal for this message to appear when the
application is started. If it appears any other time, it
indicates an internal application problem. Use
Procedure 2: SBC restart.
This message is normally generated when the
application is started and should be ignored.
This indicates the Host Link (link 1) has been reset.
No action is necessary.
Indicates the application is no longer being
overloaded.
The application is being overloaded due to excess
activity (message trace, monitoring, and so on) during
a heavy message traffic period. Messages may be
lost. Turn off all unnecessary activity on the
Application Module or IPE Module.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
There is a problem opening the trace file for link 1.
The file system may be full. Log in as maint and use
the diskuse command. Refer to the filedelete
command if the disk usage is greater than 95 percent.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Ñ continued Ñ