This is for xcat version .... Version 2.7.2 (svn r12895, built Wed May 23 02:11:50 EDT 2012)
Right now we know that we have one leg of the power missing on all the frames.. but still .. here is an example of the rvitals from a frame with 3 good legs..
frame03: Sum of all line cord power: 88629 Watts
frame03: Sum of all BPAs output: 82899 Watts
frame03: BPA-A total output: 82899 Watts
frame03: BPA-B total output: 0 Watts
frame03: Line cord 1 power: 44821 Watts
frame03: Line cord 1 AC voltage phase a to b: 474 Volts
frame03: Line cord 1 AC voltage phase b to c: 473 Volts
frame03: Line cord 1 AC voltage phase c to a: 475 Volts
frame03: Line cord 1 AC current phase a: 54 Amps
frame03: Line cord 1 AC current phase b: 55 Amps
frame03: Line cord 1 AC current phase c: 55 Amps
frame03: Line cord 2 power: 43808 Watts
frame03: Line cord 2 AC voltage phase a to b: 475 Volts
frame03: Line cord 2 AC voltage phase b to c: 473 Volts
frame03: Line cord 2 AC voltage phase c to a: 474 Volts
frame03: Line cord 2 AC current phase a: 53 Amps
frame03: Line cord 2 AC current phase b: 53 Amps
frame03: Line cord 2 AC current phase c: 53 Amps
.. First.. I only see 2 line cord status.. and the BPA-B output is zero.. the same on all of my frames... can someone please look at this.. remote monitoring of these type of values is critical to managing the system...
Assigned this rvitals bugs to JieHua .. Will need to have xCAT dev do some debug.
I looked into the perl code and fsp-api c code. The perl code outputs the fsp-api's return directly. And the fsp-api just gets the response from NetC. In the fsp-api, I found that it showed the "DC and good status" , or the "AC and good status". currently, It looks like the doc on my hand is out of date, not including this part. I will work with John on this bug.
Thanks.
We did some early investigation on this problem yesterday. We did confirm that the BPA was reporting 4 line cords but admin says there should only be 3 line cords. Also, the output is not reporting the second BPA power properly and is missing reporitng the other line cord. BPA developer is suspecting that we have a link down internally between the two BPAs and that this is causing the error. We will continue to investigate today to do more problem determination.
This looks like a hardware FSI cable problem which is causing the BPA to not able to share data using the internal mailbox. This does not look like an xCAT problem and I will close this defect once we confirm the investigation.
The GFW teams defect to fix this problem is 842075. Changing the resolution to remind to track the GFW fix.
This bug has no activity in the last two years, closing it out.