unisys ClearPath Enterprise Servers Network Services Implementation Guide ClearPath MCP 15.0 April

Transcription

1 unisys ClearPath Enterprise Servers Network Services Implementation Guide ClearPath MCP 15.0 April

2 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.

3 Contents Section 1. Introduction Documentation Updates What s New? Supported Servers What Is Network Services? Support for Shared Adapters Installation and Configuration Interfaces ClearPath Server Descriptions ClearPath Server Groups ClearPath Server Illustrations and Descriptions ClearPath VMMCP Servers ClearPath Libra 4000 Servers ClearPath Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 Servers, and FS1800 Server Network Components Network Component Descriptions Making the Connection Section 2. Installing Network Services Upgrading Network Services to Run a Later Version of Windows Overview of Network Services Installation Installation Process Preparing to Install Network Services Before You Begin Functions of the Installation Interface Configuring Network Services on a Partitionable Server Gathering Values for Installation Preparing for Shared Adapters Preparing the NICs Preparing to Use Fast Ethernet Port Aggregation Preparing to Use Ethernet Jumbo Frames Preparing to Use IEEE 802.1Q VLANS Preparing to Use Quality of Service over LAN Shared Adapter Properties Installing Network Services Software Installing Network Services on Libra Series Native MCP and FS1800 Servers iii

4 Contents Installing Network Services on Virtual Machine for ClearPath MCP (VMMCP) Servers Sample ADAPTERS.TXT File Completing Installation of Network Services (Virtual Machines with Multiple NPs) Viewing Network Services Properties on Virtual Machine for ClearPath MCP Servers How the Setup Program Manages the LMHOSTS File Bringing Network Services Into Service Verifying Network Services Installation Verifying Shared Adapter Installation Reconfiguring Network Services Reconfiguring Network Services on a Partitionable Server Reconfiguring a Shared Adapter with Network Services Setup Reconfiguring a Shared Adapter with Network Connections Properties Replacing a Shared Adapter or Updating an Adapter Driver Removing Network Services from the Windows Server Remotely Upgrading Network Services on a Windows Server or CNA Device Initiating a Remote Upgrade Reinstalling Network Services Restoring a Previous Release of Network Services Section 3. Configuring Libra Series Native MCP or FS1800 Server Networks Configuring a TCP/IP Network Choosing a Name Resolution Strategy Preventing Private IP Addresses from Being Sent to the WINS Server Configuring Each Unit Updating the MCP Network Configuration MCP Networking Values for Libra Series Native MCP and FS1800 Servers Using Sample CNS and TCP/IP Initialization Files Using Sample Heritage Network Services (BNA) Initialization Files Determining Fast Ethernet and Gigabit Ethernet Information Configuring with the NAU Updating Maintenance LAN IP Addresses Procedure for Changing Windows Server and ODW Maintenance IP Addresses Updating Windows Server Environment Values Configuring Windows Servers Updating ODW and User Workstation Values iv

5 Contents Examining or Updating Network Services Values Manually Directing Windows Data to the MCP Environment Directing Data through the EVLAN Data Path Directing Data Through the Ethernet Switch Data Path Directing MCP Data to the Windows Environment Specifying the WINS Server Address Rebooting the System Environments Verifying the System Networking Configuration Controlling the Maximum Transmission Unit (MTU) Value Viewing the RESET Reports Section 4. Configuring Virtual Machine for MCP Server Networks Choosing a Name Resolution Strategy Preventing Private IP Addresses from Being Sent to the WINS Server Configuring Each Unit Updating the MCP Network Configuration Using Sample CNS and TCP/IP Initialization Files Using Sample BNA Initialization Files Examining or Updating Network Services Values Manually Directing Windows Data to the MCP Environment Directing Data through the EVLAN Data Path Directing Data through the Externally Configured LAN Directing MCP Data to the Windows Environment Specifying the WINS Server Address Rebooting the System Environments Verifying the System Networking Configuration Controlling the Maximum Transmission Unit (MTU) Value Viewing the RESET Reports Section 5. Other Configuration Procedures Integrating Your Server with an Existing BNA Network Libra Series Native MCP Servers, and FS1800 Servers VMMCP Servers Integrating Your Server with Microsoft Networks Enabling Workstations to Browse the MCP Server Assigning Units to a Workgroup or Domain Optimizing MCP Networking Optimizing Network Services for the Enhanced VLAN (EVLAN) Section 6. Operations Operating Tasks v

