Continuum Series 600/1200 - Customer Support · 4.2.1.1. syserr_log.date File ... 139 5.10.2 IOA Chassis Power Supply ... Continuum Series 600/1200 Maintenance Guide

Continuum Series600/1200

Maintenance Guide

HM-058021

Revision 1 - 9/19/96

StratusCustomer Service

Documentation

2/10/97 - Added information on 512-MB memory modules and

added Section 4.3 (Isolating Memory Faults)G751-G758 CPU-Memory boards;

Notice

The information contained in this document is subject to change without notice.

STRATUS COMPUTER, INC. MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Stratus Computer, Inc., shall not be liable for errors contained herein or incidental or consequential damages in connection with the furnishing, performance, or use of this material.

FTX, Stratus, and the Stratus logo are registered trademarks, and Continuous Processing and Continuum are trademarks of Stratus Computer, Incorporated.

Manual Name: Continuum Series 600/1200 Maintenance Guide

Part Number: HM-058021

First Printing: March 1995

Last Updated: February 1997

Stratus Computer, IncorporatedCustomer Service Documentation Department55 Fairbanks BoulevardMarlboro, Ma 01752-1298

Warning

The equipment documented in this manual generates and uses radio frequency energy, which if not installed and used in strict accordance with the instructions in this manual, may cause harmful interference to radio communications. The equipment has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment.

Operation of this equipment in a residential area is likely to cause interference, in which case the user at his own expense will be required to take whatever measures may be required to correct the interference.

THIS DOCUMENT CONTAINS STRATUS PROPRIETARY AND CONFIDENTIAL INFORMATION . IT IS PROVIDED TO YOU AND ITS USE IS LIMITED BY THE TERMS OF YOUR CONTRACTUAL ARRANGEMENT WITH STRATUS REGARDING MAINTENANCE AND DIAGNOSTIC TOOLS.

Copyright© 1997 by Stratus Computer, Inc. All rights reserved.

Preface

Continuum Series 600/1200 Maintenance Guide (HM-058)3

Preface

The Continuum Series 600/1200 Maintenance Guide (HM-058) contains information on how to service both 6-slot (Series 600) and 12-slot (Series 1200) systems in accordance with Stratus servicing policies.

This document is organized as follows:

Chapter 1 Introduction

Chapter 2 Operating Controls and Procedures

Chapter 3 Theory of Operation

Chapter 4 Fault Isolation

Chapter 5 Removal and Replacement

Index

Audience

This guide is intended for authorized service personnel who install and maintain Stratus systems, and who have completed Stratus field-service training courses.

Related Documentation

This guide contains VOS® and FTX® commands and operating information. For information on FTX operat-ing procedures, refer to the FTX Documentation Roadmap (R003X). For more Continuum system and VOS-related information, refer to the following documents:

• Series 600 Continuum Service Announcement (HA058)

• Series 1200 Continuum Service Announcement (HB058)

• Series 600/1200 Continuum Installation Guide (HI058)

• VOS Sys Admin: Admin and Customizing System (R281)

• VOS Sys Admin: Startup and Shutdown of a Module (R282)

• VOS Sys Admin: Registration and Security (R283)

• VOS Sys Admin: Disk and Tape Administration (R284)

• VOS Sys Admin: Backup and Restoring Data (R285)

• VOS Sys Admin: Administering the Spooler Facility (R286)

• VOS Sys Admin: Configuring a System (R287)

• FTX System Administration Guide: Installation (R454X)

• FTX System Administration Guide: General Services (R455X)

• FTX System Administration Guide: File Systems and Devices (R456X)

• FTX System Administration Guide: Networking and Port Services (R457X)


Table of Contents1. Introduction ................................................................................................................................................9

1.1. Overview ..........................................................................................................................................91.2. System Configurations ...................................................................................................................101.3. System Specifications ....................................................................................................................17

2. Operating Controls and Procedures .........................................................................................................192.1. Cabinet Indicators ..........................................................................................................................19

2.1.1 CEC Cabinet ....................................................................................................................192.1.2 Expansion Cabinet ...........................................................................................................19

2.2. Basic Operating Procedures ...........................................................................................................192.2.1 Starting the System ..........................................................................................................202.2.2 Shutting Down the System ...............................................................................................21

2.2.2.1. VOS ................................................................................................................212.2.2.2. FTX ................................................................................................................21

2.2.3 Rebooting the System ......................................................................................................222.2.3.1. VOS ................................................................................................................222.2.3.2. FTX ................................................................................................................22

2.3. System Verification .......................................................................................................................222.3.1 VOS ..................................................................................................................................232.3.2 FTX ..................................................................................................................................24

2.4. Maintenance Procedures ................................................................................................................262.4.1 VOS ..................................................................................................................................26

2.4.1.1. Preparing to Remove a Main Processor Board ..............................................262.4.1.2. Logically Removing a Disk Drive .................................................................272.4.1.3. Logically Adding a Disk Drive ......................................................................29

2.4.2 FTX ..................................................................................................................................302.4.2.1. Logically Removing a Main Processor Board ...............................................302.4.2.2. Logically Removing a Disk Drive .................................................................312.4.2.3. Logically Adding a Disk Drive ......................................................................32

3. Theory of Operation .................................................................................................................................363.1. System Bus ....................................................................................................................................363.2. CPU-Memory Board ......................................................................................................................383.3. SCSI-ENET Controller.................................................................................................................. 403.4. IO Processor ...................................................................................................................................433.5. Console Controller .........................................................................................................................443.6. Cabinet Data Collector ...................................................................................................................473.7. Power System .................................................................................................................................48

3.7.1 AC Systems ......................................................................................................................483.7.2 DC Systems (Central Office) ...........................................................................................53

3.8. Cooling System ..............................................................................................................................553.9. Peripherals ......................................................................................................................................56

3.9.1 D700 Disk/Tape Subsystem ............................................................................................563.9.2 D701/702 Disk Drives .....................................................................................................563.9.3 T701/702/703 Tape Drives ..............................................................................................573.9.4 D700 Configurations ........................................................................................................573.9.5 T403 Tape Drive ..............................................................................................................593.9.6 T204 Tape Drive ..............................................................................................................59

6 Continuum Series 600/1200 Maintenance Guide (HM-0580)

4. Fault Isolation ..........................................................................................................................................604.1. LEDs ..............................................................................................................................................60

4.1.1 Cabinet LEDs ..................................................................................................................604.1.2 CRU/FRU LEDs ..............................................................................................................61

4.1.2.1. Board LEDs ...................................................................................................624.1.2.2. Disk/Tape Power Component LEDs ..............................................................634.1.2.3. Disk/Tape Power Supply ...............................................................................644.1.2.4. Two Position LEDs ........................................................................................644.1.2.5. Battery Fault LED ..........................................................................................65

4.2. System Logs ..................................................................................................................................664.2.1 VOS Error Logs ...............................................................................................................66

4.2.1.1. syserr_log.date File ........................................................................................664.2.1.2. Hardware_log.date File ..................................................................................67

4.2.2 FTX ..................................................................................................................................684.2.3 Software Commands ........................................................................................................684.2.4 VOS (list_boards) ............................................................................................................694.2.5 FTX (Hwmaint ls) ...........................................................................................................69

4.3. Isolating Memory Faults ...............................................................................................................704.3.1 FTX ..................................................................................................................................70

4.4. Troubleshooting .............................................................................................................................714.4.1 Non-Critical Fault (System Operational) ........................................................................724.4.2 Critical Fault (System not Operational) ...........................................................................724.4.3 Troubleshooting Flowcharts ............................................................................................73

5. Removal and Replacement ................................................................................................................... 815.1. Overview .................................................................................................................................... 815.2. Replacing Components ............................................................................................................... 815.3. Accessing Replaceable Components .......................................................................................... 81

5.3.1 Front Door .................................................................................................................... 815.3.2 Front Door Frame ......................................................................................................... 825.3.3 Rear Access Panel ........................................................................................................ 835.3.4 Side Panels .................................................................................................................... 85

5.4. Power Subsystem ....................................................................................................................... 865.4.1 AC Systems................................................................................................................... 865.4.2 DC Systems .................................................................................................................. 88

5.5. System Verification .................................................................................................................... 895.5.1 System Verification (VOS) .......................................................................................... 895.5.2 System Verification (FTX) ........................................................................................... 89

5.6. Cabinets ...................................................................................................................................... 905.6.1 Cabinet Cooling ............................................................................................................ 90

5.6.1.1. Fan Assembly ............................................................................................. 905.6.1.2. Cabinet Data Collector (CDC) .................................................................... 915.6.1.3. Fan Backplane ............................................................................................. 925.6.1.4. Fan Chassis ................................................................................................. 94

5.6.2 DC Module Air Filter ................................................................................................... 955.6.3 Air Filter Sensor Switch (DC Cabinets) ....................................................................... 965.6.4 Cabinet Top Cap ........................................................................................................... 965.6.5 Alarm Display Unit (ADU) .......................................................................................... 975.6.6 DC Power Controller .................................................................................................... 985.6.7 DC Power Controller Backplane .................................................................................. 100


5.6.8 Power Cords .................................................................................................................. 1015.6.8.1. DC Power Cords .......................................................................................... 1015.6.8.2. AC Power Cords .......................................................................................... 102

5.6.9 Power Tap Circuit Breaker ........................................................................................... 1045.7. Central Electronics Cabinet (CEC) ............................................................................................. 105

5.7.1 Main Processor Boards ................................................................................................. 1065.7.1.1. Preparing to Remove a Main Processor Board ........................................... 1075.7.1.2. Main Processor Board Removal and Replacement ..................................... 107

5.7.2 Console Controller ........................................................................................................ 1085.7.3 Backplane Power Supply .............................................................................................. 1095.7.4 Scorecards ..................................................................................................................... 1095.7.5 6-Slot CEC .................................................................................................................... 110

5.7.5.1. 6-Slot CEC Clock Card ............................................................................... 1115.7.5.2. 6-Slot CEC Backplane ................................................................................ 1125.7.5.3. 6-Slot CEC IOA Chassis Power Backplane ................................................ 1135.7.5.4. 6-Slot CEC IOA Chassis Backplane ........................................................... 115

5.8. AC/DC Power System ................................................................................................................ 1175.8.1 Fiber Optic Cables ........................................................................................................ 1185.8.2 Power Supply Unit (PSU) ............................................................................................. 1195.8.3 Power Control Unit (PCU) ............................................................................................ 1205.8.4 Battery Fuse Unit (BFU) ............................................................................................... 1215.8.5 AC Power Controller (ACPC) ...................................................................................... 1225.8.6 Power Control Backplane ............................................................................................. 1235.8.7 Batteries ........................................................................................................................ 1245.8.8 Battery Drawer .............................................................................................................. 1255.8.9 Battery Drawer Rails ..................................................................................................... 1255.8.10 AC/DC Power System Chassis ..................................................................................... 1265.8.11 AC/DC Power System Front Air Filter ......................................................................... 1285.8.12 AC/DC Power System Rear Air Filter ......................................................................... 129

5.9. Mass Storage ............................................................................................................................... 1305.9.1 Disk Drive ..................................................................................................................... 1305.9.2 Tape Drives ................................................................................................................... 131

5.9.2.1. T204 Table-Top Tape Drive ....................................................................... 1315.9.2.2. T403 Table-Top Tape Drive ....................................................................... 1325.9.2.3. T70X Tape Drives ....................................................................................... 133

5.9.3 Disk/Tape Power Supply .............................................................................................. 1345.9.4 Disk/Tape Drive Terminator ......................................................................................... 1355.9.5 Disk/Tape Backplane .................................................................................................... 1365.9.6 Disk/Tape Chassis ......................................................................................................... 137

5.10. Input Output Adapter (IOA) Subsystem ..................................................................................... 1385.10.1 IOAs .............................................................................................................................. 1395.10.2 IOA Chassis Power Supply ........................................................................................... 1405.10.3 IOA Chassis Power Supply Backplane ......................................................................... 1415.10.4 IOA Chassis Backplane ................................................................................................ 1425.10.5 IOA Chassis .................................................................................................................. 144

5.11. Dual Input/Output Adapter (IOA) Subsystem ............................................................................ 1455.11.1 IOA Chassis Power Supply Backplane ......................................................................... 1455.11.2 IOA Chassis Backplane (Single Chassis Configuration) .............................................. 1465.11.3 IOA Chassis Backplane (Dual Chassis Configuration) ................................................ 148


5.11.4 IOA Chassis (Single Chassis Configuration) ............................................................... 1495.11.5 IOA Chassis (Dual Chassis Configuration) .................................................................. 151

Continuum Series 600/1200 Maintenance Guide (HM-058) 9

1. Introduction

This chapter describes the major components and specifications of Stratus Continuum Series systems. It contains the following sections.

• General information

• System configurations

• System specifications

1.1 Overview

The Continuum Series 600/1200 systems are the first Stratus RISC systems based on the Hewlett Packard PA-RISC HP7100 microprocessor and a new system bus architecture. The Series 600 is an entry-level to mid-range system designed around a 6-slot backplane in the Central Electronic Cabinet (CEC). The Series 1200 version is an expandable high-end system featuring a 12-slot CEC backplane.

The system bus is 64 bits wide for communications between CPU boards. Only 32 bits of the bus extends to the I/O slots. All the memory in the system is contained on the processor boards as globally accessible localized memory. This local memory design greatly reduces system bus traffic.

The CEC main chassis boards include the following:

• CPU-Memory board - The CPU-Memory board contains the PA 7100 processor chip, external cache, and globally accessible local memory. It is available in two designs: uniprocessor (one log-ical/ two physical CPUs) and twin processor (two logical/four physical CPUs). Both the unipro-cessors and twin processors are available in 72 or 96 MHz versions containing 256 KB instruction cache (Icache) and 256 KB data cache (Dcache) or 1 MB Icache and 1 MB Dcache. Memory sizes range from 128 MB to 512 MB (using 128-MB memory modules) or 512 MB to 2 GB (using 512-MB memory modules).

• SCSI-ENET Controller - The SCSI-ENET Controller is the interface between the system bus and the SCSI and Ethernet I/O devices. It contains four differential SCSI interface ports (used for interfacing with mass storage devices such as the D700 Disk/Tape Subsystem) and one Ethernet port. Each pair of SCSI-ENET Controllers can support up to 48 physical disk drives.

• IO Processor - The IO Processor manages IO operations, primarily to IOA communications adapters and certain peripheral devices. It interfaces the system bus to two 8-bit IO busses. The IO subsystem is similar to earlier Stratus IOP configurations, except that each IO Processor supports two IOA chassis and has additional fault tolerance and connectivity features.

The CPU-Memory boards reside in dedicated slots in the backplane (slots 0 and 1 in Series 600 sys-tems and slots 0, 1, 2, and 3 in Series 1200 systems). It is recommended that a pair of SCSI-ENET Controllers occupy slots 2 and 3 in Series 600 systems and slots 4 and 5 in Series 1200 systems. The remainder of the slots can be populated with either SCSI-ENET Controllers or IO Processors.

Continuum Series 600/1200 systems do not contain an operator front panel. All control functions are conducted through the system console. A Console Controller board supports the serial ports for the system console with front panel functions, the calender clock, remote consoles, and RSN.

The fault light (LED) scheme in Continuum Series 600/1200 systems is based on a traffic light config-uration and colors. The red LED is on the top, yellow is in the middle, and green is on the bottom. Red is defined as needs service, signifying a broken state. Yellow is don’t pull, indicating the boards MUST NOT BE REMOVED. Green indicates in operation or on-line.


Both VOS and FTX operating systems support Continuum Series 600/1200 AC systems (DC systems are supported by FTX only). The minimum release for VOS is 13.0 and the minimum for FTX is 3.0.

CPU memory can be upgraded on-line by going to simplexed mode, switching to the new board, upgrading the other board, and returning to duplexed mode. On-line addition of SCSI-ENET Control-lers and IO Processors is also supported.

System fault information is collected by the Cabinet Data Collector (CDC). This is a simplexed board located on the fan assembly backplane. The CDC collects fault and ID information from CRUs within the cabinet. It also monitors and controls fan speed. An RS-485 communication link passes cabinet fault information to the Console Controllers in the CEC cabinet.

The CDC also controls the cabinet fault and system status (CEC cabinet only) indicator on the which is located at the top front of each cabinet. The alarm display panel isolates the “cabinet fault” signal and connects it to a remote monitoring location in Central Office systems.

All Continuum Series 600/1200 cabinets have a door mounted on the front for easy access by the cus-tomer. All customer replaceable units (CRUs), with the exception of certain AC/DC power system components, are accessible from the front of the cabinet. The rear of the cabinets have removable pan-els for access to field replaceable units (FRUs).

All cabinets are shipped with earthquake brackets which are designed to comply with Central Office (CO) requirements.

1.2 System Configurations

As stated earlier, there are two basic Continuum Series system configurations, the Series 600 and the Series 1200. The following subsections describe both versions.

Series 600

The Series 600 contains a 6-slot CEC backplane. The CPU-Memory boards are installed in one pair of slots (0 and 1). Slots 2 and 3 should be populated with a pair of SCSI-ENET Controllers. The remain-ing slots (4 and 5) can be used for IO or SCSI-ENET pairs. The minimum and maximum memory con-figurations are 128 MB and 512 MB, respectively.

The Series 600 CEC IOA chassis holds up to 11 IOA boards (two of which are terminators) and is powered by dual power supplies located directly above it.

The Series 600 can exist as a stand-alone CEC cabinet containing the main chassis boards, IOAs, and two D700 Disk/tape subassemblies. The CEC cabinet in an AC system contains an AC/DC power sys-tem that provides up to 3600 watts of N+1 DC power. The AC/DC power system residing in each expansion cabinet (except the AC peripheral cabinet, which has no power) provides up to 2400 watts. The major components in the AC/DC power system are the AC Power Controllers (ACPCs), Power Control Backplane, Power Supply Units (PSUs), Power Control Unit (PCU), Battery Fuse Unit (BFU), a battery drawer (contains the batteries), and fiber optic cables. The functions of these components are described in Chapter 3.

All cabinets (except the AC peripheral expansion cabinet) in a DC system are powered by DC power controllers. Two power controllers reside in each cabinet for fault tolerance.

The maximum AC system configuration consists of a CEC cabinet and three expansion cabinets. The maximum DC configuration contains a CEC cabinet and three expansion cabinets. Refer to Section for a description of Continuum Series 600/1200 expansion cabinets.


The Series 600 CEC cabinet front and rear components (AC system) are shown in Figure 1.

Figure 1. Series 600 CEC Cabinet Components (AC System)

The Series 600 CEC cabinet front and rear components (DC system) are shown in Figure 2.

Figure 2. Series 600 CEC Cabinet Components (DC System)

3 1/2” Disk Drive

CPU/Mem Board

SCSI-ENET/IO

(2 slots)

Board (4 slots)

(1-6 per enclosure)

Air Filter

AC/DC Power System

Disk/TapePower Supply

(1 or 2 per enclosure)

Fan Backplane

Front View Rear View

Fan Assembly (6)

IOA Chassis

Backplane Power

Console Controller (2)

5 1/4” Tape Drive(1 or 2 per enclosure)

IOA Chassis Power

(11 slots)

CDC/Fan Control

Air Distribution Region

Supply (2)


Supply (2)

PSU (4)

PCU (1)ACPC (2)

BFU (1)

BatteryDrawer

Air Filter

Board

3 1/2” Disk Drive

CPU/Mem Board

SCSI-ENET/IO

(2 slots)

Board (4 slots)

(1-6 per enclosure)

Air Filter

DC Controller (2)

Disk/TapePower Supply

(1 or 2 per enclosure)

Fan Backplane

Front View Rear View

Fan Assembly (6)

IOA Chassis

Backplane Power


5 1/4” Tape Drive(1 or 2 per enclosure)

IOA Chassis Power

(11 slots)

CDC/Fan Control


Supply (2)


Supply (2)

Air Filter

10

Board


The hardware configuration requirements and restrictions for the Series 600 are shown in Table 1.

NOTE: The configurations shown in this document are based on information available at the time of publication. For current (and more detailed) configuration information refer to the Continuum Series 600/1200 Configuration Specification (ES-000076) located in the (master_disk)>Stratus_Service>documentation2>specs directory.

Table 1. Series 600 Hardware Configuration Requirements

* VOS only.

Series 1200

Series 1200 systems are designed around a 12-slot CEC backplane (slots 0-11). Four slots (0-3) are dedicated for up to two pairs of CPU-Memory boards. Slots 4 and 5 should be populated with a pair of SCSI-ENET Controllers. The remaining slots (6-11) can be used for IO or SCSI-ENET pairs. The min-imum and maximum memory configurations are 128 MB and 2 GB, respectively.

The CEC cabinet contains the CPU-Memory boards, SCSI-ENET Controllers and/or IO Processors. All IOAs and peripherals in AC systems reside in expansion cabinets. The CEC cabinet in a DC system can house two D700 Disk/Tape enclosures. The Series 1200 IOA chassis holds up to 16 IOA boards (two are terminators).

Like the Series 600 systems, the CEC cabinet in an AC system contains an AC/DC power system that provides up to 3600 watts of N+1 DC power. The AC/DC power system residing in each expansion cabinet (except the AC peripheral cabinet, which has no power) provides up to 2400 watts.

Component Model 610S* Model 610 Model 620 Model 625

CPU-Memory board G731 G731-G734 G735-G738G745-G748,G755-G758

No. of CPU-Memory boards 2 2 2 2

No.of logical CPUs (duplexed) 1 1 2 2

Duplexed memoryMin. = 128 MBMax. = 128 MB

Min. = 128 MBMax. = 512 MB

Min. = 256 MBMax. = 512 MB

Min. = 256 MBMax. = 2 GB

No. of IO ProcessorsMin. = 0Max. = 2

Min. = 0Max. = 2

Min. = 0Max. = 2

Min. = 0Max. = 2

No. of SCSI-ENET ControllersMin. = 2Max. = 2

Min. = 2Max. = 4

Min. = 2Max. = 4

Min. = 2Max. = 4

No. of CEC IOA chassis (11-slot) Min. = 0Max. = 1

Min. = 0Max. = 1

Min. = 0Max. = 1

Min. = 0Max. = 1

No. of IOA chassis (16-slot)Min. = 0Max. = 0

Min. = 0Max. = 2

Min. = 0Max. = 2

Min. = 0Max. = 2

No. of D700 Disk/Tape enclosuresMin. = 2Max. = 2

Min. = 2Max. = 16

Min. = 2Max. = 16

Min. = 2Max. = 16

No. of disk drives (VOS systems)

Min. = 2Max. = 10

Min. = 2Max. = 60

Min. = 2Max. = 60

Min. = 2Max. = 60

No. of disk drives (FTX systems) NA

Min. = 2Max. = 84

Min. = 2Max. = 84

Min. = 2Max. = 84

No. of tape drivesMin. = 1Max. = 1

Min. = 1Max. = 4

Min. = 1Max. = 4

Min. = 1Max. = 4

No. of expansion cabinetsMin. = 0Max. = 0

Min. = 0Max. = 3

Min. = 0Max. = 3

Min. = 0Max. = 3


The minimum Series 1200 configuration for an AC installation is the CEC cabinet and one expansion cabinet. The maximum configuration is the CEC cabinet and six expansion cabinets. Refer to Section for a description of Continuum Series 600/1200 expansion cabinets.

Also like 600 Series systems, DC Series 1200 systems are powered by DC Power Controllers con-tained in the CEC cabinet and in each expansion cabinet. The minimum Series 1200 configuration for a DC installation is the CEC cabinet and one expansion cabinet. The maximum DC configuration is one CEC cabinet and six expansion cabinets.

