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)

37 Installing Network Services Changing the IP Addresses for Network Services EVLAN Path It is recommended that you do not change the IP Address and Subnet Mask for Network Services (EVLAN path). However, one reason to change these addresses is because you already have nodes in your network using the same subnet. In this case, choose a different private set of IP addresses that do not conflict with the subnets in your network. Notes: The Internet Assigned Numbers Authority (IANA) has reserved Class C addresses through for use within private networks (see RFC 1918). Changing the IP addresses of the EVLAN path is likely to require updates to the firewall rules on a Libra 4000 server. Table 2 1. Basic Network Services Configuration Values for VMMCP Servers Component Preconfigured Value New Value NP unit number 210 Do not change IP address of Windows server for the EVLAN path Do not change (see note 1) Subnet mask Do not change (see note 1) Host name of MCP server for this Windows environment IP address of MCP server for the EVLAN path CPMCP1 (see note 2) Do not change (see note 1) Table 2 2. Basic Network Services Configuration Values for Libra 4000 Servers Component Preconfigured Value New Value NP unit number 210 Do not change IP address of Windows server for the EVLAN path Do not change (see note 1) Subnet mask Do not change (see note 1) Host name of MCP server for this Windows environment IP address of MCP server for the EVLAN path CPMCP1 (see note 2) Do not change (see note 1)

38 Installing Network Services The following notes apply to both Table 2 1 and Table 2 2. Notes: 1. Although Unisys recommends that you do not change this IP address and Subnet Mask, you may decide to change them. If you are not using the preconfigured values, you must provide the new values in the indicated step of the Installing Network Services procedure. 2. The host name of this MCP server is preconfigured as CPMCP1. If you partition the server, a unique name must be assigned to each MCP server domain. Table 2 3. Basic Network Services Configuration Values for Libra Series Native MCP and FS1800 Servers Component Preconfigured Value New Value Windows Server A NP unit number 7000 Do not change IP address of Windows server for the EVLAN path Do not change (see note 1) Subnet mask Do not change (see note 1) Host name of MCP server for this Windows environment IP address of MCP server over this EVLAN path CPMCP1 (see note 2) Do not change (see note 1) Windows Server B NP unit number 7002 Do not change IP address of Windows server for the EVLAN path Do not change (see note 1) Subnet mask Do not change (see note 1) Host name of MCP server for this Windows environment IP address of MCP server over this EVLAN path CPMCP1 (see note 2) Do not change (see note 1) Windows Server C NP unit number 7004 Do not change IP address of Windows server for the EVLAN path Do not change (see note 1) Subnet mask Do not change (see note 1)

39 Installing Network Services Table 2 3. Basic Network Services Configuration Values for Libra Series Native MCP and FS1800 Servers Component Preconfigured Value New Value Host name of MCP server for this Windows environment IP address of MCP server over this EVLAN path CPMCP1 (see note 2) Do not change (see note 1) Windows Server D NP unit number 7006 Do not change IP address of Windows server for the EVLAN path Do not change (see note 1) Subnet mask Do not change (see note 1) Host name of MCP server for this Windows environment IP address of MCP server over this EVLAN path CPMCP1 (see note 2) Do not change (see note 1) Windows Server E NP unit number 7008 Do not change IP address of Windows server for the EVLAN path Do not change (see note 1) Subnet mask Do not change (see note 1) Host name of MCP server for this Windows environment IP address of MCP server over this EVLAN path CPMCP1 (see note 2) Do not change (see note 1) Windows Server F NP unit number 7010 Do not change IP address of Windows server for the EVLAN path Do not change (see note 1) Subnet mask Do not change (see note 1) Host name of MCP server for this Windows environment IP address of MCP server over this EVLAN path CPMCP1 (see note 2) Do not change (see note 1)

40 Installing Network Services Notes: 1. Although Unisys recommends that you do not change this IP address and Subnet Mask, you may decide to change them. If you are not using the preconfigured values, you must provide the new values in the indicated step of the Installing Network Services procedure. 2. The host name of this MCP server is preconfigured as CPMCP1. If you partition the server, a unique name must be assigned to each MCP server domain. Preparing for Shared Adapters If you intend to configure Fast Ethernet or Gigabit Ethernet NICs for shared access by the Windows and MCP environments, observe the precautions described in the following paragraphs. Note: Shared Adapters cannot be configured on Windows partitions of Libra Series native MCP servers or on FS1800 servers. Public LAN attachments are made available using CNA devices, IEA-IOP cards, and FC3-IOP cards. Preparing the NICs The appropriate adapter and driver software must be installed before you install or reinstall Network Services. If you have an adapter already configured for shared access and intend to replace it with a new adapter type, see Replacing a Shared Adapter or Updating an Adapter Driver later in this section. Network Services supports up to eight shared connections where a connection is either a Fast Ethernet or Gigabit Ethernet port, or an 802.1Q Virtual LAN (VLAN) connection. Note: TOE (TCPIP Offload Engine) function is incompatible with MCP use of adapters for all current platforms, including Libra 400, Libra 450, and Libra 4080/4090. Users should turn off TOE features on any adapters that will be used by the MCP. Preparing to Use Fast Ethernet Port Aggregation Network Services Shared Adapter software supports Fast Ethernet port aggregation, an optional feature offered on certain high-performance Fast Ethernet adapters. Port aggregation increases the effective network throughput by distributing Fast Ethernet traffic across multiple adapters. System and user programs see a single virtual port capable of operating at some factor in excess of 100 Mbps. Use the Fast Ethernet port aggregation software (as described in the third-party Fast Ethernet adapter documentation) before running Network Services Setup to share the virtual FE Port Aggregation adapter created. Setup will offer this virtual adapter to be selected as a shared adapter. The physical adapters assigned to the port aggregation may also appear in the list offered by Setup for shared adapter selection and should not be chosen

41 Installing Network Services If you have Fast Ethernet adapters already configured as shared adapters that you intend to use in Fast Ethernet port aggregation, you must first run the Network Services Setup program to un-share these adapters (i.e. disable MCP access). See "Reconfiguring a Shared Adapter" later in this section. Also, if you have configured a FE Port Aggregation adapter as a shared adapter and you intend to remove the port aggregation, you must first run Network Services Setup to un-share the FE Port Aggregation adapter. Preparing to Use Ethernet Jumbo Frames Jumbo frames improve ClearPath throughput and reduce the CPU cycles used for networking. This improvement is achieved by reducing the number of frames an application must process. This is particularly true for applications that use large message sizes such as file transfers. The remote system and the connecting network equipment must support jumbo frames to use this feature effectively. You can use Jumbo Frames with TCP/IP, BNA, and BNA over IP (BIP). In addition to the application message size, the performance benefits vary depending on which of these protocols you are using. Jumbo Frames is supported over Gigabit Ethernet connections only that use the Intel PRO/1000 F, FX, T, TX, or successor network interface cards. Note that you need driver release or higher. Also note that you must configure Jumbo Frames on both the Windows Server and the MCP. On the Windows Server or ClearPath Network Appliance (CNA) device, use Proset II to select the Jumbo Frames option and choose from the list of values for the frame size. On the Windows 2008 Server device, use the adapter properties to perform the same task. Unisys recommends On the MCP side, you must set the following attributes to desired values for applicable lines (connection groups) and devices (connections): Max Input Message Size (MIMS) Max Output Message Size (MOMS) Max Input Message Size Limit (MIMSL) Max Output Message Size Limit (MOMSL) The recommended frame size for Jumbo Frames is 9014, including the MAC header, but excluding the Cyclic Redundancy Check (CRC). Configure this value in the NIC driver, and translate it to the following MIMS/MOMS/MIMSL/MOMSL values: 9000 for the connection group 9000 or 8996 for TCP/IP and BNA/BIP connections respectively

42 Installing Network Services Communications between a jumbo-capable and a jumbo-incapable end-system is generally not a problem. This follows because a common frame size is negotiated between the systems when they establish a dialog. This applies to TCP/IP, BNA, and BIP protocols. It is not true for connectionless protocols such as UDP and ICMP, since they are datagram-based and do not negotiate a connection. If no router is in the path, each system transmits frames sized up to the systems mtu value. Any frames larger than 1,500 bytes are dropped if they are not supported by the receiver. The only potential issue occurs with the ICMP protocol pings that are larger than 1,500 bytes will fail. A useful technique in mixed networks is to logically segregate jumbo frame traffic from standard traffic by using IEEE 802.1Q Virtual LANS (VLANS). Preparing to Use IEEE 802.1Q VLANS IEEE 802.1Q VLANs are based on the addition of a 4-byte tag to the packet header, identifying the VLAN for that packet. It is important to note that if the ClearPath server is a member of only one VLAN on a given adapter port, tagging is not necessary on that port. The VLAN is configured at the LAN switch port only. No VLAN should be configured at the ClearPath server. If the ClearPath server is to be a member of multiple VLANs over the same adapter port, then both the LAN switch and the ClearPath server must be configured. The switch connected to the ClearPath server must support IEEE 802.1Q tagging. At the switch, tagging should be enabled, and all VLAN ID assignments made at the specific port. Follow whatever other vendor-specific instructions there may be. At the ClearPath server, VLAN IDs are assigned using the Windows Driver utility (Intel ProSet II). The VLAN IDs assigned to the NIC should match those assigned within the switch to the network in which you want the ClearPath host to participate. For each VLAN defined, Windows creates a new adapter and assigns it a new adapter number. Also, at the ClearPath Operator Interface, a Connection Group must be defined for each VLAN. The following are additional rules and notes for configuring VLANs on ClearPath: Assign the VLANs to the switch ports first. Before assigning VLANs to the NIC card, run NNS setup to unshare the physical adapter. Use PROSET II to assign VLANs to the physical adapter. PROSET II comes with the driver for the NIC cards. The minimum driver level is 6.1 or higher for Intel Pro 100 Fast Ethernet Adapters and Intel Pro 1000 Gigabit Ethernet Adapters on Windows 2000 or 2003 servers. DHCP will be enabled when VLAN is assigned; assign a fixed IP address for each VLAN adapter as required

43 Installing Network Services Each VLAN added will appear in the list of adapters that NNS can share. Rerun NNS setup to share the virtual adapters. Preparing to Use Quality of Service over LAN You can add Quality of service VLANs information in layer 2 or in layer 3, using the Intel PRIORITY PACKET III Optional Application. Priority Packet III is provided on the Intel Driver CD-ROM that comes with the NIC card. Priority Packet III works with Proset II, with Intel Pro/100+ Fast Ethernet cards only, using driver level or higher. Layer 2 QoS (802.1p) is based on the addition of a 4-byte tag to the packet header. This 4-byte tag specifies the priority level (0-7) for the packet. Layer 3 tags modify the existing IP header and do not increase the packet size. IEEE 802.1p is an IEEE standard for tagging packets with different priority levels. Tagging adds additional bytes of information to the packets. Packets are tagged with four additional bytes that indicate a priority level. IEEE 802.1p-aware devices transfer the higher priority packets first when they are sent out on the network. Using Priority Packet, 802.1p tagging lets you assign specific priority levels from 0 (low) to 7 (high). IEEE 802.1p tagging increases the size of the packets. Some hubs and switches will not recognize the larger packets because they exceed the maximum frame size of standard Ethernet packets. Therefore, these hubs and switches will drop these oversize packets. Check your hub or switch documentation to see if it supports 802.1p. Note: You can configure the switch to strip the tags from the packets and send them on to the next destination as normal traffic. Priority Packet III works with Windows 2000 and Windows Server Refer to the Intel Web site for additional details on Priority Packet III and Priority Packet III usage. Shared Adapter Properties Table 2 4 lists shared adapter property values that apply to each shared adapter that is being configured. You can set values for each shared adapter during Network Services setup or you can accept assigned defaults. To change property values after installation, you can run Network Services Setup again (for configuration only) or you can access these properties from the Windows Control Panel. For details see Examining or Updating Network Services Values in Section 3 (Libra native MCP servers) or Section 4 (VMMCP servers)

44 Installing Network Services Table 2 4. Shared Adapter Properties Property CNS Line ID Forward RIP Frames to MCP (Ethernet type adapters only) Unknown IP Frame Route (Ethernet type adapters only) Description A unique line number (range: 1 to 254) that must be assigned to each adapter that will be used by the MCP server (either exclusively or shared with Windows). Setup assigns the next available line number as the default. This property is used to match the adapter with a CNS Connection Group having the same LINEID attribute value in the CNS initialization file. This property determines whether Network Services will forward UDP Routing Information Protocol (RIP) frames received on this shared adapter to the MCP server. When this property is enabled (the default value), Network Services forwards RIP frames to the MCP server. When disabled, Network Services filters RIP frames so that they are not forwarded to the MCP server. See Installing Network Services on Libra Series Native MCP and FS1800 Servers later in this section for additional information. This property defines how inbound IPv4 frames with unknown addresses are to be routed. Allowable values are: Discard Frame Network Services does not accept inbound IP or ARP frames with unknown IP addresses. These frames are discarded. For maximum security of the Windows Server sharing the adapter with the MCP, you should set this value to Discard Frame. If you experience connectivity problems from Windows, set the option to To Windows TCPIP. To Windows TCPIP Network Services directs any inbound IP or ARP frames with an unknown IP address to Windows TCP/IP. This is the default value. To MCP TCPIP Network Services directs any inbound IP or ARP frames with unknown IP address to the MCP server s TCP/IP HRNP. Note: IPv6 frames are directed to Windows if the address is not known to belong to the MCP

45 Installing Network Services Installing Network Services Software Network Services is provided on both the release media and on CD-ROM. Use either type of media when installing or reinstalling Network Services on a ClearPath MCP server. The Network Services software runs in the Windows server environment of a ClearPath MCP server. It is installed in the following steps: 1. Copying Network Services files to the MCP server. 2. Install Network Services on each Windows server within the ClearPath MCP server. During the installation, a Setup program determines the server hardware and software environment and then installs the appropriate version of Network Services software. Note: These installation instructions assume that all hardware has been installed correctly. Contact your Unisys service representative if you have questions about hardware configuration. Copying Network Services Files to the MCP Server When a ClearPath MCP system is specified as the TARGET machine, the MCP Simple Installation program copies a set of Network Services files from the MCP release media to the following MCP directory: *SYSTEM/INSTALLS/CNP/= You can later access this directory to install Network Services within the Windows server environment. See the MCP Simple Installation Operations Guide for information about installing the complete software release. The Simple Installation program installs all required ICP and channel adapter firmware files. Installing Network Services in the Windows Server Environment The following subsections provide instructions for installing Network Services software in the Windows server environment of your ClearPath server: See Installing Network Services on Libra Series Native MCP and FS1800 Servers for instructions on installing Network Services on Libra Model 680 and 690, Libra Model 750, 780, and 790, Libra Model 880 and 890 servers and on FS1800 servers. See Installing Network Services on VMMCP Servers for instructions on installing Network Services on LX 180, Libra Model 400, Libra Model 450, Libra Model 460, Libra Models 4080 and 4090, FS1700, and SP1760 servers

46 Installing Network Services Installing Network Services on Libra Series Native MCP and FS1800 Servers Note: Do not run the Network Services Setup program from a Windows Terminal Services session. This is to avoid interruption of the terminal session that could occur before Setup completion when the network adapter supporting the session is assigned to Network Services as a shared adapter. Follow these steps to install and set up Network Services software within the Windows environment of the following ClearPath MCP servers: Libra Model 680, or 690 servers FS1800 servers Complete this procedure for each Windows server in your server complex: 1. Determine your method of installing Network Services: If you are installing from installation media, insert the CD-ROM in the CD/DVD drive of the Windows server. If you are installing from the MCP server, log on to Windows as an Administrator. Note: On Windows systems that have Terminal Server installed, start Setup.exe as follows: Open the Control Panel, open the Add/Remove Programs applet, open the Add Programs wizard, and start Setup.exe. 2. Start the Setup.exe program: If you are installing from installation media, access Setup.exe on the CD-ROM using Windows Explorer or Add/Remove Programs. If you are installing from the MCP server a. Map a network drive from Windows Explorer by choosing Map Network Drive from the Tools menu. b. Type the following in the Path box: \\<MCP server name>\installs For example, \\CPMCP1\INSTALLS c. Choose OK. If you are prompted for a password, enter the administrator s password. d. Select the subdirectory \CNP to see the files in this subdirectory

47 Installing Network Services 3. Run Setup.exe and follow the directions on the Specify Network Services Hardware Type screen. The Setup program attempts to detect the current environment and then install the appropriate version of Network Services software. Note: Installing a signed update of Network Services might require that the current installation be uninstalled first. In this case, Setup displays a warning and offers to initiate the uninstall process. After the uninstall process is complete, you must reboot before running Setup again. For version control, if Setup finds existing files, you see a dialog box asking for confirmation to continue. If you continue, Setup overwrites the existing files. If you are reinstalling the same version that is currently installed, the option to Update configuration options only is displayed. You can skip file installation by selecting this option and proceed with Network Services configuration in step 6. In the Windows environment, device configuration (.INF) files are also installed. For a new installation of Network Services, the Windows operating system might display a Microsoft Digital Signature warning dialog box asking if you want to proceed. Answer Yes. Setup displays the Choose Destination Location dialog box to request a directory to install files. The default is <WinDisk>:\Program Files\Unisys\NXNET. You can press Enter or browse to an alternate directory. This directory is henceforth referred to as <Network Services location>. 4. Click Next. A summary screen titled Start Copying Files is displayed. 5. Click Next. Setup installs the Network Services files. 6. For normal Windows server to MCP communications, NetBIOS Name Resolution must resolve the MCP host name to the EVLAN IP address (this is the IPv4 address assigned to the CNP or MAICP4 device). Depending on your server type, Tables 2 1 through 2 4 should contain the required host name and IP address information. A dialog box titled Specify Windows Server Environment is displayed. a. Enter the letter (as defined in Tables 2 1 through 2 4) that defines this Windows server. The Network Services Properties dialog box appears. b. Enter the NP Unit number. For a new installation, a default value is displayed that is based on the Windows server environment identified in step 6a. Depending on your server type, see Tables 2 1 through 2 4 for the applicable values. If this is a re-installation, the previous value is displayed. Choose OK. The Choose Configuration Options dialog box appears. c. Respond to the following configuration options:

48 Installing Network Services Auto-configure MCP Host Name Resolution to EVLAN path Leave this check box selected if you want the Setup program to update or create the LMHOSTS file automatically. When this check box is selected, the next dialog box prompts you for the TCP/IP host name of the MCP server. Clear the check box if you want to manage this name resolution yourself. See Directing Data through the EVLAN Data Path in Section 3 for additional information about the LMHOSTS file and the EVLAN data path. Assume default IP Addresses for Network Services Leave this check box selected unless you are changing the IP addresses used by Network Services for the EVLAN. It is recommended that you do not change these IP addresses. Clear the check box if you are changing the default IP address for Network Services. When this check box is cleared, the next dialog box prompts you for the IP address of the MCP server over the EVLAN path. If this is a re-installation, previously entered values are retained. The MCP Host Name dialog box appears and prompts you for the information (MCP Host Name, EVLAN IP address, or both) that is required based on the options you selected in step 6c. d. Perform one of the following actions: If you selected Auto-configure MCP Host Name Resolution to EVLAN path, type the TCP/IP host name of the MCP server when prompted. If you selected Assume default IP Addresses for Network Services, Setup determines the EVLAN IP address and subnet mask applicable to the identified Windows server environment. A dialog box displays a summary of your EVLAN data path choices. 7. Perform the following to complete Network Services installation: a. Check the progress messages displayed by Setup as it completes the installation. For a new installation, Setup installs one or more virtual devices and displays additional messages from Windows. b. Answer Yes to all Microsoft Digital Signature warnings displayed. Windows displays multiple Digital Signature warning dialog boxes asking whether you want to proceed. Network Services installation is now complete. Setup offers to restart the Windows server. If you are installing software from a CD-ROM, you can remove it from the CD/DVD drive at this time. If this is the initial installation, choose not to restart the Windows server and go to step 8 (system configuration steps). Otherwise, the installation is complete. Select the option to restart the Windows server

49 Installing Network Services 8. From the Windows server, alter the default settings of the Windows Event Log. Unisys recommends that you alter these settings as follows. However, configure these settings so that they are appropriate for your environment even if the settings differ from those recommended in this step. a. Open Windows Control Panel, open Administrative Tools, and then open Event Viewer. b. In the console tree, choose Application Log and then choose Properties on the Action menu. c. On the General tab of the Properties dialog box, make these changes: Change the maximum log size to a value of at least 2048 KB. Select Overwrite events as needed. Click OK to accept the changes. d. Repeat steps b and c for the system log. e. Exit the Event Viewer. 9. Open the Windows Control Panel and click the System icon. 10. Set Crash Recovery parameters for the Windows server as follows: a. Select the Advanced tab and choose Startup and Recovery. b. Verify that Recovery parameters are as follows (if required, change the indicated settings): Write debugging information to: %SystemRoot%\Memory.Dmp Complete Memory Dump Overwrite any existing file Automatically reboot c. Choose OK. d. If a choice to restart the system is displayed, select the option Don t restart the system now. 11. Shut down the Windows server by clicking the Start button and choosing Shutdown. The Shut Down Windows dialog box appears 12. Restart the Windows server by selecting Restart the Computer and clicking Yes. The initial installation of Network Services is now complete

50 Installing Network Services Installing Network Services on Virtual Machine for ClearPath MCP (VMMCP) Servers This section describes how to install and set up Network Services (NNS) software within the Windows environment of the following Virtual Machine for ClearPath MCP (VMMCP) servers: Libra Model 400 servers Libra 4000 servers FS1700 servers You can also use the procedures in this section to install multiple emulated network processors (NPs) in a single emulated MCP environment. Multiple network processor capability is supported in Windows 2000, Windows Server 2003, and later Windows release environments. Your server must be running virtual machine (VM) release 5.2 in order to support this capability. Note: When you install the Symantec Protection Agent software on Unisys virtual machines, Unisys recommends that you install the software before installing the Network Services software. If Network Services is already installed, follow the uninstall procedure Removing Network Services from the Windows Server later in this section. You can then install the Symantec Protection Agent and reinstall the Network Services software. You must install the software in this order to avoid potential conflicts between the Symantec Protection Agent software and the Unisys EVLAN adapter. Installing Network Services and Selecting Adapters Use the following procedure to install Network Services with multiple emulated ICP4 network processors (NPs) on a single Virtual Machine for ClearPath MCP system. You can install up to four NP units in a Windows 32-bit environment or up to 6 NP units in a Windows 64-bit environment. Before performing this procedure, note the following: The feature to install multiple emulated NPs is only available on Virtual Machine for ClearPath MCP systems and does not apply in a non-emulated MCP environment. Libra 4000 servers are configured with multiple emulated NPs by default. None of the adapters configured for MCP use on Libra 4000 servers can be shared with Windows TCP/IP. EVLAN is installed only for the first NP; second and subsequent NPs will not support EVLAN. A TCP/IP connection using the Network Services EVLAN can be established only to the first NP by creating static IP mapping using the EVLAN addresses assigned to that NP unit

51 Installing Network Services This feature enables you to distribute Network Services shared adapters across multiple NP units. One or more shared adapters can be assigned to each NP. However, any individual shared adapter can be assigned to only one NP. A single NP is sufficient for most purposes. On servers other than Libra 4000 servers, shared adapters assigned to NP#1 can be shared with Windows TCP/IP. Those assigned to NP#2 through NP#4 are for exclusive use by the MCP. The CNS Line IDs (1 to 254) assigned to shared adapters apply separately to each NP. For example, Line ID 1 may be assigned to an adapter of each NP. Line ID 0 is for EVLAN only and is not available for shared adapter use. To change the number of NPs, you must uninstall Network Services entirely and then install it again. To allow the MCP to access up to 11 network adapters on Libra 4000 servers, you must use the Multiple NP feature of NNS to declare each PCI slot as a separate NP. EVLAN is part of the first NP. The Network Services Setup utility assigns the adapters during the first installation of NNS on the Libra 4000 server. Subsequent installations are based on the previous installation. Use the System Editor to associate an NP instance to a specific NP number. The following table shows the default network port assignments. PCI Slot Network Port NP Instance Line ID Internal 1 (Top) Windows Exclusive Not applicable Internal 2 First 2 (Reserved) Internal 3 First 2 (JProcessor) Internal 4 First 4 (eportal) 7 Top Second 1 7 Bottom (optional) Second 2 6 Top Third 1 6 Bottom (optional) Third 2 5 Top Fourth 1 5 Bottom (optional) Fourth 2 2 (optional) Top Fifth 1 2 (optional) Bottom Fifth

52 Installing Network Services Installation Procedure 1. Determine your method of installing Network Services: If you are installing from CD-ROM, insert the CD-ROM into the Windows server CD-ROM drive. If you are installing from the MCP server, log on to Windows as an administrator. Note: You cannot perform an initial installation from the MCP server. However, you can reinstall Network Services (at the current level or higher) from the MCP server. To reinstall a previous Network Services level, see Restoring a Previous Release of Network Services later in this section. 2. Start the Setup.exe program: Note: On Windows 2000 or Windows Server 2003 with Terminal Server installed, start Setup.exe through the Add Programs wizard of the Add/Remove Programs applet of Control Panel. If you are installing from installation media, access Setup.exe from the CD- ROM. If you are installing from the MCP server: a. Map a network drive. From Windows Explorer, select Tools and then click Map Network Drive. b. Type the following in the Path box: \\<MCP server name>\installs For example: \\CPMCP1\INSTALLS c. Click OK. d. If you are prompted for a password, enter the administrator s password. e. If you want to see the files in this subdirectory, select the subdirectory \CNP. The Setup program determines the current emulated environment of your server and displays the Welcome screen. 3. Click Next on the Welcome screen and on the View Readme File screen that follows. If the Setup program cannot determine the VMMCP emulated environment, or if it finds existing NNS files, you are prompted as follows. (Otherwise, the Setup continues with step 4). If Setup cannot determine the emulated environment, the Specify Network Services Hardware Type screen is displayed. Select Virtual Machine for ClearPath MCP and then click Next. If the Setup program finds existing Network Services files, a screen asking for confirmation to continue the installation is displayed. If you continue, the Setup program overwrites the existing files

53 Installing Network Services If you are reinstalling the same NNS version that is currently installed, the option to Update configuration options only is displayed. You can skip file installation by selecting this option and proceed with Network Services configuration. Note: The NNS update installation is not available in a Windows 64-bit environment. Network Services must be uninstalled and the system must be rebooted before you can reinstall Network Services. Settings from your prior installation are retained in a persistent area of the registry so that your old settings are the values displayed on each screen during the reinstallation. Setup displays the Number of Network Processor (NP) Units to be Installed screen. 4. This screen enables you to install and configure one to four MAICP4 NP units on your VMMCP server (up to six NP units on a 64-bit architecture server). The default is one; if you choose a number greater than 1 in the NP Unit Count field, Setup installs for the appropriate number of NP units. The NP units are referred to as 1st NP, 2nd NP, 3rd NP and so on, and are mapped to ICP4 controls and assigned device numbers by the VMMCP System Editor. This example assumes you are installing two NPs. Enter 2, and then click Next. Setup displays the Choose Destination Location screen. On Libra 4000 servers, the number of NPs specified is typically the number of PCI Express NICs plus 1 for the inbuilt NIC. For example, you would specify four NPs on a system with three optical PCI Express NICs. 5. Use this screen to specify a directory in which to install files. The default is <WinDisk>:\Program Files\Unisys\NXNET. You can accept the default or browse to an alternate directory. Throughout the rest of this procedure, this directory is referred to as <Network Services location>. Click Next. A summary screen titled Start Copying Files is displayed. This screen shows the settings Setup will use to install Network Services files. 6. Click Next. After the Network Services files are installed, the Configuration of Shared Adapter Cards screen is displayed. This screen enables you to provide the VMMCP server with access to Fast Ethernet adapters or Gigabit Ethernet adapters installed in the Windows server. Note: The Shared Adapters feature applies to any use of an adapter by the MCP networking stack. This includes adapters that are configured for MCP exclusive use and adapters shared by the MCP and Windows TCP/IP. 7. Select the appropriate option: If you select Yes. Proceed with selection of adapter cards to be shared, click Next and go to step 8. If you select Do not share adapter cards with Network Services, go to Completing Installation of Network Services (Virtual Machines with Multiple NPs)