6 Contents HMP FastPath CIA Bringing Network Services Into Service Reinitializing Network Services Removing Network Services Stopping and Starting the Windows Server Initiating a Dump Recovering the Windows Event Logs Recovering the Windows Event Logs Manually Viewing Shared Adapter Information Submitting Trouble Reports MCP Operations Interface Summary Data Types Attributes for EVLAN and Shared Adapters Networking Commands and Inquiries System Commands and Inquiries Reports Section 7. Troubleshooting Troubleshooting Network Services Software Appendix A. Building Network Initialization Files Preconfigured CNS and TCP/IP Initialization Files... A 2 CNS and TCP/IP Initialization Files - VMMCP Servers... A 2 CNS and TCP/IP Initialization Files - Libra Model 680 and 690 Servers... A 2 CNS and TCP/IP Initialization Files - Libra 4000 Servers... A 2 Preconfigured SNMP Initialization File... A 3 Using NAU Network Version Dump Files... A 4 Guidelines for Building CNS Initialization Files... A 5 Guidelines for Building TCP/IP Initialization Files... A 7 Guidelines for Building BNA Initialization Files... A 9 SNMP Initialization File... A 10 Appendix B. Network Services File Summary Index... 1 vi

7 Figures 1 1. Typical ClearPath VMMCP Server Network Connections Typical ClearPath Libra 4000 Server Network Connections Typical ClearPath Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 Servers, and FS1800 Server Network Components Sample ADAPTERS.TXT File vii

8 Figures viii

9 Tables 1 1. IP Addresses for SAS-IOP and FC3-IOP on Libra Models 680 and IP Addresses for SCSI Appliance and Crypto Co-Processor (CCP) on Libra Models 680 and Network Component Descriptions Basic Network Services Configuration Values for VMMCP Servers Basic Network Services Configuration Values for Libra 4000 Servers Basic Network Services Configuration Values for Libra Series Native MCP and FS1800 Servers Shared Adapter Properties Name Resolution Strategies MCP Networking Values for Libra Series Native MCP and FS1800 Servers Maintenance LAN IP Addresses for Libra Series Native MCP and FS1800 Series Servers Windows Environment Values for Libra Series Native MCP and FS1800 Servers Name Resolution Strategies MCP Networking Values for VMMCP Servers MCP Networking Values for Libra 4000 Servers Troubleshooting Network Services B 1. Network Services File Summary... B ix

10 Tables x

11 Section 1 Introduction The purpose of this guide is to describe the network architecture for ClearPath MCP servers. This guide provides necessary information for configuring and troubleshooting your ClearPath MCP network as well as understanding and operating Network Services. Documentation Updates This document contains all the information that was available at the time of publication. Changes identified after release of this document are included in problem list entry (PLE) To obtain a copy of the PLE, contact your Unisys representative or access the current PLE from the Unisys Product Support Web site: Note: If you are not logged into the Product Support site, you will be asked to do so. What s New? New or Revised Information Location Updated the Supported Servers list. Section 1: Introduction Added information about the *FACTORY value of the LocalAddress (LA). Section 6: Attributes for EVLAN and Shared Adapters Supported Servers The purpose of this guide is to describe the network architecture for the following ClearPath MCP servers: Libra Series native MCP servers, which include the following: Libra Model 680 and 690 servers Libra Model 750, 780, and 790 servers Libra Model 880, and 890 servers Libra 4100 and FS4100 servers, which include Libra Models 4180/4190 and FS4180 and FS4190 servers

12 Introduction Note: See the Libra 4100/FS4100 Server System Implementation Guide for Network Services information for Libra 4100 and FS4100 servers. Libra 4200 and FS4200 servers, which include Libra Model 4280/4290 and FS4280 and FS4290 servers. Note: See the Libra 4200 Server System Implementation Guide for Network Services information for Libra 4200 servers or the FS4200 Server System Implementation Guide for Network Services information for FS4200 servers. Libra 6200 and FS6200 servers, which include Libra Model 6280/6290 and FS6280 and FS6290 servers. Note: See the Libra 6200 Server System Implementation Guide for Network Services information for Libra 6200 servers or the FS6200 Server System Implementation Guide for Network Services information for Libra 6200 servers. VSE 412 servers Note: See the VoiceSource Express 412 (VSE 412) Server System Implementation Guide for Network Services information for VSE 412 servers. FS1800 servers Virtual Machine for MCP (VMMCP) servers, which include the following: LX 180 Libra Model 400 Libra Model 450 Libra Model 460 Libra Model 4080 and 4090 FS1700 SP1760 This guide also provides the following information: Describes the Enhanced Virtual LAN (EVLAN) Network Services and the various Shared Adapter Network Services software products. Describes how to install and configure EVLAN Network Services and Shared Adapter Network Services software. Provides the information that you need to integrate a ClearPath server into an existing TCP/IP or Heritage Network Services (BNA) network. Provides operating information for network processors (NPs) in the MCP environment. Provides troubleshooting information

