Troubleshooting Riverbed® Steelhead® WAN Optimizers

Mon 19 May 2014 10:58:09

Abstract

General:

All rights reserved.

This book may be distributed outside Riverbed to Riverbed customers via the Riverbed Support website. Except for the foregoing, no part of this book may be further redistributed, reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without written permission from Riverbed Technology, Inc..

Warning and disclaimer:

This book provides foundational information about the troubleshooting of the Riverbed WAN optimization implementation and appliances. Every effort has been made to make this book as complete and accurate as possible, but no warranty or fitness is implied.

The information is provided on as "as is" basis. The author and Riverbed Technology shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained in this book.

The opinions expressed in this book belong to the author and are not necessarily those of Riverbed Technology.

Riverbed and any Riverbed product or service name or logo used herein are trademarks of Riverbed Technology, Inc. All other trademarks used herein belong to their respetive owners.

Feedback Information:

If you have any comments regarding how the quality of this book could be improved, please contact the author. He can be reached via email at edwin.groothuis@riverbed.com or at steelhead-troubleshooting@mavetju.org, his personal website can be found at http://www.mavetju.org/.


Table of Contents

Preface
1. Introduction to WAN Optimization
1.1. Index
1.2. Why WAN optimization?
1.3. Three different optimization methods
1.4. Effects of WAN optimization on other equipment
2. The Riverbed Approach to WAN Optimization
2.1. Index
2.2. Appliance Setup
2.3. Basic configuration of a Steelhead appliance
2.4. The layout of an optimized TCP session
2.5. The setup of an optimized TCP session.
2.6. WAN Visibility
2.7. The optimization protocol
2.8. Hardware models
3. The Command Line and Tools
3.1. Index
3.2. Dealing with the Command Line Interface
3.3. Tcpdump, the network packet capture tool
3.4. Tcpdump-x
3.5. Ping
3.6. Traceroute
3.7. Telnet
3.8. Tproxytrace
3.9. Nettest
3.10. SSL connect
4. Installation Related Issues
4.1. Index
4.2. Installation steps for fail-to-wire scenarios
4.3. Fail-to-Wire
4.4. Cables
4.5. Network Interface Card speed issues
4.6. IP Subnet configuration related issues
4.7. Wrong location
4.8. In-path support on interface not enabled
4.9. Port security
4.10. Link State Propagation (LSP)
4.11. VPN Concentrators
4.12. Licenses
4.13. LAN and WAN cable switched
4.14. After an RMA
4.15. Best cabling for remote management
5. Operation Related Issues
5.1. Index
5.2. Hardware related issues
5.3. Admission Control
5.4. Auto-negotiation and duplex issues
5.5. LAN speed maxed out
5.6. Watchdogs
5.7. Unexpected restarts of the optimization service
5.8. Unexpected reboots
5.9. Downgrade and upgrade issues
5.10. Time related issues - The NTP service.
5.11. Firewalls in the path
5.12. Data Store Synchronization
5.13. Data store related errors
5.14. WCCP issues
5.15. Asymmetric Routing
5.16. IP Routing Related Issues
5.17. Alarms and health status
5.18. Long lived TCP session treatment
5.19. Order of the in-path rules
5.20. Network monitoring and network management systems
5.21. Web proxies and web caches
5.22. Security
5.23. The Riverbed Services Platform
5.24. Access related problems
5.25. Partitions running out of space
5.26. Memory usage on the Steelhead appliance
5.27. LAN side traffic is seen on the Steelhead appliance
5.28. Service Error
5.29. Can this application be optimized?
5.30. Interceptor cluster related issues
5.31. Expiring SSL certificates
5.32. High CPU related issues
5.33. Central Management Console related issues
6. System Dump
6.1. Index
6.2. Creation of a system dump
6.3. Configuration of the system
6.4. Log files
6.5. Hardware Information
6.6. System Information
6.7. Simplified Routing related files
6.8. ATA controller SMART data
6.9. Asymmetric routing table
6.10. The Image History file
6.11. The file "lsof"
6.12. Memory dump of the process sport
6.13. Out-of-memory profiling
6.14. CIFS pre-population related data
6.15. RSP related data
6.16. SAR statistics
6.17. Active Directory Integration
6.18. Process dumps
7. Different Network Troubleshooting Scenarios
7.1. Index
7.2. Traffic is blocked when the Steelhead appliance goes in by-pass.
7.3. Traffic is not optimized between two sites.
7.4. An optimized TCP Session gets reset or hangs
7.5. Slow network
7.6. Connection-based Admission Control
8. Latency Optimization
8.1. Index
8.2. Introduction to Latency Optimization
8.3. CIFS Latency Optimization
8.4. CIFS Pre-population
8.5. NFS Latency Optimization
8.6. MAPI Latency Optimization
8.7. Windows Active Directory integration
8.8. MS-SQL Latency Optimization
8.9. FTP Latency Optimization
8.10. HTTP Latency Optimization
8.11. SSL Pre-optimization
8.12. SCA Latency Optimization
9. Logging
9.1. Index
9.2. Logging format
9.3. TCP Optimization
9.4. OOB Splice and Connection Pool
10. Further help and support
10.1. Riverbed websites
10.2. Documentation
10.3. Riverbed TAC
A. Jargon
B. Troubleshooting workflow for network performance related issues
B.1. Step One: Does the TCP session get optimized?
B.2. Step Two: Does TCP optimization and data reduction work?
B.3. Step Three: Does latency optimization work

