Compaq ProSignia 500 Compaq ProSignia Family of PC Servers Maintenance and Ser - Page 56

Server Mode an option in the EISA Configuration Utility. This option

Get Compaq ProSignia 500 PDF manuals and user guides View all Compaq ProSignia 500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 56 highlights

To maintain system security, the PC Server should be set to boot in Network Server Mode (an option in the EISA Configuration Utility). This option ensures that the PC Server keyboard is locked until you enter the Keyboard Password. You should also select an Administrator Password (an option in the EISA Configuration Utility). During attended ASR (local or remote), you must enter this Administrator Password before any modifications can be made to the PC Server configuration. Server Health Logs The Server Health Logs contain information to help identify and correct any PC Server failures and correlate hardware changes with PC Server failure. The Server Health Logs are stored in nonvolatile RAM and consist of the Critical Error Log and the Revision History Table. In the event that errors occur, information about the errors are automatically stored in the Critical Error Log. Whenever boards or components (that support revision tracking) are updated to a new revision, the Revision History Table will be updated. Critical Error Log The Critical Error Log records noncorrectable memory errors as well as catastrophic hardware and software errors that typically cause the system to fail. This information helps you quickly identify and correct the problem, minimizing downtime. The log can be viewed through Inspect Utility, Diagnostics Utility, or the optional INSIGHT Manager and Server Manager/R. The Diagnostics Utility either resolves the error or suggests corrective action. The Critical Error Log identifies and records all the following errors. Each error type is briefly explained below. When any of these errors are encountered, you should run the Diagnostics Utility. Table 3-18. Critical Error Log Error Messages Error Message Description Automatic Server Recovery Base The system detected a data error in base Memory Parity Error memory following a reset due to the Automatic Recovery Services (ASR) Timer expiration. Automatic Server Recovery The system detected a data error in Extended Memory Parity Error extended memory following a reset due to the ASR Timer expiration. Automatic Server Recovery The system ROM was unable to allocate Memory Parity Error enough memory to create a stack. Then, it was unable to put a message on the screen or continue booting the PC Server. Automatic Server Recovery The maximum number of system resets due Reset Limit Reached to the ASR timer expiration has been

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
To maintain system security, the PC Server should be set to boot in Network
Server Mode (an option in the EISA Configuration Utility). This option
ensures that the PC Server keyboard is locked until you enter the Keyboard
Password.
You should also select an Administrator Password (an option in the EISA
Configuration Utility). During attended ASR (local or remote), you must
enter this Administrator Password before any modifications can be made to
the PC Server configuration.
Server Health Logs
The Server Health Logs contain information to help identify and correct any
PC Server failures and correlate hardware changes with PC Server failure.
The Server Health Logs are stored in nonvolatile RAM and consist of the
Critical Error Log and the Revision History Table.
In the event that errors occur, information about the errors are
automatically stored in the Critical Error Log.
Whenever boards or components (that support revision tracking) are updated
to a new revision, the Revision History Table will be updated.
Critical Error Log
The Critical Error Log records noncorrectable memory errors as well as
catastrophic hardware and software errors that typically cause the system
to fail. This information helps you quickly identify and correct the
problem, minimizing downtime.
The log can be viewed through Inspect Utility, Diagnostics Utility, or the
optional INSIGHT Manager and Server Manager/R. The Diagnostics Utility
either resolves the error or suggests corrective action.
The Critical Error Log identifies and records all the following errors.
Each error type is briefly explained below. When any of these errors are
encountered, you should run the Diagnostics Utility.
Table 3-18. Critical Error Log Error Messages
===========================================================================
Error Message
Description
---------------------------------------------------------------------------
Automatic Server Recovery Base The system detected a data error in base
Memory Parity Error
memory following a reset due to the
Automatic Recovery Services (ASR) Timer
expiration.
---------------------------------------------------------------------------
Automatic Server Recovery
The system detected a data error in
Extended Memory Parity Error
extended memory following a reset due to
the ASR Timer expiration.
---------------------------------------------------------------------------
Automatic Server Recovery
The system ROM was unable to allocate
Memory Parity Error
enough memory to create a stack. Then, it
was unable to put a message on the screen
or continue booting the PC Server.
---------------------------------------------------------------------------
Automatic Server Recovery
The maximum number of system resets due
Reset Limit Reached
to the ASR timer expiration has been