13 Introduction Terminology Conventions In this guide, the term ClearPath MCP servers refers to ClearPath Libra Series servers, and FS Series servers. To simplify fully inclusive references, the term Windows is used throughout this guide to refer to supported versions of the Windows operating system. What Is Network Services? Network Services (NNS) provides a set of software services that enhance the utilization of the Windows environment in a ClearPath MCP server. These include A fast local Enhanced Virtual LAN (EVLAN) network connection between the MCP and Windows server environments. Shared adapter services which enable TCP/IP and Heritage Network Services (BNA) network providers in the MCP environment to establish network connections using a particular type of commercial network interface card (NIC) adapter hardware in the Windows environment. In other words, the MCP can share adapters with the Windows environment. Since NNS runs in both the Windows and the MCP environments of the ClearPath server, services and resources can be located in the environment that is most appropriate for the task being performed. NNS has two standard components. Enhanced Virtual LAN (EVLAN) Network Services Provides a fast and secure virtual LAN data path between the MCP and Windows environments of ClearPath servers. Communication across the EVLAN is via the TCP/IP protocol. No changes are required to the applications and services in either processing environment to use EVLAN. Note: On VMMCP servers, NNS software runs only in the MCP server. It provides communication between the emulated MCP environment and the underlying Windows environment. It also provides shared adapter support to enable the MCP server to access network interface cards (NICs) in the Windows I/O complex. Shared Adapter Network Services Enables the MCP to use a qualified Gigabit Ethernet NIC located in the Windows environment. This service supports MCP network connections through a Gigabit Ethernet copper (10/100/1000 Mbps) NIC or Gigabit Ethernet fiber (1000 Mbps only) NIC. In the MCP environment, both the TCP/IP and BNA network providers can use this connection. Support for Shared Adapters Shared adapters provide high performance and fast transaction speeds the Fast Ethernet NIC operates at 10/100 megabits per second and the Gigabit Ethernet NIC operates at up to 1000 megabits per second

14 Introduction While shared adapter software services allow connection to networks comprised of high-performance technologies, the actual data transfer rate may be less than the potential maximum for that network technology. For example, a shared Gigabit Ethernet adapter allows the MCP server to participate on a Gigabit Ethernet backbone, but it does not allow the MCP to transfer data at the maximum Gigabit Ethernet transfer rate on all platforms. Network Services supports up to eight shared adapter connections (where a connection is either a Fast Ethernet port or a Gigabit Ethernet port) per Network Processor instance. Network Services can be enabled for each of the connection types listed to allow MCP network access. Windows TCP/IP can remain enabled for the connection or be disabled. This results in the following connection categories: Exclusive to Windows TCP/IP (Windows TCP/IP enabled, Network Services disabled) Exclusive to the MCP environment (Windows TCP/IP disabled, Network Services enabled) Shared by both environments (Windows TCP/IP enabled, Network Services enabled) Note: Libra 4000, 4100, 4200, 6200 servers do not support the shared by both environments connection type. See Making the Connection later in this section for information on how Network Services connections are made in the various ClearPath servers. Heritage Network Services Support (BNA) Because a Network Services shared adapter appears as a line of an integrated communications processor (ICP) to the MCP environment, BNA services have full access to the Fast Ethernet or Gigabit Ethernet adapter. BNA support does not include CPDLAN terminal connectivity. Note: Fast Ethernet and Gigabit Ethernet shared adapter software is part of the integrated operating environment. Installation and Configuration Interfaces The Network Services installation interface operates in the Windows environment. The ClearPath network administrator installs and configures Network Services using the following: In the Windows Environment The Network Services Setup program The Windows Network Control Panel Applet

15 Introduction In the MCP Environment The Simple Installation program, which supports installation of the required firmware files for Network Services. The Network Administrative Utility (NAU), or a file editing program such as CANDE. Generally, only one of these methods is used to configure TCP/IP and EVLAN connections. Use the NAU to create new (or edit existing) CNS and TCP/IP initialization files for this ClearPath server complex. These files define all TCP/IP, Network Services EVLAN, and Network Services Shared Adapter connections. The NAU can also be used to create and edit BNA initialization files. Use an editor such as CANDE to make necessary modifications to sample CNS and TCP/IP initialization files that are provided with the ClearPath server. Refer to Appendix A for a description of these sample initialization files. After Network Services is installed on the Windows environment: Unisys Network Services appears as an installed service in the Components list of the Network and Dial-up Connections applet (Windows Control Panel). Unisys Network Services EVLAN Adapter appears as an installed adapter in the Local Area Connections list of the Network and Dial-up Connections applet (Windows Control Panel). This is the interface that the TCP/IP protocol uses to communicate between the Windows and MCP environments. ClearPath Server Descriptions This section provides illustrations and descriptions of the various groups of ClearPath servers or, in some cases, specific server models. For a detailed description of the components supported on the various ClearPath servers, see Table 1-3, Network Component Descriptions, later in this section. ClearPath Server Groups The ClearPath servers are grouped according to how they operate with the Network Services software. The groups are as follows: The Libra Series native MCP Series group includes the Libra Model 680 and 690, Libra Model 750, 780, and 790, and Libra Model 880 and 890 servers. The FS1800 servers are also included in this group. The VMMCP group includes the FS1700 servers, the SP1760 Servers, the Libra Model 400 servers, and Libra 4000 servers

