ClearPath Enterprise Servers Virtual Machine for ClearPath MCP ...

ClearPath Enterprise 

Servers 

Virtual Machine for ClearPath MCP 

Installation and Reinstallation Guide 

Virtual Machine for ClearPath 

MCP Version 5.2 

May 2005 

Printed in USA 

3845 8188–000




Installation and Reinstallation Guide 

© 2005 Unisys Corporation. 

All rights reserved. 


MCP Version 5.2 

May 2005 

Printed in USA 

3845 8188–000 

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 informaion 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 U.S. Government End Users: This is commercial computer software or hardware documentation developed at 

private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard 

commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data 

rights clauses. 

Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries. 

All other brands and products referenced in this document are acknowledged to be the trademarks or registered 

trademarks of their respective holders.




MCP 

Installation and 

Reinstallation Guide 

Virtual Machine for 

ClearPath MCP Version 5.2 

3845 8188–000 

ClearPath 

Enterprise Servers 

Virtual Machine for 

ClearPath MCP 

Installation and 

Reinstallation 

Guide 

Virtual Machine 

for ClearPath 

MCP Version 

5.2 

3845 8188–000 

Bend here, peel upwards and apply to spine.

Contents 

Section 1. Introduction 

About This Guide ......................................1–1 

Getting Started ........................................1–1 

ClearPath Enterprise Server Installation Policy .................1–2 

Prerequisites for Installation ..............................1–3 

Site-Specific Information .........................1–3 

Media and Books ..............................1–3 

Software Tools and Diagnostics ............................1–5 

System Overview ......................................1–5 

System Features ..............................1–5 

System Architecture ............................1–6 

Section 2. Setting Up the Server 

Mechanical Setup ......................................2–1 

Software Setup .......................................2–3 

Required Media ...............................2–3 

Installing the Windows Operating System ............2–4 

Configuring the Windows Operating System ..........2–4 

Installing Mass Storage Adapter Device Drivers ........2–5 

Prerequisites to Installing the Virtual Machine for 

ClearPath MCP Software. ......................2–5 

Installing Virtual Machine for ClearPath MCP Software . . . 2–7 

Installing Network Services Software. ...............2–8 

Enabling NetBIOS over TCP/IP. ....................2–8 

Creating the MCP Logical Disk Using the MCP Quick 

Install CD-ROM .............................2–9 

Configuring Windows Server 2003 for Accessing MCP 

Shares ...................................2–11 

Configuring the Optional Uninterruptible Power Supply 

(UPS) ....................................2–12 

Connecting the TCP/IP Network Drive ..............2–13 

Connecting to the External Public LAN ..............2–15 

Section 3. Complete Software Reinstallation 

Overview ............................................3–1 

Complete Reinstallation of the Software .............3–1 

3845 8188–000 iii

Contents 

Partial Reinstallation of the Software ................3–2 

Required Media ...............................3–2 

Windows Operating System ..............................3–2 

Reinstalling the Windows Operating System ..........3–3 

Configuring the Windows Operating System ..........3–3 

Virtual Machine for ClearPath MCP Software ..................3–3 

Network Services Software. ..............................3–5 

MCP Software ........................................3–5 

Using the Quick Install Program. ...................3–6 

Configuring and Halt/Loading the MCP. ..............3–6 

Section 4. Troubleshooting Information 

System Startup Problems ................................4–1 

Boot Drive Not Found, or Boot-Up Error Message 

Appears ...................................4–1 

Windows Setup Does Not Initialize .................4–2 

Virtual Machine for ClearPath MCP Setup Program Is 

Not Available ...............................4–2 

Network Services Software Setup Program Does Not 

Complete ..................................4–3 

Console for MCP Initialization Problems ..............4–3 

Logical Disk Files Have Improper Security ............4–4 

MCP Does Not Initialize .........................4–4 

TCP/IP Drive Connection Problems .........................4–4 

The Ping Fails and NP210 Is Not Present .............4–4 

The Ping Fails and NP210 Is Active and 

Communicating .............................4–5 

Section 5. Third-Party Applications 

Windows CD and DVD Writer Programs Not Supported on 

Systems Running Virtual Machine for ClearPath MCP Software. . . 5–1 

Tape Sharing Among Multiple Hosts Not Standard Supported 

Feature ...........................................5–1 

Windows Tape Management Program Supported on Virtual 

Machine for ClearPath MCP Systems .....................5–1 

Appendix A. Peripherals Information 

Using Physical Disk Drives Larger Than 100 GB ................A–1 

Data Migration Issues Using I/O Greater Than 64K ..............A–2 

Information About Multiple Paths Disk Configurations on EMC 

Storage Systems ....................................A–2 

Configuring CLARiiON Storage Systems for Control Groups .......A–3 

Using PowerPath Administrator with VSS Disks ................A–3 

iv 3845 8188–000

Contents 

VSS Disks Are Displayed in Disk Manager ....................A–3 

Using VSS Disks With Dell PERC RAID Controller Causes Error 

Messages .........................................A–4 

AfDisk Driver Error Messages in the System Event Log ..........A–4 

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

3845 8188–000 v

Contents 

vi 3845 8188–000

Section 1 

Introduction 

About This Guide 

Purpose 

Audience 

Conventions 

Prerequisites 

This document is the primary source of information for the setup and configuration of the 

ClearPath enterprise server. 

This document is directed to Unisys service representatives and to customers. 

This document is applicable to the Libra Model 300 and FS1300 platforms. The Libra 

Model 300 server is a general-purpose server. The FS1300 server has been custom 

designed for the financial services line of business and run-time optimization of solutions 

developed with Unisys Enterprise Application Environment. These servers share the same 

underlying physical architecture; however, they are separate and distinct servers. Each has 

unique software features that enable different hardware capabilities and configurability. 

Throughout this document, the term ClearPath enterprise server or server refers to these 

platforms. 

To use this guide, you should be familiar with 

• The Windows graphical user interface (GUI) used by the Console for MCP 

• The MCP ODT window 

• The MARC screen environment and CANDE 

• CMP hardware concepts 

Getting Started 

This section is the starting point for the installation process, including 

3845 8188–000 1–1

Introduction 

• ClearPath enterprise server installation policy 

• Prerequisites for installation 

• Software tools and diagnostics 

• Overview of the system 

ClearPath Enterprise Server Installation Policy 

Caution 

The customer cannot install the server. The server must be installed and 

configured by a Unisys service representative or by a licensed third-party 

installer. 

Note: Configuring the external network connection, including the setup of the Shared 

Adapters feature as a gateway from the MCP to the public LAN, is the responsibility of the 

customer. 

Separately sold services are available to assist customers through Unisys Global 

Infrastructure Services (GIS). Customers are strongly advised to use these services. 

The server installation process includes the following tasks: 

• Prearrival site preparation (customer) 

This is a customer responsibility. The customer uses the site planning materials to 

provide adequate space for the server cabinet and the console, and to provide 

adequate air conditioning, and a reliable electrical power source. Unisys 

representatives can assist the customer regarding power sources or environmental 

considerations. 

• System setup and configuration (Unisys service representative and customer) 

The customer must agree to the terms of the Microsoft software licensing 

agreement. The Unisys service representative cannot assume this responsibility. 

Mechanical and software setup is the responsibility of the Unisys service 

representative, or a licensed third-party installer. A successful installation includes the 

unpacking, setup, configuration, and testing of the system. Unauthorized persons 

attempting to install the system can cause serious software problem requiring 

extensive remedial work. 

• Arrival quality reporting (Unisys service representative) 

It is important that the Unisys service representative describe all installation problems 

to the factory using the appropriate forms. The feedback received from system 

installers is used to improve the arrival quality of the system. Every effort will be made 

to use this information to make improvements. 

• Reinstalling the system software (customer or purchased services) 

1–2 3845 8188–000

Note: Reinstalling system software is not part of a normal installation, but it is 

covered in this document. 

Occasions arise when it is necessary to reinstall certain system software 

components. In some cases the need results from a failure to follow installation 

instructions. The need might also be the result of a hardware failure or a site power 

problem. Because the software environment of the system is complicated, detailed 

instructions for reinstalling software by the Unisys service representative are included 

in this document. 

To determine whether you must reinstall the system software components, refer to 

Sections 3 and 4. You might also need to refer to other documents to install 

networking software or Windows applications. 

Installation Guidelines 

Observe the following legal and contractual guidelines when installing the server: 

• The customer cannot install the server. The server must be installed and configured by 

a Unisys service representative or by a licensed third-party installer. 

• The connection of the system to a public LAN should be performed by GIS personnel 

with the assistance of the site LAN administrator. 

• Unisys has a contractual agreement with Microsoft Corporation. Unisys and its 

representatives must require the customer to be present and to agree to the licensing 

terms for Windows. The Unisys service representative must not assume this 

responsibility. 

Prerequisites for Installation 

You need some items to install and configure the system. Some system components are 

already installed or set up by the factory. In this case, the materials you need are minimal. 

Site-Specific Information 

If the server is to be attached to an existing network, work with the site administrator to 

resolve configuration questions. You need to know 

• IP addresses for the server on the customer LAN 

• Host names of existing Unisys servers that are visible using BNA 

Media and Books 

Introduction 

The server is composed of several environments with unique features. The delivery 

methods for software and documents differ, even within the environments. The following 

