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.
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.
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 2.
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.
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.
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:
<IP address> <MCP host name> #PRE where:
<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
192.168.16.5 CPMCP1 #PRE
In an LX7100 system, to direct data from the Windows server to the MCP environment, enter
192.168.16.1 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).
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.