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

Troubleshooting MCAs, Troubleshooting the blade interface (system console)

Get HP Integrity Superdome 2 16-socket PDF manuals and user guides View all HP Integrity Superdome 2 16-socket manuals
Add to My Manuals
Save this manual to your list of manuals

Page 86 highlights

Clocks test started... Blade ========== Blade 1/1 Blade 1/2 Blade 1/3 Blade 1/4 Blade 1/5 Blade 1/6 Blade 1/7 Blade 1/8 Sys Clk 0 ========== OK OK OK OK OK OK OK OK Sys Clk 1 ========== OK OK OK OK OK OK OK OK GPSM ========== GPSM 1/1 * GPSM 1/2 * Int Clk ========== OK OK Ext Clk ========== ------- SUCCESS: Clocks test passed. Clocks test complete. Any clock failures will also be detected and reported by CAE. To obtain these failures, run show CAE -L, and then use the command show CAE -E -n to obtain more details for the CAE event. Troubleshooting MCAs In general, MCAs are partition-based crashes and are detected and reported by CAE. To obtain a general overview about an MCA event, run show CAE -L, and then use the command show CAE -E -n to obtain more details for the CAE event. MCA data is also stored at the OA and can be retrieved by running the OA command show errdump dir mca: OA1 > show errdump dir all Logtype: MCA (Machine Check Abort) Bundle nPar vPar 0x0150000000000b62 5 0 0x0150000000000b61 5 0 0x0150000000000b60 5 0 0x0150000000000b5f 5 0 time Thu Jun 14 17:59:06 GMT+4 2012 Thu Jun 14 17:50:56 GMT+4 2012 Thu Jun 14 17:42:48 GMT+4 2012 Thu Jun 11 13:54:38 GMT+4 2012 Troubleshooting the blade interface (system console) All system console connections are made through the OA CLI either through the management network or through the port connectors on the OA module (local RS-232). HP-UX uses the RS-232 serial text connection to a dumb terminal, or to terminal emulator software running on a PC, to control server blade operations locally. All other connections are unsupported. HP-UX alternatively uses the OA 10/100 BT LAN connection over a private network, to control one or more server blade operations - locally through Telnet or SSH, or remotely over a public network through a web GUI. Troubleshooting the environment Ambient intake air temperature is often different from ambient room temperature. Measure the operating temperature and humidity directly in front of the cabinet cooling air intakes 10mm from the center of the intake, rather than measuring only ambient room conditions. 86 Troubleshooting

  • 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
Clocks test started...
Blade
Sys Clk 0
Sys Clk 1
==========
==========
==========
Blade 1/1
OK
OK
Blade 1/2
OK
OK
Blade 1/3
OK
OK
Blade 1/4
OK
OK
Blade 1/5
OK
OK
Blade 1/6
OK
OK
Blade 1/7
OK
OK
Blade 1/8
OK
OK
GPSM
Int Clk
Ext Clk
==========
==========
==========
GPSM 1/1 *
OK
----
GPSM 1/2 *
OK
----
SUCCESS: Clocks test passed.
Clocks test complete.
Any clock failures will also be detected and reported by CAE. To obtain these failures, run
show
CAE
–
L
, and then use the command
show CAE
–
E
–
n <ID>
to obtain more details for the CAE
event.
Troubleshooting MCAs
In general, MCAs are partition-based crashes and are detected and reported by CAE. To obtain
a general overview about an MCA event, run
show CAE
–
L
, and then use the command
show
CAE
–
E
–
n <ID>
to obtain more details for the CAE event.
MCA data is also stored at the OA and can be retrieved by running the OA command
show
errdump dir mca
:
OA1 > show errdump dir all
Logtype:
MCA (Machine Check Abort)
Bundle
nPar
vPar
time
0x0150000000000b62
5
0
Thu Jun 14 17:59:06 GMT+4 2012
0x0150000000000b61
5
0
Thu Jun 14 17:50:56 GMT+4 2012
0x0150000000000b60
5
0
Thu Jun 14 17:42:48 GMT+4 2012
0x0150000000000b5f
5
0
Thu Jun 11 13:54:38 GMT+4 2012
Troubleshooting the blade interface (system console)
All system console connections are made through the OA CLI either through the management
network or through the port connectors on the OA module (local RS-232).
HP-UX uses the RS-232 serial text connection to a dumb terminal, or to terminal emulator software
running on a PC, to control server blade operations locally. All other connections are unsupported.
HP-UX alternatively uses the OA 10/100 BT LAN connection over a private network, to control
one or more server blade operations — locally through Telnet or SSH, or remotely over a public
network through a web GUI.
Troubleshooting the environment
Ambient intake air temperature is often different from ambient room temperature. Measure the
operating temperature and humidity directly in front of the cabinet cooling air intakes 10mm from
the center of the intake, rather than measuring only ambient room conditions.
86
Troubleshooting