On Friday, July 26, 2013 04:37:34 PM Vincent De Keyzer
wrote:
> for what I know, MTU is part of the OSPF negotiation, so
> if they are not the same on both sides, adjacency will
> not come up.
Unless you set both sides to ignore it like you can do with
some other vendor equipment.
Mark.
sign
Hi,
for what I know, MTU is part of the OSPF negotiation, so if they are not
the same on both sides, adjacency will not come up.
Vincent
On 26 July 2013 15:21, R S wrote:
>
>
> In a
> broadcast interface (GE) I’ve to run OSPF between my MX and some systems
> running OSPF.
>
>
> What about
> L
You should always match mtu if you want to avoid having problems down
the line, specially with protocols such as ospf and bgp
On 2013-07-26 7:33 AM, OBrien, Will wrote:
You have to match them appropriately. Take a look at my nexus-srx example.
On Jul 26, 2013, at 9:30 AM, Mark Tinka wrote
You have to match them appropriately. Take a look at my nexus-srx example.
On Jul 26, 2013, at 9:30 AM, Mark Tinka wrote:
> On Friday, July 26, 2013 03:21:32 PM R S wrote:
>
>> In a
>> broadcast interface (GE) I’ve to run OSPF between my MX
>> and some systems running OSPF.
>>
>>
>> What abo
On Friday, July 26, 2013 03:21:32 PM R S wrote:
> In a
> broadcast interface (GE) I’ve to run OSPF between my MX
> and some systems running OSPF.
>
>
> What about
> L2 and L3 MTU ?
>
>
> Can I fix
> greater MTU on MX and the OSPF adj will come up or not ?
> Pls advise
Layer 3 MTU must match o
In a
broadcast interface (GE) I’ve to run OSPF between my MX and some systems
running OSPF.
What about
L2 and L3 MTU ?
Can I fix
greater MTU on MX and the OSPF adj will come up or not ?
Pls advise
___
6 matches
Mail list logo