World/Mark 4800/5200 and 4850/5250 Product Guide ... - NCR

WorldMark 4800/5200 

and 4850/5250 

Product Guide 

Release 1.4 

B035-5501-090A 

September, 2000

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

Adaptec and SCSISelect are registered trademarks of Adaptec, Inc. 

BYNET is an NCR trademark registered in the U.S. Patent and Trademark Office 

Digiboard is a registered trademark of Digi International, Inc. 

Ethernet is a trademark of Xerox Corporation 

IBM is a registered trademark of International Business Machines Corporation 

Intel is a registered trademark of Intel Corporation 

Pentium is a registered tradmark of Intel Corporation 

Teradata is a registered trademark of NCR International, Inc. 

UNIX is a registered trademark of the Open Group 

TCP/IP protocol is a United States Department of Defense Standard ARPANET protocol 

Windows and Windows NT are registered trademarks of Microsoft Corporation 

WorldMark is a trademark of NCR Corporation 

THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN “AS-IS” BASIS, WITHOUT WARRANTY OF ANY 

KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A 

PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED 

WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL NCR CORPORATION (NCR) BE 

LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR 

LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 

The information contained in this document may contain references or cross references to features, functions, products, 

or services that are not announced or available in your country. Such references do not imply that NCR intends to 

announce such features, functions, products, or services in your country. Please consult your local NCR representative 

for those features, functions, products, or services available in your country. 

Information contained in this document may contain technical inaccuracies or typographical errors. Information may 

be changed or updated without notice. NCR may also make improvements or changes in the products or services 

described in this information at any time without notice. 

To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, 

and value of this document. Please e-mail: info.products@SanDiegoCA.ncr.com 

or write: 

Information Engineering 

NCR Corporation 

17095 Via Del Campo 

San Diego, California 92127-1711 

U.S.A. 

Any comments or materials (collectively referred to as “Feedback”) sent to NCR will be deemed non-confidential. NCR 

will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, 

transform, create derivative works of and distribute the Feedback and derivative works thereof without limitation on 

a royalty-free basis. Further, NCR will be free to use any ideas, concepts, know-how or techniques contained in such 

Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services 

incorporating Feedback. 

Copyright © 1999, 2000 

By NCR Corporation 

Dayton, Ohio U.S.A. 

All Rights Reserved

About This Guide 

Who Should Read This Guide 

Releases Covered in This Guide 

The WorldMark 4800/5200 and 4850/5250 Product Guide is intended to provide an 

overview of the system for users, administrators, and field support personnel. 

This guide covers Release 1.4 of the WorldMark 4800/5200 and 4850/5250 

system platforms, using either NCR UNIX SVR4 MP-RAS Enterprise Operating 

Environment (EOE) Release 3.02.00 or later, Windows NT 4.0 Server Enterprise 

Edition (EE), or Windows 2000 Advanced Server version. 

Note: This user guide covers both the 4800/5200 and the 4850/5250 system 

platforms. Throughout this book, all references to the 4800 and 5200 also apply 

to the 4850 and 5250, respectively, unless otherwise specified. 

Note: Operating environments are supported as follows in the WorldMark 

48xx and 52xx system models: 

Model UNIX MP-RAS Windows NT Windows 2000 

4800/BYNET V1 Yes Yes No 

4850/BYNET V1 * Yes Yes No 

4850/BYNET V2 Yes No Yes 

5200/BYNET V2 Yes No No 

5250/BYNET V2 Yes No Yes ** 

* coexistence and migration 

** not applicable on 64+ node configuration 

What You Should Know 

This guide assumes that you understand the following: 

• Standard industry terminology 

• System networking protocol 

WorldMark 4800/5200 and 4850/5250 Product Guide 

i


How To Use This Guide 

Conventions Used in This Guide 

The purpose of this manual is to provide a general understanding of the 

WorldMark 48xx/52xx system architecture and operation. It includes the 

following information: 

• Overview of system hardware, software, and interfaces 

• Description of system rack configurations and cabling 

• Identification and definitions of subsystems 

• Product warranty, cautions, and warnings 

• Cabling diagrams 

This guide does not document procedures for the operation, administration, or 

service of the system or its individual components, nor does it cover use of 

application software. 

The following table describes the conventions used in this guide. 

This convention.... Is used for the following item or items: For example: 

Bold • Command names 

• Package names 

• Main menu bar 

• Run mktable. 

• Use PUT to upgrade the software. 

• Use the appropriate command in the Management 

menu. 

• Select from the File menu. 

Courier Screen output # Load the CD-ROM. 

Courier bold 

User input (text that you must 

enter exactly as shown) 

• Enter /usr/etc/ping from the command line. 

• Enter \winnt\system32\ping at the command 

line. 

Helvetica bold • Keyboard keys 

• Screen buttons 

• Field names 

Italic • Directory, file, and path names 

• 

• References to guides 

• Emphasis 

• Arguments 

• Command string variables 

• Environmental variables 

• Press the Esc key. 

• Click the Exit button on the dialog box. 

• Enter the system name in the System Name field. 

• The file is in the /user/sysadm/bin directory. 

• The file is in the \winnt\system32 directory. 

• See the Product Guide. 

• Do not delete this file. 

• shutdown -i -y -g 

• The variable must have at least 6 

characters. 

• The run_only_with_dual_ac environmental variable 

must be set to yes. 

ii 

WorldMark 4800/5200 and 4850/5250 Product Guide


This convention.... Is used for the following item or items: For example: 

Bulleted lists 

Numbered lists 

 

“Text in 

Quotation 

Marks” 

[Text in square 

brackets] 

Bulleted lists do not denote order; 

numbered lists denote specific 

order. 

Numbered lists denote specific 

order; bulleted lists do not denote 

order. 

• Variables in a command string 

• Required elements of 

command strings 

• Submenus 

• References to chapter and 

appendix titles 

• References to chapter and 

appendix headings. 

Optional elements 

• Floppy disk drive 

• Hard drive 

• CD-ROM drive 

1 Insert the CD-ROM into the CD-ROM drive. 

2 Double-click install.exe. 

• $ 

• To kill a process, enter exec kill from 

the command line, where is the process 

identification number. 

• Use the appropriate command in the Management 

menu. 

• Select from the File menu. 

• See Chapter 5, “Installation Overview.” 

• See “Shipping Weights” in Appendix A. 

ls [-a] [-F] 


iii


Related Information 

Related Information 

Related information about the WorldMark 48xx/52xx platform is available 

online and in additional guides and publications. 

Web Sites 

NCR customers may access online information through the following NCR 

web sites: 

http://www.info.ncr.com/ 

http://www.ncr.com/customer_svc/support.asp 

NCR Information Product Library of technical 

documentation and user guides 

NCR customer resource link for technical 

support, information products, and training 

programs 

Publications 

The most recent versions of the publications that support the WorldMark 

48xx/52xx platform are maintained on the documentation web site. The online 

versions of these books will be updated as necessary to reflect any changes 

introduced between product releases. 

Note: In the book numbers referenced below, the first eight characters are a 

unique Product ID for the book, and can be used to navigate to the book online. 

The mmyx, where used, represents the publication date, where mm is the 

month, y is the last digit of the year, and x is an internal code. The most recent 

versions of the books are maintained on the documentation web site. 

For supplementary server software and system hardware platform 

information, the following guides are available to NCR customers: 

B035-5501-mmyx 

B035-5502-mmyx 

B035-5503-mmyx 

B035-5504-mmyx 

B035-5515-mmyx 

B035-5519-mmyx 

B035-5517-mmyx 

BD20-0931-C 

WorldMark 4800/5200, and 4850/5250 Product Guide 

WorldMark 4800/5200, and 4850/5250 Site Preparation Guide 

WorldMark 4800/5200 and 4850/5250 Server Support Log 

WorldMark 4800/5200 and 4850/5250 Administration Workstation 

User Guide 

AWS on Windows NT User Guide 

AWS on Windows 2000 User Guide 

WorldMark 4800 and 4850 for Windows Console Switch Kit 

Instruction 

Customer Support Facility User’s Guide 

iv 


Contents 


Who Should Read This Guide ......................................................................................... i 

Releases Covered in This Guide...................................................................................... i 

What You Should Know................................................................................................... i 

How To Use This Guide ..................................................................................................ii 

Conventions Used in This Guide ...................................................................................ii 

Related Information ...........................................................................................................iv 

Web Sites...........................................................................................................................iv 

Publications ......................................................................................................................iv 

Chapter 1: 

System Overview 

System Architecture........................................................................................................ 1–2 

About the Platform....................................................................................................... 1–2 

About the Subsystems ................................................................................................. 1–2 

Processing Node ........................................................................................................ 1–2 

BYNET......................................................................................................................... 1–3 

Power...........................................................................................................................1–3 

Server Management and System Networking ...................................................... 1–3 

Disk Storage................................................................................................................ 1–3 

System Configurations ................................................................................................... 1–4 

48xx System Configurations / 1 to 4 Nodes............................................................. 1–5 

52xx System / 2 to 16 Nodes....................................................................................... 1–6 

52xx System / 18 to 64 Nodes..................................................................................... 1–7 

52xx System Beyond 64 Nodes................................................................................... 1–9 

Coexistence Systems .................................................................................................. 1–10 

Chapter 2: 

Systems Components 

Rack Specifications.......................................................................................................... 2–2 

40U Rack Frame............................................................................................................ 2–2 

Rack Chassis Placement............................................................................................... 2–3 

Rack Chassis ID Conventions..................................................................................... 2–5 

Processing and BYNET Cabinets .................................................................................. 2–6 


v

Contents 

48xx System / 1 to 4 Nodes......................................................................................... 2–6 

52xx System / 2 to 16 Nodes....................................................................................... 2–7 

52xx System / 18 to 64 Nodes..................................................................................... 2–8 

52xx System / 65-512 Nodes)...................................................................................... 2–9 

Storage Cabinets ............................................................................................................ 2–10 

6000 NSC and 6000 WES......................................................................................... 2–10 

627x Storage Cabinet............................................................................................... 2–11 

System Console.............................................................................................................. 2–12 

Network Hubs at AWS .............................................................................................. 2–12 

Dual AWS .................................................................................................................... 2–12 

Remote AWS ............................................................................................................... 2–12 

Software .......................................................................................................................... 2–14 

System-Level Software............................................................................................... 2–14 

Server-Level Software................................................................................................ 2–14 

System Platform Interfaces........................................................................................... 2–15 

SLAN ............................................................................................................................2–15 

PvtLAN ........................................................................................................................ 2–17 

MLAN .......................................................................................................................... 2–18 

External MLAN........................................................................................................ 2–18 

BYNET Network......................................................................................................... 2–19 

Cabinet Power............................................................................................................. 2–20 

SCSI............................................................................................................................... 2–20 

Teradata IBM Channel............................................................................................... 2–21 

Cable Management........................................................................................................ 2–22 

Chapter 3: 

Subsystems Features 

Service Subsystem (3U) .................................................................................................. 3–2 

3U Service Subsystem Components .......................................................................... 3–2 

Hardware.................................................................................................................... 3–2 

Firmware..................................................................................................................... 3–3 

BYNET Interconnect Subsystem ................................................................................... 3–6 

BYA4P Subsystem ........................................................................................................ 3–6 

BYA4G Subsystem........................................................................................................ 3–7 

BYA16G Subsystem...................................................................................................... 3–7 

BYA64GX and BYB64G Subsystems........................................................................ 3–10 

Processing Node Subsystem ........................................................................................ 3–14 

Node Components ..................................................................................................... 3–14 

Hardware.................................................................................................................. 3–14 

Software/Firmware................................................................................................. 3–16 

Power Subsystem .......................................................................................................... 3–20 

UIS Chassis .................................................................................................................. 3–20 

vi 


Contents 

UPS Chassis................................................................................................................. 3–21 

SLAN and PvtLAN Hardware .................................................................................... 3–25 

SLAN Hubs ................................................................................................................. 3–25 

10BaseT SLAN Hub at AWS .................................................................................. 3–25 

10Base2 SLAN Hub ................................................................................................. 3–26 

PvtLAN Hub ............................................................................................................... 3–27 

PvtLAN Switch ........................................................................................................... 3–28 

Chapter 4: 

System Management and Maintenance 

Initialization ..................................................................................................................... 4–2 

Power On/Off.................................................................................................................. 4–3 

Administration................................................................................................................. 4–4 

AWS on UNIX............................................................................................................... 4–4 

AWS on Windows ........................................................................................................ 4–6 

Logs ................................................................................................................................... 4–7 

Event Log.......................................................................................................................4–7 

Server Support Log ...................................................................................................... 4–7 

Appendix A: 

Product Statements 

Regulatory and Technical Compliance ....................................................................... A–2 

Safety ............................................................................................................................. A–2 

EMI Emissions and Immunity................................................................................... A–2 

Declaration of Conformity ...................................................................................... A–2 

Electromagnetic Compatibility............................................................................... A–4 

Electromagnetic Compatibility Notices ................................................................ A–4 

Disclaimer..................................................................................................................... A–5 

Cautions and Warnings................................................................................................. A–6 

Proper cooling and airflow ..................................................................................... A–6 

Grounding ................................................................................................................. A–6 

Rack Stabilization ..................................................................................................... A–6 

Power on/off............................................................................................................. A–6 

Hazardous electrical conditions ............................................................................. A–6 

Appendix B: 

Cabling Maps 

SLAN Cabling..................................................................................................................B–2 

PvtLAN Cabling ..............................................................................................................B–4 

MLAN ...............................................................................................................................B–6 


vii

Contents 

BYNET Network..............................................................................................................B–8 

Cabinet Power................................................................................................................B–14 

SCSI..................................................................................................................................B–16 

Index.........................................................................................................................Index –1 

viii 


List of Figures 

Figure 1-1 48xx System Configuration.................................................................... 1–5 

Figure 1-2 52xx System Configuration of 2 to 16 Nodes ...................................... 1–6 

Figure 1-3 52xx System Configuration of 18 to 64 nodes .................................... 1–8 

52xx System Expansion Pattern Beyond 64 Nodes *.......................... 1–9 

Figure 2-1 40U Rack Measurements ........................................................................ 2–2 

Figure 2-2 Rack Chassis Placement Pattern (cabinet side view) ......................... 2–4 

Figure 2-3 Subsystem Chassis IDs ........................................................................... 2–5 

Figure 2-4 Typical NCR Storage Cabinet .............................................................. 2–10 

Figure 2-5 Remote AWS Connections ................................................................... 2–13 

Figure 3-1 Service Subsystem Chassis Connectors and LEDs ............................. 3–4 

Figure 3-2 BYA4P Connectors .................................................................................. 3–6 

Figure 3-3 BYA16G Subsystem Chassis (rear view) ............................................. 3–9 

Figure 3-4 BYA64GX and BYB64G Subsystem Chassis 

Connectors and LEDs ........................................................................ 3–12 

Figure 3-5 Processing Node Chassis (rear view) 

Components and Connectors ........................................................... 3–17 

Figure 3-6 Processing Node Chassis (front view) 

Components, Controls, and LEDs.................................................... 3–18 

Figure 3-7 UIS Connectors and LEDs (rear view) ............................................... 3–20 

Figure 3-8 UPS Chassis (rear view) ....................................................................... 3–22 

Figure 3-9 UPS Front Panel LEDs .......................................................................... 3–23 

Figure 3-10 SLAN Hub Connectors and LEDs *.................................................... 3–26 

Figure 3-11 PvtLAN Hub Connectors and LEDs *................................................ 3–27 

Figure 3-12 PvtLAN Switch Connectors and LEDs *............................................ 3–28 

Figure B-1 SLAN: 1 to 4 Nodes, and 2 to 16 Nodes ...............................................B–2 

Figure B-2 SLAN: 18 to 64 Nodes.............................................................................B–3 

Figure B-3 PvtLAN: 3 Nodes and 16 Nodes ...........................................................B–4 

Figure B-4 PvtLAN: 64 Nodes ..................................................................................B–5 

Figure B-5 MLAN: Processing Rack.........................................................................B–6 

Figure B-6 MLAN: BYNET Rack ..............................................................................B–7 

Figure B-7 BYNET to Node Connections: 

BYA4P Network to 4 Nodes................................................................B–8 


BYA4G Network to 4 Nodes ...............................................................B–9 


BYA16GX Network to 16 Nodes ......................................................B–10 


BYA64GX Network to 64 Nodes ......................................................B–11 


ix

List of Figures 

Figure B-11 

Figure B-12 

Figure B-13 

Figure B-14 

Figure B-15 

Figure B-16 

BYA64GX to BYB64G Connections: 

Expansion Port Cabling per BYNET Network 

(Sample 65-128 Node System) *........................................................B–12 

BYA64GX to BYB64G Connections: 

Clock Cabling per BYNET Network 

(Sample 65-128 Node System) ..........................................................B–13 

Power: Processing Rack........................................................................B–14 

Power: BYNET Rack..............................................................................B–15 

Shared SCSI: 4-Node Clique 

with NCR Storage Cabinet (NSC) ....................................................B–16 

Point-to-Point SCSI: 4-Node Clique 

