Cisco CDA Visual Quality Experience Application User Guide, Release 2.1 - VQE System Messages [Cisco Videoscape Distribution Suite for Internet Streaming]

Table Of Contents

VQE System Messages

System Message Structure

System Message Example

Basic Recovery Procedures

VQE System Messages

STUN_SERVER Messages

VQES_CP Messages

VQES_DP_CLIENT Messages

VQES_DP Messages

VQES_MLB_CLIENT Messages

VQES_MLB Messages

VQES_PM Messages

VQES_CFG Messages

VQES_HASH Messages

VQES_RTP Messages

VQES_RTSP Messages

VQE System Messages

This appendix lists and describes the Cisco VQE system messages. The VQE software writes these messages to these locations:

•VQE-S system messages are written to the /var/log/vqes/vqes.log file.

•VQE Client Channel Configuration Delivery Server (VCDS) system messages are written to the /var/log/messages file.

Not all system messages indicate problems with VQE. Some messages are purely informational, while others may help diagnose problems with communications links or the operating system (for example, file permission problems). Only critical messages are displayed on the CDE110 console.

For information on VQE-S AMT and VCPT logging output, see the "VQE-S AMT and VCPT Logging and Log Files" section on page 5-2.

System Message Structure

System messages are structured as follows:
FACILITY-SEVERITY-MNEMONIC: Message-text
•FACILITY code

The facility code consists of two or more uppercase letters that indicate the facility to which the message refers. Table C-1 lists the VQE facility codes.

Table C-1 VQE Facility Codes

Code

VQE Facility

STUN_SERVER

STUN Server (VQE-S)

VQES_CP

VQE-S Control Plane

VQES_DP_CLIENT

VQE-S Data Plane Client

VQES_DP

VQE-S Data Plane

VQES_MLB_Client

VQE-S Multicast Load Balancer Client

VQES_MLB

VQE-S Multicast Load Balancer

VQES_PM

VQE-S Process Monitor

VQE_CFG

VQE-S Configuration

VQE_HASH

VQE hash table

VQE_RTP

VQE Real-Time Transport Protocol
(Many of these messages are related to RTP Control Protocol (RTCP)).

VQE_RTSP

VQE Real Time Streaming Protocol (VCDS)

•SEVERITY level

The severity level is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table C-2 lists the message severity levels. Messages of severity 7 (Debugging) are not described in this appendix.

Table C-2 Message Severity Levels

Severity Level

Name

Description

0

Emergency

System is unusable.

1

Alert

Immediate action is required.

2

Critical

Critical condition

3

Error

Error condition

4

Warning

Warning condition

5

Notification

Normal but significant condition

6

Informational

Information message only

7

Debugging

Message that appear during debugging only

•MNEMONIC code

The combination of the facility code and the mnemonic code uniquely identifies the error message.

•Message-text

Message-text is a text string that describes the condition. The text string sometimes contains detailed information about the event, including port numbers and network addresses. Because variable fields change from message to message, they are represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table C-3 lists the variable fields in messages.

Table C-3 Representations of Variable Fields in Messages

Representation

Type of Information

[chars] or [char]

Character string

[dec]

Decimal

[hex]

Hexadecimal integer

[int]

Integer

[num]

Number

System Message Example

The following is an example of a VQE system message:
VQES_CP-3-CP_CHANNEL_DELETE_ERR: Failed to delete a channel due to [chars] 
•VQES_CP is the facility code.

•3 is the severity level.

•CP_CHANNEL_DELETE_ERR is the mnemonic code.

•"Failed to delete a channel due to [chars]" is the message text.

Basic Recovery Procedures

In the Recommended Actions of the system messages, certain recovery procedures that VQE users should perform are referred to numerous times. Table C-4 provides references to where you can find more information on these recovery procedures.

Table C-4 Recovery Procedures in Recommended Actions

Recovery Procedure in Recommended Action

Notes and Where to Find Information

Reboot the VQE-S server

Restarting the System and Verifying System and VQE-S Status, page D-13

Restart the VQE-S application.

Stopping and Restarting VQE-S, page 2-23

Restart the VQE-S channels.

In VCPT, use the Force Update button to send the channel information to the VQE Server. See the "Force Update Button" section on page 3-4.

Modify the channel configuration and resend it to the VQE Servers and/or VCDS servers.

Chapter 3, "Using the VQE Channel Provisioning Tool"

Modify vqes.conf and restart the VQE-S application.

For information on modifying the VQE-S configuration file (vqes.conf), see Appendix A, "Configuring VQE-S."

For information on restarting the VQE-S application, see the "Stopping and Restarting VQE-S" section on page 2-23.

Issue the vqereport command to gather data that may help identify the nature of the error.

"Using the vqereport Command" section on page 5-10

VQE System Messages

This section lists the Cisco VQE system messages.

STUN_SERVER Messages

This section contains STUN_SERVER messages.

STUN_SERVER-2
Error Message     STUN_SERVER-2-SS_INIT_FAILURE_CRIT: STUN Server initialization failed 
due to [chars] 
Explanation A software error has occurred during the initialization of the STUN Server process and the process will not start.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     STUN_SERVER-2-SS_INTERNAL_FORCED_EXIT: The STUN Server process is 
exiting due to an unexpected internal error condition, resulting from a problem 
with the software (reason: [chars]). 
Explanation The STUN Server process has encountered an unexpected, internal error condition, and must exit. The VQE-S Process Monitor will normally attempt to restart the STUN Server process along with any other affected processes. However, if the condition should recur, the VQE-S may eventually be left in a non-operational state. The text of the error message indicates a more specific reason for the failure. In all cases, this error condition results from a flaw in the software.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.

STUN_SERVER-3
Error Message    STUN_SERVER-3-SS_SYSCALL_ERROR: A system call failed on STUN Server: 
[chars] 
Explanation A system call has failed on the STUN Server. The reason for the failure is provided in the log message.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.

STUN_SERVER-4
Error Message    STUN_SERVER-4-SS_INVALID_OPTION_VALUE: The value [dec] for option 
"[chars]" is out of range and has been ignored. The valid range is [[dec]-[dec]]. 
The default value of [dec] is used instead. 
Explanation One of the option values that has been passed to the STUN Server process at startup time is out of range. The STUN Server process will continue normal operation, though the illegal option value that was passed will be ignored and the default value will be used instead. The error message gives both the option whose value was out of range and the legal range of values for the option.
Recommended Action Refer to the Appendix A, "Configuring VQE-S," for the acceptable range of values for the parameter. Specify the appropriate value for the parameter in the stun_server section of the VQE-S configuration file. Restart the VQE-S application.
Error Message     STUN_SERVER-4-SS_INVALID_OPTION_WARN: Invalid command line option 
"[chars]" is present. 
Explanation An illegal command line option is detected.
Recommended Action Refer to the Appendix A, "Configuring VQE-S," for the valid command line options. Restart the VQE-S application.

STUN_SERVER-6
Error Message    STUN_SERVER-6-SS_STARTUP_COMPLETE_INFO: STUN Server has (re)started 
Explanation This is an informational message logged when the STUN Server finishes startup sequence successfully.
Recommended Action No action is required.

VQES_CP Messages

This section contains VQES_CP messages.

VQES_CP-1
Error Message    VQES_CP-1-CP_XMLRPC_REMOTE_ALERT: CAUTION: INSECURE REMOTE ACCESS TO 
XML-RPC FUNCTIONS ENABLED 
Explanation The remote-xmlrpc command line switch is active, allowing insecure remote access to the xml-rpc server.
Recommended Action Remove the remote-xmlrpc option from the vqes_control_plane section of the vqes.conf file, and restart the VQE-S application.

VQES_CP-2
Error Message    VQES_CP-2-CP_INIT_FAILURE_CRIT: Control Plane initialization failed 
due to [chars] 
Explanation A software error has occurred during the initialization of Control Plane process and the process will not start.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-2-CP_INTERNAL_FORCED_EXIT: The Control Plane process is 
exiting due to an unexpected internal error condition, resulting from a problem 
with the software (reason: [chars]). 
Explanation The Control Plane process has encountered an unexpected, internal error condition, and must exit. The VQE-S Process Monitor will normally attempt to restart the Control Plane process along with any other affected processes. However, if the condition should recur, the VQE-S may eventually be left in a non-operational state. The text of the error message indicates a more specific reason for the failure. In all cases, this error condition results from a flaw in the software.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-2-CP_MISSING_CFG_CRIT: The channel configuration file for 
Control Plane process has not been specified. 
Explanation No channel configuration filename is provided and the Control Plane process will not start.
Recommended Action Refer to Appendix A, "Configuring VQE-S." Specify the cfg option in the vqes_control_plane section of the vqes.conf file. Restart the VQE-S application.

