1610-Temperature violation detected

[Steve Szuster]

Hi all,

I've recently configured a Proliant 1600R w/ 2-500mhz CPUS. All was working quite well, then I shut 'er down to intall a Smart Array 2/P RAID Controller. Unfortunatley, I gave it a little too much force when sliding the I/O card shelve in, but the only visable result of that was a torn floppy cable.

I don't know if this is related to the force, but now whenever turn the unit on, it gives me the following message "1610-Temperature violation detected", "Waiting 5 minutes for system to cool". Then a series of .......s follow, and 5 mins passes and the .......s keep coming.

The ambient temperature is well within normal limits and I have turned it off for an hour and still receive this message when powering back on. I have also reseated everything and pulled all unnecessary I/O cards.

Any ideas would be a BIG help.

Thanks in advance,

Cheers

Steve

[Prashant (I am Back)]

Hi,

Please see the below doccument
-----------------------------------------------------
Certain Compaq ProLiant 6400R Servers and ProLiant 6500 Servers with a Xeon processor may display the following error message during the Power-On Self-Test (POST):

''1610 - Temperature violation detected. Waiting 5 minutes for system to cool.''

The POST error message is displayed on a server operating in a warm environment or one that has been operational for a period of time (enough time for the system to warm up). On a ProLiant 6400R Server, the error message may be displayed either after a warm boot or when the server is powered up after it has already been operating. On a ProLiant 6500 Server, the error message is only displayed after a warm boot and does NOT occur when powering up the server.

The POST error occurs on the ProLiant 6400R Server because the thermal sensor caution trip point setting in the system ROM is 4 degrees below specification. This issue affects only the ROM boot sequence. It does not affect the functionality of the operating system, health drivers, or Insight Manager.

The POST error occurs on the ProLiant 6500 Server because the System Management Drivers for Windows NT 4.0 incorrectly set the thermal sensor caution trip point.
PRODUCTS AFFECTED
This issue affects a ProLiant 6400R Server configured with a system ROM dated 03/04/99 (March 4, 1999) and a ProLiant 6500 Server configured with a Xeon processor and system ROM dated 05/06/99 (May 6, 1999) or earlier.
RESOLUTION/SOLUTION
To resolve this issue, upgrade to system ROM (P11) dated 06/29/99 (June 29, 1999), which is available as Compaq SoftPaq SP11019 and downloadable from the Compaq website:

ftp://ftp.compaq.com/pub/softpaq/sp11001-11500/sp11019.exe

Regards,
Prashant S.

[JohnWRuffo]

Steve:

If you have a ProLiant 1600 (NOT a 6400 or 6500) do NOT do what was discribed above.

Your 1600 has a Power Backplane Board that the processor cage and I/O cage seat into. This board has all the critical connections for making this server work. It is important that the fan and small power supply signal cables are seated well. If these cables are loose and any of the pins are not making good contact I can see how this 1610 Errror is showing up.

http://h200002.www2.hp.com/bc/docs/support/UCR/SupportManual/TPM_179480-001_rev3_us/TPM_179480-001_rev3_us.pdf
Page 135 shows the board.

You said that when you seated the I/O cage in the server that you severed the floppy cable. Did you replace this cable "prior" to powering up the server?

If you did power on the server with the floppy cable crushed under the I/O cage connector, this could have electriclly shorted the Power Backplane Board or the I/O cage or any other component connected.

You may need to get a service call started to diagnose if any of the boards in this server are shorted.

[JohnWRuffo]

Also, make sure the SW1 switch pin 3 is set to ON with this server in a rack configuration.

[Steve Szuster]

Thanks John! I didn't notice the tear in the floppy cable and I powered it up, so what you say about a possible short makes perfect sense. Now I need to know where the short is. Do you think it would be on the I/O, CPU, or Backplane board?

I can found the I/O and CPU boards at a good price on eBay, but can't seem to find the backplane.

Also, just out of curiosity what does SW1/3 change in the actual workings/functionality of the system?

Cheers, and thanks again!!

[JohnWRuffo · Accepted solution]

Ok... the easy part: SW1 pin 3: This tells the server that it is in a "Rack" configuration (laying on its side) and to spin the fan up or down as needed if the heat starts to rise.

Here is the spare part number for the diskette cable: 271928-001

...as for where to look for the short, I would look at the system board LED's and at the I/O board (I think it has LED's) and see if any are amber or unlit if they are supposed to be.

I would pull the I/O cage out and look at the bus connector to see if anything looks char'd? Does the front I/O cage fan spin up?

You may have to call HP to get a diagnosis but my gut feeling is that the temperature sensor is in the I/O cage.

http://h20000.www2.hp.com/bc/docs/support/UCR/SupportManual/TPM_179480-001_rev3_us/TPM_179480-001_rev3_us.pdf

[JohnWRuffo]

Is this your board?
http://partsurfer.hp.com/cgi-bin/spi/showphoto?partnumber=149046-001
Should be about $85 - $90 retail.

You should look at the bus connections to see if any of the pins are bent or look for "melt"...

[Brian Murdoch]

Steve,

As John suggested earlier, check the small interconnect backplane for loose cables etc.

Here is a link to an earlier forum article where the backplane caused a problem in a Proliant 1600. This has attached images of the backplane so that you can check the cable locations. It's very easy to knock the connectors off.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=600171

I hope this helps,

Brian

[Steve Szuster]

Thank you John and Brian.

You hit the nail on the head with the backplane John. I found one on eBay for $10.00US and once I replaced it, she worked like a charm!! Gotta love eBay!!

Thanks again for the time and effort you dedicated to my cause!

And, lesson learnt!! Things do not like to be forced.

Cheers!!