Getting Started Guide
Websense X10G Appliance v7.6.4


Status messages from the switches, and the switch alerts that can appear on the console, are described below. Detailed recovery steps are provided for each situation.
This status indicates that the switch was configured by your Websense partner or Websense Technical Support professional in a special way, to accommodate your network.
1.
Make certain that the switch hardware is fully seated in the chassis, and that the switch lever is latched. The switch indicator LED may be on, even if the switch is not fully seated. This is because the pins connecting the switch hardware into the chassis are of varying lengths, so that they connect in this sequence as you insert the switch: grounding pin; power pin; data lines.
3.
It is possible that the switch is in the process of rebooting (to clear an error condition). Try again to verify the switch configuration in 5 minutes.
4.
If you still cannot connect from the blade to the switch, or if you must replace a switch with a new switch that was not configured by a Websense team, then these recovery steps are required (can be accomplished with line console, telnet, or Web UI). Your Websense professional can guide you through these steps.
If you must replace a switch with a new one that has not been set up by a Websense team, insert the switch and latch it. Do not cable it. Then follow these steps:
1.
Log on to the CMC and choose I/O Module Overview at the left. Select the appropriate switch and then initiate a Power Cycle, as shown below:
3.
From the list of options that appears, choose:
10 - Restore configuration to factory defaults (delete config files)
5.
Copy and paste the following configuration commands into the console for switch A2 (all commands also apply to switch A1, but IP address [line 6] for switch A1 is 169.254.253.1):
2.
On any blade except blade 16, to configure switch A1: Run the CLI command "switch A1 configure" in Security Blade Manager. This configures switch A1 for use with all X10G blade servers.
*
Run the CLI command "switch A2 configure wcg" to configure switch A2 to support failover for proxy interfaces on blade 16. (This disables the N interface, used if Network Agent runs on blade in Slot 16.)
*
Run "switch A2 configure na" to configure switch A2 with the N interface for Network Agent supported (default setting).
4.
Wait for the switch to finish rebooting, then run "switch A1 (A2) verify" to verify that the configuration is as expected.