EF5XX-Series Solid State Disk Drive User Guide EK–EF5XX–UG–001 Digital Equipment Corporation
November 1992 Copyright © Digital Equipment Corporation 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license.
German Noise Declaration: The following information is provided to meet the German Noise Declaration Decree (part of the German Equipment Safety Law). English: September 18, 1992 --------------------------------------------------------------------Acoustics - declared values per ISO 9296 and ISO 7779: Sound Power Level L , Sound Pressure Level B L , dBA pAm (operator position) WAd Product EF51/2R-AA/F BA430/440 + 3xEF51/2R R400X + 7xEF51/2R Idle Operate Idle Operate 4.4 4.5 34 35 5.6 5.
The following are trademarks of Digital Equipment Corporation: DEC, DECmailer, DECservice, DSA, DSSI, EF, KA640, KFQSA, MicroVAX, MSCP, Q-Bus, RF31, RF72, SERVICenter, TMSCP, ULTRIX, VAX, VAXsimPLUS, VMS and the Digital logo.
Contents Preface 1 General Information Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EF5XX ISE Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Shipping Contents/Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Installation Overview Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing into the BA400-Series Enclosure . . . .
MEMTST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PARAMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Data Retention System Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EF5XX Data Retention Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery Subsystem Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 1–1 5–1 5–2 EF5XX Series Performance Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . Battery Maintenance Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Parameter Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Introduction In This Guide This guide introduces the EF5XX-series solid state disk drive and describes the installation and operating procedures. Intended Audience This guide is intended for the EF5XX disk drive user.
Introduction, Continued Chapter 4 ‘‘Local Programs’’ describes how to access local programs through the: VMS system and the console by using the SET HOST/DUP command MicroVAX Diagnostic Monitor (MDM) Chapter 5 ‘‘Data Retention System’’ discusses integrated data retention system features including battery testing and monitoring.
Chapter 1 General Information Overview In this Chapter This chapter includes: EF5XX-series solid state disk drive description Using the EF5XX disk drive EF5XX options Data retention system description Digital Storage System Interconnect (DSSI) bus function Integrated Storage Element (ISE) EF5XX-Series ISE Drive performance features Drive specifications Shipping contents Related documents Continued on next page 1–1
Overview, Continued Description The EF5XX series is Digital Equipment Corporation’s first generation of solid state disk drives packaged in a full-height, 5¼-inch form factor. These DSSI ISEs supply highly reliable data storage using semiconductor memory as the storage media. Like all DSSI ISEs, the EF5XX-series disks communicate with the host using Digital Storage Architecture (DSA) and Systems Communications Architecture (SCA) protocols such as the Mass Storage Control Protocol (MSCP).
Overview, Continued Using the EF5XX You can use the EF5XX-series ISEs with these VAX family systems: VAX4000 VAX6000 VAX7000 VAX10000 EF5XX Options These are the EF5XX ISEs covered in this guide and their formatted storage capacities: EF51R, 107 megabytes EF52R, 205 megabytes EF53, 267 megabytes Data Retention System Description The EF51R and the EF52R ISEs provide non-volatility of data by a data retention system including: Power sensing logic An internal winchester magnetic disk drive A battery to po
Overview, Continued DSSI Bus Function The DSSI bus is a logical equivalent to the CI bus used on larger Digital systems. The DSSI bus is used with low-end and mid-range VAX systems. The DSSI bus is a 50-conductor cable that allows one or more hosts to communicate directly with storage devices. The hosts and devices communicate through the SCA protocols. As many as eight nodes (integrated storage elements and adapters) can connect to one DSSI bus.
Overview, Continued EF5XX-Series ISE Figure 1–1 shows the EF5XX-series disk, a full-height, 5-¼inch, fixed-disk storage device. Its dimensions are 8.26 cm (3.25 in) by 14.60 cm (5.75 in) by 20.32 cm (8.00 in). Figure 1–1 EF5XX-Series ISE–Front and Rear Views (Brackets shown are used only for certain installations.
Overview, Continued Performance Features EF5XX-series disks offer powerful performance features that are not typically available on disk storage devices in this form factor. Table 1–1 lists some of these features: Table 1–1 EF5XX Series Performance Features 1–6 Feature Function Multihost support This allows a single ISE to be used by more than one host at the same time. For example, two VAX4000 systems can be booted from a single ISE.
EF5XX ISE Specifications Introduction This section includes performance, power, media, and environmental specifications. Performance Specifications The following table lists the physical, functional, and performance specifications of the EF51R, EF52R, and EF53 ISEs: Physical EF51R EF52R EF53 Height 8.26 cm (3.25") 8.26 cm (3.25") 8.26 cm (3.25") Width 14.60 cm (5.75") 14.60 cm (5.75") 14.60 cm (5.75") Depth 20.32 cm (8.00") 20.32 cm (8.00") 20.32 cm (8.00") Weight 2.
EF5XX ISE Specifications, Continued Performance EF51R EF52R EF53 Avg Access Time (ms) .25 .25 .25 Peak Transfer Rate to DSSI Bus (Mbytes/sec) 4.00 4.00 4.00 Start Time (total min) 2.00 2.00 2.00 NOTE The average access time includes commands, array access, Error Correction Code (ECC), and buffer delays. It does not include host software or host adapter latency.
EF5XX ISE Specifications, Continued Current and Power Consumption The following table lists the maximum current and power consumption and the typical current and power specifications: Maximum Current & Power EF51R EF52R EF53 Normal 0.0 0.0 2.2 Peak 0.0 0.0 3.7 Normal1 1.5 1.4 0.0 Peak2 2.3 2.2 0.1 Normal1 18.0 16.6 11.2 Peak2 27.6 26.2 18.4 5.0 V Supply Current (amps) 12.
EF5XX ISE Specifications, Continued Typical Current & Power EF51R EF52R EF53 5.0 V Supply Current (amps) 0.0 0.0 1.8 12.0 V Supply Current (amps) 1.2 1.0 0.0 Total Power (watts) 14.3 12.4 8.
EF5XX ISE Specifications, Continued Environmental Specifications The following table lists environmental specifications: Environmental Specifications EF51R, EF52R, EF53 Temperature Operating 10 to 50°C (50 to 122°F), ambient, with a gradient of 11°C (20°F) per hour (as introduced to the drive enclosure) Non-operating -40 to 66°C (-40 to 151°F), ambient, with a gradient of 20°C (36°F) per hour Relative humidity Operating 10 to 90% with maximum wet bulb temperature of 28°C (82°F) and a minimum dew poi
Shipping Contents/Related Documents Check Shipment Ensure your shipment has all the items listed on the contents listing. If any item is missing or damaged, contact your delivery agent or your Digital representative. NOTE Save the packing materials until you are sure you will not reship any items.
Shipping Contents/Related Documents, Continued Related Documents Along with your system documentation, the following documents supplement this guide: Title Order Number BA400-Series Enclosures Storage Devices Installation Procedures EK–BA44A–IN DECarray Installation Guide EK–SF2XX–IG 1–13
Chapter 2 Installation Overview Introduction In this Chapter This chapter tells you how to prepare the EF5XX ISE and install the ISE into the: BA400-series system enclosure SF7X storage enclosure For more detailed information about the: Installation into the BA400-series enclosure, refer to BA400-Series Enclosures Storage Devices Installation Procedures, (EK–BA44A–IN). SF7X enclosure, refer to DECarray Installation Guide, (EK–SF2XX–IG).
Installing into the BA400-Series Enclosure Preparing for the Installation To prepare for the installation: CAUTION Static electricity can damage integrated circuits. Use the antistatic wrist strap and antistatic pad found in the static-protective field service kit (29-26246-00) when you work with the internal parts of a computer system. Handle the ISE with care. Dropping or bumping the ISE can damage the disk surface. 1.
Installing into the BA400-Series Enclosure, Continued Removing the Skid Plate Remove the plastic skid plate from the right side of the ISE by removing the four screws (Figure 2–1). Discard the skid plate.
Installing into the BA400-Series Enclosure, Continued Figure 2–1 Removing the Plastic Skid Plate (AF or AA version only) Skid Plate Screws Screws MLO-009302 Continued on next page 2–4
Installing into the BA400-Series Enclosure, Continued Installation Steps To install the ISE into the BA400-series enclosure: 1. With the side that had the skid plate attached to it facing to the right, slide the ISE along the guide rails into the mass storage cavity (Figure 2–2A). 2. Using the upper and lower finger cutouts on the ISE brackets, firmly push the ISE brackets until the interface card at the rear of the ISE plugs into its backplane connector.
Installing into the BA400-Series Enclosure, Continued Figure 2–2 Installing the ISE in the Enclosure (RF and RZ front panels shown for reference.) A Captive Screws Remote Front Panel Cable Guide Tabs Phillips Screw Finger Cutouts B C D Remote Front Panel Cable Remote Front Panel Cable Velcro EF/RF/RZ 5.25-inch RF 3.5-inch RZ 5.
Installing into the BA400-Series Enclosure, Continued For further information, refer to the BA400-Series Enclosures Storage Devices Installation Procedures, (EK–BA44A–IN).
Installing into the SF7X Enclosure Preparing for the Installation Prepare for the installation into an SF7X enclosure as detailed in the DECarray Installation Guide, (EK–SF2XX–IG). CAUTION Static electricity can damage integrated circuits. Use the antistatic wrist strap and antistatic pad found in the static-protective field service kit (29-26246-00) when you work with the internal parts of a computer system. Handle the ISE with care. Dropping or bumping the ISE can damage the disk surface.
Installing into the SF7X Enclosure, Continued 7. Remove the ISE bottom bracket by removing the two Phillips screws at the rubber shock bushings that secure the bracket to the chassis (Figure 2–3). NOTE Carefully note the orientation and routing of the remote front panel cable.
Installing into the SF7X Enclosure, Continued Figure 2–3 Removing the Top and Bottom Brackets (AF or AA version only) Screws Top Bracket Chassis Bottom Bracket Screws Interface Card Assembly MLO-009303 Continued on next page 2–10
Installing into the SF7X Enclosure, Continued Inserting the Wedges To insert the wedges: 1. Remove the two wedges from the shipment box. 2. Hold one wedge at the front end (contains the screw) and insert the two rear prongs into the two elongated holes on the side of the chassis (Figure 2–4). The two holes are 2-3/4 inches from the rear of the chassis. 3. Lower the front end of the wedge and insert the front prongs into the two circular holes next to the connectors on the front of the drive (Figure 2–4).
Installing into the SF7X Enclosure, Continued Figure 2–4 Inserting the Wedges on the EF5XX ISE Continued on next page 2–12
Installing into the SF7X Enclosure, Continued Installation Steps To install the ISE into the SF7X enclosure (Figure 2–5): 1. With the ISE skid plate facing the enclosure guide rails, slide the ISE along the guide rails until the ISE is locked in place inside the SF7X enclosure. 2. Use a Phillips head screwdriver to tighten the screws on the wedges, so the ISE sets securely in the enclosure. 3.
Installing into the SF7X Enclosure, Continued Figure 2–5 The SF7X Enclosure NOTE TO ILLUSTRATOR: front panel for this hardware is SHR_X1127_89 ISOL and reduced 17/64 (.265625) e SI R DS ID SI DS ID di R gi d ea l e Fa r it t W tec yP r o ta eF r it t W tec y ro ad P au lt DSSI CABLE u lt 10-PIN OCP CABLE 5-PIN DRIVE POWER CABLE SHR-X0135A-90 For more information about the SF7X enclosure, refer to the DECarray Installation Guide, (EK–SF2XX–IG).
Chapter 3 Controls and Indicators Introduction In this Chapter This chapter describes the controls and indicators associated with ISE operation. The controls and indicators are located on the: Operator control panel (OCP) on the system enclosure ISE front panel (Figure 3–1) Operator Control Panel (OCP) The operator control panel (OCP) is a set of controls on the enclosure that overrides the drive module switches and lets you set the DSSI node ID and write-protect mode for the ISE.
Introduction, Continued The following table compares the OCPs in the and BA400-series and SF7X enclosures. 3–2 In the ... an OCP ... BA400-series enclosures, is contained on each ISE and is mounted to a panel in front of the ISE (Figure 3–1). SF7X enclosure, contains four identical sets of controls and indicators.
BA400-Series Controls and Indicators OCP Each ISE installed in a BA400-series enclosure has a front panel with the following controls and indicators: DSSI bus node ID plug Fault indicator (LED) Run/Ready button Write-Protect button Figure 3–1 BA400-Series OCP (front panel) for DSSI ISEs RUN/READY BUTTON WRITE-PROTECT BUTTON BUS NODE ID PLUG FAULT INDICATOR MLO-004044 SHR-X0058-90 Continued on next page 3–3
BA400-Series Controls and Indicators, Continued Control and Indicator Functions The following table describes the functions of the controls and indicators on the BA400-series DSSI operator control panel: Control Status Function Fault LED Lit Indicates an error condition within the ISE. Not lit Indicates an error-free condition within the ISE. Quick flash (10 Hz) OCP failure, or drive select plug is missing. In (lit) The ISE is on line. When the ISE is available for use, the green LED is lit.
Changing the DSSI Node ID Plugs (BA400-Series OCPs) Spare Plugs Spare DSSI node ID plugs are supplied with the EF5XX. Use these spare plugs to reconfigure your DSSI system because of adding or removing ISEs or creating a multihost configuration. Removal The DSSI node ID plugs have prongs on the back that indicate the bus node number (and by default, the unit number) of the ISE. To remove a DSSI node ID plug, grasp it firmly and pull it straight out.
SF7X Controls and Indicators OCP Each ISE in the SF7X storage enclosure is represented by an icon on the door located on the OCP. Each set of controls and indicators is dedicated to one of the four storage compartments in the enclosure (Figure 3–2).
SF7X Controls and Indicators, Continued Control and Indicator Functions The following table describes the functions of the controls and indicators on the front of the SF7X enclosure. Control/ Indicator Color Function Ready Green Illuminates when ISE is on line and read/write ready. Fault Red Illuminates when fault is detected. DSSI Node ID Green Displays ISE DSSI Node ID. Write Protect Yellow Commands write protect mode. Shows write protect enabled.
EF5XX ISE Controls and Indicators Description Two LEDs and a DIP switchpack containing three switches are mounted on the edge of the drive module. The switches provide a means of setting the DSSI node ID if an OCP is not connected to the drive, or if the OCP fails. The two LEDs indicate drive status: READY LED FAULT LED Figure 3–3 shows the location of the switches and LEDs on the drive module.
EF5XX ISE Controls and Indicators, Continued Figure 3–3 Drive Module Switch and LED Locations Continued on next page 3–9
EF5XX ISE Controls and Indicators, Continued Assigning the DSSI Node ID To assign the DSSI node ID, set the three switches to the binary equivalent of the selected ID number, as shown in the following table. These switches are ignored when an operator control panel is connected to the ISE.
EF5XX ISE Controls and Indicators, Continued Drive Module LEDs The two LEDs mounted on the drive module monitor ISE status during operation. The following table describes the state of these two LEDs during the various phases of ISE operation. When . . . The green LED is . . . And the yellow LED is . . .
Chapter 4 Local Programs Introduction In this Chapter This chapter includes: How to access local programs through the VMS system, the console, and the MicroVAX Diagnostic Monitor (MDM) Descriptions of accessible local programs Overview Local programs are diagnostics and utilities that are internal to the ISE. You can access them in one of three ways, depending on which system you are using.
Introduction, Continued The following table refers to each section with instructions on how to access local programs: To access local programs ... Refer to ... Through VMS, using the SET HOST command, Using VMS From the console, using the SET HOST command, Using Console Commands Through MDM, using the Device Resident Programs menu, Using MDM Once you establish a connection, the local program controls the operations that are performed.
Introduction, Continued Programs1 Section DIRECT DIRECT Program Description DRVEXR DRVEXR Program Description DRVTST DRVTST Program Description HISTRY HISTRY Program Description DRINIT DRINIT Program Description BATTST BATTST Utility Description MEMTST MEMTST Utility Description PARAMS PARAMS Utility Description 1 For users familiar with the RF-series ISEs, notice that the DKUTIL, ERASE, and VERIFY local programs are not available in the EF5XX-series ISEs.
How to Access Local Programs Using VMS To access a local program from a MicroVAX system running VMS version 5.
How to Access Local Programs, Continued Using Console Commands Some systems allow you to access the local programs using console commands. The command you use depends on whether your system uses a Q–bus adapter such as the KFQSA module, or an embedded adapter such as the KA640 module.
How to Access Local Programs, Continued Q–bus Adapters (continued) To access a local program from a system with an embedded adapter, use the command: >>> SET HOST/DUP/DSSI/BUS:n # n = bus number where the ISE is located # = DSSI node number of the ISE The system then prompts you for the name of the local program you want to run. To find the DSSI node number and node name, type SHOW DSSI at the >>> prompt. To see a list of the devices on the Q–bus, type SHOW QBUS or SHOW UQSSP at the >>> prompt.
How to Access Local Programs, Continued Using MDM If neither VMS nor console commands are available on your system, you can run local programs using MDM. Use the following procedure: 1. Boot MDM. 2. Enter the date and time. 3.
How to Access Local Programs, Continued Using MDM (continued) 4. Enter the name of the local program you want to run and press Return . For information about the available local programs, refer to the program descriptions on the following pages. 5. To exit MDM, press the Break key.
Descriptions of Local Programs Overview )DIRECT Program Description The rest of this chapter describes local programs you can access. The DIRECT program provides a directory of local programs resident in the ISE.
DRVEXR )DRVEXR Program Description The DRVEXR program is a diagnostic program that applies several types of stress to the ISE. Access DRVEXR the same way you would the other local programs. Once a connection is established, the system prompts you to answer a series of questions. Your responses determine the mode and test duration. Stopping DRVEXR To stop DRVEXR in progress, press Ctrl/C , Ctrl/Y , or Ctrl/Z . When DRVEXR stops, a short report is printed.
DRVEXR, Continued Dialogue (continued) Message Explanation Test time in minutes? [(10)-100] Your response determines the length of the test, in minutes. Number of sectors to transfer at a time? [0 - 50] This question is included for compatibility with DRVEXR in RFseries ISEs. The response can be any valid entry, 0 through 50. The entry is checked for validity, but otherwise ignored.
DRVEXR, Continued DRVEXR Modes You can run the DRVEXR program in one of the following modes depending on your responses to the dialogue questions: Mode Function Read/Write Writes and reads as many blocks as possible in the given amount of time. Data Integrity Similar to Read/Write mode, but with a ‘‘manual’’ check of data buffers done by the ISE processor. Max Stress Reads the inner DBNs and outer DBNs alternately.
DRVEXR, Continued Mode/Dialogue Relationship The following table shows the relationship between the four test modes and the responses to the six questions in the dialogue: Modes Example Response to Question 1 2 3 4 5 6 Read/Write 1 1 Any Any 0 Any Data Integrity 1 1 Any Any 1 Any Max Stress 0 N/A Any 0 N/A 2 The following is an example of what is displayed when you run DRVEXR.
DRVTST DRVTST Program Description The DRVTST program provides a comprehensive test of the ISE hardware. Errors detected by this program can be isolated to the FRU level. Dialogue The following table describes the DRVTST dialogue: Message Explanation Copyright © 1989 Digital Equipment Corporation No response is expected. Write/read anywhere on the medium? [1=Yes/(0=No)] Do you want to write to the user data area? If you type 0, this is a read-only test.
DRVTST, Continued Error Messages The following table describes DRVTST error messages. Message Description Unit is currently in use. This can mean that the ISE unit is inoperative, in use by a host, or is currently running another local program. Operation aborted by user. This message appears if the user stops the program while it is in progress. xxxx - Unit diagnostics failed. This is a fatal error message where xxxx is the MSCP error code. Call Digital Services. xxxx - Unit read/write test failed.
DRVTST, Continued DRVTST Examples The following is an example of what is displayed when DRVTST runs successfully: Copyright (C) 1990, 1991, 1992 Digital Equipment Corporation Write/read anywhere on medium? [1=Yes/(0=No)] 1 User data will be corrupted. Proceed? [1=Yes/(0=No)] 1 5 minutes to complete. Test passed.
HISTRY HISTRY Program Description The HISTRY program displays ISE information that is used by programs running in the host (such as MDM).
DRINIT DRINIT Program Description The DRINIT program initializes the firmware data structures and on-disk structure of the internal data retention disk. This prepares the EF5XR ISE for saving data in case of a power failure. CAUTION You should not normally need to run DRINIT. Use the DRINIT program with caution, since running it erases the EF5XX. Copyright (C) 1990 Digital Equipment Corporation User data will be corrupted. Proceed? [1=Yes/(0=No)] 1 Test passed.
BATTST BATTST Utility Description BATTST is a utility that allows testing the batteries in an EF51R and EF52R. It also allows for conditioning the batteries to avoid or correct the voltage depression effect that sometimes occurs in nickel-cadmium batteries after a series of incomplete discharges. BATTST operates by continuing to exercise the memory and data retention disk under battery power after external DC power is removed. The time that the batteries lasted is stored in the PARAMS parameter BAT_TEST.
BATTST, Continued Stopping BATTST To stop a BATTST in progress, re-execute the BATTST local program. You will be given an opportunity to abort the test. Aborting BATTST requires the EF5XX to reset itself. Digital recommends running the BATTST utility at least once per year, or whenever a "Battery Maintenance Error" is logged to the error log. This error is logged when EF5XX charging and battery test firmware detect potential problems with the charging or discharging of the batteries.
BATTST, Continued Dialogue The following table explains the BATTST dialogue. Message Explanation Copyright © 1990,1991,1992 Digital Equipment Corporation No response is expected. Test requires the unit power to be removed. Proceed? [1=Yes/(0=No)] Do you want to remove power from the EF5XX? This may affect other drives in the cabinet or may require a system shutdown. Remove external power, Variable BAT_TEST will contain the time Remove power from the EF5XX under test.
BATTST, Continued Example The following is an example of the BATTST utility: Copyright © 1990, 1991, 1992 Digital Equipment Corporation Test requires the unit power to be removed. Proceed? [1=Yes/(0=No)] 1 Remove external power, Variable BAT_TEST will contain the time Test passed. After removing the power and allowing the batteries to drain, the following example shows how to get the test results. In this case, the batteries lasted for 40 minutes and 12 seconds.
MEMTST MEMTST Utility Description MEMTST is a utility that allows testing of the memory modules in EF5XX drives. Various patterns are written and read to the memory arrays to detect problems with the memory devices, address and data buffers, memory control, and ECC logic. Accessing MEMTST Access the MEMTST program the same way you would the other local programs. Once a connection is established, the system prompts you to answer a series of questions.
MEMTST, Continued Dialogue The following table explains the MEMTST dialogue. Message Explanation Copyright © 1990,1991,1992 Digital Equipment Corporation No response is expected. User data will be corrupted. Proceed? [1=Yes/(0=No)] Do you want to overwrite the data in the memory arrays? Test time in minutes? [0 (= 1 pass) <-> 200] Enter the time to run the test. Enter 0 to run the test once on memory module. Testing slot n: Memory module n is currently being tested.
MEMTST, Continued Example The following is an example of a successful run of the MEMTST utility. In this case, each memory module was tested twice and passed. DUP Array Bad Block Test Copyright © 1990, 1991, 1992 Digital Equipment Corporation User data will be corrupted.
MEMTST, Continued To test each memory module just once, use a test time of 0 as shown in the following example. MEMTST will calculate a test time based on the number of memory arrays installed. DUP Array Bad Block Test Copyright © 1990, 1991, 1992 Digital Equipment Corporation User data will be corrupted.
PARAMS PARAMS Utility Description The PARAMS utility allows you to examine and change internal ISE parameters such as node name, allocation class, and MSCP unit number. You can also use PARAMS to display the state of the ISE and performance statistics maintained by the ISE. The PARAMS program is an interactive, customer accessible DUP local program that functions as both a parameter editor (similar to the VMS SYSGEN utility) and a utility to display status, history, and counters.
PARAMS, Continued The following is an example response given to CTRL/G: PARAMS> ^G E1QSAA::MSCP$DUP 26-APR-1990 15:01:51 PARAMS CPU=00:00:01.09 PI=17 PARAMS> Accessing PARAMS PARAMS Process The PARAMS utility is invoked on demand from the user. Once a connection is established, all interaction occurs through the use of commands and responses. PARAMS has its own command line interpreter. PARAMS prompts you for a command at the PARAMS> prompt.
PARAMS, Continued PARAMS Commands Available PARAMS commands are: Name Function ENABLE MSCP Enables MSCP server EXIT Terminates PARAMS HELP Prints a brief list of commands and their syntax LOCATE Causes a soft fault in the ISE to help locate it SET Sets a parameter to a value SHOW Displays a parameter or a class of parameters STATUS Displays information about the drive’s history WRITE Updates the NVR from the cached copy ZERO Clears a block of counters or all known blocks of counters Th
PARAMS, Continued ENABLE MSCP Syntax ENABLE MSCP ENABLE MSCP Parameters EXIT None Use the EXIT command to terminate the PARAMS utility. The message Exiting... displays on the terminal. EXIT Syntax EXIT EXIT Parameters None HELP HELP displays a brief list of the available commands and their syntax.
PARAMS, Continued HELP Example PARAMS> help ENABLE MSCP EXIT HELP LOCATE SET {parameter | .} SHOW {parameter | . /ALL /CONST /DUP /SCS /MSCP /BSS STATUS [type] CONFIG LOGS THREADS MEMORY MSCP PATHS HOURLY VCLOGS WRITE ZERO counter ALL HOURLY MSCP PARAMS> value | /class} DUMP DATALINK BB LOCATE The LOCATE command causes a soft fault in the ISE (it has no effect on its current operation or state) to help find it.
PARAMS, Continued LOCATE Example The following appears on the screen when this command is used: PARAMS> locate Drive has been soft faulted to help locate it Press RETURN to continue: PARAMS> SET Use the SET command to change the value of a given parameter in the cached copy of the NVR image that is maintained by PARAMS. The type and radix of the new value for the parameter is determined by the type and radix of the parameter itself ONLY and not by radix specifiers or quotes in your input.
PARAMS, Continued SHOW Command Examples NOTE Since it is important to view the current value of a parameter before changing it, examples of the SHOW command are included. PARAMS> show add_cr Parameter --------ADD_CR Current -------0 Default Type Radix -------- ------- -----0 Boolean 0/1 PARAMS> set . 1 PARAMS> show . Parameter --------ADD_CR Current -------1 Default -------0 Type Radix -------- ----Boolean 0/1 Default -------0 Type Radix -------- ----Boolean 0/1 PARAMS> set add_cr 0 PARAMS> show .
PARAMS, Continued SHOW Parameters SHOW /Class Examples param-or-class is either the parameter name, possibly abbreviated, or a class name. If you use an abbreviation, the first matching parameter displays regardless of uniqueness. The parameter name may also be the special character "." which displays the most recently-shown parameter. If there is no previously-shown parameter, an error message is displayed. If you use a class name, be sure to prefix it with a slash ("/").
PARAMS, Continued STATUS STATUS displays miscellaneous information such as module configuration, history, current counters, and so forth, depending on the type specified. STATUS Syntax STATUS STATUS Parameters type The type is the optional ASCII string that denotes the type of data desired. You can also abbreviate type; an abbreviation selects all types with matching names. If omitted, all available data are displayed.
PARAMS, Continued MSCP displays MSCP statistics such as the number and type of I/O commands and various histograms. THREADS displays the known programs in the system, the amount of CPU time consumed, and other information. VC displays the last 8 virtual circuit closures. STAT Examples PARAMS> stat conf Configuration: Node EQSAA is an EF51R controller using Apache V1.
PARAMS, Continued PARAMS> stat logs NOTE: bugcheck code is last word on first line of each log.
PARAMS, Continued A WRITE command may fail for several reasons: If a parameter is modified that requires the unit and the unit cannot be acquired. (For example, it is not in the available state with respect to all hosts. Changing the unit number is an example of a parameter that requires the unit.) If a parameter is modified that requires controller initialization and the user replies negatively to the request for reboot.
PARAMS, Continued ZERO Parameters Counter is a block of performance counters or all known counters. Counter types include the following: * All - Clears all performance counter blocks. * MSCP - Clears the MSCP performance counters and histograms. * SEEKS - Clears the seek performance counters and histograms.
Chapter 5 Data Retention System Introduction In This Chapter The EF51R and EF52R ISEs contain advanced hardware and firmware that protect the data in the memory arrays from loss in case of power or other system failure.
EF5XX Data Retention Description Continuously Saving Data Unlike Digital’s earlier ESE20 and ESE50 solid state disks, the EF5XX ISE continuously moves modified data to the internal winchester disk drive. This minimizes the amount of data that must be saved under battery power and ensures that the data retention disk is still functional. Saving of data is a low priority, background task that minimizes the effect of saving data on performance.
EF5XX Data Retention Description, Continued After mounting, users’ requests from the host receive top priority and are satisfied before restore requests. If a user requests data that has not been restored yet, the EF5XX fetches the data from the internal magnetic disk and returns the data to the user. Battery Testing and Monitoring The battery subsystem (BSS) firmware logs a "Battery Maintenance Error" under certain conditions.
EF5XX Data Retention Description, Continued Table 5–1 (Continued) Battery Maintenance Errors Error Reason Battery age. The batteries have had more than 3 years of power-on time and need to be replaced. The number of poweron days until the battery needs to be replaced is available in the parameter BSS_REPL. A value of 0 indicates the age is the cause of the maintenance error. Battery charging out-of-specification. Battery charging time was not within specification. Battery deep discharge.
EF5XX Data Retention Description, Continued Using PARAMS Use the PARAMS local program (Chapter 4) to check the cause of the battery maintenance error. You can use the PARAMS command SHOW /BSS to show all BSS parameters. Except in the case of deep discharge, use the battery test utility BATTST to verify battery health when a "Battery Maintenance Error" appears in the error log.
EF5XX Data Retention Description, Continued Automatic Write Protect The EF5XX can optionally write-protect itself automatically while the battery capacity is insufficient for saving data completely. Automatic write protect is controlled by the parameter BSS_WPLC. The default value of 1 indicates that data should be protected by write-protecting automatically. Comprehensive Battery Test The BATTST local program provides a comprehensive battery test that measures the life of the battery under full load.
Battery Subsystem Parameters BSS Parameter Example The following shows the parameters that control the battery subsystem (BSS).
Battery Subsystem Parameters, Continued Table 5–2 (Continued) BSS Parameter Definitions Parameter Definition BSS_REPL Number of days of battery life left for current battery when the NVRAM was last updated. This value does not represent the run-time value. To update the NVRAM, and thus cause this parameter to reflect the current run-time value, see the BSS_UPNV parameter. BSS_CHRG Number of minutes of charge when the NVRAM as last updated. This value does not represent the run-time value.
Battery Subsystem Parameters, Continued Table 5–2 (Continued) BSS Parameter Definitions Parameter Definition BSS_SHUT This flag determines whether the unit should shut-down before the battery is drained to the point where it may become damaged, and no longer hold a charge. If the flag is 0 (the default), then the battery will continue to discharge until it is dead (that is, data is prioritized above battery life).
Battery Subsystem Parameters, Continued Table 5–2 (Continued) BSS Parameter Definitions 5–10 Parameter Definition BSS_REST This flag is used to reset the initial parameter when a battery is changed. After the battery is changed, the user should set this flag to 1. When the firmware detects the flag has been set (may take up to 1 minute), the firmware will reinitialize it parameters, and reset the flag to 0.
Chapter 6 Troubleshooting Procedures Performing Troubleshooting Procedures In this Chapter This chapter describes: Self-tests Failure indications What you should do if the ISE fails to operate correctly NOTE Remember that repairs to the ISE should be done by Digital Services engineers only.
Performing Troubleshooting Procedures, Continued Self-Tests Power-on Self-Test (POST) The ISE automatically performs a self-test whenever power is applied. This power-on self-test (POST) detects most faults that occur in the ISE. Internal Tests and Calibrations Periodic internal tests and calibrations are performed as a normal part of the operation of the ISE. These tests are run automatically on a periodic basis and cause the device to appear active (although there may be no system activity at the time).
Performing Troubleshooting Procedures, Continued Failure Indications An ISE can fail during initial power-up or during normal operation. The following table describes the states of the LEDs, what these states mean, and what actions you should take. When . . . It means . . . And you . . . The green READY LED is on and the red FAULT LED is off the operating condition is normal can use the ISE.
Performing Troubleshooting Procedures, Continued Before Calling Digital Services If a failure occurs with the ISE, ensure: The ISE has the correct DSSI node ID No other device on the DSSI bus has the same node ID Refer to Chapter 3 to ensure the DSSI node ID is set correctly. If the ID is set correctly and the ISE still fails, call Digital Services.
Index A Accessing local programs, 4–1 using console commands, 4–5 using MDM, 4–7 using VMS, 4–4 B BA400 series installation, 2–2 Battery subsystem, 5–7 Battery testing, 5–3 BATTST, 4–19, 5–5 dialogue, 4–21 BBR, 1–6 C Calibrations, 6–2 Console commands, 4–5 Control functions, 3–4 Controls and indicators BA400 series, 3–3 SF7X, 3–6 Controls and indicators, ISE, 3–1 D Data retention features, 5–1 Device resident program menu, 4–7 Diagnostics, 4–1 DIRECT, 4–9 Documents, related, 1–13 DRINIT, 4–18 Drive mod
ENABLE MSCP command PARAMS, 4–29 EXIT command PARAMS, 4–30 F Failure indications, 6–3 Fault LED, 3–1, 3–4, 3–8, 6–3 H HELP command PARAMS, 4–30 HISTRY, 4–17 I Indicator functions, 3–4 Installation, EF5XX ISE, 2–1 Integrated storage element, 1–4 ISE, 1–4 specifications, 1–7 ISE controls and indicators, 3–1 L Local programs, 4–1 LOCATE command PARAMS, 4–31 M MDM, 4–7 MEMTST, 4–23 dialogue, 4–24 MSCP server, 1–4 Multihost, 1–6 Index–2 O OCP, 3–1 for BA400-series enclosure, 3–3 for SF7X enclosure, 3–6 Op
T W Troubleshooting, 6–1 Write command PARAMS, 4–37 U Utilities, 4–1 Z ZERO command PARAMS, 4–38 Index–3