VQES_CP-3
Error Message    VQES_CP-3-CP_CHANNEL_CREATE_ERR: Failed to create a channel due to 
[chars] 
Explanation A software error has occurred during the creation of a channel and the channel will not be created.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-CP_CHANNEL_DELETE_ERR: Failed to delete a channel due to 
[chars] 
Explanation A software error has occurred during the deletion of a channel.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-CP_CHANNEL_UPDATE_ERR: Failed to update the channel 
configuration due to [chars] 
Explanation A software error has occurred during the update of channel configuration and the channel configuration has not being updated.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-CP_CHAN_FSM_ERROR: Per-channel FSM error: [chars] 
Explanation This message logs the errors that occur inside the Control Plane per-channel Finite State Machine. The errors will most likely leave a channel in a state not consistent with the current RTP source state.
Recommended Action If this condition persists, restart the affected channel or restart the VQE-S application.
Error Message     VQES_CP-3-CP_CHAN_FSM_INVALID_EVENT: Per-channel FSM has received an 
invalid event: [chars] 
Explanation This message log the errors that an invalid event is received in the Control Plane per-channel Finite State Machine. The invalid event is ignored.
Recommended Action If this condition persists, restart the affected channel or restart the VQE-S application.
Error Message     VQES_CP-3-CP_INTERFACE_ERR: Failed to find the interface for [chars]. 
Explanation A software error has occurred during finding interface by name.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-CP_MALLOC_ERR: Control Plane failed to allocate necessary 
memory. 
Explanation A software error has occurred during the allocation of memory and the Control Plane process will not start.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-CP_SHUTDOWN_ERR: Control Plane shutdown failed due to 
[chars] 
Explanation A software error has occurred during the shutdown of Control Plane process.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-CP_SOCKET_OPERATION_ERR: Failed to [chars] on socket with 
error [chars]. 
Explanation A software error has occurred during the socket operation.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_DATA_ERROR: Internal data error: [chars] 
Explanation Internal ERA data error is detected. This error message is logged when a data error does not warrant an assertion. For example during stats gathering if a stat structure is null, we will give up on providing counters by logging this message and continue.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_DP_API_FAILURE: Failed to [chars]: return code=[dec] 
Explanation A Data Plane API call has returned error.
Recommended Action Issue the vqereport command to gather data that may help identify the nature of the error. Restart the VQE-S application. If this condition persists, reboot the VQE-S server.
Error Message     VQES_CP-3-ERA_INVALID_PARAMETER: User specified parameter not valid: 
[chars] 
Explanation A user-specified ERA parameter is not valid. ERA component maintains a default value for each parameter. If the specified value is invalid, the default value will be used instead.
Recommended Action Refer to Appendix A, "Configuring VQE-S," for the acceptable range of values for the parameter. Specify the appropriate value for the parameter in the vqes_control_plane section of the VQE-S configuration file. Restart the VQE-S application.
Error Message     VQES_CP-3-ERA_INVALID_RTCP_MSG: Invalid RTCP [chars] message received 
from [chars] 
Explanation Control Plane ERA component has detected that it received an invalid RTCP message within a RTCP compound packet. The ERA component will drop the invalid message. Depending one the message type, a request for Error Repair is ignored (for Generic NACK type) or possible RTP/RTCP retransmission port changes are ignored (for PUBPORTS message)
Recommended Action If this message recurs, use a packet sniffing tool (for example, tshark or tcpdump) to capture RTCP packets from the client indicated in the error message. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_INVALID_RTCP_PKT: Invalid RTCP packet received from 
[chars] - [chars] 
Explanation Control Plane ERA component has detected that it received an invalid RTCP packet. The invalid RTCP packet is dropped and requests for Error Repair are dropped if the dropped packet contains Error Repair requests.
Recommended Action If this message recurs, use a packet sniffing tool (for example, tshark or tcpdump) to capture RTCP packets from the client indicated in the error message. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_LIBEVENT_ERROR: libevent function error: [chars] 
Explanation Error returned from a libevent function. Control Plane makes use of libevent framework to dispatch socket and timer events. This low level libevent error normally means the packet receiving and timer functionality would not work across the channels. In turn, Error Repair would not work across the channels.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_MALLOC_FAILURE: ERA component malloc failure: [chars] 
Explanation Control Plane ERA component memory allocation failure
Recommended Action Issue the vqereport command to gather data that may help identify the nature of the error. Restart the VQE-S application. If this condition persists, reboot the VQE-S server.
Error Message    VQES_CP-3-ERA_RECV_SOCK_SETUP_FAILURE: Failed to create a receiving 
libevent socket on [chars]:[dec]- [chars] 
Explanation This message is logged when the ERA component fails to create a receiving libevent socket. There are different RTCP receiving sockets: one is to receive upstream RTCP packets, one is to receive downstream RTCP packets on the primary RTCP session, and the other is to receive downstream RTCP packets on the repair sessions. Failure to create any one of above receiving sockets will result in no RTCP session being created for a channel, and there will be no Error Repair service for the channel.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_RTCP_CB_ERROR: RTCP callback function failed to 
[chars]: [chars] 
Explanation Error returned from a RTCP utility callback function when trying to add or lookup a member within a RTCP session. The occurrence of this error normally suggests that a repair session (mapped one-to-one to a member) is not available and the Error Repair functionality is not available for the client.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_RTCP_SEND_SOCK_ERROR: Failed to create a socket to send 
RTCP packets from [chars]:[dec]- [chars] 
Explanation This message is logged when ERA component fails to create a socket to send RTCP packets. When this error occurs to a channel, the RTCP session for channel will not be setup to perform Error Repair.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_RTCP_SESSION_CREATION_FAILURE: RTCP session creation 
failure: [chars] 
Explanation ERA component failed to create a RTCP session.
Recommended Action If this message recurs, restart the VQE-S application. Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-3-ERA_RTCP_TIMER_FAILURE: Failed to create a RTCP timer: 
[chars] 
Explanation This message is logged when ERA component fails to create a RTCP timer. When a RTCP timer fails to setup during channel creation, the channel RTCP session will not be created. And there will be no Error Repair functionality available for the channel.
Recommended Action Restart the VQE-S channels. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message    VQES_CP-3-ERA_SOCK_OP_ERROR: Socket operation error: [chars] 
Explanation Control Plane ERA component has encountered an error while doing socket operation.
Recommended Action Issue the vqereport command to gather data that may help identify the nature of the error. Restart the VQE-S application. If this condition persists, reboot the VQE-S server.
Error Message     VQES_CP-3-ERA_TIMER_FAILURE: Failed to create the ERA timer: [chars] 
Explanation This message is logged when ERA component fails to create. the ERA timer. The ERA Timer does the Data Plane upcall event generation number checking and Error Repair rate sampling and calculation. When this timer fails, except for the above functionality, Error Repair will still be functional for all channels.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.

VQES_CP-4
Error Message    VQES_CP-4-CP_BUFFER_SIZE_WARN: Input stream cache size is equal to 
zero. 
Explanation Internal computation has resulted a zero-size buffer.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-4-CP_CHAN_FSM_HANDLE_MISMATCH: Per-channel FSM handle 
mismatch warning: [chars] 
Explanation This message indicates a potential issue inside the Control Plane per-channel Finite State Machine. It is expected and harmless if seen shortly after the VQE-S channel configuration file has been modified. However, if no such change has occurred recently, it may indicate that the channel is not operating correctly.
Recommended Action If this condition persists, restart the affected channel or restart the VQE-S application. Contact your technical support representative and supply the text of this syslog message.
Error Message     VQES_CP-4-CP_INIT_WARN: Control Plane failed to [chars] during the 
initialization. 
Explanation A software error has occurred during the initialization of Control Plane module.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_CP-4-CP_INVALID_OPTION_WARN: Illegal command line option [chars] 
is present. 
Explanation An illegal command line option is detected.
Recommended Action Modify vqes.conf, and restart the VQE-S application.
Error Message     VQES_CP-4-CP_REACH_MAX_WARN: The Control Plane has exceeded the 
maximum allowable size [[dec] channels]. 
Explanation The Control Plane has exceeded the indicated maximum size.
Recommended Action Reduce the number of channels provisioned.
Error Message     VQES_CP-4-CP_VQM_ADDRESS_WARN: 
vqm-address'isdeprecated,pleasereplacewith'vqm-host'inVQE-Sconfigfile'
Explanation A deprecated argument was used in the command line.
Recommended Action Modify vqes.conf, and restart the VQE-S application.
Error Message     VQES_CP-4-CP_VQM_HOST_NAME_WARN: VQM host configuration appears twice 
in config file -- ignoring second vqm-address'
Explanation Multiple entries for the same option are found in the command line.
Recommended Action No action is required.
Error Message     VQES_CP-4-ERA_CHAN_STATE_CHANGED: Changed state to [chars] for 
channel [chars]: [chars] 
Explanation This message indicates the state for a channel has changed, either from inactive to active or from active to inactive. A channel will become inactive when the channel source is no longer available. An inactive channel is not able to provide Error Repair service.
Recommended Action If the channel source state change is expected (for example, the channel is inactive) because the headend is no longer distributing the channel content), then no action is required. If the state change is unexpected, use the VQE-S Application Monitoring Tool to check the status of the channel input stream. If the channel status is not as expected, restart the channel, or restart the VQE-S application. If the channel status remains unexpected, issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.'
Error Message     VQES_CP-4-ERA_WARNING: ERA warning message: [chars] 
Explanation This is a warning message from the Control Plane ERA component. The Error Repair service is not compromised when this condition occurs.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.

