WorldMark 4300 Rack Mount Product Guide - NCR

WorldMark 4300 

Rack Mount Product Guide 

B003-0207-A000 

03/98

The product described in this book is a licensed product of NCR Corporation. 

Altra and AVA are trademarks, and Adaptec, the Adaptec logo, AHA, EZ-SCSISelect, SlimSCSI, and SCSISelect are 

registered trademarks of Adaptec, Inc. Catalyst 1900 is a registered trademark of Cisco Systems, Inc. Cirrus Logic is 

a trademark of Cirrus Logic. Inc. DEC is a registered trademark of Digital Equipment Corporation. Digiboard, 

PortServer II, and the Digi logo are trademarks of Digi International, Inc. Ethernet is a trademark of Xerox 

Corporation. Hayes is a registered trademark of Hayes Microcomputer Products, Inc. Hercules is a registered 

trademark of Hercules Computer Technology, Inc. IBM, AT, OS/2, PS/2, and Micro Channel are registered 

trademarks of International Business Machines Corporation. Interphase is a registered trademark of Interphase 

Corporation. LANDesk, Intel, and Pentium are registered trademarks of Intel Corporation. Mylex is a registered 

trademark and DAC960 is a trademark of Mylex Corporation. Novell and NetWare are registered trademarks of 

Novell, Inc. Olicom is a registered trademark of Ing. C. Olivetti and Co., SpA. PROCOMM and PROCOMM PLUS 

are registered trademarks of Datastorm Technologies, Inc. SMC is a registered trademark of Standard Microsystems 

Corporation. Windows, Windows NT, MS-DOS, MS, Word, and Microsoft are registered trademarks of Microsoft 

Corporation. UNIX is a registered trademark of UNIX Systems Laboratories in the United States and other 

countries. All other trademarks are owned by their respective owners. 

It is the policy of NCR Corporation (NCR) to improve products as new technology, components, software, and 

firmware become available. NCR, therefore, reserves the right to change specifications without prior notice. 

All features, functions, and operations described herein may not be marketed by NCR in all parts of the world. In 

some instances, photographs are of equipment prototypes. Therefore, before using this document, consult with 

your NCR representative or NCR office for information that is applicable and current. 

To maintain the quality of our publications, we need your comments on the accuracy, clarity, organization, and 

value of this book. 

Address correspondence to: 

Systems Information 

NCR Corporation 

3325 Platt Springs Road 

West Columbia, SC 29170 

Copyright © 1998 

By NCR Corporation 

Dayton, Ohio U.S.A. 

All Rights Reserved

Table of Contents 

Preface 

Who Should Read This Book .........................................................................................................................vii 

What This Book Covers.................................................................................................................................vii 

Conventions Used In This Book.....................................................................................................................vii 

Related Publications ......................................................................................................................................vii 

World Wide Web Information Access...........................................................................................................viii 

Chapter 1 

Rack Mount System Description 

Introduction.........................................................................................................................................................1-1 

Rack Mount System Overview .............................................................................................................................1-2 

40U Rack......................................................................................................................................................1-2 

Rack Modules...............................................................................................................................................1-3 

Rack Configurations............................................................................................................................................1-5 

Rack Configuration Guidelines.....................................................................................................................1-5 

Typical Rack Configurations.........................................................................................................................1-6 

Rack Mount Modules Overview...........................................................................................................................1-9 

Rack Node Chassis .......................................................................................................................................1-9 

Rack Mounted Console Components.............................................................................................................1-9 

Rack Power Source .....................................................................................................................................1-10 

Rack Mounted Disk Subsystems..................................................................................................................1-12 

Rack Mounted Communications Modules...................................................................................................1-13 

Chapter 2 

Rack Power Management 

Power On/Power Off Procedures..........................................................................................................................2-1 

Rack Power On.............................................................................................................................................2-1 

Node, Disk Array, Console Switch, Monitor, PortServer II, Catalyst 1900 Power On ....................................2-9 

Rack Power Off ..........................................................................................................................................2-10 

Node Chassis Power Off .............................................................................................................................2-11 

Disk Array Power Off .................................................................................................................................2-12 

Console Switch Power Off ..........................................................................................................................2-12 

PortServer II and Catalyst 1900 Module Power Off.....................................................................................2-13 

Controlling Access to Node Power On/Off.........................................................................................................2-14 

Node Boot Process.............................................................................................................................................2-15 

Power On Self Test (POST) ........................................................................................................................2-15 

Booting the Operating Environment ...........................................................................................................2-16 

Node Device Scan Order....................................................................................................................................2-17 

Boot Order..................................................................................................................................................2-17 

UPS LEDs.........................................................................................................................................................2-20 

UPS Battery Backup ..........................................................................................................................................2-25 

Description.................................................................................................................................................2-25 

On UNIX MP-RAS.....................................................................................................................................2-25 

On Windows NT.........................................................................................................................................2-26 

More About Power Supply Calculation .......................................................................................................2-26 

WorldMark 4300 Rack Mount Product Guide 

i

Contents 

Power Monitoring and Power Failure Recovery .................................................................................................2-27 

Chapter 3 

Rack Console Administration 

Console Features and Functions ..........................................................................................................................3-1 

Using the Console Switch....................................................................................................................................3-4 

Saving the Device Settings ...........................................................................................................................3-4 

Making Connections Under Power ...............................................................................................................3-4 

Switching Between Nodes ............................................................................................................................3-4 

Security Features ..........................................................................................................................................3-5 

Resetting the Mouse and Keyboard...............................................................................................................3-5 

Hot Keys .............................................................................................................................................................3-6 

Chapter 4 

Rack Mount Node Description 

Node Features Summary......................................................................................................................................4-1 

Node Features Identification................................................................................................................................4-3 

System Board Set ................................................................................................................................................4-7 

Processor Boards ..........................................................................................................................................4-8 

Processors.....................................................................................................................................................4-8 

Bus Termination Board ...............................................................................................................................4-8 

Memory........................................................................................................................................................4-8 

Add-In Board Slots.......................................................................................................................................4-9 

Video ...........................................................................................................................................................4-9 

SCSI Controllers ........................................................................................................................................4-10 

Keyboard/Mouse Controller........................................................................................................................4-10 

Node Power System...........................................................................................................................................4-11 

Power Supply Module.................................................................................................................................4-11 

Power Distribution Backplane ....................................................................................................................4-11 

Number of Power Supplies in a Configuration ............................................................................................4-11 

Node Security....................................................................................................................................................4-12 

Intrusion Protection....................................................................................................................................4-12 

Software Locks via the System Configuration Utility (SCU) .......................................................................4-12 

Enabling BIOS Security Features................................................................................................................4-13 

Server Management ..........................................................................................................................................4-15 

Server Management Software .....................................................................................................................4-15 

Server Management Hardware....................................................................................................................4-15 

Server Management Functions....................................................................................................................4-16 

About the SMB...........................................................................................................................................4-16 

About the SMM..........................................................................................................................................4-17 

Chapter 5 

Rack Mount Node Servicing 

Service Philosophy ..............................................................................................................................................5-1 

Routine Maintenance...................................................................................................................................5-1 

Serviceable Components...............................................................................................................................5-1 

Servicing Notes ...................................................................................................................................................5-2 

Warnings and Cautions ................................................................................................................................5-2 

Updating the Configuration History File.......................................................................................................5-2 

Installing and Removing the SMB and Connected Modem ..................................................................................5-3 

Servicing Description ...................................................................................................................................5-3 

Removing the SMB ......................................................................................................................................5-5 

Installing the SMB .......................................................................................................................................5-5 

Removing the Internal Modem .....................................................................................................................5-6 

ii 

Table of Contents

Contents 

Installing the Internal Modem ......................................................................................................................5-6 

Using an External Modem ............................................................................................................................5-6 

Installing and Removing Node Power Supplies....................................................................................................5-7 


Removing a Node Power Supply ...................................................................................................................5-8 

Installing a Power Supply .............................................................................................................................5-8 

Installing or Hot-Swapping SCSI Drive ...............................................................................................................5-9 


Tools Required ...........................................................................................................................................5-10 

General Guidelines .....................................................................................................................................5-10 

Drive/Carrier Assembly ..............................................................................................................................5-10 

Install or Hot-Swap Procedure ....................................................................................................................5-10 

Chapter 6 

Remote Support 

Overview.............................................................................................................................................................6-1 

Definitions....................................................................................................................................................6-1 

Software .......................................................................................................................................................6-2 

Remote Access Methods ...............................................................................................................................6-3 

Server Management Board (SMB) ................................................................................................................6-3 

Server Monitor Module (SMM) ....................................................................................................................6-3 

Preparing the Server for Remote Management.....................................................................................................6-4 

Console Redirection.............................................................................................................................................6-5 

Enabling Console Redirection.......................................................................................................................6-5 

How Redirection Works................................................................................................................................6-6 

Keyboard Input.............................................................................................................................................6-7 

Video Display...............................................................................................................................................6-7 

Console Redirection Limitations...................................................................................................................6-7 

Configuring a Remote Support Modem................................................................................................................6-9 

Using NCR Remote ......................................................................................................................................6-9 

Using the Diagnostic Partition Menus...........................................................................................................6-9 

Terms and Definitions .................................................................................................................................6-9 

Modem and System Security.........................................................................................................................6-9 

Other Modem Security Issues......................................................................................................................6-11 

Configuring a Modem.................................................................................................................................6-11 

Accessing the Modem Utilities Menu..........................................................................................................6-12 

Enabling the Remote Support Modem.........................................................................................................6-12 

Using a Remote Password...........................................................................................................................6-14 

Configuring Other Modems........................................................................................................................6-15 

General Modem Configuration Requirements .............................................................................................6-15 

Preparing the Remote Location..........................................................................................................................6-17 

Using NCR Remote ....................................................................................................................................6-17 

Using Other Terminal Emulation Software.................................................................................................6-17 

PROCOMM PLUS Settings ........................................................................................................................6-17 

Keyboard Input...........................................................................................................................................6-19 

Key Mapping for Non-ASCII Keys .............................................................................................................6-19 

Verifying That Remote Support Is Functioning Properly....................................................................................6-21 

Setting Up the Server..................................................................................................................................6-21 

Verifying Remote Management Operation ..................................................................................................6-22 

Disabling Remote Support Passwords and Modem Access .................................................................................6-23 

Disabling Modem Passwords When Operating Remotely ............................................................................6-23 

Disabling Modem Passwords and Access from the Local Server..................................................................6-23 

Disabling Modem Passwords and Access from UNIX MP-RAS ..................................................................6-24 

Disabling Modem Passwords and Access from NT......................................................................................6-24 


iii

Contents 

Transferring Files to and from a Remote Location.............................................................................................6-25 

Using NCR Remote Client for File Transfers..............................................................................................6-25 

PROCOMM Settings..................................................................................................................................6-25 

Downloading Files......................................................................................................................................6-26 

Uploading Files ..........................................................................................................................................6-28 

File Transfer Configuration File .................................................................................................................6-30 

Modem Configuration in UNIX MP-RAS..........................................................................................................6-32 

Enable Console Redirection........................................................................................................................6-32 

Access from a Remote Terminal .................................................................................................................6-32 

Send a String to the Remote Support Modem..............................................................................................6-33 

Setting Modem Passwords in UNIX MP-RAS.............................................................................................6-33 

Other Modem Command Strings ................................................................................................................6-36 

Dialing into a UNIX MP-RAS System...............................................................................................................6-37 

Modem Configuration and Dialing into a Windows NT System.........................................................................6-38 

Using the Server Management Board for Remote Management .........................................................................6-39 

Using the Server Monitor Module for Remote Management ..............................................................................6-40 

Installing the SMM ....................................................................................................................................6-40 

PCMCIA Modem .......................................................................................................................................6-40 

Software .....................................................................................................................................................6-40 

Setting Up UNIX MP-RAS servermon for Console Redirection Support With LANDesk ............................6-41 

Chapter 7 

Troubleshooting 

Codes and Error Messages...................................................................................................................................7-1 

POST Error Codes........................................................................................................................................7-1 

POST Beep Codes ........................................................................................................................................7-1 

POST Codes and Countdown Codes .............................................................................................................7-2 

POST Error Codes and Messages .................................................................................................................7-6 

Resetting the Node ............................................................................................................................................7-10 

Keys ...........................................................................................................................................................7-10 

Initial Node Start........................................................................................................................................7-10 

Node Reset Checklist..................................................................................................................................7-11 

Verifying New Application Software .................................................................................................................7-12 

Checking for Equipment Failure........................................................................................................................7-13 

Testing Node Bring-Up .....................................................................................................................................7-14 

Preparing the Node for Diagnostic Testing .................................................................................................7-14 

Monitoring POST.......................................................................................................................................7-14 

Running System Diagnostics .............................................................................................................................7-16 

Definitions .................................................................................................................................................7-16 

Running Out-of-Service Diagnostics...........................................................................................................7-16 

When Not to Run Out-of-Service Diagnostics.............................................................................................7-16 

Additional Information...............................................................................................................................7-17 

Problems and Solutions .....................................................................................................................................7-18 

Power Light Does Not Light .......................................................................................................................7-18 

Node Boots, Then Shuts Down ...................................................................................................................7-18 

No Characters Appear on Screen ................................................................................................................7-18 

Video Connection to Node Keeps Switching...............................................................................................7-19 

Mouse Moves Erratically or Is Frozen.........................................................................................................7-19 

Incorrect or No Beep Codes ........................................................................................................................7-19 

Characters Are Distorted or Incorrect .........................................................................................................7-19 

Flex Drive Activity Light Does Not Light...................................................................................................7-20 

SCSI Disk Drive Activity Light Does Not Light..........................................................................................7-20 

Cannot Boot from Hard Drive.....................................................................................................................7-21 

Cannot Boot from CD-ROM.......................................................................................................................7-21 

iv 

Table of Contents

Contents 

No Installation Menu When Booting from CD-ROM ..................................................................................7-21 

Missing Boot Path Prompt ..........................................................................................................................7-22 

Problems with Application Software ...........................................................................................................7-22 

BIOS Corrupted During System BIOS Upgrade ..........................................................................................7-22 

Appendix A 

Regulatory Statements and Warranty 

Safety Regulations..............................................................................................................................................A-1 

EMI Emissions and Immunity ............................................................................................................................A-2 

Appendix B 

Telecommunications Platform 

Rack Configurations........................................................................................................................................... B-1 

Rack Modules..................................................................................................................................................... B-5 

Power On/Power Off........................................................................................................................................... B-6 

PortServer II Racks...................................................................................................................................... B-6 

PortServer II/Catalyst 1900 Racks................................................................................................................ B-6 

Powering Off Communications Modules Individually .................................................................................. B-7 

Related Publications ........................................................................................................................................... B-8 


v

Contents 

vi 

Table of Contents

Preface 

Who Should Read This Book 

This book is written for the person who administers the rack mount server system. 

What This Book Covers 

This product guide provides a functional description of the rack mount system and the rack mount 

computing node. It gives information on system-related utilities and applications. 

Conventions Used In This Book 

The following conventions are used throughout this book: 

• Utilities, commands, user names, and package names appear in boldface type. 

• Book titles are printed in italic type. 

• Screen output is printed in courier type. 

• Operator input is printed in courier bold type. 

• Numbered lists denote operations that must be performed in a specific order. Bulleted lists do 

not denote specific order. 

• Menu selections, screen buttons, and keyboard keys appear in courier bold type. 

• Directory names and file names are printed in italic type. 

Related Publications 

Refer to the following for additional information about the rack mount system: 

• WorldMark 4300 Rack Mount Service Guide 

B003-0210-A000 

• WorldMark 4300 Rack Mount Hardware Installation Guide 

B003-0209-A000 

• WorldMark 4300 Rack Mount Site Preparation Guide 

B003-0208-A000 

• WorldMark 4300 Third Party Rack Support Guide 

B003-0102-A000 


vii

Preface 

• WorldMark 4300 Installing MP-RAS 

BST0-2139-6400 

• WorldMark 4300 Installing Windows NT Server 

BST0-2139-6500 

• WorldMark 4300 Server Software Guide (4SMP) 

B003-0108-B000 

• AMIDiag User’s Guide 

BST0-2141-1300 

• AMIDiag Supplement (4SMP) 

BST0-2139-5700 

• WorldMark 4300 Server Support Log 

BST0-2139-5600 

• WorldMark 4300 Server Management Product Manual 

BD20-1398-B000 

• NCR Remote Services User Guide 

BD20-1401-B000 

• NCR PCI SCSI Host Adapter Service Guide 

BD10-4939-B000 

World Wide Web Information Access 

For information about preparing, installing, and configuring the system, see the list of related 

documents in this preface. NCR field engineers may also access documents and information on-line 

through NCR’s Intranet. The following sites provide additional system-specific information: 

• For the NCR Columbia, CSG Server Systems Information Product Library, which provides 

access to server documentation on 345x, 35xx, 3600, 4300, 4700, 5100, and 5150 servers and 

peripheral documentation: 

http://www.columbiasc.ncr.com/techinfo/ 

• For the NCR Learning Design and Development Page, which provides access to self-study and 

on-line courses: 

http://Infobahn.SanDiegoCA.NCR.com/lddcs/ 

• For the Knowledge Center - Logistics and Information Products, which provides access to the 

Technical Publications Catalog and its Table of Contents: 

http://www.tkc.ncr.com/tkc/cxhtml/data/htm/1/infoprod.htm 

viii 

Preface

Chapter 1 

Rack Mount System Description 

Introduction 

The rack mount system is a customer-configurable departmental server system. The modules that 

make up the system are designed for mounting in one or more semi-custom rack assemblies. 

Each rack in a rack mount system contains a power source, either an AC box or an Uninterrupted 

Power Supply (UPS). A single rack may also accommodate the following modules, in valid 

configurations: 

• Computing node (referred to in this guide as the node chassis or system server) 

• Console components, including: 

– VGA monitor 

– Keyboard and mouse 

– Console switch 

• Disk array subsystem chassis, 6210 or 6250 

• Modular entry level disk chassis, 6282-1101 (single-ended JBOD) or 6282-1103 (disk array) 

• Modular disk array chassis, 6285-1220 or 6285-1440 

• PortServer II, PortServer II expansion module 

• Catalyst 1900 switch 

Note: For information about the telecommunications platform, see Appendix B, 

“Telecommunications Platform.” 

WorldMark 4300 Rack Mount Product Guide 1-1

Rack Mount System Overview 


40U Rack 

The rack assembly is referred to as a 40U rack. “U” represents a unit of vertical measurement for 

placement of modules in the rack, as follows: 

1U = 4.445 cm (1.75 in.) high 

Vertical rails at the front of the rack (called EIA rails) have hole patterns that can be used to 

measure U space, as follows: 

3 holes = 1U 

The following figure illustrates the measurements of the standard rack assembly: 

Figure 1-1. 40U Rack 

61 cm 

24 inches 

101.6 cm 

40 inches 

45.1 cm 

17.75 inches 

1U = 

4.445 cm 

1.75 inches 

EIA 

Rails 

195.6 cm 

77 inches 

Stabilizer 

Feet 

Front 

Side 

1-2 Rack Mount System Description


The 40U rack has the following features and specifications: 

• Total rack frame height: 195.6 cm (77 in.) 

• Useable height: 40U 

• Total rack frame width: 61 cm (24 in.) 

• Total rack frame width with side stabilizers: 96.5 cm (38 in.) 

• Useable width: 45.1 cm (17.75 in.) 

• Total rack frame depth: 101.6 cm (40 in.) 

• Total rack frame depth with front and back stabilizers, or side stabilizers: 147.3 cm (58 in.) 

• Rack frame weight (unloaded): 135.9 kg (300 lb.) 

• Load limit: 499.0 kg (1,100 lb.) 

• Cable entry in floor 

• Hinged, vented, and locking rear door 

• Optional screened front door with lock (doorless model includes trim bezel) 

• Removable side panels (removed on side-by-side rack configurations) 

Rack Modules 

A rack may contain the following modules: 

• Node chassis (extendible rails) 

• Console components 

– VGA monitor, 38.1 cm (15 in.) (fixed shelf) 

– Keyboard and mouse (drawer) 

– Console switch (shelf bracket behind VGA) 

• Uninterruptible Power Supply (UPS), unless AC box is present (fixed shelf) 

• AC box, unless UPS is present (fixed shelf at rear) 

• Disk subsystem chassis, 6210 or 6250 (fixed shelf) 

• Modular entry level disk chassis, 6282-1101 single-ended JBOD or 6282-1103 disk array 

(fixed shelf) 

• Modular disk array chassis, 6285-1220 or 6285-1440 (fixed shelf) 

• PortServer II, PortServer II expansion module (fixed shelf at rear) 

• Catalyst 1900 switch (fixed shelf at rear) 



The following table lists the height and approximate weight of each rack mount module. 

Table 1-1. Rack Module Specifications 

Module Height Est. Weight Comment 

VGA Monitor Enclosure 9U 4.536 kg (10 lb) 

Console Switch * 2U, 3U 4.536 kg (10 lb) Uses zero U if mounted behind 

VGA monitor in rack 

Keyboard Drawer 2U 9.072 kg (20 lb) 

Node Chassis 9U 49.9 kg (110 lb) 

6210 Disk Array 4U 34 kg (75 lb) 

6250 Disk Array 8U 113 kg (240 lb) 

6282-1101 Single-ended JBOD 3U 38.3 kg (84.4 lb) 10 drives 

6282-1103 Modular Disk Array 3U 39.3 kg (86.6 lb) Replaces 6210; 10 drives 

6285-1220 Modular Disk Array 10U 111.1 kg(244.8 lb) Replaces 6250; 20 drives; with 

cables and mounting hardware, 

add 13.5 kg (29.9 lb) 

6285-1440 Modular Disk Array 16U 287.6 kg (413.6 lb) 40 drives; with cables and 

mounting hardware, add 13.5 kg 

(29.9 lb) 

PortServer II ** 2U 1 kg (2.25 lb) Mounts on rails at rear of rack. 

Empty space at front of rack 

covered by filler panel. 

PortServer II Expansion Module ** 2U 1 kg (2.25 lb) Mounts on rails at rear of rack. 



Catalyst 1900 Switch** 1U 3.2 kg (7 lb) Mounts on rails at rear of rack. 



UPS 3U 59 kg (130 lb) 

AC Box 2U 3.6 kg (8 lb) Mounts on rails at rear of rack. 


covered by 2U filler panel. 

Filler Panels 1U, 2U, 

or 3U 

-- Used to cover unused U space at 

front of rack 

* Note: 2U and 3U console shelves are available for 4-, 8-, and 16-port console switches. 

** Note: The PortServer II, its expansion module, and the Catalyst 1900 are also available in a 

telecommunications platform. For more information, see Appendix B, “Telecommunications 

Platform.” 


Rack Configurations 


Rack Configuration Guidelines 

The rack mount system can be designed to order, within these general guidelines for rack 

configuration: 

• Heavier components must be at the bottom of the rack. (U-size is not a reliable indicator of a 

module’s weight.) 

• Heavy, high-density components such as disk arrays must be placed above UPSs, or at the 

bottom of the rack if an AC box is present. 

• Rack must contain either UPS or AC box for power. 

• For Windows NT operating system, maximum of 2 nodes per UPS. This requires a Multiple 

Computer Interface Unit (MCIU). 

• For UNIX MP-RAS operating system, one node only per UPS in initial release. MCIU not 

used. 

• VGA monitor/keyboard/mouse are required to manage a processing node. A single 

monitor/keyboard/mouse console may be used to manage multiple nodes, depending on the 

console switch capacity. 

• Console switch may be used to connect monitor to node(s). 

• Maximum of 8 nodes can be connected per console switch. Switches can be paired for a total 

of 16 node connections. 



Typical Rack Configurations 

2 Node/1 6210 DA/Rack Console/2 UPS 

Monitor 

Console 

Switch 

Node 

Node 

Keyboard 

Keyboard 

Node 

Node 

Disk Array 

UPS 

UPS 

UPS 

UPS 

Front 

Side 



4 Node/AC Box 

Node 

Node 

Node 

Node 

Node 

Node 

Node 

Node 

AC 

Box 

Front 

Side 



2 Node/3 6210 DA or 1 6250 DA/2 UPS 

Console 

Switch 

Node 

Node 

Node 

Node 

Disk Array 

Disk Array 

Disk Array 

Disk Array 

Disk Disk Array 

UPS 

UPS 

UPS 

UPS 

Front 

Side 


Rack Mount Modules Overview 


Rack Node Chassis 

The 9U rack mount node chassis loads into the 40U rack on extendible rails. A maximum of four 

nodes can be accommodated in a single 40U rack. 

The rack node is identified by its own product class and model, independent of the rack frame. 

For operating details about the computing node, begin with Chapter 4 of this guide. 

The 9U rack computing node uses Pentium® Pro symmetric multi-processing (SMP) and PCI I/O 

(Peripheral Component Interconnect). It provides the following basic features: 

• Support for one to four Pentium Pro processors 

• Up to 4 GB ECC memory 

Note: If you have more than 2GB DIMM memory, contact your customer service 

representative before installing Windows NT 4.0. 

• Dual PCI buses 

• On-board dual SCSI buses 

• 10 expansion slots (6 PCI, 4 EISA) 

• 6 hot swappable SCSI hard drive bays 

• Hot swappable redundant power supplies 

• Redundant cooling 

• Integrated server management hardware and software 

• 4 removable media bays 

Rack Mounted Console Components 

CAUTION: Use the power cords that come with the power supply (the UPS or AC box), not the 

power cords that come with the console switch or monitor. 

Console Switch 

The console switch is used to connect a single monitor, keyboard, and mouse to multiple server 

nodes in one or more racks. This allows you to administrate multiple computing nodes from a 

single console. 

Note: A separate monitor, keyboard, and mouse can be connected to each node, if preferred. 

The switch is available in 4-port or 8-port models. One 4-port console switch can handle up to 

four nodes. One 8-port console switch can handle up to eight nodes. For systems with more than 

eight nodes, two console switches can be paired to connect up to 16 nodes. 

For operating details, see Chapter 3 of this guide. 

The console switch is a 2U or 3U rack module. It is typically mounted behind a monitor 

enclosure in the rack. In that position, it does not use vertical U space, and is accessible from the 

rear of the rack. 



Monitor 

A 15-inch super VGA monitor can be mounted in a monitor enclosure within the rack. The 9U 

monitor enclosure is a metal shelf with a removable faceplate that borders the monitor screen. 

A 17-inch or 21-inch monitor is available. They do not fit inside the rack, but can be placed on a 

table beside the rack and cabled to the console switch appropriately. 

WARNING: The only module that can be substituted for an NCR-approved module is a 

monitor module. The monitor must meet the following requirements: 

• The monitor must be compatible with the power source's output voltage. Compare the 

