I'd like to get your thoughts on the following please:
We have a Cisco 6509-E running "ipservicesk9_wan-mz.122-33.SXI4a" code and we have an FWSM module within it(WS-SVC-FWM-1). The FWSM is setup to run two contexts, an "inside" context and an "outside" context.
Now add two servers into the mix. One is connected to the "inside" context and the other is connected to the "outside" context.
All network interfaces along the way are set to standard MTU size = 1500bytes and are Gigabit Ethernet.
Running several ping tests between these two servers yields the following ping response times:
1. Test 1 - packet size = 56bytes, average response time = ~0.3ms
2. Test 2 - packet size = 1500bytes, average response time = ~1.4ms
3. Test 3 - packet size = 6000bytes, average response time = ~3.5ms
4. Test 4 - packet size = 10000bytes, average response time = ~4.3ms
Do these response times seem about right or are they a little on the high side? I'm more thinking of the response times for the pings where I have used the larger packet sizes.
Am aware that the switch and FWSM with its MTU set to 1500bytes will start fragmenting the packets. Have seen similar latency for TCP unicast traffic and my thoughts are that the interface when receiving massive size packets is dropping them causing TCP retransmission.
That's my thoughts but would appreciate your thoughts on whether the times I have shown above seem about right or whether it is worthwhile me raising a case with Cisco TAC.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.