16 Introduction ClearPath Server Illustrations and Descriptions The following figures illustrate the components of each ClearPath server group or server model and also describe how the various ClearPath servers can be configured within an external network. Figure 1 1 shows networking components and connections in the VMMCP group of servers. Figure 1 2 shows networking components and connections in Libra 4000 servers. Figure 1 3 shows networking components and connections in the Libra Model 680 and 690 servers, Libra Model 750, 780, and 790, Libra Model 880 and 890 servers, and FS1800 servers. ClearPath VMMCP Servers Figure 1 1 illustrates Fast Ethernet and Gigabit Ethernet network components and connections with ClearPath VMMCP servers (ClearPath LX 180, Libra Model 400, 450 and 460, FS1700, SP1760, and Libra4000 servers). There is one Windows server in these servers. These servers can run the Windows Server 2008 or Windows Server 2008R2, Enterprise Edition operating system. The Windows server based NICs serve as the primary data communications paths for the server. These servers support shared adapter connections over Fast Ethernet and Gigabit Ethernet. Figure 1 2 illustrates Gigabit Ethernet network components and connections with the Libra 4000 servers with one Windows server. MAICP4 Links One or more emulated MAICP4 links provide a path for high-speed data transfers between the virtual MCP and Windows environments. The first MAICP4 supports an enhanced virtual LAN (EVLAN) connection. The EVLAN is a high performance network for TCP/IP transfers between the MCP and Windows environments. The first and all additional MAICP4 links support up to eight shared adapter connections. This connection allows the MCP environment to access a NIC within the Windows server. The shared adapter supports TCP/IP transfers to or from the Windows environment BNA and TCP/IP transfers to or from the MCP environment

17 Introduction Figure 1 1. Typical ClearPath VMMCP Server Network Connections

18 Introduction ClearPath Libra 4000 Servers Figure 1 2 illustrates network components and connections to ClearPath Libra 4000 Servers (Libra Model 4080 and 4090 servers). Figure 1 2. Typical ClearPath Libra 4000 Server Network Connections ClearPath Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 Servers, and FS1800 Server Network Components The ClearPath Libra Model 680 and 690, Libra Model 750, 780 and 790, Libra Model 880 and 890 servers, and FS1800 server (Figure 1 3) are enterprise-class servers that are based on the architecture of the Unisys ES7000 Model 600 system. The Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 servers, and FS1800 servers utilize the ES7000 Cellular multiprocessing (CMP) high-performance memory architecture, scalable crossbar intraconnect, and high-capacity peripheral component interconnect (PCI) I/O subsystem. The Libra Model 680 and 690 servers: Offer a cost-effective four- processor, rack-mounted module Offer standard configurations of from one to four modules per partition Offer support for multiple operating environments within a single cabinet The Libra Model 680 and 690 servers include proprietary components required for operation in the MCP operating system environment. In addition to the MCP

19 Introduction environment, the Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 servers, and FS1800 servers support simultaneous operations of the following multiple open operating system environments in a single cabinet: MCP Virtual Machine (MCPvm) Windows Linux MCP Partitions In order for a Libra 680/690 server to run in an MCP operating environment and support basic system operations, a partition consisting of the following minimum components is required: Module, which contains: Processor Memory Module (PM Module) with four MCP style instruction processors and up to 32 gigabytes (GB) of memory Input/Output Module (I/O Module) with up to nine Fibre Channel Input/Output Processor (FC3-IOP) boards Integrated Peripheral Module (IPM) with three hard disk drives and one CD/DVD drive Service Processor, an independently powered separate computer installed in the rack. It is controlled by Server Sentinel software and monitors the hardware components for state changes, faults, and other events. It also executes operator commands and controls the configuration and initialization of the system, and controls power to various units. Secure Maintenance Device (Sonic Wall), which provides a secure path for remote support of the system. It is a 1U rack-mounted device that houses the following components: Firewall device Maintenance (private) LAN Power for the firewall device and the LAN Optional Components A Libra Model 680 or 690 or 750 or 780 or 790 or 880 or 890 or FS1800 partition might also contain the following optional components: SCSI Tape Appliance, which is used for the migration of tape devices Crypto Co-processor, which provides a secure channel for cryptography functions Non-MCP Partitions In order for a Libra Model 680 or 690 or 750 or 780 or 790 or 880 or 890 or FS1800 to run in the MCPvm, Windows, or Linux operating environments, a partition consisting of the following minimum components is required: Module containing:

