IBM BladeCenter JS12, Руководство по диагностике и обслуживанию

Страница: 214 / 318

Network connection problems
Identify network connection problem symptoms and what corrective actions to
take.
v Follow the suggested actions in the order in which they are listed in the Action column until the problem is
solved.
v
See Chapter 3, “Parts listing, Type 7998,” on page 235 to determine which components are CRUs and which
components are FRUs.
v
If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Symptom Action
One or more blade servers are
unable to communicate with
the network.
1. Make sure that:
v The I/O modules for the network interface being used are installed in the
correct BladeCenter bays and are configured and operating correctly. See the
online information or the
Hardware Maintenance Manual and Troubleshooting
Guide or Problem Determination and Service Guide for your BladeCenter unit
for details.
v
The settings in the I/O module are appropriate for the blade server (settings
in the I/O module are blade-specific).
2.
If the problem remains, see “Solving undetermined problems” on page 231.
PCI expansion card (PIOCARD) problem isolation procedure
The hardware that controls PCI adapters and PCI card slots detected an error. The
direct select address (DSA) portion of the system reference code (SRC) identifies
the location code of the failing component.
The following table shows the syntax of a nine-word B700xxxx SRC as it might be
displayed in the event log of the management module.
The first word of the SRC in this example is the message identifier, B7001111 . This
example numbers each word after the first word to show relative word positions.
The seventh word is the direct select address, which is
77777777 in the example.
Table 29. Nine-word system reference code in the management-module event log
Index Sev Source Date/Time Text
1 E Blade_05
01/21/2008,
17:15:14
(JS12-BC1BLD5E) SYS F/W: Error. Replace UNKNOWN
(5008FECF
B7001111 22222222 33333333 44444444 55555555
66666666 77777777 88888888 99999999)
Depending on your operating system and the utilities you have installed, error
messages might also be stored in an operating system log. See the documentation
that comes with the operating system for more information.
200
JS12 Type 7998: Problem Determination and Service Guide