In a roundabout fashion I was attempting to point out that this is partially incorrect. You can change the OSPF cost on an interface by either adding the ospf cost command or by tweaking the bandwidth statement.
By default, the OSPF cost for an interface is (10^8)/bandwidth. If you manipulate the bandwidth statement you change the OSPF metric. This is precisely why if you're running OSPF and EIGRP concurrently and you want to adjust the EIGRP metrics without affecting the OSPF metrics you should adjust the interface delay parameter, not the bandwidth. If you were to change the bandwidth parameter you would change both the OSPF and EIGRP metrics. HTH, John >>> "W. Alan Robertson" 5/13/02 2:04:57 PM >>> Revise and extend: There is no direct correlation between the values of the interface "bandwidth" and the "ospf cost" commands. OSPF does not examine the interface "bandwidth" statement, nor does EIGRP examine the interface "ospf cost" statement. I didn't mean to suggest that OSPF cost isn't related to bandwidth... I should have written more clearly. :) I yield the balance of my time... ----- Original Message ----- From: "John Neiberger" To: ; Sent: Monday, May 13, 2002 3:37 PM Subject: Re: Bandwidth command!! [7:44055] > >>> "W. Alan Robertson" 5/13/02 1:06:25 PM > >>> > >Rajesh, > > > >Correct... The bandwidth statement has no impact on other routing > >protocols, like OSPF. OSPF looks at the "cost" of a link in > >determining best path. There's no direct correllation between > >"bandwidth" and "cost." > > There isn't? How does OSPF determine the cost of a link? > > Regards, > John Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=44102&t=44055 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
