VQE System Messages and Recovery Procedures

This file lists and describes the Cisco VQE system messages and recovery procedures. The VQE software writes these messages to the following locations:

On VQE-S and VQE Tools servers, VQE system messages are written to the /var/log/vqe/vqe.log file.
VQE Client Channel Configuration Delivery Server (VCDS) system messages are also written to the /var/log/vqe/vqe.log 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 Cisco CDA Visual Quality Experience Application User Guide.

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. The following table lists the VQE facility codes.

Code	VQE Facility
STUN_SERVER	STUN Server (VQE-S)
VQES_CP VQE-S	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_CFGTOOL	VQE Configuration Tool (vqe_cfgtool command)
VQE_CFG	VQE channel configuration
VQE_UTILS	VQE Utilities
VQE_RPC	VQE-S Remote Procedure Call facility
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. Messages of severity 7 (Debugging) are not described in this appendix. The message severity levels are as follows:

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 appears 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]. The following table lists the 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. The following table provides references to where you can find more information on these recovery procedures.

Note: In the following table, all references are to sections found in the Cisco CDA Visual Quality Experience Application User Guide .

Recovery Procedure in Recommended Action	Notes and Where to Find Information
Reboot the VQE-S server.	See the "Restarting the System and Verifying System and VQE-S Status" section in Appendix D.
Restart the VQE-S application.	See the "Stopping, Starting, and Restarting VQE-S" section in Chapter 5.
Restart the VQE-S channels.	In VCPT, use the Force Update button to send channel information to the VQE Server. See the "Force Update Button" section in Chapter 3.
Modify the channel configuration and resend it to the VQE Servers and/or VCDS servers.	See Chapter 3, "Using the VQE Channel Provisioning Tool."
Modify vcdb.conf and apply the configuration.	For VQE configuration (vcdb.conf) information, see Chapter 6, "Configuring VQE Server and VQE Tools." For information on applying a VQE configuration with the -apply option to vqe_cfgtool, see the "Using the Configuration Tool Command-Line Options" section in Chapter 6.
Issue the vqereport command to gather data that may help identify the nature of the error.	See the “Using the vqereport Command” section in Chapter 5.

STUN_SERVER Messages

This section contains the 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 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 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.

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 Specify the appropriate value for the parameter in the stun_server section of the VQE-S configuration file. Refer to the Cisco CDA Visual Quality Experience Application User Guide for information on configuring VQE-S. Modify vcdb.conf and apply the configuration. If the condition persists, contact your Cisco technical support representative, and provide the representative with the gathered information.

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 Cisco CDA Visual Quality Experience Application User Guide for information on configuring VQE-S. Modify vcdb.conf and apply the configuration. If the condition persists, contact your Cisco technical support representative, and provide the representative with the gathered information.

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 the 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 parameter from the vcdb.conf file and apply the config.

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.

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.

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.

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 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.

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 been updated.

Recommended Action Refer to the Cisco CDA Visual Quality Experience Application User Guide for channel configuration information. 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 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.

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.

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.

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.

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 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. Correct the error (if possible). Restart the VQE-S application. If this condition persists, reboot the VQE-S server.

Error Message VQES_CP-3-ERA_INIT_FAILURE: ERA component initialization failure: [chars]

Explanation Control Plane ERA component failed initialization

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.

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 on the message type, a request for Error Repair or Rapid Channel Change is ignored, or possible RTP/RTCP retransmission port changes are ignored (for PUBPORTS message)

