Riverbed Steelhead no longer showing up as a peer and is not optimizing traffic

I am looking at the in path IP of the SH that is having trouble. That is 192.168.2.230. The primary interface IP is 192.168.2.231. I am able to ping both IP's from a server that is at the HQ office. I am assuming that would mean the SH's can talk to each other? I am not sure how else to test that?

I manage the Cisco firewalls and there has been no change in them. I remember when I initially set these things up, they had me make changes to the firewall so that they could auto discover and I left that configuration in place.

Any other thoughts on why they are not peering? All four other SH's are peered together and optimizing fine.

Thanks,

Justin

Make sure interesting traffic is generated, then the peering should happen automatically and quickly.

The other possibility I forgot to mention (may be not reqd in this case) was if someone doing passthrough by mistake.

Best,

I added the following commands to my ASA to get the SH's to peer again.

policy-map type inspect dns preset_dns_map
409       parameters
410       message-length maximum 4096
411       policy-map global_policy
412       description RiverBed TCP traffic auto discovery rule
413       class inspection_default
414       inspect dns preset_dns_map
415       inspect ftp
416       inspect h323 h225
417       inspect h323 ras
418       inspect rsh
419       inspect rtsp
420       inspect sqlnet
421       inspect skinny
422       inspect sunrpc
423       inspect xdmcp
424       inspect sip
425       inspect netbios
426       inspect tftp
427       class tcp-traffic
428       set connection advanced-options allow-probes