Sample Connection Report

prot	ip-client-addr	client-port	ip-server-addr	server-port	analysis	tcp_flags	start	end	duration
udp	10.190.36.23	55356	10.190.98.31	50540	complete		2013-04-03 17:09:34.000	2013-04-03 17:11:34.000	120

exporter-ip	exporter-name	input-int	output-int	c2s-flows	c2s-pkts	c2s-octets	c2s-tos	s2c-flows	s2c-pkts	s2c-octets	s2c-tos
10.190.48.31	0060-WestValleyCity-rtr1	Gi0/0	PO0/1	4	986	123,243	ef
10.190.48.32	0060-WestValleyCity-rtr2	Gi0/0	PO0/1					2	5,160	641,923	0
10.190.52.73	0620-FortWorth-rtr3	Gi0/1	Gi0/0	4	986	123,243	ef	2	5,248	652,770	ef

The aboves shows a 120-second bidirectional media stream (probably a phone call) between hosts on a network that looks like this:

.......................
:                     :
: 0060-WestValleyCity :
:                     :
: 10.190.36.23(client):
:        |            :
:    +--------+       :
:    | switch |       :
:    +--------+       :
:       |   |         :
:  g0/0 |   | g0/0    :
:   +----+ +----+     :
:   |rtr1| |rtr2|     :
:   +----+ +----+     :
:po0/1|      |po0/1   :
:.....|......|.........
      |      |
    .----------.
    | MPLS WAN |
    '----------'
.........|.............
:        | g0/1       :
:      +----+         :
:      |rtr3|         :
:      +----+         :
:        | g0/0       :
:        |            :
:    +--------+       :
:    | switch |       :
:    +--------+       :
:        |            :
: 10.190.98.31(server):
:                     :
:  0620-ForthWorth    :
:                     :
.......................

The connection report shows:

asymmetric traffic routing over the two 0060-WestValleyCity routers. This is normally fine and expected, but people are still surprised to see it going on
loss of DSCP marking on the MPLS WAN leading to 0060-WestValleyCity-rtr2. This indicates that the MPLS WAN may not be presering/honoring QoS properly./
packet loss on the MPLS WAN leading to 0060-WestValleyCity-rtr2. Note how the byte/packets are lower than from the ForthWorth router.