Steelhead logs frequent "No response from peer x.x.x.x:7850. Count = x" messages
When the Steelhead is using Connection Forwarding, either to another Steelhead or to an Interceptor, it will poll its neighbor device to ensure it is reachable. The steelhead requires a response within 1 sec by default. This message indicates that the steelhead's neighbor polls are timing out and, if the count reaches 3, the neighbor will be marked unavailable.
This issue can be caused by either:
Investigate if network issues between the Connection Forwarding neighbors are preventing neighbor updates.
Steelhead # ping -I inpath0_0 x.x.x.x
Where x.x.x.x is the address of the neigbor configured. This can be verified using:
Steelhead # sh in-path neighbor
In-path Neighbor Enabled: yes
In-path Neighbor Port: 7850
Keepalive Count: 3
Keepalive Interval: 10
Use the VLAN & destination
MAC address as forwarded
by the neighbor: no
Neighbor Name Main Address Port
-------------------- --------------- -----
bfcfe2-backup x.x.x.x 7850
Status: (Connection failed, last updated 20012/12/29 13:50:31)
Additional Addresses:
No additional addresses.
If there are ping failures, please investigate validity of the neighbor Steelhead by login in to it and verify if its interfaces are up and its service is running.
If this is ok, please verify network connectivy so as to ensure connectivy between neighbor Steelhead.
Prior to RiOS 6.5, neighbor updates were handled by the main thread on the Steelhead and contention on this thread could impact these updates. In RiOS 6.5 and later, these updates can now be enabled on their own dedicated thread. Please contact Riverbed Support for assistance in configuring this option.
Steelhead