54 Installing Network Services 8. On the Select Adapter Cards for MCP Server Access (1st NP of n) screen, this example assumes that you check the box for the second adapter and then click Next. Adapters that are not selected for any of the NPs are used exclusively by Windows TCP/IP and Windows IPv6. The adapters you choose (check) on this screen are assigned for MCP access via the first network processor (NP). If you select an adapter that is assigned to the currently displayed NP unit and click Properties, you can change the CNS Line ID for that adapter. The CNS Line ID must be unique only among adapters assigned to the same NP unit. That is, two adapters can have the same CNS Line ID if they are assigned to different NP units. After you click Next, the Adapter Properties screen is displayed showing the properties for the adapter assigned to the 1st NP 9. If the adapter is not assigned to an NP unit, the CNS Line ID box is not displayed on the Adapter Properties screen. You cannot set the CNS Line ID for any adapter if you click Properties while the Select Adapter Cards to be Shared screen (step 11) is displayed. Click OK to redisplay the Select Adapter Cards for MCP Server Access (1st NP of n) screen. 10. Click Next. The Select Adapter Cards for MCP Server Access (2nd NP of n) screen appears. On this screen, the same list of candidate adapters is presented for selection, but the adapter chosen for the 1st NP is dimmed (Intel (R) PRO/1000 MT Network Connection). If all the adapters are chosen for the 1st NP, this screen does not appear. Instead, the No Adapters Assigned for NP #2 Use warning message is displayed. This example assumes that you check the box to assign the first adapter on the screen (Intel (R) PRO/100+ Server Adapter) to the 2nd NP. Note: If you want to go back and change your adapter selections, each adapter has to be unchecked on the screen on which it was originally assigned. 11. Click Next. The Select Adapter Cards to be Shared screen appears. The adapters chosen for MCP Server access on the previous screens are presented for selection. Only the adapters you assigned to the 1st NP are enabled. The adapters that are chosen (checked) will be available to Windows TCP/IP. The Adapter Properties screen, displayed by clicking Properties on this screen, will show the CNS Line ID value assigned to the selected adapter, but the field will be dimmed

55 Installing Network Services You can change the Network Services properties of any adapter. Selected (checked) adapters will be used by the MCP server (for BNA and TCP/IP connections via Network Services) and by the Windows server (for TCP/IP connections). Adapters not selected (unchecked) are used exclusively by the MCP server. They will not be available to Windows TCP/IP. 12. Click Next. The Review Shared Adapter Card Selections screen appears. This screen displays the information in the ADAPTERS.TXT file (see Figure 2 1 later in this section). 13. Click Next. If you want to specify the EVLAN data path (this only applies to the 1st NP created), perform steps 14 through 16. Otherwise, proceed with "Completing Installation of Network Services (Virtual Machines with Multiple NPs)" later in this section. 14. Click Next. The Choose Configuration Options screen appears. For normal Windows server-to-mcp communications, NetBIOS Name Resolution must resolve the MCP host name to the EVLAN IP address (that is the IPv4 address assigned to the MAICP4 device). Table 2 1, earlier in this section, contains the required host name and IP address information. Respond to the configuration options as follows: Auto-configure MCP Host Name Resolution to EVLAN path Leave this check box selected if you want the Setup program to update or create the LMHOSTS file automatically. When this box is selected, the next screen will contain a prompt for the TCP/IP host name of the MCP server. Clear the check box if you want to manage this name resolution yourself. See Directing Data through the EVLAN Data Path in Section 4 for additional information about the LMHOSTS file and the EVLAN data path. Assume default IP Addresses for Network Services 15. Click Next. Leave this check box selected unless you are changing the IP addresses used by Network Services. It is recommended that you do not change these IP addresses. Clear the check box if you are changing the default IP address for Network Services. If this is a re-installation, previously entered values are retained. The next dialog box solicits the information (MCP Host Name and/or EVLAN IP address) that is required, based on the option you selected in step

56 Installing Network Services If you selected Auto-configure MCP Host Name Resolution to EVLAN path, type the TCP/IP host name of the MCP server when prompted. If you selected Assume default IP Addresses for Network Services, Setup determines the EVLAN IP address and subnet mask applicable to the identified Windows Server environment. 16. Click Next. A dialog box displays a summary of your EVLAN data path choices. Setup may then display warning messages as it completes. Go to "Completing Installation of Network Services (Virtual Machines with Multiple NPs) later in this section

57 Installing Network Services Sample ADAPTERS.TXT File The Setup program generates an ADAPTERS.TXT file in the NX/Net install folder. The file gives a summary of the installation, including a list of network adapter choices. In the following sample file: NP Unit Count shows the number of NP units Network Services is installed for NP Assignment shows the NP for adapters chosen for MCP use NP Unit Number refers the user to the VMMCP System Editor Network Services Installation Summary Software version: Hardware type: Virtual Machine for ClearPath MCP. Installed: :16:57 =============================================== Adapter cards will be assigned for use as follows: =============================================== Exclusive use by MCP Server for network connections... Name: Local Area Connection 2 Physical Address: unknown Device Name: Intel(R) PRO/100+ Server Adapter NP Instance: 2 nd NP CNS Line Id: 1 Forward RIP Frames to MCP?: Yes =============================================== Shared by MCP Server and TCP/IP on Windows... Name: Local Area Connection Physical Address: 00C09F23D9E9 Device Name: Intel(R) PRO/1000 MT Network Connection NP Instance: 1 ST NP CNS Line Id: 1 Forward RIP Frames to MCP?: Yes Unknown Ip Frame Route: Route to Windows Tcpip =============================================== Exclusive use by Windows Server... (None) =============================================== NETWORK CONFIGURATION INSTRUCTIONS: For each adapter card to be accessed by MCP Server... change (on MCP Server) the CNS Init file command NW ADD CONNNECTIONGROUP for this adapter with attributes set as follows (using values above): LOCALADDRESS = *DEFAULT (or Physical Address) ADAPTERTYPE = ETHERNET, FASTETHERNET, or GIGABIT. LINEID = (CNS Line Id number assigned to this adapter) =============================================== You chose the following configuration options: NP Unit Number: (See ICP4 Controls in System Editor of Virtual Machine for ClearPath MCP) EVLAN was not installed. Figure 2 1. Sample ADAPTERS.TXT File

58 Installing Network Services Completing Installation of Network Services (Virtual Machines with Multiple NPs) The Setup program displays progress messages as it completes the installation. For a new installation (or if additional adapters were selected for sharing), Setup installs one or more virtual devices and displays additional messages from Windows. As part of the device installation process, Windows displays multiple Digital Signature warning dialogs asking if you want to proceed. Answer Yes to all Digital Signature warnings. Network Services installation is now complete. Setup offers to restart the Windows server upon exit. If applicable, remove the installation CD-ROM at this time. If this is the initial installation, do not restart and proceed with the following system configuration steps. Otherwise, the installation is complete and you can select the option to restart the Windows server (skip the following system configuration steps). System Configuration Steps 1. From the Windows server, set parameters for the Windows Event Log. Unisys recommends that you alter these settings as follows, but you should configure these settings so that they are appropriate for your environment even if the settings differ from those recommended in this step: a. Open the Event Viewer. b. In the tree pane, click the Application Log. c. On the Action menu, click Properties. d. On the General tab of the Properties dialog box, change the Maximum Log Size to a value of at least 2048 KB and then click OK. e. Repeat steps b through d for the System Log. f. Exit the Event Viewer. 2. Open the Windows Control Panel, and then double-click the System icon. 3. Set crash recovery parameters for the Windows server as follows: a. Select the Advanced tab and click Startup and Recovery. The Startup and Recovery dialog is displayed. b. Verify that the following System Failure options are selected and if not, select them: Automatically reboot. Selecting additional recovery parameters is not recommended. Under Write debugging information: Complete Memory Dump %SystemRoot%\Memory.Dmp Overwrite any existing file c. If asked to restart the system, select Don t restart the system now

59 Installing Network Services 4. Shut down and then restart the Windows server as follows: a. Click Start and then Shutdown. b. The Shut Down Windows dialog box appears. Select Restart the Computer, and then click Yes. 5. In the virtual MCP environment, use the following procedure to verify that the MAICP4 connection is enabled: a. Ensure the Console for MCP is active. If active, xxxx Console should appear on the Windows Taskbar, where xxxx represents the model number. If applicable, use one of the following methods to activate the Console for MCP: Double-click the Console for MCP icon. Click the Console for MCP button on the Windows Taskbar. b. Click the SysEdit button on the toolbar. c. From the File menu, select Load Active PCD. d. Examine the configured resources, and look for an ICP 4. e. If there is no ICP 4 entry, the ICP 4 is not included in the PCD and will have to be configured to enable the MCP to see and use it. If an ICP 4 entry is present, right-click the entry and then select Control Properties. f. Verify that the available property indicates Yes. g. Repeat for any other ICP4 devices in the PCD

60 Installing Network Services Viewing Network Services Properties on Virtual Machine for ClearPath MCP Servers If you display the Local Area Connection Properties dialog box (through the Windows Network Connections Applet) for the adapter assigned to the 1st NP, the components list shows two entries for Network Services: Unisys Network Services for ClearPath MCP (applies to the 1st NP unit) Unisys Network Services #2 for ClearPath MCP (applies to the 2nd NP unit) Note: Only one Network Services component can be checked per adapter. You can view the Network Services Properties by selecting the enabled Network Services component and then clicking Properties. The Shared Adapter tab of the Properties dialog box shows the CNS Line ID and other parameters of the adapter. You can change any of the properties shown in the Shared Adapter tab. The new values take effect after rebooting. The Network Processor tab of the Properties dialog box shows the NP Unit Number only if Network Services has discovered the value assigned by the VMMCP System Editor. The value displayed is dimmed to indicate that it cannot be changed: How the Setup Program Manages the LMHOSTS File If you use the automated procedure for specifying the EVLAN data path during installation, the Setup program: 1. Uses the information you provide during setup to create an LMHOSTS file entry. For example, if this is the first or only Windows server, and the MCP host name is CPMCP1, the LMHOSTS file entry would be: CPMCP1 #PRE 2. Creates two identical files (LMHOSTS.ORG and LMHOSTS.CNP), which both contain the LMHOSTS file entry. The LMHOSTS.ORG file is located in the <Network Services location>. The LMHOSTS.CNP file is located in %systemroot%\system32\drivers\etc\. Note: See Managing the NetBIOS Name Cache later in the section for details about how Network Services uses these files. 3. Creates or updates the LMHOSTS file in %systemroot%\system32\drivers\etc\ to contain the line: #INCLUDE LMHOSTS.CNP

61 Installing Network Services When Reinstalling Network Services The Setup program displays the prompt to Auto-configure MCP Host Name to EVLAN path. If you select this option, the Setup program creates the include file and updates the LMHOSTS file the same as for an initial installation. If you do not select this option, the Setup program: Removes the LMHOSTS.ORG and LMHOSTS.CNP files if they are present. Removes the include statement from the LMHOSTS file if it is present. Bringing Network Services Into Service Perform the following steps for each Windows server in the configuration. Step Action 1 Note: This step applies to VMMCP servers. From an ODT window, verify the appropriate firmware file is on the pack where CNSMANAGERS looks for firmware files. a. Use the following command to list the code files associated with all network processors: NW NP CF The response should include information for both MAICP4 and CNP network processors. For example: NP CODE FILE FOR NPS:... FILE TITLE FOR MAICP4 0 IS *SYSTEM/<filename>/FIRMWARE ON <pack>, FILE TITLE FOR MAICP4 1 IS *SYSTEM/<filename>/FIRMWARE ON <pack>, FILE TITLE FOR CNP 0 IS *SYSTEM/<filename>/FIRMWARE ON <pack> FILE TITLE FOR CNP 1 IS *SYSTEM/<filename>/FIRMWARE ON <pack> where: <filename> is MAICP4 <pack> is the optional pack name b. Use the PD command to verify that the applicable firmware file is on the same pack. To verify that MAICP4 firmware exists (this firmware is required for LX7100 servers), enter: PD *SYSTEM/MAICP4/FIRMWARE on <pack name> In either case, detailed file information should be displayed if the file exists on the specified pack. If the firmware file is not present, you must install the CNS product from the NETSYSTEM media

62 Installing Network Services Step Action 2 Use the UR PORT <port number> command to make the port usable for the NP. Note: For all systems except Libra Series native MCP servers with HMP FastPath CIA, you can determine the port number by entering the following command: OL CTL <control number of NP> where <control number> is the NP unit number in Tables 2 1, 2 2, and 2 3. For Libra Series servers with FastPath CIA, the default port number is the NP unit number in Tables 2 1, 2 2, 2 4, and Note: This step applies to VMMCP servers. Use the UR CTL <control number of NP> command to cause the executing partition to resume operations through the specified control. 4 Note: This step applies to VMMCP servers. Use the RY NP <device number> command to ready the NP. where <device number> is 210 You must ready the NP before the host can load the firmware file to it. (You can ready the NP before or after initializing the network provider on the host.) 5 Note: This step is required only if you are using shared adapters or CNAs or will be changing preconfigured values (such as names or IP addresses). If you do not use shared adapters and do not plan to change preconfigured values, go directly to step 6. Configure each MCP, Windows server, SCP (if applicable), and Fast Ethernet or Ethernet switch (if applicable) as described in: Configuring a TCP/IP and BNA Network in Section 3 (for Libra native MCP servers) All of Section 4 (for LX 180, Libra Model 400, Libra Model 450, Libra Model 460, Libra Models 4080 and 4090, FS1700, and SP1760 servers) 6 From the ODT, initialize the latest version of the network providers (TCP/IP and BNA, if applicable): a. Enter the following commands to take down the current network provider versions: NW TCPIP - NW CNS - NW BNA - b. Enter the following command to initiate the latest version of CNS: NW CNS + <CNS initialization file name> c. Enter the following command to initiate the latest version of TCP/IP: NW TCPIP + <TCP/IP initialization file name> d. If necessary, enter the following command to initiate the latest version of BNA (Heritage Network Services): NW BNA + <BNA initialization file name> 7 Set up networking attributes as necessary to optimize the performance of Network Services This procedure is provided under Optimizing Network Services for the Enhanced VLAN (EVLAN) in Section

63 Installing Network Services Verifying Network Services Installation Test 1 To verify that Network Services is installed correctly, perform the following tests. Step Action 1 Enter "PING <MCP hostname>" from a Windows command prompt. 2 Verify that the address used is that of the EVLAN path (refer to Table 2 1 for applicable address values). For example: Pinging CPMCP1 [ ] with 32 bytes of data: Reply from : bytes=32 time=10ms TTL=62 If the IP Address Used Is the Ethernet/Switch Path The LMHOSTS file is not being used for TCP/IP name resolution. Check the LMHOSTS file. See "How the Setup Program Manages the LMHOSTS File" earlier in this section. If the LMHOSTS file is correct, then something else is providing TCP/IP name resolution. In most cases, this will be a Domain Name Server. To override a Domain Name Server, make an entry in the %SystemRoot%\System32\Drivers\Etc\HOSTS file that defines the appropriate preconfigured value (see Tables 2 1 and 2 3) as the address for the MCP Host. If the PING Command Is Unsuccessful The EVLAN path is not working if a PING command attempts to contact the correct IP address, but gets the response "Request timed out" for all four attempts. Open the Windows Control Panel, open Administrative Tools, double-click the Services icon, and verify that the service Unisys Network Services is started. This service should have started automatically when you rebooted the Windows server after following the "Installing Network Services on the Windows server" procedure earlier in this section. If the service Unisys Network Services is not started, reinstall the Network Services software on the Windows server

64 Installing Network Services From the MCP server, enter one of the following commands to verify that the TCP/IP connection is open: NW CONN 70000_TCPIP_70000 NW CONN 2100_TCPIP_2100 (for EVLAN to Windows server A on the Libra Series native MCP servers, and FS1600) (for EVLAN on Libra Model 400 and FS1700 servers) Ensure that the response indicates CONNECTIONSTATUS is OPEN. If the service has started and the TCP/IP connection is open, then you should contact your Unisys representative for further assistance. Test 2 Step Action 1 Open the Windows Control Panel. On Windows 2000 or Windows Server 2003, open Administrative Tools. 2 Double-click the Services applet and verify that Unisys Network Services has started. 3 With Windows Explorer, select Tools and Map Network Drive to map a drive to the INSTALLS share on the MCP. 4 From the MCP server, enter the command NW TCPIP CONNECTION IPADDRESS <Windows server EVLAN IP address>. For example, enter NW TCPIP CONNECTION IPADDRESS The system returns a list of TCPIP transport connections between the MCP server and the Windows server. If you are using the EVLAN data path, this list includes an entry that indicates MY NAME 139 and MY IP ADDRESS <MCP EVLAN IP address>. If this information is returned, the test was successful. Otherwise, proceed to step 5. 5 From the MCP server, enter the command NW CONN <EVLAN connection name>. For example, enter NW CONN 70000_TCPIP_70000 The system returns the status of the EVLAN connection between the MCP server and the Windows server. If the TCPIP Transport Connection Is Not Found If the TCPIP transport connection is not found, you probably are still using the Ethernet (or Fast Ethernet) switch data path. Check the LMHOSTS file. See "How the Setup Program Manages the LMHOSTS File" earlier in this section. Also see "Directing Data through the EVLAN Data Path" in Section 3. To examine mappings in the NetBIOS Remote Cache Name Table, enter the following command from a Command prompt: nbtstat -c

65 Installing Network Services The response should include a mapping of the MCP host name to the EVLAN IP address. For example, this response would be returned at Windows server A (hostname CPMCP1 is mapped to the preconfigured EVLAN address of ). NetBIOS Remote Cache Name Table Name Type Host Address Life (sec) CPMCP1 <03> UNIQUE CPMCP1 <03> UNIQUE CPMCP1 <03> UNIQUE If the EVLAN Connection Status Is PEND OPEN If the connection status is PEND OPEN, a failure occurred in Network Services and the MCP cannot use the EVLAN path. If the EVLAN Connection Is Not Found If the connection is not found, the MCP server did not successfully process the initialization file. Verifying Shared Adapter Installation To verify that the various shared adapters are installed correctly, perform the following tests. Step Action 1 Enter "IPCONFIG /ALL" from a Windows command prompt. If you have a record of the physical (MAC) address of the Fast Ethernet or Gigabit Ethernet adapter selected for sharing, verify that the Janus adapter used this address. For example, the output may show: Ethernet adapter Janus4: Physical Address : Also, the physical address may be encoded in your CNS initialization file: If you used the NAU to generate initialization files, this physical address value should match the LocalAddress attribute of the CNS Connection Group added for the adapter. Examples follow for Fast Ethernet or Gigabit Ethernet adapters: NW ADD CONNECTIONGROUP CG_ICP_70001 (TYPE = LAN, ICPDEVICEID = 7000, LINEID = 1, SPEED = , LOCALADDRESS = , ADAPTERTYPE = FASTETHERNET); NW ADD CONNECTIONGROUP CG_ICP_70002 (TYPE = LAN, ICPDEVICEID = 7000, LINEID = 2, SPEED = , LOCALADDRESS = , ADAPTERTYPE = GIGABIT); If you edited the preconfigured initialization files shipped with each system (see Appendix A), each shared adapter s LocalAddress attribute is set to *DEFAULT. This value forces CNS software to determine the physical address when the connection is established