20 Introduction Processor Memory Module with four Intel instruction processors and from 2 GB to 64 GB of main memory I/O Module with up to nine Peripheral Control Interface (PCI) card slots Integrated Peripheral Module with three hard disk drives and one CD/DVD drive I/O Subsystem The input/output subsystem includes the following: Internal I/O module which is used in the entry level one module and two module system configurations Fibre Channel peripheral component interconnect (PCI) adapters SAS-IOP (Serial attached SCSI Input Output Processor) which supports one Gigabit Ethernet port and four internal and external serial attached SCSI (SAS) ports FC3-IOP (Fibre Channel Input Output Processor) which provides one Gigabit Ethernet port connection and two Fibre Channel port connections External I/O module which is used in the high-end two module and four module system configurations Figure 1 3 shows the typical network components of the Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 servers, and FS1800 server. Table 1-1 shows the IP address allocations for the SAS-IOP cards and FC3-IOP cards in a two module Libra 680/690 configuration. Table 1-2 shows the IP address allocations for the SCSI appliance and Crypto Co-Processor (CCP) devices. If you want to use either more or less connectivity with your configuration, you will have to adjust the number of devices to match the connectivity you want

21 This image cannot currently be displayed. Introduction Figure 1 3. Typical ClearPath Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 Servers, and FS1800 Server Network Components

22 Introduction Table 1 1. IP Addresses for SAS-IOP and FC3-IOP on Libra Models 680 and 690 SAS-IOP or FC3-IOP NP ID MCP Private LAN IP Address MCP Public IP Address SAS-IOP Line ID 1: FC3-IOP Line ID 1: /24 FC3-IOP Line ID 1 VLAN 2 : /26 Line ID 1 VLAN 3 : /26 Line ID 1 VLAN 4 : /26 Line ID 1 VLAN 5 : /26 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 SAS-IOP Line ID 1: FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 VLAN 2 : /26 Line ID 1 VLAN 3 : /26 Line ID 1 VLAN 4 : /26 Line ID 1 VLAN 5 : /26 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /24 FC3-IOP Line ID 1 : /

23 Introduction Table 1 2. IP Addresses for SCSI Appliance and Crypto Co-Processor (CCP) on Libra Models 680 and 690 SCSI App./ CCP Device ID NP ID Private LAN IP Address MCP Public IP Address LineID=1 SCSI Appliance EVLAN IP Address MCP EVLAN Address LineID=0 SCSI Appliance 1 SCSI Appliance 2 SCSI Appliance 3 SCSI Appliance 4 SCSI Appliance 5 SCSI Appliance 6 SCSI Appliance 7 SCSI Appliance CCP CCP CCP CCP CCP CCP CCP CCP

24 Introduction Network Component Descriptions Table 1-3 describes the networking components illustrated in Figures 1-1 through 1-8. Note: Unless otherwise specified, Libra Native MCP Series in the last column refers to the Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 servers, and FS1800 server. Table 1 3. Network Component Descriptions Server Applicability Component / Description Ethernet switch The component that routes traffic through the system LAN. It provides 10/100/1000 (Gigabit Ethernet) connections to each Native MCP Series Server, Windows server, and to the external LAN. The Fast Ethernet switch is supported on all Libra MCP Series servers except the Libra Native Model servers. The Native Models 680 and 690 servers are exclusively Gigabit Ethernet servers. The Ethernet switch is external to the system and must be supplied by the user. On servers without an Ethernet switch, the MCP and Windows servers must be connected through LAN equipment outside of the server. The Ethernet switch is transport independent. It can handle BNA traffic as well as TCP/IP. For BNA traffic, the Ethernet switch imposes some restrictions on frame size. Libra Models 400, 450, SPxx, and FS1700 Libra Native MCP Series and FS

25 Introduction Table 1 3. Network Component Descriptions Server Applicability Component / Description Maintenance hub This special purpose hub provides dedicated Ethernet connections between the following components as appropriate: Each Service Processor Each MCP power domain Each Windows server Each operating system partition (through its Console Manager card) A network of one or more external workstations or operator display workstations This hub provides a secure communications path for system control and maintenance traffic. This traffic is completely isolated from the high-speed system LAN. In a redundant environment, a second maintenance hub is also provided. MCP server The component of ClearPath servers that runs the MCP operating system. The MCP server runs enterprise server solutions, such as the Enterprise Database Server, and also provides services to other environments within the ClearPath server. Windows server The component of ClearPath servers that runs a version of the Windows operating system. Virtual central processor module (CPM) The server component that provides a virtual (soft) MCP environment. Libra Models 400, 450, SPxx, and FS1700 Libra Native MCP Series and FS

