Latency with Exchange email

Unanswered Question
Jul 27th, 2007

Does anyone know how to measure latency on a WAN link? I have users at a branch location complaining that it takes 30seconds to 2 minutes to send an email..

Here is the show int from my WAN interface.

Ethernet0 is up, line protocol is up

Hardware is PQUICC Ethernet, address is 0004.dc0c.ea67 (bia 0004.dc0c.ea67)

Internet address is xxxxx/29

Backup interface Async5, failure delay 10 sec, secondary disable delay 60 sec,

kickin load not set, kickout load not set

MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 10BaseT

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:58, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: weighted fair

Output queue: 0/1000/64/0 (size/max total/threshold/drops)

Conversations 0/2/256 (active/max active/max total)

Reserved Conversations 0/0 (allocated/max allocated)

Available Bandwidth 2500 kilobits/sec

5 minute input rate 67000 bits/sec, 69 packets/sec

5 minute output rate 60000 bits/sec, 68 packets/sec

885473 packets input, 512074326 bytes, 0 no buffer

Received 16853 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 input packets with dribble condition detected

923552 packets output, 259515911 bytes, 0 underruns

0 output errors, 1299 collisions, 2 interface resets

0 babbles, 0 late collision, 12560 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
purohit_810 Fri, 07/27/2007 - 18:55

Do you have configured QOS?

You can configure PRTG.. that is also for trial version. You can download .. it Add this ethernet interface into that and check HOW BANDWIDTH SPIKE TIME TO TIME..

Second.. On swict port put one LAPTOP .. Install on it sniffer (Ethrpeak analyzer).. Make port mirror it wit connected port.

See what are the harmful machine that are attaking on the interface.

You don't have any error / relibility of link or LOAD. So no need to worry on that.


Dharmesh Purohit

bhedlund Fri, 07/27/2007 - 19:41

The most common way to measure latency is to ping from one site to the other. The higher the latency in milliseconds the worse applications like Microsoft Exchange will perform.

Talk to your Cisco account team or Cisco reseller about Cisco WAAS, which will accelerate the performance of Microsoft Exchange across your WAN links:


bobegilbert Wed, 08/01/2007 - 14:22

You should also investigate Riverbed's WAN optimization solution as they have the most robust platform for Exchange 2000/2003/2007 optimization and acceleration.

They have hundreds of customers using their Steelhead appliances to accelerate Exchange traffic.

More info here Also attached is a performance brief from Riverbed.

Durga Prasad M.S Sun, 07/29/2007 - 12:18


Try using pathping to see the latency from the PC you are facing problems to the Server running you application.


Durga Prasad

rate this post if it helps

srimural Sun, 07/29/2007 - 14:29


you can configure the saa and throw an alarm in the snmp monitoring platform to alert you when the latency goes high. You can try enabling NBAR protocol discovery as well to identify the traffic which is utilising the link. Also consider the path it takes to reach the server.

Regarding Microsoft exchange , if you have roaming profile users, its better to configure a local server and control the site to site traffic.

I hope this helps.

Thanks and Regards,




This Discussion