66 Installing Network Services 2 Compare the Fast Ethernet or Gigabit Ethernet adapter information in the "ADAPTERS.TXT" file generated by Setup with attribute information in the CNS initialization file ADD CONNECTIONGROUP command for the adapter. The ADAPTERS.TXT file can be found in the NNS installation directory (e.g. "\NXNET"). The ADAPTERS.TXT file Line ID value must match the CNS initialization file LINEID attribute. Figure 2 1 is a sample ADAPTERS.TXT file. This sample illustrates two adapters assigned for use by the MCP environment. The adapter assigned to the first NP instance can be shared between the MCP server and TCP/IP on Windows. The adapter assigned to the second NP instance can be accessed only by the MCP server. 3 Enter "PING <IP-address>" from a Windows command prompt to verify that you can ping the IP address assigned to the MCP server (via the shared adapter). Use the IP address assigned in the MCP shared adapter connection in the TCPIP initialization file. The LINEID attribute in the TCPIP TCPIPIDENTITY command must match the LINEID of the CNS Connection Group for the shared adapter. 4 Enter PING <IP-address> from a Windows command prompt to verify that you can ping a known external device. 5 Enter NW TCPIP PING <IP-address> from the MCP environment to verify that you can ping a known external device. Note: The Line Status Discovered report can be used to obtain key information about each shared adapter configured within a network processor (NP). Network Services issues the Line Status Discovered report whenever an NP is initialized. Thereafter, you can access it by issuing an NP inquiry. See Viewing Shared Adapter Information in Section 6 for more information. If the Ping Command Is Unsuccessful The shared adapter path is not working if a PING command attempts to contact the correct IP address, but gets the response "Request timed out" for all four attempts. Verify that Unisys Network Services is started in the Services Control Panel Applet. It should have started automatically when you rebooted the Windows server after following the "Installing Network Services on the Windows server" procedure earlier in this section. If the Unisys Network Services service is not started, reinstall the Network Services software on the Windows server. From the MCP server, enter a command similar to one of the following commands to verify that the TCP/IP connection is open: NW CONN 80011_TCPIP_80011 device) NW CONN 2101_TCPIP_2101 (for first MCP adapter on a CNA (for first shared adapter on CS7201 or Libra Model 520 servers)

67 Installing Network Services Ensure that the response indicates CONNECTIONSTATUS is OPEN. If the service has started and the TCP/IP connection is open, then you should contact your Unisys representative for further assistance. Reconfiguring Network Services This subsection includes these topics: 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 Reconfiguring Network Services on a Partitionable Server If, after installing Network Services on a Libra Series native MCP server, you change the MCP environment, either by splitting partitions or joining partitions, you need to update the MCP host name information in both the Windows and MCP environments. Use either of the following methods: Method 1 1. Run the Network Services Setup Program on the Windows server(s) associated with the MCP host name that was changed. 2. Use the NAU to identify changes to the MCP environment. 3. Distribute the new network initialization files. 4. Bring down and then restart TCP/IP and CNS on the MCP server (each partition). Method 2 1. Change the host name of the MCP server in the LMHOSTS file. If you selected the Auto-Configure MCP Host Name Resolution to EVLAN Path option during Network Services installation, update the host name in the LMHOSTS.ORG and the LMHOST.CNP files to reflect the new name. Refer to How the Setup Program Manages the LMHOSTS File earlier in this section for the format and location of these files. If you manage your LMHOSTS file manually, see Manually Configuring the EVLAN Data Path for Windows for information about updating the LMHOSTS file. 2. Either reboot the Windows server or type nbtstat -R at the MSDOS command prompt on the Windows server to purge and refresh the NetBIOS name cache. 3. Use the NAU to identify changes to the MCP environment. 4. Distribute the new network initialization files. 5. Bring down and then restart TCP/IP and CNS on the MCP server (each partition)

68 Installing Network Services Managing the NetBIOS Name Cache If, during installation of Network Services, the Windows server was configured to use the EVLAN data path, the Setup program created the LMHOSTS.CNP file in the following directory: %SYSTEMROOT%\SYSTEM32\DRIVERS\ETC Each time Unisys Network Services is stopped, Network Services checks for the LMHOSTS.CNP file. If this file is present, Network Services deletes it and runs nbtstat -R to flush and reload the name cache, excluding the EVLAN data path. Reconfiguring a Shared Adapter with Network Services Setup During Network Services Setup you may have defined one or more of the Windows server NICs as shared adapters. At any time, you can reconfigure a shared adapter to: Un-share an adapter (allow only Windows to use it) Share an adapter (allow both Windows and the MCP to use it) Configure an adapter for exclusive use by the MCP (for both BNA and TCP/IP transfers) Note: If the original installation media is not available, you cannot directly reconfigure the shared adapter. Instead, you must re-install Network Services (Windows). 1. Run the Setup program again, using the same installation media that was used to install the current version. See Installing Network Services Software earlier in this section. 2. In the dialog box titled Network Services Already Installed, select Update Configuration Options Only. 3. The Configuration of Shared Adapters screen is displayed. Select Yes and proceed as follows: To un-share an adapter a. Click Next until the Select Adapter Cards for MCP Server Access screen is displayed and clear the check mark to the left of the applicable adapter. b. Click Next as necessary to accept all other values and proceed through the reconfiguration. To share an adapter or configure for MCP exclusive usage a. Click Next until the Select Adapter Cards for MCP Server Access screen is displayed and check the box to the left of the applicable adapter. b. Click Next. In the Select Adapters Cards to be Shared screen, clear or check the adapter s check box as applicable: When cleared, the adapter will be used exclusively by the MCP When checked, the adapter will be shared by the MCP and Windows TCP/IP

69 Installing Network Services c. Click Next as necessary to accept all other values and proceed through the reconfiguration. Reconfiguring a Shared Adapter with Network Connections Properties Note: You cannot configure shared adapters on Windows partitions of Libra Series native MCP servers or Libra 4000 servers. In a Windows 2000 or Windows Server 2003 environment, you can use Local Area Connection Properties to: Un-share an adapter (allow only Windows to use it) Create a new shared adapter (allow Windows and the MCP to use it) Configure an adapter for exclusive use by the MCP (for both BNA and TCP/IP transfers) To reconfigure the shared adapter: 1. Bring up the Network Connections manager. This is available from Properties within the My Network Places icon on the Windows desktop. 2. Select the particular Local Area Connection assigned as a Network Services Shared Adapter (for example, Local Area Connection 3) and press Alt+Enter to display the Properties dialog. To un-share an adapter a. For all adapters: Select Unisys Network Services and clear the check box to the left of the entry. b. If the adapter was assigned for exclusive use by the MCP server, also select Internet Protocol (TCP/IP) and check the box to the left of the entry. c. Click OK. To share an adapter a. For all other adapters: Select Unisys Network Services and check the box to the left of the entry. b. If required, press the Properties button to change Network Services properties (such as CNS Line ID). c. Click OK. Reply Yes to all Microsoft Digital Signature warnings. To configure an adapter for MCP exclusive usage a. Select Internet Protocol (TCP/IP) and clear the check box to the left of the entry. b. Click OK

70 Installing Network Services Replacing a Shared Adapter or Updating an Adapter Driver Use this procedure if you have a Fast Ethernet or Gigabit Ethernet adapter already configured for shared access and intend to replace it with a new adapter type. Step Action 1 Follow the procedure Reconfiguring a Shared Adapter to disable MCP access to the original shared adapter 2 Following manufacturer instructions, install the new adapter and driver software. 3 Remove the existing adapter driver software. 4 Reboot the Windows environment. 5 Follow the procedure Reconfiguring a Shared Adapter to enable MCP access to the new adapter

71 Installing Network Services Removing Network Services from the Windows Server Normally, Network Services runs automatically when your ClearPath server is running. However, you may occasionally want to remove it from the system. Procedure Use the following procedure to remove Network Services. Step Action 1 Note: This step applies to VMMCP servers. Issue these MCP commands at an ODT window: SV NP <device number> CL NP <device number> where: the default <device number> is the NP unit number in Table 2 1. These commands make Network Services inactive and destroy all connections between Network Services and the host. 2 Note: This step applies to VMMCP servers. On the MCP server, reserve the control for the PCI Bridge or ICP4 as follows: UR CTL <device number> 3 On the MCP server, issue the following command to reserve the port for the applicable PCI Bridge, ICP4, or FC-IOP. UR PORT <port number> For servers with HMP FastPath CIA only, enter OK on the waiting job to complete the port reserve operation. Note: This step applies to VMMCP servers. You can determine the port number by entering the following command: OL CTL <device number> The port number is returned in the system response. For Libra Series native MCP servers, and FS1800 servers (with FastPath CIA), the default port number is the NP unit number in Tables 2 3 and For VMMCP servers, disable the MAICP4 as follows: a. Activate the console for MCP. b. Click the Halt button. Wait until Suspended appears on the MCP State status line; this indicates that the MCP environment is suspended. c. From the MCP menu, choose Shutdown MCP Control. Wait until a shutdown message appears on the MCP State status line; this indicates that the MCP environment is completely shut down. 5 Bring up the Windows Control Panel and open the Add/Remove Programs applet

72 Installing Network Services Step Action 6 From the list of installed programs, select ClearPath Network Services and choose the Add/Remove button. 7 Close the Control Panel and restart the system. 8 After the reboot, the Found New Hardware Wizard screen may appear. Click Next to see the Install Hardware Device Drivers screen. If the device identified is Other PCI Bridge Device, click Cancel. (The driver for the PCI Bridge or FC- IOP device is installed via Network Services Setup. It cannot be installed via Found New Hardware Wizard.) Note: The Network Services uninstall process does not re-enable Windows TCP/IP for adapters that were configured for MCP exclusive use. To re-enable Windows TCP/IP for an adapter 1. In Control Panel, open Network Connections. 2. Right-click the adapter for which Windows TCP/IP is to be re-enabled, and click Properties. 3. Select the Internet Protocol (TCP/IP) check box. 4. Click OK

73 Installing Network Services Remotely Upgrading Network Services on a Windows Server or CNA Device The CNS REMOTEINSTALL command enables a ClearPath MCP user to upgrade Network Services (NNS) software on a ClearPath Network Appliance (CNA) device. The Windows server or CNA device must be connected to the ClearPath MCP system through NNS. This command is not supported for NNS software installation in Windows 2000 Datacenter Server environments or in Windows 64-bit environments including the Libra 4000 servers. The format of this command is as follows: CNS REMOTEINSTALL NP <device number> NETWORK SERVICES [PATH <setup path>] [REBOOT AUTO/MANUAL] Before entering this command, the following conditions must be met: The boot path of the connected Windows server or CNA device must be running. If a setup path is specified in the command, it must be to a directory on the local ClearPath MCP host. The MCP and NNS software must be at the MCP release 9.0 or later level. The NNS software must be running and be able to communicate with CNS. If all of these conditions are met, proceed to Initiating a Remote Upgrade later in this subsection. If you use the default REMOTEINSTALL path, the read access permissions for the MCP Installs share must include all the files in the shared folder. To verify this: 1. From the Windows server or CNA device, map a network drive to \\<mcphostname>\installs. Note: This procedure can also be done from a Windows client workstation if it has Administrator access to the Installs share. You only need to perform this procedure from one system you don t need to do this from each target Windows server or CNA device on which NNS will be upgraded. 2. Right click on the CNP folder and then click the Properties menu selection. 3. From the MCP File Security tab, click Permissions and then Advanced>>. Click on the Files within this directory checkbox. 4. You can disconnect the mapped drive; you don t need to reboot the Windows server. Initiating a Remote Upgrade You can initiate a remote upgrade by issuing the CNS REMOTEINSTALL command with the appropriate options for your installation (listed in Command Options later in this subsection). Before you issue this command, check the precautions listed in Command Restrictions and Limitations later in this subsection

74 Installing Network Services The REMOTEINSTALL command upgrades NNS on the specified Windows server or CNA device and reboots the system if necessary. Monitoring Reports After you initiate the REMOTEINSTALL command, monitor the reports that are generated most errors resulting from this command are identified in reports. The following report indicates that the REMOTEINSTALL command was successful: REMOTE INSTALLATION OF NETWORK SERVICES ON NP nnnn: INSTALLATION COMPLETED If this report is not received, the command is not successful even if you do not receive an explicit report indicating an error. Command Options The REMOTEINSTALL command can accept the following options: Option Device number Setup path REBOOT Description A 16-bit integer that specifies the Windows server (NP) or CNA device the remote installation is to be performed on. Use the NW NP inquiry to find which NPs are in the local host. Optional. Specifies the Windows-format path to the directory where the files to be used for the installation are found. You must specify this option if the directory is on the local host. If you do not specify this option, the default setup path is the network path: \\<mcp-hostname>\installs\cnp (that is, the CNP folder of the INSTALLS share on the MCP host where the command is executed). Optional. Specifies whether the Windows server or CNA device should reboot automatically to complete the installation. The REBOOT AUTO option reboots the Windows server or CNA device automatically (if needed) to complete the installation. The REBOOT MANUAL option specifies that the Windows server or CNA device should not be rebooted, even if a reboot is required to complete installation. If rebooting is required, the user must perform the reboot manually. If you do not specify the REBOOT option, the default is MANUAL. The Windows server or CNA device will not automatically reboot even if needed to complete the installation

75 Installing Network Services Restrictions and Limitations Disable Digital Signature Warnings If you are installing NNS on a Windows server running Windows 2000 or Windows Server 2003, disable Digital Signature warnings before issuing the REMOTEINSTALL command. This applies to all host systems except CNA devices. Use REMOTEINSTALL for Network Services Upgrades Only You can use the REMOTEINSTALL command to upgrade the level of Network Services software but not to install an earlier level (downgrade) of Network Services. Network Services aborts any attempts to perform a downgrade installation. Possible Software Failure Error Under certain conditions, performing a remote installation of Network Services (NW CNS REMOTEINSTALL command) might result in the following error: UNEXPECTED ERROR. POSSIBLE SOFTWARE FAILURE This error can occur if the Windows device has run out of disk space. This error can also occur if the Windows TEMP environment variable is not configured to specify a valid Windows temp directory. This configuration can be determined by entering the Set command from a Windows command prompt. If the TEMP environment variable is not set to a valid Windows temp directory, and the system does not contain a drive C path, this is most likely the cause of the error. Workarounds: Ensure you have enough disk space to perform the operation. It is recommended you have at least 15 megabytes (MB) of free disk space available for the installation. Ensure that the Windows TEMP environment variable is configured to specify a valid Windows temp directory. Command Examples NW CNS REMOTEINSTALL NP 7000 NETWORK SERVICES Installs Network Services on NP# The Network Services setup files should be stored in \\<mcp-host name>\installs\cnp, where < mcp-host name > is the hostname of the MCP on which the command is executed. NW CNS REMIN NP 7002 NETWORK SERVICES PATH \\REM-COMP\NetServices

76 Installing Network Services Installs Network Services on NP# 7002 using the setup files in the NetServices share on the REM-COMP network-accessible computer (which is not a local host). Note that since the path is a folder on a network share, REMOTEINSTALL requires CNP Service to log on as Administrator. NW CNS REMIN NP 7000 NETWORK SERVICES REBOOT AUTO Installs Network Services on NP# The Network Services setup files should be stored in \\<mcp-host name>\installs\cnp, where \\<mcp-host name> is the hostname of the MCP on which the command is executed. The Windows server is rebooted automatically after the installation. Example of an Invalid Command NW CNS REMIN NP 7002 NETWORK SERVICES PATH \\<mcp-hostname> \Installs\<invalid pathname> In this example, NNS resides on the local MCP host but an invalid pathname is specified. CNS will try to read the invalid path, fail to find the specified files, and send the following report: UNABLE TO LOCATE SETUP FILES AT - <string 1> - INSTALLATION ABORTED Reinstalling Network Services Network Services can be reinstalled without any special considerations. Simply reinstall the software as described in Installing Network Services earlier in this section. Restoring a Previous Release of Network Services You cannot install prior Network Services releases over the current Network Services release (a major downgrade). For example, you cannot install Network Services release 11.0 or 11.1 over Network Services release You can, however, install an earlier version of Network Services software over a later version as long as both versions are part of the same major release level (a minor downgrade). For example, you can install Network Services release 11.0 over Network Services release Use the following procedure to reinstall an earlier version of Network Services (perform a minor downgrade). Note that you cannot use the CNS REMOTEINSTALL command described earlier in this section to perform a minor downgrade. Step Action 1 Copy the installation package for the previous release that you want to install (the directory with the Network Services setup utility) into a temporary directory on the Windows server. 2 Perform all the steps except for step 4 in the Removing Network Services from the Windows Server procedure provided earlier in this section

77 Installing Network Services Step Action 3 Restore the Ethernet switch data path to the MCP host. If the Setup program established the EVLAN data path, no action is required. As a result of following the procedure to remove Network Services, the Ethernet switch will automatically be restored as the data path to the MCP host. If you manually created an LMHOSTS file to establish the EVLAN data path rather than the Ethernet switch, restore the Ethernet switch data path. See Directing Data to the Fast Ethernet Switch Data Path in Section 3 for information about manually updating the LMHOSTS file. This step enables Network Services to be reinstalled from the Client Access Services disk share. 4 Reinstall the previous version of Network Services software as described in documentation for that release

78 Installing Network Services

79 Section 3 Configuring Libra Series Native MCP or FS1800 Server Networks Your ClearPath Libra Series native MCP server or FS1800 server is preconfigured with LAN connectivity, enabling all ClearPath MCP components to communicate with each other as needed. Note that unless otherwise specified, references to Libra Series native MCP servers include the Libra Models 680 and 690. You can run your system in this standalone configuration as long as you want. However, if you want to configure your ClearPath MCP server into a larger TCP/IP (and BNA, if applicable) network, you must plan and configure several aspects of the system to meet your needs. These configuration tasks are described in this section. Additional configuration tasks are described in Section 5. Configuring a TCP/IP Network To configure your server within a TCP/IP network, perform the following tasks: Choose a name resolution strategy Prevent private IP addresses from being sent to the WINS server Configure each unit Update the MCP network configuration Choosing a Name Resolution Strategy Entities in TCP/IP networks have numerical IP addresses, such as For convenience, the networking software also allows users to refer to these entities by names, such as Underlying system software automatically maps the names to IP addresses, using one of the methods discussed in Table 3-1. Note: Only the DNS server and HOSTS files name resolution strategies apply to IPv6 networks. All four methods listed in the following table apply to traditional IPv4 networks

80 Configuring Libra Series Native MCP or FS1800 Server Networks Table 3 1. Name Resolution Strategies Method Domain name server (DNS) HOSTS files LMHOSTS files Windows Internet name server (WINS server) Description A centralized server stores mappings between TCP/IP domain names and IP addresses (can be IPv4 or IPv6 addresses). Each client calls the server and asks it to resolve names into addresses. A system administrator must maintain the mapping information at the server. Every system on the network stores files that map names to IP addresses. HOSTS files map TCP/IP domain names to IP addresses in a pure TCP/IP network. The IP addresses can be IPv4 or IPv6 addresses. HOSTS files require you to maintain redundant information on each individual workstation and server. LMHOSTS files map NetBIOS names to IPv4 addresses in a Microsoft network. As with HOSTS files, LMHOSTS files require you to maintain redundant information on each individual workstation and server. A centralized server stores mappings between NetBIOS names and IPv4 addresses. You do not need to maintain the information, because each system notifies the WINS server of its address when the system comes online. The WINS server is a typical solution in Microsoft networks, which run NetBIOS protocols on TCP/IP. Windows servers in ClearPath systems were previously shipped with the WINS service installed. Due to the issues with WINS on multihomed systems, WINS is no longer preinstalled. If you want to install the WINS server, please see NX/NET FAQ on the Support Web page and review the articles on WINS and multihomed systems in the Microsoft Knowledge Base. Note: IP addresses for the Unisys NX EVLAN adapter should not appear in WINS server

81 Configuring Libra Series Native MCP or FS1800 Server Networks A related Windows server operating system capability is the Dynamic Host Configuration Protocol (DHCP). On a network that uses DHCP, a centralized server allocates IP addresses dynamically as they are requested by clients. DHCP can be used in conjunction with the DNS and WINS server name resolution strategies. You can use DHCP with ClearPath Network Services Shared Adapters. That is, an Ethernet LAN adapter configured to use DHCP within Windows can be assigned as a Network Services Shared Adapter. However, do not use DHCP to configure the EVLAN adapter. Note that the dynamic assignment of IP address by DHCP applies only to the Shared Adapter in the Windows environment. The IP address of the MCP Server accessed via the Shared Adapter must still be statically assigned in the TCPIP Init file. For instructions to configure Windows networking values including DHCP, see the topic "Updating Windows Server Environment Values" in this section. MCP TCP/IP does not support DHCP, so if you elect to use this capability, you need to predefine a range of addresses as belonging to the MCP TCP/IP. If a WINS server is defined, the Client Access Services Name Service must be enabled (using the NW NAMESERVICE + command) to allow the MCP environment to participate in WINS name resolution. If you plan to link the ClearPath server to a network that uses another of these name resolution strategies, you might want to change the name resolution method used by ClearPath. Preventing Private IP Addresses from Being Sent to the WINS Server To prevent private IP addresses from being sent to the WINS server, set LINEMODULEID to 0 in the connection group for that particular line. Configuring Each Unit ClearPath Libra Series native MCP and FS1800 servers are preconfigured with names, addresses, and related values for each of the following components: MCP environment Windows environment (optional) Service Processor Maintenance LAN components ODWs Note: The following subsections describe how to update the configurations for your system components. None of the configuration changes take effect until you reboot your system. However, you should make all of the configuration changes necessary for each component before rebooting

82 Configuring Libra Series Native MCP or FS1800 Server Networks Updating the MCP Network Configuration When you receive your Libra Series native MCP or FS1800 server, it has preconfigured CNS and TCP/IP initialization files. These initialization files establish TCP/IP communications between the components of a ClearPath system on a "private" LAN. You must modify the preconfigured initialization files if you want to bring your ClearPath server into an existing TCP/IP network. To connect to an existing TCP/IP network, you need to get IP addresses for all addressable ClearPath components and define them to the public network. Table 3-2 lists preconfigured values for the MCP environment of your Libra Model 180 server. Table 3-3 lists preconfigured values for the MCP environment of the following: Libra Model 680 and 690, Libra Model 750, 780, and 790, and Libra Model 880 and 890 FS1800 If you are upgrading from a Libra Model 180 to a Libra Model 185 server, you have some duplicate IP addresses between the two server environments. You have to select unique IP addresses on the Libra Model 185 for the new components, including the CNA devices on the maintenance (private) LAN. These tables also provide space to enter the new values you intend to use. Preconfigured values are defined in the CNS and TCP/IP initialization files provided with your server (see Appendix A). MCP Networking Values for Libra Series Native MCP and FS1800 Servers Table 3-2 contains networking values for all Libra Series native MCP servers. It also contains networking values for the FS1800 server. Note: For Libra Model 680 and 690 servers, use the following values from this table: MCP Partition 1 and 2 values and Windows Partition A thru D values. Table 3 2. MCP Networking Values for Libra Series Native MCP and FS1800 Servers MCP Environment Preconfigured Value New Value MCP Partition 1 Host Name TCP/IP Domain Name CPMCP1 CPMCP1.SITE.CUSTOMER.COM

83 Configuring Libra Series Native MCP or FS1800 Server Networks Table 3 2. MCP Networking Values for Libra Series Native MCP and FS1800 Servers MCP Environment Preconfigured Value New Value MCP Partition 2 Host Name TCP/IP Domain Name Windows Partition A NP number CPMCP2 CPMCP2.SITE.CUSTOMER.COM 7000 on CPMCP1 VLAN IP Address Do not change (note 1) Subnet Mask Do not change (note 1) LAN Local Address (line 0) 08000B (note 2) Windows Partition B NP number 7002 on CPMCP2 VLAN IP Address Do not change (note 1) Subnet Mask Do not change (note 1) LAN Local Address (line 0) 08000B (note 2) Windows Partition C NP number 7004 on CPMCP1 VLAN IP Address Do not change (note 1) Subnet Mask Do not change (note 1) LAN Local Address (line 0) 08000B (note 2) Windows Partition D NP number 7006 on CPMCP2 VLAN IP Address Do not change (note 1) Subnet Mask Do not change (note 1) LAN Local Address (line 0) 08000B (note 2)

84 Configuring Libra Series Native MCP or FS1800 Server Networks Notes: 1. Unisys recommends that you do not change the IP Address and Subnet Mask for each EVLAN adapter. However, one reason to change these addresses is because you already have nodes in your network using the same subnet. In this case, choose an IP address that is reserved by IANA and does not conflict with the subnets in your network. 2. Line 0 is reserved for the EVLAN adapter. If you change the LAN Local Address for the MCP EVLAN adapter, do not use 08000B as the address. The Windows EVLAN adapter already uses this address

85 Configuring Libra Series Native MCP or FS1800 Server Networks Using Sample CNS and TCP/IP Initialization Files Appendix A describes a set of initialization files that are shipped with each Libra Series native MCP or FS1800 server. These CNS and TCP/IP initialization files contain default values necessary to configure a standalone TCP/IP network (without shared adapters) and to configure the server with shared adapters. The sample initialization files for the Librea Model 680 and 690 servers are: INIT/SAMPLE/CLEARPATH/CS680/CPMCP1/CNS INIT/SAMPLE/CLEARPATH/CS680/CPMCP1/TCPIP You can use these initialization files without alteration if: Your server will not connect to an external network. Your server will connect to an external network and there is no need to modify preconfigured IP addresses. For any other situation, edit the appropriate CNS and TCP/IP initialization files as necessary for your configuration or build new initialization files using the NAU and sample database dumps. The file descriptions (in Appendix A) contain remarks to assist in this editing process

86 Configuring Libra Series Native MCP or FS1800 Server Networks Using Sample Heritage Network Services (BNA) Initialization Files Appendix A describes a BNA initialization file that may be a model appropriate for a Libra Native MCP Series server. You must build the file as appropriate for your configuration. Determining Fast Ethernet and Gigabit Ethernet Information Configuration information about adapters installed in the Windows server is displayed in the Review Adapter Card Selections dialog box during installation. The following information is displayed for each adapter: Server assignment (exclusive use by the MCP environment, exclusive use by Windows TCP/IP, or shared usage) Name of the connection (as defined in the Windows operating system) Physical address CNS Line ID This information is also retained in a disk file. If you have already performed the installation, examine the <location>\adapters.txt file to determine all adapter information. If you share an adapter that was not previously bound to Windows TCP/IP, the value Unknown is displayed for the physical address. In this case, you can determine the physical address of the adapter in one of the two following ways: 1. Add the connection group specifying *Default for the local address. Once the connection group is open, use the NW Conn Inquiry for the connection group. The physical address of the adapter will be reported. 2. Use the adapter diagnostics tool within Windows, (Intel Proset, for example), to examine the adapter attributes. In this case, you must know the Window s adapter number of the shared adapter

87 Configuring Libra Series Native MCP or FS1800 Server Networks Configuring with the NAU If you do not use sample initialization files, use the Network Administrative Utility (NAU) to configure the MCP server in your existing TCP/IP (and BNA, if applicable) network. After you complete the TCP/IP configuration, the NAU automatically generates permanent initialization files that establish communication between the ClearPath MCP server and your existing TCP/IP and BNA network. In the following example, CNS, TCP/IP, and BNA initialization files are created for a network that includes: Two Windows servers (connected via CNP devices 7000 and 7002). One Gigabit Ethernet adapter in each Windows server. Customized private IP addresses to operate within an existing LAN. These addresses replace the preconfigured addresses provided in Tables 3-2 and 3-3. Note: Some of the devices used in this example are no longer supported. For additional information on using the NAU to configure a TCP/IP or BNA network, refer to the TCP/IP Implementation and Operations Guide or the BNA/CNS Implementation Guide, Vol. 2: Configuration. Notes: For TCP/IP configuration, the MCP server is the local application host. All other nodes of the ClearPath MCP complex (that is, the SCP, Windows server(s), and Fast Ethernet switch) are referred to as remote hosts. Network Services shared adapters now support Class of Service 2 for LAN based BNA connections. To define this service, simply specify CLASS = CLASS_2 on the LAN DEVICE ATTRIBUTES screen for the shared adapter. 1. On the NETWORK ATTRIBUTES (1/2) screen, identify new network entities as follows: Identify any new LANs to be added to the network. ClearPath MCP components will be defined as attached to these LANs. If you are adding a new ClearPath MCP server to the network, increase the number of application hosts in the network by one. 2. Update application host information as follows: On the NETWORK HOME MENU, enter ANH in the Choice field and transmit. If you are configuring a new ClearPath MCP system, on the APPLICATION HOST LIST screen Accept the generated name or enter a user-defined host name in the Host Name field. This example renames the NAU-generated host name to match the preconfigured host name CPMCP1. Accept the generated style or enter the style CLEARPATH in the Style field

88 Configuring Libra Series Native MCP or FS1800 Server Networks In the Total ICPs field, enter the number of ICP22 or ICP26 channel adapter(s) included with your system plus 1 for each CNP (PCI Bridge) type device. Transmit the changes. An example follows. This example illustrates a host with one ICP26 channel adapter and two CNP type devices. Sample * NAU -- APPLICATION HOST LIST * 65 ACTION: [ ] HOme PArent PRevious FInd WElcome QUit TEach REfresh Total - Node Address - Total Inbuilt Updt Level Host Name SSS CCC NNNN Style ICPs Comm Hosts Stat ID [CPMCP1 ] [ 1][ 1][ 1] [CLEARPATH ] [ 3] [ 0] [+] [ ] Specify on the application host. The APPLICATION HOST MENU is displayed. Enter HST in the Choice field. 3. On the APPLICATION HOST ATTRIBUTES screen, change the default host attribute values as follows: Enter + in the Use TCP/IP field. Enter + in the Use BNA field if you are configuring this host for use in a BNA network. Enter Y in the Define Other Application Host Attributes field. Transmit the changes. Note: The NP Heartbeat Timer attribute, which closes network connections when the host is not available, applies to ICPs and channel adapters, but is not supported for CNP devices. Sample * NAU -- APPLICATION HOST ATTRIBUTES * 145 ACTION: [ ] HOme HOSt PArent PRevious WElcome QUit TEach REfresh COpy ADd Host: CPMCP1 Generate explicit station objects? [ ] (Yes/No) BNA Mode [ ] (Independent/Dependent) Host Group Name [ ] (<Host Group Name>) Logging Local [STA] (BASic, STAndard, ALL, NONe) Logging Remote [NON] (BASic, STAndard, ALL, NONe) CNS Logging Type [ ] (Cns, Bnav2) Validate Host [NON] (STRict, USEr, NONe) Use BNA [+] (+) Use TCP/IP [+] (+) Use SNA PUT5[ ] (5) Use SNMP Agent [ ] (+) NP Heartbeat Timer [ 0] (0-60 minutes) Validate Neighbor [-] (+/-) Primary Host Name [ ] (<Primary Host Name>) Define other application host attributes? [Y] (Y/N)

89 Configuring Libra Series Native MCP or FS1800 Server Networks 4. On the APPLICATION HOSTS ATTRIBUTES MENU screen, enter OPA in the Choice field and press transmit. Sample * NAU -- APPLICATION HOST ATTRIBUTES MENU * 436 ACTION: [ ] HOme HOSt PArent PRevious WElcome QUit TEach REfresh Host: CPMCP1 VAL Validation RES Resource Library OPA Operator Authorization PAG Program Agents APG Application Group NWR Network Reports PRO Optional Line/Device Profiles TUN Tuning Parameters ATM ATM Call Attributes and Valid Call Specifications Choice: [OPA] 5. On the OPERATOR AUTHORIZATION LIST screen, define a networking command authorization profile for your MCP server usercodes. Teach text (accessible from the screen Teach action line entry) provides details on defining this profile and a description of each usercode authorization category. In the following example, the Administrator is authorized the highest category (Security) while all other usercodes are authorized a more restrictive category (Network Control). Sample * NAU -- OPERATOR AUTHORIZATION LIST * 152 ACTION: [ ] HOme HOSt PArent PRevious FInd WElcome QUit TEach REfresh COpy ADd Host: CPMCP1 Usercode (or *DEFAULT) Host Name Category = (SECurity, NETwork Control, [*DEFAULT ] [ ] [NET] SYStem Control, [ADMINISTRATOR ] [CPMCP1 ] [SEC] INQuiry, [ ] [ ] [ ] NONe, [ ] [ ] [ ] DEFaultauth, [ ] [ ] [ ] *DEfault) [ ] [ ] [ ] [ ] [ ] [ ] Note: You must define components (Windows server connections) using the information defined in Tables 3-2 or 3-3. From MCP domain 0, Windows servers A, C, E, G, and I can be configured. From MCP domain 1, Windows servers B, D, F, H, and J can be configured. 6. Define any new ICPs added in step 2 as follows: On the APPLICATION HOST MENU, enter ICP in the choice field. On the ICP ASSIGNMENTS screen: Change the ICP device number for the channel adapter to 200 and define the ICP type as ICP22 or ICP26. If you have a second channel adapter, change the second ICP device number to 201 and define the ICP type as ICP22 or ICP

90 Configuring Libra Series Native MCP or FS1800 Server Networks For each Windows server or ClearPath Network Appliance component to be configured, enter the appropriate ICP device number (refer to Tables 3-2 or 3-3) and define the ICP type as CNP. Note: For servers without HMP FastPath CIA, the specified ICP device number matches the NP number defined in the PCD. Transmit the changes. This sample screen illustrates a configuration for a ClearPath MCP server with one power domain, one ICP26 channel adapter, and two Windows servers. TEST * NAU -- ICP ASSIGNMENTS * 67 ACTION: [ ] HOme HOSt PArent PRevious FInd WElcome QUit TEach REfresh Host: CPMCP1 *In EDG mode, specify on ICP Device for configuration information Device Attachment Number ICP Type Type Attachment Identifier [ 200] [ICP26 ] [ ] [ ] [ 7000] [CNP ] [PORT] [7000 ] [ 7002] [CNP ] [PORT] [7002 ] Specify on each device to configure appropriate information for it. If you specify on an ICP22 or ICP26, the LAN ICP CONFIGURATION screen is displayed next. This document does not describe the configuration of these ICPs. If you specify on CNP, the SHARED ADAPTERS ICP CONFIGURATION screen is displayed next. 7. On the SHARED ADAPTERS ICP CONFIGURATION screen., enter the number of adapters to configure for shared access by the Windows and MCP environments. If you are configuring for EVLAN only, enter 0. If you are configuring shared adapters: In the Total LAN/ATM LANE Lines field, enter the total number of Ethernet, Fast Ethernet, and Gigabit Ethernet shared adapters you are defining. These adapters (installed in the Windows environment) will be used by the MCP for network connections via this CNP device. In the Total ATM Lines field, enter the total number of native ATM lines to be configured. Transmit the screen. The SHARED ADAPTERS CONFIGURATION screen will appear. The following example illustrates one Gigabit Ethernet port and one ATM adapter configured to support one ELAN and one native ATM port

91 Configuring Libra Series Native MCP or FS1800 Server Networks Notes: If you are configuring for Fast Ethernet port aggregation, the aggregate group of Fast Ethernet adapters is considered one shared adapter. A maximum of eight shared adapters may be configured for each Windows server. Sample NAU -- SHARED ADAPTERS ICP CONFIGURATION * 430 ACTION: [ ] HOme HOSt PArent PRevious WElcome QUit TEach REfresh Host : CPMCP1 ICP Device # : 7000 ICP Type : CNP NOTE: The total of both fields cannot exceed Total Total LAN/ATM LANE ATM Lines Lines (0-8) (0-8) [ 2 ] [ 1 ] 8. The SHARED ADAPTERS CONFIGURATION screen contains an entry for the EVLAN (ICP Line ID 0), one entry for each line defined in the Total LAN/ATM LANE Lines field of the SHARED ADAPTERS ICP CONFIGURATION screen, and one entry for each ATM shared adapter defined in the Total ATM Lines field of that screen. The following illustration shows the SHARED ADAPTERS CONFIGURATION screen for a CNP, a VNP, or an MAICP4 device with three shared adapters. Sample * NAU -- SHARED ADAPTERS CONFIGURATION * 447 ACTION: [ ] HOme HOSt PArent PRevious FInd WElcome QUit TEach REfresh Host: CPMCP1 ICP Device: 7000 ICP Type: CNP Total Number of ICP NT LAN LAN CPLAN TCP/IP SNA Static Line ID Line ID Name Local Address (+/-/S) (+/-/S) Endpts ATM ATM Endpts [ 0] [ ] [VLAN ] [08000B007000] [ ] [+] [ ] [ ] [ 1] [ 4] [LAN001] [4783CB276239] [+] [+] [ ] [ ] [ 2] [ 1] [LAN002] [ AD5C2] [+] [+] [ ] [ ] [ 3] [ 3] [ ] [ AD5D0] [ ] [+] [ ] + [ 2] The ICP Line ID values are generated automatically by the NAU. With the exception of line 0, a line can be deleted by transmitting a screen with a blanked out value in the ICP Line ID field. This action will decrement the applicable value in the SHARED ADAPTERS ICP CONFIGURATION screen. If the Line ID 0 is manually deleted, the corresponding ICP needs to be deleted on the ICP ASSIGNMENTS screen and recreated for it to have Line ID

92 Configuring Libra Series Native MCP or FS1800 Server Networks In the NT Line-ID field, enter the logical line that corresponds to this LAN connection group. If no value is supplied, the ICP Line-ID value will be used. The NT Line-ID value is emitted to the initialization file as the LINEID attribute in the ADD CONNECTIONGROUP command. In the LAN Name field, enter the LAN name that you have defined for this line (native ATM lines do not require a LAN name). In the LAN Local Address field, enter information for the EVLAN or LAN shared adapter(s). For the EVLAN, there is no need to change the default LAN Local Address value. For each shared adapter, enter the physical (MAC) address of the adapter or *DEFAULT. If you have not already gathered these addresses in Table 3-2, see Determining Fast Ethernet, Gigabit Ethernet, or ATM Adapter Information later in this section for details on how to get the LAN Local Address values from the Windows environment. If you will be using this shared adapter for access to a BNA network, you should enter the physical (MAC) address. The NAU automatically generates a value in the LAN Local Address field. This information is only used for lines that correspond to a LAN connection group. In the CPLAN field, enter + if you are configuring the shared adapter for access by a BNA network. In the TCP/IP field, enter + for each line that you want to configure as a TCP/IP connection. This enables the NAU to generate a connection group and a TCP/IP component connection for the line. Transmit the screen. Notes: 1. You must use TCP/IP, and only TCP/IP, in line 0 for the enhanced virtual LAN. 2. When defining multiple ELAN shared adapters, each ELAN must be in a separate connection group and a single ELAN cannot be used in more than one connection group. 3. If the Number of Static ATM Endpts is set to zero, the NAU still generates an ATM connection group. This group can be used to open dynamic ATM SVC connections. 9. Edit the EVLAN and shared adapter lines as follows: Return to the NETWORK HOME MENU and enter UPL in the Choice field to update LAN lines. Return to the APPLICATION HOST MENU and enter LIN in the Choice field. The LINE LIST screen is displayed. The following illustration shows the lines generated for the ICP26, the virtual LAN to each Windows server, and three shared adapters on each Windows server

93 Configuring Libra Series Native MCP or FS1800 Server Networks Sample * NAU -- LINE LIST * 81 ACTION: [ ] HOme HOSt PArent PRevious FInd WElcome QUit TEach REfresh Host: CPMCP1 Station Connection Group Line/Device Group Name Group Name ID Profile [SG_ATM70003 ][CG_ATM70003 ] [ ]/ [ ] [SG_ATM70023 ][CG_ATM70023 ] [ ]/ [ ] [SG_ICP_2000 ][CG_ICP_2000 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [SG_ICP_2001 ][CG_ICP_2001 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [SG_ICP_70000 ][CG_ICP_70000 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [SG_ICP_70001 ][CG_ICP_70001 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [ ] Sample * NAU -- LINE LIST * 81 ACTION: [ ] HOme HOSt PArent PRevious FInd WElcome QUit TEach REfresh Host: CPMCP1 Station Connection Group Line/Device Group Name Group Name ID Profile [SG_ICP_70001 ][CG_ICP_70001 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [SG_ICP_70002 ][CG_ICP_70002 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [SG_ICP_70020 ][CG_ICP_70020 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [SG_ICP_70021 ][CG_ICP_70021 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [SG_ICP_70022 ][CG_ICP_70022 ] [LAN_PROF ]/ [CMP_LAN_PROF ] [ ] Note: All CNP lines are part of Group 700x, or 800x for the ClearPath Network Appliance, where the value of x depends on the Windows server designation. This applies if you changed the ICP device number as described in step 6. The virtual LAN is always line 0. Each shared adapter will also be in the group. 10. Specify on the individual shared adapter line to configure each applicable shared adapter. 11. Do not change the default settings. No changes are required to the default settings for the ICPs, virtual LANs, or the shared adapter lines. Transmit the screen. The SHARED ADAPTER LAN LINE ATTRIBUTES screen displays next. SAMPLE NAU -- SHARED ADAPTER LAN LINE ATTRIBUTES * 431 ACTION: [ ] HOme PArent PRevious WElcome QUit TEach REfresh Host: CPMCP1 Group: SG_ICP_70001 /CG_ICP_70001 Shared Adapter Attributes: Adapter Type =>[GIGA] (ATMLane, ETHErnet, FASTethernet, GIGAbit) Adapter Name =>[ ] (<name>) Speed =>[ ] ( )

94 Configuring Libra Series Native MCP or FS1800 Server Networks 12. For each shared adapter LAN line: Enter the appropriate code in the Adapter Type field. Type codes are: ETHE for Ethernet adapters FAST for Fast Ethernet adapters GIGA for Gigabit Ethernet adapters Do not enter a value in the Adapter Name field: Adapter Name is no longer used to associate the physical adapter with a Connection Group. A Speed attribute value is not required. For LAN shared adapters, Connection Services software now forces SPEED=*DEF. This value causes the adapter hardware to return the actual speed value when the connection group is opened. Normal Speed values are: 10,000,000 bps for Ethernet adapters 100,000,000 bps for Fast Ethernet adapters 1,000,000,000 bps for Gigabit Ethernet adapters If the speed value is entered, it must match the physical adapter and the adapter types listed above. SAMPLE NAU -- SHARED ADAPTER LAN LINE ATTRIBUTES * 431 ACTION: [ ] HOme PArent PRevious WElcome QUit TEach REfresh Host: CPMCP1 Group: SG ICP_70001 /CG_ICP_70001 Shared Adapter Attributes: Adapter Type =>[GIGA] Adapter Name =>[ (ATMLane, ETHErnet, FASTethernet, GIGAbit) ] (<name>) Speed =>[ ] ( ) SAMPLE NAU -- SHARED ADAPTER LAN LINE ATTRIBUTES * 431 ACTION: [ ] HOme PArent PRevious WElcome QUit TEach REfresh Host: CPMCP1 Group: SG_ICP_70002 /CG_ICP_70002 Shared Adapter Attributes: Adapter Type =>[ATML] (ATMLane, ETHErnet, FASTethernet, GIGAbit) Adapter Name =>[ ] (<name>) Speed =>[ ] ( )

95 Configuring Libra Series Native MCP or FS1800 Server Networks When you are finished configuring LAN attributes for CNP lines and any other ICPs in your configuration, return to the APPLICATION HOST MENU. Identify IP addresses and subnet mask attributes for the ICPs as follows (refer to the information entered in Tables 3-2 or 3-3): On the APPLICATION HOST MENU, enter TCP in the Choice field. On the TCP/IP CONFIGURATION MENU, enter TIL in the Choice field. On the TCP/IP IDENTITY ADDRESS LIST screen, enter the IP address and subnet mask for each line that you are defining as a TCP/IP connection. Sample NAU -- TCP/IP IDENTITY ADDRESS LIST * 326 ACTION: [ ] HOme HOSt PArent PRevious FInd WElcome QUit TEach REfresh Host: ES1 NT NP Line Line-ID/ BIP Dev # -ID VLANID IP Address Config [ /24 ] [ ] [ /24 ] [ ] This sample screen illustrates the two channel adapter lines and the virtual LAN and shared adapter lines of the CNP devices identified as TCP/IP connections. In this example, new (private) IP addresses are being assigned for ICP device number 200 and for the shared adapter lines. Because the virtual LAN is used only for internal traffic, retain the preconfigured IP address for the line 0 of each CNP device. Preconfigured addresses are listed in Table 3-2. Note: At a minimum, you must have at least the CNP virtual LAN configured as a TCP/IP connection. 14. Specify the enterprise server TCP/IP Internet host name as follows. On the TCP/IP CONFIGURATION MENU, enter THP in the Choice field. On the TCP/IP APPLICATION HOST PARAMETERS screen, enter the host name that you want to use for the local host in the TCP/IP Internet Host Name field

96 Configuring Libra Series Native MCP or FS1800 Server Networks Sample * NAU -- TCP/IP APPLICATION HOST PARAMETERS * 327 ACTION: [ ] HOme HOSt PArent PRevious WElcome QUit TEach REfresh Host: CPMCP1 ICMP LimitedBroadCast [E] (Enabled, Disabled) RIPEnabled [+] (+/-) LANRESIL Timer [ 30] ( Sec) Retry Limit [15] (0-50) RIProuteTimeout [180] ( Sec) Maximum Connections [ 64] ( ) TCP Inact Timer [ 8] (0 24 Hours) TCP ATM KeepAlive [NO] (NEver, VCopen, NOrmal) ATM Cache Timer [7] (1 7 Minutes) MulticastDefaultAddress for IPv6 [ ] MulticastDefaultAddress for IPv4 [ ] Broadcast Filter Thresholds: Low [ ] High [ ] ( ) Disable TCP Security Support Library? [N] (Y/N) TCP Security Support Library Rules File Name: [ ] TCP/IP Internet Host Name > [cpmcp1.site.customer.com ] 15. Press Transmit twice to display the TCP/IP OPTION (1/2) screen. This screen and the second TCP/IP OPTION screen enable you to define the TCP/IP options that are enabled each time the TCP/IP network provider is initialized. These screens are shown and the options on them are described in Section 3, Configuring a TCP/IP Network Using the NAU of the TCP/IP Implementation and Operations Guide. Enable (+) or disable (-) the options on these screens as necessary. 16. Optional. To connect to a router (gateway): On the TCP/IP CONFIGURATION MENU, select TDL. On the TCP/IP DEFAULT ROUTE LIST screen, enter the IP address of your router and assign it a preference of 1. To map the Windows server host names to the IP address of the CNP device: On the TCP/IP CONFIGURATION MENU, select MAP. On the TCP/IP HOST MAPPING LIST screen, create a mapping between the Windows server name (as specified in Table 3-5) and the EVLAN path IP address (as specified in Tables 2-3 or 2-4). For example, for Windows server A on a Libra Model 180 server, you would map the name CPNTA to IP address Repeat the previous step for each Windows server in the configuration. Note: If you changed the host name of the Windows server, enter the new host name instead of the default name for instance, CPNTA). Map host names to the other system components (such as the SCP and Fast Ethernet switch)

97 Configuring Libra Series Native MCP or FS1800 Server Networks This step causes the NAU to generate a TCPIP MAPPING command in the TCP/IP initialization file. Creating this mapping enables you to use the Windows server host name with the TCPIP PING and the FTP commands to force data to take the virtual LAN data path. For details, see Directing MCP Data to the Windows Environment later in this section. * NAU -- TCP/IP HOST MAPPING LIST * ACTION: [ ] HOme HOSt PArent PRevious FInd WElcome QUit TEach Refresh Copy ADd Host: CPMCP1 TCP Host Name/Mapped IP Address [CPNTA ] [ ] [ ] * NAU -- TCP/IP MAPPING IP ADDRESS LIST * ACTION: [ ] HOme PArent PRevious FInd WElcome QUit TEach REfresh Host: CPMCP1 TCP/IP Host: CPNTA IP Address [ ] [ ]. [ ]. [ ]. [ ]. 17. On the NETWORK HOME MENU, update LAN lines and connections by entering UPL in the Choice field. 18. Use the CONSISTENCY CHECK MENU to check network consistency; then generate the network initialization files using the GENERATION MENU

98 Configuring Libra Series Native MCP or FS1800 Server Networks Updating Maintenance LAN IP Addresses The maintenance LAN is used for internal (private) traffic only; therefore, there is normally no need to change preconfigured IP addresses. However, you need to change some IP addresses if you want to run your server with other systems on a combined maintenance LAN. Such an arrangement could enable a single ODW to control multiple systems. Table 3-4 lists preconfigured IP address values for Libra Series native MCP and FS1800 server components that are connected on the maintenance LAN. The maintenance LAN must remain separate from the public LAN. If these networks are combined on the same physical network segment and subnet: The Windows servers in your system do not function correctly. Microsoft has documented problems with this configuration in Knowledge Base article , Expected Behavior of Multiple Adapters on Same Network. SCP traffic is visible on the public LAN. Therefore, inbuilt system security is compromised. ClearPath Network Appliance devices are accessible from the public LAN. Therefore, Network Appliance system security is compromised

99 Configuring Libra Series Native MCP or FS1800 Server Networks Table 3 3. Maintenance LAN IP Addresses for Libra Series Native MCP and FS1800 Series Servers Component IP Address Comment Service Control Processor 0 (SP0) Service Control Processor 1 (SP1) MCP Maintenance LAN card 1 MCP Maintenance LAN card MCP Console MCP Console LAN Modem Legacy US MCP ODT service (partitions 1-4) Client Service Engineer Laptop RAS service for international dial-in service IP address SP0 RAS service for international dial-in PPP IP address SP0 RAS service for international dial-in service IP address SP1 RAS service for international dial-in PPP IP address SP1 IMS/ODW clients direct connect to private LAN Private LAN for SubDib Private LAN for SubDib Private LAN for SubDib thru 18 ODT service on FC3-IOP starting with Libra 680/690. Two addresses per partition (for resiliency) SP SP SP SP thru 59 Workstations on private LAN Intel Node part 1 (see Note) Intel Node part 2 (see Note) Intel Node part 3 (see Note) Private LAN for SubDib thru thru Intel Node part 4 thru 8 (see Note) Console Manager SubDib Intel Node part

100 Configuring Libra Series Native MCP or FS1800 Server Networks Table 3 3. Maintenance LAN IP Addresses for Libra Series Native MCP and FS1800 Series Servers Component IP Address Comment Console Manager SubDib Console Manager SubDib Intel Node part Intel Node part 3 Console Manager SubDib thru thru 108 Intel Node part 4 thru 8 MCP Partition 1 Private LAN access MCP Partition 1 Private LAN access MCP Partition 2 Private LAN access MCP Partition 2 Private LAN access MCP Partition 3 Private LAN access MCP Partition 3 Private LAN access MCP Partition 4 Private LAN access MCP Partition 4 Private LAN access MCP Alternate Partition 1 Private LAN via CNA1 for Libra 180 upgrade MCP Alternate Partition 1 Private LAN via CNA3 for Libra 180 upgrade MCP Alternate Partition 2 Private LAN via CNA2 for Libra 180 upgrade MCP Alternate Partition 2 Private LAN via CNA4 for Libra 180 upgrade MCP ESR SAS-IOP1 on Libra Model MCP ESR SAS-IOP2 on Libra Model MCP ESR MCP ESR MCP ESR MCP ESR MCP ESR MCP ESR MCP ESR MCP ESR MCP ESR MCP ESR Unisys Installer s Notebook May be used interchangeably with.20 CNA Base Address Used for CNA configuration

101 Configuring Libra Series Native MCP or FS1800 Server Networks Table 3 3. Maintenance LAN IP Addresses for Libra Series Native MCP and FS1800 Series Servers Component IP Address Comment eportal Controller 1-8 Private LAN Crypto Co-processor (CCP) 1 thru 8 JProcessor (JDP) 1 thru 8 Private LAN Managed Switch B Private LAN Managed Switch A Secure Maintenance Device thru thru thru Applies to all MCP systems

102 Configuring Libra Series Native MCP or FS1800 Server Networks Procedure for Changing Windows Server and ODW Maintenance IP Addresses At a system terminal or ODW, use the following procedure to change IP addresses for each Windows server or ODW on the maintenance LAN: Step Action 1 With Windows, open the Windows Network Connections manager (right click on My Network Places and choose Properties). 2 Note: For the integrated Windows server environment, the Unisys EVLAN adapter and normal system Fast Ethernet adapter may also be displayed. Do not make any changes to the TCP/IP configuration for the EVLAN adapter. See Updating Windows Server Environment Values later in this section for information on changing the IP address of the normal system Fast Ethernet adapter. a. In the Local Area Connections list, select the connection for the preinstalled network interface adapter. b. With the connection selected, right click and choose Properties. Note: For each Maintenance LAN connection, ensure that only the Internet Protocol (TCP/IP) box is checked. The Client for Microsoft Networks and File and Print Sharing boxes should not be checked. (Exception: Check these boxes only if you are mapping network drives from ClearPath Network Appliance devices to this Windows server. They are not enabled by default.) c. In the Connection Properties screen, select Internet Protocol (TCP/IP) and then click the Properties button. The current assigned maintenance LAN IP address and Subnet Mask are displayed. 3 To change the IP address and Subnet Mask for this Windows server or ODW: a. In the TCP/IP Properties box (IP Address tab), select Use the Following IP Address and then enter the new IP address for this Windows server or ODW environment. b. Change the Subnet Mask to or your own mask if you have changed it. 4 When you are finished with network configuration, choose OK to exit TCP/IP Properties and OK to exit Connection Properties. The IP address changes take effect without reboot

103 Configuring Libra Series Native MCP or FS1800 Server Networks Updating Windows Server Environment Values Table 3-4 lists preconfigured values for all Windows servers in Libra Series native MCP and FS1800 Series servers. These values pertain to the public LAN. This table also provides space to enter any new values you intend to use. Table 3 4. Windows Environment Values for Libra Series Native MCP and FS1800 Servers Attribute Preconfigured Value New Value Windows Server A IP Address (optional on Libra Model 185) Subnet Mask Name Workgroup Name Name for Windows registration Company for Windows registration License agreement XVision license number (not included on Libra Native MCP Series) CPNTA CLEARPATH None None Per-seat licensing with ten client licenses Included in the XVision package that came with your software order Windows Server B IP Address (optional on Libra Model 185) Subnet Mask Name Workgroup Name Name for Windows registration Company for Windows registration License agreement XVision license number (not included on Libra Native MCP Series) CPNTB CLEARPATH None None Per-seat licensing with ten client licenses Included in the XVision package that came with your software order

104 Configuring Libra Series Native MCP or FS1800 Server Networks Table 3 4. Windows Environment Values for Libra Series Native MCP and FS1800 Servers Attribute Preconfigured Value New Value Windows Server C IP Address (optional on Libra Model 185) Subnet Mask Name Workgroup Name Name for Windows registration Company for Windows registration License agreement CPNTC CLEARPATH None None Per-seat licensing with ten client licenses Windows Server D IP Address (optional on Libra Model 185) Subnet Mask Name Workgroup Name Name for Windows registration Company for Windows registration License agreement CPNTD CLEARPATH None None Per-seat licensing with ten client licenses

105 Configuring Libra Series Native MCP or FS1800 Server Networks Configuring Windows Servers At the system terminal, use the following procedure to configure the name resolution strategy, IP addresses, workgroup/domain name and computer name for each Windows server. For information on workgroups and domains, refer to Integrating Your Server with Microsoft Networks in Section 6. You can also use this procedure to configure networking values on any user workstation or ODW that is running Windows. Note that at the end of this procedure you will be asked to restart Windows for the new values to take effect. Step Action 1 Open the Windows Network Connections manager (from the desktop, right click on My Network Places and choose Properties). 2 This step displays properties of the preinstalled public network (Fast Ethernet) adapter. If preconfigured values are still in use, these adapters can be identified by their IP address values of x. Note: For the integrated Windows server environment, the Unisys EVLAN adapter and the maintenance LAN adapter may also be displayed. Do not make any changes to the TCP/IP configuration for the EVLAN adapter. See Updating Maintenance LAN IP Addresses earlier in this section for information on changing the IP address of the maintenance LAN adapter. 1. In the Local Area Connections list, select the connection for the preinstalled public network (Fast Ethernet) adapter. 2. With the connection selected, right click and choose Properties. 3. In the Connection Properties screen, select Internet Protocol (TCP/IP) and then click the Properties button to display the Internet Protocol TCP/IP Properties dialog box. 3 To change the IP address and Subnet Mask for the Windows server: The currently assigned IP address, Subnet Mask, and Default Gateway information is displayed. If you are using DHCP, select Obtain an IP address automatically. This enables automatic DHCP configuration and suppresses the IP address and Subnet Mask boxes. (Do not enable DHCP on the EVLAN adapter.) If you are not using DHCP, select Use the following IP address and click the Advanced button to display Advanced TCP/IP Settings: Select the IP Settings tab. You can enter a new IP address or modify the IP address for this Windows server environment. The Subnet Mask field usually defaults intelligently to an appropriate value. Each bit determines whether the corresponding bits in the address refer to the subnet or the unique ID. You can also specify one or more Default Gateways if necessary. Each gateway should be the address of a router that is visible to the system. Choose OK to redisplay the Internet Protocol (TCP/IP) Properties dialog box

106 Configuring Libra Series Native MCP or FS1800 Server Networks Step Action 4 Use the applicable Properties dialogs to define your DNS and WINS name resolution strategies. For DNS, you can specify DNS server addresses DNS service search order Suffix information for use with unqualified names DNS registration information For WINS, you can specify: Primary WINS and Secondary WINS addresses Enable or disable LMHOSTS lookup Import LMHOSTS file information Additional WINS configuration parameters Choose OK or Close to save the network configuration changes and exit Connection Properties. Some changes (for example, IP address changes) take effect without reboot. Others may require a reboot. 5 Use this step to change your computer name and the workgroup or domain in which it appears. You can assign a workgroup or a Microsoft Networking domain (but not both). From the desktop, right click on My Computer and choose Properties. Select the Identification tab to change your computer name and the workgroup or domain in which it appears. You can assign a workgroup or a Microsoft Networking domain (but not both). 1. Click the Change button. The Identification Changes screen appears. 2. To assign a workgroup a. Click the Workgroup option button. b. Type a workgroup name. c. Click OK. d. The system displays a message welcoming you to the workgroup or domain. Click OK

107 Configuring Libra Series Native MCP or FS1800 Server Networks Step 5 (cont) 3. To assign a domain Action a. Click the Domain option button. b. Type a domain name. c. Optionally, create an account by selecting the Create a Computer Account in the Domain check box and filling in Username and Password. d. Click OK. e. The system displays a message welcoming you to the workgroup or domain. Click OK. 4. To change the computer name a. Type the new computer name. If your ClearPath system has two Windows environments, you should assign a name different from that of the other Windows environment. Click OK. b. A message is displayed indicating that the computer name was changed. Click OK. 6 Use Connection Manager to view the list of connections for installed adapters. Use Add/Remove Hardware wizard (via Control Panel) to add, remove adapters. Use Device Manager (via Control Panel) to configure, or update adapters. Select Local Area Connection Properties (via Connection Manager) to see a list of installed components (for example, TCP/IP) or to add, remove, configure, components. You can also enable or disable a component for that connection using the check box. 7 The network configuration changes were saved in step 4 above

108 Configuring Libra Series Native MCP or FS1800 Server Networks Updating ODW and User Workstation Values For each ODW or user workstation, you must configure the name resolution strategy, IP address, and name values on that workstation. Preconfigured ODW addresses (on the public LAN) have IP addresses in the following range: through ODWs must also be visible on the maintenance LAN. Therefore, you may also need to Configure IP addresses for ODWs on the maintenance LAN Configure the SCP(s) to recognize the IP address of each ODW For information about configuring the maintenance LAN, see Updating Maintenance LAN IP Addresses earlier in this section

109 Configuring Libra Series Native MCP or FS1800 Server Networks Examining or Updating Network Services Values Use the following procedure to examine or update information for: Network Services NX EVLAN and Network drivers NP Unit Number TCP/IP configuration for shared Fast Ethernet ports Use step 5 of this procedure only for shared Fast Ethernet ports or Gigabit Ethernet ports. To configure non shared adapters, refer to Updating Windows Environment Values earlier in this section. Refer to Tables 2-2, or 2-3 for preconfigured values applicable to your Libra Series native MCP or FS1800 server. Note: Unisys recommends that you do not change the IP Address information for the virtual LAN in step 5. However, one reason to change these addresses is because you already have nodes in your network using the same subnet. In this case, choose an IP address that is reserved by IANA and does not conflict with the subnets in your network. Step Action 1 Start the Control Panel application and open Computer Management (under Administrative Tools). A shortcut from the desktop is to right-click My Computer and select Manage. 2 To examine the status of Unisys Network Services, Open Services (under Computer Management / Services and Applications). The current operating status and startup behavior of all installed services, including Unisys Network Services, is displayed. Upon installation of Network Services with the Setup program, the startup type is set to Automatic. Do not change it. 3 To examine the status of the Unisys Network Services drivers, Open Drivers (under Computer Management / System Information / Software Environment ). The current operating status and the startup behavior of all installed drivers, including Unisys Network Services drivers, is displayed. It is recommended that you do not change any settings for installed drivers. Do NOT stop or start any of the Unisys Network Services drivers

110 Configuring Libra Series Native MCP or FS1800 Server Networks Step Action 4 Examine or update the CNS Line ID and other properties for shared adapters using Connection Properties as follows. a. Access the configuration parameters for a shared adapter as follows: 1) Open the Windows Network Connections manager (from the desktop, right click on My Network Places and choose Properties). 2) In the Local Area Connections list, select the connection for a shared adapter, right click and choose Properties. 3) In the Connection Properties screen, select Unisys ClearPath Network Services and press the Properties button. 4) On the Shared Adapter tab, examine and (if applicable) update the assigned CNS Line ID and other properties. These include: Forward RIP Frames to MCP (Ethernet type adapters only) Unknown IP Frame Route (Ethernet type adapters only) See Shared Adapter Properties in Section 2 for more information. 5) On the Network Processor tab, examine and (if applicable) update the NP unit number. This is a common property value for all shared adapters and the EVLAN. For information about the appropriate value, see Table ) If you change any values you must reboot for the change to take effect. b. Choose OK to accept the parameters. Note: If you want to disable MCP access to the shared adapter or return an adapter to shared status, refer to Reconfiguring a Shared Adapter in Section 2. To examine or update other configuration parameters for Network Services, you must run Setup and select the option "Update Configuration Options Only". For information, see "Reconfiguring " in Section 2. 5 To examine or update TCP/IP addresses for EVLAN or Shared Adapters, access TCP/IP Properties information as follows: a. Access TCP/IP properties information as follows: 1) In the Windows Network Connections manager, select the Connection for one of the following adapters: Unisys Network EVLAN Adapter. Third-party adapter assigned to the shared adapter of interest. 2) With the Connection selected, right click and choose Properties. 3) In the Connection Properties screen, select Internet Protocol (TCP/IP) and then Click the Properties button. The current assigned IP address and Subnet Mask are displayed. b. To examine or update the IP configuration address of the EVLAN adapter, select Unisys NX EVLAN Adapter from the Adapter list to view the current settings: 1) Do not change the IP address and Subnet Mask because Network Services has no connections outside the MCP and Windows environments. 2) Verify that the Primary WINS Server and the Secondary WINS Server boxes are blank. 3) Choose OK to accept the parameters

