Intergraph WebScale User Manual page 73

WebScale™
Problem: Non-load-balanced application does not work properly.
Description: A TCP/IP application running on one of the cluster hosts does not appear
to work correctly when running WebScale. This application is not being load balanced.
Probable cause(s) and resolution:
1. One or more of the application's ports are being inadvertently load balanced. If
you create a port rule with a very large port range, you may inadvertently load
balance ports for other applications. Be sure that the port rules handle ports only
for the intended applications.
Problem: System error with net commands
Description: I am using WebScale's NBT support to scale the performance of Windows
NT read-only file access and printing. When I attempt to use the Microsoft network
commands, such as net view and net use, I get the following error: "System error
53 has occurred. The network path was not found."
Probable cause(s) and resolution:
1. The cluster's system name was not resolved to an IP address. The cluster's
system name, which is the first portion of the full Internet name, must be a known
NetBIOS machine name in order for the NetBIOS to resolve it into an IP address.
Be sure to create the appropriate static WINS, DNS, or LMHOSTS file entry;
please consult your Microsoft documentation for instructions on how to do this.
2. The cluster IP address is not the NIC's first IP address listed in the TCP/IP
configuration. Since the NetBIOS uses only the first IP address, the cluster IP
address must be listed first. Note that WebScale's NBT support cannot be used
in single NIC configurations since the dedicated IP address is always listed first
when a single NIC is used. To solve this problem, use multiple NIC's and be
sure that the cluster's primary IP address is listed first in the TCP/IP
configuration for the cluster NIC.
Problem: WebScale remote control commands fail.
Description: When I invoke the WebScale remote control commands from a system
outside the cluster, I get no response from one or more cluster hosts.
Probable cause(s) and resolution:
1. The cluster NIC's are not reachable from the outside system. If you have
multiple NIC's on a cluster host, the dedicated NIC may be on a separate subnet
from the cluster NIC. If you invoke a remote control command from an outside
system on this subnet, the cluster NIC's and WebScale driver will not receive the
command. Be sure that the cluster NIC's on the cluster hosts can be reached by
the outside system.
2. Remote control commands are sent to a secondary cluster IP address. Commands
must be sent to the cluster's primary IP address (which is entered in the WebScale
Setup dialog). Be sure that you send remote commands to this IP address.
3. WebScale's UDP control port is firewalled. By default, remote control
commands are sent to UDP port 1515 at the cluster IP address. Be sure that this
69
User's Guide