unisys ClearPath Enterprise Servers Virtual Machine for ClearPath MCP Installation Guide Virtual Machine for ClearPath MCP Version 10.0, SP2 September 2011 3843 4072 001
NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information described herein is only furnished pursuant and subject to the terms and conditions of a duly executed agreement to purchase or lease equipment or to license software. The only warranties made by Unisys, if any, with respect to the products described in this document are set forth in such agreement. Unisys cannot accept any financial or other responsibility that may be the result of your use of the information in this document or software material, including direct, special, or consequential damages. You should be very careful to ensure that the use of this information and/or software material complies with the laws, rules, and regulations of the jurisdictions with respect to which it is used. The information contained herein is subject to change without notice. Revisions may be issued to advise of such changes and/or additions. Notice to 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.
Contents 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 MCP Shares... 3 17 3843 4072 001 iii
Contents 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 Backing Up Data in the Windows Environment... 6 1 iv 3843 4072 001
Contents 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 3843 4072 001 v
Contents vi 3843 4072 001
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 3843 4072 001 vii
Figures viii 3843 4072 001
Tables 3 1. BIOS Settings for the Libra 450 Platform... 3 4 3843 4072 001 ix
Tables x 3843 4072 001
Section 1 Introduction This document is the primary source of information for the setup and configuration of the Virtual Machine for ClearPath MCP enterprise server. Documentation Updates Audience 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. 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 3843 4072 001 1 1
Introduction 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 CMP hardware concepts 1 2 3843 4072 001
Section 2 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 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 hotpluggable 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 integrated, serial-attached SCSI RAID controller for internal SAS disk drives 3843 4072 001 2 1
Overview 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 Windows 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 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 2 2 3843 4072 001
Overview 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 3843 4072 001 2 3
Overview 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. 2 4 3843 4072 001
Overview 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 3843 4072 001 2 5
Overview 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. 2 6 3843 4072 001
Section 3 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. 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 thirdparty 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. When resolving installation problems, you need the following information: 3843 4072 001 3 1
Setting Up the Server 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 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 Wrong 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. 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. 3 2 3843 4072 001
Setting Up the Server 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 OEM BIOS, version 1.2.3 or later 3843 4072 001 3 3
Setting Up the Server 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. 3 4 3843 4072 001
Setting Up the Server Table 3 1. BIOS Settings for the Libra 450 Platform Category Setting Description ClearPath Setting Memory Operating Mode Optimizer Mode Node Interleaving Enabled Processor Logical Processor (threading) Disabled Note: This option can be enabled only on servers with two sockets and 48 GB of physical memory. Virtualization Technology Adjacent Cache Line Prefetch Hardware Prefetcher Execute Disable Number of Cores per Processor Turbo Mode C1E Processor C States Disabled Enabled Enabled Enabled All Disabled Disabled 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 Internal USB Port Embedded NIC1 and NIC2 Embedded Gb NIC1 Embedded Gb NIC2 Embedded NIC3 and NIC4 Embedded Gb NIC3 Embedded Gb NIC4 OS Watchdog Timer I/OAT DMA Engine SR-IOV Global Enable All On Enabled Enabled with PXE Enabled Enabled Enabled Enabled Disabled Disabled Disable 3843 4072 001 3 5
Setting Up the Server Table 3 1. BIOS Settings for the Libra 450 Platform Category Setting Description ClearPath Setting Power Management CPU Power and Performance Management Fans Power and Performance Management Memory Power and Performance System Security Power Button Enabled NMI Button AC Power Recovery AC Power Recovery Delay Maximum Performance Maximum Performance Maximum Performance Note: This option is a user preference. It is recommended if the user is required to initiate an NMI dump. Last 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. 8. Set a user account and password and press Enter. 3 6 3843 4072 001
Setting Up the Server 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. 3843 4072 001 3 7
Setting Up the Server 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. The Windows Update screen appears. 3 8 3843 4072 001
Setting Up the Server 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. 6. Select Let me pick from a list of device drivers on my computer. 3843 4072 001 3 9
Setting Up the Server 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. 7. Log off and then log in with the new administrator account. 3 10 3843 4072 001
Setting Up the Server 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. 3843 4072 001 3 11
Setting Up the 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. 13. Click OK to close the Virtual Memory dialog box. 3 12 3843 4072 001
Setting Up the Server 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. 3843 4072 001 3 13
Setting Up the Server 4. Install the USB Image Enabler device in location L of the internal USB port as shown in the following figure. 5. Replace the top cover. 6. Power on the server. Figure 3 1. USB Image Enabler Device 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. 2. Click Cancel. 3 14 3843 4072 001
Setting Up the Server 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. 3843 4072 001 3 15
Setting Up the Server 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. The Advanced TCP/IP Settings dialog box appears. 3 16 3843 4072 001
Setting Up the Server 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. 3843 4072 001 3 17
Setting Up the Server 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. 3 18 3843 4072 001
Setting Up the Server 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. 3843 4072 001 3 19
Setting Up the Server 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. The changes are applied and MCP Control is shut down. 3 20 3843 4072 001
Setting Up the Server 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. 9. Ensure that Use Pop-up Blocker under Miscellaneous is set to Disable. 3843 4072 001 3 21
Setting Up the Server 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. 3 22 3843 4072 001
Setting Up the Server 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. 3843 4072 001 3 23
Setting Up the Server 3 24 3843 4072 001
Section 4 Configuring External Storage Subsystems Overview 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 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 3843 4072 001 4 1
Configuring External Storage Subsystems 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. The Add Persistent Binding dialog box appears. 4 2 3843 4072 001
Configuring External Storage Subsystems 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: SCSI HBA 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. 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 The LSI Logic MPT SCSI Setup Utility screen appears with your HBA highlighted. 3843 4072 001 4 3
Configuring External Storage Subsystems 3. Select the HBA and press Enter. 4. The message Scanning for devices appears, followed by the Adapter Properties screen. 5. Select <Device Properties> and press Enter. The Device Properties screen appears listing the tape drives in the order of their SCSI ID. For each tape drive, settings including bus speed (MT/Sec) and data width (Data Width) are displayed. 6. Select your tape drive and change MT/Sec to 10 and Data Width to 8. Repeat this step for all the tape drives in the list. 7. Press Esc to exit the Device Properties screen and then press Esc again. A dialog box containing the message Adapter property and/or device property changes have been made appears. 8. Select <Save changes then exit this menu> and press Enter. The LSI Logic MPT SCSI Setup Utility screen appears. 9. Press Esc. A message dialog box appears requesting confirmation of your exit request. 10. Select <Exit the Configuration Utility> and press Enter. The system restarts. Tape Subsystems Tape drives on the Libra Model 450 or FS1750 systems are reserved exclusively for MCP use. They are provided to the underlying Windows environment as a Unisys proprietary class of device named VMMCPDevices and not the Windows Tape drives. Tape class drivers that are packaged in Windows Server 2008 are disabled by the VMMCP software. You must not install any tape drivers from the vendor or through Windows updates. Other vendor s Windows-based tools are also not supported to run on the Libra 450 and FS1750 servers. The appropriate driver for VMMCPDevices is called AcDevice. It is packaged in the VMMCP software and copied to the system by the VMMCP software installation program. However, you must install the AcDevice driver manually after a tape drive is connected to the system. Procedures for managing the AcDevice driver are provided later in this section. Mixing tape devices and disk devices on the same Fibre Channel HBA port is not recommended and not supported. Multiple tape drives can be connected on the same HBA port. The following lists the maximum number of tape drives supported: A maximum of two tape drives of the same type on the same SCSI port. A maximum of five Fibre Channel tape drives can be connected to the same Fibre Channel HBA port. One Virtual Tape Library (VTL) library can be connected to the same Fibre Channel HBA port. You can configure one VTL unit to have multiple virtual tape libraries. 4 4 3843 4072 001
Configuring External Storage Subsystems There is no multipath I/O supported for tape drives. Sharing a tape drive between multiple MCP hosts is also not supported on Libra Model 450 and FS1750 systems. Installing and Removing the VMMCPDevices Class Driver AcDevice.sys The following files make up the AcDevice driver package. These files are distributed and copied to the MCP partition as part of the VMMCP software. AcDevice.sys AcDevice.inf AcDevice.cat AcDInstl.exe AcDevRem.exe Installing and Updating AcDevice.sys Although the AcDevice files are copied to the MCP partition, the driver is not installed until a tape drive is connected to the server and you execute the AcDevice installation program, AcDInstl.exe. When AcDInstl.exe is run, it installs AcDevice.sys for every supported tape drive connected to the server. After the AcDevice driver is installed on the system, the inf file definition allows Windows to automatically recognize any subsequent tape drives you add to the system. You do not need to run the AcDInstl.exe installation program every time you add a tape drive. Perform the following steps to install the AcDevice.sys driver using the AcDInstl.exe installation program: 1. Ensure your tape drive is powered on and connected to the system. 2. On the Start menu, right-click Computer, and then click Manage. The Server Manager window appears. 3. Expand Diagnostics from the left pane of the window and select Device Manager. Your tape drive must be listed under the Other devices category with a question mark icon. 4. Start Windows Explorer. 5. Navigate to the C:\Program Files\Unisys\Virtual Machine for ClearPath MCP\Devices folder. 6. Double-click AcDInstl.exe. A command prompt window appears and the installation begins. This might take a few minutes as the program processes each device in the AcDevice.inf file. The message Press any key to exit is displayed when the processing is complete. You can check whether the driver is installed successfully for your tape device by scrolling back the screen and checking the status displayed. 3843 4072 001 4 5
Configuring External Storage Subsystems 7. Return to Device Manager. It is updated to show a new category: VMMCPDevices. 8. Expand the VMMCPDevices to view your tape drive. Any future updates to the AcDevice driver are distributed and released through VMMCP software updates. Follow steps 1 through 8 to update the driver after the VMMCP software update is installed. Removing AcDevice.sys Removing the AcDevice driver includes removing the driver files as well as the registry settings for it. This is not expected to be a typical operation. Do not remove this driver from the Libra Model 450 or the FS1750 server unless instructed by your Unisys service representative for troubleshooting purposes only. Note: Without the AcDevice driver installed, the console for MCP and the MCP environment do not recognize the tape drive. Perform the following steps to remove the AcDevice driver from your system: 1. Make sure your tape drives are free from the MCP and are powered off. 2. On the Start menu, right-click Computer, and then click Manage. The Server Manager window appears. 3. Expand Diagnostics in the left pane and select Device Manager. Your tape drive is listed under the VMMCPDevices category. 4. Right-click each tape drive listed and select Uninstall. The Device Manager window refreshes and the list is empty. 5. Start Windows Explorer. 6. Navigate to the C:\Program Files\Unisys\Virtual Machine for ClearPath MCP\Devices folder. 7. Double-click AcDevRem.exe. A command prompt window appears and the program displays a caution with instructions. Repeat steps 1 through 4, if you have not already done so. 8. Enter YES in uppercase letters to continue. A status message appears when the program completes. 9. Press any key to exit the command prompt window. 10. Reboot Windows. The AcDevRem program does not instruct you to reboot but you must reboot Windows to complete the removal process. 11. After the system restarts, navigate to the Device Manager. The tape drive is listed under the Other devices category with the question mark icon. 4 6 3843 4072 001
Configuring External Storage Subsystems Powering Off a Tape Subsystem If you need to power off a tape subsystem for energy conservation or maintenance purposes, you must free the tape drives from the MCP operating system before taking any action. If you fail to free the tape drives before powering them down, an outstanding handle remains in the underlying Windows operating system environment, which causes problems when you power on the tape subsystem subsequently. Perform the following steps to power off a tape subsystem: 1. Type PER MT in the MCP ODT window to ensure that no job is currently using the tape that you want to free. The following examples show sample MT status messages: Example of MT 81 in use: ---------------------------------- MT STATUS --------------------------- 81*L [LTO3 ] (7513) LTO C #1 1:0 <09/18/2009 TAPE/FILE000 The presence of a job number (in this case 7513) is evidence that the tape is in use. Example of MT 81 not in use: ---------------------------------- MT STATUS ------------------------ 81*L [LTO3 ] LTO C S C R A T C H 2. Type FREE MT <MT unit number> in the MCP ODT window to free the tape drive. For example: FREE MT 81 3. Check the MCP ODT display messages to verify that the MCP operating system has freed the tape drive. For example: ---Mix-Time--------------------- 21 MESSAGES ----------------------- 7558 11:21 SUCCESSFULLY FREED MT81 4. Power off the tape drive. Disk Subsystems Disk storage options are discussed in this section. This information is provided to assist you in determining the appropriate configuration choice for your disk storage susbsystem. MCP Disk Formats The Libra Model 450 or the FS1750 server supports the same disk formats used by the MCP file system as the MCPvm systems. The formats reflect three different ways of mapping the native 180 bytes per sector of data from the original MCP disks into 512 byte sectors on currently available disk drives: VSS-1, VSS-2, and MCP Logical Disk. 3843 4072 001 4 7
Configuring External Storage Subsystems VSS Disks Virtual Sector Size (VSS) formats, VSS-1 and VSS-2, were originally developed for use by the native MCP product line. VSS disks created on any MCP system can be used on the Libra Model 450 and FS1750 servers. VSS disks are managed by the MCP and perform an overlay of 180 byte data into 512 byte sectors on a disk volume. VSS-1 attempts to optimize the overlay in terms of disk utilization by filling the disk with consecutive 180-byte sectors. As a result, each 512-byte physical disk sector contains parts (or all) of three or four 180-byte sectors; the first, last, or both of these 180-byte sectors overlap into adjacent 512-byte sectors. While this strategy makes good use of the available disk capacity, it does so at the cost of write performance. This happens because most disk writes affect only part of the starting and ending 512- byte physical disk sectors. As a result, these sectors must be read before the write is done so that the remainder of the data in the starting and ending 512-byte sectors can be preserved. A slightly different, but similar strategy is used by VSS-2. In VSS-2 disk volumes, only two 180-byte areas are placed in each 512-byte sector of the disk. The remainder of the sector is left unused. Write performance of VSS-2 is superior to VSS-1 because most disk writes are of an even number of 180-byte sectors and do not require a read before write like VSS-1. The cost of this performance improvement is that approximately thirty percent of the disk space is unusable. This can be a good tradeoff in today's era of large and relatively inexpensive disks if write performance is important. VSS-1 disks offer better read performance than VSS-2 disks because less data has to be transferred from the disk to system memory on a read operation. Each 512-byte VSS-2 sector only contains 360 bytes of user data, and so a greater number of 512- byte disk sectors must be read when the disk is formatted as VSS-2 instead of VSS-1. Because of these performance differences, some customers use a mixture of VSS-1 and VSS-2 disks, choosing which format is optimal for each disk based on their expected usage. VSS disks on the Libra Model 450 or FS1750 server are LUNs that are made exclusively for MCP use. Specialized filter drivers in the VMMCP software remove these disk units from Windows by blocking Windows access. Configuring a raw disk as VSS requires you to first mark the disk for MCP use by using the VSS Disk Acquire procedure in the System Editor MCP Disk Management tool. The VSS Disk Acquire procedure requires a reboot of the server to complete. VSS disks are only supported on external disk storage subsystems connected through a Fibre Channel HBA. 4 8 3843 4072 001
Configuring External Storage Subsystems Caution Without the blocking mechanism from VMMCP filter drivers, VSS disks are exposed to Windows and data can potentially be erased by unintentional operations. Do not leave the VMMCP software uninstalled on the Libra Model 450 or the FS1750 server for prolonged periods of time. Each VSS disk has a SCSI address assigned in Windows. This SCSI address represents a real connection from the HBA to the disk unit and comprises of port, bus, target, and LUN. In the MCP, SCSI address consists of only bus, target, and LUN. When presenting a VSS disk in the PCD, Windows port and bus IDs are combined to form a unique MCP SCSI bus ID. Windows target and LUN IDs remain unchanged when mapping the disk to the MCP configuration. When constructing the device tree for a VSS disk in the PCD using the MCP terminology, channel, control, and unit, the unique MCP SCSI bus ID is assigned to the SCSI ID property of the channel; the target ID is assigned to the SCSI ID property of the control; and the LUN ID of the disk is assigned as the Unit Position property of the unit. When the MCP issues an I/O to a unit, VMMCP I/O modules use the SCSI address information to access the device object for this unit and perform I/O operations to it. MCP Logical Disk MCP Logical Disk was a disk strategy originally developed for the MCPvm systems. The technology involves using the native Windows NT File System (NTFS) as the base file system and creating pseudo MCP volumes that actually exist as large files under NTFS. Such files have a file extension of.asd, and are typically found at the root level of an NTFS partition. For example, C:\DISK000.ASD. The MCP Logical Disks, often referred to as Logical Disks, cannot be created on non- NTFS partitions. They also cannot be used on remote, network-connected drives. Reads and writes to disk in the MCP are converted into file reads and writes at the emulation level in this Windows file. MCP Logical Disks are opened as write through, so no write caching takes place. This ensures a higher level of reliability at the cost of write performance. It protects the user from losing a write when a write logically completes and the system faults or powers off before the physical write to disk can take place. MCP Logical Disks might perform better, the same, or worse than VSS disks, depending on a number of factors, including: Your application data access patterns to the disks. Whether Windows caching is enabled for Logical Disks and how much memory Windows has available for this cache. Caching is discussed later in this section. Whether you have enabled the Virtual Machine caching feature for VSS disks and Logical Disks, and how much memory is available for use by this cache. Your storage subsystems. 3843 4072 001 4 9
Configuring External Storage Subsystems Disk Caching The following suggestions might help you optimize the performance of Logical Disks: Logical Disks in a JBOD configuration Create only one Logical Disk file per physical disk device. This configuration optimizes the caching times and the seek times of the drives. Logical Disks in a RAID array Put as many smaller Logical Disks on each disk partition as possible. This allows a maximum number of simultaneous I/O to each disk. Washing disks before use Disk washing is implemented in Windows to satisfy a Microsoft C2 requirement for security. C2 security requires that before any application can access a disk data block that was previously freed by another application, the data block in question must be explicitly overwritten with all zeros to destroy previous data before the new application can access the block. Failure to wash the disks before use causes the washing process to occur gradually during standard I/O operations. This slows down the I/O and can cause I/O timeouts. MCP Logical Disks do not have a SCSI address because they are files. Therefore, a SCSI address is fabricated for a Logical Disk when a device tree is constructed in the PCD. The MCP SCSI bus ID has a value starting from 1000. The target ID and the LUN ID both start with zero. The fabricated SCSI address for the Logical Disks is only for adhering to the PCD format and is not used when accessing the disk. Logical Disks are accessed by their file names. VMMCP software provides disk read caching algorithms, called Virtual Machine caching, for VSS disks and MCP Logical Disks. Virtual Machine caching is the only caching option for VSS disks and it is enabled by default. MCP Logical Disks can use either Windows caching or Virtual Machine caching. By default, Virtual Machine caching is enabled for Logical Disks. The caching capabilities can help system performance. Modern disk subsystems include caching within the disk subsystems themselves, which reduces the performance potential for these caches. Caching usually helps performance when there are many reads to data that has recently been accessed. Some form of caching might help write performance on both VSS-1 and Logical Disks by sometimes avoiding the necessity of doing a physical disk read before write, as discussed for VSS-1 disks. Caching might not benefit as much when doing large random accesses to disk or trying to achieve very high I/O throughput. Virtual Machine caching works as follows: Caching Memory Allocation The amount of memory for Virtual Machine caching is allocated dynamically from physical memory on need basis. You do not have to compute the amount of cache memory to allocate based on the number of drives. This allows the system to progressively improve disk read performance as more memory is allocated for 4 10 3843 4072 001
Configuring External Storage Subsystems caching. Memory allocations continue to occur dynamically until doing so reduces the physical available memory below a certain operating threshold. This threshold is called the caching fence. Dynamic memory allocation allows the Virtual Machine caching algorithm to find the optimal amount of memory to use for disk caching operations. Dynamic Sharing Among CMUs The Virtual Machine caching algorithm gives more caching memory to the channel manager unit (CMU) with the greatest I/O activity. This yields an overall system performance improvement for VSS disk reads. In many cases, it also improves the performance of write commands to VSS disks, because write commands in general are frequently preceded by one or more reads that are stored in cache. Each CMU process can occupy a maximum memory of 10 GB. Most of the memory is used for the cache. The memory size of the CMU process can be monitored using Windows Task Manager. Memory usage of a process is displayed in the Mem Usage column under the Process tab. Caching Fence The caching fence is the amount of memory that the Virtual Machine caching algorithm reserves for Windows usage. When the caching size reaches the fence, its algorithm starts releasing the less used cache back to Windows. If the algorithm determines that Windows requires memory even before reaching the fence, it attempts to release some memory for Windows use. This can result in a condition where the caching algorithm tries to release memory for Windows but Windows does not have sufficient memory to execute the release code. When this happens, MCP I/O performance can be severely impacted and might even become completely unpredictable. You can follow the suggestions discussed in Disk Caching and Memory Resource Considerations to remedy the situation. The value of the caching fence is set at a fixed value of 3072 MB when the VMMCP software is installed, regardless of the physical memory size or the MCP memory size. Virtual Machine Caching versus Windows Caching for MCP Logical Disks MCP Logical Disks are Windows files. This implementation allows Windows to use its own disk caching algorithm for improved I/O performance. The Windows disk caching algorithm is optimized for Read Ahead type of operations. If the MCP issues read operations in a forward sequence, then the Windows algorithm works fine. However, if the MCP issues read operations in a reverse sequence, for example, starting from the back of a pack and moving in reverse, then the performance of Windows disk caching is poor. Virtual Machine Caching is offered as an alternative to Windows caching for Logical Disks. The Virtual Machine Caching algorithm is not based on Read Ahead type of operations. For forward reads, Virtual Machine Caching performs comparable to Windows caching. However, for reverse reads, Virtual Machine Caching performs better than Windows caching due to its faster and more efficient use of memory. 3843 4072 001 4 11
Configuring External Storage Subsystems Disk Caching and Memory Resource Considerations Virtual Machine caching and Windows caching uses Windows memory resources and can contribute to memory contention and degraded system performance when the memory is over committed. This might occur when an I/O intensive system is configured with a maximum of MCP memory and a large number of disk devices, such as VSS and Logical Disks. In this case, Virtual Machine caching can consume most of the memory and leave only about a 3 GB caching fence for Windows. You can monitor the overall memory utilization of your system using the Windows Task Manager. The status bar of the Windows 2008 Task Manager displays overall CPU and memory utilization in percentages. If your memory utilization is around 91 percent or more, a condition might result where the caching algorithm tries to release memory for Windows but Windows does not have sufficient memory to execute the release code. Take one of the following actions to alleviate this situation: Reduce the amount of memory you selected for the MCP. Upgrade your server to a dual socket configuration if you have an upgradable single socket server. This allows you to increase the physical memory to 48 GB. Multipath I/O for Disks Multipath I/O is a fault-tolerance and performance enhancement technique where there is more than one physical path between the server and its storage devices through the buses, controllers, and switches connecting them. A simple example is a disk connected to two Fibre Channel ports. If a controller, port, or switch fails, I/O can be routed through the remaining controller transparently to applications. No changes are visible to the applications, other than incremental latency. The redundant paths can also be leveraged by software solutions to provide performance enhancing features such as load balancing. Multipath implementations consist of the storage system capabilities to provide the redundant paths and software solutions to manage the paths. Most major storage vendors provide their own multipath software solutions, for example EMC PowerPath. These solutions use the storage features in an optimal fashion and provide more advanced functionality in path failover, load balancing, and management; for example, configuration, monitoring, and reporting. Typically, vendor-specific solutions support commodity and open operating systems like Windows and Linux. Multipath technologies can be implemented in operating systems, which typically provide a common interface that can accommodate the different characteristics from the different storage devices of storage vendors. These native implementations vary in capabilities depending upon the operating system. For example, the capability that is built into the MCP I/O subsystems provides a complete solution from automatic failover and path selection of the I/O processor to monitoring and reporting through the ODT. Windows Server 2008 native Microsoft Multipath I/O (MPIO) capability provides basic multipath functions with a minimum of monitoring and reporting mechanisms. Windows relies on storage vendors to provide more complete and userfriendly multipath solutions. The Libra Model 450 or the FS1750 server can leverage both vendor-specific solutions and native solutions offered by the operating systems because of the emulated 4 12 3843 4072 001
Configuring External Storage Subsystems architecture and dual operating environments, Windows and MCP. Therefore, the Libra Model 450 or the FS1750 server offerings consist of a variety of multipath solutions for a variety of storage systems. Before examining the different multipath offerings on the Libra Model 450 or FS1750 servers, you must understand the definitions of the basic components of a multipath configuration. They are described in the following text: Initiators Initiators are devices on systems that are used to access storage devices. The Emulex Fibre Channel HBA is an initiator. In Windows, initiators are enumerated as SCSI ports. In the Libra Model 450 or the FS1750 MCP environment, initiators are configured as SCSI channels even though they are Fibre. Targets Targets are connection points on storage arrays used to present devices on the array. EMC Symmetrix directors and EMC CLARiiON storage processors are targets. For JBOD storage, each port on a disk drive is a target. Emulex HBA driver and the HBAnyware or OCManager utility map targets as a SCSI bus-target pair to the Windows operating system. In the MCP, targets are presented as controls (CTLs). Targets from different storage vendors are assigned specific CTL types so the MCP physical I/O subsystems can handle them efficiently and appropriately. Disk device Disk device is a logical unit number (LUN) as presented from the array to the targets. In Windows, LUNs are presented as SCSI LUNs. In the MCP, LUNs are referred to as units. On RAID arrays, a target usually presents multiple LUNs. JBOD targets typically only have one LUN per target. Physical path Physical path is a physical connection between an initiator and a target. This path can be a Direct Connect or through a Fibre Channel switch. For example, if you have two initiators, PA and PB, in the system connecting to storage through a switch; and each initiator is presented with 10 LUNs through two targets, T0 and T1, in the storage array; then you have four physical paths. Each LUN is said to have four physical paths: PA-T0, PA-T1, PB-T0, and PB-T1. A physical path to a LUN, in Windows terms, consists of a SCSI port, a SCSI bus, and a SCSI target. In MCP terms, a physical path to a unit consists of a channel and a control. Multipath solutions offered on the Libra Model 450 or FS1750 servers are discussed in the following text. MCP Control Groups This is a MCP-centric solution that allows the MCP to manage path failover and load balancing through the VMMCP I/O modules. In this implementation, all physical paths to a LUN are presented to the MCP through the active PCD. Controls that access the same LUNs are grouped together in a Control Group. You can configure Control Groups automatically through the Auto Build feature of the Console System Editor or manually using the System Editor drag-and-drop methods, 3843 4072 001 4 13
Configuring External Storage Subsystems when the Detect Control Groups option is enabled in the System Editor. This option is a system-wide option that affects all storage devices found in the system, including tape, CD-ROM, and DVD devices. Making any adjustment to a PCD containing Control Groups is a manual process, even when the adjustment is unrelated to Control Groups. There are a maximum of four controls in a Control Group. Configure all controls in a Control Group under the same CMU. A Control Group spanning across different CMUs is not supported. Control Groups are not available if other multipath solutions such as PowerPath that hide the multiple paths are running in the partition. Control Groups are supported for VSS disks only. MCP Logical Disks cannot be configured on the same storage subsystem where Control Groups are configured for VSS because Logical Disk files are presented multiple times and the System Editor is unable to recognize that they are the same files. The Control Groups implementation only handles active/active type of storage configurations where all paths are active all the time and have the equal ability to access the LUNs. For an active/passive storage system such as CLARiiON, where each LUN has a primary active path and an alternate passive path, I/O is only directed to the primary path. The alternate path is in a standby mode until the primary path fails. When configuring Control Groups to work with an active/passive storage system, all paths must be connected to the primary storage targets. For example, in the case of the CLARiiON, all paths must be connected to the owner storage processor of the LUN. This is a less desirable configuration because the storage processor can be a single point of failure. You can monitor and report Control Group status through ODT commands such as the RF CTL <control number command. The Control Group solution is included as part of the VMMCP software and it works similar to the MCP-based multipath implementation of the native Libra 180 MCP system. It handles failover and load balancing effectively as long as you follow the configuration rules. The Control Group solution is the only currently qualified solution for customers who need to connect multipath storage to the Libra Model 450 or FS1750 servers from vendors other than EMC. More details about configuring Control Groups are provided in Configuring Multipath VSS Disks. Windows Native MPIO Microsoft offers a multipath software package referred to in this document as Windows Native MPIO, which is included as a component of the Windows Server 2008 software. Windows MPIO is an important component because many other multipath solutions such as EMC PowerPath make use of Windows MPIO framework as a critical component of the solution. 4 14 3843 4072 001
Configuring External Storage Subsystems Windows Native MPIO includes a Microsoft Device Specific Module (DSM) that provides basic multipath functionality with limited management and monitoring tools. By default, you must manually configure the load balance policy and monitor I/O activities for each LUN through Windows Device Manager. You can automate these operations through scripting by using the Windows Management Instrumentation (WMI) interface. Due to these limitations, Windows Native MPIO using the Microsoft generic MPIO DSM is not recommended or supported for use with storage systems that have a more sophisticated multipath solution on the Libra Model 450 or FS1750 server. EMC PowerPath EMC offers a multipath software package called PowerPath. PowerPath supports a variety of storage systems including EMC CLARiiON and Symmetrix. It also supports storage systems offered by other companies. EMC provides different levels of PowerPath license, which determines different levels of functionality. Refer to EMC documentation for the appropriate license for your environment. For the Libra Model 450 or the FS1750 server, PowerPath is only qualified with EMC storage systems. PowerPath is a Windows-centric solution. PowerPath for Windows leverages the Microsoft MPIO framework. It provides an EMC specific DSM that manages failover and load balancing effectively. PowerPath requires the Windows native MPIO feature to be installed in the system. If MPIO is not installed, the PowerPath installation program installs it first. PowerPath provides a user interface management and monitoring tool set, including PowerPath Monitor and PowerPath Administrator, which allows you to configure load balancing policies and provides you with status when a path is lost or restored. PowerPath hides physical paths from the Windows file system and applications by creating PowerPath pseudo devices. Windows Native MPIO also creates pseudo devices. PowerPath pseudo devices are layered on top of Windows MPIO pseudo devices. Therefore, for each LUN, two additional pseudo devices exist. In Windows Device Manager, under Disk drives, only the Window Native MPIO pseudo devices are displayed by default. These pseudo devices are identified by the phrase Multi-Path Disk Device in their ID. For example, the Windows Native MPIO pseudo device ID for a CLARiiON RAID 5 LUN is displayed as DGC RAID5 Multi-Path Disk Device. To view the PowerPath pseudo devices or the physical devices, enable the Show hidden devices option in the View menu of Device Manager. Each pseudo device can contain any number of physical paths. When an application sends an I/O to a LUN, the I/O is really sent to the pseudo device. Then, PowerPath routes it to the actual device through the most optimal physical path. MCP Logical Disks and VSS disks both work with PowerPath. For VSS disks, the VMMCP filter drivers recognize and handle PowerPath and MPIO pseudo devices and cause the multiple paths to VSS disks to be hidden from the MCP. Only the path that has the Lowest SCSI address is exposed to the System Editor and therefore configured in the PCD. Lowest SCSI address is an important concept for keeping PowerPath and Windows Native MPIO transparent to the MCP and maintaining PCD persistence across Windows reboots. More details are provided in Lowest SCSI address Implementation for PowerPath and MPIO. 3843 4072 001 4 15
Configuring External Storage Subsystems PowerPath is the recommended multipath solution for EMC storage for the following reasons: Supports MCP Logical Disks and VSS disks in the same server. Provides advanced failover and load balancing capabilities with user-friendly management tools. Path management is automatic and transparent to the MCP application environment. Does not require special handling in storage system setup and configuration. Standard procedures for Windows applies. Allows, in the case of CLARiiON, paths to be connected to all storage processors in the disk system, avoiding a single point of failure. Pseudo devices created for PowerPath can potentially add resource overhead for Windows in CPU cycles and memory usage. During normal operations, this overhead is insignificant. I/O routed through the pseudo devices perform effectively and no visible impact is observed. There is also no overhead observed during failover operations. The impact becomes more apparent in multipath configurations that consist of many paths and a large number of LUNs. In these large configurations, longer Windows boot time and slower path recovery processing have been experienced. See Additional Considerations for the recommended maximum configuration. Lowest SCSI Address Implementation for PowerPath and MPIO The concept of Lowest SCSI Address is only applicable when PowerPath and Windows Native MPIO are used for path management of VSS disks. This concept does not apply to Logical Disks. SCSI address is only meaningful when configuring VSS disks. This concept can also apply to any other multipath solutions based on Windows MPIO framework that might be qualified in the future. Lowest SCSI Address refers to the physical path of a multipath LUN that has the lowest SCSI port ID. If multiple physical paths contain the same port ID, then the port with the lowest SCSI target ID is selected as the Lowest SCSI Address for the LUN. For example, if a LUN has the following four physical paths, then the Lowest SCSI Address selected for the LUN is Port 0, bus 0, target 2, LUN 1: Port 0, bus 0, target 2, LUN 1 Port 0, bus 0, target 4, LUN 1 Port 1, bus 0, target 0, LUN 1 Port 1, bus 0, target 1, LUN 1 As mentioned in EMC PowerPath, VMMCP filter drivers leverage PowerPath pseudo devices to hide the multiple paths of VSS disks from MCP. The SCSI address for a PowerPath pseudo device can be assigned by using any one of the multiple physical paths. This assignment is done by the PowerPath algorithms and can change across Windows reboot. If the VMMCP disk filter driver uses the SCSI address assigned to the pseudo device of a VSS disk, then the active PCD file might need to be adjusted to accommodate the SCSI address change after a reboot. To prevent the disk access problems that might result if the adjustment is not done, the Lowest SCSI Address algorithm was developed. As long as the storage configuration remains the same, no 4 16 3843 4072 001
Configuring External Storage Subsystems matter how many paths a VSS disk has, the Lowest SCSI Address is chosen and it remains constant across reboots. The Lowest SCSI Address implementation is mostly transparent to the user. I/Os from MCP applications are routed to the disk using the Lowest SCSI Address path, but PowerPath can route the I/O through a path that has a different SCSI address. If a path fails, it is only detected by the VMMCP filter drivers and not by the VMMCP I/O modules or the MCP. Failover takes place automatically without the involvement of the MCP. Note: If the Lowest SCSI Address path fails and a Windows reboot occurs before the Lowest SCSI Address path is repaired, then the Lowest SCSI Address assignment for the LUN is changed after the system restarts. An adjustment in the PCD file is required to bring the CTL online in the MCP. This is a rare occurrence. Identifying the HBA Associated with the Lowest SCSI Address You can use the Console System Editor to identify the HBA that is associated with the Lowest SCSI Address by performing the following steps: 1. Start the Console System Editor and open the active PCD file. 2. Locate the SCSI channel of the VSS disk you are interested. Right-click the channel and select Channel Properties. The SCSI Channel Properties window appears. The SCSI Port, SCSI Path, and SCSI Bus indicate the address of the lowest SCSI path. The Physical Slot number shows which slot this Emulex HBA is in. Note: The Emulex Fibre Channel HBAs configured in the Libra Model 450 and FS1750 servers can have dual ports. The SCSI Channel Properties in the PCD provides information about the slot where the HBA is but does not provide information about the port of the HBA that the SCSI address is associated with. Use the Emulex HBAnyware or OCManager utility to make this distinction. You can also use HBAnyware or OCManager and the active PCD xml file to find the physical slot number without involving the System Editor. The active PCD xml file is the xml file with the same file name as the active PCD file. Perform the following steps to use HBAnyware or OCManager to find the physical slot number: 1. Start HBAnyware or OCManager. 2. Select the required HBA port in the left pane. 3. Select the Port Information tab in the right pane and note the OS Device Name. The OS Device Name is in the form of \\.\scsi followed by a number and a colon. For example, \\.\scsi7:. The number 7 in the example represents the Windows SCSI Port ID. 4. Click File, View, and then PCD Directory from the Console for MCP window. 5. Locate the active PCD xml file and open it with the Notepad or Wordpad application. 3843 4072 001 4 17
Configuring External Storage Subsystems 6. Locate the SCSI Bus whose <Win32SymbolicLinkName> matches the OS Device Name you noted in step 3. 7. Locate the physical slot number in the field <PhysicalSlot>. For example, for SCSI Port 7, the active PCD xml file might contain the following statements: Note: The bold text in the following statements is not part of the actual interface. It is used to highlight the statements you need to locate. <SCSIBus> <PortDeviceName>Emulex</PortDeviceName> <Win32SymbolicLinkName>\\.\Scsi7:</Win32SymbolicLinkName> <DeviceName>\\.\AsScsi0070</DeviceName> <Irq>4294967277</Irq> <IOPort>0</IOPort> <IOPortMax>0</IOPortMax> <MemoryMin>3564068864</MemoryMin> <MemoryMax>3564072959</MemoryMax> <PciBusNumber>134</PciBusNumber> <Slot>0</Slot> <ScsiPort>7</ScsiPort> <PciBaseClass>12</PciBaseClass> <PciSubClass>4</PciSubClass> <PciProgIF>0</PciProgIF> <VenID>4319</VenID> <DevID>61696</DevID> <ScsiPath>0</ScsiPath> <InitiatorID>255</InitiatorID> <ScsiBus>20</ScsiBus> <PhysicalSlot>3</PhysicalSlot> <CardRelBus>0</CardRelBus></SCSIBus> Additional Considerations The following text describes large disk configurations, the expected behavior when you lose all the paths to disks, and ways to recover after losing all paths. Large Configuration Considerations Large disk configurations typically involve VSS disks because each VSS pack is one LUN. In the testing performed during Libra Model 450 and FS1750 server qualification, running a configuration with a large number of disks reveals no noticeable impact to the MCP responsiveness. The large configuration considerations discussed here primarily deal with Windows responsiveness and not MCP performance. Windows responsiveness refers to one or more of the following conditions: Time taken for the server to come up from the BIOS initialization to the Windows logon screen Time taken for Windows Disk Manager or Device Manager to start Promptness of the PowerPath Administrator to display status updates, if PowerPath is used Time taken to detect path recovery after one or more paths have failed 4 18 3843 4072 001
Configuring External Storage Subsystems General response to keyboard and mouse input Before discussing large configurations, it is important to understand Windows internal devices and their impact to the system. An internal device object is created for every device that Windows detects, including physical devices and pseudo devices, if any. In a multipath configuration, the number of internal devices Windows detects and manages can increase significantly. Each internal device consumes Windows resources in terms of CPU cycles and memory. Therefore, the more internal devices you have the more work Windows has to do. When planning a large configuration, it is not only the number of LUNs and the number of paths you need to consider but also the number of internal devices that can result from the multipath solution you choose. The formula for calculating the internal device count for each solution is described in this topic. When comparing the number of internal devices created by each solution, PowerPath has the highest count and Control Groups has the least. Control Groups No pseudo device is involved in Control Group configurations. For Control Group configurations, the formula is PowerPath number of physical paths * number of LUNs For PowerPath configurations, two pseudo devices are created for each LUN. The formula is (number of physical paths + 2) * number of LUNs Windows Native MPIO For Windows Native MPIO configurations (using the Microsoft DSM), one pseudo device is created for each LUN. The formula is (number of physical paths + 1) * number of LUNs The recommended maximum disk configuration on a Libra Model 450 or an FS1750 server is 255 LUNs with four paths to each LUN or an internal device count less than 1530. The number 1530 comes from the PowerPath formula, which yields the highest count. You can have more paths if your configuration does not require as many LUNs. Use the internal device count formula to help you gauge the size of your configuration. With this recommended maximum configuration, it can take Windows longer to perform certain tasks but the responsiveness is acceptable. If your configuration goes beyond this size, Windows responsiveness can degrade more noticeably and even becomes unpredictable. For most cases, a maximum of four paths to 255 LUNs is sufficient. If your need is larger than this recommendation, consider one or more of the following suggestions: Reduce the number of paths if you want more LUNs. Reduce the number of LUNs by increasing the capacity of each LUN. Use MCP Logical Disks. 3843 4072 001 4 19
Configuring External Storage Subsystems You can contact your Unisys representatives to review your configuration to ensure the system can perform to your expectation. Recovery after Losing All Paths Considerations If you have configured your multipath configuration appropriately for redundancy and high availability, losing all the paths at once will be a rare occurrence. The following text describes the expected behavior when you lose all your paths and how you can recover. Losing all the paths to your disks means that the MCP has lost its access to all the units behind these paths. You see CONTROL NOT PRESENT messages displayed on the ODT accompanied by flashing messages. During this time, it is difficult to accomplish much from the ODT. MCP retries the connections for a period of time. Depending on the type of storage (control type), this period can vary significantly. If the paths recover during this period, the controls are restored automatically in most cases. If not, you must use the UR and UR- ODT commands to bring the control online. Your application might be interrupted, depending on how the application is written to handle exceptional conditions. If you have VSS disks and use PowerPath, you must restore the Lowest SCSI Address path first, unless you can restore all the paths at relatively the same time. If you are not able to restore the Lowest SCSI Address path, then an adjustment to your active PCD and a halt/load is required. Use the procedure described in Identifying the HBA Associated with the Lowest SCSI Address to help identify the connection that is associated with the Lowest SCSI Address. Losing all paths to Logical Disks exhibits different behavior than the VSS disks. When the last path is lost, media errors are reported and these errors are returned to the applications. When the path is restored, you must close, free, and then acquire the disk units in the MCP to regain access. If there are open files on a disk unit, which can be determined using the PER PK command, then use a CLOSE :DS command to close the unit. The CLOSE :DS command terminates programs with open files on the unit. Under some circumstances, it might be faster and less disruptive to halt/load your system than to use this command. Configuring Multipath VSS Disks Information provided in this subsection is specifically for configuring VSS disks. If you only have MCP Logical Disks in the system, follow the instructions provided by the storage vendor and configure your storage system as if it were connected to a Windows server. This subsection demonstrates how to connect different storage systems to the Libra Model 450 or the FS1750 server using the supported multipath solutions. To better explain the different connection options, example configurations with diagrams are provided for each family of storage systems. Benefits and restrictions for each option are also discussed. The examples are shown with two to four Fibre Channel HBA ports in the server for illustration purposes only. More connections can be added and the same connection principles can be applied. The number of storage ports shown in 4 20 3843 4072 001
Configuring External Storage Subsystems the diagram does not necessarily reflect the capability of the storage system. They are intended to be examples only. Before setting the storage systems, you need to be aware of the following issues. Host mode Setting for the Storage Systems If your storage system has a setting for specifying the host type, such as EMC Symmetrix director flags, choose the settings for a Windows host. Refer to documentation provided by the storage vendor for the specific value to use for these settings. Auto Assignment Setting for CLARiiON LUNs When creating LUNs in the CLARiiON for the Libra Model 450 or the FS1750 server, ensure that the Auto Assignment setting for the LUNs is disabled. Disabling Auto Assignment allows the software multipath solution to control the ownership of the LUNs when one of the storage processors becomes unavailable instead of letting the storage system handle it automatically. This setting is required whether you use PowerPath or MCP Control Groups. PowerPath Dead and Alive Sequence during Initial Setup The PowerPath dead and alive sequence occurs after attaching EMC storage to the server and installing PowerPath for the first time. When the system restarts after the required reboot from installing PowerPath, each PowerPath managed LUN becomes dead and then becomes alive almost immediately. You can see these back-to-back dead and alive messages in the Windows System event log. You can also see errors recorded in the PowerPath Administrator for each LUN, one error for each path that the LUN has. This sequence occurs because Windows Plug-and-Play mechanism rebuilds each device with PowerPath drivers. It continues until each LUN on each path has been cycled through. If you have a configuration with many paths and many LUNs, the process can take a long time to complete. For example, for a configuration consisting of 4 paths to 255 LUNs, the process might take 45 minutes to over an hour to complete. Wait till the process completes. This behavior occurs only once during the initial storage setup. It does not occur in the subsequent reboots. Using PowerPath Administrator with VSS Disks When PowerPath is used to manage the multipath I/O for VSS disks, you can use PowerPath Administrator to monitor the VSS disk I/O activities. VSS disks are displayed in the PowerPath Administrator console window in the same way as Windows disks, which is by disk numbers. These disk numbers match the disk numbers displayed in Windows Disk Manager. Control Groups Detection Issues The VMMCP software device discovery algorithm detects Control Groups by looking at all the devices, including disks, tapes, and CD-ROMs, on each SCSI target in the Windows environment. If the number of devices and their attributes on one target perfectly match the number of devices and their attributes on another target of a different port, then the algorithm assumes that they are duplicate images of the same 3843 4072 001 4 21
Configuring External Storage Subsystems devices and group them in the same Control Group. Targets in the same SCSI port are not examined with one another; therefore, Control Groups do not support a configuration where multiple initiators are connected to the same target. Several attributes are used in this matching process, including the following: The number of LUNs behind a target. The LUN capacity. The Inquiry ID of the LUN. The target ID (for non-emc storage systems only). When a match is found, the targets are marked to be a part of the same Control Group and the duplicate devices are removed from the internal tables. This allows the Console Auto Build feature to automatically build Control Groups. On some systems, the algorithm can incorrectly detect a Control Group when it does not exist. For example, if you have two identical tape drives in the system and each is connected to a different HBA using the same target number. The Control Group detection algorithm erroneously marks them as being in a Control Group and one of the tape drives is removed from the internal tables. When this occurs, you cannot build a PCD with both devices and also cannot access the removed tape drive. If Control Groups are detected incorrectly, perform one of the following steps: If there are no Control Group configurations in the system, disable the Detect Control Groups option in the System Editor Preferences dialog box. If you are using HBAnyware or OCManager, change the target ID of any one device on either SCSI port to another available target ID. This is useful if you have multiple tape or CD-ROM devices on different ports that have the same SCSI target ID. Change the LUN attributes of any device. You can add additional LUNs or change the LUN capacity to make the LUN configuration behind one target different from the other. Changing the target ID or LUN attributes causes the algorithm to see the devices on one target as different from the other and prevents any Control Group processing. CLARiiON Storage Systems EMC CLARiiON is an active/passive type of storage system. It consists of two storage processors, SPA and SPB. Each storage processor has multiple Fibre Channel frontend ports to connect to hosts. Different models of CLARiiON might have a different number of these ports. Each LUN created in the CLARiiON consists of an owner storage processor and a non-owner storage processor. The owner storage processor provides the primary path to this LUN, which is also called the active path. The nonowner storage processor is in standby mode, also called the passive path, when this LUN is concerned and is used only for failover. I/Os to the LUN are only accepted through the active path and not the passive path. Therefore, load balancing is not available across storage processors. It is only available by using multiple ports of the same storage processor. 4 22 3843 4072 001
Configuring External Storage Subsystems Note: Some CLARiiON arrays support Asymmetric Logical Unit Access (ALUA), which allows Windows Native MPIO to perform load balancing across storage processors. This is not recommended by EMC and is not supported on the Libra Model 450 and FS1750 servers. PowerPath and MCP Control Groups are both supported with CLARiiON arrays but PowerPath is the preferred and recommended multipath solution. Windows Native MPIO is not supported with CLARiiON on the Libra Model 450 or FS1750 servers. When using Control Groups to manage paths on the Libra Model 450 or the FS1750 server, the MCP PCD can only include paths through a single storage processor for each CLARiiON based LUN. As a result, the storage processor becomes a single point of failure for LUN access. It also complicates storage processor maintenance activities such as firmware update, because these will cause loss of connectivity to the LUN. The more effective multipath solution for CLARiiON is through the use of PowerPath. PowerPath automatically detects available paths to the LUN, differentiating active ones from the passive ones and distributes I/O to LUNs appropriately. When all the active paths to a LUN fail, PowerPath initiates the trespass operation, which moves the ownership of the LUN to the other storage processor. For example, during a storage processor firmware update. I/O to the LUN continues through the new owner. In the absence of PowerPath, load balancing and failover through MCP Control Groups can be configured but the configuration is more restrictive. This becomes apparent in the examples provided later in this section. Direct Connect and SAN attach configurations are supported for both multipath solutions, but a SAN attach configuration can potentially provide more paths to each LUN, and consequently, better performance and more resiliency. An example of each type of connection is illustrated later in this section. When registering the Libra Model 450 or the FS1750 server HBA initiators to the CLARiiON using the Navisphere Manager Connectivity Status dialog box, select the following values. Parameter Value Initiator Type: Array CommPath: Failover Mode: CLARiiON Open Enabled 1 for PowerPath 0 for Control Groups Note: Other failover modes are not qualified. Note: The figures in the subsequent topics use the Libra 450 server as an example. However, the figures are also applicable to the FS1750 server. 3843 4072 001 4 23
Configuring External Storage Subsystems Direct Connect using PowerPath Figure 4 1 illustrates a configuration for PowerPath. In this example, the Libra Model 450 server is directly connected to the CLARiiON. Each LUN has two active I/O paths and two passive paths. For example, I/O to LUN 0 can go through SPA port 0 (SPA0) or SPA port 2 (SPA2). I/O to LUN 1 can go through SPB port 0 (SPB0) or SPB port 2 (SPB2). If SPB2 fails or the HBA to which it is connected fails, all I/O to LUN 1 is routed through SPB0. If the entire SPB becomes unavailable, PowerPath automatically trespasses LUN 1, 3, and 5 to SPA. I/O to LUN 1 is then routed through SPA0 and SPA2. This configuration has the following characteristics: Can configure with both VSS disks and Logical Disks on the same server using the same storage system. Redundancy is available at the HBA level. If one HBA fails, I/Os are directed through the other HBA. Redundancy at the storage level is provided across the multiple ports of each storage processor as well as cross storage processors. If any port on the same storage processor fails, the other ports of the same storage processor take over. If the storage processor becomes unavailable, all LUNs on that storage processor are trespassed to the surviving storage processor and I/O continues through that storage processor. Load balancing is performed at the HBA level and across the multiple ports of the same storage processor. I/O to a LUN is only directed through the storage processor that owns the LUN. Although there are multiple paths, only one SCSI channel is presented in the PCD. This SCSI channel represents the Lowest SCSI Address path. All load balancing and failover activities are carried out at the device level by PowerPath and are transparent to the MCP environment. I/O activities to each LUN and the status of each path can be monitored through the PowerPath Administrator. 4 24 3843 4072 001
Configuring External Storage Subsystems Figure 4 1. CLARiiON Direct Connect using PowerPath SAN Attach using PowerPath The same capabilities provided through Direct Connect using PowerPath are available in a SAN Attach configuration. By using redundant switches and appropriate zoning techniques, SAN Attach offers more opportunities for availability and resiliency. Figure 4 2 demonstrates a configuration that provides maximum load balancing and redundancy effect using two HBAs and two ports of each storage processor. According to the documentation from EMC, single-hba zoning is recommended. In addition to redundant HBA and redundant storage ports, two SAN switches in separate fabrics are used to eliminate the switch or an entire fabric from being a single point of failure. The switches are zoned to connect each HBA to two storage ports, one port from SPA and one port from SPB. Each LUN has four paths, two active and two passive. For example, I/O to LUN 0 is distributed through HBA #1 to SPA1 as well as through HBA #2 to SPA3. If either SPA1 or SPA3 fails, or if either of the HBA fails, I/O is automatically switched to the other port. If the entire storage processor becomes 3843 4072 001 4 25
Configuring External Storage Subsystems unavailable, all the LUNs on that storage processor are trespassed to the remaining storage processor and I/O continues through that storage processor. Figure 4 2. CLARiiON SAN Attach using PowerPath Direct Connect using Control Groups Control Groups do not support MCP Logical Disks. Do not configure any Windows disks on the same storage processor on which you are configuring Control Groups for VSS disks. This is because these Windows disks have no multipath software to manage them and they are presented to Windows multiple times. For example, as shown in Figure 4 3, do not use any of the LUNs owned by SPA for Windows disks to create MCP Logical Disks on it. This configuration has the following characteristics: If you want to configure Logical Disks in the same storage, then you can use the other storage processor (SPB in this example) by connecting it to a different initiator. You can then assign this initiator to a second storage group as shown in 4 26 3843 4072 001
Configuring External Storage Subsystems Figure 4 3. The LUNs in this second storage group have only one path. If you configure some single-path LUNs for MCP Logical Disks, ensure to create some differences between the LUNs for Logical Disks and those used for VSS disks. This ensures that the Control Group Detection logic does not get confused and create an erroneous Control Group. You can choose one of the following differentiation methods: Make the number of LUNs different. Make the size of the LUNs different. Make the RAID configuration for the LUNs different. A different RAID configuration will give you a different Inquiry string for the LUN. PowerPath must not be installed on the server. The Detect Control Group option must be enabled in the System Editor. MCP manages redundancy and load balancing through the definition of a Control Group in the PCD file. This Control Group contains two to a maximum of four controls and all controls can see the same units or LUNs. MCP directs I/O to each unit through either control. A control, in this case, is a port on the storage processor. LUNs are not automatically trespassed if the storage processor becomes unavailable. There is no failover and your application can be interrupted. If you need to manually trespass LUNs to the surviving storage processor, you must reboot the server for the LUNs to be detected correctly and you must also adjust your PCD manually or create a new PCD. In Figure 4 3, each LUN owned by SPA has two I/O paths, SPA0 or SPA2. If one of the storage processor port or the HBA to which it is connected fails, MCP routes I/O through the other control. If the entire storage processor becomes unavailable, LUNs are not trespassed to SPB. This is not supported using Control Groups. Therefore, all paths to the LUNs are lost. Figure 4 3 also illustrates a way to configure a second storage group using a different HBA connecting to SPB in a single path configuration. Multiple paths are not allowed because PowerPath is not installed. LUN 10 and LUN 11 can be used to create MCP Logical Disks. 3843 4072 001 4 27
Configuring External Storage Subsystems Figure 4 3. CLARiiON Direct Connect using Control Groups You can connect multiple storage systems on the same server and configure different Control Groups. However, you must ensure that one of the following conditions is true: The number of LUNs in each storage system is different. The LUNs are created using a different RAID configuration so they have a different Inquiry string. At least one of the LUNs has a different capacity. SAN Attach using Control Groups Configuring Control Groups in a SAN environment has more restrictions than configuring for PowerPath. Single-HBA zoning is still recommended. However, you must create zones that contain only one HBA and one storage processor port, as shown in Figure 4 4. No other zoning is supported. You can use two switches instead of one to avoid the switch being a single point of failure. 4 28 3843 4072 001
Configuring External Storage Subsystems The same rules and restrictions described in "Direct Connect using Control Groups" also apply to SAN Attach. Figure 4 4. CLARiiON SAN Attach using Control Groups Multiple Control Groups with MCP Mirroring To compensate for the lack of automatic failover between the storage processors, you can create a configuration with two sets of Control Groups and then mirror some of the LUNs in each of the Control Group using MCP mirroring, as shown in Figure 4 5. You can choose either Direct Connect or SAN Attach. This configuration provides added redundancy. If one storage processor becomes unavailable, you still have a copy of the data to access from the other storage processor. 3843 4072 001 4 29
Configuring External Storage Subsystems Figure 4 5. CLARiiON using Two Groups with MCP Mirroring In Figure 4 5, SPA owns 10 LUNs. SPB owns 12 LUNs. The different number of LUNs is necessary to prevent the Control Group Detection logic from creating one Control Group with four controls in it. You can create MCP mirrored disks using 10 LUNs or a subset of them from each storage processor. In case a storage processor becomes unavailable, the mirrored set is audited or possibly broken, but you still have access to the data using the LUNs on the other storage processor. However, once the storage processor is repaired, you might need to rebuild the mirror set. Symmetrix Storage Systems EMC Symmetrix is an active/active type of storage system. All paths to the same LUNs have equal access and are active at the same time. This feature makes configuring for PowerPath and Control Groups easier. The same Direct Connect configuration can be used for either PowerPath or Control Groups. The SAN Attach for PowerPath and Control Groups are slightly different in the way the zones are defined. These configurations are explained in the following text. 4 30 3843 4072 001
Configuring External Storage Subsystems PowerPath and MCP Control Groups are both supported with Symmetrix arrays but PowerPath is the preferred and recommended multipath solution. Windows Native MPIO is not supported with Symmetrix arrays on the Libra Model 450 or FS1750 server. Note: The figures in the subsequent topics use the Libra 450 server as an example. However, the figures are also applicable to the FS1750 server. Direct Connect using PowerPath This configuration has the following characteristics: Can configure with both VSS disks and Logical Disks on the same server using the same storage system. All paths have equal access to the LUNs to which they are connected. Load balancing and failover are performed equally across all paths. Although there are multiple paths to the same set of LUNs, only one path, the Lowest SCSI Address path, is presented in the PCD. This path is configured as a SCSI channel; all load balancing and failover activities are carried out at the device level by PowerPath and are transparent to the MCP environment. I/O activities to each device can be monitored through the PowerPath Administrator. VSS disks are displayed as disk number 1000 and above. In Figure 4 6, each LUN has two I/O paths, one through FC HBA 1 and Port 3a1 and the other through FC HBA 2 and Port 4a1. PowerPath distributes I/O equally across both paths. When one path fails, PowerPath routes I/O through the other path. 3843 4072 001 4 31
Configuring External Storage Subsystems Figure 4 6. Symmetrix Direct Connect using PowerPath or Control Groups Direct Connect using Control Groups You can also use the same connection in Figure 4 6 for Control Groups. Make sure to comply with the following rules: Control Groups do not work with MCP Logical Disks. This means that all the LUNs that are part of a Control Group must be configured as VSS disks. If you want to configure Windows disks and use them as MCP Logical Disks, connect them using a separate single path and make sure their attributes differ from the VSS disks to avoid confusing the Control Group Detection logic. PowerPath must not be installed on the server. The Detect Control Groups option must be enabled in the System Editor. MCP manages redundancy and load balancing through the definition of a Control Group in the PCD. This Control Group contains two to a maximum of four controls and all controls can see the same units or LUNs. MCP distributes I/O to each unit across the controls. In this configuration, Symmetrix port 3a1 and 4a1 represent the controls declared in the PCD. If any control fails, MCP routes I/O through the other control. 4 32 3843 4072 001
Configuring External Storage Subsystems SAN Attach using PowerPath The same capabilities provided through a Direct Connect using PowerPath are available in a SAN Attach configuration. By using redundant switches and appropriate zoning, SAN Attach offers more opportunities for more resiliency. Figure 4 7 illustrates an effective load balancing and redundancy configuration using four HBAs and four director ports of a Symmetrix storage system. Documentation from EMC recommends single-hba zoning. There are two sets of LUNs and each LUN is assigned to two director ports. LUNs 0-9 are assigned to Port 3a1 and Port 4a1. LUNs 10-19 are assigned to Port 7b0 and Port 8b0. Each HBA is zoned to two director ports so each LUN has four paths. LUNs 0-9 have the following paths: HBA 1 and Port 3a1 HBA 2 and Port 3a1 HBA 3 and Port 4a1 HBA 4 and Port 4a1 LUNs 10-19 have the following paths: HBA 1 and Port 7b0 HBA 2 and Port 7b0 HBA 3 and Port 8b0 HBA 4 and Port 8b0 3843 4072 001 4 33
Configuring External Storage Subsystems Figure 4 7. Symmetrix SAN Attach using PowerPath SAN Attach using Control Groups Configuring Control Groups in a SAN environment has more restrictions than configuring for PowerPath. Single-HBA zoning is recommended. However, you must create zones that contain only one HBA and one storage port, as shown in Figure 4 8. No other zoning is supported. The same rules and restrictions as described in Direct Connect using Control Groups also apply to SAN attach. 4 34 3843 4072 001
Configuring External Storage Subsystems Figure 4 8. Symmetrix SAN Attach using Control Groups 3843 4072 001 4 35
Configuring External Storage Subsystems 4 36 3843 4072 001
Section 5 Completing Software Reinstallation This section describes how to reinstall the software. Caution Software reinstallation, which is described in this section, is a customer responsibility. However, 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. Overview 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 groundzero installation. You might have to resort to ground-zero installation because of the following reasons: 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. 3843 4072 001 5 1
Completing Software Reinstallation 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: Back up data files 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: Systems Management Tools and Documentation DVD 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 Server Management CD-ROM 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 Before You Begin Before reinstalling the software on the partition, disconnect any cables that are attached to network and storage adapter ports on the server. 5 2 3843 4072 001
Completing Software Reinstallation Ensure that the cables remain routed and that connection points are tagged or labeled, to simplify the cable connection process after the server is reinstalled. Caution If external peripheral cables are left attached to the server when the Windows operating system is reinstalled, data loss or an installation failure can occur. Preparing a Replacement Drive for the Operating System Load If the operating system disk or the MCP halt/load disk fails and cannot be fixed by replacing a member of the RAID group, you must replace the drive. Before reinstalling the software on the partition, the replacement drive must be initialized and configured. The recommended configuration of the operating system disk (typically C:\) is 200 GB minimum with RAID protection. The recommended configuration of the MCP halt/load disk (typically D:\) is 73 GB minimum with RAID protection. To configure and initialize the replacement drive, refer to the documentation pertaining to the RAID card for your system (typically PERC 6/6i). This documentation is contained on the Dell Systems Management Tools and Documentation DVD that is shipped with the system. Reinstalling the Software This topic provides instructions for reinstalling the software. If you have problems during software reinstallation, refer to Section 7, Troubleshooting Information. Software reinstallation includes the following tasks: Note: For a complete software reinstallation, perform all the tasks. Otherwise, perform only the required tasks. Set up BIOS Refer to Setting Up BIOS in Section 3 for details. Reinstall the Windows operating system Refer to Installing the Windows Operating System in Section 3 for details. Configure the Windows operating system Refer to Configuring the Windows Operating System in Section 3 for details. Reinstall Virtual Machine for ClearPath MCP software If you perform a complete reinstallation of Windows, you must reinstall the Virtual Machine for ClearPath MCP software. Refer to Installing the Virtual Machine for ClearPath MCP Software in Section 3 for details. 3843 4072 001 5 3
Completing Software Reinstallation Note: After reinstalling the Virtual Machine for ClearPath MCP software, 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. Reinstall Network Services software If you need to reinstall Network Services on your system, complete the following steps: 1. Follow the steps for removing Network Services from the Windows server. See the Network Services Implementation Guide for more information. 2. Reinstall Network Services. Refer to Installing Network Services Software in Section 3 for details. Enable NetBIOS over TCP/IP Refer to Enabling NetBIOS over TCP/IP in Section 3 for details. Configure the operating system for accessing MCP shares Refer to Configuring the Operating System for Accessing MCP Shares in Section 3 for details. Create the MCP logical disk using the MCP Quick Install DVD Refer to Creating the MCP Logical Disk Using the MCP Quick Install DVD in Section 3 for details. Connect the TCP/IP network drive Refer to Connecting the TCP/IP Network Drive in Section 3 for details. Connect to the external public LAN Refer to Connecting to the External Public LAN in Section 3 for details. Configure the optional uninterruptible power supply (UPS) Refer to Configuring the Optional Uninterruptible Power Supply (UPS) in Section 3 for details. Finalizing the Reinstallation The software reinstallation for your server is complete. Perform the following tasks to finalize your system configuration: Reestablish all cable connections that were disconnected before the operating system was reinstalled. Refer to Configuring External Storage Subsystems in Section 4 to configure the external storage devices, and then perform a halt/load operation with the configuration files that you backed up. 5 4 3843 4072 001
Section 6 Backing Up the Server Backing up a Libra Model 450 or FS1750 server involves backing up data in the Windows environment and in the MCP environment. Data in the Windows environment includes the Windows operating system and critical configuration information used by the Virtual Machine for ClearPath MCP software to control and support the MCP environment. Data in the MCP environment includes the MCP operating system and customer applications and data. To back up MCP data, use tools and solutions available in the MCP environment. Backing up MCP data is not covered in this document. Backing Up Data in the Windows Environment The following options are available for backing up data in the Windows environment. These options vary in complexity and cost. However, for all the options, backing up data to Windows tape devices is not supported on the Libra Model 450 server or the FS1750 server. Backing up only critical configuration data This option involves copying the critical configuration data to a removable media or a workstation connected to the private network. A USB thumb drive is shipped with the server to help you back up the critical configuration data. Ensure that you copy the files each time you make configuration changes. The critical configuration data includes the following: PCD files C:\ProgramData\Unisys\Virtual Machine for ClearPath MCP\Configuration\*.pcd, *.pcc, *.gen, *xml, and *.txt ODT configuration files C:\ProgramData\Unisys\Virtual Machine for ClearPath MCP\ODT\*.* This option requires the least effort and cost. However, it requires a manual reinstallation if the server crashes, which might take a considerable amount of time. Using the Windows Server Backup program If you want to backup an entire Windows volume, you can use the Windows Server Backup program. This program is released as a feature by Microsoft on Windows Server 2008. Using the Windows Server Backup program, you can backup a Windows volume to removable media, hard disks, and network shares. 3843 4072 001 6 1
Backing Up the Server By default, the Windows Server Backup program is not installed when you install Windows Server 2008. Perform the following steps to install the Windows Server Backup program: 1. On the Start menu, right-click Computer, and then click Manage. The Server Manager window appears. 2. Select Add Features in the right pane. The Add Features Wizard appears. 3. Expand Windows Server Backup Features. 4. Select the Windows Server Backup and Command-line Tools check boxes. 5. Click Next. 6. Click Install. 7. Click Close when the installation completes. Starting the Windows Server Backup Program Perform the following steps to start the Windows Server Backup program: 1. On the Start menu, point to Administrative Tools, and then click Windows Server Backup. The Windows Server Backup (local) window appears. 2. Perform a single backup or schedule a regular backup. Refer to the Microsoft documentation for detailed feature description of Windows Server Backup and for information about how to backup and restore using the Windows Server Backup Wizard. Using third-party backup and restore tools You can purchase third-party backup tools, such as Norton Ghost from Symantec, for a full-system backup. Using this option can take time to create and update the image, but the recovery time is the shortest if the server requires a complete reinstallation. Notes: Do not select third-party backup tools that support only tape devices because tape devices on a Libra Model 450 or FS1750 server are configured exclusively for use in the MCP environment. Unisys does not support third-party backup tools. If these tools fail to work or interfere with the MCP environment, Unisys does not accept User Communication Forms (UCF) for such cases. 6 2 3843 4072 001
Section 7 Troubleshooting Information This section contains a list of problems that you might encounter during installation and configuration of the Libra Model 450 or FS1750 server. This information is used by customers and Unisys service representatives for solving system problems. General Hardware Installation Problems If you encounter problems with hardware installation and configuration such as platform BIOS update, inbuilt RAID array configuration using the RAID 6/I utility, or updating adapter firmware, use the System Management Tools and Documentation DVD that is shipped with the server to obtain additional information. Perform the following steps to view additional information in the System Management Tools and Documentation DVD: 1. Insert the System Management Tools and Documentation DVD in the DVD drive. 2. Click Autorun.exe. The Dell Open Manage Install window appears. 3. Click Documentation, and then click View. The Internet Explorer browser opens and displays the Dell Product Documentation screen. 4. Perform one or both of the following: Browse to select the appropriate documentation for your specific issue. Select Dell Support from the left pane. The Welcome to Dell Support screen appears. a. Select Troubleshooting under Support Options in the left pane. b. Use the service tag of the server to locate additional information. System Startup Problems Some of the following conditions can cause system startup problems. Each of these is discussed in this section, along with possible causes and some corrective actions. Network Services software Setup program does not complete. Console for MCP initialization problems. 3843 4072 001 7 1
Troubleshooting Information 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: 1. On the Start menu, click Control Panel. 2. Double-click Programs and Features and look for ClearPath Network Services in the list of installed programs. To verify that the NIC is functional, perform the following steps: 1. On the Start menu, right-click Computer, and then click Manage. The Server Manager window appears. 2. Expand Diagnostics in the left pane and select Device Manager. 3. Expand Network adapters in the right pane. 4. Select every device that has Unisys Network Services as part of the name under Network adapters. The properties for each device must report This device is working properly in the Device status field. Console for MCP Initialization Problems Some of the following conditions can cause problems: Errors were introduced during customer setup procedure. A complete software reinstallation was done, but Windows was not installed or configured 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. Check the Windows Application Event Log for error and warning messages from the VMMCP software modules. 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 as follows: 1. Right-click Console for MCP on the desktop and click Properties. 2. Select the Shortcut tab and note the application target. The target value is the UI.EXE file in your Virtual Machine for ClearPath MCP folder, which is usually C:\Program Files (x86)\unisys\virtual Machine for ClearPath MCP. 7 2 3843 4072 001
Troubleshooting Information 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. TCP/IP Drive Connection Problems Several minutes elapse while the Client Access Services software 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 EVLAN connection is operational, from a command-prompt window, enter ping cpmcp1. Note: cpmcp1 is the default MCP host name used in the Quick Install MCP image. A successful reply returns four responses from the MCP host. If you do not receive four responses, refer to the 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. 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 The Windows configuration of the EVLAN must match the information contained in the Core Network Services (CNS) and TCP/IP MCP initialization files, which supply information to the MCP. Verifying the Windows Configuration The first step is to verify the Windows networking configuration as follows: 1. On the Start menu, right-click Network, and then click Properties. The Network and Sharing Center window appears. 2. Verify that the computer and domain names are correct. 3. Click Manage network connections under Tasks in the left pane. 4. Right-click the adapter being used to connect to the public LAN, which is typically named Local Area Connection, and then click Properties. The <name of the adapter> Properties dialog box appears. 5. Select the Networking tab. 3843 4072 001 7 3
Troubleshooting Information 6. Select Internet Protocol Version 4 (TCP/IPv4) in the This connection uses the following items box and then click Properties. The Internet Protocol Version 4 (TCP/IPv4) dialog box appears. 7. Verify that the default IP address for the adapter has been set to the IP address appropriate to the site. Changes to this value must be reflected by changes to the MCP TCPIP Init file. The default IP address for the EVLAN adapter has been set to 192.168.16.2. This value should not be changed. Verifying that the Required Software Is Running If you are halt loading the MCP from the Quick Install MCP image without altering its settings, the MCP host name is cpmcp1 and 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. TCP/IP starts if it is not already active. 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 IP address 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:\Windows\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 Check the TCPIP init file and the CNS init file if pinging the MCP host through the EVLAN connection is still unsuccessful. 7 4 3843 4072 001
Troubleshooting Information Caution If the initialization 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, "Setting Up the Server"). 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 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, execute a halt/load command. You can now map a network drive using Windows Explorer. 3843 4072 001 7 5
Troubleshooting Information 7 6 3843 4072 001
Index A AcDevice.sys installing, 4-5 removing, 4-6 updating, 4-5 B BIOS setting up, 3-4 C caching fence, 4-11 changing partition computer name, 3-11 ClearPath Enterprise Server installation policy, 2-3 system architecture, 2-2 system overview, 2-1 configuring Dell Remote Access Controller (idrac6), 3-6 external storage subsystems, 4-1 Host Bus Adapters, 4-1 idrac6, 3-6 LSI Logic BIOS, 4-3 MCP, 3-19 multipath VSS disks, 4-20 persistent binding, 4-2 uninterruptible power supply (UPS), 3-23 Windows operating system, 3-9, 5-3 Windows Server 2008, 3-17 connecting external public LAN, 3-23 TCP/IP network drive, 3-22 Customer Response data to provide, 3-1 Hotline, 3-1 policy, 3-1 D Dell Remote Access Controller (idrac6) configuring, 3-6 diagnostic tools, 2-6 disk caching, 4-10 disk storage subsystems, 4-1 documentation, 2-5 Documentation updates, 1-1 E external storage subsystems configuring, 4-1 F Fibre Channel HBA, 4-1 FS1750 server, 1-2 G ground-zero reinstallation, 5-1 guidelines installation, 2-4 H HBA (See Host Bus Adapter), 4-1 Host Bus Adapters configuring, 4-1 I idrac6 configuring, 3-6 install 3843 4072 001 Index 1
Index unsigned drivers, 3-13 installation guidelines, 2-4 Microsoft agreement, 2-4 policy, 2-3 prerequisites, 2-4 site-specific information, 2-4 installation policy customer responsibility, 2-3 service representative responsibility, 2-3 installing AcDevice.sys, 4-5 MCP software, 3-15 Network Services software, 3-16 Virtual Machine for ClearPath MCP software, 3-15 Windows operating system, 3-7 L LAN connecting, 3-23 Libra 450 server, 1-2 logical disk creating, 3-18 LSI Logic BIOS configuring, 4-3 M MCP logical disk, 4-9 MCP Quick Install, 3-18 MCP software, 2-3 installing, 3-15 reinstalling, 5-3 media and books ClearPath Enterprise Server, 2-5 listing, 2-5 Virtual Machine for ClearPath MCP software, 2-5 multipath I/O, 4-12 multipath VSS disks configuring, 4-20 N NetBIOS enabling, 3-16 Network Services software installing, 3-16 P reinstalling, 5-4 partition computer name changing, 3-11 persistent binding configuring, 4-2 Q Quick Install program, 3-18 R reinstalling MCP software, 5-3 reinstalling software complete, 5-1 ground-zero, 5-1 partial, 5-2 removing AcDevice.sys, 4-6 required media Virtual Machine and MCP software, 2-5 S SCSI HBA, 4-3 setting up BIOS, 3-4 setup, 3-1 mechanical, 3-1 required media, 3-3 software, 3-2 software reinstallation, 5-1 complete, 5-1 ground-zero, 5-1 MCP software, 5-3 Network Services, 5-4 overview, 5-1 partial, 5-2 required media, 5-2 Windows operating system, 5-3 software tools, 2-6 System Editor, 2-6 Utility Partition System Utilities, 2-6 Windows Event Log Viewer, 2-6 Index 2 3843 4072 001
Index system architecture MCP software, 2-3 Virtual Machine for ClearPath MCP software, 2-2 Windows, 2-2 System Editor, 2-6 system features, 2-1 system setup, 3-1 T tape subsystems, 4-4 powering off, 4-7 TCP/IP drive connection problems, 7-3 TCP/IP network drive connecting, 3-22 troubleshooting Console for MCP icon does not initialize, 7-2 Console for MCP icon is not working, 7-2 Network Services software setup program does not complete, 7-2 NP210 is active and communicating, 7-3 NP210 is not present, 7-3 system startup, 7-1 TCP/IP drive connection, 7-3 U updating AcDevice.sys, 4-5 UPS (uninterruptible power supply), 3-23 Utility Partition System Utilities, 2-6 V Virtual Machine for ClearPath MCP software, 2-2 installing, 3-15 Virtual Sector Size disks (See VSS disks), 4-8 VMMCPDevices, 4-4 VSS disks, 4-8 W Windows event log viewer, 2-6 Windows operating system configuring, 3-9 installing, 3-7 reinstalling, 5-3 Windows Server 2008 configuring, 3-17 reinstalling, 5-3 Windows tools for ClearPath MCP setting up, 3-22 uninterruptible power supply (UPS), 3-23 3843 4072 001 Index 3
Index Index 4 3843 4072 001
.
2011 Unisys Corporation. All rights reserved. *38434072-001* 3843 4072 001