free hit counter
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
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: Service Manual, User Manual
ERserver
pSeries 690
Service Guide
SA38-0589-04

Advertisement

Table of Contents
loading

Related Manuals for IBM pSeries 690

Summary of Contents for IBM pSeries 690

  • Page 1 ERserver pSeries 690 Service Guide SA38-0589-04...
  • Page 3 ERserver pSeries 690 Service Guide SA38-0589-04...
  • Page 4 © Copyright International Business Machines Corporation, 2001, 2003. 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 ....61 IBM Hardware Management Console for Eserver pSeries (HMC) to the Primary I/O Book ..62 System Memory ....... . . 63 Memory to Processor Relationships .
  • Page 7 ....... 155 Service Agent for the Eserver pSeries 690 ..... . 156 Using the Service Processor and Service Agent Features .
  • Page 8 Running Standalone Diagnostics from a Network Installation Management (NIM) Server ..752 Booting Standalone Diagnostics from the NIM Server on a System with an HMC Attached ..753 Eserver pSeries 690 Service Guide...
  • Page 9 Booting Standalone Diagnostics from the NIM Server on a System with No HMC Attached ..754 Chapter 7. Using the Service Processor ..... . . 755 Service Processor Menus .
  • Page 10 Updating Xilinx Code on an SP Switch2 PCI Attachment Adapter ... . . 967 Hot-Plug Steps for the SP Switch2 PCI Attachment Adapter ....969 viii Eserver pSeries 690 Service Guide...
  • Page 11 Customizing the Modem Configuration Files ..... 1024 IBM 7852-400 DIP Switch Settings ......1024 Xon/Xoff Modems .
  • Page 12 Index ........1051 Eserver pSeries 690 Service Guide...

  • Page 13: 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 xii v 190 v 824 v 843 v 971 A caution notice indicates the presence of a hazard that has the potential of causing moderate or minor personal injury.
  • Page 14 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. Eserver pSeries 690 Service Guide...

  • Page 15: 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 16 Eserver pSeries 690 Service Guide...

  • Page 17: 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 18 Eserver pSeries 690 Service Guide...

  • Page 19: About This Book

    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 20: Trademarks

    AIX v Electronic Service Agent v Eserver ® v IBM v LANstreamer v pSeries v RS/6000 Other company, product, and service names may be trademarks or service marks of others. xviii Eserver pSeries 690 Service Guide...

  • Page 21: 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 22 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 23: 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 24: 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 25: 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 26 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 27 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 28 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 29 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 30: 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 31: Trial Capacity On Demand

    For further information about activating and deactivating On/Off Capacity on Demand 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 that was delivered with your hardware management console.

  • Page 32: 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 33: Activation Process For Cuod Features

    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 34: Pseries 690 Data Flow

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

  • Page 35: 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 36: Key

    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 37 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 38 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 39: Uepo Switch

    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 40: 7040 Model 681 Processor Subsystem Locations

    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 41 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 42 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 43: Media Subsystem Locations

    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 44: 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 45: 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 46 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 47: 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 48: 7040 Model 61D I/O Subsystem Rear View

    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 49: I/O Subsystem Dasd Locations

    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 50: I/O Subsystem Pci And Pci-X Phb And Pci And Pci-X Slot Locations

    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 51: I/O Subsystem Internal Scsi Distribution

    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 52: Power Subsystem Locations

    Note: For 32-way 1.7 GHz MCM systems a third BPD was added to increase the amount of power needed by the system. 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 53: 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 54 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 55 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 56: 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 57 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 58: 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 59: 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 60: I/O Subsystem Positions, Fully Populated Primary And Secondary Rack (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 61: I/O Subsystem Positions, Fully Populated Primary And Secondary Rack (Rear View With Ibfs)

    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 62: Placement Of Subsystem 4 In A Two-Rack Configuration (Rear View With Ibf)

    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 63: Rio And Rio-2 Cabling Rules

    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 64 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 65: 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

    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 66: I/O Subsystems (5 And 6) Rio Cabling To The Secondary I/O Book, Two I/O Planar Loop Configuration, 3 Or 4 Mcms Only

    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 67: I/O Subsystems (7 And 8) Rio Cabling To The Third I/O Book, Two I/O Planar Loop Configuration, 4 Mcms Only

    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 68: I/O Subsystems (1 Through 3 With Ibfs) Rio Cabling To I/O Books, Two I/O Planar Loop Configuration, 2, 3, Or 4 Mcms Only

    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 69: 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

    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 70: I/O Subsystems (1 Through 4 Without Ibfs) Rio-2 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-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, Two I/O Planar Loop Configuration, 2 Mcms Only

    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 72: I/O Subsystems (5 And 6) Rio-2 Cabling To The Secondary I/O Book, Two I/O Planar Loop Configuration, 3 Or 4 Mcms Only

    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 And 8) Rio-2 Cabling To The Third I/O Book, Two I/O Planar Loop Configuration, 3 Or 4 Mcms Only

    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 74: I/O Subsystems (1 Through 4 Without Ibfs) Rio-2 Cabling To I/O Books, One I/O Planar Loop Configuration, 3 Or 4 Mcms Only

    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 75: I/O Subsystems (5 And 6) Rio-2 Cabling To The Secondary I/O Book, One I/O Planar Loop Configuration, 3 Mcms Only

    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 76: I/O Subsystems (5 And 6) Rio-2 Cabling To The Secondary I/O Book, One I/O Planar Loop Configuration, 4 Mcms Only

    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 77: I/O Subsystems (7) Rio-2 Cabling To The Fourth I/O Book, One I/O Planar Loop Configuration, 4 Mcms Only

    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 78: I/O Subsystems (1 Through 3 With Ibfs) Rio-2 Cabling To I/O Books, One I/O Planar Loop Configuration, 3 Or 4 Mcms Only

    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 79: I/O Subsystems (1 Through 3 With Ibfs) Rio-2 Cabling To I/O Books, One I/O Planar Loop Configuration, 2 Mcms Only

    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 80: I/O Subsystem (4 With Ibfs Installed) Rio-2 Cabling To I/O Book 3, One I/O Planar Loop Configuration, 3 Or 4 Mcms Only

    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 81: 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 82: Ibm Hardware Management Console For Eserver Pseries (Hmc) To The Primary I/O Book

    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 83: 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 84 It is recommended that all systems have access to a 4-mm or 8-mm tape drive for submission of system dump information, if required. This function can be accomplished through locally attached or network-attached devices as appropriate. Eserver pSeries 690 Service Guide...

  • Page 85: 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 86 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 87: 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 88: 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 89: 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 90: 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 91: 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. Chapter 1. Reference Information...
  • Page 92 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 93 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 94 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 95 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 96 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 97 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 98 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 99 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 100 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 101 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 102 (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. Primary I/O book-1 Port 1 U1.18-P1-H2/Q3 Connector 2 (2-0) (B0) Eserver pSeries 690 Service Guide...
  • Page 103 Location Physical Logical FRU Name Code Location Connection Connection Code Primary I/O book-1 Port 1 U1.18-P1-H2/Q3# Connector 2 (2-0) Cable 3, 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”...
  • Page 104 (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. I/O Book 1, Port 5 U1.18-P1-H1/Q6 Connector 2 (1-0) (D0) Eserver pSeries 690 Service Guide...
  • Page 105 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Book 1, Port 5 U1.18-P1-H1/Q6# Connector 2 (1-0) Cable 6, 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”...
  • Page 106 (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. I/O Book 2, Port 5 U1.18-P1-H3/Q6 Connector 2 (1-0) (D0) Eserver pSeries 690 Service Guide...
  • Page 107 Location Physical Logical FRU Name Code Location Connection Connection Code I/O Book 2, Port 5 U1.18-P1-H3/Q6# Connector 2 (1-0) Cable 6, 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”...
  • Page 108 U1.18-P1-H4/Q7 Connector 1 (2-1) (B0) I/O Book 3, Port 7 U1.18-P1-H4/Q7# Connector 1 (2-1) Cable I/O Book 3, Port 7 U1.18-P1-H4/Q8 Connector 0 (2-0) (B1) I/O Book 3, Port 7 U1.18-P1-H4/Q8# Connector 1 (2-0) Cable Eserver pSeries 690 Service Guide...
  • Page 109 Location Physical Logical FRU Name Code Location Connection Connection Code DCA 1-RH U1.18-P1-V1 DCA 1- BPA A - BPC - 5 U1.18-P1-V1/Q1 Connector DCA 1- BPA A - BPC -5 U1.18-P1-V1/Q1# Cable DCA 1- BPA B - BPC - 5 U1.18-P1-V1/Q2 Connector DCA 1- BPA B - BPC -5...
  • Page 110 Processor 27 (W/ L1 & U1.18-P1-C2 00-27 L2 Cache) Processor 28 (W/ L1 & U1.18-P1-C2 00-28 L2 Cache) Processor 29 (W/ L1 & U1.18-P1-C2 00-29 L2 Cache) Processor 30 (W/ L1 & U1.18-P1-C2 00-30 L2 Cache) Eserver pSeries 690 Service Guide...
  • Page 111 Location Physical Logical FRU Name Code Location Connection Connection Code Processor 31 (W/ L1 & U1.18-P1-C2 00-31 L2 Cache) MCM Module 1 U1.18-P1-C3 Processor 08 (W/ L1 & U1.18-P1-C3 00-08 L2 Cache) Processor 09 (W/ L1 & U1.18-P1-C3 00-09 L2 Cache) Processor 10 (W/ L1 &...
  • Page 112 Fan Controller 3 TO BPC U1.18-X3/Q2 B Connector Fan Controller 3 TO BPC U1.18-X3/Q2# B Cable Fan Controller U1.18-X4 Assembly 4 Fan Controller 4 TO BPC U1.18-X4/Q1 A Connector Fan Controller 4 TO BPC U1.18-X4/Q1# A Cable Eserver pSeries 690 Service Guide...
  • Page 113 Location Physical Logical FRU Name Code Location Connection Connection Code Fan Controller 4 TO BPC U1.18-X4/Q2 B Connector Fan Controller 4 TO BPC U1.18-X4/Q2# B Cable Fan Assembly 1 U1.18-F1 Fan Assembly 2 U1.18-F2 Fan Assembly 3 U1.18-F3 Fan Assembly 4 U1.18-F4 Location Physical...
  • Page 114 2f-xx or 2g-xx EADS 2 - PCI Controller U1.9-P1 2j-58, 2j-5A, 2j-5E PCI Slot 5 Content U1.9-P1-I5 2k-08 to 2k-0F or 2m-xx or 2n-xx PCI Slot 6 Content U1.9-P1-I6 2p-08 to 2p-0F or 2q-xx or 2r-xx Eserver pSeries 690 Service Guide...
  • Page 115 Location Physical Logical FRU Name Code Location Connection Connection Code PCI Slot 7 Content U1.9-P1-I7 2v-08 to 2v-0F or 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...
  • Page 116 DASD 4-pack Cage and U1.9-P3-N1 card (1) VPD SCSI DASD 1 hdisk at ID U1.9-P2/Z2-A8 3s-08-00-8,0 8 connected to controller 2 on P2 SCSI DASD 2 hdisk at ID U1.9-P2/Z2-A9 3s-08-00-9,0 9 connected to controller 2 on P2 Eserver pSeries 690 Service Guide...
  • Page 117 Location Physical Logical FRU Name Code Location Connection Connection Code 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 SCSI Enclosure Services U1.9-P2/Z2-Bf 3s-08-00-15,0...
  • Page 118 I/O Subsystem 1 Chassis (MT/M Serial #) U1.5 & Midplane Card I/O Subsystem Left IO U1.5-P1 backplane assembly I/O Subsystem Left IO U1.5-P1-N1 backplane assembly VPD EADS 1 - PCI Controller U1.5-P1 40-58, 40-5A, 40-5C, 40-5E Eserver pSeries 690 Service Guide...
  • Page 119 Location Physical Logical FRU Name Code Location Connection Connection Code 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 PCI Slot 4 Content U1.5-P1-I4...
  • Page 120 DCA 2 to (BPA B) BPD1- U1.5-V2/Q1# 1B Cable DCA 2 to (BPA A) BPD1- U1.5-V2/Q2 1B Connector P03 DCA 2 to (BPA A) BPD1- U1.5-V2/Q2# 1B Cable Thermal Sensor U1.5-V2 I/O Subsystem SCSI U1.5-P1/Z1 4M-08 controller 1 on P1 Eserver pSeries 690 Service Guide...
  • Page 121 Location Physical Logical FRU Name Code Location Connection Connection Code 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 DASD 4-pack Cage and U1.5-P3 card (1) DASD 4-pack Cage and...
  • Page 122 I/O Subsystem Fan U1.5-F1 (MSA) 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 Eserver pSeries 690 Service Guide...
  • Page 123 Location Physical Logical FRU Name Code Location Connection Connection Code Media Drawer Power U1.5-P2-X2/Q3# Cable 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...
  • Page 124 DCA 1 to (BPA B) BPD1- U1.1-V1/Q1 1A Connector P04 DCA 1 to (BPA B) BPD1- U1.1-V1/Q1# 1A Cable DCA 1 to (BPA A) BPD1- U1.1-V1/Q2 1A Connector P04 DCA 1 to (BPA A) BPD1- U1.1-V1/Q2# 1A Cable Eserver pSeries 690 Service Guide...
  • Page 125 Location Physical Logical FRU Name Code Location Connection Connection Code 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 DCA 2 to (BPA A) BPD1- U1.1-V2/Q2 1B Connector P05 DCA 2 to (BPA A) BPD1-...
  • Page 126 9 connected to controller 1 on P1 SCSI DASD 3 hdisk at ID U1.1-P1/Z1-Aa 5s-08-00-10,0 A connected to controller 1 on P1 SCSI DASD 4 hdisk at ID U1.1-P1/Z1-Ab 5s-08-00-11,0 B connected to controller 1 on P1 Eserver pSeries 690 Service Guide...
  • Page 127 Location Physical Logical FRU Name Code Location Connection Connection Code 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) Media Drawer Power...
  • Page 128 85-xx or 86-xx PCI Slot 7 U1.13-P2-I7 8A-08 to 8A-0F or 8B-xx or 8C-xx EADS 3 - PCI Controller U1.13-P2 8E-58, 8E-5A, 8E-5E PCI Slot 8 U1.13-P2-I8 8F-08 to 8F-0F or 8G-xx or 8H-xx Eserver pSeries 690 Service Guide...
  • Page 129 Location Physical Logical FRU Name Code Location Connection Connection Code PCI Slot 9 U1.13-P2-I9 8J-08 to 8J-0F or 8K-xx or 8L-xx PCI Slot 10 U1.13-P2-I10 8Q-08 to 8Q-0F or 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...
  • Page 130 8 connected to controller 2 on P1 SCSI DASD 2 hdisk at ID U1.13-P1/Z2-A9 7b-08-00-9,0 9 connected to controller 2 on P1 SCSI DASD 3 hdisk at ID U1.13-P1/Z2-Aa 7b-08-00-10,0 A connected to controller 2 on P1 Eserver pSeries 690 Service Guide...
  • Page 131 Location Physical Logical FRU Name Code Location Connection Connection Code SCSI DASD 4 hdisk at ID U1.13-P1/Z2-Ab 7b-08-00-11,0 B connected to controller 2 on P1 SCSI Enclosure Services U1.13-P1/Z2-Af 7b-08-00-15,0 SES connected to controller 2 on P1 DASD 4-pack Cage and U1.13-P6 card (4) DASD 4-pack Cage and...
  • Page 132 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 133 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 134 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 135 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 136 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 137 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 138 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 139 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 140 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 141 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 142 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 143 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 144 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 145 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 146 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 147 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 148 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 149 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 150 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 151 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 152 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 153 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 154: 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 155: Number Of Bulk Power Regulators (Bpr) Fc 6186 Required As A Function Of Mcms And I/O Drawers

    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 156 6 BPRs U2.1 Front BPA U1.35-P1-V1 U1.35-P1-V2 U1.35-P1-V3 Back BPA U1.35-P2-V1 U1.35-P2-V2 U1.35-P2-V3 6 I/O Drawer Location 6 BPRs 6 BPRs U2.5 7 I/O Drawer Location 6 BPRs U2.13 8 I/O Draw Location 6 BPRs U2.19 Eserver pSeries 690 Service Guide...

  • Page 157: 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 158 The following figure shows a way to balance the load without changing the wiring on the output of any breakers. The three-pole breakers are alternated with single-pole breakers, so that the three-pole breakers do not all begin on Phase A. Eserver pSeries 690 Service Guide...
  • Page 159 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. Chapter 1. Reference Information...
  • Page 160 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) Eserver pSeries 690 Service Guide...

  • Page 161: 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 162 Acoustical Doors 1022 1137 1509 1583 1658 1733 Without IBF No Doors With IBF 994 1069 1144 1595 1696 1770 1845 1920 No Doors Without 1044 1429 1504 1579 1653 Note: Italicized numbers indicate single-frame systems. Eserver pSeries 690 Service Guide...

  • Page 163: Weight Distribution

    Acoustical Noise Emissions Acoustical Characteristic Product Configuration Declared A-Weighted Sound Power Declared A-Weighted Sound Pressure Level, L Level, LpAm (dB) Operating Idle Operating Idle 7040 Acoustical Doors 7040 Slimline Doors Notes: 1. Noise levels cited are for a typical configuration (A-Frame: Bulk Power, CEC cage, battery option, media drawer, and two I/O drawers).
  • Page 164 36 in. for 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 165 The following table shows floor-loading specifications for systems with acoustical covers. The values contained in the Condition column are described following the table. Condition a (sides) b (front) c (back 1 Frame 2 Frames mm (in.) mm (in.) mm (in.) kg/m (lb./ft.
  • Page 166 Plan Views The following illustration shows dimensional planning information for single-frame systems and double-frame systems. Eserver pSeries 690 Service Guide...

  • Page 167: Total System Power Consumption

    Total System Power Consumption The following tables contain minimum and maximum power consumption for the 1.1 and 1.3 GHz pSeries 690. Minimum power consumption is based on a configuration consisting of a single 4 GB memory card, 1 PCI card per I/O subsystem, and 1 DASD device per I/O subsystem. Maximum power consumption is based on a configuration consisting of two 32 GB memory cards per MCM module, maximum PCI cards (20 per I/O drawer), and maximum DASD (16 per I/O drawer).
  • Page 168 4614 6172 7730 2207 3091 3975 4859 4104 5662 7220 8778 3459 4343 5227 6710 8268 9826 3827 4711 5595 7758 9316 10874 5079 5963 10364 11922 5447 6331 11412 12970 6699 14018 7067 15066 Eserver pSeries 690 Service Guide...
  • Page 169 Number of I/O 1.7 GHz 8-way Modules (minimum power 1.7 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 2017 3079 4141 5203 3234 4970 6706 8442 2385 3447 4509 5571...

  • Page 170: Service Inspection Guide

    To maintain proper airflow, the air filters (part number 11P3781) must be inspected every six months and replaced as necessary. To replace the air filters, it is not necessary to remove power from the system or blower assemblies. Eserver pSeries 690 Service Guide...
  • Page 171 Removal To remove the air filters from the processor subsystem, grasp the finger tabs located on the air filter and pull the air filter straight out from the processor subsystem. 1 Top Filter Pull Tab 5 Bottom Filter 2 Top Filter Key 6 Bottom Filter Key 3 Processor Subsystem 7 Bottom Filter Pull Tab...
  • Page 172 Eserver pSeries 690 Service Guide...

  • Page 173: 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 174 For a list of the checkpoints, see Chapter 4, “Checkpoints”, on page 353. 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 175: 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 176: 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 177: 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 178 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 159. Eserver pSeries 690 Service Guide...

  • Page 179: Quick Entry Map

    Quick Entry MAP Quick Entry MAP Table of Contents Problem Description Page No. Service actions The system attention LED on the media subsystem operator panel is on. OK does not appear in the media subsystem operator panel display before pressing the power-on button.
  • Page 180 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 984. 3. Replace the primary I/O book, Location: U1.18-P1-H2. Refer to “I/O Books and I/O Blanks” on page 838. Eserver pSeries 690 Service Guide...
  • Page 181 Symptom Action You have a blank display on the operator panel. Other Go to “MAP 1520: Power” on page 190. 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 182 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 183 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 184 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 185 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 186: 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 187 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 188 Go to “Step 1020-4” on page 170. All other symptoms. If you were directed here from the Entry MAP, go to “MAP 1542: I/O Problem Isolation” on page 306. Otherwise, find the symptom in the “Entry MAP” on page 157. Eserver pSeries 690 Service Guide...
  • Page 189 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 190 Look up the error in the Chapter 5, “Error Code to FRU Index”, on page 391 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 306. Eserver pSeries 690 Service Guide...

  • Page 191: 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 192: 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”. Go to “Step 1321-18” on page 174. Step 1321-7 Are there any serviceable events with FRU location codes reported in “Step 1321-5”? Eserver pSeries 690 Service Guide...
  • Page 193 Go to “Step 1321-14”. 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. Step 1321-9 Examine the list of error codes you obtained from “Step 1321-8” and look for any of the form 4xxB xxxx, A0D-34x, or A1D-34x.
  • Page 194 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). Eserver pSeries 690 Service Guide...
  • Page 195 Step 1321-23 Is Linux usable in any partition with Linux installed? Go to “Step 1321-30” on page 177. Go to “Step 1321-24”. Attention: “Step 1321-24” through “Step 1321-36” on page 178 must be performed on a partition running the Linux operating system. Step 1321-24 If your system is functional, examine the Linux system log by logging in to the system as the root user and entering the following command:...
  • Page 196 <3>RTAS: WARNING: (FULLY RECOVERED) type: INTERN_DEV_FAIL <3>RTAS: initiator: UNKNOWN target: UNKNOWN <3>RTAS: Status: unrecoverable new <3>RTAS: Date/Time: 20020905 15372200 <3>RTAS: CPU Failure <3>RTAS: Internal error (not cache) <3>RTAS: CPU id: 0 <3>RTAS: Failing element: 0x0000 <3>RTAS: -------- event-scan end --------- Eserver pSeries 690 Service Guide...
  • Page 197 Step 1321-29 Record any extended data found in the Linux system log in Step 1321-24 or the Linux boot (IPL) log in Step 1321-26. Be sure to record word 13. Note: The line(s) in the Linux extended data that begin with ″<4>RTAS: Log Debug: 04″ contain the error code listed in the next 8 hex characters.
  • Page 198 2. Replace the device (for example, tape or DASD) 3. If applicable, replace the device backplane. 4. Replace the device cable. 5. Replace the adapter. 6. If the adapter resides in an I/O drawer, replace the I/O backplane. Eserver pSeries 690 Service Guide...
  • Page 199 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 178. 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”...
  • Page 200 Go to the “Quick Entry MAP” on page 159 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 Begin a new list of “Axx” partitions by copying the list of partitions obtained in “Step 1322-11”. Go to “Step 1322-16” on page 183. 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 182. If you are referred to the list of partition(s) obtained in “Step 1322-11” on page 182 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 181 been processed? Go to “Step 1322-5” on page 181 and process the next service action event in the list of serviceable events recorded in “Step 1322-4” on page 181. Go to “Step 1322-34” on page 185. 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 182? 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 187. Go to “Step 1421-5”. Step 1421-5 Shut down the partition. Eserver pSeries 690 Service Guide...

  • Page 207: Map 1422: Slot Is Empty Even When Populated

    Step 1421-6 Is the PCI slot power LED of the location recorded in “Step 1421-3” on page 186 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 189. 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 187 into the slot assigned in “Step 1422-10” on page 188. Step 1422-12 Move any external cabling from the adapter in the slot recorded in “Step 1422-1” on page 187 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 208. 101A F806 or 101A F906 for BPC A Go to “MAP 152a: Loss of ac Power or Phase Missing” on page 210. 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 291. 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 195. Go to “Step 1521-5” on page 195. 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

    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 199. Go to “Step 1524-2” on page 199. Eserver pSeries 690 Service Guide...
  • Page 219 Step 1524-2 1. Set UEPO switch on both BPCs to the BYPASS position. 2. Unplug the customer room EPO cable. 3. Set switch (J4) on the UEPO panel to EPO BYPASS position. 4. Set UEPO switch on both BPCs back to the NORMAL position. 5.

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

    The following steps check all the BPRs on the side of the BPA (A or B) referenced by the error code that sent you to this MAP. Are there any remaining BPRs to be checked? Go to “Step 1525-3” on page 201. Go to “Step 1525-4” on page 201. Eserver pSeries 690 Service Guide...
  • Page 221 Step 1525-3 Notes: 1. This problem can be caused by any BPD plugged into the failing BPA. 2. The system can have up to three BPDs, depending on the system configuration. 3. Each BPD on the failing BPA must be checked independently. The following steps check all the BPDs on the side of the BPA (A or B) referenced by the error code that sent you to this MAP.
  • Page 222 Is the error code that sent you to this MAP 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 223: Map 1526: There Is An Integrated Battery Feature (Ibf) Failure

    MAP 1526: There Is An Integrated Battery Feature (IBF) Failure Step 1526-1 Is the IBF feature installed? Replace the BPR that is connected to the IBF referenced in the error code that brought you to this MAP. Follow all steps in the removal and replacement procedures in “Bulk Power Regulator (BPR)”...
  • Page 224 Replace the IBF referenced in the error code that brought you to this MAP. Follow all steps in the removal and replacement procedures in “Integrated Battery Feature (IBF)” on page 835. Go to “Step 1526-7” on page 205. Eserver pSeries 690 Service Guide...
  • Page 225 Step 1526-6 Set the breaker to the on (down) position. Wait 10 seconds after the LED on the IBF referenced in the error code that brought you to this MAP comes on. Does the circuit breaker remain on? Exchange the following FRUs one at a time: v The BPR that is connected to the IBF referenced in the error code that brought you to this MAP.

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

    Reinstall the blower or fans removed earlier and go to “Step 1527-5” ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Step 1527-5 Call your next level of support. Eserver pSeries 690 Service Guide...

  • Page 227: 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 228: 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 229 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 230: Map 152A: Loss Of Ac Power Or Phase Missing

    “Bulk Power Controller (BPC)” on page 830. 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 833. Eserver pSeries 690 Service Guide...
  • Page 231 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 232: Map 152B: 2.5 V Current/Voltage Problem In Processor Subsystem

    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 152b-11” on page 213. Eserver pSeries 690 Service Guide...
  • Page 233 Step 152b-11 Have all the books listed in step 152b-4 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 234 Turn on the power. Step 152b-26 Did the system stop with the same error code as recorded in “Step 152b-1” on page 212? Go to “Step 152b-32” on page 215. Go to “Step 152b-27” on page 215. Eserver pSeries 690 Service Guide...
  • Page 235 Step 152b-27 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. Step 152b-28 Reinsert one of the books that is pulled out and listed in “Step 152b-24” on page 214. Step 152b-29 Turn on the power.
  • Page 236 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152b-42”. Call for support. Step 152b-42 Attention: Before replacing the system backplane, call for support. Replace the system backplane at location U1.18-P1. Eserver pSeries 690 Service Guide...
  • Page 237 Step 152b-43 Turn on the power. Step 152b-44 Did the system stop with the same error code as recorded in “Step 152b-1” on page 212? Go to “Step 152b-45”. The system backplane was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...

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

    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 152c-11” on page 219. Eserver pSeries 690 Service Guide...
  • Page 239 Step 152c-11 Have all the books listed in “Step 152c-4” on page 218 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 240 Turn on the power. Step 152c-26 Did the system stop with the same error code as recorded in “Step 152c-1” on page 218? Go to “Step 152c-32” on page 221. Go to “Step 152c-27” on page 221. Eserver pSeries 690 Service Guide...
  • Page 241 Step 152c-27 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. Step 152c-28 Reinsert one of the books that is pulled out and listed in “Step 152c-24” on page 220. Step 152c-29 Turn on the power.
  • Page 242 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152c-41 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152c-42” on page 223. Call for support. Eserver pSeries 690 Service Guide...
  • Page 243 Step 152c-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 244 Step 152c-55 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”. Eserver pSeries 690 Service Guide...

  • Page 245: 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 246 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 247 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 225? Go to “Step 152d-22” on page 228. Go to “Step 152d-17”. Step 152d-17 One of the books just removed is defective. Turn off the power.
  • Page 248 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 249 Step 152d-30 Did the system stop with the same error code as recorded in “Step 152d-1” on page 225? 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 250 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 231. Call for support. Eserver pSeries 690 Service Guide...
  • Page 251 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 252 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”. Eserver pSeries 690 Service Guide...

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

    MAP 152e: 1.5 V CPU Current/Voltage Problem in Processor Subsystem Step 152e-1 Record the error code and the location code(s) that sent you to this MAP. Step 152e-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152e-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152e-4”.
  • Page 254 DCA 2, at location U1.18-P1-V2 v DCA 3, at location U1.18-P1-V4 v DCA 4, at location U1.18-P1-V5 v DCA 5, at location U1.18-P1-V6 v DCA 6, at location U1.18-P1-V8 Step 152e-15 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 255 Step 152e-16 Did the system stop with the same error code as recorded in “Step 152e-1” on page 233? Go to “Step 152e-17”. 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 256 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. Go to “Step 152e-25”. Eserver pSeries 690 Service Guide...
  • Page 257 Step 152e-30 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152e-31 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152e-32”. Call for support. Step 152e-32 Attention: Before replacing the system backplane, call for support. Replace the system backplane, at location U1.18-P1.

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

    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. Step 152f-8 Reinsert one of the books that is pulled out and listed in “Step 152f-4”. Eserver pSeries 690 Service Guide...
  • Page 259 Step 152f-9 Turn on the power. Step 152f-10 Did the system stop with the same error code as recorded in “Step 152f-1” on page 238? 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 260 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152f-18”. Step 152f-22 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Eserver pSeries 690 Service Guide...
  • Page 261 Step 152f-23 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152f-24”. Call for support. Step 152f-24 Pull out the following books about 25 mm (1 inch), if present: v Secondary I/O book, at location U1.18-P1-H3 v Third I/O book, at location U1.18-P1-H4 v Fourth I/O book, at location U1.18-P1-H1 Step 152f-25...
  • Page 262 Remove the new book that was just installed in “Step 152f-34” and reinstall the original book. Step 152f-39 Have all the books listed in “Step 152f-34” been replaced with new or original books? Go to “Step 152f-40” on page 243. Go to “Step 152f-34”. Eserver pSeries 690 Service Guide...
  • Page 263 Step 152f-40 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 152f-41 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 152f-42”. Call for support. Step 152f-42 Remove the system clock card, at location U1.18-P1-X5.
  • Page 264 Step 152f-55 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”. Eserver pSeries 690 Service Guide...

  • Page 265: 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 266 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 267 Step 152g-16 Did the system stop with the same error code as recorded in “Step 152g-1” on page 245? 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 268 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 249. Eserver pSeries 690 Service Guide...
  • Page 269 Step 152g-31 Have all the books listed in “Step 152g-24” on page 248 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 270 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 271: 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 272 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 253. Call for support. Eserver pSeries 690 Service Guide...
  • Page 273 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 274 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 275 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 251? 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 276 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 277 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 278 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 279: 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 280 Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152i-19 Reinsert one of the cards that is removed and listed in “Step 152i-15”. Eserver pSeries 690 Service Guide...
  • Page 281 Step 152i-20 Turn on the power. Step 152i-21 Did the system stop with the same error code as recorded in “Step 152i-1” on page 259? 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 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 Eserver pSeries 690 Service Guide...
  • Page 283 Step 152i-36 Turn on the power. Step 152i-37 Did the system stop with the same error code as recorded in “Step 152i-1” on page 259? Go to “Step 152i-43”. Go to “Step 152i-38”. Step 152i-38 One of the cards just removed is defective. Turn off the power.
  • Page 284 One of the DASD in the DASD 4-pack 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 152i-52” on page 265. Eserver pSeries 690 Service Guide...
  • Page 285 Step 152i-52 Have all the cards listed in “Step 152i-45” on page 264 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 286 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152i-67 Have all the cards listed in “Step 152i-63” been replaced? Call for support. Go to “Step 152i-63”. Eserver pSeries 690 Service Guide...

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

    MAP 152j: 2.5 V Current/Voltage Problem in I/O Subsystem Step 152j-1 Record the error code and location code(s) that sent you to this MAP. Step 152j-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 288 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152j-14 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152j-15” on page 269. Call for support. Eserver pSeries 690 Service Guide...
  • Page 289 Step 152j-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 152j-16 Turn on the power.
  • Page 290 Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152j-29 Reinsert one of the cards that is removed and listed in “Step 152j-25”. Eserver pSeries 690 Service Guide...
  • Page 291 Step 152j-30 Turn on the power. Step 152j-31 Did the system stop with the same error code as recorded in “Step 152j-1” on page 267? 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 292 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152j-39”. Step 152j-43 Turn off the power. Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Eserver pSeries 690 Service Guide...
  • Page 293 Step 152j-44 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152j-45”. Call for support. Step 152j-45 Replace the cards in the following list one at a time and in the order listed: v DCA 1 at V1 v DCA 2 at V2 Step 152j-46...
  • Page 294 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152j-57 Have all the cards listed in “Step 152j-53” been replaced with new or original cards? Call for support. Go to “Step 152j-53”. Eserver pSeries 690 Service Guide...

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

    MAP 152k: 12.0 V Current/Voltage Problem in I/O Subsystem Step 152k-1 Record the error code and location code(s) that sent you to this MAP. Step 152k-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 296 Examine the green ″power good out″ LEDs of both I/O subsystem DCAs. Step 152k-14 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152k-15” on page 277. Call for support. Eserver pSeries 690 Service Guide...
  • Page 297 Step 152k-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 152k-16 Turn on the power.
  • Page 298 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152k-29 Reinsert one of the cards that is removed and listed in “Step 152k-25”. Step 152k-30 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 299 Step 152k-31 Did the system stop with the same error code as recorded in “Step 152k-1” on page 275? 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.
  • Page 300 Did the system stop with the same error code as recorded in “Step 152k-1” on page 275? Go to “Step 152k-53” on page 282. Go to “Step 152k-48”. Step 152k-48 One of the DASDs just removed is defective. Turn off the power. Eserver pSeries 690 Service Guide...
  • Page 301 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Chapter 3. Maintenance Analysis Procedures...
  • Page 302 The part 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 303 Step 152k-58 Turn off the power. Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152k-59 Remove the new card that was just installed in “Step 152k-55” on page 282 and reinstall the original card. Step 152k-60 Have all the cards listed in “Step 152k-55”...

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

    Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152l-9 Reinsert one of the cards that is removed and listed in “Step 152l-5”. Step 152l-10 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 305 Step 152l-11 Did the system stop with the same error code as recorded in “Step 152l-1” on page 284? 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.
  • Page 306 Remove the following adapter cards, if present, from the I/O subsystem. Record the adapter locations: v Adapter card at P2-I1 v Adapter card at P2-I2 v Adapter card at P2-I3 v Adapter card at P2-I4 v Adapter card at P2-I5 Step 152l-26 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 307 Step 152l-27 Did the system stop with the same error code as recorded in “Step 152l-1” on page 284? Go to “Step 152l-33”. Go to “Step 152l-28”. Step 152l-28 One of the cards just removed is defective. Turn off the power. Make sure all the green ″power good out″...
  • Page 308 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 152l-39”. Step 152l-43 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 152l-44 Are all the green ″power good out″ LEDs of both I/O subsystem DCAs off? Go to “Step 152l-45”. Call for support. Step 152l-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 152l-46...
  • Page 310 Make sure all the green ″power good out″ LEDs of both I/O subsystem DCAs are off. Step 152l-57 Have all the cards listed in “Step 152l-53” been replaced with new or original cards? Call for support. Go to “Step 152l-53”. Eserver pSeries 690 Service Guide...

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

    MAP 152m: Cable Problem in Power Subsystem Step 152m-1 Record the error code and location code(s) that sent you to this MAP. You should be supplied with one or two pairs of location codes from the action for the error code in the service guide. These location codes are the ends of the cable or cables in question.
  • Page 312 Does the error code recorded in “Step 152m-1” on page 291 reappear? Go to “Step 152m-2” on page 291. 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 313 Step 152m-18 Note: The following steps will require the system power to be removed. The operating system must be shut down in all partitions before turning off the power. Turn off the power. Turn off the UEPO switch. Examine the amber logic-power LEDs of all installed processor subsystem DCAs.
  • Page 314 Call for support. All system partitions must be shut down and the system must be powered off to correct the power cabling. Schedule nonconcurrent service with the customer to correct the power cabling. This ends this procedure. Eserver pSeries 690 Service Guide...

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

    MAP 152n: DASD Subsystem Power Problem Step 152n-1 Record the error code and location code(s) that sent you to this MAP. Step 152n-2 Press the green start service button on the panel with the UEPO switch. 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 316 The problem has changed. This ends the procedure. Go to “Step 152n-9” to reinstall the next DASD. Step 152n-14 Turn off the power. Make sure all green ″power good out″ LEDs of all installed I/O subsystem DCAs are off. Eserver pSeries 690 Service Guide...
  • Page 317 Step 152n-15 Replace the books in the following list, one at a time and in the listed order: v DCA 1 at V1 v DCA 2 at V2 Step 152n-16 Turn on the power. Step 152n-17 Did the system stop with the same error code as recorded in “Step 152n-1” on page 295? Go to “Step 152n-18”.

  • Page 318: 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 845 and “L3 Cache Modules” on page 865. Eserver pSeries 690 Service Guide...

  • Page 319: Map 1541: Jtag Problem Isolation

    Problem Isolation Procedures Symptom/Reference Code/Checkpoint Action 406x 0C09 Go to “MAP 1546: Memory Book Problem Isolation” on page 331. 406x 0C0A Go to “MAP 1547: I/O Book Problem Isolation” on page 333. 406x 0001, 406x 0002, 406x 000A, 406x 000B, Go to “MAP 154A: I2C Bus Problem Isolation”...
  • Page 320 Memory Book 5 at U1.18-P1-M8 Step 1541-7 Is (are) the location code(s) recorded in “Step 1541-1” on page 299 listed in “Step 1541-6”? Go to “Step 1541-31” on page 304. Go to “Step 1541-8” on page 301. Eserver pSeries 690 Service Guide...
  • Page 321 Step 1541-8 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1541-9 Are all the amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1541-10”. Call for support. Step 1541-10 Replace the item recorded in “Step 1541-1”...
  • Page 322 MCM module 3 at U1.18-P1-C2 if not recorded in “Step 1541-1” on page 299. v MCM module 1 at U1.18-P1-C3 if not recorded in “Step 1541-1” on page 299. v MCM module 2 at U1.18-P1-C4 if not recorded in “Step 1541-1” on page 299. Eserver pSeries 690 Service Guide...
  • Page 323 Step 1541-22 Turn on the power. Step 1541-23 Did the system stop with the same error code as recorded in “Step 1541-1” on page 299? Go to “Step 1541-24”. The part just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...
  • Page 324 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 325 Step 1541-36 Have all the books listed in “Step 1541-33” on page 304 been replaced? Go to “Step 1541-37”. Go to “Step 1541-31” on page 304. Step 1541-37 Turn off the power. Step 1541-38 Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1541-39 Are all the amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1541-40”.

  • Page 326: 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 745. Eserver pSeries 690 Service Guide...
  • Page 327 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 328 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 309. Eserver pSeries 690 Service Guide...
  • Page 329 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 330 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 331 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 332 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 314. Eserver pSeries 690 Service Guide...
  • Page 333 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 334 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 335 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 336 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 317. Eserver pSeries 690 Service Guide...
  • Page 337 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 338 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 339 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 340 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 341 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 342 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 343 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 344 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 345: 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 346 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. Step 1543-15 Call for support. This ends the procedure. Eserver pSeries 690 Service Guide...

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

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

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

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

  • Page 351: 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 352 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. Step 1546-15 Call for support. This ends the procedure. Eserver pSeries 690 Service Guide...

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

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

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

    MAP 1548: Memory and Processor Problem Isolation Step 1548-1 Record the error code and the location code(s) that sent you to this MAP. Step 1548-2 Turn off the power. Examine the amber logic-power LEDs of all installed processor subsystem DCAs. Step 1548-3 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1548-4”.
  • Page 356 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Go to “Step 1548-11”. Call for support. Step 1548-11 Attention: Before replacing the system backplane, call for support. Replace the system backplane at U1.18-P1. Eserver pSeries 690 Service Guide...
  • Page 357 Step 1548-12 Turn on the power. Step 1548-13 Did the system stop with the same error code as recorded in “Step 1548-1” on page 335? Go to “Step 1548-14”. The part just replaced was defective. This ends the procedure. Return the system to its original configuration. Go to ″MAP 0410: Repair Checkout″...

  • Page 358: Map 1549: Attention Problem Isolation

    406x 0EB9 Go to “Step 1549-33” on page 344. 406x 0EBA Go to “Step 1549-17” on page 341. 406x 0EBB Go to “Step 1549-21” on page 342. 406x 0EBC Go to “Step 1549-25” on page 343. Eserver pSeries 690 Service Guide...
  • Page 359 Step 1549-5 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 360 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 1549-12”. Step 1549-12 Have all the books listed in “Step 1549-9” been replaced? Go to “Step 1549-2” on page 338. Go to “Step 1549-13” on page 341. Eserver pSeries 690 Service Guide...
  • Page 361 Step 1549-13 Replace the following books and modules, if present, one at a time: v First location code item recorded, if any, in “Step 1549-1” on page 338. v Second location code item recorded, if any, in “Step 1549-1” on page 338. v Third location code item recorded, if any, in “Step 1549-1”...
  • Page 362 Multiple Bus Systems. Go to “Step 1549-24”. Step 1549-24 Have all the books or modules listed in “Step 1549-21” been replaced? Go to “Step 1549-2” on page 338. Go to “Step 1549-37” on page 344. Eserver pSeries 690 Service Guide...
  • Page 363 Step 1549-25 Replace the following books and modules, if present, one at a time: v First location code item recorded, if any, in “Step 1549-1” on page 338. v Second location code item recorded, if any, in “Step 1549-1” on page 338. v Third location code item recorded, if any, in “Step 1549-1”...
  • Page 364 Are all amber logic-power LEDs of all installed processor subsystem DCAs off? Call for support. Go to “Step 1549-40”. Step 1549-40 Attention: Before replacing the system backplane, call for support. Replace the system backplane at U1.18-P1. Step 1549-41 Turn on the power. Eserver pSeries 690 Service Guide...
  • Page 365 Step 1549-42 Did the system stop with the same error code as recorded in “Step 1549-1” on page 338? The part 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 366: Map 154A: I2C Bus Problem Isolation

    Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 154A-8”. Step 154A-8 Have all the books listed in “Step 154A-5” been replaced? Go to “Step 154A-2”. Go to “Step 154A-14” on page 347. Eserver pSeries 690 Service Guide...
  • Page 367 Step 154A-9 Is the value recorded in “Step 154A-1” on page 346 for word 16 of this error code equal to 00000008 or 00000009? Go to “Step 154A-5” on page 346. Go to “Step 154A-10”. Step 154A-10 Replace the following books and modules, if present, one at a time: v First location code item recorded, if any, in “Step 154A-1”...
  • Page 368 Go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Go to “Step 154A-26”. Step 154A-26 Have all the cards or modules listed in “Step 154A-23” been replaced? Go to “Step 154A-2” on page 346. Eserver pSeries 690 Service Guide...
  • Page 369 Go to “Step 154A-14” on page 347. Chapter 3. Maintenance Analysis Procedures...

  • Page 370: 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 371 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 350? 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 372 Eserver pSeries 690 Service Guide...

  • Page 373: 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 374 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 375 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 376: Service Processor Checkpoints

    Primary service processor thread waiting See note 1 on page 361. for response 9020 Service processor state set to pre-standby See note 1 on page 361. 9021 Service processor state set to standby See note 1 on page 361. Eserver pSeries 690 Service Guide...
  • Page 377 Checkpoint Description Action/ Possible Failing FRU 9022 Service processor state set to IPL See note 1 on page 361. 9023 Service processor state set to runtime See note 1 on page 361. 9024 Service processor state set to terminate See note 1 on page 361. 9025 Service processor state set to DPO See note 1 on page 361.
  • Page 378 See note 1 on page 361. from service processor 9200 Scan interface BATs See note 1 on page 361. 9300 Logic BIST See note 1 on page 361. 9301 Scanned ABIST See note 1 on page 361. Eserver pSeries 690 Service Guide...
  • Page 379 Checkpoint Description Action/ Possible Failing FRU 9302 Dedicated ABIST See note 1 on page 361. 9303 Dedicated ABIST array fuse repair See note 1 on page 361. calculation 9380 Built-in-self-test (BIST) See note 2 on page 361. 9400 Service processor is requesting system See note 1 on page 361.
  • Page 380 See note 1 on page 361. A80D Reserved; not used See note 1 on page 361. A80E Reserved; not used See note 1 on page 361. A80F Service processor dump done See note 1 on page 361. Eserver pSeries 690 Service Guide...
  • Page 381 Checkpoint Description Action/ Possible Failing FRU A810-A8FF Scan log dump in progress Informational message. (See “Scan Log Dump Policy” on page 764.) 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 382 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 383: 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 356. If you have a checkpoint with no location code associated with it, see “Determining Location Code”...
  • Page 384 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 385 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 386 Procedures” on page 298. E1AF System booted to utilities menu via NVRAM Go to “MAP 1540: Problem Isolation settings Procedures” on page 298. E1B1 Create serial node Go to “MAP 1540: Problem Isolation Procedures” on page 298. Eserver pSeries 690 Service Guide...
  • Page 387 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 388 E1F4 End self-test sequence on boot devices; Go to “MAP 1542: I/O Problem Isolation” on begin SMS. page 306. E1F5 Build boot device list Go to “MAP 1542: I/O Problem Isolation” on page 306. Eserver pSeries 690 Service Guide...
  • Page 389 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 306. E1F7 No boot image located Go to “Boot Problems” on page 388. E1F8 Partition (system firmware) is waiting for a Open a virtual terminal for the partition on virtual terminal to be opened on HMC.
  • Page 390 2. Go to “MAP 1542: I/O Problem Isolation” on page 306. E50A Check for missing I/O interface chips 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 306. Eserver pSeries 690 Service Guide...
  • Page 391 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E50B Save I/O hub information 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 306. E50C Copy all of the memory ranges 1.
  • Page 392 I./O book that the RIO cables in step 1 are attached to. 4. 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 393 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 394 3. Replace the I/O book that the failing I/O subsystem is attached to, U1.18-P1-Hx. 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 306. Eserver pSeries 690 Service Guide...
  • Page 395 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E535 Valid node ID detected at other end of the 1. Replace the I/O cable specified by the I/O cable location code. 2. Replace the I/O book that the failing I/O subsystem is attached to, U1.18-P1-Hx.
  • Page 396 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. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 690 Service Guide...
  • Page 397 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E54A Configure the I/O drawer Check the RIO cable specified by the 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 398 I/O cable in step 1 is attached E565 Set up I/O interface chip registers 1. Replace the I/O cable specified by the location code. 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 690 Service Guide...
  • Page 399 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E566 Enable device arbitration on the I/O 1. Replace the I/O cable specified by the interface chip location code. 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached E567 Set up I/O interface chip registers 1.
  • Page 400 I/O cable in step 1 is attached E583 Running BIST on the current EADS 1. Replace the I/O cable specified by the location code. 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached Eserver pSeries 690 Service Guide...
  • Page 401 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E584 Checking function of current EADS 1. Replace the I/O cable specified by the location code. 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached E585 Valid function of current EADS detected 1.
  • Page 402 2. Replace the I/O subsystem backplane that the I/O cable in step 1 is attached E595 Detected valid adapter in slot 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 306. Eserver pSeries 690 Service Guide...
  • Page 403 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E596 Read the EADS revision ID and class code 1. Replace the RIO cable specified by the location code. 2. Replace the I/O subsystem planar to which the RIO cable in Step 1 is attached.
  • Page 404 2. Call for support. E705 Create clock card VPD. 1. Check for system firmware updates. 2. Call for support. E706 Create RIO extender card VPD. 1. Check for system firmware updates. 2. Call for support. Eserver pSeries 690 Service Guide...
  • Page 405 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E707 Create system VPD. 1. Check for system firmware updates. 2. Call for support. E708 Create RIO to PCI adapter VPD. Go to “MAP 1542: I/O Problem Isolation” on page 306.
  • Page 406 1. Check for system firmware updates. 2. Call service support. E871 Initializing RTAS/EEH handling interface 1. Check for system firmware updates. 2. Go to “MAP 1542: I/O Problem Isolation” on page 306. 3. Call service support. Eserver pSeries 690 Service Guide...
  • Page 407 Table 2. Firmware Checkpoints (continued) Checkpoint Description Action/ Possible Failing FRU E872 Initializing RTAS/error inject interface 1. Check for system firmware updates. 2. Call service support. E873 Initializing RTAS/error handling interface 1. Check for system firmware updates. 2. Call service support. E880 Initializing RTAS/debug interface 1.

  • Page 408: Boot Problems

    1) Remove all removable media from devices in the boot list from which you do not want to boot. 2) If attempting to boot from a network, go to step 3 on page 389. If attempting to boot from a disk drive or CD-ROM, go to step 4 on page 389. Eserver pSeries 690 Service Guide...
  • Page 409 b. If the intended boot device is not correctly listed in the boot sequence, add it to the boot sequence using the SMS menus. If the device can be added to the boot sequence, reboot the partition. If the intended boot device cannot be added to the boot list, ask the customer or system administrator to verify that the device you are trying to boot from is assigned to the correct partition.
  • Page 410 Check the network settings and flag settings, as detailed in “Running Standalone Diagnostics from a Network Installation Management (NIM) Server” on page 752. c. Follow the procedure outlined in step 3 on page 389. 5. Go to “MAP 1542: I/O Problem Isolation” on page 306. Eserver pSeries 690 Service Guide...

  • Page 411: 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 412: Confirming Initial Error Code

    Return to the step in the “Checkpoints and Error Codes Index” on page 394 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 413: 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 414: Checkpoints And Error Codes Index

    Go to “SPCN Error Codes” on page 398 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 459, and follow the instructions in the firmware error code table. Eserver pSeries 690 Service Guide...
  • Page 415 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 416 Go to “Firmware Checkpoints” on page 363 for more information on these checkpoints. Mxxx xxxx Problem Determination-Generated Error Codes Go to “Problem Determination-Generated Error Codes” on page 741, and follow the instructions in the error code table. Eserver pSeries 690 Service Guide...

  • Page 417: 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 306 unless you were already directed to any MAP 154x by the error code.

  • Page 418: 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 419 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 420 See note on page 487. 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 487. 2. Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 690 Service Guide...
  • Page 421 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 487. 2. Primary I/O book Location: U1.18-P1-H2 1011 8425 No MCM 1 VPD card or MCM 1.
  • Page 422 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 423 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 8800 BPC A cable missing 1. BPC A cable to primary I/O book Location: U1.18-P1-H2/Q8# 2.
  • Page 424 1014 B844 Overcurrent or overvoltage problem with 12.0V Go to “MAP 1520: Power” on page 190. in first I/O subsystem 1014 B854 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 190. in first I/O subsystem Eserver pSeries 690 Service Guide...
  • Page 425 Error Code Description Action/ Possible Failing FRU 1014 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 426 1. DCA-1 primary rack. Location: U1.5-V2 2. Fan 1 Location: U1.5-F2 1015 1C06 Loss of airflow in second I/O subsystem, Go to “MAP 1527: An Airflow Loss Has Been location: U1.5 Detected” on page 206. Eserver pSeries 690 Service Guide...
  • Page 427 Error Code Description Action/ Possible Failing FRU 1015 6014 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 190. second I/O subsystem 1015 6024 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power” on page 190. second I/O subsystem 1015 6034 Overcurrent or overvoltage problem with 2.5V in Go to “MAP 1520: Power”...
  • Page 428 FRU indicated with this error code, if any, should be replaced. 1015 xx11 Second I/O subsystem in primary rack, DCA-1 U1.5-V1 1015 xx13 Seeprom fault on DCA-1 in second I/O U1.5-V1 subsystem in primary rack Eserver pSeries 690 Service Guide...
  • Page 429 Error Code Description Action/ Possible Failing FRU 1015 xx15 Second I/O subsystem in primary rack, DCA-1, Go to “MAP 1520: Power” on page 190 with cable fault these pairs of location codes: 1. U1.5-V1/Q1 and U1.35-P2-X3/Q3 2. U1.5-V1/Q2 and U1.35-P1-X3/Q3 1015 xx17 Problem with fan 1 and fan 3 in second I/O 1.
  • Page 430 2. Fans 1 and 3 Location: U1.1-F1 and U1.1-F3 1016 7127 Problem with fan 2 and fan 4 in third I/O 1. DCA-2 subsystem in primary rack Location: U1.1-V2 2. Fans 2 and 4 Location: U1.1-F2 and U1.1-F4 Eserver pSeries 690 Service Guide...
  • Page 431 Error Code Description Action/ Possible Failing FRU 1016 B014 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 190. third I/O subsystem 1016 B024 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power” on page 190. third I/O subsystem 1016 B034 Overcurrent or overvoltage problem with 2.5V in Go to “MAP 1520: Power”...
  • Page 432 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 U1.1-P3 subsystem in primary rack Eserver pSeries 690 Service Guide...
  • Page 433 Error Code Description Action/ Possible Failing FRU 1016 xx61 Third I/O subsystem in primary rack, DASD U1.1-P4 backplane 2 fault 1016 xx63 Seeprom fault on DASD backplane 2 in third I/O U1.1-P4 subsystem in primary rack 1016 xx71 Third I/O subsystem in primary rack, DASD U1.1-P5 backplane 3 fault 1016 xx73 Seeprom fault on DASD backplane 3 in third I/O...
  • Page 434 Go to “MAP 1520: Power” on page 190. subsystem in an I/O drawer. 1017 CDB6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 190. subsystem in an I/O drawer. Eserver pSeries 690 Service Guide...
  • Page 435 Error Code Description Action/ Possible Failing FRU 1017 CDC6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 190. subsystem in an I/O drawer. 1017 F4x6 Hardware configuration does not support Call Service Support N-mode power.
  • Page 436 Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 198. 101A 0866 BPR 2A communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 198. Eserver pSeries 690 Service Guide...
  • Page 437 Error Code Description Action/ Possible Failing FRU 101A 0876 BPR 3A communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 198. 101A 0D06 350 volt bulk failure, BPA-A Go to “MAP 1525: There Is a 350 Volt Bulk Failure”...
  • Page 438 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. Call service support. 101A DC56 Informational message about the IBF. Informational message. Eserver pSeries 690 Service Guide...
  • Page 439 Error Code Description Action/ Possible Failing FRU 101A DC66 Informational message about the IBF. Informational message. 101A DC76 Informational message about the IBF. Informational message. 101A DD16 External UPS: bypass ended (informational Informational message. If a problem is message) suspected: 1.
  • Page 440 Go to “MAP 1520: Power” on page 190 with these location codes: U1.35-P1-X3/Q3# to U1.5-V1/Q2# 101A x335 Power cable fault Go to “MAP 1520: Power” on page 190 with these location codes: U1.35-P1-X2/Q3# to U2.5-V1/Q1# Eserver pSeries 690 Service Guide...
  • Page 441 Error Code Description Action/ Possible Failing FRU 101A x415 Power cable fault Go to “MAP 1520: Power” on page 190 with these location codes: U1.35-P1-X4/Q4# to U1.18-X4/Q1# 101A x425 Power cable fault Go to “MAP 1520: Power” on page 190 with these location codes: U1.35-P1-X3/Q4# to U1.5-V2/Q2# 101A x435 Power cable fault...
  • Page 442 101A xx22 BPC-A to BPD-1 communications fault 1. BPD-1 Location: U1.35-P1-X3 2. BPC-A Location: U1.35-P1-X4 3. BPE backplane A Location: U1.35-P1 101A xx23 Seeprom (VPD) fault on BPD-1A U1.35-P1-X3 101A xx31 BPA-A / BPD-2 U1.35-P1-X2 Eserver pSeries 690 Service Guide...
  • Page 443 Error Code Description Action/ Possible Failing FRU 101A xx32 BPC-A to BPD-2 communications fault 1. BPD-2 Location: U1.35-P1-X2 2. BPC-A Location: U1.35-P1-X4 3. BPE backplane A Location: U1.35-P1 101A xx33 Seeprom (VPD) fault on BPD-2A U1.35-P1-X2 101A xx41 BPA-A / BPD-3 U1.35-P1-X1 101A xx42 BPC-A to BPD-3 communications fault 1.
  • Page 444 Go to “MAP 1526: There Is An Integrated Battery Feature (IBF) Failure” on page 203. 101B 7BA6 IBF 3B failure Go to “MAP 1526: There Is An Integrated Battery Feature (IBF) Failure” on page 203. Eserver pSeries 690 Service Guide...
  • Page 445 Error Code Description Action/ Possible Failing FRU 101B CE16 BPC-BPC communication failure 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. 101B D216 BPA-BPA communication failure Go to “MAP 1520: Power”...
  • Page 446 101B FE16 UEPO switch on BPC B is in the bypass position Go to “MAP 1522: UEPO Switch On The BPC Is In The Bypass Position” on page 197. 101B FE56 BPR 1B communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 198. Eserver pSeries 690 Service Guide...
  • Page 447 Error Code Description Action/ Possible Failing FRU 101B FE66 BPR 2B communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault” on page 198. 101B FE76 BPR 3B communications fault Go to “MAP 1523: There Is a Bulk Power Regulator (BPR) Communications Fault”...
  • Page 448 Go to “MAP 1520: Power” on page 190 with these location codes: U1.35-P2-X2/Q7# to U2.13-V1/Q2# 101B x825 Power cable fault Go to “MAP 1520: Power” on page 190 with these location codes: U1.35-P2-X3/Q8# to U1.13-V2/Q1# Eserver pSeries 690 Service Guide...
  • Page 449 Error Code Description Action/ Possible Failing FRU 101B x835 Power cable fault If there is no DCA in U1.18-P1-V8, go to “MAP 1520: Power” on page 190 with these location codes: U1.35-P2-X3/Q8# to U1.13-V2/Q1# If there is a 6th DCA in U1.18-P1-V8, this error code will not be reported.
  • Page 450 101B xx83 Seeprom (VPD) fault on IBF-1B U1.13-P2-V3 101B xx91 BPA-B / IBF 2 U1.15-P2-V4 101B xx93 Seeprom (VPD) fault on IBF-2B U1.15-P2-V4 101B xxA1 BPA-B / IBF 3 U2.17-P2-V6 101B xxA3 Seeprom (VPD) fault on IBF-3B U2.17-P2-V6 Eserver pSeries 690 Service Guide...
  • Page 451 Error Code Description Action/ Possible Failing FRU 101B xxB1 BPA-B / EPO_SW 1. Replace the UEPO switch, Location: U1-V1 2. Check the cable from BPC-B to the UEPO switch, Location U1-V1/Q2# 101C 0FB6 MCM 0 running over temperature 1. Verify that the MCM at U1.18-P1-C1 is installed.
  • Page 452 2. Verify that the processor MCMs are seated properly. 3. Verify the processor VPD cards in the primary I/O book are of the proper number and are positioned and seated correctly. 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 453 Error Code Description Action/ Possible Failing FRU 101C 7EB6 MCM 0 running over temperature 1. Verify that the MCM at U1.18-P1-C1 is installed. 2. Verify that there are no airflow problems with the MCM at U1.18-P1-C1 or its heatsink. 3. Verify that the MCM at U1.18-P1-C1 is installed correctly onto the processor backplane.
  • Page 454 2. Verify that there are no airflow problems with the MCM at U1.18-P1-C3 or its heatsink. 3. Verify that the MCM at U1.18-P1-C3 is installed correctly onto the processor backplane. 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 455 Error Code Description Action/ Possible Failing FRU 101C E1D6 MCM 2 running over temperature 1. Verify that the MCM at U1.18-P1-C4 is installed. 2. Verify that there are no airflow problems with the MCM at U1.18-P1-C4 or its heatsink. 3. Verify that the MCM at U1.18-P1-C4 is installed correctly onto the processor backplane.
  • Page 456 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 457 Error Code Description Action/ Possible Failing FRU 101C F596 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 location: U1.18 that more precisely indicate where the failure is.
  • Page 458 1. U1.18-X3/Q1 and U1.35-P1-X4/Q3 2. U1.18-X3/Q2 and U1.35-P2-X4/Q3 101C xx97 Fan fault on processor subsystem fan 3 1. Fan 3 controller Location: U1.18-X3 2. Fan 3 Location: U1.18-F3 101C xxA1 Processor subsystem / MDA-4 U1.18-X4 Eserver pSeries 690 Service Guide...
  • Page 459 Error Code Description Action/ Possible Failing FRU 101C xxA3 Seeprom (VPD) fault on processor subsystem U1.18-X4 MDA-4 101C xxA5 Processor subsystem / MDA-4 cable fault Go to “MAP 1520: Power” on page 190 with these pairs of location codes: 1. U1.18-X4/Q1 and U1.35-P1-X4/Q4 2.
  • Page 460 Go to “MAP 1520: Power” on page 190. subsystem in an I/O drawer. 1021 CDB6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 190. subsystem in an I/O drawer. Eserver pSeries 690 Service Guide...
  • Page 461 Error Code Description Action/ Possible Failing FRU 1021 CDC6 A power short has been detected in the DASD Go to “MAP 1520: Power” on page 190. subsystem in an I/O drawer. 1021 F4x6 Hardware configuration does not support Call Service Support N-mode power.
  • Page 462 I/O subsystem in second rack (I/O subsystem 6) 1022 6054 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 190. in second I/O subsystem in second rack (I/O subsystem 6) Eserver pSeries 690 Service Guide...
  • Page 463 Error Code Description Action/ Possible Failing FRU 1022 6814 Overcurrent or overvoltage problem with 3.3V in Go to “MAP 1520: Power” on page 190. second I/O subsystem in second rack (I/O subsystem 6) 1022 6824 Overcurrent or overvoltage problem with 5.0V in Go to “MAP 1520: Power”...
  • Page 464 1022 xx11 Second I/O subsystem in second rack (I/O U2.5-V1 subsystem 6), DCA-1 1022 xx13 Seeprom fault on DCA-1 in second I/O U2.5-V1 subsystem in second rack (I/O subsystem 6) Eserver pSeries 690 Service Guide...
  • Page 465 Error Code Description Action/ Possible Failing FRU 1022 xx15 Second I/O subsystem in second rack (I/O Go to “MAP 1520: Power” on page 190 with subsystem 6), DCA-1, cable fault these pairs of location codes: 1. U2.5-V1/Q1 and U1.35-P2-X2/Q3 2. U2.5-V1/Q2 and U1.35-P1-X2/Q3 1022 xx17 Problem with fan 1 and fan 3 in second I/O 1.
  • Page 466 I/O subsystem (with IBF, moves to second rack) 1023 6854 Overcurrent or overvoltage problem with -12.0V Go to “MAP 1520: Power” on page 190. in fourth I/O subsystem (with IBF, moves to second rack) Eserver pSeries 690 Service Guide...
  • Page 467 Error Code Description Action/ Possible Failing FRU 1023 7017 Problem with fan 3 in fourth I/O subsystem (with 1. DCA-1 IBF, moves to second rack) Location: U2.9-V1 2. Fan 3 Location: U2.9-F3 1023 7027 Problem with fan 4 in fourth I/O subsystem (with 1.
  • Page 468 2. U2.9-V1/Q2 and U1.35-P1-X2/Q5 1023 xx17 Problem with fan 1 and fan 3 in fourth I/O 1. DCA-1 subsystem (with IBF, moves to second rack) Location U2.9–V1 2. Fan 1, Location U2.9–F1 3. Fan 3, Location U2.9–F3 Eserver pSeries 690 Service Guide...
  • Page 469 Error Code Description Action/ Possible Failing FRU 1023 xx21 Fourth I/O subsystem moves to second rack U2.9-V2 (with IBF), DCA-2 1023 xx23 Seeprom fault on DCA-2 in fourth I/O subsystem U2.9-V2 (with IBF) in secondary rack 1023 xx25 Fourth I/O subsystem moves to second rack Go to “MAP 1520: Power”...
  • Page 470 (I/O subsystem 7) Location: U2.13-V1 2. Fan 3 Location: U2.13-F3 1024 7027 Problem with fan 4 in third I/O subsystem in 1. DCA-2 second rack (I/O subsystem 7) Location: U2.13-V2 2. Fan 4 Location: U2.13-F4 Eserver pSeries 690 Service Guide...
  • Page 471 Error Code Description Action/ Possible Failing FRU 1024 7117 Problem with fan 1 and fan 3 in third I/O 1. DCA-1 subsystem in second rack (I/O subsystem 7) Location: U2.13-V1 2. Fans 1 and 3 Location: U2.13-F1 and U2.13-F3 1024 7127 Problem with fan 2 and fan 4 in third I/O 1.
  • Page 472 1024 xx15 Third I/O subsystem in second rack (I/O Go to “MAP 1520: Power” on page 190 with subsystem 7), DCA-1, cable fault these pairs of location codes: 1. U2.13-V1/Q1 and U1.35-P2-X2/Q7 2. U2.13-V1/Q2 and U1.35-P1-X2/Q7 Eserver pSeries 690 Service Guide...
  • Page 473 Error Code Description Action/ Possible Failing FRU 1024 xx17 Problem with fan 1 and fan 3 in third I/O 1. DCA-1 subsystem in second rack (I/O subsystem 7) Location U2.13–V1 2. Fan 1, Location U2.13–F1 3. Fan 3, Location U2.13–F3 1024 xx21 Third I/O subsystem in second rack (I/O U2.13-V2 subsystem 7), DCA-2...
  • Page 474 I/O subsystem in second rack (I/O Location: U2.19-V1 subsystem 8) 2. Fan 3 Location: U2.19-F3 1025 7027 Problem with fan 4 in fourth I/O subsystem in 1. DCA-2 second rack (I/O subsystem 8) Location: U2.19-V2 2. Fan 4 Location: U2.19-F4 Eserver pSeries 690 Service Guide...
  • Page 475 Error Code Description Action/ Possible Failing FRU 1025 7117 Problem with fan 1 and fan 3 in fourth I/O 1. DCA-1 subsystem in second rack (I/O subsystem 8) Location: U2.19-V1 2. Fans 1 and 3 Location: U2.19-F1 and U2.19-F3 1025 7127 Problem with fan 2 and fan 4 in fourth I/O 1.
  • Page 476 3. Fan 3, Location U2.19–F3 1025 xx21 Fourth I/O subsystem in second rack (I/O U2.19-V2 subsystem 8), DCA-2 1025 xx23 Seeprom fault on DCA-2 in fourth I/O subsystem U2.19-V2 in second rack (I/O subsystem 8) Eserver pSeries 690 Service Guide...
  • Page 477 Error Code Description Action/ Possible Failing FRU 1025 xx25 Fourth I/O subsystem in second rack (I/O If there is no DCA in U1.18-P1-V8, second rack subsystem 8), DCA-2, cable fault (I/O go to “MAP 1520: Power” on page 190 subsystem 8), DCA-2, with these pairs of location codes: 1.
  • Page 478 Error Code Description Action/ Possible Failing FRU SPCNtoB Go to “MAP 1529: There Is A Bulk Power Assembly (BPA) Communication Failure” on page 208. Eserver pSeries 690 Service Guide...

  • Page 479: Firmware/Post Error Codes

    Firmware/POST 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 306 unless you were already directed to any MAP 154x by the error code.
  • Page 480 Refer to Table 2 on page 363 using code E175. 20A8 0005 File transmission (TFTP) failed. Check network connection, try again. 20A8 0006 Boot image too large Contact your next level of support for assistance. Eserver pSeries 690 Service Guide...
  • Page 481 Error Code Description Action/ Possible Failing FRU 20D0 0001 I/O subsystem has changed locations This is an informational message. The I/O subsystem at the location code associated with this messages was found at another location code during a prior boot of the system.
  • Page 482 2. Contact your next level of support for assistance. 20D0 0A0E Error initializing interface/timebase access 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 483 Error Code Description Action/ Possible Failing FRU 20D0 0A0F Error initializing interface/time-of-day access 1. Check for system firmware updates. Apply update if available. 2. Contact your next level of support for assistance. 20D0 0A10 Error initializing interface/cache access 1. Check for system firmware updates. Apply update if available.
  • Page 484 VPD module onto the new operator panel. Call service support for instructions on programming the VPD information into the new VPD module. 2. If the location code indicates an I/O subsystem, call service support. Eserver pSeries 690 Service Guide...
  • Page 485 Error Code Description Action/ Possible Failing FRU 20D0 9005 Subsystem serial number field is empty in 1. If the location code starts with U1.17 or U1.18, the problem is in the system VPD module on the media subsystem operator panel. Replace the operator panel; do not swap the old VPD module onto the new operator panel.
  • Page 486 2. Contact your next level of support for assistance. 20D1 000C Failed to send LMB-TABLE-INFO mailbox 1. Check for system firmware updates. Apply repair update if available. 2. Contact your next level of support for assistance. Eserver pSeries 690 Service Guide...
  • Page 487 Error Code Description Action/ Possible Failing FRU 20D1 000D Hypervisor function to get time-of-day failed 1. Check for system firmware updates. Apply update if available. 2. Contact your next level of support for assistance. 20D1 000F Hypervisor call to reset PHB or to check for 1.
  • Page 488 2. Call service support. 20EE 000B The system was not able to find an operating Go to “Boot Problems” on page 388. system on the devices in the boot list. Eserver pSeries 690 Service Guide...
  • Page 489 Error Code Description Action/ Possible Failing FRU 20EE 000C Pointer to the operating system found in Values normally found in non-volatile storage non-volatile storage. that point to the location of an operating system were not found. This can happen for two reasons: v Either your operating system doesn’t support storing the values...
  • Page 490 Installation Guide and Reference, order number SC23-4389, for more information. If this error occurs at any other time, complete the following steps: 1. Check for platform firmware updates. Apply if available. 2. Call service support. Eserver pSeries 690 Service Guide...
  • Page 491 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 492 20FF0090 Invalid VPD (empty VPD data from the Replace the part specified by the location service processor mailbox command) code. 2. If no location code is shown with the error code, call service support. Eserver pSeries 690 Service Guide...
  • Page 493 Error Code Description Action/ Possible Failing FRU 20FF00A0 Invalid VPD (getvpd mailbox command failed) 1. Replace the part specified by the location code. 2. If no location code is shown with the error code, call service support. 20FF00B0 Invalid VPD (the FG keyword is not found for 1.
  • Page 494 3. Replace the SCSI controller. 21ED 0002 SCSI changer: test unit ready failed; sense Before replacing any system components, data available refer to the Action under error code 21A0 0001. 1. Replace the SCSI device. 2. Replace the media. Eserver pSeries 690 Service Guide...
  • Page 495 Error Code Description Action/ Possible Failing FRU 21ED 0003 SCSI changer: send diagnostic failed; sense Before replacing any system components, data available refer to the Action under error code 21A0 0001. Replace the SCSI device. 21ED 0004 SCSI changer: send diagnostic failed - devofl Before replacing any system components, command refer to the Action under error code 21A0...
  • Page 496 20EE 0013 Unable to allocate memory for root-lpar-vpd 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 497 Error Code Description Action/ Possible Failing FRU 25A0 0001 L2 Cache controller failure Replace the MCM module specified by the location code. 25A1 0001 L2 Cache SRAM failure Replace the MCM module specified by the location code. 25A8 0xxx NVRAM problems Errors reported against NVRAM can be caused by low battery voltage and (more rarely) power outages that occur during...
  • Page 498 25Cy y001 Memory book is not supported Replace unsupported memory book(s) specified by the location code. 25Cy y002 Memory book failure Replace the memory book(s) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 499 Error Code Description Action/ Possible Failing FRU 2601 0000 Boot failed because the RIO cables, or the 1. Check both ends of the RIO cable power subsystem cables, are not routed specified in the location code that appears correctly to the I/O subsystems with this error code.
  • Page 500 Check for system firmware updates. Apply if available. 2. If the location code identifies an I/O planar: a. Check for system firmware updates. Apply if available. b. Replace the I/O planar. 3. Call service support. Eserver pSeries 690 Service Guide...
  • Page 501 Error Code Description Action/ Possible Failing FRU 2602 0010 PCI probe error, bridge in freeze state If the location code identifies a slot or PCI adapter: 1. Check for system firmware updates. Apply if update available. 2. Check the cabling to the adapter (in particular, the adapters that have serial ports). Serial ports may require null modems or special cabling configurations to avoid connecting driver outputs together.
  • Page 502 See “Determining Location Code” on page 393 for location code information related to this error. 2680 0Dxx Machine check occurred; unable to isolate to Go to “MAP 1542: I/O Problem Isolation” on a single device page 306. Eserver pSeries 690 Service Guide...
  • Page 503 Error Code Description Action/ Possible Failing FRU 27A0 0001 Error obtaining external RIO cable IDs 1. Check the SPCN and RIO cabling going to the I/O subsystem specified by the location code. 2. Check for system firmware updates. 3. Replace the I/O subsystem planar specified by the location code.
  • Page 504 AIX error log entry in which the description says I/O bus time out, access, or other error, or I/O bridge/device internal error. Replace the FRUs listed in this entry. 2B20 8888 Operating system termination request Informational message. received Eserver pSeries 690 Service Guide...
  • Page 505 Error Code Description Action/ Possible Failing FRU 2B2x 00EE An exception error has been reported on a The type of interrupt that caused the global processor exception is specified by the x as follows: Unknown interrupt System reset interrupt (SRI) Machine check interrupt (MCI) Data storage interrupt (DSI) Instruction storage interrupt (ISI)
  • Page 506 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 507: Service Processor Error Codes

    Service Processor Error Codes Attention: Follow the procedure defined in “Checkpoints and Error Codes Index” on page 394. 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 508 2. MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 4064 00B7 Processor subsystem tests detected Insufficient Go to “MAP 1540: Problem Isolation hardware resources to continue IPL after Procedures” on page 298. processor subsystem testing and initialization completed Eserver pSeries 690 Service Guide...
  • Page 509 Error Code Description Action/ Possible Failing FRU 4064 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 510 (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 511 Error Code Description Action/ Possible Failing FRU 4064 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 512 4064 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 513 Error Code Description Action/ Possible Failing FRU 4064 0B15 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-H1 4.
  • Page 514 4064 0B31 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 515 Error Code Description Action/ Possible Failing FRU 4064 0B32 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 516 Location: U1.18-P1-H4 4064 0BF7 Processor subsystem tests detected fault in I/O 1. Check the cabling on the following RIO hub chip 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 517 Error Code Description Action/ Possible Failing FRU 4064 0BF8 Processor subsystem tests detected fault in I/O 1. Check the cabling on the following RIO hub chip 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4064 0BF9 Processor subsystem tests detected fault in I/O 1.
  • Page 518 L3 cache module 14 and L3 VPD card cache module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4064 0D0F Processor subsystem tests detected fault in L3 L3 cache module 15 and L3 VPD card cache module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 519 Error Code Description Action/ Possible Failing FRU 4064 0EA0 Processor subsystem tests detected fault in 1. Access the service processor error log. Find MOPS service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 520 4065 0005 Display alter tests detected fault in MCM MCM module 1 and VPD card module 1 Location: U1.18-P1-C3 and U1.18-P1-H2.5 4065 0006 Display alter tests detected fault in MCM MCM module 3 and VPD card module 3 Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 521 Error Code Description Action/ Possible Failing FRU 4065 0007 Display alter tests detected fault in L3 VPD 1. L3 VPD card card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective.″)
  • Page 522 (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 523 Error Code Description Action/ Possible Failing FRU 4065 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 524 (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 525 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 526 4065 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 527 Error Code Description Action/ Possible Failing FRU 4065 0B15 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-H1 4.
  • Page 528 4065 0B31 Display alter 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 529 Error Code Description Action/ Possible Failing FRU 4065 0B32 Display alter 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 530 Location: U1.18-P1-H4 4065 0BF7 Display alter tests detected fault in I/O hub chip 1. Check the cabling on the following RIO 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 531 Error Code Description Action/ Possible Failing FRU 4065 0BF8 Display alter tests detected fault in I/O hub chip 1. Check the cabling on the following RIO 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4065 0BF9 Display alter tests detected fault in I/O hub chip 1.
  • Page 532 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4065 0D0F Display alter tests detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 533 Error Code Description Action/ Possible Failing FRU 4065 0EA0 Display alter tests detected fault in MOPS 1. Access the service processor error log. Find service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 534 MCM module 1 and VPD card fault in MCM module 1 Location: U1.18-P1-C3 and U1.18-P1-H2.5 4066 0006 Scan interface basic assurance tests detected MCM module 3 and VPD card fault in MCM module 3 Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 535 Error Code Description Action/ Possible Failing FRU 4066 0007 Scan interface basic assurance tests detected 1. L3 VPD card fault in L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
  • 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 4066 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 (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 539 Error Code Description Action/ Possible Failing FRU 4066 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 540 4066 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 541 Error Code Description Action/ Possible Failing FRU 4066 0B15 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-H1 4.
  • Page 542 4066 0B31 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 543 Error Code Description Action/ Possible Failing FRU 4066 0B32 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 544 4066 0BF7 Scan interface basic assurance tests detected 1. Check the cabling on the following RIO fault in I/O hub chip 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 545 Error Code Description Action/ Possible Failing FRU 4066 0BF8 Scan interface basic assurance tests detected 1. Check the cabling on the following RIO fault in I/O hub chip 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4066 0BF9 Scan interface basic assurance tests detected 1.
  • Page 546 L3 cache module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4066 0D0F Scan interface basic assurance tests detected L3 cache module 15 and L3 VPD card fault in L3 cache module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 547 Error Code Description Action/ Possible Failing FRU 4066 0EA0 Scan interface basic assurance tests detected 1. Access the service processor error log. Find fault in MOPS service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 548 4067 0004 Bus tests detected fault in MCM module 2 MCM module 2 and VPD card Location: U1.18-P1-C4 and U1.18-P1-H2.4 4067 0005 Bus tests detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 Eserver pSeries 690 Service Guide...
  • Page 549 Error Code Description Action/ Possible Failing FRU 4067 0006 Bus tests detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 4067 0007 Bus tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card.
  • 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 4067 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 (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 553 Error Code Description Action/ Possible Failing FRU 4067 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 554 4067 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 555 Error Code Description Action/ Possible Failing FRU 4067 0B15 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-H1 4.
  • Page 556 4067 0B31 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 557 Error Code Description Action/ Possible Failing FRU 4067 0B32 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 558 2. Replace the RIO book, Location: U1.18-P1-H4 4067 0BF7 Bus tests detected fault in I/O hub chip 7 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 559 Error Code Description Action/ Possible Failing FRU 4067 0BF8 Bus tests detected fault in I/O hub chip 8 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4067 0BF9 Bus tests detected fault in I/O hub chip 9 (port 1.
  • Page 560 L3 cache module 14 and L3 VPD card Location: U1.18-P1-C9 and U1.18-P1-H2.1 4067 0D0F Bus tests detected fault in L3 cache module 15 L3 cache module 15 and L3 VPD card Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 561 Error Code Description Action/ Possible Failing FRU 4067 0EA0 Bus tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 562 4068 0005 Other bus tests detected fault in MCM module MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 4068 0006 Other bus tests detected fault in MCM module MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 563 Error Code Description Action/ Possible Failing FRU 4068 0007 Other bus tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
  • Page 564 (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 565 Error Code Description Action/ Possible Failing FRU 4068 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 566 (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 567 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 568 4068 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 569 Error Code Description Action/ Possible Failing FRU 4068 0B15 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-H1 4.
  • Page 570 4068 0B31 Other 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 571 Error Code Description Action/ Possible Failing FRU 4068 0B32 Other 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 572 Location: U1.18-P1-H4 4068 0BF7 Other bus tests detected fault in I/O hub chip 7 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 573 Error Code Description Action/ Possible Failing FRU 4068 0BF8 Other bus tests detected fault in I/O hub chip 8 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4068 0BF9 Other bus tests detected fault in I/O hub chip 9 1.
  • Page 574 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4068 0D0F Other bus tests detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 575 Error Code Description Action/ Possible Failing FRU 4068 0EA0 Other bus tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 576 4069 0005 Memory tests detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 4069 0006 Memory tests detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 577 Error Code Description Action/ Possible Failing FRU 4069 0007 Memory tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
  • Page 578 (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 579 Error Code Description Action/ Possible Failing FRU 4069 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 580 (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 581 Error Code Description Action/ Possible Failing FRU 4069 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 582 4069 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 583 Error Code Description Action/ Possible Failing FRU 4069 0B15 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-H1 4.
  • Page 584 4069 0B31 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 585 Error Code Description Action/ Possible Failing FRU 4069 0B32 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 586 Location: U1.18-P1-H4 4069 0BF7 Memory tests detected fault in I/O hub chip 7 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 587 Error Code Description Action/ Possible Failing FRU 4069 0BF8 Memory tests detected fault in I/O hub chip 8 1. Check the cabling on the following RIO (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 4069 0BF9 Memory tests detected fault in I/O hub chip 9 1.
  • Page 588 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 4069 0D0F Memory tests detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 589 Error Code Description Action/ Possible Failing FRU 4069 0EA0 Memory tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 590 406A 0005 Self tests detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 406A 0006 Self tests detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 591 Error Code Description Action/ Possible Failing FRU 406A 0007 Self tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
  • Page 592 (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 593 Error Code Description Action/ Possible Failing FRU 406A 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 594 (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 595 Error Code Description Action/ Possible Failing FRU 406A 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 596 406A 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 597 Error Code Description Action/ Possible Failing FRU 406A 0B15 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-H1 4.
  • Page 598 406A 0B31 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 599 Error Code Description Action/ Possible Failing FRU 406A 0B32 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 600 2. Replace the RIO book, Location: U1.18-P1-H4 406A 0BF7 Self-tests detected fault in I/O hub chip 7 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 601 Error Code Description Action/ Possible Failing FRU 406A 0BF8 Self-tests detected fault in I/O hub chip 8 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406A 0BF9 Self-tests detected fault in I/O hub chip 9 (port 1.
  • Page 602 406A 0D0E Self-tests detected fault in L3 cache module 14 L3 cache module 14 and L3 VPD card Location: U1.18-P1-C9 and U1.18-P1-H2.1 406A 0D0F Self-tests detected fault in L3 cache module 15 L3 cache module 15 and L3 VPD card Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 603 Error Code Description Action/ Possible Failing FRU 406A 0EA0 Self-tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 604 406B 0005 Wire tests detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 406B 0006 Wire tests detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 605 Error Code Description Action/ Possible Failing FRU 406B 0007 Wire tests detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
  • Page 606 (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 607 Error Code Description Action/ Possible Failing FRU 406B 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 608 (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 609 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 610 406B 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 611 Error Code Description Action/ Possible Failing FRU 406B 0B15 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-H1 4.
  • Page 612 406B 0B31 Wire 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 613 Error Code Description Action/ Possible Failing FRU 406B 0B32 Wire 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 614 2. Replace the RIO book, Location: U1.18-P1-H4 406B 0BF7 Wire tests detected fault in I/O hub chip 7 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 615 Error Code Description Action/ Possible Failing FRU 406B 0BF8 Wire tests detected fault in I/O hub chip 8 (port 1. Check the cabling on the following RIO ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406B 0BF9 Wire tests detected fault in I/O hub chip 9 (port 1.
  • Page 616 406B 0D0E Wire tests detected fault in L3 cache module 14 L3 cache module 14 and L3 VPD card Location: U1.18-P1-C9 and U1.18-P1-H2.1 406B 0D0F Wire tests detected fault in L3 cache module 15 L3 cache module 15 and L3 VPD card Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 617 Error Code Description Action/ Possible Failing FRU 406B 0EA0 Wire tests detected fault in MOPS service 1. Access the service processor error log. Find processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 618 406C 0005 IPL detected fault in MCM module 1 MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 406C 0006 IPL detected fault in MCM module 3 MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 619 Error Code Description Action/ Possible Failing FRU 406C 0007 IPL detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.) 2.
  • Page 620 (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 621 Error Code Description Action/ Possible Failing FRU 406C 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 622 (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 623 Error Code Description Action/ Possible Failing FRU 406C 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 624 406C 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 625 Error Code Description Action/ Possible Failing FRU 406C 0B15 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-H1 4.
  • Page 626 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. Third I/O book Location: U1.18-P1-H4 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 627 Error Code Description Action/ Possible Failing FRU 406C 0B31 IPL 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 628 2. Replace the RIO book, Location: U1.18-P1-H3 406C 0BF6 IPL detected fault in I/O hub chip 6 (port x) 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q5 b. U1.18-P1-H4/Q6 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 629 Error Code Description Action/ Possible Failing FRU 406C 0BF7 IPL detected fault in I/O hub chip 7 (port x) 1. Check the cabling on the following RIO ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 406C 0BF8 IPL detected fault in I/O hub chip 8 (port x) 1.
  • Page 630 406C 0D0D IPL detected fault in L3 cache module 13 L3 cache module 13 and L3 VPD card Location: U1.18-P1-C5 and U1.18-P1-H2.1 406C 0D0E IPL detected fault in L3 cache module 14 L3 cache module 14 and L3 VPD card Location: U1.18-P1-C9 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 631 Error Code Description Action/ Possible Failing FRU 406C 0D0F IPL detected fault in L3 cache module 15 L3 cache module 15 and L3 VPD card Location: U1.18-P1-C13 and U1.18-P1-H2.1 406C 0EA0 IPL detected fault in MOPS service processor 1. Access the service processor error log. Find code the error log entry for the 406x 0EA0 error.
  • Page 632 406D 0005 Attention handler detected fault in MCM module MCM module 1 and VPD card Location: U1.18-P1-C3 and U1.18-P1-H2.5 406D 0006 Attention handler detected fault in MCM module MCM module 3 and VPD card Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 633 Error Code Description Action/ Possible Failing FRU 406D 0007 Attention handler detected fault in L3 VPD card 1. L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
  • Page 634 (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 635 Error Code Description Action/ Possible Failing FRU 406D 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 636 (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 637 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 638 406D 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 639 Error Code Description Action/ Possible Failing FRU 406D 0B15 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-H1 4.
  • Page 640 406D 0B31 Attention handler 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 641 Error Code Description Action/ Possible Failing FRU 406D 0B32 Attention handler 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 642 Location: U1.18-P1-H4 406D 0BF7 Attention handler detected fault in I/O hub chip 1. Check the cabling on the following RIO 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 643 Error Code Description Action/ Possible Failing FRU 406D 0BF8 Attention handler detected fault in I/O hub chip 1. Check the cabling on the following RIO 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406D 0BF9 Attention handler detected fault in I/O hub chip 1.
  • Page 644 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 406D 0D0F Attention handler detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 645 Error Code Description Action/ Possible Failing FRU 406D 0EA0 Attention handler detected fault in MOPS 1. Access the service processor error log. Find service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 646 406E 0005 Scan control routines detected fault in MCM MCM module 1 and VPD card module 1 Location: U1.18-P1-C3 and U1.18-P1-H2.5 406E 0006 Scan control routines detected fault in MCM MCM module 3 and VPD card module 3 Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 647 Error Code Description Action/ Possible Failing FRU 406E 0007 Scan control routines detected fault in L3 VPD 1. L3 VPD card card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
  • Page 648 (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 649 Error Code Description Action/ Possible Failing FRU 406E 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 650 (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 651 Error Code Description Action/ Possible Failing FRU 406E 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 652 406E 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 653 Error Code Description Action/ Possible Failing FRU 406E 0B15 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-H1 4.
  • Page 654 406E 0B31 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 655 Error Code Description Action/ Possible Failing FRU 406E 0B32 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 656 Location: U1.18-P1-H4 406E 0BF7 Scan control routines detected fault in I/O hub 1. Check the cabling on the following RIO chip 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 657 Error Code Description Action/ Possible Failing FRU 406E 0BF8 Scan control routines detected fault in I/O hub 1. Check the cabling on the following RIO chip 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406E 0BF9 Scan control routines detected fault in I/O hub 1.
  • Page 658 L3 cache module 14 and L3 VPD card module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 406E 0D0F Scan control routines detected fault in L3 cache L3 cache module 15 and L3 VPD card module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 659 Error Code Description Action/ Possible Failing FRU 406E 0EA0 Scan control routines detected fault in MOPS 1. Access the service processor error log. Find service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 660 406F 0005 Error code generation/logging detected fault in MCM module 1 and VPD card MCM module 1 Location: U1.18-P1-C3 and U1.18-P1-H2.5 406F 0006 Error code generation/logging detected fault in MCM module 3 and VPD card MCM module 3 Location: U1.18-P1-C2 and U1.18-P1-H2.6 Eserver pSeries 690 Service Guide...
  • Page 661 Error Code Description Action/ Possible Failing FRU 406F 0007 Error code generation/logging detected fault in 1. L3 VPD card L3 VPD card Location: U1.18-P1-H2.1 (Order the L3 cache module FRU to obtain a new L3 VPD card. Return the L3 cache module that was included in the FRU kit, and the failing L3 VPD card as ″new defective″.)
  • Page 662 (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 663 Error Code Description Action/ Possible Failing FRU 406F 0A04 Reboot message (run-time array gard failure) Reboot the system in slow mode. Run for processor 2 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 664 (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 665 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 666 406F 0B14 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-H1 4. Call service support. Eserver pSeries 690 Service Guide...
  • Page 667 Error Code Description Action/ Possible Failing FRU 406F 0B15 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-H1 4.
  • Page 668 406F 0B31 Error code generation/logging detected fault in 1. Check for system firmware updates. 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. Call service support. Eserver pSeries 690 Service Guide...
  • Page 669 Error Code Description Action/ Possible Failing FRU 406F 0B32 Error code generation/logging detected fault in 1. Check for system firmware updates. 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 670 Location: U1.18-P1-H4 406F 0BF7 Error code generation/logging detected fault in 1. Check the cabling on the following RIO I/O hub chip 7 (port x) ports: a. U1.18-P1-H4/Q7 b. U1.18-P1-H4/Q8 2. Replace the RIO book, Location: U1.18-P1-H4 Eserver pSeries 690 Service Guide...
  • Page 671 Error Code Description Action/ Possible Failing FRU 406F 0BF8 Error code generation/logging detected fault in 1. Check the cabling on the following RIO I/O hub chip 8 (port x) ports: a. U1.18-P1-H1/Q7 b. U1.18-P1-H1/Q8 2. Replace the RIO book, Location: U1.18-P1-H1 406F 0BF9 Error code generation/logging detected fault in 1.
  • Page 672 L3 cache module 14 and L3 VPD card L3 cache module 14 Location: U1.18-P1-C9 and U1.18-P1-H2.1 406F 0D0F Error code generation/logging detected fault in L3 cache module 15 and L3 VPD card L3 cache module 15 Location: U1.18-P1-C13 and U1.18-P1-H2.1 Eserver pSeries 690 Service Guide...
  • Page 673 Error Code Description Action/ Possible Failing FRU 406F 0EA0 Error code generation/logging detected fault in 1. Access the service processor error log. Find MOPS service processor code the error log entry for the 406x 0EA0 error. Look for a hardware error of the form 450x yyyy, 460x yyyy, or 4B2x yyyy with a timestamp within a few minutes of the 406x 0EA0 error.
  • Page 674 406F 25E6 SMA 4-port switch adapter fault Replace the I/O book (switch adapter) specified by the location code. 406F 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 675 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 676 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 677 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 678 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 679 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 680 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 681 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 682 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 683 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 684 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 685 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 686 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 687 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 688 Problem Isolation” on page 335. 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 335. Eserver pSeries 690 Service Guide...
  • Page 689 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 335. 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 690 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 691 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 335. 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 692 Problem Isolation” on page 335. 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 335. used with 1.3 GHz MCM Eserver pSeries 690 Service Guide...
  • Page 693 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 335. 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 694 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 695 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 298 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 696 Procedures” on page 298 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 298 to isolate the failing component. Eserver pSeries 690 Service Guide...
  • Page 697 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 327. (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 698 16 GB inner memory book Isolation” on page 327. 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 329. Eserver pSeries 690 Service Guide...
  • Page 699 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 327. 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 700 16 GB inner memory Isolation” on page 327. 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 327. book Eserver pSeries 690 Service Guide...
  • Page 701 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 329. 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 702 Isolation” on page 329. 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 327. inner memory book Eserver pSeries 690 Service Guide...
  • Page 703 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 327. 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 704 Go to “MAP 1545: Outer L3 Module Problem tests detected fault in 32 GB or 64 GB CUoD Isolation” on page 329. 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 705 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 706 1.7 GHz MCMs Problem Isolation” on page 335. 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 335. Eserver pSeries 690 Service Guide...
  • Page 707 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 335. 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 708 1.7 GHz MCMs Problem Isolation” on page 335. 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 335. Eserver pSeries 690 Service Guide...
  • Page 709 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 710 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 711 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 712 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 713 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 714 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 715 Error Code Description Action/ Possible Failing FRU 4607 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 716 2. Replace the CUoD capacity card, location: U1.18-P1-H2.2, then ask the customer to reenter the CUoD activation keys. 4609 248B I/O subsystem and memory tests detected fault Operator panel in operator panel Location: U1.17-L1 Eserver pSeries 690 Service Guide...
  • Page 717 Error Code Description Action/ Possible Failing FRU 4609 25C0 I/O subsystem and memory tests detected fault System backplane in system backplane Location: U1.18-P1 4609 25C1 I/O subsystem and memory tests detected fault Clock card in 1.0 GHz clock card Location: U1.18-P1-X5 4609 2738 I/O subsystem and memory tests detected fault 1.
  • Page 718 I/O subsystem PCI backplane at location I/O subsystem PCI backplane specified in error code 460A 28B1 I/O subsystem and self-tests detected fault in I/O subsystem DASD backplane at location I/O subsystem DASD backplane specified in error code Eserver pSeries 690 Service Guide...
  • Page 719 Error Code Description Action/ Possible Failing FRU 460A 525E 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 720 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 721 Error Code Description Action/ Possible Failing FRU 460C 273C I/O subsystem and IPL detected fault in primary Primary I/O book - Slot 0 I/O book - Slot 0 Location: U1.18-P1-H2 460C 273D I/O subsystem and processor subsystem tests Primary I/O book - Slot 0 detected fault in primary I/O book - Slot 0 Location: U1.18-P1-H2 460C 2776 I/O subsystem and processor subsystem tests...
  • Page 722 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 723 Error Code Description Action/ Possible Failing FRU 460D 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 724 I/O Location: U1.18-P1-H2 book - Slot 0 460F 273D I/O subsystem and processor subsystem tests Primary I/O book - Slot 0 detected fault in primary I/O book - Slot 0 Location: U1.18-P1-H2 Eserver pSeries 690 Service Guide...
  • Page 725 Error Code Description Action/ Possible Failing FRU 460F 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 726 ″deconfigured by the system,″ either before or after the boot to the SMS menus, go to step 2 on page 655. 2. Replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 727 Error Code Description Action/ Possible Failing FRU 4B23 25C8 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 728 ″deconfigured by the system,″ either before or after the boot to the SMS menus, go to step 2 on page 655. 2. Replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 729 Error Code Description Action/ Possible Failing FRU 4B23 25D7 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 730 ″deconfigured by the system,″ either before or after the boot to the SMS menus, go to step 2 on page 655. 2. Replace the processor MCM (on which the deconfigured processor resides) specified by the location code. Eserver pSeries 690 Service Guide...
  • Page 731 Error Code Description Action/ Possible Failing FRU 4B23 526B 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 732 Procedures” on page 298 to isolate the failing component. 4B24 25C0 Processor subsystem detected fault in system System backplane backplane Location: U1.18-P1 4B24 25C1 Processor subsystem detected fault in 1.0 GHz Clock card clock card Location: U1.18-P1-X5 Eserver pSeries 690 Service Guide...
  • Page 733 Error Code Description Action/ Possible Failing FRU 4B24 25C7 Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 298 to isolate the failing component. 4B24 25C8 Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures”...
  • Page 734 4B25 526D Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 298 to isolate the failing component. 4B26 248B Processor subsystem and scan interface basic Operator panel assurance tests detected fault in operator panel Location: U1.17-L1 Eserver pSeries 690 Service Guide...
  • Page 735 Error Code Description Action/ Possible Failing FRU 4B26 258A Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 298 to isolate the failing component. 4B26 25C0 Processor subsystem and scan interface basic System backplane assurance tests detected fault in system Location: U1.18-P1...
  • Page 736 I/O subsystem DASD backplane specified in error code 4B27 526B Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 298 to isolate the failing component. Eserver pSeries 690 Service Guide...
  • Page 737 Error Code Description Action/ Possible Failing FRU 4B27 526C Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures” on page 298 to isolate the failing component. 4B27 526D Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures”...
  • Page 738 MCM Procedures” on page 298 to isolate the failing component. 4B29 28B0 Processor subsystem and memory test I/O subsystem PCI backplane at location detected fault in I/O subsystem PCI backplane specified in error code Eserver pSeries 690 Service Guide...
  • Page 739 Error Code Description Action/ Possible Failing FRU 4B29 28B1 Processor subsystem and memory test I/O subsystem DASD backplane at location detected fault in I/O subsystem DASD specified in error code backplane 4B29 526B Fault detected in 4-way or 8-way CUoD MCM Go to “MAP 1540: Problem Isolation Procedures”...
  • Page 740 Go to “MAP 1540: Problem Isolation Procedures” on page 298 to isolate the failing component. 4B2B 25D8 Fault in 4-way processor MCM detected Go to “MAP 1540: Problem Isolation Procedures” on page 298 to isolate the failing component. Eserver pSeries 690 Service Guide...
  • Page 741 Error Code Description Action/ Possible Failing FRU 4B2B 25E5 Processor subsystem detected fault in 4-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 298 to isolate the failing component. 4B2B 25E9 Processor subsystem detected fault in 8-way Go to “MAP 1540: Problem Isolation processor MCM Procedures”...
  • Page 742 4B2D 25D5 Processor subsystem and attention handler Go to “MAP 1540: Problem Isolation detected fault in 8-way processor MCM with Procedures” on page 298 to isolate the failing VPD card (8-, 16-, or 24-way) component. Eserver pSeries 690 Service Guide...
  • Page 743 Error Code Description Action/ Possible Failing FRU 4B2D 25D7 Fault in 4-way processor MCM detected Go to “MAP 1540: Problem Isolation Procedures” on page 298 to isolate the failing component. 4B2D 25D8 Fault in 4-way processor MCM detected Go to “MAP 1540: Problem Isolation Procedures”...
  • Page 744 Procedures” on page 298 to isolate the failing processor MCM component. 4B2F 25C8 Processor subsystem and error code Go to “MAP 1540: Problem Isolation generation/logging detected fault in 4-way Procedures” on page 298 to isolate the failing processor MCM component. Eserver pSeries 690 Service Guide...
  • Page 745 Error Code Description Action/ Possible Failing FRU 4B2F 25CF Processor subsystem detected fault in 8-way Go to “MAP 1540: Problem Isolation processor MCM Procedures” on page 298 to isolate the failing component. 4B2F 25D3 Processor subsystem and error code Go to “MAP 1540: Problem Isolation generation/logging detected fault in 8-way Procedures”...

  • Page 746: System Firmware Update Messages

    A100 3000 Successful completion of scan dump Informational message; may or may not be seen during a scan log dump. A1FF 3000 Scan dump has been disabled Informational message; may or may not be seen during a scan log dump. Eserver pSeries 690 Service Guide...

  • Page 747: Common Firmware Error Codes

    Common Firmware Error Codes Attention: Follow the procedure defined in “Checkpoints and Error Codes Index” on page 394. 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 748 B1xx 4600 Service processor failure 1. Check for system firmware updates. 2. Primary I/O book Location: U1.18-P1-H2 B1xx 4601 System processor failure Reboot the system in slow mode to isolate the failure. Eserver pSeries 690 Service Guide...
  • Page 749 Error Code Description Action/ Possible Failing FRU B1xx 4602 Hardware failure 1. Was this error code logged shortly after the system crashed? Go to 3. Go to 2 2. Examine the service processor error log. Look for a 4xxx yyyy error that calls out FRU(s) in the CEC whose timestamp just precedes the B1xx 4602 error.
  • Page 750 2. Check for system firmware updates. 3. Modem and modem cable. 4. Primary I/O book Location: U1.18-P1-H2 B1xx 4622 Service processor failure 1. Operator panel Location: U1.17-L1 2. Check for system firmware updates. 3. Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 690 Service Guide...
  • Page 751 Error Code Description Action/ Possible Failing FRU B1xx 4633 System power control network (SPCN) failure This error code may be informational, or it may indicate a failure in the SPCN firmware update. 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 752 Procedures” on page 298. B1xx 4650 System processor failure (all processors reset). Reboot the system in slow mode to isolate the problem. B1xx 4651 CPU GARD VPD on MCM 0 U1.18-P1-C1 and U1.18-P1-H2.3 Eserver pSeries 690 Service Guide...
  • Page 753 Error Code Description Action/ Possible Failing FRU B1xx 4652 CPU GARD VPD on MCM 1 U1.18-P1-C3 and U1.18-P1-H2.5 B1xx 4653 CPU GARD VPD on MCM 2 U1.18-P1-C4 and U1.18-P1-H2.4 B1xx 4654 CPU GARD VPD on MCM 3 U1.18-P1-C2 and U1.18-P1-H2.6 B1xx 4660 Memory subsystem failure (cannot isolate) Reboot the system in slow mode to isolate the failure, then check the service processor error...
  • Page 754 B1xx 4692 Operator panel task interface failure 1. Check for system firmware updates. 2. Call service support B1xx 4693 Service processor firmware failure 1. Check for system firmware updates. 2. Call service support Eserver pSeries 690 Service Guide...
  • Page 755 Error Code Description Action/ Possible Failing FRU B1xx 4694 System processor firmware failure 1. Check for system firmware updates. 2. Primary I/O book Location: U1.18-P1-H2 B1xx 4695 System power control network (SPCN) to 1. Check for system firmware updates. service processor interface failure 2.
  • Page 756 1. Reset the system using the pin-hole reset button on the operator panel. Retry the operation that caused this error code. 2. Check for a later level of firmware than the one that you were trying to install. Apply if available. 3. Call service support. Eserver pSeries 690 Service Guide...
  • Page 757 Error Code Description Action/ Possible Failing FRU B1xx 4699 9903: State sequence error found after a firmware update LID was received during firmware (Cont.) update. Actions: 1. Reset the system using the pin-hole reset button on the operator panel. Retry the operation that caused this error code.
  • Page 758 B1xx 469C Firmware to I/O interface 1. Check for system firmware updates. 2. Primary I/O book Location: U1.18-P1-H2 B1xx 469D Service processor firmware 1. Check for system firmware updates. 2. Primary I/O book Location: U1.18-P1-H2 Eserver pSeries 690 Service Guide...

  • Page 759: Hmc Surveillance Error Codes

    Error Code Description Action/ Possible Failing FRU B1xx 469E Service processor firmware failure 1. Check for system firmware updates. 2. Reboot the system in slow mode to isolate a problem in the processor subsystem. 3. Primary I/O book Location: U1.18-P1-H2 B1xx 469F Service processor failure 1.
  • Page 760 HMC and partitions. 2. If short host names are not being used, or the previous step does not correct the problem, contact service support. Eserver pSeries 690 Service Guide...

  • Page 761: Problem Determination-Generated Error Codes

    Go to “MAP 1542: I/O Problem Isolation” on error code is generated by the customer page 306. 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 306.

  • Page 762: Hypervisor Dump Retrieval Procedure

    1 is necessary: devices.chrp_lpar.base.ras 5.X.X.X COMMITTED CHRP LPAR RAS Support If no output is returned, the devices.chrp_lpar.base LPP must be installed from the AIX installation media by the customer or system administrator. Eserver pSeries 690 Service Guide...
  • Page 763 After the fileset is installed, the dump file is ready to be retrieved. 2. Enter fetchdbg -k at the command prompt. This produces the following output: Retrieving Dump File ....Dump read successful This action results in a file being written into the /tmp directory named dumpMMDDYY where MM is the current month, DD is the current day, and YY is the current year.
  • Page 764 Eserver pSeries 690 Service Guide...

  • Page 765: 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 766: Identifying The Terminal Type To The Diagnostics

    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 767 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 768: 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 769: Maintenance 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 770: 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 771 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 772: Running Standalone Diagnostics From A Network Installation Management (Nim) Server

    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 773: 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 774: Booting Standalone Diagnostics From The Nim Server On A System With No Hmc Attached

    Booting Standalone Diagnostics from the NIM Server on a System with No HMC Attached Eserver pSeries 690 Service Guide...

  • Page 775: 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 776: 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 777: 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 778: Privileged User Menus

    (for example, your system administrator, network administrator, or service representative) to more quickly identify the location, configuration, and history of your server. Set the system name, from the main menu, using option 6. Eserver pSeries 690 Service Guide...
  • Page 779 Note: The information under the Service Processor Firmware heading in the following Main Menu illustration is example information only. Service Processor Firmware VERSION: RH011007 Copyright 2001 IBM Corporation SYSTEM NAME MAIN MENU 1. Service Processor Setup Menu 2. System Power Control Menu 3.

  • Page 780: Service Processor Setup Menu

    9. Scan Log Dump Policy: Currently Never 98. Return to Previous Menu 99. Exit from Menus 0> Note: Unless otherwise stated in menu responses, settings become effective when a menu is exited using option 98 or 99. Eserver pSeries 690 Service Guide...

  • Page 781: Passwords

    Passwords Passwords can be any combination of up to eight alphanumeric characters. You can enter longer passwords, but the entries are truncated to include only the first eight characters. The privileged-access password can be set from service processor menus or from System Management Services (SMS) utilities (see Chapter 8, “Using System Management Services”, on page 809).
  • Page 782 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. Alternating messages between users works best. Eserver pSeries 690 Service Guide...
  • Page 783 v OS Surveillance Setup Menu Note: This option is disabled in partitioned systems. This menu can be used to set up operating system (OS) surveillance. OS Surveillance Setup Menu 1. Surveillance: Currently Enabled 2. Surveillance Time Interval: 2 minutes 3. Surveillance Delay: 2 minutes 98.
  • Page 784 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 785 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 786: System Power Control Menu

    Services (SMS) menus. This option is intended to be used on servers that require automatic power-on after a power failure. For more information, see “System Power-On Methods” on page 788. v Ring Indicate Power-On Menu Eserver pSeries 690 Service Guide...
  • Page 787 RING INDICATE POWER-ON MENU 1. Ring indicate power-on : Currently Enabled 2. Number of rings: Currently 3 30. Refresh Modem Settings 98. Return to Previous 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.
  • Page 788 Enable/Disable Fast System Boot Allows the user to select the IPL type, mode, and speed of the system boot. Attention: Selecting the fast IPL results in several diagnostic tests being skipped and a shorter memory test being run. Eserver pSeries 690 Service Guide...
  • Page 789 v Boot Mode Menu Note: This option is disabled in partitioned systems. The Boot Mode Menu allows you to select a boot mode. Boot Mode Menu 1. Boot to SMS Menu: Currently Disabled 2. Service Mode Boot from Saved List: Currently Disabled 3.

  • Page 790: System Information Menu

    Read Service Processor Error Logs Displays error conditions detected by the service processor. Refer to “Service Processor Error Logs” on page 803 for an example of this error log. v Read System POST Errors Eserver pSeries 690 Service Guide...
  • Page 791 This option should only be used by service personnel to obtain additional debug information. v Read NVRAM Displays Non Volatile Random Access Memory (NVRAM) content. v Read Service Processor Configuration Displays current service processor configuration. v Processor Configuration/Deconfiguration Menu Enable/Disable CPU Repeat Gard: CPU repeat gard automatically deconfigures a CPU during a system boot if a processor has failed BIST (built-in self test), caused a machine check or check stop, or has reached a threshold of recoverable errors.
  • Page 792 Runtime Recoverable Error Repeat Gard is disabled by default. These configuration/deconfiguration menus allow the user to change the system memory configuration. If it is necessary to take one of the memory books partially or completely offline, this menu allows you Eserver pSeries 690 Service Guide...
  • Page 793 to deconfigure a book, and then reconfigure the book at a later time. This menu also allows you to see if the repeat gard function has partially or completely deconfigured a memory book. When this option is selected, a menu displays. The following is an example of this menu: MEMORY CONFIGURATION/DECONFIGURATION MENU 77.
  • Page 794 - For the I/O type, type 98. If either value is not valid, a failure message displays on the console. Press Enter to return to the Power Control Network Utilities Menu. – Collect & display SPCN trace data Eserver pSeries 690 Service Guide...
  • Page 795 This option is used by service personnel to dump the SPCN trace data from the processor subsystem (CEC drawer) to gather additional debug information. To dump the SPCN trace data for the processor subsystem (CEC drawer), enter 0 when prompted for the SPCN drawer number and enter d0 when prompted for the unit address, as shown in the example screen: Enter the SPCN drawer number:...
  • Page 796 The I/O drawer fault/identify LED is located on the front of each I/O subsystem. If option 1 is selected, a list of location codes of the I/O subsystems and the CEC drawer displays. The screen will be similar to the following: Eserver pSeries 690 Service Guide...
  • Page 797 1. U1.9-P1 2. U1.9-P2 3. U1.5-P1 4. U1.5-P2 5. U1.1-P1 6. U1.1-P2 7. U2.1-P1 8. U2.1-P2 9. U2.5-P1 10. U2.5-P2 Enter number corresponding to the location code, or press Return to continue, or ’x’ to return to the menu. 0>4 If one of the devices is selected using the index number, the present state of its LED will be displayed, and you are given the option to toggle it, as shown in the following screen.
  • Page 798 9. L3_7 U1.18-P1-C12 10. MCM_3 U1.18-P1-C2 11. MCM_2 U1.18-P1-C3 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 Eserver pSeries 690 Service Guide...
  • Page 799 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. When all of the new plug counts have been entered, select 50, Commit the values and write to the VPD.
  • Page 800 (after NVRAM is cleared), it will be set during the first boot and remain set during subsequent boots. The maximum RIO speed setting will remain uninitialized until set by the user. Eserver pSeries 690 Service Guide...

  • Page 801: Language Selection Menu

    The user can set the speed lower than or equal to the hardware capability, but not higher. If the hardware capability is 1000 Mbps, the user can set the link speed to 500 Mbps, and the RIO link will run at 500 Mbps. However, if the hardware capability is 500 Mbps and the user selects 1000 Mbps, the user’s selection will be ignored by the system.

  • Page 802: Call-In/Call-Out Setup Menu

    Customer Account Setup Menu, see “Customer Account Setup Menu” on page 788. v Call-Out Test tests the configuration after the modem is installed and configured correctly. Note: If the system is running in partition mode, the call-out option is disabled. Eserver pSeries 690 Service Guide...

  • Page 803: Modem Configuration Menu

    Modem Configuration Menu Note: This option applies only to a modem attached to serial port 1 (S1) or serial port 2 (S2) on the primary I/O book. The first two lines of the Modem Configuration Menu contain status of the current selections. Selections are made in the sections labeled Modem Ports and Modem Configuration File Name.

  • Page 804: Serial Port Selection Menu

    Call-in and ring indicate power-on cannot be enabled at the same time. If ring-indicate power-on is already enabled and you try to enable call-in, a message prompts you for confirmation. Refer to the message displayed on the screen. Eserver pSeries 690 Service Guide...

  • Page 805: Serial Port Speed Setup Menu

    Serial Port Speed Setup Menu This menu allows you to set serial port speed to enhance terminal performance or to accommodate modem capabilities. Serial Port Speed Setup Menu 1. Serial Port 1 Speed: Currently 9600 2. Serial Port 2 Speed: Currently 9600 98.
  • Page 806 Note: If the system is running in partition mode, call-out is disabled. However, if the system is booted in full system partition mode, at least one of the preceding three telephone numbers must be assigned in order for the call-out test to complete successfully. Eserver pSeries 690 Service Guide...

  • Page 807: Call-Out Policy Setup Menu

    v Customer Voice Telephone Number is the telephone number of a phone near the server or answered by someone responsible for the server. This is the telephone number left on the pager for callback. For test purposes, use a test number, which you can change later. v Customer System Telephone Number is the telephone number to which your server’s modem is connected.

  • Page 808: Customer Account Setup Menu

    The service processor can be enabled to recover from the loss of ac power (see Enable/Disable Unattended Power-On Mode in the SYSTEM POWER CONTROL MENU). When ac power is restored, the system returns to the power state at the time ac loss occurred. For example, if the system was Eserver pSeries 690 Service Guide...
  • Page 809 powered on when ac loss occurred, it reboots/restarts when power is restored. If the system was powered off when ac loss occurred, it remains off when power is restored. v Timed power-on - refer to the shutdown -t command on servers using AIX. Working in conjunction with AIX, the Service Processor in your server can operate a timer, much like the wake-up timer on your clock radio.

  • Page 810: Service Processor Reboot/Restart Recovery

    Enable supplemental restart policy - The default setting is yes. When set to yes on a full system partition, the service processor restarts the server when the operating system loses control and either: The Use OS-Defined restart policy is set to No. Eserver pSeries 690 Service Guide...

  • Page 811: System Firmware Updates

    The Use OS-Defined restart policy is set to Yes and the operating system has no automatic restart policy. If set to Yes on a partitioned system, the service processor restarts the system when the system loses control and it is detected by service processor surveillance. Refer to “Service Processor Reboot/Restart Recovery”...

  • Page 812: General Information On 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 813: 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 814: System Firmware Update In Aix Using A Locally Available Image

    It is strongly recommended that you create a set of firmware update diskettes from CORE as soon as possible after a system is installed. As noted below, the diskette images can be downloaded to any Eserver pSeries 690 Service Guide...

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

    personal computer or Eserver pSeries machine with access to CORE. This method is the only way to acquire a set of firmware update diskettes; they cannot be created by using the service processor menus or by using AIX. Retain and store the latest firmware diskettes each time the firmware gets updated in the event that the firmware gets damaged and must be reloaded.

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

    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 817: Recovery Mode

    Recovery Mode If the service processor detects that its programming has been damaged when it is powering on to standby mode, it will enter recovery mode. In recovery mode, it will ask for the firmware update diskettes by putting eight-digit codes on the operator panel. The eight-digit codes are as follows: Code Action...

  • Page 818: Configuring And Deconfiguring Processors Or Memory

    Note: Operating system surveillance is disabled on partitioned systems. System Firmware Surveillance System firmware surveillance is automatically enabled during system power-on. It cannot be disabled by the user, and the surveillance interval and surveillance delay cannot be changed by the user. Eserver pSeries 690 Service Guide...
  • Page 819 If the service processor detects no heartbeats during system IPL (for a set period of time), it cycles the system power to attempt a reboot. The maximum number of retries is set from the service processor menus. If the fail condition persists, the service processor leaves the machine powered on, logs an error, and displays menus to the user.

  • Page 820: 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 821: 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 822: 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 823: 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 824: Lcd Progress Indicator Log

    This action causes the system to shut down and the system power is turned off. To reset the service processor when the managed system is powered off, perform either of the following: Eserver pSeries 690 Service Guide...
  • Page 825 v If the service processor is responding to input from the HMC (or ASCII terminal), select Service Processor Setup Menu from the main menu, then select Reset Service Processor. This can only be done by a privileged user. v Put the UEPO switch in the off position, then back to the on position. Note: Do not use the pinhole reset switch to reset the service processor.

  • Page 826: 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 827: 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 828: Run-Time Phase

    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 829: 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 830: 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 831: 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 832: 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 833 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 834: 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 835: 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 836 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 837: 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 838 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 839: 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 840: 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 841: Chapter 9. Removal And Replacement Procedures

    Chapter 9. Removal and Replacement Procedures Introduction ........824 Handling Static-Sensitive Devices .
  • Page 842 Removal ....... . . 971 Eserver pSeries 690 Service Guide...
  • Page 843 Replacement....... . 972 I/O Subsystem I/O Backplane Assembly..... . . 973 Removal .

  • Page 844: Introduction

    If you need to lay the device down while it is out of the antistatic container, lay it on the antistatic container. Before picking it up again, touch the antistatic container and the metal frame of the system unit at the same time. v To prevent permanent damage, handle the devices carefully. Eserver pSeries 690 Service Guide...

  • Page 845: Powering Off And Powering On The System

    Powering Off and Powering On the System This section provides procedures for powering off and powering on the system. If you are instructed to remove the power from the system, the power cords must be disconnected from the power source. Powering Off the System With an HMC Attached and AIX Installed The HMC user interface provides a power-off function to turn off the power to the system.

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

    This indicates that power levels are satisfactory in the subsystems. Powering On the System Using the Service Processor The system can be powered on using the System Power Control menu, which is a Service Processor menu that is available to the privileged user. Eserver pSeries 690 Service Guide...

  • Page 847: Hot-Pluggable Frus

    Hot-Pluggable FRUs Notes: 1. The Linux operating system does not support some hot-pluggable procedures. 2. Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. A system with Linux installed on one or more partitions must be shutdown and powered off before replacing any PCI adapter or device assigned to a Linux partition.
  • Page 848 Optional media SCSI Yes (AIX only) Must be removed from the configuration and the partition devices must be booted afterwards to ensure correct operation. Might require additional consideration or preparation by the customer for replacement. Eserver pSeries 690 Service Guide...

  • Page 849: Power Subsystem

    Power Subsystem This section contains the removal and replacement procedures for the power subsystem. Notes: 1. All pluggable BPA FRUs are replaced concurrent with system operation when the removal and replacement instructions are followed. Exceptions to this occur when multiple failures exist in the BPA. 2.

  • Page 850: Bulk Power Controller (Bpc)

    5. Move the UEPO bypass switch to the NORMAL position. 6. Press the white Service Complete button on the UEPO switch to indicate completion of this procedure. The BPA automatically configures as it powers on. Eserver pSeries 690 Service Guide...

  • Page 851: Bulk Power Distributor (Bpd)

    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 852: Bulk Power Fan (Bpf)

    5. Plug the BPF cable to the BPC, ensuring that the plug location and the cable label agree. 6. Press the white Service Complete button on the UEPO switch to indicate completion of this procedure. Eserver pSeries 690 Service Guide...

  • Page 853: Bulk Power Enclosure (Bpe)

    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 854: Unit Emergency Power Off (Uepo) Card Assembly

    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 855: Integrated Battery Feature (Ibf)

    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 856 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 857: 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 858: I/O Books And I/O Blanks

    If the ″version mismatch″ error does not appear on the HMC, the firmware level of the new primary I/O book must still be determined. Note: You need a laptop computer (and cable part number 62H4857) capable of connecting to serial port 2 on the primary I/O book. Eserver pSeries 690 Service Guide...
  • Page 859 a. Open a virtual terminal window on the HMC. 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 (from the new I/O book) is displayed above the main menu, in the format RHyymmdd or vHyymmdd.
  • Page 860 2. If you are replacing a primary I/O book, make sure you set the system time and date through the date operating system command, and enter the I/O type as described in “Change I/O Type” on page 774. Eserver pSeries 690 Service Guide...

  • Page 861: Battery

    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 862 2. Reset the service processor settings. See “Saving and Restoring Service Processor Settings” on page 756 for information about restoring the service processor settings. 3. Ensure that the customer resets the service processor information such as the date, time, and passwords. Eserver pSeries 690 Service Guide...

  • Page 863: Processor Subsystem Dca (Distributed Converter Assembly) Books And Dca Blanks

    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 864: 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 826. Eserver pSeries 690 Service Guide...

  • Page 865: Mcm Module (Processor) And Pass Through Modules

    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 391. Handling Static-Sensitive Modules Attention: MCM and L3 modules are sensitive to static electricity discharge.
  • Page 866 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 867 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 868 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 869 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 870 (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 871 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 872 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 873 8. Use the torque wrench (supplied with the system tool kit, see “Tools” on page 1011 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 874 8. Exit the menu completely before powering on the system. Eserver pSeries 690 Service Guide...

  • Page 875: Methods For Testing Mcms And Pass Through Modules For A Short Circuit

    17. Turn on power as described in “Powering the System On” on page 826. Note: The 4-way processor MCM FRU can have odd-numbered processors or even-numbered processors. If you have just replaced a 4-way MCM module, notify the customer that they can determine their processor numbering by issuing the command lsdev -C on the partition that is using the new processors.

  • Page 876: Method 1. Testing Mcms And Pass Through Modules For A Short Circuit

    Connect Meter Meter "V" to Test Card "1.6V (Yellow Jack) Meter "COM" to Test Card "COMMON RET" (Black Jack) * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 883. Eserver pSeries 690 Service Guide...
  • Page 877 MCM Installation Shorts Test, Step 2: * See the Fail Criteria value in “Shorts Test Qualified Service Meters and Fail Criteria” on page 883. Chapter 9. Removal and Replacement Procedures...
  • Page 878 Update the history Log on SFP Fold the paper with the recorded data and place inside the plug tracking chart and then fold the chart * See “L3 Cache Modules” on page 865. Eserver pSeries 690 Service Guide...

  • Page 879: Method 2. Testing Mcms And Pass Through Modules For A Short Circuit

    Method 2. 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 a multimeter and capacitor book (part number 44P2471 or later) during MCM replacement.
  • Page 880 MCM Installation Shorts Test, Step 2: * See the Fail Criteria value in “Shorts Test Qualified Service Meters and Fail Criteria” on page 883. Eserver pSeries 690 Service Guide...
  • Page 881 MCM Installation Shorts Test, Step 3: * See “L3 Cache Modules” on page 865. Chapter 9. Removal and Replacement Procedures...

  • Page 882: Method 3. Testing Mcms And Pass Through Modules For A Short Circuit

    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 883 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 884 L3 modules before power the system on, perform “Method 3. Testing L3 Cache Modules for a Short Circuit” on page 881. 5. Install another MCM or pass through module and repeat step 4 until all required MCMs are installed. Eserver pSeries 690 Service Guide...

  • Page 885: L3 Cache Modules

    L3 Cache Modules Handling Static-Sensitive Modules Attention: MCM and L3 modules are sensitive to static electricity discharge. These devices are shipped in antistatic containers to prevent damage caused by electrostatic discharge. Take the following precautions: v Use an antistatic wrist strap while handling the device. v Do not remove the device from the antistatic container until you are ready to install the device in the system unit.
  • Page 886 10. Clean the LGA site using the brush supplied with the new module. Note: Before you remove the brush from its protective bag, loosen the bristles by pressing them on the ESD mat until they are 90 degrees from the handle. Eserver pSeries 690 Service Guide...
  • Page 887 Attention: Each time an L3 cache module is removed from the system backplane, the LGA site where the module connects must be cleaned. With the brush supplied with the replacement kit, use only downward strokes, starting in the upper left corner. Move left to right, top to bottom, using overlapping strokes as shown in the following illustration.
  • Page 888 5. If you are installing a new L3 cache module, replace the sleeves that you removed earlier with the new sleeves provided with the L3 cache module kit. If you are reseating an existing module, use a lint-free cloth to wipe any dust from the sleeves that you removed earlier. Eserver pSeries 690 Service Guide...
  • Page 889 6. Be sure to align the notches at the upper right corner of each spring plate as shown in the following illustration. Replace the spring plates that you removed earlier with the new spring plates provided with the L3 cache module kit. 1 Notch on upper right corner 2 5-mm set screw 3 Reinforced center...

  • Page 890: Methods For Testing L3 Cache Modules For A Short Circuit

    (or any capacitor books with the necessary LGA test support features), and the new LGA-ST. Refer to “Method 3. Testing L3 Cache Modules for a Short Circuit” on page 881. Eserver pSeries 690 Service Guide...

  • Page 891: Method 1. Testing L3 Cache Modules For A Short Circuit

    Method 1. 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 MCM/L3 module short-circuit test tool (part number 44P0209) and a multimeter during L3-cache module replacement.
  • Page 892 Reject the L3 cache module Are Shorts Visible? Are all The Memory Disengaged? Disengage One I/O Book Disengage A Memory Book Primary I/O Book First Memory are removed one at a time Secondary I/O Books second Eserver pSeries 690 Service Guide...
  • Page 893 L3 Cache Shorts Test, Step 3: * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 883. Chapter 9. Removal and Replacement Procedures...
  • Page 894 L3 Cache Shorts Test, Step 4: Eserver pSeries 690 Service Guide...
  • Page 895 L3 Cache Shorts Test, Step 5: Chapter 9. Removal and Replacement Procedures...

  • Page 896: Method 2. Testing L3 Cache Modules For A Short Circuit

    L3 Cache 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 883. Eserver pSeries 690 Service Guide...
  • Page 897 L3 Cache Shorts Test, Step 2: Chapter 9. Removal and Replacement Procedures...
  • Page 898 L3 Cache Shorts Test, Step 3: * See “Shorts Test Qualified Service Meters and Fail Criteria” on page 883. Eserver pSeries 690 Service Guide...
  • Page 899 L3 Cache Shorts Test, Step 4: Chapter 9. Removal and Replacement Procedures...
  • Page 900 L3 Cache Shorts Test, Step 5: Eserver pSeries 690 Service Guide...

  • Page 901: Method 3. Testing L3 Cache Modules For A Short Circuit

    Method 3. Testing L3 Cache 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 Test head 5 Toggle switch...
  • Page 902 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. 3. Install an L3 module. Eserver pSeries 690 Service Guide...

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

    4. Press the toggle switch on the LGA-ST forward to the MCM/L3 PWR/GND position. This action will test the L3 modules for power-to-ground shorts. Observe the lit LEDs on the LGA-ST and take the corresponding following actions: Green L3 LED is lit This is a pass state.
  • Page 904 83 (with CAT III front 400 Ohms +/-0.20 +0.50 panel marking) Fluke 83-3 400 Ohms +/-0.20 +0.50 Fluke 85 (with CAT III front 400 Ohms +/-0.20 +0.50 panel marking) Fluke 85-3 400 Ohms +/-0.20 +0.50 Eserver pSeries 690 Service Guide...

  • Page 905: Capacity Upgrade On Demand (Cuod) Vpd Module

    Manufacturer Model Range Accuracy @ 1.0 Fail Criteria ohms or less Fluke 87 (with CAT III front 400 Ohms +/-0.20 +0.50 panel marking) Fluke 87-3 200 Ohms +/-0.20 +0.50 Capacity Upgrade on Demand (CUoD) VPD Module Use the following instructions to replace the CUoD VPD module. This action should only be taken if the VPD module is listed as a failing FRU.
  • Page 906 If the number of processors match, reboot the system and return control of the system to the customer. v If the number of processors does not match, return to the Processor Order Information panel and verify the information with service support. Eserver pSeries 690 Service Guide...

  • Page 907: Vpd Card

    VPD Card Notes: 1. The MCM module and its associated VPD card are a single FRU and must be replaced as a set. 2. There is only one VPD card for all of the L3 modules. Replacing any L3 module requires replacing the associated VPD card.

  • Page 908: System Clock Card

    1. Squeeze the tabs on the clock card and push the card straight in. 2. Replace the fan chassis. See “Fan Chassis” on page 895. 3. Turn on power as described in “Powering the System On” on page 826. Eserver pSeries 690 Service Guide...

  • Page 909: Aluminum Backplane Stiffener

    Aluminum Backplane Stiffener Use the following procedure when populating the system with MCM processors that employ the use of copper heatsinks, or if you will be replacing a system backplane prior to November 2003. Removal 1. Turn off the power as described in “Powering Off and Powering On the System” on page 825. 2.
  • Page 910 3 Aluminum Backplane Stiffener 7 MCM with VPD Card Kit 4 MCM Alignment Rods 8 Aluminum Backplane Stiffener Retaining Screws (quantity 8) Replacement To replace the aluminum stiffener follow the removal procedure in reverse order. Eserver pSeries 690 Service Guide...

  • Page 911: Processor Subsystem Chassis

    Processor Subsystem Chassis CAUTION: This unit weighs more than 55 kg (121.2 pounds). Material handling systems such as levers, slings, or lifts are required to safely move it. When this is not possible, specially trained persons or services (such as riggers or movers) must be used. Three people are required to handle this operation: one person to push the chassis, and two people to pull the chassis.
  • Page 912 Mating the two surfaces is critical for the processor to function properly. 1. Position the lift tool such that the new processor subsystem chassis can be moved onto the lift plate. 2. Install the wheel chocks and engage the brake. Eserver pSeries 690 Service Guide...

  • Page 913: Memory Books And Memory Blanks

    3. Position the plate at the correct level, and move the new processor subsystem chassis onto the tool with the rear side flush with the lift plate. Strap the processor subsystem chassis to the lift plate using the tie-down strap. 4.

  • Page 914: Fan Controller

    3. Tighten the knurled captive screws to the fan assembly. 4. Plug all cables into their correct location in the DCA. 5. Press the white Service Complete button on the UEPO switch to indicate completion of this procedure. Eserver pSeries 690 Service Guide...

  • Page 915: Processor Fan Assemblies

    Processor Fan Assemblies Removal Attention: The fan controller weighs approximately 5 Kg (11 lb.) 1. Locate the fan assembly to be replaced. 2. Note the state of the fan controller’s LEDs. 3. Press the green Start Service button on the UEPO switch. 4.

  • Page 916: I/O Subsystem Pci Slot Led Definitions

    Perform PCI adapter remove, replace, or install only when directed by the PCI hot-plug procedures. Off/No power The PCI slot power is off. If the system power is off, perform non-hot-plug PCI adapter remove, replace, or install procedure. Eserver pSeries 690 Service Guide...

  • Page 917: Pci Adapters

    PCI Adapters Note: Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. A system with Linux installed on one or more partitions must be shut down and powered off before replacing any PCI adapter or device assigned to a Linux partition. Follow the non-hot-pluggable adapter or device procedures when replacing a PCI adapter or device in any partition with Linux installed.

  • Page 918: Removing A Pci Adapter Cassette

    The following illustration shows the PCI adapter cassette. 1 PCI Adapter Cassette 2 Handle-Release Lever Latch 3 Locking Bar 4 Handle Release Lever 5 Handle 6 PCI Adapter Tailstock Tab 7 Adapter Cassette Pull Tab Eserver pSeries 690 Service Guide...
  • Page 919 To remove a PCI adapter cassette, do the following: 1. Determine which PCI adapter cassette you are removing. 2. Disconnect any cables that are connected to the PCI adapter. 3. Press the handle release lever, then push the handle to the down position. See the following illustration.
  • Page 920 Do not force the PCI adapter cassette out of the PCI adapter slot. The cassette will slide out smoothly when this step is performed correctly. c. Do not remove more than one adapter cassette at a time. Eserver pSeries 690 Service Guide...
  • Page 921 Replacing a PCI Adapter Cassette: Attention: Perform this procedure only when you are instructed to from “Removing a Non-Hot-Pluggable PCI Adapter” on page 903 or “Hot-Pluggable PCI Adapter” on page 904. Before you replace the PCI adapter cassette, check the following: v Before installing a PCI adapter cassette in the system, an adapter or blank filler must be installed in each PCI adapter cassette and the top cover for the system must be installed.
  • Page 922 7. As you slide the cassette into the slot, ensure that the dovetail rail on the top of the PCI adapter cassette aligns with the mating slots on any cassettes that might be installed on the left and right sides. 8. Push the cassette in until it is flush with any other installed cassettes. Eserver pSeries 690 Service Guide...
  • Page 923 9. Visually check to ensure that the cassette is parallel with the cassettes to the left or right. If the cassette is not parallel with the neighboring cassettes, the cassette dovetail rails might not be correctly engaged. If the cassette is not correctly aligned, you might need to pull it out so you can see the ends of the dovetail rails.
  • Page 924 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 925 11. Answer YES to Keep Definition. Press Enter. 12. The ARE YOU SURE screen displays. Press Enter to verify the information. Successful unconfiguration is indicated by the OK message displayed next to the Command field at the top of the screen.
  • Page 926 Align the bottom edge of the PCI cassette cover with the PCI adapter guide rail on the I/O backplane. Note: If there is a cassette to the left of the one you are installing, align the ridge on the cover with the ″tick″ in the notch of the neighboring cassette. Eserver pSeries 690 Service Guide...
  • Page 927 e. Slide the cassette partially into the guide. f. Ensure that the dovetail on the top track aligns with its mating component(s) on both sides. 1 I/O Subsystem 2 PCI Adapter Cassette g. When the cassette is fully inserted, prepare to activate the handle by lowering the locking bar. Lift the handle all the way up until you hear a click.
  • Page 928 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 929 Identify a PCI Hot-Plug Slot Allows the user to identify a PCI slot. The selected PCI slot will go into the Identify state. Unconfigure a Device Allows the user to put an existing PCI adapter into the Defined state if the device is no longer in use. This step must be completed successfully before starting any removal or replacement operation.
  • Page 930 9. Use a small screwdriver to lift the guide lock, and slide the card arm away from the PCI card until the card end is free. 10. Push the lower-front heel off the card, and remove the PCI card from the assembly. Eserver pSeries 690 Service Guide...
  • Page 931 Replacement: 1. Ensure that you have the following parts: v Bezel and linkage subassembly v Cover v Clip v Insertion Clip (see the following note) v Short card arm v Long card arm Screws (10--2 are extra) Note: If you are installing a Gigabit Ethernet (FC 2969 type 9U), Ultra3 SCSI (FC 6203 Type 4Y), or 10/100 BaseT Ethernet (FC 4962 Type AF), use the additional clips listed below to help when you are seating the adapter during installation.
  • Page 932 2) To remove any slack between the top and bottom clips, use pliers or screwdriver to adjust the top front clip downward. If the top clip is pushed too far down without engaging the card, remove the top front clip by popping it off the rail. Reattach the clip and start again. Eserver pSeries 690 Service Guide...
  • Page 933 4. Attach the appropriate short card (if the card does not extend beyond the mark at the top of the linkage subassembly) or long card arm to the support arm of the linkage subassembly as follows: 1 Mark at the Top of Linkage 5 Short Adapter Subassembly 2 Top Rear Clip (Shown on the long...
  • Page 934 5. Tilt the top of the bezel away from the PCI card while lowering the bottom of the tailstock into bottom of the bezel, as shown in the following illustration. 1 Adapter Cassette Bezel 2 Short Card Arm 3 Long Card Arm Eserver pSeries 690 Service Guide...
  • Page 935 6. When the lower corner of the card is fully seated into the bezel, rotate the top of the bezel over the tailstock of the card. 1 Adapter Card 2 Adapter Card (Lower Corner) 3 Front Bottom Clip 4 Adapter Cassette Bezel 7.
  • Page 936 9. With the tailstock to the left on a flat surface, position the cover over the linkage assembly. 10. Tuck the top and bottom tabs at the left of the cover under the bezel. 1 Front Top Tab Eserver pSeries 690 Service Guide...
  • Page 937 2 Front Bottom Tab Snap the top-right corner of the cover over the guide bump on the linkage assembly. 12. Align the holes at the top of the cover with those in the linkage subassembly and screw the cover to the linkage subassembly in the sequence shown in the following illustration.
  • Page 938 1. Place the PCI adapter cassette assembly on a flat work surface with the cover facing up, and the top of the adapter facing you. See the following illustration. 1 Cover 3 Top of Cover 2 Handle Eserver pSeries 690 Service Guide...
  • Page 939 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 Chapter 9. Removal and Replacement Procedures...
  • Page 940 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 Eserver pSeries 690 Service Guide...
  • Page 941 5. Remove the bezel, as follows: a. Locate the plastic latch fingers in the top part of the cassette. 1 Top of Cassette 2 Bezel 3 Plastic Latch Fingers b. 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.
  • Page 942 This action allows the bezel to be removed. 1 Bezel Extension 2 Plastic Cover Latch in Bezel Hook d. On the opposite side of the cassette (cover side), push the cover latch to release the bezel. 1 Cover Side 2 Cover Latch Eserver pSeries 690 Service Guide...
  • Page 943 e. 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...
  • Page 944 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 Eserver pSeries 690 Service Guide...
  • Page 945 7. Remove the metal EMC shield from the top of the tailstock. 1 Metal EMC Shield 8. Remove the blank filler or adapter that is installed in the cassette linkage assembly. Note: If there is a blank filler in the cassette linkage assembly, as shipped from the manufacturer, there are two adapter arms.
  • Page 946 Slide the long and short adapter arms away from the blank filler or adapter. 1 Long Adapter Arm 2 Release Tab 3 Release Tab 4 Short Adapter Arm 5 Slotted Tab Eserver pSeries 690 Service Guide...
  • Page 947 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 948: Replacing An Adapter In A Pci Adapter Cassette

    Metal edges might be sharp. 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. Eserver pSeries 690 Service Guide...
  • Page 949 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 950 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 951 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 933. a. Remove the adapter from its protective packaging and, if present, remove the plastic extension handle from the end of the adapter.
  • Page 952 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 Eserver pSeries 690 Service Guide...

  • Page 953: 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 954 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 955 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 956 1 Short-adapter Retaining Arm 2 Adapter or Blank Filler 3 Cassette Linkage Rail Eserver pSeries 690 Service Guide...
  • Page 957 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 958 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 959 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 960 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 961 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 962 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 963 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 964 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 965 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 966 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 967 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 968 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 969 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 970: Long Adapter Installation

    1. 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 Eserver pSeries 690 Service Guide...
  • Page 971 2. Rotate the adapter so that the adapter engages the slot in the bottom retaining clip and the top corner of the adapter is seated into the top adjustable adapter-retaining clip. Note: If the adapter is not a full-height adapter, slide the top adjustable adapter-retaining clip downward until the lower edge of the adapter is seated into the slot on the bottom retaining clip.
  • Page 972 3. Install the long adapter-retaining arm onto the cassette linkage rail, as shown in the following illustration, and slide the arm toward the adapter. 1 Cassette Linkage Assembly 3 Top Adapter Retaining Clip 2 Adapter Retaining Arm Eserver pSeries 690 Service Guide...
  • Page 973 4. Ensure that the top adjustable adapter-retaining clip catches the corner of the adapter as shown in the following illustration. 1 Top Adjustable-Retaining Clip 5. Ensure that the bottom edge of the adapter is held by the groove in the lower part of the adapter-retaining arm.
  • Page 974 7. Depress the handle release lever on the handle. Rotate the adapter handle until it is in the down position (adapter or blank filler moves up into the cassette assembly). 1 Handle 2 Handle Release Lever Eserver pSeries 690 Service Guide...
  • Page 975 Ensure the right end of the cassette linkage rail moves up into the cassette linkage assembly as shown: 1 Right End of Cassette Linkage 8. Position the adapter and cassette assembly with the handle on the left (in the down position) and the top facing away from you.
  • Page 976 9. Install the cover on the cassette assembly by placing the cassette cover on the cassette assembly as shown. Slide the cover toward the handle until the hole in the cover aligns with the hole in the cassette assembly. 1 Handle 2 Hole Aligned in the Cover Eserver pSeries 690 Service Guide...
  • Page 977 Install the bezel assembly using the following procedure: a. 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 Chapter 9.
  • Page 978 1 Recess 3 Tab 2 Grooves 4 Bezel d. Insert the two tabs on the bezel extension into the two slots on the cassette assembly. 1 Tabs Eserver pSeries 690 Service Guide...
  • Page 979 11. Check for the following: Ensure that the extension arm engages the three pins on the cassette. You can see the pins in the holes in the arm. The bezel tab is seated as shown in the following illustration. 1 Pins b.
  • Page 980 1 Cover Latch 12. Position the adapter with the cover side facing up. Ensure that the holes are aligned, and insert the bushing as shown. 1 Bushing 2 Bushing-Lock Pin Eserver pSeries 690 Service Guide...
  • Page 981 1 Bushing 2 Bushing-Lock Pin 13. Insert the bushing-lock pin into the hole in the bushing. Push on the pin until it seats. 1 Location of the Installed Bushing and Bushing-Lock Pin Chapter 9. Removal and Replacement Procedures...
  • Page 982 2 Locking Bar 15. To install the metal EMC shield on the adapter bracket, grasp the metal EMC shield as shown in the following illustration, and do the following: 1 Metal EMC Shield 2 Adapter Bracket Eserver pSeries 690 Service Guide...
  • Page 983 a. Ensure that the shield slides up inside the top of the cassette. 1 Metal EMC Shield 2 Adapter Bracket Chapter 9. Removal and Replacement Procedures...
  • Page 984 1 Handle 17. Using your 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 Eserver pSeries 690 Service Guide...
  • Page 985 visible. If the adapter is not hot-swappable, the blue color is visible. 1 Orange indicates Hot-Swappable 2 Blue indicates Not Hot-Swappable 18. The adapter is ready to be installed into a system or an I/O drawer. For more information, refer to your system documentation.

  • Page 986: Replacing A Double-Wide Blind-Swap Adapter

    9. Connect power to the system and go to ″MAP 0410: Repair Checkout″ in the RS/6000 and Eserver pSeries Diagnostic Information for Multiple Bus Systems. Refer to “Powering the System On” on page 826 if necessary. 10. Ensure that the adapter is configured when the system completes the boot process. Eserver pSeries 690 Service Guide...

  • Page 987: Updating Xilinx Code On An Sp Switch2 Pci Attachment Adapter

    Updating Xilinx Code on an SP Switch2 PCI Attachment Adapter Note: This section applies only if the system is being used in a clustering environment. This procedure must be followed when an SP Switch2 PCI Attachment Adapter is installed or replaced, or when PSSP software is upgraded on a server or logical partition with an SP Switch2 PCI Attachment Adapter installed.
  • Page 988 14. When the server or logical partition is back up, from the CWS, type: Eunfence -p x nn (where x is plane 0 or 1 and nn is the node_number of the server or logical partition) RESPONSE: All nodes successfully unfenced. Eserver pSeries 690 Service Guide...

  • Page 989: Hot-Plug Steps For The Sp Switch2 Pci Attachment Adapter

    Hot-Plug Steps for the SP Switch2 PCI Attachment Adapter This procedure must be followed when doing hot-plug removal and replacements steps for the SP Switch2 PCI Attachment Adapter. On the control workstation (CWS) or from the server node, do the following: 1.

  • Page 990: I/O Subsystem Rio Riser Card

    4. Remove the two screws that attach the RIO riser card to the I/O subsystem backplane. 5. Carefully pull the card out of the slot as shown in the following illustration. 1 RIO Riser Card Replacement Replace in reverse order. Eserver pSeries 690 Service Guide...

  • Page 991: I/O Subsystem Distributed Converter Assembly (Dca)

    I/O Subsystem Distributed Converter Assembly (DCA) Notes: 1. If multiple I/O planars or I/O Drawer DCAs are being replaced during a maintenance window, then they must be replaced one at a time in order to ensure the I/O Drawer serial number does not become damaged.
  • Page 992 5. Alternate tightening the left and right thumbscrews until both are fully torqued in. 6. Check torque on both thumbscrews. 7. Plug all cables into their correct location in the DCA. 8. Press the white Service Complete button on the UEPO switch. Eserver pSeries 690 Service Guide...

  • Page 993: I/O Subsystem I/O Backplane Assembly

    I/O Subsystem I/O Backplane Assembly Removal Note: If multiple I/O planars or I/O Drawer DCAs are being replaced during a maintenance window, then they must be replaced one at a time in order to ensure the I/O Drawer serial number does not become damaged.
  • Page 994 4. Upon contact, insert the insertion tool (part number 11P4789) to cam the backplane into the connector. 5. Pry with the tool until the screw holes on the chassis and the board align. 6. Secure with two screws. 7. Reinstall all adapters and reconnect all cables to the replaced I/O backplane. Eserver pSeries 690 Service Guide...

  • Page 995: I/O Subsystem Dasd Hard Disk Drive Assembly

    I/O Subsystem DASD Hard Disk Drive Assembly Note: Linux does not support hot-plugging any hot-pluggable PCI adapters or devices. A system with Linux installed on one or more partitions must be shut down and powered off before replacing any PCI adapter or device assigned to a Linux partition. Follow the non-hot-pluggable adapter or device procedures when replacing a PCI adapter or device in any partition with Linux installed.
  • Page 996 Note: If the tab is not aligned with the slot, do not raise the handle. Remove the assembly and start again. 8. Lift the black handle to move the assembly in slightly. 9. Lift the handle and push forward until the blue latch hooks the assembly body. Eserver pSeries 690 Service Guide...

  • Page 997: I/O Subsystem Dasd 4-Pack

    I/O Subsystem DASD 4-Pack Removal 1. Press the green Start Service button on the UEPO switch. 2. Locate the DASD backplane to be replaced. 3. Turn off the power as described in “Powering Off and Powering On the System” on page 825. 4.

  • Page 998: I/O Subsystem Fan

    Replace in reverse order. When you have completed the replacement of the DASD fan, turn on the power as described in “Powering Off and Powering On the System” on page 825, and press the white Service Complete button on the UEPO switch. This completes the replacement. Eserver pSeries 690 Service Guide...

  • Page 999: I/O Subsystem Chassis

    I/O Subsystem Chassis Removal Attention: This process requires: v The use of a lift tool (part number 09P2481) and lift-plate assembly tool (part number 11P4369). v The lift tool wheels must be chocked to prevent the chassis from moving during the operation. The frame must not be on its casters, the leveling pads must be engaged to prevent the frame from moving during the operation.
  • Page 1000 9 Half I/O drawer filler plate 5 Front Cover Rear: 1 PCI I/O Subsystem Chassis 3 Blind-swap cassette or PCI filler with no adapter 2 RIO Riser Card, part of the I/O subsystem 4 PCI I/O Backplane backplane assembly Eserver pSeries 690 Service Guide...
  • Page 1001 Replacement Notes: 1. If you are replacing this assembly with a new assembly, the manufacturing label with the machine type, model number, and the serial number for the subsystem must be ordered to apply to the new part. For information on replacement labels, see Chapter 10, “Parts Information”, on page 987. 2.

Table of Contents