Implementation Guidelines

Background

We have a variety of Rockets to meet your needs, from an entry-level Bottle Rocket to a set of high-capacity appliances serving multiple roles. Use these guidelines to help you plan your implementation and your Rocket installation. We will work with you to create the right solution for your network and your needs. Keep in mind networks grow, and because of that, a little extra capacity at the beginning can be a good thing.

Tip: Multiple Rocket appliances can be set up in “Clusters” to distribute your filtering needs.

Note: To prevent latency issues, ensure that all servers in a cluster configuration are located on a common network with fast and reliable transmission rates.

Web Filter Rocket

The three main things to consider when determining which Web Filter Rocket appliance is right for you are:

  • The number of “protected” workstations
  • The total amount of available bandwidth
  • The structure of your network

Multiple Rocket appliances can be combined in “clusters” to handle any size network.

Single-appliance Web Filter appliances, meaning a single box inline performing policy lookups and reporting, should be able to handle the following amount of traffic:

 

Rocket Traffic  Load
Bottle Rocket 150Mbs
Rocket, 1Gb 300Mbs

 

If you have more than 300Mbs of traffic you should use multiple Rocket appliances. Please note Bottle Rocket Web Filters should not be used as a parent if you have more than 300Mbs of traffic.

Inline Child Rocket appliances should be able to handle the following amount of traffic:

 

Rocket Traffic Load
Rocket, 1Gb 1Gbps (see note below)
Rocket, 10Gb 2Gbps (see note below)

 

If you are expecting to sustain more than 2Gbps of throughput a scalable load-balanced solution should be used. If you wish to add Advanced Reporting with full URL details an additional Advanced Reporting Rocket is required.