List of Figures

1.1. Serialization delay
1.2. A typical Ethernet frame
1.3. Bytes in-flight over time.
1.4. Retransmission due to a time out in the acknowledgement
1.5. Retransmission due to time out
1.6. LAN/WAN bandwidth comparisons
1.7. Traffic pattern on the client-side LAN side.
1.8. Disk load on the server.
1.9. Traffic pattern on the server-side LAN side.
2.1. Back of a Steelhead appliance
2.2. Ethernet links in normal operation, fail-to-wire and fail-to-block.
2.3. Management via both the primary and auxiliary interfaces
2.4. Three independent TCP sessions
2.5. The setup of a normal TCP session without Steelhead appliances
2.6. The setup of a normal TCP session seen by Steelhead appliances
2.7. Setup of a new OOB Splice
2.8. Termination of an OOB Splice due to admission control
2.9. Termination of the Connection Pool because of the loss of the OOB Splice
2.10. In-path rules on a Steelhead appliance.
2.11. Additional fixed target in-path rule on a Steelhead appliance.
2.12. The setup of an optimized TCP session using Fixed Target rules.
2.13. The setup of an optimized TCP session using the default auto-discovery process
2.14. The setup of an optimized TCP session using the enhanced auto-discovery process
2.15. Peering rules on a Steelhead appliance.
2.16. Tcpdump output showing the Transparency TCP options
3.1. The network diagram
3.2. Setup of an SSH session to the CLI of the Steelhead appliance
3.3. Setup of an SSH session to the CLI of a replaced Steelhead appliance
3.4. Download of a system dump via SCP
3.5. Attempt to access a non-permitted directory
3.6. The Riverbed specific TCP options not decoded in tcpdump before RiOS 6.1.4 and 6.5.2
3.7. The Riverbed specific TCP options for auto-discovery decoded in tcpdump after RiOS 6.1.4 and 6.5.2
3.8. The Riverbed specific TCP options for WAN Visibility Transparency feature decoded in tcpdump after RiOS 6.1.4 and 6.5.2
3.9. The Riverbed specific TCP options decoded in tshark
3.10. The Riverbed specific TCP options decoded in Wireshark
3.11. Display the first ten packets from and to a certain host
3.12. Display the first ten packets between hosts 10.0.1.1 and 192.168.1.1
3.13. A normal 802.3 Ethernet frame
3.14. An 802.1Q VLAN Ethernet frame
3.15. Display the first ten packets between host 10.0.1.1 and host 192.168.1.1
3.16. Capture all traffic for all ICMP traffic from and to host 10.0.1.1
3.17. Capture all traffic from and to host 10.0.1.1 on port 443
3.18. Tcpdump filter for all Ethernet broadcast traffic
3.19. Incorrect TCP checksum messages because of TCP checksum offloading
3.20. Wireshark showing larger than MSS size TCP packets
3.21. Output of the command "show interface inpathX_X gso"
3.22. Examples for using tcpdump-x
3.23. Ping a host via the primary interface
3.24. Ping a host via the in-path interface
3.25. IP address 10.0.1.4 is not in use on this local IP subnet
3.26. IP address 192.168.1.1 didn't reply.
3.27. ICMP packets 3 to 5 and 8 to 9 didn't get answered.
3.28. ICMP based MTU size detection - MTU of 1500 bytes
3.29. ICMP based MTU size detection - MTU of 1492 bytes
3.30. WAN router receives packet via a different path than it send it
3.31. The command to traceroute to a remote host via the primary interface
3.32. Traceroute to a remote host via an in-path interface
3.33. Determining the MTU size with the --mtu option
3.34. Successful traceroute between two hosts
3.35. Failed traceroute due to MTU size issues
3.36. Missing reply for hop three.
3.37. Missing reply for hop three and following.
3.38. Network Unreachable response
3.39. Missing reply for the latest hop.
3.40. Host Unreachable response
3.41. Hop 4 has multiple outgoing interfaces
3.42. Successful TCP session setup via the primary interface
3.43. Successful TCP session setup via the in-path interface
3.44. Telnet attempt to a host which does not exist
3.45. Telnet attempt to a host which does not exist
3.46. Telnet attempt to a host with no service listening on port 139
3.47. Tproxytrace to a host via the primary interface
3.48. Tproxytrace to a host via the in-path interface
3.49. Output of a peer reachability test
3.50. Capture of a peer reachability test
3.51. Output of a net gateway test
3.52. Output of a duplex test
3.53. Output of the IP Port reachability test
3.54. Capture of the IP Port reachability test
3.55. Usage of the ssl-connect command
4.1. Disable LSP during installation of a new Steelhead appliance
4.2. Inpath0_0 is operational and set to fail-to-wire
4.3. Configuring interface wan0_0 with MDI-x
4.4. VLAN bridge to overcome fixed speed/duplex settings
4.5. The output of "show interfaces primary"
4.6. Interface set for auto-negotiation but coming up as half-duplex
4.7. Interface set for fixed speed but with a lot of RX/TX errors
4.8. ARP requests are coming from IP subnet 192.168.2.0/24
4.9. SMB broadcast packets are coming from IP subnet 192.168.2.0/24
4.10. OSPF broadcast and unicast packets and coming from IP subnet 192.168.170.0/24
4.11. Ping the in-path interface IP address from the default gateway
4.12. Tcpdump running for a ping from the Steelhead appliance
4.13. Remove the IP address of inpath0_1 via the CLI
4.14. Duplicate IP addresses on the in-path interfaces
4.15. Steelhead appliance by-passed with a cable.
4.16. Run these tcpdump commands
4.17. No optimization support for inpath0_1
4.18. Enabled in-path interfaces for optimization
4.19. Port security show commands
4.20. Port security configuration commands
4.21. Compare the "Up" status to see which interface was brought down.
4.22. Wrong location of the VPN concentrator
4.23. Correct location of the VPN concentrator
4.24. Automatic fetching of licenses at the startup of a new CX series model
4.25. Failure of automatic fetching because of a DNS related failure
4.26. Manual update of the licenses with "license autolicense fetch"
4.27. Three CLI sessions for troubleshooting
4.28. ICMP Echo Request and Echo Reply show up on the WAN interface.
4.29. Cabling for remote management
4.30. Configuration for routing towards remote management system via the auxiliary interface
5.1. Grep for "Attached SCSI disk" in the bootlogs
5.2. Output of the command "show raid diagram" on a 2050 model
5.3. Output of the command "show raid diagram" on a model 5050 model
5.4. Output of the command "raid swraid mdstat" on a 5050 model
5.5. A Failing disk in the system logs
5.6. Output of the command "show stats fan" on the 100 / 200 / 300 models
5.7. Output of the command "show stats fan" on the 520 / 1020 / 1520 / 2020 models
5.8. Output of the command "show stats fan" on the 3020 / 3520 / 5520 / 6020 / 6120 models
5.9. Output of the command "show stats fan" on the 150 / 250 / 550 / 555 / 755 models
5.10. Output of the command "show stats fan" on the 1050 / 2050 models
5.11. Output of the command "show stats fan" on the 5050 / 6050 / 7050 models
5.12. Output of the command "show stats fan" on the CX255 model
5.13. Output of the command "show stats fan" on the CX555 / CX755 model
5.14. Output of the command "show stats fan" on the CX5055 / CX7055 model
5.15. Output of the command "show stats fan" on the DX8000 model
5.16. Output of the command "show stats fan" on the EX560 / EX760 model
5.17. Output of the command "show stats fan" on the EX1160 model
5.18. Output of the command "show stats fan" on the EX1260 / EX1360 model
5.19. Output of the command "show stats ecc-ram"
5.20. Output of the command "show admission" for a model 560L
5.21. Determining the admission control values via the system dump
5.22. Connection-based admission control for a 250H model
5.23. Check the list of TCP sessions to find the host which uses the most
5.24. Get the list of TCP sessions for one specific host
5.25. Output of the command "show admission internal"
5.26. Optimizaiton service going into TCP Memory Pressure based admission control
5.27. Non-zero receive queues and non-zero send queues
5.28. Wireshark I/O graph for a 1 Mbps optimized WAN bandwidth limit
5.29. Wireshark TCP graph for a 1 Mbps optimized WAN bandwidth limit
5.30. Optimized Throughput graph for a 1 Mbps optimized WAN bandwidth limit
5.31. Ping through a clean network
5.32. Ping through a network with speed/duplex setting issues
5.33. Ping flood on a relative clean path in the network
5.34. Ping flood on a path with duplex configuration or negotiation issues.
5.35. LAN bandwidth is more than 10 Mbps
5.36. The wdt process is too slow
5.37. The optimization service is too slow
5.38. The optimization service has hung threads
5.39. Proper restart of the optimization service
5.40. Optimization service restart because of an assertion failure
5.41. Optimization service restart because of a process failure
5.42. Reboot caused by a kernel panic
5.43. Enabling the crash kernel feature
5.44. This device was rebooted because of loss of power.
5.45. The watchdog interval was larger than expected.
5.46. This device was rebooted by the hardware watchdog.
5.47. Determining reboots based on the IPMI logs
5.48. Output of "show version history": Upgrade to 6.1.5, then downgrade to 6.1.4
5.49. Manual upgrade via the CLI, new image installed on partition 1
5.50. Downgrade was unsuccessful
5.51. Various upgrade failure scenarios
5.52. The standard NTP service configuration
5.53. Status of the NTP service with the command "show ntp status"
5.54. Tcpdump trace for NTP traffic
5.55. Tcpdump trace for NTP traffic
5.56. Manual adjusting the date/time with the command "ntpdate"
5.57. The TCP session goes into pass-through after the third SYN from the client
5.58. Setup of an inner channel with Full Transparency with Firewall Reset WAN visibility
5.59. Data Store Synchronization can be used in various designs
5.60. Data Store Synchronization catching up after a restart
5.61. Duplicate data store ID warnings from a former data store synchronization cluster node
5.62. Duplicate data store ID warning in a data store synchronization cluster
5.63. Prevent optimization from the data store synchronization peer 192.168.1.7
5.64. Detection of duplicate labels
5.65. Detection of duplicate labels
5.66. Use of the command "service error reset"
5.67. A WCCP setup
5.68. Tcpdump of WCCP traffic
5.69. Tcpdump of WCCP traffic
5.70. Tcpdump of WCCP traffic
5.71. Tcpdump shows that the WCCP router is not forwarding packets to the WCCP cache
5.72. Tcpdump shows that the traffic is only forwarded from the server to the client
5.73. Different forms of asymmetric routing.
5.74. Asymmetric routing table via the CLI
5.75. Normal setup of an optimized TCP session on the network map
5.76. Auto-discovery for of an optimized TCP session - Flow of packets
5.77. Auto-discovery for an optimized TCP session - tcpdump
5.78. Client-side Asymmetry on the network map
5.79. Client-side Asymmetry - Flow of packets
5.80. Client-side Asymmetry on the wire
5.81. Client-side Asymmetry in the logs
5.82. Server-side Asymmetry on the network map
5.83. Server-side Asymmetry - Flow of packets
5.84. Server-side Asymmetry on the wire
5.85. Server-side Asymmetry in the logs
5.86. Complete Asymmetry on the network map
5.87. Complete Asymmetry - Flow of packets
5.88. Complete Asymmetry on the wire
5.89. Complete Asymmetry in the logs
5.90. Complete Asymmetry on the network map
5.91. TCP SYN retransmit - Flow of packets
5.92. TCP SYN retransmit on the wire
5.93. TCP SYN retransmit in the logs
5.94. Steelhead appliance with multiple LANs behind it
5.95. Tcpdump of traffic if the in-path IP address is on the same IP subnet as the hosts on the LAN
5.96. Tcpdump of traffic on a different IP subnet behind the Steelhead appliance
5.97. In-path interface gateways
5.98. Overview of the simplified routing table, pre RiOS 8.0
5.99. Overview of the simplified routing table, RiOS 8.0 and later
5.100. Matching the MAC addresses of the gateways with the LAN and WAN interfaces
5.101. Unlearning entries from the macmap tables
5.102. Full output of a log entry for an alarm before RiOS 7.0
5.103. Full output of a log entry for an alarm on RiOS 7.0 and later
5.104. Aggregate alarm tree for RiOS 8.0
5.105. Generic health alarm
5.106. Certificates related alarms
5.107. CPU load related alarms
5.108. License alarms
5.109. RSP License alarms
5.110. Disk alarms
5.111. Domain joining alarms
5.112. File system alarms
5.113. Paging alarms
5.114. RSP / VSP General alarms
5.115. ESXi specific alarms
5.116. RSP License alarms
5.117. Secure Vault alarms
5.118. Fan alarms
5.119. Flash Error alarms
5.120. Generic Hardware alarms
5.121. IPMI alarms
5.122. Memory error alarms
5.123. Power supply alarms
5.124. SSL Hardware alarm
5.125. Temperature alarms
5.126. Asymmetric routing alarms
5.127. Bypass alarms
5.128. Duplex error
5.129. Link state alarms
5.130. Virtual Steelhead related alarms
5.131. Various admission control alarms
5.132. Connection Forwarding alarms
5.133. Data store related alarms
5.134. Halt alarms
5.135. Mismatched Peer alarms
5.136. NFS related alarms
5.137. Optimization Service alarms
5.138. PFS related alarms
5.139. Process dump related alarms
5.140. Serial Cascade configuration alarms
5.141. SMB alarms
5.142. QoS alarms
5.143. Software version alarms
5.144. SSL related alarms
5.145. System Detail Report alarms
5.146. Granite related alarms
5.147. Reset Connections At Startup
5.148. Terminate Connection button in the GUI
5.149. Terminate TCP session via the CLI
5.150. Example of auto kick-off in-path rule
5.151. Configuration of a Kick-off in-path rule
5.152. Default in-path rules
5.153. In-path rules: Add a new pass-through rule
5.154. In-path rules: Change the default WAN visibility
5.155. In-path rules: Add an all-ports auto-discovery rule
5.156. In-path rules: Add an specific TCP port auto-discovery rule
5.157. Disable MAPI optimization
5.158. The right location for a spanning VLAN on a switch
5.159. The TCP sessions towards a web proxy
5.160. Telnet service is not enabled on this Steelhead appliance
5.161. Secure SSH configuration
5.162. HTTP and HTTPS security configuration
5.163. SNMP security configuration
5.164. SNMPv1 request for system.sysName.0
5.165. SNMPv3 configuration for the user "shtest" to the system MIB
5.166. SNMPv3 request for system.sysName.0
5.167. SNMPv3 request with an unknown username
5.168. SNMPv3 request for an unconfigured view
5.169. SNMPv3 request for a disallowed view
5.170. Data store encryption level
5.171. Recreation of an encrypted data store
5.172. After a move from AES_128 encryption to no encryption
5.173. Secure Vault is not unlocked yet
5.174. IPsec negotiation fails between two Steelhead appliances because the other side isn't configured for IPsec Secure Peering
5.175. Tcpdump shows that the IPsec service on the remote Steelhead appliance is not enabled
5.176. Incompatible options in the IPsec configuration
5.177. Tcpdump shows that there are incompatible values in the configuration
5.178. Incorrect shared secret
5.179. Tcpdump shows that the IPsec negotiation fails because of an incorrect shared secret
5.180. Failure due to an unknown SSL peering certificate
5.181. Output of the command "show secure-peering gray-lst-peers"
5.182. Optimized TCP session with an encrypted inner channel
5.183. Remove Steelhead appliance does not have a valid SSL license
5.184. RSP on RiOS
5.185. Steelhead GUI redirection screen
5.186. Output of the command "support show disk"
5.187. An SSH session with verbose logging
5.188. Telnet session to the SSH service
5.189. Setup of an SSH session to the CLI of a replaced Steelhead appliance
5.190. File system alarm
5.191. Output of the command "support show disk"
5.192. Removing an obsolete RSP image
5.193. Removing an obsolete RSP package
5.194. Removing an obsolete RSP backup
5.195. Check for running background tcpdump captures
5.196. Remove obsolete tcpdump capture files
5.197. Remove obsolete process dumps
5.198. Remove obsolete system dumps
5.199. Neural Framing log files
5.200. Running ipconfig on a Windows machine to check the subnet mask
5.201. Running ifconfig on a Unix machine to check the subnet mask
5.202. Tcpdump capture for a LAN side TCP conversation
5.203. Check the MAC address table
5.204. Duplicate DEF and a Service error with a Steelhead Mobile Client
5.205. Duplicate DEF and a Service error but not with a Steelhead Mobile Client
5.206. Requested reference does not exist anymore
5.207. A service error due to a checksum mismatch
5.208. An encrypted or compressed TCP session
5.209. An formerly compressed TCP session
5.210. The traffic summary report
5.211. Network setup for the Interceptor cluster
5.212. Setup of connection forwarding session between Interceptor and Steelhead appliance
5.213. Failure in the setup of connection forwarding session between Interceptor and Steelhead appliance
5.214. Failure in the setup of connection forwarding session between Interceptor and Steelhead appliance
5.215. Failure in the connection forwarding session between Interceptor and Steelhead appliance
5.216. Failure in the connection forwarding session between Interceptor and Steelhead appliance
5.217. SSL certificates have expired
5.218. SSL alarm is being raised
5.219. CPU 7 shows a higher CPU load than the other ones
5.220. Number of packets going through the LAN and WAN side
5.221. Distribution of interrupts for a NIC dealt with by a single CPU
5.222. Distribution of interrupts for a NIC dealt with by multiple CPUs
5.223. Distrubution of interrupts for a NIC dealt with by multiple CPUs
5.224. Statistics show that there are multiple queues for TX and RX
5.225. A lot of CPU usage is in the 'nice' category
5.226. Single spinning CPU
5.227. A userland process is spinning on a CPU
5.228. Single spinning CPU
5.229. CMC 'CMC' connects to a Steelhead appliance
5.230. Output of the command 'show cmc'
5.231. Auto-registration by the Steelhead appliance
5.232. Add Steelhead appliances to the unmanaged peer whitelist.
6.1. Create a system dump from the CLI
6.2. Upload a system dump directly to the Riverbed FTP server
6.3. Create a system dump from the GUI
6.4. Not being able to generate a system dump
6.5. Contents of the active-running.txt file
6.6. Configuration of the syslog daemon and SNMP daemon
6.7. Beginning of the file "messages"
6.8. Format of the log messages by the optimization service
6.9. Beginning of the file "web_access.log"
6.10. Beginning of the file "web_error.log"
6.11. Part of the file "dmesg"
6.12. Part of the file "cli_history_root"
6.13. First ten lines of the file memlog.1
6.14. Output of the "show logging" command, daily rotation
6.15. Output of the "show logging" command, rotation by size
6.16. Manually removing log files
6.17. Output of the sensors section on the 100 / 200 / 300 models
6.18. Output of the sensors section on the 520 / 1020 / 1520 / 2020 models
6.19. Output of the sensors section on the 3020 / 3520 / 5520 / 6020 / 6120 models
6.20. Output of the sensors section on the 150 / 250 / 550 models
6.21. Output of the sensors section on the 1050 / 2050 models
6.22. Output of the sensors section on the 5050 / 6050 / 7050 models
6.23. Output of the sensors section on the 255 models
6.24. Output of the sensors section on the 555 / 755 models
6.25. Output of the sensors section on the EX560 / EX760 models
6.26. Hard disk to chassis mapping for a 1050L and 1050M model
6.27. Hard disk to chassis mapping for a 1050H model
6.28. Hard disk to chassis mapping for a 2050 model
6.29. Hard disk to chassis mapping for a 5050L and 5050M model
6.30. Hard disk to chassis mapping for a 5050H model
6.31. Hard disk to chassis mapping for a 6050 model
6.32. Hard disk to chassis mapping for a 7050L model
6.33. Hard disk to chassis mapping for a 7050M model
6.34. Hard disk to chassis mapping for a 1555L, 1555M and 1555H model
6.35. Hard disk to chassis mapping for a 5055M and 5055H model
6.36. Hard disk to chassis mapping for a 7055L model
6.37. Hard disk to chassis mapping for a 7055M model
6.38. Hard disk to chassis mapping for a 7055H model
6.39. Hard disk to chassis mapping for a DX8000 model
6.40. Various hard disk fields on a 2050 model
6.41. Front LED status fields for a 2050 model
6.42. Physical characteristics of the disks in a 2050 model
6.43. RAID configuration for RAID0 on a 1050H model
6.44. Partition on a 1050H model
6.45. RAID configuration for RAID10 on a 2050 model
6.46. Partition on a 2050 model
6.47. Various IPMI event records
6.48. Output of the command "ipmitool sdr list" on the 1050 / 2050 models
6.49. PS0 is connected, PS1 is not connected
6.50. Licensed hardware in a 2050L model
6.51. The NICs and other PCI cards
6.52. Copper-based bypass cards
6.53. Fiber-based bypass cards
6.54. Virtual bypass cards
6.55. RAID controllers
6.56. Video cards
6.57. SDR Accelerator cards
6.58. System Information for a 550M model
6.59. System information for an EX1160L model
6.60. Hard disk utilization overview
6.61. Ifconfig output
6.62. ECC counter output
6.63. System routing table output
6.64. In-path routing table output
6.65. ARP table overview
6.66. Output of the netstat command
6.67. Output of the command "ss"
6.68. Output of the top program
6.69. The process lists.
6.70. Output of the "who" command
6.71. Contents of /var/log
6.72. Contents of /var/opt
6.73. Output of the "netstat -s" command
6.74. Ethtool section for an auto-negotiated Ethernet link
6.75. Ethtool section for a fixed speed and duplex Ethernet link
6.76. No Ethernet link negotiated
6.77. Ethernet flow control
6.78. TCP segmentation offloading
6.79. The contents of the file macmap_tables
6.80. The contents of the file er/0/pkttab_entries
6.81. Contents of the file "asymrouting_table"
6.82. Contents of the file "image_history"
6.83. Output of the file "lsof.txt"
6.84. Header of the mem-dump file
6.85. Memory based admission based control values
6.86. Connection based admission based control values
6.87. Contents of the file oom_profile.log
6.88. The rcud.conf section for the share \\192.168.1.1\Test
6.89. Files for the share \\192.168.1.1\Test
6.90. Contents of the files initial-copy.status and last-sync.status
6.91. Files in the rsp/slots directory
6.92. Memory allocation for the RSP slot RiverbedSMC
6.93. Overview of the SAR data files
6.94. Contents of the pfs directory
6.95. Contents of the net_ads.out
6.96. Generating a process dump of the process sport by cloning it
6.97. Generating a process dump of the process sport by restarting it
7.1. In-path interface being configured for fail-to-block
7.2. Usage of the telnet command
7.3. Reports -> Networking -> Current Connections
7.4. Output of the "show connections all" command.
7.5. TCP session details
7.6. Output of the "show connections all full" command.
7.7. No room for new TCP options for the auto-discovery phase
7.8. Running tcpdump on the LAN side
7.9. Running tcpdump on the WAN side
7.10. Running tcpdump on the LAN side
7.11. Running tcpdump on the WAN side
7.12. Running tcpdump on the client-side WAN side, seeing the SYN+ packet
7.13. Running tcpdump on the server-side WAN side without the SYN+ packet
7.14. Latency optimized SMB requests response times overview
7.15. CIFS Write Behind has been disabled by the optimization service.
7.16. Comparison of two binary files
7.17. Connection-based admission control for a 5520 model
7.18. Use "lsof" to determine which application is owning a TCP session
7.19. Use "netstat -no" to determine the Process ID of the application owning a TCP session
7.20. Windows Task Manager with Process ID
7.21. A half-closed TCP is about to be terminated
8.1. Example of a TCP session on port 139 being terminated immediately
8.2. Wireshark Response time statistics for an unoptimized CIFS session
8.3. Wireshark Response time statistics for an optimized CIFS session
8.4. Skewed statistics on the client-side Steelhead appliance because of read-ahead in the Windows Explorer.
8.5. Comparison of the client-side and server-side LAN traffic for CIFS latency optimization
8.6. Disable the CIFS read-ahead feature for files with the extension "myob"
8.7. Heads up that the replies from the file servers are slow
8.8. CIFS write-behind stopping because of a full disk.
8.9. Unable to obtain oplock on a file
8.10. CIFS pre-population configuration
8.11. Successful registration of the CIFS pre-population session
8.12. Registration failed due to an unknown hostname
8.13. Registration failed due to an non-responding remote server
8.14. Registration failed due to a login failure
8.15. Registration failed due to a login failure
8.16. A successful sync
8.17. Log file of the Initial Copy
8.18. Manually starting a CIFS pre-population sync
8.19. Unable to read some of the files
8.20. Initial copy failed due to reading errors
8.21. CIFS pre-population failure settings
8.22. No new files found during the periodical sync
8.23. The Last Sync log files shows no new files found
8.24. New files found during the periodical sync
8.25. The Last Sync log files shows new or updated files found
8.26. Status of the pre-population shares during syncing and when the share is idle
8.27. NFS optimization does not work for NFS version 4
8.28. NFS optimization does not work when using Kerberos authentication
8.29. See the MAPI probing option
8.30. 192.168.1.6 points to ssh-primary.example.org
8.31. NTP servers configured are the local Domain Controllers
8.32. DNS SRV records for _ldap._tcp.example.org
8.33. Domain join failed because of a clock skew between the Steelhead appliance and the Domain Controller
8.34. Domain join failed because of DNS related issues
8.35. Domain join failed because the object in Active Directory already exists
8.36. FTP Data reported as unknown protocols
8.37. An HTTP Reply header
8.38. A 304 response code
8.39. Network with Web-browsers, web-caches and web-servers
8.40. An invalid URL error messages due to spaces in the URL
8.41. Output of the command "show protocol http"
8.42. X-RBT-Optimized header
8.43. Enabling the HTTP debugging feature
8.44. The X-RBT-Debug line
8.45. HTTP Optimization scheme
8.46. SSL encapsulated HTTP traffic
8.47. Missing issuer certificate during the import of the server key and certificate
8.48. Output of the command "show protocol ssl server-cert"
8.49. Missing Root CA certificate missing but intermediate certificate is there
8.50. Output of the command "show protocol ssl server-cert" for a chained certificate
8.51. Successful import of the server certificate
8.52. SSL Pre-optimization in-path rule
8.53. SSL discovery list
8.54. SCA connection Direct Branch Deployment
8.55. SCA connection Back-Hauled Deployment
8.56. Output of the command 'show service cloud-accel'
8.57. Output of the command 'show service cloud-accel'
8.58. SCA passed through connections.
8.59. The first hop found by traceroute should be the SRIP-Edge host
8.60. SCA inner channel is not secure.
8.61. SCA invalid CA certificate installed in client browser.
9.1. Example log lines
9.2. Change the logging level of a single part of the optimization level
9.3. Setup of an optimized TCP session from the client-side Steelhead appliance, Enhanced Auto Discovery and no Enhanced Auto Discovery
9.4. Setup of an optimized TCP session from the server-side Steelhead appliance, Enhanced Auto Discovery
9.5. Setup of an optimized TCP session from the server-side Steelhead appliance, No Enhanced Auto Discovery
9.6. Setup of an OOB Splice from the client-side Steelhead appliance, Enhanced Auto Discovery
9.7. Setup of an OOB Splice from the server-side Steelhead appliance, Enhanced Auto Discovery
9.8. Setup of an OOB Splice from the server-side Steelhead appliance, no Enhanced Auto Discovery
9.9. Cannot setup OOB Splice
9.10. Server-side Steelhead appliance, no service listening on TCP port 25, Enhanced Auto Discovery
9.11. Client-side Steelhead appliance, no service listening on TCP port 25, no Enhanced Auto Discovery
9.12. Server-side Steelhead appliance, no service listening on TCP port 25, no Enhanced Auto Discovery
9.13. Server-side Steelhead appliance, no host with IP address 192.168.1.1, Enhanced Auto Discovery
9.14. Client-side Steelhead appliance, no host with IP address 192.168.1.1, no Enhanced Auto Discovery
9.15. Server-side Steelhead appliance, no host with IP address 192.168.1.1, no Enhanced Auto Discovery
9.16. Third SYN received before inner channel got setup
9.17. TCP session closed before the inner channel could have been setup
9.18. Local Steelhead appliance into admission control
9.19. Remote Steelhead appliance into admission control
9.20. Remote Steelhead appliance failed to setup an inner channel
9.21. Remote Steelhead becomes the backup in a High Availability cluster
9.22. Local Steelhead appliance disconnects
9.23. Local Steelhead appliance disconnects