monitor voltage rating with the output voltage rating on the rack's nameplate and 

ensure that the monitor is compatible. 

• If the monitor is to be placed in the rack, it must fit the physical requirements of the 

rack. 

Keyboard/Mouse 

A full-size keyboard and a mouse can be accommodated in the 2U keyboard drawer within the 

rack. The drawer pulls out lengthwise and rotates into position. 

Rack Power Source 

Power distribution in a rack is accomplished through either of the following options (never both): 

• 230V output AC box providing 5000W 

• 120V or 230V output UPS (one or more depending on the rack’s power requirements) 

Note: Each UPS can provide up to 2250 W, depending on its power configuration. 

WARNING: If the UPS is for international use, contact your Customer Service 

Representative before powering on the system. (The UPS plug may need to be replaced as 

described in the Hardware Installation Guide.) 

AC Box 

The AC box mounts on a fixed shelf at the rear of the rack, requiring 2U of vertical space. The 

AC box has eight available outlets into which AC power cords of the rack modules may be 

plugged. 

There are two models of AC boxes available. An AC box with eight outlets in a strip and one 

circuit breaker has no cabling specifications. An AC box with eight outlets arranged in two 

groups, with four outlets per group, and two circuit breakers per group, has cabling 

specifications. Refer to the Hardware Installation Guide for AC power cabling specifications. 

UPS 

The UPS mounts on fixed rails, taking 3U of vertical space in a rack. Upon power failure, the 

UPS can provide AC power for 10 minutes for a load of 1600W or less. 



The power consumption requirements of the modules in the rack determine the number of UPS 

units needed. Following are the general power consumption rates of the rack modules: 

Rack node 

1047W 

6250 disk array 517W 

6210 disk array 232W 

6282-1101 single-ended JBOD 272 W 

6282-1103 disk array 323 W 

6285-1220 disk array 758 W 

6285-1440 disk array 1301 W 

Monitor, 15-inch VGA color 

100W 

Monitor, 17-inch VGA color 

120W 

Monitor, 21-inch VGA color* 

160W 

16-port console switch 

30W 

4-port or 8-port console switch 

15W 

PortServer II with up to 3 expansion modules 

50W 

Catalyst 1900 switch 

65 W 

Note: 17-inch and 21-inch monitors do not fit in rack, but can 

be placed beside rack and cabled accordingly. 

Use of a UPS to power a rack node requires special software that runs on the node, and a 

communication cable that runs between the node and the UPS. If two nodes are connected to a 

single UPS, then a Multi-Computer Interface Unit (MCIU) must be installed in the UPS. The 

MCIU allows the UPS to keep track of the nodes that are connected to it. 

Note: If using the UNIX MP-RAS operating system, only one node chassis can be plugged into 

a rack-mounted UPS. If using the Windows NT operating system, up to two node chassis can be 

plugged into a rack-mounted UPS. 

Specific UPS outlets must be used for specific modules in a rack. Refer to the Hardware 

Installation Guide for AC power cabling for a UPS. 



Rack Mounted Disk Subsystems 

The rack accommodates the following disk array models on fixed rails: 

6210 • Series 3 RAID controller support 

• 10 hot plug disk bays 

6250 • Series 4 RAID controller support 

6282-1101 (Singleended 

JBOD) 


• SCSI interconnect for storage 


• 4 GB or 9 GB drives 

6282-1103 • Series 4 RAID controller support 

4U vertical space 


3 U vertical space 












For detailed information on the disk array subsystem, refer to the appropriate user guide for your 

disk array model. 

Note: In addition to the disk array subsystems installed in the rack, the 6000 NCR Storage 

Cabinet and the 6256, 6257, 6273, 6274, and 6277 external disk arrays are also supported. (These 

disk arrays are in stand-alone cabinets; they are not installed in a rack.) 



Rack Mounted Communications Modules 

The rack accommodates two communications modules: the PortServer II and the Catalyst 1900. 

• The asynchronous PortServer II is a terminal and communications server for local and 

remote access on any TCP/IP Ethernet network. 

• The Catalyst 1900 100BaseTX switch provides Ethernet switching to 100BaseT networks 

(available only in the telecommunications platform). 

Note: For information about the telecommunications platform, see Appendix B, 


The modules have the following features. 

PortServer II • 16 high-speed serial ports for each PortServer II or 

PortServer II expansion module 


(rear shelf) 

• Up to three expansion modules can be added to one 

PortServer II, for a total of 64 high-speed serial ports. 

Catalyst 1900 • 2 100Base TX ports 

• 24 10BaseT ports 


(rear shelf) 

CAUTION: Other telecommunications equipment or modules (A/B switches, etc.) are not 

certified for use inside the rack. 




Chapter 2 

Rack Power Management 

Power On/Power Off Procedures 

Rack Power On 

This procedure is for bringing up a complete rack of modules, when all power is removed. It 

addresses applying power to the power source of the rack (UPS or AC box), then to the other 

modules within the rack in appropriate sequence. 

Use the following procedure to power on a rack when all modules are powered off, including the 

rack power source (UPS or AC box): 

Note: This procedure addresses all possible modules that may be contained in a rack. Contents of 

your rack may vary. 

1. Plug the UPS or AC box into the AC wall outlet (if necessary). 

2. Verify that all modules are properly connected to the power source (UPS or AC box) in the 

rack. 

Refer to the Hardware Installation Guide or the Service Guide for AC power cabling. 

3. Turn on the circuit breaker or circuit breakers on the AC box (Figure 2-1), or press the ON 

button on the UPS (Figure 2-2). 

Note: The UPS runs a five-second self-test when you power it on. 

WorlMark 4300 Rack Mount Product Guide 2-1


Figure 2-1. AC Box Circuit Breakers 

AC Outlets (8) 

AC Cord 

Circuit Breaker 

AC Cord 

Circuit Breaker 

AC Outlets (8) 

2-2 Rack Power Management


Figure 2-2. UPS On Button 

On Button 

4. Turn on the power switch on the following modules, if present in the rack, in the following 

order: 

Note: The Catalyst 1900 does not have a power switch. If the power plug is already plugged 

into the power source, the Catalyst 1900 will power on as soon as the power source is powered 

on. Make sure that the Catalyst 1900 completes its power-on self-test (POST) before powering 

on the other modules. For more information, see Appendix B, “Telecommunications Platform.” 

a. PortServer II and attached expansion modules 

b. Console switch 

c. Monitor 

d. Disk arrays 

Note: To power on a 6285-1220 or 6285-1440 modular disk array, power on the disk 

drive modules first, then the controller module. 

e. Nodes 

See the following illustrations for the locations of the PortServer II, console, disk array, and 

node power switches. 



Figure 2-3. PortServer II Power Switch and AC Power Connector 

Power 

Figure 2-4. Console Switch Power Switch and AC Power Cord Connector 

Reset 

One 

Two 

Three 

Aux. 

K 

M 

K 

M 

K M K M 

1 

0 

Power 

Cord 

Connection 

Power 

Switch 



Figure 2-5. 6210 Power Switch and AC Power Connector 

AC Power Connector 

Main On/Off Switch 

Figure 2-6. 6250 Power Switch and AC Power Connector 

Power On/Off 

Switch 

Power 

Cord 

Connector 



Figure 2-7. 6282-1101 Power Switches (Two) 

Fault LED 

Power LED 

Power 

Connector 

Power 

Switch 

Figure 2-8. 6282-1103 Power Switches (Two) 

Fault LED 

Power LED 

Power 

Connector 

Power 

Switch 



Figure 2-9. 6285-1220 Power Switches (Six) 

RS232 BD 

Fault LED 

Power LED 

Power 

Connector 

Power 

Switch (4) 

Power 

Switch (2) 



Figure 2-10. 6285-1220 Power Switches (10) 

RS232 

BD 

Fault LED 

Power LED 

Power 

Connector 

Power 

Power 

Switch (8) Switch (2) 



Figure 2-11. Node Chassis DC Power Switch 

Power Switch 

Node, Disk Array, Console Switch, Monitor, PortServer II, Catalyst 1900 

Power On 

This procedure is for bringing up any one of the modules within a rack individually (usually after 

servicing), when power is present at the rack power source (UPS or AC box). 

Note: If you are powering on a console switch and did not first power off each node connected to 

it, you must reboot each node so it will detect the keyboard and mouse. 

Note: The Catalyst 1900 and PortServer II should be powered on before disk arrays and nodes. 

Note: If you are powering up a disk array, you need to turn on the disk array first, then power on 

the node(s) to which the disk array is connected. To power on a 6285-1220 or 6285-1440 modular 

disk array, power on the individual disk drive modules first, then the controller module. 

Use the following general procedure to power on a node, disk array, console switch, and/or monitor 

in a rack, when the rack power source (UPS or AC box) is on: 

1. Plug the module’s AC power cord into the module. (The other end of the AC power cord 

should still be plugged into the UPS or AC box). 

See the following illustrations for each module’s AC power inlet location: 

– PortServer II and attached expansion modules (Figure 2-3) 

– Console switch (Figure 2-4) 

– Disk array (Figure 2-5 through Figure 2-10) 

– Node (Figure 2-13) 

Note: For the location of the Catalyst 1900’s AC power inlet, see Appendix B, 




2. Turn on the module’s power switch. See Figure 2-3 through Figure 2-11 for the location of 

each module’s power switch. 

Note: If you are powering on a console switch and did not first power off each node connected 

to it, you must reboot each node so that it will detect the keyboard and mouse. 

Note: To power on a 6285-1220 or 6285-1440 modular disk array, power on the individual 

disk drive modules first, then the controller module. 

Rack Power Off 

This procedure is for bringing down all of the modules within a rack and removing power from the 

rack power source (UPS or AC box), in appropriate sequence. 

Use the following procedure to remove power from rack power source (UPS or AC box): 

1. Shut down each node that receives power from the UPS or AC box. See the procedure for 

“Node Chassis Power Off” later in this section. 

2. If the disk arrays that receive power from the UPS or AC box are connected to nodes in other 

racks, shut down those nodes in the other racks. See the procedure for “Node Chassis Power 

Off” later in this section. 

3. Turn off the power switch on each node chassis, disk array, PortServer II, monitor, and 

console switch connected to the UPS or AC box. See Figure 2-3 through Figure 2-11 for the 

switch locations. 

Note: To power off a 6285-1220 or 6285-1440 modular disk array, power off the controller 

module first, then the individual disk drive modules. 

4. Press the UPS Off/Standby button on the front of the UPS (see Figure 2-12) or turn off the 

circuit breaker or circuit breakers on the AC box (see Figure 2-1). 

5. Unplug the UPS or AC box from the AC outlet. 



Figure 2-12. UPS Off/Standby Button 

Off/Standby Button 

Node Chassis Power Off 

Use the following procedure to power off the node chassis: 

Note: All disk arrays attached to the node will be affected. 

1. Set the console switch to the node you want to shut down. 

2. Notify users that the system is about to be shut down. 

3. Stop all programs that are running. 

4. If you have a UNIX MP-RAS operating system, do the following as root: 

a. Type the following at the command line: 

# init 0 

b. Wait for UNIX to shut down DC power to the node chassis. (UNIX automatically turns 

off the DC power switch on the node chassis.) 

If you have a Windows NT operating system, do the following: 

a. Run the Shutdown command. 

b. Wait for the message that it is safe to power off the node. 

c. Turn off the DC power switch on the node chassis. 

5. Unplug the AC power cord from the back of the node chassis. See Figure 2-13. 



Figure 2-13. Node Chassis AC Power Inlet 

AC Input 

Power 

Disk Array Power Off 

Use the following procedure to power off a disk array: 

1. Shut down each node to which the disk array is connected. See the procedure for “Node 

Chassis Power Off” earlier in this section. 

Note: Shutting down a node affects all disk arrays connected to that node. 

2. Turn off the power switch on the disk array. 

Note: To power off a 6285-1220 or 6285-1440 modular disk array, power off the controller 

module first, then the individual disk drive modules. 

3. Unplug the AC power cord(s) from the back of the disk array. 

Console Switch Power Off 

Note: This procedure instructs you to shut down nodes connected to the console switch before you 

turn off the console switch. If you do not shut down the nodes first, you will have to reboot all 

nodes connected to the console switch before the nodes will recognize the mouse and keyboard. 

Use the following procedure to power off the console switch: 

1. Shut down each node to which the console switch is attached. See the procedure for “Node 

Chassis Power Off” earlier in this section. 

2. Turn off the power switch on the console switch. 

3. Unplug the AC power cord from the back of the console switch. 



PortServer II and Catalyst 1900 Module Power Off 

The Catalyst 1900 and the PortServer II and its attached expansion modules should be powered off 

after all other modules are powered off. 

• Use the power switch on the front of the PortServer II to remove power from it and its attached 

expansion modules. 

• The Catalyst 1900 does not have a power switch. To remove power from the Catalyst 1900, 

unplug it from the power source. 


Controlling Access to Node Power On/Off 

Controlling Access to Node Power On/Off 

The node DC power can be turned on or off as summarized in the following table. The different 

methods provide flexibility in controlling how and by whom the node can be powered on or off. 

Power On/Off by Using: 

Front panel power on/off 

switch 

Server management 

hardware and software 

(optional), via an alert action 

Real-time clock/calendar 

(RTC) 

Description 

Pressing the on/off switch is the most common method of turning 

system power on or off. This switch can initiate power-on at any time; 

powering-on in this manner is never blocked by any other system 

function. When the system is on, pressing and releasing this switch 

initiates power-off. However, secure mode prevents turning off the 

system power by using this switch. 

This is typically used to free “hung” systems by toggling power under 

the control of the LANDesk® Server Manager software running on a 

remote console. The Server Management Module (SMM) or Server 

Management Board (SMB) (whichever is connected to the feature 

connector on the system board) provides a power signal line that is 

routed through the system board to the front panel/system board 

interface connector. The board can power the system on or off. 

RTC power control can be used by the BIOS or a utility program to 

power the system on or off at a predetermined time set in the RTC. 

Server management software can also use the RTC to power off the 

system automatically if an over-temperature or over-voltage 

condition occurs. 

WARNING: The DC push-button on/off switch (a convex button) on the front panel DOES 

NOT turn off the system AC power. To remove power from system, you must unplug the AC 

power cord from the back of the node chassis. 


Node Boot Process 


Power On Self Test (POST) 

Each time you turn on the computing node, POST checks the system board, CPU module(s), ECC 

memory module, keyboard, and most installed peripheral devices. 

During the memory test, POST displays the amount of memory that it is able to access and test. 

Depending on the amount of memory installed on the ECC memory module, POST may take 

several minutes to complete the memory test. 

As part of the boot process, the following messages display: 

Press F1 Key if you want to run SETUP 

Keyboard.....Detected 

Mouse........Detected 

If you do not press F1, the above messages remain until the memory test completes. The boot 

process continues, and the system beeps once. 

If you press F1, the following message displays: 

Entering Setup - Please Wait... 

After this message is shown, the boot process continues. When the boot process is complete, the 

BIOS Setup Utility runs. 

When this message displays: 

Press for SCSISelect(TM) Utility! 

Press CTRL + A to configure the onboard SCSI-2 AIC-7880 host adapters to support SCSI devices 

in your server. When the utility displays, follow the instructions on your monitor to configure the 

SCSI-2 AIC-7880 host adapter settings and run the SCSI disk utilities. See the Server Software 

Guide (4SMP) for more information. 

The Press ... message displays twice. It displays once for each instance of the 

onboard SCSI-2 AIC-7880 chip. 

You may see the following message: 

SCSI BIOS not installed! 

This message displays if there are no hard drives connected to the SCSI-2 AIC-7880 chips. Again, 

the message may be displayed twice -- once for each instance of the AIC-7880 chip. 

If you choose not to run the SCSI Select Utility, the boot process continues. After POST 

completes, the system beeps once. 

During the POST process, while the SCSI-2 AIC-7880 chips are installing, the following message 

displays if there are no bootable disk drives on the SCSI bus: 

No SCSI Boot Device Found 

If the server halts before POST completes running, the system beeps, indicating a fatal system 

error that requires immediate attention. Write down the audible beep code (number of beeps and 

sequence); this information is useful to your service representative. For a listing of beep codes and 

error messages that POST can generate, see Chapter 7, “Troubleshooting.” 



Booting the Operating Environment 

When the BIOS POST process and the adapter BIOS scans complete, the system displays the 

following prompt: 

Press D for Diagnostic Boot Path, for Normal Boot Path 

The following table shows your options in responding to the prompt: 

If you... 

Then... 

Press the D key 

Press a key other than D 

Do not respond to the prompt 

Select normal boot and the 

boot fails 

The server boots to the Diagnostic Partition. 

The server boots to your normal operating 

environment. 

The server boots to your normal operating 

environment after 5 seconds. 

The server boots to the Diagnostic Partition 

automatically. 

Note: If you do not receive the prompt, you need to reboot from the Platform CD-ROM and 

install the Diagnostic Partition. See the Server Software Guide (4SMP) for details. 


Node Device Scan Order 


Node devices are initialized and identified in the configuration utilities in the following order: 

• Diskette drive controller 

• EISA/ISA slots 1-4 

• Serial and parallel ports 

• First four (upper) PCI slots (Bus 0, Devices B, C, and D; Bus 1 Device A) 

• Onboard SCSI-2 AIC-7880, Channel A (Bus 1, Device B) 

• Second onboard SCSI AIC-7880, Channel B (Bus 1, Device C) 

• Bottom two PCI slots (Bus 1, Devices D and E) 

Note: IDE devices are not supported for the node. However, if you add an IDE controller, the 

node initializes it immediately after initializing the diskette drive controller. 

The device scan order results in the following: 

• When adding bootable devices, the first such device encountered in the scan order becomes the 

boot device. Therefore, an EISA disk controller can become the boot device (as opposed to a 

drive on SCSI Channel A) unless the BIOS for that EISA device is disabled. 

• If a PCI bridge device is added on Bus 0, the bus numbering shown above changes. The added 

(secondary) PCI bus becomes Bus 1, and the dual peer PCI bus (on the server baseboard) is 

designated as Bus 2. Alternately, if a PCI bridge device is added on Bus 1, this added bus is 

designated as Bus 2. 

Boot Order 

The boot order can be selected using any of the following as determined by the configuration 

utility. 

• Floppy disk 

• Hard Disk 

• CD-ROM 

• Network 

Hard Disk 

If the Hard Disk is selected, the operating system is booted from the first hard drive that contains 

boot code. The scan order for these drives are: 

• Add-in ISA/EISA/PCI board IDE 

• Onboard IDE (not used in 4300) 

• Add-in ISA/EISA board SCSI 

• Add-in PCI board SCSI on the first PCI bus (PCI slot P1, then P2, then P3) 

• Add-in PCI board SCSI on the first slot of the second PCI bus (PCI slot P4) 



• Onboard SCSI (SCSI A, then SCSI B) 

• Add-in PCI board SCSI on the last two slots of the second PCI bus (PCI slot P5 then P6) 

PCI Bus Numbering 

The PCI scan order includes how to determine logical bus IDs with bridge chips. 

The rack mount node is in compliance with the PCI Spec Rev 2.1. The buses are numbered starting 

with the compatibility host bridge as PCI Bus 0. Then, if there are PCI-to-PCI bridges present, the 

buses behind the bridges are numbered sequentially. All buses located behind a PCI-to-PCI bridge 

must be numbered between the bridge’s Secondary Bus Number and Subordinate Bus Number 

(inclusive). 

Both host bridges (compatibility and peer) default to PCI Bus 0 after power-on reset. The memory 

controller is hard-coded to PCI bus 0. The logical PCI bus number of the peer (secondary) host 

bridge may change if PCI-to-PCI bridges are present. 

Figure 2-14 illustrates how buses are numbered when there are no PCI-to-PCI bridged devices. 

The PCI bus on the secondary side of the compatibility bridge is always PCI Bus 0. Because there 

are no other PCI buses, the peer bus is PCI Bus 1. 

Figure 2-14. PCI Bus Numbers Without PCI-to-PCI Bridges Example 

PPro 

PPro 

PPro 

PPro 

P6 Bus 

Compatibility 

Host Bridge 

Peer 

Host Bridge 

PCI Bus 0 PCI Bus 1 

Figure 2-15 illustrates the PCI bus numbering when there are PCI-to-PCI bridges in the system. 

The PCI bus on the secondary side of the compatibility bridge is PCI Bus 0. The secondary side of 

the first PCI-to-PCI bridge found is PCI Bus 1. 

The PCI Bus 1 is scanned (slot P1, then P2, then P3) for other bridges and they are sequentially 

numbered and then scanned for additional bridges. When the scan does not find any other bridges 

on the current PCI bus the scan is continued on the primary side of that bridge. 



Figure 2-15. PCI Bus Numbers With PCI-to-PCI Bridges Example 

PPro 

PPro 

PPro 

PPro 

P6 Bus 

Compatibility 

Host Bridge 

Peer 

Host Bridge 

PCI Bus 0 

PCI Bus ‘X+1’ (4) 

PCI-to- 

PCI 

Bridge 

PCI-to- 

PCI 

Bridge 

PCI-to- 

PCI 

Bridge 

PCI Bus 1 PCI Bus X (3) PCI Bus Y (5) 

PCI-to- 

PCI 

Bridge 

PCI Bus 2 

In this example, PCI Bus 0 scan continues and another bridge is found. In general, this is numbered 

as PCI Bus ‘X’ (in this specific case, PCI Bus 3). After all the buses are numbered on the 

compatibility host bridge, the scan continues from the P6 bus for other host bridges. The bus 

scanning continues for the peer bridge. 

Thus, in this example the peer host bridge PCI bus is PCI Bus 4 and the PCI-to-PCI bridge 

attached to this host bridge is PCI Bus 5. This bus numbering occurs on every power-up of the 

system. 


UPS LEDs 

UPS LEDs 

The LEDs on the front panels of a 120V output and 230V output UPS look and operate the same. 

The LEDs show the status of the UPS. The following tables describe the UPS LEDs and response 

needed (if applicable). 

Figure 2-16. UPS Buttons and On LED 

On LED 

On Button 

Off/Standby Button 

Test/A larm 

Reset Button 

Table 2-1. UPS Buttons and On LED 

Item 

On LED 

On Button 

Off/Standby 

Button 

Test/Alarm 

Reset Button 

Function 

A green LED shows that power is available in the outlets in the 

rear panel of the UPS 

Turns on the UPS and provides power to the outlets in the rear 

panel; the UPS performs a five-second self-test when powered 

on; when the UPS is unplugged from the AC wall outlet power 

can be run from the battery by pressing the On button for three 

seconds 

Turns off the UPS and places the UPS on standby; to completely 

turn off the UPS, you must unplug the UPS from the AC wall 

outlet 

Turns off the alarm (the alarm sounds when there is a problem 

with the UPS); runs a self-test when pressed for three seconds 


UPS LEDs 

Figure 2-17. Site Wiring Fault, Battery Service, and Comm Port LEDs 

Site Wiring 

Fault 

Comm. Port 

Activity 

Battery Service 

Table 2-2. Front Panel LEDs 

LED Description Explanation Response 

Site Wiring Fault Off Normal operation None 

Red 

Large voltage 

difference between 

ground and neutral; 

response depends 

on site configuration 

Battery Service * Off Normal operation None 

Communication 

Port ** 

Red and 

alarm active 

Green, 

steady 

Green, 

flashing 

Potential battery 

failure detected 

Node is establishing 

communication 

Data is being 

transferred between 

node and UPS 

If wiring is line to line, this is 

expected. (This LED can be 

disabled through the configure 

mode). If wiring is line to 

neutral, there is a wiring fault 

that should be corrected 

Push the Test/Alarm Reset 

button; if LED stays on, 

batteries may need replacing 

None 

None 

* Note: UPS batteries must be replaced every three years to meet the rated backup time. 

The customer is responsible for purchasing the replacement batteries. 

** Note: LED activates only with monitoring software and cable. 


UPS LEDs 

Figure 2-18. AC Input LEDs 

AC Input 

Table 2-3. AC Input LEDs 

AC Input 

LED 

Description Explanation Response 

Top Off Normal operation None 

Upper 

Middle 

Lower 

Middle 

Red, steady 

Red, flashing 

Indicates an 

overvoltage condition 

(line is too high); the 

UPS is operating on 

batteries 

Indicates a preexisting 

overvoltage 

condition at time of 

battery shutdown 

Green AC input is OK None 

Green 

AC input is 

abnormally low, but 

the UPS is not on 

battery power 

None (if normal AC input returns 

before battery shutdown, the LED 

turns off) 

When normal AC input returns after 

battery shutdown, push the Test/Alarm 

Reset button to make the LED stop 

flashing 

None 


UPS LEDs 

AC Input 

LED 

Description Explanation Response 

Bottom Off Normal operation None 

Red, steady 

Red, flashing 

Indicates that AC 

input is too low (power 

failure) and the UPS is 

operating on batteries 

Indicates a preexisting 

low voltage 

condition at time of 

battery shutdown 

None (if normal AC input returns 

before battery shutdown, the LED 

turns off) 

When normal AC input returns after 

battery shutdown, push the Test/Alarm 

Reset button to make the LED stop 

flashing 

Figure 2-19. Battery Charge LEDs 

Battery Charge 

Note: All LEDs are green when the battery is fully charged. As the loads use battery power, the 

green LEDs turn off one at a time from top to bottom. When the battery is charging, the LEDs turn 

on one at a time from bottom to top. 

Table 2-4. Battery Charge LEDs 

Battery Charge 

LED 

Description 

Explanation 

Top Green Battery charge > 90% 

Upper Middle Green Battery charge > 66-90% 

Lower Middle Green Battery charge > 33-66% 

Bottom Red Battery low; 3-5 minutes left depending 

on battery backup configuration 


UPS LEDs 

Figure 2-20. Load Level LEDs 

Load Level 

Note: The load level LEDs show how much power the loads are drawing from the UPS. 

Table 2-5. Load Level LEDs 

Load Level 

LED 

Description 

Explanation 

Top Off Normal operation 

Red Overload (load currents or watts exceed full load 

capacity of UPS) 

Upper middle Green Load current or watts (whichever is higher) > 66- 

100% 

Lower middle Green Load current or watts (whichever is higher) > 33-66% 

Bottom Green Load current or watts (whichever is higher) > 5-33% 


UPS Battery Backup 


Description 

UPS battery backup allows a system to continue operating following the loss of AC power. During 

a momentary outage, the UPS provides power for uninterrupted normal operation. After an 

extended outage, the UPS provides power for a graceful shutdown. The UPS configuration 

determines how much battery time is available for normal system operation and/or graceful 

shutdown during an outage. 

Upon loss of AC, the UPS signals the attached node(s) through the serial cable connection. The 

system must be set up appropriately to react to the loss of AC in an acceptable manner. 

The following software is used to accomplish node shutdown: 