VQES_CP-6
Error Message    VQES_CP-6-CP_INIT_COMPLETE_INFO: Control Plane initialization has 
completed successfully. 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_CP-6-CP_UPDATE_COMPLETE_INFO: Control Plane has successfully 
updated the channel configuration. 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_CP-6-CP_UPDATE_INFO: Control Plane is updating a channel - 
[chars] 
Explanation This is an informational message.
Recommended Action No action is required.
Error Message     VQES_CP-6-ERA_INFO: ERA informational message: [chars] 
Explanation This is an informational message from the ERA component.
Recommended Action This is an information message only; no action is required.

VQES_DP_CLIENT Messages

This section contains VQES_DP_CLIENT messages.

VQES_DP_CLIENT-2
Error Message    VQES_DP_CLIENT-2-DPC_CMAPI_ERROR: Communications problem with VQE 
Cache Manager (reason: [chars], linux error: [Linux error]). VQE-S processes must 
restart. 
Explanation A severe error was encountered in the communication between the Cache Manager Client API and the Data Plane process. The process running the client API and other affected processes will be restarted by the VQE-S Process Monitor. If the error should recur, the VQE-S application may be left in a non-operational state. This error normally indicates an internal problem with the software. The text of the error message provides additional detail on the reason for the error and on the associated Linux error message.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQES_DP_CLIENT-2-DPC_CMAPI_INIT_ERROR: Initialization failed 
(reason: [chars], linux error: [Linux error]). 
Explanation A severe error was encountered while attempting to initialize the Cache Manager Client API. The affected process will terminate and be restarted by the VQE-S Process Monitor. However if the failure should recur then the VQE-S application may be left in a non-operational state. The text of the error message provides additional detail on the operation that failed and on the Linux error message associated with the failure.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.

VQES_DP_CLIENT-6
Error Message    VQES_DP_CLIENT-6-DPC_INIT_INFO: Initialization: [chars] 
Explanation The Cache Manager Client API has successfully completed a step in its initialization. Normal operation will continue. The text of the message indicates which step was successfully completed.
Recommended Action This is an information message only; no action is required.

VQES_DP Messages

This section contains VQES_DP messages.

VQES_DP-2
Error Message    VQES_DP-2-DP_CMAPI_ERROR: Error in communications between the Data 
Plane and a client (reason: [chars]). The VQE-S processes will be restarted. 
Explanation Error detected in the Cache Manager Server API communications with the client process. The Data Plane process will exit and must be restarted by the Process Monitor. If the condition recurs, the VQE-S application may be left in a non-operational state. The text of the error message provides a more specific reason for the failure. This failure only results from an internal problem of the software.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQES_DP-2-DP_CMAPI_INIT_FAILURE: Failed to initialize the Cache 
Manager API (reason: [chars], linux error [Linux error]). 
Explanation A critical failure was encountered when initializing the Cache Manager API. The Data Plane process will exit and will be restarted by the VQE-S Process Monitor. If the error recurs on multiple restarts, the VQE-S application may be left in an non-operational state. The text of the error message indicates which step in the initialization process was being performed when the error occurred, and also a standard Linux error message associated with the failed step. In most cases, this type of failure indicates an installation problem with the VQE-S application software or a flaw in the software itself.
Recommended Action Check vqes.conf for any errors; refer to the "VQE-S Configuration File Format and Options" section on page A-4. Modify vqes.conf, and restart the VQE-S application. If changes to the system configuration have been made which are not indicated as part of the standard VQE-S installation and configuration process, remove these configuration changes, then restart the VQE-S application. If this message recurs after correcting any non-standard system configuration, reboot the VQE-S server. Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_DP-2-DP_INIT_FAILURE: Data Plane exiting due to an 
initialization failure (reason: [chars]). 
Explanation The VQE-S Data Plane initialization has failed. The Data Plane process will exit and the VQE-S Process Monitor will attempt to restart it. However, if subsequent initialization attempts also fail, then the VQE-S application may be left in a non-operational state. The reason code indicated within the message may provide a more specific indication of the initialization step that has failed. In most cases, the failure will be due to a problem resulting from a non-standard installation or configuration of the VQE-S application.
Recommended Action Check vqes.conf for any errors; refer to the "VQE-S Configuration File Format and Options" section on page A-4. Modify vqes.conf, and restart the VQE-S application. If changes to the system configuration have been made which are not indicated as part of the standard VQE-S installation and configuration process, remove these configuration changes, then restart the VQE-S application. If this message recurs after correcting any non-standard system configuration, reboot the VQE-S server. Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_DP-2-DP_INTERNAL_FORCED_EXIT: The Data Plane process is exiting 
due to an unexpected internal error condition, resulting from a problem with the 
software (reason: [chars]). 
Explanation The Data Plane process has encountered an unexpected, internal error condition, and must exit. The VQE-S Process Monitor will normally attempt to restart the Data Plane process along with any other affected processes. However, if the condition should recur, the VQE-S application may eventually be left in a non-operational state. The text of the error message indicates a more specific reason for the failure. In all cases, this error condition results from a flaw in the software.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.

VQES_DP-3
Error Message    VQES_DP-3-DP_BAD_ARG: A bad parameter was passed to the Cache Manager 
API (detail: [chars]). 
Explanation A bad parameter was passed to the Cache Manager API by a client process. Additional error messages should indicate the effect of the error. The text of the error message provides additional detail on the bad parameter value.
Recommended Action Perform any actions associated with the additional error messages that occur together with this error message. If any of these actions indicates that you should contact your Cisco technical support representative, then copy this error message exactly as it appears in the VQE-S system log and provide it, in addition to any other requested information, when you contact your technical support representative.
Error Message     VQES_DP-3-DP_BAD_SOCKET_CALL: Linux socket operation failed 
(operation: [chars], linux error: [Linux error]). 
Explanation An operation on a Linux socket has failed. Additional error messages should indicate the consequences of the failure. The text of the error message indicates what operation was being performed when the failure occurred and also the Linux error message associated with the failure.
Recommended Action Perform any actions associated with the additional error messages that occur together with this error message. If any of these actions indicates that you should contact your Cisco technical support representative, then copy this error message exactly as it appears in the VQE-S system log and provide it, in addition to any other requested information, when you contact your technical support representative.
Error Message     VQES_DP-3-DP_CHANNEL_CREATE_FAILED: Failed to create a channel 
(reason: [chars]). 
Explanation The Data Plane failed to create a new channel. The VQE-S will not be able to perform any of its functions for the affected channel, but other channels should not be affected. The reason for the failure is given in the text of the error message. It may be possible to successfully create the channel, through the user interface, without restarting the VQE-S application, once the reason for the failure has been corrected.
Recommended Action Correct the configuration error for the affected channel in the channel lineup provided to the VQE-S application. The reason code included in the error message should provide information which will help to identify the source of the configuration error. In cases where the channel creation failure resulted from a transient condition on the VQE-S rather than from a configuration error in the channel lineup, restart the VQE-S channels.
Error Message     VQES_DP-3-DP_FBT_GEN_ERROR: Error when performing an operation on a 
Feedback Target address (detail: [chars], linux error: [Linux error]). 
Explanation The Data Plane process encountered an error when performing an operation on a Feedback Target address. Additional error messages should indicate whether the condition caused the overall request to fail or whether the Data Plane process was able to take corrective action, and what the consequence of the failure will be. The text of the error message provides more detail on what action was being performed, and on the Linux error condition that was encountered.
Recommended Action Perform any actions associated with the additional error messages that occur together with this error message. If any of these actions indicates that you should contact your Cisco technical support representative, then copy this error message exactly as it appears in the VQE-S system log and provide it, in addition to any other requested information, when you contact your technical support representative.
Error Message     VQES_DP-3-DP_FBT_REQ_ERROR: Failed to complete operation on a 
Feedback Target address: [chars] [chars] [chars]. 
Explanation The Data Plane failed to complete a requested operation on a Feedback Target address. The failure may have left some Feedback Target addresses installed which should have been removed, or may have left some Feedback Target addresses removed which should have been installed. In the case of extra Feedback Target addresses the VQE-S application may advertise services for channels for which it is not actually able to provide service. This may cause VQE-S operations which could have been directed to a different VQE-S to be incorrectly directed to the VQE-S which cannot provide the service. In the case of missing Feedback Target addresses, clients may not be able to send requests to the VQE-S which could have successfully serviced the requests. In either case, some VQE-S operations which could have been successfully completed may fail. The text of the error message identifies the operation that was not completed successfully, the Feedback Target address, and some additional detail on the cause of the failure.
Recommended Action Restart the VQE-S application.
Error Message     VQES_DP-3-DP_INTERNAL_CHANNEL_ERROR: The Data Plane process has 
encountered an internal software problem which may affect the operation of channel 
[chars] (reason: [chars]). 
Explanation The Data Plane process has encountered an error which may prevent the VQE-S application from correctly performing its functions for a single channel. The VQE-S will continue operation, and should correctly perform its functions for other channels. The text of the error message indicates which channel was affected, and also a more specific reason for the problem. In most cases, this type of problem results only from a flaw in the software.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQES_DP-3-DP_ISOL_CPU_FAILURE: A problem occurred associating the 
Data Plane thread with an isolated CPU (reason: [chars]). 
Explanation The Data Plane encountered an error when attempting to assign the high priority data handling thread to an isolated CPU. The Data Plane process will continue to function, though in some cases it may fail to perform error repairs, particularly when heavily loaded, due to contention between non-time-critical system activities and time-critical receipt and transmission of video data. Failure to assign the data handling thread to an isolated CPU may be due to: no CPUs being specified via the isolcpus kernel boot parameter in /boot/grub/grub.conf; specifying an invalid setcpu option value for the VQE-S Data Plane process; or a software installation problem which prevents the Data Plane initialization process from finding an isolated CPU. The text of the error message gives a more specific reason for the failure which should help to determine the more specific cause of the failure.
Recommended Action Check to make sure that the file /boot/grub/grub.conf contains the kernel boot parameter string isolcpus=n, where n is in the range 0..3. If the setcpu option has been specified in the vqes_data_plane section of the vqes.conf file, make sure that its value matches the value specified in the isolcpus parameter string in /boot/grub/conf or remove the parameter from the configuration entirely. Restart the VQE-S application. If the problem persists after performing these recommended actions, copy the error message exactly as it appears in the VQE-S system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_DP-3-DP_MALLOC_FAILURE: Memory allocation of [dec] bytes failed. 
Explanation The Data Plane process failed to allocate memory. Additional error messages should indicate the consequences of the failure.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.