list helps you to understand the materials that are delivered with the system. 

3845 8188–000 1–3

Introduction 

Platform Documents and Media 

• Systems Management and Consoles CD-ROM 

• Service and Diagnostic Utilities CD-ROM 

• Installation and Server Management CD-ROM 

• Documentation CD-ROM 

Note: The CD-ROM contains the server platform documentation for your system. 

• Operating System Reinstallation CD CD-ROM 

• Resource Disc Windows System Resource Manager CD-ROM 

• Product Information Guide 

• Operating System Setup and Installation Guide 

• Quick Installation Guide 

• Rack Installation Guide 

• Operating system Getting Started 

ClearPath Enterprise Server Documents and Media 

• Libra Model 300 or FS1300 Quick Start Installation 

• Enterprise Servers Security Notice 

• Libra Model 300 or FS1300 Product Documentation CD-ROM 

Note: The CD-ROM contains the Virtual Machine documentation for your system: 

- Virtual Machine for ClearPath MCP Installation and Reinstallation Guide 

- Implementation and Operations Guide 

- Virtual Machine for ClearPath MCP Administrative Console Guide 

- Software Information Manual for VM MCP Servers 

Virtual Machine for ClearPath MCP and MCP Quick Install Media 

• Virtual Machine for ClearPath MCP Software CD-ROM 

• MCP Quick Install CD-ROM 

• Virtual Machine for ClearPath MCP Encryption Add-on CD-ROM (Optional) 

MCP Release Software 

• MCP Release Software CD-ROM 

Interim Corrections (ICs) are available at 

https://www.support.unisys.com/unisys/aseries/support/fixes.htm 

• Keys media 

• Supplemental Software Release 

1–4 3845 8188–000

• Core ClearPath MCP document set 

• ClearPath Enterprise Servers Product Documentation CD-ROM 

Note: The CD-ROM contains the ClearPath MCP software documentation, including 

the Network Services Implementation Guide. 

Software Tools and Diagnostics 

• Utility Partition System Utilities 

Use the Utility Partition System Utilities to run diagnostic tests to the server 

processors, memory, PCI adapters, and other internal peripheral devices of the server. 

During the start-up sequence, press the F10 key to enter Utility Partition System 

Utilities and follow the steps provided on the screen. 

• Host Bus Adapter Setup Utilities 

When you add a host bus adapter, a setup of the adapter might be required. During 

each start-up sequence, you have the opportunity to enter the Setup programs by 

using the appropriate key combination. Setup utilities are available for the small 

computer system interface (SCSI), Fibre Channel, and LVD host bus adapters. Refer to 

the adapter installation guides for further information. 

• System Editor 

Use the System Editor to view, create, and edit peripheral configuration diagram (PCD) 

files. A PCD file describes the data path to all I/O devices. Whenever a new I/O control 

or unit is added to the system configuration, declare it in the PCD file. Add the devices 

and generate a new PCD. Refer to the Virtual Machine for ClearPath MCP 

Administrative Console Guide. 

• Windows Event Log Viewer 

Use the event log viewer to diagnose system events when a service fails to initialize or 

an environmental problem arises. 

System Overview 

The server is a high-performance enterprise server using virtual system architecture that 

allows the Windows and MCP environments to communicate without an external LAN. 

The server offers new levels of performance and scalability with up to four Intel Xeon 

microprocessors and 16 gigabytes (GB) of system memory as well as hot-pluggable hard 

drives, expansion slots, power supplies, and system fans. 

System Features 

Introduction 

The server offers a completely integrated tower or rack-mounted server. The server 

includes 

• Up to four Intel Xeon MP microprocessors 

• Support for symmetric multiprocessing (SMP) 

• A minimum of 4 GB of system memory, upgradable to a maximum of 32 GB 

3845 8188–000 1–5

Introduction 

• Support for up to twelve 1-inch, internal, hot-pluggable Ultra3 SCSI hard drives 

• A single, 1.44-MB, 3.5-inch diskette drive 

• An optional CD-ROM or DVD/CD-RW drive 

• Two hot-pluggable, 1570-watt power supplies 

• Six redundant, hot-pluggable system cooling fans 

• An intrusion switch that signals the appropriate systems management software if the 

top cover is opened 

• Seven PCI card slots: 

- Four PCI-e slots 

- Three PCI-x slots 

• An integrated VGA-compatible video subsystem with 16 MB of SDRAM video 

memory 

• An integrated, dual-channel Ultra3 SCSI controller for internal SCSI disk drives 

• An optional dual-channel RAID controller card for connection to both internal and 

external storage 

• An optional remote access card that provides remote management functions 

• Two integrated 10/100/1000-Mbps (megabits per second) network interface cards 

(NICs), which provide an Ethernet interface 

• Embedded systems management circuitry that monitors the operation of the system 

fans as well as critical system voltages and temperatures 

• Back-panel connectors include video, two universal serial bus (USB) ports, and two 

NIC connectors 

• Front-panel connectors include two additional USB ports and one video port 

System Architecture 

A virtual machine is one on which an MCP environment functions entirely within the 

system memory under the control of the Windows operating system. The MCP operates 

within its own area in memory, and no hardware coprocessor devices compete for system 

resources. A major advantage of virtual architecture is that it is nearly platform 

independent. 

The server consists of three tightly linked software environments: 

• Windows 

• Virtual Machine for ClearPath MCP 

• MCP 

1–6 3845 8188–000

Windows 

The Virtual Machine for ClearPath MCP and the MCP environments require a functional 

Windows environment. Windows manages the disk subsystem, printing, and network 

interface to the user LAN. 


MCP 

Introduction 

The Virtual Machine for ClearPath MCP is a series of applications running within Windows 

operating system. These applications provide support for the virtual processor, memory, 

and input/output module (IOM) components. The user interface main menu includes 

system operator and control functions that regulate the MCP environment. For example, 

the Console for MCP configures, loads, and initializes the MCP. The main menu window 

includes the System Editor that builds the PCD. The System Editor has an auto-build 

feature that builds a PCD based on the installed system resources. 

The MCP environment supports the MCP software as well as server and applications 

software. The Virtual Machine for ClearPath MCP uses the delta MCP and resource 

management module (RMM) I/O, which are completely compatible with the architecture 

of large systems. 

3845 8188–000 1–7

Introduction 

1–8 3845 8188–000

Section 2 

Setting Up the Server 

This section tells the Unisys service representative how to set up and configure the server 

when it arrives at the customer site. There are two main phases of system 

installation—mechanical setup and software setup. 

Mechanical Setup 

Refer to additional documentation contained on the server platform Product 

Documentation CD-ROM for installing mechanical and hardware components of the 

server. 

WARNING 

This system cannot be installed by the customer. The server must 

be installed by a qualified Unisys service representative or a 

licensed third-party installer. Serious injury can result from 

improper installation techniques. 

What To Do About Damaged, Missing, or Incorrect Parts 

In the event of installation problems because of damaged, missing, or incorrect parts, you 

should contact the Customer Response organization or the appropriate representative for 

your location. 

If you have been instructed to use the Customer Response Hotline, the number is 1-888- 

866-7265. Information about Customer Response, policy statements, and the required 

forms are available at the Unisys Product Support Web site: 

www.support.unisys.com 

Support organizations in various locations use different methods to resolve installation 

problems. Some organizations have a factory representative available for correction of 

problems. Before installing the system, you should be aware of the policy for your 

location. 

When resolving installation problems, you need the following information: 

3845 8188–000 2–1


Site and Order Data 

Original order number 

Marketing branch organization number 

Customer name 

Shipping address 

Unisys Service Representative Data 

Requester name 

Life number 

Problem Data 

Requester phone number 

Unisys service representative assignment number 

Branch organization number 

Style number and part number 

Quantity System style 

System serial number 

Damaged Parts 

If any part or parts are damaged, do not attempt to operate the system. Contact the 

appropriate organization. Operating the system with damaged parts can cause additional 

equipment damage or erratic system performance. Do not substitute parts that are not 

provided by Unisys. 

Missing or Extra Parts 

If your order was not correctly assembled, or if required parts were not sent, contact the 

support organization before attempting to install the system. They can tell you whether to 

attempt the installation. If extra parts were shipped to the site, follow the procedure used 

in your location. 

2–2 3845 8188–000

Wrong Parts 

If the wrong parts were sent to you, do not attempt to install them in the system. Installing 

nonqualified parts can cause system performance problems and could cause damage to 

the system. If you have any question about the use of a specific part on your system, call 

the Support organization. 

Software Setup 

This topic provides instructions for a normal software setup by the Unisys service 

representative only. The system cannot be installed by the customer. 

If you have problems during software setup, refer to the Troubleshooting Information 

section in this guide. 

Software setup includes the following tasks: 

• Installing the Windows operating system 

• Configuring the Windows operating system 

• Installing mass storage adapter device drivers 

• Prerequisites to installing the Virtual Machine for ClearPath MCP software 

• Installing Virtual Machine for ClearPath MCP software 

• Installing Network Services software 

• Enabling NetBIOS over TCP/IP 

• Creating the MCP logical disk using the MCP Quick Install CD-ROM 

• Configuring Windows Server 2003 for accessing MCP shares 

• Configuring the optional uninterruptible power supply (UPS) 

• Connecting the TCP/IP network drive 