The Series 1200 CEC cabinet components (AC system) are shown in Figure 3.


Figure 3. Series 1200 CEC Cabinet Components (AC System)

The Series 1200 CEC cabinet components (DC system) are shown in Figure 4

Figure 4. Series 1200 CEC Cabinet Components (DC System)

Rear View

CPU/Mem Board

SCSI-ENET/IO

(4 slots) Backplane Power


Front View

CDC/Fan Control Board Fan Assembly (6)

Fan

Air DistributionRegion


Supply (2)

Board (8 slots)

100

AC/DC Power System

Air Filter

Backplane

PSU (4)

PCU (1)

BFU (1)

BatteryDrawer

ACPC (2)

Air Filter

Rear View

CPU/Mem Board

SCSI-ENET/IO

(4 slots) Backplane Power


Front View

CDC/Fan Control Board Fan Assembly (6)

Fan

D700 Enclosure (2)


Supply (2)

Board (8 slots)

100

DC Controller (2)

Air Filter

Backplane

Air Filter


The hardware configuration requirements and restrictions for the Series 1200 are shown in Table 2.

Table 2. Series 1200 Hardware Configuration Requirements

* VOS version of Model 1245 requires minimum VOS 13.2.1 operating system.

Expansion Cabinets

Expansion cabinets are used for housing D700 Disk/tape enclosures, IOA chassis, and AC peripherals (T204, T403-001, T403-002, and U202).

The following expansion cabinets are available for use on Continuum Series 600/1200 systems.

• Model E601 - Used on all Central Office systems (Series 600 and 1200). Contains an internal DC Power Controller.

• Model E610 - Used on all AC systems (Series 600 and 1200). Contains a 2400W AC/DC power system.

• Model E612 - Used for housing AC peripherals (T204-001 and T403-001/002 tape drives, U201 CIU for channel attach, and U250-10 remote I/O).

• Model E612-NP - Contains no power. Used for housing DB25 interconnect panels for the K118.

Maximum expansion cabinet configurations are shown in Figure 5.

Component Model 1210 Model 1215 Model 1220 Model 1225 Model 1245*

CPU-Memory board G731-G734G741-G744’G751-G754

G735-G738G745-G748,G755-G758

G745-G748,G755-G757

No. of CPU-Memory boards 2 2 2 2 4

No. of logical CPUs 1 1 2 2 4

Duplexed memoryMin. = 128 MBMax = 512 MB


Min. = 128 MBMax. = 512MB

Min. = 256 MBMax = 2 GB


No. of IO ProcessorsMin. = 0Max. = 6

Min. = 0Max. = 6

Min. = 0Max. = 6

Min. = 0Max. = 6

Min. = 0Max. = 6

No. of SCSI-ENET Controllers

Min. = 2Max. = 8

Min. = 2Max. = 8

Min. = 2Max. = 8

Min. = 2Max. = 8

Min. = 2Max. = 8

No. of IOA chassisMin. = 0Max. = 6

Min. = 0Max. = 6

Min. = 0Max. = 6

Min. = 0Max. = 6

Min. = 0Max. = 6

No. of D700 Disk/Tapeenclosures

Min. = 2Max. = 16

Min. = 2Max. = 16

Min. = 2Max. = 32

Min. = 2Max. = 16

Min. = 2Max. = 32

No. of disk drives(VOS systems)

Min. = 2Max. = 60

Min. = 2Max. = 60

Min. = 2Max. = 60

Min. = 2Max. = 60

Min. = 2Max. = 60

No. of disk drives(FTX systems)

Min. = 2Max. = 84

Min. = 2Max. = 84

Min. = 2Max. = 84

Min. = 2Max. = 84

Min. = 2Max. = 84

No. of tape drivesMin. = 1Max. = 4

Min. = 1Max. = 4

Min. = 1Max. = 4

Min. = 1Max. = 4

Min. = 1Max. = 4

No. of expansion cabinetsMin. = 1Max. = 6

Min. = 1Max. = 6

Min. = 1Max. = 6

Min. = 1Max. = 6

Min. = 1Max. = 6


Figure 5. Maximum Expansion Cabinet Configurations

Disk/Tape Subsystem

All D701/702 disk drives and T701/702/703 tape drives are contained in the D700 Disk/Tape Sub-system which is connected to a SCSI port on the SCSI-ENET Controller. After all SCSI ports on a board are filled, a second D700 Disk/Tape Subsystem can be daisy-chained to the primary D700 on each port. The cable connecting them is available in various lengths, allowing the secondary to be con-figured in either the same or another cabinet. Also, any standalone SCSI tape drive (T204 or T403) must be daisy-chained to a primary D700 Disk/Tape Subsystem.

Maximum D700Configuration

Maximum IOAConfiguration

Maximum D700/IOAConfiguration

DC Power Controller

DC Power Controller

E601 Expansion Cabinet

Maximum D700Configuration

Maximum IOAConfiguration

Maximum D700/IOAConfiguration

DC Power Controller

AC/DC PowerSystem

AC/DC PowerSystem

AC/DC PowerSystem

E610 Expansion Cabinet


If partner D70X disks need to be placed on a single pair of SCSI-ENET Controllers, a separate Con-troller should be assigned as master for each partner of the duplexed pair. Disks should never be duplexed within a single D700 enclosure or between two disks daisy-chained on the same SCSI bus.

The standard D700 Disk/Tape Subsystem contains a single power supply. A redundant power supply is optional. Each power supply occupies one chassis slot, each disk drive requires one slot, and each tape drive requires three slots.

All D700 Disk/Tape Subsystems are configured in a cabinet starting at the bottom and moving upward. Slots within a subsystem enclosure range from 0 to 6 (a triple-width slot), starting from the left-most slot (which always contains a power supply). Disk drives are added from left to right, occupying slots 1-6. If a tape drive is present, it is always in the right-most position (occupying slot 6). A second tape drive would occupy slots 3-5. The slots in the D700 Disk/Tape Subsystem are mechanically keyed in order to prevent bus addressing conflicts.

Possible maximum configurations for a D700 Disk/Tape Subsystem are shown in Table 3.

Table 3. D700 Disk/Tape Subsystem Configurations

The AC peripherals, which include the T204-001/T403-001/T403-002 tape drives, and the U202 Chan-nel Interface Unit, are housed in an E612 expansion cabinet (available VOS Rel. 13.1/FTX Rel. 3.0.1).

1.3 System Specifications

This section contains the physical, environmental, and electrical specifications for Continuum Series 600/1200 systems.

Power SupplyNumber of

Power SuppliesMax. Numberof D70X Disks

Max. Numberof T70X Tapes

Single power (disks only) 1 6 0Single power (disks and tapes) 1 2 2Single power (disks and tape) 1 5 1Dual power (disks only) 2 5 0Dual power (disks and tapes) 2 1 2Dual power (disks and tape) 2 4 1

PhysicalHeight 180.3 cm (71 inches)Width 76.2 cm (30 inches)Depth 99 cm (39 inches)Weight 544.3 kg (1200 lbs) max.

EnvironmentalOperating temperature (AC and DC systems) -200 to 6000 ft 4.5° to 40° C (40° to 104° F) 6000 to 8000 ft 4.5° to 35° C (40° to 95° F) 8000 to 10,000 ft 4.5° to 30° C (40° to 86° F)Short term (<72 hrs) operating temp. (DC systems only) -200 to 6000 ft 1.7° to 49° C (35° to 120° F) 6000 to 8000 ft 1.7° to 45° C (35° to 113° F) 8000 to 10,000 ft 1.7° to 35° C (35° to 95° F)


Heat dissipation (maximum) CEC cab. (AC systems) 15,131 Btu/hr Expansion cab. (AC systems) 15,131 Btu/hr CEC cab. (DC systems) 12,283 Btu/hr Expansion cab. (DC systems) 12,283 Btu/hrRelative humidity 10% to 80% non-condensingMax. rate of temp. change 12°/hr C (21.6°/hr F)Acoustical noise (per cabinet)

fans at normal speed 67 dBA

fans at full speed 77 dBA

Electrical (AC Cabinets)AC service requirements Two 30A, single-phase AC inputs (1 active, 1 standby)AC input voltage range Nominal 200 to 240 V AC Absolute 180 to 264 V ACAC input frequency range 47 to 63 HzEfficiency (min.) 82%Power factor >.99 (>10% load)AC input power (max.) 4.44 KVAInput current (@ 3600 W of power delivered to load) Minimum 16.8 A @ 264 V AC Nominal 22.2 A @ 200 V AC

18.5 A @ 240 V AC Maximum 24.7 A @ 180 V ACDC output voltage range -40.0 to -59.9 V DC Nominal -54.5 V DCDC output power (max.) 3600 WAC line cord (dual; 1 active, 1 standby) Standard length 4.6 m (15 ft) Optional length 7.6 m (25 ft) Termination (domestic) NEMA 30A, 250V twistlock connector Termination (intl.) IEC 309, 32A, 250V pin and sleeve connector

Electrical (DC Cabinets)DC service requirements Two 100A DC inputsDC input voltage range -42.0 to -59.9 V DC Nominal -54.5 V DCDC input power (max.) 3650 WInput current (@ 3600 W of power delivered to load) Minimum 61.0 A @ -59.9 V DC Nominal 67.0 A @ -54.5 V DC Maximum 87.0 A @ -40.0 V DCDC output power (max.) 3600 WDC line cord (dual; load sharing) Standard length 7.6 m (25 ft) Optional length 15.2 m (50 ft) Termination Double-holed ring lug connector


2. Operating Controls and Procedures

This chapter explains the basic controls and operating procedures used for system operation and main-tenance. Topics covered include the following:

• Cabinet indicators

• Basic operating procedures

• System verification

• Maintenance procedures

2.1 Cabinet Indicators

This section describes the status LEDs on the CEC and expansion cabinets.

2.1.1 CEC Cabinet

The CEC cabinet contains three LEDs (two yellow and one green) mounted horizontally and labeled as shown in the following diagram:

When the System Fault LED is on, it indicates a hardware fault in one or more of the system cabinets. The Cabinet Fault LED indicates a fault in the CEC cabinet when it is on. When the No Fault LED is on, it means the system is operating and there are no hardware faults in any system cabinets.

2.1.2 Expansion Cabinet

Each expansion cabinet contains one yellow LED (labeled Cabinet Fault) which, when on, signifies a fault within that cabinet.

2.2 Basic Operating Procedures

There is no physical control panel on Continuum Series 600/1200 systems. Operating (front panel) commands are entered at the system console which is connected to the system via the Console Control-ler card in the CEC cabinet.

The front panel commands are accessed by pressing the Ctrl and Break keys simultaneously. The fol-lowing is a list of front panel commands.

Yellow Yellow Green

System Fault Cabinet Fault No Fault


help ............... displays command list.boot_auto .......... begin automatic mode startup.boot_manual ........ begin operator assisted mode startup.shutdown ........... begin orderly system shutdown.power_off .......... immediately kill power.restart_cpu ........ force CPU into kernel dump/debug mode.reset_bus .......... force reset *ALL* boards.status ............. report state of system indicator lamps.history ............ display switch closure history.quit, q ............ exit the front panel command loop.. ................ display firmware revision.

2.2.1 Starting the System

This section describes how to perform both an automatic and manual system startup. The procedure is the same for both VOS and FTX systems.

1. Press the Ctrl and Break keys simultaneously to access the front panel commands. Then perform either step 2a or 2b.

2a. Automatic Startup:

Enter the boot_auto command to begin automatic mode startup.

The CEC initiates a startup by sending signals to the next cabinet (if there is one) in the daisy-chain. The cabinets will all sequence on. At this point the daisy-chained cabinets are sequentially powered up.

The boards in the CEC perform self tests and display their resulting status. If the tests com-plete successfully, the status is duplexed (all green LEDs illuminated). The green LED on components such as fan modules and power modules should also be illuminated.

2b. Manual Startup:

1) Enter the boot_manual command to begin operator assisted mode startup.

2) When prompted, enter the slot location of the boot disk.

Example:

4 1 1 1

where 4 is the slot number of the SCSI-ENET Controller, the first 1 is the SCSI-ENET Controller port number, the second 1 is the D700 Disk/Tape enclosure, and the last 1 is the slot number of the drive within the enclosure.

The CEC initiates a startup by sending signals to the next cabinet (if there is one) in the daisy-chain. The cabinets will all sequence on. At this point the daisy-chained cabinets are sequentially powered up.

The boards in the CEC perform self tests and display their resulting status. If the tests com-plete successfully, the status is duplexed (all green LEDs illuminated). The green LED on components such as fan modules and power modules should also be illuminated.


2.2.2 Shutting Down the System

This section describes how to shut down the system for both VOS and FTX operating systems. The following are some of the circumstances calling for a system shutdown.

• Relocating the system

• Certain FRU removal and replacement procedures

• An emergency situation

2.2.2.1 VOS

1. Login as sysadmin .

2. Enter the following command to display the names of all users still logged in.

list_users

3. Enter the broadcast command to inform users of imminent shutdown.

Example:

broadcast ‘The system will shut down in 5 minutes.’

4. To shut down all modules in the system, enter the following command.

shutdown

2.2.2.2 FTX

1. Login as root.

2. Check to see if any users are on the system by entering the who -H command.

3. If there are users on the system, enter the wall command followed by a message (on one or more separate lines) announcing the shutdown. End the message by pressing the Control and D keys simultaneously (CTRL-d).

Example:

wall

The system will shut down in 5 minutes.

Please log off.

<CTRL-d>

4. To power down the system from multiuser state (state 2):

Enter the following command.

shutdown -i0

where -i0 changes the system state to state 0 (off).

To power down the system from the single user state:

Enter the following command.

shutdown -y -i0 -g0


where the -y option assumes “yes” to all prompts, -i0 shuts down the system to state 0 (off), and -g0 defines the grace period as 0 seconds.

2.2.3 Rebooting the System

This section describes how to reboot the system for both VOS and FTX operating systems.

2.2.3.1 VOS

1. Login as sysadmin .

2. Enter the following command to display the names of users still logged in on the system.

list_users

3. Enter the broadcast command to inform users of imminent shutdown.

Example:

broadcast ‘The system will shut down in 5 minutes.’

4. To halt and immediately start up all modules in the system, enter the following command.

shutdown -reboot

2.2.3.2 FTX

1. Login as root .

2. Check to see if any users are on the system by entering the who -H command.

3. If there are users on the system, enter the wall command followed by a message (on one or more separate lines) announcing the shutdown. End the message by pressing the Control and D keys simultaneously (CTRL-d).

Example:

wall

The system will be coming down in 5 minutes.

Please log off.

<CTRL-d>

4. To halt and reboot the system, enter the following command:

shutdown -i6

where -i6 indicates state 6 , meaning stop and reboot.

2.3 System Verification

System operation must be verified before and after removal and replacement of CRUs and FRUs. This section provides verification information for both FTX and VOS operating systems. Many of the CRUs and FRUs have status lights which give you an indication of their status (refer to Chapter 5). However, it is always best to verify system operation as shown in the following subsections. The pro-cedures are provided for both VOS and FTX operating systems.


2.3.1 VOS

To verify system operation, perform the following procedure.

1. At the READY prompt, enter the following command to check the status of the controller boards, buses, fans, and power system.

analyze_system -request_line list_boards -quit

This command accesses the analyze_system subsystem, requests a listing of boards, and returns to the original command level after the list is displayed.

The information is displayed in the following format.

Module %es#m13 (12 Slot Chassis) Id Prom ------Fault Data------ Slot Board Type Model Serial Rev Rev Cnt Code Last Fault Time 0 CPU-Memory G74500 99 29 23 0 1 CPU-Memory G74500 97 25 23 0 4 SCSI-ENET Controller K45000 95 04 02 0 1 SCSI Port SCSI00 **** *** 0 1 Device Enclosure ENCL00 *** *** 1 1.05 GB SCSI Disk D70100 9999 0 0 2 1.9 GB SCSI Disk D70200 9999 0 0 2 Device Enclosure ENCL00 *** *** 0 2 1.9 GB SCSI Disk D70200 9999 0 0

If a board is removed from service, the list_boards display highlights the entire line that contains information about that board. If the board has a fault but has not been removed from service, the display highlights only the Code field for the board.

The Cnt field, when related to boards, lists the number of errors on the board since it was inserted. When related to a fan unit, it indicates the number of times the fan unit has failed, come back up to speed, and failed again. When related to a battery unit, it indicates the num-ber of successful power fail recoveries by this module since the last bootload or a problem with the battery unit charging circuit.

Whenever a board fails, the Code field displays a code describing the type of failure. When a code is displayed, it is interpreted at the bottom of the screen.

2. At the READY prompt, enter the following command to check the status of the disks.

display_disk_info -long

where -long displays a long report on the disk, including information about the capacity of the disk and the number/percentage of disk blocks being used in each paging, file and log partition.



Module %s1#m5

%cacj1#j1_masPartition Size Used Free Left

Paging 40960 2558 38402 93.75%File 227232 163320 63912 28.12%

Member Pri Sec Attributes0 04/01/01/01 04/02/01/01 D701, duplex, verify, serial

Volume Reads Writes Attributes181448 4741 mounted

%cacj1#j1_usrPartition Size Used Free Left

File 460992 124739 336253 72.94%Member Pri Sec Attributes

0 04/01/01/02 04/02/01/02 D702, duplex, verify, serialVolume Reads Writes Attributes

141425 25077 mounted

3. Test disk drive operation by making sure you can write to and read from the disk drives. This can be accomplished by creating two directories (test1 and test2). Copy several files into test1. Then copy the files from test1 to test2. Check the system error logs for any errors, then delete both directories when you are done.

4. Operate the tape drive to be sure it works properly.

2.3.2 FTX

To verify system operation, perform the following procedure.

1. At the prompt, enter the following command to check the status of the controller boards, peripherals, buses, and power supply.

/sbin/hwmaint ls |more

The information is listed in the following format:

Modelx Description State Code Flg Serial BdRv McRv Slot loc

- Continuum Chassis- GBus- GBusA- GBusB

g74500 PA-RISC 2*96 128 C onln - --- 470 374.00 0Physical CPU onln - --- 0 0Physical MEM onln - --- 0 1Physical CPU onln - --- 0 2


k45000 SCSI/Ethernet Cont onln - --- 245 2700.00 4SCSI port 0 onln - --- 4 1

d701 1GB Disk Driv onln - --- 084297 - - 4 1 1 1 0d702 2GB Disk Driv onln - --- 972298 - - 4 1 1 2 0

SCSI port 1 onln - --- 4 2d701 1GB Disk Driv onln - --- 042347 - - 4 2 1 1 0d702 2GB Disk Driv onln - --- 961432 - - 4 2 1 2 0

If a FRU is not operating, an out-of-service code is displayed in the Code field. The out-of-service code is repeated at the bottom of the display, along with a description of the problem.


NOTE: For more detailed information, use the -l option to display the FRUs in the long list format.

2. To check the virtual disk status, enter the following command.

/sbin/vdskconf -L |more

The information is listed in the following format:

vdskA06: dev(41,6):[vdskA] 1L x 2W blks=265800 status=online hard_attr: allow_subset=NO auto_recovery=YES error_notify=NO

parallel_write=YES write_verify=NO soft_attr: allow_subset=NO auto_recovery=YES error_notify=NO

parallel_write=YES write_verify=NO vdsk_uid=(7832317, 0, 21115)

Mirror #1: /dev/rdsk/c4a1d0s06 dev(99,1114118) Slot(4 1 1 1) tstamp=32 status=online mirror_uid=(7832320, 0, 21115) Mirror #2: /dev/rdsk/c4a2d0s06 dev(99,1146886) Slot(4 2 1 1) tstamp=32 status=online mirror_uid=(7832321, 0, 21115)

where vdskA06 is the virtual disk partition, vdskA is the virtual disk text name, 1L x 2W indicates there is one (L)ogical and two (W)orking disks (which means the disks are duplexed), Mirror #1 and Mirror #2 are the partners in the virtual disk. The status field for the vir-tual disk drive and both partners should say status=online .

3. Test disk drive operation by making sure you can write to and read from the disk drives. The following is a sample procedure used to test a disk named vdskC whose mount point is /usr2 (the mount point for the disk is determined by entering the mount command).

a. Change to the /usr2 directory.

cd /usr2

b. Create directories named test and test2 .

mkdir test

mkdir test2

c. Change to the test directory.

cd test

d. Copy all files from the /etc/vtocs directory into the test directory and list the files copied to verify it worked.