111 Configuring Libra Series Native MCP or FS1800 Server Networks Step 5 (cont) Action c. To examine or update the IP configuration of a shared adapter address: 1) In the Windows Network Connections manager, select the Fast Ethernet or Gigabit Ethernet adapter associated with the shared adapter connection of interest. 2) With the connection selected, right click and choose Properties. 3) In the Connection Properties screen, select Internet Protocol (TCP/IP) and click the Properties button; the currently assigned IP address, Subnet Mask, and Default Gateway information will be displayed. 4) Select the IP Settings tab. 5) Enter the IP address the Windows server s TCP/IP will use with this adapter. 6) Choose OK to accept the parameters. d. Exit the Control Panel and restart the system if any settings changed. Exit Network Configuration: Notes: 1) Exit Connection Properties. Some changes (e.g. IP address changes) take effect without reboot. Others may require a reboot. 1. The < location>\adapters.txt file defines the Janus Surrogate Adapter assigned to each shared adapter. 2. Only the Windows server IP address is configured from the Windows operating system. To change the MCP server s IP address for a shared Fast Ethernet port, refer to Updating the MCP Network Configuration earlier in this section

112 Configuring Libra Series Native MCP or FS1800 Server Networks Manually Directing Windows Data to the MCP Environment Data moving between the Windows and MCP environments can transit either the EVLAN data path or the Fast Ethernet switch. However, when it is installed and running, Windows data to the MCP is automatically directed through the EVLAN. Section 2 fully describes this automatic path configuration process. You can manually force the Windows server operating system to use a particular path (EVLAN or Fast Ethernet switch) to the MCP host. You do this by placing appropriate IP address and name information in local name resolution files. These local files are: LMHOSTS This is an ASCII text file that resolves NetBIOS computer names to IP addresses (must be IPv4 addresses). NetBIOS names are used by the Windows NetBIOS interface and by some TCP/IP programs. When present, the NetBIOS name cache, which is preloaded through the LMHOSTS file, overrides the WINS server to reduce the time required for name resolution. A pair of associated files (LMHOSTS.ORG and LMHOSTS.CNP) are created by software during the Setup process. See How the Setup Program Manages the LMHOSTS File in Section 2 for information about how these files are used. HOSTS This is an ASCII text file that resolves DNS-formatted names used by TCP/IP utilities such as PING, Telnet, and FTP. When present, the HOSTS file overrides any configured DNS servers to reduce the time required for name resolution. The HOSTS file can resolve IPv4 or IPv6 addresses to names. Use the following procedures to manually direct data over a particular data path

113 Configuring Libra Series Native MCP or FS1800 Server Networks Directing Data through the EVLAN Data Path For the Windows operating system to use the EVLAN path to the MCP host, NetBIOS Name Resolution must resolve the MCP host name to the EVLAN IPv4 address assigned to the CNP device. Complete the following procedure for each Windows server. Step Action 1 Verify that the virtual LAN is installed, configured, and running on your ClearPath server. 2 If any shares on the MCP server are mapped to drives, use Explorer to disconnect them. 3 Log on to the Windows server at the System Terminal (ST). 4 Using Notepad, create an LMHOSTS file. Either create a new file or, if you want, use the sample LMHOSTS file located at %systemroot%\system32\drivers\etc\lmhosts.sam. Note: To use the sample file, update an example line. Then remove the pound sign from the beginning of the updated line. The LMHOSTS file must include the following parameters: where: <IP address> <MCP host name> #PRE <IP address> is the CNP-based IP address of the MCP host (refer to Tables 3-2 or 3-3). <MCP host name> is the current host name, which may have been changed from the preconfigured value shown in the example. Example Assume a Libra Model 180 complex with two power domains and two Windows servers. To direct data from Windows server A to the MCP environment, type CPMCP1 #PRE To direct data from the Windows server B to the MCP environment, type CPMCP1 #PRE The #PRE extension directs Windows to enter this address in the NetBIOS name cache. Windows will use this EVLAN IP address (without accessing WINS) for sending data to the designated MCP host. 5 Save the LMHOSTS file as %systemroot%\system32\drivers\etc\lmhosts

