Troubleshooting
This chapter describes how to troubleshoot issues, including these topics:
Client-side SteelHead troubleshooting
This section includes troubleshooting suggestions for SteelHead and SteelHead SD on the client side.
Verify SaaS acceleration is running
SaaS Accelerator uses a new method to classify application traffic and the client appliance needs to recognize this type of application traffic. (The SaaS Accelerator uses the DPI classification engine.)
If you do not see accelerated SaaS connections, use the show service saas-accel application cache command. SaaS acceleration will not happen until an entry appears in the output of this command.
To troubleshoot application classification, ensure the logging level is set to info (this is the default level).
To set the log level to info
•Enter these commands on the SteelHead command line:
amnesiac # enable
amnesiac # configure terminal
amnesiac(config)# logging local info
If you don’t want to make this change globally, you can also set the log level specifically for the application classification logs.
To set application classification logs to the info level
•From the CLI, run this command:
logging filter qosd level info
When application classification is successful, log messages for the classification service appear:
“Doing appctrl query dst:... ”
"Snoopy: Classified app for dst:..."
"Snoopy: Appid # found in cache ..."
If application classification is failing, the following message appears in the logs:
"Snoopy: Failed to resolve appctrl server..."
To correct application classification failure, make sure the client SteelHead can resolve hostnames and DNS is working properly. Application classification relies on the appcs.x.riverbed.cc server and the client-side SteelHead must be able to resolve this hostname and reach this server.
Displaying SaaS service cluster peers for client-side appliances
To see details of the SaaS service cluster peered with the client-side SteelHead appliance
•From the SteelHead web interface, choose Reports > Peers.
•From the CLI, run the show peers command.
amnesiac > show peers
S IP Name Model Version Licenses
- --------------- ---------------- ------- ------- -----------------------------
O 20.37.127.226 XNFD25BAE78DF17A SaaS- 1.0.0 CIFS/MAPI/SSL
O 172.16.2.3 steelhead-1 VCX 9.8.1 CIFS/MAPI/SSL/ORACLE-FORMS
O = online, U = unknown
Total appliances: 2
Connected appliances: 2
Client-side SteelHead splice logs also indicate the SaaS service cluster peer.
SteelHead error messages
These errors appear on the SteelHead if an appliance is deleted from the SCM list of SaaS appliances.
•401: Incorrect appliance token.
•This appliance is no longer recognized by the SteelConnect Manager.
SaaS registration errors
To clear these errors, you need to deregister the appliance using the client SaaS acceleration interface.For details, see
Canceling SaaS acceleration.
SteelHead Mobile client troubleshooting
SaaS acceleration uses a new method to classify application traffic, and the SteelHead Mobile clients need to recognize this type of application traffic. (The SaaS Accelerator service runs as part of the qosd process.)
Application classification relies on the appcs.x.riverbed.cc server and SteelHead Mobile clients must be able to resolve this hostname and reach this server.
If you do not see accelerated SaaS connections, use the rbtdebug -f dns_table command to review the DNS mapping between hostnames and IP addresses and the rbtdebug -f app command to review the list of applications the SteelHead Mobile has classified.