On 13/Jan/18 05:36, Mike wrote:
> So ... the plot thickens. > > My initial analysis was flawed and reload did not in fact address the > problem. I was able to observe the neighbors all having issues again and > this time I saw that a neighbor relationship was stuck in 'loading' > state. After a lot of looking around, I determined that the interface > and ip mtu both were 9216. I suspect that this mtu was too big and that > my igp had grown to a point where fragmentation was needed but due to an > incorrect mtu here, the updates were not working due to full size > packets. I added 'ip mtu 9000' and the problem has not come back since > (>10 hours now). Hmmh - not sure how this makes sense. But if it's working... Mark. _______________________________________________ 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/
