IBM pSeries 690 Service Manual
  1. Manuals
  2. Brands
  3. IBM Manuals
  4. Server
  5. eserver pSeries 690
  6. Service manual
IBM pSeries 690 Service Manual

IBM pSeries 690 Service Manual

Hide thumbs Also See for pSeries 690:
1
2
3
4
Table Of Contents
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
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Installation Manual
ERserver
pSeries 690
Service Guide
SA38-0589-05

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the pSeries 690 and is the answer not in the manual?

Questions and answers

Related Manuals for IBM pSeries 690

Summary of Contents for IBM pSeries 690

  • Page 1 ERserver pSeries 690 Service Guide SA38-0589-05...
  • Page 3 ERserver pSeries 690 Service Guide SA38-0589-05...
  • Page 4 © Copyright International Business Machines Corporation, 2001, 2004. All rights reserved. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth is GSA ADP Schedule Contract with IBM Corp.

  • Page 5: Table Of Contents

    Chapter 1. Reference Information ......1 pSeries 690 Overview ....... 1 Hardware Management Console (HMC).
  • Page 6 Checkpoints and Error Codes Index ......418 Operator Panel Error Codes ......421 Eserver pSeries 690 Service Guide...
  • Page 7 SPCN Error Codes ....... 422 Firmware/POST Error Codes ......490 Service Processor Error Codes .
  • Page 8 Index ........1109 Eserver pSeries 690 Service Guide...

  • Page 9: Safety Notices

    Safety Notices A danger notice indicates the presence of a hazard that has the potential of causing death or serious personal injury. Danger notices appear on the following pages: v viii v 194 v 853 v 877 v 1006 A caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury.
  • Page 10 This unit has more than one power supply cord. Follow procedures for removal of power from the system when directed. CAUTION: Energy hazard, remove power before servicing. CAUTION: Energy hazard, remove all jewelry before servicing. viii Eserver pSeries 690 Service Guide...

  • Page 11: Laser Safety Information

    CAUTION: All IBM laser modules are designed so that there is never any human access to laser radiation above a class 1 level during normal operation, user maintenance, or prescribed service conditions. Data processing environments can contain equipment transmitting on system links with laser modules that operate at greater than class 1 power levels.
  • Page 12 Eserver pSeries 690 Service Guide...

  • Page 13: Data Integrity And Verification

    Data Integrity and Verification IBM computer systems contain mechanisms designed to reduce the possibility of undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience unplanned outages, system failures, power fluctuations or outages, or component failures must verify the accuracy of operations performed and data saved or transmitted by the system at or near the time of the outage or failure.
  • Page 14 Eserver pSeries 690 Service Guide...

  • Page 15: About This Book

    About This Book This book provides maintenance information that is specific to the Eserver pSeries 690, adapters, and attached devices that do not have their own service information. It also contains Maintenance Analysis Procedures (MAPs) that are not common to other systems.

  • Page 16: Related Publications

    The Eserver pSeries 690 Installation Guide, order number SA38-0587, contains information on how to set up and cable the system, install and remove options, and verify system operation. v The Eserver pSeries 690 User’s Guide, order number SA38-0588, contains information on how to use the system, use diagnostics, use service aids, and operations.

  • Page 17: Chapter 1. Reference Information

    Chapter 1. Reference Information This chapter provides an overview of the Eserver pSeries 690, including a logical description and a physical overview of the system. Additional details pertaining to the server are also provided. They include the following: v Memory overview and ordering rules...
  • Page 18 On each I/O backplane, PCI bus slots 1 through 7 are 3.3 V dc connectors running at 66 MHz, supporting 64-bit PCI adapters. Slots 8 through 10 are 64-bit 5 V dc slots, running at 33 MHz. Eserver pSeries 690 Service Guide...

  • Page 19: Hardware Management Console (Hmc)

    The media subsystem provides space for up to three media devices (diskette drive, CD-ROM drive, and optional tape drive or DVD-RAM) in the front and two additional optional devices in the rear. Hardware Management Console (HMC) The Hardware Management Console (HMC) supports your system with features that allow you to manage configuration and operation of partitions in a system, as well as add and remove hardware without interrupting system operation.

  • Page 20: Partition Requirements

    Keep this in mind when you record the amount of memory used when you are completing the planning worksheets in the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.

  • Page 21: Getting Started

    IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590. v If you need to add or change a partition name, see the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
  • Page 22 Agent application for notification. Note: You must further configure Service Agent to handle notifications sent by Service Focal Point. For more information about Service Agent, see the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
  • Page 23 4. The Service Focal Point Settings window opens. Select the Surveillance Notification tab at the top of the window. 5. Select one or more managed systems from the list, and click Enable or Disable. Surveillance notification is then either enabled or disabled for the selected managed systems. Working With Serviceable Events You can view, add, or update serviceable event information, including error details.
  • Page 24 From this panel, you can also activate and deactivate LEDs and search for other serviceable events that contain the same FRU entries. To update FRU information, do the following: Eserver pSeries 690 Service Guide...
  • Page 25 1. Perform the steps in “Viewing Serviceable Event Details” on page 7. 2. Click FRU Information. The Update FRU Information window opens. The lower table shows any parts that you have replaced or added during your current update session but that have not been committed to the serviceable event. The changes from the lower table are committed by clicking OK or Apply.

  • Page 26: Capacity Upgrade On Demand

    For further information about activating processor CUoD on your system, refer to “Activation Process for CUoD Features” on page 13, or refer to the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590, that was delivered with your hardware management console.

  • Page 27: Trial Capacity On Demand

    Permanent CUoD capacity can be activated in either one of the following scenarios. The description of each scenario indicates if and when it is necessary to send vital product data (VPD) to IBM. v New system order (new footprint): An order can contain a number of CUoD-activation features. The manufacturing facility fills orders directly at the plant of manufacture, before the server is delivered to the customer.

  • Page 28: Software Licenses And Processor Cuod

    Activating a processor may change the terms and conditions for applications that you use on your server. To determine if the license terms and conditions requirements change based on hardware configuration, consult the application documentation. Eserver pSeries 690 Service Guide...

  • Page 29: Powering The System On And Off

    3. The sales representative places an order to the system coordinator or feature coordinator for the features you request. The order specifies the upgrade features to add. 4. To process the order, you must send the system Vital Product Data (VPD) to IBM in either of the following ways: v Electronic process (Electronic Service Agent) v Web-based VPD entry.

  • Page 30: Pseries 690 Data Flow

    690 Data Flow The following figure shows the data flow for the system. Eserver pSeries 690 Service Guide...

  • Page 31: Power-On Self-Test

    Power-On Self-Test After power is turned on and before the operating system is loaded, the partition does a power-on self-test (POST). This test performs checks to ensure that the hardware is functioning correctly before the operating system is loaded. During the POST, a POST screen displays, and POST indicators display on the virtual terminal.

  • Page 32: Pseries 690 System Locations

    To exit from the open firmware command prompt, type reset-all or power off the system and reboot. pSeries 690 System Locations The pSeries 690 system consists of a minimum of four subsystems in one rack as follows: v Processor subsystem...
  • Page 33 In each of the following figures, the minimum system configuration is shown on the left. The minimum system configuration with the integrated battery feature (IBF) is shown on the right in each of the figures. 1 Rack 5 Media Subsystem 2 Bulk Power Assembly 6 Optional Integrated Battery Feature 3 UEPO Switch...
  • Page 34 Note: The I/O subsystem fan assemblies are inside the I/O subsystems, positioned from left to right behind the DASD 4-packs in order of fan assembly 1, fan assembly 2, fan assembly 3, and fan assembly 4. Eserver pSeries 690 Service Guide...
  • Page 35 UEPO Switch The UEPO (Unit Emergency Power Off) switch is accessible through the external cover. The switch contains a room emergency power off (EPO) interlock connector and bypass switch, a dual element rack service amber LED (one element driven per bulk power controller, a service complete button (white) and start service button (green), an off button and four thermistors for BPC ambient temperature sensing.
  • Page 36 Note: For slot assignments, see “Memory to Processor Relationships” on page 63. 1 Processor Subsystem Chassis 5 Fan Controller 2 Outer Memory Book 6 Fan Chassis 3 Inner Memory Book 7 Fan Filter 4 Fan Eserver pSeries 690 Service Guide...
  • Page 37 7040 Model 681 Processor Subsystem Rear View 1 I/O Book – Slot 1 8 Capacitor Book 2 DCA Book 1 9 DCA Book 6 (32-way, 1.7 GHz MCMs) 3 DCA Book 2 10 I/O book - Slot 0 4 Capacitor Book 11 I/O Book 3 - Slot 3 5 DCA Book 3 12 I/O Book 2 - Slot 2 (Inner Connectors)
  • Page 38 35 I/O Book Slot 3 (B1) (U1.18-P1-H4/Q8) 18 I/O Book Slot 2 (D1) (U1.18-P1-H3/Q5) I/O Book Slot 1 (D1) (U1.18-P1-H1/Q5) * The Y-cable that attaches to this connector terminates at BPC-A connector U1.35-P1-X4/Q10 and BPC-B connector U1.35-P2-X4/Q10. Eserver pSeries 690 Service Guide...
  • Page 39 Media Subsystem Locations The following figures show locations for devices installed in the media subsystem, and the SCSI IDs for the media devices. Note: The SCSI IDs shown for media indicate how installed devices are set when shipped from the factory.

  • Page 40: Disturbance Or System Attention Led

    The system attention LED lights on solid when an event occurs that either needs customer intervention or IBM service. The system attention LED is turned on when an entry is made in the service processor error log. The error entry is transmitted to the following:...

  • Page 41: Resetting The System Attention Led

    IBM Hardware Management Console for pSeries Installation and Operations Guide. Note: For information on these Service Focal Point settings, see ″Setting Up Surveillance and Enabling Surveillance Notifications″ in the IBM Hardware Management Console for pSeries Installation and Operations Guide.
  • Page 42 4. In the LED Management window, select one or more managed systems from the table. 5. Select Deactivate LED. The associated system attention LED is turned off. For more information about the virtual operator panel on the HMC, see the IBM Hardware Management Console for pSeries Installation and Operations Guide.

  • Page 43: 7040 Model 61D I/O Subsystem Locations

    7040 Model 61D I/O Subsystem Locations This section shows the locations for the I/O subsystem. A front view and a rear view with descriptions and locations for each part of the I/O subsystem are shown. 7040 Model 61D I/O Subsystem Front View 1 DASD 4-Pack 9 Drawer Fault/Identify LED (Amber) 2 DASD Disk Drive...
  • Page 44 4 I/O port connector 1 (Ux.y-P2/Q2) 10 I/O Subsystem Backplane Fault (Amber) 5 I/O port connector 0 (Ux.y-P2/Q1) 11 I/O Subsystem Backplane Power On (Green) 6 Media subsystem power connector 12 I/O LED (Currently Unused) (Ux.y-P2-V1/Q3) Eserver pSeries 690 Service Guide...
  • Page 45 I/O Subsystem DASD Locations The following figures show the DASD drive positions in an I/O subsystem. Note: The SCSI IDs are set when the drive is installed into the DASD 4-pack. 7040 Model 61D I/O Subsystem DASD Locations 1 Ux.y-P2/Z2-A8 9 Ux.y-P1/Z2-A8 2 Ux.y-P2/Z2-A9 10 Ux.y-P1/Z2-A9...
  • Page 46 PCI- PCI PCI- PCI Bridge Bridge Bridge SCSI Media Subsystem Power Ultra3 Internal SCSI SCSI Ultra3 Controllers SCSI PCI Slot - 64 bit 66/33mhz 3.3V PCI Slot - 64 bit 33mhz 5.0V Media Subsystem Front Eserver pSeries 690 Service Guide...
  • Page 47 I/O Subsystem Internal SCSI Distribution DASD 4 pack DASD 4 pack Rear DASD 4 pack DASD 4 pack P=PCI-PCI bridge RP=RIO-PCI bridge IS=Internal SCSI Ultra 3 I/O Subsystem Power Distribution Fan 4 DCA 2 Power Supply Fan 2 Rear Fan 3 DCA 1 Power Supply Fan 1...

  • Page 48: Power Subsystem Locations

    Note: For 32-way 1.7 GHz MCM systems a third BPD was added to supply the additional power needed by the CEC. To get the correct connector location numbers, refer to the table located in “Power Distribution Cabling” on page 33. Eserver pSeries 690 Service Guide...

  • Page 49: Power Distribution Cabling

    Power Distribution Cabling Power to the I/O subsystems, DCAs, Fans, and IBFs is connected from the bulk power distribution connectors to each subsystem through cables. The cable connectors are labeled on each end. The following describes the cables that connect from the BPC BPDs, and BPRs to the DCAs, fans, power supplies, I/O subsystems, and integrated battery features.
  • Page 50 Cabling” on page 36 for I/O subsystem power I/O subsystem power cabling. cabling. B35-BPC-J05 A09-MDA2-J02 A35-BPC-P05 to (AMD2-P01) J02 A35-BPC-J05 A09-MDA2-J01 B35-BPC-P05 to Red with white stripe (AMD2-P00) J01 B35-BPC-J04 A09-MDA1-J02 A35-BPC-P04 to (AMD1-P01) J02 Eserver pSeries 690 Service Guide...
  • Page 51 From Description Label Color A35-BPC-J04 A09-MDA1-J01 A35-BPC-P04 to Red with white stripe (AMD1-P00) J01 A35-BPC-J06 A18-MDA3-J01 A35-BPC-P06 to Red with white stripe (AMD3-P00) J01 B35-BPC-J06 A18-MDA3-J02 B35-BPC-P06 to (AMD3-P01) J02 B35-BPC-J07 A18-MDA4-J02 B35-BPC-P07 to (AMD4-P00) J02 A35-BPC-J07 A18-MDA4-J01 B35-BPC-P07 to Red with white stripe (AMD4-P01) J01 B35-BPC-J02...

  • Page 52: I/O Subsystem Power Distribution Cabling

    14b in the previous item 14b in the previous table) table) A35P-BPD1B-P06 Goes to CEC DCA-6 (see BPD1B to CEC DCA-6 (see Blue item 14a in the previous item 14b in the previous table) table) A35B-BPD1A-P07 No Connection Eserver pSeries 690 Service Guide...
  • Page 53 From Description Label Color (A=Primary) (Z=Secondary) A35P-BPD1B-P07 No Connection A35B-BPD2A-P04 Z09B-DCA1-P01 BPD1A to I/O Subsystem Yellow With Stripes #4 (with IBF) A35P-BPD2B-P04 Z09B-DCA1-P00 BPD1B to I/O Subsystem Yellow #4 (with IBF) A35B-BPD2A-P05 Z09B-DCA2-P01 BPD1A to I/O Subsystem Yellow With Stripes #4 (with IBF) A35P-BPD2B-P05 Z09B-DCA2-P00...

  • Page 54: Integrated Battery Feature Locations

    BPD3A to I/O Subsystem Blue With Stripes A35P-BPD3B-P08 Z19B-DCA1-P00 BPD3B to I/O Subsystem Blue A35B-BPD3A-P09 Z19B-DCA2-P01 BPD3A to I/O Subsystem Blue With Stripes A35P-BPD3B-P09 Z19B-DCA2-P00 BPD3B to I/O Subsystem Blue Integrated Battery Feature Locations 1 Connector to BPR Eserver pSeries 690 Service Guide...

  • Page 55: Subsystem Positioning And Cabling

    Subsystem Positioning and Cabling This section describes subsystem positioning and cabling for the Eserver pSeries 690. Operator Panel Cable and Diskette Drive Cable to the Media Subsystem (Rear View) 1 Primary I/O Book 3 Diskette Drive Data Cable 2 Cable Connecting the Operator Panel to the...

  • Page 56: Rear View Without Ibf

    C2 Secondary Rack 4 Fourth I/O Subsystem C3 Blank Space 5 Fifth I/O Subsystem C4 Blank Space 6 Sixth I/O Subsystem 1 First I/O Subsystem 7 Seventh I/O Subsystem 2 Second I/O Subsystem 8 Eighth I/O Subsystem Eserver pSeries 690 Service Guide...
  • Page 57 I/O Subsystem Positions, Fully Populated Primary and Secondary Rack (Rear View with IBFs) C1 Primary Rack 4B Four IBFs (primary rack), Position 4 C2 Primary I/O Book (Book 0) 5 Fifth I/O Subsystem C3 Secondary Rack 6 Sixth I/O Subsystem 1 First I/O Subsystem 7 Seventh I/O Subsystem 2 Second I/O Subsystem...
  • Page 58 1 First I/O Subsystem 4B Four IBFs 2 Second I/O Subsystem Note: The physical location shown for I/O Subsystem 4 is populated only when IBFs are present and four or more I/O subsystems are installed. Eserver pSeries 690 Service Guide...
  • Page 59 RIO and RIO-2 Cabling Rules If the CEC RIO ports are standard RIO, thumbscrew-style connectors, then connect a two-planar I/O loop to the RIO ports of the CEC in the following order: 1. Primary I/O Book Slot 0 (1, 2, 3, or 4 MCMs): RIO 1 A0&A1, RIO 2 B0&B1 2.
  • Page 60 2 GB per second without data path redundancy. Note: If all I/O planars are connected to the CEC with one I/O planar loops, the maximum number of I/O subsystems connected to the system is reduced to seven. Eserver pSeries 690 Service Guide...
  • Page 61 I/O Subsystems (1 Through 4 without IBFs) RIO Cabling to I/O Books, Two I/O Planar Loop Configuration, 2, 3, or 4 MCMs Only Note: The following figure applies to CECs with RIO, or thumbscrew retention, connections. 1 Primary Rack 5 First I/O Subsystem 2 Primary I/O Book 6 Fourth I/O Subsystem 3 Third I/O Subsystem...
  • Page 62 C1 Primary Rack 5 Fifth I/O Subsystem C2 Secondary Rack 6 Sixth I/O Subsystem C3 Secondary I/O Book Note: RIO cabling to I/O Subsystems 5 and 6 is the same for configurations with or without the IBFs. Eserver pSeries 690 Service Guide...
  • Page 63 I/O Subsystems (7 and 8) RIO Cabling to the Third I/O Book, Two I/O Planar Loop Configuration, 4 MCMs Only Note: The following figure applies to CECs with RIO, or thumbscrew retention, connections. C1 Primary Rack 4 Fourth I/O Subsystem C2 Secondary Rack 4B Two IBFs (maximum), Position 4 C3 Third I/O Book (Book 3)
  • Page 64 B0 Connection to I/O Book (Book 0) 4 Second I/O Subsystem B1 Connection to I/O Book (Book 0) 5 First I/O Subsystem C0 Connection to I/O Book (Book 2) 6 Secondary I/O Book C1 Connection to I/O Book (Book 2) Eserver pSeries 690 Service Guide...
  • Page 65 I/O Subsystems (4 through 6 with IBFs) RIO Cabling to I/O Books, Two I/O Planar Loop Configuration, 3 or 4 MCMs Only Note: The following figure applies to CECs with RIO, or thumbscrew retention, connections. C1 Secondary Rack 6 Sixth I/O Subsystem C2 Primary Rack 7 Seventh I/O Subsystem C3 Secondary I/O Book in I/O Slot 3...
  • Page 66 Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. 1 Primary Rack 5 First I/O Subsystem 2 Primary I/O Book 6 Fourth I/O Subsystem 3 Third I/O Subsystem 7 Secondary I/O Book 4 Second I/O Subsystem Eserver pSeries 690 Service Guide...
  • Page 67 I/O Subsystems (5 and 6) RIO-2 Cabling to the Secondary I/O Book, Two I/O Planar Loop Configuration, 2 MCMs Only Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. C1 Primary Rack 5 Fifth I/O Subsystem C2 Secondary Rack 6 Sixth I/O Subsystem C3 Secondary I/O Book...
  • Page 68 C1 Primary Rack 5 Fifth I/O Subsystem C2 Secondary Rack 6 Sixth I/O Subsystem C3 Secondary I/O Book Note: RIO-2 cabling to I/O Subsystems 5 and 6 is the same for configurations with or without the IBFs. Eserver pSeries 690 Service Guide...
  • Page 69 I/O Subsystems (7 and 8) RIO-2 Cabling to the Third I/O Book, Two I/O Planar Loop Configuration, 3 or 4 MCMs Only Note: The following figure applies to CECs with RIO-2, or bayonette retention connections. C1 Primary Rack 5 Fifth I/O Subsystem C2 Secondary Rack 6 Sixth I/O Subsystem C3 Third I/O Book (Book 3)
  • Page 70 Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. 1 Primary Rack 5 First I/O Subsystem 2 Primary I/O Book 6 Fourth I/O Subsystem 3 Third I/O Subsystem 7 Secondary I/O Book 4 Second I/O Subsystem Eserver pSeries 690 Service Guide...
  • Page 71 I/O Subsystems (5 and 6) RIO-2 Cabling to the Secondary I/O Book, One I/O Planar Loop Configuration, 3 MCMs Only Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. C1 Primary Rack 5 Fifth I/O Subsystem C2 Secondary Rack 6 Sixth I/O Subsystem C3 Secondary I/O Book...
  • Page 72 C1 Primary Rack 5 Fifth I/O Subsystem C2 Secondary Rack 6 Sixth I/O Subsystem C3 Secondary I/O Book Note: RIO-2 cabling to I/O Subsystems 5 and 6 is the same for configurations with or without the IBFs. Eserver pSeries 690 Service Guide...
  • Page 73 I/O Subsystems (7) RIO-2 Cabling to the Fourth I/O Book, One I/O Planar Loop Configuration, 4 MCMs Only Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. C1 Primary Rack 4 Fourth I/O Subsystem C2 Secondary Rack 4B Two IBFs (maximum), Position 4 C3 Third I/O Book (Book 3) 5 Fifth I/O Subsystem...
  • Page 74 B0 Connection to I/O Book (Book 0) 4 Second I/O Subsystem B1 Connection to I/O Book (Book 0) 5 First I/O Subsystem C0 Connection to I/O Book (Book 2) 6 Secondary I/O Book C1 Connection to I/O Book (Book 2) Eserver pSeries 690 Service Guide...
  • Page 75 I/O Subsystems (1 through 3 with IBFs) RIO-2 Cabling to I/O Books, One I/O Planar Loop Configuration, 2 MCMs Only Note: The following figure applies to CECs with RIO-2, or bayonette retention, connections. 1 Primary Rack A0 Connection to I/O Book (Book 0) 2 Primary I/O Book A1 Connection to I/O Book (Book 0) 3 Third I/O Subsystem...
  • Page 76 3 Third I/O Subsystem B1 Connection to I/O Book (Book 2) 4 Fourth I/O Subsystem D0 Connection to I/O Book (Book 2) 4B Integrated Battery Feature (IBF) D1 Connection to I/O Book (Book 2) 5 Fifth I/O Subsystem Eserver pSeries 690 Service Guide...

  • Page 77: Power And Scsi Cables To The Media Subsystem

    Power and SCSI Cables to the Media Subsystem 1 Primary Rack 5 SCSI Cable for Media Subsystem Rear Drives 2 Primary I/O Book 6 SCSI Cable for Media Subsystem Front Drives 3 Power Cable for Media Subsystem Front 7 Power Cable for Media Subsystem Rear Drives Drives 4 Rear of Media Subsystem Chapter 1.
  • Page 78 Primary I/O Book To connect your HMC to the Eserver pSeries 690, connect the serial cable into serial port 1 located on the back of the HMC. Connect the other end of the serial cable into the HMC1 connector located on the primary I/O book in the managed system.

  • Page 79: System Memory

    System Memory All of the main memory for the Eserver pSeries 690 consists of pluggable memory books in reserved slots with two memory controllers per book. The memory books are available in various sizes. Memory modules are not removable from the memory books. A minimum of 8 GB of memory must be installed for the system to operate.

  • Page 80: Memory Requirements

    When the system is ordered, the installed memory is positioned according to the following guidelines: v The pSeries 690 has eight memory slots. Four memory slots use inward-facing memory cards and four use outward-facing memory cards. The inward-facing memory slots are used by the first and second processor module positions, while the outward-facing memory slots support the third and fourth 8-way processor module positions.

  • Page 81: I/O Subsystem Features

    I/O Subsystem Features I/O subsystems have two redundant power supplies. One of these power supplies is capable of providing the necessary voltages and currents, independent of the other power supply. The left and right power-supply output voltages are connected and monitored by the power distribution board contained in the I/O subsystem.
  • Page 82 On, steady green System power connected System power connected System power connected and turned on and turned on and turned on Eserver pSeries 690 Service Guide...

  • Page 83: Logical And Physical Locations

    Logical and Physical Locations The Eserver pSeries 690 system uses physical location codes in conjunction with AIX location codes to provide mapping of the failing field replaceable units (FRUs). The location codes are produced by the system’s firmware and the operating system. There are no Linux-specific location codes, but physical location codes may appear in the Linux error logs.

  • Page 84: Multiple Fru Callout Instructions

    If the system is logically partitioned, the HMC must be attached. You can use the HMC to enable any FRU identify LED to be flashed. See the IBM Hardware Management Console for pSeries Installation and Operations Guide for instructions on activating and deactivating a FRU identify LED.

  • Page 85: Aix Location Codes

    AIX Location Codes Note: AIX location codes are not available if Linux is the operating system. The basic formats of the AIX location codes are as follows: v For non-SCSI devices/drives: AB-CD-EF-GH v For SCSI devices/drives: AB-CD-EF-G,H Non-SCSI Devices For planars (backplanes), cards, and non-SCSI devices, the location code is defined as follows: AB-CD-EF-GH | | | | | | | Device/FRU/Port ID...

  • Page 86: Scsi Devices

    PCI adapter in first I/O subsystem, slot 1 (primary rack): – Physical location code U1.9-P1-I1 – AIX location code 2V-08 PCI adapter in fifth I/O subsystem, slot 1 (secondary rack): – Location Code U2.1-P1-I1 – AIX location Code 8V-08 Eserver pSeries 690 Service Guide...

  • Page 87: Aix And Physical Location Code Reference Tables

    AIX location codes are not available when the operating system is Linux. The following illustrations show the location codes that are used to identify the major functional units in the pSeries 690 primary and secondary racks. The following figure shows the primary rack locations. U1.35-P2-X1 Unused U1.35-P1-X1 Unused...
  • Page 88 The following figure shows the secondary rack locations. U2.19 U2.19 U2.17-P2-V6 U2.17-P1-V5 U2.13 U2.13 U2.9 U2.9 U2.5 U2.5 U2.1 U2.1 REAR FRONT Eserver pSeries 690 Service Guide...
  • Page 89 The following illustration shows the location codes that are used to identify the MCM modules and L3 modules (located behind fans 3--U1.18-P1-F3 and 4--U1.18-P1-F4). 1 L3, Location: U1.18-P1-C5 12 L3, Location: U1.18-P1-C16 2 L3, Location: U1.18-P1-C6 13 L3, Location: U1.18-P1-C20 3 L3, Location: U1.18-P1-C10 14 L3, Location: U1.18-P1-C19 4 MCM 0, Location: U1.18-P1-C1...
  • Page 90 The following tables contain location codes that are used to identify functional units in the Eserver pSeries 690 systems. Each table shows the locations for a physical part of the system. Location Physical Logical FRU Name Code Location Connection Connection...
  • Page 91 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem -1A U1.35-P1-X3/Q1 Connector 0 I/O Subsystem 1 (DCA 1) I/O Subsystem -1A Cable U1.35-P1-X3/Q1# I/O Subsystem -1B U1.35-P1-X3/Q2 Connector 1 I/O Subsystem 1 (DCA 2) I/O Subsystem -1B Cable U1.35-P1-X3/Q2# I/O Subsystem -2A U1.35-P1-X3/Q3 Connector 2...
  • Page 92 BPC A - MDA-1 U1.35-P1-X4/Q1 Connector BPC A - MDA-1 Cable U1.35-P1-X4/Q1# BPC A - MDA-2 U1.35-P1-X4/Q2 Connector BPC A - MDA-2 Cable U1.35-P1-X4/Q2# BPC A - MDA-3 U1.35-P1-X4/Q3 Connector BPC A - MDA-3 Cable U1.35-P1-X4/Q3# Eserver pSeries 690 Service Guide...
  • Page 93 Location Physical Logical FRU Name Code Location Connection Connection Code BPC A - MDA-4 U1.35-P1-X4/Q4 Connector BPC A - MDA-4 Cable U1.35-P1-X4/Q4# BPC A - DCA-1 U1.35-P1-X4/Q5 Connector BPC A - DCA-1 Cable U1.35-P1-X4/Q5# BPC A - DCA-2 U1.35-P1-X4/Q6 Connector BPC A - DCA-2 Cable U1.35-P1-X4/Q6# BPC A - DCA-3...
  • Page 94 Bulk Power Regulator 2 U1.35-P2-V2 BPR 2 Connector U1.35-P2-V2/Q1 BPR 2 Cable to IBF 2A U1.35-P2-V2/Q1# Bulk Power Distribution U1.35-P2-X3 I/O Subsystem -1A U1.35-P2-X3/Q1 Connector 0 I/O Subsystem 1 (DCA 1) I/O Subsystem -1A Cable U1.35-P2-X3/Q1# Eserver pSeries 690 Service Guide...
  • Page 95 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem -1B U1.35-P2-X3/Q2 Connector 1 I/O Subsystem 1 (DCA 2) I/O Subsystem -1B Cable U1.35-P2-X3/Q2# I/O Subsystem -2A U1.35-P2-X3/Q3 Connector 2 I/O Subsystem 2 (DCA 1) I/O Subsystem -2A Cable U1.35-P2-X3/Q3# I/O Subsystem -2B U1.35-P2-X3/Q4 Connector 3...
  • Page 96 U1.35-P2-X4/Q5# BPC B - DCA-2 U1.35-P2-X4/Q6 Connector BPC B - DCA-2 Cable U1.35-P2-X4/Q6# BPC B - DCA-3 U1.35-P2-X4/Q7 Connector BPC B - DCA-3 Cable U1.35-P2-X4/Q7# BPC TO BPC Connector U1.35-P2-X4/Q8 BPC TO BPC Cable U1.35-P2-X4/Q8# Eserver pSeries 690 Service Guide...
  • Page 97 Location Physical Logical FRU Name Code Location Connection Connection Code BPC TO EPOC U1.35-P2-X4/Q9 Connector BPC TO EPOC Cable U1.35-P2-X4/Q9# BPC TO Primary I/O U1.35-P2-X4/Q10 Book Connector U1.18-P1-H2/Q8 BPC B ″Y″ Cable To U1.35-P2-X4/Q10# Primary I/O Book Connector U1.18-P1-H2/Q8 BPC TO BPF Connector U1.35-P2-X4/Q11 BPC TO BPF Cable U1.35-P2-X4/Q11#...
  • Page 98 Primary I/O book-1 Port 1 Connector 3 U1.18-P1-H2/Q4# (2-1) Cable 4 see “I/O Subsystems (1 Through 4 without IBFs) RIO Cabling to I/O Books, Two I/O Planar Loop Configuration, 2, 3, or 4 MCMs Only” on page 45 for cable connections. Eserver pSeries 690 Service Guide...
  • Page 99 Location Physical Logical FRU Name Code Location Connection Connection Code ISA Bridge U1.18-P1-H2 Real Time Clock (RTC) U1.18-P1-H2 Battery (TOD) U1.18-P1-H2-V1 Error logging VPD Card (MCM -0) U1.18-P1-H2.3 Error logging VPD Card (MCM -1) U1.18-P1-H2.5 Error logging VPD Card (MCM -2) U1.18-P1-H2.4 Error logging VPD Card (MCM -3) U1.18-P1-H2.6...
  • Page 100 High Performance Switch. If there is an SNI adapter in U1.18-P1-H4, go to ″SNI Adapter for High Performance Switch″ on page 85 I/O Book 3, Port 12 Connector 2 (1-0) U1.18-P1-H4/Q1 (C0) Eserver pSeries 690 Service Guide...
  • Page 101 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Book 3, Port 12 Connector 2 (1-0) U1.18-P1-H4/Q1# Cable 2 , see “I/O Subsystems (7 and 8) RIO Cabling to the Third I/O Book, Two I/O Planar Loop Configuration, 4 MCMs Only”...
  • Page 102 DCA 6- BPA A - BPD2 - 10 Cable U1.18-P1-V8/Q1# DCA 6- BPA B - BPD2 - 10 Connector U1.18-P1-V8/Q2 DCA 6- BPA B - BPD2 - 10 Cable U1.18-P1-V8/Q2# RH CAP Card U1.18-P1-V3 RH CAP Card U1.18-P1-V7 Eserver pSeries 690 Service Guide...
  • Page 103 Location Physical Logical FRU Name Code Location Connection Connection Code Hourglass Card Assembly U1.18-P1-X5 MCM Module 0 4 & 8 way U1.18-P1-C1 Processor 0 (W/ L1 & L2 Cache) U1.18-P1-C1 00-00 Processor 1 (W/ L1 & L2 Cache) U1.18-P1-C1 00-01 Processor 2 (W/ L1 &...
  • Page 104 Fan Controller 4 TO BPC A Cable U1.18-X4/Q1# Fan Controller 4 TO BPC B Connector U1.18-X4/Q2 Fan Controller 4 TO BPC B Cable U1.18-X4/Q2# Fan Assembly 1 U1.18-F1 Fan Assembly 2 U1.18-F2 Fan Assembly 3 U1.18-F3 Eserver pSeries 690 Service Guide...
  • Page 105 Location Physical Logical FRU Name Code Location Connection Connection Code Fan Assembly 4 U1.18-F4 Location Physical Logical FRU Name Code Location Connection Connection Code Media Subsystem Locations Media Drawer chassis U1.17 Media Drawer - Operator U1.17-L1 Panel, Operator Panel U1.17-L1/Q1 Connector Operator Panel Cable U1.17-L1/Q1#...
  • Page 106 2w-xx or 2x-xx EADS 3 - PCI Controller U1.9-P1 30-58, 30-5A, 30-5E PCI Slot 8 Content U1.9-P1-I8 31-08 to 31-0F or 32-xx or 32-xx PCI Slot 9 Content U1.9-P1-I9 34-08 to 34-0F or 35-xx or 36-xx Eserver pSeries 690 Service Guide...
  • Page 107 Location Physical Logical FRU Name Code Location Connection Connection Code PCI Slot 10 Content U1.9-P1-I10 3A-08 to 3A-0F or 3B-xx or 3C-xx I/O Riser Card U1.9-P1 I/O Port Connector U1.9-P1/Q1 I/O Port Cable From U1.9-P1/Q1# GX1A-port 1 I/O Port Connector U1.9-P1/Q2 I/O Port Cable to port 0 U1.9-P1/Q2#...
  • Page 108 9 connected to controller 2 on P2 SCSI DASD 3 hdisk at ID U1.9-P2/Z2-Aa 3s-08-00-10,0 A connected to controller 2 on P2 SCSI DASD 4 hdisk at ID U1.9-P2/Z2-Ab 3s-08-00-11,0 A connected to controller 2 on P2 Eserver pSeries 690 Service Guide...
  • Page 109 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI Enclosure Services U1.9-P2/Z2-Bf 3s-08-00-15,0 SES connected to controller 2 on P2 DASD 4-pack Cage and U1.9-P4 card (2) DASD 4-pack Cage and U1.9-P4-N1 card (2) VPD SCSI DASD 1 hdisk at ID U1.9-P2/Z1-A8 3b-08-00-8,0 8 connected to controller...
  • Page 110 PCI Slot 1 Content U1.5-P1-I1 41-08 to 41-0F or 42-xx or 43-xx PCI Slot 2 Content U1.5-P1-I2 44-08 to 44-0F or 45-xx or 47-xx PCI Slot 3 Content U1.5-P1-I3 47-08 to 47-0F or 48-xx or 49-xx Eserver pSeries 690 Service Guide...
  • Page 111 Location Physical Logical FRU Name Code Location Connection Connection Code PCI Slot 4 Content U1.5-P1-I4 4A-08 to 4A-0F or 4B-xx or 4C-xx EADS 2 - PCI Controller U1.5-P1 4E-58, 4E-5A, 4E-5E PCI Slot 5 Content U1.5-P1-I5 4F-08 to 4F-0F or 4G-xx or 4H-xx PCI Slot 6 Content U1.5-P1-I6 4J-08 to 4J-0F...
  • Page 112 I/O Subsystem SCSI U1.5-P1/Z1 4M-08 controller 1 on P1 I/O Subsystem SCSI U1.5-P1/Z2 4b-08 controller 2 on P1 I/O Subsystem SCSI U1.5-P2/Z1 57-08 controller 1 on P2 I/O Subsystem SCSI U1.5-P2/Z2 5M-08 controller 2 on P2 Eserver pSeries 690 Service Guide...
  • Page 113 Location Physical Logical FRU Name Code Location Connection Connection Code DASD 4-pack Cage and U1.5-P3 card (1) DASD 4-pack Cage and U1.5-P3-N1 card (1) VPD SCSI DASD 1 hdisk at ID U1.5-P2/Z2-A8 5M-08-00-8,0 8 connected to controller 2 on P2 SCSI DASD 2 hdisk at ID U1.5-P2/Z2-A9 5M-08-00-9,0...
  • Page 114 I/O Subsystem Fan U1.5-F2 (MSA) I/O Subsystem Fan U1.5-F3 (MSA) I/O Subsystem Fan U1.5-F4 (MSA) Media Drawer Power U1.5-P1-X1/Q3 Connector Media Drawer Power U1.5-P1-X1/Q3# Cable Media Drawer Power U1.5-P2-X2/Q3 Connector Media Drawer Power U1.5-P2-X2/Q3# Cable Eserver pSeries 690 Service Guide...
  • Page 115 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem 3 Locations I/O Subsystem 1 Chassis (MT/M Serial #) U1.1 & Midplane Card I/O Subsystem Left IO U1.1-P1 backplane assembly I/O Subsystem Left IO U1.1-P1-N1 backplane assembly VPD EADS 1 - PCI Controller U1.1-P1 5U-58, 5U-5A,...
  • Page 116 DCA 1 to (BPA A) BPD1- U1.1-V1/Q2# 1A Cable Thermal Sensor U1.1-V1 I/O Subsystem DCA 2 U1.1-V2 DCA 2 to (BPA B) BPD1- U1.1-V2/Q1 1B Connector P05 DCA 2 to (BPA B) BPD1- U1.1-V2/Q1# 1B Cable Eserver pSeries 690 Service Guide...
  • Page 117 Location Physical Logical FRU Name Code Location Connection Connection Code DCA 2 to (BPA A) BPD1- U1.1-V2/Q2 1B Connector P05 DCA 2 to (BPA A) BPD1- U1.1-V2/Q2# 1B Cable Thermal Sensor U1.1-V2 I/O Subsystem SCSI U1.1-P1/Z1 5s-08 controller 1 on P1 I/O Subsystem SCSI U1.1-P1/Z2 67-08...
  • Page 118 1 on P1 SCSI Enclosure Services U1.1-P1/Z1-Af 5s-08-00-15,0 SES connected to controller 1 on P1 I/O Subsystem Fan U1.1-F1 (MSA) I/O Subsystem Fan U1.1-F2 (MSA) I/O Subsystem Fan U1.1-F3 (MSA) I/O Subsystem Fan U1.1-F4 (MSA) Eserver pSeries 690 Service Guide...
  • Page 119 Location Physical Logical FRU Name Code Location Connection Connection Code Media Drawer Power U1.1-P1-X1/Q3 Connector Media Drawer Power U1.1-P1-X1/Q3# Cable Media Drawer Power U1.1-P2-X2/Q3 Connector Media Drawer Power U1.1-P2-X2/Q3# Cable Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem 4 Locations (If No IBF Installed) Note: If the Integrated Battery Feature (IBF) is installed, I/O subsystem 4 is in I/O subsystem 7 position.
  • Page 120 8R-xx or 8S-xx I/O Riser Card U1.13-P2 I/O Port Connector U1.13-P2/Q1 I/O Port Cable From U1.13-P2/Q1# Riser port 1 P1.1/Q1 I/O Port Connector U1.13-P2/Q2 I/O Port Cable to U1.13-P2/Q2# GX1A-port 2 I/O Subsystem DCA 1 U1.13-V1 Eserver pSeries 690 Service Guide...
  • Page 121 Location Physical Logical FRU Name Code Location Connection Connection Code DCA 1 to (BPA B) BPD1- U1.13-V1/Q1 1A Connector P06 DCA 1 to (BPA B) BPD1- U1.13-V1/Q1# 1A Cable DCA 1 to (BPA A) BPD1- U1.13-V1/Q2 1A Connector P06 DCA 1 to (BPA A) BPD1- U1.13-V1/Q2# 1A Cable Thermal Sensor...
  • Page 122 DASD 4-pack Cage and U1.13-P6-N1 card (4) VPD SCSI DASD 1 hdisk at ID U1.13-P1/Z1-A8 7M-08-00-8,0 8 connected to controller 1 on P1 SCSI DASD 2 hdisk at ID U1.13-P1/Z1-A9 7M-08-00-9,0 9 connected to controller 1 on P1 Eserver pSeries 690 Service Guide...
  • Page 123 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI DASD 3 hdisk at ID U1.13-P1/Z1-Aa 7M-08-00-10,0 A connected to controller 1 on P1 SCSI DASD 4 hdisk at ID U1.13-P1/Z1-Ab 7M-08-00-11,0 B connected to controller 1 on P1 SCSI Enclosure Services U1.13-P1/Z1-Af 7M-08-00-15,0...
  • Page 124 U2.9-P1 I/O Port Connector U2.9-P1/Q1 I/O Port Cable From U2.9-P1/Q1# GX1A-port 3 I/O Port Connector U2.9-P1/Q2 I/O Port Cable to port 0 U2.9-P1/Q2# on next Riser card U2.9-P2/Q1 I/O Subsystem Right IO U2.9-P2 backplane assembly Eserver pSeries 690 Service Guide...
  • Page 125 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem Right IO U2.9-P2-N1 backplane assembly VPD EADS 1 - PCI Controller U2.9-P2 7j-58, 7j-5A, 7j-5C, 7j-5E PCI Slot 1 Content U2.9-P2-I1 7k-08 to 7k-0F or 7m-xx or 7n-xx PCI Slot 2 Content U2.9-P2-I2 7p-08 to 7p-0F...
  • Page 126 DASD 4-pack Cage and U2.9-P4-N1 card (2) VPD SCSI DASD 1 hdisk at ID U2.9-P2/Z1-A8 87-08-00-8,0 8 connected to controller 1 on P2 SCSI DASD 2 hdisk at ID U2.9-P2/Z1-A9 87-08-00-9,0 9 connected to controller 1 on P2 Eserver pSeries 690 Service Guide...
  • Page 127 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI DASD 3 hdisk at ID U2.9-P2/Z1-Aa 87-08-00-10,0 A connected to controller 1 on P2 SCSI DASD 4 hdisk at ID U2.9-P2/Z1-Ab 87-08-00-11,0 B connected to controller 1 on P2 SCSI Enclosure Services U2.9-P2/Z1-Af 87-08-00-15,0...
  • Page 128 8q-xx or 8r-xx PCI Slot 7 Content U2.1-P1-I7 8v-08 to 8v-0F or 8w-xx or 8x-xx EADS 3 - PCI Controller U2.1-P1 90-58, 90-5A, 90-5E PCI Slot 8 Content U2.1-P1-I8 91-08 to 91-0F or 92-xx or 93-xx Eserver pSeries 690 Service Guide...
  • Page 129 Location Physical Logical FRU Name Code Location Connection Connection Code PCI Slot 9 Content U2.1-P1-I9 94-08 to 94-0F or 95-xx or 96-xx PCI Slot 10 Content U2.1-P1-I10 9A-08 to 9A-0F or 9B-xx or 9C-xx I/O Riser Card U2.1-P1 I/O Port Connector U2.1-P1/Q1 I/O Port Cable From U2.1-P1/Q1#...
  • Page 130 8 connected to controller 2 on P2 SCSI DASD 2 hdisk at ID U2.1-P2/Z2-A9 9s-08-00-9,0 9 connected to controller 2 on P2 SCSI DASD 3 hdisk at ID U2.1-P2/Z2-Aa 9s-08-00-10,0 A connected to controller 2 on P2 Eserver pSeries 690 Service Guide...
  • Page 131 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI DASD 4 hdisk at ID U2.1-P2/Z2-Ab 9s-08-00-11,0 B connected to controller 2 on P2 SCSI Enclosure Services U2.1-P2/Z2-Af 9s-08-00-15,0 SES connected to controller 2 on P2 DASD 4-pack Cage and U2.1-P card (2) DASD 4-pack Cage and...
  • Page 132 I/O Subsystem Fan U2.1-F2 (MSA) I/O Subsystem Fan U2.1-F3 (MSA) I/O Subsystem Fan U2.1-F4 (MSA) Media Drawer Power U2.1-P1-X1/Q3 Connector Media Drawer Power U2.1-P1-X1/Q3# Cable Media Drawer Power U2.1-P2-X2/Q3 Connector Media Drawer Power U2.1-P2-X2/Q3# Cable Eserver pSeries 690 Service Guide...
  • Page 133 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem 6 Locations I/O Subsystem 1 Chassis (MT/M Serial #) U2.5 & Midplane Card I/O Subsystem Left IO U2.5-P1 backplane assembly I/O Subsystem Left IO U2.5-P1-N1 backplane assembly VPD EADS 1 - PCI Controller U2.5-P1 A0-58, A0-5A,...
  • Page 134 DCA 1 to (BPA B) BPD2- U2.5-V1/Q1# 6A Cable DCA 1 to (BPA A) BPD2- U2.5-V1/Q2 6A Connector P02 DCA 1 to (BPA A) BPD2- U2.5-V1/Q2# 6A Cable Thermal Sensor U2.5-V1 I/O Subsystem DCA 2 U2.5-V2 Eserver pSeries 690 Service Guide...
  • Page 135 Location Physical Logical FRU Name Code Location Connection Connection Code DCA 2 to (BPA B) BPD2- U2.5-V2/Q1 6B Connector P03 DCA 2 to (BPA B) BPD2- U2.5-V2/Q1# 6B Cable DCA 2 to (BPA A) BPD2- U2.5-V2/Q2 6B Connector P03 DCA 2 to (BPA A) BPD2- U2.5-V2/Q2# 6B Cable Thermal Sensor...
  • Page 136 1 on P1 SCSI DASD 4 hdisk at ID U2.5-P1/Z1-Ab AM-08-00-11,0 B connected to controller 1 on P1 SCSI Enclosure Services U2.5-P1/Z1-Af AM-08-00-15,0 SES connected to controller 1 on P1 I/O Subsystem Fan U2.5-F1 (MSA) Eserver pSeries 690 Service Guide...
  • Page 137 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Subsystem Fan U2.5-F2 (MSA) I/O Subsystem Fan U2.5-F3 (MSA) I/O Subsystem Fan U2.5-F4 (MSA) Media Drawer Power U2.5-P1-X1/Q3 Connector Media Drawer Power U2.5-P1-X1/Q3# Cable Media Drawer Power U2.5-P2-X2/Q3 Connector Media Drawer Power U2.5-P2-X2/Q3# Cable...
  • Page 138 Cp-08 to Cp-0F or Cq-xx or Cr-xx PCI Slot 10 Content U2.13-P2-I10 Cv-08 to Cv-0F or Cw-xx or Cx-xx I/O Riser Card U2.13-P2 I/O Port Connector U2.13-P2/Q1 I/O Port Cable From U2.13-P2/Q1# Riser port 1 P1.1/Q1 Eserver pSeries 690 Service Guide...
  • Page 139 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Port Connector U2.13-P2/Q2 I/O Port Cable to U2.13-P2/Q2# GX1A-port 2 I/O Subsystem DCA 1 U2.13-V1 DCA 1 to (BPA B) BPD2- U2.13-V1/Q1 7A Connector P02 DCA 1 to (BPA B) BPD2- U2.13-V1/Q1# 7A Cable DCA 1 to (BPA A) BPD2-...
  • Page 140 C7-08-00-11,0 B connected to controller 2 on P1 SCSI Enclosure Services U2.13-P1/Z2-Af C7-08-00-15,0 SES connected to controller 2 on P1 DASD 4-pack Cage and U2.13-P6 card (4) DASD 4-pack Cage and U2.13-P6-N1 card (4) VPD Eserver pSeries 690 Service Guide...
  • Page 141 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI DASD 1 hdisk at ID U2.13-P1/Z1-A8 Bs-08-00-8,0 8 connected to controller 1 on P1 SCSI DASD 2 hdisk at ID U2.13-P1/Z1-A9 Bs-08-00-9,0 9 connected to controller 1 on P1 SCSI DASD 3 hdisk at ID U2.13-P1/Z1-Aa Bs-08-00-10,0...
  • Page 142 Dq-xx or Dr-xx PCI Slot 3 Content U2.19-P2-I3 Ds-08 to Ds-0F or Dt-xx or Du-xx PCI Slot 4 Content U2.19-P2-I4 Dv-08 to Dv-0F or Dw-xx or Dx-xx EADS 2 - PCI Controller U2.19-P2 E0-58, E0-5A, E0-5E Eserver pSeries 690 Service Guide...
  • Page 143 Location Physical Logical FRU Name Code Location Connection Connection Code PCI Slot 5 Content U2.19-P2-I5 E1-08 to E1-0F or E2-xx or E3-xx PCI Slot 6 Content U2.19-P2-I6 E4-08 to E4-0F or E5-xx or E6-xx PCI Slot 7 Content U2.19-P2-I7 EA-08 to EA-0F or EB-xx or EC-xx EADS 3 - PCI Controller U2.19-P2...
  • Page 144 SES connected to controller 1 on P2 DASD 4-pack Cage and U2.19-P5 card (3) DASD 4-pack Cage and U2.19-P5-N1 card (3) VPD SCSI DASD 1 hdisk at ID U2.19-P1/Z2-A8 Db-08-00-8,0 8 connected to controller 2 on P1 Eserver pSeries 690 Service Guide...
  • Page 145 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI DASD 2 hdisk at ID U2.19-P1/Z2-A9 Db-08-00-9,0 9 connected to controller 2 on P1 SCSI DASD 3 hdisk at ID U2.19-P1/Z2-Aa Db-08-00-10,0 A connected to controller 2 on P1 SCSI DASD 4 hdisk at ID U2.19-P1/Z2-Ab Db-08-00-11,0...

  • Page 146: System Requirements For Adding Processor Mcms

    Note: 1.7 U1.18-P1-C2 (2X) U1.18-P1-V3 U1.18-P1-M8 GHz MCMs require U1.18-P1-V1 U1.18-P1-V7 additional FC 6189 (3x U1.18-P1-V2 total) at location FC 6189 U1.18-P1-V6. All other (2X) MCM speeds require 2x FC U1.18-P1-V4 6189 as shown. U1.18-P1-V5 Eserver pSeries 690 Service Guide...
  • Page 147 Add 4th MCM Qty = 0 FC 6170 Qty = 2 C5, C9, C13, U1.18-P1-H2.6 U1.18-P1-M5 Position C2 Note: 1.7 (2X) U1.18-P1-V3 U1.18-P1-M1 GHz MCMs require U1.18-P1-V1 U1.18-P1-V7 additional FC 6189 (4x U1.18-P1-V2 total) at location FC 6189 U1.18-P1-V8. All other (3X) MCM speeds require (3x)

  • Page 148: Specifications

    690 system configurations. Power and Electrical Requirements Redundant power line cords are standard on the pSeries 690. The system uses dual ac power cords. For maximum availability, each of the power cords should be fed from independent power grids.
  • Page 149 normal operation. The following table illustrates phase imbalance as a function of BPR configuration. Number of BPRs per Phase A Line Current Phase B Line Current Phase C Line Current Power / Vline Power / Vline 0.5 Power / Vline 0.866 Power / Vline 0.5 Power / Vline 0.577 Power / Vline...
  • Page 150 The following figure shows another way of distributing the unbalanced load evenly. Using this method, the three-pole breakers are alternated with two-pole breakers. Eserver pSeries 690 Service Guide...
  • Page 151 Power Cord Configuration: The power cords exit the system from different points of the frame as indicated in the following illustration. Rear Front All Single-Frame Systems (Top Down View) Rear Front All Double-Frame Systems (Top Down View) Chapter 1. Reference Information...

  • Page 152: Dimensions And Weight

    __ 1. The pSeries 690 is equipped to use 200-240 V / 380-415 V / 480 V ac, three-phase. Check that the correct power source is available.
  • Page 153 Height 2025 mm (79.72 in.) 2025 mm (79.72 in.) 2025 mm (79.72 in.) 2025 mm (79.72 in.) Width 785 mm (30.91 in.) 1575 mm (62.00 in.) 785 mm (30.91 in.) 1575 mm (62.00 in.) Depth 1342 mm (52.83 in.) 1342 mm (52.83 in.) 1494 mm (58.83 in.) 1494 mm (58.83 in.) Weight (maximum...

  • Page 154: Acoustical Noise Emissions

    2000 kg (4409 lbs.) Width 750 mm (29.5 in.) 1539 mm (60.6 in.) 750 mm (29.5 in.) 1539 mm (60.6 in.) Depth 1173 mm (46.2 in.) 1173 mm (46.2 in.) 1173 mm (46.2 in.) 1173 mm (46.2 in.) Eserver pSeries 690 Service Guide...
  • Page 155 Notes: 1. For 2 frame systems, widths of Frame A and Frame B. were added (the depth remains 1069 mm (42.1 in.), not including frame extenders). 2. For 2 frame systems, weights are based on maximum configuration (less than addition of maximum weights for each frame).
  • Page 156 36 in. at the rear of the frame (measured from the base frame). 2. Weight-distribution areas should not be overlapped. 3. Floor-loading weight distribution distances should not exceed 762 mm (30 in.) in any direction when measured from the base frame. Eserver pSeries 690 Service Guide...
  • Page 157 Plan Views The following illustration shows dimensional planning information for single-frame systems and double-frame systems. 750 mm (29.5 in.) 18 mm 58 mm (2.3 in.) (0.7 in.) Slimline Rear Cover 211 mm (8.3 in.) Acoustical Rear Cover 1342 mm (52.8 in.) Slimline Covers 1174 mm (46.2 in.)

  • Page 158: Total System Power Consumption

    8-way 16-way 8-way 16-way 3213 5471 4932 8366 3581 5839 5980 9414 3949 6207 7028 10462 4317 6575 8076 11510 6943 12558 7311 13606 7679 14654 8047 15702 Eserver pSeries 690 Service Guide...
  • Page 159 Number of I/O 1.3 GHz 8-way Modules (minimum power 1.3 GHz 8-way Modules (maximum power Drawers consumption, in watts) consumption, in watts) (7040-61D) 8-way 16-way 24-way 32-way 8-way 16-way 24-way 32-way 2084 3213 4342 5471 3215 4932 6649 8366 2452 3581 4710 5839...
  • Page 160 16 GB memory book - 235 Watts v 32 GB memory book - 294 Watts v 64 GB memory book - 320 Watts v Each PCI card - 20 Watts v DASD - 20 Watts Eserver pSeries 690 Service Guide...

  • Page 161: Service Inspection Guide

    Service Inspection Guide Perform a service inspection on the system when: v The system is inspected for a maintenance agreement. v Service is requested and service has not recently been performed. v An alterations and attachments review is performed. v Changes have been made to the equipment that may affect its safe operation. v External devices with their own power cables have those cables attached.
  • Page 162 3 Processor Subsystem 7 Bottom Filter Pull Tab 4 Top Filter Replacement To replace an air filter in the processor subsystem, slide the air filter into the slot. The filter is keyed to ensure correct orientation. Eserver pSeries 690 Service Guide...

  • Page 163: Chapter 2. Diagnostics Overview

    This MAP provides a systematic method of isolation to the failing item or items. Checkpoints Eserver pSeries 690 systems use various types of checkpoints, error codes, and SRNs that are referred to throughout this book (primarily in Chapters 3, 4 and 5).
  • Page 164 For a list of the checkpoints, see Chapter 4, “Checkpoints,” on page 371. Each entry provides a description of the event and the recommended action if the system fails to advance. SRNs are listed in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509. Eserver pSeries 690 Service Guide...

  • Page 165: Fru Isolation

    If the system is logically partitioned, the HMC must be attached. You can use the HMC to enable any FRU identify LED to be flashed. See the IBM Hardware Management Console for pSeries Installation and Operations Guide for instructions on activating and deactivating a FRU identify LED.

  • Page 166: Service Agent For The Eserver Pseries 690

    Service Agent for the Eserver pSeries 690 Service support for the Eserver pSeries 690 can be enhanced through the use of the application program known as service agent for the Eserver pSeries 690. This application provides a number of advantages for the Eserver pSeries 690 customer, including automatic error reporting and analysis without customer intervention.

  • Page 167: Chapter 3. Maintenance Analysis Procedures (Maps)

    Chapter 3. Maintenance Analysis Procedures (MAPs) This chapter contains Maintenance Analysis Procedures (MAPs) for the pSeries 690. Entry MAP When possible, run online diagnostics in service mode. Online diagnostics perform additional functions compared to standalone diagnostics. This ensures that the error state of the system that was captured in NVRAM is available for your use in fixing the problem.
  • Page 168 The system stops and a 4-digit number beginning with 0 or 2 is displayed in the operator panel display. pSeries Diagnostic Information for Multiple Bus Systems. All other symptoms. Go to “Quick Entry MAP” on page 153. Eserver pSeries 690 Service Guide...

  • Page 169: Quick Entry Map

    Quick Entry MAP The Quick Entry MAP is provided to help you quickly resolve a problem. Use the Quick Entry MAP when you know or have been provided with a symptom. Quick Entry MAP Table of Contents Problem Description Page No. Service actions The system attention LED on the media subsystem operator panel is on.

  • Page 170: Service Actions

    LEDs on the operator panel appear to behave normally. cable. 2. Replace the operator panel assembly, Location: U1.17-L1. Refer to “Operator Panel” on page 1019. 3. Replace the primary I/O book, Location: U1.18-P1-H2. Refer to “I/O Books and I/O Blanks” on page 870. Eserver pSeries 690 Service Guide...

  • Page 171: 8-Digit Error Codes

    Symptom Action You have a blank display on the operator panel. Other Go to “MAP 1520: Power” on page 194. LEDs on the operator panel are off. 8-Digit Error Codes You have an 8-digit error code displayed 1. Look up the error code in the table in “Checkpoints and Error Codes Index”...
  • Page 172 Navigation area of the HMC Management Environment, then the HMC or the connection to the managed system might be failing. 3. Go to the Entry MAP in the IBM Hardware Management Console for pSeries Maintenance Guide, order number SA38-0603. 4. If you cannot fix the problem using the HMC tests in...

  • Page 173: Power And Cooling Problems

    Symptom Action All display problems. 1. If using the Hardware Management Console, go to the IBM Hardware Management Console for pSeries Maintenance Guide, order number SA38-0603. 2. If using a graphics display: a. Go to the problem determination procedures for the display.
  • Page 174 The system does not respond to the password being 1. If the password is being entered from the Hardware entered or the system login prompt is displayed when Management Console (HMC), go to the IBM booting in service mode. Hardware Management Console for pSeries Maintenance Guide.
  • Page 175 Symptom Action The System Management Services menu is displayed. The device or media you are attempting to boot from may be faulty. 1. Check the SMS error log for any errors. To check the error log: v Choose error log v If an error is logged, check the time stamp.

  • Page 176: Map 1020: Problem Determination

    You can disable these actions while you diagnose and service the system. If the system was set up according to the recommendations of the Eserver pSeries 690 User’s Guide, all the settings of the service processor (except language) were saved by using the SAVE/RESTORE HARDWARE MAINTENANCE POLICIES service aid.
  • Page 177 Step 1020-1 The following steps analyze a failure to load the diagnostic programs. Note: Be prepared to answer questions regarding the operator panel display and to perform certain actions based on displayed POST indicators. 1. Run diagnostics on any partition. Find your symptom in the following table; then follow the instructions given in the Action column.
  • Page 178 Go to “Step 1020-4” on page 164. All other symptoms. If you were directed here from the Entry MAP, go to “MAP 1542: I/O Problem Isolation” on page 320. Otherwise, find the symptom in the “Entry MAP” on page 151. Eserver pSeries 690 Service Guide...
  • Page 179 Step 1020-2 There is a problem with the keyboard. Find the type of keyboard you are using in the following table; then follow the instructions given in the Action column. Keyboard Type Action Type 101 keyboard (U.S.). Identified by the size of the Record error code M0KB D001;...
  • Page 180 Look up the error in the Chapter 5, “Error Code to FRU Index,” on page 415 and do the listed action. e. If no recent error is logged in the error log, go to “MAP 1542: I/O Problem Isolation” on page 320. Eserver pSeries 690 Service Guide...

  • Page 181: Map 1230: Linux Platform Error Problem Resolution

    MAP 1230: Linux Platform Error Problem Resolution Purpose of This MAP Use this MAP to resolve problems reported by SRNs A00-000 to A1F-FFF from a partition running Linux. Step 1230-1 1. The last character of the SRN is bit-encoded as follows: Replace all FRUs listed Hot-swap is supported Software or Firmware could be the cause...
  • Page 182 Note: If necessary, refer to “Powering Off and Powering On the System” on page 854 for information on system shut down and powering the system on and off. 1. If the operating system is running, perform the operating system’s shutdown procedure. 2. Turn off power to the system. Eserver pSeries 690 Service Guide...
  • Page 183 3. Refer to the last character in the SRN. A 1, 3, 5, or 7 indicates that all FRUs listed on the Problem Report Screen need to be replaced. For SRNs ending with any other character, exchange one FRU at a time, in the order listed. Note: Use the appropriate procedure in Chapter 9, “Removal and Replacement Procedures,”...
  • Page 184 You may need to wait 30 minutes or longer before the error is written back to the HMC or platform error log. Was a problem reported? The repair is completed. Return the system to the customer. Go to “Step 1230-15” on page 169. Eserver pSeries 690 Service Guide...
  • Page 185 Step 1230-15 Is the problem the same as the original problem? The symptom has changed. Check for loose cards, cables, and obvious problems. If you do not find a problem, go to “MAP 1020: Problem Determination” on page 160 and get a new SRN. Go to “Step 1230-16.”...

  • Page 186: Map 1235: System Array Self-Repair Problem Resolution For Linux

    Go to MAP 0410: Repair Checkout, located in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509. 2. If a problem is reported use the SRN to resolve the problem. Go to “Entry MAP” on page 151 with the new symptom. Eserver pSeries 690 Service Guide...

  • Page 187: Map 1320: Service Focal Point

    MAP 1320: Service Focal Point These procedures define the steps to take when servicing a machine that is equipped with Service Focal Point (SFP). You might also be directed to these procedures if the system is running Linux as its only operating system.

  • Page 188: Map 1321: Quick Entry Map For Systems With Service Focal Point

    Are there any serviceable actions events with error codes of the form #xxxxxx in the list of error codes found in “Step 1321-5”? Go to “Step 1321-7” on page 173. Go to “Step 1321-18” on page 174. Eserver pSeries 690 Service Guide...
  • Page 189 Step 1321-7 Are there any serviceable events with FRU location codes reported in “Step 1321-5” on page 172? Go to “Step 1321-14” on page 174. Go to “Step 1321-8.” Step 1321-8 From the list of open service action events with FRUs reported, examine the details of each service action event and record the error code.
  • Page 190 “Entry MAP” on page 151 later in this MAP. Go to “Step 1321-7” on page 173. Go to ″MAP 0410: Repair Checkout″ in RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 191 Step 1321-22 Look for and record any additional error information or software messages on the operator panel or the console (serial TTY, Vterm, or HMC). Choose a running Linux partition (preferably the partition with the problem). Step 1321-23 Is Linux usable in any partition with Linux installed? Go to “Step 1321-30”...
  • Page 192 Sep 4 06:00:55 larry diagela: Supporting data: Sep 4 06:00:55 larry diagela: Ref. Code: 10111520 Sep 4 06:00:55 larry diagela: Location Codes: P1 P2 Sep 4 06:00:55 larry diagela: Sep 4 06:00:55 larry diagela: Analysis of /var/log/platform sequence number: 13 Eserver pSeries 690 Service Guide...
  • Page 193 4. Also use the following command to list RTAS messages recorded in the Linux system log: cat /var/log/platform |grep RTAS |more Linux RTAS error messages are logged in the platform file under /var/log. The following is an example of the Linux system error log RTAS messages. Aug 27 12:16:33 larry kernel: RTAS: 15 -------- RTAS event begin -------- Aug 27 12:16:33 larry kernel: RTAS 0: 04440040 000003f8 96008508 19155800 Aug 27 12:16:33 larry kernel: RTAS 1: 20030827 00000001 20000000 00000000...
  • Page 194 19. Ignore all other messages in the Linux system log. If the system is configured with more than one logical partition with Linux installed, repeat “Step 1321-24” on page 175 and “Step 1321-25”for all logical partitions that have Linux installed. Eserver pSeries 690 Service Guide...
  • Page 195 Step 1321-26 If you performed substep 3 of “Step 1321-24” on page 175 for the current Linux partition, go to “Step 1321-27,” and when asked in “Step 1321-27,” do not record any RTAS messages from “Step 1321-26” for the current Linux partition. Examine the Linux boot (IPL) log by logging in to the system as the root user and entering the following command: cat /var/log/boot.msg /var/log/dmesg 2>/dev/null | grep RTAS |more...
  • Page 196 If all recorded error codes have been processed and the problem has not been corrected, go to “Step 1321-31” on page 181. Eserver pSeries 690 Service Guide...
  • Page 197 Step 1321-31 If no additional error information is available and the problem has not been corrected, shut down the system. If an HMC is not attached, you need a laptop computer (and cable, part number 62H4857) capable of connecting to serial port 1 on the processor subsystem. Note: The Linux login prompt cannot be seen on a laptop computer connected to serial port 1.
  • Page 198 7. If the device adapter resides in the CEC, replace the I/O riser card, or the CEC backplane where the device adapter is located. 8. Call service support. Do not go to “Step 1321-34” on page 181. Eserver pSeries 690 Service Guide...
  • Page 199 Step 1321-38 Does the system appear to stop or hang before reaching the login prompt or did you record any problems with resources in “Step 1321-36” on page 182? Note: If the system console or VTERM window is always blank, choose NO. If you are sure the console or VTERM is operational and connected correctly, answer the question for this step.
  • Page 200 Go to the “Quick Entry MAP” on page 153 with each symptom you have recorded. Perform the indicated actions for all recorded symptoms, one at a time, until the problem has been corrected. If all recorded symptoms have been processed and the problem has not been corrected, call support. Eserver pSeries 690 Service Guide...

  • Page 201: Map 1322: End Of Call Map For Systems With Service Focal Point

    MAP 1322: End of Call MAP for Systems with Service Focal Point Note: If you are working on a system that not managed by an HMC go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems Step 1322-1 For future reference, record the SRC or symptom and the location code of the FRU you replaced.
  • Page 202 Go to “Step 1322-14.” Go to “Step 1322-15.” Step 1322-14 Step 1322-15 Add the partition list obtained in “Step 1322-11” to the existing list of “Axx” partitions obtained from processing previous service action events in this MAP. Eserver pSeries 690 Service Guide...
  • Page 203 Step 1322-16 Remove all entries in the list of all partition(s) you recorded in “Step 1322-11” on page 186. If you are referred to the list of partition(s) obtained in “Step 1322-11” on page 186 in future steps, the list is empty. Go to “Step 1322-17.”...
  • Page 204 Have all the serviceable events recorded in “Step 1322-4” on page 185 been processed? Go to “Step 1322-5” on page 185 and process the next service action event in the list of serviceable events recorded in “Step 1322-4” on page 185. Go to “Step 1322-34” on page 189. Eserver pSeries 690 Service Guide...
  • Page 205 Step 1322-34 While processing all service action events, were you directed to “Step 1322-14” on page 186? If the system attention LED is still on, use the HMC to turn off the LED as described in “Resetting the LED when a System is Attached To an HMC” on page 25. This completes the repair. Return the system to the customer.

  • Page 206: Map 1420: Recovery Procedures For Hot-Pluggable Pci Adapters

    Remove the faulty resource from the partition that will not boot. Record the slot location and the adapter type. Step 1421-4 Attempt to boot the partition. Does the partition boot? Go to “Step 1421-12” on page 191. Go to “Step 1421-5.” Step 1421-5 Shut down the partition. Eserver pSeries 690 Service Guide...
  • Page 207 Step 1421-6 Is the PCI slot power LED of the location recorded in “Step 1421-3” on page 190 on? Go to “Step 1421-7.” Go to “Step 1421-12.” Step 1421-7 Are there any empty PCI slots attached to the system that are not assigned to any partitions? Go to “Step 1421-12.”...
  • Page 208 Are there any empty PCI slots attached to the system that are not assigned to any partitions? Go to “Step 1422-14” on page 193. Go to “Step 1422-10.” Step 1422-10 Assign the available empty and unassigned slot to the partition that the faulty slot is assigned to. Eserver pSeries 690 Service Guide...
  • Page 209 Step 1422-11 Insert a new adapter of the same type recorded in “Step 1422-1” on page 191 into the slot assigned in “Step 1422-10” on page 192. Step 1422-12 Move any external cabling from the adapter in the slot recorded in “Step 1422-1” on page 191 to the adapter in the slot assigned in “Step 1422-10”...

  • Page 210: Map 1520: Power

    CAUTION: Energy hazard, remove power before servicing. Attention: To identify a FRU, these MAPs refer to FRU Identify LEDs. Information about the FRU Identify LEDs can be found in “FRU Identify LEDs” on page 68. Eserver pSeries 690 Service Guide...
  • Page 211 Find the symptom in the following table; then follow the instructions given in the Action column. Power Problems Symptom/Reference Code Action The system will not power on and no error codes are Go to “MAP 1521: The System Will Not Power On And available No Error Codes Are Available”...
  • Page 212 (BPA) Communication Failure” on page 214. 101A F806 or 101A F906 for BPC A Go to “MAP 152a: Loss of ac Power or Phase Missing” on page 216. 101B F806 or 101B F906 for BPC B Eserver pSeries 690 Service Guide...
  • Page 213 Power Problems Symptom/Reference Code Action 1014 xx15, 1014 xx25, 1015 xx15, 1015 xx25, Go to “MAP 152m: Cable Problem in Power Subsystem” 1016 xx15, 1016 xx25, 1017 xx15, 1017 xx25, on page 302. 101C xx15, 101C xx25, 101C xx35, 101C xx45, 101C xx55, 101C xx75, 101C xx85, 101C xx95, 101C xxA5, 101A x115, 101A x125, 101A x135, 101A x215,...

  • Page 214: Map 1521: The System Will Not Power On And No Error Codes Are Available

    UEPO PWR LED turned on v BPC GOOD LED turned on v All other LEDs are off Are all of the above true? Go to “Step 1521-4” on page 199. Go to “Step 1521-5” on page 199. Eserver pSeries 690 Service Guide...
  • Page 215 Step 1521-4 Independent faults are indicated on both sides of the BPA. Each side must be isolated separately. Call for support. This ends the procedure. Step 1521-5 Check the External (Room) EPO Connection if used. If a room emergency power off (EPO) circuit is used, the external room EPO circuit is connected to the J02 connector on the lower edge of the UEPO Switch.
  • Page 216 Inform the customer that the line voltage into the BPA is missing or too low. This ends the procedure. Independent faults are indicated on both sides of the BPA. Each side must be isolated separately. Call for support. This ends the procedure. Eserver pSeries 690 Service Guide...

  • Page 217: Map 1522: Uepo Switch On The Bpc Is In The Bypass Position

    MAP 1522: UEPO Switch On The BPC Is In The Bypass Position Step 1522-1 Check the UEPO Switch on the BPC on the BPA that is exhibiting the failure. Is the switch in the NORMAL position? Set UEPO switch on the BPC to the NORMAL position and go to “Step 1522-2.” Go to “Step 1522-2.”...

  • Page 218: Map 1523: There Is A Bulk Power Regulator (Bpr) Communications Fault

    After each FRU exchanged, is the error code that sent you to this MAP still reported? Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. This ends the procedure. Replace the next FRU on the list. Eserver pSeries 690 Service Guide...

  • Page 219: Map 1524: An Open Room Epo Switch Has Been Detected From One Side

    MAP 1524: An Open Room EPO Switch Has Been Detected From One Side Step 1524-1 Check the unit emergency power off (UEPO) panel. Is a customer room EPO cable plugged into the UEPO panel? Go to “Step 1524-3” on page 204. Go to “Step 1524-2”...
  • Page 220 The problem has been corrected. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Perform the next action on the list. If all actions on the list have been performed, call for support. Eserver pSeries 690 Service Guide...

  • Page 221: Map 1525: There Is A 350 Volt Bulk Failure

    MAP 1525: There Is a 350 Volt Bulk Failure Step 1525-1 Note: Read the Danger and Caution notices under “Safety Notices” on page vii before continuing with this procedure. 1. Prepare a multimeter to measure up to 600 V ac. 2.
  • Page 222 “Step 1525-1” on page 205. Replace the BPR that is currently unplugged. Follow all steps in the removal and replacement procedures for “Bulk Power Regulator (BPR)” on page 860. Go to “Step 1525-6” on page 207. Eserver pSeries 690 Service Guide...
  • Page 223 Step 1525-5 Note: Be sure you are working on the side of the BPA (A or B) referenced by the error code that sent you to this MAP. FRUs on the operating side of the BPA (with BPC GOOD LED on) must not be disturbed during this procedure.

  • Page 224: Map 1526: There Is An Integrated Battery Feature (Ibf) Failure

    Is the cable plugged on both sides? Plug in the cable and go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 1526-4” on page 209. Eserver pSeries 690 Service Guide...
  • Page 225 Step 1526-4 Check the circuit breaker on the IBF referenced in the error code that brought you to this MAP. The IBF LED on the IBF referenced in the error code that brought you to this MAP will be off. Is the circuit breaker set on? Replace the IBF referenced in the error code that brought you to this MAP.
  • Page 226 Is the error code that sent you to this MAP still reported? The problem has been corrected. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Call for support. Eserver pSeries 690 Service Guide...

  • Page 227: Map 1527: An Airflow Loss Has Been Detected

    MAP 1527: An Airflow Loss Has Been Detected Step 1527-1 Check the following air inlets and outlets for blockage or obstruction: v Front and rear frame door openings (except for acoustical foam) v Bulk power assembly (BPA) cage – Inlet opening in left side of front BPA, BPA A –...
  • Page 228 Step 1527-5 Call your next level of support. Eserver pSeries 690 Service Guide...

  • Page 229: Map 1528: There Is A Processor (Critical/Warning) Overtemperature Fault

    MAP 1528: There Is A Processor (Critical/Warning) Overtemperature Fault Step 1528-1 Is the room ambient temperature in normal range (less than 35 degrees C/ 95 degrees F)? Notify the customer. The customer must bring the room temperature within normal range. Go to ″MAP 0410: Repair Checkout″...

  • Page 230: Map 1529: There Is A Bulk Power Assembly (Bpa) Communication Failure

    The problem has been corrected. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems Replace the next FRU on the list. If all FRUs on the list have been replaced, call for support. Eserver pSeries 690 Service Guide...
  • Page 231 Step 1529-3 Inform the customer that the line voltage into the BPA is missing or too low, and needs to be checked. Can the line voltage be checked now? Defer this repair until the customer’s utility can check the line voltage. This ends the procedure. Go to “Step 1529-4.”...

  • Page 232: Map 152A: Loss Of Ac Power Or Phase Missing

    “Bulk Power Controller (BPC)” on page 861. 5. BPE on the side referenced by the error code that sent you to this MAP. Follow all steps in the removal and replacement procedures for “Bulk Power Enclosure (BPE)” on page 865. Eserver pSeries 690 Service Guide...
  • Page 233 After each FRU is exchanged, is the error code that sent you to this MAP still reported? The problem has been corrected. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Replace the next FRU on the list.

  • Page 234: Map 152B: 2.5 V Current/Voltage Problem In Processor Subsystem

    2. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152b-8 Reinsert one of the books that is pulled out and listed in step 152b-4. Step 152b-9 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 235 Step 152b-10 Did the system stop with the same error code as recorded in “Step 152b-1” on page 218? The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 236 2. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152b-18 Reinsert one of the books that is pulled out and listed in step “Step 152b-14” on page 219. Eserver pSeries 690 Service Guide...
  • Page 237 Step 152b-19 Turn on the power. Step 152b-20 Did the system stop with the same error code as recorded in “Step 152b-1” on page 218? The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 238 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152b-33 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152b-34” on page 223. Call for support. Eserver pSeries 690 Service Guide...
  • Page 239 Step 152b-34 Replace the books in the following list, if present, one at a time and in the order listed: v Primary I/O Book, at location U1.18-P1-H2 v DCA 1-RH, at location U1.18-P1-V1 v DCA 2-RH, at location U1.18-P1-V2 v DCA 3-RH, at location U1.18-P1-V4 v DCA 4-RH, at location U1.18-P1-V5 v DCA 5-RH, at location U1.18-P1-V6 v DCA 6-RH, at location U1.18-P1-V8...
  • Page 240 Step 152b-45 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152b-46 Has the system backplane been replaced? Call for support. Go to “Step 152b-42.” Eserver pSeries 690 Service Guide...

  • Page 241: Map 152C: 1.8 V Current/Voltage Problem In Processor Subsystem

    MAP 152c: 1.8 V Current/Voltage Problem in Processor Subsystem Step 152c-1 For future reference, record the error code in the operator panel display. Step 152c-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152c-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152c-4.”...
  • Page 242 Go to “Step 152c-22” on page 227. Go to “Step 152c-17.” Step 152c-17 One of the books just removed is defective. 1. Turn off the power. 2. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Eserver pSeries 690 Service Guide...
  • Page 243 Step 152c-18 Reinsert one of the books that is pulled out and listed in “Step 152c-14” on page 226. Step 152c-19 Turn on the power. Step 152c-20 Did the system stop with the same error code as recorded in “Step 152c-1” on page 225? The book just reinserted is defective.
  • Page 244 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152c-28.” Step 152c-32 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Eserver pSeries 690 Service Guide...
  • Page 245 Step 152c-33 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152c-34.” Call for support. Step 152c-34 Replace the books in the following list, if present, one at a time and in the order listed: v Primary I/O book, at location U1.18-P1-H2 v DCA 1-RH, at location U1.18-P1-V1 v DCA 2-RH, at location U1.18-P1-V2...
  • Page 246 One of the modules just removed is defective. Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152c-46 Reinstall one of the modules that is removed and listed in “Step 152c-42.” Eserver pSeries 690 Service Guide...
  • Page 247 Step 152c-47 Turn on the power. Step 152c-48 Did the system stop with the same error code as recorded in “Step 152c-1” on page 225? The module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 248 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152c-56 Has the system backplane been replaced? Call for support. Go to “Step 152c-52” on page 231. Eserver pSeries 690 Service Guide...

  • Page 249: Map 152D: 1.5 V Auxiliary Current/Voltage Problem In Processor Subsystem

    MAP 152d: 1.5 V Auxiliary Current/Voltage Problem in Processor Subsystem Step 152d-1 Record the error code and the location code(s) that sent you to this MAP. Step 152d-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152d-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152d-4.”...
  • Page 250 Pull out the following books about 25 mm (1 inch), if present: v Memory book 4, at location U1.18-P1-M4 v Memory book 5, at location U1.18-P1-M8 v Memory book 6, at location U1.18-P1-M5 v Memory book 7, at location U1.18-P1-M1 Eserver pSeries 690 Service Guide...
  • Page 251 Step 152d-15 Turn on the power. Step 152d-16 Did the system stop with the same error code as recorded in “Step 152d-1” on page 233? Go to “Step 152d-22” on page 236. Go to “Step 152d-17.” Step 152d-17 One of the books just removed is defective. Turn off the power.
  • Page 252 Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152d-28 Reinsert one of the books that is pulled out and listed in “Step 152d-24.” Step 152d-29 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 253 Step 152d-30 Did the system stop with the same error code as recorded in “Step 152d-1” on page 233? The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 254 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152d-41 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152d-42” on page 239. Call for support. Eserver pSeries 690 Service Guide...
  • Page 255 Step 152d-42 Record the location of each installed L3 module. Attention: L3 modules have a limit of three plug cycles. Before removing any of the L3 modules in the following list, call for support. Remove all of the following modules if present: v L3 module, at location U1.18-P1-C5 v L3 module, at location U1.18-P1-C6 v L3 module, at location U1.18-P1-C7...
  • Page 256 Go to “Step 152d-55” on page 241. The system backplane was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 257 Step 152d-55 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152d-56 Has the system backplane been replaced? Call for support. Go to “Step 152d-52” on page 240. Chapter 3. Maintenance Analysis Procedures...

  • Page 258: Map 152E: 1.5 V Cpu Current/Voltage Problem In Processor Subsystem

    Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152e-8 Reinsert one of the books that is pulled out and listed in “Step 152e-4.” Step 152e-9 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 259 Step 152e-10 Did the system stop with the same error code as recorded in “Step 152e-1” on page 242? The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 260 Record the original location on each MCM. Remove the following MCM modules, if present: v MCM module 0, at location U1.18-P1-C1 v MCM module 3, at location U1.18-P1-C2 v MCM module 1, at location U1.18-P1-C3 v MCM module 2, at location U1.18-P1-C4 Eserver pSeries 690 Service Guide...
  • Page 261 Step 152e-23 Turn on the power. Step 152e-24 Did the system stop with the same error code as recorded in “Step 152e-1” on page 242? Go to “Step 152e-30” on page 246. Go to “Step 152e-25.” Step 152e-25 One of the modules just removed is defective. Turn off the power.
  • Page 262 Step 152e-35 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152e-36 Has the system backplane been replaced? Call for support. Go to “Step 152e-32.” Eserver pSeries 690 Service Guide...

  • Page 263: Map 152F: 3.3 V Current/Voltage Problem In Processor Subsystem

    MAP 152f: 3.3 V Current/Voltage Problem in Processor Subsystem Step 152f-1 Record the error code and the location code(s) that sent you to this MAP. Step 152f-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152f-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152f-4.”...
  • Page 264 Pull out the following books about 25 mm (1 inch), if present: v Memory book 4, at location U1.18-P1-M4 v Memory book 5, at location U1.18-P1-M8 v Memory book 6, at location U1.18-P1-M5 v Memory book 7, at location U1.18-P1-M1 Step 152f-15 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 265 Step 152f-16 Did the system stop with the same error code as recorded in “Step 152f-1” on page 247? Go to “Step 152f-22.” Go to “Step 152f-17.” Step 152f-17 One of the books just removed is defective. Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off.
  • Page 266 The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152f-31” on page 251. Eserver pSeries 690 Service Guide...
  • Page 267 Step 152f-31 Have all the books listed in “Step 152f-24” on page 250 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 268 The system clock card is defective. Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152f-46 Reinstall the system clock card that you removed in “Step 152f-42.” Eserver pSeries 690 Service Guide...
  • Page 269 Step 152f-47 Turn on the power. Step 152f-48 Did the system stop with the same error code as recorded in “Step 152f-1” on page 247? The system clock card just reinserted is defective, replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 270 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152f-56 Has the system backplane been replaced? Call for support. Go to “Step 152f-52” on page 253. Eserver pSeries 690 Service Guide...

  • Page 271: Map 152G: 5.0 V Current/Voltage Problem In Processor Subsystem

    MAP 152g: 5.0 V Current/Voltage Problem in Processor Subsystem Step 152g-1 For future reference, record the error code and the location code(s) that sent you to this MAP. Step 152g-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152g-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152g-4.”...
  • Page 272 Pull out the following books about 25 mm (1 inch), if present: v Memory book 4, at location U1.18-P1-M4 v Memory book 5, at location U1.18-P1-M8 v Memory book 6, at location U1.18-P1-M5 v Memory book 7, at location U1.18-P1-M1 Step 152g-15 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 273 Step 152g-16 Did the system stop with the same error code as recorded in “Step 152g-1” on page 255? Go to “Step 152g-22.” Go to “Step 152g-17.” Step 152g-17 One of the books just removed is defective. Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off.
  • Page 274 The book just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152g-31” on page 259. Eserver pSeries 690 Service Guide...
  • Page 275 Step 152g-31 Have all the books listed in “Step 152g-24” on page 258 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 276 Step 152g-45 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 152g-46 Has the system backplane been replaced? Call for support. Go to “Step 152g-42.” Eserver pSeries 690 Service Guide...

  • Page 277: Map 152H: 3.3V Current/Voltage Problem In I/O Subsystem

    MAP 152h: 3.3V Current/Voltage Problem in I/O Subsystem Step 152h-1 Record the error code and the location code(s) that sent you to this MAP. Step 152h-2 Determine the I/O subsystem number from the error code (10yy xxxx) and the following list. The remaining steps of this map refer to this I/O subsystem: v If yy=14, I/O subsystem number is 1, location is U1.9 v If yy=15, I/O subsystem number is 2, location is U1.5...
  • Page 278 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152h-14 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152h-15” on page 263. Call for support. Eserver pSeries 690 Service Guide...
  • Page 279 Step 152h-15 Remove the following adapter cards, if present, from the I/O subsystem. record the adapter locations: v Adapter card at P1-I6 v Adapter card at P1-I7 v Adapter card at P1-I8 v Adapter card at P1-I9 v Adapter card at P1-I10 Step 152h-16 Turn on the power.
  • Page 280 Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152h-29 Reinsert one of the cards that is removed and listed in “Step 152h-25.” Eserver pSeries 690 Service Guide...
  • Page 281 Step 152h-30 Turn on the power. Step 152h-31 Did the system stop with the same error code as recorded in “Step 152h-1” on page 261? The card just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 282 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152h-39.” Step 152h-43 Turn off the power. Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Eserver pSeries 690 Service Guide...
  • Page 283 Step 152h-44 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152h-45.” Call for support. Step 152h-45 Replace the DCAs in the following list, one at a time and in the order listed: v DCA 1 at V1 v DCA 2 at V2 Step 152h-46...
  • Page 284 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152h-57 Have all the cards listed in “Step 152h-53” been replaced with new or original cards? Call for support. Go to “Step 152h-53.” Eserver pSeries 690 Service Guide...

  • Page 285: Map 152I: 5.0 V Current/Voltage Problem In I/O Subsystem

    MAP 152i: 5.0 V Current/Voltage Problem in I/O Subsystem Step 152i-1 Record the error code and location code(s) that sent you to this MAP. Step 152i-2 Determine the I/O subsystem number from the error code (10yy xxxx) and the following list. The remaining steps of this map refer to this I/O subsystem: v If yy=14, I/O subsystem number is 1, location is U1.9 v If yy=15, I/O subsystem number is 2, location is U1.5...
  • Page 286 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152i-14 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152i-15” on page 271. Call for support. Eserver pSeries 690 Service Guide...
  • Page 287 Step 152i-15 Remove the following adapter cards, if present, from the I/O subsystem. Record the adapter locations: v Adapter card at P1-I6 v Adapter card at P1-I7 v Adapter card at P1-I8 v Adapter card at P1-I9 v Adapter card at P1-I10 Step 152i-16 Turn on the power.
  • Page 288 Turn on the power. Step 152i-27 Did the system stop with the same error code as recorded in “Step 152i-1” on page 269? Go to “Step 152i-33” on page 273. Go to “Step 152i-28” on page 273. Eserver pSeries 690 Service Guide...
  • Page 289 Step 152i-28 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152i-29 Reinsert one of the cards that is removed and listed in “Step 152i-25” on page 272. Step 152i-30 Turn on the power.
  • Page 290 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152i-39.” Step 152i-43 Turn off the power. Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Eserver pSeries 690 Service Guide...
  • Page 291 Step 152i-44 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152i-45.” Call for support. Step 152i-45 Remove the following DASD 4-packs, if present, from the I/O subsystem. Record the DASD locations: v DASD 4-pack at P3 v DASD 4-pack at P4 v DASD 4-pack at P5...
  • Page 292 Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152i-59 Remove the new card that was just installed in “Step 152i-55” and reinstall the original card. Eserver pSeries 690 Service Guide...
  • Page 293 Step 152i-60 Have all the cards listed in “Step 152i-55” on page 276 been replaced with new or original cards? Go to “Step 152i-61.” Go to “Step 152i-55” on page 276. Step 152i-61 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152i-62 Are all the green ″power good out″...

  • Page 294: Map 152J: 2.5 V Current/Voltage Problem In I/O Subsystem

    Step 152j-6 Turn on the power. Step 152j-7 Did the system stop with the same error code as recorded in “Step 152j-1”? Go to “Step 152j-13” on page 279. Go to “Step 152j-8” on page 279. Eserver pSeries 690 Service Guide...
  • Page 295 Step 152j-8 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152j-9 Reinsert one of the cards that is removed and listed in “Step 152j-5” on page 278. Step 152j-10 Turn on the power.
  • Page 296 The card just reinserted is defective. Replace it.This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152j-22” on page 281. Eserver pSeries 690 Service Guide...
  • Page 297 Step 152j-22 Have all the cards listed in “Step 152j-15” on page 280 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 298 Remove the following adapter cards, if present, from the I/O subsystem. Record the adapter locations: v Adapter card at P2-I6 v Adapter card at P2-I7 v Adapter card at P2-I8 v Adapter card at P2-I9 v Adapter card at P2-I10 Step 152j-36 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 299 Step 152j-37 Did the system stop with the same error code as recorded in “Step 152j-1” on page 278? Go to “Step 152j-43.” Go to “Step 152j-38.” Step 152j-38 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″...
  • Page 300 Have all the cards listed in “Step 152j-45” been replaced with new or original cards? Go to “Step 152j-51” Go to “Step 152j-45.” Step 152j-51 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Eserver pSeries 690 Service Guide...
  • Page 301 Step 152j-52 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152j-53.” Call for support. Step 152j-53 Replace the parts in the following list one at a time and in the order listed: v I/O subsystem backplane at P1 v I/O subsystem backplane at P2 Step 152j-54...

  • Page 302: Map 152K: 12.0 V Current/Voltage Problem In I/O Subsystem

    Step 152k-6 Turn on the power. Step 152k-7 Did the system stop with the same error code as recorded in “Step 152k-1”? Go to “Step 152k-13” on page 287. Go to “Step 152k-8” on page 287. Eserver pSeries 690 Service Guide...
  • Page 303 Step 152k-8 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152k-9 Reinsert one of the cards that is removed and listed in “Step 152k-5” on page 286. Step 152k-10 Turn on the power.
  • Page 304 The card just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152k-22” on page 289. Eserver pSeries 690 Service Guide...
  • Page 305 Step 152k-22 Have all the cards listed in “Step 152k-15” on page 288 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 306 Turn on the power. Step 152k-37 Did the system stop with the same error code as recorded in “Step 152k-1” on page 286? Go to “Step 152k-43” on page 291. Go to “Step 152k-38” on page 291. Eserver pSeries 690 Service Guide...
  • Page 307 Step 152k-38 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152k-39 Reinsert one of the cards that is removed and listed in “Step 152k-35” on page 290. Step 152k-40 Turn on the power.
  • Page 308 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152k-49.” Step 152k-53 Turn off the power. Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Eserver pSeries 690 Service Guide...
  • Page 309 Step 152k-54 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152k-55.” Call for support. Step 152k-55 Replace the books in the following list one at a time and in the order listed: v DCA 1 at V1 v DCA 2 at V2 Step 152k-56...
  • Page 310 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152k-67 Have all the cards listed in “Step 152k-63” been replaced? Call for support. Go to “Step 152k-63.” Eserver pSeries 690 Service Guide...

  • Page 311: Map 152L: -12.0V Current/Voltage Problem In I/O Subsystem

    MAP 152l: -12.0V Current/Voltage Problem in I/O Subsystem Step 152l-1 Record the error code and location code(s) that sent you to this MAP. Step 152l-2 Determine the I/O subsystem number from the error code (10yy xxxx) and the following list. The remaining steps of this map refer to this I/O subsystem: v If yy=14, I/O subsystem number is 1, location is U1.9 v If yy=15, I/O subsystem number is 2, location is U1.5...
  • Page 312 Remove the following adapter cards, if present, from the I/O subsystem. Record the adapter locations: v Adapter card at P1-I6 v Adapter card at P1-I7 v Adapter card at P1-I8 v Adapter card at P1-I9 v Adapter card at P1-I10 Eserver pSeries 690 Service Guide...
  • Page 313 Step 152l-16 Turn on the power. Step 152l-17 Did the system stop with the same error code as recorded in “Step 152l-1” on page 295? Go to “Step 152l-23.” Go to “Step 152l-18.” Step 152l-18 One of the cards just removed is defective. Turn off the power.
  • Page 314 The card just reinserted is defective. Replace it. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152l-32” on page 299. Eserver pSeries 690 Service Guide...
  • Page 315 Step 152l-32 Have all the cards listed in “Step 152l-25” on page 298 been reinserted? The symptom has changed. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 316 The DCA just replaced is defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 317 Step 152l-48 Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152l-49 Remove the new DCA that was just installed in “Step 152l-45” on page 300 and reinstall the original DCA. Step 152l-50 Have all the DCAs listed in “Step 152l-45”...

  • Page 318: Map 152M: Cable Problem In Power Subsystem

    Examine both ends of the power cable or cables, and make sure each end is properly connected and fully seated. Step 152m-5 Is the power cable or cables properly connected and seated fully at both ends? Go to “Step 152m-30” on page 305. Go to “Step 152m-29” on page 305. Eserver pSeries 690 Service Guide...
  • Page 319 Step 152m-6 Have you replaced the first FRU in the list of FRUs recorded in “Step 152m-1” on page 302 in a previous service action? Go to “Step 152m-18” on page 304. Go to “Step 152m-7.” Step 152m-7 Is the power-on LED of the first FRU generated from the location codes recorded in “Step 152m-1” on page 302 off? Go to “Step 152m-8.”...
  • Page 320 Step 152m-24 Turn off the power. Turn off the UEPO switch. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Also examine the green ″power good out″ LEDs of all installed I/O subsystem DCAs. Eserver pSeries 690 Service Guide...
  • Page 321 Step 152m-25 Are all amber logic-power LEDs of all installed processor subsystem DCAs and all green ″logic power out″ LEDs of all installed I/O subsystem DCAs off? Go to “Step 152m-26.” Call for support. Step 152m-26 Replace the third FRU in the list of FRUs recorded in step 152m-1. Step 152m-27 Turn on the UEPO switch.

  • Page 322: Map 152N: Dasd Subsystem Power Problem

    Turn off the power. Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152n-5 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152n-6” on page 307. Call for support. Eserver pSeries 690 Service Guide...
  • Page 323 Step 152n-6 Are there any DASD in positions A8, A9, Aa, or Ab of the DASD backplane found in “Step 152n-2” on page 306 and “Step 152n-3” on page 306? Go to “Step 152n-7.” Go to “Step 152n-15” on page 308. Step 152n-7 Record the DASD positions in slots A8, A9, Aa, or Ab, then remove any DASD in slots A8, A9, Aa, or Ab.
  • Page 324 Step 152n-22 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to Step “Step 152n-23.” Call for support. Step 152n-23 Replace the DASD backplane. Step 152n-24 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 325 Step 152n-25 Did the system stop with the same error code as recorded in “Step 152m-1” on page 302? Call for support. The book just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.

  • Page 326: Map 1540: Problem Isolation Procedures

    Attention: Before you remove or replace any MCM or L3 module, stop, read and understand the following procedures: “MCM Module (Processor) and Pass Through Modules” on page 879 and “L3 Cache Modules” on page 898. Eserver pSeries 690 Service Guide...
  • Page 327 Problem Isolation Procedures Symptom/Reference Code/Checkpoint Action 406x 0C09 Go to “MAP 1546: Memory Book Problem Isolation” on page 347. 406x 0C0A Go to “MAP 1547: I/O Book Problem Isolation” on page 350. 406x 0001, 406x 0002, 406x 000A, 406x 000B, Go to “MAP 154A: I2C Bus Problem Isolation”...

  • Page 328: Map 1541: Jtag Problem Isolation

    L3 module at U1.18-P1-C18 v L3 module at U1.18-P1-C19 v L3 module at U1.18-P1-C8 v MCM module 0 at U1.18-P1-C1 v MCM module 3 at U1.18-P1-C2 v MCM module 1 at U1.18-P1-C3 v MCM module 2 at U1.18-P1-C4 Eserver pSeries 690 Service Guide...
  • Page 329 Step 1541-3 Is (are) the location code(s) recorded in “Step 1541-1” on page 312 also listed in “Step 1541-2” on page 312? Go to “Step 1541-19” on page 315. Go to “Step 1541-4.” Step 1541-4 Check the following list to find the location code(s) recorded in “Step 1541-1” on page 312: v Fourth I/O book, at location U1.18-P1-H1 v Primary I/O Book at U1.18-P1-H2 v Secondary I/O Book at U1.18-P1-H3...
  • Page 330 Are all the amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1541-16.” Call for support. Step 1541-16 Replace the primary I/O book at U1.18-P1-H2. Step 1541-17 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 331 Step 1541-18 Did the system stop with the same error code as recorded in “Step 1541-1” on page 312? Go to “Step 1541-37” on page 318. The part just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 332 Memory Book 6 at U1.18-P1-M5 if not recorded in “Step 1541-1” on page 312. v Memory Book 7 at U1.18-P1-M1 if not recorded in “Step 1541-1” on page 312. Step 1541-28 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 333 Step 1541-29 Did the system stop with the same error code as recorded in “Step 1541-1” on page 312? Go to “Step 1541-30.” The book just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 334 The book just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 335 Step 1541-43 Turn off the power. Make sure the amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 1541-44 Call for support. This ends the procedure. Chapter 3. Maintenance Analysis Procedures...

  • Page 336: Map 1542: I/O Problem Isolation

    (5 key between the Keyboard and Speaker indicators). Therefore, on a partitioned system, make sure the partition you selected to boot in the following procedure has the CD-ROM allocated to it, as described in Chapter 6, “Using the Online and Standalone Diagnostics,” on page 773. Eserver pSeries 690 Service Guide...
  • Page 337 Step 1542-1 1. Ensure that the diagnostics and the operating system are shut down. 2. Turn off the power. 3. Select slow boot mode (select Disable Fast Boot) on the System Power Control menu from the service processor main menu. 4.
  • Page 338 The boot attempts that follow will attempt to isolate any remaining I/O subsystem problems with missing devices. Ignore any codes that may display on the operator panel unless stated otherwise. Go to “Step 1542-5” on page 323. Eserver pSeries 690 Service Guide...
  • Page 339 Step 1542-5 There are missing devices associated with one or more I/O subsystems. Note: Before continuing, check the cabling from the processor subsystem to I/O subsystem(s) to ensure that the system is cabled correctly. Refer to “Subsystem Positioning and Cabling” on page 39 for valid configurations.
  • Page 340 Step 1542-6 The Eserver pSeries 690 server must have a minimum of one I/O subsystem and one media subsystem attached to the processor subsystem. The following steps reduce the system I/O to the required minimum of one I/O subsystem: 1. Turn off the system power.
  • Page 341 Step 1542-7 I/O subsystem 1 (U1.9) is the only I/O subsystem connected to the processor subsystem. 1. Turn on the power to boot standalone diagnostics from CD. 2. If the Please define the System Console screen is displayed, follow directions to select the system console.
  • Page 342 9. Check that all attached devices and adapters are listed. Did the Please define the System Console screen display and are all attached devices and adapters listed? Go to “Step 1542-10.” Go to “Step 1542-17” on page 328. Eserver pSeries 690 Service Guide...
  • Page 343 Step 1542-14 1. If it is not already off, turn off the power. 2. Remove all adapters from slots 6, 7, 8, 9 and 10 (location codes Ux.y-P1-I6 through I10) from the left side of the I/O subsystem that are not attached to the boot device. 3.
  • Page 344 After installing all of the adapters and the Please define the System Console screen does display and all attached devices and adapters are listed, return the system to its original configuration. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 345 Step 1542-18 Replace the adapter you just installed with a new adapter and try to boot standalone diagnostics from CD again. 1. If the Please define the System Console screen is displayed, follow directions to select the system console. 2. Use the Display Configuration and Resource List to list all attached devices and adapters (refer to the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509, if necessary).
  • Page 346 Please define the System Console screen does not display or all attached devices and adapters are not listed, check any external devices and cabling. If you do not find a problem, contact your next level of support for assistance. Go to “Step 1542-20” on page 331. Eserver pSeries 690 Service Guide...
  • Page 347 Step 1542-20 1. Turn off the power. 2. The part just replaced fixed the problem. 3. If a display adapter with keyboard, and mouse were used, reinstall the display adapter card, keyboard and mouse. 4. Reconnect the diskette drive cable to the diskette drive connector on the media subsystem. 5.
  • Page 348 RIO port B1 on primary I/O book (U1.18-P1-H2/Q4). Reconfigure the system to its original condition. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 349 Step 1542-24 1. Turn off the power. 2. Slide the secondary I/O book (U1.18-P1-H3) all the way into the processor backplane until it is firmly seated and latched. 3. At the secondary I/O book, disconnect the cable connection at RIO port A0 (U1.18-P1-H3/Q4). 4.
  • Page 350 RIO cable from I/O subsystem 4 right I/O port connector 1 (Ux.y-P2/Q1) to processor subsystem RIO port D1 on secondary I/O book (U1.18-P1-H3/Q5). Reconfigure the system to its original condition. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 351 Step 1542-26 1. Turn off the power. 2. At the secondary I/O book disconnect the cable connection at RIO port A0 (U1.18-P1-H3/Q4). 3. Disconnect the cable connection at I/O subsystem 5 left I/O port connector 0 (U2.1-P1/Q2).The RIO cable that was connected to RIO port A0 should now be loose and can be removed. 4.
  • Page 352 RIO cable from I/O subsystem 6 right I/O port connector 1 (U2.5-P2/Q1) to processor subsystem RIO port B1 on secondary I/O book (U1.18-P1-H3/Q1). Reconfigure the system to its original condition. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 353 Step 1542-28 1. Turn off the power. 2. Slide the secondary I/O book (U1.18-P1-H4) all the way into the processor backplane until it is firmly seated and latched. 3. At the secondary I/O book, disconnect the cable connection at RIO port D0 (U1.18-P1-H4/Q6). 4.
  • Page 354 Information for Multiple Bus Systems. Step 1542-30 This ends the procedure. Reconfigure the system to its original condition. Go to “MAP 0410: Repair Checkout” in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...

  • Page 355: Map 1543: Mcm Module Problem Isolation

    MAP 1543: MCM Module Problem Isolation Step 1543-1 Record the error code and the location code(s) that sent you to this MAP. Step 1543-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1543-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1543-4.”...
  • Page 356 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 1543-14 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Eserver pSeries 690 Service Guide...
  • Page 357 Step 1543-15 Call for support. This ends the procedure. Chapter 3. Maintenance Analysis Procedures...

  • Page 358: Map 1544: Inner L3 Module Problem Isolation

    The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Eserver pSeries 690 Service Guide...
  • Page 359 Step 1544-7 Have all the books or modules listed in “Step 1544-4” on page 342 been replaced? Go to “Step 1544-8.” Go to “Step 1544-2” on page 342. Step 1544-8 Turn off the power. Step 1544-9 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1544-10 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1544-11.”...

  • Page 360: Map 1545: Outer L3 Module Problem Isolation

    1. First location code item recorded, if any, in “Step 1545-1.” 2. Second location code item recorded, if any, in “Step 1545-1.” 3. Third location code item recorded, if any, in “Step 1545-1.” Step 1545-5 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 361 Step 1545-6 Did the system stop with the same error code as recorded in “Step 1545-1” on page 344? Go to “Step 1545-7.” The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 362 Step 1545-15 Call for support. This ends the procedure. Eserver pSeries 690 Service Guide...

  • Page 363: Map 1546: Memory Book Problem Isolation

    MAP 1546: Memory Book Problem Isolation Step 1546-1 Record the error code and the location code(s) that sent you to this MAP. Step 1546-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1546-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1546-4.”...
  • Page 364 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 1546-14 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Eserver pSeries 690 Service Guide...
  • Page 365 Step 1546-15 Call for support. This ends the procedure. Chapter 3. Maintenance Analysis Procedures...

  • Page 366: Map 1547: I/O Book Problem Isolation

    Go to “Step 1547-2.” Step 1547-8 Turn off the power. Step 1547-9 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1547-10 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Eserver pSeries 690 Service Guide...
  • Page 367 Go to “Step 1547-11.” Call for support. Step 1547-11 Attention: Before replacing the system backplane, call for support. Replace the system backplane at U1.18-P1. Step 1547-12 Turn on the power. Step 1547-13 Did the system stop with the same error code as recorded in “Step 1547-1” on page 350? Go to “Step 1547-14.”...

  • Page 368: Map 1548: Memory And Processor Problem Isolation

    L3 module at U1.18-P1-C20 if not recorded in “Step 1548-1.” v MCM module 2 at U1.18-P1-C4 if not recorded in “Step 1548-1.” v MCM module 1 at U1.18-P1-C3 if not recorded in “Step 1548-1.” Eserver pSeries 690 Service Guide...
  • Page 369 v MCM module 3 at U1.18-P1-C2 if not recorded in “Step 1548-1” on page 352. Step 1548-5 Turn on the power. Step 1548-6 Did the system stop with the same error code as recorded in “Step 1548-1” on page 352? Go to “Step 1548-7.”...
  • Page 370 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 1548-14 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 1548-15 Call for support. This ends the procedure. Eserver pSeries 690 Service Guide...

  • Page 371: Map 1549: Attention Problem Isolation

    MAP 1549: Attention Problem Isolation Step 1549-1 Record the error code and the location code(s) that sent you to this MAP. Step 1549-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1549-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Call for support.
  • Page 372 Multiple Bus Systems. Go to “Step 1549-8.” Step 1549-8 Have all the books or modules listed in “Step 1549-5” been replaced? Go to “Step 1549-2” on page 355. Go to “Step 1549-37” on page 361. Eserver pSeries 690 Service Guide...
  • Page 373 Step 1549-9 Attention: Some of the parts in the following list are modules that have a limit of three plug cycles. Before replacing any of the modules in the following list, call for support. Replace the following books and modules, if present, one at a time: v First location code item recorded, if any, in “Step 1549-1”...
  • Page 374 Memory book 3 at U1.18-P1-M6 if not recorded in “Step 1549-1” on page 355. v Primary I/O Book at U1.18-P1-H2 if not recorded in “Step 1549-1” on page 355. Step 1549-18 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 375 Step 1549-19 Did the system stop with the same error code as recorded in “Step 1549-1” on page 355? The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 376 Fourth I/O Book at U1.18-P1-H1 if not recorded in “Step 1549-1” on page 355. v Primary I/O Book at U1.18-P1-H2 if not recorded in “Step 1549-1” on page 355. Step 1549-30 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 377 Step 1549-31 Did the system stop with the same error code as recorded in “Step 1549-1” on page 355? The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems.
  • Page 378 Multiple Bus Systems. Go to “Step 1549-43.” Step 1549-43 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 1549-44 Call for support. This ends the procedure. Eserver pSeries 690 Service Guide...

  • Page 379: Map 154A: I2C Bus Problem Isolation

    MAP 154A: I2C Bus Problem Isolation Step 154A-1 Record the error code, location code(s), word 13, and word 16 that sent you to this MAP. Step 154A-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 154A-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Call for support.
  • Page 380 Go to “Step 1549-12” on page 357. Step 154A-13 Have all the books or modules listed in “Step 154A-10” been replaced? Go to “Step 154A-2” on page 363. Go to “Step 154A-14” on page 365. Eserver pSeries 690 Service Guide...
  • Page 381 Step 154A-14 Turn off the power. Chapter 3. Maintenance Analysis Procedures...
  • Page 382 Multiple Bus Systems. Go to “Step 154A-20.” Step 154A-20 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 154A-21 Call for support. This ends the procedure. Eserver pSeries 690 Service Guide...
  • Page 383 Step 154A-22 Is the value recorded in “Step 154A-1” on page 363 for word 13 of this error code equal to 0000A218 or 0000A21B? Go to “Step 154A-5” on page 363. Go to “Step 154A-23.” Step 154A-23 Replace the following cards and modules, if present, one at a time: v First location code item recorded, if any, in “Step 154A-1”...

  • Page 384: Map 154B: Insufficient Hardware Resources Problem Isolation

    MCM module 2 at U1.18-P1-C4 if not recorded in“Step 154B-1.” v MCM module 1 at U1.18-P1-C3 if not recorded in “Step 154B-1.” v MCM module 3 at U1.18-P1-C2 if not recorded in “Step 154B-1.” Eserver pSeries 690 Service Guide...
  • Page 385 Step 154B-5 Turn on the power. Step 154B-6 Did the system stop with the same error code as recorded in “Step 154B-1” on page 368? The book or module just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 386 Step 154B-14 Turn off the power. Make sure all amber logic-power LEDs of all installed processor subsystem DCAs are off. Step 154B-15 Call for support. This ends the procedure. Eserver pSeries 690 Service Guide...

  • Page 387: Chapter 4. Checkpoints

    Chapter 4. Checkpoints Checkpoints display on the media subsystem operator panel and the virtual terminal while the system is powering on and going through the initial program load (IPL). This chapter explains the IPL flow of the system and provides a table that lists checkpoints that you might see in the media subsystem operator panel and in a virtual terminal window on the HMC.
  • Page 388 Number of bootable adapters Phase 4 0xxx or 2xxx => blank 2 to 30+ Number of SSA drives Number of SCSI drives Number of async sessions Number of processors Number of adapters Amount of memory Eserver pSeries 690 Service Guide...
  • Page 389 Checkpoints enable users and service personnel to know what the server is doing, with some detail, as it initializes. These checkpoints are not intended to be error indicators, but in some cases a server could hang at one of the checkpoints without displaying an 8-character error code. It is for these hang conditions, only, that any action should be taken with respect to checkpoints.

  • Page 390: Service Processor Checkpoints

    Primary service processor thread waiting See note 1 on page 379. for response 9020 Service processor state set to pre-standby See note 1 on page 379. 9021 Service processor state set to standby See note 1 on page 379. Eserver pSeries 690 Service Guide...
  • Page 391 Checkpoint Description Action/ Possible Failing FRU 9022 Service processor state set to IPL See note 1 on page 379. 9023 Service processor state set to runtime See note 1 on page 379. 9024 Service processor state set to terminate See note 1 on page 379. 9025 Service processor state set to DPO See note 1 on page 379.
  • Page 392 See note 1 on page 379. from service processor 9200 Scan interface BATs See note 1 on page 379. 9300 Logic BIST See note 1 on page 379. 9301 Scanned ABIST See note 1 on page 379. Eserver pSeries 690 Service Guide...
  • Page 393 Checkpoint Description Action/ Possible Failing FRU 9302 Dedicated ABIST See note 1 on page 379. 9303 Dedicated ABIST array fuse repair See note 1 on page 379. calculation 9380 Built-in-self-test (BIST) See note 2 on page 379. 9400 Service processor is requesting system See note 1 on page 379.
  • Page 394 See note 1 on page 379. A80D Reserved; not used See note 1 on page 379. A80E Reserved; not used See note 1 on page 379. A80F Service processor dump done See note 1 on page 379. Eserver pSeries 690 Service Guide...
  • Page 395 Checkpoint Description Action/ Possible Failing FRU A810-A8FF Scan log dump in progress Informational message. (See “Scan Log Dump Policy” on page 790.) The last two characters of the checkpoints will change as the scan log dump progresses. If the last two characters do not change after five minutes, the service processor is hung and must be reset.
  • Page 396 If there is not, or the update does not fix the problem, replace the following FRUs, one at a time, in the following order: 1) Modem cable 2) Modem d. If this procedure does not fix the problem, call service support. Eserver pSeries 690 Service Guide...

  • Page 397: Firmware Checkpoints

    Firmware Checkpoints Firmware uses checkpoints (progress codes) in the range of Exxx to EFFF. These checkpoints occur during system startup and can be useful in diagnosing certain problems. Service processor checkpoints are listed in “Service Processor Checkpoints” on page 374. If you have a checkpoint with no location code associated with it, see “Determining Location Code”...
  • Page 398 Follow the repair action listed for checkpoint E151. E170 Start of PCI Bus Probe Follow the repair action listed for checkpoint E151. E172 First pass of PCI device probe Follow the repair action listed for checkpoint E151. Eserver pSeries 690 Service Guide...
  • Page 399 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E174 Establishing host connection If the system is not connected to an active network, or if the target server is inaccessible (which can result from incorrect IP parameters being specified), the system still attempts to boot and because time-out durations are necessarily long to accommodate retries, the system...
  • Page 400 Procedures” on page 310. E1AF System booted to utilities menu via NVRAM Go to “MAP 1540: Problem Isolation settings Procedures” on page 310. E1B1 Create serial node Go to “MAP 1540: Problem Isolation Procedures” on page 310. Eserver pSeries 690 Service Guide...
  • Page 401 HMC and the managed system. 4. Reboot the HMC. 5. There may be a hardware problem with the HMC. Refer to the IBM Hardware Management Console for pSeries Installation and Operations Guide. 6. There may be a hardware problem with the service processor in the managed system.
  • Page 402 E1F4 End self-test sequence on boot devices; Go to “MAP 1542: I/O Problem Isolation” on begin SMS. page 320. E1F5 Build boot device list Go to “MAP 1542: I/O Problem Isolation” on page 320. Eserver pSeries 690 Service Guide...
  • Page 403 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E1F6 Determine boot device sequence Go to “MAP 1542: I/O Problem Isolation” on page 320. E1F7 No boot image located Go to “Boot Problems” on page 411. E1F8 Partition (system firmware) is waiting for a Open a virtual terminal for the partition on virtual terminal to be opened on HMC.
  • Page 404 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 320. E50B Save I/O hub information 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 320. Eserver pSeries 690 Service Guide...
  • Page 405 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E50C Copy all of the memory ranges 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 320. E50D Copy all of the I/O data 1.
  • Page 406 PCI adapter card, replace the adapter card. 5. Replace the I/O subsystem backplane specified by the location code, or the I/O subsystem backplane that the RIO cables in step 1 are attached to. Eserver pSeries 690 Service Guide...
  • Page 407 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E529 Enable the control port and driver of the 1. Check the RIO cable specified by the current RIO hub location code. If the location code specifies an I/O subsystem or its RIO interface, check the RIO cables going into and out of the I/O subsystem.
  • Page 408 PCI adapter card, replace the adapter card. 4. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached 5. Go to “MAP 1542: I/O Problem Isolation” on page 320. Eserver pSeries 690 Service Guide...
  • Page 409 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E533 Set up the I/O hub routing table 1. Replace the I/O cable specified by the location code. 2. Replace the I/O book that the failing I/O subsystem is attached to, U1.18-P1-Hx. 3.
  • Page 410 1. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card. 2. Replace the I/O subsytem backplane that the RIO cable specified by the location code is attached to. Eserver pSeries 690 Service Guide...
  • Page 411 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E540 Begin initialization of I/O subsystem Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 320. E541 Initialize the routing table 1. Replace the I/O cable specified by the location code.
  • Page 412 I/O subsystem or its RIO interface, replace the RIO cables going into and out of the I/O subsystem. 3. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card. Eserver pSeries 690 Service Guide...
  • Page 413 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E550 Begin to initialize I/O interface chip 1. Replace the I/O cable specified by the location code. 2. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card.
  • Page 414 2. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card. 3. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 690 Service Guide...
  • Page 415 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E564 Set up I/O interface chip registers 1. Replace the I/O cable specified by the location code. 2. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card.
  • Page 416 1. Check for system firmware updates. chip 2. Go to “MAP 1542: I/O Problem Isolation” on page 320. 3. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card. Eserver pSeries 690 Service Guide...
  • Page 417 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E570 Initialize the PCI-ISA bridge chip 1. Replace the I/O cable specified by the location code. 2. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card.
  • Page 418 2. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card. 3. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 690 Service Guide...
  • Page 419 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E588 Set up EADS function registers 1. Replace the I/O cable specified by the location code. 2. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card.
  • Page 420 2. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card. 3. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 690 Service Guide...
  • Page 421 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E594 Begin probing slots 1. Replace the I/O cable specified by the location code. 2. If the location code associated with this checkpoint specifies a PCI adapter card, replace the adapter card. 3.
  • Page 422 Replace the adapter. an error. E604 SSA PCI adapter BIST and subsequent Replace the adapter. POSTs have completed successfully. E605 SSA PCI adapter BIST has completed Replace the adapter. successfully but subsequent POSTS have failed. Eserver pSeries 690 Service Guide...
  • Page 423 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E60E SSA PCI open firmware about to exit (no Replace the adapter. stack corruption). E60F SSA PCI open firmware has run Replace the adapter. unsuccessfully. E6FF SSA PCI open firmware about to exit (with Replace the adapter.
  • Page 424 Start cable ID request process 1. Check the SPCN and RIO cabling to the I/O subsystems 2. Disconnect then reconnect power to the system. 3. Go to “MAP 1542: I/O Problem Isolation” on page 320. 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 425 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E854 Start collecting cable IDs 1. Check the SPCN and RIO cabling to the I/O subsystems 2. Disconnect then reconnect power to the system. 3. Go to “MAP 1542: I/O Problem Isolation”...
  • Page 426 Procedures” on page 310. E901 The system firmware is in the recoverable Go to “MAP 1540: Problem Isolation non-maskable interrupt code Procedures” on page 310. EAA1 Probe PCI-PCI bridge bus Follow the repair actions for checkpoint E151. Eserver pSeries 690 Service Guide...

  • Page 427: Boot Problems

    Boot Problems Attention: If the system is running partitions from partition standby (LPAR), the following procedure addresses the problem in which one partition will not boot while other partitions boot successfully and run the operating system successfully. This procedure also addresses the problem in which a system does not boot to a full system partition. All of the system’s resources are available to the diagnostics;...
  • Page 428 Go to ″MAP 410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. If standalone diagnostics do not boot successfully from a NIM server: a. Verify that the network adapter is assigned to the correct partition. Eserver pSeries 690 Service Guide...
  • Page 429 b. Check the network settings and flag settings, as detailed in “Running Standalone Diagnostics from a Network Installation Management (NIM) Server” on page 780. c. Follow the procedure outlined in step 3 on page 412. 5. Go to “MAP 1542: I/O Problem Isolation” on page 320. Chapter 4.
  • Page 430 Eserver pSeries 690 Service Guide...

  • Page 431: Chapter 5. Error Code To Fru Index

    Chapter 5. Error Code to FRU Index The Error Code to FRU Index lists fault symptoms and possible causes. The most likely cause is listed first. Use this index to help you decide which FRUs to replace when servicing the system. Attention: If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation”...

  • Page 432: Confirming Initial Error Code

    Return to the step in the “Checkpoints and Error Codes Index” on page 418 table immediately after the step that sent you to this ″Confirming Initial Error Code″ procedure to perform the listed repair actions. Eserver pSeries 690 Service Guide...

  • Page 433: Four-Character Checkpoints

    If the repair actions for an error code are ineffective, continue to work upward through this group of error codes (which is forward in time from the earliest time stamp to the latest) until either the problem is fixed, you reach the error code that was first reported, or you are at the top of the list. Four-Character Checkpoints Four-character checkpoints in the form 8xxx, 9xxx, Axxx, Bxxx, and Exxx are listed in “Firmware Checkpoints”...

  • Page 434: Checkpoints And Error Codes Index

    Go to “SPCN Error Codes” on page 422 with the error code(s) from step 2 and follow the instructions in the SPCN error code table. 2xxx xxxx Firmware Error Codes Go to “Firmware/POST Error Codes” on page 490, and follow the instructions in the firmware error code table. Eserver pSeries 690 Service Guide...
  • Page 435 8-Digit Error Code What You Should Do 4-Digit Checkpoint 4xxx xxxx Service Processor Error Codes 1. Is the system powered up? Go to step 2 below. Go to step 4 below. 2. Find the error code in the service processor error log and check the value of word 13. Go to step 3 below.
  • Page 436 Go to “Firmware Checkpoints” on page 381 for more information on these checkpoints. Mxxx xxxx Problem Determination-Generated Error Codes Go to “Problem Determination-Generated Error Codes” on page 770, and follow the instructions in the error code table. Eserver pSeries 690 Service Guide...

  • Page 437: Operator Panel Error Codes

    Operator Panel Error Codes Attention: If you replace FRUs or perform an action on an I/O subsystem and the problem is still not corrected, go to “MAP 1542: I/O Problem Isolation” on page 320 unless you were already directed to any MAP 154x by the error code.

  • Page 438: Spcn Error Codes

    Primary I/O book Location: U1.18-P1-H2 1011 3104 I2C bus 4 fault Primary I/O book Location: U1.18-P1-H2 1011 3106 I2C bus 6 fault Primary I/O book Location: U1.18-P1-H2 1011 3113 RIO Bus Adapter Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 690 Service Guide...
  • Page 439 Error Code Description Action/ Possible Failing FRU 1011 3114 PCI Backplane Was the primary I/O book at location U1.18-P1-H2 changed prior to the most recent reboot of the system? This error code may be due to down-level system power control network firmware on the new primary I/O book.
  • Page 440 See note on page 518. 2. Primary I/O book Location: U1.18-P1-H2 1011 8423 No MCM 0 VPD card or MCM 1. Location: U1.18-P1-H2.3 and U1.18-P1-C1 See note on page 518. 2. Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 690 Service Guide...
  • Page 441 Error Code Description Action/ Possible Failing FRU 1011 8424 No MCM 2 VPD card or MCM 1. Location: U1.18-P1-H2.4 and U1.18-P1-C4 See note on page 518. 2. Primary I/O book Location: U1.18-P1-H2 1011 8425 No MCM 1 VPD card or MCM 1.
  • Page 442 2. BPC A controller Location: U1.35-P1-X4 and BPC-B controller, Location: U1.35-P2-X4 3. Primary I/O book Location: U1.18-P1-H2 1011 8750 BPC download failure on BPA A 1. BPC A controller, Location: U1.35-P1-X4 2. Primary I/O book, Location: U1.18-P1-H2 Eserver pSeries 690 Service Guide...
  • Page 443 Error Code Description Action/ Possible Failing FRU 1011 8751 BPC download failure on BPA B 1. BPC-B controller, Location: U1.35-P2-X4 2. Primary I/O book, Location: U1.18-P1-H2 1011 875A Informational message. No power subsystem FRU code update is required. 1011 875B Informational message. The power subsystem FRU code update has begun.
  • Page 444 1014 B824 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power” on page 194. first I/O subsystem 1014 B834 Overcurrent or overvoltage problem with 2.5V in Go to “MAP 1520: Power” on page 194. first I/O subsystem Eserver pSeries 690 Service Guide...
  • Page 445 Error Code Description Action/ Possible Failing FRU 1014 B844 Overcurrent or overvoltage problem with 12.0V in Go to “MAP 1520: Power” on page 194. first I/O subsystem 1014 B854 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 194. in first I/O subsystem 1014 BF06 Unable to resolve the chassis VPD in an I/O The chassis VPD in the I/O subsystem drawer...
  • Page 446 1. U1.9-V2/Q1 and U1.35-P2-X3/Q2 2. U1.9-V2/Q2 and U1.35-P1-X3/Q2 1014 xx27 Problem with fan 2 and fan 4 in first I/O 1. DCA-2 subsystem in primary rack Location U1.9–V2 2. Fan 2, Location U1.9–F2 3. Fan 4, Location U1.9–F4 Eserver pSeries 690 Service Guide...
  • Page 447 Error Code Description Action/ Possible Failing FRU 1014 xx31 First I/O subsystem in primary rack, I/O U1.9-P1 subsystem backplane 1 fault 1014 xx33 Seeprom fault on I/O subsystem backplane 1 in U1.9-P1 first I/O subsystem in primary rack 1014 xx41 First I/O subsystem in primary rack, I/O U1.9-P2 subsystem backplane 2 fault 1014 xx43 Seeprom fault on I/O subsystem backplane 2 in...
  • Page 448 If this is the case, reinstall the original FRUs in the drawer, then replace the FRUs one at a time. If only one FRU was replaced and this error code occurred, call service support. Eserver pSeries 690 Service Guide...
  • Page 449 Error Code Description Action/ Possible Failing FRU 1015 CC36 Description: Loss of pgood on an I/O planar in the I/O drawer at location U1.5 Action: This error code can be caused by hot-plugging RIO cables. To see if this is a recoverable error, do the following: Power down the system by following the appropriate procedure in “Powering Off and Powering On the System”...
  • Page 450 1 fault 1015 xx33 Seeprom fault on I/O subsystem backplane 1 in U1.5-P1 second I/O subsystem in primary rack 1015 xx41 Second I/O subsystem in primary rack, I/O U1.5-P2 subsystem backplane 2 fault Eserver pSeries 690 Service Guide...
  • Page 451 Error Code Description Action/ Possible Failing FRU 1015 xx43 Seeprom fault on I/O subsystem backplane 2 in U1.5-P2 second I/O subsystem in primary rack 1015 xx51 Second I/O subsystem in primary rack, DASD U1.5-P3 backplane 1 fault 1015 xx53 Seeprom fault on DASD backplane 1 in second U1.5-P3 I/O subsystem in primary rack 1015 xx61 Second I/O subsystem in primary rack, DASD...
  • Page 452 1016 B844 Overcurrent or overvoltage problem with 12.0V in Go to “MAP 1520: Power” on page 194. third I/O subsystem 1016 B854 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 194. in third I/O subsystem Eserver pSeries 690 Service Guide...
  • Page 453 Error Code Description Action/ Possible Failing FRU 1016 BF06 Unable to resolve the chassis VPD in an I/O The chassis VPD in the I/O subsystem drawer subsystem identified by the location code could not be resolved. This may be an indication that more than one FRU in the drawer was replaced during a service action.
  • Page 454 3. Fan 4, Location U1.1–F4 1016 xx31 Third I/O subsystem in primary rack, I/O U1.1-P1 subsystem backplane 1 fault 1016 xx33 Seeprom fault on I/O subsystem backplane 1 in U1.1-P1 third I/O subsystem in primary rack Eserver pSeries 690 Service Guide...
  • Page 455 Error Code Description Action/ Possible Failing FRU 1016 xx41 Third I/O subsystem in primary rack, I/O U1.1-P2 subsystem backplane 2 fault 1016 xx43 Seeprom fault on I/O subsystem backplane 2 in U1.1-P2 third I/O subsystem in primary rack 1016 xx51 Third I/O subsystem in primary rack, DASD U1.1-P3 backplane 1 fault 1016 xx53 Seeprom fault on DASD backplane 1 in third I/O...
  • Page 456 Go to “MAP 1520: Power” on page 194. fourth I/O subsystem, no IBF 1017 B854 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 194. in fourth I/O subsystem, no IBF Eserver pSeries 690 Service Guide...
  • Page 457 Error Code Description Action/ Possible Failing FRU 1017 BF06 Unable to resolve the chassis VPD in an I/O The chassis VPD in the I/O subsystem drawer subsystem identified by the location code could not be resolved. This may be an indication that more than one FRU in the drawer was replaced during a service action.
  • Page 458 Location U1.13-F1 3. Fan 3, Location U1.13-F3 1017 xx21 Fourth I/O subsystem in primary rack (no IBF), U1.13-V2 DCA-2 1017 xx23 Seeprom fault on DCA-2 in fourth I/O subsystem U1.13-V2 (no IBF) in primary rack Eserver pSeries 690 Service Guide...
  • Page 459 Error Code Description Action/ Possible Failing FRU 1017 xx25 Fourth I/O subsystem in primary rack no IBFs If there is no DCA in U1.18-P1-V8, primary rack, no IBFs, go to “MAP 1520: Power” on page 194with these pairs of location codes: 1.
  • Page 460 1. Check the cable between the two BPCs; reseat and look for bent pins. 2. Replace BPC-A, location: U1.35-P1-X4 3. Replace BPC-B, location: U1.35-P2-X4. 101A D216 BPA-BPA communication failure Go to “MAP 1520: Power” on page 194 for isolation. Eserver pSeries 690 Service Guide...
  • Page 461 Error Code Description Action/ Possible Failing FRU 101A D616 Problem with external UPS: utility failure 1. Verify the cabling between the UPS and the BPCs. 2. Refer to the manufacturer’s documentation for the UPS. 3. Call service support. 101A D716 Problem with external UPS: battery low 1.
  • Page 462 Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 202. 101A FE66 BPR 2A communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 202. Eserver pSeries 690 Service Guide...
  • Page 463 Error Code Description Action/ Possible Failing FRU 101A FE76 BPR 3A communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 202. 101A FFx6 Cabling error on the BPC or a BPD that is not There is a cabling problem on a BPC or BPD isolated that cannot be isolated.
  • Page 464 If there is a 6th DCA in U1.18-P1-V8, this error code will not be reported. 101A x835 Power cable fault Go to “MAP 1520: Power” on page 194 with these location codes: U1.35-P1-X2/Q8# to U2.13-V2/Q1# Eserver pSeries 690 Service Guide...
  • Page 465 Error Code Description Action/ Possible Failing FRU 101A x925 Power cable fault Go to “MAP 1520: Power” on page 194 with these location codes: U1.35-P1-X3/Q9# to U1.18-P1-V5/Q1# 101A x935 Power cable fault If there is no DCA in U1.18-P1-V8, go to “MAP 1520: Power”...
  • Page 466 101A xx83 Seeprom (VPD) fault on IBF-1A U1.13-P1-V1 101A xx91 BPA-A / IBF 2 U1.15-P1-V2 101A xx93 Seeprom (VPD) fault on IBF-2A U1.15-P1-V2 101A xxA1 BPA-A / IBF 3 U2.17-P1-V5 101A xxA3 Seeprom (VPD) fault on IBF-3A U2.17-P1-V5 Eserver pSeries 690 Service Guide...
  • Page 467 Error Code Description Action/ Possible Failing FRU 101A xxB1 BPA-A / EPO_SW 1. Replace the UEPO switch, Location: U1-V1 2. Check the cable from BPC-A to the UEPO switch, Location U1-V1/Q1# 101B 0106 BPA B ac loss in a frame that contains only High Go to “MAP 1520: Power”...
  • Page 468 3. Call service support. 101B DB16 Problem with external UPS: UPS not available 1. Verify the cabling between the UPS and the BPCs. 2. Refer to the manufacturer’s documentation for the UPS. 3. Call service support. Eserver pSeries 690 Service Guide...
  • Page 469 Error Code Description Action/ Possible Failing FRU 101B DC16 External UPS: battery not low (informational Informational message. If a problem is message) suspected: 1. Verify the cabling between the UPS and the BPCs. 2. Refer to the manufacturer’s documentation for the UPS. 3.
  • Page 470 Go to “MAP 1520: Power” on page 194 with these location codes: U1.35-P2-X4/Q3# to U1.18-X3/Q2# 101B x325 Power cable fault Go to “MAP 1520: Power” on page 194 with these location codes: U1.35-P2-X3/Q3# to U1.5-V1/Q1# Eserver pSeries 690 Service Guide...
  • Page 471 Error Code Description Action/ Possible Failing FRU 101B x335 Power cable fault Go to “MAP 1520: Power” on page 194 with these location codes: U1.35-P2-X2/Q3# to U2.5-V1/Q2# 101B x415 Power cable fault Go to “MAP 1520: Power” on page 194 with these location codes: U1.35-P2-X4/Q4# to U1.18-X4/Q2# 101B x425 Power cable fault...
  • Page 472 101B xx22 BPC-B to BPD-1 communications fault 1. BPD-1 Location: U1.35-P2-X3 2. BPC-B Location: U1.35-P2-X4 3. BPE backplane B Location: U1.35-P2 101B xx23 Seeprom (VPD) fault on BPD-1B U1.35-P2-X3 101B xx31 BPA-B / BPD-2 U1.35-P2-X2 Eserver pSeries 690 Service Guide...
  • Page 473 Error Code Description Action/ Possible Failing FRU 101B xx32 BPC-B to BPD-2 communications fault 1. BPD-2 Location: U1.35-P2-X2 2. BPC-B Location: U1.35-P2-X4 3. BPE backplane B Location: U1.35-P2 101B xx33 Seeprom (VPD) fault on BPD-2B U1.35-P2-X2 101B xx41 BPA-B / BPD-3 U1.35-P2-X1 101B xx42 BPC-B to BPD-3 communications fault 1.
  • Page 474 4. Call service support. 101C 1C06 Loss of airflow in processor subsystem resulting Go to “MAP 1527: An Airflow Loss Has Been in over-temperature Detected” on page 211 with location U1.18. Eserver pSeries 690 Service Guide...
  • Page 475 Error Code Description Action/ Possible Failing FRU 101C 5Ax6 A DCA FRU whose firmware is too down-level to If the system is powered up: function with the power subsystem has been 1. Wait approximately 30 minutes, then press installed in the CEC. For the DCA to function, the green start-of-service button followed by the power subsystem controller must download the white end-of-service button.
  • Page 476 101C B014 Overcurrent or overvoltage problem with 2.5V in Go to “MAP 1520: Power” on page 194. processor subsystem 101C B114 Overcurrent or overvoltage problem with 1.8V in Go to “MAP 1520: Power” on page 194. processor subsystem Eserver pSeries 690 Service Guide...
  • Page 477 Error Code Description Action/ Possible Failing FRU 101C B124 Overcurrent or overvoltage problem with 1.5V in Go to “MAP 1520: Power” on page 194. processor subsystem 101C B134 Overcurrent or overvoltage problem with 1.5V in Go to “MAP 1520: Power” on page 194. processor subsystem 101C B144 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power”...
  • Page 478 Examine the service processor error log. If there are no other power-related error codes (in the time frame in which this code was generated) in the service processor error log, the FRU indicated with this error code, if any, should be replaced. Eserver pSeries 690 Service Guide...
  • Page 479 Error Code Description Action/ Possible Failing FRU 101C F536 An N+1 boundary (DCA or fan) has dropped to This is normally an informational message. It N-mode status in the processor subsystem, should be accompanied by other error codes that location: U1.18 more precisely indicate where the failure is.
  • Page 480 Go to “MAP 1520: Power” on page 194 with these pairs of location codes: 1. U1.18-P1-V5/Q1 and U1.35-P1-X3/Q9 2. U1.18-P1-V5/Q2 and U1.35-P2-X3/Q9 101C xx51 Processor subsystem / DCA-5 U1.18-P1-V6 101C xx53 Seeprom (VPD) fault on processor subsystem U1.18-P1-V6 DCA-5 Eserver pSeries 690 Service Guide...
  • Page 481 Error Code Description Action/ Possible Failing FRU 101C xx55 Processor subsystem / DCA-5 cable fault Go to “MAP 1520: Power” on page 194 with these pairs of location codes: 1. U1.18-P1-V6/Q1 and U1.35-P1-X3/Q10 2. U1.18-P1-V6/Q2 and U1.35-P2-X3/Q10 101C xx61 Processor subsystem / DCA-6 (if installed) U1.18-P1-V8 101C xx63 Seeprom (VPD) fault on processor subsystem U1.18-P1-V8...
  • Page 482 1021 6844 Overcurrent or overvoltage problem with 12.0V in Go to “MAP 1520: Power” on page 194. 5th I/O subsystem 1021 6854 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 194. in 5th I/O subsystem Eserver pSeries 690 Service Guide...
  • Page 483 Error Code Description Action/ Possible Failing FRU 1021 7017 Problem with fan 3 in first I/O subsystem in 1. DCA-1 second rack (I/O subsystem 5) Location: U2.1-V1 2. Fan 3 Location: U2.1-F3 1021 7027 Problem with fan 4 in first I/O subsystem in 1.
  • Page 484 1021 CDC6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 194. subsystem in an I/O drawer. 1021 F4x6 Hardware configuration does not support Call Service Support N-mode power. Eserver pSeries 690 Service Guide...
  • Page 485 Error Code Description Action/ Possible Failing FRU 1021 F516 An N+1 boundary (DCA or fan) has dropped to This is normally an informational message. It N-mode status in the first I/O subsystem in the should be accompanied by other error codes that secondary rack, location: U2.1.
  • Page 486 I/O subsystem in second rack (I/O subsystem 6) 1022 6814 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 194. second I/O subsystem in second rack (I/O subsystem 6) Eserver pSeries 690 Service Guide...
  • Page 487 Error Code Description Action/ Possible Failing FRU 1022 6824 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power” on page 194. second I/O subsystem in second rack (I/O subsystem 6) 1022 6834 Overcurrent or overvoltage problem with 2.5V in Go to “MAP 1520: Power”...
  • Page 488 OK in the operator panel in the media drawer, look at the service action event log in Service Focal Point on the HMC. If this error code does not reoccur, no action is required. If this error code reoccurs, replace the I/O planar, location: U2.5-P2. Eserver pSeries 690 Service Guide...
  • Page 489 Error Code Description Action/ Possible Failing FRU 1022 CD96 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 194. subsystem in an I/O drawer. 1022 CDA6 A power short has been detected in the DASD Go to “MAP 1520: Power”...
  • Page 490 IBF, moves to second rack) Location: U2.9-V2 2. Fan 2 Location: U2.9-F2 1023 1C06 Loss of airflow in fourth I/O subsystem, with IBF Go to “MAP 1527: An Airflow Loss Has Been location: U2.9 Detected” on page 211. Eserver pSeries 690 Service Guide...
  • Page 491 Error Code Description Action/ Possible Failing FRU 1023 6014 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 194. fourth I/O subsystem (with IBF, moves to second rack) 1023 6024 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power”...
  • Page 492 If this is the case, reinstall the original FRUs in the drawer, then replace the FRUs one at a time. If only one FRU was replaced and this error code occurred, call service support. Eserver pSeries 690 Service Guide...
  • Page 493 Error Code Description Action/ Possible Failing FRU 1023 CC36 Description: Loss of pgood on an I/O planar in the I/O drawer at location U2.9 Action:This error code can be caused by hot-plugging RIO cables. To see if this is a recoverable error, do the following: 1.
  • Page 494 (with IBF, moves to second rack) Location U2.9–V2 2. Fan 2, Location U2.9–F2 3. Fan 4, Location U2.9–F4 1023 xx31 Fourth I/O subsystem (with IBF) in secondary U2.9-P1 rack I/O subsystem backplane 1 fault Eserver pSeries 690 Service Guide...
  • Page 495 Error Code Description Action/ Possible Failing FRU 1023 xx33 Seeprom fault on I/O subsystem backplane 1 in U2.9-P1 fourth I/O subsystem (with IBF) in secondary rack 1023 xx41 Fourth I/O subsystem (with IBF) in secondary U2.9-P2 rack I/O subsystem backplane 2 fault 1023 xx43 Seeprom fault on I/O subsystem backplane 2 in U2.9-P2 fourth I/O subsystem (with IBF) in secondary...
  • Page 496 1024 8A00 The SPCN firmware has detected a change in Informational message. the drawer configuration 1024 B014 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 194. third I/O subsystem in second rack (I/O subsystem 7). Location: U2.13 Eserver pSeries 690 Service Guide...
  • Page 497 Error Code Description Action/ Possible Failing FRU 1024 B024 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power” on page 194. third I/O subsystem in second rack (I/O subsystem 7). Location: U2.13 1024 B034 Overcurrent or overvoltage problem with 2.5V in Go to “MAP 1520: Power”...
  • Page 498 1024 CDC6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 194. subsystem in an I/O drawer. Location: U2.13 1024 F4x6 Hardware configuration does not support Call Service Support N-mode power. Eserver pSeries 690 Service Guide...
  • Page 499 Error Code Description Action/ Possible Failing FRU 1024 F516 An N+1 boundary (DCA or fan) has dropped to This is normally an informational message. It N-mode status in third I/O subsystem in second should be accompanied by other error codes that rack (I/O subsystem 7), location: U2.13.
  • Page 500 I/O subsystem in second rack (I/O subsystem 8) 1025 6044 Overcurrent or overvoltage problem with 12.0V in Go to “MAP 1520: Power” on page 194. fourth I/O subsystem in second rack (I/O subsystem 8) Eserver pSeries 690 Service Guide...
  • Page 501 Error Code Description Action/ Possible Failing FRU 1025 6054 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 194. in fourth I/O subsystem in second rack (I/O subsystem 8) 1025 6814 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power”...
  • Page 502 OK in the operator panel in the media drawer, look at the service action event log in Service Focal Point on the HMC. If this error code does not reoccur, no action is required. If this error code reoccurs, replace the I/O planar, location: U2.19-P1. Eserver pSeries 690 Service Guide...
  • Page 503 Error Code Description Action/ Possible Failing FRU 1025 CC46 Description: Loss of pgood on an I/O planar in the I/O drawer at location U2.19 Action:This error code can be caused by hot-plugging RIO cables. To see if this is a recoverable error, do the following: 1.
  • Page 504 1025 xx41 Fourth I/O subsystem in second rack (I/O U2.19-P2 subsystem 8) I/O subsystem backplane 2 fault 1025 xx43 Seeprom fault on I/O subsystem backplane 2 in U2.19-P2 fourth I/O subsystem in second rack (I/O subsystem 8) Eserver pSeries 690 Service Guide...
  • Page 505 Error Code Description Action/ Possible Failing FRU 1025 xx51 Fourth I/O subsystem in second rack (I/O U2.19-P3 subsystem 8) DASD backplane 1 fault 1025 xx53 Seeprom fault on DASD backplane 1 in fourth U2.19-P3 I/O subsystem in second rack (I/O subsystem 8) 1025 xx61 Fourth I/O subsystem in second rack (I/O U2.19-P4 subsystem 8), DASD backplane 2 fault...

  • Page 506: Firmware/Post Error Codes

    2. Check ac power source to I/O subsystem “x”. See “AIX and Physical Location Code Tables” in Chapter 1, for location codes. 2022 0000 The I/O bus is running slowly 1. Check cabling. 2. Call second level of support. Eserver pSeries 690 Service Guide...
  • Page 507 Error Code Description Action/ Possible Failing FRU 203w 0xyz Remote I/O (RIO) configuration warning. Go to “MAP 1542: I/O Problem Isolation” on page 320. This code indicates that a RIO configuration was detected that does not result in complete loops. The system continues to boot, however performance or recovery capability may be reduced.
  • Page 508 2. Contact your next level of support for assistance. 20D0 0A03 Error initializing interface/service processor 1. Check for system firmware updates. Apply access update if available. 2. Contact your next level of support for assistance. Eserver pSeries 690 Service Guide...
  • Page 509 Error Code Description Action/ Possible Failing FRU 20D0 0A04 Error initializing interface/ operator panel 1. Check for system firmware updates. Apply access update if available. 2. Contact your next level of support for assistance. 20D0 0A05 Error initializing hardware access 1.
  • Page 510 2. Contact your next level of support for assistance. 20D0 0998 Operating system terminated with error string Call service support. A hypervisor dump may be available; see “Hypervisor Dump Retrieval Procedure” on page 771. Eserver pSeries 690 Service Guide...
  • Page 511 Error Code Description Action/ Possible Failing FRU 20D0 0999 Operating system terminated with error string Call service support. A hypervisor dump may be available; see “Hypervisor Dump Retrieval Procedure” on page 771. 20D0 9001 Subsystem information not found in VPD 1.
  • Page 512 2. Contact your next level of support for assistance. 20D1 0002 Failed to disable heartbeat alarm 1. Check for system firmware updates. Apply update if available. 2. Contact your next level of support for assistance. Eserver pSeries 690 Service Guide...
  • Page 513 Error Code Description Action/ Possible Failing FRU 20D1 0003 Failed to send boot status in LPAR partition 1. Check for system firmware updates. Apply update if available. 2. Contact your next level of support for assistance. 20D1 0004 Failed to locate service processor device tree 1.
  • Page 514 2. Check for system firmware updates. Apply update if available. 3. Contact your next level of support for assistance. 20E0 0001 Privileged-access password entry error. The password has been entered incorrectly. Try installing the password again. Eserver pSeries 690 Service Guide...
  • Page 515 Error Code Description Action/ Possible Failing FRU 20E0 0004 Battery drained or needs replacement 1. Replace the battery, Location: U1.18-P1-H2-V1 2. If problem persists, replace the primary I/O book, Location: U1.18-P1-H2 20E0 0009 Invalid password entered - system locked The password has been entered incorrectly 3 times.
  • Page 516 20EE 0010 Unable to execute the root vpd method 1. Verify that the system is in LPAR mode, and reboot the system. 2. Reflash the system with the latest level of system firmware. 3. Call service support. Eserver pSeries 690 Service Guide...
  • Page 517 Error Code Description Action/ Possible Failing FRU 20EE 0011 Unable to execute the root-lpar-vpd vpd 1. Verify that the system is in LPAR mode, method and reboot the system. 2. Reflash the system with the latest level of system firmware. 3.
  • Page 518 20EE 0100 Fcode resident on an I/O adapter is not Informational message. The adapter’s Fcode supported on this system driver is not supported on this system. IBM may produce a compatible driver in the future, but does not guarantee one. Additional information may be available from service support.
  • Page 519 Error Code Description Action/ Possible Failing FRU 20FF0021 Invalid VPD (ID tag length is more than 256 1. Replace the part specified by the location bytes) code. 2. If no location code is shown with the error code, call service support. 20FF0022 Invalid VPD (84/90 tag length is more than 1.
  • Page 520 Check the system error logs to determine the location code information associated with the error code. 1. Replace the SCSI device. 2. Replace the SCSI cable. 3. Replace the SCSI controller. Eserver pSeries 690 Service Guide...
  • Page 521 Error Code Description Action/ Possible Failing FRU 21A0 0002 SCSI DASD: test unit ready failed; sense data Before replacing any system components, available refer to the Action under error code 21A0 0001. 1. Replace the media (if a removable media device).
  • Page 522 1. Replace the SCSI device. 2. Replace the media. 21F0 0003 SCSI CD-ROM: send diagnostic failed; sense Before replacing any system components, data available refer to the Action under error code 21A0 0001. Replace the SCSI device. Eserver pSeries 690 Service Guide...
  • Page 523 Error Code Description Action/ Possible Failing FRU 21F0 0004 SCSI CD-ROM: send diagnostic failed - devofl Before replacing any system components, command refer to the Action under error code 21A0 0001. Replace the SCSI device. 21F2 0001 SCSI read/write optical device: test unit ready Before replacing any system components, failed;...
  • Page 524 Refer to Action under error code contains a null character. 25A8 0xxx 25A8 0215 NVRAM RIO-USR-select variable not found Complete the following: 1. Check for platform firmware updates. Apply if available. 2. Call service support. Eserver pSeries 690 Service Guide...
  • Page 525 Error Code Description Action/ Possible Failing FRU 25A8 0998 NVRAMRC script evaluation error - command line execution error Action: Execution of a command line within the nvram configuration variable “nvramrc” (script) resulted in a “throw” being executed. This script can be modified by the system firmware SMS utilities, the operating system, PCI adapter rom code or utility, or an operator (via the open firmware script editing command nvedit).
  • Page 526 3. Run AIX diagnostics on adapter. Replace if indicated. 4. Replace adapter. 5. Check for system firmware updates. Apply if update available. 6. Replace I/O subsystem backplane. (See notes on Chapter 5, “Error Code to FRU Index,” on page 415.) Eserver pSeries 690 Service Guide...
  • Page 527 Error Code Description Action/ Possible Failing FRU 2602 0007 PCI device I/O or memory space request 1. If the location code identifies a slot: could not be satisfied a. Reseat the adapter and reboot the system. b. Replace the adapter. c.
  • Page 528 Chapter 5, “Error Code to FRU Index,” on page 415). If the location code identifies an I/O subsystem backplane: 1. Check for system firmware updates. Apply if update is available. 2. Replace I/O subsystem backplane. Eserver pSeries 690 Service Guide...
  • Page 529 Error Code Description Action/ Possible Failing FRU 2602 0014 A PCI adapter is not properly seated, or an If the location code identifies a slot: invalid type of PCI adapter is installed in the 1. Check the PCI adapter specified by the system.
  • Page 530 2B20 0012 This is an informational code that is generated There is no action required. when the cpu_deallocate command is used To bring the processor back on-line, or back to take a processor off-line. into the system or partition configuration, reboot the operating system. Eserver pSeries 690 Service Guide...
  • Page 531 Error Code Description Action/ Possible Failing FRU 2B20 0022 Processor is deconfigured by the system. The processor has previously failed BIST or POST. Replace the processor MCM indicated by the location code associated with the error code in the error log. 2B20 0031 Processor is failing POST Replace the processor MCM indicated by the location code associated with the error code...
  • Page 532 Replace the MCM that contains the failing processor according to the following table: v hhh = 0 - 7: U1.18-P1-C1 v hhh = 8-15: U1.18-P1-C3 v hhh = 16-23: U1.18-P1-C4 v hhh = 24-31: U1.18-P1-C2 Eserver pSeries 690 Service Guide...
  • Page 533 Error Code Description Action/ Possible Failing FRU 2Dmm mhhh A processor’s timebase enable signal is stuck 1. Replace the primary I/O book, location: disabled U1.18-P1-H2. 2. hhh indicates the failing processor. Replace the MCM that contains the failing processor according to the following table: v hhh = 0 - 7: U1.18-P1-C1 v hhh = 8-15: U1.18-P1-C3 v hhh = 16-23: U1.18-P1-C4...

  • Page 534: Service Processor Error Codes

    1. Replace the CUoD capacity card Location: U1.18-P1-H2.2 2. Ask the customer to reenter the CUoD activation keys. 4064 0010 Processor subsystem tests detected fault in Memory book (slot 0) Memory book (slot 0) Location: U1.18-P1-M2 Eserver pSeries 690 Service Guide...
  • Page 535 Error Code Description Action/ Possible Failing FRU 4064 0011 Processor subsystem tests detected fault in Memory book (slot 1) Memory book (slot 1) Location: U1.18-P1-M3 4064 0012 Processor subsystem tests detected fault in Memory book (slot 2) Memory book (slot 2) Location: U1.18-P1-M7 4064 0013 Processor subsystem tests detected fault in Memory book (slot 3)
  • Page 536 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 537 Error Code Description Action/ Possible Failing FRU 4064 0A05 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 1 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 538 1. Check for system firmware updates. book (slot 0 RIO port 2) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3. Primary I/O book Location: U1.18-P1-H2 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 539 Error Code Description Action/ Possible Failing FRU 4064 0B03 Processor subsystem tests detected fault in I/O 1. Check for system firmware updates. book (slot 0 RIO port 3) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3.
  • Page 540 4064 0B27 Processor subsystem tests detected fault in I/O 1. Check for system firmware updates. book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 541 Error Code Description Action/ Possible Failing FRU 4064 0B30 Processor subsystem tests detected fault in I/O 1. Check for system firmware updates. book 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
  • Page 542 Location: U1.18-P1-H1 4064 0BF3 Processor subsystem tests detected fault in I/O 1. Check the cabling on the following RIO hub chip 3 (port x) ports: a. U1.18-P1-H1/Q1 b. U1.18-P1-H1/Q2 2. Replace the RIO book, Location: U1.18-P1-H1 Eserver pSeries 690 Service Guide...
  • Page 543 Error Code Description Action/ Possible Failing FRU 4064 0BF4 Processor subsystem tests detected fault in I/O 1. Check the cabling on the following RIO hub chip 4 (port x) ports: a. U1.18-P1-H3/Q7 b. U1.18-P1-H3/Q8 2. Replace the RIO book, Location: U1.18-P1-H3 4064 0BF5 Processor subsystem tests detected fault in I/O 1.
  • Page 544 L3 cache module 2 and L3 VPD card cache module 2 Location: U1.18-P1-C11 and U1.18-P1-H2.1 4064 0D03 Processor subsystem tests detected fault in L3 L3 cache module 3 and L3 VPD card cache module 3 Location: U1.18-P1-C10 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 545 Error Code Description Action/ Possible Failing FRU 4064 0D04 Processor subsystem tests detected fault in L3 L3 cache module 4 and L3 VPD card cache module 4 Location: U1.18-P1-C8 and U1.18-P1-H2.1 4064 0D05 Processor subsystem tests detected fault in L3 L3 cache module 5 and L3 VPD card cache module 5 Location: U1.18-P1-C20 and U1.18-P1-H2.1...
  • Page 546 If a CEC subsystem error (a 4xxx yyyy error) did not occur during the slow boot, look for a 4xxx yyyy error immediately preceding the 406x 0EBF error. Replace the part indicated by the location code associated with that error. Eserver pSeries 690 Service Guide...
  • Page 547 Error Code Description Action/ Possible Failing FRU 4064 0EE1 Processor subsystem tests detected fault in 1. Check for system firmware updates. service processor code (invalid MRU to 2. Call service support. mapping) 4064 0EE2 Processor subsystem tests detected fault in 1.
  • Page 548 1. Check for system firmware updates. problem 2. MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 4065 00B7 Display alter tests detected hardware problem Go to “MAP 1540: Problem Isolation in the processor subsystem Procedures” on page 310. Eserver pSeries 690 Service Guide...
  • Page 549 Error Code Description Action/ Possible Failing FRU 4065 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware. If AIX is available on the system, go to MAP 0235 in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509.
  • Page 550 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 551 Error Code Description Action/ Possible Failing FRU 4065 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 552 4065 0B21 Display alter tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 553 Error Code Description Action/ Possible Failing FRU 4065 0B22 Display alter tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4.
  • Page 554 I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4. 3. Third I/O book or SNI adapter Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 555 Error Code Description Action/ Possible Failing FRU 4065 0B36 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book or SNI adapter 2. Check the I/O cabling between the third I/O book and the I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4.
  • Page 556 Location: U1.18-P1-H1 4065 0BFA Display alter tests detected fault in I/O hub chip 1. Check the cabling on the following RIO 10 (port x) ports: a. U1.18-P1-H3/Q3 b. U1.18-P1-H3/Q4 2. Replace the RIO book, Location: U1.18-P1-H3 Eserver pSeries 690 Service Guide...
  • Page 557 Error Code Description Action/ Possible Failing FRU 4065 0BFB Display alter tests detected fault in I/O hub chip 1. Check the cabling on the following RIO 11 (port x) ports: a. U1.18-P1-H3/Q1 b. U1.18-P1-H3/Q2 2. Replace the RIO book, Location: U1.18-P1-H3 4065 0BFC Display alter tests detected fault in I/O hub chip 1.
  • Page 558 4065 0EA2 Display alter tests detected fault in PRD code 1. Check for system firmware updates. on service processor 2. Call service support. 4065 0EA4 The service processor firmware detected a Call service support. hardware problem but was unable to isolate the source. Eserver pSeries 690 Service Guide...
  • Page 559 Error Code Description Action/ Possible Failing FRU 4065 0EA5 PRD detected a problem in the FNM code 1. Check for system firmware updates. 2. Call service support. 4065 0EAA PRD: FNM is handling this error 1. Check for system firmware updates. 2.
  • Page 560 4066 0010 Scan interface basic assurance tests detected Memory book (slot 0) fault in Memory book (slot 0) Location: U1.18-P1-M2 4066 0011 Scan interface basic assurance tests detected Memory book (slot 1) fault in Memory book (slot 1) Location: U1.18-P1-M3 Eserver pSeries 690 Service Guide...
  • Page 561 Error Code Description Action/ Possible Failing FRU 4066 0012 Scan interface basic assurance tests detected Memory book (slot 2) fault in Memory book (slot 2) Location: U1.18-P1-M7 4066 0013 Scan interface basic assurance tests detected Memory book (slot 3) fault in Memory book (slot 3) Location: U1.18-P1-M6 4066 0014 Scan interface basic assurance tests detected Memory book (slot 4)
  • Page 562 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 563 Error Code Description Action/ Possible Failing FRU 4066 0A05 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 1 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 564 1. Check for system firmware updates. fault in I/O book (slot 0 RIO port 2) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3. Primary I/O book Location: U1.18-P1-H2 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 565 Error Code Description Action/ Possible Failing FRU 4066 0B03 Scan interface basic assurance tests detected 1. Check for system firmware updates. fault in I/O book (slot 0 RIO port 3) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3.
  • Page 566 4066 0B27 Scan interface basic assurance tests detected 1. Check for system firmware updates. fault in I/O book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 567 Error Code Description Action/ Possible Failing FRU 4066 0B30 Scan interface basic assurance tests detected 1. Check for system firmware updates. fault in I/O book 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
  • Page 568 4066 0BF3 Scan interface basic assurance tests detected 1. Check the cabling on the following RIO fault in I/O hub chip 3 (port x) ports: a. U1.18-P1-H1/Q1 b. U1.18-P1-H1/Q2 2. Replace the RIO book, Location: U1.18-P1-H1 Eserver pSeries 690 Service Guide...
  • Page 569 Error Code Description Action/ Possible Failing FRU 4066 0BF4 Scan interface basic assurance tests detected 1. Check the cabling on the following RIO fault in I/O hub chip 4 (port x) ports: a. U1.18-P1-H3/Q7 b. U1.18-P1-H3/Q8 2. Replace the RIO book, Location: U1.18-P1-H3 4066 0BF5 Scan interface basic assurance tests detected 1.
  • Page 570 L3 cache module 2 Location: U1.18-P1-C11 and U1.18-P1-H2.1 4066 0D03 Scan interface basic assurance tests detected L3 cache module 3 and L3 VPD card fault in L3 cache module 3 Location: U1.18-P1-C10 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 571 Error Code Description Action/ Possible Failing FRU 4066 0D04 Scan interface basic assurance tests detected L3 cache module 4 and L3 VPD card fault in L3 cache module 4 Location: U1.18-P1-C8 and U1.18-P1-H2.1 4066 0D05 Scan interface basic assurance tests detected L3 cache module 5 and L3 VPD card fault in L3 cache module 5 Location: U1.18-P1-C20 and U1.18-P1-H2.1...
  • Page 572 Procedures” on page 310. 4066 0EBB Attention line 10 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 310. 4066 0EBC Attention line 11 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 310. Eserver pSeries 690 Service Guide...
  • Page 573 Error Code Description Action/ Possible Failing FRU 4066 0EBF Memory error 1. Reboot the system in slow mode to the SMS menus. See “Performing Slow Boot” on page 415. 2. Examine the service processor error log. v If a CEC subsystem error (a 4xxx yyyy error) occurred during the slow boot that calls out the memory, processors, L3 cache modules, or the primary I/O book,...
  • Page 574 2. MCM module 0 and VPD card Location: U1.18-P1-C1 and U1.18-P1-H2.3 4067 00B4 Bus tests detected MCM 2/VPD problem 1. Check for system firmware updates. 2. MCM module 2 and VPD card Location: U1.18-P1-C4 and U1.18-P1-H2.4 Eserver pSeries 690 Service Guide...
  • Page 575 Error Code Description Action/ Possible Failing FRU 4067 00B5 Bus tests detected MCM 1/VPD problem 1. Check for system firmware updates. 2. MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 4067 00B6 Bus tests detected MCM 3/VPD problem 1.
  • Page 576 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 577 Error Code Description Action/ Possible Failing FRU 4067 0A05 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 1 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 578 4067 0B02 Bus tests detected fault in I/O book (slot 0 RIO 1. Check for system firmware updates. port 2) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3. Primary I/O book Location: U1.18-P1-H2 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 579 Error Code Description Action/ Possible Failing FRU 4067 0B03 Bus tests detected fault in I/O book (slot 0 RIO 1. Check for system firmware updates. port 3) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3.
  • Page 580 4067 0B27 Bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 581 Error Code Description Action/ Possible Failing FRU 4067 0B30 Bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
  • Page 582 2. Replace the RIO book, Location: U1.18-P1-H1 4067 0BF3 Bus tests detected fault in I/O hub chip 3 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q1 b. U1.18-P1-H1/Q2 2. Replace the RIO book, Location: U1.18-P1-H1 Eserver pSeries 690 Service Guide...
  • Page 583 Error Code Description Action/ Possible Failing FRU 4067 0BF4 Bus tests detected fault in I/O hub chip 4 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H3/Q7 b. U1.18-P1-H3/Q8 2. Replace the RIO book, Location: U1.18-P1-H3 4067 0BF5 Bus tests detected fault in I/O hub chip 5 (port 1.
  • Page 584 L3 cache module 2 and L3 VPD card Location: U1.18-P1-C11 and U1.18-P1-H2.1 4067 0D03 Bus tests detected fault in L3 cache module 3 L3 cache module 3 and L3 VPD card Location: U1.18-P1-C10 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 585 Error Code Description Action/ Possible Failing FRU 4067 0D04 Bus tests detected fault in L3 cache module 4 L3 cache module 4 and L3 VPD card Location: U1.18-P1-C8 and U1.18-P1-H2.1 4067 0D05 Bus tests detected fault in L3 cache module 5 L3 cache module 5 and L3 VPD card Location: U1.18-P1-C20 and U1.18-P1-H2.1 4067 0D06 Bus tests detected fault in L3 cache module 6...
  • Page 586 If a CEC subsystem error (a 4xxx yyyy error) did not occur during the slow boot, look for a 4xxx yyyy error immediately preceding the 406x 0EBF error. Replace the part indicated by the location code associated with that error. Eserver pSeries 690 Service Guide...
  • Page 587 Error Code Description Action/ Possible Failing FRU 4067 0EE1 Bus tests detected fault in service processor 1. Check for system firmware updates. code (invalid MRU to mapping) 2. Call service support. 4067 0EE2 Bus tests detected fault in service processor 1.
  • Page 588 1. Check for system firmware updates. 2. MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 4068 00B7 Other bus tests detected hardware problem in Go to “MAP 1540: Problem Isolation the processor subsystem Procedures” on page 310. Eserver pSeries 690 Service Guide...
  • Page 589 Error Code Description Action/ Possible Failing FRU 4068 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware. If AIX is available on the system, go to MAP 0235 in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509.
  • Page 590 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 591 Error Code Description Action/ Possible Failing FRU 4068 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for Processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 592 4068 0B21 Other bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 593 Error Code Description Action/ Possible Failing FRU 4068 0B22 Other bus tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4.
  • Page 594 I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4. 3. Third I/O book or SNI adapter Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 595 Error Code Description Action/ Possible Failing FRU 4068 0B36 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book or SNI adapter 2. Check the I/O cabling between the third I/O book and the I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4.
  • Page 596 Location: U1.18-P1-H1 4068 0BFA Other bus tests detected fault in I/O hub chip 1. Check the cabling on the following RIO 10 (port x) ports: a. U1.18-P1-H3/Q3 b. U1.18-P1-H3/Q4 2. Replace the RIO book, Location: U1.18-P1-H3 Eserver pSeries 690 Service Guide...
  • Page 597 Error Code Description Action/ Possible Failing FRU 4068 0BFB Other bus tests detected fault in I/O hub chip 11 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H3/Q1 b. U1.18-P1-H3/Q2 2. Replace the RIO book, Location: U1.18-P1-H3 4068 0BFC Other bus tests detected fault in I/O hub chip 1.
  • Page 598 4068 0EA2 Other bus tests detected fault in PRD code on 1. Check for system firmware updates. service processor 2. Call service support. 4068 0EA4 The service processor firmware detected a Call service support. hardware problem but was unable to isolate the source. Eserver pSeries 690 Service Guide...
  • Page 599 Error Code Description Action/ Possible Failing FRU 4068 0EA5 PRD detected a problem in the FNM code 1. Check for system firmware updates. 2. Call service support. 4068 0EAA PRD: FNM is handling this error 1. Check for system firmware updates. 2.
  • Page 600 4069 0010 Memory tests detected fault in Memory book Memory book (slot 0) (slot 0) Location: U1.18-P1-M2 4069 0011 Memory tests detected fault in Memory book Memory book (slot 1) (slot 1) Location: U1.18-P1-M3 Eserver pSeries 690 Service Guide...
  • Page 601 Error Code Description Action/ Possible Failing FRU 4069 0012 Memory tests detected fault in Memory book Memory book (slot 2) (slot 2) Location: U1.18-P1-M7 4069 0013 Memory tests detected fault in Memory book Memory book (slot 3) (slot 3) Location: U1.18-P1-M6 4069 0014 Memory tests detected fault in Memory book Memory book (slot 4) (slot 4)
  • Page 602 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 603 Error Code Description Action/ Possible Failing FRU 4069 0A05 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 1 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 604 4069 0B02 Memory tests detected fault in I/O book (slot 0 1. Check for system firmware updates. RIO port 2) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3. Primary I/O book Location: U1.18-P1-H2 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 605 Error Code Description Action/ Possible Failing FRU 4069 0B03 Memory tests detected fault in I/O book (slot 0 1. Check for system firmware updates. RIO port 3) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3.
  • Page 606 4069 0B27 Memory tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 607 Error Code Description Action/ Possible Failing FRU 4069 0B30 Memory tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
  • Page 608 Location: U1.18-P1-H1 4069 0BF3 Memory tests detected fault in I/O hub chip 3 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H1/Q1 b. U1.18-P1-H1/Q2 2. Replace the RIO book, Location: U1.18-P1-H1 Eserver pSeries 690 Service Guide...
  • Page 609 Error Code Description Action/ Possible Failing FRU 4069 0BF4 Memory tests detected fault in I/O hub chip 4 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H3/Q7 b. U1.18-P1-H3/Q8 2. Replace the RIO book, Location: U1.18-P1-H3 4069 0BF5 Memory tests detected fault in I/O hub chip 5 1.
  • Page 610 L3 cache module 2 and L3 VPD card module 2 Location: U1.18-P1-C11 and U1.18-P1-H2.1 4069 0D03 Memory tests detected fault in L3 cache L3 cache module 3 and L3 VPD card module 3 Location: U1.18-P1-C10 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 611 Error Code Description Action/ Possible Failing FRU 4069 0D04 Memory tests detected fault in L3 cache L3 cache module 4 and L3 VPD card module 4 Location: U1.18-P1-C8 and U1.18-P1-H2.1 4069 0D05 Memory tests detected fault in L3 cache L3 cache module 5 and L3 VPD card module 5 Location: U1.18-P1-C20 and U1.18-P1-H2.1 4069 0D06 Memory tests detected fault in L3 cache...
  • Page 612 Procedures” on page 310. 4069 0EB4 Attention line 3 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 310. 4069 0EB5 Attention line 4 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 310. Eserver pSeries 690 Service Guide...
  • Page 613 Error Code Description Action/ Possible Failing FRU 4069 0EB6 Attention line 5 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 310. 4069 0EB7 Attention line 6 stuck fault Go to “MAP 1540: Problem Isolation Procedures” on page 310. 4069 0EB8 Attention line 7 stuck fault Go to “MAP 1540: Problem Isolation Procedures”...
  • Page 614 406A 0017 Self tests detected fault in Memory book (slot 7) Memory book (slot 7) Location: U1.18-P1-M1 406A 00B0 Self tests detected possible problem with bus 1. Check for system firmware updates. controller or CSP code 2. Primary I/O book, Location: U1.18-P1-H2 3. Call service support. Eserver pSeries 690 Service Guide...
  • Page 615 Error Code Description Action/ Possible Failing FRU 406A 00B1 Self tests detected possible problem with bus 1. Check for system firmware updates. controller 2. Primary I/O book, Location: U1.18-P1-H2 3. Call service support. 406A 00B3 Self tests detected MCM 0/VPD problem 1.
  • Page 616 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 617 Error Code Description Action/ Possible Failing FRU 406A 0A05 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 1 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 618 406A 0B02 Self-tests detected fault in I/O book (slot 0 RIO 1. Check for system firmware updates. port 2) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3. Primary I/O book Location: U1.18-P1-H2 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 619 Error Code Description Action/ Possible Failing FRU 406A 0B03 Self-tests detected fault in I/O book (slot 0 RIO 1. Check for system firmware updates. port 3) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3.
  • Page 620 406A 0B27 Self-tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 621 Error Code Description Action/ Possible Failing FRU 406A 0B30 Self-tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
  • Page 622 2. Replace the RIO book, Location: U1.18-P1-H1 406A 0BF3 Self-tests detected fault in I/O hub chip 3 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q1 b. U1.18-P1-H1/Q2 2. Replace the RIO book, Location: U1.18-P1-H1 Eserver pSeries 690 Service Guide...
  • Page 623 Error Code Description Action/ Possible Failing FRU 406A 0BF4 Self-tests detected fault in I/O hub chip 4 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H3/Q7 b. U1.18-P1-H3/Q8 2. Replace the RIO book, Location: U1.18-P1-H3 406A 0BF5 Self-tests detected fault in I/O hub chip 5 (port 1.
  • Page 624 406A 0D02 Self-tests detected fault in L3 cache module 2 L3 cache module 2 and L3 VPD card Location: U1.18-P1-C11 and U1.18-P1-H2.1 406A 0D03 Self-tests detected fault in L3 cache module 3 L3 cache module 3 and L3 VPD card Location: U1.18-P1-C10 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 625 Error Code Description Action/ Possible Failing FRU 406A 0D04 Self-tests detected fault in L3 cache module 4 L3 cache module 4 and L3 VPD card Location: U1.18-P1-C8 and U1.18-P1-H2.1 406A 0D05 Self-tests detected fault in L3 cache module 5 L3 cache module 5 and L3 VPD card Location: U1.18-P1-C20 and U1.18-P1-H2.1 406A 0D06 Self-tests detected fault in L3 cache module 6 L3 cache module 6 and L3 VPD card...
  • Page 626 If a CEC subsystem error (a 4xxx yyyy error) did not occur during the slow boot, look for a 4xxx yyyy error immediately preceding the 406x 0EBF error. Replace the part indicated by the location code associated with that error. Eserver pSeries 690 Service Guide...
  • Page 627 Error Code Description Action/ Possible Failing FRU 406A 0EE1 Self-tests detected fault in service processor 1. Check for system firmware updates. code (invalid MRU to mapping) 2. Call service support. 406A 0EE2 Self-tests detected fault in service processor 1. Check for system firmware updates. firmware fault 2.
  • Page 628 1. Check for system firmware updates. 2. MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 406B 00B7 Wire tests detected hardware problem in the Go to “MAP 1540: Problem Isolation processor subsystem Procedures” on page 310. Eserver pSeries 690 Service Guide...
  • Page 629 Error Code Description Action/ Possible Failing FRU 406B 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware. If AIX is available on the system, go to MAP 0235 in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509.
  • Page 630 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 631 Error Code Description Action/ Possible Failing FRU 406B 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 632 406B 0B21 Wire tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 633 Error Code Description Action/ Possible Failing FRU 406B 0B22 Wire tests detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4.
  • Page 634 I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4. 3. Third I/O book or SNI adapter Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 635 Error Code Description Action/ Possible Failing FRU 406B 0B36 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book or SNI adapter 2. Check the I/O cabling between the third I/O book and the I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4.
  • Page 636 Location: U1.18-P1-H1 406B 0BFA Wire tests detected fault in I/O hub chip 10 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H3/Q3 b. U1.18-P1-H3/Q4 2. Replace the RIO book, Location: U1.18-P1-H3 Eserver pSeries 690 Service Guide...
  • Page 637 Error Code Description Action/ Possible Failing FRU 406B 0BFB Wire tests detected fault in I/O hub chip 11 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H3/Q1 b. U1.18-P1-H3/Q2 2. Replace the RIO book, Location: U1.18-P1-H3 406B 0BFC Wire tests detected fault in I/O hub chip 12 1.
  • Page 638 406B 0EA2 Wire tests detected fault in PRD code on 1. Check for system firmware updates. service processor 2. Call service support. 406B 0EA4 The service processor firmware detected a Call service support. hardware problem but was unable to isolate the source. Eserver pSeries 690 Service Guide...
  • Page 639 Error Code Description Action/ Possible Failing FRU 406B 0EA5 PRD detected a problem in the FNM code 1. Check for system firmware updates. 2. Call service support. 406B 0EAA PRD: FNM is handling this error 1. Check for system firmware updates. 2.
  • Page 640 2. Ask the customer to reenter the CUoD activation keys. 406C 0010 IPL detected fault in Memory book (slot 0) Memory book (slot 0) Location: U1.18-P1-M2 406C 0011 IPL detected fault in Memory book (slot 1) Memory book (slot 1) Location: U1.18-P1-M3 Eserver pSeries 690 Service Guide...
  • Page 641 Error Code Description Action/ Possible Failing FRU 406C 0012 IPL detected fault in Memory book (slot 2) Memory book (slot 2) Location: U1.18-P1-M7 406C 0013 IPL detected fault in Memory book (slot 3) Memory book (slot 3) Location: U1.18-P1-M6 406C 0014 IPL detected fault in Memory book (slot 4) Memory book (slot 4) Location: U1.18-P1-M4 406C 0015 IPL detected fault in Memory book (slot 5)
  • Page 642 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 643 Error Code Description Action/ Possible Failing FRU 406C 0A05 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 1 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 644 406C 0B02 IPL detected fault in I/O book (slot 0 RIO port 1. Check for system firmware updates. 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3. Primary I/O book Location: U1.18-P1-H2 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 645 Error Code Description Action/ Possible Failing FRU 406C 0B03 IPL detected fault in I/O book (slot 0 RIO port 1. Check for system firmware updates. 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3. Primary I/O book Location: U1.18-P1-H2 4.
  • Page 646 406C 0B27 IPL detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 647 Error Code Description Action/ Possible Failing FRU 406C 0B30 IPL detected fault in I/O book I/O book (slot 3 RIO port 0) Location: U1.18-P1-H4/Q1 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3.
  • Page 648 2. Replace the RIO book, Location: U1.18-P1-H1 406C 0BF3 IPL detected fault in I/O hub chip 3 (port x) 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q1 b. U1.18-P1-H1/Q2 2. Replace the RIO book, Location: U1.18-P1-H1 Eserver pSeries 690 Service Guide...
  • Page 649 Error Code Description Action/ Possible Failing FRU 406C 0BF4 IPL detected fault in I/O hub chip 4 (port x) 1. Check the cabling on the following RIO ports: a. U1.18-P1-H3/Q7 b. U1.18-P1-H3/Q8 2. Replace the RIO book, Location: U1.18-P1-H3 406C 0BF5 IPL detected fault in I/O hub chip 5 (port x) 1.
  • Page 650 406C 0D02 IPL detected fault in L3 cache module 2 L3 cache module 2 and L3 VPD card Location: U1.18-P1-C11 and U1.18-P1-H2.1 406C 0D03 IPL detected fault in L3 cache module 3 L3 cache module 3 and L3 VPD card Location: U1.18-P1-C10 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 651 Error Code Description Action/ Possible Failing FRU 406C 0D04 IPL detected fault in L3 cache module 4 L3 cache module 4 and L3 VPD card Location: U1.18-P1-C8 and U1.18-P1-H2.1 406C 0D05 IPL detected fault in L3 cache module 5 L3 cache module 5 and L3 VPD card Location: U1.18-P1-C20 and U1.18-P1-H2.1 406C 0D06 IPL detected fault in L3 cache module 6 L3 cache module 6 and L3 VPD card...
  • Page 652 If a CEC subsystem error (a 4xxx yyyy error) did not occur during the slow boot, look for a 4xxx yyyy error immediately preceding the 406x 0EBF error. Replace the part indicated by the location code associated with that error. Eserver pSeries 690 Service Guide...
  • Page 653 Error Code Description Action/ Possible Failing FRU 406C 0EE1 IPL detected fault in service processor code 1. Check for system firmware updates. (invalid MRU to mapping) 2. Call service support. 406C 0EE2 IPL detected fault in service processor firmware 1. Check for system firmware updates. fault 2.
  • Page 654 1. Check for system firmware updates. problem 2. MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 406D 00B7 Attention handler detected hardware problem in Go to “MAP 1540: Problem Isolation the processor subsystem Procedures” on page 310. Eserver pSeries 690 Service Guide...
  • Page 655 Error Code Description Action/ Possible Failing FRU 406D 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware. If AIX is available on the system, go to MAP 0235 in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509.
  • Page 656 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 657 Error Code Description Action/ Possible Failing FRU 406D 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 658 406D 0B21 Attention handler detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 659 Error Code Description Action/ Possible Failing FRU 406D 0B22 Attention handler detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4.
  • Page 660 I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4. 3. Third I/O book or SNI adapter Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 661 Error Code Description Action/ Possible Failing FRU 406D 0B36 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book or SNI adapter 2. Check the I/O cabling between the third I/O book and the I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4.
  • Page 662 Location: U1.18-P1-H1 406D 0BFA Attention handler detected fault in I/O hub chip 1. Check the cabling on the following RIO 10 (port x) ports: a. U1.18-P1-H3/Q3 b. U1.18-P1-H3/Q4 2. Replace the RIO book, Location: U1.18-P1-H3 Eserver pSeries 690 Service Guide...
  • Page 663 Error Code Description Action/ Possible Failing FRU 406D 0BFB Attention handler detected fault in I/O hub chip 1. Check the cabling on the following RIO 11 (port x) ports: a. U1.18-P1-H3/Q1 b. U1.18-P1-H3/Q2 2. Replace the RIO book, Location: U1.18-P1-H3 406D 0BFC Attention handler detected fault in I/O hub chip 1.
  • Page 664 406D 0EA2 Attention handler detected fault in PRD code on 1. Check for system firmware updates. service processor 2. Call service support. 406D 0EA4 The service processor firmware detected a Call service support. hardware problem but was unable to isolate the source. Eserver pSeries 690 Service Guide...
  • Page 665 Error Code Description Action/ Possible Failing FRU 406D 0EA5 PRD detected a problem in the FNM code 1. Check for system firmware updates. 2. Call service support. 406D 0EAA PRD: FNM is handling this error 1. Check for system firmware updates. 2.
  • Page 666 406E 0010 Scan control routines detected fault in Memory Memory book (slot 0) book (slot 0) Location: U1.18-P1-M2 406E 0011 Scan control routines detected fault in Memory Memory book (slot 1) book (slot 1) Location: U1.18-P1-M3 Eserver pSeries 690 Service Guide...
  • Page 667 Error Code Description Action/ Possible Failing FRU 406E 0012 Scan control routines detected fault in Memory Memory book (slot 2) book (slot 2) Location: U1.18-P1-M7 406E 0013 Scan control routines detected fault in Memory Memory book (slot 3) book (slot 3) Location: U1.18-P1-M6 406E 0014 Scan control routines detected fault in Memory Memory book (slot 4)
  • Page 668 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 669 Error Code Description Action/ Possible Failing FRU 406E 0A05 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 1 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 670 1. Check for system firmware updates. (slot 0 RIO port 2) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3. Primary I/O book Location: U1.18-P1-H2 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 671 Error Code Description Action/ Possible Failing FRU 406E 0B03 Scan control routines detected fault in I/O book 1. Check for system firmware updates. (slot 0 RIO port 3) 2. Check the I/O cabling between the primary I/O book and the I/O subsystems. 3.
  • Page 672 406E 0B27 Scan control routines detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 673 Error Code Description Action/ Possible Failing FRU 406E 0B30 Scan control routines detected fault in I/O book 1. Check for system firmware updates. 2. Check the I/O cabling between the third I/O book and the I/O subsystems. 3. Third I/O book Location: U1.18-P1-H4 4.
  • Page 674 Location: U1.18-P1-H1 406E 0BF3 Scan control routines detected fault in I/O hub 1. Check the cabling on the following RIO chip 3 (port x) ports: a. U1.18-P1-H1/Q1 b. U1.18-P1-H1/Q2 2. Replace the RIO book, Location: U1.18-P1-H1 Eserver pSeries 690 Service Guide...
  • Page 675 Error Code Description Action/ Possible Failing FRU 406E 0BF4 Scan control routines detected fault in I/O hub 1. Check the cabling on the following RIO chip 4 (port x) ports: a. U1.18-P1-H3/Q7 b. U1.18-P1-H3/Q8 2. Replace the RIO book, Location: U1.18-P1-H3 406E 0BF5 Scan control routines detected fault in I/O hub 1.
  • Page 676 L3 cache module 2 and L3 VPD card module 2 Location: U1.18-P1-C11 and U1.18-P1-H2.1 406E 0D03 Scan control routines detected fault in L3 cache L3 cache module 3 and L3 VPD card module 3 Location: U1.18-P1-C10 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 677 Error Code Description Action/ Possible Failing FRU 406E 0D04 Scan control routines detected fault in L3 cache L3 cache module 4 and L3 VPD card module 4 Location: U1.18-P1-C8 and U1.18-P1-H2.1 406E 0D05 Scan control routines detected fault in L3 cache L3 cache module 5 and L3 VPD card module 5 Location: U1.18-P1-C20 and U1.18-P1-H2.1...
  • Page 678 If a CEC subsystem error (a 4xxx yyyy error) did not occur during the slow boot, look for a 4xxx yyyy error immediately preceding the 406x 0EBF error. Replace the part indicated by the location code associated with that error. Eserver pSeries 690 Service Guide...
  • Page 679 Error Code Description Action/ Possible Failing FRU 406E 0EE1 Scan control routines detected fault in service 1. Check for system firmware updates. processor code (invalid MRU to mapping) 2. Call service support. 406E 0EE2 Scan control routines detected fault in service 1.
  • Page 680 3/VPD problem 2. MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 406F 00B7 Error code generation/logging detected Go to “MAP 1540: Problem Isolation hardware problem in the processor subsystem Procedures” on page 310. Eserver pSeries 690 Service Guide...
  • Page 681 Error Code Description Action/ Possible Failing FRU 406F 0A03 Reboot message (run-time array gard failure) Array bit steering, which is a function in the for processor 0 firmware, may be able to correct this problem without replacing hardware. If AIX is available on the system, go to MAP 0235 in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems, order number SA38-0509.
  • Page 682 (devices with a resource name of procx), array bit steering was successful and the problem has been corrected. If errors are reported against the hardware, follow the actions for the error code or SRN. Eserver pSeries 690 Service Guide...
  • Page 683 Error Code Description Action/ Possible Failing FRU 406F 0A06 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 3 diagnostics, then go to MAP 0235 in the .Array bit steering, which is a function in the firmware, may be able to correct this problem without replacing hardware.
  • Page 684 406F 0B21 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 685 Error Code Description Action/ Possible Failing FRU 406F 0B22 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book 2. Check the I/O cabling between the secondary I/O book and the I/O subsystems. 3. Secondary I/O book Location: U1.18-P1-H3 4.
  • Page 686 I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4. 3. Third I/O book or SNI adapter Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 687 Error Code Description Action/ Possible Failing FRU 406F 0B36 Error code generation/logging detected fault in 1. Check for system firmware updates. I/O book or SNI adapter 2. Check the I/O cabling between the third I/O book and the I/O subsystems, or the SNI adapter and the High Performance Switch, depending on which adapter is installed in location U1.18-P1-H4.
  • Page 688 Location: U1.18-P1-H1 406F 0BFA Error code generation/logging detected fault in 1. Check the cabling on the following RIO I/O hub chip 10 (port x) ports: a. U1.18-P1-H3/Q3 b. U1.18-P1-H3/Q4 2. Replace the RIO book, Location: U1.18-P1-H3 Eserver pSeries 690 Service Guide...
  • Page 689 Error Code Description Action/ Possible Failing FRU 406F 0BFB Error code generation/logging detected fault in 1. Check the cabling on the following RIO I/O hub chip 11 (port x) ports: a. U1.18-P1-H3/Q1 b. U1.18-P1-H3/Q2 2. Replace the RIO book, Location: U1.18-P1-H3 406F 0BFC Error code generation/logging detected fault in 1.
  • Page 690 1. Check for system firmware updates. PRD code on service processor 2. Call service support. 406F 0EA4 The service processor firmware detected a Call service support. hardware problem but was unable to isolate the source. Eserver pSeries 690 Service Guide...
  • Page 691 Error Code Description Action/ Possible Failing FRU 406F 0EA5 PRD detected a problem in the FNM code 1. Check for system firmware updates. 2. Call service support. 406F 0EAA PRD: FNM is handling this error 1. Check for system firmware updates. 2.
  • Page 692 4503 269A This error code indicates that the memory Replace the L3 cache module indicated by the repeat gard function has deconfigured an L3 location code reported with the error code, and cache module. the L3 VPD card, location: U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 693 Error Code Description Action/ Possible Failing FRU 4503 302A This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
  • Page 694 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 695 Error Code Description Action/ Possible Failing FRU 4503 305A This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
  • Page 696 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 697 Error Code Description Action/ Possible Failing FRU 4503 305E This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
  • Page 698 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 699 Error Code Description Action/ Possible Failing FRU 4503 307C This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
  • Page 700 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 701 Error Code Description Action/ Possible Failing FRU 4503 308B This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
  • Page 702 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 703 Error Code Description Action/ Possible Failing FRU 4503 30BD This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
  • Page 704 If any of the books have a status of ″deconfigured by the system″, either before or after the boot to the SMS menus, go to step 2. 2. Replace the memory book specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 705 Error Code Description Action/ Possible Failing FRU 4503 30C6 This error code indicates that the memory Do the following: repeat gard function has deconfigured or 1. Go to the memory partially deconfigured a memory book. configuration/deconfiguration menu, which is under the system information menu in the service processor menus.
  • Page 706 Problem Isolation” on page 352. 1.1 GHz MCM and 1.3 GHz MCM 4504 25E7 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 352. Eserver pSeries 690 Service Guide...
  • Page 707 Error Code Description Action/ Possible Failing FRU 4504 25E8 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 352. 4504 25F1 Memory subsystem and processor subsystem Go to “MAP 1548: Memory and Processor tests detected fault in L3 VPD card used with Problem Isolation”...
  • Page 708 4505 25C0 Memory subsystem and display alter tests System backplane detected fault in system backplane Location: U1.18-P1 4505 25C1 Memory subsystem and display alter tests Clock card detected fault in 1.0 GHz clock card Location: U1.18-P1-X5 Eserver pSeries 690 Service Guide...
  • Page 709 Error Code Description Action/ Possible Failing FRU 4505 25D9 Memory subsystem and display alter tests Go to “MAP 1548: Memory and Processor detected fault in L3 VPD card used with 1.1 Problem Isolation” on page 352. GHz MCM and 1.3 GHz MCM 4505 25E7 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs...
  • Page 710 Problem Isolation” on page 352. 4506 25F1 Memory subsystem and scan interface basic Go to “MAP 1548: Memory and Processor assurance tests detected fault in L3 VPD card Problem Isolation” on page 352. used with 1.3 GHz MCM Eserver pSeries 690 Service Guide...
  • Page 711 Error Code Description Action/ Possible Failing FRU 4506 25F9 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 352. 4506 269A Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation”...
  • Page 712 I/O subsystem PCI backplane at location in I/O subsystem PCI backplane specified in error code 4507 28B1 Memory subsystem and bus tests detected fault I/O subsystem DASD backplane at location in I/O subsystem DASD backplane specified in error code Eserver pSeries 690 Service Guide...
  • Page 713 Error Code Description Action/ Possible Failing FRU 4507 302A Memory subsystem and bus tests detected fault Go to “MAP 1540: Problem Isolation in 8 GB memory book (inner) Procedures” on page 310 to isolate the failing component. 4507 302B Memory subsystem and bus tests detected fault Go to “MAP 1540: Problem Isolation in 8 GB memory book (outer) Procedures”...
  • Page 714 Procedures” on page 310 to isolate the failing component. 4508 302D Memory subsystem and other bus tests Go to “MAP 1540: Problem Isolation detected fault in 32 GB memory book (outer) Procedures” on page 310 to isolate the failing component. Eserver pSeries 690 Service Guide...
  • Page 715 Error Code Description Action/ Possible Failing FRU 4508 305A Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 8 GB memory book Isolation” on page 342. (inner) 4508 305B Memory subsystem and processor subsystem Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 8 GB memory book Isolation”...
  • Page 716 16 GB inner memory book Isolation” on page 342. 4509 305F Memory subsystem and memory tests detected Go to “MAP 1545: Outer L3 Module Problem fault in 16 GB outer memory book Isolation” on page 344. Eserver pSeries 690 Service Guide...
  • Page 717 Error Code Description Action/ Possible Failing FRU 4509 307A Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 4 GB inner memory book Isolation” on page 342. 4509 307B Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 8 GB inner memory book Isolation”...
  • Page 718 16 GB inner memory Isolation” on page 342. book 450A 307E Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 16 GB inner memory Isolation” on page 342. book Eserver pSeries 690 Service Guide...
  • Page 719 Error Code Description Action/ Possible Failing FRU 450A 308A Memory subsystem and processor subsystem Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 4 GB outer memory book Isolation” on page 344. 450A 308B Memory subsystem and processor subsystem Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 4 GB outer memory book Isolation”...
  • Page 720 Isolation” on page 344. 450B 30BD Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 8 GB or 16 GB CUoD Isolation” on page 342. inner memory book Eserver pSeries 690 Service Guide...
  • Page 721 Error Code Description Action/ Possible Failing FRU 450B 30C3 Memory subsystem and processor subsystem Go to “MAP 1544: Inner L3 Module Problem tests detected fault in 32 GB or 64 GB CUoD Isolation” on page 342. inner memory book 450B 30C6 Memory subsystem and processor subsystem Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 8 GB or 16 GB CUoD Isolation”...
  • Page 722 Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 32 GB or 64 GB CUoD Isolation” on page 344. outer memory book 450D 248B Memory subsystem and attention handler Operator panel detected fault in operator panel Location: U1.17-L1 Eserver pSeries 690 Service Guide...
  • Page 723 Error Code Description Action/ Possible Failing FRU 450D 25C0 Memory subsystem and attention handler System backplane detected fault in system backplane Location: U1.18-P1 450D 25C1 Memory subsystem and attention handler Clock card detected fault in 1.0 GHz clock card Location: U1.18-P1-X5 450D 25D9 Memory subsystem and attention handler Go to “MAP 1548: Memory and Processor detected fault in L3 VPD card used with 1.1...
  • Page 724 1.7 GHz MCMs Problem Isolation” on page 352. 450E 25E8 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 352. Eserver pSeries 690 Service Guide...
  • Page 725 Error Code Description Action/ Possible Failing FRU 450E 25F1 Memory subsystem and scan control routines Go to “MAP 1548: Memory and Processor detected fault in L3 VPD card used with 1.3 Problem Isolation” on page 352. GHz MCM 450E 25F9 Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation”...
  • Page 726 1.7 GHz MCMs Problem Isolation” on page 352. 450F 269A Fault in L3 VPD card used with 1.5 GHz and Go to “MAP 1548: Memory and Processor 1.7 GHz MCMs Problem Isolation” on page 352. Eserver pSeries 690 Service Guide...
  • Page 727 Error Code Description Action/ Possible Failing FRU 450F 28B0 Memory subsystem and error code I/O subsystem PCI backplane at location generation/logging detected fault in I/O specified in error code subsystem PCI backplane 450F 28B1 Memory subsystem and error code I/O subsystem DASD backplane at location generation/logging detected fault in I/O specified in error code subsystem DASD backplane...
  • Page 728 I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books. 2. Replace I/O book 1, 3, or 4 at location specified in error code. Eserver pSeries 690 Service Guide...
  • Page 729 Error Code Description Action/ Possible Failing FRU 4604 2806 I/O subsystem and processor subsystem tests 1. If word 13 is CFF1 xxxx, a configuration detected fault in I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books.
  • Page 730 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. Eserver pSeries 690 Service Guide...
  • Page 731 Error Code Description Action/ Possible Failing FRU 4605 527C CUoD capacity card fault 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys.
  • Page 732 Primary I/O book - Slot 0 detected fault in primary I/O book - Slot 0 Location: U1.18-P1-H2 4607 273F SMA 2-port switch adapter fault Replace the I/O book (switch adapter) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 733 Error Code Description Action/ Possible Failing FRU 4607 2776 I/O subsystem and processor subsystem tests 1. If word 13 is CFF1 xxxx, a configuration detected fault in I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books.
  • Page 734 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. Eserver pSeries 690 Service Guide...
  • Page 735 Error Code Description Action/ Possible Failing FRU 4608 527A CUoD capacity card fault 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys.
  • Page 736 Primary I/O book - Slot 0 detected fault in primary I/O book - Slot 0 Location: U1.18-P1-H2 460A 273F SMA 2-port switch adapter fault Replace the I/O book (switch adapter) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 737 Error Code Description Action/ Possible Failing FRU 460A 2776 I/O subsystem and processor subsystem tests 1. If word 13 is CFF1 xxxx, a configuration detected fault in I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books.
  • Page 738 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. Eserver pSeries 690 Service Guide...
  • Page 739 Error Code Description Action/ Possible Failing FRU 460B 527A CUoD capacity card fault 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys.
  • Page 740 Primary I/O book - Slot 0 detected fault in primary I/O book - Slot 0 Location: U1.18-P1-H2 460D 273F SMA 2-port switch adapter fault Replace the I/O book (switch adapter) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 741 Error Code Description Action/ Possible Failing FRU 460D 2776 I/O subsystem and processor subsystem tests 1. If word 13 is CFF1 xxxx, a configuration detected fault in I/O book 1, 3, or 4 problem exists. Ensure that the number of MCMs is consistent with the number of I/O books.
  • Page 742 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. Eserver pSeries 690 Service Guide...
  • Page 743 Error Code Description Action/ Possible Failing FRU 460E 527A CUoD capacity card fault 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys.
  • Page 744 1. Verify that the system firmware is RH021114 or later. CUoD is not supported by the earlier firmware levels. 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. Eserver pSeries 690 Service Guide...
  • Page 745 Error Code Description Action/ Possible Failing FRU 4B23 258A The processor repeat gard function has Do the following: deconfigured a processor. 1. Go to the processor configuration/deconfiguration menu, which is under the system information menu in the service processor menus. Look at the status of the processors.
  • Page 746 If any of the processors have a status of ″deconfigured by the system,″ either before or after the boot to the SMS menus, replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 747 Error Code Description Action/ Possible Failing FRU 4B23 25D3 The processor repeat gard function has Do the following: deconfigured a processor. 1. Go to the processor configuration/deconfiguration menu, which is under the system information menu in the service processor menus. Look at the status of the processors.
  • Page 748 If any of the processors have a status of ″deconfigured by the system,″ either before or after the boot to the SMS menus, replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 749 Error Code Description Action/ Possible Failing FRU 4B23 25E5 The processor repeat gard function has Do the following: deconfigured a processor. 1. Go to the processor configuration/deconfiguration menu, which is under the system information menu in the service processor menus. Look at the status of the processors.
  • Page 750 If any of the processors have a status of ″deconfigured by the system,″ either before or after the boot to the SMS menus, replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 751 Error Code Description Action/ Possible Failing FRU 4B23 526D The processor repeat gard function has Do the following: deconfigured a processor. 1. Go to the processor configuration/deconfiguration menu, which is under the system information menu in the service processor menus. Look at the status of the processors.
  • Page 752 4B25 25C0 Processor subsystem and display alter tests System backplane detected fault in system backplane Location: U1.18-P1 4B25 25C1 Processor subsystem and display alter tests Clock card detected fault in 1.0 GHz clock card Location: U1.18-P1-X5 Eserver pSeries 690 Service Guide...
  • Page 753 Error Code Description Action/ Possible Failing FRU 4B25 25C7 Processor subsystem and display alter tests Go to “MAP 1540: Problem Isolation detected fault in 4-way processor MCM Procedures” on page 310 to isolate the failing component. 4B25 25C8 Processor subsystem and display alter tests Go to “MAP 1540: Problem Isolation detected fault in 4-way processor MCM Procedures”...
  • Page 754 Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. 4B26 526D Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. Eserver pSeries 690 Service Guide...
  • Page 755 Error Code Description Action/ Possible Failing FRU 4B26 526E Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. 4B27 248B Processor subsystem and bus tests detected Operator panel fault in operator panel Location: U1.17-L1...
  • Page 756 I/O subsystem DASD specified in error code backplane 4B28 526B Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. Eserver pSeries 690 Service Guide...
  • Page 757 Error Code Description Action/ Possible Failing FRU 4B28 526C Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. 4B28 526D Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures”...
  • Page 758 MCM Procedures” on page 310 to isolate the failing component. 4B2A 28B0 Processor subsystem and self test detected I/O subsystem PCI backplane at location fault in I/O subsystem PCI backplane specified in error code Eserver pSeries 690 Service Guide...
  • Page 759 Error Code Description Action/ Possible Failing FRU 4B2A 28B1 Processor subsystem and self test detected I/O subsystem DASD backplane at location fault in I/O subsystem DASD backplane specified in error code 4B2A 526B Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures”...
  • Page 760 Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. 4B2C 25E5 Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 310 to isolate the failing component. Eserver pSeries 690 Service Guide...
  • Page 761 Error Code Description Action/ Possible Failing FRU 4B2C 25E9 Processor subsystem detected fault in 8-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 310 to isolate the failing component. 4B2C 28B0 Processor subsystem and IPL detected fault in I/O subsystem PCI backplane at location I/O subsystem PCI backplane specified in error code...
  • Page 762 Procedures” on page 310 to isolate the failing VPD card (8-, 16-, or 24-way) component. 4B2E 25D7 Fault in 4-way processor MCM detected Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. Eserver pSeries 690 Service Guide...
  • Page 763 Error Code Description Action/ Possible Failing FRU 4B2E 25D8 Fault in 4-way processor MCM detected Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. 4B2E 25E5 Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures”...
  • Page 764 Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. 4B2F 526E Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 310 to isolate the failing component. Eserver pSeries 690 Service Guide...

  • Page 765: System Firmware Update Messages

    System Firmware Update Messages Error Code Description Action/ Possible Failing FRU A1FD 0000 Firmware update recovery mode entered Informational message A1FD 0001 Service processor flash recovery Insert Diskette #1 A1FD 0002 Service processor flash recovery Insert Diskette #2 A1FD 0003 Service processor flash recovery Insert Diskette #3 A1FD 0004 Service processor flash recovery Insert Diskette #4...

  • Page 766: Common Firmware Error Codes

    Location: U1.18-P1-H2 B10F 1008 Service processor failure Primary I/O book Location: U1.18-P1-H2 B10F 100E Service processor boot flash damaged Primary I/O book Location: U1.18-P1-H2 B10F 100F Service processor base flash damaged Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 690 Service Guide...
  • Page 767 Error Code Description Action/ Possible Failing FRU B10F 1300 Service processor failure Primary I/O book Location: U1.18-P1-H2 B10F 1370 Service processor flash update failure Primary I/O book Location: U1.18-P1-H2 B10F 1380 Service processor program failure Primary I/O book Location: U1.18-P1-H2 B10F 1381 Service processor flash error Primary I/O book Location: U1.18-P1-H2...
  • Page 768 For all other values of word 11 and word 13: 1. Check for system firmware updates. Apply if available. Call service support. B1xx 4606 Firmware failure 1. Check for system firmware updates. 2. Operator panel Location: U1.17-L1 Eserver pSeries 690 Service Guide...
  • Page 769 Error Code Description Action/ Possible Failing FRU B1xx 4608 Service processor early termination 1. Reset the system by removing, then reapplying power to the processor subsystem. 2. Reflash system firmware. 3. Primary I/O book Location: U1.18-P1-H2 B1xx 460A Time-of-day clock has been reset 1.
  • Page 770 A bad power subsystem code LID was found in the firmware image; the FRU firmware update terminates. This is logged in the AIX error log as a sysplanar0 error. Actions: Contact service support. Error code B1xx 4633 continues on to the next row. Eserver pSeries 690 Service Guide...
  • Page 771 Error Code Description Action/ Possible Failing FRU B1xx 4633 Continued from previous row. Cont’d A716: The power subsystem FRU code update was interrupted due to the system being shut down or turned off because of a critical power problem; the FRU firmware update terminates.
  • Page 772 B1xx 4682 Problem with VPD on operator panel 1. Replace the operator panel, Location: U1.17-L1 Do not swap the old VPD module onto the new op panel. Call service support for instructions on programming the new VPD module. 2. Call service support. Eserver pSeries 690 Service Guide...
  • Page 773 Error Code Description Action/ Possible Failing FRU B1xx 4683 Capacity Upgrade on Demand (CUoD) card fault Action: This error code may be informational, or it may indicate a failure of the CUoD capacity card. Before changing any parts, examine word 13 in the service processor error log entry, or bytes 68 and 69 in the AIX error log entry.
  • Page 774 B1xx 4695 System power control network (SPCN) to 1. Check for system firmware updates. service processor interface failure 2. Primary I/O book Location: U1.18-P1-H2 B1xx 4696 System firmware interface failure 1. Check for system firmware updates. 2. Call service support. Eserver pSeries 690 Service Guide...
  • Page 775 Error Code Description Action/ Possible Failing FRU B1xx 4698 Service processor firmware error This is usually an indication that the interposer plug count has not been set after an MES upgrade or FRU replacement of an MCM or L3 cache module. It can also indicate that the plug count values were not revalidated after the primary I/O book was replaced.
  • Page 776 For complete information regarding this error code, read through or informational message. this entire section. This is usually an indication of a problem in the communication path between the HMC and the service processor. It may only be an informational message. Eserver pSeries 690 Service Guide...
  • Page 777 If the managed server is down, go to the service processor error log and find the error log entry containing B1xx 4699. Examine the first two bytes of word 13 of the detailed entry information. If the managed server is running, examine the AIX error log entry containing B1xx 4699. This is a ″SCAN_ERROR_CHRP″...
  • Page 778 2. Check for a later level of firmware than the one that you were trying to install. Apply if available. 3. Call service support. 9903: State sequence error found after a firmware update LID was received during firmware update. Eserver pSeries 690 Service Guide...
  • Page 779 1. Check for a system firmware update that is later than the one that caused this error. Apply if available. 2. Call service support. 9920: Error occurred during model upgrade from a pSeries 670 (7040 model 671) to a pSeries 690 (7040 model 681). Actions: 1.
  • Page 780 2. From the service processor main menu, enter code 88484 to access the hidden menu. 3. Press enter again at ″IBM Authorized Use Only″ screen. 4. When the CUoD menu appears, the status of ″Test and Run″ should be Available.
  • Page 781 68 and 69 in the AIX error log entry is C1A4, this indicates a capacity on demand (CoD) transaction has taken place. For more detail about CUoD and CoD transactions, see the IBM Hardware Management Console for pSeries Installation and Operations Guide, order number SA38-0590.
  • Page 782 An informational log entry is made each time an on/off CoD activation code is entered. v Word 16 value (first 2 bytes): 0400 v Word 17 value (first 2 bytes): The number of processors days purchased. Eserver pSeries 690 Service Guide...
  • Page 783 v Word 17 value (second 2 bytes): The total number of activated processors of this type. This includes those previously activated plus those activated with this transaction. v Word 18 value (first 2 bytes): The current value of the processor day counter. It includes the processor days just added with this transaction.
  • Page 784 Word 18 value (second 2 bytes): The current value of the hours remaining in the current period counter. SPCN Informational Codes The following values of word 13 indicate an SPCN informational message: C006, C007, C00C, C030, C0E0, C0E2, C0F0, C0F1. No action is required by the customer or service representative. Eserver pSeries 690 Service Guide...

  • Page 785: Hmc Surveillance Error Codes

    HMC and the partitions, ensure that the short host names are set up correctly according to the instructions in ″Using Network Adapters to Communicate with Partitions″ in the IBM Hardware Management Console for pSeries Installation and Operations Guide. Correct any problems that are found, then verify that you can ping in both directions between the HMC and partitions.

  • Page 786: Problem Determination-Generated Error Codes

    Go to “MAP 1542: I/O Problem Isolation” on error code is generated by the customer page 320. performing “Problem Determination” as described in the Eserver pSeries 690 User’s Guide. M0BT 0001 The system hung during “Starting Software...”. Go to “MAP 1542: I/O Problem Isolation” on This error code is generated by the customer page 320.

  • Page 787: Hypervisor Dump Retrieval Procedure

    “Problem page 320. Determination” as described in the Eserver pSeries 690 User’s Guide. Hypervisor Dump Retrieval Procedure This procedure defines the requirements and methods for retrieving a hypervisor dump file following a system crash. This procedure is applicable only if the managed system had been running as a partitioned system before it crashed.
  • Page 788 DD is the current day, and YY is the current year. Forward the /tmp/dumpMMDDYY file to service support. If the following text displays on the AIX console, note the error and report it to service support: Retrieving Dump File Error performing dump read Eserver pSeries 690 Service Guide...

  • Page 789: Chapter 6. Using The Online And Standalone Diagnostics

    Chapter 6. Using the Online and Standalone Diagnostics The AIX diagnostics consist of online diagnostics and standalone diagnostics. Attention: The AIX operating system must be installed in a partition in order to run online diagnostics on that partition. If the AIX operating system is not installed, use the standalone diagnostic procedures. Online diagnostics, when they are installed, reside with AIX in the file system.

  • Page 790: Online Diagnostics Modes Of Operation

    The diagnostics cannot be loaded on a system (client) from a server if that system is not set up to boot from a server over a network. When the system is set up to boot from a server, the diagnostics are run in the same manner as they are from disk. Eserver pSeries 690 Service Guide...
  • Page 791 v On a full system partition, if the diagnostics are loaded from disk or a server, you must shut down the AIX operating system before turning off the system unit to prevent possible damage to disk data. Do this in either of the following ways: –...

  • Page 792: Concurrent Mode

    The full-test level requires the device not be assigned to or used by any other operation. This level of testing on a disk drive might require the use of the varyoff command. The diagnostics display menus to allow you to vary off the needed resource. Eserver pSeries 690 Service Guide...

  • Page 793: Running The Online Diagnostics In Concurrent Mode

    The diag command is then used to invoke the diagnostic controller so you can run the diagnostics. After the diagnostic controller is loaded, follow the normal diagnostic instructions. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation. The AIX Documentation CD contains the base set of publications for the operating system, including system-management and end-user documentation.

  • Page 794: Standalone Diagnostic Operation

    (get help if needed). Stop all programs. 2. Remove all tapes, diskettes, and CD-ROMs. 3. From the following list, select the type of partitioned system you are running the standalone diagnostics in, then follow the power or reboot instructions. Eserver pSeries 690 Service Guide...
  • Page 795 v If you are running standalone diagnostics in a full machine partition, power off the system unit. Wait until the Power-on LED stops flashing and remains off, then press the power button to turn on the system. v If you are running standalone diagnostics in an LPAR partition, reboot the partition that will be running the standalone diagnostics.

  • Page 796: Nim Server Configuration

    Registering a client on the NIM server v Enabling a client to run diagnostics from the NIM server Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation. The AIX Documentation CD contains the base set of publications for the operating system, including system-management and end-user documentation.

  • Page 797: Booting Standalone Diagnostics From The Nim Server On A System With An Hmc Attached

    Booting Standalone Diagnostics from the NIM Server on a System with an HMC Attached To run standalone diagnostics on a client from the NIM server, do the following: 1. Remove any removable media (tape or CD-ROM). 2. Stop all programs including the AIX operating system (get help if needed). If you are running standalone diagnostics in a full system partition, verify with the system administrator and system users that the system unit can shut down.
  • Page 798 Eserver pSeries 690 Service Guide...

  • Page 799: Chapter 7. Using The Service Processor

    U1.18-P1-H2). None of this information is applicable to the serial ports, or modems attached to those serial ports, on the IBM Hardware Management Console for pSeries (HMC). 2. On some of the system management services (or service processor) screens, you will see the term LPAR, which is equivalent to the term partitioned system.

  • Page 800: Accessing The Service Processor Menus Remotely

    The service processor exits menu mode after ten minutes of inactivity and displays a message indicating that it has done so. Pressing any key on the virtual terminal window causes the main menu to display. Eserver pSeries 690 Service Guide...

  • Page 801: General User Menu

    General User Menu The menu options presented to the general user are a subset of the options available to the privileged user. The user must know the general-access password, if one is set, to access this menu. GENERAL USER MENU 1.

  • Page 802: Privileged User Menus

    Language Selection Menu See “Language Selection Menu” on page 808 for more information. v Call-In/Call-Out Setup Menu See “Call-In/Call-Out Setup Menu” on page 809 for more information. v Set System Name Allows setting of the system name. Eserver pSeries 690 Service Guide...

  • Page 803: Service Processor Setup Menu

    Service Processor Setup Menu The following Service Processor Setup Menu is accessed from the Main Menu: SERVICE PROCESSOR SETUP MENU 1. Change Privileged Access Password 2. Change General Access Password 3. Enable/Disable Console Mirroring: Currently Enabled 4. Start Talk Mode 5.
  • Page 804 This capability can be enabled by local or remote users, providing local users with the capability to monitor remote sessions. Console mirroring can be enabled for the current session only. For more information, see “Console Mirroring” on page 832. Eserver pSeries 690 Service Guide...
  • Page 805 v Start Talk Mode In a console-mirroring session, it is useful for those who are monitoring the session to be able to communicate with each other. Selecting Start Talk Mode activates the keyboards and displays for such communications while console mirroring is established. This is a full duplex link, so message interference is possible.
  • Page 806 When the scan log dump is complete, depending on how the reboot policy is set, the system will either: – Go to the standby state (and the service processor menus will be available), indicated by OK or STBY in the operator panel – Attempt to reboot. Eserver pSeries 690 Service Guide...
  • Page 807 Scan Log Dump Setup Menu 1. Scan Log Dump Policy: Currently As Needed 2. Scan Log Dump Content: Currently As Requested 3. Immediate Dump 98. Return to Previous Menu 0>1 Select from the following options: (As Needed=2, Always=3) Enter New Option: 0>1 The scan log dump policy can be set to the following: 2=As Needed...

  • Page 808: System Power Control Menu

    Ring indicate power-on is enabled by default on both serial port 1 (S1) and serial port 2 (S2). When ring indicate power-on is enabled, call-in is disabled. If ring indicate power-on is enabled and call-in is already enabled, you will be asked to confirm your choice. Refer to the message displayed on your screen. Eserver pSeries 690 Service Guide...
  • Page 809 If the ring indicate power-on setting is changed, you must select option 30, Refresh Modem Settings to update the modem settings. If Refresh Modem Settings is selected, and the modem(s) have not been configured, you will be asked to configure the modems first. See “Call-In/Call-Out Setup Menu” on page 809 for information on configuring modems.
  • Page 810 Using this option to boot the system is the preferred way to run standalone diagnostics. – Boot to Open Firmware This option should only be used by service personnel to obtain additional debug information. When this selection is enabled, the system boots to the open firmware prompt. Eserver pSeries 690 Service Guide...

  • Page 811: System Information Menu

    System Information Menu This menu provides access to system configuration information, error logs, system resources, and processor configuration. SYSTEM INFORMATION MENU 1. Read VPD Image from Last System Boot 2. Read Progress Indicators from Last System Boot 3. Read Service Processor Error Logs 4.
  • Page 812 RAM (NVRAM) has been erased, this table may be empty. The table is rebuilt during the next boot into AIX. The fields of the previous table represent the following: Column 1 (1.) Menu selection index. Eserver pSeries 690 Service Guide...
  • Page 813 Column 2 (0) Logical processor device number assigned by AIX. You can display these logical device numbers by issuing the following command on the AIX command line: lsdev -C | grep proc Column 3 (3.0) Processor address list used by the service processor. Column 4 (00) Error status of the processors.
  • Page 814 In the previous example menu, each line shows two books and indicates whether they are configured, deconfigured, or partially deconfigured. To enable or disable Memory Repeat Gard, use menu option 77 of the Memory Configuration/Deconfiguration Menu. The default is enabled. Eserver pSeries 690 Service Guide...
  • Page 815 To enable or disable runtime recoverable error repeat gard, use option 78 of the Memory Configuration/Deconfiguration Menu. The default is enabled. The failure history of each book is retained. If a book with a history of failures is brought back online by disabling Repeat Gard, it remains online if it passes testing during the boot process.
  • Page 816 (which is shown as the ″Code level″) that is currently installed on the FRU, as well as other information, are displayed. A sample of the output of this option, which shows several of the types of power subystem FRUs in this system, follows. Eserver pSeries 690 Service Guide...
  • Page 817 Please wait..Fru type = 00f6 BPC-RH Cage id = ff BPA Port Fru id = 80 BPC Location Code = U1.35-P1-X4 Code level = 0000255e Status = 01 Successfully collected Fru type = 0048 DCA-RHP Cage id = 00 CEC Cage Fru id = 90 DCA 1 Location Code = U1.18-P1-V1...
  • Page 818 (blinking) and off. Option 1 is available only when the system is in the error state (the CEC is powered on and the service processor menus are available). Option 1 is not available when the system is in standby. Eserver pSeries 690 Service Guide...
  • Page 819 An example of this menu follows: LED Control Menu 1. Set/Reset Identify LED state 2. Clear System Attention Indicator 98. Return to Previous Menu Enter LED index 0 > The processor subsystem disturbance or system attention LED is located on the operator panel in the media drawer.
  • Page 820 Physical Location Code 1. L3_13 U1.18-P1-C5 2. L3_0 U1.18-P1-C6 3. MCM_0 U1.18-P1-C1 4. L3_1 U1.18-P1-C7 5. L3_4 U1.18-P1-C8 6. L3_14 U1.18-P1-C9 7. L3_3 U1.18-P1-C10 8. L3_2 U1.18-P1-C11 9. L3_7 U1.18-P1-C12 10. MCM_3 U1.18-P1-C2 11. MCM_2 U1.18-P1-C3 Eserver pSeries 690 Service Guide...
  • Page 821 12. L3_15 U1.18-P1-C13 13. L3_10 U1.18-P1-C14 14. MCM_1 U1.18-P1-C4 15. L3_11 U1.18-P1-C15 16. L3_6 U1.18-P1-C16 17. L3_12 U1.18-P1-C17 18. L3_9 U1.18-P1-C18 19. L3_8 U1.18-P1-C19 20. L3_5 U1.18-P1-C20 To change the plug count for a particular module, enter a menu index number. For example, to change the plug count of the L3 module that is physically in the upper-right corner (U1.18-P1-C8), type 5, then enter the new plug count.
  • Page 822 This setting provides the best performance for most applications. – Standard Operation optimizes the system for large memory bandwidth applications where minimal sharing of data occurs and the likelihood of significant hardware data-prefetching exists. Eserver pSeries 690 Service Guide...
  • Page 823 – Turbo Database Mode optimizes system operation for environments where there is a large amount of data sharing among processes running concurrently on the system. v L3 Mode Menu This function is not applicable to this system. Remote I/O (RIO) Link Speed Set Up Menu This option is used to change the speed of the RIO interface to external drawers.

  • Page 824: Language Selection Menu

    2. Francais 3. Deutsch 4. Italiano 5. Espanol 98. Return to Previous Menu 99. Exit from Menus 0> Note: Your virtual terminal window must support the ISO-8859 character set to correctly display languages other than English. Eserver pSeries 690 Service Guide...
  • Page 825 Call-In/Call-Out Setup Menu Note: The information in this section regarding the configuring of serial ports, and modems attached to those serial ports, applies only to the serial ports (S1 and S2) on the primary I/O book (location U1.18-P1-H2). These serial ports are normally used for call-in and call-out. Call-out is disabled in partitioned systems.

  • Page 826: Modem Configuration Menu

    30. Save configuration to NVRAM and Configure modem 98. Return to Previous Menu 0> For information on choosing a modem configuration file, see “Sample Modem Configuration Files” on page 1079 and “Transfer of a Modem Session” on page 1084. Eserver pSeries 690 Service Guide...

  • Page 827: Serial Port Selection Menu

    Serial Port Selection Menu This menu allows you to enable or disable the call-in and call-out functions of each serial port in any combination. Note: If the system is running in partition mode, call-out is disabled. Serial Port Selection Menu 1.

  • Page 828: Serial Port Speed Setup Menu

    2. Customer Administration Center Telephone Number: Currently Unassigned 3. Digital Pager Telephone Number: Currently Unassigned 4. Customer Voice Telephone Number: Currently Unassigned 5. Customer System Telephone Number: Currently Unassigned 98. Return to Previous Menu 0> Eserver pSeries 690 Service Guide...
  • Page 829 v Service Center Telephone Number is the number of the service center computer. The service center usually includes a computer that takes calls from servers with call-out capability. This computer is referred to as the ″catcher.″ The catcher expects messages in a specific format to which the service processor conforms.
  • Page 830 Remote timeout and remote latency are functions of your service provider’s catcher computer. Either use the defaults or contact your service provider for recommended settings. v Number of retries is the number of times you want the server to retry calls that failed to complete. Eserver pSeries 690 Service Guide...

  • Page 831: Service Processor Parameters In Service Mode (Full System Partition)

    Customer Account Setup Menu This menu allows users to enter information that is specific to their account. Customer Account Setup Menu 1. Customer Account Number: Currently Unassigned 2. Customer RETAIN Login userid: Currently Unassigned 3. Customer RETAIN login password: Currently Unassigned 98.

  • Page 832: System Power-On Methods

    Hardware Management Console (HMC) Using the HMC is the preferred method of powering on a managed system. For details on using the HMC to power up a system, see the IBM Hardware Management Console for pSeries Installation and Operations Guide.

  • Page 833: Service Processor Reboot/Restart Recovery

    Service Processor Reboot/Restart Recovery Reboot describes bringing the system hardware back up; for example, from a system reset or power-on. The boot process ends when control passes to the operating system process. Restart describes activating the operating system after the system hardware is reinitialized. Restart must follow a successful reboot.
  • Page 834 AIX default In a partitioned system, the service processor’s supplemental restart policy is the only setting that is used, as shown in the following table: Service Processor enable supplemental restart policy System Response Yes (default) Restarts Eserver pSeries 690 Service Guide...

  • Page 835: System Firmware Updates

    Download the detailed instructions, as well as the latest flash images, from the following Web address: http://techsupport.services.ibm.com/server/mdownload2. Before doing a system firmware update, check the Web site for the latest code and images. Do not attempt a firmware update if you are unsure of the image you have, or of the procedure required for the update.

  • Page 836: Determining The Level Of Firmware On The System

    The firmware level can be denoted in either of the following forms: v RHyymmdd, where RH = the pSeries 690’s firmware designation, yy = year, mm = month, and dd = day of the release. v vHyymmdd, where v = version number, H= the pSeries 690’s firmware designation, yy = year, mm = month and dd = day of the release.

  • Page 837: System Firmware Update In Aix Using A Locally Available Image

    System Firmware Update in AIX Using a Locally Available Image To update the system firmware using a locally available image, perform the following steps: 1. Log in as root user. 2. If the /tmp/fwupdate directory does not exist, create it by issuing the following command: mkdir /tmp/fwupdate 3.

  • Page 838: Updating System Firmware From The Service Processor Menus

    Refer to the detailed instructions that are provided with the latest image on CORE. Note: Because the system always reboots itself during this type of firmware update process, the update process can take from twenty to sixty minutes. Eserver pSeries 690 Service Guide...

  • Page 839: Updating System Firmware From The Aix Command Line

    Updating System Firmware from the AIX Command Line Attention: This method is not recommended for partitioned systems, but if the device resources are allocated properly, the firmware update can be done from the AIX command line. If the firmware on a partitioned system is being updated: v One partition running AIX must have service authority.

  • Page 840: Recovery Mode

    2. If B1FD 001A is displayed at any time during the process, the service processor must be reset by activating the pinhole reset switch on the operator panel. After the update process is complete, the service processor resets itself and goes through a complete reboot. Eserver pSeries 690 Service Guide...

  • Page 841: Frame (Power Subsystem) Firmware Update With A Pseries High Performance Switch Installed

    When a pSeries High Performance Switch (7045-SW4) is installed in or attached to the system, the frame firmware, which includes the power subsystem, is updated using a task on the HMC. Code updates (also called corrective service) are available at http://techsupport.services.ibm.com/server/mdownload2. This task downloads a corrective service for the frame onto the HMC.

  • Page 842: Installing Corrective Service On The Frame

    For information about system administrator or service representative roles, refer to the IBM Hardware Management Console for pSeries Installation and Operations Guide. 2. Do not power off any of the components in the frame at any time during this installation procedure.

  • Page 843: Reconfiguration Procedure For Sni Adapters

    Reconfiguration Procedure for SNI Adapters After the system has booted to the AIX login prompt, log in and verify that the SNI adapters are configured properly. On the AIX command line, issue the following command: lscfg | grep sni The number of sni adapters identified in the output of the above command (represented by their logical device names) should match the number in the system (2-8).

  • Page 844: Configuring And Deconfiguring Processors Or Memory

    AIX. At the same time, PRD marks the CPU for deconfiguration at the next boot. AIX will attempt to migrate all resources associated with that processor to another processor and then stop the defective processor. Eserver pSeries 690 Service Guide...

  • Page 845: Service Processor System Monitoring - Surveillance

    Service Processor System Monitoring - Surveillance Surveillance is a function in which the service processor monitors the system, and the system monitors the service processor. This monitoring is accomplished by periodic samplings called heartbeats. Surveillance is available during two phases: v System firmware bringup (automatic) v Operating system runtime (optional) Note: Operating system surveillance is disabled on partitioned systems.

  • Page 846: Operating System Surveillance

    If surveillance is selected from the service processor menus that are only available at system boot, then surveillance is enabled by default as soon as the system boots. From service aids, the selection is optional. Eserver pSeries 690 Service Guide...

  • Page 847: Call-Out (Call-Home)

    3. To call out before restart, set Call-out before restart to ENABLED from the Reboot/Restart Policy Setup menu. Note: Some modems, such as IBM 7857-017, are not designed for the paging function. Although they can be used for paging, they will return an error message when they do not get the expected response from another modem.

  • Page 848: Console Mirroring

    1. Local session is already in progress. 2. The service processor receives a call from the remote user. 3. The local user selects the option to enable console mirroring. The service processor immediately begins mirroring service processor menus. Eserver pSeries 690 Service Guide...

  • Page 849: Service Processor Error Logs

    Service Processor Error Logs The service processor error logs, an example of which follows, contain error conditions detected by the service processor. Error Log 1. 11/30/99 19:41:56 Service Processor Firmware Failure B1004999 Enter error number for more details. Press Return to continue, or ’x’ to return to menu. Press "C"...

  • Page 850: Lcd Progress Indicator Log

    0539.. 0742..U1.5-P1-I12/E1 0539.. 0776..U1.5-P1-I10/T1 E139 E1FB E139 E183 Press Return to continue, or ’x’ to return to menu. > EAA1..U1.9-P1-I14 E172..U1.9-P1 E172..U1.9-P1-I14 E172..U1.9-P1 94BB 9109 9380 9108 9107 9106 9105 9118 9104 9103 9102 90FD Eserver pSeries 690 Service Guide...

  • Page 851: Resetting The Service Processor

    Resetting the Service Processor Some error conditions might cause the service processor to hang. The service processor must be reset to recover from a hung condition. If the system is powered on, resetting the service processor will cause the system to shut down. When the service processor is reset, it carries out its power-on sequence, including self-tests.

  • Page 852: Service Processor Operational Phases

    The service processor does not wait for user input or power-on command, but moves through the phase and into the bring-up phase. Access the SMS menus or the service processor menus to reset the unattended start mode. Eserver pSeries 690 Service Guide...

  • Page 853: Standby Phase

    Standby Phase The standby phase can be reached in either of two ways: v With the server off and power connected (the normal path), recognized by OK in the LCD display. v With the server on after an operating system fault, recognized by an 8-digit code in the LCD display. In the standby phase, the service processor takes care of some automatic duties and is available for menus operation.
  • Page 854 On an HMC-managed system, the service processor monitors the communication link between the managed system and the HMC. If the service processor detects that this communication link has been broken, it will post an error to the operating system running on the managed system. Eserver pSeries 690 Service Guide...

  • Page 855: Chapter 8. Using System Management Services

    SMS menus. In a full system partition, all devices in the system display in the SMS menus. To start the system management services, do the following: 1. For a partitioned system, use the IBM Hardware Management Console for pSeries (HMC) to restart the partition. For a full system partition, restart the system.

  • Page 856: Select Language

    M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _ Eserver pSeries 690 Service Guide...

  • Page 857: Change Password Options

    Change Password Options The Change Password Options menu enables you to select from password utilities. Note: This option is not available in partitioned systems. Password Utilities 1 Set Privileged-Access Password 2 Remove Privileged-Access Password -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services --------------------------------------------------------------------------------------------------...

  • Page 858: Setup Remote Ipl (Initial Program Load)

    Type the number of the menu item and press Enter or Select a Navigation key: _ To change IP parameters, type the number of the parameters for which you want to change the value. Entering IP parameters on this screen will automatically update the parameters on the ping test screen. Eserver pSeries 690 Service Guide...
  • Page 859 Attention: If the client system and the server are on the same subnet, set the gateway IP address to [0.0.0.0]. Selecting Adapter Configuration allows the setting of the network speed, enabling or disabling spanning tree, and setting the protocol as shown in the following example menu: Adapter Configuration 10/100 Mbps Ethernet PCI Adapter II: U1.9-P1-I4/E1 1.

  • Page 860: Change Scsi Settings

    SMS menus and does not affect the display used by the operating system. Follow the instructions that display on the screen. The firmware automatically returns to the SMS main menu. Eserver pSeries 690 Service Guide...

  • Page 861: Select Boot Options

    Select Boot Options Use this menu to view and set various options regarding the installation devices and boot devices. 1. Select Install or Boot a Device 2. Select Boot Devices 3. Multiboot Startup -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services --------------------------------------------------------------------------------------------------...
  • Page 862 If either Normal Mode Boot or Service Mode Boot is selected, the next screen will ask, Are you sure?. If you answer yes, the device will be booted in the appropriate mode. If you answer no, the firmware will return to the Select Task menu. Eserver pSeries 690 Service Guide...

  • Page 863: Select Boot Devices

    Select Boot Devices Attention: In a partitioned system, only those devices from which an operating system can be booted that are assigned to the partition that is being booted display on the select boot devices menu. In a full system partition, devices from which an operating system can be booted display on the Select Boot Devices menu.
  • Page 864 When a device type is selected, the Select Task menu allows you to see detailed information about the device or set the device’s location in the boot list as shown below in the example menu. The following is an example of the menu for a hard disk. Eserver pSeries 690 Service Guide...

  • Page 865: Display Current Settings

    Select Task SCSI 18200 MB Harddisk (loc=U0.1-P2/Z1-A8,0) 1. Information 2. Set Boot Sequence: Configure as 1st Boot Device -------------------------------------------------------------------------------------------------- Navigation keys: M = return to main menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------------------------- Type the number of the menu item and press Enter or Select a Navigation key: _ Selecting Information displays a menu similar to the following for a hard disk.

  • Page 866: Restore Default Settings

    Multiboot Startup toggles the multiboot startup flag, which controls whether the multiboot menu is invoked automatically on startup. Exiting System Management Services After you have finished using the system management services, type x (for exit) to boot your system or partition. Eserver pSeries 690 Service Guide...

  • Page 867: Chapter 9. Removal And Replacement Procedures

    Chapter 9. Removal and Replacement Procedures Introduction ........853 Handling Static-Sensitive Devices .
  • Page 868 Media Subsystem Internal Cables ......1021 p690 Cable Installation and Management ..... . 1022 Eserver pSeries 690 Service Guide...

  • Page 869: Introduction

    Introduction Before performing any of the removal or replacement procedures in this chapter, read the following notices. DANGER An electrical outlet that is not correctly wired could place hazardous voltage on metal parts of the system or the devices that attach to the system. It is the responsibility of the customer to ensure that the outlet is correctly wired and grounded to prevent an electrical shock.

  • Page 870: Powering Off And Powering On The System

    If you are servicing an individual I/O subsystem, refer to the information about deactivating a system’s I/O drawers, found in ″Basic System Management Tasks″, located in the IBM Hardware Management Console for pSeries Installation and Operations Guide to remove 350 V power from both of the I/O subsystem DCA UPIC cable connections.
  • Page 871 v If a High Performance Switch (7045-SW4) is not installed in the processor subsystem frame, input power must be removed by turning off the UEPO switch, turning off the circuit breakers on all optional IBF subsystems (if provided), and then disconnecting both power cords from the customer’s receptacle. If the system is operating in a full system partition under AIX, typing the shutdown command causes the system to shut down and power off.

  • Page 872: Powering Off The System With An Hmc Attached And Linux Installed

    If you are servicing an individual I/O subsystem, refer to the information about deactivating a system’s I/O drawers, found in ″Basic System Management Tasks, located in the IBM Hardware Management Console for pSeries Installation and Operations Guide to remove 350 V power from both of the I/O subsystem DCA UPIC cable connections.
  • Page 873 system users. Check with the system administrator before using this command. If you cannot use this method, you can power off the system by pressing the power button on the operator panel or the appropriate command at the HMC. Attention: Using the power button on the operator panel or commands at the HMC to power off the system can cause unpredictable results in the data files.

  • Page 874: Hot-Pluggable Frus

    BPF can be replaced with power on, follow the appropriate removal and replacement procedures. IBF can be replaced with power on, follow the appropriate removal and replacement procedures. Capacitor book Processor subsystem chassis Memory cards L3 cache Clock card I/O books Eserver pSeries 690 Service Guide...
  • Page 875 I/O Subsystem FRUs Hot-Pluggable Notes Concurrent Maintenance - I/O backplane and riser card - DASD backplane - Disk drives Yes (AIX only) Might require additional consideration or preparation by the customer for replacement. - DCA (power supplies) Only one DCA can be removed at a time. - I/O fan assemblies Can be replaced only if the DASD backplane is not installed.

  • Page 876: Power Subsystem

    Order the older version of the BPR if you are not replacing all of the BPRs installed in the system and the firmware on the system is below firmware release 3H030916. Install the upgrade BPR, identified by Eserver pSeries 690 Service Guide...
  • Page 877 FRU part number 44P2645, only if the firmware on the system is 3H030916 or later. Do not mix the two versions without the firmware level being 3H030916 or later. 2. Make sure that the BPR release levers are in the UP position. Slide the unit into slot until one inch from BPE.
  • Page 878 7. If a high performance switch is installed in or attached to the system, perform the steps described in “Frame (Power Subsystem) Firmware Update with a pSeries High Performance Switch Installed” on page 825 to insure that the new BPC contains the correct code. Eserver pSeries 690 Service Guide...
  • Page 879 Bulk Power Distributor (BPD) There can be two BPDs, located immediately above the BPC. If only one BPD is required, an airflow baffle must installed in the top BPD position. Attention: This service procedure may produce other power error code(s) (101x xxxx) between the time the Start Service button is pressed, and the Service Complete button is pressed, during concurrent repair.
  • Page 880 7. If a high performance switch is installed in or attached to the system, perform the steps described in “Frame (Power Subsystem) Firmware Update with a pSeries High Performance Switch Installed” on page 825 to insure that the new BPF contains the correct code. Eserver pSeries 690 Service Guide...
  • Page 881 Bulk Power Enclosure (BPE) Attention: This service procedure may produce other power error code(s) (101x xxxx) between the time the Start Service button is pressed and the Service Complete button is pressed, during concurrent repair. If the system behaves normally, as described by this procedure, ignore these error codes. Removal Attention: The BPE unit weighs approximately 18.14 kg (40 lbs).
  • Page 882 2. Plug all cables to the UEPO card assembly, ensuring that the plug location and the cable label agree. 3. Install the external cable, if required, to connector J02. a. If the external EPO connection is installed, the internal toggle switch is mechanically forced into the ROOM EPO ACTV position (to the right). Eserver pSeries 690 Service Guide...
  • Page 883 b. If there is no external EPO cable, manually set the internal toggle switch to the ROOM EPO BYPASS position. To set this switch, pull the knob down, to the ROOM EPO BYPASS position, and release the knob (to the left). 4.
  • Page 884 11. Reinstall all components removed during the removal process. 12. Set the circuit breaker to the on (left) position. 13. Press the white Service Complete button on the UEPO switch to indicate completion of this procedure. Eserver pSeries 690 Service Guide...

  • Page 885: Processor Subsystem

    Processor Subsystem This section contains the removal and replacement procedures for the processor subsystem. Handle all processor subsystem FRUs with extreme care. Installing the MCM/L3/Passthrough Plug Map If the MCM/L3/Passthrough Plug Map is not installed in the system, install it before continuing with any repair action for MCMs or L3 cache module.
  • Page 886 Click on the partition name and choose ″Operating system reset″; on the operating system reset screen select ″Hard Reset″. j. Click on ″OK″ to shut down the partition. k. If the managed system is not powered down at this point, power it down now. Eserver pSeries 690 Service Guide...
  • Page 887 Record the full system partition mode bootlist if one has been set. a. Right-click on the full system partition name, then select ″PowerOnSMSProfile″, click on the ″Open terminal window″ box, then click on ″OK″ to power the system up to the SMS menus. At the SMS main menu, choose ″Select Boot Options″, then choose option 2, ″Select Boot Devices″.
  • Page 888 Note: You need a laptop computer and (cable part number 62H4857) capable of connecting to serial port 2 on the primary I/O book. a. Attach the laptop computer and cable to serial port 2 on the primary I/O book. Eserver pSeries 690 Service Guide...
  • Page 889 b. When OK is displayed in the operator panel on the media drawer, press a key on the virtual terminal on the laptop computer. The firmware version is displayed above the main menu, in the format RHyymmdd or vHyymmdd. If the HMC is at release 2 version 1.2 (or earlier), and the system firmware is at GA3, which is any level including RH021025 and later, and 3Hyymmdd and later, there are two options for resolving the version mismatch: –...
  • Page 890 Reenter the Boot Lists on the HMC: Using the HMC, reenter the partitions’ boot lists or the full system partition boot list using the lists that were recorded before the primary I/O book was replaced. Set the Date and Time: Set the system date and time using the operating system. Eserver pSeries 690 Service Guide...
  • Page 891 Battery CAUTION: A lithium battery can cause fire, explosion, or a severe burn. Do not recharge, disassemble, heat above 100 degrees C (212 degrees F), solder directly to the cell, incinerate, or expose cell contents to water. Keep away from children. Replace only with the part number specified for your system. Use of another battery may represent a risk of fire or explosion.
  • Page 892 2. “Set the System Name” on page 874 3. “Restore the Service Processor Settings” on page 874 4. “Reenter the Boot Lists on the HMC” on page 874 5. “Set the Date and Time” on page 874. Eserver pSeries 690 Service Guide...
  • Page 893 Processor Subsystem DCA (Distributed Converter Assembly) Books and DCA Blanks Removal The following safety notice applies to power-related field replaceable units. DANGER Do not attempt to open the covers of the power supply. Power supplies are not serviceable and are to be replaced as a unit. 1.

  • Page 894: Capacitor Books And Blanks

    5. Check torque on both fasteners. 6. If any cables were removed during the removal procedure, plug all cables into their correct locations. 7. Turn on the power as described in “Powering the System On” on page 857. Eserver pSeries 690 Service Guide...
  • Page 895 MCM Module (Processor) and Pass Through Modules Attention: All components must be replaced to the location from which they were removed. Before replacing MCMs, check with your support center to ensure you have been directed to replace the MCM(s) by a valid error code in Chapter 5, “Error Code to FRU Index,” on page 415. Handling Static-Sensitive Modules Attention: MCM and L3 modules are sensitive to static electricity discharge.
  • Page 896 7. If the MCM modules that you are removing have a copper heatsink and an aluminum stiffener attached to the backplane, do the following: Note: Remove each MCM processor from the processor drawer, one at a time, until all MCM processors that you planned to remove have been removed. Eserver pSeries 690 Service Guide...
  • Page 897 8. Beginning with the upper most module to be removed, loosen the two captive heatsink bushing screws until they are free floating. See the following illustration for heatsink bushing screw locations. 9. Insert the two steel alignment rods through the MCM alignment holes and into the aluminum stiffener. See the following illustration for MCM clearance hole locations.
  • Page 898 The steel alignment rods are used to relieve some of the weight of the MCM processor when removing them from the processor drawer. b. The field restocking plan, is to replace the 1.7 GHz copper heatsink MCM (factory installed) with a 1.7 GHz aluminum heatsink MCM. Eserver pSeries 690 Service Guide...
  • Page 899 19. With both hands, grasp the module across the narrow span of the heatsink cap, and pull the MCM module from the system board and place it, posts-down, on the ESD mat. 1 Processor Backplane 2 MCM (aluminum heatsink version) 3 MCM Pass Through 20.
  • Page 900 (top side) or counter bore pin indent (bottom side). Missing buttons 23. Record on the system log sheet on the system the date that this MCM has been removed. Eserver pSeries 690 Service Guide...
  • Page 901 Returning MCM Modules: The following procedure provides handling instructions for MCM modules to be packaged and returned to the plant of manufacture. 1. If you are replacing an MCM, use the packaging from the new module to return the old module. If the packaging is not available, order the following parts for MCM or pass through protective packaging: v 1 Black Plastic Case (Top and Bottom) 02P3750 v 1 MCM Heat Sink Cap - 7335949 or 7335963 (not required for pass through)
  • Page 902 MCM when securing both locking cams. 6. Loosen the actuation bolt at the rear of the MCM module. 7. Push the actuation bolt in and slide the spring plate assembly to the down position. Eserver pSeries 690 Service Guide...
  • Page 903 8. Use the torque wrench (supplied with the system tool kit, see “Tools” on page 1051 for the tool part number) to tighten the actuation bolt. When the wrench clicks, followed by about 15 degrees of free motion, the bolt is seated. 9.
  • Page 904 (or any capacitor books with the necessary LGA test-support features), and the new LGA-ST. Refer to “Method 3. Testing MCMs and Pass Through Modules for a Short Circuit” on page 895. Eserver pSeries 690 Service Guide...
  • Page 905 Method 1. Testing MCMs and Pass Through Modules for a Short Circuit Performing this test ensures that a short circuit was not created when installing an MCM or a pass through module. Follow the procedure to install and use the MCM/L3 module short-circuit test tool (part number 44P0209) and a multimeter during MCM replacement.
  • Page 906 MCM Installation Shorts Test, Step 2: * See the Fail Criteria value in “Shorts Test Qualified Service Meters and Fail Criteria” on page 916. Eserver pSeries 690 Service Guide...
  • Page 907 MCM Installation Shorts Test, Step 3: Are there any L3 cache modules to install? Remove The Meter & Test Card Remove Meter Follow the L3 cache module Reinstall the DCAs and reassemble replacement and and test the system procedures * Power On the System and Perform a slow boot Were any...
  • Page 908 MCM Installation Shorts Test, Step 1: Attention: Be sure to record the resistance readings taken during these tests so that you can refer to them if needed. * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 916. Eserver pSeries 690 Service Guide...
  • Page 909 MCM Installation Shorts Test, Step 2: * See the Fail Criteria value in “Shorts Test Qualified Service Meters and Fail Criteria” on page 916. Chapter 9. Removal and Replacement Procedures...
  • Page 910 MCM Installation Shorts Test, Step 3: * See “L3 Cache Modules” on page 898. Eserver pSeries 690 Service Guide...
  • Page 911 Method 3. Testing MCMs and Pass Through Modules for a Short Circuit You must test the LGA-ST unit before you can begin testing the MCM and pass through modules for a short circuit with the following steps: 1. Plug the LGA-ST test head on the test box into the 9-pin female self-test D-shell, located on the LGA-ST control box, which looks similar to the following: 1 Tester D-shell 5 Toggle switch...
  • Page 912 Capacitor book from the system. If the LED states are not as shown in this table after the Capacitor book is disengaged, the LGA-ST is defective. Replace the unit before proceeding. Eserver pSeries 690 Service Guide...
  • Page 913 3. Install an MCM or pass through module. 4. Press the toggle switch on the LGA-ST forward to the MCM/L3 PWR/GND position. This action will test the MCM or pass through modules for power-to-ground shorts. Observe the lit LEDs on the LGA-ST and take the corresponding following actions: Green MCM LED is lit This is a pass state.

  • Page 914: L3 Cache Modules

    If it has been unplugged three times, order a new module. If this is the first removal/reseat for the module, record the serial number of the module and the date of the action. Eserver pSeries 690 Service Guide...
  • Page 915 5. Use a 5-mm nut driver to loosen the set screw in the center of the L3 module spring plates as shown in the following illustration.. 1 Protective Cover 4 Rear Spring Plate 2 L3 Cache Module and Heatsink 5 Front Spring Plate with Set Screw 3 Load Posts 6 L3 Filler (Used if no L3 cache...
  • Page 916 (top side) or counter bore pin indent (bottom side). Missing buttons 12. Record on the system log sheet the date that this L3 cache module was removed. Eserver pSeries 690 Service Guide...
  • Page 917 Returning L3 Modules: The following procedure provides handling instructions for L3 modules to be packaged and returned to the plant of manufacture. 1. If you are replacing an L3 module, use the packaging from the new module to return the old module. If the packaging is not available or does not include all the parts described below, order the following part for L3 module protective packaging: v 1 L3 protective package part number 7335692, which includes: 1 carton, 1 top foam cushion, 1...
  • Page 918 If this is the last L3 cache module you are installing, remove the MCM/L3 module short-circuit test tool and meter. 8. Remove the primary I/O book (see “I/O Books and I/O Blanks” on page 870) and replace the VPD card that was provided with the L3 cache module. CUoD Eserver pSeries 690 Service Guide...
  • Page 919 9. Replace the primary I/O book. 10. Replace the fan chassis. See “Fan Chassis” on page 928. 11. Turn on power as described in “Powering the System On” on page 857. 12. If an MCM or L3 cache module was just added or replaced, go to the service processor menu and select System Information Menu, then select MCM/L3 Interposer Plug Count Menu.
  • Page 920 Record Meter Reading. Call this resistance "Meter Lead Resistance" (MLR) Are L3 cache modules installed in the system? Install First L3 Cache Module [U1.18.P1-Cx] * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 916. Eserver pSeries 690 Service Guide...
  • Page 921 L3 Cache Shorts Test, Step 2: Connect Meter "V" to Test Card "1.9V L3 LGA" (Blue Jack) Meter "COM" to Test Card either "COMMON RET" (Black Jack) Record Resistance. Call this resistance" 1.9v L3 Total Resistance"( 1.9vL3TR) Enter recorded Fail Criteria *, MLR, 1.9vL3TR in the equation below 1.9vL3TR - MLR >...
  • Page 922 L3 Cache Shorts Test, Step 3: * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 916. Eserver pSeries 690 Service Guide...
  • Page 923 L3 Cache Shorts Test, Step 4: Chapter 9. Removal and Replacement Procedures...
  • Page 924 L3 Cache Shorts Test, Step 5: Eserver pSeries 690 Service Guide...
  • Page 925 Method 2. Testing L3 Cache Modules for a Short Circuit Performing this test ensures that a short circuit was not created when an L3-cache module is installed. Follow this procedure to install and use the capacitor book (part number 44P2471) and a multimeter during L3-cache module replacement.
  • Page 926 L3 Cache Shorts Test, Step 2: Eserver pSeries 690 Service Guide...
  • Page 927 L3 Cache Shorts Test, Step 3: * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 916. Chapter 9. Removal and Replacement Procedures...
  • Page 928 L3 Cache Shorts Test, Step 4: Eserver pSeries 690 Service Guide...
  • Page 929 L3 Cache Shorts Test, Step 5: Chapter 9. Removal and Replacement Procedures...
  • Page 930 2. If the battery appears to be functioning and the LEDs are not lit as shown in this table, the LGA-ST is defective. Replace the unit before proceeding. Eserver pSeries 690 Service Guide...
  • Page 931 c. Power off the system. d. Set UEPO to OFF. e. Disengage all DCAs from the back plane. f. Plug the LGA-ST Tester D-Shell into the Capacitor card 9-pin D-Shell and tighten the screws. g. Place the toggle switch into the MCM/L3 PWR/GND position and observe the lit LEDs. Refer to the following table for valid LED states: Toggle Switch MCM Green...

  • Page 932: Shorts Test Qualified Service Meters And Fail Criteria

    200 Ohms +/-0.04 +0.40 Fluke 8062A 200 Ohms +/-0.04 +0.40 Fluke 500 Ohms +/-0.10 +0.40 Fluke 500 Ohms +/-0.10 +0.40 Fluke 83 (original models) 400 Ohms +/-0.10 +0.40 Fluke 85 (original models) 400 Ohms +/-0.10 +0.40 Eserver pSeries 690 Service Guide...
  • Page 933 Manufacturer Model Range Accuracy @ 1.0 Fail Criteria ohms or less Fluke 87 (original models) 400 Ohms +/-0.10 +0.40 Fluke 87-4 500 Ohms +/-0.10 +0.40 Fluke 89-4 500 Ohms +/-0.10 +0.40 +/-0.20 Accuracy Fluke 400 Ohms +/-0.20 +0.50 Fluke 400 Ohms +/-0.20 +0.50 Fluke...
  • Page 934 Manager window. The name of the system displays as the system’s serial number. b. From the menu that displays, select the following options, in the following order: 1) Capacity Upgrade on Demand 2) Processor 3) Processor Capacity Settings The Processor Capacity Settings window displays. Eserver pSeries 690 Service Guide...
  • Page 935 c. Click the Display Order Information button in the Processor Capacity Settings window. This will display the Processor Order Information panel, which appears similar to the following: d. Dictate the contents of each field on this panel to service support. 10.

  • Page 936: Vpd Card

    3. Locate the VPD card that must be replaced. CUoD Remove the VPD card for the associated MCM or L3 modules. Replacement Replace in reverse order with the VPD card that was provided with the new MCM or L3 modules. Eserver pSeries 690 Service Guide...

  • Page 937: System Clock Card

    System Clock Card Removal 1. Turn off power as described in “Powering Off and Powering On the System” on page 854. 2. Remove the fan chassis. See “Fan Chassis” on page 928. 3. Squeeze the tabs on the clock card, and pull the card straight out as shown in the following illustration. 1 Processor Backplane 2 System Clock Card 4.

  • Page 938: Aluminum Backplane Stiffener

    5.5 mm deep well socket to loosen and remove the two outer-side retaining screws. b. (Service Tip) When removing the aluminum stiffener, remove the outer-top retaining screw last. When installing or replacing the aluminum stiffener insert the outer-top retaining screw first. Eserver pSeries 690 Service Guide...
  • Page 939 8. Carefully remove the aluminum stiffener and put it in a safe place. 1 System Backplane 5 Clock Card 2 L3 Cache Assembly 6 MCM pass through Module 3 Aluminum Backplane Stiffener 7 MCM with VPD Card Kit 4 MCM Alignment Rods 8 Aluminum Backplane Stiffener Retaining Screws (quantity 8) Replacement...

  • Page 940: Processor Subsystem Chassis

    9. Remove the DCAs and capacitor books (and blanks if applicable). See “Processor Subsystem DCA (Distributed Converter Assembly) Books and DCA Blanks” on page 877. 10. At the front of the system, remove the safety bars from the memory books and blanks. Eserver pSeries 690 Service Guide...
  • Page 941 11. Remove the memory books (and blanks if applicable). See “Memory Books and Memory Blanks” on page 926. 12. Remove the four fan assemblies. See “Processor Fan Assemblies” on page 928. 13. Remove the fan chassis. See “Fan Chassis” on page 928. 14.

  • Page 942: Memory Books And Memory Blanks

    After the memory book is removed from the ESD bag, examine the book VHDM connector using the 3X Magnification Glass (part number 11P4747) included in the system toolkit. If any connector shows signs of damage, do not use it. Eserver pSeries 690 Service Guide...

  • Page 943: Fan Controller

    Replacement Note: If there is no book installed in the position next to the one that you are replacing, install a filler (part number 21P8218) in that adjacent location. To replace a book, do the following: 1. Inspect the new book for damage. For more information, see “Inspection” on page 926. 2.

  • Page 944: Processor Fan Assemblies

    . Removal To remove, grasp finger tabs on the air filter and pull straight out. Replacement To remove, slide the air filter into the slot. The filter is keyed to ensure correct orientation. Eserver pSeries 690 Service Guide...

  • Page 945: I/O Subsystem

    I/O Subsystem I/O Subsystem PCI Slot LED Definitions 1 I/O LED (Currently Unused) 4 I/O Subsystem Backplane Power On (Green) 2 Auxiliary Power Good (Green) 5 I/O Card Power On LED (Green) 3 I/O Subsystem Backplane Fault (Amber) 6 Failing I/O Card LED (Amber) The following table describes the possible states of the LEDs associated with the I/O subsystem PCI slots.

  • Page 946: Pci Adapters

    If a bad gasket is found on a riser card, then the I/O Planar containing the riser card needs to be replaced. If you are removing a PCI adapter that is: v Not hot-pluggable, go to “Removing a Non-Hot-Pluggable PCI Adapter” on page 936. v Hot-pluggable, go to “Hot-Pluggable PCI Adapter” on page 937. Eserver pSeries 690 Service Guide...

  • Page 947: Removing A Pci Adapter Cassette

    Removing a PCI Adapter Cassette Attention: Perform this procedure only when you are instructed to by the removal and replacement procedures in “Removing a Non-Hot-Pluggable PCI Adapter” on page 936 or “Hot-Pluggable PCI Adapter” on page 937. Note: An adapter or a blank filler must be installed into the PCI adapter cassette before it is reinstalled in a processor subsystem or an I/O subsystem.
  • Page 948 4. Push in the locking bar until it clicks into the locked position. See the following illustration. Note: In this position, the locking bar locks the handle in the down position and prevents it from being pulled up while the PCI adapter cassette is being removed. Eserver pSeries 690 Service Guide...
  • Page 949 1 Locking Bar 2 PCI Adapter Tailstock Tab 3 Adapter Cassette Pull Tab 5. Position your index finger under the handle and push up the adapter tailstock tab. Grasp the adapter cassette pull tab with the other hand. Pull the PCI adapter cassette from the adapter slot by pulling on the adapter cassette pull tab.
  • Page 950 See the following illustration. 1 Cassette Dovetail Rails 2 Handle-Release Lever Latch 3 Handle Release Lever 2. Push the top of the locking bar in until it clicks into the locked position. Eserver pSeries 690 Service Guide...
  • Page 951 Note: In this position, the locking bar locks the handle in the down position and prevents it from being pulled up while the PCI adapter cassette is being removed. 3. Examine the PCI adapter slot opening carefully, and note the location of the dovetail rails and the cassette guide rails.
  • Page 952 Multiple Bus Systems. Refer to ″Starting the System Without an HMC Attached″ in your installation or service guides. 5. Set the color slide to blue. 6. Ensure that the adapter is configured when the system completes the boot process. Eserver pSeries 690 Service Guide...
  • Page 953 For additional information about taking an adapter offline or removing it from the system configuration, see the AIX System Management Guide: Operating System and Devices. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation.
  • Page 954 24. Press F10 to exit the Hot-Plug Manager. If you have added, removed, or replaced any adapters, run the diag -a command. If the system responds with a menu or prompt, follow the instructions to complete the device configuration. Eserver pSeries 690 Service Guide...
  • Page 955 Installing a New Hot-Pluggable PCI Adapter: Note: Before installing a new adapter, ensure the device driver for the adapter is installed. Check with the system administrator if the device driver is not already installed. To install an adapter, perform the following steps: 1.
  • Page 956 The installation instructions for hot-pluggable PCI adapters refer you to these procedures when it is appropriate to perform them. Note: A PCI adapter is only hot-pluggable if the PCI adapter supports hot-plug applications. See the PCI Adapter Placement Reference, order number SA38-0538. Eserver pSeries 690 Service Guide...
  • Page 957 For additional information about taking an adapter offline or removing it from the system configuration, see the AIX System Management Guide: Operating System and Devices. Documentation for the AIX operating system is available from the IBM Eserver pSeries Information Center at http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base. Select AIX documentation.
  • Page 958 PCI slot. Isolate the problem by retrying the operation in a different PCI slot, or trying a different adapter in the slot. If you determine that you have failing hardware, call your service representative. Eserver pSeries 690 Service Guide...
  • Page 959 PCI Adapter or Blank Filler Removal from a Screw Assembly Type Cassette: Note: Before doing the following procedure determine if your PCI adapter cassette is snapped together or held together with three screws. If your PCI adapter cassette is held together with three screws, follow this procedure.
  • Page 960 There are different clips (1) for each adapter type (2): 44P0323 Clip for Gigabit Ethernet FC 2969 type 9U 44P0324 Clip for Ultra3 SCSI FC 6203 Type 4Y 44P0321 Clip for 10/100 BaseT Ethernet FC 4962 Type AF Eserver pSeries 690 Service Guide...
  • Page 961 2. Position the bezel and linkage subassembly with the bezel to the left, on a flat ESD surface. 3. Pivot the bezel so that the lower end is away from the linkage subassembly. Note: Ensure that the top front clip is in the uppermost position before continuing. a.
  • Page 962 Bend the support arm downward, to allow the middle spacer (long cards only) and card arm to slide onto the end of the support arm. b. Slide the card arm until the top-rear and lower clips align with the edge of the card. Eserver pSeries 690 Service Guide...
  • Page 963 c. Press the lower clip under the bottom edge of the card. The bottom of the clip should be even with the bottom of the card. d. Slide the top rear clip of the card arm downward to engage the top corner of the card. The card should now be securely stabilized in all the clips, as shown in the following illustration.
  • Page 964 7. Position the bezel fully onto the assembly by snapping the three small holes on bezel arm over the three small embossments on the linkage assembly, as shown in the following illustration. 1 Alignment Studs 2 Adapter Card 3 ESD Surface Eserver pSeries 690 Service Guide...
  • Page 965 8. Secure the bezel arm to the linkage assembly with three small screws in the sequence shown in the following illustration. 1 Retaining Screws 9. With the tailstock to the left on a flat surface, position the cover over the linkage assembly. 10.
  • Page 966 15. Visually inspect the assembly and ensure that the following are correct: v The card moves up and down correctly when the handle is raised and lowered. v The tailstock clip rides within the bezel opening. Eserver pSeries 690 Service Guide...
  • Page 967 PCI Adapter or Blank Filler Removal from a Snap-Assembly-Type Cassette: CAUTION: Metal edges might be sharp. Note: Before doing the following procedure determine if your PCI adapter cassette is snapped together or held together with three screws. If your PCI adapter cassette is held together with three screws, go to “PCI Adapter or Blank Filler Removal from a Screw Assembly Type Cassette”...
  • Page 968 2. Using two fingers, remove the bushing-lock pin from the bushing. The bushing-lock pin can be removed by pulling it out of the bushing with your fingernails. 1 Bushing 2 Bushing-Lock Pin 1 Bushing-Lock Pin Eserver pSeries 690 Service Guide...
  • Page 969 3. Remove the bushing. The bushing can be removed by pulling it out of the PCI adapter cassette assembly with your fingernails. 1 Bushing 4. Turn over the PCI adapter cassette assembly so that the top is facing away from you. 1 Top of Adapter 2 Handle Chapter 9.
  • Page 970 Using one hand, pinch the plastic latch fingers, and with your other hand, carefully lift the top part of the bezel extension out until the tabs clear the slots in the PCI adapter cassette assembly. 1 Slots 2 Tab 3 Bezel Extension Eserver pSeries 690 Service Guide...
  • Page 971 c. While holding the bezel extension out, push the plastic cover latch out of the bezel hook, as shown in the following illustration. This action allows the bezel to be removed. 1 Bezel Extension 2 Plastic Cover Latch in Bezel Hook d.
  • Page 972 While holding the bezel extension out, carefully slide the bezel off. You might have to work from both sides to loosen the bezel assembly from the cassette assembly. When the bezel is free, slide it completely off the cassette assembly, and set it aside. 1 Bezel Extension 2 Bezel 1 Bezel Eserver pSeries 690 Service Guide...
  • Page 973 6. Turn over the cassette so that the cover is facing up, as shown in the following illustration. Remove the cover from the cassette as follows: a. Slide the cover until it releases from the cassette assembly. Attention: The cover might be tight and difficult to slide. If you grasp the left end (handle end) of the cassette and the right end of the cover, you can use enough force to pull the cover off the PCI adapter cassette assembly.
  • Page 974 (long adapter arm). If you are removing a short adapter or blank filler, see “Short Adapter or Blank Filler Removal” on page 959. If you are removing a long adapter, see “Long Adapter Removal” on page 962. Eserver pSeries 690 Service Guide...
  • Page 975 Short Adapter or Blank Filler Removal: To remove a short adapter or blank filler, do the following: Slide the long and short adapter arms away from the adapter or blank filler by doing the following: Each adapter arm has a release tab that allows the arm to be moved away from the adapter or blank filler in the cassette assembly.
  • Page 976 1 Short PCI Adapter Card 2 Short Adapter Arm 3 Middle-Spacer Arm 4 Long Adapter Arm 5 Long PCI Adapter Card Eserver pSeries 690 Service Guide...
  • Page 977 2. Remove the adapter or blank filler from the cassette linkage assembly by rotating the bottom of the tailstock out, as shown in the following illustration. Store the adapter or blank filler in a safe place. 1 Cassette Linkage Assembly 2 Bottom of Tailstock 3 Handle 3.

  • Page 978: Replacing An Adapter In A Pci Adapter Cassette

    See the illustration on page 960. To install a short adapter into a cassette see “Replacing an Adapter in a PCI Adapter Cassette.” Replacing an Adapter in a PCI Adapter Cassette CAUTION: Metal edges might be sharp. Eserver pSeries 690 Service Guide...
  • Page 979 This procedure is performed when preparing to install a new adapter or a blank filler in the processor subsystem or an I/O drawer. Familiarize yourself with the entire procedure before performing the following steps. 1. Place the empty PCI Adapter Cassette Assembly linkage on a flat work surface in front of you. Position the cassette so that the handle is in the raised (up) position, and on the left, with the top of the linkage facing away from you.
  • Page 980 5700 IBM Gigabit Ethernet-SX PCI-X Adapter 53P5450 5701 IBM 10/100/1000 Base-TX Ethernet PCI-X Adapter 53P5450 5706 IBM 2-Port 10/100/1000 Base-TX Ethernet PCI-X Adapter 53P5450 5707 IBM 2-Port Gigabit Ethernet-SX PCI-X Adapter 53P5450 6203 PCI Dual Channel Ultra3 SCSI Adapter 44P2661...
  • Page 981 2. To determine if you are installing a long adapter or a short adapter, use the following steps. If you know the length of your adapter, skip the following steps and proceed to step 3 on page 967. a. Remove the adapter from its protective packaging and, if present, remove the plastic extension handle from the end of the adapter.
  • Page 982 Ensure that the corner on the left end of the adapter is still aligned into the top adapter-retaining clip, and determine the length of the adapter. LONG SHORT 1 Top Adapter-Retaining Clip 2 Long Adapter-Retaining Arm and Clip Eserver pSeries 690 Service Guide...

  • Page 983: Short Adapter Or Blank Filler Installation

    3. Remove the adapter or blank filler and ensure that the handle is in the up position. If you need to move the handle, ensure that the locking bar is pulled into the unlocked position, and then rotate the adapter handle until the handle is in the up position (the cassette linkage assembly will extend down beyond the cassette top).
  • Page 984 1. Place the adapter or blank filler into the cassette so that the upper-left corner of the adapter engages the adjustable top adapter-retaining clip as shown in the following illustration. 1 Cassette Linkage Assembly 2 Bottom of Tailstock 3 Retaining Clip 4 Handle Eserver pSeries 690 Service Guide...
  • Page 985 2. Rotate the adapter so that the adapter engages the slot in the bottom adapter-retaining clip and the top corner of the adapter is seated into the adjustable top adapter-retaining clip. Note: If the adapter is not a full-height adapter, you must slide the adjustable top adapter-retaining clip downward until the lower edge of the adapter is seated into the slot on the bottom adapter-retaining clip.
  • Page 986 1 Short-adapter Retaining Arm 2 Adapter or Blank Filler 3 Cassette Linkage Rail Eserver pSeries 690 Service Guide...
  • Page 987 4. Ensure that the adjustable top retaining clip catches the corner of the adapter as shown in the following illustration: 1 Short Adapter Top Retaining Clip 5. Use the lower short adapter arm clip to engage and hold the bottom of the adapter. Note: It might be necessary to apply pressure to engage and hold the bottom of the adapter.
  • Page 988 6. To hold the top of the adapter, slide down the adjustable top adapter-retaining clip on the retaining arm. Ensure that the bottom edge of the adapter is held by the lower part of the adapter retaining arm. 1 Adjustable Top Adapter-Retaining Clip Eserver pSeries 690 Service Guide...
  • Page 989 7. Press the lock on the handle, and rotate the adapter handle until it is in the down position (adapter or blank filler moves up into the cassette assembly). 1 Handle Release Lever 2 Lock Ensure that the right end of the cassette linkage rail moves up into the cassette linkage assembly as shown in the following illustration: 1 Right End of Cassette Linkage Chapter 9.
  • Page 990 8. Position the adapter and cassette assembly with the handle on the left (in the down position) and the top facing away from you. 1 Top of Cassette 2 Handle Eserver pSeries 690 Service Guide...
  • Page 991 9. Install the cover on the cassette assembly, as follows: a. Place the cassette cover on the cassette assembly as shown in the following illustration. Slide the cover toward the handle until the hole in the cover aligns with the hole in the cassette assembly. 1 Handle 2 Holes Aligned Chapter 9.
  • Page 992 Carefully slide the bezel onto the cassette assembly. 1 Bezel Align and insert the cover arm latch in the hooked notch in the bezel. 1 PCI Adapter Pull Tab 2 Hooked Notch in the Bezel for the Cover Arm Latch Eserver pSeries 690 Service Guide...
  • Page 993 c. Align the top of the bezel assembly into the grooves on the top of the cassette assembly. Push the bezel onto the cassette linkage assembly until the tab on the top of the bezel is seated in the recess of the cassette assembly. 1 Recess 3 Tab 2 Groove...
  • Page 994 The bezel tab should be seated as shown in the following illustration. 1 Pin b. Ensure that the cover arm latch is completely pressed into the hooked notch on the bezel as shown. 1 PCI Adapter Pull Tab 2 Hooked Notch in the Bezel Eserver pSeries 690 Service Guide...
  • Page 995 c. Turn the cassette assembly over so the cover is facing up. Check the cover latch to ensure that it is holding the bezel to the cover as shown. 1 Cover Latch 12. Ensure the holes are aligned, and insert the bushing-lock pin into the bushing as shown. 1 Bushing 2 Bushing-Lock Pin Chapter 9.
  • Page 996 1 Location of the Installed Bushing and Bushing-Lock Pin 13. Insert the bushing-lock pin into the hole in the bushing, and push it in until it seats as shown in the following illustration. 1 Bushing-Lock Pin Eserver pSeries 690 Service Guide...
  • Page 997 14. Depress the handle release lever to ensure the locking bar on the handle is pulled into the unlocked position. Raise the handle on the cassette linkage assembly until it locks into the up position (the blank filler or adapter moves downward). 1 Handle Release Lever 2 Locking Bar 15.
  • Page 998 1 Metal EMC Shield b. The metal EMC shield has clips that slide over the top of the tailstock. Ensure that these clips are holding the metal EMC shield to the tailstock. 1 Top of Tailstock Eserver pSeries 690 Service Guide...
  • Page 999 16. Depress the handle release lever on the handle, and rotate the adapter handle until the handle is in the down position (adapter or blank filler moves up into the cassette assembly). 1 Handle 17. Using the system documentation, determine if the adapter you are installing is hot-swappable. If the adapter is hot-swappable, move the slider on the color indicator to allow the orange color to be visible.
  • Page 1000 1 Embossed Middle-Spacer Alignment 4 Adapter Connector (Leading Edge) Lines 2 Top Cassette Rail 5 Long Adapter Card 3 Middle-Spacer Arm 6 Long Adapter Arm Eserver pSeries 690 Service Guide...
  • Page 1001 3. Place the adapter into the cassette so that the upper-left corner of the adapter engages the top adjustable adapter-retaining clip as shown in the following illustration: 1 Top Adapter-Retaining Clip 3 Adapter 2 Cassette Linkage Assembly 4 Bottom of Tailstock 5 Handle Chapter 9.

Table of Contents