114 Configuring Libra Series Native MCP or FS1800 Server Networks Step Action 6 If DNS servers are not configured, there is no need to configure a HOSTS file. Skip to step 7. Otherwise, create a new file (or use the sample HOSTS file located at %systemroot%\system32\drivers\etc\hosts.sam) and copy the LMHOSTS file entries (created in step 3) into the HOSTS file. Note: The HOSTS file does not support the use of keyword extensions such as #PRE. These extensions are ignored (recognized as comments). 7 Save the HOSTS file as %systemroot%\system32\drivers\etc\hosts 8 To complete the data path redefinition process, perform either of the following tasks: Reboot the Windows server, or Perform the following steps: a. Enter nbtstat -R at the MS-DOS command prompt on the Windows server. This command purges and refreshes the NetBIOS name cache. b. Enter netstat 10 at the MS-DOS command prompt on the Windows server. This command form continuously displays (at 10 second intervals) all active TCP/IP connections. Initially, the MCP server connection will probably be in a Time_Wait state. For example: TCP CP-NTA:1233 CP-MCP1:nbsession TIME_WAIT Note: Per TCP standard, the original connection remains active in a Time_Wait state for up to two Maximum Segment Lifetimes (MSL) after a connection closure is requested. Typically, this Time_Wait period will last approximately four minutes. c. Monitor the returned TCP/IP connection status until the MCP server connection is no longer on the list. d. Press Ctrl+C to terminate the netstat command sequence. e. Now, traffic from the Windows server to the MCP server will use the EVLAN data path

115 Configuring Libra Series Native MCP or FS1800 Server Networks Directing Data Through the Ethernet Switch Data Path For the Windows operating system to use the Ethernet switch data path to the MCP host, NetBIOS Name Resolution must resolve the MCP host name to the Ethernet switch IP address. To manually direct data to use the Ethernet switch data path, complete the following procedure for each Windows environment in your configuration. Step Action 1 If any shares on the MCP server are mapped to drives, use Explorer to disconnect them. 2 On the MCP server, issue the appropriate command from an ODT window: NW TCPIP MAPPING (disables mapping to Windows server A) NW TCPIP MAPPING (disables mapping to Windows server B) NW TCPIP MAPPING (disables mapping to Windows server C) NW TCPIP MAPPING (disables mapping to Windows server D) NW TCPIP MAPPING (disables mapping to Windows server E) NW TCPIP MAPPING (disables mapping to Windows server F) NW TCPIP MAPPING (disables mapping to Windows server G) NW TCPIP MAPPING (disables mapping to Windows server H) NW TCPIP MAPPING (disables mapping to Windows server I) NW TCPIP MAPPING (disables mapping to Windows server J) 3 Log on to the Windows server at the System Terminal (ST). 4 Using Notepad, create an LMHOSTS file, or modify the existing file. a. Include the following parameters in the file: <IP address> <MCP host name> #PRE where: <IP address> is address of NP 200 or NP 201 in the MCP host. This address may have been changed from the preconfigured value shown in the example (refer to Tables 3-2 or 3-3). <MCP host name> is the current host name, which may have been changed from the preconfigured value shown in the example. b. Enter #### before the following line (this changes the statement into a comment): #INCLUDE... lmhost.cnp Example To direct data from any Windows server to the MCP environment, type CPMCP1 #PRE The #PRE extension directs Windows to use the Fast Ethernet switch address first for sending data to the designated MCP host. 5 Save the LMHOSTS file as %systemroot%\system32\drivers\etc\lmhosts

116 Configuring Libra Series Native MCP or FS1800 Server Networks Step Action 6 If DNS servers are not configured, there is no need to configure a HOSTS file. Skip to step 8. Otherwise, create a new file (or use the sample HOSTS file located at %systemroot%\system32\drivers\etc\hosts.sam) and update the file as follows: a. Copy all LMHOSTS file entries (created in step 4) into the HOSTS file. b. Ensure that there are no statements for the EVLAN data path. If necessary, remove (or comment out) statements that map to the EVLAN data path. Note: The HOSTS file does not support the use of keyword extensions such as #PRE. These extensions are ignored (recognized as comments). 7 Save the HOSTS file as %systemroot%\system32\drivers\etc\hosts 8 To complete the data path redefinition process, perform either of the following tasks: Reboot the Windows server, or Perform the following steps: a. Enter nbtstat -R at the MS-DOS command prompt on the Windows server. This command purges and refreshes the NetBIOS name cache. b. Enter netstat 10 at the MS-DOS command prompt on the Windows server. This command form continuously displays (at 10 second intervals) all active TCP/IP connections. Initially, the MCP server connection will probably be in a Time_Wait state. For example: TCP CP-NTA:1233 CP-MCP1:nbsession TIME_WAIT Note: Per TCP standard, the original connection remains active in a Time_Wait state for up to two Maximum Segment Lifetimes (MSL) after a connection closure is requested. Typically, this Time_Wait period will last approximately four minutes. c. Monitor the returned TCP/IP connection status until the MCP server connection is no longer on the list. d. Press Ctrl+C to terminate the netstat command sequence. e. Now, traffic from the Windows server to the MCP server will use the Fast Ethernet switch data path

117 Configuring Libra Series Native MCP or FS1800 Server Networks Directing MCP Data to the Windows Environment In most cases, dialogs are initiated from the Windows server environment to the MCP. In the following cases, however, data transfers are initiated from the MCP environment: When you issue an NW TCPIP PING command to determine if a remote host is available When you use the File Transfer Protocol (FTP) command In these cases and any other MCP-initiated dialogs, you need to specify either the IP address or the host name for the applicable Windows server. Using the NW TCPIP PING Command If you use the IPADDR option of the NW TCPIP PING command, enter the exact address shown in the example. If you use the HOSTNAME option of the command, enter the current host name, which may have been changed from the preconfigured value shown in the example. For example: To direct data from CPMCP1 to Windows server A via the EVLAN, enter NW TCPIP PING IPADDR = or NW TCPIP PING HOSTNAME = CPNTA Note: The TCPIP PING command HOSTNAME option will only work if the hostname has been mapped to the IP address of the Windows server. This mapping is provided in the MCP environment s default TCP/IP initialization file. However, if you changed your MCP configuration (as specified in Updating the MCP Configuration, earlier in this section), this mapping may have been removed. To direct data from CPMCP1 to Windows server A via the Fast Ethernet switch, enter NW TCPIP PING IPADDR = <external IP address> Note: Default Windows server (shared adapter) address is For More Information For more information on the automated procedure for directing data to take the virtual LAN data path, see Installing and How the Setup Program Manages the LMHOSTS File in Section

118 Configuring Libra Series Native MCP or FS1800 Server Networks Specifying the WINS Server Address Windows servers in ClearPath systems were previously shipped with the WINS service installed. Due to the issues with WINS on multihomed systems, WINS is no longer preinstalled. If you want to install the WINS server, please see NX/NET FAQ on the Support Web page and review the articles on WINS and multihomed systems in the Microsoft Knowledge Base. If you have a WINS server somewhere in your network, specify its IP address to each Windows server within the ClearPath system. You can enter this address at the WINS Address tab of the TCP/IP Properties Sheet. You must also inform Client Access Services of the WINS server address. The following table describes this procedure Step Action 1 At the system terminal, switch to or initiate the Administration Center application. If necessary, connect to the MCP server specifying its hostname and a privileged usercode, such as ADMINISTRATOR. 2 From the Resources menu, choose Create or Modify. 3 Another menu appears. Choose Server Properties. 4 On the Server Properties on <Server Name> screen a. Select the WINS Server tab. b. Type a primary WINS server IP address and/or secondary WINS server IP address. c. Choose Modify. 5 Administration Center displays a message stating that the change will not take effect until you save the configuration. Choose OK. 6 From the Resources menu, choose Save. 7 Administration Center displays a message, asking if you want to make the changes permanent. Choose Yes. For More Information For more information on WINS configuration, see the WINS Manager help

119 Configuring Libra Series Native MCP or FS1800 Server Networks Rebooting the System Environments If you have not already done so, you should reboot the MCP server, each Windows server, and the Fast Ethernet switch as described in the following table. The configuration changes for each of these environments do not take effect until they are restarted. Step Action 1 Reboot the Windows server by following the procedure in Section 7, Stopping and Starting the Windows Server. 2 Reboot the MCP server. In the ODT window, type the command??phl. Verifying the System Networking Configuration Verify the system networking environment configuration as follows: Step Action 1 Be sure the ST switch is in the Windows setting. Verify that SYCON windows appear on the Windows screen. 2 At the ST, switch to or initiate the Administration Center application. If necessary, connect to the MCP server specifying its hostname and a privileged usercode, such as ADMINISTRATOR. 3 Verify that the application connects to the MCP by seeing that the MCP server name appears in the Connected MCP Server(s) dialog box on the toolbar. 4 Terminate Administration Center. Controlling the Maximum Transmission Unit (MTU) Value The USERFCMTU option provides control of the maximum transmission unit (MTU) value for TCP/IP. This option is set by default on ClearPath Series servers. As a result, TCP/IP uses a maximum transmission size of 536. This low value is chosen to comply with RFC 1122, and might help to prevent fragmentation of a datagram by intermediate gateways along the path. Note: Before making any changes to the USERFCMTU option, you should determine the minimum MTU value of all gateways and nodes in the network. If you reset the USERFCMTU option, you can use a larger MTU size that matches the type of physical LAN in use. As the system is originally shipped, the connecting medium and MTU value is an Ethernet cable with an MTU value of 1496 bytes. To set the USERFCMTU option, enter the following OI command: NW TCPIP OPTION + USERFCMTU

120 Configuring Libra Series Native MCP or FS1800 Server Networks To reset (clear) the USERFCMTU option, enter the following OI command: NW TCPIP OPTION - USERFCMTU Note: 1. You can also use the NAU to define the USERFCMTU option during the MCP network configuration process. This function was described in the Configuring with the NAU paragraph earlier in this section. 2. The USERFCMTU applies only to IPv4. IPv6 uses PathMTU to address the MTU size question. Refer to the TCP/IP Implementation and Operations Guide for information on PMTU Verification Interval. Viewing the RESET Reports The TCP/IP software in the MCP environment enters RESET reports in a table whenever remotely initiated RESET actions are received. To view this table, enter the following command: NW TCPIP DISPLAY TABLE RESETRPTS

121 Section 4 Configuring Virtual Machine for MCP Server Networks This section describes how to integrate the following Virtual Machine for MCP (VMMCP) servers into a TCP/IP network: Libra Model 400, Libra Model 450, Libra Model 460, and Libra Model 4080 and 4090 FS1700 ClearPath MCP servers are preconfigured with LAN connectivity, enabling all ClearPath components within a server to communicate with each other as needed. You can run your server in this standalone configuration but if you want to integrate your ClearPath server into a larger TCP/IP network (and Heritage Network Services (BNA) network, if applicable), you must plan and configure several aspects of the server to meet your needs. To integrate your server into a TCP/IP network, you must be familiar with the following tasks: Choosing a name resolution strategy Configuring each unit Manually directing Windows data to the MCP environment 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

122 Configuring Virtual Machine for MCP Server Networks Choosing a Name Resolution Strategy Entities in TCP/IP networks have numerical IP addresses, such as For convenience, the networking software also allows users to refer to these entities by names, such as Underlying system software automatically maps the names to IP addresses, using one of the strategies discussed in Table 4-1. Note: Only the DNS server and HOSTS files name resolution strategies apply to IPv6 networks. All four methods listed in the following table apply to traditional IPv4 networks. Table 4 1. Name Resolution Strategies Method Domain name server (DNS) HOSTS files LMHOSTS files Windows Internet name server (WINS server) Description A centralized server stores mappings between TCP/IP domain names and IP addresses (can be IPv4 or IPv6 addresses). Each client calls the server and asks it to resolve names into addresses. A system administrator must maintain the mapping information at the server. Every system on the network stores files that map names to IP addresses. HOSTS files map TCP/IP domain names to IP addresses in a pure TCP/IP network. The IP addresses can be IPv4 or IPv6 addresses. HOSTS files require you to maintain redundant information on each individual workstation and server. LMHOSTS files map NetBIOS names to IPv4 addresses in a Microsoft network. As with HOSTS files, LMHOSTS files require you to maintain redundant information on each individual workstation and server. A centralized server stores mappings between NetBIOS names and IPv4 addresses. You do not need to maintain the information, because each system notifies the WINS server of its address when the system comes online. The WINS server is a typical solution in Microsoft networks, which run NetBIOS protocols on TCP/IP. Windows servers in ClearPath systems were previously shipped with the WINS service installed. Due to the issues with WINS on multihomed systems, WINS is no longer preinstalled. If you want to install the WINS server, please see NX/NET FAQ on the Support Web page and review the articles on WINS and multihomed systems in the Microsoft Knowledge Base. Note: IP addresses for the Unisys NX EVLAN adapter should not appear in WINS server

123 Configuring Virtual Machine for MCP Server Networks A related Windows Server capability is the Dynamic Host Configuration Protocol (DHCP). On a network that uses DHCP, a centralized server allocates IP addresses dynamically as they are requested by clients. This method is available only on Microsoft networks. DHCP can be used in conjunction with the DNS and WINS server name resolution strategies. DHCP can be used with ClearPath Network Services Shared Adapters. That is, an Ethernet LAN adapter configured to use DHCP can be assigned as a Network Services Shared Adapter. However, do not use DHCP to configure the EVLAN adapter. Note that the dynamic assignment of IP address by DHCP applies only to the Shared Adapter in the Windows environment. The IP address of the MCP Server accessed via the Shared Adapter must still be statically assigned in the TCPIP Init file. For instructions to configure Windows networking values including DHCP, see the topic "Updating Windows Environment Values" in this section. MCP TCP/IP does not support DHCP, so if you elect to use this capability, you need to predefine a range of addresses as belonging to the MCP TCP/IP. If a WINS server is defined, the Client Access Services Name Service must be enabled (using the NW NAMESERVICE + command) to allow the MCP environment to participate in WINS name resolution. If you plan to link the ClearPath Network Services system to a network that uses another of these name resolution strategies, you might want to change the name resolution method used by ClearPath. Preventing Private IP Addresses from Being Sent to the WINS Server To prevent private IP addresses from being sent to the WINS server, set LINEMODULEID to 0 in the connection group for that particular line. Configuring Each Unit The ClearPath Network Services system is preconfigured with names, addresses, and related values for each of the following components: MCP environment Windows environment Note: The following subsections describe how to update the configurations for your system components. None of the configuration changes take effect until you reboot your system. However, you should make all of the configuration changes necessary for each component before rebooting your system

124 Configuring Virtual Machine for MCP Server Networks Updating the MCP Network Configuration When you receive a ClearPath system, it has preconfigured CNS and TCP/IP initialization files. These initialization files establish TCP/IP communications between the components of a ClearPath system on a "private" LAN. You must modify the preconfigured initialization files if you want to bring your ClearPath system into an existing TCP/IP network. To connect to an existing TCP/IP network, you need to get IP addresses for the addressable ClearPath components and define them to the public network. Table 4-2 lists preconfigured values for the MCP environment in VMMCP servers. Table 4-3 lists preconfigured values for the MCP environment in Libra 4000 servers. If you are installing multiple emulated network processors (NPs), use the values in this table as many times as needed. Table 4-2 and Table 4-3 also provide space to enter the new values you intend to use. Preconfigured values are defined in the CNS and TCP/IP initialization files provided with your server (described in Appendix A). Note: Before your Windows 2000 partition can communicate with the VMMCP server partition, you must assign an IP address and subnet mask appropriate for your networking environment

125 Configuring Virtual Machine for MCP Server Networks Table 4 2. MCP Networking Values for VMMCP Servers MCP Environment Preconfigured Value New Value Host Name TCP/IP Domain Name CPMCP1 CPMCP1.SITE.CUSTOMER.COM NP number (optional) 200 IP Address Subnet Mask LAN Local Address 08000B MAICP4 number 210 Do not change EVLAN IP Address Do not change (note 1) Subnet Mask Do not change (note 1) LAN Local Address (line 0) 08000B (note 2) Shared Adapter #1 IP Address (for LX7100 or CS7201 ) Subnet Mask (for LX7100 or CS7201) LAN Local Address (line 1) (note 3) Adapter Name (line 1) (note 3) NT Line-ID (note 3) Shared Adapter #2 IP Address (note 4) Subnet Mask LAN Local Address (line 2) (note 3) Adapter Name (line 2) (note 3) NT Line-ID (note 3) Shared Adapter #3 IP Address (note 4) Subnet Mask LAN Local Address (line 3) (note 3) Adapter Name (line 3) (note 3) NT Line-ID (note 3)

126 Configuring Virtual Machine for MCP Server Networks Table 4 2. MCP Networking Values for VMMCP Servers MCP Environment Preconfigured Value New Value Shared Adapter #4 IP Address (note 4) Subnet Mask LAN Local Address (line 4) (note 3) Adapter Name (line 4) (note 3) NT Line-ID (note 3) Shared Adapter #5 IP Address (note 4) Subnet Mask LAN Local Address (line 5) (note 3) Adapter Name (line 5) (note 3) NT Line-ID (note 3) Shared Adapter #6 IP Address (note 4) Subnet Mask LAN Local Address (line 6) (note 3) Adapter Name (line 6) (note 3) NT Line-ID (note 3) Shared Adapter #7 IP Address (note 4) Subnet Mask LAN Local Address (line 7) (note 3) Adapter Name (line 7) (note 3) NT Line-ID (note 3) Shared Adapter #8 IP Address (note 4) Subnet Mask LAN Local Address (line 8) (note 3) Adapter Name (line 8) (note 3) NT Line-ID (note 3)

127 Configuring Virtual Machine for MCP Server Networks Table 4 3. MCP Networking Values for Libra 4000 Servers MCP Environment Preconfigured Value New Value Host Name CPMCP1 TCP/IP Domain Name CPMCP1.CUSTOMER.COM MAICP4 number Instance 1, NP 210 Do not change EVLAN IP Address Do not change (note 1) Subnet Mask Do not change (note 1) LAN Local Address (line 0) 08000B (note 2) Shared Adapter #1 Reserved IP Address Subnet Mask 1) LAN Local Address (line NT Line-ID 2 Shared Adapter #2 Direct connection to JProcessor IP Address Subnet Mask LAN Local Address (line 2) *Default NT Line-ID 3 Shared Adapter #3 Direct connection to eportal IP Address Subnet Mask

128 Configuring Virtual Machine for MCP Server Networks Table 4 3. MCP Networking Values for Libra 4000 Servers MCP Environment Preconfigured Value New Value LAN Local Address (line *Default 3) NT Line-ID 4 MAICP4 number Instance 2, NP 211 Do not change Shared Adapter #1 IP Address Subnet Mask (/24) 1) LAN Local Address (line *Default NT Line-ID 1 Shared Adapter #2 IP Address Subnet Mask (/24) LAN Local Address (line 2) *Default NT Line-ID 2 MAICP4 number Instance 3, NP 212 Do not change Shared Adapter #1 IP Address Subnet Mask (/24) 1) LAN Local Address (line *Default NT Line-ID 1 Shared Adapter #2 IP Address

129 Configuring Virtual Machine for MCP Server Networks Table 4 3. MCP Networking Values for Libra 4000 Servers MCP Environment Preconfigured Value New Value Subnet Mask (/24) LAN Local Address (line 2) *Default NT Line-ID 2 MAICP4 number Instance 4, NP 213 Do not change Shared Adapter #1 IP Address Subnet Mask (/24) 1) LAN Local Address (line *Default NT Line-ID 1 Shared Adapter #2 IP Address Subnet Mask (/24) LAN Local Address (line 2) *Default NT Line-ID 2 MAICP4 number Instance 5, NP 214 Do not change Shared Adapter #1 IP Address Subnet Mask (/24) 1) LAN Local Address (line *Default NT Line-ID

130 Configuring Virtual Machine for MCP Server Networks Table 4 3. MCP Networking Values for Libra 4000 Servers MCP Environment Preconfigured Value New Value Shared Adapter #2 IP Address Subnet Mask (/24) LAN Local Address (line 2) *Default NT Line-ID 2 The following notes apply to both Table 4-2 and Table 4-3. Notes: 1. Unisys recommends that you do not change the IP Address and Subnet Mask for each EVLAN adapter. However, one reason to change these addresses is because you already have nodes in your network using the same subnet. In this case, choose an IP address that is reserved by IANA and does not conflict with the subnets in your network. 2. Line 0 is reserved for the EVLAN adapter. If you change the LAN Local Address for the MCP EVLAN adapter, do not use 08000B as the address. The Windows EVLAN adapter already uses this address. 3. Network Services supports the configuration of up to eight shared adapters (Ethernet ports, Fast Ethernet ports, or Gigabit Ethernet ports) per Network Processor. If you are configuring an adapter for shared MCP access, you need to supply the following values to the NAU: NT Line ID (corresponds to the CNS Line ID specified in Network Services Setup) LAN Local Address (physical or MAC address of the adapter), To view these address and name values in the Windows environment, see Determining Fast Ethernet or Gigabit Ethernet Adapter Information later in this section 3. An IP address/subnet mask is preconfigured for only one Fast Ethernet shared adapter (Shared Adapter #1). For additional shared adapter connections (Fast Ethernet port or Gigabit Ethernet port), you must assign an IP address and subnet mask appropriate for your networking environment

131 Configuring Virtual Machine for MCP Server Networks Using Sample CNS and TCP/IP Initialization Files Appendix A describes a set of initialization files that are shipped with each VMMCP server. These CNS and TCP/IP initialization files contain default values necessary to configure a standalone TCP/IP network (without shared adapters) and to configure an LX7100 server with shared adapters. The sample initialization files are INIT/SAMPLE/CLEARPATH/VMMCP/CPMCP1/CNS INIT/SAMPLE/CLEARPATH/VMMCP/CPMCP1/TCPIP The sample CNS and TCP/IP initialization files for the Libra 4000 servers are INIT/SAMPLE/CLEARPATH/CS4000/CPMCP1/CNS INIT/SAMPLE/CLEARPATH/CS4000/CPMCP1/TCPIP You can use these initialization files without alteration if do not need to connect to an external network. Otherwise, edit the appropriate CNS and TCP/IP initialization files as necessary for your configuration. The file descriptions (in Appendix A) contain remarks to assist in this editing process. Using Sample BNA Initialization Files Appendix A describes a BNA initialization file that may be appropriate for a VMMCP server. This file defines a single shared adapter connection through each Windows server. You can edit the file as appropriate for your configuration. Examining or Updating Network Services Values Use the following procedure to examine or update information for: Network Services EVLAN and Client Access Services drivers NP Unit Number TCP/IP configuration for shared Fast Ethernet ports or Gigabit Ethernet ports Use step 5 of this procedure only for shared Fast Ethernet ports or Gigabit Ethernet ports. Refer to Table 2-1 and Table 2-2 for the preconfigured Network Services values applicable to VMMCP servers and Libra 4000 servers respectively. Note: Unisys recommends that you do not change the IP Address information for Network Services (step 5). However, one reason to change these addresses is because you already have nodes in your network using the same subnet. In this case, choose an IP address that is reserved by IANA and does not conflict with the subnets in your network

