> Mike > Sent: Sunday, January 14, 2018 2:32 AM > > > >> mtu 9000' and the problem has not come back since > >> (>10 hours now). > >> > >> > > Hmm could it be that you hit the mtu limit of your links (which is not > > 9216 but just 9000)? > > > > adam > > Thats what Im thinking; the hardware mtu was set to 9216 but for whatever > reason the mtu actually was not that and so ospf flooding couldn't complete > since full mtu sized packets were lost/damaged. > Setting the ip mtu down to 9000 was the answer. Ugh. > Try pinging with mtu higher than 9000 and fragmentation disabled to see if it indeed is the case. Or you can verify with the provider of these links, to see what is the mtu on these links.
adam netconsultings.com ::carrier-class solutions for the telecommunications industry:: _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
