International Technical Support Organization SG24-4690-00 A Technical Introduction to PCI-Based RS/6000 Servers April 1996
IBM International Technical Support Organization SG24-4690-00 A Technical Introduction to PCI-Based RS/6000 Servers April 1996
Take Note! Before using this information and the product it supports, be sure to read the general information under “Special Notices” on page xv. First Edition (April 1996) This edition applies to the PCI-based RS/6000 servers, Model E20 and Model F30, for use with the AIX Version 4.1.4 Operating System. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below.
Abstract After the successful introduction of the PCI-based RS/6000 workstations (40P/43P), the RISC System/6000 family of products has been expanded to include a new line of workgroup servers based on the PowerPC microprocessor, the Peripheral Component Interconnect (PCI) and the PowerPC Reference Platform Specification (PReP). These servers, which offer large memory and internal disk capacities, PC I/O compatibility and flexible configurations, use “industry standard” components and subsystems.
iv Introduction to PCI-Based RS/6000 Servers
Contents Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Rationale for the PowerPC Reference Platform Specification . . . . . . 1.2 Introducing the PowerPC Reference Platform Specification . . . . . . . 1.
3.1.1 Backplanes . . . . . . . . . . . . . . . 3.1.2 Hot-Swap Bays and Banks . . . . . . 3.2 Installation . . . . . . . . . . . . . . . . . . 3.2.1 Accessing the Hot-Swap Banks . . . 3.2.2 Installing Drives in Bank C . . . . . 3.2.3 Installing Drives in Bank D . . . . . . 3.2.4 Installing Drives in Bank E . . . . . . 3.2.5 Disk Carriers . . . . . . . . . . . . . . 3.3 Using the Hot-Swap Subsystem . . . . . 3.3.1 Adding a New Drive to a Live System 3.3.2 Removing a Drive from a Live System 3.3.
5.4.5 Creating System Backups on Microchannel-Based RS/6000 Systems 5.4.6 Cloning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 Graphics Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.1 Installing the S15 Graphics Adapter . . . . . . . . . . . . . . . . . . . . 5.6.2 Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.
7.2.2 Device-to-Device Cables . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3 Terminators for Use with this Adapter . . . . . . . . . . . . . . . . . 7.3 Cabling the SCSI-2 Fast/Wide Differential PCI Adapter . . . . . . . . . . 7.3.1 Adapter-to-First Device Cables . . . . . . . . . . . . . . . . . . . . . 7.3.2 Device-to-Device Cables . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.3 SCSI-2 F/W Differential PCI Adapter Terminators . . . . . . . . . . . 7.3.
10.6.6 Operator Panel F30 LED Status 10.6.7 Dealing With Power Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix A. Firmware Checkpoint Three-Digit Codes . . . . . . . . . . . 189 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
x Introduction to PCI-Based RS/6000 Servers
Figures 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. Copyright IBM Corp. 1996 Old Compatibility Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Innovation Within The Old Compatibility Model . . . . . . . . . . . . . . . PReP Specification Compatibility Model . . . . . . . . . . . . . . . . . . . PReP Specification Design Environment . . . . . . . . . . . . . . . . . .
45. 46. 47. 48. 49. 50. 51. 52. 53. 54. 55. xii Sample Network Topology . . . . . . . . . . . . . . . . . Network Topology Used in Our Lab . . . . . . . . . . . . Defining the Third Network . . . . . . . . . . . . . . . . . Defining the Route Between First and Second Networks Machine Object Definition Menu . . . . . . . . . . . . . . Resource Object Definition Menu (SPOT Resource) . . Initial Boot Screen . . . . . . . . . . . . . . . . . . . . . . System Management Services Menu . . . . . . . . . . .
Tables 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. Copyright IBM Corp. 1996 PowerPC and Bus Specification . . . . . . . . . . . . . . . . . . Optional Disk Drives on Model E20 . . . . . . . . . . . . . . . . Optional Tape Drives on Model E20 . . . . . . . . . . . . . . . Optional CD-ROM drive on Model E20 . . . . . . . . . . . . . . Supported Monitors on Model E20 . . . . . . . . . . . . . . . .
xiv Introduction to PCI-Based RS/6000 Servers
Special Notices This publication is intended to help system engineers, system administrators, customer personnel and users to support, configure and manage the PCI-based RS/6000 Servers, RS/6000 Model E20 and RS/6000 Model F30. The information in this publication is not intended as the product specification for these systems.
IBM OS/2 PowerPC PowerPC 604 RISC System/6000 SP InfoExplorer Power Series PowerPC Reference Platform PS/2 RS/6000 400 The following terms are trademarks of other companies: C-bus is a trademark of Corollary, Inc. PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
Preface This document is intended to assist system engineers, customer engineers, system administration personnel, and customers in configuring, managing and using AIX Version 4.1 on the PCI-based RS/6000 servers, RS/6000 Model E20 and RS/6000 Model F30. It contains descriptions of processes which are unique to AIX Version 4.1 on PCI-based RS/6000 servers. Practical configuration and environment examples are provided as well as hints and tips to address "how-to" issues involving PCI-based RS/6000 servers.
Chapter 7, “SCSI Cabling” This chapter describes the main SCSI cabling features used with the PCI-based RS/6000 servers. It addresses frequently asked questions, such as: How many SCSI devices can be attached to a single SCSI adapter? What are the right cable features to attach more SCSI devices on the same SCSI chain? and others. Chapter 8, “Diagnostics Support” This chapter describes the diagnostics support provided by the PCI-based RS/6000 servers.
How Customers Can Get Redbooks and Other ITSO Deliverables Customers may request ITSO deliverables (redbooks, BookManager BOOKs, and CD-ROMs) and information about redbooks, workshops, and residencies in the following ways: IBMLINK Registered customers have access to PUBORDER to order hardcopy, to REDPRINT to obtain BookManager BOOKs IBM Bookshop — send orders to: usib6fpl@ibmmail.com (USA) bookshop@dk.ibm.
Internet Listserver With an Internet E-mail address, anyone can subscribe to an IBM Announcement Listserver. To initiate the service, send an E-mail note to announce@webster.ibmlink.ibm.com with the keyword subscribe in the body of the note (leave the subject line blank). A category form and detailed instructions will be sent to you.
Acknowledgments This project was designed and managed by: Miguel Crisanto International Technical Support Organization, Austin Center The authors of this document are: Alexandre Bonfim de Azevedo IBM Brazil Giampiero Galli IBM Italy Simon M. Robertson IBM UK Miguel Crisanto IBM Austin Thanks also to our editor: Marcus Brewer Editor, ITSO Austin Center This publication is the result of a residency conducted at the International Technical Support Organization, Austin Center.
xxii Introduction to PCI-Based RS/6000 Servers
Chapter 1. Introduction IBM offers a family of powerful workgroup servers, the RS/6000 Model E20 and the RS/6000 Model F30, that are ideal for running small business and departmental applications. These servers use the PowerPC processor architecture and offer large memory capacities, PC I/O compatibility and flexible configurations. The RS/6000 Model E20 is the lowest-cost entry server and is intended to be the RS/6000 family's competitive product for the price-conscience entry server market.
The PowerPC Microprocessor Common Hardware Reference Platform, previously known as the Common Hardware Reference Platform (CHRP), is a superset of the PReP Specification. Although IBM has not yet announced any system based on this new specification, it is becoming very popular, and many companies have published their intentions to develop CHRP-compliant systems. For this reason, we include a description of the CHRP specification in this chapter. 1.
To be sustainable and to continue growing, the computer industry must define computer architectures which allow system and application designs to utilize the latest silicon, interface, storage, display, and software technologies. The key to these new computer architectures is the ability of the software to abstract the hardware from the operating system kernel and applications without sacrificing compatibility or performance. Figure 3. PReP Specification Compatibility Model.
Independent software vendors (ISV) would like to develop for a large, installed base of hardware systems and on as few operating system platforms as possible. For this to happen, an industry standard computer architecture is required.
Portables Medialess Desktop Workstations Servers Because PReP requires machine abstractions, the specification accommodates the evolution of software and hardware technologies without losing system compatibility. The PReP specification covers: Hardware Configuration The hardware configuration defines the minimum and recommended hardware standards and capacities required to be PowerPC Reference Platform-compliant and compatible with targeted operating environments.
Macro Power Management This uses system software to control the hardware. Macro Power Management is, by far, the more powerful technique and thus is the basis for the PReP Power Management model. 1.3 The PowerPC Microprocessor Common Hardware Reference Platform (CHRP) This section introduces the PowerPC Microprocessor Common Hardware Reference Platform, previously referred to within the industry as Common Hardware Reference Platform (CHRP), and describes the purposes and the goals of this platform.
Apple, IBM, Microsoft, Novell, and SunSoft are planned to support the PowerPC Platform. The PowerPC Platform, combined with the superior performance of the PowerPC RISC microprocessor, will support today's advanced applications and drive the next generation of applications which address emerging customer requirements for video, multimedia, virtual reality, speech recognition, 3D graphics, and enhanced communications.
so on) and newer bus architectures, interfaces and protocols (PCI, PC Card, IrDA, and so forth) provide higher levels of performance or utility that are not achievable by the older standards. The architecture allows platform and system designers to determine which buses, interfaces and protocols best suit their target environment. To provide a flexible address map. Another key attribute of this specification is the relocatability of devices and subsystems within the PowerPC address space.
PowerPC Microprocessor Common Hardware Reference Platform: A System Architecture Specification. The AIM Alliance has established the CHRP certification process to accomplish the following specific goals: To establish concrete testing criteria for determining the compliance with the requirements stated in the document titled, PowerPC Microprocessor Common Hardware Reference Platform: A System Architecture. To ensure multiple operating system interchangeability on certified CHRP computer systems.
10 Introduction to PCI-Based RS/6000 Servers
Chapter 2. PCI-Based RS/6000 Server Hardware The PCI-based RS/6000 server's hardware design is driven by accepted “industry standards” both formal and de-facto. This means that open, standard interfaces are used whenever possible, and much of the expansion of the system will be performed by the end user utilizing standard adapters and controllers. The design of the PCI-based RS/6000 servers is intended to have much in common with the PC Server line of products from Boca Raton/Raleigh.
Figure 5. PCI RS/6000 Entry Server Logical Block Diagram 2.1.1 The PCI Bus Architecture The Peripheral Component Interconnect (PCI) is a specification standard for computer bus implementation developed by the PCI Special Interest Group (PCI-SIG), led by a group of companies including Compaq, Digital, IBM, Intel and NCR. There are now over 300 companies in the PCI-SIG supporting the architecture and currently producing PCI products.
(Version 2.0 in April of 1993) included upgrade capability through expansion connectors. According to PCI Specification Version 2.0, the PCI bus operates on 32- or 64-bits of data at a clock speed of 33 MHz. This yields a local bus performance of 132 MB/sec for 32-bit transfers and 264 MB/sec for 64-bit transfers. The next PCI Specification (Version 2.1) is expected to include a definition of 66 MHz PCI capability, increasing local bus performance to 528 MB/sec for 64-bit transfers.
The key to cross-platform compatibility is processor independence. Until PCI, different systems used different buses, such as ISA, EISA, NuBus, and so forth. Now, different systems can use one bus. Multi-bus Support An important aspect to PCI-based system architecture is support for multiple PCI buses, operating transparently to existing software.
Table 1. PowerPC and Bus Specification Specification PowerPC PCI ISA(8) ISA(16) EISA Processor Speed (601-604) 66-132 - - - - Databus 64 64 8 16 16/32 Address Bus 32 64 20 24 24/32 Bus Clock 66 MHz 33 MHz 4.7 MHz 8.3 MHz 8.3 MHZ Interrupts - 4 6 11 11 DMA Channel - busmaster 3 7 7 The solution to the problem is to use the PCI local bus as the primary system bus and the ISA bus as an expansion bus.
Up to 66 MHz bus clock Superscalar design with integrated integer, floating-point and branch units 16 KB four-way set-associative instruction cache 16 KB four-way set-associative data cache 64-bit memory interface with 32-bit addressing Virtual memory support for up to four petabytes (252) Real memory support for up to four gigabytes Support for Big-Endian and Little-Endian modes Nap power management mode Figure 6. PowerPC 604 Microprocessor Logical Block Diagram 2.2.
The cache controller supports disable, inhibit and invalidate functions in addition to the expected L2 memory caching operations. 2.2.3 The Memory Controller and PCI Bridge The Memory Controller chip is directly attached to the processor bus and acts as a PCI Bridge to the primary PCI bus as well. It issues two different bus interfaces: The CPU bus interface that runs at 66 MHz The PCI bus interface that runs at 33 MHz The memory controller supports address and data-bus parity generation and checking.
2.2.6 The Secondary PCI Bus The secondary PCI bus is generated through the use of a PCI-to-PCI bridge chip. This component regenerates a second PCI bus interface from the primary bus and uses it to drive additional PCI expansion card slots. The PCI-to-PCI bridge handles all the arbitration for devices on the secondary bus. Due to arbitration restrictions on the primary PCI bus, the SCSI interface resides on this secondary PCI bus.
2.3 Electronics Partitioning The system electronics are divided into two cards for packaging. One card contains the processor and its support electronics, master clock generation, memory controller and IPL microcode. The other card is considerably larger and contains the native I/O subsystems, memory modules and I/O expansion slots. Figure 7 shows how the components are split across the two boards in the system. Figure 7.
The X-bus interface An IòC bus which supports RAS monitoring features on processor card 2.4 RS/6000 Model E20 Product Description The RS/6000 Model E20 is the first member of the PCI-based RS/6000 family of servers to become available. It is designed to allow for system growth in memory, disk and media devices as the customer's needs grow. The E20 server is a low-priced, high performance commercial server. By combining AIX Version 4.1.
2.4.1 Standard Features In this section, we describe the standard features of the RS/6000 Model E20 and point out their most important characteristics. Processor Subsystem The PCI-based RS/6000 Model E20 server features the PowerPC 604 microprocessor at 100 MHz. The processor includes an L1 cache composed by a 16 KB instruction and a 16 KB data cache. The L2 cache is integrated onto the CPU board and is always present in the base system. The synchronous L2 cache is 512 KB in size.
Figure 9. RS/6000 Model E20 Front View Slots Eight slots are available which can accommodate the following adapters types: Five slots for PCI adapters Two slots for ISA adapters One shared slot that can accommodate either a PCI or an ISA adapter Integrated SCSI-2 adapter The system comes standard with an integrated PCI-based internal SCSI-2 fast/wide controller that can be used for internal SCSI-2 devices only.
2.4.2 Supported Optional Features In this section, we consider as “optional features” the internal optional devices, external adapters and external subsystems that can be configured on the RS/6000 Model E20. 2.4.2.1 Internal Disk Drives Six internal SCSI-2 disk drives can be accommodated in the internal bays of the system. The disk drives that can be installed and configured are described in Table 2. Only disk drives with a 1-inch height (half-height) are supported for internal use. Disk drives with 1.
2.4.2.3 Internal CD-ROM Drives A maximum of two internal CD-ROM drives can be installed in the E20 system. The CD-ROM provides four-speed performance with the convenience of loading CDs without a caddy. Table 4. Optional CD-ROM drive on Model E20 CD-ROM Capacity Feature Number 600 MB # 2616 Interface SCSI-2 (8 bit) Interface Speed (average) 600 KB/sec Interface Speed (burst) 5.0 MB/sec Bays 1 half-height Note: Maximum CD-ROM Drives: 2 2.4.2.
Table 5. Supported Monitors on Model E20 Description Model Feature Code Screen Size P50 UV-N MPR-II Color Monitor 6553-503 3612 13.6" P50 UV-S MPR-II Color Monitor 6553-504 - 13.6" P50 TCO-92 Color Monitor 6553-523 - 13.6" P70 Color Monitor 6554-603 3613 15.9" P70 UV-S MPR-II Color Monitor 6554-604 - 15.9" P200 Color Monitor 6555-703 3614 19.1" P200 UV-S MPR-II Color Monitor 6555-704 - 19.1" P201 Color Monitor 6555-803 3615 19.1" IBM 14V Color Monitor 6324/001 - 13.
PCI SCSI-2 Differential Fast/Wide Adapter The adapter can burst data to devices on the SCSI bus at 20 MB/sec. It has a single connector for attachment of external differential devices. It is a shielded 68-conductor connector consisting of two rows of 34 female contacts. Both 8-bit and 16-bit device attachments are supported, but intermixing 8-bit and 16-bit devices is not supported.
Auto LANstreamer Token-Ring PCI Adapter (feature #2979) It is designed to allow a PCI-based RS/6000 server to attach to 4 Mbps or 16 Mbp s token-ring local area networks. The adapter automatically selects the correct token-ring speed (4-16 Mbps). It is compatible with all IBM PS/2 Token-Ring adapters; no new cables or network components are required. The adapter has one connector, RJ-45. The RJ-45 connector is used to attach to Unshielded Twisted Pair (UTP) cabling.
X.21 (not switched) up to 64 Kbps Each feature is selected by the cable, which can be ordered in 3m (9 foot) or 6m (18 foot) length. These are the main characteristics for this adapter: Code resident on the adapter off-loads low-level X.
card and an 8-port DB25 connector box, composed of eight asynchronous ports from a single I/O card slot. The main characteristics for this adapter are: Data rates up to 115.
2.4.2.7 External Subsystems The following is a list of the external subsystems which are officially supported in the RS/6000 Model E20. Disk Subsystems 7131 Model 105 SCSI Multi-Storage Tower 7137 RAID Disk Array Subsystem Model 412, 413, 414 7203 Model 001 External Portable Disk Tape Drive Subsystem 7207 Model 012 - 1.
2.4.3 RS/6000 Model E20 Limitations When planning or implementing an RS/6000 Model E20, give special consideration to the following limitations, which are also listed in the announcement letter for this product. Internal Disk Drives Only internal disk drives with a 1-inch height (half-height) are supported. Disk drives with 1.6-inch height (4.5 GB disks) are not supported.
that allows fast, easy addition and replacement of drives, also called “Hot-swap subsystem” (see Chapter 3, “Hot-Swap Subsystem” on page 41 for information about this subsystem). This system allows up to a maximum of 40 GB of internal storage capacity and features a flexible I/O subsystem of three PCI, three ISA and four shared slots.
Figure 10. RS/6000 Model F30 Bays Standard bays are composed of four media and six hot-swap disk bays which accommodate the following drives: Two of the media bays accommodate the following standard devices: – 3.5-inch diskette drive bay that accommodates a standard 1.44 MB diskette drive – 5.25-inch CD-ROM drive bay that accommodates a Quad-speed 680 MB CD-ROM drive with the convenience of loading a CD without a caddy. The tray loading mechanism provides support for 12cm and 8cm disks.
The system comes standard with an integrated PCI-based internal SCSI-2 fast/wide adapter that can be used only for internal, single ended, either fast/wide, narrow or both, SCSI-2 devices (maximum of seven). Standard I/O Ports The system provides the following standard I/O ports: Keyboard port. The IBM Enhanced Keyboard is an optional feature on the Model F30. Mouse port. A port is provided to support an optional three-button mouse. Two 9-pin D-shell serial connectors for external RS232 access.
Table 7. Optional Disk Drives on Model F30 Formatted Capacity 1.1 GB 2.2 GB 4.5 GB Feature number # 3082 # 3083 # 3084 SCSI Bus Rate MB/sec 20 20 20 Average Seek Time ms 7.2 7.8 8.3 RPM 7200 7200 7200 Avarage Latency ms 4.17 4.17 4.17 SCSI-2 F/W SCSI-2 F/W SCSI-2 F/W 16-bit 16-bit 16-bit 1 1 2 Interface Data Width Swappable Bays Note: Maximum Internal Half-height Disk Drives: 18 2.5.2.
2.5.2.5 PCI SCSI-2 Adapters The following two PCI SCSI adapters are supported: PCI SCSI-2 Single Ended Fast/Wide Adapter (feature #2408) PCI SCSI-2 Differential Fast/Wide Adapter (feature #2409) Each adapter occupies one PCI slot, and a maximum of seven adapters can be installed in the Model F30. Refer to 2.4.2.5, “PCI SCSI-2 Adapters” on page 25 for technical information about these SCSI-2 Adapters. As described in 2.5.
ISA 128-Port Asynchronous Controller These are the same adapters that can be installed and configured in the RS/6000 Model E20. Refer to 2.4.2.6, “Communication Adapters” on page 26 for technical information about these PCI and ISA adapters. 2.5.2.7 External Subsystems Here, we list the external subsystems that are officially supported in the RS/6000 Model F30.
2.5.3 RS/6000 Model F30 Limitations When planning or implementing an RS/6000 Model E20, give special consideration to the following limitations, which are also listed in the announcement letter for this product. Internal Disk Drives 4.5 GB Disk drives (1.6 inch height) require two hot-swappable bays. Graphics Adapter There can be a maximum of two graphics adapters installed in the system. SCSI Adapters There are also SCSI limitations, depending on the adapter, as shown in Table 9 on page 36. 2.
Table 10. PCI-based RS/6000 Comparison Performance Table Description C20 43P E20 F30 Processor PowerPC 604 604 604 604 Clock (MHz) 120 133 100 133 L2 Cache (MB) 1ñ 0.5 0.5 0.5 SPECint95 - 4.72 3.67 4.74 SPECfp95 - 3.76 3.13 3.49 SPECint_base95 3.85 ò 4.55 3.43 4.56 SPECfp_base95 3.50 ò 3.59 3.06 3.34 LINPACK DP (MFLOPS) 22.7 ò 27.8 23.5 23.1 LINPACK TPP (MFLOPS) 62.7 ò 67.5 62.3 69.0 tpm est. (02/96) 620 ò 400 735 850 ó Notes 1. Optional L2 Cache 2.
2.7.1 SPEC95 Software Benchmark SPEC95 is a forward step in the performance measurement of the core of a system. It covers the CPU, caches, memory, and compiler. The programs and datasets which make up the suite cannot "fit" into cache, making the benchmark more representative of real workloads. SPEC has also standardized the compiler settings so that the results for "base" measurements are more comparable between suppliers.
Chapter 3. Hot-Swap Subsystem The F30 is the first PCI-based RS/6000 server to provide hot-swap disk capability. The hot-swap subsystem allows the addition or removal of disk drives without powering-down the system. The hot-swap subsystem also allows applications to keep running which do not use the disk that has to be replaced or removed. The hot-swap subsystem uses special, hot-swappable disk carriers that allow you to easily plug and unplug disks in the system.
Hot-Swap Disk Drive Carrier The hot-swap SCSI disk drive carrier is a tray with built-in SCSI connectors that provide the interface between an industry standard SCSI 16-bit or 8-bit disk drive and the 80-pin backplane connector. The carrier includes two LEDs. One of the LEDs is used to indicate the status of the disk drive, and the other one is the power LED indicator for the carrier. Carriers are available for two drive types: narrow (half-height) and wide (full-height).
Figure 12. Installing Hot-Swap The second (feature #6421) and the third (feature #6422) backplanes are installed in banks D and E, respectively. The features, #6421 and #6422, contain all of the necessary hardware to completely enable up to six hot-swap disks to be installed in the machine: the backplane, the power cable, the SCSI controller, the SCSI cable, and mounting hardware.
Figure 13. Front Bays 3.2 Installation The requirements for installing hot-swap disk drives are not the same for all three banks. A general requirement is that each hot-swap bank requires a separate SCSI-2 adapter. In the case of the first bank, bank C in Figure 12 on page 43, it uses the integrated SCSI-2 controller. Banks D and E require the installation of one additional backplane each. These additional backplanes use the second power supply which is provided with the F30. 3.2.
. Figure 14. Removing the Front Panel This will provide you access to the hot-swap banks. If you only have one backplane installed you will be able to add or remove up to six disks. 3.2.2 Installing Drives in Bank C The backplane for bank C comes installed in the system. The SCSI IDs are automatically assigned by the backplane for each bank. Therefore, no jumpers are required on the drives. If your disk drive has SCSI ID jumpers set, you must remove them.
3.2.4 Installing Drives in Bank E Installation of drives in bank E is exactly the same as the procedure for installing drives in bank D. 3.2.5 Disk Carriers The disk carriers have two lights which enable you to determine the status of the drive. Figure 15 shows a diagram of the lights and the spin down button, and Table 11 explains their meanings. Figure 15. Disk Drive Light Table 11.
3.3 Using the Hot-Swap Subsystem Having the hot-swap subsystem is very useful. As previously mentioned, it allows you to add, remove or replace disk drives without shutting down and powering-off your system. There are, however, three levels at which you can use the hot-swap subsystem. First, you can use the hot-swap subsystem to simply add and remove disk drives from the system. You can buy and add new drives with ease, and these can be quickly configured into your system without affecting the users.
3.3.2 Removing a Drive from a Live System To be able to remove a hot-swap drive from the system without causing problems, you will have to tell AIX that you are removing the drive. 3.3.2.
3.3.3 Replacing a Previously Defined Drive If you add a disk drive which was already configured to the system and was removed using the procedures described above, then you can simply add the new drive as described in 3.3.1, “Adding a New Drive to a Live System” on page 47. 3.3.3.1 Replacing a Previously Defined Drive into the Same Bay If a drive was physically removed without first being logically removed from the operating system, then AIX may have problems.
Running lspv now shows: lspv hdiskð hdisk1 hdisk2 hdisk3 ðððððððða641877c ððððððððbða645bð ðððððððða62746ð4 ððððððððbða645bð rootvg None None None 4. rmdev -d -l hdisk1 5. rmdev -d -l hdisk3 6. cfgmgr Running lspv now shows the correct disks: lspv hdiskð hdisk1 hdisk2 ðððððððða641877c ððððððððbða645bð ðððððððða62746ð4 rootvg None None 7. importvg -y testvg hdisk1 8. Mount all the filesystems. You may have to run fsck -y on the filesystems first if they were written to while the disk was removed. 3.3.
If the disk is part of the root volume group and the filesystems which are on the disk can't be unmounted, then you can either wait for a reboot of the system or remove the disk from the volume group, and then re-add the disk by performing the following: 1. Remove all the mirrored copies from the mirrored disk (for example, if we had a logical volume called lv00, there were a total of two copies of the logical volume and the disk which was removed was hdiskx): rmlvcopy lvðð 1 hdiskx 2.
52 Introduction to PCI-Based RS/6000 Servers
Chapter 4. Boot Support and Firmware The PCI RS/6000 Entry Server systems are based on the PowerPC Reference Platform Specification (PReP); thus, in contrast to the microchannel-based RS/6000 systems systems, their hardware is not bound to a specific operating system. In order to separate the hardware from the software, an abstraction layer, defined in PReP, is required.
data. In the case of AIX, the abstraction layer builds the required IPL control block before the AIX boot image is loaded. In the first part of this chapter, we will explain the components involved in the boot process: Boot record Firmware Software ROS NVRAM Boot image Then, we will describe the boot process performed by the firmware, and finally we will give an introduction to the System Management Services (SMS) programs. 4.
Different partitions could hold different operating systems or different versions of AIX. The user could be able to choose the operating system to boot, as in “dualboot” on OS/2 and DOS. The problem with this implementation is that both the Master boot record and the AIX boot record are required to start on disk block 0. To satisfy this requirement, the boot record on PCI-based RS/6000 systems is a combination of both, as shown in Figure 19. Figure 19.
1. Firmware 2. Software ROS for AIX 3. AIX boot image 4.2.1 Firmware The firmware is the first code executed when the machine is powered-on. Firmware takes the system from a power-on state to a state where an operating system loader is in memory, ready for execution. Firmware is typically stored in read-only memory (ROM) or in programmable read-only memory (PROM). The firmware on PCI-based RS/6000 systems performs the following steps: 1. Initializes processor registers 2.
Little-Endian format and must be converted to Big-Endian format as required by AIX. Software ROS converts the data into Big-Endian format and handles all the differences in formats and structures so that the AIX kernel will be able to use this data at a later time. Prior to locating the AIX boot image, Software ROS updates the IPL control block with the address of the converted residual data. 4.2.2.
Configuration data for non-native ISA devices area Additionally, NVRAM contains a header that describes the location and length of these areas. Figure 20. NVRAM Layout GEArea Contains definitions of global environment variables which can be updated and used by different operating systems. Global variables are used mainly by the firmware for cached data or by operating systems to communicate with the firmware.
Table 12 (Page 2 of 2). Platform Types Name rspc Description PCI-based RS/6000 systems The AIX boot image used in each of the above platforms is platform-specific. To create platform-specific boot images, AIX provides support for the following two issues: Recognition of the platform type The given platform is specified in the IPL control block built by Software ROS. The boot utility command, bootinfo -T, inspects the IPL control block and prints the platform type to the standard output.
Figure 21. Relation Map of Base Proto and Proto Extension Files Base Proto Files: The Base Proto files are platform specific. They contain libraries, non-device-related commands and ODM data files relevant to a specific platform. They are named with the platform type as their prefix: For microchannel-based RS/6000 systems: rs6k.disk.proto, rs6k.tape.proto, rs6k.cd.proto, rs6k.tok.proto, rs6k.ent.proto, rs6k.fddi.proto For SMP systems: rs6ksmp.disk.proto, rs6ksmp.tape.proto, rs6ksmp.cd.proto, rs6ksmp.
Proto Extension Configuration File As an example, for the PCI-based RS/6000 platform, the file is called rspc.pcfg and is located in the directory /usr/lib/boot/protoext. 4.3.1.2 RAM File System When the bosboot command is running, it determines the type of platform and the boot device for the boot image. It builds the prototype file based on the information provided by the base proto and proto extension files(4.3.1.1, “Base Proto and Proto Extension Files” on page 59).
Figure 22. Boot Image Layout on PCI-Based RS/6000 Systems When the system is booted, the firmware loads the first sector containing the Master Partition Header, which includes the AIX boot record and the partition table. The Partition Entry Offset and the Length of Partition In Sectors, extracted from the first partition entry in the table, indicates where to find the next partition to be loaded and the size of the partition, respectively. This partition contains the Software ROS code.
4.3.3 Boot Image Creation on PCI-Based RS/6000 Systems To support boot image creation for PCI-based RS/6000 systems, several commands involved within the boot support process were changed in AIX Version 4. The changes were limited to a minimum, and the main idea is to still use the bosboot command to generate a boot image. Some options have been changed in bosboot to support the new platforms (SMP and RSPC systems). In fact, most of the changes are hidden to the user.
Figure 24. AIX Version 4 Boot Image Creation When the bosboot command is started, it creates a RAM file system and calls the mkboot command to create the boot image as is normal for an AIX system. Upon detection of a RSPC system, the bosboot command calls the mkmboot routine to encapsulate the AIX Version 4 boot image into the RSPC-style boot image. 4.4 Understanding the Firmware The firmware is the first code to execute when the machine is powered-on.
Firmware Core Brings the system up to where the compressed image has been decompressed and running Virtual Disk Contains the firmware modules required to support each hardware subsystem 4.4.1 Firmware Boot Sequence This section describes the firmware booting process on PCI-based RS/6000. This is also shown on Figure 25. Figure 25. Firmware Boot Sequence When the system is powered-on, the hardware passes control to the storage address 0xfff00100, the firmware entry point. 1.
If the firmware is corrupted, run the firmware recovery procedure (see 4.4.4, “Firmware Recovery” on page 69). 6. The firmware core copies a particular part of the firmware code into the small amount of memory. This firmware code runs the memory POST and configures 3 MB of good memory. If it fails, the hard file LED is turned on, and the system stops. Passed Critical Phase After 3 MB of good memory has been successfully configured, the system will not stop.
13. If Power-On Password or Privileged Access Password options are in effect, then the Password screen appears. There are three attempts to the correct password; otherwise the 8-digit error code 00016005 is displayed, and the system stops. The only way to recover the system is to power-off and power-on again. 4.4.2 Firmware Passwords The user can limit access to the system by using passwords. The passwords can be up to eight characters long and are stored in NVRAM.
4.4.3 Firmware Flash Update There are several situations where a firmware flash update may be required. For example, after a field EC (engineering change) or to provide firmware support for a new adapter. The firmware flash update can be performed by the user in Normal mode or by the system in Recovery mode. The default is the Normal mode update performed by the user from the SMS Tools (Utilities in the ASCII version) menu. Messages and errors are communicated through the menu pop-up interface.
4.4.4 Firmware Recovery During the firmware boot process, one of the first tasks is to verify the Cycle Redundancy Check (CRC) of the firmware code. If the update portion of the firmware has a CRC miscompare (is corrupted), you will see the following symptoms: One short beep will be sounded on the speaker. The hard disk LED will blink continuously. The diskette drive LED is selected or blinking, waiting for a diskette to be inserted. The display or tty is blank.
one of the icons will be the memory icon. During the display of this icon, an 8-digit error code will be displayed if the L2 cache is not fully functional. The remainder of memory is also tested, and if a failure is detected, an 8-digit error code is posted. This error indicates which Dual Inline Memory Module (DIMM) slot is at fault. The basic algorithm for the system memory configuration is as follows: 1. Query each memory slot to see if there is a memory DIMM installed. If yes, determine its size.
Note The 8-digit POST error codes are listed and described in the User's Guide manual for the corresponding PCI-based RS/6000 system. 4.5 LCD Panel The LCD panel is part of the PCI-based RS/6000 hardware. During the boot process the system will display 3-digit codes on the left of the top row on the LCD panel. The intended use of the 3-digit codes is to assure the observer that the firmware is operational after power-on and before information appears on the console display.
Table 13.
To start the programs: 1. Turn on or shut down and restart the computer. 2. When the first screen appears, press the F1 key to use the GUI interface. To use the ASCII interface, press the F4 key. On an ASCII terminal, you can press either the number 1 or the number 4 key. Note: You must press above listed keys before the last indicator appears. 4.6.
select it. A number indicating the order of the startup sequence will appear on the device. To cancel the configured selections, the Cancel icon can be used. The ASCII interface offers an additional function (option 7. Boot Other Device) which can be use to boot directly from the specified device without having to change the boot-order list. 4.6.4 Test Menu The corresponding menu to the graphical Test menu in the ASCII SMS version is the Test the Computer menu.
Chapter 5. AIX Version 4.1.4 Support AIX Version 4.1.4 is the first supported operating system on the PCI-based RS/6000 servers, E20 and F30. These machines can be installed from a standard AIX Version 4.1.4, or later, installation CD-ROM or over the network. AIX Version 4.1.
This list cannot be changed. The second is a customized list, and it can be changed by using the bootlist command or by using System Management Services (SMS - see 4.6, “System Management Service (SMS)” on page 72). When AIX is installed, it will set the customized list using the bootlist command so that the hard disk which has been installed will boot when the RS/6000 is powered on. Figure 26 shows the menu in SMS which is used to change the customized Boot List. Figure 26.
With the introduction of the E20 came a new electronic key-switch function. As with the 43P, there is no physical key, but there is a static electronic key. The key-switch abstraction is set by the firmware at boot time. The provision of the electronic key is essential for the machine to boot AIX diagnostics from hard disk, which both the 40P and 43P are unable to do. 5.1.
5.1.3 bootlist Command On the E20 and F30 (and 43P), the bootlist command can be used to alter the customized Boot List. For example, you can set the customized Boot List with the following command: bootlist -m normal hdiskð This would set the customized Boot List in the NVRAM to hdisk0. Then, hdisk0 would then be used to attempt a boot in Normal mode. It should be noted that the Boot Device Order List service (which is the default Boot List) cannot be altered.
5.3 System Dump Support Your system will generate a system dump when a severe error occurs. System dumps can also be initiated by root, which is useful when, in the rare case, your system appears to have hung, but no dump has occurred. A system dump creates a "picture" of your system's memory contents and is useful for support staff and developers in helping determine why a system crashed. The AIX dump facility is included in the bos.sysmgt.serv_aid fileset.
Change the Directory to which Dump is Copied on Boot choosing a filesystem which will have enough space, determined by step 1, to accommodate the dump on reboot. Enter the following command (for example, using the /var filesystem): sysdumpdev -d /var In the above example, if the system were to crash and save a system dump in the paging space, upon reboot, AIX would copy the dump into the /var filesystem. 5.3.
CTL-ALT-NUMPAD1 will create a dump in the primary dump device, and CTL-ALT-NUMPAD2 will create a dump in the secondary dump device. Before AIX Version 4.1.4, on the PCI-Based RS/6000 Systems (40P/43P), the CTL-ALT-NUMPADx key sequences to initiate a system crash dump were not functional. This was because AIX expected the key to be in the Service position, and the key switch value on those systems is always set to Normal when AIX is operational.
5.3.4 Dump LCD Support With the current version, 4.1.4, of AIX, only the 0CX codes will be displayed by the front LCD panel on the E20 and F30. If the system crashes, there will be no flashing 888 followed by 102 or 103 as there is with microchannel-based RS/6000 systems. A system crash will cause a dump to be initiated immediately. In most cases, 0C2 will be displayed during the dump, and this will be followed by 0C0, for example, which indicates that a dump has completed.
5.4.1 The bootinfo Command The type of machine (platform type) being used can be determined with the bootinfo command. This command uses the device configuration databases to obtain information. In addition, the bootinfo command uses the values which are stored in NVRAM. Using bootinfo with the -T option displays the platform type of the machine. There are currently three values that the command can return. These are shown in Table 15. Table 15.
à ð Back Up the System Type or select values in entry fields. Press Enter AFTER making all desired changes. [Entry Fields] WARNING: Execution of the mksysb command will result in the loss of all material previously stored on the selected output medium. This command backs up only rootvg volume group.
/home/george/tmp, then /home/george/tmp. will be backed up, but none of the files contained within it will be backed up. Make BOOTABLE backup? This item applies to tapes only and will allow you to create a tape with or without a boot image. Normally, you would leave this option to its default of yes.
smit lsmksysb This will list all the files on your mksysb tape and in doing so, will verify the contents of the tape. Note The only way to test if a mksysb will boot correctly is by booting from that tape. 5.4.4 Restoring Your System Backup You can restore your mksysb by booting from the tape which you have created and following the instructions which are displayed. To boot from the tape, you have to press F4 (or 4 on an ASCII terminal) during the firmware boot, and select the tape device to boot from.
5.4.4.1 Restoring to Different Machines Creating a mksysb on one machine and using the backup to install several other machines can be useful and will save the time taken to perform multiple installations. A problem with this is that the mksysb may not contain enough device drivers to be able to run on the target machine. If you are going to restore a mksysb from one machine to another, always check to see that all the required device drivers are installed.
à DATA cfgsys ---- 777 ð ð /usr/lib/methods/cfgsys cfgsys_p ---- 777 ð ð /usr/lib/methods/cfgsys_p ENDOFDATA fi fi ð ${bosboot} -d$device -a $KERNEL rc="$?" rm -f /usr/lib/boot/protoext/tape.proto.ext.base.com.upmp ffl "$rc" -ne ð “ && cleanup "$CMD_EC" \ " ${dspmsg} -s $MSGSET $MSGCAT 18 \ á ñ Figure 29.
# # # # mkdir /tmp/clone cd /tmp/clone echo data > signature cp /var/adm/ras/bosinst.data . Refer to the section "Customizing the BOS Install Program" in InfoExplorer for more details about creating a bosinst.data file. You may want to customize it for your system to get a no-prompt install, in which case you will need to set more than is listed below (like CONSOLE and PROMPT) 2. Edit the bosinst.
BLVDISK= lslv -l hd5 | grep hdisk | head -1 | cut -d' ' -f1 ln -f /dev/r$BLVDISK /dev/ipldevice bosboot -a -d /dev/ipldevice rm -f /etc/firstboot sync sync sync exit ð 4. Backup the 3 files to a diskette: # find . -print | backup -ivqf/dev/rfdð 5. Create a mksysb tape from the system that you want to clone. 6. Boot the target machine (the one you want to install) with the AIX CD-ROM product media, and insert the diskette in the drive. Make sure the tape drive is turned on. 7.
lscfg -r ioplanFð Part Number.................ð4ðH5411 EC Level....................ððD28864 Serial Number...............843ððð46 FRU Number..................ð12H22ð9 Displayable Message.........I/O Card Device Specific.(PL)........ðð-ð1 Processor Component ID......c4 Device Specific.(Zð)........PCI=ð7,EIS=ð7,CPU=ð1,CL=ðð Processor Identification.... Device Specific.(Z1)........ procFð Part Number.................ð73Hð793 EC Level....................3ZD74339 Serial Number...............861ððð39 FRU Number...
ioplanF0 This stanza provides information about the I/O planar. The first four numbers identify the part number and level of the I/O planar card. The Device-Specific information, Zð, is the most interesting as this shows that there are: 7 PCI slots (PCI=ð7) 7 EISA slots (EIS=ð7) 1 CPU Slots (CPU=ð1) procF0 This stanza provides information about the CPU card. Again information is given about part numbers and so forth.
First, the firmware must have device support for a particular graphics adapter to be able to display the firmware power-on self test (POST) icons and, if selected, the SMS graphical/ASCII screen. The firmware will test the adapter but not the display. If the graphics adapter is found to be non-functional, the system will provide a beep sequence to indicate that there is a problem. The beep sequence is one long beep followed by one short beep after which an error is logged and the system continues.
5.6.2 Resolution The S15 can display resolutions from 640x480 to 1600x1280 with a variety of refresh rates.
à ð Select the Display Type Type or select values in entry fields. Press Enter AFTER making all desired changes. Graphics Adapter Select the Display Type F1=Help F5=Reset F2=Refresh F6=Command [Entry Fields] ggað IBM_P2ðð F3=Cancel F7=Edit + F4=List F8=Image á ñ Figure 30.
cannot handle will result in an unreadable screen and possible damage to your display. Note: AIX V4.1.4 will not allow you to alter the resolution of your display if you select either of the alternative VESA-compliant options. Trying to change the resolution through SMIT will result in an error stating that the Other_HiRes_VES attribute does not exist in the predefined device configuration database. To fix this problem, you must install Authorized Program Analysis Report (APAR) IX53366.
gga1 ð5 pci S15 S15 Graphics Adapter IBM Personal Computer Power Series S15 Graphics Adapter Default display = ggað 5.6.4.2 Changing the Default Display In the above example, the ggað device is the default graphics adapter. This can be changed to gga1 by using the chdisp command. By using this command, you can temporarily change the default display or change the default display for all subsequent reboots.
xterm -display hostname:ð.1 2. Move the mouse off the right of the default screen. The mouse should appear on the other screen. You can now gain focus on the Xwindow. From here, you use the new window or open more windows. Accessing a second display by using standard Xwindows and Motif is also very easy. You can start Xwindows and access the second display using the same method described above. In addition, you can "stack" the screens in any order you like.
Chapter 6. Adapter and Device Configuration on PCI-Based RS/6000 Servers PCI-based RS/6000 systems include support for new buses, such as the Peripheral Component Interconnect (PCI) and Industry Standard Architecture (ISA) as well as new devices which are different than the ones that are supported on the microchannel-based RS/6000 systems.
The ISA/EISA bus has no standard method of identifying adapters or their configuration requirements. Non-native ISA devices will have to be configured manually and may even need to change some of the device's predefined or customized attribute values, especially when configuring two or more ISA adapters of the same type. Plug and Play ISA adapters provide dynamic detection and modification of settings on the card.
6.1.2 Device Location Codes Location Codes are defined slightly differently depending on the type of device they are used for, non-SCSI or SCSI. For planars, cards and non-SCSI devices, the Location Code is defined as: AB-CD-EF-GH For SCSI devices, the Location Code is defined as: AB-CD-EF-G,H While AB-CD-EF have the same meaning for both non-SCSI and SCSI devices, the last two letters identify different codes.
à sysð sysplanarð busð memð procð L2cacheð Available Available Available Available Available Available ðð-ðð ðð-ðð ðð-ðð ðð-ðð ðð-ðð ðð-ðð fdað fdð ppað sað ttyð sa1 siokað kbdð siomað mouseð tokð ampxð Available Available Available Available Available Available Available Available Available Available Available Available ð1-Að ð1-Að-ðð-ðð ð1-Bð ð1-Cð ð1-Cð-ðð-ðð ð1-Dð ð1-Eð ð1-Eð-ðð-ðð ð1-Fð ð1-Fð-ðð-ðð ð1-ð1 ð1-ð2 bus2 bus1 scsið cdð rmtð hdiskð hdisk1 hdisk2 scsi1 rmt1 gga1 tokð entð ggað Availabl
drivers and diagnostic support (if available), and the system will automatically configure the PCI adapters. If you have a system installed and running, then you can use smit cfgmgr. This method will require you to put the AIX installation media in place (CD-ROM, tape, and so forth) before configuring the adapters. The media will be used only if the device drivers for your adapters are not currently installed.
device is installed. If not, use SMIT to configure the device, and provide an input device or directory where the installation software can be accessed. 6.3 ISA Adapter Configuration When configuring ISA adapters, you will have to configure some adapter hardware parameters. The values you assign to the parameters are used by AIX to communicate with the adapter; thus, it is important they are selected carefully in order to perform a conflict-free configuration. AIX manages five resources for ISA adapters.
Having the previously installed adapter parameters documented allows better planning for the installation of additional ISA adapters and enables you to start with a set of conflict-free definitions. To obtain a list of ISA adapters already configured in your system, enter the following command: lsdev -Cc adapter -s isa à ampxð Available ð1-ð1 X.25 CoProcessor/1 Adapter sa2 Available ð1-ð2 IBM 8-Port Async, EIA-232 (ISA) á ð ñ Figure 32.
6.3.2 Selecting ISA Adapter Hardware Parameters Your system will work without problems only if there are no conflicts among the parameters for the different ISA adapters in the system. When selecting the parameters for the new ISA adapter, you can use the information collected at the previous step and the information provided by the Installation Guide booklet for the adapter. Try to use the predefined default parameters whenever possible. The number of parameters to set depends on the type of adapter.
à ð ISA Adapters Move cursor to desired item and press Enter. Install ISA Adapter Software Add an ISA Adapter Change / Show Characteristics of an ISA Adapter Remove an ISA Adapter List all Defined ISA Adapters List all Supported ISA Adapters Configure a Defined ISA Adapter F1=Help F9=Shell F2=Refresh F1ð=Exit F3=Cancel Enter=Do F8=Image á ñ Figure 35. SMIT ISA Menu Once there, select Add an ISA Adapter. The follow-up screen is not the same for all adapters.
Matching Parameters It is very important to understand that some parameters, such as the IRQ and I/O Port, are set at both the hardware and AIX level, and the settings must be identical. Refer to the sections describing each ISA adapter configuration to know how to set DIP switches on each particular adapter. Shut down and power-off the system, and then physically install the adapter in an ISA free slot. 6.3.
Table 17. 8-Port Asynchronous ISA Adapter DIP Switches Hex Addr Address Switch 1 2 3 4 104 Off Off On On 114 Off On Off On 124 Off On On On 204 On Off Off On 224 On Off On On 304 On On Off On 324 On On On On Note: The on and off DIP-switch selections are set by switching them down and up, respectively. The mapping is: off = up on = down 6.4.
4. Install the 8-Port Asynchronous ISA Adapter device driver and diagnostic by choosing: smit isa Install ISA Adapter Software to install the fileset device.isa.cxia. 5. After installing the software, you might enter: smit isa Add an ISA Adapter 6. Select pcxr isa IBM 8-Port Async, EIA-232 (ISA) from the SMIT pop-up menu. 7. Select bus1 Available ISA Bus from the following SMIT pop-up menu. 8. From the menu described in Figure 36, select the correct Bus I/O Address, and press Enter.
It does not matter. You should use this procedure just to make sure that the selected adapter parameter is correct. 9. If the Bus I/O Address is in conflict with the parameter setting for another ISA adapter already installed, the following message will be displayed: sa3 Defined lsresource : The attribute(s) for some device(s) in the system could not be resolved. To resolve conflicts, attribute(s) need to be modified. A suggested value for each attribute is provided.
128-port asynchronous card Two terminators Asynchronous wrap plug The device driver for the 128-Port Asynchronous ISA Adapter is included in devices.isa.cxia128 fileset. Note Refer to the 128-Port Asynchronous ISA Adapter Installation Guide shipped with the adapter for detailed information on this adapter. 6.5.1 DIP-Switch Setting The only parameter you have to set to install the adapter into the system is the Bus I/O Address.
2.
à Add an IBM 128-Port Async, EIA-232 (ISA) Adapter ð Type or select values in entry fields. Press Enter AFTER making all desired changes.
ð514-ð4ð Error initializing a device into the kernel. cxiað deleted Change the parameter value as suggested by the lsresource command, and press Enter. 10. Once no parameters conflicts are reported, you can set the DIP switches on the adapter card, as described in Table 18 on page 112, to reflect the selected Bus I/O Address correct value. 11. Shut down and power-off the system. 12. Physically install the adapter on an ISA slot. 13. Power on and reboot the system. 14.
The following table shows the supported interfaces for each port. Table 19. Physical Interfaces on 4-Port Multiprotocol Interface Cable Port Number Supported Interfaces #0 EIA-232 EIA-422 V.35 X.21 #1 EIA-232 - V.35 - #2 EIA-232 EIA-422 - - #3 EIA-232 - - - The maximum cable lengths that are supported for the various communications protocols are described in the following table. Table 20. Maximum Cable Length Protocol Length (meters) Length (feet) RS-232 15.2 50 V.35 15.
Table 22. 4-Port Multiprotocol Adapter: DIP-Switch Suggested Settings Dip Switch # Position Comment First Second Third Adapter Adapter Adapter 1 on off on IRQ Level 2 off off on 3 on on off 4 off off off Memory Size .a/ 5 off off off I/O Port Address 6 on off on 7 on on off 8 on on on 9 on on on Edge Connector .b/ 10 off off off Bus-Width .
Default Parameters If this is the first adapter of this type on the system, you may select the default values which are: Interrupt Level = 7 Bus I/O Address = 0x6a0 Bus Memory = 0X0e2000 and go directly to step number 9. 2.
7. Select a bus memory address that is not currently in use. The valid bus memory values for use with the 4-Port Multi-Protocol ISA Adapter start at 0x0e0000 and increment by 0x002000. For example 0x0e2000, 0x0e4000, 0x0e6000, etc. The previous example shows ampxð is using the first bus memory range of 0X0e000 and apmð is using the second range of 0x0e2000. 8.
apm1 Defined lsresource : The attribute(s) for some device(s) in the system could not be resolved. To resolve conflicts, attribute(s) need to be modified. A suggested value for each attribute is provided. DEVICE ATTRIBUTE CURRENT SUGGESTED DESCRIPTION --------------- --------------- --------- --------- ----------apm1 bus_intr_lvl 7 9 Interrupt Level apm1 bus_io_addr ðx6að ðxeað Connection Address apm1 deleted Change the parameter value as suggested by the lsresource command, and press Enter. 13.
Note Refer to the X.25 Interface Co-Processor ISA Adapter Installation Guide shipped with the adapter for detailed information on this adapter. 6.7.1 DIP-Switch Setting The X.25 Interface Co-Processor ISA Adapter has a 10-position DIP switch which is used to set the following parameters: Table 23. DIP Switches on the X.
Notes: Refer to the document Adapters, Devices, and Cable Information for Multi Bus Systems, SA38-0516-00, for detailed information on DIP-switch positions for setting other parameter values. The on and off DIP-switch selections are set by switching them down and up, respectively. The mapping is: off = up on = down .a/ This switch is factory set to indicate the size of RAM installed on the adapter. Verify that the position of this switch is on to reflect a RAM size of 512 KB. .
N N ampxð scsið bus_intr_lvl bus_intr_lvl 11 (Að) 13 (Að) 3. Select an Interrupt Level that is not currently in use. 4.
12. From the menu described in Figure 39 on page 124, select the correct Interrupt Level, Bus I/O Address and Bus Memory values, and press Enter. à ð Add a X.25 Coprocessor/1 Adapter Type or select values in entry fields. Press Enter AFTER making all desired changes. Description Parent Device ISA Interrupt Level Bus IO Address Bus Memory Address Define device only, do not configure F1=Help F5=Reset F9=Shell F2=Refresh F6=Command F1ð=Exit [Fields] X.
15. Physically install the adapter on an ISA slot. 16. Power on and reboot the system. 17. Configure the adapter using the fastpath: smit isa Configure a Defined ISA Adapter 18. Verify the results with the following command: lsdev -Cc adapter -s isa If the configuration was successful, the adapter will be available, and the system will display information similar to the following: ampx1 Available ð1-ð4 X.25 Coprocessor/1 Adapter 19.
recommend you configure the adapter at the AIX level on the PCI-based server system in the defined state before setting the right parameters, as in step number 5. 6.8.1 Configuring an ISA Ethernet Adapter Before the hardware parameters for the new ISA adapter can be selected and tested using the 40P or 43P firmware, you will have to tell AIX the values of these parameters.
This command generates a list of adapters using bus I/O that looks similar to the following: O O O O O O O O O ð O O fdað fdað ppað sað sa1 siokað siomað ampxð sa2 entð scsið scsi1 bus_io_addr bus_io_addr2 bus_io_addr bus_io_addr bus_io_addr bus_io_addr bus_io_addr bus_io_addr bus_io_addr bus_io_addr bus_io_addr bus_io_addr 1 1 ðxððððð3fð - ðxððððð3f5 ðxððððð3f7 ðxððððð3bc - ðxððððð3be ðxððððð3f8 - ðxððððð3ff ðxððððð2f8 - ðxððððð2ff ðxðððððð6ð ðxðððððð6ð ðxððððð2að - ðxððððð2a6 ðxððððð1ð4 - ðxððððð1ð7 ð
à ð Add a Ethernet ISA Adapter Type or select values in entry fields. Press Enter AFTER making all desired changes.
IO is the I/O address MEM is the shared memory address TYPE is the type of cable connection you will be using 13. Once no parameters conflicts are reported, you can set the parameters on the adapter card as described in 6.8.2, “Setting ISA Ethernet Adapter Parameters at Firmware Level,” to reflect the selected parameters' correct values. 14. Shut down and power-off the system. 15. Physically install the adapter on an ISA slot. 16. Power-on and reboot the system. 17.
9. Select Adapter Parameters, and press Enter. 10. Select IBM LAN Adapter for Ethernet, and press Enter. Note The Ethernet adapter entry will be displayed only if the Interrupt Level set on the adapter does not conflict with the any Interrupt Level used by the computer. For example, if your Ethernet adapter is set to interrupt 5 and you install it on a 43P, the entry for the adapter will not be displayed, and you will not be able to change the parameters.
Shared Bus Memory Address = 0xc0000, 0xc4000, 0xc8000, and so on Length in shared bus memory = 8 KB, 16 KB, 32 KB, 64 KB Address of bus memory for BIOS = 0xc8000, 0xca000, 0xcc000, and so on Ring Speed = 16 MB, 4 MB 1.
5. Select a Bus I/O Address that is not currently in use. 6. If any token-ring adapter is installed, check for available Shared Bus Memory values by entering the following command: lsresource -l busð -a | grep shared_mem_addr This command generates a list of ISA adapters using a Bus Memory Address that looks similar to the following: B tokð shared_mem_addr ðxðððdðððð - ðxðððd7fff 7. Select a Shared Memory Address that is not currently in use.
à ð Add a Token Ring ISA Adapter Type or select values in entry fields. Press Enter AFTER making all desired changes.
IRQ is the interrupt level IO is the I/O address MEM is the shared memory address LEN is the length of shared memory BIOS is the ROM memory address SPEED is speed of the network ring 15. Once no parameters conflicts are reported, you can set the parameters on the adapter card, as described in 6.8.4, “Setting Auto 16/4 Token-Ring ISA Adapter Parameters at Firmware Level,” to reflect the selected parameters' correct values. 16. Shut down and power-off the system. 17.
The second path Configure Token-Ring adapter provides an entry field that will accept parameters for each option that is being modified. Chapter 6.
136 Introduction to PCI-Based RS/6000 Servers
Chapter 7. SCSI Cabling It is very likely that you will face problems regarding configuration and installation of SCSI adapters and devices. SCSI cabling can be one of the most confusing topics to face.
Devices which have two SCSI connectors have internal cabling which must be included when calculating the total cable length. When attaching these devices to a SCSI chain, connect one cable to one connector and the other cable to the other connector. 7.1.2 SCSI Terminators There must be exactly two terminators on the SCSI bus, and they must be located at each end of the bus. For SCSI adapters with external devices only, make sure the appropriate SCSI terminator is connected to the last device on the bus.
Mixed-width internal attachment is supported concurrently with single width external attachment as long as maximum cable length restrictions are not exceeded. 7.2 Cabling the SCSI-2 Fast/Wide Single-Ended PCI Adapter SCSI Fast/Wide devices support data rates of up to 10 MB/sec for 8-bit or 20 MB/sec for 16-bit transfers. If a configuration includes SCSI-2 Fast/Wide devices, the maximum cable length supported is three meters (approximately 10 feet).
Table 26. SCSI-2 Fast/Wide Single-Ended Adapter-to-First Device Cables M/T F/C Part Number Length (meters) Cable Description Host System 2111 06H6037 1.0 Adapter-to-first device (where first device has two connectors), 8-bit narrow bus Host System 2113 52G0174 1.5 Adapter-to-first device (where first device has one connector),8-bit narrow bus Host System 2115 06H6036 1.0 Adapter-to-first device (where first device has two connectors), 16-bits wide bus Host System 2117 52G0173 0.
7.2.2 Device-to-Device Cables This table describes the device-to-device cables for single-ended applications. Table 27. Device-to-Device Cables for Single-Ended Installations M/T F/C Part Number Length Cable Description (meters) SE Bridge Box 2840 33F4607 0.7 Device-to-Device (where second device has two connectors), 8-bit narrow bus SE Bridge Box 3130 31F4222 0.66 Device-to-Device (where second device has one connector), 8-bit narrow bus SE Bridge Box 2860/9139 52G9921 0.
7.3 Cabling the SCSI-2 Fast/Wide Differential PCI Adapter The following tables describe the cables, terminator features, part numbers, and lengths for the SCSI-2 F/W Differential PCI Adapter (FC 2409). The maximum supported cable length for configurations is 25 meters (approximately 80 feet). 7.3.1 Adapter-to-First Device Cables This table describes the SCSI-2 Fast/Wide Differential PCI Adapter cables for connection to the first device. Table 29.
7.3.2 Device-to-Device Cables This table describes the SCSI-2 Fast/Wide Differential PCI Adapter cables for connections from device to device. Table 30. Device-to-Device Cables for Differential Installations M/T F/C Part Number Length Cable Description (meters) DE Bridge Box 2848/9134 74G8511 0.6 Device-to-Device (where second device has two connectors), 8-bit narrow bus DE Bridge Box 2860/9139 52G9921 0.
7.3.3 SCSI-2 F/W Differential PCI Adapter Terminators This table describes the SCSI-2 Fast/Wide Differential PCI Adapter terminators. Table 31. Terminators for Differential Installations M/T F/C Part Number Connector Terminator Description DE External devices part of cable F/C 87G1356 50-pin low density 8-bit external bus terminator DE External devices part of cable F/C 61G8324 68-pin high density 16-bit external bus terminator 7.3.
Figure 42. Example of HACMP Cabling Table 32. HACMP/6000 Cabling Features and Part Numbers Item number F/C 1 2409 Part Number Cable Length (meters) Description Adapter 2 Dual Port Device 3 2114 52G0173 0.94 Y-cable 4 2884/9160 2846/9132 2885/9161 2870/9146 2869/9145 52G4291 52G4233 88G5749 88G5747 88G5748 0.6 2.5 4.5 12.0 14.0 Device-to-Device (wide 16-bit) 5 61G8324 Terminator Chapter 7.
146 Introduction to PCI-Based RS/6000 Servers
Chapter 8. Diagnostics Support One of the most important features provided by the PCI-based RS/6000 servers is support of the AIX diagnostics programs. Servers, by their nature, should provide enhanced Reliability, Availability and Serviceability (RAS) features. Access to AIX diagnostics, stand-alone and online, helps provide these features (which are available on the microchannel-based RS/6000 systems). Both the 40P and 43P PCI-based RS/6000 workstations do not provide support for AIX diagnostics.
When you run Stand-alone Diagnostics, you will have to select the console display. The diagnostics program displays instructions on graphics displays and on terminals attached to the S1 serial port. Identifying the Terminal Type to Diagnostics When you run diagnostics, the diagnostic program must know what type of terminal you are using.
in your system except for the SCSI adapter used to boot the diagnostics CD-ROM. If the diagnostics are run in Concurrent mode using Stand-alone Diagnostics (the CD-ROM is mounted while AIX is running), then you have access to the AIX Error Log and the AIX Configuration Data, but you are limited to which devices you can test.
8.2.1.1 Configuring ISA Adapters from Diagnostics As mentioned above, when booting into diagnostics from CD-ROM, you can only test the ISA adapters in your system after they have been configured. The configuration is only for diagnostics purposes and will not affect the adapters configuration in AIX. The following procedure explains how to configure an adapter using diagnostics. For the purpose of the explanation, we have used an 8-port adapter as an example. 1.
à ð ISA ADAPTER ATTRIBUTE SELECTION Press 'List' to select additional values. If a range is indicated below the description, then enter a value within the range. Press 'Commit' when finished. Bus I/O Address Bus Memory Address ISA Interrupt Level F1=Help F5=Reset F2=Refresh F7=Commit [ðx1ð4] [ðxdðððð] [ ] F3=Cancel F1ð=Exit F4=List á ñ Figure 44.
If you wish to test ISA adapters which have not yet been configured, use SMIT to configure the adapter before running diagnostics. 8.3 Online Diagnostics The Online Diagnostics are an AIX Version 4.1 installable package. They are packaged under bos.diag. There is a separate, installable option for each device or adapter supported by diagnostics. If you install your system from an AIX Version 4.1.
Memory Processor There are three levels of testing in Concurrent mode: The Share-test level tests a resource while it is being shared by programs running in normal operation. This test is mostly limited to normal commands that test for the presence of a device or adapter. The Sub-test level tests a portion of a resource while the remaining part of the resource is being used in normal operation.
8.3.3 Maintenance Mode Diagnostics can run from Single-User mode (Maintenance mode - although this is different from booting into Maintenance mode from a CD-ROM or a tape). You can shut your system down into a Single-User mode which will allow testing many of your system resources which would normally be in use while AIX is running. All the system resources, except the SCSI adapters and disks used for paging, memory and processors, can be tested. Error Log Analysis is available in this mode.
8.4.1.2 Booting Diagnostics over the Network To boot the bos.diag package from a NIM Master, you have to perform the following steps: 1. Allocate the spot resource object to your NIM Client machine (see 9.2.7, “Allocating Resources for the Stand-Alone Installation” on page 172) 2. Enter the following command: smitty nim_mac_op 3. When the Machine Object Name screen appears, select the name that represents your Client machine. 4. When the Operation to Perform screen appears, select the diag operation. 5.
156 Introduction to PCI-Based RS/6000 Servers
Chapter 9. Network Installation Management (NIM) Support The PCI-based RS/6000 servers are powerful servers which can be used to install other machines in the network. In this chapter, we explain the steps you require to configure your PCI-based RS/6000 server as a Network Installation Management (NIM) Master. We will also explain the steps involved in configuring the PCI-based RS/6000 server as a NIM Client and how it can be installed over the network.
Table 33 on page 158 shows the resources required to classify a machine as having a stand-alone, diskless or dataless configuration in the NIM environment. In the table, the resources that are accessed locally are indicated by L, and the resources that are accessed remotely are indicated by R. Table 33.
9.1.2.2 Network Objects The network objects and their attributes reflect the physical characteristics of the network environment. This information does not affect the running of a physical network but is used internally by NIM for configuration information. All the machines and networks environment used in the NIM installation must be defined in the NIM database. We strongly suggest that you make a drawing of your networking environment. This will avoid confusion, especially regarding the gateways. 9.1.2.
Figure 45. Sample Network Topology The example above requires the definition of the following NIM objects: NIM Master Fileset This object defines the network where the NIM Master is connected to (network1). The Master machine object is created automatically when the Master fileset object is created. Network3 This is a network object. Standalone1 This is a machine object (NIM Client). Additionally, two Network Install Route attributes, Gateway1 and Gateway2, must be defined.
environment (see 9.2.4, “ Network Objects Definition” on page 163 for more information about NIM network objects definition). 9.2 Configuring a PCI-Based RS/6000 Server as NIM Master Technically, the PCI-based RS/6000 servers can be used as Masters in the NIM environment. However, some specifics related to the rspc platform type should be taken into consideration. We found that when the AIX Version 4.1.4 SMIT NIM support was used to activate the NIM Master (see 9.2.
9.2.3 NIM Master Activation Prior to NIM Master activation, do not forget to mount the previously created filesystems. To activate the Master, you will need the following information: Network object name Specifies the identifier you wish to name the objects that NIM creates to represent the network, where the Master's primary interface connects. You can use any name you like, and you should choose a name which is meaningful to you.
The nimesis daemon has been started on the Master. This daemon is used for TCP/IP socket communication between the Master and Client machines in the NIM environment. To display information about the objects that are so far defined, enter: lsnim For more detailed information about one specific object, enter: lsnim -l object_name 9.2.4 Network Objects Definition Figure 46 on page 164 shows the network topology we used in our lab. As NIM Master, we used a RS/6000 Model F30 and as NIM Client, a 40P.
Figure 46. Network Topology Used in Our Lab In the previous step, when you activated the NIM Master, a network object was defined representing the network to which the NIM Master's primary interface is connected. When this network is the only physical network you have, or when the Master and the Clients are attached to the same network, you do not have to define any additional network objects.
In our network topology example shown in Figure 46, the NIM Master is connected to the network network1, and the NIM Client is connected to the network Network3. Both networks and their gateways, gw1_tok and gw1_eth, must be defined to the NIM environment. In the previous step, when the NIM Master was activated, network1 was defined. Thus, now we only need to define network3 and the gateways. Note: Neither network2 nor its gateways, gw2_tok and gw3_tok, need to be defined.
Look for any missing entry. In our example, the definition of the route to Network3 is missing. We will add the definition using the command: smitty nim_mkroute Select the Originating and Destination Network Object Names; in our example, network1 and network3, respectively. à ð Define a Network Install Route Type or select values in entry fields. Press Enter AFTER making all desired changes.
platform type of the IPL ROM emulation that you wish to create. To create IPL ROM emulation media, perform the following: 1. Insert a formatted diskette into the NIM Master. 2. Enter: bosboot -r /usr/lpp/bos.sysmgt/nim/methods/IPLROM.emulation \ -d /dev/fdð -M both -T rs6k It is advisable to test the physical connection between the NIM Client and NIM Master.
Select the standalone machine object type. In our example, the following screen appears: à ð Primary Network Move cursor to desired item and press Enter. Network1 Network3 F1=Help F8=Image /=Find networks networks tok ent F2=Refresh F1ð=Exit n=Find Next F3=Cancel Enter=Do á ñ The network to be selected here is the network to which the NIM Client's primary interface connects; in our case, we must select Network3. The following SMIT screen will be displayed.
9.2.6 Resource Objects Definition The following resources are required for a stand-alone installation: lpp_source spot 9.2.6.1 Defining the lpp_source Resource Object When defining the lpp_source object, we will use the /inst.images created previously (see 9.2.2, “Filesystem Creation” on page 161). The /inst.images directory will contain the software packages which may be copied from tape or CD-ROM. This filesystem can also be made available from another server, using NFS.
4. Enter the resource-specific information as required. à ð Define a Resource Object Type or select values in entry fields. Press Enter AFTER making all desired changes. \ \ \ \ [Entry Fields] [imagesNIM] lpp_source [master] + [/inst.images] [rmtð] + [bos bos.rte.up bos.
à ð Define a Resource Object Type or select values in entry fields. Press Enter AFTER making all desired changes.
In order to have a SPOT with all the software we want to have on the Client (including the CDE package), we need to install the filesets listed above. This can be done with the cust operation on the SPOT resource. This operation can be performed using the following SMIT fastpath: smitty nim_res_op Then select the SPOT resource object (spotNIM in our case) and the cust operation. Enter the fileset names listed above. à ð Customize a SPOT Type or select values in entry fields.
9.2.8 Initiating the BOS Installation The network installation for a PCI-based RS/6000 NIM Client cannot be initiated from the NIM Master. This means, to perform network installation, manual intervention is required on the Client system that will be installed. Perform the following steps on the NIM Master to initiate the NIM operation: 1. Enter the following fastpath command: smit nim_mac_op 2. Select the object name of the Client machine (standalone1). 3. Select bos_inst from the list of operations. 4.
NIM Warning! warning : ðð42-134 m_bos_inst : unable to initiate network boot on "MachineObjectName" The warning means NIM was unable to force the target to load the network boot image. Loading the network boot image must be initiated from the NIM client. 9.3 Using a PCI-Based RS/6000 Server as a NIM Client In our example, we tested the PCI-based RS/6000 server as a NIM Master and as a NIM Client.
Figure 51. Initial Boot Screen 3. Select the Utilities option from the System Management Services menu. Use the Down Arrow key to highlight the option, and then press the Enter key. Figure 52. System Management Services Menu 4. Select the Remote Initial Program Load Setup option from the System Management Services Utilities menu. Chapter 9.
Figure 53. System Management Services Utilities Menu 5. Select the Adapter Parameters option from the Network Parameters submenu. Select the corresponding LAN adapter (IBM LAN Adapter for Ethernet or IBM Token-Ring Adapter). Select the View Parameters option and the Hardware Address option. Check to see if the hardware address is correct. Use the Esc key to return to the Network Parameters submenu. Figure 54. Adapter Parameters Submenu 6.
If you don't use a gateway between both systems, the Gateway IP Address should be the same as the Server IP Address. 9. If the ping operation was successful, press the Esc key to return to the Network Parameters submenu. 10. Press the Esc key again to return to the System Management Services menu. Select the Select Boot Devices option from the menu. 11. Select the Boot Other Device option, followed by the corresponding Network Adapter option.
à ð Perform a Network Install Type or select values in entry fields. Press Enter AFTER making all desired changes.
Chapter 10. Troubleshooting In an ideal world, computers would not have problems, and if they did, the computers would correct them without user intervention. In the real world, however, things are different. In this chapter, we aim to provide you with ways of overcoming some problems that you may run into when using the PCI-based RS/6000 server. On the whole, the PCI-based RS/6000 servers will be susceptible to the same problems that the microchannel-based RS/6000 systems can have.
the system does not restart after a few minutes, the system planar may have to be replaced. There are no other means of recovery other than the recovery diskette. 10.1.1.2 Firmware Language Problems The E20 and F30's firmware have the ability to change the language in which the System Management Services menus and options (ASCII interface) are displayed.
2. Select the option to access the root volume group, and start a shell before the filesystems are mounted. 3. Check the root volume group filesystems: fsck fsck fsck fsck fsck -y -y -y -y -y /dev/hd1 /dev/hd2 /dev/hd3 /dev/hd4 /dev/hd9var 4. Format the Journaled File System (JFS) log: logform /dev/hd8 Answer YES when asked if you want to destroy the log. 5. Type exit to mount the root filesystems. 6. Check the inittab file for any entries which may be causing problems. 7.
4. Select AIX Shell Prompt. 5. Enter the root password. 6. Perform maintenance work. Remember to set the $TERM variable so that you can use full screen editors, for example if you are using an ibm3151 ASCII terminal: TERM=ibm3151 export TERM 7. Shut down and restart the system. If problems persist, then you may require media to boot into Maintenance mode, or you may have to restore the system. 10.
10.4 Accessing Diagnostics With NIM There is a problem accessing diagnostics on a NIM Master from the PCI-Based RS/6000 Systems. If you are using a graphics card with a display and a directly attached keyboard is connected to the system, when you access diagnostics from the NIM Master, the keyboard will not work since it does not get defined. The only way around this problem is to remove the graphics adapter, and use an ASCII terminal with keyboard. 10.
It is recommended to set these passwords to disable unauthorized access to your machine. If you forget either of the passwords, the only way to remove the passwords is by removing the battery from the RS/6000 for at least 30 seconds. Removing the battery, however, will cause all the user-configured data, such as the Boot Device Order List, to be lost. All of the user-configured data will be reset to the default values. 10.6.2.
10.6.4 Configuration Information Information about the ISA and PCI adapters can be obtained by running the lscfg command (see 5.5, “Configuration Information” on page 90). To determine how much memory you have in your machine, run the following command: lsattr -El memð This will show the size of memory in your machine and how much usable memory there is. You can also see the size of the L2 cache installed in your system by using the lsattr command: lsattr -El L2cacheð 10.6.
Figure 55. Operator Panel An explanation of the LEDs on the front panel of the F30 is given in Table 35. Table 35. LED Functions LED Status Definition Power Good On System power is On Off System power is Off On System power is On Off Power not connected to system Blinks slowly Power is connected to system Blinks rapidly AIX memory dump has been initiated by start/stop method On System electronics are not reporting errors Off System electronic failures are detected On Disk drive active.
then it may be worth considering the purchase of a Uninterruptible Power Supply (UPS). Chapter 10.
188 Introduction to PCI-Based RS/6000 Servers
Appendix A. Firmware Checkpoint Three-Digit Codes The three digit codes listed in Table 36 will appear to the left of the top row on the Liquid Crystal Display (LCD) which is located on the front panel of the system. The intended use of these codes is to assure the observer that the Firmware is operational after power on, and before information appears on the console display. Refer to 4.4, “Understanding the Firmware” on page 64 for more information on the Firmware boot process. Table 36 (Page 1 of 5).
Table 36 (Page 2 of 5).
Table 36 (Page 3 of 5). Firmware Checkpoint Three-Digit Codes Code Description F55 Bad System Board (Unsupported EPOW) F56 Voltage problem.
Table 36 (Page 4 of 5).
Table 36 (Page 5 of 5). Firmware Checkpoint Three-Digit Codes Code Description FFA Error during flash update FFC Operating System boot - No errors reported by IPL ROS FFD Operating System boot - Non-critical errors reported by IPL ROS FFE No boot - Critical error(s) reported by IPL ROS or "F1" key pressed Appendix A.
194 Introduction to PCI-Based RS/6000 Servers
List of Abbreviations ABI Application Binary Interface OSA Operating System Area APA all points addressable PCI BTAS Boot-Time Abstraction Software Peripheral Component Interconnect PCI-SIG PCI Special Interest Group PIO Parallel Input/Output POST Power-On Self Test POP Power-On Password PNP Plug and Play PROM Programmable Read-Only Memory PReP PowerPC Reference Platform PROFS Professional Office System RAN Remote Asynchronous Nodes RAS Reliability, Availability, Serviceability
196 Introduction to PCI-Based RS/6000 Servers
Index A abbreviations 195 acronyms 195 adapter configuration on PCI-based RS/6000 servers 99 defining ISA adapters 106 device configuration database 100 device driver installation 106 device location codes 101 device types 99 ISA 104 making ISA adapters available 108 non-graphic PCI 103 PCI 102 recording settings of already configured ISA adapters 104 SCSI devices 103 selecting ISA hardware parameters 106 setting ISA DIP switches 107 AIX V4.1.
device configuration on PCI-based RS/6000 servers 99 database 100 defining ISA adapters 106 device driver installation 106 device types 99 ISA adapter 104 ISA adapter DIP switch setting 107 ISA adapters, recording settings of already configured 104 ISA adapters, selecting hardware parameters 106 location codes 101 making ISA adapters available 108 non-graphic PCI 103 PCI adapter 102 SCSI devices 103 diagnostic support 147 accessing with NIM 183 booting over the network 155 booting stand-alone from CD-ROM 14
Model E20 (continued) PCI SCSI-2 adapters 25 performance positioning 38 standard features 21 supported optional features 23 Model F30 31 communication adapters 36 external subsystems 37 graphics adapter 35 internal CD-ROM drives 35 internal disk drives 34 internal tape drives 35 limitations 38 PCI SCSI-2 adapters 36 performance positioning 38 standard features 32 Model F30 hot-swap subsystem 41 accessing banks 44 adding new drive to live system 47 backplanes 42 bays and banks 43 components 41 disk carriers
PowerPC Platform certification 8 description of 6 goals of 7 history 6 PowerPC Reference Platform (PReP) Specification description of 4 new compatibility model 3 old compatibility model 2 what it covers 5 processor subsystem 15 S SCSI cabling 137 general considerations 137 bus length 137 bus width 138 device addresses 138 terminators 138 SCSI-2 fast/wide differential PCI adapter cabling adapter-to-first device 142 device-to-device 143 high-availability multi-initiator cabling 144 terminators 144 SCSI-2 fas
ITSO Technical Bulletin Evaluation RED000 International Technical Support Organization A Technical Introduction to PCI-Based RS/6000 Servers April 1996 Publication No. SG24-4690-00 Your feedback is very important to help us maintain the quality of ITSO Bulletins. Please fill out this questionnaire and return it using one of the following methods: Mail it to the address on the back (postage paid in U.S.
ITSO Technical Bulletin Evaluation SG24-4690-00 Fold and Tape RED000 Please do not staple IBM Cut or Fold Along Line Fold and Tape NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO.
IBM Printed in U.S.A.
