HP Integrity Superdome 2 16-socket HP Integrity Superdome 2 User Service Guide - Page 81

Troubleshooting processors, Processor module behaviors, Firmware, System firmware

Page 81 highlights

Parameter Parity Stop bits Protocol Value None 1 None 3. When prompted, enter a valid user name, and then press Enter. 4. Enter a valid password, and then press Enter. The CLI command prompt appears. 5. Enter commands for the Onboard Administrator. 6. To end the terminal session, enter Exit at the prompt. NOTE: If the serial session is not closed properly using the exit command, it can cause the console to respond slowly. Troubleshooting processors Processor module behaviors All physical processors become functional after blade power is applied. Each processor is in a race to fetch their instructions from their processor instruction and data caches to complete early self test and rendezvous. Double-bit data cache errors in any physical processor core can cause a local MCA event, which can have one of the following results: • The entire system crashes. • The failure is corrected and the processor is restarted. • The failure is corrected, but the processor is disabled if it has experienced a local MCA within a certain time span. IMPORTANT: L4 cache errors are the result of blade failure. Firmware There are three different firmware systems on Superdome 2: • System firmware bundle. • IO firmware (PCIe and LOM) • Interconnect module firmware. All firmware systems can be updated. System firmware The Superdome 2 complex system firmware bundle includes firmware for complex components including: • Server blade firmware (not including LOMs) • Partition firmware for each server blade • OA firmware • Manageability module firmware, including GPSMs and XFMs • Compute enclosure firmware • IOX enclosure firmware Troubleshooting processors 81

  • 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
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104

Value
Parameter
None
Parity
1
Stop bits
None
Protocol
3.
When prompted, enter a valid user name, and then press
Enter
.
4.
Enter a valid password, and then press
Enter
. The CLI command prompt appears.
5.
Enter commands for the Onboard Administrator.
6.
To end the terminal session, enter
Exit
at the prompt.
NOTE:
If the serial session is not closed properly using the
exit
command, it can cause
the console to respond slowly.
Troubleshooting processors
Processor module behaviors
All physical processors become functional after blade power is applied. Each processor is in a
race to fetch their instructions from their processor instruction and data caches to complete early
self test and rendezvous.
Double-bit data cache errors in any physical processor core can cause a local MCA event, which
can have one of the following results:
The entire system crashes.
The failure is corrected and the processor is restarted.
The failure is corrected, but the processor is disabled if it has experienced a local MCA within
a certain time span.
IMPORTANT:
L4 cache errors are the result of blade failure.
Firmware
There are three different firmware systems on Superdome 2:
System firmware bundle.
IO firmware (PCIe and LOM)
Interconnect module firmware.
All firmware systems can be updated.
System firmware
The Superdome 2 complex system firmware bundle includes firmware for complex components
including:
Server blade firmware (not including LOMs)
Partition firmware for each server blade
OA firmware
Manageability module firmware, including GPSMs and XFMs
Compute enclosure firmware
IOX enclosure firmware
Troubleshooting processors
81