The only way to get debug information from PowerPath is to open a case with the Support Center, they can engage PP engineering team who have some debug packages they can use to diagnose any PowerPath bugs.

Conor

we open a call. but EMC is on the track of finding the problem at qlogic not PP.
i think PP is to blame, but i don't have any proof.

shenar,

do you have SanSurfer agent/client loaded on these systems ? I believe one of the metrics is path errors or something like that. Would be interesting to see if PP errors correspond to Qlogic errors.

The only way to get debug logs from PowerPath is to get PowerPath Engineering through the support center supply a PowerPath Trace tool. The problem with that is if they don't have a pretty precise idea what they are tracing for the output can be megabytes a second and this can fill up your disk very quickly. Consequently troubleshooting of this type starts at the HBA level to identify what maybe causing PowerPath to do this.
Given that you have the same configuration with Emulex and are not experiencing an issue I would have to say that the issue is more than likely with QLogic than PowerPath.
Sam Claret TSE III