Multi-topology IS-IS

IS-IS has “forever” (at least since RFC 1195) supported multiple layer-3 protocol, but always with a nasty side-effect: if a link in your network did not support one of them, you could get hard-to-diagnose black holes. The problem is illustrated in the left-hand column of the following diagram. Due to a single IS-IS topology, the shortest path between A and B is the direct link and since IPv6 is not enabled on that link (click on the diagram to get an enlarged version where you'll be able to see the link colors), A and B cannot exchange IPv6 traffic even though there’s an alternate path between them.

I’m describing further implications of single/multi-topology IS-IS and deployment guidelines in the Building IPv6 Service Provider Core webinar.

When you enable multi-topology IS-IS (right-hand column in the diagram), the routers build two topologies, one for each L3 protocol (usually IPv4 and IPv6) and can find the optimum path for each L3 protocol even when some links in the network support only one of them.

You’ll find more details in the Multi-topology IS-IS white paper published by Cisco.

3 comments:

  1. Yap Chin Hoong11 June, 2010 08:40

    Hi Ivan, is the concept of this multi-topology is basically the same thing as the "multi-area" or "multi-process" IS-IS to be precise. Thank you. :)

    one more question, to you feel that the "multi-area IS-IS configuration" that often found in many docs should be referred to as "multi-process IS-IS configuration"? The wording of the area really made me mad, same like VTP, VLAN trunking procotol, that has nothing to do with VLAN trunking. 8-)

    ReplyDelete
  2. Ivan Pepelnjak15 June, 2010 18:25

    They are three completely different topics. Will write about the other two as well.

    ReplyDelete
  3. the link to the MT ISIS white paper no longer works:

    http://www.cisco.com/en/US/products/ps6553/products_white_paper09186a00801e199f.shtml

    ReplyDelete

You don't have to log in to post a comment, but please do provide your real name/URL. Anonymous comments might get deleted.

Ivan Pepelnjak, CCIE#1354, is the chief technology advisor for NIL Data Communications. He has been designing and implementing large-scale data communications networks as well as teaching and writing books about advanced technologies since 1990. See his full profile, contact him or follow @ioshints on Twitter.