Nortel Meridian Meridian 1 Maintenance Manual page 291

Table 12
Application messages that appear in the SysLog file (continued)
Message
x25dmin: xopen( ) - errno ='UNIX
error number'
x25dmin: ioctl( ) - errno ='UNIX
error number'
x25dmin: shmget( ) - errno
='UNIX error number'
x25dmin: x25stat_data( ) - errno
='UNIX error number'
x25dmin: lapbstat_data( ) - errno
='UNIX error number'
x25dmin: Initiating Link Panic
Restart
Error: Could not read message
queue after 60 tries
MMLH: Open link failed [errno]
No physical connection
MMLH: HandleSighup: No
physical connection, [errno]
MMLH: HandleSighup:
Synchronization lost
Meridian Link Release 5C/CCR Release 3C Diagnostic and Maintenance Guide
Chapter 5: Application Module and IPE Module error messages 279
Description
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates an internal application problem. Use
Procedure 2: SBC restart.
Indicates that the application is being restarted due to
an X.25 communication software crash.
Indicates that the traffic reporting process could not
report on traffic because it could not establish inter-
process communication.
Indicates that MML Handler (link 2) cannot open the
device connected to the MML. Check the configuration
to see if the device exists (using display link or change
link commands)
The MML cable has become disengaged. Check the
MML cable to make sure that it is still in place.
Ñ end Ñ