On an Interceptor appliance, what does the Neighbor Peers reporting page display?

What is the default behavior of an Interceptor appliance using 2.0 code when its peer Interceptor appliance is
unavailable?

A deployment has two parallel Interceptor appliances (A and B) each across a different link directed at different
data center locations. Each data center has one Steelhead appliance (Steelhead-1 or Steelhead-2). The
administrator wants probes coming into Interceptor A to be first serviced by Steelhead-1, then Steelhead-2 only
if Steelhead-1 is full or unavailable. What is the most appropriate rule to be configured?

A data center location has three Steelhead appliances and one Interceptor appliance clustered together. If
Steelheads A and B are unable to handle the new web traffic on port 80, the administrator does not want the
connection to be serviced by Steelhead C. Given the current rules, we want to prevent traffic from redirecting to
Steelhead C.
Current Rules:
Rule 1: Redirect rule for ports 445, 139, 80, target SH A
Rule 2: Redirect rule for ports 8080, 80, target SH B
Auto (default rule)
Which rule should be added on the Interceptor to achieve desired functionality?

A customer wants to deploy parallel Interceptor appliances. How should an Interceptor appliance be configured
in relation to another parallel Interceptor appliance?

What is the command to verify a configuration of the Interceptor peers and peer neighbors?

The Interceptor appliance can be configured to redirect traffic to the Steelhead appliances via what methods?

If a Steelhead appliance is configured for logical in-path mode:

To configure a Steelhead appliance for logical in-path mode, the following must be enabled in the General
Service Settings page:

What type of configuration must be used on a Steelhead appliance in order to communicate with an Interceptor
appliance?