VQES_DP-4
Error Message    VQES_DP-4-DP_BAD_OPTION_VALUE: The value for option "[chars]" provided 
to the Data Plane process is out of range and has been ignored. The valid range 
is [[dec]-[dec]]. 
Explanation One of the option values that has been passed to the Data Plane process at startup time is out of range. The Data Plane process will continue normal operation, though the illegal option value that was passed will be ignored and the default value will be used instead. The error message gives both the option whose value was out of range and the legal range of values for the option.
Recommended Action Modify the vqes.conf file in order to correct the value of the option indicated in the error message so that it lies within the range indicated in the error message. Refer to the "VQE-S Configuration File Format and Options" section on page A-4 for more information on the meanings of specific options and option values. Restart the VQE-S application.
Error Message     VQES_DP-4-DP_BAD_OPTION: The following option provided to the Data 
Plane process is invalid and has been ignored: "[chars]". 
Explanation One of the options that has been passed to the Data Plane process at startup time is not recognized. The Data Plane process will continue normal operation, though the invalid option will be ignored. The option that is not recognized is shown within the error message.
Recommended Action Modify the vqes.conf file in order to correct or remove the option indicated in the error message. Refer to the "VQE-S Configuration File Format and Options" section on page A-4 for more information on the meanings of specific options and option values. Restart the VQE-S application.
Error Message     VQES_DP-4-DP_INIT_WARN: An abnormal condition occurred during Data 
Plane initialization, but VQES operation should continue normally (reason: 
[chars]). 
Explanation An unexpected, though relatively minor, issue has occurred during the initialization of the Data Plane process. The Data Plane should continue to function normally. The text of the error message gives a more specific indication of the error that has occurred.
Recommended Action If this message recurs, restart the VQE-S application. In most cases, normal operation of the VQE-S application should continue. However if this error condition should occur and the VQE-S application does not function correctly, or if the error condition occurs together with more serious error conditions, then copy the error message exactly as it appears in the VQE-S system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_DP-4-DP_REALTIME_WARN: An error occurred which may affect the 
real-time responsiveness of the VQE-S, though it should perform most error repairs 
successfully (reason: [chars]). 
Explanation The Data Plane process encountered an unexpected limitation which may affect its real-time performance. The VQE-S may continue to perform its functions in most cases, but may fail to complete certain operations reliably, particularly when under load. The reason for the failure is given in the text of the message.
Recommended Action Correct any non-standard system configuration or installation that has been performed. Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQES_DP-4-DP_SHUTDOWN_FAILURE: Abnormal condition encountered while 
shutting down Data Plane (reason: [chars], linux error: [Linux error]). 
Explanation A problem was encountered in shutting down the Data Plane process. The VQE-S Process Monitor will normally restart the Data Plane and any other affected processes as required, and normal VQE-S operation should continue. The text of the error message gives more specific information about which step of the shutdown process was being performed when the problem was encountered and also a standard Linux error message associated with the step that failed.
Recommended Action In most cases, the normal operation of the VQE-S application will resume automatically after the Process Monitor restarts the VQE-S application processes, and no further action is required. However if the VQE-S application should fail to resume normal operation after this error message has been seen, then restart the VQE-S application manually.

VQES_DP-5
Error Message    VQES_DP-5-DP_LOST_UPCALL: A notification sent from the Cache Manager 
to a client process was lost (reason: [chars]). Normal operation will continue. 
Explanation A notification message sent from the Cache Manager within the Data Plane to a client process was lost. The client process will detect the loss and re-synchronize its state with the Cache Manager shortly, and normal operation will continue. The client process may react somewhat more slowly than normal to the changed state within the Cache Manager, and as a result the operation of the VQE-S application for a particular channel may be impaired for a few seconds before normal operation for that channel is restored. The text of the error message identifies a more specific reason for the lost message.
Recommended Action No action is required.
Error Message     VQES_DP-5-DP_RTP_INFO_MISSING: Failed to locate RTP information 
(context: [chars]). 
Explanation The RTP code within the Cache Manager failed to locate a requested object. Additional error messages will provide information on the consequences of the failure. In most cases, normal operation will continue.
Recommended Action No action is required.
Error Message     VQES_DP-5-DP_TOO_MANY_SOURCES_GLOBAL: Could not recognize a new 
traffic source for channel [chars] because the Data Plane is already receiving 
from the maximum number of sources that it is able to support across all channels. 
Explanation The Data Plane process has detected incoming RTP traffic from a new source, but must ignore the traffic from that source because it is already receiving traffic from too many other sources, across all channels. The VQE-S may continue normal operation if one of the sources it has already recognized is the desired source, but may fail to operate correctly for the channel if the new source is the one that it should be receiving traffic from. Also, the new source will not be reported by the VQE-S application among its lists of known sources, and this may make troubleshooting of network configuration problems involving multiple sources more difficult. The affected channel is reported in the text of the error message. Other channels are not immediately affected. However, other channels on the system are likely to encounter the same problem as soon as they attempt to recognize new traffic sources. This problem is most likely due to a network configuration issue which causes multiple sources to be sending simultaneously on a single channel.
Recommended Action Correct any network configuration issue which might cause the VQE-S application to be detecting extra sources for any of the channels being received by the VQE-S application.
Error Message     VQES_DP-5-DP_TOO_MANY_SOURCES: Could not recognize a new traffic 
source for channel [chars] because the Data Plane is already receiving from the 
maximum number of sources (limit [dec]) for that channel as may be recognized at 
once for a single channel. 
Explanation The Data Plane process has detected incoming RTP traffic from a new source, but must ignore the traffic from that source because it is already receiving traffic from too many other sources for that channel. The VQE-S may continue normal operation if one of the sources it has already recognized is the desired source, but may fail to operate correctly for the channel if the new source is the one that it should be receiving traffic from. Also, the new source will not be reported by the VQE-S application among its lists of known sources, and this may make troubleshooting of network configuration problems involving multiple sources more difficult. The affected channel is reported in the text of the error message. All other channels are unaffected. This problem is most likely due to a network configuration issue which causes multiple sources to be sending simultaneously on a single channel.
Recommended Action If the VQE-S application is functioning correctly for the channel indicated in the error message, then no action is required. If the VQE-S application is not functioning correctly for the channel indicated in the error message, then correct any network configuration issue which might cause the VQE-S application to be detecting more than one traffic source for the channel indicated in the error message.

