Netra Proxy Cache Array User's Manual

Installation of Proxy Cache and Array Configuration Fails

If installation fails for one or more hosts, note the reason in the page that reports the failure. The following conditions must be in effect for successful installation:

Each array member must be running and must be configured, as described in the Netra Proxy Cache Array Configuration Guide.

All host and service addresses must be unique and must have the same subnet number.

One host in the array must be configured as a DNS server for the array and must have a unique DNS service address with the same subnet number as the host and proxy cache service addresses.

All control addresses must be unique and must have the same subnet number.

If you configured a local name service (not recommended), you might have made a mistake so that, for example, on one or more hosts, the loopback interface is configured with the host address.

There are other, relatively remote possibilities, such as the update process being dead on a given array member. You could probably correct such an obscure problem by rebooting the affected host.

In the event of installation failure, consult the error logs.

To View Installation Error Logs

Click the home icon to load the Main Administration page.

Click Proxy Cache Service to load the Proxy Cache Administration page.

Under the Monitoring heading, click Log Files.

In the Proxy Cache Log Administration page, click View for the Administration Client Error log or the Configuration Installation Error log.

In addition to the error logs, a useful troubleshooting tool, if you have a serial connection to a Netra Proxy Cache Server, is ifconfig. On an array member, correct ifconfig output is as follows:

# ifconfig -a
lo0: flags=<num><UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
        inet 127.0.0.1 netmask ff000000

hme0: flags=<num><UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
        inet <host address> netmask <service net netmast> broadcast <service net number>.255
        ether <ethernet address>

hme0:1: flags=<num><UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,PRIVATE> mtu 1500
inet <proxy cache service address> netmask <service net netmast> broadcast <service net number>.255

The following entry (hme0:2:) is present only on the array DNS server:
hme0:2: flags=<num><UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST,PRIVATE> mtu 1500
inet <DNS service address> netmask <service net netmast> broadcast <service net number>.255

hme1: flags=<num><UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet <control net address> netmask <control net netmast> broadcast <service net number>.255
        ether <ethernet address>

In the preceding output, note that spacing is altered for readability. Also, the broadcast addresses show examples of Class C broadcast addresses. Your own broadcast address might differ, depending on the netmask you use on your service and control networks.

Regarding ifconfig output, if a host cannot provide a service (proxy cache or DNS), the hme0:<num> entry will not be present for that service. On the other hand, a host might have additional hme0:<num> entries, indicating that it has acquired additional service addresses, from other array members.