Pretty sure, but ready to be corrected if there are exceptions:

Point to Point Serial link is full duplex.
Data is being clocked in and out at the same time, by Tx and Rx clocks (even
though those clocks may be tied together) so capability is 256K in both
directions simultaneously.

I suppose the encapsulation may alter this. I take it that something like
X25 encapsulation, where the receiving station sends acknowledgements before
further transmissions, will go some way towards making it half duplex?
I believe the crux of it is that the link is capable of full duplex if the
higher layers can handle it.

Anyone care to clarify?

Gaz

""Jason J. Roysdon""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> The average sampling can be changed on a per-interface basis with the load
> command.  I usually change ports I'm testing to 'load 30' so I can easily
> see after 30 seconds of generated traffic how a link is performing.  10
> minute sampling would just be 'load 600.'
>
> One of our the groups gurus can answer you best on the speeds, but it's my
> understanding that the total transmit and receive can't go above the total
> speed on a serial link, making it a half-duplex connection (but that seems
> totally wrong since a T1 has two pair of wires, and I believe one pair is
> for transmit and the other receive).  I truly don't know any of these
layer
> 1 details, but just spouting off the top of my head with random logical
> guesses ;-p
>
> --
> Jason Roysdon, CCNP+Security/CCDP, MCSE, CNA, Network+, A+
> List email: [EMAIL PROTECTED]
> Homepage: http://jason.artoo.net/
>
>
>
> ""Sim, CT (Chee Tong)""  wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Hi.. group
> >
> > May I ask if a serial link is said to be 256K, does it mean that the
both
> > input and output rate cannot exceed 256K or the SUM of input rate and
> output
> > rate cannot exceed 256K.
> >
> > What is the Duplex type of Serial link as shown below?
> >
> > Why some of the serial link traffic rate are based on 5 minute in/output
> > rate, but some of them are based on 10 minute in/output rate.   How to
> > change it?  Does it shown the same info?  How they count? They
determined
> > the number of bits in 5 minute and divided by the number of second in 5
> > minute 5X60s??
> >
> >
> >
> > SIN01>sh int s2/0
> > Serial2/0 is up, line protocol is up
> >   Hardware is M4T
> >   Description: --- Connects to LON01 S2/0 - MCI Circuit ID W0B73202 ---
> >   Internet address is 57.192.240.70/30
> >   MTU 1500 bytes, BW 256 Kbit, DLY 20000 usec,
> >      reliability 255/255, txload 77/255, rxload 49/255
> >   Encapsulation HDLC, crc 16, loopback not set
> >   Keepalive set (10 sec)
> >   Last input 00:00:01, output 00:00:00, output hang never
> >   Last clearing of "show interface" counters never
> >   Input queue: 0/75/0 (size/max/drops); Total output drops: 14248
> >   Queueing strategy: weighted fair
> >   Output queue: 0/1000/64/0 (size/max total/threshold/drops)
> >      Conversations  0/20/256 (active/max active/max total)
> >      Reserved Conversations 0/0 (allocated/max allocated)
> >   5 minute input rate 50000 bits/sec, 28 packets/sec
> >   5 minute output rate 78000 bits/sec, 32 packets/sec
> >      101610672 packets input, 3280206236 bytes, 0 no buffer
> >      Received 872308 broadcasts, 1 runts, 35 giants, 0 throttles
> >      5313 input errors, 4073 CRC, 0 frame, 7 overrun, 0 ignored, 1233
> abort
> >      115170761 packets output, 3847528448 bytes, 0 underruns
> >      0 output errors, 0 collisions, 547 interface resets
> >      0 output buffer failures, 0 output buffers swapped out
> >      554 carrier transitions     DCD=up  DSR=up  DTR=up  RTS=up  CTS=up
> >
> > ==================================================================
> > De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
> > is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
> > onterecht ontvangt wordt u verzocht de inhoud niet te gebruiken en
> > de afzender direct te informeren door het bericht te retourneren.
> > ==================================================================
> > The information contained in this message may be confidential
> > and is intended to be exclusively for the addressee. Should you
> > receive this message unintentionally, please do not use the contents
> > herein and notify the sender immediately by return e-mail.
> >
> >
> > ==================================================================
> > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=1204&t=864
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to