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
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
Choosing a Name Resolution Strategy
Entities in TCP/IP networks have numerical IP addresses, such as 192.63.100.98. For convenience, the networking software also allows users to refer to these entities by names, such as www.unisys.com. 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 Description
Domain name
server (DNS) 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.
HOSTS files 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 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.
Windows Internet name server (WINS 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 10011990 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.
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.
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.
Table 4–2. MCP Networking Values for VMMCP Servers
MCP Environment Preconfigured Value New Value
Host Name CPMCP1
TCP/IP Domain Name CPMCP1.SITE.CUSTOMER.COM NP number (optional) 200
IP Address 192.168.237.10
Subnet Mask 255.255.255.0
LAN Local Address 08000B002000
MAICP4 number 210 Do not change
EVLAN
IP Address 192.168.16.1 Do not change
(note 1)
Subnet Mask 255.255.255.0 Do not change
(note 1) LAN Local Address (line 0) 08000B002100 (note 2)
Shared Adapter #1
IP Address 192.168.237.150
(for LX7100 or CS7201 )
Subnet Mask 255.255.255.0
(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)
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)
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 192.168.16.5 Do not change (note 1) Subnet Mask 255.255.255.252 Do not change (note 1) LAN Local Address (line 0) 08000B002100 (note 2)
Shared Adapter #1 Reserved
IP Address
Subnet Mask
LAN Local Address (line 1)
NT Line-ID 2
Shared Adapter #2 Direct connection to JProcessor
IP Address 192.168.16.141
Subnet Mask 255.255.255.252
LAN Local Address (line 2)
*Default
NT Line-ID 3
Shared Adapter #3 Direct connection to ePortal
IP Address 192.168.223.250
Subnet Mask 255.255.255.0
Table 4–3. MCP Networking Values for Libra 4000 Servers
MCP Environment Preconfigured Value New Value
LAN Local Address (line 3)
*Default
NT Line-ID 4
MAICP4 number Instance 2, NP 211 Do not change
Shared Adapter #1
IP Address 192.168.237.50
Subnet Mask 255.255.255.0 (/24)
LAN Local Address (line 1)
*Default
NT Line-ID 1
Shared Adapter #2
IP Address 192.168.237.51
Subnet Mask 255.255.255.0 (/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 192.168.237.52
Subnet Mask 255.255.255.0 (/24)
LAN Local Address (line 1)
*Default
NT Line-ID 1
Shared Adapter #2
IP Address 192.168.237.53
Table 4–3. MCP Networking Values for Libra 4000 Servers
MCP Environment Preconfigured Value New Value
Subnet Mask 255.255.255.0 (/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 192.168.237.54
Subnet Mask 255.255.255.0 (/24)
LAN Local Address (line 1)
*Default
NT Line-ID 1
Shared Adapter #2
IP Address 192.168.237.55
Subnet Mask 255.255.255.0 (/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 192.168.237.56
Subnet Mask 255.255.255.0 (/24)
LAN Local Address (line 1)
*Default
NT Line-ID 1
Table 4–3. MCP Networking Values for Libra 4000 Servers
MCP Environment Preconfigured Value New Value
Shared Adapter #2
IP Address 192.168.237.57
Subnet Mask 255.255.255.0 (/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 08000B062259 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.
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.