- 論壇徽章:
- 0
|
1. 先從information center 中錯誤代碼 B1551380 .
" B1551380 Error trying to write register to device "
2. 從題目給的信息類型來看 , 直接go到 Service processor firmware reference code callouts .
大致如下 :
B1xx reference code indicates that an error occurred in a service processor firmware-detected operation. To resolve any B1xx reference code, use th e following procedure:
Does the reference code have a format of B151 72xx or B181 72xx that displays during the power-on process after power was connected to the server but before the server reaches the Power On Standby state?
Yes: See the description in Table 1. (B1xx) Service processor early termination reference codes. Perform Failing Item FSPSP02.
No: Continue with the next step.
a. Perform the following:
Using the callout list provided with the error replace the first or next FRU or perform the first or next isolation procedure in the list starting with the highest priority. For more information, see the following:
Finding part locations for links to removal and replacement information
(查找位置,有圖 . 不好截圖)
Service processor isolation procedures for links to service processor isolation procedures
從上面紅色的信息來看 , 先從最高優(yōu)先級來做 . 從給出的信息提示來看 ,是這個
Priority : Medium Priority
Procedure Number : FSPSP41
Service processor isolation procedures
These procedures help you to isolate problems with the service processor.
DANGER
When working on or around the system, observe the following precautions:
Electrical voltage and current from power, telephone, and communication cables are hazardous. To avoid a shock hazard:
Connect power to this unit only with the IBM provided power cord. Do not use the IBM provided power cord for any other product.
Do not open or service any power supply assembly.
Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration of this product during an electrical storm.
The product might be equipped with multiple power cords. To remove all hazardous voltages, disconnect all power cords.
Connect all power cords to a properly wired and grounded electrical outlet. Ensure that the outlet supplies proper voltage and phase rotation according to the system rating plate.
Connect any equipment that will be attached to this product to properly wired outlets.
When possible, use one hand only to connect or disconnect signal cables.
Never turn on any equipment when there is evidence of fire, water, or structural damage.
Disconnect the attached power cords, telecommunications systems, networks, and modems before you open the device covers, unless instructed otherwise in the installation and configuration procedures.
Connect and disconnect cables as described in the following procedures when installing, moving, or opening covers on this product or attached devices.
To Disconnect:
Turn off everything (unless instructed otherwise).
Remove the power cords from the outlets.
Remove the signal cables from the connectors.
Remove all cables from the devices
To Connect:
Turn off everything (unless instructed otherwise).
Attach all cables to the devices.
Attach the signal cables to the connectors.
Attach the power cords to the outlets.
Turn on the devices.
根據(jù)FSPSP41 這個型號 找到以下信息 (同樣由于沒有561的型號信息 , 我查看的是570的信息)
FSPSP41: Model 570
Use this procedure to help you isolate a problem that occurred when trying to access a chip on the I2C bus on model 570 (4-way or 8-way through 16-way).
1. Record words 3, 7, and 8 from the primary system reference code (SRC) of the error log.
28DA4410 00060052 000F00C0
下面的分析 ,yddll已經(jīng)分析的很細致了 .
2. Determine the enclosure that contains the service processor that started the I2C operation.
Note: The remainder of this procedure refers to this enclosure as the FSP enclosure.
Refer to the last byte in word 3 of the primary SRC to find the service processor enclosure:
If the last byte is a 10, then the primary unit service processor started the I2C.
If the last byte is a 20, then the secondary unit 1 service processor started the I2C.
If the last byte is a 30, use one of the following methods to determine the enclosure:
If you have access to the Advanced System Management Interface (ASMI), log on and display the details of the service processor error log. Using the Platform Event Log id (shown in the first table of each detail of the log), look at the first byte.
If the first byte is a 50, then the primary unit service processor started the I2C.
If the first byte is a 51, then the secondary unit 1 service processor started the I2C.
If you have access to an Hardware Management Console (HMC), log in as PE user and bring up Manage Serviceable Events under the Service Focal Point screen. Display the events for the corresponding service processor system, then double-click the system to see the details. Look at the Field Platform log ID, which contains a decimal value that you need to convert to a hexadecimal value.
If the first byte of the hexadecimal value is a 50, then the primary unit service processor started the I2C.
If the first byte of the hexadecimal value is a 51, then the secondary unit 1 service processor started the I2C.
3. Determine which enclosure contains the target I2C device.
Note: The remainder of this procedure refers to the enclosure that contains the I2C device as the target enclosure.
In the I2C Target enclosure table, find word 7 from the primary SRC. The enclosure listed beside word 7 is the target enclosures. Click the following link to display the I2C Target enclosure table: I2C Target enclosures for model 570 (4-way or 8-way through 16-way)
Does word 7 have a match in the I2C Target enclosure table?
Yes: Continue with the step 6.
No: Continue with the next step.
The upper word of word 7 does not have a match in the I2C Target enclosure table. Use the following statements to determine which enclosure contains the target I2C device:
If the upper word of word 7 is either 0002 or 0003, then the FSP enclosure and the target enclosure are the same.
If the upper word of word 7 is either 0000 or 0001, then refer to the following conditions
i. If the FSP enclosure is the primary unit, then the target enclosure is the secondary unit
If the FSP enclosure is secondary unit 1, then the target enclosure is the primary unit.
Determine which parts you need to replace on the target enclosure.
Using the following I2C FRU table for model 570, refer to words 7 and 8 of the primary SRC to locate the I2C FRU list. The I2C FRU list identifies the parts that you need to replace. Click the following link to display the I2C FRU table: I2C FRU table for model 570 (4-way or 8-way through 16-way)
Did you find the I2C FRU list?
Yes: Continue with the next step.
No: Contact your next level of support. This ends the procedure.
Starting with the first FRU in the list that you located the I2C FRU table, do the following:.
Power off the system.
Replace the FRU on the target enclosure. Go to Finding part locations for location, part number, and exchange information.
Go to Perform a slow boot, then continue with the next step.
Is the problem resolved?
Yes: This ends the procedure.
No: Continue with the next step.
Have you replaced all of the FRUs in the list?
No: Repeat step 7 for the next FRU in the list.
Yes: Continue with the next step.
Replace the following FRUs, one at a time and in the order listed. After you replace each FRU, perform a slow boot until the problem is resolved. For more information, see Perform a slow boot.
System/service processor cable connected from the service processor enclosure to the target enclosure
Service processor on the service processor enclosure
I/O backplane on the target enclosure
I/O backplane on the service processor enclosure
Is the problem resolved?
Yes: This ends the procedure.
No: Contact your next level of support. This ends the procedure.
b . Perform a slow-boot IPL.
通過ASMI來設(shè)置啟動 .
last : Did the same error code appear?
No: Go to Verifying the repair. This ends the procedure.
Yes: Continue with the next step.
Is the new error code the same as the one that brought you to this procedure?
Yes: Replace the next FRU or perform the next procedure in the list.
No: Go to the Start of call procedure to service this new error code. This ends the procedure.
如果還是出現(xiàn)同樣的錯誤代碼 . 做另外個vpd的程序和上面一樣 .
如果出現(xiàn)新的代碼 , 要開個IBM call
Start of call procedure
Provides a starting point for analyzing problems. You should begin all service actions with this procedure.
This is the starting point for diagnosing and repairing servers. From this point, you will be guided to the appropriate information to help you diagnose server problems, determine the appropriate repair action, and then perform the necessary steps to repair the server. A system attention light indicates there is a serviceable event (an SRC in the control panel or in one of the serviceable event views) on the system. This procedure will guide you through finding the serviceable event.
Note: In this topic, control panel and operator panel are synonymous.
Before beginning, perform as many of the following tasks as possible:
Note: Ask the customer for the Using the problem reporting forms (available in the Customer service, support, and troubleshooting topic) that they should have completed when working with the support center.
Verify the symptoms and service call data, including:
The server machine type, model number, and serial number.
The customer problem number.
A reference code (SRC, SRN or progress code). If you do not have a reference code, ask the customer for the date and time of the problem.
Any available location code information
Any data stored in:
the service action event log in Service Focal Point
the Service Action Log (i5/OS® servers)
other operating system-specific logs as directed
Symptoms reported to you by the customer.
Symptoms reported to you by the service support center.
Symptoms reported to you by an attached input/output (I/O) device, for example, a disk drive enclosure expansion drawer.
Record information to help you return the server to the same state that the customer typically uses, such as:
The IPL type that the customer typically uses for the server. (See Function 01: Display selected IPL type, system operating mode, and IPL speed for more information.)
The IPL mode that is used by the customer on this server.
The way in which the server is configured or partitioned.
Ensure that the customer has put the server into a state in which you can perform service tasks.
Is the failing component a monitor (display) or keyboard?
No:
Continue with the next step.
Yes:
Is the monitor or keyboard attached to a keyboard, video, mouse (KVM) switch?
No:
Continue with the next step.
Yes:
Go to Troubleshooting the keyboard, video, and mouse (KVM) switch for the 1x8 and 2x8 console manager.
Is the failing unit a 7037-A50 or a 7047-185?
No: Continue with the next step.
Yes: Go to Diagnosing a problem on a 7037-A50 or a 7047-185.
Is the failing server an xSeries or a BladeCenter blade server attached to an iSeries™ server through an iSCSI Host Bus Adapter (HBA)?
No: Continue with the next step.
Yes: Go to the iSeries integrated xSeries troubleshooting procedure.
Is there a Hardware Management Console (HMC) attached to the failing unit?
No: Continue with the next step.
Yes: Continue with step 7.
Is this an HMC-managed system?
Notes:
Look for HMC=x displayed in the control panel. The x represents a 0, 1, or 2, and depends on the number of HMCs attached to your server.
Ask the customer.
If the server does not have a control panel, then it should have an HMC.
No: Go to step 9.
Yes: Continue with the next step.
Inform the customer that an HMC is required to continue servicing the system, and ask the customer to reattach the HMC to the server. When the HMC is reattached to the managed system, continue with the next step.
Is the HMC functional?
No: Go to HMC problem isolation procedures. Once the HMC is functional, return here and continue with the next step.
Yes: Continue with the next step.
Perform the following steps from the HMC that is used to manage the server. During these steps, refer to the service data that was gathered earlier:
In the Navigation Area, open Service Applications.
Select Service Focal Point.
Select Repair Serviceable Event.
On the Select Failing System window, select the managed system that has the problem, and click OK.
Scroll through the log and verify that there is a problem with the status of Open to correspond with the customer's reported problem.
Note: If you are unable to locate the reported problem, and there is more than one open problem near the time of the reported failure, use the earliest problem in the log.
Do you find the reported problem, or an open problem near the time of the reported problem?
No: Continue with the next step.
Yes: Select the serviceable event you want to repair, and select Repair from the Selected menu.
This launches a series of windows that guides you through the steps to repair the serviceable event. The system guides you through one of the two following methods of repair, depending on the type of FRU you need to exchange:
An interactive step-by-step process that provides illustrations and video presentations to help you exchange the FRU.
A link to the appropriate information center topic that provides instructions to help you exchange the FRU.
After you complete the repair procedure, the system automatically closes the serviceable event. This ends the procedure.
Note: If the Repair procedures are not available, continue with the next step.
Is there an eight-digit reference code (except Cxxxxxxx) displayed in function 11 on the control panel, or if applicable on the HMC?
No: Continue with the next step.
Yes: Record all reference code data, including the values for functions 11 through 20 (see Collecting reference codes and system information), and note the failing partition. Then, go to the Reference codes topic to further isolate the problem. This ends the procedure.
Notes: If you are working at an HMC, check the HMC for operator panel values by performing the following steps:
In the Navigation Area, expand Server and Partition > Server Management.
Choose from the following options:
To view managed system reference codes:
In the right pane, right-click the system and select Properties.
Select the Reference Code tab to view the codes.
When finished, click Cancel.
To view logical partition reference codes:
In the right pane expand the system that contains the partition.
Open Partitions.
Right-click the logical partition and select Properties.
Select the Reference Code tab to view the codes.
When finished, click Cancel.
Is the system managed by the Integrated Virtualization Manager (IVM)?
Note: For information about the IVM, refer to Managing the Integrated Virtualization Manager
Yes: Go to step 13.
No: Continue with the next step.
Is an operating system console session available and can you log into the session?
Notes:
For servers with logical partitions, the console session must be available for the failing partition.
If you suspect a problem is on a device (a disk drive enclosure expansion drawer for example) that is attached to a server or a partition, the console session must be available for the partition to which the device is attached.
See 5250 Console in the Managing your server topic for details on accessing a 5250 console session on the HMC.
Yes: Go to step 14.
No: Continue with the next step.
Work with the customer to open an operating system console session. Can you successfully open an operating system console session?
Yes: Go to step 14.
No: Go to step 16.
Work with the customer to access the IVM web interface if it is not already running. Refer to Connecting to Integrated Virtualization Manager. Can you successfully open the console session for IVM?
Yes: Continue with the next step.
No: Go to step 16.
Use the operating system-specific, the IVM-specific, or the Virtual I/O server (VIOS)-specific service tools and system logs to locate a "serviceable event" in the logs, or if there is no serviceable event, use the customer-reported symptom in step 14.b.
Ask the customer for the date and time of the problem.
Note: If you are unable to locate the reported problem and there is more than one open problem near the time of the reported failure, use the earliest failure.
Go to the appropriate procedure depending on the operating system, IVM, or VIOS that is reporting a problem.
If your server is managed by IVM, go to Collect serviceable events in IVM, and then return here and continue on step 15.
If your server or partition is running AIX, go to AIX fast-path problem isolation.
If your server or partition is running Linux®, go to Linux fast-path problem isolation.
If your server or partition is running i5/OS, go to Using the Service Action Log.
If your server or partition is running a Virtual I/O Server partition, go to Virtual I/O Server troubleshooting.
Did you find a reference code associated with this failure near the time of the reported problem?
No: Continue with the next step.
Yes: Collect all reference code data and note the failing partition. Go to the Reference codes topic to further isolate the problem. This ends the procedure.
Use the HMC or a web browser to access the Advanced System Management Interface (ASMI). See Accessing the Advanced System Management Interface for details. Then, perform the following steps:
Log into the ASMI.
Click the plus sign next to System Service Aids.
Select Error/Event Logs to view the service processor error log.
Note: For more information on using the ASMI, see Managing your server using the Advanced System Management Interface.
Were you able to access ASMI and is there a reference code in the service processor error log that requires service?
No: Continue with the next step.
Yes: Collect all reference code data and note the failing partition. Go to the Reference codes topic to further isolate the problem. This ends the procedure.
The following examples show the possible formats of reference codes that display during the power-on process:
C1xx xxxx codes are displayed during the time after power is connected to the server until the service processor initial power-on process completes (indicated by "01" in the upper-left corner of the physical or logical control panel).
C2xx xxxx and C7xx xxxx codes are displayed after the power-on sequence is initiated.
CAxx xxxx codes are displayed while an AIX or Linux partition is initializing its resources.
xxx, 0xxx, 2xxxx, or C6xx xxxx, C9xx xxxx codes are displayed during the time that the operating system boots and configures resources.
888-xxx code
Does the power-on process for the server appear to be stopped, and does function 11 display a reference code of a format shown in the list above?
No: Go to the Symptom index. This ends the procedure.
Yes: Collect all reference code data and note the failing partition. Go to the List of progress codes topic to further isolate the problem. This ends the procedure.
Diagnosing a problem on a 7037-A50 or a 7047-185
This is the entry procedure for diagnosing problems on a 7037-A50 or a 7047-185
PS : yddll , 看到你的更改了 . 自己還是沒算到這一步 . 謝謝
以后不能偷懶了 , 得檢討下自己了
[ 本帖最后由 金牌小臥底 于 2007-11-20 02:16 編輯 ] |
|
免費注冊
發(fā)表于 2007-11-19 17:20