with WorldMark Enterprise Storage (WES) ...................................B–17 

x 


Chapter 1: 

System Overview 

This chapter provides the following introductory information about the 

4800/5200 and 4850/5250 platform systems: 

• System Architecture 

• System Configurations 

WorldMark 4800/5200 and 4850/5250 Product Guide 1 – 1

Chapter 1: System Overview 

System Architecture 


About the Platform 

About the Subsystems 

The NCR WorldMark 4800/5200 and 4850/5250 products are Massively 

Parallel Processing (MPP) platforms for Teradata Warehouse applications. The 

platform offers two levels of scalability: 

• The WorldMark 4800 and 4850 series systems are designed for data 

warehouses of 50 GB to 1 Terabyte (TB), with scalability from 1 to a 

maximum of 4 processing nodes. 

• The WorldMark 5200 and 5250 series systems can support data warehouses 

from 250 GB to 100+ TB, and offers system expansion from 2 to 512 

processing nodes. 

The WorldMark 4800/5200 and 4850/5250 

systems use industry standard rack mount 

architecture. It consists of individual 

subsystem chassis that are housed in standard 

rack frames. Subsystems are self-contained, 

and their configurations -- either internal or 

within a system -- are redundant. The design 

ensures overall system reliability, enhances its 

serviceability, and enables time and costefficient 

upgrades. 

Following are the types of subsystems that can make up WorldMark 4800/5200 

and 4850/5250 systems: 

• Symmetrical multi-processing (SMP) nodes 

• BYNET interconnect 

• Uninterruptible power supplies (UPS) and UPS input selectors 

• Server management 

• Disk storage 

Processing Node 

SMP nodes are housed in processing racks, typically two Teradata nodes per 

rack. There is also a minimum single-node rack configuration housing one non- 

Teradata node, referred to as a non-TPA (trusted parallel applications) node. 

1 – 2 




BYNET 

The nodes communicate with each other through the BYNET interconnect 

network. Depending on the overall system size, the BYNET network switch 

may be located in one of the processing racks in a system, or it may be housed 

in its own BYNET rack. In either case, the BYNET switch is always paired in the 

system for redundancy. 

Power 

Multiple UPS chassis per rack support dual AC power sources. The redundant 

power sources feed into UPS input selectors (UIS), one on each UPS chassis. 

The input selectors choose the power source and direct it to their respective 

UPS chassis. The UPS chassis then distribute the AC power to all other chassis 

within the rack. All subsystem chassis are designed with multiple power inlets. 

Server Management and System Networking 

Each rack contains a service subsystem that monitors and controls all the 

chassis in its rack. The service subsystem chassis is connected to each chassis 

within its rack through a Management Local Area Network (MLAN). 

Service subsystems across multiple racks are connected over the System Local 

Area Network (SLAN). The SLAN interfaces all the racks with the 

Administration Workstation (AWS) for a single operational view of the 

complete system. The BYNET subsystems are also included in the SLAN for 

administration and control of the BYNET switching network. SLAN hubs are 

used in larger network environments to facilitate the rack-to-rack connections. 

SMP nodes have a connection to the AWS over a Private Local Area Network 

(PvtLAN) for TCP/IP login capability. PvtLAN hub and switch hardware is 

used in the system racks to provide for consistent cabling protocol, from small 

to expansion systems. 

Disk Storage 

In association with this system architecture, processing nodes are connected to 

disk storage devices in “cliques,” where as many as four nodes share a disk 

array. The type of disk array determines how it is connected to the system 

platform. The NCR storage cabinet (NSC) and the WorldMark enterprise 

storage (WES) present disk arrays in a rack that includes a service subsystem 

chassis to link the disk cabinet to the platform. The NSC and the WES models 

link via an external MLAN to a controlling service subsystem in a processing 

rack. The 627x models are interfaced through SCSI connection software for 

minimal administrative functions. 

In addition, a channel interface capability is available for node-to-mainframe 

connections. 



System Configurations 


Following is a summary of the available 48xx/52xx system configurations: 

Model 

4800 

1 to 4 nodes 


1 to 4 nodes 


1 to 4 nodes 

(coexistence and 

migration) 


2 to 16 nodes 


2 to 16 nodes 


18 to 64 nodes 


18 to 64 nodes 


64+ nodes 


64+ nodes 

Features 

450 - 550 MHz 

BYNET version 1 (BYA4P switch board) 

UNIX or Windows NT 

700 MHz 

BYNET version 2 (BYA4G switch board) 

UNIX or Windows 2000 

700 MHz 

BYNET version 1 (BYA4P switch board) 

UNIX or Windows NT 

450 - 550 MHz 

BYNET version 2 (BYA16G switch chassis) 

UNIX 

700 MHz 

BYNET version 2 (BYA16G switch chassis) 


450 - 550 MHz 

BYNET version 2 (BYA64GX switch cabinet) 

UNIX 

700 MHz 

BYNET version 2 (BYA64GX switch cabinet) 


450 - 550 MHz 

BYNET version 2 (BYA64/BYB64 switch cabinet) 

UNIX 

700 MHz 

BYNET version 2 (BYA64/BYB64 switch cabinet) 

UNIX 

1 – 4 


48xx System Configurations / 1 to 4 Nodes 



The WorldMark 4800 and 4850 series systems have one to four SMP nodes. 

Figure 1-1 illustrates the maximum 4-node configuration of processing racks. 

Figure 1-1 

48xx System Configuration 

Base 

Cabinet 

Service 

Subsystem 

Expansion 

Cabinet 

Service 

Subsystem 

PvtLAN Hub 

BYA Switch 

SLAN Hub 

Node 

Node 

AWS 

PvtLAN Hub 

BYA Switch 

Node 

Node 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

The 48xx system is anchored by a base cabinet (also referred to as the system 

cabinet). The base cabinet houses a BYNET switch board (BYA4P or BYA4G 

depending on model) in each of two SMP Teradata nodes. The BYA switch 

board can interconnect as many as four nodes. The dual switches provide for a 

redundant BYNET network. A BYNET adapter (BIC2G or BIC2C, depending 

on model) is contained in every node in the system. The multi-ported adapter 

provides for node connection to both BYNET switches. 

The expansion cabinet is the add-on rack, with two SMP Teradata nodes 

connecting to the BYNET switches in the base rack. The expansion cabinet also 

contains a PvtLAN hub, which is used to connect all four node chassis in the 

system to the system console for TCP/IP login capability. 

A single node cabinet is an option for a one or three-node 4800 or 4850 system 

configuration. The 48xx single node cabinet contains one SMP node and no 

PvtLAN hub. 




52xx System / 2 to 16 Nodes 

All cabinet variations are configured with 3 UPS/UIS chassis at the bottom of 

the rack and a service subsystem chassis at the top. 

All 48xx system configurations include an AWS with two network hubs, one 

for the PvtLAN and one for the SLAN. The PvtLAN hub funnels multiple node 

Ethernet connections into a single connection at the console. The SLAN hub 

converts a 10Base2 coaxial connection from the rack cabinets to a 10BaseT 

twisted pair Ethernet connection at the console. 

Note: Earlier AWS models use an internal coaxial adapter for the SLAN 

connection, instead of the external SLAN hub. 

The WorldMark 5200 and 5250 system configuration of 2 to 16 nodes is 

illustrated in Figure 1-2. 

Figure 1-2 

52xx System Configuration of 2 to 16 Nodes 

Expansion Cabinet (7x) 

Base 

Cabinet 

Service 

Subsystem 

BYA16G 

Service 

Subsystem 

PvtLAN Hub 

BYA16G 

SLAN Hub 

Node 

Node 

AWS 

PvtLAN Hub 

Node 

Node 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

1 – 6 





The dual-node base cabinet houses two BYA16G switch chassis that support a 

maximum of 16 Teradata nodes in redundant networks. Each SMP node in the 

system contains a multi-ported BYNET adapter (BIC4G) for connection to both 

BYNET chassis. 

The expansion cabinet is an add-on rack with two Teradata nodes that connect to 

the BYNET chassis in the base rack. The expansion cabinet also contains a 

PvtLAN hub, which is used to connect the node chassis in the cabinet to the 

system console. 

A single node cabinet is an option for an odd-numbered configuration of 52xx 

nodes beyond the initial dual node base cabinet. The 52xx single node cabinet 

contains one non-TPA node (no Teradata) as well as a PvtLAN hub. 

All cabinet variations are configured with 3 UPS/UIS chassis at the bottom of 

the rack, and a service subsystem chassis at the top. 

All 52xx system configurations up to 16 nodes include an AWS with two 

network hubs, one for the PvtLAN and one for the SLAN. The PvtLAN hub 

funnels multiple node Ethernet connections into a single connection at the 

console.The SLAN hub converts a 10Base2 coaxial connection from the rack 

cabinets to a 10BaseT twisted pair Ethernet connection at the console. 



The WorldMark 5200 and 5250 system of 18 to 64 nodes consists of a 

combination of processing and BYNET racks, as shown in 

Figure 1-3. 

The BYA64GX switch cabinet is the anchor rack of this large system model. It 

contains a single BYA64 chassis that can interconnect a maximum of 64 

Teradata nodes. A second BYA64 cabinet is included in the system to provide a 

redundant BYNET network. Every node in the system contains a multi-ported 

BYNET adapter (BIC4G), providing connection to both 64-node switches. 

The BYA64GX cabinet also houses the PvtLAN switch and the SLAN hub. The 

PvtLAN switch consolidates the PvtLAN hub connections of node cabinets in 

groups, and links them to the AWS console. The SLAN hub in the BYNET 

cabinet repeats the SLAN connection from the AWS console to groups of node 

cabinets. 

The node expansion cabinet is the system building block, with two Teradata 

nodes per cabinet connecting to each of the BYA64 chassis in the system. The 

expansion cabinet also contains a PvtLAN hub which is used to connect the 

node chassis in the cabinet with the PvtLAN switch in the BYNET cabinet. 

A single node cabinet is an option for an odd-numbered configuration of 52xx 

nodes. The 52xx single node cabinet contains one non-TPA node (no Teradata) 

as well as a PvtLAN hub. 




Figure 1-3 

52xx System Configuration of 18 to 64 nodes 

Expansion Cabinet (32x) 

BYA64 Cabinet (2x) 

Service 

Subsystem 

SLAN Hub 

Service 

Subsystem 

PvtLAN Hub 

PvtLAN Switch 

SLAN Hub 

BYA64GX 

Node 

AWS 

Node 

UPS 

UPS 

UPS 

UPS 

UPS 

The BYNET rack contains only two UPS/UIS chassis; the processing rack uses 

three. All cabinets contain a service subsystem chassis at the top of the rack. 

All 52xx system configurations from 18 to 64 nodes include an AWS with a 

network hub for the SLAN. The SLAN hub converts a 10Base2 coaxial 

connection from the rack cabinets to a 10BaseT twisted pair Ethernet 

connection at the console. 



1 – 8 


52xx System Beyond 64 Nodes 

52xx System Expansion Pattern Beyond 64 Nodes * 



The WorldMark 5200 and 5250 systems can be expanded beyond 64 nodes with 

the addition of BYNET racks. shows the general expansion pattern. 

65 to 128 

Nodes 

to 192 

Nodes 

to 256 

Nodes 

Pattern 

Repeats 

every 64 Nodes 

Up to 512 Nodes 

Service 

Subsystem 

PvtLAN Hub 

Service 

Subsystem 

PvtLAN Hub 

Service 

Subsystem 

PvtLAN Hub 

Service 

Subsystem 

PvtLAN Hub 

Node 

Node 

Node 

Node 

Node 

Node 

Node 

Node 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

Expansion 

Cabinet (32x) 

Expansion 

Cabinet (32x) 

Expansion 

Cabinet (32x) 

Expansion 

Cabinet (32x) 

Service 

Subsystem 

SLAN Hub 

Service 

Subsystem 

Service 

Subsystem 

SLAN Hub 

Service 

Subsystem 

SLAN Hub 

PvtLAN Switch 

PvtLAN Switch 

PvtLAN Switch 

BYA64GX 

BYA64GX 

BYA64GX 

BYB64G 

BYB64G 

BYB64G 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

UPS 

BYA64 

Cabinet (2x) 

BYB64 

Cabinet (2x) 

BYA/BYB64 

Cabinet (2X) 

BYA/BYB64 

Cabinet (2X) 

The BYB64G switch cabinet is the upgrade rack for the initial BYA64GX cabinet. 

The BYB64G switch allows the BYA64GX chassis to communicate with 

additional BYA64GX chassis as the BYNET network grows to support nodes 

beyond 64 in number. The BYB64G is designed to interconnect as many as eight 

BYA64GX chassis. 

The BYA64/BYB64 switch cabinet is an extender rack. It houses both BYA64GX 

and BYB64G chassis types, thus allowing the system to grow by up to 64 nodes 

for each BYA/BYB cabinet introduced. Like the single BYA64GX switch cabinet, 

the BYA/BYB cabinet also contains a PvtLAN switch and a 10Base2 SLAN hub. 

Note: An initial system ordered with greater than 64 nodes will use only the 

BYA64/BYB64 cabinet configuration, rather than the upgrade configuration of 

a BYA64 cabinet and a BYB64 cabinet. 

All BYNET cabinets have two UPS/UIS chassis at the bottom of the rack, and a 

service subsystem chassis at the top. 




Coexistence Systems 

The following WorldMark platforms (UNIX-based only) can coexist as a single 

MPP platform: 

• 4800 and 4700/5150 

• 4800 and 4850 

• 4850 and 4700/5150 

• 5200 and 5250 

In a coexistence system, all processing nodes in each platform are connected as 

one system through the same BYNET infrastructure (either version 1 or 

version 2 as applicable to the platforms involved). All of the nodes can be 

administered through the single operational view of the AWS. 

For more information about WorldMark product coexistence configurations, 

talk to your NCR representative. 

1 – 10 


Chapter 2: 

Systems Components 

This chapter provides the following information about the components of the 

48xx/52xx systems: 

• Rack Specifications 

• Processing and BYNET Cabinets 

• Storage Cabinets 

• System Console 

• Software 

• System Platform Interfaces 

• Cable Management 


Chapter 2: Systems Components 

Rack Specifications 


40U Rack Frame 

All system cabinets use a standard rack frame, referred to as a 40U rack. “U” 

represents a unit of vertical measurement for placement of chassis 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 

Each chassis occupies a specific number of U spaces in the rack. The U spaces 

are labeled on the four EIA rails of the rack frame. Also, notches in the EIA rail 

delineate each U. The U spaces are numbered from bottom to top in the rack. 

Figure 2-1 

40U Rack Measurements 

The following figure illustrates the measurements of the standard rack 

assembly: 

61 cm 

24 in. 

101.6 cm 

40 in. 

45.1 cm 

17.75 in. 

1U = 

4.445 cm 

1.75 in. 

EIA 

Rails 

195.6 cm 

77 in. 

Stabilizer 

Feet 

Front 

Side 

2 – 2 


Rack Chassis Placement 



The 40U rack has the following features and specifications: 

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

• Usable height: 40U 

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

• Usable width: 45.1 cm (17.75 in.) 

• Total rack frame depth: 101.6 cm (40 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 front and rear doors 

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

Each chassis has a standard placement in the rack. The SMP node chassis are 

mounted in the rack on extendible rails, allowing the node chassis to be 

extended from the rack for servicing access. All other chassis are installed on 

fixed mounts. 

Note that the chassis are installed from the front of the rack, with the exception 

of the UPS input selectors and Ethernet hub and switch hardware, which load 

from the rear of the rack. 

Figure 2-2 illustrates the placement pattern of the various chassis types in 

processing and BYNET rack frames, as viewed from the right side of the 

cabinet. 




Figure 2-2 

Rack Chassis Placement Pattern (cabinet side view) 

Service Subsystem Chassis (3U) BYA16X Chassis (3U) SMP Node Chassis (11U) 

UPS Chassis (3U) UPS Input Selector (3U) PvtLAN Hub (1U) 

SLAN Hub (1U) 

PvtLAN Switch (2U) 

BYA64GX Chassis (12U) 

BYB64G Chassis (12U) 

2 – 4 




Rack Chassis ID Conventions 

Subsystem chassis have assigned positions in a cabinet. Each position is 

identified by a number. The following figure is a general representation of a 

processing and a BYNET cabinet, identifying the chassis ID for each subsystem 

that may reside in that cabinet type. 

Figure 2-3 

Subsystem Chassis IDs 

Note that the chassis number does not change, relative to the presence or 

absence of other chassis in the rack. Also note that the PvtLAN and SLAN hub 

and switch hardware components within the cabinets are not identified by 

chassis numbers, since those units are not defined as subsystems within the 

cabinet. 

Processing 

Cabinet 

Service Subsystem 

Chassis #1 

BYA16G 

Chassis #2 

BYA16G 

Chassis #3 

BYNET 

Cabinet 

Service Subsystem 

Chassis #1 

SMP Node 

Chassis #4 

BYA64GX 

Subsystem 

Chassis #2 

SMP Node 

Chassis #5 

UPS/UIS 

Chassis #6 

UPS/UIS 

Chassis #7 

UPS/UIS 

Chassis #8 

BYB64G 

Subsystem 

Chassis #3 

UPS/UIS 

Chassis #4 

UPS/UIS 

Chassis #5 



Processing and BYNET Cabinets 



The WorldMark 48xx series system is built on three processing rack variations, 

as shown below. See “System Configurations” in Chapter 1 for an overview of 

the 1 to 4 node configuration. 

48xx System Base Cabinet 

1 service subsystem 

2 SMP nodes (4800 or 4850) 


- 450 - 550 MHz processors 

- BYA4P switch board 

- BIC2G adapter 


- 700 MHz processors 

- BYA4G switch board 

- BIC2C adapter 

3 UPS and UIS 

48xx System Expansion Cabinet 


1 PvtLAN hub 











48xx Single Node Cabinet 


1 SMP node (4800 or 4850) 










2 – 6 





The WorldMark 52xx system of 2 to 16 nodes has three processing rack 

variations, as shown below. See “System Configurations” in Chapter 1 for an 

overview of the 2 to 16 node configuration. 

52xx System / 2 to 16 Node 

Base Cabinet 


2 BYA16GX subsystems 











1 PvtLAN hub 









52xx Non-TPA 

Single Node Cabinet 


1 PvtLAN hub 

1 non-TPA (trusted parallel 

applications) SMP node 

(5200 or 5250) 












The WorldMark 5200 system of 18 to 64 nodes consists of a combination of 

processing and BYNET racks, as shown below. See “System Configurations” in 

Chapter 1 for an overview of the 18 to 64 node configuration. 



1 PvtLAN hub 









52xx Non-TPA 

Single Node Cabinet 


1 PvtLAN hub 

1 non-TPA (trusted parallel 

applications) SMP node 

(5200 or 5250) 








BYA64 Cabinet 


1 SLAN hub 

1 PvtLAN switch 

1 BYA64GX subsystem 


2 – 8 




52xx System / 65-512 Nodes) 

