Network recommendations

The Network recommendations for OnePart are detailed below.

This page discusses:

Users

  • Local OnePart users are best served by a 100Mbps LAN

  • Remote OnePart users need at least 2Mbps bandwidth each

Remote files

  • Between OnePart and files: 100Mbps LAN

Indexing remote sources (WAN…) is possible with a OnePart consultant; contact your NETVIBES consulting partner.

Port ranges

You need to allocate 100 consecutive TCP ports for OnePart.

For example, OnePart installs by default on port 10000 (known as the baseport), so it will use ports 10000-10100:

  • the OnePart User Interface uses the base port number 10000.

  • the CloudView Administration Console, which allows you to configure the OnePart backend, uses port 10001

If you need to change the baseport:

  • You can specify a different base port during the installation using the -port parameter.
  • We recommend that you avoid using the ephemeral port ranges: 32768 to 61000 (Linux) or 49152 to 65535 (Windows). For more information, see: http://en.wikipedia.org/wiki/Ephemeral_port .

We also recommend that you:

  • use a reverse proxy to serve end-users on port 80.
  • filter incoming traffic to the OnePart host with a firewall.

Common issues

You may need to open the ports for the baseport entry points on your firewall as detailed in the table below. Once the installation is complete, you can access the Exalead CloudView Services available at BASEPORT+1, for example, http://host:10001.