From: Michael Snyder (msnyder@revolutioncomputer.com)
Date: Thu Feb 26 2004 - 01:48:54 GMT-3
-----Original Message-----
From: Jonathan Hays [mailto:nomad@gfoyle.org]
Sent: Wednesday, February 25, 2004 6:13 PM
To: ccielab@groupstudy.com
Subject: RE: Very Stupid question about showing clock speed of a normal
serial interface.
you wrote:
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
>Behalf Of Michael Snyder
>Sent: Wednesday, February 25, 2004 11:09 AM
>To: ccielab@groupstudy.com
>Subject: Very Stupid question about showing clock speed of a
>normal serial interface.
>
>
>I hit a silly thing last night, that I thought was simple but wasn't
>
>I was doing some frame-relay traffic shaping, didn't remember the exact
>speed my frame-relay switch.
>
>I wanted to nail down the port speed.
>
>I tried show controller, show int, show ip int.
>
>I understand that show service-mod would give me the speed,
>but this was
>a normal cisco 60 pin serial interface, not an integrated dsu/csu.
>
>The hardware will auto-switch speeds on a serial interface, which means
>the router has to know the port (clock) speed of the interface.
>
>Where do you show that auto-switched port speed?
Let me understand this better: do you have a back-to-back DB-60 serial
cable from your rouer to the frame switch? If not, please describe the
setup in more detail.
On a lab setup with back-to-back DB-60 serial cables, the speed shows up
on the physcial DCE side of the cable:
R8#sh controller serial 0/0
Interface Serial0/0
Hardware is PowerQUICC MPC860
DCE V.35, clock rate 64000
idb at 0x82479F98, driver data structure at 0x82482284
SCC Registers:
[snip]
So you are asking how to see the clock rate on the other end (DTE), is
that correct?
--------------------------------------------------------------
R2#show controllers s 0
HD unit 0, idb = 0x2B5008, driver structure at 0x2BC5C8
buffer size 2024 HD unit 0, V.35 DTE cable
cpb = 0xE2, eda = 0x408C, cda = 0x40A0
RX ring with 8 entries at 0xE24000
00 bd_ptr=0x4000 pak=0x72979C ds=0xE1F244 status=80 pak_size=326
01 bd_ptr=0x4014 pak=0x729A4C ds=0xE18F34 status=80 pak_size=326
02 bd_ptr=0x4028 pak=0x734DDC ds=0xE640A4 status=80 pak_size=86
03 bd_ptr=0x403C pak=0x73431C ds=0xE61DE4 status=80 pak_size=12
04 bd_ptr=0x4050 pak=0x6B43B0 ds=0xE1A094 status=80 pak_size=229
05 bd_ptr=0x4064 pak=0x6B3E50 ds=0xE1FAF4 status=80 pak_size=88
06 bd_ptr=0x4078 pak=0x734B2C ds=0xE637F4 status=80 pak_size=86
07 bd_ptr=0x408C pak=0x72A078 ds=0xE1E994 status=80 pak_size=12
08 bd_ptr=0x40A0 pak=0x733B0C ds=0xE203A4 status=80 pak_size=326
cpb = 0xE2, eda = 0x4814, cda = 0x4814
TX ring with 1 entries at 0xE24800
00 bd_ptr=0x4800 pak=0x000000 ds=0xE32EF0 status=80 pak_size=16
01 bd_ptr=0x4814 pak=0x000000 ds=0xE32B18 status=80 pak_size=86
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns
--More--
In my case my frame switch is a 50 pin ags port connected to a crossover
60 pin going to a 2501 serial port.
Don't get me wrong, I can look at ags config to get the port speed.
But stubbornly I wanted to find the incoming clock speed on the 2501.
Whatever the ags is clocking out, the 2501 has to be syncing to it.
This archive was generated by hypermail 2.1.4 : Fri Mar 05 2004 - 07:13:57 GMT-3