WLA Archiver - data collection policies

My guess is that the Symms in questions may be posting 'No configuration for Symm xxxx' messages. Load balancing, gatekeepers etc would have to be looked at if that is the case.


Regards,
Séamus

Hi,

The Storage Agent for Symmetrix (EGS) logs from the hosts that are managing the Symms in question would need to be examined in order to troubleshoot the issue.

Best to open a SR. Support would then be able to identify what error messages are being posted at the scheduled WLA collection times.


Regards,
Séamus Coffey
EMC Global Services

Yes. I have SR opened.
Thank you Seamus.

Regards,
JRP.

Do you by any chance have more than one WLA Archiver deployed? We had some trouble a while back where some data was getting gathered but was being sent to the wrong WLA Archiver so was no visible in Performance Manager, but if you checked the director structure on the WLA Archiver hosts you could see the data for the missing objects on the other Archiver host.

Actually, we moved the archiver from one host to the other due to resources issues on the 1st one.
Collections are working for all the symms except one. For this one, it works if the primary is set to one host. If the primary is shifted to another host, it is not working.
Is there a way to manually set the primary for the symm agents?

Hi,

Load balancing for Symm Agents is automatic and is based on the following criteria:

1. The agent that has the highest version level (for example, 6.1). The
primary agent should have version equal or higher than the
version of the agent that last reported data on the managed object
to ControlCenter.

2. The agent that has the shortest logical distance to the managed
object.

3. The agent that has the lowest processing load.

4. The first agent located by the ECC Server.

There is a 'Configure Agent Load Balancing' section in the ControlCenter Planning & Installation Guide which explains and more besides in greater detail.


Regards,
Séamus

Thank you Seamus. I restarted the agents and the primary is set as it was expected.
But, I do have another question regarding how the ttp & btp files. We have 2 DCPs for the symms.

30 min dcp for 2 symms
10 min dcp for the rest 4 symms.

My question is, should we see .ttp & .btp files generated every 30 min for the 2 symms and every 10 min for the 4 symms?
I have noticed that some of the .ttp files are disappearing and some stays in the "interval" folder.
can someone explain how this whole thing works?

thanks,
JRP.

Hi JRP,

I've uploaded a WLA Data Flow diagram to ftp://ftp.emc.com/outgoing/wladataflow/ - hopefully that explains the full WLA collection process.


Regards,
Séamus

Seamus,

Thank you so much. Ihave a better understanding on the WLA data collection policies with that piece of information you shared.
By the way, support recommended the primus solution 212795 for the issue that we are having. Just want to let you know for your reference.
We will be upgrading the microcode on our symm to resolve the issue.

-JRP.

Thanks JRP, I'll make a note of that Primus solution.

Regards,
Séamus

Thankyou Seamus.

Regards,
Bannu.