ClearPath Enterprise Servers
Virtual Machine for ClearPath MCP
Installation Guide
Virtual Machine for ClearPath MCP Version 10.0, SP2
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.
Section 1. Introduction Documentation Updates ... 1–1 Audience ... 1–1 What’s New? ... 1–1 Conventions ... 1–2 Prerequisites ... 1–2 Section 2. Overview System Overview ... 2–1 System Features ... 2–1 System Architecture ... 2–2 ClearPath Server Installation Policy ... 2–3 Installation Guidelines ... 2–4 Prerequisites for Installation ... 2–4 Site-Specific Information ... 2–4 Media and Books ... 2–4 Platform Documents and Media ... 2–5 ClearPath Enterprise Server Documents and
Media ... 2–5 Virtual Machine for ClearPath MCP and MCP Quick
Install Media ... 2–5 MCP Release Software ... 2–6 Software Tools and Diagnostics ... 2–6
Section 3. Setting Up the Server
Mechanical Setup ... 3–1 What To Do About Damaged, Missing, or
Incorrect Parts... 3–1 Software Setup ... 3–2 Required Media... 3–3 Setting Up BIOS ... 3–4 Configuring the Dell Remote Access Controller ... 3–6 Installing the Windows Operating System ... 3–7 Configuring the Windows Operating System... 3–9 Installing the Virtual Machine for ClearPath MCP
Software ... 3–15 Installing Network Services Software ... 3–16 Enabling NetBIOS Over TCP/IP ... 3–16 Configuring the Operating System for Accessing
Creating the MCP Logical Disk Using the MCP
Quick Install DVD ... 3–18 Connecting the TCP/IP Network Drive ... 3–22 Connecting to the External Public LAN ... 3–23 Configuring the Optional Uninterruptible Power
Supply (UPS) ... 3–23 Configuring Fibre Channel and SCSI Connections ... 3–23
Section 4. Configuring External Storage Subsystems
Overview ... 4–1 Host Bus Adapter Configuration ... 4–1 Fibre Channel HBA ... 4–1 SCSI HBA ... 4–3 Tape Subsystems ... 4–4
Installing and Removing the VMMCPDevices Class
Driver AcDevice.sys ... 4–5 Powering Off a Tape Subsystem ... 4–7 Disk Subsystems ... 4–7 MCP Disk Formats ... 4–7 Disk Caching ... 4–10 Multipath I/O for Disks ... 4–12 MCP Control Groups ... 4–13 Windows Native MPIO ... 4–14 EMC PowerPath ... 4–15 Lowest SCSI Address Implementation for
PowerPath and MPIO ... 4–16 Additional Considerations ...4–18 Large Configuration Considerations ...4–18 Recovery after Losing All Paths Considerations ... 4–20 Configuring Multipath VSS Disks ... 4–20 CLARiiON Storage Systems ... 4–22 Symmetrix Storage Systems ... 4–30
Section 5. Completing Software Reinstallation
Overview ... 5–1 Complete Reinstallation of the Software ... 5–1 Partial Reinstallation of the Software ... 5–2 Required Media... 5–2 Before You Begin ... 5–2 Preparing a Replacement Drive for the Operating System
Load ...5–3 Reinstalling the Software ...5–3 Finalizing the Reinstallation ... 5–4
Section 6. Backing Up the Server
Section 7. Troubleshooting Information
General Hardware Installation Problems ... 7–1 System Startup Problems ... 7–1 Network Services Software Setup Program Does Not
Complete ... 7–2 Console for MCP Initialization Problems ... 7–2 TCP/IP Drive Connection Problems ... 7–3 The Ping Fails and NP210 Is Not Present ... 7–3 The Ping Fails and NP210 Is Active and
Communicating ... 7–3 Index ... 1
Figures
3–1. USB Image Enabler Device ... 3–14 4–1. CLARiiON Direct Connect using PowerPath ... 4–25 4–2. CLARiiON SAN Attach using PowerPath... 4–26 4–3. CLARiiON Direct Connect using Control Groups ... 4–28 4–4. CLARiiON SAN Attach using Control Groups... 4–29 4–5. CLARiiON using Two Groups with MCP Mirroring ... 4–30 4–6. Symmetrix Direct Connect using PowerPath or Control Groups ... 4–32 4–7. Symmetrix SAN Attach using PowerPath ... 4–34 4–8. Symmetrix SAN Attach using Control Groups ... 4–35
Tables
This document is the primary source of information for the setup and configuration of the Virtual Machine for ClearPath MCP enterprise server.
Documentation Updates
This document contains all the information that was available at the time of publication. Changes identified after release of this document are included in the problem list entry (PLE) 18828928. To obtain a copy of the PLE, contact your Unisys representative or access the current PLE from the Unisys Product Support Web site:
http://www.support.unisys.com/all/ple/18828928
Note: If you are not logged into the Product Support site, you will be asked to do so.
Audience
This document is directed to Unisys service representatives and to customers.
What’s New?
New or Revised Information Location
Updated procedures to account for
VM SP2 software. Section 3: Setting Up BIOS
Changing the Video Adapter
Installing Virtual Machine for ClearPath MCP Software
Configuring and Halt/Loading MCP Configuring the Optional Uninterruptible Power Supply (UPS)
Added new procedures. Section 3:
Configuring the Dell Remote Access Controller
Conventions
This document is applicable to the Libra Model 450 and FS1750 platforms. The Libra Model 450 server is a general-purpose server. The FS1750 server has been custom designed for the financial services line of business. 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.
Note: The term 64-bit used throughout this document refers to the underlying processor type and the operating system. Specifically, the term refers to the 64-bit extended addressing capabilities offered by Intel EM64T processors, along with the x64 versions of the Microsoft Windows operating systems. In the context of this document, it does not refer to execution on the Intel Itanium processor family (IPF). Currently, no Itanium processor platform is supported for execution of VMMCP.
Prerequisites
To use this guide, you should be familiar with the following:
• The Windows graphical user interface (GUI) used by the Console for MCP
• The MCP ODT window
• The MARC screen environment and CANDE
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 one or two quad-core Intel Xeon DP microprocessors, system memory size of 24 GB for one quad-core configuration and 48 GB for two quad-core configuration, as well as hot-pluggable hard drives, expansion slots, power supplies, and system fans.
System Overview
The system is comprised of the following features and architecture.
System Features
The server offers a completely integrated tower or rack-mounted configuration. The server includes the following:
• One or two quad-core Intel Xeon CPU X5560 2.8 GHz microprocessors
• Support for symmetric multiprocessing (SMP)
• 24 GB of system memory for single socket and 48 GB for dual socket
• Support for up to sixteen 2.5-inch, internal, hot-pluggable serial-attached SCSI (SAS) hard drives
• Available as a rackmount system or a tower system
• Two hot-pluggable, 1100-watt power supplies
• Redundant, hot-pluggable system cooling fans
• An intrusion switch that signals the appropriate systems management software if the top cover is opened
• Six PCIe Gen 2 card slots:
− One PCIe x4 Connector x4 Link Slot 1
− One PCIe x16 Connector x8 Link Slot 2
− Four PCIe x8 Connector x4 Link Slot 3, 4, 5, 6
• An integrated Matrox G200 video subsystem with 128 MB DDR2 memory shared with iDR
• An optional remote access card that provides remote management functions
• Two dual port 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, including video, four universal serial bus (USB) ports, two dual-port NIC connectors, and an optional remote access connector
• Front-panel connectors, including two additional USB ports and one video port This section is the starting point for the installation process, including the following:
• ClearPath enterprise server installation policy
• Prerequisites for installation
• Software tools and diagnostics
• Overview of the system
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. 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
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.
For the Libra Model 450 and FS1750 systems, the supported operating system is Windows Server 2008 R2 Enterprise x64 with SP1.
Virtual Machine for ClearPath MCP
The Virtual Machine for ClearPath MCP is a series of applications running within the 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.
MCP
The MCP environment supports the MCP operating system 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.
ClearPath Server Installation Policy
WARNING
This system cannot be installed by a customer. The server must be
installed and configured by a qualified Unisys service representative or by a licensed third-party installer. Serious injury can result from improper
installation techniques.
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 with information regarding power sources or environmental considerations.
• System setup and configuration (Unisys service representative and customer) The customer must be present and 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 unpacking, setup, configuration, and testing the system. Unauthorized persons attempting to install the system can cause serious software problems requiring extensive remedial work.
• Arrival quality reporting (Unisys service representative)
It is important that the Unisys service representative describe any 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 is extended to use this information to make improvements.
• Reinstalling the system software (customer or purchased services) 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 are included in this document. To determine whether you must reinstall the system software components, refer to Section 5, “Completing Software Reinstallation.” You might also need to refer to other documents to install networking software.
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.
• 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 cannot assume this responsibility.
Prerequisites for Installation
A number of items are needed to initially install and configure the system (which must done by the Unisys service representative) or to reinstall the software (which may be done by the customer). Some system components are already installed or set up by the factory. In this case, the materials needed are minimal. Review the following information before beginning the installation process.
Site-Specific Information
If the server is to be attached to an existing network, the service representative works with the site administrator to resolve configuration questions. The following are needed:
• IP addresses for the host system on the customer LAN
• Host names of existing Unisys host systems that are visible using BNA
Media and Books
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.
Platform Documents and Media
The following platform documents and media are required:
• Getting Started with Your System
• Systems Management Tools and Documentation DVD, which includes the following:
− Dell Systems Build and Update Utility
− Dell OpenManage™ Server Administrator
− Dell OpenManage IT Assistant
− Dell Remote Access Controller
− BMC Management Utility
− Dell-optimized Drivers
− Dell Online Diagnostics
− Documentation
• Windows Server 2008 R2 Enterprise x64 with Service Pack 1 (SP1) operating system
• Resource Disc Windows System Resource Manager CD-ROM
• Operating system Setup and Installation Guide
• Rack Installation Guide
• Operating system Getting Started
ClearPath Enterprise Server Documents and Media
The following ClearPath Enterprise Server documents and media are required:
• Libra Model 450 or FS1750 Quick Start Installation Guide
• Libra Model 450 or FS1750 Product Documentation Download the product documentation from:
http://www.support.unisys.com
Virtual Machine for ClearPath MCP and MCP Quick Install
Media
The following Virtual Machine for ClearPath MCP and MCP Quick Install media are required:
• Virtual Machine for ClearPath MCP Software CD-ROM
• ClearPath Enterprise Server Virtual Machine for ClearPath MCP Quick Install DVD
MCP Release Software
The following MCP software is required:
• ClearPath MCP Release Software CD-ROM Interim Corrections (ICs) are available at:
http://www.support.unisys.com/common/fixes.cfm?pla=AS&nav=AS • Keys media
• Supplemental Software Release
• Core ClearPath MCP document set
Software Tools and Diagnostics
The following tools are provided as part of the normal system environment and may be used by the customer or the Unisys service representative to help diagnose problems.
• Utility Partition System Utilities
Use the Utility Partition System Utilities to run diagnostic tests on 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 on the screen.
• 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 Help.
• Windows Event Log Viewer
Use the event log viewer to diagnose system events when a service fails to initialize or an environmental problem arises.
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.
Note: A Unisys Service Representative must perform the initial mechanical and software setup for the system.
Mechanical Setup
Refer to additional documentation contained on the server platform DVD-ROMs 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
If installation problems occur because of damaged, missing, or incorrect parts, 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.
Site and Order Data
• Original order number
• Marketing branch organization number
• Customer name
• Shipping address
Unisys Service Representative Data
• Requester name
• Life number
• Requester phone number
• Unisys service representative assignment number
• Branch organization number
Problem Data
• Style number and part number
• Quantity system style
• System serial number
Damaged Parts
If any 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 Unisys Product 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.
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 Unisys Product 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:
• Setting up BIOS
• Installing the Windows operating system
• Configuring the Windows operating system
• Installing Virtual Machine for ClearPath MCP software
• Installing Network Services software
• Enabling NetBIOS over TCP/IP
• Configuring the operating system for accessing MCP shares
• Creating the MCP logical disk using the MCP Quick Install DVD
• Connecting the TCP/IP network drive
• Connecting to the external public LAN
• Configuring the optional uninterruptible power supply (UPS)
• Configuring Fibre Channel and SCSI connections
Required Media
Be sure you have the following items and media before you begin:
• Virtual Machine for ClearPath MCP Software CD-ROM
• Network Services Installation CD-ROM
• ClearPath Enterprise Server Virtual Machine for ClearPath MCP Quick Install DVD
Interim Corrections (ICs) are available at:
http://www.support.unisys.com/common/mcp/downloads.aspx?pla=AS&nav=AS • Libra Model 450 or FS1750 Product Documentation
Download the product documentation from:
http://www.support.unisys.com
• ClearPath MCP Product Documentation Download the product documentation from:
http://www.support.unisys.com
• Libra 450 Server or FS1750 Server Quick Start Installation Guide
• Operating system Setup and Installation Guide
• Customer-supplied virus protection software
• Windows Server 2008 R2 Enterprise x64 with SP1 DVD
• Dell Systems Management Tools and Documentation DVD, version 6.1 or later
Setting Up BIOS
Caution
Take the following precautions before performing this procedure:
• Disconnect all cables attached to external peripheral devices.
• Disconnect all network cables.
• Ensure that the Image Enabler device is not attached.
Failure to follow these precautions can result in a non-operational system or destruction of certain data files.
To properly set up BIOS, perform the following steps:
1. Ensure that the keyboard, mouse, and monitor are connected to your system and then power on the server.
2. Verify that the BIOS splash screen displays the Unisys logo.
Note: In the BIOS settings, ensure that the Logical Processor and Virtual CD-ROM settings are disabled.
If the Unisys logo does not appear, perform the following steps:
a. Insert the OEM ready ES3000 ES3560T G1 BIOS media in the drive (USB thumb drive or CD-ROM).
b. Reboot the server.
The BIOS flash update utility automatically starts and the Flash BIOS Update Program appears.
c. Follow the on-screen instructions.
The Flash BIOS Update Program completes. d. Press any key to reboot the server.
The server powers off for a few seconds and then restarts.
e. During the boot process, press F2 when prompted to open the BIOS menu. The BIOS menu appears.
f. Ensure that the server BIOS options are set to the recommended values listed in Table 3–1. The settings correspond to BIOS version 2.2.8 or later.
Table 3–1. BIOS Settings for the Libra 450 Platform
Category Setting Description ClearPath Setting
Memory System Memory Test Disabled
Note: This option is a user preference.
Table 3–1. BIOS Settings for the Libra 450 Platform
Category Setting Description ClearPath Setting
Memory Operating Mode Optimizer Mode Node Interleaving Enabled
Note: This option can be enabled only on servers with two sockets and 48 GB of physical memory.
Processor Logical Processor (threading) Disabled Virtualization Technology Disabled Adjacent Cache Line Prefetch Enabled Hardware Prefetcher Enabled Execute Disable Enabled Number of Cores per Processor All Turbo Mode Disabled C1E Disabled Processor C States Disable SATA Settings Embedded SATA ATA Mode
Port A Auto Port B Off Boot Settings Boot Mode BIOS
Boot Sequence 1. SATA Optical Drive 2. Hard Disk C Integrated Devices Integrated RAID Controller Enabled
User Accessible USB Ports All Internal USB Port On Embedded NIC1 and NIC2 Enabled
Embedded Gb NIC1 Enabled with PXE Embedded Gb NIC2 Enabled
Embedded NIC3 and NIC4 Enabled Embedded Gb NIC3 Enabled Embedded Gb NIC4 Enabled OS Watchdog Timer Disabled I/OAT DMA Engine Disabled SR-IOV Global Enable Disable
Table 3–1. BIOS Settings for the Libra 450 Platform
Category Setting Description ClearPath Setting
Power Management CPU Power and Performance Management
Maximum Performance Fans Power and Performance
Management Maximum Performance Memory Power and Performance Maximum Performance System Security Power Button Enabled
NMI Button Note: This option is a user preference. It is recommended if the user is required to initiate an NMI dump.
AC Power Recovery Last AC Power Recovery Delay Immediately
g. Press ESC.
h. Select Save Changes and Exit and press Enter. i. Remove the BIOS media.
The BIOS splash screen displays the Unisys logo.
Configuring the Dell Remote Access Controller
If a Dell Remote Access Controller (iDRAC6) Enterprise card is installed on the server, perform the following steps to configure the card:
1. Connect a LAN cable from the iDRAC6 Enterprise card port on the back of the server to the network.
2. Reboot the system.
A Remote Access Setup message appears. 3. Press CTRL + E.
The iDRAC6 Configuration Utility appears.
4. Select LAN User Configuration and press Enter.
5. Set the proper IPv4 address, subnet, and Default Gateway for your system. 6. Press Enter.
7. From the iDRAC6 Configuration Utility screen, select LAN Parameters and press Enter.
Note: The Libra 450 and FS1750 Servers with iDRAC6 have a default IP address of 192.168.0.120, a default username of root, and a default password of
calvin. 9. Press ESC.
10. Select Save Changes and Exit to exit the utility.
Installing the Windows Operating System
Perform the following steps to install the Windows operating system on your server: 1. Insert the Dell Systems Management Tools and Documentation DVD (version 6.4
or later) in the DVD drive.
2. Select Dell Systems Build and Update Utility in the initial screen.
Note: If you do not select an option within 10 seconds, the system boots automatically through the DVD and executes the Dell Systems Build and Update Utility.
3. Click Configure for Server OS Installation in the right pane. If the screen becomes blank, move the mouse to view the screen.
4. Type the correct information for your site in the Set Date and Time screen and click Continue.
The Select an Operating System to Install screen appears.
5. Select the Microsoft Windows Server 2008 R2 SP1 option and click Continue.
The Select RAID Configuration screen appears. If the RAID is preconfigured, the Select RAID Configuration screen displays the existing RAID configuration and points the boot virtual disk to the first disk array.
6. Select the Retain RAID Configuration existing on the system option and click Continue.
The Operating System Installation Summary screen appears.
7. Select the Eject CD/DVD Automatically option and click Apply Now.
The system completes the remaining steps in the System Build and Update Utility, ejects the DVD, and reboots the server.
8. Remove the Dell Systems Management Tools and Documentation media from the DVD drive.
Note: If the option to eject the CD/DVD automatically is set, the DVD drive ejects the media and the server reboots. When the server reboots, the DVD drive closes. If the media is still in the DVD drive when it closes, the Dell Systems Build and Update Utility restarts again.
After the server reboots, a message appears prompting you to insert the Windows 2008 DVD in the DVD drive.
9. Insert the Windows Server 2008 R2 Enterprise with SP1 DVD and click OK. A message appears indicating that a valid operating system media is found.
10. Click OK to start the installation.
11. Click OK to accept the message describing the consequences if the installation fails.
The Install Windows screen appears.
12. Enter the preferred language and other preferences and click Next. 13. Click Install Now.
14. Type the product key from the product key sticker and click Next.
15. Select Windows Server 2008 Enterprise (Full Installation) and click Next. The Please read the license terms screen appears.
16. Ensure that the customer reads the license terms and selects I accept the license terms.
Note: This step is a customer responsibility. Do not accept the license terms on behalf of the customer. Refer to the local policy for more information.
17. Click Next.
The Which type of installation do you want? screen appears. 18. Select Custom (advanced).
The Where do you want to install Windows? screen appears. 19. Select the proper disk for the installation and click Next.
The default selection for disk location is the setting selected by the factory and must be a minimum of 200 GB.
The progress of the installation is displayed. The system reboots at the end of the process.
20. Remove the Windows Server 2008 DVD from the DVD drive and click OK to accept the message prompting you to change the password before logging in the first time.
21. Perform the following actions:
a. Type the new administrator password in the New password box. b. Type the new administrator password in the Confirm password box. c. Click the right arrow and then click OK to accept the password change. 22. Insert a network cable in one of the available Ethernet ports.
The Set Network Location screen appears.
23. Select Work for the location and click Close when the “Successfully set network settings” message appears.
The Initial Configuration Tasks screen appears. 24. Select Download and install updates.
25. Select Change settings in the upper-left corner of the screen. The Change settings screen appears.
26. Select Never check for updates (not recommended) and click OK. The Windows Update screen appears.
27. Select Check for updates in the upper-left corner of the screen and click Install Now to allow the Windows update software to properly install any software required.
The important updates are now available for installation.
Note: Install only the updates recommended by Microsoft for Windows update and security. Do not install any optional updates that load drivers for tape devices. Click Install Updates, select I accept the license terms, and then click Finish. When “The updates were successfully installed” message appears, click Restart now in the Windows Update screen.
28. Log in with the administrator account credentials.
29. Select Do not show this window at logon in the lower-left corner of the screen and click Close to close the Initial Configuration Tasks screen.
Install the customer-supplied recommended virus protection software on this partition at this time. All partitions must be fortified with virus protection software before the system can be connected to a public or operations LAN.
Configuring the Windows Operating System
To configure the Windows operating system for use with the Virtual Machine for ClearPath MCP software, perform these procedures.
Note: The instructions are based on the standard Start menu setting. If you changed the view to the Classic Start menu setting, adjust the instructions accordingly.
Changing the Video Adapter Driver
Perform the following steps to change the video adapter driver: 1. On the Start menu, right-click Computer and click Manage.
The Server Manager window appears.
2. Expand Diagnostics in the left pane and select Device Manager. 3. Expand Display adapters in the right pane.
4. Right-click Matrox adapter and click Update Driver Software.... The Update Driver Software screen appears.
5. Select the Browse my computer for driver software option.
7. Select Standard VGA Graphics Adapter and click Next.
A message appears confirming that Windows has successfully updated the driver software.
8. Click Close to close the Update Driver Software screen. 9. Click No when you are prompted to restart the system.
10. Under Device Manager, expand Monitors. Ensure that the monitor device is set
to Generic Non-PnP Monitor.
If the monitor device is not set to Generic Non-PnP Monitor, perform the following steps to update the device driver:
a. Under Monitors, right-click Adapter and click Update Driver Software…. The Update Driver Software screen appears.
b. Select the Browse my computer for driver software option.
c. Select Let me pick from a list of device drivers on my computer. d. Select Generic Non-PnP Monitor and click Next.
A message appears confirming that Windows has successfully updated the driver software.
e. Click Close to exit the Update Driver Software screen. f. Click No when you are prompted to restart the system.
Renaming the Administrator Account
Perform the following steps to rename the Administrator account: 1. On the Start menu, right-click Computer and click Manage.
The Server Manager window appears. 2. Expand Configuration in the left pane.
3. Expand Local Users and Groups and double-click Users. 4. Right-click Administrator in the right pane and click Rename.
5. Type a new name of your choice following the naming conventions for your site and press Enter.
6. Close the Server Manager window.
Changing the Partition Computer Name
The preinstalled Windows operating system uses a default computer name. Change the partition computer name by performing the following steps:
1. On the Start menu, right-click Computer and click Manage. The Server Manager window appears.
2. Click the Change System Properties link in the upper-right corner of the Computer Information panel.
The System Properties dialog box appears. 3. Select the Computer Name tab.
4. Click Change.
The Computer Name/Domain Changes dialog box appears.
5. Type the desired name in the Computer name box following the naming conventions for your site and click OK.
6. Click OK when prompted to restart the system. 7. Click Close to close the System Properties dialog box. 8. Click Restart Later when prompted to restart your system.
Note: You are instructed to restart the system later in this section.
Setting Windows Virtual Memory
A Windows paging file is a requirement for MCPvm-based servers. You must comply with the following guidelines when configuring Windows Virtual Memory:
• Do not select the Automatically manage paging file size for all drives option. Manually select a paging file size.
• Configure a single paging file on the boot partition, which is drive C. This is the recommended option. If the paging file is spread across multiple drives, various operations might fail. For example, a Windows kernel memory dump might not complete.
• Calculate the minimum paging file size by adding 256 MB to the total physical memory size in the server. If the Libra Model 450 or the FS1750 server has 24 GB of memory, the minimum paging file size required is 24832 MB (24 x 1024 + 256). If the Libra Model 450 or the FS1750 server has 48 GB of memory, the minimum paging file size required is 49408 MB (48 x 1024 + 256). You can also select a bigger paging file size.
• Ensure that the Initial size and Maximum size values are identical.
• Note that paging file size options, System managed size and No paging file, are not supported on the Libra Model 450 or the FS1750 server.
Perform the following steps to set the Windows Virtual Memory: 1. On the Start menu, right-click Computer and click Manage.
The Server Manager window appears.
2. Click Server Manager (<your computer name>).
3. Click the Change System Properties link in the upper-right corner of the Server Manager panel.
The System Properties dialog box appears. 4. Select the Advanced tab.
5. Click Settings in the Performance box. The Performance Options dialog box appears. 6. Select the Advanced tab.
7. Click Change... in the Virtual memory box. The Virtual Memory dialog box appears.
Caution
Do not select the System managed size or No paging file options. Also, do not specify an Initial size that is different from the value of Maximum size. Selecting any of these unsupported virtual memory settings, for example, while changing from a smaller to a larger page file size, allows Windows to enter a state that causes fatal, unrecoverable I/O errors in the Virtual Machine for ClearPath MCP (VMMCP) software.
8. Clear the Automatically manage paging file size for all drives check box. 9. Select the boot drive. Typically, this is the C drive.
10. Click Custom size.
11. Type one of the following values in the Initial size and Maximum size boxes:
• If the server has 24 GB of physical memory, type 24832 or a greater value.
• If the server has 48 GB of physical memory, type 49408 or a greater value.
Notes:
• You can view the total physical memory by referring to the System Information screen. On the Start menu, point to All Programs,
Accessories,System Tools, and then click System Information.
• If you use a paging file size greater than the minimum, make sure the size you select leaves at least 1024 MB of free space on the boot drive. 12. Click Set to set the virtual memory for the selected drive.
14. Click OK if the following message is displayed:
The changes you have made require you to restart your computer before they can take effect.
15. Click OK to close the Performance Options dialog box. 16. Click OK on the System Properties dialog box.
17. Click Restart Later if you are prompted to restart the system.
Note: You are instructed to restart the system later in this section.
Configuring Windows Update Driver Settings
Install the unsigned drivers by performing the following steps: 1. On the Start menu, right-click Computer and click Manage.
The Server Manager window appears.
2. Click the Change System Properties link in the upper-right corner of the Computer Information panel.
The System Properties dialog box appears.
Note: Ensure that you have selected Server Manager (<your computer name>) in the Server Manager window.
3. Select the Hardware tab.
4. Click Device Installation Settings in the Device Installation Settings box. 5. Select No, let me choose what to do and Never Install driver software
from Windows Update. Click Save Changes. 6. Click OK to close the System Properties dialog box. 7. Click Close to close the Server Manager dialog box.
Installing the USB Image Enabler Device
You must attach the USB Image Enabler device to a USB port on the system. For added security and decreased risk of damage or loss, it is recommended that you attach the USB Image Enabler device to the internal USB port on the system.
However, if required, you can attach the USB Image Enabler device to an external USB port. Refer to “External Installation” for details.
Note: Multiple Image Enabler devices are not supported on the same system. Internal Installation
Perform the following steps to attach the USB Image Enabler device to the internal USB port:
1. Power off the server. 2. Remove the top cover.
3. Note the location (labeled L) of the internal USB port as shown on the Service Information Label (PN P664H) that is affixed on the inside of the top cover.
4. Install the USB Image Enabler device in location L of the internal USB port as shown in the following figure.
Figure 3–1. USB Image Enabler Device 5. Replace the top cover.
6. Power on the server.
7. Press F2 when prompted to enter the system setup screen. 8. Select Integrated Devices from the main screen.
9. Ensure that Internal USB Port is set to ON. 10. Save the changes and allow the system to boot.
11. Click Cancel if the Welcome to the Found New Hardware Wizard dialog box appears.
External Installation
Perform the following steps to attach the USB Image Enabler device to an external USB port:
1. Attach the Image Enabler device to one of the USB ports on the system. The Found New Hardware Wizard dialog box appears.
Installing the Virtual Machine for ClearPath MCP Software
Perform the following steps to install the base release of the Virtual Machine for ClearPath MCP software: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/DVD drive.
The AutoPlay window appears. 3. Click Run Autorun.exe.
4. Click Install Virtual Machine for ClearPath MCP. 5. Click Next on the Install Shield Wizard Welcome screen. 6. Accept the license agreement, and then click Next. 7. Fill out the customer information, and then click Next.
8. Click Next to accept the default location for the destination folder. 9. Click Next to accept the default location for the application data folder. 10. Click Next to accept the default setup type.
11. Click Install.
The files are copied from the CD-ROM to the hard disk.
12. Click Install to load the device driver for the USB Image Enabler device. 13. Click Finish.
14. Click No when asked to restart the system. 15. Click Exit to leave the window.
16. Remove the CD-ROM from the CD/DVD drive. 17. Reboot the server.
18. Log on using an account with Administrator privileges and the appropriate password.
19. Repeat steps 5 through 15 for any Virtual Machine for ClearPath MCP Service Packs or software updates.
20. Install any add-on software ordered with your system.
21. If the USB Image Enabler device was already installed prior to installing the Virtual Machine for ClearPath MCP software, skip this step.
If the USB Image Enabler device was not attached to the system prior to installing the Virtual Machine for ClearPath MCP software, perform the following procedure to install the device at this time:
a. Attach the USB Image Enabler device to the USB port of the server. The Found New Hardware Wizard dialog box appears.
b. Select No, not this time in the Can Windows connect to Windows Update to search for software? group box, and then click Next.
c. Select the Install the software automatically (Recommended) option on the following screen, and then click Next.
The Completing the Found New Hardware Wizard dialog box appears. d. Click Finish.
22. Click No if prompted to restart the system.
Note: You are instructed to restart the system later in this section.
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.
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.
Note: Do not restart the system after the installation. You are instructed to restart the system later in this section.
After you complete the installation, proceed to “Enabling NetBIOS over TCP/IP” if a static IP address is used or if the DHCP server at the site does not provide NetBIOS settings.
Note: Record the MCP host name information during the Network Services software installation, for later use during the host system setup.
Enabling NetBIOS Over TCP/IP
To enable NetBIOS over TCP/IP, complete the following steps:
1. On the Start menu, click Control Panel, and then click View Network status and tasks under Network and Internet.
2. Click Change adapter settings.
The Network Connections window appears, displaying multiple adapter
connections. Refer to the adapter.txt file for more information about the adapters displayed. The adapter.txt file is located at Program Files\Unisys\Nxnet\.
3. Right-click the Local Area Connection icon that is used for the shared adapter, and then click Properties.
The <Adapter Identifier> Properties dialog box appears.
4. Select Internet Protocol Version (TCP/IPv4) and then click Properties. The Internet Protocol Version (TCP/IPv4) Properties dialog box appears. 5. Click Advanced.
6. Click Enable NetBIOS over TCP/IP on the WINS tab.
7. Click OK to close the Advanced TCP/IP Settings and Internet Protocol Version 4 (TCP/IPv4) Properties dialog boxes.
8. Click Close on the <Adapter Identifier> Properties dialog box. 9. Repeat steps 2 through 8 on any additional shared adapters.
10. Close the Network Connections and the Network and Sharing Center windows.
Configuring the Operating System for Accessing MCP Shares
Network Services software enables you to connect to the MCP shares from the Windows environment. However, the default LAN Manager Authentication Level in the local security policy for Windows Server 2008 R2 Enterprise x64 with SP1 might cause attempts to map a share on the MCP system to fail.
Complete the following steps to resolve this problem:
1. On the Start menu, click Control Panel, click System and Security, and then double-click Administrative Tools.
2. Double-click Local Security Policy in the right pane of the Administrative Tools window.
The Local Security Policy window appears.
3. In the left pane, expand Local Policies and select Security Options. 4. In the right pane, right-click Network security: LAN Manager
authentication level and click Properties. The Network Security dialog box appears.
5. Select Send LM and NTLM responses from the list. 6. Click OK.
7. In the right pane, right-click Network security: Minimum session security for NTLM SSP based client and click Properties.
The Network Security dialog box appears
8. Ensure that all are options are unchecked, click Apply, and then click OK. 9. In the right pane, right-click Network security: Minimum session security
for NTLM SSP based servers and click Properties. The Network Security dialog box appears
10. Ensure that all are options are unchecked, click Apply, and then click OK. 11. Close all of the windows.
12. Start Internet Explorer.
13. On the Tools menu, click Internet Options. The Internet Options dialog box appears. 14. Select the Security tab.
15. Select the Internet zone, and then click Custom Level. The Security Settings dialog box appears.
16. Under the Miscellaneous settings, disable Use Pop-up Blocker. 17. Under the Scripting settings, enable Active scripting.
18. Click OK to save the changed settings and close the Security Settings dialog box. Click Yes to confirm that you want to save the settings.
19. Click OK on the Internet Options dialog box.
Creating the MCP Logical Disk Using the MCP Quick Install
DVD
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 ClearPath Enterprise Server Virtual Machine for ClearPath MCP Quick Install DVD 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 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 select from them. The program informs you if it does not find a suitable drive for the installation of 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 ClearPath Enterprise Server Virtual Machine for ClearPath MCP Quick Install DVD in the CD/DVD drive.
The Autoplay window appears. 2. Click Run Quick InstallMCP.exe. 3. Accept the license agreement.
The Quick Install program searches your system for suitable drives for your MCP files.
4. When prompted, select the drive on which to install the MCP software. It is recommended that you select drive D.
Note: The Quick Install program takes about 15 minutes to load the MCP files, eliminating the need to perform the configuration tasks required during a normal cold-start.
The MCP Quick Install Successful dialog box appears informing you that MCP has been successfully installed and requesting that you add DISK000.asd to the PCD.
5. Click OK.
The Quick Install program is now complete. 6. Remove the DVD from the CD/DVD drive. 7. Restart the system.
8. After the system restarts, log on using an account with Administrator privileges. A Console for MCP configuration message is displayed.
9. Click OK.
Configuring and Halt/Loading MCP
To configure and halt/load the MCP, perform the following steps: 1. Double-click the Console for MCP icon.
Note: If the Console for MCP application initiates before the Console for MCP Connection Service is running, a message is displayed notifying users that the Console for MCP Connection Service is not currently running and the Console for MCP application is terminating. This error message often appears if the Console for MCP application is placed in the Windows Startup group. If you encounter this error message, wait a few minutes and then restart the Console for MCP application.
2. Click Go to System Editor to create a new PCD file and click OK on the Console for MCP Configuration dialog box.
3. Click MCP Disk Management on the Tools menu. 4. Select Logical Disk Operations, and then click Next.
The Logical Disk File Management window appears. 5. Select Security from the toolbar.
6. If any logical disk files lack proper security, select them and click Apply. Click OK if the message “All Logical Disk files have proper security at this time” appears. 7. Close the Logical Disk File Management window.
8. Resize the logical disk as follows:
Note: The Quick Install program allocates 3000 megabytes (MB) of logical disk space for the halt/load disk. If your system does not require more space for the halt/load disk, proceed to step 9.
a. From the MCP Disk Management window, select Logical Disk Operations and click Resize.
The Resize Logical Disk File window appears. b. Select D:\DISK000.ASD.
c. In the Capacity field, update the amount of memory required for the halt/load disk for your system.
Note: The capacity ranges below the Capacity field are given in MB. d. Select Resize.
e. Click Close.
9. Close the MCP Disk Management window.
10. Click Build to create a new PCD using the Auto Build feature.
11. Verify that the ICP4 210 is present if there is 1 NP instance. For up to six NP instances, verify that ICP4 211, ICP4 212, ICP4 213, ICP4 214, and ICP4 215 are also present.
For assistance, refer to the Virtual Machine for ClearPath MCP Administrative Console Help.
12. Save the new PCD and close the System Editor window. A message appears asking if you want to select a PCD. 13. Click Yes.
The Partition Properties window appears. 14. Perform the following steps:
a. Click Select next to the PCD file. The Select PCD File dialog box appears.
b. Select the PCD file you have just created, and then click OK. c. Select Unit 1 in the list next to the Halt/Load ODT.
d. Select Unit 500 in the list next to the Halt/Load disk.
e. By default, the MCP Memory Size box contains the maximum value calculated by the VMMCP software based on the total amount of physical memory. This value can be modified later as needed.
Refer to the Memory Configuration Guidelines in the Virtual Machine for ClearPath MCP Administrative Console Help for information about memory restrictions.
f. By default, the Enable Virtual Machine Caching option is selected. This setting can be modified later as needed.
g. By default, the Use Virtual Machine Caching option is selected. This setting can be modified later as needed.
h. Click OK.
15. If the MCP Memory Size option, Enable Virtual Machine Caching option, or
the Use Windows Caching option is changed in the previous step, a Console
for MCP Message appears prompting you to shut down MCP Control. Complete the following steps:
a. Click OK.
b. Click Init MCP to initialize MCP Control.
16. On the MCP menu of the Console for MCP window, click Run System Loader. 17. Start the ODT window by double-clicking the ODT Unit 1 icon on the desktop. 18. Type RECONFIGURE GROUP AS DEFAULT in the ODT1 window and transmit
(press the plus (+) key on the numeric key pad). Wait until the System/Loader reconfigures. 19. Type STOP in the ODT1 window and transmit.
This action terminates the loader and displays the EOJ message. The MCP initializes and displays the MCP ADM screen.
Disk initialization stops awaiting user input.
20. Type HN=<MCP host name> in the ODT1 window and transmit.
21. On the ODT 1 window, the STARTSYSTEM job is in a waiting status. This is often mix# 5 or 6. Use the ODT command HLUNIT to determine the halt/load disk number, which is typically 500.
22. Type <mix#> IL PK <nnn> in the ODT1 window and transmit. The system fully initializes.
23. Set the MCP date and time.
24. Type ??PHL in the ODT1 window and transmit.
25. Follow the IC cover letter instructions to load any applicable ICs.
26. Load separately purchased software according to instructions in the ClearPath MCP software documents.
Adding Trusted Sites for the MCP Server
Perform the following steps to add trusted sites for the MCP server: 1. Open Internet Explorer.
2. From the Tools menu, select Internet Options. The Internet Options dialog box appears.
3. Select the Security tab.
4. Select Trusted sites and click Sites.
5. Type \\<MCP hostname> in the Add this website to the zone: box. 6. Ensure that the Require server verification (https:) for all sites in this
zone check box is clear.
7. Click Add and then click Close. 8. Click Custom Level.
The Security Settings dialog box appears.
10. Click OK to close the Security Settings dialog box. 11. Close the Internet Options dialog box.
12. Close Internet Explorer.
Connecting the TCP/IP Network Drive
To enable the virtual LAN, perform the following ping and drive connection procedures.
When performing tasks related to Network Services, refer to the Network Services Implementation Guide, which 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 steps: 1. After the system recovers from the previous halt/load, type P NP and transmit
from the ODT1 window to ensure that NP210 is active and communicating. 2. On the command prompt in Windows, type ping <MCP host name> and then
press Enter.
You can also ping the IP address, which is 192.168.16.1.
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 Section 7, “Troubleshooting Information,” to solve the problem, and then go to step 4.
4. From Windows Explorer, click Map Network Drive on the Tools menu. 5. Perform the following steps:
a. Type \\<MCP host name\Installs in the Folder box.
b. Ensure that the Reconnect at logon check box is not selected. c. Select Connect using a different name.
d. Click OK.
6. Enter the appropriate user name and password when prompted. (The factory uses the user name Administrator and password ADMINISTRATOR.)
7. Click OK to close the Connect As... dialog box.
8. Click Finish to close the Map Network Drive dialog box.
Setting Up Windows Tools for ClearPath MCP
Refer to the ClearPath Enterprise Servers MCP Implementation Guide for the steps to set up the Windows tools for ClearPath MCP.
It is recommended that you clear the check boxes for the following products during the installation.
• XVision Fonts
This is not relevant to virtual machine systems.
• Clearpath MCP Interface to Microsoft’s Transaction Integrator An X64 version is not available.
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.
Configuring the Optional Uninterruptible Power Supply (UPS)
If your system has an optional UPS, you can configure it to shut down the system in an orderly manner in the event of a site power problem. Refer to the instructions provided with the UPS to set up and configure this optional capability.
Configuring Fibre Channel and SCSI Connections
To attach external peripheral devices to the server, refer to Section 4, “Configuring External Storage Subsystems.”
Subsystems
This section tells the Unisys service representative how to set up and configure external tape and disk storage subsystems.
Peripheral qualification is an ongoing activity spanning across the life cycle of a server. Therefore, additional storage subsystems might become available after the initial release of the server. Information about such storage subsystems is provided through a Service Product Information (SPI) publication.
This section does not present support information about specific peripherals. Information about qualified peripheral devices is available at the Unisys Product Support Web site:
http://support.unisys.com/framework/login.aspx
Overview
Configuring external tape and disk storage subsystems involves setting up the Host Bus Adapters (HBA), storage subsystems, host drivers, and multipath solutions.
Host Bus Adapter Configuration
The Libra Model 450 and FS1750 servers support the following adapters for disk and tape devices at the initial release:
• Fibre Channel HBA
• SCSI HBA
Check the Unisys Product Support Web site for the latest updates of the qualified adapters and their BIOS, firmware, and driver levels.
Fibre Channel HBA
Emulex 4 GB and 8 GB Fibre Channel HBAs are qualified for connecting Fibre Channel disk arrays and tape drives to the Libra Model 450 and FS1750 servers.
The AutoMap feature of the Emulex driver, which assigns SCSI IDs to detected Fibre Channel targets, is enabled by default. If you are configuring Virtual Sector Size (VSS) disks, using JBOD disk storage or Fibre Channel tape drives, you must disable this
feature and use persistent binding described later in this section. If you are using only MCP Logical Disks, disabling AutoMap and using persistent binding is recommended but not mandatory.
When AutoMap is disabled, devices connected to the server are not automatically presented to the underlying Windows operating system until persistent binding is defined. Using persistent binding ensures that the same SCSI IDs are assigned to the disk and tape targets, called controllers, across Windows reboot and possible Loop Initialization Procedures (LIP). This ensures that the configuration defined in your Peripheral Configuration Diagram (PCD) remains unaffected by Windows reboots or LIPs.
Configuring Persistent Binding
Persistent binding can only be configured after the storage system is connected to the Libra Model 450 or the FS1750 server. The HBAnyware or OCManager utility must first discover the storage targets before you can assign a SCSI ID to it. A SCSI ID in the context of persistent binding is a SCSI bus and target pair. A storage target can be a storage controller of a RAID array or a Virtual Tape Library (VTL) with many LUNs behind it. It can also be a JBOD disk or single tape drive with only one logical unit number (LUN). Perform the following steps to configure persistent binding:
1. Make sure the storage system is connected to the HBA, either directly or through a storage area network (SAN) switch.
2. Click Start, point to All Programs, Emulex, and then click HBAnyware or OCManager.
The HBAnyware or OCManager window appears.
A list of all the HBAs discovered in the system is displayed in the left pane in a tree view. When you select an HBA port in the left pane, its parameters and properties are displayed in the right pane under different property tabs. When you expand the tree for an HBA port, its connected targets and LUNs are listed. An HBA port that is not connected to any storage target is shown with a red X icon. 3. Select an HBA port from the left pane that is connected to storage targets and
then click the Driver Parameters tab in the right pane.
4. Click AutoMap from the Adapter Parameter list and then type 0 in the Value field under Modify Adapter Parameter.
5. With the same HBA port selected, select the Target Mapping tab. All the targets are displayed.
6. Under Current Settings, ensure that the Active Bind Type is WWPN. This is the default binding type and must not be changed. AutoMap must show Disabled because it has been disabled in the Driver Parameter tab.
Note: Always use the Driver Parameter tab to disable AutoMap. Do not use the Change Settings button to change the AutoMap setting.
7. To add persistent binding to the targets, select a target from the Persistent Binding Configuration table and click Add Binding.
8. Leave WWPN as the Bind Type Selection. Select zero as the Bus ID and then select a Target ID that has not been assigned.
Note: Always select zero as your Bus ID. Other Bus ID values have not been tested in the Libra Model 450 and FS1750 server environments.
9. Repeat step 8 for all the targets of the HBA port you selected in step 3. 10. Continue to add persistent binding for other HBA ports in the system.
Caution
If you have a dual-path JBOD configuration, it is imperative that you bind the targets on both paths with the same SCSI ID. Failure to do so can result in data corruption.
Notes:
• More information about the HBAnyware or OCManager utility can be found in the HBAnyware or OCManager Utility User Manual. You can download this document from the EmulexWeb site at www.emulex.com. You can also access the online help information from the HBAnyware or OCManager utility.
• You can add persistent binding from the HBAnyware or OCManager utility one at a time. When there are multiple JBOD disks in the system and each disk is a target that needs binding defined, it can be a tedious and time-consuming task. HBAnyware or OCManager provides a command-line interface, hbacmd, for scripting these operations in a batch file. Syntax for this interface can be found in the HBAnyware or OCManager Utility User Manual.
SCSI HBA
LSI Logic SCSI HBA is used to connect SCSI tape drives to the Libra Model 450 or FS1750 servers. SCSI disk arrays are not supported on Libra Model 450 and FS1750. The LSI HBA can be connected to a supported low voltage differential (LVD) drive.
Configuring LSI Logic BIOS for Older Tape Drives
You need to reduce the LSI HBA bus speed and data width for some older tape drives, such as ALP 440. Otherwise, data might be lost in transfer.
Perform the following steps to set the proper bus speed and data width: 1. Power on or restart the Libra Model 450 or the FS1750 server.
2. Note the messages displayed as the BIOS for each adapter is processed. When you see the following banner from LSI Logic, press CTRL-C to enter the configuration utility:
LSI Logic Corp. MPT BIOS
Press CTRL-C to run the Configuration Utility