26 Introduction Table 1 3. Network Component Descriptions Server Applicability Component / Description MAICP4 emulation A high-speed data path between the virtual MCP and Windows environments. The ClearPath Network Services software uses this dedicated connection to provide fast and secure communications between applications residing on the two environments. This is an in the box channel that requires no network hardware. Instead, data is transferred using an advanced memory sharing technology. System control processor (SCP) A processor in the system control subsystem that controls maintenance functions for the server complex. This processor runs a SYCON application on the SVR4 or UnixWare operating system. The SCP maintains a Peripheral Control Diagram (PCD). All network processors must be defined in the PCD. A second SCP may be configured for redundancy. Console for MCP A server component that provides a virtual system console environment. The Console for MCP provides a System Editor to support dynamic configuration of the system. Operator display workstation (ODW) An optional, remote workstation that provides interfaces for managing the MCP and other operating environments of ClearPath servers. Each MCP or Windows server includes a Console Manager card that exports monitoring and control functions (that is, the required keyboard, video, and mouse connection) to any Windows based workstation that includes a compatible browser. The Service Processor also includes software that can be controlled and monitored from a remote workstation. See the Service Processor description later in this table for additional information. Libra Models 400, 450, SPxx, and FS1700 Libra Native MCP Series and FS

27 Introduction Table 1 3. Network Component Descriptions Server Applicability Component / Description Fast Ethernet (or Ethernet) NIC A device that provides a 10-Mbps (10BaseT) or 100-Mbps (100BaseT) connection to/from the Windows server. Based on the remote connection, this device automatically determines the required transfer rate. In LX7100 servers, there is normally one Fast Ethernet NIC in each Windows server. In the CS7201, Libra Model 520, and FS1400 servers, there is normally one Fast Ethernet NIC in each configured MCP and Windows server. In all ClearPath MCP servers, the Network Services shared adapter service enables the MCP server to share access to the Fast Ethernet NIC. In Libra Model 180 Windows partitions, one Fast Ethernet NIC provides a connection to the maintenance hub and a second optional Fast Ethernet NIC provides a 100-Mbps connection to the system LAN or to an external LAN. In Libra Model 185 servers, the Fast Ethernet NIC is part of the ClearPath Network Appliance (CNA) device. Note: Libra 4000 servers do not support a Fast Ethernet (or Ethernet) NIC. Libra Models 400, 450, SPxx, and FS1700 Libra Native MCP Series and FS

28 Introduction Table 1 3. Network Component Descriptions Server Applicability Component / Description Gigabit Ethernet NIC A PCI-based device in the Windows environment that provides a 1000-Mbps connection between the Windows server and an external Gigabit Ethernet switch. If the appropriate Network Services Shared Adapter service is configured, the MCP server has access to the Gigabit Ethernet NIC. The Libra Models 680 and 690 servers are exclusively Gigabit Ethernet systems. In Libra 4000 servers, the copper Gigabit Ethernet NIC allows a connection at 10, 100, or 1000 Mbps. On Libra Model 680 or 690 servers, the copper Gigabit Ethernet NIC allows a connection only at 1000 Mbps. Service Processor A computer that controls the Libra native MCP Series central electronics complex (CEC) hardware. The Service Processor runs the Integrated Maintenance System, which controls and continuously monitors the hardware. The Service Processor also runs other software that supports system operations, administration, and management. Console Manager A peripheral component interconnect (PCI) card with embedded software, including a Web server. This card enables one or more remote workstations to communicate with and control a particular Libra Series partition (either MCP server or Windows partition) by directing the console function to a browser-based window at the remote workstation. A Console Manager client program must be downloaded from the Console Manager card to each applicable remote workstation. One Console Manager card is needed for each partition. Libra Models 400, 450, SPxx, and FS1700 Libra Native MCP Series and FS

29 Introduction Table 1 3. Network Component Descriptions Server Applicability SAS-IOP Component / Description Supports one Gigabit Ethernet port and four internal and external serial attached SCSI (SAS) ports. The Gigabit Ethernet port provides the interface to the ODT. One internal SAS connector is used to provide the path to the integrated Peripheral Module that contains the disk and DVD drives. In a Libra Model 680 or 690 server configuration, the connections are only capable of running Gigabit Ethernet. There is no capability to drop down to lower speeds (10 Mbps or 100 Mbps). FC3-IOP Provides one Gigabit Ethernet port connection and two Fibre Channel port connections. The Gigabit Ethernet port provides external networking and ODT support. The Fibre Channel ports provide the interface to external I/O devices. In a Libra Model 680 or 690 server configuration, the connections are only capable of running Gigabit Ethernet. There is no capability to drop down to lower speeds (10 Mbps or 100 Mbps). SCSI Tape Appliance The SCSI tape appliance is a 1U device that supports the migration of SCSI tape devices. It connects to an I/O storage port in the MCP module. The SCSI tape appliance has 3 SCSI ports, each supporting 4 SCSI tape devices. Available for SCSI tape attachment only; all disk attachment is via an optical Fibre Channel connection. Crypto Co-processor (CCP) Provides cryptography services; each module supports a maximum of 2 CCPs. Libra Models 400, 450, SPxx, and FS1700 Libra Native MCP Series and FS