cp /etc/vtocs/* ./

ls

e. Copy the files in /usr2/test to /usr2/test2 .

cp ./* /usr2/test2

f. Change to the /usr2/test2 directory and list the files copied to verify it worked.

cd .. /test2

ls

g. Change to the /usr2 parent directory and delete the test and test2 directories.


cd ..

rm -r test

rm-r test2

4. Verify that the tape drive works properly using the tar or cpio command.

The following is a sample tar command:

/usr/sbin/tar -u * /dev/rmt/c20a3d0

where /usr/sbin/tar -u updates and copies the all the files (*) in the current directory to the tape drive whose device file name is /dev/rmt/c20a3d0 .

The following is a sample cpio command:

ls | cpio -oc > /dev/rmt/c20a4d0

where ls lists the contents of the current directory, | pipes it to cpio -oc (copy out command), and > redirects it to /dev/rmt/c20a4d0 which is the device file name of the tape drive.

2.4 Maintenance Procedures

This section provides a set of frequently used maintenance procedures for both VOS and FTX systems. Included are software procedures that need to be followed when preparing to remove a main processor board or when removing/adding a disk drive. Use these procedures in conjunction with the removal and replacement procedures located in Chapter 5.

2.4.1 VOS

2.4.1.1 Preparing to Remove a Main Processor Board

If a board’s red LED is lit and the yellow and green LEDs are off, it is safe to remove that board. If the board is not red lit, perform the following procedure.

1. Test the duplex status of the main processor boards by entering the following command.

analyze_system -request_line list_boards -quit

This command accesses the analyze_system subsystem, requests a listing of boards, and returns to the original command level after the list is displayed.


Module %es#m13 (12 Slot Chassis, Model xxxx) Id Prom ------Fault Data------ Slot Board Type Model Serial Rev Rev Cnt Code Last Fault Time 0 CPU-Memory G74500 99 29 23 0 1 CPU-Memory G74500 97 25 23 0 4 SCSI-ENET Controller K45000 95 04 02 0 1 SCSI Port SCSI00 **** *** 0 1 Device Enclosure ENCL00 *** *** 1 1.05 GB SCSI Disk D70100 9999 0 0 2 1.9 GB SCSI Disk D70200 9999 0 0 2 Device Enclosure ENCL00 *** *** 0 2 1.9 GB SCSI Disk D70200 9999 0 0

If a board is removed from service, the list_boards display highlights the entire line that contains information about that board. If the board has a fault but has not been removed


from service, the display highlights only the Code field for the board.

The Cnt field lists the number of errors on the board since it was inserted.

Whenever a board fails, the Code field displays a code describing the type of failure and interprets the failure at the bottom of the screen.

2. Check to see if the board you want to remove has a partner listed.

a. If the board has a partner and the partner is not highlighted in the board listing, it is safe to remove that board.

b. If the board has no partner, it can be replaced on-line only if the replacement board is at a compatible board revision and will duplex with the existing simplexed board. To do this, insert the board in the simplexed board’s “partner” slot. When both boards are fully duplexed (green lights are on, yellow and red are off), remove the original board.

NOTE: If the board is a SCSI-ENET board, the active ENET port will have moved to the partner slot.

If the replacement board is not at a compatible board revision, it is not safe to remove the board without crashing the system. You must shut down the module to remove the board.

c. If the board has a partner and the partner is highlighted in the board listing, it is not safe to remove either board without crashing the system. You must shut down the module to remove this board.

2.4.1.2 Logically Removing a Disk Drive

Before you physically remove a disk drive it must be deleted from the operating system. The following procedure describes how to logically delete the disk drive from the VOS operating system.

NOTE: If you are logged in remotely and CSS is installed, you can execute the monitor_syserr.pm command located in >system>tools_library as a back-ground process to enable the terminal to display error log information. However, you will be unable to use the terminal for normal commands while it is running.

1. Check the status of the failing disk by entering the display_disk_info -long com-mand. The information is displayed in the following format.


Module %cacj1#m1

%cacj1#j1_masPartition Size Used Free Left

Paging 40960 2558 38402 93.75%File 227232 163320 63912 28.12%

Member Pri Sec Attributes0 04/01/01/01 04/02/01/01 D701, duplex, verify, serial

Volume Reads Writes Attributes181448 4741 mounted

%cacj1#j1_usrPartition Size Used Free Left


0 04/01/01/02 04/02/01/02 D702, nonduplex, verify, serialVolume Reads Writes Attributes

141425 25077 mounted

%cacj1#j1_d02Partition Size Used Free Left


0 02/01/01/03 D702, nonduplex, verify, serialVolume Reads Writes Attributes

25106 150832 mounted

2. Check the Attributes column. Decide which of the following applies to the failing disk drive and then go to step 3a, 3b or 3c.

Case A: Disk drive is listed as duplex or nonduplex with an on-line partner.Case B: Disk drive is listed as non-duplex and does not have an on-line partner.Case C: Disk drive is not listed.

3a. Case A: Duplex or nonduplex disk.

Logically delete the failing disk by executing the remove_disk command.

Sample command:

remove_disk 04/02/01/02

where 04/02/01/02 is the device id of the disk drive to be removed (04 is the slot num-ber of the SCSI-ENET Controller, 02 is the SCSI-ENET Controller port number, 01 is the number of the D700 Disk/Tape enclosure, and 02 is the slot number of the disk drive within the enclosure).

The disk drive is placed in the unknown state and powered down. The green LED on the disk drive goes out and the yellow LED flashes while the disk drive is powering down, then goes out. When the yellow light is out, it is safe to remove the disk.

3b. Case B: Disk is listed, but has no on-line partner.

There are three situations to be considered.

(1) The failed disk is a simplexed master disk and/or has a paging partition.


(2) The failed disk is a simplexed data disk without a paging partition.

(3) The disk is a simplexed disk and it needs to be replaced either due to an increasingerror rate or an FCO installation.

Situation (1)

The module must be shut down before replacing the disk. When the replacement disk has been installed, the contents of the master disk will have to be reloaded from the most recent boot tape which was made using the dump_disk command.

For information on performing backup and restore procedures, refer to the following manu-als: VOS System Administration: Disk and Tape Administration (R284) and VOS System Administration: Backing Up and Restoring Data (R285).

Situation (2)

The system does not have to be shut down; however, the disk will have to be dismounted. This may mean that the customer application that uses this disk will have to be stopped. Consult with the customer prior to attempting to dismount the disk. The data disk can be reloaded from the most recent “save” tape.

For information on performing backup and restore procedures, refer to the following manu-als: VOS System Administration: Disk and Tape Administration (R284) and VOS System Administration: Backing Up and Restoring Data (R285).

Situation (3)

Try to duplex the disk by performing either of the following procedures:

a. Simplex a duplexed member of a logical volume using the procedure for removing a disk described in Step 3a above. Then duplex that disk with the disk that has to be

replaced by following the procedure in Section 2.4.1.3. Once recovery has been com-pleted, the disk can be safely removed.

b. Install the replacement disk in an unused slot. Then duplex it with the disk that is to be replaced by following the procedure in Section 2.4.1.3.

If neither of the above actions are possible, then proceed as in situation (1) or (2) above.

3c. Case C: Disk is not listed.

In this case the failed disk drive has already been removed from the system. You may safely replace the disk drive and then add it back following the procedure in Section 2.4.1.3.

2.4.1.3 Logically Adding a Disk Drive

Adding a Duplex Disk Partner

1. Use the setup_disk command to bring the disk to the known state.

Sample command:

setup_disk 04/02/01/02

where 04/02/01/02 is the device id of the disk drive to be removed (04 is the slot number of the SCSI-ENET Controller, 02 is the SCSI-ENET Controller port number, 01 is the number of the D700 Disk/Tape enclosure, and 02 is the slot number of the disk within the enclosure).

2. Initialize the disk as the secondary or primary partner of the duplex disk using the


initialize_duplex_disk command.

Sample command:

initialize_duplex_disk disk_04_02_01_02 d01 0

where disk_04_02_01_02 is the uninitialized name of the disk, d01 is the logical vol-ume of which the initialized disk will be a member, and 0 is the member disk number (between 0 and 9, inclusive) which refers to the member disk’s location within the logical volume.

3. Enter the following command to bring the disk up to date with its partner.

start_disk_recovery

4. Enter the display_disk_info -long command to verify that the replacement disk drive now shows as duplex or recovering .

2.4.2 FTX

2.4.2.1 Logically Removing a Main Processor Board

If a board’s red LED is lit and the yellow and green LED are off, it is safe to remove that board. If the board is not red lit, perform the following procedure.

1. Test the board’s duplex status by entering the following command.

/sbin/hwmaint ls bd



g74500 PA-RISC 2*96/128 C onln - --- 470 3724.00 0g74500 PA-RISC 2*96/128 C onln - --- 597 3724.00 1k45000 SCSI/Ethernet Cont onln - --- 245 2700.00 4k45000 SCSI/Ethernet Cont onln - --- 262 2800.00 5k60000 IOP Board onln - --- 248 312.139 10

2. Check to see if the failed board’s partner is listed as onln in the State field. To do this, use the following method to determine which slot number holds the partner board: if the board you want to remove is in an odd-numbered slot, the board in the lower-numbered slot immediately adjacent to it is its partner. If you want to remove an even-numbered board, then the board in the higher-numbered slot immediately adjacent to it is its partner.

3. If the board has a partner, and the partner is on-line, enter the hwmaint delete com-mand for the board you want to remove.

Sample command:

/sbin/hwmaint delete 5

where 05 is the slot location of the board in the main chassis.

If the board has no partner, it can be replaced on-line only if the replacement board is at a compatible board revision and will duplex with the existing simplexed board. To do this, insert the board in the simplexed board’s “partner” slot. When both boards are fully duplexed (green lights are on, yellow and red are off), remove the original board.


NOTE: If the board is a SCSI-ENET board, the active ENET port will have moved to the partner slot.

If the replacement board is not at a compatible board revision, it is not safe to remove the board without crashing the system. You must shut down the module to remove the board.

2.4.2.2 Logically Removing a Disk Drive

Before you physically remove a disk drive it must be deleted from the operating system. The following procedure describes how to logically delete the disk drive from the FTX operating system.

NOTE: If you are logged in remotely, you can execute the elgnotify & command as a background process to enable the terminal to display informational and errlog information. elgnotify is assigned a process id number when executed as a background process. This id can be used to kill the background process in order to stop the displaying of console messages on the user’s screen.

NOTE: The SCSI ID of a disk is not the same as the slot number of the disk within the D700 Disk/Tape enclosure. SCSI IDs range from 0 to 5; slot numbers range from 1 to 6. Example: if the SCSI ID of a disk is 1, the slot number of the disk is 2. In the following procedures, the SCSI ID is used with the vdskconf command and the slot number is used with the hwmaint command.

1. Check the status of the failing disk by executing the vdskconf -L and hwmaint ls disk commands. Decide which of the following applies to the disk drive and then perform step 2a, 2b, 2c, or 2d. Then proceed as directed.

vdskconf -L |more hwmaint ls disk |more

A. status = offline state = suspvirtual disk is duplexed (1L x 2W)

B. status = online state = onlnvirtual disk is duplexed (1L x 2W)

C. disk not listed state = EMPTYvirtual disk is duplexed (1L x 2W)

D. disk not listed state = EMPTYvirtual disk is simplexed (1L x 1W)

2a. Case A: Disk is offline and suspended, virtual disk is duplexed.Execute the vdskconf -E command to remove the disk as a virtual disk partner. Then go to Step 3.

Sample command:

vdskconf -E -v /dev/rdsk/vdskA06 -d /dev/rdsk/c4a1d1s06

where -E removes the disk as a virtual disk partner, -v specifies the virtual disk device name /dev/rdsk/vdskA06 , and -d specifies the device name of the failing disk /dev/rdsk/c4a1d1s06 (4 is the slot number of the SCSI-ENET Controller, 1 is the SCSI-ENET Con-troller port number, 1 is the SCSI ID of the disk drive, and 06 is the partition number).

2b. Case B: Disk is online, virtual disk is duplexed.


Execute the vdskconf -D command to remove the disk as a virtual disk partner. Then go to Step 3.

Sample command:

vdskconf -D -v /dev/rdsk/vdskA06 -d /dev/rdsk/c4a1d1s06

where -D removes the disk as a virtual disk partner, -v specifies the virtual disk device name /dev/rdsk/vdskA06 , and -d specifies the device name of the failing disk /dev/rdsk/c4a1d1s06 (4 is the slot number of the SCSI-ENET Controller, 1 is the SCSI-ENET Con-troller port number, 1 is the SCSI ID of the disk drive, and 06 is the partition number).

2c. Case C: Disk is not listed, state is empty, virtual disk is duplexed.Use the vdskconf -E command to remove the disk as a virtual disk partner. Then go to Step 3.

Sample command:

vdskconf -E -v /dev/rdsk/vdskA06 -d /dev/rdsk/c4a1d1s06

where -E removes the disk as a virtual disk partner, -v specifies the virtual disk device name /dev/rdsk/vdskA06 , and -d specifies the device name of the failing disk /dev/rdsk/c4a1d1s06 (4 is the slot number of the SCSI-ENET Controller, 1 is the SCSI-ENET Con-troller port number, 1 is the SCSI ID of the disk drive, and 06 is the partition number).

2d. Case D: Disk is not listed, state is empty, virtual disk is simplexed.It is safe to physically remove the disk.

3. Logically delete the failing disk by executing the hwmaint delete command.

Sample command:

/sbin/hwmaint delete 4 1 1 2 0

where 4 is the slot number of the SCSI-ENET Controller, 1 is the SCSI-ENET Controller port number, 1 is the D700 Disk/Tape enclosure, 2 is the slot number of the drive within the enclosure, and 0 is the logical unit number (always 0 for disks).

When the command is executed, the yellow LOCK light on the disk starts blinking, and the Starting Disk Deletion message appears on the display.

When the disk deletion completed message appears on the screen, it is safe to physi-cally remove the disk.

CAUTION: If the disk drive is removed prior to the appearance of the disk dele-tion completed message, loss of data and/or damage to the disk drive can occur.

2.4.2.3 Logically Adding a Disk Drive

1. Add the disk drive to the system by executing the hwmaint add command.

Sample command:

/sbin/hwmaint add 4 1 1 2 0

where 4 is the slot number of the SCSI-ENET Controller, 1 is the SCSI-ENET Controller port number, 1 is the D700 Disk/Tape enclosure, 2 is the slot number of the drive within the enclosure, and 0 is the logical unit number (always 0 for disks).


NOTE: If a message is displayed indicating the slot is reserved, execute the hwmaint unreserve command to cancel it, then enter the hwmaint add command again.

2. Wait for the disk drive to come on-line.

3. Check the status of the disk using the following command.

/sbin/hwmaint ls disk

The information will look similar to the following:

Modelx Description State Code Flg Serial BdRv McRv Slotloc

d701 1 GB SCSI Disk Driv onln - --- 084297 - - 4 1 1 1 0d702 2 GB SCSI Disk Driv SLABEL - --- 072298 - - 4 1 1 2 0d701 1 GB SCSI Disk Driv onln - --- 104297 - - 4 2 1 1 0d702 2 GB SCSI Disk Driv onln - --- 073298 - - 4 2 1 2 0

The word SLABEL should appear in the Code column indicating the disk drive has an invalid disk label.

4. Write (initialize) the disk label by executing the ilab command.

Sample command for a root disk:

ilab -d /dev/rdsk/c4a1d1s14 -r 0 -m d702

where -d /dev/rdsk/c4a1d1s14 specifies the device file (4 is the slot number of the SCSI-ENET Controller, 1 is the SCSI-ENET Controller port number, 1 is the SCSI ID of the disk drive, and 14 is the partition number). -r 0 specifies the root partition (partition 0). -m specifies the disk model (d702 ).

NOTE: The -r option is used only with root (boot) disks.

Sample command for a non-root disk:

ilab -d /dev/rdsk/c4a1d1s14 -m d702

where -d /dev/rdsk/c4a1d1s14 specifies the device file. -m specifies the disk model (d702 ).

ilab suspends the disk in order to write the labels to it. When it’s finished, it leaves the disk in the SUSPENDED state and displays a message similar to the following:

ilab: /dev/rdsk/c4ad1s14 should be partitioned before it is brought online.

5. If this is a root disk, place the boot program load on the boot partition using the newboot command. If this is not a root disk, go toStep 6.


Sample command:

/sbin/newboot /stand/load /dev/rdsk/c4a1d1s14

where load is the boot program and /dev/rdsk/c4a1d1s14 is the device file for the physi-cal disk.

6. Save the volume table of contents (VTOC) of the partner of the failed disk and redirect it to a file that can be used to partition the replacement drive using the mkvtoc -z command.

Sample command:

/sbin/mkvtoc -z /dev/rdsk/c4a2d1s14 > /etc/vtocs/d702.new

where the -z option saves the current VTOC for the failed disk’s partner (/dev/rdsk/c4a2d01s14 ) and > redirects it to the d702.new file in /etc/vtocs .

7. Put the VTOC on the replacement disk using the mkvtoc -s command.

Sample command:

/sbin/mkvtoc -s /etc/vtocs/d702.new /dev/rdsk/c4a1d1s14

where -s /etc/vtocs/d702.new is the partition information in the VTOC file of the failed disk’s partner. /dev/rdsk/c4a1d1s14 is the device file for the physical disk.

8. Bring the new disk drive into service by executing the hwmaint start command.

Sample command:

/sbin/hwmaint start 4 1 1 2 0

9. Add the new disk drive to the existing simplexed virtual disk by executing the vdskconf -A command.

NOTE: By convention, vdsk06 is the name of the first virtual disk pair (the root disk pair) on the system. The second virtual disk pair is usually named vdskA06, the third is vdskB06, etc. In each case, 06 specifies partition 6, which is the entire usable disk area.

Sample command:

vdskconf -A -v /dev/rdsk/vdskA06 -d /dev/rdsk/c4a1d1s06

where -A adds the new disk as a mirrored partner, -v specifies the virtual disk device name (/dev/rdsk/vdskA06 ), -d specifies the physical device name of the new disk (/dev/rdsk/c4a1d1s06 ).

After a short time the message recovery started should appear on the screen, mean-ing an automatic recovery of the disk is in progress.

10.Check the status of the virtual disk recovery by executing the vdskconf -L command.

The information is listed in the following format.


vdskA06: dev(41,6):[vdskA] 1L x 2W blks=265800 status=online hard_attr: allow_subset=NO auto_recovery=YES error_notify=NO

parallel_write=YES write_verify=NO soft_attr: allow_subset=NO auto_recovery=YES error_notify=NO

parallel_write=YES write_verify=NO vdsk_uid=(7832317, 0, 21115)

Mirror #1: /dev/rdsk/c4a1d1s06 dev(99,1114118) Slot(4 1 1 2) tstamp=32 status=in_recovery mirror_uid=(7832320, 0, 21115) Mirror #2: /dev/rdsk/c4a2d1s06 dev(99,1146886) Slot(4 2 1 2) tstamp=32 status=online mirror_uid=(7832321, 0, 21115)

In the above listing, auto_recovery=YES indicates disk recovery starts automatically. Mirror #1 and Mirror #2 are the partners in the virtual disk. status=in_recovery for Mirror #1 means the disk is in automatic recovery and will come on-line when the recovery is complete.

In case recovery does not occur automatically (if auto_recovery=NO in the vdskconf -L display), initiate a directed recovery when both mirrors are online using the vdskconf -R command. The disk being recovered will be updated with information from its partner.

Sample command:

vdskconf -R -v /dev/rdsk/vdskA06 -x rdelay=0

where -R starts the recovery and -x rdelay=0 sets the time delay between I/O opera-tions in recovering the disk to 0.

NOTE: A maximum of two recoveries can take place simultaneously.

For more information on commands pertaining to disk maintenance, refer to the FTX System Adminis-trator’s Guide (R124).


3. Theory of Operation

This chapter contains an overview of the theory of operation for the Continuum Series 600/1200 sys-tems. It provides information on how the system operates and includes a description of each of the fol-lowing major components/subsystems.

• System bus

• CPU-Memory board

• SCSI-ENET Controller

• IO Processor

• Console controller

• Cabinet data collector

• Power system

• Cooling system

• Peripherals

3.1 System Bus

The system bus and its interfaces perform the following major functions:

• Transfer information between the boards residing on the system bus backplane

• Provide fault detection and isolation for the system bus and boards

The system bus is a single logical split transaction multiplexed address/data-type bus. It’s duplicated to provide fault tolerance. Major features of the bus include the ability to support 32- and 64-bit bus inter-face widths, completely synchronous operation, cache consistency support, and a single logical Appli-cation Specific Integrated Circuit (ASIC) interface.

The bus is 64 bits wide for communications between CPU-Memory boards, but only 32 bits extend to the IO slots (SCSI-ENET Controllers and IO Processors). Peak supported bandwidths are 128 MB/sec between CPU-Memory boards (assuming all line transfers) and 76.8 MB/sec for IO boards. All infor-mation transfer across the system bus occurs synchronously to and from the bus transceivers at 24 MHz.

A single logical bus is used for both address and data transfer. The bus contains up to 64 bits of infor-mation (data or address and function code), 7 bits of tag, and a single bit which indicates whether the information lines are carrying data or address and function code. The IO boards only connect to 32 bits of the information bus.

Control signals and arbitration lines are protected by a three-way voting algorithm. This provides the ability to tolerate a single control signal failure within each three-way voted control line.

The system bus interface provides full checking between the C-side and D-side of its resident boards via loopback, thereby providing board-level fault detection. The system bus interface can isolate itself from the system bus, even in the event of clock failures, to provide board-level fault isolation.

Because of the split nature of the bus, all boards in the system must be able to arbitrate for the bus and initiate a bus operation.


The system bus is implemented on two different backplanes: the Series 600 6-slot backplane and the Series 1200 12-slot backplane.

The system bus has an extremely efficient physical implementation. Support for its information trans-fer and fault detection/isolation capabilities requires only the following:

• Clock generation circuitry

• Connectors

• Transceivers

• One logical (two physical) ASICs

• One logical (two physical) Medium Scale Integration (MSI) 20-pin register component

• MSI circuitry to support board ID PROMs and board LEDs

The 32-bit section of the bus interface requires fewer than 150 backplane signal connections and the 64-bit section requires fewer than 250 backplane signal connections. The 32-bit and 64-bit interfaces coexist in the same backplane, but backplane slots are wired to support one or the other. An AMP-SL-100 connector is used for the system bus backplane connections. Both the 32-bit and 64-bit interfaces are supported via two 391-pin ASICs.

The transceiver used on the system bus is the FB20333 with controlled edge rates capable of delivering 100 mA on the bus side.

The system bus interface requires three clocks to transfer information across the backplane: a ~24 MHz transmit clock, and a ~12 MHz receive clock, and a ~12 MHz phase information clock qualifier. In addition, the bus interfaces require two ~24 MHz clocks for transferring information from the bus transceivers to the bus ASICs.

Figure 6 is a high-level architectural view of the Continuum Series 600/1200 system.


Figure 6. Continuum Series 600/1200 System Block Diagram

3.2 CPU-Memory Board

The CPU-Memory board is a combined processor/memory board containing up to two logical (four physical) Hewlett Packard PA-RISC 7100 processors. The PA7100 chip is a highly integrated CPU that provides support for integer, floating point, and memory management functions all on the same integrated circuit. Unlike the Intel i860, there is no internal cache on the PA7100 chip. Instead, it sup-ports a large external cache with separate RAMs for instructions and data.

The CPU-Memory board is available in two designs:uniprocessor (one logical/ two physical CPUs) or twin processor (two logical/four physical CPUs). Both the uniprocessors and twin processors are avail-able in 72 or 96 MHz versions with 256 KB instruction cache (Icache) and 256 KB data cache (Dcache) or 1 MB Icache and 1 MB Dcache. Memory sizes range from 128 MB to 512 MB (using 128-MB memory modules) or 512 MB to 2 GB (using 512-MB memory modules).

As in earlier Stratus designs, the CPU-Memory board contains a C-side and D-side which are com-pared side-to-side to detect on-board errors. A partner board runs in lockstep and a detected failure on either board causes the board to go off-line. The CPU subsystem and system bus interface are fully duplicated and compared.

CPU/

Memory

Console

SCSI-ENET

IO

IOA Chassis

IOAAdapter

IOAAdapter

IOA Chassis

IOAAdapter

IOAAdapter

ENET

Dual Initiated SCSI

Console, RSNSystem Bus

Controller

Processor

Controller


The CPU-Memory board design uses a small number of high density CMOS ASICs which signifi-cantly reduces the number of components. The board is designed around a single motherboard with a broad range of CPU modules and DRAM configurations.

The CPU modules are housed on daughter cards. Each module contains a PA7100 CPU chip, separate 64-bit Icache and Dcache, and an interface to a high speed bus called the P-Bus.

All control for the Icache and Dcache is incorporated into the PA7100 chip. The Dcache and Icache implementation on the CPU module is a primary (1st level) cache which results in higher cache perfor-mance than other RISC architectures which implement small on-chip 1st level caches and large 2nd level caches. The caches are implemented using CMOS SRAMs and execute at the same clock fre-quency as the internal CPU pipeline. Duplicate copies of the cache tags are provided on the CPU board for assisting in cache coherency support for multi-processor operations.

Each CPU-Memory board can contain from 128 MB to 2 GB (in increments of 128 or 512 MB) of main memory mounted on small daughter cards called memory modules (banks). Each CPU-Memory board can contain up to four memory modules. A memory module consists of the following compo-nents:

• 128 or 512 MB of ECC-protected DRAM set up in four sub-banks (0, 1, 2, and 3)

• Four Memory Interface ASICs running at 48 MHz and fully lockstepped

• Memory bus (M-Bus) interface

The Memory Interface ASICs contain all control, address, and data buffering used to interface between the DRAMs on the memory module and the M-Bus. Each ASIC drives two sub-banks, either 0 and 2, or 1 and 3.

The M-Bus connects the memory modules to the CPU/Memory Control ASIC. This is a 391-pin ASIC interfacing two logical CPU modules to the high speed local memory and the system bus backplane. It supports the following functions:

• Memory system queue control and arbitration

• P-Bus arbitration and control

• Cache coherency checking for all P-Bus and I-Bus transactions

• CPU-specific timers and IO registers

• Board-specific sync and duplex logic

• JTAG boundary and internal scan

Another ASIC, the 391-pin System Bus Interface ASIC, connects the system bus with the CPU-Mem-ory board’s internal I-Bus. It provides logic for the system bus interface and fault detection/isolation for the CPU-Memory board. The system bus ASIC supports the following external interfaces:

• 32-bit data path to IO boards

• 64-bit data path to CPU boards

• Arbitration for the system bus

• I-Bus interface to the CPU-Memory Control ASIC

• ID Prom interface

• System-specific board sync and duplex logic

• Broken logic for checking system bus transactions


The third major ASIC contained on the CPU-Memory board is called the Sable ASIC. It connects the CPU-Memory Control ASIC to the following:

• Snoop tag SRAMs

• Boot Prom

• Console controller interface

The Snoop tag SRAMs are used by the CPU-Memory Control ASIC to manage cache coherency for the CPU module internal caches. The Sable ASIC implements an 8-bit wide data path to a bank of up to four 128KB x 8 Boot Proms. The Sable ASIC communicates with the Console Controllers over a 4MHz bus on the system backplane.

As stated earlier, each CPU-Memory board contains a C-side and a D-side which are compared side-to-side to detect on-board errors. A partner board runs in lockstep and a detected failure in either board causes that board to go off-line. The CPU subsystem and system bus interface are fully duplicated and compared. The memory subsystem uses ECC detection and correction to handle recoverable faults.

Figure 7 is a block diagram of the CPU-Memory board.

Figure 7. CPU-Memory Board Block Diagram

3.3 SCSI-ENET Controller

In addition to providing all the interface between the system bus and the SCSI and Ethernet IO devices, the SCSI-ENET Controller provides a place for functions such as memory protection to reside. It con-tains four differential SCSI interface ports (used for interfacing with mass storage devices such as the

CPUModule

CPUModule

CPUModule

Mem Bank 0Mem Bank 1Mem Bank 2Mem Bank 3

CPU-Memory

(D-Side)

Memory Modules

Sable

Snoop TagSRAMs

32K x 80

Snoop TagSRAMs32K x 80

Boot Prom768 KB

Boot Prom768 KB

System Bus

(D-Side)

IDProm

Console Controller BusSystem Bus

Interface ASICSystem Bus

(C-Side)Interface ASIC

Control ASIC CPU-Memory

(C-Side)Control ASIC

ASIC(D-Side)

SableASIC

(C-Side)

(D-Side) (C-side) (C-Side)

CPUModule(D-Side)

P-Bus P-Bus

I-Bus I-Bus

M-Bus


D700 Disk/Tape subsystem and T204/T403 tape drives) and one Ethernet port.

SCSI-ENET Controllers are self checking boards and will not corrupt main memory or disk IO in the event of a failure. They are not designed to operate as hardware lock-stepped pairs. Instead their pair-ing is a “hot-standby” approach where system performance degrades during the switch over and cer-tain services or data may be lost.

The SCSI-ENET microprocessor is the Intel 80960CA. This is a highly integrated controller with DMA, instruction cache, and interrupt control integrated on one chip. The processor has access to all the devices on the board.

The 80960CA has the following major features.

• Internal 4-channel DMA

• 1-MB SRAM main microprocessor memory

• 2-MB SRAM dedicated to IO devices

• 512-KB Flash PROM for diagnostics and microprocessor code space

• Microprocessor Flash PROM copied to SRAM after reset

The Links front-end gate array provides the connection between the system bus and a 32/32-bit SCSI-ENET internal address/data bus (known as the Linksbus). The Linksbus later splits into several buses:

• i960 bus - where the 80960CA microprocessor and its associated 1 MB of SRAM reside

• Serial port bus (SP bus) - where the 85C30 serial IO chips reside

• Serial IO (SIO bus)

• Multiple-SCSI-Ethernet bus (MSE bus) - where the four SCSI controllers and a single Ether-net controller reside

The Linksbus contains the 2-MB SRAM array (mentioned above) dedicated to the IO devices on the MSE-bus. Connected to the drive-side of the i960-bus are the serial communication chips (SCC), also known as the SIO devices, and µp PROM.

The ID PROM, connected between the two Links gate arrays, is an addressable storage device used for board ID as well as maintenance and diagnostic (M&D) information such as board configuration and broken status history.

The Links front-end gate array provides arbitration control for the Linksbus and parity checking/gener-ation for devices that support parity.

The SCSI-ENET Controller contains an ASIC (named Topflight) which is essentially a “glue” ASIC since it combines and supports various functions on the SCSI-ENET Controller. It contains the follow-ing components:

• SRAM controllers for µp memory and IO memory

• Address decoders for the i960 bus and the Linksbus

• Check logic for the i960 bus, Linksbus, and MSE bus devices

• SCSI-ENET IO memory and slave access check logic

• IO registers accessed via the i960 bus

• Transceiver control for the Linksbus, i960 bus, MSE bus SP bus, and SIO bus

The 80960CA microprocessor, the Links front-end gate array, and the Topflight ASIC are all dupli-


cated and self-checking. The IO devices are not self-checking. An address protection mechanism is provided for IOMem and facilitated by Links to protect the host system bus as well as partitioned memory regions on the SCSI-ENET Controller from failing IO devices.

The local memory is divided into two sections. The IO memory supplies configuration and control information for devices on the MSE bus. The microprocessor memory provides data and code space for the local processor.

The SCSI and Ethernet controllers transfer data directly to the host system with minimal intervention from the local processor. The SIO devices connected to the SP-bus require the processor for the move-ment of data. SIO devices are used for SCSI M&D functions.

The SCSI-ENET Controller supports boot from SCSI disk, SCSI tape, or from the Ethernet controller located on the SCSI-ENET.

SCSI bus termination is provided by scorecards located on the backplane. The scorecards provide a hardware medium between two same-numbered ports on a pair (odd and even) of SCSI-ENET Control-lers. Each pair of same-numbered SCSI ports (one logical port) requires two scorecards. No scorecard is required on the ENET port since it is not hardwired. Also, a selector dial (coding key) on the back-plane must be set to position 2 on each slot containing a SCSI-ENET Controller. A receptacle on the SCSI-ENET Controller mates with the coding key when the board is inserted.

A block diagram of the SCSI-ENET Controller is shown in Figure 8. The diagram shows how the board interfaces with the system bus and devices.

Figure 8. SCSI-ENET Controller Block Diagram

SCSI

SCSI

SCSI

SCSI

ENET

SIOPROM

IO MemoryTopflight

ID Prom

Link

s G

ate

Arr

ayD

-Sid

eLi

nks

Gat

e A

rray

C-S

ide

80960CA µp µp Memory

IO Memory

80960CA µp µp Memory

SP Bus SIO Busi960 Bus

MS

E B

us

Linksbus

Sys

tem

Bus

Sys

tem

Bus

ASIC

TopflightASIC


3.4 IO Processor

The Stratus IO processor interfaces the system bus to two 8-bit IO busses. The IO subsystem is similar to earlier Stratus IOP configurations, except that each IO processor supports two IOA chassis and has additional fault tolerance and connectivity features.

The IO bus and card cage operate off 24 V DC which has been converted from 48 V DC by the IOA chassis power supply.

Each IO bus is logically capable of supporting 16 IOA cards, two of which must be terminator cards. The IOA cardcage in the Series 600 CEC cabinet can hold up to 11 IOA cards, including two termina-tors; the IOA card cages in the expansion cabinet can support the full complement of 16 IOAs, includ-ing two terminators.

The IO processor has an address map containing physical and virtual index translations. This is used to relocate addresses anywhere in the physical address space and provide cache consistency with the CPU. The processor scan cycle allows the 68030 microprocessor to scan a single IO slot.

The IO processor contains the following major components:

• MC68030 microprocessor operating at 48 MHz

• Two IO interfaces

• 4 MB duplexed DRAM (using eight 1MBx4 60ns DRAMs)

• 1 MB Flash EEPROM (using eight 128KBx8 120ns flash EEPROM)

• Dennison ASIC - consolidates much of the discrete control logic, 68030 interface, DRAM control, address map RAM, 2 logical gate arrays for DMA, and timer support

• System bus interface ASIC - interfaces the system bus to the Dennison ASIC

• 2 KB globally accessible serial FLASH EEPROM - used for ID information

The MC68030 processor provides 32-bit registers and 32-bit data paths with direct addressing of up to 4 GB of combined memory and IO space. Features of the MC68030 include the following:

• 256-byte instruction cache and 256-byte data cache

• Dynamic bus sizing supporting 8-, 16-, and 32-bit memories and peripherals

• Full 32-bit general purpose data and address registers

• Sixteen 32-bit general purpose data and address registers

• Two 32-bit supervisor stack pointers and 10 special purpose control registers

• Paged memory management unit that translates addresses in parallel with instruction execu-tion and internal cache accesses

• Pipelined architecture

• Enhanced bus controller support for asynchronous bus cycles, synchronous bus cycles, and burst data transfers

Termination requirements for the IO processor are provided by scorecards located on the backplane. The IO processor requires four scorecards per port. Also, a selector dial (coding key) on the backplane must be set to position 4 on each slot containing an IO processor. A receptacle on the IO processor mates with the coding key when the board is inserted.


A block diagram of the IO Processor is shown in Figure 9.

Figure 9. Block Diagram of IO Processor

3.5 Console Controller

The Console Controller serves as the hardware interface between the system logic boards and all the devices that are not connected to the system bus. In the CEC cabinet this includes the Remote Service Network (RSN), console, calendar clock, backplane power supplies, backplane ID PROM, power sub-system, cooling system, cabinet LEDs, filter switches, and other miscellaneous devices. The Console Controller also interfaces to the Cabinet Data Collectors (CDCs) in remote cabinets.

The Console Controller performs a number of critical functions. First, it is used as an IO board for key low speed communications, which provides an interface to the console and the RSN. Next, it serves as a central collection point for Maintenance and Diagnostics (M&D) services. Third, it controls and monitors the main power supply for the system. In essence, the Console Controller functions as a cen-tralized controller for the entire system.

The Console Controller is a duplexed hardware design. All the components except the DUARTS and the calender clock are duplexed. Since these are asynchronous devices, there is no way to lock-step them. Therefore, a pair of Console Controllers (one on-line and one on hot-standby) are connected to

IOA Chassis IOA Chassis

DRAM

68030 µp

IO ProcessorIO

IO Interface Logic & transceivers

IO Interface Logic & transceivers

BusIOBus

Dennison ASIC

System Bus EEPROM

IDPROM

InternalIO Bus

InternalIO Bus

Clocks

System Bus transceivers

InternalBus

System Bus

Interface ASIC


all the host CPUs in a system by a fault-tolerant 8-bit multiplexed bus. If the on-line Console Control-ler fails, there is a “failover” to the standby Console Controller. In general, the off-line Console Con-troller is idle. When a Console Controller comes on-line after its partner goes off-line, any pending IOs may or may not have completed. The software resets all of the lines and sends a message to the console indicating this state. This is similar to pulling and re-plugging in an IOA card. There is interruption to the service, but the system remains up.

The Console Controller is powered by the housekeeping power supply. It is the only board in the sys-tem powered by this supply since it is responsible for controlling the main power system which powers the rest of the system. This means the Console Controllers are powered, even when the rest of the sys-tem is powered down.

The Console Controller firmware provides a number of services including the use of the console as a “soft” front panel. This “soft” front panel interface uses asynchronous communications lines for all functions instead of the more traditional buttons or switches. The Console Controller also provides col-lection and dispatching of M&D data, RSN access to the system, access to the calendar clock, and the use of the secondary console for kernel debugging.

The interface between the host and the Console Controller consists of a 1024 bytes of shared memory through which data are transferred and a set of three interrupt registers. Although the Console Control-lers are physically connected to all CPUs in the system and each CPU has a shared memory and a set of interrupt registers, the Console Controller “sees” only one shared memory and one interrupt register.

Because of the on-line/hot-standby configuration, the host can communicate with both Console Con-trollers. This allows the host to provide both Console Controllers with up-to-date boot information, to set the clock to the same (nominal) time, and to burn the prom on the off-line board.

The Console Controller is a bus-based design. Its MC68000 microprocessor bus connects all devices on the board. The bus consists of a 24-bit address bus and a 16-bit data bus. The following components are resident on the microprocessor bus.

• MC68000 microprocessor

• DUARTS (2)

• SRAM

• EEPROM

• Calendar clock

• Gate array

The MC68000 microprocessor runs at 16 MHz. It features a 24-bit address bus, 16-bit data bus, 17 32-bit internal registers, and 56 instruction types.

The DUART is an industry standard Z85230 DUART which is an extremely versatile communications controller. Its present implementation uses only async protocols. The Z95230 contains an A channel and a B channel that are virtually identical. Each channel contains nine read and 16 write registers.

The SRAM holds both data and code for normal user execution.

The EEPROM is used to hold static variables for the microprocessor, configuration information for the system, boot information, ID information, fault status information, and diagnostics and operating code.

The calendar clock is a battery backed up real time clock chip. It is used only at boot time and occa-sionally as specified by the user. It should not be confused with the Time of Day clocks local to each CPU-Memory board.


The gate array decodes the address and function code and generates the pertinent control signals required to access each particular device.

A block diagram of the Console Controller is shown in Figure 10.

Figure 10. Block Diagram of Console Controller

The Console Controller interconnections are shown in Figure 11.

MC68000 EEPROMSRAM

Gate ArrayBuffer

C Address Bus

C Data Bus (16 bits)

D Data Bus (16 bits)

Comparator

D Address Bus

MC68000 EEPROMSRAM

Gate ArrayBuffer

Time of Day

D Address Bus

D Data Bus (16 bits)

DUART Data Bus (8 bits)

Clock/CalendarSerial

Comparator

ConsoleController

Bus

ConsoleController

Bus

Comm.Controllers

C-Side

D-Side


Figure 11. Console Controller Interconnections

3.6 Cabinet Data Collector

The Cabinet Data Collector (CDC) is a simplexed, non fault-tolerant board. Every cabinet in a Contin-uum Series 600/1200 system contains a CDC board. It is part of the CDC/Fan Control board which resides on the fan backplane.

The CDC gathers and reports non mission-critical fault and status information for local and remote cabinets and transmits the data back to the Console Controller board over a serial, half-duplexed RS-485 line. The information includes two kinds of device status: ID PROM status and current fault infor-mation. The current fault status of every cabinet is continuously available by reading the various status registers in each CDC.

The CDC provides on-line readable ID PROM capability to selected “dumb” FRUs/CRUs in both remote and local cabinets. Each of these FRUs/CRUs contains an ID PROM daughter board. The CDC provides the interface between the daughter board and the Maintenance System Network.

Another function of the CDC is responsibility for monitoring and controlling the speed of the cabinet fans in a fail-safe manner. Under normal operating conditions (no fan failures, inlet air temperature, and bulk voltage OK), the CDC runs the fans at approximately two-thirds speed (2200-2300 rpm). This is done to reduce acoustical noise to within acceptable limits and enhance fan Mean Time Between Failures (MTBF). If the CDC fails or any of the operating conditions mentioned above are not met, the fans will run at full speed (3500 rpm).

The CDC also controls the cabinet fault light located in the alarm display panel. All CRUs and FRUs in the cabinet are constantly monitored for fault conditions by the CDC. When the CDC detects a fault, it reports it to the appropriate fault status register and turns on the cabinet fault light.

Logical Host CPU 0 Logical Host CPU 1

On-lineConsole Controller

StandbyConsole Controller

ConsoleRemoteConsole RSN M&D

System Bus

Console Controller Bus


A block diagram of the CDC is shown in Figure 12.

Figure 12. Cabinet Data Collector Block Diagram

3.7 Power System

3.7.1 AC Systems

Power for Continuum Series 600/1200 AC systems is provided by an AC/DC power system wholly contained within each cabinet (except the AC peripherals expansion cabinet, which contains an AC controller). The AC/DC power system in the CEC cabinet provides up to 3600 watts of N+1 DC power (2400 watts in an expansion cabinet). The N+1 architecture is modeled after telecommunications power plants where AC/DC converters (rectifiers), also known as Power Supply Units (PSUs), are connected in parallel and maintain a constant voltage across the batteries and load. Every configura-tion of output power includes a “spare” PSU. The spare is available to pick up the load in the event of a single PSU failure. During steady state operation, the energy from the spare is used to charge the bat-teries. Only the PSUs are scalable. The batteries are not N+1 configured.

The AC/DC power system is equipped with two single-phase line cords which are connected to each cabinet via two NEMA 30A, 250V twistlock connectors (domestic) or two IEC 309 32A, 250V pin and sleeve connectors (international).

The nominal DC output voltage is -54.5 V DC, which is the optimal charging voltage of the batteries. The DC output bus is divided into two separate distribution paths, each of which can maintain full sys-tem operation in the event of a DC distribution path loss.

Fan Speed Control

TempSensor

AddressPAL

Inter-Cabinet Maintenance Bus (RS-485)

Intra-Cabinet Bus (Single Ended)

IDPROM

16-Bit Data Bus

ControlPAL

Address from previous cabinet

Address to next cabinet

MC14469

CommandDecode

Shift Register

Converter


The AC/DC power system is comprised of the following major components:

• Two AC Power Controllers (ACPCs)

• Power control backplane

• Three or four Power Supply Units (PSUs)

• One Power Control Unit (PCU)

• One Battery Fuse Unit (BFU)

• One battery drawer (contains four batteries)

• Fiber optics cables

• Two air filters

The ACPCs control AC input to the system. The ACPC sends an alarm to the CDC if any of the fol-lowing occur: an AC failure, the ACPC circuit breaker is released, or the ACPC is faulty.

The APCs work in a master/slave arrangement, which means only one ACPC supplies ALL of the power to that cabinet. When the line on ACPC (A) fails, the batteries discharge and after three (3) sec-onds the ACPC (B) takes over. The system will not automatically switch back to the A linecord. When the line on ACPC (B) fails, the batteries discharge and after one (1) second the ACPC (A) takes over. The system will not automatically switch back to the B linecord.

The system always defaults to start on the left ACPC (A). (that's why the A to B transition is three sec-onds and the B to A transition is one second)

If there is no power on the ACPC, where it switches over to, the system will run on the batteries. If the batteries are exhausted at that moment, the system will crash.

The power fail detector looks for something longer than 1.5 seconds, so that is why warnings occur on A to B but not B to A. In both cases however, the batteries do discharge for a short time.

The ACPC contains three LEDs, aligned vertically (red, yellow, green). The red LED (labeled Error ) is on steady when the ACPC is faulty, the green LED (labeled On) is on steady if no faults are detected, and the yellow LED (labeled Alarm ) illuminates if the ACPC’s partner has a fault.

The power control backplane is a simplexed board that serves as the signal interface to/from the AC/DC power system and between units within the power system. Each AC/DC power system contains a power control backplane. Signals to/from the CDC/fan control board are transmitted via cables from the power control backplane to the backplane of the fan assembly where the CDC/fan control assembly board is located. The signals between cabinets are transmitted via the connectors on the power control backplane. These are labeled PrevA, PrevB, PrevC, NextA, NextB, and NextC. The Prev connectors are inputs; the Next connectors are outputs. An RS-232 interface is also located on the power control backplane.

The PSU is a 1200W high frequency rectifier that converts the 220 V AC input voltage into a regulated -48 V DC. There are four (3+1) PSUs in the AC/DC power system in the CEC cabinet (three in the expansion cabinet), resulting in a maximum output of 3600 W + 1200 W redundant power (2400 W + 1200 W in the expansion cabinet). Communication between the PSU and the power control unit (PCU) is via optical fiber. Control signals for output voltage and maximum output power are sent from the PCU to the PSUs. Alarm signals and status signals are sent from the PSUs to the PCU.

The PSU contains two LEDs. The red LED (labeled Error ) is on steady when the PSU is faulty. A green LED (labeled On) is on steady when the unit is functioning properly. Another green LED (labeled Communication) is on steady when communication with the PSU is OK; it flashes when


communication is interrupted.

The PCU is the control and supervision unit of the AC/DC power system. It monitors all FRU/CRU faults within its cabinet. Communication between system units is via optical fiber. The PCU sends alarm signals to the CDC when faults occur. The signals are sent via relays and an isolated RS-232 interface. Status information from the PSUs is also obtained via the RS-232 interface.

The PCU contains two LEDs. The green LED (labeled On) is on steady when the PCU is functioning properly; it flashes when communication is interrupted. The red LED (labeled Alarm ) lights when there is a fault.

The BFU monitors system voltage, battery voltage, battery current, battery temperature, and the bat-tery circuit breaker. It sends an alarm to the Console Controller if the battery is discharging, and an alarm to the CDC if there is a BFU fault or if the battery temperature gets too high. If the BFU detects low voltage, high battery temperature, or certain other faults, it disconnects the low voltage disconnect unit (LVDU) contactor. It will reconnect the battery when the fault is corrected.

The BFU contains three LEDs. The red LED (labeled Error ) lights when the BFU is faulty. The green LED (labeled On) lights when the unit is on. Another green LED (labeled Communication) is on steady when communication with the BFU is OK, and flashes when the communication is interrupted.

Each battery drawer contains four -12 V DC batteries connected in series. The four batteries make up a battery string of -48 V DC. Each battery string is rated at 5 KW. The battery drawer monitors battery status and communicates these signals to the LVDU, Console Controller, and CDC.

The battery drawer also contains four temperature sensors connected to the BFU via a cable from the back of the drawer. The CDC/fan control board collects the cabinet’s alarm data and transfers it to the CEC cabinet.

The battery drawer has a red LED at the front which lights when the battery temperature is greater than 60°C (140°F) or when the battery voltage is below -44 V DC after the battery has been disconnected.

In the event of a powerfail (defined as any occurrence where the batteries are discharging), the batter-ies have sufficient load capacity to provide up to four minutes of continuous power. Typically, full sys-tem operation is sustained for a one minute ride-through, after which the software initiates a system shutdown. The CEC is notified of the powerfail situation via a fault-tolerant reporting network (reported over 3 signal lines to the Console Controller).

A powerfail prompts the following activities:

• AC powerfail and/or battery discharge is detected and the information made available to the CEC through both the fault-tolerant 3-way voted signals and the CDC.

• The PSUs turn off with the loss of AC.

• Batteries discharge backing up system components.


The actions taken during the powerfail process are shown in Figure 13.

Figure 13. Powerfail Timing

Issue stop

4 minutes

1 min

Begin s/w shutdown of machine

Issue warning

Battery LVD

10 sec 10 sec

DisconnectsBattery

DischargeDetected


If AC power returns during ride-through, then the PSUs automatically come on-line. If AC remains failed and/or the batteries continue to discharge, the CEC generates a STOP command to the CEC power controllers when it has completed its powerfail process. This is done to conserve battery energy.

If the powerfail condition continues and the CEC has not completed its powerfail process, then battery discharge continues until the batteries reach the low voltage disconnect threshold of -40.0 V DC. At this point, the batteries are disconnected from the load via the power system LVDU contactor.

The battery subsystem has enough energy to sustain full system ride-through during a repetitive pow-erfail occurrence. All tests are conducted at full-rated load for each configuration and the battery sub-system is in normal operation. The battery subsystem must also be able to successfully ride through four one-minute full-rated load battery backup cycles with no recharge.

The electrical block diagram for the 3600W AC/DC power system is shown in Figure 14.


Figure 14. 3600W AC/DC Power System Electrical Block Diagram

3.7.2 DC Systems (Central Office)

All cabinets in a Central Office (CO) system are powered by DC power controllers. These power controllers are used to control and monitor Telco’s negative voltage, redundant power plant. Two power controllers reside in each cabinet for fault tolerance. The power controllers are the same for the 12-slot CEC, the 6 -slot CEC and the E601 expansion cabinets. Each power controller accepts a single -48 V DC input from the CO battery plant and performs the following functions before the power is passed on to the remainder of the cabinet:

• Provides 100A circuit protection for the cabinet power

• Filters the input and output power from conducted EMI

• Switches the power on/off

PSU 1

PSU 2

PSU 3

PSU 4

PCU

CDC

BFU

Battery Drawer(Four -12 V DC Batteries)

AC IN1

AC IN2

-54.5 V DC Bus

Battery Bus

ACPC

ACPC


• Filters transients

• Monitors over/under voltages

• Slow-charges frame filter capacitors

• Sequences system startup

• Provides power to the CDC

• Generates cabinet-level housekeeping power

The DC power controllers do not have battery backup capabilities. This is due to the Telco power plant’s output (battery and generator backup) in a CO installation.

Service to a cabinet is provided by a cable assembly consisting of two #1/0 gauge wires carrying -48 V DC and -48 Return, respectively. The distribution system requires two CO input power cables per cab-inet, each mating with a separate power controller.

Power is distributed from the power controllers to other components in the cabinet via a bus bar. Each power controller has one power output connection to the bus bar. The bus bar contains four high cur-rent conductors: -48 V DC “A”, -48 V DC “B”, -48 RETURN and CHASSIS/SAFETY GROUND, each rated for 200 A of continuous current.

Each cabinet contains a power backplane residing behind the two power controllers. This backplane provides the signal interface from the cabinet to each power controller. The power controllers plug directly into the backplane via 72-pin connectors. The backplane is a simplexed board.

A block diagram of the DC power controller is shown in Figure 15.


Figure 15. DC Power Controller Block Diagram

3.8 Cooling System

The Continuum Series 600/1200 cooling system components consist of the following:

• Fan assemblies

• Air distribution regions

• Air filter

The cooling system uses a pull-through vertical cooling scheme. The fans are located at the top of each cabinet. Air is drawn into the cabinet through the air inlet regions located at the bottom front and rear of the cabinet and exhausted through the top of the cabinet.

The pull-through air delivery system provides balanced air flow distribution throughout the cabinet by creating a high static pressure, low velocity condition. The air is far less sensitive to being split and redirected than in a blow-through system.

Each cabinet contains six fan assemblies, each of which contains three 6-inch fans. The assembly also contains a single connector for power/signal interconnects, an in-line fuse holder, and a visual fault indicator located on the front surface of the assembly.

EMI Filters

Frame Filter Caps

Circuit Breaker-48 V DC Input

-48 V DC to System

Control PCB

Input PowerSwitch

-48 V DC

LEDPCB

Power In and CRU Faults

to CDC and Console Controller


The air distribution regions direct air into critical areas where the air flow cross section may not be optimum.

The air filter(s) is/are mounted horizontally within the air inlet area at the bottom of the cabinet. AC systems have two air filters and DC systems have one. An air filter sensor switch is located at the rear of each filter and is activated when the filter is in place.

Normal cooling system operation is approximately two thirds of full speed operation to reduce cabinet noise levels. Certain environmental conditions shall cause the CDC to issue a “Full Speed” signal to each fan that will force the fans to 100% operating speed until normal environmental conditions have been restored. (See Section 3.6.)

3.9 Peripherals

3.9.1 D700 Disk/Tape Subsystem

The D700 Disk/Tape subsystem is a 24-inch rack-mounted enclosure with backplane supporting 3.5-inch D701/702 disk drives and 5.25-inch T701/702/703 tape drives. Each subsystem is powered by a single (or dual) power supply that receives -48 V DC system power and outputs +5 V DC to the devices. Since the D700 subsystem does not contain any fans, it utilizes the cooling system within the cabinet.

The D700 subsystem provides an alarm interface to the system cabinet. A serial status and control interface also is provided to the SCSI-ENET Controller to assist in fault detection, reporting, and isola-tion within the D700 subsystem. An alarm cable (RS-485) is daisy-chained from the CDC to all D700 enclosures within a cabinet. All disk and tape drives are hot-pluggable, and do not require system shut-down or power removal for normal customer replacement of a failed unit.

Each D70X disk/T70X tape drive contains three LEDs, aligned vertically (red, yellow, green). The red LED is used to indicate power and disk/tape drive faults. The green LED indicates the presence of +5V DC power and the disk drive is operational. The yellow LED is used to indicate a simplexed condi-tioned.

The D700 subsystem interfaces, via a differential SCSI interface, to the SCSI-ENET Controller. The D700 features a differential/fast-wide SCSI bus which allows for 16 devices on a single bus. All tape drives have an 8-bit, single-ended SCSI interface which is converted to differential SCSI within the device.

Synchronous data transfers occur at 10 MHZ/20 MB per second. Command queueing support is pro-vided for faster random access times.

3.9.2 D701/702 Disk Drives

The D701/D702 disk drives combine high performance with high reliability. They have an average positioning time of 10-11 msec and a maximum start/stop time of 20 sec. The internal transfer rate is 3.25-5.25 MB per second (26-42 MHz). The bus transfer rate is 20 MB per second (synchronous) and 10 MB per second (asynchronous). Each disk is capable of supporting at least 10 random IO accesses per CPU MIP. A complete disk recovery can occur in less than two hours, with less than a 10% degra-dation in system application performance.

The D701 contains 2372 cylinders and nine data surfaces. It has a formatted capacity of 1.108 GB. The D702 has 2372 cylinders and 15 data surfaces. Its formatted capacity is 1.903 GB.


3.9.3 T701/702/703 Tape Drives

The T701/T702 tape drives are 4-mm, Digital Audio Tapes(DAT) drives providing up to 4.0 GB stor-age capacity and a data transfer rates of 510 KB per second. The T702 features an autoloader with a 6-cartridge magazine with 50-60 second cartridge swap time. The T701/T702 have Media Recognition System (MRS) detection enabled. The drives can read both MRS and non-MRS tapes, but can only write to MRS tapes.

The T703 QIC cartridge tape drive provides 525MB storage capacity and a data transfer rate of 200 KB per second.

3.9.4 D700 Configurations

All D700 enclosures are configured in a cabinet starting at the bottom and moving upward. After all SCSI ports on a SCSI-ENET Controller are filled, a second D700 Disk/Tape Subsystem can be daisy-chained to the primary D700 on each port. The cable connecting the enclosures is available in various lengths allowing the secondary to be configured in either the same or another cabinet.

A standalone SCSI tape drive (T204 or T403) cannot be connected directly to a SCSI-ENET port. It must be daisy-chained to a primary D700 enclosure containing only disk drives (maximum of 5), or a primary D700 enclosure containing a maximum of two disk drives and one T70X tape drive which is installed in the left-most tape location. (Refer to the slot numbering scheme described later in this doc-ument.) T70X tape drives cannot be configured in secondary D700 enclosures.

Devices within the D700 enclosure are controlled by SCSI-ENET Controllers configured as dual initi-ators. This means that two SCSI-ENET Controllers are attached to the same SCSI bus. Disk duplexing on the SCSI-ENET pair is achieved through the use of two ports on each of the boards and specially designed scorecards. The scorecards function as a two-into-one conductor allowing two controllers to cable onto the same SCSI bus and serves as a hardware medium for dual initiation.

During normal operation, one port on the SCSI-ENET Controller is the default SCSI bus master and functions as initiator on the bus; the same port on the second SCSI-ENET Controller acts as initiator on the SCSI bus only in the event of a failure of the master SCSI-ENET Controller port. In FTX sys-tems, primary and secondary paths to duplexed disks are always split between the two SCSI-ENET Controllers. In VOS systems, primary paths to duplexed disks are always driven from the even-num-bered SCSI-ENET Controller and secondary paths are driven by the odd-numbered SCSI-ENET Con-troller.

This dual initiator configuration provides higher system availability, since the duplexed drives are not forced into a simplex condition in the event of a SCSI-ENET Controller failure.

Each SCSI bus has a single host module connected to it. This is referred to as a single host configura-tion. And, since only one SCSI-ENET Controller can access data from a set of disks/tapes on the SCSI bus, it is called a single access configuration.

The maximum number of D700 enclosures supported by a pair of SCSI-ENET Controllers in a dual initiator configuration in a VOS system is shown in Figure 16.


Figure 16. Maximum Dual Initiator Configuration (VOS)

The maximum number of D700 enclosures supported by a pair of SCSI-ENET Controllers in a dual initiator configuration in an FTX system is shown in Figure 17.

Figure 17. Maximum Dual Initiator Configuration (FTX)

SCSI-ENETController (Odd)

Primary path

Secondary path

SC Scorecard

s Secondary D700

SCSI-ENETController (Even)

3

2

1

4

p Primary D700

Duplexed Pairs

Term

Term

Term

Term

D700p D700s

D700p D700s

D700p D700sD700p D700sD700p D700s

D700p D700s

3

2

1

4 SC SC

SC SC

SC SC

SC SC

VOS System

SCSI-ENETController (Odd)

Primary path

Secondary path

SC Scorecard

s Secondary D700

SCSI-ENETController (Even)

3

2

1

4

p Primary D700

Duplexed Pairs

Term

Term

Term

Term

D700p D700s

D700p D700s

D700p D700sD700p D700sD700p D700s

D700p D700s

3

2

1

4 SC SC

SC SC

SC SC

SC SC

FTX System


Slots within a subsystem enclosure range from 0 to 6 (a triple-width slot), starting from the left-most slot (which always contains a power supply). If a second power supply is present, it occupies slot 1. Disk drives are added from left to right, occupying slots 1-6. If a tape drive is present, it is always in the right-most position (occupying slot 6). A second tape drive would occupy slots 3-5. The slots in the D700 Disk/Tape Subsystem are mechanically keyed in order to prevent bus addressing conflicts.

SCSI IDs range from 0 to 5 for the primary enclosure, and 8 to 13 for a secondary enclosure. For example, a disk drive in slot #1 has a SCSI ID of 0.

Valid maximum D700 daisy-chain configurations are shown in Figure 18.

Figure 18. D700 Daisy-chain Configurations

3.9.5 T403 Tape Drive

The T403 tape drive is available in two versions: 19-inch rack mount (housed in the E612 AC periph-eral expansion cabinet) and desktop. It features a 10-cartridge magazine and has a tape speed of 79 inches per second. Its data transfer rate is 3.0 MB per second.

The T403 tape drive utilizes a 68-pin SCSI connector for IO and termination.

3.9.6 T204 Tape Drive

Like the T403, the T204 is available in two versions: rack mount (housed in the E612 AC peripheral expansion cabinet) and desktop. It uses a differential SCSI interface and standard 50-pin amphenal connector for IO and termination. It requires a unique SCSI ID to be set via the user interface.

The T204 has a nominal tape speed of 125 inches per second. Its data capacity is 154 MB (GCR)/42 MB (PE) and data transfer rate is 769 KB per second (GCR) and 208 KB per second (PE).

SCSI-

Cntrlr.

SCSI ID = 7

210

SCSI ID = 6

PSENET

0 1 2 3 4 5 6Slot # = SCSI ID = --

TERMDISK

DISK

DISK

DISK

DISK

DISK

3 4 5

1098

PS

0 1 2 3 4 5 6Slot # = SCSI ID = --

DISK

DISK

DISK

DISK

DISK

DISK

11 12 13

SCSI-

Cntrlr.

SCSI ID = 7

210

SCSI ID = 6

PSENET

0 1 2 3 4 5Slot # = SCSI ID = --

DISK

DISK

DISK

DISK

DISK

3 4

SCSI-

Cntrlr.

SCSI ID = 7

210

SCSI ID = 6

PSENET

0 1 2Slot # = SCSI ID = --

DISK

DISK

5

T204/T403Tape Drive

T204/T403Tape Drive

5SCSI ID =

SCSI ID =

Tape

3 4 5


4. Fault Isolation

The isolation of Continuum Series 600 and 1200 hardware system failures is accomplished through the use of LEDs, error messages, log files, and flowcharts. When a failure occurs the Remote Service Net-work (RSN) reports the error back to Stratus and a replacement part is shipped. The customer typically replaces Customer Removable Units (CRUs), while an authorized service provider replaces the Field Replaceable Units (FRUs).

The troubleshooting procedures in this chapter provide and overview of the process you should follow when troubleshooting continuum systems. You have several methods to check the machine’s status, they are:

• LEDs

• System Logs

• Isolating Memory Faults

• Software Commands

• Troubleshooting Procedures

4.1 LEDs

The Continuum series system use LEDs to report CRU/FRU status. The following sections describe the various LED codes for cabinets and system components.

4.1.1 Cabinet LEDs

The cabinet LEDs are located in the alarm display panel at the top of each cabinet. The Central Elec-tronics Cabinet (CEC) has three LEDs while the expansion cabinets have only one. The LEDs are shown in Figure 19.

Figure 19. Cabinet LEDs

Table 4 provides an explanation of each LED.

1051

System Cabinet No CabinetFault Fault Fault Fault

CEC Cabinet Expansion Cabinet


Table 4. Cabinet LED Definitions

During normal operation, the NO FAULT LED is lit on the CEC and all other cabinet LEDs are off. When a hardware error occurs, the CEC’s SYSTEM FAULT LED is lit, the NO FAULT LED goes out, and the CABINET FAULT LED on the cabinet that houses the failed component is also lit.

4.1.2 CRU/FRU LEDs

The continuum series 600 and 1200 systems use LEDs to report system and CRU/FRU status. The LED codes for the boards, disks, and various power components are listed on a label located inside the cabinet’s front door. (See Figure 20.) This label may be used as a quick reference to determine the sta-tus of various CRUs and FRUs.

LED Color Definition

SYSTEM FAULT Amber There is a component that has failed in the system.CABINET FAULT Amber There is a component that has failed in this cabinet.NO FAULT Green The system is operating normally.


Figure 20. LED Label

For a more detailed explanation of the LED status codes for the various components in the system see the subsections that follow.

4.1.2.1 Board LEDs

The CEC houses boards that use three LEDs to indicate status. Figure 21 shows the CEC board LED status codes.

SCSI-ENET Slot

LED LEGENDS

FaultRunningNo Fault

Two LEDS

ADDITIONAL DISK INFORMATION

SCSI-ENET Slot

Enclosure Daisy Chain #

SCSI-ENET Port

SCSI-ENETConfiguration:

LCD LegendDisk Power Supply

Three LEDS (Boards)

Three LEDS (Disks)

Fault

Fault

Running(Duplexed)

Ready(Duplexed)

Do NOT Pull(Simplexed)


Testing

(Blinking)Inserted NOT Ready

(Blinking)NOT Configured

Partially BrokenOK to Pull

Partially BrokenDo NOT Pull

Disk ChassisSlot Numbering

6Slots 0 1 2 3 4 5

(RED)

(GREEN)

(RED)

(GREEN)

(YELLOW)

(RED)

(GREEN)

(YELLOW)

PowerSupply

(FTX)

SCSI-ENET Port Enclosure Daisy Chain #Enclosure Slot #(VOS)


Figure 21. Board LED Codes

The LED codes are as follows:

• Fault - (OK to Pull) When a board has been remove from service by the operating system. The board is broken and it’s partner is usually displaying Simplexed status).

• Running (Duplexed) - When a board is fully functional and is partnered.

• Do NOT Pull (Simplexed) - When a board is fully functional but is not partnered.

• Testing - Occurs upon power up or when a board is hot-plugged into a system.

• NOT Configured (Blinking LED) - When a replacement board doesn’t have a compatible prom revision with its partner.

• Partially Broken OK to Pull - When a SCSI-ENET board has a port that has failed. The failed port goes bad, the data transfers fail over to the partner SCSI-ENET board.

• Partially Broken Do NOT Pull - When a SCSI-ENET board has a port failure but is still function-ing on other ports.

4.1.2.2 Disk/Tape Power Component LEDs

The SCSI devices (disk/tape), AC Power Controller (ACPC), and IOA bulk power supplies use three LEDs to indicate status. Figure 22 shows the LEDs and codes.

Figure 22. Disk/Tape/Power Component LEDs

The LED codes are as follows:

• Fault - (OK to Pull) The component has failed or is not in service.

• Ready (Duplexed) - The component is duplexed and in normal operating mode.

• Do NOT Pull (Simplexed) - The component is simplexed and in normal operating mode.

• Inserted NOT Ready - (disk/tape specific status) The device is waiting to be configured and mounted by the operating system.

Three LEDS (Boards)

Fault Running

(Duplexed)Do NOT Pull(Simplexed)

Testing (Blinking)

NOT ConfiguredPartially Broken

OK to PullPartially BrokenDo NOT Pull

(RED)

(GREEN)

(YELLOW)

Three LEDS (Disks/Power Components)

Fault Ready(Duplexed)


(Blinking)Inserted NOT Ready

(RED)

(GREEN)

(YELLOW)


4.1.2.3 Disk/Tape Power Supply

Each disk/tape chassis houses power supplies which have two LEDs and an LCD to show status. The LED status codes are the same as those shown in Section 4.1.2.4. The LCD, shown in Figure 23, dis-plays configuration information.

Figure 23. Disk/Tape Chassis Power Supply LCD Codes

The LCD codes display the controller slot number information as well as port and daisy chain numbers (SCSI-ENET controller).

4.1.2.4 Two Position LEDs

A number of components in the continuum system have two (Red and Green) LEDs. The Red LED represents a Fault condition and the Green LED represents a Running No Fault condition. (See Figure 24.)

Figure 24. Two Position LEDs

The following components use two LEDs:

• Fans

• Cabinet Data Collector (CDC)

• Clock Card

• Disk/Tape power supply

• Power Supply Unit (PSU)

• Power Control Unit (PCU)

• Battery Fuse Unit (BFU)

Communication LED

A single green LED is used on the PSU and BFU. This is the communication LED which in normal operating mode stays on. When a communication fault occurs (usually caused by a bad or missing fiber optic cable) this green LED will flash along with the “running no fault” LED on the PSUs and

SCSI-ENET Slot Enclosure Daisy Chain #

SCSI-ENET Port

SCSI-ENETConfiguration

LCD LegendDisk Power Supply

(FTX)

SCSI-ENET Port Enclosure Daisy Chain #Enclosure Slot #(VOS)

SCSI-ENET Slot

FaultRunningNo Fault

Two LEDS

(RED)

(GREEN)


BFUs. Under a communication fault, the power component will continue to function normally.

Figure 25 shows the communication LEDs on the PSU and BFU.

Figure 25. Communication LEDs

4.1.2.5 Battery Fault LED

Each battery drawer has a single red LED which stays illuminated when fault occurs. (See Figure 26.) A fault condition would be when the battery temperature is greater than 60° C (140° F) or when the battery voltage level drops below -44 V DC after the battery has been disconnected.

1053

Communication(green)

Front View

Rear View

(PSU)

(BFU)


Figure 26. Battery Drawer LED

4.2 System Logs

System logs contain information concerning major system events and the time they occurred which can help you detect and evaluate system problems. This section includes information for both VOS and FTX system logs.

4.2.1 VOS Error Logs

All Stratus modules with VOS operating systems contain system log files in the >system directory. The system log files are the syerr_log .date and hardware_log .date . These files contain infor-mation concerning system events which may help you to detect and evaluate system problems.

The Overseer program creates these files while VOS maintains them for each operation day of the module. These files may be accessed directly or through the VOS analyze_system request dump_syserr . Refer to the analyze_system request later in this chapter for more information on the dump_syserr request.

4.2.1.1 syserr_log.date File

The syserr_log .date file provides information concerning the major system events and the time they occurred. These events include the following:

• Overseer processes (log-in processes, batch facility, broadcast_file command, and module shutdown)

• Communications status

• Hardware errors

1052

Rear View

Error (red)


To examine a syserr_log .date file, enter

display syserr_log. date

NOTE: When accessing a log, the date is entered in the format, yy-mm-dd .

The following is a partial listing of syserr_log . date file.

09:45:20 recc_callback: ReCC channel 0 is down.09:45:20 recc_register_broken:recc channel is broken.09:45:21 recc 002i 36 563 xx 00000000 00000000 removed from service09:45:21 recc 002i 37 560 xx 00000000 00000000 adding online09:45:22 recc_board_up: recc is up and running.09:45:23 recc_advance_config_state: configure ReCC channel 0 is queued.09:45:23 recc_callback: ReCC channel 0 is configured.09:45:23 Process 29018029, PreLogin.System (oc1), terminated.

4.2.1.2 Hardware_log .date File

The hardware_log .date file contains only the daily hardware status and failures which are also con-tained in the syserr_log .date file. If no hardware errors occur on a given day, a hardware_log .date file is not created for that day.

The following is a partial listing of a hardare_log .date file. The field designations in this example are used as a reference and do not appear in the actual file. See Table 5 for a description of the fields.

Time Type aab/S1 Slot S2 S3 Status Address Message14:35:34 cpu 1802i 00 752 00 00000000 00000000 second cpu in service14:35:35 bio 0002i 04 348 00 00000000 00000000 testing14:35:57 bio 0002i 04 348 00 00000000 00000000 adding14:35:57 bio 0002n 04 348 00 00000000 00000000 restored to service14:36:03 disk 0300i 04/01/01/02 0 00000000 00000000 sequence drive up14:36:03 disk 0300i 04/02/01/01 0 00000000 00000000 sequence drive up14:36:03 disk 0300i 04/02/01/02 0 00000000 00000000 sequence drive up14:36:03 tape 2202i 04/01/01/06 0 00000000 00000000 restored to service14:36:04 disk 2202i 04/01/01/01 EEEEE 00000000 00000000 restored to service14:36:14 disk 2202i 04/01/01/02 EEEEE 00000000 00000000 restored to service14:36:16 disk 2202i 04/02/01/02 EEEEE 000000000 00000000 restored to service14:36:16 disk 2202i 04/02/01/01 EEEEE 000000000 00000000 restored to service

Table 5. Description of hardware_log Fields

Field Description

Time Time the problem occurred.Type Designates the type of board having the detected problem; CPU, disk, and Comm are examples.aa Indicates the reference for the specific text in the message field.bb Identifies the source that detected the error:

00 VOS device driver 01 Maintenance Process 02 Diagnostic Process Device Code 03 Diagnostic Process General Code

S1 Provides a code that indicates the severity of the message fieldCode Definitioni or blank space informationalr recoverablen nonrecoverablef fatal


4.2.2 FTX

The elgpost command is used to read daily error messages from the /etc/errlog file. To examine today’s error log, enter the following:

/etc/elgpost <RETURN>

To examine the error log for another day, enter the following:

/etc/elgpost -f /etc/errlog. date <RETURN>

NOTE: The date is entered in the yymmdd format.

The following is a partial listing of a /etc/errlog .date file. The field designations in this example are used as a reference and do not necessarily appear in the error log. The following is an example of the error log resulting form a IO processor board being removed and replaced.

# hwmaint del 10Feb 23 13:56:48.71 [FTS,cpu0] k600 10 IOP board deletedFeb 23 13:56:48.71 [FTS,cpu0] k600 10 Paired board brokeFeb 23 13:57:08.76 [FTS,cpu1] k600 10 board insertedFeb 23 13:57:08.76 [IDP,cpu1] 10: IDprom object 5 converted to FTXFeb 23 13:57:08.76 [IDP,cpu1] 10: Bad IDprom object 5 crc 0x54a7Feb 23 13:57:08.96 [IDP,cpu1] k600 10 IOP board identifiedFeb 23 13:57:08.96 [IDP,cpu1] k600 10 IOP board failure: Slot ReservedFeb 23 13:57:19.64 [CAB,cpu1] cab cab 00 Central Equipment Cabinet FaultFeb 23 13:57:19.64 [CAB,cpu1] cab cab 00 Central Fault On

# hwmaint add 10

hwmaint: 10 bringup failed: Broken# Feb 23 13:57:49.31 [FTS, cpu1] k600 10 IOP board bringup initiatedFeb 23 13:58:07.86 [FTS, cpu1] k600 10 IOP board all tests passedFeb 23 13:58:07.86 [FTS, cpu1] k600 10 IOP board partnering initiatedFeb 23 13:58:09.88 [FTS, cpu1] k600 10 IOP board partnering complete

4.2.3 Software Commands

The Continuum systems use software commands to display system configuration. The most common commands list the boards in the system and identify what components have been removed from ser-vice. The board list serves as a simple troubleshooting tool to verify that all the components are present and their status (in/out of service). The sections that follow describe how to list the system configura-tion in both VOS and FTX.

Slot Indicates the slot number where the faulty controller is locatedS2 Indicates the serial number of the faulty deviceS3 Indicates the sub-device number for disk drives or the subchannel number for communications line

adapter cards when there is more than one device of the same type on the moduleStatus When applicable, indicates the operation that the device was performing when the error occurredAddress When applicable, indicates the address fault locationMessage Defines the error type. the aabb field references the text for the message

Field Description


4.2.4 VOS (list_boards)

The list_boards command is in the analyze_system subsystem under VOS. To enter the analyze_system subsystem, type:

analyze_system <RETURN>

Your terminal displays:

VOS Release XX.XX, analyze_system Release XX.XX, Current process is XXX, ptep XXXX, user_nameas:

At the as: prompt enter:

as: list_boards


Module %es#m13 (12 Slot Chassis, Model xxxx) Id Prom ------Fault Data------ Slot Board Type Model Serial Rev Rev Cnt Code Last Fault Time 0 CPU-Memory G74500 99 29 23 0 1 CPU-Memory G74500 97 25 23 0 4 SCSI-ENET Controller K45000 95 04 02 0 1 SCSI Port SCSI00 **** *** 0 1 Device Enclosure ENCL00 *** *** 1 1.05 GB SCSI Disk D70100 9999 0 0 2 1.9 GB SCSI Disk D70200 9999 0 0 2 Device Enclosure ENCL00 *** *** 1 1.05 GB SCSI Disk D70100 9999 0 0 2 1.9 GB SCSI Disk D70200 9999 0 0

If a board is out of service, it appears highlighted in the list. At this point, you can enter requests. To exit the analyze_system subsystem, type:

quit <RETURN>

Refer to the Customer Service Analyze System Pocket Guide (HP-015070) or the VOS System Analysis Manual (R073) for more information on analyze_system and the various requests.

4.2.5 FTX (Hwmaint ls)

In FTX the ls command is used to list the system configuration. To list the configuration, type:

Hwmaint ls <RETURN>




- Continuum Chassis- GBus- GBusA- GBusB



k45000 SCSI/Ethernet Cont onln - --- 245 2700.00 4SCSI port 0 onln - --- 4 1

d701 1GB Disk Driv onln - --- 084297 - - 4 1 1 1 0d702 2GB Disk Driv onln - --- 972298 - - 4 1 1 2 0

SCSI port 1 onln - --- 4 2d701 1GB Disk Driv onln - --- 042347 - - 4 2 1 1 0d702 2GB Disk Driv onln - --- 961432 - - 4 2 1 2 0

If a component is not functioning properly, an out of service code is displayed in the code field. The out-of-service code is repeated at the bottom of the display with a short description of the prob-lem.

4.3 Isolating Memory Faults

This section describes how to decode memory ECC error messages and identify which memory mod-ule on a CPU-Memory board has failed.

4.3.1 FTX

Memory modules are mapped into the address space starting as base address 0 or base address 2GB (in a Continuum 1245 remote board) - ie. 0x00000000 or 0x80000000.

A given CPU-Memory board is either populated with 128-MB (M702) or 512-MB (M713) memory modules. The following tables indicate the mapping of memory modules to physical locations on the CPU-Memory board.

128-MB memory module identification for base address 0x00000000

128-MB memory module identification for base address 0x80000000

Memory Module # Address Range Physical Location on CPU-Memory Board

0 0x00000000-0x07FFFFFF J8/J91 0x08000000-0x0FFFFFFF J12/132 0x10000000-0x17FFFFFF J10/J113 0x18000000-0x1FFFFFFF J14/J15


0 0x80000000-0x87FFFFFF J8/J91 0x88000000-0x8FFFFFFF J12/132 0x90000000-0x97FFFFFF J10/J113 0x98000000-0x9FFFFFFF J14/J15


512-MB Memory Module identification for Base address 0x00000000

512-MB Memory Module identification for Base address 0x80000000

NOTE: Note: only 3 modules are present in a Continuum 1245 Remote CPU Board.

The following is a sample output from the elgpost -f command indicating a memory module fail-ure on a Continuum 1245 system with 128-MB memory modules running FTX 3.2.

Sample Command:

# elgpost -f errlog.961030 | grep -i ecc

Sample Output:

Oct 30 16:29:36.21 [FTS:I FTS_ECC_ERR ,cpu1] g748 03 CPU board single bit ecc error at 0x1e4f7a50 syndrome 0x1fOct 30 16:33:52.34 [FTS:I FTS_ECC_ERR ,cpu1] g748 03 CPU board single bit ecc error at 0x1e4f7a50 syndrome 0x1fOct 30 16:38:08.29 [FTS:I FTS_ECC_ERR ,cpu1] g748 03 CPU board single bit ecc error at 0x1e4f7a50 syndrome 0x1fOct 30 16:42:24.25 [FTS:I FTS_ECC_ERR ,cpu1] g748 03 CPU board single bit ecc error at 0x1e4f7a50 syndrome 0x1fOct 30 16:46:40.21 [FTS:I FTS_ECC_ERR ,cpu0] g748 03 CPU board single bit ecc error at 0x1e4f7a50 syndrome 0x1f

The errors at location 0x1e4f7a50 indicate a failure on memory module 3 since the address is between 0x18000000 and 0x1FFFFFFF .

4.4 Troubleshooting

When a fault occurs several things can happen. If it is a non-critical fault, the system will continued to process data. If it is a critical fault, the system (or a subsystem) may be inoperative. Whenever you troubleshoot the system you should always determine the fault first by using the LEDs and screen mes-sages. Then, you should verify that the component(s) are out of service using software commands. This flow is shown in shown in Figure 27.


0 0x00000000-0x1FFFFFFF J8/J91 0x20000000-0x3FFFFFFF J12/132 0x40000000-0x5FFFFFFF J10/J113 0x60000000-0x7FFFFFFF J14/J15


0 0x80000000-0x9FFFFFFF J8/J91 0xA0000000-0xBFFFFFFF J12/132 0xC0000000-0xDFFFFFFF J10/J11


Figure 27. Troubleshooting Flow

When troubleshooting system faults, use the following process:

• Check the cabinet LEDs to locate the cabinet housing the failed component.

• Check the overseer terminal for fault information.

• Locate the failed component(s) using the LEDs.

• Verify the component is bad by using software commands/error logs. (If this fails try using the flow charts.)

• Remove and replace the failed component.

• Check to make sure the problem is resolved.

4.4.1 Non-Critical Fault (System Operational)

A non-critical fault is when there is a fault of bad component in the system, but the system is still func-tioning. Some components, especially boards may have a transient or hard failure. A transient failure is a temporary hardware failure that causes the board’s red light to illuminate, but the board or software corrects the failure. It does not place the board out of service unless the error count occurring on the board is very high. Inspect the hardware_log .date file (VOS) or elgpost file (FTX) for transient failures. Analyze the type and frequency of the failure to determine if board replacement is necessary.

Hard failures cause the red LED to light on the failed board to remain On, and the board cannot be restored to service. Replace boards experiencing a hard failure after verifying that the board is config-ured in the module’s .tin file. If necessary, add the board to the module configuration in the .tin file. For more information about the .tin file, refer to the VOS System Administrator’s Guide (R012).

If after following troubleshooting process, the problem is not repaired, go to Section 4.4.3.

4.4.2 Critical Fault (System not Operational)

A critical fault is when the system is partially or totally inoperable. To isolate a critical system prob-lem, use the same troubleshooting procedure described in Section 4.4. If you are unable to use software commands or read error logs, you should use the troubleshooting flowcharts. (See Section 4.4.3.)

LEDs

Screen Messages

Software Commands

Error Logs

(Initial Check)

(Verification)

(Error/Status History)


If you’re unable to isolate and repair the system, call your Customer Assistance Center (CAC).

4.4.3 Troubleshooting Flowcharts

This section provide a series of troubleshooting flowcharts that you should follow if you’re unable to repair the system using the LEDs, error messages, and system logs. Each list provides a series of checks designed to help isolate the system fault. If you’re unable to isolate and repair the system, call your Customer Assistance Center (CAC).

The flowcharts provide general things to look for. There are Illustrated Parts Breakdowns (IPBs) in Chapter 6 and system level interconnection diagrams in Appendix A which will help when trouble-shooting the system.

Table 6 list the troubleshooting flowcharts.

Table 6. Troubleshooting Flowcharts

Figure Number Flowchart Title/Symptom

Figure 28 System Will Not Power UpFigure 29 System Will Not Power DownFigure 30 System Will Not Auto BootFigure 4-13 System Will Not Manual BootFigure 32 Expansion Cabinet(s) Fails to Power OnFigure 33 Individual Peripheral Fails to Power OnFigure 34 Module Does Not Recover from a Power Failure


Figure 28. System Will Not Power Up

Start

Are the GreenLEDs on the console

controller On?

Call the CAC.

Check/Replace the

Does the problem still

Return the module

N

YAre the Green

LEDs on the ACPCs or

Check/Replace:1. ACPCs or

DC power controllersOn?

Y

No power present. ACPC or DC powercontroller LEDs are

not lit.

2. DC Power Controllers

N

Check/Replace:1. CEC Sequencer

Y

N

Check:1. Main Circuit

2. ACPC Breakers3. DC Breakers

Breakers

to service.

exist?

sequencer cables

2. Console Controllers Cables


Figure 29. System Will Not Power Down

Start

Return the moduleDoes theproblem still

Call the CAC.

N

Y

Install thesequencer cables.

Are all thesequencer cables

(PrevA,B,C / NextA, B,C)present?

Y

N

Is the BatteryFuse Unit’s (BFU) Green

or Red LED On?

Make sure the BFUis inserted properly.N

Y

Replace the BFU if itis inserted properly.

1. Remove the BFUand/or Batteries andshutdown the system.

2. Replace the BFU.

exist?

System fails to powerdown after issuing the

power_off command.

to service.


Figure 30. System Will Not Auto Boot

Start

Refer to the System Will Not Power Up

Flowchart.(See Figure 4-11.)

Are the

Check:

2. Console:

Doesboot_auto find

boot disk?

Check:1. Console Controller

Call the CAC.

Is systempower On?

Do thedisk drivesspin up?

Return the moduleto service.

N

N

N

Y

Y

Y

N

green LEDson the console

controllerslit?

Check/Replace 1. Sequencer Cables

Check/Replace:1. D700 Circuit Breaker2. D700 Power Supply3. Disk Drive(s)

1. Terminal Setup*

* Terminal Setup:Baud Rate: 9600Data/Parity: 7/oddStop Bits: 1

Terminal CableAW-000152

2. Console Controllers

Check/Replace the

Does the terminal enter

console mode?

4. SCSI-ENET boards5. Score cards6. SCSI disk cabling

Cable/Connection

boot path.2. CPUs

Does the systemboot?

N

N

Y

Y

Y

Sequencer Cables


Figure 31. System Will Not Manual Boot

Start

Refer to the System Will Not Power Up

Flowchart.(See Figure 4-11.)

Are the

Check:

2. Console:

Doesboot_manual

return a prom: Check CPUs

Call the CAC.

Is systempower On?

Do thedisk drivesspin up?

Return the moduleto service.

N

N

N

Y

Y

Y

N

green LEDson the console

controllerslit?

Check/Replace 1. Sequencer Cables

Check/Replace:1. D700 Circuit Breaker2. D700 Power Supply3. Disk Drive(s)

1. Terminal Setup*

* Terminal Setup:Baud Rate: 9600Data/Parity: 7/oddStop Bits: 1

Terminal CableAW-000152

2. Console Controllers

Check/Replace the

Does the terminal enter

console mode?

4. SCSI-ENET boards5. Score cards6. SCSI disk cabling

Cable/Connection

Does the systemboot?

N

N

Y

Y

Y

Sequencer Cables

prompt?

Type:boot S P E D

(See Note)

Note:

S = SCSI-ENET Slot NumberP = SCSI-ENET Port NumberE = Disk Enclosure

D = Disk Location

A

A


Figure 32. Expansion Cabinet Fails to Power On

Y

Is there sourcevoltage to the expansion

cabinet(s)?

Check/Verify:1. Presence of power at the cabinet.2. All circuit breakers are in the On position and the LEDs are On.3. Previous cabinet (relative to sequencer cables)

4. Ensure the sequencercables are connected

to the AC/DC power systems.

Ensure all circuit breakersare turned on. If there isa problem with the site’s

source voltage, it should beresolved by the customer.

Ensure the sequencercables are connected to

the AC/DC power systems.

Is this an ACPC or DC

power controllerreplacement?

Ensure the component is installed correctly

and the thumb screwsare tightened securely.

Disconnect the sequencercables from the suspect

cabinet. Check the cable(s)with an Ohm meter.

(The cable is wired Pins 1 to 1, 2 to 2, etc.)

Is there a problem with the

sequencer

Replace the power control

backplane.

Return the module to service.

Does the problem

still exist?

Y

Y

N

N

is On.

N

Replace the sequencer cable(s).

N

Is this a newInstallation?

Y

Call the CAC.

Start

Y

N

cables?


Figure 33. Individual Peripheral Fails to Power On

Start


Does the problem

still exist?

Is theperipheral’s power

cord connected and power tap circuit

breaker On?

Plug in the power cordor place the power tapcircuit breaker in the

On position.

Unplug the peripheral’spower cord (remote device) or power tap circuit breaker

cable. With a DVM verify

Check/replace:power tap circuit breaker

Is power present?

Call the CAC.

N

Y

Y

the presence of power.

Problem lies with peripheral(check fuse) or with

cabinet power (check

N

D700 power supply).

power cord (external device)

N

Y


Figure 34. Module Does Not Recover from a Power Failure

Start

Replace the

Replace the batteries.

N

Y

Be sure there are no hardwareor software revisions

incompatibilities caused bythe installation of replacementboards or the installation of a

new software release.

Check the battery status in theAC/DC power system(s). Thebattery fuse unit’s Green LEDshould be constantly On. TheLEDs on the battery drawers

should be Off.

Is the batteryfuse unit’s GreenLED constantly

On? Battery Fuse Unit.

Are the redLEDs on the battery

drawers On?

Ensure that theexternal battery supplied by the

customer isfunctioning properly.

Call the CAC.Does the

problem stillexist?


N

Y

N

Is theresource voltage to

all cabinets?

Ensure all circuitbreakers are turned on.

If there is a problemwith the site’s sourcevoltage, it should be

N

resolved by thecustomer.

Y

Y


5. Removal and Replacement

This chapter provides removal and replacement information for the system's replaceable parts. This informa-tion is written for Stratus trained service personnel who install and maintain Stratus Systems.

NOTE: When performing removal and replacement procedures, use care when installing or reinstalling screws and covers to maintain FCC compliance.

5.1 Overview

This chapter provides instructions on how to remove and replace both Customer Replaceable Units (CRUs) and Field Replaceable Units (FRUs). Both CRU and FRU information is provided for field engineers to have a complete understanding of all replaceable components. Throughout this chapter we refer to FRUs and CRUs as “FRUs”; when necessary we will make the distinction between FRU and CRU. For a complete list of FRUs and an illustrated parts breakdown of all the system cabinets, refer to Chapter 6.

When performing removal and replacement procedures be sure to take the necessary steps when handling system components. For example, keep all components in their shipping containers and antistatic bags until you are ready to perform the repair procedures. Be sure to return the defective parts to Stratus using the shipping materials from the replacement part.

Other than the standard tool kit (part number TL-STRATUS-3), there are no special tools required to perform removal and replacement procedures.

5.2 Replacing Components

When replacing components you should always use the software to verify suspected failures before performing removal and replacement procedures. The repair procedures provide a step-by-step removal process and instruct the readers to simply reverse the procedure to replace the component. It is understood that when replacing components, the steps are not only reversed, but certain functions are as well (e.g. power On versus power Off).

5.3 Accessing Replaceable Components

The system has several doors and access panels that must be removed to access failing FRUs. During the removal and replacement procedure you may be instructed to open/remove one or more doors or panels. This section provides an overview of the doors and panels in the system.

5.3.1 Front Door

To open and remove the cabinet’s front door, see Figure 35 and perform the following procedure:


Figure 35. Opening and Removing the Front Cabinet Door

1. Unlock the door.

2. Pull up on the latch then turn it 90 degrees to open the door.

NOTE: If you plan to remove the door, you must disconnect the ground strap.

3. Once opened you may lift the door off its hinge pins.

To replace the door, see Figure 35 and reverse the preceding steps.

5.3.2 Front Door Frame

The front door is mounted to a two-piece (top & bottom) door frame. To remove and replace the front door frame, see Figure 36 and perform the following procedure:

99


Figure 36. Front Door Frame Removal and Replacement

1. Unlock and open the cabinet’s front door. (See Section 5.3.1.)

2. Remove the cabinet door from the door frame.

3. Remove the Phillips screw on the door frame (top or bottom) and lift up and out to remove it from the cabinet.

To replace the front door frame, see Figure 36 and reverse the preceding steps.

5.3.3 Rear Access Panel

To remove the cabinet’s rear access panel, see Figure 37 and perform the following procedure:

92

Screw

Door Frame

Screw


Figure 37. Removing the Cabinet’s Rear Access Panel

1. Unlock the rear access panel latches by turning the knobs counterclockwise.

2. Remove the access panel by grasping the top and bottom of the door (3/4 door) or door han-dles (full door) and lifting the door slightly upward while pulling it away from the cabinet. Note that the alignment pins have edges which must clear the alignment holes to remove the door.

3. When removing the access panel to perform maintenance procedures with power on, press the fan switch on the Cabinet Data Collector (CDC) to increase air flow. Upon completion of the procedure, press the switch again to return the fans to normal speed before replacing the panel.

When replacing the rear access panel, align the pins with the alignment holes in the cabinet rails. Turn the latches 1/4 turn clockwise to engage them to the cabinet and then tighten the latches until snug.

CAUTION: Do not over tighten the latches. Overtightening may crease the rear panel.

91

Knobs (4)

Rear Access Panel


5.3.4 Side Panels

To remove the side panels, see Figure 38 and perform the following procedure:

Figure 38. Removing Cabinet Side Panels

1. Unlock and open the cabinet’s front door and remove the rear access panel and top cap. (See Section 5.3 and Section 5.6.4.)

2. Using a 9/16-inch socket wrench, unlatch the cabinet side panels by turning the six camlocs counterclockwise.

3. Lift the side panel up and out.

To replace the cabinet side panels, see Figure 38 and reverse the preceding steps. Note that there is a lip on the side panel which properly aligns the side panel to the cabinet.

90

Camlocs

Side PanelRear Access Panel

Top Cap

Lip


5.4 Power Subsystem

It is Stratus’ policy to maintain continuous transaction processing even during FRU removal and replacement. Most of the system FRUs may be serviced without powering down the module. However, the cabinet must be powered down to service the following FRUs.

• Central Electronics Cabinet (CEC) card cage

• Fan backplane

• CEC backplane

• Clock card

• DC power controller backplane


• AC/DC power system

• Chassis

If power must be removed to perform repair procedures, it is only necessary to remove power from the cabinet(s) that house the failed component(s). This section provides procedures for removing power from individual cabinets within the system. For information on how to shutdown the entire system and remove power, refer to Chapter 2. Refer to the following subsections to remove power from individual cabinets (AC and DC).

5.4.1 AC Systems

To remove power from an AC/DC power system see Figure 39 and perform the following procedure:

Figure 39. Removing Power from the AC/DC Power System

96

ACPC Circuit Breaker

Power Sequencing Cables (NextA, B, & C)

Power Sequencing Cables (PrevA, B, & C)

Battery Drawer


1. Notify the system administrator that power will be removed from this cabinet. If this cabinet is critical to system operation (e.g. CEC), shut down the system. Refer to Chapter 2 for shut-down procedures.

NOTE: To maintain Start, Stop, and powerfail functionality on cabinets downline from the one being serviced, disconnect the respective “Prev” and “Next” cables and connect them together during the service operation. The cabinet being serviced and the next cabinet down-line may report errors as these cables are disconnected from the power system.

2. Disconnect the power sequencing cables labelled NextA and PrevA from the power system and connect them together. Repeat this step for the remaining sequencer cables (NextB/PrevB and NextC/PrevC).

NOTE: If the system is not equipped with (optional) batteries, go to Step 4.

3. Loosen the two thumb-screws on the battery drawer and pull the drawer out approximately four inches to disconnect the battery backup from the power system.

4. Place the circuit breakers on both ACPCs in the OFF position.

5. Disconnect the AC power cords.

WARNING: To prevent personal injury and possible equipment damage, ensure that the cir-cuit breakers are in the OFF position and the AC power cords are disconnected.

Once the repairs are completed, restore power by reversing the preceding steps and following the procedures in Chapter 2. Once the system is powered up, verify that the system is functioning properly according the procedures in Section 5.5.


5.4.2 DC Systems

To remove power from the CEC / expansion cabinet, see Figure 40 and perform the following procedure:

Figure 40. Removing Power from the CEC / Expansion Cabinet (DC Systems)

1. Notify the system administrator that power will be removed from this cabinet. If this cabinet is critical to system operation (e.g. CEC), shut down the system. Refer to Chapter 2 for shut down procedures.


3. Place both DC power controller circuit breakers in the Off position.

4. Loosen the captive screws on each controller.

5. Pull both DC power controllers out approximately four inches (enough to disengage the con-nector from the power cables).

WARNING: To prevent personal injury and possible equipment damage, ensure that the DC power controller’s circuit breakers are in the Off position and the DC power controllers are disengaged from their backplane connectors.

6. At this point, power is removed from the cabinet’s power bus. If you want to totally remove power from the cabinet, you have to remove the cabinet’s rear access panel and disconnect the DC power cords. (See Section 5.6.8.1.)

1036

Locking Pin

Circuit Breaker

Captive Screw (2)


Once the repairs are completed, restore power by reversing the preceding steps and following the procedures in Chapter 2. Once the system is powered up, verify that the system is functioning properly according the procedures in Section 5.5.

5.5 System Verification

System operation must be verified before and after you remove and replace a component. This section provides verification information for both FTX and VOS operating systems. Many of the FRUs have status lights which give you an indication of their status. However, it is always best to verify system operation as shown in the fol-lowing subsections.

5.5.1 System Verification (VOS)

To verify system operation, perform the following procedure:

NOTE: Chapter 2 provides a more detailed explanation of this procedure with examples of actual screen displays.

1. At the READY prompt, enter the following command to check the status of the controller boards, buses, fans, and power system:

analyze_system -request line_list_boards -quit <RETURN>

2. At the READY prompt, enter the following command to check the status of the disks:

display_disk_info -long <RETURN>


5.5.2 System Verification (FTX)

To verify system operation, perform the following procedure:

NOTE: Chapter 2 provides a more detailed explanation of this procedure with examples of actual screen displays.

1. At the prompt, enter the following command to check the status of the controller boards, buses, and power supply.

/sbin/hwmaint |more -ls <RETURN>

2. To check the virtual disk status, enter the following command:

/sbin/vdskconf |more -L <RETURN>



5.6 Cabinets

This section describes the removal and replacement procedures for FRUs which are common to all cabinets in the system. Unless otherwise noted, all FRUs described in this section are common to both AC and DC sys-tems. This section provides removal and replacement procedure for the following:

• Cabinet cooling

• Air filter

• Air filter sensor switch (DC systems only)

• Cabinet top cap

• Alarm display panel

• DC power controller (DC systems only)

• DC power controller backplane (DC systems only)

• Power cords

• Power tap circuit breaker

5.6.1 Cabinet Cooling

The cabinets are cooled using fans. There are six fans located at the top of each cabinet. The fan FRUs are:

• Fan assembly

• Cabinet Data Collector (CDC)

• Fan backplane

• Fan chassis

The following subsections provide removal and replacement procedures.

5.6.1.1 Fan Assembly

To remove a fan assembly, see Figure 41 and perform the following procedure:


Figure 41. Fan Removal and Replacement

1. Unlock and open the cabinet's front door. (See Section 5.3.1.)

2. Loosen the thumbscrew (counterclockwise) on the fan assembly.

CAUTION: To prevent physical injury support the fan assembly while removing it from the cabinet in Step 3.

3. Grasp the fan’s handle and slide it all the way out of the cabinet.

To replace the fan, see Figure 41 and reverse the preceding steps.

5.6.1.2 Cabinet Data Collector (CDC)

To remove the CDC, see Figure 42 and perform the following procedure:

88

Fan Assembly

Thumbscrew


Figure 42. CDC Removal and Replacement

CAUTION: Use anti-static precautions when performing this procedure.

1. Remove the cabinet’s rear access panel. (See Section 5.3.3.)

2. Remove the four Phillips-screws and washers from the control board’s EMI shield and remove the EMI shield.

CAUTION: To prevent damaging connector pins, pull the CDC board straight off the con-nector in Step 3.

3. Remove the four Phillips screws and washers. Remove the CDC board.

To replace the CDC, see Figure 42 and reverse the preceding steps.

5.6.1.3 Fan Backplane

To replace the fan backplane, see Figure 43 and perform the following procedure:

91

EMI Shield

CDC

Fan Backplane

Phillips Screws (4)


Figure 43. Fan Backplane Removal and Replacement

1. Unlock and open the cabinet’s front door and remove the rear access panel. (See Section 5.3.)

2. Remove power from the cabinet. (See Section 5.4.)

3. Remove the power tap circuit breaker. (See Section 5.6.9.)

WARNING: To prevent personal injury and possible equipment damage, remove power from the cabinet before continuing with this procedure.

4. Pull each fan assembly out approximately two inches. (Just enough to disengage the connec-tors from the backplane. (See Section 5.6.1.1.)

5. Remove the CDC. (See Section 5.6.1.2.)

6. Disconnect the power and signal cables from the backplane. Excluding J007 and J015 the backplane connectors are all different to eliminate the risk of reconnecting a cable to the wrong connector.

7. Remove the eight Phillips-screws securing the fan backplane to the chassis. Hold the back-plane in place while removing the last two screws.

To replace the fan backplane, see Figure 43 and reverse the preceding steps.

91

Screws (8)


5.6.1.4 Fan Chassis

To remove the fan chassis, see Figure 44 and perform the following procedure:

Figure 44. Fan Chassis Removal and Replacement

1. Unlock and open the cabinet's front door and remove the rear access panel. (See Section 5.3.)

2. Remove power from the cabinet. (See Section 5.4.)

WARNING: To prevent personal injury and possible equipment damage, removepower from the cabinet before continuing with this procedure.

3. Remove the six fan assemblies from the chassis. (See Section 5.6.1.1.)

4. Disconnect all I/O cables from the fan backplane. (See Section 5.6.1.3.)

5. Remove the four Phillips-screws that secures the chassis to the cabinet.

CAUTION: To prevent physical injury use care when removing the fan chassis from the cabinet in Step 6.

6. Slide the fan chassis out of the cabinet.

To replace the fan chassis, see Figure 44 and reverse the preceding steps.

91


5.6.2 DC Module Air Filter

To remove a cabinet air filter, see Figure 45 and perform the following procedure:

Figure 45. Air Filter Removal and Replacement


2. Loosen the two captive thumb-screws which secures the access panel to the cabinet and remove the panel.

3. Slide the filter out of the cabinet.

NOTE: Fault messages occur when the air filter is removed.

To replace the air filter, see Figure 45 and reverse the preceding steps. When replacing the filter, make sure the air flow direction arrows are facing upward.

91Filter

Access Panel


5.6.3 Air Filter Sensor Switch (DC Cabinets)

To remove a cabinet air filter sensor switch, see Figure 46 and perform the following procedure:

Figure 46. Cabinet Air Filter Sensor Switch Removal and Replacement

1. Remove the cabinet's rear access panel. (See Section 5.3.3.)

2. Remove the two Phillips-screws securing the switch assembly to the cabinet rails and remove the assembly from the cabinet.

3. Disconnect the switch cable from the fan backpanel.

NOTE: The switch cable is replaced along with the switch.

To replace the air filter sensor switch, see Figure 46 and reverse the preceding steps.

5.6.4 Cabinet Top Cap

To remove the cabinet top cap, see Figure 47 and perform the following procedure:

102

Bracket

Switch


Figure 47. Cabinet Top Cap Removal and Replacement


2. Loosen the two captive thumb-screws which secures the top cap to the cabinet.

3. Disconnect the ADU cable from top cap.

4. Remove the alarm display panel. (See Section 5.6.5.) (Only necessary if you are replacing the top cap assembly. Do not remove the display panel for servicing.)

To replace the cabinet’s top cap assembly, see Figure 47 and reverse the preceding steps.

5.6.5 Alarm Display Unit (ADU)

To remove the cabinet’s ADU, see Figure 48 and perform the following procedure:

92

Top Cap

Thumbscrews

Alignment Pins


Figure 48. Alarm Display Panel Removal and Replacement

1. Remove the cabinet’s top cap. (See Section 5.6.4.)

2. Unscrew the four captive-screws on the ADU board.

3. Disconnect the cable from the ADU assembly.

To replace the ADU, see Figure 48 and reverse the preceding steps.

5.6.6 DC Power Controller

To remove a DC power controller, see Figure 49 and perform the following procedure:

99

ADU Board/ShieldCable

(Bottom View)


Figure 49. DC Power Controller Removal and Replacement


2. Place the circuit breaker on the DC power controller (being removed) in the Off position.

3. Loosen the captive screws on the controller.

4. Pull the DC power controller out until the safety latches catch.

WARNING: Upon completion of Step 4, wait 30 seconds before proceeding. This allows internal circuitry to dissipate power connector voltage/current to safe levels before drawer removal.

NOTE: To prevent physical injury, support the DC power controller while removing it from the cabinet in Step 5.

5. Press in the safety latch and remove the power controller.

To replace a DC power controller, see Figure 49 and reverse the preceding steps.

89

DC Power Controller

Captive

CircuitBreaker

Screw

Safety Latch


5.6.7 DC Power Controller Backplane

To remove a DC power controller backplane, see Figure 50 and perform the following procedure:

Figure 50. DC Power Controller Backplane Removal and Replacement

1. Notify the system administrator that power will be removed from the cabinet with the failed power controller backplane. If this cabinet is critical to system operation, shut down the sys-tem. Refer to Chapter 2 for shutdown procedures.


3. Remove power from the cabinet. (See Section 5.4.2.)

WARNING: To prevent personal injury and possible equipment damage, remove power

99

DC Power Controller Backplane

Phillips Screws (6)

(DC Power Cords)

Continuum Series 600/1200 Maintenance Guide (HM-058)

from the cabinet before continuing with this procedure.

NOTE: To maintain Start, Stop, and powerfail functionality on cabinets downline from the one being serviced, disconnect the respective “Prev” and “Next” and connect them together during the service operation. The cabinet being serviced and the next cabinet downline may report errors as these cables are disconnected from the power system.

4. Disconnect the power sequencing cables labelled NextA and PrevA from the power system and connect them together. Repeat this step for the remaining sequencer cables (NextB/PrevB and NextC/PrevC).

5. Disconnect the power and signal cables from the backplane. (See Section 5.6.8.)

6. Remove the six Phillips screws that secures the rear power cable bulkhead to the cabinet and remove the bulkhead.

7. Remove the twelve Phillips-screws securing the DC power controller backplane / EMI shield and remove it from the chassis.

WARNING: To prevent personal injury and possible equipment damage, verify DC power polarity before re-inserting the DC power controllers.

To replace the DC power controller backplane, see Figure 50 and reverse the preceding steps.

5.6.8 Power Cords

This section provides removal and replacement information for AC and DC powered systems. Since all sys-tems have duplexed power cords, it is not necessary to shutdown the system when replacing a single cord.

5.6.8.1 DC Power Cords

In DC powered systems, the power cords are connected directly to each cabinet. To remove and replace a DC power cord, see Figure 51 and perform the following procedure:


Figure 51. DC Power Cord Removal and Replacement


2. Remove power from the cabinet. (See Section 5.4.2.)

WARNING: To prevent personal injury and possible equipment damage, remove power from the cabinet before continuing with this procedure. Ensure that customer power is removed from incoming power cables.

3. Disconnect the DC power cables by turning the connectors’ T-handles counterclockwise.

4. The other end of the cable is hard-wired to DC power and requires a licensed electrician to disconnect and reconnect the cable.

WARNING: To prevent personal injury and possible equipment damage, check the voltage and polarity before continuing with this procedure. If they are incorrect, notify the customer.

To replace a DC power cord, see Figure 51 and reverse the preceding steps.

5.6.8.2 AC Power Cords

To remove an AC power cord, see Figure 52 and perform the following procedure:

99

DC Power Cord

T-Handle


Figure 52. AC Power Cord Removal and Replacement

CAUTION: Do NOT turn OFF the circuit breaker on both ACPCs simultaneously as this causes the system to initiate a powerfail shutdown sequence.

NOTE: A momentary powerfail message may occur if the ACPC powered Off was provid-ing AC to the PSUs. The second ACPC turns on within several seconds to reconnect AC to the PSUs.

1. Place the AC power controller circuit breaker in the OFF position.

2. Disconnect the power cord from the source voltage.

3. Disconnect the twist-lock power cord from the AC power controller.

To replace the AC power cord, see Figure 52 and reverse the preceding steps.

99

AC Power Cable

ACPC


5.6.9 Power Tap Circuit Breaker

To remove a power tap circuit breaker, see Figure 53 and perform the following procedure:

Figure 53. Power Tap Circuit Breaker Removal and Replacement

1. Notify the system administrator before powering off CRU/FRUs.


3. Place the power tap circuit breakers in the OFF (0) position.

4. Disconnect the power cable from the device (e.g. fan backplane).

WARNING: The power bus is live. To prevent personal injury and possible equipment dam-age, do NOT use tools to pry the circuit breaker off the power bus connector in Step 5.

5. Loosen the two thumb-screws (top and bottom) on the circuit breaker and remove the circuit breaker from the power bus.

To replace the power tap circuit breaker, see Figure 53 and reverse the preceding steps. Be sure to install the replacement with the circuit breaker switches in the OFF position.

92CircuitBreakers

Thumbscrew (2)

Power Cable

Power Bus


5.7 Central Electronics Cabinet (CEC)

This section describes the removal and replacement procedures for FRUs which are common to the 6- and 12-slot CECs. There are several differences between a 6-slot and a 12-slot CEC which are shown in Figure 54 and Figure 55.

Figure 54. 6- and 12-Slot DC CECs (Front View)

10

CEC Chassis

Fan Chassis

D700Enclosure

IOA PowerSupply

IOAChassis

(6-Slot)

CEC Chassis (12-Slot)

DC PowerController

Fan Chassis

DC PowerController

(12-Slot) (6-Slot)

Air Filter Air Filter


Figure 55. 6- and 12-Slot AC CEC (Rear View)

The 6-slot CEC card cage uses the same components as the 12-slot. The procedures to remove and replace these components common to both CEC cabinets show a 12-slot CEC, the 6-slot differs only in physical loca-tion or number of boards. The following components are common to both 6- and 12-slot CEC.

• Main processor boards

• Console Controller

• Backplane power supply

• Scorecards

5.7.1 Main Processor Boards

This section provides information on how to remove and replace main processor boards which reside in the CEC. Removing and replacing a main processor board involves a two-step process where you must determine if it is safe to remove the board (step 1), then remove it (step 2). The main processor boards are

• CPU/Memory

• IO controller

• SCSI-ENET controller

10

CDC/Fan

FanBackplane

BFU (1)

BatteryDrawer

Control Board

11-SlotIOA Chassis

BFU (1)

D700Enclosure

FanBackplane

CDC/FanControl Board

BatteryDrawer

Power ControlBackplane

ACPC (2) ACPC (2)

Air FilterAir Filter

Power ControlBackplane


The following subsections describe when it is safe to perform removal and replacement procedures.

5.7.1.1 Preparing to Remove a Main Processor Board

There is a bank of three LEDs on each main processor board. These LEDs provide various codes which indi-cate whether or not it is safe to remove the board. (See Figure 1) It is safe to remove a board when it is online-duplexed or in a broken state.

It is always advisable to see if it is safe to remove a board by using the analyze_system (VOS) and hwmaint (FTX) commands. If the board is not partnered it is unsafe to remove the board without crashing the system. See Chapter 2 for a more detailed explanation on how to use these commands.

5.7.1.2 Main Processor Board Removal and Replacement

To remove a main processor board, see Figure 56 and perform the following procedure:

Figure 56. Main Processor Board Removal and Replacement

Table 1. Main Processor Board Leds

Condition Red Yellow GreenOnline-duplexed Off Off On*Online-sim-plexed

Off On On

Broken On Off OffTesting Off On OffPower Fail Off Off Off* DO NOT PULL

89



2. Check to see if it is safe to remove the board. (See Section 5.5 and Section 5.7.1.1.)

CAUTION: To prevent physical injury, support the board while removing it in Step 3.

3. Loosen the captive thumb-screws and release the locking levers. Grasp the handle and slide the board out of the cabinet.

CAUTION: The chassis IO slots are keyed. When installing replacement I/O controllers, ensure the new controller is installed in the same slot the defective one was removed from. The SCSI-ENET uses a key setting of 2 and the IO processor uses a setting of 4. Do not force the board into the slot. If the key and the board are mismatched, the board does not go in far enough to engage the ejector levers.

To replace the board, see Figure 56 and slide it back into the cabinet slot, seat the locking levers against the chassis frame, and tighten the thumbscrews.

5.7.2 Console Controller

To remove the console controller, see Figure 57 and perform the following procedure:

Figure 57. Console Controller Removal and Replacement

1. Unlock and open the CEC cabinet’s front door. (See Section 5.3.1.)

89



3. Loosen the captive thumb-screws and release the locking levers. Slide the board out of the cabinet.

To replace the console controller, see Figure 57 and slide it back into the cabinet slot, seat the locking levers against the chassis frame, and tighten the thumbscrews.

5.7.3 Backplane Power Supply

To remove a backplane power supply, see Figure 58 and perform the following procedure:

Figure 58. Backplane Power Supply Removal and Replacement

1. Unlock and open the CEC cabinet’s front door. (See Section 5.3.1.)


3. Loosen the captive thumb-screws and release the locking levers. Slide the board out of the cabinet.

To replace a backplane power supply, see Figure 58 and slide it back into the cabinet slot, seat the locking levers against the chassis frame, and tighten the thumbscrews.

5.7.4 Scorecards

To remove a scorecard, see Figure 59 and perform the following procedure:

89


Figure 59. Scorecard Removal and Replacement

NOTE: There are four scorecards for a IO processor and up to eight for a SCSI-ENET con-troller.

1. Remove the CEC cabinet’s rear access panel. (See Section 5.3.3.)

2. Remove the scorecard’s EMI shield by loosening the four thumbs screws.

3. Using a gentle up and down motion, pull the card off its backplane connectors.

CAUTION: Inserting the incorrect scorecard into a backplane connector may cause system damage. Before inserting a new scorecard in to the backplane connector be sure that the card used is the proper type for the adapter that occupies that slot. The SCSI-ENET controller uses the (AA-K45100) scorecard and the IO processor uses AA-K60100 scorecard. The above fig-ure shows the proper orientation for the scorecard. Do not force the scorecard on the connec-tors.

To replace a scorecard, align the backplane pins to the scorecard socket and firmly push the connector in place.

5.7.5 6-Slot CEC

This section provides removal and replacement procedures for all components unique to the 6-slot CEC. The components are:

• Clock card

• Backplane

• IOA chassis power backplane

• IOA chassis backplane

• IOA chassis

93

Scorecard

Backplane Connectors


5.7.5.1 6-Slot CEC Clock Card

To remove a 6-slot clock card, see Figure 60 and perform the following procedure:

Figure 60. 6-Slot Clock Card Removal and Replacement

CAUTION: Use anti-static precautions when performing this procedure.

1. Notify the system administrator that power will be removed from the CEC. Since this cabi-net is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.

2. Remove power from the central electronics cabinet. (See Section 5.4.)

WARNING: To prevent personal injury and possible equipment damage, ensure that power is removed from the CEC.


97

Power Cable

Clock Card

Clock Card EMI Shield EMI Shield


4. Loosen the four thumb-screws and remove the clock card EMI shield.

5. Loosen the four thumb-screws and remove the backplane power cable EMI shield.

6. Loosen the four screws that secures the clock card in place.

NOTE: To prevent damaging connector pins, use care when removing the clock card in Step 7.

7. Grasp the clock card and pull it straight off the backplane’s connectors.

To replace a clock card, see Figure 60 and reverse the preceding steps.

5.7.5.2 6-Slot CEC Backplane

To remove the 6-slot CEC backplane, see Figure 61 and perform the following procedure:

Figure 61. 6-Slot CEC Backplane Removal and Replacement

95

Backplane

Power Connector EMI Shield

Clock Card

Backplane Power Cable/Connector

Scorecard(s)

Thumbscrews(2)

Clock CardEMI Shield


1. Notify the system administrator that power will be removed from the CEC. Since this cabi-net is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.

2. Remove power from the CEC. (See Section 5.6.)


3. At the front of the system, release all the boards in the CEC card cage approximately two-inches from their backplane connectors. This includes the console controllers, backplane power supplies, and all the main processor boards. (See Section 5.7.1 through Section 5.7.3.)

4. Label and disconnect the I/O cables from the backplane.

5. Remove all the EMI shields from the backplane.

6. Remove the clock card. (See Section 5.7.5.1.)

7. Remove the scorecards from slots two through five. (See Section 5.7.4.)

8. Remove the EMI shield covering the backplane’s power connector.

9. Loosen the two thumbs screws and disconnect the backplane power cable from the power bus.

CAUTION: Be sure to support the backplane when removing the last screw in Step 10.

10. Remove the ten Phillips-screws securing the backplane to the chassis and remove the back-plane.

To replace a 6-slot CEC backplane, see Figure 61 and reverse the preceding steps.

5.7.5.3 6-Slot CEC IOA Chassis Power Backplane

To remove the 6-slot CEC IOA chassis power backplane, see Figure 62 and perform the following procedure:


Figure 62. 6-Slot CEC IOA Chassis Power Backplane Removal and Replacement

1. Notify the system administrator that power will be removed from the IOA chassis. If this chassis is critical to system operation, shut down the system. Refer to Chapter 2 for shut-down procedures.

98

EMI Shield

IOA Access Panel

Power Backplane

PowerCable


2. Unlock and open the CEC cabinet’s front door and remove the rear access panel. (Section 5.3.)

3. Place the IOA chassis power tap circuit breakers in the Off position.

4. Disengage both IOA chassis power supplies from their backplane connectors. (See Section 5.10.2.)

5. Loosen the two screws and disconnect the power cable form the backplane.

6. Remove the IOA access panel from the CEC. There are four spring-pins holding it in place.

7. Loosen the six captive thumb-screws to remove the power backplane EMI shield.

8. Remove the eight Phillip-screws and lock washers and remove the power backplane.

To replace the 6-slot CEC IOA chassis power backplane, see Figure 62 and reverse the preceding steps.

5.7.5.4 6-Slot CEC IOA Chassis Backplane

To remove the 6-slot CEC IOA chassis backplane, see Figure 63 and perform the following procedure:


Figure 63. 6-Slot CEC IOA Chassis Backplane Removal and Replacement

98

Screws (12)

EMI ShieldIOA Access

PowerCable

Panel

To CDC

To SCSI-ENET Controller

IOA Chassis Backplane

Alignment

Alignment Slots

AlignmentTabs

Tabs

AlignmentSlots


5.8 AC/DC Power System

This section describes the removal and replacement procedures for the AC/DC power system. (See Figure 64)

Figure 64. AC/DC Power System FRUs

The AC/DC power system components are

• Fiber-optic cables

• Power Supply Unit (PSU)

• Power Control Unit (PCU)

• Battery Fuse Unit (BFU)

• AC Power Controller (ACPC)


• Batteries

• Battery drawer

• Battery drawer rails

• AC/DC power system chassis

• Front and rear air filters

96

(Front View) (Rear View)

Power Control

AC Power

BatteryDrawer

Power Control Backplane

Battery Fuse Unit (BFU)

Unit (PCU)

Power Supply Controller (ACPC) Unit (PSU)

FrontFilter

RearFilter


5.8.1 Fiber Optic Cables

To remove a fiber-optic cable, see Figure 65 and perform the following procedure:

NOTE: The fiber optic cables are necessary for maintaining error reporting on the AC/DC power system. The cable may be removed and replaced without affecting system operation. However, if the cables aren’t connected properly, you receive communication errors on the PSUs, PCU, and the BFU.

Figure 65. Fiber Optic Cable Removal and Replacement

1. Unlock and open the cabinet’s doors. (See Section 5.3.)

2. Disconnect the fiber-optic cable by squeezing the connector clip.

To replace a fiber-optic cable, see Figure 65 and connect the blue end to the blue connector and the gray end to the black connector (left to right).

99

Fiber Optic Cable Connector

Clip


5.8.2 Power Supply Unit (PSU)

To remove a PSU, see Figure 66 and perform the following procedure:

Figure 66. Power Supply Unit Removal and Replacement


2. Disconnect the fiber-optic cables from the PSU being removed. (See Section 5.8.1.)

3. Loosen the four captive thumb-screws on the PSU.

CAUTION: To prevent physical injury, support the PSU while removing it from the chassis in Step 4.

4. Grasp the handle and remove the PSU from the cabinet.

To replace the PSU, see Figure 66 and reverse the preceding steps. The daisy-chained fiber-optic cables are always connected from black to blue (left to right).

98


5.8.3 Power Control Unit (PCU)

To remove a PCU, see Figure 67 and perform the following procedure:

Figure 67. Power Control Unit Removal and Replacement


2. Disconnect the fiber-optic cables from the PCU being removed. (See Section 5.8.1.)

3. Loosen the four captive thumb-screws on the PCU.

CAUTION: To prevent physical injury, support the PCU while removing it from the chas-sis in Step 4.

4. Grasp the handle and remove the PCU from the cabinet.

To replace the PCU, see Figure 67 and reverse the preceding steps. The daisy-chained fiber-optic cables are always connected from black to blue (left to right).

99


5.8.4 Battery Fuse Unit (BFU)

To remove a BFU, see Figure 68 and perform the following procedure:

Figure 68. Battery Fuse Unit Removal and Replacement

1. Disconnect the fiber-optic cables from the defective BFU.

2. Loosen the four captive thumb-screws on the BFU.

CAUTION: To prevent physical injury, support the BFU while removing it from the chas-sis in Step 3.

3. Grasp the handle and remove the BFU from the cabinet.

To replace the BFU, see Figure 68 and reverse the preceding steps. The daisy-chained fiber-optic cables are always connected from blue to black (left to right).

100


5.8.5 AC Power Controller (ACPC)

To remove an ACPC, see Figure 69 and perform the following procedure:

Figure 69. ACPC Removal and Replacement

1. Place the ACPC’s circuit breaker in the Off position.

2. Disconnect the AC power cable by twisting the cable counter-clockwise and pulling it away from the system.

3. Loosen the four captive thumb-screws on the ACPC.

CAUTION: To prevent physical injury, support the ACPC while removing it from the chassis in Step 4.

4. Grasp the handle and remove the ACPC from the AC/DC power system.

To replace the ACPC, see Figure 69 and reverse the preceding steps.

100


5.8.6 Power Control Backplane

To remove the power control backplane, see Figure 70 and perform the following procedure:

Figure 70. Power Control Backplane Removal and Replacement

1. Notify the system administrator that power will be removed from the cabinet. If this AC/DC power system is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.

2. Remove power from the AC/DC power system. (See Section 5.4.)



4. Disconnect the cables from the power control backplane.

5. Remove the four Phillips-screws which secures the power control backplane bezel to the cabinet and remove the bezel.

6. Remove the ten torx screws (20T) which secure the backplane to the chassis and remove the backplane.

95Torx Screws (10)

Power Control Backplane

Bezel


7. Disconnect the signal cables from the rear of the backplane. You may have to remove the battery drawer to disconnect the signal cables. (See Section 5.8.8.)

To replace the power control backplane, see Figure 70 and reverse the preceding steps.

5.8.7 Batteries

To remove the batteries, see Figure 71 and perform the following procedure:

Figure 71. Battery Removal and Replacement

1. Open the battery drawer by loosening the two captive thumb-screws and pulling the drawer out until it locks in place.

2. Open the top cover by loosening the two captive thumb-screws.

3. Disconnect the battery connectors and remove the batteries from the drawer.

NOTE: When a battery drawer fault is detected, all four batteries in the defective drawer must be replaced at the same time.

To replace the batteries, see Figure 71 and reverse the preceding steps. When closing the drawer, push in the locking lever on each rail.

Battery Strap

Battery

Connector

Battery Cable

Battery Cover

95

Locking Lever


5.8.8 Battery Drawer

To remove the battery drawer, see Figure 72 and perform the following procedure:

Figure 72. Battery Drawer Removal and Replacement

1. Remove the batteries from the battery drawer. (See Section 5.8.7.)

2. Remove the drawer by pushing in the two locking lever on the rails and pulling the drawer all the way out.

To replace the battery drawer, see Figure 72 and reverse the preceding steps.

5.8.9 Battery Drawer Rails

If the battery drawer rails have to be replaced, the entire AC/DC power chassis must be replaced. (See Section 5.8.10.)

95


5.8.10 AC/DC Power System Chassis

To remove the AC/DC power system chassis, see Figure 73 and perform the following procedure:

Figure 73. AC/DC Power System Removal and Replacement

96

A

A

A

A

(Rear View)

(Front View)

Bezel

Power Cable

AC/DC Power System

Shipping Bracket

Shipping Bracket

Screws (6)


1. Notify the system administrator that power will be removed from this cabinet. If this cabinet is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.

2. Unlock and open the cabinet’s front door and remove the rear access panel. (Section 5.3.)

3. Remove power from the AC/DC power system. (See Section 5.4.)

WARNING: To prevent personal injury and possible equipment damage, ensure that power is removed from the AC/DC power system.

4. Remove the following components from the AC/DC power system:

• Power supply units (See Section 5.8.2.)

• Power control unit (See Section 5.8.3.)

• Battery fuse unit

• ACPC (See Section 5.8.5.)

• Power control backplane (See Section 5.8.6.)

• Batteries (See Section 5.8.7.)

• Battery drawer (See Section 5.8.8.)

• Air filters (See Section 5.8.11 and Section 5.8.12)

5. Disconnect the power cable from the power bus.

6. Remove the eight Phillips-screws which secure the chassis to the cabinet rails.

7. Remove the six (three on each side) Phillips-screws from the side brackets.

8. Remove the AC/DC power system from the cabinet.

To replace the AC/DC power system, see Figure 73 and reverse the preceding steps.

NOTE: The AC/DC power system is shipped with shipping brackets used for lifting the chassis. Once the chassis is installed, the brackets may be removed.


5.8.11 AC/DC Power System Front Air Filter

To remove the AC/DC power system front air filter, see Figure 74 and perform the following procedure:

Figure 74. AC/DC Power System Front Air Filter Removal and Replacement


2. Loosen the four captive thumb-screws and remove the filter access panel.


To replace the AC/DC power system front air filter, see Figure 74 and reverse the preceding steps. When replacing the filter, make sure the air flow direction arrows are facing upward.

95

Filter

Filter Access Panel


5.8.12 AC/DC Power System Rear Air Filter

To remove the AC/DC power system’s rear air filter, see Figure 75 and perform the following procedure:

Figure 75. AC/DC Power System’s Rear Air Filter Removal and Replacement

1. Loosen the two captive thumb-screws and remove the filter access panel.


To replace the AC/DC power system’s rear air filter, see Figure 75 and reverse the preceding steps. When replacing the filter, make sure the air flow direction arrows are facing upward.

95

Filter

Filter Access Panel


5.9 Mass Storage

This section describes removal and replacement for the following:

• Disk drives

• Tape drives

• Disk/Tape power supply

• Disk/Tape drive terminator

• Disk/Tape backplane

• Disk/Tape chassis

5.9.1 Disk Drive

Removing a disk drive is a three-step process where the drive(s) must be deleted from the operating system, physically removed/replaced, then added back into the operating system. To remove and replace a disk drives, see Figure 76 and perform the following procedure:

Figure 76. Disk Drive Removal and Replacement

1. Delete the failing drive from the operating system. (See Chapter 2 for VOS and FTX disk drive commands.)


3. Unlock the drive by turning the cam latch counterclockwise (unlocked position).

4. Remove the drive by sliding it out of the chassis.

To replace the disk drive, see Figure 76 and reverse the preceding steps. Refer to Chapter 2 for the software commands to add the replacement disk drive to the operating system.

89

Cam Latch

Disk Drive


5.9.2 Tape Drives

The following tapes drive are supported by the model 600 and 1200 systems. Refer to the sections that follow for removal and replacement procedures.

• T204 6250 1/2-inch SCSI

• T403 (single and dual drive configurations)

• T701 3.5-in DAT

• T702 3.5-in DAT with autoloader

• T703 525-MB QIC

5.9.2.1 T204 Table-Top Tape Drive

To remove a table-top T204 tape drive, see Figure 77 and perform the following procedure:

Figure 77. T204 Removal and Replacement (Tabletop Model)

CAUTION: Logically delete all devices in associated D700 enclosure before performing this procedure.

1. Remove the media from the tape drive.

2. Disconnect the data cable from the tape drive.

99

Data Cable

Power Cord

Terminator


3. Turn off the AC power switches on the rear of the drive.

4. Disconnect the power cable as shown and remove the drive from the table.

WARNING: To prevent personal injury and possible equipment damage, ensure that the tape drive is Off and the AC power and data cables are disconnected. The tape drive weighs 38.5 kg (85 lbs) and requires two people to remove it.

To replace the T204 tape drive, see Figure 77 and reverse the preceding steps. Note that you may have to remove the terminator and install it in the replacement drive.

5.9.2.2 T403 Table-Top Tape Drive

To remove a table-top T403 tape drive, see Figure 78 and perform the following procedure:

Figure 78. T403 Tape Drive Removal and Replacement (Tabletop Model)

CAUTION: Logically delete all devices in associated D700 enclosure before performing this procedure.

1. Remove tape cartridge magazine.

2. Disconnect the data cable from the disk drive.

3. Turn off the AC power switches on the rear of the drive.

4. Disconnect the power cable as shown and remove the drive from the table.

WARNING: The T403 weighs 27.2 kg (60 lbs). To prevent personal injury, two people may be required to remove the tape drive.

101

Power Cable

Data Cable

Terminator


To replace the T403 tape drive, Figure 78 and reverse the preceding steps. Note that you may have to remove the terminator and install it in the replacement drive.

5.9.2.3 T70X Tape Drives

To remove a T70X tape drive, see Figure 79 and perform the following procedure:

Figure 79. T70X Tape Drive Removal and Replacement


2. Unlock the tape drive by turning cam latch counterclockwise (unlocked position). The latch should be completely horizontal.

3. Remove the tape drive by sliding it out of the chassis.

To replace the T70X tape drive, see Figure 79 and reverse the preceding steps.

98

Tape Drive

Cam Latch


5.9.3 Disk/Tape Power Supply

To remove a disk/tape power supply, see Figure 80 and perform the following procedure:

CAUTION: This procedure should not be performed on simplexed power configurations unless the power supply is defective. Removing a good simplexed power module will cause all the devices in the D700 enclosure to loose power.

Figure 80. .Disk/Tape Power Supply Removal and Replacement


2. Unlock the power supply by turning cam latch counterclockwise.

3. Remove the power supply by sliding it out of the cabinet.

To replace the disk/tape power supply, see Figure 80 and reverse the preceding steps

89

Disk/Tape Power Supply

Cam Latch


5.9.4 Disk/Tape Drive Terminator

To remove the disk/tape drive SCSI terminator, see Figure 81 and perform the following procedure:

Figure 81. Disk/Tape Drive Terminator Removal and Replacement

NOTE: The disk drives which occupy this chassis must be removed from the operating sys-tem and the T70X tape drives must not be in use before continuing with this procedure.

1. Delete the disk drives from the operating system. (See Section 5.9.1.)


3. Depress the sprint clips on the side of the terminator and remove it from the connector.

To replace the disk/tape terminator, see Figure 81 and reverse the preceding steps.After replacing the termina-tor, ensure the disk drives are added back into the operating system and are functioning properly before replac-ing the rear access panel.

97

Disk/Tape Terminator


5.9.5 Disk/Tape Backplane

To remove the disk/tape backplane, see Figure 82 and perform the following procedure:

Figure 82. Disk/Tape Backplane Removal and Replacement

1. Delete the disk drives (which occupy the chassis) from the operating system. (See Section 5.9.1.)

CAUTION: The disk drives which occupy this chassis must be removed from the operating system and the D70X tape drives must not be in use before continuing with this procedure.


3. Pull the disk drives and tapes drives out enough to disengaged them from their backplane connectors. (See Section 5.9.1 and Section 5.9.2.)

4. Turn the power tap circuit breakers for the disk drive enclosure Off. If the circuit breaker must be removed to perform this procedure, refer to Section 5.6.9.

5. Disconnect the power and data cables from the backplane.

6. Remove the terminator or external tape drive cable. (See Section 5.9.4.)

97

Disk/Tape Backplane

Power/Data Cables

Disk/Tape Terminator

CDC Daisy-Chain Cables


7. Loosen the six captive-screws that secures the backplane to the chassis and remove the back-plane.

To replace the Disk/Tape backplane, refer to Figure 82 and reverse the preceding steps.

5.9.6 Disk/Tape Chassis

To remove the disk/tape chassis, see Figure 83 and perform the following procedure:

Figure 83. Disk/Tape Chassis Removal and Replacement

97


1. Delete the disk drives (which occupy the chassis) from the operating system. (See Section 5.9.1.)

2. Unlock and open the cabinet’s front door and remove the rear access panel. (See Section 5.3.3.)

CAUTION: The disk drives which occupy this chassis must be removed from the operating system before continuing with this procedure.

3. Remove the disk and tape drive(s). (See Section 5.9.2.)

4. Turn the power tap circuit breakers for the disk/tape chassis Off.

5. Disconnect power and data cables at the rear of the system.

6. From the front of the cabinet, remove the four Phillip-screws that secure the chassis to the rails and slide the chassis out of the cabinet.

To replace the disk/tape chassis, see Figure 83 and reverse the preceding steps.

5.10 Input Output Adapter (IOA) Subsystem

The IOA subsystem consists of the following components:

• Input / Output Adapters (IOAs)

• IOA chassis power supply

• IOA chassis power supply backplane

• IOA chassis backplane

• IOA chassis


5.10.1 IOAs

To remove an IOA or an IOA terminator from an IOA chassis, see Figure 84 and perform the following proce-dure:

Figure 84. IOA removal and Replacement


2. Locate the defective IOA, and if applicable, label the communication cables connected to the card. Loosen the connector mounting screws or disengage slide locks if applicable.

3. Extend the ejector lever(s) on the defective IOA and slide the card out of the chassis.

To replace the IOA or IOA terminator, see Figure 84 and reverse the preceding steps.

97


5.10.2 IOA Chassis Power Supply

To remove an IOA chassis power supply, see Figure 85 and perform the following procedure:

Figure 85. IOA Chassis Power Supply Removal and Replacement


2. Loosen the captive thumb-screws on each ejector lever.

3. Lift up on the power supply ejector lever to disengage the power supply from its backplane connectors.

CAUTION: To prevent physical injury support the power supply while removing it from the chassis in Step 4.

4. Grasp the power supply’s handle and slide it out of the chassis.

To replace the IOA chassis power supply, see Figure 85 and reverse the preceding steps.

97


5.10.3 IOA Chassis Power Supply Backplane

To remove the IOA chassis power supply backplane, see Figure 86 and perform the following procedure:

Figure 86. IOA Power Supply Backplane Removal and Replacement

1. Notify the system administrator that the IOAs in the chassis will be disabled to accommo-date this repair procedure. If this IOA chassis is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.


3. Turn the power tap circuit breakers for the IOA chassis Off.

4. Loosen the four captive thumb-screws and remove the EMI shield.

5. Pull both IOA chassis power supplies out far enough to disengage the backplane connectors. (See Section 5.10.2.)

6. At the rear of the cabinet, loosen the captive screws that secure the EMI shield and remove the shield.

7. Disconnect the power cable.

100

IOA PowerSupply Backplane

Power Cable


8. Loosen the four captive-screws securing the EMI shield to the power supply backplane and set the cover aside.

9. Remove the eight Phillips-screws securing the backplane to the chassis and remove the backplane.

To replace the IOA power supply backplane, see Figure 86 and reverse the preceding steps.

5.10.4 IOA Chassis Backplane

To remove the IOA chassis backplane, see Figure 87 and perform the following procedure:

Figure 87. IOA Chassis Backplane Removal and Replacement

99


J002 Cable to

J001 Cable to

J021 Cable to

Screws (14)

Next IOA Chassis

Fan Backplane

IO Processor Port


1. Notify the system administrator that the IOAs in the chassis will be removed to accommo-date the repair procedure. If this IOA chassis is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.dure.

2. Open the cabinet that houses the IOA chassis. Unlock and open the front door and remove the rear access panel. (See Section 5.3.)


4. Pull the IOA adapters out far enough to disengaged them from their backplane connectors. (See Section 5.10.1.)


6. At the rear of the cabinet, remove the IOA chassis backplane EMI shield. The are four spring-pins holding the shield in place.

7. Disconnect the following cables from the backplane. (J001, J002, and J021)

8. Label and disconnect the I/O cables connected to the rear of the chassis.

9. Remove the fourteen Phillips-screws that secures the backplane to the IOA chassis. Support the backplane as you remove the last screw.

To replace the IOA backplane, see Figure 87 and reverse the preceding steps.


5.10.5 IOA Chassis

To remove the IOA chassis, see Figure 88 and perform the following procedure:

Figure 88. IOA Chassis Removal and Replacement

98


1. Notify the system administrator that the IOAs in the chassis will be removed to accommo-date the repair procedure. If this IOA chassis is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.


3. Turn the power tap circuit breakers for the IOA chassis Off and disconnect the power cable.

4. Remove the IOA chassis power supply. (See Section 5.10.2.)

5. Remove the I/O adapter cards from the IOA chassis. (See Section 5.10.1.)

6. Disconnect the J001, J002, and J021 cables from the backplane. (See Figure 87.)


8. At the front of the cabinet, remove the four screws that secures the chassis in place.

9. Slide the chassis out of the cabinet.

To replace the IOA chassis, see Figure 88 and reverse the preceding steps

5.11 Dual Input/Output Adapter (IOA) Subsystem

The maximum Dual IOA Subsystem configuration consists of the following hardware components:

• Dual IOA enclosure

• Two IOA chassis (front and rear)

• Two IOA chassis backplanes

• Two IOA chassis power supplies

• Two IOA chassis power supply backplanes

• IOA adapters

5.11.1 IOA Chassis Power Supply Backplane

To remove the IOA chassis power supply backplane, see Figure 89 and perform the following proce-dure:


Figure 89. IOA Power Supply Backplane Removal and Replacement

1. Notify the system administrator that the IOAs in the chassis will be disabled to accommo-date this repair procedure. If this IOA chassis is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.

2. Remove the cabinet’s rear access panel. (See Section 5.3.)

3. At the rear of the cabinet, turn the power tap circuit breakers for the IOA chassis Off.

4. At the front of the IOA chassis, pull both IOA chassis power supplies out far enough to dis-engage the backplane connectors. (See Section 5.10.2.)

5. At the rear of the IOA chassis, loosen the two captive thumb-screws on the access panel behind the power supply backplane and remove the panel.

6. Disconnect the power cable from the power supply backplane.

7. Loosen the four captive-screws securing the EMI shield to the power supply backplane and set the cover aside.

8. Remove the eight Phillips-screws securing the backplane to the chassis and remove the backplane.

To replace the IOA power supply backplane, see Figure 89 and reverse the preceding steps.

5.11.2 IOA Chassis Backplane (Single Chassis Configuration)

To remove the front IOA chassis backplane when there is no rear chassis present in the dual IOA

Power Tap

Power Supply Backplane

Power Supply Backplane EMI Shield

Power Cable

Access Panel

Screws (8)


enclosure, see Figure 90 and perform the following procedure:

Figure 90. IOA Chassis Backplane Removal and Replacement (Single IOA Chassis Configuration)




4. At the front of the IOA chassis, pull the IOA adapters out far enough to disengaged them from their backplane connectors. (See Section 5.10.1.)


6. At the rear of the cabinet, disconnect the cables from the J001, J002, and J021 connectors on the backplane.


8. Remove the IOA chassis backplane EMI shield. The are four spring-pins holding the shield

J021 Cable

J001 CableJ002 Cable

Spring-Pins

Spring-Pins

EMI Shield

Screws (14)



in place.

9. Remove the fourteen Phillips-screws that secure the backplane to the IOA chassis. Support the backplane as you remove the last screw.

To replace the IOA backplane, see Figure 90 and reverse the preceding steps.

5.11.3 IOA Chassis Backplane (Dual Chassis Configuration)

To remove an IOA chassis backplane when both front and rear IOA chassis are present in the dual IOA enclosure, see Figure 91 and perform the following procedure:

Figure 91. IOA Chassis Backplane Removal and Replacement (Dual IOA Chassis Configuration)

1. Notify the system administrator that the IOAs in the chassis will be removed to accommo-date the repair procedure. If this IOA chassis is critical to system operation, shut down the system. Refer to Chapter 2 for shutdown procedures.dure.



4. Remove the IOA adapters from the chassis containing the failed backplane. (See Section 5.10.1.)

Cable Tray

Screws (4)

Table

Power Supply Backplane Access Panel


5. Remove both IOA chassis power supplies. (See Section 5.10.2.)

6. At the front of the IOA chassis, loosen the two captive thumb-screws securing the cable tray and remove the tray.

7. Remove the four screws securing the IOA chassis to the dual IOA enclosure.

8. Remove the power supply backplane access panel to provide better access to the IOA chassis.

CAUTION: Be very careful when performing the next step, since there still are cables connected to the backplane at the rear of the chassis.

9. Place a small table or chair in front of the cabinet and carefully slide the IOA chassis out of the enclosure and place it on the chair/table.

10.Disconnect the cables from the J001, J002, and J021 connectors on the IOA chassis back-plane.

11. Remove the IOA chassis backplane EMI shield. The are four spring-pins holding the shield in place.

12.Remove the fourteen Phillips-screws that secures the backplane to the IOA chassis. Support the backplane as you remove the last screw.

To replace the IOA backplane, see Figure 90 and Figure 91 and reverse the preceding steps.

5.11.4 IOA Chassis (Single Chassis Configuration)

To remove the front IOA chassis from the dual IOA enclosure when there is no rear chassis present, see Figure 92 and perform the following procedure:


Figure 92. IOA Chassis Removal and Replacement (Single Chassis Configuration)

1. Notify the system administrator that the IOAs in the chassis will be removed to accommodate the repair procedure. If this IOA chassis is critical to system operation, shut down the system.

2. Open the expansion cabinet that houses the IOA chassis. Unlock and open the front door and remove the rear access panel. (See Section 5.3.)


4. Disconnect the cables from the J001, J002, and J021 connectors on the IOA chassis back-plane.


6. At the front of the IOA chassis, remove the IOA adapter cards from the IOA chassis. (See Section 5.10.1.)

7. Remove the IOA chassis power supplies. (See Section 5.10.2.)

8. Loosen the two captive thumb-screws securing the cable tray and remove the tray.


Cable Tray

Screws (4)

Access Panel J021 Cable

PowerCable

Access Panel

J001 Cable

J002 Cable

EMI Shield


10.Carefully slide the chassis out of the enclosure.

11.Remove the IOA chassis backplane EMI shield. The are four spring-pins holding the shield in place.

To replace the IOA chassis, see Figure 92 and reverse the preceding steps.

5.11.5 IOA Chassis (Dual Chassis Configuration)

To remove either IOA chassis from the dual IOA enclosure when both front and rear chassis are present, see Figure 93 and perform the following procedure:

Figure 93. IOA Chassis Removal and Replacement (Dual Chassis Configuration)


2. Open the expansion cabinet that houses the IOA chassis. Unlock and open the front door and remove the rear access panel. (See Section 5.3.)

Cable Tray

Screws (4)

Table

Power Supply Backplane Access Panel

J021 Cable

PowerCable

Access Panel

J001 Cable

J002 Cable

Rear View

EMI Shield



4. At the front of the IOA chassis, remove the IOA adapter cards from the IOA chassis. (See Section 5.10.1.)

5. Remove the IOA chassis power supply. (See Section 5.10.2.)

6. Loosen the two captive thumb-screws securing the cable tray and remove the tray.


CAUTION: Be very careful when performing the next step, since there still are cables connected to the backplane at the rear of the chassis.

8. Place a chair or small table in front of the cabinet and carefully slide the IOA chassis out of the enclosure and place it on the chair/table.

9. At the rear of the IOA chassis, disconnect the cables from the J001, J002, and J021connectors on the backplane.

10. Remove the IOA chassis backplane EMI shield. The are four spring-pins holding the shield in place.

To replace the IOA chassis, see Figure 93 and reverse the preceding steps.

❖

Documents

Continuum Series 600/1200 - Customer Support · 4.2.1.1. syserr_log.date File ... 139 5.10.2 IOA Chassis Power Supply ... Continuum Series 600/1200 Maintenance Guide