RE: OSPF vs EIGRP [7:41613]

2002-04-27 Thread Lupi, Guy
on the tunnel interface, works like a charm. Just thought it was interesting so I figured I would send this. ~-Original Message- ~From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]] ~Sent: Thursday, April 18, 2002 10:18 PM ~To: [EMAIL PROTECTED] ~Subject: Re: OSPF vs EIGRP [7:41613

Re: OSPF vs EIGRP [7:41613]

2002-04-19 Thread Howard C. Berkowitz
At 10:57 PM -0400 4/18/02, nrf wrote: Priscilla Oppenheimer wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... He didn't say that BGP negotiates the MTU in any of its PDUs. He just says that mismatched MTUs can be a problem, which is all I mentioned in my message about OSPF also

Re: OSPF vs EIGRP [7:41613]

2002-04-19 Thread Howard C. Berkowitz
There's not a word about MTU in draft 17 of the update to RFC1771 (even being on the working group, I'm not sure if draft 18 is out yet). There is a maximum update length of 4K, but updates are inherently variable length. At 9:53 PM -0400 4/18/02, nrf wrote: Really? I had never heard of

Re: OSPF vs EIGRP [7:41613]

2002-04-19 Thread nrf
That's what I thought, which is why what suaveguru said made me so curious. The only problems with MTU that I thought BGP would have are the same problems that any IP packet might have with MTU (fragmentation, etc.) Howard C. Berkowitz wrote in message [EMAIL PROTECTED]">news:[EMAIL

Re: OSPF vs EIGRP [7:41613]

2002-04-19 Thread Priscilla Oppenheimer
BGP Keepalives are very short, but Updates can be very long. It looks like they can be 4096 bytes from RFC 1771 (not counting headers). BGP relies on TCP and IP, as you know, of course. Those layers would have to make sure that the IP Don't Fragment bit was set to 0 (which means May

RE: OSPF vs EIGRP [7:41613]

2002-04-18 Thread suaveguru
If I am not wrong this problem also occurs for BGP peers with unmatched MTU sizes which causes BGP to flap when they exchange routing tables , especially if one neighbour is configured with full-routes regards, suaveguru --- Priscilla Oppenheimer wrote: The problem happens when the routers

Re: OSPF vs EIGRP [7:41613]

2002-04-18 Thread nrf
Really? I had never heard of this problem. I'm not aware that BGP negotiates MTU in any of its PDU's. Can you provide the RFC that discusses this problem? suaveguru wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... If I am not wrong this problem also occurs for BGP peers with

Re: OSPF vs EIGRP [7:41613]

2002-04-18 Thread Priscilla Oppenheimer
He didn't say that BGP negotiates the MTU in any of its PDUs. He just says that mismatched MTUs can be a problem, which is all I mentioned in my message about OSPF also (although OSPF does in fact also include the MTU in database description packets and refuse to become adjacent with a router

Re: OSPF vs EIGRP [7:41613]

2002-04-18 Thread nrf
Priscilla Oppenheimer wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... He didn't say that BGP negotiates the MTU in any of its PDUs. He just says that mismatched MTUs can be a problem, which is all I mentioned in my message about OSPF also (although OSPF does in fact also include

Re: OSPF vs EIGRP [7:41613]

2002-04-17 Thread Persio Pucci
EIGRP [7:41613] The most frequently mismatched parameters relevant for OSPF configuration seem to be dead intervals mtu sizes. OSPF doesn't care about MTU size. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=41753t=41613

Re: OSPF vs EIGRP [7:41613]

2002-04-17 Thread nrf
Kane, Christopher A. wrote in message news:[EMAIL PROTECTED]... The most frequently mismatched parameters relevant for OSPF configuration seem to be dead intervals mtu sizes. OSPF doesn't care about MTU size. Uh, excuse me? Go read RFC 2178 (OSPF v2), section G.9: When two

RE: OSPF vs EIGRP [7:41613]

2002-04-17 Thread Kane, Christopher A.
The most frequently mismatched parameters relevant for OSPF configuration seem to be dead intervals mtu sizes. OSPF doesn't care about MTU size. Uh, excuse me? Go read RFC 2178 (OSPF v2), section G.9: When two neighboring routers have a different interface MTU for their

Re: OSPF vs EIGRP [7:41613]

2002-04-17 Thread nrf
You got here just before I did. I was just about to say that RFC 2328 overrides 2178. Kane, Christopher A. wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... The most frequently mismatched parameters relevant for OSPF configuration seem to be dead intervals mtu sizes.

RE: OSPF vs EIGRP [7:41613]

2002-04-17 Thread Priscilla Oppenheimer
The problem happens when the routers try to exchange database description packets. One side can send packets that are too large for the other side to receive. Then the routers never achieve adjacency. It's an infamous problem. I was glad that Kevin brought it up. I was thinking we should have

OSPF vs EIGRP [7:41613]

2002-04-16 Thread Madory Douglas C 1Lt 603 ACS/LGC
What experiences have people had in setting up and maintaining OSPF vs EIGRP on a large network? I'm aware of the proprietary implications of EIGRP and the basic differences in design of the protocols - how they are _supposed_ to work, but, in practice, would you say one is more stable /

RE: OSPF vs EIGRP [7:41613]

2002-04-16 Thread Bill Carter
- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Madory Douglas C 1Lt 603 ACS/LGC Sent: Tuesday, April 16, 2002 10:21 AM To: [EMAIL PROTECTED] Subject: OSPF vs EIGRP [7:41613] What experiences have people had in setting up and maintaining OSPF vs EIGRP on a large network? I'm

RE: OSPF vs EIGRP [7:41613]

2002-04-16 Thread Kane, Christopher A.
Also, what about OSPF between Cisco and non-Cisco products? Do they always work together like they're supposed to? Doug, I've worked with OSPF in a multi-vendor environment and had no problems. All the required parameters in the Hello packets were met and neigh/adj's were established with