NetVault 13.0.1 - Administration Guide for Managed Service Providers

When the NetVault Service starts, it attempts to resolve all client IP addresses listed in the machines.dat file, which resides in the etc directory under the NetVault installation directory. Resolving all client addresses can cause a significant delay in the service startup and the machine can appear unresponsive during this time. You can reduce or avoid the startup delay by specifying the addresses that are not to be resolved during startup.

To specify the addresses that are not to be resolved:

In the Navigation pane, click Change Settings.

On the NetVault Server Settings page, complete one of the following actions:

•

To configure default settings for the NetVault Server, continue to Step 3.

•

To configure default settings for a NetVault Client, click Choose machine. In the Choose machine drawer, select the client, and click Go to settings.

Under Services, click Network Manager.

In the Network Manager dialog box, under Connections, configure the following setting:

•

Comma separated list of networks and addresses not to resolve: To reduce or avoid the startup delay, specify the addresses that are not to be resolved during startup.

You can specify a single address or a range, for example, 192.168.1.2 or 192.168.x.x. If you want to configure multiple addresses or networks, use a comma as delimiter.

To get the list of networks from the machines.dat file, issue the following command on Windows:

findstr Network <NetVault home>\etc\machines.dat

The following is an example output:

C:\NetVault\etc>findstr Network machines.dat

Networks=192.168.203.1,192.168.65.1,172.16.245.1

Networks=10.1.40.81,172.16.211.1,172.16.62.1

Networks=10.1.2.37,172.16.22.1,172.16.128.1

Networks=10.1.240.222,172.16.4.1

Networks=192.168.122.1,10.1.240.52

Networks=10.1.80.83,10.1.2.68,172.16.116.1

Networks=192.168.172.1,10.1.40.98,192.168.147.1

Networks=192.168.174.1,10.1.8.71,192.168.120.1

Networks=192.168.122.1,10.1.8.79

Networks=10.1.8.132,192.168.91.1,192.168.106.1

Networks=10.1.8.163,192.168.233.1,192.168.207.1

Networks=10.1.8.16,200.0.0.1

...

Based on this output, you can configure the following values in the Comma separated list of networks and addresses not to resolve box:

10.0.0.0, 172.0.0.0, 192.0.0.0, 200.0.0.0

Some networks may have names instead of IP addresses. To find IP addresses for such clients, you can use the nslookup tool.

Note the following:

•

To prevent the NetVault Service from resolving all networks, specify the first octet of a network address (that is, 192.0.0.0, 10.0.0.0).

•

Using 0.0.0.0 does not prevent the service from resolving the networks.

•

The clients that are offline and listed on the Manage Clients page can also cause the startup delay. To speed up the process, you can remove the clients that are offline or no longer in use.

•

In a domain managed by a Windows-based NetVault Server, you may experience a long delay as the service attempts to resolve all client IP addresses using the NBNS (NetBIOS Name Service) protocol. In this environment, you can use the Comma separated list of networks and addresses not to resolve setting to reduce the startup delay.

You can also use this setting in a NetVault Client Cluster setup to prevent the service from resolving the private cluster IP addresses.

Click Apply to apply the new settings and close the dialog box.