VQES_DP-6
Error Message    VQES_DP-6-DP_CHANNEL_CREATE: Successfully created channel [chars]. 
Explanation The Data Plane has successfully created a channel. The channel is identified in the text of the message. The VQE-S will now be able to perform all of its functions for this channel.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_DP-6-DP_FBT_REQ_INFO: Successfully completed operation on 
Feedback Target address: [chars] [chars] [chars]. 
Explanation The Data Plane successfully completed an operation on a Feedback Target address. Normal operation will continue. The completed operation, the Feedback Target address and some additional detail are provided in the message.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_DP-6-DP_INIT_INFO: Initialization: [chars] 
Explanation The Data Plane has successfully completed a step in its initialization. Normal operation will continue. The text of the message identifies the step that was completed, and may also provide additional information that will be useful in tracing the operation of the Data Plane process.
Recommended Action This is an information message only; no action is required.

VQES_MLB_CLIENT Messages

This section contains VQES_MLB_CLIENT messages.

VQES_MLB_CLIENT-2
Error Message    VQES_MLB_CLIENT-2-MLBCLIENT_INIT_ERR: MLB client failed to initialize 
[chars]. 
Explanation MLB client failed to initialize. Application will not function properly.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_MLB_CLIENT-2-MLBCLIENT_LOCK_ERR: MLB client failed to [chars] 
rpc_lock. 
Explanation Error detected during lock operation. Application will not operate properly and must be restarted.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.

VQES_MLB_CLIENT-3
Error Message    VQES_MLB_CLIENT-3-MLBCLIENT_RPC_READ_ERR: MLB client socket read 
error: [chars]. 
Explanation Failed to read data from remote service. MLB client will continue to function but this is abnormal.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_MLB_CLIENT-3-MLBCLIENT_SEND_ERR: MLB client RPC send failed. 
Explanation Failed to send an RPC command to MLB service. Application will not function properly under such condition.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.

VQES_MLB_CLIENT-6
Error Message    VQES_MLB_CLIENT-6-MLBCLIENT_RETURN_CODE: MLB_API got return code: %i. 
Explanation Return code from MLB service, -1 means failure, 0 means success, 1 means recoverable failure, 2 means unrecoverable failure, 3 means invalid command.
Recommended Action This is an information message only; no action is required.

VQES_MLB Messages

This section contains VQES_MLB messages.

VQES_MLB-2
Error Message    VQES_MLB-2-MLB_CLIENT_OVERFLOW: MLB client table is full. 
Explanation MLB has reached its limit on number of clients connected. No new client will be able to connect to MLB before some existing client disconnects. This condition should never occur during normal operation.
Recommended Action Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQES_MLB-2-MLB_CORRUPT_DATA: MLB detected corrupted data structure: 
[chars] 
Explanation MLB detected corrupted data. It should be restarted.
Recommended Action Restart the VQE-S application.
Error Message     VQES_MLB-2-MLB_IFNAME_OVERFLOW: Interface names [chars] exceeds 
maximum length allowed. MLB exit. 
Explanation MLB initialization has failed due to interface name length exceeded maximum length allowed. MLB will abort init.
Recommended Action Refer to the "VQE-S Configuration File Format and Options" section on page A-4 to determine acceptable values for MLB options. Modify vqes.conf, and restart the VQE-S application.
Error Message     VQES_MLB-2-MLB_INIT_FAILURE: MLB initialization has failed: [chars]. 
Explanation Multicast Load Balancer process initialization has failed due to XMLRPC module failure. The process is terminated and need to be investigated.
Recommended Action Process monitor will automatically try to start MLB again. If this message recurs, copy the error message exactly as it appears or in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_MLB-2-MLB_INVALID_INTERVAL: Invalid poll interval: %i, MLB exit. 
Explanation MLB initialization has failed due to invalid poll interval. Operator must correct the configuration file.
Recommended Action Refer to the "VQE-S Configuration File Format and Options" section on page A-4 to determine acceptable values for MLB options. Modify vqes.conf, and restart the VQE-S application.
Error Message     VQES_MLB-2-MLB_INVALID_RESERV: Invalid unicast reservation ratio: %f. 
MLB exit. 
Explanation MLB initialization has failed due to invalid reservation ratio. Operator must correct the configuration file.
Recommended Action Refer to the "VQE-S Configuration File Format and Options" section on page A-4 to determine acceptable values for MLB options. Modify vqes.conf, and restart the VQE-S application.
Error Message     VQES_MLB-2-MLB_INVALID_XMLRPC_PORT: Invalid XML RPC port: %i, MLB 
exit. 
Explanation MLB initialization has failed due to invalid XMLRPC port. Operator must correct the configuration file.
Recommended Action Refer to the "VQE-S Configuration File Format and Options" section on page A-4 to determine acceptable values for MLB options. Modify vqes.conf, and restart the VQE-S application.
Error Message     VQES_MLB-2-MLB_LOCK_FAILURE: MLB failed to [chars] lock: [chars]. 
Explanation MLB failed in a lock operation due to an internal software error. It will not function properly and must be restarted.
Recommended Action Restart the VQE-S application.
Error Message     VQES_MLB-2-MLB_XMLPRC_ADD_ERR: MLB XMLRPC failed to add [chars] 
method to xmlrpc server thread. 
Explanation MLB XML RPC server failed to add a method during init. The XML remote interface will not function properly.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_MLB-2-NETLINK_SOCKET_INIT_ERR: Failed to initialize interface to 
Linux kernel: [chars]. 
Explanation MLB failed to initialize interface to Linux kernel for the specified reason. MLB will not function properly after encountering this error.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.

