Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

The HP ProLiant DL580 systems (G5 is the one I'm interested in at the moment) have a two-digit 7-segment display on the system board (visible only inside the chassis) which displays various diagnostic codes which they refer to as "port 84" or "port 85", switchable via a DIP switch.

The manuals mention this display but give only sketchy information about the actual codes displayed. Is there anywhere I could find a more specific & complete reference of the display codes? (I've done some web searches but have so far found only unrelated results.)

share|improve this question
    
You really should not need the port codes. Are you experiencing a particular issue where the system is unable to post IML log information? –  ewwhite Jan 27 '13 at 20:58

1 Answer 1

You should not need to reference port codes unless you're really having an issue with the server getting through the POST process.

What behavior is the server exhibiting?

The ProLiant POST boot troubleshooting flowchart still indicates checking the codes as a necessary step. It's not valid on newer boxes, but the ProLiant DL580 G5 you're dealing with uses them.

The full reference of Port 85 codes appears on page 64 of the HP ProLiant DL580 Generation 5 Server Maintenance and Service Guide. In general, the action needed to remediate the issues is reseating of the proper components.

enter image description here

share|improve this answer
    
I did fix the problem inspiring the question, although I didn't find any good reference. I knew about the small list in the manual, but as someone who'se engineered adapter cards from scratch, I was looking for a more complete, less generalized list. Even for the problem I fixed, the list's recommendation was completely off base (reseating the processor can't fix a watchdog timeout caused by firmware misconfiguration). –  Kevin Feb 4 '13 at 0:01
    
I would have been more interested in knowing what the original problem was. –  ewwhite Feb 4 '13 at 0:04
    
I actually wanted a better list even before any problem came up. I've noticed several codes show even when no problem is evident. The problem I did have showed a 5xh code I don't recall, maybe 51h. The system hung on boot with no video. Eventually I let it run long enough to find that it actually would start booting after 20+ min, and emit video characters one-by-one. I then suspected it was trying to output to a non-existent serial console. Sure enough that's what it was. I assume BIOS halted the CPU too long waiting for CTS, causing some kind of watchdog timeout and the 5xh code. –  Kevin Feb 5 '13 at 7:16

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.