Remote Terminal Protocol:Failed to Initialize-Reason Timeout in Performance Center 9.52

14 Jan

Problem Statement

Last week we came across a interesting situation where my team was testing with RTE Protocol for mainframe application via Performance center 9.52.

The application was Banking Mainframe application and we had tested this application earlier also around 3 months back.The script which was prepared around 3 months back was running perfectly fine in Vugen and was giving issues while running in Performance center.

When the RTE script was loaded in the performance center, users were failing to come into the run state.They were held up in initiation state forever.After couple of minutes, we received the error message in output window as Failed to initialize: Reason timeout.

Workarounds which we tried to resolve the issue.

1. Checked in Runtime setting whether Vusers are running as a process rather than thread.Interesting observation noted while running in Thread mode via RTE  protocol was that behind the scene PC still uses winlnet replay rather than socket replay.

2. We did check the application was working manually.

3. We did check the application was able to ping the CICS Host from the Load Generator boxes using ping command and tracert command.

4. We did check event logs in Performance Center admin module and Performance center Project module.None of the logs  gave an hint as why users were sitting idle at init state for minutes together and then going straight into the Error state.

5.Thought the issue might be with Load Generators.Changed Load Generators many times,but no success.

6.Changed the name of the script at least twice to ensure that there is no duplication of script names. HP Support recommends this step for users failing to initialize.


Team has enabled IP Spoofing for the workload while building the scenario.


Disable IP Spoofing and run the test.Test ran perfectly fine.


Team wasted around 5 hours to troubleshoot this issue.Well I feel that lot of people these days are abusing the IP Spoofing without really knowing as what IP Spoofing basically is and under what situation it works and under what situation it does not work.If your project follows strong development process which also includes complete rounds of security testing, then one needs to aware that IP spoofing requires a lot of changes to be done in configuration files of the webservers, application servers and database servers.This is just not as simple as enabling the check box in Performance center or enabling the drop down checkbox in controller machine.



4 Responses to “Remote Terminal Protocol:Failed to Initialize-Reason Timeout in Performance Center 9.52”

  1. Doyle January 9, 2012 at 9:31 pm #

    Do you have further details of what configuration settings in app/web/db servers would need to be changed to allow IP spoofing to work? I must be one of these “abusers” because I cannot understand why any web server would not handle IP spoofing correctly, considering the application hardware in actual use will be hit by a variety of different IP addresses from various human users on different computers.

    • kiranbadi1991 January 10, 2012 at 4:03 am #

      Hi Doyle,

      There are some application which might require you to configure client details first in the backend servers before you start testing them.I have seen some legacy mainframe systems which do not accept any requests from any clients unless they are registered with it and sometimes that includes source IP as well.this is one of reasons I quite often suggest to check if your application really requires spoofed IP.

  2. pneuma March 16, 2012 at 9:04 pm #

    Encountered this problem on our setup – turns out one of the IP addresses assigned to our load generator was already in use. Removing that IP corrected the init issue. FYI.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: