Intel S1200RP Technical Product Specification - Page 76

Embedded Platform Debug

Page 76 highlights

Platform Management Functional Overview Intel® Server Board S1200V3RP  During Power action, Power button/Reset button will not accept the next action until current Power action is complete and the acknowledgment from BMC is received.  EWS will provide a valid message during Power action until it completes the current Power action.  The VFP does not have any effect on whether the front panel is locked by Set Front Panel Enables command.  The chassis ID LED provides a visual indication of a system being serviced. The state of the chassis ID LED is affected by the following actions: - Toggled by turning the chassis ID button on or off. - There is no precedence or lock-out mechanism for the control sources. When a new request arrives, previous requests are terminated. For example, if the chassis ID button is pressed, the chassis ID LED changes to solid on. If the button is pressed again, the chassis ID LED turns off. - Note that the chassis ID will turn on because of the original chassis ID button press and will reflect in the Virtual Front Panel after VFP sync with BMC. Virtual Front Panel will not reflect the chassis LED software blinking from the software command as there is no mechanism to get the chassis ID Led status. - Only Infinite chassis ID ON/OFF from the software command will reflect in EWS during automatic /manual EWS sync up with BMC.  Virtual Front Panel help is available for virtual panel module.  At present, NMI button in VFP is disabled. It can be used in future. 6.11.15 Embedded Platform Debug The Embedded Platform Debug feature supports capturing low-level diagnostic data (applicable MSRs, PCI config-space registers, and so on). This feature allows a user to export this data into a file that is retrievable from the embedded web GUI, as well as through host and remote IPMI methods, for the purpose of sending to an Intel engineer for an enhanced debugging capability. The files are compressed, encrypted, and password protected. The file is not meant to be viewable by the end user but rather to provide additional debugging capability to an Intel support engineer. A list of data that may be captured using this feature includes but is not limited to:  Platform sensor readings - This includes all readable sensors that can be accessed by the BMC FW and have associated SDRs populated in the SDR repository. This does not include any event-only sensors. (All BIOS sensors and some BMC and ME sensors are event-only; meaning that they are not readable using an IPMI Get Sensor Reading command but rather are used just for event logging purposes).  SEL - The current SEL contents are saved in both hexadecimal and text format.  CPU/memory register data - Useful for diagnosing the cause of the following system errors: CATERR, ERR[2], SMI timeout, PERR, and SERR. The debug data is saved and timestamped for the last 3 occurrences of the error conditions. - PCI error registers - MSR registers - MCH registers  BMC configuration data 64 Revision 1.0

  • 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
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262

Platform Management Functional Overview
Intel® Server Board S1200V3RP
During Power action, Power button/Reset button will not accept the next action until
current Power action is complete and the acknowledgment from BMC is received.
EWS will provide a valid message during Power action until it completes the current
Power action.
The VFP does not have any effect on whether the front panel is locked by
Set Front
Panel Enables
command.
The chassis ID LED provides a visual indication of a system being serviced. The state of
the chassis ID LED is affected by the following actions:
-
Toggled by turning the chassis ID button on or off.
-
There is no precedence or lock-out mechanism for the control sources. When a new
request arrives, previous requests are terminated. For example, if the chassis ID
button is pressed, the chassis ID LED changes to solid on. If the button is pressed
again, the chassis ID LED turns off.
-
Note that the chassis ID will turn on because of the original chassis ID button press
and will reflect in the Virtual Front Panel after VFP sync with BMC. Virtual Front
Panel will not reflect the chassis LED software blinking from the software command
as there is no mechanism to get the chassis ID Led status.
-
Only Infinite chassis ID ON/OFF from the software command will reflect in EWS
during automatic /manual EWS sync up with BMC.
Virtual Front Panel help is available for virtual panel module.
At present, NMI button in VFP is disabled. It can be used in future.
6.11.15
Embedded Platform Debug
The Embedded Platform Debug feature supports capturing low-level diagnostic data (applicable
MSRs, PCI config-space registers, and so on). This feature allows a user to export this data into
a file that is retrievable from the embedded web GUI, as well as through host and remote IPMI
methods, for the purpose of sending to an Intel engineer for an enhanced debugging capability.
The files are compressed, encrypted, and password protected. The file is not meant to be
viewable by the end user but rather to provide additional debugging capability to an Intel support
engineer.
A list of data that may be captured using this feature includes but is not limited to:
Platform sensor readings – This includes all readable sensors that can be accessed by
the BMC FW and have associated SDRs populated in the SDR repository. This does not
include any event-only sensors. (All BIOS sensors and some BMC and ME sensors are
event-only; meaning that they are not readable using an IPMI
Get Sensor Reading
command but rather are used just for event logging purposes).
SEL – The current SEL contents are saved in both hexadecimal and text format.
CPU/memory register data – Useful for diagnosing the cause of the following system
errors: CATERR, ERR[2], SMI timeout, PERR, and SERR. The debug data is saved and
timestamped for the last 3 occurrences of the error conditions.
-
PCI error registers
-
MSR registers
-
MCH registers
BMC configuration data
Revision 1.0
64