WLA agents

Do you refer to WLA agents as in WLA archiver agents? As the WLA collection from objects is performed from the specific agent for those objects. aka. Host agent for Windows on a Windows platform will run WLA dcp's, which then get pushed back to the desginated WLA archiver agent (ENW).

The number of WLA Archiver agents you have will be dependant on 2 main factors, is the host running WLA Archiver dedicated or a shared host with other agents/components. And how many MO (Managed Objects) will be looked after by the WLA Archiver agent.



I'd recommend you check out the following document available on Powerlink.

ControlCenter 5.2 Performance and Scalability Guidelines

Message was edited by:
michaelf

I mean WLA archiver agents (ENW).



I have allready check this document. That's why I installed 3 WLA archivers, errors are still present. There are now 2 solutions,
1/ decrease frequency of DCPs
2/ add more WLA archivers

First solution is not acceptable because we may need to proced to perfomance analyses after performance issues.
Second solution seems to be good but after adding 3 more WLA archivers there are still errors.

Regards,
Fox

Errors we are seing are in ECC Console Alerts windows such as :

Error processing WLA Daily collection 20061011 for Host=******. where the object name is a WLA Archiver Hostname in charge of Host

or

Error processing WLA Daily collection 20061031 for Clariion=*****. where the object name is a WLA Archiver Hostname in charge of Clariion

Regards,
Fox

Errors? Any chance you can advise me of what errors you are seeing on the environment?

I'd love to see what is being reported.

I see, what patch level do you currently have for your ControlCenter environment. To date you have no indicated.

You don't happen to be on ControlCenter 5.2 SP4 by chance?

And according to what you said previously you must now have something like 4-5 WLA archivers installed correct?

We are running 5.2 SP4 (is that a chance ? )
We now have 6 WLA archivers - 3 old and 3 new, but only new hosts are using new archivers

Thank's a lot
Fox

Sounds like the WLA Archivers are not all balanced, and the errors you get are because those objects are still trying to the use the same WLA Archiver. A util/method was made available with SP4 to balance things manually across WLA Archivers and the knowledge article talking about this can be found by looking up "emc143446" which then talks about hotfix 3039.

If your going to need to balance your WLA Archivers, then your going to need a case raised to EMC to get access to the hotfix.

The errors your getting, check to see if all the errors against those objects being reported are all against a certain WLA Archiver. I'd imagine they probably are, and as such haven't automatically swapped to one of the newer archivers who is not busy.