This document provides installation instructions for CVP4.1(1) ES4. It also contains a list of CVP issues resolved by this engineering special. Please review all sections in this document pertaining to installation before installing the product. Failure to install this engineering special as described may result in inconsistent CVP behavior.
This document contains these sections:
The Product
Alert Tool offers you the ability to set up one or more profiles that will
enable you to receive email notification of new Field Notices, Product Alerts
or End of Sale information for the products that you have selected.
The Product
Alert Tool is available at http://www.cisco.com/cgi-bin/Support/FieldNoticeTool/field-notice
This ES updates all occurrences of the cvp-common.jar and the cvp.war file (located under
%CVP_HOME%/CallServer/Tomcat/webapps). The jar contains a fixes to speed
up PG failover when CVP is used with a duplex PG.
You
must have CVP4.1(1) on your machine before installing this ES.
CVP4.1(1) ES4 is compatible with
and should be installed on these CVP components:
Do not install this engineering special on any of the
following components:
· CVP VXML Server
· CVP Component version before and including CVP4.0(2)
CVP4.1(1) should be installed prior to applying this ES.
· The CVP Call Server must be taken out of service before applying this ES because the ES will abruptly stop the CVP Call Server. To bring the CVP Call Server out of service, do the following:
1. Using a web browser log into the OPSConsole (e.g. https://opsconsole:9443/oamp) with appropriate Username and Password.
2. In OPSConsole, go to “System” menu > “
3. In the
4. Refresh the
5. Log onto that CallServer:
· Download ES4 patch to that machine
· Install the ES by double clicking on the ES Patch installer and following the prompts
· Restart the machine at the end of the patch
6. After the CallServer machine restarts, go back to your
7. Refresh the
This section provides a list of significant CVP defects resolved by this engineering special. It contains these subsections:
Note: You can view more information on and track individual CVP defects using the Cisco Bug Toolkit located at: http://www.cisco.com/support/bugtools/Bug_root.html
Defect Number: CSCsm26428
Component: infrastructure
Severity: 3
Headline: CVP VRU PIM slow to fail over, ICM_DIALOGUE_FAILURE EVENT
Symptom: Intermittently the CVP VRU PIM is slow to come up on PG failover, can take up to 30 seconds for PIM to come up. PIM logs indicate Dialogue Failure event "message received form VRU out of sequence" and TCP connection to VRU is broken.
Condition: Duplex PG environment when primary PG fails.
Workaround: None
Further Problem Description:
Basically, there are 2 threads that are receiving messages from PG (ICM PIM
Listener and AdvisoryMessagePublisher threads). One
is handling Advisory messages and the other is handling MessageBus
requests. CVP (ICM subsystem) detects PG failure via the AdvisoryMessagePublisher
thread, this message that indicates that the connection is
"Down". After this
message is
received it starts cleaning up, but during the cleanup process the OPEN_REQ
message comes in on the ICM PIM Listener.
In addition, the Messaging Layer was occasionally not notifying the ICM subsystem when the Messaging Layer connection went down. This caused the ICM subsystem to reject the OPEN_REQ from the redundant PG as the ICM subsystem still thought it was connected to the failed PG. (Visible when ICM DEBUG ALL tracing is enabled.)
Please refer to the defect for more information.
Defect Number: CSCsl59762
Component: infrastructure
Severity: 3
Headline: CVP VRU PIM takes 30 seconds to go active on PG failover
Symptom: After PG Failover it can take up to 30 seconds before VRU PIM to CVP becomes active
Condition: Duplex PG ICM with CVP VRU PIM. When the active PG is stopped it can take up to 30 seconds for the VRU PIM to go active on the other PG
Workaround: None, must wait for PIM to become active
Further Problem Description:
In a duplex PG environment PG failover sometimes taking as much as 30 seconds
before the CVP VRU PIM goes active. (Note: Failover sometimes took ~1.5seconds
and other times ~30seconds). Investigation into the 30 second failover showed
that CVP Messaging Layer can get stuck in WAIT state for ~29 seconds. (Note:
Turning on all Message Layer tracing in non-production environment will show
how long in WAIT state).
When MESSAGING_LAYER DEBUG ALL tracing is enabled, extra debugging information will be logged to the CVP log file similar to the “Example CVP Log File”. This example shows the several state changes that occur during the PG failover scenario. Occasionally the connection with the VRU PIM may take ~29 seconds to transition out of the “Waiting” state (see details below). (Please note that some of the log information has been removed – indicated by “…”.)
In general, here are the following state transitions:
[*1*]: When the first PG fails, the GED125 plugin goes down and CVP transitions into the “Partial Service” state.
[*2*]: GED125 plugin transitions from “Down” to “Waiting” state.
[*3*]: GED125 still in “Waiting” state and it waiting to configure. In this example, the GED125 plugin (ConnectionServer) is in the Waiting state for ~29 seconds, which is slowing the connection to the redundant PG.
[*4*]: GED125 plugin transitions from “Waiting” to “Configure” state.
[*5*]: VRU PIM connection is established
Example CVP Log File
52: 142.125.119.74: Nov 26
2007 16:12:36.791 -0500: %CVP_4_0_ICM-2-LOGMSG_ICM_SS_PIM_SHUTDOWN: Lost socket
connection to VRU PIM. Transitioning to partial service. [id:2002] [*1*]
9572:
142.125.119.74: Nov 26 2007 16:12:36.791 -0500:
%CVP_4_0_MessagingLayer-3-MESSAGING_LAYER: ConnectionServer(GED125)::terminateConnection [id:1]9573: 142.125.119.74: Nov 26 2007
16:12:36.806 -0500: %CVP_4_0_MessagingLayer-7-INTERNAL_STATE: {Thrd=ConnectionServer(GED125)} ConnectionServer:changeState: Changed internal state from
Transport down to Waiting [*2*]
...
9575:
142.125.119.74: Nov 26 2007 16:12:36.806 -0500: %CVP_4_0_MessagingLayer-7-CODE_MARKER:
{Thrd=ConnectionServer(GED125)}
ConnectionServer:dispatchState: Current state of the ConnectionServer
Waiting [*3*]
9576:
142.125.119.74: Nov 26 2007 16:12:36.806 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
...
53:
142.125.119.74: Nov 26 2007 16:12:36.806 -0500:
%CVP_4_0_ICM-1-LOGMSG_ICM_SS_STATE: Waiting for VRU PIM Connection. [id:2006]
25:
142.125.119.74: Nov 26 2007 16:12:36.806 -0500:
%CVP_4_0_Infrastructure-5-RECEIVED_STATE_MSG: StateManager:
Subsystem [ICM1] reported change to state [Partial Service] due to [Dependency
not at full service] [id:1014]
...
9738:
142.125.119.74: Nov 26 2007 16:12:38.806 -0500: %CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)}
ConnectionServer:dispatchState: Current state of the ConnectionServer
Waiting [*3*]
9739:
142.125.119.74: Nov 26 2007 16:12:38.806 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
...
9780:
142.125.119.74: Nov 26 2007 16:12:40.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer Waiting [*3*]
9781:
142.125.119.74: Nov 26 2007 16:12:40.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
9782:
142.125.119.74: Nov 26 2007 16:12:42.807 -0500: %CVP_4_0_MessagingLayer-7-CODE_MARKER:
{Thrd=ConnectionServer(GED125)}
ConnectionServer:dispatchState: Current state of the ConnectionServer
Waiting [*3*]
9783:
142.125.119.74: Nov 26 2007 16:12:42.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
...
9811:
142.125.119.74: Nov 26 2007 16:12:44.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer Waiting [*3*]
9812:
142.125.119.74: Nov 26 2007 16:12:44.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
...
9873:
142.125.119.74: Nov 26 2007 16:12:46.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer
Waiting [*3*]
9874:
142.125.119.74: Nov 26 2007 16:12:46.807 -0500: %CVP_4_0_MessagingLayer-7-METHOD_CALL:
{Thrd=ConnectionServer(GED125)} ConnectionServer:waitForConnection:
Waiting for a client
9875:
142.125.119.74: Nov 26 2007 16:12:48.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer
Waiting [*3*]
9876:
142.125.119.74: Nov 26 2007 16:12:48.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
...
9917:
142.125.119.74: Nov 26 2007 16:12:50.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer Waiting [*3*]
9918:
142.125.119.74: Nov 26 2007 16:12:50.807 -0500: %CVP_4_0_MessagingLayer-7-METHOD_CALL:
{Thrd=ConnectionServer(GED125)} ConnectionServer:waitForConnection:
Waiting for a client
9919:
142.125.119.74: Nov 26 2007 16:12:52.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer
Waiting [*3*]
9920:
142.125.119.74: Nov 26 2007 16:12:52.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a client
9921:
142.125.119.74: Nov 26 2007 16:12:54.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer
Waiting [*3*]
9922:
142.125.119.74: Nov 26 2007 16:12:54.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
...
9983:
142.125.119.74: Nov 26 2007 16:12:56.807 -0500: %CVP_4_0_MessagingLayer-7-CODE_MARKER:
{Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer
Waiting [*3*]
9984:
142.125.119.74: Nov 26 2007 16:12:56.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
9985:
142.125.119.74: Nov 26 2007 16:12:58.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer
Waiting [*3*]
9986:
142.125.119.74: Nov 26 2007 16:12:58.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
...
10057:
142.125.119.74: Nov 26 2007 16:13:00.807 -0500: %CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)}
ConnectionServer:dispatchState: Current state of the ConnectionServer
Waiting [*3*]
10058:
142.125.119.74: Nov 26 2007 16:13:00.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
10059:
142.125.119.74: Nov 26 2007 16:13:02.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer
Waiting [*3*]
10060:
142.125.119.74: Nov 26 2007 16:13:02.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
10061:
142.125.119.74: Nov 26 2007 16:13:04.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)} ConnectionServer:dispatchState:
Current state of the ConnectionServer Waiting [*3*]
10062:
142.125.119.74: Nov 26 2007 16:13:04.807 -0500: %CVP_4_0_MessagingLayer-7-METHOD_CALL:
{Thrd=ConnectionServer(GED125)} ConnectionServer:waitForConnection:
Waiting for a client
...
10123: 142.125.119.74: Nov 26 2007 16:13:06.807 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)}
ConnectionServer:dispatchState: Current state of the ConnectionServer Waiting [*3*]
10124:
142.125.119.74: Nov 26 2007 16:13:06.807 -0500:
%CVP_4_0_MessagingLayer-7-METHOD_CALL: {Thrd=ConnectionServer(GED125)}
ConnectionServer:waitForConnection: Waiting for a
client
10125:
142.125.119.74: Nov 26 2007 16:13:07.776 -0500:
%CVP_4_0_MessagingLayer-7-INTERNAL_STATE: {Thrd=Socket Connection listener
Thread} ConnectionServer:changeState:
Changed internal state from Waiting to Configure [*4*]
10126:
142.125.119.74: Nov 26 2007 16:13:07.776 -0500:
%CVP_4_0_MessagingLayer-7-EXTERNAL_STATE: {Thrd=Socket
Connection listener Thread} ConnectionServer:notifyNewClient: New client requests connection:Socket[addr=/142.125.119.70,port=3175,localport=5000]
10127:
142.125.119.74: Nov 26 2007 16:13:07.776 -0500:
%CVP_4_0_MessagingLayer-7-CLASS_DUMP: {Thrd=Socket
Connection listener Thread} ConnectionServer:notifyNewClient: Shadow socket(Socket[addr=/142.125.119.70,port=3175,localport=5000]) existing
socket(null)
10128:
142.125.119.74: Nov 26 2007 16:13:07.776 -0500:
%CVP_4_0_MessagingLayer-7-CODE_MARKER: {Thrd=ConnectionServer(GED125)}
ConnectionServer:dispatchState: Current state of the ConnectionServer Configure
10129:
142.125.119.74: Nov 26 2007 16:13:07.776 -0500: %CVP_4_0_MessagingLayer-7-INTERNAL_STATE:
{Thrd=ConnectionServer(GED125)} ConnectionServer:checkAndConfigureSocket:
New client socket acceptedSocket[addr=/142.125.119.70,port=3175,localport=5000]
10130:
142.125.119.74: Nov 26 2007 16:13:07.776 -0500: %CVP_4_0_MessagingLayer-7-LOCAL_DUMP:
{Thrd=ConnectionServer(GED125)} ConnectionServer:checkAndConfigureSocket:
Socket parameters: Linger(0), Nagle's algorithm off(true), Read timeout(0)
10131:
142.125.119.74: Nov 26 2007 16:13:07.776 -0500: %CVP_4_0_MessagingLayer-6-MESSAGING_LAYER:
ConnectionServer(GED125)::checkAndConfigureSocket
[id:1]
55:
142.125.119.74: Nov 26 2007 16:13:07.776 -0500:
%CVP_4_0_ICM-6-LOGMSG_ICM_SS_PIM_ACTIVE: Socket connection with VRU PIM
established. [id:2004]
...
56: 142.125.119.74: Nov 26
2007 16:13:07.776 -0500: %CVP_4_0_ICM-6-LOGMSG_ICM_SS_PIM_ACTIVE: VRU PIM
Connection Established... [id:2004] [*5*]
Please refer to the defect for more information.
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Cisco documentation is available in the following ways:
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
We appreciate your comments.
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to: http://www.cisco.com
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website: http://www.cisco.com/tac
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website: http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website: http://www.cisco.com/tac/caseopen
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows: