First Created: February 27, 2016 By Rajendra ( Raj ) Patel.
Revised: Nov 22. 2016
Techdoc: Pending 

In order to have the top down approach to understand and debug any
PowerVC / HMC/ VIO config problem we need to collect below 
information data analyzed in the following order.

PowerVC => HMC => VIOs

Following questions should help narrow down the problem.

Q1. Are PowerVC, HMC and VIOs using NTP Servers to sync time across
    mutliple data centeres.

Q2. Is this problem during client VM deployment or something else?

Q3. Is the client depolyed ( AIX, Linux, or IBMi )

Q4. What is the issue seen? If its something else?

    a) What was the time of the error on PowerVC GUI / CLI.

    b) Are there any other errors seen on HMC / VIOs ?

Q5. Is the problem on one frame or multiple frames.

Q6. How many VIO Server are there?

Q7. Are VIO Servers using NPIV, Vscsi, or BOTH.

Q8. Does this have SSP cluser configured.

Then Gather:
1.  PowerVC logs
2.  HMC pedbg
3.  VIO snap for the CEC, LPAR Name shown by PowerVC error.
4.  Provide CEC where the error is being reported.
5.  VIO lpar name where the error is being reported.
6.  VIO lpar ID where the error is being reported.

Based on above below sequence will need be carried out.

A.  PowerVC to answer what above error means?
    a) i.e which REST API query etc is failing ?
    b) What does that error translate to in terms or error VIOs reports?
    c) What VIOS API or function is failing?
    d) Confirm what is the time frame when the error is seen?

B.  HMC to answer what above means? i.e what query etc is failing ?
    a) i.e which REST API query etc is failing ?
    b) What does that error translate to in terms or error VIOs reports?
    c) What VIOS API or function is failing?
    d) Confirm what is the time frame when the error is seen?


C. VIOs to follow above date/time to narrow down the problem.