30 Introduction Making the Connection ClearPath Network Services offers a dedicated TCP/IP communications path to the MCP and Windows environments. It also provides a BNA communications path to the MCP environment. The following paragraphs describe how connections are made in the various ClearPath servers. Libra Native MCP Series and FS1800 Servers The MCP I/O subsystem on the Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 servers, and FS1800 servers support the peripheral devices. In addition, the MCP I/O subsystem features high performance Fibre Channel Interconnect for communication between MCP and Windows partitions and between the MCP and the ClearPath Appliance (CNA). High performance Fibre Channel cards provide ports for connecting external networking and storage devices. Figure 1 3 illustrates the network components within the ClearPath Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890, and FS1800 server environment. VMMCP Servers Note: For VMMCP servers, client use of the Windows environment supporting the virtual MCP is not recommended. Instead, one or more Windows environments are provided in separate operating system partitions. EVLAN and Shared Adapter software is not provided in these separate Windows environments. A virtual MCP environment (consisting of one to twelve CPMs) runs within the Windows processing complex. The MCP and Windows environments exchange data through a high-speed EVLAN adapter over an emulated MAICP4 device. No network hardware is required. All VMMCP servers include a license for Fast Ethernet or Gigabit Ethernet Network Services Shared Adapter connections. Network Services SA supports a maximum of eight shared adapter connections for each NP instance, where a connection is either a Fast Ethernet port or a Gigabit Ethernet port. With each shared connection: Either processing environment can own the high-speed connection, or it can be shared by both environments. Libra 4000 servers do not allow adapters to be shared between the Windows TCP/IP stack and the MCP TCP/IP stack. TCP/IP is supported to and from either processing environment BNA is supported to and from the MCP environment

31 Section 2 Installing Network Services This section provides the information required to install, configure, and verify Network Services software in the following ClearPath servers: Libra Series native MCP servers (Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890, and FS1800 servers). VMMCP servers (LX 180, Libra, Libra Model 400, Libra Model 450, Libra Model 460, Libra Model 4080 and 4090, FS1700, and SP1760 servers) This section consists of the following parts: Upgrading Network Services to Run a Later Version of Windows Overview of Network Services Installation Preparing to Install Network Services Installing Network Services Software Reconfiguring Network Services Removing Network Services from the Windows Server Remotely Upgrading Network Services on a Windows Server or CNA Device Reinstalling Network Services Restoring a Previous Release of Network Services Upgrading Network Services to Run a Later Version of Windows If you plan to upgrade your ClearPath MCP system to run a later version of Windows, proceed as follows to ensure that Network Services will operate properly in the new Windows environment: 1. Uninstall Network Services using the procedure Removing Network Services from the Windows Server later in this section. 2. Upgrade to the new version of Windows. 3. Run Network Services Setup. See Installing Network Services Software later in this section. Overview of Network Services Installation

32 Installing Network Services Prerequisites When you initially receive your ClearPath MCP server complex, a standalone internal networking environment has been established using these preconfigured initialization files: CLEARPATH/INIT/CNS CLEARPATH/INIT/TCPIP However, you will probably want to integrate your ClearPath server within your existing network. The following process describes the general steps required to install Network Services and configure your ClearPath server to operate within your network environment. The following conditions must be satisfied before you can configure Network Services and integrate your ClearPath server into a network: The Windows and MCP software environments must be installed and ready for use. Any Fast Ethernet adapter or Gigabit Ethernet adapter to be shared must be configured in the Windows environment. Installation Process 1. Determine your initial networking requirement: Will your ClearPath server act as a freestanding system (no LAN connection)? If your answer is yes, go to step 3. Will your ClearPath server be connected to an existing local LAN? - or - Will you be configuring multiple ClearPath servers on a common LAN? If your answer to either question is yes, assign unique private IP addresses where necessary to resolve all duplicated IP addresses. Record your new server complex IP addresses in applicable environment variable tables within this guide: For Libra native MCP servers use Tables 3 3, 3 4, and 3 5. For VMMCP servers use Table 4 2. For Libra 4000 servers use Table

33 Installing Network Services Will your ClearPath server be connected to the Internet? If your answer is yes, contact an Internet registry and obtain public IP addresses for the MCP server(s) and Windows server(s). Record these new IP addresses in applicable environment variable tables within this guide: For Libra native MCP servers, use Tables 3 3, 3 4, and 3 5. For VMMCP servers use Table 4 2. For Libra 4000 servers use Table Will you be using shared adapters? If your answer is yes, see Preparing for Shared Adapters later in this section. 3. Install or reinstall Network Services. For details, see Installing Network Services Software later in this section. 4. Start Network Services. For details, see Bringing Network Services Into Service for the First Time later in this section. 5. Will you be using shared adapters? -or- Did you assign new MCP server IP addresses in step 1? -or- Do you plan to run BNA? If the answer to any of these questions is yes, configure your MCP environment for operation within the external TCP/IP (and BNA, if applicable) network. This can be done in two ways: Use the Network Administration Utility (NAU) to generate CNS, TCP/IP, and BNA initialization files. Refer to "Updating the MCP Configuration" in Section 3 (for Libra native MCP or FS1800 servers) or Section 4 (for VMMCP servers). Use CANDE or some other editor to edit the sample CNS, TCP/IP, and BNA initialization files provided with your server. Refer to Appendix A for information on these files. 6. After your CNS and TCP/IP initialization files are complete, initiate the new CNS and TCP/IP environment. 7. Verify proper operation of the EVLAN. For details, see Verifying Network Services Installation later in this section. If you are configuring a freestanding ClearPath server (no external LAN connection), installation is complete. No additional steps are required