• Connecting to the external public LAN 

Required Media 

Make certain that you have the following items and media before you begin: 



• Network Services Installation CD-ROM 






3845 8188–000 2–3


• Server platform Documentation CD-ROM 

• MCP Product Documentation CD-ROM 


• Operating system Setup and Installation Guide 

Installing the Windows Operating System 

Perform the following steps to determine if an operating system has been installed on 

your server: 

1. Ensure that the keyboard, mouse, and monitor are connected to your system, and 

then power on your server. 

2. Read and accept the software license agreement to continue. 

Your system restarts. If a message appears indicating that bootable drives do not exist 

or that an operating system was not found, then an operating system has not been 

installed on your system. Continue with step 3. 

If an operating system has been preinstalled on your system, it is not necessary to 

continue with this process. Locate the operating system Setup and Installation Guide 

that is provided with your system, and follow those instructions to complete the 

installation process. 

3. Insert the Installation and Server Management CD-ROM in the CD-ROM drive and 

restart your system. 

The Server Assistant screen appears. 

4. Click Server Setup. 

5. Follow the step-by-step instructions to configure your hardware and to install your 

operating system. 

Configuring the Windows Operating System 

Set the performance and file dump options on the Windows operating system by 

performing the following steps: 

1. On the desktop, click Start, select Settings, select Control Panel, and then click 

System. 

The System Properties dialog box appears. 

2. Select the Advanced tab in the System Properties dialog box. 

3. In the Performance box, select Settings. 

The Performance Options dialog box appears. 

4. Select the Advanced tab on the Performance Options dialog box. 

5. In the Virtual memory box, click Change. 

The Virtual Memory dialog box appears. 

6. Select the C: drive. 

2–4 3845 8188–000

7. Select Custom size. 

8. Add 32 MB to the amount of total physical memory (RAM) available on your system, 

and enter that combined value, in megabtyes, in both the Initial size and Maximum 

size fields. If the combined value exceeds 4095 MB, enter 4095 MB in the size 

fields. 

Note: You can view the total physical memory available on your system on the 

System Information screen. On your desktop, click Start, select Programs, 

Accessories, System Tools, and click System Information. 

9. Click OK to close the Virtual Memory dialog box. 

10. Click OK to close the Performance Options dialog box. 

11. Click OK on the System Properties dialog box. 

12. Click Yes to Do you want to restart your computer now? 

Installing Mass Storage Adapter Device Drivers 

If your system uses a mass storage adapter (such as a RAID or a Fibre Channel adapter), 

install the manufacturer-supplied driver using the Installation and Server Management 

CD-ROM. You can also obtain the latest version of the driver from the Unisys Product 

Support Web site. 

Prerequisites to Installing the Virtual Machine for ClearPath MCP 

Software 

Before installing the Virtual Machine for ClearPath MCP software, you must perform the 

following system settings to ensure that the software installs and functions correctly. 

Disabling Hyperthreading in the System BIOS 


For optimal server performance, hyperthreading must be disabled in the system BIOS. 

Hyperthreading enables one physical microprocessor to appear as two logical processors 

to the operating system and application programs. 

To disable hyperthreading, perform the followings steps: 

1. During the start-up sequence, press the F2 key to enter System Setup (or BIOS 

Setup). 

2. Select CPU Information on the System Setup main screen. 

The CPU Information screen shows the different processors in the system (speed, 

cache size, and so forth). 

3. Disable hyperthreading by changing the setting of the logical processor. 

Note: The default setting is enabled. 

3845 8188–000 2–5


Enabling the USB Controller in the System BIOS 

In order for the server to use the new 1-wire USB Image Enabler device, also referred to as 

a USB security device, of the Virtual Machine for ClearPath MCP software, the USB 

controller must be enabled in the system BIOS. Refer to the applicable document 

contained on the server platform Product Documentation CD-ROM for information on 

changing the system BIOS settings. 

Installing Unsigned Drivers 

Facilitate the installation of unsigned drivers by performing the following steps: 

1. On the Start menu, point to Programs and then Administrative Tools, and click 

Local Security Policy. 

The Local Security Settings window appears. 

2. Double-click Local Policies in the Tree tab, and then select Security Options. 

3. Right-click Devices: Unsigned driver installation behavior and click 

Properties. 

The Drivers: Unsigned Driver Installation Behavior dialog box appears. 

4. On the Local Security Setting tab, select Silently Succeed, and then click OK. 

5. In the right pane of the Local Security Settings window, under the Local Setting 

column, verify that the unsigned driver is set to Silently Succeed. If it is not, repeat 

steps 1 through 4. 

6. Close the Local Security Settings window. 

Attaching the USB Image Enabler device 

The server does not have a parallel port to support the conventional Virtual Machine for 

ClearPath MCP parallel port security device. The Image Enabler device for the server is a 

1-wire USB device. 

Note: Multiple Image Enabler devices are not supported on the same system. 

Caution 

Do not attach the USB Image Enabler device until the Virtual Machine for 

ClearPath MCP software installation is complete. If the device is plugged in 

before the software installation is complete, the wrong device driver will be 

installed. 

2–6 3845 8188–000

Installing Virtual Machine for ClearPath MCP Software 

Installation Procedure 

Caution 


Install the Virtual Machine for ClearPath MCP software before running any 

application or installing any other software. 

To install the Virtual Machine for ClearPath MCP software, perform the following 

procedure: 

1. Log on, using an account with Administrator privileges, and the appropriate password. 

2. Insert the Virtual Machine for ClearPath MCP Software CD-ROM in the CD-ROM 

drive. 

The autorun program executes. A screen appears with the following choices: 

Install Virtual Machine for ClearPath MCP 

Install Hot Fix 

View Read Me 

Exit 

3. Select Install Virtual Machine for ClearPath MCP. 

4. Click Next on the InstallShield wizard welcome screen. 

5. Accept the license agreement, and then click Next. 

6. Fill out the customer information, and then click Next. 

7. Click Next to accept the default location for the destination folder. 

8. Click Next to accept the default location for the application data folder. 

9. Click Next to accept the default setup type. 

10. Click Install. 

The files are copied from the CD-ROM to the hard disk. 

11. Click Finish. 

12. Click No when asked to restart the system. 

13. On the autorun screen, select Install Hot Fix. 

The Hot Fix Installer command screen appears, which automatically launches the 

Hot Fix readme file. 

14. In the Hot Fix command screen, type Yes. 

15. Type No when asked to restart the system. 

16. Press any key to exit the Hot Fix Installer command screen. 

3845 8188–000 2–7


17. Click Exit on the autorun screen. 

18. Remove the CD-ROM from the CD-ROM drive. 

19. Initiate the installation of any add-on software ordered with your system. For 

example, the Virtual Machine for ClearPath MCP Software High Encryption Add On. 

20. Attach the USB Image Enabler device to the USB port of the server. 

21. When the Found New Hardware Wizard appears asking if you want to install the 

device automatically, click Next. 

The Found New Hardware Wizard dialog box appears stating that the software 

installation for the device known as “USB Host for 1-Wire Microlan” is finished. 


23. Restart the computer. 

24. Click OK when the VM ClearPath MCP-Console Config message about Windows 

server optimization option appears. 

Note: You might not need to remove and reattach the USB Image Enabler device 

each time you upgrade the Virtual Machine for ClearPath MCP software. 

Installing Network Services Software 

Network Services are software services that enhance the use of the Windows 

environment in a Virtual Machine for ClearPath MCP system. For complete information, 

refer to the Network Services Implementation Guide. 

To install the Network Services software, follow the directions for installing Network 

Services software on Virtual Machine for ClearPath MCP servers outlined in the Network 

Services Implementation Guide. After you complete the installation, perform the steps 

under the “Enabling NetBIOS over TCP/IP” topic. 

Enabling NetBIOS over TCP/IP 

To enable Network Services to use the shared adapters, perform the following procedure: 

1. On the Start menu, point to Settings, and then click Control Panel. 

2. Double-click the Network Connections icon. 

The Network Connections window appears. 

3. Right-click the Local Area Connection icon that is used for the shared adapter, and 

then click Properties. 

The Local Area Connection Properties dialog box appears. 

4. Select Internet Protocol (TCP/IP) under the General tab, and then click 

Properties. 

The Internet Protocol (TCP/IP) Properties dialog box appears. 

5. Click Advanced. 

The Advanced TCP/IP Settings dialog box appears. 

2–8 3845 8188–000

6. Click Enable NetBIOS over TCP/IP on the WINS tab. 

7. Click OK to close the Advanced TCP/IP Settings and Internet Protocol 

(TCP/IP) Properties dialog boxes. 

8. Click Close on the Local Area Connection Properties dialog box. 

Creating the MCP Logical Disk Using the MCP Quick Install 

CD-ROM 

The MCP software is not loaded on the disk by the factory. You must create a logical disk 

drive and load the MCP files at this time. Use the MCP Quick Install CD-ROM to perform 

these tasks. Additional MCP software, keys, and Interim Corrections (ICs) are loaded later 

in the installation process. 

Prerequisites for Using the Quick Install Program 

A valid NTFS partition must be available for the logical disk. If necessary, you can use the 

Disk Management to create an NTFS partition. If required, adjust the drive letters before 

you use the Quick Install program. 

The Quick Install program locates all usable NTFS partitions and lets you click from them. 

