High Packet Drop and connection failure

Thx Macro for your quick reply. I also think the the direct ping between LTM and 2960 shows that the network cable is good at least and there are some other issues with that. Lets see my answer below:-

 

 

1. The duplex and line speed are 1000 full on both end which is matched.

 

2. From what I can see, the network utilization is not high. I don't have mrtg graph but just to get a test using sh int as well as using the dashboard of F5 only.

 

3. see 2

 

4. I have already turned off cdp on the port in order to reduce the packet drop and actually cdp is not useful for port connecting F5 either. The reason behind turning off CDP is that, I would like to reduce the no of packet drop down to zero which is required by our management team so is there any configuration in the cisco end that I can enable/disable in order to further reduce the packet drop due to unused feature or traffic?

 

5. Still scratching my head and pulling my hair with the capture, coz it is in terms of tens of mega bytes. Will start with TCP reset. Any other hints for me?

 

6. No. Not actually using any iRules.

 

7. There are no errors on the cisco etherchannel, just packet drop. In higip, how can I obtain the interface errors?

 

8. Actually I have been fighting for the packet drop for long and found article saying that the flowcontrol is not working very well between cisco and big-ip with the auto setting. Anyway, can try to switch it back to auto if that would really help.

 

9. The LB algorithm is simply round robin but I think it is not related. Coz I have packet drop even simply pinging to the node drirectly from external subnet.

 

 

I have done a capture on both interface (as well as on the node and the external host), therefore I am now checking four * tens of mega bytes capture. The size is huge bcoz the connection is really quite intermittent. I can successfully establish a connection with the node very often but not always. Thats why I have to capture the traffic for a bit long in order to ensure that there must of at least one failure connection within the capture.