VQES_MLB-3
Error Message    VQES_MLB-3-MLB_ETHTOOL_ERR: MLB link status monitoring returned error 
for interface [chars]. 
Explanation MLB cannot get parameter for interface for the specified reason. This will make the interface unusable.
Recommended Action Please check your Ethernet hardware and driver and make sure they are working properly. Issue the vqereport command to gather data that may help identify the nature of the error.
Error Message     VQES_MLB-3-MLB_ETHTOOL_UNKOWN_DUPLEX: MLB link status monitoring 
returned unknown duplex status %i for [chars]. 
Explanation MLB link status monitoring failed to recognize link duplex status of an interface. It will not affect MLB but is abnormal.
Recommended Action Please check your Ethernet hardware and driver and make sure they are working properly. Issue the vqereport command to gather data that may help identify the nature of the error.
Error Message     VQES_MLB-3-MLB_ETHTOOL_UNKOWN_SPEED: MLB link status monitoring 
returned unknown link speed %i for interface [chars]. 
Explanation MLB link status monitoring failed to recognize link speed of an interface. The interface cannot be used by MLB.
Recommended Action Please check your Ethernet hardware and driver and make sure they are working properly. Issue the vqereport command to gather data that may help identify the nature of the error.
Error Message     VQES_MLB-3-MLB_IGMP_JOIN_ERR: Failed to join multicast group [chars] 
on interface [chars]: [chars] 
Explanation Failed to join a multicast group. MLB is ignoring the error but this condition is abnormal.
Recommended Action Verify that the multicast address is valid and in use. Verify that the configuration of the indicated interface is correct. If corrections have been made, restart the affected channel. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_MLB-3-MLB_IGMP_LEAVE_ERR: Failed to leave multicast group 
[chars] on interface [chars]: [chars] 
Explanation Failed to leave a multicast group. MLB is ignoring the error but this condition is abnormal.
Recommended Action Restart the VQE-S application. Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_MLB-3-MLB_INACTIVE_INTF: Interface "[chars]" is not up or not 
running. 
Explanation Detected a network interface that is not up or not running; it will be ignored and used later when it is ready.
Recommended Action Refer to Appendix A, "Configuring VQE-S." If the interface was not intended to be used by the VQE-S application, remove its interface name from the interface option in the mlb section of vqes.conf. Otherwise, refer to the "Configuring the Linux Operating System for VQE-S" section on page D-3. Check the configuration of the interface and its status. If not as expected, modify the interface configuration and/or bring up the interface.
Error Message     VQES_MLB-3-MLB_MALLOC_FAILURE: [chars] 
Explanation Multicast Load Balancer process failed to allocate required memory for the reason specified in the error message.
Recommended Action Issue the vqereport command to gather data that may help identify the nature of the error. Check available system memory. Restart the VQE-S application. If the condition persists after VQE-S restart, Reboot the VQE-S server.
Error Message     VQES_MLB-3-MLB_NEG_BANDWIDTH: Invalid parameter: bandwidth must be a 
positive integer for multicast join requests, this request will be abandoned. 
Explanation MLB requires a positive bandwidth for multicast join request. Invalid request will be abandoned.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQES_MLB-3-MLB_NIC_DOWN: Network interface [chars] went down. 
Explanation MLB detected an interface down event. The interface is marked inactive and monitored.
Recommended Action If the interface down event is unexpected, check the interface configuration and status. Make any needed corrections, and bring the interface up.
Error Message     VQES_MLB-3-MLB_NIC_UP: Network interface [chars] came up. 
Explanation MLB detected an interface up event. The interface is marked active and will be used for future requests.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_MLB-3-MLB_NO_BANDWIDTH: No interface has enough bandwidth to 
handle request to join [chars]/[chars], it will be retried by MLB when bandwidth 
is available. 
Explanation MLB does not have enough bandwidth to handle a join request. The request has been queued for retry.
Recommended Action MLB cannot find an interface with enough available bandwidth to service a new channel. If this is due to one or more interface failures, restore the failed interfaces. If interface status is as expected, refer to the "Configuring the Linux Operating System for VQE-S" section on page D-3. Check the interface configuration and interface status of the VQE server. If not as expected, modify the interface configuration and bring up the interfaces. If the interface configuration and status were as expected, check the channel configuration for this server, to verify that the total bandwidth of all channels does not exceed the expected interface capacity. If necessary, modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQES_MLB-3-MLB_NO_IP: Failed to retrieve IP address of interface 
[chars] 
Explanation MLB failed to retrieve an IP address for one interface, and marked it as inactive. MLB will monitor the status of this interface and use it when it becomes active.
Recommended Action Refer to Appendix A, "Configuring VQE-S." If the interface was not intended to be used by the VQE-S application, remove its interface name from the interface 'option in the 'mlb' section of vqes.conf. Otherwise, refer to the "Configuring the Linux Operating System for VQE-S" section on page D-3. Check the configuration of the interface and its status. If not as expected, modify the interface configuration and/or bring up the interface.'
Error Message     VQES_MLB-3-MLB_RECORD_NOT_FOUND: Cannot find multicast group record 
[chars] for removal. 
Explanation MLB cannot find the multicast group in the leave request. The request will be ignored; however, this is abnormal.
Recommended Action Restart the VQE-S application. Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_MLB-3-MLB_RPC_ERR: MLB failed to execute an RPC [chars] request. 
Explanation MLB failed to execute a client request. If the failure is recoverable, MLB will automatically retry. Unrecoverable failures are usually caused by wrong channel configuration.
Recommended Action Verify the channel configuration. Restart the VQE-S channels.
Error Message     VQES_MLB-3-MLB_RPC_RESPONSE_ERR: MLB RPC response failed. 
Explanation MLB failed to send RPC response back to client. This may indicate that the client connection is abnormal.
Recommended Action Restart the VQE-S application.
Error Message     VQES_MLB-3-MLB_RPC_UNKNOWN_CMD: Unknown RPC command: %i. 
Explanation MLB received an unknown RPC command and ignored it.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_MLB-3-MLB_SOCK_INIT_FAILURE: Failed to create MLB mcast socket 
for interface [chars] 
Explanation MLB multicast socket initialization failed for an interface; as a result it has been marked inactive. MLB will automatically retry it later.
Recommended Action Restart the VQE-S application. If the condition persists after VQE-S restart, Reboot the VQE-S server.
Error Message     VQES_MLB-3-MLB_UNKOWN_OPTION: MLB ignored unrecognized option: 
[chars]. 
Explanation MLB detected unrecognized option and ignored it.
Recommended Action Refer to Appendix A, "Configuring VQE-S," to determine acceptable MLB configuration options. Modify vqes.conf, and restart the VQE-S application.
Error Message     VQES_MLB-3-NETLINK_SOCKET_BIND_ERR: Failed to bind interface to Linux 
kernel: [chars]. 
Explanation MLB failed to bind interface to Linux kernel for the specified reason. MLB will not function properly after encountering this error.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQES_MLB-3-NETLINK_SOCKET_SEND_ERR: Failed to send message to Linux 
kernel: [chars]. 
Explanation MLB failed to send a message to Linux kernel for the specified reason. MLB will not function properly after encountering this error.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.

VQES_MLB-4
Error Message    VQES_MLB-4-MLB_CLIENT_DISCONNECT: Client %i disconnected 
unexpectedly, there might be some stale multicast memberships. 
Explanation MLB detected an unexpected client disconnect. This should not happen during normal VQES operation and may leave stale multicast memberships and waste bandwidth.
Recommended Action Restart the VQE-S application.
Error Message     VQES_MLB-4-MLB_ETHTOOL_HALF_DUPLEX: Link [chars] is running in 
half-duplex mode. 
Explanation MLB detected link is running in half-duplex mode. This does not affect function but does affect performance.
Recommended Action If half-duplex mode is not expected, check the wire and remote port configuration. Issue the vqereport command to gather data that may help identify the nature of the error.
Error Message     VQES_MLB-4-MLB_IP_CHANGE: Detected IP address change from [chars] to 
[chars] on interface [chars] 
Explanation MLB detected an IP address change on one interface.
Recommended Action This is an information message only; no action is required.

VQES_MLB-6
Error Message    VQES_MLB-6-MLB_ETHTOOL_FULL_DUPLEX: Link [chars] is running in 
full-duplex mode. 
Explanation MLB detected link is running in full-duplex mode.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_MLB-6-MLB_JOIN_MULTICAST: Joined multicast group [chars]/[chars] 
on interface %i: [chars] 
Explanation MLB joined new multicast membership.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_MLB-6-MLB_NEW_CLIENT: Connected new client with socket id: %i 
Explanation MLB accepted a new client.
Recommended Action This is an information message only; no action is required.

VQES_PM Messages

This section contains VQES_PM messages.

VQES_PM-2
Error Message    VQES_PM-2-PM_CFG_FAILURE: Missing or invalid information in 
configuration file: [chars] 
Explanation Missing or invalid information detected while parsing the configuration file. The error string will provide greater detail on the specific error that occurred. The VQE-S application could not be successfully started.
Recommended Action Refer to Appendix A, "VQE-S Configuration File Location and Editing," and perform the indicated corrective actions. Restart the VQE-S application.
Error Message     VQES_PM-2-PM_CFG_FILE_MISSING: Cannot open configuration file [chars] 
Explanation The VQE-S Configuration File is missing or has incorrect permissions. The VQE-S application could not be successfully started.
Recommended Action Refer to the "VQE Files, Directories, and Permissions" section on page 5-3 for information on correcting permissions and replacing lost files, and perform the indicated corrective actions. Restart the VQE-S application.
Error Message     VQES_PM-2-PM_CFG_PARSE_FAILURE: Configuration file syntax error 
"[chars]" on line [dec] in file [chars] 
Explanation Process Monitor encountered the specified syntax error on the line specified. The VQE-S application could not be successfully started.
Recommended Action Refer to the "VQE-S Configuration File Location and Editing" section on page A-3, and perform the indicated corrective actions. Restart the VQE-S application.
Error Message     VQES_PM-2-PM_CRIT_ERROR: Process Monitor exiting due to error: 
[chars] 
Explanation Critical error in Process Monitor. Process Monitor has encountered an internal error from which it cannot recover.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_PM-2-PM_INIT_FAILURE: Process Monitor initialization has failed 
for the specified reason: [chars] 
Explanation Process Monitor initialization has failed. A reason code describes the specific error encountered. A common cause is insufficient user permissions.
Recommended Action Process Monitor may not be running with proper permissions. Refer to the "VQE Files, Directories, and Permissions" section on page 5-3 for information on correcting permissions and replacing lost files, and perform the indicated corrective actions. Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_PM-2-PM_INIT_START: Process Monitor has (re)started 
Explanation This message is used to indicate that the VQE-S Health Monitoring Application has just been (re)started. This is either expected behavior from starting the Process Monitor or PM exited unexpectedly and has restarted.
Recommended Action If the VQE-S application has just been manually started, or the VQE-S server has just come up, no action is required. Otherwise, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQES_PM-2-PM_PROC_START_FAILURE: Could not start [chars] 
Explanation Process Monitor could not start the specified process.
Recommended Action This executable file for the specified process may be missing or have incorrect permissions. Refer to the "VQE Files, Directories, and Permissions" section on page 5-3 for information on correcting permissions and replacing lost files, and perform the indicated corrective actions. Restart the VQE-S application.
Error Message     VQES_PM-2-PM_PROC_STOP_FAILURE: Could not stop [chars] 
Explanation Process Monitor could not stop the specified process. The process is being stopped because another process stopped or a shutdown was requested.
Recommended Action Reboot the VQE-S server.

