The MPLS-OPS Archive

Cell Relay Retreat>MPLS-OPS Archive>month:2004-Oct> msg00014



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

vendor mtu differences

  • From: "Amos Rosenboim" <r.amos@zahav.net.il>
  • Date: Wed, 6 Oct 2004 22:23:45 +0200
  • Resent-Date: Wed, 6 Oct 2004 17:11:56 -0400
  • X-OriginalArrivalTime: 06 Oct 2004 20:24:11.0218 (UTC) FILETIME=[7088AB20:01C4ABE2]

Hi all,

 

While adding a Juniper router to a cisco based network I noticed something that looks strange to me.

We are running isis as the igp.

As far as I know isis requires the mtu to be equal on any adjacent routers. When adding the juniper isis adjacency wouldn’t come up. The cisco would show the adjacency in init state while the juniper wouldn’t show any adjacency.

When checking a little deeper I noticed that clns/iso mtu of the routers is different when both of them are configured with the same L2 mtu. The solution by the way was to increase the mtu in the juniper side so iso/clns mtu would be the same.

My question is: what is the implementation difference between those vendors that causes this?

 

Thanks

Amos