|
|
This appendix provides a discussion of system tasks and messages generated by the Billing and Measurements Server (BAMS) and their use in troubleshooting. These messages can be categorized as alarms or events and are generated by the different software tasks running on the BAMS. This chapter also provides information on the file naming conventions used for files collected or processed by the BAMS.
The BAMS traps alarms and minor (*), major (**), or critical (*C) events and forwards them to the Cisco Media Gateway Controller Node Manager. Alarms marked "*C", "**" or "*" generate SNMP traps.
 |
Note The following alarms are auto-cleared when the alarm condition is removed: ACC227, MGR801, MSC030, MSC031, MSC032, MSC040, MSC041, MSC042, MSC130, MSC131, MSC132, MSC140, MSC141, MSC142,CRD502, POL327, POL401, and POL 402. |
The BAMS writes alarms only to the alarm history file. When an alarm is cleared, its entry is deleted from that file.
Alarms and minor, major, or critical event messages to be forwarded to a message queue and trapped are defined with the Alarm Parameters TagID (ALM-PARMS), with the msgfwdlevel field (see "Operating BAMS," for details).
|
Note All task messages are written to the system log (syslog) file. It is recommended that the operations support personnel monitor the syslog file on a regular basis and note alarms and events that require troubleshooting. The bootstrap function can facilitate this task. |
BAMS functions are governed by system tasks. Table A-1 displays BAMS tasks. For information about the messages produced by these system tasks, see the "Generic Messages" section.
| Task | Explanation |
|---|---|
ACC | The accumulation task. This task accumulates numerical information on collected usage records. |
ALM | The alarm task. This task collects and distributes alarm and event information. |
AUG (AGB, AGS) | The augmentation task. This task uses lookup information to add value to the collected usage records. Messages related to BAF output are written with an Augmented BAF (AGB) task identifier to the system log, those related to statistical measurements as Augmented Statistics (AGS). |
ASC | The ASCII conversion task. This task is used to convert the Cisco MGC CDR files to ASCII files. |
COR | The correlation task. This task correlates records received from each Cisco MGC in a redundant pair configuration into a single-record format. |
CRD | The check remote down task. This task monitors communications between the two BAMS units and checks the status of the remote data collector. |
CTB | The call detail record (CDR) to Bellcore AMA Format (BAF) conversion task. This task converts CDRs into a BAF format. |
DRX | The message receive task. This task is used by one BAMS unit to receive messages from another BAMS unit. |
DTX | The message transmit task. This task transmits communications from one data collector to the next. |
FMT | The formatting task. This task controls the initial formatting of data collected from the Cisco MGCs. |
MGR | The manager task. This task manages and spawns all other BAMS tasks. |
MML (mml) | The Man-Machine Language (MML) task. This task displays the mml interface. |
MSC | The mass storage control task. This task manages the user-defined attributes governing the maintenance removal of files from BAMS. |
POL | The redundant unit polling task. This task is used to collect data from (redundant) Cisco MGC units. |
P01 | The P01 output task. This task is used to output records in the Infostrada P01 format. |
RCV | The control file receive task. This task is used by the BAMS unit to receive a control file. Note This task is executed by the POL task and is not a full-time running task.
|
SXF | The send file transfer task. This task is used by the system to send a control file to a remote BAMS unit. Note This task is executed by the POL task and is not a full-time running task.
|
The normal state of the redundant BAMS is active/standby, where one unit is actively polling the Cisco MGC and the other unit is in a standby mode. Under certain error conditions, the BAMS unit can enter an active/active polling state. The following procedure explains how to recover from the undesired active/active polling state.
The polling software was designed so the worst-case scenario would be a standby/standby state, because in this state neither BAMS unit is polling and data is accumulating on the MGC. In safe-guarding the system so a standby/standby state would not occur, certain race conditions (where a possible standby/standby state may occur) have been taken care of by defaulting to an active/active polling state. There are few cases in which this would happen, but defaulting to an active/active polling state is a safe method of avoiding any critical problems.
The active/active polling state is not a critical state because in this mode, the BAMS unit that has the correct sequence numbers would be able to continue polling, and the other BAMS unit, although in an active state would not be able to poll the files that the first BAMS has already polled. Also, the processing would not be interrupted because the BAMS unit that is able to poll forwards the data to the other BAMS unit for redundant processing.
To reset the system to a normal active/standby state, the system that is not polling and has the incorrect sequence numbers must be updated. Updating can be accomplished by executing a rotation (sw-ovr) from active to standby on the BAMS unit that has the correct sequence numbers; that is, the unit that is actually polling files. By rotating from active to standby, this BAMS unit goes to standby, and the other BAMS unit that was active but was not able to poll is updated with the correct polling sequence numbers. Once the sw-ovr is executed, the active unit is able to poll the MGC successfully, and a normal active/standby state results.
For consistency, the application requires that the data sources follow certain file-naming conventions. The convention is to use a unique prefix per file format, followed by a time stamp that indicates when the file was created or generated on the data source, and a file sequence number.
The following file-naming conventions are used for BAMS input and output files.
The file-naming convention for BAF billing record files is:
Prefix_YYYYMMDDHHMMSS_SeqNo.bin
Table A-2 explains each element of the filename. Note the use of the underscore.
| Element | Description |
|---|---|
Prefix | Represents the filename prefix; for example, baf_cdr_ |
YYYY | Represents the year; for example, 2000 |
MM | Represents the month; for example, 05 |
DD | Represents the day; for example, 15 |
HH | Represents the hour; for example, 19 |
MM | Represents the minute; for example, 46 |
SS | Represents the second; for example, 23 |
SeqNo | Represents the sequence number; for example, _000051 |
.bin | Represents the suffix |
The file-naming convention for data collected from the Cisco MGC is:
Prefix_YYYYMMDDHHMMSS_SeqNo.bin
Table A-3 explains each element of the filename. Note the use of the underscore.
| Element | Description |
|---|---|
Prefix | Represents the filename prefix; for example, cdr_ |
YYYY | Represents the year; for example, 2000 |
MM | Represents the month; for example, 05 |
DD | Represents the day; for example, 15 |
HH | Represents the hour; for example, 19 |
MM | Represents the minute; for example, 46 |
SS | Represents the second; for example, 23 |
SeqNo | Represents the sequence number; for example, _000051 |
.bin | Represents the suffix |
The file-naming convention for data collected from the Cisco MGC and converted into ASCII 1110 record format is:
Prefix_YYYYMMDDHHMMSS_SeqNo.csv
Table A-4 explains each element of the filename. Note the use of the underscore.
| Element | Description |
|---|---|
Prefix | Represents the filename prefix; for example, cdr_ |
YYYY | Represents the year; for example, 2000 |
MM | Represents the month; for example, 05 |
DD | Represents the day; for example, 15 |
HH | Represents the hour; for example, 19 |
MM | Represents the minute; for example, 46 |
SS | Represents the second; for example, 23 |
SeqNo | Represents the sequence number; for example, _000051 |
.csv | Represents the suffix |
Log files are used to save debug or status information for a particular task. These files are saved to the /opt/CiscoBAMS/files directory.
task-identifier.log
Table A-5 explains each element of the filename. Note the use of the underscore.
| Element | Description |
|---|---|
task_identifier | Tag to identify the task that this log file refers to; for example, the FMT task. Sometimes followed by a qualifier; for example, _cdr. |
.log | Fixed suffix to indicate that the file is a log file. |
Task configuration files pass all the necessary command-line switches that are needed by the MGR task to properly execute a particular task. These files are stored in the /opt/CiscoBAMS/files directory. The following filenames are used.
task_identifier{task_instance}_cfg
Table A-6 explains each element of the filename. Note the use of the underscore.
| Element | Description |
|---|---|
task_identifier | Tag to identify the task that this configuration file refers to. |
task_instance | Optional instance sequence. For example, if there are two instances of the COR task running, the following filenames can be used for the configuration files; for example, cor0_cfg, cor1_cfg. |
_cfg | Fixed suffix to indicate that the file is a task configuration file. |
Task parameter files contain parameter definition files for a particular task. These files are stored in the /opt/CiscoBAMS/files directory. These files are in ASCII format. The filenames used are shown in Table A-7.
Format task_identifier{task_instance}.cfg
BAMS stores system activity in the System Log File (syslog) in the format shown in Table A-8. Located in the /CiscoBAMS/files directory, the syslog is composed of individual log entries that follow this format example: MM/DD/YY hh:mm:ss severity message ID: +message text.
| Item | Description |
|---|---|
MM/DD/YY | The date that BAMS wrote the entry to the file. |
hh:mm:ss | The time that BAMS wrote the entry to the file. |
severity | If indicated, represents the importance level of the message: *C indicates a critical event or alarm. ** indicates a major event or alarm. * indicates a minor event or alarm. W indicates a warning event. M indicates a manual problem (operator intervention required). Two blank spaces indicate an informational event. DB indicates a debug event. |
message ID | A three-character task name that generated the message, followed by a three-digit code that identifies the particular message. |
message text | The brief message or description of the alarm or event. If indicated, a plus sign (+) represents the line as a continuation of the previous line. |
The syslog file holds a user-specified number of messages. When the syslog file's maximum file size is reached, BAMS changes the name of the syslog file to oldlog and then creates a new syslog file.
While only one syslog file can exist at a time, BAMS can retain multiple oldlog files. BAMS creates additional oldlog files in the same manner that it creates syslog files. If an oldlog file exists when it is time to create a syslog, BAMS renames the oldlog file to oldloga. If more than two oldlog files exist, BAMS uses the letters b, c, d, and so on to identify the oldest oldlog file. (For example, oldlogd is older than oldlogc).
The following categories of information are provided for each system message:
The message ID (also known as the message header) is a six-character label that uniquely identifies each message. The first three characters are the application task ID, which identifies the application task that generated the message. (For example, MGR denotes the Manager task and MSC denotes the Mass Storage Control task.) The second three characters are the message number; for example, 013 or 123.
|
Note In the task listings below, the alarm levels are indicated in parentheses after the alarm number. If the words Log Event appear in parentheses, this indicates that the event level is undefined or can assume any threshold level: minor, major, critical, informational, and so on. This is particularly true for the MSC task. |
The text is the verbal part of the message as it appears on your screen or in the system log file.
Arguments are variable parts of the message (message arguments) and are enclosed in angle brackets (< >). Explanations of arguments are provided.
The message description explains the events that generated the message.
The action describes what you should do as a result of the event described in the message. In some cases (for example, informational messages), no action may be required. Actions for error messages (manual, warning, minor, major, and critical) may include steps that should be followed to identify and correct problems. Error actions may also describe how BAMS responds to the specified error condition.
The Alarm (ALM) task is responsible for handling all alarm and event messages that are written to the system log. This includes clearable alarms that are based on user-defined thresholds and are written to an alarm history file:
ALM100 ALM Version <version> has started.
The <version> argument represents the task version. This message indicates that the ALM task has started. This is an informational message. No action is necessary.
* ALM102 <routine> failed on error <UNIX error number>
The <routine> argument represents the routine name. The <UNIX error number> argument represents the UNIX error set by the system function. This message indicates that a system failure occurred. Check the UNIX error number for an explanation of this error.
** ALM103 <string>() failed on error <number>
The <number> represents the UNIX error number. This message indicates that the ALM task encountered a serious error condition. This is a major event. Examine the error number. Contact the Cisco Technical Assistance Center.
ALM104 get_qid (<name>) returned <error> (errno <UNIX error number>)
The <name> argument represents the QID. The <error> argument represents the returned error. The <UNIX error number> argument represents the UNIX error set by the system function. This message indicates that BAMS could not get the QID from the acecqid file.Verify that the $FILES environment variable is located in the acecqid file. Make sure that the read permissions are correct.
* ALM105 Mssget <function> failed (errno <UNIX error number>)
The <function> argument represents the function name. The <UNIX error number> argument represents the UNIX error set by the system function. This message indicates that the ALM task experienced an error. Check the UNIX error number for an explanation of this error.
* ALM106 Can not load <name>
The <name> argument represents the parameter name. This message indicates that the ALM task experienced an error.
* ALM108 Cannot access <string> (errno <UNIX error number>)
The <UNIX error number> argument represents the UNIX error set by the system function. This message indicates that the ALM task experienced an error. Check the UNIX error number for an explanation of this error.
ALM120 Alarm parameters have been updated
This message indicates that alarm parameters have been updated. This is an informational message. No action is necessary.
The MGR task controls BAMS operations and uses what is called generic messaging. This means that message numbers can be used by more than one software task (ACC001 and MGR001, for example). The text of the message is always be the same, although the arguments, if any, may be different. The system messages are numbered from 000 through 399 (not all numbers are used).
|
Note All system messages start with a date and time stamp (not shown below). The standard three-character task identifier is denoted by XXX in the generic messages that follow. |
XXX000 <task> Version <number> has started, pid <ID>.
The <task> argument represents the task mnemonic, <version> represents the task version number and <ID> represents the UNIX process ID. The task logs this message when it is started.
XXX002 Task completed, pid <process id>
The <process id> argument represents the UNIX process ID. The task has completed its job successfully.
(*,**, or *C) XXX003 Exiting with error code <error code>, pid <process id>
The <error code> argument represents the error code, and <process id> represents the UNIX process ID. The task is ending due to an error. Refer to a previous message by the same task in the syslog to get more detailed information.
(*,**,or *C) XXX004 Terminating on signal <signal code>, pid <process id>
The <signal code> argument represents the signal code, and <process id> represents the UNIX process ID. The task is ending abnormally due to a receipt of an unexpected signal. Refer to a previous message by the same task in the syslog to get more detailed information.
XXX005 Sending <message> to <task or task component>
The < message> argument represents the information or message sent, and <task> represents the task or task component recipient. The task sent information or a message to another task or task component.
XXX006 Waiting for <message> message
The <message> argument represents the message being waited for. The task is attempting to receive some information from another task or task component.
XXX007 Received <item>
The <item> argument represents the item or message received. The task has received some information from another task or task component.
XXX008 Processing <item to process>
The <item to process> argument represents the item to process, such as file name or message type name. Task is ready to process an item.
XXX009 Successfully processed <processed item>
The <processed item> argument represents the processed item. The task has successfully processed the indicated item.
XXX010 System state is <system state>
The <system state> argument represents the system state (for example, Running or Booting, or Active or Standby). For a redundant system, this message is displayed by the task, if its actions are dependent on the system state.
XXX011 SIG setting signal <signal number> handler to <signal handler name>
The <signal number> argument represents the signal number, and <signal handler name> represents the signal handler name. The task is setting the handler for the given signal.
XXX012 SHM Creating shared memory key= <shared memory key> size= <size of shared memory
requested>
The <shared memory key> argument represents the shared memory key, and <size of shared memory requested> represents the size of shared memory requested. The task allocates a shared memory as a mechanism for interprocess communication.
XXX013 SHM Attaching to shared memory key= <shared memory key> size= <size of shared
memory>
The <shared memory key> argument represents the shared memory key, and <size of shared memory> represents the size of shared memory. The task attaches to a region in shared memory.
XXX014 MSGQ Creating message queue key= <message queue key>
The <message queue key> argument represents the message queue key. The task allocates a message queue as a mechanism for interprocess communication.
XXX015 SEMA Creating semaphore key= <semaphore key>
The <semaphore key> argument represents the semaphore key. The task allocates a semaphore as a mechanism for interprocess communication.
XXX016 DIR Changing to <directory name>
The <directory name> argument represents the directory name. The task is setting its current work directory.
XXX017 Renaming <original file name> to <new file name>
The <original file name> argument represents the original file name, and <new file name> represents the new file name. The task renames (or move) a file, typically to mark it as processed.
XXX018 Connecting to <remote host address or name> / < port number or service name>
The <remote host address or name> argument represents the remote host address or name, and <port number or service name> represents the port number or service name. The task attempts to connect to the remote host (or server). If the task uses a TCP/IP socket and the second argument is supplied as a service name, the service must be registered in the /etc/services file. In addition, when the host name is used instead of an IP address, the host name must be registered in the /etc/hosts file.
XXX019 Connected to <remote host address or name> / <port number or service name>
The <remote host address or name> argument represents the remote host address or name, and <port number or service name> represents the port number or service name. The task has successfully connected to the named host. At this point, application-layer communication may continue.
XXX020 Disconnecting from <remote host address or name> / <port number or service name>
The <remote host address or name> argument represents the remote host address or name, and <port number or service name> represents the port number or service name. The task closes the connection to the remote server. To find out why the task is disconnecting, check previous messages in the syslog file.
XXX100 Timed out waiting for <description>.
The <description> argument represents the description of what the task was waiting for. The task logs a message when the attempt to receive some information from another task or task component has exceeded a certain time threshold.
(*, **, or *C) XXX101 Invalid command-line option, <unsupported character>.
The <unsupported character> argument represents the unsupported character command-line switch. The task was passed an unknown or unsupported command-line argument. The configuration file for the task contains an invalid option. To check all available options, invoke the task using the -h option, and check the contents of the configuration file.
(*, **, or C) XXX102 Unrecoverable failure.
The task cannot recover from an error. Analyze previous or following entries in the syslog file. These messages provide more information on the potential cause of the failure. Contact the Cisco Technical Assistance Center.
(*, **, *C) XXX103 SIG errno <error number> setting handler for signal <signal number>
The <error number> argument represents the UNIX error number, and <signal number> represents the signal number. The task failed to set the handler for the given signal. Contact the Cisco Technical Assistance Center if necessary.
(*, **, *C) XXX104 SYS errno <error number> on system() for <argument>
The <error number> argument represents the UNIX error number, and <argument> represents the description of the argument passed to the system() call. The task detected an error when passing a command to the UNIX shell. The shell may be unable to find and execute the specified command. Check if the command or script passed to the system call is valid. If it is a script, verify that the execute permissions are set. Another possible reason for a system call to fail is an excessive number of UNIX processes already executing. To see if this is the case, issue the ps -eaf | pg command.
(*, **, *C)XXX105 SYS errno <error number> on fork() for <description>
The <error number> argument represents the UNIX error number, and <description> indicates why the process is cloning itself. The task failed to clone itself. This may happen if the maximum number of processes in the system has been reached. To see if this is the case, issue the ps -eaf | pg command.
(*, **, *C)XXX106 ENV variable <name> undefined
The <name> argument represents the name of the undefined environment variable. A variable is undefined in the run-time environment of the task. Check the sym_defs file if there is no entry for the given environment variable. If there is an entry, check if the variable is exported.
(*, **, *C)XXX107 ENV variable <name> is undefined, using default value <default string>
The <name> argument represents the name of the undefined environment variable, and <default string> represents the default string to be used. A variable is undefined in the run-time environment of the task. The task is using a default string value.
(*, **, *C)XXX108 ENV variable <name> is undefined, using default value <default string>
The <name> argument represents the name of the undefined environment variable, and <default string> represents the default string to be used. A variable is undefined in the run-time environment of the task. The task is using a default numeric value.
(*, **, *C)XXX109 SHM errno <error number> code <return code> getting key for <name>
The <error number> argument represents the return code of the function that provides the mapping between shared memory names and the shared memory keys, <return code> represents the UNIX error number, and <name> represents the shared memory name.
The task cannot get the shared memory key value for the given shared memory name. Either the acecmid file is not in the files directory or the named shared memory is not defined in the acecmid file. Contact the Cisco Technical Assistance Center to update this file.
(*, **, *C)XXX110 SHM errno <error number> creating key=$ <memory key>
The <error number> argument represents the UNIX error number, and <memory key> represents the shared memory key. The task failed to create the shared memory with the given key. A shared memory with the same key may already exist.
(*, **, *C)XXX111 SHM errno <error number> attaching to key=$ <memory key>
The <error number> argument represents the UNIX error number, and <memory key> represents the shared memory key. The task failed to attach to the shared memory with the given key. The shared memory with the given key may not yet have been created or may have been removed.
(*, **, *C)XXX112 SHM chunk not defined for <memory chunk>
The <memory chunk> argument represents the name of the memory chunk that caused the lookup failure. The task failed to look up a memory chunk in the shared memory region. Check the configuration file in the files directory.
(*, **, *C)XXX113 SHM chunk is <assigned memory> bytes for <expected memory> Expecting
<chunk size>
The < assigned memory> argument represents the memory chunk size, <expected memory> represents the expected memory chunk size, and <chunk size> represents the memory chunk size in bytes. The expected memory chunk size of the task does not match the allocated chunk. Check the configuration file in the files directory.
(*, **, *C)XXX114 MSGQ errno <error number> code <return code> getting key for queue name
The <error number> argument represents the UNIX error number, <return code> represents the return code of the function that provides the mapping between the message queue names and message queue keys, and <queue name> represents the message queue name.
The task cannot get the message queue key value for the given message queue name. Either the acecqid file is not in the files directory or the named message queue is not defined in the acecqid file.
(*, **, *C)XXX115 MSGQ errno <error number> creating key=$ <queue key>
The <error number> argument represents the UNIX error number, and <queue key> represents the message queue key. The task cannot create a message queue with the given key. A message queue with the same key may already exist. Look in /CiscoBAMS/files/acecqid for duplicate key definitions. Contact the Cisco Technical Assistance Center to correct the configuration if duplicates are found.
(*, **, *C)XXX116 MSGQ errno <error number> code <return code> on sendlocal() key=$ <queue
key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of sendlocal(), and <queue key> represents the message queue key.
The task failed to send a message to a task on the same machine. The message queue with the given key may have been removed, or the system-imposed maximum number of pending messages may have been reached. From the UNIX prompt, issue the command ipcs -qob. Check if the queue with the given key still exists and if the total QNUM is less than 40.
(*, **, *C)XXX117 MSGQ errno <error number> code <return code> on sendremote() key=$<queue
key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of sendremote(), and <queue key> represents the message queue key.
The task failed to send a message to a task on a remote machine. The message queue for the task dealing with intermachine communication may have been removed, or the system-imposed maximum number of pending messages may have been reached. From the UNIX prompt, issue the command ipcs -qob. Check if the queue with the given key still exists and if the total QNUM is less than 40.
(*, **, *C)XXX118 MSGQ errno <error number> code <error number> on recvmsg() key=$<queue
key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of recvmsg(), and <queue key> represents the message queue key. The task failed to receive a message from a message queue with the given key. The message queue with the given key may have been removed, or the task may have been interrupted.
(*, **, *C)XXX119 SEMA errno <error number> code <return code> getting key for <semaphore
name>
The <error number> argument represents the UNIX error number, <return code> represents the return code of the function that provides the mapping between semaphore names and semaphore keys, and <semaphore name> represents the semaphore name. The task cannot get the semaphore key value for the given semaphore name. Either the acecsid file is not in the files directory or the named semaphore is not defined in the acecsid file.
(*, **, *C)XXX120 SEMA errno <error number> creating key=$<semaphore key>
The <error number> argument represents the UNIX error number, and <semaphore key> represents the semaphore key. The task cannot create the semaphore with the given key. A semaphore with the same key may already exist.
(*, **, *C)XXX121 FILE errno <error number> opening <name> for <file open>
The <error number> argument represents the UNIX error number, <name> represents the name of file, and <file open> represents the file open modifier (for example, create, read, append). The task failed to open the named file using the indicated file open operation.
(*, **, *C)XXX122 FILE errno <error number> reading <file name> size <total byte size>
The <error number> argument represents the UNIX error number, <file name> represents the file name or item being read, and <total byte size> represents the total byte size available to read. The task failed to read the requested number of bytes.
(*, **, *C)XXX123 FILE errno <error number> writing <file name> size <total byte size>
The <error number> argument represents the UNIX error number, <file name> represents the file name or item being written, and <total byte size> represents the total byte size available to write. The task failed to write requested number of bytes. Check if the disk is full and if the file exists.
(*, **, *C)XXX124 FILE errno <error number> seeking <file name> offset <offset> whence
<flag>.
The <error number> argument represents the UNIX error number, <file name> represents the file name or description of input file, <offset> represents the requested offset, and <flag> represents the seek flag (0, 1, or 2). The task failed to move the pointer on the named file.
(*, **, *C)XXX125 FILE fprintf() returned <return code>. Expecting <number>.
The <return code> argument represents the return code of fprintf(), and <number> represents the number of items requested. The task failed to write the requested number of items.
(*, **, *C)XXX126 FILE fscanf() returned <return code>. Expecting <number>
The <return code> argument represents the return code of fscanf(), and <number> represents the number of items requested. The task failed to read the requested number of items.
(*, **, *C)XXX127 FILE errno <error number> linking <file> to <name>
The <error number> argument represents the UNIX error number, <file> represents the file to link from, and <name> represents the name of new file link. The task failed to create a link to a file. This may happen when the first file does not exist.
(*, **, *C)XXX128 FILE errno <error number> unlinking <unlink>.
The <error number> argument represents the UNIX error number, and <unlink> represents the name of the file to unlink. The task failed to remove a file link. Check if the named file exists. If it does, check the permissions in the file.
(*, **, *C)XXX129 FILE errno <error number> renaming <rename> to <new name>
The <error number> argument represents the UNIX error number, <rename> represents the name file to rename, and <new name> represents the new name. The task failed to rename a file.
(*, **, *C)XXX130 DIR errno <error number> changing to <directory>.
The <error number> argument represents the UNIX error number, and <directory> represents the directory name. The task failed to set its working directory. Check if the directory exists and if the execute permissions are set.
(*, **, *C)XXX131 DIR errno <error number> opening <directory>.
The <error number> argument represents the UNIX error number, and <directory> represents the directory name. The task failed to open the named directory. Check if the directory exists and if the read permissions are set.
(*, **, *C)XXX132 DIR errno <error number> reading <error number>
The <error number> argument represents the UNIX error number, and <directory name> represents the directory name. The task failed to read an entry from the named directory. Check if the directory exists and if the read permissions are set.
(*, **, *C)XXX133 SCKT errno <error number> creating <protocol> socket for <socket>
The <error number> argument represents the UNIX error number, <protocol> represents the protocol (TCP or UDP), and <socket> represents the use of socket. The task failed to create an end point for communication (socket). This may happen if the task has opened too many sockets.
(*, **, *C)XXX134 SCKT errno <error number> connecting to <address>/<port number>
The <error number> argument represents the UNIX error number, <address> represents the server name or address, and <port number> represents the service name or port number (as a string).
The task failed to initiate a connection to a server process. This may be due to one of two things: the server name does not have an entry in the /etc/hosts file or the service name is not in the /etc/services file. If IP address and port number are used instead of names and the message still shows up, contact the Cisco Technical Assistance Center.
(*, **, *C)XXX135 SCKT errno <error number> binding socket <socket>
The <error number> argument represents the UNIX error number, and <socket> represents the socket descriptor. The task failed to link a name to a socket.
(*, **, *C)XXX136 SCKT errno <error number> listening on socket <socket>, qlength=<queue
length>
The <error number> argument represents the UNIX error number, <socket> represents the socket descriptor, and <queue length> represents the requested queue length. The task failed to listen for connections on a socket.
(*, **, *C)XXX137 SCKT errno <error number> accepting from socket=<socket>
The <error number> argument represents the UNIX error number, and <socket> represents the socket ID. The task failed to accept a connection from a socket.
(*, **, *C)XXX138 SCKT errno <error number> reading <description> size <number>
The <error number> argument represents the UNIX error number, <description> represents the description of data to read, and <number> represents the number of bytes to read. The task encountered an error while reading data from a socket.
(*, **, *C)XXX139 SCKT errno <error number> writing <description> size <number>
The <error number> argument represents the UNIX error number, <description> represents the description of data to write, and <number> represents the number of bytes to write. The task encountered an error while writing data to a socket.
(*, **, *C)XXX140 FILE errno <error number> getting file stat for <name>
The <error number> argument represents the UNIX error number, and <name> represents the name or description of file. The task failed to get file statistics. Check if the file exists.
(*, **, *C)XXX141 MSGQ errno <error number> code <return code> deleting key=$<queue key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of the routine to delete the message queue, and <queue key> represents the message queue key. The task failed to delete the message queue with the given key, which may have been deleted manually or by another task.
(*, **, *C)XXX142 SHM errno <error number> code <return code> deleting key=$< queue key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of routine to delete the shared memory, and <queue key> represents the message queue key. The task failed to delete the shared memory with the given key, which may have been deleted manually or by another task.
(*, **, *C)XXX143 SHM errno <error number> attaching to <name> shared memory
The <error number> argument represents the UNIX error code, and <name> represents the task name of shared memory owner. Use this alarm message only in cases where the task does not explicitly acquire the shared memory ID through get_mid().
The task failed to attach to the shared memory owned by the given task. The shared memory may not have been created, or it may have been deleted by the owning process. Check if the shared memory owner is executing by issuing the UNIX command ps -eaf | grep <task>, where <task> is the owner of the shared memory.
(*, **, *C)XXX200 Timed out waiting for <task>
The <task> argument represents the description of what the task was waiting for. The task logs the message when the attempt to receive some information from another task or task component has exceeded a certain time threshold.
(*, **, *C)XXX201 Invalid command-line option, <switch>
The <switch> argument represents the unsupported character command-line switch. The task was passed an unknown or unsupported command-line argument. The configuration file for the task contains an invalid option. To check all available options, invoke the task using the -h option and check the contents of the configuration file.
(*, **, *C)XXX202 Unrecoverable failure
The task cannot recover from an error. Previous or following entries in the log file provide more information on the potential cause of the failure.
(*, **, *C)XXX203 SIG errno <error number> setting handler for signal <signal>
The <error number> argument represents the UNIX error number, and <signal> represents the signal number. The task failed to set the handler for the given signal. Contact the Cisco Technical Assistance Center if necessary.
(*, **, *C)XXX204 SYS errno <error number> on system() for <argument>
The <error number> argument represents the UNIX error number, and <argument> represents the description of the argument passed to the system() call.
The task detected an error when passing a command to the UNIX shell. The shell may be unable to find and execute the specified command. Check if the command or script passed to the system call is valid. If it is a script, verify that the execute permissions are set. Another possible reason why a system() call would fail is due to an excessive number of UNIX processes already executing. To see if this is the case, issue the command ps -eaf | pg.
(*, **, *C)XXX205 SYS errno <error number> on fork() for <description>
The <error number> argument represents the UNIX error number, and <description> represents the description of why the process is cloning itself. The task failed to clone itself. This may happen when the maximum number of processes in the system has been reached. To see if this is the case, issue the command ps -eaf | pg.
(*, **, *C)XXX206 ENV variable <name> undefined
The <name> argument represents the name of the undefined environment variable. A variable is undefined in the run-time environment of the task. Check the sym_defs file to see if there is an entry for the given environment variable. If there is an entry, check if the variable is exported.
(*, **, *C)XXX207 ENV variable <name> is undefined, using default value <default string>
The <name> argument represents the name of the undefined environment variable, and <default string> represents the default string to be used. A variable is undefined in the run-time environment of the task. The task uses a default string value.
(*, **, *C)XXX208 ENV variable <variable> is undefined, using default value <default
string>
The <variable> argument represents the name of the undefined environment variable, and <default string> represents the default string to be used. A variable is undefined in the run-time environment of the task. The task is using a default numeric value.
(*, **, *C)XXX209 SHM errno <error number> code <return code> getting key for <memory
name>
The <error number> represents the UNIX error number, <return code> represents the return code of the function that provides the mapping between shared memory names and shared memory keys, and <memory name> represents the shared memory name.
The task cannot get the shared memory key value for the given shared memory name. Either the acecmid file is not in the files directory or the named shared memory is not defined in the acecmid file. Contact the Cisco Technical Assistance Center if necessary.
(*, **, *C)XXX210 SHM errno <error number> creating key=$<memory key>
The <error number> argument represents the UNIX error number, and <memory key> represents the shared memory key. The task failed to create the shared memory with the given key. A shared memory with the same key may already exist.
(*, **, *C)XXX211 SHM errno <error number> attaching to key=$<memory key>
The <error number> argument represents the UNIX error number, and <memory key> represents the shared memory key. The task failed to attach to the shared memory with the given key. The shared memory with the given key may not yet have been created or may have been removed.
(*, **, *C)XXX212 SHM chunk not defined for <lookup failure>
The <lookup failure> argument represents the name of memory chunk that caused the lookup failure. The task failed to look up a memory chunk in the shared memory region. Check the configuration file in the files directory.
(*, **, *C)XXX213 SHM chunk is <assigned> bytes for <name>. Expecting <size> bytes
The <assigned> argument represents the assigned memory chunk size, <name> represents the memory chunk name, and <size> represents the expected memory chunk size. The expected memory chunk size of the task does not match the allocated chunk. Check the configuration file in the files directory.
(*, **, *C)XXX214 MSGQ errno <error number> code <return code> getting key for <queue
name>
The <error number> argument represents the UNIX error number, <return code> represents the return code of the function that provides the mapping between message queue names and message queue keys, and <queue name> represents the message queue name.
The task cannot get the message queue key value for the given message queue name. Either the acecqid file is not in the files directory or the named message queue is not defined in the acecqid file.
(*, **, *C)XXX215 MSGQ errno <error number> creating key=$<queue key>
The <error number> argument represents the UNIX error number, and <queue key> represents the message queue key. The task cannot create a message queue with the given key. A message queue with the same key may already exist. Look in at the acecqid file found in the /CiscoBAMS/files directory for duplicate key definitions. Contact the Cisco Technical Assistance Center to correct the configuration if duplicates are found.
(*, **, *C)XXX216 MSGQ errno <error number> code <return code> on sendlocal() key=$<queue
key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of sendlocal(), and <queue key> represents the message queue key.
The task failed to send a message to a task on the same unit. The message queue with the given key may have been removed, or the system-imposed maximum number of pending messages may have been reached. From the UNIX prompt, issue the command ipcs -qob. Check if the queue with the given key still exists and if the total QNUM is less than 40.
(*, **, *C)XXX217 MSGQ errno <error number> code <return code> on sendremote() key=$<queue
key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of sendremote(), and <queue key> represents the message queue key.
The task failed to send a message to a task on a remote unit. The message queue for the task dealing with inter-unit communication may have been removed, or the system-imposed maximum number of pending messages may have been reached. From the UNIX prompt, issue the command ipcs -qob and check that the queue with the given key still exists and that the total QNUM is less than 40.
(*, **, *C)XXX218 MSGQ errno <error number> code <return code> on recvmsg() key=$<queue
key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of recvmsg(), and <queue key> represents the message queue key. The task failed to receive a message from a message queue with the given key. The message queue with the given key may have been removed, or the task may have been interrupted.
(*, **, *C)XXX219 SEMA errno <error number> code <return code> getting key for <semaphore
name>
The <error number> argument represents the UNIX error number, <return code> represents the return code of the function that provides the mapping between semaphore names and semaphore keys, and <semaphore name> represents the semaphore name.
The task cannot get the semaphore key value for the given semaphore name. Either the acecsid file is not in the files directory or the named semaphore is not defined in the acecsid file.
(*, **, *C)XXX220 SEMA errno <error number> creating key=$<semaphore>
The <error number> argument represents the UNIX error number, and <semaphore> represents the semaphore key. The task cannot create the semaphore with the given key. A semaphore with the same key may already exist.
(*, **, *C)XXX221 FILE errno <error number> opening <name> for <file>
The <error number> argument represents the UNIX error number, <name> represents the name of the file, and <file> represents the file open modifier (for example, create, read, append). The task failed to open the named file using the indicated file open operation.
(*, **, *C)XXX222 FILE errno <error number> reading <file name> size <byte size>
The <error number> argument represents the UNIX error number, <file name> represents the file name or item being read, and <byte size> represents the total byte size to read. The task failed to read the requested number of bytes.
(*, **, *C)XXX223 FILE errno <error number> writing <byte size> size <file name>
The <error number> argument represents the UNIX error number, <byte size> represents the total byte size to write, and <file name> represents the file name or item being written. The task failed to write the requested number of bytes. Check if the disk is full and if the file exists.
(*, **, *C)XXX224 FILE errno <error number> seeking <file name> offset <offset> whence
<flag>
The <error number> argument represents the UNIX error number, <file name> represents the file name or description of the input file, <offset> represents the requested offset, and <flag> represents the seek flag (0, 1, or 2). The task failed to move the pointer on the named file.
(*, **, *C)XXX225 FILE fprintf() returned <return code>. Expecting <number>
The <return code> argument represents the return code of fprintf(), and <number> represents the number of items requested. The task failed to write the requested number of items.
(*, **, *C)XXX226 FILE fscanf() returned <return code>. Expecting <number>
The <return code> argument represents the return code of fscanf(), and <number> represents the number of items requested. The task failed to read the requested number of items.
(*, **, *C)XXX227 FILE errno <error number> linking <file> to <new file>
The <error number> argument represents the UNIX error number, <file> represents the file to link from, and <new file> represents the name of new file link. The task failed to create a link to a file. This may happen when the first file does not exist.
(*, **, *C)XXX228 FILE errno <error number> unlinking <name>
The <error number> argument represents the UNIX error number, and <name> represents the name of file to unlink. The task failed to remove a file link. Check if the named file exists. If it does, check the permissions in the file.
(*, **, *C)XXX229 FILE errno <error number> renaming <name> to <new name>
The <error number> argument represents the UNIX error number, <name> represents the original file name, and <new name> represents the new name. The task failed to rename a file.
(*, **, *C)XXX230 DIR errno <error number> changing to <directory name>
The <error number> argument represents the UNIX error number, and <directory name> represents the directory name. The task failed to set its working directory. Check if the directory exists and if the execute permissions are set.
(*, **, *C)XXX231 DIR errno <error number> opening <directory name>
The <error number> argument represents the UNIX error number, and <directory name> represents the directory name. The task failed to open the named directory. Check if the directory exists and if the read permissions are set.
(*, **, *C)XXX232 DIR errno <error number> reading <directory name>
The <error number> argument represents the UNIX error number, and <directory name> represents the directory name. The task failed to read an entry from the named directory. Check if the directory exists and if the read permissions are set.
(*, **, *C)XXX233 SCKT errno <error number> creating <protocol> socket for <use>
The <error number> argument represents the UNIX error number, <protocol> represents the protocol (TCP or UDP), and <use> represents the use of socket. The task failed to create an end point for communication (socket). This may happen if the task has opened too many sockets.
(*, **, *C)XXX234 SCKT errno <error number> connecting to <name>/<string>
The <error number> argument represents the UNIX error number, <name> represents the server name or address, and <string> represents the service name or port number (as a string). The task failed to initiate a connection to a server process. Either the server name does not have an entry in the /etc/hosts file or the service name is not in the /etc/services file. If IP address and port number are used instead of names and the message still shows up, contact the Cisco Technical Assistance Center.
(*, **, *C)XXX235 SCKT errno <error number> binding socket <descriptor>
The <error number> argument represents the UNIX error number, and <descriptor> represents the socket descriptor. The task failed to bind a name to a socket.
(*, **, *C)XXX236 SCKT errno <error number> listening on socket <descriptor>,
qlength=<queue length>
The <error number> argument represents the UNIX error number, <descriptor> represents the socket descriptor, and <queue length> represents the requested queue length. The ask failed to listen for connections on a socket.
(*, **, *C)XXX237 SCKT errno <error number> accepting from socket=<id>
The <error number> argument represents the UNIX error number, and <id> represents the socket ID. The task failed to accept a connection from a socket.
(*, **, *C)XXX238 SCKT errno <error number> reading <data> size <bytes>
The <error number> argument represents the UNIX error number, <data> represents the description of data to read, and <bytes> represents the number of bytes to read. The task encountered an error while reading data from a socket.
(*, **, *C)XXX239 SCKT errno <error number> writing <data> size <bytes>
The <error number> argument represents the UNIX error number, <data> represents the description of data to write, and <bytes> represents the number of bytes to write. The task encountered an error while writing data to a socket.
(*, **, *C)XXX240 FILE errno <error number> getting file stat for <description>
The <error number> argument represents the UNIX error number, and <description> represents the name or description of file. The task failed to get file statistics. Check if the file exists.
(*, **, *C)XXX241 MSGQ errno <error number> code <return code> deleting key=$<queue key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of the routine to delete the message queue, and <queue key> represents the message queue key. The task failed to delete the message queue with the given key, which may have been deleted manually or by another task.
(*, **, *C)XXX242 (SHM errno <error number> code <return code> deleting key=$<queue key>
The <error number> argument represents the UNIX error number, <return code> represents the return code of the routine to delete the shared memory, and <queue key> represents the message queue key. The task failed to delete the shared memory with the given key, which may have been deleted manually or by another task.
(*, **, *C)XXX243 SHM errno <error code> attaching to <task name> shared memory
The <error code> argument represents the UNIX error code, and <task name> represents the task name of shared memory owner.
The task failed to attach to the shared memory owned by the given task. The shared memory may not have been created or may have been deleted by the owning process. Check if the shared memory owner is executing by issuing the UNIX command ps -eaf | grep <task>, where <task> is the owner of the shared memory.
(*, **, *C)XXX244 SYS errno <error code> on UNIX system call <call>
The <error code> represents the UNIX error code, and <call> represents the system call name. The task encountered an error during a UNIX system call.
The Manager (MGR) task error messages are numbered from 400 through 899 (not all numbers are used). The specific tasks use the same range of numbers, but the text of the message is different for each task.
MGR500 Spawning <task>
The <task> argument represents the task name. The MGR task is responsible for managing the BAMS application software. The MGR task starts and stops the tasks. This informational message indicates that a task is being started.
MGR501 Sending <signal number> to <task>
The <signal number> argument represents the signal number, and <task> represents the task name. Some communication between UNIX tasks is by signal number. This message indicates that a signal has been sent to a UNIX task.
MGR502 Attempting a restart
This message indicates that the MGR task is attempting to restart the system. The startup messages that follow this message are displayed and are logged in the syslog file.
MGR503 Keepalive internal passed
Keep alive is a security feature that monitors system activity when you log on to the system as an administrator or operator. If control session activity is idle for more than a desired amount of time, the application logs the user out. This message indicates that the keep alive interval has passed.
MGR504 Task <name> will be restarted
The <name> argument represents the task name. The MGR is restarting the displayed task.
MGR505 Invoking task <name>
The <name> argument represents the task name. The MGR is starting the displayed task.
* MGR600 Function <name> failed, code <rc>, errno:<UNIX error number>
The <name> argument represents the function name, <rc> represents the return code, and <UNIX error number> represents the UNIX error number. The displayed function returned an unexpected return code.
* MGR601 Too many options for <process>
The <process> represents the process name. This message indicates that too many optional parameters are passed to a process listed in the proglist file. The proglist file contains the names of configuration files specific to each task.
Verify the parameters in the configuration file of the offending task. If the configuration file has been modified, remove some of the options within the configuration file or restore the original configuration file.
** MGR700 Too few parameters <total>/<expected> on line <number> of proglist
The <total> argument represents the number of parameters, <expected> represents the number of expected parameters, and <number> represents the line number in the file. The proglist file has an incorrect number of parameters. Contact the Cisco Technical Assistance Center.
** MGR800 Failed spawning <name>
The <name> argument represents the task name. This message indicates that the MGR task is unable to start the displayed task. This message can be caused by a combination of hardware and software problems.
Restart the application software and monitor the system log for the same occurrence. If the problem persists, restart the operating system. If the problem is still present, reinstall the application software.
*C MGR801 Task <name> has died.
The <name> argument represents the task name. This message indicates that the specified task has stopped responding to the system. The MGR task automatically attempts a restart of the indicated task. Verify the permissions and ownerships on the task that has died. Restart the application and monitor the system log to see if the error persists. If MGR is unable to restart the task, you may need to reinstallation the software.
|
Note This alarm is cleared after the error alarm condition is removed. |
*C MGR802 Manager shutting down the application
This message indicates that a task has exited due to the receipt of the specified UNIX signal. The application has been terminated with a software interrupt. A signal 15 would indicate that the system received the stop command. A signal 11 would indicate that a segmentation violation occurred. The MGR task attempts a restart of the application. The MGR task attempts a restart of the application for signals other than signal 15. If the MGR task is unable to restart the application, a UNIX shutdown may be necessary. This error can be associated with either a hardware and software failure.
*C MGR803 Received unexpected signal number <number>. Exiting
The <number> argument represents the signal number. This error message indicates that the task has exited due to the receipt of the specified UNIX signal. The MGR task should reinitialize the system automatically. Monitor the syslog file during the next hour. If the error message reoccurs, reinstall the software.
*C MGR804 Disk full. Must be cleaned up manually
The system has a full data directory and the Mass Storage Control task is unable to effect an automatic system cleanup. This type of error can occur if the disk thresholds are set too high.
The /CiscoBAMS/data directory requires clean-up. Change to the /CiscoBAMS/data directory and remove older data files. The Mass Storage Control parameters should be verified and changed, as necessary, to allow for the following conditions:
The ACC task on BAMS is involved in the accumulation of peg counts for measurements.
ACC000 <name> version <number1> has started, pid <number2>
The <name> argument represents the task name. The <number1> argument represents the task version. The <number2> argument represents the process ID number. This message indicates that the ACC task has started. This is an informational message. No action is necessary.
ACC001 <name> terminating with code <errno>
The <name> argument represents the task name. The <errno> argument represents the UNIX error number set by the system function. This message indicates that the ACC task has been ended. See the error number to determine the reason for the error.
ACC002 <name> terminating with signal number <number>
The <name> argument represents the task name. The <number> argument represents the signal number. This message indicates that the ACC task has been ended. See the signal number to determine the reason for the error.
ACC003 <name> terminating normally
The <name> argument represents the task name. This message indicates that the ACC task is ending normally. This is an informational message. No action is necessary.
ACC004 Processing file <name>
The <name> argument represents the filename. This message indicates that the ACC task is processing the displayed file. This is an informational message. No action is necessary.
ACC005 File <name> processed
The <name> argument represents the filename. This message indicates that the ACC task processed the displayed file. This is an informational message. No action is necessary.
ACC010 <number> calls processed
The <number> argument represents the number of processed calls. This message indicates the number of call records the ACC task has processed. This is an informational message. No action is necessary.
* ACC019 No flat files to process. Retry in <number> seconds
The <number> argument represents the number of seconds. This message indicates that the ACC task has found no data files to process and is pausing for a period of time before attempting to process additional files. If no *, **, or *C is displayed, this message is displayed as an informational message. No action is necessary.
ACC022 Processed call set in <number> seconds
The <number> argument represents the number of seconds. This message indicates the elapsed time to process a single call set (data file). This is an informational message. No action is necessary.
ACC023 <name>: User time=<time1> sec, CPU time=<time2> sec
The <name> argument represents the process name. The <time1> argument represents the CPU time used while executing instructions in user space. The <time2> argument represents the CPU time used while executing instructions in system space. This alarm message indicates the user and CPU time used for processing enclosure files. This is an informational message. No action is necessary.
* ACC101 File error: <name> on <filename> (<errno>)
The <name> argument represents the name of the failed system call. The <filename> argument represents the file name. The <errno> argument represents the UNIX error number set by the system function. This message indicates that the ACC task encountered an error when performing a system call operation on the specified file. See the UNIX error number for more information.
*C ACC102 File I/O error: <name> on <filename>, requested: <number1>, got: <number2>
(<errno>)
The <name> argument represents the name of the failed system call. The <filename> argument represents the file name. The <number1> argument represents the amount of requested bytes. The <number2> argument represents the amount of received bytes. The <errno> argument represents the UNIX error number set by the system function. This message indicates that the ACC task encountered an error when performing a file I/O operation. Contact the Cisco Technical Assistance Center.
W ACC204 Duplicate VSCid/Trunk Group Key <vscid>/<trunk group> IC:<carrier id>
The <vscid> argument represents the Cisco MGC identifier. The <trunk group> argument represents the trunk group. The <carrier id> argument represents the carrier identifier. An error occurred adding the vscid/trunk group key. Contact the Cisco Technical Assistance Center.
** ACC206 Undefined environment variable <varname>
The <varname> argument represents the variable name. This message indicates that an expected environment variable has not been defined. Try logging out and logging back in. If this problem persists, verify that the specified environment variable is defined in /CiscoBAMS/bin/sym_defs. If it is missing, contact the Cisco Technical Assistance Center for directions on how to proceed.
** ACC207 Function <name> failed <errno>
The <name> argument represents the name of the failed function. The <errno> argument represents the UNIX error number set by the system function. This message indicates that an unexpected function failed. Contact the Cisco Technical Assistance Center.
*C ACC210 The EOF marker missing for the file <file name>
The <file name> argument represents the file name. This message indicates a missing end-of-file marker in the displayed file. Contact the Cisco Technical Assistance Center.
* ACC221 Old call set received <id> current <interval string>
The <id> argument represents a new call set, and <interval string> represents the current call set. This message appears when an older call set than the current one is received. Contact the Cisco Technical Assistance Center.
* ACC222 Missing call set expected <next interval string> received <call set id>
The <next interval string> argument represents a new call set, and <call set id> represents the current call set. This message appears when a time gap has been detected in the ACC input stream. Contact the Cisco Technical Assistance Center.
* ACC223 Can't load interval value from check point file
This message appears when an error is detected reading the checkpoint file. Contact the Cisco Technical Assistance Center.
* ACC224 Memory allocation failed requested by <function name>
The <function name> argument represents the name of the function requesting memory. Contact the Cisco Technical Assistance Center.This message appears when memory is allocated and none is returned.
ACC225 No Checkpoint file to load
This message appears when ACC task starts and no checkpoint file is found. This is an informational message. No action is necessary.
ACC226 Check point loaded, last interval was <current interval string>
The <current interval string> argument represents the current interval string loaded from the checkpoint. This message appears when ACC task starts and the checkpoint file is loaded. This is an informational message. No action is necessary.
* ACC227 <vscid>:<count direction> <description>, TG <trunk group> <counter value>
<condition> <threshold value>
The <vscid> argument represents the identifier of the Cisco MGC, <count direction> represents the direction of the count, <description> is a description, <trunk group> represents the trunk group, <counter value> represents the counter value, <condition> represents the threshold crossing condition, and <threshold value> represents the value of the threshold. This message appears when a counter passes a user-determined threshold test or clears. To clear this alarm, a matching text message must be provided because multiple ACC227 alarms may be active (each with a different message).
ACC228 <vscid>:<count direction> <description>, TG <trunk group number> contains an
invalid condition
The <vscid> argument represents the identifier of the Cisco MGC, <count direction> represents the direction of the count, <description> is a description, and <trunk group number> represents the trunk group number. This message appears when a threshold is tested and the condition (<=>) is an unknown test. This is an informational message. No further action is necessary.
* ACC230 Control file error: <string>
The <string> argument represents a string from ai_strerror(). This message displays errors from calls to the Web API. Contact the Cisco Technical Assistance Center.
* ACC231 Threshold file error <key> <threshold name> <value> <text>
The <key> argument represents the vscid/tg, <threshold name> represents the name of the threshold (for example, "ANSWERED"), <value> represents the value in error, and <text> represents a description of the error condition. This message appears when the threshold file contains an incorrect value. Contact the Cisco Technical Assistance Center.
* ACC232 Multiple Global thresholds found
On each new call set, ACC reloads the threshold table if the file contains more than one global threshold record that this alarm displays. Contact the Cisco Technical Assistance Center.
* ACC233 Out of table Space
If ACC attempts to insert a new node in a tree and no space is available, this alarm is displayed. Contact the Cisco Technical Assistance Center.
* ACC234 Known node can't be found deleting
If ACC attempts to delete a node in a tree and delete returns null (not found), this alarm is displayed. Contact the Cisco Technical Assistance Center.
The Augmentation (AUG) task controls the augmentation of data through the use of lookup tables. Depending on the type of data augmentation that occurs, messages are written to the syslog with an AGB (Augmented BAF) or AGS (Augmented Statistics) task identifier.
AGB000 <task> version <version> has started <pid>
The <task> argument represent the task name, <version> represents the task version, and <pid> represents the process identifier. This message indicates that the AUG task has started. This is an informational message. No action is necessary.
AGB001 <task> terminating with <code> <pid>
The <task> argument represents the task name, <code> represents UNIX error code, and <pid> represents the process identifier. This message indicates that the AUG task has ended abnormally. See the UNIX error code for an explanation of the problem.
AGB002 <name> terminating with signal <number1>, pid <number2>
The <name> argument represents the task name, <number1> represents the UNIX signal number, and <number2> represents the UNIX process identifier. This message indicates that the displayed signal ended the task. See the UNIX signal number for an explanation of the problem.
AGB003 <name> terminating normally, pid <number>
The <name> argument identifies the task name, and <number> identifies the process ID number of the task. This message indicates that the task terminated normally. This is an informational message. No action is necessary.
AGB004 Processing file <name>
The <name> argument represents the filename. This message indicates that the AUG task is processing the displayed file. This is an informational message. No action is necessary.
AGB009 Received system signal <signal name>.
The <signal name> argument represents the name of the UNIX signal. The AUG task received a system signal. This is an informational message. No action is necessary.
AGB010 Processed <file name>, total: <number> good: <number> sunerr: <number> semerr
<number> lk uperr <number>
The <file name> argument represents the name of the processed file, and number> represents the total number of call records, the number of good call records, the number of call records with syntax errors, the number of call records with semantic errors, and the number of call records with error lookups, respectively. This message provides summary information of call records being processed. This is an informational message No action is necessary.
AGB019 No flat files to process. Retry in <number> seconds.
The <number> argument represents the time delay in seconds. There are no data files to process. The task waits and retries in the specified number of seconds. This is an informational message. No action is necessary.
AGB024 Creating <name> table
The <name> argument represents the lookup table name, that is, NPA_NXX, RATE_EXC, RATE_TYPE, TRUNK_GRP. The named lookup table is created and loaded into memory. This is an informational message. No action is necessary.
AGB025 Refreshing <name> table.
The <name> argument represents the lookup table name. The lookup table is reloaded. This is an informational message. No action is necessary.
* AGB100 System call failure: <name> <errno>
The <name> argument represents the name of failed system call, and <errno> represents the UNIX error number. This message indicates that the AUG task encountered an error when requesting the displayed system call. Look up UNIX error number. Contact the Cisco Technical Assistance Center.
* AGB101 File error: <call> on <file> (<code>)
The <call> argument represents the name of the failed system call, <file> represents the name of file being operated on, and <code> is the UNIX error number. This message indicates an error when performing the displayed system call operation. Look up the UNIX error number. A software-related problem is indicated. Contact the Cisco Technical Assistance Center.
*C AUG102 File I/O error: <call> on <file>, requested <number1>, got <number2>
The <call> argument represents the failed system call, <file> represents the name of the file being operated on, <number1> represents the number of bytes requested, and <number2> represents number of bytes received. This message indicates an error when performing the displayed I/O file operation. Check if the disk space is full or not. If disk space is not full, a software-related problem is indicated. Contact the Cisco Technical Assistance Center.
* AGB104 Cannot find file <name> to process
The <name> argument represents the file name. This message indicates that the task is expected to reprocess the named file but did not find it. Contact the Cisco Technical Assistance Center.
* AGB201 Undefined environment variable <name>
The <name> argument represents the name of the undefined environment variable. This message indicates an environment variable is not defined. Check the sym_defs file. Contact the Cisco Technical Assistance Center.
* AGB202 <index> - Invalid <field>: <value>
The <index> argument represents the call record index, <field> represents the field name in the call record, and <value> indicates the value of the field. This message indicates that the AUG task detected and invalid field value in the call record. The input data has an invalid call reference ID. Check the Cisco MGC raw data and make sure the call reference ID has the correct format. Contact the Cisco Technical Assistance Center.
* AGB203 <index> - fail <function> lookup of <field>: <value>
The <index> argument represents the call record index, <function> represents the function name of the table lookup, <field> represents the field name in the call record, and <value> represents the value of the field being looked up. This message indicates a failed table lookup. Make sure the specific value exists in the table. Contact the Cisco Technical Assistance Center.
* AGB210 CTL file: <name> error: <ai string error>
The <name> argument represents the function name, and <ai string error> represents the error string. This message indicates an error returned by a control file function. Make sure the CTL file exists in the specified directory. Check the existence of the CTL file (*.CTL) and verify the structure of the control file (*.CFDT). If the CFDT file is corrupt, copy the default CFDT file. Contact the Cisco Technical Assistance Center.
* AGB211 CTL file BAF value error: <value>
The <value> argument represents a bad value. This message indicates that the contents of the BAF field in the control file is not 0 or 1. Verify sysparm configurations. Make sure the BAF output is set to 0 (disabled) or 1 (enabled) parameters. Contact the Cisco Technical Assistance Center.
* AGB232 #<index> Fail <function> lookup of<field1>:<value1> <field2>:<value2>
<field3>:<value3>
The <index> argument represents the call record index, <function> represents the function name of the table lookup, <field1> represents the first field name in the call record, <value1> represents the value of the first field, <field 2> represents the second field name in the call record, <value2> represents the value of the second field, <field3> represents the third field name in the call record, and <value3> represents the value of the third field. This message indicates a failed table lookup at the named locations. The system tried to match 3 field values to the lookup table. Verify the table configuration file and make sure the field values exist in that configuration file. Contact the Cisco Technical Assistance Center.
* AGB233 #<index> Fail <function> lookup of <field>:<value>
The <index> argument represents the call record index, <function> represents the function name, <field> represents the field name of the call record, and <value> represents the value of the field being looked up. This message indicates a failed table lookup of this field. Verify the input raw file used 1 field value to match to the lookup table. Contact the Cisco Technical Assistance Center.
* AGB234 #<index> - Invalid block: <field name>
The <index> argument represents the record index, and <field name> represents field names and values. This message indicates that an invalid block format was encountered when reading blocks from the table file. For example, the system expects a six-digit value for NPANXX but it received only 5 digits. Verify the CTL file field value. Make sure you enter the required value. Contact the Cisco Technical Assistance Center.
* AGB235 #<number> records failed trunk group lookup for file
cor_agcdr_<timestamp>_<sequencenumber>.bin
The <number argument> represents the number of records that failed the trunk group lookup, the <timestamp> argument represents the date and time and the <sequence number> argument represents the file sequence number. This minor alarm indicates the trunk group table is not correctly or fully populated. This error precludes these records from being processed by the measurements function. Fix the trunk group table. Refer to the AUG*log files in the opt/CiscoBAMS/files directory. This file specifies which trunk group should be modified so that these configuration failures do not occur.
AGB236 <number> record(s) default to interlata due to absent NPANXX for file
The <number> argument represents the record number that defaulted to the INTERLATA rating type due to this NPANXX combination not being in the NPANXX tables. This message indicates that the AUG task has started. This is an informational message. No action is necessary.
The Augmentation (AUG) task controls the augmentation of data through the use of lookup tables. Depending on the type of data augmentation that occurs, messages are written to the syslog with an AGB (Augmented BAF) or AGS (Augmented Statistics) task identifier.
AGS000 <task> version <version> has started <pid>
The <task> arguments represent the task name, and <version> represents the task version. The <pid> argument represents the process identifier. This message indicates that the AUG task has started. This is an informational message. No action is necessary.
AGS001 <task> terminating with <code> <pid>
The <task> argument represent the task name, <code> represents the UNIX error code, and <pid> represents the process identifier. This message indicates that the AUG task has ended abnormally. See the UNIX error code for an explanation of the problem.
AGS002 <name> terminating with signal <number1>, pid <number2>
The <name> argument represents the task name, <number1> represents the UNIX signal number, and <number2> represents the process identifier. This message indicates that the displayed signal terminated the task. See the UNIX signal number for an explanation of the problem.
AGS003 <name> terminating normally, pid <number>
The <name> argument represents the task name, and <number> represents the process identifier. This message indicates that the task terminated normally. This is an informational message. No action is necessary.
AGS004 Processing file <name>
The <name> argument represents the file name. This message indicates that the AUG task is processing the displayed file. This is an informational message. No action is necessary.
AGS009 Received system signal <signal name>.
The <signal name> argument represents the UNIX signal name. The AUG task received a system signal. This is an informational message. No action is necessary.
AGS010 Processed <file name>, total: <number> good: <number> sunerr: <number> semerr
<number> lk uperr <number>
The <file name> argument represents the name of the processed file, <number> represents the total number of call records, number of good call records, number of call records with syntax errors, number of call records with semantic errors, and number of call records with error lookups, respectively. This message displays summary information of call records being processed. This is an informational message. No action is necessary.
AGS019 No flat files to process. Retry in <number> seconds.
The <number> argument represents a time delay in seconds. There are no data files to process. The task waits and retries in the specified number of seconds. This is an informational message. No action is necessary.
AGS024 Creating <name> table
The <name> argument represents the lookup table name; for example, NPA_NXX, RATE_EXC, RATE_TYPE, TRUNK_GRP. The named lookup table is created and loaded into memory. This is an informational message. No action is necessary.
AGS025 Refreshing <name> table.
The <name> argument represents the lookup table name. The lookup table is reloaded. This is an informational message. No action is necessary.
* AGS100 System call failure: <name> <errno>
The <name> argument represents the name of failed system call, and <errno> represents the UNIX error number. This message indicates that the AUG task encountered an error when requesting the displayed system call. Look up the UNIX error number. A software-related problem is indicated. Contact the Cisco Technical Assistance Center.
* AGS101 File error: <call> on <file> (<code>)
The <call> argument represents the name of the failed system call, <file> represents the name of file being operated on, and <code> represents the UNIX error number. This message indicates an error when performing the displayed system call operation. Look up the UNIX error number. A software-related problem is indicated. Contact the Cisco Technical Assistance Center.
*C AGS102 File I/O error: <call> on <file>, requested <number1>, got <number2>
The <call> argument represents the failed system call, <file> represents the name of the file being operated on, <number1> represents the number of bytes requested, and <number2> represents the number of bytes received. This message indicates an error when performing the displayed I/O file operation. Check if the disk space is full or not. If disk space is not full, a software-related problem is indicated. Contact the Cisco Technical Assistance Center.
* AGS104 Cannot find file <name> to process
The <name> argument represents the file name. This message indicates that the task is expected to reprocess the file but did not find it. Contact the Cisco Technical Assistance Center.
* AGS201 Undefined environment variable <name>
The <name> argument represents the name of the undefined environment variable. This message indicates an environment variable is not defined. Check the sym_defs file. Contact the Cisco Technical Assistance Center.
* AGS202 <index> - Invalid <field>: <value>
The <index> argument represents the call record index, <field> represents the field name in the call record, and <value> represents the field value. This message indicates that the AUG task detected an invalid field value in the call record. The input data has an invalid call reference ID. Check the Cisco MGC raw data and make sure the call reference ID has the correct format. Contact the Cisco Technical Assistance Center.
* AGS203 <index> - fail <function> lookup of <field>: <value>
The <index> argument represents the call record index, <function> represents the function, <field> represents the field name in the call record, and <value> represents the field value being looked up. This message indicates a failed table lookup. Make sure the specific value exists in the table. Contact the Cisco Technical Assistance Center.
* AGS210 CTL file: <name> error: <ai string error>
The <name> argument represents the function name, and <ai string error> represents the error string. This message indicates an error returned by a control file function. Make sure the CTL file exists in the specified directory. Check the existence of the CTL file (*.CTL) and verify the structure of the control file (*.CFDT). If the CFDT file is corrupt, copy the default CFDT file. Contact the Cisco Technical Assistance Center.
* AGS211 CTL file BAF value error: <value>
The <value> argument represents a bad value. This message indicates that the contents of the BAF field in the control file is not 0 or 1. Verify sysparm configurations. Make sure the BAF output is set to 0 (disabled) or 1 (enabled) parameters. Contact the Cisco Technical Assistance Center.
* AGS232 #<index> Fail <function> lookup of<field1>:<value1> <field2>:<value2>
<field3>:<value3>
The <index> argument represents the call record index, <function> represents the table lookup function name, <field1> represents a first field in the call record, <value1> represents the value of the first field, <field2> represents the second field name in the call record, <value2> represents the value of the second field, <field3> represents a third field name in the call record, and <value3> represents the value of the third field. This message indicates a failed table lookup in the named locations. The system tried to match 3 field values to the lookup table. Verify the table configuration file and make sure the field values exist in that configuration file. Contact the Cisco Technical Assistance Center.
* AGS233 #<index> Fail <function> lookup of <field>:<value>
The <index> argument represents the call record index, <function> represents the function name, <field> represents the field name of the call record, and <value> represents the value of the field being looked up. This message indicates a failed table lookup of this field. Verify the input raw file used 1 field value to match to the lookup table. Contact the Cisco Technical Assistance Center.
* AGS234 #<index> - Invalid block: <field name>
The <index> argument represents the record index, and <field name> represents field names and values. This message indicates that an invalid block format was encountered when reading blocks from table file. For example, the system expects a six-digit value for NPANXX but it received only five digits. Verify the CTL file field value. Make sure you enter the required value. Contact the Cisco Technical Assistance Center.
* AGS235: <number> records failed trunk group lookup for file
cor_agcdr_<timestamp>_<sequence number>.bin
The <number argument> represents the number of records that failed the trunk group lookup, the <timestamp> argument represents the date and time and the <sequence number> argument represents the file sequence number. This minor alarm indicates the trunk group table is not correctly or fully populated. This error precludes these records from being processed by the measurements function. Fix the trunk group table. Refer to the AUG*log files in the opt/CiscoBAMS/files directory. This file specifies which trunk group should be modified so that these configuration failures do not occur.
AGS236 <number> record(s) default to interlata due to absent NPANXX for file.
The <number> argument represents the number of records that defaulted to the INTERLATA rating type due to this NPANXX combination not being in the NPANXX tables. This is an informational message. No action is required.
The ASC task is responsible for the output of Cisco MGC End of Call 1110 ASCII records.
ASC000 <task name><version> <version number> has started, pid <process id>
The <task name> argument represents the task name,<version> represents the task version, <version number> represents the version number, and <process id> represents the UNIX process identifier. This message defines what version of the task is running. This message is displayed for informational purposes. No action is necessary.
ASC001 <task name> terminating with code <return error code>, pid <process id>
The <task name> argument represents the task name, <return error code> represents the return error code, and <process id> represents the process identifier. The named task has been terminated abnormally. The code identifies the error encountered by the system. Check the error number.
ASC002 <task name> terminating with signal <signal number>, <process id>
The <task name> argument represents the name of the task, <signal number> represents the signal number received, and <process id> represents the process identifier. The named task has been terminated by a UNIX signal. See the "Signal Numbers" section.
ASC003 <name> terminating normally, pid <number>
The <name> argument represents the task name, and <number> represents the process identifier. This message indicates that the task terminated normally. This is an informational message. No action is necessary.
ASC004 No file to be processed. Retries in <n> seconds
The <n> argument represents the number of seconds. The task sleeps for n seconds before accessing more files. This is an informational message. No action is necessary.
* ASC101 File error <data type> on <system call> (<error number>)
The <data type> argument represents the type of data format, <system call> represents the name of the failed system, and <error number> represents the UNIX error number. The system encountered an error when performing a system call operation on the specified file. Look up the UNIX error number in the listing at the end of this appendix. Contact the Cisco Technical Assistance Center for help in checking the system configuration and making any necessary modifications.
** ASC200 Environment variable <variable name> not found
The <variable name> argument represents the name of the environment variable that was not found. The system encountered a missing or undefined variable. The symbol definitions either are missing or the variable must be set before running the task. Contact the Cisco Technical Assistance Center for help in checking the system configuration and making any necessary modifications.
(*,**) ASC201 Function <calling function> failed, (<error number>)
The <calling function> represents the calling function, and <error number> argument represents the UNIX error number. The system encountered a failure trying to make a function call. Examine the system error. Contact the Cisco Technical Assistance Center for help in checking the system configuration and making any necessary modifications.
** ASC202 Invalid AMADEF format, read <error string>, expected <expected string>
The <error string> represents the error string found, and <expected string> argument represents the string that was expected. The system encountered a format problem while trying to read the AMADEF file. The AMADEF file needs to be fixed. Contact the Cisco Technical Assistance Center for help in checking the system configuration and making any necessary modifications.
* ASC205 Unsupported field <field name>, conversion not defined
The <field name> argument represents the name of the field. The system encountered an AMA field that cannot be processed. Contact the Cisco Technical Assistance Center for help in checking the system configuration and making any necessary modifications.
ASC207 Processed <file name>, converted <record number> records, output <output file name>
The <file name> argument represents the name of the processed file, <record number> represents the converted number of records, and <output file name> represents the name of the output file. The system displays the following process information: name of processed file, number of records converted, and output file name. This message is displayed for informational purposes. No further action is necessary.
(*,**) ASC208 <data type> code <structure code> not found, cannot process record
The <data type> argument represents the type of data, and <structure code> represents the structure code or call type. The system is unable to process a record due to missing code and structure code information. Check the AMADEF file. Contact the Cisco Technical Assistance Center for help in checking the system configuration and making any necessary modifications.
** ASC209 Error <return value> reading file: CALLSTRUCT_MAP
The <return value> represents the value returned. The system encountered a format error reading the callstruct file. Check the CALLSTRUCT_MAP file. Contact the Cisco Technical Assistance Center for help in checking the system configuration and making any necessary modifications.
The Correlation Task (COR) is responsible for correlating call record data collected from the Cisco MGC.
COR000 <task> version <version number> has started pid <process ID>.
The <task> argument represents the version task, <version number> represents the task version number, and <process ID> represents the UNIX process identifier. This message defines the version of the task that is running. This is an informational message. No action is necessary.
COR001 <task> terminating with code <return code>, pid <process ID>.
The <task> argument represents the task name, <return code> represents the return code, and <process ID> represents the UNIX process identifier. The named task has ended abnormally. The code identifies the error encountered by the system. This is an informational message. No action is necessary.
COR002 <task> terminating with signal <number>, pid <process ID>.
The <task> argument represents the task name, <signal number> represents the signal number received, and <process ID> is the UNIX process identifier. The named task was ended by a UNIX signal. This is an informational message. No action is necessary.
COR003 <task> terminating normally, pid <process ID>.
The <task> argument represents the task, and <process ID> represents the UNIX process identifier. The named task has ended normally. This is an informational message. No action is necessary.
COR004 No file to be processed. Retries in <number> seconds.
The <number> argument represents the time interval in seconds. The task sleeps for n seconds before accessing more files. This is an informational message. No action is necessary.
COR005 Start processing file <name>.
The <name> argument represents the file name. This message indicates that a file is processing. This is an informational message. No action is necessary.
COR006 Processed file <name>: Output-> Complete:<number1> Incomplete:<number2>
Ldur:<number3> Hold-> Incomplete:<number4>.
The <name> argument represents the name of file that has finished processing, <number1> represents the number of complete calls output, <number2> represents the number of incomplete calls output, <number3> represents the number of long duration calls output, and <number 4> represents the number of incomplete calls. This message indicates that the displayed file has been processed. This is an informational message. No action is required.
* COR100 System call failure: <call name> (<error number>)
The <call name> represents the name of the failed system call, and <error number> represents the UNIX error number. An error was encountered when requesting this system call. Look up the UNIX error number for more information. Contact the Cisco Technical Assistance Center
(*,**) COR101 File error: <system call> on <filename> (<error number>)
The <system call> argument represents the name of the failed system call, <file name> represents the name of the file being operated on, and <error number> represents the UNIX error number. An error was encountered when performing a system call operation on the specified file. See the UNIX error number for more information. Contact the Cisco Technical Assistance Center.
** COR200 Environment variable <variable name> not found.
The <variable name> argument represents the name of the environment variable that was not found. This message indicates that the displayed environment variable was not found. Verify that the variable is defined in the sym_defs file, or make sure that it is set before running the task. Contact the Cisco Technical Assistance Center.
(*,**) COR201 Function <function name>() failed, (<error number>)
The <function name> argument represents the calling function name, and <error number> represents the UNIX error number. This message indicates the failure of a function call. See the UNIX error number for more information. Contact the Cisco Technical Assistance Center.
** COR202 Number of CDR memory extensions exceeded <max number>
The <max number> argument represents the maximum number of memory extensions. The maximum number of CDR memory extensions is set too small. Increase the maximum number of CDR memory extensions in the cor_cfg file in the opt/CiscoBAMS/files directory. The maximum number of CDR memory extensions is set too small. The -m value indicates the size of the extents and measures the number of CDRs to save into the memory, and the -e value indicates the number of extents. Contact the Cisco Technical Assistance Center.
** COR203 Read incomplete block size <file name>, <file name> expected.
The <file name> argument represents the name of the file found and the name of the file expected, respectively. The input file generated by the previous task has an I/O error (either a bad disk block or the disk space is full). The input file is incomplete. COR expected multiple records for each input file. The previous task wrote incomplete records, for example, because of a disk space problem. Contact the Cisco Technical Assistance Center.
** COR204 Invalid CDB type: <name>
The <name> argument represents the file name found. For more information, check the error file called err_<raw_file_name>. This message indicates that an invalid CDB type was encountered. The COR task writes invalid CDBs to that file. Check the Cisco MGC XECFGPARM.dat file and make sure the MGC CDB type is configured properly, as specified. Contact the Cisco Technical Assistance Center.
** COR205 Exhausted all possible sequence numbers: <file name>
The <file name> argument represents the name of the file. This message indicates that the number of input files in a single interval exceeded 99,999. Contact the Cisco Technical Assistance Center.
** COR206 Multiple boundary crossings in a single file: <file name>
The <file name> argument represents the name of the input file. This message indicates too many boundary crossings in one input file. This message is generated if there are more than two boundary crossings in a data file. Contact the Cisco Technical Assistance Center.
* COR207 Errors generating boundary crossing file: <file name>
The <file name> argument represents the name of the file. This message indicates that an error was encountered generating the boundary crossing file. Contact the Cisco Technical Assistance Center.
COR208 <string> stat file: <file name>
The <string> argument represents an action, such as "Creating" or "Closing," and <file name> represents the name of the file.This message is generated for the displayed stat file. This is an informational message. No action is necessary.
* COR210 CTL file: <function name> error: <ai string error>
The <function name> argument represents the name of the function, and <ai string error> represents the error code. This message indicates an error returned by a control file function. Contact the Cisco Technical Assistance Center.
* COR211 CTL file measurement value error: <value>
The <value> argument represents the incorrect value. This message indicates that the contents of the measurement field in the control file is not 0 or 1. Contact the Cisco Technical Assistance Center.
The CRD task is used to monitor communications between redundant BAMS units, and checks to see whether or not the remote unit is down.
* CRD500 Cannot attach to shared memory errno: <error number>
The <error number> argument represents the UNIX error number. The system is unable to access the shared memory segment and displays an error message. Look up the UNIX error for further explanation. Contact the Cisco Technical Assistance Center.
* CRD501 Get Message Queue ID for <message queue name> error, returned <return number>
The <message queue name> represents the name of the message queue, and <return number> represents the number of the returned function. The system is unable to get the message from the sender/receiver message queue and displays the sender/receiver message queue ID. Use ipcs to check the message queue status. Contact the Cisco Technical Assistance Center.
* CRD502 Redundant polling unit is down.
The redundant polling unit is down. Check the remote BAMS unit. If it is down, contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared when the alarm condition is removed. |
* CRD503 <operation> failed, returned <return number>, errno <error number>
The <operation> argument represents the failed operation, <return number> represents the number of the returned function, and <error number> represents the UNIX error number. The system is unable to send local, send remote, or receive messages and displays an error category and code. Look up the UNIX error. Contact the Cisco Technical Assistance Center.
* CRD504 Receive message time out
The system experienced a receive message time out. Check the network connection to the remote BAMS unit. Contact the Cisco Technical Assistance Center.
CRD505 Redundant polling unit is up
The redundant polling unit is back on-line. This message is displayed for informational purposes. No action is necessary.
The CTB task on the BAMS is responsible for generating the BAF output.
CTB000 <version> <version number> has started, pid <process ID>
The <version> argument represents the task version, the <version number> represents the task version number, and <process ID> represents the UNIX process identifier. The system displays a message that the named task and version has started. This message is displayed for informational purposes. No action is necessary.
CTB001 <task name> terminating with code <return error code>, pid <process id>
The <task name> argument represents the name of the task, <return error code> represents the returned error code, and <process ID> represents the UNIX process identifier. The named task has terminated abnormally. The code identifies the error encountered by the system. Look up the error code. Contact the Cisco Technical Assistance Center.
CTB002 <task name> terminating with signal <signal number>, <process ID>
The <task name> argument represents the name of the task, <signal number> represents the UNIX signal number, and <process ID> represents the UNIX process identifier. The named task was ended by a UNIX signal. This is an informational message. No action is necessary. See the "Signal Numbers" section.
CTB003 <name> terminating normally, pid <number>
The <name> argument represents the task name, and <number> represents the process ID number of the task. This message indicates that the task terminated normally. This is an informational message. No action is necessary.
CTB004 No file to be processed. Retries in <n> seconds
The <n> argument represents the number of seconds. The task will sleep for n seconds before accessing more files.
* CTB101 File error <data type> on <system call> (<error number>)
The <data type> argument represents the type of data format, <system call> represents the failed system call, and <error number> represents the UNIX error number. The system encountered an error when performing a system call operation on the specified file. Look up the error number. Contact the Cisco Technical Assistance Center.
** CTB200 Environment variable <variable name> not found
The <variable name> argument represents the name of environment variable not found. The system encountered a missing or undefined variable. The symbol definitions either are missing, or the variable must be set before running the task. Contact the Cisco Technical Assistance Center.
(*,**) CTB201 Function <calling function> failed, (<error number>)
The <calling function> argument represents the name of the calling function, and <error number> represents the UNIX error number. The system encountered a failure trying to make a function call. Look up the error number. Contact the Cisco Technical Assistance Center.
** CTB202 Invalid AMADEF format, read <error string>, expected <expected string>
The <error string> argument represents the error string found, and <expected string> represents the string expected. The system encountered a format problem while trying to read the AMADEF file. The AMADEF file needs to be fixed. Contact the Cisco Technical Assistance Center.
* CTB205 Unsupported field <field name>, conversion not defined
The <field name> argument represents the name of the field that is not supported. The system encountered an AMA field that cannot be processed. Contact the Cisco Technical Assistance Center.
CTB207 Processed <file name>, converted <record number> records, output <output file name>
The <file name> argument represents the name of the processed file, <record number> represents the record number, and <output file name> represents the output file name. The system displays the following process information: name of processed file, number of records converted, and output file name. This is an informational message. No action is necessary.
(*,**) CTB208 <data type> code <structure code> not found, cannot process record
The <data type> argument represents the data type, and <structure code> represents the structure code. The system is unable to process a record due to missing code and structure code information. Check the AMADEF file. A major alarm is generated if an incomplete, on-going call is rejected by the Correlation Task (COR) because an on-going record was not received within 12 hours (based on the cdb_creation_time of the latest data) this record will not have an associated map type. In release 2.6x, this cdr is written out to an error file ebaf* stored in the error directory, /opt/CiscoBAMS/data/error. Contact the Cisco Technical Assistance Center.
** CTB209 Error <return value> reading file: CALLSTRUCT_MAP
The <return value> represents the error value returned. The system encountered a format error reading the callstruct file. Check the CALLSTRUCT_MAP file. Contact the Cisco Technical Assistance Center.
The DRX task is used by one BAMS unit to receive messages from the other unit in a redundant configuration.
DRX000 Message Receive Task version <Version number> has started
The <Version number> argument represents the task version number. The system displays a message at start of the named task. This message is an informational message. No action is necessary.
DRX001 Terminating with signal <signal number>
The <signal number> argument represents the UNIX signal number. The system ends the DRX task and displays a signal number. Check the signal number. If an operator stops the system, it terminates with signal 15. Contact the Cisco Technical Assistance Center.
DRX002 Terminating with exit value <signal number>
The <signal number> argument represents the UNIX signal number. The system terminates the DRX task and displays a signal number. Look up the "Signal Numbers" section. Contact the Cisco Technical Assistance Center.
DRX003 Established connection with remote unit
The system has successfully established a connection with the remote unit. This is an informational message. No action is necessary.
DRX004 Closed connection with remote unit
The system has successfully closed the connection with the remote unit. This is an informational message. No action is necessary.
** DRX005 Cannot wait for connections <error number>
The <error number> argument represents the UNIX error number. The system cannot wait for connection and displays a UNIX error. Look up the error number. Contact the Cisco Technical Assistance Center.
** DRX006 Cannot accept connection <error number>
The <error number> argument represents the UNIX error. The system is unable to accept the connection request and displays a UNIX error. Look up the error number. Contact the Cisco Technical Assistance Center.
** DRX007 Cannot read from connection <error number>
The <error number> argument represents the UNIX error number. The system cannot read from the connection and displays a UNIX error. Look up the error number. Contact the Cisco Technical Assistance Center.
DRX008 Cannot route local message queue; <message queue ID>, <return value>, <error
number> <
The <message queue ID> argument represents the message queue identifier, <return value> represents the returned value, and <error number> represents the UNIX error number. The system is unable to route the local message to the intended destination and displays a UNIX error. Look up the error number. Check the message queue status by ipcs. Contact the Cisco Technical Assistance Center.
* DRX009 Connection broken <error number>. Will reconnect
The <error number> argument represents the UNIX error number. The system displays an error message regarding a broken connection. Look up the error number. Check if the remote BAMS unit system was stopped by the operator. Contact the Cisco Technical Assistance Center.
The DTX task is responsible for communication transmissions between BAMS units.
DTX000 Message Transmit Task version <version number> has started
The <version number> argument represents the task version number. The system has started the Message Transmit task. This is an informational message. No action is necessary.
DTX001 Terminating with signal <signal number>
The <signal number> argument represents the UNIX signal. The system is terminating this task and displaying a UNIX signal. Look up the signal number. Check if system was stopped by operator if signal number = 15. Contact the Cisco Technical Assistance Center.
DTX002 Terminating with exit value <exit value>
The <exit value> argument represents the UNIX exit value. The system is terminating this task and displaying a UNIX exit value. Contact the Cisco Technical Assistance Center.
DTX003 Established connection with remote unit
The system has established a connection to the remote unit. This is an informational message. No action is necessary.
DTX004 Closed connection with remote unit
The system has closed the connection with the remote unit. This is an informational message. No action is necessary.
DTX005 Could not discard queued messages <returned value> (<error number>)
The <returned value> argument represents the return value, and <error number> represents the UNIX error number. The system is unable to discard queued messages and displays a UNIX error code. Look up the error number. Contact the Cisco Technical Assistance Center.
DTX006 Connect attempt failed <error number>. Will retry later
The <error number> argument represents the UNIX error number. The system is unable to connect and displays a UNIX error. The system tries to establish the connection again later. Look up the error number. Contact the Cisco Technical Assistance Center.
** DTX007 Failed receiving message <return value> (<error number>)
The <return value> argument represents the returned value, and <error number> represents the UNIX error number. The system is unable to receive a message. Look up the error. Check if the remote BAMS unit is down. Contact the Cisco Technical Assistance Center.
* DTX008 Connection broken <error number>. Will re-connect
The <error number> argument represents the UNIX error number. The system reports an interrupted connection to the remote unit and displays a UNIX error. The system attempts to reconnect to the remote unit. Look up the error number. Check network to remote BAMS unit. Check if the operator stopped the remote BAMS unit or some error on that unit. Contact the Cisco Technical Assistance Center.
** DTX009 Cannot write to connection.
The system is unable to transmit information. Contact the Cisco Technical Assistance Center.
*C DTX010 Could not create message queue <return value> (<error number>).
The <return value> argument represents the returned value, and <error number> represents the UNIX error number. The system is unable to create a message queue. Look up the error number. Use ipcs to check the message queue status. Contact the Cisco Technical Assistance Center.
* DTX011 Connect socket for host <first host name> failed, trying host <second host name>
The <first host name> argument represents the primary host name for the remote BAMS unit, and <second host name> represents the secondary name. The system was unable to connect to the remote BAMS unit using the first host name and is now trying to connect to the unit using the second host name. Check the host names. Check if a network problem exists that prevents connection to <first host name>. Contact the Cisco Technical Assistance Center.
The FMT task is responsible for formatting files on the BAMS.
FMT000 <task> version <version number> has started pid <process ID>.
The <task> argument represents the task name, <version number> represents the task version number, and <process ID> represents the UNIX process identifier. This message identifies the version of the task that is running. This is an informational message. No action is necessary.
FMT001 <task> terminating with code <return code>, pid <process ID>.
The <task> argument represents the task name, <return code> identifies the terminating signal number encountered by the system, and <process ID> represents the UNIX process identifier. The named task ended abnormally. The code identifies the error encountered by the system. This is an informational message. No action is necessary.
FMT002 <task> terminating with signal <number>, pid <process ID>.
The <task> argument represents the task name, <number> represents the UNIX signal number, and <process ID> represents the UNIX process identifier. The named task was ended by a UNIX signal.
FMT003 <task> terminating normally, pid <process ID>.
The <task> argument represents the task name, and <process ID> represents the UNIX process identifier. The named task ended normally. This is an informational message. No action is necessary.
FMT004 Processing file <file name>
The <file name> represents the name of the file being processed. The task has started processing the named file. This is an informational message. No action is necessary.
FMT009 Received system signal <signal>
The <signal> argument represents the received signal number. The FMT task received a system signal. This is an informational message. No action is necessary.
FMT010 Processed <filename>, total:<number1> good:<number2> fmterr:<number3>
synerr:<number4> semerr:<number5>
The <file name> argument represents the type of data format, <number1> represents the processed file name, <number2> represents the number of good call records, <number3> represents the number of bad format call records, <number4> represents the number of call records with syntax errors, and <number5> represents the number of call records with semantic errors. This message displays call process summary information. This is an informational message. No action is necessary.
FMT019 [CDR] No flat files to process. Retry in <number> seconds.
The <number> argument represents the number of seconds.This message indicates that no data exists for processing. The FMT task retries in the displayed number of seconds. This is an informational message. No action is necessary.
* FMT101 File error: <call> on <file> (<code>)
The <call> argument represents the name of the failed system call, <file> represents the file name, and <code> represents the UNIX error number. This message indicates that the FMT task encountered an error when performing the displayed system call operation. Look up the error number. Contact the Cisco Technical Assistance Center.
*C FMT102 File I/O error: <call> on <file>, requested <number1>, got <number2>
The <call> argument represents the name of the failed I/O system call, <file> represents the name of the file being operated on, <number1> represents the number of bytes requested, and <number2> represents the number of bytes received. This message indicates that the FMT task encountered an error when performing the displayed I/O file operation. Contact the Cisco Technical Assistance Center.
* FMT201 Undefined environment variable <name>
The <name> represents the name of the environment variable. This message indicates that the displayed environment variable is not defined. Contact the Cisco Technical Assistance Center.
* FMT202 Input file does not start with header CDB
This message indicates that the FMT task detected an invalid field value in the call record. Verify the Cisco MGC input file. Contact the Cisco Technical Assistance Center.
* FMT203 Error reading TAG/LEN of TLV errno=<error number>
The <error number> argument represents the UNIX error number. An error occurred when reading TLV (T = Tag field code, L = Length of the field value, V = field Value). The FMT task stops processing this file, renames it as an error file, then begins processing the next input file. Look up the error. Verify the Cisco MGC input file. Contact the Cisco Technical Assistance Center.
* FMT204 Input file is not ended by footer CDB
The system encountered the displayed error. Contact the Cisco Technical Assistance Center.
* FMT222 Invalid TLV len:<length> at <position>th chars, CDB len:<size>
The <length> argument represents the incorrect TLV length, <position> represents the TLV position in the CDB, and <size> represents the size of the CDB. The system read in invalid TLV in length. The FMT task stops further processing of the input file and renames the input file by prepending "err_" to the input file name. Verify the Cisco MGC input file. Contact the Cisco Technical Assistance Center.
* FMT224 Process all CDBs: Error in parsing record.
This message indicates that the FMT task encountered an error when parsing this record. Verify the Cisco MGC input file. Contact the Cisco Technical Assistance Center.
* FMT225 Dump_cde: Unrecognized tag <tag number>
The <tag number> represents the number of the tag. This message indicates that the FMT task encountered an unrecognized tag. Verify the Cisco MGC input file. Contact the Cisco Technical Assistance Center.
* FMT226 Incorrect field length <field value length>.
The <field value length> argument represents the length of the field value.This message indicates that the FMT task encountered an incorrect field length. Verify the Cisco MGC input file. Contact the Cisco Technical Assistance Center.
The MML task on the BAMS is responsible for supporting the command-line interface (MML). This task will also display syntax error messages on the screen if the operator makes a mistake entering a command. The following syntax error messages are generally not written to the syslog file.
* MML600 Missed ';' in CLI_REC_MAP file, line number
The <#> argument indicates which line has a problem. The system encountered a syntax error in the record map file found in the opt/CiscoBAMS/files directory. Each line in the record map file has a maximum of 3 semicolon-separated fields. Use vi to look at the file and insert the semicolon field separator, if it is missing. Contact the Cisco Technical Assistance Center
* MML603 Open control file <name> failed
The <name> argument represents the name of the control file that the MML task could not open. The system was unable to open the displayed control file. Verify the control file exists in the opt/CiscoBAMS/files directory with the *.CTL and *.CFDT file extensions and that the group permissions (775) and ownership (bams) are properly set up. Contact the Cisco Technical Assistance Center.
* MML604 Set field <name> failed for record <number>
The <name> argument represents the name of the field name that the MML task could not set, and <number> represents the call record number. The system was unable to set a field name for the displayed record. Contact the Cisco Technical Assistance Center.
* MML605 Update record <number> failed
The <number> argument represents the number of the record that the MML task was unable to update. The system was unable to update the displayed record. Contact the Cisco Technical Assistance Center.
* MML606 Close control file <name> failed
The <name> argument represents the name of the control file that the MML task was unable to close. The system was unable to close the displayed control file. Contact the Cisco Technical Assistance Center.
(*,**,*C) MML608 Get number of keys failed
The system was unable to get the number of keys. Contact the Cisco Technical Assistance Center.
(*,**,*C) MML609 Missing row number or key field
The system encountered a missing row number or key field. Contact the Cisco Technical Assistance Center.
(*,**,*C) MML610 Get number of fields failed
The system experienced the displayed failure. Contact the Cisco Technical Assistance Center.
(*,**,*C) MML611 Get field names failed
The system experienced the displayed failure. Contact the Cisco Technical Assistance Center.
* MML612 Get field names error, NULL field name encountered
The system experienced the displayed failure. Contact the Cisco Technical Assistance Center.
* MML613 Get fields <name> failed for record <number>
The <name> argument represents the name of the field that the MML task was unable to get, and <number> represents the record number. The system was unable to get the displayed fields for the displayed record. Contact the Cisco Technical Assistance Center.
** MML614 Error finding type for field <name>. May have problem with CFDT file.
The <name> argument represents the field name.This message indicates an error encountered finding the displayed field name type. There may be a problem in the configuration file. Contact the Cisco Technical Assistance Center.
(*,**,*C) MML615 Get key names failed
The system experienced the displayed failure. Contact the Cisco Technical Assistance Center.
(*,**.*C) MML616 Get max number of records failed
The system experienced the displayed failure. Contact the Cisco Technical Assistance Center.
(*,**,*C) MML617 Max number of records should be greater than 0
The system experienced the displayed failure. Contact the Cisco Technical Assistance Center.
*C MML618 Dir <destination directory> could not be created.
The <destination directory> variable represents the destination directory name. The system was unable to create a destination directory. Contact the Cisco Technical Assistance Center.
* MML619 System call <name> failed. errno=<error number>
The <name> argument represents the name of the failed system call, and <error number> represents the UNIX error number. A system call failed. Look up the error number. Contact the Cisco Technical Assistance Center.
MML621 Successful prov-dply from <source directory>.
The <source directory> argument represents the file location specified with the prov-dply command. This is an informational message. No action is necessary.
(*, **, *C) MML622 File <number> could not be opened for <file name>.
The <number> argument represents the record number and <file name> represents the control file name. The file may not exist or may have become corrupt. Check the file. Contact the Cisco Technical Assistance Center for further assistance.
MML623 Read record <number> failed for control <file>.
The <number> argument represents the record number and <file name> represents the control file name. The control file may be in use. Try again in a few minutes. Contact the Cisco Technical Assistance Center for further assistance.
The MSC task is responsible for conserving disk space on the BAMS units, generating alarms when disk occupancy passes user-defined thresholds based on file prefixes found in specified the data directories, and deleting files to free disk space. Polled files are files that have been polled by a polling computer. Unpolled files are files that have not been polled yet. The MSC task can be set up to delete polled files when the percentage of disk space occupied by these files exceeds the user-defined thresholds. For example, if the polled upper threshold is set at 80 percent of disk occupancy and the lower polled threshold at 60 percent, the MSC task will begin deleting polled files from oldest to newest when the total polled file size exceeds the 80 percent upper threshold and stop deleting these files when it falls below the lower threshold. The unpolled threshold value is usually set high to avoid losing unpolled data, for example 90 percent and an alarm is generated to alert the user that the disk is filling up.
MSC001 MSC version <version> cleaning disk
The <version> argument represents the version number of the MSC task. The MSC task periodically deletes user-specified files from the disk at user-defined intervals so that the disk does not fill up and cause system failure. This message indicates that the MSC task is currently working. This is an informational message. No action is necessary.
* MSC003 <string1> error <UNIX error number> on <string2>
The <string1> argument represents the path or full file name and statistics. The <UNIX error number> argument represents the UNIX error set by the system function. The <string2> argument represents the path, or full filename, and statistics. This message indicates that an error occurred while the MSC task was searching for files to set up for deletion. An informational message is recorded in the system log file if the MSC task cannot obtain information on the file. A minor event is recorded if an error occurs while the MSC task attempts to retrieve information on the number of inodes, free disk space, and other similar information.
Check the UNIX error number to determine the reason for the error. Log in to the BAMS and source the sym_defs file. Use the make nodes and make home commands, restart the BAMS, and monitor the system log file to see if the error persists. If the problem continues, restart the BAMS to clear system resources.
* MSC006 Error <UNIX error number> opening <file>
The <UNIX error number> argument represents the UNIX error set by the system function. The <file> argument represents the file name. This message indicates that an error occurred while the BAMS was attempting to locate a file within the subdirectories of the /CiscoBAMS/data directory.
Check the UNIX error number to determine the reason for the error. Verify that the msct.parm file exists and that the permissions are correct. Contact the Cisco Technical Assistance Center.
* MSC007 Invalid parameter file
This message indicates that the parameter file for the MSC task has a problem. The file may be corrupted or may have an invalid parameter that was saved during MSC maintenance.
Verify that the msct.parm file exists and that the permissions are correct. Verify the information in the file. Contact the Cisco Technical Assistance Center.
MSC008 Maximum number of files exceeded
This message indicates that the MSC task attempted to clean up the disk by deleting files specified by the data storage attributes and has found that there are too many files on the disk. Log in to the BAMS and check disk usage. Delete data files from the BAMS manually. The data storage attributes may not be set correctly; check them to ensure that this situation does not recur.
MSC009 Error <UNIX error number> opening DISK_STATS file
The <UNIX error number> argument represents the UNIX error set by the system function. This message indicates that the BAMS tried to open the DISK_STATS file and encountered the specified UNIX error. The DISK_STATS file shows the amount of disk space currently being used on the BAMS.
Log in to the BAMS and check if the DISK_STATS file is on the disk using the ls command (ls DISK_STATS).
* MSC010 Undefined environment variable: <variable>
The <variable> argument represents the undefined variable. This message indicates that the MSC task encountered an error while attempting to run the housekeeping utility of deleting older data files. The data storage utility checks to see if the path for the data directory is defined and is able to get the specific attributes from the msct.parm file.
Verify that the /CiscoBAMS/data directory is defined in the sym_defs file (located in the /CiscoBAMS/bin directory). Verify that the file names that are set in the deletion list are correct (case-sensitive).
* MSC012 Cannot convert regular expression <reg>
The <reg> argument represents the regular expression. This message indicates that the BAMS could not recognize the displayed regular expression attribute. Verify the expression used on the MSC menu through the user interface. Contact the Cisco Technical Assistance Center.
* MSC014 regBAMS() returned NULL for pattern <reg>
The <reg> argument represents the regular expression. This message indicates that the BAMS provided a null value in place of the displayed regular expression. Verify the expression used on the MSC menu through the user interface.
(*,**,*C) MSC015 <file> is <number> days old, exceeded <number> day limit
The <file> argument represents the name of the file. The <number> argument represents the limit. This message indicates that the BAMS has identified the displayed file as being too old to remain on the system. Contact the Cisco Technical Assistance Center.
(*,**,*C) MSC016 <file> is <number> days old, exceeded <number> day limit DELETED.
The <file> argument represents the name of the file. This message indicates that the BAMS has identified the displayed file as being too old to remain on the system and has deleted the file. Contact the Cisco Technical Assistance Center.
(*,**,*C) MSC017 Disk block utilization <number> percent.
The <number> argument represents the number of blocks as a percentage. This message identifies the number of blocks used in the file system. Contact the Cisco Technical Assistance Center.
(*,**,*C) MSC018 Disk inode utilization <number> percent
The <number> argument represents the number of inodes as a percentage. This message identifies the number of blocks used in the file system. The alarm level depends on the percentage of inode usage. No action is necessary, unless there is a very high percentage of inode usage. In that case, contact the Cisco Technical Assistance Center.
MSC019 MSC waiting <number> minutes before starting.
The <number> argument represents the number of minutes.The task is waiting the displayed number of minutes before starting. This is an informational message. No action is necessary.
* MSC020 Access error trying to access <directory path>
The <directory path> argument represents the directory path. Search permission is denied on a component of the path prefix. Verify the directory path and try again. Contact the Cisco Technical Assistance Center.
* MSC021 Not a valid directory <directory path>
The <directory path> argument represents the directory path that is not valid. A component of the path prefix of <directory path> is not a directory. Verify the directory path and try again. Contact the Cisco Technical Assistance Center.
* MSC022 The directory does not exist <directory path>
The <directory path> argument represents the missing directory or file. Either a component of the path prefix or the file referred to by path does not exist. Verify the directory path and try again. Contact the Cisco Technical Assistance Center.
*C MSC030 Dir Entry 0: Data Disk block utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk utilization. "Dir Entry 0:" refers to the data disk partition. This message reports on disk usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed |
** MSC031 Dir Entry 0: Data Disk block utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk utilization. "Dir Entry 0:" refers to the data disk partition. This message reports on disk usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
* MSC032 Dir Entry 0: Data Disk block utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk utilization. "Dir Entry 0:" refers to the data disk partition. This message reports on disk usage when thresholds are exceeded. Contact. the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
MSC033 Disk block utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk utilization. This message reports on disk usage when thresholds are exceeded.
*C MSC040 Dir Entry 0: Data Disk inode utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk inode utilization. "Dir Entry 0:" refers to the data disk partition. This message reports on disk inode usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
** MSC041 Dir Entry 0: Data Disk inode utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk inode utilization. "Dir Entry 0:" refers to the data disk partition. This message reports on disk inode usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
* MSC042 Dir Entry 0: Data Disk inode utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk inode utilization. "Dir Entry 0:" refers to the data disk partition. This message reports on disk inode usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
MSC043 Disk inode utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk inode utilization. This message reports on disk inode usage when thresholds are exceeded.
MSC100 Update MSC task parameters
The parameters in the MSC configuration file have been updated and saved to disk. Someone has logged on as an administrative user and has modified the MSC parameters. Administrative users have access to all of the operator-level features. As well, they can modify system parameters and disk files. This is an informational message. No action is necessary.
* MSC101 Error <UNIX error number> running script: <name>
The <UNIX error number> argument represents the UNIX error set by the system function. The <name> argument represents the script name. This message indicates that the MSC task experienced an error while running the displayed script from the command line. Look up the error number. Contact the Cisco Technical Assistance Center.
*C MSC130 Dir Entry 1: Archive Disk block utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk utilization. "Dir Entry 1:" refers to the archive disk partition. This message reports on disk usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed |
** MSC131 Dir Entry 1: Archive Disk block utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk utilization. "Dir Entry 1:" refers to the archive disk partition. This message reports on disk usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
* MSC132 Dir Entry 1: Archive Disk block utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk utilization. "Dir Entry 1:" refers to the archive disk partition. This message reports on disk usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
*C MSC140 Dir Entry 1: Archive Disk inode utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk inode utilization. "Dir Entry 1:" refers to the archive disk partition. This message reports on disk inode usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
** MSC141 Dir Entry 1: Archive Disk inode utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk inode utilization. "Dir Entry 1:" refers to the archive disk partition. This message reports on disk inode usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
* MSC142 Dir Entry 1: Archive Disk inode utilization <number> percent
The <number> argument represents the threshold value as a percentage of disk inode utilization. "Dir Entry 1:" refers to the archive disk partition. This message reports on disk inode usage when thresholds are exceeded. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed. |
The POL task on BAMS units is responsible for data collection from the Cisco MGCs.
POL100 POL Version <version number> for site <site number> has started
The <version number> argument represents the software or task version, and <site number> represents the polling site number.The POL task has been started. This is an informational message. No action is necessary.
POL101 POL for site <site number> is terminating with signal <signal number>
The <site number> argument represents the polling site number, and <signal number> represents the UNIX signal number.The POL task stops. This is an informational message. No action is necessary.
POL103 Polling MGC units <MGC node 0 name> and <MGC node 1 name> for site <site number>
The <MGC node 0 name> argument represents the name of the Cisco MGC node 0, <MGC node 1 name> represents the name of the Cisco MGC node 1, and <site number> represents the polling site number.The POL task has started polling the named Cisco MGC units. This is an informational message. No action is necessary.
POL104 Polling MGC unit <MGC node name> for site <site number>
The <MGC node name> argument represents the name of the Cisco MGC, and <site number> represents the polling site number. The POL task has started to poll the named Cisco MGC unit. This is an informational message. No action is necessary.
*POL105 Polling unit rotates from unit <from unit number> to <to unit number> for site
<site number> successfully.
The <from unit number> represents the number of the unit that was actively polling before the polling unit rotation, <to unit number> represents the number of the unit that was the standby unit before the polling unit rotation, and <site number> represents the polling site number. The unit responsible for polling has rotated as displayed.
POL106 File <file name> send to redundant poll unit <redundant unit number> for site <site
number> successfully
The <file name> argument represents the name of the file transferred to the redundant polling unit, <redundant unit number> represents the number of the redundant unit, and <site number> represents the polling site number. The named file is sent to the redundant BAMS unit. This is an informational message. No action is necessary.
POL107 File <file name> receive from unit <from unit number> for site <site number>
successfully
The <file name> argument represents the name of the file that was successfully received from the polling unit, <from unit number> represents the remote polling unit number, and <site number> represents the site number. The POL task has received a file as displayed. This is an informational message. No action is necessary.
POL108 Retry #<retry times> will start in <sleep seconds> for site <site number>
The <retry times> argument represents the times the task has retried to poll the site, <sleep seconds> represents the number of seconds the task waits before attempting to poll the site again, and <site number> represents the polling site number. The POL task retries polling the data. This is an informational message. No action is necessary.
POL109 Successfully polled <file name> with size <file size> for site <site number>
The <file name> argument represents the name of the file that was successfully polled, <file size> represents the file size of the polled file, and <site number> represents the polling site number. The POL task has polled the named file. This is an informational message. No action is necessary.
POL110 Cannot update CTLFILE from polling unit to standby unit
The task performed an illegal operation in attempting to update the Control file. Check the task permissions and times. The control file is locked while either unit is actively polling and can be modified only when both units are at rest.
POL111 This is standby unit for site <site number>
The <site number> argument represents the unit site number. The identified unit is not the current polling unit. This is an informational message. No action is necessary.
POL112 Polling MGC host <MGC host name> failed, trying host <MGC host name 2> for site
<site number>
The <MGC host 1> argument represents the name of the first Cisco MGC host line polled, <MGC host 2> represents the name of the Cisco MGC host for second Ethernet card, and <site number> represents the site number.The system's attempt to poll the first Cisco MGC host failed and it is now trying to poll the Cisco MGC host for second Ethernet card. This is an informational message. No action is necessary.
POL201 POL session ended normally for site <site number>
The poll session ends. The <site number> argument represents the polling site number. This is an informational message. No action is necessary.
POL202 POL session from BAMS unit <unit number> starts for site <site number>
The <unit number> argument represents the BAMS unit number, and the <site number> argument represents the polling site number. The poll session starts. This is an informational message. No action is necessary.
* POL203 chgno executed, unit: <unitno> old: <seqno> new: <seqno>
The <unit number> represents the unit number of the BAMS unit, <sequence number 1> represents the old sequence number, and <sequence number 2> represents the new sequence number. The sequence number has changed. This is recorded as a minor event for audit purposes only.
* POL204 chgno cannot execute, POL record <sequence number> is in use
The <sequence number> represents the sequence number of the polling record. The sequence number cannot be changed, because the control file is in use. Try again later.
* POL300 Environment variable <environment variable name> is undefined
The <environment variable name> argument represents the name of the environment variable. The named environment variable is not defined. Contact the Cisco Technical Assistance Center.
* POL302 regBAMS returned NULL for pattern <pattern> for site <site number>
The <pattern> argument represents the polling pattern, and <site number> represents the polling site number. This message indicates that an error occurred in a regular expression compare. This message indicates the file pattern does not match. Verify the polling parameters and file prefix and suffix values. Contact the Cisco Technical Assistance Center.
* POL305 Invalid operation: <operation number> for site <site number>
The <operation number> argument represents the invalid operation, and <site number> represents the polling site number. The system was unable to perform the named FTP operation; it is not valid. Contact the Cisco Technical Assistance Center.
* POL306 Cannot open <file name> for site <site name>
The <file name> argument represents the file name that cannot be opened, and <site number> represents the polling site number. The system is unable to open the named file. This message indicates that the polling task cannot open the displayed file name on the BAMS unit. Check the directory permissions and file ownership. Contact the Cisco Technical Assistance Center.
* POL307 Poll failed for <file name> for site <site number>
The <file name> argument represents the file name of file that could not be polled, and <site number> represents the polling site number. The system was unable to poll the named file. Manually test whether FTP is working. Create a test file on the Cisco MGC and manually FTP it to the BAMS unit. This message may indicate a Cisco MGC or network problem. Contact the Cisco Technical Assistance Center.
* POL308 Cannot get file status for <file name> for site <site number>
The <file name> argument represents the file name of file that could not be polled, and <site number> represents the polling site number. The system was unable to obtain a file status for the named file. Check if the filename exists on the local BAMS unit. Check the file, directory, and ownership permissions. Contact the Cisco Technical Assistance Center.
* POL309 File size incorrect for polling <file name> for site <site number>
The <file name> argument represents the name of the file to be polled, and <site number> represents the polling site name. The polling file size is not correct. The polling task compares the file size expected from the Cisco MGC. Check whether a test file can be transferred by FTP to the BAMS unit from the Cisco MGC. If the file size is different, a network problem is indicated. Contact the Cisco Technical Assistance Center.
* POL312 Failed updating control record file for site <site number>
The <site number> argument represents the polling site number. The POL task was unable to update the control record file for the named site. This message indicates the control file is locked. Check if other users are logged in and may have opened the control file using the who command. Check the MML command history in the MML daily log file. Contact the Cisco Technical Assistance Center.
* POL321 Cannot open directory file <directory name> for site <site number>
The <directory name> represents the name of the directory, and <site number> represents the site number. The polling task cannot open the directory. If the problem persists, contact the Cisco Technical Assistance Center.
* POL322 System () call failed, errno = <error number>
The <error number> argument represents the UNIX error number. The POL task displays an error code for a failed system call. Look up the error. Contact the Cisco Technical Assistance Center.
* POL325 Fork () failed for site <site number>
The <site number> represents the polling site number. The system reports a fork failure for the named site. This message indicates the task cannot create a child process. Restart the application. If the problem persist, contact the Cisco Technical Assistance Center.
* POL327 Login failed for MGC unit <MGC node name> for site <site number>, please check
ID/password
The <MGC node name> argument represents the name of the Cisco MGC node, and <site number> represents the polling site number. The system was unable to log in to the named Cisco MGC unit. Check the user ID and password. Check setpollpwd. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the error alarm condition is removed |
* POL328 File <file name> send to redundant poll unit <redundant unit number> for site
<site number> failed
The <file name> argument represents the name of the file to be sent, <redundant unit number> represents the number of the redundant polling unit, and <site number> represents the polling site number. The system was unable to send the named file to the redundant unit. Check that FTP is working on the BAMS unit. Create a test file on the Cisco MGC and manually FTP it to the BAMS unit. If unsuccessful, this may indicate a network problem. Contact the Cisco Technical Assistance Center.
POL329 File <file name> sent to poll unit for site <site number> successfully.
The <file name> argument represents the name of the file sent and the <site number> argument represents the polling site number. In a redundant system, after a Cisco MGC file is polled by one BAMS unit, it is processed by that unit and also sent to the redundant BAMS unit for processing. This is an informational message. No action is necessary.
POL330 Cannot open XFR directory, errno <error number>
The <error number> represents the error number. The polling task cannot open the xfr directory to transfer files to the redundant BAMS unit. Check the error. If the problem persists, contact the Cisco Technical Assistance Center.
* POL331 Polling unit rotates from unit <from unit number> to <to unit number> for site
<site number> failed
The <from unit number> argument represents the polling unit that was actively polling just before the unit rotation, <to unit number> represents the unit that was on standby, and <site number> represents the polling site number. The system was unable to perform the requested polling unit rotation. Check the network connection between the BAMS units. Perform an FTP test. Contact the Cisco Technical Assistance Center.
* POL332 Polling unit rotates from unit <from unit number> to <to unit number> for site
<site number>, but CTLFILE transfer failed
The <from unit number> argument represents the polling unit that was actively polling just before the unit rotation, <to unit number> represents the unit that was on standby, and <site number> represents the polling site number. The POL task was able to perform the requested polling unit rotation, but unable to transfer the necessary control file information. Check the network and perform an FTP test. Contact the Cisco Technical Assistance Center.
* POL333 Error in linking to <directory name> directory for site <site number>, errno
<error number>
The <error number> argument represents the UNIX error code. The POL task was unable to perform the requested file linking operation. Check the permissions for the specified directory. Contact the Cisco Technical Assistance Center.
* POL334 Cannot attach to shared memory, errno <error number>
The <error number> argument represents the UNIX error code. The POL task was unable to access the shared device memory. Use ipcs to check the shared memory status. Contact the Cisco Technical Assistance Center.
* POL335 Rotate cannot be executed in non-polling unit
The POL task was unable to rotate the requested unit that was on standby at the time. The system only allows polling unit rotation only from the current polling unit to the standby unit.
* POL336 File <file name> receive from unit <from unit number> for site <site number>
failed
The <file name> argument represents name of the file the system was unable to receive, <from unit number> represents the unit number of the sending device, and <site number> represents the polling site number. The POL task was unable to receive a file from the named unit and site. Perform an FTP test. Contact the Cisco Technical Assistance Center.
* POL338 Site number invalid or not specified
The POL task is unable to validate the site number; it may be undefined. Check polling parameters, and ensure the site exists. Contact the Cisco Technical Assistance Center.
* POL340 No data in 3 consecutive polling sessions for site <site number>
The <site number> argument represents the polling site number. The POL task was unable to execute the requested polling operation in three consecutive attempts. Check Cisco MGC and verify existence of data. Check the sequence numbers on the BAMS units using change_no. Contact the Cisco Technical Assistance Center.
* POL341 Cannot access shared memory, MGR may not have started
The polling tasks cannot get the contents of the shared memory. If the problem persists, contact the Cisco Technical Assistance Center.
* POL342 Cannot <access> xfr directory <directory name>, errno <error number>
The <access> argument represents the operation, <directory name> represents the name of the directory, and <error number> represents the error number. The polling task is unable to perform the named operation on the xfr directory. Check the error message. If the problem persists, contact the Cisco Technical Assistance Center.
* POL343 Cannot <operation> site data directory <directory>, errno <error number>
The <operation> argument represents the attempted system operation, <directory> represents the site data directory, and <error number> represents the UNIX error number. The POL task is unable to perform the specified system operation on the site data directory and displays a UNIX error code. Look up the error. Check permissions of BAMS user to access or create this directory. Contact the Cisco Technical Assistance Center.
* POL353 Record <record number> already in use
The <record number> argument represents the record number. The POL task was unable to access the requested record. The record may be locked by another process. Determine who is using and locking the screen. Contact the Cisco Technical Assistance Center.
* POL356 Record # <record number> already in use in file <control file name>.CTL
The <record number> argument represents the record number, and the <control file name> argument represents the control file name. This record is already locked by another process. Try again later. If the problem persists, contact the Cisco Technical Assistance Center.
* POL358 Invalid REDUNDANCY_MODE
The symbol definitions contain an invalid redundancy mode specification. Check the collect_defs configuration file in the opt/CiscoBAMS/bin directory. The Redundancy mode value should be 2 for redundant and 1 for simplex configuration. Run change_mode in the opt/CiscoBAMS/bin directory if the setting is wrong. Contact the Cisco Technical Assistance Center.
* POL359 Cannot rotate unit in simplex mode
The POL task is unable to rotate polling units, because the system in operating in simplex (single-unit) mode, which does not permit a polling unit rotation. Contact the Cisco Technical Assistance Center.
* POL360 Open control file <file name> failed
The <file name> argument represents the name of the control file. The POL task is unable to open the control file. Check permissions of the control file and ownership. Contact the Cisco Technical Assistance Center.
* POL361 Polling config record# <number> is blank in <file name>
The <number> argument represents the site number, and <file name> represents the name of the control file. The polling configuration record is blank. Check the polling configuration file and verify that polling configuration file is populated for this site. Contact the Cisco Technical Assistance Center.
|
Note This alarm is cleared after the alarm condition is removed. |
* POL362 Sequence number is blank for config record <number> in <file name>.CTL
The <number> argument represents the site number, and <file name> represents the name of the control file. The sequence number is blank. Use change_no to specify sequence number to poll. Contact the Cisco Technical Assistance Center.
* POL363 Cannot open <directory name> directory, errno <error number>
The <directory name> argument represents the name of the polled directory, and <error number> represents the UNIX error. The POL task cannot open the named directory and returns a UNIX error. Check the UNIX error number and permissions on the directory.
*C POL401 Max FTP failures for one file reached for site <site number>
The <site number> argument represents the polling site number. The POL task has exceeded the maximum FTP failure threshold specified for a single file polling operation at the named site. Contact the Cisco Technical Assistance Center immediately and request they check the network and perform an FTP test.
|
Note This alarm is cleared after the alarm condition is removed. |
*C POL402 Cannot connect to unit <unit name> for site <site number>
The <unit name> argument represents the name of the unit the system is attempting to poll, and <site number> represents the polling site number. The system is unable to connect to the specified unit at the named site. Contact the Cisco Technical Assistance Center immediately and request they check the network and perform an FTP test.
|
Note This alarm is cleared after the alarm condition is removed. |
The RCV task on the BAMS is responsible for receiving control files.
*RCV501 Error loading record <error number>
The <error number> argument represents the UNIX error code. The RCV task is unable to load a control record. Look up the error number. Contact the Cisco Technical Assistance Center.
* RCV502 Invalid operation <operation number>
The <operation number> argument represents the operation number. The RCV task has performed an invalid operation. Contact the Cisco Technical Assistance Center.
* RCV503 Cannot open <file name>
The <file name> argument represents the name of the file that could not be opened. The RCV task is unable to open the named file. Verify the file exists and that the file directory can be written to by user bams. Contact the Cisco Technical Assistance Center.
* RCV507 FTP failed for <file name>
The <file name> argument represents the name of the file that the RCV task could not operate on. The RCV task is unable to perform an FTP operation on the named file. Check if the control filename exists on the remote BAMS unit. Check the network connection to the remote BAMS unit and perform an FTP test. Contact the Cisco Technical Assistance Center.
* RCV508 Cannot get file status of <file name>
The <file name> argument represents the name of the file. The RCV task is unable to get a file status for the named file. Check if the control file exists on the local BAMS unit and user has read permissions on the file. Contact the Cisco Technical Assistance Center.
* RCV509 File size incorrect for FTP <file name>
The <file name> argument represents the name of the file. The RCV task is unable to match the file size for the named file. Perform an FTP test. If the file sizes match, contact the Cisco Technical Assistance Center.
* RCV520 Cannot connect to unit <unit host name>
The <unit host name> argument represents the name of the unit host. The RCV task is unable to connect to the other unit. Check the network connection to <unit host name>. Contact the Cisco Technical Assistance Center.
* RCV521 Cannot open directory file <directory name>
The <directory name> argument represents the name of the directory. The RCV task is unable to open the named directory file. Check if the user has permission to read directory <directory name>. Contact the Cisco Technical Assistance Center.
* RCV522 system () call failed, errno = <error number>
The <error number> argument represents the UNIX error number. A system call has failed and the system displays a UNIX error. Look up the error number. Contact the Cisco Technical Assistance Center.
* RCV524 Max FTP failures for one file reached
The RCV task has failed to FTP the file after the maximum number of tries. Check the network connection to the remote BAMS unit and perform an FTP test. Contact the Cisco Technical Assistance Center.
* RCV525 fork () failed for site <site number>
The <site number> argument represents the site number. The RCV task experienced a fork failure at the named site. Contact the Cisco Technical Assistance Center.
* RCV527 Login failed for unit <unit host name>, please check ID/passwd
The <unit host name> argument represents the name of the unit host. The login has failed for the other BAMS unit. Check the user ID and password using setbamunit. Contact the Cisco Technical Assistance Center.
RCV528 Receive control information from redundant poll unit host <unit host 1> failed,
trying host <unit host2>
The <unit host 1> argument represents the name of the first unit host, and <unit host 2> represents the name of the unit host for the second Ethernet card. The RCV task was unable tor receive the control file from the displayed host. Check the network connection to the remote BAMS <unit host 1> and perform an FTP test.
The SXF task on the BAMS is responsible for sending a control file to a redundant BAMS unit.
* SXF037 Error loading control record, returned <return value>
The <return value> argument represents the system-returned error value. The SXF task experienced an error loading a control record and returns an error value. Contact the Cisco Technical Assistance Center.
SXF041 Send control information to redundant poll unit host <unit host name> failed,
trying host <unit host name of second ethernet card>
The <unit host name1> argument represents the first unit host name polled, and <unit host name2> represents the unit host name of the second Ethernet card. The SXF task failed in its attempt to send the control record and is trying another line. Check the network connection to the remote BAMS <unit host name> and perform an FTP test.
* SXF502 stat () on <filename> failed, errno <error number>
The <filename> argument represents the name of the file, and <error number> represents the UNIX error number. Check the UNIX error.
* SXF503 <filename> size incorrect: remote=<remote size>, local=<standard buffer size)
The <filename> argument represents the name of the file, <remote size> represents the size on the remote unit, and <standard buffer size> represents the standard buffer size on the local unit. Check the network status. A communication problem exists between the two BAMS units. Check whether the Ethernet connection is good. Verify that the setbamunit utility has the correct parameters.
* SXF510 Attempt #<number> to rename or transfer <filename> failed
The <number> argument represents the number of communication attempts, and <filename> represents the name of the file to be transferred or renamed. Check the network status. A communication problem exists between the two BAMS units. Check whether the Ethernet connection is good. Verify that the setbamunit utility has the correct parameters.
* SXF640 <directory filename> No such file or directory.
The <directory filename> argument represents the directory filename. Verify the path exists on the remote unit.
Table A-9 lists the UNIX error numbers.
| Number | Reason |
|---|---|
1 | Not super-user |
2 | No such file or directory |
3 | No such process |
4 | Interrupted system call |
5 | I/O error |
6 | No such device or address |
7 | Arg list too long |
8 | Exec format error |
9 | Bad file number |
18 | Cross-device link |
19 | No such device |
20 | Not a directory |
21 | Is a directory |
22 | Invalid argument |
23 | File table overflow |
24 | Too many open files |
25 | Inappropriate ioctl for device |
26 | Text file busy |
27 | File too large |
28 | No space left on device |
29 | Illegal seek |
30 | Read only file system |
31 | Too many links |
32 | Broken pipe |
33 | Math argument out of domain of function |
34 | Math result not representable |
35 | No message of desired type |
36 | Identifier removed |
37 | Channel number out of range |
38 | Level 2 not synchronized |
39 | Level 3 halted |
40 | Level 3 reset |
41 | Link number out of range |
42 | Protocol driver not attached |
43 | No CSI structure available |
44 | Level 2 halted |
45 | Deadlock condition |
46 | No record locks available |
47 | Operation canceled |
48 | Operation not supported |
49 | Disk quota exceeded |
50 | Invalid exchange |
51 | Invalid request descriptor |
52 | Exchange full |
53 | No anode |
54 | Invalid request code |
55 | Invalid slot |
56 | File locking deadlock error |
57 | Bad font file format |
60 | Device not a stream |
61 | No data (for no delay I/O) |
62 | Timer expired |
63 | Out of streams resources |
64 | Machine is not on the network |
65 | Package not installed |
66 | The object is remote |
67 | The link has been severed |
68 | Advertise error |
69 | Srmount error |
70 | Communication error on send |
71 | Protocol error |
74 | Multihop attempted |
77 | Trying to read unreadable message |
78 | Path name is too long |
79 | Value too large to be stored in data type |
80 | Given log. name not unique |
81 | F.D. invalid for this operation |
82 | Remote address changed |
83 | Cannot access a needed shared library |
84 | Accessing a corrupted shared library |
85 | .lib section in a.out corrupted |
86 | Attempting to link in too many libraries |
87 | Attempting to execute a shared library |
88 | Illegal byte sequence |
89 | Unsupported file system operation |
90 | Symbolic link loop |
91 | Restartable system call |
92 | If pipe/FIFO, do not sleep in stream head |
93 | Directory not empty |
94 | Too many users (for UFS) |
95 | Socket operation on non-socket |
96 | Destination address required |
97 | Message too long |
98 | Protocol wrong type of socket |
99 | Protocol not available |
120 | Protocol not supported |
121 | Socket type not supported |
122 | Operation not supported on socket |
123 | Protocol family not supported |
124 | Address family not supported by protocol family |
125 | Address already in use |
126 | Cannot assign requested address |
127 | Network is down |
128 | Network is unreachable |
129 | Network dropped connection because of reset |
130 | Software caused connection abort |
131 | Connection reset by peer |
132 | No buffer space available |
133 | Socket is already connected |
134 | Socket is not connected |
143 | Cannot send after socket shutdown |
144 | Too many references: can't splice |
145 | Connection timed out |
146 | Connection refused |
147 | Host is down |
148 | No route to host |
149 | Operation already in progress |
150 | Operation now in progress |
151 | Stale NFS file handle |
Table A-10 displays the signal numbers.
| Number | Name | Reason |
|---|---|---|
1 | SIGHUP | Hangup |
2 | SIGINT | Interrupt (rubout) |
3 | SIGQUIT | Quit (ASCII FS) |
4 | SIGILL | Illegal instruction (not reset when caught) |
5 | SIGTRAP | Trace trap (not reset when caught) |
6 | SIGIOT | IOT instruction |
7 | SIGEMT | EMT instruction |
8 | SIGFPE | Floating-point exception |
9 | SIGKILL | Kill (cannot be caught or ignored) |
10 | SIGBUS | Bus error |
11 | SIGSEGV | Segmentation violation |
12 | SIGSYS | Bad argument to system call |
13 | SIGPIPE | Write on a pipe with no one to read it |
14 | SIGALRM | Alarm clock |
15 | SIGTERM | Software termination signal from kill |
16 | SIGUSR1 | User-defined signal 1 |
17 | SIGUSR2 | User-defined signal 2 |
18 | SIGCLD | Child status change |
18 | SIGCHLD | Child status change alias (POSIX) |
19 | SIGPWR | Power-fail restart |
20 | SIGWINCH | Window size change |
21 | SIGURG | Urgent socket condition |
22 | SIGPOLL | Pollable event condition |
22 | SIGIO | Socket I/O possible (SIGPOLL alias) |
23 | SIGSTOP | Stop (cannot be caught or ignored) |
24 | SIGSTP | User stop requested from tty |
25 | SIGCONT | Stop process has been continued |
26 | SIGTTIN | Background tty read attempted |
27 | SIGTTOU | Background tty write attempted |
28 | SIGVTALRM | Virtual time expired |
29 | SIGPROF | Profiling timer expired |
30 | SIGXCPU | Exceeded CPU limit |
31 | SIGXFSZ | Exceeded file size limit |
32 | SIGWAITING | Process's lwps are blocked |
33 | SIGLWP | Special signal used by thread library |
34 | SIGFREEZE | Special signal used by CPR |
35 | SIGTHAW | Special signal used by CPR |
36 | SIGCANCEL | Thread cancellation signal used by libthread |
37 | SIGTMIN | First (highest-priority) real-time signal |
44 | SIGRTMAX | Last (lowest-priority) real-time signal |
Posted: Fri Aug 24 10:51:15 PDT 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.