132 Configuring Virtual Machine for MCP Server Networks Step Action 1 Start the Control Panel application. Open Computer Management (under Administrative Tools). A shortcut from the desktop is to right-click My Computer and select Manage. 2 To examine the status of Unisys Network Services, open Services (under Computer Management / Services and Applications: The current operating status and startup behavior of all installed services, including Unisys Network Services, is displayed. Upon installation of Network Services with the Setup program, the startup type is set to Automatic. Do not change this setting. 3 To examine the status of the Unisys Network Services drivers, open Drivers (under Computer Management / System Information / Software Environment). The current operating status and the startup behavior of all installed drivers, including Unisys Network Services drivers, is displayed. It is recommended that you do not change any settings for installed drivers. Do not stop or start any of the Unisys Network Services drivers. Some are started automatically by Windows and others are started and stopped by Network Services

133 Configuring Virtual Machine for MCP Server Networks Step Action 4 Examine or update the CNS Line ID and other properties for shared adapters using Connection Properties as follows. a. Access the configuration parameters for a shared adapter as follows: 1. Open the Windows Network Connections manager (from the desktop, right click on My Network Places and choose Properties). 2. In the Local Area Connections list, select the connection for a shared adapter, right click and choose Properties. 3. In the Connection Properties screen, select Unisys ClearPath Network Services and press the Properties button. 4. On the Shared Adapter tab, examine and (if applicable) update the assigned CNS Line ID and other properties. These include: Forward RIP Frames to MCP (Ethernet type adapters only) Unknown IP Frame Route (Ethernet type adapters only) See Shared Adapter Properties in Section 2 for more information. 5. If you change any values you must reboot for the change to take effect. b. Choose OK to accept the parameters. Note: If you want to disable MCP access to the shared adapter or return an adapter to shared status, refer to Reconfiguring a Shared Adapter in Section 2. To examine or update other configuration parameters for Network Services, you must run Setup and select the option "Update Configuration Options Only". For information, see "Reconfiguring a Shared Adapter with Network Services Setup" in Section

134 Configuring Virtual Machine for MCP Server Networks Step Action 5 a. To examine or update TCP/IP addresses for EVLAN adapters or shared adapters on VMMCP servers, access TCP/IP properties information as follows: 1. In the Windows Network Connections manager, select the Connection for one of the following adapters: Unisys Network EVLAN Adapter. Third-party adapter assigned to the shared adapter of interest. 2. With the Connection selected, right-click and choose Properties. 3. In the Connection Properties screen, select Internet Protocol (TCP/IP) and then click the Properties button. The current assigned IP address and Subnet Mask are displayed. b. To examine or update the IP configuration address of the EVLAN adapter, select Unisys Network EVLAN Adapter from the Adapter list to view the current settings: 1. Do not change the IP address and Subnet Mask because Network Services has no connections outside the MCP and Windows environments. 2. Verify that the Primary WINS Server and the Secondary WINS Server boxes are blank. 3. Choose OK to accept the parameters. c. To examine or update the IP configuration of a shared adapter address, perform the following steps: Note: The following steps under step c are not applicable for Libra 4000 servers. 1. In the Windows Network Connections manager, select the Fast Ethernet or Gigabit Ethernet adapter associated with the shared adapter connection of interest. 2. With the connection selected, right click and choose Properties. 3. In the Connection Properties screen, select Internet Protocol (TCP/IP) and click the Properties button; the currently assigned IP address, Subnet Mask, and Default Gateway information is displayed. 4. Select the IP Settings tab. 5. Enter the IP address the Windows server s TCP/IP will use with this adapter. 6. Choose OK to accept the parameters. d. Exit the Control Panel and restart the system if any settings changed. Exit Network Configuration and then exit Connection Properties. Some changes (for instance, IP address changes) take effect without reboot. Others might require a reboot. Notes: The < location>\adapters.txt file defines the Janus Surrogate Adapter assigned to each shared adapter. Only the Windows server IP address is configured from the Windows operating system. To change the MCP server IP address for a shared Fast Ethernet port, refer to Updating the MCP Network Configuration earlier in this section

135 Configuring Virtual Machine for MCP Server Networks Manually Directing Windows Data to the MCP Environment Data transfers between the Windows and MCP environments can use the following paths: The EVLAN data path An externally-configured LAN (the optional MAICP3 channel adapter must be configured in the MCP environment) When Network Services is installed and running, Windows data to the MCP is automatically directed through the EVLAN. Section 2 fully describes this automatic path configuration process. You can manually force the Windows server operating system to use a particular path (EVLAN or external network) to the MCP host. You do this by placing appropriate IP address and name information in local name resolution files. These local files are: LMHOSTS This is an ASCII text file that resolves NetBIOS computer names to IP addresses (must be IPv4 addresses). NetBIOS names are used by the Windows NetBIOS interface and by some TCP/IP programs. When present, the NetBIOS name cache, which is preloaded through the LMHOSTS file, overrides the WINS server to reduce the time required for name resolution. A pair of associated files (LMHOSTS.ORG and LMHOSTS.CNP) are created by Network Services software during the Setup process. See How the Setup Program Manages the LMHOSTS File in Section 2 for information about how these files are used. HOSTS This is an ASCII text file that resolves DNS-formatted names used by TCP/IP utilities such as PING, Telnet, and FTP. When present, the HOSTS file overrides any configured DNS servers to reduce the time required for name resolution. The HOSTS file can resolve IPv4 or IPv6 addresses to names. Use the following procedures to manually direct data over a particular data path

136 Configuring Virtual Machine for MCP Server Networks Directing Data through the EVLAN Data Path For the Windows operating system to use the EVLAN path to the MCP host, NetBIOS Name Resolution must resolve the MCP host name to the EVLAN IP address assigned to the MAICP4 device. Complete the following procedure for each Windows server. Step Action 1 Verify that Network Services and the virtual LAN are installed, configured, and running on your ClearPath server. 2 Log on to the Windows server. 3 Using Notepad, create an LMHOSTS file. Either create a new file or, if you want, use the sample LMHOSTS file located at %systemroot%\system32\drivers\etc\lmhosts.sam. Note: To use the sample file, update an example line. Then remove the pound sign from the beginning of the updated line. The LMHOSTS file must include the following parameters: where: <IP address> <MCP host name> #PRE <IP address> is the MAICP4-based IP address of the MCP host which may have been changed from the preconfigured value shown in the example (see Table 4-2). <MCP host name> is the current host name, which may have been changed from the preconfigured value shown in the example. Example In a Libra 4000 system, to direct data from the Windows server to the MCP environment, enter CPMCP1 #PRE In an LX7100 system, to direct data from the Windows server to the MCP environment, enter CPMCP1 #PRE The #PRE extension directs Windows to enter this address in the NetBIOS name cache. Windows will use this EVLAN IP address (without accessing WINS) for sending data to the designated MCP host. 4 Save the LMHOSTS file as %systemroot%\system32\drivers\etc\lmhosts 5 If DNS servers are not configured, there is no need to configure a HOSTS file. Skip to step 7. Otherwise, create a new file (or use the sample HOSTS file located at %systemroot%\system32\drivers\etc\hosts.sam) and copy the LMHOSTS file entries (created in step 3) into the HOSTS file. Note: The HOSTS file does not support the use of keyword extensions such as #PRE. These extensions are ignored (recognized as comments)

137 Configuring Virtual Machine for MCP Server Networks Step Action 6 Save the HOSTS file as %systemroot%\system32\drivers\etc\hosts 7 Either reboot the Windows server or type nbtstat -R at the MS-DOS command prompt on the Windows server to purge and refresh the NetBIOS name cache. Directing Data through the Externally Configured LAN If the optional MAICP3 channel adapter is installed and an external network is configured, Windows data can direct data to the MCP via the external network. For this routing to occur, NetBIOS Name Resolution must resolve the MCP host name to the MAICP3 address in the MCP environment. To manually direct data to use the external network path, complete the following procedure. Step Action 1 If any shares on the MCP server are mapped to drives, use Explorer to disconnect them. 2 On the MCP server, issue the appropriate command for an LX7100 system from an ODT window to disable EVLAN mapping to the Windows server: NW TCPIP MAPPING On the MCP server, issue the appropriate command for a Libra 4000 system from an ODT window to disable EVLAN mapping to the Windows server: NW TCPIP MAPPING Log on to the Windows server

138 Configuring Virtual Machine for MCP Server Networks Step Action 4 Using Notepad, create an LMHOSTS file, or modify the existing file. a. Include the following parameters in the file: <IP address> <MCP host name> #PRE where: <IP address> is address of NP 200 in the MCP host. This address may have been changed from the preconfigured value shown in the example (refer to Table 4-2). <MCP host name> is the current host name, which may have been changed from the preconfigured value shown in the example. b. Enter #### before the following line (this changes the statement into a comment): #INCLUDE... lmhost.cnp Example In an LX7100 system, to direct data from any Windows server to the MCP environment, type CPMCP1 #PRE The #PRE extension directs Windows to use the indicated address first for sending data to the MCP host. 5 Save the LMHOSTS file as %systemroot%\system32\drivers\etc\lmhosts 6 If DNS servers are not configured, there is no need to configure a HOSTS file. Skip to step 8. Otherwise, create a new file (or use the sample HOSTS file located at %systemroot%\system32\drivers\etc\hosts.sam) and update the file as follows: a. Copy all LMHOSTS file entries (created in step 4) into the HOSTS file. b. Ensure that there are no statements for the EVLAN data path. If necessary, remove (or comment out) statements that map to the EVLAN data path. Note: The HOSTS file does not support the use of keyword extensions such as #PRE. These extensions are ignored (recognized as comments). 7 Save the HOSTS file as %systemroot%\system32\drivers\etc\hosts

139 Configuring Virtual Machine for MCP Server Networks Step Action 8 To complete the data path redefinition process, perform either of the following tasks: Reboot the Windows server, or Perform the following steps: a. Enter nbtstat -R at the MS-DOS command prompt on the Windows server. This command purges and refreshes the NetBIOS name cache. b. Enter netstat 10 at the MS-DOS command prompt on the Windows server. This command form continuously displays (at 10 second intervals) all active TCP/IP connections. Initially, the MCP server connection will probably be in a Time_Wait state. For example: TCP CP-NTA:1233 CP-MCP1:nbsession TIME_WAIT Note: Per TCP standard, the original connection remains active in a Time_Wait state for up to two Maximum Segment Lifetimes (MSL) after a connection closure is requested. Typically, this Time_Wait period will last approximately four minutes. c. Monitor the returned TCP/IP connection status until the MCP server connection is no longer on the list. d. Press Ctrl+C to terminate the netstat command sequence. e. Now, traffic from the Windows server to the MCP server will use the external LAN data path

140 Configuring Virtual Machine for MCP Server Networks Directing MCP Data to the Windows Environment Normally, dialogs are initiated from the Windows server environment. In the following cases, however, data transfers are initiated from the MCP environment: When you issue an NW TCPIP PING command to determine if a remote host is available When you use the File Transfer Protocol (FTP) command In these cases, you need to specify either the IP address or the host name for the applicable Windows server. Using the NW TCPIP PING Command Note: The default firewall rules for a Libra 4000 server will prevent PING commands initiated from the MCP over the EVLAN path. For information on changing the firewall rules, see the Libra 4000 Server MCP Partition Software Operations Guide. If you use the IPADDR option of the NW TCPIP PING command, enter the exact address shown in the example. If you use the HOSTNAME option of the command, enter the current host name, which may have been changed from the preconfigured value shown in the example. For example: In a Libra 450 server, to direct data from CPMCP1 to the Windows server via the EVLAN, enter NW TCPIP PING IPADDR = or NW TCPIP PING HOSTNAME = CPNTA Note: The TCPIP PING command HOSTNAME option will only work if the hostname has been mapped to the IP address of the Windows server. This mapping is provided in the MCP environment s default TCP/IP initialization file. However, if you changed your MCP configuration (as specified in Updating the MCP Configuration, earlier in this section), this mapping may have been removed. In a Libra 460 server, to direct data from CPMCP1 to the Windows server via the external network, enter NW TCPIP PING IPADDR = <external IP address> Note: The Default Windows server (shared adapter) address is For More Information For more information on the automated procedure for directing data to take the virtual LAN data path, see Installing Network Services and How the Setup Program Manages the LMHOSTS File in Section

141 Configuring Virtual Machine for MCP Server Networks Specifying the WINS Server Address Windows servers in ClearPath MCP systems were previously shipped with the WINS service installed. Due to the issues with WINS on multihomed systems, WINS is no longer preinstalled. If you want to install the WINS server, please see NX/NET FAQ on the Support Web page and review the articles on WINS and multihomed systems in the Microsoft Knowledge Base. If you have a WINS server somewhere in your network, specify its IP address to each Windows server within the ClearPath MCP system. You can enter this address at the WINS Address tab of the TCP/IP Properties Sheet. You must also inform Client Access Services of the WINS server address as described in the following table: Step Action 1 At the ST, switch to or initiate the Administration Center application. If necessary, connect to the MCP server specifying its hostname and a privileged usercode, such as ADMINISTRATOR. 2 From the Resources menu, choose Create or Modify. 3 Another menu appears. Choose Server Properties. 4 On the Server Properties on <Server Name> screen a. Select the WINS Server tab. b. Type a primary WINS server IP address and/or secondary WINS server IP address. c. Choose Modify. 5 Administration Center displays a message stating that the change will not take effect until you save the configuration. Choose OK. 6 From the Resources menu, choose Save. 7 Administration Center displays a message, asking if you want to make the changes permanent. Choose Yes. For More Information For more information on WINS configuration, see the WINS Manager help. Rebooting the System Environments If you have not already done so, reboot the MCP and Windows server environments as described in the following table. The configuration changes for each of these environments do not take effect until they are restarted

142 Configuring Virtual Machine for MCP Server Networks Step Action 1 Shut down the MCP environment as follows: For Libra Model 400 and FS1700 servers: a. Activate the Console window. b. Click the Halt button on the tool bar if the system is running, started, or not responding. Wait until the partition status indicates that the partition has halted. c. From the MCP menu, choose Shutdown MCP Control. Wait until the status line indicates that MCP Control and OPM have been shut down. 2 Reboot the Windows server by following the procedure in Section 7, Stopping and Starting the Windows Server. Verifying the System Networking Configuration Verify the system networking environment configuration as follows: Step Action 1 Switch to or initiate the Administration Center application. If necessary, connect to the MCP server specifying its hostname and a privileged usercode, such as ADMINISTRATOR. 2 Verify that the application connects to the MCP by seeing that the MCP server name appears in the Connected MCP Server(s) dialog box on the toolbar. 3 Terminate Administration Center. Controlling the Maximum Transmission Unit (MTU) Value The USERFCMTU option provides control of the maximum transmission unit (MTU) value for TCP/IP. This option is set by default on ClearPath MCP servers. As a result, TCP/IP uses a maximum transmission size of 536. This low value is chosen to comply with RFC 1122, and might help to prevent fragmentation of a datagram by intermediate gateways along the path. Note: Before making any changes to the USERFCMTU option, you should determine the minimum MTU value of all gateways and nodes in the network. If you reset the USERFCMTU option, you can use a larger MTU size that matches the type of physical LAN in use. As the system is originally shipped, the connecting medium and MTU value is an Ethernet cable with an MTU value of 1496 bytes. To set the USERFCMTU option, enter the following OI command: NW TCPIP OPTION + USERFCMTU

143 Configuring Virtual Machine for MCP Server Networks To reset (clear) the USERFCMTU option, enter the following OI command: NW TCPIP OPTION - USERFCMTU Note: 1. You can also use the NAU to define the USERFCMTU option during the MCP network configuration process. This function was described in the Configuring with the NAU paragraph earlier in this section. 2. The USERFCMTU applies only to IPv4. IPv6 uses PathMTU to address the MTU size question. Refer to the TCP/IP Implementation and Operations Guide for information on PMTU Verification Interval. Viewing the RESET Reports The TCP/IP software in the MCP environment enters RESET reports in a table whenever remotely initiated RESET actions are received. To view this table, enter the following command: NW TCPIP DISPLAY TABLE RESETRPTS

144 Configuring Virtual Machine for MCP Server Networks

145 Section 5 Other Configuration Procedures Your ClearPath MCP server is preconfigured with LAN connectivity, enabling all ClearPath components to communicate with each other as needed. You can run the system in this standalone configuration as long as you want. However, if you want to integrate your ClearPath server into a larger network, you must plan and configure several aspects of the system to meet your needs. This section describes various configuration procedures that are basically common to all server models. They include: Integrating your server with an existing BNA network Integrating your server with Microsoft networks Optimizing MCP networking Integrating Your Server with an Existing BNA Network BNA is a network provider that connects MCP Series enterprise servers and other devices so that the resources at one can be used at another. These resources include files, programs, and processors. BNA is an optional software package on your ClearPath server. To find out the packet size currently in use by BNA, use the NW CONNECTION inquiry at a BNA host and view the MIMS (Maximum Input Message Size) and MOMS (Maximum Output Message Size) settings. Libra Series Native MCP Servers, and FS1800 Servers Normally, you can connect your MCP environment to a BNA network via the Fast Ethernet (or Ethernet) switch. The switch has a maximum packet size of approximately 1,500 bytes. If your BNA network is configured to use a packet size greater than 1,500 bytes, you may want to optimize your performance by bypassing the switch. However, to do this, you may need to add a LAN adapter that supports larger packet sizes. For example, the Intel PRO/1000 series Gigabit Ethernet adapter in conjunction with Network Services Jumbo Frames feature supports up to 9,000 byte frames. Gigabit CNA devices incorporate Intel Pro/1000 NICs and are able to take advantage of Jumbo Frames

146 Other Configuration Procedures To bypass the Fast Ethernet or Ethernet switch, connect one or more of the MCP environment LAN adapters directly to an outside LAN. No corresponding change is required to the BNA initialization file. However, you may want to revise the BNA initialization file to take advantage of larger packet sizes. The BNA network can also share network connections with a Fast Ethernet port or Gigabit Ethernet port in the Windows environment via Network Services. A Fast Ethernet connection typically is routed through the switch. A Gigabit Ethernet port bypasses the switch. VMMCP Servers You can connect your emulated MCP (VMMCP) system directly onto a BNA network. Through the standard Shared Adapter for Network Services Fast Ethernet service, a BNA network can access the MCP environment through a Fast Ethernet port or Gigabit Ethernet port configured in the Windows environment. The message packet size is limited to that of the NIC. Usually this limit is 1,500 bytes. Using the Jumbo Frames feature and the Gigabit Ethernet adapter, the limit is extended to 9,000 byte frames. Note: Configure 9000-byte jumbo frames by setting the MIMS and MOMS attributes to 8996 for BNA connections and to 9000 for the LAN connection group. Integrating Your Server with Microsoft Networks If you need help in integrating your server with Microsoft networks, the best starting place is the Microsoft support site on the Internet. You can reach the support site home page by entering the following URL: From the support site home page, you can navigate to the support sites for individual Microsoft products, search the Microsoft knowledge base, and get assistance from Microsoft online or by phone. In addition, Microsoft networks support a browse feature. Browsing enables you to use the mouse to select a network resource using Explorer, Network Neighborhood, and other client applications. For example, you can use My Network Places (Windows 2000 or Windows Server 2003) to view a list of Microsoft Networking domains and workgroups. Within this list, you can Select a domain from the list of computers that belong to the domain. Select a computer from the list of domains. Select a resource which connects you to the computer and, if you are authorized to access the selected computer, optionally maps a drive letter to the resource. To successfully use the browse capability to access MCP environment resources, your LAN and servers must meet a number of configuration requirements. Most of these configuration steps are also necessary to enable users to access the Windows environment and other servers on the LAN

147 Other Configuration Procedures For the MCP environment to participate in browsing, you must enter the NW NAMESERVICE + command to enable the Client Access Services Name Service. The name server support of the MCP environment is normally sufficient to provide support for browse to Windows servers on the same LAN segment as the MCP system. To enable Windows servers on other LAN segments to browse the MCP system, Microsoft networking domains are required. For a Windows server to be able to find the MCP server using browse, the following conditions must be met: That server or another Windows server on the same local LAN segment must belong to the domain specified for Client Access Services using Administration Center. Some Windows server on the same local LAN segment as the MCP system must also belong to the domain specified for Client Access Services. The browse capability is optional and can be ignored without serious consequences. When the LAN requirements for browsing are not met, users may not see the MCP server s name listed, but will still be able to access the ClearPath server environments by entering the desired server and share names into dialog boxes. The remainder of this section provides additional detail and background information on these concepts. Enabling Workstations to Browse the MCP Server The MCP environment can only act as a member of a workgroup and the MCP can only function as a non-browser in the Microsoft Networking environment. The default browse domain name for both the MCP environment and the Windows environment is ClearPath. The Windows server is also configured to belong to the ClearPath MCP workgroup. The MCP periodically makes broadcast announcements to all other known browsers (both host name and domain or workgroup name) on its segment. The MCP name appears in the browse list only when there is another computer present that has all the following properties: Capable of maintaining a browse list Located on the same LAN segment as the MCP environment Participates in the same browse domain as the MCP environment These conditions are met by the default configuration of the MCP and Windows environments in an MCP ClearPath system. These enable workstations on the MCP subnet to browse the MCP environment. The MCP subnet is the subnet that includes the MCP environment

148 Other Configuration Procedures Workstation Browsing Across Subnets To enable workstations not on the MCP subnet to browse the MCP environment, you must ensure that the master browser for each segment knows the address of the master browser for the MCP workgroup. You can use either the WINS servers or the LMHOSTS files to make this information available to the necessary master browsers. This can be accomplished by configuring a common WINS for all your systems. Alternatively, you can place the address of the master browser for the MCP workgroup in the LMHOSTS file of each master browser as shown in the following example: <IP address> <host name of PDC> #PRE #DOM:< domain name> If servers or workstations on other subnets of your network are configured to be part of the same workgroup as the ClearPath MCP and Windows servers, browse difficulties may arise. These difficulties can be avoided by changing the Windows server installation to turn the workgroup name into a domain. However, this is not generally necessary as workstations do not have to be part of the same browse domain in order to access a server. Unisys does not, however, recommend making the ClearPath Windows server into a PDC or BDC

149 Other Configuration Procedures Assigning Units to a Workgroup or Domain Perform the following steps at a Windows server to configure the workgroup or domain name for that unit: Step Action 1 Start the Control Panel application. 2 From the Control Panel screen, double-click System to enter network settings. 3 Select the Network Identification tab. 4 To assign a workgroup or domain, choose the Properties button next to Workgroup Name. You can then assign a workgroup or a Microsoft Networking domain (but not both). To assign a workgroup a. Choose the Workgroup option button. b. Type a workgroup name. c. Choose OK. To assign a domain a. Choose the Domain option button. b. Type a domain name. c. Optionally, create an account by selecting the Create a Computer Account in the Domain check box and filling in Username and Password. d. Choose OK. 5 The system displays a message welcoming you to the workgroup or domain. Choose OK. 6 The Network screen reappears. Choose OK. 7 The system displays a message stating that the Windows server must be restarted before the changes can take effect. 8 Choose Yes to restart now

150 Other Configuration Procedures Optimizing MCP Networking For all systems, you can now block the transfer of Routing Information Protocol (RIP) frames into the MCP server. This action significantly improves MCP networking performance during periods of heavy RIP broadcast activity. For systems that do not include HMP FastPath - CIA, you can use a variety of different settings to adjust the behavior and performance of networking in the MCP environment, on Windows servers, and on Microsoft client workstations. The following procedure describes how to optimize MCP networking for EVLAN performance. Optimizing Network Services for the Enhanced VLAN (EVLAN) Note: This procedure applies to VMMCP servers. Network Services transfer very large message blocks between the MCP and Windows environments. Therefore, a pool of large MCP buffers is needed to accept these messages. Perform the following steps to implement define the required MCP buffer environment: Step Action 1 Switch to an ODT window. 2 To determine which network processors are used for Network Services, type PER NP View the resulting file to determine the device number for each CNP type network processor. Note: In this example, commands are entered using the default NP device number for the Windows server A connection of a ClearPath MCP server (7000). You will need to enter the NP device number applicable to your configuration. 3 Enter the following commands: SEND NP 7000 BUFFERSIZE SAVE NP 7000 CLEAR NP 7000 READY NP 7000 This command sequence defines an MCP buffer size of 65,280 bytes for NP 7000 and then reinitializes communications through this EVLAN path. 4 If more MCP memory is needed for other applications, you might need to reduce the number of buffers in the pool to a value of 20 or 30 (the default is 45). To define a pool of 30 buffers, enter the following commands: SEND NP 7000 MAXINPUTS 30 SAVE NP 7000 CLEAR NP 7000 READY NP

151 Section 6 Operations This section provides the following operating information for network processors in the MCP environment: Operating tasks Data types Attributes for EVLAN and shared adapters Networking commands and inquiries System commands and inquiries Reports Operating Tasks These are tasks that you may need to perform periodically. The following procedures include commands that are described later in this section. Before you can perform any of the tasks described in this section, the Windows server must be operational and Network Services must be installed. See Section 2 for installation procedures. See Sections 3 or 4 for server-specific configuration procedures. HMP FastPath CIA The HMP FastPath ClearPath Intraconnect Architecture (HMP FastPath CIA) channel is available on all Libra Series native MCP and FS1800 servers. This channel provides a high-bandpass, low-latency connection path between the MCP and each Windows server environment. The HMP FastPath CIA channel is not configured as a system device and is not dedicated to any specific use. As an undedicated system resource it is available to various clients in both the MCP and Windows operating environments. Network Services is one of these clients. Note: You can determine whether or not you have an HMP FastPath CIA channel by executing an OL PORT <device number> command. If you do, in addition to the regular OL PORT <device number> output response, you will receive a Sub Protocol line of output similar to the following: Sub Protocol: CIA over ABC, State: Initialized

152 Operations HMP FastPath CIA uses a PCD definition that is different than earlier MCP to Windows channel definitions. Each HMP FastPath CIA port is simply configured as an Address Based Communications (ABC) channel. The only explicitly defined value is a Channel Type (DAC). The Control, Unit, and NP Device fields are not specified. This means that several operating commands associated with managing the device do not apply. Unusable commands include SV, CL, RY NP and OL CTL as well as UR/UR- CTL and UR/UR- NP. Bringing Network Services Into Service Perform the following steps at the ODT window for each Windows server in your system. Procedure for Servers without HMP FastPath CIA (VMMCP Servers): Step Action 1 Use the UR PORT <port number> command to make the port usable for the NP. To determine the port number, issue the following command at the ODT: OL CTL 210 Note: 210 is the control number for VMMCP servers (LX 180, Libra Model 400, Libra Model 450, Libra Model 460, Libra Models 4080 and 4090, FS1700, and SP1760). 2 Use the UR CTL <control number of NP> command to cause the executing partition to resume operations through the specified control. 3 Use the RY NP <device number> command to ready the NP. The <device number> is 210 (for VMMCP servers). You must ready the NP before the host can load the firmware file to it. (You can ready the NP before or after initializing the network provider on the host.) 4 Initialize the network provider on the host. Procedure for servers with HMP FastPath CIA (Libra Series Native MCP and FS1800 Servers): Step Action 1 Use the OL PORT <port number> command to verify that the HMP FastPath CIA connection is operational. The following message should appear in the command response: CIA over ABC - Initialized 2 Initialize the network provider on the host. 3 Use the A command (Active Mix Entries) to verify that the following stack is active: CIA/INDICANT/FOR/<task number>

153 Operations Reinitializing Network Services Reinitialize Network Services whenever you install new firmware files on the MCP server. Reinitialization is performed when the network provider is in Networking mode. Procedure for Servers without HMP FastPath CIA (VMMCP Servers): Step Action 1 Use the NW NP command, if necessary, to determine the NP device number. 2 Use the SV NP <device number> command to save the NP. 3 Use the CL NP <device number> command to clear the NP. 4 Use the RY NP <device number> command to ready the NP. Procedure for servers with HMP FastPath CIA (Libra Series Native MCP and FS1800 Servers): Step Action 1 Use the NW NP command, if necessary, to determine the NP device number. This command also returns the state of the NP device. An example of an NP Device state is NASCENT. NASCENT indicates the host operating system has been asked to initialize the NP, possibly after loading its firmware. If the device number is zero and the state is NASCENT then the greeting with the NP has not yet taken place. For information on other states that may be displayed, see the NP Inquiry command in the Networking Commands and Inquiries Help. 2 Use the NW CNS CLEAR NP <device number> command to shut down the applicable NP. If the device number is not available, it may be necessary to UR/UR- the related port. Following this shutdown, the NP will reload and be reinitialized. Removing Network Services If problems arise or if you want to upgrade the software, you might want to remove Network Services. For details, refer to Removing Network Services from the Windows Server in Section

154 Operations Stopping and Starting the Windows Server On occasion, you may need to power down or simply restart a Windows server operating system on a server within the ClearPath system. Use the following procedure to isolate this Windows server operation from the MCP environment. In this procedure, the MCP commands are issued to the port that connects with the affected Windows server. Procedure for Servers without HMP FastPath CIA (VMMCP Servers): Step Action 1 Issue these MCP commands at an ODT window: SV NP <device number> CL NP <device number> The default <device number> for VMMCP servers is 210 (for the first NP configured) 211 (for the second NP configured) 212 (for the third NP configured) 213 (for the fourth NP configured) 214 (for the fifth NP configured) 215 (for the sixth NP configured) These commands make Network Services inactive and destroy all connections between Network Services and the host. 2 On the MCP server, reserve the control for the device referenced in Step 1 as follows: UR CTL <device number> 3 On the MCP server, issue the following command to reserve the port for the applicable device referenced in Step 1. UR PORT <port number> Note: You can determine the port number by entering the following command: NW NP <device number> The port number is returned in the last line of the system response. 4 As necessary, either shut down or simply restart the Windows server. Perform the remaining steps after Windows has completely reinitialized. 5 Issue the following command to make the port usable for the NP: UR - PORT <port number> 6 Issue the following command to cause the executing partition to resume operation through the specified control: UR - CTL <NP control number>

155 Operations Step Action 7 The NP must be readied before the host can load the firmware file to it. (This can be done before or after initializing the network provider on the host.) If necessary, use the following command to ready the NP: RY NP <device number> Procedure for Servers with HMP FastPath CIA (Libra Series Native MCP and FS1800 Servers): Step Action 1 On the MCP server, issue the following command to reserve the port for the applicable device. UR PORT <port number> Enter OK on the waiting job to complete the port reserve operation. Note: You can determine the port number by entering the following command: NW NP <device number> The port number is returned in the last line of the system response. 2 As necessary, either shut down or simply restart the Windows server. Perform the remaining steps after Windows has completely reinitialized. 3 Issue the following command to make the port usable for the NP: UR - PORT <port number>

156 Operations Initiating a Dump Use the NW DUMP NP command to initiate a dump. You cannot initiate a dump of Network Services from the Windows server. For more information, see the DUMP NP command description later in this section. Location of the Dump Data Much of the MAICP4 or CNP dump data is placed in the Windows Event Logs (Application and System). Some data is returned to the MCP server and placed into this NP dump file: *DUMP/<hostname>/NP/<dlp_id>/<date>/<time> Additional data is returned to the Windows server and placed in this Network Services dump file: <Network Services location>\log\cnpdumpnn.dmp where nn is a dump file number between 00 and 19. You must provide the NP and Network Services dump files when submitting trouble reports against the Network Services software. Recovering the Windows Event Logs After the MCP server reports that the dump is complete, the Windows Event Logs are backed up on the Windows server. Location of the Event Log Backups These log backups are located in the Network Services directory that is established when Network Services software is installed. This directory defaults to <Network Services location>\log The log backup file names are CNPAPP1.EVT (Application) CNPSYS1.EVT (System) You can copy the Event Log backups to removable media. You must provide this information when submitting trouble reports against the Network Services software. Viewing Event Log Backups Online You can view the Event Log backups at the Windows server using the Windows Event Viewer found in the Administrative Tools program group. See the Windows Help for directions on how to use the Event Viewer

157 Operations Recovering the Windows Event Logs Manually Occasionally, you may need to use a manual procedure to recover the Windows Event Logs. For example, you may see a blue screen with an error message that indicates a serious problem, and manual recovery may be the only method you can use to retrieve the Event Logs. Follow this procedure to retrieve the Event Logs manually. You can recover both the System and Application Event Logs using this method. Step Action 1 Access the Windows Event Viewer, which is found in the Administrative Tools program group. 2 From the Log menu, select the Event Log that you want to view (System or Application). 3 Choose the Save As option to save the file as another name. Be sure to use.evt as the file suffix. Viewing Shared Adapter Information The Line Status Discovered report can be used to obtain key information about each shared adapter configured within a network processor (NP). Adapters are defined by Line Number, a CNS attribute that must map to the Line ID assigned as an adapter property value during setup. Network Services issues the Line Status Discovered report whenever an NP is initialized. Thereafter, you can access it by issuing an NP inquiry. For example: NW NP 7000 Here is a typical Line Status Discovered report: LINE STATUS DISCOVERED FOR NP 7000 LINE 0 TYPE = EVLAN STATUS = PASSED LINE 1 TYPE = GIGABIT ETHERNET STATUS = PASSED (EXCLUSIVE) LINE 2 TYPE = FAST ETHERNET STATUS = PASSED (SHARED) LINE 3 TYPE = ETHERNET STATUS = PASSED (SHARED) The report includes pertinent information on the sharing status of each line. SHARED means that the line is shared with Windows networking protocols. EXCLUSIVE means that the line is not shared; MCP networking has exclusive use of it. If sharing status is not provided, it does not apply (for example, it is an EVLAN) or the sharing status could not be determined

158 Operations Submitting Trouble Reports If you need to submit a trouble report (UCF) against Unisys products including Network Services software, use the following Primus identifiers: Primus Product: NX/NET Component: NX/NET What to Submit When submitting trouble reports against the Network Services software, supply the following information to Unisys: From the MCP environment: SUMLOG covering the time period when the problem occurred (NX/NET component only) NP dump file. This file is not available on servers with HMP FastPath CIA. From the Windows environment: System Event Log file To obtain this file, use the Windows Event Viewer utility to view the System Event Log and choose the Save As option under the Log menu. Application Event Log file To obtain this file, use the Windows Event Viewer utility to view the Application Event Log and choose the Save As option under the Log menu. MEMORY.DMP file This file is available if Windows is configured to take a crash dump and a dump is taken for this failure. Get a full memory dump, not a mini-dump or kernel dump. CNPDUMPnn.DMP file Up to 20 of these files are located in the <Network Services location>\log directory. Probes file To obtain this file, run the Extract.Exe utility located in the \NXNET\TOOLS directory. This utility copies internal diagnostic information into a text file. Since the data is stored in circular buffers, you must run the Extract utility as soon as possible following the failure, and prior to rebooting the Windows environment. Problem description provided by the first three lines of the Windows blue screen, if applicable DrWtsn32.log file This file is required only if a Dr. Watson fault is reported in CNP.Exe. The file may be located in either of the following directories: Windows directory Windows partition root directory

159 Operations USER.DMP file This user level dump file is required only if a Dr. Watson fault is reported in CNP.Exe. The file may be located in either of the following directories: Windows directory Windows partition root directory How to Submit Information You can submit files on either tape or diskette media. To submit files on tape, do one of the following: Put the files on a backup tape accessible from the Windows environment. Copy the files to a disk share accessible to the MCP environment, and then copy the files to a tape. Information on submitting UCF materials through the Internet is available from the Unisys Product Support Web site at

160 Operations MCP Operations Interface Summary Data Types This topic summarizes the MCP commands, reports, and data types related to Network Services and ClearPath MCP networking operations. The following table shows the internal values that identify the ClearPath HMP network processor components to the MCP environment. Hardware Type <NP type> <NP version> <component type> Emulated Systems ICP4 DLP emulation MAICP4 none MAICP4 FC3-IOP CNP none CNP Attributes for EVLAN and Shared Adapters Use the following attributes for configuring network connections for virtual LAN and shared adapters via MAICP4 or CNP. ADAPTERTYPE (ADT) This attribute indicates if the adapter is a virtual LAN line, a Fast Ethernet line, or a Gigabit Ethernet line. Values include: LINEID EVLAN (the default) MIMS/MOMS/MIMSL/MOMSL is set to For MAICP4, line 0 must be set to EVLAN and must be configured for TCP/IP. FASTETHERNET SPEED is set to 100,000,000. MIMS/MOMS/MIMSL/MOMSL is set to GIGABIT SPEED is set to 1,000,000,000. MIMS/MOMS/MIMSL/MOMSL is set to ADAPTERNAME (ADN) This attribute is now ignored. Network Services uses this attribute to map a LAN connection group to the adapter in the Windows environment

161 Operations The LINEID specified in the MCP environment must match the CNS Line Id assigned to the adapter name to be shared in the Windows environment. See Determining Fast Ethernet or Gigabit Ethernet Information for directions on how to determine the adapter name LocalAddress (LA) This attribute indicates the local address associated with a particular EVLAN or shared adapter. For EVLANs and other ICPs, LA is a configured 12-character hexadecimal value (there is no physical address). For Fast Ethernet and Gigabit Ethernet shared adapters, LA is the physical (MAC) address of the adapter (12 hexadecimal characters). For shared adapters, a LA value of *DEFAULT or causes the software to detect the hardware s MAC address. Automatic address detection also occurs if no LA value is specified. For shared adapters on VNP network processors, a LA value of *FACTORY specifies that local address should be reset to the factory default value stored on the adapter. Refer to Determining Fast Ethernet or Gigabit Ethernet Information in Section 3 or 4 for details on how to determine the physical address of an adapter. Command Examples Definition of an EVLAN: NW ADD CONNGRP CG_ICP_70000 (TYPE = LAN, ICPDEVICEID = 7000, LINEMODULEID = 1, LINEID = 0, LOCALADDRESS = 08000B007000, SPEED = , MAXINPUTMESSAGESIZELIMIT = 4352, MAXOUTPUTMESSAGESIZELIMIT = 4352, MAXINPUTMESSAGESIZE = 4352, MAXOUTPUTMESSAGESIZE = 4352) Definition of a Gigabit Ethernet shared adapter (using actual MAC address value): NW ADD CONNGRP CG_ICP_70001 (TYPE = LAN, ADT = GIGABIT, ICPDEVICEID = 7000, LINEMODULEID = 1, LINEID = 1, LOCALADDRESS = 08000B001234, SPEED = ) Definition of a Gigabit Ethernet shared adapter (allowing software to detect its actual address): NW ADD CONNGRP CG_ICP_70001 (TYPE = LAN, ADT = GIGABIT, ICPDEVICEID = 7000, LINEMODULEID = 1, LINEID = 1, LOCALADDRESS = , SPEED = )

162 Operations Networking Commands and Inquiries CNS ADD NP ATTACHMENT MAPPING <device number> This command enables the system operator to configure a network processor so there is a mapping between the attached network processor and the attachment identifier for the processor. The attachment type is a port, and the identifier is the port number. This feature is needed when a system runs in a ClearPath Intraconnect Architecture (CIA) FastPath environment, and it is necessary to know the attached network processor identifier before bringing up the network processor. This command is a companion to the CNS DELETE NP Attachment Mapping command. Command Example NW CNS ADD NP ATTACHMENT MAPPING 8001 PORT CNS CLEAR NP <device number> Use this command to shut down a specified network processor and all connections that are currently attached to it. If the NP is still available following completion of the shutdown operation, the NP is reloaded and reinitialized. The host is informed of affected connections during the NP reload phase. Command Example NW CNS CLR NP 7000 CNS DELETE NP ATTACHMENT MAPPING <device number> This command enables the system operator to remove attachment mapping for the specified network processor. If the network processor was added by a previous ADD NP attachment mapping command, the network processor entry is deleted as part of the operation. This command is a companion to the CNS ADD NP Attachment Mapping command. Command Example NW CNS DELETE NP ATTACHMENT MAPPING 8001 CONNECTION <connection/connection group name> Use this inquiry to determine the connection status of a connection or connection group. Command Examples NW CONN CG_ICP_200A NW CONN CG_ICP_

163 Operations DUMP NP <device number> [<family name> LOCAL [To NP] REBOOT] Use this command to dump data for a specific network processor (NP) or to reboot a Windows server. There are two dump types, non-local and local, which dump data for an NP and create a dump file: Non-Local Dump The data is copied to a user-specified disk pack or to the network pack on an enterprise server in the MCP environment of operation. The name of the file is dump/<hostname>/np/<np number>/<date>/. The command shuts down the NP and all connections that are currently attached to the NP. After the dump completes, the NP is reinitialized and reloaded. The host may not handle data requests during a non-local NP dump; it depends on whether more than one NP is operational at the time of the dump. Local Dump The data is collected without impacting the operation of the device (The NP remains operational during the dump.) The data is stored locally on the device. The dump file resides in the NxNet installation path in the Log directory under the name NNSDMPxx.TXT, where xx is a value of A non-local dump is the only option for devices other than the NNS network processor. For the network processor, there are two possible dump variants depending on the attachment type (HMP FastPath CIA or non-hmp FastPath CIA) For HMP FastPath CIA, the default dump type and the local option result in a local dump. The reboot option results in a reboot. For non-hmp FastPath CIA, the default dump is non-local but a local dump can be obtained by specifying the LOCAL dump option in the DUMP NP command. Network Processors (Dump Type) Non-Local Local Default Local Option NNS VMMCP X NA X NNS HMP FastPath CIA NA X X

164 Operations Reboot The Reboot option causes the Windows server specified by the NP to reboot. It does not cause a dump or create a dump file. This option: Is only valid for Network Services (NNS) devices. Shuts down the NP and all connections that are currently attached to the NP. When the Windows server comes up again, connections may reinitialize depending on their autoinit properties. Does not allow the host to handle data requests during a reboot; it depends on whether more than one NP is operational at the time of the reboot. Usage For HMP FastPath CIA devices, do not specify <family name> in the command syntax. The data is dumped to the device. For devices other than HMP FastPath CIA devices, specifying <family name> dumps the data to the disk pack identified by <family name>. Omitting <family name> from the command dumps the data to the same pack running your network managers. REBOOT option enables rebooting of a Windows server or CNA device running NNS software if the NNS software was installed via the REMOTEINSTALL command and the REBOOT MANUAL option was entered on the command. Command Examples NW DUMP NP 7000 (example for an HMP FastPath - CIA device) NW DUMP NP 156 USERFILE (example for a non HMP FastPath - CIA device) NW DUMP NP 9000 LOCAL (example for NNS-type network processor) NW DUMP NP 7000 REBOOT (example for NNS-type network processor)

165 Operations ESTABLISHCALL BY CONN <connection/connection group name> NP UTILIZATION Use this command to prepare the specified connection or connection group to initiate an outgoing call. Command Examples NW EC BY CONN CG_ICP_200A NW EC BY CONN CG_ICP_7000 Use this inquiry to find the device numbers of the network processors on your system or to see detailed information for a particular network processor. This command also returns the state of the NP device. An example of an NP Device state is NASCENT. NASCENT indicates the host operating system has been asked to initialize the NP, possibly after loading its firmware. If the device number is zero and the state is NASCENT then the greeting with the NP has not yet taken place. For information on other states that may be displayed, see the NP Inquiry command in the Networking Commands and Inquiries Help. Command Examples NW NP NW NP 7000 NW NP 200 Use this inquiry to view the percentage of processor capacity and memory being used (processor utilization and memory utilization). For Network Services devices, the reported information is the: Total Windows processor utilization for the server Amount of physical memory in use. Note that this is physical memory, not total memory, since it does not include virtual memory. Networking processors (NPs) using the HMP FastPath CIA interface to the MCP environment can provide data rate calculations for I/Os and kilobytes per second using this command. The rates displayed are network processor specific. Command Example NW UTIL

166 Operations CNS REMOTEINSTALL Command The information describing the syntax and usage of the CNS REMOTEINSTALL command has been moved to Section 2 of this guide under the heading Remotely Upgrading Network Services on a Windows Server or CNA Device. System Commands and Inquiries CLEAR NP <device number> Note: This command does not apply to servers with HMP FastPath CIA. Use this command to terminate all connections between the host and the specified network processor. Command Examples CL NP 7000 CL NP 200 OL CTL <device number> Note: This command does not apply to servers with HMP FastPath CIA Use this command to display the inboard and outboard information for the control unit. For example, use this command to get the port number and port status of the PCI Bridge. Command Examples OL CTL 7000 OL CTL 200 OL NP <device number> Note: This command does not apply to servers with HMP FastPath CIA Use this command to display the label and path information for the specified NP device. Command Examples OL NP 7000 OL NP

167 Operations OL PORT <port number> PER NP PER NP Use this command to get the inboard and outboard information for the port. For example, you can obtain information about the PCI Bridge port and a list of all controls associated with the port and their status. For servers with HMP FastPath CIA, the following message in the command response indicates an online CIA (HMP FastPath CIA) port: CIA over ABC - Initialized Command Example OL PORT 7020 Note: This command does not apply to servers with HMP FastPath CIA. Use this inquiry to obtain the device number and status of all network processors that are in a ready state. Command Example P NP Note: This command does not apply to servers with HMP FastPath CIA. Use this inquiry to obtain the device number and the status of every network processor that is in an active or reserved state. Command Example P NP - READY NP <device #> Note: This command does not apply to servers with HMP FastPath CIA. Use this command to ready a network processor. You must ready a network processor before the host can load the firmware to it. Command Examples RY NP 7000 RY NP 7002 RY NP 200 RY NP

168 Operations SAVE NP <device #> Note: This command does not apply to servers with HMP FastPath CIA. Use this command to prevent a network processor from establishing any new connections. This command makes the NP inactive. It must be readied before the host can load firmware to it. Command Examples SV NP 7000 SV NP 200 UR PORT <port number> Use this command to make the specified port unavailable as a path for I/O operations. For servers with HMP FastPath CIA: This command will terminate all client services currently using this port (Network Services may not be the only client). To limit the operation to networking, use the NW CNS CLEAR NP <device number> command. After entering the UR PORT command, enter OK on the waiting entry to complete the port reserve operation. Command Example UR PORT 7020 UR PORT <port number> Use this command to cause the system to resume I/O operations through the specified port. Command Example UR - PORT 7020 UR CTL <control number of NP> Note: This command does not apply to servers with HMP FastPath CIA. Use this command to stop issuing commands through the specified control. Command Example UR CTL

169 Operations UR CTL<control number of NP> Note: This command does not apply to servers with HMP FastPath CIA. Use this command to cause the system to resume I/O operations through the specified control. Command Example UR - CTL 7000 UR NP<device number> Note: This command does not apply to servers with HMP FastPath CIA. Use this command to reserve the specified network processor. Command Examples UR NP 7000 UR NP 200 UR NP<device number> Note: This command does not apply to servers with HMP FastPath CIA. Use this command to restore the specified network processor. Command Examples UR - NP 7000 UR - NP

170 Operations Reports NP UNUSABLE This report shows the status of a network processor. The syntax is NP <device number> TYPE <NP type> UNUSABLE DUE TO <reason> <interface level> <software version ID> NP Event Notification This report notifies the system administrator that a Windows-based network processor (NP), such as a ClearPath Network Appliance (CNA) device or a Windows server, has encountered a reportable event. Currently, there are two types of events that are reported: A Crash Dump event indicating that a system reboot due to a system crash has occurred and a dump file is available for analysis. An SNMP trap can also be generated to notify a remote administrator that a system crash dump has occurred. A Raid Failure event indicating that an NP has a failed Raid disk When the NP Event Notification report appears in the system SUMLOG, a waiting entry message is displayed to notify the system operator. If a Crash Dump occurs, the operator or system administrator should retrieve the dump from the specified location and send it to Unisys support for analysis. If a Raid failure occurs, the operator or system administrator should schedule a replacement of the failed disk to restore redundancy to the raid array. The syntax is NP Event Notification Report Report Type=<type> <event info> where: <type> = None (0) Information (1) Warning (2) Critical (3) <event info> = Crash Dump Occurred On NP <np id> Name: <host name> Dump Information: <dump info> Raid Failure Occurred On NP <np id> Name: <host name> Event Information: Array 1 is Critical at startup

171 Section 7 Troubleshooting This section provides troubleshooting information for Network Services software. Table 7-1 lists various problem situations and the actions you can take to correct the problems. If you have an Electronic Service Request (ESR) agreement, your Customer Support Center (CSC) is automatically notified if certain networking products generate a system dump on the application host. These products include TCP/IP, SNMP Agent, CNS, BNA, and NAU. A CSC representative will contact you, but in the meantime you should also report the problem to Unisys. See Submitting Trouble Reports in Section 6 for details on how to submit information and which information to include. Troubleshooting Network Services Software The following table describes various problems you might experience with Network Services software and suggests possible corrective actions. Table 7 1. Troubleshooting Network Services Problem Possible Corrective Action Applies To The Windows Network Connections manager reports Network cable unplugged status for a EVLAN. Connecting to the MCP from the Windows server fails or uses the public LAN rather than EVLAN on servers with more than 4 NICs defined. The network cable unplugged status now indicates that the connection group on the MCP server is closed. See Microsoft knowledge base article , How to Disable NetBT Per Adapter Cache Behavior for information about a registry setting that must be made on Windows servers that have more than four network adapters being used for NetBIOS over TCP/IP communications. All Platforms Libra Series servers

172 Troubleshooting Table 7 1. Troubleshooting Network Services Problem Possible Corrective Action Applies To The response to the NW NP <NP #> command for an NNS device indicates that the device is NASCENT. The status <OUT OF SERVICE> is reported when you issue the OL PORT <port #> command. This occurs after Network Services has been running successfully. The following message displays when you issue the UR PORT command: PORT <port #> is available, but it is unusable as a path to all controls it services. Check for a popup window on the Windows server for the Service Control Manager indicating that "At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details". In this case, the event log would be the Windows system event log. Look for log entries for the Service Control Manager of the appropriate date and time and examine them. If the description indicates that any of the NNS services or drivers listed in Appendix B failed to start or load then a reboot of the Windows server is necessary to restart NNS. Also, check for a popup window indicating that an application error has occurred and an application error log is being generated. If this window indicates that any of the NNS services listed in Appendix B is at fault then a reboot of the Windows server is necessary to restart NNS. In some rare cases, an NxNet uninstall and reinstall may be necessary to resolve the problem of one of the services or drivers (in Appendix B) not starting properly. Note that a state of NASCENT is normal in some cases while the MCP Server is waiting for the Windows server to complete its boot cycle and initialize the NNS device. The Windows server boot cycle may take several minutes to complete. See Section 6 for a description of the materials to collect when reporting these types of problems. Network Services was stopped for more than 10 minutes for any reason. These reasons could include manually stopping the service, rebooting the Windows server, or a software or hardware failure that caused the Windows server to halt. To correct the problem, issue the UR PORT command after Network Services is active. 1. From the desktop, right click on "My Computer" and choose "Manage". 2. Select "System Information" and then "Software Environment". 3. Select "Drivers" and verify that the Unisys NNSDRLOG Driver (nnsdrlog) is running. 4. Select "Services" and verify that the Unisys Network Services service (CNP) is running. All Platforms All Platforms MCPvm

173 Troubleshooting Table 7 1. Troubleshooting Network Services Problem Possible Corrective Action Applies To The following message displays when you issue the UR CTL command: CTL <control #> not made available. It is not in partition. The following messages display when you issue the UR PORT command: PORT <port #> HAS BEEN REPORTED BROKEN BY THE IOP. PORT <port #> NOT MADE AVAILABLE. IT FAILED TO INITIALIZE. PORT <port #> NOT USABLE AS AN ABC CHANNEL. IT FAILED ABC PROTOCOL INITIALIZATION. PORT <PORT #> WILL NOT BE USED; ABC PROTOCOL FAILED TO INITIALIZE. The control number was not acquired. Use the ACQUIRE CTL command as follows: ACQUIRE CTL <control # of NP> where <control #> is 7000 for a PCI bridge, increments by 2 up to 7018 for the 10 th PCI bridge, and is 210 for emulated systems. These messages indicate that Network Services has not been installed correctly on the Windows server. See Installing Network Services in Section 2 for instructions for installing Network Services on the Windows server. Also see Bringing Network Services Into Service for the First Time and Reinitializing Network Services in Section 6. See Gathering Values for Installation in Section 2 for information. Also see Examining or Updating Network Services Values in Section 3 or 4. MCPvm All platforms

174 Troubleshooting Table 7 1. Troubleshooting Network Services Problem Possible Corrective Action Applies To You see a Windows blue screen with an error message that describes the problem and the module where the problem occurred. A serious problem has occurred. Report the problem to your Unisys representative, and submit the following: NP dump file from the MCP server Event Log backup from the Windows server Problem description as reported on the first three lines of a Windows blue screen Crash dump file MEMORY.DMP. (If the Windows server is configured to do so, it puts this crash dump file into the directory that is specified in the Recovery section of the System applet on the Control Panel.) See these topics in Section 6 for related information: Recovering the Windows Event Log Recovering the Windows Event Log Manually Submitting Trouble Reports Also see this topic in Section 2: Managing the NetBIOS Name Cache After encountering a Windows blue screen, use the following procedure to recover from the Windows stop: 1. Issue the UR PORT <port#> command for the port associated with the Windows server. 2. Wait for the Windows server to finish copying its memory to a dump file. The memory image copy is complete when the message beginning Restart and set the recovery options in the system control panel is displayed at the bottom of the screen. 3. Issue the UR- PORT <port#> command to bring the port online. 4. Power off and power on the Windows server. Wait for the Windows server to complete its initialization. All platforms A message indicating that the Event Log is full displays. Examine the contents of the Windows Event Log. If you don t notice anything unusual, you may need to change the parameters of the Event Log as described in Completing Installation of Network Services (Virtual Machines with Multiple NPs). All platforms

175 Troubleshooting Table 7 1. Troubleshooting Network Services Problem Possible Corrective Action Applies To You cannot establish connections to network drives in the MCP environment over a non-evlan path. You are able to successfully PING a remote host by specifying its name, but when you try to connect a network drive to a share on the remote host, you get the following message: SEMAPHORE TIMEOUT PERIOD HAS EXPIRED An OL NP inquiry on the EVLAN adapter (700n or 210) shows that the NP is active - communicating, but the response to an NW NP <device number> inquiry is GREETING SENT. You are not sure if data is taking the EVLAN data path During CNS initialization file processing on the MCP server, the following error message displays in response to an ADD CONNECTIONGROUP command for a Network Services shared adapter: Hardware Not Present Check the Services applet on the Control Panel to verify that Network Services is running. Network Services may be attempting to use the EVLAN path when it is not available. To restore the non-evlan path See Directing Data through the Fast Ethernet Switch Data Path in Section 3, Directing Data through the Ethernet Switch Data Path in Section 4, or Directing Data through the Externally Configured LAN in Section 5. Also see Managing the NetBIOS Name Cache in Section 2 for information about how Network Services manages the NetBIOS Name Cache. The NetBIOS remote name cache probably contains an entry for the remote host that cannot be used. This usually occurs when the LMHosts file contains an entry for the MCP server using the EVLAN path, but the Network Services service is not running. To restore the non-evlan path, see Directing Data through the Fast Ethernet Switch Data Path in Section 3, or Directing Data through the Externally Configured LAN in Section 5. Also see Managing the NetBIOS Name Cache in Section 2 for information about how Network Services manages the NetBIOS Name Cache. It is likely that the NP Unit Number for Network Services defined in the Windows environment does not match the NP Number defined in the MCP environment. To update NP Unit Number in the Windows environment so that it matches the number defined in the MCP environment, see Examining or Updating Network Services Values in Section 3 or 4. Step 4 of the procedure describes how to change the value. Refer to Verifying Network Services Installation in Section 2 for two test procedures to use. Verify that the LINEID specified in the initialization file matches the CNS Line ID specified during Network Services Setup. All platforms All platforms MCPvm All platforms All platforms

176 Troubleshooting Table 7 1. Troubleshooting Network Services Problem Possible Corrective Action Applies To During CNS initialization file processing on the MCP server, the following error message displays in response to an ADD CONNECTIONGROUP command for a Network Services shared adapter: Invalid Attribute Value ClearPath Network Appliance Problems The IP address for Network Services EVLAN is not correct (as shown in the configuration summary of the Adapters.txt file generated by Network Services Setup) MCP Cryptographic Services does not work when the Windows Firewall is active on a Windows 7 system. Verify that the value specified as the local address (in the initialization file ADD CONNECTIONGROUP command) matches the MAC address of the adapter NIC in the Windows server. For additional information, see Determining Fast Ethernet or Gigabit Ethernet Information in Section 3 or 4. Verify that the speed setting is appropriate for the adapter type you are using. Refer to the appropriate ClearPath Network Appliance Implementation Guide for troubleshooting procedures for the CNA on Libra Series native MCP servers. Examine the IP address for Network Services EVLAN via the Windows Control Panel for the correct value. For details, see Examining or Updating Network Services Values in this guide. Note that changes to Network Services parameters via the Windows Control Panel are not reflected in the Adapters.txt file. To keep this file up to date, use Network Services Setup to make configuration changes. Firewall Products, such as Windows Firewall may not work with the EVLAN drivers. To maintain all EVLAN functions, you should deactivate the Windows Firewall on the EVLAN adapter. All platforms Libra Series native MCP servers, FS1800 servers All platforms MCPvm

177 Appendix A Building Network Initialization Files This appendix provides guidelines for building CNS, TCP/IP, and BNA network initialization files and also includes a preconfigured SNMP initialization file. You can find sample CNS and TCP/IP initialization files for the following servers on the Network System Software NETSYSTEM release media. VMMCP servers (LX 180, Libra Model 400, Libra Model 450, Libra Model 460, Libra Models 4080 and 4090, FS1700, and SP1760) Libra 4000, and FS1800 servers Libra Model 680 and 690 servers In addition, a preconfigured SNMP agent initialization file is included on the NETSYSTEM release media. If you want to create your own CNS or TCP/IP initialization files, refer to the sample files on the NETSYSTEM release media and to the Guidelines for Building CNS Initialization Files or Guidelines for Building TCP/IP Initialization Files sections later in this appendix. If you want to create BNA (also known as Heritage Network Services) initialization files, refer to Guidelines for Building BNA Initialization Files later in this appendix A 1

178 Building Network Initialization Files Preconfigured CNS and TCP/IP Initialization Files The following sections describe the CNS and TCP/IP sample initialization files for all ClearPath Series model groups. CNS and TCP/IP Initialization Files - VMMCP Servers These CNS and TCP/IP initialization files define the commands preconfigured for ClearPath VMMCP servers with or without shared adapters. INIT/SAMPLE/CLEARPATH/VMMCP/CPMCP1/CNS This CNS initialization file defines the CNS commands preconfigured for ClearPath servers with the standard EVLAN path (NP 210 line 0) and Fast Ethernet shared adapter (NP 210 line 1). Minor changes are required to support a Gigabit Ethernet adapter. This file can be used to support a Fast Ethernet port aggregation shared adapter. Such an adapter is defined through the use of a unique Line ID. For additional information, see Preparing to Use Fast Ethernet Port Aggregation in Section 2. INIT/SAMPLE/CLEARPATH/VMMCP/CPMCP1/TCPIP This TCP/IP initialization file defines TCP/IP configuration commands that are preconfigured for ClearPath servers with a Fast Ethernet or Gigabit Ethernet shared adapter. CNS and TCP/IP Initialization Files - Libra Model 680 and 690 Servers These CNS initialization files define the commands preconfigured for ClearPath Libra Model 680 and 690 servers: INIT/SAMPLE/CLEARPATH/CS680/CPMCP1/CNS These TCP/IP initialization files define the TCP/IP commands preconfigured for ClearPath Libra Model 680 and 690 servers: INIT/SAMPLE/CLEARPATH/CS680/CPMCP1/TCPIP CNS and TCP/IP Initialization Files - Libra 4000 Servers These CNS initialization files define the commands preconfigured for ClearPath Libra 4000 servers: INIT/SAMPLE/CLEARPATH/CS4000/CPMCP1/CNS INIT/SAMPLE/CLEARPATH/CS4000/CPMCP1/TCPIP A

179 Building Network Initialization Files Preconfigured SNMP Initialization File This SNMP initialization file provides the preconfigured SNMP configuration commands for identifying required information for an SNMP Management station. INIT/SAMPLE/SNMPAGENT/INITFILE Notes: The ADAPTERNAME attribute cannot be used to map shared adapters to the MCP; mapping is provided by the LINEID attribute. The ADAPTERNAME attribute is still accepted but will be ignored. ADAPTERNAME will be deimplemented in a future release. There is no need to specify SPEED attribute values for LAN shared adapters. Connection Services forces SPEED=*DEF which causes the shared adapter hardware to return an actual speed value when the connection group is opened A 3

180 Building Network Initialization Files Using NAU Network Version Dump Files If you use the Network Administrative Utility (NAU) to configure the MCP server, you can load the appropriate sample NAU network version disk dump file for editing or review. These files are: For this System Load this Sample NAU Network Version Disk Dump File System Name LX 170, Libra 400, Libra 450 (VMMCP) Libra Models 680, 690, 750, 780 and 790 With Shared Adapters VMMCP_SA CS680 With Shared Adapters and Heritage Network Services VMMCP_SA_BNA Libra Model 4000 CS 4000 Note: You can define a router (gateway) IP address for your router on the NAU TCP/IP DEFAULT ROUTE LIST screen. For additional information, refer to the TCP/IP Implementation and Operations Guide. If you are loading the file for editing, load it to a version name that is different than the samples. This will prevent your version disk dump file from being overwritten if you update your NAU release. For additional information about loading an NAU network version disk dump file, refer to the Network Administrative Utility Operations Guide. A

181 Building Network Initialization Files Guidelines for Building CNS Initialization Files This section provides general guidelines for building a CNS initialization file. The examples in this section are taken from the following file on the NETSYSTEM release media: INIT/SAMPLE/CLEARPATH/CIOM/SHARED_ADAPTERS/CNS A connection group is required for each network interface For each network interface: Windows server and ClearPath Network Appliance devices always have 1 EVLAN connection group and may have up to 8 shared adapter network interfaces NW AUTHORIZE statements are included as follows. Adjust for your own environment: NW AUTHORIZE *DEFAULT = NETWORKCONTROL;% NW AUTHORIZE ADMINISTRATOR AT CPMCP1 = SECURITY;% The NW CONNECTION GROUP statements you may need to change are ICPDEVICEID, LINEID, and LOCALADDRESS, which must be set for an ICP26. The LOCALADDRESS is allowed to default for Network Services devices (Windows servers, CNA devices) by using *DEFAULT as shown in the following: ;% NW ADD CONNECTIONGROUP CG_ICP_70000% % Connection Group Information % ( TYPE = LAN%, ICPDEVICEID = 7000%, LINEMODULEID = 1%, LINEID = 0%, LOCALADDRESS = 08000B007000%, MAXINPUTMESSAGESIZELIMIT = 4352%, MAXOUTPUTMESSAGESIZELIMIT = 4352%, MAXINPUTMESSAGESIZE = 4352%, MAXOUTPUTMESSAGESIZE = 4352% )% NW ADD CONNECTIONGROUP CG_ICP_70001% A 5

182 Building Network Initialization Files % Connection Group Information % ( TYPE = LAN%, ICPDEVICEID = 7000%, LINEMODULEID = 1%, LINEID = 1%, LOCALADDRESS = *DEFAULT%, ADAPTERTYPE = FASTETHERNET% Note also that the MIMS, MOMS, MIMSL, and MOMSL values are required for an EVLAN connection. The recommended value is A

183 Building Network Initialization Files Guidelines for Building TCP/IP Initialization Files This section provides general guidelines for building a TCP/IP initialization file. The examples in this section are taken from the following file on the NETSYSTEM release media: INIT/SAMPLE/CLEARPATH/CIOM/SHARED_ADAPTERS/TCPIP Note that the following statements are included in the initialization file: NW TCPIP TCPIPIDENTITY NW TCPIP TCPIPIDENTITY ADD NP 200 LINE /24% There must be one TCPIPIDENTITY statement for each network interface. Each combination of NP and LINE in a NW TCPIP TCPIPIDENTITY statement must have a corresponding NW ADD CONNECTION statement. As of ClearPath MCP 11.0, you must use the new syntax for the TCPIP TCPIPIDENTITY command; the old syntax is no longer supported. For more information on this command, refer to the Networking Commands and Inquiries Help. NW TCPIP HOSTNAME NW TCPIP TCPIPHOSTNAME CPMCP1.SITE.CUSTOMER.COM;% % % Note that you have to set the TCPIPHOSTNAME. Include your fully qualified Domain Name in this statement. By default, all ClearPath initialization file samples name the host CPMCP1.SITE.CUSTOMER.COM NW TCPIP OPTION NW TCPIP OPTION - USERFCMTU;% % % Note that by default, USERFCMTU is reset to improve performance. NW TCPIP ROUTE ADD % NW TCPIP ROUTE ADD DEFAULT ;% % % Note that you need to uncomment and change this value to match the value of the router on your network segment. NW TCPIP MAPPING A 7

184 Building Network Initialization Files NW TCPIP MAPPING + CNA1% ;% % % % NW TCPIP MAPPING + CPNTA% ;% % The NW TCPIP MAPPING statements are included to associate the host name of the Windows servers and CNA devices with the EVLAN IP address of those devices. NW ADD CONNECTION TO NW ADD CONNECTION TO CG_ICP_2000% ;% 2000_TCPIP_2000% % Connection Information % ( NETWORKLAYERENTITY = IP%, REMOTEADDRESS = %, CLASS = CLASS1%, FRAMETRACE = FALSE%, RETRYLIMITXID = 10%, MAXINPUTMESSAGESIZELIMIT = 4352%, MAXOUTPUTMESSAGESIZELIMIT = 4352%, MAXINPUTMESSAGESIZE = 4352%, MAXOUTPUTMESSAGESIZE = 4352% )% A

185 Building Network Initialization Files This statement adds a connection to a connection group defined in a CNS initialization file. The entries that must be unique for each connection are: CONNECTION GROUP NAME CONNECTION NAME Note also that for the CLASS statement: CLASS_1 is for an EVLAN connection; ETHIP is for Ethernet connections. MIMS, MOMS, MIMSL, and MOMSL are required for an EVLAN connection. The recommended value is Guidelines for Building BNA Initialization Files This section provides general guidelines for building a BNA initialization file. It shows sample BNA configuration commands required to identify the Fast Ethernet or Gigabit Ethernet shared adapter of a LX 180, Libra Model 400, Libra Model 450, Libra Model 460, Libra Models 4080 and 4090, FS1700, and SP1760 servers. This adapter provides connections to a pair of BNA hosts (BNAHOST1 and BNAHOST2. For BNA based operations, Network Services now supports Class of Service 2. To specify this class of service, simply add the following attribute to each required connection: CLASS = CLASS_2 Sample BNA Initialization File % On the following lines, REMOTEADDRESS values are configured % addresses. ICP's do not have hardware-specific MAC addresses. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % Local Identity % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% NW LOCALIDENTITY CPMCP1(1,1,1,1)% NW ADD CONNECTION TO CG_ICP_2101% 2101_BNAHOST1_1% % Connection Information ( NETWORKLAYERENTITY = ROUTER%, REMOTEADDRESS = 08000B000834), % <--- See shaded comment 2101_BNAHOST2_1% % Connection Information ( NETWORKLAYERENTITY = ROUTER%, REMOTEADDRESS = 08000B000C1C); % <--- See shaded comment %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % END INITIALIZATION % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% NW ENDINITIALIZATION;% A 9

186 Building Network Initialization Files Note that in this file, you must: Set the LOCALIDENTITY. Add component connections to your connection groups for each remote host you are communicating with by using the NW ADD CONNECTION statement. Do not add component connections to an EVLAN connection group. EVLAN can only be used for TCP/IP. The NETWORKLAYEDIDENTITY value is always ROUTER for BNA. The REMOTEADDRESS value must match the LOCALADDRESS of the connection on the remote host. The last statement in BNA initialization files in NW END INITIALIZATION. SNMP Initialization File This SNMP initialization file (INIT/SAMPLE/SNMPAGENT/INITFILE) provides the preconfigured SNMP configuration commands for identifying required information for an SNMP Management station. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%% MCP SNMP Sample Init File %%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%% %%%%% %%%%% This file is not a configured SNMP initfile. It is meant to %%%%% %%%%% be used as a guide for building a configured SNMP initfile. %%%%% %%%%% The xxx.xxx.xxx.xxx IP addresses must be changed to valid %%%%% %%%%% IP addresses; if those commands are used, they must be %%%%% %%%%% uncommented. The community values listed as "community" %%%%% %%%%% must be changed to values that cannot be easily guessed; %%%%% %%%%% this must be done to provide increased security from %%%%% %%%%% malicious attacks. (Do not remove the quotes; they are %%%%% %%%%% required for processing the command.) The ReadOnly community %%%%% %%%%% string CPMCP1 must also be changed. %%%%% %%%%% The first section contains the read-only COMMUNITY SET and %%%%% %%%%% examples of read-write COMMUNITY and TRAPCOMMUNITY commands %%%%% %%%%% usable on all MCP platforms; the second section contains %%%%% %%%%% examples of the COMMUNITY/TRAPCOMMUNITY SET commands with %%%%% %%%%% Server Sentinel explicit comments for Server Sentinel %%%%% %%%%% knowledgable users. The third section contains the SETs %%%%% %%%%% for System variables and the object managers. Commands %%%%% %%%%% which are not commented out should be included in the %%%%% %%%%% SNMP initfile (the only exception being the read-only SET %%%%% %%%%% in environments that want to tightly control read-only %%%%% %%%%% access.) %%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % The first command allows read-only access from all IP addresses. %NW SNMP COMMUNITY ADD "CPMCP1" ReadOnly; % % The next command sets read-write access from a particular IP address A

187 Building Network Initialization Files % Update the community value and the IP address; copy the command % to give read-write access to multiple IP addresses/community strings. %NW SNMP COMMUNITY ADD % % "community" xxx.xxx.xxx.xxx ReadWrite;% % % The next commmand identifies a destination for traps from this system. % Update the IP address to a valid IP address destination; copy the % command to add more destinations. %NW SNMP TRAPCOMMUNITY ADD % % "public" xxx.xxx.xxx.xxx;% % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % Server Sentinel % The next command adds SP0. %NW SNMP COMMUNITY ADD % % "community" xxx.xxx.xxx.xxx ReadWrite;% % % The next command adds SP1. %NW SNMP COMMUNITY ADD % % "community" xxx.xxx.xxx.xxx ReadWrite;% % % Add the external Management Server if it exists. %NW SNMP COMMUNITY ADD % % "community" xxx.xxx.xxx.xxx ReadWrite;% % % Define a SNMP TRAPCOMMUNITY for each Service processor and the % external management server if it exists. As sites may/may not use the % default IP addresses for SP0 and SP1, the IP address must be updated; % the command must be uncommented to use. The community value does not % need to be updated unless the "public" community value has not been % defined on the system. % % Add SP0 Trapcommunity %NW SNMP TRAPCOMMUNITY ADD % % "public" xxx.xxx.xxx.xxx;% % % Add SP1 Trapcommunity %NW SNMP TRAPCOMMUNITY ADD % % "public" xxx.xxx.xxx.xxx;% % % Add the external Management Server trapcommunity if it exists. %NW SNMP TRAPCOMMUNITY ADD % % "public" xxx.xxx.xxx.xxx;% % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % The next command sets the SysContact, SysName, and SysLocation % objects. Change the values in parentheses to meaningful values. % (Do not remove the parentheses; they are needed for processing the % command.) NW SNMP SET SysContact = "ClearPath Administrator" %,SysName = "ClearPath System" % A 11

188 Building Network Initialization Files,SysLocation = "ClearPath Location" % ; % % The next command identifies the Host Resources Object Manager to % the SNMP Agent. NW SNMP SET % agentapiprowstatus "Host Resources MIB Object Manager" = 4%,agentAPIPCodefile "Host Resources MIB Object Manager" = "RUN *SYSTEM/SNMPOBJMGR/HOSTMIB"%,agentAPIPAdminStatus "Host Resources MIB Object Manager" = 1%,agentAPIPRspTimer "Host Resources MIB Object Manager" = 5% ;% % % The next command identifies the MCP Resource Object Manager to the % SNMP Agent. NW SNMP SET % agentapiprowstatus "MCP Resource Object Manager" = 4%,agentAPIPCodefile "MCP Resource Object Manager" = "RUN *SYSTEM/SNMPOBJMGR/MCP"%,agentAPIPAdminStatus "MCP Resource Object Manager" = 1%,agentAPIPRspTimer "MCP Resource Object Manager" = 5% ;% % % The next two commands set the agent response timer to a value higher % than the default of 3 seconds. (The response timers for the object % managers above are also set higher than the default. Setting the % response timer to a higher value is recommended for MCP platforms % with high processor demand.) Note that the CNS Object Manager and % the System/Assistant Object Manager can only have the response timer % timer set; these are libraries and the other objects normally set in % the initfile for object managers cannot be set for libraries. NW SNMP SET % agentapiprsptimer "CNS Object Manager" = 10% ;% NW SNMP SET % agentapiprsptimer "System/Assistant Object Manager" = 10% ;% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% A

189 Appendix B Network Services File Summary Table B-1 lists all code and data files created when you install Network Services software. As indicated, these files are located in directories NXNET and %SYSTEMROOT% of the Windows server file system. Table B 1. Network Services File Summary Directory\File When Installed Description NXNET\ readme.txt adapters.txt NNS_Install.log lmhosts.org dllnetcfg.dll NXNET\Images\ netunsld.inf netujavm.inf netuja_rn.inf Always Always Always Always Always Windows Windows Windows Release notes Shared adapter summary Installation diagnostic log LMHOSTS include backup Uninstall wrapper DLL INF file for NNS Legacy drivers INF file for Janus service INF file for Janus miniports netucfid.inf netujavm2.inf netuja_m2.inf netujavm3.inf netuja_m3.inf netujavm4.inf netuja_m4.inf Windows 2003, Libra 680 and 690, Libra 750,780, and 790, Libra 880 and 890, and FS1800 VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=4 VM-MCP Multi-NP>=4 INF file for FC-IOP driver (FID) (CIA) INF file for Janus service INF file for Janus miniports INF file for Janus service INF file for Janus miniports INF file for Janus service INF file for Janus miniports B 1

190 Network Services File Summary Table B 1. Network Services File Summary Directory\File When Installed Description %SYSTEMROOT %\SYSTEM32\ cnp.exe NSStreamUL.dll ciawin32.exe jtdnotify.dll cnp2.exe cnp3.exe cnp4.exe jtdnotify2.dll jtdnotify3.dll jtdnotify4.dll %SYSTEMROOT %\SYSTEM32\ DRIVERS\ NSStream.sys nnsdrlog.sys janus.sys qspcia.sys qsp.sys openca.sys dtcm.sys mss.sys ciapci.sys Fid.sys janus2.sys janus3.sys janus4.sys nnsdrlo2.sys nnsdrlo3.sys nnsdrlo4.sys NSStrea2.sys NSStrea3.sys NSStrea4.sys openca2.sys openca3.sys openca4.sys qsp2.sys qsp3.sys qsp4.sys Always Always Sites with CIA Windows VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=4 VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=4 Always Always Always Sites with CIA VM-MCP VM-MCP Always Always Sites with CIA Libra Model Native MCP Systems VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=4 VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=4 VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=4 VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=4 VM-MCP Multi-NP>=2 VM-MCP Multi-NP>=3 VM-MCP Multi-NP>=4 CNP service NNS Streams support CIA (HMP FastPath - CIA) dialog management services support Notify object DLL for Janus CNP service NP2 CNP service NP3 CNP service NP4 Notify object DLL for Janus NP2 Notify object DLL for Janus NP3 Notify object DLL for Janus NP4 NNS Streams driver NNS support driver Janus driver Queue service provider (CIA) Queue service provider (CIA) Open channel adapter driver Distributed TCP/IP Com. Mgmt. driver Messaging Subsystem driver for DTCM CIA (HMP FastPath - CIA) PCI Bridge FC-IOP driver Janus driver NP2 Janus driver NP3 Janus driver NP4 NNS support driver NP2 NNS support driver NP3 NNS support driver NP4 NNS Streams driver NP2 NNS Streams driver NP3 NNS Streams driver NP4 Open channel adapter driver NP2 Open channel adapter driver NP3 Open channel adapter driver NP4 Queue service provider NP2 Queue service provider NP3 Queue service provider NP4 B

191 Network Services File Summary Table B 1. Network Services File Summary Directory\File When Installed Description %SYSTEMROOT %\SYSTEM32\ DRIVERS\ETC\ lmhosts.cnp Imhosts.org Always Always LMHOSTS include file LMHOSTS include backup B 3

192 Network Services File Summary B

193 Index A ADAPTERTYPE attribute (for defining EVLANs and shared adapters), 6-10 ADD NP ATTACHMENT MAPPING networking command, 6-12 attributes configuring 9000-byte Jumbo Frames, 5-2 configuring with the NAU, 3-9 determining adapter information, 3-8 EVLAN, 6-10 Jumbo Frames, 2-11 shared adapters, 6-10 B BNA connecting native MCP network with, 5-1 connecting VMMCP network with, 5-2 initialization file building, A-9 integrating networks with, 5-1 using initialization files, 3-8 browse feature browsing across subnets, 5-4 enabling workstations to browse MCP environment, 5-3 general description, 5-2 C central processor module (CPM), 1-15 changing IP address for Network Services, 2-7 channel adapters data types, 6-10 CLEAR NP networking command, 6-12 system command, 6-16 ClearPath Network Appliance (CNA) Libra Series native MCP and FS1800 networking values, 3-4 maintenance LAN IP addresses for Libra Series native MCP and FS1800 servers, 3-21 CNP configuring with NAU, 3-10 dump data, 6-6 CNS initialization file creating, 3-9 guidelines for building, A-5 preconfigured (Libra Series native MCP and FS1800 servers), 3-4 preconfigured (VMMCP servers), 4-4 CNS Line ID property, 2-13 CNS REMOTEINSTALL command, 2-43 configuration values Libra 4000 servers, 2-7 Libra Series native MCP and FS1800 servers, 2-8 networking values for Libra 4000 servers, 4-7 networking values for Libra Series native MCP and FS1800 servers, 3-4 networking values for VMMCP servers, 4-5 storing in Windows registry, 2-5 updating Network Services information, 2-5 VMMCP servers, 2-7, 4-3 Windows server values, 3-25 configuring IP addresses on Windows servers, 3-25 Network Services on a partitionable server, 2-6 updating MCP network configuration, 3-4 CONNECTION inquiry, 6-12 connection overview TCP/IP and Heritage Network Services, 1-20 connection status, 2-35 Console for MCP, 1-16 Console Manager, 1-18 control number, 2-32, 6-2, 6-18, 6-19 CPM (central processor module), 1-15 crash recovery Index 1

194 Index file, 7-4 setting parameters, 2-19, 2-28 Crypto Co-processor IP addresses, 1-13 D data path EVLAN, 2-35 excluding the EVLAN path, 2-38 DELETE NP ATTACHMENT MAPPING command, 6-12 DHCP (Dynamic Host Configuration Protocol), 3-3, 4-3 DNS (domain name server), 3-2, 4-2 domain name server (DNS), 3-2, 4-2 domains, in Microsoft Networks assigning units to, 5-5 dump files NAU network version, using, A-4 Network Services, 6-6 NP, 6-6 DUMP NP command, 6-13 Dynamic Host Configuration Protocol (DHCP), 3-3, 4-3 E Enhanced Virtual LAN (See EVLAN) ESTABLISHCALL command, 6-15 Ethernet Jumbo Frames preparing to use, 2-11 Ethernet NIC, 1-17 event log location, 6-6 recovering, 6-6, 6-7 viewing online, 6-6 EVLAN attributes, 6-10 configuring data path for the Windows server, 3-34, 4-15 described, 1-3 examining driver values VMMCP servers, 4-11 examining values, 3-31 excluding data path, 2-38 overview of EVLAN adapter, 1-5 specifying data path, 2-38, 3-35 verifying Network Services installation, 2-33 EVLAN data path, specifying, 4-16 F Fast Ethernet Heritage Network Services (BNA) support, 1-4 NAU support of, 1-5 NIC, 1-17 Fast Ethernet port aggregation preparing to use, 2-10, 3-13 Fast Ethernet shared adapters configuration information, 3-8 preparing for, 2-10 replacing with a different type, 2-40 updating driver for, 2-40 Fast Ethernet switch described, 1-14 rebooting, 3-41 specifying data path to MCP, 3-37 FC3-IOP described, 1-19 IP addresses, 1-12 Forward RIP Frames to MCP property, 2-13 FS1100 servers diagram, 1-7 FS1300 servers diagram, 1-7 FS1700 servers diagram, 1-7 FS1800 servers installing Network Services, 2-16 MCP networking values, 3-4 Network Services configuration values, 2-8 FTP, 3-39, 4-20 G Gigabit Ethernet NIC, 1-18 Gigabit Ethernet network components Libra 4000 servers, 1-6 Gigabit Ethernet shared adapters configuration information, 3-8 preparing for, 2-10 replacing with a different type, 2-40 updating driver for, 2-40 Index

195 Index H Heritage Network Services (BNA) integrating networks with, 5-1 using initialization files, 3-8 HMP FastPath - CIA configuration information, 6-1 host parameters, defining, 3-17 HOSTS file, 3-2, 4-2 I IEEE 802.1Q VLANS preparing to use, 2-12 initialization files BNA, 3-8 CNS, 3-9 creating with NAU, 3-9 described, A-1 guidelines for building BNA files, A-9 guidelines for building CNS files, A-5 guidelines for building TCP/IP files, A-7 Heritage Network Services, 3-9 Libra Model 180 servers, 3-7 Libra Model 680 and 690 servers, A-2 Libra Series native MCP and FS1800 servers, 3-7 preconfigured files, 3-4 required information for SNMP Management station, A-10 SNMP, A-3 VMMCP servers, 4-11, A-2 installation interface (Network Services) for a partitioned system, 2-6 functions, 2-5 installing Network Services in the Windows server environment, 2-15 Network Services on Libra Series native MCP and FS1800 servers, 2-16 Network Services on MCP server, 2-15 Network Services on VMMCP servers, 2-20 overview of the process for Network Services, 2-2 Internet host name, defining, 3-17 IP addresses changing for Network Services EVLAN path, 2-7 configuring (Libra Series native MCP and FS1800 servers), 3-3 J configuring for workstations, 3-30 configuring maintenance LAN, 3-20 configuring on VMMCP servers, 4-3 preventing private addresses from being sent to WINS Server, 3-3, 4-3 reconfiguring WINS servers, 3-40, 4-21 SAS-IOP and FC3-IOP, 1-12 SCSI tape appliance and Crypto Coprocessor, 1-13 Windows servers (Libra Series native MCP and FS1800 servers), 3-25 Janus Surrogate adapters, 3-32, 4-13 Jumbo Frames attributes, 2-11 preparing to use, 2-11 L Libra 4000 servers configuration values, 2-7 diagram, 1-7, 1-8 MCP networking values, 4-7 network architecture description, 1-6 Libra Model 185 servers MCP networking values, 3-4 Libra Model 400 servers diagram, 1-7 Libra Model 580 and 590 servers MCP networking values, 3-4 Libra Model 585 and 595 servers MCP networking values, 3-4 network architecture description, 1-6 Libra Model 680 and 690 servers diagram, 1-11 I/O subsystem, 1-10 initialization files, A-2 MCP networking values, 3-4 MCP partitions, 1-9 network architecture description, 1-6 non-mcp partitions, 1-9 optional components, 1-9 Libra Series native MCP servers configuration values, 2-8 installing Network Services, 2-16 TCP/IP network integration, 3-1 LINEID attribute (for defining shared adapters), Index 3

196 Index LMHOSTS file, 3-2, 4-2 and browsing across subnets, 5-4 Libra native MCP, and FS1800 servers, 3-34 setting up, 2-30, 2-35, 2-38 used to specify the EVLAN data path, 2-47, 4-16 used to specify the external LAN data path, 4-18 LocalAddress attribute (for defining VLANs and shared adapters), 6-11 LX7100 servers diagram, 1-7 M MAICP4 description, 1-6 dump data, 6-6 emulation on VMMCP servers, 1-16 link between virtual MCP and Windows, 1-6 preconfigured values, 3-6 maintenance hub, 1-15 maintenance LAN described, 1-15 IP addresses, 3-20 maximum transmission unit (MTU) controlling on native MCP servers, 3-41 controlling on VMMCP servers, 4-22 MCP environment (VMMCP servers) rebooting, 4-21 MCP networking values Libra Series native MCP and FS1800, 3-4 VMMCP servers, 4-4 MCP networking, optimizing, 5-6 MCP server described, 1-15 mapping host names to IP addresses, 3-18 rebooting, 3-41 Microsoft Networks integrating ClearPath servers into, 5-2 MTU (maximum transmission unit) controlling on native MCP servers, 3-41 controlling on VMMCP servers, 4-22 multiple network processors installing Network Services on VMMCP servers, 2-20 N name resolution for EVLAN data path, 3-34 strategies for choosing, 3-1, 4-2 native MCP servers Network Services configuration values, 2-8 NAU configuring shared adapters, 3-12 creating initialization files, 3-9 NetBIOS name cache, managing, 2-30, 2-38 name resolution, 2-38 network applet, 2-5 network commands and inquiries CNS ADD NP ATTACHMENT MAPPING, 6-12 CNS CLEAR NP, 6-12 CNS REMOTEINSTALL, 2-43 CONNECTION, 6-12 DELETE NP ATTACHMENT MAPPING, 6-12 DUMP NP, 6-13 ESTABLISHCALL BY CONN, 6-15 NP, 6-15 REMOTEINSTALL, 6-16 UTILIZATION, 6-15 network configurations FS1100, FS1300, and FS1700 servers, 1-6 Libra 4000 servers, 1-8 Libra Model 400, 1-6 Libra Model 680/690 servers, 1-8 verifying for Libra native MCP and FS1800 servers, 3-41 network integration (VMMCP servers), 4-1 Network Services bringing into service, 2-31, 6-2 configuration values for Libra 4000 servers, 2-7 configuration values for Libra native MCP and FS1800 Series servers, 2-8 configuration values for VMMCP servers, 2-7 data types, 6-10 dump file, 6-6 EVLAN configuration and installation interfaces, 1-4 examining values (VMMCP servers), 4-11 file summary, B-1 initiating a dump, 6-6 installation values, gathering, 2-6 Index

197 Index installing Libra Series native MCP, and FS1800 servers, 2-16 installing Network Services on VMMCP servers, 2-20 MCP reports, 6-20 operations, 6-1 operations interface summary, 6-10 optimizing for EVLAN performance, 5-6 overview, 1-3 post-installation activities, 2-33 pre-installation activities, 2-5 recovering the event log, 6-6, 6-7 reinitializing, 6-3 reinstalling, 2-31, 2-46 removing, 6-3 removing from Windows server, 2-41 restoring a previous release, 2-46 SA configuration and installation interfaces, 1-4 setup program (partitioned system) reconfiguring on, 2-37 setup program for a partitioned system, 2-6 submitting trouble reports, 6-8 troubleshooting, 7-1 upgrading on a connected Windows server, 2-43 upgrading Windows, 2-1 verifying EVLAN installation, 2-33 verifying shared adapter installation, 2-35 viewing the event log online, 6-6 Network Services values examining, 3-31 updating (Libra Series native MCP and FS1800 servers), 3-31 network version dump files, using, A-4 networking configuration, verifying, 4-22 networking values Libra Series native MCP and FS1800 servers, 3-4 VMMCP servers, 4-4 NP dump files, 6-6 NP Event Notification report, 6-20 NP heartbeat timer, 3-10 NP inquiry, 6-15 NP number, 2-6 NP UNUSABLE report, 6-20 O ODW (See operator display workstation) OL CTL command, 6-16 OL NP command, 6-16 OL PORT command, 6-17 operator display workstation (ODW) described, 1-16 updating values, 3-30 P partitioned system configuring Network Services, 2-6 partitioned system reconfiguration, 2-37 PCI Bridge configuring with NAU, 3-10 PEND OPEN, 2-35 PER NP inquiry, 6-17 PING command specifying EVLAN path (native MCP servers), 3-39 specifying the EVLAN path (VMMCP servers), 4-20 verifying EVLAN path, 2-33 port aggregation preparing to use Fast Ethernet port aggregation, 2-10, 3-13 port number, 2-32, 6-2, 6-18 preparing to use Ethernet JumboFrames, 2-11 preparing to use IEEE 802.1Q VLANS, 2-12 preparing to use Quality of Service over LAN, 2-13 properties, shared adapters, 2-13 Q Quality of Service over LAN preparing to use, 2-13 R READY NP command, 2-32, 6-17 rebooting system environments, 4-21 Libra native MCP, and FS1800 servers, 3-41 rebooting Windows servers VMMCP servers, 4-21 reconfiguring shared adapter, 2-40 reinstalling Network Services, Index 5

198 Index REMOTEINSTALL command, 6-16 upgrading on a connected Windows server, 2-43 reports, 6-20 Request for Comments (RFC) 1122, 3-41, 4-22 RESET reports viewing on Libra Native MCP servers, 3-42 viewing on VMMCP servers, 4-23 restoring a previous release of Network Services, 2-46 RFC 1122, 4-22 S SAS-IOP described, 1-19 IP addresses, 1-12 SAVE NP command, 6-18 SCP (See system control processor) SCSI tape appliance described, 1-19 IP addresses, 1-13 Service Processor on CS7201/Libra Series, 1-18 setup program (Network Services) description of, 2-5 installing on native MCP servers, 2-16 installing on VMMCP servers, 2-20 management of LMHOSTS file, 2-30 using in a partitioned system, 2-6 shared adapters and Heritage Network Services (BNA), 1-4 attributes, 6-10 configuring with NAU, 3-12 obtaining MAC addresses, 3-8 obtaining names, 3-8 preparing to configure, 2-10 properties, 2-13 reconfiguring with network connections properties, 2-39 replacing or updating, 2-40 verifying installation, 2-35 SNMP initialization files, A-3, A-10 soft MCP server, 1-15 system commands CLEAR NP, 6-16 OL CTL, 6-16 OL NP, 6-16 OL PORT, 6-17 PER NP, 6-17 READY NP, 6-17 SAVE NP, 6-18 UR, 6-18 UR - CTL, 6-19 UR NP, 6-19 system control processor described, 1-16 T TCP/IP host name to IP address mapping, 3-18 initialization files, A-1 network integration in Libra Series native MCP servers, 3-1 packet size, controlling, 3-41 RESET reports, viewing, 3-42 TCP/IP initialization file creating (Libra Series native MCP, and FS1800 servers), 3-9 guidelines for building, A-7 preconfigured, 3-4 preconfigured (VMMCP servers), 4-4 trouble reports, submitting, 6-8 troubleshooting, 7-1 Network Services, 7-1 U UCFs, submitting, 6-8 UNIT RESERVE (UR) CONTROL command, 6-18, 6-19 UNIT RESERVE (UR) NP command, 6-19 UNIT RESERVE (UR) PORT command, 2-32, 6-18, 7-3 Unknown IP Frame Route property, 2-13 upgrading Network Services on a connected Windows server, 2-43 UTILIZATION inquiry, 6-15 V version control, 2-17 Virtual Machine for ClearPath MCP VMMCP) installing Network Services, 2-20 VMMCP servers configuration values, 2-7 Index

199 Index initialization files, A-2 initialization files (preconfigured), 4-4 IP addresses, configuring, 4-3 MCP networking values for, 4-4 TCP/IP network integration, 4-1 W Windows directing Windows data to MCP environment, 3-34 upgrading Network Services to later Windows version, 2-1 Windows Internet name server (WINS), 3-40 Windows event log location, 6-6 recovering, 6-6, 6-7 viewing online, 6-6 Windows Internet name server (WINS) and name resolution strategies, 3-2, 4-2 browsing across subnets, 5-4 preventing private IP address from being sent to, 3-3, 4-3 specifying IP address, 3-40 specifying IP address of VMMCP servers, 4-21 Windows server described, 1-15 in VMMCP environment, 1-6 IP addresses for Libra Series native MCP and FS1800 servers, 3-25 WINS (See Windows Internet name server) workgroups assigning units, 5-5 workstations configuring on Libra native MCP and FS1800 servers, 3-30 enabling to browse MCP environment, Index 7

200 Index Index

201 .

202 2013 Unisys Corporation. All rights reserved. * *