Comments on: Installing HP Diagnostics

By: alvin

alvin — Wed, 21 Sep 2011 04:39:28 +0000

hi,

what is the maximum amount of agents (java or .net) that the mediator can handle? In your post above, you stated “for more than 40 agents, you will need another server acting as a mediator” could you please explain me about this? from your statement, I can assume the maximum agents for 1 mediator is 40, is that right?

Thanks,
Alvin

By: Deb

Deb — Fri, 08 Jul 2011 02:44:09 +0000

Hi Stuart,

We have just enhanced our test env to mimic prod. So basically test env used to be with one server that was shared as DB, App and Dialog (SAP) with different instances. So I had set one test server as both Commander and Mediator and another test server as Collector. Then it integrated to LoadRunner.
Now as we have updated the test env capacity to 8 servers (1 app, 1- DB and rest Dialog), should I configure one collector for collecting data across from all servers or do I need to set up different collectors for each servers.

Can you please suggest ?

Thanks

By: My Load Test » HP Software Universe 2010 (recap)

My Load Test » HP Software Universe 2010 (recap) — Sun, 18 Jul 2010 00:32:31 +0000

[...] you have to use Diagnostics, you might also be interested in my articles on Installing HP Diagnostics and Scaling HP [...]

By: Biswas

Biswas — Thu, 27 May 2010 18:59:11 +0000

Just opening those ports should be fine. Just make sure that the direction you open them is correct.

What would be the direction. below is the situation-

Commander -> Mediator-> |firewall| Appserver and probe.

I need to request to the team who manages firewall should I tell any thing else apart from opening those port? If yes then what? Please…your suggession.

By: Biswas

Biswas — Tue, 25 May 2010 18:13:19 +0000

Thanx for the good topic here. I had a little query here. If I had my application server behind firewall how do I configure to communicate with mediator/commander? Just if I open 2006,2612 and 35000 to 35xxx, is it enough or should i do some other configuration?
NB. My commander/Mediator is not behind firewall.

By: Bharathi

Bharathi — Mon, 12 Apr 2010 12:43:29 +0000

Getting the following error; Any idea , what could be wrong?

[HP Diagnostics Java Probe] The Linux kernel version is NOT_SUPPORTED for thread CPU timestamping feature.

[HP Diagnostics Java Probe] The Linux kernel version is SUPPORTED for process CPU utilization feature.

By: Stuart Moncrieff

Stuart Moncrieff — Tue, 24 Nov 2009 23:15:14 +0000

Today I was reminded how important it is to check the Product Availability Matrix (available from: http://support.openview.hp.com/sc/support_matrices.jsp), when I found that the SOAP Payload feature (which I had been promoting heavily in a meeting) wasn't actually supported on the client's application server. Oops.