>Yeah that is what we do alot to check out code before we launch it in
>production. Always TFTPing for a new IOS.
>You throw me when you said 56 or 64 cause clockrate is expressed in bits not
>kbits. Sorry
OK, I see how the bandwidth vs. clockrate could be confusing, when I
used shorthand. You are also correct you need a fast rate for TFTP.
Nevertheless, a slow rate does help see debug.
>Duck
>----- Original Message -----
>From: Howard C. Berkowitz <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Wednesday, August 02, 2000 10:02 AM
>Subject: Re: Clock Rate
>
>
> > >The 56 or 64 is bandwidth clock rate is something different and is not
> > >expressed in kilobytes. A good one to use is 500000 for a lab
>environment.
> >
> > No, while I do agree setting bandwidth is a good habit to get into, I
> > did mean clockrate. The only reason I would set that high a
> > clockrate in a lab is if I was going to do TFTP downloads across the
> > serial interface.
> >
> > >Here is how you set up a dce on a serial interface.
> > >Duck
> > >% Password: timeout expired!
> > >Password:
> > >Password:
> > >c2600>en
> > >Password:
> > >c2600#conf
> > >Configuring from terminal, memory, or network [terminal]?
> > >Enter configuration commands, one per line. End with CNTL/Z.
> > >c2600(config)#int s0/0
> > >c2600(config-if)#ip addre 10.1.1.1 255.255.255.0
> > >10.1.1.0 overlaps with Ethernet0/0
> > >c2600(config-if)#ip addre 10.2.1.1 255.255.255.0
> > >c2600(config-if)#clock
> > >c2600(config-if)#clock r
> > >c2600(config-if)#clock rate ?
> > > Speed (bits per second)
> > > 1200
> > > 2400
> > > 4800
> > > 9600
> > > 14400
> > > 19200
> > > 28800
> > > 32000
> > > 38400
> > > 56000
> > > 57600
> > > 64000
> > > 72000
> > > 115200
> > > 125000
> > > 128000
> > > 148000
> > > 500000
> > > 800000
> > > 1000000
> > > 1300000
> > > 2000000
> > > 4000000
> > > 8000000
> > >
> > > <300-4000000> Choose clockrate from list above
> > >
> > >c2600(config-if)#clock rate 500000
> > >c2600(config-if)#ba
> > >c2600(config-if)#ban
> > >c2600(config-if)#bandwidth ?
> > > <1-10000000> Bandwidth in kilobits
> > >
> > >c2600(config-if)#bandwidth 56
> > >c2600(config-if)#no sh
> > >----- Original Message -----
> > >From: Howard C. Berkowitz <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Sent: Wednesday, August 02, 2000 8:29 AM
> > >Subject: Re: Clock Rate
> > >
> > >
> > > > >How does one know the proper clock rate to set on a DCE interface.
> > > > >I understand
> > > > >that in real world apps, this would be provided by the
> > > > >Telco....but....in a lab situation,
> > > > >or any other for that matter that requires to routers to be linked
> > > > >through their serial interfaces,
> > > > >what is the best way to determine the proper clock rate?
> > > > >
> > > > >Thanks,
> > > > Roman
> > > >
> > > >
> > > > Well, in the Cisco training labs, we generally used 56 or 64 Kbps. A
> > > > conservative speed that was gentle on cable requirements.
> > > >
> > > > In a lab, you'll frequently find that slower is better, if, for
> > > > example, you are running a debug and want to see events.
> >
> > ___________________________________
> > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> > FAQ, list archives, and subscription info: http://www.groupstudy.com
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