The WorldMark 52xx system can be expanded beyond 64 nodes with the 

addition of BYNET racks to support more expansion racks, as shown below. 

See “System Configurations” in Chapter 1 for an overview of the 65 to 512 

node configuration. 

52xx System Expansion 

Cabinet 


1 PvtLAN hub 









BYB64 Cabinet 


1 BYB64G subsystem 


BYA64/BYB64 Cabinet 


1 SLAN hub 

1 PvtLAN switch 

1 BYA64GX subsystem 

1 BYB64G subsystem 




Storage Cabinets 


The WorldMark 48xx/52xx system uses one of the following brands of storage 

cabinet for external storage of processing data: 

• 6000 NCR storage cabinet (NSC) 

• 6000 WorldMark enterprise storage (WES) 

• 627x storage cabinet 

Note: Operating environment and applications programs are stored on the 

internal disk drives in the individual processing nodes. 

6000 NSC and 6000 WES 

Figure 2-4 is an example of a 6000 storage cabinet. Both the NSC and the WES 

have the same cabinet architecture. The cabinet contains a 2U service 

subsystem chassis at the top of the rack. It is connected to and controlled by the 

3U service subsystem in a processing rack, affording full AWS control of the 

storage cabinet. The NSC and WES models also contains two UPS/UIS chassis 

at the bottom of the rack. 

Figure 2-4 

Typical NCR Storage Cabinet 

UPS 

UPS 

2 – 10 




The 6000 NSC houses disk array subsystems in the following supported 

configurations: 

• 6285-1220 disk arrays: 1 to 3 per NSC 

• 6285-1440 disk arrays: 1 or 2 per NSC 

The 6000 WES houses disk array subsystems in the following supported 

configurations: 

• 6288-1440 disk arrays: 1 to 2 per WES 

627x Storage Cabinet 

The 627x cabinet does not have a physical connection to the system except 

through SCSI cabling from the 627x disk arrays to SMP nodes in the processing 

racks. The 627x has its own cabinet protocol with a dedicated console for its 

own control. 

The 627x storage cabinet houses the following types of disk array subsystems: 

• 6273 

• 6274 

• 6276 

• 6277 

• 6278-2000 

• 6278-3000 

For complete information, see the product documentation for your disk array. 



System Console 


Network Hubs at AWS 

Dual AWS 

Remote AWS 

The Administration Workstation (AWS) is an NCR deskside computer. It serves 

as the WorldMark MPP systems console, providing a single operational view in 

a large systems environment. 

Two AWS configurations are available, one for MPP systems of 1 to 12 nodes, 

the second for MPP systems of 12+ nodes. 

For specific information on the server used as the AWS, see the NCR user guide 

which is provided with the product. 

The AWS is packaged with two 8-port Ethernet hubs, one for the Private LAN 

(PvtLAN) and one for the System LAN (SLAN). 

• The PvtLAN hub at the AWS is used in system configurations of 16 nodes 

or less. It funnels multiple node connections into a single connection to the 

console. 

• The SLAN hub converts a 10Base2 coaxial connection from the rack 

cabinets to a 10BaseT twisted pair Ethernet connection at the console. 



For more information on system networks, see “System Platform Interfaces” 

later in this chapter. 

In the UNIX operating environment, a redundant AWS, referred to as “dual 

AWS,” is an available option. It provides a redundant system console 

connection to the platform. Both consoles are totally independent, each having 

full stand-alone functionality. 

Enabling software allows the two consoles to operate on the same System LAN 

(SLAN) simultaneously for all unrestricted functions. Security lockout software 

allows only one AWS at a time to execute security function operations. 

In the hardware configuration for a second AWS, the Private LAN (PvtLAN) 

and the SLAN extend to and terminate at the second AWS. 

A single AWS can be extended for multiple operators and administrators by 

adding Administration Stations (AS). The AS is an X terminal that connects to 

the AWS to gain management functions. Up to five Administration Stations can 

be supported by an AWS. 

2 – 12 




The AS can connect to the AWS locally via Ethernet or remotely through a 

modem. When the AS connects to the AWS from a remote location, the AWS 

must support the X-Remote protocol. 

Figure 2-5 depicts the remote AWS interface. 

Figure 2-5 

Remote AWS Connections 

SLAN 

AWS 

Console 

PvtLAN 

(Private LAN) 

Administration 

Stations (AS) 



Software 

Software 

System-Level Software 

Server-Level Software 

The WorldMark 48xx/52xx platform requires the following system-level 

operating software: 

• Operating system: 

– NCR UNIX SVR4 MP-RAS Enterprise Operating Environment (EOE), 

release 3.02 (with platform-required compatibility update and patches), 

available for 4800, 5200, 4850, and 5250 

– Windows NT 4.0 Server Enterprise Edition (EE), available on 4800 and 

4850 with BYNET version 1 (coexistence and migration model only) 

– Windows 2000 Advanced Server, available on 4850 and 5250 

• Teradata Warehouse 6.0 

• Supporting packages and patches for both the AWS and processing nodes 

The system software is installed before shipment. Operating system software is 

also delivered in CD-ROM media. The three-piece CD set includes the 

following: 

• Core CD 

• Packages CD 

• Documentation CD 

You can list software installed on the system as follows: 

• On UNIX: To list all software, run the pkginfo utility (pkginfo -x). To list 

the contents of a single package, use the command pkginfo -l . 

• On Windows: To list software packages that loaded via Install Shield, access 

the . 

A platform CD-ROM is provided with the WorldMark 48xx/52xx system. It 

contains the software utilities that are pre-loaded in the Diagnostic Partition, a 

DOS partition on each node’s boot disk. 

Server software includes node-enabling components such as Power On Self 

Test (POST), BIOS Setup Utility, System Setup Utility (SSU), BIOS flash utility, 

SCSI configuration utilities and others. The CD is bootable (no flex required) 

with utilities executable directly off of the CD. 

For information on these software utilities, see the Server Software Guide. 

For information on other specific subsystem level software that runs on nodes 

in an MPP environment, see Chapter 3 in this guide. 

2 – 14 



System Platform Interfaces 


The WorldMark 48xx/52xx system uses the following interfaces to accomplish 

communications among the system platform components. 

This interface… 

System LAN (SLAN) 

Private LAN (PvtLAN) 

Management LAN 

(MLAN) 

External MLAN 

BYNET Network 

Cabinet Power 

Small Computer Systems 

Interface (SCSI) 

Teradata IBM Channel 

Connects these components… 

Processing cabinets, BYNETs, and NCR 

storage cabinets to AWS 

AWS to processing nodes 

Service subsystem to each chassis within its 

own rack 

2U service subsystem in NCR storage 

cabinet to 3U service subsystem in 

processing cabinet (“collective”) 

BYNET to each processing node chassis, 

and BYNET to BYNET chassis 

UPS/UIS to each chassis within a rack 

Processing nodes to disk arrays 

Processing nodes to IBM (or compatible) 

mainframes 

Note: These interfaces are specific to the networking requirements of the 

WorldMark 48xx/52xx system hardware platform. A complete line of interface 

offerings are available for the varied networking requirements of the user site. 

SLAN 

The SLAN is a private network for the system. It is a coaxial (10Base2) Ethernet 

LAN that interconnects all processing and BYNET cabinets and the AWS. It 

uses the following hardware: 

• 8-port 10BaseT hub at the AWS 

Note: Earlier AWS models do not use this 10BaseT hub for the SLAN 

connection. They have an internal 10Base2 adapter to handle the SLAN 

connection directly. 

• 4-port 10Base2 hub in each BYA64 cabinet and each BYA64/BYB64 cabinet 




The following table outlines the SLAN connections, based upon system 

configuration. 

Note that for systems that do not have the 10Base2 SLAN hub (no BYNET 

cabinet in the configuration), the SLAN consists of a single segment, or 

sequence of connections terminated at either end. The larger systems with the 

4-port 10Base2 SLAN hub have multiple segments, each port representing a 

segment, with a maximum of 30 connections per segment. 

System Configuration 

4 nodes or less, using 

BYA4P switch boards 


BYA16 chassis 


BYA64GX chassis 

SLAN Cabling 

Starting at the AWS*, the SLAN connects to the 10BaseT 

SLAN hub**, then to the service subsystem in the expansion 

cabinet, then to the service subsystem in the system cabinet, 

terminating at that chassis. 

See Appendix B, Figure B-1. 


SLAN hub**, then to the service subsystem chassis in each 

cabinet in sequence, from expansion cabinets to the system 

cabinet. At the system cabinet, the SLAN connection 

continues from the service subsystem to each of the two 

BYA16G chassis, terminating at the lower BYNET. 



SLAN hub**, then to the AUI port of the 10Base2 SLAN hub 

in each BYA64GX cabinet in sequence. This is the primary 

segment of the SLAN. 

Ports 1, 2, and 3 are the start of separate segments of the 

SLAN, each connecting to a group of expansion cabinets, 

which are daisy-chained together through service 

subsystem connections. 

Port 4 of each SLAN hub connects to the service subsystem 

chassis in its respective BYNET rack, creating an internal 

segment. 


* In a dual AWS configuration, the segment starts at the second AWS and continues to 

the first AWS, then to the racks. 

** On earlier AWS models, the SLAN connects directly to an internal 10Base2 adapter. 

There is no 10BaseT SLAN hub in the configuration. 

2 – 16 




The SLAN must be operational for system bringup. It carries the “heartbeats,” 

system events, and AWS commands. A heartbeat is a broadcast message that 

goes out from the service subsystem -- specifically, its Cabinet Module Interface 

Controller (CMIC2) -- to the AWS to inform the AWS of its presence. 

When a new CMIC2 joins the SLAN (as in the addition of an expansion rack), it 

starts heartbeating. The AWS reads the message and updates its view of the 

system configuration. If the CMIC2 stops running, or “heartbeating,” an AWS 

event is generated to report the lost heartbeat. 

A CMIC2 broadcasts all events relating to its rack cabinet. An event is 

generated when the CMIC2 detects an environmental change in any subsystem 

within its rack. Rack subsystems forward event messages to the CMIC2 over 

the MLAN, and the CMIC2 broadcasts the events on the SLAN. 

Once the system has booted, the SLAN is not critical to continued operation. 

The SLAN is not a fault-tolerant network. Any break in the network causes a 

failure along the entire network. However, the SLAN is not used for any 

system-critical functions during operation. It is primarily a mechanism for 

passing messages and events to the AWS. The system will continue operation 

even if the SLAN fails. 

PvtLAN 

The Private LAN (PvtLAN) is a 10BaseT Ethernet connection from the AWS 

console to each processing node to enable TCP/IP login capability. 

Caution: The PvtLAN is intended to be private, and should not be configured as part of 

the user facility network. 

The following hardware is used to provide consistency in the PvtLAN cabling 

protocol, from small to expansion system configurations: 

• 8-port 10BaseT hub on the AWS, in systems with 16 nodes or less 

• 8-port 10BaseT hub in each expansion cabinet 

• 24-port 10/100BaseT switch in each BYA64 cabinet and each BYA64/BYB64 

cabinet 

SMP nodes in each expansion cabinet connect to the PvtLAN hub in their 

cabinet. For a cabinet that does not have a PvtLAN hub (i.e., single node cabinet 

or system cabinet with BYA4P switch cards or BYA16 chassis), the node(s) in 

that cabinet are connected to the PvtLAN hub in a neighboring cabinet. 

In a 3-node system configuration, each node connects directly to the PvtLAN 

hub at the AWS, since there is no PvtLAN hub resident in a cabinet. See 

Appendix B, Figure B-3. 




In a system of 16 nodes or less, each cabinet’s PvtLAN hub is connected to the 

PvtLAN hub at the AWS. This completes the connectivity to each node in the 

system for TCP/IP login capability. See Appendix B, Figure B-3. 

In systems greater than 16 nodes, the PvtLAN hubs are daisy-chained together 

in segments, with no more than four hubs per segment. Each segment is 

connected to the PvtLAN switch in the BYNET cabinet. In expansion systems 

with multiple PvtLAN switches, one switch is the central connecting point for 

all other PvtLAN switches. The central PvtLAN switch connects to the AWS, 

thus completing the connectivity to each node in the system for TCP/IP login 

capability. See Appendix B, Figure B-4. 

Hub-to-node and hub-to-AWS connections use twisted pair straight through 

cable. Hub-to-hub and hub-to-switch connections require cross-over cabling. 

MLAN 

The Management LAN (MLAN) is the main diagnostic and control LAN for all 

subsystem chassis within a cabinet. It is a 78 Kbps free topology network that 

links the service subsystem chassis to distributed management boards for the 

other subsystem chassis in the cabinet. 

There is a distributed management board for each rack subsystem chassis. Each 

board interfaces with the CMIC2 in the service subsystem chassis. 

For the BYNET chassis, the management board resides within the respective 

chassis. Point-to-point connection is between the management board and a 

pass-through board in the service subsystem. 

For all other subsystem chassis types, including the processing node, the 

UPS/UPS input selector, and the disk array, their respective management 

boards are located in the service subsystem chassis. Each is linked to its 

management board through a serial connection. 

See Appendix B, Figure B-5 and Figure B-6 for sample MLAN cabling 

configurations. 

The distributed management boards provide the interface for handling 

management functions within the chassis. These functions include power 

control, remote console, reset, and environmental monitoring. The CMIC2 

coordinates cabinet level reset, cabinet level network management, and 

physical chassis location. 

The MLAN is fault tolerant, thereby providing protection against broken and 

shorted connections. 

External MLAN 

The MLAN is commonly understood as the management LAN that is internal 

to the cabinet. In a “collective” configuration, an external MLAN is supported. 

2 – 18 




A “collective,” as defined in the current release, is a group of NCR storage 

cabinets (NSCs) or WorldMark enterprise storage (WES) connected to and 

controlled by the service subsystem in a processing rack. The disk cabinets 

have service subsystem chassis that do not contain the CMIC2 component (the 

Cabinet Module Interface Controller). These special chassis are identified by 

their smaller size, i.e., 2U. These are connected over an external MLAN to a 

collective-enabled 3U service subsystem that resides in a processing rack. 

The collective-enabled 3U chassis is the standard as of the current product 

release, and can be distinguished from the earlier version by a label on the back 

panel indicating “CRSM” (Collective Ready Server Management). This chassis 

is required to support the 2U service subsystems in a collective configuration. 

The external MLAN has the same properties as the MLAN that is internal to a 

cabinet. 

BYNET Network 

The BYNET network enables the processing nodes to communicate with each 

other. 

Each of two BYNET switches in a system represents a separate, redundant 

switching network for the processing nodes. Each node contains a multi-ported 

BYNET adapter card (BIC2G, BIC2C, or BIC4G, depending on the model), with 

one port cabled to one of the BYNET switches, a second port cabled to the 

second BYNET switch. This comprises dual BYNET switching networks. 

In 4800 and 4850 systems, the BYA switch board is used to interface a 

maximum of 4 nodes. See Appendix B, Figure B-7 and Figure B-8. 

In a 5200 or 5250 system using the BYA16G chassis, as many as 16 nodes are 

supported in the BYNET network. See Appendix B, Figure B-9. 

In a 5200 or 5250 system using the BYA64GX chassis, 64 nodes can be 

