ClearPath IX Systems Installation and Configuration Guide

Unisys e-@ction 

ClearPath Enterprise 

Servers 

ClearPath IX Systems 

Installation and Configuration Guide 

Draft Version 7850 5104-009B, 12/29/00 

This electronic copy of the Installation and Configuration Guide (ICG) is a 

draft update to the currently released ICG (7850 5104-009). It provides 

advance documentation of a capability or feature which will be included in 

the next official release of the ICG. The changes within must be considered 

preliminary and subject ot change without notice. Reader comments and 

suggestions on the changes are welcome via e-mail to doc@unisys.com. 

This draft is available in electronic form only and is not orderable. 

Added in this draft are the following: 

• Mylex AcceleRAID 352 Mylex Controller (RAD6002-P64) 

• Service Pack 1 for Windows 2000 

Printed in USA 

December 2000 7850 5104–009

Format these characters as “white” to force printing of blank page.



Servers 


Installation and Configuration Guide 

û 2000 Unisys Corporation. 

All rights reserved. 

Printed in USA 

December 2000 7850 5104–009 

Unisys

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information 

described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to 

purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the 

products described in this document are set forth in such agreement. Unisys cannot accept any financial or other 

responsibility that may be the result of your use of the information in this document or software material, including 

direct, special, or consequential damages. 

You should be very careful to ensure that the use of this information and/or software material complies with the laws, 

rules, and regulations of the jurisdictions with respect to which it is used. 

The information contained herein is subject to change without notice. Revisions may be issued to advise of such 

changes and/or additions. 

Notice to Government End Users: The software and accompanying documentation are delivered and licensed as 

“commercial computer software” and “commercial computer software documentation” as those terms are used in 48 

C.F.R. § 12.212 and 48 C.F.R. § 227.7202-1 through 227.7202-4, as applicable. The Government shall receive only those 

rights provided in the standard commercial software license, or where applicable, the restricted and limited rights 

provisions of the contract FAR or DFARS (or equivalent agency) clause. 

Correspondence regarding this publication can be e-mailed to doc@unisys.com. 

Unisys and ClearPath are registered trademarks and e-@ction is a trademark of Unisys Corporation. 

All other marks are acknowledged to be the trademarks or registered trademarks of their respective owners. Unisys 

Corporation cannot attest to the accuracy of this information.



Servers 


Installation and 

Configuration Guide 


ClearPath 

Enterprise Servers 

ClearPath IX 

Systems 

Installation and 

Configuration 

Guide 

7850 5104–009 7850 5104–009 

Bend here, peel upwards and apply to spine.

Format these characters as “white” to force printing of 

blank page.

Contents 

About This Guide ....................................................................................... xxi 

Section 1. Introduction and Installation Overview 

1.1. New Features and Software for This Release ........... 1–1 

1.2. CSR Installation Overview ......................................... 1–2 

1.2.1. Main Components ................................................ 1–2 

1.2.2. Installation Procedure Overview ............................. 1–5 

Hardware and Plateau Software Installation .... 1–5 

2200 Node Hardware Verification ................. 1–6 

Intel Node Software Installation ..................... 1–7 

SPO Server Software Installation ................... 1–7 

SPO Workstation Software Installation ........... 1–7 

Configuration of Intel Nodes for Monitoring by 

SPO ....................................................... 1–7 

2200 Node Software Installation ................... 1–8 

Verifying Interconnect Communications and 

Achieving Hardware RFU .......................... 1–8 

Installing the Remaining IOE .......................... 1–8 

Customizing the Site .................................... 1–8 

1.3. Overview of Multinode Installation and Configuration 

Procedures ............................................................ 1–9 

1.3.1. Resilient 2200 Nodes ........................................... 1–9 

1.3.2. Single or Multiple OS 2200 Nodes with Multiple Intel 

Nodes ............................................................. 1–9 

Section 2. Installation Checklists and Tips 

2.1. Preinstallation Checklist ............................................ 2–1 

2.2. Installation Checklists ............................................... 2–2 

2.3. Installation Tips ......................................................... 2–7 

2.3.1. Hardware Tips ..................................................... 2–7 

Recovering from a RAID Subsystem Problem . 2–7 

Recovering from a PING Test Failure ............. 2–8 

2.3.2. Software Tips ...................................................... 2–8 

Creating Emergency Recovery Diskettes ....... 2–8 

7850 5104–009 Version 009B (Web Only) iii

Contents 

Performing a Full Installation When Software Is 

Preloaded or Preinstalled ......................... 2–8 

Finding Correct UnixWare and EBRS License 

Information .............................................. 2–9 

Configuring OS 2200 Print Queues ................ 2–9 

Installing a Windows Node as a PDC or BDC ... 2–9 

Changing SPO Aliases .................................. 2–10 

Configuring CMS 1100 ................................. 2–10 

Changing Passwords Following Installation ..... 2–10 

Modifying Windows NT/2000 Server Network 

Settings after Installation .......................... 2–10 

2.4. Additional Site Requirements .................................... 2–10 

2.4.1. DEPCON Workstation Requirements ....................... 2–11 

2.4.2. Planning for ClearPath IX Server Installation as a 

Private Network ............................................... 2–11 

2.4.3. Integrating with an Existing SPO Server .................. 2–13 

2.5. Configuring and Using the Monitor Concentrator ..... 2–14 

2.5.1. Configuring the Monitor Concentrator .................... 2–14 

2.5.2. Using the Monitor Concentrator ............................. 2–15 

Section 3. Installing Windows 2000 Advanced Server 

(ES5044R, ES5085R, and ES2024R) 

3.1. Determining Whether Software Is Preloaded ............ 3–3 

3.2. Steps to Take If Windows 2000 Advanced Is 

Preloaded .............................................................. 3–6 

3.3. Configuring the RAID Controller ................................ 3–13 

3.4. Installing and Configuring Windows 2000 Advanced 

Server .................................................................... 3–16 

3.4.1. Installing the Windows 2000 Advanced Server 

Operating System ............................................ 3–16 

3.4.2. Configuring Windows 2000 Advanced Server .......... 3–19 

3.5. Logging On As the Administrator .............................. 3–28 

Section 4. Installing Windows NT Server, Enterprise Edition 

(ES5044R, ES5085R, and ES2024R) 


4.2. Steps to Take If Windows NT Is Preloaded ................ 4–6 


iv Version 009B (Web Only) 7850 5104–009

Contents 

4.4. Installing and Configuring Windows NT Server, 

Enterprise Edition .................................................. 4–13 

4.4.1. Installing the Windows NT Server, Enterprise Edition 


4.4.2. Configuring Windows NT Server, Enterprise Edition . 4–18 


Section 5. Installing Windows NT Server, Enterprise Edition 

(ES2045R) 



5.3. Configuring the RAID Controller ............................... 5–9 


Enterprise Edition .................................................. 5–14 



5.4.2. Configuring Windows NT Server, Enterprise Edition . 5–18 


Section 6. Installing Windows NT Server 4.0 (DR/2) 



6.3. Configuring the RAID Controller ............................... 6–9 

6.4. Installing and Configuring Windows NT Server 4.0 .. 6–12 

6.4.1. Installing the Windows NT Server 4.0 Operating 

System ........................................................... 6–12 

6.4.2. Configuring Windows NT Server 4.0 ...................... 6–15 


Section 7. Completing Windows Installation 

7.1. Completing Windows NT Installation ......................... 7–3 

7.1.1. Installing Service Pack 3 for Windows NT (Full Install 

Only) ............................................................... 7–4 

7.1.2. Installing the Unisys Hardware Monitor (DR/2 Only) . 7–5 

7.1.3. Configuring ClearPath Networking ......................... 7–6 

7.1.4. Configuring the Number of Client Licenses ............. 7–6 

7.1.5. Installing and Configuring RAID Utility Software ....... 7–7 

7850 5104–009 Version 009B (Web Only) v

Contents 

Installing and Configuring RAID for a DR/2 

Node ...................................................... 7–7 

Installing and Configuring RAID for an 

ES5044R, ES5085R, ES2045R, or 

ES2024R Node ....................................... 7–8 

7.1.6. Installing and Configuring Video Drivers (Full Install 

Only) ............................................................... 7–9 

7.1.7. Installing Internet Explorer (Full Install Only) ............. 7–10 

7.1.8. Installing the Active Server Pages Upgrade for IIS 

(ES2045R, ES5085R, or ES2024R) ................... 7–11 

7.1.9. Installing and Configuring ControlIT ........................ 7–12 

7.1.10. Configuring the Tape Drive ................................... 7–14 

7.1.11. Setting Balanced Server Priorities ......................... 7–15 

7.1.12. Configuring the FTP Service ................................. 7–15 

7.1.13. Enabling the Guest Account .................................. 7–16 

7.1.14. Creating a Logical F: Drive ................................... 7–16 

7.1.15. Reapplying the Latest Service Pack ...................... 7–17 

7.1.16. Installing ess Software .......................................... 7–19 

7.1.17. Creating an Emergency Repair Disk ....................... 7–19 

7.2. Completing Windows 2000 Installation ..................... 7–19 

7.2.1. Configuring ClearPath Networking ......................... 7–20 

7.2.2. Configuring the Number of Client Licenses ............. 7–20 

7.2.3. Installing and Configuring RAID Utility Software ....... 7–21 

7.2.4. Installing and Configuring ControlIT ........................ 7–22 

7.2.5. Configuring the FTP Service .................................. 7–24 

7.2.6. Enabling the Guest Account ................................... 7–24 

7.2.7. Creating a Logical F: Drive .................................... 7–25 

7.2.8. Installing ess Software .......................................... 7–26 

7.2.9. Installing the Service Pack .................................... 7–26 

7.2.10. Creating an Emergency Repair Disk ....................... 7–26 

Section 8. Installing UnixWare 7 


8.2. Steps to Take If Software Is Preloaded ..................... 8–5 

8.2.1. Entering the License ............................................. 8–5 

8.2.2. Changing the Host Name ...................................... 8–5 

8.2.3. Changing the Date and Time Zone ......................... 8–6 


8.3.1. Load DACCF Utilities ............................................. 8–7 

Loading DACCF Utilities on an ES2045R or 

DR/2 Node .............................................. 8–7 

Loading DACCF Utilities on an ES2085R 

Node ...................................................... 8–7 

8.3.2. Complete the RAID Configuration ........................... 8–7 

Procedure for the ES2045R and DR/2 

Nodes ..................................................... 8–7 

Procedure for the ES2085R Node ................. 8–13 

vi Version 009B (Web Only) 7850 5104–009

Contents 

8.4. Installing the UnixWare 7 Operating System ............ 8–16 

8.4.1. Installing the Operating System ............................. 8–16 

8.4.2. Installing the UnixWare and Open Server 

Development Kit (UDK) ..................................... 8–21 

8.4.3. Installing the Drivers Updates ................................ 8–23 

8.5. Granting User Privileges ........................................... 8–24 

8.6. Configuring the Network Adapter ............................. 8–24 

8.6.1. Configuring the Ethernet and FDDI Network 

Adapters ......................................................... 8–24 

8.6.2. Configuring a Domain Name Service Client ............. 8–25 

8.7. Setting Up the Documentation Search Engine .......... 8–26 

8.8. Installing and Running the Tuning Script (Site- 

Installed UnixWare) ............................................... 8–26 

8.9. Retrieving and Applying Fixes ................................... 8–29 

8.10. Configuring Internet FastStart .................................. 8–29 

8.11. Logging On to UnixWare ........................................... 8–30 

8.11.1. Logging On As the Root User (Superuser) .............. 8–30 

8.11.2. Switching Windows .............................................. 8–30 

8.12. Creating and Using UnixWare Emergency Recovery 

Diskettes ............................................................... 8–30 

8.12.1. Creating the Emergency Recovery Diskettes .......... 8–31 

8.12.2. Booting from the Emergency Recovery Diskettes .... 8–32 

Section 9. Installing the ClearPath IX Customer Web Site 

Section 10. Installing SPO Basic Edition and Related Software 

10.1. Overview of Installing the Operating System and 

SPO Basic Edition Software .................................. 10–3 

10.2. Determining Whether Software Is Preinstalled ......... 10–4 

10.3. Steps to Take If Software Is Preinstalled .................. 10–4 

10.3.1. Entering the License ............................................ 10–4 

10.3.2. Changing the Host Name ...................................... 10–5 

10.3.3. Modifying the Hosts File ........................................ 10–5 

10.3.4. Changing the Date and Time Zone ......................... 10–6 

10.4. Installing UnixWare 7.1.1 on the SPO Server ........... 10–7 

10.5. Installing the UnixWare Platform Support Kit (PSK) . 10–13 

7850 5104–009 Version 009B (Web Only) vii

Contents 

10.6. Retrieving and Applying Additional Fixes .................. 10–13 

10.7. Setting Up the Documentation Search Engine .......... 10–14 

10.8. Configuring the SPO Server ...................................... 10–14 

10.9. Creating UnixWare Emergency Recovery Diskettes . 10–16 

10.10. Installing the Multiport Card Driver ........................... 10–17 

10.11. Installing SPO Basic Edition Software ....................... 10–19 

10.12. Creating a 2200 Console Hosts File Diskette ........... 10–20 

10.13. Copying the Hosts File to 2200 System Consoles .... 10–20 

10.14. Installing and Activating the AMS Database on the 

2200 System Console ........................................... 10–24 

10.14.1. Remotely Installing the AMS Database from the 

SPO Server ..................................................... 10–24 

10.14.2. Activating the SPO AMS Database at the 2200 

System Consoles ............................................. 10–26 

10.14.3. Changing the Start-Up Session to Systems 

Operations at the System Consoles ................... 10–26 

10.15. Logging On to UnixWare ............................................ 10–28 

10.15.1. Switching Windows .............................................. 10–28 

10.15.2. Logging On As the Root User (Superuser) in 

Graphical Mode ................................................ 10–28 

10.15.3. Logging On As the Root User (Superuser) in 

Character Mode ............................................... 10–28 

10.16. Stopping and Starting the SPO Daemons ................. 10–29 

Section 11. Installing and Configuring SPO Workstation 

Software 

11.1. Preparing the SPO Workstation for Use .................... 11–1 

11.2. Installing and Configuring Windows NT Workstation . 11–8 

11.2.1. Installing Windows NT on the Workstation ............... 11–8 

11.2.2. Configuring Windows NT on the Workstation ........... 11–9 

11.3. Installing Network Services on the Windows NT 

Workstation ........................................................... 11–14 

11.4. Installing the Latest Service Pack for Windows NT 

Workstation 4.0 ..................................................... 11–15 

11.5. Installing Y2K Service Packs on the Windows NT 

Workstation ........................................................... 11–16 

viii Version 009B (Web Only) 7850 5104–009

Contents 

11.6. Configuring the FTP Service on the Windows NT 

Workstation ........................................................... 11–17 

11.7. Installing the Video Driver on the Windows NT 

Workstation ........................................................... 11–18 

11.8. Installing SPO Display Software on the Windows NT 

Workstation ........................................................... 11–19 

11.8.1. Installing and Configuring XVision on the Windows 

NT Workstation ................................................ 11–19 

Copying SPO Basic Edition Fonts .................. 11–21 

Installing SPO Basic Edition Fonts in XVision ... 11–22 

Configuring XVision Display, Server, and 

Security Properties .................................. 11–22 

11.8.2. Installing ControlIT on the Windows NT 

Workstation ..................................................... 11–23 

11.8.3. Installing Winsock RSHD/NT on the Windows NT 

Workstation ..................................................... 11–25 

11.9. Setting Up the Windows 2000 Workstation If 

Windows Is Preloaded ........................................... 11–26 

11.10. Installing Windows 2000 on the SPO Workstation .... 11–26 

11.11. Configuring Display Properties on the Windows 

2000 Workstation ................................................. 11–28 

11.12. Installing and Configuring Internet Information 

Services on the Windows 2000 Workstation ......... 11–29 

11.13. Installing SPO Display Software on the Windows 

2000 Workstation ................................................. 11–30 

11.13.1. Installing and Configuring XVision on the Windows 

2000 Workstation ............................................ 11–30 

Copying SPO Basic Edition Fonts .................. 11–31 

Installing SPO Basic Edition Fonts in XVision ... 11–33 

Configuring XVision Display, Server, and 

Security Properties .................................. 11–33 

11.13.2. Installing ControlIT on the Windows 2000 

Workstation ..................................................... 11–34 

11.13.3. Installing Winsock RSHD/NT on the Windows 2000 

Workstation ..................................................... 11–36 

11.14. Installing SPO Product Information on the 

Workstation ........................................................... 11–37 

11.15. Logging On to the Windows Workstation .................. 11–39 

11.15.1. Logging On to the Windows 2000 (Professional) 

Workstation as the Administrator ....................... 11–39 

11.15.2. Logging On to the Windows NT Workstation as the 

Administrator ................................................... 11–39 

11.15.3. Changing the Default Windows Password .............. 11–40 

7850 5104–009 Version 009B (Web Only) ix

Contents 

Section 12. Configuring Intel Nodes for Monitoring by SPO 

12.1. Starting the Single Point Configuration Routine ....... 12–1 

12.2. Creating a Custom SPO Basic Edition 

Configuration ......................................................... 12–2 

12.3. Configuring and Installing the URM Agent for the 

SPO Server and UnixWare Nodes ......................... 12–4 

12.4. Transferring the SPO Windows Agent ....................... 12–6 

12.5. Configuring Windows Intel Nodes for ControlIT ......... 12–7 

12.6. Exiting from the Single Point Configuration Routine . 12–8 

12.7. Starting Normal SPO Console Operations ................. 12–8 

12.8. Installing the SPO Windows Agent ............................. 12–11 

12.9. Running the Console Output Redirection Script ........ 12–12 

Section 13. Installing the Basic OS 2200 IOE 

13.1. Read-and-Reply Message Format ............................. 13–2 

13.2. Performing the Initial Boot ........................................ 13–3 

13.2.1. Initial Boot Steps If Boot Partition Is Not Activated ... 13–3 

13.2.2. Initial Boot Steps If Partition Is Up and Exec Is 

Running ........................................................... 13–4 

13.2.3. Completing the Boot Procedure ............................. 13–4 

13.3. Installing Products from Tape HMP-FLD ................... 13–6 

13.4. Establishing the Performance Level (IX6000, 

IX5000, and IX4800 Servers Only) ....................... 13–7 

13.5. Installing Products from Tape HMP-OE1 ................... 13–9 

Section 14. Verifying the Interconnects and Achieving 

Hardware RFU 

14.1. Verifying Interconnect Communications ................... 14–2 

14.2. Installing Microcode .................................................. 14–2 

14.2.1. Installing HLC-2 Microcode .................................... 14–3 

14.2.2. Installing Channel Adapter Microcode (CSIOP) ......... 14–4 

14.3. Installing the CC or CEC Tape ................................... 14–6 

x Version 009B (Web Only) 7850 5104–009

Contents 

14.4. Installing DSPER ........................................................ 14–7 

14.5. Preparing for Communications Verification .............. 14–8 

14.5.1. Starting the PING Run ........................................... 14–9 

14.5.2. Bringing Up CMS 1100 ........................................ 14–9 

The CMS-SETUP Run .................................... 14–10 

A Minimum CMS 1100 Configuration ............. 14–10 

Running CMS-SETUP .................................... 14–11 

Starting CMS 1100 ...................................... 14–14 

Using CMS 1100 in Verifying Hardware 

Communications (If Not Yet Done) ............. 14–15 

14.6. Running the PING Test to Verify Hardware 

Communications ................................................... 14–15 

14.7. Achieving Hardware RFU ........................................... 14–16 

Section 15. Installing the Remaining IOE Software 

15.1. Remaining IOE Products ........................................... 15–1 

15.2. Installing Default UDS Application Group 3 from 

Fast-Load Tapes .................................................... 15–1 

15.2.1. Installing TIPUTIL, MCB, and DPS from Fast-Load 

Tape HMP-OE2 ................................................ 15–2 

15.2.2. Setting Up the TIP Environment ............................. 15–3 

15.2.3. Setting Up Application Group 3 ............................. 15–4 

15.2.4. Installing UDS Application Group 3 from Fast-Load 

Tape HMP-UDS3 .............................................. 15–5 

15.3. Installing Integration Expert ...................................... 15–7 

Section 16. Customizing the Site 

16.1. About Using Integration Expert ................................. 16–1 

16.2. Customizing CMS 1100 ............................................ 16–2 

16.3. Considerations for the IX Network Identity 

Repository ............................................................. 16–3 

16.3.1. Configuring CMS 1100 for the IX Network Identity 

Repository ...................................................... 16–3 

16.3.2. Preparing to Access the IX Network Identity 

Repository: IXNAGX ......................................... 16–4 

16.3.3. Updating the ClearPath HMP IX Network Identity 

Repository ...................................................... 16–4 

16.4. Optional IOE Products ............................................... 16–5 

16.5. Modifying SPO Basic Edition Configurations ............. 16–6 

7850 5104–009 Version 009B (Web Only) xi

Contents 

16.5.1. Removing the URM Agents .................................... 16–6 

16.5.2. Editing the Hosts Files to Reflect New Node 

Names ............................................................ 16–7 

16.5.3. Copying the Modified SPO Server Hosts File to the 

System Consoles ............................................. 16–9 

Copying the Modified File to Diskette ............. 16–9 

Loading the Hosts File to a System Console ... 16–9 

16.5.4. Changing a Windows 2000 or Windows NT 

Representation Using the Rename Script ............ 16–11 

16.5.5. Changing a Representation Using the Single Point 

Configuration Routine ....................................... 16–12 

16.5.6. Reinstalling the URM Agents (UnixWare Nodes 

Only) ............................................................... 16–15 

16.6. Testing TCP/IP Communications ............................... 16–18 

16.7. Installing Optional UnixWare Products ...................... 16–18 

16.8. Repartitioning the UnixWare Node ............................ 16–19 

16.9. Configuring Resilient Partitions (2200 Node) ........... 16–19 

Section 17. Installing Optional OS 2200 Software from the 

Package Tapes 

17.1. Registering the OS 2200 Product Key Tape ............. 17–1 

17.2. Product Installation Documentation .......................... 17–2 

Appendix A. Tables of Documentation, Support, and Migration 

A.1. Matrix of ClearPath Components and ICG Release 

Levels .................................................................... A–1 

A.2. Intel Environment Overview ....................................... A–6 

A.3. Hardware Migration Requirements ........................... A–8 

Appendix B. Communication Settings Specific to ClearPath IX 

Appendix C. SPO/HMP IX Interface License Key Registration 

C.1. How to Obtain a Permanent Key ............................... C–2 

C.2. Upgrades to Single Point Operations Console .......... C–2 

C.3. Permanent Key Request Form .................................. C–2 

xii Version 009B (Web Only) 7850 5104–009

Appendix D. Configuring the FDDI Interconnect 

Contents 

D.1. Configuring 2200 Node FDDI Connections ............... D–1 

D.1.1. IX4400 Server Configuration (HLC2) ...................... D–2 

D.1.2. IX5000 Series or IX4800 Server Configuration ....... D–5 

D.2. Configuring UnixWare Node FDDI Interconnects ...... D–6 

Appendix E. Installing OPE and SysAdmin 

Glossary ....................................................................................................... 1 

Bibliography ............................................................................................... 1 

Index ............................................................................................................. 1 

7850 5104–009 Version 009B (Web Only) xiii

Contents 

xiv Version 009B (Web Only) 7850 5104–009

Figures 

1–1. ClearPath IX Server Configuration ........................................................... 1–4 

1–2. Installation Process Overview ................................................................. 1–6 

1–3. Single OS 2200 Node with Multiple Intel Nodes (Up to Four) ..................... 1–10 

1–4. Multiple OS 2200 Nodes with Multiple Intel Nodes .................................... 1–11 

2–1. Example Use of LAN Addresses for the External Network (Recommended 

Only for Sites without an Existing Network) .......................................... 2–12 

2–2. Example of Monitor Concentrator Port Name Assignments ....................... 2–15 

5–1. Easy Configuration—ARRAY SELECTION MENU ........................................ 5–11 

5–2. Logical Drives Configured Screen ........................................................... 5–12 

6–1. Windows NT Server Setup (DR/2) ........................................................... 6–14 

8–1. ES2045R and DR/2 Drive Matrix ............................................................ 8–9 

10–1. Possible Intel Node Connections (with UnixWare) to the SPO Server ........... 10–17 

10–2. System Console F3 Utilities Session Menu ............................................... 10–21 

10–3. Single Point Interface Utility Session Window ........................................... 10–21 

10–4. Specify Load Diskette Menu ................................................................... 10–22 

10–5. Add Router Information Window .............................................................. 10–23 

10–6. System Console F3 Utilities Dynamic Configuration Menu ......................... 10–27 

11–1. SPO Monitoring and Control Software Components .................................. 11–3 

12–1. Maintain UNIX Agents Window ................................................................. 12–4 

12–2. URM Policies Window ............................................................................. 12–4 

12–3. SPO Basic Edition Main Menu ................................................................. 12–10 

12–4. SPO Basic Edition TopCluster Window (Four OS 2200 Nodes, Four 

Windows NT Intel Nodes, and a Single UnixWare Node) ........................ 12–10 

16–1. Resilient Configurations ......................................................................... 16–20 

7850 5104–009 Version 009B (Web Only) xv

Figures 

xvi Version 009B (Web Only) 7850 5104–009

Tables 

1–1. Operating System Levels and Installation Procedures ............................... 1–1 

1–2. ClearPath IX Server Components ............................................................ 1–2 

2–1. General Installation Information ............................................................... 2–3 

2–2. Network Names, Addresses, and Mask Values ......................................... 2–5 

2–3. Location of Correct License Information .................................................. 2–9 

2–4. Example Use of LAN Addresses for the External Network (Recommended 

Only for Sites without an Existing Network) .......................................... 2–13 

3–1. Windows 2000 Advanced Server: ES5044R, ES5085R, and ES2024R 

Installation Checklist .......................................................................... 3–2 

4–1. Windows NT Server, Enterprise Edition: ES5044R, ES5085R, and 

ES2024R Installation Checklist ........................................................... 4–2 

5–1. Windows NT Server, Enterprise Edition ES2045R Installation Checklist ...... 5–2 

6–1. Windows NT Server 4.0 Installation Checklist ........................................... 6–2 

7–1. Checklist for Completing Windows NT Installation ..................................... 7–1 

8–1. UnixWare 7 Installation Checklist ............................................................. 8–2 

10–1. SPO Basic Edition and Related Software Installation Checklist ................... 10–2 

10–2. Boot Disk (Disk 0) Required Configuration Values .................................... 10–7 

11–1. SPO Workstation Installation Checklist ..................................................... 11–4 

13–1. OS 2200 Installation Checklist ................................................................ 13–2 

14–1. Checklist for Verifying Interconnects and Achieving RFU ........................... 14–1 

A–1. ClearPath Components and ICG Release Levels ....................................... A–2 

A–2. Server Platforms Versus Operating Systems ............................................ A–6 

A–3. Hardware Migration Requirements .......................................................... A–8 

B–1. IP Addresses and Host Names Used by the Private FDDI Interconnect ....... B–1 

B–2. TSAM Configuration Assignments ........................................................... B–3 

7850 5104–009 Version 009B (Web Only) xvii

Tables 

xviii Version 009B (Web Only) 7850 5104–009

Examples 

14–1. A Minimum CMS 1100 Configuration ....................................................... 14–11 

16–1. SPO Server Hosts File Format before Editing ........................................... 16–8 

16–2. UnixWare Node Hosts File Format before Editing ...................................... 16–8 

16–3. SPO Server Hosts File Format after Editing .............................................. 16–8 

16–4. UnixWare Node Hosts File Format after Editing ........................................ 16–9 

B–1. Default Hosts File for UnixWare Nodes and OPE ....................................... B–4 

7850 5104–009 Version 009B (Web Only) xix

Examples 

xx Version 009B (Web Only) 7850 5104–009

About This Guide 

Purpose 

Scope 

This guide (previously titled ClearPath HMP IX Series Installation and Configuration 

Guide) summarizes how to install, configure, and activate the Integrated Operating 

Environment (IOE) software for a Unisys e-@ction ClearPath Enterprise Server IX. 

Note: This guide contains all information available at the time of publication. The 

most recent version of this document is provided in PDF format at this Web site: 

http://public.support.unisys.com/os1/txt/web-verity?type=list 

Technical corrections not yet incorporated into the Web update are available in 

problem list entry (PLE) 17506285. This PLE will be updated as necessary to 

reflect the rapid rate of change for Intel configurations. Please monitor the PLE 

for the most recent information. Your Unisys representative can provide you 

with a copy of the PLE. 

This guide describes how to install and configure the following software: 

• These operating systems, on Intel nodes of a ClearPath IX server: 

− Windows 2000 Advanced Server 

− Windows NT Server 4.0 

− Windows NT Server, 4.0 Enterprise Edition 

− SCO UnixWare 7 

• OS 2200 and related IOE software on 2200 nodes 

• Single Point Operations Basic Edition for ClearPath IX and related display and control 

software that allows full control and monitoring of nodes from a single workstation 

Certain Unisys product names have changed, and the new names appear throughout this 

guide. These are the name changes: 

Previous Name New Name 

Open Application Development Environment 

(OADE) 

PathMate Integration Expert 

Programmer’s Workbench for ClearPath OS 

2200 

continued 

7850 5104–009 Version 009B (Web Only) xxi


Previous Name New Name 

SPO/HMP Console Single Point Operations Basic Edition for 

ClearPath IX, also known by short name Basic 

Edition 

SPO Console or SPO/ESE Console Single Point Operations Console 

Unisys Repository Manager—Workstation Repository Workstation 

WebTx Transaction Integrator 

Audience 

In 2000, Unisys began offering several IX5600 Series and IX6600 Series entry-level systems. 

These systems may or may not include Intel server nodes or SPO servers. Depending on 

which entry-level system is delivered, sections of this book that document the installation 

of these servers and associated software are not applicable and should be ignored. 

This guide also provides overviews of site preparation requirements and hardware and 

software installation tips and checklists to aid in successful software installation. 

The goal of these procedures is to achieve hardware ready for use (RFU), so that the client 

can begin customizing the software for the site. Instructions for installing and using 

Integration Expert software are provided to aid in further customization. 

To successfully install and customize optional software, sites may need many documents 

in the ClearPath IX server product libraries. Most documents are available electronically 

from the ClearPath HMP IX Server Information Web Site or on CD-ROM. Refer to 

ClearPath Enterprise Servers Getting Started Guide for details about product 

documentation. 

Note: For initial installation, installation procedures in this guide replace procedures 

in Windows NT Server and UnixWare operating system documents. 

The audience for this document includes Unisys customer support representatives (CSR) 

or service providers who install, configure, and make operational a ClearPath IX server. 

Site administrators or other personnel at the site also need this document when installing 

new levels of software. 

Prerequisites 

Some knowledge of OS 2200, Windows NT (if applicable), and UnixWare operating system 

installation, configuration, and operation is helpful. 

Before reading this overview, you should read the ClearPath Enterprise Servers Getting 

Started Guide. 

xxii Version 009B (Web Only) 7850 5104–009

How to Use This Guide 


Section 1 provides a list of new features and software levels for this release and an 

overview of the entire installation process. Read this before beginning. 

Section 2 provides essential checklists that must be completed before beginning. It also 

provides installation notes that should be read. 

To install an operating system on the Intel nodes of a ClearPath IX system: 

• Read Section 3 plus Section 7 when installing Windows 2000 Advanced on an Intel 

node. 

• Read Section 4, 5, or 6 plus Section 7 when installing Windows NT on an Intel node. 

• Read Section 8 when installing UnixWare 7.1.1. 

Other sections apply to all sites except as noted. 

Organization 

This guide is organized as follows: 

Section 1. Introduction and Installation Overview 

This section lists new features and software levels for this release. It also provides an 

overview of the entire installation process. 

Section 2. Installation Checklists and Tips 

This section provides a preinstallation checklist, installation checklist, set of installation 

tips, description of additional site requirements, and procedure for configuring and using 

the monitor concentrator. 

Section 3. Installing Windows 2000 Advanced Server (ES5085R and ES2024R) 

This section describes how to configure the RAID controller and install and configure 

Windows 2000 Advanced Server and related IOE software on an ES5085R or ES2024R Intel 

node. 

Section 4. Installing Windows NT, Enterprise Edition (ES5085R and ES2024R) 

This section describes how to configure the redundant array of independent disks (RAID) 

controller and install and configure Windows NT Server, Enterprise Edition and related 

IOE software on an ES5085R or ES5024R Intel node. 

Section 5. Installing Windows NT, Enterprise Edition (ES2045R) 


Windows NT Server, Enterprise Edition and related IOE software on an Aquanta ES2045R 

Intel node. 

7850 5104–009 Version 009B (Web Only) xxiii


Section 6. Installing Windows NT Server 4.0 (DR/2) 


Windows NT Server 4.0 and related IOE software on an Aquanta DR/2 Intel node. 

Section 7. Completing Windows Installation 

This section describes the final steps for completing installation of Windows NT or 

Windows 2000 on the Intel node. 

Section 8. Installing UnixWare 7 

This section describes how to configure the RAID controller. It also describes how to 

install and configure UnixWare and related IOE software on Intel nodes. 

Section 9. Installing the ClearPath IX Customer Web Site 

This section describes how to install the Web-enabled documentation for the ClearPath IX 

Series servers on a Windows 2000, Windows NT, or UnixWare node. 

Section 10. Installing SPO Basic Edition and Related Software 

This section describes how to install the UnixWare operating system and related Single 

Point Operations Basic Edition for ClearPath IX software on the SPO server. It also 

describes how to copy the hosts file and Autoaction Message System (AMS) database to 

the 2200 node system consoles and how to activate the AMS database. 

Section 11. Installing and Configuring SPO Workstation Software 

If your SPO workstation is a PC running Windows NT, this section describes procedures 

for installing and configuring SPO workstation software, including the Windows 2000 

Professional Workstation operating system, the Windows NT Workstation operating 

system, and the Single Point Operations Basic Edition for ClearPath IX display software. 

Section 12. Configuring Intel Nodes for Monitoring by SPO 

This section describes procedures for configuring and installing agents to enable 

monitoring and control of the Windows NT and UnixWare nodes from Single Point 

Operations Basic Edition for ClearPath IX. 

Section 13. Installing the Basic OS 2200 IOE 

This section describes how to install the basic OS 2200 IOE software from fast-load tape. 

This is the minimum set of 2200 node software required to achieve hardware ready for use 

(RFU). 

Section 14. Verifying the Interconnects and Achieving Hardware RFU 

This section describes how to install microcode and achieve hardware RFU by verifying 

communication through the internal interconnects. 

xxiv Version 009B (Web Only) 7850 5104–009


Section 15. Installing the Remaining IOE Software 

Procedures in this section are performed by site personnel after hardware RFU. This 

section describes how to install the remaining IOE software, including OS 2200 server and 

Windows workstation software. 

Section 16. Customizing the Site 


section describes how to use Integration Expert to configure other software or to create 

and populate the IX Network Identity Repository. It also describes how to perform TCP/IP 

communications tests, how to customize SPO Basic Edition configurations, and how to 

configure resilient partitions. 

Section 17. Installing Optional OS 2200 Software from the Package Tapes 


section describes how to register the key tape and points to documentation for installing 

more optional products. 

Appendix A. Tables of Documentation, Support, and Migration 

The tables in this appendix do the following: 

• Relate ClearPath components to the levels of the ClearPath IX Installation and 

Configuration Guide in which they are documented (Table A–1) 

• Summarize the supported combinations of software and Intel processors (Table A–2) 

• Summarize the hardware migration requirements for moving from an HMP IX 4.0 

server to an HMP IX 5.0 operating system (Table A–3) 

Appendix B. Communication Settings Specific to ClearPath IX 

This appendix describes required private FDDI interconnect IP addresses and names, and 

TSAM configuration values used by the internal network of the server. 

Appendix C. SPO/HMP IX Interface License Key Registration 

This appendix contains the form used by Single Point Operations Console (formerly known 

as SPO/ESE) sites to request the permanent software license key needed to manage the 

server using Single Point Operations Console software. 

Appendix D. Configuring the FDDI Interconnect 

This appendix explains how to create the fiber distributed data interchange (FDDI) 

interconnect configuration in the Site Configuration Management System (SCMS) database 

if it must be re-created for some reason. The database is provided prebuilt from the 

factory so this should not be necessary. 

Appendix E. Installing OPE and SysAdmin 

This appendix explains how to install Open Programming Environment (OPE) and 

SysAdmin, two optional IOE products that are provided with the ClearPath system. 

7850 5104–009 Version 009B (Web Only) xxv


Related Product Information 

The following documents are relevant to installing your ClearPath system. The current 

version of each document is available on the Web at one of these sites: 

http://public.support.unisys.com/a-s/txt/web-verity?collection=ixins&pla=os1 

http://www.support.unisys.com/OS1/TXT/OS1-DOC?PLA=OS1 

Unisys e-@ction ClearPath Enterprise Servers ClearPath HMP IX and 2200 

Systems Software Planning and Migration Overview (7831 0349) 

Previous title: ClearPath HMP IX Series and 2200 Series Software Planning and 

Migration Overview 

This overview describes how to migrate to the ClearPath HMP IX release from earlier 

releases. 

ClearPath HMP IX Series and OS 2200 Product Information CD-ROM (7848 

4482) 

This CD-ROM contains electronic ready-to-print versions of ClearPath HMP IX 


Unisys e-@ction ClearPath Enterprise Servers Conceptual Overview (7848 4052) 

Previous title: ClearPath HMP IX Series Conceptual Overview 

This overview provides a high-level view of ClearPath HMP IX servers to help customers 

understand the key attributes of ClearPath IX servers and the key technologies used. This 

information is intended to help customers determine how ClearPath IX servers can be of 

benefit to their existing information infrastructure. 

Unisys e-@ction ClearPath Enterprise Servers Getting Started Guide (7848 

4060) 

Previous title: ClearPath HMP IX Series and OS 2200 Getting Started Guide 

This guide tells how you begin using your ClearPath HMP IX server once initial installation 

and configuration of the hardware and software have occurred. It describes what you do 

next and tells you where to go for complete information about all aspects of the system. 

ClearPath HMP IX Series Open/OLTP Pathway Installation and Operations 

Guide (7848 4409) 

This guide describes how to install and use the Pathway client software that runs on a 

Windows NT or UnixWare node of a ClearPath HMP IX server. The client software 

communicates with the Open/OLTP Transaction Manager software running on the 2200 

node of a ClearPath HMP IX server to provide a distributed transaction processing (DTP) 

environment. 

xxvi Version 009B (Web Only) 7850 5104–009


ClearPath HMP IX Series Operations Guide (7848 4094) 

This guide provides an overview of the ClearPath IX server hardware. It also describes 

how to accomplish the following tasks for each component: system start-up and shutdown, 

system reboot and recovery, partition management, and integrated operations monitoring 

and control using the SPO/HMP Console product. 

ClearPath HMP IX Series SysAdmin Administration Guide (7848 4086) 

This guide provides an overview of the system administration application, SysAdmin. It 

describes how to use SysAdmin for managing users, groups, and accounts across the 

ClearPath HMP IX environment and for managing distributed transactions across multiple 

platforms. In addition, it manages both network performance and software installation. 

ClearPath HMP IX Series Web Servers User’s Guide (7848 4458) 

This guide provides programming information for the various World Wide Web servers and 

Web support tools available on ClearPath HMP IX servers. For some products, 

configuration, administration, or installation information is also included. While this guide 

does not cover the basic principles of the Web in any detail, it does contain an extensive 

reading list of material in several languages. 

Unisys e-@ction ClearPath Web Enablement Solutions Transaction Integrator 

User’s Guide (7850 4230) 

Previous title: ClearPath HMP IX Series Web Transaction Enabler (WebTx) 

Administration Guide 

This guide is an online help system that can be viewed with any Web browser. It provides 

information on installation, configuration, and administration of WebTx software, which is 

the Web transaction server package for ClearPath HMP IX servers. WebTx works with 

Windows NT or UnixWare Web server software to provide Web access to files and 

transactional applications on ClearPath IX servers. This guide is distributed with the 

WebTx software for the Windows NT or UnixWare operating environment. 

Unisys e-@ction Web Transaction Server for ClearPath OS 2200 Administration 


Previous title: ClearPath HMP IX Series Web Transaction Server (WebTs) 

Administration Guide 

This guide provides task-oriented information to help system administrators set up Web 

Transaction Server (WebTS) software. WebTS is an OS 2200 Web server that allows 

desktop users with Web browsers to access static Web pages and transaction programs in 

the OS 2200 environment of a ClearPath HMP IX server. You use WebTS administration 

software (WebTSA) on a Windows 95 or Windows NT workstation to administer the 

WebTS server software. 

Unisys e-@ction Web Transaction Server for ClearPath OS 2200 Programming 


Previous title: ClearPath HMP IX Series Web Transaction Server (WebTs) Programming 


7850 5104–009 Version 009B (Web Only) xxvii


This guide describes the interface between a Web browser and transaction programs 

running on the ClearPath IX server. Part of this interface is a new software component, 

called WebTS. This guide describes WebTS and provides information enabling application 

programmers to develop the interface between a Web browser and the transaction 

programs. 

Unisys e-@ction ClearPath Enterprise Servers Single Point Operations Basic 

Edition for ClearPath IX Administration and Operations Overview (7846 0540) 

Previous title: ClearPath HMP IX Series SPO/HMP Console Administration and 

Operations Overview 

This overview provides operators and administrators an introduction to the use of 

SPO/HMP Console for managing the ClearPath HMP IX server. It is a prerequisite to using 

SPO/HMP Console. The overview refers to the Single Point Operations/Enterprise Server 

Edition library for detailed information about configuring, administering, and operating 

SPO/HMP Console. 

ClearPath HMP IX4400 Server Configuration Guide (7848 4334) 

This guide tells how to configure new ClearPath HMP IX4400 servers and how to upgrade 

or expand existing ClearPath HMP IX4400 servers. This guide is a companion to the 

IX4400 Server I/O Channel Assignment Planning Guide and IX4000/IX5000 Servers 

Peripheral Subsystems Configuration Guide. Use these documents together to properly 

configure the central electronics complex and peripheral subsystems for the server. 

ClearPath HMP IX4400 Server I/O Channel Assignment Planning Guide (7848 

4888) 

This guide gives configuration guidelines for the channel assignment of the various channel 

types. Other related information includes channel rack configuring, I/O channel 

characteristics, I/O performance, subsystem configuration, peripheral partitioning, and 

channel cabling. This guide assists system analysts in establishing an initial channel 

configuration assignment and in expanding existing configurations. You can use this guide 

to optimize a system configuration for best channel usage. 

Unisys e-@ction ClearPath Enterprise Servers IX5000 and IX6000 Servers 

Configuration Guide (7847 5746) 

Previous title: ClearPath HMP IX5000 and IX6000 Servers Configuration Guide 

This guide tells how to configure new ClearPath HMP IX4800 servers and how to upgrade 

or expand existing ClearPath HMP IX4800/IX5000/IX6000 servers. This guide is a 

companion to the IX4000/IX5000/IX6000 Servers Peripheral Subsystems Configuration 

Guide and IX4800/IX5000/IX5000 Servers I/O Channel Assignment Planning Guide. 

Use these documents together to properly configure the central electronics complex and 

peripheral subsystems for the server. 

ClearPath HMP IX4800/IX5000/IX6000 Servers I/O Channel Assignment 

Planning Guide (7848 4896) 

Previous title: ClearPath HMP IX4800/IX5600/IX5800 Servers I/O Channel Assignment 

Planning Guide 

xxviii Version 009B (Web Only) 7850 5104–009


This guide gives configuration guidelines for the channel assignment of the various channel 

types. Other related information includes channel rack configuring, I/O channel 

characteristics, I/O performance, subsystem configuration, peripheral partitioning, and 

channel cabling. This guide assists system analysts in establishing an initial channel 

configuration assignment and in expanding existing configurations. You can use this guide 

to optimize a system configuration for best channel usage. 

ClearPath HMP IX4000/IX5000/IX6000 Servers Peripheral Subsystems 


This guide is for Unisys ClearPath server clients who are interested in new peripheral 

subsystems or who want to upgrade or expand their current peripheral subsystems. 

The following documents contain detailed information summarized in this overview. Use 

the version that corresponds to the hardware model or level of software at your site. 

Aquanta GPS, GPS/U, GPR, and GPR/U Series Hardware User’s Guide (3816 

2293) 

This document is a reference for the SPO server hardware (GPR) in a ClearPath IX server. 

ClearPath HMP IX Series Open Programming Environment (OPE) 


This guide contains installation and configuration information for OPE. 

ClearPath HMP IX4800/IX5000/IX6000 Servers Installation and Servicing 

Reference (7842 5980) 

This reference provides information for the customer service representative (CSR) to 

install and service a ClearPath IX4800/IX5000/IX6000 heterogeneous multiprocessor (HMP) 

server. 

Unisys e-@ction ClearPath Enterprise Servers IX4800/IX5000/IX6000 Series 

Systems Plateau Customer Reference Manual (7859 5774) 

Previous title: ClearPath HMP IX6800 Series Systems Plateau Customer Reference 

Manual 

This manual describes the contents of the Unisys e-@ction ClearPath Enterprise Servers 

IX4800/IX5000/IX6000 Series systems plateau, the plateau system media, and the plateau 

installation directions. 

ClearPath 2200/3000 Series System Control Facility (SCF) Operations Guide 

(7844 8560) 

This guide describes how to load operational database (ODB) files, and boot and operate 

the 2200 node from the SCF workstation (2200 node system console). If you have a Model 

IX4400 ClearPath HMP IX server, refer to the 2200/500 System System Control Facility 

(SCF) Operations Guide (7833 3622). 

7850 5104–009 Version 009B (Web Only) xxix


ClearPath 2200/3000 Series Systems Plateau Customer Reference Manual (7847 

4145) 

This manual describes the plateau content of the 2200/3000 central electronics complex 

(CEC) and presents the system media package supporting the plateau, considerations and 

restrictions, and installation procedures. 

DEPCON Software Configuration and Operations Guide (7833 3960) 

This guide describes in detail how to install, configure, and operate DEPCON software. 

Microsoft Windows NT Server Version 4.0 Concepts and Planning (69940) 

This document describes in detail how to plan a Windows NT server domain. 

OS 1100 SX 1100 Network File System (NFS) Administrator’s Guide (7833 2392) 

The Network File System is an SX 1100 facility for sharing files among a variety of 

hardware systems and operating systems in a network. This guide describes how to 

administer NFS, including how to prepare NFS for use, make files available to remote 

users, monitor system operations, and troubleshoot problems. 

OS 2200 Communications Management System (CMS 1100) Configuration 

Reference Manual (7830 9853) 

This manual provides detailed explanations of the network definition statements used to 

configure CMS 1100. 

OS 2200 Communications Management System (CMS 1100) Installation and 


This guide describes the overall CMS 1100 installation and configuration process and 

explains the required tasks. 

OS 2200 Enterprise Backup and Restore Windows Installation and Operations 


This guide describes installation of the Enterprise Backup and Restore (EBRS) software 

workstation module. 

OS 2200 Enterprise Backup and Restore Host Installation Guide (3495 3067) 

This guide describes installation of the EBRS 2200 node software module. 

OS 2200 Enterprise Backup and Restore UNIX Server Installation and 

Operations Guide for Windows (3498 1308) 

This guide describes installation and operation of the EBRS UNIX server module, which 

runs on either SCO UnixWare or UNIX SVR4. 

xxx Version 009B (Web Only) 7850 5104–009


OS 2200 Exec System Software Installation and Configuration Guide (7830 

7915) 

This guide describes the stream generation statements needed to reconfigure the OS 2200 

Exec. 

Unisys e-@ction Application Development Solutions Programmer’s Workbench 

for ClearPath OS 2200 User Guide (7848 3989) 

Previous title: OS 2200 Open Application Development Environment (OADE) for 

Windows User Guide 

This guide describes how to install and use the OADE program development tool. 

OS 2200 Series Single Point Interface Software Installation and Configuration 


This guide explains how to install and configure the Single Point Interface software on 

each of the OS 2200 system consoles that are part of the ClearPath IX server . It also 

explains how to configure the Ethernet boards that are installed in each of the OS 2200 

system consoles. 

OS 2200 Software Library Administrator (SOLAR) End Use Reference Manual 

(7831 0604) 

This manual describes the SOLAR processor used to register and install OS 2200 software 

products. 

Unisys e-@ction ClearPath Enterprise Servers Software Products Installation 


Previous title: OS 2200 Software Products Installation Guide 

This guide describes how to install OS 2200 software products. 

OS 2200 TeamQuest Baseline Framework and TeamQuest Online User’s Guide 

(7830 7717) 

Previous title: OS 2200 TeamQuest Baseline and TeamQuest Online Administration 

and End Use Reference Manual 

This manual describes how to install and use TeamQuest Baseline and TeamQuest Online. 

Personal Workstation2 (PW2 ) Unisys Repository Workstation (UREP-WS) Use 


This guide describes how to install and use the Unisys Repository Manager (UREP) 

workstation software. 

SCO UnixWare Application Server Personal Edition (CD-ROM 2 of 2) (400-92A- 

102) 

This CD-ROM provides the SCO UnixWare operating system documentation set, which 

includes a Desktop User Handbook, system administration information, and other 

information. 

7850 5104–009 Version 009B (Web Only) xxxi


Unisys e-@ction Single Point Operations Administration and Configuration 


Previous title: Single Point Operations Console/Enterprise Server Edition 

Administration and Configuration Guide. 

This guide describes how to use the Single Point Configuration routine to create a 

configuration for Single Point Operations Console that is tailored to the specific needs of 

your data center. 

Unisys e-@ction Single Point Operations Installation Guide (7833 4075) 

Previous title: Single Point Operations Console/Enterprise Server Edition Installation 


This guide provides detailed instructions for installing and configuring Single Point 

Operations (SPO) server and console software. 

Single Point Status Operations Guide (7833 4778) 

This guide describes Single Point Status and explains how to use it to monitor the status of 

hardware and software components in your ClearPath IX server. 

Site Configuration Management System (SCMS) Administration Guide Volume 

1, Reference Information (7832 8861) 

Site Configuration Management System (SCMS) Administration Guide Volume 

2, Tutorial (7833 2434) 

These guides describe how to create and maintain configuration information for the 2200 

node using the Site Configuration Management System (SCMS). 

OSR5000 Open Systems RAID Subsystem Installation and Operations Guide 

(4487 1390) 

Previous title: Unisys OSR5000 Open Systems RAID Subsystem Installation and 

Operations Guide 

This guide provides instructions for installing, configuring, and operating the OSR5000 disk 

subsystem and related software. 

Unisys RAID Storage Subsystem NT Attachment Guide (4488 2389) 

This guide provides instructions for connecting the OSR5000 disk subsystem as a shared 

disk in a Microsoft Cluster Server (MSCS) cluster. 

UnixWare Migration Guide (7442 4185) 

This guide gives procedures for migrating from UNIX System V Release 4.0 to UnixWare. 

2200/XPA System Migration Guide (7830 9697) 

Provides information about migrating to the 2200 node of a ClearPath IX server from an 

existing 1100 or 2200 Series system. 

xxxii Version 009B (Web Only) 7850 5104–009

Notation Conventions 


To simplify and clarify procedures, the following conventions are used throughout this 

guide: 

• Bold text is used to show a sample response to a prompting message in a procedure. 

The response is shown as on the same line as the prompt. For example: 

Your system IP Address has been set to xxx.xxx.xxx.xxx 

Is that correct [y/N]: Y 

If the default value is entered, nothing is shown. 

The explanation of what you are to enter follows the prompting message and any 

sample entry. For example: 

1. You are prompted to confirm that the IP address you entered is correct. 


Is that correct [y/N]: Y 

2. Enter yes (Y) if the entry is correct. Enter no (N) if it is incorrect. 

• In addition to document titles and notes, plain italic text is used to indicate 

information that may vary. For example: 


Is that correct [y/N]: 

• Bold italic text indicates variable input. For example: 

Your system IP Address is? xxx.xxx.xxx.xxx 

If the variable input must be formatted in a certain way, as in the above example, the 

format is shown. 

7850 5104–009 Version 009B (Web Only) xxxiii


xxxiv Version 009B (Web Only) 7850 5104–009

Section 1 

Introduction and Installation Overview 

This release continues support for ClearPath IX 4000/5000/6000 servers. This introduction 

provides 

• A list of new features and software levels for this release (1.1) 

• An overview of ClearPath IX server installation procedures (1.2) 

• An overview of additional steps when installing and configuring servers with multiple 

Intel or 2200 nodes (1.3) 

1.1. New Features and Software for This Release 

Key new features for the release include 

• The e-@ction ES2024R server 

• The Windows 2000 operating system, available on the ES5085R and the ES2024R 

servers. 

The ES5085R is also available with Windows NT Enterprise Edition. The ES2085R is 

available with UnixWare 7. 

Table 1–1 identifies the operating system levels for this release and the sections where 

detailed procedures are found. See 1.2 for a brief installation overview. 

Table 1–1. Operating System Levels and Installation Procedures 

Operating System Level Node Sections 

Microsoft Windows 

2000 Advanced Server 

Microsoft Windows NT 

Server, Enterprise 

Edition 

N/A ES5085R Intel node 3, 7, 14 

N/A ES2024R Intel node 3, 7, 14 

4.0 ES5085R Intel node 4, 7, 14 

4.0 ES5044R Intel node 4, 7, 14 

4.0 ES2024R Intel node 4, 7, 14 

4.0 ES2045R Intel node 5, 7, 14 

continued 

7850 5104–009 Version 009B (Web Only) 1–1


Table 1–1. Operating System Levels and Installation Procedures 

Microsoft Windows NT 

Server 

4.0 DR/2 Intel node 6, 7, 14 

SCO UnixWare 7.1.1 ES2045R Intel node 

DR/2 Intel node 

ES2085R Intel node 

ES2024R SPO server 

Unisys OS 2200 IOE HMP IX 4.1 

or higher 

1.2. CSR Installation Overview 

This overview provides 

2.1.3 Single Point Operations server 

(DR/6) 

1–2 Version 009B (Web Only) 7850 5104–009 

8, 10 

10 

2200 node (all) 13 

• A list and brief description of main ClearPath IX server components (1.2.1) 

• An overview of the entire ClearPath IX server installation procedure (1.2.2) 

1.2.1. Main Components 

Table 1–2 describes the main ClearPath IX server hardware components (Figure 1–1). 

Table 1–2. ClearPath IX Server Components 

Component Description 

2200 node The IX 4000/5000/6000 processor that supports the OS 2200 operating 

system and related software. The 2200 node is located in the processing 

complex cabinet (PCC). 

Channel service I/O 

processor (CSIOP) 

The 2200 node channel interface that supports communication with other 

server nodes over a private interconnect (the private FDDI LAN). 

FDDI cable (internal LAN) A private FDDI LAN interconnects all nodes in the ClearPath IX server. Each 

node communicates with every other node using reserved hostnames and 

private IP addresses on this LAN (see Appendix B). 

Intel node The e-@ction server node that supports the Windows NT or UnixWare operating 

system and related software. The Intel nodes are located in the Intel processing 

complex cabinet (IPCC). 

continued

Table 1–2. ClearPath IX Server Components 

Component Description 


SCF PCs The OS 2200 system consoles, located in the console hardware cabinet, which 

are connected by a token ring network to the 2200 node. 

Single Point Operations 

server 

An Intel computer, running UnixWare, on which Single Point Operations Basic 

Edition for ClearPath IX (Basic Edition) software runs. Basic Edition, which is a 

restricted version of Single Point Operations (SPO) Console, allows the Single 

Point Operations (SPO) workstation to monitor and control all nodes of the 

ClearPath IX server. The Single Point Operations (SPO) server is located in the 

console hardware cabinet. 

Monitor concentrator An electronic switchbox that connects a single monitor, keyboard, and mouse in 

the console hardware cabinet to the Intel nodes, SPO server, and SCF PCs. The 

monitor, keyboard, and mouse provide a single operator interface to use for 

entering commands to locally operate all connected systems and to switch 

between those systems as desired. 

Serial port connection A serial port connection from an Intel node to the SPO server that is required 

when UnixWare is installed on the Intel node. The connection allows a UnixWare 

console session to be redirected to the SPO server for Basic Edition monitoring 

and control. 

Ethernet concentrator A 16-port Ethernet hub (see Figure 2–1) is provided with all ClearPath IX servers. 

The hub improves installation by concentrating all server-related Ethernet 

connections prior to connection to a site’s LAN. Only a single connection from 

the hub to the site’s production Ethernet network is then required. An AUI 

connector (on the hub) and an external transceiver are provided for connection 

to the customer LAN, which is assumed to be 10Base5 (Thick Coax) cabling. A 

secondary purpose of the hub is to standardize on 10BaseT cabling for 

connection to Ethernet ports 

SPO workstation or 

terminal 

The primary workstation from which an operator monitors and controls all nodes 

of the server. Because it is connected by Ethernet to the server, the 

workstation can be remotely located. Basic Edition screens are displayed on 

this workstation. The SPO workstation is a PC running Windows NT Workstation 

or Windows 2000 Professional Workstation and SCO XVision. 

DEPCON Workstation A site-supplied workstation on which to run DEPCON (see 2.4.1 for 

requirements). DEPCON is an enterprise print distribution and control system 

that allows distribution of print files among all nodes of the server, PCs, Novell 

NetWare print queues and servers, and other systems such as other OS 2200 

systems or A Series systems. 



1 

1 

SPO 

Workstation 

Site-Supplied 

DEPCON 

Server PC 

Production 

TCP/IP 

Network 

Ethernet Concentrator 

SCF PC 

Token 

Ring 

SCF PC 

1 Monitor, keyboard, and mouse not shown. 

SPO 

Server 

Serial Port Connection 

Console Hardware Cabinet 

VGA Monitor Cable 

Keyboard Cable 





Mouse Cable 

Processing Complex Cabinet 

2200 Nodes 

(upto2) 

Intel 

Nodes 

(upto4) 

2 Connection applies only when UnixWare is on the Intel node. 

CSIOP 

FDDI Cable (Internal LAN) 



Mouse Cable 


2 

Cluster Interconnect 

(optional) 

Figure 1–1. ClearPath IX Server Configuration 

Monitor Concentrator 

VGA Monitor 

Keyboard 

Mouse

1.2.2. Installation Procedure Overview 


This subsection briefly describes the overall ClearPath IX server installation procedure. 

Figure 1–2 illustrates the steps. The procedure identifies sections with detailed 

information. 

Hardware and Plateau Software Installation 

These are the main steps covered in this manual: 

1. Install and cable all ClearPath IX server hardware. Refer to the Unisys e-@ction 

Enterprise Servers IX4800/IX5000/IX6000 Servers Installation and Servicing 

Reference (7842 5980)for additional information. 

2. Configure the monitor concentrator (switch box). Refer to 2.5.1. 

3. Switch the monitor concentrator to the SCF master position (2.5.2), power on the SCF 

master console, and install and configure SCF workstation software. For all SCF 

software installation steps, use procedures described in the Unisys e-@ction 

ClearPath Enterprise Servers IX4800/IX5000/IX6000 Series Systems Plateau 

Customer Reference Manual (7859 5774). 

Note: While system console software is loading, you can switch the monitor 

concentrator to the Intel node position and install Windows NT or UnixWare 

IOE software (step 9). 

4. Take the following steps to load the SCMS database and operations database (ODB) 

files: 

a. Reboot the 2200 node master console in site data facility (SDF) online mode, and 

load the factory-built customer SCMS database. 

b. Reboot the master console in SCF offline mode and load the factory-built 

customer ODB files. 

c. Reboot the master console in SCF online mode. 

5. Repeat steps 3 and 4 for optional backup master SCF console. Repeat step 4 for 

optional slave SCF consoles. 

Note: Once the operating system tape has been loaded on the master system 

console, you can remove the boot diskette and tape and start loading the 

operating system tape on the next system console. 



Install the central electronics 

complex 

Install the FDDI connections 

for the internal LAN and connect 

site administraton LANs 

Install SCF workstation software 

(if not preinstalled) 

Power on 2200 Node 

and run 

diagnostic tests 

Install and configure 

Windows NT or UnixWare 

software on each Intel node 

(if not preinstalled) 

Does site 

already have 

SPO Console 

? 

Yes 

No 

Modify current configurations 

to include ClearPath HMP IX 

nodes and automation 

2200 Node Hardware Verification 

1 

Figure 1–2. Installation Process Overview 

6. Perform a 2200 node system check as follows: 

a. Power on the 2200 nodes. 

b. Run microdiagnostics. 

c. Boot and run SUMMIT. 


1 

Install and configure SPO server 

software (if not preinstalled) 

Copy SPO server hosts 

file to system consoles 

Install and configure SPO 

workstation software 

If using SPO Console, install 

temporary license key and 

submit registration form for 

permanent key. (Skip if using 

SPO Basic Edition.) 

Install SPO agents 

on Intel nodes 

Install and configure 

OS2200IOEsoftwareon 

2200 node 

Run interconnect tests to verify 

2200 node to Intel nodes 

communications 

Use Integration Expert to 

customize the configuration


7. Run SUMMIT to verify intercabinet connections. Note that the minimum level of 

CEC500 (model IX4400 is 1R8 and the minimum level of CC3000 (model IX5000 server 

or IX4800 server) is 1R1. 

8. Run the applicable FDDI LAN Test under UPTS-OS2200 interface sender to Sxxxxxxx 

receiver as follows: 

• IX4400 server—Run SRLANF 

• IX5000 server or IX4800 server—Run CALANF 

Intel Node Software Installation 

9. Install and configure the Windows NT or UnixWare operating system as follows: 

Windows 2000 Advanced Server Installation 

Install and configure Windows 2000 as described in Section 3 (Installing Windows 

2000 Advanced Server, ES5085R and ES2024R). 

Note: When installing multiple Intel nodes or multiple OS 2200 nodes, see 1.3. 

Windows NT Server Installation 

Install and configure Windows NT as described in Section 4 (Windows NT Server, 

Enterprise Edition, for ES5085R), Section 5 (Windows NT Server, Enterprise 

Edition, for ES2045R), or Section 6 (Windows NT Server 4.0, for DR/2). 

Note: When installing multiple Intel nodes or multiple OS 2200 nodes, see 1.3. 

UnixWare Installation 

Install and configure UnixWare 7 as described in Section 8. (UnixWare 7). 

10. Install and configure the ClearPath IX Customer Information Web Site as described in 

Section 9. 

Note: This step can be done at any convenient time after step 9. 

SPO Server Software Installation 

11. Sites using SPO Basic Edition install and configure Basic Edition and related software 

(Section 10). Sites using SPO Console must take the steps described in 2.4.3. 

SPO Workstation Software Installation 

12. Install and configure Windows NT Workstation, or configure Windows 2000 

Professional Workstation (which comes preloaded), at the SPO workstation as 

described in Section 11. 

Configuration of Intel Nodes for Monitoring by SPO 

13. Configure the Intel nodes for monitoring by SPO Basic Edition as described in 

Section 12. 



2200 Node Software Installation 

14. Install the basic OS 2200 IOE software on the 2200 node as described in Section 13. 

Verifying Interconnect Communications and Achieving Hardware RFU 

15. Follow the instructions in Section 14 for running the PING test to verify 

communications among nodes of the system. Once the PING test is finished, the 

hardware is considered ready for use (RFU). The CSR turns the ClearPath IX server 

over to the site. 

Installing the Remaining IOE 

16. After the customer service representative (CSR) turns the ClearPath IX server over to 

the site, site personnel may install the remaining Integrated Operating Environment 

(IOE) software as described in Section 15: 

Customizing the Site 

• Products on fast-load tapes HMP-OE2 and HMP-UDS3 

• Repository Workstation (formerly known as Unisys Repository Manager (UREP) 

Workstation) 

• Programmer’s Workbench for ClearPath OS 2200 (formerly known as Open 

Application Development Environment (OADE) for Windows) 

• TeamQuest Online 

• Remaining UnixWare IOE products: 

− Open/OLTP Pathway 

− Transaction Integrator (formerly known as WebTx) 

17. After installing the remaining IOE, the site may customize the installation as described 

in Section 16: 

Note: If you plan to use SPO Console to monitor the ClearPath IX system, refer to 

Appendix C for licensing information. 

• Use Integration Expert (formerly known as PathMate) to configure other software 

or to create and populate the IX Network Identity Repository. 

• Install optional OS 2200 software from package tapes. 

• Customize SPO Console configurations with site-specific names. 

• Edit the contents of the SPO Console configuration file to permanently change the 

default configuration. 

• Test TCP/IP communications. 

• Administer users, accounts, and groups using SysAdmin. 

• Install optional UnixWare software products (if applicable). 

• Repartition the UnixWare node. 

1–8 Version 009B (Web Only) 7850 5104–009

• Configure a resilient 2200 node partition. 


1.3. Overview of Multinode Installation and 

Configuration Procedures 

A basic (minimum) ClearPath IX server includes the following nodes: 

• A single 2200 node running a single instance of OS 2200 

• A single Intel node running a single instance of either Windows NT or UnixWare 

These nodes are connected by a private interconnect (an FDDI LAN), and they 

communicate with each other using reserved hostnames and addresses (see Appendix B). 

The following configurations beyond the basic configuration are supported: 

• Resilient 2200 nodes (1.3.1) 

• Single or multiple OS 2200 nodes with multiple Intel nodes (1.3.2) 

1.3.1. Resilient 2200 Nodes 

A single 2200 node can be partitioned into two OS 2200 nodes for resiliency. The OS 2200 

nodes operate independently of each other, but only one at a time connects to the private 

interconnect and interoperates with the Intel node. The second node backs up the first 

and interoperates with the Intel node should the first node lose its connection for some 

reason. See 16.8 for detailed information. 

1.3.2. Single or Multiple OS 2200 Nodes with Multiple Intel Nodes 

In addition to the basic configurations, a single 2200 node, configured as one OS 2200 node, 

can connect to and interoperate with up to four Intel nodes (Figure 1–3). 

Also, a single 2200 node can be configured as two OS 2200 nodes, and each of those nodes 

can connect to the four possible Intel nodes (must be the same set of Intel nodes) (Figure 

1–4). 

Note: For simplicity, only two Intel nodes are shown in Figure 1–3 and Figure 1–4. 

In either multinode configuration, each OS 2200 node connects to and interoperates with 

all of the other nodes through the private interconnect using the reserved hostnames and 

IP addresses listed in Appendix B. 

Each Intel node can be a Windows 2000, Windows NT, or UnixWare node in any 

combination. For example, all four Intel nodes could be UnixWare nodes, they all could be 

Windows NT nodes, or they could be any combination of the two (for example, one 

UnixWare node and three Windows NT nodes). 



OS 2200 Node 

2200 System 

Application 

External 

Communications 

Interface 

Private 

Interconnect 

External 


Interface 

Intel Node Client 

Application 

Intel Node Operating System 


Application 


Figure 1–3. Single OS 2200 Node with Multiple Intel Nodes (Up to Four) 


External 


Interface 

OS 2200 Node 1 

2200 System 

Application 1 

OS 2200 Node 2 

2200 System 

Application 2 

Partitioned 2200 System 


Private 

Interconnect 

External 


Interface 


Application 



Application 


Figure 1–4. Multiple OS 2200 Nodes with Multiple Intel Nodes 

Follow these steps when installing a ClearPath IX server with multiple nodes: 

1. Ensure that the factory-built customer ODB files are configured to support planned OS 

2200 node HMP configurations (Appendix D). 

2. Install the ClearPath IX server 2200 node, boot and run SUMMIT, and run the 

applicable FDDI LAN test as summarized in the CSR overview (1.2). 

3. Install the operating system IOE on the first Intel node according to the instructions in 

the applicable operating system IOE section. During installation of the operating 

system or later (such as when running a tuning script in the case of UnixWare), 

configure the following networking information: 

a. The hostname and IP address that identify the node on the private interconnect 

(see Appendix B). 

b. The hostname and IP address that identify the node on the external Ethernet 

(TCP/IP) network at the site (see 2.2). 

c. The same hostnames and IP addresses as configured for the operating system 

must be configured for network interface cards (both FDDI and Ethernet) for the 

node. 

4. Repeat step 3 for each subsequent Intel node until the operating system IOE has been 

installed on each Intel node. 



5. Install and configure SPO/HMP Console and related software as described in Section 

10. 

6. Install SPO workstation software and enable communication between the SPO 

workstation and each Intel node as described in Section 11. 

7. Configure monitored nodes as described in Section 12. 

8. Install the basic OS 2200 IOE on each OS 2200 node as described in Section 13. 

9. Before testing the private LAN interconnect as described in the next step, configure 

CMS 1100 with required IP addresses (16.2.1). 

10. Verify that the OS 2200 node or nodes can communicate with the Intel node or nodes 

by performing interconnect tests as described in Section 14. 

Install the remaining IOE and customize the site as described in Sections 15, 16, and 17. 


Section 2 

Installation Checklists and Tips 

This section provides the following: 

• Preinstallation checklist (2.1) 

• Installation checklist (2.2) 

• Set of installation tips (2.3) 

• Description of additional site requirements (2.4) 

• Procedure for configuring and using the monitor concentrator (2.5) 

2.1. Preinstallation Checklist 

Before beginning installation on any node, ensure that the site 

• Is ready for the installation and that all installation information has been obtained per 

the relevant Technical Information Bulletin (TIB). 

• Has a correct operations database (ODB) based on customer-specific configuration 

information. 

• Has planned for migration from an existing 1100 or 2200 Series system using the 

procedures in the ClearPath HMP IX and 2200 Systems Software Planning and 

Migration Overview. 

• Has planned for additional requirements as described later in this section (2.4), 

including 

− Obtaining workstation hardware required to support certain Unisys products 

(2.4.1). 

− Planning for a network if the site does not currently have one (2.4.2). 

− Planning to integrate with an existing SPO server (optional), if the site already has 

one (2.4.3). 

You should also obtain the ClearPath HMP IX installation checklist. You can print this 

checklist or view it directly from the Planning and Installation Information Web page on 

Engineering PRIMUS Application System (EPAS) or from the Service and Support Web 

site. These are the uniform resource locators (URL) for the pages: 

http://epas1.rsvl.unisys.com/unisys/2200/cfswww/prodsupp/install.htm 

http://www.support.unisys.com/unisys/2200/cfswww/prodsupp/install.htm 



Other checklists and support documents are also available on the Internet. Search for the 

TIB Internet Access for 2200 Support Documents (SPI 10061903). Use a text search for 

“internet access” for instructions on logging on to the site. 

2.2. Installation Checklists 

During software installation, you need to input the information in the following two tables 

in response to prompts. Work with site personnel to define the required installation 

information identified in Table 2–1 and Table 2–2. 

You also need to input private interconnect (FDDI LAN) network parameters, which are 

identified in Appendix B, and which are predefined for each node. 

For more information on SPO aliases, see 2.3.2. 

Caution 

To prevent rework, accurately complete the checklists to prevent conflicts with 

existing network names and addresses at the site. 


Table 2–1. General Installation Information 

Prompt Entry 

Windows 2000 and Windows NT Server Parameters 

Name and Organization Name __________________________ 

Server Type 

Installation procedures 

in this Guide are for 

member server (standalone 

server) installation 

only. If sites choose a 

different server type, 

they must provide the 

additional information 

required during 

installation, which is not 

documented here. 


Determine the name the site wants identified with the Windows 2000 or 

Windows NT node (for example, the administrator’s name or the Windows 

owner name). 

Organization _____________________________ 

Determine the organization name the site wants identified with the Windows 

2000 or Windows NT node. 

Have the client determine the Windows server type: 

− Primary Domain Controller (PDC) 

Directly maintains security and user account information in the master 

copy of the domain’s directory database. 

− Backup Domain Controller (BDC) 

If BDC is selected, the PDC must be accessible on the LAN during 

setup of the BDC. The BDC maintains a replicated copy of the 

directory database maintained by the PDC. Can be promoted to serve 

as a PDC. 

− Stand-alone Server (default recommendation) 

Stand-alone server is recommended in the following circumstances: 

If the server is to perform time critical tasks and the site does not 

want it spending time authorizing domain logon attempts or receiving 

synchronized copies of the domain’s directory database. 

If the site wants this server to have a different administrator or 

different user accounts from the rest of the servers in the domain. 

A member server can participate in a domain, although that is not 

required. 

SNMP Properties System administrator name __________________________ 

Date/Time Properties; 

Time Zone 

Phone number __________________________ 

Location (room number) __________________________ 

Time zone at the site _____________________________ 

Daylight saving time 

Check the checkbox provided on the Time Zone tab screen to indicate 

daylight saving time is used. Leave empty if daylight saving time is not 

used. 

continued 



Table 2–1. General Installation Information 

Prompt Entry 

UnixWare Parameters 

SNMP configuration System administrator name __________________________ 


Keyboard Type Keyboard type (language) to use __________________________ 

Language Supplement Select the country (language) to use __________________________ 


Time Zone 

Number of 2200 node 

system consoles. 

SPO Server UnixWare Parameters 

Time zone at the site ______________________ 

Daylight saving time Yes ___ No ___ 

Number of 2200 node system consoles (1 to 12) ___________ 

Keyboard type Keyboard type (language) to use ________________________ 

Language Supplement 

Installation 


Time Zone 

Select the country (language) to use __________________________ 

SPO Workstation Parameters 




Component 

Windows 2000 or 

Windows NT node 1 (if 

applicable)** 



applicable)** 



applicable)** 



applicable)** 

UnixWare node 1 (if 

applicable) 


applicable) 


applicable) 


applicable) 

Table 2–2. Network Names, Addresses, and Mask Values 

External 

Network Host 

Name 

External 

Network IP 

Address 


Alias Assigned for SPO 

Console* 

cp_nt1 

cp_nt2 

cp_nt3 

cp_nt4 

CP_UNIX1 




SPO server SPO_Server 

SPO workstation or 

terminal 

Additional SPO 

workstations (optional) 

2200 system console 1 cp_cons01 

(Not prompted)* 

2200 system console 2 

(optional) 


(optional) 

cp_cons02 


cp_cons03 

through 

cp_cons12 


2200 node 

cp_ws 

continued 



Component 

Domain name server 

(DNS) (optional)ò 

Domain name for DNS 

(optional) 

Additional DNS (optional) 

External router (optional) 

Primary Windows Internet 

Name Service (WINS) 

(optional) 

Secondary WINS 

(optional) 

Broadcast address 

(optional) 

Domain name (for 

example, 

rsvl.unisys.com) 

Netmask (optional; only 

required if site uses 

subnet masking) 

Table 2–2. Network Names, Addresses, and Mask Values 

External 

Network Host 

Name 

Other 

External 

Network IP 

Address 

Alias Assigned for SPO 

Console* 

*These names are predetermined. To change them, customize the SPO/HMP Console configuration (16.4). 

**The ES5085R comes with a Dual-Port Intel-Pro/100 Ethernet card. You will have to obtain a second IP 

address for the second port. 

ò You are not prompted for the DNS host name when you install Windows 2000 or Windows NT. It is required 

when you install UnixWare. 

Cautions 

• The ClearPath IX server private interconnect (FDDI LAN) must not be 

connected in any way to any external network (for example, by a gateway or 

router). 

• CMS 1100 must be configured for the 2200 node and system consoles as 

described in 2.3. 

• If the site does not currently have a network, it must consider installing the 

ClearPath IX server as a private network as described in 2.4.2. 


2.3. Installation Tips 

Caution 


Failure to follow the procedures recommended in this subsection may result in 

installation problems and additional work. 

This subsection describes procedures you can use to minimize problems during and after 

installation. 

2.3.1. Hardware Tips 

Return to this section in either case below. More information follows. 

• Problems with the RAID subsystem 

• PING test failure 

Recovering from a RAID Subsystem Problem 

To recover from a problem with the RAID subsystem, take the appropriate set of steps 

below: 

For AMI MegaRAID cards— 

1. Run the FlexRAID utility software (7.1.5 or 7.2.3). 

2. Click the prointer icon under Configuration to get a listing of the RAID configuration. 

3. Save a listing, especially if the configuration is different from the default. 

For Mylex RAID cards— 

1. If you are currently logged on, shut down and reboot your server. 

2. During the reboot, press ALT-R to obtain the Mylex DAC1100 RAID configuration 

options. The Welcome to RAID EzAssist menu is displayed. 

3. Select “Back up configuration” and press enter. The Back Up Configuration menu 

appears. 

4. Insert a blank diskette into the floppy drive and press Enter. 

5. When the configuration file has been written to the diskette, the menu closes, and you 

return to the main Welcome menu. 

6. Press the ESC key, select YES to exit from RAID EzAssist, and press Enter. The server 

reboots. 



Recovering from a PING Test Failure 

The most common reason for PING test failure when you test interconnect communications 

(Section 14) is lack of an FDDI driver, or an incorrectly installed one, on the Intel 

node. Refer to the full operating system software installation procedure, or the Windows 

2000, Windows NT, or UnixWare documentation, for steps to correctly install and 

configure the FDDI driver. 

2.3.2. Software Tips 

These are points to be aware of as you install and configure the software. More 

information follows in this section. 

• Creating emergency recovery diskettes 

• Choosing to perform a full installation even when software is preloaded or preinstalled 

• Finding the correct license information for SCO UnixWare and Enterprise Backup and 

Restore 

• Configuring OS 2200 print queues 

• Deciding to install Windows NT Server as a primary or backup domain controller 

• Changing SPO aliases 

• Configuring CMS 1100 

• Changing the installation passwords following hardware RFU 

• Modifying Windows NT/2000 server network settings after installation 

Creating Emergency Recovery Diskettes 

You must create an emergency recovery diskette for each Windows 2000 node, each 

Windows NT node, each UnixWare node, and the SPO server. The procedures for creating 

those diskettes are described as part of the procedures for completing installation of 

Windows NT (7.1.17), Windows 2000 (7.2.9), and UnixWare (8.13). 

Performing a Full Installation When Software Is Preloaded or Preinstalled 

Intel node and system console software are preloaded on servers shipped to U.S. sites. 

SPO server software, in addition to being preloaded, is preinstalled. Because a full set of 

installation media is provided, you may wish to perform the full installation procedure, 

even with software preloaded or preinstalled, for the following reasons: 

• A problem was encountered while performing the procedure for preloaded or 

preinstalled software. 

• The site wants to verify that the installation media are good for future use. 

• The site wants to train people in installation and configuration procedures for a 

particular node. 

• Some other reason particular to the site or to the system being installed. 


Finding Correct UnixWare and EBRS License Information 


Table 2–3 identifies where to find correct site license information for UnixWare and EBRS. 

Table 2–3. Location of Correct License Information 

Product License Description 

SCO UnixWare 

License Information 

EBRS Site License 

Number 

Configuring OS 2200 Print Queues 

SCO UnixWare 7 Application Server comes with a Certificate of 

License and Authenticity for the following licenses: 

• One 5-user license (found inside the SCO UnixWare installation 

media package) 

• Two 25-user licenses 

When initially installing UnixWare—on either an Intel node or the SPO 

server—you must enter the serial number and activation key from 

the certificate for the 5-user license. 

The EBRS installation media include a cover letter that identifies the 

site license number and the number of workstations allowed by the 

license. During installation of EBRS, you must enter the site license 

number using instructions given in the cover letter. 

Record that license number here: 

EBRS Site License Number: ______________________________ 

The OS 2200 master and boot tapes provided with a ClearPath IX server contain new 

required station local statements that define print queues for DEPCON. The queues 

EMAIL, WINDOC, and DEPERR are required by the Integration Expert software. For 

Integration Expert to operate correctly, you must include the station-local statements that 

establish those queues if the site performs a system generation. 

Installing a Windows Node as a PDC or BDC 

This guide provides procedures for installing nonclustered Windows 2000 or Windows NT 

nodes as member servers only (stand-alone Windows systems). Sites that choose to install 

a Windows node as a primary domain controller (PDC) or backup domain controller (BDC) 

will need additional information, and must take additional steps, beyond what is described 

in this document. 

Use the basic procedures provided in this document, and refer to Microsoft documentation 

or help files as needed for additional information. For more information about domain 

planning, refer to the Microsoft Concepts and Planning guides for Windows 2000 and 

Windows NT. 



Changing SPO Aliases 

The SPO aliases listed in Table 2–2 are automatically assigned to some host names for 

predefined SPO/HMP Console configurations. If you must change an alias for some 

reason, perform the steps described in 16.4 to modify the SPO/HMP Console default 

configurations. For example, if you have a second ClearPath IX server on the same LAN as 

another ClearPath IX server, you could change the names for the second ClearPath IX 

server as described in 16.4. 

Configuring CMS 1100 

Sites must configure CMS 1100 to define LAN connections for Intel nodes, IP addresses for 

OS 2200 nodes and system consoles, Simple Network Management Protocol (SNMP) Agent 

communities for SysAdmin, and at least one TCP/IP path to each OS 2200 node so that 

Integration Expert can be used to further customize the configuration. 

See 16.1 for more information. 

Changing Passwords Following Installation 

Throughout the installation procedures, predefined passwords are used to simplify initial 

installation of the software, or they are supplied for preinstalled software. To prevent 

unauthorized access to data or programs, the site must change those passwords following 

hardware RFU. 

Modifying Windows NT/2000 Server Network Settings after Installation 

Network settings that you enter during installation can be modified later. (There are two 

exceptions; see below.) If you are unsure of a particular value while you are installing a 

server, you can enter what you believe is correct and change it later if you discover an 

error. If you expect to make such changes, it is recommended that you do not connect the 

server to the client’s network until you have made the corrections. Otherwise you risk 

disrupting the client’s network operation. 

Two items cannot be changed without a reinstallation: 

• A server’s operation mode (stand-alone server, primary domain controller, or backup 

domain controller). 

• A server’s DNS domain. IIS does not register changes to this value after installation. 

2.4. Additional Site Requirements 

Additional requirements sites should plan for include 

• Obtaining workstation hardware to support DEPCON (2.4.1). 

• Planning for a network if they do not currently have one (2.4.2). 

• Planning to integrate with an existing SPO server (optional), if they already have one 

(2.4.3). 


2.4.1. DEPCON Workstation Requirements 


Sites must provide a workstation on which to run DEPCON. Requirements are listed 

below. 

Note: If your ClearPath IX server includes a Windows NT node, you may wish to use 

that node to provide this capability. 

• Windows 2000, Windows 95, Windows 98, or Windows NT 3.51 or higher 

• Minimum processor required for the Windows operating system 

• 3-1/2-inch diskette drive or access to a network for installation 

• Minimum memory required for the Windows operating system 

• A hard disk with a minimum of 6 MB available for the DEPCON software (25MB for a 

full installation) and enough space for the files you want to print 

• A monitor with a minimum display resolution of 800 x 600 pixels 

Refer to the DEPCON Application Configuration and Operations Guide for detailed 

information. 

Note: You can connect block multiplexer channel (BMC) printers to the DEPCON 

workstation only on Windows NT and Windows 2000, not Windows 95 or 

Windows 98. 

2.4.2. Planning for ClearPath IX Server Installation as a Private 

Network 

Note: For additional guidance on the use of Internet addresses, read the Internet 

Engineering Task Force (IETF) Request for Comments (RFC) 1918, which can 

be found on the Web. 

A site without an existing TCP/IP network can initially set up a private network by 

selecting IP numbers reserved by the IANA for private Internets (from 192.168.1.xxx to 

192.168.255.xxx—excluding the range used by Unisys for the internal FDDI LAN). 

Using addresses reserved for private networks is an easy way to get started. But to later 

connect to the external Internet the site must get official IP addresses and reconfigure all 

server components with the official addresses. 



10 Base 

5LAN 

(Thick Coax) 

Cautions 

• IP numbers reserved for private Internets by the Internet Assigned Numbers 

Authority (IANA) can be used to initially configure the ClearPath IX server; but 

to connect to the external Internet in the future, the site must get official IP 

addresses and then reconfigure all ClearPath IX server components with those 

addresses. 

• A site must not use numbers in the range 192.168.57.xxx. Unisys has 

selected numbers in that range for the ClearPath IX server’s internal FDDI LAN 

(see Appendix B). 

A suggested methodology for using addresses reserved for private LANs is to use Ethernet 

IP addresses in the range 192.168.58.xxx. That ensures that the Ethernet addresses identify 

a different LAN segment from the internal FDDI LAN, which uses numbers in the range 

192.168.57.xxx. Figure 2–1 and Table 2–4 illustrate the connection of server components 

to the Ethernet network, and IP addresses that could be assigned, using that methodology. 

In addition, the site also must reconfigure CMS 1100 to support IP addresses for the 2200 

node and system consoles (see 16.2). 

Note: Figure 2–1 and Table 2–4 show the use of this methodology with single-node 

systems only. 

2200 Node 

192.168.58.5 

Coax 

Cable 

RJ-45 Cables 

Intel Node 

192.168.58.3 

or 192.168.58.4 

Master System 

Console (2200 node) 

192.168.58.11 

SPO Server 

192.168.58.15 

Ethernet Hub 

Backup System 

Console (2200 node) 

192.168.58.12 

To Other System 

Consoles 

(SCF Workstations) 

SPO Workstation 

192.168.58.16 

Figure 2–1. Example Use of LAN Addresses for the External Network 

(Recommended Only for Sites without an Existing Network) 


Caution 


The IP addresses shown in Figure 2–1 and Table 2–4 are meant to illustrate the 

use of IP addresses reserved for private networks. Those addresses are not 

necessarily valid addresses for the site. 

Table 2–4. Example Use of LAN Addresses for the External Network (Recommended 

Only for Sites without an Existing Network) 

Component 

Windows 2000 or Windows NT 

node (if applicable) 

UnixWare or UNIX node (if 

applicable) 

Ethernet 

Host Name 

Ethernet IP 

Address 

Alias Assigned 

Automatically for 

SPO Basic Edition* 

eth1ntsr 192.168.58.3 eth1ntsr 

eth1uxsr 192.168.58.4 CP_UNIX 

SPO server ixspo 192.168.58.15 SPO_Server 

First SPO workstation ixterm1 192.168.58.16 cp_ws 

Second SPO workstation 

(optional) 

ixterm2 192.168.58.17 

2200 node eth122sr 192.168.58.5 

2200 system console 1 cp_cons01 

(not prompted) 

2200 system console 2 (optional) cp_cons02 


2200 system console 3 through 


(optional) 

cp_cons03 through 

cp_cons12 


192.168.58.11 

192.168.58.12 

192.168.58.13 

* These are the alias names automatically assigned as labels in the SPO Basic Edition default configurations. If you 

need to change an alias, customize the SPO Basic Edition configuration as described in 16.4. 

2.4.3. Integrating with an Existing SPO Server 

The purchase of a ClearPath IX server entitles the site to use Single Point Operations Basic 

Edition for ClearPath IX (Basic Edition) software to operate a stand-alone ClearPath IX 

server or alternatively to manage one ClearPath IX server from one or more Single Point 

Operations Console (SPO Console) servers. 



If SPO Console is already installed, the site can use the temporary key provided in 

Appendix C to enable the SPO interface that allows management of the ClearPath IX 

server. 

To enable control of a ClearPath IX server from an existing SPO Console server, the site 

must 

• Migrate to SPO Console level 4.3 or higher (must be at that level to manage a ClearPath 

IX server). 

• Customize existing SPO Console configurations to add host representations for the 

ClearPath IX nodes. 

• Modify existing Autoaction Message System (AMS) databases to add ClearPath IX 

server automation logic and to ensure that it does not conflict with existing 

automation logic. 

• Copy and install agent files to enable communication with the Windows 2000, 

Windows NT, and UnixWare nodes (see Section 10). 

Other SPO Console installation instructions are contained in the following documents: 

• Single Point Operations Installation Guide 

• Single Point Operations Administration and Configuration Guide 

• Single Point Interface Software Installation and Configuration Guide 

Integration of an existing SPO Console server with the ClearPath IX server is the 

responsibility of the site, or is a purchased service available from Unisys. 

Sites migrating to this release from a previous release should refer to the ClearPath HMP 

IX and 2200 Systems Software Planning and Migration Overview for more information 

about migrating their existing SPO server. 

2.5. Configuring and Using the Monitor 

Concentrator 

For easy identification of each system being monitored, you should assign unique names to 

each port of the monitor concentrator as described in 2.5.1. Use of the monitor 

concentrator is described in 2.5.2. 

2.5.1. Configuring the Monitor Concentrator 

The procedure for assigning names to each port of the monitor concentrator (see Figure 

2–2) is as follows: 

1. Press Print Screen. The On Screen Configuration and Activity Reporting (OSCAR) 

selection screen appears in the upper left corner of the display. 

2. Press F2. The ADVANCED MENUS screen appears. 



3. Use the left and right arrow keys to select the Setup menu. Then use the up and down 

arrow keys to select Names and press Enter. A PORT NAMING window similar to 

Figure 2–2 appears. 

4. Use the arrow keys to select the port whose name you want to enter or change. Type 

in the desired name. Up to 12 characters can be entered. Legal characters are A–Z, 0– 

9, and the hyphen character (-). Lowercase letters are converted to uppercase. Press 

Backspace to delete an incorrect entry. 

5. When done, press Enter. 

6. Press Escape to exit. 

PORT NAMING 

Port Name 

1 

UNIXNODE1 

2 

UNIXNODE2 

3 

SPO SERVER 

4 

SCF MASTER 

5 

SCF BACKUP 

6 

NT NODE 1 

7 

NT NODE 2 

8 

Figure 2–2. Example of Monitor Concentrator Port Name Assignments 

Refer to the Apex Outlook Concentrator User Guide for detailed information on 

configuring the monitor concentrator. 

2.5.2. Using the Monitor Concentrator 

In normal operating mode, the number of the port being monitored appears in the upper 

left corner of the monitor screen. To switch to a different port, take the following steps: 

1. Press Print Screen. The port selection menu appears in the upper left corner of the 

monitor screen. 

2. Use the arrow keys to select the desired system, then press Enter. 

Switching disconnects the keyboard, mouse, and monitor from one system and switches 

them to the selected system. 




Section 3 

Installing Windows 2000 Advanced 

Server (ES5044R, ES5085R, and 

ES2024R) 

This section tells how to install and configure the Windows 2000 Advanced Server 

operating system on an Intel server node. Section 7 describes additional steps you must 

take to complete Windows 2000 Advanced installation. A full installation, with the 

checklist in Table 3–1 completed and all software media readily available, takes about 1 

hour. 

The information in this section applies to the following server node configurations: 

Computer Components Unisys Styles 

ES5044R 

(ESR504141-GZN) 

ES5085R 

(ESR508151-GZN) 

Windows 2000 Advanced Server operating 

system 

Mylex DAC1164P 

or 

Mylex AcceleRAID 352 

WSA200008-xxx 

RAD5003-P64 

RAD6002-P64 

SysKonnect SK-NET FDDI PCI FDI101-PCI 

Seagate 18GB disk drive HDM18110-CX1 

Intel Server Management Card MGT50-PCI 


system 


or 


WSA200008-xxx 

RAD5003-P64 

RAD6002-P64 


Intel EtherExpress PRO (dual) ETH1010053-PCI 

Intel Server Management card MGT50-PCI 

continued 


Installing Windows 2000 Advanced Server (ES5044R, ES5085R, and ES2024R) 


ES2024R 

(ESR202141-2) 

Fujitsu 18GB disk drive 

or 

Seagate 186B disk drive 


system 


or 


HDL1817-CX1 

HDM18110-CX1 

WSA200008-xxx 

RAD5003-P64 

RAD6002-P64 


Seagate 18GB disk drive ES2024-18G 

Note: The client, or a representative of the client, must read and agree to the Software 

License Agreement during the installation procedure. 

Table 3–1 lists media and information you need to complete the installation. Obtain the 

information or media before beginning. 

Table 3–1. Windows 2000 Advanced Server: ES5044R, ES5085R, and ES2024R 

Installation Checklist 

√ Media or Information Required 

3.4.1. Installing the Windows 2000 Advanced Server Operating System 

Media needed: 

• Windows 2000 Advanced Bootable CD-ROM (unless software is preloaded) 

• Blank 3-1/2 inch diskette (label this diskette “Emergency Repair Disk”) 

The hardware diskettes can be located in the operating kit that is strapped to the top of the server. 

3.4.2. Configuring Windows 2000 Advanced Server 

Information needed: 

Name and Organization screen 

Name __________________________ 

Determine the name the site wants identified with the Windows 2000 Advanced node (for example, 

the administrator’s name or the Windows 2000 Advanced owner name). 

Organization _____________________________ 

Determine the organization name the site wants identified with the Windows 2000 Advanced node. 

continued 



Table 3–1. Windows 2000 Advanced Server: ES5044R, ES5085R, and ES2024R 



Your Product Key screen 

Registration number ______________________________________ 

To register Windows 2000 Advanced, you need the key number printed on a label on the back of 

the Windows 2000 Advanced CD-ROM jewel case or on the Certificate of Authentication. 

Date/Time Properties screen; Time Zone tab screen 


Daylight saving time: If daylight saving time is being used, check the check box provided on the 

Time Zone tab screen. 

3.1. Determining Whether Software Is Preloaded 

Caution 

To prevent installation problems or wasted time, determine whether Windows 

2000 Advanced has been preloaded. Then follow either the procedure for 

preloaded software or the full installation procedure, as appropriate. 

To determine whether the Windows 2000 Advanced operating system is preloaded, 

perform the steps below. 

Notes: 

• Before powering on the Intel node, verify that the preloaded RAID disks are installed 

in the correct bays as labeled on the disks. See the applicable server system map for 

the location and layout of the drive bays. 

• If you encounter any problems installing the RAD6002-P64 RAID card, refer to the 

Unisys Ultra160 RAID Adapter Driver Update Notice (4556 3947). 

1. Power the Intel node on and allow it to fully boot (takes about 2 minutes). 

During the boot, the following message may appear: 

DAC1100 found new configuration, it will 

reset to update configuration. 

DAC1100 reset complete. 

That message indicates that the RAID configuration saved in nonvolatile memory by 

the RAID controller does not match the current configuration. If no errors occurred 

during the reset, proceed to step 11 below. Otherwise, continue with step 2 to correct 

the problem. 



2. Press Alt-M to start BIOS Options Utility. A BIOS options menu appears: 

----BIOS Options----- 

BIOS enabled 

CD-ROM boot disabled 

8GB drive geometry 

Note: The BIOS should be enabled from the factory. 

If BIOS options are not set as above, continue with steps b through f as needed; 

otherwise, go to step e. 

3. Select the BIOS option using the arrow keys. Press Enter to change the option to 

Enabled. 

4. Select the drive geometry option using the arrow keys. Press Enter to change the 

option to 8GB. 

A warning message appears: 

Changing drive geometry may lead to non-bootable 

system drives and/or loss of data! 

Proceed anyway? (Y/N) 

5. Type Y (yes) and press Enter. The drive geometry is now 8GB. 

6. Press Esc twice to quit BIOS Option Utility. 

A message appears: 

The system will restart. 

Press any key to continue. 

7. Press Enter and let the system reboot. 

Watch the messages on the screen for the ALT-R prompt. 

8. Press Alt-R to start the Mylex RAID EzAssist utility. 

An EzAssist Menu for configuring RAID logical arrays appears as follows: 

----EzAssist Menu---- 

Configure RAID Drive 

View or Modify Controller Configuration 

Perform Administration on... 

Rescan for New Devices 

Advanced Options 

9. Select the option Configure RAID Drive using the arrow keys, then press Enter. 

A Configuration Method menu appears: 

------Configuration Method----- 

Automatic 

Assisted 

Custom 



Notes: 

• Unless noted otherwise, use the arrow keys to select menu options throughout the 

rest of this procedure. 

• If a message appears stating that there are no disks to configure, return to the 

EzAssist menu (step 8) and select Advanced Options; then select “clear 

configuration.” You will then be able to configure the RAID drive. 

10. Select Automatic, then press Enter. 

The RAID Configuration Summary window appears: 

RAID Configuration Summary 

Logical Drive 0 

Fault Tolerance: Yes 

Spare: No 

Optimization: Performance 

Logical Drive Count: 1 

Total Capacity: 17.0 GB 

Chan: 10 Vendor Model Version Capacity (GB) Status 

1:00 UNISYS ....... 17.0 Online 

1:01 UNISYS ....... 17.0 Online 

Make sure Apply is highlighted , then press Enter. 

A message window appears: 

Writing RAID Configuration 

Please wait... 

A final window appears: 

Congratulations! 

Configuration Status 


RAID configuration is successful. 

You may utilize this drive immediately. 

[Reboot] Main Menu 

Press Enter or Ctrl-Alt-Del to reboot. 

11. Once the reboot is complete, watch for a Windows 2000 setup screen. If one appears, 

the operating system has been preloaded. 

Windows may run check-disk; if so, the system automatically reboots when check-disk 

finishes. 

If Windows 2000 Advanced is preloaded, perform the steps described in 3.2. Then 

complete the installation as described in Section 7. 

If Windows 2000 Advanced is not preloaded, take the following steps: 

1. Configure the RAID controller (3.3). 

2. Install the Windows 2000 Advanced operating system (3.4). 



3. Log on to Windows 2000 Advanced (3.5). 

4. Complete the installation (Section 7). 

3.2. Steps to Take If Windows 2000 Advanced Is 

Preloaded 

Following the screen that indicates Windows is preloaded (3.1, step 11), a second Windows 

2000 server-setup screen appears. 

Note: If you decide to perform a full installation even though the system is preloaded, 

do not format the RAID disk. Instead, use the DAC BIOS utility to initialize the 

RAID volume before you reload the operating system. Formatting the disk 

makes the drive unrecognizable to the software. 

1. Click Next to continue. 

A Software License Agreement screen appears. 

2. Have the client, or a representative of the client, accept the license agreement as 

follows: 

a. Read the contents of the first page, then press the Page Down key to read the next 

page. 

b. When you have read the entire agreement, click “I accept this agreement.” 

c. Click Next. 

After a few seconds a Windows 2000 Regional Settings screen appears. 

d. If the settings are acceptable, click Next to proceed. Otherwise, modify the 

settings as needed, then click Next. 

The Windows 2000 Personalize Your Software screen appears, followed by a Name and 

Organization screen. 

3. Enter name and organization as follows: 

a. Name field—Enter the user name the site wants identified with the Windows 2000 

Advanced node. 

b. Press the Tab key to advance to the Organization field. 

c. Organization field—Enter the organization the site wants identified with the 

Windows 2000 Advanced node. 

d. Click Next to proceed to the next screen. 

A Registration screen appears asking for the registration number from the Certificate 

of Authentication. 

4. Enter the registration number as recorded in Table 2–2, or enter it directly from the 

Certificate of Authentication, as follows: 

a. Type the required digits in each field. 

b. Click Next to proceed. 



A Licensing Modes screen appears. 

5. Click the per-seat licensing option, then click Next to proceed. 

The Computer Name and Administrator Password screen appears. 

Note: The computer name (up to 15 characters) is the Network Basic 

Input/Output System (NETBIOS) name that uniquely identifies the 

computer in the Windows 2000 Advanced workgroup or domain. It must be 

different from the workgroup or domain name. 

6. In the name field, enter the host name from Table 2–2 by which the Windows 2000 

node will be identified on the external TCP/IP network. Tab to the administrator 

password. 

a. In the password field, type administrator. 

b. Tab to Confirm Password. Type administrator in that field. 

c. Click Next to proceed. 

Note: Following installation, the site must change the default password 

(administrator) to a different password. 

A tabbed Date and Time Settings screen appears. If you do not need to set the date 

and time, click Next, then skip to step 8. Otherwise continue with step 7. 

7. Click the Date, Time, and Time Zone tabs (in any order) for the changes you need to 

make. All are optional. Set the fields as follows: 

• Month—Click the arrow keys and select the correct month on the calendar. 

• Day of the month—Click the correct date to set it on the calendar. 

• Time—Click the scroll bar arrow and scroll up or down until the correct time 

appears. 

• Time zone—To change the time zone, click the scroll bar arrow and scroll up or 

down to select the correct time zone. The map shifts over the time zone selected. 

• Daylight saving time—Click the check box to select daylight saving time if it 

applies to the time zone. 

Click Next when done with both the date and time. 

After a minute or two, the Windows 2000 Server Setup screen indicates that Setup is 

installing the networking settings. 

About a minute later, a Windows 2000 Advanced Setup screen for configuring 

networking appears. 

8. A Networking Settings screen appears with the following check boxes: 

• Typical settings 

• Custom settings 

9. Select Custom settings, then click Next. 

Continue customization by following the instructions in the appropriate server 

subsection below. 



ES5085R server: 

A screen appears with a set of networking components for the first network device 

detected, the Intel[R] PRO/100+ Dual Port Server Adapter #2. These default 

components are checked: 

• Client for Microsoft Networks 

• File and Print Sharing for Microsoft Networks 

• Network Monitor Driver 

• Internet Protocol (TCP/IP) 

You may change these selections as desired. Click components to check or uncheck 

them. By default, this adapter is not used by ClearPath. 

Next, proceed as follows: 

a. Click Next. 

A screen appears with the next configurable device: the Intel[R] PRO/100+ Dual 

Port Server Adapter. The same default components are checked again (see 

bulleted list above). 

b. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. Configure 

the Fast Ethernet network adapter card as follows: 

1) Click “Use the following IP address.” In the IP Address field enter the IP 

address for the Windows 2000 Advanced node from Table 2–2, then press Tab. 

2) Change the subnet mask to the netmask address from Table 2–2, or skip this 

field (accept the default). 

3) If you have a gateway (router), tab to the Default Gateway field and type the 

gateway address from Table 2–2. This completes the entering of IP address 

information. 

4) Click Advanced and add any additional gateway entries that the site requires. 

5) If the site chooses to implement WINS, click the WINS tab (otherwise skip this 

step), then do the following to enter WINS information: 

a) Click Add and type address from Table 2–2. Click Add again. 

b) Enter any additional IP addresses from Table 2–2. 

6) Click the DNS tab. 

7) If the site has any DNS servers, click Add (otherwise skip this step). In the 

window that appears, enter the IP address for the first DNS server from Table 

2–2; then click Add again. 

8) If applicable, click Add and enter any additional DNS servers. 

9) Click “Register this connection’s addresses in DNS” to clear it. 

10) Leave the default selections for the DNS suffix as they are. (“Append 

primary…and append parent….”) 

11) Click OK. 

12) Click OK. 



13) Click Next. 

A screen appears with the next configurable device: the SysKonnect FDDI PCI 

Adapter SK-5544 [SK-NET…]. 

c. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. Configure 

the FDDI network adapter card as follows: 

1) Select the option “Use the following IP address.” 

Note: You must know if this Windows 2000 or NT server node is being 

installed as the first, second, third, or fourth Windows node in the 

ClearPath IX system to which it is connected. You will use the IP 

address associated with that node number. The addresses are listed 

in Table B-1. 

1) In the IP Address field, type the appropriate FDDI address for this node (for 

example, 192.168.057.003 for the first Intel node) as described in Appendix B, 

Table B–1. Then press Tab. 

2) In the Subnet Mask field, enter the address 255.255.255.0. Do not enter a 

gateway address. 

3) Click the Advanced button. 

4) Click the Add button in the IP Addresses box. 

5) Enter the other two addresses and subnet masks from Table B–1. Then click 

OK. 

6) Click OK. 


d. Skip to step 10. 



detected, the Intel[R] PRO/100+ Server Adapter. These default components are 

checked: 






them. Then proceed as follows: 

a. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. Configure 










information. 




a) Click Add and type the address from Table 2–2. Click Add again. 







9) Click to uncheck “Register the connections added in DNS.” 



11) Click OK. 

12) Click OK. 




b. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. Configure 


1) Click the option “Use the following IP address.” 





in Table B-1. 




3) In the Subnet Mask field, enter the address 255.255.255.0. 




OK. 

7) Click OK. 


c. Skip to step 10. 





detected, the SysKonnect FDDI PCI Adapter SK-5544. These default components are 

checked: 






them. Then proceed as follows: 

a. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. 

b. Click “Use the following IP address.” 




address associated with that node number. The addresses are listed in 

Table B-1. 

c. In the IP Address field, type the appropriate FDDI address for this node (for 



d. In the Subnet Mask field, enter the address 255.255.255.0. 

e. Click the Advanced button. 

f. Click the Add button in the IP Addresses box. 

g. Enter the other two addresses and subnet masks from Table B–1. Then click OK. 

h. Click OK. 

i. Click Next. 

A screen appears with the next configurable device: the IBM Netfinity Fault 

Tolerance PCI Adapter. The following default components are checked: 




Continue by configuring the Netfinity card: 

j. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. 

k. Click “Use the following IP address.” 

l. In the IP Address field, enter the IP address for the Windows 2000 Advanced node 

from Table 2–2, then press Tab. 

m. Change the subnet mask to the netmask address from Table 2–2, or skip this field 

(accept the default). 



n. If you have a gateway (router), tab to the Default Gateway field and type the 

gateway address from Table 2–2. 

o. Click Advanced and add any additional gateway entries that the site requires. 

p. If the site chooses to implement WINS, click the WINS tab (otherwise skip this 

step), then enter WINS information as follows: 

1) Click Add and type the address from Table 2–2. Click Add again. 

2) Enter any additional IP addresses from Table 2–2. 

q. Click the DNS tab. 

r. If the site has any DNS servers, click Add (otherwise skip this step). In the 

window that appears, enter the IP address for the first DNS server from Table 2–2; 

then click Add again. 

s. If applicable, click Add and enter any additional DNS servers. 

t. Click to uncheck “Register the connections added in DNS.” 

u. Leave the default selections for the DNS suffix as they are. (“Append 


v. Click OK. 

w. Click OK. 

x. Click Next. 

10. A Workgroup or Computer Domain screen identifies the host name of the Windows 

2000 node and asks whether the node is to participate in a workgroup or domain. 

Proceed as follows: 

a. Click No. 

b. Enter the workgroup name CLEARPATH in the box labeled Workgroup or 

computer domain. 

Note: You can enter a different workgroup name if the client site 

requirements are different. 


The Windows 2000 Server Setup screen indicates that it is installing Windows 2000 

components. This may take several minutes. A progress bar shows the status of the 

installation. 

The following message appears: 

You have successfully completed Windows 2000 Setup. 

If there is a CD in your drive, remove it. Then, 

to restart your computer, click Finish. 

11. Click Finish. 

The server reboots. After a few minutes, the Windows 2000 Advanced Server logo 

appears and you are prompted to press Ctrl-Alt-Del to log on. 

12. Log on as the administrator (3.5). 

A menu labeled Windows 2000 Configure Your Server appears, giving three options: 



ù This is the only server in my network. 

ù One or more servers are already running in my network. 

ù I will configure this server later. 

13. Click “I will configure this server later.” Then click Next. 

14. Tab to the check box labeled “Show this screen at startup” and clear it. 

15. Close the Configure Your Server window. 

At this point, you should still be logged on as the administrator. Complete Windows 2000 

Advanced installation as described in 7.2. 

3.3. Configuring the RAID Controller 

Configure the RAID disk controller for RAID level 1 (mirroring) for two disks units. 

Sites can reconfigure a different RAID level following hardware RFU, if desired. For 

detailed information see the Mylex RAID Management documentation available on the CD- 

ROM labeled "Mylex Solutions Software Kit x.xx." 

Notes: 

• Switch the monitor concentrator to the Intel node position before beginning (see 

2.5.2). 

• If you are performing a full installation on a system that was preloaded, do not 

format the RAID disk. Instead, use the DAC BIOS utility to initialize the RAID 

volume before you reload the operating system. Formatting the disk makes the drive 

unrecognizable to the software. 

• In step 2, you must press Alt-M within a few seconds to enter the BIO Options 

Utility. 

• In step 8, you must press Alt-R within a few seconds to enter the RAID controller 

configuration procedure; otherwise, the normal boot procedure continues. See next 

note for ES2024R server. 

• For the ES2024R server, before you press Alt-R, you must press Alt-M to access the 

BIOS options utility. Then press Alt-R in order to access the Mylex RAID EzAssist 

utility, as instructed in step 8. 

Take the following steps to run the RAID controller configuration utility: 

1. Power on or reboot the Intel node. 

Several start-up messages appear, ending in a prompt to press Alt-M, as follows: 

DAC1100 ADAPTER BIOS VERSION x.xx 

Mylex Corporation 

Host Adapter-1 Firmware Version x.xx DRAM size xxx MB 

. 

. 

. 

Spinning up drives... 

. 



. 

. 

1 Logical Drives found on the Host Adapter 

1 Logical Drives handled by BIOS 

> 

2. Immediately press Alt-M to start BIOS Options Utility. A BIOS options menu appears: 


BIOS enabled 

CD-ROM boot enabled 


Note: If BIOS options are not set as above, continue with steps 3 through 7 as 

needed; otherwise, go to step 8. 


Enabled. 

4. Select the CD-ROM option using the arrow keys. Press Enter to change the option to 

Boot Enabled. 













9. Immediately press Alt-R to start the Mylex RAID EzAssist utility. 








10. Select the option Configure RAID Drive using the arrow keys, then press Enter. 





Automatic 

Assisted 

Custom 

Notes: 

• Unless noted otherwise, use the arrow keys to select menu options throughout 

the rest of this procedure. 

• If a message appears stating that there are no disks to configure, return to the 

EzAssist menu (step 8) and select Advanced Options; then select “clear 

configuration.” You will then be able to configure the RAID drive. 






Spare: No 





1:00 UNISYS ....... 17.0 Online 

1:01 UNISYS ....... 17.0 Online 

Make sure Apply is highlighted, then press Enter. 











12. Insert the Windows 2000 Advanced Bootable CD-ROM in the drive. 

13. Highlight Reboot, then press Enter. 

Continue by installing and configuring Windows 2000 Advanced as described in 3.4. 



3.4. Installing and Configuring Windows 2000 

Advanced Server 

The Windows 2000 Advanced Server installation process consists of an installation phase 

(3.4.1) in which prompts appear as text messages and a configuration phase (3.4.2) in 

which prompts are presented as graphical screens. The following subsections describe the 

Notes: 


2.5.2). 

• Configuration settings are chosen to minimize problems during initial installation. 

After hardware RFU, the site may wish to customize the configuration to meet its 

needs. 

3.4.1. Installing the Windows 2000 Advanced Server Operating 

System 

Begin Windows 2000 Advanced Server installation as follows: 

1. Insert the Windows 2000 Advanced Bootable CD-ROM into the drive unit. 

Note: To avoid missing a five-second timing window, please read all of step 2 

(next) before executing it. 

2. On the Intel node, reboot or turn power on. 

After the hardware initialization messages are displayed, the following messages 

appears at the top of the screen: 

Setup is inspecting your computer's hardware configuration... 

Windows 2000 Setup 

================== 

If you have the RAD6002-P64 RAID Controller, press the F6 key within five seconds. 

This will let you install the driver before the OS installation, a requirement at this time. 

3. For all systems, wait for the Windows 2000 installation program to load its standard 

device files. The following message is then displayed: 

Setup could not determine the type of one or more mass storage devices... 

4. Insert the “Unisys-Mylex RAID Win2000 Drivers” diskette (4556 3780) and press S, then 

Enter. 

5. Select the Mylex AcceleRAID 352 Disk Array Controller to install it. 

6. After the driver is installed, remove the diskette and press Enter to continue. 

7. The Setup welcome menu appears: 

Welcome to Setup 

This portion of the Setup program prepares 

Microsoft Windows 2000 to run on your computer. 



ù To set up Windows 2000 now, press Enter. 

ù To repair a Windows 2000 installation, press R. 

ù To quit Setup without installing Windows 2000, press F3. 

8. Press Enter to begin setting up Windows 2000. 

If an operating system was previously installed on this server, the following message 

may appear: 

Setup has determined that your computer's startup hard disk is new 

or has been erased, or that your computer is running an operating 

system that is incompatible with Windows 2000. 

If the hard disk is new or has been erased, or if you want to discard 

its current contents, you can choose to continue Setup. 

If your computer is running an operating system that is incompatible 

with Windows 2000, continuing Setup may damage or destroy the existing 

operating system. 

ù To continue Setup, press C. 

CAUTION: Any data currently on your computer's startup hard disk 

will be lost. 

ù To quit Setup, press F3. 

If the message above appears, press C to continue. 

A Windows 2000 Licensing Agreement screen appears. 

9. Press F8 to indicate that you agree with the terms of the license agreement. 

A screen appears that identifies the unpartitioned disk space. 

Windows 2000 Server Setup 

====================== 

The following shows existing partitions and 

unpartitioned space on this computer. 

Use the UP and DOWN ARROW keys to move the highlight to an item in the list. 

To set up Windows 2000 on the selected items, press ENTER. 

To create a partition in the unpartitioned space, press C. 

To delete the selected partition, press D. 

Unpartitioned space xxxx MB 

ENTER=Install C=Create Partition F3=Exit 



10. Use the arrow keys to highlight “Unpartitioned space,” then press C to create a new 

partition. You are prompted to enter the size of the partition to be created. 

11. Press Backspace to clear the field, type 12000, then press Enter. The screen now 

shows a new partition with unformatted space of 12002 MB. 

12. Select the new, unformatted partition, then press Enter. 

A message asks you to select a file system for the partition. 

Format the partition using the NTFS file system 

Format the partition using the FAT file system 

13. Press enter. (The NTFS line is highlighted by default.) 

A message indicates that the disk is being formatted. 

After the formatting, a second message says that Windows Setup is examining the hard 

drives. 

A third message appears: 

Please wait while Setup copies files to the Windows 2000 

installation folders. 

This may take several minutes to complete. 

A progress bar shows the percentage of completion. When the files have been copied, 

a message appears briefly, saying that this portion of Setup is complete. The message 

asks you to remove the diskette and CD-ROM from the drives in preparation for 

rebooting. 

14. Remove the CD-ROM from the drive. The system reboots by itself. 

Following reboot, the Windows 2000 GUI screen appears. Continue by configuring 

Windows 2000 as described in 3.4.2. 

3.4.2. Configuring Windows 2000 Advanced Server 

This procedure follows immediately after, and is continuous with, the installation 

procedure in 3.4.1. 

After the Windows 2000 Advanced operating system reboots (3.4.1), a Windows 2000 Setup 

screen appears with a message box instructing you to insert the Windows 2000 Advanced 

Server CD-ROM. Take the following steps: 

1. Insert the Windows 2000 CD-ROM (labeled “Microsoft Windows 2000 Advanced 

Server”) into the drive, then click OK. 

If you click OK before the drive is ready, a prompt indicates that files are needed from 

the Windows 2000 Server CD-ROM. A scroll box identifies the directory from which 

they will be copied. Click OK in the box if this occurs. 

After about a minute, a Windows Wizard screen appears, followed by the Windows 

2000 Server Setup screen. You can click Next and continue immediately or wait for 

Setup to resume. Setup automatically starts detecting and installing devices. A 

progress bar on the screen indicates that Setup is working. This process may take 

several minutes. 



A Regional Settings screen appears, with a Customize button for making changes to 

system locale or keyboard layout controls. 

2. Click Next to defer making changes until later. 

A screen labeled Personalize Your Software appears. 

3. Enter the name and organization responsible for the node as follows: 

a. Name field—Enter the name of the person responsible for the node. 

b. Press the tab key to advance to the organization field. 

c. Organization field—Enter the organization responsible for the Windows 2000 

Advanced node. 


A screen labeled Your Product Key appears asking for the registration number 

from the Certificate of Authentication. 

4. Enter the registration number as recorded in Table 2–2, or directly from the Certificate 

of Authentication, as follows: 




5. Click the “Per seat” licensing option, then click Next to proceed. 

The Computer Name and Administrator Password screen appears. 

Note: The computer name (up to 15 characters) is the Network Basic 

Input/Output System (NETBIOS) name that uniquely identifies the 

computer in the Windows 2000 Advanced workgroup or domain. It must be 

different from the workgroup or domain name. 

6. In the name field, enter the host name from Table 2–2 by which the Windows 2000 

node will be identified on the external TCP/IP network. Tab to the administrator 

password. 

a. In the password field, type administrator. 

b. Tab to Confirm Password. Type administrator in that field. 




The Windows 2000 Components screen may appear, with the following items checked 

as defaults: 

• Accessories and Utilities 

• Indexing Service 

• Internet Information Services (IIS) 

• Script Debugger 

Otherwise, the Date and Time Settings screen appears. 



7. If the Windows 2000 Components screen appears, proceed as follows; otherwise, skip 

to step 10: 

a. Select Accessories and Utilities, if it is not highlighted by default. 

b. Click Details. A list of accessories and utilities appears. 

c. Click Games to uncheck it. 

d. Highlight Multimedia, then click Details. Click Media Player to check it. 

e. Click OK. 

f. Click Communications to highlight it. Click Details, then uncheck Chat and Phone 

Dialer. Leave HyperTerminal checked. 

g. Click OK. 

h. Click OK (again) to proceed. 

i. On the Components screen, click Management and Monitoring Tools to checkmark 

it. Click Details. Uncheck Connection Manager Components. 

j. Click OK. 

k. Click Networking Services to highlight it, but leave the box unchecked. 

l. Click Details. A box labeled Subcomponents of Networking Services appears. 

m. Click Simple TCP/IP Services to checkmark it 

n. Click OK to proceed. 

8. Review the list. The following items should be checkmarked: 

• Accessories and Utilities (partial—box is checked but grayed out) 

• Indexing Service 

• Internet Information Service (partial) 

• Management and Monitoring Tools (partial) 

• Networking Services (partial) 

• Script Debugger 

Note: You can also select Windows Messaging and Games, if the customer wishes. 

9. Click Next to proceed. 

A tabbed Date and Time Settings screen appears. If you do not need to set the date 

and time, click Next, then skip to step 11. Otherwise continue with step 10. 

10. Click the Date, Time, and Time Zone tabs (in any order) for the changes you need to 

make. All are optional. Set the fields as follows: 

• Month—Click the arrow keys and select the correct month on the calendar. 

• Day of the month—Click the correct date to set it on the calendar. 

• Time—Click the scroll bar arrow and scroll up or down until the correct time 

appears. 

• Time zone—To change the time zone, click the scroll bar arrow and scroll up or 




• Daylight saving time—Click the check box to select daylight saving time if it 


Click Next when done with both the date and time. 

The Windows 2000 Server Setup screen indicates that Setup is installing the 

networking settings. 

11. A Networking Settings screen appears with the following check boxes: 

• Typical settings 

• Custom settings 

12. Select Custom settings, then click Next. 


detected. Follow the instructions below (the remainder of step 12) for the type of 

server you are installing. 


The detected device is the SysKonnect FDDI PCI Adapter SK-5544 [SK-NET…]. These 

default components are checked: 




Customize the ES5044R as follows: 

a. Select File and Print Sharing and click Properties. 

A Server Optimization box appears. 

b. Select Balance, then click OK. 

c. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. Configure 


1) Click the option “Use the following IP address.” 





in Table B-1. 








OK. 

7) Click OK. 




A screen appears with the next configurable device: the Intel(R)82559 Fast 

Ethernet LAN. 

d. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. Configure 








information. 




a) Click Add and type the address from Table 2–2. Click Add again. 







9) Click to uncheck “Register the connections added in DNS.” 



11) Click OK. 

12) Click OK. 


Skip to step 13. 


The detected device is the Intel[R] PRO/100+ Dual Port Server Adapter #2. These 

default components are checked: 





them. By default, this adapter is not used by ClearPath. 

Continue customizing the ES5085R as follows: 



a. Click Next. 

A screen appears with the next configurable device: the Intel[R] PRO/100+ Dual 

Port Server Adapter. The same default components are checked again (see 

bulleted list above). 

b. Select File and Print Sharing and click Properties. 


c. Select Balance, then click OK. 

d. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. Configure 








information. 




a) Click Add and type address from Table 2–2. Click Add again. 







9) Click to uncheck “Register this connection’s addresses in DNS.” 



11) Click OK. 

12) Click OK. 






e. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. Configure 


1) Click “Use the following IP address.” 





in Table B-1. 








OK. 

7) Click OK. 


Skip to step 13. 


The detected device is the SysKonnect FDDI PCI Adapter SK-5544 [SK-NET…]. 

Configure the adapter card as follows: 

a. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. 

b. Click “Use the following IP address.” 




address associated with that node number. The addresses are listed in 

Table B-1. 

c. In the IP Address field, type the appropriate FDDI address for this node (for 



d. In the Subnet Mask field, enter the address 255.255.255.0. 

e. Click the Advanced button. 

f. Click the Add button in the IP Addresses box. 

g. Enter the other two addresses and subnet masks from Table B–1. Then click OK. 

h. Click OK. 




A screen appears with the next configurable device: the IBM Netfinity Fault 

Tolerance PCI Adapter. The following default components are checked: 




Continue by configuring the Netfinity card: 

j. Select File and Print Sharing and click Properties. 


k. Select Balance, then click OK. 

l. Click Internet Protocol (TCP/IP) to highlight it, then click Properties. 

m. Click “Use the following IP address.” 

n. In the IP Address field, enter the IP address for the Windows 2000 Advanced node 


o. Change the subnet mask to the netmask address from Table 2–2, or skip this field 

(accept the default). 

p. If you have a gateway (router), tab to the Default Gateway field and type the 

gateway address from Table 2–2. 

q. Click Advanced and add any additional gateway entries that the site requires. 

r. If the site chooses to implement WINS, click the WINS tab (otherwise skip this 

step), then enter WINS information as follows: 

1) Click Add and type the address from Table 2–2. Click Add again. 

2) Enter any additional IP addresses from Table 2–2. 

s. Click the DNS tab. 

t. If the site has any DNS servers, click Add (otherwise skip this step). In the 

window that appears, enter the IP address for the first DNS server from Table 2–2; 

then click Add again. 

u. If applicable, click Add and enter any additional DNS servers. 

v. Click to uncheck “Register the connections added in DNS.” 

w. Leave the default selections for the DNS suffix as they are. (“Append 


x. Click OK. 

y. Click OK. 

z. Click Next. 

13. A Workgroup or Computer Domain screen identifies the host name of the Windows 

2000 node and asks whether the node is to participate in a workgroup or domain. 


a. Click No. 



b. Enter the workgroup name CLEARPATH in the box labeled Workgroup or 

computer domain. 

Note: You can enter a different workgroup name if the client site 

requirements are different 


The Windows 2000 Server Setup screen indicates that it is installing Windows 2000 

components. This may take several minutes. A progress bar shows the status of the 

installation. 

14. The Performing Final Tasks window appears briefly and displays the list below. 

Note: The displays in this step occur very quickly and may be easy to miss. 

ù Installs Start menu items 

ù Registers components 

ù Saves settings 

ù Removes any temporary files used 

Setup executes these tasks automatically and checks them off the list as they are 

completed. 

Finally, a Windows 2000 Server Setup screen appears briefly and displays the following 

messages: 

Completing the Windows 2000 Setup Wizard 

You have successfully completed Windows 2000 setup. 

If there is a CD in your drive, remove it. Then, to restart 

your computer, click Finish. 

15. Remove the CD-ROM, then click Finish. The server reboots automatically. 

16. After the server reboots, log on as the administrator (3.5). 

Note: If you are installing an ES5044R server, a Found New Hardware wizard 

may start for the ESG-SHV SCA HSBP M9 SCSI Processor device. Ignore it 

(do not close it) and wait for the Configure Your Server screen to pop up as 

detailed below. You will respond to the New Hardware wizard later. 

A menu labeled Windows 2000 Configure Your Server appears, giving three options: 

ù This is the only server in my network. 

ù One or more servers are already running in my network. 

ù I will configure this server later. 

17. Click “I will configure this server later.” Then click Next. 

18. Tab to “Show this screen at startup.” Click the box to remove the check mark. 

19. Close the Configure Your Server window. 

20. If you are installing an ES5044 and the Found New Hardware wizard has started, click 

Next on the wizard screen. Otherwise skip the remainder of these steps (21 through 

34). 

21. Click “Display a list…” to select it, then click Next. 

22. Click Other Devices to select it, then click Next. 



23. Click Have Disk and insert the Unisys Supplemental Drivers CD into the server’s drive. 

24. Click the Browse button and select the CD drive (D:) from the drop-down box. 

25. Double-click the win2000 folder. 

26. Double-click the platform folder. 

27. Double-click the es2044 folder. 

28. Double-click the HSB folder 

29. Click the ESGSHV file icon to select it, then click Open. 

30. Click OK. 

31. Click “Intel SCA Hotswap backplane” to select it, then click Next. 

32. Click Yes to the “Update driver warding” message 

33. Click Next. 


At this point, you should still be logged on as the administrator. Complete Windows 2000 

Advanced installation as described in 7.2. 

3.5. Logging On As the Administrator 

Caution 

To prevent unauthorized access to the Windows 2000 Advanced node following 

initial installation, the site must change the default password (administrator) to a 

different password. 

Whenever you restart or power on the Windows 2000 Advanced node during installation, 

the Windows 2000 Advanced Server logo appears and you are prompted to press Ctrl-Alt- 

Del to log on. Take the following steps to log on. 

Notes: 

• The logon information is case-sensitive. 

• If the Windows 2000 Advanced node is part of a domain, you must also enter a 

domain name. 

1. Press Ctrl-Alt-Del. 

A logon screen appears. 

2. Take the following steps to enter information on that screen: 

a. Press the Tab key to advance to the password field. 

b. Password—Enter administrator (the installation password). 

Note: The user name administrator is already displayed. 



c. Click OK. 

A Welcome to Windows 2000 Advanced window appears. 

3. Close the welcome window. 


Section 4 

Installing Windows NT Server, 

Enterprise Edition (ES5044R, 

ES5085R, and ES2024R) 

This section tells how to install and configure the Windows NT Server, Enterprise Edition 

operating system on an Intel server node. Section 7 describes additional steps you must 

take to complete Windows NT installation. A full installation, with the checklist in Table 

4–1 completed and all software media readily available, takes about 1 hour. 



ES5044R 

(ESR504141-GZN) 

ES5085R 

(ESR508151-GZN) 

Windows NT Server, Enterprise Edition (4.0) 

operating system 


or 


NTE4008-xxx 

RAD5003-P64 

RAD6002-P64 


Seagate 18GB disk drive HDM18110-CX1 





or 


NTE4008-xxx 

RAD5003-P64 

RAD6002-P64 


Fujitsu 18GB disk drive 

or 

Seagate 186B disk drive 

HDL1817-CX1 

HDM18110-CX1 


continued 


Installing Windows NT Server, Enterprise Edition (ES5044R, ES5085R, and 

ES2024R) 


ES2024R 

(ESR202141-Z) 




or 


NTE4008-xxx 

RAD5003-P64 

RAD6002-P64 


Seagate 18GB disk drive ES2024-18G 





Table 4–1. Windows NT Server, Enterprise Edition: ES5044R, ES5085R, and ES2024R 



4.4.1. Installing the Windows NT Server, Enterprise Edition Operating System 

Media needed: 

• Setup diskettes—labeled “Microsoft Windows NT Server Setup Disk x” (where x is 1, 2, and 3) 

• Windows NT CD-ROM—labeled “Microsoft Windows NT Server Enterprise Edition” 

• RAID drivers diskette—labeled “Mylex Solutions Software Kit...” 

• Symbios drivers diskette—labeled “Unisys Supplemental Drivers" (23389166-xxx) 

• For ES5085R only: Intel Ether Express drivers diskette—labeled “Intel Pro Dual Port Driver 

Diskette" (user-created) 



4.4.2. Configuring Windows NT Server, Enterprise Edition 

Media needed: 

User-created diskette for the installation of the Intel Pro Dual Port Ethernet adapter— labeled "Intel Pro 

Dual Port Driver Diskette." For instructions, see note following this table. 



Name __________________________ 

Determine the name the site wants identified with the Windows NT node (for example, the 

administrator’s name or the Windows NT owner name). 

Organization _____________________________ 

Determine the organization name the site wants identified with the Windows NT node. 



ES2024R) 

Table 4–1. Windows NT Server, Enterprise Edition: ES5044R, ES5085R, and ES2024R 



Registration screen 

CD-KEY ______________________________________ 

continued 

To register Windows NT, you need the key number printed on a label on the back of the Windows 

NT CD-ROM jewel case or on the Certificate of Authentication. 

SNMP Properties screen 

System administrator name __________________________ 

Phone number __________________________ 






Note: If you are installing an ES5085R server, you must prepare a driver diskette for 

the installation of the Intel Pro Dual Port Ethernet adapter in 4.4.2. You can 

prepare the diskette in either of two ways: 

• Download the diskette information from the Unisys Support page as a selfextracting 

executable. Label the new diskette "Intel Pro Dual Port Driver 

Diskette." 

–or– 

• On another DOS/Windows PC, copy the makems.bat run on the CD root of 

the Intel Pro CD that came with your system to create a diskette. For 

example, 

D:\makems.bat D: A: 

where D: is the drive name of the CD and A: is an empty or freshly 

formatted DOS-based diskette. Label the new diskette "Intel Pro Dual Port 

Driver Diskette." 



ES2024R) 


Caution 

To prevent installation problems or wasted time, determine whether Windows NT 

has been preloaded. Then follow either the procedure for preloaded software or 

the full installation procedure, as appropriate. 

To determine whether the Windows NT operating system is preloaded, power the Intel 

node on and allow it to fully boot. This takes about 2 minutes. 

Notes: 


in the correct bays as labeled on the disks. See the applicable server system map for 

the location and layout of the drive bays. 

• If you encounter any problems installing the RAD6002-P64 RAID card, refer to the 

Unisys Ultra160 RAID Adapter Driver Update Notice (4556 3947). 


DAC1100 found new configuration, it will 

reset to update configuration. 

DAC1100 reset complete. 

This message indicates that the RAID configuration saved in nonvolatile memory by the 

RAID controller does not match the current configuration. You must correct this error 

condition before you continue. If the message appears, take steps 1 through 10 below. 

Otherwise, skip to step 11. 

1. Press Alt-M to start BIOS Options Utility. A BIOS options menu appears: 


BIOS enabled 



Note: The BIOS should be enabled from the factory. 

If BIOS options are not set as above, continue with steps 2 through 6 as needed; 

otherwise, go to step 7. 


Enabled. 









ES2024R) 


5. Press Esc twice to quit the BIOS Option Utility. 














8. Use the arrow keys to select the Configure RAID Drive option, then press Enter. 



Automatic 

Assisted 

Custom 

Note: Unless noted otherwise, use the arrow keys to select menu options 

throughout the rest of this procedure. 

9. If there are no disks to configure, return to the EzAssist menu (step 7) and select 

Advanced Options; then select “clear configuration.” You will then be able to 

configure the RAID drive. 






Spare: No 





1:00 UNISYS ....... 17.0 Online 

1:01 UNISYS ....... 17.0 Online 



ES2024R) 











11. Press Ctrl-Alt-Del to reboot. 

The first Windows NT Setup window appears, followed by one or two reboots. 

12. Once the reboot (or second reboot, if you executed step 10 above) is complete, watch 

for the Windows NT Software License Agreement screen. If this screen appears, the 

operating system has been preloaded. 

If the operating system is preloaded, continue with 4.2. Otherwise, take the following 

steps: 


2. Install the Windows NT operating system (4.4). 

3. Log on to Windows NT (4.5). 


4.2. Steps to Take If Windows NT Is Preloaded 

Take the steps below to initially configure Windows NT when it is preloaded. 

Note: If you decide to perform a full installation even though the system is preloaded, 

do not format the RAID disk. Instead, use the DAC BIOS utility to initialize the 

RAID volume before you reload the operating system. Formatting the disk 

makes the drive unrecognizable to the software. 

1. Have the client, or a representative of the client, accept the license agreement. The 

Windows NT Software License Agreement should still be displayed on the screen. Do 

the following to accept the agreement: 


page. 

b. When you have read the entire agreement, click “I agree.” 

After a few seconds a Windows NT Setup screen appears. 


After a few more seconds, the Windows NT Setup screen reappears, followed by a 

Name and Organization screen. 



ES2024R) 


a. Name field—Enter the user name the site wants identified with the Windows NT 

node. 



Windows NT node. 








The Computer Name screen appears. 

Note: This name (up to 15 characters) is the Network Basic Input/Output System 

(NETBIOS) name that uniquely identifies the computer in the Windows NT 

workgroup or domain. It must be different from the workgroup or domain 

name. 

4. In the Name field, enter the host name from Table 2–2 by which the Windows NT node 

will be identified on the external TCP/IP network. Click Next to proceed to the next 

screen. 

The Server Type screen appears. 

5. Click Stand Alone (the ClearPath default) or the option requested by the site. (See 

Table 2–1.)Click Next to proceed, then click Next again. 

Note: In this step, the client may elect to install the server as a primary domain 

controller (PDC) or backup domain controller (BDC), rather than a standalone 

server. In this case, however, additional steps must be taken that are 

not described in this procedure (see Table 2–1). 

The Administrator Account screen appears. 

6. Enter and confirm the password for the administrator’s account as follows: 

a. In the Password field, type the password administrator. 

b. Press the Tab key to go to the Confirm Password field. Type administrator in 

that field. 




After about 1 minute, a Windows NT Setup screen for configuring networking appears. 


The setup program searches for network adapters. After a brief wait, an error message 

appears: 



ES2024R) 

The IP Address key has an invalid IP address. 

Please correct the problem after the property sheet is displayed. 

8. Click OK. 

After about 1 minute, a tabbed Microsoft TCP/IP Properties screen appears. 

9. Configure the FDDI network adapter card as follows: 

a. Use the scroll bar to select the following adapter from the drop-down list of 

adapters: 

SK-NET FDDI PCI Adapter 

b. Click the IP Address tab, then enter IP address information as follows: 

1) Click “Specify an IP address.” A dot appears in the circle to indicate it is 

selected. 





in Table B-1. 



then press Tab. 

3) A default address of 255.255.255.0 may be automatically calculated for the 

Subnet Mask field. Verify that the address has this value. (Edit it, if 

necessary.) 

c. Click the Advanced button. 


2) Enter the other two addresses and subnet masks for Windows NT from Table 

B-1. 

3) Click OK. 

10. Configure the Ethernet network adapter card as follows: 

a. Use the scroll bar to select the appropriate adapter from the drop-down list of 

adapters: 

For the ES5044R or ES5085R: 

Intel Pro/100+ Dual Port Adapter [port 1] 

For the ES2024R: 

AMD Pcnet PermaNet Server LFT Adapter 

b. Click the IP Address tab, then enter the following IP address information: 

1) Click “Specify an IP address.” 

2) In the IP Address field, enter the IP address for the Windows NT node from 

Table 2–2, then press Tab. 

3) Change the subnet mask to the netmask address identified in Table 2–2, or 

skip this field (accept the default). 



ES2024R) 

4) If you have a gateway (router), click Advanced and take the following steps: 

5) Click Add. 

6) In the Gateway address field of the Gateways section, type the gateway 

address identified in Table 2–2. 

7) Click Add. 

The address appears in the gateways list box. 

8) Repeat these steps for each additional gateway required, then click OK when 

done. 

c. If the site chooses to implement WINS, click the WINS Address tab (otherwise 

skip this step), then enter the following WINS information: 

1) In the Primary WINS Server field, type the address identified in Table 2–2, then 

press Tab. 

2) If applicable, type the IP address of the Secondary WINS Server identified in 

Table 2–2. 

d. Click the DNS tab and take the following steps: 

1) Enter the IP address for the first DNS server from Table 2–2, if the site has any 

DNS servers. 

2) Click Add. 

The DNS address is added to the search order list box. 

3) Repeat these steps for each additional DNS server. 

4) Enter a domain name, if possible, for proper operation of the IIS services. 

e. Click the Routing tab. Then click “Enable IP forwarding” to clear the check box if 

it is not already clear. This ensures the security of the HMP interconnect. You 

must not enable IP forwarding. 

f. ES5085R only:Use the scroll bar to select the second port (Intel Pro/100+ Dual 

Port Adapter [port 2]) from the drop-down list of adapters. Then repeat steps b 

through d above if the second port will be used. (By default, it is not.)When 

finished, continue with step 14. 

11. Click OK. 

The following message appears if (and only if) you have selected to install WINS: 

At least one adapter card has an empty WINS address. 

Do you want to continue? 

12. Click YES. 

Windows NT loads files and configures the network, and then the tabbed date/time 

properties screen appears. 

13. Click “Time zone” and, if necessary, take the following steps for each field: 

a. Time zone—To change the time zone, click on the scroll bar arrow and scroll up or 


b. Daylight saving time—Click the check box to select daylight saving time if it 




ES2024R) 

14. Click the Date and Time tab and, if necessary, take the following steps for each field: 

a. Month field—Click the scroll bar arrow and scroll up or down to select the correct 

month. 

b. Year field—Click the scroll bar arrow and scroll up or down to select the correct 

year. 

c. Day of the month—Click the correct date to set it on the calendar. 

d. Time—Click the scroll bar arrow and scroll up or down until the correct time 

appears. 

e. Click Close when done with both the date and time. 

Files are copied from the CD-ROM; then Windows NT service-pack setup starts. When 

installation is complete, a screen with a message similar to the following appears: 

One of more minor errors occurred installing... 

15. Click No. 


Windows NT has been installed successfully. 

Remove floppies and choose Restart Computer. 

16. Click Restart Computer. 

After a few minutes, the Windows NT Server logo appears and you are prompted to 

press Ctrl-Alt-Del to log on. 

17. Log on (4.5). Close the Welcome window when it appears. You will see that Internet 

Explorer Active Setup is started. It will automatically install the needed components. 

After the installation completes, your server is automatically rebooted. 

18. When the automatic reboot completes, log on as the administrator again (4.5). 

Microsoft Internet Explorer Setup runs once more. 

A window saying Welcome to Windows NT appears. 

19. Close the Welcome window. 

A window appears with the following message: 

Microsoft Windows NT Server, Enterprise Edition Installer 

You have successfully set up Microsoft Windows NT Server, Enterprise 

Edition. If you have more than 256 Megabytes of RAM, restart your 

computer so your system can gain access to that memory. For instructions 

on enabling 4GB RAM Tuning (4GT), see the Windows NT Server/E 

Administrator’s Guide. You can find this guide in two places: in 

\Support\Books\NTSEAdm.hlp and in the readme.doc file in the root 

directory of the Windows NT Server/E Base CD. 

20. Click OK. 

A window appears displaying Microsoft Windows NT Server, Enterprise Edition 

Installer. 

21. Clear the check box “Show this installer next time you start Windows NT.” 



ES2024R) 

22. Click Continue, then click Exit. 

A prompt asks, “Are you sure?” 

23. Click Yes. 

Continue by configuring the hosts file (7.1.3). 



Sites can reconfigure a different RAID level following hardware RFU if desired. For 


ROM labeled "Mylex Solutions Software Kit x.xx." 

Notes: 


2.5.2). 





• In step 2, you must press Alt-M within a few seconds to enter the BIO Options 

Utility. 


configuration procedure; otherwise, the normal boot procedure continues. See next 

note for ES2024R server. 

• For the ES2024R server, before you press Alt-R, you must press Alt-M to access the 

BIOS options utility. Then press Alt-R in order to access the Mylex RAID EzAssist 

utility, as instructed in step 8. 



Several start-up messages appear, including a prompt to press Alt-M, as follows: 






> 



ES2024R) 

2. Immediately press Alt-M to start the BIOS Options Utility. A BIOS options menu 

appears: 


BIOS enabled 






Enabled. 













8. Immediately press Alt-R to start the Mylex RAID EzAssist utility. 








9. Select the Configure RAID Drive option using the arrow keys, then press Enter. 



Automatic 

Assisted 

Custom 





ES2024R) 









Spare: No 





1:00 UNISYS ....... 17.0 Online 

1:01 UNISYS ....... 17.0 Online 

Make sure Apply is highlighted, then press Enter. 











12. Insert the Windows NT Setup diskette 1 in the drive. 


Continue by installing and configuring Windows NT as described in 4.4. 


Enterprise Edition 

The Windows NT Server, Enterprise Edition, installation process consists of an installation 

phase (4.4.1) in which prompts appear as text messages and a configuration phase (4.4.2) 

in which prompts are presented as graphical screens. The following subsections describe 

the steps to take during each phase. 

Notes: 


2.5.2). 



ES2024R) 


After hardware RFU, the site may wish to customize the configuration to meet their 

needs. 


Operating System 

Begin Windows NT Server, Enterprise Edition installation as follows: 

1. Insert the diskette labeled “Microsoft 1-x CPU Edition Setup Disk 1” into the drive unit. 

2. Reboot or turn power on the Intel node. 

After the hardware initialization messages are displayed, the following message 


Windows NT Setup 

================ 

After about 2 minutes, you are prompted to insert the next setup disk. 


================ 

Please insert the disk labeled 

Windows NT Server Setup Disk #2 

into Drive A: 

*Press ENTER when ready 

3. Insert the diskette labeled “Microsoft 1- x CPU Edition Setup Disk 2” into the drive, 

then press Enter. 

After 1 minute, a message similar to the following appears briefly: 

Microsoft(R) Windows NT(TM) Version 4.0 (Build xxxx). 

1 System Processor [xxx MB memory] Multiprocessor Kernel 

The Setup welcome menu appears. 

4. Press Enter to begin setting up Windows NT. 

A screen appears asking whether you want to skip mass storage autodetection. 

5. Enter S to skip autodetection and manually select the SCSI adapter. 

A screen appears to indicate that no adapter has been found or selected. 

6. Enter S to manually specify the SCSI adapter. 

A window for selecting an adapter appears. 

7. Select adapters in that window as follows: 

a. Press Enter to select the highlighted Other entry. You are prompted to insert a 

diskette containing the controller drivers. 

Windows NT Server Setup 

======================= 




ES2024R) 

Manufacturer - supplied hardware support disk 

into Drive A: 


b. Insert the diskette containing the RAID drivers labeled “Mylex Solutions Software 

Kit x.xx NX/NW Drivers Diskette” and press Enter to continue. 

After a brief wait, the Mylex…Disk Array Controller drivers are listed in the 

adapter window. 

c. If you have the DAC1100 RAID Controller, select the highlighted “Mylex 

DAC960…Disk Array Controller” entry. If you have the AcceleRAID 352 RAID 

Controller, select “Mylex EXR2000/3000…Disk Array Controller. Then press 

Enter. 

A message indicates that Setup has recognized the Mylex adapter. 

d. If you are installing the ES2024R or ES5044R, skip to step j. 

e. Enter S to specify an additional SCSI adapter. 

The adapter selection window reappears. 

f. Press Enter to select the highlighted Other entry. You are prompted to insert a 

diskette containing the controller drivers diskette. 


======================= 



into Drive A: 


g. Insert the Unisys diskette labeled “Unisys Supplemental Drivers” (23389166- xxx) 

and press Enter. 

h. After a brief wait, the Symbios driver is listed in the adapter window. 

i. Press Enter to select the highlighted “Symbios PCI High Performance Driver” 

entry. 

A message indicates that Setup has recognized the Symbios adapter. 

j. Enter S to specify an additional SCSI adapter. 


k. Use the up and down arrow keys to select IDE CD-ROM (ATAPI 1.2)/PCI IDE 

Controller. 

l. Press Enter to select the highlighted entry (IDE CD-ROM…). 

You are prompted to insert disk 3, as follows: 


======================= 





ES2024R) 

into Drive A: 


8. Insert the diskette labeled “1- X CPU Edition Setup Disk 3” in the drive, then press 

Enter to continue. 

A message indicates that setup has recognized all of your adapters. 

9. Press Enter to continue. 

The following message appears at the top of the screen, followed by a message 

confirming that the adapters have been recognized. 


======================= 

Setup has detected that one or more of your hard disks has more than 1024 

cylinders 

10. Press Enter again. 

A message states that Setup has detected that your computer’s hard disk is new. 

11. Press C to continue. 

You are prompted to insert the CD-ROM. 

12. Insert the CD-ROM and wait for the drive light to stop flashing; then press Enter. 

A license agreement text screen then appears. 

13. Read the contents of the license agreement as follows: 


page. 

b. When you reach the last page, press F8 to indicate that you agree with the terms of 

the license agreement . 

A hardware and software components list appears for you to verify. 

14. Be sure that the Computer line reads “MPS Multiprocessor PC.” If it does not, use the 

arrow keys to move to that line, press Enter, and change as needed. 





ES2024R) 


==================== 

The list below shows existing partitions and spaces available for 

creating new partitions. 

Use the UP and DOWN ARROW keys to move the highlight to an item 

in the list. 

To install Windows NT on the highlighted partition 

or unpartitioned space, press ENTER. 


To delete the highlighted partition, press D. 


ENTER=Install C=Create Partition F1=Help F3=Exit 

16. Use the arrow key to highlight “Unpartitioned space,” then press C to create a new 








19. Use the up and down arrow keys to select the NT file system (NTFS), then press Enter. 

A message indicates that the disk is being formatted. After format finishes, a message 

appears asking for the directory in which to install Windows NT. 

20. Press Enter to accept the default directory (WINNT). 

A message asks whether you want an exhaustive examination of the hard drives. 

21. Press Enter to perform an exhaustive examination of the hard disk. 

The examination takes a few seconds. Then the following message appears: 


======================= 


Mylex Software Kit x.xx (NT4) 

into Drive A: 


22. Insert the diskette containing the RAID drivers labeled “Mylex Solutions Software Kit 

x.xx …," then press Enter to continue. 



ES2024R) 

If you are installing an ES2024R or ES5044R, skip to step 24. 

If you are installing an ES5085R, the following message appears: 


======================= 


NT 4.0 Supplementary Driver Disk 1 

into Drive A: 


23. Insert the diskette labeled “Unisys Supplemental Drivers” (23389166-002), then press 


Setup begins copying files. When the files are copied, a message asks you to remove 

the diskette in preparation for rebooting. 

24. Remove the diskette and the CD-ROM from the drives, then press Enter. 

Two reboots occur. First Windows NT boots using the file allocation table (FAT) file 

system. Then the FAT file system is converted to the desired NTFS and Windows NT 

reboots again. 

25. If you are installing an ES2024R, a virus check messages appears. Press Enter to 

continue. 

Following reboot, the Windows NT Setup GUI screen appears. Continue by configuring 

Windows NT as described in 4.4.2. 


This procedure follows immediately after, and is continuous with, the installation 

procedure in 4.4.1. 

For an ES5085R, this procedure requires the "Intel Pro Dual Port Driver Diskette" created 

earlier by the user. See the note following Table 4–1 for instructions. 

After the Windows NT operating system reboots (4.4.1), a Windows NT Setup screen 

appears with a message box instructing you to insert the Windows NT CD-ROM. Take the 

following steps: 

1. Insert the Windows NT CD-ROM (labeled “Microsoft Windows NT Server Disc 1”) into 

the drive, then click OK. 

If you click OK before the drive is ready, a prompt indicates that files are needed from 

the Windows NT Server CD-ROM. A scroll box identifies the directory from which 

they will be copied. Click OK in the box if this occurs. 

After a few seconds, a Windows NT Setup screen indicates that setup includes 

• Gathering information about your computer 

• Installing Windows NT networking 

• Finishing setup 

2. Click Next to proceed to the next screen. 



ES2024R) 

A Name and Organization screen appears. 




c. Organization field—Enter the organization responsible for the Windows NT node. 


A registration screen appears asking for the registration number from the 

Certificate of Authentication. 






5. Click the Per Seat licensing option, then click Next to proceed. 





name. 



screen. 


Note: In the following step, the client may elect to install as a primary domain 

controller (PDC) or backup domain controller (BDC), rather than standalone 

server; however, additional steps must be taken which are not 

described in this procedure (see Table 2–1). 

7. On the Server Type screen, click Stand-alone Server (or the selection from Table 2–1), 

then click Next to proceed. 

8. When the Administrator Account screen appears, enter and confirm the password for 

the administrator’s account as follows: 



that field. 




An Emergency Repair Disk screen appears. 

9. Click No. Then click Next to proceed. 



ES2024R) 

Note: You will create the emergency repair disk later. Have a labeled diskette 

ready for that purpose. 

The Select Components screen appears with the following defaults selected: 

• Accessibility options 

• Accessories 

• Communications 

• Multimedia 

Note: You can also select Windows Messaging and Games if desired by the site. 


The Windows NT Setup screen indicates that installing Windows NT networking is 

about to begin. 


A screen appears with the option “Computer will participate in network” selected. The 

following check boxes also appear: 

• Wired to the network 

• Remote access to the network 

12. Select Wired to the network, then click Next. 

A screen appears with a check box labeled “Install Microsoft Internet Information 

Server” already checked. 


A screen for selecting network adapters appears. 

14. Select network adapters as follows: 

Perform steps a through g for ES5085R only: 

a. Click “Start search.” 

The SysKonnect SK-NET FDDI PCI adapter is detected and added to the list box. 

b. Click “Select from list.” 

c. Click “Have disk.” 

d. Insert the diskette labeled “Intel Pro Dual Port Driver Diskette” in the drive. (For 

information on creating this diskette, see the note following Table 4–1.) 

e. Click OK. 

The Intel EtherExpress PRO adapter is detected and both ports are displayed in 

the list box. 

f. Click OK. 

Both adapter types (Syskonnect FDDI and Intel PRO) should now be listed. 

g. Click Next. 

Perform steps h through j for the ES2024R only: 



ES2024R) 

h. Click “Start search.” 

The AMD PCNET Family Ethernet Adapter is detected and added to the list box. 

i. Click “Find next.” 


Both adapters (AMD PCNET and Syskonnect) should now be listed. 

j. Click Next. 

Perform steps k through q for the ES5044R only: 

k. Click “Select from list.” 

l. Click “Have disk.” 

m. Insert the diskette labeled “Supplemental Drivers Diskette.” 

n. Click OK. 

The Intel(R)82559 Fast Ethernet Lan on Motherboard is detected and added to the 

list box. 

o. Click OK. 

p. Click “Find next.” 


q. Click Next. 

A Network Protocols screen appears. The only required protocol is the TCP/IP 

protocol. The NWLink IPX/SPX compatible transport and NetBEUI protocol are not 

required for initial installation, but they may be selected if required by the site. 

15. Deselect any protocols not required. 

16. Ensure that the TCP/IP protocol is selected. If it is not, click TCP/IP Protocol to select 

it. 


A screen for selecting Network services appears. The following networking 

components are listed in the list box by default: 

• Microsoft Internet Information Server 2.0 

• Remote procedure call (RPC) configuration 

• Network Basic Input/Output System (NETBIOS) Interface 

• Workstation 

• Server 

In addition, the following network services are required: 

• Simple TCP/IP service. 

• Simple Network Management Protocol (SNMP) service. (The SNMP agent 

package is needed for SysAdmin.) 



ES2024R) 

18. Add the additional services to the list as follows: 

a. Click “Select from list . . .” 

b. Scroll down the list of services (use the scroll bar) and highlight Simple TCP/IP 

Service. 

c. Click OK. 

The service is added to the list of services already in the list box. 

d. Repeat steps a, b, and c for SNMP Service. 

e. Review the list of services to ensure that it contains the following: 





• Server 

• Simple TCP/IP service 

• SNMP service 

f. Click Next to proceed. 

A Windows NT Server Setup screen indicates that Windows NT is now ready to install 

networking components. 


20. For the ES5085R only, a screen for setting FDDI parameters appears. 

Click Continue to accept the defaults. 

21. Depending on the server model you are installing, either Intel PRO or AMD PCNET PCI 

adapter information is displayed. Click Continue. 

Note: For the ES5085R, two adapters should be detected. 

22. If you are installing an ES2024R or ES5044R, a screen for setting FDDI parameters 

appears. 

Click Continue. 

23. If you are installing an ES5085R, click OK. 

24. For both server types, installation of networking components begins. A message box 

asks if you want to use Dynamic Host Configuration Protocol (DHCP) server. 

25. Click No. 

Messages indicate software is being installed. After about 1 minute, you are prompted 

with a tabbed SNMP Properties screen. 

26. Set the SNMP properties as follows: 

a. Agent tab—Click this tab, then enter the name and location of the system 

administrator. Accept the service defaults (Applications, Internet, and End-to- 

End). 



ES2024R) 

b. Security tab—Click this tab, then clear the check box labeled Send Authentication 

Trap. Leave the Accept SNMP Packets from Any Host option set. 

c. Click OK. 

d. If you select IPX/SPX protocol (see step 16), you are prompted to assign a unique 

network number to one of the adapters. 

After about a minute, a tabbed Microsoft TCP/IP Properties screen appears. 



adapters: 



1) Click “Specify an IP address” to select it. 





in Table B-1. 





c. Click Advanced. 



B–1. 

3) Click OK. 


a. Click the IP Address tab. 

b. Use the scroll bar to select one of the following: 

• For the ES5044R, the Intel EtherExpress Pro 

• For the ES5085R, the Intel EtherExpress PRO adapter Bus 3 slot 4 from the 

drop-down list of adapters 

• For the ES2024R, the AMD PCNET PCI Ethernet Adapter 

c. Enter the following IP address information: 

1) Click “Specify an IP address.” 

2) In the IP Address field, enter the IP address for the Windows NT node from 






ES2024R) 

4) If you have a gateway (router), click Advanced (otherwise skip this step) and 

take the following steps: 

a) Click Add. 

b) In the New Gateway field, type the gateway address from Table 2–2. 

c) Click Add. 

The address appears in the Installed gateways: list box. 

d) Repeat these steps for each additional gateway required, then click OK 

when done. 

d. If the site chooses to implement WINS, click the WINS Address tab (otherwise 


Note: Be sure the Ethernet adapter is selected, and not the FDDI adapter. 

WINS should not be used on the FDDI interconnect. 

1) In the Primary WINS Server field, type the address from Table 2–2, then press 

Tab. 

2) If applicable, type the IP address of the Secondary WINS Server from Table 

2–2. 

e. Click the DNS tab and take the following steps: 


DNS servers. 

2) Click Add. 



4) Enter a domain (Internet) name to which the server belongs, for proper 

operation of the IIS services. 

f. If you are installing an ES5085R, use the scroll bar to select the second port of the 

Intel Ether Express Pro adapter Bus 3 slot 5 from the drop-down list of adapters. 

Then repeat steps 25(c) through 25(e) above. 

g. For both server types, click OK and continue with step 29 when finished. 


A screen appears that allows you to confirm the network bindings. 


A screen appears indicating that Windows NT is ready to start the network. 


32. A setup screen identifies the host name of the Windows NT node and asks whether the 

node is to participate in a workgroup or domain. 

Click Workgroup, enter a workgroup name of CLEARPATH, then click Next to 

proceed. 

You can enter a different workgroup name if the client site requirements are different. 

The Windows NT Setup screen indicates it is ready to finish the setup. 



ES2024R) 


A message indicates that Setup is configuring Windows NT. Then a Microsoft Internet 

Information Server 2.0 Setup screen appears. 

34. Configure Internet Information Server (IIS) properties as follows: 

a. Click OK to accept the defaults. 

A prompt asks if you want to create an inetsrv directory. 

b. Click Yes to create the directory. 

A list of publishing directories appears. 

c. Click OK to accept the default Publishing Directories. 

A prompt says directories do not exist. 

d. Click Yes to create the directories. 

Directories are created and a prompt appears to install drivers. 

e. Click SQL Server, then click OK to install the ODBC driver. 

Files are copied, then a tabbed Date/Time Properties screen appears. 

35. Click the Time Zone tab and, if necessary, take the following steps for each field: 

a. Time zone—To change the time zone, click the scroll bar arrow and scroll up or 






month. 


year. 



appears. 


A message box appears that indicates the type of video adapter that was detected. 

37. Click OK to continue. 

A screen appears for configuring the video display. 

38. Configure the video display as follows: 

a. Click Test to ensure that the default settings work. 

A message box indicates that a test will be performed with the video mode 

selected (default VGA mode with 256 colors for ES5085R or ES5044R, 16 colors for 

ES2024R). 

b. Click OK to proceed. 



ES2024R) 

A color test pattern briefly appears followed by a message box asking if you saw 

the test pattern properly. 

c. Click Yes if you saw the pattern correctly. 

A message box instructs you to click OK to save the settings. 

d. Click OK to save the display properties settings. 

You are returned to the display properties screen. 

e. Click OK to proceed. 

Files are copied from the CD-ROM. Messages indicate progress. 

When the installation is complete, a screen with a message like the following appears: 

One or more minor errors occurred installing ... 

39. Click No. 

Then the following message appears. 

Windows NT 4.00 has been installed successfully. 

Remove disks from floppy drives and choose Restart Computer. 

40. Remove the diskette and the CD-ROM from the drive units, then click Restart 

Computer. 

Ignore messages for selecting the Windows NT mode and allow Windows NT to start 

automatically. The Windows NT Server logo appears and a message box prompts you 

to press Ctrl-Alt-Del to log on. 


A logon dialog box appears. 

42. Log on as described in 4.5. 

The Windows NT desktop appears with a Welcome to Windows NT screen. 

Following logon, you can complete Windows NT installation as described in Section 7. 



ES2024R) 


Caution 

To prevent unauthorized access to the Windows NT node following initial 

installation, the site must change the default password (administrator) to a 


Whenever you restart or power on the Windows NT node during installation, the Windows 

NT Server logo appears, and you are prompted to press Ctrl-Alt-Del to log on. Take the 

following steps to log on: 

Notes: 


• If the Windows NT node is part of a domain, you must also enter a domain name. 







c. Click OK. 

A Welcome to Windows NT window appears. 




ES2024R) 


Section 5 

Installing Windows NT Server, 

Enterprise Edition (ES2045R) 

This section tells you how to install and configure the Windows NT Server, Enterprise 

Edition operating system on an Intel server node. Section 7 describes additional steps you 

must take to complete Windows NT installation. A full installation, with the checklist in 

Table 5–1 completed, and all software media readily available, takes about 1 hour. 



ES2045R 

(VX1501/1505) 



NTE4008-xxx 

MegaRAID Ultra PCI RAD302-PCI 


Intel EtherExpress PRO ETH1010051-PCI 

Fujitsu 9GB disk drive HDS917-CX1 






Installing Windows NT Server, Enterprise Edition (ES2045R) 

Table 5–1. Windows NT Server, Enterprise Edition ES2045R Installation Checklist 


5.4.1. Installing the Windows NT Server, Enterprise Edition Operating System 

Media needed: 


• Windows NT CD-ROM—labeled “Microsoft Windows NT Server Enterprise Edition” 

• RAID drivers diskette—labeled “Windows NT 4.0/3.51 Driver MEGARAID.SYS...” 

• Symbios drivers diskette—labeled “DRIVER-SDMS PCI SCSI NT 896 Driver” (23381676–000) 

• Intel Ether Express drivers diskette—labeled “Aquanta DR2 Ether Express PRO 100+” (38160685– 

001) 

• (MSCS only) Adaptec drivers diskette—labeled “Adaptec 7800 Family Manager Set 3.02” 

(23382849–000) 



5.4.2 Configuring Windows NT Server, Enterprise Edition 



Name __________________________ 



Organization _____________________________ 



CD-KEY ______________________________________ 





Phone number __________________________ 









Caution 

To prevent installation problems or wasted time, determine whether Windows 

NT has been preloaded. Then follow either the procedure for preloaded 

software or the full installation procedure, as appropriate. 

To determine whether the Windows NT operating system is preloaded, 

1. Power on the Intel node and allow it to fully boot (takes about 2 minutes). 

2. If the Windows NT Software License Agreement screen appears, the operating system 

is preloaded. 

If Windows NT is preloaded, perform the steps described in 5.2, Steps to Take If Windows 

NT Is Preloaded. Then complete the installation as described in Section 7, Completing 

Windows NT Installation. 

If Windows NT is not preloaded, 






You must take the steps below to initially configure Windows NT when it is preloaded. 

Notes: 


in the correct bays as labeled on the disks. See the QR/2 system map for the location 

and layout of the drive bays. 

• If you decide to perform a full installation even though the system is preloaded, do 

not format the RAID disk. Instead, use the DAC BIOS utility to initialize the RAID 





Configuration of NVRAMM and drives mismatch 

Run View/Add Configuration option of configuration utility 

Press any key to enter the Configuration Utility 



That message indicates that the RAID configuration saved in nonvolatile memory by 

the RAID controller does not match the current configuration. Take the following 

steps to correct the problem. (If the message does not appear, proceed to step 2.) 

a. As indicated by the message, press any key to enter the configuration utility. 

The Management Menu for configuring RAID appears as follows: 

----Management Menu---- 

Configure 

Initialize 

Objects 

Format 

Rebuild 

Check Consistency 

Disable BIOS 

b. Select Configure, then press Enter. 

A Configure Menu appears as follows: 

------Configure----- 

Easy Configuration 

New Configuration 

View/Add Configuration 

Clear Configuration 

c. Select View/Add Configuration, then press Enter. 

A popup menu appears. 

d. Select View Disk Configuration, the press Enter. 

A screen similar to Figure 5–1 appears, except the disks say ONLIN A1-1 and 

ONLIN A1-2 instead of READY. 

e. Press F10. 

A Save Configuration? menu appears. 

f. Select YES, then press Enter. 

You are returned to the previous menu. 

g. Press any key to continue. 

h. Press Esc three times to back out of all menus. 

The following prompt appears: 

------EXIT?----- 

YES 

NO 

i. Select YES, then press Enter. 

j. Press Ctrl-Alt-Del to reboot. 





follows: 


page. 

b. When you have read the entire agreement, click I agree. 


After a few seconds, a Windows NT Setup screen appears, followed by a Name and 


3. Enter Name and Organization as follows. 


node. 















name. 



screen. 


6. Click Stand Alone (the ClearPath default) or the option requested by the site (see 

Table 5–1). Then click Next to proceed. 

Note: In this step, the client may elect to install as a primary domain controller 

(PDC) or backup domain controller (BDC), rather than a stand-alone 

server. In this case, however, additional steps must be taken that are not 








that field. 






After a brief wait during which the setup program searches for network adapters, the 

following message appears: 

SK-NET FDDI PCI Adapter Card Setup 

Continue Cancel Help 

9. Click Continue. 

An error message appears as follows: 

The IP Address key in the TCP/IP section of the database must be set to a value. 

Please correct the problem after the property sheet is displayed. 

10. Click OK. 




adapters: 



• Click Specify an IP address (a dot appears in the circle to indicate it is 

selected). 





in Table B-1. 

• In the IP Address field, type the appropriate FDDI address for this node (for 



• A default address of 255.255.255.0 is automatically calculated for the Subnet 

Mask field. Do not change that address. 



adapters: 

Intel Pro/100+ Server Adapter 


• Click Specify an IP address. 



• In the IP Address field, enter the IP address for the Windows NT node from 


• Change the subnet mask to the netmask address identified in Table 2–2, or 


• If you have a gateway (router), click Advanced and take the following steps: 

• Click Add. 

• In the New Gateway field, type the gateway address identified in Table 2–2. 


The address appears in the Installed gateways list box. 

• Repeat these steps for each additional gateway required, then click OK when 

done. 



• In the Primary WINS Server field, type the address identified in Table 2–2, then 

press Tab. 

• If applicable, type the IP address of the Secondary WINS Server identified in 

Table 2–2. 



DNS servers. 

2) Click Add. 






must not enable IP forwarding. 

14. Click OK. 

The following message appears if (and only if) you have selected to install WINS: 

At least one adapter card has an empty WINS address. 



Windows NT loads files and configures the network, and then the tabbed date/time 

properties screen appears. 

16. Click the Time zone tab and, if necessary, take the following steps for each field: 

a. Time zone—To change the time zone, click on the scroll bar arrow and scroll up or 








month. 


year. 



appears. 


Files are copied from the CD-ROM. Now Windows NT service-pack setup starts. 

Messages appear to indicate progress. When installation is complete, a screen with a 

message like the following appears: 

One of more minor errors occurred installing... 

18. Click No. 





After a few minutes, the Windows NT Server logo appears and you are prompted to 


20. Log on (5.5). Close the Welcome window when it appears. You will see that Internet 

Explorer Active Setup is started. It will automatically install the following 

components: 

• Internet Explorer Web Browser 

• Communications Components 

• Multimedia Components 

• Web Authorizing Components 

• Additional ActiveX Controls 

After the installation completes, your server is automatically rebooted. 

21. When the automatic reboot completes, log on as the administrator again (5.5). 

Microsoft Internet Explorer Setup runs. 


22. Close the Welcome window, and also close the Welcome – Microsoft Internet Explorer 

window. 









Administrator’s Guide. You can find this guide in two places: in 



23. Click OK. 

A window appears displaying Microsoft Windows NT Server, Enterprise Edition 

Installer. 



A prompt asks if you are sure. 


Continue by configuring the hosts file (7.1.3). 




detailed information see the MegaRAID and MegaRAID Ultra PCI SCSI Disk Array 

Controller User’s Guide. 

Notes: 


2.5.2). 





• In step 2, you must press Ctrl-M within a few seconds to enter the RAID controller 

configuration procedure, otherwise the normal boot procedure continues. 



Several start-up messages appear including a prompt to press Ctrl-M as follows: 

MEGARAID ULTRA PCI ADAPTER BIOS VERSION x.xx 

Copyright(c) AMERICAN MEGATRENDS INC. 




> 

2. Press Ctrl-M to start the RAID BIOS configuration utility. 



A Management Menu for configuring RAID logical arrays appears as follows: 

----Management Menu---- 

Configure 

Initialize 

Objects 

Format 

Rebuild 

Check Consistency 

Disable BIOS 

3. Select the Configure option using the arrow keys, then press Enter. 

A Configure menu appears: 

------Configure----- 

Easy Configuration 


View/Add Configuration 

Clear Configuration 



4. Select Clear Configuration, then press Enter. 

The following prompt usually appears: 

Clear Configuration? 

YES 

NO 

5. If the prompt in step 4 appears, highlight YES, then press Enter. 

Note: You may instead receive a message “no existing configuration to clear.” If 

so, proceed to step 6. 

6. Press any key to continue. 

7. Select the Easy Configuration option, then press Enter. 

After a brief wait, an Easy Configuration–ARRAY SELECTION MENU appears 

showing the available disk drive units (Figure 5–1 shows two units available). 

Note: The CD-ROM position in Channel-3 may be at 6 instead of 4. 


ID 

0 

1 

2 

3 

4 

5 

6 


MegaRAID BIOS Configuration Utility Ver 1.20 Oct 10, 1995 Adapter-1 

Easy Configuration - ARRAY SELECTION MENU 

Channel-1 Channel-2 Channel-3 

ID 

ID 

0 

0 READY 

1 

2 

3 

4 

5 

6 

Ch-1 ID-0 DISK 2049MB SEAGATE 32155W 0498 

Ch-1 ID-0 DISK 4149MB UNISYS 003557M2954C-512 0641 

7850 5104–009 Version 009B (Web Only) 5–11 

1 

2 

3 

4 

5 

6 

READY 

CDROM 

PROC 

SPACE-Array,ENTER-Configure,F2-Drive Information,F3-Logical Drives,F4-HotSpare 

Figure 5–1. Easy Configuration—ARRAY SELECTION MENU 

8. Select the first drive unit (ID 0), then press the spacebar. 

The ID 0 drive indicator changes from READY to ONLIN A1-1. A1-1 (which blinks) 

indicates that drive unit 1 is selected for array 1. The cursor automatically moves to 

the next drive unit. 

9. Select the Channel-3 ID 1 drive unit, then press the spacebar to select that drive unit 

for array 1. 

The ID 1 drive indicator changes from READY to ONLIN A1-2. 

10. Press Enter to stop selection of the drive units. 

A Logical Drives Configured window appears together with a smaller Logical Drive 1 

menu (Figure 5–2).


MegaRAID BIOS Configuration Utility Ver 1.20 Oct 10, 1995 Adapter-1 

ID 

0 

1 

2 

3 

4 

5 

6 6 

Logical Drives Configured 

LD RAID Size #Stripes #StrpSz Drive-State 

1 1 4096 2 8KB OPTIMAL 


RAID=1 

Size = 4096 

Advanced Menu 

Accept 

Choose RAID Level For This Logical Drive 

Use cursor keys to navigate, ENTER to select an option and ESC to go back 

Figure 5–2. Logical Drives Configured Screen 

11. Select RAID= in the Logical Drive 1 menu, then press Enter. 

A list of available RAID levels appears. 

12. Select RAID level 1, then press Enter. 

Note: Do not change any settings in the Advanced Menu. The default parameters 

are acceptable for RAID level 1. 

13. Select Accept, then press Enter (press Enter twice). 

The Logical Drives Configured window shows the configuration (Figure 5–2). 


Save Configuration? 

YES 

NO 

14. Highlight YES, then press Enter. 

The configuration is saved. 

15. Press Enter. 

16. Press Esc to return to the Management Menu. 


4 

5 

6


17. Select Initialize, then press Enter. 

A screen appears showing the logical drives configured. Also, a Logical Drives menu 

appears as follows: 

----Logical Drives---- 


18. Press the space bar to select Logical Drive 1 (if it is not already selected), then press 

F10 to initialize it. 

Note: When selected, the highlighted color switches from gray to yellow. 


----Initialize Drives?---- 

YES 

NO 

19. Select YES, then press Enter. 

A bar graph message shows progress of the initialization (takes about 15 minutes). 

20. When initialization is complete, press any key to continue. 

The logical drives configured screen reappears. 

21. Press the Esc key twice to exit. 


--EXIT?-- 

YES 

NO 

22. Select YES, then press Enter. 


Configuration has changed. Press Ctrl-Alt-Del to reboot. 

23. Before pressing Ctrl-Alt-Del to reboot, insert the Windows NT Setup diskette 1 and the 

Windows NT CD-ROM Disc 1 in the drives. 






The Windows NT Server, Enterprise Edition installation process consists of an installation 

phase (5.4.1) in which prompts appear as text messages and a configuration phase (5.4.2) 

in which prompts are presented as graphical screens. The following subsections describe 

the steps to take during each phase. 

Notes: 


2.5.2). 


After hardware RFU, the site may wish to customize the configuration to meet their 

needs. 


Operating System 

Begin Windows NT Server, Enterprise Edition installation as follows: 

1. Insert the Windows NT CD-ROM (labeled “Microsoft Windows NT Server”) and the 

diskette labeled “Microsoft 1-8 CPU Edition Setup Disk 1” into the drive units. 


After the hardware initialization messages are displayed, the following message 



================ 



================ 



into Drive A: 


3. Insert the diskette labeled “Microsoft 1-8 CPU Edition Setup Disk 2” into the drive, 




1 System Processor [xxx MB memory] Multiprocessor Kernel 














======================= 



into Drive A: 


b. Insert the diskette containing the RAID drivers labeled “Windows NT 4.0/3.51 

Driver MEGARAID.SYS...” (Disk 1 of 2) and press Enter to continue. 

After a brief wait, the MEGARAID NT SCSI driver is listed in the adapter window. 

c. Press Enter to select the highlighted MEGARAID NT SCSI Driver entry. 

A message indicates that Setup has recognized the MEGARAID adapter. 

d. Enter S to specify an additional SCSI adapter. 


e. Press Enter to select the highlighted Other entry. You are prompted to insert a 



======================= 



into Drive A: 


f. Insert the Unisys diskette labeled “DRIVER-SDMS PCI SCSI NT 896 Driver” 

(23381676–000) and press Enter. 

g. After a brief wait, the Symbios driver is listed in the adapter window. 

h. Press Enter to select the highlighted Symbios PCI High Performance Driver entry. 

A message indicates that Setup has recognized the Symbios adapter. 




You are prompted to insert disk 3 as follows: 


======================= 



into Drive A: 


9. Insert the diskette labeled “1-8 CPU Edition Setup Disk 3” into the drive, then press 



confirming that the adapters have been recognized. 


======================= 

Setup has detected that one or more of your hard disks has more than 1024 

cylinders 


Note: You may be prompted to insert the CD-ROM, if you did not do so as 

instructed in step 1. 

A message states that Setup has detected that your computer’s hard disk is new. 


A license agreement text screen then appears. 



page. 


the license agreement . 


13. Be sure that the Computer line reads “MPS Multiprocessor PC.” If it does not, use the 

arrow keys to move to that line, press Enter and change as needed. 






==================== 

The list below shows existing partitions and spaces available for 

creating new partitions. 

Use the UP and DOWN ARROW keys to move the highlight to an item 

in the list. 

To install Windows NT on the highlighted partition 

or unpartitioned space, press ENTER. 


To delete the highlighted partition, press D. 


ENTER=Install C=Create Partition F1=Help F3=Exit 

15. Use the arrow key to highlight Unpartitioned space, then press C to create a new 









A message indicates that the disk is being formatted. After the disk is formatted, a 

message appears asking for the directory in which to install Windows NT. 




The examination takes a few seconds. Then the following message appears: 


======================= 


MEGARAID NT RAID DRIVER 

into Drive A: 


21. Insert the diskette containing the RAID drivers labeled “Windows NT 4.0/3.51 Driver 

MEGARAID.SYS...” (Disk 1 of 2), then press Enter to continue. 



Then the following message appears: 


======================= 


SYMBIOS PCI HIGH PERFORMANCE DRIVER 

into Drive A: 


22. Insert the diskette labeled “DRIVER-SDMS PCI SCSI NT 896 Driver,” then press Enter 

to continue. 

Setup begins copying files. When the files are copied, a message asks you to remove 

the diskette in preparation for rebooting. 

23. Remove the diskette and the CD-ROM from the drives, then press Enter. 







Note: This procedure follows immediately after, and is continuous with, the 

installation procedure in 5.4.1. 


appears with a message box saying to insert the Windows NT CD-ROM. Take the 



the drive, then click OK. 

If you click OK before the drive is ready, a prompt indicates files are needed from the 

Windows NT Server CD-ROM. A scroll box identifies the directory from which they 

will be copied. Click OK in the box if this occurs. 


























name. 



screen. 






7. On the Server Type screen, click Stand-alone Server (or the selection from Table 2–1), 

then click Next to proceed. 

8. When the Administrator Account screen appears, enter and confirm the password for 

the administrator’s account as follows: 



that field. 















Note: You can also select Windows Messaging and Games if desired by the site. 





A screen appears with the option Computer will Participate in Network selected. The 





A screen appears with a check box labeled Install Microsoft Internet Information 

Server already checked. 




a. Click Start Search. 


b. Click Select from list. 

c. Click Have disk. 

d. Insert the diskette labeled “Aquanta DR2 Intel Ether Express PRO 100+” 

(38160685–001) in the drive. 

e. Click OK. 

The Intel EtherExpress PRO adapter is detected and displayed in the list box. 

f. Click OK. 

Both adapter types (Syskonnect FDDI and Intel EtherExpress PRO) should now 

be listed. 

g. Click Next. 


protocol. The NWLink IPX/SPX compatible transport and NetBEUI protocol are not 


15. Deselect any protocols not required. 

16. Ensure that the TCP/IP protocol is selected. If not, click TCP/IP protocol to select it. 










• Server 

In addition, the following network services also are required: 


• Simple Network Management Protocol (SNMP) service (the SNMP agent package 

is needed for SysAdmin). 


a. Click Select from list . . . 


Service. 

c. Click OK. 








• Server 







A screen for setting FDDI parameters appears. 

20. Click Continue to accept the defaults. 

Intel PROSet adapter information is displayed. 



21. Click OK. 

Installation of networking components begins. A message box asks if you want to use 

Dynamic Host Configuration Protocol (DHCP) server. 

22. Click No. 




a. Agent tab—Click this tab, then enter the name and location of the system 

administrator. Accept the service defaults (Applications, Internet, and End-to- 

End). 

b. Security tab—Click this tab, then click the Send Authentication trap check box to 

remove the check mark. Leave the Accept SNMP Packets from Any Host option 

set. 

c. Click OK. 






adapters: 



• Click Specify an IP address to select it. 





in Table B-1. 

• In the IP Address field, type the appropriate FDDI address for this node (for 



• In the Subnet Mask field, enter the address 255.255.255.0. 


• Click the Add button in the IP Addresses box. 

• Enter the other two addresses and subnet masks for Windows NT from Table 

B–1. 

• Click OK. 


a. Click the IP Address tab. 



b. Use the scroll bar to select the Intel EtherExpress PRO adapter from the dropdown 

list of adapters. 

c. Enter the following IP address information: 

• Click Specify an IP address. 

• In the IP Address field enter the IP address for the Windows NT node from 


• Change the subnet mask to the netmask address from Table 2–2, or skip this 


• If you have a gateway (router), click Advanced (otherwise skip this step) and 


− Click Add. 

− In the New Gateway field, type the gateway address from Table 2–2. 

− Click Add. 

The address appears in the Installed gateways list box. 

− Repeat these steps for each additional gateway required, then click OK 

when done. 

d. If the site chooses to implement WINS, click the WINS Address tab (otherwise 



WINS is not used on the FDDI interconnect. 

• In the Primary WINS Server field, type the address from Table 2–2, then press 

Tab. 

• If applicable, type the IP address of the Secondary WINS Server from Table 

2–2. 

e. Click the DNS tab and take the following steps: 

• Enter the IP address for the first DNS server from Table 2–2, if the site has any 

DNS servers. 



• Repeat these steps for each additional DNS server. 

• Enter a domain (Internet) name to which the server belongs, for proper 

operation of the IIS services. 






29. A setup screen identifies the host name of the Windows NT node and asks whether the 




Click Workgroup, enter a workgroup name of CLEARPATH, then click Next to 

proceed. 


The Windows NT Setup screen indicates it is ready to Finish Setup. 













e. Click SQL Server, then click OK to install the ODBC driver. 









month. 


year. 



appears. 










selected (default VGA mode with 16 colors). 




c. Click Yes to proceed if you saw the pattern correctly. 

A message box says to click OK to save the settings. 




Files are copied from the CD-ROM. Messages appear to indicate progress. 

When the installation is complete, a screen with a message like the following appears: 

One or more minor errors occurred installing ... 

36. Click No. 

Then the following message appears. 




Computer. 












Caution 





NT Server logo appears and you are prompted to press Ctrl-Alt-Del to log on. Take the 


Notes: 









c. Click OK. 




Section 6 

Installing Windows NT Server 4.0 

(DR/2) 

This section tells you how to install and configure the Windows NT Server 4.0 operating 

system on an Intel server node. Section 7 describes additional steps you must take to 

complete Windows NT installation. A full installation, with the checklist in Table 6–1 

completed, and all software media readily available, takes about 1 hour. 



DR/2 (VX1301/1305) Windows NT Server 4.0 operating system NTS4004-xxx 

Mylex DAC 1164P RAD5003-P64 


Intel Pro 100+ (built in to the DR/2) 

Table 6–1 lists media and information for the various installation scenarios (installation 

with preloaded software, full installation, and steps you need to take in either instance). 

Obtain that information or media before beginning. 




Installing Windows NT Server 4.0 (DR/2) 

Table 6–1. Windows NT Server 4.0 Installation Checklist 



Media needed: A blank diskette for creating an emergency repair disk. 



Name __________________________ 

Organization _____________________________ 

Determine the name of the user (for example, the administrator) and organization responsible for 

the node. 


Windows NT Registration Number: 

The Windows NT registration number is found on a Certificate of Authentication provided with the 

installation media. 

Server Type screen 

Have the client determine the Windows NT Server type: 

− Primary Domain Controller (PDC) 

Directly maintains security and user account information in the master copy of the 

domain’s directory database. 

− Backup Domain Controller (BDC) 

If BDC is selected, the PDC must be accessible on the LAN during setup of the BDC. 

The BDC maintains a replicated copy of the directory database maintained by the PDC. 

Can be promoted to serve as a PDC. 

− Member Server (default recommendation) 

Member (stand-alone) server mode is recommended in the following circumstances: 

If the server is to perform time critical tasks and the site does not want it spending time 

authorizing domain logon attempts or receiving synchronized copies of the domain’s 

directory database. 

If the site wants this server to have a different administrator or different user accounts 

from the rest of the servers in the domain. 

A member server can participate in a domain, although that is not required. 

This document describes installation procedures for a member server only. For more information about 

domain planning, refer to Microsoft Windows NT Server Version 4.0 Concepts and Planning. 

continued 



Table 6–1. Windows NT Server 4.0 Installation Checklist 


6.5. Installing and Configuring Windows NT Server 4.0 

Media needed: 


• Windows NT CD-ROM—labeled “Microsoft Windows NT Server” 

• RAID drivers diskette—labeled “NT 4.0 Supplemental Drivers Diskette" 

• Video drivers diskette—labeled “NT 4.0 Supplementary Drivers Diskette” 


• DR/2 drivers diskette—labeled “Mylex Solution Software Kit 2.01 NT/NW Drivers Diskette" 

6.5.2. Configuring Windows NT Server 4.0 



Name __________________________ 



Organization _____________________________ 



CD-KEY ______________________________________ 





Phone number __________________________ 









Caution 

To prevent installation problems, or wasted time, determine whether Windows NT 

has been preloaded. Then follow either the procedure for preloaded software or 

the full installation procedure, as appropriate. 

To determine whether the Windows NT operating system is preloaded, 

1. Power on the Intel node and allow it to fully boot (takes about 2 minutes). 

2. If the Windows NT Software License Agreement screen appears, the operating system 

is preloaded. 

If Windows NT is preloaded, perform the steps described in 6.2. Then complete the 

installation as described in Section 7. 

If Windows NT is not preloaded, 






You must take the steps below to initially configure Windows NT when it is preloaded. 

Notes: 


into the correct bays as labeled on the disks. See the DR/2 system map for the 

location and layout of the drive bays. 

















3. Use the arrow keys to select the Configure RAID Drive option, then press Enter. 



Automatic 

Assisted 

Custom 











Spare: No 





1:00 UNISYS ....... 17.0 Online 

1:01 UNISYS ....... 17.0 Online 














follows: 




page. 

b. When you have read the entire agreement, click I agree. 


After a few seconds, a Windows NT Setup screen appears, followed by a Name and 


8. Enter Name and Organization as follows: 


node. 

















name. 



screen. 


12. Click Primary Domain Controller (PDC), Backup Domain Controller (BDC), or 

Member Server as chosen by the site (see Table 6–1). Then click Next to proceed. 

Note: Member Server was chosen as the default option for this procedure. If you 

choose the PDC or BDC option you may need to respond to additional 

prompts not documented here. See Microsoft Windows NT Server 4.0 

Concepts and Planning for more information. 







that field. 






After a brief wait during which the setup program searches for network adapters, the 

following message appears: 

SK-NET FDDI PCI Adapter Card Setup 

Continue Cancel Help 


Intel Pro 100 is detected on the DR/2. 

16. Click Close. 

An error message appears as follows: 

The IP Address key has an invalid IP address. 

Please correct the problem after the property 

sheet is displayed. 

17. Click OK. 




adapters: 



1) Click Specify an IP address (a dot appears in the circle to indicate it is 

selected). 





in Table B-1. 




3) A default address of 255.255.255.0 is automatically calculated for the Subnet 

Mask field. Do not change that address. 






B–1. 

3) Click OK. 



adapters: 

Intel EtherExpress Pro Adapter 


1) Click Specify an IP address. 

2) In the IP Address field enter the IP address for the Windows NT node from 


3) Change the subnet mask to the netmask address identified in Table 2–2, or 


4) If you have a gateway (router), click Advanced and take the following steps: 

a) Click Add in the gateways section. 

b) In the gateway address field, type the gateway address identified in Table 

2–2. 

c) Click Add. 

The address appears in the gateways list box. 


when done. 



1) In the Primary WINS Server field, type the address identified in Table 2–2, then 

press Tab. 

2) If applicable, type the IP address of the Secondary WINS Server identified in 

Table 2–2. 



DNS servers. 

2) Click Add. 






must not enable IP forwarding 



21. Click OK. 


At least one adapter cards has an empty WINS address. 



Windows NT loads files, configures the network, and then the following message 

appears: 



The system goes through an automatic installation of Service Pack 3. Messages may 

appear indicating that the target file exists and that it is newer than the source file. 

Select NO to not overwrite the target file (keep the newer file). 


After a few seconds, the Windows NT Server logo appears and you are prompted to 


24. Log on (6.5), then complete the installation as follows: 

a. Configure site-specific Windows NT characteristics such as the following: 

• Windows NT license mode 

• Local date and time 

• Network services such as WINS, DNS, and file transfer protocol (FTP) 

security 

For instructions on configuring site-specific characteristics of Windows NT, refer 

to Windows NT help for the specific characteristic that you wish to reconfigure. 

b. Take the steps for completing a Windows NT installation described in Section 7. 


This subsection describes the procedure for configuring the DR/2 RAID disk controller. 

Configure the controller for RAID level 1 (mirroring) for two disks units—even if more 

units are available. 



ROM labeled "Mylex Solutions Software Kit 2.01." 

Notes: 


2.5.2). 








configuration procedure; otherwise, the normal boot procedure continues. 



Several start-up messages appear, including a prompt to press Alt-M, as follows: 






> 

2. Press Alt-R to start BIOS Options Utility. A BIOS options menu appears: 


BIOS enabled 






Enabled. 













8. Press Alt-M to start the Mylex RAID EzAssist utility. 













Automatic 

Assisted 

Custom 











Spare: No 





1:00 UNISYS ....... 17.0 Online 

1:01 UNISYS ....... 17.0 Online 











12. Insert the Windows NT Setup diskette 1 and the Windows NT CD-ROM Disc 1 in the 

drives. 


After rebooting, proceed with the instructions for installing and configuring Windows NT 

4.0 in 6.4. 

Note: Upon completion of Windows NT installation, install and configure the RAID 

utility software (see 7.1.5). 



6.4. Installing and Configuring Windows NT Server 

4.0 

The Windows NT Server 4.0 installation process consists of an installation phase (6.4.1) in 

which prompts appear as text messages and a configuration phase (6.4.2) in which 

prompts are presented as graphical screens. The following subsections describe the steps 

to take during each phase. 

Notes: 


2.5.2). 


After hardware RFU, sites may wish to customize the configuration to meet their 

needs. 

6.4.1. Installing the Windows NT Server 4.0 Operating System 

Begin Windows NT Server 4.0 installation as follows: 

1. Insert the diskette labeled “Microsoft 1-4 CPU Edition Setup Disk 1” into the drive 

units. 


The following message appears at the top of the screen: 


================ 



================ 



into Drive A: 


3. Insert the Windows NT CD-ROM labeled “Microsoft Windows NT Server.” 

4. Insert the diskette labeled “Microsoft 1-4 CPU Edition Setup Disk 2” into the drive unit, 




1 System Processor [xxx MB memory] multiprocessor kernel 












diskette containing the RAID controller drivers diskette. 


======================= 



into Drive A: 


b. Insert the following diskette containing the RAID drivers and press Enter to 

continue: 

Mylex Solution Software Kit 2.01 NT/NW Drivers Diskette 

After a brief wait, select the Mylex driver listed in the adapter window. 

c. Press Enter to select the highlighted "Mylex Disk Array Controller" entry. 

A message indicates that Setup has recognized the Mylex adapter. 

d. Enter S to specify an additional SCSI adapter. 

The adapter window reappears. 

e. Press Enter again to select the highlighted Other entry. 

f. Reinsert the diskette "NT 4.0 Supplemental Drivers 01." Again there is a brief wait. 

When the list of adapters appears, use the up arrow key to scroll up the list until 

you highlight the following adapter: 

AHA294XU2/295XU2/395XU2/AIC-789X PCI SCSI Controller (NT 4.0) 

g. Press Enter to select the highlighted entry. Press Enter to continue. 

You are prompted to insert disk 3 as follows: 


======================= 



into Drive A: 


9. Insert the diskette labeled “Microsoft Windows NT Server Setup Disk 3” into the drive 

unit, then press Enter to continue. 


confirming that both adapters have been recognized. 


======================= 





A screen (Figure 6–3) appears that identifies the MS-DOS partition created in 6.4 and 

the remaining unpartitioned disk space. 


==================== 

Setup has determined that your computers startup hard disk is new or has been 

erased, or that an operating system is installed on your computer with which 

Windows NT cannot coexist. 

If such an operating system is installed on your computer, 

continuing setup may damage or destroy it. 

If the hard disk is new or has been erased, or you want to discard it's current contents, 

you can choose to continue setup. 

To continue setup, press C. Warning: Any data currently on your computer's start up hard 

disk will be permanently lost. 

To exit setup, press F3. 

C=Continue Setup F3=Exit 

Figure 6–1. Windows NT Server Setup (DR/2) 



page. 


the license agreement (press F8 twice). 

13. A hardware and software components list appears for you to verify. Be sure that the 

Computer line reads MPS Multiprocessor PC. If it does not, use the arrow keys to 

move to that line, press Enter and change as needed. 

14. Use the arrow key to highlight Unpartitioned space, then press C to create a new 




16. Select the new partition, then press Enter. 











19. Press Enter to perform an exhaustive examination of the hard disk. The examination 

takes a few seconds. 

20. Unless you removed it, the diskette you need is already in the drive. If it is not, 

reinsert the following: 

Mylex Solution Software Kit 2.01 NT/NW Drivers Diskette 

Setup begins copying files. When done, a message asks you to remove the diskette in 

preparation for rebooting. 

21. Remove the diskette and the CD-ROM from the drive units, then press Enter. 






6.4.2. Configuring Windows NT Server 4.0 


installation procedure in 6.4.1. 


appears with a message box saying to insert the Windows NT CD-ROM. Take the following 

steps: 

1. Insert the Windows NT CD-ROM (labeled “Microsoft Windows NT Server”) into the 

drive unit, then click OK. 

A prompt indicates files are needed from the Windows NT Server CD-ROM. A scroll 

box identifies the directory from which they will be copied. 

2. Click OK to proceed. 







4. Enter the Name and Organization responsible for the node as follows: 



















name. 



screen. 






8. Click Standalone Server (or the selection from Table 6–1), then click Next to proceed. 





that field. 















Note: You can also select Windows Messaging and Games if the site wishes. 










A screen appears with a check box labeled Install Microsoft Internet Information 

Server already checked. 




a. Click Select from list. 

Scroll to the SysKonnect SK-NET FDDI PCI adapter. 

b. Click OK. 

c. Click Select from list. 

d. Click Have disk. 

e. Insert the following diskette in the drive: 

NT 4.0 Supplemental Driver disk 02 of 03 

You will be asked for the path name of the driver. Enter A:\Intelpro 

f. Click OK. 

The window should now display the selected item: 

Intel Ether Express Pro Adapter 

g. Click OK. 

Both adapters should now be listed. 

h. Click Next. 

A Network Protocols screen appears. 

Note: The only required protocol is the TCP/IP protocol. The NWLink IPX/SPX 

compatible transport and NetBEUI Protocol are not required for initial 

installation, but they may be selected if required by the site. 

16. Click NWLink IPX/SPX compatible transport to deselect it. 



17. Ensure that the TCP/IP protocol is selected. If not, click TCP/IP protocol to select it. 








• Server 

In addition, the following network services also are required: 


• Simple Network Management Protocol (SNMP) service (the SNMP agent package 

is needed for SysAdmin). 

• Windows Internet Name Service (WINS) 


a. Click Select from list . . . 


Service. 

c. Click OK. 








• Server 



• WINS 





A screen for setting FDDI parameters appears. 

21. Click Continue to accept the defaults. 



A screen appears for setting the Intel Pro 100. Click OK to continue. 

22. Installation of networking components begins. A message box asks if you want to use 

Dynamic Host Configuration Protocol (DHCP) server. 

23. Click No. 




a. Agent tab—Click this tab, then enter the name, room number, and phone number 

of the system administrator. Accept the service defaults (Applications, Internet, 

and End-to-End). 

b. Security tab—Click this tab, then click the Send Authentication trap check box to 

remove the check mark. Leave the Accept SNMP Packets from Any Host option 

set. 

c. Click OK. 






adapters: 



1) Click Specify an IP address to select it. 





in Table B-1. 







2) Enter the other two addresses and subnet masks for Windows NT. 

3) Click OK. 



adapters: 

Intel EtherExpress PRO Adapter 





2) In the IP Address field enter the IP address for the Windows NT node from 






a) Click Add. 


c) Click Add. 



when done. 




WINS is not used on the FDDI interconnect. 


Tab. 


2–2. 



DNS servers. 

2) Click Add. 




27. Click OK. 


At least one adapter cards has an empty WINS address. 









A setup screen identifies the host name of the Windows NT node and asks whether the 


31. Click Workgroup, enter a workgroup name of CLEARPATH, then click Next to 

proceed. 


The Windows NT Setup screen indicates it is ready to Finish Setup. 













e. Click to highlight SQL Server, then click OK to install the ODBC driver. 









month. 


year. 



appears. 










selected (default VGA mode with 16 colors). 




c. Click Yes to proceed if you saw the pattern correctly. 





Files are copied from the CD-ROM. Messages appear to indicate progress. 

When the installation is complete, a screen with the following message appears: 




Computer. 











Caution 





NT Server logo appears and you are prompted to press Ctrl-Alt-Del to log on. Take the 


Notes: 





2. Enter the following information on that screen: 

a. User name—Enter administrator. 

b. Press the Tab key to advance to the password field. 

c. Password—Enter administrator (the installation password). 

d. Click OK. 







Section 7 

Completing Windows Installation 

This section describes how to finish installing and configuring software on either a 

Windows NT node or a Windows 2000 Node. 

For Windows NT, carry out the steps in 7.1. For Windows 2000, proceed to 7.2. 

Table 7–1 lists procedures that require you to have information or installation media 

available at the time of installation. Obtain these materials before beginning. 

Table 7–1. Checklist for Completing Windows NT Installation 

ß Media or Information Required 

7.1.1. Installing Service Pack 3 for Windows NT 

Media needed: 

For ES5044R, Aquanta ES2045R, Aquanta ES2085R, or Aquanta ES5085R: Windows NT Server, 

Enterprise Edition, Disk 1 (CD-ROM) 

For Aquanta DR/2: Service pack CD-ROM—labeled “Windows NT Service Pack n” 

7.1.2. Installing the Unisys Hardware Monitor (DR/2 Only) 

Media needed: Unisys Hardware Monitor Service diskette—labeled “Unisys Hardware Env Service 

(part number 38164992-002)” 

7.1.3. Configuring ClearPath Networking 

Media needed: Windows NT installation tools diskette—labeled “NT Installation Tools” 

The Windows NT installation tools diskette is provided as part of the server IOE. 

7.1.5. Installing and Configuring RAID Utility Software 

Media needed: 

For a DR/2 node: RAID controller software diskette—labeled “Windows NT 4.0/3.51 Driver 

MEGARAID.SYS...” Disks 1 and 2 (ES2045R or DR/2) 

For an ES5044R, ES5085R, or ES3045R node: RAID controller software CD—labeled "Mylex Solutions 

Software Kit x.x " 

7.1.6. Installing and Configuring Video Drivers (Full Install Only) 

Media needed: Video driver diskette—labeled “Unisys Supplemental Drivers and Utilities CD,” part 

number 23387707- xxx 

continued 



Table 7–1. Checklist for Completing Windows NT Installation 

ß Media or Information Required 

7.1.7. Installing Internet Explorer (Full Install Only) 

Media needed: Windows NT Service Pack 4 CD-ROM 

7.1.8. Installing the Active Server Pages Upgrade for IIS (ES2045R, ES5085, or ES2024R) 

Media needed: Microsoft Windows NT Server, Enterprise Edition CD-ROM 2 

7.1.9. Installing and Configuring ControlIT 

Note: The ControlIT media kit is included in the SPO software package. 


Registration window 

License number: 

Enter the server key code from the back of the CD-ROM sleeve. 

7.1.10. Configuring the Tape Drive 

Media needed: Windows NT CD-ROM labeled “Microsoft Windows NT Server” 

7.1.15. Applying the Latest Service Pack 

Media needed: Service Pack CD-ROM—labeled “Windows NT Service Pack n” 

7.1.17. Creating an Emergency Repair Disk 

Media needed: A blank formatted diskette 


Media needed: Windows 2000 installation tools diskette—labeled “NT Installation tools” 

The Windows 2000 installation tools diskette is provided as part of the server IOE. 


Media needed: RAID controller software CD—labeled "Mylex Solutions Software Kit x.x” 


Note: The ControlIT media kit is included in the SPO software package. 


Registration window 

License number: 

Enter the server key code from the back of the CD-ROM sleeve. 


Media needed: A blank formatted diskette 


7.1. Completing Windows NT Installation 


This section describes how to complete installation and configuration of software on a 

Windows NT node for these systems: 

• Windows NT Server, Enterprise Edition, on an ES5044R node 




• Windows NT Server 4.0 on a DR/2 node 

To complete a Windows NT installation, take the following steps: 

1. (Full install only)Install Service Pack 3 (or the latest service pack) for Windows NT 

(7.1.1). 

2. (DR/2) Install the Unisys hardware monitor (7.1.2). 

3. Configure the hosts file for ClearPath networking (7.1.3). 

4. Configure the correct number of client licenses (7.1.4). 

5. Install and configure the RAID utility software (7.1.5). 

6. (Full install only) Install and configure video drivers (7.1.6). 

7. (Full install only) Install current Microsoft Internet Explorer (7.1.7). 

8. (ES5085R and ES2045R) Install the Active Server Pages upgrade for Microsoft Internet 

Information Server (IIS) 3.0 (7.1.8). 

9. (DR/2) Install and configure ControlIT server software (7.1.9). 

10. Configure the tape drive (7.1.10). 

11. Set balanced server priorities (7.1.11). 

12. Configure the FTP service (7.1.12). 

13. Enable a guest account (7.1.13). 

14. Create a logical F drive (7.1.14). 

15. Apply the latest service pack (7.1.15). 

16. (ES5085R) Install ess software (7.1.16). 

17. Create the emergency repair disk (7.1.17). 



7.1.1. Installing Service Pack 3 for Windows NT (Full Install Only) 

Installation of Microsoft Service Pack 3 is required for Windows NT Server, Enterprise 

Edition. For the ES5044R, ES2045R, ES5085R, or ES2024R, follow the steps below. For 

the DR/2, skip to 7.1.2. The service pack for the DR/2 will be installed in 7.1.15. (For the 

other servers, 7.1.15 is a reinstallation.) 

Note: This procedure is necessary only for a full Windows NT installation. If 

Windows NT is preloaded, skip this procedure and continue with 7.1.3. 

To install Service Pack 3 for Windows NT Server, Enterprise Edition, take the following 

steps: 

1. If you are not currently logged on, power on or restart the Windows NT node and log 

on as the administrator. 

If Service Pack 3 is not yet installed, you are automatically prompted to install it when 

you log on. 

Note: If you do not receive the prompt to install Service Pack 3, you can skip this 

procedure and go to 7.13. 

2. Click Start Installation. 

3. Insert the Windows NT Server, Enterprise Edition, disc 1 into the CD-ROM drive. 

4. Click OK in the “Files needed for Windows NT Service Pack 3” window. 

5. Close the setup window that appears. 

A Welcome screen appears. 


A License Agreement screen appears. 

7. Click Yes. 

A Service Pack Setup screen appears. 

8. Click Next to install the service pack. 

A message asks whether you want to create an uninstall directory. 

9. Click No, then click Next. 


Files are copied and Service Pack 3 is installed. During installation, a Windows NT 

Service Pack Setup window may appear, listing the name of a file with the following 

message: 

This file has been identified as an oem-installed file. 

Would you like to overwrite the version of the file on your system with 

the Service Pack 3 version? 

11. Click No for all file messages that may appear. 

When setup finishes, a prompt appears to reboot the server. 

12. Remove the CD-ROM from the drive. 

13. Click OK to reboot. 



14. After you reboot, log on as the administrator again. 









Administrator's Guide. You can find this guide in two places: in 



16. Click OK. 

A Microsoft Windows NT Server, Enterprise Edition Installer window appears. 



19. Click Yes for the prompt asking whether you are sure. 

Continue by configuring ClearPath networking ( 7.1.3). 

7.1.2. Installing the Unisys Hardware Monitor (DR/2 Only) 

This subsection explains how to install the Unisys hardware monitor for DR/2 systems. 




2. Click Start, then Run. 

A Run window appears. 

3. Insert the CDROM labeled “Server Hardware Manager (SHM)” into the drive unit. 

4. In the Run window, type the following, then click OK: 

a:\setup.exe 

A Server Hardware Manager window appears. 


6. Select the defaults for the directory and click Next. 

7. Select SHM for server and click Next. 

8. Select the default for program folder, and click Next. 

9. Click OK. 



10. Reboot the Windows NT node and log on as the administrator. (This reboot applies 

the changes you made to the environment.) 

Continue by configuring ClearPath networking (7.1.3). 


Following installation of Windows NT Server, you must set up a hosts file so that the 

Windows NT node can communicate with other nodes on the private interconnect (FDDI 

LAN). Take the following steps to set up the hosts file: 





3. Insert the hosts file setup diskette (labeled “NT Installation Tools”) into the drive unit. 


a:copyhost 

ClearPath HMP IX also provides some TCP/IP stack optimization settings to improve 

network performance by adding some entries to the registry. With the “NT Installation 

Tools” diskette still in the drive 




a:tunent.reg 

3. A Registry Editor box appears that confirms that the information has been entered into 

the registry. Click OK to close it. 

Continue by configuring the number of client licenses (7.1.4). 

7.1.4. Configuring the Number of Client Licenses 

The number of client licenses provided with the Windows NT node depends on the version 

of Windows NT: 

• Windows NT Server, Enterprise Edition provides 25 licenses (ES2045R, ES5085R, or 

ES2024R). 

• Windows NT Server 4.0 provides 10 licenses (DR/2). 

Note: Additional client licenses for either version may be purchased either from 

Unisys Corporation or from Microsoft Corporation. 



To set up the correct number of licenses using the Windows NT license manager, take the 




2. Click Start > Programs > Administrative Tools > License Manager. 

An Enterprise-License Manager window opens. 

3. Click the Purchase History tab (if it is not already in front). 

4. Select License, then New License from the menu bar. 

5. From the Product drop-down box, select Windows NT Server. 

6. Set the Quantity field to the number appropriate to the Windows NT Server version: 

• For Windows NT Server, Enterprise Edition (ES2045R, ES5085R, or ES2024R), set 

the number to 25. 

• For Windows NT Server 4.0 (DR/2), set the number to 10. 

7. In the Comment field, type in the following: 

Initial ClearPath Licenses 

8. Click OK. 

9. In the Per Seat Licensing window, click “I agree,” then click OK to proceed. 

10. Exit License Manager by selecting License; then select Exit from the menu bar or click 

the upper right-hand corner X box. 

Continue with the steps in 7.1.5. 


After installing and configuring Windows NT and the service pack, install and configure the 

RAID utility software for the Windows NT node. Follow the appropriate set of instructions 

below, depending on the type of hardware you have: 

• A DR/2 

• An ES5044R, ES5085R, ES2045R, or ES2024R 

Installing and Configuring RAID for a DR/2 Node 

These are the steps for installing and configuring the FlexRAID utility software for a DR/2 

server with an AMI Megaraid controller: 



2. Insert the diskette labeled “Windows NT 4.0/3.51 Driver MEGARAID.SYS...” (Disk 1 of 

2), containing the RAID drivers. 


A Run dialog box appears. 



4. In the dialog box type the following, then click OK: 

A:setup 



A user information window appears. 


After you have reviewed the ReadMe information, close this window. 

7. Select Power Console PLUS and click Next. 

8. Select Standalone and click Next. 

9. It is OK to install to the default directory. Click Next. 

10. It is OK to use the default program folder. Click Next. 

11. When prompted, insert disk 2 and click OK. 

The Setup Complete window appears. 

12. Click Finish, then remove the diskette. 

13. Right-click on the MegaRAID taskbar icon and click Close. 

You can now run the Power Console PLUS utility software when desired by selecting Start, 

Programs, MegaRaid, then MegaRAID Power Console. 

Note: You cannot back up the MegaRAID configuration, but you can print a listing of 

the configuration for future reference. Run the RAID utility software, then click 

the printer icon under Configuration. 

Installing and Configuring RAID for an ES5044R, ES5085R, ES2045R, or 

ES2024R Node 

These are the steps for installing and configuring the Global Array Manager (GAM) utility 

software for the ES5044R, ES5085R, ES2045R, or ES2024R, servers, using the Mylex 

eXtremeRAID 1100 Controller. 


on as administrator. 

2. Insert the CD labeled "Mylex Solutions Software Kit x.xx" into the CD-ROM drive. 

A Mylex Solutions window appears. 

3. Click Install Global Array Manager 

A Welcome window appears. 


A Select Components window appears. 

5. Click Global Array Manager Client and Server for installation. Click Next. 

A Choose Destination Folder window appears. 



6. Accept the default and click Next. 

The Installation Summary window appears. 


8. Click Next again to bypass the Modify Server Configuration File setup menu. 

9. Click OK to the informative message. 


11. Click Finish, then remove the CD. The server automatically reboots. 

You can now run the Mylex Global Array Manager utility software when desired by 

selecting Start > Programs > Mylex Global Array Manager Client Administrator. 

Continue by installing video drivers (7.1.6). 

7.1.6. Installing and Configuring Video Drivers (Full Install Only) 

Notes: 

• This procedure is necessary only when you perform a full Windows NT installation. 

Skip this procedure if Windows NT is preloaded. 

• Skip this procedure for the DR/2 node. Proceed to 7.1.7. 

To enable console monitor resolution higher than VGA on an ES5044R, ES2045R, ES5085R, 

or ES2024R, you must install video drivers on the Windows NT node. 

Follow these steps: 



2. Insert the CD labeled “Unisys Supplemental Drivers and Utilities” (23389174- xxx) into 

the CD-ROM. 

3. Right-click on the desktop, then click Properties in the pop-up menu that appears. 

A tabbed Display Properties screen appears. 

4. Click the Settings tab to bring it to the front, then click Display Type. 

A Display Type screen appears. The Adapter Type field shows the current adapter 

type (most likely Cirrus-compatible display adapter). 

5. Click Change for the Adapter Type field. 

A Change Display screen appears with a list of currently available adapter models. 

6. Click Have Disk. 

An Install From Disk screen appears that instructs you to insert the manufacturer’s 

disk in the drive unit. The A: prompt should appear in the scroll box by default. 

(ES5044R only) Scroll to D:\NT40\atirage\ (where D: is the CD-ROM) and select it. 

(ES2045R and ES5085R only) Scroll to D:\WINNT40\Display\cl54xx (where D: is 

the CD-ROM) and select it. 



(ES2024R only) Scroll to D:\WINNT40\Display\S3savage4 (where D: is the CD-ROM) 

and select it. 

7. Click OK. 

(ES5044R only) An entry appears for the ATI 3D RAGEIIC PCI graphics adapter. 

(ES2045R and ES5085R only) An entry appears for the Cirrus Logic CL-GD54xx 

graphics adapter. Click this entry to highlight it. 

(ES2024R only) An entry appears for the S3Inc. Savage 4… graphics adapter. Click 

this entry to highlight it. 

8. Click OK, then Yes to proceed with the third-party driver installation. 


Drivers were successfully installed 

9. Click OK, then Close on each open screen to close it. 

When the last screen is closed, the following message appears: 

Do you want to restart your computer now? 

Yes No 

10. Remove the CD from the drive unit, then click Yes to reboot the server. 

a. When the server reboots, log on as administrator. 

b. Click OK on the Invalid Display Settings window. 

A tabbed Display Properties screen appears. 

11. Click the Settings tab to bring it to the front, then select the desired video resolution, 

color depth, and refresh rate. 

12. Click Test, then click OK to start the test. 

A test screen appears. 

13. If the test screen appears to be correct, click Yes to confirm the setting is OK. 

14. Click Apply to apply the new settings. You may have to reboot the server depending 

on the settings you have chosen; otherwise, click OK on the Display Properties screen. 

Continue by installing Internet Explorer (7.1.7). 

7.1.7. Installing Internet Explorer (Full Install Only) 

Follow these steps to install a more current Internet Explorer. 

Note: This procedure is necessary only for a full Windows NT installation. Skip this 

procedure if Windows NT is preloaded. 

1. Insert the Service Pack n CD-ROM (labeled “Windows NT Service Pack n”) into the 

drive unit. Internet Explorer (IE) should start automatically and a Service Pack n 

home page appears. 

2. Scroll down to the Install IE for Intel-based Systems link and click Open. 



3. Click Next to Internet Explorer Active Setup. 


4. Click Accept and then click Install. 

A prompt appears, asking whether you want to select which Internet Explorer 

components are installed. 

5. Select Standard Installation and click Next.. 

A prompt appears, asking whether you want to install the Windows Desktop update. 

Select No and click Next. 

6. For the Active Channel selection, scroll to the top and select NONE. Click Next. 

7. Click Next for Default Folder Location. 

8. When Internet Explorer Active Setup has finished installing components, click OK to 

finish the installation. 

9. Remove the CD-ROM and click OK to restart your computer. 

10. When the reboot is complete, log on as the administrator again. Microsoft Internet 

Explorer Setup runs. 


11. Close the Welcome - Microsoft Internet Explorer window. 

Depending on your server, continue with the steps in 7.1.8 (ES2045R, ES5085R, or 

ES2024R) or 7.1.9 (DR/2). 

7.1.8. Installing the Active Server Pages Upgrade for IIS 

(ES2045R, ES5085R, or ES2024R) 

Follow these steps to install the Active Server Pages update for IIS with Windows NT 

Server, Enterprise Edition (ES2045R, ES5085R, or ES5024R): 



2. Click Start, then select Programs > Administrative Tools > Enterprise Edition Installer. 

A Microsoft Windows NT Server, Enterprise Edition Installer window appears. 

Note: If Enterprise Edition Installer is not present, do the following: 

a. Click Start, then select Run. 

b. Type the following command. 

NHLOADER 

c. Click OK. 


4. Highlight the following (but do not check the box): 

Internet Information Server 3.0 Upgrade 



5. Click Details. 

An IIS Components window appears. 

6. Click the check box to select Active Server Page. 

7. Click OK. 

8. Click Start Installation. 

9. Insert the CD-ROM labeled “Windows NT Server, Enterprise Edition Disc 2” into the 

drive. 

10. Click OK. 

A License Agreement window appears. 

11. Click “I agree” to accept the license agreement. 


13. Click Yes to stop IIS and continue with the installation. 

A Select Options window appears. 

14. Click Next to accept the default Active Server Pages components to install. 

15. Click Next to accept the default paths for Active Server Pages samples, Adventure 

Works Sample Site, and Tutorial. 

Installation proceeds. A “Setup is complete” window appears. 

16. Click OK. 

A message informs you that an Active Server Pages Roadmap icon has been added. 

17. Click OK. 

A message asks whether you want to restart IIS now. 


19. Click Exit. 

20. Click Yes to exit setup. 



ControlIT software, a product of Computer Associates, enables full monitoring and control 

of Windows NT nodes from the Single Point Operations (SPO) workstation. To implement 

that monitoring and control, ControlIT must be installed and configured on each Windows 

NT node as described in this subsection. 

The ControlIT software is also installed on the SPO workstation (see Section 11). 

Note: The ControlIT CD-ROM is included in the SPO software package. Use the same 

CD-ROM to install ControlIT on both the SPO workstation and the Windows NT 

node. 



This is the procedure for installing ControlIT: 



2. Insert the ControlIT CD-ROM into the drive unit. 

When the CD-ROM has been inserted, the installation program starts automatically. 

The Management Solutions window appears. 

3. Under Install Your Product, click ControlIT. 

The License Agreement window appears. 

4. Click “I agree.” 

You are asked to select the type of ControlIT environment to install. Select Install 

Non-Managed Viewer and Host Components. 


The Installation Wizard screen appears. 

6. Make sure Install Agent Host is checked and Install Agent Viewer is not checked. 

Under Setup Options, select Advanced. 


The Change Preferences screen appears. 

8. Click OK. 

The Emergency Repair Disk screen appears. 


The Select Destination Directory screen appears. 

10. Click Next to accept the default. 

A screen for creating program icons appears. 


A Ready to Install message appears. 


When the installation finishes, click OK. 


Your system must be restarted. Restart now? 

13. Remove the CD-ROM from the drive unit, then click Yes. 

After the system reboots, configure ControlIT as follows: 

1. Click Start, then again select Programs > Control-IT > Control-IT. 

The main ControlIT screen appears. 

2. Select File, then Preferences. 

A tabbed Change User Preferences screen appears. 



3. Click the General tab and configure the general preferences as follows: 

a. In the box labeled “Start automatically when Windows starts,” click “Start before 

logon” to select it. 

b. Ensure that the check box labeled “Waiting for incoming connection on startup” is 

selected (has a check mark). If it does not, click the check box to select it. 

4. Click the TCP/IP tab and configure TCP/IP preferences as follows: 

a. Click “Allow incoming calls” to select it, if it is not already selected. 

5. 

b. If “Enable inactivity timer” is selected (has a check mark), click its check box to 

deselect it. 

Click OK to close the window. 

6. Click File, then click Exit to close ControlIT. 

7. Reboot the Windows NT node. 

ControlIT automatically starts in Listen mode, ready to be controlled remotely from the 

SPO workstation. 


7.1.10. Configuring the Tape Drive 

If the Windows NT node has a tape drive unit, configure it as follows: 




the CD-ROM drive. 

3. Close the Windows NT CD-ROM autostart screen when it appears. 

4. Click Start > Settings > Control Panel. 

A Control Panel window opens. 

5. Double-click Tape Devices. 

A Tape Drives window opens. 

6. Click OK to install the driver now. 

7. Click OK and close the Control Panel window. 

8. Click Start, then select Programs > Administrative Tools > Backup. 

9. Click Operations, then click Hardware Setup. 

A list appears. Verify that one of the following entries is in that list, followed by a 

version number (for example, 330B): 

SCSI 2, Bus 0, Id 6, Lun 0, HP c1537A 

SCSI 0, Bus 1, Id 5, Lun 0 SONY SDT-5000 


SCSI 0, Bus 1, Id 5, Lun 0 ARCHIVE PYTHON 02779-XXX 

10. Click OK, then close the Backup window. 



7.1.11. Setting Balanced Server Priorities 


To set up the Windows NT node for balanced file and application server priorities, take the 




2. Click Start > Settings > Control Panel. 

3. Double-click the Network icon. 

4. Click the Services tab, and in the window that opens set the properties as follows: 

a. Click the Server line to select it. 

b. Click Properties. 

c. Click the Balance option to select it. 

d. Click OK to apply the selection and close the window. 

5. In the Network window, click Close to apply the changes and close the window. 

6. Close the Control Panel window. 

7. Click YES to reboot the server. 

Continue by configuring the FTP service (7.1.12). 

7.1.12. Configuring the FTP Service 

To configure the the FTP service, take the following steps: 



2. Click Start > Programs > Microsoft Internet Server (common) > Internet Services 

Manager. 

3. In the Computer column, double-click the icon associated with the FTP service (FTP 

listed in Service column). 

A tabbed FTP Service Properties screen opens. 

4. Click the Directories tab and configure access as follows: 

a. Select the drive:\InetPub\ftproot (alias ) directory by clicking on it. The 

drive may be C or D. 

b. Click Edit Properties. 



A Directory Properties window appears. 

c. Click the Write check box in the Access section at the bottom of the window to 

enable write access (ensure that a check mark appears in the check box). 

d. Click OK, then Apply, then OK again. 

5. Exit the Microsoft Internet Service Manager. 


7.1.13. Enabling the Guest Account 

Integration Expert and other software products require a Windows NT guest account in 

order to function. To enable the guest account, take the following steps: 



2. Click Start > Programs > Administrative Tools > User Manager for Domains. 

A User Manager window opens. 

3. Double-click the Username line for Guest. 

A User Properties window opens. 

4. Click the Account Disable box to remove the check mark (if there is one). 

5. Click OK, then close the User Manager window. 


7.1.14. Creating a Logical F: Drive 

Create an F drive on each Windows NT node to enable a new volume that can be shared 

for Unisys product information, as well as for user applications. 

To create an F drive: 

1. If you are not currently logged on, power on or restart the Windows NT nodes and log 


2. Click Start > select Programs > Administrative Tools > Disk Administrator. 

You receive a message that you have entered Disk Administration for the first time or 

have added a disk. 

3. Click OK. 

4. Click OK to allow Disk Administrator to place a signature on disks. 

5. Click the Free Space sector of Disk 0. 

6. Right-click to present a menu, then left-click Create. 

You are asked to confirm. 

7. Click Yes. 



8. Enter a value equal to the maximum size listed, then click OK. 

9. (ES2045R only) You receive a warning message that the partition may not be 

accessible to some operating systems, and you are asked to confirm. Click Yes. 

10. Right-click the unformatted segment of Disk 0 to present the menu. 

11. Left-click “Commit changes now.” 



14. Right-click the same unformatted segment of Disk 0 again. 

15. Left-click “Assign drive letter.” 

16. Specify F as the new drive letter, then click OK. 

17. Click Yes to the message asking if you want to continue. 

18. Right-click the same unformatted segment of Disk 0 again. 

19. Left-click Format. 

20. Select NTFS file system, and the default allocation size. 

21. Click Start, then OK. 

Disk formatting proceeds. 

22. Click OK, then Close. 

23. (ES2045R and DR/2 only) Right-click CD-ROM and assign drive letter D. 

Note: Drive letter D may already be assigned. If it is, skip steps 25 through 27. 

24. Right-click CD-ROM 0. 

25. Left-click Assign Drive Letter. 

26. Specify D as the assigned drive letter and click OK. 

27. Close the Disk Administrator window. 

Continue by reapplying the latest service pack (7.1.15). 

7.1.15. Reapplying the Latest Service Pack 

The final configuration step is to reapply the service pack. This subsection gives the 

procedure. 

Notes: 

• For the DR/2, this is the first installation of the service pack. For the ES5085R, 

ES5044R, ES2024R, and ES2045R, it is a reinstallation. 

• The service pack medium supplied provides 40-bit security only. If your site 

requires 128-bit security, download it from the Microsoft Web site. 

• If you have an Install icon for Service Pack n, you can double-click the icon instead 

of using the CD to install the service pack. 



To apply the service pack for Windows NT Server 4.0 

1. Insert the service pack CD-ROM (labeled “Windows NT Service Pack n”) into the drive 

unit. Internet Explorer should start automatically, and a Service Pack home page 

should appear. (See the note below for the exception.) 

Note: If Internet Explorer does not start automatically, take the following steps: 

a. Click Start, then Run. 


b. In the Run window, type the following, then click OK: 

d:\spsetup 

c. Skip to step 3. 

2. Click the Install Service Pack n link, then 

• (IE 4.01 and higher) Select “Run this program from its current location” and 

click OK. 

• (IE 3.02) Select “Open it” and click OK. 


3. A License Agreement screen appears. 

4. Click the check box to accept the license agreement. Uncheck the backup-files box. 

5. Click the Install button. 

Files are copied and the service pack is installed. During installation, a Windows NT 


message: 



the Service Pack n version? 


When setup finishes, a prompt appears to reboot the server. 

7. Click Restart. 

8. After the server finishes rebooting, log on as Administrator. 

9. If a NO button appears, click it to view Y2K.txt message. Otherwise skip to 7.1.16. 

10. Apply the Y2K DAO update. 

a. Click Start, then Run. 

b. Type D:\I386\update\y2ksetup. 

c. Click Yes to install these programs now. 

d. After update completes, click OK to restart the computer. Remove the CD media. 

e. After server reboots, log on as Administrator. The Y2K update will finish. 

Continue with 7.1.16. 


7.1.16. Installing ess Software 


For the installation of your ess software, refer to the Aquanta ess Software Release Notes 

and the ES2000 Getting Started and Reinstallation Guide that came with your server. 

To avoid setup issues, sites installing ess software should use the ClearPath IOE version of 

DEPCON instead of the ess version. 



Upon completion of Windows NT installation, be sure that you have a final copy of your 

Windows NT configuration by creating an emergency repair disk, as follows: 



2. Click Start, then RUN. 

A Run dialog box appears. 

3. In the dialog box type the following, then click OK: 

\winnt\system32\rdisk.exe /s 

A window appears asking if you want to create an Emergency Repair Disk. 

4. Click Yes. 

A window appears instructing you to insert a diskette into the drive unit. 

5. Place a diskette in the drive unit and click OK. 

The Repair Disk Utility window appears. 

6. Click Exit and remove the diskette from the drive unit. 

7. Label the diskette “Windows NT Emergency Repair Disk” and set it aside for later use 

if needed. 

Continue by installing the Single Point Operations Console and related software, as 


7.2. Completing Windows 2000 Installation 

This section describes how to complete installation and configuration of software on an 

ES5044R, ES5085R, or ES2024R node running Windows 2000 Advanced Server. 

To complete a Windows 2000 installation, take the following steps: 

1. Configure the hosts file for ClearPath networking (7.2.1). 

2. Configure the correct number of client licenses (7.2.2). 

3. Install and configure the RAID utility software (7.2.3). 

4. Install and configure ControlIT server software (7.2.4). 



5. Configure the FTP service (7.2.5). 

6. Enable a guest account (7.2.6). 

7. Create a logical F drive (7.2.7). 

8. Install ess software (7.2.8). 

9. Install the service pack (7.2.9). 

10. Create the emergency repair disk (7.2.10). 

Refer to Table 7–1 for procedures that require you to have information or installation 

media available at the time of installation. Obtain these materials before beginning. 


Following installation of Windows 2000 Server, you must set up a hosts file so that the 

Windows 2000 node can communicate with other nodes on the private interconnect (FDDI 

LAN). Take the following steps to set up the hosts file: 

1. If you are not currently logged on, power on or restart the Windows 2000 node and log 




3. Insert the hosts file setup diskette (labeled “NT Installation Tools”) into the drive unit. 


a:copyhost 

Note: On Windows 2000, if there is no disk in the CD drive during the copy, you 

will receive an error message saying that the system is unable to mount the 

volume. Click Continue in the dialogue box to permit the hosts file copy to 

complete. 

Continue by configuring the number of client licenses (7.2.2). 

7.2.2. Configuring the Number of Client Licenses 

Windows 2000 Advanced Server provides 25 client licenses. Additional client licenses may 

be purchased from either Unisys Corporation or Microsoft Corporation. 

Note: The server must have at least one active network connection for this procedure 

to work. It is recommended that you have the FDDI interconnect cabled to 

provide an active connection at this point. 

To set up the correct number of licenses using the Windows 2000 license manager, take the 




2. Click Start > Programs > Administrative Tools > Licensing. 



An Enterprise License Manager window opens. 

3. Click the Purchase History tab (if it is not already in front). 

4. Select License, then New License from the menu bar. 

5. From the Product drop-down box, select Windows Server. 

6. Set the Quantity field to 25 (or, if additional licenses have been purchased, to the 

appropriate number). 

7. In the Comment field, type in the following: 

Initial ClearPath Licenses 

8. Click OK. 

9. In the Per Seat Licensing window, click “I agree,” then click OK to proceed. 

10. Exit License Manager by selecting License, then Exit, from the menu bar or by clicking 

the upper right-hand corner X box. 

Continue with the steps in 7.2.3 


For an ES5044R, ES5085R, or ES2024R node, the RAID utility software to be installed is the 

Global Array Manager (GAM). These are the steps for installing and configuring GAM, 

using the Mylex eXtremeRAID 1100 Controller. 


on as administrator. 

2. Insert the CD labeled "Mylex Solutions Software Kit x.xx" into the CD-ROM drive. 

3. The Mylex Solutions menu appears. Click Install Global Array Manager. 



A Select Components window appears. 

5. Click Global Array Manager Client and Server for installation. Click Next. 

A Choose Destination Folder window appears. 

6. Accept the default and click Next. 

The Installation Summary window appears. 


8. Click Next again to bypass the Modify Server Configuration File setup menu. 

9. Click OK to the informative message. 


11. Click Finish, then remove the CD. 

You can now run the Mylex Global Array Manager utility software, when desired, by 

selecting Start > Programs > Mylex Global Array Manager Client Administrator. Use the 



help menu item from the Global Array Manager Client to learn how to operate it. If you 

have an RAD5003-P64 RAID card in your server and discover that the Array Manager does 

not find the card, you will need to update the driver using the following procedure: 

1. Launch the System applet from Start > Settings > Control Panel > System. 

2. Click the Hardware tab to get to the Device Manager start button. Click the button. 

3. In the device manager, open the “SCSI and RAID controllers” device tree and doubleclick 

the DAC1164P card. 

4. Click the driver tab, then click the Update Driver button. 

5. The Upgrade Device Driver Wizard starts. Click Next. 

6. Click the “Display a list…” option button, then click Next. 

7. Click “Have disk” and insert the Unisys Supplementatl Drivers CD into the server’s 

drive. 

8. Click Browse and select the CD drive (D:) from the drop-down box. 

9. Double-click the win2000 folder. 

10. Double-click the raid folder. 

11. Double-click the Dac960nt folder. 

12. Double-click the Dac1164p folder. 

13. Click to select the Dac1164p file icon, then click Open. 

14. Click OK. 

15. Click to select the RAID controller item, then click Next. 

16. Click Next, then click Finish. 

Continue by installing ControlIT (7.2.4). 


ControlIT software, a product of Computer Associates, enables full monitoring and control 

of Windows NT nodes from the Single Point Operations (SPO) workstation. To implement 

that monitoring and control, ControlIT must be installed and configured on each Windows 

node as described in this subsection. 

The ControlIT software is also installed on the SPO workstation (see Section 11). 

Note: The ControlIT CD-ROM is included in the SPO software package. Use the same 

CD-ROM to install ControlIT on both the SPO workstation and the Windows NT 

node. 

The procedure for installing ControlIT is as follows: 










4. Click I Agree. 




The Installation Wizard screen appears. 

6. Make sure Install Agent Host is checked and Install Agent Viewer is not checked. 

Under Setup Options, select Advanced. 

7. Click Next, then click Next again. 


8. Click OK. 

The Emergency Repair Disk screen appears. 


The Select Destination Directory screen appears. 










After the system reboots, configure ControlIT as follows: 

1. Click Start > then select Programs > Control-IT > Control-IT. 

The main ControlIT screen appears. 

2. Select File, then Preferences. 

A tabbed Change User Preferences screen appears. 

3. Click the General tab and configure the General preferences as follows: 

a. In the box labeled “Start automatically when Windows starts,” click “Start before 

logon” to select it. 

b. Ensure that the check box labeled “Waiting for incoming connection on startup” is 

selected (has a check mark). If it does not, click the check box to select it. 



4. Click the TCP/IP tab and configure TCP/IP preferences as follows: 

a. Click the check box labeled “Allow incoming calls” to select it, if it is not already 

selected. 

b. If the option “Enable inactivity timer” is selected (has a check mark), click its 

check box to deselect it. 

5. Click OK to close the window. 

6. Click File, then click Exit to close ControlIT. 

ControlIT automatically starts in Listen mode, ready to be controlled remotely from the 



7.2.5. Configuring the FTP Service 

To configure the FTP service, take the following steps: 



2. Click Start > Programs > Administrative Tools > Internet Services Manager. 

3. In the tree column, click the appropriate computer to expand it. Then right-click 

“Default FTP Site” in the right-hand pane and click Properties. 

A tabbed Default FTP Site Properties screen opens. 

4. Click the Home Directory tab and configure access as follows: 

a. Click the Write check box in the FTP Site Directory section of the window to 

enable write access (ensure that a check mark appears in the check box). Note 

that the Read and Log Visits boxes are already checked and should be left that 

way. 

b. Click OK. 

c. If an Inheritance Override window appears, Click Select all, then OK. 



7.2.6. Enabling the Guest Account 

Integration Expert and other software products require a Windows NT guest account in 

order to function. To enable the guest account, take the following steps: 



2. Click Start > Programs > Administrative Tools > Computer Management. 

3. Click Local Users and Groups to expand it. Then click Users. 

4. Double-click the Username line for Guest. 



5. 

A Guest Properties window opens. 

Click the Account Disable box to remove the check mark (if there is one). 

6. Click OK, then close the Computer Management window. 


7.2.7. Creating a Logical F: Drive 

Create an F drive on each Windows 2000 node to enable a new volume that can be shared 

for Unisys product information, as well as for user applications. 

To create an F drive: 



2. Click Start > select Programs > Administrative Tools > Computer Management. 

3. Click Disk Management. 

4. Right-click the unallocated sector of Disk 0, then click Create Partition on the menu 

that appears. 

A screen titled Welcome to the Create a Partition Wizard appears. 


A Partition Type menu appears. 

6. Click Primary, then click Next. 

The Partition Size screen appears. 

7. Enter the size of the remaining portion of the disk and click Next. 

The “Assign drive letter or path” screen appears. 

8. Click “Assign a drive letter.” 

9. Click the pull-down arrow and select F. 


The Format Partition screen appears. 

11. Click “Format this partition with the following setups.” 

12. Select NTFS and Default. Under Formatting, enter a volume label, if you wish. Then 

click Perform a Quick Format. 



The new volume is formatted. When the formatting is complete, a message says that 

the volume is healthy. 

15. Close Computer Management. 




7.2.8. Installing ess Software 

For the installation of your ess software, refer to the appropriate manuals that came with 

your server: 

• Aquanta ess Software Release Notes 

• Aquanta ES5000 Series with Windows NT Getting Started and Reinstallation Guide 

• Aquanta ES2000 Series with Windows NT Getting Started and Reinstallation Guide 

To avoid setup issues, sites installing ess software should use the ClearPath IOE version of 

DEPCON instead of the ess version. 


7.2.9. Installing the Service Pack 

Follow this procedure to install the service pack for Windows 2000: 

1. Insert the service pack CD-ROM (labeled “Windows 2000 Service Pack n”) into the 

drive unit. Internet Explorer should start automatically, and a Service Pack home page 

should appear. (See the note below for the exception.) 

2. Click the Install Service Pack n link, then click the blue-highlighted “Click here” to 

install service pack n. 

The file download menu appears. 

3. Click “Run this program from its current location,” then click OK. 

The security warning window appears. 

4. Click Yes to continue. 


5. Click the check box to accept the license agreement. Uncheck the backup-files box. 

6. Click the Install button. 

Files are copied and the service pack is installed. When setup finishes, a prompt 

appears to reboot the server. 

7. Click Restart. 



Upon completion of Windows 2000 installation, be sure that you have a final copy of your 

Windows 2000 configuration by creating an emergency repair disk, as follows: 



2. Click Start > Programs > Accessories > System Tools > Backup. 



A screen with a menu appears: Welcome to the Windows 2000 Backup and Recovery 

Tools. 

3. Click the Emergency Repair Disk option. 

A window appears instructing you to insert a diskette into the drive unit. 

4. Click “Also back up the registry directory.” 

5. Place a diskette in the drive unit and click OK. 

The Repair Disk Utility window appears. 

6. Click Exit and remove the diskette from the drive unit. 

7. Label the diskette “Windows 2000 Emergency Repair Disk” and set it aside for later 

use if needed. 

Continue by installing the Single Point Operations Console and related software, as 





Section 8 

Installing UnixWare 7 

This section tells you how to install the UnixWare 7 operating system on an Intel server 

node. A full installation, with the checklist in Table 8–1 completed, and all software media 

readily available, takes about 2 hours. 



ES2045R (VX1525) UnixWare 7 operating system IXS7105-UW 

Mylex DAC960 PJ RAID controller RAD9602-PCI 


Intel PRO 100+ Ethernet ETH1010052-PCI 

DR/2 (VX1325) UnixWare 7 operating system IXS7105-UW 

Mylex DAC960 PJ RAID controller RAD9602-PCI 


ES2085R UnixWare 7 operating system IXS7105-UW 

Mylex DAC1164P RAID controller RAD5003-P64 


Intel PRO 100+ Ethernet ETH1010053-PCI 

Table 8–1 lists media and information for the various installation scenarios (installation 

with preloaded software, full installation, and steps you need to take in either instance). 




Table 8–1. UnixWare 7 Installation Checklist 


8.2. Steps to Take if Software Is Preloaded 

Media needed: Tuning script diskette—labeled “UnixWare 7 Intel Server Node” 


System Licensing prompt 

Serial number: 

Activation key: 

Type this information exactly as found on the SCO license certificate provided with the installation 

media inside the SCO UnixWare package. 



You are prompted whether or not you want daylight saving time support. 


Media needed: 

• Disk array controller configuration utility (DACCF) diskette—labeled “DAC960P Configuration and 

Utilities” 

• Blank 3-1/2-inch diskette (label this diskette “RAID Configuration Backup”) 

• (ES2045R and DR/2 only) MS-DOS bootable diskette (must be supplied by CSR or customer) 

8.4.1. Installing the Operating System 

Media needed: 

• Boot diskettes— labeled ”Unisys UnixWare 7 Installation Diskette Vol: 1 of 2” and "Unisys UnixWare 

7 Installation Diskette Vol: 2 of 2” 

• UnixWare host bus adapters (HBA) diskette—labeled “Unisys UnixWare 7 Operating System 

PSK/UNX71-PSK Host Bus Adapter” 

• UnixWare operating system CD-ROM—labeled “SCO UnixWare 7 Runtime” 

• Platform Support Module (OEMPSM) diskette—labeled “Unisys UnixWare 7 Operating System 

PSK/UNX71-PSK PSM” 

• Blank 3-1/2 inch diskette (label this diskette “System Configuration Backup” 


• Zone (default America) ______________________________ 

• Locale (default C (English)) ______________________________ 

• Keyboard type (language) to use (default United States) ______________________________ 

continued 


Table 8–1. UnixWare 7 Installation Checklist 



Serial number: 

Activation key: 


The UnixWare serial number and activation key are found on the SCO license certificate provided with 

the installation media. 

Node name of the system (obtain from customer) ____________________________ 

Date, Time, and Time Zone prompt 



You are prompted whether you want daylight saving time support. 

8.4.2. Installing the UnixWare and Open Server Development Kit (UDK) 

Media needed: UnixWare 7 UDK CD-ROM—labeled “UnixWare and Open Server Development Kit” 

8.4.3. Installing the Drivers Updates 

Media needed: UnixWare 7 Drivers Updates diskette—labeled “Drivers Update” 

8.6. Configuring the Network Adapter 


• Domain name ______________________________ 

• IP address ______________________________ 

• Default router IP address ______________________________ 

8.6.2. Configuring a Domain Name Service Client 


• Local domain name for the server (obtain from customer) ______________________________ 

• Either of the following (obtain from customer): 

− Up to 6 domains to search for host names 

_________________________ _________________________ 

_________________________ _________________________ 

_________________________ _________________________ 

− Up to 3 DNS name servers to search, in order 

_________________________ 

_________________________ 

_________________________ 

8.8. Installing and Running the Tuning Script (Site-Installed UnixWare) 

Media needed: Tuning script diskette—Labeled “UnixWare 7 Intel Server Node” 

8.12. Creating and Using UnixWare Emergency Recovery Diskettes 

Media needed: Two blank diskettes for creating UnixWare node emergency recovery diskettes. 




Caution 

To prevent installation problems, or wasted time, determine whether or not 

UnixWare has been preloaded. Then follow either the procedure for preloaded 


Updated information may be available in the Web version of this document: 


To determine if UnixWare is preloaded, power on the system. If UnixWare is preloaded, 

the system boots. Otherwise, the system displays the following error message: 

Missing operating system 

Cannot boot UnixWare. 

If UnixWare is preloaded, perform the steps in 8.2. 

If UnixWare is not preloaded, perform the steps from 8.3 through 8.11. 

Disk partitions are as follows: 

• ES2085R—The default (and minimum) hard disk configuration of the UnixWare node 

is one logical disk. Two physical disks are configured as one logical 18-GB disk with 

mirroring at RAID level 1. (It is partitioned that way when UnixWare is preloaded.) 

• ES2045R and DR/2—The default (and minimum) hard disk configuration of the 

UnixWare node is one logical disk. Two physical disks are configured as one logical 9- 

GB disk with mirroring at RAID level 1. (It is partitioned that way when UnixWare is 

preloaded.) 


8.2. Steps to Take If Software Is Preloaded 


If the UnixWare operating system is preloaded, take the steps in 8.2.1 through 8.2.3. 

Notes: 

• Perform this procedure only if the UnixWare operating system was loaded at the 

factory (you have not copied the operating system from the installation CD-ROM. 





8.2.1. Entering the License 

Follow these steps to enter the license information. 

1. At the console screen, log on as the root user (user-id root) (8.12.1). 

loginid: root 

pswd: unisysas 

2. In the Task bar, click the second arrow from the right (above the fifth icon from the 

right) to present the SCO menu. 

3. Click SCO Admin. 

4. Double-click License Manager. 

5. Click License. 

6. Click Add. 

7. Enter License Info. Click License button. 

8. Click OK. 

9. If you have a license for the UDK or any other additional licenses, enter them now by 

repeating steps 4 through 7. 

10. When you have finished entering licenses, click Host, then click Exit. 

8.2.2. Changing the Host Name 

Follow these steps to change the host name. 

1. Open the console terminal window by clicking the dtterm icon in the upper left-hand 

corner. 

2. Type setuname -n newsystemname and press Enter. 

3. Type uname -a to verify the new system name. 



8.2.3. Changing the Date and Time Zone 

Follow these steps to change the date and time zone. 

1. Open the SCO Admin window. 

2. Scroll to the System folder and double-click. 

3. Double-click System Time Manager. 

4. Click Host. 

5. Click Change Time Zone. 

6. Select the appropriate country and time zone and click OK. 

7. After reading the time zone change message, click OK. 


9. Click Set Time. 

10. Enter the correct time and date. Click OK. 

11. Click OK when the message appears saying the system time will change. 

12. In the upper left-hand side of the window, click Host. 


14. In the SCO Admin window, click File and then Exit. 

15. Click Exit on the lower bar and then click OK to log off. 

16. Perform all of these tasks as described in other subsections: 

a. Configure the Ethernet and FDDI network adapters (8.6.1). 

b. Configure a domain name service client (8.6.2). 

c. Set up the documentation search engine (8.7). 

d. Run the tuning script (8.8). 

Note: Answer Y to “Did you install the OS?” 

e. Retrieve and apply fixes (8.9) 

f. Configure Internet FastStart (8.10). 

After you have completed all these steps, you are returned to the terminal session 

prompt. 

17. Enter the following command to reboot: 

# shutdown- y - g0 - i6 

Reboot takes about 7 minutes. When it is done, UnixWare displays the GUI logon 

screen. 

18. Log on as the root user (user-id root) (8.11.1). 

The UnixWare root prompt (#) appears. Procedures for preloaded UnixWare 7 

configuration are completed at this point. 




The steps for installing and configuring a new RAID disk array controller (DAC) are as 

follows: 

1. Load the DACCF Utilities (8.3.1). 

2. Complete the RAID configuration (8.3.2). 

Note: If you are performing a full installation on a system that was preloaded, do not 


volume before you reload the operating system. Formatting the disk makes the 

drive unrecognizable to the software. 

8.3.1. Load DACCF Utilities 

Follow the procedures for the type of node you are configuring (DR/2, ES2045R, or 

ES2085R). 

Loading DACCF Utilities on an ES2045R or DR/2 Node 

To load DACCF utilities on an ES2045R or DR/2 node, do the following: 

1. Insert a DOS bootable diskette. 

2. When the MS-DOS prompt appears, remove the diskette and insert the diskette labeled 

“DACCF CONFIGURATION AND UTILITIES” in drive A. 


Loading DACCF Utilities on an ES2085R Node 

To load DACCF utilities on an ES2085R node, do the following: 

1. Turn on the power. 

2. During booting, press Alt-R when the DAC1100 BIOS begins to load. 


8.3.2. Complete the RAID Configuration 

Follow one of the two procedures below to finish configuring the RAID controller. 

Procedure for the ES2045R and DR/2 Nodes 

1. Change directories on the A drive by typing CD DACCFG, then press Enter. 

CD DACCFG 



2. Start the DACCF utility by typing DACCF and pressing Enter: 

DACCF 

Note: If more than one DAC is installed, a list is displayed so you can select the 

DAC to be configured. 

The DACCF utility Main Menu should appear as follows: 

Main Menu 

01. Automatic Configuration 

02. New Configuration 

03. View/Update Configuration 

04. Rebuild 

05. Initialize System Drive 

06. Consistency Check 

07. Tools 

08. Select DAC960 

09. Advanced Functions 

10. Diagnostics 

If you get an Installation Aborted message and a list of detected drives instead of the 

menu, take the following steps: 

a. Press any key to proceed. A drive matrix appears, showing the current 

configuration (Figure 8–1). 

b. Press S to save the current configuration. 

A message indicates you should reboot. 

3. Reboot and reload the DACCF utility. 

a. Reboot. 

b. Insert a DOS-bootable diskette. 

c. When the MS-DOS prompt appears, remove the diskette and insert the diskette 

labeled “DACCF CONFIGURATION AND UTILITIES” in drive A. 

4. Change directories on the A drive by typing CD DACCFG, then press Enter. 

CD DACCFG 

5. Start the DACCF utility by typing DACCF and pressing Enter: 

DACCF 

6. In the DACCF utility Main Menu, use the arrow keys to select 02 (New Configuration), 


The New Configuration menu appears as follows: 


1. Define Pack 

2. Define System Drive 



7. Use the arrow keys to select 1 (Define Pack), then press Enter. 

A screen containing a drive matrix and the Pack Definition menu appears: 

Pack Definition 

1. Create Pack 

2. Cancel Pack 

3. Arrange Pack 

4. Device Information 

Tgt 

ID 

0 

1 

2 

3 

4 

5 

6 

Channel Number 

0 1 


2 

RDY 

RDY 

Figure 8–1. ES2045R and DR/2 Drive Matrix 

8. Use the arrow keys to select 1 (Create Pack), then press Enter. 

A small cursor moves to the drive matrix so you can select the drives to be included in 

the pack. 

9. Select the drives for drive pack 1 as follows: 

a. Use the arrow keys to move the cursor to drive 2,0 (channel 2, target ID 0). 

b. Press Enter to select the drive.


c. Repeat steps a and b for drive 2,1. 

You are returned to the Pack Definition menu. 

10. Press Enter to select the Arrange Pack option. 

The cursor moves to the drive matrix. 

11. Press Enter again to arrange the pack. 

The pack being arranged moves to the pack table on the screen and the New 

Configuration menu is redisplayed. 




12. Select 2 (Define System Drive), then press Enter. 

Two tables are displayed on the left side of the screen. The top left table lists all the 

arranged packs and their sizes. The bottom left table is empty (no system drives have 

been defined). 

A System Drive Definition menu is displayed on the right side as follows: 

System Drive Definition 

1. Create System Drive 

2. Toggle Write Policy 

13. Select 1 (Create System Drive), then press Enter. 

All arranged packs that are not part of a system drive are selected for the system drive. 

A RAID Level window is displayed: 

RAID Level 

RAID 0 

RAID 1 

RAID 5 

RAID 6 

RAID 7 

14. Select RAID 1, then press Enter. 

A window appears that displays the maximum possible size for the system drive to be 

defined. 

15. Press Enter to use the entire disk. 

An information window describes the drive being created, followed by a confirmation 

window. 

16. Select Yes, then press Enter. 

The system drive is created and the system drive table on the bottom left is updated. 



17. Change the write policy for the drive from write-through (write cache not enabled) to 

write-back (write cache enabled) as follows: 

a. Select 2 (Toggle Write Policy) from the System Drive Definition menu, then press 

Enter. 

The cursor jumps to the Write Mode column in the system drive table. 

b. Press Enter to toggle the write mode. 

18. Press Esc to return to the System Drive Definition menu; then press Esc twice again to 

return to the Main Menu. 

A confirmation window appears asking whether you want to save the configuration. 


The configuration is saved, and you are notified that drive 0 is available for immediate 

use. 


The Main Menu is redisplayed. 

Main Menu 

01. Automatic Configuration 

02. New Configuration 

03. View/Update Configuration 

04. Rebuild 

05. Initialize System Drive 

06. Consistency Check 

07. Tools 

08. Select DAC960 

09. Advanced Functions 

10. Diagnostics 

21. Select 05 (Initialize System Drive), then press Enter. 

The Initialize System Drive menu appears. 

Initialize System Drive 

1. Select System Drive 

2. Start Initialize. 

22. Select 1 (Select System Drive), then press Enter. 

A screen appears that lists all of the defined system drives on the left side. The 

following messages appear on the right side and below the list: 

More than one System Drive can be 

initialized simultaneously. Select 

to start initialization of the selected 

System drives. 

!!WARNING!! Initialization of the System 

Drives will destroy data on the drives. 

Select System drive(s) using cursor keys, hit , to Previous 

Menu 



23. Initialize the system drive as follows: 

a. Use the arrow keys (or press Tab) to highlight the system drive, then press Enter. 

b. Hit Esc key. 

This returns to previous menu. 

c. Select 2, press Enter. 

d. Select Yes, press Enter. 

A confirmation message appears. 

e. Select Yes, press Enter. 

The system drives are initialized simultaneously. Initialization takes from 1 to 2 

hours with 2-GB drive units. A progress bar appears for each drive unit. 

Once initialization is complete, a message to that effect is displayed. 

24. Press any key to return to the Main Menu. 

25. Select 03 (View/Update Configuration), then press Enter. 

A View/Update Configuration menu appears as follows: 

View/Update Configuration 



3. Add Drive to Last Pack 

26. Select 2 (Define System Drive), then press Enter. 

The System Drive Definition screen and menu appear. 

27. Change the write policy for the drive back to write through from write back as follows: 

a. Select 2 (Toggle Write Policy) from the System Drive Definition menu, then press 

Enter. 

The cursor jumps to the Write Mode column in the system drive table. 

b. Press Enter to toggle the write mode. 

28. Press Esc to return to the System Drive Definition menu; then press Esc twice again to 

return to the Main Menu. 

A confirmation window appears asking whether you want to save the configuration. 


The Main Menu is redisplayed. 

30. Use the arrow keys to select 07 (Tools), then press Enter. 

The Tools menu appears as follows: 

Tools 

1. Bad Block Table 

2. Error Counts 

3. Format Drive 

4. Make Online 


5. Kill Drive 

6. Backup/Restore Conf 

7. Clear Configuration 

8. Print Configuration 

31. Use the arrow keys to select 6 (Backup/Restore Conf), then press Enter. 

The Backup/Restore Conf menu appears as follows: 

Backup/Restore Conf 


Backup Configuration 

Restore Configuration 

32. Select the Backup Configuration option, then press Enter. 

You are prompted to enter a file name where the configuration is to be stored. 

33. Insert a blank diskette labeled “RAID Configuration Backup” into the drive unit, then 

enter the file name and press Enter. 

A confirmation message indicates that any existing file of the same name will be 

overwritten on the diskette. 


The configuration is saved to diskette. 

35. Press Esc to return to the Main Menu. 

An exit confirmation screen appears. 

36. Select Yes to exit. 

The A:\ prompt is displayed. 

37. Remove the diskette and reboot. 

Now install the UnixWare 7 operating system as described in 8.4. 

Procedure for the ES2085R Node 


Notes: 


2.5.2). 

• In step 2, you must press Alt-R within a few seconds to enter the BIO Options 

Utility. 


configuration procedure; otherwise, the normal boot procedure continues. 





Several start-up messages appear including a prompt to press Alt-R, as follows: 






> 

2. Press Alt-R to start the BIOS Options Utility. A BIOS options menu appears: 


BIOS enabled 






Enabled. 


























Automatic 

Assisted 

Custom 











Spare: No 





1:00 UNISYS ....... 17.0 Online 

1:01 UNISYS ....... 17.0 Online 












Continue by installing the operating system as described in 8.4. 



8.4. Installing the UnixWare 7 Operating System 

If you must install the UnixWare 7 operating system software, perform all of the steps in 

this subsection (8.4.1 through 8.4.3). 

Cautions 

• This procedure should be used only to initially install the operating system. 

Because this is a destructive procedure, make sure you have read and 

understand the procedure before proceeding. 

• During the procedure, be sure the Caps Lock key does not become locked in 

the uppercase position while making entries. Use the Shift key if you want to 

enter an uppercase password. 

Note: Switch the monitor concentrator to the Intel Node position before beginning (see 

2.5.2). 

8.4.1. Installing the Operating System 

This subsection applies to all systems (ES2045R, ES2085R, and DR/2). 

To install the operating system: 

1. With the power off, insert the boot diskette #1 (labeled “Installation Disk Vol: 1 of 2”) 

into the primary (boot) diskette drive unit. 

If you have more than one diskette drive, and you do not know which is the primary 

drive, see your computer hardware manual. 

2. Turn the power on. 

After hardware information is displayed, you see a “starting UnixWare” message and 

the SCO logo. It may take several minutes to load the system from the installation 

diskette. You are asked to select a language for the installation. 

3. Select a language and press Enter. You receive a prompt to insert the second 

installation diskette. 

4. When you receive the prompt, insert the boot diskette #2 (labeled “Installation Disk 

Vol: 2 of 2”) into the diskette drive and press Enter. 

After a brief delay, the Welcome window appears. 

5. Press F10 to continue. 

You are prompted to select the zone, locale, and keyboard type. 



6. Select the zone, locale, and keyboard appropriate for the site, and press F10 to apply 

your selections. 

The following are default selections for a U. S. installation: 

Zone America (Latin - 1) 

Locale C (English) 

Keyboard United States 

You are prompted for licensing information. 

7. Enter the license number, license code, and other license data from the information 

preprinted on the installation package, and press F10 to apply. 

Note: All licensing information is case-sensitive. 

You are prompted with the option to load hardware configuration information from 

the HBA diskette. 

8. Remove the boot diskette from the drive. 

9. Insert the host bus adapter diskette (labeled “Unisys UnixWare 7.x.x Operating System 

PSK/UNX71-PSK Host Bus Adapter (HBA)”) into the drive. 

10. Press F10. 

After the diskette is loaded, you are prompted to install additional HBA diskettes. 

11. Remove the HBA diskette from the drive. 

12. Select Proceed with Installation and press F10. 

The Device Configuration Utility (DCU) window appears. 

13. Select Do Not Enter the DCU (auto-configure drivers). 



Please wait while the system hardware drivers are loaded 

You are prompted for the node name of the system. 

15. Obtain the node name of the system from the customer. Enter the node name and 

press F10. 

Note: Do not enter a fully qualified node name that includes the domain. You can 

enter the domain name later during network configuration. 

The Select Installation Method menu appears. 

16. Insert the Enterprise Edition CD-ROM 1 of 3 into the drive. 

17. Select Install from CD-ROM and press F10. 


Please wait while the installation media (cdrom) is verified 



Then the following menu appears: 

Disk Configuration 

Disk No. Character Node Action 

======== ========= ==== ====== 

1 /dev/rdsk/c0b0t0d0s0 Use whole disk for Unix 

18. Configure up to two detected hard disks. Do the following for each disk you 

configure: 

a. Use the Tab key to select the disk to configure. 

b. For the first disk, select Use whole disk for Unix. This uses the whole disk for 

UnixWare 7 and removes all data on existing partitions. 

c. For the second disk (optional), you can select Do not modify. 

After you have selected the options for the disks you want to configure, press F10. 

The following menu appears: 

Choose one 

(*) Use default filesystem sizes and types 

( ) Customize filesystem and slices 

19. Select Customize filesystem and slices, press Enter. 

Change the values on the screen as shown below. 

Note: To change the type to vxfs, as instructed below, press F2, tab to vxfs, and 

press Enter. 

For a 9-GB disk: 

• Root File System (/)—Change size to 2048. Keep the file system type default 

(vxfs). 

• Boot File System (/stand)—Accept the default; do not change the size. 

• Swap Slice (/dev/swap)—Accept the default; do not change the size. 

• User File System (/home)—Change the type to vxfs (see note above) and the size 

to 2048. 

• Second User File System (/home2)—Change the type to vxfs and the size to 2048. 

• Var File System (/var)—Change the type to vxfs and the size to the remaining disk 

space. 

For the rest of the settings, accept the defaults. 

For an 18-GB disk: 

• Root File System (/)—Change size to 9654. Keep the file system type default 

(vxfs). 



• User File System (/home)—Change the type to vxfs (see note above) and the size 

to 2048. 




• Var File System (/var)—Change the type to vxfs and the size to the remaining disk 

space. 




Choose one 

(*) Use default disk options 

( ) Customize disk options 

21. Select Use default disk options and press F10. 

The Choose System Profile menu appears. 

22. Customize your configuration as follows: 

a. Select Customize Installation of Packages and press F10. 

b. Select Core System Services and press F10. 

c. Select Extended OS Utilities and press F2. 

d. Select Select all packages (FULL) and press Enter. 

e. Verify that State of Extended OS Utilities Service is set to Full. 

f. Press F10. 

g. Select Accept Current Selection and Continue, then press F10. 

The Choose Platform Support Module menu appears. 

23. Select a platform support module: 

a. Press PageDown. 

b. Tab to Add-on Platform Support Module Diskette. 

c. Press Enter. 

The system now attempts to detect a network adapter. It should detect two. 

The Select Network Adapter menu appears. 

24. Select Defer network configuration and press F10. (This procedure is performed later; 

see 8.6.1.) 

You are next prompted for the time, date, and time zone. 

25. Enter the correct time, date, and time zone for the locale. (For time zone selection, 

press F2.) 


You are next prompted for the security level. 

27. Select Traditional and press F10. 

An Owner’s Account screen appears with the following fields: 

Owner's name: 

Owner's login ID: 

Owner's user number: 101 



Password: 

Re-enter Password: 

28. Enter the following: 

• unisys as the owner’s name 

• unisys as the owner’s logon ID 

• (default) as the owner’s user number. 

• unisysas for the password 

Note: Passwords do not appear on the screen as they are typed. Sites must later 

change all passwords during site customization. 


A Root Account Password screen appears. 

30. Enter unisysas as the password. This is the default installation password. 

Note: If it is preferred, you can enter a site-supplied password. 

31. Tab to the next line and reenter the password, then press F10. 

Note: Do not forget the root account password. If you forget this password, you 

must completely reinstall the system to set up a new one. 

32. View the license terms, select Accept, and press F10 when you are finished. 

You are then prompted to continue the installation. 

33. If you need to change any information in the installation, you can step back through 

the installation by pressing F9. 

34. Save the installation information to a blank formatted diskette by doing the following: 

a. Insert a blank formatted diskette into the diskette drive. 

b. Press F3. 

You can use the diskette to quickly reinstall this system, or another UnixWare 7 

system, using the same installation responses. 

35. Continue the installation by pressing F10. 

The software load begins. This process typically takes from 40 to 60 minutes. The 

software load can continue unattended. 

During the software load, you can track the progress of the installation by viewing 

progress indicators that are displayed for each package loaded. 

You are prompted to insert the HBA diskette when the software load is completed. 


PSK/UNX7-PSK Host Bus Adapter (HBA)”) into the drive and press Enter. 

You are prompted to insert the platform support module (PSM) disk. 

37. Insert the PSM (Unisys) diskette into the diskette drive and press Enter. 

The kernel (/stand/unix) is rebuilt. This process takes several minutes. A message is 

displayed when the kernel is successfully rebuilt. 

38. Remove all diskettes, tapes, and CD-ROMs and store them safely. 



39. Press any key to reboot the UnixWare 7 system. 

After the system reboots, a Mouse Selection screen appears. 

40. Configure the mouse as follows: 

a. Tab to select the PS/2-compatible mouse, then press F10. 

b. The default number of buttons is two. Press F10. 

c. Press Enter to start the mouse test. 

d. Move the mouse. 

e. Press a mouse button to end the test. 

When you are finished testing the mouse, the following message appears: 

To continue installing the system, insert CD-ROM #2 and press . 

41. Insert the CD-ROM and press F10. 

42. When the window “Select products to install” appears, press Enter. 

43. At Enhanced Event Logging System Installation, Enter Default Database Location 

window, tab to apply and press Enter. 

44. When the window “The following products were successfully installed:” appears, 

press F10. 

45. Another message appears asking for CD-ROM #3. Press . 

The system automatically boots into multi-user mode. 

Installation of the UnixWare 7 operating system is now complete. 

Continue by installing the UnixWare and Open Server Development Kit (8.4.2). 

8.4.2. Installing the UnixWare and Open Server Development Kit 

(UDK) 

Note: This procedure is required for each ClearPath IX node running the UnixWare 7 

operating system. 

To install the UnixWare and OpenServer Development Kit (UDK): 


2. Insert the UnixWare 7 UnixWare and OpenServer Development Kit (UDK) CD-ROM 

into the CD-ROM drive. 

3. From the command line at the root directory, type the following command, and press 

Enter: 

pkgadd -d cdrom1 


You receive a message asking you not to remove the CD-ROM from the drive. Then 

you are prompted to select the package you want to add (there is only one). 



5. Press Enter to accept the default (all packages) and continue. 

A UnixWare Open Server Development Kit Installation, Package Selection window 

appears. 

6. For this window and the next window, do the following for each package listed: 

a. Tab to the package. 

b. Use the right-arrow key to change the selection to Yes, to install the package. 

7. Tab to Apply and press Enter. 

A Package Installation Options screen appears. 


The software packages are loaded. (This takes about 30 minutes.) Then the licensing 

window appears. 


preprinted on the license form. 

If you do not have a license, tab to Apply and press Enter. At the No Valid License 

window, press Enter. (If a license is obtained later, it can be installed using the 

License Manager in SCO Admin.) 

Note: All license information is case-sensitive. 


An Installation Results screen appears. 


A second Results screen appears. 


13. Type q and press Enter to quit. 

Next, reload the UW7.1.1 update: 

1. Insert the CD-ROM 2 of 3. 

2. Open the console window and enter 

pkgadd -d cdrom1 update711 

3. Type go and press Enter. 

A Disk Space Usage window appears. 


5. Enter the following command to reboot the system, so that all changes can take effect: 

shutdown -y -g0 -i6 

Rebooting takes several minutes, because the kernel is being rebuilt in the 

background. 

Continue by installing the drivers updates (8.4.3). 


8.4.3. Installing the Drivers Updates 


To install the UnixWare 7.x.x Drivers/Updates diskette (Unisys), do the following: 


2. Insert the UW 7.x.x Drivers/Updates diskette into the primary diskette drive. 

3. Open the console window. 

4. From the command line at the root directory, enter the following pkgadd command 

and press Enter: 

pkgadd -d diskette1 


You receive a message asking you not to remove the diskette from the drive. Then you 

are prompted for the number or name of the package you want to add. 

6. Enter package number 1. 

Read each information screen for the package, repeating these steps as necessary: 

a. Press Enter each time to move to the next screen. 

b. Select Y to proceed with installation. 

7. 

You receive a message when the installation is completed. 

Type q and press Enter to quit. 

8. Remove the diskette from the drive and store it safely. 

9. Shut down the system by doing the following (from the graphical interface): 

a. In the task bar, click the second arrow from the right, above the fifth icon from the 

right, to present the SCO menu. 

b. Click the SCO Admin icon. 

c. Double-click System. 

d. Double-click System Shutdown Manager. 

e. Select Shutdown. 

f. Select Begin Shutdown. 

g. Select OK. 

h. Select OK. 

Note: System shutdown is configured for a 1-minute wait. 

10. Press any key to reboot. 

11. After the system restarts, log on as the root user (user-id root) (8.12.1). 

Add and run the tuning script. Continue by installing and running the tuning script (8.8). 



8.5. Granting User Privileges 

If you need to grant privileges to a user (for example, the system owner), execute the 

following commands as the root user: 

# /bin/adminuser -n -a pkgadd:/user/sbin/pkgadd:dacread:dacwrite user_name 

# /bin/adminuser -a pkgrm:/user/sbin/pkgrm:dacread:dacwrite user_name 

The user can then execute pkgadd or pkgrm as follows: 

$ /sbin/tfadmin /usr/sbin/pkgadd 

$ /sbin/tfadmin /usr/sbin/pkgrm 

8.6. Configuring the Network Adapter 

This subsection explains how to configure the network adapter and how to configure a 

domain name service client. 

8.6.1. Configuring the Ethernet and FDDI Network Adapters 

Configure the network adapter by doing the following (from the graphical interface): 

1. Log on as the root user (user-id root) , if you are not already logged on (8.12.1). 

2. In the task bar, click the second arrow from the right, above the fifth icon from the 


3. Click the SCO Admin icon. 

4. Scroll to Networking and double-click. 

5. Double-click Network Configuration Manager. 

6. Select Hardware. 

7. Select Add new LAN adapter. 

8. Select the following adapter: 

ES2045R and DR/2: 

Ethernet - Intel(R) PRO/100B / PRO/100 + (7.1.1 - v1.3.9) - PCI Slot 7 Bus 3 

Device 4 Function 0 

ES2085R: 

Ethernet - Intel(R) PRO/100B / PRO/100 + (7.1.1 - v1.3.9) - PCI Slot 4 Bus 3 

Device 4 Function 0 

9. Select Continue. 

As the adapter is added, you are prompted to select a protocol. 

10. Select TCP/IP. 

11. Select Add. 

You are prompted for your domain name, IP address, and default router. 



12. Enter the domain name, IP address, and default router, and click OK. 

You receive a message when the adapter has been successfully added. 

13. Click OK. 

14. Click OK again. 


16. Select Add new LAN adapter. 

17. Select the following adapter : 

SysKonnect FDDI PCI Adapter - PCI Slot x Bus x Device x Function 0 

18. Select Continue. 

The Network Driver Configuration dialog box is displayed. Select OK. 

As the adapter is added, you are prompted to select a protocol. 

19. Select TCP/IP. 

20. Select Add. 

21. Enter the domain name, IP address, and default router, and click OK. 

Enter the correct information in the required fields as follows (do not change other 

fields): 

• Node name—Enter the assigned node name (for example, fddiuxsr for UnixWare 

node 1) as identified in Appendix B. 

• Domain name—Enter the domain name for the site (for example, 

companyname.com) 

• System IP address—Enter the assigned IP address for this node (for example, 

192.168.57.4 for UnixWare node 1) as identified in Appendix B. 

• Netmask—255.255.255.0 

You receive a message when the adapter has been successfully added. 

22. Select OK. 


24. Select Exit. 

Continue by configuring a domain name service client (8.6.2). 

8.6.2. Configuring a Domain Name Service Client 

To configure a domain name service client, do the following (from the graphical interface): 

1. Double-click Client Manager. 

2. Double-click DNS client. 

3. Enter either one of the following: 

• Domain search order 



Enter a list of up to 6 domains to search for a host name that does not include a 

domain name. For each domain you enter, click Add to add the domain to the list. 

You should include the local domain in this list. 

Host names are searched in the order in which you specify them in this list. Click 

Promote or Demote to move the selected item to a different position in the order. 

• Name server search order 

Enter a list of up to three DNS name servers, specified by their IP addresses. For 

each server address you enter, click Add to add the server to the list. 

If the host you are configuring is already configured as a domain name server, 

specify it first in the list. Use the loopback IP address (127.0.0.1). 

The resolver queries each DNS server in the list, in the order listed, until it receives 

an answer. Click Promote or Demote to move the selected item to a different 

position in the order. 

4. Click OK. 

5. Select Host. 

6. Select Exit. 

8.7. Setting Up the Documentation Search Engine 

To set up the documentation search engine, follow these steps: 

1. Run the following command as the root user (user-id root) in the console window: 

/usr/man/bin/config_search -f 

This takes approximately 15 minutes. 

2. Reboot. 

Continue by installing and running the tuning script (8.8). 

8.8. Installing and Running the Tuning Script (Site- 

Installed UnixWare) 

Note: Perform this procedure only if you installed the UnixWare operating system 

and entered site-specific information as described in 8.4. If the UnixWare 

operating system was preloaded, install and run the tuning script as described 

in 8.2. 

The tuning scripts diskette contains a script you must run to complete installation and 

configuration of the UnixWare operating system IOE. Take the following steps to install 

and run that tuning script: 

1. If you are not already logged on, log on as the root user (user-id root) (see 8.12.1). 

2. Open the console window. 



3. Insert the tuning scripts diskette (labeled “UnixWare 7 Intel Server Node”) into the 

disk drive and enter the following command to install and execute the tuning script 

(cptune): 

# pkgadd-d diskette1 cptune 

A prompt to insert the diskette appears: 

Insert diskette into Floppy drive 1. 

Type [go] when ready, 

or [q] to quit (default: go) 


Messages appear, prompting you to enter commands to change directories and start 

the tuning script: 

ClearPath tuning and configuration script 

Version x.x 

Copyright (c) 1997 Unisys, Inc. All Rights Reserved. 

## Processing package information. 

## Processing system information. 

## Verifying disk space requirements. 

Installing ClearPath Tuning and configuration script as 

## Installation of part 1 of 1 is complete. 

## Executing postinstall script. 

Please enter the following commands to complete the ClearPath tuning: 

cd /var/sadm/pkg/cptune/install 

sh CP_tune 

Installation of ClearPath Tuning and Configuration Script (cptune) 

was successful. 

5. As indicated in the message, enter the cd and sh commands as follows: 

# cd /var/sadm/pkg/cptune/install 

# sh CP_tune 

A prompt asks whether or not the script is being run on the SPO server. 

Is this a SPO server? 

6. Enter N (no) to indicate that this is not the SPO server. 

You are asked whether the operating system was installed by you or by the factory. 

If you installed the UNIXWARE OS, you have already 

configured it. If the OS was installed at the 

factory, you need to customize it for your site. 

Did you install the UNIXWARE OS? [Y/n]: 

7. Type Y, then press Enter to indicate that you installed UnixWare. 

Note: Enter Y for preloaded disks also. 



A series of messages appears relating to kernel parameters being set and the setting up 

of partitions on disk. 

Tuning SEMMNI 500 

Tuning SEMMNS 800 

Tuning SEMMSL 300 

Tuning SHMMNI 256 

Tuning MSGMNI 128 

Tuning SHMMAX 134217728 

Tuning NPROC 1600 

Tuning MAXUP 1200 

Tuning SDATLIM 0x7FFFFFFF 

Tuning HDATLIM 0x7FFFFFFF 

Tuning SVMMLIM 0x7FFFFFFF 

Tuning HVMMLIM 0x7FFFFFFF 

Tuning SFSZLIM 0x7FFFFFFF 

Tuning HFSZLIM 0x7FFFFFFF 

Tuning SFNOLIM 512 

Tuning NCALL 400 

Tuning SSTKLIM 0x7FFFFFFF 

Tuning HSTKLIM 0x7FFFFFFF 

Tuning MSGSSZ 524288 

Tuning MSGMNB 65536 

Adding ClearPath default to /etc/hosts 

Adding "fddi22am" to /etc/hosts.equiv 

UX:idbuild: INFO: 

The unix kernel will be rebuilt now. 

This will take some time. Please wait. 

UX:idbuild: INFO: The unix kernel has been rebuilt. 

**************************************************** 

The system must be rebooted to load the new kernel. 

After the system has been rebooted, make some 

Emergency Repair Diskettes: 

/sbin/emergency_disk diskette1 

**************************************************** 

Finished running the ClearPath tuning script. 

Press return to shutdown and reboot. 

8. Press Enter to reboot the system. Reboot takes about 7 minutes. 

Continue by retrieving and applying fixes (8.9). 


8.9. Retrieving and Applying Fixes 


For information and the latest upgrades and fixes, see the Unisys Web page and follow the 

instructions at 

http://www.support.unisys.com 

After applying any fixes, continue with the steps in 8.10. 

8.10. Configuring Internet FastStart 

To configure Internet FastStart, do the following: 


2. From the graphical interface: 

a. In the task bar, click the second arrow from the right, above the fifth icon from the 


b. Click the SCO Admin icon. 

3. Double-click Netscape Server Admin. 

Informational messages appear about Netscape Server Admin start-up. 

4. Click OK. 

The Netscape logon screen appears. 

5. Enter admin as the user-id. 

6. Enter unisysas as the password. 

Note: If the password has been changed, enter the new root user (superuser) 

password instead. 

7. Click OK. 

8. Click Install a New Netscape FastTrack Server. 

9. Click OK. 

A security warning message appears. 

10. Click Continue Submission. 

11. Click Start your new server. 

A message appears to inform you that the server has started up. 

12. Click OK. 

13. Click File. 


Continue by creating emergency recovery diskettes (8.12). 



8.11. Logging On to UnixWare 

Caution 

To prevent unauthorized access to the UnixWare node following initial installation, 

the site must change the default password to a different password. 

Note: Switch the monitor concentrator to the Intel Node position before beginning (see 

2.5.2). 

Several installation and configuration procedures require you to log on as the root user 

(user-id root). Root logon also provides superuser privileges. 

8.11.1. Logging On As the Root User (Superuser) 

When UnixWare displays the graphical user interface (GUI) logon screen, log on as 

follows: 

1. In the Login ID field, enter root. 

2. In the Password field, enter unisysas. 

3. Click Login or press Enter. 

The UnixWare graphical desktop appears following this logon. 

8.11.2. Switching Windows 

You can switch between graphical mode and console(character ) mode, and switch among 

all configured windows, by using either of these control key combinations: 

Alt-PrintScreen-N Next window 

Alt-PrintScreen-P Previous window 

8.12. Creating and Using UnixWare Emergency 

Recovery Diskettes 

Caution 

You must create emergency recovery diskettes to use to boot the UnixWare node 

in the event that the console output redirection procedure described in Section 12 

is not successful. As described in Section 10, you also need to create emergency 

recovery diskettes for use with a SPO server running UnixWare. 



Console output from the UnixWare node is redirected to the SPO workstation during 

installation and configuration of that workstation as described in Section 12. Before 

redirecting console output, you must ensure that you have emergency recovery diskettes to 

use if the procedure should fail. The following subsections describe how to create (8.13.1) 

and use (8.13.2) UnixWare emergency recovery diskettes. 

Notes: 

• Sites should create emergency recovery diskettes periodically to ensure that device 

drivers are up to date. 

• See the SCO UnixWare documentation for more information on UnixWare recovery 

procedures. 

8.12.1. Creating the Emergency Recovery Diskettes 

Take the following steps to create emergency recovery diskettes for each UnixWare server 

node, and for the SPO server if it is running UnixWare: 

1. If you are not already logged on, log on as the root user (user-id root) (superuser) 

(8.12.1). 

2. Enter the following command: 

# emergency_disk diskette1 

You are prompted to insert a diskette. 

Please insert a floppy and press 

3. Insert a diskette into the disk drive and press Enter. 


This will take some time. Please wait . . . 

After about 4 minutes, the following message appears: 

Remove the floppy from the floppy drive. 

Insert the second floppy and Press 

4. Remove the first diskette, then insert the second diskette into the disk drive and press 

Enter. 



After a few minutes, the following message appears: 

Creation of the Emergency Recovery boot floppy was successful. 

Label the diskettes as follows and set them aside for later use if needed: 

• For a UnixWare node—“UnixWare Emergency Recovery Disk 1 of 2” and “UnixWare 

Emergency Recovery Disk 2 of 2” 

• For the SPO server—“SPO Server Emergency Recovery Disk 1 of 2” and “SPO Server 


See 8.13.2 for procedures for using the diskettes. 

8.12.2. Booting from the Emergency Recovery Diskettes 

If a UnixWare node or the SPO server does not successfully reboot for any reason, you can 

boot from the emergency recovery diskettes as follows: 

1. Insert the applicable UnixWare node or SPO server diskette labeled “Emergency 

Recovery Disk 1 of 2” into the drive unit. 

2. Turn power on if it is currently off, or briefly turn power off and then back on. 

After 2 minutes, the SCO screen appears, then after another minute, an Emergency 

Recovery screen appears followed by a message to insert the second emergency 

recovery disk: 

UnixWare 2 - Emergency Recovery 

Insert the second emergency recovery 

floppy and press ENTER. 

3. Insert the applicable UnixWare node or SPO server diskette labeled “Emergency 

Recovery Disk 2 of 2” into the drive unit, then press Enter. 

After a brief wait, the following message appears: 

The hard disk is sane. 

Press ENTER to continue. 


An Emergency Recovery Menu appears as follows: 

---Emergency Recovery Menu--- 

Mount File Systems 

Unmount File Systems 

Access UnixWare Shell 

Restore Disk(s) 

Reboot 

5. The actions you now take depend on whether you are rebooting a SPO server or a 

UnixWare node as follows: 

• For the SPO server—Use the up and down arrow keys to select the desired 

recovery action as determined by procedures set up at the site. 



• Use the up and down arrow keys to select Mount File Systems, then press Enter. 

This mounts the UnixWare operating system file systems under the /mnt directory. 

6. Use the up and down arrow keys to select Access UnixWare Shell. 

The UnixWare shell prompt appears. 

# 

7. Enter the following commands to access the boot file for editing (you can use a 

different editor from vi, which is used in this example). 

# cd /mnt/stand 

# vi boot 

8. Edit the boot file as follows: 

a. Find the line in the file that begins with the word Console. 

b. Insert a pound sign (#) character in front of that word (this makes the line a 

comment). 

c. Save the file and exit from the editor. 

d. Exit from the UnixWare shell by entering the following command: 

# exit 

The Emergency Recovery Menu reappears. 

9. Select Unmount File Systems from the menu. 

This removes the operating system files from the /mnt directory. 

10. Remove the diskette from the drive unit, then select Reboot from the menu. 

After about 5 minutes, the UnixWare desktop reappears. 

If you need to redirect console output again (Section 12), take the following steps: 

1. At the desktop, double-click Applications, then Terminal. 


$ 

2. Use an editor to access the boot file again as in the following example: 

$ vi /stand/boot 

3. Find the Console line and remove the pound sign (#) character. The line now begins 

with the word Console. 

4. Save the file and exit from the editor. 

5. Enter the following command to return to the UnixWare desktop: 

# exit 

6. Double-click the Shutdown icon. 


Shutdown system are you sure? 

7. Click SHUTDOWN. 




This will end your desktop session. Remove all media then Click Exit. 


The UnixWare node reboots (takes about 3 minutes). When done rebooting, UnixWare 

displays the graphical user interface (GUI) logon screen. 

9. Log on as the administrator. 

After the reboot, proceed to Section 12 to redirect console output again. 


Section 9 

Installing the ClearPath IX Customer 

Web Site 

Support for the ClearPath IX Customer Web Site has been discontinued. 


Installing the ClearPath IX Customer Web Site 


Section 10 

Installing SPO Basic Edition and 

Related Software 

This section tells how to install SPO Basic Edition and related software on the SPO server. 

If SPO Basic Edition and related software are not preinstalled, the required procedures 

take about 4 hours. If the software is preinstalled, the remaining procedures take about 1 

hour. 

The information in this section applies to the following configuration: 


ES2024R UnixWare 7.1.1 operating system 

SPO Basic Edition, Level 6.1 CP 

SMS4030-SPO (for consolidated 

configuration) 

SMS4031-SPO (for legacy 

configuration) 

Table 10–1 lists media and information needed for the various installation scenarios: 

• Installation with preinstalled software 

• Full installation 

• Steps you need to take in either instance 



Installing SPO Basic Edition and Related Software 

Table 10–1. SPO Basic Edition and Related Software Installation Checklist 


10.4. Installing the Operating System and SPO Basic Edition Software 

Media needed: 

• Boot diskettes—labeled “SCO UnixWare 7 Installation Diskette for Release 7.1.1 (1 of 2)” and 

“SCO UnixWare 7 Installation Diskette for Release 7.1.1 (2 of 2)” 

• UnixWare operating system CD-ROMs—labeled “UnixWare 7.1.1 Installation CD-ROM Disk 1 of 3,” 

UnixWare 7.1.1 Updates CD-ROM Disk 2 of 3,” and “UnixWare 7.1.1 Optional Services CD-ROM 

Disk 3 of 3” 

• Diskette labeled “UnixWare 7.1.1 Operating System PSK UNX71-PSK for UW 7.1.1 Host Bus 

Adapter Diskette Level R3” 

Keyboard type (language) to use ________________________ 


Serial number: ________________________________________________ 

Activation key: ________________________________________________ 

Enter this information exactly as found on the SCO UnixWare 7.1.1 Business Edition Certificate of 

License and Authenticity provided with the installation media inside the SCO UnixWare package. 

Time zone at the site ________________________ 

Language Supplement Installation screen 

Select the country (language) to use __________________________ 

10.5. Installing the UnixWare Platform Support Kit (PSK) 

Media needed: CD-ROM labeled “Unisys UnixWare 7 UNX71-PSK for UW 7.1.1 PSK Release 3 CD- 

ROM (PSM/Drivers/Updates/PTFs)” 

Number of 2200 node system consoles (between 1 and 12) ___________ 

Enter the number of 2200 node system consoles. 

10.9. Creating UnixWare Emergency Recovery Diskettes 

Media needed: Two blank diskettes for creating UnixWare emergency recovery diskettes 

10.10. Installing the Multiport Card Driver 

Media needed: Diskette containing multiport card driver software—labeled “Asynchronous Multiport 

Driver UW6000-ACD” 

10.11. Installing SPO Basic Edition Software 

Media needed: SPO Basic Edition software CD-ROM—Labeled “SPO/HMP Console for UnixWare 

Software Level 6.1CP” 

continued 



Table 10–1. SPO Basic Edition and Related Software Installation Checklist 


10.12. Creating a 2200 Console Hosts File Diskette 

Media needed: Blank, formatted MS-DOS diskette (3-1/4-inch)—Diskette on which to save the hosts 

files for copying to the system consoles 

10.13. Copying the Hosts File (Done at 2200 System Consoles) 

Media needed: Diskette created in 10.12 that contains the hosts files for copying to the system 

consoles 

10.1. Overview of Installing the Operating System 

and SPO Basic Edition Software 

The operating system may be preinstalled, or you may need to install it yourself. This 

section covers both cases. Proceed as follows: 

1. Determine whether the software is preinstalled on the SPO server (10.2). If it is not 

preinstalled, skip to 10.4. 

2. If the software is preinstalled, follow the procedures in the next subsection (10.3). 

Then skip to 10.12. 

3. Install the operating system on the SPO server (10.4). 

4. Log on as the superuser (10.15.3). 

5. Install the UnixWare Platform Support Kit (PSK) (10.5). 

6. Retrieve and apply fixes (10.6). 

7. Set up the documentation search engine (10.7). 

8. Configure the SPO server (10.8). 

9. Create an emergency recovery diskette (10.9). 

10. Install the multiport card driver (10.10). 

11. Install SPO Basic Edition software on the server (10.11). 

12. Create a 2200 console hosts file diskette (10.12). 

13. Copy the hosts file to the system consoles (10.13). 

14. Remotely install Autoaction Message System (AMS) databases on 2200 node system 

consoles (10.14). 



10.2. Determining Whether Software Is Preinstalled 

Caution 

To prevent installation problems, or wasted time, determine whether or not 

UnixWare has been preinstalled. Then follow either the procedure for preinstalled 


Updated information may be available in the Web version of this document: 


To determine if UnixWare is preinstalled, power on the system. If UnixWare is 

preinstalled, the system boots. Otherwise, the system displays the following error 

message: 

Missing operating system 

Cannot boot UnixWare. 

If UnixWare is preinstalled, perform the steps in 10.3. 

If UnixWare is not preinstalled, perform the steps from 10.4 through 10.14. 

Note: When booting the SPO server for the first time or two, you may see an error 

message saying, “Could not modify qmon1a about modified data, try running 

SACADM -x -pqmon1a.” A message similar to this usually appears. It concerns 

the initialization of the multiport asynch card and can be ignored. 

10.3. Steps to Take If Software Is Preinstalled 

Note: Perform this procedure only if the UnixWare operating system has been 

installed at the factory (you have not installed the operating system). 

If the UnixWare operating system is preinstalled, you must do the following steps: 

10.3.1. Entering the License 

Follow these steps to enter the license information. 

1. At the console screen, log on as the root user (user-id root) in graphical mode 

(10.15.2). 

loginid: root 

pswd: unisysas 

2. In the terminal window, enter scoadmin. A System Administration window appears. 

3. Double-click License Manager. 

4. Click License. 



5. Click Add. 

6. Enter License Info and click the License button. 

7. Click OK. 

8. When you have finished entering licenses, click Host, then click Exit. 

10.3.2. Changing the Host Name 

Follow these steps to change the host name, if needed. 

1. Open the console terminal window by clicking the dtterm icon in the upper left-hand 

corner. 

2. Type setuname -n newsystemname and press Enter. 

3. Type uname -a to verify the new system name. 

10.3.3. Modifying the Hosts File 

If the operating system was preinstalled, a hosts file with default names and addresses is 

on the SPO server. To add, change, or remove names and addresses, follow the steps 

below. 

Note: If you changed the name of the SPO server, you must add an entry for the new 

name and address, even if you did not change the address. 

1. Log on to the system as root from the graphical logon screen (10.15.2). 

2. If the terminal window appears as an icon, double-click the icon to restore it. 

3. At the prompt (#), enter the following command: 

scoadmin 

A system administration window appears. 

4. Scroll down until you see the Networking folder. 

5. Double-click the Networking folder to expand it. 

6. Double-click the Client Manager. 

A Network Client Manager window appears. 

7. Double-Click the /etc/hosts file entry in the Configured Network Client Services box. 

An /etc/hosts Configuration window appears. 

8. To add an entry for the SPO server, a 2200 system console, a SPO workstation, or a 

monitored Intel node, do the following: 

a. Click the Add button. 

A window labeled Add new entry appears. 

b. Enter the IP address and host name as identified in Table 2–2. The Comment field 

is optional. 

c. Click OK. 



The entry appears in the /etc/hosts Configuration. 

Repeat steps 8(a) through 8(c) for each additional console, workstation, and Intel 

node. 

9. To modify an entry, do the following: 

a. Click the entry to highlight it, then click the Modify button. 

A Modify Entry window appears. 

b. Change the fields as needed. 

c. Click OK. 

Repeat steps a through c as needed. 

10. To delete an entry, do the following: 

a. Click the entry to highlight it. 

b. Click the Delete button. 

11. Click OK to close the /etc/hosts Configuration window. 

12. Click the Host menu and select Exit from the pull-down menu to close the Network 

Client Manager window. 

13. Click the file menu and select Exit from the pull-down menu to close the System 

Administration window. 

14. If you changed the node name of the SPO server, enter the following commands to 

rebuild the kernel and reboot the system: 

/etc/conf/bin/idbuild 

init 6 


10.3.4. Changing the Date and Time Zone 

Follow these steps to change the date and time zone. 

1. If you are not already logged on, log on in graphical mode (10.15.2). 

2. Open the SCO Admin window. 

3. Scroll to the System folder and double-click. 

4. Double-click System Time Manager. 


6. Click Change Time Zone. 

7. Select the appropriate country and time zone and click OK. 

8. After reading the time zone change message, click OK. 


10. Click Set Time. 

11. Enter the correct time and date. Click OK. 



12. Click OK when the message appears saying the system time will change. 

13. In the upper left-hand side of the window, click Host. 


15. In the SCO Admin window, click File and then Exit. 

Continue by following the procedure in 10.12 to create a 2200-console hosts-file diskette. 

10.4. Installing UnixWare 7.1.1 on the SPO Server 

If you are required to install the UnixWare operating system, enter the information shown 

in Table 10–2 in response to disk slicing prompting messages. 

Table 10–2. Boot Disk (Disk 0) Required Configuration 

Values 

File System Description Type Size 

/ Root File System vxfs Remaining 

space 

/dev/swap Swap Slice slice 

/stand Boot File System bfs 

/usr usr File System off 

/home User File System vxfs 

/dev/dump Dump Slice off 

/var Add-ons File System off 

/home2 Second User File 

System 

/tmp Temporary File 

System 

vxfs 2048 MB 

memfs 100MB 

/dev/volprivate Private Volume slice 1 

/var/tmp Temporary File 

System 

ALTS TABLE Alt/Sector Slice slice 

memfs 50 MB 



Cautions 

• The following procedure is a destructive installation procedure. Make sure 

you have read and understand the procedure before proceeding. 

• During the procedure, be sure the Caps Lock key on the keyboard does not 

become locked in the uppercase position while making entries. Use the Shift 

key if you want to enter an uppercase password. 

To install UnixWare, take the steps below. 

Notes: 

• Switch the monitor concentrator to the SPO Server position before beginning (see 

2.5.1). 

• Ignore any error messages for invalid disk header that may appear before the 

prompt to insert installation media. 

1. With the power off, insert the boot diskette #1 (labeled “UnixWare 7 Installation 

Diskette for Release 7.1.1 (1 of 2)”) into the primary (boot) diskette drive unit. 

2. Turn the power on. 

After hardware information is displayed, you see a “starting UnixWare” message and 

the SCO logo. It may take several minutes to load the system from the installation 

diskette. You are asked to select a language for the installation. 

3. Select a language and press Enter. You receive a prompt to insert the second 

installation diskette. 

4. When you receive the prompt, insert the boot diskette #2 (labeled “UnixWare 7 

Installation Diskette for Release 7.1.1 (2 of 2)”) into the diskette drive and press Enter. 

After a brief delay, the Welcome window appears. 

5. Press F10 to continue. 

You are prompted to select the zone, locale, and keyboard type. 

6. Select the zone, locale, and keyboard appropriate for the site, and press F10 to apply 

your selections. 

The following are default selections for a U. S. installation: 

Zone America (Latin - 1) 

Locale C (English) 

Keyboard United States 

You are prompted for licensing information. 


preprinted on the installation package, and press F10 to apply. 

Note: All licensing information is case-sensitive. 

You are prompted with the option to load hardware configuration information from 

the HBA diskette. 



8. Remove the boot diskette from the drive. 


PSK/UNX71-PSK Host Bus Adapter (HBA)”) into the drive. 


After the diskette is loaded, you are prompted to install additional HBA diskettes. 

11. Remove the HBA diskette from the drive. 

12. Select Proceed with Installation and press F10. 

The Device Configuration Utility (DCU) window appears. 

13. Select Do Not Enter the DCU (auto-configure drivers). 



Please wait while the system hardware drivers are loaded 

You are prompted for the node name of the system. 

15. Obtain the node name of the system from the customer. Enter the node name and 

press F10. 

Note: Do not enter a fully qualified node name that includes the domain. You can 

enter the domain name later during network configuration. 

The Select Installation Method menu appears. 

16. Insert the Business Edition CD-ROM 1 of 3 into the drive. 

17. Select Install from CD-ROM and press F10. 


Please wait while the installation media (cdrom) is verified 

Then the following menu appears: 

Disk Configuration 

Disk No. Character Node Action 

======== ========= ==== ====== 

1 /dev/rdsk/c0b0t0d0s0 Use whole disk for Unix 

18. Select Use whole disk for Unix. This uses the whole disk for UnixWare 7 and removes 

all data on existing partitions. 



Choose one 

(*) Use default filesystem sizes and types 

( ) Customize filesystem and slices 

20. Select Customize file system and slices and press Enter. 

The screen values to change are shown below. 



Notes: 

• To change the type to vxfs, as instructed above, press F2, tab to vxfs, and press 

Enter. 

• For Root File System (/), above, adjust Size for root so that Allocated (MB) is not 

greater than Available (MB). 

Change the values as follows: 



• User File System (/home)— Accept the default; do not change the size. 


• Var File System (/var)— Accept the default; do not change the size. 

• Temporary File System (/tmp)—Leave the type as memfs; change the size to 100. 

• Temporary File System (/var/tmp)—Leave the type as memfs; change the size to 

50. 

• Root File System (/)—Change Size to the size of the remaining space. Keep the file 

system type default (vxfs). 




Choose one 

(*) Use default disk options 

( ) Customize disk options 

22. Select Use default disk options and press F10. 

The Choose System Profile menu appears. 

23. Customize your configuration as follows: 

a. Select Customize Installation of Packages and press F10. 

b. Select Core System Services and press F10. 

c. Select Extended OS Utilities and press F2. 

d. Select Select all packages (FULL) and press Enter. 

e. Verify that State of Extended OS Utilities Service is set to Full. 

f. Press F10. 

g. Select Accept current selection and continue, then press F10. 

The Choose Platform Support Module menu appears. 

24. Select a platform support module: 

a. Press PageDown. 

b. Tab to Install No PSM at This Time. 

c. Press Enter. 



The system now attempts to detect a network adapter. 

25. From the Choices box, choose AMD PCnet family mdi driver, then press F10. 

The Select Network Adapter menu appears. 

26. Select Use the detected adapter shown above, then press F10. 

The Configure TCP/IP Networking window appears. 

27. Enter the IP address from Table 2–2, the press Enter. The system netmask and 

broadcast address are filled in automatically. 


The Configure IPX Networking Protocol window appears. 

29. Press F8 to defer. 

The NIS Configuration window appears. 

30. Press F8 to defer. 

You are prompted for the time, date, and time zone. 

31. Enter the correct time, date, and time zone for the locale. (For time zone selection, 

press F2.) 


You are prompted for the security level. 

33. Select Traditional and press F10. 

An Owner’s Account screen appears with the following fields: 

System owner name: 

System owner login name: 

System owner user ID number: 101 

System owner password: 

Repeat Password: 

34. Enter the following: 

• For system owner name: UnixWare 7 Administrator 

• For system owner login name: unisys 

• For system owner user ID number: 101 (accept the default) 

• For system owner password: unisysas 

• For repeat password: unisysas 

Note: Passwords do not appear on the screen as they are typed. The site must 

later change all passwords during site customization. 


A Root Account Password screen appears. 

36. Enter unisysas as the password. This is the default installation password. 

Note: You can enter a site-defined password, if this is preferred. 

37. Tab to the next line and reenter the password, then press F10. 



Note: Do not forget the root account password. If you forget this password, you 

must completely reinstall the system to set up a new one. 

38. View the license terms, select Accept, and press F10 when you are finished. 


If you are ready to install the system, press F10. 

Note: If you need to change any information in the installation, you can step back 

through the installation by pressing F9. 

39. Continue the installation by pressing F10. 

The software load begins. This process typically takes less than 40 minutes. The 

software load can continue unattended. 

During the software load, you can track the progress of the installation by viewing 

progress indicators that are displayed for each package loaded. 

You are prompted to insert the HBA diskette when the software load is completed. 


PSK/UNX7-PSK Host Bus Adapter (HBA)”) into the drive and press Enter. 

The kernel (/stand/unix) is rebuilt. This process takes several minutes. A message is 

displayed when the kernel is successfully rebuilt. 

41. Remove all diskettes, tapes, and CD-ROMs. 

42. Press any key to reboot the UnixWare 7 system. 

After the system reboots, a Mouse Selection screen appears. 

43. Configure the mouse as follows: 

a. Tab to select the PS/2-compatible mouse, then press F10. 

b. The default number of buttons is two. Press F10. 

c. Press Enter to start the mouse test. 

d. Move the mouse. 

e. Press a mouse button to end the test. 

When you are finished testing the mouse, the following message appears: 

To continue installing the system, insert CD-ROM #2 and press . 

44. Insert the CD-ROM and press F10. 

45. When the window “Select products to install” appears, press Enter. This process 

typically takes less than 30 minutes. 

46. When the window “The following products were successfully installed:” appears, press 

F10. 

47. Another message appears asking for CD-ROM #3. Press F8. 

The system automatically boots into multi-user mode. 

Installation of the UnixWare 7 operating system is now complete. 

Continue by installing the PSK updates (10.5). 



10.5. Installing the UnixWare Platform Support Kit 

(PSK) 

To install the UnixWare 7.1.1 PSK Release 3 CD-ROM(Unisys), do the following: 

1. Log on as the root user (user-id root) in character mode (10.15.3). 

2. Insert the UW 7.1.1 PSK Release 3 CD-ROM into the CD-ROM drive. 

3. From the command line at the root directory, enter the following pkgadd command 

and press Enter: 

pkgadd -d cdrom1 erf oempsm 

A prompt to insert the CD-ROM appears. 

Insert CD into CD-ROM Drive 1. 


or [q] to quite: (default: go) 

The erf and oempsm packages are installed. 

4. When the erf and oempsm installation completes, you must install the required 

program temporary fixes (PTF) from the PSK CD-ROM. Proceed as follows: 

a. With the CD-ROM still in the drive, enter 

mount -F cdfs -r /dev/cdrom/cdrom1 /mnt 

/mnt/ptfs/go 

A list of required PTFs is displayed. 

b. Select ALL by pressing ENTER. 

The PTFs are installed. 

c. When the installation completes, remove the CD-ROM from the drive. 

d. Enter the following to reboot the system: 

init 6 

5. After the system restarts, log on as the root user (user-id root) in character mode 

(10.15.3). 

Continue by applying any additional fixes(10.6). 

10.6. Retrieving and Applying Additional Fixes 

For information and the latest upgrades and fixes, see the Unisys Web page at 

http://www.support.unisys.com/useries/html/ux/UWProducts.html 

After applying any fixes, continue by setting up the search engine (10.7). 



10.7. Setting Up the Documentation Search Engine 

To set up the documentation search engine, follow these steps: 

1. Run the following command as the root user (user-id root) in the console window: 

/usr/man/bin/config_search -f 

This takes 6 to 7 minutes. 

2. Reboot. 

Continue by configuring the SPO server (10.8). 

10.8. Configuring the SPO Server 

To configure the SPO server, take the following steps: 

1. Log on to the system as root from the graphical logon screen (10.15.2). 

2. If the terminal window appears as an icon, double-click the icon to restore it. 

3. At the prompt (#), enter the following command: 

scoadmin 

A system administration window appears. 

4. Scroll down until you see the Networking folder. 

5. Double-click the Networking folder to expand it. 

6. Double-click the Client Manager. 

A Network Client Manager window appears. 

7. Double-click the /etc/hosts file entry in the Configured Network Client Services box. 

An /etc/hosts Configuration window appears. 

8. Add entries for each 2200 system console, SPO workstation, and monitored Intel node 

as follows: 

a. Click the Add button. 

A window labeled Add new entry appears. 

b. Enter the IP address and host name as identified in Table 2–2. The Comment field 

is optional. 

c. Click OK. 

The entry appears in the /etc/hosts Configuration. 

Repeat steps 8(a) through 8(c) for each additional console, workstation, and Intel 

node. 

Note: You can modify or delete any of the entries (with the exception of Localhost 

and the host name) by clicking on the entry to highlight it and clicking the 

Modify button. 

9. Click OK to close the /etc/hosts Configuration window. 



10. Click the Host menu and select Exit from the pull-down menu to close the Network 

Client Manager window. 

11. Click the file menu and select Exit from the pull-down menu to close the System 

Administration window. 

12. Return to the Terminal window and tune the system kernel by entering the commands 

below at the root prompt (#). Answer Y to any questions asking if it is OK to change 

the parameter. 

cd /etc/conf/bin 

./idtune -m SFSZLIM 0x7FFFFFFF 

./idtune -m HFSZLIM 0x7FFFFFFF 

./idtune -m SDATLIM 0x7FFFFFFF 

./idtune -m HDATLIM 0x7FFFFFFF 

./idtune -m SVMMLIM 0x7FFFFFFF 

./idtune -m HVMMLIM 0x7FFFFFFF 

./idtune -m SSTKLIM 0x7FFFFFFF 

./idtune -m HSTKLIM 0x7FFFFFFF 

./idtune -m MAXUP 1000 

./idtune -m NPROC 1000 

./idtune -m SFNOLIM 2048 

./idtune -m HFNOLIM 2048 

./idtune -m NCALL 400 

./idtune -m SEMMNI 1000 

./idbuild 

cd / 

13. Remap the /home2 file system to /var/opt/SPO_Log as follows: 

a. Enter the following to unmount the /home2 file system: 

umount /home2 

b. Enter the following to create the /var/opt/SPO_Log mount point: 

mkdir -p /var/opt/SPO_Log 

c. Use the text editor to change the entry in /etc/vtstab as follows: 

dtpad /etc/vfstab 

d. Locate the line containing /home2 (this should be the third line) and change 

/home2 to /var/opt/SPO_Log. 

e. Click the file menu and select Save. 

f. Click the file menu and select Close. 

g. Enter the following to mount the /var/opt/SPO_Log file system: 

mount /var/opt/SPO_Log 

h. Enter the following to reboot the system: 

init 6 

The kernel rebuilds, and the system reboots. 

Continue by creating emergency recovery diskettes, as described in 10.9. 



10.9. Creating UnixWare Emergency Recovery 

Diskettes 

This subsection describes how to create UnixWare emergency recovery diskettes. 

Notes: 

• Sites should create emergency recovery diskettes periodically to ensure that device 

drivers are up to date. 

• See the SCO UnixWare documentation for more information on UnixWare recovery 

procedures. 

Take the following steps to create emergency recovery diskettes for the SPO server: 

1. If you are not already logged on, log on as the root user (user-id root) in character 

mode (10.15.3). 


/sbin/emergency_disk diskette1 

You are prompted to insert a diskette. 

Please insert a floppy and press 

3. Insert a diskette into the disk drive and press Enter. 


This will take some time. Please wait . . . 

After about 2 minutes, the following message appears: 

Please enter the medium to use for emergency_rec (e.g. ctape1)? 

4. Enter diskette1. 

After another 2 minutes, the following message appears: 

Insert the SECOND boot floppy into diskette drive and press 

5. Remove the first diskette, then insert the second diskette into the disk drive and press 

Enter. 

After a few minutes, the following message appears: 

Creation of the Emergency Recovery boot floppy was successful. 

Label the diskettes as follows and set them aside for later use if needed: 

• For a UnixWare node—“UnixWare Emergency Recovery Disk 1 of 2” and “UnixWare 


• For the SPO server—“SPO Server Emergency Recovery Disk 1 of 2” and “SPO Server 


Continue by installing the multiport card driver, as described in 10.10. 



10.10. Installing the Multiport Card Driver 

With UnixWare installed on an Intel node, the node is directly connected to a serial port in 

a multiport I/O board in the SPO server as shown in Figure 10–1. Alternatively, it could be 

connected to an existing SPO Console server. 

Intel 

Nodes 

(upto4) 

Connections to an Existing SPO Server (Typical) 

Serial 

Connection 

(via NAS) 

Serial 

Connection 

(via NAS and 

Other Device) 

Signal 

Splitter 

(Optional; 

Site- 

Provided) 

Serial 

Console 

Direct Serial Connection (Default) 

Network 

Access 

Server 

(NAS) 

Network 

Access 

Server 


LAN 

LAN 

SPO Server 

EISA 

Multiport 

Card 

Existing SPO 

Server at Site 

(e.g., U6000) 

Existing SPO 

Server at Site 

(e.g., U6000) 

Figure 10–1. Possible Intel Node Connections (with UnixWare) to the SPO Server 

To install the driver software for the multiport card, take the following steps: 

Note: Switch the monitor concentrator to the SPO server position. 

1. If you are not already logged on, log on as the root user (user-id root) in character 

mode (10.15.3). 

2. Insert the diskette containing the PCI driver software (labeled “Asynchronous 

Multiport Driver UW6000-ACD”) into the drive unit.



pkgadd -d diskette1 eqn 

A prompt to insert the diskette appears: 

Insert diskette into Floppy Drive 1. 


or [q] to quit: (default: go) 


Several messages appear indicating progress of the installation. After a few minutes, a 

prompt asks whether this is an ISA system: 

This seems to be an ISA system. Is this correct [Y/n]? 

6. Type Y, then press Enter. 

A message asks whether you want the driver to autoconfigure all ISA boards: 

Should the driver autoconfigure all Equinox ISA boards [Y/n]? 


After a few seconds, a message appears stating that you can enable high baud rates. 

You may enable selection of baud rates above 38400 for all ports by 

answering "Yes" to the following question. 

If you enable baud rates above 38400, speeds below 300 baud will be 

unavailable. Speeds 300 to 38400 are unaffected. 

The high baud rates are selected according to the following table: 

57600 B50 

76800 B75 

115200 B110 

230400 B134 (depending on board/module type) 

Enable high baud rate selection [y/N]? y 


A message asks for further instructions: 

Should the default set of port monitors/services be installed [Y/n]? 


A message asks for the baud rate: 

Enter the port service baud rate [9600]: 

10. Press Enter to accept the default (9600). 

The installation completes. 

11. Remove the diskette from the drive unit. 

Installation of the multiport card driver is now complete. Proceed with installation of the 

SPO Basic Edition software (10.11). 



10.11. Installing SPO Basic Edition Software 

To install SPO Basic Edition software and related online documentation, take the following 

steps at the SPO server: 

1. Log on as the root user (user-id root) in character mode (10.15.3).The pound sign (#) 

prompt appears indicating that you are the root user. 

2. Put the SPO Basic Edition CD-ROM (labeled “SPO/HMP Console for UnixWare 

Software level 6.1CP”) in the drive unit of the SPO server. 


pkgadd -d cdrom1 spo-cp.61 

A prompt to insert the CD-ROM appears: 

Insert CD into SCSI CD-Rom Drive 1. 


or [q] to quite: (default:go) 


The installation script now prompts you for the following information to which you 

can respond by pressing the Enter key to accept the default: 

• The directory where you want to install SPO software (default is /opt/SPO). 

• The directory where you want to store your SPO log files (default 

is/var/opt/SPO_Log). 

• The directory where you want to store your site-dependent data (default is 

/var/opt/spo). 

In addition, the script automatically configures the following information: 

• The Single Point Operations administrator logon name (spadmin). 

• The group name for the installation files (spo). 

• The operator name for users of SPO Basic Edition (spoper). 

After configuring this information, the installation script displays your entries and asks 

you to confirm them. 

5. Press Enter to confirm your selections. 

You are prompted for an administrator password. 

Note: The prompts for administrator and operator passwords appear only on 

initial installation when the spadmin and spoper user-ids are added to the 

system. 

6. Type unisys12 and press Enter. 

You are prompted for an operator password. 

7. Type unisys12 and press Enter. 

The script now installs the software according to the information provided and 

displays a message when done. 

8. Remove the CD from the CD-ROM drive. 



9. Enter the following command to reboot: 

init 6 

Continue by creating a hosts file diskette (10.12). 

10.12. Creating a 2200 Console Hosts File Diskette 

Follow these steps to create a diskette containing the hosts file for the 2200 console: 

1. If you are not already logged on at the SPO server, log on as superuser in character 

mode (10.15.3). 

2. Insert a blank diskette into the drive. 

3. Enter the following command to change the default directory to /etc/inet: 

cd /etc/inet 

4. Enter the following command to copy the hosts file to the diskette: 

tar cv ./hosts 

5. Remove the diskette from the drive. 

Continue the installation by copying the hosts file from diskette to the system consoles 

(10.13). 

10.13. Copying the Hosts File to 2200 System 

Consoles 

Before using SPO Basic Edition software, you must copy the hosts file you saved to 

diskette (10.12) to each 2200 system console. The hosts file provides the system consoles 

with the network addresses (IP addresses) of the SPO server and other hosts on the 

network. The hosts file does not provide the IP address of the router to which the console 

LAN might be connected. 

You load the hosts file to each system console from diskette using the Single Point 

Interface Utility accessed through the 2200 Series system console Utilities session 

(Optional Features option) (see Figure 10–2). The consoles can be done in any order, but 

you must repeat the procedure on every system console. 



Figure 10–2. System Console F3 Utilities Session Menu 

Take the following steps. 

Note: Switch the monitor concentrator to the first system console position (see 2.5.2). 

1. On the system console, press F3 to activate the Utilities menu (Figure 10–2). 

2. Select Optional Features and press Enter. 

A list of utilities appears, similar to the list in the right-hand panel of Figure 10–2. 

3. Select SP Interface Utility and press Enter. An Execute box appears. 

4. Press Enter. The Single Point Interface Utility Session window appears (Figure 10–3). 

5. Press Esc to get the menu bar and use the arrow keys to select the Hosts File menu bar 

item. A list of options appears as follows: 

Load 

Save 

Edit 

6. Press Enter to select the Load option. A form appears for selecting the media (see 

Figure 10–4). 

? Exit Hosts File Routers Subnetwork Changes 

Session x - SP Interface Utility 

Console [console] [network] Host host device SP Interface [status] 

SP Operations Role Status Previous Status 

network - name master connection - status Previous - connection - status 



Figure 10–3. Single Point Interface Utility Session Window 



? Exit Hosts File Routers Subnetwork Changes 

Console co 

SP Operations I 

System 

Load 

Save 

Edit 

Diskette type: UNIX 

Host Name: cp_cons01 

Use hosts file subnetwork information if available?: No 

Use hosts file router information if available?: Yes 

Figure 10–4. Specify Load Diskette Menu 

7. Press Enter again to position the cursor in the diskette type field. Press an arrow key 

to activate the following drop down list: 

DOS-HD 

DOS-DD 

UNIX 

8. Select the UNIX option and press Enter. 

9. Tab to the Host Name field and enter the name of the system console you are loading. 

This name identifies the system console on the TCP/IP network (for example, so the 

SPO server can communicate with it). 

Note: The name specified can be different from the system console name used on 

the SCF token ring LAN. 

10. Tab to the other fields on the form and make entries as follows: 

• Select No in the "Use hosts file subnetwork information if available?" field, unless 

you are using subnet masking, in which case you should select Yes. 

• Select Yes in the "Use hosts file router information if available?" field, unless for 

some reason you do not wish to use the router, in which case you should enter No. 

11. Press Enter. When the Execute box appears, press Enter again. You are prompted to 

insert the diskette. 

Insert the diskette 

Note: Be sure to insert the diskette in the system console diskette drive unit. 

12. In the system console diskette drive unit, insert the hosts file diskette created when 

you ran the tuning script. Press Enter. A window appears indicating that the system is 

working and that you should wait. The following message appears: 

Added old router information to the new hosts file. 

New hosts file loaded. Press Enter to continue. 

13. Press Enter to continue. If the SPO server and system consoles are not all on the same 

LAN, you need to add router information to the hosts file as follows: 



Note: Skip steps a through h and proceed to step 14 if your SPO server and system 

consoles are all on the same LAN. 

a. Press Esc to get the menu bar and select the Changes menu bar item (Figure 

10–3). A list of options appears as follows: 

Initialize Work 

Execute Changes 

Report Changes 

b. Select Initialize Work. Press Enter, then press Enter again to execute. 

c. Press Esc to activate the menu bar, and select the Routers menu bar item (Figure 

10–3). A list of options appears as follows: 

Add Router 

Delete Router 

Display Routers 

d. Press Enter to select Add Router. The window shown in Figure 10–5 appears. 

Destination Network Number: 0_____ . 0_____ . 0_____ . 0_____ 

Destination Network Name: _______________________________ 

______________________________________________________ 

Network Address of Router to ADD: _____ . _____ . _____ . _____ 

Router Name: __________________________________________ 

Comment: _____________________________________________ 

Figure 10–5. Add Router Information Window 

e. In the bottom portion of that window, enter the IP address and host name of the 

router. 

f. When done, press Enter. The Single Point Interface Utility window reappears. 

g. Select the Changes menu bar item (Figure 10–3). A list of options appears as 

follows: 




h. Select Execute Changes to enable the changes to the hosts file, and press Enter to 

execute. 

Note: When the router is configured, you can use the SAVE option to save the 

router and host information for later loading at other system consoles. 



14. Enable the SP Interface by taking the following steps: 

a. Press the F2 key to activate the Display Control menu. 

b. Select SP Interface and press Enter. 

c. Select Enable and press Enter again. Press Enter again to execute. 

15. Remove the diskette from the drive unit. 

Repeat this procedure for each system console. 

When done with a system console, you may copy and activate the Autoaction Message 

System (AMS) database at that console (10.14). Alternatively, you may install the hosts 

files first on all system consoles, then copy and activate the AMS databases. 

Continue with the steps in 10.14. 

10.14. Installing and Activating the AMS Database 

on the 2200 System Console 

Autoaction Message System (AMS) provides a pattern-matching capability to recognize and 

take automated actions for OS 2200 console messages. For SPO Basic Edition to operate 

properly, you must 

1. Remotely install the SPO AMS database (hmp-ix22) on each system console (10.14.1). 

2. Activate each system console’s AMS database using the AMS Utility session (10.14.2). 

3. Change each system console’s startup sessions to Systems Operations (10.14.3). 

Note: The installation of the AMS database is done from the SPO server. The 

activation is done on the 2200 system console. 

10.14.1. Remotely Installing the AMS Database from the SPO 

Server 

To remotely install the SPO AMS database (hmp-ix22) for each system console, take the 


Notes: 

• Before running the Remote Install Utility (RIU), you may wish to start the SPO 

daemons (10.16) to ensure that installation of the AMS database is recorded in the 

Remote-Install log. Information from that log may be needed if something goes 

wrong during the installation. 

• Switch the monitor concentrator to the SPO server position before beginning. 

• If you are not in console logon mode, switch out of graphical logon by pressing 

Alt-SysRq-P. 

1. If you are not already logged on, log on in character mode as spadmin, the SPO 

administrator (10.15.3). 



2. Run the RIU by entering the following command for each system console: 

/opt/SPO/riu hmp-ix22 console 

where console is the name of the system console (for example, cp_cons01) to which 

you are copying the database. 

The following message indicates RIU has started: 

riu 4.1 Wed Dec 20 13:49:47 CST 2000 

• If the console has not yet been configured for remote install, this message appears: 

-Console "console" not installed using riuc. 

Would you like to configure console now? 

(Y to configure, N to skip this console): 

You must then take the following steps: 

a. In response to that message, enter Y. You are prompted to enter the system 

type: 

What system type is console "console" connected to? 

1 = 1100/90, 2200/100, 2200/200, 2200/400, or 2200/600 

2 = Any other 2200 system (e.g., 2200/500, 2200/900) 

3 = don't know (so cannot configure "console" now) 

b. Enter 2 to specify the 2200 node. A message confirms that the system console 

has been configured: 

+Console "console" dynamically configured. 

• If the console has been configured for remote install, or after you take steps a and 

b, RIU compares the SMART level on the console with the database level to ensure 

that they are compatible. It then asks you to confirm the install or update. 

Getting SMART level from console "console" ... 

Interactive mode off. 

Hash mark printing on (1024 bytes/hash mark). 

# 

SMART level, on console "console", is 5R2 and database "hmp-ix22" 

level is 6. 

INSTALL or UPDATE hmp-ix22 on console? 

( or Y to execute, # to quit riu): 

3. Enter Y to proceed. Messages appear indicating that the database is being copied and 

installed. 

Looking for hmp-ix22 on console ... 



/console/backup/ams/*.t: No such file or directory. 

can't find list of remote files, oops 

/console/backup/ams/hmp-ix22.ams: No such file or directory. 

INSTALLING hmp-ix22 on console ... 





################################# 

+AMS database "hmp-ix22" successful INITIAL INSTALL on console "console". 

Note: If the database already exists on the console, riu asks whether you want to 

overwrite it. Answer Y if this is replacing an older version that you do not 

want to save. Answer N if you have modified an older version of hmp-ix22 and 

want to save it. If you enter Y and later change your mind, you can use 

rirestore to put back the previous version as described in the Single Point 

Operations Console/Enterprise Server Edition Administration and Configuration 

Guide. 

Repeat this procedure for each OS 2200 system console. Then continue with 10.14.2. 

10.14.2. Activating the SPO AMS Database at the 2200 System 

Consoles 

To activate the hmp-ix22 AMS database, perform the following at each 2200 system 

console: 

1. On the system console, press F3 to activate the Utilities menu (Figure 10–2). 

2. Select Optional Features and press Enter. 

A list of utilities appears, similar to the list in the right-hand panel of Figure 10–2. 

3. Select AMS Utility and press Enter. An Execute box appears. 

4. Press Enter. The AMS Utility window appears. 

5. At the command prompt, enter the following command: 

activate hmp-ix22 

A response indicating that the database will be activated appears. 

I0007: Database "hmp-ix22" will be activated. 

6. At the command prompt, enter exit to exit the AMS Utility session. 


10.14.3. Changing the Start-Up Session to Systems Operations at 

the System Consoles 

The start-up session for each system console determines which session is displayed when 

the replicated console is opened from the SPO Basic Edition. Change the start-up session 

to the Systems Operations session for each system console with the following steps: 

1. On the system console, press F3 to activate the Utilities menu. 

2. Select Configuration: Dynamic and press Enter. A list of change options appears. 

3. Select both options and press Enter. Another list of options appears (Figure 10–6). 



Figure 10–6. System Console F3 Utilities Dynamic Configuration Menu 

1. Select Display Current Values and press Enter. An Execute box appears. 

2. Press Enter. The Dynamic Configuration window appears with the cursor on the 

Console Control option. 

3. Press Enter. Tab down to the Start-up Session option. A list of options appears. 

4. Select the System Operations option. 

5. Press Enter. System Operations is now displayed as the start-up session. 

6. Press Enter. The cursor returns to the Dynamic Configuration menu. 

7. Select Execute Changes and press Enter. An Execute box appears. 

8. Press Enter. Wait for the “Working, please wait” box to disappear. 

9. Select Exit Configuration and press Enter. An Execute box appears. 


Switch the monitor concentrator to the SPO server position and proceed with Section 11, 

configuring the SPO workstation. 



10.15. Logging On to UnixWare 

Caution 

To prevent unauthorized access to the UnixWare node following initial installation, 

the site must change the default password to a different password. 

Note: Switch the monitor concentrator to the SPO_Server position before beginning 

(see 2.5.2). 

Several installation and configuration procedures require you to log on as the root user 

(user-id root). Root logon also provides superuser privileges. 

Before you start, press any key to stop the screen saver, if it is running. 

If the root prompt (#) is showing, you are already logged on as the root user (superuser). 

10.15.1. Switching Windows 

You can switch between graphical mode and console(character) mode, and switch among 

all configured windows, by using these control key combinations: 

Ctrl-Alt-Esc Console (character) mode 

Ctrl-Alt-F1 Graphical mode 

Ctrl-Alt-F2 through F8 Character-mode virtual terminals 

10.15.2. Logging On As the Root User (Superuser) in Graphical 

Mode 

Ensure you are in graphical mode by pressing Ctrl-Alt-F1. When UnixWare displays the 

graphical user interface (GUI) logon screen, log on as follows: 

1. In the Login ID field, enter root. 

2. In the Password field, enter unisysas. 

3. Click Login or press Enter. 

The UnixWare graphical desktop appears following this logon. 

10.15.3. Logging On As the Root User (Superuser) in Character 

Mode 

Ensure you are in the console session by pressing Ctrl-Alt-Esc. Then log on as follows: 

1. At the console login prompt, enter root. 


2. At the password prompt, enter unisysas. 

The root prompt (#) appears following this logon. 


10.16. Stopping and Starting the SPO Daemons 

Note: Switch the monitor concentrator to the SPO server position. 

The SPO daemons are background processes on the SPO server that must be running for 

the correct operation of SPO Basic Edition. If you need to stop them or start them, enter 

the appropriate command from the procedure below: 

1. If you are not already logged on at the SPO server, log on as superuser in character 

mode (10.15.3). 

2. Enter the following command to stop the SPO daemons: 

/etc/init.d/spod stop 

3. Enter the following command to start the SPO daemons: 

/etc/init.d/spod start 

Whenever the SPO server is rebooted, the SPO daemons restart automatically. 

You can use steps 2 and 3 above independently if for any reason you need to stop the 

daemons or restart them (for example, if one was stopped inadvertently). 




Section 11 

Installing and Configuring SPO 

Workstation Software 

This section describes how to prepare the SPO workstation for monitoring and control of 

either Windows or UnixWare nodes. 

The SPO workstation runs either Windows NT Workstation 4.0 or Windows 2000 

Professional Workstation, depending on the model of PC you receive. Use the following 

table to determine which operating system you will use. 

Workstation Model Operating System 

CWP Windows NT 4.0 

GWP-1—Identified by label E-4200 on front panel. Approximate 

size: H 5.5” (14cm), W 18” (46 cm), D 17” (43 cm). 

GWP-W—Identified by label E-1400 on front panel. Approximate 

size: H 3.5” (9 cm), W 11.5” (29 cm), D 14” (36 cm). 

Windows NT 4.0 

Windows 2000 

Professional 

The GWP-1 (Windows NT) and GWP-W (Windows 2000) workstations have the operatingsystem 

installation files preloaded on the hard drive, so full installation from the CD-ROM 

is not required. However, the operating system still must be installed and configured. You 

must complete the installation at the site. 

If the operating system has not been preloaded, you must perform a full installation from 

the CD-ROM. 

11.1. Preparing the SPO Workstation for Use 

Follow the appropriate instructions below to prepare the SPO workstation for use. 

Note: The client, or a representative of the client, must read and agree to software 

license agreements during the installation procedure. 

For Windows NT Workstation 4.0— 

1. Install and configure the Windows NT Workstation operating system (11.1) 

2. Install network services (11.2) 

3. Install the latest service pack for Windows NT Workstation 4.0 (11.3) 


Installing and Configuring SPO Workstation Software 

4. Install Y2K service packs, if needed (11.4) 

5. Configure the FTP service (11.5) 

6. Install the video driver (11.6) 

7. Install SPO display software (11.7), including 

a. XVision (11.7.1) 

b. ControlIT (if the monitored Intel node is running Windows) (11.7.2) 

c. Winsock Remote Shell Daemon (RSHD/NT) (if the monitored Intel node is running 

Windows) (11.7.3) 

8. Install SPO product information (11.13) 

For Windows 2000 Professional Workstation— 

1. Install and configure the Windows 2000 Professional Workstation operating system 

(11.9) 

2. Configure the display properties of the workstation (11.10) 

3. Install and configure Internet Information Services (11.11) 

4. Install SPO display software (11.12), including 

a. XVision (11.12.1) 

b. ControlIT (if the monitored Intel node is running Windows) (11.12.2) 

c. Winsock Remote Shell Daemon (RSHD/NT) (if the monitored Intel node is running 

Windows) (11.12.3) 

5. Install Single Point Operations product information (11.13) 

Figure 11–1 shows the software components you must install to monitor and control 

ClearPath IX server components using SPO Basic Edition software. 

Table 11–1 lists media and information needed for the various installation scenarios. 

Obtain these materials before beginning. 


SPO Server 

SPO Basic Edition 

SPO Workstation 

(Windows Workstation) 

SCO XVision 

ControlIT Viewer 

Winsock RSHD/NT 


Ethernet 

Managed Windows Nodes 

ControlIT Host 

Managed UnixWare Nodes 

UNIX Resource Monitor 

(URM) Agents 

Managed 2200 Nodes 

Figure 11–1. SPO Monitoring and Control Software Components 

HMP IX Server 



Table 11–1. SPO Workstation Installation Checklist 


11.1.1. Installing Windows NT on the Workstation 

Media needed: Windows NT Workstation CD-ROM—labeled “Microsoft Windows NT Workstation” 



Name __________________________ 



Organization _____________________________ 



CD-KEY ______________________________________ 



Computer Name screen 

Host name _____________________________ 

Determine the name by which the SPO workstation will be identified on the external TCP/IP 

network. 

11.1.2. Configuring Windows NT on the Workstation 


continued 






IP address _____________________________ 

Determine the IP address of the Windows NT workstation. 

Subnet mask or 255.255.255.0_____________________________ 

Determine the netmask address, if applicable. 

Primary WINS server address _____________________________ 

Determine the IP address of the primary WINS server, if applicable. 

Secondary WINS server address _____________________________ 

Determine the IP address of the secondary WINS server, if applicable. 

Domain name _____________________________ 

Determine the domain name the site uses for DNS, if applicable. 

IP address for DNS _____________________________ 

Determine the IP address or addresses for as many domain name servers as the site has. 





11.2. Installing Network Services on the Windows NT Workstation 


11.3. Installing the Latest Service Pack for Windows NT Workstation 4.0 

Media needed: Windows NT Service Pack CD-ROMs, numbered 1–n 

11.4. Installing Y2K Service Packs on the Windows NT Workstation 

Media needed: Windows NT Service Pack CD-ROM 

11.6. Installing the Video Driver on the Windows NT Workstation 

Media needed: ATI Installation CD-ROM International 

11.7.1. Installing and Configuring XVision on the Windows NT Workstation 

Media needed: SCO XVision CD-ROM—labeled “SCO Vision 2K” 

continued 






License Number ______________________________________ 

Enter the license number from the SCO Vision Family Certificate of License. 

Ethernet IP address ______________________________ 

Determine the Ethernet IP address of the SPO server. 

11.7.2. Installing ControlIT on the Windows NT Workstation 

Media needed: ControlIT installation package 

11.7.3. Installing Winsock RSHD/NT on the Windows NT Workstation 

Media needed: Winsock RSHD/NT 3.5" diskette 

11.9. Installing and Configuring Windows 2000 on the SPO Workstation 


Personalize Your Software screen 

Name __________________________ 

Determine the name the site wants identified with the Windows 2000 node (for example, the 

administrator’s name or the Windows 2000 owner name). 

Organization _____________________________ 

Determine the organization name the site wants identified with the Windows 2000 node. 

Computer Name and Administrator Password screen 

Host name _____________________________ 

Determine the name by which the SPO workstation will be identified on the external TCP/IP 

network. 

continued 





Internet Protocol (TCP/IP) Properties screen 

IP address _____________________________ 

Determine the IP address of the Windows NT workstation. 

Subnet mask or 255.255.255.0 _____________________________ 

Determine the netmask address, if applicable. 

Primary WINS server address _____________________________ 

Determine the IP address of the primary WINS server, if applicable. 

Secondary WINS server address _____________________________ 

Determine the IP address of the secondary WINS server, if applicable. 

Default gateway _____________________________ 

Determine the address of the default gateway, if applicable. 

IP address for DNS server _____________________________ 

Determine the IP address for the DNS server, if applicable. 

IP address for alternate DNS server _____________________________ 

Determine the IP address for the alternate DNS server, if applicable. 

11.12.1. Installing and Configuring Xvision on the Windows 2000 Workstation 

Media needed: SCO XVision CD-ROM—labeled “SCO Vision 2K” 


License number _____________________________ 

Determine the XVision license number. 

SPO server IP address _____________________________ 

Determine the IP address of the SPO server. 

11.12.2. Installing ControlIT on the Windows 2000 Workstation 

Media needed: ControlIT CD-ROM—labeled “ControlIT Advanced Edition” 

11.12.3 Installing Winsock RSHD/NT on the Windows 2000 Workstation 

Media needed: Remote Shell Daemon diskette—labeled “Winsock RSHD/NT” 

11.13 Installing SPO Product Information on the Workstation 

Media needed: CD-ROM labeled “SPO HMP Console for UnixWare Product Information CD-ROM” 



11.2. Installing and Configuring Windows NT 

Workstation 

This section tells how to install and configure the Windows NT operating system on the 


11.2.1. Installing Windows NT on the Workstation 

Begin Windows NT Workstation installation as follows: 

1. Insert the CD-ROM labeled “Microsoft Windows NT Workstation" into the drive. 

2. Reboot or power on the SPO workstation. 

The workstation boots from the CD-ROM, and a Welcome to Setup menu appears. 


A message appears to indicate that Setup has recognized the following mass storage 

device in your computer: 

Adaptec AHA-294X/AHA-394X/AIC-78XX SCSI Controller 


A message similar to this may appear: 

Setup has determined that one or more of your hard disks has more than 

1024 cylinders. 

5. If the message above appears, press Enter to continue. 

A message informs you that your hard disk is either new or erased, or that an operating 

system already exists. [Does this imply preload?] 


After a brief wait, a license agreement text screen appears. 



page. 


the license agreement. 



A screen appears that identifies the unpartitioned space on the hard drive. 

9. Use the arrow key to highlight the unpartitioned space, then press C to create a new 

partition. 

10. Press Backspace to clear the field, type 4000, then press Enter. 

The screen now shows a new partition with unformatted space of 4001 MB. 

11. Select the new partition, then press Enter. 






12. Use the up and down arrow keys to select the Windows NT file system (NTFS), then 

press Enter. 






The examination takes less than a second, then Setup begins copying files. When 

done, a message asks you to remove the CD-ROM in preparation for rebooting. 

15. Remove the CD-ROM from the drive, then press Enter. 




Following reboot, the Windows NT Setup screen appears. Continue by configuring 

Windows NT as described in the next subsection. 

11.2.2. Configuring Windows NT on the Workstation 


installation procedure in the preceding subsection. 

After Windows NT reboots, a Windows NT Setup screen appears with a message box 

asking you to insert the Windows NT CD-ROM. Take the following steps: 

1. Insert the Windows NT Workstation CD-ROM (labeled “Microsoft Windows NT 

Workstation 4.0”) into the CD-ROM drive, then click OK. 

A prompt indicates files are needed from the Windows NT CD-ROM. A scroll box 

identifies the directory from which they will be copied. 

2. Click OK to proceed. 





3. Click Next to continue with gathering information about your computer. 

A Setup Options screen appears. 

4. Select Typical setup, then click Next. 




5. Enter Name and Organization as follows: 


node. 












7. In the Name field, enter the host name from Table 2–2 by which the SPO workstation 


screen. 





that field. 



(administrator) to a different password. See 11.14.3 for the procedure. 


9. Click No, do not create an emergency repair disk option to select it. Then click Next 

to proceed. 

Note: There will be further instructions for creating an emergency repair disk 

after all software in installed and configured. Have a labeled blank diskette 


You are given the option to select Most Common or Show List. 

10. Select Show List, then click Next. 








Note: You can also select Windows Messaging and Games if the site prefers. 









13. Click Wired to the network, then click Next. 



a. Click Start Search. 

“DEC PCI Ethernet DECchip 21041 (detected)” is added to the list box. 

b. Click Find Next. 


No more adapters were found. 



protocol. The NWLink IPX/SPX compatible transport and NetBEUI Protocol are not 


15. Ensure that the TCP/IP protocol is selected. If not, click TCP/IP protocol to select it, 

then click Next, then click Next again. 

A dialogue box appears for DEC DECchip 21041 Based Adapter Setup. The default of 

AutoSense should be displayed. 


Installation of networking components begins. A message box asks whether you want 

to use Dynamic Host Configuration Protocol (DHCP) server. 

17. Click No. 




adapters: 

DEC PCI Ethernet DECchip 21041 





2) In the IP Address field enter the IP address for the Windows NT workstation 


3) Change the subnet mask to the netmask address from Table 2–2, or change it 

to 255.255.255.0 (class C). 



a) Click Add. 


c) Click Add. 



when done. 




Tab. 


2–2. 

d. If the site has a domain name server (DNS), click the DNS tab (otherwise skip this 

step), and take the following steps: 

1) Enter the domain name the site uses for DNS (Table 2–2). 

2) Enter the IP address for the first DNS from Table 2–2. 

3) Click Add. 



19. Click OK. 


A setup screen identifies the host name of the SPO workstation and asks whether the 


21. Click Workgroup, enter a workgroup name of CLEARPATH, then click Next to 

proceed. 

The Windows NT Setup screen indicates it is ready to finish setup. 











a. Month—Click the scroll bar arrow and scroll up or down to select the correct 

month. 

b. Year—Click the scroll bar arrow and scroll up or down to select the correct year. 



appears. 


A message box appears that indicates the type of video adapter and VGA-compatible 

display adapter detected 




Files are copied from the CD-ROM. Messages appear to indicate progress: 



27. Remove the CD-ROM from the drive unit, then click Restart Computer. 


automatically. The Windows NT logo appears and a message box prompts you to 



A logon dialogue box appears. 

29. Enter the following information: 




d. Click OK. 

Notes: 


• If the SPO workstation is part of a domain, you must also enter a domain 

name. 

The Welcome to Windows NT screen appears on the Windows NT desktop. 



Continue by installing network services (11.2). 

11.3. Installing Network Services on the Windows 

NT Workstation 

To install network services for the SPO workstation: 

1. Click Start, Settings, Control Panel to go to the control panel. 

2. In the control panel, double-click Network. 

3. Click the Services tab. 

4. Click Add. 

5. Click Microsoft Peer Web Services. 

6. Click OK. 

You are prompted to insert the Windows NT CD-ROM. 

7. Insert the CD-ROM. If a Windows CD-ROM window appears, you can close it. 

Verify that the path is set to D:\I386. 

8. Click OK. 

A Peer Web Services Setup window appears. 

9. Click OK. 

10. Click OK again. 

A message asks if you want to create a directory. 


A Publishing Directories window appears. 

12. Click OK. 

13. Click Yes to create the directories. 

In a few seconds, a window appears for installing the SQL Server driver. 

14. Click SQL Server once to highlight it, then click OK. 

Setup completes. 

15. Click OK. 

16. Click Add to add more services. 

17. By the same method as that for the Peer Web Service, select and add Simple TCP/IP 

services. 

18. Review the list of services, which should contain the following: 

• Computer browser 

• Microsoft Peer Web Services 

• NetBIOS interface 


• RPC configuration 

• Server 

• Simple TCP/IP services 



19. Close the Network window. 

A message asks whether you want to shut down the computer at this time. 

20. Click No. 

Continue with 11.3. 

11.4. Installing the Latest Service Pack for Windows 

NT Workstation 4.0 

Note: The latest recommended service pack is shipped with the system. The 

instructions that follow are based on Windows NT Service Pack 4. If a later 

service pack arrived with the system, install it using these instructions as a 

guideline. 

To install a Windows NT Service Pack on the SPO workstation, follow these steps: 

1. Insert the Windows NT Service Pack n CD-ROM into the drive unit. Internet Explorer 

should start automatically and a Service Pack n home page appears. 

2. Click the Install Service Pack n link, then click Open. 


3. Click Accept the License Agreement. 

4. Click Install. 

A Service Pack Setup screen appears. 

Files are copied and the service pack is installed. During installation, a Windows NT 


message: 



the Service Pack n version? 


When setup finishes, a prompt appears to reboot the system. 

6. Remove the CD-ROM from the drive and click Restart. 




11.5. Installing Y2K Service Packs on the Windows 


Once the system is rebooted (11.3, step 6), log on to the workstation(11.14.2). The 

operating system checks for possible Year 2000 problems and displays a message listing 

any service packs needed to correct them: 

To resolve Windows NT 4.0 Year 2000 issues you must install: 

Microsoft Internet Explorer Service Pack 

Microsoft Data Access Components Service Pack 

Note: Make note of any other service packs not listed here so that you can install them 

as well. 

If no year-2000 issues are detected (no service packs are listed), continue by configuring 

the FTP service, as described in 11.5. Otherwise, follow these steps to install the service 

packs for Y2K remediation: 

1. Click No to View the Y2K.TXT file. 

2. Close the Welcome to Windows NT window. 

3. Insert the Windows NT Service Pack CD-ROM in the drive. Internet Explorer should 

again start automatically. 

4. Scroll down the page and click Microsoft Internet Explorer Service Pack. 

5. Click Install IE 4.01 SP1 for Intel-Based Systems. 

6. Click Open. 

An Active Setup window appears. 


8. Check I accept, then click Next. 

9. In the Installation Option list, click Standard Installation. 


11. In the Windows Desktop Update, select No. 


13. Highlight the correct country and click Next. 

14. Click Next again. 

A status bar shows the progress of the update installation. 

15. When setup has finished, click OK. 

A restart window is displayed. 

16. Remove the CD-ROM and click OK. 

The system reboots. 



17. When the reboot is finished, log on to Windows NT (11.14.2). The update continues 

setting up components and then brings up the desktop. 

18. Close any Welcome windows that appear. 

19. Insert the service pack CD-ROM again. Internet Explorer starts again. 

20. Scroll down and click Microsoft Data Access Components 2.0 Service Pack 1. 

21. Click Install Data Access Components for Intel-Based Systems. 

22. Select Run this program from its current location, then click OK. 

23. Click Yes for the security warning. 

24. Click Yes to accept the license agreement. 


26. Click Complete Install. 


28. Remove the CD-ROM and click Restart Windows. 

If any other year-2000 service packs were listed at the beginning of this section, install 

them in the same manner. 

Continue by configuring the FTP service (11.5). 

11.6. Configuring the FTP Service on the Windows 


To configure the FTP service, take the following steps: 

1. If you are not currently logged on, power on or restart the Windows NT workstation 

and log on as the administrator. 

2. Click Start, Programs, Microsoft Peer Web Services (common), then Internet Service 

Manager. 

3. In the Computer column, double-click the icon associated with the FTP service (FTP 

listed in Service column). 

A tabbed FTP Service Properties screen opens. 

4. Click the Directories tab and configure access as follows: 

a. Select the drive:\InetPub\ftproot (alias ) directory by clicking on it. The 

drive may be C or D. 

b. Click Edit Properties. 

A Directory Properties window appears. 

c. Click the Write check box in the Access section at the bottom of the window to 

enable write access (ensure that a check mark appears in the check box). 

d. Click OK, then Apply, then OK again. 




Continue by installing the video driver (11.6). 

11.7. Installing the Video Driver on the Windows NT 

Workstation 

Follow this procedure to install the video driver: 

Notes: 

• If you received the GWP-1 console type, start at step 1. 

• The GWP-1 console video driver requires Service Pack 4 or higher. 

• For the CWP console type, start at step 10. 

For GWP-1 console type only: 

1. Log on to Windows NT (11.14.2) and insert the ATI Installation CD-ROM International 

into the drive. 

The ATI Installation program starts automatically. 

2. Click Easy Install. 


4. Select I agree, then click Next. 

5. Select Express Setup if it is not already selected, then click Finish. 

A message appears when the installation finishes: 

Install completed successfully. 

6. Click OK. 

A message asks if you wish to restart the computer. 

7. Remove the CD-ROM from the drive and click Yes. 

The system reboots. 

8. When the reboot is done, log on to Windows NT again. 

An Invalid Display Settings window appears. 

9. Click OK. 

A window appears for configuring the video display. 

For both GWP-1 and CWP console types: 


Note: If the Display Properties window is not on the screen, right-click anywhere 

on the desktop, then click Properties in the pop-up menu that appears. 

a. Move the Desktop Area slider to the right to select 1280x1024 pixels. 



b. Click Test to ensure that the default settings work. 


selected. 

c. Click OK to proceed. 

A color test pattern briefly appears followed by a message box asking whether you 

saw the test pattern properly. 

d. Click Yes to proceed. 


e. Click OK to save the display properties settings. 


f. Click OK to proceed. 

Continue by installing SPO display software, 11.7. 

11.8. Installing SPO Display Software on the 

Windows NT Workstation 

SPO display software includes SCO XVision, ControlIT (a product of Computer 

Associates), and Winsock RSHD/NT. 

Take these steps to install the SPO display software on the SPO workstation: 

1. Install and configure XVision (11.7.1) 

2. Install ControlIT (11.7.2). 

3. Install Winsock RSHD/NT (11.7.3) 

After you finish installing the display software, you will skip to 11.13 and continue by 

installing SPO product information. 

11.8.1. Installing and Configuring XVision on the Windows NT 

Workstation 

XVision is an X terminal emulator that runs on the SPO workstation. XVision allows the 

SPO workstation to display SPO Basic Edition screens for monitoring and controlling 

ClearPath IX server components. 

Install and configure XVision on the SPO workstation as follows: 

1. If you are not currently logged on, power on or restart the SPO workstation and log on 

(11.14.2). 

2. Insert the CD-ROM labeled “SCO Vision 2K” into the drive unit. 

Note: If autoinsert notification is configured in Windows NT, the setup program 

may start, and the Welcome screen appears automatically, in which case 

you can proceed to step 7. 



3. Click Start, Settings, then Control Panel. 

The Control Panel window appears. 

4. Double-click Add/Remove Programs. 

An Add/Remove Programs Properties window appears. 

5. At the Install/Uninstall tab, click Install. 

You are prompted to insert the product’s diskette or CD-ROM. 

6. Click Next, then Finish to install. 

An SCO Vision 2K screen appears. 


The SCO Vision 2K Setup Wizard appears. 

8. Click OK. 

A Product Selection menu appears. 

9. Select SCO XVision Eclipse 7.3. 


A setup options menu appears. 

11. Select Typical, then click Next. 

A prompt to enter your license number appears. Clear the checkmark for "I would like 

to evaluate the above products." 

12. Type the license number from Table 11–1 or from the SCO Vision Family Certificate of 

License, then click Next. 

An XVision Online Registration window appears. 

13. Click No, then Next. 

A summary window appears. 

14. Click OK. 

Software is now loaded. 

A Restart the Computer window appears. 

15. Remove the CD-ROM and click Yes. 

The workstation reboots and the logon prompt appears. 

16. Log on to the workstation again (11.14.2). 

An XVision Optimizer window appears. 


XVision Server Optimization occurs. Wait for completion. 


Complete XVision installation as described in the following subsections by 

• Copying the SPO Basic Edition fonts 


• Installing the SPO Basic Edition fonts 

• Configuring XVision 

Copying SPO Basic Edition Fonts 


SPO Basic Edition uses fonts that are not supplied by either Windows NT or XVision. In 

addition, SPO Basic Edition uses aliases for some of the fonts supplied by XVision. The 

fonts and aliases are supplied on the SPO Basic Edition release media and reside on the 

SPO server. 

Standard X fonts (100dpi, 75dpi, misc, and so on) are supplied in .FON format, which is the 

format supported by Windows NT. Font files specific to SPO Basic Edition are in .pcf 

format, which XVision can use without recompilation. 

To make the SPO Basic Edition fonts available to XVision, you must copy the fonts from 

the SPO server to the SPO workstation and then install them. The procedures for these 

tasks are given next. 

This procedure describes how to copy the SPO Basic Edition fonts from the SPO server to 

the SPO workstation: 


(11.14.2). 

2. Click Start, Programs, then Command Prompt. 

A command prompt window opens. 

3. At the command prompt, type the following command, then press Enter to change to 

the directory containing XVision fonts. 

cd \progra~1\vision\fonts 

4. Create a subdirectory under that directory, and then change to it, by entering the 

following commands: 

mkdir spofonts 

cd spofonts 

5. Initiate an FTP session by entering the following command: 

ftp sposerver-ip 

where sposerver-ip is the Ethernet IP address of the SPO server (see Table 2–2). 

An FTP logon prompt appears. 

6. Log on as follows: 

a. Type spadmin (the SPO administrator user-id). 

b. Press Enter to advance to the password field. 

c. Type unisys1234 (the default installation password). 

d. Press Enter again. 



7. Enter the following commands to 

• Set the transfer mode to binary. 

• Turn off interactive prompting. 

• Change to the XVision fonts directory on the SPO server. 

• Transfer the font files to the PC. 

binary 

prompt 

mget /opt/SPO/XP/xvfonts/*.* 

8. Enter the following commands to exit FTP and the command prompt window: 

quit 

exit 

You now install the new fonts in XVision. 

Installing SPO Basic Edition Fonts in XVision 

The procedure for making the SPO Basic Edition fonts available to XVision is as follows: 

1. Click the right mouse button on the green XVision logo on the right side of the taskbar, 

then click Properties. 

A Properties for XVision window appears. 

2. Click the Fonts tab. 

3. Add the new fonts as follows: 

a. Click Add. 

b. In the Add New Font Path Item window, click Add. 

c. In the “Choose a folder of fonts” window, double-click the spofonts folder. 

d. With Look in: showing the spofonts directory, and File name: showing fonts or 

fonts.dir, click Open. 

e. Click Apply, but do not close the Properties for XVision window (do not click OK). 

SPO font installation is complete. 

Configuring XVision Display, Server, and Security Properties 

Follow these steps to configure the XVision display, server, and security properties: 

1. Configure display settings as follows: 

a. If the Properties for XVision window is not open, right-click the green XVision logo 

on the right side of the taskbar, then click Properties. 

A Properties for XVision window opens. 

b. Click the Display tab (if it is not already the active tab). 

c. Click Single window. 



d. Click Virtual root. 

e. Click Custom, then set root size to 1280 x 1024. 

f. Click Advanced and make sure all accessible boxes are deselected (not checked). 

g. While still at the Single-Window Mode window, click OK (do not click OK at the 

Properties for XVision window). 

2. At the Properties for XVision window, configure Server and Security properties for 

XVision as follows: 

a. Click the Server tab. 

b. Click Bug compatibility to select it. 

c. Make sure the X Display number is 0 (default). 

d. Verify in the Advanced, Extensions area that only SHAPE is selected. Click the 

scroll bar to scroll down and uncheck any items that are checked, other than 

SHAPE. 

e. Click the Security tab. 

f. Click the XDMCP check box to select it, then click Direct. 

g. Type the IP address of the SPO server in the Host entry box. No other boxes on 

this tab should be checked. 

h. Click the Diagnostics tab. 

i. Clear the check box for Helpful Interactive Support. 

3. Click OK to complete the XVision configuration. 

A window asks whether you wish to restart the XVision server. 

4. Click Yes. 

If the Intel node of the ClearPath system is running Windows NT, minimize the XVision 

window now and proceed by installing ControlIT (11.7.2). 

If the Intel node is running UnixWare, proceed to 11.13. 

11.8.2. Installing ControlIT on the Windows NT Workstation 



as the administrator (11.14.2). 












The Installation Wizard screen appears. Make sure Install Agent Viewer is checked 

and Install Agent Host is not checked. Under Setup Options, select Advanced. 


A screen for installing Unicenter TNG Framework appears. 



8. Click OK. 

A Select Destination Directory screen appears. 










13. Set the Windows NT path to ControlIT as follows: 

a. Click Start, Settings, then Control Panel. 


b. Double-click the System icon. 

c. Click the Environment Tab. 

The System Properties window appears. 

d. Click Path in the list of system variables. 

e. In the Value field, go to end of path and type the following: 

;C:\ControlIT 

f. Click SET, then click OK to exit. 

14. Reboot the SPO workstation. 

Continue by installing Winsock RSHD/NT (11.7.3). 



11.8.3. Installing Winsock RSHD/NT on the Windows NT 

Workstation 

Winsock Remote Shell Daemon (RSHD/NT) is a Windows NT service that supports 

ControlIT by providing Remote Copy (RCP) server capabilities. Once installed, Winsock 

RSHD/NT runs as a service that automatically starts whenever the SPO workstation is 

booted. No further user interaction is required. 

Install Winsock RSHD/NT as follows: 


(11.14.2). 

2. Insert the Winsock RSHD/NT diskette into the drive. 


4. Double-click Add/Remove Programs. 

An Add/Remove Programs Properties window appears. 


You are prompted to insert the product diskette or CD-ROM. 


An NT Run Installation window appears. 

7. Click Finish. Windows NT momentarily displays the ADD/REMOVE window. Then a 

Winsock RSHD/NT installation window appears. 

8. Verify that the information shown in the window is correct: 

• The destination drive and directory should be C:\WRSHDNT. 

• The box labeled Install as a Windows NT service should be checked. 

9. If necessary, change the drive and directory, and click the check box to set it. When 

done, click INSTALL to begin the installation. Files will be copied to disk. 

A Winsock RSHD/NT warning window is displayed next. Click Yes. 

After a brief wait, the following prompt appears: 

Do you want to start the Winsock RSHD/NT Service automatically when 

Windows NT starts? 


The Winsock RSHD/NT install completes, and the service is installed and automatically 

appears in the Windows NT list of services following reboot. 

Answer Yes or No to the message about reading the manual. 

11. Reboot the Windows NT workstation. 

Proceed to 11.13 and install the SPO product information. 

Continue by changing the default Windows password (11.14.3); then proceed to Section 12. 



11.9. Setting Up the Windows 2000 Workstation If 

Windows Is Preloaded 

The next subsections tell how to prepare the SPO workstation for use if Windows 2000 has 

been preloaded on it. (Windows 2000 is preloaded on workstation style GWP-W.) Take the 


1. Run Windows 2000 Professional Setup to configure the workstation with information 

local to the site. 

2. Configure the display properties. 

3. Install and configure Internet Information Services. 

4. Install the display software. 

These procedures are described in 11.9 through 11.12. 

11.10. Installing Windows 2000 on the SPO 

Workstation 

Take the following steps to configure a workstation on which Windows 2000 has been 

preloaded: 

1. Power on the workstation. 

The system boots, and the Windows 2000 Professional Setup window appears. 


The License Agreement dialogue box is displayed. 

3. Click I accept this agreement, then click Next. 

The Regional Settings dialogue box appears. 

4. Customize the locale and keyboard settings if the defaults are not correct. (The 

dialogue box is self-explanatory.) Then click Next. 

A dialogue box labeled Personalize Your Software appears. 


a. Name field—Enter the user name the site wants identified with the Windows 2000 

node. 



Windows 2000 node. 


A dialogue box labeled Computer Name and Administrator Password appears. 

6. In the Name field, enter the host name from Table 2–2 by which the SPO workstation 

will be identified on the external TCP/IP network. 






that field. 


(administrator) to a different password. See 11.14.3 for the procedure. 

A dialogue box labeled Date and Time Settings appears. 

8. Set the correct date, time, and time zone for the site. (The dialogue box is selfexplanatory.) 

Then click Next. 

The Network Settings dialogue box appears. 

9. Select Custom Settings, then click Next. 

The Networking Components dialogue box appears. 

10. Click Internet Protocol (TCP/IP) to highlight it, then click the Properties button. 

An Internet Protocol (TCP/IP) Properties window appears. 

11. Click Use the following IP address. Enter the information from Table 2–2 in the fields 

for the IP address, subnet mask, default gateway, DNS server, and alternate DNS 

server, where applicable. 

12. Click OK to close the Internet Protocol (TCP/IP) Properties window. 


The Workgroup or Computer Domain dialogue box appears. 

14. Click the first option (No, this computer is not on a network…). 

15. Change the workgroup name to CLEARPATH, then click Next. 

The components you entered are installed; then a Performing Final Tasks window 

charts progress as the Start menu is updated and other tasks are completed. This may 

take up to 10 minutes. Finally, a message says you have successfully completed the 

setup. 

16. Click Finish on the message about successful completion. 

The workstation reboots. Following reboot, the Network Identification Wizard 

appears. 


The Users of This Computer dialogue box appears. 

18. Select Users must enter a user name… 


Network identification completes. 


A logon screen appears. Leave it in place for step 1 below. 

Continue by setting up the display properties on the workstation, as described next. 



11.11. Configuring Display Properties on the 

Windows 2000 Workstation 

Follow these steps to prepare the workstation for installing SPO display software. 

1. Log on to the workstation (11.14.1) using the logon screen that appeared in step 20, 

above. The screen will already show Administrator as the user-id. 

Following logon, your personal settings are automatically loaded, and a Getting Started 

with Windows 2000 window appears. 

2. If you do not want the Getting Started window to appear every time you log on, 

uncheck the box labeled Show this screen at startup. Then close the window (click X 

in the upper right-hand corner of the screen). Continue with step 3. 

3. Click Start. On the succeeding menus, highlight Settings, click Control Panel, and 

double-click the Display icon. 

The Display Properties window appears. 

4. Click the Screen Saver tab. 

5. Click the Power button in the section labeled Energy-saving features of monitor. 

The Power Options Properties dialogue box appears. 

6. Click the pull-down menu in the Power Schemes section and select the Presentation 

scheme. 

7. Click OK. 

You are returned to the Display Properties window. 

8. Click the Settings tab, then make the following selections: 

• Colors: Click the pull-down menu, then click True Color (24-bit). 

• Screen area: Move the slider to the right until 1280 x 1024 appears. 

9. Click OK. 

The new settings are applied, and the Display Properties window reappears. 

Note: Following step 10 below, you have 15 seconds to click Yes on the Monitor 

Settings screen (step 11). After that the original settings are reestablished. If 

that happens, repeat steps 8 through 11. 

10. Click OK on the Display Properties window. 

The Monitor Settings screen appears. This screen may be reduced in size because of 

the new screen-area value just selected. 

11. Quickly click Yes on the Monitor Settings screen. (See note above.) 

Continue by installing and configuring Internet Information Services, as described next. 



11.12. Installing and Configuring Internet 

Information Services on the Windows 2000 

Workstation 

Follow these steps to install and configure Internet Information Services (IIS). 

1. If the Control Panel is not already displayed, click Start, then Settings, then Control 

Panel. 


2. Double-click the Add/Remove Programs icon. 

The Add/Remove Programs window appears. 

3. Click Add/Remove Windows Components. 

The Windows Components Wizard window appears. 

4. Check the box for Internet Information Services, then click Next. 

Components are configured, and the Insert Disk window appears. 

5. Click OK. 

The Files Needed window appears. 

6. In the box labeled Copy files from, enter C:\I386. 

7. Click OK. 

The Insert Disk window appears again. 

8. Click OK. 

The Files Needed window appears again. 

9. Again in the box labeled Copy files from, enter C:\I386. 

10. Click OK. 

The following message appears in the Windows Components Wizard window: 

You have successfully completed the Windows Component Wizard. 


12. In the Add/Remove Programs window, click Close. 

13. In the Control Panel window, double-click the Administrative Tools icon. 

The Control Panel window becomes the Administrative Tools window. 

14. Double-click the Internet Services Manager icon. 

The Internet Information Services window appears. 

15. Click the plus sign (+) to the left of the Workstation icon to expand the tree. 

16. Right-click the Default FTP Site icon and select Properties from the pull-down menu 

that appears. 

The Default FTP Site Properties window appears. 



17. Select the Home Directory tab and check the Write box in the FTP Site Directory 

section. 

18. Click OK. 

19. Close the Internet Information Services window (click X in the upper right-hand 

corner of the window). 

20. Close the Administrative Tools window. 

Continue by installing the SPO display software, as described next. 

11.13. Installing SPO Display Software on the 

Windows 2000 Workstation 

SPO display software includes SCO XVision, ControlIT (a product of Computer 

Associates), and Winsock RSHD/NT. This section gives the following procedures for 

installing these products, in the order shown: 

1. Install and configure XVision. 

2. Install ControlIT. 

3. Install Winsock RSHD/NT. 

The installation procedures are described next. 

11.13.1. Installing and Configuring XVision on the Windows 2000 

Workstation 

XVision is an X terminal emulator that runs on the SPO workstation. XVision allows the 

SPO workstation to display SPO Basic Edition screens for monitoring and controlling 

ClearPath IX server components. 

Install and configure XVision on the SPO workstation as follows: 


(11.14.1). 

2. Insert the CD-ROM labeled “SCO Vision 2K” into the drive unit. 

A SCO Vision 2K screen appears. 


The SCO Vision 2K Setup Wizard appears. 

4. Click OK. 

A product-selection menu appears. 

5. Select SCO XVision Eclipse 7.3. 


A setup options menu appears. 



7. Select Typical, then click Next. 

A prompt to enter your license number appears. A prompt also appears asking 

whether you wish to evaluate the above products. Clear the checkmark for the prompt 

about evaluating products. 

8. In the box for the license number, type the license number from Table 11–1 or from the 

SCO Vision Family Certificate of License, then click Next. 

A registration window appears. 

9. Click No, then Next. 

A summary window appears. 

10. Click OK. 

Software is now loaded (about 2 minutes), and a Results window appears confirming 

the loading of SCO XVision Eclipse 7.3. 

11. Click OK. 

A window appears asking you to restart the computer. 


The workstation reboots and the logon prompt appears. 

13. Log on to the workstation again (11.14.1). 

A few screens appear briefly; then an XVision Optimizer window appears. 


XVision server optimization occurs. Wait for completion (about 4 minutes). 


16. Remove the CD ROM from the drive. 

Complete XVision installation as described in the following subsections by 

• Copying the SPO Basic Edition fonts 

• Installing the SPO Basic Edition fonts 

• Configuring XVision 

Copying SPO Basic Edition Fonts 

SPO Basic Edition uses fonts that are not supplied by either Windows 2000 or XVision. In 

addition, SPO Basic Edition uses aliases for some of the fonts supplied by XVision. The 

fonts and aliases are supplied on the SPO Basic Edition release media and reside on the 

SPO server. 

Standard X fonts (100dpi, 75dpi, misc, and so on) are supplied in .FON format, which is the 

format supported by Windows 2000. Font files specific to SPO Basic Edition are in .pcf 

format, which XVision can use without recompilation. 



To make the SPO Basic Edition fonts available to XVision, you must copy the fonts from 

the SPO server to the SPO workstation and then install them. The procedures for these 

tasks are given next. 

This procedure describes how to copy the SPO Basic Edition fonts from the SPO server to 

the SPO workstation: 


(11.14.1). 

2. Click Start, Programs, Accessories, then Command Prompt. 


3. At the command prompt, type the following command, then press Enter to change to 

the directory containing XVision fonts. 

cd \progra~1\vision\fonts 

4. Create a subdirectory under that directory, and then change to it, by entering the 

following commands: 

mkdir spofonts 

cd spofonts 

5. Initiate an FTP session by entering the following command: 

ftp sposerver-ip 

where sposerver-ip is the Ethernet IP address of the SPO server (see Table 2–2). 

An FTP logon prompt appears. 

6. Still on the workstation, log on to the server as follows: 



c. Type unisys1234 (the default installation password). 

d. Press Enter again. 

7. Enter the commands below to accomplish the following tasks: 

• Set the transfer mode to binary. 

• Turn off interactive prompting. 

• Change to the XVision fonts directory on the SPO server. 

• Transfer the font files to the PC. 

These are the commands: 

binary 

prompt 

mget /opt/SPO/XP/xvfonts/*.* 

8. Enter the following commands to exit FTP and the command prompt window: 

quit 

exit 



You now install the new fonts in XVision, as described next. 

Installing SPO Basic Edition Fonts in XVision 

The procedure for making the SPO Basic Edition fonts available to XVision is as follows: 

1. Click the right mouse button on the green XVision logo on the right side of the taskbar, 

then click Properties. 

A Properties for XVision window appears. 

2. Click the Fonts tab. 

3. Add the new fonts as follows: 

a. Click Add. 

b. In the Add New Font Path Item window, click Add. 

c. In the “Choose a folder of fonts” window, double-click the spofonts folder. 

A dialogue box appears with a Look in: text box showing the spofonts directory 

and a list of file names that includes either fonts or fonts.dir. If the Look in: box 

does not contain spofonts, enter that name before proceeding. 

d. Click Add. (Do not select anything first.) 

e. Click Apply, but do not close the Properties for XVision window (do not click OK). 

SPO font installation is complete. Continue by configuring XVision, as described next. 

Configuring XVision Display, Server, and Security Properties 

Follow these steps to configure the XVision display, server, and security properties: 

1. Configure display settings as follows: 

a. If the Properties for XVision window is not open, right-click the green XVision logo 

on the right side of the taskbar, then click Properties. 

A Properties for XVision window opens. 

b. Click the Display tab (if it is not already the active tab). 

c. Click Single window. 

d. Click Virtual root. 

e. Click Custom, then set root size to 1280 x 1024. 

f. Click Advanced and make sure all accessible boxes are deselected (not checked). 

g. While still at the Single-Window Mode window, click OK (do not click OK at the 

Properties for XVision window). 

2. At the Properties for XVision window, configure server and security properties for 

XVision as follows: 

a. Click the Server tab. 

b. Click Bug compatibility to select it. 



c. Make sure the X Display number is 0 (default). 

d. Verify in the Advanced, Extensions area that only SHAPE is selected. Click the 

scroll bar to scroll down and uncheck any items that are checked, other than 

SHAPE. 

e. Click the Security tab. 

f. Click the XDMCP check box to select it, then click Direct. 

g. Type the IP address of the SPO server in the Host entry box. No other boxes on 

this tab should be checked. 

h. Click the Diagnostics tab. 

i. Clear the check box for Helpful Interactive Support. 

3. Click OK to complete the XVision configuration. 

A window asks whether you wish to restart the XVision server. 

4. Click Yes. 

If the Intel node is running UnixWare, proceed to Section 12. 

If the Intel node of the ClearPath system is running Windows 2000, minimize the XVision 

window now and proceed by installing ControlIT and Winsock RSHD/NT, as described in 

11.12.2 and 11.12.3. 

11.13.2. Installing ControlIT on the Windows 2000 Workstation 



as the administrator (11.14.1). 

2. Insert the ControlIT CD-ROM (labeled “ControlIT Advanced Edition”) into the drive 

unit. 




After an initial ControlIT window, the License Agreement window appears. 





The Installation Wizard on the ControlIT Setup screen appears. Make sure Install 

Agent Viewer is checked and Install Agent Host is not checked. Under Setup Options, 

select Advanced. 


A screen for installing Unicenter TNG Framework appears. 





8. Click OK. 

A screen for selecting the destination directory appears. 




A message indicates that ControlIT Setup is ready to install the required files. 


When the installation finishes, a message says that installation is complete. 

12. Click OK. 



13. Click No, then close the ControlIT screen. (Click X in the upper right-hand corner.) 

14. Set the Windows 2000 path to ControlIT as follows: 

a. Click Start, Settings, then Control Panel. 


b. Double-click the System icon. 

The System Properties window appears. 

c. Click Advanced tab. 

d. Click Environment Variables. 

The Environment Variables window appears. 

e. Click Path in the System list of variables. 

f. Click Edit. 

The Edit System Variable window appears. 

g. In the Variable Value field, go to the end of the path and type the following: 

;C:\ControlIT 

h. Click OK to exit the Edit System Variable window. 

i. Click OK to exit the Environment Variables window. 

j. Click OK to exit the System Properties window. 

14. Close the Control Panel. 

The setting is complete, but it will not take effect until the SPO workstation is 

rebooted. 

15. Reboot the SPO workstation, as follows: 

a. Click Start. 



b. Click Shut Down. 

c. Click to get the drop-down menu, then click Restart. 

d. Click OK. 

16. Log on as the administrator (11.14.1) using the logon dialogue box that appears. 

17. If an XVision screen appears, close it by clicking X in the upper right-hand corner; then 

click OK to the message saying your XVision session will end. 


Continue by installing Winsock RSHD/NT. 

11.13.3. Installing Winsock RSHD/NT on the Windows 2000 

Workstation 

Winsock Remote Shell Daemon (RSHD/NT) is a Windows service that supports ControlIT 

by providing Remote Copy (RCP) server capabilities. Once installed, Winsock RSHD/NT 

runs as a service that automatically starts whenever the SPO workstation is booted. No 

further user interaction is required. 

Install Winsock RSHD/NT as follows: 


(11.14.1). 

2. Insert the Remote Shell Daemon diskette (labeled “Winsock RSHD/NT”) into the 

floppy drive. 


4. Double-click the Add/Remove Programs icon. 

An Add/Remove Programs window appears. 

5. Click the Add New Programs icon. 

A dialogue box appears. 

6. Click the CD or Floppy box. 

You are prompted to insert the product diskette or CD-ROM. The diskette labeled 

“Winsock RSHD/NT” should already be in the floppy drive. If it is not, insert it now. 


A Run Installation Program window appears. 

8. Click Finish. Windows 2000 momentarily displays the Add/Remove window. Then a 

Winsock RSHD/NT installation window appears. 

9. Verify that the information shown in the window is correct: 

• The destination drive and directory should be C:\WRSHDNT. 

• The box labeled Install as a Windows NT Services should be checked. 



10. If necessary, change the drive and directory, and click the check box to set it. When 

done, click Install to begin the installation. Files will be copied to disk. 

A Winsock RSHD/NT warning window is displayed next. 

11. Click Yes on the warning window. 

After a brief wait during which files are copied, the following prompt appears: 

Do you want to start the Winsock RSHD/NT Service automatically when 

Windows NT starts? 


The Winsock RSHD/NT install completes, and the service is installed and automatically 

appears in the Windows list of services following reboot. 

13. Answer Yes or No to the message about reading the manual. 

14. Close the Add/Remove Programs window (click X in the upper right-hand corner). 

15. Close the Control Panel window. 

16. Remove the diskette from the drive. 

17. Reboot the Windows 2000 workstation. 


11.14. Installing SPO Product Information on the 

Workstation 

Documentation for the SPO product is provided on a CD-ROM labeled “SPO HMP Console 

for UnixWare Product Information CD-ROM.” Follow these steps to install the 

documentation on the SPO workstation: 

1. Insert the CD-ROM labeled “Single Point Operations Product Information” into the 

SPO workstation CD-ROM drive. 

2. If the CD-ROM Setup window launches automatically, click Exit to close it. 

3. Open the Windows Explorer as follows: 

• For Windows NT 4.0 click Start > Programs > Windows NT Explorer. 

• For Windows 2000 click Start > Programs > Accessories > Windows Explorer. 

4. Create a spo-pi folder on the C drive as follows: 

a. Click once on the C drive to highlight it. 

b. On the main menu bar, click File, then click New > Folder. 

c. In the highlighted New Folder box that appears in the right-hand pane, type spo-pi 

to name the folder. 

d. Press Enter. 



5. Copy the contents of the CD-ROM to the spi-pi folder as follows: 

a. Click once on the CD-ROM icon (spohmp6_1) in the folders pane. 

The contents of the CD-ROM are displayed in the right-hand pane. 

b. Press Ctrl-A to highlight all of the files and folders on the CD-ROM. 

c. Press Ctrl-C. 

The highlighted materials are marked to be copied. 

d. Click the spo-pi folder in the left-hand pane. 

e. Press Ctrl-V 

The material is copied from the CD-ROM to the spo-pi folder. 


7. Install the Single Point Operations Product Information as follows: 

a. Double-click the Setup icon in the right-hand pane of the Windows Explorer 

window. 

The SPO HMP Console Product Documentation CD-ROM Setup window appears. 

b. Click Adobe Acrobat Reader with Search. 

An informational window appears. 

c. Click OK. 

The Acrobat Reader Setup launches. 

d. Click Next. 

The Choose Destination Location window appears. 

e. Click Next. 

The Acrobat Reader installation continues. 

f. Click OK. 

The installation is complete. 

g. Click OK. 

You return to the SPO HMP Console Product Documentation window. 

h. Click Unisys CDLib Manager. 



A User Information window appears. 

j. Click Next. 

A Destination Location window appears. 

k. Click Next. 

A Select Program Folder window appears. 

l. Click Next. 



A Start Copying Files window appears. 

m. Click Next 

The installation continues, and a Setup Complete window appears. 

n. Click Finish. 

Close Windows Explorer and any windows created by the setup program. 


11.15. Logging On to the Windows Workstation 

This section describes how to log on to Windows 2000 and Windows NT and how to 

change the default password for either Windows 2000 or Windows NT. 

11.15.1. Logging On to the Windows 2000 (Professional) 

Workstation as the Administrator 

Whenever you restart or power on the SPO workstation during installation, if the 

workstation is running Windows 2000, the Log On to Windows 2000 window appears. Take 

the following steps to log on: 

Notes: 


• If the SPO workstation is part of a domain, you must also enter a domain name. 

1. In the logon window, verify that the name in the user-name text box is administrator. 

If it is not, enter administrator (deleting any existing user name). 

2. In the password text box, enter administrator (the default installation password), 

unless you have already changed the password from the default. In that case, enter the 

site-specific password. 

3. Click OK. 

The Welcome to Windows 2000 screen appears on the desktop. 

11.15.2. Logging On to the Windows NT Workstation as the 

Administrator 

Whenever you restart or power on the SPO workstation during installation, if the 

workstation is running Windows NT, the Windows NT logo appears and you are prompted 

to press Ctrl-Alt-Del to log on. Take the following steps to log on: 

Notes: 


• If the SPO workstation is part of a domain, you must also enter a domain name. 





2. Enter the following information on that screen: 




d. Click OK. 

The Welcome to Windows NT screen appears on the Windows NT desktop. 

11.15.3. Changing the Default Windows Password 

Caution 

To prevent unauthorized access to the SPO workstation following initial installation, 

the site must change the default password (administrator) to a different password. 

After you complete the installation of Windows on the workstation, change the default 

password as follows: 

Note: The procedure for changing the password may vary slightly depending on your 

version of Windows. The basic procedure remains the same, and variations 

should be self-explanatory. 

1. Log on as the administrator (11.14.1 or 11.14.2). 

2. After logging on, press Ctrl-Alt-Del. 

A Windows security dialogue box appears. 

3. Click Change Password. 

A Change Password dialogue box appears. 

4. In the Old Password text box, enter the present password (administrator). 

5. Tab to the New Password text box and enter the new (site-specific) password. 

6. Tab to Confirm New Password and reenter the new password. 

7. Click OK. 

A dialogue box appears confirming that your password has been changed. 

8. Click OK 


Section 12 

Configuring Intel Nodes for Monitoring 

by SPO 

Follow these steps to configure the Intel nodes of the ClearPath IX system so they can be 

monitored by SPO Basic Edition: 

1. If your SPO workstation is a PC running XVision, log on to the workstation as 

described in 11.14. 

2. Start the Single Point Configuration routine (12.1). 

3. Customize the SPO Basic Edition configuration (12.2). 

4. Configure and install the UNIX Resource Monitor (URM) agent on the SPO server and 

each UnixWare Intel node (12.3). 

5. Transfer the SPO Windows agent to each Windows 2000 and Windows NT Intel node 

(12.4). 

6. Configure each Windows NT Intel node for monitoring and control by ControlIT (if 

applicable) (12.5). 

7. Exit from the Single Point Configuration routine (12.6) and log on to SPO Basic 

Edition as the operator (12.7). 

8. For each Windows 2000 and Windows NT node, install the SPO Windows agent (12.8). 

9. For each UnixWare node, run the URM agent installation and console output 

redirection script (12.9). 

12.1. Starting the Single Point Configuration 

Routine 

To install and configure agents, you must log on as the administrator and use the Single 

Point Configuration routine. 

Start the Single Point Configuration routine as follows: 

1. If you are not currently logged on, power on or restart the SPO workstation. 

2. If your SPO workstation is a Windows NT PC, log on as described in 11.14, then click 

Start, Programs, XVision, then XVision server. 

The SPO server’s UnixWare graphical user interface (GUI) logon screen appears. 


Configuring Intel Nodes for Monitoring by SPO 

3. Log on as the Single Point administrator as follows: 



c. Type unisys1234 (the default installation password) and press Enter. 

4. 

A window for selecting a configuration appears. 

Select one of the supplied configurations that most closely match the ClearPath 

configuration. For example, 

1_INT_6.1CP One OS 2200 partition, one Windows 2000 or Windows NT 

Intel node 

2_1UNIX_6.1CP 

Click OK to edit. 

Two OS 2200 partitions, one UNIX Intel node 

After you select a configuration, the Single Point Configuration routine main menu and the 

TopCluster diagram open. Continue by customizing the configuration (12.2). 

12.2. Creating a Custom SPO Basic Edition 

Configuration 

After selecting a supplied configuration that is similar to the site’s existing ClearPath 

configuration (12.1), you must create a new configuration to use the node names that have 

been chosen during the ClearPath installation. The TopCluster diagram and the main 

menu of the Single Point Configuration routine should still be open. 

Follow these steps to customize the configuration: 

1. Save the current configuration under a new name, as follows: 

a. On the main menu bar, click File. A drop-down menu appears. 

b. In the drop-down menu, click Save Configuration As. 

A dialogue box appears, asking you to enter the name of the new configuration. 

c. Enter a name (for example, the customer’s name) and click OK. 

The title bar of the main menu now shows that you are editing the new configuration. 

2. To change the name of a node or 2200 console, follow these steps: 

a. On the TopCluster menu bar, click Edit and select the menu item for the category 

of node or console you wish to rename (for instance, OS 2200 Consoles). 

An Edit window appears. 

b. In the name column for the category you selected, click the name of the node or 

console you wish to change. 

A dialogue window appears, asking you to enter a new name. 

c. Enter the new name and click OK. 

Note: The name is case-sensitive. 



d. Repeat steps b and c for all names of the current category that you wish to change. 

e. When you have finished changing names for one category, click Window on the 

Windows menu bar, then select Close. 

f. Repeat steps a through e for all node and console categories that have names you 

wish to change. 

3. If nodes or consoles that are unused or not physically present are named in the 

configuration, delete them as follows: 

a. On the TopCluster menu bar, click Delete, then select the appropriate menu item 

for the node or console you wish to remove from the configuration. 

A dialogue window appears, asking which systems or consoles you wish to delete. 

b. Click (highlight) the names of the systems or consoles to be deleted. 

c. Click OK. 

4. Verify the configuration by clicking File on the main menu bar of the configuration 

routine, then select Verify Configuration. 

A Configuration Verification Results window appears, listing the results of your 

changes. 

If you find errors in the Results window, correct them by repeating the appropriate 

steps above to rename incorrect nodes or consoles, delete unused ones, or update the 

hosts file on the SPO server (10.3.3). After you resolve the errors, repeat the 

verification process (step 4). 

If there are no errors, a window appears, asking if you wish to verify network 

connectivity. Click Yes if you wish the SPO server to ping each of the consoles and 

Intel nodes in the configuration. Click No to skip this test. 

5. To save the changes to the configuration, click File on the main menu bar of the 

configuration routine, then select Save Configuration from the drop-down menu. 

A dialogue window appears, asking if you want to perform configuration verification. 

6. Click No. 

The configuration is saved. 

You must repeat this procedure for each Single Point configuration the site will use. To 

select another configuration, click File on the main menu bar, then click Select 

Configuration in the drop-down menu that appears. For this release, SPO Basic Edition 

configurations are named as follows: 

x_yUNIX_zNT_level 

where: 

x is the number of 2200 nodes. 

y is the number of UnixWare nodes. 

z is the number of Windows 2000 and Windows NT nodes. 

level is the SPO Basic Edition release level. 



For example, a configuration named 2_2UNIX_2NT_6.3CP is a configuration for managing 

a ClearPath IX server with two OS 2200 nodes, two UnixWare nodes, and two Windows 

2000 or Windows NT nodes. 

Continue by configuring and installing URM agents, as described in 12.3. 

12.3. Configuring and Installing the URM Agent for 

the SPO Server and UnixWare Nodes 

After starting the configuration routine, configure the URM agent for the SPO server and 

each UnixWare node (if applicable) as follows: 

1. On the Configuration routine's main menu bar, click Application, then select Maintain 

Unix Agents from the drop-down menu. 

After a brief wait, the Maintain UNIX Agents (Figure 12–1) and UNIX Resource 

Monitor Policies (Figure 12–2) windows appear. Each node is identified by the node's 

alias (SPO_Server for the SPO server and CP_UNIXx for the UnixWare nodes) in the 

Maintain UNIX Agents window. 

File Execute Help 

System 

Name 

Console 

Heartbeat 

Period 

URM 

Enabled? URM 

Policy 

URM 

Policy 

Current? 

Maintain UNIX Agents 

Date & Time Agents 

Installed or Updated 

Security 

Scheme 

Host 

Network 

Name 

Install 

Directory 

Root 

Userid Configurations 

SPO_Server - yes default - - 

Access Allowed SPO_Server /opt/SPO-agent root 1_1NT... 

CP_UNIX x - yes default - - 

Alays Ask CP_UNIX x /opt/SPO-agent root 1_1NT... 

Window File Help 

Policy 

Name 

Sample 

Period 

Heartbeat 

Period 

Figure 12–1. Maintain UNIX Agents Window 

Monitored 

Classes 

UNIX Resource Monitor Policies 

Logged 

Data 

Critical 

Processes 

Daemon 

Processes 

Agent 

Directory 

default 300 120 UNIXHost, ... CPU, ... cron - - yes 

Figure 12–2. URM Policies Window 

Use 

API? 



2. In the Maintain UNIX Agents window, select the default URM policy and security 

scheme for each node (system) as follows: 

• For the SPO server (SPO_Server), take the following steps: 

− Click the hyphen (-) in the URM Policy column. 

A dialogue window appears. 

− In the dialogue window, click default, then click OK. 

The word default appears in the URM Policy column for SPO_server. 

• For each UnixWare node (CP_UNIXx), take the following steps (skip these steps if 

you have no UnixWare node): 

− Click the hyphen (-) in the URM Policy column. 


− In the dialogue window, click default, then click OK. 

The word default appears in the URM Policy column for CP_UNIXx. 

− Click Access Allowed in the Security Scheme column for CP_UNIXx. 


− In the dialogue window, click Always Ask, then click OK. 

Repeat these steps for each UnixWare node. 

Figure 12–1 shows how the window should look if these steps are performed for both 

the SPO server and a single UnixWare node. 

3. In the Maintain UNIX Agents window, select Execute, then Install. 

A dialogue window appears identifying systems on which the agents can be installed. 

4. Click SPO_Server, then click each of the CP_UNIXx systems. 

They appear in the lower half of the window. 

5. Click OK. Messages for the SPO server and UnixWare nodes appear as follows (the 

order may vary): 

• For the SPO server, a message indicates that the URM agent was installed 

successfully. Click Continue to proceed. 

• For each UnixWare node, a dialogue box asks for the root password for that 

system. Respond as follows: 

a. Enter the root password. (Your typing is not displayed.) 

b. Press Enter. 

A message indicates that the URM agent was installed successfully. 

c. Click Continue to proceed. 

6. Verify that the URM agent on the SPO server is running as follows: 

a. At the SPO workstation, open a new X terminal window session by positioning the 

cursor on the screen background, clicking the right mouse button, selecting New 

Window, and then releasing the mouse button. 



b. In the new window, enter the following command: 

ps -ef | grep urm.loop 

7. Check the right half of the listing produced by that command to ensure that the URM 

agent is running. This is indicated by the following process being listed: 

sh ./urm.loop 

8. If the URM agent is not running, log on as superuser (10.15.3) at the SPO server using 

the su command and enter the following command: 

/opt/SPO-agent/spo_urm start 

Then repeat steps 6 and 7. 

9. Once you verify that the URM agent is running, select the File option, then select Exit 

in the Maintain UNIX Agents window. 

If you have one or more Windows 2000 or Windows NT nodes, you now must transfer the 

SPO Windows agent to each of these nodes (12.4). Otherwise, you can exit from the Single 

Point Configuration routine and log on as the operator as described in 12.6 and 12.7. 

12.4. Transferring the SPO Windows Agent 

Take the following steps to transfer the SPO Windows Agent to each Windows 2000 and 

Windows NT node and the PC being used as a SPO workstation. 

Note: If there is more than one PC being used as a SPO workstation, it is not 

necessary to install the SPO Windows agent on all of them. Install the SPO 

Windows agent on each Windows 2000 and Windows NT node and the first SPO 

workstation. 

1. On the Single Point Configuration routine main menu bar, click Application. 

A menu of possible applications appears. 

2. Click the Maintain Windows Software Interfaces menu entry, and then select Transfer 

Software. 

A dialogue box asks you to select a Windows system. 

3. Click the name of the Windows system to highlight it, then click OK. 

A dialogue box asks you to enter the name of a valid FTP user or select Unknown for 

Anonymous FTP. 

4. Click Unknown. 

The agent software transfer is initiated, and a window appears stating that the transfer 

succeeded. 


Note: If the agent software transfer fails, an explanation appears. The message is 

recorded in two logs (NTINSTALL and host-name, where host-name is the host 

name of the Windows node) that you can view using the Log View window from 

the SPO Console menu. 



Continue by configuring the Windows server nodes for ControlIT (12.5). 

12.5. Configuring Windows Intel Nodes for ControlIT 

Perform this procedure for each Windows 2000 and Windows NT Intel node, so that 

ControlIT can monitor and control the nodes. In this procedure, it is assumed that you are 

still logged on to the Single Point Configuration routine. 

1. In the TopCluster window displayed by the configuration routine, click Edit, then 

Windows Systems. 

A table listing each Windows 2000 and Windows NT server node appears. 

2. For each of the Windows NT server nodes, do the following: 

a. Click Program. A dialogue window appears. 

b. Select Remotely Possible/32. (This also works for ControlIT.) 

c. Click OK. 

Note: Do not perform this procedure (step 2) for the SPO workstation cp_ws (PC 

running Windows NT Workstation). 

3. Close the Edit Windows Systems window. 

4. On the configuration routine's main menu bar, click File, then select Save from the 

drop-down menu that appears. 

A window asks whether you want to perform configuration verification. 

5. Click Yes. 

When configuration verification is done, a window asks whether you would like to 

verify network connectivity. 

6. Click Yes. 

A message indicates that network connectivity has been verified. 


After you have performed this procedure for each configuration, continue with the 

procedure in 12.6. 



12.6. Exiting from the Single Point Configuration 

Routine 

Exit from the Single Point Configuration routine as follows: 

1. On the Configuration Routine main menu bar, click File, then select Exit from the 

drop-down menu that appears. 

If you have not previously saved changes to the selected configuration, a dialogue 

window asks whether you want to save the changes you made. 

2. Click Yes. 

A dialogue window asks whether you want to perform configuration verification. 

3. Click Yes. 

When configuration verification is done, a dialogue window asks whether you would 

like to verify network connectivity. 

4. Click Yes. 

A message indicates that network connectivity has been verified. 


The following prompt appears in a window: 

Quit Single Point Configuration Routine? 

OK CANCEL 

6. Click OK. 

A Goodbye window appears. 

7. Click Press to End Session. 

8. Click OK to quit the session. 


12.7. Starting Normal SPO Console Operations 

To start normal operations of SPO Basic Edition, you must first log on as the operator. 

Follow these steps: 

1. At the SPO workstation, in the UnixWare logon screen 

a. Type spoper (the SPO operator user-id). 


c. Type unisys1234 (the default installation password) and press Enter. 

You are prompted to select a Single Point configuration. 



2. Select a configuration for operations. For this release, SPO Basic Edition 

configurations are named as follows: 

x_yUNIX_zNT_level 

where: 

x is the number of 2200 nodes. 

y is the number of UnixWare nodes. 

z is the number of Windows 2000 and Windows NT nodes. 

level is the SPO Basic Edition release level. 

For example, a configuration named 2_2UNIX_2NT_6.3CP is a configuration for managing 

a ClearPath IX server with two OS 2200 nodes, two UnixWare nodes, and two Windows 

2000 or Windows NT nodes. 

After you select a configuration, the following windows open: 

• The SPO Basic Edition main menu (Figure 12–3) includes an Alarms icon that turns red 

whenever an alarm is raised against any node of the ClearPath IX server. 

• The TopCluster window (Figure 12–4) contains icons representing the SPO server, the 

Windows 2000, Windows NT, and UnixWare nodes, and each OS 2200 partition and 

console. Each icon turns red whenever an alarm is raised against the corresponding 

node. You can click an icon to open a console session. 

• The Alarms window describes each alarm currently raised against the ClearPath IX 

server. Click the text of any alarm for more information about the alarm. 

After those windows open, you can click the appropriate Windows 2000, Windows NT, or 

UnixWare node in the TopCluster window to open a session to that node to 

• Install the SPO Windows agent (12.8) that was previously copied to each Windows 

2000 and Windows NT node. 

• Redirect console output from the UnixWare node to the SPO server (12.9). 

You can also start Single Point Status and activate the Single Point Autoaction Message 

System (SP-AMS) database as described in the following documents: 

• ClearPath HMP IX Series Operations Guide (provides a brief overview of SPO Basic 

Edition software operations) 

• Single Point Operations Basic Edition Administration and Operations Overview 

• Single Point Operations Console User Guide 

• Single Point Status Operations Guide 

SPO Console documentation can be viewed online. From the SPO workstation select Start 

> Programs > SPO HMP Console CD-ROM Library > CD-ROM Library. 



Figure 12–3. SPO Basic Edition Main Menu 

Figure 12–4. SPO Basic Edition TopCluster Window (Four OS 2200 Nodes, Four Windows NT 

Intel Nodes, and a Single UnixWare Node) 



12.8. Installing the SPO Windows Agent 

To fully enable control of each Windows 2000 and Windows NT node by SPO Basic 

Edition, you must install the SPO Windows Agent that you previously transferred to each 

node (12.4). 

Note: In this procedure, it is assumed that you have already logged on to SPO Basic 

Edition as the operator (12.7). 

The procedure is as follows: 

1. In the TopCluster window of SPO Basic Edition, click the desired Windows 2000 or 

Windows NT node icon. 

The Windows desktop for the selected node takes over the SPO workstation screen. 

2. Switch to viewer mode, then click Start, Programs, Command Prompt. 


3. Type the following command, then press Enter to change to the installation directory 

(if you are not already in that directory): 

cd \InetPub\ftproot\temp 

4. Enter the following command to start the installation program: 

spinst 

When the command prompt returns, the installation is complete. 

5. Type exit and press Enter. 

6. Press Ctrl-Shift-Esc to exit from the Windows 2000 or Windows NT node and return to 

SPO Basic Edition control. 



12.9. Running the Console Output Redirection 

Script 

Cautions 

1. For each UnixWare node, create an emergency recovery diskette that you can 

use to reboot the node if the console redirection procedure should fail (8.13). 

2. SPO daemons must be running on the SPO server in order to redirect console 

output as described in this subsection. See 10.16 if they are not running. 

3. Before running the URM installation script, verify in the TopCluster window that 

the SPO server, the UnixWare node, and the system console icons are green. 

Green icons indicate that the SPO server has a normal connection to those 

components. If the icons have not turned green within about 30 seconds of 

starting normal operations, ensure that all SPO daemons are running by 

stopping and restarting them as described in 10.16. 

The script described in this section can handle both manual installation of the URM agent 

and console output redirection. However, only the redirection feature of this script is 

actually used. (See step 7 below.) 

To use this procedure, SPO Console sites must have Console 4.3 or higher installed in the 

default location. 

If the TopCluster window did not appear when normal SPO Basic Edition operations were 

started, click Displays on the main menu bar, then click Cluster in the drop-down menu 

that appears. 

After starting SPO Basic Edition operations (12.7), run the script to install URM agent files 

on each UnixWare node and to redirect console output from the node to the SPO server so 

that the node can be monitored by SPO Basic Edition. 

The procedure, which you must do for each UnixWare node, is as follows: 

1. In the TopCluster diagram of SPO Console, click the icon of the UnixWare node 

(CP_UNIXx) to open a console session. You must open a SPO session to monitor the 

node because the node will not boot if a process is not monitoring the serial port. 

2. At the system console of the UnixWare node, log on to the node as the root user (userid 

root) if you are not already logged on, as follows: 

a. Double-click Applications, then Terminal. 

The dollar sign ($) prompt appears. 

b. Type the su command, then press Enter. 

You are prompted to enter a password. 



c. Enter unisys12, the default installation password. 

The UnixWare root prompt (#) appears. 

3. Type the following command and press Enter to install and start the script that 

redirects console output: 

sh /usr/lbin/CP_urm.inst 

Messages appear and you are prompted to enter the IP address of the SPO server. 

You must be root to execute this script. 

This script installs the SPO/HMP UNIX Resource Monitor agent, 

and configures the console re-direction to port com1. 

Please enter the SPO system IP Address. 

IP Addresses are written as four decimal integers, 

separated by decimal points and no spaces (e.g. 128.10.2.70). 

The SPO IP Address is? : 

4. Enter the SPO server IP address from Table 2–2. A prompt asks for the SPO server 

name. 

Please enter the SPO Server node name. 

This is typically the name returned when the uname -n 

command is entered on the SPO Server. 

The SPO Server node name is? : 

5. Enter the SPO server name from Table 2–2. A message indicates that the system name 

and IP address of the SPO server are being added to the hosts file at the UnixWare 

node. 

Adding the following line to /etc/hosts: 

xxx.xxx.xxx.xxx name SPO_Server # SPO 

That message is followed by a prompt for the SPO Basic Edition representation to be 

used to identify the UnixWare node. 

SPO/HMP Console monitors up to four UNIX based systems. These 

systems are represented with the following names: 

1) CP_UNIX1 




Please select the SPO representation for this system: 

6. Type the number (or the name if you wish) of the UnixWare node being configured, 




Messages indicate that the name is added as an alias for the UnixWare node in the 

hosts file. 

Changing line in /etc/hosts from: 

xxx.xxx.xxx.xxx systemname 

to: 

xxx.xxx.xxx.xxx systemname CP_UNIXx # Alias needed by URM 

Those messages are followed by a prompt asking whether you wish to install the URM 

agent. 

Do you wish to install the UNIX Resource Monitor (URM) at this time? 

Please enter y or n: 

7. Type N,then press Enter. 

A prompt asks whether you wish to redirect the console output. 

Do you wish to perform console re-direction to port com1 at this time? 

Please enter y or n: 


Messages indicate that the console output is being redirected to the serial port. 

Configuring console to use com1 as the console device. 

The change will take effect at the next system reboot. 

To reverse this change, remove or comment out the line that starts 

with "console=" in the file /stand/boot. 

9. Shut down the system by entering the following: 

shutdown -i6 

Shutdown messages now appear. If you receive a prompt asking if you want to 

continue, type Y in response and press Enter. 

10. When the UnixWare node reboots, the first part of the boot operation displays at the 

monitor concentrator, then the console output is redirected to the SPO workstation. 

You can observe that in the CP_UNIXx session that you started in step 1. 

Some messages are mirrored at the monitor concentrator, but the CP_UNIXx session 

on the SPO workstation is the only console session you can interact with. 

If the UnixWare node does not successfully reboot, see the procedures for using the 

emergency recovery diskette in 8.13. 

To remove the console redirection changes and restore the UnixWare node to normal 

console operation, do the following: 

1. Remove or comment out the line that starts with “console=” in the /stand/boot file. 

2. On UnixWare 7 systems, remove the following file: 

/etc/dt/config/Xservers 


Section 13 

Installing the Basic OS 2200 IOE 

Fast-load tapes have been created to speed up installation of the OS 2200 Integrated 

Operating Environment (IOE). This section describes installation of the basic OS 2200 

software from the following fast-load tapes: 

• Tape HMP-FLD (“first load”) contains products that must be installed before migrating 

to the new Exec . 

• Tape HMP-OE1 contains the basic OS 2200 IOE software that typically can be installed 

without change at a site and which should not need to be reinstalled. HMP-OE1 is 

either a single tape or a two-tape set. 

The procedures described in this section take about 2 hours. 

Software from fast-load tape HMP-OE1 is the minimum set of 2200 node software required 

to achieve hardware ready for use (RFU). Section 15 describes how to install the 

remaining OS 2200 IOE products that are on fast-load tapes HMP-OE2 and HMP-UDS3. 

These are not needed to achieve hardware RFU. 

Note: Not all of the ClearPath IOE products are present on the fast-load tapes. For 

detailed information about fast-load tape contents, refer to the ClearPath HMP 

IX and 2200 Systems Software Planning and Migration Overview. 

Once products have been installed from a fast-load tape, they need not be reinstalled from 

a package tape unless the site wishes to customize the installation for some reason. 

The runstream that installs products from fast-load tapes also registers the products with 

SOLAR. 

This section describes what you need to perform these procedures: 

1. Read-and-reply message format (13.1) 

2. How to perform an initial boot (13.2) 

3. How to install IOE products from fast-load tape HMP-FLD (13.3) 

4. How to establish the contracted performance level for IX6000, IX5000, and IX4800 

Series servers (13.4) 

5. How to install IOE products from fast-load tape HMP-OE1 (13.5) 

Upon completion of procedures in this section, you must verify that the hardware is ready 

for use by testing the communications links (Section 14). 



Table 13–1 lists information or installation media you need during installation. Obtain the 

information or media before beginning. Only the procedures for which you need 

information or media are listed. 

Table 13–1. OS 2200 Installation Checklist 


13.2. Performing the Initial Boot 

Media needed: Boot tape HMP-BOOT 

13.2.1. Initial Boot Steps If Boot Partition Is Not Activated 


If you need to activate a partition, you must enter the partition name to be activated. 

Partition name ____________________________ 

13.3. Installing Products from Tape HMP-FLD 

Media needed: 

“First-Load” fast-load tape—labeled “HMP-FLD” 

13.4. Establishing the Performance Level (IX6000, IX5000, and IX4800 Series Servers) 

Media needed: Exec key tape—labeled “Software Controlled Performance Key Tape” (applicable to 

IX6000, IX5000, and IX4800 Series servers only) 

13.5. Installing Products from Tape HMP-OE1 

Media needed: 

Basic fast-load tape—labeled “HMP-OE1” (may be a single tape or a two-tape set) 


Reel number for HMP-OE1 tape 1 ___________________ 

Reel numbers can be any character string up to 6 characters in length. 

Reel number for HMP-OE1 tape 2 of 2 ___________________ 

This is applicable only if HMP-OE1 is a two-tape set. 

13.1. Read-and-Reply Message Format 

Replies to outstanding OS 2200 read-and-reply console messages must begin with the readand-reply 

message number followed by a space. The following example illustrates a 

typical read-and-reply message and how you would respond. 

Ø Enter reel number 



Your reply begins with the same message number and a space, followed by the answer to 

the request (in this example, the reel number): 

Ø CPOE1A 

Note that the reel number is only 6 characters long. Some ClearPath IX tape names are 

longer than 6 characters (for example, HMP-OE1)—you can enter only 6 characters in 

response to a prompt for a reel number. 

13.2. Performing the Initial Boot 

Caution 

The initial boot with jump key 13 set destroys all files on fixed mass storage. Do 

not perform an initial boot except when initially setting up the 2200 node. 

Before you can install OS 2200 software products, you must perform an initial boot to load 

and activate the Exec from the boot tape. The first steps you take to perform the boot 

depend on the current state of the 2200 node as follows: 

• Steps to take if the partition you want to boot is not activated (13.2.1) 

• Steps to take if the partition you want to boot already is up and the Exec is running 

(13.2.2) 

Do the procedure in either 13.2.1 or 13.2.2 to prepare for the boot, then complete the boot 

process as described in 13.2.3. 

Note: Either the command line or the menu bar can be used to perform the steps 

described. To toggle between the command line and menu bar, press the Esc 

key. 

13.2.1. Initial Boot Steps If Boot Partition Is Not Activated 

If you do not have an activated boot partition, take the following steps to activate one: 

1. Press F5 to access the SCF System Control display session at the master system 

console. 

2. If the cursor is not on the command line, press the Esc key to bring the cursor to the 

command line. 

3. Type the following command and press Enter to activate the partition: 

AP xxxx 

where xxxx is the partition name to be used to boot the system. 

4. Proceed to 13.2.3. 



13.2.2. Initial Boot Steps If Partition Is Up and Exec Is Running 

Caution 

To prevent loss of data, do not use a halt partition (hp) command to stop the Exec. 

Use the procedures and commands described in this subsection. 

If the partition you wish to use is already activated and the Exec is running, take these 

steps to halt the Exec and confirm that it is halted: 

1. At an Exec logical console for the running partition, press F4 to display the System 

Operations Session. 

2. Enter the following keyin to set jump key 3 to inhibit autorecovery: 

sj 3 

3. Enter the following keyin to halt the Exec: 

$! 

Wait for the partition to change from running to stopped. 

4. Press F5 to display the System Control session. A list of activated partitions appears in 

the upper right corner of the display. 

5. Press the function key (for example, F7) identified in the display for the partition. 

That shows the partition’s Control session. 

6. Proceed to 13.2.3. 

13.2.3. Completing the Boot Procedure 

After preparing the boot partition as described in 13.2.1 or 13.2.2, take the following steps 

at the master console session to perform the initial boot: 

1. Enter the following system control facility (SCF) command to set the boot type to 

tape: 

st tape 

2. Set the tape drive name from which you will be booting with the following SCF 

command: 

std tape-device-name 

where tape-device-name is the name of a tape device in the partition. 

3. Enter the following command to specify the name of the Disk Resident System (DRS) 

disk to which the Exec will be written: 

sd diskname 

where diskname is the name of the DRS disk device in the partition. 

4. Clear all jump keys with the following keyin: 

cj all 



5. Set jump keys for library load (jump key 4) and initialization (jump key 13) as follows: 

sj 4,13 

Whenever jump key 13 is set, a prompt appears with a field for specifying the 

reinitialize option. 

6. In the field that appears, set the reinitialize option by typing the following entry and 

pressing Enter twice. 

destroyfiles 

7. Load the tape HMP-BOOT in the tape drive specified in step 2. 

8. Start the partition by entering the following SCF command: 

sp 

The Start Partition command initializes the partition and performs an initial program 

load of the partition. 

9. Press the F4 key to change to the System Operations session. The following message 

is displayed: 

n MODIFY CONFIG, THEN ANSWER: DONE 

10. Before continuing the boot process, determine the current state of peripheral devices 

by entering appropriate facility status (fs) keyins. For example, check the status of all 

mass storage devices with the following keyin: 

fs,ms 

You can use this keyin to display only disks that are up: 

fs,adisk 

11. Use the UP or DN keyin to set devices to the state you want for the partition. 

12. When done, end modification of the configuration by entering the following: 

n done 

where n is the number of the MODIFY CONFIG message requiring a response. 

In response to that message, the following message appears: 

n ARE YOU SURE YOU WANT JK 13 SET? ANSWER Y OR N 

13. Enter Y to confirm that you want to perform an initial boot: 

n Y 

A messages appears indicating the number of fixed mass storage disks that are up: 

n FIXED MS DEVICES= m - CONTINUE? YN 

14. Answer yes (Y). 

n Y 

A message solicits down keyins. You must bring down disks that should not be up. 

n ENTER LOCAL DOWN PACK KEYINS - ANS GO 

15. Enter keyins to down devices as needed. (If no device must be downed, continue with 

the next step.) For example, 



dn devname 

Caution 

Once you continue with the boot, you cannot bring down any fixed mass storage 

devices without a reboot. Be sure the correct disks are up before proceeding. 

16. Enter the following to continue with the boot: 

n go 

You are prompted to enter the security officer user-id. 

n ENTER 12-CHARACTER SECURITY OFFICER ID 

17. Enter security as the default security officer user-id as follows: 

n security 

You are prompted to enter the master account number. 

n ENTER MASTER ACCOUNT 

18. Enter 0 (zero) as the master account number. 

n 0 

Several messages are displayed. Initial boot is finished when the following message 

appears: 

SYS FIN 

The run MSCPRT will start after SYS FIN. This is a background service run and can be 

left active. 

Continue installation with the procedures in 13.3. 

13.3. Installing Products from Tape HMP-FLD 

Once OS 2200 is initialized, take the following steps to install the first-load tape labeled 

HMP-FLD: 

1. Enter the following command to start the installation runstream: 

ST INSTALLFLD 

You are prompted to enter the reel number for the reel or reels you are loading: 

INSFLD START 

n INSTALLFLD: Enter reel number 



2. Because the tape or tapes are unlabeled, you can enter any reel number. For example, 

for the “first-load” fast-load tape, enter the following to assign the tape as a temporary 

file, indicate that it is unlabeled (TJ), and indicate a cartridge tape device: 

n HMPFLD,TJ,type 

where type is the assign mnemonic (HICL, HIC51, etc.). 

The following messages appear: 

LOAD HMPFLD T40A12 TAPE$ - 1 INSFLD 

(LOAD HMPFLD )(ANY UNASSIGNED CT0899 ) 

n ANSWER WITH REEL NUMBER ON T40A12 E,REEL 

3. Enter the reel number of the tape reel to confirm that the unlabeled tape reel you 

mounted is the one you intended to mount: 

n HMPFLD 

Messages appear indicating that the installation has started. 

A message indicates that SYS$DATA$ has no SCP Exec key: 

SYS$DATA$ exists without SCP Exec key 

The INSFLD FIN message indicates that the runstream has finished. 

The HMP-FLD tape installs the following products: CMS 1100, COMUS, FURPUR, 

I18NLIB, PCFP, PERFEV, ROLRUNS, and SOLAR. 

IX6000, IX5000, or IX4800 Series server sites now must establish the contracted Software 

Controlled Performance level as described in 13.4. All sites must verify that the hardware 

is ready for use by performing the communication tests described in Section 14. 

13.4. Establishing the Performance Level (IX6000, 

IX5000, and IX4800 Servers Only) 

For an IX6000, IX5000, or IX4800 server, you should establish the Software Controlled 

Performance (SCP) contracted performance level as soon as possible after SOLAR is 

installed (refer to ClearPath HMP IX Series and 2200 Series Software Planning and 

Migration Overview for an overview of SCP). 

The 2200 node runs at 100 percent performance until SOLAR creates the SYS$*DATA$ file 

during installation. After that, until you register your contracted performance level, it runs 

at the default performance level and the default of one IP. A console message is issued 

every 5-minute time-and-date interval stating that the system is running with the SCP 

default performance value. 

Using SOLAR, you must register the Exec key tape included in the system packaging 

(labeled “System Controlled Performance Key Tape”). Optionally, a new or replacement 

Exec key may be provided in a file for registering from disk. 

The Exec key tape or file contains encrypted fields for various SCP attributes. The Exec 

key tape or file is valid only for the system with a cabinet serial number that matches the 



Exec key serial number. Both the cabinet and Exec key tape have labels identifying the 

Manufacturing Cabinet Number (MCN). 

The process for registering the tape is as follows: 

Note: The following procedure is valid only if you are establishing the performance 

level immediately following installation of the first-load tape labeled HMP-FLD 

and have used the boot tape labeled HMP-BOOT. If you used a different boot 

tape or established site-specific security, then you need to start runstreams with 

a user-id/password and account number assigned by the site. 

1. Start the runstream for registering the key tape by entering the following command: 

ST SYS$LIB$*SOLAR.REGISTERPKG,,,0/SECURITY 

You are prompted to enter a password. 

2. Type the password SECURI as follows, then press Enter: 

n SECURI 


REGPKG START 

n Register package from or DISK? 

n 

3. Press Enter to register from tape. A prompt asks for entry of the reel number from 

which the key is to be installed. 

n Enter reel number 

n SCPKEY,TJ,type 

4. Because the tape is unlabeled, enter any reel number. Also enter the parameters to 

indicate that the tape is to be assigned as a temporary unlabeled file (TJ) and to 

indicate the type of the cartridge device on which the tape is to be mounted (for 

example, HICL or HIC51). 

The following message is displayed: 


n 

5. Press Enter to select the default of and mount the key tape in the specified 

drive. Loading begins, and you are prompted to verify that the unlabeled tape you 

mounted is the correct reel. 

LOAD SCPKEY T40Z0 NORING PP$TAPE - 1 REGPKG 

(LOAD SCPKEY )(ANY UNASSIGNED CT0899 ) 

n ANSWER WITH REEL NO ON T40Z0 E,REEL 

n SCPKEY 

The following messages appear indicating that the key tape is registered: 

REGPKG FIN 

Model: IX6802-88 Key MCN: 00001001 IPs: 8 Performance: 100% 

Note: The model number message does not appear if an Exec key tape or file 

registration problem is encountered such as a registration number that does 

not match a previous installation or a registration expiration date that has 

passed. 



You only need to register the Exec key tape or file once because the data is stored in the 

SOLAR SYS$*DATA$ file for recovery boots and a backup copy is written by the Exec to 

the disk-resident system (DRS) device. The SCP data recovery first tries the SYS$*DATA$ 

file and alternately the DRS device. The DRS device SCP data is used if a SYS$*DATA$ file 

does not exist or an Exec key tape was never registered. 

Continue product installation with the procedure in 13.5. 

13.5. Installing Products from Tape HMP-OE1 

Notes: 

• Although Interactive Processing Facility (IPF 1100) is installed from fast-load tape 

HMP-OE1, it cannot be used in full-screen mode until Display Processing System 

(DPS 2200) is installed. If the site needs to use IPF 1100 in full-screen mode, DPS 

2200 should be installed from either fast-load tape HMP-OE2 or package tape 

HMP12 (see Section 15) after hardware RFU. 

• During installation of products from HMP-OE1, you can ignore warning messages 

relating to installation of an IPF component at this time. The Interactive 

Processing Facility (IPF 1100) can be configured after installation. Configuration 

instructions are in the IPF 1100 Administration Guide. 

• The IOE products on tape HMP-OE1 are installed in default mode. 

Follow these steps to install the IOE products on tape HMP-OE1: 


ST INSTALLIOE 

2. You are prompted to enter the reel number for the reel or reels you are loading: 

INSIOE START 

n INSTALLIOE: Enter reel number 

3. Because the tape or tapes are unlabeled, you can enter any reel number. For example, 

for the HMP-OE1 fast-load tape enter the following to assign the tape as a temporary 

file, indicate that it is unlabeled (TJ), and indicate a cartridge tape device: 

n HMPOE1,TJ,type 

where type is, for example, HICL or HIC51. 

Note: If tape HMP-OE1 is a two-tape set, you must enter two reel numbers 

separated by a slash (for example, CPOE1A/CPOE1B,TJ,HICL). 


LOAD HMPOE1 T40A12 TAPE$ - 1 INSIOE 

(LOAD HMPOE1 )(ANY UNASSIGNED CT0899 ) 

n ANSWER WITH REEL NUMBER ON T40A12 E,REEL 



4. Enter the reel number of the tape reel to confirm that the unlabeled tape reel you 

mounted is the one you intended to mount: 

n HMPOE1 

5. Messages appear indicating that the installation has started. The INSIOE FIN message 

indicates that the runstream has finished. 


Section 14 

Verifying the Interconnects and 

Achieving Hardware RFU 

Following installation of OS 2200 software from fast-load tape HMP-OE1, you must verify 

that the OS 2200 nodes and each Intel node can communicate via the internal interconnect 

(14.1). 

Table 14–1 lists procedures that require you to have information or installation media 

available at the time of installation. Obtain that information or media before beginning. 

With this checklist completed and all installation software media readily available, the 

procedures in this section take 3 hours. 

Table 14–1. Checklist for Verifying Interconnects and Achieving RFU 


14.1. Verifying Interconnect Communications 

Media needed: 

Applicable tape containing microcode and the PING test for verifying communications as follows: 

• Model IX4400 

CEC500 tape (minimum level of 1R8 is required, except when the 2200 node is configured 

for resilient partitions, then a minimum level of 1R11 is required to execute the PING test for 

the second 2200 node) 

Host LAN Controller-2 (HLC-2) microcode on cartridge tape. Found in the HLC2-FMK package 

that comes with the HLC-2. 

• Model IX5000 Series or IX4800 server 

CC6000 tape or CC3000 tape. CC6000 supersedes CC3000 for all configurations at 

Plateau 2.0. At Plateau 2.0 a minimum CC6000 level of 2R1 is required. Below Plateau 2.0, 

a minimum CC3000 level of 1R1 is required, except when the 2200 node is configured for 

resilient partitions, then a minimum level of 1R2 is required to execute the PING test for the 

second 2200 node. 

Channel adapter microcode tape, called FDDI/ETHERNET CA-MCODE 

The Diagnostic Software Peripheral Equipment Routines (DSPER) also should be installed following 

installation of the CEC tape. 

continued 


Verifying the Interconnects and Achieving Hardware RFU 

Table 14–1. Checklist for Verifying Interconnects and Achieving RFU 


14.2.1. Installing HLC-2 Microcode 

Reel number for tape ___________________ 


14.2.2. Installing Channel Adapter Microcode (CSIOP) 



14.3. Installing the CC or CEC Tape 



14.1. Verifying Interconnect Communications 

Here are the steps for verifying interconnect communications between the OS 2200 nodes 

and each Intel node. 

1. Depending on communications controller model, install microcode as follows: 

• For servers with a Host LAN Controller-2 (HLC-2), install microcode as described 

in 14.2.1. 

• For servers with a channel service I/O processor (CSIOP), install channel adapter 

microcode as described in 14.2.2. 

2. Install the CC or CEC tape for verifying communications (14.3). 

3. Install DSPER (14.4). 

4. Bring up a version of CMS 1100 that is adequate for at least the communications test 

(14.5). 

5. Test interconnect communications to determine whether the hardware is ready for use 

(14.6). 

14.2. Installing Microcode 

This subsection describes how to install the microcode for the HLC-2 and the channel 

adapter. 


14.2.1. Installing HLC-2 Microcode 


A cartridge tape containing microcode is included in the HLC2-FMK package that comes 

with the HLC-2. To install the microcode, take the following steps: 

1. Enter the following command at the 2200 node system console: 

ST INSTALLPKG 

A run (run-id INSPKG) starts and asks the following question: 

Install from , DISK, or RSS? 

2. Press Enter to use the tape default. You are prompted to enter the reel number. 

n INSPKG*Enter reel number 

n HLC2M,TJ,type 

3. Because the tape is unlabeled, you can enter any reel number. Also enter the 

parameters to indicate that the tape is to be assigned as a temporary unlabeled file 

(TJ) and to indicate the type of cartridge device on which the tape is to be mounted 

(for example, HICL or HIC51). 

You are asked whether you want to install using default modes. 

n Install default modes? /N 

n N 

4. Type N and press Enter. You are prompted to enter the product name. 

n Enter product name, transmit if complete 

n HLC2-MCODE 

5. Enter the name HLC2-MCODE (found on the tape label) and press Enter. You are 

prompted to enter the product level. 

n Enter product level 

n level 

6. Enter level (where level is the product level identified on the tape label such as 1R1 or 

1R2) and press Enter. You are prompted for the product mode. 

n Enter product mode 

n FDDI 

7. Enter FDDI as the product mode and press Enter. You are again prompted for the 

product name. 


n HLC2-MCODE 

8. Enter the name HLC2-MCODE (found on the tape label) and press Enter. You are 



n level 




n ETHER 



10. Enter ETHER as the product mode and press Enter. You are again prompted for the 

product name. 


11. Press Enter to indicate that you are done. Loading begins, and you are prompted to 

verify that the unlabeled tape you mounted is the correct reel. 

LOAD HLC2M T40Z0 NORING PP$TAPE - 1 INSPKK 

(LOAD HLC2M )(ANY UNASSIGNED CT0899 ) 


n HLC2M 

The following message indicates when the run is finished: 

INSPKG FIN 

When CMS 1100 is started, it detects the new microcode level and automatically loads the 

microcode into the HLC-2. 

14.2.2. Installing Channel Adapter Microcode (CSIOP) 

To enable CSIOP communications, you must install Ethernet and FDDI channel adapter 

(CA) production mode microcode into the CAs. 

To install the microcode from the FDDI/Ethernet CA-MCODE tape, take the following 

steps: 

1. Enter the following command at the 2200 node system console: 

ST INSTALLPKG 

A run (run-id INSPKG) starts and asks the following question: 

n Install from , DISK, or RSS? 

n 



n CACODE,TJ,type 



(TJ) and to indicate the type of the cartridge device on which the tape is to be 

mounted (for example, HICL or HIC51). 



n N 

4. Enter no (N) and press Enter. You are prompted to enter the product name. 


n CA-MCODE 



5. Enter the name CA-MCODE (found on the tape label) and press Enter. You are 



n level 




n FDDI 

7. Enter FDDI as the product mode and press Enter. You are again prompted for the 

product name. 


n CA-MCODE 

8. Enter the name CA-MCODE (found on the tape label) and press Enter. You are 



n level 




n ETHER 

10. Enter ETHER as the product mode and press Enter. You are again prompted for the 

product name. 


n 

11. Press Enter (transmit) to indicate that you are done. A message asks if you want to 

register the INSPKG: 

n INSPKG* Register package also? Y/ 

n 

12. Press Enter (transmit) to accept the default. Loading begins, and you are prompted to 

verify that the unlabeled tape you mounted is the correct reel. 

LOAD CACODE T40Z0 NORING PP$TAPE - 1 INSPKK 

(LOAD CACODE )(ANY UNASSIGNED CT0899 ) 


n CACODE 

The following console message indicates when the run is finished. 

INSPKG FIN 

When CMS 1100 is started, it detects the new microcode level and automatically loads the 

microcode into the CA. 



14.3. Installing the CC or CEC Tape 

The CC or CEC tape provided with the plateau contains hardware diagnostic tools 

(including PING) that are run to verify communications at the 2200 node. The tape you 

have depends on the model being installed: 

• Model IX4400—CEC500 tape 

• Model IX4800/5000/6000 servers on Plateau 2.0 or higher—CC6000 

• Model IX4800/5000/6000 servers below Plateau 2.0—CC3000 

Notes: 

• CC6000 supersedes CC3000 for all configurations at Plateau 2.0. At Plateau 2.0 a 

minimum CC6000 level of 2R1 is required. Below Plateau 2.0, a minimum CC3000 

level of 1R1 is required, except when the 2200 node is configured for resilient 

partitions, then a minimum level of 1R2 is required to execute the PING test for the 

second 2200 node. 

• Examples shown in this subsection illustrate use of the CEC500 tape. 

Follow these steps to install the tape: 

1. Enter the following command at the system console: 

ST INSTALLPKG 

A run (run-id INSPKG) starts and the following messages appear: 

INSPKG START 


N 



n CEC500,TJ,type 

3. Because the tape is unlabeled, you can enter any reel number (for example, CEC500). 

Also enter the parameters to indicate that the tape is to be assigned as a temporary 

unlabeled file (TJ) and to indicate the type of the cartridge device on which the tape 

is to be mounted (for example, HICL or HIC51). 

Following that entry, you are asked whether you want to install using default modes. 


n 

4. Press Enter to install using the default modes. A message asks if you want to register 

the INSPKG: 


n 



5. Press Enter (transmit) to accept the default. You are prompted to verify that the 

unlabeled tape you mounted is the correct reel. 

LOAD CEC500 T40Z0 NORING PP$TAPE ? 1 REGPKG 

(LOAD CEC500) (ANY UNASSIGNED CT0899) 


n CEC500 

The tape is installed when the following message appears: 

INSPKG FIN 

Continue with subsection 14.4. 

14.4. Installing DSPER 

At this time, it is recommended that the Diagnostic Software Peripheral Equipment 

Routines (DSPER) tape be installed. 

These are the steps: 

1. Enter the following command at the system console: 

ST INSTALLPKG 

A run (run-id INSPKG) starts and the following messages appear: 

INSPKG START 


n 



n ,TJ,type 

3. Because the tape is unlabeled, you can enter any reel number (for example, DSPER). 

Also enter the parameters to indicate that the tape is to be assigned as a temporary 

unlabeled file (TJ) and to indicate the type of the cartridge device on which the tape 

is to be mounted (for example, HICL or HIC51). 

Following that entry, the INSPKG run assigns the tape, and you are prompted to verify 

that the unlabeled tape you mounted is the correct reel. 

LOAD DSPER T40Z0 NORING PP$TAPE ? 1 REGPKG 

(LOAD DSPER) (ANY UNASSIGNED CT0899) 


n DSPER 

4. Type the reel ID you entered in step 3 and press Enter. 

The INSPKG run installs DSPER (and, incidentally, DPREP1100) and displays a 

message giving the package and level. Installation is complete when the following 

message appears: 

INSPKG FIN 



Notes: 

• This procedure installs DPREP1100 at the same time as DSPER. 

• For more detailed information see the DSPER (Extended Mode) Tape Definition 

Reference Manual. 

Continue with subsection 14.5. 

14.5. Preparing for Communications Verification 

This section provides two paths to communications verification (hardware RFU). The first 

path is for sites that set up all or nearly all of their own software environment. The second 

is for sites that have the customer service representative (CSR) install at least part of the 

software in Sections 15, 16, and 17. The difference is in the version of CMS 1100 used for 

communications verification. 

Communication between ClearPath nodes is tested by the diagnostic tool PING, which 

requires CMS 1100 to be active in some form. There are two ways to bring up CMS in a 

form sufficient for the PING test: 

• The PING-RUN starts a limited version of CMS 1100 that supports only the PING test 

(14.5.1). 

• The run CMS-SETUP configures a version of CMS 1100 that can be used not only for 

the PING test, but also for subsequent software installation (14.5.2). 

Follow one of these two procedures, depending on the point at which the site will take 

over software installation: 

• For sites that do most of their own software installation, this is the quickest path to 

RFU: 

1. The CSR executes 14.5.1. 

2. The CSR executes 14.6, achieving hardware RFU. 

3. The CSR terminates the CMS 1100 started in 14.6. 

4. Either the site or the CSR executes 14.5.2 to bring up a permanent CMS 1100. 

5. The site takes over the system and continues with Section 15. 

• For sites that have the CSR set up at least part of the software environment, this 

procedure provides RFU and a permanent version of CMS: 

1. The CSR executes 14.5.2. 

2. The CSR executes 14.6, achieving hardware RFU. 

3. The CSR continues with Section 15 and installs whatever software has been agreed 

upon with the site. 

4. The site takes over the system. 

Note: Either 14.5.1 or 14.5.2 must be executed to allow hardware verification. There 

is no harm, however, in executing both. 



Continue with either 14.5.1 or 14.5.2, as determined above. 

14.5.1. Starting the PING Run 

This subsection describes the quickest way to prepare for hardware verification: the PING 

run (PING-RUN). PING-RUN brings up a minimal version of CMS 1100 that supports only 

the interconnect communications test (PING test). When the test is complete, the CMS 

1100 run started by PING-RUN must be terminated and a new CMS 1100 configured and 

started by the site. 

Note: The CMS 1100 run started by PING-RUN cannot be used to verify public or SPO 

network connections. To create a CMS 1100 that can be left on the system and 

enhanced after hardware verification, follow the procedures in 14.5.2 instead. 

To use PING-RUN, take the following steps: 

1. Access an OS 2200 console session at either the SPO workstation or at the monitor 

concentrator. 

2. Enter one of the following console key-ins to start the setup run: 

• If this is the only 2200 node, or the first 2200 node in a resilient partition, enter the 

following keyin: 

ST PING-RUN 

A run called CMS starts. 

• If this is the second 2200 node in a resilient partition, enter the following keyin: 

ST PING-RUN2 

A run called CMS2 starts. 

Messages similar to the following indicate that CMS 1100 has access to the LAN: 

CONFIGURATION ERRORS(0) WARNINGS(0) 

LAN FDDIVI FDDI HLC IS USING MICROCODE LEVEL 006.52 

LAN FDDIVI MAC ADDRESS = 02E6D3070058 

Continue by executing the PING test as described in 14.6. 

14.5.2. Bringing Up CMS 1100 

This subsection describes basic CMS 1100 configuration considerations and considerations 

for implementing the IX Network Identity Repository (16.2). 

To complete the load process and verify the system, the site must use CMS 1100. This 

subsection gives the procedures for creating a minimum CMS 1100 configuration that is 

tailored to the installed external Ethernet LAN. Once the steps in this section are 

completed, CMS 1100 is ready to use. 



The CMS-SETUP Run 

A run called CMS-SETUP, provided on the HMP-FLD tape (13.3), prepares CMS 1100 for 

use. CMS-SETUP interactively solicits the addresses and device names needed for a 

minimum configuration. The information you need is described after these notes. 

Notes: 

• The external Ethernet LAN may be installed as a private network (2.4.2) or as part 

of a much larger network such as the Internet. In either case, you must supply the 

second and third items of information listed below. 

• The external Ethernet LAN is separate from the internal FDDI LAN. The two must 

not have the same IP address. For the external LAN, do not use any of the IP 

addresses reserved for the internal FDDI LAN as documented in Appendix B. 

This is the information you need for the CMS-SETUP run: 

• The 2200 ODB-defined device names of the FDDI controller's input and output devices. 

These usually default to HLVI01 and HLVI02, but they may be different if the site uses 

local naming conventions. The site may also have extra names for additional partitions 

or hosts. Default names exist for up to four hosts or partitions, and the utility allows 

you to change any of the defaults to match the actual ODB. 

• Whether the external Ethernet LAN contains a gateway and, if so, the gateway's IP 

address. 

• The IP address of the 2200 on the external LAN. 

• The 2200 ODB-defined device names of the Ethernet controller's input and output 

devices. These may be either an HLC or a CSBUS Ethernet channel adapter. 

A Minimum CMS 1100 Configuration 

A minimum CMS 1100 configuration includes definitions for both the internal FDDI LAN 

and an external Ethernet LAN. For each instance of an OS 2200 operating environment, 

sites must configure CMS 1100 to define 

• Up to four FDDI LAN connections for each possible Intel node. All four can be 

defined, even if there are fewer Intel nodes. Connections beyond the first available are 

treated as resilient connections by CMS 1100 and are not used. 

• FDDI LAN IP addresses for the OS 2200 nodes and system consoles. 

• At least one TCP/IP path to each OS 2200 node, so that Integration Expert can be used 

following hardware RFU to modify existing CMS 1100 configurations. 



Example 14–1 shows a typical minimum configuration. 

. CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH*CLEARPATH 

. PRIVATE FDDI INTERNAL LAN 

. 

LAN,FDDIVI INPUT-NODE,HLVI01 OUTPUT-NODE,HLVI02 STATUS,UP 

LAN,FDDIVJ INPUT-NODE,HLVJ01 OUTPUT-NODE,HLVJ02 STATUS,UP 

LAN,FDDIVK INPUT-NODE,HLVK01 OUTPUT-NODE,HLVK02 STATUS,UP 

LAN,FDDIVL INPUT-NODE,HLVL01 OUTPUT-NODE,HLVL02 STATUS,UP 

. 

INTERNET-ADR,IPAD IP,V$IP,192.168.57.5 


. 

. PRIVATE OR PUBLIC ETHERNET EXTERNAL LAN 

. 

LAN,ETHCUB INPUT-NODE,ethin OUTPUT-NODE,ethout DNS,NO 

. 

IP,IP1 LINK-LAYER,ETHCUB GATEWAY,gateway-IP-address 

. 

PROCESS,RSDCSU INTERNET-ADR,IPA1 

. 

INTERNET-ADR,IPA1 IP,IP1,2200-ethernet-IP-address 

Example 14–1. A Minimum CMS 1100 Configuration 

Note: If you intend to set up an IX Network Identity Repository, additional CMS 1100 

configuration statements are required. See 16.2. 

Running CMS-SETUP 

Note: This run creates a new cycle of the default CMS configuration file CMS1100$*- 

CONFIG$ and places in it a symbolic configuration element called CONFIG. 

This is the assumed location of the CMS configuration. 



WARNING 

TEMPORARY CMS-SETUP RESTRICTION AND WORKAROUND 

If you plan to use Integration Expert (15.3), you must first correct the 

output from CMS-SETUP. The configuration that CMS-SETUP produces 

supports PING testing and basic communications, but it does not allow 

Integration Expert to function. 

Example 14–1 contains two ClearPath sentinels that Integration Expert 

requires but that CMS-SETUP omits. Each sentinel consists of the 

following line: 


To permit Integration Expert to execute correctly, you must 

1. Update the element CMS1100$*CONFIG$.CONFIG to contain the two 

ClearPath sentinel lines exactly as shown in Example 14–1. Each line 

is exactly 81 characters long, begins with a period and a space, and 

contains eight repetitions of the word CLEARPATH separated by 

asterisks. You can use a Telnet session on any Windows workstation 

attached to the LAN to do the editing. 

2. Terminate the CMS 1100 run (if you have started it—see "Starting 

CMS") by entering the following keyin: 

II CMS TERM 

3. Start CMS 1100 again with the following keyin: 

ST STARTCMS,1 

The need for this workaround will be eliminated with the next ClearPath 

release. 

Follow the steps below to configure CMS 1100 with a minimum, or basic, configuration, 

using the CMS-SETUP run. This configuration lets you use CMS 1100 to install other 

products and customize your site (Sections 15 and 16). Later, if you wish, you can enhance 

the CMS 1100 configuration to meet the site's full requirements. 

1. Start the run using the ST keyin on the 2200 node. 

ST CMS-SETUP 

The following messages from CMS-SETUP appear: 

CMS-SETUP START 

n-ENTER HOST1 FDDI LAN INPUT DEVICE NAME 

n 

2. Press Enter to accept the default, or type a different device name. 

You are asked for an FDDI LAN output device name for the same host (Host1): 

n-ENTER HOST1 FDDI LAN OUTPUT DEVICE NAME 

n 




You are asked for an input device name for the FDDI LAN on the next host, Host2: 


n 


You are asked for an output device name for the FDDI LAN on Host2: 


n 


You are asked for an input device name for the FDDI LAN on the next host, Host3: 


n 




n 


You are asked for an input device name for the FDDI LAN on the last host, Host4: 


n 




n 


You are asked to enter the name of the Ethernet LAN input device: 

n-ENTER ETHERNET LAN INPUT DEVICE NAME < > 

n devnam 

10. Type the name of the input device and press Enter. 

You are asked to enter the name of the corresponding output device: 

n-ENTER ETHERNET LAN OUTPUT DEVICE NAME < > 

n devnam 

11. Type the name of the output device and press Enter. 

The following query appears: 

*****MESSAGE,I THE EXTERNAL LAN MAY OPTIONALLY HAVE A GATEWAY 

n-DO YOU HAVE A GATEWAY ON YOUR LAN? Y/N 

n 



If you have a gateway on the external LAN: 

12. Type Y and press Enter. 

You are asked for the IP address of the gateway: 

n-ENTER THE IP ADDRESS OF THE GATEWAY 

n nnn.nnn.nnn.nnn 

13. Type the numeric IP address as requested and press Enter. You are asked to confirm 

the address: 

n-IS nnn.nnn.nnn.nnn CORRECT? Y/N 

n 

14. Type Y and press Enter if the address is correct. (Otherwise, type N (no), press Enter, 

and reenter the address.) 

You are then asked for the IP address of the 2200 node on the Ethernet LAN: 

n-ENTER THE ETHERNET LAN IP ADDRESS FOR THE 2200 NODE 


Continue at step 16. 

If you do not have a gateway on the external LAN: 

15. Type N and press Enter. 

You are asked for the IP address of the 2200 node on the Ethernet LAN: 

n-ENTER THE ETHERNET LAN IP ADDRESS FOR THE 2200 NODE 


Continue with step 16. 

16. Type the numeric IP address of the 2200 node as requested, then press Enter. You are 

asked to confirm the address: 

n-IS nnn.nnn.nnn.nnn CORRECT? Y/N 

n 

17. If the address is correct, type Y and press Enter. (Otherwise type N, press Enter, and 

reenter the address.) 

When you have successfully entered the information requested in these steps, you are 

ready to start CMS 1100. 

Note: You may repeat this entire process whenever necessary if any information has 

been miskeyed or you wish to change the configuration. 

Starting CMS 1100 

To start CMS 1100 for the first time after it has been configured, enter the following keyin 

on the 2200 node: 

ST STARTCMS,1 



The "1" option instructs CMS 1100 to retrieve the system configuration from CMS1100$*- 

CONFIG$.CONFIG and save an internal representation of it. This option must be used 

whenever the system configuration changes and CMS 1100 is reconfigured. At other times, 

it is unnecessary but harmless. 

Using CMS 1100 in Verifying Hardware Communications (If Not Yet Done) 

At this point, if the PING test for hardware communications has not been done, continue 

with 14.6. Otherwise continue with Section 15. 

14.6. Running the PING Test to Verify Hardware 


Once CMS 1100 is up and running (14.5.1 or 14.5.2), take the steps below to test 

interconnect communications and achieve hardware RFU. 

Notes: 

• For Model IX5000 Series or IX4800 servers below Plateau 2.0 that are configured for 

resilient partitions, a minimum CC3000 tape level of 1R2 is required to execute the 

PING test for the second 2200 node. At Plateau 2.0, the CC6000 tape supersedes the 

CC3000 for all configurations. The minimum required level of CC6000 is 2R1. 

• If the second 2200 node in a resilient partition is up and running, perform the 

PING test for both nodes. 

• During a PING test, CMS 1100 warning messages may appear stating “*FDDIVn 

NODE(S) NOT CONFIGURED IN THE EXEC.” You can ignore those messages if the 

connections were not configured because the extra interconnect hardware 

components were not purchased as part of the system. But, if you receive four of 

those messages where n is equal to I, J, K, and L then the ODB either does not have 

the interconnect configured, or it is configured with the wrong device names. 

1. At each Intel node, log on as follows: 

• If running UnixWare, log on as superuser at a console session, if you are not 

already logged on (8.12.1). 

• If running Windows NT, log on as administrator, if you are not already logged on 

(3.5), and launch a Command Prompt session. 

2. For each active 2200 node, type the following command, then press Enter: 

ping fddiname 

where fddiname is the FDDI host name of the 2200 node being tested (see Appendix B 

for assigned FDDI host names). 

The response depends on which software is being run as follows: 

• For UnixWare, the following message appears: 

fddiname is alive 

The connection is not operational if the following message appears: 

no answer from fddiname 



• For Windows NT, the following messages appear: 

Pinging fddiname (192.168.57.5) with 32 bytes of data: 

Reply from 192.168.57.5: bytes=32 time

Section 15 

Installing the Remaining IOE Software 

Following hardware ready for use (RFU), the customer service representative (CSR) turns 

the ClearPath IX server over to the site. Site personnel may then install the remaining 

Integrated Operating Environment (IOE) software from the fast-load tapes, as described in 

this section, and customize the site to their requirements as described in Section 16. 

Note: Not all of the ClearPath IOE products are present on the fast-load tapes. For 

detailed information about fast-load tape contents, refer to the ClearPath HMP 

IX Series and 2200 Series Software Planning and Migration Overview. 

15.1. Remaining IOE Products 

The products listed in this subsection are not normally installed by the CSR; they are the 

responsibility of client personnel at the site. 

These software products may now be installed: 

• Products on fast-load tapes HMP-OE2 and HMP-UDS3 (15.2) 

• Integration Expert for ClearPath IX Series (15.3) 

15.2. Installing Default UDS Application Group 3 

from Fast-Load Tapes 

Fast-load tape HMP-OE2 and fast-load tape HMP-UDS3 are provided to allow you to 

rapidly install a default UDS application group 3. Contents of these tapes are as follows: 

• Tape HMP-OE2—Products TIPUTIL, MCB, and DPS that you may or may not need to 

reconfigure to your particular needs. To reconfigure these products, you must build 

and install them from the package tapes instead of the fast-load tape. 

• Tape HMP-UDS3—UDS products in absolute format. If you need to customize these 

products or configure additional applications, you must build and install them from the 

package tapes instead of the fast-load tape. 

This subsection describes how to 

1. Install TIPUTIL, MCB, and DPS from fast-load tape HMP-OE2 (15.2.1) 

2. Set up the TIP environment (15.2.2) 

3. Set up application group 3 (15.2.3) 

4. Install UDS application 3 from fast-load tape HMP-UDS3 (15.2.4) 



15.2.1. Installing TIPUTIL, MCB, and DPS from Fast-Load Tape 

HMP-OE2 

Note: The runstream used to install TIPUTIL, MCB, and DPS (INSTALLPKG) is a 

generic runstream used to install products from tape. This same runstream 

can be used to install optional products from package tapes. 

The tape HMP-OE2 contains products (TIPUTIL, MCB, and DPS) that may or may not need 

to be configured to your particular needs. Use the INSTALLPKG runstream to install those 

products in default mode as follows: 


ST INSTALLPKG 

You are prompted to select the installation source. 

INSPKG START 

n-INSPKG*Install from , DISK, or RSS? 

n 

2. Enter the default to select TAPE as the source. You are prompted to enter the reel 

number. 

n-INSPKG*Enter reel number 

n 



(TJ) and to indicate the type of the cartridge device on which the tape is to be 

mounted: 

n HMPOE2,TJ,type 

where type is, for instance, HICL or HIC51. 

In response, you are asked whether the installation is in default mode. 

n-INSPKG*Install default modes? /N 

n 


the INSPKG: 


n 

6. Enter (transmit) to accept the default. You are prompted to verify that the unlabeled 

tape you mounted is the correct reel. 

LOAD HMPOE2 T40A12 NORING PP$TAPE - 1 INSPKG 

(LOAD HMPOE2 )(ANY UNASSIGNED CT0899 ) 

INSPKG FIN 

The INSPKG FIN message indicates that the runstream has finished. Proceed with setting 

up the TIP environment as described in the next subsection. 


15.2.2. Setting Up the TIP Environment 


Immediately after installing TIPUTIL, MCB, and DPS from fast-load tape HMP-OE2, take 

the following steps to set up the TIP environment prior to bringing up application group 3: 


TIP UP 

Messages appear indicating that TIP automatic recovery is up. This begins recording 

of TIP activities. 

*TIP* ARF$00 - TIP AUTOMATIC RECOVERY IS UP 

. 

. 

2. Enter the following command to start the runstream that initializes TIP for use: 

ST TIPINIT 

This runstream does the following: 

• Creates SUPUR file 1000 

• Does the VALBLD of VALTAB 9 for the application group 3 error notification 

program (ENP) 

• Copies the absolute for the MCB3 example ENP into the SUPUR file 

WARNING 

Any existing VALTAB entries are destroyed. 


TIPINT START 

TIPINT*MSG: CREATE VALTAB ENTRIES 

RECOVERY OFF TIPINT 

SCHEDULE OFF TIPINT 

STICKING ON TIPINT 

RECOVERY ON TIPINT 

*TIP* VINDEX BANK LOADED - TIP SCHEDULING ON 

USER KONS INITIALIZED 

TIPINT*MSG: CAT/TREG/RES TIP SUPUR FILE 1000 

TIPINT FIN 

The TIPINT FIN message indicates that the runstream has finished. Proceed with setting 

up application group 3 as described in the next subsection. 



15.2.3. Setting Up Application Group 3 

To set up application group 3 so that the UDS tape can be installed, take the following 

steps: 

1. Application group 3 must be up to start this procedure. Take these steps to check its 

state: 

a. Check the facility status of the application by entering this command: 

AP 3 FS 

The following message should be returned to indicate that IRU short recovery is 

pending (“PND”) and is in the “INIT” recovery state: 

APP 3 RCV 0% IRU:PND REC: INIT 

b. If a message indicates that application group 3 is not in the correct recovery state, 

enter the following commands: 

AP 3 DN 

AP 3 UP INIT 

2. Enter the following command to start the runstream to set up application group 3: 

ST AP3SETUP 

This runstream does the following to perform an IRU short recovery of application 

group 3 (required to set up the application group): 

• Creates rollback page file to TIP file 301 

• Adds the MCBSETUP3 runstream 

• Sets up the IRU history file for application group 3 

• Adds the IRU3 runstream to short recover application group 3 

Messages appear and you are prompted to open an audit trail. 

Note: The common bank error messages appear as a result of UDS products not 

yet being installed when IRU short recovers application group 3 during the 

initial set up. Application group 3 must be up and short-recovered when 

UDS is initially installed (15.2.4). 

SETUP3 START 

SETUP3*MSG: CREATE ROLLBACK PAGE FILE FOR APP3 

SETUP3*MCB File Setup 8R1A 8R1A (A3) 

SETUP3*(940914 1100:56) 1996 May 30 Thu 1103:14 

SETUP3*MCB IRU Setup 8R1A 8R1A (A3) 

SETUP3*(940914 1101:16) 1996 May 30 Thu 1103:15 

SETUP3*MSG: CREATE IRU HISTORY FOR APP 3 

SETUP3*MSG: PERFORMING A SHORT RECOVERY OF UDSSRC 

Common bank error 9 . -0-> 

-0-> common bank " UNDETERMINED " with bdi 400665 -0-> 

-0-> referenced by run-id " SETUP3 " is not installed. 

Common bank error 9. bdi 400665 not found -0-> 

-0-> in omnibus element BANK-BDI$ 

-0-> in file SYS$*LIB$(1) . 

SETUP3*App 3 Init of MCB complete 


APP 3 ROLLBACK INITIALIZATION STARTED 

APP 3 ROLLBACK INITIALIZATION COMPLETE 

SETUP3**WARNING* 5807 App 3 UDS is not configured 


SETUP3*App 3 AOR phase not required 

0-EXEC 8 REQUIRES AUDIT TRAIL: 3 ANS. OP, E, OR DN 

3. Open an audit trail by making the following entry: 

0 OP 

More messages appear. The SETUP3 FIN message indicates that the runstream has 

finished. 

AT 3 ACI$03(1) *FILE ASSIGNED* 1103:18 

AT 3 L1 FIX(1,1) *OPEN* 1103:19 

AT 3 L1 BLK 1 TBSN 0 1103:19 

AT 3 OP 

APP 3 RESTARTED 

SETUP3*App 3 short recovery complete 

AT 3 S1 FIX(2,2) *SPARE* 1103:19 

SETUP3 FIN 

After the SETUP3 FIN message appears, proceed with installing UDS application group 3 

as described in the next subsection. 

15.2.4. Installing UDS Application Group 3 from Fast-Load Tape 

HMP-UDS3 

After application 3 has been set up, you can take the following steps to install the default 

UDS application group 3 from fast-load tape HMP-UDS3: 

1. Enter the following command to start MCB: 

ST MCB3 

MCB initialization messages appear as follows: 

MCB3 START 

MCB3 *MCB 8R1A 8R1A (A3) 

MCB3 *(940914 1058:42) 1996 May 30 Thu 1103:37 

MCB3 *MCB INITIALIZATION COMPLETE 96/05/30 1103:40 

2. Enter the following command to start the runstream that installs UDS application 

group 3: 

ST INSTALLAPP3 

That runstream installs and registers the following products from the HMP-UDS3 tape. 

• Data Management System (DMS 2200) 

• Relational Data Management System (RDMS 2200) 

• Shared File System (SFS 2200) 

• Universal Data System Control (UDSC) 



• Unisys Repository Manager (UREP) 

Messages appear and you are prompted to enter a reel number: 

INAP3 START 

n-INAP3 *INSTALLAPP3: Enter reel number 


parameters to indicate that the tape is to be assigned as a temporary file, that it is 

unlabeled, and that it is mounted on device type HICL. For example: 

n HMPUD3,TJ,HICL 

Several messages are displayed as follows: 

LOAD HMPUD3 T40A13 TAPE$ - 1 INAP3 

(LOAD HMPUD3 )(ANY UNASSIGNED CT0899 ) 

INAP3*MSG: STARTING THE INSTALL OF THE UDS PRODUCTS FOR APP3 

INAP3*MSG: INSTALLING UDSC 

INAP3 * 

INAP3 *UDSC install processing could not assign the ADT-FILE. 

INAP3 *It is assumed that the SYS-FILE for this application 

INAP3 *group does not exist. UDSC will not attempt to free 

INAP3 *the SYS-FILE from the UDS domain. 

INAP3 * 

INAP3 * 

INAP3 **INFO* UDSC 

INAP3 *File UDS$$SRC*ADT-FILE has been initialized by this 

INAP3 *Solar PRODLD of the UDSC default application. 

INAP3 * 

INAP3 * 


INAP3 *File UDS$$SRC*SYS-FILE has been initialized by this 


INAP3 * 

INAP3 * 


INAP3 *The following files have been cataloged during this 


INAP3 * 

INAP3 * STD#UDS$$SRC*ADT-FILE 

INAP3 * UDS$$SRC*SYS-FILE 

INAP3*MSG: THE INSTALLATION OF UDSC APP3 COMPLETED CORRECTLY 

INAP3*MSG: INSTALLING RDMS 

INAP3*MSG: THE INSTALLATION OF RDMS APP3 COMPLETED CORRECTLY 

INAP3*MSG: INSTALLING DMS 

INAP3*MSG: THE INSTALLATION OF DMS APP3 COMPLETED CORRECTLY 

INAP3*MSG: INSTALLING UREP 

INAP3 MAX TIME 

INAP3 *IRU history file - UDSSRC*IRU$HF - has been initialized 


INAP3 MAX PAGES 


INAP3 MAX TIME 

INAP3*MSG: THE INSTALLATION OF UREP APP3 COMPLETED CORRECTLY 

INAP3*MSG: INSTALLING SFS 

INAP3*MSG: THE INSTALLATION OF SFS APP3 COMPLETED CORRECTLY 

INAP3*MSG: STARTING THE REGISTER OF THE UDS APP3 TAPE 

INAP3*MSG: THE REGISTER OF THE UDS APP3 PACKAGE COMPLETED CORRECTLY 

INAP3 FIN 

The INAP3 FIN message indicates that the runstream has finished. 

15.3. Installing Integration Expert 

You can install Integration Expert on the SPO workstation if the workstation is a PC 

running the Windows NT Workstation operating system, or you can install it on any 

Windows 95 or Windows NT workstation with connections to the 2200 nodes of the 

ClearPath IX server. 

Notes: 

Caution 

If you used the CMS-SETUP run to configure CMS 1100, you must edit the CMS 

1100 configuration to allow Integration Expert to function correctly. For 

instructions, see the warning in 14.5.2. 

• To use Integration Expert with any 2200 node, the 2200 node must have a CMS 

1100 configuration that includes at least one TCP/IP path to the node. 

• The instructions below are also given in the jewel-case insert booklet provided with 

the Integration Expert for ClearPath HMP IX Series CD-ROM. 

Follow these steps to install the full version of Integration Expert: 

1. Close all other applications you are running. 

2. Insert the Integration Expert CD-ROM into the CD-ROM drive. The installation 

program starts automatically. 

3. Wait until a message indicates that installation has completed successfully. 

The full version of Integration Expert is now ready to use. 

A subset of Integration Expert called PMLite is also provided on the CD-ROM. This 

version does not contain any of the Integration Expert tools. It allows general users to 

benefit from Integration Expert without jeopardizing the system configuration. 



To allow users to install PMLite, do the following: 

1. Place both the SETUP.EXE and README.TXT files from the Integration Expert CD- 

ROM in a shared directory on your network. 

2. Instruct users to map a drive to the shared directory. 

3. Instruct users that they can install PMLite by executing file SETUP.EXE from their 

workstations. 


Section 16 


Customer personnel at the site perform these additional tasks: 

• Use Integration Expert (formerly known as PathMate) to configure other software (for 

example, CMS 1100) (16.2) 

• Use Integration Expert to create and populate the IX Network Identity Repository 

(16.3) 

• Install optional IOE products (16.4) 

• Customize SPO Basic Edition configurations with site-specific names (16.5) 

• Test TCP/IP communications (16.6) 

In addition, you can optionally do any of the following: 

• Install optional UnixWare software products (if applicable) (16.7). 

• Repartition the UnixWare node (16.8). 

• Configure a resilient 2200 node partition (16.9). 

You can also perform any other system configuration or tuning tasks not described in this 

guide. For example, you can tune or regenerate the Exec using procedures in the Exec 

Installation and Configuration Guide. 

16.1. About Using Integration Expert 

The first task following hardware RFU is normally the configuration of other software. 

Integration Expert is the application that helps you do this. Before you can use Integration 

Expert, however, you must first install, on a 2200 node, a CMS 1100 configuration that 

includes at least one TCP/IP path to the node for communication with Integration Expert 

(14.5.2). 

After establishing an appropriate CMS 1100 configuration, you can use Integration Expert 

to 

• Further customize CMS 1100 (16.2) 

• Create and populate the IX Network Identity Repository (16.3) (applicable only if 

integrating SPO Basic Edition with CA Unicenter TNG). 

• Configure other products such as 

− TransIT Open/OLTP (OLTP-TM2200) 

− Open Programming Environment (OPE) 



− DEPCON 2200 

− DEPCON PC 

− UniAccess ODBC 

Integration Expert provides assistance ranging from totally automated services to step-bystep 

instructions. Capabilities include 

• Intrinsic capabilities—Fully automated solutions are provided. An example is basic 

print management for ClearPath IX servers. 

• Tools—Single-purpose applications are provided to help manage integrated 

technologies. For example, a configuration utility creates basic configurations to get 

ClearPath IX server software up and running. 

• Templates—Overall structures are provided that sites can customize. An example is 

the sample Excel macro for accepting OS 2200 application output. 

• Demonstrations—These provide ideas or techniques that can be used to develop a 

similar solution. An example is creating a distributed transaction between the UNIX 

and OS 2200 environments. 

• How To—Instructions, explanations, and background information are centralized and 

summarized for several tasks. References to product documentation are provided if 

more detailed information is needed. An example is the process for designing OLTP 

applications. 

The introductory overview describes the kinds of problems and solutions in each category. 

The overview for each category describes the problems and solutions in more detail and 

links directly to the appropriate process or procedure. 

16.2. Customizing CMS 1100 

To customize CMS 1100, execute the Config ACE tool included in Integration Expert. See 

the section of Integration Expert labeled Perform Basic Software Configuration for a 

ClearPath IX Server for complete details. 

The Config Ace tool provides an interactive interface that simplifies basic software 

configuration tasks for a ClearPath IX server. The dialogue for each product is in the form 

of a wizard that steps through the procedure and returns to the main Config Ace form 

when finished. Make sure you read the general prerequisites section as well as the CMS 

1100 prerequisites section before customizing CMS 1100 using the Integration Expert 

Config Ace tool. 

Config Ace places the new CMS 1100 configuration in the following default output file: 

CLEARPATH*CMS.CONFIG/NODE1 

(You can change the name of the output file using Integration Expert. The procedure 

below assumes the default name.) 

Follow these steps to start the newly configured CMS 1100 after using Config Ace to create 

the configuration: 



1. Copy the new configuration file, CLEARPATH*CMS.CONFIG/NODE1, to the following 

file: 

CMS1100$*CONFIG$.CONFIG 

2. At the 2200 node console, terminate the old CMS 1100 by entering the following keyin: 

II CMS TERM 

3. Start the new CMS 1100 by entering the following keyin: 

ST STARTCMS,1 

16.3. Considerations for the IX Network Identity 

Repository 

An IX Network Identity Repository contains management information base (MIB) data, 

such as network names, addresses, and object identifiers, needed to manage ClearPath IX 

server components using SPO Basic Edition when integrated with Unicenter TNG. You 

need to use Integration Expert to create the repository and add or remove network 

components to be managed. Use the ClearPath HMP IX Network Identity Repository 

Manager (RepoMan) tool to populate, update, and view the ClearPath HMP IX Network 

Identity Repository. See the section of Integration Expert labeled Update the ClearPath 

HMP IX Network Identity Repository for complete details. 

16.3.1. Configuring CMS 1100 for the IX Network Identity 

Repository 

Before you set up an IX Network Identity Repository, the CMS 1100 configuration must 

include the following statements: 

Note: These statements are generated automatically when you use Integration Expert 

to configure CMS 1100. 

• A process statement for the IX network identity repository object manager, IXNAGX: 

PROCESS,IXNAGX PASSWORD,SNMP TYPE,TSAM 

Note: If you change the password to something other than SNMP, you also must 

change the IXNAGX runstream to specify a new password for the IXNAGX 

processor call. 

• An SNMP management statement enabling write access in order to update the 

repository. This write access can be restricted to community name and to specific IP 

addresses. The community name PUBLIC should not be given write access. 

SNMP-MGMT,snmp-mgmt-id COMMUNITY-NAME,community-name ; 

WRITE-ACCESS,YES ; 

[SECURITY-IP-ADDRESS,ip-address1] ; 

... 

[SECURITY-IP-ADDRESS,ip-address10] ; 

where: 

snmp-mgmt-id 



is the unique name for this configuration statement in the CMS 1100 configuration. 

community-name 

is the name used for this SNMP community by both the SNMP agent and the SNMP 

managers. 

ip-address-n 

the Internet address or addresses allowed to have write access to the repository. 

For detailed information about configuring CMS 1100, refer to the CMS 1100 Installation 

and Configuration Guide. 

Note: Because Integration Expert asks you to identify the 2200 node with which a 

generated configuration is to be used, CMS 1100 configuration file names 

should match the name of the ODB partitions with which they are to be used. 

Also, batch runstreams should be named accordingly to prevent an operator 

from starting the wrong runstream and thus using the wrong CMS 1100 

configuration. 

16.3.2. Preparing to Access the IX Network Identity Repository: 

IXNAGX 

Before the repository can be accessed, the IX Network Identify Agent (IXNAGX) must be 

installed and running on the 2200 node as follows: 

• IXNAGX is included in SNMP-AGX2200 and is installed when that product is installed 

from the fast-load tape during basic OS 2200 IOE installation. 

• You must start the IXNAGX background run using the ST IXNAGX command. 

16.3.3. Updating the ClearPath HMP IX Network Identity 

Repository 

To update the Network Identity Repository, follow these steps: 

1. Start the Integration Expert RepoMan tool. 

2. Initiate access to the HMP IX Network Identity Repository (MIB). 

a. Enter the SNMP Community name; use the Community name with write privileges 

defined in the CMS 1100 configuration. 

b. Enter the Host name; this is the OS 2200 host where the repository resides. 

3. Supply the quantity of each type of node that exists in the ClearPath HMP IX server. 

After the solicitation, the utility adds skeletal node entries to the repository, which you 

can edit and save. 

4. Update the node entries (or Console entries contained within node entries) by 

selecting Edit Selected Object from the Edit menu, or double-click the icon that 

represents the selected entry. Supply values for fields on the form using the Help 

command button if you need help. Save entries when the form is complete. 



5. Verify your changes by viewing the information displayed by the Repository Manager 

(RepoMan) tool after saving updates to the repository. 

16.4. Optional IOE Products 

A number of products provided with the ClearPath system can be used at the discretion of 

the site. The following is a sample of the products that are provided with the IOE but 

whose installation is optional: 

• Unisys Repository Manager (UREP) Workstation 

For UREP Workstation installation procedures, see the UREP-WS End Use Guide. 

• Open Application Development Environment (OADE) for Windows 

For OADE installation procedures, see the OADE for Windows User Guide. 

• Enterprise Backup and Restore (EBRS) 

EBRS software includes components for 2200 and Intel ClearPath IX nodes, as well as 

a workstation module for a Windows NT workstation. You can install the workstation 

component on the SPO workstation, if the SPO workstation is a PC running the 

Windows NT Workstation operating system. You can also install the EBRS 

workstation component on any other Windows NT workstation. See these documents 

for information about the components of EBRS: 

− EBRS Windows NT Workstation Installation and Operations Guide 

− EBRS Windows NT Server Installation and Operations Guide 

− EBRS UNIX Server Installation and Operations Guide 

− EBRS Host Installation Guide 

− EBRS Capabilities Overview 

Note: EBRS cannot be used with either a workstation or a server that is running 

Windows 2000. 

• Web Transaction Server (WebTS) 

For instructions about installing WebTS, see the WebTS Administration Guide. 

• Web Transaction Enabler (WebTx) 

For information about installing WebTx and its required and optional components, see 

the booklet (jewel case insert) provided with the WebTx 4.0 Web Transaction Enabler 

for ClearPath HMP Series Software CD-ROM. 

• Open Programming Environment (OPE) 

OPE provides an SCO/NOVELL/USL-based implementation of the UNIX System V 

operating environment, including the kernel, shell, library, and utilities. 

Note: Installation instructions for OPE are provided in Appendix E. 

• SysAdmin 

SysAdmin, a component of OPE, is a Web-based application that provides a single 

interface for administering various system objects across multiple heterogeneous 



nodes in the ClearPath environment. It allows the system administrator to manage 

accounts, users, groups, transactions, and system performance. 

Note: Installation instruction for SysAdmin are provided in Appendix E. 

16.5. Modifying SPO Basic Edition Configurations 

Following initial installation, sites can modify SPO Basic Edition configurations to reflect 

site-specific naming conventions rather than predefined names. 

The steps for modifying SPO Basic Edition configurations depend on whether the desired 

name for a node was input as the system name (host name) during the installation process. 

• If the desired host names were not input as system names during installation—and 

thus not configured as aliases in the hosts file for the SPO server and UnixWare 

nodes—you must take the following steps: 

1. Remove URM agent files from the SPO server and any UnixWare node being 

renamed (see 16.5.1). 

2. Edit the SPO server and UnixWare node hosts files to change the node names and 

aliases (see 16.5.2). You cannot edit Windows 2000 or Windows NT node hosts 

files, because they are in a fixed format that does not allow aliases. You must, 

however, change entries in the other hosts files for Windows 2000 and Windows 

NT nodes to reflect new names. 

3. Copy the new SPO server hosts file to each of the OS 2200 consoles (16.5.3). 

4. Replace old node representations in the SPO Basic Edition configurations with 

new ones using one of the following methods: 

− Use the rename script (16.5.4) to replace all Windows 2000 and Windows NT 

node representations with new ones (or optionally use the Single Point 

Configuration routine, described in 16.5.5, to replace them one at a time). 

− Use the Single Point Configuration routine (16.5.5) to replace representations 

of Windows 2000, Windows NT, UnixWare, and OS 2200 nodes, as well as 2200 

system consoles and the SPO server. 

5. Reinstall the URM agents so they can identify components by their new names 

(16.5.6). 

• If the desired host names were input as system names during installation procedures, 

you only need to replace old representations with new ones (step 4). 

16.5.1. Removing the URM Agents 

Before editing the SPO server hosts file as described in 16.5.2, you must remove the UNIX 

Resource Monitor (URM) agent from the SPO server and any UnixWare node that is being 

renamed. Take the following steps: 

1. In the Single Point Configuration routine's main menu, click Application, then click 

Maintain UNIX Agents. 

2. In the Maintain UNIX Agents window menu, click Execute, then Remove. 



A dialogue box asks you to select the systems from which you want to remove agents. 

3. Select any CP_UNIXx systems, the SPO_Server, or both, that you will be renaming. 

• If you select a CP_UNIXx node, a dialogue box appears informing you that the 

UNIX agent for system CP_UNIXx has been removed and that you must execute 

/opt/SPO-agent/remove on the CP_UNIXx system. 

• If you select the SPO_Server, a dialogue box appears informing you that the UNIX 

agent for system SPO_Server has been removed successfully. 

4. Click OK in response to either dialogue box. 

5. If you selected a CP_UNIXx node, sign on to the UnixWare node as root. 

6. Enter the following commands: 

cd /opt/SPO-agent 

./remove 

The URM agent is now removed. 

16.5.2. Editing the Hosts Files to Reflect New Node Names 

Note: This step cannot be performed for a Windows 2000 or Windows NT node hosts 

file because the Windows node hosts file is in a fixed format that does not allow 

aliases. 

To edit the hosts file on the SPO server and UnixWare nodes (if applicable) to reflect new 

names for nodes, take the following steps: 

1. If not already logged on, log on as superuser (10.13.2). 

2. Using an editor (for example, vi), open the /etc/hosts file. 

3. Determine whether the names of the nodes are correct (Example 16–1 shows the SPO 

server hosts file before editing and Example 16–2 shows a UnixWare node hosts file, 

both for a server with two Windows 2000 or Windows NT nodes and two UnixWare 

nodes). 

4. If the names are not correct, add the desired names or aliases to the current names. 

The names for UnixWare nodes and the SPO server should be the same as their UNIX 

system names (uname). The uname can be determined by entering the following 

command on each system: 

uname -n 

For the 2200 node system consoles, the site’s preferred name should be used as the 

name in the SPO server host file; otherwise, SPO Basic Edition cannot bring up the 

replicated 2200 Console display. 

lan-address lan-node-name alias1.. ..aliasn # comment 

192.168.57.3 Intelnode1-name cp_nt1 

192.168.57.4 Intelnode3-name CP_UNIX1 

192.168.57.6 fddi22am # reserved for OPE 

192.168.57.7 fddi22mr # reserved for MAPPER 





192.168.58.11 cp_cons01 

192.168.58.12 cp_cons02 

192.168.58.15 sposerver-name SPO_Server 

192.168.58.16 xterm-name cp_xterm 

Example 16–1. SPO Server Hosts File Format before Editing 








192.168.58.15 sposerver-name SPO_Server 

Example 16–2. UnixWare Node Hosts File Format before Editing 

Example 16–3 and Example 16–4 show how those hosts files would appear after editing for 

the new site-specific host names. 


192.168.57.3 newIntelnode1-name Intelnode1-name cp_nt1 

192.168.57.4 newIntelnode3-name Intelnode3-name CP_UNIX1 





192.168.58.11 newconsole1name console1name cp_cons01 

192.168.58.12 newconsole2name console2name cp_cons02 

192.168.58.15 newsposerver-name sposerver-name SPO_Server 

192.168.58.16 xterm-name cp_xterm 

Example 16–3. SPO Server Hosts File Format after Editing 










192.168.58.15 newsposerver-name sposerver-name SPO_Server 

Example 16–4. UnixWare Node Hosts File Format after Editing 

16.5.3. Copying the Modified SPO Server Hosts File to the System 

Consoles 

After being modified, the newly edited SPO server hosts file should be copied to diskette 

and then loaded at each of the 2200 system consoles. 

Copying the Modified File to Diskette 

To copy the modified hosts file from the SPO server to diskette, take the following steps: 

1. If not already logged on at the SPO server, log on as superuser (10.15). 

2. Place a diskette into the drive unit of the SPO server and enter the following 

commands to copy the hosts file to diskette: 

cd /etc/inet 

tar cvf /dev/rdsk/f03ht ./hosts 

Loading the Hosts File to a System Console 

To load the new hosts file on each 2200 node system console, take the following steps: 

1. On the system console, press F3. 

The Utilities Session menu appears (Figure 10–2). 

2. Select Optional Features, then press Enter. 

A list of utilities appears as follows: 

AMS Utility 

USP Utility 

USP APFG Utility 

SP Interface Utility 

3. Select SP Interface Utility, then press Enter. 

An execute box appears. 


The Single Point Interface Utility window appears. 



5. Select the Hosts File menu bar item, then press Enter. 

A list of options appears as follows: 

Load 

Save 

Exit 

6. Select Load, then press Enter. 

7. Press the up or down arrow keys to get the following drop down list: 

DOS-HD 

DOS-DD 

UNIX 

8. Use the arrow keys to select the UNIX option, then press Enter. 

9. Tab to the Host Name field, enter the site-defined name of the console you are loading. 

The Execute box appears. 

10. Again press Enter. 

You are prompted to insert the diskette. 

11. Insert the diskette with the hosts file on it, then press Enter. 

A window appears indicating that the system is working and that you should wait. 

When the system completes loading the hosts file, it returns to the Single Point 

Interface Utility window. 

12. If you do not have a router, skip this step. If you have a router, add router information 

as follows: 

a. Select the Routers menu bar item. 


Add Router 

Delete Router 

Display Routers 

b. Select Add Router, then press Enter. 

An Add Router window appears. 

c. Enter information in that window as follows: 

• In the top portion enter the IP address and host name that defines the 

destination of messages to be routed through the router. That destination can 

be either a network or a host. 

• In the bottom portion, enter the IP address and host name of the router. 

13. When done, press Enter. 

The Single Point Interface Utility window reappears. 


14. Select the Changes menu bar item. 





15. Select Execute Changes to enable the changes to the hosts file. 

16. Select Exit to exit from the Single Point Interface utility. 

Repeat this procedure for each system console. 


16.5.4. Changing a Windows 2000 or Windows NT Representation 

Using the Rename Script 

When the SPO server operating system is installed, a tuning script is run. The tuning script 

prompts for Windows 2000 and Windows NT node system names. It assigns those system 

names as labels for the Windows node representations in SPO cluster diagrams. 

To later change the names of those node representations, you must first edit the SPO 

server and UnixWare hosts files to reflect the desired Windows 2000 or Windows NT node 

names (see 16.5.2). The format of those changes in the hosts files must be as follows: 

where: 

xxx.xxx.xxx.xxx newname oldname cp_ntx 

xxx.xxx.xxx.xxx The IP address of the node 

newname The new name 

oldname The name currently being used, if not cp_ntx 

cp_ntx The CP_NT alias designation 

Once the hosts files have been edited, you can use the Single Point Configuration routine 

as described in 16.5.5 to replace existing node representations with new ones one at a time. 

Or you can run a rename script to replace them all at once. 

The rename script searches all SPO configurations whose names contain NT (for example, 

2_2UNIX_2NT_6.3CP) for lines with the cp_nt aliases and substitutes all occurrences of 

the third field in the hosts file with the second field. 

To run the rename script, take the following steps at the SPO server: 

1. If you are not already logged on, log on as the root user (user-id root). 

2. Enter the following command to change to the directory containing the script: 

cd /var/sadm/pkg/cptune/install 



3. Start the rename script by entering the following command: 

sh ./rename_nt.sh 

16.5.5. Changing a Representation Using the Single Point 

Configuration Routine 

The most complete method of changing the host and console representations is to first 

delete the predefined host or console, then add a new host or console using a site-defined 

name. The following procedure describes the steps to take: 

1. Create a new configuration as follows: 

a. Log on to SPO Basic Edition as spadmin to start the Single Point Configuration 

routine. 

You are prompted to select a configuration to edit. 

b. Select the configuration to edit (for example, 2_2UNIX_2NT_6.3CP), then select 

OK. 

In a few moments, the TopCluster window and the Configure SPO Basic Edition 

main menu window appear. 

c. Click File in the main menu and select the Save Configuration As option. 

You are prompted to enter the name of the new configuration. 

d. Enter a name for the new configuration you are creating, then click OK. 

After a few moments, the new configuration is created and the main menu title 

reflects that you are now editing your new configuration (the Single Point 

Configuration routine automatically switches to the new configuration). 

e. In the TopCluster window menu, click Edit, then select the Icon Placement option. 

This opens the Edit Icon Placement window. Move the window to keep it 

accessible without overlapping the TopCluster window. 

2. Customize UnixWare node representations as follows: 

a. If the node is not included in a UnixWare 7 ReliantHA cluster: 

• In the TopCluster window menu, click Delete, then select the UNIX Systems 

option. 

A window appears, listing the nodes that are currently configured. 

If the node is included in a UnixWare 7 ReliantHA cluster: 

• In the TopCluster window menu, click Edit, then select the Clusters option. 

A window appears, listing the clusters that are currently configured. 

• Select the cluster that contains the CP_UNIXx node you want to change and 

click OK. 

A window appears, showing the systems contained in the cluster. 

• In the cluster window menu, click Delete, then select the UNIX Systems 

option. 



b. Select CP_UNIXx and click OK. 

The system is now removed from the configuration. 

c. In the TopCluster window menu, click Add, then select the UNIX Systems option. 

A window for entering the new system representation appears. 

d. Enter the site-defined name of the Intel node and select OK. 

The node is added to the TopCluster diagram and a window also appears 

requesting the system’s network connection name. 

e. Click the Unknown button if the node is directly connected to the SPO server. If 

the connection is through a Network Access Server (NAS), enter the NAS network 

name that is listed in the /etc/hosts file. 

A window requesting the /etc/services name for the system appears. 

f. Enter CP_UNIXx, then select OK. This entry was already made in the 

/etc/services file for the direct connection to the UNIX node to port 1 of the 

Equinox multiport board. If the system is connected through a NAS, you need to 

enter the service entry for the port assigned on the NAS. 

g. Position the icon where you want it by clicking the icon once, then click the 

desired position once in the TopCluster window. X and Y coordinates can be 

further adjusted by entering coordinates through the Edit Icon Placement window. 

3. Customize the SPO server representation (SPO_Server) as follows: 

a. In the TopCluster window menu, click Delete, then select the UNIX Systems 

option. 

A window listing the nodes that are currently configured appears. 

b. Select SPO_Server and click OK. 

The SPO_Server is now removed from the configuration. 

c. In the TopCluster window menu, click Add, then select the UNIX Systems option. 

A window for entering the new system appears. 

d. Enter the site-defined name of the SPO server and select OK. 

The system is added to the TopCluster diagram. 

A window requesting the system’s network connection name appears. 

e. Enter spo_telnet and select OK (this entry was already made in the /etc/services 

file by the SPO Basic Edition installation routine). 

f. Position the icon where you want it by clicking the icon once, then clicking the 


further adjusted by entering coordinates through the Edit Icon Placement window 

(the original SPO server icon was located at X=800 and Y=600). 

4. Disable the SPO server timeout feature. This feature determines the time interval 

between the receipt of console message traffic before a timeout alarm is generated and 

is not needed for monitoring ClearPath IX server nodes. Disable it as follows: 

a. In the TopCluster window menu, click Edit, then select the UNIX Systems option. 

In a few moments, the Edit UNIX Systems window appears. 



b. Click the value in the Timeout Period column for the new Intel node name. 

A window appears for you to enter the new timeout value. 

c. Change the timeout value to 0 (this disables the timeout feature), then click Enter 

or OK. 

d. Repeat this process for each Intel node and for the renamed SPO server, then 

close the Edit UNIX Systems window. 

5. Customize 2200 node partitions and OS 2200 system console representations as 

follows: 

a. In the TopCluster window menu, click Delete, then select the OS 2200 Systems 

option. 

A window appears, listing the currently configured 2200 node partitions. 

b. Select the 2200 partition you want to rename, then click OK. 

The 2200 partition is now removed from the configuration. 

c. In the TopCluster window menu click Add, then select the OS 2200 Systems 

option. 

A window for entering the new system appears. 

d. Enter the site-defined name of the 2200 node partition, then select OK. 

The node is added to the TopCluster diagram (note that the system does not have 

a console icon connected at this time). 

e. Position the icon where you want it by clicking the icon once, then clicking the 



(the original 2200 node icons were located at X=300,700 and Y=150). 

f. In the TopCluster window menu, click Delete, then select the OS 2200 Consoles 

option. 

A window listing the currently configured 2200 system consoles appears. 

g. Select the OS 2200 console, then click OK. 

The system console is removed from the configuration. 

h. In the TopCluster window menu, click Add, then select the OS 2200 Consoles 

option. 

A window for entering the new console appears. 

i. Enter the site-defined name of the OS 2200 console, then select OK. 

The console is added to the TopCluster diagram. A window asks you to identify 

the OS 2200 partition to which the console should be connected. 

j. Click the name of the new OS 2200 partition (from step d), then select OK. 

The console now shows a connection to the new OS 2200 partition. 

k. Position the icon where you want it by clicking the icon once, then clicking the 



(the original OS 2200 console icons were located at X=300,700 and Y=350). 



l. Repeat these procedures for each of the OS 2200 systems and consoles you wish to 

customize. 

6. Save and Verify the new configuration changes as follows: 

a. In the Configure SPO Basic Edition main menu click File, then select the Save 

Configuration option. 

A window asks if you want to perform configuration verification. 

b. Click Yes. 

After a few moments, a window appears stating that no errors were found. 

If errors are detected, two windows appear, one describing the errors and the 

other asking if you wish to save the configuration anyway. Follow the instructions 

given in the results window to fix the errors. 

You now must reinstall the URM agents for UnixWare nodes (if applicable) as described in 

16.5.6. 

16.5.6. Reinstalling the URM Agents (UnixWare Nodes Only) 

After modifying host representations, you must take the following steps to reinstall URM 

agents on UnixWare nodes to allow the agents to interact with the new site-defined 

representation names: 

1. In the Single Point Configuration routine's main menu click Application, then select 

the Maintain UNIX Agents option. 

Two windows with tables appear—a Maintain UNIX Agents window and a URM 

policies window. 

2. In the Maintain UNIX Agents table, click the hyphen (-) under URM Policy for each 

new UnixWare node name. 


3. Under URM Policy, double-click default. 

4. Under Security Scheme, click Access Allowed for each new UnixWare node name. 


5. Under Security Scheme, double-click Manual Install. 

6. In the Maintain UNIX Agents table, click the hyphen (-) under URM Policy for the new 

SPO server name. 


7. Under URM policy, double-click default. 

8. In the Maintain UNIX Agents window's menu bar, click Execute, then select Install. 

A dialogue box appears asking you to select the systems on which you want to install 

agents. 



9. Select each new UnixWare node name and the new SPO server name. 

A dialogue box appears for each new UnixWare node name, informing you that the 

UNIX agent for the new UnixWare node name has been placed into directory 

/var/opt/spo/manual/new-Intelnode-name on the SPO server. 

10. Click OK for each dialogue box. 

A dialogue box appears informing you that the UNIX agent for the new SPO server 

name has been installed successfully. 

11. Click OK. 

12. Check to see that the URM agent is running on the SPO server as follows: 

a. Enter the following command on the SPO server: 


b. Check the response output for sh ./urm.loop. 

If the URM agent is not running, su to the root user (enter the su command to 

become superuser) and enter the following command: 

/opt/SPO-agent start 

13. Sign on to each UnixWare node as the root user (user-id root) and enter the following 

commands: 

rcp -pr spo-server-name:/var/opt/spo/data/manual/new-Intelnode-name /tmp 

where spo-server-name is the network name of the SPO server. 

cd /tmp/new-Intelnode-name 

./install 

14. Again, check to see that the URM agent is running on the UnixWare node by entering 

the following command: 


a. Check the response output for sh ./urm.loop. 

b. If the URM agent is not running, enter the following command: 

/opt/SPO-agent start 

15. At the SPO workstation, in the Maintain UNIX Agents window's menu bar, click File, 

then select Exit. 

16. Exit the Single Point Configuration routine as follows: 

a. From the Configure SPO Basic Edition main menu window click File, then select 

the Exit Configuration Routine option. A window appears to verify that you wish 

to quit. 

b. Click OK. 


16.6. Testing TCP/IP Communications 


Once sites customize their CMS 1100 configuration(16.2), they can test TCP/IP 

communications as follows: 

1. Access an OS 2200 console session at either the SPO workstation or at the monitor 

concentrator. 

2. Start the customized CMS 1100 configuration. CMS 1100 should indicate that the 

Ethernet interface has been initialized, and is up and active. 

3. At the Intel node, log on as follows: 

• At a UnixWare node, log on as superuser at a console session, if you are not 

already logged on (10.13.2). 

• At a Windows NT node, log on as administrator, if you are not already logged on 

(11.8), and open the Command Prompt window (MS-DOS prompt). 

4. Type the following command, then press Enter: 

ping xxx.xxx.xxx.xxx 

where xxx.xxx.xxx.xxx is the IP address of the 2200 node. Alternatively, you 

could enter hostname instead of the IP address, where hostname is the Internet 

system name assigned to the 2200 node. 

The following message should appear in response: 

xxx.xxx.xxx.xxx is alive 

where xxx.xxx.xxx.xxx is the IP address of the 2200 node. 

The connection is not operational if the following message appears: 

no answer from xxx.xxx.xxx.xxx 

16.7. Installing Optional UnixWare Products 

After running the tuning script to complete installation of UnixWare, sites can install 

optional application packages. In general, optional packages are installed using the 

following procedure: 

1. If you are not already logged on, log on as the root user (user-id root). 

2. Load the application package release medium (CD-ROM, tape, or diskette) in the 

appropriate drive unit. 

3. At the shell prompt enter a pkgadd command appropriate to the media. For example: 

# pkgadd -d /dev/rdsk/device 

where device is the name of the device from which software is being installed (for 

example, c0s0 or f03ht). 

Answer any prompts that appear on the screen. Refer to the individual product 

documentation for specific instructions. 

4. After the last package has been installed, reboot. 



See the documentation for your version of UnixWare for details about installing optional 

products. 

16.8. Repartitioning the UnixWare Node 

Following initial installation, a site may wish to repartition UnixWare. The only method 

for doing that, without reinstalling UnixWare, is to create a new partition in the 

unallocated free space that was not partitioned during installation. See the ClearPath IX 

Operations Guide for instructions. 

16.9. Configuring Resilient Partitions (2200 Node) 

Sites can configure the 2200 node for resilient partitions as shown in Figure 16–1. During 

normal operation, the 2200 node connects to the FDDI LAN and communicates with the 

Intel node through the primary connection. Whenever the primary partition is unavailable, 

the resilient connection automatically is made available and communication switches from 

the primary path to the resilient path. 

Take the following steps to configure resilient partitions: 

1. Configure the resilient connection in the operations database (ODB) using the Site 

Configuration Management System (SCMS). This is the responsibility of whoever 

generates the ODB. For more information on using SCMS to configure a resilient 

connection, see the SCMS Administration Guide Volume 1. 

2. The resilient connection must be configured in CMS 1100 by site personnel using the 

Integration Expert Config Ace tool. 

Notes: 

• The second 2200 node partition is OS 2200 only. The CMS 1100 configuration for 

the second partition cannot contain heterogeneous multiprocessing (HMP) 

interconnect components that allow the resilient connection to access the Intel node. 

Thus, the two partitions cannot run together as two instances of a ClearPath IX 

system. 

• When configuring the resilient connection in the ODB using SCMS, the name 

FDDIVI must be assigned to the first FDDI control unit and FDDIVJ to the second 

control unit (see Appendix D). Those names are required by automated 

configuration tools. 



ClearPath IX5000 Series 

or IX4800 Server ClearPath IX4400 Server 

2200 System 2200 System 

Power 

Domain 0 

Primary 

Connection 

Intel 

Node 

Internal 

FDDI LAN 

Power 

Domain 1 

Resilient 

Connection 

Intel 

Node 

Primary 

Connection 

PCC0 PCC1 

Intel 

Node 

Figure 16–1. Resilient Configurations 

Internal 

FDDI LAN 

Resilient 

Connection 

Intel 

Node 




Section 17 

Installing Optional OS 2200 Software 

from the Package Tapes 

After you have customized the site (Section 16), you can install optional OS 2200 software 

from package tapes. 

Caution 

When reinstalling products, do not attempt to install them in package tape 

numerical order. Products must be installed in an order described in the 

ClearPath HMP IX and 2200 Systems Software Planning and Migration Overview. 

OS 2200 products available on keyed package tapes are listed in ClearPath HMP IX and 

2200 Systems Software Planning and Migration Overview. To install a product from a 

keyed package tape, you must 

1. Register the key tape (labeled KEYTAPE) using the procedure in 17.1. 

2. Refer to the documents listed in 17.2 for installation instructions. 

17.1. Registering the OS 2200 Product Key Tape 

Registering the product key tape is required to install optional products from package tape. 

To register the product key tape, take the following steps: 

1. Start the runstream for registering the key tape by entering the following command: 

ST REGISTERPKG 


n Register package from or DISK? 

n 

2. Press Enter to select the default location of the key tape. A prompt asks for entry of 

the reel number from which the key is to be installed. 


n CPKEY,TJ,type 


Installing Optional OS 2200 Software from the Package Tapes 

3. Because the tape is unlabeled, enter any reel number. Also enter the parameters to 

indicate that the tape is to be assigned as a temporary unlabeled file (TJ) and to 

indicate the type of cartridge device on which the tape is to be mounted (for example, 

HICL or HIC51). 

The following message is displayed: 


n 

4. Press Enter to select the default and mount the key tape in the specified drive. 

Loading begins, and you are prompted to verify that the unlabeled tape you mounted is 

the correct reel. 

LOAD CPKEY T40Z0 NORING PP$TAPE - 1 REGPKG 

(LOAD CPKEY )(ANY UNASSIGNED CT0899 ) 


n CPKEY 

The following message appears to indicate that the key tape is registered: 

REGPKG FIN 

17.2. Product Installation Documentation 

Once you have registered the key tape (17.1), you can install optional products or product 

features from the package tapes. For information about product interdependencies and 

installation procedures, refer to the following documents: 

• ClearPath Enterprise Servers Software Products Installation Guide 

• ClearPath HMP IX and 2200 Systems Software Planning and Migration Overview. 

• Individual product documents (for example, the SCO UnixWare Installation 

Handbook). 


Appendix A 

Tables of Documentation, Support, and 

Migration 

The tables in this appendix do the following: 

• Relate ClearPath components to the levels of the ClearPath IX Installation and 

Configuration Guide in which they are documented (Table A–1) 

• Summarize the supported combinations of software and Intel processors (Table A–2) 

• Summarize the hardware migration requirements for moving from an HMP IX 4.0 

server to an HMP IX 5.0 operating system (Table A–3) 

Note: For details of software migration, see the ClearPath Enterprise Servers Software 

Planning and Migration Overview. 

A.1. Matrix of ClearPath Components and ICG 

Release Levels 

Table A–1 allows you to determine which version of the ClearPath HMP IX Installation and 

Configuration Guide (ICG) contains information on your particular HMP IX configuration. 

The suggested starting point is the most recent version associated with your configuration. 

In some cases, however, depending upon when (early or late) in the product life cycle you 

installed your configuration, you may have to back up to an earlier ICG version. The ICG 

availability date can assist you in making this determination. 

All ICG revisions are available on the Web at 


They will remain available until the support life has expired for the products included in 

the revision. The revision shipped to you with your HMP IX order is always the most 

recent. 

7850 5104–009 Version 009B (Web Only) A–1

Tables of Documentation, Support, and Migration 

Major 

Hardware or 

Software 

Changes 

ICG 

Available 

(mm/yy) 

IX System 

ICG 

7850 

5104- 

000 

HMP IX 2.1 X 

Table A–1. ClearPath Components and ICG Release Levels 

ICG 

7850 

5104- 

001 

ICG 

7850 

5104- 

002 

ICG 

7850 

5104- 

003 

ICG 

7850 

5104- 

004 

ICG 

7850 

5104- 

005 

ICG 

7850 

5104- 

006 

ICG 

7850 

5104- 

007 

ICG 

7850 

5104- 

008 

ICG 

7850 

5104- 

009 

6/97 9/97 1/98 8/98 12/98 2/99 4/99 2/00 7/00 8/00 

HMP IX 3.0 X X 








2200 Node 

IX4400 X X X X X 

IX4800 X X X X X 

IX5600 X X X X X X X X 

IX5800 X X X X X X X X 

IX6600 X X X 

IX6800 X X X 

Intel Node 

VX12xx 

(SMP61000) 

SVR4 X X 

UW 2.x X X X 

continued 

A–2 Version 009B (Web Only) 7850 5104–009

Major 

Hardware or 

Software 

Changes 

ICG 

Available 

(mm/yy) 

VX13xx 

(DR/2) 

ICG 

7850 

5104- 

000 



ICG 

7850 

5104- 

001 

ICG 

7850 

5104- 

002 

ICG 

7850 

5104- 

003 

ICG 

7850 

5104- 

004 

ICG 

7850 

5104- 

005 

ICG 

7850 

5104- 

006 

ICG 

7850 

5104- 

007 

ICG 

7850 

5104- 

008 

ICG 

7850 

5104- 

009 

6/97 9/97 1/98 8/98 12/98 2/99 4/99 2/00 7/00 8/00 

NT 4.0 X X X X 

UW 7.x X X X X 

VX14xx 

(QR/6) 

NT 4.0 X X X X X X X X 

UW 2.x X X X X X X X 

UW 7.x X X X X X 

VX15xx 

(ES2045R) 

(QR/2) 

NT 4.0 X X X X X X 

MSCS X 


RHA X X 

VX18xx 

(XR/6) 

NT 4.0 X X X X X X 

UW 2.x X X X X X X 


RHA X X X X 

continued 



Major 

Hardware or 

Software 

Changes 

ICG 

Available 

(mm/yy) 

ES2024R 

ICG 

7850 

5104- 

000 


ICG 

7850 

5104- 

001 

ICG 

7850 

5104- 

002 

ICG 

7850 

5104- 

003 

ICG 

7850 

5104- 

004 

ICG 

7850 

5104- 

005 

ICG 

7850 

5104- 

006 

ICG 

7850 

5104- 

007 

ICG 

7850 

5104- 

008 

ICG 

7850 

5104- 

009 

6/97 9/97 1/98 8/98 12/98 2/99 4/99 2/00 7/00 8/00 

NT 4.0 X X 

W2K X X 

ES5044R 

NT 4.0 X 

W2K X 

ES2085R 

UW 7.x X X X 

ES5085R 

NT 4.0 X X X 

W2K X X 

SPO Server 

SMP5400 

SVR4 X X X 

IX401x 

(DR/6) 

UW 2.x X X X X X X X 

continued 


Major 

Hardware or 

Software 

Changes 

ICG 

Available 

(mm/yy) 

ES2024R 

ICG 

7850 

5104- 

000 



ICG 

7850 

5104- 

001 

ICG 

7850 

5104- 

002 

ICG 

7850 

5104- 

003 

ICG 

7850 

5104- 

004 

ICG 

7850 

5104- 

005 

ICG 

7850 

5104- 

006 

ICG 

7850 

5104- 

007 

ICG 

7850 

5104- 

008 

ICG 

7850 

5104- 

009 

6/97 9/97 1/98 8/98 12/98 2/99 4/99 2/00 7/00 8/00 

UW 7.1.1 

/SPO 6.1 X X 

SPO Console 

LT501 

Terminal X X X X X X X 

HMP 5000 

w/s X X X X X 

Gateway 

GWP-1 w/s X 

GWP-W w/s X X 

Notes: 

• Beginning with ICGs 7850 5104-002 and higher, refer to ICG 1.1 (Table 1–1), which 

identifies the specific sections containing the software installation procedures for 

each server node. 

• This matrix is included in Appendix A starting with ICG version 007. 

• Preliminary versions of this matrix are included on the Web and have letter 

designations, for example, Version -007A. 



A.2. Intel Environment Overview 

This table summarizes the support combinations of Intel processors, Intel operating 

systems, and ClearPath IX Integrated Operating Environment (IOE) releases. 

Intel 

Platform 

Table A–2. Server Platforms Versus Operating Systems 

HMP IX Microsoft NT SCO UnixWare 

Release 

Level eNT 4.0 NTS 4.0 W2K 

UW 7.1/ 

7.1.1 

UW 7.0/ 

7.0.1 

VX1300 3.1 n/s n/s n/s n/s n/s n/s 

4.0 n/s n/s n/s n/s n/s n/s 

4.1 n/s √ n/s √ n/s 

(√ 7.0.1 

only) 

4.2 n/s √ n/s √ n/s 

(√ 7.0.1 

only) 

5.0 n/s √ nca √ n/s n/s 

5.1 n/s √ nca √ n/s n/s 

6.0 n/s √ nca √ n/s n/s 

VX1400 3.1 n/s √ n/s n/s n/s √ 

4.0 n/s √ n/s n/s √ √ 

4.1 n/s √ n/s √ √ √ 

4.2 n/s √ n/s √ √ √ 

5.0 n/s √ n/s √ n/s n/s 

5.1 n/s √ n/s √ n/s n/s 

6.0 n/s √ n/s √ n/s n/s 

VX1500 3.1 n/s n/s n/s n/s n/s n/s 

4.0 √ n/s n/s n/s n/s n/s 

4.1 √ n/s n/s √ n/s 

(√ 7.0.1 

only) 

4.2 √ n/s n/s √ n/s 

(√ 7.0.1 

only) 

UW 

2.1.3 

A–6 Version 009B (Web Only) 7850 5104–009 

n/s 

n/s 

n/s 

n/s 

continued

Intel 

Platform 


Table A–2. Server Platforms Versus Operating Systems 

HMP IX Microsoft NT SCO UnixWare 

Release 

Level eNT 4.0 NTS 4.0 W2K 

UW 7.1/ 

7.1.1 

UW 7.0/ 

7.0.1 

5.0 √ n/s nca √ n/s n/s 

5.1 √ n/s nca √ n/s n/s 

6.0 √ n/s nca √ n/s n/s 

VX1800 3.1 √ √ n/s n/s n/s √ 

4.0 √ √ n/s n/s √ √ 

4.1 √ √ n/s √ √ √ 

4.2 √ √ √ √ √ √ 

5.0 √ √ n/s √ n/s n/s 

5.1 √ √ n/s √ n/s n/s 

6.0 √ √ n/s √ n/s n/s 

ES2085R 5.0 n/s n/s n/s √ n/s n/s 

5.1 n/s n/s n/s √ n/s n/s 

6.0 n/s n/s n/s √ n/s n/s 

ES5085R 5.0 √ n/s √ n/s n/s n/s 

5.1 √ n/s √ n/s n/s n/s 

6.0 √ n/s √ n/s n/s n/s 

ES5044R 5.1 √ n/s √ n/s n/s n/s 

6.0 √ n/s √ n/s n/s n/s 

ES2024R 5.1 √ n/s √ n/s n/s n/s 

Legend: 

6.0 √ n/s √ n/s n/s n/s 

UW 

2.1.3 

√ The Intel platform is supported for the combination of operating environment and release level. 

n/s Indicates product, Intel software, and release level combination has not been tested, and problem 

reports will not be accepted. 

nca Indicates an option is not currently available. 



A.3. Hardware Migration Requirements 

The following table identifies the hardware implications of moving an existing HMP IX 4.0 

server to an HMP IX 5.0-supported operating system. 

Note: For details of software migration, see the ClearPath Enterprise Servers Software 

Planning and Migration Overview. 

Table A–3. Hardware Migration Requirements 

Migrating from System… To… Requirements 

VX12xx with SVR4 (no longer 

supported) 

VX13xx with UnixWare 7.x VX13xx with NT 4.0 Server 

Edition 

VX12xx with UnixWare 2.1.3 Not available. UnixWare 2.1.3 is no 

longer offered on HMP IX systems. 

VX12xx with UnixWare 7.1 Not available. You must first migrate 

to a currently offered server. 

VX12xx with NT Server 4.0 Not available. You must first migrate 

to a currently offered server. 

VX13xx with NT 4.0 

Enterprise Edition. Not offered. 

VX13xx with any OS VX13xx with Windows 2000 Not offered. 

VX14xx with UnixWare 2.1.2 

or 2.1.3 

VX14xx with UnixWare 7.1 You must 

Replace the RAD9602-PIC, RAD9602- 

MEM RAID controller with RAD302- 

PCI, RAD242-MEM, RAD302-BAT. 

• Replace the RAID controller 

RAD1341-PCI with RAD9602-CI 

and RAD9602-MEM 

• Upgrade to FDI 101-PCI FDDI 

card with UnixWare 7.x driver 

VX14xx with NT Server 4.0 Replace the SF1001-FET Ethernet 

card with ETH1010071-PCI. 

VX14xx with UnixWare 7.0 VX14xx with NT Server 4.0 Replace the SF1001-FET Ethernet 

card with ETH1010071-PCI. 

VX14xx with NT Server 4.0 VX14xx with NT Enterprise 

4.0 

Not available. 

VX14xx with any OS VX14xx with Windows 2000 Not available. 

VX15xx with UnixWare 7.x VX15xx with NT 4.0 Server 

Edition 

VX15xx with NT 4.0 


Not offered. 

VX15xx with any OS VX15xx with Windows 2000 Not offered. 

Replace the RAD9602-PIC, RAD9602- 

MEM RAID controller with RAD302- 

PCI, RAD242-MEM, RAD302-BAT. 

continued 



Table A–3. Hardware Migration Requirements 

Migrating from System… To… Requirements 

VX18xx with UnixWare 2.1.2 

or 2.1.3 

VX18xx with UnixWare 7.1 Upgrade to UnixWare 7.x driver for 

FDI101 PCI FDDI card. No changes 

are required. 

VX18xx with NT Server 4.0 Not available. 

VX18xx with NT Server 4.0 VX18xx with NT Enterprise 

4.0 

VX18xx with NT Enterprise Replace the SFV 6200-PCI video card 

with SFV 6201-PCI. 

VX18xx with any OS VX18xx with Windows 2000 Not available. 

ES2085R with UnixWare 7.1.1 ES5085R with NT Enterprise 

4.0 

ES5085R with NT Enterprise 

4.0 

ES5085R with Windows 

2000 Advanced Server 

No card changes are required for this 

migration. 

Add ESS software package and 

required systems management card. 

Not offered. 




Appendix B 

Communication Settings Specific to 

ClearPath IX 

This appendix describes ClearPath Enterprise Server IX specific communication settings 

including 

• Internal FDDI Interconnet IP addresses used by server components, depending on the 

server configuration (Table B–1). These addresses cannot be used otherwise by 

customer sites. 

• TSAM configuration values (Table B–2). 

• Sample default contents of a hosts file (/etc/hosts) (Example B–1). 

Caution 

Integration Expert configuration assistants define the values in Table B–1 by 

default. ClearPath does not function properly if those values are not used. 

Note: Other predefined IP addresses and host names also are used, in addition to those 

listed in Table B–1, whenever a ClearPath IX server is configured as a private network 

without connection to a public network (see 2.4.2). 

Table B–1. IP Addresses and Host Names Used by the Private FDDI 

Interconnect 

FDDI IP Address Product FDDI Host 

Name 

192.168.57.1 Windows NT/2000 server node 1 fddinttp 

192.168.57.2 fddintul 

192.168.57.3 fddintsr 

192.168.57.21 Windows NT/2000 server node 2 fdd2nttp 

192.168.57.22 fdd2ntul 

192.168.57.23 fdd2ntsr 


continued 

7850 5104–009 Version 009B (Web Only) B–1

Communication Settings Specific to ClearPath IX 

Table B–1. IP Addresses and Host Names Used by the Private FDDI 

Interconnect 

FDDI IP Address Product FDDI Host 

Name 

192.168.57.42 fdd3ntul 

192.168.57.43 fdd3ntsr 


192.168.57.62 fdd4ntul 

192.168.57.63 fdd4ntsr 

192.168.57.4 UnixWare server 1 fddiuxsr 

192.168.57.24 UnixWare server 2 fdd2uxsr 



192.168.57.5 2200 node 1 (OS 2200 demand/common) fddi22sr 

192.168.57.6 Open Programming Environment (OPE) IP Address 

(2200 node 1) 

fddi22am 

192.168.57.7 MAPPER (2200 node 1) fddi22mr 

192.168.57.25 2200 node 2 (if applicable) (OS 2200 

demand/common) 

192.168.57.26 Open Programming Environment (OPE) IP Address 

(2200 node 2) 

fdd222sr 

fdd222am 

192.168.57.27 MAPPER (2200 node 2) fdd222mr 

B–2 Version 009B (Web Only) 7850 5104–009


Table B–2. TSAM Configuration Assignments 

Product TSAM 

Process 

Name 

TSAM Password TSAM T- 

Selector 

DEPCON V$DEP DEPCON DEPCON 

MAPPER TSAMID PASSWORD 

Open Programming 

Environment (2200) IP 

Address 

AMTSAA SCRAMBLED-EGGS-WITH- 

HASH-BROWNSA 

TM 2200 IP Address V$TM2 TM2200 

UniAccess (2200) IP Address UACP UA 

InfoAccess (2200) IP Address IASOCK IA 

Oracle Transparent Gateway ORALSN ORA 

Example B–1 shows the default contents of the hosts file (/etc/hosts) for UnixWare nodes 

and OPE. See 7.3 for information on setting up the Windows NT node hosts file. 

# begin ClearPath IX /etc/hosts defaults 

# The following host numbers and names are reserved for ClearPath 

# private internal LAN. The IP network number 192.168.57.xx is 

# from the block of IP network numbers that the Internet Assigned 

# Numbers Authority (IANA) has reserved for private internets. 

# See RFC# 1918 for details. 

# 

# WARNING! 

# 

# Do not change these values. Your ClearPath system will not 

# function properly if these values are modified or removed. 

# 

# One or more alias names may be added for any entry. 

192.168.57.1 fddinttp # Reserved for NT HTP 

192.168.57.2 fddintul # Reserved for NT Upper Layer Services 

192.168.57.3 fddintsr # Reserved for NT node 

192.168.57.4 fddiuxsr # Reserved for Unix node 

192.168.57.5 fddi22sr # Reserved for shared 2200 

192.168.57.6 fddi22am # Reserved for OPE 1 

192.168.57.7 fddi22mr # Reserved for Mapper 

192.168.57.8 fddi22a2 # Reserved for OPE 2 

192.168.57.9 fddi22a3 # Reserved for OPE 3 

192.168.57.21 fdd2nttp # Reserved for second NT HTP 

192.168.57.22 fdd2ntul # Reserved for second NT Upper Layer Services 

192.168.57.23 fdd2ntsr # Reserved for second NT node 

192.168.57.24 fdd2uxsr # Reserved for second Unix node 

7850 5104–009 Version 009B (Web Only) B–3


192.168.57.25 fdd222sr # Reserved for second shared 2200 

192.168.57.26 fdd222am # Reserved for second OPE 1 

192.168.57.27 fdd222mr # Reserved for second Mapper 

192.168.57.28 fdd222a2 # Reserved for second OPE 2 

192.168.57.29 fdd222a3 # Reserved for second OPE 3 

192.168.57.41 fdd3nttp # Reserved for third NT HTP 

192.168.57.42 fdd3ntul # Reserved for third NT Uppder Layer Services 

192.168.57.43 fdd3ntsr # Reserved for third NT node 

192.168.57.44 fdd3uxsr # Reserved for third Unix node 

192.168.57.45 fdd322sr # Reserved for third shared 2200 

192.168.57.46 fdd322am # Reserved for third OPE 1 

192.168.57.47 fdd322mr # Reserved for third Mapper 

192.168.57.48 fdd322a2 # Reserved for third OPE 2 

192.168.57.49 fdd322a3 # Reserved for third OPE 3 

192.168.57.61 fdd4nttp # Reserved for fourth NT HTP 

192.168.57.62 fdd4ntul # Reserved for fourth NT Upper Layer Services 

192.168.57.63 fdd4ntsr # Reserved for fourth NT node 

192.168.57.64 fdd4uxsr # Reserved for fourth Unix node 

192.168.57.65 fdd422sr # Reserved for fourth shared 2200 

192.168.57.66 fdd422am # Reserved for fourth OPE 1 

192.168.57.67 fdd422mr # Reserved for fourth Mapper 

192.168.57.68 fdd422a2 # Reserved for fourth OPE 2 

# Put your site specific information after the next line. 

# end ClearPath IX /etc/hosts defaults 

Example B–1. Default Hosts File for UnixWare Nodes and OPE 

B–4 Version 009B (Web Only) 7850 5104–009

Appendix C 

SPO/HMP IX Interface License Key 

Registration 

This appendix is for sites using Single Point Operations Console (formerly known as 

SPO/ESE Console). 

The ClearPath HMP IX server includes Single Point Operations Basic Edition for ClearPath 

IX software (component style name SMS 154-CPS). Your ClearPath IX server software 

license entitles you to use Basic Edition to operate a stand-alone ClearPath IX server or 

alternatively to manage one ClearPath IX server from one or more Single Point Operations 

servers (formerly known as SPO/ESE servers). 

License keys are not used within a stand-alone Basic Edition server. However, the feature 

that allows Single Point Operations Console to control a ClearPath IX server is enabled by 

a license key. That feature is known as the SPO/HMP IX Interface. 

When the license key is installed on the Single Point Operations server, an increment in 

Single Point Operations Console functionality is provided as follows: 

• The ANSI X3.64 connectivity attributes are enabled for monitoring the Single Point 

Operations server. 

• If Windows NT is installed on an Intel node 

− The Windows NT connectivity attributes are enabled for monitoring the 


− The 2200Mon Status classification is enabled for running the HMP preconfigured 

Status display. 

• If UnixWare is installed on an Intel node 

− The ANSI X3.64 connectivity attributes are enabled for monitoring the UnixWare 

node. 

− The Unix2200Mon Status classification is enabled for running the HMP 

preconfigured Status display. 

Each ClearPath IX server delivery includes a temporary key that enables you to 

immediately configure and manage the ClearPath IX server from a Single Point Operations 

server. You should obtain a permanent key as soon as possible (see C.1). 

7850 5104–009 Version 009B (Web Only) C–1

SPO/HMP IX Interface License Key Registration 

C.1. How to Obtain a Permanent Key 

The key listed below will temporarily enable the SPO/HMP IX Interface feature of Single 

Point Operations Console necessary to manage your ClearPath IX server. It will expire on 

11/30/00. 

Your temporary key is: 8606 9731 3117 8353 6049 

In order for Unisys to provide accurate license key services in the future, you must request 

a permanent key as soon as you begin the integration of your ClearPath IX server into the 

Single Point Operations Console environment. 

Take the following steps to obtain a permanent key: 

1. Complete the permanent key request form in C.3. The form is used to identify your 

ClearPath IX server order numbers plus the Single Point Operations server-id values 

used for permanent keying. 

2. Send the form to Plymouth Operations Software Manufacturing (POSM). 

3. Upon receipt of the key request, POSM generates a permanent key and returns it to 

you on standard permanent key shipment forms (43059784 and 43059785). 

4. Upon receiving the permanent key, install the new keys on the designated server or 

servers. 

Permanent keys for the SPO/HMP IX Interface reflect the total number of ClearPath IX 

servers that you have registered to be managed by Single Point Operations Console. 

Normally, this is one per ClearPath IX server purchased. The resultant key includes the 

accumulated total as the license count value. 

C.2. Upgrades to Single Point Operations Console 

To upgrade from standard Basic Edition software to Single Point Operations Console, you 

must purchase package style SMS 6000-CPS. That package consists of two components: 

Single Point Operations Console and Single Point Status. In this case, the registration of 

license keys begins with receipt of the software order in Plymouth Operations Software 

Manufacturing (POSM). Initial delivery of temporary keys and subsequent delivery and 

registration of permanent keys are performed through the normal SPO key registration 

process which is documented in the Single Point Operations Administration and 

Configuration Guide. 

In order to manage the ClearPath IX servers from Single Point Operations Console, 

however, you must install the temporary key provided in C.1 and follow the instructions 

there for requesting a permanent key. If you have more than one ClearPath IX server, the 

order number for each must be indicated on the request. If you have more than one Single 

Point Operations server, the server-id for each must be indicated on the request. 

C.3. Permanent Key Request Form 

To obtain a permanent key, submit the following form using the instructions in C.1. 

C–2 Version 009B (Web Only) 7850 5104–009


Permanent Key Request Form 

To obtain a permanent key, you must identify the UNIX server system on which Single Point Operations Console software 

is installed. In the first table below, enter your server identification code in the Server ID column. You can find this code by 

selecting About under the Help menu in the Single Point Operations Console software. If you are running Single Point 

Operations Console on more than one server (for instance, on redundant servers), you must supply the server ID codes of 

all Single Point Operations Console systems. 

Enter the server host names and server IDs of your Single Point Operations Console server systems below. 

Use large, bold print—for example, 1234 5678 90 

Server Host Name Server ID 

Attention: Verify that your server ID values are transcribed correctly on this form! 

Your permanent license key (or keys) will be bound to the server IDs identified on this form. You will receive one key for 

each server. The license count authorized by the key will equal your total entitlement for SPO/HMP IX Interface software 

as provided through your ClearPath IXS4xxx-xx contracted shipments. 

The following additional information is required to make a complete registration of your license keys: 

Date of Request: Unisys Customer Number: 

Customer Name: Site Name: 

Address: Site Location: 

Requester Name: 

Requester Phone: 

Number of IXS4xxx-xx systems licensed by these orders: 

ClearPath Order Numbers: _____________________ 

Select ( √ ) method for delivery of permanent key: 

� Telephone FAX Number ______________________ � E-mail/Internet Address ______________________ 

This form must be sent by FAX to 1-734-737-4943 

Unisys Corporation Plymouth Operations Software Manufacturing 

7850 5104–009 Version 009B (Web Only) C–3


C–4 Version 009B (Web Only) 7850 5104–009

Appendix D 

Configuring the FDDI Interconnect 

The SCMS database and operations database (ODB) are provided prebuilt from the factory. 

If you need to recreate them at the site for some reason, you must configure fiber 

distributed data interface (FDDI) connections as described in this appendix. 

Cautions 

• Naming conventions used in the SCMS procedures must be followed for 

Integration Expert to operate correctly. 

• Modification of the SCMS configuration requires a stop of all partitions to allow 

reloading of the SCMS-generated ODB files. Use procedures described in the 

ClearPath IX Operations Guide to deactivate active partitions. 

D.1. Configuring 2200 Node FDDI Connections 

To configure FDDI connections for a 2200 node, you must reboot the master system 

console (or whichever console you use for generating ODB files) in SDF online mode and 

use the SCMS software to 

• Define the logical system configuration 

• Generate ODB files that you can load into the SCF workstation and use to reboot the 

2200 node 

Note: The SCMS Administration Guide Volume 1, Reference Information describes 

detailed procedures for using the SCMS software. 

A critical aspect of setting up the logical system configuration is configuring the FDDI 

channel that connects a 2200 node and an Intel node. This section describes how to 

change the SCMS system definition to include an FDDI channel if it has not already been 

configured. 

The type of system you have determines how the FDDI channel is connected as follows: 

• IX4400 server—The FDDI connection is provided by a Host LAN Controller-2 (HLC-2) 

or an FDDI channel card. 

• IX5000 Series or IX4800 server—The FDDI connection is provided by an FDDI channel 

card. 

7850 5104–009 Version 009B (Web Only) D–1


The following subsections describe how to configure each type of server. 

D.1.1. IX4400 Server Configuration (HLC2) 

ClearPath IX4400 servers contain the following hardware components that you must 

configure using SCMS: 

• Processing complex cabinet 0 (PCC0) contains a dedicated input/output processor 

(IOP). 

• That IOP connects to block multiplexer channels (BMC) in a BMC rack in PCC0. 

• A Host LAN Controller-2 (HLC-2) connects to a BMC channel. 

• The HLC-2 contains an FDDI channel card that connects to an EISA FDDI card in the 

Intel node. 

• The HLC-2 contains an Ethernet feature, if needed, to make a TCP/IP connection to a 

site’s production LAN. 

Notes: 

• Multiple Intel node configurations require that you configure multiple PCC 

cabinets, because each FDDI control unit/device combination is normally 

configured to IOPs in different PCC cabinets. 

• A TCP/IP Ethernet connection to the site’s production LAN is required. If a 

connection does not already exist, the connection can be made through the HLR2- 

EDF Ethernet feature. 

Configure those components as follows: 

1. Power on or reboot the SCF workstation (master system console) in SDF online mode. 

2. Using SCMS, add a 4.5-MB-per-second block multiplexer channel input/output 

processor module (IOPM-BMC-4.5) to the processor complex cabinet (PCC) 

configuration. Select that module from the PCC feature screen as follows: 

D–2 Version 009B (Web Only) 7850 5104–009

INVENTORY_INCLUDE: Limited Comprehensive 

Generic Inventory Information 

Enter info. for PCC-500 

at location CAB 

Features associated with: PCC-500.PCC0 

Select features for the above component. 


# Used # Left Feature Name Description 

x x xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 

x x xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 

1 7 IOPM-BMC-4.5 Block I/O Module 4.5 or 3.0 m/s 

F9=Add feature F10=Subtract feature 

3. Configure the HLC-2 to match the hardware configuration as follows: 

a. Add an HLC-2 unit to inventory and assign it whatever name is appropriate for the 

site. 

b. Add the FDDI feature to location 00 (the A position) in the HLC-2. Make sure the 

feature component name for the first control unit is FDDIVI. SCMS automatically 

names the devices as HLVI01 (address=1 type=output) and HLVI02 (address=2 

type=input). Do not change those names. 

Add additional control units for additional Intel nodes, as needed, and name them 

as follows: 

• FDDIVJ (device names HLVJ01 and HLVJ02 are generated by default) for 

control unit 2 

• FDDIVK (device names HLVK01 and HLVK02 are generated by default) for 


• FDDIVL (device names HLVL01 and HLVL02 are generated by default) for 


Note: These names are required for later use by automated configuration 

tools. Either device name (it does not matter which) can be assigned as 

input or output. 

c. Exit from the inventory add procedure. 

d. Modify inventory to add the Ethernet feature to the HLC-2 in location 01 (the B 

position). 

e. Exit to the main menu of SCMS. 

f. Use System_include to include the HLC-2 in the system configuration. 

7850 5104–009 Version 009B (Web Only) D–3 

i02 

i18


4. Make Host LAN Controller-2 (HLC-2) connections by selecting the Subsystem option 

from the System_Connect menu. Then select the HLC-2 to which to make each FDDI 

connection. This screen appears as follows: 

The HLC-2 Subsystem Connections 

HLC-2.FDDIVI 

F1 = Help, F2 = Choices, F5 = Parameters, Enter = Choose F12 = Done 

5. In that screen, define the channels to which the HLC-2 is connected and specify the 

contents of the HLC-2 cabinet as shown in the following screen: 


CU Cabinet Containees 

I0CH00 I0CH01 

0 0 

CU1:FDDIVI 

CU2:(optional, your choice) 

Tab, Shift/Tab, Esc = Discard Screen Changes, F12 = Done 

6. Modify the HLC-2 subsystem media access control (MAC) address and channel address 

configuration parameters as appropriate as shown in the following screen. The MAC 

address can be read from the HLC-2 maintenance panel menu. 



FDDIVI Parameters 

MAC Address Vendor # 000000 

MAC Address Device # 000000 

Number of Devices 2 

Device default name HLVI 


HLC Devices 

Dest. MAC address LSAP/ 

Name Address Type Vendor # Device # DSAP 

HLVI01 1 OUTPUT 

HLVI02 2 INPUT 

F! = Help, F2 = Choices, F5 = Parameters, Enter = Choose F12 = Done 

7. Verify/lock the system and partitions, create and mark the partitions, and send the 

ODB to a floppy disk or tape, whichever is preferred. 

8. Reboot the SCF in offline mode and load the new ODB. 

9. Reboot the SCF in online mode, then reboot the 2200 node. 

D.1.2. IX5000 Series or IX4800 Server Configuration 

IX5000 Series or IX4800 servers need the following hardware components configured in 

SCMS system inventory: 

• A Power Domain (PWRD) with at least one CSIOP for the required FDDI and Ethernet 

connections. The CSIOP is identified by Feature Name IOPM-CS under PWRD. 

• Connect the FDDI/Ethernet channel adapters to Bus0 of physical IOP0 in Power 

Domain 0. 

• An FDDI control unit (CS-FDDI) to provide the 2200 connection to the FDDI port in 

the Intel node. This control unit must be named FDDIVI for proper OS 2200 

identification. With that name, SCMS automatically names the devices as HLVI01 

(address=1 type=output) and HLVI02 (address=2 type=input). Do not change those 

names. No parameter changes are needed in System_Connect/Subsystem. 

Add additional control units for additional Intel nodes, as needed, and name them as 

follows: 

− FDDIVJ (device names HLVJ01 and HLVJ02 are generated by default) for control 

unit 2 

− FDDIVK (device names HLVK01 and HLVK02 are generated by default) for control 

unit 3 

− FDDIVL (device names HLVL01 and HLVL02 are generated by default) for control 

unit 4 

7850 5104–009 Version 009B (Web Only) D–5


Note: These names are required for later use by automated configuration tools. 

Either device name (it does not matter which) can be assigned as input or 

output. 

• An Ethernet control unit (CS-ETH) to provide the 2200 connection to the site’s 

production LAN. There is no special naming for this control unit and no parameter 

changes are needed in System_Connect/Subsystem. 

D.2. Configuring UnixWare Node FDDI Interconnects 

The UnixWare node FDDI connection is configured when the tuning script is run during 

procedures described in Section 8 (UnixWare 7). 


Appendix E 

Installing OPE and SysAdmin 

This appendix gives installation instructions for two of the optional IOE products provided 

with the ClearPath system, OPE and SysAdmin. 

OPE and SysAdmin are part of the standard IOE software package. They are packaged 

together on the OPE tape. They are installed on a 2200 node, where OPE provides the 

UNIX-compatible environment and basic open services needed by SysAdmin. 

Use the INSTALLPKG runstream with an install mode of A to install both products at the 

same time, as follows: 


ST INSTALLPKG 

2. A run (run-id INSPKG) starts and asks the following question: 

INSPKG START 

n-INSPKG*Install from , DISK, or RSS? 

n 


n-INSPKG*Enter reel number 

n OPE,TJ,type 



(TJ) and to indicate the type of cartridge device on which the tape is to be mounted 

(for example, HICL or HIC51). 


n-INSPKG*Install default modes? /N 

n N 


the INSPKG: 


n 

6. Enter (transmit) to accept the default. You are prompted for the product name. 

n-INSPKG*Enter product name, transmit if complete 

n OPE 

7850 5104–009 Version 009B (Web Only) E–1

Installing OPE and SysAdmin 

7. Enter OPE. You are prompted for the product level. 

n-INSPKG*Enter product level 

n level 

8. Enter level (where level is the product level identified on the tape label, such as 4R1A) 

and press Enter. You are prompted for the product mode. 

n-INSPKG*Enter product mode 

n A 

9. Type A and press Enter. You are again prompted for the product name. 

n-INSPKG*Enter product name, transmit if complete 

n 

10. Press Enter to indicate that you are done. Both OPE and SysAdmin are loaded from 

the tape. You are prompted to verify that you specified the correct reel by messages 

such as these: 

LOAD OPE T40A12 NORING PP$TAPE - 1 INSPKG 

(LOAD OPE )(ANY UNASSIGNED CT0899 ) 

The following message indicates that the run is finished: 

INSPKG FIN 

To use the Network File System (NFS) features provided by OPE, the site must update the 

/etc/hosts file of OPE as follows: 

• The 2200 node host name must match the name displayed by the OPE uname -n 

command. 

• Entries must be added for any remote systems that will be accessed as NFS clients. 

After you update the /etc/hosts file, normal NFS administrative tasks can be performed. 

E–2 Version 009B (Web Only) 7850 5104–009

Glossary 

A 

ACID properties 

The essential attributes of transaction processing systems. See also TransIT Open/OLTP 

Transaction Manager (OLTP-TM2200). 

alias 

AMS 

• Atomicity: All changes a transaction makes to a database are made permanent or all 

are nullified. 

• Consistency: A successful transaction transforms a database from a previous valid 

state to a new valid state. 

• Isolation: Changes that a transaction makes to a database are not visible to other 

operations until the transaction completes its work. 

• Durability: Changes that a transaction makes to a database survive future system or 

media failures. 

A symbolic name defined by the user that can be used in place of an OS 2200 transaction 

code. The alias can be the same as the transaction code or it can be different. See also 

network alias. 

See Autoaction Message System. 

AMS database 

The patterns and associated actions used by the Autoaction Message System that allow it 

to automatically recognize and respond to OS 2200 console messages. 

API 

See application program interface. 

application 

A computer program used for a particular kind of work, such as word processing. This 

term is often used interchangeably with program. 

application program interface (API) 

A set of callable functions or routines that an application programmer can use to request 

and carry out lower-level or common services. 

7850 5104–009 Version 009B (Web Only) Glossary–1

Glossary 

asynchronous transfer mode (ATM) 

An emerging standard for high-speed, cell-switching network services. The ATM standard 

defines an access method that can be used for both local and wide area networking. ATM 

is intended to provide a common, efficient service for communication of data, voice, video, 

and images. 

Autoaction Message System (AMS) 

A component of SMART (residing on OS 2200 system consoles) that provides automatic 

message recognition and corresponding actions to enable the system to run without an 

operator. 

availability 

Continuous operation regardless of failures. Clustering is designed to make client 

applications highly available. 

B 

backup domain controller (BDC) 

One or more computers in a Windows NT domain that maintain a replicated copy of the 

directory database for the domain. The copy is synchronized periodically and 

automatically with the master copy on the primary domain controller (PDC). Backup 

domain controllers can authenticate user logons for a domain. They also can be promoted 

to function as the primary domain controller. See also primary domain controller (PDC) 

and directory database. 

basic input/output system (BIOS) 

Instructions stored on read-only memory that provide the lowest level interface to 

peripheral devices. The BIOS performs an autostart routine that tests for peripheral 

devices on startup. After preparing pointers (interrupt vectors) to allow access to its 

routines by device drivers and application programs, the BIOS loads the operating system 

and passes control to it. 

BDC 

binding 

BIOS 

C 

CA 

See backup domain controller. 

A process that establishes the communication channel between a protocol driver (such as 

TCP/IP) and a network interface card. 

See basic input/output system. 

Abbreviation for channel adapter. 

CA ControlIT 

See ControlIT. 

Glossary–2 Version 009B (Web Only) 7850 5104–009

Glossary 

central electronics complex (CEC) 

Comprises the instruction processors, cache complex, main storage units, input/output 

complex, and the system control and operation complex, all housed in a modular set of 

cabinets. 

central processing module (CPM) 

TBS 

CERN 

CGI 

Abbreviation for Conseil Européen pour la Recherche Nucléaire (European Laboratory for 

Particle Physics), the origin of the World Wide Web. CERN is where much of the original 

Web software was developed, including the first Web server and Web browser software. 

See common gateway interface. 

channel service I/O processor (CSIOP) 

A processor that handles input/output operations between instruction processors and 

channels in the 2200 Series component of ClearPath HMP IX servers. 

CHC 

See console hardware cabinet. 

check box 

A small box in a dialog box or property page in Windows NT that can be selected or 

cleared. Check boxes represent an option that you can turn on or off. When a check box 

is selected, an X appears in the box. You clear a check box by clicking it, or by selecting it 

and then pressing the Spacebar. 

classification 

A defined set of component classes that can be monitored simultaneously by Status. A 

classification is independent of a particular SPO Console configuration. 

click 

client 

cluster 

To press and release a mouse button quickly. 

Typically, a desktop personal computer that communicates with other PCs, a server, or a 

host computer. 

A group of independent systems managed as a single system for higher availability, easier 

manageability, and greater scalability. See also resilient cluster. 

Cluster Administrator 

Client application in Microsoft Cluster Server (MSCS) used to configure a Windows NT 

cluster and its nodes, groups, and resources. 

COM 

CMOS 

See Component Object Module 

See complementary metal-oxide semiconductor. 


Glossary 

CMS 1100 

Software that provides and manages all communications into and out of OS 2200 host 

computers. CMS 1100 enables communication between applications on an OS 2200 host 

and 

• Applications on other processors, including other OS 2200 hosts 

• Users on networks to which CMS 1100 has access 

common gateway interface (CGI) 

(1) A standard that defines the mechanism by which Web server software communicates 

with executable programs on the Web server. This enables the Web server software to call 

executables to help fulfill requests. (2) A standard that defines the use of environment 

variables set by a server program before it transfers data to an executable program. The 

environment variables are available to both the server program and the executable 

program and govern how data is transferred between the programs. 

complementary metal-oxide semiconductor (CMOS) 

A semiconductor device made up of two metal-oxide semiconductor transistors (each a 

different type), integrated on a single silicon chip. Such devices run at very high speeds 

and have extremely low power requirements. The Intel and custom processors in 

ClearPath IX servers use CMOS technology. 

component class 

A group of similar components, such as hosts, instruction processors, or processes 

monitored by Single Point Status. All components within a class have the same attributes. 

component group 

A collection of components that a site has decided to represent as a single icon in the 

status diagram of Single Point Status. Components in a component group are selected 

based on the name of the component, the class of the component, and the host on which 

the component resides. 

Component Object Model (COM) 

The object-oriented programming model that defines how objects interact in a single 

application or between applications. In the COM model, client software accesses an object 

through a pointer to an interface (a related set of functions called methods) on the object. 

configuration 

A definition of the host systems that SPO/HMP Console monitors and controls. The 

definition also specifies the means of connection for each system. 

console hardware cabinet (CHC) 

A stand-alone cabinet that houses console hardware, including System Control Facility 

(SCF) PCs, a monitor, the monitor concentrator (switchbox), keyboard, and mouse, and 

the SPO server for the ClearPath IX server. 

ControlIT 

ControlIT is a secure application for controlling remote Windows systems through 

network access, dial-up, or the Internet. ControlIT is a Computer Associates (CA) product. 

CPM 

See central processing module. 


CSIOP 

D 

DAC 

daemon 

datagram 

See channel service I/O processor. 

Abbreviation for disk array controller. 

Glossary 

A background process, often perpetual, that performs a system-wide public function. 

Daemons run on the Single Point Operations (SPO) server in the background and perform 

various services, including the management of all network activity pertaining to SPO/HMP 

Console. The daemons must be running in order to run SPO/HMP Console. 

A self-contained, independent entity of data (such as a piece of a message) that carries 

sufficient information to be routed from a source to a destination computer without 

reliance on earlier exchanges between the source and destination. Each datagram, 

because it contains a source, a destination, and a data packet, can follow a different route 

to the destination. 

Data Management System (DMS 2200) 

The CODASYL-based data manager that provides a fixed network database model. 

DCOM 

See Distributed Component Object Module. 

DCOM/OLE Gateway (DGate) 

A gateway supplied with the WebTx software that enables users to access OS 2200 

applications from a Distributed Component Object Model (DCOM) environment. DGate is 

available for the Windows NT environment of ClearPath IX servers. 

directory database 

A shared database of security information in a Windows NT domain that contains user 

account names, passwords, and security settings. The computer designated as the primary 

domain controller (PDC) contains the master copy of the database. Replicated copies are 

hosted on one or more backup domain controllers (BDC) and are synchronized 

periodically and automatically with the master copy. 

directory service agent (DSA) 

The server component defined in the X.500 standard for global directories. The DSA 

executes requests from directory user agents (DUA) to read and update the directory 

entries on the global directory server. 

directory user agent (DUA) 

The client component defined in the X.500 standard for global directories. An application 

on a client workstation uses a local DUA to read and update the directory entries on a 

global directory server. 


Glossary 

disk mirroring 

Fault-tolerant technique that writes data simultaneously to two disks using the same disk 

controller. The disks operate in tandem, constantly storing and updating the same files. 

Mirroring alone does not ensure data protection. If both disks fail at the same time, data is 

still lost. 

Distributed Component Object Model (DCOM) 

The Microsoft model for distributed object computing. The nondistributed component 

object model (COM) is the technology underlying Object Linking and Embedding (OLE). 

DCOM extends this technology to multisystem usage and is the technology underlying 

ActiveX technology. 

distributed transaction processing (DTP) 

(X/Open) A form of processing in which multiple application programs update multiple 

resources (such as databases) in a coordinated manner. Programs and resources can 

reside on one or more computers across a network. See also global transaction, X/Open 

Distributed Transaction Processing model. 

DLL 

DNS 

domain 

See dynamic link library. 

See domain name system. 

In Windows NT, a collection of computers (defined by the network administrator) that 

share a common directory database. Each domain has a unique name. Users have only 

one account in the domain, thus simplifying sign-on and administration. Users log on to 

the domain, not to individual servers in the domain. See also directory database and 

domain controller. 

domain controller 

A computer in a Windows NT Server domain that uses information in the directory 

database to manage all aspects of user-domain interactions, including authentication of 

users logging on to domain accounts. A domain has one primary domain controller (PDC) 

and one or more backup domain controllers (BDC). See also directory database, primary 

domain controller (PDC), backup domain controller (BDC), and member server. 

domain name 

A hierarchical name that identifies a host system or portion of a network in a TCP/IP 

environment. Each domain name is composed of subnames or labels that identify 

successive levels in a tree structure. A name that includes the local host name and all 

levels (for example, hlcnt.rsvl.unisys.com) is referred to as a fully qualified domain name. 

domain name system (DNS) 

(Also domain name server) The mechanism that implements a hierarchical naming scheme 

known as domain names for TCP/IP networks. A domain name consists of a sequence of 

subnames separated by periods that identify successive levels in directory structure. This 

system maps host names to IP addresses. 

DRS 

Abbreviation for disk-resident system. 


DSA 

DSPER 

DTP 

DUA 

See directory service agent. 

Acronym for Diagnostic Peripheral Equipment Routines. 

See distributed transaction processing. 

See directory user agent. 

Glossary 

dynamic link library (DLL) 

A separate file containing executable routines and functions that are loaded into memory 

only when called by a program. DLLs are used for common functions that are needed by 

more than one program. 

E 

EBRS 

EDI 

EISA 

Abbreviation for Enterprise Backup and Restore Software. 

See electronic data interchange. 

Abbreviation for extended industry-standard architecture. 

electronic data interchange (EDI) 

The ability to transmit business documents, such as purchase orders and invoices, 

electronically over a network. The goal is to streamline conventional ordering and billing 

processes by eliminating the need for paper forms and mail delivery. To be able to 

implement EDI, users must agree on standards for formatting and exchanging information. 

See also X.400. 

Ethernet 

F 

A widely implemented type of local area network (LAN) in which devices are connected to 

a single network cable in a bus configuration. Any device can transmit as long as no other 

devices are transmitting. In the event of a collision, an algorithm ensures that the two 

devices do not transmit again at the same time. Ethernet, developed by the Xerox Palo 

Alto Research Center in 1976, is the basis for the IEEE 802.3 standard for LANs with carrier 

sense multiple access with collision detection (CSMA/CD). 

Fiber Distributed Data Interface (FDDI) 

An American National Standards Institute (ANSI) standard for high-speed data 

transmission using fiber optics technology with devices connected to two concentric fiberoptic 

rings. Because it uses fiber optic cable, FDDI supports higher transmission speeds 

than other LAN technologies, such as Ethernet and token ring. 


Glossary 

file allocation table (FAT) 

A table or list maintained by some operating systems to keep track of the status of various 

segments of disk space used for file storage. Also referred to as the FAT file system. 

File Gateway (FileGate) 

A gateway supplied with the WebTx software that enables you to store static Web pages 

(HTML files) and other text files in the OS 2200 environment of your ClearPath IX server 

and provide them to Web users on your intranet or the Internet. FileGate is available for 

both the Windows NT and UnixWare environments of ClearPath IX servers. 

file transfer protocol (FTP) 

A service supporting file transfers between local and remote systems that support this 

protocol. FTP supports several commands that allow bidirectional transfer of binary and 

ASCII files between systems. 

fourth-generation language (4GL) 

Programming environments that streamline the application development process by 

allowing programmers to focus more on the results desired and less on the specific 

programming techniques required to process the data. LINC and MAPPER are examples of 

fourth-generation languages. 

FTP 

G 

gateway 

See file transfer protocol. 

A device that performs data conversions to enable interconnections between dissimilar 

networks. A router is an example of a gateway. See also WebTx gateways. 

global transaction 

A single unit of work that is performed by one or more application programs and one or 

more resource managers, possibly on different machines. An application program defines 

the start and end of a global transaction. A transaction manager coordinates a global 

transaction’s initiation and completion (on behalf of an application program) by 

communicating with participating resource managers. An application program can also 

perform work outside of any global transaction (a nonglobal transaction). See also 

distributed transaction processing (DTP) X/Open Distributed Transaction Processing 

model. 

group 

In UnixWare, a file ownership mechanism that allows files or user-ids to be grouped for the 

purpose of granting file access permissions (for example, read, write, or execute). 

guest account 

On computers running Windows NT Workstation or Windows NT Server, a built-in account 

used for logons by people who do not have a user account on the computer or domain or in 

any of the domains trusted by the computer’s domain. 

GUI 

Abbreviation for graphical user interface. 


H 

HBA 

Abbreviation for host bus adapter. 

Glossary 

heartbeat 

Message that is sent regularly by the Cluster Service on one node in a cluster to the Cluster 

Service on an alternate node to detect failure. 

heterogeneous multiprocessing (HMP) 

A Unisys computing paradigm in which multiple dissimilar processors (for example, Intel 

and custom CMOS processors) and operating system kernels (for example, Windows NT 

and OS 2200) execute as a single server. 

High-Performance Transaction Processing Interconnect (HTP/ic) 

System software that provides the underlying connection between the ClearPath HMP 

Windows NT node and the custom node for Open/OLTP client/server applications using the 

FDDI link. HTP/ic facilitates communication to the HTP/x product and ultimately, the 

Open/OLTP product on the custom node. HTP/ic is based on XATMI and OSI TP 

standards. 

High-Performance Transaction Processing for XATMI (HTP/x) 

Unisys system software that supports the transaction processing protocols as defined in 

ISO/IEC 10026-3. These protocols allow heterogeneous computer systems to communicate 

in support of distributed transactions. The HTP/x interface supports access to the OSI-TP 

functions required by the X/Open CAE specification of the XATMI Application 

Programming Interface (XATMI API) and provides services to 

• Initiate and accept or reject remote service requests both inside and outside of a global 

transaction 

• Send and receive data 

• Prepare, commit, and roll back transactions. 

High-Volume Transaction Processing (HVTIP) 

An OS 2200 product used for applications that require a high rate of throughput and whose 

processing can pass through an arbitrary sequence of subprograms. To maximize 

performance, modular programs are executed in sequence from a special area of main 

storage dedicated to Transaction Processing (TIP) applications. An HVTIP program library 

is a TIP user file designated (through the TPUR utility) as a container for HVTIP program 

banks. See also Transaction Processing (TIP). 

HMP 

See heterogeneous multiprocessing. 

HMP Workstation 

A PC, running Windows NT Workstation, that an operator uses to monitor and control all 

nodes of a ClearPath IX server. X terminal emulation allows display of SPO/HMP Console 

screens on the workstation for monitoring and control. Software hosted on the 

workstation allows system management, system administration, and the viewing of user 



Glossary 

hosts file 

HTML 

HTP/ic 

HTP/ix 

HTTP 

HVTIP 

The TCP/IP network configuration file that identifies the network addresses (IP addresses) 

of other hosts on the network. 

See Hypertext Markup Language. 

See High-Performance Transaction Processing Interconnect. 

See High-Performance Transaction Processing for XATMI. 

See hypertext transfer protocol. 

See High-Volume Transaction Processing 

HyperText Markup Language (HTML) 

The language used to tag the various structures of a document, such as headings and lists, 

so Web browsers can apply formatting rules to display the document’s contents and related 

graphics. HTML allows authors to define hypertext links between locations in the same 

document, between documents, and between documents and multimedia objects. 

hypertext transfer protocol (HTTP) 

The primary protocol for transferring data over the Web. HTTP uses a simple algorithm 

that makes fast response times possible compared to earlier protocols, such as FTP. 

I 

IANA 

IIS 

See Internet Assigned Numbers Authority. 

Abbreviation for Microsoft Internet Information Server. 

instruction processor (IP) 

The central processing unit for execution of program and system software instructions. 

The instruction processor executes instructions, initiates input/output operations, and 

obtains instructions and data from main storage. 

integrated Operating Environment (IOE) 

The foundation software bundled with ClearPath HMP Series servers. The IOE includes 

operating systems, a database manager, online transaction processing (OLTP) software, 

integrated administration and operations software, integrated printing software, and 

application development software. 


Glossary 

Integration Expert 

The online integration assistant for effectively using ClearPath IX servers and creating 

solutions for business problems. Integration Expert (formerly PathMate) contains a 

Windows Help application that explains and runs the other built-in components including a 

package of tools, working prototype solutions, procedures, and product configuration aids. 

Intel node 

A computer in a ClearPath IX server that uses Intel processors and supports either 

Windows NT or UnixWare operating systems. A ClearPath IX server can contain from one 

to four Intel nodes. See also node, Windows NT node, and UnixWare node. 

Intel processing complex cabinet (IPCC) 

The cabinet housing the Intel nodes in a ClearPath IX server. See also Intel node. 

interconnect 

Private network that connects nodes in a ClearPath IX server. See also internal LAN. 

internal LAN 

The link that provides a private interconnect between nodes in a ClearPath IX server. 

Internet protocol (IP) addresses assigned to the nodes are from a block of addresses 

reserved for private internets by the Internet Assigned Numbers Authority (IANA). 

Internet Assigned Numbers Authority (IANA) 

The central coordinator for assigning new Internet-wide IP addresses and other unique 

parameter values for Internet protocols such as domain names, port numbers, and 

management information base (MIB) object identifiers. 

internet protocol (IP) 

The routing or network layer of the TCP/IP architecture. IP is based on MIL–STD-1777 

specifications for the Defense Data Network system. IP is a connectionless datagram 

protocol that routes data to host systems within a complex system of multiple network 

nodes and interconnected networks. 

interrupt request lines (IRQ) 

Hardware lines over which devices can send signals to get the attention of the processor 

when the device is ready to accept or send information. 

intranet 

IOE 

IP 

A private, enterprise-wide network that uses TCP/IP and Web technologies. 

See Integrated Operating Environment. 

See instruction processor and TCP/IP. 

IP address 

The 32-bit address assigned to hosts in a TCP/IP internet. An IP address identifies the 

network to which a host is attached, as well as a specific host on that network. The IP 

address usually is represented in dotted decimal notation (for example, xxx.xxx.xxx.xxx) 

with each part (xxx) being a decimal number from 0 to 255 (represented by 8 bits). 


Glossary 

IP Address resource 

A 32-bit number in dotted decimal format that represents an internet protocol (IP) address 

that is supported as a cluster resource by MSCS. 

IPCC 

IRQ 

ISO 

J 

See Intel processing complex cabinet. 

See interrupt request lines. 

Abbreviation for International Organization for Standardization. 

Java Gateway (JGate) 

A gateway supplied with the WebTx software that enables you to manipulate applications 

in the OS 2200 environment of your ClearPath IX server with Java applets that can be 

accessed by Web users on your intranet or the Internet. These applets use the WebTx Java 

class library. JGate is available for both the Windows NT and UnixWare environments of 

ClearPath IX servers. 

L 

local area network (LAN) 

A data communications network that enables computers, terminals, and other data 

processing resources, typically at one location, to communicate with each other. 

logging 

log on 

M 

See Single Point Logging. 

To provide a user name and password that identify you to the network. 

management information base (MIB) 

A set of objects in a database that represents various types of information about a device. 

These objects can be used by a network management protocol (for example, SNMP) to 

manage the devices in a network. The entire set of objects that any service or protocol 

uses is referred to as its MIB. See also simple network management protocol (SNMP). 

MAPI 

See Messaging Application Program Interface. 


Glossary 

master configuration table (MCT) 

A table built at system generation to reflect the system configuration. The MCT is an Exec 

file that primarily contains system configuration information. Audit control and 

Transaction Processing (TIP) use the MCT for recovery information. The MCT is recreated 

on tape recovery boots. 

master system console 

The single system console that supports an Exec logical console for one partition and that 

has full System Control Facility (SCF) control capabilities including partitioning, 

initializing, booting, and maintaining. 

MCB 

MCT 

See Message Control Bank. 

See master configuration table. 

member server 

A computer running Windows NT Server that has been installed as a stand-alone server in a 

Windows NT domain rather than as a primary or backup domain controller. 

Message Control Bank (MCB) 

A Unisys software product that interfaces with the Communications Management System 

(CMS 1100) and transaction programs to provide message recovery and transaction 

scheduling. 

message store 

The software component of an X.400 mail system that accepts messages from message 

transfer agents (MTA) and stores them until they are retrieved by remote user agents 

(RUA). 

message transfer agent (MTA) 

The software component of an X.400 mail system that cooperates with other MTAs to 

perform store-and-forward message delivery. 

Messaging Application Program Interface (MAPI) 

A Windows dynamic link library (DLL) that provides Windows applications with access to 

e-mail, message store, and address book services through a set of API calls. The service 

provider can be any MAPI-compliant messaging software, such as Microsoft Mail. 

MIB 

See management information base. 

Microsoft Access 

A relational database application for the Windows 95, Windows 98, Windows 2000, and 

Windows NT environments. It can integrate data from spreadsheets and other databases, 

support queries, and produce reports. 


Glossary 

Microsoft Cluster Server (MSCS) 

A product that provides resiliency for applications in the Windows NT environment. MSCS 

software uses a clustering architecture that enables a group of independent Windows NT 

systems to work as a single system, allows the end user to interact with the cluster as a 

single server, keeps server-based applications highly available regardless of individual 

component failure, and provides high availability of resources, including data and 

applications. 

Microsoft Excel 

A spreadsheet application for the Windows 95 and Windows NT environments. It supports 

basic operations, formula creation, formatting, printing, and charting. 

Microsoft Internet Explorer 

A popular Web browser developed by Microsoft Corporation. 

Microsoft Internet Information Server (IIS) 

A Web server integrated in the Windows NT Server 4.0 environment that provides 

enhanced performance and management features to make administering your Internet or 

intranet site easier. 

Microsoft Transaction Server (MTS) 

A product that enables developing and deploying high-performance, scalable, and reliable 

distributed applications. MTS combines the technology of component-based development 

and deployment environments with the reliability and scalability of transaction processing 

monitors. See also Microsoft Transaction Server component. 

Microsoft Transaction Server component 

A COM component that executes in the Microsoft Transaction Server (MTS) run-time 

environment. An MTS component must be a dynamic link library (DLL), implement a class 

factory to create objects, and describe all the component’s interfaces in a type library for 

standard marshaling. 

Microsoft Visual Basic 

A programming system that allows users to rapidly create applications having a graphical 

user interface (GUI) for the Microsoft Windows environment. 

middleware 

Software required to support interactions between clients and servers. Examples of 

middleware are TCP/IP software, NetWare, remote procedure call (RPC) software, Open 

Database Connectivity (ODBC) drivers, and client software for accessing distributed 

transaction processing (DTP) applications. 

mount 

MTA 

To integrate the local directory structure of a physical disk partition into the overall SVR4 

directory hierarchy. 

See message transfer agent. 


N 

NAS 

NetBIOS 

See network access server. 

See Network Basic Input/Output System. 

Glossary 

Netscape Enterprise Server 

A high-performance, secure, World Wide Web (WWW) platform for creating, managing, and 

intelligently distributing information and live, online applications. 

NetWare 

A popular network operating system (NOS) that enables client systems to share files and 

resources (such as printers) on servers. 

network access server (NAS) 

A hardware component that connects one or more serial devices to a LAN. 

network alias 

An alias, or equivalent name, for a network host name in the hosts file. 

Network Basic Input/Output System (NetBIOS) 

An application program interface (API) used in Windows NT, Ethernet, and token ring 

networks to provide computer name-to-IP address resolution functions for LANs. 

Windows Internet Name Service (WINS) is a NetBIOS name service for Windows NT. See 

also Windows Internet Name Service. 

Network File System (NFS) 

Client/server middleware that provides client workstations with access to files on a server 

over a network. The files appear to clients much like local files. 

network interface card (NIC) 

An expansion card or other device used to connect a computer to a local area network 

(LAN). Also called a network card, network adapter card, network adapter, or adapter 

card. 

network interface module (NIM) 

A module that connects the processing complex cabinet (PCC) with the SCF for system 

operations. 

network segment 

A part of an Ethernet network on which all message traffic is common to all nodes. 

Specifically, a message broadcast from one node is received by all other nodes on the 

segment, typically because the segment is a continuous conductor. 

NFS 

NIC 

See Network File System. 

See network interface card. 


Glossary 

NIM 

node 

NTFS 

O 

See network interface module. 

In a ClearPath HMP IX context, an instance of an operating system running on a computer. 

A ClearPath HMP IX server can include one to four Windows NT nodes or UnixWare 

nodes, in any combination (for example, three Windows NT nodes and one UnixWare 

node) and two OS 2200 nodes (where a single 2200 hardware device is partitioned into 

separate nodes). 

See Windows NT File System. 

Object Linking and Embedding (OLE) 

A feature of Microsoft Windows applications that allows applications to work together to 

share data and create compound documents. 

ODB 

ODBC 

OLTP 

See operations database. 

See Open Database Connectivity. 

See online transaction processing. 

OLTP-TM2200 

See TransIT Open/OLTP Transaction Manager. 

online transaction processing (OLTP) 

A high-performance type of application characterized by a service request from a user 

immediately followed by an action and response from a server system. A complete 

request-response cycle is called a transaction. OLTP systems must meet certain criteria, 

called ACID properties (atomicity, consistency, isolation, and durability), to maintain the 

integrity of the data and ensure that transactions are executed correctly. 

OPE 

See Open Programming Environment. 

Open Database Connectivity (ODBC) 

A Microsoft call level interface for Structured Query Language (SQL) that has become a de 

facto standard. ODBC is an extended version of the call level interface defined by the SQL 

Access Group (SAG), a consortium of database vendors. ODBC middleware enables 

Windows database clients to interoperate with a variety of server databases that would 

otherwise be incompatible. 

Open Network Computing (ONC) 

A distributed applications architecture. 


Glossary 

Open/OLTP Pathway 

An Open/OLTP middleware component that provides applications in the Intel (UnixWare 

or Windows NT) environment of a ClearPath IX server with a gateway to the Open/OLTP 

Transaction Manager in the OS 2200 environment. This allows Windows NT or UnixWare 

applications to execute transactions against OS 2200 databases. 

Open Programming Environment (OPE) 

The Unisys implementation of the SVR4 environment. OPE is not a product but rather an 

optional programming environment available in the OS 2200 operating environment of a 


Open Systems Interconnect Transaction Processing (OSI TP) 

An ISO standard (ISO/IEC 10026-2) for protocols and services that establish dialogues and 

pass messages between client programs and service routines on different computers. 

operations database (ODB) 

A database populated with information unloaded from the Site Configuration Management 

System (SCMS) database. The ODB contains configuration information needed by the OS 

2200 Exec to operate 2200 Series component hardware. 

OSI 

Abbreviation for Open Systems Interconnection. 

OSI-MHS 

Abbreviation for Open Systems Interconnection Message Handling System. 

P 

Packet Internet Groper (PING) 

A command used to verify connections to one or more remote hosts. The PING utility uses 

the Internet Control Message Protocol (ICMP) echo request and echo reply packets to 

determine whether a particular IP system on a network is functional. The PING utility is 

useful for diagnosing IP network or router failures. 

parity 

An extra bit added to a group of bits (for example, a byte or a word) to reveal errors in data 

storage or transmission. 

partition databank (PDB) 

A data structure passed by the System Control Facility (SCF) to the Exec that contains all 

the necessary information for the Exec to operate the hardware in the partition. The PDB 

is used to build the I/O, tape translator, and other sections of the master configuration 

table (MCT). The partition databank is created by the SCMS partitioning function. 

PathMate 

See Integration Expert. 

PCC 

See processing complex cabinet. 


Glossary 

PDB 

PDC 

See partition databank. 

See primary domain controller. 

Peripheral Component Interconnect (PCI) 

Local bus for personal computers that provides a high-speed data path between the 

processor and peripheral devices. 

PERL 

Abbreviation for Practical Extraction and Report Language. A scripting language that 

makes it easy to perform string-manipulation and parsing tasks. Common gateway 

interface (CGI) scripts are often written in PERL. 

physical disk resource 

SCSI-attached disk for containing shared folders or storage, which is supported as a cluster 

resource in an MSCS cluster. 

PING 

POST 

See Packet Internet Groper. 

Acronym for power-on self-test. 

possible owners 

A list that specifies which nodes in the cluster are capable of running that resource. By 

default, both nodes appear as possible owners, so the resource can run on either node. In 

most cases, it is appropriate to use this default setting. If you want the resource to be able 

to fail over, both nodes must be designated as possible owners. 

preinstalled 

Installed on the computer at the factory. Software that is preinstalled must first have been 

preloaded. It must be configured at the site, but it does not have to be either loaded or 

installed. 

preloaded 

Copied to the hard drive of the computer at the factory. The software must be installed at 

the site but does not have to be copied from the installation CD-ROM. 

primary domain controller (PDC) 

The computer running Windows NT server that directly receives and tracks changes to the 

directory database in a Windows NT domain. Both primary and backup domain controllers 

can authenticate user logons. A backup domain controller can be promoted to function as 

the PDC. See also backup domain controller (BDC) and directory database. 

private network 

A TCP/IP network that supports only node-to-node communication within an enterprise 

and does not require access to hosts in other enterprises or to the Internet at large. 

Typically, the IP addresses assigned to hosts in such a network would be allocated from 

blocks of IP addresses reserved for private networks by the Internet Assigned Numbers 

Authority (IANA). See also public network. 


Glossary 

processing complex cabinet (PCC) 

A single cabinet that can include one or two 2200 Series system instruction processors and 

one or two main storage units completely independent from each other. 

protocol 

A set of rules or standards describing methods to achieve compatible transmission and 

receipt of data (for example, message packets) over a network. 

protocol port 

The abstraction that transport protocols use to distinguish between multiple destinations 

within a host computer. TCP/IP protocols identify ports using small positive integers. 

Usually, the operating system allows an application program to specify which ports it 

wants to use. Some ports are used for standard services (for example, electronic mail). 

public network 

A TCP/IP network that supports communication within the Internet at large. Hosts in a 

public network must have globally unique IP addresses assigned by an Internet Registry. 

Q 

quorum 

Voting mechanism used to guarantee that specific data necessary for recovery can be 

maintained consistently between all cluster members. 

quorum resource 

A resource, accessible by all nodes of a cluster, that stores cluster management data such 

as recovery logs for changes made to cluster data. 

R 

RAS 

Abbreviation for reliability, availability, and serviceability. 

RDMS 2200 

See Relational Data Management System. 

redundant array of independent disks (RAID) 

(Originally, redundant array of inexpensive disks, or devices.) Multiple disk units 

combined into a single logical device designed to increase data integrity and availability by 

means of redundant copies of disk contents. Organization of the disks is defined by six 

RAID levels—two of which (levels 1 and 5) are fault tolerant. In level 1 (disk mirroring) 

disks are duplicated 100 percent on another disk for redundancy. In level 5 (striping with 

parity) free space across multiple disks is combined into one logical volume and data is 

spread in a fixed order across those disks (striping). Parity data saved with the striped 

data allows information to be recreated if a disk should fail. 

Relational Data Management System (RDMS 2200) 

The Unisys relational data manager that provides a nonhierarchical database model. 


Glossary 

ReliantHA 

See SCO ReliantHA. 

remote procedure call (RPC) 

A client/server mechanism that enables processes on client systems to execute procedures 

stored on remote systems. On the client side, the RPC software encapsulates the 

parameters for a procedure call in a message and sends the message to a server. The 

server unpacks the parameters, calls the procedure, and sends a response to the client. 

From the application program’s perspective, remote procedures are indistinguishable from 

local procedures because they are called in the same manner. 

remote user agent (RUA) 

The client software of an X.400 mail system that provides remote users with access to a 

message store. 

resilient cluster 

Two or more Intel nodes, shared disk drives, and multiple (redundant) physical and virtual 

network connections that make system resources highly available to clients. To the end 

user, the resources appear to be available from a single system. Cluster software can 

automatically detect failure of hardware or an application on one node and restart the 

application on the other (surviving) node of the cluster with little noticeable interruption of 

service. See also cluster. 

resource 

RFU 

router 

RPC 

RUA 

S 

SBCON 

SCF 

SCMS 

An object that can be migrated between systems in a cluster. File systems and virtual IP 

addresses are examples of resources. 

Abbreviation for ready for use. 

A hardware device used to transfer packets of data from one logical network to another, in 

the TCP/IP protocol. 

See remote procedure call. 

See remote user agent. 

Abbreviation for single-byte command code set connection. 

See System Control Facility. 

See Site Configuration Management System. 


Glossary 

SCO UnixWare 

A popular version of SVR4. UnixWare software combines Symmetrical Multi-Processing 

(SMP) technologies from Unix System Laboratories, Inc. (USL), enhancement by Novell, 

Inc., and solution delivery from The Santa Cruz Operation, Inc. (SCO). SCO UnixWare has 

improved reliability and price/performance ratios. 

SCP 

SCSI 

SCU 

SDF 

SDK 

Abbreviation for Software Controlled Performance. 

See small computer system interface. 

See system configuration utility. 

See site data facility. 

Abbreviation for site development kit. 

shared resource 

Cluster organization in which some resources are accessible to all nodes in the cluster. 

shared SCSI bus 

Each shared storage bus attaches one or more disks that hold data used either by server 

applications running on the cluster or by applications for managing the cluster. MSCS 

currently supports only SCSI shared–storage buses. Each disk on the shared SCSI bus is 

owned by only one node of the cluster. The ownership of disks moves from one node to 

another when the disk group fails over or moves to the other node. 

shell 

The command interpreter that passes commands to SVR4. The most common shells are 

the c shell and the Bourne shell. 

shell script 

A collection of commands stored in a file that can be executed as input to the shell (similar 

to batch file commands in MS-DOS). 

simple network management protocol (SNMP) 

A protocol for transporting management data between networked devices and 

applications, typically from a variety of vendors, and systems or applications that monitor 

or control those devices and applications in a TCP/IP-based network. See also SNMP 

agent. 

Single Point Operations (SPO) 

Unisys software that enables you to monitor and operate multiple systems from one 

location by gathering operations-related information over a network. This information is 

presented in a window environment. The displayed information can include exact 

replications of one or more system console displays and remote terminal sessions. 


Glossary 

Single Point Autoaction Message System (SP-AMS) 

A program that runs on the SPO server and provides automatic message recognition and 

corresponding actions while monitoring ANSI X3.64-compliant (UNIX) host systems and A 

Series host systems. Contrast with Autoaction Message System. 

Single Point Logging 

A SPO Console capability that enables a user to store, in log files at a central location, an 

electronic history of messages from selectable message sources (managed host systems, 

SPO Console, and external applications). 

Single Point Status 

A capability of Single Point Operations that lets a user monitor the status of hardware and 

software components across multiple host systems. See also Status feature. 

Site Configuration Management System (SCMS) 

Software that runs on a site data facility (SDF) PC that is part of the System Control 

Facility (SCF). SCMS is used to configure system and partition definitions of hardware at a 

site. Information from the SCMS database includes an operations database (ODB) and a 

partition databank (PDB). The ODB and PDB give the Exec the information needed to 

operate the system hardware. The PDB is used to build several areas of the master 

configuration table (MCT). 

site data facility (SDF) 

The personal computer hosting SCMS in the System Control Facility (SCF). 

small computer system interface (SCSI) 

A protocol for connecting devices from several classes of peripherals to a host system 

without requiring modifications to hardware and software. 

SMTP 

Abbreviation for simple mail transfer protocol. See also SMTP address. 

SMTP address 

A simple mail transfer protocol (SMTP) address that uses the following Internet protocol 

for an e-mail address: 

[SMTP:address] 

For example, 

[SMTP:jdoe@site.com] 

SNMP 

See simple network management protocol. 

SNMP agent 

A software component on a network node that collects information and performs network 

management functions on behalf of authorized SNMP managers. Communications 

Management System (CMS 1100) includes SNMP agent software, which allows OS 2200 

hosts to respond to requests for managed information by SNMP network managers. 

socket 

A software abstraction that provides the interface between application programs and 

communications software. 


Glossary 

Software Controlled Performance (SCP) 

A software feature that controls OS 2200 performance by means of an Exec key that 

authorizes the number of IPs the system may use and the performance level (a percentage 

of the maximum possible performance) at which the IPs may run. 

SP-AMS 

See Single Point Autoaction Message System. 

SP-AMS database 

The patterns and associated actions used by the Single Point Autoaction Message System 

that allows it to automatically recognize messages from UnixWare and A Series host 

systems and respond to these messages. 

SPO 

See Single Point Operations. 

SPO Console 

A software application that enables a user to monitor and control multiple host systems 

from a single workstation. 

SPO Console/Enterprise Server Edition (ESE) 

The full-featured version of SPO Console capable of monitoring and controlling OS 2200, A 

Series, UnixWare, and Windows NT systems. 

SPO/HMP Console 

A restricted version of SPO Console, specifically adapted to monitor and control a single 


SPO server 

The SVR4 hardware platform on which SPO Console runs. 

SQL 

See Structured Query Language. 

static load balancing 

Manually moving a group between nodes of a cluster to manually balance the load across 

two nodes. 

static page 

A document object in the form of a file. The file can contain any type of data, such as text, 

graphic images, video, or audio. It is not an executable program file. 

Status feature 

A feature of SPO Console/ESE that allows a site to define additional classifications for use 

by Single Point Status and that allows new classes and attributes to be defined in 

classifications provided with SPO Console. 

Structured Query Language (SQL) 

A specialized language for defining, retrieving, changing, and maintaining data in 

databases. End users can use SQL to perform ad hoc, interactive queries. Programmers 

can include SQL statements in applications written with high-level languages, such as C, 

C++, and COBOL. 


Glossary 

subnet 

A portion of a network, which may be a physically independent network segment, that 

shares a network address with other portions of the network and is distinguished by a 

subnet number. A subnet is to a network what a network is to an internet. 

superuser 

A privileged account with unrestricted access to all commands and all files regardless of 

permissions. The user name of this account is root. 

system configuration utility (SCU) 

A software utility used to configure Intel nodes that support Extended Industry Standard 

Architecture (EISA) expansion boards. 

system console 

A general term applying to any System Control Facility (SCF) workstation. System 

consoles are used for system operations (Exec logical console) and system control 

(partitioning, initializing, booting, and maintaining). 

System Control Facility (SCF) 

A set of workstations, connected in a local area network, that provides an operator 

interface to a ClearPath IX server. The SCF provides system operator console and system 

control functions through a minimum of two workstations. System configuration 

functions are provided through the workstation on which the Site Configuration 

Management System (SCMS) runs (referred to as the site data facility, or SDF). 

T 

TAS 

TCP 

TCP/IP 

Acronym for TCP/IP Application Services. 

See transmission control protocol. 

See transmission control protocol/internet protocol. 

third-generation language (3GL) 

High-level programming languages such as C, COBOL, and FORTRAN. 3GLs hide much of 

the complexity of machine processing from programmers, allowing them to focus more on 

the problem to be solved. Programs written in 3GLs are more machine-independent than 

programs written in assembly (second-generation) languages. 

TIP 

See Transaction Processing. 


Glossary 

token ring 

A type of local area network (LAN) in which devices are connected to a network cable in a 

ring configuration. Before devices can transmit, they must possess a logical token, which 

is passed from device to device in sequence around the ring. When a device has something 

to transmit, it labels the token as busy until the transmission is complete. When the 

transmission is complete, the token is labeled not busy and the token is again passed 

around the ring. The IEEE 802.5 standard defines a token ring type of network. 

transaction 

A complete unit of work that transforms a database from one consistent state to another. 

In distributed transaction processing (DTP), a transaction can include multiple units of 

work performed on one or more systems. See also ACID properties, global transaction, 

X/Open Distributed Transaction Processing model. 

Transaction Processing (TIP) 

The Unisys software that provides a form of immediate data processing in which user 

requests are entered directly at the terminal and online programs satisfy the requests (for 

example, by updating database files and displaying output messages). An OS 2200 

transaction processing environment is also called a TIP environment. See also High- 

Volume Transaction Processing (HVTIP). 

TransIT Open/OLTP Transaction Manager (OLTP-TM2200) 

The Unisys implementation of an X/Open compliant transaction manager (TM) in the OS 

2200 environment. OLTP-TM2200 software provides an open, standards-compliant 

environment for developing distributed transaction processing (DTP) applications. See 

also ACID properties, global transaction, online transaction processing (OLTP), X/Open 

Distributed Transaction Processing model, TUXEDO Transaction Manager. 

transmission control protocol (TCP) 

A connection-oriented transport-layer protocol in the TCP/IP suite of protocols. TCP 

provides end-to-end reliability, error recovery, and multiplexing for the upper-layer 

protocols. TCP/IP applications such as simple mail transfer protocol (SMTP), file transfer 

protocol (FTP), and TELNET use TCP. 

transmission control protocol/internet protocol (TCP/IP) 

An open systems network architecture and set of communications protocols. It was 

developed by the U.S. Department of Defense to promote compatibility among US military, 

government, and research communications networks. It has since become popular in the 

private sector as a method of interconnecting systems from different vendors on local area 

networks (LAN) and wide area networks (WAN). 

Transport Service Access Method (TSAM) 

A program interface that allows Unisys and user-written applications to access the 

communications services of CMS 1100 at the transport layer. TSAM provides access to the 

CMS 1100 DCA, OSI, and TCP/IP protocol stacks. 

tuning script 

An initialization program (supplied by Unisys), written in Bourne shell script, that is run to 

initialize kernel parameters, partition disks, and install software. 


Glossary 

Tuxedo 

A software product that is based on the X/Open model for distributed transaction 

processing (DTP). Tuxedo was developed by AT&T, sold to Novell, and is currently owned 

by BEA Systems. Tuxedo and other X/Open compliant DTP software (including the Unisys 

product TransIT Open/OLTP) allows organizations to develop applications that execute 

transactions across multiple systems and database types. 

TUXEDO Gateway (TUXGate) 

A gateway supplied with the WebTx software that enables you to make TUXEDO 

transactions in the Windows NT environment of your ClearPath IX server available with 

the Web interface over your intranet or the Internet. TUXGate is available for the Windows 

NT environment of ClearPath IX servers. 

U 

UDP 

See user datagram protocol. 

Uniform Resource Locator (URL) 

A unique reference locating a file on the World Wide Web (WWW). An example of a URL is 

http://www.si.edu/start.htm 

Universal Data System (UDS) 

An expandable, modular collection of related Unisys products for database management in 

an integrated recovery environment. UDS supports three database management software 

products: Data Management System (DMS 2200), Relational Data Management System 

(RDMS 2200), and Shared File System (SFS 2200). 

UnixWare 

See SCO UnixWare. 

UnixWare node 

An instance of UnixWare running in a ClearPath IX server. See also node and Intel node. 

unmount 

URL 

URM 

To remove the local directory structure of a physical disk partition from the overall SVR4 

directory hierarchy. 

See Uniform Resource Locator. 

Abbreviation for UNIX Resource Monitor. 

URM agent 

A program of the Event Server API that sends event reports from a managed SVR4 system 

to Single Point Status running on the SPO server. 


Glossary 

URM policy 

Parameters set by the Single Point administrator that control the execution of the URM 

agent on each managed SVR4 system, in terms of which information to collect and how 

often. 

user datagram protocol (UDP) 

The TCP/IP standard transport level protocol that enables an application program on one 

machine to send a datagram to an application program on another machine. UDP uses the 

internet protocol (IP) to send the datagram. The datagram includes a port number 

enabling the sender to distinguish between multiple destinations (application programs) on 

another machine. 

V 

View Gateway (ViewGate) 

A gateway supplied with the WebTx software that interoperates with Open/OLTP or other 

services and performs conversions between VIEW data definitions and HTML forms. This 

gateway provides access to Open/OLTP transactions or other application types in the OS 

2200 environment of your ClearPath IX server using the Web interface over your intranet or 

the Internet. ViewGate is available for both the UnixWare and Windows NT environments 

of ClearPath IX servers. 

virtual node 

See virtual server. 

virtual server 

Collection of services that gives the appearance of a physical Windows NT Server to 

clients. A virtual server is typically a group containing all of the resources to run a 

particular application, including a Network Name resource and an IP Address resource. 

VTOC 

W 

Abbreviation for volume table of contents. 

Web browser 

Client software for viewing documents on the World Wide Web and navigating hyperlinks 

to other documents. Used with a ClearPath IX server to access the Single View 

administration software on the Web. 

Web Transaction Server (WebTS) 

WebTS focuses on Web access to transactions and data in a high-volume and missioncritical 

electronic business environment. WebTS allows clients to both modify existing 

applications and build new business solutions that harness the potential of 

Internet/intranet technology. WebTS also allows the client to modernize Web-enabled 

applications with the "look and feel" of a new Internet application, making it more 

appealing and usable. 


Glossary 

WebTx gateways 

The WebTx software components that allow HTML-based Web browsers to interoperate 

with various types of applications on ClearPath HMP Series servers. The gateways 

included with WebTx software are 

• DCOM/OLE Gateway (DGate) 

• File Gateway (FileGate) 

• Java Gateway (JGate) 

• TUXEDO Gateway (TUXGate) 

• View Gateway (ViewGate) 

Windows Internet Name Service (WINS) 

A name resolution service that resolves computer names to IP addresses in a routed 

environment. A WINS server handles name registrations and queries. WINS is a NetBIOS 

Name Service for Windows NT. 

Windows NT File System (NTFS) 

A Windows NT operating system file system that supports extremely large storage media, 

long file names (up to 255 characters), file-level security, and transaction-based 

recoverability. 

Windows NT node 

An instance of Windows NT Server running in a ClearPath IX server. See also node and 

Intel node. 

Windows Open Services Architecture (WOSA) 

A Microsoft software architecture intended to integrate Windows workstations with backend 

services on a broad range of vendors’ systems. WOSA consists of a set of application 

program interfaces (API) that enable Windows client applications to access data 

independent of the type of network, the software providing the services, and the type of 

server system. Two examples of WOSA components are Open Database Connectivity 

(ODBC) and Messaging Application Program Interface (MAPI). 

WINS 

See Windows Internet Name Service. 

Winsock RSHD/NT 

A Windows NT service that provides Remote Copy server capabilities. Once installed, 

RSHD runs as a service that automatically starts whenever the SPO workstation is booted. 

World Wide Web (WWW) 

A world-wide network (a subset of the Internet) that is populated by hyperlinked 

documents. Web browsers such as Microsoft Internet Explorer and Netscape hide much of 

the complexity of the WWW and allow users to view multimedia documents and easily 

jump from one document to another and from one Web site to another. 

WOSA 

See Windows Open Services Architecture. 


WWW 

X 

X.400 

X.500 

X/Open 

See World Wide Web. 

Glossary 

A standard for electronic mail developed by the International Organization for 

Standardization (ISO). Products implementing the X.400 standard provide a mail backbone 

across which users can send e-mail, faxes, images, and EDI documents. See also message 

store, message transfer agent (MTA), and remote user agent (RUA). 

A standard for global directory services developed by the International Organization for 

Standardization (ISO). The X.500 standard defines protocols and interfaces that enable 

client applications to read and update directory databases on global directory servers. See 

also directory service agent (DSA) and directory user agent (DUA). 

An international nonprofit consortium dedicated to the advancement of open systems. Its 

primary activities include defining standards and branding products to ensure 

interoperability between the products of different vendors. 

X/Open Distributed Transaction Processing (DTP) model 

The distributed transaction processing model specified in standards developed by the 

X/Open Company, Ltd. The TransIT Open/OLTP architecture is based on these standards. 

The model defines four components of a DTP system. Application programs (AP) define 

the boundaries of transactions and perform the actions that make up the transaction 

(typically database updates). Resource managers (RM), such as database management 

systems, provide access to shared resources. Communication resource managers (CRM) 

allow application programs to communicate with each other. A transaction manager (TM) 

assigns unique identifiers (XID) to transactions, monitors the progress of transactions, and 

handles transaction completion or recovery. See also distributed transaction processing 

(DTP), global transaction. 

X terminal 

A terminal that provides X Window Access for Single Point Operations. For SPO/HMP 

Console, an LT501 X terminal provides this capability. 

X Window Access 

An SVR4-based GUI window environment that enables a user to perform various functions 

in multiple windows on a single display screen. 

3GL 

4GL 

See third-generation language. 

See fourth-generation language. 


Glossary 


Bibliography 

2200 Series Single Point Interface Software Installation and Configuration Guide (7831 

3400). Unisys Corporation. 

2200/XPA System Migration Guide (7830 9697). Unisys Corporation. 

American Megatrends MegaRAID and MegaRAID Ultra PCI SCSI Disk Array Controller 

User’s Guide. American Megatrends, Inc. 

Apex Outlook Concentrator User Guide. Apex PC Solutions, Inc. 

Aquanta DR/6 and DR/6U Series Hardware Installation and User’s Guide (3814 0125). 

Unisys Corporation. 

Aquanta ES2000 Series with Windows NT Getting Started and Reinstallation Guide 

(8999 5492). Unisys Corporation. 

Aquanta ES5000 Series with Windows NT Getting Started and Reinstallation Guide 


Aquanta ess Software Release Notes (8999 5427). Unisys Corporation. 

Aquanta QR/6 Series CPU Drawer Installation and User’s Guide (3814 0802). Unisys 

Corporation. 

Aquanta XR/6, XS/6, and SMP61000 System Configuration Utility (SCU) User’s Guide 


ClearPath 2200/3000 Series System Control Facility (SCF) Operations Guide (7844 


ClearPath 2200/3000 Series Systems Plateau Customer Reference Manual (7847 4145). 


ClearPath HMP IX Series Open Programming Environment (OPE) Configuration Guide 


ClearPath HMP IX Series Open/OLTP Pathway Installation and Operations Guide (7848 


ClearPath HMP IX Series Operations Guide (7848 4094). Unisys Corporation. 

ClearPath HMP IX Series SysAdmin Administration Guide (7848 4086). Unisys 

Corporation. 

7850 5104–009 Version 009B (Web Only) Bibliography–1

Bibliography 

ClearPath HMP IX Series Web Servers User’s Guide (7848 4458). Unisys Corporation. 

ClearPath HMP IX4000/IX5000/IX6000 Servers Peripheral Subsystems Configuration 

Guide (7847 5704). Unisys Corporation. 

ClearPath HMP IX4400 Server Configuration Guide (7848 4334). Unisys Corporation. 

ClearPath HMP IX4400 Server I/O Channel Assignment Planning Guide (7848 4888). 


ClearPath HMP IX4800/IX5000/IX6000 Servers I/O Channel Assignment Planning 

Guide (7848 4896). Previously titled Clear Path HMP IX4800/IX5600/IX5800 

Servers I/O Channel Assignment Planning Guide. Unisys Corporation. 

ClearPath SMP61000 Series System Configuration Utility User’s Guide (4619 7901). 


DEPCON Software Configuration and Operations Guide (7833 3960). Unisys 

Corporation. 

Diagnostic Software Peripheral Equipment Routines (DSPER) (Extended Mode) Tape 

Definition Reference Manual (7853 8469). Unisys Corporation. 

MAPPER System for 2200 Software Release Announcement (7832 1106). Unisys 

Corporation. 

MAPPER System for the UNIX Operating System Software Release Announcement (7846 


MAPPER System for Windows NT Software Release Announcement (7846 0268). Unisys 

Corporation. 

MegaRAID and MegaRAID Ultra PCI SCSI Disk Array Controller User’s Guide (MAN- 

MR). American Megatrends Incorporated. 

Microsoft Windows NT Server Version 4.0 Concepts and Planning (69940). Microsoft 

Corporation. 

Microsoft Windows NT Server, Version 4 (69935 0696). Microsoft Corporation. 

Microsoft Windows NT System Administration Guide. Microsoft Corporation. 

Open Systems Terminals LT500 X Terminal Software Installation Guide (4621 5372). 


Open Systems Terminals LT500 X Terminal Software User’s Guide (4621 5380). Unisys 

Corporation. 

OS 1100 SX 1100 Network File System (NFS) Administrator’s Guide (7833 2392). Unisys 

Corporation. 

Bibliography–2 Version 009B (Web Only) 7850 5104–009

Bibliography 

OS 2200 Communications Management System (CMS 1100) Configuration Reference 

Manual (7830 9853). Unisys Corporation. 

OS 2200 Communications Management System (CMS 1100) Installation and 

Configuration Guide (7830 9846). Unisys Corporation. 

OS 2200 Enterprise Backup and Restore Capabilities Overview (3495 3059). Unisys 

Corporation. 

OS 2200 Enterprise Backup and Restore Host Installation Guide (3495 3067). Unisys 

Corporation. 

OS 2200 Enterprise Backup and Restore UNIX Server Installation and Operations Guide 

for Windows (3498 1308). Unisys Corporation. 

OS 2200 Enterprise Backup and Restore Windows 3.1 Installation and Operations 

Guide (3495 3091). Unisys Corporation. 

OS 2200 Enterprise Backup and Restore Windows 95 Installation and Operations Guide 


OS 2200 Enterprise Backup and Restore Windows NT Server Installation and 

Operations Guide (7850 4321). Unisys Corporation. 

OS 2200 Enterprise Backup and Restore Windows NT Workstation Installation and 

Operations Guide (7850 4339). Unisys Corporation. 

OS 2200 Exec System Software Installation and Configuration Guide (7830 7915). 


OS 2200 Interactive Processing Facility (IPF 1100) Administration Guide (7833 3754). 


OS 2200 Software Library Administrator (SOLAR) End Use Reference Manual (7831 


OS 2200 TeamQuest Baseline Framework and TeamQuest Online User’s Guide (7830 

7717). Previously titled OS 2200 TeamQuest Baseline and TeamQuest Online 

Administration and End Use Reference Manual. TeamQuest Corporation. 

OSR5000 Open Systems RAID Subsystem Installation and Operations Guide (4487 


Personal Workstation 2 (PW 2 ) Unisys Repository Workstation (UREP-WS) Use Guide 


SCO UnixWare Application Server Personal Edition (CD-ROM 2 of 2) (400-92A-102). 

The Santa Cruz Operation, Inc. 

SCO UnixWare Installation Handbook (AU40000P000). The Santa Cruz Operation, Inc. 


Bibliography 

SCO UnixWare User Upgrade and Processor Upgrade Overview and Installation 

(AU40004P000). The Santa Cruz Operation, Inc. 

Single Point Status Operations Guide (7833 4778). Unisys Corporation. 

Site Configuration Management System (SCMS) Administration Guide Volume 1, 

Reference Information (7832 8861). Previously titled 2200 Series Site 

Configuration Management System (SCMS) Administration Guide Volume 1, 

Reference Information. Unisys Corporation. 

Site Configuration Management System (SCMS) Administration Guide Volume 2, 

Tutorial (7833 2434). Previously titled 2200 Series Site Configuration Management 

System (SCMS) Administration Guide Volume 2, Tutorial. Unisys Corporation. 

Unisys e-@ction Application Development Solutions Programmer’s Workbench for 

ClearPath OS 2200 User Guide (7848 3989). Previously titled OS 2200 Open 

Application Development Environment (OADE) for Windows User Guide. Unisys 

Corporation. 

Unisys e-@ction ClearPath Enterprise Servers ClearPath HMP IX and 2200 Systems 

Release 6.0 Software Planning and Migration Overview (7831 0349). Previously 

titled ClearPath HMP IX Series and 2200 Series Software Planning and Migration 

Overview. Unisys Corporation. 

Unisys e-@ction ClearPath Enterprise Servers Conceptual Overview (7848 4052). 

Previously titled ClearPath HMP IX Series Conceptual Overview. Unisys 

Corporation. 

Unisys e-@ction ClearPath Enterprise Servers Getting Started Guide (7848 4060). 

Previously titled ClearPath HMP IX Series and OS 2200 Getting Started Guide. 


Unisys e-@ction ClearPath Enterprise Servers IX4800/IX5000/IX6000 Series Systems 

Plateau Customer Reference Manual (7859 5774). Previously titled ClearPath HMP 

IX6800 Series Systems Plateau Customer Reference Manual. Unisys Corporation. 

Unisys e-@ction ClearPath Enterprise Servers IX5000 and IX6000 Servers 

Configuration Guide (7847 5746). Previously titled ClearPath HMP IX5000 and 

IX6000 Servers Configuration Guide. Unisys Corporation. 

Unisys e-@ction ClearPath Enterprise Servers Single Point Operations Basic Edition for 

ClearPath IX Administration and Operations Overview (7846 0540). Previously 

titled ClearPath HMP IX Series SPO/HMP Console Administration and Operations 

Overview. Unisys Corporation. 

Unisys e-@ction ClearPath Enterprise Servers Software Products Installation Guide 

(7831 0612). Previously titled OS 2200 Software Products Installation Guide. 


Unisys e-@ction ClearPath Web Enablement Solutions Transaction Integrator User’s 

Guide (7850 4230). Previously titled ClearPath HMP IX Series Web Transaction 

Enabler (WebTx) Administration Guide. Unisys Corporation. 


Bibliography 

Unisys e-@ction Enterprise Server ES2000 Getting Started and Reinstallation Guide 

(8999 5492). Previously titled Aquanta es2000 Series with Windows NT Getting 

Started and Reinstallation Guide. Unisys Corporation. 

Unisys e-@ction Enterprise Servers IX4800/IX5000/IX6000 Servers Installation and 

Servicing Reference (7842 5980). Unisys Corporation. 

Unisys e-@ction Single Point Operations Administration and Configuration Guide 

(7830 7527). Previously titled Single Point Operations Console/Enterprise Server 

Edition Administration and Configuration Guide. Unisys Corporation. 

Unisys e-@ction Single Point Operations Console User Guide (7831 2337). Previously 

titled Single Point Operations/Enterprise Server Edition User Guide. Unisys 

Corporation. 

Unisys e-@ction Single Point Operations Installation Guide (7833 4075). Previously 

titled Single Point Operations Console/Enterprise Server Edition Installation 

Guide. Unisys Corporation. 

Unisys e-@ction Web Transaction Server for ClearPath OS 2200 Administration Guide 

(7850 4073). Previously titled ClearPath HMP IX Series Web Transaction Server 

(WebTs) Administration Guide. Unisys Corporation. 

Unisys e-@ction Web Transaction Server for ClearPath OS 2200 Programming Guide 

(7850 4248). Previously titled ClearPath HMP IX Series Web Transaction Server 

(WebTs) Programming Guide. Unisys Corporation. 

Unisys RAID Storage Subsystem NT Attachment Guide (4488 2389). Unisys Corporation. 

Unisys Ultra160 RAID Adapter Driver Update Notice (4556 3947). Unisys Corporation. 

Unisys Volume Manager Installation Guide (4358 5322). Unisys Corporation. 

UnixWare 7 ReliantHA Configuration Guidelines and Unisys Scripts (7442 4607). 


UnixWare Migration Guide (7442 4185). Unisys Corporation. 


Bibliography 


Index 

Numbered Entries 

2200 node 

defined, 1-2 

3COM Fast Etherlink controller 

Windows NT Server 4.0, 6-8, 6-17, 6-19 

A 

Active Server Pages upgrade, 7-11 

administrator logon 

SPO workstation, 11-39 

Windows 2000 Advanced Server, 3-28 

Windows 2000 Professional 

Workstation, 11-39 

Windows NT Server 4.0, 6-23 

Windows NT Server, Enterprise 

Edition, 4-27, 5-26 

Windows NT Workstation 4.0, 11-39 

AMD PCNET Family Ethernet Adapter 


Edition, 4-21 

AMS, See Autoaction Message System 

application group 3 

installing, 15-4, 15-5 

Aquanta, See DR/2, DR/6, QR/6, ES2045R, or 

ES2085R 

Autoaction Message System (AMS), 10-24 

B 

backup domain controller (BDC), 2-3 

backups 

Enterprise Backup and Restore 

(EBRS), 16-5 

UnixWare 7 configuration, 8-20 

balanced server priorities, Windows NT, 7-15 

BDC, See backup domain controller 

7850 5104–009 Version 009B (Web Only) Index–1 

C 

CA ControlIT, See ControlIT 

cabling 

instructions (reference), 1-5 

CC3000 tape, 14-6, 14-15 

CC6000 tape, 14-6, 14-15 

CEC500 tape, 14-6, 14-15 

channel service I/O processor (CSIOP), 1-2, 

14-4, D-5 

checklists 

CSR installation, 2-1 

site planning, 2-1 

Cirrus Logic graphics adapter, 7-10 

ClearPath HMP IX 

new features, 1-1 

server components, 1-2 

CLEARPATH workgroup 



Edition, 4-24, 5-23 

client licenses, Windows NT, 7-6 

client service engineer (CSE), See customer 

service representative (CSR) 

CMS 1100 

configuring, 14-10, 14-11, 16-2 

using CMS-SETUP, 14-10, 14-12 

communications 

ClearPath HMP IX settings, B-1 

planning network addresses, 2-2 

Communications Management System, See 

CMS 1100 

configuring 

ControlIT, 7-13, 7-23 

ControlIT 

configuring, 7-13, 7-23 

installing, 7-12, 7-22, 12-7 

CSE (client service engineer), See customer 

service representative (CSR) 

CSIOP, See channel service I/O processor 

CSR, See customer service representative 

customer service representative (CSR) 

installation overview, 1-2 

customer service representative (CSR) 

checklist, 2-1 

D 

daemons 

SPO Basic Edition, 10-29


SPO/HMP workstation, 11-25 

Data Management System (DMS 2200) 

installing, 15-5 

DEC PCI Ethernet controller, 11-11 

DEPCON, 2-9, 2-11, 16-2 

Diagnostic Software Peripheral Equipment 

Routines (DSPER), 14-7 

disk configuration 

F drive, Windows NT, 7-16 


UnixWare 7, 8-18, 10-9 




Edition, 4-17 

disk configuration, (See also RAID 

configuration), 3-18, 4-17 

Display Processing System (DPS 2200), 13-9 


display resolution, configuring 

SPO workstation, 11-18, 11-28 

Windows NT Server, Enterprise Edition, 7-9 

XVision, 11-19, 11-30 

DNS, See Domain Name Service 

documentation levels, A-1 

Domain Name Service (DNS) 

client configuration 

UnixWare 7, 8-25 

DR/2 

MegaRAID configuration, 7-7 

Mylex configuration, 6-13 

Mylex DAC1164P RAID controller, 6-9, 6-13 

network adapter configuration, 8-24 

preinstalled operating system 


preloaded operating system 


Windows NT Server, 6-4 

RAID configuration, 7-7 


SysKonnect FDDI controller, 8-25 

Unisys Hardware Monitor, 7-5 

UnixWare 7 installation, 8-1 


DR/6 

multiport card driver installation, 10-17 

SPO Basic Edition installation, 10-1 

UnixWare 2.1 installation, 10-7 

drivers updates 

UnixWare 7, 8-23, 10-13 

DSPER, See Diagnostic Software Peripheral 

Equipment Routines 

Index–2 Version 009B (Web Only) 7850 5104–009 

E 

emergency recovery diskettes 

UnixWare 2.1, 8-31, 8-32 

emergency repair disks 


Windows NT, 7-19 


Enterprise Backup and Restore (EBRS) 


ES2024R 

AMD PCNET Family Ethernet Adapter, 4-21 

MegaRAID configuration, 7-8, 7-21 

Mylex AcceleRAID 352 RAID 

controller, 3-13, 4-11, 4-15 

Mylex DAC1164P RAID controller, 3-13, 

4-11, 4-15 



RAID configuration, 4-15, 7-8, 7-21 

Windows 2000 Advanced Server, 3-13, 

7-21 



Edition, 4-11 

SPO Basic Edition installation, 10-1 

SysKonnect FDDI controller, 3-11, 3-25 

video drivers, 7-9 

Windows 2000 Advanced Server, 3-1, 3-16 


Edition, 4-1, 4-13 

ES2045R 

Cirrus Logic graphics adapter, 7-10 

description, 1-1 

Intel EtherExpress PRO controller, 5-20, 

5-22 

MegaRAID configuration, 5-9, 5-15, 7-8, 7-21 










Edition, 5-9





Edition, 5-1, 5-14 

ES2085R 

FDDI interconnect, UnixWare 7, 8-24 

Mylex DAC1164P RAID controller, 8-7, 8-13 


RAID configuration 


Edition, 8-13 

SysKonnect FDDI controller, 8-25 


ES5044R 

Intel EtherExpress PRO controller, 4-23 

Intel Fast Ethernet Lan on 

Motherboard, 4-21 

MegaRAID configuration, 7-8 


controller, 3-13, 4-11, 4-15 


4-11, 4-15 



RAID configuration, 4-15, 7-8 




Edition, 4-11 


SysKonnect SK-NET FDDI PCI 

Adapter, 4-21 




Edition, 4-1, 4-13 

ES5085R 

Intel EtherExpress PRO controller, 3-8, 

3-23, 4-20, 4-23 

MegaRAID configuration, 7-8, 7-21 


controller, 3-13, 4-11, 4-15 


4-11, 4-15 




Windows 2000 Advanced Server, 3-13, 

7-21 



Edition, 4-11 

SysKonnect FDDI controller, 3-9, 3-24, 4-23 




Edition, 4-1, 4-13 

Ethernet controllers 





Edition, 4-20, 4-23, 5-20, 5-22 


F 

F drive, creating, Windows NT, 7-16 

FastTrack Server, See Netscape FastTrack 

Server 

FAT, See file allocation table (FAT) file system 

FDDI interconnects 

CMS 1100, 14-10 

communications settings, B-1 

configuring, D-1 

defined, 1-2 

hardware test, 1-7 

naming requirements, D-6 

network interface configuration, 1-11 

UnixWare 7, 8-24, 8-25 

verifying communications, 14-2 

Windows NT Server 4.0, 6-7, 6-19 


Edition, 4-23, 5-22 

FDDIVI and FDDIVJ 

name requirement, D-3 

fiber distributed data interface (FDDI), See 

FDDI interconnect 

file allocation table (FAT) file system, 11-9 

fonts, SPO Basic Edition, 11-21, 11-22, 11-31, 

11-33 

FTP service, Windows 2000 Advanced 

Server, 7-24 

FTP service, Windows NT, 7-15, 11-17 

G 

guest account, Windows 2000 Advanced 

Server, 7-24 

guest account, Windows NT, 7-16

H 

hardware 

planning installation, 2-1 

hardware platforms, A-1 

hardware ready for use (RFU), 14-16 

HMP-FLD tape, 13-1, 13-6 

HMP-OE1 tape, 13-1, 13-9 

HMP-OE2 tape, 15-1, 15-2 

HMP-UDS3 tape, 15-1, 15-5 

Host LAN Controller-2 (HLC2), 14-3, D-2 

hosts file 

default UnixWare hosts files, B-3 

SPO Basic Edition, 10-20 


Windows NT, 7-6 

I 

IIS, See Microsoft Internet Information Server 

initial boot, OS 2200, 13-3, 13-4 

installation 

CSR-performed procedures, 1-2, 14-8 

overview, 1-2 

tips and recommendations, 2-7 

installing 


AMS database, 10-24 

application group 3, 15-4, 15-5 

ControlIT, 7-12, 7-22, 12-7 

CSIOP, 14-4 

DMS 2200, 15-5 

DPS 2200, 13-9, 15-2 

Enterprise Backup and Restore 

(EBRS), 16-5 

HLC-2 microcode, 14-3 

IPF 1100, 13-9 

IX Network Identity Repository, 16-4 

MCB, 15-2 

OADE-WIN, 16-5 

Open Programming Environment 

(OPE), E-1 

optional OS 2200 products, 17-1 

optional UnixWare packages, 16-18 

OS 2200, 13-6 

RDMS 2200, 15-5 

Service Pack 3 for Windows NT, 7-4 

SFS 2200, 15-5 

SPO Basic Edition, 10-1, 10-19 

SPO workstation software, 11-1, 11-2 

SysAdmin, E-1 

TIP, 15-3 

TIPUTIL, 15-2 

UDS application group 3, 15-1 

UDSC, 15-5 

UnixWare 7, 8-1, 8-16 

UREP, 15-6 

UREP Workstation (UREP-WS), 16-5 

WebTS, 16-5 

WebTx, 16-5 

Windows 2000 Advanced Server, 3-1, 3-16, 

7-19 



Edition, 4-1, 4-13, 5-1, 5-14, 7-3 

Winsock RSHD/NT, 11-25, 11-36 

installing basic IOE, 13-1 

intalling 

Single Point Operations Product 

Information, 11-37 

Integrated Operating Environment (IOE) 

customer-installed products, 15-1 

Integration Expert 

guest account, Windows 2000 Advanced 

Server, 7-24 

guest account, Windows NT, 7-16 


OS 2200 print queues, 2-9 

using, 14-12 

Intel EtherExpress PRO controller 



Edition, 4-20, 4-23, 5-20, 5-22 

Intel Fast Ethernet Lan on Motherboard 


Edition, 4-21 

Intel node 

defined, 1-2 

Interactive Processing Facility (IPF 1100), 13-9 

interconnect (private LAN) 

defined, 1-2 

Internet FastStart 


IP addresses 

CMS 1100, 16-3 

DNS 


DNS servers 

Windows NT Server 4.0, 4-9, 5-7, 6-8, 6-20 


Edition, 4-24, 5-23 

FDDI interconnect, B-1 

Index–4 Version 009B (Web Only) 7850 5104–009

planning, 2-2 

private networks, planning, 2-12 

SPO workstation, 11-11, 11-21, 11-27, 11-32 

WINS, 11-12 

IX Network Identity Repository 

configuring in CMS 1100, 14-11, 16-3 


IX4400 servers 

CEC500 tape, 14-6 

FDDI configuration, D-2 

IX4800 servers 


System Controlled Performance, 13-7 

IX5000 Series servers 

CC3000 tape, 14-6 

CC6000 tape, 14-6 


System Controlled Performance, 13-7 

IXNAGX, See IX Network Identity Repository 

J 

jump keys, initial boot, 13-4 

K 

key tapes 

registering, 13-8 

KEYTAPE tape, 17-1 

L 

licenses 

EBRS, 2-9 

SPO/HMP Console, C-1 

UnixWare 2.1, 2-9 

UnixWare 7, 8-2, 8-17, 10-8 




Windows NT client licenses, 7-6 



Edition, 4-19 

Windows NT Workstation 4.0, 11-8, 11-10 

XVision, 11-20, 11-31 

logon 

administrator logon 






Edition, 4-27, 5-26 



UnixWare 7, 8-30, 10-28 


M 

master account number, OS 2200, 13-6 

MegaRAID configuration 


Windows NT Server 4.0, 6-9, 6-13, 7-7, 7-8 


Edition, 5-9, 5-15 

member server, 2-3 

Message Control Bank (MCB) 


messages, read-and-reply, 13-2 

Microsoft Internet Information Server (IIS) 




Edition, 4-25, 5-24 

migration 

considerations, 2-1 

monitor concentrator 

configuring, 2-14 

using, 2-15 

mouse 

configuring 

UnixWare 7, 8-21, 10-12 

Mylex AcceleRAID 352 RAID controller 


Edition, 4-15 

Mylex DAC1164P RAID controller 





Edition, 4-11, 4-15, 8-13 

Mylex DAC960 PJ RAID controller 

UnixWare 7, 8-7

N 

Netscape FastTrack Server 


network adapters 

configuring 





Edition, 4-20 

Network File System (NFS) 

Open Programming Environment 

(OPE), E-2 

network protocols 



Edition, 4-21, 5-20 

NFS, See Network File System 

nodes 

identifying, 2-2 

multiple, 1-9 

overview, 1-9 

NTFS, See Windows NT File System 

O 

ODB, See operations database 

OLTP-TM2200, 16-1 

Open Application Development Environment 

for Windows NT (OADE-WIN) 


Open Programming Environment (OPE) 


installing, E-1 

IP address and host name, B-2 

operating systems 

UnixWare 2.1, 10-7 


operations database (ODB) 

loading, 1-5 

OS 2200 

applicable software levels, 2-1 

CC3000 tape, 14-6 

CC6000 tape, 14-6 

CEC500 tape, 14-6 

HMP-OE1 tape, 13-9 

HMP-OE2 tape, 15-1, 15-2 

HMP-UDS3 tape, 15-1, 15-5 

initial boot, 13-3, 13-4 


installing basic IOE, 13-1 

jump keys, initial boot, 13-4 

KEYTAPE tape, 17-1 

master account number, 13-6 

print queues, 2-9 

product installation 

optional products, 17-1 

resilient partitions, 1-9, 16-19 

overview 

installation, 1-2 

owner’s account 

UnixWare 7, 8-19, 10-11 


P 

partitions 

OS 2200 resilient partitions, 1-9 





Edition, 4-17 

passwords 

changing default, 11-40 

SPO workstation, 11-10, 11-27, 11-40 

UnixWare 7, 8-19, 8-20, 8-30, 10-11, 10-28 





Edition, 4-19 


PathMate, See Integration Expert 

PDC, See primary domain controller 

PING 

using, 14-9, 14-15 

planning 

site preparation, 2-1 

preinstalled software 

choosing full installation, 2-8 

determining if software preinstalled 


procedures 


preloaded software 

choosing full installation, 2-8 

determining if software is preloaded 


determining if software preloaded


procedures 





primary domain controller (PDC), 2-3 

private LAN (interconnect) 

defined, 1-2 

Q 

QR/6 



R 

RAID configuration 

MegaRAID, 5-15, 6-13, 7-7, 7-8, 7-21 


controller, 4-15 

Mylex DAC1164P RAID controller, 4-15, 6-9, 

8-7 

Mylex DAC960, 8-7 





Edition, 4-11, 5-9, 8-13 

read-and-reply message format, 13-2 

ready for use (RFU), 14-16 

redundant array of independent disks 

(RAID), See RAID configuration 

Relational Data Management System (RDMS 

2200) 


release levels, A-1 

resilient OS 2200 nodes, 1-9 

root logon 

UnixWare 7, 8-20, 8-30, 10-11, 10-28 

S 

SCMS, See Site Configuration Management 

System 

SCO UnixWare 2.1 operating system, See 

UnixWare 2.1 

SCO UnixWare 7 operating system, See 

UnixWare 7 

SCO XVision, See XVision 

SCU, See system configuration utility 

security 


UnixWare 7, 8-19, 10-11 



Edition, 4-19 

server 

type (Windows NT), 2-3 

Service Pack, applying, 7-17, 7-26 

Shared File System (SFS 2200) 


Simple Network Management Protocol 

(SNMP), See SNMP agents; SNMP 

properties 

Single Point Configuration routine, 12-1, 12-8 

Single Point Interface Utility, 10-21, 10-26 

Single Point Operations (SPO), See SPO/HMP 

Console 

Single Point Operations Product Information 


Site Configuration Management System 

(SCMS) 

configuring the FDDI interconnect, D-1 

database requirement, 2-1 

site planning 

checklist, 2-1 

SNMP agents 

OS2200, 16-3 

SNMP properties 



Edition, 4-22 

software installation tips, 2-8 

software levels, A-1 

SPO Basic Edition 

AMS database, 10-24 

daemons, 10-29 

fonts, installing, 11-21, 11-22, 11-31, 11-33 

hosts file, 16-7, 16-9 


modifying configurations, 16-6 

multiport card driver installation, 10-17 

redirecting console output, 12-1, 12-12 

rename script, 16-11 

SPO workstation installation, 11-1, 11-2 

starting normal operations, 12-8 

UnixWare nodes 

monitoring, 12-1 

7850 5104–009 Version 009B (Web Only) Index–7

URM agents, 12-4, 12-12, 16-6, 16-15 

Windows NT agents, 12-6, 12-11 

Windows NT representations, 16-11 

SPO workstation 

configuring Windows 2000 Professional 


DEC PCI Ethernet controller, 11-11 

disk configuration, 11-8 

display resolution, 11-18, 11-28 

installing and configuring, 11-2 

installing and configuring Windows NT 

Workstation 4.0, 11-8 

logon, 11-39 

XVision, installing, 11-19, 11-30 

SPO/HMP Console 

automatic alias assignment, 2-10 

ControlIT, 7-12, 7-22 

registering, C-1 

stand-alone server, See member server 

status classification 

Unix2200Mon, C-1 

SUMMIT 

requirement to run, 1-6 

superuser logon 

UnixWare 7, 8-30, 10-28 

SYS FIN message, 13-6 

SysAdmin 

installing, E-1 

SysKonnect FDDI controller 


Windows 2000 Advanced Server, 3-9, 3-10, 

3-11, 3-22, 3-24, 3-25 



Edition, 4-20, 4-23, 5-20, 5-22 

SysKonnect SK-NET FDDI PCI Adapter 


Edition, 4-21 

System Controlled Performance (SCP) 

enabling, 13-7 

T 

tape drives, Aquanta, 7-14 

tapes 

boot 

OS 2200, 13-5 

CC3000 tape, 14-6 

CC6000 tape, 14-6 

CEC500 tape, 14-6 

fast-load tapes, 13-1 

HLC-2 microcode, 14-3 

HMP-FLD, 13-1 

HMP-OE1, 13-1 

KEYTAPE, 17-1 

TCP/IP, See also communications; IP 

addresses 

configuring in CMS 1100, 14-10 


SPO workstation, configuring, 11-11, 11-27 

testing communications, 16-18 

Technical Information Bulletin (TIB), 2-1 

TIP 

setting up the TIP environment, 15-3 

TransIT Open/OLTP, 16-1 

TSAM configuration, 16-3, B-1 

tuning scripts 



U 

UDK installation, UnixWare 7, 8-21 

UDS application group 3 


UniAccess ODBC, 16-2 


Unisys Repository Manager (UREP) 

installing 

server software, 15-6 

workstation (UREP-WS), 16-5 

Universal Data System Control (UDS Control) 


Unix2200Mon status classification, C-1 

UnixWare 2.1 

emergency recovery diskettes, 8-31, 8-32 

optional packages, installing, 16-18 

repartitioning, 16-19 

SPO Basic Edition, 10-7 

UnixWare 7 

configuration backup, 8-20 

determining if UnixWare is 

preinstalled, 10-4 

determining if UnixWare is preloaded, 8-4 

disk configuration, 8-18, 10-9 

disk partitions, 8-4 

DNS client configuration, 8-25 

drivers updates installation, 8-23, 10-13 

FDDI interconnect, 8-24, 8-25 


Internet FastStart, 8-29

license information, 8-2 

logon, 8-30, 10-28 

mouse configuration, 8-21, 10-12 

Netscape FastTrack Server, 8-29 


optional packages, installing, 16-18 

passwords, 8-19, 8-30, 10-11, 10-28 

preinstalled, procedures, 10-4 

preloaded, procedures, 8-5 


repartitioning, 16-19 

security configuration, 8-19, 10-11 

tuning script, 8-26 

UDK installation, 8-21 

UnixWare and Open Server Development Kit 

(UDK), 8-21 

URM agents, SPO, 16-6, 16-15 

V 

video, See display resolution, configuring 

W 

Web Transaction Enabler (WebTx), 16-5 

Web Transaction Server (WebTS) 


Windows 2000, See Windows 2000 Advanced 

Server; Windows 2000 Professional 

Workstation 

Windows 2000 Advanced Server 


ControlIT, 7-22 

FTP service, 7-24 

guest account, 7-24 




Windows 2000 Professional Workstation 

configuring for SPO, 11-26 


preloaded, procedures, 11-26 

Windows Internet Name Service (WINS) 




Edition, 4-24, 5-23 

Windows NT, See Windows NT Server 4.0; 


Edition; Windows NT Workstation 4.0 

Windows NT agents, SPO Basic Edition, 12-6, 

12-11 

Windows NT File System (NTFS), 3-18, 4-17, 

6-14, 7-17, 11-9 

Windows NT Server 4.0 

balanced server priorities, 7-15 

CLEARPATH workgroup, 6-21 

client licenses, 7-6 



DNS servers, 4-9, 5-7, 6-8, 6-20 

F drive, creating, 7-16 

FDDI interconnect, 6-7 

FTP service, 7-15, 11-17 


IIS, configuring, 6-18 


license information, 6-6, 6-16 

preloaded, procedures, 4-6, 6-4 

RAID configuration, 7-7, 7-8 

server type options, 6-6, 6-16 

SNMP properties, 6-19 

WINS, 6-8, 6-20 

Windows NT Server, Enterprise Edition 

balanced server priorities, 7-15 

CLEARPATH workgroup, 4-24, 5-23 

client licenses, 7-6 



DNS servers, 4-24, 5-23 

F drive, creating, 7-16 

FTP service, 7-15 


IIS Active Server Pages upgrade, 7-11 

IIS, configuring, 4-21 

installing, 4-1, 4-13, 5-1, 5-14 


server type options, 4-19 

SNMP properties, 4-22 



WINS, 4-24, 5-23 

Windows NT Workstation 4.0 

configuring for SPO, 11-9 

emergency repair disk, 11-10 

license information, 11-8, 11-10 

WINS, See also Windows Internet Name 

Service 

Winsock RSHD/NT, installing, 11-25, 11-36 

7850 5104–009 Version 009B (Web Only) Index–9

X 

XVision, installing, 11-19, 11-22, 11-30, 11-33 

Index–10 Version 009B (Web Only) 7850 5104–009

*78505104-009* 

78505104– 009

ClearPath IX Systems Installation and Configuration Guide

Create successful ePaper yourself

Delete template?

Save as template?