• PowerMon II® for UNIX MP-RAS systems 

• LanSafe III for Windows NT systems 

WARNING: System shutdown activities are dependent on configuration and application. 

You should test your shutdown and/or flush-timing to make sure that the PowerMon or 

LanSafe shutdown configuration time settings are correct. Do not expect or configure a UPS 

to provide more than 10 minutes of support for a load of 1600W or more. A new UPS may 

actually work longer, but as batteries age, the backup time will approach the 10-minute 

threshold. Make sure that fresh batteries are installed every three years. (Cost of the batteries 

is the responsibility of the user.) 

On UNIX MP-RAS 

The PowerMon II software package used on UNIX MP-RAS can be configured in either of two 

ways: 

• Power fail recovery mode 

• Orderly shutdown mode 

For complete details about PowerMon II, refer to the PowerMon II software manual. 

Power Fail Recovery 

The power fail recovery mode works only with applications that are compliant with the power fail 

recovery process. In power fail recovery mode, the system saves the contents of memory to disk 

upon loss of AC. When AC recovers, the system will restart where execution halted at the time of 

AC loss. 

Once the power fail shutdown is initiated due to AC loss, the process will not be aborted if AC is 

restored before the completion of flush-to-disk operation. 



Be sure that the memory can be fully flushed before exhaustion of the UPS batteries. In general, it 

is best to allocate most of the backup time for flushing data to disk. That is, the flush should be 

initiated 10 to 15 seconds after AC is lost, leaving all of the remaining battery backup time for 

flushing to disk. The UPS provides 10 minutes of backup for a load of 1600W or less. If a node 

has more memory than can be flushed in 10 minutes, then backup time of the UPS can be increased 

by reducing the loading on the UPS. A UPS loaded with only one node (no other modules) will 

provide backup for 15.5 minutes. 

Orderly Shutdown 

In the orderly shutdown mode, when AC power is lost, the node alerts users that the system has 

gone on backup power and will shut down in a specified (configurable) period of time. The system 

will run normally until the shutdown timer expires, then terminate applications and power off. 

If AC is restored before the shutdown starts, the shutdown will be aborted and the system will 

continue to run. 

If your system can shut down quickly, you can set the shutdown timer value to be a majority of the 

available backup time, leaving enough of the backup time for the system to shut down. 

Alternatively, if the system requires a long time to shut down, as with a node connected to a RAID 

system, you decrease the shutdown time value, thus allowing more UPS support time. 

In an orderly shutdown, the process will be similar to an init 0 command. 

On Windows NT 

The operation of LanSafe for Windows NT systems is similar to the orderly shutdown on UNIX 

MP-RAS, as described in the preceding section. For complete details on LanSafe III Power 

Management, see the LanSafe software manual. 

More About Power Supply Calculation 

For more information on calculating the power requirements of a rack system, see the Site 

Preparation Guide or the Service Guide. 


Power Monitoring and Power Failure Recovery 


For information about power failure, power failure recovery, and configuring power monitoring 

software, see the user guide delivered with the software. 




Chapter 3 

Rack Console Administration 

Console Features and Functions 

The rack mount console may consist of the following modules: 

• Keyboard/Mouse 

• Monitor 

• Console Switch 

The keyboard, mouse, and monitor provide the communication interface between user and multiple 

nodes. Communication to the nodes is controlled by a console switch. 

The console switch enables the use of a single keyboard, mouse, and monitor for multiple nodes. 

You can switch between nodes through the console switch interface, known as “Oscar.” You type a 

command at the keyboard or select one with the mouse. The console switch interface then transfers 

control of the keyboard/mouse and monitor to the selected node. 

Figure 3-1 shows a single console switch configuration connecting four nodes to a keyboard, 

mouse and monitor. One 4-port console switch can handle up to four nodes. One 8-port console 

switch can handle up to eight nodes. For systems with more than eight nodes, two console switches 

can be paired to connect up to 16 nodes, as shown in Figure 3-2. 

The switch is available in 4, 8 and 16-port configurations. It provides on-screen configuration and 

activity reporting, programmable node scanning, NVRAM for saving configuration parameters, 

and an external reset switch. 

Note: For supplemental information on the console switch, see the User Guide that came with 

your system. 



Figure 3-1. 4 Port Console Switch Configuration 

Monitor 

Keyboard 

Mouse 


Node 1 

Keyborad 

Mouse and 

Monitor 

Cables 

Node 2 

Node 3 

Node 4 

3-2 Rack Console Administration


Figure 3-2. Paired Console Switch Configuration 

RJ45 

Interconnecting 

Cables 

Monitor 


Node 1 

Node 2 

Node 3 

Keyboard 

Mouse 


Node 9 

Node 10 


Using the Console Switch 


Saving the Device Settings 

Device settings need to be saved in the console switch’s non-volatile memory (NVRAM) when any 

of the following occurs: 

• The console switch is initially powered-up 

• Nodes are added or removed from the rack mount system 

• There is a change in the keyboard, mouse, or monitor 

Note: If device settings are not saved and the power to the console switch is lost, it may be 

necessary to reboot each node in the system to re-establish keyboard and mouse communications. 

Perform the following to save the device settings in the console switch’s NVRAM: 

1. Press Print Screen. The OSCAR selection window appears on the display. 

2. Press F2 and the Advanced menu window appears. The highlight is in the Commands menu. 

3. Using the Up and Down arrow keys, move the highlight to Snapshot and press Enter. The 

device settings are now saved to NVRAM. 

Making Connections Under Power 

You can connect additional nodes to the console switch while it is running. When you power up the 

newly connected node, the console switch recognizes it, and you can switch to the new node 

without taking any additional steps. 

You can also connect the mouse, keyboard, and/or monitor to the console switch while the system 

is powered up. When you connect a new device, the console switch recognizes it, and configures it 

to the settings of the currently selected node. This allows replacement of failed devices without 

having to restart the system. 

Switching Between Nodes 

Switching disconnects the keyboard, mouse, and monitor from one node in the rack mount system 

and connects them to another. 

Perform the following to switch between nodes: 


Note: The nodes are listed in order by port or by node name, depending on user-definable 

settings in OSCAR menu attributes. 



2. To select a node, do one of the following: 

a. Using the Up and Down arrow keys, select the node you want and press Enter. 

b. Press the numeric key that corresponds to the node’s port number and press Enter. 

c. Move to the node you want using the mouse and double click your selection. 

3. Press Escape to exit OSCAR and remove the OSCAR selection window from the display; the 

status flag window returns to the display to indicate the currently connected node. 

Security Features 

The console switch provides for system security through the OSCAR interface. This security 

provides a simple keyboard and screen lock. 

The security screen is displayed by selecting Advanced Menus, Setup, Security. You must 

always provide a password to access the fields on the screen. The default password is oscar. 

You can change passwords, set wait-time for locking to take effect, and set low power mode for 

monitors so configured. 

Resetting the Mouse and Keyboard 

If the mouse and keyboard are not working properly, (for example, no cursor response), you may 

need to reset the mouse and keyboard. Resetting them attempts to restore the correct settings for 

the selected node. Perform the following to reset the mouse and keyboard: 


2. Press F2 and the Advanced menu window appears. The highlight is in the Commands menu. 

3. Using the Up and Down arrow keys, move the highlight to Reset and press Enter. The mouse 

and keyboard are now reset. 

If the mouse or keyboard are still locked up, you can push the reset button on the back panel to 

reset the console switch. Pressing the reset button may allow you to recover the device settings 

without power cycling the nodes. 


Hot Keys 

Hot Keys 

Use the keyboard’s numeric pad to enter the following numbers and symbols when needed: 

To Perform This Function 

Set slow mode⎯node emulates an 8 MHz CPU. 

The setting can be changed to slow to debug 

potential timing problems in the server. 

Set fast mode⎯node runs at the rated speed of 

the CPU. 

Increase the volume of the click made when a 

key is pressed. 

Decrease the volume of the click made when a 

key is pressed. 

Secure your server immediately. 

Press These Keys 

CTRL+ALT+1 

CTRL+ALT+2 

CTRL+ALT and + 

CTRL+ALT and - 

(You can specify a hot-key combination for 

this purpose with the SCU or BIOS Setup 

Utility.) 


Chapter 4 

Rack Mount Node Description 

Node Features Summary 

The following table summarizes the features of the rack mount computing node. 

Feature 

Modular board set 

Add-in board support 

Hot swap-capable 

backplane 

6 SCSI-2 hard drive hotswap 

bays 

Four removable media 

drive bays 

Power supply 

Description 

Node is intended for use with a modular board set based 

on Pentium® Pro technology. It supports from one to four 

processors and up to 4 GB of memory. 

10 expansion slots (6 PCI, 4 EISA) are available for addin 

boards. 

A hot swap-capable backplane is part of each 3.5-inch 

drive bay assembly for SCSI drives. The backplane 

supports wide and fast SCSI-2 devices that use the 

industry standard 80-pin Single Connector Attach (SCA) 

connector. The backplane consists of two rows of three 

drive connectors. 

Drive status is monitored to detect failing drives and to 

control LED indicators. Critical event data and drive 

status is reported over the I 2 C bus and logged for server 

management software to interpret. 

SCSI drive chassis can hold six 3.5-inch SCSI-2 hard 

drives. Drives are mounted in plastic carriers to enable 

hot-swapping of drives. Carriers have locking handles to 

secure drive/carrier assemblies in SCSI bays. The bays 

are secure behind a lockable metal EMI door. (Node 

faceplate must be removed to access SCSI bay door.) 

The array of drives allows easy setup of RAID 

applications. 

Four externally accessible 5.25-inch half-height bays are 

available for diskette, CD-ROM, and/or tape drives. 3.5- 

inch diskette drive is mounted in 5.25-inch carrier for 

insertion in any of these bays. 

Caution: Do not put hard drives in the 5.25-inch halfheight 

bays. The EMI generated by hard drives and the 

increased susceptibility to ESD may damage the drives. 

From one to three self-contained 625-watt autoranging 

power supplies are easily removed/installed for service. 

Power supplies can be hot-swapped in nodes configured 

for redundancy. 


Node Features Summary 

Feature 

Cooling fans 

Security 

Software-related utilities, 

setup 

System management 

Description 

Pair of dual fan assemblies at front of node chassis 

provide cooling for boards and drives; redundancy in 

case of single fan failure. Air flow is from front to rear. 

Each power supply has an integral cooling fan. 

Intrusion sensor (on inside wall making contact with top 

cover of node chassis) disables power to node when top 

cover is removed. 

BIOS: Password enable; secure mode power-off disable. 

Diagnostic Partition, BIOS Setup, System Configuration 

Utility (SCU), SCSI Select Utility. 

Inter-Integrated Circuit interface (I 2 C) for diagnostic and 

intra-chassis communication. 

4-2 Rack Mount Node Description

Node Features Identification 


The following figure identifies the components and connectors located at the rear of the node 

chassis: 

Figure 4-1. Rear of Node Chassis 

Parallel 

Port 

Com 1 

Mouse 

Keyboard 

Com 2 

VGA 

SMB 

Power Supplies 

AC Input 

Power 

Expansion Slots 

Item 

Mouse 

Keyboard 

Com1 

Description 

PS/2-compatible 6-pin connector. Keyboard and mouse 

connectors are identical. 

PS/2-compatible 6-pin connector. Keyboard and mouse 

connectors are identical. 

Serial port 9-pin connector. To SMB Comm In port. 



Item 

Com2 

Parallel Port Connector 

(LPT1) 

VGA 

Server Management 

Board (SMB) 

Power Supplies 

AC Input Power 

Expansion Slots 

Description 

Serial port 9-pin connector (COM2). To UPS serial port or 

MCIU. 

25-pin connector, parallel port. 

15-pin connector, monitor. 

Hot-plug board, enables monitoring of node functions. 

Remote node management capability. 

SMB LEDs 

Left Reserved for future use 

Right Green = SMB ready 

3 maximum in 3 bays, numbered left to right 

Quantity Redundancy Considerations 

One Entry-level system (non-redundant) 

Two High-end system (redundant for most 

configurations) 

Three High-end system (required for redundancy in 

certain heavily loaded system configurations) 

Power Supply Status LED 

Green light, visible through fan grate 

On Power supply good 

Off Power supply failed (if power is on) 

Single input for 120/220 volts. 

Card cage for add-in boards, 6 PCI, 4 EISA. 



The following figure identifies the components and controls located at the front of the node chassis. 

Note that the faceplate is removed: 

Figure 4-2. Front of Node Chassis 

Control Panel 

A B C D E F 

LCD 

SCSI Drive 

Bays 

SCSI Drive 

LEDS 

Removable 

Media 

Bays 

Bracket 

Faceplate 

Item 

Control Panel 

A 

B 

C 

D 

E 

F 

Description 

Board includes power and reset switches, system speaker, LED indicators, 

LCD interface, and chassis intrusion switch connectors. Visible switches 

and LEDs are listed below. 

DC power switch (convex button). May be disabled through BIOS secure 

mode. 

Caution: DC power switch DOES NOT turn off AC power to the node. To 

remove power from node, you must disconnect the AC power cord from 

the node chassis. 

Reset switch (concave button). Causes hard reset; power-on self test 

(POST) will run. May be disabled through BIOS secure mode. 

Power-on LED, green. When lit, power is present (+5Vdc). When off, 

power is turned off or power source is disrupted. 

Power-fail LED, yellow. When lit, power supply failed or node intrusion 

occurred (top cover removed). 

Cooling-fail LED. Unused. 

Drive-fault LED, yellow. General indicator that a drive has failed. See 

“SCSI Drive LEDs” in this table. 



Item 

LCD 

Removable Media 

Bays 

SCSI Drive Bays 

SCSI Drive LEDs 

Description 

Displays processor type ID, error and diagnostic information in two lines of 

16 characters each. Display can be modified through System 

Configuration Utility (SCU). 

4 available 5.25” half-height bays to accommodate tape, CD-ROM, and 

flex drives. 3.5” flex drive is mounted in 5.25” carrier. 

6 hot-swap bays, stacked 3 on top, 3 on bottom. Accessible by removing 

node faceplate and opening SCSI bay door. Each drive has set of three 

LEDs, visible through cutout in bay door just above each drive. 

Power 

LED 

Activity 

LED 

Fault 

LED 

Description 

On Off Off Drive powered on, no activity 

On Blink Off Drive powered on and being accessed 

Off Off On Drive powered off; fault condition. Drive 

CAN BE replaced at this time. 

On Off Slow 

Blink 

Drive powered on, in recovery mode (i.e., 

drive array being rebuilt). Drive SHOULD 

NOT be replaced at this time. 

Note: Assumes that a SCSI host controller is installed to send SAF-TE 

signals to the drive fault LED 


System Board Set 


The board set includes the following: 

• System board 

• One or two processor boards 

• Memory board 

• Bus termination board (required if only one processor board is installed) 

The following table summarizes the system board features. 

System Board Feature 

Multiple processor support 

Upgradable memory 

Add-in board support 

SCSI controllers 

BIOS 

Video 

External device connectors 

Clock 

System hardware 

monitoring 

Configuration utilities 

Description 

Two slots (primary and secondary) for processor boards; 

up to four Pentium® Pro microprocessors (two on each 

processor board). Node may include one processor board 

and one bus termination board, or two processor boards. 

One slot for memory board. Two board types available: 

- 2 GB memory board supports 16 SIMM devices for a 

minimum memory size of 32 MB up to a total of 2 GB of 

memory. 

- 4 GB memory board supports 16 DIMM devices for a 

minimum memory size of 512 MB up to a total of 4 GB of 

memory. Note: If you have more than 2GB DIMM 

memory, contact your customer service representative 

before installing Windows NT 4.0. 

Four dedicated EISA bus slots on system baseboard. 

Six dedicated 32-bit PCI slots on system baseboard. Dual 

(peer) bus architecture. 

Two onboard SCSI-2s; fast and wide SCSI channel 

support (PCI-based). 

Flash memory-based BIOS (Basic Input/Output System) 

and Setup utilities. 

Integrated super VGA controller chip with 1 MB of video 

memory. 

Onboard connectors for two serial ports, parallel port, 

PS/2-compatible keyboard and mouse, and VGA monitor. 

Real-time clock/calendar (RTC) chip. 

Detects chassis intrusion and contains sensors for 

temperature, voltage, and fan failure. 

System Configuration Utility (SCU) and SCSI Select 

Utility. 



Processor Boards 

The node can include one or two processor boards, supporting up to four Pentium Pro processors 

(two per board). Each processor board has two processor sockets. 

The system board has a primary connector and a secondary connector for the processor boards. 

The processor board contains termination circuitry required by the GTL+ signaling environment, 

DC to DC converters for power to each processor and termination circuitry, and logic for I 2 C 

support and clock ratio programming. 

Processors 

The server supports the following types of processors: 

• Single 166 MHz and 200 MHz Pentium Pro with integrated 512 KB write-back cache 

• Dual 166 MHz and 200 MHz Pentium Pro with integrated 512 KB write-back cache 

• Dual 200 MHz Pentium Pro with integrated 1 MB write-back cache 

You can upgrade a system with a single processor per board to two processors per board with a 

processor upgrade kit. In addition, the server provides an upgrade path to future processor speeds 

and cache sizes. 

CAUTION: You cannot mix processor speeds within a single node. For example, you can have up 

to four 166 MHz or four 200 MHz Pentium Pro processors, but not both. Future processor 

releases may have different cache sizes. You cannot mix processors with different cache sizes 

within the same node. 

Bus Termination Board 

If only one processor board is installed, a bus termination board must be installed in the secondary 

connector. The termination board provides GTL+ signal termination and voltage regulation. 

Memory 

The memory subsystem consists of the following: 

• Memory chipset 

• Memory board connector on the system board 

• Memory board 

The system board contains the data path and data control portions of the chipset. Two different 

memory boards are supported: 

• 2 GB board using SIMMs 

• 4 GB board using DIMMs 



Note: Only use SIMMs or DIMMs approved for use in this server system. Call your customer 

service representative for information 

2 GB Memory Board 

The 2 GB memory board contains the buffer devices from the chipset and 16 72-pin SIMM sockets 

for a total of up to 2 GB of system memory, using 128 MB DRAM SIMMs. SIMM sockets on the 

board are organized as two 72-bit wide, 2- or 4-way interleaved banks. For example, a 4-way 

interleaved bank requires 8 SIMMs. SIMM sockets accept 72-pin, single- or double-sided SIMMs. 

Note: 1-way interleaved banks are no longer supported. 

A bank must be populated using identical pairs of SIMMs. SIMMs may vary from one bank to 

another. 

4 GB Memory Board 

The 4 GB memory board contains the buffer devices from the chipset and 16 168-pin DIMM 

sockets for a total of up to 4 GB of system memory, using 128 MB and 256 MB DRAM DIMMs. 

DIMM sockets on the board are organized as two 72-bit wide, with 4-way interleaved banks. 

DIMM sockets accept 168-pin single- or double-density DIMMs. 

DIMM must be placed in groups of four identical DIMMs. DIMMs may vary from one bank to 

another. 

CAUTION: If you have more than 2GB DIMM memory, contact your customer service 

representative before installing Windows NT 4.0. 

Add-In Board Slots 

The system board has four EISA bus slots for add-in boards. The EISA bus is an extension of the 

Industry Standard Architecture (ISA) bus. Because EISA is fully backward-compatible with ISA, 

you can install old or new ISA add-in boards in your server. 

The system board has six PCI (Peripheral Component Interconnect) bus slots for add-in boards. 

The PCI subsystem consists of two I/O bus segments, PCI Bus #0 and PCI Bus #1. PCI Bus #0 is 

the primary (compatibility) bus; it connects the processor bus to a PCI/EISA bridge and three PCI 

connectors. PCI Bus #1 connects the processor bus to two embedded fast/wide SCSI controllers 

and three PCI connectors. 

Video 

The onboard, integrated Cirrus Logic CL-GD5424 super VGA controller (ISA) is fully compatible 

with these video standards: 

• CGA 

• EGA 

• Hercules Graphics 

• MDA 

• VGA 



The standard system configuration comes with 1 MB of onboard 70 ns video memory. The SVGA 

controller supports only analog monitors (single and multiple frequency, non-interlaced) with a 

maximum vertical retrace non-interlaced frequency of 75 Hz. 

With 1 MB memory, the video controller supports 132-column text modes and high resolution 

graphics with up to 1280 x 1024 x 16 colors. Depending on the environment, the controller 

displays up to 64,000 colors in some video resolutions. 

SCSI Controllers 

The system board includes two embedded fast/wide SCSI-2 controllers (Adaptec AIC-7880, 

compatible with Adaptec AIC-7870), Channels A and B, integrated as PCI bus masters. The 

controllers support data path widths of 8-bits (fast SCSI) at a data transfer rate of 10 MB/sec and 

16-bit (fast/wide SCSI) at a data transfer rate of 20 MB/sec. As PCI bus masters, these controllers 

support burst data transfer rates up to the maximum of 133 MB/sec. 

You can connect up to seven 8-bit narrow SCSI devices or typically up to ten 8-bit narrow and/or 

16-bit fast/wide SCSI devices to each channel. Devices can be disk drives, tape drives, optical 

media drives, and others. 

The SCSI drive backplane is configured as one SCSI bus. The backplane automatically terminates 

the full 16-bit-wide bus. 

Keyboard/Mouse Controller 

The keyboard/mouse controller is PS/2-compatible. You can specify (through the BIOS Setup 

Utility) that the system be locked automatically if there is no keyboard or mouse activity for a 

predefined length of time. Once the inactivity timer has expired, the keyboard or mouse does not 

respond until you enter the password stored previously in the keyboard controller. 


Node Power System 

Node Power System 

Power Supply Module 

A node may be configured with one, two, or three 625W power supplies. 

Each power supply module in the node has the following features: 

• 625 watts 

• Self-contained; hot-swappable if redundant 

• A 120 mm cooling fan integrated within each power supply enclosure 

• Built-in thermal protection if air flow through the power supply is reduced sufficiently to cause 

damage 

• Built-in overvoltage and overcurrent protection 

All output grounds connect to the power supply chassis and to earth ground through the AC line 

cord. 

(The node AC power cord is connected to the power source in the rack, either a UPS or AC box.) 

Power Distribution Backplane 

Each power supply docks into a power distribution backplane inside the node chassis. The 

backplane provides connections for the DC power signals and status and control functions, such as 

server management features (quantity, location, and reporting of installed and failed supplies), 

through I 2 C control. 

The node can sense an overvoltage condition on the +3.3 Vdc, +12 Vdc, and +5.1 Vdc outputs for 

each supply. If the node senses an overvoltage condition, the power supply shuts down and latches 

off until you press the front panel power switch off (for several seconds) and then on again. 

Number of Power Supplies in a Configuration 

In a node with more than one supply, power is drawn equally from all supplies present (from one to 

three). A node with two power supplies can be fully loaded (all drive bays and add-in board slots 

filled). 

Two (or three) supplies use a forced current-sharing technique that ensures that the supplies share 

within 10% at full load. In a high-access node with three power supplies, the third supply gives 

redundancy, because the load is redistributed if one supply fails. 


Node Security 

Node Security 

Intrusion Protection 

The node contains an intrusion switch, mounted on the inside wall in contact with the top cover. 

Power to the node is disabled when the top cover is lifted. 

CAUTION: The intrusion switch does not remove AC power from the node. To remove AC power 

from the system, you must disconnect the AC power cord from the node. 

Software Locks via the System Configuration Utility (SCU) 

The SCU has software features that let you control access to one or more parts of the system in the 

following ways: 

• Enable the keyboard lockout timer so that the server requires a password to reactivate the 

keyboard and mouse after a specified time-out period⎯1 to 128 minutes 

• Set and enable an administrative password 

• Set and enable a user password 

• Set secure mode to prevent keyboard or mouse input and to prevent use of the front panel reset 

and power switches 

• Activate a hot-key combination to enter secure mode quickly 

• Disable writing to the diskette drive when secure mode is set 

Using Passwords 

For complete information on using passwords, see the table in the “Security Settings and System 

Boot” section in Chapter 6. 

Secure Mode 

You can use the SCU to enable and configure the secure boot mode. When secure mode is in effect, 

note the following: 

• You can boot the system to get the operating system running, but you must enter the user 

password to use the keyboard or mouse. 

• You cannot power-off or reset the system with the front panel switches. 

Secure mode has no effect on functions enabled via the server management board or power control 

via the real-time clock/calendar. 

Taking the system out of secure mode does not change the state of system power. That is, if you 

press and release the power switch while secure mode is in effect, the system does not power-off 

when secure mode is later removed. However, if the front panel power switch remains depressed 

when secure mode is removed, power-off occurs. 


Node Security 

Enabling BIOS Security Features 

Once you enable BIOS security measures, access to the system is allowed only after you enter the 

correct password(s). The table below lists the features, describes what protection each offers, and 

tells how to enable or disable each feature. 

In general, to enable or set the features listed in the following table, you must run the SCU and go 

to the Peripheral Configuration Group, Security Subsystem menu. If you have to use a different 

menu or use the BIOS Setup Utility, it is noted in the following table. 

Feature 

Enter secure mode 

immediately with hotkeys 

Inactivity timer: 

keyboard, mouse, blank 

video, diskette writeprotect 

Lock the reset button 

and power switch 

Disable writing to 

diskette 

Specify the boot 

sequence 

Description 

To secure the system immediately, rather than wait for the inactivity 

time-out period, use a hot-key combination that you set through the 

SCU or Setup. 

You can specify a keyboard/mouse inactivity time-out period of 1 to 128 

minutes (in 1-minute increments). If the timer is enabled, and no 

keyboard or mouse action occurs for the specified period, keyboard and 

mouse input are inhibited. 

In addition, if you have enabled these security features through Setup 

or the SCU, the monitor display goes blank, and the diskette drive (if 

enabled) is write-protected. 

To resume activity, enter the password. 

The power switch and reset button are disabled when the system is in 

secure mode. 

If the system is in secure mode, it does not boot from or write to a 

diskette unless you enter a password. To set this feature, use the SCU 

Peripheral Configuration Group, “Security Subsystem Group.” 

To write-protect diskette access whether the system is in secure mode 

or not, select “Floppy Options” from the Setup main menu and specify 

Floppy Access as read only. 

Boot sequence depends on whether system is in secure mode. 

When the system is NOT in secure mode: 

Boots from diskette A, or if no diskette is present, boots from hard disk 

C. 

Boots from hard disk C, or if no bootable OS is present on disk C, 

boots from diskette A. 

Boots from hard disk C only. 

Boots from diskette A only. 

When the system IS in secure mode: 

Boots from hard disk C if present. After booting, system remains in 

secure mode. Even if the power cycles off and on for an unattended 

system, the system still comes up in secure mode. 

Boots from a diskette ONLY if you enter the correct password. Without 

