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.
• 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 2
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.
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)”.
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.
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
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.
15. Click Next.
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 14.
• 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.