No, it's not the same, but it's not the same on a working interface either.
The 15.3(3)S1a ME3600 has a CLNS MTU of 9213. The 15.3(3)S ME3600 has a CLNS MTU of 1497. The 4.3.1 ASR9000 has a CLNS MTU of 9199. 15.3(3)S1a ME3600 is directly connected to the 15.3(3)S ME3600 and has an ISIS adjacency and BFD session. The 15.3(3)S1a ME3600 is directly connected to the 4.3.1 ASR9K and does not have an ISIS adjacency or BFD session. If it was a CLNS MTU issue, I'd suspect the 15.3(3)S1a and 15.3(3)S ME3600 ISIS and BFD session would be down as well, but it's not. That notwithstanding, the BFD session between the 9K and 15.3(3)S1a ME3600 is down as well. ISIS CLNS issue or not, that's not going to work unless BFD works, no? On Nov 12, 2013, at 10:20 AM, Adam Vitkovsky <[email protected]> wrote: > Hi Jason, > > Is the CLNS MTU equal at both ends please? > It appears this is again one of the conditions to form ISIS session in > 15.3(3)S1 > > adam > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
