From: Courtney Alexander Foster (cfoster@xxxxxxx)
Date: Fri Dec 14 2001 - 12:37:05 GMT-3
Well...it is only good to specify a bandwidth on an Ethernet interface
if you have more than one way to get to the same destination...and you
would like one to be preferred over another. Also, if you have multiple
links one being 10MB and the other being 100MB...you could use the
bandwidth statement to make them look identical so that they will do
load balancing. Bandwidth is also good if you have atm and Ethernet in
the same box. ATM at 144MB and Ethernet at 100MB is calculated as being
the same speed to many protocols such as OSPF.
Hope this help,
-CAF
-----Original Message-----
From: Thomas Larus [mailto:tlarus@mwc.edu]
Sent: Friday, December 14, 2001 10:11 AM
To: ccielab@groupstudy.com
Subject: Is there any need to specify bandwidth on ethernet interfaces,
since the default should always be correct?
I have read a lot of posts where very smart people suggest always
specifying bandwidth. But with Ethernet, the bandwidth will always be
correct, wont it? Same for token ring, isnt it? If it is ring-speed
16, the sho int will show 16, and that will be used by IGRP and EIGRP.
It would seem that just about the ONLY important place to specify the
bandwidth is serial interfaces, where it is rare in a practice lab to be
using the default bandwidth for a full T1 synch serial interface). I
dont even know how I would ever set the clock rate 1.544, since it is
not offered as an option to the clock rate command. (But this is
bringing back unpleasant memories of threads past. Please bring us
back to the present, spirit, Scrooge pleads.)
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:43 GMT-3