ATT AUDIX Voice Power Release 2.1.1 Guide

							Appendix B: Error Messages
605 (ET_CKSHMEM), MAJOR
ET has Tried to Check/Reinit its SHMEM (ETCOUNTS)
ET tried to check/reinitialize its shared memory. If this message occurs
continuously without a user’s request, ET will not work properly until this is
fixed.
n     Try stopping and restarting the system.
n      If this message persists, call your AT&T Field Service
Representative for assistance.
606 (ET_ESLOT), INFORM
ET Discarded Msg of Type : Error Count Array Full
A software error exists or ET is getting an extreme number of messages.
n      Call your AT&T Field Service Representative for assistance when
convenient.
607 (ET_MSGRCV), CRITICAL
ET Not Read Msg: errno = , rc = 
Something is wrong with the interprocess communication. ET cannot
receive messages.
n     Try stopping and restarting the system.
n     Call your AT&T Field Service Representative for assistance.
608 (ET_MSGSND), CRITICAL
ET Not Send Msg to : errno = , rc = 
Something is wrong with the interprocess communication. ET cannot send
a message to the specified process.
n     Try stopping and restarting the system.
n     Call your AT&T Field Service Representative for assistance.
B-21 
						

							Appendix B: Error Messages
609 (ET_NO_ATT), MAJOR
Cannot open ATT Error Rules File (vs/data/errors)
n     Check to see that the file /vs/data/errors exists and check its
permissions.
610 (ET_NOQ), CRITICAL
ET Cannot Open its Message Queue
Something is wrong with the interprocess communication. ET cannot open
its message queue.
n    Try stopping and restarting the system.
n    Call your AT&T Field Service Representative for assistance.
611 (ET_NORULES), MAJOR
ET Cannot Access Error Rules File ()
ET cannot access the specified error rules file. ET will not work properly
until this problem is fixed.
n    Call your AT&T Field Service Representative for assistance.
612 (ET_NOSHMEM), CRITICAL
ET Cannot Attach SHMEM 
ET is having problems with its shared memory. ET will not work properly
until this problem is fixed.
n    Try stopping and restarting the system.
n     Call your AT&T Field Service Representative for assistance.
B-22 
						

							Appendix B: Error Messages
613 (ET_NO_ VAR), INFORM
Cannot open VAR Error Rules File (gendb/data/errors)
This is an informational message unless there is supposed to be a VAR
error file. The application-specific error rules file is missing.
n     Contact the provider of the application software package that is
installed.
616 (ET_SHMIT), INFORM
ET Shared Memory (SHMEM ETCOUNTS) Init
ET initialized its shared memory. This is an informational message. No
action is required.
617 (ET_SHOWER), STATUS
ET Printing Rules as Requested
This should not appear unless the user asks ET to print its rule file. This is
an informational message. No action is required.
618 (ET_VAR), INFORM
Unexpected EOF on VAR Err Rules File after  Lines
There is an error in the VAR rules file.
n     Contact the provider(s) of the application packages that are
installed.
620 (ET_DEBUG), STATUS
ET Verbose Mode for Debugging Toggled
This message should not appear unless the user sends the MSG to ET.
n     If the verbose mode appeared unexpectedly, report this to your
AT&T Field Service Representative.
B-23 
						

							Appendix B: Error Messages
621 (ET_FLOOD), INFORM

This message is printed as a result of the flood control being turned on to
prevent messages from flooding the screen or the ET history file.
622 (ET_URS), CRITICAL
User Ordered ET to RESTART System
The user ordered ET to restart the system.
623 (ET_URB), CRITICAL
User Ordered ET to REBOOT System
The user ordered ET to restart the system.
624 (ET_WIPE), INFORM
ET Removed Defunct Process  () from Bulletin
Board
ET removed a defunct processor an invalid process entry it found in the
bulletin board.
n     This message should be reported to your AT&T Field Service
Representative.
626 (ET_STUCK), MAJOR
ET Noticed  () to be Stuck
ET noticed that the specified process was hung. This error message will
continue to appear until something is done about the process bulletin
board entry.
n     Stopping and restarting the system should clear the bulletin board.
n     This message should be reported to your AT&T Field Service
Representative.
B-24 
						

							Appendix B: Error Messages
627 (ET_BAD_ARGS), INFORM
Invld channel ()/brd() for msgid()
Recvd from 
ET received a message with bad arguments (for example, an invalid
board number, invalid channel number for the given board number, etc.).
628 (ET_NEW_PID), MAJOR
ET Noticed PID for  changed:  to ;
Proc probably respawned
ET noticed the process ID for a given process changed, which indicates
that the process probably died and respawned.
n     This message should be reported to your AT&T Field Service
Representative.
651 (ET_DYKE), STATUS
ET turned flood control  as requested
The user ordered ET to turn its flood control on or off via the etset
command.
652 (ET_NEWS), STATUS
ET set summary to  as requested
The user ordered ET to set the summary to be displayed only when it
receives new error messages since it last displayed the summary or all
the time regardless of whether it receives any new messages. The user
made the request via the etset command.
653 (ET_PRIORITY), STATUS
ET set summary priority to  as requested
The user ordered ET to set its summary priority level to the specified level
via the etset command.
B-25 
						

							Appendix B: Error Messages