supported on one switch. See Appendix B, Figure B-10. 

Multiple BYA64GX chassis can be interfaced through multiple BYB64G chassis 

to expand the system to a maximum of 512 nodes. 

In an expansion configuration, each BYA64GX in a single network is connected 

to each BYB64G within its network. Each BYA64GX chassis supports 8 X-port 

connections to BYB chassis. Likewise, every BYB chassis presents 8 interface 

connections for BYAs. 

All expansion ports on the BYA and BYB chassis are used in any expansion 

configuration, affording maximum throughput. See Appendix B, Figure B-11. 

The 8 X-port connections on the BYA64GX chassis are distributed as evenly as 

possible among all BYB64G chassis in the network.Additionally, all BYA64GX 

and BYB64G chassis in a single BYNET network are daisy-chained through 

“clock cabling.” The first BYB64G chassis in the cabling chain is defined as the 

master; it has an output cable (Clock-Out), but no input cable (Clock-In). See 

Appendix B, Figure B-12. 




Cabinet Power 

SCSI 

Dual AC to each cabinet in the system is accommodated through two separate 

AC power sources, or through one AC power source with two separate circuit 

breakers. 

One power source is connected to power inlets on the left side of each UPS 

input selector (UIS), and the other power source is connected to the power 

inlets on the right side of each UIS. Power inlets on the left of the UIS represent 

Leg A of the power source, and the power inlets on the right represent Leg B. 

Leg A is the default power leg. That is, the UIS distributes power to its UPS 

through Leg A. Connections from cabinet to power source (UIS to AC power 

outlet) use the following cabling protocol: 

• In a system configured for load sharing: 

– Leg A of even-numbered cabinets, and leg B of odd-numbered cabinets, 

are plugged into one power source (AC1). 

– Leg A of odd-numbered cabinets, and leg B of even-numbered cabinets, 

are plugged into the other power source (AC2). 

• In a system configured without load sharing: 

– Leg A in each cabinet is plugged into one power source (AC1). 

– Leg B of each cabinet is plugged into the other power source (AC2). 

UPS to chassis connections also follow strict cabling protocol. Node chassis 

have three power inlets, so each UPS in a processing rack is connected to each 

node. All other subsystem chassis have two power inlets. Note that the 

PvtLAN and SLAN hub hardware has a single power inlet. 

See Appendix B, Figure B-13 and Figure B-14 for UPS to chassis power 

connections. 

PCI quad SCSI cabling provides the high-speed data link between processing 

nodes and disk arrays for external storage purposes. 

For connection to 6000 NCR storage cabinet (NSC) or 627x storage, processing 

nodes are populated with PCI quad SCSI (PQS) adapter boards, shared and 

unshared, that use special cable assemblies. Each of the four buses on a PQS 

board can support as many as 15 external devices. 

The configuration of PQS shared and unshared boards within groups of nodes 

determines the connectivity to disk storage devices. Up to four processing 

nodes can access the same disk array in a shared configuration, known as a 

“clique.” See Appendix B, Figure B-15 for a sample PQS shared cabling 


2 – 20 


Teradata IBM Channel 



For connection to 6000 WorldMark enterprise storage (WES), the nodes use 

high performance PCI quad SCSI (HP-PQS) adapters. These employ standard 

industry cabling that allows for point-to-point connectivity from the node to 

multi-ported disk arrays in the WES. Termination is end-of-bus only. See 

Appendix B, Figure B-16 for a sample HP-PQS/WES cabling configuration. 

The Teradata IBM channel provides the interconnect between the 48xx/52xx 

platform Teradata database and IBM (or compatible) mainframes for very high 

speed data transfer. Two types of channel interfaces are supported: 

• Parallel channel interface, referred to as bus and tag, PCI-based 

• Serial channel interface, referred to as ESCON (Enterprise Systems 

Connection), PCI-based 

The bus and tag interconnect consists of PCI bus channel adapter (PBCA) 

boards in the processing node (maximum of 2 per node), with 80-pin cable 

connecting to the channel tailgate assembly (CTGA). The tailgate assembly 

interfaces the PBCA cables to the IBM bus & tag channel cables. Tailgate 

assemblies are rack mounted. A tailgate rack can accommodate as many as 

eight tailgate assemblies. Each of the tailgate assemblies supports two PBCA 

cable interfaces. 

The ESCON interconnect consists of PCI Bus-to-ESCON adapter (PBSA) boards 

in the processing node, with fiber optic connections that plug directly into the 

edge of the adapter boards. No tailgate assembly is required for the PCI 

ESCON channel interface. 

These hardware interconnects are supported by Teradata system software. 



Cable Management 

Cable Management 

Standard cable management hardware on all system rack types consists of D 

rings along the inside vertical frame of the rack. These are used to secure routed 

cables from each of the chassis in the rack. 

Specialized hardware to handle the numerous cables from the node chassis and 

the BYA64GX chassis is also included in the respective racks. 

The processing rack is outfitted with a cable bracket that attaches to the left 

inside rear frame of the rack, in alignment with the node chassis it supports. 

Five clamps on the bracket are positioned top to bottom, to hold the cables from 

the node’s I/O panel in a cascading fashion. 

The BYNET rack uses a pair of cable brackets on the left and right inside rear 

frames of the rack, just behind the BYA64GX chassis. Each of the brackets is 

designed to hold half of the possible 64 total node interface cables. The brackets 

secure the cables in the pattern that they are presented from the back of the 

chassis. 

2 – 22 


Chapter 3: 

Subsystems Features 

This chapter provides details on each of the following WorldMark 48xx/52xx 

subsystem types: 

• Service Subsystem (3U) 

– 3U chassis 

• BYNET Interconnect 

– BYA4P Subsystem 

– BYA4G Subsystem 

– BYA16G Subsystem 

– BYA64GX and BYB64G Subsystems 

• Processing Node Subsystem 

• Power subsystem 

– UPS Chassis 

– UIS Chassis 

This chapter also includes descriptions of the following LAN hardware 

components, which are used in the WorldMark 48xx/52xx system cabling 

protocol: 

• SLAN Hubs 

• PvtLAN Hub and PvtLAN Switch 


Chapter 3: Subsystems Features 

Service Subsystem (3U) 


3U Service Subsystem Components 

The service subsystem is the top chassis in each rack. It is always chassis ID #1. 

Note: This section defines the 3U service subsystem chassis. There is a 2U 

service subsystem model, which is a “slave” to the 3U. In the current release, 

the 2U is used in the NCR storage cabinet only. The 2U is linked via external 

MLAN to a 3U in a processing rack to form a “collective.” For specifications on 

the 2U chassis, see the product documentation for the NCR storage cabinet. 

Hardware 

Following is a summary of the hardware components that make up the 3U 

service subsystem in processing and BYNET racks: 

• CMIC2 assembly: Message passing interface, performs the following 

system level functions: 

– SLAN to MLAN gateway 

– MLAN management 

– Distributed management board firmware downloading 

The CMIC2 assembly includes an ISA processor board with 4 MB RAM, 4 

MB flash EEPROM, an Ethernet port; serial board with 2 RS-232 ports for 

remote console support to nodes; passive ISA backpanel. 

• Management boards cage: Hot-swap capable backpanel with 8 slots. 

Supports the distributed management boards listed below: 

Rack CMB 

UMB 

PTB 

CMB 

(Chassis Management Board) Monitors service subsystem 

chassis status and keeps track of the rack configuration (i.e., the 

number and types of chassis within the rack). 

(Universal Management Board) Connects to processing node, 

enabling service subsystem to monitor node status and to access 

and administer the node remotely. 

(Pass-Through Board) Provides MLAN interface to BYNET CMB 

(which resides in the BYNET chassis) and NCR storage cabinet 

(NSC) 2U service subsystem. BYNET CMB performs same 

functions for BYNET as the UMB does for the node. 

Interfaces with UPS chassis, performing same function for UPS 

as the UMB does for the node. 

• Fans: Redundant fans, 12V DC each, for chassis cooling. 

3 – 2 




• Power: Two hot-plug power supplies, one on each AC leg, providing DC 

voltages. Redundant in a 1+1 configuration. Two separate AC feeds, each 

connecting to one of the two power supplies, accommodate dual AC input 

for high availability. 

Firmware 

Following is a summary of the firmware resident on the 3U service subsystem 

chassis. 

• CMIC2 firmware: Runs on CMIC2 to enable CMIC2 functionality 

including: 

– UMB, CMB, and rack configuration on MLAN 

– Command routing from AWS to appropriate chassis 

– Event routing from a chassis to AWS 

– Remote console from AWS to target processing node 

• UMB firmware: Runs on UMB to enable monitoring and remote control of 

node chassis 

• UMB network firmware: For MLAN communications processor on UMB 

• Rack CMB firmware: Runs on the rack CMB to enable monitoring of 

service subsystem chassis status/environment and MLAN conditions 

• CMB UPS firmware: Runs on CMB to enable monitoring and remote 

control of UPS chassis 

Figure 3-1 identifies the connectors and LEDs on the front and rear of the 

service subsystem chassis in a processing rack. Note that this same chassis is 

used in the BYNET rack, with minor variations in the population of the 

management boards cage, as noted in the table legend below the figure. 




Figure 3-1 

Service Subsystem Chassis Connectors and LEDs 

A 

Front 

CMIC2 Assembly 

B 

Management Boards 

Cage 

C E D 

L 

N 

P 

Rear 

Collective 

Enabled 

F 

G H I J K M O 

Figure 3-1 Item 

A 

B 

C 

D 

E 

F 

G 

Figure 3-1 Item Description 

Chassis status LED: 

Green = OK 

Amber = Chassis off-line, being reset, or booting up 

Power supply LEDs: Green = OK 

Ethernet BNC. SLAN connection 

CMIC2 processor LED: Green = Traffic on SLAN 

Serial interface to processing nodes for remote console support. Uses quad cable assembly 

(P1-P4 connectors) to nodes in rack as follows: 

