MTU will be an issue on a link connecting two OSPF neighbors. The MTU value is part of the database description packet and no adjacency will form, if the values are not the same.
Also MTU related issues might arise, because a frame larger than the interface MTU will be discarded. In an IP environment there is fragmentation if DF not set, but Ethernet does not support fragmentation, so dropping is the only possible result.
I personally would not recommend such setups (not knowing the underlying reasons to suggest this setup).
ospf adjacencies will form if you tell the ospf config to ignore mtu size, of course that only matters if you are using ospf. I have this situation myself and unless you are configuring the MTU to be less than 1500 then you shouldn't run into a problem, since by default, hosts are configured with 1500 MTU.
I am facing an issue where I am forced to give the "system jumbo mtu 1522" globally, mtu 1522 on l2 ports and mtu 1700 on the uplink l3 ports. Once I clear my ospf adjacancies, they never form again (gets stuck at loading). What could be the issue?. Once i remove system jumbo mtu..every thing is fine..
You may want to try and increase the routing mtu to 1700 using "system mtu routing 1700".
For the 3750: The size of frames that can be received by the switch CPU is limited to 1998 bytes, no matter what value was entered with the system mtu or system mtu jumbo commands. Although frames that are forwarded or routed typically are not received by the CPU, in some cases packets are sent to the CPU, such as traffic sent to control traffic, SNMP, or Telnet, or routing protocols.
Routed packets are subjected to MTU checks on the egress ports. The MTU value used for routed ports is derived from the system mtu configured value (not the system mtu jumbo value). That is, the routed MTU is never greater than the system MTU for any VLAN. The system MTU value is used by routing protocols when negotiating adjacencies and the MTU of the link. For example Open Shortest Path First (OSPF) protocol uses this MTU value before setting up an adjacency with a peer router.
The problem " system mtu routing 1700" is not supported on 6524ME switches. What you mentioned is right about the issue. I sorted out the issue by giving ip mtu 1522 apart from mtu 1700 on MPLS interfaces.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...