[c-nsp] Network Perefromance
harbor235
harbor235 at gmail.com
Wed Jun 17 09:57:35 EDT 2009
I am definitely aware of IP SLA and also agree that it is very useful,
however, this customer's network is Juniper so I will be
unable to uitlize that feature.
MTR looks like it is doable, however, it uses icmp. I doubt that you can get
an accurate picture of the network using
icmp, can it be programed to use TCP or udp and vary the packet size?
mike
On Tue, Jun 16, 2009 at 4:35 PM, Matthew Huff <mhuff at ox.com> wrote:
> We are a Cisco shop, so we use "ip sla" feature of newer IOS releases with
> CiscoWorks LMS. Netflow is useful for trafic monitoring, but for latency
> and
> jitter, the cisco featureset is really nice.
>
> For example, between two of our voice gateway boxes (running sip trunking
> between them) in NY & SF:
>
> rtr-nyvoip#show ip sla statistics aggregated 1
> IPSLAs aggregated statistics
>
> IPSLA operation id: 1
> Start Time Index: .16:15:07.749 EDT Tue Jun 16 2009
> Type of operation: udp-jitter
> Voice Scores:
> MinOfICPIF: 11 MaxOfICPIF: 11 MinOfMOS: 4.6 MaxOfMOS: 4.6
> RTT Values:
> Number Of RTT: 18000 RTT Min/Avg/Max: 91/91/96
> milliseconds
> Latency one-way time:
> Number of Latency one-way Samples: 0
> Source to Destination Latency one way Min/Avg/Max: 0/0/0
> milliseconds
> Destination to Source Latency one way Min/Avg/Max: 0/0/0
> milliseconds
> Jitter Time:
> Number of SD Jitter Samples: 17982
> Number of DS Jitter Samples: 17982
> Source to Destination Jitter Min/Avg/Max: 0/1/4 milliseconds
> Destination to Source Jitter Min/Avg/Max: 0/1/4 milliseconds
> Packet Loss Values:
> Loss Source to Destination: 0 Loss Destination to Source:
> 0
> Out Of Sequence: 0 Tail Drop: 0
> Packet Late Arrival: 0 Packet Skipped: 0
> Number of successes: 18
> Number of failures: 0
>
> Start Time Index: .15:15:07.749 EDT Tue Jun 16 2009
> Type of operation: udp-jitter
> Voice Scores:
> MinOfICPIF: 11 MaxOfICPIF: 11 MinOfMOS: 4.6 MaxOfMOS: 4.6
> RTT Values:
> Number Of RTT: 60000 RTT Min/Avg/Max: 91/91/103
> milliseconds
> Latency one-way time:
> Number of Latency one-way Samples: 0
> Source to Destination Latency one way Min/Avg/Max: 0/0/0
> milliseconds
> Destination to Source Latency one way Min/Avg/Max: 0/0/0
> milliseconds
> Jitter Time:
> Number of SD Jitter Samples: 59940
> Number of DS Jitter Samples: 59940
> Source to Destination Jitter Min/Avg/Max: 0/1/11 milliseconds
> Destination to Source Jitter Min/Avg/Max: 0/1/7 milliseconds
> Packet Loss Values:
> Loss Source to Destination: 0 Loss Destination to Source:
> 0
> Out Of Sequence: 0 Tail Drop: 0
> Packet Late Arrival: 0 Packet Skipped: 0
> Number of successes: 60
> Number of failures: 0
>
> The config is:
>
> ip sla responder
> ip sla logging traps
> ip sla 1
> udp-jitter x.x.x.x 12420 source-ip x.x.x.x codec g729a
> ip sla schedule 1 life forever start-time now
>
>
> ----
> Matthew Huff | One Manhattanville Rd
> OTA Management LLC | Purchase, NY 10577
> http://www.ox.com | Phone: 914-460-4039
> aim: matthewbhuff | Fax: 914-460-4139
>
>
>
> > -----Original Message-----
> > From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> > bounces at puck.nether.net] On Behalf Of harbor235
> > Sent: Tuesday, June 16, 2009 3:46 PM
> > To: cisco-nsp at puck.nether.net
> > Subject: [c-nsp] Network Perefromance
> >
> > I wanted to ping everyone on tools they were using to understand the
> > performace of their
> > network, specifically, measuring packet loss, latency, and jitter.
> >
> > mike
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list