VQES_PM-3
Error Message    VQES_PM-3-PM_NONCRIT_ERROR: Process Monitor continuing after internal 
error: [chars] 
Explanation Process Monitor encountered a potentially recoverable error and is continuing to run.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQES_PM-3-PM_PROCESS_POST_FAIL: Post-processing for process [chars] 
did not complete 
Explanation The post-processing command for the specified process did not complete successfully. This often indicates that some feedback target addresses were not removed properly from the routing table.
Recommended Action Use the VQE-S Application Monitoring Tool to enable the PM_DEBUG_PROC_ERR and PM_DEBUG_PROC_DETL debug flags. After the log message recurs, issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. Reboot the VQE-S server.
Error Message     VQES_PM-3-PM_PROCESS_STOPPED: Process [chars] has stopped, attempting 
to restart it. 
Explanation The specified process has exited. Process Monitor will attempt to restart.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information.

VQES_PM-4
Error Message    VQES_PM-4-PM_ALREADY_RUNNING: Process Monitor is already running. 
Explanation An attempt was made to start further instances of Process Monitor while one is already running.
Recommended Action This is an information message only; no action is required.

VQES_PM-6
Error Message    VQES_PM-6-PM_EXIT: Process Monitor Exiting 
Explanation Process Monitor exiting. This message will be seen whenever Process Monitor exits if a shutdown has been requested or if an unrecoverable error has occurred.
Recommended Action This is an information message only; no action is required.
Error Message     VQES_PM-6-PM_RESTART_SUCCESS: Successfully restarted [chars] 
Explanation The specified process was successfully restarted by Process Monitor.
Recommended Action This is an information message only; no action is required.

VQES_CFG Messages

This section contains VQES_CFG messages.

VQES_CFG-2
Error Message    VQE_CFG-2-CFG_CREATE_HASH_TABLE_CRIT: Failed to create the hash table 
for session keys. 
Explanation A software error involving creation of hash table has occurred.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_CFG-2-CFG_FILE_OPEN_CRIT: Failed to open channel configuration 
file [chars]. 
Explanation The channel configuration file either does not exist or has no read permission.
Recommended Action Check the location or the permissions of the channel configuration file and make any necessary corrections.
Error Message     VQE_CFG-2-CFG_FILE_READ_CRIT: Failed to process channel configuration 
file [chars]. 
Explanation A software error has occurred during the processing of the channel configuration file.
Recommended Action Check the contents of the channel configuration file and make any necessary corrections.

VQES_CFG-3
Error Message    VQE_CFG-3-CFG_CREATE_KEY_ERR: The channel configuration module failed 
to create or add the key [chars] to the hash table. 
Explanation A software error has occurred during the key creation.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_CFG-3-CFG_DELETE_KEY_ERR: The channel configuration module failed 
to delete the key [chars] from the hash table. 
Explanation A software error has occurred during the key deletion.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_CFG-3-CFG_DESTROY_ALL_ERR: Failed to destroy all the channel 
configuration data. 
Explanation A software error has occurred during the cleanup of the channel configuration data structure.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_CFG-3-CFG_FILE_CLOSE_ERR: Failed to close the channel 
configuration file [chars]. 
Explanation A software error has occurred during the close of the channel configuration file.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_CFG-3-CFG_FILE_WRITE_ERR: Failed to write the channel 
configuration file [chars]. 
Explanation A software error has occurred during the writing of the channel configuration file.
Recommended Action Check the permissions of the channel configuration file and make any necessary corrections.
Error Message     VQE_CFG-3-CFG_MALLOC_ERR: The channel configuration module failed to 
allocate memory. 
Explanation A software error has occurred during the allocation of memory.
Recommended Action Restart the VQE-S application. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_CFG-3-CFG_SAVE_ERR: The channel configuration file [chars] does 
not have write permission. 
Explanation The channel configuration file has insufficient file permissions.
Recommended Action Check the permissions of the channel configuration file and make any necessary corrections.
Error Message     VQE_CFG-3-CFG_VALIDATION_ERR: Channel [chars] failed validation due 
to [chars] 
Explanation Channel configuration data failed semantic validation.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.

VQES_CFG-4
Error Message    VQE_CFG-4-CFG_ADD_TO_MAP_WARN: Failed to add channel [chars] to the 
channel map. 
Explanation A software error has occurred during the addition of a channel to the channel map.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_CFG-4-CFG_ADD_WARN: Failed to add channel [chars] to the channel 
manager. 
Explanation A software error has occurred during the addition of a channel to the channel manager.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_CFG-4-CFG_DELETE_WARN: Failed to delete a channel from the channel 
manager. 
Explanation A software error has occurred during the deletion of a channel from the channel manager.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_CFG-4-CFG_DUPLICATED_FBT_ADDR_WARN: Channel [chars] has the same 
feedback target address or port as other channels. 
Explanation The same feedback target address or port is used by more than one channel in the channel configuration file.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_CFG-4-CFG_DUPLICATED_RTX_ADDR_WARN: Channel [chars] has the same 
retransmission address or port as other channels. 
Explanation The same retransmission address or port is used by more than one channel in the channel configuration file.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_CFG-4-CFG_DUPLICATED_SRC_ADDR_WARN: Channel [chars] has the same 
original source address or port as other channels. 
Explanation The same source address or port is used by more than one channel in the channel configuration file.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_CFG-4-CFG_ILLEGAL_SDP_SYNTAX_WARN: Illegal SDP syntax: [chars] 
Explanation The specified SDP description has illegal syntax.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_CFG-4-CFG_NO_FILE_WARN: The channel configuration file [chars] 
does not exist. 
Explanation The channel configuration file cannot be found.
Recommended Action Check the location of the channel configuration file and make any necessary corrections.
Error Message     VQE_CFG-4-CFG_NO_SESSION_DIVIDER_WARN: The channel configuration does 
not contain a session divider 
Explanation Each channel configuration data must be separated by a session divider in the channel configuration file. Otherwise, a channel configuration might be skipped during data parsing.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_CFG-4-CFG_REACH_MAX_WARN: The channel configuration data has 
exceeded the maximum allowable size [[dec] channels]. 
Explanation The channel configuration data has exceeded the indicated maximum size.
Recommended Action Reduce the number of channels provisioned.
Error Message     VQE_CFG-4-CFG_REMOVE_FROM_MAP_WARN: Failed to remove channel [chars] 
from the channel map. 
Explanation A software error has occurred during the remove of a channel from the channel map.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_CFG-4-CFG_SDP_PARSE_WARN: Failed to parse SDP content due to 
[chars] 
Explanation A parsing error has occurred during the parse of a channel configuration data from SDP syntax.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_CFG-4-CFG_VALIDATION_WARN: Channel [chars] failed validation due 
to [chars] 
Explanation Channel configuration data failed semantic validation.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.

VQES_CFG-6
Error Message    VQE_CFG-6-CFG_CLOSE_COMPLETED_INFO: Configuration module is 
successfully shutdown. 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.
Error Message     VQE_CFG-6-CFG_INIT_COMPLETED_INFO: Configuration module is 
successfully initialized. 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.
Error Message     VQE_CFG-6-CFG_UPDATE_COMPLETED_INFO: Configuration module is 
successfully updated. 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.

VQES_HASH Messages

This section contains VQES_HASH messages.

VQES_HASH-3
Error Message    VQE_HASH-3-VQE_HASH_BAD_ARG: A bad parameter was passed to the hash 
table API (detail: [chars]). 
Explanation A bad parameter was passed to the hash table API by a client process. The text of the error message provides additional detail on the bad parameter value.
Recommended Action Perform any actions associated with the additional error messages that occur together with this error message. If any of these indicates that you should contact your Cisco technical support representative, then copy this error message exactly as it appears in the VQE-S system log and provide it, in addition to any other requested information, when you contact your technical support representative.
Error Message     VQE_HASH-3-VQE_HASH_INSERT_FAILURE: Insertion of an element into the 
hash table failed (detail [chars]) 
Explanation Insertion of an element into the hash table by a client process failed. The text of the error message provides additional detail on the cause of the failure
Recommended Action Perform any actions associated with the additional error messages that occur together with this error message. If any of these indicates that you should contact your Cisco technical support representative, then copy this error message exactly as it appears in the VQE-S system log and provide it, in addition to any other requested information, when you contact your technical support representative.
Error Message     VQE_HASH-3-VQE_HASH_MALLOC_FAILURE: Memory allocation for hash table 
data structures failed, (detail [chars]) 
Explanation The hash table API failed to allocate memory. The text of the error message provides additional detail on the failure.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQE_HASH-3-VQE_HASH_REMOVE_FAILURE: Removal of a requested element 
from the hash table failed (detail [chars]) 
Explanation The requested removal of an element from the hash table by a client process failed. The text of the error message provides additional detail on the cause of the failure
Recommended Action Perform any actions associated with the additional error messages that occur together with this error message. If any of these indicates that you should contact your Cisco technical support representative, then copy this error message exactly as it appears in the VQE-S system log and provide it, in addition to any other requested information, when you contact your technical support representative.

VQES_RTP Messages

This section contains VQES_RTP messages.