Recommended Action If this message recurs, use a packet sniffing tool (e.g., 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 or Rapid Channel Change are dropped if the dropped packet contains Error Repair or Rapid Channel Change requests.

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 or Rapid Channel Change would not work across the channels.

Error Message VQES_CP-3-ERA_MALLOC_FAILURE: ERA component malloc failure: [chars]

Explanation Control Plane ERA component memory allocation failure

Error Message VQES_CP-3-ERA_RCC_ERROR: Rapid Channel Change error: [chars]

Explanation Error occurred in Control Plane ERA component while servicing a Rapid Channel Change request.

Error Message VQES_CP-3-ERA_RCC_INT_ERROR: ERA internal error during an RCC: [chars]

Explanation An internal error occurs during an RCC processing.

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 pkts 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 or Rapid Channel Change service for the channel.

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 that Error Repair or Rapid Channel Change functionality is not available for the client.

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 or Rapid Channel Change .

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 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 the 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 or Rapid Channel Change 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 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_SEND_PKT_FAILURE: Failed to send a [chars] packet to [chars]

Explanation Control Plane ERA component failed to send a packet to a client. The RTCP NULL APP packet indicates that Rapid Channel Change (RCC) is not feasible at this time. Failure to send a NULL APP packet means the client will have to wait for some extra amount of time, i.e. APP timeout, before it starts a normal channel change. Failure to send a RTCP APP packet during RCC processing means the client will not be able to perform an RCC; it will perform a normal channel change instead, after the APP timeout interval.

Recommended Action If this condition persists, restart the VQE-S application. If this condition persists after restart, reboot the VQE-S server.

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.

Error Message VQES_CP-3-ERA_TIMER_FAILURE: Failed to create the ERA timer: [chars]

Explanation This message is logged when the 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 and Rapid Channel Change will still be functional for all channels.

VQES_CP-4

Error Message VQES_CP-4-CP_BUFFER_SIZE_WARN: Input stream cache size is equal to zero for channel [chars].

Explanation Internal computation has resulted a zero-size buffer.

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, reset 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_CONFIG_CONFLICT_NO_RL: Inconsistent configuration: [chars]

Explanation Configuration conflict is found at startup time. For example, when RCC is disabled on VQE-S but enabled on a channel, or when VQE-S is set to use Aggressive RCC Mode but ER is disabled on a channel.

Error Message VQES_CP-4-CP_CONFIG_CONFLICT_SLOW: Inconsistent configuration: [chars]

Explanation Configuration conflict is found. For example, when VQE-S is in Aggressive RCC Mode but ER is disabled on a channel; or when max-client-bw is set such than the calculated e-factor is lower than the minimum value for a channel

Recommended Action If this condition persists, restart the affected channel or restart the VQE-S application.

Error Message VQES_CP-4-CP_DEPRECATED_OPTION_WARN: Deprecated command line option found: [chars].

Explanation A deprecated command line option is found in the vqes_control_plane section of the .vqes.conf file.

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.

Error Message VQES_CP-4-CP_INVALID_OPTION_WARN: Illegal command line option found: [chars] is ignored.

Explanation An illegal command line option has been detected in the vqes_control_plane section of the .vqes.conf file.

Recommended Action Investigate and fix any error in .vqes.conf. Refer to the Cisco CDA Visual Quality Experience Application User Guide for information on configuring VQE-S. Modify vcdb.conf and apply the configuration. If the condition persists, contact your Cisco technical support representative, and provide the representative with the gathered information.

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_REMOVE_CHN_WARN: The Control Plane has removed the channel - [chars]

Explanation The Control Plane has removed a channel based on the channel configuration.

Recommended Action No action is required.

Error Message VQES_CP-4-CP_VQM_ADDRESS_WARN: 'vqm-address' is deprecated, please replace with 'vqm-host' in VQE-S config file

Explanation A deprecated argument was used in the command line.

Error Message VQES_CP-4-CP_VQM_HOST_NAME_WARN: VQM host configuration appears twice in config file -- ignoring second 'vqm-address =' or 'vqm-host =' line in VQE-S config file

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_ADD_BITMAP_RB_FAILED: Failed to add bitmap repair burst for client [chars] on channel [chars]:[dec] - return code=[dec]

Explanation Error reported from the Data Plane that an Error Repair repair burst is not able to be scheduled. This would normally happen when the number of active ER requests is larger than a value (20) set on the system, which suggests that the packet drop on the client access link is very bursty.

Recommended Action If this occurs frequently, you many want to contact your Cisco technical support representative.

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 or Rapid Channel Change service.

Recommended Action If the channel source state change is expected (e.g., 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, reset the channel, or restart the VQE-S application. If the channel status remains unexpected, issue the vqereport command to gather data the 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_CLIENT_PKT_TB_RATE_LIMITED: Per-client packet policer has dropped [dec] repair packets ([dec] bitmaps) for client [chars] on channel [chars]:[dec]

Explanation Error Repair requests from a STB client are rate limited by the per-client packet policer whose parameters are configurable via the VQE-S configuration file.

Recommended Action Understand the STB packet drop pattern and tune the per-client policer parameter values if necessary.

Error Message VQES_CP-4-ERA_DROP_ER_REQUEST_INVALID_E: No excess bandwidth available for client [chars] on channel [chars]:[dec]: dropped [dec] bitmaps and [dec] repair packets

Explanation Error Repair requests from a STB client are dropped since no excess bandwidth is available for the client.

Recommended Action Make sure the excess bandwidth fraction (also known as e-factor) is configured properly on VQE-S. If max-client-bw is configured on VQE-S, make sure that it is at least 5% over the highest bit rate of the VQE-S channels.

Error Message VQES_CP-4-ERA_GLOBAL_BITMAP_TB_RATE_LIMITED: Global bitmap policer has dropped [dec] ER bitmaps ([dec] repair packets) for client [chars] on channel [chars]:[dec]

Explanation The aggregated ER bitmap request rate has exceeded the limiting rate set for the global ER bitmap policer, which is set at 10K bitmaps/second.

Recommended Action Reduce the aggregated ER bitmap request rate at the VQE Server, for example, by adding VQE Servers to distribute the ER request load. You many want to contact your Cisco technical support representative to discuss the solution.

Error Message VQES_CP-4-ERA_GLOBAL_PKT_TB_RATE_LIMITED: Global packet policer has dropped [dec] repair packets ([dec] bitmaps) for client [chars] on channel [chars]:[dec]

Explanation The aggregated ER packet request rate has exceeded the limiting rate set for the global ER packet policer, which is set at 50K pkts/second.

Recommended Action Reduce the aggregated ER packet request rate at the VQE Server, for example, by adding VQE Servers to distribute the ER request load. You many want to contact your Cisco technical support representative to discuss the solution.

Error Message VQES_CP-4-ERA_REFUSE_RCC_REQUEST_INVALID_E: No excess bandwidth available for client [chars] on channel [chars]:[dec]: refuse the RCC request

Explanation RCC request from a STB client is refused since no excess bandwidth is available for the client.

Error Message VQES_CP-4-ERA_WARNING: ERA warning message: [chars]

Explanation This is a warning message from the Control Plane ERA component. Error Repair or Rapid Channel Change service is not compromised when this condition occurs.

Recommended Action If this message recurs, copy the error message exactly as it appears in the 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-CP_UPDATE_START_INFO: Control Plane has received a channel update request.

Explanation This is an informational message.

Recommended Action This is an information message only; 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 the 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.

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.

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 the 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.

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 the VQE-S configuration for any errors. Refer to the Cisco CDA Visual Quality Experience Application User Guide for information on configuring VQE-S. Modify vcdb.conf and apply the configuration. If the condition persists, contact your Cisco technical support representative, and provide the representative with the gathered information. 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 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.

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.

Error Message VQES_DP-2-MP_INIT_FAIL: The MPEG Parser failed to initialize properly: [chars]

Explanation The MPEG Parser failed to initialize properly. A possible cause could be insufficient memory.

Recommended Action No action is required.

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.

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_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.

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.

Error Message VQES_DP-3-MP_CHANNEL_ADD_FAIL: The MPEG Parser failed to add a channel([hex]): [chars]

Explanation The MPEG Parser failed to add a channel. A possible cause could be insufficient memory or misconfigured channel.

Recommended Action No action is required.

Error Message VQES_DP-3-MP_CHANNEL_DEL_FAIL: The MPEG Parser failed to delete a channel([hex]): [chars]

Explanation The MPEG Parser failed to delete a channel properly. A possible cause could be ... XXX

Recommended Action No action is required.

Error Message VQES_DP-3-MP_GLOBAL_STATS_GET_FAIL: The MPEG Parser could not retrieve global statistics: [chars]

Explanation The MPEG Parser could get global statistics

Recommended Action No action is required.

Error Message VQES_DP-3-MP_STATS_GET_FAIL: The MPEG Parser could not retrieve statistics on channel [hex]: [chars]

Explanation The MPEG Parser could get statistics on the given channel.

Recommended Action No action is required.

Error Message VQES_DP-3-VQE_FBT_GEN_ERROR: Error when performing an operation on a Feedback Target address (detail: [chars], linux error: [Linux error]).

Explanation The Control 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 Control 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.

Error Message VQES_DP-3-VQE_FBT_REQ_ERROR: Failed to complete operation on a Feedback Target address: [chars] [chars] [chars].

Explanation The Control 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.

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.

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.

Error Message VQES_DP-4-DP_CORE_UTIL_EXCEEDS_LIMIT: Maximum CPU utilization has been exceeded on core [dec].

Explanation The Data Plane has exceeded the maximum utilization for the given core while reserving resources for a new channel. The Data Plane process will continue to function, though in some cases it may fail to perform error repairs or RCC operations, due to the core being overloaded. A core overload condition may be transient if the amount of error repairs being handled by that core is unusually high when the new channel is created, or the condition may be caused by too many channels being configured, in which case the condition will persist.

Recommended Action Correct any non-standard system configuration or installation that has been performed. Copy the error message exactly as it appears in the 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_INIT_WARN: An abnormal condition occured 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.

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.

Error Message VQES_DP-4-MP_LOW_PERF_OPTION: The VQE-S has been started with a performance affecting option enabled.This option removes a performance enhancing internal limit of the VQE-S and could lead to system instability or interruption of Error Repair and Rapid Channel Change functionality.

Explanation When this option is enabled, the VQE-S ignores a limit used in processing video data. This may cause the VQE-S to consume a more than nominal amount of CPU time. In this mode the VQE-S functionality may be affected.

Recommended Action No action is required.

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_SRC_MGMT_ERROR: Failed to complete an operation on an RTP source for channel [chars] (reason: [chars]).

Explanation The RTP code within the Cache Manager failed an operation on an RTP source. 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 simultaneouly 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 simultaneouly 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_CORE_UTIL_CORRUPT: CPU utilization accounting is corrupt on core [dec].

Explanation The Data Plane has encountered a corruption of the utilization accounting function for the given core. This problem is self-correcting, and the Data Plane process will continue to function. In all cases, this error condition results from a flaw in the software.

Error Message VQES_DP-6-DP_HIST_OP_FAILURE: A histogram operation failed on one or more cores (operation: [chars]).

Explanation The Data Plane process encountered an error when performing an operation on a histogram. Histogram operations are performed on all dedicated cores, and this message indicates that the operation has failed on one or more of the cores, thus the information gathered will not be complete. The text of the error message provides more detail on what action was being performed.

Recommended Action 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.

Error Message VQES_DP-6-MP_CHANNEL_ADD_GOOD: The MPEG Parser has successfully added channel [hex]

Explanation The MPEG Parser has successfully added the given channel

Recommended Action No action is required.

Error Message VQES_DP-6-MP_CHANNEL_DEL_GOOD: The MPEG Parser has successfully deleted channel [hex]

Explanation The MPEG Parser has successfully deleted the given channel

Recommended Action No action is required.

Error Message VQES_DP-6-MP_INIT_START: Initializing the MPEG Parser

Explanation Beginning MPEG Parser initialization. If it fails at a later stage, another syslog will be displayed indicating the reason for failure.

Recommended Action No action is required.

Error Message VQES_DP-6-VQE_FBT_REQ_INFO: Successfully completed operation on Feedback Target address: [chars] [chars] [chars].

Explanation The Control 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.

VQES_MLB_CLIENT Messages

This section contains the 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.

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.

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.

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.

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 the 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_DUPLICATE_COMMAND_LINE_OPTION: The MLB command-line option '-[dec]' has been repeated. MLB exit.

Explanation All the MLB command-line arguments must appears no more than once. If an argument requires multiple values, you must concatinate them together after a single argument.

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.

Error Message VQES_MLB-2-MLB_IFS_NUMBER_OVERFLOW: There are too many MLB interfaces. MLB exit. You cannot list more than [dec] interfaces.

Explanation The MLB interface list has overflowed. All the interfaces beyond this point are ignored.

Error Message VQES_MLB-2-MLB_INIT_FAILURE: MLB initialization has failed: [chars]. MLB exit.

Explanation Multicast Load Balancer process initialization has failed. 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 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_COMMAND_LINE_ARG: The MLB command-line argument '[chars]' is invalid. MLB exit.

Explanation All the MLB command-line arguments must be of the form of either '-x [ARG]' or '--full-name-x [ARG]'.

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.

Error Message VQES_MLB-2-MLB_INVALID_RESERV: Invalid unicast reservation ratio: %f. MLB exit.

Explanation MLB initialization has failed due to invalid unicast reservation ratio. Operator must correct the configuration file.

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.

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_SOCK_FAILURE: MLB socket binding has failed: [chars].

Explanation Multicast Load Balancer process initialization has failed due to socket binding 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, try remove file /var/tmp/.mlb_rpc as root and start vqe-s again. If the problem is still there, 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-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.

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.

VQES_MLB-3

Error Message VQES_MLB-3-MLB_COMMAND_LINE_OVERFLOW: MLB command line overflow: [chars]

Explanation An MLB command line parameter is too long.

Recommended Action Correct the VQE-S configuration, then restart the VQE-S service.

Error Message VQES_MLB-3-MLB_COMMAND_LINE_ROUTING_MISCONFIG: MLB command-line sets [dec] static candidate route(s) while using dynamic routing. Will ignore the candidate routes.

Explanation Static candidate routes were set, while also having dynamic routing. The MLB therefore ignores the given candidate routes and assumes dynamic routing.

Error Message VQES_MLB-3-MLB_CONST_STRING_OVERFLOW: MLB constant string overflow: '[chars]'

Explanation MLB attempted to write a fix-length command string that is too long.

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_UNKNOWN_DUPLEX: MLB link status monitoring returned an 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.

Error Message VQES_MLB-3-MLB_ETHTOOL_UNKNOWN_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.

Error Message VQES_MLB-3-MLB_HAS_NO_INTERFACES: The MLB is being run without any set interfaces.

Explanation The MLB should be called with a non-zero set of interfaces listed in the VCDB ('--interface' option)

Error Message VQES_MLB-3-MLB_IFS_NAME_IS_REPEATED: The MLB interface name '[chars]' already exists

Explanation The MLB interface name already appeared earlier in the list, and therefore was ignored.

Error Message VQES_MLB-3-MLB_IFS_NAME_IS_TOO_LONG: MLB interface name '[chars]' is too long. All interface names must less than [dec] characters long.

Explanation An MLB interface name was too long, and therefore was ignored.

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 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 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 If the interface was not intended to be used by the VQE-S application, remove its interface name from the vcdb.conf file. Refer to the Cisco CDA Visual Quality Experience Application User Guide for information on configuring VQE-S. Modify vcdb.conf and apply the configuration. If the condition persists, contact your Cisco technical support representative, and provide the representative with the gathered information.

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 bandwith for multicast join request. Invalid request will be abandoned.

Error Message VQES_MLB-3-MLB_NEXTHOP_STRING_OVERFLOW: MLB string overflow: '[chars]'

Explanation MLB attempted to concatenate too many gateways for the same IP prefix address.

Recommended Action Remove some of the gateways routed for this prefix address (see first address in string). You may want to associate them instead with more specific IP prefixes.

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 Cisco CDA Visual Quality Experience Application User Guide for information on configuring Ethernet interfaces. 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 the "Configuring VQE-S" appendix of the Cisco CDA Visual Quality Experience Application User Guide . If the interface was not intended to be used by the VQE-S application, remove its interface name from the vqe.vqes.vqe_interfaces option in the vcdb.conf file. Otherwise, refer to the Cisco CDA Visual Quality Experience Application User Guide for information on configuring Ethernet interfaces. 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_OUT_OF_BOUND_SYSTEM_INFO: MLB system information is out of bound: [chars]

Explanation MLB read an invalid value in the routing table. This is likely due to an unsupported routing option that could not be parsed.

Recommended Action Reboot the VQE-S server. Copy the error message exactly as it appears in the 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_PIPE_READ_FAILURE: MLB pipe read failure: [chars]

Explanation MLB failed to create or read information from a system call pipe. The OS may not have sufficient resources. Verify status of memory, hard disk quota, and CPU.

Recommended Action If disk quota is full, free hard disk space. Otherwise, Reboot the VQE-S server.

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.

Error Message VQES_MLB-3-MLB_RETURNED_INVALID_FORMAT: An MLB system call returned a string with an invalid format: [chars]

Explanation The system call utility is of a wrong version or the OS/routing table has an invalid configuration

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_SHARED_MEM_FAILURE: MLB shared memory failure: [chars]

Explanation MLB failed to write to the shared memory. OS may not have sufficient memory, or this memory segment may be in use by another process.

Recommended Action Restart the VQE-S application.

Error Message VQES_MLB-3-MLB_SKIPPED_COMMAND_LINE_ARG: The MLB skipped over [dec] command-line string(s): [chars]

Explanation All the MLB command-line arguments must have no more than one white-space-delimited string following them. Make sure that if the string contains a white-space that is it surrounded with quotation marks.

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_SYSTEM_CALL_FAILURE: MLB system call failure: [chars]

Explanation An MLB system call failed to execute properly. The OS may not have sufficient resources. Verify the status of memory, hard disk quota, and CPU.

Recommended Action If disk quota is full, free hard disk space. Otherwise, Reboot the VQE-S server.

Error Message VQES_MLB-3-MLB_UNKNOWN_OPTION: MLB ignored an option that is either unrecognized or is missing an argument: [chars]

Explanation MLB detected unrecognized option and ignored it. This error can also be caused by ending the command-line with an option that requires an additional argument.

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.

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.

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_EMPTY_ROUTE_CANDIDATE_STRING: The MLB command-line route candidate option string is empty: '[chars]'

Explanation MLB encountered the candidate route option in the command- line, however the parser could not identify any candidates in the string dfollowing it.

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.

Error Message VQES_MLB-4-MLB_LACK_AVAIL_BW: Lack of available bandwidth: %i.

Explanation The available bandwidth is set below 1000Mbps.

Recommended Action

Error Message VQES_MLB-4-MLB_MISSING_ROUTE_CANDIDATES: MLB uses static routing but does not have any candidate routes.

Explanation MLB is using static routing, but does not have any candidate routes. This is unusual, but may not be an error.

VQES_MLB-5

Error Message VQES_MLB-5-MLB_ROUTING_TABLE_UPDATE: MLB updated the routing table: [chars]

Explanation MLB added or deleted routes from the routing table

Recommended Action 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 the 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 specfic error that occurred. The VQE-S application could not be successfully started.

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 "Troubleshooting VQE Software Components" chapter of the Cisco CDA Visual Quality Experience Application User Guide 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.

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.

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 "Troubleshooting VQE Software Components" chapter of the Cisco CDA Visual Quality Experience Application User Guide 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 "Troubleshooting VQE Software Components" chapter of the Cisco CDA Visual Quality Experience Application User Guide 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.

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.

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_PROCESS_STOPPING: Process Monitor attempting to stop [chars]

Explanation Process Monitor is attempting to stop a specified process. Process Monitor is either shutting down by request or is currently restarting all VQE-S processes to maintain system health.

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.

VQE_CFGTOOL Messages

This section contains the VQE_CFGTOOL messages.

VQE_CFGTOOL-0

Error Message VQE_CFGTOOL-0-CE_CHECKSUM_MISMATCH: CE - Checksum mismatch detected in this file [chars].

Explanation This message indicates there is a checksum mismatch in /etc/ files.

Recommended Action Operator should investigate the file and make sure all changes are expected.

Error Message VQE_CFGTOOL-0-CE_SKIP_FILE_IGNORE: CE - File [chars] is skipped by CMS due to ""IGNORE configuration.

Explanation This message indicates at least one parameter in this /etc/ file is configured to be ignored. And CMS will not process it.

Recommended Action Information only, no action needed.

Error Message VQE_CFGTOOL-0-CE_SKIP_FILE: CE - File [chars] is skipped by CMS due to checksum mismatch.

Explanation This message indicates there is a checksum mismatch in /etc/ file. And CMS will not process it.

Recommended Action Operator should investigate the file and make sure all changes are expected.

VQE_CFGTOOL-3

Error Message VQE_CFGTOOL-3-CE_IGNORE_FILE: CE - File ([chars]) has multiple definitions for this single-valued key ([chars]). This file is being skipped.

Explanation All key value pairs belong to this file are ignored by Configuration Engine.

Recommended Action User needs to manually fix this file and leave only one definition for this key.

Error Message VQE_CFGTOOL-3-CE_TARGET_ERR: CE - target directory ([chars]) does not exist.

Explanation Config engine aborted because specified target directory does not exist.

Recommended Action Fix vqe_ce command line argument.

Error Message VQE_CFGTOOL-3-CFG_ARGS_ERR: CFGTOOL - unrecognized command argument: [chars].

Explanation Vqe_cfgtool aborted on above unrecognized argument.

Recommended Action Fix the command line argument.

Error Message VQE_CFGTOOL-3-VCDBPARSER_BAD_SYNTAX: VCDB Parser - Invalid syntax in this line: [chars].

Explanation Invalid syntax delected in this line of the VCDB file.

Recommended Action Need to fix the syntax error.

Error Message VQE_CFGTOOL-3-VCDBPARSER_BAD_VALUE: VCDB Parser - Invalid value ([chars]) for key ([chars]).

Explanation A key is being set to an invalid value.

Recommended Action User needs to correct the bad value configuration in vcdb.conf.

Error Message VQE_CFGTOOL-3-VCDBPARSER_DUPLICATE_KEY: VCDB Parser - Multiple values are configured for the single-value key -- [chars].

Explanation Only one value should be configured for this parameter.

Recommended Action Need to remove extra configurations.

Error Message VQE_CFGTOOL-3-VCDBPARSER_DUPLICATE_VALUE: VCDB Parser - Duplicate values are configured for the same key -- [chars].

Explanation Values need to be different for a multi-value parameter.

Recommended Action Need to remove extra configurations.

Error Message VQE_CFGTOOL-3-VCDBPARSER_NO_QUOTE: VCDB Parser - Invalid syntax (missing double quotes around value) in this line ([chars]).

Explanation Invalid syntax -- Value of a key needs to be in double quote

Recommended Action Need to fix the syntax error.

Error Message VQE_CFGTOOL-3-VCDBPARSER_NO_ROUTERID: Router ID needs to be configured when routing type is set to ospf.

Explanation Router ID is a required parameter for OSPF to run properly.

Recommended Action Set network.ospf.router_id parameter in vcdb.conf via editor or Config Tool UI.

Error Message VQE_CFGTOOL-3-VCDBPARSER_PARSING_FAILED: Invalid syntax or value detected in vcdb.conf file. Please correct above problems in vcdb.conf file and retry. Aborting.

Explanation There is invalid key, value or syntax in vcdb.conf.

Recommended Action Need to fix the error then run the tool again.

Error Message VQE_CFGTOOL-3-VCDBPARSER_UNKNOWN_KEY: VCDB Parser - Unrecognized key: [chars].

Explanation Unknown key detected in the VCDB file.

Recommended Action Unknown key needs to be removed.

Error Message VQE_CFGTOOL-3-VCDB_BLANK_VALUE: Blank value is detected in vcdb.conf, configuration tool can not proceed.

Explanation Blank value is not allowed in vcdb.conf, CMS will assume it is an error and abort execution.

Recommended Action Correct the line with blank value in vcdb.conf, or comment it out.

Error Message VQE_CFGTOOL-3-VCDB_SAMPLE_ERR: VCDB syntax file /etc/opt/vqes/.vcdb.conf.sample is either corrupted, missing or does not have correct checksum file. Aborting.

Explanation VCDB syntax file is unusable, configuration tool will not proceed.

Recommended Action /etc/opt/vqes/.vcdb.conf.sample must be fixed before configuration tool can be used.

Error Message VQE_CFGTOOL-3-VCDB_UNKNOWN_HW: Can not determine the hardware platform type.

Explanation There might be some hardware problem or system corruption.

Recommended Action Check installation logs and vqe.log. Re-install software if needed.

VQE_CFGTOOL-4

Error Message VQE_CFGTOOL-4-BACKSPACE: VCDB Parser -- Invalid control character detected, possible backspace issue.

Explanation Some terminal emulator send non-standard control character for backspace, which will be ignored by the config tool.

Recommended Action Check the terminal configuration to find the correct key stroke for backspace, or avoid it during input.

Error Message VQE_CFGTOOL-4-CE_IGNORE_KVPAIR: CE - Ignoring key: [chars].

Explanation This key value pair is being ignored by Configuration Engine.

Recommended Action This key does not take effective. Information only. No action needed.

Error Message VQE_CFGTOOL-4-CE_INVALID_MGMT_ROUTE: The management route specified([chars]) is not included in OSPF routing map.

Explanation OSPF routing map does not accept management route that has prefix of 0.

Recommended Action Information only. No action needed.

Error Message VQE_CFGTOOL-4-CE_INVALID_VALUE: CE - Ignoring invalid value: [chars] :: [chars].

Explanation This invalid value is being ignored by Configuration Engine.

Recommended Action This value is either out of range or invalid type. Need correct value.

Error Message VQE_CFGTOOL-4-VCDBPARSER_ROUTERID_DUP: Router ID has the same value as one of the interface IP address.

Explanation The Router ID matches an interface IP address, which may cause OSPF issues in certain configurations (such as NSSA).

Recommended Action The Router ID should be changed to a unique IP address.

Error Message VQE_CFGTOOL-4-VCDBPARSER_TRUSTHOST_DEPRECATE: Parameter vqe.iptables.trusted_vcpt is deprecated. Its value in vcdb.conf will be converted to system.iptables.trusted_provisioner when you run vqe_cfgtool -config, and choose save option.

Explanation Parameter vqe.iptables.trusted_vcpt is deprecated. Should use new parameter system.iptables.trusted_provisioner.

Recommended Action Stop using the old parameter.

Error Message VQE_CFGTOOL-4-VCDB_MISSING_HW_INFO: Problem detected while retrieving platform information -- [chars]

Explanation There might be some hardware problem or system corruption.

Recommended Action Check installation logs and vqe.log. Re-install software if needed.

Error Message VQE_CFGTOOL-4-VQEPARSER_LEAD_TRAIL_SPACE: VCDB Parser - There are spaces around value inside double quotes in this line ([chars]). Spaces are being ignored.

Explanation This is a warning message to user, these spaces are being ignored.

Recommended Action User may want to fix the value.

VQE_CFGTOOL-6

Error Message VQE_CFGTOOL-6-CE_IPTABLES_RELOAD: CE - Reloading iptables filter rules.

Explanation This message indicates that iptables service will reload filter rules.

Recommended Action This is information only. No action needed.

Error Message VQE_CFGTOOL-6-CE_NET_RESTART: CE - Restarting network interfaces to apply configuration changes.

Explanation This message indicates that network restart is going to be performed.

Recommended Action This is information only. No action needed.

Error Message VQE_CFGTOOL-6-CE_NTPD_RESTART: CE - Reloading NTP service.

Explanation This message indicates that NTP service will restart.

Recommended Action This is information only. No action needed.

Error Message VQE_CFGTOOL-6-CE_REBOOT: CE - Rebooting system to apply configuration changes.

Explanation This message indicates that a system reboot is going to be performed.

Recommended Action This is information only. No action needed.

Error Message VQE_CFGTOOL-6-CE_SNMP_RESTART: CE - Restarting snmpd service to apply configuration changes.

Explanation This message indicates that snmpd service is going to be restarted.

Recommended Action This is information only. No action needed.

Error Message VQE_CFGTOOL-6-CE_VQES_CFGUPDATE: CE - Updating config file [chars].

Explanation Config tool is updating the indicated /etc/ configuration file.

Recommended Action This is information only. No action needed.

Error Message VQE_CFGTOOL-6-CE_VQES_RESTART: CE - Restarting VQES services to apply configuration changes.

Explanation This message indicates that VQES service restart is going to be performed.

Recommended Action This is information only. No action needed.

Error Message VQE_CFGTOOL-6-CT_CHANGE_LOG_PRIORITY: CE - Changing log priority to [chars].

Explanation This message indicates log priority level is changed.

Recommended Action This is information only. No action needed.

VQE_CFGTOOL-7

Error Message VQE_CFGTOOL-7-CE_APPLY_IF: CE - Apply value of [chars] to interface key [chars].

Explanation This is debug message.

Recommended Action No action is needed.

Error Message VQE_CFGTOOL-7-CE_APPLY_KVPAIR: CE - Processing key value pair: [chars] :: [chars].

Explanation .

Recommended Action .

Error Message VQE_CFGTOOL-7-GENERAL_DEBUG_MSG: cfgtool - [chars]

Explanation Message for debug/trace purpose.

Recommended Action Information only. No action is needed.

VQE_CFG Messages

This section contains the VQE_CFG messages.

VQE_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.

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.

VQE_CFG-3

Error Message VQE_CFG-3-CFG_ADD_ERR: Channel [chars] failed to add due to the same channel already being in the system.

Explanation Channel configuration uses the same identifier as another channel.

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.

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.

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.

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.

Error Message VQE_CFG-3-CFG_FILE_PROCESS_ERR: Channel process failed due to [chars]

Explanation Some channel configuration data failed validation checking.

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.

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_UPDATE_ERR: Channel update failed due to [chars]

Explanation Some channel configuration data failed validation checking.

Error Message VQE_CFG-3-CFG_VALIDATION_ERR: Channel [chars] failed validation due to [chars]

Explanation Channel configuration data failed semantic validation.

VQE_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.

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.

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.

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.

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.

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.

Error Message VQE_CFG-4-CFG_EXCEED_BUFFER_SIZE_WARN: The size of channel configuration [[chars]] exceeds the maximum size [dec] allocated

Explanation The size of each channel configuration data must be less than the maximum size allocated. Otherwise, a channel configuration might be skipped during data parsing.

Error Message VQE_CFG-4-CFG_ILLEGAL_SDP_SYNTAX_WARN: Illegal SDP syntax: [chars]

Explanation The specified SDP description has illegal syntax.

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 [[chars]] 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.

Error Message VQE_CFG-4-CFG_OLD_VERSION_WARN: Configuration module has received an older version of a configuration for channel [chars] than it currently has. The older version will be ignored.

Explanation Channel configuration data receiving is older than the one in the system.

Recommended Action No action is required.

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.

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.

Error Message VQE_CFG-4-CFG_VALIDATION_WARN: Channel [chars] has [chars]

Explanation Channel configuration data has unsupported data.

Recommended Action No action is required.

VQE_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.

VQE_RPC Messages

This section contains the VQE_RPC messages.

VQE_RPC-2

Error Message VQE_RPC-2-RPC_PROCESS_ABORT: RPC process abort: [chars]

Explanation An RPC (remote procedure call) client or server process has aborted, due to a previous unrecoverable internal software error, specified in an earlier system message. The process will be restarted.

VQE_RPC-3

Error Message VQE_RPC-3-RPC_INTERNAL_ERR: RPC internal error: [chars]

Explanation The RPC (remote procedure call) mechanism has experienced an internal software error, for the specified reason.

Error Message VQE_RPC-3-RPC_MESSAGE_ERR: RPC message error: [chars]

Explanation The RPC (remote procedure call) mechanism has detected an error in an RPC message, for the specified reason.

VQE_RPC-4

Error Message VQE_RPC-4-RPC_PROCESS_EXIT: RPC [chars] process has exited: [chars]

Explanation An RPC (remote procedure call) client or server process has exited, for the specified reason. This may occur when the VQE-S service is stopped or restarted, but may also occur when the other process has aborted due to an error. The process will be restarted.

Recommended Action If this message is not related to VQE-S service stop or restart, copy the error message (and any related ones) exactly as they appears in the system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.

VQE_RTP Messages

This section contains the VQE_RTP messages.

VQE_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 (e.g., ERA) using the pool, which is specified as part of the pool name, will not function correctly.

VQE_RTP-3

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 configuration file (vcdb.conf). The reason string identifies which parameter is missing or invalid.

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 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 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 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 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 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 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 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 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 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 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 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-sesssion 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 (e.g., repair requests) may not be processed correctly.

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 (e.g., repair requests) may not be processed correctly.

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 (e.g., RTCP report generation) may not function properly.

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-sesssion 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 (e.g., repair requests) may not be processed correctly.

VQE_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 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-4-RTCP_XR_NOT_INCLUDED_WARN: RTCP XR data (report block type [dec]) exceeds the given size in RTCP compound packet. Report block will not be included.

Explanation Size of RTCP XR report is larger than the given size.

Recommended Action No action is required.

VQE_RTP-6

Error Message VQE_RTP-6-RTCP_XR_EXCEED_LIMIT_INFO: RTCP XR data (block type [dec], data size [dec]) exceeds given size [dec] in RTCP compound packet. Data will be trimmed to fit into the packet.

Explanation Size of RTCP XR report is larger than the given size and XR data will be trimmed to fit into the given space.

Recommended Action No action is required.

Error Message VQE_RTP-6-RTCP_XR_NOT_REPORTED_INFO: [dec] packets not being reported in RTCP XR [chars].

Explanation Number of packets is not reported in RTCP XR.

Recommended Action No action is required.

VQE_RTSP Messages

This section contains the VQE_RTSP messages.

VQE_RTSP-3

Error Message VQE_RTSP-3-RTSP_CFG_FAILURE: Missing or invalid information in configuration file: [chars]

Error Message VQE_RTSP-3-RTSP_CFG_FILE_PARSE_ERR: Configuration syntax error "[chars]" on line [dec] in file [chars]

Explanation VCDS encountered the specified syntax error on the line specified. The VCDS application could not be successfully started.

Error Message VQE_RTSP-3-RTSP_CFG_UPDATE_ERR: Failed to update the configuration due to [chars]

Explanation A software error has occurred during the update of configuration and the configuration has not been updated.

Error Message VQE_RTSP-3-RTSP_EXCEED_MAX_ERR: The group IDs in the group mapping file has exceeded the maximum number [[dec]] allowed.

Explanation The group IDs in the group mapping file has exceeded the maximum number allowed.

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.

Error Message VQE_RTSP-3-RTSP_FILE_READ_ERR: The configuration file [chars] is not readable.

Explanation The configuration file for VCDS does not have read permission.

Recommended Action Check the location or permissions of the configuration file and make any necessary corrections.

Error Message VQE_RTSP-3-RTSP_FILE_WRITE_ERR: The configuration file [chars] is not writable.

Explanation The configuration file for VCDS does not have write permission.

Recommended Action Check the permissions of the 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 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 system log. Contact your Cisco technical support representative, and provide the representative with the gathered information.

Error Message VQE_RTSP-3-RTSP_PROCESS_ERR: VCDS has failed to process RTSP requests due to [chars]

Explanation VCDS has encountered an error and will not be available for use.

VQE_RTSP-4

Error Message VQE_RTSP-4-RTSP_CHECKSUM_CREATE_WARN: VCDS failed to create MD5 checksum for [chars].

Explanation This is an informational message.

Recommended Action No action is required.

Error Message VQE_RTSP-4-RTSP_CHECKSUM_MISSING_WARN: VCDS could not find MD5 checksum for [chars].

Explanation This is an informational message.

Recommended Action No action is required.

Error Message VQE_RTSP-4-RTSP_CONTENT_MODIFIED_WARN: File [chars] has been modified.

Explanation This is an informational message.

Error Message VQE_RTSP-4-RTSP_CONTENT_NOT_FOUND_WARN: VCDS does not have corresponding content for the request.

Explanation This is an informational message.

Recommended Action No action is required.

Error Message VQE_RTSP-4-RTSP_EXIT: VCDS has received a SIGTERM signal and is exiting now.

Explanation This is an informational message.

Recommended Action This is an information message only; no action is required.

Error Message VQE_RTSP-4-RTSP_ILLEGAL_GROUP_ID_WARN: Group ID [chars] in [chars] is an illegal value.

Explanation This is an informational message.

Recommended Action No action is required.

Error Message VQE_RTSP-4-RTSP_ILLEGAL_REQUEST_WARN: VCDS has received an illegal request.

Explanation This is an informational message.

Recommended Action No action is required.

Error Message VQE_RTSP-4-RTSP_REQUEST_TOO_BIG_WARN: VCDS has received a request exceeding the buffer length of [dec] bytes.

Explanation This is an informational message.

Recommended Action No action is required.

Error Message VQE_RTSP-4-RTSP_START: VCDS process has (re)started

Explanation This message is used to indicate that the VCDS Application has just been (re)started. This is either expected behavior from starting the VCDS service or VCDS exited unexpectedly and has restarted.

Recommended Action If the VDS application has just been manually started, or the VCDS 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.

VQE_RTSP-5

Error Message VQE_RTSP-5-RTSP_CFG_READ_NOTICE: VCDS reads in [chars].

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_DATA_NOTICE: No data exists in [chars].

Explanation This is an informational message.

Recommended Action This is an information message only; no action is required.

Error Message VQE_RTSP-5-RTSP_REACH_MAX_CONNECT_NOTICE: VCDS has reached the maximum number of client connections [[dec]] allowed.

Explanation This is an informational message.

Recommended Action This is an information message only; no action is required.

Error Message VQE_RTSP-5-RTSP_TURN_ON_LISTENER_NOTICE: VCDS has room to receive new client connections.

Explanation This is an informational message.

Recommended Action This is an information message only; no action is required.

Error Message VQE_RTSP-5-RTSP_VQEC_ATTR_UPDATE_NOTICE: VCDS receives a vqec attribute 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_VQEC_MAP_UPDATE_NOTICE: VCDS receives a vqec group mapping [chars] update ...

Explanation This is an informational message.

Recommended Action This is an information message only; no action is required.

VQE_UTILS Messages

This section contains the VQE_UTILS messages.

VQE_UTILS-3

Error Message VQE_UTILS-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 system log and provide it, in addition to any other requested information, when you contact your technical support representative.

Error Message VQE_UTILS-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

Error Message VQE_UTILS-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.

Error Message VQE_UTILS-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

Error Message VQE_UTILS-3-VQE_MP_TLV_ERR_BUF_TOO_SMALL: Problem with MP_TLV Buffer size (detail: [chars])

Explanation The buffer into which a write was attempted was too small The text of the error message provides additional detail on the failure.

Error Message VQE_UTILS-3-VQE_MP_TLV_ERR_OUTBUF_PAD: Error related to output buffer padding (detail: [chars])

Explanation Padding output buffer failed. The text of the error message provides additional detail on the failure.

Error Message VQE_UTILS-3-VQE_MP_TLV_ERR_PID: Error in PID (detail: [chars])

Explanation The PID for the packet was not found The text of the error message provides additional detail on the failure.

Error Message VQE_UTILS-3-VQE_MP_TLV_ERR_PKTDEC: Problem in decoding (detail: [chars])

Explanation Error decoding TLV packets. The text of the error message provides additional detail on the failure.

Error Message VQE_UTILS-3-VQE_MP_TLV_ERR_PKT_DEC_TYPE: Error in TLV packet type (detail: [chars])

Explanation Error decoding TLV packet type The text of the error message provides additional detail on the failure.

VQE_UTILS-6

Error Message VQE_UTILS-6-VQE_MP_TLV_INFO: MP_TLV related info message (detail: [chars])

Explanation This is an informational message generated by MP_TLV. The text of the error message provides additional detail on the failure.

Recommended Action This is an information message only; no action is required.