34 Installing Network Services 8. Did you assign new Windows server IP addresses in step 1? If your answer is yes, configure applicable Windows servers as defined in "Updating Windows Server Environment Values" in Section 3 or Did you assign new maintenance LAN IP addresses in step 1? (Applicable for Libra Series native MCP, and FS1800 servers) If your answer is yes, reconfigure the maintenance LAN as defined in Updating Maintenance LAN IP Addresses in Section Did you assign new ODW IP addresses in step 1? (Applicable for Libra Series native MCP, and FS1800 servers) If your answer is yes, reconfigure installed ODWs as defined in Updating ODW and User Workstation Values in Section If applicable, verify proper operation of each shared adapter. For details, see Verifying Network Services Shared Adapter Installation later in this section. 12. If required, configure server components to operate in an SNMP environment. For details, refer to the online help provided with the Server Sentinel software product. Preparing to Install Network Services This subsection describes the steps you take to install Network Services. It includes these topics: Functions of the installation interface Configuring Network Services on a partitionable server Gathering values for installation Preparing for Shared Adapters Network Services may have already been installed on your ClearPath server. If this is the case, see Examining or Updating Network Services Values" in Section 3 (for Libra Series native MCP or FS1800 servers) or Section 4 (LX 180, Libra Model 400, Libra Model 450, Libra Model 460, Libra Model 4080 and 4090, FS1700, and SP1760 servers) for information about modifying the preconfigured Network Services values

35 Installing Network Services Before You Begin Certain tasks must be completed prior to installing Network Services. Libra Models 400 and FS1700 Servers The MCP environment and Windows operating system must be installed and configured. Your Unisys service representative performed these tasks when your equipment arrived on site. Libra 4000 Servers The MCP environment and Windows operating system must be installed and configured. Consult the documentation for your server. Libra Series Native MCP and FS1800 Servers If you choose to install an EVLAN interconnect between the MCP environment and the Windows environment, the Fibre Channel I/O Processor (FC-IOP) and associated cable must be installed and configured in your MCP and Windows environments. This includes: Defining the FC-IOP in the Libra server partition profile Attaching the cable between the MCP and Windows partitions After Network Services is installed, the MCP IO-CD should be installed in order to update the FC-IOP firmware. Functions of the Installation Interface As the ClearPath server administrator, you will use a Setup program accessible from the Windows Server installation interface to install and configure the Network Services software components. The installation interface allows you to: Install Network Services software on the drive where Windows is installed. Provide the MCP server with access to a Fast Ethernet adapter or Gigabit Ethernet adapter. Accept device configuration values and store them in the Windows registry. Create Network Services, register its drivers with Windows, and allow necessary driver bindings to occur. Configure Windows to use the enhanced virtual LAN (EVLAN) data path to the MCP host. Update Network Services configuration information. Remove Network Services and drivers from the server

36 Installing Network Services Configuring Network Services on a Partitionable Server Note: LX7100, Libra Model 300, Libra Model 400, and Libra 4000 servers are not partitionable. If you have a partitionable ClearPath MCP server that has been split into two partitions, with each partition running independently, you need to gather values and run the Setup program for each Network Services environment. If, after installing Network Services, you change the MCP environments by splitting or joining partitions, you need to update the MCP host name information in both the Windows and MCP environments. See Reconfiguring Network Services on a Partitionable Server later in this section for additional information. Gathering Values for Installation The Setup program requests information about Network Services. Table 2 1 provides installation information for Windows servers within VMMCP servers (LX7100, Libra Model 400, CS7201, and FS1100, FS1300, FS1400, and FS1700 servers). Table 2 2 provides installation information for Windows servers within Libra 4000 servers. Table 2 3 provides installation information for Windows servers within Libra Series native MCP servers, and FS1800 servers. Each table provides: Information that you need for the installation A reference to the step in the Installing Network Services on the Windows Server procedure that requires the information Preconfigured values for each component Space for recording values when you do not want to use the preconfigured values Gathering Values from the MCP Environment Certain components must have the same value in both the MCP and the Windows environments. Therefore, before you install Network Services on the Windows server, you need to determine their values in the MCP environment. VMMCP Server Values None required Libra Series Native MCP Servers and FS1800 Server Values To determine these component values, ask your Unisys service representative. Or, if you are familiar with the configuration editor on the Service Processor, you can use the editor to determine the value for NP unit number (Not defined in the PCD for CIA)