The program informs you if it does not find a suitable drive for the installation of the MCP. 

Using the Quick Install Program 


After you have verified that your system environment is ready for the Quick Install 

program, follow these steps: 

1. Insert the MCP Quick Install CD-ROM in the CD-ROM drive. 

2. Accept the license agreement. 

Quick Install searches your system for suitable drives for your MCP files. 

3. When prompted, select the drive on which to install the MCP software. 

Quick Install takes about 15 minutes to complete the loading of the MCP files. The 

Quick Install program eliminates the need for you to perform the configuration tasks 

required during a normal cold-start. 

The MCP Quick Install Successful dialog box appears informing you that you 

successfully installed the MCP, and requesting that you add DISK000.asd to the 

PCD. 

4. Click OK. 

The Quick Install program is now complete. 


6. If you installed the Virtual Machine for ClearPath MCP software before running the 

MCP Quick Install and have not restarted the system yet, restart the system and log 

on using an account with Administrator privileges. 

3845 8188–000 2–9


Configuring and Halt/Loading the MCP 

1. Double-click the Console for MCP icon. 

2. Click System Editor in the Console Configuration Error dialog box. 

3. Click MCP Disk Management on the Tools menu. 

4. Select Logical Disk Operations, and then click Next. 

From the Logical Disk Management window, select Security. 

5. If any logical disk files are found that lack proper security, select them from the list and 

click Apply for proper security. 

6. Close the Logical Disk Management window. 

7. Create and save a new PCD using the Auto Build feature. 

This action ensures that the MCP finds the halt/load disk drive and ODT required for a 

successful halt/load. Refer to the Administrative Console Guide. 

8. Verify that the ICP4 210 is present. If multiple NP instances were selected, verify that 

NP211, NP212, and NP213 are also present, if applicable. and then end the System 

Editor session. 

For assistance, refer to the Virtual Machine for ClearPath MCP Administrative Console 

Guide and the Virtual Machine for ClearPath MCP Administrative Console Help. 

9. On the Configure menu of the main Console for MCP window, perform the following 

steps: 

a. Select Partition Properties, or click Properties from the toolbar. 

b. Click Select next to the PCD file. 

c. Select the PCD file you have just created, and then click OK. 

d. In the box next to the Halt/Load ODT, select Unit 1. 

e. In the box next to the Halt/Load disk, select Unit 500. 

10. In the MCP Memory size field, insert a value within the valid range displayed for your 

server. The full memory size range is 16 to 180 megawords (MW). 

Note: If Windows 2003 Service Pack 1 is installed, the maximum MCP memory is 

limited to 116 megawords (MW). On these systems, enter a value less than or equal 

to 116 MW for the MCP Memory size, to avoid error messages that might result 

when performing a Load operation or running the System/Loader program. You can 

also refer to the Unisys Product Support Web site for more information about the 

MemFixer utility solution. 

The Virtual Machine for ClearPath MCP Console calculates the valid memory size for 

your server based on the amount of server memory, and the amount of memory used 

by the Virtual Machine for ClearPath MCP disk cache. For more information about 

memory, refer to Memory Configuration Guidelines for the Virtual Machine for 

ClearPath MCP, available at 

http://www.support.unisys.com/aseries/docs/Hardware/LX-VM5.2-SR0/41264342- 

000.pdf 

11. Select a value within the allowed range, and then click OK. 

2–10 3845 8188–000

12. If the MCP memory size is increased in the previous step, the Shut Down MCP 

Control command automatically starts. Perform the following steps: 

a. Wait until a status message confirms that the MCP Control is shut down. 

b. Select MCP on the main menu for the Console for MCP window, and then click 

Init MCP Control. 

13. Select MCP and then Run SystemLoader on the main menu of the Console for 

MCP window. 

Refer to the Virtual Machine for ClearPath MCP Administrative Console Guide and the 

Virtual Machine for ClearPath MCP Administrative Console Help. 

14. Start the ODT window by double-clicking the ODT Unit 1 icon on the desktop. You 

can maximize the ODT screen by holding down the Alt key and pressing Enter. 

15. Type RECONFIGURE GROUP AS DEFAULT and transmit (press the + key on the 

numeric key pad). 

Wait until the System/Loader reconfigures. 

16. Type STOP and transmit. 

This action terminates the loader and displays the EOJ message. 

The MCP initializes and displays the MCP ADM screen. 

17. Type TERM DCSTATION TRUE, and transmit. 

Disk initialization stops awaiting user input. 

18. Type HN = CPMCP1 and transmit. 

19. Use the ODT command HL UNIT to determine the halt/load pack (PK) number, which 

