Operating tips

60199 | Release Notes | X-Series Appliances | 2-February-2015

Interface setup tips

Avoiding port conflicts

Web security deployment tips

Backup and restore tips

Interface setup tips

Using the P2 interface

If the P2 interface is used and it is in the same subnet as P1, the default gateway is automatically assigned to P2, which is bound to eth1. You should perform a test to ensure that outbound packets can reach the Internet.

Changing the P1 interface IP address

Sometimes it is necessary to change the blade server P1 interface IP address. What is affected and what must be done depends on the configuration of your blade servers and the details of your deployment. The number of activities that must be performed and the service disruption can be significant. If possible, retain the current P1 interface IP address.

If you must change the address, see X-Series: Changing the P1 Interface IP Address for complete details.

Avoiding port conflicts

See the ports list for a table of the Websense software module versions that are compatible with each appliance version.

Check the ports article to avoid port conflicts if you plan to make a change from a default port.

For example, if you want to use an HTTP proxy server port that is different from the default port (8080), be sure to check the ports list first, to avoid conflict with ports already in use by the X-Series.

Web security deployment tips

Policy source tips

When Policy Broker is run on an X-Series appliance (configured as the full policy source), all Policy Server instances that point to that Policy Broker must be installed on X-Series appliances (configured as user directory and filtering appliances). You cannot install and run Policy Servers on off-box machines and point them to a Policy Broker that runs on an appliance. This configuration is not supported.

You can run Policy Server on multiple appliances (configured in user directory and filtering mode) and point these appliances to a Policy Broker running either on or off an appliance.

Policy Broker replication is not supported when Policy Broker resides on an appliance. If you plan to enable Policy Broker replication, be sure that your policy source is not an appliance.

Subscription key tip

In a deployment with the TRITON AP-WEB Hybrid Module and multiple Policy Server appliances, use the TRITON AP-WEB with Hybrid Module subscription key for the policy source appliance (the Policy Server that connects to Sync Service), and use a TRITON AP-WEB subscription key for all other appliances. Otherwise, you receive superfluous alerts from the hybrid service.

Integrated Windows Authentication (IWA) tip

When Content Gateway Integrated Windows Authentication (IWA) is configured, if the appliance hostname is changed, IWA will immediately stop working. To repair the IWA configuration, log onto the Content Gateway manager, unjoin the stale domain and join the domain with the new hostname.

Backup and restore tips

When configuring scheduled backups to a remote storage location (FTP or Samba share), make sure that the account used for backup file creation has read and write permissions.

In a multiple Web security blade deployment, after restoring the configuration of a policy source security blade, restart any filtering only or user directory and filtering security blades in your network to ensure that user requests are managed correctly.