Release 3.3.1 for Windows
Part No. A96684-01
 Contents |
 Index |
|
Oracle® Fail Safe Concepts and Administration Guide
Release 3.3.1 for Windows Part No. A96684-01 |
|
This appendix describes the network requirements for the Microsoft Windows software.
This appendix discusses the following topics:
| Topic | Reference |
|---|---|
| Registering Host Names and IP Addresses | Section B.1 |
| Validating Proper Name Resolution in the Cluster | Section B.2 |
| Troubleshooting Problems with Improper Name Resolution | Section B.3 |
Each IP address and its corresponding host name must be registered in either the Hosts file (in the system32\drivers\etc\ directory under the system directory) on each cluster node or in DNS regardless of whether or not WINS is used. You must register all of the following addresses:
If you make changes in any of the name registries (DNS server or Host file), use the following command to purge the local cache and make the changes effective:
nbtstat -R
This section describes how to ping all systems to validate that you have properly registered the IP addresses and host names. The procedures described in this section ensure that the same IP address is echoed when you ping a host name from the host itself and from any other systems.
Suppose there is a cluster of two systems and a client system. The host name of the systems and the cluster alias are shown in the following table:
| System | Host Name |
|---|---|
| Cluster system 1 | ClusterHost1 |
| Cluster system 2 | ClusterHost2 |
| Cluster alias | ClusterAlias |
| Client system | ClientHost |
On each system, Cluster system 1, Cluster system 2, and Client system ping all four host names. For example, on Cluster system 1:
ping ClusterHost1 ping ClusterHost2 ping ClusterAlias ping ClientHost
For each host name that you ping, the ping test should echo the same IP address. For example, if ClusterHost1 is registered to map to IP address 192.1.99.202, then pinging ClusterHost1 on Cluster system 1, Cluster system 2, and Client system should echo 192.1.99.202.
If all ping tests are successful, your network is configured correctly.
If any ping tests do not return the proper IP address, see Section B.3.
If the ping test in Section B.2 does not return the correct addresses, one of the following is probably causing the discrepancy:
You have incorrectly registered the IP address, or the host name, or both in the Host file or with the DNS server.
If you suspect this is the problem, reexamine Section B.1 to ensure that you have registered the addresses correctly, or contact your network administrator to verify your IP addresses and host names.
You have multiple network interface cards.
On a system with multiple network interface cards, multiple IP addresses are assigned to the host name. For example, Cluster system 1 has two network interface cards. Each card is assigned an IP address on a different network or subnet, as follows:
| Network | IP Address |
|---|---|
| Net1 | 192.1.22.101 |
| Net2 | 192.1.99.202 |
On system Cluster system 1, host name ClusterHost1 maps to both IP addresses, although the ping program echoes only one IP address. If the ping program does not echo the same IP address that is echoed on other systems, it could mean that there is an ordering problem with the IP addresses for the host name.
To correct an ordering problem, use the instructions in one of the following sections, depending on the Windows operating system you are using.
On systems running Windows NT version 4.0 Service Pack 5 or higher, you can modify the order in which IP addresses are mapped to the network name such that the well-known address is returned for the host name. To modify the mapping order:
Open the Windows Control panel.
Double-click Network.
Select the Bindings tab.
Select Show Bindings for all protocols.
Expand the TCP/IP Protocol folder.
Select the adapter you want to move, then click Move Up or Move Down to change the order.
Click OK.
The goal is to select an order such that the IP addresses map to the well-known address for the host name. When you complete your modifications, use the process described in Section B.2 to confirm that the new configuration is correct.
On systems running Windows 2000 Advanced Server or Datacenter Server, you can modify the order in which IP addresses are mapped to the network name such that the well-known address is returned for the host name. To modify the mapping order:
Open the Windows Control panel.
Double-click Network and Dialup Connections.
Select the Bindings tab.
On the Advanced menu, select Advanced Settings.
Select the Adapters and Bindings tab.
In the Connections box, select the adapter you want to move, then click the up or down arrow to change the order.
Click OK.
When you complete your modifications, use the process described in Section B.2 to confirm that the new configuration is correct.
|
 Copyright © 1996, 2002 Oracle Corporation All rights reserved |
|