VQES_RTP-2
Error Message    VQE_RTP-2-RTCP_MEM_INIT_FAILURE: Failed to initialize RTCP memory pool 
[chars] 
Explanation The initialization of the specified RTCP memory pool has failed; the application (for example, ERA) using the pool, which is specified as part of the pool name, will not function correctly.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the vqereport command output, contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application. If this message recurs after restart, reboot the VQE-S server.
Error Message     VQE_RTP-3-EXP_CONFIG_ERROR: Exporter failed to initialize due to 
invalid or missing configuration; reason: [chars] 
Explanation The Exporter failed to initialize because Exporter configuration information is either missing from or incorrect in the VQE-S application configuration file (vqes.conf). The reason string identifies which parameter is missing or invalid.
Recommended Action Refer to Appendix A, "Configuring VQE-S" to determine acceptable options and parameter values. Modify vqes.conf, and restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_EXPORT_FAIL_BAD_INPUT: Exporter failed to export a 
packet due to bad input argument; function: [chars], bad argument: [chars], 
argument value: [dec] 
Explanation The Exporter failed to export a packet because it was called with an invalid input argument.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_EXPORT_FAIL_BAD_RETURN: Exporter failed to export a 
packet due to bad return value: calling function: [chars], called function: 
[chars], returned value: [dec] 
Explanation The Exporter failed to export a packet because it received a bad return code from an internal function call.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_EXPORT_FAIL_INVALID_STATE: Exporter failed to export a 
packet due to being called while in an invalid state; function called: [chars], 
current state: [dec] 
Explanation The Exporter failed to export a packet because its export function was called while the Exporter was in an invalid state.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_EXPORT_FAIL_TOO_BIG: Exporter failed to export 
oversized RTCP report of [dec] bytes. Maximum allowed size is [dec] 
Explanation The Exporter failed to export an RTCP packet because it was larger than the maximum allowable size. Other packets will continue to be exported.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_RTP-3-EXP_INIT_FAIL_BAD_RETURN: Exporter failed to initialize due 
to unexpected return value: calling function: [chars], called function: [chars], 
returned value: [dec] 
Explanation The Exporter failed to initialize because it received an undefined return code from an internal function call. The Exporter will periodically retry the initialization, but if this condition persists, the Exporter will not function.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_INIT_FAIL_RETRY: Exporter failed to initialize due to 
a potentially temporary condition; reason: [chars] 
Explanation The Exporter failed to initialize due to a potentially temporary system condition such as lack of available memory, or failure to start a timer. The Exporter will periodically retry its initialization, but if this condition persists, the Exporter will not function.
Recommended Action If this condition persists, contact your Cisco technical support representative, provide the representative with this error message exactly as it appears in the VQE-S system log, and restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_INIT_FAIL_SOCKET_INIT: Exporter failed to initialize 
due to an error creating or initializing the TCP socket; failed operation: [chars], 
failure reason: [chars] 
Explanation The Exporter failed to initialize because it received an error from a system socket initialization function call. The Exporter will periodically retry the initialization, but if this condition persists, the Exporter will not function.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_SHUTDOWN_ERROR: Exporter experienced an error on 
shutdown; function called: [chars], shutdown operation being performed: [chars] 
Explanation The Exporter received an error return code from an internal function called during shutdown.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_SOCKET_CLEANUP_ERROR: Exporter experienced an error on 
socket cleanup; function called: [chars], cleanup operation being performed: 
[chars] 
Explanation The Exporter received an error return code from an internal function called during socket cleanup. This error is likely benign.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_UI_FAIL_BAD_INPUT: Exporter failed to return status 
information to the user interface due to bad input argument; function called: 
[chars], bad argument: [chars], argument value: [dec] 
Explanation The Exporter failed to respond to a query from the user interface because it was called with an invalid input argument.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_UI_FAIL_INVALID_STATE: Exporter failed to return status 
information to user interface due to being called when in an undefined state; 
function called: [chars], current state: [dec] 
Explanation The Exporter failed to respond to a query from the user interface because its UI function was called when Exporter was in an undefined state.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-EXP_UI_FAIL_UNINIT_STATE: Exporter failed to return status 
information to user interface due to being called before it has initialized; 
function called: [chars]. 
Explanation The Exporter failed to respond to a query from the user interface because its UI function was called before Exporter was initialized.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.
Error Message     VQE_RTP-3-RTCP_CNAME_ROLLBACK_FAILURE: Rollback failure: could not 
restore the member of session [chars]:[dec] with SSRC [hex] CNAME [chars] back to 
the member database, after a failure to update the CNAME to [chars] 
Explanation An attempt to restore a member back to the per-session member database, with its original CNAME, has failed, after an attempt to update the CNAME has failed. In nearly all cases, this is due to an internal software error. If this condition persists, messages from the member (for example, repair requests) may not be processed correctly.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQE_RTP-3-RTCP_CNAME_UPDATE_FAILURE: Could not update the member of 
session [chars]:[dec] with SSRC [hex] from CNAME [chars] to CNAME [chars]: [chars] 
Explanation An attempt to update the CNAME of a member of the specified session failed, for the indicated reason. In nearly all cases, this is due to an internal software error. If this condition persists, messages from the member (for example, repair requests) may not be processed correctly.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQE_RTP-3-RTCP_LOCAL_SSRC_UPDATE_FAILURE: Could not update the local 
SSRC of [chars] session [chars]:[dec] from SSRC [hex] to SSRC [hex] 
Explanation An attempt to update the local SSRC of the specified session has failed. In nearly all cases, this is due to an internal software error. If this condition persists, services of this session (for example, RTCP report generation) may not function properly.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.
Error Message     VQE_RTP-3-RTCP_SSRC_ROLLBACK_FAILURE: Rollback failure: could not 
restore the member of session [chars]:[dec] with SSRC [hex] CNAME [chars] back to 
the member database, after a failure to update the SSRC to [hex] 
Explanation An attempt to restore a member back to the per-session member database, with its original SSRC, has failed, after an attempt to update the SSRC has failed. In nearly all cases, this is due to an internal software error. If this condition persists, messages from the member (for example, repair requests) may not be processed correctly.
Recommended Action If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. Restart the VQE-S application.

VQES_RTP-4
Error Message    VQE_RTP-4-EXP_DUPLICATE_INIT: Duplicate initialization of Exporter; 
routine called: [chars] current state: [dec] 
Explanation An Exporter initialization routine has been called more than once; duplicate calls are ignored.
Recommended Action Copy the error message exactly as it appears in the VQE-S system log. Issue the vqereport command to gather data that may help identify the nature of the error. Contact your Cisco technical support representative, and provide the representative with the gathered information. If this message recurs, restart the VQE-S application.

VQES_RTSP Messages

This section contains VQES_RTSP messages.

VQES_RTSP-43
Error Message    VQE_RTSP-3-RTSP_FILE_PARSE_ERR: The channel configuration file [chars] 
is not parseable. 
Explanation The channel configuration file for VCDS failed to pass parsing and validation.
Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide. Modify the channel configuration, and resend it to the VQE-S and/or VCDS servers.
Error Message     VQE_RTSP-3-RTSP_FILE_READ_ERR: The channel configuration file [chars] 
is not readable. 
Explanation The channel configuration file for VCDS does not have read permission.
Recommended Action Check the location or permissions of the channel configuration file and make any necessary corrections.
Error Message     VQE_RTSP-3-RTSP_FILE_WRITE_ERR: The channel configuration file 
[chars] is not writable. 
Explanation The channel configuration file for VCDS does not have write permission.
Recommended Action Check the permissions of the channel configuration file and make any necessary corrections.
Error Message     VQE_RTSP-3-RTSP_INIT_ERR: VCDS initialization has failed due to 
[chars] 
Explanation VCDS initialization has encountered an error and will not be available for use.
Recommended Action Check the reason in the system error message. Modify VCDServer.cfg if necessary, and restart the VQECCfgDeliveryServer process. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message     VQE_RTSP-3-RTSP_MALLOC_ERR: VCDS failed to malloc necessary memory 
for internal use. 
Explanation A software error has occurred during the memory allocation and VCDS will not be available for use.
Recommended Action Restart the VQECCfgDeliveryServer process. If this message recurs, copy the error message exactly as it appears in the VQE-S system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.

VQES_RTP-5
Error Message    VQE_RTSP-5-RTSP_CHANNEL_NOTICE: VCDS reads in [dec] channels [[dec] 
bytes]. 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.
Error Message     VQE_RTSP-5-RTSP_CHANNEL_UPDATE_NOTICE: VCDS receives a channel lineup 
update ... 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.
Error Message     VQE_RTSP-5-RTSP_NAME_PORT_NOTICE: VCDS is running on server [chars] 
and using port [dec]. 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.
Error Message     VQE_RTSP-5-RTSP_NO_CHANNEL_NOTICE: No channel data exists in [chars]. 
Explanation This is an informational message.
Recommended Action This is an information message only; no action is required.