• P1 top node (chassis #4) 

• P2 bottom node (chassis #5) 

Note: P3 and P4 connectors not used at this time 

Serial connections to CMIC2 for diagnostics: 

• Com 1 (right) at 38.8 Kbps 

• Com 2 (left) -- unused 

CMIC2 reset button 

3 – 4 





H 

I 

J 

K 

L 

M 

N 

O 

P 

CMIC2 assembly LED: Green = Power on 

Slot 1 - Rack CMB 

Slot 2 - PTB for BYNET: 

• 1st port to 2U service subsystem chassis in NSC (external MLAN) 

• 2nd port from 2U service subsystem chassis in NSC (external MLAN) 

• 3rd port to top BYNET in rack 

• 4th port to bottom BYNET in rack 

Note: PTB is resident in all service subsystem chassis, regardless of rack type. 

Slots 3 and 4 - UMBs for node chassis #4 and #5, respectively: 

• top port to ICMB connector on node 

• bottom port to COM 2 connector on node 

Note: These slots are vacant in service subsystem for BYNET rack. 

UMB LEDs: 

Service (left): Green = Power on 

Status (right): 

Green = OK 

Amber = Critical fault 

Blinking = Board is faulted or booting 

Slots 6, 7, and 8 - CMBs for UPS chassis, as follows: 

• In processing rack 

Slot 6 to UPS/UIS chassis #6 



• In BYNET rack: 

Slot 6 is vacant 



“Y” communications cable is used for each chassis. It connects 15-pin communications port on 

the UPS input selector to the top and bottom ports of the respective CMB in service subsystem. 

CMB LED: 

Green = OK 

Amber = Problem with board or firmware flash in progress 

Blinking = Unconfigured board 

Dual AC power inlets, 120/220 volts each: 

• Top (inlet #1) to UPS 1 

• Bottom (inlet #2) to UPS 2 


“Collective Enabled” indicates that this 3U service subsystem model is enabled to support 2U 

“slave” service subsystems in disk racks in a collective environment. 

Note: For information about the 2U service subsystem chassis, see the product documentation 

for the NCR storage cabinet. 



BYNET Interconnect Subsystem 


The BYNET interconnect enables transaction passing among Symmetrical 

Multi-Processing (SMP) nodes in a high-speed, loosely coupled fashion. 

Following are the types of BYNET subsystems, based upon system 


BYA4P switch board 4800 system / 

1-4 nodes max. 

BYA4G switch board 4850 system / 


BYA16G chassis 5200 and 5250 system / 


BYA64GX chassis 5200 and 5250 system / 

18-64 nodes 

PCI adapter board, plugs into the I/O board in the 

processing node. One BYA4P is installed in each of the 

two nodes in the base cabinet. 

PCI adapter board, plugs into the I/O board in the 

processing node. One BYA4G is installed in each of the 

two nodes in the base cabinet. 

3U chassis. Two installed in base cabinet as Chassis 

IDs #2 and #3, respectively. 

12U chassis. Installed in BYA64G cabinet and in 

BYA64/BYB64 cabinet as Chassis ID #2. 

BYB64G chassis 

5200 and 5250 system 

beyond 64 nodes 

5200 and 5250 system 

beyond 64 nodes 

12U chassis. Installed in BYB64G cabinet and in 

BYA64/BYB64 cabinet as Chassis ID #3. 

BYA4P Subsystem 

Following is a summary the hardware components of the BYA4P subsystem 

type. Note that BYA4P interconnect is a board only, and is housed in the 

processing node, rather than in its own rack chassis. 

Figure 3-2 

• BYA4P switch board: Four-port BYNET network board provides bidirectional 

communication among a maximum of four SMP nodes. 

Supports four 10 MB per second taxi ports, compatible with BYNET v 1.0 

and v1.1. 

The BYA4P does not include the Diagnostic Processor (DP). BYNET DP 

functions for the BYA4P subsystem are handled through driver software. 

Figure 3-2 identifies the BYA4P switch board faceplate, as it is presented at 

the node bulkhead. The BYA4P board is conventionally seated in PCI slot 10 

in the node adapter cage. 

BYA4P Connectors 

3 2 1 0 

3 – 6 




• BIC2G adapter: Circuit board providing connection to BYNET switch. Two 

10 MB per sec channels (Ports 2 and 3), compatible with BYNET v1.0 and 

v1.1 switches, as shown below. 

3/v1 2/v1 1/v2 0/v2 

Connect to BYA4Ps 

BYA4G Subsystem 

Note: Two 1 Gbit per sec channels, compatible with BYNET v2.0 switches, 

(Ports 0 and 1) are not used. Only ports 2 and 3 are used to connect to the 

BYA4P switch in the current release of WorldMark 4800/5200. 

Following is a summary the hardware components of the BYA4G subsystem 

type. Note that BYA4G interconnect is a board only, and is housed in the 

processing node, rather than in its own rack chassis. 

• BYA4G switch board: Version 2 four-port network board provides bidirectional 

communication among a maximum of four SMP nodes. 

Supports four serial 1.0625 Gbit/sec Fibre Channel ports, compatible with 

BYNET v2 only. The 4G switch interfaces with the BIC2C adapter in the 

node. 

The BYA4G does not include the Diagnostic Processor (DP). BYNET DP 

functions for the BYA4G subsystem are handled through driver software. 

The switch board faceplate is identical to the BYA4P, as shown earlier in 

Figure 3-2. 

• BIC2C adapter: Circuit board providing connection to BYA4G switch in the 

4850 platform. Two 1 Gbit per sec channels, compatible with BYNET v2.0 

switches (Ports 0 and 1), as shown below. 

BIC2C 

1/v2 0/v2 

BYA16G Subsystem 

Following is a summary of the hardware and firmware components of the 

BYA16G subsystem. All listed components are located within the BYA16G 

chassis, except for the adapter card, which is installed in the processing node. 

The BYA16G chassis contains no field-replaceable components; it is serviced as 

a single replaceable unit in the rack. 




• BIC4G adapter (installed in processing node): Circuit board in processing 

node, provides access to BYNET switch. BIC4G has four 1 Gbit per sec 

channels (Ports 0-3, right to left, as shown below), compatible with BYNET 

v2.0 switches. Port 0 to BYNET 0, Port 1 to BYNET 1. 

3/v2 2/v2 1/v2 0/v2 

Note: BIC4G Ports 2 and 3 are not used in the current release of WorldMark 

48xx/52xx. 

• BYA16G switch board: Stage A non-expandable switch board. Supports 

maximum 16 links to nodes (through BIC4G adapters). The BYA16G switch 

board also includes the Diagnostic Processor (DP) and power supply 

interface. 

• Power supplies: Two AC-DC power supplies. Redundant in a 1+1 

configuration. Two separate AC feeds to accommodate dual AC input. 

• Fans: Three fans, 12V each, for chassis cooling. 

• BYNET CMB: Chassis management board that handles out-of-band 

management functions within the BYNET chassis, including power control, 

reset, environmental monitoring. Provides the MLAN connection to the 

service subsystem. 

• BYNET CMB firmware: Runs on the BYNET CMB to monitor the status 

and functionality of the BYNET-DP/BYNET chassis and report status to the 

CMIC2 via the MLAN. 

Figure 3-3 identifies the LEDs and connectors on the BYA16G chassis. 

3 – 8 




Figure 3-3 

BYA16G Subsystem Chassis (rear view) 

A 

C D 

Not Used 

SERVICE 

MLAN 

Not Used 

DP 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 5 

Port 6 

Port 7 

Port 8 

Port 9 

Port A 

Port B 

Port C 

Port D 

Port E 

Port F 

ETHERNET 

E 

AC 1 

AC 2 

B 

F 


A 

B 

C 

D 

E 

F 


Diagnostic Processor (DP) LED: 

Off = Powered off 

Green, solid = Powered on, diagnostics passed 

Green, blinking = Awaiting IP address, diagnostics passed 

Amber or Red = Abnormal 

Note: Within 10 seconds of power-up, the BYNET switch board’s LED should go from red to 

amber to green. 

Node connections. 16 ports in two banks (Ports 0-7 in bank 1; Ports 8-F in bank 2) to BIC4G 

adapters in processing nodes. 

Indicator for BYNET chassis management board (CMB): 

Green = MLAN connection good 

Amber = Connection error or card flash underway 

Note: An LED on the front panel of the chassis reflects the state of the BYNET chassis’ 

MLAN connection. It is on and green when the BYNET CMB is connected through the 

MLAN to a live service subsystem chassis. 

Management LAN (MLAN) connection from BYNET CMB to appropriate connector on the 

pass-through board (PTB) in slot 2 of the service subsystem chassis, as follows: 

• Top BYNET in rack to slot 2 PTB connector 3 

• Bottom BYNET in rack to slot 2 PTB connector 4 

Ethernet connection used for System LAN (SLAN) interface. Connections as follows: 

• From service subsystem chassis BNC connector to top BYNET in rack 

• From top BYNET to bottom BYNET in rack and terminated 

Dual AC power inputs, 120/220 volts each: 

• Top BYNET: left inlet (#1) to UPS 2, right inlet (#2) to UPS 3 

• Bottom BYNET: left inlet (#1) to UPS 1; right inlet (#2) to UPS 3 




BYA64GX and BYB64G Subsystems 

Following is a summary of the hardware and firmware components of the 

BYA64GX and the BYB64G subsystems. All listed components are located 

within the BYNET chassis, except for the adapter card, which is installed in the 

processing node. 

Both the BYA64GX and BYB64G chassis are designed so that their components 

are field-replaceable; this allows for parts maintenance of the chassis in the 

field. Also note that several components are the same ones used for the 

BYA16G chassis. 

• BIC4G adapter (installed in processing node): Circuit board in processing 

node, provides access to BYNET switch. BIC4G has four 1 Gbit per sec 

channels (Ports 0-3, r-l), compatible with BYNET v2.0 switches. Port 0 to 

BYNET 0, Port 1 to BYNET 1. (See the BIC4G illustration in the previous 

section on BYA16G.) 

Note: BIC4G Ports 2 and 3 are not used in the current release of WorldMark 

48xx/52xx. 

• Chassis Backpanel: BYA64GX backpanel supports 8 BYA8X switch boards 

and DP board. BYB64G backpanel supports 4 BYB16G switch boards and 

DP board. See part descriptions below. 

• BYA8X switch board (in BYA64GX chassis): Stage A base switch board. 

Each board supports 8 links to nodes. The BYA64GX chassis can contain a 

maximum of 8 BYA8X switches, allowing for 64 links to nodes. In systems 

greater than 64 nodes, the BYA8GX switch boards also connect the 

BYA64GX chassis to BYB64G chassis through X-port connectors, one on 

each BYA8X board. 

• BYB16G switch board (in BYB64G chassis): Stage B expansion switch 

board. The BYB64G chassis contains 4 BYB16G boards. These boards 

interconnect through the BYB backpanel to provide 8 expansion ports. The 

expansion ports are used to interconnect BYA64GX chassis (through X-port 

connections on BYA8X switch boards). A maximum of 8 BYA64GX chassis 

can be interconnected to a maximum of 8 BYB64G chassis (one X-port 

connection from each BYA64 chassis to the expansion port on each BYB64 

chassis), thus providing up to 512-node switching capacity. 

• BYNET CMB: Chassis management board that handles out-of-band 

management functions within the BYNET chassis, including power control, 

reset, environmental monitoring. Provides the MLAN connection to the 

service subsystem. 

• DP board: Diagnostic Processor board, provides the BYNET diagnostic 

interface and BYNET clock distribution. 

• Power supplies: Two AC-DC power supplies. Redundant in a 1+1 

configuration. Two separate AC feeds, each connecting to one of the two 

power supplies, accommodates dual AC input for high availability. 

• Fans: Three fans, 12V each, for chassis cooling. 

3 – 10 




• Diagnostic Processor (DP) core firmware: Runs on BYNET switch board to 

enable diagnostics, self-configuring topology generation, exception 

handling, and event logging. 

• BYNET CMB firmware: Runs on the BYNET CMB to monitor the status 

and functionality of the BYNET-DP/BYNET chassis and report status to the 

CMIC2 via the MLAN. 

Figure 3-4 identifies the components and connectors located on the rear of the 

BYA64GX and BYB64G chassis: 


Port 2Port 2 

Port 0Port 0 

Port 3Port 3 

Port 1Port 1 

Port 2Port 2 

Port 2Port 2 

Port 5Port 5 



Figure 3-4 

BYA64GX and BYB64G Subsystem Chassis Connectors and LEDs 

BYA64GX Rear 

Slot 0 Slot 2 Slot 4 Slot 6 DP Slot 7 Slot 5 Slot 3 Slot 1 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

Not 

Used 

BYABGX 

Service 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Not MLAN 

Port 6 

Used 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 2Port 

Port 3 

Port 0 

Port 3 

Port 1 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Service 

Port 5 Clock 

Out 

Port 4 

Clock MLAN 

In 

Port 4 

Port 5 

Port 4 

Port 4 

Port 5 

Port 4 

Port 5 

Front BYA64GX & BYB64G 

B 

A 

Port 3 

Port 2 

Port 1 

Port 0 

Port 3 

Port 2 

Port 1 

Port 0 

Port 3 

Port 2 

Port 1 

Port 0 

Not Port 6 

Used 

Port 7 

DPClock 

Out BYABGX 

Clock 

ETHERNET 

In 

X-Ports 

Not 

Used 

DP 

ETHERNET 

Port 6 

Port 7 

BYABGX 

X-Ports 

X-Ports 

Port 6 

Port 7 

BYABGX 

X-Ports 

Port 3 

Port 6 

Port 7 

Port BYABGX 4 

Port 5 

X-Ports 

Port 6 

Port 7 

BYABGX 

X-Ports 

C 

D 

STATUS PS 1 PS 2 

BYB64G Rear 

E 

F 

Slot 0 Slot 1 Slot 2 Slot 3 DP 

BYB16G BYB16G 0-7 

8-F 

BYB16G 

BYB16G 

10-17 

18-1F 

20-27 

28-2F 

30-37 

38-3F 

Not 

Used 

MLAN 

Clock 

Out 

Clock 

In 

G 

H 

I 

DP 

Not 

Used 

ETHERNET 

J 

K 

3 – 12 






A 

B 

C 

D 

MLAN connection LED: 

Green = OK 

Power supply LEDs: Green = OK 

Connectors on BYA8X switch board, providing interface to BIC4G adapters in processing 

nodes. 8 connectors (ports 0-7) per BYA8X board, 8 boards (slots 0-7) per BYA64GX chassis, 

for maximum 64 node connections. 

Note: The four left BYA8X boards are installed with the X-ports at the top; the four right 

BYA8X boards are inverted, with the X-ports at the bottom. 

X-ports, one on each BYA8X switch in the BYA64GX chassis. 8 X-ports per BYA64GX chassis 

to interface to BYB64G chassis. All 8 ports are used in any expansion system configuration 

beyond 64 nodes. The 8 X-port connections on each BYA64GX chassis are distributed equally 

among the BYB64G chassis in the network. For example: 

• In 65-128 node system with 2 BYA64GX and 2 BYB64G in a single BYNET network, each 

BYA64GX will have 4 connections to each BYB64G. 

Note: The system has a second, redundant BYNET network cabled in the same pattern. 

E 8 expansion ports on BYB64G, to interface with BYA64GX chassis through X-ports. All 8 

expansion ports are used. The 8 ports on each BYB64G are connected to each BYA64GX in a 

single network, with connections distributed equally. See the X-ports definition above. 

F 

G 

H 

I 

J 

K 

Dual AC power inputs, 120/220 volts each: 

• Left (inlet #1) to UPS Leg 1 

• Right (inlet #2) to UPS Leg 2 

Indicator for BYNET chassis management board (CMB): 

• Green = MLAN connection good 

• Amber = Connection error or card flash underway 

MLAN connection from BYNET CMB to appropriate connector on the pass-through board 

(PTB) in slot 2 of the service subsystem chassis, as follows: 

• BYA64GX to slot 2 PTB connector 3 

• BYB64G to slot 2 PTB connector 4 

Clock cabling connectors to link all BYNET chassis in single network. Chassis are 

daisy-chained, from Clock-Out on one chassis to Clock-In on next, starting with BYBs then 

moving to BYAs. First BYB in chain (no Clock-In cable) is master. 

Diagnostic Processor (DP) LED: 

Off = Powered off 

Green, solid = Powered on, diagnostics passed 

Green, blinking = Awaiting IP address, diagnostics passed 

Amber or Red = Abnormal 

Ethernet connection for System LAN (SLAN) interface. 



Processing Node Subsystem 


Node Components 

Two symmetrical multi-processing (SMP) node chassis are resident in a typical 

processing rack configuration. They are always referenced as chassis IDs #4 and 

#5, top and bottom respectively. 

Note: In the single node rack configuration of the 48xx system model, only the 

bottom node, chassis #5, is present. 

The SMP node is the processor building block of the system, with each node 

containing a minimum configuration that includes: 

4 Pentium III CPUs, 1 MB cache (XEON modules) 

1 GB of EDO RAM 

1 BYNET interface adapter (BIC2G, BIC2C, or BIC4G, depending on model) 

1 dual 10/100 Ethernet adapter (PvtLAN) 

1 single-ended SCSI adapter (internal drives only) 

4 9GB 10,000 RPM disk drives 

1 8mm tape drive 

1 3.5-inch flex drive 

1 CD ROM drive 

Additional PCI-based options are available, as required per system site, 

including the NCR PCI Quad SCSI (PQS) adapter or high performance PQS 

(HP-PQS) adapter for mass external storage interface, and Teradata IBM 

channel adapter for mainframe interface. 

Hardware 

Following is a summary of the hardware components that comprise the SMP 

node subsystem: 

• A450NX system board set: Dual baseboard design that includes: 

– CPU baseboard 

– I/O baseboard 

– Interconnect backplane 

The baseboards are physically placed back to back, connected to each other 

by the interconnect backplane. Two expander buses (F16 buses) electrically 

connect the two baseboards together. Power to the board set is supplied 

through the interconnect backplane. 

• CPU baseboard: Faces the left side of the chassis, and supports the 

following features: 

3 – 14 




– Processors: Four Xeon processor modules, each containing the 

processor core and L2 cache components inside a single edge connect 

(S.E.C.) cartridge. The cartridges plug into the CPU baseboard, and 

interconnect through the front side bus (FSB) to form 4-way SMP 

architecture. 

– Memory: Two high capacity DRAM memory boards. The 4800/5200 

node supports up to 4 GB of memory, using 16 dual in-line memory 

modules (DIMMs). 

• I/O baseboard: Faces the right side of the chassis, and provides the 

following connections: 

– 11 PCI bus master slots (one shared with ISA) 

– fast/wide SCSI II connection for flex drive 

– ultra/wide SCSI connection for 5.25-inch tape drive and CD-ROM 

– two IDE connectors 

– I/O panel including serial, parallel, and USB ports 

• ICMB (Intelligent Chassis Management Bus): Provides interface between 

the server management components within the node (i.e., Intel I 2 C 

microcontrollers) and the service subsystem in the rack. This interface of 

node to service subsystem accomplishes the overall chassis management 

strategy of the larger system. 

• Power: Three AC power inputs to three hot-plug 625-watt AC-DC power 

supplies. Each power supply connects to power adapter board, then to 

power translator board, then to power distribution backplane. The 

distribution backplane interfaces with the interconnect backplane to 

provide power to the CPU and I/O baseboards. It also distributes power to 

the SCSI backplane and fans. 

• Fans: Eight fans in three separate assemblies. CPU side of the chassis is 

cooled by a pair of dual fan arrays, at front and rear. I/O side of the chassis 

is cooled by a four-fan array at the front. 

• SCSI Drives/Backplane: Hot-swap drive backplane supports 5 available 

hot-swappable internal disk drives, 9 GB or 18 GB 10000 RPM. 




Software/Firmware 

Following is a list of the server software utilities available through the 

Diagnostic Partition (located on the first sector of the first partition on the first 

bootable hard drive in the node). These utilities are identified here as “server 

software”: 

• System Setup Utility (SSU): Used to configure the server; add, remove, 

and edit add-in boards; set passwords. 

• System Manager Event Log (SEL): Used to view, save, or clear the system 

event log. 

• BIOS Flash Utility (iflash): Used to update the BIOS as new versions 

become available. 

Following is a list of component firmware and software installed on the node: 

• Chassis enabling firmware: Enables front panel logic using front panel 

controller (FPC) code. Enables SCSI backplane using hot-swap SCSI 

backplane controller (HSC) code. 

• UMB software: Universal management board software, includes baseboard 

management controller (BMC) driver, UMB driver, and UMB agent. 

• BYNET driver software: BYNET Link Manager (BLM). UNIX STREAMS 

device driver that manages the physical device which connects a UNIX 

processor node to a BYNET. 

• BYNET adapter diagnostic software: BYNET utility program with 

command line interface that performs level 0 diagnostics through interface 

to the BIC adapter in node. 

• BYNET Administrative Menu (BAM) software: BYNET utility program 

with command line interface that determines BYNET configuration from 

node perspective for current installation. 

Figure 3-5 identifies the components and connectors on the rear of the 

processing node chassis: 

3 – 16 




Figure 3-5 

Processing Node Chassis (rear view) Components and Connectors 

B C E G 

A 

D 

F 

H 

I 


A 

B 

C 

D 

E 

F 

G 


Intelligent Chassis Management Board (ICMB) connection. To appropriate UMB in service 

subsystem chassis. as follows: 

• Top node in cabinet (chassis #4) to UMB, slot 3, top port 

• Bottom node in cabinet (chassis #5) to UMB, slot 4, top port 

Mouse (top) and keyboard (bottom) ports. Not used. 

Node console redirection connection. Quad cable assembly from CMIC2 serial port to node 

as follows: 

• Top node in cabinet (chassis #4) P1 connector 

• Bottom node in cabinet (chassis #5) P2 connector 

Note: P3 and P4 connectors of quad cable assembly unused at this time. 

MLAN connection to UMB in service subsystem chassis, as follows: 

• Top node in cabinet (chassis #4) to UMB, slot 3, bottom port 

• Bottom node in cabinet (chassis #5) to UMB, slot 4, bottom port 

Parallel port 

Video port. Not used. 

USB connector 





H 


11 PCI bus master slots numbered 1-11, top to bottom: 

• Primary 32-bit PCI slots (bus/segment 0), P1-P2 

• Secondary 32-bit PCI slots (bus/segment 1), P3-P6 

• 64-bit PCI slots (bus/segment 2), P7-P11 

I AC power inputs, numbered left to right, #1-#3: 

• inlet #1 to UPS chassis #6 



Figure 3-6 identifies the features found on the front of the node chassis: 

Figure 3-6 

Processing Node Chassis (front view) Components, Controls, and LEDs 

D 

C 

E 

A 

B 

F G H 

I 

J 

3 – 18 





A 

B 

C 

D 

E 

F 

G 

H 

I 

J 


LCD. Displays processor type information and failure codes. 

NMI switch. Causes non-maskable interrupt. 

DC power switch. May be disabled through BIOS secure mode. 

Caution: In standard operation, the node power is controlled through the AWS functions. 

The DC power switch does NOT completely remove AC power from the node. You must 

disconnect the AC power cord from the node chassis. 

Reset switch. 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 supply fail LED, yellow. When lit continuously, it indicates a power supply failure. 

When flashing, it indicates a 240 VA overload shutdown and power control failures. 

Fan fail LED, yellow. Flashing indicates a fan failure. 

Internal SCSI drive fault LED, yellow. When lit continuously, it indicates a fault status on 

one or more hard disk drives in the hot-dock bays. When flashing, it indicates drive reset in 

progress. 

3 removable media bays, populated as follows, left to right: 

• Flex (3.5 in.) 

• CD-ROM (5.25 in.) 

• Tape (5.25 in.) 

Five SCSI hot-swap bays in two separate compartments, with two bays on the left, three on 

the right. Drives identified left to right as follows: 

#1 (SCSI ID 0) 

#2 (SCSI ID 1) note: drive #3 connector is not accessible 


#5 (SCIS ID 4) 


LED light pipes above each drive bay are connected to the SCSI backplane to indicate drive 

power, activity, and fault. 

Note: The LEDs are visible only when the faceplate is removed. 



Power Subsystem 


AC power to each cabinet in the system is provided by a power subsystem 

consisting of the following: 

Power Subsystem Chassis 

# in 

Processing 

Cabinet 

# in BYNET 

Cabinet 

# in NCR 

Storage 

Cabinet 

Uninterruptible power supply (UPS) 3 2 2 

UPS input selector (UIS) 3 2 2 

The UPS and UIS chassis are paired in the rack, with a UIS mounted on the left 

rear of each UPS. UPS/UIS chassis are always the bottom-most chassis. Chassis 

IDs are #6, #7, and #8 in the processing rack; #4 and #5 in the BYNET rack. 

UIS Chassis 

The UIS chassis interfaces between the AC power sources and the UPS. It takes 

power from both sources, then selects one of the sources and delivers it to its 

respective UPS. The selected power source is always defaulted to Leg A. 

Figure 3-7 identifies the components and connectors on the rear panel of a UIS. 

Figure 3-7 

UIS Connectors and LEDs (rear view) 

A 

B 

15 AMP 

15 AMP 

15 AMP 

15 AMP 

! 

Caution ! 

Double-pole neutral 

overcurrent protection 

C 

DEF G H 

3 – 20 






A AC power source inlet (Leg A) 

B AC power source inlet (Leg B) 

C 

D 

E 

F 

G 

H 

AC power outlet (connects to the AC power inlet on its respective UPS) 

Leg A status LED: 

Green = Leg is operating normally (power present, within tolerance) 

Amber = Leg is out of tolerance or power is absent. If other leg’s LED is green, power has 

been switched to that leg; if other leg’s LED is amber, power will not switch to other leg, and 

UPS will go on batteries 

Leg B status LED (same definition as Leg A status LED above) 

UIS fault LED: 

Green = UPS-IS is operating normally 

Amber = UPS-IS has a fault condition 

Management LAN (MLAN) connection. To appropriate UPS CMB in the service subsystem 

chassis, as follows: 

• In processing rack: 

UIS chassis #6 to slot 6 CMB 



• In BYNET rack: 



“Y” communications cable is used to connect this port on UIS to both the top and bottom 

ports of the respective CMB in the service subsystem. 

Communications port to connect UIS to UPS 

UPS Chassis 

The UPS chassis distributes 200-240V AC output to the other chassis to which it 

is connected in the cabinet. The UPS can provide approximately 10 minutes of 

battery backup to a processing node in case of power failure, thus allowing for 

orderly shutdown of the node or a power-fail memory dump. 

Figure 3-8 identifies the components and connectors located at the rear of the 

UPS chassis: 




Figure 3-8 

UPS Chassis (rear view) 

A 

C 

E 

B 

D 

F 



A 

B 

C 

D 

E 

F 

AC inlet for UIS power cord. 

unused 

Four circuit breakers; one for each of the three outlet groups (see D) and one for all outlet 

groups. 

Outlets for chassis power cords. Outlets are grouped vertically, groups are numbered right to 

left (1,2,3). Within each group, outlets are lettered top to bottom (A,B,C). Groups and outlets 

are critical to chassis cabling protocol. 

Serial communications port to UIS. 

Emergency power off (EPO) connector that can be wired to a remote EPO switch. Enables 

shutdown of both AC power and battery backup power from a remote EPO switch 

3 – 22 




Figure 3-9 identifies the controls and LEDs located on the front panel of the 

UPS chassis: 

Figure 3-9 

UPS Front Panel LEDs 

Battery Charge 

AC Input 

Load Level 

On LED 

On Button 

Standby Button 

Comm. Port 

Battery Service 

Site Wiring 

Test/Alarm Reset 

Button 


On Button 


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 source, power can be run from the battery by 

pressing the On button for three seconds. 

Standby Button 

Test/Alarm 

Reset Button 

On LED 

Site Wiring Fault 

Removes power from the load groups and places UPS on standby. (Caution: UPS must be 

unplugged from the AC source for complete power-off.) 

Turns off the alarm. (The alarm sounds when there is a problem with the UPS). Runs a selftest 

when pressed for three seconds. 

Green = Power is available in the outlets in the rear panel of the UPS 

Off = Normal 

Red = Large voltage difference between ground and neutral 

(Note: LED disabled if site wiring configuration is line to line) 

Battery Service 

Off = Normal 

Red and alarm active = Potential battery failure detected 

Comm. Port 

Green, steady = Establishing communication with service subsystem 

Green, flashing = Transferring data between service subsystem, UPS 





AC Input 

(4 LEDs) 

Top 

Upper 

Middle 

Lower 

Middle 

Bottom 


Off = Normal 

Red, steady = Overvoltage condition; UPS operating on batteries 

Red, flashing = Pre-existing overvoltage condition, at battery shutdown 

Green = AC input OK 

Green = AC input low but UPS not on battery power 

Off = Normal 

Red, steady = AC input is too low (power failure), UPS on battery power 

Red, flashing = Pre-existing low voltage condition, at battery shutdown 

Battery Charge 

(4 LEDs) 

All Battery Charge 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. 

Top Green = Battery charge > 90% 

Load Level 

(4 LEDs) 

Upper 

Middle 

Lower 

Middle 

Bottom 

Top 

Upper 

Middle 

Lower 

Middle 

Green = Battery charge > 66-90% 

Green = Battery charge > 33-66% 

Red = Battery low; 3-5 minutes left 

Off = Normal 

Red = Overload (load currents or watts exceed UPS load capacity) 

Green = Load current or watts > 66-100% 

Green = Load current or watts > 33-66% 

Bottom Green = Load current or watts > 5-33% 

3 – 24 


SLAN and PvtLAN Hardware 



Hub and switch hardware is used in the WorldMark 48xx/52xx configurations 

to provide for consistent SLAN and PvtLAN cabling protocol, from small to 

expansion systems. Hardware components of the System LAN (SLAN) and the 

Private LAN (PvtLAN) are as follows: 

Component Description Locations 

SLAN hub 

8-port 10BaseT hub* 

4-port 10Base2 hub 

At the AWS console. 

In every BYA64 cabinet and BYA64/BYB64 cabinet. 

Installed below service subsystem chassis. 

PvtLAN hub 8-port 10BaseT hub At the AWS console. 

In every expansion cabinet. Installed below service 

subsystem chassis. 

Also included with AWS. 

PvtLAN switch 24-port 10/100BaseT switch In every BYA64 cabinet and BYA64/BYB64 cabinet. 

Installed below SLAN hub. 

* The 10BaseT SLAN hub is not included in system configurations that use an earlier AWS model with an 

internal 10Base2 network interface card. 

SLAN Hubs 

10BaseT SLAN Hub at AWS 

The SLAN hub at the AWS is the same model that is used for the PvtLAN hub 

throughout the system. See “PvtLAN Hub” later in this chapter for a hardware 

description. 

Note: In system configurations of 16 nodes or less, there are two 10BaseT hubs 

located at the AWS, one for the SLAN connection and one for the PvtLAN. You 

can differentiate the SLAN hub by the 10Base2 (coaxial) cable going into it from 

the processing cabinets. 

Note: The 10BaseT SLAN hub is not included in system configurations that use 

an earlier AWS model with an internal 10Base2 network interface card (NIC). 




10Base2 SLAN Hub 

Figure 3-10 SLAN Hub Connectors and LEDs * 

The following identifies the significant connectors and LEDs on the 10Base2 

SLAN hub, as applicable to this network: 

A 

Front 

View 

CentreCOM 

3004SL 

IEEE 802.3 10 BASE2 ETHERNET 

4 PORT REPEATER 

10 BASE2 PORTS 

1 2 3 4 

ON-LINE 

ON-LINE 

ON-LINE 

ON-LINE 

RECEIVE RECEIVE 

RECEIVE RECEIVE 

COLLISION COLLISION 

COLLISION COLLISION 

AUI 

PORT 

ON-LINE 

RECEIVE 

COLLISION 

ACTIVE 

POWER 

D 

Rear 

View 

AUI 

PORT 

4 


3 2 1 

CentreCOM 

3004SL 



POWER 

B 

C 

E 



A 

B 

C 

D 

Port status LEDs (4 sets of LEDs, one per port, as labeled): 

• Yellow = On-line. Port is connected to another On-line port. 

• Blue = Receive. Port is functional and incoming traffic is present. 

• Red = Collision. Flickering LED indicates data collision. (Occasional collisions are 

common; excessive collisions may indicate problem on segment.) If lit continuously, 

problem with port, cabling, or excessive traffic may exist. 

AUI connector, used to link AWS to each BYNET rack in daisy chain (primary segment). 

BNC ports 4 - 1, left to right, each representing a segment: 

• Port 4: to service subsystem chassis within cabinet (internal segment) 

• Ports 3, 2, and 1: each to group of expansion cabinets (in daisy chain via service 

subsystem in each cabinet) 

Note: No more than 30 connections supported per segment, including the SLAN hub port. 

Termination/ground switch at each BNC connector. Default is on. 

E Single power inlet to UPS 1. 

* Note: The hub is mounted in the BYNET rack at the rear, with the BNC connectors accessible from the back of 

the rack. The LEDs on the front of the hub are visible only when the appropriate filler panel on the front of the 

rack is removed. 

3 – 26 


PvtLAN Hub 

Figure 3-11 PvtLAN Hub Connectors and LEDs * 



The following identifies the significant connectors and LEDs on the PvtLAN 

hub: 

Front 

View 

IEEE 802.3 10BASE-T/AUI 

MULTIPORT MICRO-HUB REPEATER 

TM 

NETWORK LOAD 

LINK OK 

10BASE-T NETWORK PORTS 

1 2 3 4 5 6 7 8 

HUB STATUS 

1 2 4 8 16 32 64 84 + % 

RECIEVE 1 2 3 4 5 6 7 8 

ACTIVITY COLLISION POWER 

D 

E 

F 

Rear 

View 


8 7 6 5 4 3 2 1 

X X X X X X 

X 

10BASE2/AUI BACKBONE PORTS 

AUX 

POWER 

A 

B** 

C 



A 

B** 

8 STP/UTP 10BaseT (RJ45) ports for node-to-hub connections within rack (using straightthrough 

cable), and for hub-to-hub connections between racks (using crossover cable). 

BNC port for connecting SLAN 10Base2 network to AWS 10BaseT network interface card. 

C Single power inlet to UPS 2. 

D 

E 

F 

Network load LEDs. Indicate percentage of network use. 

Port status LEDs, two for each RJ45 port: 

• Link OK: No light = physical connection problem. Green steady = valid link 

• Receive: Amber flashing = Link OK and there is activity on port 

Hub status LEDs. 

• Power: Green = power on 

• Collision: Amber flashing = SQE or frame collisions. May be caused by overloaded 

segment, faulty cable, or loose connection. (Occasional collisions are normal; constant 

illumination may indicate excessive traffic problems.) 

• Activity: Green = hub is functional and is transmitting packets 

* Note: The hub is mounted in the processor expansion rack at the rear, with the Ethernet connectors accessible 

from the back of the rack. The LEDs on the front of the hub are visible only when the appropriate filler panel on 

the front of the rack is removed. 

** Note: The BNC connector is used only on a 10BaseT hub serving as an SLAN hub at the AWS. See “SLAN 

Hubs” for explanation. 


STATUS 

FAULT 

POWER 

RESET 



PvtLAN Switch 

The following identifies the significant connectors and LEDs on the PvtLAN 

switch, as applicable to this network: 

Figure 3-12 PvtLAN Switch Connectors and LEDs * 

Note: Your switch model may vary slightly in appearance from the one shown 

here but the functionality remains the same. 

E 

Front 

View 

Rear 

View 

CentreCOM 8124XL 

10 BASE-T/100 BASE-TX 

FAST ETHERNET SWITCH 

10 BASE-T/100BASE-TX PORT ACTIVITY RS-232 

9x 11x 13x 15x TERMINAL PORT 

1x 3x 5x 7x 17x 19x 21x 23x 

1 3 57 9 11 1315 1719 21 23 

24 6810 12 1416 18 20 22 24 

2x 4x 6x 8x 10x 12x 14x 16x 18x 20x 22x 24x 

D 

A 

B 

C 


A 

B 

C 

D 


24 auto-negotiating 10Base-T/100Base-TX ports for hub-to-switch segment connections. 

Port activity LEDs, two for each 10Base-T/100Base-TX port: 

• Link OK/Receive (top LED per port): 

Green steady = physical link with device 

Green flashing = port is receiving packets 

• 100M (bottom LED per port): 

Amber = port is operating at 100Mbps 

Unlit = port is operating at 10 Mbps 

Power LED: 

• Green steady = power on, voltage within range, power supply working 

Fault LED. 

• Red steady = switch or management software malfunctioning 

• Red flashing = switch is booting, running diagnostics, writing image to flash, transferring 

files via XMODEM 

E Single power inlet to UPS 2. 

* Note: The switch unit is mounted in the BYNET rack at the rear, with the Ethernet connectors accessible from 

the back of the rack. The power connector for the unit faces the front of the rack. 

3 – 28 


Chapter 4: 

System Management and Maintenance 

This chapter provides the following information on system management and 

maintenance: 

• Initialization 

• Power On/Off 

• Administration 

• Logs 


Chapter 4: System Management and Maintenance 

Initialization 

Initialization 

The system is self-configuring upon power-up through the functions of the 

service subsystem in each rack. 

The CMIC2 in the service subsystem detects the type of chassis connected to it 

by the management boards and their location. The CMIC2’s ability to identify 

the rack components enables it to generate information for the system 

configuration at power-up. 

This auto-configuration routine requires about three minutes, while each 

chassis establishes communications with the service subsystem in the rack. 

Once initialized, the system will continue to recognize physical and 

environmental changes, as well as communicate on-line operating events. 

4 – 2 



Power On/Off 

Power On/Off 

The system’s power is controlled and monitored through the Administration 

Workstation (AWS). Note that the control panel power switch on the node 

chassis is not used for power control under normal operating conditions. 

When power is available at the UPS/UIS and all cables are connected, the 

service subsystem and BYNET chassis are set to power on automatically. The 

nodes, as well as disk arrays that are physically connected to the AWS, must be 

powered on through the AWS. 

Note: 627x disk arrays are not controlled through the AWS. See “System 

Platform Interfaces” in Chapter 2 for more about disk array interfaces. 

Following are the strategies for powering on and powering off the nodes and 

disk arrays physically connected through the AWS. 

AWS Function 

System Level 

Power On/Off 

Cabinet Level 

Power On/Off 

Chassis Level 

Power On/Off 

Chassis Component 

Level Power On/Off 

Result 

Powers on/off all nodes, and NCR storage cabinet (NSC) or WorldMark enterprise 

storage (WES) disk arrays in the system environment. Service subsystem, BYNET, 

and UPS chassis across the system remain on-line. 

Note: BYNET power-off is optional during system power-off routine. 

Powers on/off both nodes within a target cabinet, and connected NSC or WES disk 

arrays. Service subsystem, BYNET, and UPS chassis in the target cabinet remain 

on-line. 

Note: BYNET power-off is optional during cabinet power-off routine, but it is not 

recommended if other nodes are attached to the BYNET switch boards. 

Powers on/off an individual chassis in the rack. AWS/UNIX allows for this 

function on each chassis type in rack, under the FRU power on/off function. 

AWS/NT allows for this function on the node chassis only; the other chassis types 

in the rack can be powered on/off individually at the chassis switch. 

Note: Disconnect the power cords from the chassis to completely remove power. 

On AWS/UNIX only, the FRU Replace function removes power from a targeted 

hot-plug component in a selected chassis. 

Caution: This is a servicing function. It should be used only by technically 

qualified field service personnel. 

At power-on, wait three minutes to allow each chassis in the cabinet to 

establish communication with the service subsystem. This is the autoconfiguration 

process. Once the power-on is complete, make sure the service 

subsystem can communicate with each chassis, by checking cabinet status 

through the AWS. 





The Administration Workstation (AWS) is the interface used by system 

administrators to configure and monitor the WorldMark systems. The AWS 

provides single-point administration in a multi-node configuration. 

AWS on UNIX 

The AWS under the UNIX operating system provides a graphical 

representation of the system configuration. The main window displays an 

appropriate icon for each cabinet in the configuration, as follows: 

AWS 

AWS 

AWS console: 

There is always only one AWS icon, even in a dual 

AWS configuration. Under dual AWS, the icon 

shown on the screen represents the console at which 

you are sitting. 

48xx/52xx processing cabinet: 

This icon will reflect each subsystem detected in the 

cabinet. 

BYNET cabinet: 


cabinet. 

4 – 4 




6000 NCR storage cabinet (NSC): 


cabinet. 

EMC 

CAB101 

627x disk array: 

This icon (for the 627x series disk arrays) is not 

generated automatically, as are the preceding icons. 

You can create the icon through the Edit Node 

Records function of the AWS. The icon will reflect 

the operational status of the 627x cabinet. However, 

because the 627x disk array has no physical 

connection to the AWS, you cannot perform control 

or maintenance functions through selection of this 

icon. 

From the cabinet-level view at the AWS main window, you can select a single 

cabinet and bring up a processor-level view of that cabinet. Through icon and 

menu selections, you can effectively monitor the system and its subsystems, 

and perform the necessary administrative and control functions. 

For complete information on using the AWS on UNIX to administer the system, 

see the Administration Workstation User Guide. 




AWS on Windows 

The AWS under the Windows NT or the Windows 2000 (when available) 

operating system provides a tree-based view of the system configuration. The 

main console window lists all of the managed components in a hierarchal 

arrangement, beginning at the enterprise level and branching downward to 

include systems, cabinets, chassis and their subcomponents, as in the following 

sample: 

From the tree view, you can choose a managed component of the system. The 

menu bar at the top of the main window allows you to select categories from 

which to perform administrative functions. The results window pane on the 

right shows the results of commands you have issued. 

For complete information on using the AWS on Windows NT or Windows 2000 

to administer the system, see the AWS User Guide for your system. 

4 – 6 



Logs 

Logs 

Event Log 

Server Support Log 

Events are generated through system software to execute functions and 

communicate the operational status of the overall system and its components. 

There are four event types, including: 

• Critical events: Indicate potential system loss, such as AC failure, 

subsystem failures, or high temperature. 

• Informational events: General logs, status messages and ungraded events. 

• Command events: Dispatched from an AWS or other sending agent and 

acted on by all CMIC2s. 

• Command completion events: Contain return status after a command event 

has been processed. (Not all command events generate a command 

completion event.) 

These system events are distributed over the SLAN and recorded in the Event 

Log. The Event Log is accessible through the AWS. You can use it to monitor 

the system. 

In a multiple AWS configuration, the SLAN commands sent out by one AWS 

will show up in the Event Log of all AWS consoles on the SLAN, ensuring a 

consistent single operational view of the system. 

Note: Each AWS is able to simultaneously execute unrestricted operations, 

such as alert monitoring or status review. However, only one AWS can enable 

and execute management functions at a time, thus locking out the other AWS 

from security operations. 

For information on accessing and using the Event Log, see the user guide for 

your AWS. 

When system support or service is required, use the Server Support Log for 

reference and documentation. 

The Server Support Log provides information on how to contact NCR support 

services. It also serves as a central place to record and store the system 

hardware and software history. The log includes forms for keeping the 

following records on the system: 

• System component and peripheral identification 

• Hardware/software performance and service 

• Preventive maintenance activities 



Logs 

These forms, if filled out accurately and on a regular basis, will provide 

information for the system operator and field service personnel to ensure 

successful operation of the server. 

4 – 8 


Appendix A: 

Product Statements 

WorldMark 4800/5200 and 4850/5250 Product Guide A – 1

Appendix A: Product Statements 

Regulatory and Technical Compliance 


Safety 

Cabinets in 48xx/52xx systems comply with the following safety standards: 

USA 

UL 1950, 3rd edition 

Canada CSA C22.2 No. 950-M95 

Europe 

CE Directive 73/23/EEC 

EN60950, 2nd edition 

IEC 950, 2nd edition 

EMI Emissions and Immunity 

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. 

Declaration of Conformity 

This product is in conformity with European Union EMC Directive 

89/336/EEC, using the following standards: 

• EN55022 (Class A) 

• EN55024 

• EN50081-1 

• EN50082-1 

The WorldMark 48xx/52xx system complies with the following standards for 

Electromagnetic Interference (EMI) and Susceptibility: 

A – 2 




DECLARATION OF CONFORMITY 

Type of Equipment: 

WorldMark 4800/5200 Enterprise System 

Model Number: Class 9100 

Power Rating: 

200-240 VAC; 16 Amps; 50/60 Hz; Single phase 

EU Directive Harmonized Standard(s) File/Test Report Number 

Directive EMC 89/336/EEC 

EMC 92/31/EEC 

EN 50081-1 : 1992 Emissions 

EN 55022 : 1994 

Test Report 007-0007165 

CISPR 22 : 1993 Class A Test Report 007-0007165 

EN 50082-1 : 1992 Immunity 

EN 61000-4-2 IEC 1000-4-2 : 1995 Test Report 007-0007165 



Directive LVD 73/23 EN 60950 Safety Test Report 007-0006668 

“NCR, headquarters at 1700 South Patterson Boulevard, Dayton, Ohio, 45479, USA declares that the 

equipment specified above conforms to the referenced EU Directives and Harmonized Standards.” 

Signature: (original signed by Alan Chow) Date: 

Alan Chow, Vice President, Data Warehousing Solutions Division 

NCR Corporation 

17095 Via del Campo 

San Diego, CA 92127 USA 

“Having received the Declaration of Conformity for the above product, signed by the responsible 

Director of Operations, I am authorized to countersign this Declaration of Conformity on behalf of 

NCR.” 

Signature: (original signed by Fidelma Cleary) Date: 

Name (printed): 

Fidelma Cleary, Attorney 

European Patent Attorney 

NCR Limited 

206 Marylebone Road 

London NW1 6LY, England 




Electromagnetic Compatibility 

Both conducted and radiated emissions meet the following requirements: 

USA Federal Communications Commission (FCC) 47 

Class A CFR Parts 2 and 15 

Canada 

Europe 

International 

Australia 

Taiwan 

Japan 

Industry Canada (IC) ICES-003 Class A 

EMC Directive 89 / 336 / EEC 

(European Economic Community) 

EN55022 Class A 

EN50081-1 

EN50082-1 

EN61000-4-2 

EN61000-4-3 

EN61000-4-4 

International Special Committee on Radio Interference (CISPR) 

Class A 

AS/NZS 3548, C-Tick Mark 

EMC Certification CNS13438 

VCCI (Voluntary Control Council for Interference) 

1st Class 

Electromagnetic Compatibility Notices 

The following table lists electromagnetic compatibility notices for this product: 

A – 4 




USA 

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. 

Canada 

European 

Union 

Disclaimer 

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. 

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, EN50081-1, EN50082-1 

and IEC (International Electrotechnical Committee) IEC 1000-4-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. 

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 user’s responsibility. 



Cautions and Warnings 

Cautions and Warnings 

The subsystem chassis in the WorldMark 48xx/52xx platform system contain 

no user-serviceable components. Only a technically qualified field engineer 

should service the system. 

The following warnings and cautions apply: 

Proper cooling and airflow 

Adequate ventilation must be maintained in the front and rear of the rack. The 

maximum temperature for the equipment in this environment is 40 o C (104 o F). 

Grounding 

Reliable earthing of the rack equipment must be maintained. Particular 

attention should be given to supply connections when connecting to power 

strips, rather than direct connections to the branch circuit. 

Rack Stabilization 

Front and rear stabilizers on the bottom of the rack frame must remain in place 

as installed. 

No more than one node chassis drawer should be extended at one time. 

Extension of more than one loaded module could cause the rack to tip or fall. 

A top-heavy rack could tip or fall. Proper weight distribution must be 

maintained. 

Power on/off 

The power on/off switch on subsystem chassis do not completely remove AC 

power. After shutting down and turning off a subsystem, the AC power cords 

must be unplugged from the chassis. 

Hazardous electrical conditions 

Hazardous electrical conditions may be present on power, telephone, and 

communication cables. Power must be properly removed to access equipment. 

Consult the field service technician. 

Hazardous energy levels are present behind the protective cover over the 

power distribution backplane in the node chassis. There are no user-serviceable 

parts; servicing should be done by technically qualified personnel. 

A – 6 


Appendix B: 

Cabling Maps 

This appendix illustrates the cabling of the system interfaces described in 

Chapter 2 of this guide. Use the following table to link to the descriptions 

and/or the illustrations of the WorldMark 48xx/52xx system interfaces: 

System Interface Description 

System Interface Illustration 

SLAN Figure B-1, Figure B-2 

PvtLAN Figure B-3, Figure B-4 

MLAN Figure B-5, Figure B-6 

BYNET Network 

Figure B-7, Figure B-8, Figure B-9, Figure B-10, 

Figure B-11, Figure B-12 

Cabinet Power Figure B-13, Figure B-14 

SCSI Figure B-15, Figure B-16 

WorldMark 4800/5200 and 4850/5250 Product Guide B – 1

8 

8 


7 6 5 4 3 2 1 


7 6 5 4 3 2 1 


POWER 

X X X X X X X X 


POWER 


8 7 6 5 4 3 2 1 

X X X X X X X 

Appendix B: Cabling Maps 

SLAN Cabling 

SLAN Cabling 

Figure B-1 

SLAN: 1 to 4 Nodes, and 2 to 16 Nodes 

1-4 Nodes 

AWS 

Console 

AWS SLAN Hub* 

*Not present with 

earlier AWS models 

2-16 Nodes 

AWS 

Console 

AWS SLAN Hub* 

B – 2 



8 7 6 5 4 3 2 1 



8 7 6 5 4 3 2 1 


8 


7 6 5 4 3 2 1 


POWER 



8 7 6 5 4 3 2 1 



8 7 6 5 4 3 2 1 


AUI 

PORT 

AUI 

PORT 

Port 1 Port 1 Port 1 

Port 1 Port 1 Port 1 

1x 

2x 

1x 

2x 

7x 

8x 

7x 

8x 

Port 3 

Port 2 

Port 1Port 1 

Port 3 

Port 2 

Port 1Port 1 

Port 0 

Port 0 

Port 5 

Port 5 



X-Ports 



X-Ports 

Port 2 

Port 2 

Port 2 

Port 2 


SLAN Cabling 

Figure B-2 

SLAN: 18 to 64 Nodes 

18-64 Nodes 

CentreCOM 

3004SL 

AWS 

Console 

AWS SLAN Hub ** 

* * 

* 

CentreCOM 

3004SL 

*** 

*Maximum 29 expansion 

cabinets per segment 

** Not present with 

earlier AWS models 


8 

8 



1 


X X X X X 

POWER 

X 

X X 

1 


POWER 



8 7 6 5 4 3 2 1 



8 

8 7 6 5 4 3 2 1 


POWER 


X X 

8 


7 6 5 4 3 2 1 


8 

8 7 6 5 4 3 2 1 


POWER 



POWER 


X 

X 


PvtLAN Cabling 


Figure B-3 

PvtLAN: 3 Nodes and 16 Nodes 

3 Nodes 

AWS 

Console 

AWS PvtLAN Hub 

7 6 5 4 3 2 1 


AWS 

Console 

AWS PvtLAN Hub 

7 6 5 4 3 2 1 

X X X 

**** 

*To Expansion Cabinet 

B – 4 




AUI 

PORT 

AUI 

PORT 

4 

4 


3 2 1 


3 2 1 

3004SL 



3004SL 



POWER 

POWER 

1 

3 5 7 9 11 1315 1719 21 23 

2 4 6 8 10 12 1416 18 20 22 24 

1 

3 5 7 9 11 1315 1719 21 23 

2 4 6 8 10 12 1416 18 20 22 24 

STATUS 

FAULT 

POWER 

STATUS 

FAULT 

POWER 

RESET 

RESET 

8 


7 6 5 4 3 2 1 


X X X X X X 

POWER 

X X AUX 

8 


7 6 5 4 3 2 1 



AUX 

POWER 

8 


7 6 5 4 3 2 1 


X X X X X X 

POWER 

X X AUX 

8 


7 6 5 4 3 2 1 



AUX 

POWER 



Figure B-4 

PvtLAN: 64 Nodes 

64 Nodes 

AWS 

Console 

CentreCOM 




1x 3x 5x 7x 9x 11x 13x 15x 17x 19x 21x 23x 

TERMINAL PORT 

2x 4x 6x 8x 10x 12x 14x 16x 18x 20x 22x 

24x 

* 

* 



CentreCOM 


1x 3x 5x 7x 9x 11x 13x 15x 17x 19x 21x 23x 

TERMINAL PORT 

* 

2x 4x 6x 8x 10x 12x 14x 16x 18x 20x 22x 

24x 

* 


15 AMP 

15 AMP 

15 AMP 

15 

AMP 

15 AMP 

15 AMP 

15 AMP 

15 AMP 

15 AMP 

15 AMP 

15 AMP 

15 AMP 

Not Used 

Not Used 

SERVICE 

SERVICE 

MLAN 

MLAN 

Not Used 

ETHERNET 

Not Used 

ETHERNET 


MLAN 

MLAN 

Figure B-5 

MLAN: Processing Rack 

in/out ports for 

WES and NSC 

connection 

(if no WES or NSC 

present, loopback 

cable required) 

Collective 

Enabled 

Not Used 

SERVICE 

MLAN 

Not Used 

ETHERNET 

Not Used 

SERVICE 

MLAN 

Not Used 

ETHERNET 

! 

Caution ! 



! 

Caution ! 



! 

Caution ! 



B – 6 




X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

Port 1 

Port 0 

15 AMP 

15 AMP 

15 AMP 

15 

AMP 

15 AMP 

15 AMP 

AUI 

PORT 

X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

Port 1 

Port 0 

X-Ports 

BYABGX 


1x 3x 5x 7x 9x 11x 13x 15x 17x 19x 21x 23x 

TERMINAL PORT 

2x 4x 6x 8x 10x 12x 14x 16x 18x 20x 22x 24x 

15 AMP 

15 AMP 

4 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

Port 1 

Port 0 


3 2 1 

X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 2Port 2 

Port 0Port 0 

Port 3Port 3 

Port 1Port 1 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 5 

Port 6 

Port 7 

BYABGX 

X-Ports 



Port 5Port 5 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 6 

Port 7 

1 3 5 7 9 11 13 15 17 19 21 23 

2 4 6 8 10 12 1416 18 20 22 24 

BYABGX 

X-Ports 

X-Ports 

Port 0 

Port 1 

Port 4 

Port 5 

Port 6 

Port 7 

BYABGX 

X-Ports 

POWER 

Port 0 

Port 1 

Port 4 

Port 5 

Port 6 

Port 7 

STATUS 

FAULT 

POWER 

BYABGX 

X-Ports 

RESET 


MLAN 

Figure B-6 

MLAN: BYNET Rack 

Collective 

Enabled 

CentreCOM 

3004SL 


Not 

Used 

Port 2 2Port 

Port 3 

Port 2 2Port 

Port 3 

Service 

MLAN 

Clock 

Out 

Clock 

In 

Not 

Used 

DP 

ETHERNET 

BYB16G 

BYB16G 

Conn 0 

BYB16G 

BYB16G 

Not 

Used 

Conn 1 

Conn 2 

Not MLAN 

Used 

Conn 3 

Conn 4 

Service 

Clock 

Out 

Clock 

MLAN 

In 

Conn 5 

Conn 6 

Conn 7 

Not 

Used 

Clock 

DP 

Out 

ETHERNET Clock 

In 

Not 

Used 

DP 

ETHERNET 

! 

Caution ! 



! 

Caution ! 





BYNET Network 

BYNET Network 


BYA4P Network to 4 Nodes 

3 2 1 0 

BIC2G 

3 2 1 0 

BYA4P Network 0 

Node 3 

Node 1 

BYA4P 

Network 1 

Node 4 

General Cabling Protocol: 

Node 2 

BIC2G Port 2 to BYNET Network 0 


Node 1 to BYA4P Port 0 




B – 8 



BYNET Network 


BYA4G Network to 4 Nodes 

1 0 

BIC2C 

3 

2 

1 

0 

BYA4G Network 0 

Node 3 

Node 1 

BYA4G 

Network 1 

Node 4 

General Cabling Protocol 

Node 2 

BIC2C Port 0 to BYNET Network 0 

BIC2C Port 1 to BYNET Network 1 

Node 1 to BYA4G Port 0 





DP 

DP 


BYNET Network 


BYA16GX Network to 16 Nodes 

BYA16G 

(Network 0) 

Not Used 

SERVICE 

MLAN 

Not Used 

ETHERNET 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 5 

Port 6 

Port 7 

Port 8 

Port 9 

Port A 

Port B 

Port C 

Port D 

Port E 

Port F 

AC 1 

AC 2 

BYA16G 

(Network 1) 

Not Used 

SERVICE 

MLAN 

Not Used 

ETHERNET 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 5 

Port 6 

Port 7 

Port 8 

Port 9 

Port A 

Port B 

Port C 

Port D 

Port E 

Port F 

AC 1 

AC 2 

Node 3 

Node 5 

3 2 1 0 BIC4G 

Node 7 

Node 1 

Node 4 

Node 6 

Node 2 




Node 8 

Nodes are distributed as evely as 

possible between the two banks of 

BYNET connectors (0-7 & 8-F). 

B – 10 



BYNET Network 


BYA64GX Network to 64 Nodes 

BYA64GX 

(Network 0) 

Slot 

0 

Slot 

2 

Slot 

4 

Slot 

6 

Slot 

7 

Slot 

5 

Slot 

3 

Slot 

1 

Node 8 

Node 7 

X-Ports 

BYABGX 

Port 7 

Port 6 

X-Ports 

BYABGX 

Port 7 

Port 6 

X-Ports 

BYABGX 

Port 7 

Port 6 

X-Ports 

Not 

Used 

BYABGX 

Service 

Port 7 

MLAN 

Port 6 

Port 0 

Port 1 

Port 2 

Port 3 

Port 0 

Port 1 

Port 2 

Port 3 

Port 0 

Port 1 

Port 2 

Port 2 

Port 3 

Port 0 

Port 1 

Port 2 

Port 2 

Port 3 

Node 9 

Node 10 

Node 11 

Node 12 

Node 6 

Node 5 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Clock 

Out 

Clock 

In 

Port 4 

Port 5 

Port 4 

Port 5 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Node 13 

Node 14 

Node 4 

Node 3 

Node 2 

Node 1 

Port 3 

Port 2 

Port 1 

Port 0 

Port 3 

Port 2 

Port 1 

Port 0 

Port 3 

Port 2 

Port 1 

Port 0 

Port 3 

Port 3 

Port 2 

Port 2 

Port 1 

Port 1 

Port 0 

Port 0 

Not Port 6 

Used 

Port 7 

DP 

BYABGX 

ETHERNET 

X-Ports 

Port 6 

Port 7 

BYABGX 

X-Ports 

X-Ports 

Port 6 

Port 7 

BYABGX 

X-Ports 

Port 6 

Port 7 

BYABGX 

X-Ports 

Node 15 

Node 16 

BYNET Network 0 

BYNET Network 1 

Nodes 

17-24 

Node 1 

Nodes 

33-40 

Nodes 

49-56 

Nodes 

57-64 

Nodes 

41-48 

Nodes 

25-32 

X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

BYA64GX 

(Network 1) 

X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

X-Ports 

Not 

Used 

BYABGX 

Service 

Port 7 

MLAN 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

Port 3 

Port 2 

Clock 

Out 

Clock 

In 

Not 

Used 

DP 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 5 

Port 6 

Port 7 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 5 

Port 5 

Port 6 

Port 7 

Port 0 

Port 1 

Port 2 

Port 2 

Port 3 

Port 4 

Port 5 

Port 6 

Port 7 

Port 0 

Port 1 

Port 2 

Port 2 

Port 3 

Port 4 

Port 5 

Port 6 

Port 7 

3 2 1 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 1 

Port 0 

Port 0 

BYABGX 

ETHERNET 

X-Ports 

BYABGX 

X-Ports 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 




Nodes are cabled in pattern that works from 

outer slots to inner slots of BYNET chassis, 

filling ports and slots in numerical sequence. 

Node 2 



Port 2Port 2 

Port 0Port 0 

Port 3Port 3 

Port 1Port 1 

Port 5Port 5 

Port 2Port 2 

Port 0Port 0 

Port 3Port 3 

Port 1Port 1 

Port 5Port 5 


BYNET Network 

Figure B-11 BYA64GX to BYB64G Connections: 

Expansion Port Cabling per BYNET Network 

(Sample 65-128 Node System) * 

BYA64GX 

(1) 

BYA64GX 

(2) 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

Not 

Used 

Service 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

Not 

Used 

Service 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

MLAN 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 2Port 

Port 3 

Port 2 2Port 

Port 3 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

MLAN 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 2Port 

Port 3 

Port 2 2Port 

Port 3 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Clock 

Out 

Clock 

In 

Port 4 

Port 5 

Port 4 

Port 4 

Port 5 

Port 4 

Port 5 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Clock 

Out 

Clock 

In 

Port 4 

Port 5 

Port 4 

Port 4 

Port 5 

Port 4 

Port 5 

Port 3 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 

Not 

Used 

DP 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 3 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 

Not 

Used 

DP 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

ETHERNET 

X-Ports 

X-Ports 

X-Ports 

X-Ports 

X-Ports 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

ETHERNET 

X-Ports 

X-Ports 

X-Ports 

X-Ports 

X-Ports 

BYB16G 

BYB16G 

Conn 0 

BYB16G 

BYB16G 

Not 

Used 

BYB16G 

BYB16G 

0-7 

BYB16G 

BYB16G 

Not 

Used 

Conn 1 

Conn 1 

Conn 2 

MLAN 

Conn 2 

MLAN 

Conn 3 

20-27 

Clock 

Out 

Clock 

In 

Conn 3 

20-27 

Clock 

Out 

Clock 

In 

28-2F 

30-37 

38-3F 

Not 

Used 

DP 

ETHERNET 

28-2F 

30-37 

38-3F 

Not 

Used 

DP 

ETHERNET 

BYB64G 

(1) 

BYB64G 

(2) 


All expansion ports on the BYA and BYB chassis are used. X-port connections on the BYA 

chassis are distributed as evenly as possible among all BYB chassis in a single BYNET network. 

B – 12 


Port 2Port 2 

Port 0Port 0 

Port 3Port 3 

Port 1Port 1 

Port 5Port 5 

Port 2Port 2 

Port 0Port 0 

Port 3Port 3 

Port 1Port 1 

Port 5Port 5 


BYNET Network 

Figure B-12 BYA64GX to BYB64G Connections: 

Clock Cabling per BYNET Network 

(Sample 65-128 Node System) 

BYA64GX 

(1) 

BYA64GX 

(2) 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

Not 

Used 

Service 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

X-Ports 

BYABGX 

Not 

Used 

Service 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

MLAN 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 2Port 

Port 3 

Port 2 2Port 

Port 3 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

MLAN 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 2Port 

Port 3 

Port 2 2Port 

Port 3 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Clock 

Out 

Clock 

In 

Clock 

Port 4 

Out 

Port 5 

Clock 

In 

Port 4 

Port 4 

Port 5 

Port 4 

Port 5 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Port 5 

Port 4 

Clock 

Out 

Clock 

In 

Clock 

Port 4 

Out 

Port 5 

Clock 

In 

Port 4 

Port 4 

Port 5 

Port 4 

Port 5 

Port 3 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 

Not 

Used 

DP 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 3 

Port 2 

Port 3 

Port 2 

Port 3 

Port 2 

Not 

Used 

DP 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

Port 6 

Port 7 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

BYABGX 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

ETHERNET 

X-Ports 

X-Ports 

X-Ports 

X-Ports 

X-Ports 

Port 1 

Port 0 

Port 1 

Port 0 

Port 1 

Port 0 

ETHERNET 

X-Ports 

X-Ports 

X-Ports 

X-Ports 

X-Ports 

BYB16G BYB16G 0-7 

BYB16G 

BYB16G 

Not 

Used 

BYB16G 

BYB16G 

0-7 

BYB16G 

BYB16G 

Not 

Used 

8-F 

10-17 

MLAN 

8-F 

10-17 

MLAN 

18-1F 

20-27 

28-2F 

30-37 

38-3F 

DP 

Not 

Used 

ETHERNET 

Clock 

Out 

Clock 

In 

18-1F 

20-27 

28-2F 

30-37 

38-3F 

DP 

Clock 

Clock 

Out Out 

Clock Clock 

In 

In 

Not 

Used 

ETHERNET 

BYB64G 

(1) 

BYB64G 

(2) 


All BYNET Chassis in a single network are daisy chained, from Clock-Out on one 

chassis to Clock-In on next, beginning with BYBs and moving to BYAs. 


Not Used 

Not Used 

SERVICE 

SERVICE 

MLAN 

MLAN 

Not Used 

ETHERNET 

Not Used 

ETHERNET 

8 


7 6 5 4 3 2 1 

X X X X X X X 


AUX 


Cabinet Power 

Cabinet Power 

Figure B-13 

Power: Processing Rack 

Collective 

Enabled 

! 

! 

15 AMP 

15 AMP 

15 AMP 

Caution ! 



15 AMP 

15 AMP 

15 AMP 

Caution ! 



15 AMP 

15 AMP 

15 AMP 

POWER 

15 AMP 

15 AMP 

15 AMP 

! 

Caution ! 



B – 14 




X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

Port 1 

Port 0 

15 AMP 

15 AMP 

15 AMP 

15 

AMP 

15 AMP 

15 AMP 

AUI 

PORT 

X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

Port 1 

Port 0 

X-Ports 

BYABGX 


1x 3x 5x 7x 9x 11x 13x 15x 17x 19x 21x 23x 

TERMINAL PORT 

2x 4x 6x 8x 10x 12x 14x 16x 18x 20x 22x 24x 

15 AMP 

15 AMP 

4 

Port 7 

Port 6 

Port 5 

Port 4 

Port 3 

Port 2 

Port 1 

Port 0 


3 2 1 

X-Ports 

BYABGX 

Port 7 

Port 6 

Port 5 

Port 4 

Port 2Port 2 

Port 0Port 0 

Port 3Port 3 

Port 1Port 1 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 5 

Port 6 

Port 7 

BYABGX 

X-Ports 



Port 5Port 5 

Port 0 

Port 1 

Port 2 

Port 3 

Port 4 

Port 6 

Port 7 

1 3 5 7 9 11 13 15 17 19 21 23 

2 4 6 8 10 12 1416 18 20 22 24 

BYABGX 

X-Ports 

X-Ports 

Port 0 

Port 1 

Port 4 

Port 5 

Port 6 

Port 7 

BYABGX 

X-Ports 

POWER 

Port 0 

Port 1 

Port 4 

Port 5 

Port 6 

Port 7 

STATUS 

FAULT 

POWER 

BYABGX 

X-Ports 

RESET 


Cabinet Power 

Figure B-14 

Power: BYNET Rack 

Collective 

Enabled 

CentreCOM 

3004SL 


Not 

Used 

Service 

MLAN 

Port 2 2Port 

Port 3 

Port 2 2Port 

Port 3 

Clock 

Out 

Clock 

In 

DP 

Not 

Used 

ETHERNET 

BYB16G 

BYB16G 

Conn 0 

BYB16G 

BYB16G 

Not 

Used 

Conn 1 

Conn 2 

MLAN 

Conn 3 

Conn 4 

Clock 

Out 

Clock 

In 

Conn 5 

Conn 6 

Not 

Used 

Conn 7 

DP 

ETHERNET 

! 

Caution ! 



! 

Caution ! 





SCSI 

SCSI 

Figure B-15 

Shared SCSI: 4-Node Clique with NCR Storage Cabinet (NSC) 

Node 

Cabinet 

NSC Disk 

Cabinet 

1440 

NSC Disk 

Cabinet 

1440 

Node 

Cabinet 

Q-s 

Q-u 

IN OUT 

Q-s 

Q-u 

Q-u 

Q-s 

1440 

1440 

Q-u 

Q-s 

....Repeat cabling for path to each redundant disk array controller... 

B – 16 



SCSI 

Figure B-16 

Point-to-Point SCSI: 4-Node Clique with WorldMark Enterprise Storage (WES) 

Node 

1 

Node 

2 

Node 

3 

Node 

4 



SCSI 

B – 18 


Index 

0 

Numerics 

6000 NCR storage cabinet See NSC 

6000 WorldMark enterprise storage See WES 

627x storage cabinet 1–3, 2–11 

disk arrays supported 2–11 

A 

AWS (Administration Workstation) 2–12 

icons 4–4 

network hubs at 2–12 

redundant consoles 2–12 

remote consoles 2–12 

BYB64G cabinet 1–9 

BYNET CMB (chassis management board) 3–2 

BYNET network 1–3, 2–19 

cabling description 2–19, 3–13 

cabling diagram B–8, B–9, B–10, B–11, B–12, 

B–13 

BYNET rack 1–3, 2–6 

cable management 2–22 

BYNET subsystem 3–6 

in 48xx 1–5 

in 52xx system, 18 to 64 nodes 1–7 


in 52xx system, greater than 64 nodes 1–9 

types 1–3, 3–6 

C 

B 

base cabinet 

in 48xx 1–5 

in 48xx system 2–6 

in 52xx system 1–7, 2–7 

BIC2C 1–5, 3–7 

BIC2G 1–5, 3–7 

BIC4G 1–7, 3–8, 3–10 

bus and tag 2–21 

BYA16G subsystem 1–7 

components 3–7 

connectors 3–9 

LEDs 3–9 

BYA4G 1–5 

BYA4G subsystem 


BYA4P 1–5 

BYA4P subsystem 



BYA64 cabinet 1–7, 2–8 

BYA64 subsystem 


connectors and LEDs 3–12 

BYA64/BYB64 cabinet 1–9, 2–9 

BYB64 cabinet 2–9 

BYB64 subsystem 



cabinets, types of 






cabling diagrams B–1, B–2 

BYNET network B–8, B–9, B–10, B–11, B–12, 

B–13 

MLAN B–6, B–7 

power B–14, B–15 

PvtLAN B–4, B–5 

SCSI B–16, B–17 

SLAN B–3 

cautions and warnings A–6 

CD-ROM, software 2–14 

CDROM, software 2–14 

chassis ID 

numbering conventions in rack 2–5 

clique 1–3, 2–20 

CMB (chassis management board) 3–2 

CMIC2 4–2 

CMIC2 (Cabinet Module Interface Controller) 2–17 

coexistence 1–10 

collective 2–18 

compliance, statements of A–2 

WorldMark 4800/5200 and 4850/5250 Product Guide Index –1

Index 

D 

Declaration of Conformity A–3 

disk storage 1–2, 1–3 

types 2–10 

dual AC 2–20 

dual AWS 2–12 

BYA16G subsystem chassis 3–9 

BYA64 and BYB64 chassis 3–12 

node subsystem 3–18 

PvtLAN hub 3–27 

PvtLAN switch 3–28 

service subsystem 3–4 

SLAN hub 3–26 

UIS chassis 3–20 

UPS chassis 3–23 

E 

EIA rails 2–2 

ESCON 2–21 

Ethernet LANs See interfaces, system platform 

event log 4–7 

events, system 2–17 

expansion cabinet 

in 48xx 1–5 


in 52xx system 2–7, 2–8, 2–9 


in 52xx systems greater than 16 nodes 1–7 

M 

maintenance, system 4–8 

management boards 2–18, 3–2 

memory See node subsystem, components 

MLAN (Management Local Area Network) 1–3, 

2–18 

cabling description 2–18 

cabling diagram B–6, B–7 

external to NSC 2–18 

F 

firmware 

BYNET 3–8, 3–11 

node subsystem 3–16 


I 

ICMB (intelligent chassis management bus) 3–15 

interfaces, system platform 2–15 

BYNET network 2–19 

cabinet power 2–20 

MLAN 2–18 

MLAN, external 2–18 

PvtLAN 2–17 

SCSI 2–20 

SLAN 2–15 

Teradata IBM channel 2–21 

L 

LANs See interfaces, system platform 

LEDs 

N 

node subsystem 1–2, 3–14 



LEDs, front 3–18 

non-TPA (trusted parallel applications) node 1–2 

NSC (NCR storage cabinet) 1–3, 2–10 


external MLAN connection 2–19 

P 

power on/off 

auto-configuration at power-on 4–2 

caution A–6 

power subsystem 

chassis specifications 3–20 

chassis types 1–2 

summary 1–3 

power, cabinet 

cabling description 2–20, B–14 

cabling diagram B–15 

processing node See node subsystem 

processing rack 1–2, 2–6 


Index –2 


Index 

processors See node subsystem, components 

PTB (pass-through board) 3–2 

PvtLAN (Private Local Area Network) 1–3, 2–17 



hub and switch hardware 2–17, 3–25 

hub connectors and LEDs 3–27 

switch connectors and LEDs 3–28 

types in WorldMark 48xx/52xx 1–2 

system cabinet See base cabinet 

system console 2–12 

systems, 48xx/52xx configurations 1–4 

48xx, 1-4 nodes 1–5 

52xx, 18 to 64 nodes 1–7 

52xx, 2 to 16 nodes 1–6 

52xx, greater than 64 nodes 1–9 

R 

rack 

chassis placement in 2–3 

specifications of 2–2 

rack CMB (chassis management board) 3–2 

rack mount architecture 1–2 

remote console 2–12 

T 

TCP/IP login See PvtLAN 

Teradata IBM channel 2–21 

Teradata node 1–2 

Teradata Warehouse 1–2, 2–14 

TPA (trusted parallel applications) 1–2 

S 

SCSI 



drives and controllers See node subsystem, 

components 

SDW See Teradata Warehouse 

server management See service subsystem 

Server Support Log 4–7 


2U in NSC 2–10, 2–19 



LEDs 3–4 

serviceability A–6 

single node cabinet 1–5, 1–7, 2–6, 2–7, 2–8 

SLAN (System Local Area Network) 1–3, 2–15 



hub hardware 2–15, 3–25 


SMP (symmetrical multi-processing) See node 

subsystem 

software 

BYNET 3–16 

server-level 2–14, 3–16 

system-level 2–14 

subsystems 

chassis IDs 2–5 

chassis placement in rack 2–3 

U 

U (unit of vertical space in rack) 2–2 

UIS (UPS input selector) 1–3, 3–20 


UMB (universal management board) 3–2 

UNIX operating system 2–14 

UPS (uninterruptible power supply) 1–3, 3–21 


LEDs 3–23 

W 

WES (WorldMark enterprise storage) 1–3, 2–10 


external MLAN connnection 2–19 

WorldMark 4800/5200 and 4850/5250 Product Guide Index –3

Index 

Index –4

World/Mark 4800/5200 and 4850/5250 Product Guide ... - NCR

Create successful ePaper yourself

Delete template?

Save as template?