Avaya Media Processing Server Series Alarm Reference Manual (Software Release 2.1) Uživatelský manuál

Avaya Business Communications ManagerRelease 6.0Document Status: StandardDocument Number: P0602478Document Version: 04.03Date: June 2010Avaya Media Pr

VENGINE 26008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321VENGINE 26009 . . . . . . . . . . . . . . . . . . . . . . . .

CONFMGMT 11000MESSAGEFailed to create conference [ conference name ]. SEVERITY4PROBABLE CAUSEThe system does not have enough conference resources conf

GeoTel Features User Manual CONFMGMT AlarmsP0602482 Ver. 04.03 Avaya Page 101CONFMGMT 11001MESSAGEFailed to create port for conference [ conference na

CONFMGMT 11002MESSAGEFailed to create bridge for conference [<conference name>]. SEVERITY4PROBABLE CAUSE1. The Network Interface Controller (NIC

GeoTel Features User Manual CONFMGMT AlarmsP0602482 Ver. 04.03 Avaya Page 103CONFMGMT 11003MESSAGEFailed to destroy conference [ conference name ]. SE

CONFMGMT 11004MESSAGE Failed to destroy port for conference [ conference name ]. SEVERITY4PROBABLE CAUSEThere is a potentially serious software/hardwa

GeoTel Features User Manual CONFMGMT AlarmsP0602482 Ver. 04.03 Avaya Page 105CONFMGMT 11005MESSAGEFailed to destroy bridge for conference [ conference

This page has been intentionally left blank.

This chapter covers:FAXMGR Alarms1. Fax Manager Alarms

FAXMGR 11000MESSAGEFailed to process configuration file. SEVERITY4PROBABLE CAUSE• Configuration file does not exist or is corrupt.• Failed to process

This chapter covers:NCD Alarms1. NCD Alarms

GeoTel Features User ManualP0602482 Ver. 04.03 Avaya Page 11VENGINE 28027 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367V

NCD 10001MESSAGE<message> SEVERITY1POSSIBLE CAUSEThis is an information display alarm. A typical message is "NCD entering ready state"

GeoTel Features User Manual NCD AlarmsP0602482 Ver. 04.03 Avaya Page 111NCD 10004MESSAGE<message> SEVERITY4POSSIBLE CAUSEDependent on message di

NCD 10005MESSAGE<message> SEVERITY1PROBABLE CAUSEThere was a normal system event in the TMS or NIC hardware.ACTIONMost normal TMS/NIC system eve

GeoTel Features User Manual NCD AlarmsP0602482 Ver. 04.03 Avaya Page 113NCD 10006MESSAGEMemory Allocation Failure. Cannot Proceed.SEVERITY9PROBABLE CA

NCD 10007MESSAGESystem has no network timing reference. Bridging is not available.SEVERITY9PROBABLE CAUSE• Spans specified in Sync List for Reference

GeoTel Features User Manual NCD AlarmsP0602482 Ver. 04.03 Avaya Page 115NCD 10008MESSAGESystem has network timing reference. Bridging is available.SEV

NCD 10009MESSAGELost network timing for reference source A.SEVERITY4PROBABLE CAUSESpans specified in Sync List for Reference Clock A are out of Servic

GeoTel Features User Manual NCD AlarmsP0602482 Ver. 04.03 Avaya Page 117NCD 10010MESSAGELost network timing for reference source B.SEVERITY4PROBABLE C

NCD 10011MESSAGEUnable to Start Ping Timer. Pinging Disabled.SEVERITY1PROBABLE CAUSE•Network problems.• PERIbrdge packages on the two nodes are differ

GeoTel Features User Manual NCD AlarmsP0602482 Ver. 04.03 Avaya Page 119NCD 10012MESSAGEUnable to reallocate memory. No new connections will be accept

VMM 11001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413VMM 11002 . . . . . . . . . . . . . . . . . . . . . . . .

NCD 10013MESSAGEGained network timing for reference source A/B.SEVERITY1PROBABLE CAUSEThe system has gained network timing for reference source A or B

This chapter covers:RCM Alarms1. RCM Alarms

RCM 20001MESSAGEMemory allocation failure - size=<NUMBER>SEVERITY9PROBABLE CAUSEMemory allocation failed, probably caused by running too many re

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 123RCM 20002MESSAGE'numchannels' configuration error - <REASON>SE

RCM 20003MESSAGEConfiguration error - <REASON>SEVERITY9PROBABLE CAUSELabels are not properly configured. Reasons could be:• Number of labels con

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 125RCM 20004MESSAGEVendor Name configuration error - <REASON>SEVERITY9PROBA

RCM 20005MESSAGEUnknown resource type: type='[<RESOURCE TYPE>]'SEVERITY9PROBABLE CAUSEAn incorrect resource type specified in file rcm

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 127RCM 20006MESSAGECannot open vendor interface library.SEVERITY9PROBABLE CAUSECa

RCM 20007MESSAGELicense failure - <REASON>SEVERITY9PROBABLE CAUSEFailed to obtain license. Reasons could be:• Failed to initialize license clien

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 129RCM 20008MESSAGECADI Initialization failed.SEVERITY9PROBABLE CAUSEFailed to in

This chapter covers:Preface1. How to Use This Manual2. Organization of This Manual3. Conventions Used in This Man-ual4. Solaris and Windows 2000 Conve

RCM 20009MESSAGEUnable to send message: message=’<MESSAGE>’SEVERITY9PROBABLE CAUSEFailed to send a message. Messages could be:• gotres - The &ap

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 131RCM 20010MESSAGEUnable to open ’<FILENAME>’SEVERITY9PROBABLE CAUSEFailed

RCM 20011MESSAGERCM shutting down due to reason (shutdown_code=#) SEVERITY9PROBABLE CAUSERCM has shut down due to the given reason.ACTIONCheck the RCM

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 133RCM 20201MESSAGEInvalid client number - [ID=<NUMBER>], check 'vos.c

RCM 20202MESSAGEEncountered an error parsing AVS stringSEVERITY4PROBABLE CAUSEParsing AVS string failed either in Send Resource or Set Parameter.ACTIO

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 135RCM 20203MESSAGEPooled resource configuration error: <REASON>SEVERITY4PR

RCM 20204MESSAGEResource configuration error - <REASON>SEVERITY4PROBABLE CAUSEA resource configuration error has occurred. The reasons could be:

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 137RCM 20205MESSAGECannot change label - poolname '<POOLNAME>' no

RCM 20206MESSAGEA non-startup options has been issued at startup - option='<OPTION>'SEVERITY4PROBABLE CAUSEThe option specified can on

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 139RCM 20207MESSAGEFailed to process parameter - <REASON>. SEVERITY4PROBABL

Scope This manual is a reference for the system alarm messages generated by the Avaya Media Processing Server (Avaya MPS) Series.Intended Audience Thi

RCM 20208MESSAGEChannel is down (max # of reinits exceeded).SEVERITY4PROBABLE CAUSEChannel is down after maximum number of reinitializations failed.AC

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 141RCM 20209MESSAGESome channels failed to come up. SEVERITY4PROBABLE CAUSENot al

RCM 20401MESSAGEGC Log error - <reason>SEVERITY1PROBABLE CAUSEA Generic Call Logging error has occurred. The displayed reason could be one of th

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 143ACTION1. Verify patch levels on OSCAR (including vendor software) are up-to-da

RCM 20402MESSAGEFile operation error - <REASON>SEVERITY1PROBABLE CAUSEAn error occurred when performing a file operation. Reasons could be:• Una

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 145RCM 21001MESSAGEGCL memory allocation failure - malloc error, turning off Audi

RCM 21201MESSAGEGCL configuration error - <reason> SEVERITY4POSSIBLE CAUSEAn error occurred while configuring Generic Call Logging (from the $OS

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 147RCM 21202MESSAGEGCL parameter error - <reason> SEVERITY4POSSIBLE CAUSEAn

RCM 21203MESSAGEGCL file operation error - <reason> SEVERITY4POSSIBLE CAUSEAn error occurred while operating on GC Log files. The displayed reas

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 149RCM 21204MESSAGEGCL Disk space error - <details> SEVERITY4POSSIBLE CAUSE

GeoTel Features User Manual PrefaceP0602482 Ver. 04.03 Avaya Page 15Organization of This Manual The following chapters comprise this reference manual:

RCM 22001MESSAGEsl> <ERROR MESSAGE>SEVERITY9PROBABLE CAUSEThis is an error alarm generated by the shared library interfacing the vendor softw

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 151RCM 22002MESSAGEsl> <ERROR MESSAGE>SEVERITY9PROBABLE CAUSEThis is an

RCM 22003MESSAGEsl> <ERROR MESSAGE>SEVERITY9PROBABLE CAUSEThis is an error alarm generated by the shared library interfacing the vendor softw

GeoTel Features User Manual RCM AlarmsP0602482 Ver. 04.03 Avaya Page 153RCM 22200MESSAGEsl> <WARNING MESSAGE>SEVERITY4PROBABLE CAUSEThis is a

RCM 22400MESSAGEsl> <INFO MESSAGE>SEVERITY1PROBABLE CAUSEThis is an informational alarm generated by the shared library interfacing the vendo

This chapter covers:SRP Alarms1. SRP Alarms

SRP 1MESSAGEsrp: COMPONENT component UP SEVERITY1POSSIBLE CAUSEThe displayed component is up.ACTIONNone required. This alarm is an information message

GeoTel Features User Manual SRP AlarmsP0602482 Ver. 04.03 Avaya Page 157SRP 12001MESSAGEprocess: DOWN (pid: pid, exit code: exit_code) - restarting S

SRP 12002MESSAGEprocess: DOWN (pid: pid, exit code: exit_code) - no restart SEVERITY9POSSIBLE CAUSEProcess exited abnormally or crashed. SRP will not

GeoTel Features User Manual SRP AlarmsP0602482 Ver. 04.03 Avaya Page 159SRP 12003MESSAGECOMPONENT component STARTUP ABORTED [details] SEVERITY9POSSIBL

Chapter 12 — VAMP AlarmsLists VAMP alarms.Chapter 13 — VENGINE AlarmsLists VENGINE alarms.Chapter 14 — VMM AlarmsLists Voice Memory Manager (VMM) alar

SRP 12004MESSAGEcomponent: test alarm: alarm_text SEVERITY1PROBABLE CAUSEThis is a generic alarm that can be generated by the SRP command srp comp[com

GeoTel Features User Manual SRP AlarmsP0602482 Ver. 04.03 Avaya Page 161SRP 12005MESSAGEsrp: swap space exceeded HWM [hwm%]: capacity at current_capac

SRP 12006MESSAGEsrp: swap space below LWM [lwm%]: capacity at current_capacity% SEVERITY1PROBABLE CAUSESwap space usage fell below the low watermark.

GeoTel Features User Manual SRP AlarmsP0602482 Ver. 04.03 Avaya Page 163SRP 12007MESSAGEsrp: disk space for mount_point exceeded HWM [hwm%]: capacity

SRP 12008MESSAGEsrp: disk space for mount_point below LWM [lwm%]: capacity at current_capacity% SEVERITY1PROBABLE CAUSEDisk space usage fell below the

GeoTel Features User Manual SRP AlarmsP0602482 Ver. 04.03 Avaya Page 165SRP 12009MESSAGEsrp: Ignoring bad line [line#] for COMP [component] [reason] S

SRP 12012MESSAGEsrp: System is up SEVERITY1PROBABLE CAUSESRP has successfully started all configured components. The system is ready to take calls.ACT

GeoTel Features User Manual SRP AlarmsP0602482 Ver. 04.03 Avaya Page 167SRP 12013MESSAGEcomp#<component>: COMPONENT <component> DOWN [<

SRP 12014MESSAGESystem coming down... SEVERITY9PROBABLE CAUSESRP has been killed or encountered a fatal error.ACTIONReview the SRP and alarm logs to d

GeoTel Features User Manual SRP AlarmsP0602482 Ver. 04.03 Avaya Page 169SRP 12020MESSAGEsysmon: cpu usage exceeded HWM [ hwm% ]: usage at current_perc

GeoTel Features User Manual PrefaceP0602482 Ver. 04.03 Avaya Page 17Conventions Used in This Manual This manual uses different fonts and symbols to di

SRP 12021MESSAGEsysmon: cpu usage below LWM [ lwm%]: usage at current_percentage%SEVERITY1PROBABLE CAUSECPU usage has dropped below the low water mark

This chapter covers:TCAD Alarms1. TCAD Alarms

TCAD 10000MESSAGE<message>SEVERITY9PROBABLE CAUSEThere is a problem with the NIC or TMS hardware.ACTIONMost TMS/NIC alarms are sent through TCAD

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 173TCAD 10001MESSAGESystem Set Params failed. status = <status value>SEVER

TCAD 10002MESSAGEDevice Control Signal failed. status =<status value>SEVERITY9PROBABLE CAUSEA D_channel mapping may be incorrect or an ExtInt ma

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 175TCAD 10003MESSAGEBuild Resource Load List failed. status =<status value>

TCAD 10004MESSAGEMaximum Failure Count reached.SEVERITY9PROBABLE CAUSEFailed to load DSP three times, the Maximum Fail Count.ACTION• Selecting the Ava

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 177TCAD 10005MESSAGENo DSPs found for this TMS <TMS number>SEVERITY9PROBAB

TCAD 10006MESSAGETMSNum invalid in <function name>: <TMS number>SEVERITY9PROBABLE CAUSEThe TMS number mapped to the local VPS component nu

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 179TCAD 10007MESSAGEError parsing tms.cfgSEVERITY9PROBABLE CAUSEFailed to parse

Solaris and Windows 2000 Conventions This manual depicts examples (command line syntax, configuration files, and screen shots) in Solaris format. In c

TCAD 10008MESSAGEFailed to open file: <file name>SEVERITY9PROBABLE CAUSEFile <file name> was not found.ACTIONMake sure <file name> e

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 181TCAD 10009MESSAGELicense server is down, standing in demo mode.SEVERITY9PROBA

TCAD 10010MESSAGELicense request denied for <product name>.SEVERITY9PROBABLE CAUSECould not acquire licenses, since no license key for the speci

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 183TCAD 10011MESSAGENo additional license avail for <product name>.SEVERIT

TCAD 10012MESSAGELicensing Error. The system is going to shutdownSEVERITY9PROBABLE CAUSEFailed to reacquire licenses after refresh failure.ACTIONCheck

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 185TCAD 10013MESSAGEMode Create failed. Status=<status value>SEVERITY9PROB

TCAD 10014MESSAGEMode Destroy failed. Status=<status value>SEVERITY9PROBABLE CAUSEFailed to destroy Mode for default parameters specified in tms

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 187TCAD 10015MESSAGENo Configuration for this TMSSEVERITY9PROBABLE CAUSEThere is

TCAD 10016MESSAGEProcess Device List failed. status=<status value>SEVERITY9PROBABLE CAUSEFailed to process the device list response from the TMS

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 189TCAD 10017MESSAGEProcessDeviceList: Message Record Count is zero. Nothing to

GeoTel Features User Manual PrefaceP0602482 Ver. 04.03 Avaya Page 19Trademark Conventions The following trademark information is presented here and ap

TCAD 10018MESSAGERsrc Create Completing for Spans failed. status =<status value>SEVERITY9PROBABLE CAUSEFailed to create resources for spans.ACTI

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 191TCAD 10019MESSAGERsrc Create for Span Loading failed. status =<status valu

TCAD 10020MESSAGEFailed to acquire license after refresh failure.SEVERITY9PROBABLE CAUSECould not reacquire the licenses after refresh failure, probab

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 193TCAD 11000MESSAGE<message> SEVERITY4PROBABLE CAUSEDependent on message

TCAD 11001MESSAGENot enough DSPs to support the configurationSEVERITY4PROBABLE CAUSEThe configuration for DSP in tms.cfg is over configured.ACTIONUsin

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 195TCAD 11002MESSAGEFor <'product name'>, granted <number1>

TCAD 11003MESSAGEInvalid entry found, not found in tms command table:<entry name>SEVERITY4PROBABLE CAUSEThe command in tms.cfg is not in the com

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 197TCAD 11004MESSAGEFailed on attempt to reacquire license. Retry <number>

TCAD 11005MESSAGEDCHANMAP section of tms.cfg maybe incomplete, ...SEVERITY4PROBABLE CAUSEThe configuration for some spans where not assigned a D-Chann

GeoTel Features User Manual TCAD AlarmsP0602482 Ver. 04.03 Avaya Page 199TCAD 12000MESSAGE<message>SEVERITY1PROBABLE CAUSEThere was a normal sys

© 2010 Avaya Inc.All Rights Reserved.NoticesWhile reasonable efforts have been made to ensure that the information in this document is complete and ac

This page has been intentionally left blank.

This page has been intentionally left blank.

This chapter covers:TMSCFG Alarms1. TMSCFG Alarms

TMSCFG 10001MESSAGEtmscfg: Section Error - error_detailscommand SEVERITY9POSSIBLE CAUSEA TMS configuration command (command) was found in a section of

GeoTel Features User Manual TMSCFG AlarmsP0602482 Ver. 04.03 Avaya Page 203TMSCFG 10002MESSAGEtmscfg: Command cmd received N arguments, expected [at

TMSCFG 10010MESSAGEtmscfg: misconfiguration detected: error_details command SEVERITY9POSSIBLE CAUSEA misconfiguration has been found in the $MPSHOME/c

GeoTel Features User Manual TMSCFG AlarmsP0602482 Ver. 04.03 Avaya Page 205Config name already defined The name specified in a CONFIG_NAME command was

LINE command has invalid DTC number The specified TMS number is invalid. Specify a TMS previously defined in a BIND command.LINE command found without

GeoTel Features User Manual TMSCFG AlarmsP0602482 Ver. 04.03 Avaya Page 207Unknown parameter There is an unknown parameter specified in a PARAM comman

This page has been intentionally left blank.

This chapter covers:TRIP Alarms1. TRIP Alarms

This chapter covers:Introduction1. Introduction to Avaya MPS Alarms2. Alarm Message Format3. Alarm Reference Format

TRIP 10001MESSAGEEntering ACTIVE state for <mps component id> SEVERITY1POSSIBLE CAUSESecondary Avaya MPS successfully acquired the TMS and is in

GeoTel Features User Manual TRIP AlarmsP0602482 Ver. 04.03 Avaya Page 211TRIP 10002MESSAGEEntering STANDBY stateSEVERITY1CAUSESecondary Avaya MPS is e

TRIP 10004MESSAGEMissed more than # pings from TMS Chs/Slt chassis / BPS - restarting SEVERITY9POSSIBLE CAUSETRIP is in the ‘controlling’ state and it

This chapter covers:VAMP Alarms1. VAMP Alarms

VAMP 10000MESSAGEFailed to get system configuration information.SEVERITY1PROBABLE CAUSESystem configuration information could not be obtained.ACTIONId

GeoTel Features User Manual VAMP AlarmsP0602482 Ver. 04.03 Avaya Page 215VAMP 10001MESSAGEFailed to enable media event notification.SEVERITY1PROBABLE

This page has been intentionally left blank.

This chapter covers:VENGINE Alarms1. VENGINE Alarms

VENGINE 25000MESSAGE[Para <block_name>/1] Generic vengine error SEVERITY3PROBABLE CAUSEAvaya supplies this alarm to use in user-created CALL fun

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 219VENGINE 25001MESSAGE[Para <block_name>/1>] No data for ACCEPT sta

Introduction to Avaya MPS AlarmsThe system alarms feature provides a facility to display various system messages in a uniform format. The ALARMD proce

VENGINE 25002MESSAGE[Para <block_name>/<1>] Invalid source or target offset <source/offset> SEVERITY3PROBABLE CAUSEThe application u

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 221VENGINE 25003MESSAGE[Para <block_name>/<1>] Item '<ite

VENGINE 25004MESSAGE[Para <block_name>/<1>] Invalid number of elements <#> SEVERITY3PROBABLE CAUSEThe application attempted to execu

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 223VENGINE 25005MESSAGE[Para <block_name>/<1>] Endfile for '

VENGINE 25006MESSAGE[Para <block_name>/1>] Cannot write into file <filename> SEVERITY3PROBABLE CAUSE1. The file ownership/permissions a

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 225VENGINE 25007MESSAGE[Para <block_name>/<1>] Invalid starting p

VENGINE 25008MESSAGE[Para <block_name>/<1>] Source is not integer or length (<length>)>4 SEVERITY3PROBABLE CAUSEThe application a

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 227VENGINE 25009MESSAGE[Para <block_name >/<1>] CALL function is

VENGINE 25010MESSAGE[Para <block_name>/<1>] Cannot create pipe for CALL daemon SEVERITY3PROBABLE CAUSEThere is an error which may indicate

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 229VENGINE 25011MESSAGE[Para <block_name>/<1>] Cannot fork or run

GeoTel Features User Manual IntroductionP0602482 Ver. 04.03 Avaya Page 23The name of the component from which the alarm was generated.alm_codeThe alar

VENGINE 25013MESSAGE[Para <block_name>/<1>] Cannot write or read CALL arguments SEVERITY3PROBABLE CAUSEIf the application references a use

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 231VENGINE 25014MESSAGE[Para <block_name>/<1>] CALL timer expired

VENGINE 25015MESSAGE[Para <block_name>/<1>] Inconsistent function '<function>' return: code <var> with no cond SEVER

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 233VENGINE 25016MESSAGE[Para <block_name>/<1>] Function '<

VENGINE 25017MESSAGE[Para <block_name>/<1>] Non-array item <item> SEVERITY3PROBABLE CAUSEThe application attempted an array-qsort ca

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 235VENGINE 25018MESSAGE[Para <block_name>/<1>] Invalid number of

VENGINE 25019MESSAGE[Para <block_name>/<1>] Invalid number of split keys (max 8) SEVERITY3PROBABLE CAUSEThere are too many split keys spec

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 237VENGINE 25020MESSAGE[Para <block_name>/<1>] Invalid sorting ke

VENGINE 25021MESSAGE[Para <block_name>/<1>] Dataset '<name>' was not read for UPDATE SEVERITY3PROBABLE CAUSEThe applicatio

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 239VENGINE 25022MESSAGE[Para <block_name>/<1>] Invalid key for da

host_numThe host number which generated the alarm. This is only valid if the Alarm Viewer is set to monitor external Avaya MPS systems. An asterisk (*

VENGINE 25023MESSAGE[Para <block_name>/<1>] Record from dataset '<name>' (reclen <length>) was truncated to <#>

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 241VENGINE 25024MESSAGE[Para <block_name>/<1>] For dataset '

VENGINE 25025MESSAGE[Para <block_name>/<1>] Browse (REQID '<id>') for dataset '<name>' exists SEVERITY3PRO

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 243VENGINE 25026MESSAGE[Para <block_name>/<1>] Browse (REQID &apo

VENGINE 25027MESSAGE[Para <block_name>/<1>] READPREV was requested for HSAM dataset '<name>' SEVERITY3PROBABLE CAUSEThe ap

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 245VENGINE 25028MESSAGE[Para <block_name>/<1>] Invalid dataset na

VENGINE 25029MESSAGE[Para <block_name>/<1>] Cannot read dataset '<name>' header SEVERITY3PROBABLE CAUSE1. The file ownersh

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 247VENGINE 25030MESSAGE[Para <block_name>/<1>] Invalid flags for

VENGINE 25031MESSAGE[Para <block_name>/<1>] RIDFLD length <length> less than KEYLENGTH <length2> fordataset '<name>

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 249VENGINE 25032MESSAGE[Para <block_name>/<1>] Invalid key length

GeoTel Features User Manual IntroductionP0602482 Ver. 04.03 Avaya Page 25Alarm Reference FormatThe alarm reference pages in this manual are presented

VENGINE 25033MESSAGE[Para <block_name>/<1>] Cannot open dataset '<name>'. Data base is empty or locked SEVERITY3PROBABLE C

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 251VENGINE 25034MESSAGE[Para <block_name>/<1>] Dataset '<

VENGINE 25035MESSAGE[Para <block_name>/<1>] Invalid record of dataset '<name>' in DB master file SEVERITY3PROBABLE CAUSETh

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 253VENGINE 25036MESSAGE[Para <block_name>/<1>] Item <name>

VENGINE 25037MESSAGE[Para <block_name>/<1>] SET variable <name> is not from Linkage Section SEVERITY3PROBABLE CAUSEThe application a

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 255VENGINE 25038MESSAGE[Para <block_name>/<1>] POST timer expired

VENGINE 25039MESSAGE[Para <block_name>/<1>] Vastimer is not running (or msg queue full) SEVERITY3PROBABLE CAUSE1. The $ASEHOME environment

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 257VENGINE 25040MESSAGE[Para <block_name>/<1>] No room in SM to s

VENGINE 25041MESSAGE[Para <block_name>/<1>] Cannot move char '<character>' according to PIC '<descriptor>'

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 259VENGINE 25042MESSAGE[Para <block_name>/<1>] Internal error. Ra

EXAMPLESOne or more examples of the alarm’s output may be presented. If no examples are provided, this heading is omitted.NOTESAdditional information

VENGINE 25043MESSAGE[Para <block_name>/<1>] Invalid option '<option>' or process '<processname>' SEVERITY3

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 261VENGINE 25044MESSAGE[Para <block_name>/<1>] Option '<n

VENGINE 25046MESSAGE[Para <block_name>/<1>] Vengine option <option_name>not implemented SEVERITY3PROBABLE CAUSEAn invalid option was

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 263VENGINE 25047MESSAGE[Para <block_name>/<1>] Internal error. Co

VENGINE 25049MESSAGE[Para <block_name>/<1>] Internal error. Dataset map lost (nrec #<#> map <var> mapoffset <offset> nre

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 265VENGINE 25050MESSAGE[Para <block_name>/<1>] No space left in d

VENGINE 25051MESSAGE[Para <block_name>/<1>] Unimplemented COMPUTE OP <option> SEVERITY3PROBABLE CAUSEThere is an error which may ind

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 267VENGINE 25052MESSAGE[Para <block_name>/<1>] LINK program &apos

VENGINE 25053MESSAGE[Para <block_name>/<1>] Cannot find <#>-th argument for '<application>' SEVERITY3PROBABLE CAUSET

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 269VENGINE 25054MESSAGE[Para <block_name>/<1>] Argument list mism

This chapter covers:CCM Alarms1. CCM Alarms

VENGINE 25055MESSAGE[Para <block_name>/<1>] Argument '<name>' (group item or array) does not match <nameusing> SEVER

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 271VENGINE 25056MESSAGE[Para <block_name>/<1>] Literal '<

VENGINE 25057MESSAGE[Para <block_name>/<1>] Subitems passed (argument <name>) do not match <usingname> SEVERITY3PROBABLE CAUSE

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 273VENGINE 25058MESSAGE[Para <block_name>/<1>] Item <argname&g

VENGINE 25059MESSAGE[Para <block_name>/<1>] Infinite loop, starting from the paragraph <name> SEVERITY3PROBABLE CAUSEVENGINE detecte

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 275VENGINE 25060MESSAGE[Para <block_name>/<1>] Too many (<#>

VENGINE 25061MESSAGE[Para <block_name>/<1>] Unimplemented OP <option> SEVERITY3PROBABLE CAUSEThere is an error which may indicate a

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 277VENGINE 25062MESSAGE[Para <block_name>/<1>] Subscript value &l

VENGINE 25063MESSAGE[Para <block_name>/<1>] Cannot index nonarray item <item_name> SEVERITY3PROBABLE CAUSEThe application specified

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 279VENGINE 25065MESSAGE[Para <block_name>/<1>] No data in '&

CCM 11000MESSAGEService parameter [<parameter name>] does not exist.SEVERITY4PROBABLE CAUSEThe parameter was misspelled or there was a typo.ACTI

VENGINE 25066MESSAGE[Para <block_name>/<1>] Unknown management request '<request>' SEVERITY3PROBABLE CAUSEThe amu request

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 281VENGINE 25067MESSAGE[Para <block_name>/<1>] Not implemented op

VENGINE 25068MESSAGE[Para <block_name>/<1>] Cannot get lib name for LOCATION management request SEVERITY3PROBABLE CAUSEThe amu request is

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 283VENGINE 25069MESSAGE[Para <block_name>/<1>] Cannot detach path

VENGINE 25070MESSAGE[Para <block_name>/<1>] Cannot attach path (library) '<library_name>' SEVERITY3PROBABLE CAUSEThe amu r

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 285VENGINE 25071MESSAGE[Para <block_name>/<1>] Undefined file nam

VENGINE 25072MESSAGE[Para <block_name>/<1>] Invalid port in VAG management request SEVERITY3PROBABLE CAUSEThere is an error which may indi

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 287VENGINE 25074MESSAGE[Para <block_name>/<1>] Cannot move <ty

VENGINE 25076MESSAGE[Para <block_name>/<1>] Internal error. NULL Symbol pointer to move SEVERITY3PROBABLE CAUSEThere is an error which may

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 289VENGINE 25077MESSAGEInvalid range [1, <limit>] for random number SEV

GeoTel Features User Manual CCM AlarmsP0602482 Ver. 04.03 Avaya Page 29PROBABLE CAUSEThe value given is out of range. For example the parameter takes

VENGINE 25078MESSAGE[Para <block_name>/<1>] <alarm_text> SEVERITY3PROBABLE CAUSEThe alarm text displayed can be:Invalid MMF name &l

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 291VENGINE 25079MESSAGE[Para <block_name>/<1>] Pipe to CALLdaemon

VENGINE 25080MESSAGE[Para <block_name>/<1>] Reclength was not specified for <itemname> SEVERITY3PROBABLE CAUSEThere is an error whic

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 293VENGINE 25081MESSAGE[Para <block_name>/<1>] Confidence was not

VENGINE 25082MESSAGE[Para <block_name>/<1>] Cannot check length < 2 SEVERITY3PROBABLE CAUSEThe length parameter specified for a [double

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 295VENGINE 25083MESSAGE[Para <block_name>/<1>] Cannot get vms bou

VENGINE 25084MESSAGE[Para <block_name>/<1>] Invalid InitValue structure or attempt to init const '<itemname>' SEVERITY3PRO

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 297VENGINE 25085MESSAGE[Para <block_name>/<1>] Cannot get <mas

VENGINE 25086MESSAGE[Para <block_name>/<1>] Cannot read master SM segment information SEVERITY3PROBABLE CAUSE1. The file permission/owners

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 299VENGINE 25087MESSAGE[Para <block_name>/<1>] Cannot attach/deta

GeoTel Features User ManualP0602482 Ver. 04.03 Avaya Page 3Table of ContentsPreface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

from CCM causing it to terminate processing of the configuration file.ACTIONVerify that the configuration file is present and correct.Possible hardwar

VENGINE 25088MESSAGE[Para <block_name>/<1>] Cannot remove <master> segment, ID <segid> SEVERITY3PROBABLE CAUSE1. The file perm

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 301VENGINE 25089MESSAGE[Para <block_name>/<1>] No room in SM uppe

VENGINE 25090MESSAGE[Para <block_name>/<1>] Cannot create SM segment for item <itemname>(Key<segnum>, len <seglength>) S

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 303VENGINE 25091MESSAGE[Para <block_name>/<1>] Item <itemname&

VENGINE 25092MESSAGE[Para <block_name>/<1>] Item <itemname> does not fit into existing SM segment (probably because of names) SEVERI

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 305VENGINE 25093MESSAGE[Para <block_name>/<1>] Existing SM segmen

VENGINE 25094MESSAGE[Para <block_name>/<1>] Item <itemname> belongs to another SM segment SEVERITY3PROBABLE CAUSEThe application att

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 307VENGINE 25095MESSAGE[Para <block_name>/<1>] Item <itemname&

VENGINE 25096MESSAGE[Para <block_name>/<1>] Run out of UID slots for SM SEVERITY3PROBABLE CAUSEThere is an error which may indicate a more

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 309VENGINE 25097MESSAGE[Para <block_name>/<1>] Cannot find UID &l

GeoTel Features User Manual CCM AlarmsP0602482 Ver. 04.03 Avaya Page 31CCM 12001MESSAGELoadInfo error, no phone line resource in RSET profile.SEVERITY

VENGINE 25098MESSAGE[Para <block_name>/<1>] Cannot find another UID to pass SM ownership (shmid <schmid>) SEVERITY3PROBABLE CAUSEThe

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 311VENGINE 25099MESSAGE[Para <block_name>/<1>] Cannot read SM seg

VENGINE 25100MESSAGE[Para <block_name>/<1>] Items <itemname> and <itemname> (subitem <itemname>) do not match in aggreg

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 313VENGINE 26000MESSAGE[Para <block_name>/<1>] Invalid SEND PHONE

VENGINE 26001MESSAGE[Para <block_name>/<1>] Too many digits <#> to speak SEVERITY3PROBABLE CAUSEThere is an error which may indicate

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 315VENGINE 26002MESSAGE[Para <block_name>/<1>] Invalid time to sp

VENGINE 26003MESSAGE[Para <block_name>/<1>] Invalid month number <#> to speak SEVERITY3PROBABLE CAUSEThe application attempting to s

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 317VENGINE 26004MESSAGE[Para <block_name>/<1>] Invalid day number

VENGINE 26005MESSAGE[Para <block_name>/</1>] Invalid RECSIZE <size> for TDQ file '<filename>' SEVERITY3PROBABLE CAUS

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 319VENGINE 26006MESSAGE[Para <block_name>/<1>] File '<fil

class ID>] reason [<reason code>] shutting down.SEVERITY9PROBABLE CAUSEThere is a configuration/licensing error.ACTION• The system was config

VENGINE 26007MESSAGE[Para <block_name>/<1>] File '<filename>' has been opened with recsize = <size> SEVERITY3PROBABL

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 321VENGINE 26008MESSAGE[Para <block_name>/<1>] TDQ file '<

VENGINE 26009MESSAGE[Para <block_name>/<1>] Cannot reopen TDQ file '<filename>' after truncation SEVERITY3PROBABLE CAUSETh

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 323VENGINE 26010MESSAGE[Para <block_name>/<1>] File '<fil

VENGINE 26011MESSAGE[Para <block_name>/<1>] File '<filename>' is open SEVERITY3PROBABLE CAUSEThe application attempted to

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 325VENGINE 26012MESSAGE[Para <block_name>/<1>] Cannot remove TDQ

VENGINE 26013MESSAGE[Para <block_name>/<1>] Cannot write TDQ file '<filename>' SEVERITY3PROBABLE CAUSE1. The file permissi

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 327VENGINE 26014MESSAGE[Para <block_name>/<1>] Cannot read TDQ fi

VENGINE 26015MESSAGE[Para <block_name>/<1>] Timer was not started SEVERITY3PROBABLE CAUSEThe application executed a timer-difference call

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 329VENGINE 26016MESSAGE[Para <block_name>/<1>] Cannot initialize

This chapter covers:COMMGR Alarms1. COMMGR Alarms

VENGINE 26017MESSAGE[Para (<block_name>/<1>] Key '<name>' not found in dataset '<name>' SEVERITY3PROBABLE

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 331VENGINE 26018MESSAGE[Para <block_name>/<1>] Duplicate record k

VENGINE 26019MESSAGE[Para <block_name>/<1>] Attempt to set the second lock for dataset '<name>' SEVERITY3PROBABLE CAUSEThe

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 333VENGINE 26020MESSAGE[Para <block_name>/<1>] I/O error in datas

VENGINE 26021MESSAGE[Para <block_name>/<1>] Cannot change access mode for CONST SM segment #<number>SEVERITY3PROBABLE CAUSEShared m

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 335VENGINE 26024MESSAGE[Para <block_name >/<1>] Function '&l

VENGINE 26025MESSAGE[Para <block_name >/<1>] Function '<function-name>' from library '<library-name>' chan

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 337VENGINE 26026MESSAGE[Para <block_name >/<1>] Function '&l

VENGINE 26027MESSAGE[Para <block_name >/<1>] Library '<library-name>' changed MT state.SEVERITY3PROBABLE CAUSEDynamic load

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 339VENGINE 26028MESSAGE[Para <block_name >/<1>] Heap is damaged &

COMMGR 10100MESSAGEWarning: Protocol alarm, <text> SEVERITY3PROBABLE CAUSEThere is an error at the protocol level of host communications. The er

VENGINE 26029MESSAGE[Para <block_name >/<1>] vengine exits after -z <number> runs to prevent possible memory leaks.SEVERITY3PROBABLE

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 341VENGINE 28000MESSAGE[Para <block_name>/<1>] Cannot change the

VENGINE 28001MESSAGE[Para <block_name>/<1>] Invalid file name, function <array-read/array-write/file-to-message/message-to-file/openq/T

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 343VENGINE 28002MESSAGE[Para <block_name>/<1>] Cannot open <ty

VENGINE 28003MESSAGE[Para <block_name>/<1>] Invalid length (<length>), function/for '<convert-from-binary/ convert-to-binary

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 345VENGINE 28004MESSAGE[Para <block_name>/<1>] Cannot create &apo

VENGINE 28005MESSAGE[Para <block_name>/<1>] MPS receive time expired for <str> request SEVERITY3PROBABLE CAUSEThe application receiv

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 347VENGINE 28006MESSAGE[Para <block_name>/<1>] Unexpected reply f

VENGINE 28007MESSAGE[Para <block_name>/<1>] Invalid option '<optname>' for function '<extern/issue>' SEVER

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 349VENGINE 28008MESSAGE[Para <block_name>/<1>] Invalid NULL condi

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 35COMMGR 10101MESSAGEWarning: Transmit of message <msg_type>/<msg_sub

VENGINE 28009MESSAGE[Para <block_name>/<1>] Expected condition '<condition>' arrived SEVERITY3PROBABLE CAUSEVENGINE was st

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 351VENGINE 28010MESSAGE[Para <block_name>/<1>] Asynchronous ignor

VENGINE 28011MESSAGE[Para <block_name>/<1>] Synchronous expected condition '<condition>' arrived SEVERITY3PROBABLE CAUSEVE

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 353VENGINE 28012MESSAGE[Para <block_name>/<1>] Ignored condition

VENGINE 28014MESSAGE[Para <block_name>/<1>] <Exception/unexpected> condition '<condition>' arrived SEVERITY3PROBABLE

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 355VENGINE 28015MESSAGE[Para <block_name>/<1>] Cannot allocate &l

VENGINE 28016MESSAGE[Para <block_name>/<1>] Cannot map file '<filename>' SEVERITY3PROBABLE CAUSE1. The displayed map file

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 357VENGINE 28017MESSAGE[Para <block_name>/<1>] Cannot send '

VENGINE 28018MESSAGE[Para <block_name>/<1>] Invalid (NULL) message to or from vastimer SEVERITY3PROBABLE CAUSEThere is an error which may

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 359VENGINE 28019MESSAGE[Para <block_name>/<1>] Cannot find servic

COMMGR 10102MESSAGEWarning: Received unexpected message <msg_type>/<msg_subtype> from <process>(cd=<dest_conn_ID>) SEVERITY3PR

VENGINE 28020MESSAGE[Para <block_name>/<1>] Cannot lock <file> SEVERITY3PROBABLE CAUSEThere is an error which may indicate a more se

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 361VENGINE 28021MESSAGE[Para <block_name>/<1>] Shared memory corr

VENGINE 28022MESSAGE[Para <block_name>/<1>] No map fields to send or receive (fields #<#>) SEVERITY3PROBABLE CAUSEThere is an error

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 363VENGINE 28023MESSAGE[Para <block_name>/<1>] Internal error. Fi

VENGINE 28024MESSAGE[Para <block_name>/<1>] Received <#received> map fields instead of <#expected> SEVERITY3PROBABLE CAUSEThe

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 365VENGINE 28025MESSAGE[Para <block_name>/<1>] Received invalid f

VENGINE 28026MESSAGE[Para <block_name>/<1>] Invalid program function name in item <#> SEVERITY3PROBABLE CAUSEThe application specifi

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 367VENGINE 28027MESSAGE[Para <block_name>/<1>] Invalid program or

VENGINE 28029MESSAGE[Para <block_name>/<1>] Cannot initialize shared memory SEVERITY3PROBABLE CAUSEThere is an error which may indicate a

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 369VENGINE 28030MESSAGE[Para <block_name>/<1>] Invalid number of

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 37COMMGR 10104MESSAGEWarning: Invalid MX handle <handle> in message <

VENGINE 28031MESSAGE[Para <block_name>/<1>] Program (function) <user CALL function name> was not found or there are unresolved refer

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 371VENGINE 28032MESSAGE[Para <block_name>/<1>] Unexpected host me

VENGINE 28033MESSAGE[Para <block_name>/<1>] Cannot receive <type> message SEVERITY3PROBABLE CAUSEThere is an error which may indicat

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 373VENGINE 28034MESSAGE[Para <block_name>/<1>] Failure for <bi

VENGINE 28035MESSAGE[Para <block_name>/<1>] Cannot deliver message to line/port #<line/port#> SEVERITY3PROBABLE CAUSEThe system atte

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 375VENGINE 28036MESSAGE[Para <block_name>/<1>] Cannot translate r

VENGINE 28038MESSAGE[Para <block_name>/<1>] Service <name> is not attached to port <#> SEVERITY3PROBABLE CAUSEThe system attem

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 377VENGINE 28039MESSAGE[Para <block_name>/<1>] In Execute-Command

VENGINE 28040MESSAGE[Para <block_name>/<1>] Shell cannot be executed for '<var>' SEVERITY3PROBABLE CAUSEThe application at

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 379VENGINE 28041MESSAGE[Para <block_name>/<1>] Cannot find host &

COMMGR 10112MESSAGECannot allocate <string>, size <string>. SEVERITY7PROBABLE CAUSEThere has been an error in internal memory allocation,

VENGINE 28043MESSAGE[Para <block_name>/<1>] Cannot uncompress map fields SEVERITY3PROBABLE CAUSEThe application cannot uncompress host ma

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 381VENGINE 28044MESSAGE[Para <block_name>/<1 >] Second argument

VENGINE 28045MESSAGE[Para <block_name>/<1 >] Unresolved INVOKE <appname> SEVERITY3PROBABLE CAUSEThe application attempted to link t

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 383VENGINE 29001MESSAGE[Para <block_name>/<1>] Line will be immed

VENGINE 29002MESSAGE[Para <block_name>/<1>] Cannot run non-redundant with secondary vvpether SEVERITY3PROBABLE CAUSEThere is an error whic

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 385VENGINE 29003MESSAGE[Para <block_name>/<1>] Cannot connect to

VENGINE 29004MESSAGE[Para <block_name>/<1>] Line is not bound SEVERITY3PROBABLE CAUSEThe application attempted to execute a function which

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 387VENGINE 29005MESSAGE[Para <block_name>/<1>] Socket to vms is b

VENGINE 29006MESSAGE[Para <block_name>/<1>] Redundancy Socket is broken fd <rssocket>) SEVERITY3PROBABLE CAUSEThere is an error whi

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 389VENGINE 29007MESSAGE[Para <block_name>/<1>] File <filename&

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 39COMMGR 11000MESSAGEInvalid mode specified for host.SEVERITY4PROBABLE CAUSEAn

VENGINE 29008MESSAGE[Para <block_name>/<1>] MPS number is unavailable SEVERITY3PROBABLE CAUSEThere is an error which may indicate a more s

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 391VENGINE 29010MESSAGE[Para <block_name>/<1>] Program <name&g

VENGINE 29011MESSAGE[Para <block_name>/<1>] Executable for Program <name> outdated and has to be recreated SEVERITY3PROBABLE CAUSEVE

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 393VENGINE 29012MESSAGE[Para <block_name>/<1>] Program <name&g

VENGINE 29015MESSAGE[Para <block_name>/<1>] No useful i/o detected SEVERITY3PROBABLE CAUSEThe application did not perform any input/output

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 395VENGINE 29016MESSAGE[Para <block_name>/<1>] Norestart conditio

VENGINE 29017MESSAGE[Para <block_name>/<1>] Terminal status '<soft termination/hard termination/fatal error/initialization>&apo

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 397VENGINE 29028MESSAGE[Para <block_name>/<1>] NOOP found in the

VENGINE 29051MESSAGE[Para <block_name>/<1>] Asynchronous <datatype> data arrived SEVERITY3PROBABLE CAUSEAsynchronous data arrived.A

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 399VENGINE 29053MESSAGE[Para <block_name>/<1>] Exception 0x<n

COMMGR 11019 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52COMMGR 11023 . . . . . . . . . . . . . . . . . . . . . . . .

COMMGR 11001MESSAGEInvalid VT number: <vt_number>.SEVERITY4PROBABLE CAUSEThe VT number specified in the assignvt command is not within the valid

VENGINE 29054MESSAGE[Para <block_name>/<1>] Illegal type for Argument <name> in timed Call Function <name> SEVERITY3PROBABLE

GeoTel Features User Manual VENGINE AlarmsP0602482 Ver. 04.03 Avaya Page 401VENGINE 29056MESSAGE[Para <block_name>/<1>] Throw condition &

VENGINE 29058MESSAGE[Para <block_name>/<1>] Call function <name> is not MT safeSEVERITY3PROBABLE CAUSEThere is an error which may i

This chapter covers:VMM Alarms1. VMM Alarms

VMM 10000MESSAGEElement not found: element_info SEVERITY1PROBABLE CAUSEThe MMF file containing the element has not been loaded, does not contain the s

GeoTel Features User Manual VMM AlarmsP0602482 Ver. 04.03 Avaya Page 405<element name><element name!offset><element name!offset,duratio

VMM 10001MESSAGEFailed to load MMF mmfname: reason_text SEVERITY1PROBABLE CAUSEThe specified MMF file could not be loaded. The cause depends on the re

GeoTel Features User Manual VMM AlarmsP0602482 Ver. 04.03 Avaya Page 407MMF can only be opened READ ONLY The specified MMF is being opened for recordi

VMM 10002MESSAGEInvalid hash table size specified for cmd. Valid range is 1-#. SEVERITY1PROBABLE CAUSEAn invalid parameter for the hash table size was

GeoTel Features User Manual VMM AlarmsP0602482 Ver. 04.03 Avaya Page 409VMM 10003MESSAGEInvalid value specified for numcachethd. Valid range is 1-#. S

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 41COMMGR 11002MESSAGELine number out of range: <line_number>.SEVERITY4PR

VMM 10004MESSAGEInvalid page size specified. Valid values are 1, 2, 4, and 8. SEVERITY1PROBABLE CAUSEAn invalid page size was specified for the vmm pa

GeoTel Features User Manual VMM AlarmsP0602482 Ver. 04.03 Avaya Page 411VMM 10005MESSAGEInvalid value specified for vdmmaxlock. SEVERITY1PROBABLE CAUS

VMM 11000MESSAGECache Full. Failed to load data. SEVERITY4PROBABLE CAUSECache memory is filled to capacity and no data can be swapped out, causing dat

GeoTel Features User Manual VMM AlarmsP0602482 Ver. 04.03 Avaya Page 413VMM 11001MESSAGEFailed to open filename. SEVERITY4PROBABLE CAUSE1. Attempting

VMM 11002MESSAGEMMF [ mmf_name ] needs check with mfck. SEVERITY4PROBABLE CAUSEThe specified MMF was not closed properly the last time the system was

GeoTel Features User Manual VMM AlarmsP0602482 Ver. 04.03 Avaya Page 415VMM 11003MESSAGEFailed to process configuration file [ filename ]. SEVERITY4PR

VMM 11004MESSAGEDisk I/O Error at Address address. SEVERITY4PROBABLE CAUSE1. An MMF file is corrupt.2. There is a hard disk error.ACTION1. Unload the

GeoTel Features User Manual VMM AlarmsP0602482 Ver. 04.03 Avaya Page 417VMM 12000MESSAGEFailed to process MMF configuration file [ filename ] SEVERITY

VMM 12001MESSAGECannot determine the size of voice memory. SEVERITY9PROBABLE CAUSEA request for TMS package memory information. There may be a problem

GeoTel Features User Manual VMM AlarmsP0602482 Ver. 04.03 Avaya Page 419VMM 12002MESSAGEFailed to establish communications with TMS. SEVERITY9PROBABLE

COMMGR 11003MESSAGENo pooled vt associated with the line.SEVERITY4PROBABLE CAUSEAn ENVIRONMENT parameter "...$VT..." command was executed in

VMM 12003MESSAGEFailed to configure digit table. SEVERITY4PROBABLE CAUSE1. Incompatible software packages have been installed or were installed incorr

This chapter covers:VSTAT Alarms1. VSTAT Alarms

VSTAT 11000MESSAGEData received from more lines (<# received>) than expected (<# expected>)SEVERITY4PROBABLE CAUSEStatus messages from tca

GeoTel Features User Manual VSTAT AlarmsP0602482 Ver. 04.03 Avaya Page 423VSTAT 11001MESSAGEData received from less lines (<# received>) than ex

VSTAT 11002MESSAGEData received from previously unknown span: <span logical identifier>SEVERITY4PROBABLE CAUSEDuring the most recent update cycl

GeoTel Features User Manual VSTAT AlarmsP0602482 Ver. 04.03 Avaya Page 425VSTAT 11003MESSAGEData received from more hosts (<# received>) than ex

VSTAT 11004MESSAGEData received from less hosts (<# received>) than expected (<# expected>)SEVERITY4PROBABLE CAUSEDuring the update cycle,

GeoTel Features User Manual VSTAT AlarmsP0602482 Ver. 04.03 Avaya Page 427VSTAT 11005MESSAGEUPDATE failed: <reason>SEVERITY4PROBABLE CAUSENormal

VSTAT 11006MESSAGE<Message type> message transmission failed to <process>SEVERITY4PROBABLE CAUSEA vstat message could not be sent to eithe

GeoTel Features User Manual VSTAT AlarmsP0602482 Ver. 04.03 Avaya Page 429VSTAT 11007MESSAGEunsolicited statistics data received from <process>;

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 43COMMGR 11009MESSAGERead for non-pooling lines only. SEVERITY4PROBABLE CAUSET

This page has been intentionally left blank.

This chapter covers:VXMLI Alarms1. VXMLI Alarms

VXMLI 10000MESSAGEThe MMF play prefetch failed: element_nameSEVERITY1PROBABLE CAUSEThe MMF file containing the element is not loaded or does not conta

GeoTel Features User Manual VXMLI AlarmsP0602482 Ver. 04.03 Avaya Page 433VXMLI 10001MESSAGEThe audio server play prefetch failed: URL_of_audio_fileSE

This page has been intentionally left blank.

This chapter covers:NCD Alarm Messages1. Messages for NCD alarm 100042. Diagnostics

NCD AlarmsThe NCD alarms display the alarm/diagnostics messages sent from the Network Interface Controller (NIC) and the redundant backup controller.N

GeoTel Features User Manual NCD Alarm MessagesP0602482 Ver. 04.03 Avaya Page 437NIC Clearing Loss of Secondary NIC NIC Clearing Loss of data integrity

3 Volt Power supply for TMS in slot %d is out of tolerance, detecting voltage below 2.9 volt threshold • See “Voltage” on page 442.3 Volt Power supply

GeoTel Features User Manual NCD Alarm MessagesP0602482 Ver. 04.03 Avaya Page 439Temperature for TMS in slot # is out of tolerance, detecting temperatu

COMMGR 11010MESSAGECannot connect to the RTU service. SEVERITY3PROBABLE CAUSEThere is a network configuration problem.ACTIONRestart SRP. If the proble

Clearing Alarm for TMS in slot # failure to load software image Clearing alarm for TMS Resource faulty

GeoTel Features User Manual NCD Alarm MessagesP0602482 Ver. 04.03 Avaya Page 441Troubleshooting GuidelinesNIC Phase Lock Loop (PLL)A system can functi

TemperatureThe system (and all components) are designed to operate within a normal temperature range. If the system operates outside that range for ex

GeoTel Features User Manual NCD Alarm MessagesP0602482 Ver. 04.03 Avaya Page 443TMS InitializationFailed TMS bootup usually prevents the rest of the s

This page has been intentionally left blank.

This chapter covers:TCAD Alarm Messages1. Messages for TCAD alarm 110002. Diagnostics

TCAD AlarmsThe TCAD alarms display the alarm/diagnostics messages sent from the Telephony Media Server (TMS), sent through the Network Interface Contr

GeoTel Features User Manual TCAD Alarm MessagesP0602482 Ver. 04.03 Avaya Page 447Alarms, Diagnostics and Statistics Management (ADSM) failed to initia

TMS_PLL Loss of Reference Clock A • There is no longer a redundant reference clock (clock A) available for the Phase Locked Loop. See “TMS PLL” on pag

GeoTel Features User Manual TCAD Alarm MessagesP0602482 Ver. 04.03 Avaya Page 449TMS in slot # received restart command • The TMS received a command t

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 45COMMGR 11011MESSAGESend error: <message> SEVERITY3PROBABLE CAUSEThis i

Clearing Monitor (MON) failure to initialize Clearing Failure to initialize a TMS Card Clearing alarm Resource Set Manager (RSET) unable to spawn proc

GeoTel Features User Manual TCAD Alarm MessagesP0602482 Ver. 04.03 Avaya Page 451Troubleshooting GuidelinesTMS InitializationFailed TMS bootup usually

TMS SpansThe TMS spans interface directly with the external telephone network. Properly working spans should be in the "green" state. All ot

Keyboard locked • Two SEND TEXT/MAPs were sent consecutively with no RECEIVE TEXT/MAP or AID (RESET) between them.map not supported • A map was sent t

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 47EXAMPLETue May 23 14:39:45 <commgr> 11011 Line 16 Host 1 Severity 3 Vp

COMMGR 11014MESSAGEMemory allocation error: <error_message> SEVERITY4PROBABLE CAUSEThere is no more available memory in the system.ACTIONFor sho

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 49COMMGR 11015MESSAGE<command> for a generic host. SEVERITY4PROBABLE CAU

GeoTel Features User ManualP0602482 Ver. 04.03 Avaya Page 5COMMGR 11116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98CON

COMMGR 11017MESSAGEHost <#> status: <text> SEVERITY4PROBABLE CAUSEThe status of the specified host is displayed. It can be either up and r

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 51COMMGR 11018MESSAGEA pool must be associated with the <command> comman

COMMGR 11019MESSAGEPool <poolname> undefined SEVERITY4PROBABLE CAUSEAn attempt was made to use the displayed pool name in a command but the pool

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 53COMMGR 11023MESSAGEtty receive problem: No line associated with VT 1. SEVERI

COMMGR 11025MESSAGECannot send RTU <event> generic event SEVERITY3PROBABLE CAUSEThere was an internal system failure error in attempting to send

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 55COMMGR 11026MESSAGECannot get RTU generic event ack data. SEVERITY3PROBABLE

COMMGR 11027MESSAGEDevice <dev> already assigned to host <#>. SEVERITY3PROBABLE CAUSEThe displayed device is already being used by the dis

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 57COMMGR 11029MESSAGEHost down. SEVERITY3PROBABLE CAUSEThe host has gone down.

COMMGR 11030MESSAGEInvalid polled information request subtype <#>. SEVERITY3PROBABLE CAUSEThere is an internal host messaging communications err

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 59COMMGR 11031MESSAGECannot set tran code, invalid mode for host. SEVERITY3PRO

RCM 20207 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139RCM 20208 . . . . . . . . . . . . . . . . . . . . . . .

COMMGR 11032MESSAGEInvalid rtu message subtype <#> SEVERITY3PROBABLE CAUSEThere is an internal host messaging communications error.ACTIONIf this

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 61COMMGR 11033MESSAGEVT <#> already assigned to line <#>. SEVERITY

COMMGR 11034MESSAGEVT <#> already assigned to pool <poolname> SEVERITY3PROBABLE CAUSEAn attempt was made to assign a VT to a pool when the

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 63COMMGR 11036MESSAGEVT <#> is down. SEVERITY3PROBABLE CAUSEA RECEIVE TE

COMMGR 11038MESSAGELine <#> already has VT <#> assigned to it. SEVERITY3PROBABLE CAUSEAn attempt was made to assign a VT to a service (lin

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 65COMMGR 11039MESSAGEInvalid line number, non-numeric number entered:<chara

COMMGR 11040MESSAGEGetvt request failed, couldn't set vt <#> to line <#>. SEVERITY3PROBABLE CAUSEMemory has been corrupted when a VT

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 67COMMGR 11041MESSAGECannot pool {an async | a non-screen} host. SEVERITY3PROB

COMMGR 11042MESSAGEPool <poolname> cannot be added after the system has been initialized. SEVERITY3PROBABLE CAUSEAn attempt was made to create a

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 69COMMGR 11043MESSAGEMemory allocation problem, cannot create Pool: <poolna

GeoTel Features User ManualP0602482 Ver. 04.03 Avaya Page 7TCAD 10011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

COMMGR 11044MESSAGECannot add entry to Queue <string>.SEVERITY3PROBABLE CAUSEThere is an internal host messaging communications error.ACTIONIf t

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 71COMMGR 11045MESSAGEPooling mode is not allowed for a console sendtext. SEVER

COMMGR 11046MESSAGENo VT associated with pool <poolname>, line <#>. SEVERITY3PROBABLE CAUSEAn ENVIRONMENT usepool or ENVIRONMENT freevt co

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 73COMMGR 11050MESSAGEGot a receive map for a non-screen host. SEVERITY3PROBABL

COMMGR 11055MESSAGEInvalid vt number, async host only allowed 1 to 1 mappingof vt to line. SEVERITY3PROBABLE CAUSEAn attempt was made to assign a VT t

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 75COMMGR 11056MESSAGEGeneric host protocol alarmNo translation function for ho

COMMGR 11057MESSAGEThe default aid key is too long, maximum length is <length>. SEVERITY3PROBABLE CAUSEThe default aid key was set to a string t

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 77COMMGR 11058MESSAGEInvalid protocol name specified. SEVERITY3PROBABLE CAUSET

COMMGR 11059MESSAGEMemory allocation error.SEVERITY3PROBABLE CAUSEThe system was out of memory when the application issued a RECEIVE MAP or a RECEIVE

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 79COMMGR 11067MESSAGEInvalid mode specified, valid modes are 24, pace, screen,

VENGINE 25011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229VENGINE 25013 . . . . . . . . . . . . . . . . . . . . . . . .

COMMGR 11069MESSAGECommand <command> for a <host_type> host only. SEVERITY3PROBABLE CAUSESpecified command is not valid for configured ho

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 81COMMGR 11071MESSAGECommand <string> has already been received.SEVERITY

COMMGR 11072MESSAGECommand <string> value <decimal> is out of range. SEVERITY3PROBABLE CAUSECOMMGR received a configuration option or comm

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 83COMMGR 11073MESSAGEAttempt to open connection on host <string> on port

COMMGR 11076MESSAGEAttempt to open connection to host <host_name> (<ip_address>) for protocol <protocol> failed. SEVERITY2PROBABLE C

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 85COMMGR 11077MESSAGEUnable to get the system name. SEVERITY2PROBABLE CAUSECOM

COMMGR 11102MESSAGEAttempted to get or set an unknown parameter <string> for host service <id>. SEVERITY3PROBABLE CAUSEThere was an attemp

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 87COMMGR 11103MESSAGEWarning: Attempted to get or set an unknown MX parameter

COMMGR 11105MESSAGEWarning: No pooled vt associated with the service <service> SEVERITY3PROBABLE CAUSEThere was an attempt to use pooled Virtual

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 89COMMGR 11106MESSAGEOption <string> requires a specific host number to

GeoTel Features User ManualP0602482 Ver. 04.03 Avaya Page 9VENGINE 25060 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275VE

COMMGR 11107MESSAGEOption <string> issued for a undefined host. SEVERITY3PROBABLE CAUSEAn option was specified in a command for an undefined hos

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 91COMMGR 11108MESSAGEFailed to open <filename>, <reason>. SEVERITY

COMMGR 11109MESSAGEOption <string> requires a host service identifier to be specified. SEVERITY3PROBABLE CAUSEAn option was specified in a comma

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 93COMMGR 11110MESSAGETimeout <string> must be between <value> secs

COMMGR 11111MESSAGETimer <string> requires ‘er’ to be larger that ‘intime’ on host service <id>. SEVERITY3PROBABLE CAUSEThe timeout value

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 95COMMGR 11113MESSAGEAttempt to set parameter <string> to invalid value

COMMGR 11114MESSAGEOption <string> requires a virtual terminal to be specified.SEVERITY3PROBABLE CAUSEAn option was specified in a command witho

GeoTel Features User Manual COMMGR AlarmsP0602482 Ver. 04.03 Avaya Page 97COMMGR 11115MESSAGENo line associated with vt <id>.SEVERITY3PROBABLE C

COMMGR 11116MESSAGEThe line associated with vt <id> differs from line <id>.SEVERITY3PROBABLE CAUSEAn option was specified in a command req

This chapter covers:CONFMGMT Alarms1. Conference Manager Alarms