is typically PK500. Type 4 IL PK, and transmit (press the + key on the 


This action allows the system to fully initialize. 

Wait for the “System Initialization Completed” message. 

20. Type ??PHL and transmit. 

21. Follow the IC cover letter instructions to load any applicable ICs. 

22. Load separately purchased software according to instructions in the ClearPath MCP 

software documents. 

Configuring Windows Server 2003 for Accessing MCP Shares 

The Network Services software enables you to connect to the MCP shares from the 

Windows environment. However, the default local security policy for Windows 

Server 2003, Enterprise Edition, might cause attempts to map a share on the MCP system 

to fail and reject the MCP password. This can occur if the Windows local security policy is 

set to “Send NTLM response only” and the MCP password is not entered in uppercase 

letters. 

Perform the following procedure to resolve this problem: 


3845 8188–000 2–11



2. In the Control Panel, double-click the Administrative Tools icon. 

3. In the Administrative Tools window, double-click the Local Security Policy icon. 

4. In the left pane of the Local Security Settings window, expand the Local Policies 

tree and select Security Options. 

5. In the right pane, right-click Network Security: LAN Manager Authentication 

Level and click Properties. 

The Local Security Setting dialog box appears. 

6. From the LAN Manager Authentication Level list, select Send LM and NTLM 

responses. Click OK. 

7. Close all the windows and then connect to the MCP shares. 

Configuring the Optional Uninterruptible Power Supply (UPS) 

If your system has an optional UPS feature, you can configure it to shut down the system 

in an orderly manner in the event of a site power problem. If your system does not have a 

UPS, then skip these instructions. 

To set up and configure the UPS connection, perform the following steps: 

1. Verify that the RS232 cable is attached from the port on the UPS to one of the two 

serial ports on the server unit rear panel. 

The Windows environment must be running to configure the UPS using the LAN Safe 

III software. 

Caution 

If the UPS signal cable is not attached, shut down and power off the server unit 

before connecting the cable. Also verify that the site wiring fault alarm is 

disabled. 

2. With the MCP running, from the ODT window enter the CLOSE CDnn, FREE 

CDnn, and FREE CTLnn commands. These entries ensure that the CD-ROM drive is 

available to Windows. 

3. Insert the LAN Safe III CD-ROM in the drive. The CD-ROM is provided with the UPS. 

4. On the Start menu, click Run. Click Browse to navigate to the subfolder 

/FAILSAFE/NT and the 95/setup.exe file. 

5. Invoke the Setup program and click OK to begin the installation. 

6. On the FAILSAFE Installation Options screen, select the following: 

2–12 3845 8188–000

• Standard option 

• Com port where the cable is attached 

• Unisys UPR series 


8. Click OK at the end of the installation. 

9. Double-click the battery icon (near the clock) to verify that communication is 

established with the UPS. 

10. Select Run Console for a display of the UPS information. 

11. Remove the LAN Safe III CD-ROM. 

12. In the ODT window, acquire the CD-ROM device and control, if applicable. 

Connecting the TCP/IP Network Drive 

To enable the virtual LAN, perform the following ping and the drive connection procedures. 

When performing any task related to Network Services, you should refer to the Network 

Services Implementation Guide. This document is shipped with your server. 

Pinging the MCP Environment from the Windows Server 


To ping the MCP environment from the Windows server, perform the following procedure: 

1. Ensure that the ICP4 is active and communicating after disk initialization is complete. 

2. On the command prompt in Windows, type ping cpmcp1 and then press Enter. 

The factory defaults are cpmcp1 with an IP address of 192.168.16.1. As part of the 

installation process, it is likely that you will change the host name. If you perform the 

ping connectivity check later, use the new host name, not cpmcp1. 

3. Perform one of the following actions: 

• If the ping is successful (no timeout message is returned), go to step 4. 

• If the ping fails, refer to the troubleshooting information in Section 4 of this guide, 

to solve the problem, then go to step 4. 

4. From Windows Explorer, click Map Network Drive on the Tools menu. 

Perform the following steps: 

a. Type \\CPMCP1\Installs in the Folder box. 

b. Select Connect using a different name. 

c. Ensure that the Reconnect at logon check box is not selected. 

d. Click OK. 

5. Type the appropriate user name and password when prompted. (The factory uses the 

password administrator.) 

6. Click OK. 

3845 8188–000 2–13


Windows Explorer shows several subdirectories. 

Setting Up Network Services Applications 

Note: Refer to the Network Services Implementation Guide for descriptions of the 

applications. 

1. In Windows Explorer, double-click the Setup application icon in the 

\\CPMCP1\Installs folder. 

The Windows Tools for ClearPath MCP screen appears. 

2. Expand the Product Selection tree view, select the Windows Tools check box, 

and then clear the check box next to each of the following components. 

Caution 

If you do not clear the appropriate check boxes, the following components 

cause errors during installation. 

Component Category 

Application Data Access Database Query and Reporting 

ClearPath MCP Interface to Microsoft 

Message Queuing (formerly, WinMQ for 

ClearPath MCP) 

ClearPath MCP Interface to Microsoft 

Transaction Integrator (formerly, COMTI for 

ClearPath MCP) 

Transaction Processing 


SAN DataMover ClearPath Integration Software 

WebSphere MQ for ClearPath MCP 

(formerly, MQ Series for ClearPath MCP) 


XVision Fonts Tools and Utilities 

3. Click Next. 

4. Review the Selected Products list and ensure that the correct applications are 

listed. 


Files are copied from the MCP environment to the Windows environment. This 

process takes a few minutes to complete. 

6. Review the Installation Progress window and ensure that all the applications were 

installed successfully. 


2–14 3845 8188–000

8. Disconnect the network drives mapped to the host. 

9. Click Halt in the Console for MCP window to halt the MCP environment. 

10. Restart the Windows operating system. 

11. Start the MCP environment again. 

Connecting to the External Public LAN 


The Shared Adapters feature can be configured to provide an “out-of-the-box” connection 

to the public LAN. As stated in the server installation policy, this configuration is not part of 

a normal system installation. For complete information, refer to the Network Services 

Implementation Guide. 

After you configure the connection to the public LAN, you can perform the Entity MIB 

Agent setup, if needed. Refer to the Network Services Implementation Guide. 

3845 8188–000 2–15


2–16 3845 8188–000

Section 3 

Complete Software Reinstallation 

Overview 

Before you install any software components, review the restrictions detailed in the 

“Third-Party Applications” section of this guide. 

Caution 

The customer must complete the reinstallation tasks in this section. Because 

the system software environment is complicated, it is recommended that you 

contact Unisys for assistance. Loss of data occurs if software is not installed 

correctly. 

Software reinstallation can be time-consuming. Unnecessary reinstallation of software 

should be avoided. However, a complete reinstallation sometimes is required. Information 

in this section can help you minimize the number of software components loaded in the 

event of a problem. 

Complete Reinstallation of the Software 

An integral part of Unisys service representative training includes the complete 

reinstallation of the software. This operation is sometimes referred to as “ground-zero” 

installation. Some reasons why you might have to resort to “ground-zero” installation 

follow: 

• The Windows boot or system disk developed a serious problem. Either the disk 

crashed, or the boot record is corrupted. As a result, you cannot initialize the 

Windows environment. If the partition structure is still viable, you might be able to 

reload Windows with a new directory name. 

• Windows is severely disabled due to corrupted files or registry problems. This 

condition might require reloading Windows with a new directory name. 

3845 8188–000 3–1


Partial Reinstallation of the Software 

Many software components are modular in nature. They can be reloaded and the 

applications can be restarted. The media to perform partial reinstallations is shipped with 

the system. Some configuration information cannot be restored without difficulty. 

Therefore, it is suggested that you do the following: 

• Create a Windows emergency diskette as soon as the system is stable. 

• Back up customer data files to tape on a regular basis. 

• Mirror disks, or use a RAID configuration whenever possible. 

• Do not lose the Administrator password, and do not allow unauthorized persons 

access to it. 

Some software is periodically updated. To install a new release, the cover letter might 

refer you to the information in this section. 

Required Media 

Make certain that you have the following items and media before you begin: 


• Operating system Reinstallation CD CD-ROM 


• Network Services Installation CD-ROM 




• Server Management CD-ROM 

• Server platform Documentation CD-ROM 


• MCP Product Documentation CD-ROM 


• Quick Installation Guide 

• Operating system Setup and Installation Guide 

Windows Operating System 

The following text explains how to reinstall and configure the Windows operating system. 

3–2 3845 8188–000

Reinstalling the Windows Operating System 

To reinstall the Windows operating system, refer to the Quick Installation Guide, and under 

the “Installing Your Operating System” topic, perform the steps to install an operating 

system. 

Configuring the Windows Operating System 


Set the performance and file dump options on the Windows operating system by 

performing the following steps: 

1. On the desktop, click Start, select Settings, select Control Panel, and then click 

System. 

The System Properties dialog box appears. 

2. Select the Advanced tab in the System Properties dialog box. 

3. In the Performance box, select Settings. 

The Performance Options dialog box appears. 

4. Select the Advanced tab on the Performance Options dialog box. 

5. In the Virtual memory box, click Change. 

The Virtual Memory dialog box appears. 

6. Select the C: drive. 

7. Select Custom size. 

8. Add 32 MB to the amount of total physical memory (RAM) available on your system, 

and enter that combined value, in megabtyes, in both the Initial size and Maximum 

size fields. If the combined value exceeds 4095 MB, enter 4095 MB in the size 

fields. 

Note: You can view the total physical memory available on your system on the 

System Information screen. On your desktop, click Start, select Programs, 

Accessories, System Tools, and click System Information. 

9. Click OK to close the Virtual Memory dialog box. 

10. Click OK to close the Performance Options dialog box. 

11. Click OK on the System Properties dialog box. 

12. Click Yes to Do you want to restart your computer now? 

Virtual Machine for ClearPath MCP Software 

If you perform a complete reinstallation of Windows, you must reinstall the Virtual 

Machine for ClearPath MCP software. 

The troubleshooting information in Section 4 of this document tells you when to reinstall 

the Virtual Machine for ClearPath MCP software. Make certain that you have the following 

items and media before you begin: 

3845 8188–000 3–3



• Virtual Machine for ClearPath MCP Administrative Console Guide 

The following steps restore the Virtual Machine for ClearPath MCP environment on the 

system hard disk drive. When this phase is completed, you can set up a halt/load disk and 

reload networking and MCP software components as necessary. 

Reinstallation Procedure 

Caution 

Do not attach the USB Image Enabler device until the Virtual Machine for 

ClearPath MCP software installation is complete. If the device is plugged in 

before the software installation is complete, the wrong device driver will be 

installed. 

Note: After reinstalling the Virtual Machine for ClearPath MCP software, you should 

reload the Network Services software and perform the networking configuration 

procedures. You must make certain that a valid halt/load unit exists for the MCP 

environment. 

To reinstall the Virtual Machine for ClearPath MCP software, follow these steps: 

1. Log on using an account with administrator privileges and the appropriate password. 

2. Insert the Virtual Machine for ClearPath MCP Software CD-ROM in the CD-ROM 

drive. 

The autorun program executes. A screen appears with the following choices: 

Install Virtual Machine for ClearPath MCP 

Install Hot Fix 

View Read Me 

Exit 

3. Select Install Virtual Machine for ClearPath MCP. 

4. Click Next on the InstallShield wizard welcome screen. 

5. Accept the license agreement, and then click Next. 

6. Fill out the customer information, and then click Next. 

7. Click Next to accept the default location for the destination folder. 

8. Click Next to accept the default location for the application data folder. 

9. Click Next to accept the default setup type. 


The files are copied from the CD-ROM to the hard disk. 

3–4 3845 8188–000


12. Click No when asked to restart the system. 

13. On the autorun screen, select Install Hot Fix. 

The Hot Fix Installer command screen appears, which automatically launches the 

Hot Fix readme file. 

You can choose to close the Hot Fix readme file. 

14. On the Hot Fix Installer command screen, type Yes. 

15. Type No when asked to restart the system. 

16. Press any key to continue. 

17. Click Exit on the autorun screen. 


19. Initiate the installation of any add-on software ordered with your system. For 

example, the Virtual Machine for ClearPath MCP Software High Encryption Add On. 

20. Attach the USB Image Enabler device to the USB port of the server. 

21. When the Found New Hardware Wizard appears asking if you want to install the 

device automatically, click Next. 

The Found New Hardware Wizard dialog box appears stating that the software 

installation for the device known as “USB Host for 1-Wire Microlan” is finished. 


23. Restart the computer. 

24. Click OK when the VM ClearPath MCP-Console Config message appears. 

Note: You might not need to remove and reattach the USB Image Enabler device 

each time you upgrade the Virtual Machine for ClearPath MCP software. 

Network Services Software 

If Network Services is installed on your machine and you want to reinstall it on your 

system, perform the following steps: 

1. Uninstall the Network Services software on your Windows 2003 system by following 

the steps for removing Network Services from the Windows server, as outlined in the 

Network Services Implementation Guide. 

2. Reinstall the Network Services software on your system by following the steps for 

installing Network Services on Virtual Machine for ClearPath MCP servers outlined in 

the Network Services Implementation Guide. 

MCP Software 


The following information explains how to rebuild the MCP environment using the MCP 

Quick Install CD-ROM. 

3845 8188–000 3–5


Using the Quick Install Program 

After you have verified that your system environment is ready for the Quick Install 

program, follow these steps: 

1. Insert the MCP Quick Install CD-ROM in the CD-ROM drive. 

2. Accept the license agreement. 

Quick Install searches your system for suitable drives for your MCP files. 

3. When prompted, select the drive on which to install the MCP software. 

Quick Install takes about 15 minutes to complete the loading of the MCP files. The 

Quick Install program eliminates the need for you to perform the configuration tasks 

required during a normal cold-start. 

The MCP Quick Install Successful dialog box appears informing you that you 

successfully installed the MCP, and requesting that you add DISK000.asd to the 

PCD. 

4. Click OK. 

The Quick Install program is now complete. 


6. If you installed the Virtual Machine for ClearPath MCP software before running the 

MCP Quick Install and have not restarted the system yet, restart the system and log 

on using an account with Administrator privileges. 

Configuring and Halt/Loading the MCP 

1. Click Yes when the warning box is displayed, and then close the welcome screen. Also 

close the Internet Explorer window. 

2. Double-click the Console for MCP icon. 

3. Click System Editor in the Console Configuration Error dialog box. 

4. Create and save a new PCD using the Auto Build feature. 

5. In the Partition Properties window, verify that valid entries exist for the halt/load disk 

drive, ODT, and MCP Memory size. 


Virtual Machine for ClearPath MCP Administrative Console Help for more information. 

6. If the MCP Memory size is increased in the previous step, perform the following steps: 

a. Click OK on the Partition Properties window. 

b. Select MCP on the main menu of the Console for MCP window, and then click Init 

MCP Control. 

7. On the main menu of the Console for MCP window, select MCP and then Run 

SystemLoader. 


Virtual Machine for ClearPath MCP Administrative Console Help for more information. 

3–6 3845 8188–000


8. Double-click the ODT icon, and then press the Home key to position the cursor. Press 

the Caps Lock key to set typing to uppercase letters. 

9. Wait for the ODT INPUT REQUIRED message. 

10. Type RECONFIGURE GROUP AS DEFAULT and transmit (press the + key on the 


Wait until the System/Loader reconfigures. 

11. Type STOP and transmit. 

This action terminates the loader and displays the EOJ message. 

The MCP initializes and displays the MCP screen. 

12. Type TERM DCSTATION TRUE, and transmit. 

Disk initialization is stopped awaiting two user inputs. 

13. Type HN = CPMCP1 and transmit. 

14. Type IL PK500 and transmit. 

15. In response to the Please Verify Time and Date waiting entry, type 

OK and transmit. 

The system fully initializes. You can use the ODT command HL UNIT to determine the 

halt/load pack (PK) number. 

Wait for the “System Initialization Completed” message. 

16. Type ??PHL and transmit (press the + key on the numeric key pad). 

17. Follow the IC cover letter instructions to load any applicable ICs. 

18. Load separately purchased software according to instructions in the ClearPath MCP 

software documents. 

3845 8188–000 3–7


3–8 3845 8188–000

Section 4 

Troubleshooting Information 

This section contains a list of problems that you might encounter during installation and 

configuration of the Virtual Machine for ClearPath MCP software. 

System Startup Problems 

Some of the following conditions can cause system startup problems: 

• Boot drive is not found, or boot-up error message appears. 

• Windows Setup does not initialize. 

• Virtual Machine for ClearPath MCP Setup program is not available. 

• Network Services software Setup program does not complete. 

• Console for MCP has initialization problems. 

• MCP does not initialize. 

Boot Drive Not Found, or Boot-Up Error Message Appears 

The boot drive is installed improperly, is unformatted, or is broken. 

When you power on the system, the boot drive activity light flickers in the upper bank of 

LEDs. 

When power is applied, the SCSI host adapter initializes and communicates with the drive, 

causing the activity light to flicker. If your system has several disk drives, you can compare 

the boot drive activity with another drive to isolate problems. 

The optional SCSI host adapter board has BIOS enabled. 

The server defaults to the boot drive. If Windows attempts to boot from drive “” in the 

SCA drive bays of SCSI Controller Channel “A,” it does not find the true system boot unit 

that is connected to the embedded SCSI adapter on the system board. The boot controller 

you are on has to be enabled, and the other device should be disabled. 

To enable BIOS, perform the following steps: 

1. Press Control+A when prompted during start up. 

2. Select Configure/View Host Adapter Settings, and then press Enter. 

3845 8188–000 4–1


3. Select Advanced Configuration Options, and then press Enter. 

4. Enable the Host Adapter BIOS. 

5. Save the configuration. 

6. Press Esc to exit. 

The Master Boot Record program on the boot drive displays an error 

message. 

The system partition files on the Windows boot drive might be corrupted. Some boot 

failure messages include Invalid partition table, Error loading operating system, and 

Missing operating system. Contact the Unisys Product Support organization. 

Windows Setup Does Not Initialize 

The setup files are corrupted. 

If the Setup application does not initialize and the Windows Licensing Agreement window 

does not display, a failure in the factory roll-back process might have occurred, or the 

following GUI mode Windows Setup files might have become corrupted: 

• $win_2000$.~bt 

• $win_2000$.~l 

Contact the Unisys Product Support organization. 

Virtual Machine for ClearPath MCP Setup Program Is Not 

Available 

The roll-forward program is not working properly. 

The Virtual Machine for ClearPath MCP Setup program is provided to reinitiate the Virtual 

Machine for ClearPath MCP software. The absence of the Virtual Machine for ClearPath 

MCP icon on the desktop indicates a failure of the factory load of the roll-forward files. The 

Virtual Machine for ClearPath MCP software and the Network Services software must be 

reinstalled. 

Note: Check first to see if the Virtual Machine for ClearPath MCP Setup icon was 

accidentally deleted. Use Windows Explorer to verify the presence of the autoset.exe file 

in the C:\Program Files\Unisys\Virtual Machine for ClearPath MCP folder. If the executable 

file exists in the folder, then you can run the roll-forward program by double-clicking on 

autoset.exe or by entering Autoset in the command-prompt window. 

4–2 3845 8188–000

Network Services Software Setup Program Does Not Complete 

To verify whether the Network Services software is installed, verify hardware and 

software by performing the following steps: 


2. Double-click Add/Remove Programs and look for ClearPath Network Services in 

the list of installed programs. 

Note: If it becomes necessary to reinstall the Network Services software, you must 

uninstall adapter devices before reinstalling the software. 

To verify that the NIC is functional, perform the following steps: 

1. On the desktop, right-click My Computer, and then click Manage. 

2. Under System tools, select Device Manager, and then expand the Network 

Adapters folder. 

3. Under the Network Adapters, select both VLAN and PublicNet. Both should 

report This device is working properly. 

Console for MCP Initialization Problems 


Some of the following conditions can cause problems: 

• Errors were introduced during the factory roll-back process or during the customer 

setup roll-forward procedure. 

• A complete software reinstallation was done, but Windows was not installed 

correctly. Problems might be in the areas of permissions, registry, or device drivers. 

• The boot/system disk partitions or directory structures were changed, and the Virtual 

Machine for ClearPath MCP software cannot locate vital components. 

In general, these problems revolve around the location of files and the properties 

associated with these files. Normally, you can resolve these problems using Windows 

Explorer and the Disk Administrator tool. 

Double-Clicking the Unisys Console for MCP Icon Has No Effect 

Check the properties of the shortcut icon and ensure that the application target is pointed 

to the correct file, in the correct folder, on the correct disk. 

1. Right-click Unisys Console for MCP on the desktop and click Properties. 

2. Select the Shortcut tab and note the application target. The target folder is your 

Virtual Machine for ClearPath MCP folder, which is usually C:\Program 

Files\Unisys\Virtual Machine for ClearPath MCP \ui.exe. 

Note: When reinstalling the Virtual Machine for ClearPath MCP software, delete the 

shortcut icons from the Startup menu and the desktop. Then replace the icons after the 

reinstallation, if desired. 

3845 8188–000 4–3


Logical Disk Files Have Improper Security 

If there are logical disk files that were created in a release prior to Virtual Machine for 

ClearPath MCP version 4.0, the Console for MCP displays a window that says that there 

are one or more logical disks with improper security. The logical disks that have improper 

security are not picked up by the Auto Build feature and cannot be used by the Virtual 

Machine for ClearPath MCP software until the proper security is set. To set the proper 

security attributes on the logical disk files, perform the following steps: 

1. Log on with Administrator privileges. 

2. Run the Console for MCP System Editor tool named MCP Disk Management, and 

click Logical Disk Operations. 

3. Click on Security in the Logical Disk File Management window. 

MCP Does Not Initialize 

You selected Load Bootstrap & Start, but the system failed to initialize. Verify that the 

unit you selected for the halt/load unit is labeled DISK and that the unit has been initiated 

by using the CM system command for the MCP software. Follow these steps: 

1. Using the Console System Editor, examine the PCD to see if you have a visible disk 

and ODT for the halt/load. Exit the System Editor. 

2. On the main menu of the Console for MCP window, select Partition Properties 

and apply the PCD to update the fields on the screen. 

3. Load the MCP and double-click ODT. 

TCP/IP Drive Connection Problems 

Several minutes elapse while for the Client Access Services software completely 

initializes and while the network DLP becomes Active and Communicating. You must 

wait until the NP210 is set to Active and Communicating before you proceed to test 

the connection between the MCP and Windows. 

To ensure that the VLAN connection is operational, from a command-prompt window, 

enter ping cpmcp1. 

A successful reply returns four responses from the MCP host. If you do not receive four 

responses, refer to the ClearPath HMP LX5000 and NX4200 Virtual LAN and 

Shared_Adapter Debug Flowchart at the following URL: 

http://www.support.unisys.com/unisys/aseries/mvweb/new/vlandbg.pdf 

The Ping Fails and NP210 Is Not Present 

If you cannot ping the MCP host and the NP210 is not present, verify that the PCD was 

generated after the Network Services software was installed. 

4–4 3845 8188–000

If the PCD Editor is not configuring ICP4 NP210, reinstall the Network Services software 

and reboot the system. Generate a new PCD to pick up the NP210. 

The Ping Fails and NP210 Is Active and Communicating 

Two MCP files are important to this process: the initialization files for the Core Network 

Services (CNS) and TCP/IP. The Windows configuration of the VLAN must match the 

information that these files supply to the MCP. 

Verifying the Windows Configuration 

The first step is to verify the Windows networking configuration. 

1. On the desktop, right-click My Network Places, and then click Properties. 

The Network and Dial-up Connections window appears. 

2. Select Advanced, and then click Network Identification. 

The Identification Changes dialog box appears. 

3. Under the Network Identification tab, click Properties. 

The Network Identification dialog box appears. 

4. Verify that the computer and domain names are correct. 

5. Click Cancel. 

6. Click Cancel. 

The Network and Dial-up Connections window reappears. 

7. Right-click PublicNet, and then click Properties. 

The PublicNet Properties dialog box appears. 

8. Under the General tab, select Internet Protocol (TCP/IP), and then click 

Properties. 

The Internet Protocol (TCP/IP) Properties dialog box appears. 

9. Verify that the default IP address for the PublicNet has been set to 10.0.0.3. Changes 

to this value must be reflected by changes to the MCP TCPIP Init file. The default IP 

address for the VLAN adapter has been set to 192.168.16.2. This value should not 

be changed. 

Verifying That the Required Software Is Running 


If the factory-default settings are in place, you can assume that the installation of the 

software is the source of the problem. Verify that HOSTNAME is cpmcp1 and that 

BNAVERSION is BNAV2. 

1. If the NP210 is Active and Communicating, then the CNS is running. Issue an NW 

CNS command from the ODT to confirm the status of the NP. 

2. Check to see that TCP/IP is running. Transmit the NW TCPIP + command. Then 

TCP/IP starts if it is not active. 

3845 8188–000 4–5


Verifying That the LMHOSTS and HOSTS Files Are Configured 

Correctly 

A successful ping requires that the host names in the LMHOSTS and HOSTS (when 

configured as DNS servers) files are correctly defined for adapter 192.168.16.1. Normally, 

a valid host name is supplied during the Network Services software installation. 

Make certain that a valid host name exists in the LMHOSTS file for the adapter. If no valid 

entry exists in the LMHOSTS file, supply one or reload the Network Services software. To 

supply the MCP host name that you have chosen, follow these steps: 

1. Using Windows Explorer, locate the C:\Program Files\Unisys\NXNet folder. 

2. Open the LMHOSTS.ORG file using Notepad. 

3. Verify that the MCP host name is correct. If not, change the name to the correct MCP 

host name. 

4. Locate the C:\WINNT\System32\Drivers\ETC folder and open the 

LMHOSTS.CNP file using Notepad. 

5. Verify that the MCP host name is correct. If not, change the name to the correct MCP 

host name. 

6. To make the changes effective, from a command prompt, enter NBTSTAT -R. 

Correcting Mismatched Settings in MCP Files 

The pings are still unsuccessful, or some of the conditions checked earlier do not match 

the factory settings. To change the settings, edit the two MCP initialization files. 

Caution 

If the init files are not available, or if the BNAVERSION is not set to BNAV2, the 

MCP software was not properly installed. Reload the MCP software (refer to 

Section 3). 

To modify the init files and restart MCP networking, perform the following tasks: 

1. In MARC, use CANDE and transmit GET *CLEARPATH/INIT/CNS. Ensure that 

NP210 has an established connection group. 

2. Transmit GET *CLEARPATH/INIT/TCPIP. 

The TCPIPHOSTNAME and the TCP/IP address are assigned, and a connection is 

made to the connection group established in step 1. You can verify that the correct 

Windows computer name is mapped to the MCP by using the NW TCPIP map 

statement. Also, you can add a default router at the end of this file. 

3. If the MCP host name is to be changed, perform a halt/load command. 

The ping commands should now be responding correctly. 

4–6 3845 8188–000

You can now map a network drive using Windows Explorer. 


3845 8188–000 4–7


4–8 3845 8188–000

Section 5 

Third-Party Applications 

This section contains restriction information about third-party applications used in 

conjunction with Virtual Machine for ClearPath MCP software. 

Windows CD and DVD Writer Programs Not 

Supported on Systems Running Virtual Machine for 

ClearPath MCP Software 

Windows CD and DVD writing software, such as Roxio Easy CD Creator, NERO Burning 

ROM, and Pinnacle Instant CD/DVD, is not compatible with Virtual Machine for ClearPath 

MCP software, and must not be installed on a system running the Virtual Machine for 

ClearPath MCP software. 

Note: Roxio Easy CD Creator is a product of Roxio, Inc. NERO Burning ROM is a product 

of Ahead Software AG. Pinnacle Instant CD/DVD is a product of Pinnacle Systems. 

Tape Sharing Among Multiple Hosts Not Standard 

Supported Feature 

Tape sharing among multiple hosts in a storage area network (SAN) environment, where 

one or more hosts is a Virtual Machine for ClearPath MCP server, is not a standard 

supported configuration. If this feature is needed, contact your Unisys Marketing 

representative. 

Windows Tape Management Program Supported on 

Virtual Machine for ClearPath MCP Systems 

Windows Backup utility is the only Windows tape management program qualified and 

supported on a Virtual Machine for ClearPath MCP system. This backup utility uses the 

Removable Storage service to manage removable media, such as tape devices. All other 

Windows tape management software, such as Veritas Netbackup, are not supported for 

use on a Virtual Machine for ClearPath MCP system. 

3845 8188–000 5–1

Third-Party Applications 

5–2 3845 8188–000

Appendix A 

Peripherals Information 

This appendix contains restriction information about peripherals used with your system. 

Using Physical Disk Drives Larger Than 100 GB 

The maximum disk size supported by the MCP is 131,064,000,000 bytes. There are 

different calculations to convert bytes to Gigabytes (GB). The common tendency is to 

assume that 1000^3 bytes equals 1 GB. However, the precise computation of 1 GB is 

1024^3 bytes. Therefore, the maximum disk size for MCP disks in Gigabytes is 122 GB, 

not 131 GB. 

When using disk drives that are over 100 GB in capacity, always check the size in bytes. 

While Windows and most commodity storage systems compute one GB to be 1024^3 

bytes, some vendors might use a different calculation. 

Follow the guidelines below to configure a large disk for the MCP in a MCPvm server. 

In JBOD Configuration 

• Disk drives that are used for MCP logical disks have no physical size restrictions. The 

Console for MCP System Editor does not allow creation of a logical disk to exceed the 

MCP limit. If performance is not a concern, you can create multiple MCP logical disks 

to utilize all the disk space. 

• Disk drives that are greater than 122 GB (122 * 10243 = 130,996,502,528 byes) 

cannot be used for VSS1 disks. 

• Disk drives that are greater than 173 GB (173 * 10243 = 185,757,335,552 bytes) 

cannot be used for VSS2 disks. 

In a RAID Configuration 

In a RAID configuration, a disk unit is a logical unit number (LUN) created from a RAID 

group consisting of multiple physical disks. Each physical disk can be of any size, but the 

size of a LUN must follow the guidelines below: 

• For VSS disks, be sure the size of the LUN created is within the MCP limit for VSS 

disks: up to 122 GB (130,996,502,528 bytes) for VSS1 and 173 GB (185,757,335,552 

bytes) for VSS2. 

• For MCP logical disks, there is no size limit on the LUN. Multiple MCP logical disks can 

be created on the same LUN in a RAID configuration without impacting performance. 

3845 8188–000 A–1


Data Migration Issues Using I/O Greater Than 64K 

Block sizes in excess of 65,535 bytes (64K) to tape and disk devices are now supported. In 

order to leverage this feature, several configuration restrictions must be met. 

• The MCP level must be 48.189.8276 or greater. 

• For Library Maintenance to use the new capability, the LMBLOCKSIZE option can be 

set to 64,800 words by specifying “SYSOPS LMBLOCKSIZE 64800”, or the blocksize 

can be specified in the copy statement as shown here: 

COPY TEST TO TAPE (SERIALNO=123456, BLOCKSIZE=64800) 

• Adapters in use must support I/O greater than 65,535 bytes. 

In order for this feature to work, adapters must be capable of supporting the large 

blocksize as well. Two modes of operation are selected by a switch in the boot.ini file: 

non-PAE mode and PAE mode. If there is a /PAE switch in the active entry of the boot.ini 

file, the system is in PAE mode. 

In non-PAE mode, the system is limited to 4 GB of RAM. This is not a problem for any MCP 

partition, because it allows the maximum E-mode memory to be supported by the Virtual 

Machine, as well as an ample amount of memory for disk caching. All supported Adaptec 

and Emulex adapters work in this environment. 

In PAE mode, the system is capable of supporting more than 4 GB of memory. However, 

the driver of the 64-bit Adaptec 39160 is not fully PAE-mode compliant. Therefore, I/O 

length in this mode is further restricted to 61,440 bytes. When Adaptec releases a 

compatible driver, this restriction is removed. If you choose to operate in this mode, you 

must specify a blocksize that is 61,440 bytes or less. This is true of Library Maintenance, 

DM Utilities, and other user programs. 

You can choose to set your LMBLOCKSIZE to 9900 words using the SYSOPS command to 

cause Library Maintenance to restrict I/O block sizes to 59,400 bytes (under the 61,440 

byte limit with /PAE set). An example of the SYSOPS command is 

SYSOPS LMBLOCKSIZE=9900 

All Emulex adapters correctly support PAE mode and are capable of supporting the long 

blocksize. 

Information About Multiple Paths Disk 

Configurations on EMC Storage Systems 

All MCP logical disks configured on an EMC Storage system must use PowerPath for load 

balancing and failover capabilities. For VSS disks, Virtual Machine for ClearPath MCP offers 

two options, PowerPath or Control Groups. The PowerPath option is the recommended 

method because it more effectively uses the capability of the storage systems, requires 

less configuration manipulation and supports both logical disks and VSS Disks. The two 

options are exclusive of each other. By default, Control Group detection is disabled. You 

should enable it only if PowerPath is not installed. 

A–2 3845 8188–000

Configuring CLARiiON Storage Systems for Control 

Groups 

Each CLARiiON RAID storage system offers two storage processors, SPA and SPB. On a 

CX200, or CX300, each storage processor (SP) has two ports (connectors). These ports are 

connected internally to the same Fibre Channel bus to the devices. Typically, these ports 

are used for connecting two different servers in a Windows clustering configuration. 

However, to configure control groups in the MCP environment, both ports of the same SP 

must be connected to the Fibre Channel host bus adapters on the same server, and that 

SP must own all of the LUNs to be detected by the server. In this case, although the PCD 

presents two paths to the MCP (that is, two controls) to the same unit, and the MCP is 

load balancing between the two controls, it is still the same Fibre Channel bus that is 

performing the I/O operation at the storage end. The load balancing effect is limited. 

On a CX400, CX500, CX600, or CX700, each SP has 2 or 4 ports and each port is an 

independent Fibre Channel bus to the devices. This multiple port design supports 

connections to the same server or multiple servers, whether it is a clustered configuration 

or not. To configure these systems for control groups in the MCP, you connect the host 

bus adapters on the same server to the multiple ports on the same SP and assign all the 

LUNs to that SP. In this case, the load balancing is more effective because it is also 

happening at the SP end. 

Both Direct Connect and SAN Attach commands are supported for Control Groups. 

Using PowerPath Administrator with VSS Disks 

When PowerPath is used to manage the multiple paths I/O for the VSS disks, you can use 

the PowerPath Administrator to monitor the VSS I/O activities. VSS disks are displayed in 

the PowerPath Administrator the same way Windows disks are. The PowerPath 

Administrator disk number matches the Windows Disk Manager disk number. 

VSS Disks Are Displayed in Disk Manager 


VSS disks are visible in both the Windows operating system and the MCP environment. 

However, the AfDisk driver controls the I/O to VSS disks and blocks them from any 

destructive I/O from a Windows application. Only MCP applications and the VM software 

have full access to the VSS disks. 

In Windows Disk Manager, VSS disks are shown as Unknown and Uninitialized with 

unallocated space. When you select the disk properties, the VSS Disk tab shows VSS 

information. In Veritas Volume Manager, VSS disks are shown as Basic disks with no 

signatures. 

Windows prompts to write signatures to VSS disks. However, writing signatures to VSS 

disks from Windows application is blocked by the AfDisk driver and does not take place. 

Please refer to Windows Knowledge Base article KB838913 for additional information on 

Windows Disk Initialization issues. The hot fix described in the article can be downloaded 

from the Unisys Support Online Web site. 

3845 8188–000 A–3


Using VSS Disks With Dell PERC RAID Controller 

Causes Error Messages 

It is recommended that physical disks on the DELL PERC RAID controller be configured as 

Windows disks and used as MCP Logical disks. 

When physical disks are configured as VSS disks, error messages are displayed in the 

ODT and the Windows Application Log after every halt/load. Though the error messages 

might appear to be serious, the VSS disks are functional with no known problems. This 

issue is specific to the DELL PERC RAID Controller. 

This is an example of the VSS disk error message from the MCP, displayed on the ODT: 

PK2001 ERROR DETERMINING UNIT STATUS:FATE=02, Unit H/W error, 

Hrslt=010000 000005, Ctl RD=0200 F000 0400 0000 0000 0000 045D 

This is an example of the associated Application Eventlog entry: 

An error has been returned to NativeScsi. Information being 

returned is: 

GetLastError = 1117 (0x45d) for target 5 lun 0 

AfDisk Driver Error Messages in the System Event 

Log 

On a system with CLARiiON storage systems configured with multiple paths, but without 

PowerPath running, the following AfDisk driver error message might appear in the System 

Event Log. Multiple instances of the error message can be logged, depending on how the 

LUNs are configured in the storage system. These messages are expected and can be 

ignored. 

Event ID: 5 

Description: The AsLib function call AsLibSendIoctl for 

Device failed. 

A–4 3845 8188–000

Index 

A 

AfDisk driver, A–4 

C 

CLARiiON storage systems, A–3 

ClearPath enterprise server 

installation policy, 1–2 

ClearPath Enterprise server 

system architecture, 1–6 

system overview, 1–5 

configuring 

MCP, 2–10 , 3–6 

uninterruptible power supply, 2–12 

Windows operating system, 2–4 , 3–3 

Windows Server 2003, 2–11 

connecting, external public LAN, 2–15 

Console for MCP, 4–3 

creating, MCP logical disk, 2–9 

Customer Response 

data to provide, 2–1 

Hotline, 2–1 

policy, 2–1 

D 

data migration, A–2 

disabling hyperthreading, 2–5 

disk drives, large, A–1 

documentation, 1–3 

E 

EMC storage systems, A–2 

errors 

attempted boot from the wrong drive, 4–1 

F 

FS1300 server, 1–1 

G 

ground-zero reinstallation, 3–1 

guidelines, installation, 1–3 

H 

hyperthreading, disabling, 2–5 

I 

installation policy 

customer responsibility, 1–2 

service representative responsibility, 1–2 

installation 

guidelines, 1–3 

Microsoft agreement, 1–3 

policy, 1–2 

prerequisites, 1–3 

site-specific information, 1–3 

installing 

mass storage adapter device drivers, 2–5 

MCP software, 2–7 , 3–5 

Network Services software, 2–8 

unsigned drivers, 2–6 


software, 2–7 


Windows operating system, 2–4 

Windows Server 2003, 2–4 

L 

LAN connecting, 2–15 

Libra 300 server, 1–1 

logical disk 

creation, 2–9 

security, 4–4 

M 

mass storage adapter device drivers, 2–5 

MCP Quick Install, 2–9 

3845 8188–000 Index–1

Index 

MCP software, 1–7 

installing, 2–7 

reinstalling, 3–5 

media and books 

listing, 1–3 




N 

NetBios enabling, 2–8 

Network Services software 

enabling, 2–8 



P 

peripherals, A–1 

PowerPath Administrator, A–3 

Q 

Quick Install program, 2–9 

R 

reinstallation, software, 3–1 

partial, 3–2 

S 

setup, 2–1 

mechanical, 2–1 

required media, 2–3 


TCP/IP drive connection, 2–13 

software reinstallation, 3–1 

complete, 3–1 

ground-zero, 3–1 


Network Services software, 3–5 

overview, 3–1 

partial, 3–2 

required media, 3–2 



Windows operating system, 3–3 

software tools, 1–5 

System Editor, 1–5 

Windows Event Log Viewer, 1–5 

storage systems 

CLARiiON, A–3 

EMC, A–2 

system architecture 




Windows, 1–7 

System Editor, 1–5 , 1–7 

system features, 1–5 

system setup, 2–1 

T 

TCP/IP, 2–13 , 4–4 

third-party applications, 5–1 

troubleshooting 

bad boot record, 4–2 

boot drive not found, 4–1 

boot up, 4–1 

Console for MCP does not initialize, 4–3 

Console for MCP icon not working, 4–3 

ICP4 is active and communicating, 4–5 

ICP4 is not present, 4–4 

improper logical disk file security, 4–4 

MCP does not intialize, 4–4 

Network Services setup does not 

complete, 4–3 

peripherals, A–1 

system startup, 4–1 

TCP/IP drive connection, 4–4 

third-party applications, 5–1 

Virtual Machine setup not available, 4–2 

Windows setup does not initialize, 4–2 

U 

uninterruptible power supply (UPS), 2–12 

unsigned drivers, installing, 2–6 

UPS (uninterruptible power supply), 2–12 

USB controller, enabling, 2–6 

USB Image Enabler device, 2–6 

V 

Virtual Machine for ClearPath MCP software, 

1–7 



reinstallation, 3–3 

Index–2 3845 8188–000

VSS disks, A–3 , A–4 

W 

Windows Event Log Viewer, 1–5 

Windows operating system 

configuring, 2–4 , 3–3 



Windows Server 2003 

configuring, 2–4 , 2–11 , 3–3 



Index 

3845 8188–000 Index–3

Index 

Index–4 3845 8188–000

*38458188-000* 

3845 8188–000

ClearPath Enterprise Servers Virtual Machine for ClearPath MCP ...

Create successful ePaper yourself

Delete template?

Save as template?