the password, the system does not boot from diskette. Once you enter 

a password, the system is no longer in secure mode. 


Node Security 

Feature 

Control access to using 

the SCU: set 

administrative password 

Control access to the 

system other than SCU: 

set user password 

Put the system into 

secure boot mode 

Boot without keyboard 

Description 

To control access to setting or changing the system configuration, set 

an administrative password and enable it through Setup or the SCU. 

If you enable both the administrative and user passwords, either can be 

used to boot the system. Only the user password can be used to enable 

the keyboard and/or mouse. Only the administrative password allows 

you to change Setup and the SCU. 

To disable a password in Setup, change it to a null string. To disable a 

password in the SCU, enter CTRL-D. 

To control access to using the system, set a user password and enable 

it through Setup or the SCU. 

To disable a password in Setup, change it to a null string. To disable a 

password in the SCU enter CTRL-D. 

To put the system into secure mode, enable secure boot mode and set 

a user password. When secure mode is enabled, the system can boot 

and run the OS, but does not accept mouse or keyboard input until you 

enter the user password. 

In secure boot mode, if the system detects a diskette in the A drive at 

boot time, the system prompts for the password. When you enter the 

password, the system boots from the diskette and is no longer in secure 

mode. If there is no diskette in the A drive, the system boots from the C 

drive and is automatically in the secure mode. All of the secure mode 

features that are enabled go into effect at boot time. 

The BIOS boots whether a keyboard is installed or not. POST 

automatically detects the presence of a keyboard, and tests the 

keyboard if one is present. There is no entry in the SCU to enable or 

disable a keyboard. 




Server management is provided by a combination of software and hardware. Refer to the Server 

Manager publications on the ValuePlus CD for complete information. 

Server Management Software 

The following table shows the server management software supported for different operating 

systems: 

Operating 

System 

Windows NT 

Server 

Software 

Server Availability Manager (SAM) 

LANDesk Server Manager (includes SMM 

software) 

Server Management Board (SMB) software 

NCR Remote Services 

UNIX MP-RAS 

LANDesk Server Manager (ldsm) 

Server Management Board (SMB) software 

(smbci) 

DMI Service Layer (smidmi) 

4300 Baseboard Component Instrumentation 

(smibasebd) 

Server Component Instrumentation (smisci) 

Server Monitor Module (SMM) software 

(servermon) 

NCR Remote Services 

Server Management Hardware 

SMB 

The rack node chassis is equipped with a Server Management Board (SMB). The SMB may have 

an internal modem, or it may be connected to an external modem, as required for remote 

management purposes. The SMB enables the NCR Remote Console software. 

SMM 

A Server Monitor Module (SMM) is an optional board for server management purposes. It enables 

the LANDesk remote control feature. 



Server Management Functions 

Monitoring capabilities of the management software allow it to track and report on a broad range 

of significant hardware and operating system indicators. This allows for assessment of system 

performance and condition. 

With the server management hardware, the server can monitor and collect information about the 

system and environment (for example, temperature, power usage, and voltage). 

Server management software also examines operating system-based statistics, disk utilization 

information, and memory allocation status. This information allows you to diagnose operating 

system-based as well as hardware-based system concerns. 

Server management software includes a DMI Service Layer and DMI-compliant component 

instrumentation. The LANDesk DMI browser can be used to view the server components described 

in MIF files. Various server attributes can be monitored or edited. 

About the SMB 

The SMB is a circuit board used to monitor and control the rack node. 

The SMB, with the associated Intel® LANDesk Server Manager software, enables the monitoring 

and control of the server in-band when the server and network are operating normally, or out-ofband 

over a phone-line. 

The SMB software is a DMI-compliant software component integrated with the LANDesk console, 

thus providing in-band and out-of-band server control and monitoring through the SMB hardware. 

The SMB supports either an internal or an external modem. This provides an interface for remote 

server management and dial-out alerting when the server is not functioning properly. 

The SMB has the following components: 

• Flash circuitry used to reprogram the SMB firmware 

• Interface circuitry to the rack node’s I 2 C control buses and RS232 communications port 

• Either an internal modem or an RS232 connector to be used with an external modem 

The SMB software includes an SMB extension to the LANDesk user interface, the SMB 

driver, and DMI-compliant instrumentation. SMB interfaces through DMI and I 2 C interfaces 

to monitor and control various system attributes. As well as the ability to configure and control 

the SMB itself, the SMB provides the following server management capabilities: 

• Server status of power supply, temperature, voltage, and chassis, including SMB and chassis 

event logs 

• Server configuration of OS version, server name, model number, serial number, chassis 

information 

• Server administration including power off, power cycle, sever reset, reset, and dump 

• In-band notification of server status changes and critical events 

Note: Actions can be configured via LANDesk Alert Management System. 

• Out-of-band notification of critical events at LANDesk Server Manager console or to a pager 



You can use the internal modem you receive with your SMB or your external modem to enable an 

RS232C interface to NCR Remote Console. 

About the SMM 

The Server Monitor Module (SMM) is an optional ISA adapter board that contains its own 

processor, memory, and battery power. You can also install a modem on the SMM to enable it to 

communicate with a remote console or a pager. 

The system can interface to a remote console through an RS232C port (for a Hayes-compatible 

modem), an onboard PCMCIA modem installed in a type II slot, or through Ethernet/Token Ring 

controllers (in-band) if the network is active. 

The SMM provides the following capabilities: 

• Temperature monitoring of both an on-board and remote temperature probe 

• Voltage monitoring of key voltages in the server system 

• Ability to reset or power the server system up and down from a remote location 

• Delivery of alerts to a monitoring system or to a pager 

• Ability to redirect the server console to a remote system 

• Logging of system state changes and BIOS diagnostic information 

You can use the modem you receive with your server to enable an RS232C interface to a remote 

console. 




Chapter 5 

Rack Mount Node Servicing 

Service Philosophy 

The fixed disk drives and all removable media drives (diskette drives, CD-ROM drives, tape 

drives) are configured as field replaceable units (FRUs). 

The service philosophy is to replace and return each FRU as a complete unit. Fixed disk drives and 

power supplies are designed to be easily replaceable while the system is operating. This results in 

an easily serviceable subsystem with very high fault tolerance. 

Routine Maintenance 

The node should be vacuumed every six months. The first scheduled preventive maintenance is at 

the completion of four years of continuous operation. The following preventive maintenance 

actions should be performed at that time: 

• Replace the system cooling and power supply fans 

• Remove and clean all plug-in boards; vacuum and clean all plug-in board connectors 

• Vacuum and clean the backplane and all connectors 

• Vacuum and clean the fixed media SCSI backplane and all connectors 

• Remove, clean, and/or replace all removable media devices 

Serviceable Components 

Following is a list of the customer-serviceable components in the rack node chassis. This chapter 

provides procedures for the installation and removal of these components: 

• Server Management Board (SMB), and the internal or external modem connected to it 

• Redundant 625W power supply 

• Single Connector Attach (SCA) drives in the hot swap bays of the SCSI drive chassis 

All of the customer serviceable components are hot-pluggable. That is, they can be installed and/or 

removed without disconnecting AC power to the node chassis. 

CAUTION: The only components you can hot-swap (replace with the power on) are the SCSI 

drives, power supplies, and the Server Management Board (SMB). Do not attempt to add or 

remove any of the other components unless you unplug the AC power cord from the back of the 

node chassis. 


Servicing Notes 

Servicing Notes 

Warnings and Cautions 

The following warnings and cautions apply throughout this chapter. Only a technically qualified 

person should integrate and configure the system. 

WARNING: System power on/off: The DC push-button on/off switch (a convex button) on 

the front panel of the node DOES NOT turn off the node AC power. To remove power from 

the node, you must unplug the AC power cord at the node. 

WARNING: Hazardous conditions, power distribution backplane: Hazardous energy levels 

are present behind the protective cover over the power distribution backplane. There are no 

user-serviceable parts; servicing should be done by technically qualified personnel. 

CAUTION: Electrostatic discharge (ESD) and ESD protection: ESD can damage disk drives, 

boards, and other system parts. This system can withstand normal levels of environmental ESD 

while you are hot-swapping SCSI hard drives. However, we recommend that you do all procedures 

in this chapter only at an ESD workstation. If one is not available, provide some ESD protection 

by wearing an anti-static wrist strap attached to a chassis ground⎯any unpainted metal 

surface⎯on your system when handling parts. 

Updating the Configuration History File 

When you install or replace a system component, update the configuration history file on the 

Diagnostic Partition. To update the configuration history file: 

1. Boot to the Diagnostic Partition. 

2. Select “Run Utilities and Diagnostics” from the MS-DOS Startup Menu. 

3. Select “System Config Utils.” 

4. Select “View Version Info.” 

5. Select “Edit Config History.” 

5-2 Rack Mount Node Servicing

Installing and Removing the SMB and Connected Modem 

Installing and Removing the SMB and Connected 

Modem 

Servicing Description 

For complete information about the Server Management Board (SMB), see the Server 

Management Product Manual. 

The SMB is installed at the rear on the node chassis, in a slot over the power supplies. The 

following figure shows the location of the SMB in the rack node chassis. 

Figure 5-1. SMB Placement in Rack Node Chassis 

SMB 

The SMB has an optional internal modem. If present, the internal modem must be removed from 

the SMB to enable SMB connection to an external modem. 



The following figure defines connections and components of the SMB: 

Figure 5-2. Server Management Board Components 

Ribbon Cable 

DC Power Cable 

Modem 

Phone Cable 

Comm In 

MLAN 

Line 

LEDs (Service\Status) 

Comm Out 

Item 

Comm In 

MLAN 

Line 

LEDs 

Comm Out 

Phone Cable 

Ribbon Cable 

DC Power Cable 

Modem 

Description 

Connects to Com1 port on node chassis, if using internal or 

external modem line on SMB. DB9 connector. 

Management LAN cable connection 

Phone line connection when using SMB internal modem 

Left: Reserved for future use 

Right: Green = SMB ready 

Connects SMB to an external modem. Disables SMB’s internal 

modem. DB9 connector. 

Connection for internal modem, if used 



Internal modem for remote management (optional item). Must 

be removed to enable SMB connection to external modem 

through COMM out. 



Removing the SMB 

Perform the following steps to remove the SMB: 

CAUTION: Before removing the SMB, ensure that the modem is not in use. 

1. If cables impede access to the SMB board, extend the node far enough to gain clearance. 

2. Remove the cables connected to the SMB. Refer to Figure 5-2 for connections. 

3. Unscrew the jack screw located at the center of the SMB faceplate. Use a manual slotted 

screwdriver; do not use a power tool. 

4. Using the jack screw as a handle, remove the SMB from the slot. 

Installing the SMB 

Perform the following steps to install the SMB: 

1. If cables impede access to the SMB slot, extend the node far enough to gain clearance. 

2. Slide the SMB into the slot on the back of the node chassis, as far as it will go. See Figure 5-1 

for slot location. 

CAUTION: Do not try to force the board all the way into the slot. The board will engage 

fully as you begin tightening the jack screw. 

3. Tighten the jack screw to hold the SMB in place. 

4. Attach the cables to the SMB connectors as appropriate: 

– If using SMB internal modem, connect the Comm In and Line cables. 

– If using an external modem, connect the Comm In and Comm Out cable. 

5. Wait for the right LED (status) on the board to turn green. 

If the light does not turn green within 30 seconds, check that the SMB is properly inserted and 

connected. 

6. Perform an SMB firmware flash to install the firmware on the SMB. See the Server 

Management Product Manual for procedure. 



Removing the Internal Modem 

To remove the internal modem, proceed as follows: 

1. Remove the SMB following the procedures earlier in this chapter. 

2. Disconnect the following cables: 

– Ribbon cable connecting the modem to the SMB 

– Phone cable 

– DC power cable 

3. Using a Phillips screwdriver, remove the two screws holding the modem on the SMB. 

4. Remove the modem. 

Installing the Internal Modem 

To install a new internal modem, proceed as follows: 

CAUTION: Before installing a new modem, contact your manufacturer’s representative to ensure 

the modem has been certified to operate correctly with the SMB. 

1. Slip the back of the modem into the SMB standoff. 

2. Place the modem on the SMB so that the two screw holes are aligned. 

3. Insert and tighten the two screws. 

4. Connect the following cables: 

– Ribbon cable connecting the modem to the SMB 

– Phone cable 

– DC power cable 

5. Install the SMB. 

Using an External Modem 

Perform the following steps to install the external modem: 

CAUTION: If the SMB in the node has an internal modem, you must first remove it to enable 

connection to the external modem. 

1. Connect the external modem, including the phone line, following the instructions in the modem 

user guide. 

2. Connect the modem cable to the Comm Out line on the SMB. 

3. Connect SMB Comm In line to node chassis Com1 port. 

4. Perform an SMB reset before using the modem. 


Installing and Removing Node Power Supplies 



A node chassis contains from one to three self-contained, hot-pluggable power supplies. The 625W 

power supplies are located at the rear of the rack node chassis, as shown in the following figure: 

Figure 5-3. Power Supply Placement in Rack Node Chassis 

Bay 1 

Thumb 

Screw 

Power Distribution 

Backplane 

Bay 2 

Node Power 

Supply Connector 

Bay 3 

You do not need to power off the node before removing or installing a power supply in a node 

chassis, if it is configured for redundancy. If you remove a non-redundant power supply with the 

power on, an overload condition may occur and cause the system to shut down. 



Removing a Node Power Supply 

Perform the following steps to remove a power supply from the node chassis: 

CAUTION: This is a hot-plug procedure. Ensure that the power supply is redundant before 

removing it while the power is on. 

1. Locate the power supplies in the rear of the node chassis. 

2. Unscrew the thumb screw located at the top center of the power supply faceplate. Use a 

manual slotted screwdriver; do not use a power tool. 

Note: Loosening the thumbscrew disengages the power supply from the power distribution 

backplane. 

3. Carefully slide the power supply out of the node chassis. 

Installing a Power Supply 

Use the following steps to install a node power supply: 

1. Slide the new or replacement power supply into the bay in the node chassis as far as it will go. 

Note: Do not try to force it all the way into the bay. The power supply will engage fully as 

you begin tightening the thumbscrew. 

2. Make sure that the power supply is properly aligned with the connector on the power 

distribution backplane. 

3. Tighten the thumbscrew to engage the power supply in the power distribution backplane. Use a 

manual slotted screwdriver; do not use a power tool. 


Installing or Hot-Swapping SCSI Drive 



The SCSI drive hot swap bays are located at the left front of the node chassis. The following figure 

shows the location of the SCSI drive hot swap bays in the node chassis. 

Figure 5-4. SCSI Drive Chassis 

Node Top Cover 

Slide Rail 

Release Clip 

Faceplate 

There are 6 drive bays for 3.5 inch SCSI-2 hard drives. The bays are stacked, 3 on top and 3 on 

the bottom, with a status LED board above each row of 3 bays. 

The status LED board has a set of 3 LEDs for each drive. See SCSI LED definitions in Chapter 2. 



Tools Required 

You need the following tools and supplies to perform the procedures described in this section: 

• Phillips screwdrivers, one with a #2 bit and one with a #1 bit 

• Hexagonal-head nut driver 

• Standard tip screwdriver 

• Anti-static wrist strap and conductive foam pad 

• Equipment log: as you integrate new parts into the system, add information about them to your 

equipment log. 

General Guidelines 

If installing new drives, fill bays from left to right across the top row, then move to the bottom row, 

left to right. 

If replacing a drive, you can hot-swap an existing drive with a replacement drive. This is the only 

SCSI drive chassis servicing procedure that is safe to perform with system power left on. 

Drive/Carrier Assembly 

Each drive requires a plastic carrier, which enables hot-swapping. 

• 7200 RPM disks are enclosed in plastic carriers. 

• 10,000 RPM disks are enclosed in metal carriers. 

The drive is mounted in the carrier, and the carrier is inserted in the drive bay. The carrier has a 

locking handle that secures the drive/carrier assembly in the SCSI bay. 

CAUTION: Do not place plastic and metal carriers (disks with different RPMs) in the same SCSI 

drive chassis. 

Install or Hot-Swap Procedure 

Perform the following steps to install or hot-swap a SCSI drive: 

1. Remove the faceplate of the node chassis. 

2. Locate the SCSI bay door at the left front of the node chassis. Loosen the two thumbscrews on 

the right side and swing open the door. 



3. If swapping a drive, do the following. For a new install, skip to the next step. 

– Locate the drive to be removed. Read the LEDs to identify a faulty drive. 

– Grasp the drive carrier and pull its locking handle toward you to release it from the bay. 

– Lay the unit on a flat surface, carrier side up, and remove the four screws that hold the 

drive in the carrier. See Figure 5-5 for reference. 

– Dispose of the drive appropriately. Save the screws and drive carrier for reuse. 

4. Remove the new drive from its protective wrapper and lay it on an anti-static surface. 

5. Record the drive model and serial numbers in the equipment log. 

6. Orient the drive with the power and signal connector on the top side. See the following figure 

for reference. 

Figure 5-5. SCSI Drive/Carrier Assembly 

A 

B 

E 

C 

D 

A 

B 

C 

D 

E 

Four screws 

Drive carrier 

Hard disk drive 

Drive power and signal connector 

EMI/ESD grounding clip (integral part of carrier) 



7. Place the carrier on top of the drive. Attach the carrier with the four screws. 

The carrier includes EMI/ESD grounding clips that make contact with the drive through two of 

the screws. 

CAUTION: Do not place plastic and metal carriers in the same SCSI drive chassis. 

8. Align the drive/carrier assembly so it engages the guide rails in the bay. 

9. Gently push the assembly into the bay until the drive docks with the backplane connector. 

10. Push the locking handle on the carrier to the right until it locks around the small metal posts. 

11. Close the SCSI bay door and tighten the two thumbscrews. 

12. Replace the faceplate on the node chassis. 


Chapter 6 

Remote Support 

Overview 

Servers have special requirements regarding high availability and fast mean-time-to-repair 

(MTTR). If a server is down, the system’s users are also down and losing productivity. 

Your server comes with a modem and software (NCR Remote) to enable remote serviceability and 

availability of the system. You can set up your system so that a knowledgeable person at a remote 

console can perform server management and support functions. You can also use the modem for 

other purposes when it is not required for remote support. 

For more information about NCR Remote, see the NCR Remote Services User Guide. 

Using the server’s remote support capabilities, skilled personnel can perform the following tasks 

from a remote location: 

• Configure a system 

• Diagnose problems 

• Perform some system repairs 

• Transfer files 

They do not need to be on site to solve most problems. 

This chapter deals mainly with configuring and using the remote support capabilities of your 

server. It discusses server management software only as it pertains to remote support. 

This section provides an overview of the components involved in remote access and management. 

Definitions 

In this chapter, “the server” refers to a server which is being managed from a remote location. 

“Remote location” or “remote terminal” refers to the console or client machine from which remote 

server management is being performed. 

“Console redirection” is the ability to redirect the system console and manipulate it from a remote 

location. 


Overview 

Software 

The following table shows the remote management software supplied with your server. 

Operating Environment 

All 

System Boot/Diagnostic 

Partition 

Windows NT Server 

Software 

The NCR Remote client can interface to the server, whether it is 

in the process of booting, or operating under Windows NT, 

UNIX MP-RAS, or DOS. 

When the remote client is connected to a server running 

Windows NT (with the NCR Remote Server services active), the 

user may execute command-line utilities on the host, do remote 

screen captures, chat, and transfer files. 

When the client is connected to a server which is either in the 

process of booting, operating DOS (Diagnostic Partition mode) 

or running NCR UNIX MP-RAS, the remote client provides ANSI 

terminal emulation for the remote console. While in ANSI 

terminal emulation mode, the remote client will have an 

identical text-mode screen image of what is shown on the 

remote server's console. The NCR Remote Client software can 

be used in place of ANSI terminal emulator software, such as 

PROCOMM PLUS. 

The client transition from an ANSI terminal emulator to a 

Windows NT client is automatic when the server boots 

Windows NT. 

The Diagnostic Partition and Platform CD-ROM contain modem 

utilities. 

The system BIOS provides console redirection support. 

You can execute all system setup, diagnostic and configuration 

utilities on the Diagnostic Partition and Platform CD-ROM from 

a remote console. 

NCR Remote Server is installed on your server when NT is 

installed. It provides extensive remote management capabilities, 

including: 

Command line utilities 

Native Windows NT security 

File transfer 

Logged actions/results 

Remote listing of active windows on server desktop 

Remote screen capture 

Remote chat 

Remote modem configuration 

NT Server Availability Manager also provides server 

management capabilities, in conjunction with Server Monitor 

Module hardware. 

6-2 Remote Support

Overview 

Operating Environment 

UNIX MP-RAS 

Software 

NCR Remote Client controls remote servers both in-band and 

out-of-band for UNIX MP-RAS. The NCR Remote Client 

software can be used in place of ANSI terminal emulator 

software, such as PROCOMM software. 

MP-RAS Server Monitor Software also provides server and 

remote management capabilities, in conjunction with Server 

Monitor Module hardware. 

You can use the MP-RAS commands contty and setmodem to 

configure the server and modem manually for console 

redirection and remote management. 

Remote Access Methods 

You can use the following to access the server from a remote location: 

• Hayes-compatible modem (provided with your server) attached to the COM1 or COM2 

RS232C port, or installed on the NCR Server Management Board 

• PCMCIA modem installed on the Server Monitor Module hardware 

Server Management Board (SMB) 

The Server Management Board (SMB) is an adapter that connects to the server’s I 2 C management 

bus and COM port. It contains its own processor and memory, and operates independently of the 

server hardware. 

For more information about using the SMB, see the Server Management Product Manual. 

Server Monitor Module (SMM) 

The Server Monitor Module (SMM) is an ISA adapter card that has its own processor, memory, 

and battery power. The SMM provides additional diagnostic, monitoring, and management 

capabilities that supplement those available in your server management software. 

For information about using the SMM to perform remote management functions, see “Using the 

Server Monitor Module for Remote Management” at the end of this chapter. 


Preparing the Server for Remote Management 

Preparing the Server for Remote Management 

Remote management functions and console redirection support are available through the following: 

• Base BIOS and operating system services used with the remote support modem provided with 

your server 

• The Server Monitor Module (SMM) and its associated software 

For information on using the SMM, refer to “Using the Server Monitor Module for Remote 

Management” at the end of this chapter. 

To use the base BIOS and operating system services for remote management, you must perform 

the following actions: 

• Enable console redirection. See “Console Redirection” later in this chapter for more 

information. 

• Enable remote access through the provided Hayes-compatible modem. See “Configuring a 

Remote Support Modem” later in this chapter for information about configuring the modem. 

• Verify that the system is correctly set up for remote management by performing the test 

described in “Verifying That Remote Support Is Functioning Properly” later in this chapter. 

Note: If you want to run hardware diagnostic and configuration utilities from a remote 

location with no user intervention, make sure that the server’s boot disk contains the 

Diagnostic Partition. See Chapter 5, “Hardware-Related Utilities and Applications,” for a 

discussion of the Diagnostic Partition. 

• If you wish to have remote console features while the server is running Windows NT, install 

the NCR Remote software. For more information on how to install NCR Remote, see NCR 

Remote Services User Guide. 

6-4 Remote Support

Console Redirection 


Console redirection is a BIOS and operating system feature that enables a person at a remote 

location to control your server’s console operations. 

Enabling Console Redirection 

You can enable console redirection at the BIOS level with either the System Configuration Utility 

(SCU) or the BIOS Setup Utility. Normally you use the SCU to perform this function. 

You can also enable console redirection through your operating environment. Refer to your 

operating environment documentation or to the operating system-specific sections at the end of this 

chapter for more information. 

Enabling console redirection increases the Diagnostic Partition boot timeout from 10 seconds to 2 

minutes. This permits more time to dial into a system as it is rebooting. 

Note: Before changing console redirection parameters via BIOS Setup or the SCU, make sure that 

there is no active modem connection. 

Enabling Console Redirection with the SCU 

The following table defines the SCU options that must be set to enable console redirection. These 

options are found in various functional groups of System Board device definition. (Use the SCU’s 

Step 3: Change Configuration Settings menu option to configure System Board options.) 

Group Options Comments 

On-Board 

Communicat 

ion Devices 

Console 

Redirection 

Serial Port 1 Configuration 

or 

Serial Port 2 Configuration 

Select COM Port for 

Redirection 

Serial Port Baud Rate 

Hardware Flow Control 

Select Terminal Type 

Both COM1 and COM2 are available for general purpose 

use. 

If remote management and console redirection support 

are required, you must enable COM1 or COM2 for these 

functions. 

UNIX MP-RAS only uses COM1 for console redirection. 

Enable the COM port you want to use for console 

redirection. Your choices are: Disable, Redirection on 

COM1 @ E4000, or Redirection on COM2 @ E4000. 

Enter the baud rate for the remote support modem. Your 

choices are: 9600 Baud, 19.2 K Baud, 38.4 K Baud, or 

115.2 K Baud. 

115.2 K baud rate is not recommended. The Diagnostic 

Partition does not support file downloads (via the rf 

utility) at 115.2 K baud. 

UNIX MP-RAS does not support the 115.2 K baud rate 

for remote console, either via modem or direct connect 

terminal. 

Enter the type of flow control to be used. Always set this 

option to “CTS/RTS & Carrier Detect” flow control. 

“ANSI” is the only available option. 



After you save the configuration and exit from the SCU, you must reboot the system for changes to 

take effect. 

Note: When you change the console redirection baud rate, you must synchronize your modem’s 

baud rate to the new speed. To do this, select Auto Answer On/Off (Enable Auto Answer or 

Disable Auto Answer) or Re-init Modem from the Modem Utilities menu of the Diagnostic 

Partition or Platform CD-ROM. 

Enabling Console Redirection with BIOS Setup 

The following table defines the BIOS Setup Utility options that must be configured to enable 

console redirection. 

Menu Options Comments 

Peripheral 

Configuration 

Serial Port 1 Address 

or 

Serial Port 2 Address 


Serial Port Baud Rate 

Redirection Flow Control 

Both COM1 and COM2 are available for general 

purpose use. 

If remote management and console redirection 

support are required, you must enable either 

COM1 or COM2 for these purposes. 

UNIX MP-RAS only uses COM1 for console 

redirection. 

Select Port 1 to redirect the console to COM1 or 

Port 2 to redirect the console to COM2. 

Enter the baud rate for the remote support 

modem. Your choices are: 9600, 19.2 K, 38.4 K, 

or 115.2 K. 

115.2K baud rate is not recommended. The 

Diagnostic Partition does not support file 

downloads (via the rf utility) at 115.2K baud. 

UNIX MP-RAS does not support 

115.2 K baud rate for remote console, either via 

modem or direct connect terminal. 

