IBM QS21 Service Guide - Page 112

Problem, reporting, description

Page 112 highlights

Table 21. NMI messages (continued) Message DIAGS: SB1 NMI: DIMM 11 Severity Error Event Cell/B.E. companion chip 2 indicates an error on JDIMM 11 Lightpath LED NMI Error Action Problem reporting Firmware logs and Firmware settings are located in the system's Non-Volatile Random Access Memory (NVRAM). In the case of an error where IBM support is needed, complete the following steps to provide the firmware log information: 1. Boot Linux. 2. Log in as root. 3. Extract the log with this command: cat /dev/nvram > /tmp/QS21-fw-nvram.img 4. Create a problem description in the /tmp/PROBLEM.txt file. See "Problem description" for further information. 5. Go to the Advanced Management Module Web interface for the blade and save the event log as a text file with the name QS21-event-log.txt. 6. Create a .tgz file using the following commands: tar cvfz QS21-error-log--.tgz \ /tmp/PROBLEM.txt /tmp/QS21-fw-nvram.img where: Contains a short name of the customer. Contains the creation date. 7. Provide IBM support with the tgz file. Problem description The problem description must added to/tmp/PROBLEM.txt together with the following information: v Customer name and address. v Name of the person who created the log, including their contact information. v Date and time. v Blade server slot position in BladeCenter unit. You can obtain this from the Advanced Management Module. v Blade server serial number. You can obtain this from the Advanced Management Module. v BMC firmware version number. You can obtain this from the Advanced Management Module v Linux Kernel version number. You must indicate if this is a private build. 94 BladeCenter QS21 Type 0792: Problem Determination and Service Guide

  • 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

Table
21.
NMI
messages
(continued)
Message
Severity
Event
Lightpath
LED
Action
DIAGS:
SB1
NMI:
DIMM
11
Error
Cell/B.E.
companion
chip
2
indicates
an
error
on
JDIMM
11
NMI
Error
Problem
reporting
Firmware
logs
and
Firmware
settings
are
located
in
the
system’s
Non-Volatile
Random
Access
Memory
(NVRAM).
In
the
case
of
an
error
where
IBM
support
is
needed,
complete
the
following
steps
to
provide
the
firmware
log
information:
1.
Boot
Linux.
2.
Log
in
as
root.
3.
Extract
the
log
with
this
command:
cat
/dev/nvram
>
/tmp/QS21-fw-nvram.img
4.
Create
a
problem
description
in
the
/tmp/PROBLEM.txt
file.
See
“Problem
description”
for
further
information.
5.
Go
to
the
Advanced
Management
Module
Web
interface
for
the
blade
and
save
the
event
log
as
a
text
file
with
the
name
QS21-event-log.txt
.
6.
Create
a
.tgz
file
using
the
following
commands:
tar
cvfz
QS21-error-log-<customer>-<date>.tgz
\
/tmp/PROBLEM.txt
/tmp/QS21-fw-nvram.img
where:
<customer>
Contains
a
short
name
of
the
customer.
<date>
Contains
the
creation
date.
7.
Provide
IBM
support
with
the
tgz
file.
Problem
description
The
problem
description
must
added
to
/tmp/PROBLEM.txt
together
with
the
following
information:
v
Customer
name
and
address.
v
Name
of
the
person
who
created
the
log,
including
their
contact
information.
v
Date
and
time.
v
Blade
server
slot
position
in
BladeCenter
unit.
You
can
obtain
this
from
the
Advanced
Management
Module.
v
Blade
server
serial
number.
You
can
obtain
this
from
the
Advanced
Management
Module.
v
BMC
firmware
version
number.
You
can
obtain
this
from
the
Advanced
Management
Module
v
Linux
Kernel
version
number.
You
must
indicate
if
this
is
a
private
build.
94
BladeCenter
QS21
Type
0792:
Problem
Determination
and
Service
Guide