08-04-2014 05:51 AM - edited 03-04-2019 11:28 PM
When viewing the output of this command, how much traffic would be classed as a "lot"
Over a VPN tunnel between two of our sites and over a period of a few minutes I was seeing the the following bursts between a PC and Exchange Server over the VPN.
SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP Bytes
Tu1 10.0.10.10 Gi0/0.10* 172.27.30.4 06 E8CB EE58 52M
Tu1 10.0.10.10 Gi0/0.10 172.27.30.4 06 E8CB EE58 52M
08-04-2014 06:09 AM
"lot" would really be based on the expected value of the traffic.
It really depends on if the rate is expected or not between the two points.
08-04-2014 06:11 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Well, "lot" could be whenever you ingress rate exceeds egress rate capacity. Or, "lot" might be when you start to encounter queuing which causes delays and/or drops. (NB: the latter usually isn't significant until your exceed 2/3 of egress capacity, assuming general queuing distribution.)
08-04-2014 09:58 AM
Regarding the ingress rate exceeding egress rate. Are we talking about traffic coming into the router LAN side as the ingress and leaving the WAN / Tunnel Interface as the Egress?
08-04-2014 04:42 PM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Perhaps, perhaps not. LAN to WAN is a very common way to exceed an egress port's bandwidth, but whether port is LAN or WAN, doesn't really matter. What matters is how much traffic is being sent to the egress interface.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: