No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-Why ISIS adjacency cannot be established when the MTU mismatch between devices

Publication Date:  2012-07-27 Views:  142 Downloads:  0

Issue Description

Q:

Why ISIS adjacency cannot be established when the MTU mismatch between devices?
      

      

Alarm Information

Null
      

Handling Process

A:

Because ISO specifies that IS-IS Hellos must be padded, using type 8 Padding TLVs, to within one octet less than this maximum, partly to allow a router to implicitly communicate its MTU to its neighbors. More important, sending Hellos at or near the link MTU is intended to help detect link failure modes in which small PDUs pass but larger PDUs are dropped. If a neighboring interface does not support the minimum required MTU, the padded Hellos are dropped and no adjacency is established.
      

      

Root Cause

Null
      

Suggestions

 When you deploy ISIS in network, you must guarantee MTU consistent between two connected interface.

END