Enter the type of flow control to be used. Always 

set this option to “CTS/RTS & CD” flow control. 

Note: When you change the console redirection baud rate, you must synchronize your modem’s 

baud rate to the new speed. To do this, select Auto Answer On/Off (Enable Auto Answer or 

Disable Auto Answer) or Re-init Modem from the Modem Utilities menu of the Diagnostic 


How Redirection Works 

During console redirection, the remote terminal (the NCR Remote client or any system with an 

ANSI terminal emulator, such as PROCOMM PLUS) sends keystrokes to the local server, which 

then passes back video information. 

Information from the local server’s video buffer is sent to the remote terminal for display. 

Keyboard information from the remote terminal is forwarded to the local server’s application using 

the INT 16h BIOS Keyboard Services interrupt. 

6-6 Remote Support


Keyboard Input 

Keyboard strings are based on the ANSI BBS terminal standard. Since these terminals do not 

support all of the keys on the standard 101-key U.S. keyboard, some combinations of keyboard 

characters are defined to represent keys such as the following: 

• F5 through F12 

• ALT-a through ALT-z 

• ALT-0 through ALT-9 

• Page Up and Page Down 

The server application must interpret these non-standard character combinations correctly. 

Keyboard strings are fully defined in the “Key Mapping for Non-ASCII Keys” section later in this 

chapter. 

Video Display 

A screen is not painted/repainted at the remote terminal until the local video console is updated. 

Therefore, when you first connect a remote terminal to the local server, nothing may display at the 

remote site. This is because no video changes have occurred since the last screen was output to the 

COM port. 

If you connect to the local server and no video information displays at the remote terminal, press 

the ENTER key to generate a change to the local screen. This should trigger the output of the video 

buffer to the local terminal. 

Note: DOS-based applications should be tested to verify BIOS redirection support since this 

support relies on BIOS video and keyboard services in order to operate. 

Console Redirection Limitations 

Following are some console redirection limitations: 

• BIOS console redirection does not transmit bitmap graphics (such as the server logo screen 

that displays before the SCU is invoked); only character-based data are transmitted. Therefore, 

a blank screen (or gray screen in PROCOMM) may display on the remote terminal. Press 

ENTER to continue. 

• When the server reboots, there is no output from the COM port until the POST sequence 

initializes this port. This process may take some time if a large amount of memory must be 

tested. The remote terminal screen continues to display the last contents of the video buffer 

before the system reboot until BIOS POST initializes the COM port. 

• To reboot the server remotely, you must either enter the init command from UNIX or select the 

reboot option provided on the Diagnostic Partition and Platform CD-ROM menus, and in the 

SCU, BIOS Flash, and Diagnostics Utilities. (If you enter CTRL-ALT-DEL at a remote terminal, 

only the remote terminal is rebooted.) 

• To shutdown a remote system running Windows NT, use the rcshutdown command-line utility 

(you must have NCR Remote Server installed on NT). 



• You cannot execute the DOS edit.exe program remotely because the program uses ALT – 

keystrokes in its menu code. Use other DOS utilities, such as the type command, to view text 

files. 

• Timing problems in the remote interface can occur since the ESC key is both a valid keystroke 

(for example, to exit a program) and the initial character in a string that represents a keystroke 

(for example, ESC-OP represents F1). 

Using the F1 example above, if the system takes too long to receive the “OP” string following 

the ESC keystroke, redirection interprets this string as several distinct characters. The ESC 

keystroke is forwarded to the server application, followed by the “O” and “P” strings. 

• For keyboard redirection to work, the application on the server must use the INT 16h BIOS 

services to receive keystrokes. If the application uses INT 9h or INT 15h services, console 

redirection does not work. 

• Unusual key combinations (such as CTRL-F1) for non-ASCII keys are not supported. 

• WordPerfect does not work due to its extensive use of SHIFT-F1 and CTRL-F1 key 

combinations. 

6-8 Remote Support

Configuring a Remote Support Modem 


Your system comes with a modem. You can use this modem for general purpose communications 

and for remote management. You can also use a Hayes-compatible modem similar to the one 

provided with your server to enable remote support. 

We recommend that you reserve the modem for remote support so that the system is appropriately 

configured if a problem occurs. 

Using NCR Remote 

If you are using the NCR Remote software in Windows NT, see the NCR Remote Services User 

Guide for information on configuring a remote support modem. 

Using the Diagnostic Partition Menus 

This section discusses how to use the Diagnostic Partition menus to configure a remote support 

modem. You can also perform many of these configuration tasks through your operating system. 

Refer to your operating system documentation or the operating system-specific sections at the end 

of this chapter for more information. 

Terms and Definitions 

You should be familiar with the following terms before configuring your remote support modem. 

auto-answer mode 

Mode in which your modem is configured to answer incoming calls automatically and permit 

remote connections. 

call-back password 

Modem password associated with a call-back phone number. When you enter a call-back 

password at the modem password prompt, the modem disconnects the phone line and dials the 

specified call-back number. 

call-through password 

Modem password with no call-back phone number. When a call-through password is entered at 

the modem password prompt, the remote user is directly connected to the local server’s COM 

port. 

Modem and System Security 

The security of the server system is of primary concern when enabling remote management. Any 

mechanism that permits a remote support person to enter a system can permit an unauthorized user 

to enter as well. 



The following security measures are recommended for enabling remote management: 

• By default, console redirection should be disabled in BIOS Setup and the System 

Configuration Utility (SCU), as well as in the operating environment. The modem should not 

be initialized for auto-answer mode. 

• The safest mechanism for allowing remote access by expert personnel is to define call-back 

passwords to assure the integrity of the remote user. However, this is not possible in all cases, 

especially if modem pools are used by support personnel. 

• If call-back passwords are not possible in your support environment, remote access should 

typically be disabled. 

Access can be permitted in server down situations by locally enabling redirection and locally 

setting a modem for auto-answer. 

A person sitting at the machine needing service enables redirection in the BIOS and/or 

operating environment and initializes the modem for auto-answer. Someone should watch what 

is happening on the local console to verify the integrity of the caller (to prevent unauthorized 

access at just the wrong moment). 

• When setting up a modem for auto-answer, always enable modem passwords and define callback 

or call-through passwords. You can configure your modem with the Diagnostic Partition 

or Platform CD-ROM utilities, with the NCR Remote software, or with direct modem (AT) 

commands from your operating environment. The sections that follow discuss modem 

configuration in more detail. 

• It may be impossible to enable the server for redirection locally due to the location of the 

hardware or the lack of computer knowledge by local personnel. 

In this case, call-back passwords are required for security reasons. Console redirection should 

be ENABLED by default and the modem set for auto-answer with one or more call-back 

numbers defined. 

A user can then dial into the modem, enter the password, receive the call-backs and perform 

necessary remote debug, configuration and update tasks. In addition, if more expert support is 

required, you can define a call-through or call-back password remotely. 

You can use the following methods to define a call-through or call-back password: 

• The Set Remote Password Diagnostic Partition or Platform CD-ROM menu option 

• The NCR Remote software in Windows NT 

• An operating system application that transmits manually entered modem (AT) commands to 

COM1 or COM2 

See the “Using a Remote Password” section later in this chapter. 

Note: Enable call-through passwords only for the minimum time necessary to debug and correct a 

system problem. 

6-10 Remote Support


Other Modem Security Issues 

The modem shipped with your server provides many different features. The Remote Support 

utilities do not use some of these features. 

Predefined Telephone Numbers 

The modem has the capability to store pre-defined phone numbers. This feature represents a 

security risk for your system. Pre-defined numbers are stored in the same data space as call-back 

and call-through passwords. Therefore, a predefined telephone number is also interpreted as a valid 

password. 

It is recommended that you not store telephone numbers in the modem. 

Password Checking 

Another modem feature is the ability to disable modem password checking. The Diagnostic 

Partition and Platform CD-ROM modem utilities support this feature. You can access it from the 

Administer Passwords menu of the Set Password/Country utility. 

From the Administer Passwords options list, you can select Disable Password Checking to 

disable redundant checking. You should not use this command in normal operations. 

If you execute the Disable Password Checking command after enabling the modem for autoanswer, 

a caller has free access to your system console. Although passwords are provided in the 

operating system environments, this is not true at the BIOS or Diagnostic Partition and Platform 

CD-ROM levels. 

It is recommended that you never disable password checking in the modem. 

Configuring a Modem 

You can access the Modem Utilities menu from either the Diagnostic Partition or the Platform CD- 

ROM. The Modem Utilities menu contains functions that enable you to 

• Configure your modem type, passwords and command strings 

• Set or delete a call-through or call-back password remotely 

• Enable or disable the modem for auto-answer 

• Hang up an existing connection 

• Send commands to the modem interactively 

Operating system-specific utilities and commands also exist to configure your modem. For 

information about these utilities and commands, see your operating environment documentation or 

the operating system-specific sections later in this chapter. 

This section discusses the steps necessary to configure a modem for remote management from the 

Diagnostic Partition or Platform CD-ROM menus. These menus also provide other modem 

utilities. See the Server Software Guide (4SMP) for a general discussion of the Diagnostic 

Partition and Platform CD-ROM modem utilities. 



Accessing the Modem Utilities Menu 

This section explains how to access the Modem Utilities menu from the Diagnostic Partition and 

the Platform CD-ROM. 

Accessing From the Diagnostic Partition 

Perform the following steps to access the Modem Utilities menu from the Diagnostic Partition: 

1. Boot to the Diagnostic Partition. 

2. Select Run Utilities and Diagnostics from the MS-DOS Startup menu. 

3. Select Remote Support from the main menu. 

4. Select Modem Utilities from the Remote Support menu. 

The system displays the Modem Utilities menu. 

Accessing from the Platform CD-ROM 

Perform the following steps to access the Modem Utilities menu from the Platform CD-ROM: 

1. Boot from the Platform CD-ROM. 

2. Select Run CD Utilities and Diagnostics from the MS-DOS Startup menu. 

3. Select Remote Support from the CD main menu. 

Note: If the Diagnostic Partition is not installed, you must first select “Execute Utils from 

CD.” 

4. Select Modem Utilities from the Remote Support menu. 

The system displays the Modem Utilities menu. 

Enabling the Remote Support Modem 

Perform the following steps to enable the remote support modem: 

1. Access the Modem Utilities menu as detailed in the previous section. 

2. Select Configure Modem from the Modem Utilities menu. 

3. Select Edit Modem Profile from the Modem Configuration menu. 

4. The first time that you run modem utilities, verify the modem vendor . 

Choose the 1. Select Modem Vendor menu option for “Lasat.” Currently, the only modem 

vendor is “Lasat.” (The modem on the SMB is a Lasat modem.) 

If you have any other type of modem, choose 2. Other from the modem vendor option menu. 

Verify all modem (AT) command strings using the Edit Modem Profile menu option 2. 

Define Modem Strings. 

If your “Other” modem provides password and/or country support, use the Interactive Modem 

program on the Modem Utilities menu to enable, disable, and set these features. 

6-12 Remote Support


Note: If you have any questions or if your modem does not operate correctly after you define 

your modem strings, contact the appropriate support center. 

5. Exit from Edit Modem Profile utility by selecting option 3. Exit from the utility’s main 

menu. 

6. Select Set Password/Country from the Modem Configuration menu. 

Note: You must enable console redirection before you can run the Set Password/Country 

utility. This utility uses the COM port and baud rate specified for redirection to program the 

modem. 

Verify the country information by choosing the 2. Configure Country Code menu option. 

From the Configure Country Code menu, press 1 and ENTER to view and verify country code 

information. 

If the country information is not correct, select menu option 2. Change Country Code from 

the Configure Country Code menu. This menu option allows you to configure the modem to 

operate in another country. 

If your country does not display for selection, contact the appropriate support center defined in 

the Server Support Log. 

7. Select 3. Exit to return to the Set Password/Country utility main menu. 

8. Using the Set Password/Country utility, define one or more modem passwords to protect your 

server from unauthorized use. Define call-back or call-through passwords using the 1. 

Administer Passwords option from the Set Password/Country main menu. 

9. From the Administer Passwords menu, you can view all currently defined passwords, define 

and delete individual call-back or call-through passwords, and enable and disable all password 

checking at the modem. 

For remote support, you must define at least one password and enable password checking. 

Press 2 and ENTER to define a password. Provide password and optional call-back number 

information when prompted by the utility. After providing the information, press 4 and ENTER 

to “Enable Password Checking.” 

Note: Password 0 contains the remote password. This is a call-through or call-back password 

that can be manipulated remotely. Password 0 is automatically modified when you enable or 

disable the remote password using the Set Remote Password and Delete Remote 

Password programs on the Modem Utilities menu. The next section discusses the remote 

password in detail. 

Never enable passwords without defining at least one call-back or call-through password. If 

you enable passwords but do not define a password, remote modem access is impossible. 

10. Exit from the Set Password/Country utility by pressing 6 and ENTER to exit from the 

Administer Passwords menu, and then pressing 3 and ENTER to exit from the modem utility’s 

main menu. 

11. Press the left arrow or ESC once to return to the Modem Utilities menu. 

12. Select Auto Answer On/Off from the Modem Utilities menu. Then select Enable Auto 

Answer from the Auto Answer menu. 



Note: For the modem shipped with your server, Enable Auto Answer automatically enables 

password checking for security. In order to connect to the server from a remote location, define 

at least one call-back or call-through password. 

13. Press the keyboard’s left arrow or ESC three times to return to the main menu of the Diagnostic 


Using a Remote Password 

When you run the modem utilities from the Diagnostic Partition or Platform CD-ROM, they 

initialize the COM port and modem. The utilities transmit modem command strings through the 

COM port. 

Using the COM port and transmitting commands to the modem disrupts console redirection 

functions provided by the system BIOS. A person who is accessing the server remotely relies on 

console redirection to view the server screen and input keyboard data. If redirection is disrupted by 

the modem utilities, there is no remote indication of what is happening on the server screen or what 

to enter at the keyboard. For these reasons, you cannot run most of the modem utilities remotely. 

For security reasons, two modem applications on the Diagnostic Partition and Platform CD-ROM 

are written especially for remote use. These applications set or delete a Remote Password. 

It is important to be able to set and delete the Remote Password from a remote location. This 

allows remote management of a server in a “lights out” environment, if the server console and 

keyboard hardware are not easily accessible, or if local personnel are not sufficiently trained. 

In these situations, call-back passwords are required to be defined for the server’s modem, for 

security reasons. Console redirection should be enabled by default and the modem set for autoanswer 

with one or more call-back passwords defined. 

A user can then dial into the modem, enter the password, receive the call-back and perform 

necessary remote debug, configuration and update tasks. In addition, if more expert support is 

required, the capability exists to define a call-through or call-back password remotely. 

This call-through or call-back password is the remote password. It is automatically stored in the 

modem as Password 0. When you select Delete Remote Password, Password 0 is automatically 

cleared. 

The Set and Delete Remote Password utilities are designed to initialize and command the modem 

only when all necessary information has been obtained from a remote user. After this, the COM 

port and modem are initialized, the current connection is hung up, the modem is commanded, and 

the system is reset to restore console redirection capabilities. No other passwords (but Password 0) 

are affected. No other modem strings (except the update password command string, at*p) are 

transmitted. 

Note: As mentioned in the “Modem and System Security” section, you should enable a callthrough 

password only for the minimum time required for support purposes. When you enable the 

call-through password, inform a support person immediately and allow them access to the server 

through the modem. 

6-14 Remote Support


Configuring Other Modems 

There are certain modem configuration settings required for remote management. Review this 

section if you selected “Other” as your modem vendor while running the Edit Modem Profile 

utility. 

If you do not have a Lasat Safire modem, you must verify (and maybe also modify) the modem 

(AT) command strings that are used by the modem utilities on the Diagnostic Partition and 

Platform CD-ROM. The exact settings of the strings depend on the command set supported by 

your modem. The following information provides guidelines regarding how to configure your 

modem. 

You can use the Edit Modem Profile utility to edit the modem (AT) commands used by the 

Diagnostic Partition and Platform CD-ROM modem utilities. Refer to the “Enabling the Remote 

Support Modem” section and the Server Software Guide (4SMP) for additional information about 

using the Edit Modem Profile utility. 

You can edit any modem (AT) command strings used by the modem utilities on the Diagnostic 

Partition or Platform CD-ROM. However, because the CD-ROM is a read-only device, these 

changes are made to a RAMDisk file. The changes are in effect from the time you enter them until 

the next reboot of the system. At system reboot, the RAMDisk and its contents are lost. 

Note: Default settings for the “AT” command strings used by the Modem Configuration Utilities 

are described in detail in the Server Software Guide (4SMP). 

General Modem Configuration Requirements 

Configure the remote access modem to perform as follows: 

• Operate at the same line speeds as console redirection. Some modems remember the last line 

speed used. These modems might not operate correctly if they are initialized at one speed (for 

example, 9600 baud) and redirection is set for a different speed (for example, 19.2 K baud). 

• Force the Carrier Detect line to follow Off-Hook/ On-Hook. 

• Not return result codes or only provide result codes in originate mode. 

• Operate with command echo off. 

• Maintain settings across sessions. 

• Ignore the DTR signal line. The modem must ignore DTR since this line toggles low when the 

server is rebooted. Ignoring the DTR line allows the modem to maintain a session through 

system reboot. 

For example, assume that a remote reboot invokes a new hardware configuration. In this case, 

the modem must maintain the remote session so that support personnel can verify that the 

system boots correctly and problems have been resolved. 



Initialization Settings 

The following table shows sample AT commands that should be included in the remote support 

modem’s Enable Auto Answer initialization string. 

These commands are for a Hayes-compatible modem; they may vary for other modems. 

Characteristic 

DTR ignored 

DSR forced on 

LSD (line signal detect, corresponding to 

CD - Carrier Detect) follows standard RS- 

232 operation - ON when on-Hook 

No result codes or result codes only in 

originate mode 

Command character echo disabled 

Asynchronous operation with AT 

command set dialing 

Set for auto-answer 

AT Command 

(&D0) 

(&S0) 

(&C1) 

Note: This setting is required so that BIOS and UNIX 

MP-RAS can detect when someone is connected to the 

modem by sensing the Carrier Detect state. When 

Carrier Detect is low, console redirection information is 

not transmitted through the COM port. 

(Q1) or (Q2) 

(E0) 

(&M0) 

(S0=1) 

6-16 Remote Support

Preparing the Remote Location 


This section describes how to prepare a system to act as a remote terminal when remote 

management of your server is required. 

Using NCR Remote 

The NCR Remote client will act as an ANSI terminal emulator when connected to a server booted 

under DOS (Diagnostic Partition), in the process of booting, or when running UNIX MP-RAS 

from the command line. The key-mappings are predefined to work with the WorldMark 4300. See 

the NCR Remote Services User Guide for additional configuration information. 

Using Other Terminal Emulation Software 

You may alternately use other terminal emulation software, such as PROCOMM PLUS. However, 

if you have NCR Remote installed, you do not need other terminal emulation software. 

If you want to use PROCOMM PLUS, use the guidelines in this section to configure PROCOMM 

PLUS, Version 3.0. PROCOMM PLUS is the only other communications program tested to date 

(other than NCR Remote) that fully supports the ANSI BBS standard and ANSI color. In addition, 

you can configure extended keyboard mapping information with PROCOMM PLUS. 

General Requirements 

You need the following to support a system from a remote location with PROCOMM PLUS, 

Version 3.0: 

• Analog phone line (digital phone lines do not work with the modem) 

• High speed modem (a 28.8 Kbps modem is recommended if you are running console 

redirection at 38.4 K baud speeds. However, you can also use a 14.4 Kbps modem if you 

reduce the redirection speeds accordingly.) 

• Windows operating environment (Windows 3.1, Windows NT, or Windows 95) 

PROCOMM PLUS Settings 

Information in this section is based on the following assumptions: 

• You performed an Express Install of PROCOMM PLUS, Version 3.0. 

• PROCOMM is defined to operate on COM1 or COM2 with your remote support modem 

• You selected a default window setup 

To connect to the server, run the PROCOMM PLUS Terminal application. You can select this 

application from the PROCOMM PLUS Program Manager Group. 



Configuring PROCOMM PLUS Terminal Software 

Perform the following steps to configure your PROCOMM PLUS Terminal software: 

1. Press ALT-F8 to start the PROCOMM PLUS Keyboard Editor utility. Use the keyboard 

mapping information provided in the sections “Keyboard Input” and “Key Mapping for Non- 

ASCII Keys” to define valid keystroke combinations required by the console redirection 

software. Save the keyboard information to a keyboard file, 4300.kbd. 

2. Using the PROCOMM PLUS Connection Directory, define a new Data entry that represents 

the server to be managed remotely. As part of this definition, provide the following 

information: 

– Phone number of the analog line that connects to the server 

– The type of connection: internal, local, long distance or international 

– Selection of COM1 or COM2 and your remote support modem for the “Data Connection.” 

This may be the “Current Connection” PROCOMM default. 

– Terminal type = ANSI BBS 

– Parity = None 

– Data bits = 8 

– Stop bits = 1 

– Protocol = Zmodem 

3. After defining the data entry, select OK to continue and then select File/Save from the 

Connection Directory action bar. You can now return to the Terminal window to continue 

defining the terminal parameters. 

4. Select the Setup/Data/Terminal Options menu items from the Terminal action bar. Define the 

following parameters on the Terminal Options window: 

– Terminal Size = 25 Rows and 80 Columns 

– Terminal Keyboard File = 4300.kbd (You can edit this file from the Terminal Options 

menu by pressing the “Edit Keyboard File” button.) 

– Toggle support OFF for “Line Wrap” and “Destructive Backspace” 

– Select the “Advanced” button and toggle “Treat Music sequence as Delete Line” ON 

5. From the button list at the left of the current window, select Data Connection. Verify that the 

“Use hardware flow control” toggle is ON. 

6. From the button list at the left, select Terminal Fonts. Verify that the “PCPlus 437” font is 

selected. 

7. From the button list at the left, select Terminal Colors. Set the background color to black. 

8. Press the OK button at the bottom left corner to save the terminal parameter settings. 

9. To dial the modem, open the Connection Directory and the Data window. Highlight the entry 

that represents the 4300 server to be remotely managed. Click the Dial button at the bottom 

right of the window. 

Additional PROCOMM settings may be required to transfer files. Several options are possible. See 

the “Transferring Files to and from a Remote Location” section later in this chapter for details. 

6-18 Remote Support


Keyboard Input 

The local server maps keyboard input from the remote console as follows: 

If the key... 

Has an ASCII mapping 

(such as A or CTRL-A) 

Does not have an ASCII mapping 

(such as F5 or Page Down) 

Then... 

The ASCII character typed at the remote console is 

transmitted directly to the local server and placed in the local 

server’s keyboard buffer. 

The character typed at the remote console is translated by the 

PROCOMM software to the keystroke combination defined in 

the keyboard file. This combination is then transmitted to the 

local server. The local system translates the keystroke 

combinations back to the appropriate keyboard character and 

places the character in the local keyboard buffer. 

The tables in the following sections define key mappings expected by BIOS and UNIX MP-RAS 

console redirection software. You can define these mappings in PROCOMM PLUS by performing 

the following actions: 

• Pressing ALT-F8 in the Terminal window to start the PROCOMM Keyboard Editor utility 

• Selecting a key to be defined from the displayed keyboard by tabbing to the key or pressing the 

left mouse button when the cursor is positioned over the key 

• Pressing the spacebar to edit the key’s mapping 

• Defining the “Normal” key combinations as documented in the sections that follow 

If you do not want to define all of the keyboard mapping settings individually, you can obtain a 

PROCOMM keyboard file, REMCON.KBD, from the World Wide Web site. To get the keyboard 

file from the WWW site: 

• Use a Web Browser to connect to the www.ncr.com Web site. 

• The URL to obtain the REMCON.KBD file is 

http://www.ncr.com/support/pc/pcdesc/library/4300.shtml. 

• Select the “REMCON.EXE” hot spot. 

Key Mapping for Non-ASCII Keys 

The following table defines mappings for non-ASCII keys. NS means not supported, (xxh) = 

ASCII character xx. 

Key Normal SHIFT CTRL ALT 

