T3: After replacing PSU, id read u1pcu1 is blank

About 5 hours agi, I replaced a PSU in my T3 since the old one had batteries that were 2 years past their expiration date :-). However, on the replacement, id read u1pcu1output is all blank:

T3-foo:/:<5>id read u1pcu1

Revision :

Manufacture Week:

Battery Install Week :

Battery Life Used:

Battery Life Span:

Serial Number:

Battery Warranty Date:

Battery Internal Flag:

Vendor ID:

Model ID :

Here's the other one (can you say "deferred maintenance"?):

T3-foo:/:<6>id read u1pcu2

Revision : 0000

Manufacture Week: 00262000

Battery Install Week : 00462002

Battery Life Used: 1132 days, 17 hours

Battery Life Span: 730 days, 12 hours

Serial Number: 012232

Battery Warranty Date: 20021115134029

Battery Internal Flag: 0x00000000

Vendor ID: TECTROL-CAN

Model ID : 300-1454-01(50)

I have two solid greens on the repalced PSU, and fru stat says everything is normal.

Do I need to wait a few more hours for the new batteries to charge?

Do I need to do the "id write busage" to fill in this info?

Any ideas?

Thanks,

-w

[1573 byte] By [wsanders1] at [2007-11-25 22:45:04]
# 1

This could be an old PSY I just popped in, the battery just went to "fault" state and id read data is still blank:

POWERSTATUSSTATESOURCE OUTPUT BATTERY

u1pcu1 readyenabledlinenormal fault

u1pcu2 readyenabledlinenormal normal

Oddly, the battery that is 2 years past its expiration is listed as "normal" although the yellow LED in on on the PSU.

wsanders1 at 2007-7-5 16:57:01 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 2

A very little reassurance ... I raised a call with Sun back in January about this very thing and was sent a script to run to extend the battery life from 730 days to 1095 days - used for T3s with 1.x firmware and T3+s with 2.x firmware, but not not needed for T3+ with 3.x firmware.

I know 1095 days is still less than the battery life used that you have but at least it is closer!!! I would suggest raising a call with Sun to see about getting them changed.

SimonM at 2007-7-5 16:57:01 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 3

Well, with the "new" PSU (that has probably been sitting on a shelf for two or three years) , and the other "old" PSU with the 4 year old batteries, "fru stat" is now cycling betweeb both batteries good, one at fault, and the other at fault, at about 8 hour intervals. "id read" output is still blank.

NiMh batteries should be good for a least hundreds of charge-discharge cycles, and should last for many years if charged properly. I have some NiCds AA cells are almost 10 years old (although most lasted about 3 years), and most of my NiMh AA cells are about 3 or 4 years old and show no signs of wekness.

An excellent link to battery information: <a href="http://batteryuniversity.com/" target="_blank">http://batteryuniversity.com/</a>

Sun has every right to be conservative with T3 batteries, considering the criticality of the application, but the batteries should be good for more than two years if your electricity is not going off every day. I only wonder if the output from "fru stat" is a true indication of the battery's ability to power the system.

wsanders1 at 2007-7-5 16:57:01 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 4

True, 2 years is very little - which is why, I would guess, they decided that 3 years was ok to support (and hence the change to 36 months (1095 days)).

Depending on what is running on the T3s and what official support you have for them, I would certainly strongly think about gettting the batteries swapped out. Basically it's your data, your choice :) Having said that I am not certain what effect the batteries going would have on a) an active system and b) a restarted sytem.

SimonM at 2007-7-5 16:57:01 > top of Java-index,Sun Hardware,Other Sun Hardware...
# 5

To wrap this up:

1) I have one PCU that prints all-blank info from "id read". This is a fault in the PCU not the batteries. The PCU is normal otherwise - all LEDS are green and output from "fru stat" is all normal.

2) The batteries take a while to charge after insertion and will show fault state until charged.

3) The battery life settings set by the ".id write busage" and ".bat" commands do not seem to be related to the output of "fru stat". "Fru stat" battery status seems to be determined from periodic refresh checks and not the dates in the "id read" data registers.

4) The refresh daemon seems to die sometimes and needs to be restarted wiht the "refresh -i" command. Check with "refresh -s" first.

wsanders1 at 2007-7-5 16:57:01 > top of Java-index,Sun Hardware,Other Sun Hardware...