654 (ET_SUMSHOW), STATUS
ET showed summary settings as requested
The user ordered ET to display its current summary settings. The user
made the request via the etset command.
655 (ET_SUMTIME), STATUS
ET set summary Interval to  minutes as requested
The user ordered ET to set its summary interval for the time between the
display of summary messages to the specified number of minutes via the
etset command.
Maintenance (MTC) Process
700 (STA_CHAN), STATUS
MTC reports channel  is now in state 
Maintenance reports that the permanent state of a channel has changed.
701 (STA_CARD), STATUS
MTC reports card  is now in state 
Maintenance reports that the permanent state of a card has changed.
710 (INV_RQST), INFORM
MTC received invalid request, morig=, mcont=,
reqst=
Maintenance received an invalid request message. The message has
been ignored. This is an indication of software problems.
n     If this error persists, try stopping and restarting the system.
B-26 
						

							Appendix B: Error Messages
711 (INV_TSMR), INFORM
MTC received Invalid tsmr, state= , mcont=
Maintenance received an invalid response from TSM. The response has
been ignored. This is an indication of software problems.
n     If this error persists, try stopping and restarting the system.
712 (INV_MESG), INFORM
MTG received invalid message, state=, morig=,
mcont=
Maintenance received an invalid message while interacting with TSM.
The message has been ignored. This is an indication of software
problems.
n     If this error persists, try stopping and restarting the system.
713 (RLS_FAIL), MAJOR
Maintenance cannot acquire a device from TSM. This is an indication of
software problems.
n     If this error persists, try stopping and restarting the system.
714 (RCVE_MSG), CRITICAL
MTC cannot receive a message, return= , errno=,

Maintenance cannot receive messages. This is an indication of system
problems.
n     Try stopping and restarting the system or rebooting the system.
B-27 
						

							Appendix B: Error Messages
715 (SEND_MSG), CRITICAL
MTC cannot send a message, return= , errno=
Maintenance cannot send messages. This is an indication of system
problems.
n      Try stopping and restarting the system or rebooting the system.
716 (UNK_TYPE), MAJOR
MTC detected an invalid type (), on card 
Maintenance detected an invalid device type in shared memory. This is an
indication of system problems.
n     Try stopping and restarting the system or rebooting the system.
717 (SYS_FAIL), MAJOR
MTC cannot  for card , return=,
errno=
Maintenance failed a system call. This is an indication of system
problems.
n   Try stopping and restarting the system or rebooting the system.
718 (NO_CLOCK), MAJOR
MTC cannot find clock on card 
Maintenance detected no clock on a system-master board. This is an
indication of hardware problems. The board may need to be replaced.
n   Try removing the device from service and rebooting the system. If
the device passes initial boot diagnostics, you may then restore the
device.
B-28 
						

							Appendix B: Error Messages
722 (GET_SEMA), MAJOR
MTC cannot acquire the semaphore
Maintenance cannot create the semaphore. This is an indication of
system problems.
n     Try stopping and restarting the system or rebooting the system.
723 (SET_SEMA), MAJOR
MTC cannot set the semaphore
Maintenance cannot lock the semaphore. This is an indication of software
problems.
n      Try stopping and restarting the system or rebooting the system.
724 (SHM_FAIL), CRITICAL
MTC cannot attach the  area
Maintenance cannot attach shared memory. This is an indication of
software problems.
n    Try stopping and restarting the system or rebooting the system.
725 (SHM_INVD), CRITICAL
MTC detects a invalid  area
Maintenance detected invalid shared memory. This is an indication of
software problems.
n     Try stopping and restarting the system or rebooting the system.
726 (OPN_FAIL), CRITICAL
MTC cannot perform a 
Maintenance cannot open the tip/ring driver. This is an indication of
software problems.
n    Try stopping and restarting the system or rebooting the system.
B-29 
						

							Appendix B: Error Messages 
727 (CLR_SEMA), MAJOR
MTC cannot clear the semaphore
Maintenance cannot unlock the semaphore. This is an indication of
software problems.
n    Try stopping and restarting the system or rebooting the system.
740 (DG_START), STATUS
MTC reports diag started on () card 
Maintenance reports that diagnostics have started on a hardware card.
741 (DG_RESLT), STATUS
MTC reports diag results on card , return=,
errno=, 
Maintenance reports on diagnostic results.
742 (DG_PASSD), STATUS
MTC reports diag passed on () card 
Maintenance reports that diagnostics have passed on a hardware card.
750 (DG_FAILD), STATUS
MTC reports diag failed on card , because 
Maintenance reports that diagnostics have failed on a hardware card. This
is an indication of hardware problems. The board may need to be
replaced.
n    Try removing the device from service, and rebooting the system.  If
the device passes initial boot diagnostics, you may then restore the
device.
B-30