Re: T1 Timeslot Frame-relay question

From: James (james@towardex.com)
Date: Fri Sep 17 2004 - 01:56:14 GMT-3


On Fri, Sep 17, 2004 at 04:25:03AM +0000, W Walla wrote:
> Thanks Guys!
>
> I enabled fair queing and it seems to help. What is your opinion of these
> extended ping results, over the new T1:

Looks fine other than high latency, but that also looks normal since
you increased the datagram size, hence increasing serialization delay.

There is only so much a 256kbps pipe can carry :P

-J

-- 
James Jun                                            TowardEX Technologies, Inc.
Technical Lead                        Network Design, Consulting, IT Outsourcing
james@towardex.com                  Boston-based Colocation & Bandwidth Services
cell: 1(978)-394-2867           web: http://www.towardex.com , noc: www.twdx.net

> Protocol [ip]: > Target IP address: 192.168.250.3 > Repeat count [5]: 200 > Datagram size [100]: 1500 > Timeout in seconds [2]: > Extended commands [n]: y > Source address or interface: 192.168.0.250 > Type of service [0]: > Set DF bit in IP header? [no]: > Validate reply data? [no]: > Data pattern [0xABCD]: > Loose, Strict, Record, Timestamp, Verbose[none]: > Sweep range of sizes [n]: > Type escape sequence to abort. > Sending 200, 1500-byte ICMP Echos to 192.168.250.3, timeout is 2 seconds: > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > Success rate is 100 percent (200/200), round-trip min/avg/max = 56/57/60 ms > > >From: MADMAN <dmadlan@interprise.com> > >To: James <james@towardex.com> > >CC: W Walla <wallafly@hotmail.com>, ccielab@groupstudy.com > >Subject: Re: T1 Timeslot Frame-relay question > >Date: Thu, 16 Sep 2004 14:03:13 -0500 > > > > > > > >James wrote: > > > >>On Thu, Sep 16, 2004 at 03:52:23PM +0000, W Walla wrote: > >> > >>>/Hello good people- > >>> > >>>I have a question on how this hub and spoke is configured. I have a > >>>full T1 on both side but the HUB shows timeslots 1-24 and the spoke side > >>>doesn't have that sommand. How is this affecting performance, what > >>>should be done to take advantage of the Full T1 between the two. Also, > >>>the HUB has other spokes it shares with the "spoke" in question they are > >>>all 256k with timeslots 1-4 command.. Thanks! > > > > The side the "doesn't have that command" is not fractional capable most > >likely. > > > > Dave > >> > >> > >>By default, timeslots are 1-24. > >> > >>The timeslots shouldn't be determined by you in general per se, it > >>should be determined by what type of contract you purchase from the > >>telco w/ respect to a particular circuit. > >> > >>If you are buying a fractional 384k frame circuit at one location, > >>then it would be 1-6 for the timeslot. The hub site would remain > >>at 1-24, assuming the hub site's circuit ID in telco's database > >>says it is a full T1, and assuming the hub site's circuit is really > >>full T1. > >> > >>-J > >> > >>-- > >>James Jun TowardEX > >>Technologies, Inc. > >>Technical Lead Network Design, Consulting, IT > >>Outsourcing > >>james@towardex.com Boston-based Colocation & Bandwidth > >>Services > >>cell: 1(978)-394-2867 web: http://www.towardex.com , noc: > >>www.twdx.net > >> > >>_______________________________________________________________________ > >>Subscription information may be found at: > >>http://www.groupstudy.com/list/CCIELab.html > >> > > > >-- > >David Madland > >CCIE# 2016 > >Sr. Network Engineer > >Qwest Communications > >612-664-3367 > > > >"Emotion should reflect reason not guide it" > > _________________________________________________________________ > Check out Election 2004 for up-to-date election news, plus voter tools and > more! http://special.msn.com/msn/election2004.armx > > _______________________________________________________________________ > Subscription information may be found at: > http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Fri Oct 01 2004 - 15:00:45 GMT-3