After installing a Steelhead appliance at a remote site, users started complaining about some optimized
applications being slower. After some initial investigating, you discovered a backup job was consuming most of
the bandwidth causing congestion. You also found that QoS is configured on the router and should have
prevented this but it did not. What is the most likely cause?
While performing a health check for a Steelhead appliance at a remote site, you noticed some of the passthrough traffic should have been optimized. The pass-through reason for the suspicious traffic is “SYN on WAN
side”. Upon further investigating, you also noticed that all of the traffic initiated at the data center is passthrough while all of the traffic initiated at the remote site is optimized. There is only one path between the data
center and the remote site and both Steelhead appliance are physically in-path. What are the possible causes?
On the Interceptor appliance, connection tracing feature enables you:
In a virtual-inpath deployment, when the Steelhead appliance exports data to a flow data collector:
Authentication fails for certain users after configuring the Server-Side Steelhead Appliance to be a RODC.
What could be the issue?
On Steelheads, by default tcpdump:
After completing the SRDF configuration on both Steelhead appliances and restarting the optimization service,
the SRDF connections in the Current Connections report show a red protocol error icon in the Notes column.
What could be a cause of this issue?
Citrix remote applications, running on the server and to access printers and disk drives, are not performing well.
What can you configure to improve the performance?
Citrix optimization does not work although you removed ports 1494 and 2598 from the Interactive Ports label
and enabled Citrix optimization on the client-side Steelhead appliance. What could be the problem? (Select 2)
What type of problem does the error message below indicate:
Sep 7 22:53:50 SH pm: [pm.NOTICE]: Output from sport:
/opt/rbt/bin/sport (pid 27529) received signal 12 (SIGUSR2) marking bit