"I have also bumped up the bandwidth as high as possible in lab situations
or staging areas where I was TFTPing a large file across a lab network that

included a back-to-back serial link."

I would have thought bumping up the clockrate parameter would have had more
effect than changing the bandwidth parameter.

JMcL
----- Forwarded by Jenny Mcleod/NSO/CSDA on 02/10/2001 09:04 am -----
                                                                                       
    
                   
"Priscilla
                    Oppenheimer"         To:    
[EMAIL PROTECTED]
                                 Subject:     Re: When to put Bandwidth
on
                    Sent by:             interfaces???
[7:21415]
                   
nobody@groups
                   
tudy.com
                                                                                       
    
                                                                                       
    
                   
29/09/2001
                    03:28
am
                   
Please
                    respond
to
                   
"Priscilla
                   
Oppenheimer"
                                                                                       
    
                                                                                       
    




I would say set the interface bandwidth if the default doesn't match
reality and you are using a feature that uses the bandwidth. IGRP, EIGRP,
and OSPF use bandwidth in their routing protocol metrics. I don't know
about your question about bringing up an backup (ISDN) link. Anyone?

So, when might the default not match reality? Serial ports default to 1.5
Mbps even though the circuit could be faster or slower. You could have a
Frame Relay CIR that is less, and you might want your routing protocol
metrics to match the CIR rather than the default, to avoid a route getting
picked as best when it's really not.

I have also bumped up the bandwidth as high as possible in lab situations
or staging areas where I was TFTPing a large file across a lab network that

included a back-to-back serial link.

At 07:19 AM 9/28/01, [EMAIL PROTECTED] wrote:
>Any time that you don't want EIGRP to send more traffic on a frame relay
>link then it can handle.  Remember that EIGRP will use 50% of what ever is
>set as bandwidth.

The goal of the ip bandwidth-percent EIGRP command is to make sure that the

routing protocol itself doesn't use too much bandwidth. Something is
probably wrong if the routing protocol is using 50 percent of the
bandwidth, and just giving it more bandwidth to consume might work, but
might also cause you not to troubleshoot the real problem. EIGRP is
generally a quiet protocol, except for the incessant hellos, which don't
use much bandwidth.

I think the ip bandwidth-percent command got added because of people who
were running EIGRP on unstable networks and on networks with slow links.
When EIGRP converges (during startup) or reconverges (during problems) it
could use a lot of bandwidth on a slow link. I'm sure there are uses for
the command, but I think it's kind of a Band-Aid command.

Priscilla

[stuff snipped]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=21607&t=21415
--------------------------------------------------
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