While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing,
Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document
without the obligation to notify any person or organization of such changes.
Documentation disclaimer
Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation
unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya,
Avaya’s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with,
subsequent modifications, additions or deletions to this documentation, to the extent made by End User.
Link disclaimer
Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by
Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not
necessarily endorse the products, services, or information described or o ffered within them. Avaya does not guarantee that these links will
work all the time and has no control over the availability of the linked pages.
Warranty
Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In
addition, Avaya’s standard warranty language, as well as information regarding support for this product, while under warranty, is
available to Avaya customers and other parties through the Avaya Support Web site: http://www.avaya.com/support
Please note that if you acquired the product from an authorized reseller, the warranty is provided to you by said reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/
ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM
AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A
COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO
BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE
OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE
RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A
LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU,
ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE
SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THESE
TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE ("AVAYA").
Copyright
Except where expressly stated otherwise, no use should be made of the Documentation(s) and Product(s) provided by Avaya. All content
in this documentation(s) and the product(s) prov id ed by A vaya including the selection, arrangement and design of the content is owned
either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating
to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any
content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or
use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law.
Third Party Components
Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements
("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party
Terms"). Information regarding distributed Linu x OS sour ce c ode (for those Products that have distributed the Linux OS source code),
and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the
Avaya Support Web site: http://support.avaya.com/Copyright.
Trademarks
The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior
written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and
product(s) should be construed as granting, by implication, estoppel, or other wise, any license or right in and to the Marks without the
express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-Avaya
trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support. Web site: http://www.avaya.com/support
Contact Avaya Support
Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone
number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://
This manual is a reference for the system alarm messages generated by the Avaya
Media Processing Server (Avaya MPS) Series.
Intended Audience
This reference manual is directed toward advanced users of the Avaya MPS Series. To
use the information in this manual effectively, you should have a good understanding
of the Avaya MPS Series software architecture, hardware architecture, and the base
operating system of your particular Avaya MPS (i.e., Solaris or Win32). You should be
experienced and comfortable working in a command line environment.
How to Use This Manual
This manual uses many standard terms relating to computer system and software
application functions. However, it contains some terminology that can only be
explained in the context of the Avaya MPS system. Refer to the Glossary of Avaya MPS Terminology for definitions of Avaya MPS specific terms.
Initially, you should start reading with Introduction to Avaya MPS Alarms on page
22. This chapter provides an overview of the Avaya MPS system alarm facility and
explains how to use the alarm message reference pages in this manual. Each of the
subsequent chapters contains alarm message reference pages for a particular process
or task. Within each chapter, alarm message reference pages appear in numerical order
by alarm number.
If you are reading this document online, use the cross-reference links (shown in blue)
to quickly locate related topics. <L
with your cursor over the cross-reference link. Click on any point in a Table of
Contents entry to move to that topic. Click on the page number of any Index entry to
access that topic page.
To familiarize yourself with various specialized textual references within the manual,
see Conventions Used in This Manual on page 17.
Periphonics is now part of Avaya. The name Periphonics, and variations thereof,
appear in this manual only where it is referred to in a product. (For examples, a
PeriProducer application, the PERImps package, the perirev command, etc.)
EFT> click once with your mouse while positioned
GeoTel Features User ManualPreface
Organization of This Manual
The following chapters comprise this reference manual:
Chapter 1— Introduction
Describes how system alarms are generated, the basic alarm message components, and
how to use the information for the documented alarm messages.
Lists TMS Configuration and Alarm Daemon (TCAD) alarms.
Chapter 10 — TMSCFG Alarms
Lists TMS Configuration (TMSCFG) process alarms.
Chapter 11 — TRIP Alarms
Lists TMS Routing Interface Process (TRIP) alarms.
P0602482 Ver. 04.03AvayaPage 15
Chapter 12 — VAMP Alarms
Lists VAMP alarms.
Chapter 13 — VENGINE Alarms
Lists VENGINE alarms.
Chapter 14 — VMM Alarms
Lists Voice Memory Manager (VMM) alarms.
Chapter 15 — VSTAT Alarms
Lists Voice Statistics (VSTAT) process alarms.
Chapter 16 — VXMLI Alarms
Lists VoiceXML Interpreter (VXMLI) process alarms.
Appendix A — NCD Alarm Messages
Lists possible output for NCD alarm 10004 and diagnostic actions.
Appendix B — TCAD Alarm Messages
Lists possible output for TCAD alarm 11000 and diagnostic actions.
GeoTel Features User ManualPreface
Conventions Used in This Manual
This manual uses different fonts and symbols to differentiate between document
elements and types of information. These conventions are summarized in the
following table.
Conventions Used in This Manual Sheet 1 of 2
NotationDescription
Normal text
important term
system
command
command,
condition, and
alarm
file name /
directory
on-screen field
<KEY NAME>
Book Reference
Normal text font is used for most of the document.
The Italics font is used to introduce new terms, to highlight
meaningful words or phrases, or to distinguish specific terms from
nearby text.
This font indicates a system command and/or its arguments. Such
keywords are to be entered exactly as shown (i.e., users are not to
fill in their own values).
Command, Condition and Alarm references appear on the screen
in magenta text and reference the Command Reference Manual,
the Condition Reference Manual, or the Alarm Reference Manual.
Refer to these documents for detailed information about
Commands, Conditions, and Alarms.
This font is used for highlighting the names of disk directories, files,
and extensions for file names. It is also used to show displays on
text-based screens (e.g., to show the contents of a file.)
This font is used for field labels, on-screen menu buttons, and
action buttons.
A term that appears within angled brackets denotes a terminal
keyboard key, a telephone keypad button, or a system mouse
button.
This font indicates the names of other publications referenced
within the document.
cross reference
!
A cross reference or man page reference appears on the screen in
blue text. Click on the cross reference to access the referenced
location. A cross reference that refers to a section name accesses
the first page of that section. Click on the man page reference to
elicit a pop-up window displaying the subject man page.
The Note icon identifies notes, important facts, and other keys to
understanding.
The Caution icon identifies procedures or events that require
special attention. The icon indicates a warning that serious
problems may arise if the stated instructions are improperly
followed.
P0602482 Ver. 04.03AvayaPage 17
Conventions Used in This Manual Sheet 2 of 2
NotationDescription
The flying Window icon identifies procedures or events that apply
to the Windows 2000 operating system only.
The Solaris icon identifies procedures or events that apply to the
Solaris operating system only.
a. Windows 2000 and the flying Window logo are either trademarks or registered
trademarks of the Microsoft Corporation.
b. Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the
United States and other countries.
Solaris and Windows 2000 Conventions
This manual depicts examples (command line syntax, configuration files, and screen
shots) in Solaris format. In certain instances Windows 2000 specific commands,
procedures, or screen shots are shown where required. The following table lists
examples of general operating system conventions to keep in mind when using this
manual with either the Solaris or Windows operating system.
SolarisWindows 2000
Environment$MPSHOME%MPSHOME%
a
b
Paths$MPSHOME/common/etc%MPSHOME%\common\etc
Command<command> &start /b <command>
GeoTel Features User ManualPreface
Trademark Conventions
The following trademark information is presented here and applies throughout for
third party products discussed within this manual. Trademarking information is not
repeated hereafter.
Solaris is a trademark or registered trademark of Sun Microsystems, Inc. in the United
States and other countries.
Microsoft, Windows, Windows 2000, Internet Explorer, and the Flying Windows logo
are either trademarks or registered trademarks of Microsoft Corporation.
Netscape® and Netscape Navigator® are registered trademarks of Netscape
Communications Corporation in the United States and other countries. Netscape's
logos and Netscape product and service names are also trademarks of Netscape
Communications Corporation, which may be registered in other countries.
P0602482 Ver. 04.03AvayaPage 19
This page has been intentionally left blank.
Introduction
This chapter covers:
1. Introduction to Avaya MPS Alarms
2. Alarm Message Format
3. Alarm Reference Format
Introduction to Avaya MPS Alarms
The system alarms feature provides a facility to display various system messages in a
uniform format. The ALARMD process collects alarms from the various processes,
writes them to the alarm logs, and forwards the alarms to any Alarm Viewers
requesting to receive messages.The alarm messages are translated into the standard
format via an alarm database file (alarm.db.pag and alarm.db.dir) which is
located in the $MPSHOME/common/etc directory. This file contains textual and
other data associated with each alarm message in the system.
The alarm logs are located in the directory $MPSHOME/common/log in the format alarm.<component_type>.<component_#>.log, with backup files being
appended with the .bak extension.
Alarms are also assigned a severity level, ranging from 1 (least severe) to 9 (most
severe). Less severe alarms may indicate errors which do not have significant impact
on system functioning or indicate normal system events (such as a process going into a
ready state). More severe alarms may indicate critical system failure and require
immediate action to correct the problem.
Use the PeriView Alarm Viewer utility to display logged system alarms and to create
filters to selectively allow/ignore certain alarms to be displayed/logged. Refer to the
PeriView Reference Manual for more information on using the Alarm Viewer and for
alarm filtering.
Use the merge utility to merge alarm logs into a single output (typically a separate
file). merge automatically outputs the alarms according to their chronological order
in their source log files. Refer to the Command Reference Manual for more
information.
Use the genalm utility to generate alarms from the command line. genalm can also
display alarms to the standard output (STDOUT). Refer to the Command Reference Manual for more information.
Alarm Message Format
Alarms are organized numerically within a software process name. The source of this
alarm information is the individual alarm database records. Alarms are displayed by
the PeriView Alarm Viewer. They are displayed in the format:
The name of the process which generated the alarm.
comp_name
GeoTel Features User ManualIntroduction
The name of the component from which the alarm was generated.
alm_code
The alarm code/number. The alarm code can potentially be any value that is
represented by an int variable. However, the current conventions use only a 5digit alarm code that indicates the category of the alarm. The major alarm
categories, which determine the first digit of the alarm code, are as follows:
00000 - 09999 ALMGENERIC Reserved for generic system alarms.
10000 - 19999 ALMPROCESS Process-specific alarms.
20000 - 29999 ALMLINE Line command alarms.
30000 - 39999 <none> Device status alarms.
40000 - 49999 <none> Data message content alarms.
50000 - 89999 <none> Reserved for future use.
90000 - 99999 ALMUSER User Alarms.
Within the above major categories, except for the User Alarms, there are the
following subcategories:
For alert or error type messages:
0000 - 0999 ALMINFO Problem detected.
1000 - 1999 ALMCMD Incorrect command or message received.
2000 - 2999 ALMSTATUS Unexpected command or message.
3000 - 3999 ALMDATA Unsolicited command or message.
4000 - 4999 <none> Aborted process command or message.
For information-type messages:
5000 - 5999 <none> Received command or message.
6000 - 6999 <none> Debug check performed.
7000 - 9999 <none> Reserved for future use.
P0602482 Ver. 04.03AvayaPage 23
host_num
The host number which generated the alarm. This is only valid if the Alarm
Viewer is set to monitor external Avaya MPS systems. An asterisk (*) in this
field indicates alarms generated by a local process/component.
phone_line
The phone line which is associated with the generated alarm. An asterisk (*)
in this field indicates alarms which are not associated with an individual line.
date_time
The date and time the alarm was generated.
severity
The severity of the alarm. Severity 1 alarms are either minor errors (which
generally do not affect system function) or information messages. Severity 9
alarms indicate major system failure.
message
A text message indicating the cause for the alarm.
GeoTel Features User ManualIntroduction
Alarm Reference Format
The alarm reference pages in this manual are presented using the format and
conventions described below. The presentation is based on traditional reference
command manual (man) pages.
<task> <alarm_#>
Each reference page starts with a primary heading listing the task and the alarm
number. The subheadings of the alarm reference page are described below.
MESSAGE
The alarm text message as appears in the alarm log file/alarm viewer
SEVERITY
The alarm severity. This can be from 1 (information or low priority) to 9 (very high
priority).
PROBABLE CAUSE
The possible reason(s) why the alarm was produced. Some alarms are produced only
under specific circumstances and may have only one cause. Others can be produced
under multiple circumstances. Some alarms use variable text fields to display further
information about the condition which caused the alarm.
The cause can be better determined by noting the system state when the alarm
occurred. For example, if the alarm was generated during system startup, it is likely to
be a system configuration problem.
Note that not all alarm error messages indicate failure of the Avaya MPS. There may
be external causes (such as an external database/host going down).
ACTION
The steps to take to correct any error condition. For many severity 1 (information)
alarms, there are no actions because the alarm is the result of normal system operation.
Error message alarms may require changing system configuration parameters,
modifying applications, or pilfering some sort of system maintenance (e.g., moving
messages from a full Caller Message Recording file to a different file or media).
For alarms with multiple causes, each cause will usually have an associated action.
Some error conditions caused by external factors cannot be fixed by doing anything on
the Avaya MPS. You may need to involve others.
There are many alarm messages which should never occur except with major system
failure. These severe alarms indicate conditions which can only be analyzed and
remedied by Avaya Technical Support.
P0602482 Ver. 04.03AvayaPage 25
EXAMPLES
One or more examples of the alarm’s output may be presented. If no examples are
provided, this heading is omitted.
NOTES
Additional information not discussed elsewhere in this reference page. If there is none,
this heading is omitted.
CCM Alarms
This chapter covers:
1. CCM Alarms
CCM 11000
CCM 11001
MESSAGE
Service parameter [<parameter name>] does not exist.
SEVERITY
4
PROBABLE CAUSE
The parameter was misspelled or there was a typo.
ACTION
Check and fix spelling of the service parameter.
MESSAGE
Failed to configure service param [<parameter name>] to
value [<parameter value>]. Error in parsing value.
CCM 11002
SEVERITY
4
PROBABLE CAUSE
The value given is of the wrong type. For example a parameter requires a time value
(numeric) but the value provided was "ON" (string).
ACTION
Check and fix the value that this parameter is being set to.
MESSAGE
Failed to configure service parameter [<parameter name>] to
value [<parameter value>]. Out of range [<the allowable range of values>].
SEVERITY
4
GeoTel Features User ManualCCM Alarms
PROBABLE CAUSE
The value given is out of range. For example the parameter takes a time for its value
with a range of 2s-500s and the value provided is 1s.
ACTION
Check and fix the value that this parameter is being set to.
CCM 11003
MESSAGE
Failed to execute console opt [<the console option>] invalid
format (see CCM help for this option)
SEVERITY
4
CCM 11004
PROBABLE CAUSE
The wrong format/syntax was used for this console option in CCM's configuration
file. For example, setsvcparam first 10s is syntactically incorrect. The
correct syntax is, setsvcparam first=10s.
ACTION
Check CCM's configuration file and fix the syntax that is being used for
[<the console option>].
NOTES
CCM's configuration file is located in $MPSHOME/mpsN/etc. Phone line CCM's
use "ccm_phoneline.cfg" and administrative CCM's use "ccm_admin.cfg".
MESSAGE
WARNING failed to process configuration file "<file name>"
reason [<reason code>:<reason string>].
SEVERITY
4
PROBABLE CAUSE
Configuration file may be corrupt or there is a communication problem between CCM
and CONFIGD/TMS. The configuration process may have timed out on a response
P0602482 Ver. 04.03AvayaPage 29
CCM 12000
from CCM causing it to terminate processing of the configuration file.
ACTION
Verify that the configuration file is present and correct.
Possible hardware/software problem. CCM may not respond in a timely manner to the
configuration process if the hardware (TMS, hard disk, etc) does not respond in a
timely manner to a request. Also check CPU utilization to ensure that the CPU is not
overloaded during this time.
NOTES
CCM's configuration file is located in $MPSHOME/mpsN/etc. Phone line CCM's
use "ccm_phoneline.cfg" and administrative CCM's use "ccm_admin.cfg".
MESSAGE
TMS [<resource name>] resource is not available.
SEVERITY
9
PROBABLE CAUSE
The resource was not loaded in TMS, the resource is not part of the RSET profile, or
the pool of resources was depleted.
ACTION
•The resource was not loaded in TMS.
Verify that the resource is properly configured using the Avaya MPS
configuration utility.
Verify that enough licenses exist for the number of resources desired.
•The resource is not part of the RSET profile.
If the resource is "dtmf" verify that the resource is in the RSET profile for the
line. Use the Avaya MPS configuration utility to verify that a dtmf resource is
in the RSET profile of all lines that will need access to a dtmf receiver (dtmf
resources are not shareable).
•The pool of resources was depleted.
Check for resource leaks in CCM/TMS.
Increase the number of resources of this type that are available to the Avaya
MPS.
Loading...
+ 422 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.