|
This topic contains the Alarm and Administrator's Log entries
related to the Message Networking core and its remote machines:
IC - Message Networking Core alarms
Customer-resolvable alarms
The following alarms can be resolved by the system administrator:
Alarm Code: 0002
Event ID: SWFAILRET
Description:
Message Text: Message delivery failed for msgid:xxxxxx error code=xx.
This alarm indicates that the Message Networking module failed to
deliver remote mail.
Message Networking error codes include:
2 - recipient mailbox was full
3 - recipient did not exist
5 - inter-machine permission failure
6 - sending restrictions failure
7 - miscellaneous failure to deliver message
Repair Procedure:
- None. This alarm is for informational purposes only.
Alarm Code: 3003
Event ID: SWRETRYEX
Description:
Retry count or max time for the message exceeded. This alarm is
generated when the maximum transit time is exceeded for a given
message type.
Repair Procedure:
- None. This alarm is for informational purposes only.
Alarm Code: 4000
Event ID: SWIPROCDEAD
Description:
Process <process name> has reached the restart limit of <number>.
A process died unexpectedly and the system has failed to restart
it and keep it running after several tries.
Repair Procedure:
These steps could require assistance from technical support personnel.
- Stop and restart the voice system.
- After the voice system has restarted, wait about ten minutes
to see if any alarm (including this one) occurs, indicating
that either a process has died (or died repeatedly), or a process
could not be started.
- If a major alarm occurs, escalate to technical support personnel
immediately. Otherwise, report the problem to technical support
personnel during normal business hours.
Alarms requiring remote support center contact
If you receive the following alarms, contact
your remote support center.
| ID |
Description |
| 0003
SWICINITFAIL |
IC
module initialization failure. This alarm indicates that the
Message Networking module failed to initialize. |
| 3001
SWICOPENFAIL |
IC database open failure. This alarm indicates that the database
server is not running. |
| 3001
SWICCLOSEFAIL |
IC
database open failure. This alarm indicates that the database
server is not running. |
| 3002
SWICINTERR |
IC
internal error. This alarm indicates that an Message
Networking process could not communicate with another Message
Networking process or that a network problem occurred. If this
alarm is active, it is likely that the Message Networking is
not in service or is not installed properly. |
| 3003
SWRETRYEX |
Retry
count or max time for the message exceeded. This alarm is generated
when the maximum transit time is exceeded for a given message
type. |
|
3004 SWICORAINTERR |
This
alarm can indicate a database error. |
| 3005
SWICINVALIDVAL |
Invalid
value for sid or nid. This alarm indicates that the system limits
for subscriber IDs and node IDs have been exceeded. |
| 3006
SWICCOREDUMP |
IC
module core dump saved. This alarm indicates that a software
problem caused a core dump of a Message Networking process.
|
| 3007
SWICAUDERR |
IC
audit failed. This alarm indicates that an audit of the Message
Networking database failed. This alarm does not mean that the
Message Networking database is corrupted. |
AG - AMIS Analog alarms
Customer-resolvable alarms
There are no customer-resolvable AG alarms.
Alarms requiring remote support center contact
If you receive the following alarms, contact
your remote support center.
| ID |
Description |
| AAG001 |
Unable
to determine status of incoming call. The incoming call did
not contain the AMIS start protocol tones. |
| AAG002 |
Unable
to connect to remote machine <machine name>. The AAG did
not receive the AMIS start protocol tones when trying to connect
to a remote AMIS machine.
TSC
Only:
- Check
the dial string for the remote machine through the telephone
or screen interface.
- Check
the IVC6 card and the telephone line connections to determine
if excessive noise on the line might have caused the touchtones
to not be recognized
|
| AAG011 |
Timeout
in the middle of protocol <protocol step>. The initial
connection was made, but the AAG did not receive any protocol
tone during the <protocol step>
indicated in the message text.
TSC Only: Check the analog-line voice card and the telephone
line connections to determine if excessive noise on the line
might have caused the touchtones to not be recognized. Also check
the /aag/text/README.DELAY file for descriptions of the delays.
|
| AAG012 |
Remote
machine <machine name> disconnected.
TSC Only: Check the logs on the remote machine to determine
the cause of the error. |
| AAG013 |
Checksum
error. The AAG script detected a protocol error during transmission.
TSC Only: Check the IVC6 card and the telephone line
connections to determine if excessive noise on the line might
have caused the touchtones to not be recognized. |
| AAG014
|
Zero
Messages Received. The AAG receive script did not receive any
messages. There was no error detected in the protocol. This
could indicate that the remote machine experienced an error
during message transmission.
TSC Only: Check the logs on the remote machine to determine
the cause of the error. |
| AAG015 |
Unable
to Access Message. The AAG script was unable to access a message.
TSC Only: This alarm is a software problem. Use standard
escalation procedures. |
| AAG016 |
Do
Not Accept Messages From This System. The AAG receive script
received a message from an unknown system. |
| AAG021 |
Send
script started without node id. The AMIS send application was
started with a blank machine ID.
TSC Only: This alarm is a software problem. Use standard
escalation procedures. |
| AAG022 |
Send
script started with incorrect node id. The AMIS send script
application was started with an incorrect machine ID. |
| AAG031 |
Database
error. The AAG could not access the database table indicated
in the message text. The database could have been corrupted.
|
| AAG041 |
SCE
failure. The interface between the Service Creation Environment
(SCE) and the AAG returned an error.
TSC Only: This alarm is a software problem. Use standard
escalation procedures. |
| AAG061 |
Too
many invalid login attempts. The system received too many invalid
login attempts.
TSC Only: Verify the administration user ID and password
in the database. |
| AAG081
|
Start
up failure. The AMIS send script trigger mechanism is unable
to start.
TSC Only: Verify that the feature option for the AAG
module is turned on. This alarm is a software problem. Use standard
escalation procedures. |
| AAG082 |
Unable
to initialize socket. A system error has occurred.
TSC Only: This alarm is a software problem. Use standard
escalation procedures. |
| AAG083 |
Client
not registered. The triggering process is not registered in
the system process. The process entry has not automatically
been made in the /etc/services file.
TSC Only: This alarm is a software problem. Use standard
escalation procedures. |
| AAG084 |
Triggering
process starting too frequently. The AAG triggering process
is respawning more than five times in 10 minutes.
TSC Only: This alarm is a software problem. Use standard
escalation procedures. The remote AMIS system entry is either
not present in the AAG table or is wrong. Add the entry or verify
that a valid AMIS system is trying to connect to the Message
Networking system. |
AG process alarms are not resolved at the time the Message Networking
system is started.
TSC Only:
- Access the Maintenance Log. On the Maintenance Log page, enter
IC for Application and SWICAUDERR for Event ID. Click Save.
- In the output, note the name audit(s) that failed and search
for other recent occurrences of the failure of this audit.
- If this audit has failed consistently, escalate to the next
level of support.
OG - Octel Analog Networking alarms
Customer-resolvable alarms
The following alarms can be resolved by the system administrator:
Event ID: ONG001
Description:
Unable to determine status of incoming call. The incoming call
did not contain the Octel Analog Networking start protocol tones.
Repair Procedure:
To resolve the alarm:
- The system administrator could have called the number multiple
times without electing to administer the system; check with the
system administrator to verify that the system has been administered
correctly.
- Excessive noise on the telephone line might have caused the
touchtones to not be recognized; check the telephone lines for
noise and check the analog port board.
- Another machine could be set up incorrectly to call the Octel
Analog Networking protocol; check the machine administration with
the system administrator.
Event ID: ONG002
Description:
Unable to connect to remote machine <machine name>. The Message
Networking system did not receive the Octel Analog Networking start
protocol tones when trying to connect to a remote Aria or Serenade
Analog machine.
Repair Procedure:
To resolve the alarm:
- Excessive noise on the telephone line might have caused the
touchtones to not be recognized; check the telephone lines for
noise and check the analog port board.
- The dial string for this remote machine could be incorrect;
check with the system administrator to verify the dial string.
Event ID: ONG011
Description:
Timed out during <protocol step> while sending|receiving
to|from <machine name>. The initial connection was made and
then the Message Networking system did not receive the protocol
tone during the protocol step mentioned in the message text.
Repair Procedure:
- Excessive noise on the telephone line might have caused the
touchtones to not be recognized; check the telephone lines for
noise and check the analog port board.
Event ID: ONG012
Description:
Remote machine <machine name> disconnected. The remote machine
disconnected prematurely.
Repair Procedure:
- The remote machine probably had an error; the system administrator
needs to check the error logs on the remote machine.
Event ID: ONG013
Description:
Checksum/Frame error during <protocol step> while sending|receiving
to|from <machine name>. The ONG script detected a protocol
error during transmission.
Repair Procedure:
- Excessive noise on the telephone line might have caused the
touchtones to not be recognized; check the telephone lines for
noise and check the analog port board.
Event ID: ONG014
Description:
Zero messages received. The ONG receive script received zero messages.
There was no error detected in the protocol.
Repair Procedure:
- The remote machine probably had an error during message transmission;
the system administrator needs to check the error logs on the
remote machine.
Event ID: ONG016
Description:
Do not accept messages from this system. The ONG receive script
received a message from an unknown system.
Repair Procedure:
- The remote Octel Analog Networking system entry is either not
present in the ONG table or is incorrect.
TSC Only: Either add the Octel Analog Networking system
entry or verify that a valid Octel system is trying to connect to
the Message Networking system.
Event ID: ONG018
Description:
No fax component. The ONG send script received a fax only message.
Repair Procedure:
- None. This alarm is for informational purposes only.
Event ID: ONG021
Description:
Non-deliverable mailbox. The ONG send script attempted to deliver
a message to a special mailbox.
Repair Procedure:
- None. The mailbox is automatically deleted from the Message
Networking system.
Event ID: ONG22
Description:
Mailbox future delivery full. The ONG send script tried to deliver
a future delivery message to a full mailbox.
Repair Procedure:
- The system administrator needs to administer the mailbox on
the remote machine.
Event ID: ONG024
Description:
Remote node disabled. The ONG send script tried to communicate
with a disabled remote machine.
Repair Procedure:
- The system administrator needs to administer the end node back
online.
Event ID: ONG026
Description:
No voice component. The ONG send script is sending a fax-only message
with a system default voice component attached to it.
Repair Procedure:
- None. This alarm is for informational purposes only.
Event ID: ONG051
Description:
Error accessing ONG database table <table name>. The ONG
database could have been corrupted.
Repair Procedure:
- The system administrator needs to restore the database from
backup tapes.
Event ID: ONG062
Description:
Mbx <mailbox number> not updated on <node>; Same mailbox
exists on <node>. A duplicate mailbox number exists on end
nodes. Message Networking accepts only the first mailbox number
registered.
Repair Procedure:
- The system administrator needs to determine which user has one
mailbox number on different end nodes. Update the Message Networking
system with the correct mailbox.
- The system administrator can use different dial plans for different
end nodes.
Event ID: ONG063
Description:
Node protocol level < 3; cannot proceed with updates. Directory
updates need to have protocol revision level 3 or later. The end
node protocol revision is less that 3.
Repair Procedure:
- The system administrator needs to check the updates parameters
on the Remote Parameters screen and on the Local System Parameters
screen.
Event ID: ONG067
Description:
Updates <In/Out> not allowed on <Node/Base>; Check
Parameters Screen. The Updates In or Updates Out flag does not permit
updates to or from this node.
Repair Procedure:
- Verify that the Updates In and Updates Out fields on the Message
Networking General Parameters screen are administered correctly.
Event ID: ONG081
Description:
Cannot start Octel Analog Networking script trigger process. The
Octel Analog Networking script trigger mechanism is unable to start.
Repair Procedure:
- The system administrator needs to verify that the Max Number
of Octel Nodes is administered correctly on the Feature Options
screen.
Alarms requiring remote support center contact
If you receive the following events, contact
your remote support center.
| ID |
Description |
| ONG015 |
Unable
to access message component. The ONG send or administration
script received a corrupted message.
TSC Only: The message header on the Message Networking
system might be corrupted or missing; use standard escalation
procedures. |
|
ONG017 |
Remote
node file system full. The ONG send or administration script
received a file system full response.
TSC Only: The remote Octel system does not have enough
space for the message; use standard escalation procedures. |
| ONG019 |
No
access to the Octel node. The ONG send or administration script
has been refused access to the remote Octel system.
TSC Only: The Octel remote machine is not configured
properly for the Message Networking system; use standard escalation
procedures. |
| ONG020 |
Invalid
Opcode. The ONG script does not understand the Opcode received.
TSC Only: Indicates a software error; use standard escalation
procedures. |
| ONG023 |
No
access to remote machine NameNet. The ONG send script could
not access the NAMENET type for a remote machine.
TSC Only: Indicates a software error; use standard escalation
procedures. |
| ONG025 |
Bad
message. The ONG send script delivered a message that the remote
machine could not understand.
TSC Only: Indicates a software error; use standard escalation
procedures. |
| ONG041 |
Script
Octel Analog Networking without node ID. The Octel Analog Networking
protocol was started without machine ID.
TSC Only: Indicates a software error; use standard escalation
procedures. |
| ONG042 |
Script
started with incorrect node ID <ID>. The Octel Analog
Networking protocol was started with an incorrect machine ID.
TSC
Only: Indicates a software error; use standard escalation
procedures. |
| ONG061 |
Radiant
external function <function name> failed, return code
<return code>. The interface between Radiant and an underlying
environment received a return error.
TSC Only: Indicates a software error; use standard escalation
procedures. |
| ONG062 |
Mailbox
not updated. Same mailbox exists on another node. |
| ONG063 |
Updates
not allowed. Check the Parameters screen. |
| ONG064 |
Update
started - node name. |
| ONG065 |
Last
update failed/success - node name. |
| ONG066 |
Update
canceled. Next update start from. |
| ONG082 |
Error
initializing socket: ERRNO xxx. exiting. System error has occurred.
TSC Only: Indicates a software error; use standard escalation
procedures. |
| ONG083 |
Client:
tcp/ONG_trig:unknown service. The triggering process is not
registered in the Message Networking system correctly.
TSC Only: Indicates a software error; use standard escalation
procedures. |
| ONG084 |
The
triggering process is starting too frequently. The triggering
process is respawning more than five times in 10 minutes.
|
Octel Analog Networking process alarms are not resolved at the
time the Message Networking system is started.
TSC Only:
- Access the Maintenance Log.
On the Maintenance Log Display Selection screen enter IC
or EL for Application and SWICAUDERR for Event ID.
Press (Save).
- In the output, note the name audit(s) that failed and search
for other recent occurrences of the failure of this audit.
- If this audit has failed consistently, escalate to the next
level of support.
NW - Networking alarms
Customer-resolvable alarms
The following alarms can be resolved by the system administrator:
Alarm Code: 0003
Event ID: SWINITFAIL
Description:
Module failed to initialize correctly.
Repair Procedure:
These steps could require assistance from technical support personnel:
- Stop and restart the voice system.
- After the voice system has restarted, wait approximately ten
minutes to determine if any alarm (including this one) occurs,
indicating initialization failure.
- If a major alarm occurs, escalate to technical support personnel
immediately. Otherwise, report the problem to technical support
personnel during normal business hours.
Alarm Code: 0000
Event ID: SWIPROCDEAD
Description:
Process <process name> has reached the restart limit of <number>.
A process died unexpectedly and the system has failed to restart
it and keep it running after several tries.
Repair Procedure:
These steps could require assistance from technical support personnel:
- Stop and restart the voice system.
- After the voice system has restarted, wait approximately ten
minutes to determine if any alarm (including this one) occurs,
indicating that either a process has died (or died repeatedly),
or a process could not be started.
- If a major alarm occurs, escalate to technical support personnel
immediately. Otherwise, report the problem to technical support
personnel during normal business hours.
If a major alarm occurs, escalate to technical support personnel
immediately. Otherwise, report the problem to technical support
personnel during normal business hours.
Alarm Code: 0004
Event ID: SWNWVMDBSYNC
Description:
Database failed to initialize correctly.
Repair Procedure:
These steps could require assistance from technical support personnel:
- Stop and restart the voice system.
- After the voice system has restarted, wait approximately ten
minutes to determine if any alarm (including this one) occurs.
- If a major alarm occurs, escalate to technical support personnel
immediately. Otherwise, report the problem to technical support
personnel during normal business hours.
Alarms requiring remote support center contact
If you receive the following events, contact
your remote support center.
| ID |
Description |
| NW
software alarms |
| 1000
SWNONSTD |
Non-standard
NW software in use. |
| 1001 SWCOREDUMP
|
NW module
coredump saved. |
| 1002 SWANECONN |
Connection
failure to machine. |
| 1003 SWXMQFILL
|
Possible
message delivery problem to machine. |
| NW
database alarms |
| 1000 SWNDSTARTFAIL |
Data server
startup failure. |
| 1001 SWNDOPENFAIL |
Database
open failure. |
| 1002 SWNDINTERR |
Database
internal error. |
| 1003 SWAUDDBERR |
Database
audit failure. |
| 1004 SWNDDBERR |
Database
error. |
| 3001 SWNWOPENFAIL
|
Database
open failure. |
| 3004 SWNWORAINTERR |
Database
internal error. |
| 3004 SWICORAINTERR |
Database
internal error. |
SC - SCE events
An SC event is logged during a start_vs (voice) of the system.
This event indicates that the SCE (analog) processes are going to
be started by the SCE process manager. If the process manager fails
to start the processes, a subsequent error is logged. The SC event
requires no action.
SD - Serenade Digital alarms
Customer-resolvable alarms
The following alarms can be resolved by the system administrator:
Event ID: ADM_CPU_3
Description:
loc=<location code>, d1=<data1>d2=<data2>d3=<data3>d4=<data4>.
Serenade Digital Networking administration error. The location code
specifies the general area where the error occurred. Data1 specifies
the type of error. Data2, data3, and data4 are associated with the
particular error type.
Loc code=42, Configuration Error.
d1=0x6, Gateway error mailbox not configured.
d1=0x14, Received inaccessible creator mailbox digits during a digital
network message transfer. d2, d3, and d4 contain the leading six
digits of inaccessible creator mailbox.
d1=0x22, Sent a prefix the remote side did not recognize during
NameSend.
d1=0x23, Other side does not have the NameSend feature.
d1=0x25, Names Directory error during NameSend.
d1=0x2B, Other side does not have the NetName feature.
Loc code=64 LAN Subsystem Error.
d1=0x7, OEM Network Compatibility key of other system does not match
ours. OEM type between systems is incompatible.
Loc code=73 Protocol Revision Level Error.
d1=0x1 Digital Networking.
d2=Local protocol revision level.
d3=Remote protocol revision level.
d4=Location number of remote location.
Repair Procedure:
- Check Serenade configuration on the Message Networking system
and/or remote Serenade remote machine.
Alarms requiring remote support center contact
If you receive the following alarms, contact
your remote support center.
| ID |
Description |
| ERR_SMU_1
|
loc=<location
code>, <error message>. The SMU component experienced
an error. The location code uniquely identifies where the error
occurred. The error message describes the particular error.
|
| ERR_SMU_2 |
loc=<location
code>, <error message>.The SMU component experienced
an error. The location code uniquely identifies where the error
occurred. The error message describes the particular error.
|
| ERR_CPU_1
|
loc=<location
code>,<error message>. The CPU component experienced
an error. The location code uniquely identifies where the error
occurred. The error message describes the particular error.
|
| ERR_CPU_2 |
loc=<location
code>, d1=<data1>,d2=<data2>,d3=<data3>,d4=<data4>.
The CPU component experienced an error. The location code uniquely
identifies where the error occurred. Data1, data2, data3, and
data4 are associated with the particular error. |
| ERR_CPU_4 |
loc=<location
code>,<error message>. The CPU component experienced
an error. The location code uniquely identifies where the error
occurred. The error message describes the particular error.
|
| ERR_VCU_1 |
loc=<location
code>,<error message>. The VCU component experienced
an error. The location code uniquely identifies where the error
occurred. Data1, data2, data3, and data4 are associated with
the particular error. |
| ERR_VCU_2
|
loc=<location
code>,<data1><data2><data3>. The VCU component
experienced an error. The location code uniquely identifies
where the error occurred. Data1, data2, and data3 are data associated
with the particular error. |
| ERR_VCU_3 |
loc=<location
code>,<error message>. The VCU component experienced
an error. The location code uniquely identifies where the error
occurred. |
| ERR_LAN_1
|
loc=<location
code>,<error message>. The LAN component experienced
an error. The location code uniquely identifies where the error
occurred. The error message describes the particular error.
|
| ERR_LAN_2
|
loc=<location
code>,<data1><data2><data3>. The LAN component
experienced an error. The location code uniquely identifies
where the error occurred. Data1, data2, and data3 are associated
with the particular error. |
| ERR_LAN_4 |
loc=<location
code>,<error message>. The LAN component experienced
an error. The location code uniquely identifies where the error
occurred. The error message describes the particular error.
|
| ERR_LIB_1
|
loc=<location
code>,<error message>. The LAN component experienced
an error. The location code uniquely identifies where the error
occurred. The error message describes the particular error.
|
| WRN_CPU_1 |
loc=<location
code>,<error message>. The CPU component experienced
an warning. The location code uniquely identifies where the
warning occurred. The error message describes the particular
warning. |
| WRN_CPU_2 |
loc=<location
code>,<error message>. The CPU component experienced
an warning. The location code uniquely identifies where the
warning occurred. The error message describes the particular
warning. |
| WRN_CON_1 |
Warning
in connection. |
| SWICOPENFAIL |
Database
open failure. This alarm indicates that the database server
is not running. |
| SWICINTERR |
IC
internal error. This alarm indicates that a Message Notification
process could not communicate with another Message Networking
process or that a network problem occurred. If this alarm is
active, it is likely that the Message Networking system is not
in service or is not installed properly. |
| SWICINVALIDVAL |
Invalid
value for sid or nid. |
AD - Aria Digital alarms
Customer-resolvable alarms
There are no customer-resolvable AD alarms.
Alarms requiring remote support center contact
If you receive the following alarms, contact
your remote support center.
| ID |
Description |
| ERR_SOFTWARE |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
software error. The Aria Digital gateway experienced a software
error. The location code uniquely identifies where the error
occurred. The suberr code gives additional information about
the error that occurred. Data1 and data2 are data specific to
the location code. |
| ERR_PROTOCOL |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
protocol error. The Aria Digital gateway experienced a series
of protocol errors. The location code uniquely identifies where
the error occurred. The suberr code gives additional information
about the error that occurred. Data1 and data2 are data specific
to the location code. |
| ERR_NACK |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
negative ack. The Aria Digital gateway received a series of
negative acknowledgements from remote nodes. The location code
uniquely identifies where the error occurred. The suberr code
gives additional information about the error that occurred.
Data1 and data2 are data specific to the location code. |
| ERR_INVMSG |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
invalid message. The Aria Digital gateway encountered an invalid
message. The location code uniquely identifies where the error
occurred. The suberr code gives additional information about
the error that occurred. Data1 and data2 are data specific to
the location code. |
|
ERR_FS |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
file system error. The Aria Digital gateway experienced a file
system error. The location code uniquely identifies where the
error occurred. The suberr code gives additional information
about the error that occurred. Data1 and data2 are data specific
to the location code. |
| ERR_TIMEOUT |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
timeout. The Aria Digital gateway experienced a series of timeouts.
The location code uniquely identifies where the latest error
occurred. The suberr code gives additional information about
the latest error that occurred. Data1 and data2 are data specific
to the location code. |
| ERR_ABORT |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
node requested abort. The Aria Digital gateway received a series
of abort requests from remote nodes. The location code uniquely
identifies where the latest error occurred. The suberr code
gives additional information about the latest error that occurred.
Data1 and data2 are data specific to the location code. |
| ERR_PACKET |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
packet error. The Aria Digital gateway experienced a series
of packet errors. The location code uniquely identifies where
the latest error occurred. The suberr code gives additional
information about the latest error that occurred. Data1 and
data2 are data specific to the location code. |
| ERR_COREFAIL |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
core failure. The Aria Digital gateway experienced a failure
related to the core library area. The location code uniquely
identifies where the error occurred. The suberr code gives additional
information about the error that occurred. Data1 and data2 are
data specific to the location code. |
| ERR_CONNECT |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
connect failure. The Aria Digital gateway experienced a series
of connection failures. The location code uniquely identifies
where the latest error occurred. The suberr code gives additional
information about the latest error that occurred. Data1 and
data2 are data specific to the location code. |
| ERR_SESSION
|
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
session failure. The Aria Digital gateway experienced a series
of errors during session setup. The location code uniquely identifies
where the latest error occurred. The suberr code gives additional
information about the latest error that occurred. Data1 and
data2 are data specific to the location code. |
| ERR_INIT |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
process initialization failure. An Aria Digital gateway process
failed to start up. The location code uniquely identifies where
the error occurred. The suberr code gives additional information
about the error that occurred. Data1 and data2 are data specific
to the location code. |
| ERR_UNKNOWN |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
unknown error. An Aria Digital gateway experienced an unknown
error. The location code uniquely identifies where the error
occurred. The suberr code gives additional information about
the error that occurred. Data1 and data2 are data specific to
the location code. |
| ERR_SYSCALL
|
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
system call error. The Aria Digital gateway experienced a system
call error. The location code uniquely identifies where the
error occurred. The suberr code gives additional information
about the error that occurred. Data1 and data2 are data specific
to the location code. |
| ERR_PROCDEATH |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
unexpected process death. An Aria Digital gateway process died
unexpectedly. The location code uniquely identifies where the
error occurred. The suberr code gives additional information
about the error that occurred. Data1 and data2 are data specific
to the location code. |
| ERR_ENVIRON |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
environment variable not found. The Aria Digital gateway failed
to find a needed environment variable. The location code uniquely
identifies where the error occurred. The suberr code gives additional
information about the error that occurred. Data1 and data2 are
data specific to the location code. |
| ERR_SHMEM |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
shared memory problem. The Aria Digital gateway encountered
a shared memory problem. The location code uniquely identifies
where the error occurred. The suberr code gives additional information
about the error that occurred. Data1 and data2 are data specific
to the location code. |
| ERR_MEMALLOC |
1=<location
code> s=<suberr code> w=<data1> dw=<data2>
memory allocation problem. The Aria Digital gateway encountered
a memory allocation problem. The location code uniquely identifies
where the error occurred. The suberr code gives additional information
about the error that occurred. Data1 and data2 are data specific
to the location code. |
LDAP alarms
Customer-resolvable alarms
There are no customer-resolvable LDAP alarms.
Alarms requiring remote support center contact
If you receive the following alarms, contact
your remote support center.
| ID |
Description |
| SWNWOPENFAIL |
An
LDAP database open failure occurred. |
| SWNWEXECLFAIL |
An
Execl failure occurred. |
VI - VPIM alarms
Customer-resolvable alarms
Alarm Code: 0
Event ID: VCARD_XCODERR
Description:
Transcoder failed: result=<return code>. During communication
with a remote machine, the remote machine transmitted information
that is not supported by Message Networking.
Repair Procedure:
- Make sure that the remote machine has been certified by Avaya
to be compatible with the Message Networking system. If it has
not been certified, differences in the transmission protocol could
prevent proper communication with the remote machine.
Alarm Code: 1
Event ID: VMNODE_READ
Description:
Error reading VM. An unexpected error occurred.
Repair Procedure:
- This is an internal software error. Escalate this problem to
Tier 4 during normal business hours, unless conditions indicate
the need for an immediate resolution.
Alarm Code: 2
Event ID: REAPCHILD_SIG
Description:
Signal failed. An error occurred while the VPIM protocol was processing
the end of a message transmission.
Repair Procedure:
- This is an internal software error. Escalate this problem to
technical support personnel during normal business hours, unless
conditions indicate the need for an immediate resolution.
Alarm Code: 3
Event ID: MIME_SEG
Description:
During processing of a message, an error occurred while attempting
to read from/write to the disk.
Repair Procedure:
One or more file systems used for messaging might have run out
of space. Determine if the /voice file systems are full. If they
are, there are two likely reasons for this to happen. Take the following
steps to address the possible causes (some of these steps could
require assistance from technical support personnel):
- Run dfspace from the
command prompt to see if any file systems are unusually low on or
have run out of space.
- If any file systems are in this condition, check in those file
systems to see if there are ways to free up space without adversely
affecting the system.
- Start at the Administration menu, and select Message Networking
Administration > Subscriber Administration >
Subscriber Count.
The system displays the Subscriber Count page.
If the number is close to or exceeds the advertised limit, the
storage space needed to hold the names is probably reducing the
amount of space available for messages.
- From the command prompt, run audit_vname
to delete voiced names that have not been used for a long time
from the system. Take administrative steps to reduce the number
of voiced names stored on the system.
For example, depending on the type of remote machine, some remote
machines can be administered not to send their voiced names to
the Message Networking system.
- The operating system might need to be rebooted, because an operating
system limitation was exceeded. Follow normal procedures for stopping
the voice system and then rebooting the machine.
Alarm Code: 4
Event ID: MSG_ACC_SVC
Description:
During processing of a message, an error occurred while attempting
to read from/write to the disk.
Repair Procedure:
One or more file systems used for messaging could have run out
of space. Determine if the /voice file systems are full. If they
are, there are two likely reasons for this to happen Take the following
steps to address the possible causes (some of these steps could
require assistance from Avaya remote service center personnel):
- Run dfspace from the command prompt to see if any file
systems are unusually low on or have run out of space.
- If any file systems are in this condition, check in those file
systems to see if there are ways to free up space without adversely
affecting the system.
- Start at the Administration menu, and select Message Networking
Administration > Subscriber Administration > Subscriber
Count.
The system displays the Subscriber Count page.
If the number is close to or exceeds the advertised limit, the
storage space needed to hold the names is probably reducing the
amount of space available for messages.
- From the command prompt, run audit_vname to delete voiced
names that have not been used for a long time from the system.
Take administrative steps to reduce the number of voiced names
in the system.
For example, depending on the type of remote machine, some remote
machines can be administered not to send their voiced names to
the Message Networking system.
- The operating system might need to be rebooted, because an
operating system limitation was exceeded. Follow normal procedures
for stopping the voice system and then rebooting the machine.
Alarm Code: 5
Event ID: NAM_ACC_SVC
Description:
An unexpected error occurred.
Repair Procedure:
- This is an internal software error. Escalate this problem to
technical support personnel during normal business hours, unless
conditions indicate the need for an immediate resolution.
Alarm Code: 6
Event ID: PKGER_SVC
Description:
During processing of a message, an error occurred while attempting
to read from/write to the disk.
Repair Procedure:
One or more file systems used for messaging might have run out
of space. Determine if the /voice file systems are full. If they
are, there are two likely reasons for this to happen. Take the following
steps to address the possible causes (some of these steps could
require assistance from Avaya remote service center personnel):
- Run dfspace from the command prompt to see if any file
systems are unusually low on or have run out of space.
- If any file systems are in this condition, check in those file
systems to see if there are recognizable ways to free up space
without adversely affecting the system.
- Start at the Administration menu, and select Message Networking
Administration > Subscriber Administration >
Subscriber Count.
The system displays the Subscriber Count page.
If the number is close to or exceeds the advertised limit, the
storage space needed to hold the names is probably reducing the
amount of space available for messages.
- From the command prompt, run audit_vname
to delete voiced names that have not been used for a long time
from the system. Take administrative steps to reduce the number
of voiced names stored on the system.
For example, depending on the type of remote machine, some remote
machines can be administered not to send their voiced names to
the Message Networking system.
- The operating system might need to be rebooted, because an
operating system limitation was exceeded. Follow normal procedures
for stopping the voice system and then rebooting the machine.
Alarm Code: 7
Event ID: OUTCALL_MSG
Description:
Error Opening Message. During processing of a message, an error
occurred while attempting to read from/write to the disk.
Repair Procedure:
One or more file systems used for messaging might have run out
of space Determine if the /voice file systems are full. If they
are, there are two likely reasons for this to happen. Take the following
steps to address the possible causes (some of these steps could
require assistance from Avaya remote service center personnel):
- Run dfspace from the command prompt to see if any file
systems are unusually low on or have run out of space.
- If any file systems are in this condition, check in those file
systems to see if there are ways to free up space without adversely
affecting the system.
- Start at the Administration menu, and select Message Networking
Administration > Subscriber Administration >
Subscriber Count.
The system displays the Subscriber Count page.
If the number is close to or exceeds the advertised limit, the
storage space needed to hold the names is probably reducing the
amount of space available for messages.
- From the command prompt, run audit_vname to delete voiced
names that have not been used for a long time from the system.
Take administrative steps to reduce the number of voiced names
on the system. For example, depending on the type of remote machine,
some remote machines can be administered not to send their voiced
names to the Message Networking system.
- The operating system might need to be rebooted, because an operating
system limitation was exceeded. Follow normal procedures for stopping
the voice system and then rebooting the machine.
Alarm Code: 8
Event ID: MIMOUT_MSG
Description:
Error Opening Message. During processing of a message, an error
occurred while attempting to read from/write to the disk.
Repair Procedure:
One or more file systems used for messaging might have run out
of space. Determine if the /voice file systems are full. If they
are, there are two likely reasons for this to happen. Take the following
steps to address the possible causes (some of these steps could
require assistance from Avaya remote service center personnel):
- Run dfspace from the command prompt to see if any file
systems are unusually low on or have run out of space.
- If any file systems are in this condition, check in those file
systems to see if there are ways to free up space without adversely
affecting the system.
- Start at the Administration menu, and select Message Networking
Administration > Subscriber Administration >
Subscriber Count.
The system displays the Subscriber Count page.
If the number is close to or exceeds the advertised limit, the
storage space needed to hold the names is probably reducing the
amount of space available for messages.
- From the command prompt, run audit_vname to delete voiced
names that have not been used for a long time from the system.
Take administrative steps to reduce the number of voiced names
in the system.
For example, depending on the type of remote machine, some remote
machines can be administered not to send their voiced names to
the Message Networking system.
- The operating system might need to be rebooted, because an
operating system limitation was exceeded. Follow normal procedures
for stopping the voice system and then rebooting the machine.
Alarm Code: 9
Event ID: OVMOUT_HDR
Description:
ovmoOutMsg::Error Opening [mediaText][RFC_822]. During processing
of a message, an error occurred while attempting to read from/write
to the disk.
Repair Procedure:
One or more file systems used for messaging could have run out
of space. Determine if the /voice file systems are full. If they
are, there are two likely reasons for this to happen. Take the following
steps to address the possible causes(some of these steps could require
assistance from Avaya remote service center personnel):
- Run dfspace from the command prompt to see if any file
systems are unusually low on or have run out of space.
- If any file systems are in this condition, check in those file
systems to see if there are ways to free up space without adversely
affecting the system.
- Start at the Administration menu, and select Message Networking
Administration > Subscriber Administration >
Subscriber Count.
The system displays the Subscriber Count page.
If the number is close to or exceeds the advertised limit, the
storage space needed to hold the names is probably reducing the
amount of space available for messages.
- From the command prompt, run audit_vname to delete voiced
names that have not been used for a long time from the system.
Take administrative steps to reduce the number of voiced names
in the system.
For example, depending on the type of remote machine, some remote
machines can be administered not to send their voiced names to
the Message Networking system.
- The operating system might need to be rebooted, because an
operating system limitation was exceeded. Follow normal procedures
for stopping the voice system and then rebooting the machine.
Alarm Code: 10
Event ID: VPIMS_SIG
Description:
signal (<signal type>) failed. An error occurred during initialization
of one of the processes used for the VPIM protocol.
Repair Procedure:
- This is an internal software error. Escalate this problem to
Tier 4 during normal business hours, unless conditions indicate
the need for an immediate resolution.
Alarm Code: 11
Event ID: REC_PSTMSTR
Description:
Receipt of a postmaster@domain message. A message has been delivered
to the postmaster mailbox of the Message Networking system.
Repair Procedure:
To view the message, do the following:
- Start at the Administration menu, and select Message Networking
Administration > Remote Machine Administration >
Display postmaster@domain.
The system displays the message.
- Review the delivered message.
Alarm Code: 12
Event ID: SMPT_ERR
Description:
An error occurred during the communication with the remote machine.
The error was likely caused by an incompatibility in the message
transmission protocol.
Repair Procedure:
- Make sure the remote machine has been certified by Avaya to
be compatible with the Message Networking system. If it has not
been certified, differences in the transmission protocol could
prevent proper communication with the remote machine.
Alarm Code: 13
Event ID: CONN_ERR
Description:
Unable to connect to <machine> ...The Message Networking
system was unable to connect to the remote machine, <machine>,
as part of a message delivery.
Repair Procedure:
- This problem could result from any of the following causes:
Some of these steps could require assistance from Avaya remote
service center personnel.
- The remote machine might not be accepting connections. Verify
that the remote machine is in its normal run state. Make sure
all of its processes are running normally. Determine if unusually
heavy traffic on the remote machine could be preventing the machine
from accepting connections.
- The remote machine might not be communicating with the network.
Make sure the remote machine is connected to the network. Also
make sure the network hardware on the remote machine is running
properly.
- The Message Networking system might not be communicating with
the network. Make sure the Message Networking system is connected
to the network. Also, make sure the network hardware on the Message
Networking system is working properly.
- There could be an administration problem. Make sure the administration
information for the remote machine is entered properly in the
Message Networking administration screens. Also ensure that the
Message Networking system is properly administered in the remote
machine.
- Network problems could be interfering with communication. Determine
if any network problems are occurring.
Alarm Code: 14
Event ID: RMT_DISC_FULL
Description:
<machine> disk full. During a message delivery attempt the
remote machine, <machine>, indicated that it had a full disk.
Repair Procedure:
- Reduce the amount of disk space that is in use on the remote
machine.
Alarm Code: 15
Event ID: SMTP_TIMEOUT
Description:
<machine> : Protocol time out. Communication with the remote
machine was interrupted, because the remote machine did not send
a response when one was expected.
Repair Procedure:
This problem could be the result of any of the following causes
(some of these steps could require assistance from Avaya remote
service center personnel):
- The remote machine might not be communicating with the network.
Verify that the remote machine is in its normal run state. Make
sure all of its processes are running normally. Determine if unusually
heavy traffic on the remote machine could be preventing the machine
from communicating in a normal fashion. Make sure that the remote
machine is still connected to the network. Verify that the network
hardware on the remote machine is running properly.
- The Message Networking system might not be communicating with
the network. Make sure the Message Networking system is still
connected to the network. Verify that the network hardware on
the Message Networking system is working properly.
- Network problems could be interfering with communication. Determine
if any network problems are occurring.
- The remote machine might not be compatible with the Message
Networking system. Make sure the remote machine has been certified
by Avaya to be compatible with the Message Networking system.
Alarm Code: 16
Event ID: VPIMS_LOGON
Description:
An unknown system (<machine>) tried to log on. The remote
machine, <machine>, attempted to communicate with the Message
Networking system. However, the remote machine's name is not
in the Message Networking system's database.
Repair Procedure:
- On the Message Networking system, add an entry for the remote
machine using the Message Networking administration pages.
- If the machine that tried to log on is not a legitimate voice
messaging machine, this alarm could also indicate that an unauthorized
machine is attempting to gain improper access to the Message Networking
system.
Alarm Code: 17
Event ID: MSG_TOO_LONG
Description:
Message Too Large: from <sender>. During transmission of
a message to a remote machine, the remote machine indicated that
the message was too long.
Repair Procedure:
- Determine if the remote machine is low on disk space. If it
is low on disk space, take steps to make more disk space available.
- If the remote machine has adequate disk space, determine if
the remote machine has a restriction on message size. If it does
and the value can be changed, increase the value.
Alarm Code: 18
Event ID: NO_IC_DOMAIN
Description:
Local hub domain name not found. No domain name is defined for
the Message Networking system.
Repair Procedure:
- Set the domain name for the Message Networking system on the
General Parameters page. To access the General Parameters page,
from the main menu, select Message Networking Administration
> System Parameters > General Parameters.
Alarm Code: 19
Event ID: SMTP_RPLY
Description:
Error generating SMTP reply; Reply code = <reply code> and
state = <state> do not correspond. An error occurred during
the communication with a remote machine. The error was likely caused
by an incompatibility in the message transmission protocol.
Repair Procedure:
- Make sure the remote machine has been certified by Avaya to
be compatible with the Message Networking system. If it has not
been certified, differences in the transmission protocol could
prevent proper communication with the remote machine.
Alarm Code 20
Event ID: VP_ERROR
Description:
An unexpected error occurred.
Repair Procedure:
- This is an internal software error. Escalate this problem to
Tier 4 during normal business hours, unless conditions indicate
the need for an immediate resolution.
Alarm Code: 21
Event ID: VP_WARNING
Description:
An unexpected error occurred.
Repair Procedure:
- This is an internal software error. Escalate this problem to
Tier 4 during normal business hours, unless conditions indicate
the need for an immediate resolution.
Alarm Code: 22
Event ID: REM_DISC
Alarm Level: N/A (only visible in the Administrator's Log)
Description:
Remote machine disconnected <machine>. The remote machine,
<machine>, unexpectedly disconnected from the Message Networking
system.
Repair Procedure:
This problem might be temporary and require no action. However,
if the problem persists, it could be the result of any of the following
causes (some of these steps could require assistance from Avaya
remote service center personnel):
- The remote machine might not be communicating with the network.
Verify that the remote machine is in its normal run state. Make
sure all of its processes are running normally. Determine if unusually
heavy traffic on the remote machine could be preventing the machine
from communicating in a normal fashion. Make sure the remote machine
is still connected to the network. Verify that the network hardware
on the remote machine is running properly.
- The Message Networking system might not be communicating with
the network. Make sure the Message Networking system is still
connected to the network.
- Network problems could be interfering with communication. Determine
if any network problems are occurring.
- The remote machine might not be compatible with the Message
Networking system. Make sure the remote machine has been certified
by Avaya to be compatible with the Message Networking system.
Alarm Code: 23
Event ID: NO_MBOX
Description:
Mailbox does not exist <machine> <mailbox>. A message
was sent to a mailbox (<mailbox>) on the remote machine <machine>,
and the mailbox does not exist.
Repair Procedure:
- If the mailbox does not exist, notify senders of messages to
that mailbox that the mailbox is nonexistent.
- If the mailbox does exist, make sure that it is administered
properly on the remote machine to accept incoming messages from
an external system (like the Message Networking system).
Alarm Code: 24
Event ID: COMP_UNSUP
Description:
Mailbox not fax/text/binary capable <machine> <mailbox>.
A message containing multimedia message components (for example,
fax and/or text and/or binary attachments) was sent to a mailbox
<mailbox> on the remote machine <machine>, and that
machine cannot accept one or more of the types of components that
was sent.
Repair Procedure:
- If the remote machine cannot support all the types of message
components that were sent, notify senders to that remote machine
of the inability of the machine to accept specific components.
- If the remote machine can support all the types of message components
that were sent, modify the administration of the mailbox on the
remote machine to accept the types of components that were sent.
Alarm Code: 25
Event ID: NOAUTH_SND
Description:
Sender is not authorized <machine> <sender> <mailbox>.
The remote machine, <machine>, refused to deliver a message
to a mailbox, because the sender did not have proper authorization.
Repair Procedure:
- Update the security information for the mailbox on the remote
end node to allow messages to be delivered.
Alarm Code: 26
Event ID: PRIV_UNSUP
Description:
Mailbox not private capable <machine>. A private message
could not be delivered to the remote machine, because handling of
private messages is not supported.
Repair Procedure:
- If possible, change administration in the remote machine, either
at a system level or at a mailbox level, to accept private messages.
Alarm Code: 27
Event ID: NO_MSG_3
Description:
Zero messages received this call <machine>. The remote machine,
<machine>, has established a connection to the Message Networking
system three separate times but has transmitted no message.
Repair Procedure:
- This behavior could indicate a problem with the remote machine.
Verify that the remote machine is operating normally. Also determine
if there is a message on the remote machine's queue that might
have no message contents.
- This alarm could also indicate that an unauthorized machine
is attempting to masquerade as a legitimate voice messaging machine
to gain improper access to the Message Networking system.
Alarm Code: 30
Event ID: NO_MORE_SEED
Description:
If your Message Networking system has a default SMTP/MIME remote
machine to handle SMTP messages from remote machines not administered
on Message Networking, the SMTP/MIME Auto-Assign Mailbox ID field
on the General Parameters page is used to determine the starting
number to generate network addresses for unknown message senders.
Each time a network address is automatically assigned, this field
is incremented. If the SMTP/MIME Auto-Assign Mailbox ID field reaches
the highest network address allowed in the default SMTP remote machine's
dial plan, this field becomes unavailable.
Repair Procedure:
- If this problem occurs, you must modify
the dial plan for the default SMTP remote machine and then
enter a new value for this field that is within the modified dial
plan range.
Top of page
|