ESC ^[ NS NS NS 

F1 ^[OP NS NS NS 

F2 ^[OQ NS NS NS 

F3 ^[OR NS NS NS 

F4 ^[OS NS NS NS 

F5 ^[OT NS NS NS 

F6 ^[OU NS NS NS 

F7 ^[OV NS NS NS 



Key Normal SHIFT CTRL ALT 

F8 ^[OW NS NS NS 

F9 ^[OX NS NS NS 

F10 ^[OY NS NS NS 

F11 ^[OZ NS NS NS 

F12 ^[O1 NS NS NS 

Print Screen NS NS NS NS 

Scroll Lock NS NS NS NS 

Pause NS NS NS NS 

Insert ^[[L NS NS NS 

Delete (7Fh) NS NS NS 

Home ^[[H NS NS NS 

End ^[[K NS NS NS 

Page Up ^[[M NS NS NS 

Page Down ^[[2J NS NS NS 

Up Arrow ^[[A NS NS NS 

Down Arrow ^[[B NS NS NS 

Right Arrow ^[[C NS NS NS 

Left Arrow ^[[D NS NS NS 

Tab ^I (=09h) NS NS NS 

6-20 Remote Support

Verifying That Remote Support Is Functioning Properly 

Verifying That Remote Support Is Functioning 

Properly 

This section tells you how to verify that remote support is functioning properly. 

Setting Up the Server 

Perform the following steps at the server: 

1. Boot to the Diagnostic Partition or Platform CD-ROM. 

2. Select Run Utilities and Diagnostics from the MS-DOS Startup menu if you booted to 

the Diagnostic Partition. Select Run CD Utilities and Diagnostics if you booted to the 

Platform CD-ROM. 

3. Select System Config Utils from the main menu. 

Note: If the Diagnostic Partition is not installed, and you are executing from the Platform CD- 

ROM, you must first select “Execute Utils” from CD. 

4. Select Execute SCU from the System Config Utils menu. 

5. Select Step 3: Change Configuration Settings from the System Configuration Utility 

main menu. 

6. Select System Board from the Change Configuration Settings menu. 

7. Scroll down to Console Redirection and change or verify the settings as described in the 

“Console Redirection” section in this chapter. 

8. Press ESC twice to return to the SCU main menu. 

9. Select Step 4: Save Configuration from the System Configuration Utility menu. 

10. Select Step 6: Exit. 

Note: Although the System Configuration Utility instructs you to reboot, do not do so at this 

time. 

11. Define a call-back or call-through password for the modem, as described in the “Enabling the 

Remote Support Modem” section earlier in this chapter. (If you are defining a call-through 

password, define it as Password 0.) 

12. From the Modem Utilities menu, select Auto Answer On/Off. From the Auto Answer menu, 

select Enable Auto Answer. 

13. Press the keyboard’s left arrow or ESC three times to return to the main menu of the Diagnostic 

Partition or Platform CD-ROM. Select Reboot System from this menu. 

14. Press D (when prompted) to enter the Diagnostic Partition, or boot from the Platform CD- 

ROM. 

15. Select Run Utilities and Diagnostics from the MS-DOS Startup menu if you booted to 

the Diagnostic Partition. Select Run CD Utilities and Diagnostics if you booted from 

the Platform CD-ROM. The main menu of the Diagnostic Partition or Platform CD-ROM 

should display. 


Verifying That Remote Support Is Functioning Properly 

At this point, a remote location must be configured to access your server and verify the operation 

of the remote management components. You can do this yourself, or contact the appropriate 

support center, a list of which is available in the Server Support Log. 

Verifying Remote Management Operation 

To verify the operation of the remote management components, perform the following steps: 

1. Configure and dial from a remote terminal with the NCR Remote client or with PROCOMM 

PLUS. See the NCR Remote Services User Guide or the “Preparing the Remote Location” 

section earlier in this chapter. 

2. Enter your call-back or call-through password when prompted by the modem. 

– If you use a call-through password and enter it successfully, you should see the Diagnostic 

Partition or Platform CD-ROM main menu on your remote terminal. 

– If you use a call-back number, your current call is disconnected and the modem dials the 

call-back number. The server transmits the Diagnostic Partition or Platform CD-ROM 

main menu to the remote terminal after the call-back connects successfully. 

3. From the remote terminal, select the following in sequence from the Diagnostic Partition or 

Platform CD-ROM menus: 

– System Config Utils 

– View Version Information 

– View S/W Version 

Verify that the version information displays exactly as it displays when View S/W Version is 

selected from the local console. 

4. Press ESC twice to exit the View Version Information utility and return to the Diagnostic 

Partition or Platform CD-ROM main menu. 

5. If you accessed the server with a call-through password, select the following in sequence from 

the menus: 

– Remote Support 

– Modem Utilities 

– Delete Remote Passwd 

As part of the “Delete Remote Passwd” processing, the system disconnects your call and 

disables the call-through password. 

6. If you accessed the server with a call-back password, disconnect the call. If you are using 

PROCOMM, use the Hang Up button in the upper right corner of PROCOMM’s Terminal 

window. If you are using NCR Remote, use the Disconnect option in the Connect menu 

(accessed from the program’s action bar). 

7. Remove all non-production or test-related call-back or call-through passwords from the local 

console. To do this, follow the instructions in the next section. 

6-22 Remote Support

Disabling Remote Support Passwords and Modem Access 

Disabling Remote Support Passwords and Modem 

Access 

Remote management capabilities are disabled differently in different situations. This section 

discusses these situations in detail. 

Disabling Modem Passwords When Operating Remotely 

If you are using a call-through password to operate remotely and have completed debug and repair 

of a system, it is necessary to delete the password. 

From the Diagnostic Partition or Platform CD-ROM environments, select Delete Remote 

Password from the Modem Utilities menu. It is important to perform this function because the 

remote password is a call-through password that permits anyone who types it correctly to access 

your server’s console. 

If you are using a call-back number to operate remotely and have completed debug and repair, you 

do not need to do anything to disable remote support. You should hang up the current connection. 

If you are using PROCOMM, use the Hang Up button in the upper right corner of PROCOMM’s 

Terminal window. If you are using NCR Remote, use the Disconnect option in the Connect menu 

(accessed from the program’s action bar). 

You cannot delete passwords 1 through 3 remotely -- you can delete only password 0 remotely. 

This requires the ability to execute the modem utilities remotely on the Diagnostic Partition or 

Platform CD-ROM. As discussed in the section, “Using a Remote Password,” execution of most of 

the modem utilities is not possible from a remote location. 

Disabling Modem Passwords and Access from the Local Server 

To disable remote support when operating from the local server, first select Hang Up from the 

Modem Utilities menu on the Diagnostic Partition or Platform CD-ROM. 

If you defined a call-through password (or a call-back password that is no longer needed), perform 

the following steps to delete this password: 

1. Select Configure Modem from the Modem Utilities menu on the Diagnostic Partition or 

Platform CD-ROM. 

2. Select Set Password/Country from the Modem Configuration menu. 

3. From the Set Password/Country main menu, press 1 and ENTER to Administer Passwords. 

4. From the Administer Passwords menu, press 3 and ENTER to Delete Password. 

5. At the prompt, enter the number of the password to be deleted. 

If you want auto-answer mode to remain active (this activity can be performed locally only), no 

further action is required. 


Disabling Remote Support Passwords and Modem Access 

If you want to disable modem call-back or call-through access (this activity can be performed 

locally only), go to the Modem Utilities menu on the Diagnostic Partition or Platform CD-ROM. 

From there, select Auto Answer On/Off, then select Disable Auto Answer. After you disable 

auto-answer, remote modem access is prevented until you select Enable Auto Answer or until 

you dial out from the server through the modem. 

Note: If you enable your modem for auto-answer, the command string that performs this function 

also enables password checking. 

Limitations of “Disable Password Checking” 

You cannot disable remote access by selecting the Disable Password Checking option from the 

Configure Modem menu. This option disables password checking only. 

If you select Disable All Passwords after enabling the modem for auto-answer, a caller has free 

access to your system console. Although operating system environments provide passwords, this is 

not true at the BIOS or Diagnostic Partition and Platform CD-ROM levels. 

It is recommended that you never disable password checking for the modem. 

Disabling Modem Passwords and Access from UNIX MP-RAS 

From the UNIX MP-RAS environment, you can run the cu utility to disable modem passwords and 

auto-answer mode. For more information on the UNIX MP-RAS cu command, refer to your 

operating system documentation. 

For information about using MP-RAS to define and delete modem passwords, refer to the “Setting 

Modem Passwords in UNIX MP-RAS” section later in this chapter. 

Disabling Modem Passwords and Access from NT 

Within the NT environment, you can use the NCR Remote software, the Terminal program, 

Remote Access Service (RAS), or other modem-related NT applications to disable modem 

passwords and auto-answer mode. 

To issue any commands to the remote modem while connected to a server running Windows NT, 

you may use the "Remote Modem Chit Chat" feature of the NCR Remote client. 

For more information, refer to your operating system documentation and to the “Modem 

Configuration and Dialing into a Windows NT System” section later in this chapter. 

6-24 Remote Support

Transferring Files to and from a Remote Location 


This section explains how to send files to and from your server. 

You can perform the following types of file transfers from the Diagnostic Partition or Platform 

CD-ROM menus: 

• Download files from a remote location to the server 

• Upload files from the server to a remote location 

If the file transfer is unsuccessful, the server will automatically reboot. If the file transfer is 

successful, the default is not to reboot the server. This reboot behavior upon successful transfer 

can be controlled either by the transfer program’s -r command line option or in the file transfer 

configuration file. 

Using NCR Remote Client for File Transfers 

Using the NCR Remote client, you may transfer files to and from a server running DOS 

(Diagnostic Partition mode), NCR MP-RAS UNIX, or Windows NT. See the help file or the NCR 

Remote Services User Guide for more information. 

PROCOMM Settings 

To transfer files using PROCOMM at your remote location, you can use either the default 

ZMODEM protocol or the YMODEM protocol. 

ZMODEM Settings 

The following table shows the PROCOMM software settings required to use the ZMODEM 

protocol. 

Option 

Receiver Crash Recovery 

Receiver Overwrite Options 

Sender Crash Recovery 

Sender Overwrite Options 

Transmit Window 

Required Setting 

Crash Recovery Off 

Always Overwrite 

Crash Recovery Off 

Always Overwrite 

2k - Window 

This setting is necessary when transmitting large files to your 

server at 38.4K baud. This alleviates (but does not eliminate) 

a problem where ZMODEM detects “Bad CRC” and resends 

many packets. If file downloads are terminated due to 

excessive retries, use 19.2K baud. 

Verify these settings (and modify them if necessary) by selecting Setup/Data/Transfer Protocol 

from PROCOMM’s Terminal window action bar. Perform the following actions from the Transfer 

Protocol window: 



1. Select Change Settings for Receiver Crash Recovery settings. 

2. Set the individual Crash Recovery and Overwrite options as specified in the table. 

3. Select Change Settings for Sender Crash Recovery settings. 

4. Set the individual Crash Recovery and Overwrite options as specified in the table. 

5. Select Transmit Method and select 2K-Window. 

YMODEM Settings 

If you plan to use the YMODEM protocol, make sure that you select the crash recovery option, 

Overwrite existing file. 

Note: You can change the transfer protocol from ZMODEM to YMODEM by selecting 

“Setup/Data/Transfer Protocol” from PROCOMM’s Terminal window action bar. From the 

Transfer Protocol window, select the down arrow button to the right of the Current Transfer 

Protocol list box. 

Downloading Files 

Perform the following steps to download files from a remote location to the server: 


2. Select Run Utilities and Diagnostics from the MS-DOS Startup menu of the Diagnostic 

Partition. Select Run CD Utilities and Diagnostics if you booted from the Platform CD- 

ROM. 


Note: If the Diagnostic Partition is not installed and you are executing from the Platform CD- 

ROM, you must first select Execute Utils from CD. 

4. Select File Transfer Utils from the Remote Support menu. 

5. Select File Download from the File Transfer Utilities menu. 

The system transfers you to a DOS shell and displays a DOS prompt. 

6. Use the rf command to download files. The next section explains how to use this command. 

You can obtain a list of valid command line options by entering rf -h at the DOS prompt. 

Default settings for the various rf command line options are defined in the file transfer 

configuration file, ft.cfg, discussed later in this section. 

Using the rf Command 

Use the rf (receive file) command to download files from a remote location to the server. By 

default, the rf command uses the ZMODEM protocol for file transfer. You can specify a command 

line option that lets you use the YMODEM protocol. 

The syntax for the rf command is the following: 

rf 

6-26 Remote Support


rf Command Options 

The following table lists the command line options for the rf command, defines their possible 

values and gives a brief description of each option. Default values are designated in boldface type. 

Option Values Description 

-b 300, 1200, 2400, 4800, 

9600, 19200, 38400, 

57600, 115200 

Baud rate 

Note: The file transfer baud rate must be the same as the 

console redirection baud rate. Only 9600, 19.2K, and 38.4K 

are recommended. 

-dd Directory into which files are downloaded 

Note: If you do not use the -dd option, the default directory 

is the directory name specified in the file transfer 

configuration file, ft.cfg. If no download directory is 

specified in ft.cfg, the current directory (\TMP) is used. The 

-dd command line option overrides the download directory 

setting in ft.cfg. 

-f 

\ 

Name of the directory in which the file transfer 

configuration file (ft.cfg) is located. The filename (ft.cfg) 

can also be overridden. 

Note: The default setting is the directory containing the rf 

executable file. This is the \REMOTE directory on your 

server. 

-h Display online help text 

-p 1, 2 Server COM port to use for file transfer 

Note: The COM port must be the same as the console 

redirection port. 

-r Reboot the server after receiving files 

-s x - XON/XOFF 

Type of flow control to use 

r - RTS/CTS 

n - none 

Note: The flow control setting must be the same as the 

console redirection flow control setting. 

-w 1-60 (8) Seconds to wait before sending file(s) from a remote 

location 

Note: You have approximately 30 seconds after the 

specified wait period to send the file from a remote 

location. If the file is not received in this time period, the rf 

program assumes that the file transfer failed. For example, 

using the default of 8 seconds, you must send the file from 

a remote location between 8 and 38 seconds after the 

entering the rf command. 

-y Use YMODEM for file transfer 

Note: When running the rf utility from the Platform CD-ROM, be sure to download a file to a 

“real” directory. When running from the Platform CD-ROM, your current directory may be a 

RAMDisk. (You can determine if you are in a RAMDisk directory by entering the DOS dir /p 

command and checking the volume name. If the volume name is MS-RAMDRIVE, then you are 

running from a RAMDisk directory.) 



If the current directory is a RAMDisk directory and you did not override the download directory 

setting, files are downloaded to the RAMDisk. In this case, when the server is rebooted, the 

RAMDisk directory and its contents are lost. 

Download Filenames 

The rf utility assigns the filenames specified at the remote (sending) location. You cannot override 

these filenames. 

rf Example 

The following command starts the receive file program on the remote server: 

rf 

If the file transfer configuration file (ft.cfg) has not been modified, the program waits about 8 

seconds before it expects to start receiving files from the remote location. If ft.cfg does not specify 

a download directory and you did not specify a directory name with the -dd option, files are placed 

in your current directory. The filenames are the same as those specified at the remote (sending) 

location. 

Uploading Files 

Perform the following steps to upload files from the server to a remote location: 


2. Select Run Utilities and Diagnostics from the MS-DOS Startup menu of the Diagnostic 

Partition. Select Run CD Utilities and Diagnostics if you booted from the Platform CD- 

ROM. 


Note: If the Diagnostic Partition is not installed and you are executing from the Platform CD- 

ROM, you must first select Execute Utils from CD. 

4. Select File Transfer Utils from the Remote Support menu. 

5. Select File Upload from the File Transfer Utilities menu. 

The system transfers you to a DOS shell and displays a DOS prompt. 

6. Use the sf command to upload files. The next section explains how to use this command. You 

can obtain a list of valid command line options by entering sf -h at the DOS prompt. Default 

settings for the various sf command line options are defined in the file transfer configuration 

file, ft.cfg, discussed later in this section. 

Using the sf Command 

Use the sf (send file) command to upload files from the server to a remote location. By default, the 

sf command uses the ZMODEM protocol for file transfer. You can specify a command line option 

that lets you use the YMODEM protocol. 

6-28 Remote Support


The syntax for the sf command is: 

sf 

sf Command Options 

The following table lists the command line options for the sf command, defines their possible 

values and gives a brief description of each option. Default values are designated in boldface type. 

Option Values Description 

-b 300, 1200, 2400, 4800, 

9600, 19200, 38400, 

57600, 115200 

-f 

\ 

Baud rate 

Note: The file transfer baud rate must be the same as 

the console redirection baud rate. Only 9600, 19.2K, and 

38.4K are recommended. 

Name of the directory in which the file transfer 

configuration file (ft.cfg) is located. The filename (ft.cfg) 

can also be overridden. 

Note: The default setting is the directory containing the 

sf executable file. This is the \REMOTE directory on your 

server. 

-h Display online help text 

-l File containing a list of files to send. (You might want to 

create such a file if you frequently send the same files.) 

Note: The specified file should be an ASCII file 

containing one filename per line. 

-p 1, 2 Server COM port to use for file transfer 

Note: The COM port must be the same as the console 

redirection port. 

-r Reboot machine after sending files 

-s x - XON/XOFF 


r - RTS/CTS 

n - none 

Note: The flow control setting must be the same as the 

console redirection flow control setting. 

-w 1-60 (8) Seconds to wait before sending file(s) to a remote 

location 

Note: You have approximately 30 seconds after the 

specified wait period to send the file(s) to a remote 

location. The wait period allows time to prepare the 

remote system to receive the file(s). If the remote 

location does not acknowledge the request to send the 

file(s) in this time period, the sf program assumes that 

the file transfer failed. For example, using the default of 8 

seconds, the remote system must acknowledge and 

begin processing the request to send file(s) between 8 

and 38 seconds after you enter the sf command. 

-y Use YMODEM for file transfer 



Specifying sf Filenames 

You can send multiple files using a single sf command. If you enter multiple file names on the sf 

command line, separate file names with a blank space. 

Alternately, you can define a list of filenames in an ASCII file (one name per line). Use the -l 

command line option to specify this ASCII file name when you enter the sf command. 

sf Examples 

The following command sends the config.sys and autoexec.bat files from the server to a remote 

location via ZMODEM: 

sf c:\config.sys c:\autoexec.bat 

The following command sends one or more files which are listed (one per line) in the c:\files.txt 

file: 

sf -l c:\files.txt 

For example, the c:\files.txt file might contain the following list of files to be sent: 

c:\autoexec.bat 

c:\config.sys 

c:\log\error.txt 

File Transfer Configuration File 

You can use the file transfer configuration file, ft.cfg, to set default options for the sf and rf 

commands. Unless you move this file, it is located in the same directory as the sf and rf executable 

files, \REMOTE. 

Runtime options that you specify on the command line override default options specified in the 

configuration file. 

Editing the ft.cfg File 

You can use any DOS ASCII file editor to modify the ft.cfg file in the Diagnostic Partition. You 

can also edit the ft.cfg file if you boot from the Platform CD-ROM. 

Because the CD-ROM is a read-only device, you must perform the following steps to edit and use 

the ft.cfg configuration file on the CD: 

1. Copy the file from CD to RAMDisk (x:\tmp where x is the RAMDisk directory) or some other 

writeable file system (for example, the A:\ drive). 

Note: You can determine whether you are in a RAMDisk directory by entering the DOS dir 

/p command and checking the volume name. If the volume name is MS-RAMDRIVE, then you 

are running from a RAMDisk directory. 

2. Use any DOS ASCII file editor to change and save the file. 

3. Use the -f command line option to specify the correct configuration file directory when you 

enter an sf or rf command. 

6-30 Remote Support


Configuration File Parameters 

The following table lists the configuration file parameters and their possible values, and gives a 

description of each parameter. 

Parameter Values Description 

Port= 1, 2 Server COM port to use for file transfer 

Note: The COM port must be the same as the 

console redirection port. Console redirection defaults 

to COM1. 

Baud= 300, 1200, 2400, 4800, 

9600, 19200, 38400, 

57600, 115200 

Baud rate 

Note: The file transfer baud rate must be the same 

as the console redirection baud rate. Console 

redirection defaults to 38400 baud. Only 9600, 19.2K, 

and 38.4K are recommended. 

DownloadDir= Directory into which files are downloaded on the 

server by the rf utility 

Note: Support does not specify a default directory. 

Files are downloaded into your current directory. 

Handshaking= 

Protocol= 

XON/XOFF 

RTS/CTS 

None 

ZMODEM 

YMODEM 


Note: The flow control setting must be the same as 

the console redirection flow control setting. Console 

redirection defaults to RTS/CTS + Carrier Detect 

monitoring. Choose RTS/CTS for file transfers. 

File transfer protocol 

Note: The default is ZMODEM. 

Filelist= File containing a list of files to send when using the sf 

utility 

Note: A default is specified. Files to be sent are 

specified on the sf command line. 

Reboot= 

Yes 

No 

Reboot your server after sending or receiving 

Reboot Delay= 1-60 Seconds to wait before rebooting 

Note: Default is 5 seconds. 

TransferDelay= 1-60 Seconds to wait before sending or receiving files 

Note: The default is 8 seconds. 

File Transfer Configuration File Example 

Following is an example of a file transfer configuration file. Note that you must enter each 

parameter on a separate line. 

Port=1 

Baud=38400 

Handshaking=RTSCTS 

Protocol=ZMODEM 

TransferDelay=8 


Modem Configuration in UNIX MP-RAS 


If you want your server to be accessed from a remote console (such as from a remote support 

center or from a remote help desk) via the remote support modem, you must configure the modem 

within the Diagnostic Partition or MP-RAS. 

After installation of the operating system is complete, you can log in and perform the procedure 

below: 

Note: Set or verify a modem password and send the initialization string to the modem each time 

you want to use the remote support modem. 

1. Add the following line to the end of the /etc/uucp/Modems file: 

Direct term/00,M - 38400 safire288init 

2. Edit the /etc/uucp/Dialers file to correspond to the modem settings required by the Diagnostic 

Partition. 

– Locate the safire288init string 

– Change *C0 to *C1 

– At the end of the line, add a space and then type ATQ1 

– Save your modifications 

3. Set a call-back or call-through password. Refer to the “Setting Modem Passwords in UNIX 

MP-RAS” section for information about setting a password. 

4. Type the following command at the prompt and press ENTER to send the initialization string to 

the modem. 

/usr/lib/uucp/setmodem -d -m safire288init /dev/term/00 

Note: There are some security issues related to having an auto answer modem enabled on your 

server. Refer to the “Configuring a Remote Support Modem” section for additional information. 

Enable Console Redirection 

Enter the following command to enable console redirection while UNIX MP-RAS is running: 

contty -s /dev/tern/00 -b 38400 -p 

where the -b parameter specifies the redirection baud rate and the -p parameter specifies that 

redirection should be maintained through system reboot. 

Access from a Remote Terminal 

To access the server’s BIOS and MP-RAS consoles from a single remote terminal running 

PROCOMM PLUS or NCR Remote Client software, you must specify the “ansi-bbs” terminal 

type in MP-RAS. Use the following instruction to specify this: 

TERM = ansi-bbs 

6-32 Remote Support


Send a String to the Remote Support Modem 

To send an initialization string to the remote support modem, use the following command: 

/usr/lib/uucp/setmodem -d -m safire288init /dev/term/00 

Note: The setmodem command uses information in the /etc/uucp/Dialers file to initialize the 

modem. The modem command in the Dialers file is designed to work with the default settings of 

the Diagnostic Partition and Platform CD-ROM modem utilities, and the default configuration of 

BIOS-level console redirection. 

If you change the modem command string in the Dialers file and send the modified command to the 

modem, it might configure the modem incorrectly for BIOS redirection. A similar problem might 

occur if an MP-RAS application reconfigures the modem. 

If you experience problems when performing BIOS-level redirection, go to the Diagnostic Partition 

or Platform CD-ROM’s Modem Utilities menu, select Auto Answer On/Off, then Enable Auto 

Answer or Re-init Modem. This synchronizes your modem with the current BIOS-level 

redirection settings. 

Setting Modem Passwords in UNIX MP-RAS 

Some modems provide call-through and call-back password support. The modem provided with 

your server supports these passwords. 

When using call-through passwords, the modem does not connect to the server system until the 

user at the remote system enters a valid call-through password. Do not confuse this with the 

operating system login password. The call-through password must be entered first and is in 

addition to any operating system login password. 

For modem setup for remote management, the call-through password provides a level of security 

when the server is out-of-service (for example, when the operating system is not running). 

Call-back passwords are similar to call-through passwords except that a call-back password 

requires a call-back phone number as well as a password. 

With MP-RAS, there are two basic ways to set up either type of modem password. One is to 

include the passwords in the modem initialization strings in the /etc/uucp/Dialers file. You can edit 

the initialization string directly with any editor program or modify it using the sysadm menus 

under the following tasks: 

 

 

Another method for defining a modem password is to connect directly to the modem using the cu 

utility and issue the appropriate modem commands. 



For the Lasat Safire 288 modem, there are up to four passwords for use as either call-back or callthrough 

passwords. The format of the modem command to set passwords is as follows: 

AT*Px:password:call-back_number 

where 

• x is the password number (0-3) 

• password is the modem password, comprised of at least 6 and no more than 12 alphanumeric 

characters 

• call-back_number is the optional call-back phone number. The call-back_number is 

comprised of up to 22 numbers and dialing characters (dashes, commas and parentheses). 

When you set a call-through password, omit the call-back number and its preceding colon. 

Note: If you enter a password that contains less than 6 or more than 12 characters, the password 

currently stored at the specified password number is deleted. Also, the modem returns an error 

indicating that an invalid password was entered. Use this mechanism to manually delete a 

password. 

The following table lists other password-related AT commands: 

Command 

at*c1 

at*c0 

at*l 

Description 

enable password checking at the modem 

disable password checking at the modem 

list all currently defined passwords 

Sample cu Session 

Following is a sample cu command session that shows how to set the modem’s password 0 to 

SUPONLY4300 in call-through mode. The example assumes that you have a Lasat modem 

connected to the COM1 serial port. Commands typed by the user are in bold, system responses are 

in normal font, and comments on the sequence are in italics. 

1. Starting at the shell prompt, enter: 

# cu -lterm/00 

The system displays: 

Connected 

2. Enter: 

ATE1Q0 

This command enables echo and OK responses. The modem may not echo this command back 

to you. The system displays: 

OK 

3. Enter: 

AT*L 

6-34 Remote Support


This command displays all current passwords, as follows: 

0 - (blank or current password : call back number) 





Note: Only the Lasat modem has four passwords. 

4. Enter: 

AT*P0:SUPONLY4300 

This command sets the call-through password. The system displays: 

OK 

5. Enter: 

AT*C1 

This command enables password checking. The system displays: 

OK 

6. Enter: 

ATZ 

This command restores the modem state to no echo. 

7. Enter: 

ATEOQ1 

This command resets modem result codes. 

8. Enter the following to end the cu session: 

~ 

The system displays: 

Disconnected 

# 

Note: Password 0 contains the remote password. The remote password is a call-back or callthrough 

password that can be manipulated from a remote location. It is discussed in detail earlier in 

this chapter in the “Using a Remote Password” section. 

Password 0 is automatically modified when you enable or disable a password using the Set 

Remote Password and Delete Remote Password menu items on the Diagnostic Partition and 

Platform CD-ROM Modem Utilities menu. 

Setting Passwords in the Dialers File 

The alternate way to set modem passwords involves adding initialization strings to the 

/etc/uucp/Dialers file. 

For example, assume that you want to define a call-through password of SUPONLY4300 and a 

call-back password of SUPPORT that dials 1-800-555-1212. 



You would add the following line to the Dialers file: 

safire288passwd =,- 

, “” \MATQ0 OK\r AT*P0:SUPONLY4300 OK\r AT*P1:SUPPORT:1,800,555- 

1212 OK\r AT*C1 OK\r ATZ 

To initialize the passwords specified in the Dialers file, enter the following command at the MP- 

RAS system prompt: 

/usr/lib/uucp/setmodem -d -m safire288passwd /dev/term/00 

Other Modem Command Strings 

When using the server’s modem in a UNIX MP-RAS environment, you may also need the 

following command strings: 

• Enable Auto-Answer – at&f0&d0&c1l3*k1*c1e0s0=1&q5 

• Disable Auto-Answer – ats0=0 

• Hang Up – ath0 

• Store Current Modem Configuration in Modem NVRAM – at&w0&w1&y0 

• Enable Password Checking –- at*c1 

• Disable Password Checking – at*c0 

• Query Country Code – ati5 

• List current passwords – at*l 

You can send these strings to the modem using the MP-RAS cu utility or the modem utilities on the 

server’s Diagnostic Partition or Platform CD-ROM. 

For more information on the individual command strings used by the Diagnostic Partition’s Modem 

Configuration Utilities, see the Server Software Guide (4SMP). 

6-36 Remote Support

Dialing into a UNIX MP-RAS System 

Dialing into a UNIX MP-RAS System 

UNIX MP-RAS provides two levels of access through a system’s COM ports: 

• If the contty command has been issued, or BIOS-level console redirection is active, MP-RAS 

transfers control of the system console to a remote user connected through the system COM 

port. 

• If the contty command has not been issued, and BIOS-level redirection is disabled, MP-RAS 

port monitor services control the system’s COM ports and present a normal login prompt to a 

remote user. 


Modem Configuration and Dialing into a Windows NT System 

Modem Configuration and Dialing into a Windows NT 

System 

The NCR Remote products provide facilities for a remote user to connect to an NCR NT server 

over a dial-up telephone line or local area network (LAN) for the purpose of diagnosing and 

troubleshooting problems. NCR Remote is composed of two components - Server and Client 

software. More information can be found on these products in the NCR Remote Services User 

Guide. 

The following functionality is provided in an NT environment by the NCR Remote Client and 

Server products: 

• Command line utilities to shutdown the system and to access the registry editor, event log 

viewer, and process viewer 

• Support for native Windows NT security 

• File transfers 

• Logged actions/results 

• Remote listing of active windows on server desktop 

• Remote screen capture 

• Remote chat 

• Remote modem configuration 

To issue any commands to the remote modem while connected to a server running Windows NT, 

you may use the "Remote Modem Chit Chat" feature of the NCR Remote client. 

The following modem (AT) command strings may be needed in the NT environment: 

• Enable Auto-Answer – at&f0&d0&c1l3*k1*c1e0s0=1&q5 

• Disable Auto-Answer – ats0=0 

• Hang Up – ath0 

• Store Current Modem Configuration in Modem NVRAM – at&w0&w1&y0 

• Enable Password Checking – at*c1 

• Disable Password Checking – at*c0 

• Define a Password – at*pn:password:call-back number (See “Setting Modem Passwords in 

UNIX MP-RAS,” for more information on this modem command.) 

• Query Country Code –- ati5 

For more information on the individual command strings used by the Diagnostic Partition’s Modem 

Configuration Utilities, see Server Software Guide (4SMP). 

6-38 Remote Support

Using the Server Management Board for Remote Management 

Using the Server Management Board for Remote 

Management 

The Server Management Board (SMB), with the associated server manager software, enables the 

monitoring and control of the server in-band when the server and network are operating normally, 

or out-of-band over a phone-line. 

For complete information on the SMB and how it is used for remote management, see the Server 

Management Product Manual. 


Using the Server Monitor Module for Remote Management 

Using the Server Monitor Module for Remote 

Management 

The Server Monitor Module (SMM) is an ISA adapter with an on-board battery-backed CPU. It 

provides server management and remote access capabilities for a server system. 

Installing the SMM 

To install the SMM, refer to the LANDesk® Server Monitor Module Installation and User’s 

Guide packaged with the adapter hardware. After completing the installation of the adapter, run the 

SCU (System Configuration Utility) from the Diagnostic Partition or Platform CD-ROM. See the 

Server Software Guide (4SMP) for additional information about the SCU. 

Add the SMM adapter to your system configuration using the SMM configuration file, 

!INT0016.CFG. The default resources required by the adapter are: 

Parameter 

Address 

IRQ 5 

DMA 3 

Default 

C8000 

PCMCIA Modem 

To provide alerting when the server is powered off or to support console redirection functions, a 

PCMCIA modem (14.4 to 28.8 KB) must be installed on the SMM. This modem can communicate 

with remote and server management software or a paging service. Setting up the modem is 

dependent upon the operating environment and the server administration application installed on 

the system. 

Software 

NT users can install the Server Manager from the ValuePlus CD to operate with the Server 

Monitor Module. SAM does not support console redirection at this time, but it does support server 

management through the SMM. 

On UNIX MP-RAS systems, add the servermon package included with the operating system. 

Information on installing and using servermon and SAM is available with your operating system 

documentation. 

In order to use the server management and console redirection capabilities of the Server Monitor 

Module, you must install monitoring console software on a remote system. Available software 

includes SAM for NT and the smmremote package for UNIX MP-RAS. You can also use the 

Intel LANDesk ® Server Manager application (Release 1.3) as a remote server management and 

remote console application, running on a Windows95, 3.x or NT system. 

6-40 Remote Support


The Intel LANDesk ® Server Manager software is not provided, but may already be running in a 

heterogeneous system where an Windows NT or MP-RAS system is to be installed. Refer to the 

documentation provided with the LANDesk ® Server Manager software for information about 

installing the software, connecting to a Server Monitor Module, and using the various features of 

the SMM. 

Setting Up UNIX MP-RAS servermon for Console Redirection Support 

With LANDesk 

The Server Monitor Module provides the ability to redirect console operations to a LANDesk 

console system. This means that the server’s console display is duplicated at the remote LANDesk 

console, and that keyboard input entered at the LANDesk console has the same effect as keyboard 

input at the server console. 

The MP-RAS data file /etc/default/servermon defines operating defaults for the Server Monitor 

Module. One of the parameters in this file disables and enables console redirection. By default, 

console redirection is enabled at installation. You can use the following command to disable 

redirection: 

defadm servermon CONSOLE_REDIRECT=0 

To enable console redirection at a later date, use the following command: 

defadm servermon CONSOLE_REDIRECT=1 

The SMM hardware should be reset after issuing either the “disable” or “enable console 

redirection” command. 



6-42 Remote Support

Chapter 7 

Troubleshooting 

Codes and Error Messages 

POST Error Codes 

The system BIOS displays error messages on the video screen. At power-on, before the video 

adapter has been initialized, beep codes are used to inform you of errors. POST (Power On Self 

Test) error codes are logged in NVRAM and the Extended BIOS Data Area (EBDA). 

BIOS displays POST error codes both on the LCD panel and the console monitor. 

Note: If the node monitor is managed through a console switch, be sure the console switch is set to 

view the appropriate node. 

When you turn on the system, POST displays messages that provide information about the system. 

If a failure occurs, POST uses beep codes to indicate errors in hardware, software, or firmware. If 

POST can display a message on the video display screen, it causes the speaker to beep twice as the 

message displays. 

This rest of this section contains the following: 

• POST beep codes 

• POST codes 

• POST error messages 

POST Beep Codes 

At power-on, before the video adapter has been initialized, BIOS indicates failures by using 

audible beep codes. A given code consists of a series of individual beeps, each equal in length. The 

table below describes the error condition associated with each code and the corresponding POST 

checkpoint code as seen by a “port-80h” card. 

Beep Count Port 80 Codes Error Condition 

1 71h Refresh failure 

2 72h Parity cannot be reset 

3 73h First 4 MB memory failure 

4 74h Timer not operational 

5 75h Processor failure 

6 76h Keyboard controller gate A20 is off (v_mode) 



Beep Count Port 80 Codes Error Condition 

7 77h Exception interrupt error 

8 78h Display memory R/W error 

9 79h ROM checksum error 

10 7Ah Shutdown register R/W error 

POST Codes and Countdown Codes 

At power-on, after the video adapter has been initialized, BIOS indicates the current testing phase 

by sending a 2-digit hex code to I/O location 80h. If a port-80h board is installed, it displays this 2- 

digit code on a pair of hex display LEDs. The current countdown code also displays on the LCD 

panel after this panel is initialized. 

Standard Port-80 Codes and Countdown Codes 

The following table shows the standard port-80 and countdown codes: 

Port 80 Code 

D0h 

D1h 

D2h 

D3h 

D4h 

D5h 

D6h 

Countdown 

Code 

Reason 

Early multi-processor initialization, telling 

processor to enter real big mode 

Power On Initialization 

Disable NMI 

Reset video controller 

Enter real mode 

Checksum the 8 KB loader BIOS 

Loader BIOS checksum good 

D7h 900 Check if Keyboard Controller (KBC) buffers 

are free 

D8h 

D9h 

DAh 

Issue BAT (basic assurance test) command to 

KBC 

Read BAT results 

Check if Keyboard Controller passed BAT 

DBh 820 Keyboard initialization passed 

DDh 

DFh 

Disable keyboard and auxiliary devices 

Disable both DMA controllers 

E0h 780 Preliminary initialization of PICs 

E1h 

E2h 

Enter real big mode and initialize chipset, size 

memory 

Initialize timer 2 for speaker 

E3h 760 Initialize timer channel 0 for system timer 

7-2 Troubleshooting


Port 80 Code 

E4h 

Countdown 

Code 

Reason 

Clear any pending parity errors 

E6h 740 Test RAM from 0-640 KB 

E7h 

Test and initialize 2 MB memory 

E8h 

RAM failure, remap memory partitions and 

test again 

E9h 

RAM test complete, passed. Clear parity 

errors. 

EAh 730 Set up stack at 30:100, enable cache and 

shadow BIOS 

EBh 

Initialize code dispatcher 

ECh 

Make F000h DRAM R/W Enabled 

EDh 

Dispatch POST 

23h 700 Initializations before setting up vector table 

24h 

Setup interrupt vector table 

0Dh 

Check CMOS clear jumper 

0Eh 690 Check validity of CMOS 

0Fh 

Force CMOS defaults if required 

10h 

CMOS initialization complete 

25h 

Nothing 

28h 

Set monochrome mode 

29h 

Set color display 

2ah 

Clear parity status if any, initialize warm reset 

flag 

2bh 

Video auto-configuration and initialization 

F0h 

EISA Slot Initialization 

F1h 

Enable extended NMI sources 

F2h 

Test extended NMI sources 

2ch 580 Conventional video option ROM search 

2dh 

Scan user flash 

2eh 570 Initialize monochrome display if no other video 

present 

2fh 560 Test buffer memory for monochrome 

30h 

Check vertical and horizontal retrace 

31h 

Test for color display memory if no external 

video BIOS found 

32h 

Check vertical retrace 

34h 

Sign on message 

36h 

Initialize Messaging Services and clear screen 

37h 500 Custom sign on display 



Port 80 Code 

Countdown 

Code 

Reason 

80h 370 Keyboard/mouse port check 

81h 

Keyboard controller initialization and testing 

83h 

Check if keyboard is locked 

F5h 330 Initialize mouse 

39h 

Keyboard, mouse and other sign-ons 

3bh 

Prepare for memory test 

43h 290 Decide memory size from chipset 

4Fh 

Disable cache, test memory and display 

memory size on screen 

52h 

Initialize for the other processors in MP 

system, reset DMA controller 

61h 250 DMA register tests 

62h 

DMA test OK 

65h 

Initialize 8237 DMA controller 

66h 

Clear DMA write request register and mask 

set/reset register 

67h 220 8259 Interrupt controller test 

F4h 

Enable extended NMI sources 

8Ch 140 Enable console redirection, initialize remaining 

Plug-N-Play devices (i.e. other than video), 

initialize IPL, initialize IDE controller 

8Fh 130 Floppy Initialization 

92h 

Set printer, RS-232 time out 

96h 

Optional ROM scan and initialize above 

C800h 

97h 080 Scan User flash and conventional option ROM 

scan 

98h 

Scan User flash area 

9Ah 

Clear soft reset flag, complete MP Table 

9Dh 070 Timer data area initialization 

A0h 

Printer setup 

A1h 

RS232 setup 

A2h 

Check for stuck key 

ABh 

Before NPX test and initialization 

ACh 060 NPX test and initialization 

ADh 

Update coprocessor information in CMOS and 

recalculate checksum 

AEh 

Set typematic rate 

AFh 050 Keyboard read ID command 

7-4 Troubleshooting


Port 80 Code 

B0h 

A3h 

A6h 

Countdown 

Code 

Reason 

Wait for READ ID response 

Display POST errors 

Before Setup 

A7h 030 Call Setup if required, prompt for password if 

enabled 

B1h 

B3h 

B4H 

Enable Cache for boot 

Setup display mode set 

Jump to pre-OS code 

BBh 020 Initialize SMI code, prepare for boot 

00h 000 Prompt to boot Diagnostic Partition or execute 

normal operating system boot 

Recovery Port-80 Codes and Countdown Codes 

During BIOS recovery, the diskette in drive A is booted, and a BIOS image is automatically 

installed. 

The following table shows the recovery port-80 and countdown codes: 

Port 80 

Code 

02h 

08h 

13h 

Countdown 

Code 

Reason 

Disable internal cache 

Disable DMA controller #1, #2, disable 

interrupt controller #1, #2, and reset video 

display 

Initialize all chipset registers (Enable LCD 

display here) 

15h 900 Initialize system timer 

1Bh 800 Real mode base 64 KB test 

20h 700 16 KB base RAM test 

23h 650 Setup interrupt vectors 

40h 600 Test memory in virtual mode 

65h 500 Initialize 8237 DMA controller 

67h 400 8259 interrupt controller test 

80h 300 Unmask diskette, keyboard and timer 

interrupts 

88h 200 Floppy unit initialization 

A0h 100 Cache enable 

00h 000 Boot OS 



POST Error Codes and Messages 

The BIOS indicates errors as follows: 

• By writing an error code to the PS/2-standard logging area in the Extended BIOS Data Area 

• By displaying a POST error code and message on the screen 

The following table shows the POST error codes and messages. 

Number 

Error Message 

0002 Primary Boot Device Not Found 

0010 Cache Memory Failure, Do Not Enable Cache 

0015 Primary Output Device Not Found 

0016 Primary Input Device Not Found 

0041 EISA ID Mismatch for Slot 

0042 ISA Configuration Contains Invalid Info 

0043 EISA Invalid Configuration for Slot 

0044 EISA Config NOT ASSURED! 

0045 EISA Expansion Board Not Ready in Slot 

0047 EISA CMOS Configuration Not Set 

0048 EISA CMOS Checksum Failure 

0049 EISA NVRAM Invalid 

0050 PNP Memory Conflict 

0051 PNP 32-bit Memory Conflict 

0052 PNP IRQ Conflict 

0053 PNP DMA Conflict 

0054 PNP Error Log Is Full 

0055 Bad PNP Serial ID Checksum 

0056 Bad PNP Resource Data Checksum 

0060 Keyboard Is Locked ... Please Unlock It 

0070 CMOS Time & Date Not Set 

0080 Option ROM has bad checksum 

0081 Custom Binary Checksum Failure 

0083 Shadow of PCI ROM Failed 

0084 Shadow of EISA ROM Failed 

0085 Shadow of ISA ROM Failed 

0131 Floppy Drive A: 

0132 Floppy Drive B: 

0135 Floppy Disk Controller Failure 

0140 Shadow of System BIOS Failed 

7-6 Troubleshooting


Number 

Error Message 

0170 Disabled CPU Slot # 

0171 CPU Failure - Slot 1, CPU # 1 




0175 CPU modules are incompatible or one is not present 

Note: If a processor board is removed, it must be replaced 

with a terminator board or another processor board. If a 

processor board slot on the system baseboard is empty, 

the server either does not boot or does not operate 

correctly. Both connectors on the system baseboard must 

be populated in order to provide proper electrical 

termination of the system bus. 

0176 Previous CPU Failure - Slot 1, CPU # 1 




0180 Attempting to boot with failed CPU 

0181 BSP Switched, System May Be In Uniprocessor Mode 

0191 CMOS Battery Failed 

0195 CMOS System Options Not Set 

0198 CMOS Checksum Invalid 

0289 System Memory Size Mismatch 

0295 Address Line Short Detected 

0297 Memory Size Decreased 

0299 ECC Error Correction failure 

0301 ECC Single bit correction failed, Correction Disabled 

0302 ECC Double bit Error 

0303 ECC SIMMs Incompatible 

0304 Invalid Configuration For Memory Sizes Between Banks 

0310 ECC Address failure, Partition # 

0313 ECC Memory Size Decreased, Bank # 

0370 Keyboard Controller Error 

0373 Keyboard Stuck Key Detected 

0375 Keyboard and Mouse Swapped 

0380 ECC SIMM failure, Board in slot 1 SIMM # 

0392 ECC SIMM failure, Board in slot 2 SIMM # 

0430 Timer Channel 2 Failure 

0440 Gate-A20 Failure 



Number Error Message 

0441 Unexpected Interrupt in Protected Mode 

0445 Master Interrupt Controller Error 

0446 Slave Interrupt Controller Error 

0450 Master DMA Controller Error 

0451 Slave DMA Controller Error 

0452 DMA Controller Error 

0460 Fail-safe Timer NMI Failure 

0461 Software Port NMI Failure 

0465 Bus Timeout NMI in Slot 

0467 Expansion Board NMI in Slot 

0501 PCI System Error 

0510 PCI Parity Error 

0511 PCI System Error 

0710 System Board Device Resource Conflict 

0711 Static Device Resource Conflict 

0780 PCI Segment 1 Memory Request Exceeds 998 MB 

0781 PCI Segment 1 I/O Request Exceeds 12K 

0782 PCI I/O Request Exceeds Amount Available 

0783 PCI Memory Request Exceeds Amount Available 

0784 Illegal Bus For Memory Request Below 1 MB 

0785 Memory Request Below 1 MB Exceeds 1 MB 

0800 PCI I/O Port Conflict 

0801 PCI Memory Conflict 

0802 PCI IRQ Conflict 

0803 PCI Error Log is Full 

0804 PCI ROM Not Found, May Be OK For This Card 

0805 Insufficient Memory To Shadow PCI ROM 

0806 Memory Allocation Failure For Second PCI Request 

0809 Shadow of PCI ROM failed 

0810 Floppy Disk Controller Resource Conflict 

0811 Primary IDE Controller Resource Conflict 

0812 Secondary IDE Controller Resource Conflict 

0815 Parallel Port Resource Conflict 

0816 Serial Port 1 Resource Conflict 

0817 Serial Port 2 Resource Conflict 

0820 Expansion Board Disabled in Slot 

0900 NVRAM Checksum Error, NVRAM Cleared 

0903 NVRAM Data Invalid, NVRAM Cleared 

7-8 Troubleshooting


Number Error Message 

0905 NVRAM Cleared By Jumper 

0906 Password Cleared By Jumper 

0982 I/O Expansion Board NMI in Slot 

0984 Expansion Board Disabled in Slot 

0985 Fail-safe Timer NMI 

0986 System Reset caused by Watchdog Timer 

0987 Bus Timeout NMI in Slot 


Resetting the Node 


Keys 

Ctrl+Alt+Del 

Pressing these keys clears system memory and reloads the operating system. This process is called 

a “soft boot” reset. 

Note: The soft boot process does not automatically reset a system running Windows NT Server. 

The soft boot process does offer you the opportunity to perform a shutdown or to log off from the 

system, as well as several other options. 

Reset Button 

Pushing the reset button clears the system memory, restarts POST, and reloads the operating 

system. 

Power On/Off 

Turning the power off and on with the DC push-button switch on the front panel has the same 

effect as pushing the reset button, except that power is halted to all peripherals. This process is 

called a “cold boot” reset. 

Initial Node Start 

Problems that occur at initial system startup are usually caused by incorrect software installation 

or system configuration. Hardware failure is a less frequent cause. 

7-10 Troubleshooting


Node Reset Checklist 

When problems occur during a node reset, check the following: 

• Is AC power available at the wall outlet 

• Is the power source on (UPS or AC box) 

• Is the node power cord properly connected to the power source 

• Did you press the DC power on/off push-button switch on the front panel to turn on the node 

(Power-on light should be lit.) 

• Are all cables correctly connected and secured 

• Are there any conflicts between add-in boards⎯for example, two add-in boards sharing the 

same interrupt 

In the case of ISA boards, it is necessary to add the boards manually, using the System 

Configuration Utility (SCU) to avoid resource conflicts with installed EISA and PCI boards. 

Refer to the Server Software Guide (4SMP) for more information about adding ISA boards to 

your system. 

• If the system has a hard disk drive, is it properly formatted or defined 

• Are all device drivers properly installed For information about installing drivers, see the 

Server Software Guide (4SMP). 

• Are the configuration settings made with the System Configuration Utility (SCU) correct For 

information about running the SCU, see the Server Software Guide (4SMP). Some SCU 

settings are set to certain values based on the operating environment being installed. Refer to 

the installation guide for your operating environment (Installing MP-RAS or Installing 

Windows NT Server) to determine the correct settings. 

• Is the operating system properly loaded Refer to the operating system documentation. 

• If you have more than 2GB DIMM memory and are running Windows NT 4.0, have you 

contacted your service representative before installing more memory or installing Windows NT 

4.0 


Verifying New Application Software 

Verifying New Application Software 

Problems that occur when you run new application software are usually related to the software. 

Faulty equipment is usually not the cause of the error, especially if other software runs correctly. 

If problems occur when running new application software, check the following: 

• Does the node meet the minimum hardware requirements for the software Refer to the 

software documentation for system hardware requirements. 

• Is the software an authorized copy If not, get one; unauthorized copies often do not work. 

• If you are running the software from a diskette, is it a good copy Does your operating system 

support running software from diskette 

• If you are running the software from a hard disk drive, is the software correctly installed 

Were all necessary procedures followed and files installed 

• Are the correct device drivers installed 

• Is the software correctly configured for the node 

• Are you using the software correctly 

If the problems persist, contact the software vendor’s customer service representative. 


Checking for Equipment Failure 

Checking for Equipment Failure 

Problems that occur after the system hardware and software have been running correctly often 

indicate equipment failure. 

To check for equipment failure, check the following: 

• If you are running the software from a diskette, try a new copy of the software. Does your 

operating system support running software from diskette Can other software be run from this 

drive If not, you might have a problem with your diskette drive. 

• If you are running the software from a hard disk drive, try running it from the original 

installation media, if possible. 

• If the problems are intermittent, there may be a loose cable, dirt in the keyboard (if keyboard 

input is incorrect), a marginal power supply, or other random component failures. 

• If you suspect that a transient voltage spike, power outage, or brownout might have occurred, 

reload the software and try running it again. (Symptoms of voltage spikes include a flickering 

video display, unexpected system reboots, and the system not responding to user commands.) 

Note: If you are receiving random errors in your data files, voltage spikes on your power line may 

be corrupting them. Verify there is a surge suppressor between the power outlet and the server 

power cord. 

If you receive any error messages, refer to the “Codes and Error Messages“ section of this chapter 

for an explanation of the messages and suggested corrective actions. 


Testing Node Bring-Up 


Preparing the Node for Diagnostic Testing 

Before disconnecting any peripheral cables from the node, turn off the node and any external 

peripheral devices. Failure to do so can cause permanent damage to the node and/or the peripheral 

devices. 

To prepare the node for diagnostic testing: 

1. Turn off the node and all external peripheral devices. Disconnect all peripheral devices from 

the node, except the keyboard, mouse, and video monitor. 

2. Make sure the system (UPS or AC box) power cord is plugged into a properly grounded power 

source. 

3. Make sure your video display monitor and keyboard are correctly connected to the node. Turn 

on the video monitor. Set the video monitor’s brightness and contrast controls to at least twothirds 

of their maximum ranges. (Refer to the documentation supplied with your video display 

monitor.) 

4. If the operating system normally loads from the hard disk drive, make sure there is not a 

diskette in drive A. If the drive is empty, place a diskette containing the operating system files 

in drive A. 

5. Turn on the system. If the power LED does not light, refer to the “Power Light Does Not 

Light” section later in this chapter. 

Monitoring POST 

To monitor power-on self-test (POST): 

1. Each time you turn on the server, POST checks the system board, CPU module(s), ECC 

memory module, keyboard, and most installed peripheral devices. 

As each mass storage device is checked, its activity light should turn on briefly. If it does not, 

see the appropriate discussion later in this chapter -- “Flex Drive Activity Light Does Not 

Light” or “SCSI Disk Drive Activity Light Does Not Light.” 

2. During the memory test, POST displays the amount of memory that it is able to access and 

test. Depending on the amount of memory installed on the ECC memory module, the memory 

test may take several minutes to complete. 

3. After a soft boot (pressing CTRL+ALT+DEL), POST does not test the memory. 

The following message displays: 

Press key if you want to run SETUP 

Keyboard.....Detected 

Mouse........Detected 

4. If you do not press F1, the message remains for a few seconds, the system beeps once, and the 

boot process continues. The following prompt displays: 

Enter Control-P to start NCR PCI SCSI Configuration Utility (2.00) 



5. If you do not press CTRL+P, the boot process continues. 

Press CTRL+P to use the utility to set SCSI IDs for external devices attached to PQS adapters 

in the node. When the utility displays, follow the screen prompts. When you are done, you will 

return to the boot process. For details about the NCR PCI SCSI Configuration utility, see the 

NCR PCI SCSI Host Adapter Service Guide. 

6. After the NCR PCI SCSI Configuration utility prompt, the boot process continues to the 

following prompt: 

Press for SCSISelect(TM) Utility! 

7. If you do not press CTRL+A, the boot process continues. 

Press CTRL+A if you need to configure SCSI devices in your server that are attached to one of 

the onboard controllers. When the utility displays, follow the instructions on your monitor to 

configure the onboard SCSI AIC-7880 host adapter settings and run the SCSI disk utilities. 

When you are done, you will return to the boot process. 

8. When the BIOS POST process and the adapter BIOS scans have completed, the node displays 

the following prompt: 

Press to boot the Diagnostic Partition, for Normal Boot 

If this prompt does not appear, refer to “Missing Boot Path Prompt” later in this chapter. 

If the server halts before POST completes running, a beep code sounds, indicating a fatal 

system error that requires immediate attention. Note the screen display and write down any 

beep code emitted. (See the “Codes and Error Messages” section in this chapter for a list of 

beep codes.) This information is useful to your service representative. 

9. Once the system boots up, the operating system prompt displays on the screen. 

If the operating system prompt does not appear, check for possible incorrect software 

installation or system configuration. 


Running System Diagnostics 


If your server does not boot or operate properly, you might need to run system diagnostics to 

determine the problem. This section describes some problem situations that might require you to 

run system diagnostics. 

Definitions 

You should be familiar with the following terms before reading the rest of this section: 

Out-of-service diagnostics 

Hardware-level diagnostics that require you to shut down your operating system before 

running them 

In-service diagnostics 

Diagnostics that you can run while your operating system is running 

Running Out-of-Service Diagnostics 

To run out-of-service diagnostics, you must boot to the Diagnostic Partition or the Platform CD- 

ROM. See the Server Software Guide (4SMP) for information about accessing the Diagnostic 

Partition. 

Following are some situations when you might run out-of-service diagnostics: 

• The server fails to load and/or boot the operating system software when you turn on the power 

and select normal boot 

• The server fails to load and/or boot the operating system software after you add additional 

hardware such as more memory, processors, SCSI devices, adapter cards, and so on 

• The operating system software panics and/or hangs repeatedly and you have not recently made 

changes to it such as a kernel patch, a new application which required a kernel rebuild, or a 

changed kernel tuning parameter value 

When Not to Run Out-of-Service Diagnostics 

Following are some situations when you should not run out-of-service diagnostics: 

• The operating system software panics and/or hangs repeatedly after you made a change to it 

such as a kernel patch, a new application which required a kernel rebuild, or a changed kernel 

tuning parameter value 

• The server runs normally but one of the user applications fails to execute correctly 

• A device such as printer, tape, disk, modem, network adapter, or terminal fails to function 

properly but the server’s operating system software is working. Run in-service-diagnostics to 

test the failing device. 



Additional Information 

For additional information about running diagnostics on your server, see the AMIDiag User’s 

Guide and AMIDiag Supplement. 


Problems and Solutions 


This section addresses possible problems and provides a checklist for problem solving. 

Power Light Does Not Light 

Check the following: 

• Is the node’s top cover in place The intrusion switch will not allow power-on without the 

cover. 

• Is the node operating normally If so, the power LED is probably defective. 

• Are there other problems with the system If so, check the items listed under “Node Boots, 

Then Shuts Down.” 

If all items are correct and problems persist, contact your service representative or authorized 

dealer for assistance. 

Node Boots, Then Shuts Down 


• Does the error log indicate a tandem fan failure in a node 

Note: In addition to the chassis cooling fans, each power supply contains a fan as one of its 

integral parts. There are no serviceable components in a power supply. Because hazardous 

voltages may be present within a power supply at any time, do not open a power supply for 

any reason. 

• What is the battery status on the UPS Check LEDs. See Chapter 2 for LED definitions. 

• Is the UPS serial cable connected to the node 

• Do you have the correct UPS serial cable 

• If you have more than 2GB DIMM memory and are running Windows NT 4.0, have you 

contacted your service representative before installing more memory or installing Windows NT 

4.0 

If the switches and connections are correct and AC power is available, the power supply has 

probably failed. Contact your service representative or authorized dealer for assistance. 

No Characters Appear on Screen 


• Is the console switch directed to the node that you wish to view 

• Is the keyboard working 

• Is the video monitor plugged in and turned on 



• Are the brightness and contrast controls on the video monitor properly adjusted 

• Are the video monitor switch settings correct 

• Are the cables connected correctly to the console switch 

• If you have just installed a monitor or console switch, did you use the long power cables (the 

power cables that were already installed) 

• Is the console switch turned on 

• Are the video monitor switch settings correct 

POST emits one long beep and four short beeps or a long-short-long-short beep pattern to indicate 

a possible problem with the video display controller. If you do not receive a beep pattern and 

characters do not appear, the video display monitor or video controller may have failed. If possible, 

try connecting a video display which you know works correctly to your server. If this still fails, 

contact your service representative or authorized dealer for assistance. 

Video Connection to Node Keeps Switching 

• Is Scan mode initiated on the console switch Press any key or move the mouse. 

Mouse Moves Erratically or Is Frozen 

• Reset the mouse through OSCAR or the reset switch. 

Incorrect or No Beep Codes 


• Is the speaker enabled 

• Is the signal cable connected to the front panel 

If the system operates normally, but there was no beep, the speaker may be defective. Use the SCU 

to verify that the speaker is enabled. See the Server Software Guide (4SMP) for more information. 

Characters Are Distorted or Incorrect 


• Are the brightness and contrast controls properly adjusted on the video monitor Refer to the 

video monitor documentation from the manufacturer. 

• Is the video monitor cable properly installed 

If the problem persists, the video monitor may be faulty or the monitor may be the incorrect type. 

Contact your service representative or authorized dealer for assistance. 



Flex Drive Activity Light Does Not Light 


• Is the diskette drive properly configured 

– If you are using the onboard diskette controller, use the SCU to make sure that “On-Board 

Floppy Controller” is set to “Enabled.” 

– If you are using an add-in diskette controller, make sure that “On-Board Floppy 

Controller” is set to “Disabled.” 

• Be sure the server has been configured with “Secure Boot Mode” disabled. Otherwise, it is not 

possible to boot from the diskette drive. 

For information about running the SCU, see the Server Software Guide (4SMP). 

If the problem persists, there may be a problem with the diskette drive, system board, or drive 

signal cable. Contact your service representative or authorized dealer for assistance. 

SCSI Disk Drive Activity Light Does Not Light 

If you have installed one or more hard disk drives in your system, check the following: 

• Is the hard disk drive properly configured 

• Do the SCSI IDs of drives located in the removable media bays conflict with drives attached to 

the hot-pluggable backplane 

If you received error messages, refer to the “Codes and Error Messages” section of this chapter for 

information about error messages. 

If you did not receive error messages, run the SCU and make sure that the hard disk drive is 

configured with the correct parameters. For information about running the SCU, see the Server 

Software Guide (4SMP). 

If the problem persists, there may be a problem with one of the following: 

• Hard disk drive 

• Add-in controller board 

• System board 

• Drive signal cable 

• LED connector 

Contact your service representative or authorized dealer for assistance. 



Cannot Boot from Hard Drive 

The following options must be enabled for you to boot from a hard drive attached to an on-board 

controller: 

Option 

SCSI ROM BIOS Scan 

Host Adapter BIOS 

How to Enable or Disable 

SCU or BIOS Setup Utility 

SCSISelect Utility 

These options are enabled by default. If you disable them for any reason, you must re-enable them 

before you can boot from the hard drive. 

In addition, one of Boot Options (First/Second/ Third/Fourth Boot Device, found in the SCU and 

BIOS Setup Utility) must be set to “Hard Disk” to boot your operating system from disk. The 

settings of these options are irrelevant when you boot from the Diagnostic Partition or Platform 

CD-ROM. 

Cannot Boot from CD-ROM 

The following options must be enabled for you to boot from the Platform CD-ROM: 

Option 

SCSI ROM BIOS Scan 

Host Adapter BIOS (for the 

adapter to which the CD-ROM 

device is connected) 

BIOS Support for Bootable CD- 

ROM 

BIOS Support for Int13 

Extension 

How to Enable or Disable 

SCU or BIOS Setup Utility 




These options are enabled by default. If you disable them for any reason, you must re-enable them 

before you can boot from the Platform CD-ROM. 

No Installation Menu When Booting from CD-ROM 

If the Diagnostic Partition is not installed on your boot disk, the installation version of the CD- 

ROM main menu should display when you boot from the Platform CD-ROM. If this menu does 

not display, check to make sure the boot disk is properly formatted and defined. 



Missing Boot Path Prompt 

You should receive the following prompt when POST completes: 

Press to boot the Diagnostic Partition, for Normal Boot 

If a Diagnostic Partition is not detected on drive C: (80h), the following startup message displays: 

Diagnostic Partition is not present on drive C: (80h). Beginning normal boot. 

This message is seen when a Platform CD-ROM is present in the CD-ROM drive, as the Platform 

CD-ROM becomes drive C: (80h) when detected. 

If you do not receive the first prompt, check the following: 

• Have you disabled booting from the Diagnostic Partition To re-enable this feature, you must 

run the SCU from diskette or the Platform CD-ROM and enable the “Diagnostic Partition” 

option in the Management Subsystem Group. See the Server Software Guide (4SMP) for 

information about running the SCU and enabling the Diagnostic Partition. 

• Do you have the correct version of the system BIOS which supports the Diagnostic Partition 

See the Server Software Guide (4SMP) for information about upgrading your system BIOS. 

Problems with Application Software 

If you have problems with application software: 

• Verify that the software is properly configured for the system. Refer to the software 

installation and operation documentation for instructions on installing and using the software. 

• Try a different copy of the software to see if the problem is with the copy of the software you 

are using. 

• Try running the software in a different speed mode. 

• If other software runs correctly on the system, contact your software vendor to determine the 

reason for the software failure. 

If the problem persists, contact the software vendor’s customer service representative for 

assistance. 

BIOS Corrupted During System BIOS Upgrade 

If the BIOS is corrupted during a flash memory upgrade procedure (for example, due to a power 

failure or an inability to read the BIOS diskette which results in a fatal BIOS upgrade error), and 

the system cannot be booted at all, call your customer service representative. 


Appendix A 

Regulatory Statements and Warranty 

Safety Regulations 

The following safety certifications apply to rack mount systems: 

• UL 1950 

• CSA C22.2 No. 950-M95 

• EC Directive 73/23/EEC 

• EN60950 

• IEC 950 

Note: When installing an international modem that interfaces to the public telecommunications 

network, it is essential that it be certified by the authority having jurisdiction. 

WorldMark 4300 Rack Mount Product Guide A-1

EMI Emissions and Immunity 


Both conducted and radiated emissions meet the following requirements: 

• FCC (Federal Communications Commission) CFR Part 15 Class A 

• Industry Canada (IC) Radio Interference Regulations 22, amendment, dated September 15, 

1988 Class A 

• CISPR (International Special Committee on Radio Interference) Class A 

• VCCI (Voluntary Control Council for Interference) Class 1 

• EMC Directive 89/336/ EEC (European Economic Community) EN55022 Class A, EN50081- 

1, EN50082-1 

Disclaimer: NCR is not responsible for any radio or television interference caused by unauthorized 

modifications of this equipment or the substitution or attachment of connecting cables and 

equipment other than those specified by NCR. The correction of interference caused by such 

unauthorized modifications, substitution or attachment will be the responsibility of the user. 

United States of America 

This equipment has been tested and found to comply with the limits for a Class A digital 

device, pursuant to Part 15 of the FCC rules. These limits are designed to provide 

reasonable protection against harmful interference when the equipment is operated in a 

commercial environment. This equipment generates, uses, and can radiate radio frequency 

energy, and, if not installed and used in accordance with the instruction manual, may cause 

harmful interference to radio communications. Operation of this equipment in a residential 

area is likely to cause harmful interference in which case the user will be required to correct 

the interference at his own expense. 

CAUTION: Changes or modifications not expressly approved by NCR Corporation 

could void the user’s authority to operate this equipment. 

Japan 

Translation: This is a Class A product based on the standard of the Voluntary Control 

Council for Interference by Information Technology Equipment (VCCI). If this equipment is 

used in a domestic environment, radio disturbance may arise. When such trouble occurs, 

the user may be required to take corrective actions. 

A-2 Regulatory Statements and Warranty


Canada 

Le présent appareil numérique n'émet pas de bruits radioélectriques dépassant les limites 

applicables aux appareils numériques de la classe A prescrites dans le Règlement sur le 

brouillage radioélectrique édicté par le ministère des Communications du Canada. 

Translation: This digital apparatus does not exceed the Class A limits for radio noise 

emissions from digital apparatus set out in the Radio Interference Regulations of the 

Canadian Department of Communications. 

European Union 

In accordance with meeting the requirements of EMC 89/336/ EEC (as amended 92/31/ 

EEC), the rack mount system meets the EMI emissions and immunity standards of 

CENELEC (Committee for European Electrotechnical Standardization) EN55022-1, 

EN50081-1, EN50082-1 and IEC (International Electrotechnical Committee) IEC 1000-4-1, 

2, 3, 4. 

WARNING: This is a Class A product. In a domestic environment this product may 

cause radio interference in which case the user may be required to take adequate 

measures. 

WorldMark 4300 Rack Mount Product Guide A-3


A-4 Regulatory Statements and Warranty

Appendix B 

Telecommunications Platform 


The telecommunications platform is a two-rack configuration that contains a base rack and one of 

the following racks: 

• PortServer II/Catalyst 1900 rack 

• PortServer II rack 

CAUTION: Power cord cabling protocol is essential to the rack mount system. See the Hardware 

Installation Guide for the power cord cabling protocol for the telecommunications platform. 

The following table describes each rack configuration. 

Rack 

Configuration 


Illustration 

Base Rack • Monitor 

Figure B-1 

PortServer II / 

Catalyst 1900 Rack 

• Keyboard 

• Console switch (mounted at the rear of the rack) 

• Node chassis 

• 6250 disk array 

• UPS 

• Node chassis 


• UPS 

• Two Catalyst 1900 switches (mounted at the rear of the rack) 

• Two PortServer II units (mounted at the rear of the rack) 

Note: A PortServer II unit consists of one PortServer II and 

one PortServer II expansion module daisy-chained together. 

Figure B-2 

PortServer II Rack • Node chassis 

Figure B-3 


• UPS 

• Two PortServer II units (mounted at the rear of the rack) 

Note: A PortServer II unit consists of one PortServer II and 

one PortServer II expansion module daisy-chained together. 

WorldMark 4300 Rack Mount Product Guide B-1


Figure B-1. Telecommunications Platform Base Rack 

Monitor 

Console 

Switch 

Keyboard 

Keyboard 

Node 

Node 

6250 

UPS 

UPS 

Front 

Side 

B-2 Telecommunications Platform


Figure B-2. Telecommunications Platform PortServer II/Catalyst 1900 Rack 

Catalyst 

1900 

PortServer II Expansion Module 

PortServer II 

1U space 

1U 

1U 

1U 

2U 

2U 

7U space 


PortServer II 

2U 

2U 

1U space 

Node 

Node 

9U 

6250 

8U 

UPS 

UPS 

3U 

Front 

Side 



Figure B-3. Telecommunications Platform PortServer II Rack 

3U space 


PortServer II 

2U 

2U 

8U space 


PortServer II 

2U 

2U 

1U space 

Node 

Node 

9U 

6250 

8U 

UPS 

UPS 

3U 

Front 

Side 




The asynchronous PortServer II is a terminal and communications server for local and remote 

access on TCP/IP networks. Each PortServer II and PortServer II expansion module has 16 highspeed 

serial ports, for a total of 64 ports. 

The Catalyst 1900 100BaseTX switch is available only in the telecommunications platform. It is a 

stand-alone switch that provides Ethernet switching to 100BaseT networks. 

CAUTION: Other telecommunications equipment or modules (A/B switches, etc.) are not 

certified for use inside the rack. 

The following table shows the height and weight of the Catalyst 1900 and PortServer II 

communications modules. See Chapter 1 for the height, weight, and descriptions of the other 

modules. 

Module Height Est. Weight Comment 

PortServer II 2U 1 kg (2.25 lb) Mounts on rails at rear of rack. Empty space 

at front of rack covered by filler panel. 

PortServer II Expansion 

Module 

2U 1 kg (2.25 lb) Mounts on rails at rear of rack; daisy-chained 

to the PortServer II. Empty space at front of 

rack covered by filler panel. 

Catalyst 1900 Switch 1U 3.2 kg (7 lb) Mounts on rails at rear of rack. Empty space 

at front of rack covered by filler panel. 


Power On/Power Off 


PortServer II Racks 

When a platform does not contain a Catalyst 1900 switch, the rack and modules in a 

telecommunications platform rack should be powered on and off as described in Chapter 2, “Rack 

Power Management.” 

PortServer II/Catalyst 1900 Racks 

When a rack contains a Catalyst 1900, the rack should be powered on as described in Chapter 2, 

but the following order should be used: 

1. Catalyst 1900 

Note: Make sure that the Catalyst 1900 (if present) has successfully completed its power on 

self-test (POST) before powering on the other modules. 

2. PortServer II and attached expansion modules 

3. Console switch 

4. Monitor 

5. Disk arrays 

6. Nodes 

When powering off a rack that has a Catalyst 1900, power off all modules as described in Chapter 

2, then power off the Catalyst 1900. 

The Catalyst 1900 does not have a power switch. 

• To power on a Catalyst 1900, plug the appropriate end of the power cord into the Catalyst 

1900’s AC power inlet, and the other end into a UPS or AC box. 

• To power off a Catalyst 1900, remove its power cord from its AC power inlet. 

See Figure B-4 for the location of the Catalyst 1900’s AC power inlet. 



Figure B-4. Catalyst 1900 AC Power Inlet 

AC Power 

Inlet 

Powering Off Communications Modules Individually 

When powering off modules individually, communications modules (PortServer II and Catalyst 

1900) should be powered off after all other modules are powered off as described in Chapter 2, 

“Rack Power Management.” 

• Use the power switch on the front of the PortServer II to remove power from it and its attached 

expansion modules. 

• The Catalyst 1900 does not have a power switch. Power it off by removing the power cord 

from its AC power inlet. 




See the following publications for more information: 

• For information about installation of and power cord cabling of a telecommunications platform 

rack, see the Hardware Installation Guide. 

• For information about installing and configuring the communications modules in a 

telecommunications platform rack, see the HATP OSS/Adjunct R2 CIOP Installation and 

Configuration Guide, B018-0029-0000, and the documentation delivered with the Catalyst 

1900 and PortServer II modules. 


Index 

4 

40U rack See rack 

A 

AC box 

description 1-10 

height, weight 1-4 

power off 2-10 

power on 2-1 

AC power inlet, node chassis 4-4 

add-in boards 4-1, 4-7 

EISA slots 4-9 

PCI slots 4-9 

airflow 4-2 

auto-answer mode 

definition 6-9 

enabling 6-13 

B 

backplane, SCSI, SCA connectors 4-1 

battery backup See UPS 

beep codes 7-1 

BIOS 

corrupted 7-22 

upgrading 7-22 

BIOS security features 4-13 

BIOS Setup Utility 

inactivity timer 4-10 

boot path prompt, missing 7-22 

boot process 

boot order selection 2-17 

bootable devices in scan order 2-17 

booting to Diagnostic Partition 2-16 

booting to operating environment 2-16 

POST 2-15 

bus termination board 4-8 

C 

call-back password 

defining with the Diagnostic Partition 

menus 6-13 


call-through password 


menus 6-13 


Catalyst 1900 



in telecommunications platform B-5 

power off 2-13, B-6 

power on 2-9, B-6 

CD-ROM drive See removable media bays 

codes 

beep 7-1 

recovery port-80 and countdown 7-5 

standard port-80 and countdown 7-2 

Com1 4-3 

Com2 4-4 

computing node See node chassis 

configuration utilities 4-7 

configurations 

telecommunications platform B-1 

console redirection 


enabling with the BIOS Setup Utility 6-6 

enabling with the SCU 6-5 

enabling with UNIX MP-RAS 6-32 

key mapping 6-19 

limitations 6-7 

console switch 

configurations 3-1 

device settings 3-4 


in rack console 1-9 

keyboard/mouse reset 3-5 


Index-1

Index 

new node connection 3-4 

node selection 3-4 


power on 2-9 

security feature 3-5 

control panel board, node chassis 

identification of switches and LEDs 4-5 

controllers 

keyboard/mouse 4-10 

SCSI 4-10 

video 4-9 

cooling 

number of fans 4-2 

power supply fan 4-11 

countdown codes 

recovery 7-5 

standard 7-2 

D 

device scan order 2-17 

diagnostic and intra-chassis communication 4-2 

Diagnostic Partition 

booting to 2-16 

booting to, problems 7-22 

diagnostics 

when to run 7-16 

dialup telephone line 6-38 

disk arrays 

external (non-rack) 1-12 


power on 2-9 

rack mount models 1-12 

disk subsystem chassis 

height, weight (6210) 1-4 

height, weight (6250) 1-4 

height, weight (6282-1101) 1-4 

height, weight (6282-1103) 1-4 

height, weight (6285-1220) 1-4 

height, weight (6285-1440) 1-4 

downloading files 6-26 

E 

EIA rails 1-2 

EISA boards See add-in boards 

electrostatic discharge 5-2 

EMI A-2 

ESD warnings and cautions 5-2 

expansion slots 4-1, 4-4 

F 

fans 4-2 

file transfer 

configuration file 6-30 

downloading 6-26 

uploading 6-28 

filler panels 1-4 

flash memory 

BIOS 4-7 

flex drive See removable media bays 

ft.cfg file 6-30 

H 

hot keys 3-6 

I 

I2C circuit 4-2 

intrusion sensor 4-2, 4-12 

K 

keyboard 

compatibility 4-10 

connector 4-3 

hot keys 3-6 



keyboard drawer height, weight 1-4 

L 

LAN See local area network 

LanSafe software 2-25 

LCD 4-6 

local area network 6-38 

locking keyboard 4-10 

locking mouse 4-10 

LPT1 4-4 

M 

MCIU (multiple computer interface unit) See 

UPS 

memory 

board features 4-8 

maximum configuration 4-7 

Index-2 

WorldMark 4300 Rack Mount Product Guide

Index 

video 4-9 

modem 

configuring 6-11, 6-15 

configuring in UNIX MP-RAS 6-32 

configuring in Windows NT 6-38 

configuring with the Diagnostic Partition 

menus 6-9 

disabling password access 6-23 

displaying current passwords 6-35 

enabling remote support 6-12 

passwords 6-10 

security issues 6-9 

setting passwords, UNIX MP-RAS 6-33 

modem support 

for server management 4-16, 4-17 

Modem Utilities menu, accessing 6-12 

modules See rack modules. See rack modules 

monitor 

connector 4-4 



mouse 

compatibility 4-10 

connector 4-3 



N 

NCR Remote software package 6-1 

node chassis 

boot process 2-15 

components, front 4-5 

components, rear 4-3 

connectors, rear 4-3 

control panel LEDs 4-5 

DC power switch 2-14, 4-5 

device scan order 2-17 

features list 4-1 


orderly shutdown 2-26 

overview 1-9 

power fail recovery 2-25 


power on 2-9 

reset switch 4-5 

security 4-12 

shutdown time 2-25 

UPS battery backup 2-25 

O 


Oscar 3-4, 3-5 

P 

parallel port, node chassis 4-4 

password 

administrative 4-12 

remote 6-14 

system security 4-2 

system security, which to set 4-12 

user 4-12 

password 0 6-13 

passwords, modem 6-10 


menus 6-13 

disabling remote access 6-23 

setting in UNIX MP-RAS 6-33 

PCI boards See add-in boards 

PCI bus numbering 2-18 

PCI SCSI Configuration utility 7-14 

Platform CD-ROM 

no installation menu 7-21 

problems in booting from 7-21 

port-80 codes 

recovery 7-5 

standard 7-2 

PortServer II 



in telecommunications platform B-5 


power on 2-9 

PortServer II expansion module 


POST 2-15 

power 

failure and recovery 2-27 

monitoring 2-27 

power distribution backplane 



power off 

AC box 2-10 

Catalyst 1900 2-13, B-6 

console switch 2-12 

disk arrays 2-12 

node chassis 2-11 


Index-3

Index 

PortServer II 2-13 

rack 2-10 

sequence 2-10 

UPS 2-10 

power on 

AC box 2-1 

Catalyst 1900 2-9, B-6 


disk arrays 2-9 

node chassis 2-9 

PortServer II 2-9 

rack 2-1 

sequence 2-1 

UPS 2-1 

power on self test See POST 

power on/off 

controlling access to 2-14 

controlling with real-time clock 2-14 

controlling with server management 2-14 

node chassis power switch 2-14 

procedures per rack module 2-1 

warnings and cautions 5-2 

power requirements 1-11 

calculation of 2-26 

power source See AC box or UPS 

power supplies, node chassis 4-4, 4-11 

cooling fan 4-11 

current sensing 4-11 

installing 5-8 

number supported 4-1 

redundancy 4-1 

removing 5-8 

PowerMon software 2-25 

Power-On Self-Test (POST) 

beep codes 7-1 

error codes and messages 7-6 

testing phase codes 7-2 

problems 

remote diagnosing 6-38 

processor boards 


in system board set 4-7 

processors 


number supported 4-7 

R 

rack 

40U rack description 1-2 

configuration guidelines 1-5 

configurations 


typical 1-6 

modules, overview 1-9 

modules, specifications 1-4 

modules, types within rack 1-1, 1-3 

power See AC box or UPS 


power on 2-1 


rack console 1-5 

components 1-9 


keyboard/mouse 1-10 

monitor 1-10 

rack node chassis See node chassis 

remote password 6-14 

remote server management 

access methods 6-3 

configuring a modem 6-9 

console redirection 6-5 

disabling access 6-23 

modem support for 4-16, 4-17 

overview 6-1 

preparing the remote location for 6-17 

preparing the server for 6-4 

software 6-2 

terminal emulation, using NCR Remote 6-17 

terminal emulation, using other than NCR 

Remote 6-17 

transferring files 6-25 

verifying operation 6-21 

removable media bays 4-1 

location 4-6 

reset, node 7-10 

rf command 6-26 

S 

safety, product A-1 

SCA, definition of 4-1 

SCSI backplane 

hot-swappable drives 4-1 

SCA connectors 4-1 

SCSI bus 

controllers 4-10 

termination 4-10 

Index-4 


Index 

SCSI configuration utility 

for NCR PCI SCSI adapters (PQS) 7-14 

for onboard controllers 7-15 

SCSI drives 

controllers 4-7 


installation sequence 5-10 

installing or hot-swapping 5-10 

LEDs 4-6 

location 4-6 

secure mode 4-2, 4-12 

security 

BIOS security features 4-13 

console switch security features 3-5 

intrusion sensor 4-2 

locking mouse, keyboard with timer 4-10 

password protection 4-2 

secure mode 4-2, 4-12 

setting secure mode in SCU 4-12 

software lock in SCU 4-12 

using modems 6-9 

sensors, hardware 4-7 

serial ports, node chassis 4-3, 4-4 

server See node chassis 

server management 

functions 4-16 

hardware (SMB, SMM) 4-15 

remote power on/off 2-14 

software 4-15 

server management board See SMB 

Server Monitor Module (SMM) See SMM 


using for remote management 6-40 

service 

philosophy 5-1 

routine maintenance 5-1 

serviceable components 5-1 

warnings and cautions 5-2 

Setup Utility See BIOS Setup Utility 

sf command 6-28 

SMB 4-4 

components 5-4 

external modem, using 5-6 


installing board 5-5 

internal modem, installing 5-6 

internal modem, removing 5-6 

modem support 4-16 

removing board 5-5 

software 4-16 

using for remote management 6-39 

SMM See Server Monitor Module (SMM) 


modem support 4-17 

system board set 4-1, 4-7 

System Configuration Utility (SCU) 

software locking feature 4-12 

system server See node chassis 

system speed 

fast mode 3-6 

slow mode 3-6 

T 

tape drive See removable media bays 

telecommunications platform 

description B-1 

rack power on/off B-6 

timer, inactivity 

keyboard, mouse 4-10 

transferring files 6-25 

troubleshooting 

boot path prompt 7-22 

booting from hard drive 7-21 

booting from Platform CD-ROM 7-21 

characters on screen 7-18, 7-19 

checking for equipment failure 7-13 

incorrect beep codes 7-19 

monitoring POST 7-14 

mouse movement 7-19 

no activity light for diskette drive 7-20 

no activity light for hard drive 7-20 

no power light 7-18 

node boots, shuts down 7-18 

node reset 7-11 

preparing for diagnostic testing 7-14 

running software 7-12, 7-22 

video scanning 7-19 

U 

U (unit of vertical space in rack) 1-2 

uploading files 6-28 

UPS 

battery backup 2-25 

buttons 2-20 




Index-5

Index 

LEDs 2-20 




power on 2-1 

with MCIU 1-11 

utilities, configuration 4-7 

V 

VGA monitor See monitor or rack console 

video 

controller 4-7 

controller 4-9 

memory, amount of 4-7 

video memory 4-9 

Index-6

WorldMark 4300 Rack Mount Product Guide - NCR

Create successful ePaper yourself

Delete template?

Save as template?