List of Tables

2.1. Model 50, 100, 200, 300
2.2. Model 520, 1020, 1520, 2020
2.3. Model 3020, 3520, 5520, 6020, 6120
2.4. Model 150
2.5. Model 250
2.6. Model 550
2.7. Model 1050
2.8. Model 2050
2.9. Model 5050
2.10. Model 6050
2.11. Model 7050
2.12. Model CX255
2.13. Model CX555
2.14. Model CX755
2.15. Model CX570
2.16. Model CX770
2.17. Model CX1555
2.18. Model CX5055
2.19. Model CX7055
2.20. Model EX560
2.21. Model EX760
2.22. Model EX1160
2.23. Model EX1260
2.24. Model EX1360
2.25. Model DX8000
3.1. The less pager cheat sheet
3.2. Control characters on the CLI
4.1. Cabling for placement of Steelhead appliance between switch and router
4.2. Cabling for placement of Steelhead appliance between two routers
4.3. Cabling for placement of two Steelhead appliances between switch and router
4.4. Cabling for placement of two Steelhead appliances between two routers
5.1. Example of configuration changes for the Simplified Routing feature for the value "none"
5.2. Example of configuration changes for the Simplified Routing feature for the value "dest-only"
5.3. Example of configuration changes for the Simplified Routing feature for the value "all"
6.1. RiOS EX software and matching RiOS version
8.1. HTTP Optimization Scheme Code
8.2. Optimization scheme bit mask
8.3. Cache related category
8.4. Prefetch related category
8.5. Miscellaneous category